{"query_id": "q-en-kubernetes-0000ac51c1276b4740fb122d9b802bdadd2033eee75dec85386e4ab3896771a8", "query": "} factory.CreateFromConfig(policy) <ins> hpa := factory.GetHardPodAffinitySymmetricWeight() if hpa != v1.DefaultHardPodAffinitySymmetricWeight { t.Errorf(\"Wrong hardPodAffinitySymmetricWeight, ecpected: %d, got: %d\", v1.DefaultHardPodAffinitySymmetricWeight, hpa) } } func TestCreateFromConfigWithHardPodAffinitySymmetricWeight(t *testing.T) { var configData []byte var policy schedulerapi.Policy handler := utiltesting.FakeHandler{ StatusCode:   500, ResponseBody: \"\", T:            t, } server := httptest.NewServer(&handler) defer server.Close() client := clientset.NewForConfigOrDie(&restclient.Config{Host: server.URL, ContentConfig: restclient.ContentConfig{GroupVersion: &api.Registry.GroupOrDie(v1.GroupName).GroupVersion}}) informerFactory := informers.NewSharedInformerFactory(client, 0) factory := NewConfigFactory( v1.DefaultSchedulerName, client, informerFactory.Core().V1().Nodes(), informerFactory.Core().V1().Pods(), informerFactory.Core().V1().PersistentVolumes(), informerFactory.Core().V1().PersistentVolumeClaims(), informerFactory.Core().V1().ReplicationControllers(), informerFactory.Extensions().V1beta1().ReplicaSets(), informerFactory.Apps().V1beta1().StatefulSets(), informerFactory.Core().V1().Services(), v1.DefaultHardPodAffinitySymmetricWeight, ) // Pre-register some predicate and priority functions RegisterFitPredicate(\"PredicateOne\", PredicateOne) RegisterFitPredicate(\"PredicateTwo\", PredicateTwo) RegisterPriorityFunction(\"PriorityOne\", PriorityOne, 1) RegisterPriorityFunction(\"PriorityTwo\", PriorityTwo, 1) configData = []byte(`{ \"kind\" : \"Policy\", \"apiVersion\" : \"v1\", \"predicates\" : [ {\"name\" : \"TestZoneAffinity\", \"argument\" : {\"serviceAffinity\" : {\"labels\" : [\"zone\"]}}}, {\"name\" : \"TestRequireZone\", \"argument\" : {\"labelsPresence\" : {\"labels\" : [\"zone\"], \"presence\" : true}}}, {\"name\" : \"PredicateOne\"}, {\"name\" : \"PredicateTwo\"} ], \"priorities\" : [ {\"name\" : \"RackSpread\", \"weight\" : 3, \"argument\" : {\"serviceAntiAffinity\" : {\"label\" : \"rack\"}}}, {\"name\" : \"PriorityOne\", \"weight\" : 2}, {\"name\" : \"PriorityTwo\", \"weight\" : 1} ], \"hardPodAffinitySymmetricWeight\" : 10 }`) if err := runtime.DecodeInto(latestschedulerapi.Codec, configData, &policy); err != nil { t.Errorf(\"Invalid configuration: %v\", err) } factory.CreateFromConfig(policy) hpa := factory.GetHardPodAffinitySymmetricWeight() if hpa != 10 { t.Errorf(\"Wrong hardPodAffinitySymmetricWeight, ecpected: %d, got: %d\", 10, hpa) } </ins> } func TestCreateFromEmptyConfig(t *testing.T) {", "positive_passages": [{"docid": "doc-en-kubernetes-88466bc637a805045217da94feabbdbd3df0ba52cd0d9904e95d3984c4cf4efa", "text": "( noticed this) HardPodAffinitySymmetricWeight should be in the , not in KubeSchedulerConfiguration If/when fixing this, we need to be careful to do it in a backward-compatilble way.\nDo you mean ? It seems scheduler policy config's args can not passed to FitPredicates; it need to update related interface. For the : mark to be deprecated and set scheduler policy config to HardPodAffinitySymmetricWeight if policy config is empty.\nAre you working on this? if no, I can take it.\n, nop; please go ahead.\n/ / / , When reviewing the PR, there's one question on : the default value of is 1, which means the weight (1) will always add to priorities if term matched (), does it our expectation? And the user has to set it to 0 to disable it. IMO, the default value of should be 0.\nThe value 1 (instead of 0) was chosen so that if you say A must run with B, there is an automatic preference that B should run with A. This seems like reasonable behavior.\nThanks very much; reasonable case to me. But it seems we can not disable it: if set to 0, the default funcs will set it to default (1); similar result to un-set. Anyway, no user complain this now :).", "commid": "kubernetes_issue_43845", "tokennum": 306}], "negative_passages": []}
{"query_id": "q-en-kubernetes-002b4e03797943125ecc2bf5697fa0fc18e6137434144c1a6bbfcefbb129a789", "query": "opName := op.Name return wait.Poll(operationPollInterval, operationPollTimeoutDuration, func() (bool, error) { start := time.Now() <del> gce.operationPollRateLimiter.Accept() </del> duration := time.Now().Sub(start) if duration > 5*time.Second { glog.Infof(\"pollOperation: waited %v for %v\", duration, opName)", "positive_passages": [{"docid": "doc-en-kubernetes-599cbd9914ac52a34ee08ac617d1f4bd774f52f2d5bdcb07fa1a0e76f7194545", "text": "On a large cluster, the routecontroller basically makes O(n) requests all at once, and most of them error out with \"Rate Limit Exceeded\". We then wait for operations to complete on the ones that did stick, and damn the rest, they'll be caught next reconcile (which is a while). In fact, in some cases it appears we're spamming hard enough to get rate limited by the upper-level API DOS protections and seeing something akin to , e.g.: We can do better than this!\nc.f. , which is the other leg of this problem\nI took a look into code and it seems that we are doing full reconciliation every 10s. If we need to create 2000 routes at the beginning it seems to frequently. I think that we need to: first compute how many routes we have to create based on that try to spread them over some time to reduce possibility of causing 'rate limit exceeded' I will try to put some small PR together as a starting point.\nI'm reopening this one, since this doesn't seem to be solved. So basically something strange is happening here. With PR we have 10/s limit on API calls send to GCE. And we are still rate-limitted. However, according to documentation we are allowed for 20/s: So something either doesn't work or is weird.\nWhat is super interesting from the logs of recent run: It starts to creating routes: After 2 minutes from that, we are hitting \"Rate limit Exceeded\" for the first time: And only after 9 minutes we create the first route ever. The second one is created after 15 minutes, and from that point we create a number of them So it seems that nothing useful is happening for the first 2 minutes, and then between 3m30 and 9m30\nOK - so I think that what is happening is that all controllers are sharing GCE interface (and thuse they have common throttling). So if one controller is generating a lot of API calls, then other controllers may be throttled. has a hypothesis that it may be caused by nodecontroller.\nOne thing my PR didn't address (because it was late): Now we have some obnoxious differences in logging when you go to make a request, because the versus could actually be absorbing a fair amount of ratelimiter.", "commid": "kubernetes_issue_26119", "tokennum": 488}], "negative_passages": []}
{"query_id": "q-en-kubernetes-002b4e03797943125ecc2bf5697fa0fc18e6137434144c1a6bbfcefbb129a789", "query": "opName := op.Name return wait.Poll(operationPollInterval, operationPollTimeoutDuration, func() (bool, error) { start := time.Now() <del> gce.operationPollRateLimiter.Accept() </del> duration := time.Now().Sub(start) if duration > 5*time.Second { glog.Infof(\"pollOperation: waited %v for %v\", duration, opName)", "positive_passages": [{"docid": "doc-en-kubernetes-bf24c8733a67a958496376416be2eb636c6e4bfb94999815173220461c93fd0c", "text": "It could before because of the operation rate limiter and operation polling anyways, but now could be worse.\n- yes I'm aware of that. And probably this is exactly the case here.\nI got fooled by that - I guess we should fix it somehow.\nOne approach to fixing it is a similar approach to the operation polling code, but in the : warn if we ratelimited for more than N seconds (and dump the request or something? not clear how to clarify what we were sending).\nI found something else - Kubelet is also building GCE interface: We have 2000 kubelets, so if all of them send multiple requests to GCE, we may hit limits.\nAny idea in what circumstances Kubelet will contact cloud provider?\nHmm - it seems it contacts GCE exactly once at the beginning. So it doesn't explain much.\nI think it's only here: I've rarely seen GCE ratelimit readonly calls, in practice, and kubelets come up pretty well staggered.\nOK - so with logs that I , it is pretty clear that we are very heavily throttled on GCE api calls. In particular, when I was running 1000-node cluster, I see lines where we were throttle for 1m30. I'm pretty sure it's significantly higher in 2000-node cluster. I'm going to investigate a bit more where all those reuqests come from.\nActually - it seems that we have a pretty big problem here. Basically, Kubelet seems to send a lot of requests to GCE. So to clarify: every time Kubelet is updating NodeStatus (so every 10s by default) it is sending an API call to GCE to get it's not addresses: that means, that if we have 2000 nodes, kubelets generate 200 QPS to GCE (which is significantly more than we can afford) We should think how to solve this issue, but I think the options are: increasing QPS quota or calling GCE only once per X statusUpdates.\nThe second issue is that we are throttled at the controller level too, and this one I'm tryin to understand right now.", "commid": "kubernetes_issue_26119", "tokennum": 457}], "negative_passages": []}
{"query_id": "q-en-kubernetes-002b4e03797943125ecc2bf5697fa0fc18e6137434144c1a6bbfcefbb129a789", "query": "opName := op.Name return wait.Poll(operationPollInterval, operationPollTimeoutDuration, func() (bool, error) { start := time.Now() <del> gce.operationPollRateLimiter.Accept() </del> duration := time.Now().Sub(start) if duration > 5*time.Second { glog.Infof(\"pollOperation: waited %v for %v\", duration, opName)", "positive_passages": [{"docid": "doc-en-kubernetes-b1dad1b374e4c58d925d9fef62d9846d5e0e5eda04aecdd78a124036a36cf31c", "text": "- that said, any rate-limitting on our side, will not solve the kubelet-related problem\nHmm - actually looking into implementation it seems that NodeAddresses are only contacting metadata server, so I'm not longer that convinced...\nAlso, I think that important thing is that a single call to GCE API can translate to multiple api calls to GCE. In particular - CreateRoute translates to: get instance insert route a bunch of getOperation (until this is finished)\nOK - so I think that what is happening here is that since CreateRoute translates to: get instance insert route a bunch of getOperations That means that if we call say 2000 CreateRoute() at the same time, all of them will try to issue: getInstance at the beginning. So we will quickly accumulate 2000 GET requests in the queue. Once they are processed, we generate the \"POST route\" then for any processed. So It's kind of expected what is happening here. So getting back to the Zach`s PR - I think that throttling POST and GET and OPERATION calls separate is kind of good idea in general.\nBut I still don't really understand why do we get \"RateLimitExceeded\". Is that because of Kubelets?\nI think that one problem we have at the RouteController level is that if CreateRoute fails, we simply don't react on it. And we will wait at least 5 minutes before even retrying it. We should add some retries at the route controller level too. I will send out some short PR for it.\nBut I still don't understand why do we get those \"RateLimitExceeded\" error\nOK - so as an update. In GCE, we have a separate rate-limit for number of in-flight CreateRoute call per project. is supposed to address this issue.\nOK - so this one is actually fixed. I mean that it is still long, but currently it's purely blocked on GCE.\nAs a comment - we have an internal bug for it already.", "commid": "kubernetes_issue_26119", "tokennum": 438}], "negative_passages": []}
{"query_id": "q-en-kubernetes-002bc89728cd2e5146319758d63519449dcadeb2768732643dcf899c0c6c6e58", "query": "} if err := proxyHandler.ServeConn(conn); err != nil && !shoulderror { <ins> // If the connection request is closed before the channel is closed // the test will fail with a ServeConn error. Since the test only return // early if expects shouldError=true, the channel is closed at the end of // the test, just before all the deferred connections Close() are executed. </ins> if isClosed() { return }", "positive_passages": [{"docid": "doc-en-kubernetes-631bc5da562ebc33bd49790f3078648639a2126878c5fc7773cd8143bd3bdf27", "text": "TestRoundTripSocks5AndNewConnection Disabled by No response No response No response /sig\nThere are no sig labels on this issue. Please add an appropriate label by using one of the following commands: - Please see the for a listing of the SIGs, working groups, and committees available. <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\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nthere is a race shutting down the socks5 server", "commid": "kubernetes_issue_107766", "tokennum": 198}], "negative_passages": []}
{"query_id": "q-en-kubernetes-003aaec0b8629cfccb6fccb934b32f4853e3fab305e7dd1df0d2647bded7e072", "query": "var podClient *framework.PodClient const ( podCheckInterval     = 1 * time.Second <del> podWaitTimeout       = 3 * time.Minute </del> postStartWaitTimeout = 2 * time.Minute preStopWaitTimeout   = 30 * time.Second ) Context(\"when create a pod with lifecycle hook\", func() { <ins> var targetIP string podHandleHookRequest := &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name: \"pod-handle-http-request\", }, Spec: v1.PodSpec{ Containers: []v1.Container{ { Name:  \"pod-handle-http-request\", Image: \"gcr.io/google_containers/netexec:1.7\", Ports: []v1.ContainerPort{ { ContainerPort: 8080, Protocol:      v1.ProtocolTCP, }, }, }, }, }, } </ins> BeforeEach(func() { podClient = f.PodClient() <ins> By(\"create the container to handle the HTTPGet hook request.\") newPod := podClient.CreateSync(podHandleHookRequest) targetIP = newPod.Status.PodIP </ins> }) <del> Context(\"when it is exec hook\", func() { var file string testPodWithExecHook := func(podWithHook *v1.Pod) { podCheckHook := getExecHookTestPod(\"pod-check-hook\", // Wait until the file is created. []string{\"sh\", \"-c\", fmt.Sprintf(\"while [ ! -e %s ]; do sleep 1; done\", file)}, ) By(\"create the pod with lifecycle hook\") podClient.CreateSync(podWithHook) if podWithHook.Spec.Containers[0].Lifecycle.PostStart != nil { By(\"create the hook check pod\") podClient.Create(podCheckHook) By(\"wait for the hook check pod to success\") podClient.WaitForSuccess(podCheckHook.Name, postStartWaitTimeout) } By(\"delete the pod with lifecycle hook\") podClient.DeleteSync(podWithHook.Name, metav1.NewDeleteOptions(15), framework.DefaultPodDeletionTimeout) if podWithHook.Spec.Containers[0].Lifecycle.PreStop != nil { By(\"create the hook check pod\") podClient.Create(podCheckHook) By(\"wait for the prestop check pod to success\") podClient.WaitForSuccess(podCheckHook.Name, preStopWaitTimeout) } </del> <ins> testPodWithHook := func(podWithHook *v1.Pod) { By(\"create the pod with lifecycle hook\") podClient.CreateSync(podWithHook) if podWithHook.Spec.Containers[0].Lifecycle.PostStart != nil { By(\"check poststart hook\") Eventually(func() error { return podClient.MatchContainerOutput(podHandleHookRequest.Name, podHandleHookRequest.Spec.Containers[0].Name, `GET /echo?msg=poststart`) }, postStartWaitTimeout, podCheckInterval).Should(BeNil()) </ins> } <del> BeforeEach(func() { file = \"/tmp/test-\" + string(uuid.NewUUID()) }) AfterEach(func() { By(\"cleanup the temporary file created in the test.\") cleanupPod := getExecHookTestPod(\"pod-clean-up\", []string{\"rm\", file}) podClient.Create(cleanupPod) podClient.WaitForSuccess(cleanupPod.Name, podWaitTimeout) }) It(\"should execute poststart exec hook properly [Conformance]\", func() { podWithHook := getExecHookTestPod(\"pod-with-poststart-exec-hook\", // Block forever []string{\"tail\", \"-f\", \"/dev/null\"}, ) podWithHook.Spec.Containers[0].Lifecycle = &v1.Lifecycle{ PostStart: &v1.Handler{ Exec: &v1.ExecAction{Command: []string{\"touch\", file}}, }, } testPodWithExecHook(podWithHook) }) It(\"should execute prestop exec hook properly [Conformance]\", func() { podWithHook := getExecHookTestPod(\"pod-with-prestop-exec-hook\", // Block forever []string{\"tail\", \"-f\", \"/dev/null\"}, ) podWithHook.Spec.Containers[0].Lifecycle = &v1.Lifecycle{ PreStop: &v1.Handler{ Exec: &v1.ExecAction{Command: []string{\"touch\", file}}, </del> <ins> By(\"delete the pod with lifecycle hook\") podClient.DeleteSync(podWithHook.Name, metav1.NewDeleteOptions(15), framework.DefaultPodDeletionTimeout) if podWithHook.Spec.Containers[0].Lifecycle.PreStop != nil { By(\"check prestop hook\") Eventually(func() error { return podClient.MatchContainerOutput(podHandleHookRequest.Name, podHandleHookRequest.Spec.Containers[0].Name, `GET /echo?msg=prestop`) }, preStopWaitTimeout, podCheckInterval).Should(BeNil()) } } It(\"should execute poststart exec hook properly [Conformance]\", func() { lifecycle := &v1.Lifecycle{ PostStart: &v1.Handler{ Exec: &v1.ExecAction{ Command: []string{\"sh\", \"-c\", \"curl http://\" + targetIP + \":8080/echo?msg=poststart\"}, </ins> }, <del> } testPodWithExecHook(podWithHook) }) }) Context(\"when it is http hook\", func() { var targetIP string podHandleHookRequest := &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name: \"pod-handle-http-request\", </del> }, <del> Spec: v1.PodSpec{ Containers: []v1.Container{ { Name:  \"pod-handle-http-request\", Image: \"gcr.io/google_containers/netexec:1.7\", Ports: []v1.ContainerPort{ { ContainerPort: 8080, Protocol:      v1.ProtocolTCP, }, }, }, </del> <ins> } podWithHook := getPodWithHook(\"pod-with-poststart-exec-hook\", \"gcr.io/google_containers/hostexec:1.2\", lifecycle) testPodWithHook(podWithHook) }) It(\"should execute prestop exec hook properly [Conformance]\", func() { lifecycle := &v1.Lifecycle{ PreStop: &v1.Handler{ Exec: &v1.ExecAction{ Command: []string{\"sh\", \"-c\", \"curl http://\" + targetIP + \":8080/echo?msg=prestop\"}, </ins> }, }, } <del> BeforeEach(func() { By(\"create the container to handle the HTTPGet hook request.\") newPod := podClient.CreateSync(podHandleHookRequest) targetIP = newPod.Status.PodIP }) testPodWithHttpHook := func(podWithHook *v1.Pod) { By(\"create the pod with lifecycle hook\") podClient.CreateSync(podWithHook) if podWithHook.Spec.Containers[0].Lifecycle.PostStart != nil { By(\"check poststart hook\") Eventually(func() error { return podClient.MatchContainerOutput(podHandleHookRequest.Name, podHandleHookRequest.Spec.Containers[0].Name, `GET /echo?msg=poststart`) }, postStartWaitTimeout, podCheckInterval).Should(BeNil()) } By(\"delete the pod with lifecycle hook\") podClient.DeleteSync(podWithHook.Name, metav1.NewDeleteOptions(15), framework.DefaultPodDeletionTimeout) if podWithHook.Spec.Containers[0].Lifecycle.PreStop != nil { By(\"check prestop hook\") Eventually(func() error { return podClient.MatchContainerOutput(podHandleHookRequest.Name, podHandleHookRequest.Spec.Containers[0].Name, `GET /echo?msg=prestop`) }, preStopWaitTimeout, podCheckInterval).Should(BeNil()) } } It(\"should execute poststart http hook properly [Conformance]\", func() { podWithHook := &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name: \"pod-with-poststart-http-hook\", }, Spec: v1.PodSpec{ Containers: []v1.Container{ { Name:  \"pod-with-poststart-http-hook\", Image: framework.GetPauseImageNameForHostArch(), Lifecycle: &v1.Lifecycle{ PostStart: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path: \"/echo?msg=poststart\", Host: targetIP, Port: intstr.FromInt(8080), }, }, }, }, }, }, } testPodWithHttpHook(podWithHook) }) It(\"should execute prestop http hook properly [Conformance]\", func() { podWithHook := &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name: \"pod-with-prestop-http-hook\", </del> <ins> podWithHook := getPodWithHook(\"pod-with-prestop-exec-hook\", \"gcr.io/google_containers/hostexec:1.2\", lifecycle) testPodWithHook(podWithHook) }) It(\"should execute poststart http hook properly [Conformance]\", func() { lifecycle := &v1.Lifecycle{ PostStart: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path: \"/echo?msg=poststart\", Host: targetIP, Port: intstr.FromInt(8080), </ins> }, <del> Spec: v1.PodSpec{ Containers: []v1.Container{ { Name:  \"pod-with-prestop-http-hook\", Image: framework.GetPauseImageNameForHostArch(), Lifecycle: &v1.Lifecycle{ PreStop: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path: \"/echo?msg=prestop\", Host: targetIP, Port: intstr.FromInt(8080), }, }, }, }, }, </del> <ins> }, } podWithHook := getPodWithHook(\"pod-with-poststart-http-hook\", framework.GetPauseImageNameForHostArch(), lifecycle) testPodWithHook(podWithHook) }) It(\"should execute prestop http hook properly [Conformance]\", func() { lifecycle := &v1.Lifecycle{ PreStop: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path: \"/echo?msg=prestop\", Host: targetIP, Port: intstr.FromInt(8080), </ins> }, <del> } testPodWithHttpHook(podWithHook) }) </del> <ins> }, } podWithHook := getPodWithHook(\"pod-with-prestop-http-hook\", framework.GetPauseImageNameForHostArch(), lifecycle) testPodWithHook(podWithHook) </ins> }) }) }) <del> func getExecHookTestPod(name string, cmd []string) *v1.Pod { </del> <ins> func getPodWithHook(name string, image string, lifecycle *v1.Lifecycle) *v1.Pod { </ins> return &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name: name,", "positive_passages": [{"docid": "doc-en-kubernetes-523d59ec5104a53f44aa3efaa79fa37e525dbabb537793d9e95c31ff14a3e1c1", "text": "The prestop and poststart exec tests volume mount /tmp from the host and attempt to create a file there from inside the pod. This is blocked by selinux. Failure:\nwe need to have a mechanism to say that a test should not be run if selinux is enabled (if legitimately required) or fix each test (where appropriate)", "commid": "kubernetes_issue_42905", "tokennum": 76}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0065dda5385eb3b17e6502fa715d517455f15bfce77f0e78077e4ff98bdab5bf", "query": "clusterAddonLabelKey   = \"k8s-app\" kubeAPIServerLabelName = \"kube-apiserver\" clusterComponentKey    = \"component\" <ins> svcReadyTimeout = 1 * time.Minute </ins> ) var (", "positive_passages": [{"docid": "doc-en-kubernetes-c5b2d72b2e785256d7a2577807fdbd43ef000a4da594f69c949ac55e4186d114", "text": "[x] two weeks soak end date : 18 March 2021 According to this APIsnoop query, there are still some remaining RESOURCENAME endpoints which are untested. with this query you can filter untested endpoints by their category and eligiblity for conformance. e.g below shows a query to find all conformance eligible untested,stable,core endpoints Note: Community feedback for the e2e test has lead to a number of improvements including extending the test coverage to all outstanding endpoints listed above. As each endpoint is tested a &rsquo;watch&rsquo; confirms that the result is valid before testing the next endpoint. readCoreV1NamespacedServiceStatus (get /status) patchCoreV1NamespacedServiceStatus (patch /status) replaceCoreV1NamespacedServiceStatus (update /status) patchCoreV1NamespacedService Create a Service with a static label Patch the Service with a new label and updated data Get the Service to ensure it&rsquo;s patched Upate the Service with a new label and updated data Get the Service to ensure it&rsquo;s updated Delete Namespaced Service via a Collection with a LabelSelector This query by apisnoop shows that all outstanding endpoints as list at the start of this document have been hit by the e2e test. Note that the results do include other service endpoints that have been addressed in other conformance tests. If a test with these calls gets merged, test coverage will go up by 4 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance\nCan you please review the proposed test and advise if we could go ahead with a PR\n/assign\nIt looks like it's patching metadata and spec but not status?\nIssues 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\n/remove-lifecycle stale\nI've been retesting this mock test and apisnoop does log as been hit. From my testing below it looks like the patchStatus is working as expected or have I missed something?", "commid": "kubernetes_issue_94867", "tokennum": 517}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0065dda5385eb3b17e6502fa715d517455f15bfce77f0e78077e4ff98bdab5bf", "query": "clusterAddonLabelKey   = \"k8s-app\" kubeAPIServerLabelName = \"kube-apiserver\" clusterComponentKey    = \"component\" <ins> svcReadyTimeout = 1 * time.Minute </ins> ) var (", "positive_passages": [{"docid": "doc-en-kubernetes-6c98fb90bee2cd0d2fc404edc784deab934fddaa81022ed1883862c51f5dae6d", "text": "Using the following code before the patch request Gives this response Then after running the patch ServiceStatus Then running The response shows the patched changes.\nDuring the Conformance Meeting on 12th of January 2021, reviewed approach with Clayton, and we will start on the test PR this week!\n/reopen\nReopened this issue. <detailsIn response to : /reopen </details\n/triage accepted", "commid": "kubernetes_issue_94867", "tokennum": 79}], "negative_passages": []}
{"query_id": "q-en-kubernetes-00694ccb77f15dae69cc5944b653bca5d74a24bcf871c525f6c314111af6a87d", "query": "_, result.MissingAggregationRuleSelectors = aggregationRuleCovers(existing.GetAggregationRule(), expected.GetAggregationRule()) switch { <ins> case expected.GetAggregationRule() == nil && existing.GetAggregationRule() != nil: // we didn't expect this to be an aggregated role at all, remove the existing aggregation result.Role.SetAggregationRule(nil) result.Operation = ReconcileUpdate </ins> case !removeExtraPermissions && len(result.MissingAggregationRuleSelectors) > 0: // add missing rules in the union case aggregationRule := result.Role.GetAggregationRule()", "positive_passages": [{"docid": "doc-en-kubernetes-cf86a1652325e783afd2e6de68ee19a134c3d5bc67e73b574ad8b67c1852b0fb", "text": "/kind bug What happened: I deployed a fresh custom HA kubernetes v1.10.2 cluster with 3 nodes (all controller and worker currently, more workers planned). I then created a namespace called \"stummi\" and a rolebinding with \"user=stummi clusterrole=admin\" in this namespace. User stummi (successfully authenticated by TLS client certificate) was not able to list pods or anything else in his namespace: While trying to figure things out, I downgraded to v1.8.11 (a version without cluster role aggregation, that worked) and also tried v1.11 alpha2 (which did not work). I never purged my etcd and I sadly do not have logs from before the different versions. Shortly after posting on slack and before writing this ticket, I dumped the cluster roles in question: Note the rules. What you expected to happen: I expected user stummi to be able to do most things in his namespace. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: I posted this problem on slack and helped me and wanted this issue opened. /sig auth The cluster is deployed with ansible and I can give the playbooks when required. Environment: Kubernetes version (use ):Cloud provider or hardware configuration: 3 virtual machines (2 cores, 8GB memory) OS (e.g. from /etc/os-release): Debian Stretch Kernel (e.g. ): Install tools: custom ansible playbooks Others: Please let me know if you need more information. I'm happy to provide everything you need to fix this :)\n/assign", "commid": "kubernetes_issue_63760", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0073702efbb5981682ba3c908601a3ddb5372466bf4d5913e21b59c06db1e6e0", "query": "{utiliptables.TableNAT, KubeNodePortChain}, {utiliptables.TableNAT, KubeLoadBalancerChain}, {utiliptables.TableNAT, KubeMarkMasqChain}, <del> {utiliptables.TableNAT, KubeMarkDropChain}, </del> {utiliptables.TableFilter, KubeForwardChain}, } <ins> var iptablesEnsureChains = []struct { table utiliptables.Table chain utiliptables.Chain }{ {utiliptables.TableNAT, KubeMarkDropChain}, } </ins> var iptablesCleanupChains = []struct { table utiliptables.Table chain utiliptables.Chain", "positive_passages": [{"docid": "doc-en-kubernetes-6cbf7dcb5e6486cb532532a59cda0ac4f93a00ec9c96bc20136b3a20d89cc61b", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: ci-kubernetes-e2e-gci-gce-ipvs Which test(s) are failing: [sig-network] Services should only allow access from service loadbalancer source ranges [Slow] Testgrid link: https://k8s- Reason for failure: Anything else we need to know: The test is failing consistently, however, there is also test that is failing a lot but not always, may it be related?\n/sig-network /area ipvs /cc /help wanted\n/sig network\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/assign\n/remove-triage unresolved\nHi, , turnout this is because mark drop rule in be deleted, I raied a pr to fix this issue, PTAL. : )\n/close as duplicate of\nClosing this issue. <detailsIn response to : /close as duplicate of 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\n/reopen this was affecting ipvs only before , let's keep it open until we verify is not failing anymore\nReopened this issue. <detailsIn response to : /reopen this was affecting ipvs only before , let's keep it open until we verify is not failing anymore 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\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign Ok I tested this out with kind in ipvs-mode with metallb. In iptables mode I had zero failures but ipvs does not pass at all during the timeout window. This is likely due to", "commid": "kubernetes_issue_94356", "tokennum": 488}], "negative_passages": []}
{"query_id": "q-en-kubernetes-00d2dcce31529e985e50075d48baaedcbd37ac6b162b70c0e7d14a7db1ac568c", "query": "continue } // Write the log line into the stream. <del> if err := writer.write(msg); err != nil { </del> <ins> if err := writer.write(msg, isNewLine); err != nil { </ins> if err == errMaximumWrite { klog.V(2).InfoS(\"Finished parsing log file, hit bytes limit\", \"path\", path, \"limit\", opts.bytes) return nil", "positive_passages": [{"docid": "doc-en-kubernetes-1611cacb700fc7bde4bed341ff7dc392aeb6c35e6c0f63ce6a10b84981e8d04a", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Docker has a hardcoded 16K limit on log line length, which splits lines longer than that into multiple messages in the log file. in , however, doesn't account for this when is set to and prints the timestamp in front of every entry in the log file instead of every logical line. This leads to random timestamps appearing in the middle of log lines, potentially breaking the applications that parse these logs. What you expected to happen: inserts timestamps once per logical line, so original log data is preserved. Alternatively, allow API to request the logs in a sane format like JSON, which would allow merging the lines back and combining them with the timestamps more intelligently on the application side. How to reproduce it (as minimally and precisely as possible): Create : apiVersion: v1 kind: Pod metadata: name: log-lines spec: containers: name: main image: busybox command: ['sh', '-c', 'while sleep 1; do echo -n ; for i in $(seq 1 ); do echo -n A; done; echo ; done'] Start the pod with Fetch the logs with , or using the API () Observe random timestamps inserted in the middle of the log lines. Environment: Kubernetes version (use ):\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI will work on it. /sig cli /remove-sig node\nThe logs are being corrupted by the API endpoint in kubelet, so shouldn't it be in scope of SIG node?\nThe log is not corrupted by k8s. The same log could be got using \"docker container logs -t CONTAINERID\" I think you should post your requirement to Docker.", "commid": "kubernetes_issue_77603", "tokennum": 465}], "negative_passages": []}
{"query_id": "q-en-kubernetes-00d2dcce31529e985e50075d48baaedcbd37ac6b162b70c0e7d14a7db1ac568c", "query": "continue } // Write the log line into the stream. <del> if err := writer.write(msg); err != nil { </del> <ins> if err := writer.write(msg, isNewLine); err != nil { </ins> if err == errMaximumWrite { klog.V(2).InfoS(\"Finished parsing log file, hit bytes limit\", \"path\", path, \"limit\", opts.bytes) return nil", "positive_passages": [{"docid": "doc-en-kubernetes-495f248c0af4a1a8db07569505db46eac9f11be4907de183bc6923cd7882b142", "text": "Please refer following code Line 50 ~ 52 if config.Timestamps { logLine = append([]byte(msg.Timestamp.Format(jsonmessage.RFC3339NanoFixed)+\" \"), logLine...) }\nkubelet doesn't rely on Docker when reading logs, it reads the files itself (see the code linked in the issue). I don't think Docker would change the forced line splitting (see for example), so this should be fixed in Kubernetes.\nYour are right and kubelet read log file from host such as /var/log/pods/pods/NAMESPACEPOD-NAMExxx/....(JSON format) I will post a PR for it. /remove-sig cli /sig node\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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 .", "commid": "kubernetes_issue_77603", "tokennum": 539}], "negative_passages": []}
{"query_id": "q-en-kubernetes-00d2dcce31529e985e50075d48baaedcbd37ac6b162b70c0e7d14a7db1ac568c", "query": "continue } // Write the log line into the stream. <del> if err := writer.write(msg); err != nil { </del> <ins> if err := writer.write(msg, isNewLine); err != nil { </ins> if err == errMaximumWrite { klog.V(2).InfoS(\"Finished parsing log file, hit bytes limit\", \"path\", path, \"limit\", opts.bytes) return nil", "positive_passages": [{"docid": "doc-en-kubernetes-2f614c9ad06da31fe9313a5b2eaea6d6901d55cba8508cf5ebe57105d301c4f6", "text": "Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\nStale 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\nI saw the attempt fixing this but it was scary (echo this comment: ). I suggested a way it may be improved. Also the proposed fix didn't introduce any e2e tests to validate that runtime behavior is not changed and runtimes keep the no-newline-on-splitted-log logic. are you or anybody on this thread are still interested to work on this? Please re-open if so. Meanwhile closing this ahead of bot doing it because the inactivity. /close\nClosing this issue. <detailsIn response to : I saw the attempt fixing this but it was scary (echo this comment: ). I suggested a way it may be improved. Also the proposed fix didn't introduce any e2e tests to validate that runtime behavior is not changed and runtimes keep the no-newline-on-splitted-log logic. Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_77603", "tokennum": 493}], "negative_passages": []}
{"query_id": "q-en-kubernetes-00d2dcce31529e985e50075d48baaedcbd37ac6b162b70c0e7d14a7db1ac568c", "query": "continue } // Write the log line into the stream. <del> if err := writer.write(msg); err != nil { </del> <ins> if err := writer.write(msg, isNewLine); err != nil { </ins> if err == errMaximumWrite { klog.V(2).InfoS(\"Finished parsing log file, hit bytes limit\", \"path\", path, \"limit\", opts.bytes) return nil", "positive_passages": [{"docid": "doc-en-kubernetes-2e8714433462894a36e35ec9c24fb7c5a56d0558d2953a09bb86920b184c167e", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nYou can't reopen an issue/PR unless you authored it or you are a collaborator. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/remove-lifecycle rotten /reopen will fix it.\nReopened this issue. <detailsIn response to : /remove-lifecycle rotten /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/triage accepted\nThe Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.", "commid": "kubernetes_issue_77603", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-00d2dcce31529e985e50075d48baaedcbd37ac6b162b70c0e7d14a7db1ac568c", "query": "continue } // Write the log line into the stream. <del> if err := writer.write(msg); err != nil { </del> <ins> if err := writer.write(msg, isNewLine); err != nil { </ins> if err == errMaximumWrite { klog.V(2).InfoS(\"Finished parsing log file, hit bytes limit\", \"path\", path, \"limit\", opts.bytes) return nil", "positive_passages": [{"docid": "doc-en-kubernetes-422d52914e9725e7355cb5e937e13c24e15f273f63951d92fe52d86a167487cb", "text": "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]:\nThe 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]:\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_77603", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-00d2dcce31529e985e50075d48baaedcbd37ac6b162b70c0e7d14a7db1ac568c", "query": "continue } // Write the log line into the stream. <del> if err := writer.write(msg); err != nil { </del> <ins> if err := writer.write(msg, isNewLine); err != nil { </ins> if err == errMaximumWrite { klog.V(2).InfoS(\"Finished parsing log file, hit bytes limit\", \"path\", path, \"limit\", opts.bytes) return nil", "positive_passages": [{"docid": "doc-en-kubernetes-0e28d298340708e57a780633dba41fa2a744d19c9ab3d061a118f6b1e6c3d902", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI received a bug report about this issue. The root cause is that the buffer reads up to a new line. If the line is greater than 4096 bytes and '--timestamps' is turrned on the kubelet will write the timestamp and the partial log line. We will need to refactor the ReadLogs function to allow for a partial line read.", "commid": "kubernetes_issue_77603", "tokennum": 104}], "negative_passages": []}
{"query_id": "q-en-kubernetes-00f13634ae830a01925a78490b7d53a63396d51143ecd591255015150a3dbe2c", "query": "recorder record.EventRecorder } <del> func (irecorder *innerEventRecorder) shouldRecordEvent(object runtime.Object) (*clientv1.ObjectReference, bool) { </del> <ins> func (irecorder *innerEventRecorder) shouldRecordEvent(object runtime.Object) (*v1.ObjectReference, bool) { </ins> if object == nil { return nil, false } <del> if ref, ok := object.(*clientv1.ObjectReference); ok { if !strings.HasPrefix(ref.FieldPath, ImplicitContainerPrefix) { return ref, true } } // just in case we miss a spot, be sure that we still log something </del> if ref, ok := object.(*v1.ObjectReference); ok { if !strings.HasPrefix(ref.FieldPath, ImplicitContainerPrefix) { <del> return events.ToObjectReference(ref), true </del> <ins> return ref, true </ins> } } return nil, false", "positive_passages": [{"docid": "doc-en-kubernetes-b0087f3d33811f5a8bf21a1757c4fff7aaef7add29731940c9c3bd61ec9b29c4", "text": "Is this a BUG REPORT or FEATURE REQUEST?: What happened: Now the and has been consistent in by PR . There is no need to convert v1.ObjectReference to clientv1.ObjectReference in . What you expected to happen: Remove this function and cleanup the codes which call this function. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?:\nThere are no sig labels on this issue. Please by:<br(1) mentioning a sig: <bre.g., for API Machinery<br(2) specifying the label manually: <bre.g., for sig/scalability<br<brNote: method (1) will trigger a notification to the team. You can find the team list and label list\nWill submit the cleanup after PR merged.\n/sig api-machinery\n/sub", "commid": "kubernetes_issue_48747", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-01088ddce912f218dcbcf091f77a80ddf0c6b0f8ae14ba3434a6bb7f818d5397", "query": "Rules:      kubeSchedulerRules, }) <del> externalProvisionerRules := []rbacv1.PolicyRule{ rbacv1helpers.NewRule(\"create\", \"delete\", \"get\", \"list\", \"watch\").Groups(legacyGroup).Resources(\"persistentvolumes\").RuleOrDie(), rbacv1helpers.NewRule(\"get\", \"list\", \"watch\", \"update\", \"patch\").Groups(legacyGroup).Resources(\"persistentvolumeclaims\").RuleOrDie(), rbacv1helpers.NewRule(\"list\", \"watch\").Groups(storageGroup).Resources(\"storageclasses\").RuleOrDie(), rbacv1helpers.NewRule(\"get\", \"list\", \"watch\", \"create\", \"update\", \"patch\").Groups(legacyGroup).Resources(\"events\").RuleOrDie(), rbacv1helpers.NewRule(\"get\", \"list\", \"watch\").Groups(legacyGroup).Resources(\"nodes\").RuleOrDie(), } if utilfeature.DefaultFeatureGate.Enabled(features.CSINodeInfo) { externalProvisionerRules = append(externalProvisionerRules, rbacv1helpers.NewRule(\"get\", \"watch\", \"list\").Groups(\"storage.k8s.io\").Resources(\"csinodes\").RuleOrDie()) } roles = append(roles, rbacv1.ClusterRole{ // a role for the csi external provisioner ObjectMeta: metav1.ObjectMeta{Name: \"system:csi-external-provisioner\"}, Rules:      externalProvisionerRules, }) </del> addClusterRoleLabel(roles) return roles }", "positive_passages": [{"docid": "doc-en-kubernetes-083944d00199b655f25fb35f51e7ea3786d4181f487cac5cdbda9f2140ce4497", "text": "<!-- Please only use this template for submitting enhancement requests --The built-in and cluster roles here are deprecated in 1.13 when this issue was resolved: /sig storage /milestone v1.17 /priorit important-longterm\nYou must be a member of the GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility. <detailsIn response to : <!-- Please only use this template for submitting enhancement requests -- /milestone v1.17 /priorit important-longterm 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\n/cc /priority important-longterm\nIssues 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\n/remove-lifecycle stale /assign\nBug triage for 1.17 here with a gentle reminder that code freeze for this release is on November 14. Is this issue still intended for 1.17?", "commid": "kubernetes_issue_78739", "tokennum": 293}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0132744d9d2e28d96bc6f1c64a6478043b0dd60ad6e5263b52be76874a3e48dc", "query": "func restartKubelet() { kubeletServiceName := findRunningKubletServiceName() <del> stdout, err := exec.Command(\"sudo\", \"systemctl\", \"restart\", kubeletServiceName).CombinedOutput() </del> <ins> // reset the kubelet service start-limit-hit stdout, err := exec.Command(\"sudo\", \"systemctl\", \"reset-failed\", kubeletServiceName).CombinedOutput() framework.ExpectNoError(err, \"Failed to reset kubelet start-limit-hit with systemctl: %v, %v\", err, stdout) stdout, err = exec.Command(\"sudo\", \"systemctl\", \"restart\", kubeletServiceName).CombinedOutput() </ins> framework.ExpectNoError(err, \"Failed to restart kubelet with systemctl: %v, %v\", err, stdout) }", "positive_passages": [{"docid": "doc-en-kubernetes-32f73fe3230f64533d19b392edefbaf0b0e1a8feaecfa7ce5826559c53a1a616", "text": "Which jobs are flaking: ci-kubernetes-node-kubelet-serial-hugepages Which test(s) are flaking: all Testgrid link: https://k8s- Reason for failure:\n/sig node\n/assign /cc\nGitHub didn't allow me to assign the following users: cynepco3hahue. 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 /cc 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\ntestgrid alert:\n/cc\nI started to look into logs and the issue that one of the kubelet restarts fails on: I will try to reproduce the issue locally.\nany news? Have you managed to reproduce the issue locally?\nI already have a fix that is waiting for merge -", "commid": "kubernetes_issue_93323", "tokennum": 227}], "negative_passages": []}
{"query_id": "q-en-kubernetes-01462297c67229b9e5224afcbd2d36e104fbbf4cdd1fbed121bf4baad81637cc", "query": "// We could try a wget the service from the client pod.  But services.sh e2e test covers that pretty well. }) <ins> It(\"should be restarted with a docker exec \"cat /tmp/health\" liveness probe\", func() { runLivenessTest(c, &api.Pod{ ObjectMeta: api.ObjectMeta{ Name:   \"liveness-exec\", Labels: map[string]string{\"test\": \"liveness\"}, }, Spec: api.PodSpec{ Containers: []api.Container{ { Name:    \"liveness\", Image:   \"busybox\", Command: []string{\"/bin/sh\", \"-c\", \"echo ok >/tmp/health; sleep 10; echo fail >/tmp/health; sleep 600\"}, LivenessProbe: &api.Probe{ Handler: api.Handler{ Exec: &api.ExecAction{ Command: []string{\"cat\", \"/tmp/health\"}, }, }, InitialDelaySeconds: 15, }, }, }, }, }) }) It(\"should be restarted with a /healthz http liveness probe\", func() { runLivenessTest(c, &api.Pod{ ObjectMeta: api.ObjectMeta{ Name:   \"liveness-http\", Labels: map[string]string{\"test\": \"liveness\"}, }, Spec: api.PodSpec{ Containers: []api.Container{ { Name:    \"liveness\", Image:   \"kubernetes/liveness\", Command: []string{\"/server\"}, LivenessProbe: &api.Probe{ Handler: api.Handler{ HTTPGet: &api.HTTPGetAction{ Path: \"/healthz\", Port: util.NewIntOrStringFromInt(8080), }, }, InitialDelaySeconds: 15, }, }, }, }, }) }) </ins> })", "positive_passages": [{"docid": "doc-en-kubernetes-563adcd071a3c6fe544aec5f1bf507590a5c621259a5e37f4edab1ba22b77da9", "text": "Park of ginkgo-ization\nPer IRC, is working on this\nPushed an update yesterday to address comments.\nwhat's the status of this? There's an issue open to de-flake this test (), but it's tough to do that if the code is in the middle of being moved to ginkgo.\nThis has been merged.", "commid": "kubernetes_issue_4253", "tokennum": 76}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0147f94634c67fafe3c076ebac216ce5ba6828db21c800f03675623f1b9e843c", "query": "docs/yaml/kubectl/kubectl.yaml docs/yaml/kubectl/kubectl_alpha.yaml docs/yaml/kubectl/kubectl_annotate.yaml <ins> docs/yaml/kubectl/kubectl_api-resources.yaml </ins> docs/yaml/kubectl/kubectl_api-versions.yaml docs/yaml/kubectl/kubectl_apply.yaml docs/yaml/kubectl/kubectl_attach.yaml", "positive_passages": [{"docid": "doc-en-kubernetes-3c17ea4b4f4a9bb23915ee9fbb41703ef0532ac00becc05b8dda4d23a9ea9da2", "text": "As the RBAC role need to be related to resources. I think we could use a command to get the supported resources. ref to\nThis would be cool.\nI thought we a command that listed resources in the discover doc a long time ago.\nis just the versions, but principle is the same. We want to list all the types, their resources, and tie that back to \"explain\".\nWhat's the best way to determine this information currently? I'm having difficulty figuring out the exact set of permissions (and how they would be written in an RBAC role) for any given kubectl command. The documentation for this right now is split across multiple places and certain things are not explained at all. Specifically, it's difficult to determine which \"API verb\" is used for which operations. Take as an example. It's unclear if the way to allow this is to use the \"proxy\" subresource of a pod or service with \"get\"/\"create\"/etc. verbs, or to use the \"proxy\" verb with the resource (pod, service) directly. is a similar case. The almost works for this purpose, but it's still difficult. Operations for a given resource are grouped into categories like write, read, status, and proxy, but these things don't obviously correlate with API verbs. Again, proxy is especially confusing as there is no mention of a proxy \"verb\". The API operations are only shown using their HTTP verbs. One thing that could help on this document would be a section on the right column under \"kubectl command\" that shows exactly the rule needed in an RBAC role to allow this command via kubectl. And even then, that assumes an exact 1-to-1 mapping between API endpoints and kubectl commands, which I doubt is always the case. (For example, port fowarding to a pod seems to require both a GET on the pod resource and a CREATE on a port forward subresource.) There also needs to be better documentation about how this information could have been determined in the first place. I've resorted to manually looking through API requests made with but even then it's difficult to figure out. Amusingly, I was the one who wrote which is referenced in the original issue description (as well as the table explaining verbs in ).", "commid": "kubernetes_issue_42932", "tokennum": 494}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0147f94634c67fafe3c076ebac216ce5ba6828db21c800f03675623f1b9e843c", "query": "docs/yaml/kubectl/kubectl.yaml docs/yaml/kubectl/kubectl_alpha.yaml docs/yaml/kubectl/kubectl_annotate.yaml <ins> docs/yaml/kubectl/kubectl_api-resources.yaml </ins> docs/yaml/kubectl/kubectl_api-versions.yaml docs/yaml/kubectl/kubectl_apply.yaml docs/yaml/kubectl/kubectl_attach.yaml", "positive_passages": [{"docid": "doc-en-kubernetes-20fd632aaf82ba3efee7609ebeda29ca6df3199abf73ef8bcfe417660974a0ce", "text": "tl;dr: It's too difficult right now to go from \"I want a user to be able to run \" to \"here is the RBAC rule to use for that\" for any case where there isn't a specific example shown in the docs.\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nIt seem that relative PR stop updated. If this issue still valuable, i will help fix it\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close", "commid": "kubernetes_issue_42932", "tokennum": 279}], "negative_passages": []}
{"query_id": "q-en-kubernetes-015129c3de70294f19753a1e9095a3d1fa7157ad8cdd220e35645be62976eb4d", "query": "return nil } <del> func (lb *LoadBalancer) DeleteTCPLoadBalancer(name, region string) error { glog.V(4).Infof(\"DeleteTCPLoadBalancer(%v, %v)\", name, region) vip, err := getVipByName(lb.network, name) if err != nil { return err } pool, err := pools.Get(lb.network, vip.PoolID).Extract() if err != nil { return err </del> <ins> func (lb *LoadBalancer) EnsureTCPLoadBalancerDeleted(name, region string) error { glog.V(4).Infof(\"EnsureTCPLoadBalancerDeleted(%v, %v)\", name, region) // TODO(#8352): Because we look up the pool using the VIP object, if the VIP // is already gone we can't attempt to delete the pool. We should instead // continue even if the VIP doesn't exist and attempt to delete the pool by // name. vip, vipErr := getVipByName(lb.network, name) if vipErr == ErrNotFound { return nil } else if vipErr != nil { return vipErr } // It's ok if the pool doesn't exist, as we may still need to delete the vip // (although I don't believe the system should ever be in that state). pool, poolErr := pools.Get(lb.network, vip.PoolID).Extract() if poolErr != nil { detailedErr, ok := poolErr.(*gophercloud.UnexpectedResponseCodeError) if !ok || detailedErr.Actual != http.StatusNotFound { return poolErr } </ins> } <ins> poolExists := (poolErr == nil) </ins> <del> // Have to delete VIP before pool can be deleted err = vips.Delete(lb.network, vip.ID).ExtractErr() if err != nil { </del> <ins> // We have to delete the VIP before the pool can be deleted, so we can't // continue on if this fails. // TODO(#8352): Only do this if the VIP exists once we can delete pools by // name rather than by ID. err := vips.Delete(lb.network, vip.ID).ExtractErr() if err != nil && err != ErrNotFound { </ins> return err } // Ignore errors for everything following here <del> for _, monId := range pool.MonitorIDs { pools.DisassociateMonitor(lb.network, pool.ID, monId) </del> <ins> if poolExists { for _, monId := range pool.MonitorIDs { // TODO(#8352): Delete the monitor, don't just disassociate it. pools.DisassociateMonitor(lb.network, pool.ID, monId) } pools.Delete(lb.network, pool.ID) </ins> } <del> pools.Delete(lb.network, pool.ID) </del> return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-9fca6378f8b8df6d20b226b62d39deddc0dd6ba6166f0f70fb99239f64c63f5d", "text": "All of our external load balancer tests failed for the better part of a day due to the GCE project that our tests run in hitting its quota for number of target pools. While the target pools have been deleted, the fact that we hit our quota indicates that there must be a leak somewhere, and we need to plug it.\nFor reference, the previous issue was\nCould the leakage be related to ? The quota exhaustion occurred about 22 hrs after that.\nI'd guess that this is due to GetTCPLoadBalancer returning that the load balancer doesn't exist if the forwarding rule is gone, ignoring the target pool, while the service controller considers its deleting done if the cloud provider says that the load balancer doesn't exist. I that logic to the cloud provider because the other implementations of DeleteTCPLoadBalancer weren't/won't be idempotent in the sense of returning ok if the LB doesn't exist. To fix it, we'll either need to make sure all Delete implementations are idempotent and remove the Get call in the controller, or add a method along the lines of IsTCPLoadBalancerDeleted to ask the cloud provider whether all pieces of it have been completely cleaned up. We can't make GetTCPLoadBalancer check that because it's relied on to tell us whether or not the balancer is fully created.\nCopying over my commentary from on why the GKE e2e tests are leaking so many forwarding rules and target pools vs the GCE tests:\nIs there a way for the services test to wait for the service controller to clean up the external resources before finishing (without just doing a sleep)?\nNot without polling GCE directly for whether the resources still exist, although that may be worth it as a workaround. What would be perfect is that clean-up-all-cloud-provider-resources API method that we talked about a couple months ago.\nCan we not perhaps use GCE namespaces or projects as a cheap way of getting this here?\nI don't believe so. We can't use projects due to the fact that projects can't be programatically created (they're intended to be long-lived). I'm not aware of anything along the lines of a GCE namespace other than networks, which won't work because target pools and forwarding rules unfortunately don't seem to be scoped to networks.", "commid": "kubernetes_issue_7753", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-015129c3de70294f19753a1e9095a3d1fa7157ad8cdd220e35645be62976eb4d", "query": "return nil } <del> func (lb *LoadBalancer) DeleteTCPLoadBalancer(name, region string) error { glog.V(4).Infof(\"DeleteTCPLoadBalancer(%v, %v)\", name, region) vip, err := getVipByName(lb.network, name) if err != nil { return err } pool, err := pools.Get(lb.network, vip.PoolID).Extract() if err != nil { return err </del> <ins> func (lb *LoadBalancer) EnsureTCPLoadBalancerDeleted(name, region string) error { glog.V(4).Infof(\"EnsureTCPLoadBalancerDeleted(%v, %v)\", name, region) // TODO(#8352): Because we look up the pool using the VIP object, if the VIP // is already gone we can't attempt to delete the pool. We should instead // continue even if the VIP doesn't exist and attempt to delete the pool by // name. vip, vipErr := getVipByName(lb.network, name) if vipErr == ErrNotFound { return nil } else if vipErr != nil { return vipErr } // It's ok if the pool doesn't exist, as we may still need to delete the vip // (although I don't believe the system should ever be in that state). pool, poolErr := pools.Get(lb.network, vip.PoolID).Extract() if poolErr != nil { detailedErr, ok := poolErr.(*gophercloud.UnexpectedResponseCodeError) if !ok || detailedErr.Actual != http.StatusNotFound { return poolErr } </ins> } <ins> poolExists := (poolErr == nil) </ins> <del> // Have to delete VIP before pool can be deleted err = vips.Delete(lb.network, vip.ID).ExtractErr() if err != nil { </del> <ins> // We have to delete the VIP before the pool can be deleted, so we can't // continue on if this fails. // TODO(#8352): Only do this if the VIP exists once we can delete pools by // name rather than by ID. err := vips.Delete(lb.network, vip.ID).ExtractErr() if err != nil && err != ErrNotFound { </ins> return err } // Ignore errors for everything following here <del> for _, monId := range pool.MonitorIDs { pools.DisassociateMonitor(lb.network, pool.ID, monId) </del> <ins> if poolExists { for _, monId := range pool.MonitorIDs { // TODO(#8352): Delete the monitor, don't just disassociate it. pools.DisassociateMonitor(lb.network, pool.ID, monId) } pools.Delete(lb.network, pool.ID) </ins> } <del> pools.Delete(lb.network, pool.ID) </del> return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-d79b213781c20847fbb47c058c0afaba60ed2f1d9f5b51e77a0a4cda944c52e0", "text": "The target pool leak in the code might be fixed, but the forwarding rule + target pool leak from deleting GKE clusters too quickly is certainly still happening. Reopening for the sake of that half of the issue.\nCan we just add a short sleep to jenkins after the last test has run before it deletes anything?\nYes, you could add a sleep to Ginkgo's AfterEachSuite(): But I'd be concerned about what the upper bound on the sleep period is. Can we get the tests and code in sync with a 1 minute latency here? (e.g. if the controller garbage collects every 60 seconds, then the test only needs to sleep for 60 sec?) And add a BEEG comment to the test's sleep config noting that increasing the sleep time will not improve things, otherwise I'm pretty sure that someone noting flakes in this test in future will think \"maybe I should just increase the sleep period a little bit.\"\nActually, thinking about this a little more, it would be better to put the \"sleep\" logic in the k8s master teardown procedure (i.e. not in the e2e tests or in Jenkins), because otherwise users are going to run into the same resource leakage problems as we are. So master deletion blocks on cleanup of backend cloud resources.\nThere's no way to block master deletion from the master itself. The test framework (or user) just pulls the rug out from underneath the master. See\nRobby's right -- is the real solution to this, but until we have that the best we can do is to have the wait happen elsewhere. The options seem to be: GKE itself Ginkgo's post-testing logic Jenkins' teardown logic I don't like putting it in GKE, because arbitrarily slowing down our API makes for a poor experience for the majority of people that don't still have resources being deleted. I'm not eager to put it in Gingko either, since won't that sleep also take effect whenever anyone runs an e2e test locally against a dev cluster? Putting it in the Jenkins logic makes the most sense to me. I'll send a PR and cc you.\nWe may also want to change the kube-down logic to bring down the master and then nodes in parallel to both speed it up and more closely resemble GKE's teardown logic.\nI've deleted the old forwarding rules and target pools from the project.", "commid": "kubernetes_issue_7753", "tokennum": 530}], "negative_passages": []}
{"query_id": "q-en-kubernetes-015129c3de70294f19753a1e9095a3d1fa7157ad8cdd220e35645be62976eb4d", "query": "return nil } <del> func (lb *LoadBalancer) DeleteTCPLoadBalancer(name, region string) error { glog.V(4).Infof(\"DeleteTCPLoadBalancer(%v, %v)\", name, region) vip, err := getVipByName(lb.network, name) if err != nil { return err } pool, err := pools.Get(lb.network, vip.PoolID).Extract() if err != nil { return err </del> <ins> func (lb *LoadBalancer) EnsureTCPLoadBalancerDeleted(name, region string) error { glog.V(4).Infof(\"EnsureTCPLoadBalancerDeleted(%v, %v)\", name, region) // TODO(#8352): Because we look up the pool using the VIP object, if the VIP // is already gone we can't attempt to delete the pool. We should instead // continue even if the VIP doesn't exist and attempt to delete the pool by // name. vip, vipErr := getVipByName(lb.network, name) if vipErr == ErrNotFound { return nil } else if vipErr != nil { return vipErr } // It's ok if the pool doesn't exist, as we may still need to delete the vip // (although I don't believe the system should ever be in that state). pool, poolErr := pools.Get(lb.network, vip.PoolID).Extract() if poolErr != nil { detailedErr, ok := poolErr.(*gophercloud.UnexpectedResponseCodeError) if !ok || detailedErr.Actual != http.StatusNotFound { return poolErr } </ins> } <ins> poolExists := (poolErr == nil) </ins> <del> // Have to delete VIP before pool can be deleted err = vips.Delete(lb.network, vip.ID).ExtractErr() if err != nil { </del> <ins> // We have to delete the VIP before the pool can be deleted, so we can't // continue on if this fails. // TODO(#8352): Only do this if the VIP exists once we can delete pools by // name rather than by ID. err := vips.Delete(lb.network, vip.ID).ExtractErr() if err != nil && err != ErrNotFound { </ins> return err } // Ignore errors for everything following here <del> for _, monId := range pool.MonitorIDs { pools.DisassociateMonitor(lb.network, pool.ID, monId) </del> <ins> if poolExists { for _, monId := range pool.MonitorIDs { // TODO(#8352): Delete the monitor, don't just disassociate it. pools.DisassociateMonitor(lb.network, pool.ID, monId) } pools.Delete(lb.network, pool.ID) </ins> } <del> pools.Delete(lb.network, pool.ID) </del> return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-6b81898435dc239c0c98669b4836ce5b1423be788127f142aa9eb15c198137cf", "text": "I'll periodically check to see whether anything is leaked after this point. I apologize if the deletions affected any running tests - everything looked to only be from GKE and parallel e2e runs.", "commid": "kubernetes_issue_7753", "tokennum": 42}], "negative_passages": []}
{"query_id": "q-en-kubernetes-018ecba037828f5f59349091e3f0f6427d58a2f18f64e7a933c38b6586b32e59", "query": "cgroupRoots = append(cgroupRoots, cm.NodeAllocatableRoot(s.CgroupRoot, s.CgroupDriver)) kubeletCgroup, err := cm.GetKubeletContainer(s.KubeletCgroups) if err != nil { <del> return fmt.Errorf(\"failed to get the kubelet's cgroup: %v\", err) } if kubeletCgroup != \"\" { </del> <ins> klog.Warningf(\"failed to get the kubelet's cgroup: %v.  Kubelet system container metrics may be missing.\", err) } else if kubeletCgroup != \"\" { </ins> cgroupRoots = append(cgroupRoots, kubeletCgroup) } runtimeCgroup, err := cm.GetRuntimeContainer(s.ContainerRuntime, s.RuntimeCgroups) if err != nil { <del> return fmt.Errorf(\"failed to get the container runtime's cgroup: %v\", err) } if runtimeCgroup != \"\" { </del> <ins> klog.Warningf(\"failed to get the container runtime's cgroup: %v. Runtime system container metrics may be missing.\", err) } else if runtimeCgroup != \"\" { </ins> // RuntimeCgroups is optional, so ignore if it isn't specified cgroupRoots = append(cgroupRoots, runtimeCgroup) }", "positive_passages": [{"docid": "doc-en-kubernetes-ba159de838e276a42915cbe831ad277f6b9150cbf7cfdd40b9245b21c2eb7560", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: kubelet terminated unexpectedly during hack/local-up-cluster kubelet log as a result apiserver cannot find the node to schedule pods What you expected to happen: kubelet runs successfully and hack/local-up-cluster creates a single node cluster How to reproduce it (as minimally and precisely as possible): run hack/local-up-cluster from HEAD Anything else we need to know?: additional cgroups check seemed to be introduced in ; hack/local-up-cluster works when I check out the parent commit have CI for hack/local-up-cluster and , so I'm not sure if it's an error on my side. It would be greatly appreciated if someone could explain it to me Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Debian GNU/Linux Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others: /sig node cc\nThanks for raising such a detailed issue! cc any thoughts here? Confusingly, I think the kubelet has been assigned a different cgroup for memory and for cpu... however the fact that its using makes me think the user is relying on system defaults. out of curiosity, have you made any mods to how your system assigns cgroups?\nIt sounds like we might want to handle the error more gracefully. If we can't get the kubelet's cgroup, we should fall back to collecting metrics from all cgroups.\ncollecting metrics from all the cgroups on the system? Any concerns about how many cgroups there could be? Also, or any interest in implementing this fix (assuming we go with the fallback behavior)? If not, I can try.\nthanks for looking into this! Sorry I'm not familiar with cgroups. I'm don't know any modification to my system assigns cgroups in particular\nI can put out a PR this week\nxref\nThanks!", "commid": "kubernetes_issue_78950", "tokennum": 487}], "negative_passages": []}
{"query_id": "q-en-kubernetes-01b5e93136c029e7016d91bdfac2407e8944d0ee4f8d7f228a65e64e5b94c62d", "query": "// CreateAdapter creates Custom Metrics - Stackdriver adapter // adapterDeploymentFile should be a filename for adapter deployment located in StagingDeploymentLocation <del> func CreateAdapter(namespace, adapterDeploymentFile string) error { </del> <ins> func CreateAdapter(adapterDeploymentFile string) error { </ins> // A workaround to make the work on GKE. GKE doesn't normally allow to create cluster roles, // which the adapter deployment does. The solution is to create cluster role binding for // cluster-admin role and currently used service account. <del> err := createClusterAdminBinding(namespace) </del> <ins> err := createClusterAdminBinding() </ins> if err != nil { return err }", "positive_passages": [{"docid": "doc-en-kubernetes-cecee0a132f84dbf6d5783d328e94b49c8666ebba8eef4ded1687e53b0451e97", "text": "/kind failing-test <!-- If this is a flake, please add: /kind flake --/sig autoscaling Looks like it just started happening today (@ 2020-09-15 03:54:19 +0000 UTC) !\ncc the namespace from the provided object \"kube-system\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=kube-system' to perform this operation. the namespace from the provided object \"custom-metrics\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=custom-metrics' to perform this operation. the namespace from the provided object \"custom-metrics\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=custom-metrics' to perform this operation.\nrelated fix:\nNo I don't think that's the fix for this (that is just a little cleanup). Actually I think we have to delete namespace parameter in line : Because before , the will have no actually effect. But now with the change of , it will have namespace : at the end of the command. But the namespace in yaml file is which is different from . We should not have parameter when applying from file because this test didn't have before, right? Related PR:\n/assign", "commid": "kubernetes_issue_94809", "tokennum": 318}], "negative_passages": []}
{"query_id": "q-en-kubernetes-021f53738c2b4ca56970222e0a3c72d68689504e7dbac9188a359ffba5b32a2b", "query": "} t.Run(fmt.Sprintf(\"feature enabled=%v, old pod %v, new pod %v\", enabled, oldPodInfo.description, newPodInfo.description), func(t *testing.T) { <del> defer featuregatetesting.SetFeatureGateDuringTest(t, utilfeature.DefaultFeatureGate, features.VolumeSubpathEnvExpansion, enabled)() </del> var oldPodSpec *api.PodSpec if oldPod != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-a166ddd65322b2b4c2d8cbe35891249f4d033568413f3b77fc1f46ee1d1ee8b8", "text": "/kind cleanup /sig storage /sig node Description: Feature gate VolumeSubpathEnvExpansion was GA in 1.17 and is marked for removal in 1.19 Related Issues: GA Release:\n/assign\n/cc", "commid": "kubernetes_issue_89519", "tokennum": 48}], "negative_passages": []}
{"query_id": "q-en-kubernetes-023082f579d724dd4f119f8fec2a16b46b30dc5eba6bf7fc3318010d37d1c220", "query": "defer featuregatetesting.SetFeatureGateDuringTest(b, utilfeature.DefaultFeatureGate, feature, flag)() } dataItems.DataItems = append(dataItems.DataItems, runWorkload(b, tc, w)...) <ins> // Reset metrics to prevent metrics generated in current workload gets // carried over to the next workload. legacyregistry.Reset() </ins> }) } })", "positive_passages": [{"docid": "doc-en-kubernetes-43f40e78041c5b4f7b71fe448bfb25306103aa8e8278b5a81de2f92cd8b688c4", "text": "In the new scheduler performance testing framework, (bool) is provided to benchmark performance of pods created in an \"operator\": (L11 below) However, the initialized Pods created in L5~L7 seem to be also benchmarked, although it doesn't specify . (please see the reproduce steps below). I think it's b/c once scheduler starts, the associated Prometheus artifacts are also up, and it's a single in-memory datastore. So no matter we start to collect the metric in which step, the prometheus data is already up-to-date. In the above workload config, the final data have benchmarked 1500 pods instead of 1000 pods. I guess it won't work either if running in the pod initialization step or not. Unless we manage a breakpoint at the end of each step, and calculate delta histogram for the step that specifies . Pods created in step without are not benchmarked. Apply the following diff: And then run: You will get an output sth. like: /sig scheduling\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nCould you please help confirm if it's an issue?\ncc\nUnfortunately, does not apply for metrics gathered from . As you mentioned. The default gatherer collects all metrics produced by the scheduler. It's the scheduler itself who knows pod specs and would have to decide which pods will get ignored when updating metrics. The question is if computing metrics for a subset of pods processed by the scheduler is a valid use case.\nThis is probably what we want. Is something like that possible ?\nI think being able to absolutely ignore certain pods for metrics is an overkill.\nThe use case is to ignore the pods created in steps that don't specify , so as to collect the Pod metrics create at particular step(s) (). Otherwise, the semantics of option is quite misleading. Nope, that's not the intention. We don't need to target certain pods, like using label selector or whatever. Just as I mentioned, measure pods created at particular steps.", "commid": "kubernetes_issue_99218", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-023082f579d724dd4f119f8fec2a16b46b30dc5eba6bf7fc3318010d37d1c220", "query": "defer featuregatetesting.SetFeatureGateDuringTest(b, utilfeature.DefaultFeatureGate, feature, flag)() } dataItems.DataItems = append(dataItems.DataItems, runWorkload(b, tc, w)...) <ins> // Reset metrics to prevent metrics generated in current workload gets // carried over to the next workload. legacyregistry.Reset() </ins> }) } })", "positive_passages": [{"docid": "doc-en-kubernetes-a8b513dba6e655a29138693e1746ea6f16e628420cb4b4aca138e84f0ed453fc", "text": "I would do something like the following: if a step has collectMetrics:false, we wait for them to finish scheduling, and then we take a snapshot of the histogram. Then for the next step that has collectMetrics:true, we take the diff with the latest snapshot to report the results. This might not be perfect, as we don't control if the metrics have finished syncing when we take the snapshot. But I think that's fine. Would doing this be possible? Now, if we have steps that run in parallel, one with collectMetrics:false and another with collectMetrics:true, then this doesn't work. Note that I don't know the details of how the gatherer works.\nThat adheres to what I have in my mind - we can only manage this on client side. I think it's fine. As we are already fetching the \"snapshot\" when pods get scheduled when equals true. True. An alternative is to design the case to be like: the step with to employ Pods that are all unschedulable, and then specify a custom metric \"schedulere2eschedulingdurationseconds[result=\"unschedulable\"]\" to target a particular histogram instead of all histograms (default option) inside a histogramVec. Note this can only be possible when and some subsequent changes get in place.\nWe might just call Histogram.Clear() method which will clear what has been collected so far at the end of phase: Assuming individual phases have no pods in common and each phase can clear metrics without affecting other phases. Though, as said, it will work only for serial case.\nWDYT\nI'm afraid doesn't work. That was my initial thought as well, but no luck. I guess it's b/c, theoretically, we cannot reset a metric on the server side - Promoetheus' model doesn't support this. But let me know if I miss anything.\nThe performance tests assume all the metrics all gathered and accessed in the same binary. As long as that's the case, works.", "commid": "kubernetes_issue_99218", "tokennum": 457}], "negative_passages": []}
{"query_id": "q-en-kubernetes-023082f579d724dd4f119f8fec2a16b46b30dc5eba6bf7fc3318010d37d1c220", "query": "defer featuregatetesting.SetFeatureGateDuringTest(b, utilfeature.DefaultFeatureGate, feature, flag)() } dataItems.DataItems = append(dataItems.DataItems, runWorkload(b, tc, w)...) <ins> // Reset metrics to prevent metrics generated in current workload gets // carried over to the next workload. legacyregistry.Reset() </ins> }) } })", "positive_passages": [{"docid": "doc-en-kubernetes-c977cd9286b4a197ec98b02fe65342de07359c1835b69599916b95554e8a5e53", "text": "We already call in the code:\nThat was my understanding as well, but no luck :( Here is a diff to call in case when \"concreteOp.CollectMetrics\" is false: <details<summaryDiff:</summary<p</p</detailsAnd below is the output - it's still 1500 (500 init pods plus 1000 measured pods) instead of 1000 being benchmarked: <details<summaryOutput:</summary<p</p</details\nAlso, if you run the tests and together, the result proves doesn't work as expected:\nBut I do find a way to fix this: .", "commid": "kubernetes_issue_99218", "tokennum": 136}], "negative_passages": []}
{"query_id": "q-en-kubernetes-02369f5455d315618e0fe3a5d64d150795609f5590ddf5c6cca8520c03a0b991", "query": "\"k8s.io/apimachinery/pkg/util/wait\" utilfeature \"k8s.io/apiserver/pkg/util/feature\" \"k8s.io/client-go/dynamic\" <ins> \"k8s.io/client-go/informers\" </ins> clientset \"k8s.io/client-go/kubernetes\" <ins> restclient \"k8s.io/client-go/rest\" </ins> featuregatetesting \"k8s.io/component-base/featuregate/testing\" apiservertesting \"k8s.io/kubernetes/cmd/kube-apiserver/app/testing\" podutil \"k8s.io/kubernetes/pkg/api/v1/pod\" <ins> \"k8s.io/kubernetes/pkg/controller/statefulset\" </ins> \"k8s.io/kubernetes/pkg/features\" \"k8s.io/kubernetes/test/integration/framework\" )", "positive_passages": [{"docid": "doc-en-kubernetes-0cad02d163e61aff3cc2c1257b68701a42fb1145e0b51f6816fd9a85adca78e6", "text": "I create a ResourceQuota with two pods limit in my namespace. Then, I create a statefuleSet with 3 replicas. As expected, two pods are created successfully, and the third pod failed to create. But, the ReadyReplicas is not 2 ,but 1. The ReadyReplicas is correct 1Create a ResourceQuota with two pods limit in a new namespace. 2Create a statefulSet with 3 replicas 3Check if the ReadyReplicas of statefulSet matchs the number of stateful running pods. 1According to the logic of the statefulSet controller, new pod created in current sync is not be immediately counted into the ReadyReplicas. 2Failure to create pod will cause to return error, then skip updating status. <details</details<details</details<detailskind v1.23.3 </details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig apps\n/assign", "commid": "kubernetes_issue_108837", "tokennum": 302}], "negative_passages": []}
{"query_id": "q-en-kubernetes-025ea28fea33d5cfe8b370def88157996e58408a512ecee36a6bf0848e622c0d", "query": "type NodeClient interface { // NodePrepareResources prepares several ResourceClaims // for use on the node. If an error is returned, the <del> // response is ignored. Failures for individidual claims </del> <ins> // response is ignored. Failures for individual claims </ins> // can be reported inside NodePrepareResourcesResponse. NodePrepareResources(ctx context.Context, in *NodePrepareResourcesRequest, opts ...grpc.CallOption) (*NodePrepareResourcesResponse, error) // NodeUnprepareResources is the opposite of NodePrepareResources.", "positive_passages": [{"docid": "doc-en-kubernetes-e8eec0a3f7a81297ed919db6952e73e9801661fbfe386a524b19b8189beefe88", "text": "When ResourceClaimParameters or ResourceClassParameters fail validation in resource driver during PodSchedulingContext sync loop, the error is visible only in the events of the PodSchedulingContext. The error should be visible on the object that fails validation as well, ResourceClaim or ResourceClass respectively. Creating ResourceClaim with unsupported parameters' values or unsupported No response <details</details<details</details<details</details<details</details<details</details<details</details\n/assign\n/sig node\n/triage accepted\nKEP:", "commid": "kubernetes_issue_121063", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-02825031b6134f7b312b9f4eff9efb9653395814d9bb43e29bbaf3a50c7566ef", "query": "priorityPairs = append(priorityPairs, priorityPair{name: priorityName, value: priorityVal}) _, err := cs.SchedulingV1().PriorityClasses().Create(context.TODO(), &schedulingv1.PriorityClass{ObjectMeta: metav1.ObjectMeta{Name: priorityName}, Value: priorityVal}, metav1.CreateOptions{}) if err != nil { <del> framework.Logf(\"Failed to create priority '%v/%v': %v\", priorityName, priorityVal, err) framework.Logf(\"Reason: %v. Msg: %v\", apierrors.ReasonForError(err), err) </del> <ins> framework.Logf(\"Failed to create priority '%v/%v'. Reason: %v. Msg: %v\", priorityName, priorityVal, apierrors.ReasonForError(err), err) </ins> } framework.ExpectEqual(err == nil || apierrors.IsAlreadyExists(err), true) }", "positive_passages": [{"docid": "doc-en-kubernetes-3bda2fba5ce2ad90b89601bf2aa62ec37353e4edef7a62972ac2a85cc1aff832", "text": "The following PriorityClass endpoints was Promoted it 1.14 without Conformance tests, and remain untested: replace-, read-, patch-, list-, delete-collection- SchedulingV1PriorityClass According to this APIsnoop query, there are still some remaining PriorityClass endpoints which are untested. with this query you can filter untested endpoints by their category and eligiblity for conformance. e.g below shows a query to find all conformance eligible untested,stable,core endpoints ! createSchedulingV1PriorityClass deleteSchedulingV1PriorityClass Promoted to Conformance 1.19 with /sig testing /sig architecture /area conformance\nIs the ultimiate goal to use conformance tests to explicitly issue all CRUD requests against PriorityClass? And, is equivalent to \"update PriorityClass\"?\nall APIs must have Conformance tests unless they are not eligible for Conformance due to the There is other APIGroups that have both Replace and Update as endpoints. That is the prerogative of the SIG to decide.\ncan you please point us to similar conformance tests used for core objects such as pods and nodes?\nThis is a life cycle test for Create, List, Update, Patch, DeleteCollection More can be found in the test/e2e folder. Also look for examples on the Conformance at previously Promoted Conformance test Reach out if we can help with more information on our approach to Conformance testing.\nI remembered about this PR. Last week a few lines of code was to cover the last of the \"Lease\" endpoint group for conformance. The one file contain the Conformance tests for the complete life cycle of Lease endpoints.\n/assign I will work on it.\n/reopen Will monitor in test grid to move to Conformance after 2 weeks soak.\nReopened this issue. <detailsIn response to : /reopen Will monitor in test grid to move to Conformance after 2 weeks soak. </details\n/triage accepted", "commid": "kubernetes_issue_94954", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-02a41c9a107426f683a4fa1f4e8bde09e41433d97adbefe6d307c5b958254cd3", "query": "}) }) <del> // TODO: Get rid of [DisabledForLargeClusters] tag when issue #56138 is fixed. var _ = SIGDescribe(\"ESIPP [Slow] [DisabledForLargeClusters]\", func() { </del> <ins> var _ = SIGDescribe(\"ESIPP [Slow]\", func() { </ins> f := framework.NewDefaultFramework(\"esipp\") var loadBalancerCreateTimeout time.Duration", "positive_passages": [{"docid": "doc-en-kubernetes-23d2f241356f8f089aacd04cb02b22714ea2023d38ddcb3dae2268a8e3824c6f", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug This is a followup from filed separately now that we're not tracking this as part of 1.9 release. The tests have been disabled with [DisabledForLargeClusters] tag for now, and this fact will be mentioned in the scalability validation report for v1.9. This issue tracks fixing the test so the tag can be removed and the test ran again in the large cluster. /assign /kind e2e-test-failure\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIs this e2e test still broken?\nSorry for the confusion here. Currently this e2e test is disabled on extra large cluster due to some scalability issues with the load balancer related components. At the moment the issues haven't been completely resolved yet.\nok, adding priority so that I know it's not a 1.13 blocker. /priority important-longterm\ncc - this is why the relevant tests for are not part of the e2e suite.\nThis issue is still valid --- some action items on top of my head: Figure out a plan to make service controller properly handle operations in parallel. Check on the status for cloud providers (especially GCP, which the test ran against) on handling large number of nodes as LB backends. /remove-triage unresolved\nIssues 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 .", "commid": "kubernetes_issue_56138", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-02a41c9a107426f683a4fa1f4e8bde09e41433d97adbefe6d307c5b958254cd3", "query": "}) }) <del> // TODO: Get rid of [DisabledForLargeClusters] tag when issue #56138 is fixed. var _ = SIGDescribe(\"ESIPP [Slow] [DisabledForLargeClusters]\", func() { </del> <ins> var _ = SIGDescribe(\"ESIPP [Slow]\", func() { </ins> f := framework.NewDefaultFramework(\"esipp\") var loadBalancerCreateTimeout time.Duration", "positive_passages": [{"docid": "doc-en-kubernetes-82e0e423f6c651003322d5e3ca8baa34b91f0522dd0c015fbde1e81f949704e6", "text": "/lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten /lifecycle frozen\n/reopen Reopening as is being reverted in\nReopened this issue. <detailsIn response to : /reopen Reopening as is being reverted in 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\nthese tests are flaking in xref\ncc since these were enabled by\nYeah - though these failures doesn't seem to be scale related, they seem to be test related to me. This basically means nodes without public ips: It's pretty much the same thing as (just for a different test). should be addressing these kinds of errors. [Not a release blocker for sure]\nBTW - has been opened directly for this one.\n... so since is closed, Can we close this and re-enable for large clusters ? (i.e. remove the Tag in that disables this test) ? I'm not up to speed on the history but 2 related notes I came across digging into related test today... 's a couple of TODOs in the code referencing this specific issue, but your above direct issue is now closed, so we can close this as well right?... And if so, we can remove the TODO on the test... -enabling the test ... not sure wether the timing is good right now (given that is open right now , which sparked my stumbling upon this issue :))\nWe tried to enable all of them and that caused us a bunch of issues and those had to be reverted: A couple tests were enabled later in: and those seem fine. The remaining (mostly session-affinity ones) had some issue, which so far we didn't have time to debug and I haven't heard a good explanation why those were failing. It's possible that they were improved with , but I doubt those would really cause the failures we've seen in the past. So until this is debugged (or at least understood) I'm reluctant to enabling them.", "commid": "kubernetes_issue_56138", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-02e194168c141f899b758863577dd7012f38c2b46ede0453977acdcca44ae845", "query": "proxy_cpu=${KUBEMARK_HOLLOW_PROXY_MILLICPU:-$proxy_cpu} proxy_mem_per_node=${KUBEMARK_HOLLOW_PROXY_MEM_PER_NODE_KB:-50} proxy_mem=$((100 * 1024 + proxy_mem_per_node*NUM_NODES)) <ins> hollow_kubelet_params=$(eval \"for param in ${HOLLOW_KUBELET_TEST_ARGS:-}; do echo -n \"$param\",; done\") hollow_kubelet_params=${hollow_kubelet_params%?} hollow_proxy_params=$(eval \"for param in ${HOLLOW_PROXY_TEST_ARGS:-}; do echo -n \"$param\",; done\") hollow_proxy_params=${hollow_proxy_params%?} </ins> sed -i'' -e \"s@{{hollow_kubelet_millicpu}}@${KUBEMARK_HOLLOW_KUBELET_MILLICPU:-40}@g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" sed -i'' -e \"s@{{hollow_kubelet_mem_Ki}}@${KUBEMARK_HOLLOW_KUBELET_MEM_KB:-$((100*1024))}@g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\"", "positive_passages": [{"docid": "doc-en-kubernetes-d99484417892d904a3f5edbb73fa06d2de654c460b279ad73f511e028afa6a6f", "text": "There are CVEs happening in different images - we already migrated Kubmeark from busybox in , but we should go one step further and migrate the base image to distroless. There are some things that would need to be changed mentioned here: /sig scalability\nCan I work on this? /assign\n/remove-help\n- sure that would be great.\nHi based on the discussion in , the kubemark image has dependency on and maybe more other utilities. So it seems impossible to migrate the base image to distroless? Or do we need something like debian-hyperkube-base?\nThe mount one we may get rid of - basically we should be able to switch to FakeMounter:", "commid": "kubernetes_issue_84284", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-02ec77d18505e4bc131b02e15b0a3694e5580f01d74e11d8db1e42d4a27f85eb", "query": "if len(o.FilenameOptions.Filenames) != 1 { return cmdutil.UsageErrorf(cmd, \"--raw can only use a single local file or stdin\") } <del> if strings.HasPrefix(o.FilenameOptions.Filenames[0], \"http\") { </del> <ins> if strings.Index(o.FilenameOptions.Filenames[0], \"http://\") == 0 || strings.Index(o.FilenameOptions.Filenames[0], \"https://\") == 0 { </ins> return cmdutil.UsageErrorf(cmd, \"--raw cannot read from a url\") } if o.FilenameOptions.Recursive {", "positive_passages": [{"docid": "doc-en-kubernetes-fb3d610f127a7a4f9ff1a7fc03ca6b60768656de779ed421c207f21093cd272e", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: Currently when run kubectl create with --raw, it will raise \"--raw cannot read from a url \" if the filename has a prefix \"http\", which is not proper as we may have filenames like \"httptest\" or similar. What you expected to happen: Restrict the url check with \"https://\" or \"http://\" prefix. How to reproduce it (as minimally and precisely as possible): Run 'kubectl create --raw URI -f' with a filename which has a \"http\" prefix.\n/sig cli\n--raw should start with\nthe message could be improved, but I think the check is reasonable (I'd actually change it to error if the raw path doesn't start with )\nThis is the filename url check, not the raw path. I think you mean this", "commid": "kubernetes_issue_57370", "tokennum": 228}], "negative_passages": []}
{"query_id": "q-en-kubernetes-031eb3039d12727a047ed13abc100a83b2cc0c7f3e83a572ed84365e2588afc5", "query": "_, err = client.CoreV1().Nodes().Patch(context.TODO(), old.Name, types.StrategicMergePatchType, patchBytes, metav1.PatchOptions{}, \"status\") return err } <ins> func patchPriorityClass(cs clientset.Interface, old, new *schedulingv1.PriorityClass) error { oldData, err := json.Marshal(old) if err != nil { return err } newData, err := json.Marshal(new) if err != nil { return err } patchBytes, err := strategicpatch.CreateTwoWayMergePatch(oldData, newData, &schedulingv1.PriorityClass{}) if err != nil { return fmt.Errorf(\"failed to create merge patch for PriorityClass %q: %v\", old.Name, err) } _, err = cs.SchedulingV1().PriorityClasses().Patch(context.TODO(), old.Name, types.StrategicMergePatchType, patchBytes, metav1.PatchOptions{}) return err } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-3bda2fba5ce2ad90b89601bf2aa62ec37353e4edef7a62972ac2a85cc1aff832", "text": "The following PriorityClass endpoints was Promoted it 1.14 without Conformance tests, and remain untested: replace-, read-, patch-, list-, delete-collection- SchedulingV1PriorityClass According to this APIsnoop query, there are still some remaining PriorityClass endpoints which are untested. with this query you can filter untested endpoints by their category and eligiblity for conformance. e.g below shows a query to find all conformance eligible untested,stable,core endpoints ! createSchedulingV1PriorityClass deleteSchedulingV1PriorityClass Promoted to Conformance 1.19 with /sig testing /sig architecture /area conformance\nIs the ultimiate goal to use conformance tests to explicitly issue all CRUD requests against PriorityClass? And, is equivalent to \"update PriorityClass\"?\nall APIs must have Conformance tests unless they are not eligible for Conformance due to the There is other APIGroups that have both Replace and Update as endpoints. That is the prerogative of the SIG to decide.\ncan you please point us to similar conformance tests used for core objects such as pods and nodes?\nThis is a life cycle test for Create, List, Update, Patch, DeleteCollection More can be found in the test/e2e folder. Also look for examples on the Conformance at previously Promoted Conformance test Reach out if we can help with more information on our approach to Conformance testing.\nI remembered about this PR. Last week a few lines of code was to cover the last of the \"Lease\" endpoint group for conformance. The one file contain the Conformance tests for the complete life cycle of Lease endpoints.\n/assign I will work on it.\n/reopen Will monitor in test grid to move to Conformance after 2 weeks soak.\nReopened this issue. <detailsIn response to : /reopen Will monitor in test grid to move to Conformance after 2 weeks soak. </details\n/triage accepted", "commid": "kubernetes_issue_94954", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-037b11db681326842ad5c6371325d0baeef1820779da3b42d10e2286957408f6", "query": "if p.isPodBackingOff(pod) { if err := p.podBackoffQ.Add(pInfo); err != nil { klog.Errorf(\"Error adding pod %v to the backoff queue: %v\", pod.Name, err) <ins> } else { p.unschedulableQ.delete(pod) </ins> } } else { if err := p.activeQ.Add(pInfo); err != nil { klog.Errorf(\"Error adding pod %v to the scheduling queue: %v\", pod.Name, err) <ins> } else { p.unschedulableQ.delete(pod) </ins> } } <del> p.unschedulableQ.delete(pod) </del> } p.moveRequestCycle = p.schedulingCycle p.cond.Broadcast()", "positive_passages": [{"docid": "doc-en-kubernetes-25b4b43b77be18dfeeb1e5d60f56671fd9593ee9c291ed7dcecd0e9048479b76", "text": "What happened: We will now always delete the pods from unschedulable queue no matter the Add operations succeed or not in function. What you expected to happen: Delete pods from unschedulable queue only when add operations succeeds\n/sig scheduling\n/assign\nWill the pods be to the queues again somewhere if we delete them by mistake here ? It seems that can not make sure to add them again.\nI am not sure if we will add them back again somewhere. If not, not only but also need to be updated. I have already send a PR here:", "commid": "kubernetes_issue_78631", "tokennum": 120}], "negative_passages": []}
{"query_id": "q-en-kubernetes-03893711550b910023fb896859b81e1ea918738eec7af48edb2e99e3a32f4294", "query": "DescribeEvents(events, w) } <ins> printPodsMultiline(w, \"Mounted By\", mountPods) </ins> return nil }) }", "positive_passages": [{"docid": "doc-en-kubernetes-b97e647702b8859b86e9b0127fc694e7b8feffe09fe2ccd8837b28995c7af595", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: I need to know to which Pod(s) a PVC is being mounted to, without having to go through each Pod one by one checking the Volume mounts and the PersistentVolumeClaim. The kubectl describe pvc and get pvc, only tell you to which Persistent Volume the PVC is bound to, but not if is being used by a Pod(s) What you expected to happen: Add a new field in the describe or get that lists the pods that are using the PVC as a volume mount How to reproduce it (as minimally and precisely as possible): Have a PV/PVC bound and create a pod using a volume mount Anything else we need to know?: Not sure if this is only for Azure Disk, which is the Storage Class I am using. Environment: Kubernetes version (use ): 7 Cloud provider or hardware configuration: Azure OS (e.g. from /etc/os-release): Ubuntu 16.04 Kernel (e.g. ): 4 Install tools: Azure Kubernetes Services Others: -n/a\n/sig storage\n/sig cli\nI think the kubectl describe can just construct this on the fly. Another angle is should we add this information to PVC object itself\nThat will be great, as right now the only way to correlate a PVC to a Pod is via a \"describe\" on the Pod.\nI can work on a PR for this!\nGitHub didn't allow me to assign the following users: clandry94. Note that only and repo collaborators can be assigned. <detailsIn response to : I can work on 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\n+1 for the feature. cc\nHow to find \"what pods are using particular PVC through command line\"\n+1 for the feature.\nthis feature will be in Kubernetes 1.12\nok kubernetes 1.12 released, how to? which command?\nCan someone point to the documentation or paste command to get the pods which have the PVC in use\nsee the associated PR to see an example usage of this The line in should show it.\nWorkaround for the meantime:\nThanks , this workaround is great for those people who still use old kubernetes version.", "commid": "kubernetes_issue_65233", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-03893711550b910023fb896859b81e1ea918738eec7af48edb2e99e3a32f4294", "query": "DescribeEvents(events, w) } <ins> printPodsMultiline(w, \"Mounted By\", mountPods) </ins> return nil }) }", "positive_passages": [{"docid": "doc-en-kubernetes-d7becb5323d04fe79bf1f030fc587d9b0aefb9105f1724f943828245df0352e1", "text": "However it will meet an error if the pod have no volumes, so I improves it by adding a to check whether the volumes exists or not.\npython script to list pods with pvc in namespace(s): Is a part of a cli to set pods with velero/restic annotations. Hope it helps someone :)\nFor posterity... There is a Used By: field in the output of describe.\nclient-go didn't give this api... ,PodPVCIndex can solve the problem\nHi thanks worked for me ;) but I want to make it reverse my workarounds with adding after didn't worked do you have any ideas\n$ kubectl describe pvc -A Used\" Name: ocs-deviceset-lso-volumeset-0-data-1b45dn Namespace: openshift-storage StorageClass: lso-volumeset Used By: rook-ceph-osd-1--8fwpd Also useful ^\nthe reason it didn't work is because each return does, in point of fact, have a key defined for claimName. That key is just set to null value. So, what you'd actually want to do is test for nulls. As nice as answer is, it's a PITA to parse unstructured human-readable command output, as opposed to command output in a markup language that well known shell parsers like jq and yq can work with. Towards that end, because I had use of this, I came up with the following: That simple not null test at the end plucks out all your nulls. Obviously invert the last conditional if you want all the nulls, but you'll get all sorts of temp things that way that you probably won't care about.", "commid": "kubernetes_issue_65233", "tokennum": 387}], "negative_passages": []}
{"query_id": "q-en-kubernetes-042f1da61c6a2a685fc274cff1043abc97db694df02f325fae44e4ccdb5b9765", "query": "} } } <ins> func TestMinionListConversionToNew(t *testing.T) { oldMinion := func(id string) v1beta1.Minion { return v1beta1.Minion{JSONBase: v1beta1.JSONBase{ID: id}} } newMinion := func(id string) Minion { return Minion{JSONBase: JSONBase{ID: id}} } oldMinions := []v1beta1.Minion{ oldMinion(\"foo\"), oldMinion(\"bar\"), } newMinions := []Minion{ newMinion(\"foo\"), newMinion(\"bar\"), } table := []struct { oldML *v1beta1.MinionList newML *MinionList }{ { oldML: &v1beta1.MinionList{Items: oldMinions}, newML: &MinionList{Items: newMinions}, }, { oldML: &v1beta1.MinionList{Minions: oldMinions}, newML: &MinionList{Items: newMinions}, }, { oldML: &v1beta1.MinionList{ Items:   oldMinions, Minions: []v1beta1.Minion{oldMinion(\"baz\")}, }, newML: &MinionList{Items: newMinions}, }, } for _, item := range table { got := &MinionList{} err := Convert(item.oldML, got) if err != nil { t.Errorf(\"Unexpected error: %v\", err) } if e, a := item.newML, got; !reflect.DeepEqual(e, a) { t.Errorf(\"Expected: %#v, got %#v\", e, a) } } } func TestMinionListConversionToOld(t *testing.T) { oldMinion := func(id string) v1beta1.Minion { return v1beta1.Minion{JSONBase: v1beta1.JSONBase{ID: id}} } newMinion := func(id string) Minion { return Minion{JSONBase: JSONBase{ID: id}} } oldMinions := []v1beta1.Minion{ oldMinion(\"foo\"), oldMinion(\"bar\"), } newMinions := []Minion{ newMinion(\"foo\"), newMinion(\"bar\"), } newML := &MinionList{Items: newMinions} oldML := &v1beta1.MinionList{ Items:   oldMinions, Minions: oldMinions, } got := &v1beta1.MinionList{} err := Convert(newML, got) if err != nil { t.Errorf(\"Unexpected error: %v\", err) } if e, a := oldML, got; !reflect.DeepEqual(e, a) { t.Errorf(\"Expected: %#v, got %#v\", e, a) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-a574ac2a261fa7b4cd59d0907178e287efcaa3989e734104cb2eecf5d89ff460", "text": "should have the JSON attribute name \"items\", not \"minions\"\nDoh! Fix now and break clients?\nDefine Items and Minions and use Convertors to resolve it?\nSure. I'll make a fix.", "commid": "kubernetes_issue_1101", "tokennum": 45}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0468a7a443e8b8de6d0479dce53518bc4efaf4853bf25bf1534b857eeafb5f97", "query": "const ConfigSourceAnnotationKey = \"kubernetes.io/config.source\" const ConfigMirrorAnnotationKey = \"kubernetes.io/config.mirror\" const ConfigFirstSeenAnnotationKey = \"kubernetes.io/config.seen\" <ins> const ConfigHashAnnotationKey = \"kubernetes.io/config.hash\" </ins> // PodOperation defines what changes will be made on a pod configuration. type PodOperation int", "positive_passages": [{"docid": "doc-en-kubernetes-8bc8d69d49aedfb4a9bf3991de80f7c339e96bfbefe5b1f250dae70fa0393729", "text": "See for more context. Currently, kubelet compares the spec of a mirror pod (created via apiserver) with that of a static pod (config stored as a file) to decide whether the two are considered identical. If they differ, kubelet would delete the mirror pod and re-create it with the correct spec. Due to the fact that apiserver may set default values for some fields in the spec of the mirror pod, the specs could deviate undesirably. To avoid problems like this, we can store the config of a static pod as an annotation in the mirror pod, and compare the static pod with the annotation.\nWould a hash of the config be sufficient if we're only going to compare? The whole spec would generally be more useful, but I wonder if that is too much data to put in an annotation.\nThis seems totally reasonable to me, but I'm still desperately curious why you can't just bypass defaulting when you generate mirror pod from static pod? (i.e. just use the static pod's configuration verbatim)\nIt's not kubelet who applies the default values here. The admission plugin was only run at the apiserver, and to bypass that, you have to ask apiserver to treat mirror pods differently and potentially at multiple places.\nOn May 22, 2015 10:38 AM, \"Yu-Ju Hong\" wrote: Understood, but is it really multiple places? If so then I agree it's a bad idea. Otherwise it might be worth considering as an alternative.\nIt's untenable for Kubelet to assume to know/circumvent all fields that will be set by other entities: admission control, defaulting, late initialization, auto-something, whatever. It needs to obey the same rules as other clients.\nI don't understand why you would ever want to apply any of the things you mentioned to static pods. Static pods should be copied verbatim into the mirror pods, right? That's what I'm proposing.\nWhat if the master is updated before the kubelet, and the master adds a new API field with a default value?\nThat case should be discussed in\nI agree that mirror pod should reflect the true status of the static pod running on the node, and no default values should be set in this case.", "commid": "kubernetes_issue_8683", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0468a7a443e8b8de6d0479dce53518bc4efaf4853bf25bf1534b857eeafb5f97", "query": "const ConfigSourceAnnotationKey = \"kubernetes.io/config.source\" const ConfigMirrorAnnotationKey = \"kubernetes.io/config.mirror\" const ConfigFirstSeenAnnotationKey = \"kubernetes.io/config.seen\" <ins> const ConfigHashAnnotationKey = \"kubernetes.io/config.hash\" </ins> // PodOperation defines what changes will be made on a pod configuration. type PodOperation int", "positive_passages": [{"docid": "doc-en-kubernetes-0491e123884f0f20f50d0a788bca7a6a29e2fa08227703a00221ecbd3bcf483c", "text": "However, I think it'd be harder to implement this way since, as stated above, that there are many things to circumvent in the apiserver itself. It could also be harder to keep this special case from being broken by a yet another new feature/plugin. Keeping the hash of the config in the annotation seems like a good compromise even though it may not reflect the true status 100% accurately. I think this is acceptable. What do you think?\nSure, if you think the annotation approach is easier, I would go with that. I guess in the case Brian mentoined (master adds a new API field with a default value), you would not update the mirror pod, because the static pod definition has not changed?\nYes, a hash would be sufficient.\nIt shouldn't be necessary to update the mirror pod in the case that a new default field was updated, because that field should be populated automatically by the apiserver on decode from etcd.\nWe should fix this so we don't have this problem again in 1.2.", "commid": "kubernetes_issue_8683", "tokennum": 226}], "negative_passages": []}
{"query_id": "q-en-kubernetes-047c471c80eb1acc728dc378bd9f21b8835537ab80436da88be9cb942c953b51", "query": "decoder := legacyscheme.Codecs.DecoderToVersion( legacyscheme.Codecs.UniversalDeserializer(), runtime.NewMultiGroupVersioner( <del> *defaultGroup.GroupVersion(), schema.GroupKind{Group: defaultGroup.GroupVersion().Group}, schema.GroupKind{Group: extGroup.GroupVersion().Group}, </del> <ins> defaultGroup, schema.GroupKind{Group: defaultGroup.Group}, schema.GroupKind{Group: extGroup.Group}, </ins> ), )", "positive_passages": [{"docid": "doc-en-kubernetes-fe4a53f9c12ffb58184de5c048a5217a0a9a95660f59883741a14147feb2210e", "text": "Execute make test WHAT=./pkg/api/testing/ And it failed with information: /kind failing-test\n/sig api-machinery\nwhat's the urgency of fixing this? Is it a release blocker?\ni don't see it as a release blocker. but the problem is in client-go, so it's important to get fixed.", "commid": "kubernetes_issue_71369", "tokennum": 78}], "negative_passages": []}
{"query_id": "q-en-kubernetes-048218f9b2febaa5797d8c6a7c882302dc10af29adf6b29ae337e8b3c7796040", "query": "} func getPatchedJS(contentType string, originalJS, patchJS []byte, obj runtime.Object) ([]byte, error) { <ins> // Remove \"; charset=\" if included in header. if idx := strings.Index(contentType, \";\"); idx > 0 { contentType = contentType[:idx] } </ins> patchType := api.PatchType(contentType) switch patchType { case api.JSONPatchType:", "positive_passages": [{"docid": "doc-en-kubernetes-c21754b57b54e9212f2cf7773a0f449c984b1bc5da8671633611701b2ce62a1e", "text": "Given a request with a Content-Type header set to , the server will respond with an error because it does not exactly match the existing strings. Some browsers (Firefox, see: ) will automatically add to a Content-Type header when making an XHR request.", "commid": "kubernetes_issue_14872", "tokennum": 56}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0488c1df890f349769f24b41eadc6e66660b4f690ea2e35ede119638386b533f", "query": "dockercontainer \"github.com/docker/docker/api/types/container\" dockerfilters \"github.com/docker/docker/api/types/filters\" \"github.com/golang/glog\" <del> \"k8s.io/api/core/v1\" </del> runtimeapi \"k8s.io/kubernetes/pkg/kubelet/apis/cri/v1alpha1/runtime\" )", "positive_passages": [{"docid": "doc-en-kubernetes-fc6177451e9ae3dd109f95c34ca28c9d9a0c4aae10f2acbc42a784aa55bc42f8", "text": "seems to belong to sig node PTAL and fix ASAP\n/assign as it seems like having something to do with", "commid": "kubernetes_issue_50675", "tokennum": 24}], "negative_passages": []}
{"query_id": "q-en-kubernetes-048eb8a50e79825fdf4336ca626219a8b4c182e0a184827a71287bb2b7d5a97c", "query": "glog.Errorf(\"Failed to get hostname. err: %+v\", err) return nil, err } <del> vs.vmUUID, err = getVMUUID() if err != nil { glog.Errorf(\"Failed to get uuid. err: %+v\", err) return nil, err </del> <ins> if cfg.Global.VMUUID != \"\" { vs.vmUUID = cfg.Global.VMUUID } else { vs.vmUUID, err = getVMUUID() if err != nil { glog.Errorf(\"Failed to get uuid. err: %+v\", err) return nil, err } </ins> } runtime.SetFinalizer(vs, logout) return vs, nil", "positive_passages": [{"docid": "doc-en-kubernetes-4b4094f56c55cfa490f4fdbec1ba6d40dc83e208d3fe25d4f173459fce063c48", "text": "Is this a BUG REPORT or FEATURE REQUEST?: What happened: Currently the vsphere cloud provider blocks the controller-manager from running if its running on a non-vmware host, because it reads and checks if its content starts with . What you expected to happen: The controller manager to start How to reproduce it (as minimally and precisely as possible): Start a on a non-vmware environment with the flags set Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/sig vmware\ncan you please share some more context- Why do you want vSphere cloud provider to work with non-vmware host (I believe you mean ESXi)? Where is this requirement coming from.\nWe are building a Kubernetes cluster management solution which does Kubernetes in Kubernetes and works by creating the control planes in one cluster, then creating worker instances on one of the supported platforms, among them vsphere. Currently the cluster hosting the control planes (We call it seed cluster) has to run on ESXi, otherwise the controller-manager crashes. Having the check in place for the Kubelets is completely fine and definitely makes sense, but for the controller-manager it should IMHO not be required.", "commid": "kubernetes_issue_65145", "tokennum": 300}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0490097e924a6ce39172052a8988d33087f97c2e86c6905af339ccdc31fe303f", "query": "<del> apiVersion: v1 kind: ReplicationController metadata: name: es-client labels: component: elasticsearch role: client spec: replicas: 1 template: metadata: labels: component: elasticsearch role: client spec: serviceAccount: elasticsearch containers: - name: es-client securityContext: capabilities: add: - IPC_LOCK image: quay.io/pires/docker-elasticsearch-kubernetes:1.7.1-4 env: - name: KUBERNETES_CA_CERTIFICATE_FILE value: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt - name: NAMESPACE valueFrom: fieldRef: fieldPath: metadata.namespace - name: \"CLUSTER_NAME\" value: \"myesdb\" - name: NODE_MASTER value: \"false\" - name: NODE_DATA value: \"false\" - name: HTTP_ENABLE value: \"true\" ports: - containerPort: 9200 name: http protocol: TCP - containerPort: 9300 name: transport protocol: TCP volumeMounts: - mountPath: /data name: storage volumes: - name: storage emptyDir: {} </del>", "positive_passages": [{"docid": "doc-en-kubernetes-5fef938b0452d0f6b58e576cd11f17813fb6d6b970f83a7868d905b7784a5e39", "text": "Presently, the elasticsearch example Kubernetes configurations target elasticsearch v1.7.1, which is quite old. As of this writing, the latest elasticsearch release is v5.6.2, with many deployment changes since then. Could the elasticsearch examples be updated to target the v5 series of elasticsearch? See for a more up to date reference configuration.\ncc\nhey it's been a long while since I last contributed to the docs. i can do it soon but i need pointers on how to properly do it.\nhey, so we need to update the stuff under examples/elasticsearch/ *&repos=kubernetes So basically update the images, yaml files etc and test that everything works (and submit a PR)\n/sig testing\nAh, so there's no documentation updates anymore. OK I'll take care of it, assign it to me.\nIssues 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\nGitHub didn't allow me to assign the following users: me. Note that only and repo collaborators can be assigned. <detailsIn response to : /assign me 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\n/assign pires\n/remove-lifecycle stale\nit seems that the example moved to I am now reading that repo guidelines and will update this there. I'll also open a PR that cleans this folder in the current repo and closes this issue.", "commid": "kubernetes_issue_53142", "tokennum": 387}], "negative_passages": []}
{"query_id": "q-en-kubernetes-04b7a64a68b1bf1979a36364d72568d5346788def3ea278216866715619708b2", "query": "return res, nil } <ins> // doCmdWithoutAttr a simple wrapper of netlink socket execute command func (i *Handle) doCmdWithoutAttr(cmd uint8) ([][]byte, error) { req := newIPVSRequest(cmd) req.Seq = atomic.AddUint32(&i.seq, 1) return execute(i.sock, req, 0) } </ins> func assembleDestination(attrs []syscall.NetlinkRouteAttr) (*Destination, error) { var d Destination", "positive_passages": [{"docid": "doc-en-kubernetes-13eba344b12142e2782a67745f08ac2e814f1785c70b127779bdac58248d8b7b", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: Currently, we flush ipvs services by deleting them one by one. That's because there was no flush API in libnetwork. Now, libnetwork supports flush API, I think it's time to rsync. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration**: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig network\n/area kube-proxy\n/assign", "commid": "kubernetes_issue_52070", "tokennum": 279}], "negative_passages": []}
{"query_id": "q-en-kubernetes-04bdb3d2bb63267cc2d28461f18221496da6ec0095e36e4d303c9ec939a231a7", "query": "} return false, nil } <ins> // stripComments will transform a YAML file into JSON, thus dropping any comments // in it. Note that if the given file has a syntax error, the transformation will // fail and we will manually drop all comments from the file. func stripComments(file []byte) []byte { stripped, err := yaml.ToJSON(file) if err != nil { stripped = manualStrip(file) } return stripped } // manualStrip is used for dropping comments from a YAML file func manualStrip(file []byte) []byte { stripped := []byte{} for _, line := range bytes.Split(file, []byte(\"n\")) { if bytes.HasPrefix(bytes.TrimSpace(line), []byte(\"#\")) { continue } stripped = append(stripped, line...) stripped = append(stripped, 'n') } return stripped } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-5d8539be161cacf223528437869590f13423a31b1176c381211bcba6b79e0cca", "text": "When trying to edit multiple resources, for example: will panic. Ref as the possible cause cc\nif was the cause, any fix needs to happen in 1.1 as well, was already cherry picked there\nAlso shows that we need a test for this case.\nis the cause. When we edit multiple resources (i.e., list-type objects), the list's Accessor.annotations (type ) is nil and will panic when UpdateApplyAnnotation tries to SetAnnotations ().", "commid": "kubernetes_issue_15907", "tokennum": 108}], "negative_passages": []}
{"query_id": "q-en-kubernetes-04ca28e209619b51de2fc00ab3155bf930e55991a0c8a1b712ecaf344bf00a5a", "query": "t.Errorf(\"unexpected portallocator state: %d free\", free) } } <ins> func TestCollectServiceNodePorts(t *testing.T) { tests := []struct { name        string serviceSpec corev1.ServiceSpec expected    []int }{ { name: \"no duplicated nodePorts\", serviceSpec: corev1.ServiceSpec{ Ports: []corev1.ServicePort{ {NodePort: 111, Protocol: corev1.ProtocolTCP}, {NodePort: 112, Protocol: corev1.ProtocolUDP}, {NodePort: 113, Protocol: corev1.ProtocolUDP}, }, }, expected: []int{111, 112, 113}, }, { name: \"duplicated nodePort with TCP protocol\", serviceSpec: corev1.ServiceSpec{ Ports: []corev1.ServicePort{ {NodePort: 111, Protocol: corev1.ProtocolTCP}, {NodePort: 111, Protocol: corev1.ProtocolTCP}, {NodePort: 112, Protocol: corev1.ProtocolUDP}, }, }, expected: []int{111, 111, 112}, }, { name: \"duplicated nodePort with UDP protocol\", serviceSpec: corev1.ServiceSpec{ Ports: []corev1.ServicePort{ {NodePort: 111, Protocol: corev1.ProtocolUDP}, {NodePort: 111, Protocol: corev1.ProtocolUDP}, {NodePort: 112, Protocol: corev1.ProtocolTCP}, }, }, expected: []int{111, 111, 112}, }, { name: \"duplicated nodePort with different protocol\", serviceSpec: corev1.ServiceSpec{ Ports: []corev1.ServicePort{ {NodePort: 111, Protocol: corev1.ProtocolTCP}, {NodePort: 112, Protocol: corev1.ProtocolTCP}, {NodePort: 111, Protocol: corev1.ProtocolUDP}, }, }, expected: []int{111, 112}, }, { name: \"no duplicated port(with health check port)\", serviceSpec: corev1.ServiceSpec{ Ports: []corev1.ServicePort{ {NodePort: 111, Protocol: corev1.ProtocolTCP}, {NodePort: 112, Protocol: corev1.ProtocolUDP}, }, HealthCheckNodePort: 113, }, expected: []int{111, 112, 113}, }, { name: \"nodePort has different protocol with duplicated health check port\", serviceSpec: corev1.ServiceSpec{ Ports: []corev1.ServicePort{ {NodePort: 111, Protocol: corev1.ProtocolUDP}, {NodePort: 112, Protocol: corev1.ProtocolTCP}, }, HealthCheckNodePort: 111, }, expected: []int{111, 112}, }, { name: \"nodePort has same protocol as duplicated health check port\", serviceSpec: corev1.ServiceSpec{ Ports: []corev1.ServicePort{ {NodePort: 111, Protocol: corev1.ProtocolUDP}, {NodePort: 112, Protocol: corev1.ProtocolTCP}, }, HealthCheckNodePort: 112, }, expected: []int{111, 112, 112}, }, } for _, tc := range tests { t.Run(tc.name, func(t *testing.T) { ports := collectServiceNodePorts(&corev1.Service{ ObjectMeta: metav1.ObjectMeta{Namespace: \"one\", Name: \"one\"}, Spec:       tc.serviceSpec, }) sort.Ints(ports) if !reflect.DeepEqual(tc.expected, ports) { t.Fatalf(\"Invalid resultnexpected: %vngot: %v\", tc.expected, ports) } }) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-8c9ebf4e41021efd0692132f5b2f5e7ec08451127a302fc405c42cb972b9ed2e", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: I created several Workloads which require up to ten ports for both UDP and TCP protocol. Now my logs get spammed with . What you expected to happen: should consider -combination instead of only . How to reproduce it (as minimally and precisely as possible): Deploy any service with a node-port with both protocols, e.g.: Anything else we need to know?: This was already acknowledged by here: However, as this thread addresses a different bug and seems kind of stuck, i'd like to suggest that this might be addressed in a new context. Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Deployed via Rancher v2.4.3\n/sig api-machinery\n/remove-sig api-machinery /sig network\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nHow did you get into this situation? The allocator should not have granted the same node port twice?\nOh right, that issue. The only real way out is to de-allocate the NodePorts and then re-allocate them, I think\nAs this happens for all of my ports in the said Production Application (the one where my log gets spammed) as well as complete fresh installation (where i verified the bug), i think there's no \"way out\" except fixing the bug. As said, for me it's necessary to assign both protocols to the same port. This might be a niche-use-case, but checking the it's actually very likely for ports to allow tcp AND udp. I'm not sure about the history of this, but it might be that issue was the origin, which was adressed in PR (\"Allow services which use same port, different protocol to use the same nodePort for both\"). But this PR doesn't contain the adjustment of the said , so still considers the behaviour as invalid, while it's actually allowed and supported.", "commid": "kubernetes_issue_91404", "tokennum": 498}], "negative_passages": []}
{"query_id": "q-en-kubernetes-04ca28e209619b51de2fc00ab3155bf930e55991a0c8a1b712ecaf344bf00a5a", "query": "t.Errorf(\"unexpected portallocator state: %d free\", free) } } <ins> func TestCollectServiceNodePorts(t *testing.T) { tests := []struct { name        string serviceSpec corev1.ServiceSpec expected    []int }{ { name: \"no duplicated nodePorts\", serviceSpec: corev1.ServiceSpec{ Ports: []corev1.ServicePort{ {NodePort: 111, Protocol: corev1.ProtocolTCP}, {NodePort: 112, Protocol: corev1.ProtocolUDP}, {NodePort: 113, Protocol: corev1.ProtocolUDP}, }, }, expected: []int{111, 112, 113}, }, { name: \"duplicated nodePort with TCP protocol\", serviceSpec: corev1.ServiceSpec{ Ports: []corev1.ServicePort{ {NodePort: 111, Protocol: corev1.ProtocolTCP}, {NodePort: 111, Protocol: corev1.ProtocolTCP}, {NodePort: 112, Protocol: corev1.ProtocolUDP}, }, }, expected: []int{111, 111, 112}, }, { name: \"duplicated nodePort with UDP protocol\", serviceSpec: corev1.ServiceSpec{ Ports: []corev1.ServicePort{ {NodePort: 111, Protocol: corev1.ProtocolUDP}, {NodePort: 111, Protocol: corev1.ProtocolUDP}, {NodePort: 112, Protocol: corev1.ProtocolTCP}, }, }, expected: []int{111, 111, 112}, }, { name: \"duplicated nodePort with different protocol\", serviceSpec: corev1.ServiceSpec{ Ports: []corev1.ServicePort{ {NodePort: 111, Protocol: corev1.ProtocolTCP}, {NodePort: 112, Protocol: corev1.ProtocolTCP}, {NodePort: 111, Protocol: corev1.ProtocolUDP}, }, }, expected: []int{111, 112}, }, { name: \"no duplicated port(with health check port)\", serviceSpec: corev1.ServiceSpec{ Ports: []corev1.ServicePort{ {NodePort: 111, Protocol: corev1.ProtocolTCP}, {NodePort: 112, Protocol: corev1.ProtocolUDP}, }, HealthCheckNodePort: 113, }, expected: []int{111, 112, 113}, }, { name: \"nodePort has different protocol with duplicated health check port\", serviceSpec: corev1.ServiceSpec{ Ports: []corev1.ServicePort{ {NodePort: 111, Protocol: corev1.ProtocolUDP}, {NodePort: 112, Protocol: corev1.ProtocolTCP}, }, HealthCheckNodePort: 111, }, expected: []int{111, 112}, }, { name: \"nodePort has same protocol as duplicated health check port\", serviceSpec: corev1.ServiceSpec{ Ports: []corev1.ServicePort{ {NodePort: 111, Protocol: corev1.ProtocolUDP}, {NodePort: 112, Protocol: corev1.ProtocolTCP}, }, HealthCheckNodePort: 112, }, expected: []int{111, 112, 112}, }, } for _, tc := range tests { t.Run(tc.name, func(t *testing.T) { ports := collectServiceNodePorts(&corev1.Service{ ObjectMeta: metav1.ObjectMeta{Namespace: \"one\", Name: \"one\"}, Spec:       tc.serviceSpec, }) sort.Ints(ports) if !reflect.DeepEqual(tc.expected, ports) { t.Fatalf(\"Invalid resultnexpected: %vngot: %v\", tc.expected, ports) } }) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-33f53ed726ab1a89c68c77aae3b932484545b038842bda14047a639f615b725d", "text": "/assign\nAhh, I thought you meant that you had accidentally been allocated the same nodePorts and I was very confused when you said \"all of them\". I have reproduced this issue, and I can see it by inspection. The obvious fix would be to collect ports split by protocol, but I think that's not right since we don't store it split. An even simpler fix would be for to build a . Then for each protocol, for each port, build that contains all the port numbers, but remove any duplicates ONLY IF they are duplicated across protocols. Duplicates in the same protocol should be retained (to report an error later). I don't have time to tackle this tonight (and write a test), but it seems like a good bug.\nperhaps I can fix this problem /assign\nthings may be a little more complicated. Right now the is not aware of the protocol of the port so I guess simply rewriting function to return is not enough, the port allocator will still return on same node port even with different protocol. perhaps we need to refactor the to make it protocol-aware.\nI don't think we need to do make the allocator be protocol aware. IIRC we allow you to use the same nodeport on different protocols ONLY within a single service. This means (I think) that we can do hyper-local deduplication as we collect the nodeports for each service. If we find the same nodeport number with different protocols, just remove the duplicates because it is allowed. I.e. a service that looks like: return - deduped. if ANY OTHER service tried to use it would be an error at the \"rebuilt\" allocator Likewise if a single Service claims to use the same nodeport number more than once on the same protocol, it should be an error: return - NOT deduped.\nobviously, we want a great unit test here :P\nah got it! thanks for your detailed explanation!\nHi! I have filed a PR to resolve this issue, could you take a look?", "commid": "kubernetes_issue_91404", "tokennum": 428}], "negative_passages": []}
{"query_id": "q-en-kubernetes-04db253b97c90cd8e841c3d62b63604327cd4a68b99ff8c949e2b145c733c6c7", "query": "dir := cacheDir if len(dir) > 0 { version, err := clientset.Discovery().ServerVersion() <del> if err != nil { return nil, err </del> <ins> if err == nil { dir = path.Join(cacheDir, version.String()) } else { dir = \"\" // disable caching as a fallback </ins> } <del> dir = path.Join(cacheDir, version.String()) </del> } fedClient, err := clients.FederationClientForVersion(nil) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-0e6152e65eb2ac92729fbf36045ced1b3b82ff210ce22134b0c0a6ef8bf6047e", "text": "kubectl works mostly fine without /version. But a number of commands (apply, create, convert, ....) are wired to this: A 404 on /version let's the kubectl to fail hard. For environments where might be a security problem (cf. ) this is a nogo. Relates to minimal apiserver routes:\n/cc\n/version is desirable (we think all servers should have it) but it should not be required for the proper functioning of a client to be able to retrieve it.", "commid": "kubernetes_issue_32679", "tokennum": 111}], "negative_passages": []}
{"query_id": "q-en-kubernetes-04def097fbcc25d785370bcc4246ec8670516b4ed1fc7f2bb7e66fb620c942c7", "query": "} } <ins> // createCustomResourceDefinition removes potentially stale storage so it gets re-created func (r *crdHandler) createCustomResourceDefinition(obj interface{}) { crd := obj.(*apiextensions.CustomResourceDefinition) r.customStorageLock.Lock() defer r.customStorageLock.Unlock() // this could happen if the create event is merged from create-update events r.removeStorage_locked(crd.UID) } // updateCustomResourceDefinition removes potentially stale storage so it gets re-created </ins> func (r *crdHandler) updateCustomResourceDefinition(oldObj, newObj interface{}) { oldCRD := oldObj.(*apiextensions.CustomResourceDefinition) newCRD := newObj.(*apiextensions.CustomResourceDefinition)", "positive_passages": [{"docid": "doc-en-kubernetes-16c95be4925a0d298a67709c93efbb137b71325e5e3041edcf306d6572e4ae65", "text": "Which jobs are failing: pull-kubernetes-integration Which test(s) are failing: TestWebhookConverterWithDefaulting /assign /priority important-soon /area custom-resources /sig api-machinery /kind flake /milestone v1.16\n/cc\nseveral of the webhook converter tests have similar flakes. it looks like the wait for storage version to become effective times out occasionally Rare flakes seen in all of these tests: TestWebhookConverterWithWatchCache/nontrivial-converter TestWebhookConverterWithWatchCache/metadata-mutating-converter TestWebhookConverterWithDefaulting/metadata-mutating-converter TestWebhookConverterWithWatchCache/noop-converter TestWebhookConverterWithDefaulting/empty-response TestWebhookConverterWithoutWatchCache/nontrivial-converter/check-2 TestWebhookConverterWithoutWatchCache/noop-converter/check-0/v1beta2 TestWebhookConverterWithoutWatchCache/nontrivial-converter/check-0/v1beta2\ncc\nYikes, I\u2019ll sort it out.\niiuc sending an empty patch gets short-circuited and doesn't bump CR generation, even if the storage version gets changed, which means we do not re-write to etcd and go through the encoding path this would be racing and doing noop's if the first pass of didn't get the expected storage version I will send a fix to make the patch do actual mutation\nIt doesn't bump generation, but the bytes to persist in etcd would still be different if the storage version had changed, so they should persist. You can verify that by changing the storage version on a CRD yourself, do an empty patch, and see if the resourceVersion changes.\nyou're right. Generation is for non-metadata change only, and the RV changes. I queried etcd locally and the apiVersion did change for an empty patch (sidetracking: another observation is after changing the storage version (say v1 -v2; noop convertor), empty-patching v2 endpoint would bump generation, while empty-patching v1 endpoint wouldn't)\nanother theory: our cached storage strategy could be stale if the CRD informer merges multiple events together (e.g. the informer does a re-list).", "commid": "kubernetes_issue_78913", "tokennum": 546}], "negative_passages": []}
{"query_id": "q-en-kubernetes-04def097fbcc25d785370bcc4246ec8670516b4ed1fc7f2bb7e66fb620c942c7", "query": "} } <ins> // createCustomResourceDefinition removes potentially stale storage so it gets re-created func (r *crdHandler) createCustomResourceDefinition(obj interface{}) { crd := obj.(*apiextensions.CustomResourceDefinition) r.customStorageLock.Lock() defer r.customStorageLock.Unlock() // this could happen if the create event is merged from create-update events r.removeStorage_locked(crd.UID) } // updateCustomResourceDefinition removes potentially stale storage so it gets re-created </ins> func (r *crdHandler) updateCustomResourceDefinition(oldObj, newObj interface{}) { oldCRD := oldObj.(*apiextensions.CustomResourceDefinition) newCRD := newObj.(*apiextensions.CustomResourceDefinition)", "positive_passages": [{"docid": "doc-en-kubernetes-4d6bef5a272bfef04fa7527d92c495ee5b0e5d06d06a593b8089b98a3b84ddb9", "text": "Two scenarios: -create-update events merged into an update event: strategy with UID:a was created on demand for CRD Foo Foo was deleted and recreated strategy with UID:b was created on demand for the new Foo new Foo got updated (e.g. switching storage version) the strategy with UID:b is supposed to be deleted and , to reflect the last update. But if the CRD informer merges the delete-create-update events into , the strategy with UID:a will be deleted, but the strategy with UID:b won't. -update events merged into a create event: strategy with UID:a was created on demand for CRD Foo Foo was updated (e.g. switching storage version) the strategy with UID:a is supposed to be deleted and , to reflect the last update. But if the CRD informer merges the create-update events into , the strategy with UID:a won't be deleted (as we don't react on create events). another race found in , which could happen in a single update.\nI think I :", "commid": "kubernetes_issue_78913", "tokennum": 234}], "negative_passages": []}
{"query_id": "q-en-kubernetes-04f6efb8bcb4aec413d39ba2091672c3b22dfbbeb4999e9a75a7904a4970f1d6", "query": "} func (tc *patchTestCase) runner(t *testing.T) { <ins> scheme := NewTestScheme() metav1.AddMetaToScheme(scheme) </ins> client := NewSimpleMetadataClient(scheme, tc.object) resourceInterface := client.Resource(schema.GroupVersionResource{Group: testGroup, Version: testVersion, Resource: testResource}).Namespace(testNamespace)", "positive_passages": [{"docid": "doc-en-kubernetes-d7e6fda1614d5720cc8c8b15824f08c5e880f7950d0c5cc5cd811c2fcceb82ab", "text": "Because of this scheme mutation, this leads to concurrent use of the same scheme to cause the program to panic. It would be ideal to do this in some concurrent safe manner or add a warning or similar\n/sig api-machinery\n/assign\n/assign /triage accepted", "commid": "kubernetes_issue_107823", "tokennum": 54}], "negative_passages": []}
{"query_id": "q-en-kubernetes-04f9f923d5cede3fd1a8a91bb5c038893421e978953a1b06f2df3c5cc25de6e4", "query": "SchedulingAlgorithmPremptionEvaluationDuration, PreemptionVictims, PreemptionAttempts, <ins> equivalenceCacheLookups, EquivalenceCacheWrites, </ins> } )", "positive_passages": [{"docid": "doc-en-kubernetes-aa59e6a5adfc1b233e34e0c1fe9e3a0ec7f2fe6a4636f877a41f4c9aef45f71d", "text": "/kind feature The equivalence cache feature is planned to move to beta in 1.11, and it would be useful to have some metrics attached to it. The equivalence cache should improve scheduling throughput, so we want to be able to correlate e.g. throughput with eCache hit rate. /sig scheduling /sig instrumentation\n/assign misterikkit\nIssues 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\n/remove-lifecycle stale", "commid": "kubernetes_issue_63259", "tokennum": 154}], "negative_passages": []}
{"query_id": "q-en-kubernetes-051f02595cd7d529a3bd93f350b832bfe02a46f84a8639f92fae7f920de0051a", "query": "t.Fatalf(\"fail to enumerate network interface, %s\", err) } if !ipv6 { <del> t.Fatalf(\"no ipv6 loopback interface\") </del> <ins> t.Skip(\"no ipv6 loopback interface\") </ins> } host, port, err := LoopbackHostPort(\"[ff06:0:0:0:0:0:0:c3]:443\")", "positive_passages": [{"docid": "doc-en-kubernetes-a8f4a2c4efafea09945dcba88cce946e365cd281546f6c4fd8280bc12f2c4ef5", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: TestLoopbackHostPortIPv6 fails when run in the machine where there is no IPv6 loopback device configured, with following error: Especially running in the containers where IPv6 is not really configured for the runtime What you expected to happen: Unit tests shouldn't really depend on the environment it is running, How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): master\n/sig testing /cc\n/assign\n/remove-sig testing /sig api-machinery EDIT: This is a specific SIG's unit test that is environment dependent, not a systemic test issue or the framework etc.\n/cc", "commid": "kubernetes_issue_94375", "tokennum": 207}], "negative_passages": []}
{"query_id": "q-en-kubernetes-053eff727a21b343aa7d5f278bf254d95ee89937d98c2e7ddbb6e298e3604d02", "query": "} patchedJS, retErr = jsonpatch.MergePatch(versionedJS, p.patchBytes) <ins> if retErr == jsonpatch.ErrBadJSONPatch { return nil, nil, errors.NewBadRequest(retErr.Error()) } </ins> return patchedJS, strictErrors, retErr default: // only here as a safety net - go-restful filters content-type", "positive_passages": [{"docid": "doc-en-kubernetes-70cc8a837504b60a5c6c5f5140cd4a6de426afd5bd1cc3a810b5342e232bd03d", "text": "integration-master ci-kubernetes-integration-master.OverallChanges 11/19/2021 23:54 CET see this as example to get information about the failure No response No response_\ngreat catch /sig api-machinery /priority critical-urgent it seems all tests fail with how can this fail consistently only in periodics and not in presubmits? is an external dependency?\nI would say this is the origin Server Side Strict Field Validation \npresubmits only run short tests, periodics run all long ones... looking if there's a long test that needs fixup\nfix in", "commid": "kubernetes_issue_106573", "tokennum": 127}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0572b682d3f6d59213034439da9e9372bff033c3ad358dde5090be089c9ed473", "query": "http_archive( name = \"io_bazel_rules_go\", <del> sha256 = \"a4ea00b71a6fc3bd381cbbf6eb83ec91fe8b32b1c622c048f1e6f0d965bb1a2d\", strip_prefix = \"rules_go-a280fbac1a0a4c67b0eee660b4fd1b3db7c9f058\", urls = [\"https://github.com/bazelbuild/rules_go/archive/a280fbac1a0a4c67b0eee660b4fd1b3db7c9f058.tar.gz\"], </del> <ins> sha256 = \"441e560e947d8011f064bd7348d86940d6b6131ae7d7c4425a538e8d9f884274\", strip_prefix = \"rules_go-c72631a220406c4fae276861ee286aaec82c5af2\", urls = [\"https://github.com/bazelbuild/rules_go/archive/c72631a220406c4fae276861ee286aaec82c5af2.tar.gz\"], </ins> ) http_archive(", "positive_passages": [{"docid": "doc-en-kubernetes-1b1e05089c93c6eb59b848626d58302483d33d2f2e5531ac5b621da204277493", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind feature This is a followup on , but for Go 1.9 We should do the same kind of testing now to possibly catch bugs in either Go or Kubernetes when doing this kind of dependency version bump. Ideally we'd have automated tests against Go tip (), but we don't have that at the moment, so we have to do it kind of manually. We should also decide which k8s version we should target. k8s v1.8 or v1.9? What Go versions have been used so far? Kubernetes v1.7.0 - go1.8.3 Kubernetes v1.6.0 - go1.7.5 Kubernetes v1.5.0 - go1.7.4 Kubernetes v1.4.0 - go1.6.3 Kubernetes v1.3.0 - go1.6.2 Kubernetes v1.2.0 - go1.4.2 Seems like the trend has been to stay on the same Go version for two releases and then bump. That'd mean we'd switch to Go1.9 in k8s v1.9 Everyone happy with that? Or is there any reason for us to go start using go1.9 in k8s v1.8? In any case, we should indeed start testing go1.9 out now... cc\nLet me know if you find any bugs\nFWIW pretty tight to code-freeze I would prefer punting out a cycle fwiw.\nI don't think we're that close to code freeze given that we have 5 (of 8) weeks left in this coding cycle But I'm happy to defer this to v1.9 if others think that. I guess the main reason for a bump would be scalability goals, but I'm not sure we have the need to expand above 5000 (and that Go would be the bottleneck in that case) for v1.8\nmade the Go benchmarks 9% faster with 15% larger binaries. I'm interested to see how that affects our numbers.\nmid-stack inlining was not included in Go 1.9. It made the compiler too slow. It's being targeted to Go 1.10 now instead, after some compiler optimization work.\nOh, thanks for the correction!", "commid": "kubernetes_issue_49484", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0572b682d3f6d59213034439da9e9372bff033c3ad358dde5090be089c9ed473", "query": "http_archive( name = \"io_bazel_rules_go\", <del> sha256 = \"a4ea00b71a6fc3bd381cbbf6eb83ec91fe8b32b1c622c048f1e6f0d965bb1a2d\", strip_prefix = \"rules_go-a280fbac1a0a4c67b0eee660b4fd1b3db7c9f058\", urls = [\"https://github.com/bazelbuild/rules_go/archive/a280fbac1a0a4c67b0eee660b4fd1b3db7c9f058.tar.gz\"], </del> <ins> sha256 = \"441e560e947d8011f064bd7348d86940d6b6131ae7d7c4425a538e8d9f884274\", strip_prefix = \"rules_go-c72631a220406c4fae276861ee286aaec82c5af2\", urls = [\"https://github.com/bazelbuild/rules_go/archive/c72631a220406c4fae276861ee286aaec82c5af2.tar.gz\"], </ins> ) http_archive(", "positive_passages": [{"docid": "doc-en-kubernetes-018b01245292fe1977b7eec8bea53846947ed737ea149d849054911d63924f58", "text": "Regardless, we need to run the scalability tests against the RC so we can report issues earlier-- the last upgrade was particularly painful because of an HTTP regression that we caught way too late.\nyeah. I filed for that now\nyeah, my recollection is that the Go releases usually occur too late in our release cadence and end up getting bumped to the next Kubernetes release. (Also we inevitably find something wrong, though testing RCs would help with that. Though I'm not sure anyone has cycles to test RCs and fix all of the issues that do come up.)\nBased on our current time frame, it looks like go1.9 support will have to slip to k8s 1.9. is open to dig into and start things testing, but there's a number of things that have to move.. I'll try to document those this time around to help with future go version bumps. So far: bazel build rules needed to be updated to support go1.9 () bazel version possibly needs to be updated? some of our custom bazel rules broke\nWhen done, we should update this:\n/priority important-soon\nUpdating the dependency is blocked pending bazel 0.6.0 - .\nCan we upgrade to 0.6.0 now? Does bazel 0.6.0 have multiarch support btw?\nWe can't update to depend on bazel 0.6.0+ until we can figure out how to support different versions of the bazelbuild and kubekins-e2e images in PR jobs in prow based on what branch is being tested. cc\nNoting that we're working on branching jobs, is testing one option here:\n[MILESTONENOTIFIER] Milestone Issue Current <details open<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts. : New functionality.", "commid": "kubernetes_issue_49484", "tokennum": 416}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0572b682d3f6d59213034439da9e9372bff033c3ad358dde5090be089c9ed473", "query": "http_archive( name = \"io_bazel_rules_go\", <del> sha256 = \"a4ea00b71a6fc3bd381cbbf6eb83ec91fe8b32b1c622c048f1e6f0d965bb1a2d\", strip_prefix = \"rules_go-a280fbac1a0a4c67b0eee660b4fd1b3db7c9f058\", urls = [\"https://github.com/bazelbuild/rules_go/archive/a280fbac1a0a4c67b0eee660b4fd1b3db7c9f058.tar.gz\"], </del> <ins> sha256 = \"441e560e947d8011f064bd7348d86940d6b6131ae7d7c4425a538e8d9f884274\", strip_prefix = \"rules_go-c72631a220406c4fae276861ee286aaec82c5af2\", urls = [\"https://github.com/bazelbuild/rules_go/archive/c72631a220406c4fae276861ee286aaec82c5af2.tar.gz\"], </ins> ) http_archive(", "positive_passages": [{"docid": "doc-en-kubernetes-69273b286facac9ab246a3deb71fa6e24d55618a503d411a1618742e8a027c28", "text": "</details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details\nI approved this for v1.9, this is something we definitely want in order to keep up with Go (and for improved performance)\nwe're starting to use the forked images now /cc this should be more feasible very soon Edit: test-infra jobs have also been using bazel 0.6 (now 0.6.1) / a recent rules_go to soak things a bit\nWe've identified a failing test as a result of the WIP PR to upgrade the codebase to go1.9: The admission webhook test fails with certificate errors under go1.9.1, but runs successfully under go1.8.3. cc: who wanted to be alerted to potential bugs\n- please see for a possible fix", "commid": "kubernetes_issue_49484", "tokennum": 212}], "negative_passages": []}
{"query_id": "q-en-kubernetes-057d19e40eb2ef70e7cd79e96c68c5c796108fe4f4f1000a13c95c10e04ff230", "query": "<ins> /* Copyright 2024 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package features import ( utilfeature \"k8s.io/apiserver/pkg/util/feature\" \"testing\" ) func TestKubeFeatures(t *testing.T) { features := utilfeature.DefaultFeatureGate.DeepCopy().GetAll() for i := range features { featureName := string(i) if featureName == \"AllAlpha\" || featureName == \"AllBeta\" { continue } if _, ok := defaultKubernetesFeatureGates[i]; !ok { t.Errorf(\"The feature gate %q is not registered\", featureName) } } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-6eb9bac2f3074e091af4e33eda553e3139bfcfe5ecf153737d95dc4605072155", "text": "This avoids drift between Kubernetes components and allows for cluster management tools that pass uniform feature gates to all components. xref:\n/assign\nHey I f you stuck anywhere. Please free to involve me in this.", "commid": "kubernetes_issue_121613", "tokennum": 45}], "negative_passages": []}
{"query_id": "q-en-kubernetes-05b22e6e790c935a7450ef969b1696b117363d9778fe8c17baf78c6c21c72df2", "query": "\"os/exec\" \"strings\" <del> v1 \"k8s.io/api/core/v1\" </del> <ins> \"k8s.io/api/core/v1\" </ins> metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" <ins> \"k8s.io/apimachinery/pkg/util/sets\" </ins> \"k8s.io/apimachinery/pkg/util/uuid\" utilfeature \"k8s.io/apiserver/pkg/util/feature\" \"k8s.io/kubernetes/pkg/features\"", "positive_passages": [{"docid": "doc-en-kubernetes-b8a3e3a5c22dc8491069aa612d226f113bfee5a5c0b17ff9cb35a90b4b6a10ba", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: , Which test(s) are failing: Since when has it been failing: since this PR introduced them Testgrid link: Note that this is the flakiest test in both dashboards, and failing quite frequently. Reason for failure: unknown Anything else we need to know: cc\n/sig node\nsee: , both getting empty PID and multiple PIDs.\nopened revert at\nfor discoverability for the release team /priority critical-urgent /milestone v1.17", "commid": "kubernetes_issue_84209", "tokennum": 127}], "negative_passages": []}
{"query_id": "q-en-kubernetes-05c4205e1ef110a852b4e4be43bf1cd4993924044da9990a9f98c9030550d785", "query": "Namespace: api.NamespaceDefault, }, Spec: api.ReplicationControllerSpec{ <del> Replicas: 0, </del> <ins> Replicas: replicas, </ins> Template: &d.Spec.Template, }, }", "positive_passages": [{"docid": "doc-en-kubernetes-ceb20554e653f6657baad1bbb36c40e66d8a76887956e3c674b77febc82d4455", "text": "There's some practical limit on the number of concurrent access tokens that can be used in a Kubernetes cluster before it begins to spend all of its time in the authn stack verifying them. Absent fixes to it was < 500; with the fixes linked there it's still not infinitely scalable-- I still hit (what I believe to be) with ~ 5k unique tokens @ ~700QPS. This request is to this dimension an official name & definition, and list it with others, e.g. here: it it have a useful value (I think it should be 10k) /kind bug /sig scalability\n/cc\noh and 4. add tests which verify it is as high as believed.\ncc since projected tokens will increase the number of unique tokens\n/sig auth\nLRUs are not good at scaling and sharding has some major pitfalls as pointed out. I would suggest that we try to drop the LRU cache for successful authentication results in the token cache. The main benefit of using an LRU here is bound cache size. Entries in the token cache have a fast expiration independent of the LRU policy. The records probably take up O(2kb) (guesstimate) of memory. Given that these are successful attempts with presumably valid tokens, I don't think we are getting any benefit from the LRU. If we don't have a constraint on fixed cache size, we can back the token cache with a sync.Map and run a single background goroutine to periodically walk the map and remove expired entries. This would fix the problematic locking and eviction due to nonuniform distribution of tokens over shards. The failure cache is less important and we don't cache failures by default. If we consider this the \"slowpath\", we can probably leave it as. If that's not good enough, we have a couple options (with various tradeoffs) to improve it.\nIf off by default is not enough, more reasoning why the failed cache is not super useful: it might help with an accidental DoS but it doesn't prevent anything actively malicious DoS. I think we can focus our improvements on the success cache.\n/assign He is already working on adding an explicit test for it.\nhas taken it over and is actively working on this. Unfortunately, I cannot assign this issue to him as he's not a k8s member yet\nIt's not closed - all testes must be submitted and appropriate documentation must be\nThanks everyone!!", "commid": "kubernetes_issue_83375", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-05c4e6878112ce64375041da94bbd0932ff7432bb56daa057f00523a0683a935", "query": "\"description\": \"EndpointPort represents a Port used by an EndpointSlice\", \"properties\": { \"appProtocol\": { <del> \"description\": \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and http://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.\", </del> <ins> \"description\": \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.\", </ins> \"type\": \"string\" }, \"name\": {", "positive_passages": [{"docid": "doc-en-kubernetes-3e7e95e6f142ca39e6e3ca0b78c3932bd6cbdfdc898eed9d3ffda27d28f904c7", "text": "We should make the change in PR API reference links to should use HTTPS, not HTTP Visit h and look at the IANA hyperlinks Once this fix is made, a PR to is needed to update the docs (by autogenerating them). This typically would be deferred until the next Kubernetes release. v1.23 not applicable not applicable not applicable not applicable not applicable\n/sig docs\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI opened this issue so that someone else can open a new PR that is equivalent to .\n/retitle Update links to IANA for Service Name and Transport Protocol Port Number Registry\nI would like to work on this issue. May I assign it to myself?\nAnyone - including you - is welcome to work on this issue! So long as you've you can open a pull request to propose a fix.\nThanks\n/assign\nI have made the PR. I hope this works. If not then will be happy to do the necessary changes.\nHad to close the previous PR because of issues, here is the new one I made.", "commid": "kubernetes_issue_106980", "tokennum": 300}], "negative_passages": []}
{"query_id": "q-en-kubernetes-05cbbb1130d078f0cdb84100ef880fca820725df0ad18718541203fea4a908fe", "query": "}, []string{\"runtime_handler\"}, ) <ins> // RunningPodCount is a gauge that tracks the number of Pods currently running RunningPodCount = metrics.NewGauge( &metrics.GaugeOpts{ Subsystem:      KubeletSubsystem, Name:           \"running_pod_count\", Help:           \"Number of pods currently running\", StabilityLevel: metrics.ALPHA, }, ) // RunningContainerCount is a gauge that tracks the number of containers currently running RunningContainerCount = metrics.NewGaugeVec( &metrics.GaugeOpts{ Subsystem:      KubeletSubsystem, Name:           \"running_container_count\", Help:           \"Number of containers currently running\", StabilityLevel: metrics.ALPHA, }, []string{\"container_state\"}, ) </ins> ) var registerMetrics sync.Once", "positive_passages": [{"docid": "doc-en-kubernetes-3f173d1022a4408031efac17c8299f04d835794ab8a77d69bb7667b0107a08bf", "text": "Some kubelet metrics use non-standard prometheus collectors unnecessarily. Specifically, we have which can be simple gauges. Since we cannot migrate non-standard prometheus collectors using the internal metrics stability framework, we will need to convert these metrics into standard prometheus variants. /sig instrumentation /assign\nGitHub didn't allow me to assign the following users: solodov. Note that only and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : Some kubelet metrics use non-standard prometheus collectors unnecessarily. Specifically, we have which can be simple gauges. Since we cannot migrate non-standard prometheus collectors using the internal metrics stability framework, we will need to convert these metrics into standard prometheus variants. /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\nrecommends that we generate those metrics in the GenericPLEG during the relist. We can generate the data directly from the pods call there ().\nI would be interested to work on this issue if no one else is working on it currently\nGo for it!\n/assign", "commid": "kubernetes_issue_79286", "tokennum": 282}], "negative_passages": []}
{"query_id": "q-en-kubernetes-05d2c7b88b249ee53353f127bb06f7f34ad4fe97c45b5ae5654d00741e51f5ac", "query": "if class.DriverName != ctrl.name { return nil, nil } <del> // Check parameters. claimParameters, classParameters, err := ctrl.getParameters(ctx, claim, class) </del> <ins> // Check parameters. Record event to claim and pod if parameters are invalid. claimParameters, classParameters, err := ctrl.getParameters(ctx, claim, class, true) </ins> if err != nil { <ins> ctrl.eventRecorder.Event(pod, v1.EventTypeWarning, \"Failed\", fmt.Sprintf(\"claim %v: %v\", claim.Name, err.Error())) </ins> return nil, err } return &ClaimAllocation{", "positive_passages": [{"docid": "doc-en-kubernetes-e8eec0a3f7a81297ed919db6952e73e9801661fbfe386a524b19b8189beefe88", "text": "When ResourceClaimParameters or ResourceClassParameters fail validation in resource driver during PodSchedulingContext sync loop, the error is visible only in the events of the PodSchedulingContext. The error should be visible on the object that fails validation as well, ResourceClaim or ResourceClass respectively. Creating ResourceClaim with unsupported parameters' values or unsupported No response <details</details<details</details<details</details<details</details<details</details<details</details\n/assign\n/sig node\n/triage accepted\nKEP:", "commid": "kubernetes_issue_121063", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0607ef810afbbc2b53a979427c675cb70fb854773d13dcc159c5e3d054970e19", "query": "// try set ip families (for missing ip families) // we do it here, since we want this to be visible // even when dryRun == true <del> if err := rs.tryDefaultValidateServiceClusterIPFields(service); err != nil { </del> <ins> if err := rs.tryDefaultValidateServiceClusterIPFields(nil, service); err != nil { </ins> return nil, err }", "positive_passages": [{"docid": "doc-en-kubernetes-572d0164a11730b1ec949ed970afee14cdb12823b4b7a698fae66a86d82f748e", "text": "1) start with a single stack cluster 2) create a PreferDualStack service 3) configure API server with a 2nd service CIDR 4) Confirm the above service is not dual-stack 5) Add a label to the above service 6) Observe that the service becomes dual-stack I think the correct answer is to have a \"repair loop\" that upgrades (and downgrades!) PreferDualStack Services to match the config. I think this is a GA blocker.\n/triage accepted The current thought is: of type with are special new breed of api objects that I don't think we have any similar precedent in the apis, i could be wrong. Their behavior is tied to how the cluster is configured. Thus their behavior must change as the cluster behavior change. a way the user is stating . If it is cluster then i am good with two ClusterIPs. If it is single stack cluster then I am also good with a single ClusterIP. One can assume that if the user was ok was with getting a additional IP when possible then they must be ok with taking it away when it is no longer possible. Based on the above I believe best course of action is create a new repair loop or piggyback on any of the existing (or better: fix it in rest stack during list and get calls). The new logic takes care of matching to the .\nreproducer and regression test if somebody takes this, feel free to add it\nack - Scheduled to tackle 3rd week of May. Will definitely include that patch.", "commid": "kubernetes_issue_101681", "tokennum": 322}], "negative_passages": []}
{"query_id": "q-en-kubernetes-062853fc57e3975866d88f5aca17fbd98ff71683df91d9b50d148fd841a4f32b", "query": "JessieDnsutils           = ImageConfig{e2eRegistry, \"jessie-dnsutils\", \"1.0\", true} Kitten                   = ImageConfig{e2eRegistry, \"kitten\", \"1.0\", true} Liveness                 = ImageConfig{e2eRegistry, \"liveness\", \"1.0\", true} <del> LogsGenerator            = ImageConfig{gcRegistry, \"logs-generator\", \"v0.1.0\", false} </del> <ins> LogsGenerator            = ImageConfig{e2eRegistry, \"logs-generator\", \"1.0\", true} </ins> Mounttest                = ImageConfig{e2eRegistry, \"mounttest\", \"1.0\", true} MounttestUser            = ImageConfig{e2eRegistry, \"mounttest-user\", \"1.0\", true} Nautilus                 = ImageConfig{e2eRegistry, \"nautilus\", \"1.0\", true}", "positive_passages": [{"docid": "doc-en-kubernetes-b17ee1dc189a7b4f3a1873cc63d0b98225c1c3184abd41b75f3a03dd8e681b66", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: Failures - https://k8s- Part of pause is not used properly for tests for other arches than x86. As the current pause image is not a manifest image, so we need to use a different image for different archs like for , for etc.. With this, I'm using logs-generator from repo What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/sig testing\n/assign", "commid": "kubernetes_issue_57588", "tokennum": 189}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0637a2ada9a56a4f9caa078d934299294f513ead878dc68450f51d5d3421a0a1", "query": "execAffinityTestForLBServiceWithTransition(f, cs, svc) }) <del> // TODO: Get rid of [DisabledForLargeClusters] tag when issue #56138 is fixed. </del> // [LinuxOnly]: Windows does not support session affinity. <del> ginkgo.It(\"should have session affinity work for LoadBalancer service with ESIPP off [Slow] [DisabledForLargeClusters] [LinuxOnly]\", func() { </del> <ins> ginkgo.It(\"should have session affinity work for LoadBalancer service with ESIPP off [Slow] [LinuxOnly]\", func() { </ins> // L4 load balancer affinity `ClientIP` is not supported on AWS ELB. e2eskipper.SkipIfProviderIs(\"aws\")", "positive_passages": [{"docid": "doc-en-kubernetes-23d2f241356f8f089aacd04cb02b22714ea2023d38ddcb3dae2268a8e3824c6f", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug This is a followup from filed separately now that we're not tracking this as part of 1.9 release. The tests have been disabled with [DisabledForLargeClusters] tag for now, and this fact will be mentioned in the scalability validation report for v1.9. This issue tracks fixing the test so the tag can be removed and the test ran again in the large cluster. /assign /kind e2e-test-failure\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIs this e2e test still broken?\nSorry for the confusion here. Currently this e2e test is disabled on extra large cluster due to some scalability issues with the load balancer related components. At the moment the issues haven't been completely resolved yet.\nok, adding priority so that I know it's not a 1.13 blocker. /priority important-longterm\ncc - this is why the relevant tests for are not part of the e2e suite.\nThis issue is still valid --- some action items on top of my head: Figure out a plan to make service controller properly handle operations in parallel. Check on the status for cloud providers (especially GCP, which the test ran against) on handling large number of nodes as LB backends. /remove-triage unresolved\nIssues 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 .", "commid": "kubernetes_issue_56138", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0637a2ada9a56a4f9caa078d934299294f513ead878dc68450f51d5d3421a0a1", "query": "execAffinityTestForLBServiceWithTransition(f, cs, svc) }) <del> // TODO: Get rid of [DisabledForLargeClusters] tag when issue #56138 is fixed. </del> // [LinuxOnly]: Windows does not support session affinity. <del> ginkgo.It(\"should have session affinity work for LoadBalancer service with ESIPP off [Slow] [DisabledForLargeClusters] [LinuxOnly]\", func() { </del> <ins> ginkgo.It(\"should have session affinity work for LoadBalancer service with ESIPP off [Slow] [LinuxOnly]\", func() { </ins> // L4 load balancer affinity `ClientIP` is not supported on AWS ELB. e2eskipper.SkipIfProviderIs(\"aws\")", "positive_passages": [{"docid": "doc-en-kubernetes-82e0e423f6c651003322d5e3ca8baa34b91f0522dd0c015fbde1e81f949704e6", "text": "/lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten /lifecycle frozen\n/reopen Reopening as is being reverted in\nReopened this issue. <detailsIn response to : /reopen Reopening as is being reverted in 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\nthese tests are flaking in xref\ncc since these were enabled by\nYeah - though these failures doesn't seem to be scale related, they seem to be test related to me. This basically means nodes without public ips: It's pretty much the same thing as (just for a different test). should be addressing these kinds of errors. [Not a release blocker for sure]\nBTW - has been opened directly for this one.\n... so since is closed, Can we close this and re-enable for large clusters ? (i.e. remove the Tag in that disables this test) ? I'm not up to speed on the history but 2 related notes I came across digging into related test today... 's a couple of TODOs in the code referencing this specific issue, but your above direct issue is now closed, so we can close this as well right?... And if so, we can remove the TODO on the test... -enabling the test ... not sure wether the timing is good right now (given that is open right now , which sparked my stumbling upon this issue :))\nWe tried to enable all of them and that caused us a bunch of issues and those had to be reverted: A couple tests were enabled later in: and those seem fine. The remaining (mostly session-affinity ones) had some issue, which so far we didn't have time to debug and I haven't heard a good explanation why those were failing. It's possible that they were improved with , but I doubt those would really cause the failures we've seen in the past. So until this is debugged (or at least understood) I'm reluctant to enabling them.", "commid": "kubernetes_issue_56138", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-06472af30c5c1fe6cbe371bcaf6f07ceb18fd8e2ee5de8002e8a453e7313b8a7", "query": "return fmt.Errorf(\"timed out waiting for apiserver to be restarted\") } <del> func GetApiserverRestartCount(c clientset.Interface) (int32, error) { </del> <ins> func getApiserverRestartCount(c clientset.Interface) (int32, error) { </ins> label := labels.SelectorFromSet(labels.Set(map[string]string{\"component\": \"kube-apiserver\"})) listOpts := metav1.ListOptions{LabelSelector: label.String()} pods, err := c.CoreV1().Pods(metav1.NamespaceSystem).List(listOpts)", "positive_passages": [{"docid": "doc-en-kubernetes-45049cecee14166a5520f4dc4cbecae5a5a4a44f20c23557ee81cd45d6979f23", "text": "This test is failing in both gce serial suite: http://k8s- /sig network /priority failing-test /priority critical-urgent /kind bug /status approved-for-milestone cc /assign PTAL\nxref\n/milestone v1.10\nthis also fails in http://k8s-\nFailing to connect to Services at all. I can't even ping pod IPs:\nSo I can ping pods same-node and cross-node right up until it kills the apiserver. Rebooting fixes a given node. The apiserver demonstrably comes back - I can query it for info...\n- I could use help - have to shift attention soon.\nFWIW, I am testing on a Calico-enabled node\nI'll take a look at this as well.\nWeird, now even after a reboot, this condition is sticky. I have a cluster in this state, if you want to poke.\nugh, now it is resolved.\nI just repro'ed without the e2e - have a cluster, proved ping works, killed apiserver ping fails.\nInteresting - docker shows the pods not running, but apiserver says they are alive.\nUpdate: docker sees no running pods. API server thinks kubelet is running them. kubelet is getting \"\" from apiserver, even after kubelet restart.\nUpdate and recap: Bring up a cluster Run some pods Prove that pods are running and services work pkill -9 apiserver Wait. Watch kubelets \"lose\" pods that were assigned to them Observe that pods are not running and services do not work Observe that apiserver says the pods are running pkill -9 kubelet Observe that it is still broken kubectl delete one pod Observe that kubelet is fixed for that one pod, but not others Q: Why is kubelet not getting a full listing when it restarts?\nWhat exactly does it mean for it to be fixed for a deleted pod?\nKubelet started running the pod that was deleted - it got the update for that one.\nThe cluster I was testing was a week or 2 old. I built a cluster from HEAD and I can not repro - said the same. Is this test running against head of master?\nI also ran the test manually against my new cluster and it passed\nFWIW I was also unable to reproduce this yesterday on a cluster from HEAD.", "commid": "kubernetes_issue_60761", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-06472af30c5c1fe6cbe371bcaf6f07ceb18fd8e2ee5de8002e8a453e7313b8a7", "query": "return fmt.Errorf(\"timed out waiting for apiserver to be restarted\") } <del> func GetApiserverRestartCount(c clientset.Interface) (int32, error) { </del> <ins> func getApiserverRestartCount(c clientset.Interface) (int32, error) { </ins> label := labels.SelectorFromSet(labels.Set(map[string]string{\"component\": \"kube-apiserver\"})) listOpts := metav1.ListOptions{LabelSelector: label.String()} pods, err := c.CoreV1().Pods(metav1.NamespaceSystem).List(listOpts)", "positive_passages": [{"docid": "doc-en-kubernetes-a335c4245d7a15c6e680ffd06bca4d469bc98515fa6a43286dbf7f7a3bfccc88", "text": "Did some investigations and had some findings for this specific failure: Traced down a bit on the history, the first occurrence was https://k8s- From the , seems suspicious because it modified . Also found reported a relevant symptom: The fix () for that was merged a day ago and may explained why we can't repro from HEAD anymore.\nnice, is this issue reproducible without the fix ()?\nSorry should have had confirmed this, bringing up a cluster now.\nQuick update: I was able to repro the same failure () from HEAD with reverted. Though this test is now flaky on some other errors: https://k8s- https://k8s- They all seem to failed while communicating with apiserver.\nThanks ! So fixed the issue and I am curious about what introduced the issue. Do you happen to know when did this test start to fail? Just trying to find out what went wrong in between. We have some other possibly related issues so finding out the root cause of this one would be super helpful.\n/assign\nThe first occurrence (for that exact failure) I noticed was https://k8s-, which happened on 2018-02-15 09:49 PST.\nYou all rock! I see a couple greens on it now, but still mostly red?\nThe test is now flaky mostly on creating an exec pod after restarting apiserver. Some sample failures: To elaborate a bit more, a snippet of the test procedure is: ssh to master and (sending a SIGTERM) Keep polling on /healthz on apiserver until 200 is returned. Create an exec pod for later steps (and failed on various erros --- EOF, connection refused, apiserver terminating). According to above test failures, my suspicion is that the test is assuming the apiserver is restarted too soon. It is possible that apiserver captured SIGTERM and did a graceful termination, so that polling on /healthz may succeed even in the termination phase. I'm not surprised trying to create a pod via a terminating apiserver will hit those errors. Could anyone confirme the SIGTERM theory?\nSpoke with folks, sounds like after SIGTERM apiserver does wait a bit for remaining requests to finish. I will take a stab to refine the test. cc\nSent .\nTest is now passing on gce but failing on gke.", "commid": "kubernetes_issue_60761", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-06472af30c5c1fe6cbe371bcaf6f07ceb18fd8e2ee5de8002e8a453e7313b8a7", "query": "return fmt.Errorf(\"timed out waiting for apiserver to be restarted\") } <del> func GetApiserverRestartCount(c clientset.Interface) (int32, error) { </del> <ins> func getApiserverRestartCount(c clientset.Interface) (int32, error) { </ins> label := labels.SelectorFromSet(labels.Set(map[string]string{\"component\": \"kube-apiserver\"})) listOpts := metav1.ListOptions{LabelSelector: label.String()} pods, err := c.CoreV1().Pods(metav1.NamespaceSystem).List(listOpts)", "positive_passages": [{"docid": "doc-en-kubernetes-937105a0fb62d0b30f0dcf82865ffcd7dde374c2d2e0895384450ffe72527abd", "text": "Apparently we don't have a way to trigger apiserver restart on gke at this moment. Sending a PR to skip this test on gke.\n[MILESTONENOTIFIER] Milestone Issue Needs Attention Action required: During code freeze, issues in the milestone should be in progress. If this issue is not being actively worked on, please remove it from the milestone. If it is being worked on, please add the label so it can be tracked with other in-flight issues. Note: This issue is marked as , and must be updated every 1 day during code freeze. Example update: <details<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Never automatically move issue out of a release milestone; continually escalate to contributor and SIG through all available channels. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details\nCommented too quick. On gke we do a same-version master upgrade. Will send another fix :/", "commid": "kubernetes_issue_60761", "tokennum": 256}], "negative_passages": []}
{"query_id": "q-en-kubernetes-06e04410d88676f82467fb75190a4d59d2566d0fb09de9f1838bded94e855242", "query": "\"//staging/src/k8s.io/client-go/kubernetes:go_default_library\", \"//staging/src/k8s.io/component-base/config:go_default_library\", \"//staging/src/k8s.io/component-base/metrics/legacyregistry:go_default_library\", <ins> \"//staging/src/k8s.io/component-base/metrics/prometheus/workqueue:go_default_library\", </ins> \"//vendor/k8s.io/klog:go_default_library\", ], )", "positive_passages": [{"docid": "doc-en-kubernetes-532b1798e6d44b2cb365a3a392f829271af9f2d30a6550736395566aab22d4dd", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : kube-controller-manager currently does not expose work queue metrics Why is this needed: queuing delay and queue length are important information to debug control plane performance in large scale cluster /assign zhan849 /sig apps", "commid": "kubernetes_issue_87966", "tokennum": 72}], "negative_passages": []}
{"query_id": "q-en-kubernetes-06edcd9ebe6a3b3b4cef80d21288804a7b8de12d17dcbaca2d5789a6048d8c65", "query": "<del> /* Copyright 2019 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package main import ( \"io\" \"io/ioutil\" \"log\" \"os\" \"os/signal\" \"path/filepath\" \"github.com/pkg/errors\" ) func main() { env := envWithDefaults(map[string]string{ resultsDirEnvKey: defaultResultsDir, skipEnvKey:       defaultSkip, focusEnvKey:      defaultFocus, providerEnvKey:   defaultProvider, parallelEnvKey:   defaultParallel, ginkgoEnvKey:     defaultGinkgoBinary, testBinEnvKey:    defaultTestBinary, }) if err := configureAndRunWithEnv(env); err != nil { log.Fatal(err) } } // configureAndRunWithEnv uses the given environment to configure and then start the test run. // It will handle TERM signals gracefully and kill the test process and will // save the logs/results to the location specified via the RESULTS_DIR environment // variable. func configureAndRunWithEnv(env Getenver) error { // Ensure we save results regardless of other errors. This helps any // consumer who may be polling for the results. resultsDir := env.Getenv(resultsDirEnvKey) defer saveResults(resultsDir) // Print the output to stdout and a logfile which will be returned // as part of the results tarball. logFilePath := filepath.Join(resultsDir, logFileName) logFile, err := os.Create(logFilePath) if err != nil { return errors.Wrapf(err, \"failed to create log file %v\", logFilePath) } mw := io.MultiWriter(os.Stdout, logFile) cmd := getCmd(env, mw) log.Printf(\"Running command:n%vn\", cmdInfo(cmd)) err = cmd.Start() if err != nil { return errors.Wrap(err, \"starting command\") } // Handle signals and shutdown process gracefully. go setupSigHandler(cmd.Process.Pid) return errors.Wrap(cmd.Wait(), \"running command\") } // setupSigHandler will kill the process identified by the given PID if it // gets a TERM signal. func setupSigHandler(pid int) { c := make(chan os.Signal, 1) signal.Notify(c, os.Interrupt) // Block until a signal is received. log.Println(\"Now listening for interrupts\") s := <-c log.Printf(\"Got signal: %v. Shutting down test process (PID: %v)n\", s, pid) p, err := os.FindProcess(pid) if err != nil { log.Printf(\"Could not find process %v to shut down.n\", pid) return } if err := p.Signal(s); err != nil { log.Printf(\"Failed to signal test process to terminate: %vn\", err) return } log.Printf(\"Signalled process %v to terminate successfully.n\", pid) } // saveResults will tar the results directory and write the resulting tarball path // into the donefile. func saveResults(resultsDir string) error { log.Printf(\"Saving results at %vn\", resultsDir) err := tarDir(resultsDir, filepath.Join(resultsDir, resultsTarballName)) if err != nil { return errors.Wrapf(err, \"tar directory %v\", resultsDir) } doneFile := filepath.Join(resultsDir, doneFileName) resultsTarball := filepath.Join(resultsDir, resultsTarballName) resultsTarball, err = filepath.Abs(resultsTarball) if err != nil { return errors.Wrapf(err, \"failed to find absolute path for %v\", resultsTarball) } return errors.Wrap( ioutil.WriteFile(doneFile, []byte(resultsTarball), os.FileMode(0777)), \"writing donefile\", ) } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-b6e1a63eb087c1fdbaf4f20789cf4dc422d7eb3a250658bf836af9dda6b010da", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be modified: image to be based on anything other than Docker Hub sourced Why is this needed: With Docker Hub rate-limit policy in-place, we probably should consider removing this dependency to stay in sync with other base images in Kubernetes project. Folks building their own binaries (i.e. with ) might run into this as well. Notes: Prior discussion happened on An idea from is to use the should probably be renamed to avoid confusion with k/release (h/t Currently, is set to , so migrating to may not be a drop-in move However, , so maybe we don't have to start from scratch /sig testing /area conformance /sig release (cc'ing because builds conformance image, though my quick search seem to show there isn't any build pipelines referencing )\n/assign\ndo we still want to do this? I read somewhere that the images built in Google Cloud are being mirrored from Docker Hub, right? This would mean that the API rate limiting will not hit us any more.\nWomp yeah I think DockerHub rate limit is not really the big motivator at this point. However, I think I still want to consider using distroless / go-runner to build and produce conformance image to reduce the noise from CVE scanning done in downstream places. What do you think?\nYeah I think this seems a valuable addition. Are you planning to work on this issue? :)\nI will, though probably won't start until next week. If you have ideas and would like to start early feel free to go for it! Otherwise, I'd be happy to work on and deliver this.\nThank you Wilson! Feel free to ping again if you need any assistance. /assign\n/triage accepted\none thing I need a little help with is to find a reference for using go-runner image that's used everywhere -- the one that I've found is inside conformance directory which seems to be different from what everyone else is using\nWe maintain a go-runner in k/release:\noops, I forgot to get back on this last week -- I meant to say that I need a reference for image which I can use as , so something like on Dockerfile. Is that a possible thing to do?", "commid": "kubernetes_issue_96692", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-06edcd9ebe6a3b3b4cef80d21288804a7b8de12d17dcbaca2d5789a6048d8c65", "query": "<del> /* Copyright 2019 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package main import ( \"io\" \"io/ioutil\" \"log\" \"os\" \"os/signal\" \"path/filepath\" \"github.com/pkg/errors\" ) func main() { env := envWithDefaults(map[string]string{ resultsDirEnvKey: defaultResultsDir, skipEnvKey:       defaultSkip, focusEnvKey:      defaultFocus, providerEnvKey:   defaultProvider, parallelEnvKey:   defaultParallel, ginkgoEnvKey:     defaultGinkgoBinary, testBinEnvKey:    defaultTestBinary, }) if err := configureAndRunWithEnv(env); err != nil { log.Fatal(err) } } // configureAndRunWithEnv uses the given environment to configure and then start the test run. // It will handle TERM signals gracefully and kill the test process and will // save the logs/results to the location specified via the RESULTS_DIR environment // variable. func configureAndRunWithEnv(env Getenver) error { // Ensure we save results regardless of other errors. This helps any // consumer who may be polling for the results. resultsDir := env.Getenv(resultsDirEnvKey) defer saveResults(resultsDir) // Print the output to stdout and a logfile which will be returned // as part of the results tarball. logFilePath := filepath.Join(resultsDir, logFileName) logFile, err := os.Create(logFilePath) if err != nil { return errors.Wrapf(err, \"failed to create log file %v\", logFilePath) } mw := io.MultiWriter(os.Stdout, logFile) cmd := getCmd(env, mw) log.Printf(\"Running command:n%vn\", cmdInfo(cmd)) err = cmd.Start() if err != nil { return errors.Wrap(err, \"starting command\") } // Handle signals and shutdown process gracefully. go setupSigHandler(cmd.Process.Pid) return errors.Wrap(cmd.Wait(), \"running command\") } // setupSigHandler will kill the process identified by the given PID if it // gets a TERM signal. func setupSigHandler(pid int) { c := make(chan os.Signal, 1) signal.Notify(c, os.Interrupt) // Block until a signal is received. log.Println(\"Now listening for interrupts\") s := <-c log.Printf(\"Got signal: %v. Shutting down test process (PID: %v)n\", s, pid) p, err := os.FindProcess(pid) if err != nil { log.Printf(\"Could not find process %v to shut down.n\", pid) return } if err := p.Signal(s); err != nil { log.Printf(\"Failed to signal test process to terminate: %vn\", err) return } log.Printf(\"Signalled process %v to terminate successfully.n\", pid) } // saveResults will tar the results directory and write the resulting tarball path // into the donefile. func saveResults(resultsDir string) error { log.Printf(\"Saving results at %vn\", resultsDir) err := tarDir(resultsDir, filepath.Join(resultsDir, resultsTarballName)) if err != nil { return errors.Wrapf(err, \"tar directory %v\", resultsDir) } doneFile := filepath.Join(resultsDir, doneFileName) resultsTarball := filepath.Join(resultsDir, resultsTarballName) resultsTarball, err = filepath.Abs(resultsTarball) if err != nil { return errors.Wrapf(err, \"failed to find absolute path for %v\", resultsTarball) } return errors.Wrap( ioutil.WriteFile(doneFile, []byte(resultsTarball), os.FileMode(0777)), \"writing donefile\", ) } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-5d193977829c25729bf0cf7e65192f8c845e68df9f65fd9e6c218e9e5725e8bf", "text": "after searching around, I found this -- going to try and use and see how it works :smile:\nStarted a PR -- plenty of things I'd like to be discussed but we should probably have the discussions there\nIssues 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\n/remove-lifecycle stale there is work in progress", "commid": "kubernetes_issue_96692", "tokennum": 118}], "negative_passages": []}
{"query_id": "q-en-kubernetes-06f98db6afeb9a986b3023d01755ead5e1bbaff37b19367b7174ee8bd9dab63e", "query": "const connectionTimeout = 1 * time.Second <del> type connection interface { serverReachable(address string) bool parseServerList(serverList []string) error CheckEtcdServers() (bool, error) } </del> // EtcdConnection holds the Etcd server list type EtcdConnection struct { ServerList []string", "positive_passages": [{"docid": "doc-en-kubernetes-cc18fa8624c9153eb5caf2824e8d5840bb7b2767a3286fa9c73b8b488eed7889", "text": "/kind bug What happened: Every time a health check is called on the APIServer via the endpoint, an etcd healthcheck is performed. However, as this just starts at the first server in the list passed to the apiserver binary all the healthchecks generate read load on a single etcd member. What you expected to happen: The first server that is checked should either increment (and wrap around) each time or be randomised to spread load around the cluster\n/assign\nI think a random check is ok.\n/sig api-machinery", "commid": "kubernetes_issue_61180", "tokennum": 117}], "negative_passages": []}
{"query_id": "q-en-kubernetes-073868281bf741180f8b32c38ca693a7a0561efba0a8ddf9d0d49edaf6089961", "query": "} missingIPs := desiredIPs.Difference(currentIPs) if len(missingIPs) > 0 { <del> glog.V(2).Infof(\"Current certificate is missing requested IP addresses %v, rotating now\", missingIPs.List()) return time.Now() </del> <ins> glog.V(2).Infof(\"Current certificate is missing requested IP addresses %v\", missingIPs.List()) return false </ins> } <ins> currentOrgs := sets.NewString(m.cert.Leaf.Subject.Organization...) desiredOrgs := sets.NewString(template.Subject.Organization...) missingOrgs := desiredOrgs.Difference(currentOrgs) if len(missingOrgs) > 0 { glog.V(2).Infof(\"Current certificate is missing requested orgs %v\", missingOrgs.List()) return false } } return true } func (m *manager) certSatisfiesTemplate() bool { m.certAccessLock.RLock() defer m.certAccessLock.RUnlock() return m.certSatisfiesTemplateLocked() } // nextRotationDeadline returns a value for the threshold at which the // current certificate should be rotated, 80%+/-10% of the expiration of the // certificate. func (m *manager) nextRotationDeadline() time.Time { // forceRotation is not protected by locks if m.forceRotation { m.forceRotation = false return time.Now() } m.certAccessLock.RLock() defer m.certAccessLock.RUnlock() if !m.certSatisfiesTemplateLocked() { return time.Now() </ins> } notAfter := m.cert.Leaf.NotAfter", "positive_passages": [{"docid": "doc-en-kubernetes-8be37f8ebf3b929ba13e3d88ac8f62b2b24f9ed008212f39c0aaa7e2ec850c18", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: I'm testing the new option in kubernetes 1.12 and it seems that kubelet always requests the signing of a new CSR and tries to rotate the certificates when it is started. This is happening even though there's a valid (brand new) certificate on disk issued by kube-controller-manager. From what I can tell, this is happening because kubelet implements and is set after a successful certificate rotation, but is never persisted to disk. If kubelet is restarted, then the last requested CSR is nil. What you expected to happen: Ideally, kubelet should only request the signing of a new CSR if it doesn't already have a serving certificate or it's about to expire. How to reproduce it (as minimally and precisely as possible): Restart a kubelet instance that had it's serving certificate issued by kube-controller-manager Check and see that it requested the signing of a new CSR Anything else we need to know?: kubelet is being run with . , , and are all omitted to use the default values. The TLS bootstrapping for client certificates is currently not being used--just the bootstrapping for serving certificates. Environment: Kubernetes version: v1.12.0 - built from source at the tag () Cloud provider or hardware configuration: Bare metal OS: CentOS 7.5.1804 Kernel: Install tools: Custom RPMs built from this git repo with no additional patches Others:\n/sig node\n/sig auth\nNot sure if this is the ideal fix, but I've patched it so that it compares the current CSR template to the last requested template only if it doesn't already match the current cert.\ncc\nthanks for the proposed fix. I think it looks good. Could you send a PR? We should also remove entirely and only look at current cert and template. does that sound reasonable?\nSure thing, I'd be happy to do that. EDIT: I will submit a PR after approval from my employer.\nI think that's probably ok, as long as it checks everything we include in the template and we consider a certificate missing anything we request to be cause for re-requesting another cert (an issuer couldn't choose to issue a cert that drops some SANs and us not request another cert) left some comments in\nThis regression is a frequent flyer.", "commid": "kubernetes_issue_69471", "tokennum": 523}], "negative_passages": []}
{"query_id": "q-en-kubernetes-073868281bf741180f8b32c38ca693a7a0561efba0a8ddf9d0d49edaf6089961", "query": "} missingIPs := desiredIPs.Difference(currentIPs) if len(missingIPs) > 0 { <del> glog.V(2).Infof(\"Current certificate is missing requested IP addresses %v, rotating now\", missingIPs.List()) return time.Now() </del> <ins> glog.V(2).Infof(\"Current certificate is missing requested IP addresses %v\", missingIPs.List()) return false </ins> } <ins> currentOrgs := sets.NewString(m.cert.Leaf.Subject.Organization...) desiredOrgs := sets.NewString(template.Subject.Organization...) missingOrgs := desiredOrgs.Difference(currentOrgs) if len(missingOrgs) > 0 { glog.V(2).Infof(\"Current certificate is missing requested orgs %v\", missingOrgs.List()) return false } } return true } func (m *manager) certSatisfiesTemplate() bool { m.certAccessLock.RLock() defer m.certAccessLock.RUnlock() return m.certSatisfiesTemplateLocked() } // nextRotationDeadline returns a value for the threshold at which the // current certificate should be rotated, 80%+/-10% of the expiration of the // certificate. func (m *manager) nextRotationDeadline() time.Time { // forceRotation is not protected by locks if m.forceRotation { m.forceRotation = false return time.Now() } m.certAccessLock.RLock() defer m.certAccessLock.RUnlock() if !m.certSatisfiesTemplateLocked() { return time.Now() </ins> } notAfter := m.cert.Leaf.NotAfter", "positive_passages": [{"docid": "doc-en-kubernetes-1b55ad000b296f12b046608a2d187d8503e900f5b67dbcaa87fc7ef8e9366d19", "text": "I'd love to see an integration test that would catch this (but that shouldn't block a fix).\nThanks for the comments! Now that I have the CLA signed, I'll address those and submit a PR.\nJust submitted the PR:", "commid": "kubernetes_issue_69471", "tokennum": 53}], "negative_passages": []}
{"query_id": "q-en-kubernetes-073ac03f31d14a32ee40e9ef502f5157fd20287f4ebe002365a552415fe84bf5", "query": "if longRunningRequestCheck(req) { return nil, \"\" } <del> return time.After(time.Minute), \"\" </del> <ins> return time.After(globalTimeout), \"\" </ins> } if secureLocation != \"\" {", "positive_passages": [{"docid": "doc-en-kubernetes-98dd9e78520525bf65ff2afc2de58a6375036f9264791def3d02921656a321fe", "text": "this job failed with It seems it is imssing some dependency The job history confirms it is totally broken Originally posted by in\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig testing", "commid": "kubernetes_issue_103738", "tokennum": 114}], "negative_passages": []}
{"query_id": "q-en-kubernetes-073cdf4b4fa530261142a6b8c641d500b181f89ff097be0c02a05d336ae84dbf", "query": "return volumeToMount.GenerateError(\"MapVolume failed\", fmt.Errorf(\"Device path of the volume is empty\")) } <ins> // When kubelet is containerized, devicePath may be a symlink at a place unavailable to // kubelet, so evaluate it on the host and expect that it links to a device in /dev, // which will be available to containerized kubelet. If still it does not exist, // AttachFileDevice will fail. If kubelet is not containerized, eval it anyway. mounter := og.GetVolumePluginMgr().Host.GetMounter(blockVolumePlugin.GetPluginName()) devicePath, err = mounter.EvalHostSymlinks(devicePath) if err != nil { return volumeToMount.GenerateError(\"MapVolume.EvalHostSymlinks failed\", err) } </ins> // Map device to global and pod device map path volumeMapPath, volName := blockVolumeMapper.GetPodDeviceMapPath() mapErr = blockVolumeMapper.MapDevice(devicePath, globalMapPath, volumeMapPath, volName, volumeToMount.Pod.UID)", "positive_passages": [{"docid": "doc-en-kubernetes-226c0928db9d5aa6f1446838b8788eb7c60cd41b1b8246f4bd1a4e2614bb7834", "text": "/kind bug Using , if a block device is symlinked to the discovery directory e.g. , then MapVolume will fail with since the containerized kubelet cannot see the path on host. is mounted by containerized kubelet, so if before we try to map the device we set devicePath to the evaluation of symlink and end up with a devicePath of , containerized kubelet will see the device and successfully map the device. Are there any issues with this solution? This is on Kubernetes 1.10\n/sig storage\nah yes containerized kubelet has many issues when dealing with symlinks. Check out Mounter.GetMode(), it calls a nsenter EvalSymlinks which should be able to do what you need. But actually, one thing to consider, is do you need to do the losetup on the host, or does inside the container work?\nYes it appears to work from inside the container, on the host I run which disappears after I delete the pod using the device. My understanding of running losetup in MapVolume is not that great but I suppose that as long as that /dev/loop0 is created we are fine. Thanks for the quick response, I'll create a PR using that function and tag you\nDoes it create it on the host or in the containerized kubelet? What happens when containerized kubelet is restarted? The purpose of losetup is to do \"refcounting\" on the block device to prevent possible naming collisions when devices are attached/detached under unhealthy conditions. Ie, if a device showed up as /dev/sdb and you gave that to a pod, and then for some reason it become unhealthy and disappeared (while the pod is still running), another device (maybe even another volume type) could get attached to the node and reuse /dev/sdb. Now the pod has access to a device it's not supposed to. With filesystem volumes, the refcounting is done with mount points, but for block device, loopback is the equivalent.\nIt is created on the host (and also visible in the container), and stays around through restart. I understand now, thank you.\nActually after I restart it becomes /vdb instead of /dev/vdb in the losetup output, idk what that is about.", "commid": "kubernetes_issue_65445", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-073cdf4b4fa530261142a6b8c641d500b181f89ff097be0c02a05d336ae84dbf", "query": "return volumeToMount.GenerateError(\"MapVolume failed\", fmt.Errorf(\"Device path of the volume is empty\")) } <ins> // When kubelet is containerized, devicePath may be a symlink at a place unavailable to // kubelet, so evaluate it on the host and expect that it links to a device in /dev, // which will be available to containerized kubelet. If still it does not exist, // AttachFileDevice will fail. If kubelet is not containerized, eval it anyway. mounter := og.GetVolumePluginMgr().Host.GetMounter(blockVolumePlugin.GetPluginName()) devicePath, err = mounter.EvalHostSymlinks(devicePath) if err != nil { return volumeToMount.GenerateError(\"MapVolume.EvalHostSymlinks failed\", err) } </ins> // Map device to global and pod device map path volumeMapPath, volName := blockVolumeMapper.GetPodDeviceMapPath() mapErr = blockVolumeMapper.MapDevice(devicePath, globalMapPath, volumeMapPath, volName, volumeToMount.Pod.UID)", "positive_passages": [{"docid": "doc-en-kubernetes-e6271b0ba1dda755d5bb536a727016a621c7c29c599386bc1e9c22a230980cbf", "text": "There is no such thing as /vdb and /dev/vdb is still intact of course. Seems inconsequential since it is disappearing after all pods using the device are deleted, i.e. it's still serving as a refcounter", "commid": "kubernetes_issue_65445", "tokennum": 55}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0798345d8b65ec0563895e13843885977ba4797bc7b103f7f13d14611e84e319", "query": "// singleCallTimeout is how long to try single API calls (like 'get' or 'list'). Used to prevent // transient failures from failing tests. singleCallTimeout = 5 * time.Minute <ins> // sshBastionEnvKey is the environment variable key for running SSH commands via bastion. sshBastionEnvKey = \"KUBE_SSH_BASTION\" </ins> ) // GetSigner returns an ssh.Signer for the provider (\"gce\", etc.) that can be", "positive_passages": [{"docid": "doc-en-kubernetes-375711dd290c57e850707ef6745091e3080fe654060082beb69e30fe80db0e88", "text": "ci-kubernetes-e2e-gce-scale-correctness Kubernetes e2e suite: [sig-node] SSH should SSH to all nodes and run commands kubetest.Test Jul 10 14:01:51 UTC+0200 Kubernetes e2e suite: [sig-node] SSH should SSH to all nodes and run commands: more . Test /sig node\n/cc\n/triage accepted\nUhhh, this may help here\n/milestone v1.22\n/sig scalability FYI\nI got annoyed that I couldn't click through to see the other logs, so now you can, ref: (spyglass doesn't render build- because it's 500MB, and the limit for rendering is 100MB)\n/assign SIG Scalability chairs/TLs, please find someone to address or call this a non-release-blocking failure\nAssigning to current scalability oncall (): /assign\nThis is sig-node issue - should be addres by SIG-node folks. /sig node\nis being discussed as a fix for this and I'm not sure it's correct\nis it sig scalability's intent that 5k node clusters should support SSH?\nThe SSH test in question passes in the \"default\" job: So the fact that this failure is unique to a scalability job means to me that scalability needs to own at least some part of this\nI did a little bit of digging and ci-kubernetes-e2e-gce-scale-correctness uses option in kubetest, which according to seems to be setting KUBESSHBASTION env. So I believe this is main difference between our scalability job and \"default\".\nDebugging the test in and providing a fix there. The crictl host PR () is doing something different.", "commid": "kubernetes_issue_103688", "tokennum": 400}], "negative_passages": []}
{"query_id": "q-en-kubernetes-07caf30dc2b6535d580fe04eb9a95d9a009b5ca8be700f09117be34953b5f771", "query": "} else if hours < 24*365*2 { return fmt.Sprintf(\"%dd\", hours/24) } else if hours < 24*365*8 { <del> return fmt.Sprintf(\"%dy%dd\", hours/24/365, (hours/24)%365) </del> <ins> dy := int(hours/24) % 365 if dy == 0 { return fmt.Sprintf(\"%dy\", hours/24/365) } return fmt.Sprintf(\"%dy%dd\", hours/24/365, dy) </ins> } return fmt.Sprintf(\"%dy\", int(hours/24/365)) }", "positive_passages": [{"docid": "doc-en-kubernetes-c52a82aeae83a0ba9ff68393d2821e656f88f6d5fbc5e134627056e17acb1808", "text": "What happened: When the duration is exactly 2 years or 3 years, human readable duration is returned as or . But when the duration is exactly 4 years, 5 years, etc, the human readable duration is returned as , , etc. What you expected to happen: The format of an exact year should be consistent. Remove when duration is an exact year: should be should be Check other years... 4, 5, 6, 7... not sure if they also have the problem. How to reproduce it (as minimally and precisely as possible): Because this is time-dependent, it can be difficult to reproduce via the CLI, but you can see the problem illustrated in which shows the current behavior: The and test cases should be changed to want and , and the code should be changed to make that pass. Anything else we need to know?: Note, this is not a problem when the duration is exactly 1 year because the human readable duration is still shown in days. So nothing needs to change to handle the case of exactly 1 year. Environment: Kubernetes version (use ): 1.18 Cloud provider or hardware configuration: n/a OS (e.g: ): n/a Kernel (e.g. ): n/a Install tools: n/a Network plugin and version (if this is a network-related bug): n/a Others: n/a\n/sig api-machinery\n/good-first-issue\nThis request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /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\nCould I pick this up as my first issue?\nAbsolutely. Just use to assign it to yourself.\nAlso I just updated the issue description. Check the other exact years 4, 5, 6, 7 because they might also have the problem, I can't remember. I know 8 and beyond don't have the problem because it just stops showing days after 8 years.\n/assign bitscuit\nmight recall a related PR?", "commid": "kubernetes_issue_89960", "tokennum": 475}], "negative_passages": []}
{"query_id": "q-en-kubernetes-07caf30dc2b6535d580fe04eb9a95d9a009b5ca8be700f09117be34953b5f771", "query": "} else if hours < 24*365*2 { return fmt.Sprintf(\"%dd\", hours/24) } else if hours < 24*365*8 { <del> return fmt.Sprintf(\"%dy%dd\", hours/24/365, (hours/24)%365) </del> <ins> dy := int(hours/24) % 365 if dy == 0 { return fmt.Sprintf(\"%dy\", hours/24/365) } return fmt.Sprintf(\"%dy%dd\", hours/24/365, dy) </ins> } return fmt.Sprintf(\"%dy\", int(hours/24/365)) }", "positive_passages": [{"docid": "doc-en-kubernetes-f6c1495fe924460d9eb2ac0fa6ac2f987b00b8ce0493b8b416038d6dd8a8b830", "text": "(also, I have to leave the pedantic note: a year isn't always 365 days, so it's surprising to me to see the abbreviation exists at all)\nI can't find it. Maybe I was remembering\nYeah it was probably that one. At first I had the tests and the fix. But it sat for a while. I changed it to just the tests of existing behavior so it could be approved more easily. Then I made this issue for the fix but decided it would probably be a good first time issue for someone instead of me doing it.\nso should leap years be considered by the code?\nThere's no way to know how long a year is without knowing the date, so it's not a good unit--in the abstract, there's no way to know if it's a leap year or not. The go language deliberately omits it IIRC. Henry Li <:\nWhat's the intention of HumanDuration? From what I've seen, it is just an approximation of a timestamp solely for humans to understand, so assuming 365 days per year sounds about right to me. This issue is about consistency though, so it could be solved the other way. Instead of abbreviating when it's an exact year (2y, 3y, etc.), exact years could just all have 0d (2y0d, 3y0d, etc.)\nI think it is just used for a ballpark duration. It loses accuracy as the duration increases anyway because it changes the units. I guess my intention for opening the issue was to make it consistent with itself. For example it doesn't say 2d0h or 2h0m, so it should not say 2y0d.\n(FTR I agree that Xy0d looks worse than Xy.) Brian Pursley <:\nHi I have made the required changes. Shall I raise the PR if you haven't started working in it ?\nalready assigned it, so I think it would be good to let him submit the PR, unless he unassigns or does not submit a PR in a reasonable amount of time.\nThanks I was planning on submitting the PR over the weekend\nHello, I am a first timer in open source contribution community. I think I made the required changes for that issue. However, I don't know how assignment rules work.", "commid": "kubernetes_issue_89960", "tokennum": 495}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0803131c5f0120628deab42665abd4e36e55e345aca0173db3f46c410d11b9b3", "query": "package jsonpatch import ( <ins> \"bytes\" </ins> \"encoding/json\" \"fmt\" \"reflect\"", "positive_passages": [{"docid": "doc-en-kubernetes-e51351c05e6844b765acf34eaa6a0653d5a4e3452baed4722f32f9c5caa3ece5", "text": "/kind bug What happened: Wrote a that returned a faulty json patch which specified an our of range index (e.G. when there is only one container). This resulted in the apiserver crashing. Stacktrace: What you expected to happen: No crash /sig-api-machinery\n/sig api-machinery\nThis maybe a bug in . I will follow this question.\nThis bug had been fixed in PR: you can checkout it.\nThanks for your comment but I don't think the linked PR fixed the issue, as it got merged almost a year ago and I am running Kube 1.10.1 which does contain that patch but still panics. Just from quickly looking at the code I the linked PR I believe there are two things wrong: The check if the index is valid only happens when a negative index was given should be\nOnce the PR of is merged I will update kubernetes.\n/kind bug", "commid": "kubernetes_issue_64291", "tokennum": 194}], "negative_passages": []}
{"query_id": "q-en-kubernetes-08079a1a3b9c6995ad34ad1086db607120a55d908c66f497eaa08ce57604a009", "query": "}, } podWithHook := getPodWithHook(\"pod-with-poststart-https-hook\", imageutils.GetPauseImageName(), lifecycle) <ins> // make sure we spawn the test pod on the same node as the webserver. nodeSelection := e2epod.NodeSelection{} e2epod.SetAffinity(&nodeSelection, targetNode) e2epod.SetNodeSelection(&podWithHook.Spec, nodeSelection) </ins> testPodWithHook(podWithHook) }) /*", "positive_passages": [{"docid": "doc-en-kubernetes-52b8d78c627cb5787b11bea8197d2293333b64736fbbbb287954cc79911301a5", "text": "release-master-informing: capz-windows-containerd-masterKubernetes e2e suite: [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop https hook properly [MinimumKubeletVersion:1.23] [NodeConformance] Kubernetes e2e suite: [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart https hook properly [MinimumKubeletVersion:1.23] [NodeConformance] Both the tests have been failing during most of the runs since 20th October Kubernetes e2e suite: [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop https hook properly [MinimumKubeletVersion:1.23] [NodeConformance] | 1m6s -- | -- {Oct 31 18:42:02.425: Timed out after 30.001s. Expected <errors.errorString | 0xc0015283b0: { s: \"failed to match regexp \"GET /echo?msg=prestop\" in output \"I1031 18:41:06. 8988 ] Started HTTP server on port 9090nI1031 18:41:06. 8988 ] Started UDP server on port 9091n\"\", } to be nil failed (0xc000f1d000) +0x469 () +0x335} Kubernetes e2e suite: [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart https hook properly [MinimumKubeletVersion:1.23] [NodeConformance] | 5m11s -- | -- {Oct 31 19:05:50.205: timed out while waiting for pod container-lifecycle-hook-6892/pod-with-poststart-https-hook to be running and ready failed (PodClient).CreateSync(0xc000eb5920, 0x22?) +0x94 (0xc0045e8c00) +0x73 () +0x325} No response_ /sig windows cc\n/triage accepted /cc\nThese failures happen also with Kubernetes master + containerd master with Flannel CNI. Testgrid link:\nI figured out why these new failures appear.", "commid": "kubernetes_issue_113479", "tokennum": 564}], "negative_passages": []}
{"query_id": "q-en-kubernetes-08079a1a3b9c6995ad34ad1086db607120a55d908c66f497eaa08ce57604a009", "query": "}, } podWithHook := getPodWithHook(\"pod-with-poststart-https-hook\", imageutils.GetPauseImageName(), lifecycle) <ins> // make sure we spawn the test pod on the same node as the webserver. nodeSelection := e2epod.NodeSelection{} e2epod.SetAffinity(&nodeSelection, targetNode) e2epod.SetNodeSelection(&podWithHook.Spec, nodeSelection) </ins> testPodWithHook(podWithHook) }) /*", "positive_passages": [{"docid": "doc-en-kubernetes-468407671b0c3bb4dc0cf6c503c02539c6d31cfb69250c40c5c81f059af779f1", "text": "I've submitted the fix via PR\nThis issue is also affecting 1.25 tests: If possible, we should cherry-pick to the release-1.25 branch once it's merged on master.", "commid": "kubernetes_issue_113479", "tokennum": 42}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0809b7205d791058efeec91cfdf48c3e3dc9409006c232df7b4355fad893b1ac", "query": "# github.com/opencontainers/go-digest v1.0.0 ## explicit; go 1.13 github.com/opencontainers/go-digest <del> # github.com/opencontainers/runc v1.1.4 </del> <ins> # github.com/opencontainers/runc v1.1.5 </ins> ## explicit; go 1.16 github.com/opencontainers/runc/libcontainer github.com/opencontainers/runc/libcontainer/apparmor", "positive_passages": [{"docid": "doc-en-kubernetes-3a5f1791fd28a186fcf23c773fa97525e98fb83cc70e7098ac61d449614dcefb", "text": "opencontainers/runc has fixed three CVEs: Latest runc is pulled by k/k Check runc version in file No response n/a n/a <details</details<details</details<details</details<details</details\n/assign /sig security architecture release\n/triage accepted", "commid": "kubernetes_issue_117094", "tokennum": 68}], "negative_passages": []}
{"query_id": "q-en-kubernetes-081f42ec839fa3bf52a339b10ab883b555a0e0aebf1023aed51d215b4c421118", "query": "// WriteStaticPodManifests builds manifest objects based on user provided configuration and then dumps it to disk // where kubelet will pick and schedule them. func WriteStaticPodManifests(cfg *kubeadmapi.MasterConfiguration) error { <ins> volumes := []api.Volume{k8sVolume(cfg)} volumeMounts := []api.VolumeMount{k8sVolumeMount()} if isCertsVolumeMountNeeded() { volumes = append(volumes, certsVolume(cfg)) volumeMounts = append(volumeMounts, certsVolumeMount()) } if isPkiVolumeMountNeeded() { volumes = append(volumes, pkiVolume(cfg)) volumeMounts = append(volumeMounts, pkiVolumeMount()) } </ins> // Prepare static pod specs staticPodSpecs := map[string]api.Pod{ kubeAPIServer: componentPod(api.Container{ Name:          kubeAPIServer, Image:         images.GetCoreImage(images.KubeAPIServerImage, cfg, kubeadmapi.GlobalEnvParams.HyperkubeImage), Command:       getAPIServerCommand(cfg), <del> VolumeMounts:  []api.VolumeMount{certsVolumeMount(), k8sVolumeMount()}, </del> <ins> VolumeMounts:  volumeMounts, </ins> LivenessProbe: componentProbe(8080, \"/healthz\"), Resources:     componentResources(\"250m\"), <del> }, certsVolume(cfg), k8sVolume(cfg)), </del> <ins> }, volumes...), </ins> kubeControllerManager: componentPod(api.Container{ Name:          kubeControllerManager, Image:         images.GetCoreImage(images.KubeControllerManagerImage, cfg, kubeadmapi.GlobalEnvParams.HyperkubeImage), Command:       getControllerManagerCommand(cfg), <del> VolumeMounts:  []api.VolumeMount{certsVolumeMount(), k8sVolumeMount()}, </del> <ins> VolumeMounts:  volumeMounts, </ins> LivenessProbe: componentProbe(10252, \"/healthz\"), Resources:     componentResources(\"200m\"), <del> }, certsVolume(cfg), k8sVolume(cfg)), </del> <ins> }, volumes...), </ins> kubeScheduler: componentPod(api.Container{ Name:          kubeScheduler, Image:         images.GetCoreImage(images.KubeSchedulerImage, cfg, kubeadmapi.GlobalEnvParams.HyperkubeImage),", "positive_passages": [{"docid": "doc-en-kubernetes-aa0efe62d493b3611250d6c4d1b34c71d8fe0e732e78e4445af443d5c2b2f03c", "text": "<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.--What keywords did you search in Kubernetes issues before filing this one? controller /etc/ssl/certs kubeadm /etc/ssl/certs Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT <!-- If this is a BUG REPORT, please: Fill in as much of the template below as you can. If you leave out information, we can't help you as well. If this is a FEATURE REQUEST, please: Describe in detail the feature/behavior/change you'd like to see. In both cases, be ready for followup questions, and please respond in a timely manner. If we can't reproduce a bug or think a feature already exists, we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why. --Kubernetes version (use ): 5 custom built master I also use a custom built hyperkube image instead of the single app images for apiserver, controller, ... Environment: Cloud provider or hardware configuration: azure OS (e.g. from /etc/os-release): CentOS 7.2 Kernel (e.g. ): Linux ma-kub8ms0 3.10.0-327.36.3.el7.x8664 SMP Mon Oct 24 16:09:20 UTC 2016 x8664 x8664 x8664 GNU/Linux Install tools: kubeadm Others: deployed with Azure RM template and ansible What happened: controller is not able to do https, including calls to the Azure RM API What you expected to happen: https should work as usual How to reproduce it (as minimally and precisely as possible): Use kubeadm to install kubernetes on CentOS exec into the controller and try \"curl \" Anything else do we need to know: It looks like caused this issue. On CentOS, I see these files on the host OS: I suspect the symlinks to /etc/pki/... being the problem here, as they are not available inside the hyperkube Debian image. I also tried to verify this with It seems to not be based on Debian and thus gives a different error: I see 2 possible solutions: of host mounting /etc/ssl/certs into the controller pod, the ca certificates could be installed into the image.", "commid": "kubernetes_issue_36150", "tokennum": 529}], "negative_passages": []}
{"query_id": "q-en-kubernetes-081f42ec839fa3bf52a339b10ab883b555a0e0aebf1023aed51d215b4c421118", "query": "// WriteStaticPodManifests builds manifest objects based on user provided configuration and then dumps it to disk // where kubelet will pick and schedule them. func WriteStaticPodManifests(cfg *kubeadmapi.MasterConfiguration) error { <ins> volumes := []api.Volume{k8sVolume(cfg)} volumeMounts := []api.VolumeMount{k8sVolumeMount()} if isCertsVolumeMountNeeded() { volumes = append(volumes, certsVolume(cfg)) volumeMounts = append(volumeMounts, certsVolumeMount()) } if isPkiVolumeMountNeeded() { volumes = append(volumes, pkiVolume(cfg)) volumeMounts = append(volumeMounts, pkiVolumeMount()) } </ins> // Prepare static pod specs staticPodSpecs := map[string]api.Pod{ kubeAPIServer: componentPod(api.Container{ Name:          kubeAPIServer, Image:         images.GetCoreImage(images.KubeAPIServerImage, cfg, kubeadmapi.GlobalEnvParams.HyperkubeImage), Command:       getAPIServerCommand(cfg), <del> VolumeMounts:  []api.VolumeMount{certsVolumeMount(), k8sVolumeMount()}, </del> <ins> VolumeMounts:  volumeMounts, </ins> LivenessProbe: componentProbe(8080, \"/healthz\"), Resources:     componentResources(\"250m\"), <del> }, certsVolume(cfg), k8sVolume(cfg)), </del> <ins> }, volumes...), </ins> kubeControllerManager: componentPod(api.Container{ Name:          kubeControllerManager, Image:         images.GetCoreImage(images.KubeControllerManagerImage, cfg, kubeadmapi.GlobalEnvParams.HyperkubeImage), Command:       getControllerManagerCommand(cfg), <del> VolumeMounts:  []api.VolumeMount{certsVolumeMount(), k8sVolumeMount()}, </del> <ins> VolumeMounts:  volumeMounts, </ins> LivenessProbe: componentProbe(10252, \"/healthz\"), Resources:     componentResources(\"200m\"), <del> }, certsVolume(cfg), k8sVolume(cfg)), </del> <ins> }, volumes...), </ins> kubeScheduler: componentPod(api.Container{ Name:          kubeScheduler, Image:         images.GetCoreImage(images.KubeSchedulerImage, cfg, kubeadmapi.GlobalEnvParams.HyperkubeImage),", "positive_passages": [{"docid": "doc-en-kubernetes-41c6565c36e0283a9e2054713b809a870281386c810e77c1faf5476befe20dbf", "text": "This is already done for hyperkube and would work out of the box when the host mount would be omitted. could try to figure out if /etc/pki should also be host mounted and add this to the controller manifest if required. I'd be happy to provide a fix by myself, I just need to know which solution you would prefer.\nSame problem seems to apply to the apiserver. Not sure however if it actually does https calls.\nimplements solution 2.\nThis issue was moved to kubernetes/kubeadm", "commid": "kubernetes_issue_36150", "tokennum": 111}], "negative_passages": []}
{"query_id": "q-en-kubernetes-082e7d35941be3e789d491496de3cc2d3041fad7b5e8ac402cd9dd1071c07661", "query": "## Protocols for Collaborative Development <del> Please read [this doc](docs/collab.md) for information on how we're running development for the project. </del> <ins> Please read [this doc](docs/devel/collab.md) for information on how we're running development for the project. </ins> ## Adding dependencies", "positive_passages": [{"docid": "doc-en-kubernetes-7c5448078f172c3dba4d1f6f6ed5d66f21d2fc0ea9dd38dbb1ed9b4cc49eea15", "text": "Right now, we have a mixture of user documentation and developer documentation in the top-level directory. We should make it easier to find a just user documentation. Step 1 would be to move developer documentation into a subdir like docs/development or something like that. User docs would stay in the top-level docs dir.\nmove to", "commid": "kubernetes_issue_1797", "tokennum": 71}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0847533c8e9f496eea43d1ad9e11d3121fc423c5c3fd581d7d7f1d0aaa4da72b", "query": "} configurer = NewConfigurer(recorder, nodeRef, nil, testClusterDNS, testClusterDNSDomain, defaultResolvConf) <ins> configurer.getHostDNSConfig = fakeGetHostDNSConfigCustom </ins> for i, pod := range pods { var err error dnsConfig, err := configurer.GetPodDNS(pod)", "positive_passages": [{"docid": "doc-en-kubernetes-5e93ba1a338583c6193506912a68a67fcc908451a37c483694071bc120df2bcb", "text": "When a --resolv-conf (DNS resolver config) is passed to kubelet on a Windows node, the config content is used as part of sandbox initialization (through getHostDNSConfig()). Now with the recent changes (), it seems now to fail with an error like: E0315 10:22:16. 4764 ] \"Error syncing pod, skipping\" err=\"failed to \"CreatePodSandbox\" for \"img-pull-(-b40a-459d-9033-)\" with CreatePodSandboxError: \"Failed to generate sandbox config for pod \"img-pull-(-b40a-459d-9033-)\": Unexpected resolver config value: \"C:etckubernetescni\". Expected \"\" or \"Host\".\"\" pod=\"img-puller-3842/img-pull-\" podUID=-b40a-459d-9033- This is showing on all the runs of GCE testgrid (latest): Reading/using the passed resolv config on Windows Run a Windows pool with DNS resolv config being set as part of kubelet params. No response_ 27 alpha.3 1.27 beta.0 master <detailsGCE </details<details</details<details</details<details</details<details</details\n/triage accepted /milestone v1.27 /sig node /sig network\n/sig windows /cc\n/priority criticial-urgent as this is likely a release blocking\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority criticial-urgent 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\n/priority critical-urgent\nHmm, so you're setting the [1]. This PR introduced the capability to read the DNS config options from the Windows host registries while removing the capability to read from a file, introducing a regression. I've sent a PR addressing this issue: [1]\nIs the file you are pointing to a UNIX-style or something else?\nWas the file changing the behavior of the node?", "commid": "kubernetes_issue_116782", "tokennum": 565}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0847533c8e9f496eea43d1ad9e11d3121fc423c5c3fd581d7d7f1d0aaa4da72b", "query": "} configurer = NewConfigurer(recorder, nodeRef, nil, testClusterDNS, testClusterDNSDomain, defaultResolvConf) <ins> configurer.getHostDNSConfig = fakeGetHostDNSConfigCustom </ins> for i, pod := range pods { var err error dnsConfig, err := configurer.GetPodDNS(pod)", "positive_passages": [{"docid": "doc-en-kubernetes-a55794e1d2c420cf7484c297920657922704eb45d045ae8237364febdd60d634", "text": "Yeah, what used on GCE/GKE, seems to be a Linux-like conf, eg: nameserver 10.128.0.1 search c.<project_name.internal google.internal ` We haven't tried to remove from kubelet to see the behavior.\nThis Issue/PR has been marked as release blocker. Please have the fix merged by eod today otherwise the feature has to be reverted. For the Issue/PR owner: please have a revert/feature disable PR open today in case the fix failed to get in. Thank you! See the -- Kubernetes 1.27 release manager\nI opened up a revert PR in case this PR does not merge by code freeze.\nThanks for the resolution! both 2019 and 2022 grids seems to be back to green now!\nThanks for confirming! I opened to ensure gets updated too", "commid": "kubernetes_issue_116782", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0869e4b2e3bd87e88bd1b86e3f1ee2747488120dc4d6dc5f8ca320365f919b42", "query": "CONTAINER_RUNTIME=${CONTAINER_RUNTIME:-\"docker\"} CONTAINER_RUNTIME_ENDPOINT=${CONTAINER_RUNTIME_ENDPOINT:-\"\"} IMAGE_SERVICE_ENDPOINT=${IMAGE_SERVICE_ENDPOINT:-\"\"} <ins> ENABLE_CRI=${ENABLE_CRI:-\"true\"} </ins> RKT_PATH=${RKT_PATH:-\"\"} RKT_STAGE1_IMAGE=${RKT_STAGE1_IMAGE:-\"\"} CHAOS_CHANCE=${CHAOS_CHANCE:-0.0}", "positive_passages": [{"docid": "doc-en-kubernetes-6248148605ea242e531a4bb3c184ba4481934859726617f8259287d94988a4e9", "text": "When setting for other container runtime, won't start kubelet correctly because cri is disabled : Is there any reason of disabling cri at ? cc\nno, that wasn't supposed to go in. I was testing something and it slipped in accidentally. I'll open a PR to fix.\nAh I see your PR for it. Thanks!", "commid": "kubernetes_issue_42315", "tokennum": 75}], "negative_passages": []}
{"query_id": "q-en-kubernetes-086eef9604a2614cb1940562ab07df053b6265e68437ee83fa88c287bd8f437c", "query": "} type gcepdSource struct { <del> diskName string </del> <ins> pvc *v1.PersistentVolumeClaim </ins> } func initGCEPD() volSource {", "positive_passages": [{"docid": "doc-en-kubernetes-1e6e7a922459aa1ae762d90ee2c0c561e09f7928de6f5ad4ad5cc72934b7dcd1", "text": "New tests for subpath consistently fail in ci-kubernetes-e2e-gce-multizone: https://k8s- /kind bug /sig storage\nIs this a blocker for 1.10?\nI would expect so, yes. /milestone v1.10\nI'm on it /assign\nThe problem is likely due to inline GCE PD volumes not having enough zone information. Considering changing volumes to PVs instead.\nfix was in progress in to change to a PV\n/unassign\n[MILESTONENOTIFIER] Milestone Issue: Up-to-date for process Note: This issue is marked as , and must be updated every 1 day during code freeze. Example update: <details open<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Never automatically move issue out of a release milestone; continually escalate to contributor and SIG through all available channels. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details", "commid": "kubernetes_issue_61101", "tokennum": 262}], "negative_passages": []}
{"query_id": "q-en-kubernetes-089634bdc5e4420857951709f9da55da61312b8541e0fb7f4926475d766f2c01", "query": "rolebindingetcd \"k8s.io/kubernetes/pkg/registry/rbac/rolebinding/etcd\" rolebindingpolicybased \"k8s.io/kubernetes/pkg/registry/rbac/rolebinding/policybased\" utilruntime \"k8s.io/kubernetes/pkg/util/runtime\" <ins> \"k8s.io/kubernetes/pkg/util/wait\" </ins> \"k8s.io/kubernetes/plugin/pkg/auth/authorizer/rbac/bootstrappolicy\" )", "positive_passages": [{"docid": "doc-en-kubernetes-b8d2c0da68304e83135ba886da3cc34043a1f75faa72e9753c7e99fa612dae72", "text": "From etcd3: May need to retry poststarthook a few times to avoid bootstrapping failures like this.", "commid": "kubernetes_issue_39108", "tokennum": 26}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0896a3070e8de53a45ffa287160719e393a8f5c4c33f0f4bf49025daca55100f", "query": "// ListRegisteredFitPredicates returns the registered fit predicates. func ListRegisteredFitPredicates() []string { <del> schedulerFactoryMutex.Lock() defer schedulerFactoryMutex.Unlock() </del> <ins> schedulerFactoryMutex.RLock() defer schedulerFactoryMutex.RUnlock() </ins> var names []string for name := range fitPredicateMap {", "positive_passages": [{"docid": "doc-en-kubernetes-a3c7d28dcea4cbdaac9e2be0d7d2d60e791f1250fe870aa2d2d4769d84db6cae", "text": "What would you like to be : Currently Mutex lock is acquired in for accessing different maps. Some functions only read map entry: We can utilize RWMutex where the above function acquires read lock. Why is this needed: For concurrent calls to IsFitPredicateRegistered / IsPriorityFunctionRegistered, read lock would lower contention.\n/sig scheduling\nfunctions getFitPredicateFunctions, getPriorityFunctionConfigs, ListRegisteredFitPredicates, ListRegisteredPriorityFunctions and GetAlgorithmProvider can also use read lock.\nI happened to raise earlier today. Anyone can finish resting ones.\nGood to know,\nThanks for raising this ! My PR covered and . Feel free to raise another PR to cover others.\nOnce is merged, I will send my PR thanks\nit's merged now.", "commid": "kubernetes_issue_76248", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-089efce9d7c45a7b2ae456a5c542e9fa4df3a112e669470939142aed9d1ab15f", "query": "ctx.init(null, trustAll, new SecureRandom()); URL url = new URL(host + path + serviceName); <ins> logger.info(\"Getting endpoints from \" + url); </ins> HttpsURLConnection conn = (HttpsURLConnection)url.openConnection(); // TODO: Remove this once the CA cert is propogated everywhere, and replace", "positive_passages": [{"docid": "doc-en-kubernetes-600b05087b3e5a02baef82de4ad7a72820fecd2de58582bba171390ab13fae8d", "text": "The namespace seems to be hard coded :\ncc:\nThanks. We can improve it after v1 release.", "commid": "kubernetes_issue_10034", "tokennum": 22}], "negative_passages": []}
{"query_id": "q-en-kubernetes-08bab1e2c4e0889c10f13d756d1dd7951235cf61bea19e23283cb54484dc02b3", "query": "ENV RESULTS_DIR=\"/tmp/results\" ENV KUBECONFIG=\"\" <del> CMD [ \"/bin/bash\", \"-c\", \"/run_e2e.sh\" ] </del> <ins> ENTRYPOINT [ \"kubeconformance\" ] </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-b6e1a63eb087c1fdbaf4f20789cf4dc422d7eb3a250658bf836af9dda6b010da", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be modified: image to be based on anything other than Docker Hub sourced Why is this needed: With Docker Hub rate-limit policy in-place, we probably should consider removing this dependency to stay in sync with other base images in Kubernetes project. Folks building their own binaries (i.e. with ) might run into this as well. Notes: Prior discussion happened on An idea from is to use the should probably be renamed to avoid confusion with k/release (h/t Currently, is set to , so migrating to may not be a drop-in move However, , so maybe we don't have to start from scratch /sig testing /area conformance /sig release (cc'ing because builds conformance image, though my quick search seem to show there isn't any build pipelines referencing )\n/assign\ndo we still want to do this? I read somewhere that the images built in Google Cloud are being mirrored from Docker Hub, right? This would mean that the API rate limiting will not hit us any more.\nWomp yeah I think DockerHub rate limit is not really the big motivator at this point. However, I think I still want to consider using distroless / go-runner to build and produce conformance image to reduce the noise from CVE scanning done in downstream places. What do you think?\nYeah I think this seems a valuable addition. Are you planning to work on this issue? :)\nI will, though probably won't start until next week. If you have ideas and would like to start early feel free to go for it! Otherwise, I'd be happy to work on and deliver this.\nThank you Wilson! Feel free to ping again if you need any assistance. /assign\n/triage accepted\none thing I need a little help with is to find a reference for using go-runner image that's used everywhere -- the one that I've found is inside conformance directory which seems to be different from what everyone else is using\nWe maintain a go-runner in k/release:\noops, I forgot to get back on this last week -- I meant to say that I need a reference for image which I can use as , so something like on Dockerfile. Is that a possible thing to do?", "commid": "kubernetes_issue_96692", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-08bab1e2c4e0889c10f13d756d1dd7951235cf61bea19e23283cb54484dc02b3", "query": "ENV RESULTS_DIR=\"/tmp/results\" ENV KUBECONFIG=\"\" <del> CMD [ \"/bin/bash\", \"-c\", \"/run_e2e.sh\" ] </del> <ins> ENTRYPOINT [ \"kubeconformance\" ] </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-5d193977829c25729bf0cf7e65192f8c845e68df9f65fd9e6c218e9e5725e8bf", "text": "after searching around, I found this -- going to try and use and see how it works :smile:\nStarted a PR -- plenty of things I'd like to be discussed but we should probably have the discussions there\nIssues 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\n/remove-lifecycle stale there is work in progress", "commid": "kubernetes_issue_96692", "tokennum": 118}], "negative_passages": []}
{"query_id": "q-en-kubernetes-091c843d6d413128b565c23d62793a09670622f6c02b95b84b4bf06e34be2682", "query": "}, { \"ImportPath\": \"github.com/json-iterator/go\", <del> \"Rev\": \"f2b4162afba35581b6d4a50d3b8f34e33c144682\" </del> <ins> \"Rev\": \"ab8a2e0c74be9d3be70b3184d9acc634935ded82\" </ins> }, { \"ImportPath\": \"github.com/modern-go/concurrent\",", "positive_passages": [{"docid": "doc-en-kubernetes-0d085a3ee589d9a38ade8c650d9534110265a809ec41b82f41ce81cebea870e6", "text": "is a library yet is is instead of release tag. Please consider vendoring by tag whenever possible. Thanks.\nWe vendored it that way because the commit that fixed a bug (which we needed to be fixed and vendored back in) was This was merged on June 13. The release 1.1.4 () was released on July 1. If we want to update it to 1.1.4, I believe it should be fine. Between the commit we have vendored right now and the latest release, there are only three commits: adds tests merges (?) the case-sensitive fix - I'm not really sure what this commit is doing. fixes renaming when naming strategy is set (looks fine). Also, there are also no licensing changes. opinions?\n/sig api-machinery\n+1 to what said, it was a fire drill and 1.11.0 release was in trouble. Though in hind sight, we should have opened a issue to track that. something better to do next time. cc\nI'm indifferent to updating this. I'm okay with moving up if it doesn't break anything, or I'm fine with leaving things as is. We don't require deps to match semver. We can version out any commit in a deps tree, as we rely on our vendored copy.\nIt is always a good idea to match semver and it should be a default policy. Even if it doesn't matter to you, it should, because it is a best practice. Moreover downstream it matters much more as dependencies may be un-vendored in favour of tested re-usable packages.\n/cc\nIssues 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\nSomeone please take care of this or bot will eventually close this valid issue without action...\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_66422", "tokennum": 501}], "negative_passages": []}
{"query_id": "q-en-kubernetes-091c843d6d413128b565c23d62793a09670622f6c02b95b84b4bf06e34be2682", "query": "}, { \"ImportPath\": \"github.com/json-iterator/go\", <del> \"Rev\": \"f2b4162afba35581b6d4a50d3b8f34e33c144682\" </del> <ins> \"Rev\": \"ab8a2e0c74be9d3be70b3184d9acc634935ded82\" </ins> }, { \"ImportPath\": \"github.com/modern-go/concurrent\",", "positive_passages": [{"docid": "doc-en-kubernetes-3d634ec524d1253e3e5f3f0b99b6d74925e6b15b79d6d989e49b255bf837eee0", "text": "/lifecycle rotten\n/lifecycle rotten\n/remove-lifecycle rotten PR open (thanks,\noops! sorry, I meant to remove it. thanks!\nThanks.\nplease do feel free to open issues/prs of this sort early in the release cycle, so we can work through things needed well before the milestones/freeze etc. we are getting some heat about updating dependencies and we kind of settled on some guidelines here: if you think that needs updating, we could definitely debate that as well :) (on a PR against that doc)\nit have nothing to do with release cycle or justification for upgrade if/when dependency has been vendored incorrectly. It is basically a vendoring bug. No debate is necessary although that kind of issues usually meet some resistance and even hostility here... Bugs are filed when they are discovered, regardless of release cycle. It would be wrong to sit on the bug without reporting it in order to synchronise with release cycle.", "commid": "kubernetes_issue_66422", "tokennum": 200}], "negative_passages": []}
{"query_id": "q-en-kubernetes-091f5be6409cc88a58cd3be145c19d9e108e4522746270ed889860b62f315c06", "query": "<del> apiVersion: extensions/v1beta1 </del> <ins> apiVersion: networking.k8s.io/v1beta1 </ins> kind: Ingress metadata: name: multiple-certs", "positive_passages": [{"docid": "doc-en-kubernetes-bb7c21eb048735f6a80e177a210d26530b5959539babed9d56a66ccfff61adf4", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: Which test(s) are failing: Since when has it been failing: Testgrid link: https://k8s- Reason for failure: Anything else we need to know: /cc /milestone v1.19 /priority important-soon /sig network\nRef:\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nmy fu points me to this commit [] Fix multiple conversion tests that belongs to this PR , that seems related can you confirm if that PR is causing this test to fail? (should we gate on this test?)\nYes, that PR is related to the failure. The test utility is trying to convert extensions/v1beta1 data read from various files directly to a go type. This was never a valid thing to do, and happened to silently succeed because the two structs had an identical structure. This is exactly the type of bug was designed to flush out\nthe correct fix is to update the test/e2e/testing- files to\n/assign\nIt was my PR that broke this - I can also fix that.\nThanks, o it was the commit that was good but the test that was wrong :upsidedownface: , At least I got right the commit :sweat_smile:\nis out for review (talked with offline, he was aware that I'll send that out)", "commid": "kubernetes_issue_90451", "tokennum": 318}], "negative_passages": []}
{"query_id": "q-en-kubernetes-09367ee2d9d6d91720a1f6fc123177b28691d6b051ee3bd4c5af5bf1bebd93ae", "query": "return pullSecrets } <del> // Returns true if pod is in the terminated state (\"Failed\" or \"Succeeded\"). </del> <ins> // podIsTerminated returns true if pod is in the terminated state (\"Failed\" or \"Succeeded\"). </ins> func (kl *Kubelet) podIsTerminated(pod *v1.Pod) bool { <del> var status v1.PodStatus </del> // Check the cached pod status which was set after the last sync. status, ok := kl.statusManager.GetPodStatus(pod.UID) if !ok {", "positive_passages": [{"docid": "doc-en-kubernetes-05fa43eac8c17b852831e6979a2d93db8ab276262ace733bb7d146872dff7701", "text": "pointed out that for scheduling and kubelet admission, we should consider resources of terminated-but-not-yet-deleted pods to still be in use, because it may take an arbitrary amount of time for the system to deallocate resources. We didn't check to see if this is currently how it is implemented or not. cc/ /sig scheduling\ncc/\nFor terminated-but-not-yet-deleted & phase is case, the Pod is still in scheduler's cache, so it's handled well in scheduler; the Pod will be removed from cache when it's deleted. But in kubelet, it filtered terminated-but-not-yet-deleted out () when using scheduler.predicates. The option in my mind is to ~pass all Pods (including terminated-but-not-yet-deleted) to each admin, and let each admin decide whether filter terminated-but-not-yet-deleted out~ only filter out finished (Failed or Succeed) pods for Admits.\nIn -, it already consider by . So both scheduler & kubelet handles terminated-but-not-yet-deleted pods well.\nGreat, thanks for looking into it!\nshould this issue be closed then?\nI think so.\nJust to clarify: Kubelet correctly accounts the resources used by terminated-but-not-yet-deleted pods, i.e, kubelet does not count the resource usage of those pods towards total usage on the node. Scheduler, however, does not do the same. Scheduler waits for a pod to be deleted, and then it deducts its resource request from the associated node total usage. Upon deletion of a pod, scheduler is notified and acts: So, scheduler and kubelet behaviors are not exactly the same. I am not sure if scheduler can receive an event when a pod's container status changes. If it could, we could make the logic the same as that of Kubelet.\nI guess the current behavior is OK because it is conservative (scheduler considers the resources to be in use even though kubelet considers them free). And actually it seems that scheduler is more \"correct\" than kubelet, since the resources really aren't usable until the pod is deleted, right? (IIUC that was Vish's original point)\nI agree. The current behavior is correct, but a bit conservative. Basically, the scheduler side is more conservative and waits until a pod is deleted from the cache before considering its resources released.", "commid": "kubernetes_issue_47867", "tokennum": 529}], "negative_passages": []}
{"query_id": "q-en-kubernetes-09367ee2d9d6d91720a1f6fc123177b28691d6b051ee3bd4c5af5bf1bebd93ae", "query": "return pullSecrets } <del> // Returns true if pod is in the terminated state (\"Failed\" or \"Succeeded\"). </del> <ins> // podIsTerminated returns true if pod is in the terminated state (\"Failed\" or \"Succeeded\"). </ins> func (kl *Kubelet) podIsTerminated(pod *v1.Pod) bool { <del> var status v1.PodStatus </del> // Check the cached pod status which was set after the last sync. status, ok := kl.statusManager.GetPodStatus(pod.UID) if !ok {", "positive_passages": [{"docid": "doc-en-kubernetes-0f8f1ec2a7e3c6ce351bcfa7358868ba1886341c66515327ef662e361aa12de0", "text": "That said, I believe resources of terminated-but-not-deleted pods are usable on nodes (should be verified). So, the current behavior is a bit less than ideal in terms of efficiency, but AFAIK the duration between termination and deletion is only a few seconds. So, it may not be worth optimizing.\nI thought was saying the opposite (see my first entry in this issue). Maybe he can clarify.", "commid": "kubernetes_issue_47867", "tokennum": 91}], "negative_passages": []}
{"query_id": "q-en-kubernetes-094870966e6e1a2c88b39e37a663eb50014231283c09f81d5d847e2d3a5b94b2", "query": "} } <ins> func isCertsVolumeMountNeeded() bool { // Always return true for now. We may add conditional logic here for images which do not require host mounting /etc/ssl // hyperkube for example already has valid ca-certificates installed return true } </ins> // certsVolume exposes host SSL certificates to pod containers. func certsVolume(cfg *kubeadmapi.MasterConfiguration) api.Volume { return api.Volume{", "positive_passages": [{"docid": "doc-en-kubernetes-aa0efe62d493b3611250d6c4d1b34c71d8fe0e732e78e4445af443d5c2b2f03c", "text": "<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.--What keywords did you search in Kubernetes issues before filing this one? controller /etc/ssl/certs kubeadm /etc/ssl/certs Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT <!-- If this is a BUG REPORT, please: Fill in as much of the template below as you can. If you leave out information, we can't help you as well. If this is a FEATURE REQUEST, please: Describe in detail the feature/behavior/change you'd like to see. In both cases, be ready for followup questions, and please respond in a timely manner. If we can't reproduce a bug or think a feature already exists, we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why. --Kubernetes version (use ): 5 custom built master I also use a custom built hyperkube image instead of the single app images for apiserver, controller, ... Environment: Cloud provider or hardware configuration: azure OS (e.g. from /etc/os-release): CentOS 7.2 Kernel (e.g. ): Linux ma-kub8ms0 3.10.0-327.36.3.el7.x8664 SMP Mon Oct 24 16:09:20 UTC 2016 x8664 x8664 x8664 GNU/Linux Install tools: kubeadm Others: deployed with Azure RM template and ansible What happened: controller is not able to do https, including calls to the Azure RM API What you expected to happen: https should work as usual How to reproduce it (as minimally and precisely as possible): Use kubeadm to install kubernetes on CentOS exec into the controller and try \"curl \" Anything else do we need to know: It looks like caused this issue. On CentOS, I see these files on the host OS: I suspect the symlinks to /etc/pki/... being the problem here, as they are not available inside the hyperkube Debian image. I also tried to verify this with It seems to not be based on Debian and thus gives a different error: I see 2 possible solutions: of host mounting /etc/ssl/certs into the controller pod, the ca certificates could be installed into the image.", "commid": "kubernetes_issue_36150", "tokennum": 529}], "negative_passages": []}
{"query_id": "q-en-kubernetes-094870966e6e1a2c88b39e37a663eb50014231283c09f81d5d847e2d3a5b94b2", "query": "} } <ins> func isCertsVolumeMountNeeded() bool { // Always return true for now. We may add conditional logic here for images which do not require host mounting /etc/ssl // hyperkube for example already has valid ca-certificates installed return true } </ins> // certsVolume exposes host SSL certificates to pod containers. func certsVolume(cfg *kubeadmapi.MasterConfiguration) api.Volume { return api.Volume{", "positive_passages": [{"docid": "doc-en-kubernetes-41c6565c36e0283a9e2054713b809a870281386c810e77c1faf5476befe20dbf", "text": "This is already done for hyperkube and would work out of the box when the host mount would be omitted. could try to figure out if /etc/pki should also be host mounted and add this to the controller manifest if required. I'd be happy to provide a fix by myself, I just need to know which solution you would prefer.\nSame problem seems to apply to the apiserver. Not sure however if it actually does https calls.\nimplements solution 2.\nThis issue was moved to kubernetes/kubeadm", "commid": "kubernetes_issue_36150", "tokennum": 111}], "negative_passages": []}
{"query_id": "q-en-kubernetes-094973dee423cb76c8061c047828274e4cac927c51cf1ecbec0afbe115997599", "query": "package azure import ( <ins> \"context\" </ins> \"fmt\" \"reflect\" \"testing\"", "positive_passages": [{"docid": "doc-en-kubernetes-4ac48b480971aca26f0a1896d0fa1bdd3b9ed6e78abeeb1cea4ee05f140cc101", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: controller-manager is stuck in deleting an incorrectly configured LB type service. it cannot be recovered until restarted. What you expected to happen: controller-manager should recover. At least it should allow us to create the service without restarting it. How to reproduce it (as minimally and precisely as possible): put a random IP in above yaml and make sure the resource group doen't exist. Anything else we need to know?: Environment: Kubernetes version (use ): 1.12.4 Cloud provider or hardware configuration: AKS OS (e.g: ): Kernel (e.g. ): Install tools: Others:\n/sig azure\nI also want to add that the above repro is stuck in 403. It's possible for it to be stuck in 404 as well when the SP has the right permission.\nCan you share the log for 404?\nThanks for reporting the issue. /assign Do you mean other services couldn't be configured when this happens?\ncorrect.\nFYI, we had the same issue when the Idle Timeout annotation was set to \"3\" which isn't a supported case. Will this PR also cover this edge case ?\nUnfortunately , this is still not fixed. The idle timeout is not 403 or 404. We need another fix for this (and possibly more for other annotations)", "commid": "kubernetes_issue_75198", "tokennum": 337}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0971a11db3f66d48166a682d294bb90ea5174409a7b4d2964447b99d1ce2b1b9", "query": "<del> apiVersion: v1 kind: Service metadata: name: elasticsearch labels: component: elasticsearch spec: type: LoadBalancer selector: component: elasticsearch ports: - name: http port: 9200 protocol: TCP - name: transport port: 9300 protocol: TCP </del>", "positive_passages": [{"docid": "doc-en-kubernetes-5fef938b0452d0f6b58e576cd11f17813fb6d6b970f83a7868d905b7784a5e39", "text": "Presently, the elasticsearch example Kubernetes configurations target elasticsearch v1.7.1, which is quite old. As of this writing, the latest elasticsearch release is v5.6.2, with many deployment changes since then. Could the elasticsearch examples be updated to target the v5 series of elasticsearch? See for a more up to date reference configuration.\ncc\nhey it's been a long while since I last contributed to the docs. i can do it soon but i need pointers on how to properly do it.\nhey, so we need to update the stuff under examples/elasticsearch/ *&repos=kubernetes So basically update the images, yaml files etc and test that everything works (and submit a PR)\n/sig testing\nAh, so there's no documentation updates anymore. OK I'll take care of it, assign it to me.\nIssues 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\nGitHub didn't allow me to assign the following users: me. Note that only and repo collaborators can be assigned. <detailsIn response to : /assign me 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\n/assign pires\n/remove-lifecycle stale\nit seems that the example moved to I am now reading that repo guidelines and will update this there. I'll also open a PR that cleans this folder in the current repo and closes this issue.", "commid": "kubernetes_issue_53142", "tokennum": 387}], "negative_passages": []}
{"query_id": "q-en-kubernetes-098aafb978b6878440d52bf74e3ca793f76de8a5ebc4a75ee820c0af0b0c487d", "query": "// If selectedNode is set, the driver must attempt to allocate for that // node. If that is not possible, it must return an error. The // controller will call UnsuitableNodes and pass the new information to <del> // the scheduler, which then will lead to selecting a diffent node </del> <ins> // the scheduler, which then will lead to selecting a different node </ins> // if the current one is not suitable. // // The Claim, ClaimParameters, Class, ClassParameters fields of \"claims\" parameter", "positive_passages": [{"docid": "doc-en-kubernetes-e8eec0a3f7a81297ed919db6952e73e9801661fbfe386a524b19b8189beefe88", "text": "When ResourceClaimParameters or ResourceClassParameters fail validation in resource driver during PodSchedulingContext sync loop, the error is visible only in the events of the PodSchedulingContext. The error should be visible on the object that fails validation as well, ResourceClaim or ResourceClass respectively. Creating ResourceClaim with unsupported parameters' values or unsupported No response <details</details<details</details<details</details<details</details<details</details<details</details\n/assign\n/sig node\n/triage accepted\nKEP:", "commid": "kubernetes_issue_121063", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0995d2b6be9e7d82400e300ca29385e5b3acbbbb999c83d1291bf25b7d2532a7", "query": "} } <ins> func TestMatchImageTagOrSHA(t *testing.T) { for _, testCase := range []struct { Inspected dockertypes.ImageInspect Image     string Output    bool }{ { Inspected: dockertypes.ImageInspect{RepoTags: []string{\"ubuntu:latest\"}}, Image:     \"ubuntu\", Output:    true, }, { Inspected: dockertypes.ImageInspect{RepoTags: []string{\"ubuntu:14.04\"}}, Image:     \"ubuntu:latest\", Output:    false, }, { Inspected: dockertypes.ImageInspect{ ID: \"sha256:2208f7a29005d226d1ee33a63e33af1f47af6156c740d7d23c7948e8d282d53d\", }, Image:  \"myimage@sha256:2208f7a29005d226d1ee33a63e33af1f47af6156c740d7d23c7948e8d282d53d\", Output: true, }, { Inspected: dockertypes.ImageInspect{ ID: \"sha256:2208f7a29005d226d1ee33a63e33af1f47af6156c740d7d23c7948e8d282d53d\", }, Image:  \"myimage@sha256:2208f7a29005\", Output: false, }, { Inspected: dockertypes.ImageInspect{ ID: \"sha256:2208f7a29005d226d1ee33a63e33af1f47af6156c740d7d23c7948e8d282d53d\", }, Image:  \"myimage@sha256:2208\", Output: false, }, } { match := matchImageTagOrSHA(testCase.Inspected, testCase.Image) assert.Equal(t, testCase.Output, match, testCase.Image+\" is not a match\") } } </ins> func TestApplyDefaultImageTag(t *testing.T) { for _, testCase := range []struct { Input  string", "positive_passages": [{"docid": "doc-en-kubernetes-73e94f1f9679cf5fca554c149f1c357d9b16156cc7199a4d351eb3b22980b589", "text": "We had rather strange case today when after rolling update one of the kubelet's started wrong container. For this specific replicationcontroller we are using What happened was that after rolling-update when i started to debug the issue i discovered that one of the kubelet's did not pull the image: When looking into what image it actually started i saw: When checking from the actual node i saw this It seems that instead of starting myimage with tag 2208 kubelet started image tagged as 1393 since the docker image id starts with 2208.", "commid": "kubernetes_issue_30355", "tokennum": 119}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0996a78a87754a5bece303db7fe6ef873f30836fad9a65fe7d36370dc25c38de", "query": "// Volume is added to asw, volume should be reported as attached to the node. waitForVolumeAddedToNode(t, generatedVolumeName, nodeName1, asw) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <del> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw) </del> <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw, volumeAttachedCheckTimeout) </ins> // Delete the pod dsw.DeletePod(types.UniquePodName(podName1), generatedVolumeName, nodeName1)", "positive_passages": [{"docid": "doc-en-kubernetes-dc8aac09a0e4bb26f9dc5f50aef7f845ea9d7c4b925d34b9f6eda044925f80f5", "text": "TestRunOneVolumeDetachFailNodeWithReadWriteOnce 4 times since 03-19 23:00 PDT, intermittently ! https://k8s- Still investigating whether this is a tolerable flake or not with more history than testgrid view, or otherwise would appreciate input from anyone with expertise in this test, especially as regards to whether this should be a blocker for tomorrows beta cut. maybe: /sig storage /sig testing\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nis already open for this, looks like it is attempting to fix it\nthank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. /close\nClosing this issue. <detailsIn response to : thank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. 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", "commid": "kubernetes_issue_116774", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0996a78a87754a5bece303db7fe6ef873f30836fad9a65fe7d36370dc25c38de", "query": "// Volume is added to asw, volume should be reported as attached to the node. waitForVolumeAddedToNode(t, generatedVolumeName, nodeName1, asw) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <del> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw) </del> <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw, volumeAttachedCheckTimeout) </ins> // Delete the pod dsw.DeletePod(types.UniquePodName(podName1), generatedVolumeName, nodeName1)", "positive_passages": [{"docid": "doc-en-kubernetes-aef7ec00dc93616f97177ca3d23f28217445848b34c429e5746962ea28329f43", "text": "pull-kubernetes-unit TestRunOneVolumeDetachFailNodeWithReadWriteOnce Jan 7th, 2022 Check volume <fake-plugin/volume-nameis reported as attached to node <fail-detach-node, got false, expected true No response_ /sig storage\n/cc\nthis is the top unit test flake according to\ncc\nThe 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]:\nI think this test is no longer flaky by checking the test grid, close it now.\nUnfortunately this does still seem to be flaky: Here was the output from : /reopen\nReopened this issue. <detailsIn response to : Unfortunately this does still seem to be flaky: 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\n/remove-lifecycle stale\nstill the case\nHow about adding some logging to help troubleshoot this? I looked at it a little, but it is hard to tell which part of the test is failing. PR\n/\nThis is still happening\n/triage accepted\nFrom the logs, in the OneVolumeDetachFailNodeWithReadWriteOnce test, succeeded, but the next verification failed. In verifyVolumeAttachedToNode, the attachState is from calling and within asw, it calls . In verifyVolumeReportedAsAttachedToNode, the volumes are obtained from calling , it seems that the node is not in asw.nodesToUpdateStatusFor at this step. Cannot reproduce locally. I tried to run the test 100 times locally with debug.Stack()... 3 * 100 times all passed.\nTried to run stress test on my linux machine as well but still cannot reproduce. Command: Result: Also tried running n process in parallel. Command: Result:\nIt seems like it happens more frequently.", "commid": "kubernetes_issue_107414", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0996a78a87754a5bece303db7fe6ef873f30836fad9a65fe7d36370dc25c38de", "query": "// Volume is added to asw, volume should be reported as attached to the node. waitForVolumeAddedToNode(t, generatedVolumeName, nodeName1, asw) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <del> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw) </del> <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw, volumeAttachedCheckTimeout) </ins> // Delete the pod dsw.DeletePod(types.UniquePodName(podName1), generatedVolumeName, nodeName1)", "positive_passages": [{"docid": "doc-en-kubernetes-62e47fd83b7fc1cc39259be1688a9f133b9cd2dc48247eb5d858fae7fd13955b", "text": "But I may have no time to dig into the cause. Let's see.\ncc as the test author.\nThe problem is that this test has a lot of dependency on the sleeps that are hardcoded with a very narrow scope, but our CI seems to be able to stress it much more. As soon as you slightly change one of the sleep duration it starts to flake locally The test can not make an assumption that timing is perfect, even more in the sub second range can someone in sig-storage review this test and make it less dependant on those tight sleeps?\nAccording to most failures, it failed at Line 660. Let me run some stress locally. with 250ms sleep with 100ms sleep\nI agree this test case is too brittle due to its specific timing dependencies. To fix this, I suggest reworking the test case to: 1) Add retry with timeout to wait for final conditions 2) Remove the intermediate timing-based state transition checks. Instead, we can keep track of state transitions in the Fakes and validate those stats. wdyt?\nFriendly ping from 1.27 CI Signal that this test is still a noisy flake on the master-blocking dashboard as CI Signal has flagged it in and", "commid": "kubernetes_issue_107414", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-09a2b5d80feff9e0ef019e5da82c93b3af86cc7ac320eeac89002a821d137c74", "query": "By(\"verifying service-disabled is still not up\") framework.ExpectNoError(framework.VerifyServeHostnameServiceDown(cs, host, svcDisabledIP, servicePort)) }) <ins> It(\"should be rejected when no endpoints exist\", func() { namespace := f.Namespace.Name serviceName := \"no-pods\" jig := framework.NewServiceTestJig(cs, serviceName) nodes := jig.GetNodes(framework.MaxNodesForEndpointsTests) labels := map[string]string{ \"nopods\": \"nopods\", } port := 80 ports := []v1.ServicePort{{ Port:       int32(port), TargetPort: intstr.FromInt(80), }} By(\"creating a service with no endpoints\") _, err := jig.CreateServiceWithServicePort(labels, namespace, ports) if err != nil { framework.Failf(\"Failed to create service: %v\", err) } nodeName := nodes.Items[0].Name podName := \"execpod-noendpoints\" By(fmt.Sprintf(\"creating %v on node %v\", podName, nodeName)) execPodName := framework.CreateExecPodOrFail(f.ClientSet, namespace, podName, func(pod *v1.Pod) { pod.Spec.NodeName = nodeName }) execPod, err := f.ClientSet.CoreV1().Pods(namespace).Get(execPodName, metav1.GetOptions{}) framework.ExpectNoError(err) serviceAddress := net.JoinHostPort(serviceName, strconv.Itoa(port)) framework.Logf(\"waiting up to %v wget %v\", framework.KubeProxyEndpointLagTimeout, serviceAddress) cmd := fmt.Sprintf(`wget -T 3 -qO- %v`, serviceAddress) By(fmt.Sprintf(\"hitting service %v from pod %v on node %v\", serviceAddress, podName, nodeName)) expectedErr := \"connection refused\" if pollErr := wait.PollImmediate(framework.Poll, framework.KubeProxyEndpointLagTimeout, func() (bool, error) { _, err := framework.RunHostCmd(execPod.Namespace, execPod.Name, cmd) if err != nil { if strings.Contains(strings.ToLower(err.Error()), expectedErr) { framework.Logf(\"error contained '%s', as expected: %s\", expectedErr, err.Error()) return true, nil } else { framework.Logf(\"error didn't contain '%s', keep trying: %s\", expectedErr, err.Error()) return false, nil } } else { return true, errors.New(\"expected wget call to fail\") } }); pollErr != nil { Expect(pollErr).NotTo(HaveOccurred()) } }) </ins> }) // TODO: Get rid of [DisabledForLargeClusters] tag when issue #56138 is fixed.", "positive_passages": [{"docid": "doc-en-kubernetes-12565e8dbeb532aef2fc81c48820204edabd27cddb58e2c25eb51a8447b79e73", "text": "introduced somethng that really should be e2e tested.\nWould be nice to get this in in the 2 weeks we have after 1.2 branch cut, if no more flakes crop up (but I'm not too optimistic). Bumping to next-release.\n/sig network I'm assuming sig-network owns kube-proxy\nI thought I noted a change related to this recently, but I may be mistaken.\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\n/lifecycle frozen /remove-lifecycle stale\n/remove-lifecycle rotten\nGoing to try to take this on.\nthanks!\nI've had some trouble constructing a test for this. should I determine the timeout? There doesn't appear to be an existing mechanism for waiting for service creation. seem to time out rather than be refused - I'm confused by this, as it seems to be the opposite of the intended behavior.\ncan look at the endpoints + wait for longer than kube-proxy sync time. refused means packets got to their destination but there was nothing listening there. If traffic is blocked, then you will just get a timeout.\nI created a service with no matching pods to test manually outside of the e2e suite. # curl test-api curl: (7) Failed to connect to athena-api port 80: Connection timed out # curl --connect-timeout 8 test-api curl: (28) Connection timed out after 8000 milliseconds Looking back at original example in I see that I'm getting the \"before\" behaviour. An iptables REJECT should send a denial, not a timeout. Am I looking at the wrong thing here? To me this looks like a regression, but I don't think that's likely.", "commid": "kubernetes_issue_20767", "tokennum": 514}], "negative_passages": []}
{"query_id": "q-en-kubernetes-09a2b5d80feff9e0ef019e5da82c93b3af86cc7ac320eeac89002a821d137c74", "query": "By(\"verifying service-disabled is still not up\") framework.ExpectNoError(framework.VerifyServeHostnameServiceDown(cs, host, svcDisabledIP, servicePort)) }) <ins> It(\"should be rejected when no endpoints exist\", func() { namespace := f.Namespace.Name serviceName := \"no-pods\" jig := framework.NewServiceTestJig(cs, serviceName) nodes := jig.GetNodes(framework.MaxNodesForEndpointsTests) labels := map[string]string{ \"nopods\": \"nopods\", } port := 80 ports := []v1.ServicePort{{ Port:       int32(port), TargetPort: intstr.FromInt(80), }} By(\"creating a service with no endpoints\") _, err := jig.CreateServiceWithServicePort(labels, namespace, ports) if err != nil { framework.Failf(\"Failed to create service: %v\", err) } nodeName := nodes.Items[0].Name podName := \"execpod-noendpoints\" By(fmt.Sprintf(\"creating %v on node %v\", podName, nodeName)) execPodName := framework.CreateExecPodOrFail(f.ClientSet, namespace, podName, func(pod *v1.Pod) { pod.Spec.NodeName = nodeName }) execPod, err := f.ClientSet.CoreV1().Pods(namespace).Get(execPodName, metav1.GetOptions{}) framework.ExpectNoError(err) serviceAddress := net.JoinHostPort(serviceName, strconv.Itoa(port)) framework.Logf(\"waiting up to %v wget %v\", framework.KubeProxyEndpointLagTimeout, serviceAddress) cmd := fmt.Sprintf(`wget -T 3 -qO- %v`, serviceAddress) By(fmt.Sprintf(\"hitting service %v from pod %v on node %v\", serviceAddress, podName, nodeName)) expectedErr := \"connection refused\" if pollErr := wait.PollImmediate(framework.Poll, framework.KubeProxyEndpointLagTimeout, func() (bool, error) { _, err := framework.RunHostCmd(execPod.Namespace, execPod.Name, cmd) if err != nil { if strings.Contains(strings.ToLower(err.Error()), expectedErr) { framework.Logf(\"error contained '%s', as expected: %s\", expectedErr, err.Error()) return true, nil } else { framework.Logf(\"error didn't contain '%s', keep trying: %s\", expectedErr, err.Error()) return false, nil } } else { return true, errors.New(\"expected wget call to fail\") } }); pollErr != nil { Expect(pollErr).NotTo(HaveOccurred()) } }) </ins> }) // TODO: Get rid of [DisabledForLargeClusters] tag when issue #56138 is fixed.", "positive_passages": [{"docid": "doc-en-kubernetes-075a02cd819ce7b09a20727c244a2aff5570644c9d21afadee17b14b07c37e5c", "text": "I have a cluster from HEAD as of 2 weeks ago: So indeed it seems to not work. If I hit that same service IP from the VM itself I immediately get curl: (7) Failed to connect to 10.0.199.54 port 80: Connection refused. If I insert an iptables jump to KUBE-SERVICES at the front of FORWARD, it correctly rejects. This seems in accordance with the iptables flowchart. I'll do some spelunking to see if there's a reason NOT to reject in this case. Vallery Lancey <:\nCan you check IPVS mode?\nThis is why we need tests. Sigh.\nProposed fix is - still needs your e2e :)\nThanks Tim, if I have time I\u2019ll get a PR up tonight.\nSure will check IPVS mode.\nBase on my test, IPVS has no such issue.", "commid": "kubernetes_issue_20767", "tokennum": 186}], "negative_passages": []}
{"query_id": "q-en-kubernetes-09a30bfeac2759a1502479a9ab062396c2a37f8cd14fd6d03ce1c5c463c30908", "query": "} klog.Errorf(\"Failed to GetNodeNameByIPConfigurationID(%s): %v\", ipConfigurationID, err) <del> errors = append(errors, err) </del> <ins> allErrs = append(allErrs, err) </ins> continue } nodeResourceGroup, nodeVMSS, nodeInstanceID, nodeVMSSVM, err := ss.ensureBackendPoolDeletedFromNode(nodeName, backendPoolID) if err != nil { <del> klog.Errorf(\"EnsureBackendPoolDeleted(%s): backendPoolID(%s) - failed with error %v\", getServiceName(service), backendPoolID, err) errors = append(errors, err) </del> <ins> if !errors.Is(err, ErrorNotVmssInstance) { // Do nothing for the VMAS nodes. klog.Errorf(\"EnsureBackendPoolDeleted(%s): backendPoolID(%s) - failed with error %v\", getServiceName(service), backendPoolID, err) allErrs = append(allErrs, err) } </ins> continue }", "positive_passages": [{"docid": "doc-en-kubernetes-27479256c4cd4a81489a76c239bc26b6dc52b8a0b6a444f52adbe9ce38513013", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --/kind bug /sig cloud-provider /area provider/azure Azure in-tree CCM fails to delete a load balancer: The corresponding logs: The clouprovider config is: The Nodes are actually Azure VMs that belong to a VMO (aka vmss with flexible orchestration mode) - regular VMs and managed independently of the vmss. So those VMs are managed on Azure as . LoadBalancer deletion works with the very same setup with v1.21.1 of the in-tree Azure CCM. After recent cherry-picks, with v1.21.4 we observe the failure above. a cluster using VMs that belong to a VMO a Service of type LoadBalancer the Service of type LoadBalancer sure that the deletion fails with: Kubernetes version (use ): v1.21.4 Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Gardener Network plugin and version (if this is a network-related bug): Others:\n/assign /triage accepted", "commid": "kubernetes_issue_105184", "tokennum": 289}], "negative_passages": []}
{"query_id": "q-en-kubernetes-09f55eea4acb93558518e82e86888b5d51a02329e1f53f0f6f8d89efab01f261", "query": "optf(dm) } <del> // initialize versionCache with a updater dm.versionCache = cache.NewVersionCache(func() (kubecontainer.Version, kubecontainer.Version, error) { return dm.getVersionInfo() }) // update version cache periodically. if dm.machineInfo != nil { dm.versionCache.UpdateCachePeriodly(dm.machineInfo.MachineID) } </del> return dm }", "positive_passages": [{"docid": "doc-en-kubernetes-c9313de66f3508f8886cd07268b253d5e2cfa321359afb89838b6984a0afe883", "text": "The recently merged PR a version cache in dockertools, which makes the test  flaky. The reason is that injected error into fakedockerclient and then expected to see the error from right after that (See ). However, the error was consumed by the goroutine which periodically updates the version cache (See ). The docker daemon version is rarely updated, and we only need version once for each container creating, during which we also do container create, start, inspect #etc. 1) Do we care about the cost of the call so much that we have to introduce the complexity? 2) Kubelet periodically calls , can we rely on that to update the cache? Anyhow, at least, we should disable the cache or have a fake one in the unit test. :) /cc\nI once considered move this cache to runtime level, while thus may need to change runtime interface. What if only cache apiversion?\nWe can only get via , so there will still be the data race. :) One option is to update the version cache in , now kubelet periodically call to check the runtime status. Another better option is to cache the version in layer, now is under our control, we can refactor it with an additional argument indicating whether to use cached value or get directly from the daemon. If we cache the version only for performance, I prefer the second option which is cleaner and more efficient. :)\nOK, will look into this tonight\nThe unit test itself should not start a goroutine to update the cache (unless you're actually testing the goroutine). We should disable it anyway, as we often do in our unit tests. It also sounds like we don't need a goroutine dedicated for this. If we can tolerate the additional overhead from time to time, we can set a expiration time (e.g., 1 minute), and only call the runtime if the entry expires.\nTotally agree. :) Maybe a new function in wrapping the update logic, or wrapping the logic in the .\nexpiration time sounds good in this case\nThis is happening quite frequently - increasing priority to P0.", "commid": "kubernetes_issue_24298", "tokennum": 452}], "negative_passages": []}
{"query_id": "q-en-kubernetes-09f8e3880067931ab288ea524667b11a98827bb2a26a831cf4cde403ec0cc924", "query": "# Get the compute project project=$(gcloud info --format='value(config.project)') <ins> project=${project// /} </ins> if [[ ${project} == \"\" ]]; then echo \"Could not find gcloud project when running: `gcloud info --format='value(config.project)'`\" exit 1", "positive_passages": [{"docid": "doc-en-kubernetes-eb797bc1cabb351f81b78965d26c745c1a384907fc5b719bed4a9e14b0656c34", "text": "The compute project and zone in the prerequisites check are incorrectly calculated: !!! Error in hack/make-rules/test-e2e- Error in hack/make-rules/test-e2e- 'tee -i \"${artifacts}/build-\"' exited with status 1 0 Call stack: 1: hack/make-rules/test-e2e- main(...) Exiting with status 1 blocked by the following errors in each case: 1- Could not find gcloud compute/zone when running: .... 2- Could not find gcloud project when running: ..... 1- gcloud config unset compute/zone 2- gcloud config unset project 3- make test-e2e-node REMOTE=true LIST_IMAGES=true gcloud --version Google Cloud SDK 453.0.0 alpha 2023.10.27 beta 2023.10.27 bq 2.0.98 core 2023.10.27 gcloud-crc32c 1.0.0 <details</details<details</details<details</details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig node /assign", "commid": "kubernetes_issue_127362", "tokennum": 358}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0a30ba01cf05db9619fa44fe18171fac1440747ab02490903c69f0d8e3e24adc", "query": "return &Result{visitor: VisitorList(visitors), sources: visitors} } <del> // visit single item specified by name if len(b.name) != 0 { </del> <ins> // visit items specified by name if len(b.names) != 0 { isSingular := len(b.names) == 1 </ins> if len(b.paths) != 0 { <del> return &Result{singular: true, err: fmt.Errorf(\"when paths, URLs, or stdin is provided as input, you may not specify a resource by arguments as well\")} </del> <ins> return &Result{singular: isSingular, err: fmt.Errorf(\"when paths, URLs, or stdin is provided as input, you may not specify a resource by arguments as well\")} </ins> } if len(b.resources) == 0 { <del> return &Result{singular: true, err: fmt.Errorf(\"you must provide a resource and a resource name together\")} </del> <ins> return &Result{singular: isSingular, err: fmt.Errorf(\"you must provide a resource and a resource name together\")} </ins> } if len(b.resources) > 1 { <del> return &Result{singular: true, err: fmt.Errorf(\"you must specify only one resource\")} </del> <ins> return &Result{singular: isSingular, err: fmt.Errorf(\"you must specify only one resource\")} </ins> } mappings, err := b.resourceMappings() if err != nil { <del> return &Result{singular: true, err: err} </del> <ins> return &Result{singular: isSingular, err: err} </ins> } mapping := mappings[0] <ins> client, err := b.mapper.ClientForMapping(mapping) if err != nil { return &Result{err: err} } selectorNamespace := b.namespace </ins> if mapping.Scope.Name() != meta.RESTScopeNameNamespace { <del> b.namespace = \"\" </del> <ins> selectorNamespace = \"\" </ins> } else { if len(b.namespace) == 0 { <del> return &Result{singular: true, err: fmt.Errorf(\"namespace may not be empty when retrieving a resource by name\")} </del> <ins> return &Result{singular: isSingular, err: fmt.Errorf(\"namespace may not be empty when retrieving a resource by name\")} </ins> } } <del> client, err := b.mapper.ClientForMapping(mapping) if err != nil { return &Result{singular: true, err: err} } info := NewInfo(client, mappings[0], b.namespace, b.name) if err := info.Get(); err != nil { return &Result{singular: true, err: err} </del> <ins> visitors := []Visitor{} for _, name := range b.names { info := NewInfo(client, mapping, selectorNamespace, name) if err := info.Get(); err != nil { return &Result{singular: isSingular, err: err} } visitors = append(visitors, info) </ins> } <del> return &Result{singular: true, visitor: info, sources: []Visitor{info}} </del> <ins> return &Result{singular: isSingular, visitor: VisitorList(visitors), sources: visitors} </ins> } // visit items specified by paths", "positive_passages": [{"docid": "doc-en-kubernetes-8781beaf9cecb5a2a5891763e358d97bbb8efac5ebba9fc986604965efa0dda5", "text": "Currently, it could not delete multiple pods at once, need to delete them one by one, it's very inconvenient if I have tons of pods to delete. Unlike docker, docker can multiple stop/rm containers/images at once.\nThis is possible using label selectors as of , which is better if you have tons of pods.\nI agree that using label selector is better to delete all of pods under the label. But to delete multile pods at once is still usable: I just want to delete 1/2 pods under the label, label selector will not work selector could not span over other selectors or pods Another reason is docker rm/stop x y z works, I will wonder why kubectl cannot. This is not urgent, but I hope it can be implemented.\nI agree. Thanks for the suggestion.\nWould this be a suitable task for someone new to k8s development? If so, I'd be willing to take a look at this, if someone could provide a couple of hints where to start.\nFurther to my last message, I have a functional work in progress I would like to share, if anyone is interested?\nPRs are welcome. See\nYes, this is a reasonable place to start. Since its in the client, you won't get much orientation to the core server code, but it will be a good place to orient to the client side API. There us also prior art that you can model off of. The kubectl create ... command already supports multiple resources. A good command to adapter would be the 'label' command. You can find it in Many thanks in advance! Brendan On Feb 19, 2015 8:21 AM, \"Eric Tune\" wrote:", "commid": "kubernetes_issue_3050", "tokennum": 364}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0a352af816a32a2c80d4209d9be04de73012cbc63c9d2c41388b6f4f9d33e893", "query": "defer func() { framework.DeletePodWithWait(f, f.ClientSet, pod) }() <del> err = framework.WaitForPodRunningInNamespace(f.ClientSet, pod) Expect(err).To(HaveOccurred(), \"while waiting for pod to be running\") </del> By(\"Checking for subpath error event\") selector := fields.Set{", "positive_passages": [{"docid": "doc-en-kubernetes-5b9acc75297a25b96aff671a444795dd08937bfc26a86f521e5dacf125ddfa55", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: gce-new-master-upgrade-cluster-new-parallel Which test(s) are failing: Varies, but all subpath failures, including: [sig-storage] CSI Volumes [Driver: csi-hostpath-v0] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath with backstepping is outside the volume [Slow] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath directory is outside the volume [Slow] [sig-storage] CSI Volumes [Driver: csi-hostpath-v0] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath file is outside the volume [Slow] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath file is outside the volume [Slow] ... and pretty much every other subpath test, but never all of them at once. There's also a few other storage tests failing, such as: [sig-storage] Volume expand [Slow] Verify if editing PVC allows resize [sig-storage] Detaching volumes should not work when mount is in progress Since when has it been failing: 11/22 Testgrid link: https://k8s- Reason for failure: These flakes started around the time that merged, but doesn't match up with the exact merge stamp, so it's probably coincidental. The subpath test failures seem to be mostly timeouts: ... so possibly this is just GCE fail. Anything else we need to know: This test job has always been flaky, with around a 40% failure rate. <!-- DO NOT EDIT BELOW THIS LINE --/kind flake /sig storage /priority important-soon cc\ncan you please help investigate this. It looks to me like the tests are flaking for and . I wonder if the v0 tests are racing with the non-v0 tests for something in this test?\nThe other tests including for the other CSI driver and non-CSI in-tree plugins are solid green which also makes me think this is a issue with the hostpath tests or driver.", "commid": "kubernetes_issue_71383", "tokennum": 534}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0a352af816a32a2c80d4209d9be04de73012cbc63c9d2c41388b6f4f9d33e893", "query": "defer func() { framework.DeletePodWithWait(f, f.ClientSet, pod) }() <del> err = framework.WaitForPodRunningInNamespace(f.ClientSet, pod) Expect(err).To(HaveOccurred(), \"while waiting for pod to be running\") </del> By(\"Checking for subpath error event\") selector := fields.Set{", "positive_passages": [{"docid": "doc-en-kubernetes-b96111816628bb5b6b036ae1cc6a1fd4cca373f6f47aaa901c194d255325d8fd", "text": "(just adding additional similar flakes here for tracking) Similar flakes in :\nadding to the milestone for triage since the flakes look new\nThese all 4 subpath tests call and it fails in finding a specific failed event by using . As uses to check if the specific error event happens, and , I guess that tests may flake if other failed event happens before the expected one. Also, already wait for the event, we might be able to delete  in . I will create a PR to fix above.\n/priority critical-urgent /remove-priority important-soon /milestone v1.13\nwhile we should update the test with your PR, I'm not sure if it's going to fix the failure. Looking at one failing test log, these are the events I see on the failing pod: So it seems to be failing before even reaching the subpath logic.\nTimeline of events: Test pod started getting processed by kubelet: It took a minute after the test pod was created for the csi driver to finish registering and mount to succeed, and then subpath event to trigger: So should address the issue. I was initially confused because the test logs didn't show the subpath event for some reason\nI opened up to investigate if 1 minute for csi plugin registration is expected\nI've a tracker issue for the complete list of storage flakes: This is so that we can track whether we're addressing most of the flakes with the subpath fixes, or if additional fixes are required.\nkeeping open until flakes are verified cleaned up\n/reopen Reopening this issue until we can verify the fix in CI\nAs of this morning we are seeing CSI \"subpath should fail\" flakes in the following job Multiple \"subpath should fail\" flakes in this slow job alone Multiple \"subpath should fail\" flakes in the 1.13 slow job, similar to master. The following 2 tests are flaky only in this upgrade job can you help us determine if these are cases are flaky tests that you are fixing or is there an underlying CSI bug that needs addressing?\nroot cause of this is a delay in an external sidecar containers and the tests not waiting long enough to accommodate the delay. There are no changes required in (outside of test) to handle this. These should not be 1.13 blocking. We'll continue to look in to getting them non-flaky today.", "commid": "kubernetes_issue_71383", "tokennum": 498}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0a352af816a32a2c80d4209d9be04de73012cbc63c9d2c41388b6f4f9d33e893", "query": "defer func() { framework.DeletePodWithWait(f, f.ClientSet, pod) }() <del> err = framework.WaitForPodRunningInNamespace(f.ClientSet, pod) Expect(err).To(HaveOccurred(), \"while waiting for pod to be running\") </del> By(\"Checking for subpath error event\") selector := fields.Set{", "positive_passages": [{"docid": "doc-en-kubernetes-bf7ca95c6d3fe47cf47149272c15b0cd4379bd169d397f0222144854aadb75e6", "text": "In the meantime, we can mark these tests as flaky to reduce the noise, if you'd like. looks like the same issue () is still being hit. See : And logs from (): We need to make the tests handle this condition more gracefully. The suggestion here is one possible solution.\nWould be good to capture this as a known issue in release notes.\nto followup on capturing this in Release notes\nper , can you create a targeted fix increasing the timeout? Looks like marking these tests as flaky will be difficult for 1.13, but if that doesn't fix it we will need to do that.\nShort term fix to bump the test timeout:\nAs per discussion in release burndown meeting, this is not a 1.13 blocker. please move this issue to 1.14 if there are no pending issues you are concerned about\nOk looks like the test still flaked. Looking at , the mount succeeded after a minute and proceeded to subpath processing, which (correctly) failed. However, for some resaon, the test is not seeing the subpath event and still failed after 4 minutes. On kubelet, subpath processing failed after a minute and generated the event: But the test doesn't see it for some reason, and still times out after 4 more minutes:\nI saw the same on CSI volume mount succeeded at: Kubelet correctly failed the pod because of subpath But test still failed: Because the test failed to find the pod event. This looks like a test issue. Not a 1.13 blocker.\ncan you PTAL at this\nIs there a way to check if events are overloaded and not able to handle new events? The MountVolume retries while the driver is not registered is very frequent and could have overloaded the event server.\nChecking for the existence of an event seems like the wrong way to test this. Would checking pod status alone be insufficient? Ultimately that is what we really care about.\nChecking for the specific event guarantees that we are failing with the correct error. But perhaps events are not reliable enough to depend on. Checking if the Pod never came up running would probably reduce the flakes but could potentially mask false negatives. cc for any thoughts.", "commid": "kubernetes_issue_71383", "tokennum": 461}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0a352af816a32a2c80d4209d9be04de73012cbc63c9d2c41388b6f4f9d33e893", "query": "defer func() { framework.DeletePodWithWait(f, f.ClientSet, pod) }() <del> err = framework.WaitForPodRunningInNamespace(f.ClientSet, pod) Expect(err).To(HaveOccurred(), \"while waiting for pod to be running\") </del> By(\"Checking for subpath error event\") selector := fields.Set{", "positive_passages": [{"docid": "doc-en-kubernetes-134801dda9ebcf7b8cdf97d148e6b55c98d4c0b9989e7755b1ae0bf2d394c600", "text": "Tests are still flaking and actually it seems like in general storage flakes in slow are flaking more since 11-21 or so: https://k8s- My theory is that the driver registration delay is causing a flood of events, which causes tests that check for events to fail. I think this is revealing multiple issues in both the tests and product, and we should work on fixing them all, although any one of the fixes should mitigate the test flakes: Driver registrar can sometimes take a minute to come up: Volume manager operation executor doesn't seem to be throttling retries or backing off: Tests should not rely on events: Tests should wait for CSI driver to be registered on all nodes before creating test pods:\nand have been merged and will address the biggest issues. has been backported to 1.13 already, backport is still pending.\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nClosing 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", "commid": "kubernetes_issue_71383", "tokennum": 441}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0a57b5175a21436409a798156431592f09424685affe76488902cd2526eba3c6", "query": "case \"${KUBE_OS_DISTRIBUTION}\" in ubuntu|coreos) <del> echo \"Starting cluster using os distro: ${KUBE_OS_DISTRIBUTION}\" >&2 </del> source \"${KUBE_ROOT}/cluster/aws/${KUBE_OS_DISTRIBUTION}/util.sh\" ;; *)", "positive_passages": [{"docid": "doc-en-kubernetes-22d12c96031ea08416343124eb9503ad24bb849f7be271f6e9f581299968b0bd", "text": "Example: kubectl cluster-info shows a redundant line: The cluster is already up, so the phrase \"Starting cluster\" is confusing in context of the command. (My kubernetes test cluster is running on AWS i.e. KUBERNETES_PROVIDER=aws. I had used kube- to create a test kubernetes cluster on aws). Log of my shell session:\nThanks for the bug report I've filed a PR to fix it.", "commid": "kubernetes_issue_9246", "tokennum": 103}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0a667653e503c8d9b1cfb88c03df59ff3d611179d14fabbe29603ede72734012", "query": "func (r *LogREST) NewGetOptions() (runtime.Object, bool, string) { return &api.PodLogOptions{}, false, \"\" } <ins> // OverrideMetricsVerb override the GET verb to CONNECT for pod log resource func (r *LogREST) OverrideMetricsVerb(oldVerb string) (newVerb string) { newVerb = oldVerb if oldVerb == \"GET\" { newVerb = \"CONNECT\" } return } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-818250efc38f3e1e4f69f5ba9f53826c59d17d9aa3970f389bfaed5f09e5cc10", "text": "Is this a BUG REPORT or FEATURE REQUEST?: What happened: use kubectl search log with follow option get api latency (apiserverrequestlatenciessummary{quantile=\"0.99\",resource=\"pods\",verb=\"GET\"} )high to give a alert in my cluster. the apiserver log is below and we can see it costs 1m25s. What you expected to happen: do not make this api latency account in getting pod request api latency How to reproduce it (as minimally and precisely as possible): use kubectl to search a pod log with follow option long enough and you will get this metric apiserverrequestlatenciessummary{quantile=\"0.99\",resource=\"pods\",verb=\"GET\"} higher than the ordinary case. Anything else we need to know?: I am happy to fix it. Environment: Kubernetes version (use ): 1.6 Cloud provider or hardware configuration**: bare-metal OS (e.g. from /etc/os-release): ubuntu 16.04 Kernel (e.g. ): 4.4 Install tools: kubeadm Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig API Machinery\n/area apiserver\n/sig api-machinery\n/assign Thanks... looking forward to your PR!\nfixed with PTAL", "commid": "kubernetes_issue_49998", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0a90a4d932f845be1743a10b11735e1b1d80866e3e65ecc931a59240d66d7f9e", "query": ") const ( <del> // When these values are updated, also update cmd/kubelet/app/options/options.go // A copy of these values exist in e2e/framework/util.go. </del> <ins> // When these values are updated, also update cmd/kubelet/app/options/container_runtime.go // A copy of these values exist in test/utils/image/manifest.go </ins> currentPodInfraContainerImageName    = \"gcr.io/google_containers/pause\" <del> currentPodInfraContainerImageVersion = \"3.0\" </del> <ins> currentPodInfraContainerImageVersion = \"3.1\" </ins> ) // GetServerArchitecture fetches the architecture of the cluster's apiserver.", "positive_passages": [{"docid": "doc-en-kubernetes-a834f77ddd825b3d04a660aa7c11d0734893e4dcde6e0d4a7399e3b3daf56428", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: the pause-amd64:3.0 image on has an empty schema2 manifest, which prevents is from being pulled by proxy/caches which only support V2 registries. What you expected to happen: Being able to pull ` using a V2 manifest compatible client. Anything else we need to know?: The proxy/cahce is requesting this\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nAfter talking with , he mentionned the following\nAFAIK, does not support well. After inspecting the image, you can find is still using manifest v1.\n/cc FYI\nIm not sure which exact version x sch\u00e9ma X is needed. What I know is that we can download through the proxy/cache all other Kubernetes kube-system images, only the pause image is giving us trouble. Therefore, I would say that having the image available using the same format as the other kube-system images would be the request here.\nYeah, we haven't updated the pause image in a while, since it doesn't really ever change. I'm not sure whether rebuilding + pushing over the existing tag is safe, or if we should bump to or something. thoughts?\nIf we do rebuilding/updating the image, that would help and a bunch of similar issues.\nit's better/save to go with new tag\nI didn't realize there were changes to the pause binary that were never actually deployed. It seems like we should probably just do that (and bump the tag).\nthat sounds great. Any idea when the existing 3.0 tag could be pushed again?\nWe shouldn't push over the 3.0 tag; we should push a 3.1 or 4.0 tag instead. I'm not sure who owns the pause container who should drive this. Maybe sig-node and/or\nIt seems like it should be sig-node. I'll look into it.\nThe new container has been built, can you test with\nIts working! thanks! I was able to pull it through our artifactory proxy , Lee Verberne <:\nexcellent, thanks for checking. /assign", "commid": "kubernetes_issue_56253", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0a90a4d932f845be1743a10b11735e1b1d80866e3e65ecc931a59240d66d7f9e", "query": ") const ( <del> // When these values are updated, also update cmd/kubelet/app/options/options.go // A copy of these values exist in e2e/framework/util.go. </del> <ins> // When these values are updated, also update cmd/kubelet/app/options/container_runtime.go // A copy of these values exist in test/utils/image/manifest.go </ins> currentPodInfraContainerImageName    = \"gcr.io/google_containers/pause\" <del> currentPodInfraContainerImageVersion = \"3.0\" </del> <ins> currentPodInfraContainerImageVersion = \"3.1\" </ins> ) // GetServerArchitecture fetches the architecture of the cluster's apiserver.", "positive_passages": [{"docid": "doc-en-kubernetes-7628cd26f0dafa992a4ea43a6c68b9bcdbf056fca43ee32b40ab60cef4154c17", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: pause does not reap zombie processes using the default pause container provided by What you expected to happen: should include the up to date pause code to reap zombie processes when using docker = 1.13.1 found here How to reproduce it (as minimally and precisely as possible): a.out will leave a zombie process that is not cleaned up Anything else we need to know?: Building the pause container from master solves this issue Related: Environment: Kubernetes version (use ): 1.7.0+ Cloud provider or hardware configuration**: N/A OS (e.g. from /etc/os-release): CentOS 7 Kernel (e.g. ): 4.10.13+ Install tools: Others: docker = 1.13.1\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\ni get a simliar problem when i run crond service in pod container, every day it makes some [anacron] zombie progresses UID PID PPID C STIME TTY TIME CMD root 1 0 0 Nov14 ? 00:00:00 /pause root 7 0 0 Nov14 ? 00:00:00 /usr/local/bin/dumb-init /usr/lo root 13 7 0 Nov14 ? 00:00:00 nginx: master process /usr/local nobody 21 13 0 Nov14 ? 00:00:01 nginx: worker process nobody 22 13 0 Nov14 ? 00:00:07 nginx: worker process nobody 23 13 0 Nov14 ? 00:00:07 nginx: worker process nobody 24 13 0 Nov14 ? 00:00:05 nginx: worker process root 77 1 0 Nov14 ? 00:00:00 [anacron] root 1 0 00:01 ? 00:00:00 [anacron] <defunctroot 1 0 01:01 ? 00:00:00 [anacron] <defunctroot 1 0 02:01 ?", "commid": "kubernetes_issue_50865", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0a90a4d932f845be1743a10b11735e1b1d80866e3e65ecc931a59240d66d7f9e", "query": ") const ( <del> // When these values are updated, also update cmd/kubelet/app/options/options.go // A copy of these values exist in e2e/framework/util.go. </del> <ins> // When these values are updated, also update cmd/kubelet/app/options/container_runtime.go // A copy of these values exist in test/utils/image/manifest.go </ins> currentPodInfraContainerImageName    = \"gcr.io/google_containers/pause\" <del> currentPodInfraContainerImageVersion = \"3.0\" </del> <ins> currentPodInfraContainerImageVersion = \"3.1\" </ins> ) // GetServerArchitecture fetches the architecture of the cluster's apiserver.", "positive_passages": [{"docid": "doc-en-kubernetes-6179feaaee46a15cd909bb088c82657b9b59fba8efdee1296995076588512032", "text": "00:00:00 [anacron] <defunctroot 1 0 03:01 ? 00:00:00 [anacron] <defunctroot 0 0 11:49 ? 00:00:00 /bin/bash root 0 1 19:15 ? 00:00:00 /bin/bash root 0 19:15 ? 00:00:00 ps -ef !\nDo we know why this was never resolved / was never deployed?\nI just fought through this issue with a rabbitmq helm chart. I had to custom build a pause container from master to fix it. The rabbitmq helm chart uses for its liveness checks. It's a thin wrapper around a call to the rabbitmq-server daemon, which is not PID 1 (/pause is PID 1). The rabbitmq-server process forks some children to do the work and then they exit. Since the pause-amd64:3.0 is not reaping, those processes stick around as zombies. The liveness check runs every 5 seconds. After about 4 hours, there are about 27K zombies and the node begins failing to launch new containers because it's starved for resources. The pause container built from current master fixes that behavior, no zombies at all in the container.\nThe plan is to build a new version of pause-amd64 and then update the image referenced by Kubernetes. This means the default image will change in the next Kubernetes release. We can make the new image available once the freeze lifts and we can merge .\nLooks like this made it into 1.10", "commid": "kubernetes_issue_50865", "tokennum": 336}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0add3ab52da07373382c08191a9be6f440603d7147db0ac32bea34055c83d973", "query": "} idx = len(ary) - idx } <ins> if idx < 0 || idx >= len(ary) || idx > len(cur) { return fmt.Errorf(\"Unable to access invalid index: %d\", idx) } </ins> copy(ary[0:idx], cur[0:idx]) ary[idx] = val copy(ary[idx+1:], cur[idx:])", "positive_passages": [{"docid": "doc-en-kubernetes-e51351c05e6844b765acf34eaa6a0653d5a4e3452baed4722f32f9c5caa3ece5", "text": "/kind bug What happened: Wrote a that returned a faulty json patch which specified an our of range index (e.G. when there is only one container). This resulted in the apiserver crashing. Stacktrace: What you expected to happen: No crash /sig-api-machinery\n/sig api-machinery\nThis maybe a bug in . I will follow this question.\nThis bug had been fixed in PR: you can checkout it.\nThanks for your comment but I don't think the linked PR fixed the issue, as it got merged almost a year ago and I am running Kube 1.10.1 which does contain that patch but still panics. Just from quickly looking at the code I the linked PR I believe there are two things wrong: The check if the index is valid only happens when a negative index was given should be\nOnce the PR of is merged I will update kubernetes.\n/kind bug", "commid": "kubernetes_issue_64291", "tokennum": 194}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0b04581b03e953347c12b885b5907d300595c2b3f322103fb508958c23888de4", "query": "return m.wrappedMounter.ExistsPath(pathname) } <ins> func (m *execMounter) EvalHostSymlinks(pathname string) (string, error) { return m.wrappedMounter.EvalHostSymlinks(pathname) } </ins> func (m *execMounter) PrepareSafeSubpath(subPath Subpath) (newHostPath string, cleanupAction func(), err error) { return m.wrappedMounter.PrepareSafeSubpath(subPath) }", "positive_passages": [{"docid": "doc-en-kubernetes-226c0928db9d5aa6f1446838b8788eb7c60cd41b1b8246f4bd1a4e2614bb7834", "text": "/kind bug Using , if a block device is symlinked to the discovery directory e.g. , then MapVolume will fail with since the containerized kubelet cannot see the path on host. is mounted by containerized kubelet, so if before we try to map the device we set devicePath to the evaluation of symlink and end up with a devicePath of , containerized kubelet will see the device and successfully map the device. Are there any issues with this solution? This is on Kubernetes 1.10\n/sig storage\nah yes containerized kubelet has many issues when dealing with symlinks. Check out Mounter.GetMode(), it calls a nsenter EvalSymlinks which should be able to do what you need. But actually, one thing to consider, is do you need to do the losetup on the host, or does inside the container work?\nYes it appears to work from inside the container, on the host I run which disappears after I delete the pod using the device. My understanding of running losetup in MapVolume is not that great but I suppose that as long as that /dev/loop0 is created we are fine. Thanks for the quick response, I'll create a PR using that function and tag you\nDoes it create it on the host or in the containerized kubelet? What happens when containerized kubelet is restarted? The purpose of losetup is to do \"refcounting\" on the block device to prevent possible naming collisions when devices are attached/detached under unhealthy conditions. Ie, if a device showed up as /dev/sdb and you gave that to a pod, and then for some reason it become unhealthy and disappeared (while the pod is still running), another device (maybe even another volume type) could get attached to the node and reuse /dev/sdb. Now the pod has access to a device it's not supposed to. With filesystem volumes, the refcounting is done with mount points, but for block device, loopback is the equivalent.\nIt is created on the host (and also visible in the container), and stays around through restart. I understand now, thank you.\nActually after I restart it becomes /vdb instead of /dev/vdb in the losetup output, idk what that is about.", "commid": "kubernetes_issue_65445", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0b04581b03e953347c12b885b5907d300595c2b3f322103fb508958c23888de4", "query": "return m.wrappedMounter.ExistsPath(pathname) } <ins> func (m *execMounter) EvalHostSymlinks(pathname string) (string, error) { return m.wrappedMounter.EvalHostSymlinks(pathname) } </ins> func (m *execMounter) PrepareSafeSubpath(subPath Subpath) (newHostPath string, cleanupAction func(), err error) { return m.wrappedMounter.PrepareSafeSubpath(subPath) }", "positive_passages": [{"docid": "doc-en-kubernetes-e6271b0ba1dda755d5bb536a727016a621c7c29c599386bc1e9c22a230980cbf", "text": "There is no such thing as /vdb and /dev/vdb is still intact of course. Seems inconsequential since it is disappearing after all pods using the device are deleted, i.e. it's still serving as a refcounter", "commid": "kubernetes_issue_65445", "tokennum": 55}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0b0b8eb1c8f9de75456d29b0326b5e2c2eda1365c41e0056e7667162aca5097d", "query": "cp kubernetes/server/kubernetes/server/bin/kubelet  kubernetes/server/kubernetes/server/bin/kube-proxy binaries/minion <ins> cp kubernetes/server/kubernetes/server/bin/kubectl binaries/ </ins> rm -rf flannel* kubernetes* etcd* echo \"Done! All your commands locate in ./binaries dir\"", "positive_passages": [{"docid": "doc-en-kubernetes-6ad186288ef256533240c5bfccb6ba92929a47585cc346f791c0fbaeeb93c979", "text": "Though I have successfully installed kubernetes via :smiley: , still want to point out this doc missing the step to install . Thus, if user just follow the guide in the doc without having much knowledge about kubernetes, he/she would get error \"It looks as if you don't have a compiled kubectl binary\" during the step of . Manually install kubectl on at least master node should be necessary (suggest to let user also install on minion node for convenience), any way, the installation step is .\nI forget to mention that.I will update the doc this tuned\nI update the scripts in pr , you can try it now. I copied the kubectl binary from the kubernetes release and put it in , so there is no extra step for user to manually download . Actually, in the first version of ubuntu k8s deployment, I copied the to every node, but I think it is an overhead, so I removed it.I think this is just enough.\nDoc update : Move the kubectl into the PATH, it may need sudo privilege so I decide not do for the user.\nHave the same issue, please update the doc ASAP.\nGreat job :+1:\nAlso ran into this bug after recklessly running ( instead of ) :)", "commid": "kubernetes_issue_8373", "tokennum": 276}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0b84423e75d46b0cba7f4fd94e0c646e11690484942523ca223f4465f892e9ce", "query": "targetNamePath := sessionPath + \"/iscsi_session/\" + sessionName + \"/targetname\" targetName, err := io.ReadFile(targetNamePath) if err != nil { <del> return nil, err </del> <ins> klog.Infof(\"Failed to process session %s, assuming this session is unavailable: %s\", sessionName, err) continue </ins> } // Ignore hosts that don't matchthe target we were looking for.", "positive_passages": [{"docid": "doc-en-kubernetes-2bba8e4fb458ddf612a1ae84873c0951878ae27f68765b5b6efc434715382796", "text": "If one target in multipath volume gets down and a pod that uses the volume is deleted and quickly recreated (e.g. by a Deployment), the new pod never starts. How to reproduce it (as minimally and precisely as possible): Deployment with single replica with one multipath iSCSI volume one target (e.g. switch the machine off). Multipath will mark appropriate path as failed: the deployment pod. will quickly start a new pod for the Deployment. new pod will be (or ) forever, What happened: Kubelet tries to WaitForAttach / SetUp volume for the new pod. The volume is still attached. Kubelet goes through all targets and tries to find out if it's logged in or not. Eventually it tries to read of the failed path and that returns error: What you expected to happen: Kubelet assumes that the path is failed / not logged in and tries to recover it. If it fails it continues with multipath with 2 available devices and 1 failed one. IMO, simple instead of will do its job just fine. /assign /sig storage cc for iSCSI expertise\nFix:", "commid": "kubernetes_issue_74305", "tokennum": 238}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0b94534a6252ca41597cdabdae2ca17f357f5b9acbc855283b5c28d84f98c021", "query": "framework.ExpectNoError(err, \"failed to count the required APIServices\") framework.Logf(\"APIService %s has been deleted.\", apiServiceName) <del> ginkgo.By(\"Confirm that the group path of \" + apiServiceName + \" was removed from root paths\") groupPath := \"/apis/\" + apiServiceGroupName err = wait.PollUntilContextTimeout(ctx, apiServiceRetryPeriod, apiServiceRetryTimeout, true, func(ctx context.Context) (done bool, err error) { rootPaths := metav1.RootPaths{} statusContent, err = restClient.Get(). AbsPath(\"/\"). SetHeader(\"Accept\", \"application/json\").DoRaw(ctx) if err != nil { return false, err } err = json.Unmarshal(statusContent, &rootPaths) if err != nil { return false, err } return !slices.Contains(rootPaths.Paths, groupPath), nil }) framework.ExpectNoError(err, \"Expected to not find %s from root paths\", groupPath) </del> cleanupSampleAPIServer(ctx, client, aggrclient, n, apiServiceName) }", "positive_passages": [{"docid": "doc-en-kubernetes-a36678f387087dd8252401a5249426873ced2ebb26644cae4efea96ce80ca1f6", "text": "reported that conformance testing with the latest version of sonobuoy against a version 1.29.0-alpha.3 cluster fails on the support the 1.17 Sample API Server using the current Aggregator test: , related to I found the reason why the test is working fine in Kubernetes CI jobs but fails with sonobuoy is because the service account used by sonobuoy \"sonobuoy-serviceaccount\" doesn't have read permission of the non-resource url \"/\", which is used by the test to confirm the removal of group path: The permission of \"sonobuoy-serviceaccount\" is as below: There may be two ways to fix it: the RBAC rule of sonobuoy to include \"get\" of \"/\". However, could other test runners encounter this issue? Is there a doc listing the required permissions for running e2e tests? the e2e to skip checking the removal of the group path if the service account doesn't have permission to access the root path. Which way do we usually prefer? Running e2e with sonobuoy should succeed. a v1.29.0-alpha.3 cluster. No response <details</details<details</details<details</details<details</details<details</details<details</details\nimplemented this solution.\n/sig api-machinery\nthank you for opening this issue and working on a solution. I'm probably not the right person to decide on which solution is preferred. From my perspective, either solution is fine.\nNote: Sonobuoy is not owned by any Kubernetes SIG. At most it is between SIG Architecture and the CNCF to choose whether to recommend it for running tests. SIG Testing owns the e2e image that sonobuoy can be used to schedule but not sonobuoy. IMHO this is a bug in running the tests via a pod, which is not how we develop the tests (they're run outside the cluster, by a cluster admin account typically). I would say 1) is the correct answer. xref: /sig architecture /sig testing /triage accepted cc\nthanks for your comment. I guess 1) means non of the existing sonobuoy versions can pass K8s conformance test against a cluster 1.29.0-alpha3, as the RBAC rule is hardcoded.", "commid": "kubernetes_issue_121985", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0b94534a6252ca41597cdabdae2ca17f357f5b9acbc855283b5c28d84f98c021", "query": "framework.ExpectNoError(err, \"failed to count the required APIServices\") framework.Logf(\"APIService %s has been deleted.\", apiServiceName) <del> ginkgo.By(\"Confirm that the group path of \" + apiServiceName + \" was removed from root paths\") groupPath := \"/apis/\" + apiServiceGroupName err = wait.PollUntilContextTimeout(ctx, apiServiceRetryPeriod, apiServiceRetryTimeout, true, func(ctx context.Context) (done bool, err error) { rootPaths := metav1.RootPaths{} statusContent, err = restClient.Get(). AbsPath(\"/\"). SetHeader(\"Accept\", \"application/json\").DoRaw(ctx) if err != nil { return false, err } err = json.Unmarshal(statusContent, &rootPaths) if err != nil { return false, err } return !slices.Contains(rootPaths.Paths, groupPath), nil }) framework.ExpectNoError(err, \"Expected to not find %s from root paths\", groupPath) </del> cleanupSampleAPIServer(ctx, client, aggrclient, n, apiServiceName) }", "positive_passages": [{"docid": "doc-en-kubernetes-4545476cbce0605bfe46d5a01c41b8f4cf7b5ac07772bfb1748611bc506e90ef", "text": "I will file an issue to sonobuoy first.\nquestion here is what are the set of client permissions required to run the conformance suite? perhaps a level of access or a more granular recommendation should be documented. what is your take on the root path requirement as approver for: EDIT: slack thread:\nI agree, we already require e.g. privileged pods for a long time in conformance tests and we should make it clear that we expect a highly privileged client.\n+1 for what is saying, that we should expect that the user running the tests has required permissions. These tests are not built for being run unprivileged.\ni wanted to PR the admin note in our conformance docs under sig-arch, but then i saw this: so broke this guarantee. sounds like SIG Arch needs to comment.\nThis statement surprises me. Root discovery is one of the least-privileged permissions you can have on a cluster. For years this was even open for unauthorized users on the internet (if your api endpoint has been exposed). In other words, just add the permission. While thinking about it, it is surprising that the user in question does not have this access already. Don't we allow that for every authorized user?\nIn contrast, I hope that lots of privileged operations are tested by conformance today. If we don't test things like admission webhooks for example, we have much bigger problems. And admission webhooks are basically equivalent to cluster-admin.\nthat is outdated, we use hostNetwork pods one some of the tests IIRC\nlooks like we don't. before this ticket, i was under the impression that the conformance suite already requires admin and that all testers (like Sonobuoy) use admin level credentials. it is non-privileged (e.g., does not require root on nodes, access to raw network interfaces, or cluster admin permissions) looks like we may have to change that sentence completely.\nWould have expected it here: The PR in question explicitly fixes the result returned by . If that is part of conformance (IMO it should), every conformance test needs access it obviously. Whether we require admin, or we add it manually, either would work.", "commid": "kubernetes_issue_121985", "tokennum": 474}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0b94534a6252ca41597cdabdae2ca17f357f5b9acbc855283b5c28d84f98c021", "query": "framework.ExpectNoError(err, \"failed to count the required APIServices\") framework.Logf(\"APIService %s has been deleted.\", apiServiceName) <del> ginkgo.By(\"Confirm that the group path of \" + apiServiceName + \" was removed from root paths\") groupPath := \"/apis/\" + apiServiceGroupName err = wait.PollUntilContextTimeout(ctx, apiServiceRetryPeriod, apiServiceRetryTimeout, true, func(ctx context.Context) (done bool, err error) { rootPaths := metav1.RootPaths{} statusContent, err = restClient.Get(). AbsPath(\"/\"). SetHeader(\"Accept\", \"application/json\").DoRaw(ctx) if err != nil { return false, err } err = json.Unmarshal(statusContent, &rootPaths) if err != nil { return false, err } return !slices.Contains(rootPaths.Paths, groupPath), nil }) framework.ExpectNoError(err, \"Expected to not find %s from root paths\", groupPath) </del> cleanupSampleAPIServer(ctx, client, aggrclient, n, apiServiceName) }", "positive_passages": [{"docid": "doc-en-kubernetes-06abc1218304c92779dae2744e33107a4d26263c1c54e4453f3f92a1949c2aa2", "text": "adding to milestone and making release blocking ... we should not release 1.29 in a state that the most commonly used conformance tool will fail\nIMO we should clarify the state and go fix the tool, but we should keep the test and we should NOT add skip. Conformance docs are not a release artifact, and sonobuoy release lifecycle is not a conformance artifact. If we can't get sonobuoy working in a reasonable time, we already know the tests can be run by scheduling the image (which is ours) directly with kubectl instead and we can document that in the upstream conformance docs. We need to fix the for this image: ,%20master%20(dev) And it should probably be to release-blocking in the future.\nit looks like the e2e change made in was not consciously made part of conformance, it was just trying to functionally test the bugfix being made. For 1.29, I think we should revert the change to and make an integration test that validates the fix instead. We can revisit whether content of is part of conformance or not for 1.30\nI opened to revert the e2e change and move the functional test to an integration test\nFiled to try to get the image job passing again.\nWe probably need another issue to track 1.30 follow-up?\nIf no one has done it, I could create another issue and follow up with the items that have been discussed here: outdated privilege requirement in commonly used conformance tools like sonobuoy aware of the required priviledge to avoid similar situations in the future. permission of GET \"/\" to authorized users via the role for root discovery.", "commid": "kubernetes_issue_121985", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0ba71479220eaf6606c5c272d460494a746e284fe0f9feb512a99b298efe5721", "query": "return true, errors.New(\"not implemented\") } <ins> func (*NsenterMounter) EvalHostSymlinks(pathname string) (string, error) { return \"\", errors.New(\"not implemented\") } </ins> func (*NsenterMounter) SafeMakeDir(pathname string, base string, perm os.FileMode) error { return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-226c0928db9d5aa6f1446838b8788eb7c60cd41b1b8246f4bd1a4e2614bb7834", "text": "/kind bug Using , if a block device is symlinked to the discovery directory e.g. , then MapVolume will fail with since the containerized kubelet cannot see the path on host. is mounted by containerized kubelet, so if before we try to map the device we set devicePath to the evaluation of symlink and end up with a devicePath of , containerized kubelet will see the device and successfully map the device. Are there any issues with this solution? This is on Kubernetes 1.10\n/sig storage\nah yes containerized kubelet has many issues when dealing with symlinks. Check out Mounter.GetMode(), it calls a nsenter EvalSymlinks which should be able to do what you need. But actually, one thing to consider, is do you need to do the losetup on the host, or does inside the container work?\nYes it appears to work from inside the container, on the host I run which disappears after I delete the pod using the device. My understanding of running losetup in MapVolume is not that great but I suppose that as long as that /dev/loop0 is created we are fine. Thanks for the quick response, I'll create a PR using that function and tag you\nDoes it create it on the host or in the containerized kubelet? What happens when containerized kubelet is restarted? The purpose of losetup is to do \"refcounting\" on the block device to prevent possible naming collisions when devices are attached/detached under unhealthy conditions. Ie, if a device showed up as /dev/sdb and you gave that to a pod, and then for some reason it become unhealthy and disappeared (while the pod is still running), another device (maybe even another volume type) could get attached to the node and reuse /dev/sdb. Now the pod has access to a device it's not supposed to. With filesystem volumes, the refcounting is done with mount points, but for block device, loopback is the equivalent.\nIt is created on the host (and also visible in the container), and stays around through restart. I understand now, thank you.\nActually after I restart it becomes /vdb instead of /dev/vdb in the losetup output, idk what that is about.", "commid": "kubernetes_issue_65445", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0ba71479220eaf6606c5c272d460494a746e284fe0f9feb512a99b298efe5721", "query": "return true, errors.New(\"not implemented\") } <ins> func (*NsenterMounter) EvalHostSymlinks(pathname string) (string, error) { return \"\", errors.New(\"not implemented\") } </ins> func (*NsenterMounter) SafeMakeDir(pathname string, base string, perm os.FileMode) error { return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-e6271b0ba1dda755d5bb536a727016a621c7c29c599386bc1e9c22a230980cbf", "text": "There is no such thing as /vdb and /dev/vdb is still intact of course. Seems inconsequential since it is disappearing after all pods using the device are deleted, i.e. it's still serving as a refcounter", "commid": "kubernetes_issue_65445", "tokennum": 55}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0c0f57001ac47b4d64cd25032ca4707bf223f809ff02491ee627a586c2278ddb", "query": "set -o pipefail ### Hardcoded constants <del> DEFAULT_CNI_VERSION='v0.8.7' DEFAULT_CNI_HASH='8f2cbee3b5f94d59f919054dccfe99a8e3db5473b553d91da8af4763e811138533e05df4dbeab16b3f774852b4184a7994968f5e036a3f531ad1ac4620d10ede' </del> <ins> DEFAULT_CNI_VERSION='v0.9.1' DEFAULT_CNI_HASH='b5a59660053a5f1a33b5dd5624d9ed61864482d9dc8e5b79c9b3afc3d6f62c9830e1c30f9ccba6ee76f5fb1ff0504e58984420cc0680b26cb643f1cb07afbd1c' </ins> DEFAULT_NPD_VERSION='v0.8.7' DEFAULT_NPD_HASH='853576423077bf72e7bd8e96cd782cf272f7391379f8121650c1448531c0d3a0991dfbd0784a1157423976026806ceb14ca8fb35bac1249127dbf00af45b7eea' DEFAULT_CRICTL_VERSION='v1.21.0'", "positive_passages": [{"docid": "doc-en-kubernetes-dfff84e3b11879758919fecc393710655267c5015ee34e69e71565465ba5db90", "text": "The latest release of CNI plugins is , but we still have . I'll attempt to create a PR for this based on the .\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig network\n- assigning to you :)", "commid": "kubernetes_issue_102311", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0c27dc9269463d68be33f02fb16abc2a50d57f28e79ff20b73b070221e6ffb90", "query": "addKnownTypes(scheme) addConversionFuncs(scheme) addDefaultingFuncs(scheme) <ins> addDeepCopyFuncs(scheme) </ins> } // Adds the list of known types to api.Scheme.", "positive_passages": [{"docid": "doc-en-kubernetes-5056a2515a29befdf589a74f13db031ed4142bbabfa8d2c37cafac2de4fccaea", "text": "I started the federation-apiserver and went to and got the following output: Expected: I should have got an empty v1.ServiceList Any idea on what we are doing wrong? Have you guys seen this error?\nI think your deep copiers or conversion functions are not getting registered properly. If you look at my change in , some places are inappropriately registering with api.Scheme instead of the passed in scheme. Maybe you have that problem or a similar one, since I think you guys copied some code. , Nikhil Jindal wrote:\nDeep copy generation was slightly broken as well - you may want to double check that they are registered. On May 23, 2016, at 5:50 PM, Daniel Smith wrote: I think your deep copiers or conversion functions are not getting registered properly. If you look at my change in , some places are inappropriately registering with api.Scheme instead of the passed in scheme. Maybe you have that problem or a similar one, since I think you guys copied some code. , Nikhil Jindal wrote: \u2014 You are receiving this because you are on a team that was mentioned. Reply to this email directly or view it on GitHub\nI got the same error with latest branch, as I was swamping on service controller, so I use a previous version and worked around it.\ndeep copies were indeed missing, but adding them hasnt fixed the issue. Will debug more. is my PR to add the deep copies cc Please feel free to file issues for any such problem you face. We need to fix all these issues. Its good if we know about them early. Thanks!\nfixes this", "commid": "kubernetes_issue_26111", "tokennum": 335}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0c9ca3587e96b1c07d244c5c3cb19c0f04bc880c3d17e99c64514eb40c496eb2", "query": "} }) <ins> // TODO: move this under volumeType loop </ins> Context(\"when one pod requests one prebound PVC\", func() { var testVol *localTestVolume", "positive_passages": [{"docid": "doc-en-kubernetes-9df8e5ba2e9f919d9bec92d550979c4e420a21d16e91da208714cd0aae742f47", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /assign What happened: The tests are failing again because the scheduler messages have changed yet again. I'm going to remove the check for the exact messages because this is at least the 3rd time this has happened. Instead depend on unit/integration tests to check for specific failures. Also there's no need for these tests to run across all types of local volumes because it's just testing the scheduler part.", "commid": "kubernetes_issue_59369", "tokennum": 123}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0cb1482370150c55f35e6881c825d53a47cdc1ec5403c3c525c342c28d627a38", "query": "EOF } <ins> function create-kubecontrollermanager-kubeconfig { echo \"Creating kube-controller-manager kubeconfig file\" mkdir -p /etc/srv/kubernetes/kube-controller-manager cat <<EOF >/etc/srv/kubernetes/kube-controller-manager/kubeconfig apiVersion: v1 kind: Config users: - name: kube-controller-manager user: token: ${KUBE_CONTROLLER_MANAGER_TOKEN} clusters: - name: local cluster: insecure-skip-tls-verify: true server: https://localhost:443 contexts: - context: cluster: local user: kube-controller-manager name: service-account-context current-context: service-account-context EOF } </ins> function create-master-etcd-auth { if [[ -n \"${ETCD_CA_CERT:-}\" && -n \"${ETCD_PEER_KEY:-}\" && -n \"${ETCD_PEER_CERT:-}\" ]]; then local -r auth_dir=\"/etc/srv/kubernetes\"", "positive_passages": [{"docid": "doc-en-kubernetes-19a61d82ec14336213ef377c4e39e11807c2ce9673880ce3d82a192d5a783624", "text": "Typically, the dns and dashboard is in crash loop. Ref cc\nif you check the file, does it contain lines like ?\nPrevious comment is ref: from I'll copy that to container-linux as well.", "commid": "kubernetes_issue_39395", "tokennum": 44}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0cb174e0b09b2124daa4d822b63b47427072e66fb1c268e8deec64b5df144a1e", "query": "\"path\" \"strings\" <del> \"k8s.io/api/core/v1\" </del> <ins> v1 \"k8s.io/api/core/v1\" </ins> \"k8s.io/apimachinery/pkg/types\" utilerrors \"k8s.io/apimachinery/pkg/util/errors\" utilfeature \"k8s.io/apiserver/pkg/util/feature\"", "positive_passages": [{"docid": "doc-en-kubernetes-b90c168e06a7b711f67a139e334802368690ddadfe42c413624f21a9b2a8ae1a", "text": "What happened: When debugging timeouts related to the stopping of cgroups, the current logs from -tryKillingCgroupProcesses do not provide any correlation between the PIDs which were killed and the cgroup they belonged to. What you expected to happen: Log the cgroup name along with the PID How to reproduce it (as minimally and precisely as possible): N/A Anything else we need to know?: N/A Environment: Kubernetes version (use ): master\n/sig node", "commid": "kubernetes_issue_83624", "tokennum": 111}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0cb2123cd1884514f4e53169459fe8a19c2868ddbd05cf5b5c7ea8b2a4b6d920", "query": "expectContinue(t, w, w.doProbe(ctx), msg) expectResult(t, w, results.Success, msg) } <del> func TestGetPodLabelName(t *testing.T) { testCases := []struct { name   string pod    *v1.Pod result string }{ { name: \"Static pod\", pod: &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name: \"kube-controller-manager-k8s-master-21385161-0\", }, }, result: \"kube-controller-manager-k8s-master-21385161-0\", }, { name: \"Deployment pod\", pod: &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name:         \"coredns-845757d86-ccqpf\", GenerateName: \"coredns-845757d86-\", Labels: map[string]string{ apps.DefaultDeploymentUniqueLabelKey: \"845757d86\", }, }, }, result: \"coredns\", }, { name: \"ReplicaSet pod\", pod: &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name:         \"kube-proxy-2gmqn\", GenerateName: \"kube-proxy-\", }, }, result: \"kube-proxy\", }, } for _, test := range testCases { ret := getPodLabelName(test.pod) if ret != test.result { t.Errorf(\"Expected %s, got %s\", test.result, ret) } } } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-8720ed8a574bdce7c104bd3a62cc93935fad36eef53bf2f2ff98186bbe4abc40", "text": "The metric used to report acutal pod in the label , but now I see the podname prefix only. The full pod name in the label, so I can trace the metric to the failing pod. Check raw api and verify the actual pod name with uids. <details</detailsAzure AKS <details</detailsNo response No response No response_\n/sig node\n/triage accepted /priority important-soon /cc As discussed this is a change in functionaloty that wasn't highlighted in release notes. Need to decide on what do do with it. I understand it's a change of functionality. what is the side effect of this for you? Does the label without last part not informational enough?\nI've been using the metric in my custom grafana dashboard that shows CPU, RAM, IO usage of pods with graph of increases in probes. If the apps are stable, the probe graph looks steadily. I can see if some irregularities in system metrics are influencing probes of respective pod. Also, if readiness probe is failing, the pod is removed from service, but is not restarted so I must have knowledge of pods with failing readiness probes. I attach the screenshot of my graph. ! So I'd welcome the possibility to pair the probes with exact pod and thank you for looking into it.\nare we thinking that this resulted in an undesirable change? Spologies for being a bit late to reply, I'm returning from a brief paternity leave staycation.\nThis issue is labeled with but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release. You can: Confirm that this issue is still relevant with (org members only) Deprioritize it with or Close this issue with For more details on the triage process, see /remove-triage accepted\nWell this is awkward... I still believe the actual behavior does not respect the intended idea...\nThis issue makes it hard to link probe metrics with right pods. The value of pod label in and are also inconsistent with how it is used in other kubelet metrics, see: vs Definitely a bug, regression since 1.25.\nI can't get anyone to look at the fix/revert: you may have better luck\n/milestone v1.28\ndiscussion in\nYou've pushed it through, congrats!", "commid": "kubernetes_issue_115766", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0cb4a75b0e11431bdc7eb22b5a7acb8073c63df27c61a3fdc4d824b127194287", "query": "return allErrs } <ins> func validateIPVSTimeout(config kubeproxyconfig.KubeProxyIPVSConfiguration, fldPath *field.Path) field.ErrorList { allErrs := field.ErrorList{} if config.TCPTimeout.Duration < 0 { allErrs = append(allErrs, field.Invalid(fldPath.Child(\"TCPTimeout\"), config.TCPTimeout, \"must be greater than or equal to 0\")) } if config.TCPFinTimeout.Duration < 0 { allErrs = append(allErrs, field.Invalid(fldPath.Child(\"TCPFinTimeout\"), config.TCPFinTimeout, \"must be greater than or equal to 0\")) } if config.UDPTimeout.Duration < 0 { allErrs = append(allErrs, field.Invalid(fldPath.Child(\"UDPTimeout\"), config.UDPTimeout, \"must be greater than or equal to 0\")) } return allErrs } </ins> func validateIPVSExcludeCIDRs(excludeCIDRs []string, fldPath *field.Path) field.ErrorList { allErrs := field.ErrorList{}", "positive_passages": [{"docid": "doc-en-kubernetes-be027d483b5644a511b34dd42acd191f0a8a8265cd239e919307434a4dbdd401", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: kube-proxy doesn't validate the configurable IPVS tcp, tcpfin and udp timeouts. For example, when kube-proxy starts with , it will always log a warning: . What you expected to happen: kube-proxy should validate --ipvs-tcp-timeout, --ipvs-tcpfin-timeout, --ipvs-udp-timeout flag values at start. How to reproduce it (as minimally and precisely as possible): add flags to kube-proxy Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig network /area ipvs\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d", "commid": "kubernetes_issue_88656", "tokennum": 269}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0cb7d3d532775a546f890a7704e763c6c3dbf66b22d1a382f0bcf8c474d0fed6", "query": "func k8sVolumeMount() api.VolumeMount { return api.VolumeMount{ <del> Name:      \"pki\", </del> <ins> Name:      \"k8s\", </ins> MountPath: \"/etc/kubernetes/\", ReadOnly:  true, }", "positive_passages": [{"docid": "doc-en-kubernetes-aa0efe62d493b3611250d6c4d1b34c71d8fe0e732e78e4445af443d5c2b2f03c", "text": "<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.--What keywords did you search in Kubernetes issues before filing this one? controller /etc/ssl/certs kubeadm /etc/ssl/certs Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT <!-- If this is a BUG REPORT, please: Fill in as much of the template below as you can. If you leave out information, we can't help you as well. If this is a FEATURE REQUEST, please: Describe in detail the feature/behavior/change you'd like to see. In both cases, be ready for followup questions, and please respond in a timely manner. If we can't reproduce a bug or think a feature already exists, we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why. --Kubernetes version (use ): 5 custom built master I also use a custom built hyperkube image instead of the single app images for apiserver, controller, ... Environment: Cloud provider or hardware configuration: azure OS (e.g. from /etc/os-release): CentOS 7.2 Kernel (e.g. ): Linux ma-kub8ms0 3.10.0-327.36.3.el7.x8664 SMP Mon Oct 24 16:09:20 UTC 2016 x8664 x8664 x8664 GNU/Linux Install tools: kubeadm Others: deployed with Azure RM template and ansible What happened: controller is not able to do https, including calls to the Azure RM API What you expected to happen: https should work as usual How to reproduce it (as minimally and precisely as possible): Use kubeadm to install kubernetes on CentOS exec into the controller and try \"curl \" Anything else do we need to know: It looks like caused this issue. On CentOS, I see these files on the host OS: I suspect the symlinks to /etc/pki/... being the problem here, as they are not available inside the hyperkube Debian image. I also tried to verify this with It seems to not be based on Debian and thus gives a different error: I see 2 possible solutions: of host mounting /etc/ssl/certs into the controller pod, the ca certificates could be installed into the image.", "commid": "kubernetes_issue_36150", "tokennum": 529}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0cb7d3d532775a546f890a7704e763c6c3dbf66b22d1a382f0bcf8c474d0fed6", "query": "func k8sVolumeMount() api.VolumeMount { return api.VolumeMount{ <del> Name:      \"pki\", </del> <ins> Name:      \"k8s\", </ins> MountPath: \"/etc/kubernetes/\", ReadOnly:  true, }", "positive_passages": [{"docid": "doc-en-kubernetes-41c6565c36e0283a9e2054713b809a870281386c810e77c1faf5476befe20dbf", "text": "This is already done for hyperkube and would work out of the box when the host mount would be omitted. could try to figure out if /etc/pki should also be host mounted and add this to the controller manifest if required. I'd be happy to provide a fix by myself, I just need to know which solution you would prefer.\nSame problem seems to apply to the apiserver. Not sure however if it actually does https calls.\nimplements solution 2.\nThis issue was moved to kubernetes/kubeadm", "commid": "kubernetes_issue_36150", "tokennum": 111}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0cf53afab6e1a371f73fb452be09998504ce88f67a645fb7c88619dbe17126bb", "query": "// ErrorNotVmssInstance indicates an instance is not belongint to any vmss. ErrorNotVmssInstance = errors.New(\"not a vmss instance\") <del> scaleSetNameRE        = regexp.MustCompile(`.*/subscriptions/(?:.*)/Microsoft.Compute/virtualMachineScaleSets/(.+)/virtualMachines(?:.*)`) resourceGroupRE       = regexp.MustCompile(`.*/subscriptions/(?:.*)/resourceGroups/(.+)/providers/Microsoft.Compute/virtualMachineScaleSets/(?:.*)/virtualMachines(?:.*)`) vmssMachineIDTemplate = \"/subscriptions/%s/resourceGroups/%s/providers/Microsoft.Compute/virtualMachineScaleSets/%s/virtualMachines/%s\" vmssIPConfigurationRE = regexp.MustCompile(`.*/subscriptions/(?:.*)/resourceGroups/(.+)/providers/Microsoft.Compute/virtualMachineScaleSets/(.+)/virtualMachines/(.+)/networkInterfaces(?:.*)`) </del> <ins> scaleSetNameRE         = regexp.MustCompile(`.*/subscriptions/(?:.*)/Microsoft.Compute/virtualMachineScaleSets/(.+)/virtualMachines(?:.*)`) resourceGroupRE        = regexp.MustCompile(`.*/subscriptions/(?:.*)/resourceGroups/(.+)/providers/Microsoft.Compute/virtualMachineScaleSets/(?:.*)/virtualMachines(?:.*)`) vmssMachineIDTemplate  = \"/subscriptions/%s/resourceGroups/%s/providers/Microsoft.Compute/virtualMachineScaleSets/%s/virtualMachines/%s\" vmssIPConfigurationRE  = regexp.MustCompile(`.*/subscriptions/(?:.*)/resourceGroups/(.+)/providers/Microsoft.Compute/virtualMachineScaleSets/(.+)/virtualMachines/(.+)/networkInterfaces(?:.*)`) vmssPIPConfigurationRE = regexp.MustCompile(`.*/subscriptions/(?:.*)/resourceGroups/(.+)/providers/Microsoft.Compute/virtualMachineScaleSets/(.+)/virtualMachines/(.+)/networkInterfaces/(.+)/ipConfigurations/(.+)/publicIPAddresses/(.+)`) </ins> ) // scaleSet implements VMSet interface for Azure scale set.", "positive_passages": [{"docid": "doc-en-kubernetes-c62a800befd6b705c74ea2036c66907711f830c03e53ca86df0e2014d6541d16", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Node external IP of azure VMSS cannot be obtained when cloud-controller-manager is enabled. Corresponding logs are shown as follows:\n/sig azure\n/milestone v1.16", "commid": "kubernetes_issue_80014", "tokennum": 92}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0d64135ab0b00b4058fb4103e07c20c3bc5a9861f187b52f4de338e7a1f6d2ee", "query": "// but no errors in the sections requested or referenced.  It does not return early so that it can find as many errors as possible. func (config *DirectClientConfig) ConfirmUsable() error { validationErrors := make([]error, 0) <ins> var contextName string if len(config.contextName) != 0 { contextName = config.contextName } else { contextName = config.config.CurrentContext } if len(contextName) > 0 { _, exists := config.config.Contexts[contextName] if !exists { validationErrors = append(validationErrors, &errContextNotFound{contextName}) } } </ins> validationErrors = append(validationErrors, validateAuthInfo(config.getAuthInfoName(), config.getAuthInfo())...) validationErrors = append(validationErrors, validateClusterInfo(config.getClusterName(), config.getCluster())...) // when direct client config is specified, and our only error is that no server is defined, we should", "positive_passages": [{"docid": "doc-en-kubernetes-f651131826f05881213cb9e37bd90a3c65eb2d3012bfdb53d9a39fc66f409d28", "text": "In 1.1, if you specify \"current-context: i-do-not-exist\" in a kubeconfig, and there's no matching context by that name in the contexts, kubelet silently uses what I assume is either an empty or a default configuration. This can result in hilarity like wondering why your kubelet isn't using the TLS settings you provided, and spending several hours debugging the whole stack only to discover that you typo'd current-context :). It would be better if kubelet and other users of errored out on such a misconfiguration, to make the failure obvious and trivial.\ncc\nI think kubelet silently uses an empty configuration. Guess we should give a waring here.\nDid you start to work on this?\nBelow is related code: can you confirm this? Besides if we want to log a waring in kubelet, we may need to get in kubelet.\ncc\ncc\nI believe kubelet already uses . Adding a check in that current context exists if specified sounds like the right approach.\nAre there any backwards compatibility implications here? would this break users who have existing configs (that fallback to default namespace)? , Jeff Lowdermilk wrote:\nI think kubelet directly use not . Also already checks whether the user-specified current context exists, the problem is that if not exist, we just skip. We need to do something if the current context not exist, like log a warning.\nErroring on a specified and bad seems reasonable. If it is not specified and there's only one option, I don't think we should fail.\nyeap, the case is that user specify the but not exist, in such case we should just fail.\nIf no one is working on this I can take it.\nI think this is the root cause. Basically we should error on this not exist context. If you have extra bandwidth, please go ahead :)\nThis is related to - the defaulting is what allows us to continue. When that merges, only kubectl will have the \"use localhost:8080\" as defaulting.", "commid": "kubernetes_issue_21062", "tokennum": 453}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0d75b449290453dfd7051e96e9b1641e79b051242d5d16979b0694c5a1106bde", "query": "exit 1 fi <del> APIROOT=\"${KUBE_ROOT}/pkg/api\" TMP_APIROOT=\"${KUBE_ROOT}/_tmp/api\" </del> <ins> DIFFROOT=\"${KUBE_ROOT}/pkg\" TMP_DIFFROOT=\"${KUBE_ROOT}/_tmp/pkg\" </ins> _tmp=\"${KUBE_ROOT}/_tmp\" mkdir -p \"${_tmp}\" <del> cp -a \"${APIROOT}\" \"${TMP_APIROOT}\" </del> <ins> cp -a \"${DIFFROOT}\" \"${TMP_DIFFROOT}\" </ins> \"${KUBE_ROOT}/hack/update-generated-swagger-docs.sh\" <del> echo \"diffing ${APIROOT} against freshly generated swagger type documentation\" </del> <ins> echo \"diffing ${DIFFROOT} against freshly generated swagger type documentation\" </ins> ret=0 <del> diff -Naupr -I 'Auto generated by' \"${APIROOT}\" \"${TMP_APIROOT}\" || ret=$? cp -a \"${TMP_APIROOT}\" \"${KUBE_ROOT}/pkg\" </del> <ins> diff -Naupr -I 'Auto generated by' \"${DIFFROOT}\" \"${TMP_DIFFROOT}\" || ret=$? cp -a \"${TMP_DIFFROOT}/\" \"${KUBE_ROOT}/\" </ins> rm -rf \"${_tmp}\" if [[ $ret -eq 0 ]] then <del> echo \"${APIROOT} up to date.\" </del> <ins> echo \"${DIFFROOT} up to date.\" </ins> else <del> echo \"${APIROOT} is out of date. Please run hack/update-generated-swagger-docs.sh\" </del> <ins> echo \"${DIFFROOT} is out of date. Please run hack/update-generated-swagger-docs.sh\" </ins> exit 1 fi", "positive_passages": [{"docid": "doc-en-kubernetes-e1455c8231c3d7b8e80cabcafbaabb5d8dbfa173f57128f88fd42bbd8e6a09fe", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Following the example in , I created a pod with 3 sysctls specified in the pod's security context. Setting the sysctl resulted in the pod failing to start. What you expected to happen: I expected the pod to start with no issues. If there is something missing in the docs, I appreciate updating There is also a discussion at that suggests that kernel does not namespace certain net.* sysctls. If that's the case, can we document which sysctls are supported? I assumed is a supported sysctl because it's in the official k8s docs. How to reproduce it (as minimally and precisely as possible): Following the pod creation, the pod doesn't start: Once I delete the following two lines from the pod securityContext, the pod starts fine: Anything else we need to know?: You can see that I've enabled the unsafe sysctls with kubelet: Environment: Kubernetes version (use ):Cloud provider or hardware configuration: VMware Fusion OS (e.g: ):Kernel (e.g. ):Install tools: A single-node k8s cluster created with kubeadm Network plugin and version (if this is a network-related bug): Calico Others:\n/sig node\nThank you for the incredibly detailed issue report :) I did some poking around, and if is accurate and still current, then I believe the issue is that is not namespaced (i.e. cannot be set on a per pod/container level). If I'm understanding correctly, we'd need to make changes to the Linux kernel in order for it to be namespaced. As a disclaimer, I'm not positive if this parameter became namespaced in new kernels... it could be interesting to investigate if this still happens on a machine with the latest kernel. W.r.t. fixes... I would agree with you that short term, we need to update this documentation so that it doesn't include . do you have any interest in doing so? If not, I'm happy to.", "commid": "kubernetes_issue_77546", "tokennum": 511}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0d75b449290453dfd7051e96e9b1641e79b051242d5d16979b0694c5a1106bde", "query": "exit 1 fi <del> APIROOT=\"${KUBE_ROOT}/pkg/api\" TMP_APIROOT=\"${KUBE_ROOT}/_tmp/api\" </del> <ins> DIFFROOT=\"${KUBE_ROOT}/pkg\" TMP_DIFFROOT=\"${KUBE_ROOT}/_tmp/pkg\" </ins> _tmp=\"${KUBE_ROOT}/_tmp\" mkdir -p \"${_tmp}\" <del> cp -a \"${APIROOT}\" \"${TMP_APIROOT}\" </del> <ins> cp -a \"${DIFFROOT}\" \"${TMP_DIFFROOT}\" </ins> \"${KUBE_ROOT}/hack/update-generated-swagger-docs.sh\" <del> echo \"diffing ${APIROOT} against freshly generated swagger type documentation\" </del> <ins> echo \"diffing ${DIFFROOT} against freshly generated swagger type documentation\" </ins> ret=0 <del> diff -Naupr -I 'Auto generated by' \"${APIROOT}\" \"${TMP_APIROOT}\" || ret=$? cp -a \"${TMP_APIROOT}\" \"${KUBE_ROOT}/pkg\" </del> <ins> diff -Naupr -I 'Auto generated by' \"${DIFFROOT}\" \"${TMP_DIFFROOT}\" || ret=$? cp -a \"${TMP_DIFFROOT}/\" \"${KUBE_ROOT}/\" </ins> rm -rf \"${_tmp}\" if [[ $ret -eq 0 ]] then <del> echo \"${APIROOT} up to date.\" </del> <ins> echo \"${DIFFROOT} up to date.\" </ins> else <del> echo \"${APIROOT} is out of date. Please run hack/update-generated-swagger-docs.sh\" </del> <ins> echo \"${DIFFROOT} is out of date. Please run hack/update-generated-swagger-docs.sh\" </ins> exit 1 fi", "positive_passages": [{"docid": "doc-en-kubernetes-29c4d3d8cbaaaaa0e62ad55e361fb5835540d2eb3a9414143acd94f95c7db66b", "text": "Long term, I think it would be great to have better documentation re which sysctl parameters are namespaced (and thus supported) and which ones are not, and also a more descriptive error message if you try and utilize a non-supported parameter.\nThis historic issue also seems relevant: Perhaps we were premature to close it.\nMatt, thanks for confirming the problem! I found the following comments very helpful: Looking at , there doesn't seem to be any difference between Linux 4.15 and 5.1. I'm happy to remove the references to in the docs, but before doing so, should we confirm sysctl worked at some point in the past? As you said, we should enhance the error message and the docs with the supported sysctls. I understand documenting the namespaced sysctls can be a moving target, but not everyone likes to check the Linux source code to see what's namespaced or not. :)\nIt's probably better to change the docs to set a namespaced sysctl like or . A good way to figure out what network sysctls are namespaced is to pass to kubelet and see all the sysctls listed under inside the pod.\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nAgree with all your statements here :) I'm also surprised that ever worked, but perhaps we could sync with the original author of the docs? +1 to in the meantime changing the docs to a namespaced sysctl.\nI don't think ever worked as it's hardly to believe a sysctl got unnamespacified in the kernel (it's always the other way around). is a good example of namespaced networking sysctl. However, the above suggested is not in some cases - it's unnamespaced in kernel 4.14 and became namespaced in 4.15. In general, this is hard to document because there are hundreds of parameters and some of them is kernel version dependent and you always need to lookup the kernel code for answers. I think what we should do now is to with in the example in the doc. in the doc to something like . I think this should be very close ( is an exception) - I couldn't verify all of them as there are so many sysctls and they can also be by loading kernel modules.\nSGTM, can you drive that?", "commid": "kubernetes_issue_77546", "tokennum": 525}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0d91aaa73e9c2d41966a9abb3b6625d2c0cdc68fc1727caa047339c6e694f459", "query": "\"${DOCKER[@]}\" rmi \"${release_docker_image_tag}\" 2>/dev/null || true \"${DOCKER[@]}\" tag \"${docker_image_tag}\" \"${release_docker_image_tag}\" 2>/dev/null fi <ins> else kube::log::status \"Not a release, so deleting docker image ${docker_image_tag}\" \"${DOCKER[@]}\" rmi ${docker_image_tag} 2>/dev/null || true </ins> fi <del> kube::log::status \"Deleting docker image ${docker_image_tag}\" \"${DOCKER[@]}\" rmi ${docker_image_tag} 2>/dev/null || true </del> ) & done", "positive_passages": [{"docid": "doc-en-kubernetes-2ba48dfbc5ff8b560d4d7fc12720c1689ab1c2d3bbdba3005ad7428905707669", "text": "Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT Kubernetes version (use ): HEAD Since v1.7.0-alpha.3, control plane images are only pushed for amd64. Compare: to This is a release-blocker and should be fixed ASAP. I guess the actual regression code-wise happened in test infra. cc\n/assign\nalso cc\n/remove-sig testing\nStill looking, but \"Only tag release containers if the name is different.\" makes me suspicious.\noh, this is a bug introduced by . fix should be easy.\nI can open a new issue as well to track what I sig-testing for but I want us to set up the required testing to make sure this never happens again\nthe removal was under the guise of \"sig testing doesn't control the cutting of bits\", if there are tests that need to be put in place to ensure all the right things are cut/released, I would expect sig-release to track that eg: if there's code that needs to be changed in kubernetes/release, it's a sig-release issue; if there's code that needs to be changed in kubernetes/test-infra, it might be a sig-testing issue (or we can triage to the right group)\nSounds good\nDetails about the exact bug and the fix are in . The reason we didn't notice this sooner is that anago only if the required image doesn't exist - it does so because we don't support all arches for all release versions, and we didn't want to hard-code a list of expected versions into the release repo. (Also, anago automatically , so we were still pushing the legacy versions - we were only dropping the non-amd64 images with this bug.)\nCan we add a after the warns? Otherwise even is the user of anago sees the warning, there's nothing he can do about it.\nAnago is moving toward being less interactive. If any checks need to be done, they should be done at build time. 1) Determine what should be built 2) Stop right there if the build fails for whatever reason. Adding redundant checks comes with the cost of maintaining hardcoded lists in multiple places. The push step (and release infra in general) should be agnostic and just push what was built.\nBut in this issue, the build was successful, but some images were removed due to the bug.", "commid": "kubernetes_issue_47307", "tokennum": 523}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0d91aaa73e9c2d41966a9abb3b6625d2c0cdc68fc1727caa047339c6e694f459", "query": "\"${DOCKER[@]}\" rmi \"${release_docker_image_tag}\" 2>/dev/null || true \"${DOCKER[@]}\" tag \"${docker_image_tag}\" \"${release_docker_image_tag}\" 2>/dev/null fi <ins> else kube::log::status \"Not a release, so deleting docker image ${docker_image_tag}\" \"${DOCKER[@]}\" rmi ${docker_image_tag} 2>/dev/null || true </ins> fi <del> kube::log::status \"Deleting docker image ${docker_image_tag}\" \"${DOCKER[@]}\" rmi ${docker_image_tag} 2>/dev/null || true </del> ) & done", "positive_passages": [{"docid": "doc-en-kubernetes-ecee26c3d0c9764e1c3372f00c48d9f570739b7afcc76ce0d3ff7c1362459190", "text": "I'm worried that when building beta.2 this Wednesday, if a similar problem happens, i won't be able to stop anago from pushing the incomplete image sets.\nI'm reopening this unless we are really sure that it actually works...\nHow can we create the testing required to stop this from happening again?\nI'm doing a dry run today.\nanago could have some sort of sanity checking, though I'm not sure how we'd do that without maintaining hardcoded lists, as notes. I guess the \"real\" fix is having some automated testing somewhere to consume the non-x86 docker images.\nAfter anago dry run, i saw these images on my machine, so it looks fixed.\nThanks and :tada:!", "commid": "kubernetes_issue_47307", "tokennum": 160}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0db40b513370e57d388c7494a635485273972f456cd6fb992474ad69c8193304", "query": "defer cancel() vsi, err := vs.getVSphereInstance(nodeName) if err != nil { <del> return false, err </del> <ins> return false, volPath, err </ins> } // Ensure client is logged in and session is valid err = vs.nodeManager.vcConnect(ctx, vsi) if err != nil { <del> return false, err </del> <ins> return false, volPath, err </ins> } vm, err := vs.getVMFromNodeName(ctx, nodeName) if err != nil { if err == vclib.ErrNoVMFound { klog.Warningf(\"Node %q does not exist, vsphere CP will assume disk %v is not attached to it.\", nodeName, volPath) // make the disk as detached and return false without error. <del> return false, nil </del> <ins> return false, volPath, nil </ins> } klog.Errorf(\"Failed to get VM object for node: %q. err: +%v\", vSphereInstance, err) <del> return false, err </del> <ins> return false, volPath, err </ins> } volPath = vclib.RemoveStorageClusterORFolderNameFromVDiskPath(volPath) <ins> canonicalPath, pathFetchErr := getcanonicalVolumePath(ctx, vm.Datacenter, volPath) // if canonicalPath is not empty string and pathFetchErr is nil then we can use canonical path to perform detach if canonicalPath != \"\" && pathFetchErr == nil { volPath = canonicalPath } </ins> attached, err := vm.IsDiskAttached(ctx, volPath) if err != nil { klog.Errorf(\"DiskIsAttached failed to determine whether disk %q is still attached on node %q\",", "positive_passages": [{"docid": "doc-en-kubernetes-e1df151812a738ca8d7e9f97519d671c643638f3ca9d9400cc430f5f7a7d204c", "text": "When user creates a static PV using folder name in path: on vSAN backed datastore then detach disk does not work because check fails - The code expects folder name to be UUID but it does not and hence it determines disk is not attached to the node and hence no detach is ever performed. /sig storage cc", "commid": "kubernetes_issue_95121", "tokennum": 68}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0db8b9a9963fe172f8c526f5dbad63325026a59f82106da42a11e780e7146730", "query": "// claimOwnerMatchesSetAndPod returns false if the ownerRefs of the claim are not set consistently with the // PVC deletion policy for the StatefulSet. func claimOwnerMatchesSetAndPod(claim *v1.PersistentVolumeClaim, set *apps.StatefulSet, pod *v1.Pod) bool { <del> policy := set.Spec.PersistentVolumeClaimRetentionPolicy </del> <ins> policy := getPersistentVolumeClaimRetentionPolicy(set) </ins> const retain = apps.RetainPersistentVolumeClaimRetentionPolicyType const delete = apps.DeletePersistentVolumeClaimRetentionPolicyType switch {", "positive_passages": [{"docid": "doc-en-kubernetes-0282c95c8ddc11607ba516e065f4121126017f786957d03a031978171c244a62", "text": "The replicas is 3 but just create 1 pod 'web-0' and one pvc, then kube-controller-manager panic happend. Should create 3 pod and 3 pvc add '--feature-gates=StatefulSetAutoDeletePVC=true' arg for kube-controller-manager, then create statefulset with 2 replicas and volumeClaimTemplates. No response <details</details<details</details<details</details<details</details<details</details<details</details\n/sig apps\nI can reproduce the issue and want to fix it. It seems like variables cause . /assign\n/triage accepted\nGreat find! Does this only happen on an upgraded cluster? I'll spin up a cluster and see if the e2e test catches this problem.\nThe e2e tests are still passing on a 1.24 cluster, so I suspect this is an upgrade problem. I wonder if there are other holes here.\nI installed the Kubernetes 1.25 cluster directly using and still reproduced this issue, so it was probably not caused by upgrading the cluster.\nInteresting. I thought that would set the policy to be non-nil. Let's keep this bug open after you submit your PR as I think something else is going on here---I don't think we should be seeing the null policy in the first place.\nI suspect that somewhere accidentally set it to nil, and I'll keep looking at this code.\nI tried the following (and also with parallel pod management), and it didn't seem to cause the panic. This was a 1.24 cluster, maybe this is only happening on head versions?\nI just tried this on a kind cluster running on k8s head, and the problem didn't seem to reproduce. But this was setting the feature flag default in I wonder----does the api server need to have the feature gate as well? That would explain why defaulting wasn't happening.\nAs far as I'm concerned,I just set the in kube-controller-manager manifests to reproduce this issue. I repeat the yaml used as follows: I tested that in statefulset yaml, setting or not would cause the component to panic. The panic logs are the same as above, so ignore them here.", "commid": "kubernetes_issue_113319", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0db8b9a9963fe172f8c526f5dbad63325026a59f82106da42a11e780e7146730", "query": "// claimOwnerMatchesSetAndPod returns false if the ownerRefs of the claim are not set consistently with the // PVC deletion policy for the StatefulSet. func claimOwnerMatchesSetAndPod(claim *v1.PersistentVolumeClaim, set *apps.StatefulSet, pod *v1.Pod) bool { <del> policy := set.Spec.PersistentVolumeClaimRetentionPolicy </del> <ins> policy := getPersistentVolumeClaimRetentionPolicy(set) </ins> const retain = apps.RetainPersistentVolumeClaimRetentionPolicyType const delete = apps.DeletePersistentVolumeClaimRetentionPolicyType switch {", "positive_passages": [{"docid": "doc-en-kubernetes-bacc559e7a05833801486ab81cebdf65b8969406a4ba99bead3e0d4a0613defb", "text": "statefulset with : The environment\nI believe you---this doesn't seem to be well-documented, but it's my understanding that you need to set the feature gate on all of the system components. Obviously failing to do so shouldn't cause a panic, so thank you again for finding & fixing this bug! Let me ask around to see what the expected behavior is. I know there may be skew between kubelets and master versions, but I didn't expect to have to deal with skew between master components.\nI read the code, and now I understand what you mean. This feature gate must be enabled in both the and components. We need to describe it in the to prevent someone from ignoring the component, which also needs to enable the feature gate.\nI don't think we need all the system components, like the component, right? I read the original KEP documentation. This feature gate only involves components and :\nI had a bit of discussion about this with others. Because upgrades don't occur atomically, any feature gate has to work regardless of how the other system components are configured (things shouldn't panic!). I suppose if the cluster administrator wants to track what needs to be enabled on each feature they can try to sequence which component has which feature gate. If it were me I'd try to make all the components consistent though.\nThis is certainly a method, but it is a bit more cumbersome for the administrator. It is best to have a place for the document to be queried by the administrator and avoid confusion. I don't think everyone is very familiar with the k8s mechanism. I suggest adding a partial description to this section of the : Before: After: I can submit this PR on .\nThis is going to be true of any api change. When you tried to use it with only adding the controller manager feature gate, I think you would be able to set the retain policy, but there wouldn't be any defaulting or validation (?).\nI've seen other feature gates that say what components are needed to enable it to use the new feature. For example: If it's not necessary, then I close .\nonly adding the controller manager feature gate, I think you would be able to set the retain policy, but there wouldn't be any defaulting or validation (?). I remember just enabling it in kube-controller-manager.", "commid": "kubernetes_issue_113319", "tokennum": 500}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0db8b9a9963fe172f8c526f5dbad63325026a59f82106da42a11e780e7146730", "query": "// claimOwnerMatchesSetAndPod returns false if the ownerRefs of the claim are not set consistently with the // PVC deletion policy for the StatefulSet. func claimOwnerMatchesSetAndPod(claim *v1.PersistentVolumeClaim, set *apps.StatefulSet, pod *v1.Pod) bool { <del> policy := set.Spec.PersistentVolumeClaimRetentionPolicy </del> <ins> policy := getPersistentVolumeClaimRetentionPolicy(set) </ins> const retain = apps.RetainPersistentVolumeClaimRetentionPolicyType const delete = apps.DeletePersistentVolumeClaimRetentionPolicyType switch {", "positive_passages": [{"docid": "doc-en-kubernetes-dc6539ce5e1daf74890724a45ab3f8f9d1791d28b0765a687405f604711fc05a", "text": "it using the retain policy, but the statefulset does not have the policy from output of (It should be the apiserver authentication forbids it)\nYeah I think that makes sense. Thanks for finding this issue! After your PR with the panic fix is submitted, I think we can close this?\nYes. I agree. /close\nClosing this issue. <detailsIn response to : Yes. I agree. 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", "commid": "kubernetes_issue_113319", "tokennum": 117}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0dd1aeb1f9045b954d321ac7cf8e31b292653024daaf39046e6fc0ad1d462bed", "query": "} } else { rawMgr := mngr.(*manager) <del> rawScope := rawMgr.scope.(*containerScope) if rawScope.policy.Name() != tc.expectedPolicy { t.Errorf(\"Unexpected policy name. Have: %q wants %q\", rawScope.policy.Name(), tc.expectedPolicy) </del> <ins> var policyName string if rawScope, ok := rawMgr.scope.(*containerScope); ok { policyName = rawScope.policy.Name() } else if rawScope, ok := rawMgr.scope.(*noneScope); ok { policyName = rawScope.policy.Name() } if policyName != tc.expectedPolicy { t.Errorf(\"Unexpected policy name. Have: %q wants %q\", policyName, tc.expectedPolicy) </ins> } } }", "positive_passages": [{"docid": "doc-en-kubernetes-4d10931e14d2065e9a15e6880eb555f03f2fd6b09352947daeddff0435b576bc", "text": "Follow up from: See details there. When is , there is no need to discover the NUMA topology. /sig node /priority backlog /kind feature /help-wanted\n/cc\n/triage accepted\nI would like to take this up also can I get more brief information about it? code review comments from asking that inside the NewManager() implementation, we need to skip NewPolicyOptions and NewNUMAInfo but when the NumaTopology comes kubelet issue also comes. I need some more information to start with this!\n/cc\nWhen there is no topology manger policy specified, NewManager should be a no-op. Just skip all checks.\nExactly. Just to add: we may need few iterations over the change to get a clean flow in the call.\n/assign", "commid": "kubernetes_issue_116391", "tokennum": 166}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0e0ee27d3740aa5cd317375f73e37dc0e8bb8ddd5e65afe004f45a31dfbea499", "query": "cidr.IP.To4()[3] += 1 json := fmt.Sprintf(NET_CONFIG_TEMPLATE, BridgeName, plugin.MTU, network.DefaultInterfaceName, podCIDR, cidr.IP.String()) <ins> glog.V(2).Infof(\"CNI network config set to %v\", json) </ins> plugin.netConfig, err = libcni.ConfFromBytes([]byte(json)) if err == nil { glog.V(5).Infof(\"CNI network config:n%s\", json)", "positive_passages": [{"docid": "doc-en-kubernetes-3e2b7d9568ee0bf267de4bcdac04137844677bca3ba3f5eceb5026951de8c86d", "text": "Event for a pod: The cni plugins do exist at /opt/cni/bin. They cannot be executed and bash is complaining:\ncc\nI'm guessing this is a shared lib problem, since /usr/grte/v4/lib64/ld-linux-x86- doesn't exist on my gce vm. We should update docs to make it clear how someone would install manually (if they run into such problems again) and statically link (if the problem is indeed the shared lib) with something like Unsure how we'd support different GOOS (vend different tarballs vs checking in and building the plugin inline with our make scripts)\nuggh. These binaries need to be ultra-static or else we need to containerize them.\nEssentially doing would've prevented this bug :)\nAnd see for the CNI_ARGS problems\nalso , re ... however, I'm not too sure if your comment was mean to be on this ticket.\ncc\nI have a working version. I uploaded my cni binary with bug fix on GCS. change source to change sourcehash to Welcome to give it a try.\nAlso see problem:", "commid": "kubernetes_issue_23011", "tokennum": 252}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0e1fea483f385fcc51ddfcd134fe4d99e06504b0a77ba026d173740a02202eb3", "query": "framework.ExpectNoError(err) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, webserverPod0.Name, f.Namespace.Name, framework.PodStartTimeout)) <del> validateEndpointsPortsOrFail(cs, ns, serviceName, portsByPodName{webserverPod0.Name: {servicePort}}) </del> <ins> validateEndpointsPortsOrFail(cs, ns, serviceName, portsByPodName{webserverPod0.Name: {endpointPort}}) </ins> <del> ginkgo.By(\"Creating 2 pause pods that will try to connect to the webservers\") </del> <ins> ginkgo.By(\"Creating 2 pause pods that will try to connect to the webserver\") </ins> pausePod0 := e2epod.NewAgnhostPod(ns, \"pause-pod-0\", nil, nil, nil) e2epod.SetNodeSelection(&pausePod0.Spec, e2epod.NodeSelection{Name: node0.Name})", "positive_passages": [{"docid": "doc-en-kubernetes-06e17cf980b6b4fe370857f0b2e0687536ee3b3b60ed1f78548a694def2f21f6", "text": "Failed here /retest Originally posted by in This fails because the pod tries to bind port 80, that is a very demanded port, but there are two tests doing that, that increase the chance to collide\n/sig network\nClose when merges\n/triage accepted", "commid": "kubernetes_issue_104406", "tokennum": 54}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0e22b66c887d330bf3531be45430d4734782b5fc7925f66e2e718a152ceca17f", "query": "result := make(chan T, 1) // non-blocking c.inFlight[key] = result go func() { <del> // Make potentially slow call </del> <ins> // Make potentially slow call. // While this call is in flight, fillOrWait will // presumably exit. </ins> data := timeCacheEntry{ item:       c.fillFunc(key), lastUpdate: c.clock.Now(),", "positive_passages": [{"docid": "doc-en-kubernetes-0882877f8aa87dd9f2fab7aa6c2163d630c073e98d0481f7c1762728faaae3b6", "text": "Failed due to an apparently unrelated PR: https://travis-\nProblem here is that I left a small chance of a double-call in my parallelized cache. Didn't realize this was being tested. Will fix.", "commid": "kubernetes_issue_3439", "tokennum": 46}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0e4e1829efc8af46d9d3be100e8488cf6ab7addf293e8a6c4e935d3c43ed0ed1", "query": "} // exampleCert was generated from crypto/tls/generate_cert.go with the following command: <del> //    go run generate_cert.go  --rsa-bits 512 --host example.com --ca --start-date \"Jan 1 00:00:00 1970\" --duration=1000000h </del> <ins> //    go run generate_cert.go  --rsa-bits 1024 --host example.com --ca --start-date \"Jan 1 00:00:00 1970\" --duration=1000000h </ins> var exampleCert = []byte(`-----BEGIN CERTIFICATE----- <del> MIIBdzCCASGgAwIBAgIRAOVTAdPnfbS5V85mfS90TfIwDQYJKoZIhvcNAQELBQAw EjEQMA4GA1UEChMHQWNtZSBDbzAgFw03MDAxMDEwMDAwMDBaGA8yMDg0MDEyOTE2 MDAwMFowEjEQMA4GA1UEChMHQWNtZSBDbzBcMA0GCSqGSIb3DQEBAQUAA0sAMEgC QQCoVSqeu8TBvF+70T7Jm4340YQNhds6IxjRoifenYodAO1dnKGrcbF266DJGunh nIjQH7B12tduhl0fLK4Ezf7/AgMBAAGjUDBOMA4GA1UdDwEB/wQEAwICpDATBgNV HSUEDDAKBggrBgEFBQcDATAPBgNVHRMBAf8EBTADAQH/MBYGA1UdEQQPMA2CC2V4 YW1wbGUuY29tMA0GCSqGSIb3DQEBCwUAA0EAk1kVa5uZ/AzwYDVcS9bpM/czwjjV xq3VeSCfmNa2uNjbFvodmCRwZOHUvipAMGCUCV6j5vMrJ8eMj8tCQ36W9A== </del> <ins> MIIB+zCCAWSgAwIBAgIQArqTHmCaW6G843kgXgy12DANBgkqhkiG9w0BAQsFADAS MRAwDgYDVQQKEwdBY21lIENvMCAXDTcwMDEwMTAwMDAwMFoYDzIwODQwMTI5MTYw MDAwWjASMRAwDgYDVQQKEwdBY21lIENvMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCB iQKBgQDSt6+lUEp2Fk8OcLuPz3Z9lrPSDFnfLz30RrA3DaZlVgeNVzyrOsxQuRp+ 9wgljadxVEDMY69x8NDJnC0mem7kYaIt+gyEtxAPqo7wrsqT17g9MGBQbthtpFeZ jEPrL9aqAhY9O8kFN2iWkEf8kU2+MGwsaoK/icQH+eyFQ+/VuQIDAQABo1AwTjAO BgNVHQ8BAf8EBAMCAqQwEwYDVR0lBAwwCgYIKwYBBQUHAwEwDwYDVR0TAQH/BAUw AwEB/zAWBgNVHREEDzANggtleGFtcGxlLmNvbTANBgkqhkiG9w0BAQsFAAOBgQAy fpch5gzwsQucZ1pIAj4qZ3wku3mJiXzUtjHBiTkYpwcCMvH2JxNZWTzGQKSO7eJH hbmHPOfUbr6UazRiVqJuRJ6oI1iHnTFJxELuIx/mM+YThzdZjlq9Dn8VxkZwMpOI ru5O2VXdMHW/wpK4kCy+FI+VazpHHyPUSMHFVr0Wjw== </ins> -----END CERTIFICATE-----`) var exampleKey = []byte(`-----BEGIN RSA PRIVATE KEY----- <del> MIIBOgIBAAJBAKhVKp67xMG8X7vRPsmbjfjRhA2F2zojGNGiJ96dih0A7V2coatx sXbroMka6eGciNAfsHXa126GXR8srgTN/v8CAwEAAQJASdzdD7vKsUwMIejGCUb1 fAnLTPfAY3lFCa+CmR89nE22dAoRDv+5RbnBsZ58BazPNJHrsVPRlfXB3OQmSQr0 SQIhANoJhs+xOJE/i8nJv0uAbzKyiD1YkvRkta0GpUOULyAVAiEAxaQus3E/SuqD P7y5NeJnE7X6XkyC35zrsJRkz7orE8MCIHdDjsI8pjyNDeGqwUCDWE/a6DrmIDwe emHSqMN2YvChAiEAnxLCM9NWaenOsaIoP+J1rDuvw+4499nJKVqGuVrSCRkCIEqK 4KSchPMc3x8M/uhw9oWTtKFmjA/PPh0FsWCdKrEy </del> <ins> MIICdwIBADANBgkqhkiG9w0BAQEFAASCAmEwggJdAgEAAoGBANK3r6VQSnYWTw5w u4/Pdn2Ws9IMWd8vPfRGsDcNpmVWB41XPKs6zFC5Gn73CCWNp3FUQMxjr3Hw0Mmc LSZ6buRhoi36DIS3EA+qjvCuypPXuD0wYFBu2G2kV5mMQ+sv1qoCFj07yQU3aJaQ R/yRTb4wbCxqgr+JxAf57IVD79W5AgMBAAECgYEAuOSGUZbnD0C586DFYwWWIdK3 TCqcPTJ1uT7BZj0q8SYQkFuol1KLbpVNA3T9B/6Imu9jwDQEAQVeHllUYLvzSggt n8C3bytUfKYNQbj0729EapygQ0Xda5ZTZYIjz312mfwdIIs8A5/taBQU5j3ku9Lg PPinOXZqiYAMNpTHswECQQDoaIXHTdzPGB9KSMc2Htg2xbRptJ5aYAYic1VXiXDO XB2XzVYiUrQ/+Bs2gyjtoJyfOWjoN1qlDdN4V7ETSnAhAkEA6Bt/GQoPjb3BE/CQ ZU6c9+VaY2RWoFemiE+rxRt78Av5F+0c5KufYpJNUktd/1NJUsiyNJHkYFnpOU7R OICSmQJBAOB3443l9DjJcZ9Lv6zUCbyNI31dB/z99a7cejb79ko5yhNOLb0k6BdI yO/TqnoowF1BE8QFgrUcL31yJQMeyEECQCJM9fJoVzYWJbNhqKUgAfhsb3giut6F NXoNdA/z6NPnoQ8VHmD4r9wsTLrtol16HGrcd+Fm8f3/K4Upjaew8HkCQEQLBYeI VR3mybfS4TQE+4jX/PrgOAXGhKjdmtPqqaqk5KAfZUwR86kFXtVFH/TwKGQAwL1T awwC4qga/9zIa6U= </ins> -----END RSA PRIVATE KEY-----`) // localhostCert was generated from crypto/tls/generate_cert.go with the following command: <del> //     go run generate_cert.go  --rsa-bits 512 --host 127.0.0.1,::1,example.com --ca --start-date \"Jan 1 00:00:00 1970\" --duration=1000000h </del> <ins> //     go run generate_cert.go  --rsa-bits 1024 --host 127.0.0.1,::1,example.com --ca --start-date \"Jan 1 00:00:00 1970\" --duration=1000000h </ins> var localhostCert = []byte(`-----BEGIN CERTIFICATE----- <del> MIIBjzCCATmgAwIBAgIRAKpi2WmTcFrVjxrl5n5YDUEwDQYJKoZIhvcNAQELBQAw EjEQMA4GA1UEChMHQWNtZSBDbzAgFw03MDAxMDEwMDAwMDBaGA8yMDg0MDEyOTE2 MDAwMFowEjEQMA4GA1UEChMHQWNtZSBDbzBcMA0GCSqGSIb3DQEBAQUAA0sAMEgC QQC9fEbRszP3t14Gr4oahV7zFObBI4TfA5i7YnlMXeLinb7MnvT4bkfOJzE6zktn 59zP7UiHs3l4YOuqrjiwM413AgMBAAGjaDBmMA4GA1UdDwEB/wQEAwICpDATBgNV HSUEDDAKBggrBgEFBQcDATAPBgNVHRMBAf8EBTADAQH/MC4GA1UdEQQnMCWCC2V4 YW1wbGUuY29thwR/AAABhxAAAAAAAAAAAAAAAAAAAAABMA0GCSqGSIb3DQEBCwUA A0EAUsVE6KMnza/ZbodLlyeMzdo7EM/5nb5ywyOxgIOCf0OOLHsPS9ueGLQX9HEG //yjTXuhNcUugExIjM/AIwAZPQ== </del> <ins> MIICEzCCAXygAwIBAgIQZYovfgbbbhbli5vN0HAfKzANBgkqhkiG9w0BAQsFADAS MRAwDgYDVQQKEwdBY21lIENvMCAXDTcwMDEwMTAwMDAwMFoYDzIwODQwMTI5MTYw MDAwWjASMRAwDgYDVQQKEwdBY21lIENvMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCB iQKBgQDm4Srs2LoP4+Yotx7M+itbWen7IbdHVPmIfguzzzFEzXJlc/ipeQ8uze15 gWFwBbY2Cvdy1LU3oItO8X1/75Cx/66B+tdhENExe6w5gZPqNPXhf9ei2vJ0jdEu MedteXu9AqAKJBU23H5HBlaTr2irNCBGc77K2pQt0a9DLSdMCQIDAQABo2gwZjAO BgNVHQ8BAf8EBAMCAqQwEwYDVR0lBAwwCgYIKwYBBQUHAwEwDwYDVR0TAQH/BAUw AwEB/zAuBgNVHREEJzAlggtleGFtcGxlLmNvbYcEfwAAAYcQAAAAAAAAAAAAAAAA AAAAATANBgkqhkiG9w0BAQsFAAOBgQDDG08vFeL8353MsLbRwqUZ6uwa+w1SnMFu +gjgJhVcPhS7n4H8J8wanAjzikomOZVfUdkz5n2PE6ShQyXeu7LAN63abvWVcfyl g7RVq3/Pryhah21lyOxVr11EjsCaEeiGO1WuzOEdIOFD9BXJEhg+HRN9gxv/HrRg fHSFpMgCwA== </ins> -----END CERTIFICATE-----`) // localhostKey is the private key for localhostCert. var localhostKey = []byte(`-----BEGIN RSA PRIVATE KEY----- <del> MIIBOwIBAAJBAL18RtGzM/e3XgavihqFXvMU5sEjhN8DmLtieUxd4uKdvsye9Phu R84nMTrOS2fn3M/tSIezeXhg66quOLAzjXcCAwEAAQJBAKcRxH9wuglYLBdI/0OT BLzfWPZCEw1vZmMR2FF1Fm8nkNOVDPleeVGTWoOEcYYlQbpTmkGSxJ6ya+hqRi6x goECIQDx3+X49fwpL6B5qpJIJMyZBSCuMhH4B7JevhGGFENi3wIhAMiNJN5Q3UkL IuSvv03kaPR5XVQ99/UeEetUgGvBcABpAiBJSBzVITIVCGkGc7d+RCf49KTCIklv bGWObufAR8Ni4QIgWpILjW8dkGg8GOUZ0zaNA6Nvt6TIv2UWGJ4v5PoV98kCIQDx rIiZs5QbKdycsv9gQJzwQAogC8o04X3Zz3dsoX+h4A== </del> <ins> MIICdwIBADANBgkqhkiG9w0BAQEFAASCAmEwggJdAgEAAoGBAObhKuzYug/j5ii3 Hsz6K1tZ6fsht0dU+Yh+C7PPMUTNcmVz+Kl5Dy7N7XmBYXAFtjYK93LUtTegi07x fX/vkLH/roH612EQ0TF7rDmBk+o09eF/16La8nSN0S4x5215e70CoAokFTbcfkcG VpOvaKs0IEZzvsralC3Rr0MtJ0wJAgMBAAECgYBN4IG0Jl6MYZkO/sW66l+Zjrin 5vWFcBpDehDEdAzwYkRGCFpF//mpFfkWVRfiy2pszEIvT6RYwSR8WmS0tMAfRkE/ apJ7w9v7ghhIMXKuO/ohLyHi5hgPWy1L4+gje4YB+TsZftcDxEVklIplUv8eC9cU NBP49S/tKLaLg+baCQJBAOuEFAfglYZKlXZ9d8mSPAOTCEvV7e/RFDI8w8OUdcyE zSB5kx0lS3DFY5AirmpPswB1lupdxec1B9FWSE/CoU8CQQD69duGx5DM7oSCw8Wo x5KljuMxs4mbfcXEGS+oP++khEWoa5evW+m3EzrxLVHDgYG+pMdy3UROXIzmHARm 63cnAkBWSHs2L5dYLbb4RBtAo+yMuq9NaUDUnVqy1QQ7gQZvOTAVd7Tn9qPe2tIR GkOf+zbvMiVqE5TPkeQdU2kGn52NAkEAtzRyTSM1BxX8sIWAr2T6HliAbREXHOcl T7HfQ6FhLaXOQFRDSKX9qUOlnNkrvmC1udoLLERxkA8qYPYFFKlCswJBANQJf9j5 mhgfW8Z7iyQboufgSUq4UYJPpevEfLWAg6809sWHhzeg8AHOH8rap1Z97PUjeeWf XbCRvoe8v2wSoo0= </ins> -----END RSA PRIVATE KEY-----`)", "positive_passages": [{"docid": "doc-en-kubernetes-c0ae7c5a9b926980f7fbe5b2efcf245b830bbe6bb1b2519b4aac2b3a38b48ce6", "text": "Golang 1.13 uses TLS 1.13 by default (opt-out), which introduces RSA-PSS. RSA-PSS does not work with keys that are too small. The issue was uncovered during Fedora mass rebuild which uses Golang 1.13: See /sig api-machinery\nWhat is the failure mode if a smaller key is used?\n/sig auth /sig scalability\n/sub", "commid": "kubernetes_issue_80733", "tokennum": 90}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0e5a4474c58195a3b8859ef50ca44aa752bc0e238c33df258ac70f4dd45cd73e", "query": "} // Fail if there are other errors. <del> if len(errors) > 0 { return utilerrors.Flatten(utilerrors.NewAggregate(errors)) </del> <ins> if len(allErrs) > 0 { return utilerrors.Flatten(utilerrors.NewAggregate(allErrs)) </ins> } // Ensure the backendPoolID is also deleted on VMSS itself.", "positive_passages": [{"docid": "doc-en-kubernetes-27479256c4cd4a81489a76c239bc26b6dc52b8a0b6a444f52adbe9ce38513013", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --/kind bug /sig cloud-provider /area provider/azure Azure in-tree CCM fails to delete a load balancer: The corresponding logs: The clouprovider config is: The Nodes are actually Azure VMs that belong to a VMO (aka vmss with flexible orchestration mode) - regular VMs and managed independently of the vmss. So those VMs are managed on Azure as . LoadBalancer deletion works with the very same setup with v1.21.1 of the in-tree Azure CCM. After recent cherry-picks, with v1.21.4 we observe the failure above. a cluster using VMs that belong to a VMO a Service of type LoadBalancer the Service of type LoadBalancer sure that the deletion fails with: Kubernetes version (use ): v1.21.4 Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Gardener Network plugin and version (if this is a network-related bug): Others:\n/assign /triage accepted", "commid": "kubernetes_issue_105184", "tokennum": 289}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0e8c4ed2343887927a45c8688462896c312c6677d6aaaaf21fa2acdbd2e67498", "query": "// the cluster is restored to health. ginkgo.By(\"waiting for system pods to successfully restart\") err := e2epod.WaitForPodsRunningReady(c, metav1.NamespaceSystem, systemPodsNo, 0, framework.PodReadyBeforeTimeout, map[string]string{}) <del> framework.ExpectEqual(err, nil) </del> <ins> framework.ExpectNoError(err) </ins> }) ginkgo.It(\"node lease should be deleted when corresponding node is deleted\", func() { leaseClient := c.CoordinationV1().Leases(v1.NamespaceNodeLease) err := e2enode.WaitForReadyNodes(c, framework.TestContext.CloudConfig.NumNodes, 10*time.Minute) <del> framework.ExpectEqual(err, nil) </del> <ins> framework.ExpectNoError(err) </ins> ginkgo.By(\"verify node lease exists for every nodes\") originalNodes, err := e2enode.GetReadySchedulableNodes(c)", "positive_passages": [{"docid": "doc-en-kubernetes-4d7af6d1d5d1ba0c7ab59da9ea13925b54c282d46d48402ebb3f5409fd2b1204", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: kubernetes/node-problem-detector/node-problem-detector-ci: ci-npd-e2e-node See the Which test(s) are failing: [] NodeProblemDetector [NodeFeature:NodeProblemDetector] [] SystemLogMonitor should generate node condition and events for corresponding errors Since when has it been failing: Dec 03. was at 19:50 PST, was at 21:51 PST. Testgrid link: https://k8s- Reason for failure: Apparently is the culprit. Anything else we need to know: This is likely caused by some library upgrade. Nothing big.\n/sig node\n/assign\nSeems like the failure is caused by . /cc /cc /cc /cc\n/priority critical-urgent\nThe particular bug I care about has been fixed in . I'm gonna still work on submitting , as the same error should also be affecting a few other tests.", "commid": "kubernetes_issue_85933", "tokennum": 235}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0eb33793590f16ee7ffb6327842a883f5bc8a89dc94cb4eecb24870e18b007fa", "query": "SCHEDULER_TEST_ARGS=\"${SCHEDULER_TEST_ARGS:-} ${TEST_CLUSTER_API_CONTENT_TYPE}\" KUBEPROXY_TEST_ARGS=\"${KUBEPROXY_TEST_ARGS:-} ${TEST_CLUSTER_API_CONTENT_TYPE}\" <ins> # Historically fluentd was a manifest pod and then was migrated to DaemonSet. # To avoid situation during cluster upgrade when there are two instances # of fluentd running on a node, kubelet need to mark node on which # fluentd is not running as a manifest pod with appropriate label. # TODO(piosz): remove this in 1.8 NODE_LABELS=\"${KUBE_NODE_LABELS:-alpha.kubernetes.io/fluentd-ds-ready=true}\" </ins> # Optional: Enable node logging. ENABLE_NODE_LOGGING=\"${KUBE_ENABLE_NODE_LOGGING:-true}\" LOGGING_DESTINATION=\"${KUBE_LOGGING_DESTINATION:-gcp}\" # options: elasticsearch, gcp", "positive_passages": [{"docid": "doc-en-kubernetes-3936c52aacccf581fb5174635de31acc9a85b981ebc339b83016fc7b6087f92b", "text": "PR introduced an annotation for fluentd migration from static pod to the daemonset to avoid two instances of fluentd on a single node during the transition stage. I didn't read the pr carefully, but based on the code at , every node object has one label be default: \"\". I think this is wrong. 1) Not everyone use fluentd as the logging agent. 2) It is hard-coded in Kubelet code as part of kubeletnodestatus. No matter running fluentd as a static pod or a daemonset on the node, Kubelet shouldn't treat it different from other pods. The right approach is introducing an external controller to apply this cloud-provider / kubernetes vendor (i.e. GKE) specific label to the node. cc/\nThe string \"fluentd\" shouldn't appear anywhere in our code. Please remove it ASAP.\nAbsolutely agree with you, thanks for bringing this up! Is it possible to apply labels to the node as part of the node startup script/salt?\nTo clarify, I'm thinking about possible ways to provide a fix for that ASAP. Writing external controller is a best solution, but here we have a release coming and this label is intended to be only a temporary measure to perform upgrade from using fluentd as static pods to using daemon set.\nThere are many ways to achieve this outside the core system. But I believe GKE already has an existing mechanism to add this kind of labels to the node, and the consistency is important for GKE management. cc/\nOK, thanks! However, I believe we should be sure not to break everyone's upgrade process, i.e. after master upgrade to 1.6 on any platform, there should be only one fluentd agent on each node. I propose changing the configure scripts and salt to set up needed labels in kubelet's flag (). WDYT?\nIt seems to me like upgrades could survive without the explicit dependency on fluentd: I'm not sure if upgrades call initialNode or not, my own ignorance ? If they do, and this is removed, can't an external controller just do the work of re--adding that label if its dropped?\nthanks for raising this. Let's sync f2f\ncc\nWDYT about exposing kubelet version as a label and have a selector in fluentd ds config targeting version 1.6+?", "commid": "kubernetes_issue_42840", "tokennum": 508}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0eb33793590f16ee7ffb6327842a883f5bc8a89dc94cb4eecb24870e18b007fa", "query": "SCHEDULER_TEST_ARGS=\"${SCHEDULER_TEST_ARGS:-} ${TEST_CLUSTER_API_CONTENT_TYPE}\" KUBEPROXY_TEST_ARGS=\"${KUBEPROXY_TEST_ARGS:-} ${TEST_CLUSTER_API_CONTENT_TYPE}\" <ins> # Historically fluentd was a manifest pod and then was migrated to DaemonSet. # To avoid situation during cluster upgrade when there are two instances # of fluentd running on a node, kubelet need to mark node on which # fluentd is not running as a manifest pod with appropriate label. # TODO(piosz): remove this in 1.8 NODE_LABELS=\"${KUBE_NODE_LABELS:-alpha.kubernetes.io/fluentd-ds-ready=true}\" </ins> # Optional: Enable node logging. ENABLE_NODE_LOGGING=\"${KUBE_ENABLE_NODE_LOGGING:-true}\" LOGGING_DESTINATION=\"${KUBE_LOGGING_DESTINATION:-gcp}\" # options: elasticsearch, gcp", "positive_passages": [{"docid": "doc-en-kubernetes-4cb16c5ce2a173a3021e859767a51a1df9544dd94429e93c357c1a133ef72828", "text": "and I talked about this issue a bit for migrating kube-proxy. One idea we came up with was that of running a controller that will identify kubelet versions and apply taints to nodes running static pods. The daemonset version would not tolerate that taint and that way we keep daemon set pods off of nodes running static pods. Have you considered that approach?\nIt doesn't differ from a controller applying labels. I'd like to avoid necessity of introducing such controller, since it's not clear what is it's responsibility (generic controller for applying labels on nodes based on some rules? a custom controller just for fluentd purposes). In GKE we can do it on GKE control plane side, but we need a story for open source.\nMove applying labels to startup scripts/salt seems to be the least intrusive and easiest to implement way.\nActually what I proposed in is not an option since nodeSelector in PodSpec is old style selector.\nI'm not a big fan of approach with salt, but it seems there is no better option.\nRe: Instead of exposing Kubelet version as a label, why not using field selector. Kubelet version is part of NodeStatus already. I just simply don't want to have a duplicate info for the same object.\nis it possible to schedule based on fieldselector? I'm only aware of using field selector while listing objects.\nAlso node-labels option is in alpha\nBut it's present since 1.2 What is the status of this flag? Can we use it for fluentd purposes or better avoid this?\nMaybe it does make sense to implement a temporary ad-hoc controller? It's the easiest to deploy solution, just another in fluentd addon.\nI know. It totally doesn't make sense to introduce anything custom. I'll use just the flag. It's rather hacky but unfortunately I can't see anything better.\nCool thing about controller is that you can deploy it into any cluster and it will work, with CA also. You don't have to set up your node labels manually then or restart the cluster.\nThere is a number of open question with having a new controller: it run on the master or a node? we guarantee that it will be always running? it have any resource requirements? I'd like to avoid discussing it right before the release.\nHaving a controller will help with kube-proxy transition too in the future.", "commid": "kubernetes_issue_42840", "tokennum": 507}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0eb33793590f16ee7ffb6327842a883f5bc8a89dc94cb4eecb24870e18b007fa", "query": "SCHEDULER_TEST_ARGS=\"${SCHEDULER_TEST_ARGS:-} ${TEST_CLUSTER_API_CONTENT_TYPE}\" KUBEPROXY_TEST_ARGS=\"${KUBEPROXY_TEST_ARGS:-} ${TEST_CLUSTER_API_CONTENT_TYPE}\" <ins> # Historically fluentd was a manifest pod and then was migrated to DaemonSet. # To avoid situation during cluster upgrade when there are two instances # of fluentd running on a node, kubelet need to mark node on which # fluentd is not running as a manifest pod with appropriate label. # TODO(piosz): remove this in 1.8 NODE_LABELS=\"${KUBE_NODE_LABELS:-alpha.kubernetes.io/fluentd-ds-ready=true}\" </ins> # Optional: Enable node logging. ENABLE_NODE_LOGGING=\"${KUBE_ENABLE_NODE_LOGGING:-true}\" LOGGING_DESTINATION=\"${KUBE_LOGGING_DESTINATION:-gcp}\" # options: elasticsearch, gcp", "positive_passages": [{"docid": "doc-en-kubernetes-3203f30994cf42c5336d5a6d0dc1585171cc98cff1719959478ccaf13036f1c4", "text": ", Piotr Szczesniak <:\nis this a 1.6 release blocker?\nI think yes. The PR is already sent and approved. I need to fix e2e tests because it doesn't work well with the test infra (e2e tests passes locally). EDIT: I'll do it hopefully today.\nThe PR is ready to be merged and lgtmed. Waiting for approvals.", "commid": "kubernetes_issue_42840", "tokennum": 89}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0edb3e6dcf1709154b9a5029060dc17a89db1541663fbb056ee79d93f5e3110f", "query": "return s.converter.Convert(src, dest, flags, s.meta) } <ins> // DefaultConvert continues a conversion, performing a default conversion (no conversion func) // for the current stack frame. func (s *scope) DefaultConvert(src, dest interface{}, flags FieldMatchingFlags) error { return s.converter.DefaultConvert(src, dest, flags, s.meta) } </ins> // SrcTag returns the tag of the struct containing the current source item, if any. func (s *scope) SrcTag() reflect.StructTag { return s.srcStack.top().tag", "positive_passages": [{"docid": "doc-en-kubernetes-518f837785f17a5fd9706a6c0a0614adac703d65f6bb6045d79a025795dcb97b", "text": "Files storing latest versions for minors are not updated since infix was to the version string. Example Similar issues can be found in 1.25 and 1.24 builds (last 1.23 build infix so it has not happened there yet): I expect the files to be overwritten with newer version of the build. Manually run build job for one of the minors. No response Not related. Not related. No response No response No response No response\nI believe this may be also responsible for breaking kubemark tests: since they fail due to version mismatch\n/sig release\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority high 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\nThanks for raising the issue! /cc who is working on before\nI assume this will be fixed automatically with the next patches, because then we would compare with . Anyway, I think we should fix that intermediately by manually updating the version markers to match their correct version. I did that now for the bucket\nWe had to update the versions markers again, because those were pointing to two commits earlier and didn't include the Go updates. The latest version markers are: v1.24.12-35+ v1.25.8-37+ v1.26.3-41+\nlatest-1.27 has been affected by this as well. I updated it manually to v1.27.0-9+. See this thread for more details:\n/triage accepted\nThis should be fixed now, closing it. Feel free to reopen if we missed anything.\nThis issue is still present, see this Slack thread for more details: /reopen\nReopened this issue. <detailsIn response to : This issue is still present, see this Slack thread for more details: /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nWe have a similar situation with latest-1.28 which is currently pointing to: . This is one commit before the release commit: ! It's mostly like that the release step didn't update version markers, we should look into this.", "commid": "kubernetes_issue_117115", "tokennum": 486}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0edb3e6dcf1709154b9a5029060dc17a89db1541663fbb056ee79d93f5e3110f", "query": "return s.converter.Convert(src, dest, flags, s.meta) } <ins> // DefaultConvert continues a conversion, performing a default conversion (no conversion func) // for the current stack frame. func (s *scope) DefaultConvert(src, dest interface{}, flags FieldMatchingFlags) error { return s.converter.DefaultConvert(src, dest, flags, s.meta) } </ins> // SrcTag returns the tag of the struct containing the current source item, if any. func (s *scope) SrcTag() reflect.StructTag { return s.srcStack.top().tag", "positive_passages": [{"docid": "doc-en-kubernetes-5a00e106d863b6b2d6ffe122805a64f76a2709c3a46b9a75024b175401623671", "text": "As of now, I'm going to manually update this version marker to unblock 1.28.1 patch release. I'll also take a look into this. /assign\nThe PR that fixed this issue got reverted so this is still relevant: /reopen\nReopened this issue. <detailsIn response to : The PR that fixed this issue got reverted so this is still relevant: /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nWe're running into this issue again with stable-1.29 marker. It's currently pointing to which is It should instead point to I'm going to manually change it following the same procedure as the last time. Version marker updated to\nThis issue is labeled with but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release. You can: Confirm that this issue is still relevant with (org members only) Deprioritize it with or Close this issue with For more details on the triage process, see /remove-triage accepted\n/triage accepted\nSame issue for 1.30, where I had to update the version marker manually again.", "commid": "kubernetes_issue_117115", "tokennum": 278}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0ee0fa0252d544b835406a3956fb0b808f275127294f689d9f80d60f7b1133b9", "query": "<ins> ./build/build-image/rsyncd.sh ./build/common.sh ./build/copy-output.sh ./build/lib/release.sh ./build/make-build-image.sh ./build/make-clean.sh ./build/package-tarballs.sh ./build/release-images.sh ./build/release-in-a-container.sh ./build/release.sh ./build/run.sh ./build/shell.sh ./build/util.sh ./cluster/addons/addon-manager/kube-addons.sh ./cluster/addons/fluentd-elasticsearch/es-image/run.sh ./cluster/addons/fluentd-elasticsearch/fluentd-es-image/run.sh ./cluster/centos/build.sh ./cluster/centos/config-build.sh ./cluster/centos/config-default.sh ./cluster/centos/config-test.sh ./cluster/centos/deployAddons.sh ./cluster/centos/make-ca-cert.sh ./cluster/centos/master/scripts/flannel.sh ./cluster/centos/node/bin/mk-docker-opts.sh ./cluster/centos/node/scripts/flannel.sh ./cluster/centos/util.sh ./cluster/clientbin.sh ./cluster/common.sh ./cluster/gce/config-common.sh ./cluster/gce/config-default.sh ./cluster/gce/config-test.sh ./cluster/gce/delete-stranded-load-balancers.sh ./cluster/gce/gci/configure-helper.sh ./cluster/gce/gci/configure.sh ./cluster/gce/gci/flexvolume_node_setup.sh ./cluster/gce/gci/health-monitor.sh ./cluster/gce/gci/master-helper.sh ./cluster/gce/gci/mounter/stage-upload.sh ./cluster/gce/gci/node-helper.sh ./cluster/gce/gci/shutdown.sh ./cluster/gce/list-resources.sh ./cluster/gce/upgrade-aliases.sh ./cluster/gce/upgrade.sh ./cluster/gce/util.sh ./cluster/get-kube-binaries.sh ./cluster/get-kube-local.sh ./cluster/get-kube.sh ./cluster/images/conformance/run_e2e.sh ./cluster/images/etcd-empty-dir-cleanup/etcd-empty-dir-cleanup.sh ./cluster/juju/prereqs/ubuntu-juju.sh ./cluster/juju/util.sh ./cluster/kube-down.sh ./cluster/kube-up.sh ./cluster/kube-util.sh ./cluster/kubeadm.sh ./cluster/kubectl.sh ./cluster/kubemark/gce/config-default.sh ./cluster/kubemark/iks/config-default.sh ./cluster/kubemark/util.sh ./cluster/local/util.sh ./cluster/log-dump/log-dump.sh ./cluster/pre-existing/util.sh ./cluster/restore-from-backup.sh ./cluster/test-e2e.sh ./cluster/test-network.sh ./cluster/test-smoke.sh ./cluster/update-storage-objects.sh ./cluster/validate-cluster.sh ./hack/benchmark-go.sh ./hack/build-cross.sh ./hack/build-go.sh ./hack/build-ui.sh ./hack/cherry_pick_pull.sh ./hack/dev-build-and-push.sh ./hack/dev-build-and-up.sh ./hack/dev-push-conformance.sh ./hack/dev-push-hyperkube.sh ./hack/e2e-internal/e2e-cluster-size.sh ./hack/e2e-internal/e2e-down.sh ./hack/e2e-internal/e2e-grow-cluster.sh ./hack/e2e-internal/e2e-shrink-cluster.sh ./hack/e2e-internal/e2e-status.sh ./hack/e2e-internal/e2e-up.sh ./hack/e2e-node-test.sh ./hack/generate-bindata.sh ./hack/generate-docs.sh ./hack/get-build.sh ./hack/ginkgo-e2e.sh ./hack/godep-restore.sh ./hack/godep-save.sh ./hack/grab-profiles.sh ./hack/install-etcd.sh ./hack/jenkins/benchmark-dockerized.sh ./hack/jenkins/build.sh ./hack/jenkins/test-dockerized.sh ./hack/jenkins/upload-to-gcs.sh ./hack/jenkins/verify-dockerized.sh ./hack/lib/etcd.sh ./hack/lib/golang.sh ./hack/lib/init.sh ./hack/lib/logging.sh ./hack/lib/protoc.sh ./hack/lib/swagger.sh ./hack/lib/test.sh ./hack/lib/util.sh ./hack/lib/version.sh ./hack/list-feature-tests.sh ./hack/local-up-cluster.sh ./hack/make-rules/build.sh ./hack/make-rules/clean.sh ./hack/make-rules/cross.sh ./hack/make-rules/helpers/cache_go_dirs.sh ./hack/make-rules/make-help.sh ./hack/make-rules/test-cmd.sh ./hack/make-rules/test-e2e-node.sh ./hack/make-rules/test-integration.sh ./hack/make-rules/test-kubeadm-cmd.sh ./hack/make-rules/test.sh ./hack/make-rules/update.sh ./hack/make-rules/verify.sh ./hack/make-rules/vet.sh ./hack/print-workspace-status.sh ./hack/run-in-gopath.sh ./hack/test-go.sh ./hack/test-integration.sh ./hack/test-update-storage-objects.sh ./hack/update-all.sh ./hack/update-api-reference-docs.sh ./hack/update-bazel.sh ./hack/update-codegen.sh ./hack/update-generated-device-plugin-dockerized.sh ./hack/update-generated-device-plugin.sh ./hack/update-generated-docs.sh ./hack/update-generated-kms-dockerized.sh ./hack/update-generated-kms.sh ./hack/update-generated-kubelet-plugin-registration-dockerized.sh ./hack/update-generated-kubelet-plugin-registration.sh ./hack/update-generated-pod-resources-dockerized.sh ./hack/update-generated-pod-resources.sh ./hack/update-generated-protobuf-dockerized.sh ./hack/update-generated-protobuf.sh ./hack/update-generated-runtime-dockerized.sh ./hack/update-generated-runtime.sh ./hack/update-generated-swagger-docs.sh ./hack/update-godep-licenses.sh ./hack/update-gofmt.sh ./hack/update-openapi-spec.sh ./hack/update-staging-godeps-dockerized.sh ./hack/update-staging-godeps.sh ./hack/update-swagger-spec.sh ./hack/update-translations.sh ./hack/update-workspace-mirror.sh ./hack/verify-all.sh ./hack/verify-api-groups.sh ./hack/verify-api-reference-docs.sh ./hack/verify-bazel.sh ./hack/verify-boilerplate.sh ./hack/verify-cli-conventions.sh ./hack/verify-codegen.sh ./hack/verify-description.sh ./hack/verify-generated-device-plugin.sh ./hack/verify-generated-docs.sh ./hack/verify-generated-files-remake.sh ./hack/verify-generated-files.sh ./hack/verify-generated-kms.sh ./hack/verify-generated-kubelet-plugin-registration.sh ./hack/verify-generated-pod-resources.sh ./hack/verify-generated-protobuf.sh ./hack/verify-generated-runtime.sh ./hack/verify-generated-swagger-docs.sh ./hack/verify-godep-licenses.sh ./hack/verify-godeps.sh ./hack/verify-gofmt.sh ./hack/verify-golint.sh ./hack/verify-govet.sh ./hack/verify-import-boss.sh ./hack/verify-imports.sh ./hack/verify-linkcheck.sh ./hack/verify-no-vendor-cycles.sh ./hack/verify-openapi-spec.sh ./hack/verify-pkg-names.sh ./hack/verify-readonly-packages.sh ./hack/verify-spelling.sh ./hack/verify-staging-godeps.sh ./hack/verify-staging-meta-files.sh ./hack/verify-swagger-spec.sh ./hack/verify-symbols.sh ./hack/verify-test-featuregates.sh ./hack/verify-test-images.sh ./hack/verify-test-owners.sh ./hack/verify-typecheck.sh ./pkg/kubectl/cmd/edit/testdata/record_testcase.sh ./pkg/util/verify-util-pkg.sh ./plugin/pkg/admission/imagepolicy/gencerts.sh ./staging/src/k8s.io/apiextensions-apiserver/examples/client-go/hack/update-codegen.sh ./staging/src/k8s.io/apiextensions-apiserver/examples/client-go/hack/verify-codegen.sh ./staging/src/k8s.io/apiextensions-apiserver/hack/build-image.sh ./staging/src/k8s.io/apiextensions-apiserver/hack/update-codegen.sh ./staging/src/k8s.io/apiextensions-apiserver/hack/verify-codegen.sh ./staging/src/k8s.io/apiserver/pkg/admission/plugin/webhook/testcerts/gencerts.sh ./staging/src/k8s.io/apiserver/pkg/util/webhook/gencerts.sh ./staging/src/k8s.io/apiserver/plugin/pkg/authenticator/token/oidc/testdata/gen.sh ./staging/src/k8s.io/apiserver/plugin/pkg/authorizer/webhook/gencerts.sh ./staging/src/k8s.io/code-generator/generate-groups.sh ./staging/src/k8s.io/code-generator/generate-internal-groups.sh ./staging/src/k8s.io/code-generator/hack/update-codegen.sh ./staging/src/k8s.io/code-generator/hack/verify-codegen.sh ./staging/src/k8s.io/csi-api/hack/update-codegen.sh ./staging/src/k8s.io/csi-api/hack/verify-codegen.sh ./staging/src/k8s.io/kube-aggregator/hack/build-image.sh ./staging/src/k8s.io/kube-aggregator/hack/local-up-kube-aggregator.sh ./staging/src/k8s.io/kube-aggregator/hack/register-all-apis-from.sh ./staging/src/k8s.io/kube-aggregator/hack/update-codegen.sh ./staging/src/k8s.io/kube-aggregator/hack/verify-codegen.sh ./staging/src/k8s.io/metrics/hack/update-codegen.sh ./staging/src/k8s.io/metrics/hack/verify-codegen.sh ./staging/src/k8s.io/node-api/hack/update-codegen.sh ./staging/src/k8s.io/node-api/hack/verify-codegen.sh ./staging/src/k8s.io/sample-apiserver/hack/build-image.sh ./staging/src/k8s.io/sample-apiserver/hack/update-codegen.sh ./staging/src/k8s.io/sample-apiserver/hack/verify-codegen.sh ./staging/src/k8s.io/sample-controller/hack/update-codegen.sh ./staging/src/k8s.io/sample-controller/hack/verify-codegen.sh ./test/cmd/apply.sh ./test/cmd/apps.sh ./test/cmd/authorization.sh ./test/cmd/batch.sh ./test/cmd/certificate.sh ./test/cmd/core.sh ./test/cmd/crd.sh ./test/cmd/create.sh ./test/cmd/diff.sh ./test/cmd/discovery.sh ./test/cmd/generic-resources.sh ./test/cmd/get.sh ./test/cmd/initializers.sh ./test/cmd/legacy-script.sh ./test/cmd/node-management.sh ./test/cmd/old-print.sh ./test/cmd/proxy.sh ./test/cmd/rbac.sh ./test/cmd/request-timeout.sh ./test/cmd/run.sh ./test/cmd/save-config.sh ./test/cmd/storage.sh ./test/cmd/template-output.sh ./test/cmd/version.sh ./test/e2e_node/conformance/run_test.sh ./test/e2e_node/environment/setup_host.sh ./test/e2e_node/gubernator.sh ./test/e2e_node/jenkins/conformance/conformance-jenkins.sh ./test/e2e_node/jenkins/copy-e2e-image.sh ./test/e2e_node/jenkins/e2e-node-jenkins.sh ./test/e2e_node/jenkins/ubuntu-14.04-nvidia-install.sh ./test/images/image-util.sh ./test/images/pets/redis-installer/on-start.sh ./test/images/pets/zookeeper-installer/install.sh ./test/images/pets/zookeeper-installer/on-start.sh ./test/images/volume/gluster/run_gluster.sh ./test/images/volume/iscsi/create_block.sh ./test/images/volume/nfs/run_nfs.sh ./test/images/volume/rbd/bootstrap.sh ./test/images/volume/rbd/create_block.sh ./test/images/volume/rbd/mon.sh ./test/images/volume/rbd/osd.sh ./test/integration/ipamperf/test-performance.sh ./test/integration/scheduler_perf/test-performance.sh ./test/kubemark/common/util.sh ./test/kubemark/configure-kubectl.sh ./test/kubemark/gce/util.sh ./test/kubemark/iks/shutdown.sh ./test/kubemark/iks/startup.sh ./test/kubemark/iks/util.sh ./test/kubemark/master-log-dump.sh ./test/kubemark/pre-existing/util.sh ./test/kubemark/resources/start-kubemark-master.sh ./test/kubemark/run-e2e-tests.sh ./test/kubemark/start-kubemark.sh ./test/kubemark/stop-kubemark.sh ./third_party/forked/shell2junit/sh2ju.sh ./third_party/intemp/intemp.sh ./third_party/multiarch/qemu-user-static/register/qemu-binfmt-conf.sh ./third_party/multiarch/qemu-user-static/register/register.sh </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-33260ec64a7d900f1342ac27e4dcabb354b23351ec3e8ae604c63a04e69f42d4", "text": "is a bash script linter which could help catch common problems in our (numerous) bash scripts. I know we'd like to reduce our use of bash scripts, but until then I think being stricter about script quality would be helpful. /cc\ncc you were talking about this earlier. It has to only check modified lines.\nFalse positives are a problem. For instance, not being able to follow a call through an environment variable causes an error. I would be much more comfortable with a non-blocking way to point out these issues, and leave to it human judgement.\nYeah, I've been interested in doing this for a while, but can be pretty persnickety and I haven't yet taken the time to configure it to be less noisy (or figure out if it can be). It's good, though.\nYeah, it would definitely need to be configured to ignore a lot of types of errors, but I still think it could be used to check for some types of errors. We could start with a pretty minimal set.\nI would settle for something that just produced a quick-fix format artifact in the GCS bucket, and then the PR munger reading from it and commenting on the PR. We could re-use that for other linters too.\nhas been pretty accurate historically.\nshellcheck, not spellcheck\nreading too many issues in a on\n/sig testing /priority awaiting-more-evidence Might be more noise than it's worth, but we do pylint our .py scripts now\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with .", "commid": "kubernetes_issue_24614", "tokennum": 500}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0ee0fa0252d544b835406a3956fb0b808f275127294f689d9f80d60f7b1133b9", "query": "<ins> ./build/build-image/rsyncd.sh ./build/common.sh ./build/copy-output.sh ./build/lib/release.sh ./build/make-build-image.sh ./build/make-clean.sh ./build/package-tarballs.sh ./build/release-images.sh ./build/release-in-a-container.sh ./build/release.sh ./build/run.sh ./build/shell.sh ./build/util.sh ./cluster/addons/addon-manager/kube-addons.sh ./cluster/addons/fluentd-elasticsearch/es-image/run.sh ./cluster/addons/fluentd-elasticsearch/fluentd-es-image/run.sh ./cluster/centos/build.sh ./cluster/centos/config-build.sh ./cluster/centos/config-default.sh ./cluster/centos/config-test.sh ./cluster/centos/deployAddons.sh ./cluster/centos/make-ca-cert.sh ./cluster/centos/master/scripts/flannel.sh ./cluster/centos/node/bin/mk-docker-opts.sh ./cluster/centos/node/scripts/flannel.sh ./cluster/centos/util.sh ./cluster/clientbin.sh ./cluster/common.sh ./cluster/gce/config-common.sh ./cluster/gce/config-default.sh ./cluster/gce/config-test.sh ./cluster/gce/delete-stranded-load-balancers.sh ./cluster/gce/gci/configure-helper.sh ./cluster/gce/gci/configure.sh ./cluster/gce/gci/flexvolume_node_setup.sh ./cluster/gce/gci/health-monitor.sh ./cluster/gce/gci/master-helper.sh ./cluster/gce/gci/mounter/stage-upload.sh ./cluster/gce/gci/node-helper.sh ./cluster/gce/gci/shutdown.sh ./cluster/gce/list-resources.sh ./cluster/gce/upgrade-aliases.sh ./cluster/gce/upgrade.sh ./cluster/gce/util.sh ./cluster/get-kube-binaries.sh ./cluster/get-kube-local.sh ./cluster/get-kube.sh ./cluster/images/conformance/run_e2e.sh ./cluster/images/etcd-empty-dir-cleanup/etcd-empty-dir-cleanup.sh ./cluster/juju/prereqs/ubuntu-juju.sh ./cluster/juju/util.sh ./cluster/kube-down.sh ./cluster/kube-up.sh ./cluster/kube-util.sh ./cluster/kubeadm.sh ./cluster/kubectl.sh ./cluster/kubemark/gce/config-default.sh ./cluster/kubemark/iks/config-default.sh ./cluster/kubemark/util.sh ./cluster/local/util.sh ./cluster/log-dump/log-dump.sh ./cluster/pre-existing/util.sh ./cluster/restore-from-backup.sh ./cluster/test-e2e.sh ./cluster/test-network.sh ./cluster/test-smoke.sh ./cluster/update-storage-objects.sh ./cluster/validate-cluster.sh ./hack/benchmark-go.sh ./hack/build-cross.sh ./hack/build-go.sh ./hack/build-ui.sh ./hack/cherry_pick_pull.sh ./hack/dev-build-and-push.sh ./hack/dev-build-and-up.sh ./hack/dev-push-conformance.sh ./hack/dev-push-hyperkube.sh ./hack/e2e-internal/e2e-cluster-size.sh ./hack/e2e-internal/e2e-down.sh ./hack/e2e-internal/e2e-grow-cluster.sh ./hack/e2e-internal/e2e-shrink-cluster.sh ./hack/e2e-internal/e2e-status.sh ./hack/e2e-internal/e2e-up.sh ./hack/e2e-node-test.sh ./hack/generate-bindata.sh ./hack/generate-docs.sh ./hack/get-build.sh ./hack/ginkgo-e2e.sh ./hack/godep-restore.sh ./hack/godep-save.sh ./hack/grab-profiles.sh ./hack/install-etcd.sh ./hack/jenkins/benchmark-dockerized.sh ./hack/jenkins/build.sh ./hack/jenkins/test-dockerized.sh ./hack/jenkins/upload-to-gcs.sh ./hack/jenkins/verify-dockerized.sh ./hack/lib/etcd.sh ./hack/lib/golang.sh ./hack/lib/init.sh ./hack/lib/logging.sh ./hack/lib/protoc.sh ./hack/lib/swagger.sh ./hack/lib/test.sh ./hack/lib/util.sh ./hack/lib/version.sh ./hack/list-feature-tests.sh ./hack/local-up-cluster.sh ./hack/make-rules/build.sh ./hack/make-rules/clean.sh ./hack/make-rules/cross.sh ./hack/make-rules/helpers/cache_go_dirs.sh ./hack/make-rules/make-help.sh ./hack/make-rules/test-cmd.sh ./hack/make-rules/test-e2e-node.sh ./hack/make-rules/test-integration.sh ./hack/make-rules/test-kubeadm-cmd.sh ./hack/make-rules/test.sh ./hack/make-rules/update.sh ./hack/make-rules/verify.sh ./hack/make-rules/vet.sh ./hack/print-workspace-status.sh ./hack/run-in-gopath.sh ./hack/test-go.sh ./hack/test-integration.sh ./hack/test-update-storage-objects.sh ./hack/update-all.sh ./hack/update-api-reference-docs.sh ./hack/update-bazel.sh ./hack/update-codegen.sh ./hack/update-generated-device-plugin-dockerized.sh ./hack/update-generated-device-plugin.sh ./hack/update-generated-docs.sh ./hack/update-generated-kms-dockerized.sh ./hack/update-generated-kms.sh ./hack/update-generated-kubelet-plugin-registration-dockerized.sh ./hack/update-generated-kubelet-plugin-registration.sh ./hack/update-generated-pod-resources-dockerized.sh ./hack/update-generated-pod-resources.sh ./hack/update-generated-protobuf-dockerized.sh ./hack/update-generated-protobuf.sh ./hack/update-generated-runtime-dockerized.sh ./hack/update-generated-runtime.sh ./hack/update-generated-swagger-docs.sh ./hack/update-godep-licenses.sh ./hack/update-gofmt.sh ./hack/update-openapi-spec.sh ./hack/update-staging-godeps-dockerized.sh ./hack/update-staging-godeps.sh ./hack/update-swagger-spec.sh ./hack/update-translations.sh ./hack/update-workspace-mirror.sh ./hack/verify-all.sh ./hack/verify-api-groups.sh ./hack/verify-api-reference-docs.sh ./hack/verify-bazel.sh ./hack/verify-boilerplate.sh ./hack/verify-cli-conventions.sh ./hack/verify-codegen.sh ./hack/verify-description.sh ./hack/verify-generated-device-plugin.sh ./hack/verify-generated-docs.sh ./hack/verify-generated-files-remake.sh ./hack/verify-generated-files.sh ./hack/verify-generated-kms.sh ./hack/verify-generated-kubelet-plugin-registration.sh ./hack/verify-generated-pod-resources.sh ./hack/verify-generated-protobuf.sh ./hack/verify-generated-runtime.sh ./hack/verify-generated-swagger-docs.sh ./hack/verify-godep-licenses.sh ./hack/verify-godeps.sh ./hack/verify-gofmt.sh ./hack/verify-golint.sh ./hack/verify-govet.sh ./hack/verify-import-boss.sh ./hack/verify-imports.sh ./hack/verify-linkcheck.sh ./hack/verify-no-vendor-cycles.sh ./hack/verify-openapi-spec.sh ./hack/verify-pkg-names.sh ./hack/verify-readonly-packages.sh ./hack/verify-spelling.sh ./hack/verify-staging-godeps.sh ./hack/verify-staging-meta-files.sh ./hack/verify-swagger-spec.sh ./hack/verify-symbols.sh ./hack/verify-test-featuregates.sh ./hack/verify-test-images.sh ./hack/verify-test-owners.sh ./hack/verify-typecheck.sh ./pkg/kubectl/cmd/edit/testdata/record_testcase.sh ./pkg/util/verify-util-pkg.sh ./plugin/pkg/admission/imagepolicy/gencerts.sh ./staging/src/k8s.io/apiextensions-apiserver/examples/client-go/hack/update-codegen.sh ./staging/src/k8s.io/apiextensions-apiserver/examples/client-go/hack/verify-codegen.sh ./staging/src/k8s.io/apiextensions-apiserver/hack/build-image.sh ./staging/src/k8s.io/apiextensions-apiserver/hack/update-codegen.sh ./staging/src/k8s.io/apiextensions-apiserver/hack/verify-codegen.sh ./staging/src/k8s.io/apiserver/pkg/admission/plugin/webhook/testcerts/gencerts.sh ./staging/src/k8s.io/apiserver/pkg/util/webhook/gencerts.sh ./staging/src/k8s.io/apiserver/plugin/pkg/authenticator/token/oidc/testdata/gen.sh ./staging/src/k8s.io/apiserver/plugin/pkg/authorizer/webhook/gencerts.sh ./staging/src/k8s.io/code-generator/generate-groups.sh ./staging/src/k8s.io/code-generator/generate-internal-groups.sh ./staging/src/k8s.io/code-generator/hack/update-codegen.sh ./staging/src/k8s.io/code-generator/hack/verify-codegen.sh ./staging/src/k8s.io/csi-api/hack/update-codegen.sh ./staging/src/k8s.io/csi-api/hack/verify-codegen.sh ./staging/src/k8s.io/kube-aggregator/hack/build-image.sh ./staging/src/k8s.io/kube-aggregator/hack/local-up-kube-aggregator.sh ./staging/src/k8s.io/kube-aggregator/hack/register-all-apis-from.sh ./staging/src/k8s.io/kube-aggregator/hack/update-codegen.sh ./staging/src/k8s.io/kube-aggregator/hack/verify-codegen.sh ./staging/src/k8s.io/metrics/hack/update-codegen.sh ./staging/src/k8s.io/metrics/hack/verify-codegen.sh ./staging/src/k8s.io/node-api/hack/update-codegen.sh ./staging/src/k8s.io/node-api/hack/verify-codegen.sh ./staging/src/k8s.io/sample-apiserver/hack/build-image.sh ./staging/src/k8s.io/sample-apiserver/hack/update-codegen.sh ./staging/src/k8s.io/sample-apiserver/hack/verify-codegen.sh ./staging/src/k8s.io/sample-controller/hack/update-codegen.sh ./staging/src/k8s.io/sample-controller/hack/verify-codegen.sh ./test/cmd/apply.sh ./test/cmd/apps.sh ./test/cmd/authorization.sh ./test/cmd/batch.sh ./test/cmd/certificate.sh ./test/cmd/core.sh ./test/cmd/crd.sh ./test/cmd/create.sh ./test/cmd/diff.sh ./test/cmd/discovery.sh ./test/cmd/generic-resources.sh ./test/cmd/get.sh ./test/cmd/initializers.sh ./test/cmd/legacy-script.sh ./test/cmd/node-management.sh ./test/cmd/old-print.sh ./test/cmd/proxy.sh ./test/cmd/rbac.sh ./test/cmd/request-timeout.sh ./test/cmd/run.sh ./test/cmd/save-config.sh ./test/cmd/storage.sh ./test/cmd/template-output.sh ./test/cmd/version.sh ./test/e2e_node/conformance/run_test.sh ./test/e2e_node/environment/setup_host.sh ./test/e2e_node/gubernator.sh ./test/e2e_node/jenkins/conformance/conformance-jenkins.sh ./test/e2e_node/jenkins/copy-e2e-image.sh ./test/e2e_node/jenkins/e2e-node-jenkins.sh ./test/e2e_node/jenkins/ubuntu-14.04-nvidia-install.sh ./test/images/image-util.sh ./test/images/pets/redis-installer/on-start.sh ./test/images/pets/zookeeper-installer/install.sh ./test/images/pets/zookeeper-installer/on-start.sh ./test/images/volume/gluster/run_gluster.sh ./test/images/volume/iscsi/create_block.sh ./test/images/volume/nfs/run_nfs.sh ./test/images/volume/rbd/bootstrap.sh ./test/images/volume/rbd/create_block.sh ./test/images/volume/rbd/mon.sh ./test/images/volume/rbd/osd.sh ./test/integration/ipamperf/test-performance.sh ./test/integration/scheduler_perf/test-performance.sh ./test/kubemark/common/util.sh ./test/kubemark/configure-kubectl.sh ./test/kubemark/gce/util.sh ./test/kubemark/iks/shutdown.sh ./test/kubemark/iks/startup.sh ./test/kubemark/iks/util.sh ./test/kubemark/master-log-dump.sh ./test/kubemark/pre-existing/util.sh ./test/kubemark/resources/start-kubemark-master.sh ./test/kubemark/run-e2e-tests.sh ./test/kubemark/start-kubemark.sh ./test/kubemark/stop-kubemark.sh ./third_party/forked/shell2junit/sh2ju.sh ./third_party/intemp/intemp.sh ./third_party/multiarch/qemu-user-static/register/qemu-binfmt-conf.sh ./third_party/multiarch/qemu-user-static/register/register.sh </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-7c2396e8c525e9f1f7bfa4cd4f910bc5e5cdd53da779129188a0590e81ff81c5", "text": "Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nI'd like to reopen this, and eventually implement (first we need to deal with the failures ...) I've easily found a lot of bugs in test-infra and kubernetes/kubernetes bash with shellcheck. See also /assign\n/reopen /remove-lifecycle rotten /priority important-longterm\nReopening this issue. <detailsIn response to : /reopen /remove-lifecycle rotten /priority important-longterm 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\nWe also have non-blocking and optionally-run presubmits, even just having an easy way for reviewers to request a shellcheck result for changed files seems like something we should do. I also think we should fix the existing failures. Glancing through some k/k bash with shellcheck in my editor, these generally seem to be things that are actually wrong.\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten coming back to this hopefully\nThis is done now. Only took two years :^)", "commid": "kubernetes_issue_24614", "tokennum": 400}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0ee1b9f701fba62bd62aad7b806f4f58c6a19c524d3f76384ca90ef4ff0adeb9", "query": "} func (c *defaultAuthenticationInfoResolver) ClientConfigFor(server string) (*rest.Config, error) { <ins> return c.clientConfig(server) } func (c *defaultAuthenticationInfoResolver) ClientConfigForService(serviceName, serviceNamespace string) (*rest.Config, error) { return c.clientConfig(serviceName + \".\" + serviceNamespace + \".svc\") } func (c *defaultAuthenticationInfoResolver) clientConfig(target string) (*rest.Config, error) { </ins> // exact match <del> if authConfig, ok := c.kubeconfig.AuthInfos[server]; ok { </del> <ins> if authConfig, ok := c.kubeconfig.AuthInfos[target]; ok { </ins> return restConfigFromKubeconfig(authConfig) } // star prefixed match <del> serverSteps := strings.Split(server, \".\") </del> <ins> serverSteps := strings.Split(target, \".\") </ins> for i := 1; i < len(serverSteps); i++ { nickName := \"*.\" + strings.Join(serverSteps[i:], \".\") if authConfig, ok := c.kubeconfig.AuthInfos[nickName]; ok {", "positive_passages": [{"docid": "doc-en-kubernetes-73496a383d34eb1ab5962a20be4dce66952c6d20058c4ff89ce94afc1cb5683d", "text": "We are getting the following error when the apiserver connects the webhook on localhost (configured via URL). We should only use the SSL tunnel for the connections to nodes when the webhooks are running as services. /sig api-machinery /kind bug /assign\n/close", "commid": "kubernetes_issue_58779", "tokennum": 64}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0f1e3403e35e8fa545cda0b153f1dd2c25c9d1ce66305d9e58aafea6c90d4b5f", "query": "utilpointer \"k8s.io/utils/pointer\" \"github.com/onsi/ginkgo/v2\" <ins> \"github.com/onsi/gomega\" </ins> imageutils \"k8s.io/kubernetes/test/utils/image\" )", "positive_passages": [{"docid": "doc-en-kubernetes-c9c1c743d3f3434b5b176b4daffd6034698e7589ba7079b19c7793ebc64267f8", "text": "Kubernetes e2e suite. Kubernetes e2e suite.[It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicationController Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods and verify decision stability [sig-autoscaling, Feature:HPA, Serial, Slow] Kubernetes e2e suite.[It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicationController Should scale from 5 pods to 3 pods and then from 3 pods to 1 pod and verify decision stability [sig-autoscaling, Feature:HPA, Serial, Slow] Kubernetes e2e suite.[It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with autoscaling disabled shouldn't scale down [sig-autoscaling, Feature:HPA, Serial, Slow] Kubernetes e2e suite.[It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with autoscaling disabled shouldn't scale up [sig-autoscaling, Feature:HPA, Serial, Slow] Kubernetes e2e suite.[It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with both scale up and down controls configured should keep recommendation within the range with stabilization window and pod limit rate [sig-autoscaling, Feature:HPA, Serial, Slow] Kubernetes e2e suite.", "commid": "kubernetes_issue_121860", "tokennum": 407}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0f1e3403e35e8fa545cda0b153f1dd2c25c9d1ce66305d9e58aafea6c90d4b5f", "query": "utilpointer \"k8s.io/utils/pointer\" \"github.com/onsi/ginkgo/v2\" <ins> \"github.com/onsi/gomega\" </ins> imageutils \"k8s.io/kubernetes/test/utils/image\" )", "positive_passages": [{"docid": "doc-en-kubernetes-50a764361af76177e3b0fd7754c28175d0d0117b957f7afce14b1a8f0955f9e1", "text": "[It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with both scale up and down controls configured should keep recommendation within the range over two stabilization windows [sig-autoscaling, Feature:HPA, Serial, Slow] 11/3/2023 <*fmt.wrapError | 0xc000812080: client rate limiter Wait returned an error: context deadline exceeded { msg: \"client rate limiter Wait returned an error: context deadline exceeded\", err: <context.deadlineExceededError{}, } looks similiar to /sig autoscaling /sig windows\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_121860", "tokennum": 242}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0f3dc5e6f38ff6334211019f6e75716bab58a113bc4f2fa35c566ea0c270297f", "query": "} waitSTSStable(t, c, sts) } <ins> var _ admission.ValidationInterface = &fakePodFailAdmission{} type fakePodFailAdmission struct { limitedPodNumber int succeedPodsCount int } func (f *fakePodFailAdmission) Handles(operation admission.Operation) bool { return operation == admission.Create } func (f *fakePodFailAdmission) Validate(ctx context.Context, attr admission.Attributes, o admission.ObjectInterfaces) (err error) { if attr.GetKind().GroupKind() != api.Kind(\"Pod\") { return nil } if f.succeedPodsCount >= f.limitedPodNumber { return fmt.Errorf(\"fakePodFailAdmission error\") } f.succeedPodsCount++ return nil } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-0cad02d163e61aff3cc2c1257b68701a42fb1145e0b51f6816fd9a85adca78e6", "text": "I create a ResourceQuota with two pods limit in my namespace. Then, I create a statefuleSet with 3 replicas. As expected, two pods are created successfully, and the third pod failed to create. But, the ReadyReplicas is not 2 ,but 1. The ReadyReplicas is correct 1Create a ResourceQuota with two pods limit in a new namespace. 2Create a statefulSet with 3 replicas 3Check if the ReadyReplicas of statefulSet matchs the number of stateful running pods. 1According to the logic of the statefulSet controller, new pod created in current sync is not be immediately counted into the ReadyReplicas. 2Failure to create pod will cause to return error, then skip updating status. <details</details<details</details<detailskind v1.23.3 </details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig apps\n/assign", "commid": "kubernetes_issue_108837", "tokennum": 302}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0f8ac6c6ad189a4e71a5effc72a78d6681f7463d280e2e45d5b58e1aee6aee39", "query": "return stringOrDefaultValue(strings.Join(volumes, \",\"), \"<all>\") } <ins> func sysctlsToString(sysctls []string) string { return stringOrNone(strings.Join(sysctls, \",\")) } </ins> func hostPortRangeToString(ranges []policy.HostPortRange) string { formattedString := \"\" if ranges != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-1c37f3b13ef66319b53623e24b4fece0550cb85e7e62ca9b694924c6c433e0c8", "text": "/kind bug What happened: does not show the description for the new field in What you expected to happen: should describe the new field. How to reproduce it (as minimally and precisely as possible): Environment: Kubernetes version (use ): master\n/sig auth\nGitHub didn't allow me to assign the following users: fanzhangio. Note that only and repo collaborators can be assigned. <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\nIf nobody has started yet, I wanna to pick it up.\nwas working on it AFAIR.\nIndeed. if you don't mind, I'd take over.", "commid": "kubernetes_issue_65181", "tokennum": 165}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0fb987d86186121faa0e23db0fe744567a9963c5cf0beb0f724137e8c09ac012", "query": "if err != nil { return nil, err } <ins> volumePath = strings.Replace(volumePath, \"040\", \" \", -1) </ins> glog.V(5).Infof(\"vSphere volume path is %q\", volumePath) vsphereVolume := &v1.Volume{ Name: volumeName,", "positive_passages": [{"docid": "doc-en-kubernetes-65b87d6ab9dc4eafe4d20be92d7fc50e93b7f8fc56cfe96572cf225758153ef7", "text": "Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG <!-- If this is a BUG REPORT, please: Fill in as much of the template below as you can. If you leave out information, we can't help you as well. If this is a FEATURE REQUEST, please: Describe in detail the feature/behavior/change you'd like to see. In both cases, be ready for followup questions, and please respond in a timely manner. If we can't reproduce a bug or think a feature already exists, we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why. --Kubernetes version (use ): Client Version: version.Info{Major:\"1\", Minor:\"4\", GitVersion:\"v1.4.5\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2016-10-29T01:38:40Z\", GoVersion:\"go1.6.3\", Compiler:\"gc\", Platform:\"linux/amd64\"} Server Version: version.Info{Major:\"1\", Minor:\"4\", GitVersion:\"v1.4.5\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2016-10-29T01:32:42Z\", GoVersion:\"go1.6.3\", Compiler:\"gc\", Platform:\"linux/amd64\"} Environment: Cloud provider or hardware configuration: vSphere OS (e.g. from /etc/os-release):Kernel (e.g. ):Install tools: None Others: None What happened: When I create a deployment with vSphere cloud provider dynamic provisioning, it creates a volume spec with volume path - [datastore] kubevols/volume which contains a white space in it. In this case the cloud provider queries the getDeviceNameFromMount() to return the path of the volume mounted. Since getDeviceNameFromMount() queries the filesystem to get the mount references, it returns a volume path \"[datastore]040kubevols/volume\". Later the kubelet searches for this volume path in both the actual and desired states. Th actual and desired states contains volume with path \"[datastore] kubevols/volume\". So, it couldn't find such volume path and therefore kubernetes stalls unable to make any progress further similar to one described in .", "commid": "kubernetes_issue_38148", "tokennum": 574}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0fb987d86186121faa0e23db0fe744567a9963c5cf0beb0f724137e8c09ac012", "query": "if err != nil { return nil, err } <ins> volumePath = strings.Replace(volumePath, \"040\", \" \", -1) </ins> glog.V(5).Infof(\"vSphere volume path is %q\", volumePath) vsphereVolume := &v1.Volume{ Name: volumeName,", "positive_passages": [{"docid": "doc-en-kubernetes-4472e5c92e91fa48fbd9ae4b2faf4fe2f973ca70781a7072044a8b4998a8c4c5", "text": "Also similar issue described in What you expected to happen: All the pods in the recreated deployment comes up. How to reproduce it (as minimally and precisely as possible): See above. Anything else do we need to know: None\ncc", "commid": "kubernetes_issue_38148", "tokennum": 48}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0fb987d86186121faa0e23db0fe744567a9963c5cf0beb0f724137e8c09ac012", "query": "if err != nil { return nil, err } <ins> volumePath = strings.Replace(volumePath, \"040\", \" \", -1) </ins> glog.V(5).Infof(\"vSphere volume path is %q\", volumePath) vsphereVolume := &v1.Volume{ Name: volumeName,", "positive_passages": [{"docid": "doc-en-kubernetes-856660a825f3ffe3a03d6e2754ae87c832572ac27681226648a4feba9d3ff6d0", "text": "I tried to create a kubernetes deployment with vSphere volume with volume path \"[datastore] kubevols/redis-master\". In this case the cloud provider queries the getDeviceNameFromMount() to return the path of the volume mounted. Since getDeviceNameFromMount() queries the filesystem to get the mount references, it returns a volume path \"[datastore]040kubevols/redis-master\". Later the kubelet searches for this volume path in both the actual and desired states. Th actual and desired states contains volume with path \"[datastore] kubevols/redis-master\". So, it couldn't find such volume path and therefore kubernetes stalls unable to make any progress further similar to one described in . However, when I create a kubernetes deployment with volume path - \"[datastore]kubevols/redis-master\" which doesn't contain any spaces, it works perfectly fine. So, the basic problem is to format and return the correct volume path from getDeviceNameFromMount() function. Alternatively, we can format it properly in the cloud provider code but this has to be done individually in all the cloud provider code base. Inorder to prevent it, it would be better to fix the getDeviceNameFromMount() function to return the correct formatted volume path.\nCC Kubernetes should handle volumes with spaces (looks like vsphere is the first such volume) gracefully. Non a blocker issue for 1.5.\nyou should make sure that the 1.5 release notes capture that \"vsphere volumes w/spaces have problems\". Known issue accumulator in\ngetDeviceNameFromMount is function which queries /proc/mount to get mount points. 040 - is an escape sequence. 040 is the ascii code, in octal(base 8) number system, of the space. The mount command interprets 040 as literal space in the mount point. : Can't we provide a fix for this in 1.5 release itself? There a 2 options: can provide a fix in getDeviceNameFromMount. can provide a fix to vSphere cloud provider to fix it after the call to getDeviceNameFromMount. For option 1, we have to make sure it works for all cloud providers where as for option 2 its not needed. Let me know which option you think is feasible. I am ok with anything.", "commid": "kubernetes_issue_37712", "tokennum": 548}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0fb987d86186121faa0e23db0fe744567a9963c5cf0beb0f724137e8c09ac012", "query": "if err != nil { return nil, err } <ins> volumePath = strings.Replace(volumePath, \"040\", \" \", -1) </ins> glog.V(5).Infof(\"vSphere volume path is %q\", volumePath) vsphereVolume := &v1.Volume{ Name: volumeName,", "positive_passages": [{"docid": "doc-en-kubernetes-f0c75eb090ebda051cbb8d4dcd548ddf167d040dce30f4ff6f2c05a5971aa5a4", "text": "1 is the right answer. But we're very close to 1.5.0 release (<1 week). I'd also like whoever addresses this to ensure the entire system works end-to-end for volumes with spaces, not just patch one little corner. I'm afraid it would be a large change and we're not going to have enough time to validate it in 1.5. You can certainly start working on it. If you get a PR in time, we can consider it for 1.5.0. Otherwise it'll have to go in a patch release.", "commid": "kubernetes_issue_37712", "tokennum": 124}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0fc85c246ff6a6e9eb42b87b795776235afea8df637aa2ce6479a7ac408a3090", "query": "import ( \"context\" <ins> \"encoding/json\" </ins> \"fmt\" \"strconv\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-9deab690131da58e4566d26be974a26500a50c4525ef4b542cd9399a25bc940c", "text": "[x] Test PR : [x] Two weeks soak end date : 6 April 2022 [X] Test promotion PR : According to this APIsnoop query, there are still some remaining Job status endpoints which are untested. There are conformance tests for CronJob status endpoints already the existing as a template, a new for job test has been created. The e2e logs for this test are listed below. This query shows the endpoints hit within a short period of running the e2e test If a test with these calls gets merged, test coverage will go up by 3 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance\n/triage accepted\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_108113", "tokennum": 205}], "negative_passages": []}
{"query_id": "q-en-kubernetes-0fea181f6260b7fe537170aff5b21e560ad57282d8c5165169fe965e578344db", "query": "} // validateCSINodeDriver tests if CSINodeDriver has valid entries <del> func validateCSINodeDriver(driver storage.CSINodeDriver, driverNamesInSpecs sets.String, fldPath *field.Path, </del> <ins> func validateCSINodeDriver(driver storage.CSINodeDriver, driverNamesInSpecs sets.Set[string], fldPath *field.Path, </ins> validationOpts CSINodeValidationOptions) field.ErrorList { allErrs := field.ErrorList{}", "positive_passages": [{"docid": "doc-en-kubernetes-c6679bcd8f59ea95eb0b6a4e2bf394545d09b32db20c61705567c0727bbb7817", "text": "It seems to be valid to add here. Would you like to open a pull request for it? this is like a cleanup, as the set insert will skip and the validation will do twice. is used to track bugs. I suggest you open a PR for that if you like.\n/sig storage\nI think adding ` == true and we didn't skip, it will insert set twice I believe? wasn't notice that at first glance. However, I can file a PR now\n/triage accepted\nThe label cannot be applied. Only GitHub organization members can add the label. <detailsIn response to : /triage accepted 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\n/triage accepted\nPlease feel free to submit a PR.", "commid": "kubernetes_issue_117027", "tokennum": 176}], "negative_passages": []}
{"query_id": "q-en-kubernetes-10187efb51f6155c79cf38dfde0508802a82ace79d84abdf2e03a0ea2848accb", "query": "return nil, nil, nil, err } <del> leaderElectionClient, err := clientset.NewForConfig(restclient.AddUserAgent(kubeConfig, \"leader-election\")) </del> <ins> // shallow copy, do not modify the kubeConfig.Timeout. restConfig := *kubeConfig restConfig.Timeout = timeout leaderElectionClient, err := clientset.NewForConfig(restclient.AddUserAgent(&restConfig, \"leader-election\")) </ins> if err != nil { return nil, nil, nil, err }", "positive_passages": [{"docid": "doc-en-kubernetes-638d244f4d44257351ae4786f705d88f47a0e12c74ce71a459164cb07c9c1943", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: kube-cm kube-scheduler does not exit when kube-apiserver suspended What you expected to happen: kube-cm kube-scheduler should exit after LeaderElector stops leading How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/sig api-machinery /kind bug\n/assign\n/cc", "commid": "kubernetes_issue_65090", "tokennum": 179}], "negative_passages": []}
{"query_id": "q-en-kubernetes-104ad197bf735db95d76b4e9163b3ba6d65fa4c2e264e4b237c1add4979cf977", "query": "fieldPath: metadata.namespace # END_PROMETHEUS_TO_SD nodeSelector: <del> # TODO(liggitt): switch to cloud.google.com/metadata-proxy-ready=true in v1.16 beta.kubernetes.io/metadata-proxy-ready: \"true\" </del> <ins> cloud.google.com/metadata-proxy-ready: \"true\" </ins> beta.kubernetes.io/os: linux terminationGracePeriodSeconds: 30", "positive_passages": [{"docid": "doc-en-kubernetes-2c9ef8984ebaf899659836b925069334113c910fc47ebe0516a7d659674f044a", "text": "xref In 1.16: change the metadata-proxy addon to use change the kube-proxy addon to use change the masq-agent addon to use stop setting , , and in kube-up\nHey I'm trying to start to contribute to kubernetes and this seem to be an easy task. Can I help with this one?", "commid": "kubernetes_issue_75050", "tokennum": 77}], "negative_passages": []}
{"query_id": "q-en-kubernetes-105f5b742976b63369331fb97c69c060e0115aa70674bd42603555ef4ead905f", "query": "Logf(\"Getting external IP address for %s\", node.Name) host := \"\" for _, a := range node.Status.Addresses { <del> if a.Type == v1.NodeExternalIP { </del> <ins> if a.Type == v1.NodeExternalIP && a.Address != \"\" { </ins> host = net.JoinHostPort(a.Address, sshPort) break }", "positive_passages": [{"docid": "doc-en-kubernetes-3fbd6fe4c52deabe3c900459c29c36a04807fdd1453263d11d2244d21f4a4f4a", "text": "Public IPs are expensive resources. Given that we're running scalability tests on 5k-node clusters, we are unnecessarily consuming 5k IPs which is a lot. We should switch our tests so that nodes have only private IP addresses. We are going to do that by configuring NAT so that nodes can talk to outside world (e.g. to download image from dockerhub). But that also requires changing some correctness tests which assume public IPs.\nTo summarize recent work: setting up private gce clusters with nat, feature is gated via the env test and dashboard with correctness tests on gce private cluster - https://k8s- 27 tests fail on fixing the tests - should fix majority of them\nIssues 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\n/remove-lifecycle stale /lifecycle frozen\n- is there anything missing to be done here?\nNo, we can close this one. It was done long time ago. Thanks for catching /close\nClosing this issue. <detailsIn response to : No, we can close this one. It was done long time ago. Thanks for catching 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", "commid": "kubernetes_issue_76374", "tokennum": 335}], "negative_passages": []}
{"query_id": "q-en-kubernetes-106f397c7d6060fb74318da6c04a7b47c3317049601c7174116a3273b58295fa", "query": "// GCECloud is an implementation of Interface, LoadBalancer and Instances for Google Compute Engine. type GCECloud struct { <del> service                  *compute.Service containerService         *container.Service projectID                string region                   string localZone                string   // The zone in which we are running managedZones             []string // List of zones we are spanning (for Ubernetes-Lite, primarily when running on master) networkURL               string nodeTags                 []string // List of tags to use on firewall rules for load balancers useMetadataServer        bool operationPollRateLimiter flowcontrol.RateLimiter </del> <ins> service           *compute.Service containerService  *container.Service projectID         string region            string localZone         string   // The zone in which we are running managedZones      []string // List of zones we are spanning (for Ubernetes-Lite, primarily when running on master) networkURL        string nodeTags          []string // List of tags to use on firewall rules for load balancers useMetadataServer bool </ins> } type Config struct {", "positive_passages": [{"docid": "doc-en-kubernetes-599cbd9914ac52a34ee08ac617d1f4bd774f52f2d5bdcb07fa1a0e76f7194545", "text": "On a large cluster, the routecontroller basically makes O(n) requests all at once, and most of them error out with \"Rate Limit Exceeded\". We then wait for operations to complete on the ones that did stick, and damn the rest, they'll be caught next reconcile (which is a while). In fact, in some cases it appears we're spamming hard enough to get rate limited by the upper-level API DOS protections and seeing something akin to , e.g.: We can do better than this!\nc.f. , which is the other leg of this problem\nI took a look into code and it seems that we are doing full reconciliation every 10s. If we need to create 2000 routes at the beginning it seems to frequently. I think that we need to: first compute how many routes we have to create based on that try to spread them over some time to reduce possibility of causing 'rate limit exceeded' I will try to put some small PR together as a starting point.\nI'm reopening this one, since this doesn't seem to be solved. So basically something strange is happening here. With PR we have 10/s limit on API calls send to GCE. And we are still rate-limitted. However, according to documentation we are allowed for 20/s: So something either doesn't work or is weird.\nWhat is super interesting from the logs of recent run: It starts to creating routes: After 2 minutes from that, we are hitting \"Rate limit Exceeded\" for the first time: And only after 9 minutes we create the first route ever. The second one is created after 15 minutes, and from that point we create a number of them So it seems that nothing useful is happening for the first 2 minutes, and then between 3m30 and 9m30\nOK - so I think that what is happening is that all controllers are sharing GCE interface (and thuse they have common throttling). So if one controller is generating a lot of API calls, then other controllers may be throttled. has a hypothesis that it may be caused by nodecontroller.\nOne thing my PR didn't address (because it was late): Now we have some obnoxious differences in logging when you go to make a request, because the versus could actually be absorbing a fair amount of ratelimiter.", "commid": "kubernetes_issue_26119", "tokennum": 488}], "negative_passages": []}
{"query_id": "q-en-kubernetes-106f397c7d6060fb74318da6c04a7b47c3317049601c7174116a3273b58295fa", "query": "// GCECloud is an implementation of Interface, LoadBalancer and Instances for Google Compute Engine. type GCECloud struct { <del> service                  *compute.Service containerService         *container.Service projectID                string region                   string localZone                string   // The zone in which we are running managedZones             []string // List of zones we are spanning (for Ubernetes-Lite, primarily when running on master) networkURL               string nodeTags                 []string // List of tags to use on firewall rules for load balancers useMetadataServer        bool operationPollRateLimiter flowcontrol.RateLimiter </del> <ins> service           *compute.Service containerService  *container.Service projectID         string region            string localZone         string   // The zone in which we are running managedZones      []string // List of zones we are spanning (for Ubernetes-Lite, primarily when running on master) networkURL        string nodeTags          []string // List of tags to use on firewall rules for load balancers useMetadataServer bool </ins> } type Config struct {", "positive_passages": [{"docid": "doc-en-kubernetes-bf24c8733a67a958496376416be2eb636c6e4bfb94999815173220461c93fd0c", "text": "It could before because of the operation rate limiter and operation polling anyways, but now could be worse.\n- yes I'm aware of that. And probably this is exactly the case here.\nI got fooled by that - I guess we should fix it somehow.\nOne approach to fixing it is a similar approach to the operation polling code, but in the : warn if we ratelimited for more than N seconds (and dump the request or something? not clear how to clarify what we were sending).\nI found something else - Kubelet is also building GCE interface: We have 2000 kubelets, so if all of them send multiple requests to GCE, we may hit limits.\nAny idea in what circumstances Kubelet will contact cloud provider?\nHmm - it seems it contacts GCE exactly once at the beginning. So it doesn't explain much.\nI think it's only here: I've rarely seen GCE ratelimit readonly calls, in practice, and kubelets come up pretty well staggered.\nOK - so with logs that I , it is pretty clear that we are very heavily throttled on GCE api calls. In particular, when I was running 1000-node cluster, I see lines where we were throttle for 1m30. I'm pretty sure it's significantly higher in 2000-node cluster. I'm going to investigate a bit more where all those reuqests come from.\nActually - it seems that we have a pretty big problem here. Basically, Kubelet seems to send a lot of requests to GCE. So to clarify: every time Kubelet is updating NodeStatus (so every 10s by default) it is sending an API call to GCE to get it's not addresses: that means, that if we have 2000 nodes, kubelets generate 200 QPS to GCE (which is significantly more than we can afford) We should think how to solve this issue, but I think the options are: increasing QPS quota or calling GCE only once per X statusUpdates.\nThe second issue is that we are throttled at the controller level too, and this one I'm tryin to understand right now.", "commid": "kubernetes_issue_26119", "tokennum": 457}], "negative_passages": []}
{"query_id": "q-en-kubernetes-106f397c7d6060fb74318da6c04a7b47c3317049601c7174116a3273b58295fa", "query": "// GCECloud is an implementation of Interface, LoadBalancer and Instances for Google Compute Engine. type GCECloud struct { <del> service                  *compute.Service containerService         *container.Service projectID                string region                   string localZone                string   // The zone in which we are running managedZones             []string // List of zones we are spanning (for Ubernetes-Lite, primarily when running on master) networkURL               string nodeTags                 []string // List of tags to use on firewall rules for load balancers useMetadataServer        bool operationPollRateLimiter flowcontrol.RateLimiter </del> <ins> service           *compute.Service containerService  *container.Service projectID         string region            string localZone         string   // The zone in which we are running managedZones      []string // List of zones we are spanning (for Ubernetes-Lite, primarily when running on master) networkURL        string nodeTags          []string // List of tags to use on firewall rules for load balancers useMetadataServer bool </ins> } type Config struct {", "positive_passages": [{"docid": "doc-en-kubernetes-b1dad1b374e4c58d925d9fef62d9846d5e0e5eda04aecdd78a124036a36cf31c", "text": "- that said, any rate-limitting on our side, will not solve the kubelet-related problem\nHmm - actually looking into implementation it seems that NodeAddresses are only contacting metadata server, so I'm not longer that convinced...\nAlso, I think that important thing is that a single call to GCE API can translate to multiple api calls to GCE. In particular - CreateRoute translates to: get instance insert route a bunch of getOperation (until this is finished)\nOK - so I think that what is happening here is that since CreateRoute translates to: get instance insert route a bunch of getOperations That means that if we call say 2000 CreateRoute() at the same time, all of them will try to issue: getInstance at the beginning. So we will quickly accumulate 2000 GET requests in the queue. Once they are processed, we generate the \"POST route\" then for any processed. So It's kind of expected what is happening here. So getting back to the Zach`s PR - I think that throttling POST and GET and OPERATION calls separate is kind of good idea in general.\nBut I still don't really understand why do we get \"RateLimitExceeded\". Is that because of Kubelets?\nI think that one problem we have at the RouteController level is that if CreateRoute fails, we simply don't react on it. And we will wait at least 5 minutes before even retrying it. We should add some retries at the route controller level too. I will send out some short PR for it.\nBut I still don't understand why do we get those \"RateLimitExceeded\" error\nOK - so as an update. In GCE, we have a separate rate-limit for number of in-flight CreateRoute call per project. is supposed to address this issue.\nOK - so this one is actually fixed. I mean that it is still long, but currently it's purely blocked on GCE.\nAs a comment - we have an internal bug for it already.", "commid": "kubernetes_issue_26119", "tokennum": 438}], "negative_passages": []}
{"query_id": "q-en-kubernetes-109f66fad3e761a2c8e6fa7b819a5941619b0ac0e532c8c7da0fc2536c201e49", "query": "ConsumeMemAddress       = \"/ConsumeMem\" BumpMetricAddress       = \"/BumpMetric\" GetCurrentStatusAddress = \"/GetCurrentStatus\" <del> MetricsAddress          = \"/Metrics\" </del> <ins> MetricsAddress          = \"/metrics\" </ins> MillicoresQuery              = \"millicores\" MegabytesQuery               = \"megabytes\"", "positive_passages": [{"docid": "doc-en-kubernetes-2d0ebe90b3c755e0edf33c6811bf431b4c51fd00f4f7b6a1d49649dd59cb487b", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: Used the endpoint /BumpMetric to create fake metrics for Prometheus. When I tried to curl /metrics I got the following response: Bad request. Not a POST request What you expected to happen: I expected to see something like this: # HELP info message. # TYPE gauge 0. How to reproduce it (as minimally and precisely as possible): Following the docs, after having it running inside kubernetes: Anything else we need to know?: Looks like introduced this by mistake. Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: <!-- DO NOT EDIT BELOW THIS LINE --/kind bug\n/sig testing", "commid": "kubernetes_issue_72403", "tokennum": 213}], "negative_passages": []}
{"query_id": "q-en-kubernetes-10abaf67cb7c330032311b8f35245826c7cec33eea327aee85a271caf60b5a55", "query": "<ins> /* Copyright 2018 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package cmd import ( \"fmt\" \"io\" \"sort\" \"strings\" \"github.com/spf13/cobra\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/runtime/schema\" \"k8s.io/apimachinery/pkg/util/sets\" \"k8s.io/kubernetes/pkg/kubectl/cmd/templates\" cmdutil \"k8s.io/kubernetes/pkg/kubectl/cmd/util\" \"k8s.io/kubernetes/pkg/printers\" ) var ( apiresources_example = templates.Examples(` # Print the supported API Resources kubectl api-resources # Print the supported API Resources with more information kubectl api-resources -o wide # Print the supported namespaced resources kubectl api-resources --namespaced=true # Print the supported non-namespaced resources kubectl api-resources --namespaced=false # Print the supported API Resources with specific APIGroup kubectl api-resources --api-group=extensions`) ) // ApiResourcesOptions is the start of the data required to perform the operation.  As new fields are added, add them here instead of // referencing the cmd.Flags() type ApiResourcesOptions struct { out io.Writer Output     string APIGroup   string Namespaced bool NoHeaders  bool } // groupResource contains the APIGroup and APIResource type groupResource struct { APIGroup    string APIResource metav1.APIResource } func NewCmdApiResources(f cmdutil.Factory, out io.Writer) *cobra.Command { options := &ApiResourcesOptions{ out: out, } cmd := &cobra.Command{ Use:     \"api-resources\", Short:   \"Print the supported API resources on the server\", Long:    \"Print the supported API resources on the server\", Example: apiresources_example, Run: func(cmd *cobra.Command, args []string) { cmdutil.CheckErr(options.Complete(cmd)) cmdutil.CheckErr(options.Validate(cmd)) cmdutil.CheckErr(options.RunApiResources(cmd, f)) }, } cmdutil.AddOutputFlags(cmd) cmdutil.AddNoHeadersFlags(cmd) cmd.Flags().StringVar(&options.APIGroup, \"api-group\", \"\", \"The API group to use when talking to the server.\") cmd.Flags().BoolVar(&options.Namespaced, \"namespaced\", true, \"Namespaced indicates if a resource is namespaced or not.\") return cmd } func (o *ApiResourcesOptions) Complete(cmd *cobra.Command) error { o.Output = cmdutil.GetFlagString(cmd, \"output\") o.NoHeaders = cmdutil.GetFlagBool(cmd, \"no-headers\") return nil } func (o *ApiResourcesOptions) Validate(cmd *cobra.Command) error { validOutputTypes := sets.NewString(\"\", \"json\", \"yaml\", \"wide\", \"name\", \"custom-columns\", \"custom-columns-file\", \"go-template\", \"go-template-file\", \"jsonpath\", \"jsonpath-file\") supportedOutputTypes := sets.NewString(\"\", \"wide\") outputFormat := cmdutil.GetFlagString(cmd, \"output\") if !validOutputTypes.Has(outputFormat) { return fmt.Errorf(\"output must be one of '' or 'wide': %v\", outputFormat) } if !supportedOutputTypes.Has(outputFormat) { return fmt.Errorf(\"--output %v is not available in kubectl api-resources\", outputFormat) } return nil } func (o *ApiResourcesOptions) RunApiResources(cmd *cobra.Command, f cmdutil.Factory) error { w := printers.GetNewTabWriter(o.out) defer w.Flush() discoveryclient, err := f.DiscoveryClient() if err != nil { return err } // Always request fresh data from the server discoveryclient.Invalidate() lists, err := discoveryclient.ServerPreferredResources() if err != nil { return err } resources := []groupResource{} groupChanged := cmd.Flags().Changed(\"api-group\") nsChanged := cmd.Flags().Changed(\"namespaced\") for _, list := range lists { if len(list.APIResources) == 0 { continue } gv, err := schema.ParseGroupVersion(list.GroupVersion) if err != nil { continue } for _, resource := range list.APIResources { if len(resource.Verbs) == 0 { continue } // filter apiGroup if groupChanged && o.APIGroup != gv.Group { continue } // filter namespaced if nsChanged && o.Namespaced != resource.Namespaced { continue } resources = append(resources, groupResource{ APIGroup:    gv.Group, APIResource: resource, }) } } if o.NoHeaders == false { if err = printContextHeaders(w, o.Output); err != nil { return err } } sort.Stable(sortableGroupResource(resources)) for _, r := range resources { if o.Output == \"wide\" { if _, err := fmt.Fprintf(w, \"%st%st%st%vt%st%vn\", r.APIResource.Name, strings.Join(r.APIResource.ShortNames, \",\"), r.APIGroup, r.APIResource.Namespaced, r.APIResource.Kind, r.APIResource.Verbs); err != nil { return err } } else { if _, err := fmt.Fprintf(w, \"%st%st%st%vt%sn\", r.APIResource.Name, strings.Join(r.APIResource.ShortNames, \",\"), r.APIGroup, r.APIResource.Namespaced, r.APIResource.Kind); err != nil { return err } } } return nil } func printContextHeaders(out io.Writer, output string) error { columnNames := []string{\"NAME\", \"SHORTNAMES\", \"APIGROUP\", \"NAMESPACED\", \"KIND\"} if output == \"wide\" { columnNames = append(columnNames, \"VERBS\") } _, err := fmt.Fprintf(out, \"%sn\", strings.Join(columnNames, \"t\")) return err } type sortableGroupResource []groupResource func (s sortableGroupResource) Len() int      { return len(s) } func (s sortableGroupResource) Swap(i, j int) { s[i], s[j] = s[j], s[i] } func (s sortableGroupResource) Less(i, j int) bool { ret := strings.Compare(s[i].APIGroup, s[j].APIGroup) if ret > 0 { return false } else if ret == 0 { return strings.Compare(s[i].APIResource.Name, s[j].APIResource.Name) < 0 } return true } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-3c17ea4b4f4a9bb23915ee9fbb41703ef0532ac00becc05b8dda4d23a9ea9da2", "text": "As the RBAC role need to be related to resources. I think we could use a command to get the supported resources. ref to\nThis would be cool.\nI thought we a command that listed resources in the discover doc a long time ago.\nis just the versions, but principle is the same. We want to list all the types, their resources, and tie that back to \"explain\".\nWhat's the best way to determine this information currently? I'm having difficulty figuring out the exact set of permissions (and how they would be written in an RBAC role) for any given kubectl command. The documentation for this right now is split across multiple places and certain things are not explained at all. Specifically, it's difficult to determine which \"API verb\" is used for which operations. Take as an example. It's unclear if the way to allow this is to use the \"proxy\" subresource of a pod or service with \"get\"/\"create\"/etc. verbs, or to use the \"proxy\" verb with the resource (pod, service) directly. is a similar case. The almost works for this purpose, but it's still difficult. Operations for a given resource are grouped into categories like write, read, status, and proxy, but these things don't obviously correlate with API verbs. Again, proxy is especially confusing as there is no mention of a proxy \"verb\". The API operations are only shown using their HTTP verbs. One thing that could help on this document would be a section on the right column under \"kubectl command\" that shows exactly the rule needed in an RBAC role to allow this command via kubectl. And even then, that assumes an exact 1-to-1 mapping between API endpoints and kubectl commands, which I doubt is always the case. (For example, port fowarding to a pod seems to require both a GET on the pod resource and a CREATE on a port forward subresource.) There also needs to be better documentation about how this information could have been determined in the first place. I've resorted to manually looking through API requests made with but even then it's difficult to figure out. Amusingly, I was the one who wrote which is referenced in the original issue description (as well as the table explaining verbs in ).", "commid": "kubernetes_issue_42932", "tokennum": 494}], "negative_passages": []}
{"query_id": "q-en-kubernetes-10abaf67cb7c330032311b8f35245826c7cec33eea327aee85a271caf60b5a55", "query": "<ins> /* Copyright 2018 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package cmd import ( \"fmt\" \"io\" \"sort\" \"strings\" \"github.com/spf13/cobra\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/runtime/schema\" \"k8s.io/apimachinery/pkg/util/sets\" \"k8s.io/kubernetes/pkg/kubectl/cmd/templates\" cmdutil \"k8s.io/kubernetes/pkg/kubectl/cmd/util\" \"k8s.io/kubernetes/pkg/printers\" ) var ( apiresources_example = templates.Examples(` # Print the supported API Resources kubectl api-resources # Print the supported API Resources with more information kubectl api-resources -o wide # Print the supported namespaced resources kubectl api-resources --namespaced=true # Print the supported non-namespaced resources kubectl api-resources --namespaced=false # Print the supported API Resources with specific APIGroup kubectl api-resources --api-group=extensions`) ) // ApiResourcesOptions is the start of the data required to perform the operation.  As new fields are added, add them here instead of // referencing the cmd.Flags() type ApiResourcesOptions struct { out io.Writer Output     string APIGroup   string Namespaced bool NoHeaders  bool } // groupResource contains the APIGroup and APIResource type groupResource struct { APIGroup    string APIResource metav1.APIResource } func NewCmdApiResources(f cmdutil.Factory, out io.Writer) *cobra.Command { options := &ApiResourcesOptions{ out: out, } cmd := &cobra.Command{ Use:     \"api-resources\", Short:   \"Print the supported API resources on the server\", Long:    \"Print the supported API resources on the server\", Example: apiresources_example, Run: func(cmd *cobra.Command, args []string) { cmdutil.CheckErr(options.Complete(cmd)) cmdutil.CheckErr(options.Validate(cmd)) cmdutil.CheckErr(options.RunApiResources(cmd, f)) }, } cmdutil.AddOutputFlags(cmd) cmdutil.AddNoHeadersFlags(cmd) cmd.Flags().StringVar(&options.APIGroup, \"api-group\", \"\", \"The API group to use when talking to the server.\") cmd.Flags().BoolVar(&options.Namespaced, \"namespaced\", true, \"Namespaced indicates if a resource is namespaced or not.\") return cmd } func (o *ApiResourcesOptions) Complete(cmd *cobra.Command) error { o.Output = cmdutil.GetFlagString(cmd, \"output\") o.NoHeaders = cmdutil.GetFlagBool(cmd, \"no-headers\") return nil } func (o *ApiResourcesOptions) Validate(cmd *cobra.Command) error { validOutputTypes := sets.NewString(\"\", \"json\", \"yaml\", \"wide\", \"name\", \"custom-columns\", \"custom-columns-file\", \"go-template\", \"go-template-file\", \"jsonpath\", \"jsonpath-file\") supportedOutputTypes := sets.NewString(\"\", \"wide\") outputFormat := cmdutil.GetFlagString(cmd, \"output\") if !validOutputTypes.Has(outputFormat) { return fmt.Errorf(\"output must be one of '' or 'wide': %v\", outputFormat) } if !supportedOutputTypes.Has(outputFormat) { return fmt.Errorf(\"--output %v is not available in kubectl api-resources\", outputFormat) } return nil } func (o *ApiResourcesOptions) RunApiResources(cmd *cobra.Command, f cmdutil.Factory) error { w := printers.GetNewTabWriter(o.out) defer w.Flush() discoveryclient, err := f.DiscoveryClient() if err != nil { return err } // Always request fresh data from the server discoveryclient.Invalidate() lists, err := discoveryclient.ServerPreferredResources() if err != nil { return err } resources := []groupResource{} groupChanged := cmd.Flags().Changed(\"api-group\") nsChanged := cmd.Flags().Changed(\"namespaced\") for _, list := range lists { if len(list.APIResources) == 0 { continue } gv, err := schema.ParseGroupVersion(list.GroupVersion) if err != nil { continue } for _, resource := range list.APIResources { if len(resource.Verbs) == 0 { continue } // filter apiGroup if groupChanged && o.APIGroup != gv.Group { continue } // filter namespaced if nsChanged && o.Namespaced != resource.Namespaced { continue } resources = append(resources, groupResource{ APIGroup:    gv.Group, APIResource: resource, }) } } if o.NoHeaders == false { if err = printContextHeaders(w, o.Output); err != nil { return err } } sort.Stable(sortableGroupResource(resources)) for _, r := range resources { if o.Output == \"wide\" { if _, err := fmt.Fprintf(w, \"%st%st%st%vt%st%vn\", r.APIResource.Name, strings.Join(r.APIResource.ShortNames, \",\"), r.APIGroup, r.APIResource.Namespaced, r.APIResource.Kind, r.APIResource.Verbs); err != nil { return err } } else { if _, err := fmt.Fprintf(w, \"%st%st%st%vt%sn\", r.APIResource.Name, strings.Join(r.APIResource.ShortNames, \",\"), r.APIGroup, r.APIResource.Namespaced, r.APIResource.Kind); err != nil { return err } } } return nil } func printContextHeaders(out io.Writer, output string) error { columnNames := []string{\"NAME\", \"SHORTNAMES\", \"APIGROUP\", \"NAMESPACED\", \"KIND\"} if output == \"wide\" { columnNames = append(columnNames, \"VERBS\") } _, err := fmt.Fprintf(out, \"%sn\", strings.Join(columnNames, \"t\")) return err } type sortableGroupResource []groupResource func (s sortableGroupResource) Len() int      { return len(s) } func (s sortableGroupResource) Swap(i, j int) { s[i], s[j] = s[j], s[i] } func (s sortableGroupResource) Less(i, j int) bool { ret := strings.Compare(s[i].APIGroup, s[j].APIGroup) if ret > 0 { return false } else if ret == 0 { return strings.Compare(s[i].APIResource.Name, s[j].APIResource.Name) < 0 } return true } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-20fd632aaf82ba3efee7609ebeda29ca6df3199abf73ef8bcfe417660974a0ce", "text": "tl;dr: It's too difficult right now to go from \"I want a user to be able to run \" to \"here is the RBAC rule to use for that\" for any case where there isn't a specific example shown in the docs.\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nIt seem that relative PR stop updated. If this issue still valuable, i will help fix it\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close", "commid": "kubernetes_issue_42932", "tokennum": 279}], "negative_passages": []}
{"query_id": "q-en-kubernetes-10d365c208452025a8f46777893f83dec640340c6d47a893cdec65b77c121550", "query": "// have a place they can schedule. testRootDir = makeTempDirOrDie(\"kubelet_integ_2.\", \"\") glog.Infof(\"Using %s as root dir for kubelet #2\", testRootDir) <del> kcfg = kubeletapp.SimpleKubelet(cl, &fakeDocker2, machineList[1], testRootDir, \"\", \"127.0.0.1\", 10251, api.NamespaceDefault, empty_dir.ProbeVolumePlugins(), nil, cadvisorInterface, \"\") </del> <ins> kcfg = kubeletapp.SimpleKubelet(cl, &fakeDocker2, machineList[1], testRootDir, secondManifestURL, \"127.0.0.1\", 10251, api.NamespaceDefault, empty_dir.ProbeVolumePlugins(), nil, cadvisorInterface, \"\") </ins> kcfg.PodStatusUpdateFrequency = 1 * time.Second kubeletapp.RunKubelet(kcfg) return apiServer.URL, configFilePath", "positive_passages": [{"docid": "doc-en-kubernetes-56027fa26048aea64718f2bd7d7c5d6f58ddca1472c1fc738c03141b6dea3ad6", "text": "Currently it assumes it can read ContainerManifest - it should try both\nWhy not hold on this until we have Kubelet-read-Pod in?\nAlso the HTTP source has the same problem.\nIt should read Pod. Changed the title.\nIdeally, I'd like all Pods created directly via Kubelet to be to etcd and surfaced via the API. If updates are made via the API, I'd like those to propagate back to the node. We can discuss whether the config file should be updated or ignored. At some point, I'd like Kubelet to persistently cache pods received from the apiserver, perhaps by just writing them all out as config files.\nis the issue to sync local pods back to apiserver.\nthis is somewhat related to other issues we talked about.\nDetail: We want locally specified pods to be able to use YAML config files, but we also want to rip YAML out of the API server . The config-file behavior should be as similar to the kubectl experience. Kubelet could use parts of the kubectl library to translate YAML to JSON. Vision: Eventually, I'd like Kubelet to use the apiserver library and support exactly the same Pod API as the master, at which time I'd like kubectl be able to create pods directly on Kubelets, as well as reading from config files. I also expect to have a per-node controller . I'd like to be able to use the per-node controller to update pods started via config files (or direct kubectl-kubelet pods), overriding those original files. For availability and self-hosting, we'll eventually need local checkpointing , ideally just using serialized JSON for each object. If Kubelet used apiserver, this could be done using a custom registry implementation.\nI think that is a prerequisite for it.\nIf noone picks it up, I'm going to start working on it tomorrow.\nthanks, wojtek-t\nfixed it for http channel", "commid": "kubernetes_issue_3372", "tokennum": 445}], "negative_passages": []}
{"query_id": "q-en-kubernetes-10f033261a772529f226fae74f3d221671b9839ee7a71e22778960ca5b6b7121", "query": "kind: Pod metadata: name: b <ins> namespace: nsb </ins> labels: prune-group: \"true\" spec:", "positive_passages": [{"docid": "doc-en-kubernetes-55af5a538910186290479e8a37adc800d26766e6d09583162f76a512f0433ab7", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Actually, the parameter depends to all namespaces in the cluster. Filtering is only possible with labels. When running the should only depend on the objects defined in . Why is this needed: A typical use-case is having one repository and namespace per project. When working with declarative objects it should be possible to remove objects and get them pruned like having them described in the respository. This would also help when renaming objects within the repository - which actually needs a manual on the host for the old objects. This even could be a better solution for the problem described in\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig api-machinery\ncc\n/assign\nGitHub didn't allow me to assign the following users: Liujingfang1. Note that only and repo collaborators can be assigned and that 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\nWe have been aware of the issues in prune and we want to improve it. Recently we opened a for improving pruning in . With the proposed solution, the problem from current will be fixed.\nIssues 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\n/remove-lifecycle stale\nIssues 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 .", "commid": "kubernetes_issue_74414", "tokennum": 481}], "negative_passages": []}
{"query_id": "q-en-kubernetes-10f033261a772529f226fae74f3d221671b9839ee7a71e22778960ca5b6b7121", "query": "kind: Pod metadata: name: b <ins> namespace: nsb </ins> labels: prune-group: \"true\" spec:", "positive_passages": [{"docid": "doc-en-kubernetes-cb54288fa32d0be96e99fcb10abda15ff9759ea2461e12485115b7e51b53055d", "text": "/lifecycle stale\n/remove-lifecycle stale\nI just deleted a bunch of things in another team's namespace (:blush:). I'd would love to have this feature. I had been using dry-run in another context, but then forgot to check it again after switching contexts.\nIs there any workaround for this? I want to prune resources within a single namespace only.\nWe're still working on improving prune, the current mechanism is broken enough that we don't recommend people us it.\nAlso look like it's been fixed recently.\nCan someone confirm if this is implemented? I tried using this feature with kubectl 1.18.2, which has , yet as with previous versions kubectl it returned an error about pruning a nonNamespaced object of kind Namespace.\nI assume the problem is that \"Namespace\" is a non-namespaced resource, and therefore is not filtered by namespace, so gets deleted by \"prune\". As a workaround it's possible to manually pass a (whitelist of resources allowed to be deleted), and not include \"Namespace\" in it: The list of resources is taken from .\nWould wrapping this loop with achieve the same result?", "commid": "kubernetes_issue_74414", "tokennum": 262}], "negative_passages": []}
{"query_id": "q-en-kubernetes-113aeead39e8af4504fecb1c2529c94203bfbe9d643650eedefa712e4e83d1f5", "query": "return nil, cleanupAction, fmt.Errorf(\"volume subpaths are disabled\") } <del> if !utilfeature.DefaultFeatureGate.Enabled(features.VolumeSubpathEnvExpansion) { return nil, cleanupAction, fmt.Errorf(\"volume subpath expansion is disabled\") } </del> subPath, err = kubecontainer.ExpandContainerVolumeMounts(mount, expandEnvs) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-a166ddd65322b2b4c2d8cbe35891249f4d033568413f3b77fc1f46ee1d1ee8b8", "text": "/kind cleanup /sig storage /sig node Description: Feature gate VolumeSubpathEnvExpansion was GA in 1.17 and is marked for removal in 1.19 Related Issues: GA Release:\n/assign\n/cc", "commid": "kubernetes_issue_89519", "tokennum": 48}], "negative_passages": []}
{"query_id": "q-en-kubernetes-11418ab700b0e88cf5bcf7563597032e7bd44b4ec5881c6b5a3dc2b33abe94c4", "query": "func CheckAffinity(execPod *v1.Pod, serviceIP string, servicePort int, shouldHold bool) bool { serviceIPPort := net.JoinHostPort(serviceIP, strconv.Itoa(servicePort)) cmd := fmt.Sprintf(`curl -q -s --connect-timeout 2 http://%s/`, serviceIPPort) <del> timeout := TestTimeout </del> <ins> timeout := AffinityTimeout </ins> if execPod == nil { timeout = LoadBalancerPollTimeout }", "positive_passages": [{"docid": "doc-en-kubernetes-3bd2c8928ffbfbb644dae4df3d9fa0aa73d567a5bc560c59938e22bd3dd510ca", "text": "Which jobs are failing: pull-kubernetes-e2e-gce Which test(s) are failing: [sig-network] Services should have session affinity work for NodePort service [LinuxOnly] [sig-network] Services should be able to switch session affinity for service with type clusterIP [LinuxOnly] [sig-network] Services should be able to switch session affinity for NodePort service [LinuxOnly] [sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] Since when has it been failing: At least since 9/30 (). But that's almost at the end of what's currently visible on the testgrid, so maybe longer Testgrid link: Not sure what I'm supposed to put here. ? Reason for failure: The test case connects to a service every 2 seconds for 1 minute and checks if it hit the same endpoint at least 15 times in a row. But the individual checks are taking unexpectedly long and so sometimes the test doesn't even manage to run 15 times total in 1 minute.", "commid": "kubernetes_issue_83617", "tokennum": 235}], "negative_passages": []}
{"query_id": "q-en-kubernetes-11418ab700b0e88cf5bcf7563597032e7bd44b4ec5881c6b5a3dc2b33abe94c4", "query": "func CheckAffinity(execPod *v1.Pod, serviceIP string, servicePort int, shouldHold bool) bool { serviceIPPort := net.JoinHostPort(serviceIP, strconv.Itoa(servicePort)) cmd := fmt.Sprintf(`curl -q -s --connect-timeout 2 http://%s/`, serviceIPPort) <del> timeout := TestTimeout </del> <ins> timeout := AffinityTimeout </ins> if execPod == nil { timeout = LoadBalancerPollTimeout }", "positive_passages": [{"docid": "doc-en-kubernetes-be859aec3019c8f94fa574b44096bac92d128f839b0ed157072d5b09f5ea53f4", "text": "eg: Oct 8 13:32:01.402: INFO: Running ' --server=https://34.82.143.14 -- exec --namespace=services-1060 execpod-affinityklpfn -- /bin/sh -x -c curl -q -s --connect-timeout 2 http://10.40.0.5:/' Oct 8 13:32:07.627: INFO: stderr: \"+ curl -q -s --connect-timeout 2 http://10.40.0.5:/n\" Oct 8 13:32:07.627: INFO: stdout: \"affinity-nodeport-2z9hv\" Oct 8 13:32:07.627: INFO: Received response from host: affinity-nodeport-2z9hv Oct 8 13:32:09.402: INFO: Running ' --server=https://34.82.143.14 -- exec --namespace=services-1060 execpod-affinityklpfn -- /bin/sh -x -c curl -q -s --connect-timeout 2 http://10.40.0.5:/' Oct 8 13:32:16.027: INFO: stderr: \"+ curl -q -s --connect-timeout 2 http://10.40.0.5:/n\" Oct 8 13:32:16.027: INFO: stdout: \"affinity-nodeport-2z9hv\" Oct 8 13:32:16.027: INFO: Received response from host: affinity-nodeport-2z9hv Note the gap between the \"Running\" line and the \"stderr\" line. It's not clear if the slowness is in connecting to the execpod or in connecting from the execpod to the affinity service. It is also not particularly consistent between attempts. (Here it was 6s, 1s, 2s, 3s, 5s, 7s, 7s, 3s, 4s, 6s, 7s, 8s.) Anything else we need to know: It looks the checks are also slow in successful runs, it's just that they're not quite as slow, so they pass.", "commid": "kubernetes_issue_83617", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-11418ab700b0e88cf5bcf7563597032e7bd44b4ec5881c6b5a3dc2b33abe94c4", "query": "func CheckAffinity(execPod *v1.Pod, serviceIP string, servicePort int, shouldHold bool) bool { serviceIPPort := net.JoinHostPort(serviceIP, strconv.Itoa(servicePort)) cmd := fmt.Sprintf(`curl -q -s --connect-timeout 2 http://%s/`, serviceIPPort) <del> timeout := TestTimeout </del> <ins> timeout := AffinityTimeout </ins> if execPod == nil { timeout = LoadBalancerPollTimeout }", "positive_passages": [{"docid": "doc-en-kubernetes-0f765c22d0d19db3b6df2fd444c9da8d7f7f8af548830f46d73b17c37e323eed", "text": "I'm not sure if the problem is \"something is making the cluster slow and so this totally valid test is taking too long and failing\" or \"e2e-gce has grown over time and now cluster load has reached the point where this formerly-passing test now has unreasonable performance expectations\". /sig network", "commid": "kubernetes_issue_83617", "tokennum": 66}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1164aec3e1c35848a8f471a980369a40628f3a3744ba906a5426f3c88f297fc6", "query": "return json.Marshal(doc) } <del> // CreateMergePatch creates a merge patch as specified in http://tools.ietf.org/html/draft-ietf-appsawg-json-merge-patch-07 // // 'a' is original, 'b' is the modified document. Both are to be given as json encoded content. // The function will return a mergeable json document with differences from a to b. // // An error will be returned if any of the two documents are invalid. func CreateMergePatch(a, b []byte) ([]byte, error) { aI := map[string]interface{}{} bI := map[string]interface{}{} err := json.Unmarshal(a, &aI) </del> <ins> // resemblesJSONArray indicates whether the byte-slice \"appears\" to be // a JSON array or not. // False-positives are possible, as this function does not check the internal // structure of the array. It only checks that the outer syntax is present and // correct. func resemblesJSONArray(input []byte) bool { input = bytes.TrimSpace(input) hasPrefix := bytes.HasPrefix(input, []byte(\"[\")) hasSuffix := bytes.HasSuffix(input, []byte(\"]\")) return hasPrefix && hasSuffix } // CreateMergePatch will return a merge patch document capable of converting // the original document(s) to the modified document(s). // The parameters can be bytes of either two JSON Documents, or two arrays of // JSON documents. // The merge patch returned follows the specification defined at http://tools.ietf.org/html/draft-ietf-appsawg-json-merge-patch-07 func CreateMergePatch(originalJSON, modifiedJSON []byte) ([]byte, error) { originalResemblesArray := resemblesJSONArray(originalJSON) modifiedResemblesArray := resemblesJSONArray(modifiedJSON) // Do both byte-slices seem like JSON arrays? if originalResemblesArray && modifiedResemblesArray { return createArrayMergePatch(originalJSON, modifiedJSON) } // Are both byte-slices are not arrays? Then they are likely JSON objects... if !originalResemblesArray && !modifiedResemblesArray { return createObjectMergePatch(originalJSON, modifiedJSON) } // None of the above? Then return an error because of mismatched types. return nil, errBadMergeTypes } // createObjectMergePatch will return a merge-patch document capable of // converting the original document to the modified document. func createObjectMergePatch(originalJSON, modifiedJSON []byte) ([]byte, error) { originalDoc := map[string]interface{}{} modifiedDoc := map[string]interface{}{} err := json.Unmarshal(originalJSON, &originalDoc) </ins> if err != nil { return nil, errBadJSONDoc } <del> err = json.Unmarshal(b, &bI) </del> <ins> err = json.Unmarshal(modifiedJSON, &modifiedDoc) </ins> if err != nil { return nil, errBadJSONDoc } <del> dest, err := getDiff(aI, bI) </del> <ins> dest, err := getDiff(originalDoc, modifiedDoc) </ins> if err != nil { return nil, err } return json.Marshal(dest) } <ins> // createArrayMergePatch will return an array of merge-patch documents capable // of converting the original document to the modified document for each // pair of JSON documents provided in the arrays. // Arrays of mismatched sizes will result in an error. func createArrayMergePatch(originalJSON, modifiedJSON []byte) ([]byte, error) { originalDocs := []json.RawMessage{} modifiedDocs := []json.RawMessage{} err := json.Unmarshal(originalJSON, &originalDocs) if err != nil { return nil, errBadJSONDoc } err = json.Unmarshal(modifiedJSON, &modifiedDocs) if err != nil { return nil, errBadJSONDoc } total := len(originalDocs) if len(modifiedDocs) != total { return nil, errBadJSONDoc } result := []json.RawMessage{} for i := 0; i < len(originalDocs); i++ { original := originalDocs[i] modified := modifiedDocs[i] patch, err := createObjectMergePatch(original, modified) if err != nil { return nil, err } result = append(result, json.RawMessage(patch)) } return json.Marshal(result) } </ins> // Returns true if the array matches (must be json types). // As is idiomatic for go, an empty array is not the same as a nil array. func matchesArray(a, b []interface{}) bool {", "positive_passages": [{"docid": "doc-en-kubernetes-e51351c05e6844b765acf34eaa6a0653d5a4e3452baed4722f32f9c5caa3ece5", "text": "/kind bug What happened: Wrote a that returned a faulty json patch which specified an our of range index (e.G. when there is only one container). This resulted in the apiserver crashing. Stacktrace: What you expected to happen: No crash /sig-api-machinery\n/sig api-machinery\nThis maybe a bug in . I will follow this question.\nThis bug had been fixed in PR: you can checkout it.\nThanks for your comment but I don't think the linked PR fixed the issue, as it got merged almost a year ago and I am running Kube 1.10.1 which does contain that patch but still panics. Just from quickly looking at the code I the linked PR I believe there are two things wrong: The check if the index is valid only happens when a negative index was given should be\nOnce the PR of is merged I will update kubernetes.\n/kind bug", "commid": "kubernetes_issue_64291", "tokennum": 194}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1177e9826c6c9069e28f549a8ef25809476c85dfc767bd0a36fb48bd3648af96", "query": "} type Zones interface { <del> // List returns the managed Zones, or an error if the list operation failed. </del> <ins> // List returns the (possibly empty) list of managed Zones, or an error if the list operation failed. </ins> List() ([]Zone, error) // Add creates and returns a new managed zone, or an error if the operation failed Add(Zone) (Zone, error)", "positive_passages": [{"docid": "doc-en-kubernetes-2b4d325d4814fe81f2a99615b844cff823940de918e3b360e7f108b94b4fe81b", "text": "/kind bug What happened: walteraa [6:55 AM] Hi, The controller manager of the federation using Google cloud DNS is crashing, the log showed is that: the hyperkube command is that: I have created this in the Google DNS Someone knows why the DNS zone query is getting the 404 error?? :disappointed: What you expected to happen: It should have created the missing domain. How to reproduce it (as minimally and precisely as possible): As per above. Anything else we need to know?: Environment: Kubernetes version (use ): 1.7.4 Cloud provider or hardware configuration**: OpenStack (irrelevant) OS (e.g. from /etc/os-release): irrelevant Kernel (e.g. ): irrelevant Install tools: irrelevant Others: irrelevant\nThe bug is related to this: The above code assumes that the provider code returns no error but an empty list if the domain does not exist, but instead the provider returns a 404. Need to fix the provider and/or the above code.\n/sig federation\nI am unlikely to have time to work on this soon, so if anyone else wants to, go right ahead.\n/assign\nAn additional information: I have created a which is based on the credential JSON file created through instruction. After that, I have configured the Federation controller manager to mount this secret as a volume in the container and set the environment variable to the JSON file inside this volume. Before doing that, I was getting an authentication error so the google DNS provider couldn't be instantiated, and after doing the instructions that I mentioned before, this authentication error was solved but now I'm getting 404 error when Google DNS provider tries access the specified managed zone. The file that I have generated follow this structure:", "commid": "kubernetes_issue_51139", "tokennum": 376}], "negative_passages": []}
{"query_id": "q-en-kubernetes-11a83aa1e5d8f1260a04c38d4fe0063dcfd2ac28dfd855a0edc20be7e938fb82", "query": "\"net/http/httptest\" \"os\" \"reflect\" <ins> \"strconv\" </ins> \"strings\" \"sync\" \"testing\"", "positive_passages": [{"docid": "doc-en-kubernetes-ddb9bacde18c9f97d2ebd4306efde2d358d8075e932023fee86edf729006549a", "text": "Which jobs are failing: Which test(s) are failing: Since when has it been failing: Testgrid link: Reason for failure: Anything else we need to know: /sig api-machinery /assign\n/cc\nwant to take a look at the audit event issue first? I can dig in after that if issues remain.\nyes, I'm looking at the audit event issue now\nactually the failure message suggests that the missing audit log is caused by unexpected admission invocation: I think it's unrelated to auditing Note that there are two tests named \"no reinvocation of webhook B when in-tree or prior webhook mutations\" :( and from the audit log (), it also suggests that the test is hitting a wrong endpoint\nThanks I'll dig in.", "commid": "kubernetes_issue_82693", "tokennum": 163}], "negative_passages": []}
{"query_id": "q-en-kubernetes-11cd9e1833e3221ff458f4a96dea12982572262cbf5339ddc7779ed15160a934", "query": "<del> // +build cgo,linux </del> <ins> // +build linux </ins> /* Copyright 2015 The Kubernetes Authors.", "positive_passages": [{"docid": "doc-en-kubernetes-5266c57682848ccf4bbfd7d438a66f7fa505006f21647746bff2e69ab7956c41", "text": "In cluster/saltbase/salt/kube-proxy/kube-proxy.manifest, we have this: But kube-proxy also has a flag. Is there a reason to use the approach instead of using the flag? cc as you wrote the code, in\n/cc who's working on moving kube-proxy to a DaemonSet\nIn general, oomscoreadj is not expected to be directly updated by pods and kubelet is expected to manage it. If kube-proxy runs in the Guaranteed QoS class, then it's OOM score adj will be set to a low number. Until that happens, kube-proxy process may want to be shielded from OOM kills to an extent (this matters only when kube-proxy's memory usage memory request) Meanwhile, it does not make sense to have two means to configure the same thing. I'll let decide which option he prefers and sunset the other option.\nThanks for clarifying. At this point, I prefer to use the built-in flag instead of relying on composing bash commands. Sent for this.", "commid": "kubernetes_issue_51083", "tokennum": 231}], "negative_passages": []}
{"query_id": "q-en-kubernetes-11eddce6fd2f02cab044be77bfdbb2b592b786dd676f9b4ccaf5b143b7dc4e77", "query": "}, { \"ImportPath\": \"github.com/evanphx/json-patch\", <del> \"Rev\": \"ed7cfbae1fffc071f71e068df27bf4f0521402d8\" </del> <ins> \"Rev\": \"94e38aa1586e8a6c8a75770bddf5ff84c48a106b\" </ins> }, { \"ImportPath\": \"github.com/ghodss/yaml\",", "positive_passages": [{"docid": "doc-en-kubernetes-e51351c05e6844b765acf34eaa6a0653d5a4e3452baed4722f32f9c5caa3ece5", "text": "/kind bug What happened: Wrote a that returned a faulty json patch which specified an our of range index (e.G. when there is only one container). This resulted in the apiserver crashing. Stacktrace: What you expected to happen: No crash /sig-api-machinery\n/sig api-machinery\nThis maybe a bug in . I will follow this question.\nThis bug had been fixed in PR: you can checkout it.\nThanks for your comment but I don't think the linked PR fixed the issue, as it got merged almost a year ago and I am running Kube 1.10.1 which does contain that patch but still panics. Just from quickly looking at the code I the linked PR I believe there are two things wrong: The check if the index is valid only happens when a negative index was given should be\nOnce the PR of is merged I will update kubernetes.\n/kind bug", "commid": "kubernetes_issue_64291", "tokennum": 194}], "negative_passages": []}
{"query_id": "q-en-kubernetes-11ff3993a3e4a332754968c4fc0424287ee890091a3f94641701da10f31b45ea", "query": "if cleanupInfo != nil { // we don't perform the clean up just yet at that could destroy information // needed for the container to start (e.g. Windows credentials stored in <del> // registry keys); instead, we'll clean up after the container successfully // starts or gets removed </del> <ins> // registry keys); instead, we'll clean up when the container gets removed </ins> ds.containerCleanupInfos[containerID] = cleanupInfo } return &runtimeapi.CreateContainerResponse{ContainerId: containerID}, nil } <del> // the creation failed, let's clean up right away </del> <ins> // the creation failed, let's clean up right away - we ignore any errors though, // this is best effort </ins> ds.performPlatformSpecificContainerCleanupAndLogErrors(containerName, cleanupInfo) return nil, createErr", "positive_passages": [{"docid": "doc-en-kubernetes-486ca0159276eedd0d2aa336961ee5fd6fb83d0ac97af7f3f9c8c863d43fcef2", "text": "What would you like to be : Periodically remove cleanupInfos for old containers from dockershim's map. One way of doing that would be to just forget about s older than say an hour, as they should always be short-lived. Why is this needed: introduced a new in-memory map for the dockershim, that could potentially (in pathological cases) cause memory leaks - for containers that use GMSA cred specs, get created successfully, but then never get started nor removed. This might be okay for the alpha release of the GMSA feature, but should be addressed in the beta. See\n/assign wk8\n/sig windows\n/milestone v1.15\ngot moved out. let's move this issue with it as well /milestone v1.16\nHello! I'm bug triage lead for the 1.16 release cycle and considering this issue is tagged for 1.16, but not updated for a long time, I'd like to check its status. The code freeze is starting on August 29th (about 1.5 weeks from now), which means that there should be a PR ready (and merged) until then. Do we still target this issue to be fixed for 1.16?\n: yup we'd love to have this in 1.16, still waiting for kind reviewers on :) ...", "commid": "kubernetes_issue_74843", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-122f3a456d031012e73f8f653f5f4942a6e68ef89472e98845e2953eb1ee494b", "query": "// 1. Add a volume to DSW and wait until it's mounted volumeSpec := &volume.Spec{Volume: &pod.Spec.Volumes[0]} <ins> // copy before reconciler runs to avoid data race. volumeSpecCopy := &volume.Spec{Volume: &pod.Spec.Volumes[0]} </ins> podName := util.GetUniquePodName(pod) generatedVolumeName, err := dsw.AddPodToVolume( podName, pod, volumeSpec, volumeSpec.Name(), \"\" /* volumeGidValue */)", "positive_passages": [{"docid": "doc-en-kubernetes-d047193f0eb4348dad25266c8f06cc7d0100df3011e6281006c74e70d78d442e", "text": "<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI --pull-kubernetes-unit : (PR with no go code changes, should not have failed any unit tests) links to appreciated links to specific failures in spyglass appreciated <!-- Please see the deflaking doc () for more guidance! --/sig storage\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assigne\n/assign\n/assign tried to fix it in", "commid": "kubernetes_issue_99815", "tokennum": 196}], "negative_passages": []}
{"query_id": "q-en-kubernetes-122f7e43074f9549496e5cadcd5a57fdff10b887a6fe1d9fd73966fd11f33bce", "query": "func (f *Framework) BeforeEach() { f.beforeEachStarted = true <del> // The fact that we need this feels like a bug in ginkgo. // https://github.com/onsi/ginkgo/v2/issues/222 f.cleanupHandle = AddCleanupAction(f.AfterEach) </del> if f.ClientSet == nil { ginkgo.By(\"Creating a kubernetes client\") config, err := LoadConfig()", "positive_passages": [{"docid": "doc-en-kubernetes-2e8b5198754cc6270240a247dfa503fa4a3eeae2d5481e425503db2c2c68474d", "text": "Here is a list of TODOs that could be fixed for Ginkgo migration from v1 to v2. [x] Lost the validation on the SIGDescribe: [x] Ginkgo V2 currently cannot get the number of specs that will run in , this might be fixed in the Ginkgo's minor release of V2 in the future. [x] <delGinkgo dry-run mode has dropped the test spec in V2 (), consider to switch back to use to generate test spec when the feature is ready in . </del--- This has been fixed in Ginkgo 2.1.4 [x] <delMigrate all the custom reporter in , should be lightweight and not sure where those custom reporters are used. </delFixed here: [x] Replace all the camel case flags to kebab case flags, e.g. to . [x] <delRemove the legacy e2e test binary's parameter and in 1.28, those parameters were used to manage report, this is no longer needed for Ginkgo v2. </delno longer needed. [x] upgrade vendor when is migrated to ginkgo v2, this will help to remove the dependency of - [x] <delrevisit to explore the possibility to cover the test in Ginkgo V2. </delfixed by [x] remove the workaround introduced in Ginkgo V1 ( is not called after hitting ^c): partially addressed by: , some cleanup needed for each sig before removing the hook entirely. I think has the pr to fix this entirely, but I cannot get the link for that, mark it as resolved. : [x] New work item (?): capture only a single output text output stream () in JUnit (this issue was resolved along with another one in ) [ ] Due to the junit format change, some tool which use to grab \"value\" directly cannot get the failure reason as what it does in v1. [x] Test failures are missing information since GinkgoV2 migration [ ] is clustering stack traces, not failure text () Address those leftovers if there is any update from Ginkgo in the future. see the relevant link on the each of the issues.", "commid": "kubernetes_issue_109744", "tokennum": 483}], "negative_passages": []}
{"query_id": "q-en-kubernetes-122f7e43074f9549496e5cadcd5a57fdff10b887a6fe1d9fd73966fd11f33bce", "query": "func (f *Framework) BeforeEach() { f.beforeEachStarted = true <del> // The fact that we need this feels like a bug in ginkgo. // https://github.com/onsi/ginkgo/v2/issues/222 f.cleanupHandle = AddCleanupAction(f.AfterEach) </del> if f.ClientSet == nil { ginkgo.By(\"Creating a kubernetes client\") config, err := LoadConfig()", "positive_passages": [{"docid": "doc-en-kubernetes-c4753cc2146447a07d108ff02ffe6d67b2be2a6ba7adffaf5026d0a94c1c787a", "text": "No response_ <details</details<detailsall </details<details</details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig testing\n/cc\n/cc\nhello! I would like to work on this issues\nI think we cannot do anything now except the last two, and those two should be based on top of the:\nI would like to work on task 5 of this issue\nno problem, pls wait for an while until that PR got merged, then you can create a pr to fix those deprecated parameters.\nRegarding : searching for points out the places where the workaround is used and needs to be replaced once is solved.\nI just noticed this comment in\nseems like is not used in k/k, but in other sigs.\nhmm... I just grepped the test code, will push a pr to fix this.\n/open\n/re-open\nokay, this is not resolved actually, but I have no way to re-open it.\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n~ it seems that some more jobs needs to be adapted to not use parallel~ [repo][0]=kubernetes/test-infra~ ~ACTION REQUIRED: Ginkgo V2 doesn't accept go test's flags to parallelize Ginkgo specs, please switch to use or instead.~ Sorry for the noise, the flag is passed to kubetest, and it correctly translate it to , it is not the issue here\nnp, thanks for the update!\nNew work item (?): capture only a single output text output stream () in JUnit.\nupdated the issue, haven't got a chance to take a close look at the item though.\nThis should be resolved by \"open stdout\" now should only appear if a test intentionally records SpecReports.\nmark it as resolved.\nis this complete now?", "commid": "kubernetes_issue_109744", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-122f7e43074f9549496e5cadcd5a57fdff10b887a6fe1d9fd73966fd11f33bce", "query": "func (f *Framework) BeforeEach() { f.beforeEachStarted = true <del> // The fact that we need this feels like a bug in ginkgo. // https://github.com/onsi/ginkgo/v2/issues/222 f.cleanupHandle = AddCleanupAction(f.AfterEach) </del> if f.ClientSet == nil { ginkgo.By(\"Creating a kubernetes client\") config, err := LoadConfig()", "positive_passages": [{"docid": "doc-en-kubernetes-138d08f1aeca8e81cbf8aa639b51baa29b1653208e0d897ccfc4810c9421dc3e", "text": ", Only two of them left, I need to follow this one, here is the issue for this one opened in the Ginkgo: I think this should be fixed in the third party tools instead of Kubernetes, if we agree with that, we can mark it as completed as well. For the first one, I will continue to follow until there is a update from Ginkgo's side, for the later one, there is no consensus yet IIUC, we can open a separate issue for that, I am gonna to close this one since there is no much thing we can do now. /close\nWe agreed to fix the tool, but had no issue open for it. I just created one:\nAnother issue for", "commid": "kubernetes_issue_109744", "tokennum": 149}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1298e6eba39cee5750bb216fb06030dca2ab935a6e66bcf00a767193d85f5231", "query": "for n, pods := range nodeToDaemonPods { if !isNodeRunning[n] { for _, pod := range pods { <del> results = append(results, pod.Name) </del> <ins> if len(pod.Spec.NodeName) == 0 { results = append(results, pod.Name) } </ins> } } }", "positive_passages": [{"docid": "doc-en-kubernetes-2bd3e1d9e94a5358a6c2d5b4c6b5864c879bb8cabae55e6531ce8f2da7e1ce93", "text": "What happened: Occasionally we get a Daemonset stuck with less Current replicas than Desired, causing a Daemonset sync tends to fix it, e.g (add a new node). This happens to all our Daemonsets. I'm using fluentd as an example. There are no Daemonsets pods in pending nor are there any errors when describing the Daemonset What you expected to happen: The Daemonset Pod to be scheduled How to reproduce it (as minimally and precisely as possible): Reproducing this state is very tricky, I've had the most success by terminating nodes in our ASG causing a new one to come up. However I think I've identified why this is happening. The issue appears to be related to daemonset Pod deletion, a Pod gets deleted causing to trigger, this lowers the expectations by as expected. The delete pod event then triggers a sync of the daemonset, in which it finds which involves fetching pods from the informer cache This is somehow returning the deleted pod. You can see in the logs here thinks that it needs to delete the pod that was deleted. It is also setting the expectation back to after the delete pod event previously lowered it by 1. At this point you're stuck as the function can't get past this line As the expectation can not be satisfied as syncNodes set it back to and there's nothing it to get it back to . So I believe this is what's causing us to get less replicas than expected, the function is stuck due to the expectation so it can't perform a full sync to schedule the new pods. There's also not much to trigger a new sync once the expectation has expired until a new node comes up or one goes down. Environment: Kubernetes version (use ):Cloud provider or hardware configuration: AWS OS (e.g: ):Kernel (e.g. ):\n/sig apps\nI investigated this as much as I could without getting some external input, it feels like it's some kind of race condition in the informer cache. If anyone has ideas of if places to dig deeper that would be handy.\nReiterating the mentions to trigger a notification: <detailsIn response to : I investigated this as much as I could without getting some external input, it feels like it's some kind of race condition in the informer cache. If anyone has ideas of if places to dig deeper that would be handy.", "commid": "kubernetes_issue_75836", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1298e6eba39cee5750bb216fb06030dca2ab935a6e66bcf00a767193d85f5231", "query": "for n, pods := range nodeToDaemonPods { if !isNodeRunning[n] { for _, pod := range pods { <del> results = append(results, pod.Name) </del> <ins> if len(pod.Spec.NodeName) == 0 { results = append(results, pod.Name) } </ins> } } }", "positive_passages": [{"docid": "doc-en-kubernetes-cf3a9a922f150fcd06b37026fcb1a4fe5fd4fd3de4493928a0abbcee85e2e3a6", "text": "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\nThis problem is definitely related to node termination, it's trying to delete the already deleted pod from the node that's been terminated. The problem seems to go away if is set, I think although this kind of race condition may have always been possible, it's being frequently caused via Which is finding the non-existent pod in the pod cache and seeing that it is assigned to a non-running node, resulting in a request to delete the non-existent pod. cc\nReiterating the mentions to trigger a notification: <detailsIn response to : This problem is definitely related to node termination, it's trying to delete the already deleted pod from the node that's been terminated. 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\n/assign could you please take a look at this? It seems that it is related to the code you in .\nThanks for reporting the bug. Bug was introduced in which deleting pods without nodes. There is race condition between removing pod from cache and listing pods for DaemonSet. Bug occurs during following scenario: is deleted. for node is deleted by PodGCController. handler is executed by informer () set is to queue by delete handler () is processed and pods are taken from cache before deleted pod is removed. for deleted pod is not found so we add deleted pod to podsToDelete list (). are set to del:1() succeeds as pod is not found(). are never met so we need to wait till expectations expire. As fix I will send a change to so only pods that can't be deleted by PodGCController are deleted by DaemonSet controller.", "commid": "kubernetes_issue_75836", "tokennum": 399}], "negative_passages": []}
{"query_id": "q-en-kubernetes-12b950a98e4e777957e7251e5866d0712d89a02691520b19b4d3f443a74e3f43", "query": "<ins> // +build linux /* Copyright 2021 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package e2enode import ( \"time\" \"golang.org/x/sys/unix\" \"github.com/onsi/ginkgo\" \"github.com/onsi/gomega\" \"k8s.io/kubernetes/test/e2e/framework\" ) const contentionLockFile = \"/var/run/kubelet.lock\" var _ = SIGDescribe(\"Lock contention [Slow] [Disruptive] [NodeFeature:LockContention]\", func() { ginkgo.It(\"Kubelet should stop when the test acquires the lock on lock file and restart once the lock is released\", func() { ginkgo.By(\"perform kubelet health check to check if kubelet is healthy and running.\") // Precautionary check that kubelet is healthy before running the test. gomega.Expect(kubeletHealthCheck(kubeletHealthCheckURL)).To(gomega.BeTrue()) ginkgo.By(\"acquiring the lock on lock file i.e /var/run/kubelet.lock\") // Open the file with the intention to acquire the lock, this would imitate the behaviour // of the another kubelet(self-hosted) trying to start. When this lock contention happens // it is expected that the running kubelet must terminate and wait until the lock on the // lock file is released. // Kubelet uses the same approach to acquire the lock on lock file as shown here: // https://github.com/kubernetes/kubernetes/blob/master/cmd/kubelet/app/server.go#L530-#L546 // and the function definition of Acquire is here: // https://github.com/kubernetes/kubernetes/blob/master/pkg/util/flock/flock_unix.go#L25 fd, err := unix.Open(contentionLockFile, unix.O_CREAT|unix.O_RDWR|unix.O_CLOEXEC, 0600) framework.ExpectNoError(err) // Defer the lock release in case test fails and we don't reach the step of the release // lock. This ensures that we release the lock for sure. defer func() { err = unix.Flock(fd, unix.LOCK_UN) framework.ExpectNoError(err) }() // Acquire lock. err = unix.Flock(fd, unix.LOCK_EX) framework.ExpectNoError(err) ginkgo.By(\"verifying the kubelet is not healthy as there was a lock contention.\") // Once the lock is acquired, check if the kubelet is in healthy state or not. // It should not be. gomega.Eventually(func() bool { return kubeletHealthCheck(kubeletHealthCheckURL) }, 10*time.Second, time.Second).Should(gomega.BeFalse()) ginkgo.By(\"releasing the lock on lock file i.e /var/run/kubelet.lock\") // Release the lock. err = unix.Flock(fd, unix.LOCK_UN) framework.ExpectNoError(err) ginkgo.By(\"verifying the kubelet is healthy again after the lock was released.\") // Releasing the lock triggers kubelet to re-acquire the lock and restart. // Hence the kubelet should report healthy state. gomega.Eventually(func() bool { return kubeletHealthCheck(kubeletHealthCheckURL) }, 10*time.Second, time.Second).Should(gomega.BeTrue()) }) }) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-45f48f64f34b41c2ff28ff0a971f436119bbad623219cbe5456b39a5b105f849", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Node E2E tests for Kubelet lock contention flags: --exit-on-lock-contention --lock-file Why is this needed: These flags are being graduated to KubeletConfiguration on , we should add E2E tests for these flags before proceeding.\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig node /wg component-standard\nIssues 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\nStale 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\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /close\nClosing 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", "commid": "kubernetes_issue_96766", "tokennum": 406}], "negative_passages": []}
{"query_id": "q-en-kubernetes-12d6b3a159aea8eee5a9683154182fec6523a0a9f7eb98bda08221c6a26c638a", "query": "\"//staging/src/k8s.io/apimachinery/pkg/runtime/schema:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/util/diff:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/util/sets:go_default_library\", <ins> \"//staging/src/k8s.io/apimachinery/pkg/watch:go_default_library\", </ins> \"//staging/src/k8s.io/client-go/dynamic:go_default_library\", \"//test/integration/framework:go_default_library\", \"//vendor/github.com/coreos/etcd/clientv3:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-7ee140198c665b218e0dfb7e3cd2f2624912887cfcfab5f30828d12c6130aa35", "text": "What happened: Set up a HA cluster with 1.9 and 1.10 API servers (occurs on any apiserver skew boundary where a cohabitating resource's storage version changed groups) Observed errors when modifying workload objects: when modified via the 1.10 server, saw this error in the 1.9 server: when modified via the 1.9 server, saw this error in the 1.10 server: When this error was encountered, all watchers for the resource in question would be dropped and have to re-establish, and the internal watchers feeding the watch cache would drop and re-establish What you expected to happen: Watch events from all supported storage versions are processed correctly How to reproduce it (as minimally and precisely as possible): Start a server from master (for inspectability, store in json). With Create a deployment (e.g. kube-dns in kube-system) Establish a watch via extensions (kubectl get deployments.extensions --all-namespaces -w) Establish a watch via apps (kubectl get --all-namespaces -w) Tail the kube-apiserver log Change the apps/v1 deployment in etcd to extensions/v1beta1: Observer client watches drop and server log errors: Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: /sig api-machinery /cc /priority critical-urgent\nerror is triggered by this returning false: constructed here: the info about expected cohabitating groups is not included in the list of acceptable inputs", "commid": "kubernetes_issue_73478", "tokennum": 368}], "negative_passages": []}
{"query_id": "q-en-kubernetes-13262b63f105cecc57709e4f388363bf13ef887663e116026e6ba258ba4d6c48", "query": "if err != nil { t.Fatal(err) } ss1Rev1.Namespace = ss1.Namespace ss1Rev2, err := NewControllerRevision(ss1, parentKind, ss1.Spec.Template.Labels, rawTemplate(&ss1.Spec.Template), 2, ss1.Status.CollisionCount) if err != nil { t.Fatal(err) } ss1Rev2.Namespace = ss1.Namespace ss1Rev3, err := NewControllerRevision(ss1, parentKind, ss1.Spec.Template.Labels, rawTemplate(&ss1.Spec.Template), 3, ss1.Status.CollisionCount) if err != nil { t.Fatal(err) } <del> ss1Rev3.Namespace = ss1.Namespace </del> <ins> ss1Rev3Time2, err := NewControllerRevision(ss1, parentKind, ss1.Spec.Template.Labels, rawTemplate(&ss1.Spec.Template), 3, ss1.Status.CollisionCount) if err != nil { t.Fatal(err) } ss1Rev3Time2.Namespace = ss1.Namespace ss1Rev3Time2.CreationTimestamp = metav1.Time{Time: ss1Rev3.CreationTimestamp.Add(time.Second)} ss1Rev3Time2Name2, err := NewControllerRevision(ss1, parentKind, ss1.Spec.Template.Labels, rawTemplate(&ss1.Spec.Template), 3, ss1.Status.CollisionCount) if err != nil { t.Fatal(err) } ss1Rev3Time2Name2.Namespace = ss1.Namespace ss1Rev3Time2Name2.CreationTimestamp = metav1.Time{Time: ss1Rev3.CreationTimestamp.Add(time.Second)} </ins> tests := []testcase{ {", "positive_passages": [{"docid": "doc-en-kubernetes-4d5dc3f2fd1aa2418695125e98dd263b9bbd4b25db7ea8b25723d335bfe8c79b", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Statefulsets are sometimes continually rolling pods and I don't know why statefulset created: storageclass referenced: kubectl describe statefulset statefulset-test: As you can see from the above describe, the pod in the statefulset has been restarted a lot of times. Observing the created pod, 1) The pod comes up ready 2) immediately transitions to terminating 3) Is terminated 4) A new pod is created 5) Go back to (1) (repeats forever) Despite no updates to the statefulset spec ocurring. Making a change to the statefulset template (for example a trivial change adding a nonsense annotation) stops the rolling and fixes the issue When this statefulset was created, there was a mutating webhook enabled. After the observed pod rolling. I disabled this by making its configuration invalid and making it non required, and the rolling persisted. The status of the statefulset: : You can see that there is a discrepency between currentRevision and updateRevision. currentRevision: statefulset-test- updateRevision: statefulset-test- A short while later the status is changed to contain currentRevision: statefulset-test- updateRevision: statefulset-test- This change happened at Sun Apr 1 19:48:48 2018 Presumably after the rollout of statefulset-test- is complete.", "commid": "kubernetes_issue_61998", "tokennum": 342}], "negative_passages": []}
{"query_id": "q-en-kubernetes-13262b63f105cecc57709e4f388363bf13ef887663e116026e6ba258ba4d6c48", "query": "if err != nil { t.Fatal(err) } ss1Rev1.Namespace = ss1.Namespace ss1Rev2, err := NewControllerRevision(ss1, parentKind, ss1.Spec.Template.Labels, rawTemplate(&ss1.Spec.Template), 2, ss1.Status.CollisionCount) if err != nil { t.Fatal(err) } ss1Rev2.Namespace = ss1.Namespace ss1Rev3, err := NewControllerRevision(ss1, parentKind, ss1.Spec.Template.Labels, rawTemplate(&ss1.Spec.Template), 3, ss1.Status.CollisionCount) if err != nil { t.Fatal(err) } <del> ss1Rev3.Namespace = ss1.Namespace </del> <ins> ss1Rev3Time2, err := NewControllerRevision(ss1, parentKind, ss1.Spec.Template.Labels, rawTemplate(&ss1.Spec.Template), 3, ss1.Status.CollisionCount) if err != nil { t.Fatal(err) } ss1Rev3Time2.Namespace = ss1.Namespace ss1Rev3Time2.CreationTimestamp = metav1.Time{Time: ss1Rev3.CreationTimestamp.Add(time.Second)} ss1Rev3Time2Name2, err := NewControllerRevision(ss1, parentKind, ss1.Spec.Template.Labels, rawTemplate(&ss1.Spec.Template), 3, ss1.Status.CollisionCount) if err != nil { t.Fatal(err) } ss1Rev3Time2Name2.Namespace = ss1.Namespace ss1Rev3Time2Name2.CreationTimestamp = metav1.Time{Time: ss1Rev3.CreationTimestamp.Add(time.Second)} </ins> tests := []testcase{ {", "positive_passages": [{"docid": "doc-en-kubernetes-25284c3702a45280c2a40fae68a3ba4d1c026c9e5d96ab43c2dee09fe3985aa0", "text": "Here are all the controllerrevisions from above: kubectl get controllerrevision statefulset-test- -o yaml kubectl get controllerrevision statefulset-test- -o yaml: kubectl get controllerrevision statefulset-test- -o yaml: The differences between the above controllerrevisions are insignificant (the hash, the creation timestamp, the name, the resource version, the uid, the self link) Interestingly all these controllerrevisions were created very close together in time shortly after I created the statefulset The current controllerrevisions are After watching the state change for a while, it actually seems like the statefulset is just cycling through the updateRevision being one of the above 10 controllerrevisions Leaders during this time From kube-controller-manager logs during this time, here is one excerpt: The error sync in there is suspicous, and as you can see the controllerrevisions are changing in the logs I have the full logs from a 5 minute window on either side of the above if necessary. The reason I'm inclined to think this is a kubernetes bug is that any update to the statefulset template fixes the problem. How to reproduce it (as minimally and precisely as possible): Not really sure. Worth just trying to create the above statefulset (requires creating the I tried deleting and recreating the above statefulset and it didn't happen, so something flaky is going on Anything else we need to know?: kubernetes 1.9.3 (client and server) cloud provider: aws\n/sig apps\nI realize this will probably need some further debugging, happy to get some direction\nConsistent repro: Create a statefulset that creates a controllerrevision whose hash is between max int32 and max uint32 (this shouldn't be that hard to do, possibly a 50/50 chance of this). Manually create a controllerrevision identical to the first (same revision), incrementing both the name and hash by one. See that the statefulset controller will continually switch which controller revision should be the target of the statefulset.\nDue to the issue fixed here: , under some circumstances controllerrevisions whose revision is the same were being considered equal.", "commid": "kubernetes_issue_61998", "tokennum": 496}], "negative_passages": []}
{"query_id": "q-en-kubernetes-13262b63f105cecc57709e4f388363bf13ef887663e116026e6ba258ba4d6c48", "query": "if err != nil { t.Fatal(err) } ss1Rev1.Namespace = ss1.Namespace ss1Rev2, err := NewControllerRevision(ss1, parentKind, ss1.Spec.Template.Labels, rawTemplate(&ss1.Spec.Template), 2, ss1.Status.CollisionCount) if err != nil { t.Fatal(err) } ss1Rev2.Namespace = ss1.Namespace ss1Rev3, err := NewControllerRevision(ss1, parentKind, ss1.Spec.Template.Labels, rawTemplate(&ss1.Spec.Template), 3, ss1.Status.CollisionCount) if err != nil { t.Fatal(err) } <del> ss1Rev3.Namespace = ss1.Namespace </del> <ins> ss1Rev3Time2, err := NewControllerRevision(ss1, parentKind, ss1.Spec.Template.Labels, rawTemplate(&ss1.Spec.Template), 3, ss1.Status.CollisionCount) if err != nil { t.Fatal(err) } ss1Rev3Time2.Namespace = ss1.Namespace ss1Rev3Time2.CreationTimestamp = metav1.Time{Time: ss1Rev3.CreationTimestamp.Add(time.Second)} ss1Rev3Time2Name2, err := NewControllerRevision(ss1, parentKind, ss1.Spec.Template.Labels, rawTemplate(&ss1.Spec.Template), 3, ss1.Status.CollisionCount) if err != nil { t.Fatal(err) } ss1Rev3Time2Name2.Namespace = ss1.Namespace ss1Rev3Time2Name2.CreationTimestamp = metav1.Time{Time: ss1Rev3.CreationTimestamp.Add(time.Second)} </ins> tests := []testcase{ {", "positive_passages": [{"docid": "doc-en-kubernetes-59ace9008f72ca5d82f22a23445c41e6f5a4a98690d88922022af0dc9f3faebe", "text": "This ends up causing this bug to manifest as follows: ListRevisions finds many controllerrevisions with the same revision (unclear how this state happens, but it can happen) The sort here randomly sorts them Due to the linked bug , FindEqualRevisions incorrectly finds that all these controller revisions are equal to the proposed udpate. The updateRevision selects the last revision found here Therefore, updateRevision, is randomly selected and causes the bug. This fixes the immediate issue, but the sort should probably be made stable (i.e not just look at the revision number, perhaps just consider the hash for tie breakers)\nAs an update, fixing the equality check will not be sufficient because it is possible for multiple controller revisions to be created that are actually equal, including the same hash, that have the same revision number. I believe the fix will need to be equal controllerrevisions with the same revision number from being created sort the controllerrevisions so that the controllerrevision that is the target of the statefulset is stable\nIssues 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\n/remove-lifecycle stale\nping I use the K8S which version is 1.11.4 and encounter the same problem. I want to reproduce the problem and find your way: Manually create a controllerrevision identical to the first (same revision), incrementing both the name and hash by one. Could you tell me how to mannually create a same controllerrevision identical to the first? Thanks in anvance.", "commid": "kubernetes_issue_61998", "tokennum": 374}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1340f62342e0311a88dd481dd63ad49a82761b8b3b77022c3fa4db1c26897fff", "query": "} framework.ExpectEqual(successes, largeCompletions, \"expected %d successful job pods, but got  %d\", largeCompletions, successes) }) <ins> ginkgo.It(\"should apply changes to a job status\", func() { ns := f.Namespace.Name jClient := f.ClientSet.BatchV1().Jobs(ns) ginkgo.By(\"Creating a job\") job := e2ejob.NewTestJob(\"notTerminate\", \"suspend-false-to-true\", v1.RestartPolicyNever, parallelism, completions, nil, backoffLimit) job, err := e2ejob.CreateJob(f.ClientSet, f.Namespace.Name, job) framework.ExpectNoError(err, \"failed to create job in namespace: %s\", f.Namespace.Name) ginkgo.By(\"Ensure pods equal to paralellism count is attached to the job\") err = e2ejob.WaitForAllJobPodsRunning(f.ClientSet, f.Namespace.Name, job.Name, parallelism) framework.ExpectNoError(err, \"failed to ensure number of pods associated with job %s is equal to parallelism count in namespace: %s\", job.Name, f.Namespace.Name) // /status subresource operations ginkgo.By(\"patching /status\") // we need to use RFC3339 version since conversion over the wire cuts nanoseconds now1 := metav1.Now().Rfc3339Copy() jStatus := batchv1.JobStatus{ StartTime: &now1, } jStatusJSON, err := json.Marshal(jStatus) framework.ExpectNoError(err) patchedStatus, err := jClient.Patch(context.TODO(), job.Name, types.MergePatchType, []byte(`{\"metadata\":{\"annotations\":{\"patchedstatus\":\"true\"}},\"status\":`+string(jStatusJSON)+`}`), metav1.PatchOptions{}, \"status\") framework.ExpectNoError(err) framework.ExpectEqual(patchedStatus.Status.StartTime.Equal(&now1), true, \"patched object should have the applied StartTime status\") framework.ExpectEqual(patchedStatus.Annotations[\"patchedstatus\"], \"true\", \"patched object should have the applied annotation\") ginkgo.By(\"updating /status\") // we need to use RFC3339 version since conversion over the wire cuts nanoseconds now2 := metav1.Now().Rfc3339Copy() var statusToUpdate, updatedStatus *batchv1.Job err = retry.RetryOnConflict(retry.DefaultRetry, func() error { statusToUpdate, err = jClient.Get(context.TODO(), job.Name, metav1.GetOptions{}) if err != nil { return err } statusToUpdate.Status.StartTime = &now2 updatedStatus, err = jClient.UpdateStatus(context.TODO(), statusToUpdate, metav1.UpdateOptions{}) return err }) framework.ExpectNoError(err) framework.ExpectEqual(updatedStatus.Status.StartTime.Equal(&now2), true, fmt.Sprintf(\"updated object status expected to have updated StartTime %#v, got %#v\", statusToUpdate.Status.StartTime, updatedStatus.Status.StartTime)) ginkgo.By(\"get /status\") jResource := schema.GroupVersionResource{Group: \"batch\", Version: \"v1\", Resource: \"jobs\"} gottenStatus, err := f.DynamicClient.Resource(jResource).Namespace(ns).Get(context.TODO(), job.Name, metav1.GetOptions{}, \"status\") framework.ExpectNoError(err) statusUID, _, err := unstructured.NestedFieldCopy(gottenStatus.Object, \"metadata\", \"uid\") framework.ExpectNoError(err) framework.ExpectEqual(string(job.UID), statusUID, fmt.Sprintf(\"job.UID: %v expected to match statusUID: %v \", job.UID, statusUID)) }) </ins> }) // waitForJobFailure uses c to wait for up to timeout for the Job named jobName in namespace ns to fail.", "positive_passages": [{"docid": "doc-en-kubernetes-9deab690131da58e4566d26be974a26500a50c4525ef4b542cd9399a25bc940c", "text": "[x] Test PR : [x] Two weeks soak end date : 6 April 2022 [X] Test promotion PR : According to this APIsnoop query, there are still some remaining Job status endpoints which are untested. There are conformance tests for CronJob status endpoints already the existing as a template, a new for job test has been created. The e2e logs for this test are listed below. This query shows the endpoints hit within a short period of running the e2e test If a test with these calls gets merged, test coverage will go up by 3 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance\n/triage accepted\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_108113", "tokennum": 205}], "negative_passages": []}
{"query_id": "q-en-kubernetes-13985989fa01b84b01950a7af482c10d3dac2d6fd981d7263434ac78b0ce5f58", "query": "publicIP := \"\" if ipConfig.PublicIPAddress != nil && ipConfig.PublicIPAddress.ID != nil { pipID := *ipConfig.PublicIPAddress.ID <del> pipName, err := getLastSegment(pipID) if err != nil { return \"\", \"\", fmt.Errorf(\"failed to get publicIP name for node %q with pipID %q\", nodeName, pipID) </del> <ins> matches := vmssPIPConfigurationRE.FindStringSubmatch(pipID) if len(matches) == 7 { resourceGroupName := matches[1] virtualMachineScaleSetName := matches[2] virtualmachineIndex := matches[3] networkInterfaceName := matches[4] IPConfigurationName := matches[5] publicIPAddressName := matches[6] pip, existsPip, err := ss.getVMSSPublicIPAddress(resourceGroupName, virtualMachineScaleSetName, virtualmachineIndex, networkInterfaceName, IPConfigurationName, publicIPAddressName) if err != nil { klog.Errorf(\"ss.getVMSSPublicIPAddress() failed with error: %v\", err) return \"\", \"\", err } if existsPip && pip.IPAddress != nil { publicIP = *pip.IPAddress } } else { klog.Warningf(\"Failed to get VMSS Public IP with ID %s\", pipID) </ins> } <ins> } </ins> <del> resourceGroup, err := ss.GetNodeResourceGroup(nodeName) if err != nil { return \"\", \"\", err } </del> <ins> return internalIP, publicIP, nil } </ins> <del> pip, existsPip, err := ss.getPublicIPAddress(resourceGroup, pipName) if err != nil { return \"\", \"\", err } if existsPip { publicIP = *pip.IPAddress } </del> <ins> func (ss *scaleSet) getVMSSPublicIPAddress(resourceGroupName string, virtualMachineScaleSetName string, virtualmachineIndex string, networkInterfaceName string, IPConfigurationName string, publicIPAddressName string) (pip network.PublicIPAddress, exists bool, err error) { var realErr error var message string ctx, cancel := getContextWithCancel() defer cancel() pip, err = ss.PublicIPAddressesClient.GetVirtualMachineScaleSetPublicIPAddress(ctx, resourceGroupName, virtualMachineScaleSetName, virtualmachineIndex, networkInterfaceName, IPConfigurationName, publicIPAddressName, \"\") exists, message, realErr = checkResourceExistsFromError(err) if realErr != nil { return pip, false, realErr </ins> } <del> return internalIP, publicIP, nil </del> <ins> if !exists { klog.V(2).Infof(\"Public IP %q not found with message: %q\", publicIPAddressName, message) return pip, false, nil } return pip, exists, err </ins> } // returns a list of private ips assigned to node", "positive_passages": [{"docid": "doc-en-kubernetes-c62a800befd6b705c74ea2036c66907711f830c03e53ca86df0e2014d6541d16", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Node external IP of azure VMSS cannot be obtained when cloud-controller-manager is enabled. Corresponding logs are shown as follows:\n/sig azure\n/milestone v1.16", "commid": "kubernetes_issue_80014", "tokennum": 92}], "negative_passages": []}
{"query_id": "q-en-kubernetes-13a8369d752d7971f28e19cabf90e848d340a7d88ea3e5354decc1888631ab30", "query": "return g.service } <ins> type rateLimitedRoundTripper struct { rt      http.RoundTripper limiter flowcontrol.RateLimiter } func (rl *rateLimitedRoundTripper) RoundTrip(req *http.Request) (*http.Response, error) { rl.limiter.Accept() return rl.rt.RoundTrip(req) } </ins> func getProjectAndZone() (string, string, error) { result, err := metadata.Get(\"instance/zone\") if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-599cbd9914ac52a34ee08ac617d1f4bd774f52f2d5bdcb07fa1a0e76f7194545", "text": "On a large cluster, the routecontroller basically makes O(n) requests all at once, and most of them error out with \"Rate Limit Exceeded\". We then wait for operations to complete on the ones that did stick, and damn the rest, they'll be caught next reconcile (which is a while). In fact, in some cases it appears we're spamming hard enough to get rate limited by the upper-level API DOS protections and seeing something akin to , e.g.: We can do better than this!\nc.f. , which is the other leg of this problem\nI took a look into code and it seems that we are doing full reconciliation every 10s. If we need to create 2000 routes at the beginning it seems to frequently. I think that we need to: first compute how many routes we have to create based on that try to spread them over some time to reduce possibility of causing 'rate limit exceeded' I will try to put some small PR together as a starting point.\nI'm reopening this one, since this doesn't seem to be solved. So basically something strange is happening here. With PR we have 10/s limit on API calls send to GCE. And we are still rate-limitted. However, according to documentation we are allowed for 20/s: So something either doesn't work or is weird.\nWhat is super interesting from the logs of recent run: It starts to creating routes: After 2 minutes from that, we are hitting \"Rate limit Exceeded\" for the first time: And only after 9 minutes we create the first route ever. The second one is created after 15 minutes, and from that point we create a number of them So it seems that nothing useful is happening for the first 2 minutes, and then between 3m30 and 9m30\nOK - so I think that what is happening is that all controllers are sharing GCE interface (and thuse they have common throttling). So if one controller is generating a lot of API calls, then other controllers may be throttled. has a hypothesis that it may be caused by nodecontroller.\nOne thing my PR didn't address (because it was late): Now we have some obnoxious differences in logging when you go to make a request, because the versus could actually be absorbing a fair amount of ratelimiter.", "commid": "kubernetes_issue_26119", "tokennum": 488}], "negative_passages": []}
{"query_id": "q-en-kubernetes-13a8369d752d7971f28e19cabf90e848d340a7d88ea3e5354decc1888631ab30", "query": "return g.service } <ins> type rateLimitedRoundTripper struct { rt      http.RoundTripper limiter flowcontrol.RateLimiter } func (rl *rateLimitedRoundTripper) RoundTrip(req *http.Request) (*http.Response, error) { rl.limiter.Accept() return rl.rt.RoundTrip(req) } </ins> func getProjectAndZone() (string, string, error) { result, err := metadata.Get(\"instance/zone\") if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-bf24c8733a67a958496376416be2eb636c6e4bfb94999815173220461c93fd0c", "text": "It could before because of the operation rate limiter and operation polling anyways, but now could be worse.\n- yes I'm aware of that. And probably this is exactly the case here.\nI got fooled by that - I guess we should fix it somehow.\nOne approach to fixing it is a similar approach to the operation polling code, but in the : warn if we ratelimited for more than N seconds (and dump the request or something? not clear how to clarify what we were sending).\nI found something else - Kubelet is also building GCE interface: We have 2000 kubelets, so if all of them send multiple requests to GCE, we may hit limits.\nAny idea in what circumstances Kubelet will contact cloud provider?\nHmm - it seems it contacts GCE exactly once at the beginning. So it doesn't explain much.\nI think it's only here: I've rarely seen GCE ratelimit readonly calls, in practice, and kubelets come up pretty well staggered.\nOK - so with logs that I , it is pretty clear that we are very heavily throttled on GCE api calls. In particular, when I was running 1000-node cluster, I see lines where we were throttle for 1m30. I'm pretty sure it's significantly higher in 2000-node cluster. I'm going to investigate a bit more where all those reuqests come from.\nActually - it seems that we have a pretty big problem here. Basically, Kubelet seems to send a lot of requests to GCE. So to clarify: every time Kubelet is updating NodeStatus (so every 10s by default) it is sending an API call to GCE to get it's not addresses: that means, that if we have 2000 nodes, kubelets generate 200 QPS to GCE (which is significantly more than we can afford) We should think how to solve this issue, but I think the options are: increasing QPS quota or calling GCE only once per X statusUpdates.\nThe second issue is that we are throttled at the controller level too, and this one I'm tryin to understand right now.", "commid": "kubernetes_issue_26119", "tokennum": 457}], "negative_passages": []}
{"query_id": "q-en-kubernetes-13a8369d752d7971f28e19cabf90e848d340a7d88ea3e5354decc1888631ab30", "query": "return g.service } <ins> type rateLimitedRoundTripper struct { rt      http.RoundTripper limiter flowcontrol.RateLimiter } func (rl *rateLimitedRoundTripper) RoundTrip(req *http.Request) (*http.Response, error) { rl.limiter.Accept() return rl.rt.RoundTrip(req) } </ins> func getProjectAndZone() (string, string, error) { result, err := metadata.Get(\"instance/zone\") if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-b1dad1b374e4c58d925d9fef62d9846d5e0e5eda04aecdd78a124036a36cf31c", "text": "- that said, any rate-limitting on our side, will not solve the kubelet-related problem\nHmm - actually looking into implementation it seems that NodeAddresses are only contacting metadata server, so I'm not longer that convinced...\nAlso, I think that important thing is that a single call to GCE API can translate to multiple api calls to GCE. In particular - CreateRoute translates to: get instance insert route a bunch of getOperation (until this is finished)\nOK - so I think that what is happening here is that since CreateRoute translates to: get instance insert route a bunch of getOperations That means that if we call say 2000 CreateRoute() at the same time, all of them will try to issue: getInstance at the beginning. So we will quickly accumulate 2000 GET requests in the queue. Once they are processed, we generate the \"POST route\" then for any processed. So It's kind of expected what is happening here. So getting back to the Zach`s PR - I think that throttling POST and GET and OPERATION calls separate is kind of good idea in general.\nBut I still don't really understand why do we get \"RateLimitExceeded\". Is that because of Kubelets?\nI think that one problem we have at the RouteController level is that if CreateRoute fails, we simply don't react on it. And we will wait at least 5 minutes before even retrying it. We should add some retries at the route controller level too. I will send out some short PR for it.\nBut I still don't understand why do we get those \"RateLimitExceeded\" error\nOK - so as an update. In GCE, we have a separate rate-limit for number of in-flight CreateRoute call per project. is supposed to address this issue.\nOK - so this one is actually fixed. I mean that it is still long, but currently it's purely blocked on GCE.\nAs a comment - we have an internal bug for it already.", "commid": "kubernetes_issue_26119", "tokennum": 438}], "negative_passages": []}
{"query_id": "q-en-kubernetes-13cb3089998420c019d6232f14ee687d776c016c8b9d35a9031a6531b9228e82", "query": "<ins> /* Copyright 2023 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package service import \"context\" /* Copied from: k8s.io/apiserver/pkg/storage/value/encrypt/envelope/kmsv2 */ // Service allows encrypting and decrypting data using an external Key Management Service. type Service interface { // Decrypt a given bytearray to obtain the original data as bytes. Decrypt(ctx context.Context, uid string, req *DecryptRequest) ([]byte, error) // Encrypt bytes to a ciphertext. Encrypt(ctx context.Context, uid string, data []byte) (*EncryptResponse, error) // Status returns the status of the KMS. Status(ctx context.Context) (*StatusResponse, error) } // EncryptResponse is the response from the Envelope service when encrypting data. type EncryptResponse struct { Ciphertext  []byte KeyID       string Annotations map[string][]byte } // DecryptRequest is the request to the Envelope service when decrypting data. type DecryptRequest struct { Ciphertext  []byte KeyID       string Annotations map[string][]byte } // StatusResponse is the response from the Envelope service when getting the status of the service. type StatusResponse struct { Version string Healthz string KeyID   string } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-82432c9a9613bf4aed980cc8db469ba43857eb8e48c1e0dd0f39492115206ab6", "text": "generation for local KEK based on counter; also rotate once a week even if the counter does not hit 2 million? using AES-GCM encryption of local KEK ref: The implementation would be to the directory.\n/sig auth /triage accepted\n/assign\nGitHub didn't allow me to assign the following users: ibihim. 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\n/assign\nthank you !\n/milestone v1.26\nHi bug-triage shadow team member for 1.26 here. Looks like this issue is in the 1.26 milestone, but has been moved to 1.27. Is there something else or should this issue go to 1.27 as well? Thank you!\nI just forgot to move this issue /milestone v1.27\n/reopen is the partial implementation.\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nMy suggestion on the reference implementation, after reading 's comments is like so... The GRPC server, which implements the expects an implementation that satisfies . The local key logic can be a middleware. So it expects a it can fallback to, if it doesn't know a key or needs to encrypt its own local KEK. So the local implementation would be need to: have a storage of s have a reference to the current in use (if we put it into the cache, it might vanish) have a reference to another , which should be the remote KMS. So the sub-stories could look like: write Middleware write Transformers that can get exhausted (by time, by usage) write 's storage write some dummy for remote KMS? I have some sketches of what I am talking about .", "commid": "kubernetes_issue_112859", "tokennum": 462}], "negative_passages": []}
{"query_id": "q-en-kubernetes-13cb3089998420c019d6232f14ee687d776c016c8b9d35a9031a6531b9228e82", "query": "<ins> /* Copyright 2023 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package service import \"context\" /* Copied from: k8s.io/apiserver/pkg/storage/value/encrypt/envelope/kmsv2 */ // Service allows encrypting and decrypting data using an external Key Management Service. type Service interface { // Decrypt a given bytearray to obtain the original data as bytes. Decrypt(ctx context.Context, uid string, req *DecryptRequest) ([]byte, error) // Encrypt bytes to a ciphertext. Encrypt(ctx context.Context, uid string, data []byte) (*EncryptResponse, error) // Status returns the status of the KMS. Status(ctx context.Context) (*StatusResponse, error) } // EncryptResponse is the response from the Envelope service when encrypting data. type EncryptResponse struct { Ciphertext  []byte KeyID       string Annotations map[string][]byte } // DecryptRequest is the request to the Envelope service when decrypting data. type DecryptRequest struct { Ciphertext  []byte KeyID       string Annotations map[string][]byte } // StatusResponse is the response from the Envelope service when getting the status of the service. type StatusResponse struct { Version string Healthz string KeyID   string } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-b75b4d558a76c05a2f299aa9e4208bfe14cbcf4125785eeef841ee037778035f", "text": "I would implement that in terms of the interface so that it can be used both in testing (via a local key) and in real code (by delegating to a HSM).\nHi bug-triage team member for 1.27 here. This issue is still open but has had no recent activity, and no active PRs. Is everything on track for the Code Freeze in March 14th? Thank you!\n/milestone clear\nCould be closed, right? :)\nWe still need metrics and tracing support for the reference implementation (though it is all a lot less important now).\n/retitle [KMSv2] Add metrics and tracing in for plugins\nThis is duplicate of /close\nClosing this issue. <detailsIn response to : This is duplicate of 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", "commid": "kubernetes_issue_112859", "tokennum": 192}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1433c3a5d98c016afeece42862a47cbf2459d69f20aae71c9968851e19945c79", "query": "apps \"k8s.io/api/apps/v1\" \"k8s.io/api/core/v1\" <ins> apiequality \"k8s.io/apimachinery/pkg/api/equality\" </ins> \"k8s.io/apimachinery/pkg/api/errors\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/labels\"", "positive_passages": [{"docid": "doc-en-kubernetes-56dc15a3fe2161c6cf8927a51d2d0dce03fea80f01ef1e0345dcc3ca50d1379f", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: a cluster, And node1 with resource 1 DaemonSet, request resource 4 run , There is no pod created. resource to the node: run , There is still no pod created. What you expected to happen: In step 5, There is one pod created. How to reproduce it (as minimally and precisely as possible): see above description Anything else we need to know?: Environment: Kubernetes version (use ):1.10.5 Cloud provider or hardware configuration: OS (e.g. from /etc/os-release):CentOS7 Kernel (e.g. ): Install tools: Others: /sig app\nxref\nThanks! is not work here! Because: DaemonSetsController didn't watch the changes.(we use to updateNode.) we restart kubelet, The DaemonSetsController watch the changes, but it seems that the node info is not updated, and still failed to create pod:\nI found it is a bug here, ignore the changes. I made a fix , PTAL! Thanks!\nAny workarounds for old cluster versions? Up: looks like in my case helped but after some delay.\n, which version of k8s are you using? If it's sunset, you have to merge the pr yourself :). I think restart kubelet trigger delete/add to make sure it sync .\nSorry, I didn't say\nI think we still support 1.12 for now :) let's cherry pick it if not and wait for next 1.12 release.", "commid": "kubernetes_issue_67225", "tokennum": 342}], "negative_passages": []}
{"query_id": "q-en-kubernetes-143abc9f10f3a4e58d6b55563595a05b8eefd676d1b1d179c58a7380dee60f22", "query": "<ins> # Releasing Kubernetes This document explains how to create a Kubernetes release (as in version) and how the version information gets embedded into the built binaries. ## Origin of the Sources Kubernetes may be built from either a git tree (using `hack/build-go.sh`) or from a tarball (using either `hack/build-go.sh` or `go install`) or directly by the Go native build system (using `go get`). When building from git, we want to be able to insert specific information about the build tree at build time. In particular, we want to use the output of `git describe` to generate the version of Kubernetes and the status of the build tree (add a `-dirty` prefix if the tree was modified.) When building from a tarball or using the Go build system, we will not have access to the information about the git tree, but we still want to be able to tell whether this build corresponds to an exact release (e.g. v0.3) or is between releases (e.g. at some point in development between v0.3 and v0.4). ## Version Number Format In order to account for these use cases, there are some specific formats that may end up representing the Kubernetes version. Here are a few examples: - **v0.5**: This is official version 0.5 and this version will only be used when building from a clean git tree at the v0.5 git tag, or from a tree extracted from the tarball corresponding to that specific release. - **v0.5-15-g0123abcd4567**: This is the `git describe` output and it indicates that we are 15 commits past the v0.5 release and that the SHA1 of the commit where the binaries were built was `0123abcd4567`. It is only possible to have this level of detail in the version information when building from git, not when building from a tarball. - **v0.5-15-g0123abcd4567-dirty** or **v0.5-dirty**: The extra `-dirty` prefix means that the tree had local modifications or untracked files at the time of the build, so there's no guarantee that the source code matches exactly the state of the tree at the `0123abcd4567` commit or at the `v0.5` git tag (resp.) - **v0.5-dev**: This means we are building from a tarball or using `go get` or, if we have a git tree, we are using `go install` directly, so it is not possible to inject the git version into the build information. Additionally, this is not an official release, so the `-dev` prefix indicates that the version we are building is after `v0.5` but before `v0.6`. (There is actually an exception where a commit with `v0.5-dev` is not present on `v0.6`, see later for details.) ## Injecting Version into Binaries In order to cover the different build cases, we start by providing information that can be used when using only Go build tools or when we do not have the git version information available. To be able to provide a meaningful version in those cases, we set the contents of variables in a Go source file that will be used when no overrides are present. We are using `pkg/version/base.go` as the source of versioning in absence of information from git. Here is a sample of that file's contents: ``` var ( gitVersion   string = \"v0.4-dev\"  // version from git, output of $(git describe) gitCommit    string = \"\"          // sha1 from git, output of $(git rev-parse HEAD) ) ``` This means a build with `go install` or `go get` or a build from a tarball will yield binaries that will identify themselves as `v0.4-dev` and will not be able to provide you with a SHA1. To add the extra versioning information when building from git, the `hack/build-go.sh` script will gather that information (using `git describe` and `git rev-parse`) and then create a `-ldflags` string to pass to `go install` and tell the Go linker to override the contents of those variables at build time. It can, for instance, tell it to override `gitVersion` and set it to `v0.4-13-g4567bcdef6789-dirty` and set `gitCommit` to `4567bcdef6789...` which is the complete SHA1 of the (dirty) tree used at build time. ## Handling Official Versions Handling official versions from git is easy, as long as there is an annotated git tag pointing to a specific version then `git describe` will return that tag exactly which will match the idea of an official version (e.g. `v0.5`). Handling it on tarballs is a bit harder since the exact version string must be present in `pkg/version/base.go` for it to get embedded into the binaries. But simply creating a commit with `v0.5` on its own would mean that the commits coming after it would also get the `v0.5` version when built from tarball or `go get` while in fact they do not match `v0.5` (the one that was tagged) exactly. To handle that case, creating a new release should involve creating two adjacent commits where the first of them will set the version to `v0.5` and the second will set it to `v0.5-dev`. In that case, even in the presence of merges, there will be a single comit where the exact `v0.5` version will be used and all others around it will either have `v0.4-dev` or `v0.5-dev`. The diagram below illustrates it. ![Diagram of git commits involved in the release](./releasing.png) After working on `v0.4-dev` and merging PR 99 we decide it is time to release `v0.5`. So we start a new branch, create one commit to update `pkg/version/base.go` to include `gitVersion = \"v0.5\"` and `git commit` it. We test it and make sure everything is working as expected. Before sending a PR for it, we create a second commit on that same branch, updating `pkg/version/base.go` to include `gitVersion = \"v0.5-dev\"`. That will ensure that further builds (from tarball or `go install`) on that tree will always include the `-dev` prefix and will not have a `v0.5` version (since they do not match the official `v0.5` exactly.) We then send PR 100 with both commits in it. Once the PR is accepted, we can use `git tag -a` to create an annotated tag *pointing to the one commit* that has `v0.5` in `pkg/version/base.go` and push it to GitHub. (Unfortunately GitHub tags/releases are not annotated tags, so this needs to be done from a git client and pushed to GitHub using SSH.) ## Parallel Commits While we are working on releasing `v0.5`, other development takes place and other PRs get merged. For instance, in the example above, PRs 101 and 102 get merged to the master branch before the versioning PR gets merged. This is not a problem, it is only slightly inaccurate that checking out the tree at commit `012abc` or commit `345cde` or at the commit of the merges of PR 101 or 102 will yield a version of `v0.4-dev` *but* those commits are not present in `v0.5`. In that sense, there is a small window in which commits will get a `v0.4-dev` or `v0.4-N-gXXX` label and while they're indeed later than `v0.4` but they are not really before `v0.5` in that `v0.5` does not contain those commits. Unfortunately, there is not much we can do about it. On the other hand, other projects seem to live with that and it does not really become a large problem. As an example, Docker commit a327d9b91edf has a `v1.1.1-N-gXXX` label but it is not present in Docker `v1.2.0`: ``` $ git describe a327d9b91edf v1.1.1-822-ga327d9b91edf $ git log --oneline v1.2.0..a327d9b91edf a327d9b91edf Fix data space reporting from Kb/Mb to KB/MB (Non-empty output here means the commit is not present on v1.2.0.) ``` </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-7c5448078f172c3dba4d1f6f6ed5d66f21d2fc0ea9dd38dbb1ed9b4cc49eea15", "text": "Right now, we have a mixture of user documentation and developer documentation in the top-level directory. We should make it easier to find a just user documentation. Step 1 would be to move developer documentation into a subdir like docs/development or something like that. User docs would stay in the top-level docs dir.\nmove to", "commid": "kubernetes_issue_1797", "tokennum": 71}], "negative_passages": []}
{"query_id": "q-en-kubernetes-14c37d942ca329d6b44ffa891b7f5448ddb283e93ca32102c6b2309b956060d6", "query": "cmds.AddCommand(NewCmdPlugin(f, in, out, err)) cmds.AddCommand(NewCmdVersion(f, out)) cmds.AddCommand(NewCmdApiVersions(f, out)) <ins> cmds.AddCommand(NewCmdApiResources(f, out)) </ins> cmds.AddCommand(NewCmdOptions(out)) return cmds", "positive_passages": [{"docid": "doc-en-kubernetes-3c17ea4b4f4a9bb23915ee9fbb41703ef0532ac00becc05b8dda4d23a9ea9da2", "text": "As the RBAC role need to be related to resources. I think we could use a command to get the supported resources. ref to\nThis would be cool.\nI thought we a command that listed resources in the discover doc a long time ago.\nis just the versions, but principle is the same. We want to list all the types, their resources, and tie that back to \"explain\".\nWhat's the best way to determine this information currently? I'm having difficulty figuring out the exact set of permissions (and how they would be written in an RBAC role) for any given kubectl command. The documentation for this right now is split across multiple places and certain things are not explained at all. Specifically, it's difficult to determine which \"API verb\" is used for which operations. Take as an example. It's unclear if the way to allow this is to use the \"proxy\" subresource of a pod or service with \"get\"/\"create\"/etc. verbs, or to use the \"proxy\" verb with the resource (pod, service) directly. is a similar case. The almost works for this purpose, but it's still difficult. Operations for a given resource are grouped into categories like write, read, status, and proxy, but these things don't obviously correlate with API verbs. Again, proxy is especially confusing as there is no mention of a proxy \"verb\". The API operations are only shown using their HTTP verbs. One thing that could help on this document would be a section on the right column under \"kubectl command\" that shows exactly the rule needed in an RBAC role to allow this command via kubectl. And even then, that assumes an exact 1-to-1 mapping between API endpoints and kubectl commands, which I doubt is always the case. (For example, port fowarding to a pod seems to require both a GET on the pod resource and a CREATE on a port forward subresource.) There also needs to be better documentation about how this information could have been determined in the first place. I've resorted to manually looking through API requests made with but even then it's difficult to figure out. Amusingly, I was the one who wrote which is referenced in the original issue description (as well as the table explaining verbs in ).", "commid": "kubernetes_issue_42932", "tokennum": 494}], "negative_passages": []}
{"query_id": "q-en-kubernetes-14c37d942ca329d6b44ffa891b7f5448ddb283e93ca32102c6b2309b956060d6", "query": "cmds.AddCommand(NewCmdPlugin(f, in, out, err)) cmds.AddCommand(NewCmdVersion(f, out)) cmds.AddCommand(NewCmdApiVersions(f, out)) <ins> cmds.AddCommand(NewCmdApiResources(f, out)) </ins> cmds.AddCommand(NewCmdOptions(out)) return cmds", "positive_passages": [{"docid": "doc-en-kubernetes-20fd632aaf82ba3efee7609ebeda29ca6df3199abf73ef8bcfe417660974a0ce", "text": "tl;dr: It's too difficult right now to go from \"I want a user to be able to run \" to \"here is the RBAC rule to use for that\" for any case where there isn't a specific example shown in the docs.\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nIt seem that relative PR stop updated. If this issue still valuable, i will help fix it\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close", "commid": "kubernetes_issue_42932", "tokennum": 279}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1561c89861f88e3512e0ac02cbf05e2c56544709cf4b8534770797416e727199", "query": "name: \"TestPlugin1\", inj:  injectedResult{FilterStatus: int(framework.Error)}, }, { name: \"TestPlugin2\", inj:  injectedResult{FilterStatus: int(framework.Error)},", "positive_passages": [{"docid": "doc-en-kubernetes-63751a7023e8b04f1af20ab3ae3207ec2b4f40a0fbf73a42db07ba523eb8b990", "text": "changed the default behavior of scheduler framework's - from stopping at the first failed filter to always running all filters. This change breaks Cluster Autoscaler at scale. Cluster Autoscaler imports the scheduler framework to simulate filters on artificial nodes. In a (pretty common) one-pod-per-node scenario, the number of calls is ~quadratic wrt. the number of nodes needed for unschedulable pods - it can be a lot of calls. Before , in such scenario the vast majority of calls would stop at failing Fit or NodeAffinity filters, and not run the rest of them (e.g. PV-related filters). After the change, every call to runs all filters, which completely breaks Cluster Autoscaler at scale (an example scenario of 300 1-pod-per-node pods and 200 node groups takes 10min in 1.24, and ~50s in <1.22). Can we get the old behavior back? Or re-introduce the config option so that Cluster Autoscaler can set it accordingly? Ideally, we'd also like to get this backported as far as possible (the change was introduced in 1.24).\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scheduling\nThis seems to be a regression. I would be interested in adding a toggle flag that allows one to toggle on that behavior if this was done on purpose.\nThat PR wasn't supposed to change the behavior actually. Scheduler is always defaulted to stop upon the first Filter failure, and it's just we offered an option to continue go through other Filter plugins upon failures, and that option was removed recently. Let me check the code to see if there is a regression.\nWhen removed the following changes: It should have kept . I will submit a fix along with test, and backport to 1.24, 1.25, 1.26. Thanks for reporting!", "commid": "kubernetes_issue_114509", "tokennum": 478}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1561c89861f88e3512e0ac02cbf05e2c56544709cf4b8534770797416e727199", "query": "name: \"TestPlugin1\", inj:  injectedResult{FilterStatus: int(framework.Error)}, }, { name: \"TestPlugin2\", inj:  injectedResult{FilterStatus: int(framework.Error)},", "positive_passages": [{"docid": "doc-en-kubernetes-64891c2c5f731cd49a5bc282c860dc0eba8f556ac4ce7c46f89d192c47705edc", "text": "cc /assign /kind bug /kind regression /priority critical-urgent /triage/accepted\nThanks Kuba, this is indeed a regression on the scheduler end.\n/open for patches\n/re-open /reopen\nReopened this issue. <detailsIn response to : /re-open /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThanks for the reporting, and thanks for the fix.\nReally sorry about this regression, and hope not to happen again. I think there's no e2e tests between kubernetes scheduler and cluster-autoscaler, so can we also have testcases of pods unschedulable in scheduling perf-test, maybe this can also help to prevent this happening again. UT benchmark test also makes sense, but it's not graphical.\nThanks for the quick fix! Unfortunately I'm afraid this kind of issue would only be caught in a large-scale test scenario, which is not cheap to run continuously.\nFor this particular issue, UT ( in the PR) is able to catch it. And hence doesn't need to be that complicated to test with cluster-autoscaler. However, standing from a broader angle, why we didn't catch the regression in perf test is b/c the triggering actor is unschedulable Pods, instead of schedulable Pods (which are the happy path most perf tests covered). So going forward, I'd like to see more perf tests to mixin unschedulable Pods, and hence more likely to surface this kind of issue. (we have preemptio preemption test suite but doesn't seem adequate)\nThis is not for the particular issue, but keeping an eye on whether there's any performance degradation between two kubernetes components, like we do for scheduling performance. but it's actually out of the scope of scheduler. I'll add it as one of the goals of\nActually, the schedulerperf has a test case . And, the schedulerperf collects the metric (), which has the label in it (). But, the problem is currently we don't distinguish the metric values by label on each data; we just collect/aggregate it regardless the label.", "commid": "kubernetes_issue_114509", "tokennum": 494}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1561c89861f88e3512e0ac02cbf05e2c56544709cf4b8534770797416e727199", "query": "name: \"TestPlugin1\", inj:  injectedResult{FilterStatus: int(framework.Error)}, }, { name: \"TestPlugin2\", inj:  injectedResult{FilterStatus: int(framework.Error)},", "positive_passages": [{"docid": "doc-en-kubernetes-e7a581bff1a17589b65e3454390d917eb3d7571d932e457d6db360afa738d97e", "text": "(We can distinguish the metric values by any labels in the schedulerperf as we do in the metric ()) I'd say just distinguishing the happy path and unhappy path with label in metric should be enough to observe the particular performance degradation in the unhappy path.\ncould you help share the perf-dash link where this metric () is exposed?\nHm, cannot see any scheduler metrics result from the current perf-dash I see some configuration that seems to be to parse the schedulerperf result file though. https://perf- TBH, I haven't visited the perf-dash so much, so not sure whether it's not working for a long time, or got broken recently. Also, another thing, I noticed the perf-dash doesn't show all test cases. All test cases after haven't been executed.\nSo... probably, something wrong happens in  job (probably in the test case) and the schedulerperf is failing. The schedulerperf doesn't make the result file when fails, so I'm guessing that's why we cannot see any scheduler metrics results from the perf-dash. Okay, I found it. Let me open another issue for this.\ncc is this actually a regression, and is it resolved yet?\nIt's resolved by , and also cherry-picked to 1.24.x ~ 1.26.x. /close\nClosing this issue. <detailsIn response to : It's resolved by , and also cherry-picked to 1.24.x ~ 1.26.x. 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", "commid": "kubernetes_issue_114509", "tokennum": 369}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1569220cdd6645154e4e59ada26c2ee9510c3a953d16557a170bc8354fd53dd0", "query": "Subsets:    []corev1.EndpointSubset{subset}, }, epSlice } <ins> func TestEndpointsAdapterEnsureEndpointSliceFromEndpoints(t *testing.T) { endpoints1, epSlice1 := generateEndpointsAndSlice(\"foo\", \"testing\", []int{80, 443}, []string{\"10.1.2.3\", \"10.1.2.4\"}) endpoints2, epSlice2 := generateEndpointsAndSlice(\"foo\", \"testing\", []int{80, 443}, []string{\"10.1.2.3\", \"10.1.2.4\", \"10.1.2.5\"}) testCases := map[string]struct { endpointSlicesEnabled bool expectedError         error expectedEndpointSlice *discovery.EndpointSlice endpointSlices        []*discovery.EndpointSlice namespaceParam        string endpointsParam        *corev1.Endpoints }{ \"existing-endpointslice-no-change\": { endpointSlicesEnabled: true, expectedError:         nil, expectedEndpointSlice: epSlice1, endpointSlices:        []*discovery.EndpointSlice{epSlice1}, namespaceParam:        \"testing\", endpointsParam:        endpoints1, }, \"existing-endpointslice-change\": { endpointSlicesEnabled: true, expectedError:         nil, expectedEndpointSlice: epSlice2, endpointSlices:        []*discovery.EndpointSlice{epSlice1}, namespaceParam:        \"testing\", endpointsParam:        endpoints2, }, \"missing-endpointslice\": { endpointSlicesEnabled: true, expectedError:         nil, expectedEndpointSlice: epSlice1, endpointSlices:        []*discovery.EndpointSlice{}, namespaceParam:        \"testing\", endpointsParam:        endpoints1, }, \"endpointslices-disabled\": { endpointSlicesEnabled: false, expectedError:         nil, expectedEndpointSlice: nil, endpointSlices:        []*discovery.EndpointSlice{}, namespaceParam:        \"testing\", endpointsParam:        endpoints1, }, } for name, testCase := range testCases { t.Run(name, func(t *testing.T) { client := fake.NewSimpleClientset() epAdapter := EndpointsAdapter{endpointClient: client.CoreV1()} if testCase.endpointSlicesEnabled { epAdapter.endpointSliceClient = client.DiscoveryV1alpha1() } for _, endpointSlice := range testCase.endpointSlices { _, err := client.DiscoveryV1alpha1().EndpointSlices(endpointSlice.Namespace).Create(endpointSlice) if err != nil { t.Fatalf(\"Error creating EndpointSlice: %v\", err) } } err := epAdapter.EnsureEndpointSliceFromEndpoints(testCase.namespaceParam, testCase.endpointsParam) if !apiequality.Semantic.DeepEqual(testCase.expectedError, err) { t.Errorf(\"Expected error: %v, got: %v\", testCase.expectedError, err) } endpointSlice, err := client.DiscoveryV1alpha1().EndpointSlices(testCase.namespaceParam).Get(testCase.endpointsParam.Name, metav1.GetOptions{}) if err != nil && !errors.IsNotFound(err) { t.Fatalf(\"Error getting Endpoint Slice: %v\", err) } if !apiequality.Semantic.DeepEqual(endpointSlice, testCase.expectedEndpointSlice) { t.Errorf(\"Expected Endpoint Slice: %v, got: %v\", testCase.expectedEndpointSlice, endpointSlice) } }) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-12f7047d8d873a7d6bac7023fc38517c350449071b3fe2b6d53f3ea14de5351f", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: EndpointSlice for masters was not created after enabling EndpointSlice on a pre-existing cluster. Only those EndpointSlices managed by kube-controller-manager were created. What you expected to happen: EndpointSlice for masters should be created after enabling EndpointSlice on a pre-existing cluster, the same as the EndpointSlices managed by kube-controller-manager. How to reproduce it (as minimally and precisely as possible): kubeadm to create a cluster: the EndpointSlice feature by editing the kube-apiserver, kube-controller-manager, kube-proxy manifest kube-apiserver and kube-controller-manager is restarted, the EndpointSlice in namespace will be missing. Anything else we need to know?: Environment: Kubernetes version (use ):Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools:Network plugin and version (if this is a network-related bug): Others:\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/remove-triage unresolved /assign", "commid": "kubernetes_issue_84419", "tokennum": 307}], "negative_passages": []}
{"query_id": "q-en-kubernetes-157482496461231dbde9c145573688ba466ab3c2cda143416d21c7e4e6bed3e3", "query": "config.CloudProviderBackoffDuration = backoffDurationDefault } <del> // Do not add master nodes to standard LB by default. if config.ExcludeMasterFromStandardLB == nil { config.ExcludeMasterFromStandardLB = &defaultExcludeMasterFromStandardLB </del> <ins> if strings.EqualFold(config.LoadBalancerSku, loadBalancerSkuStandard) { // Do not add master nodes to standard LB by default. if config.ExcludeMasterFromStandardLB == nil { config.ExcludeMasterFromStandardLB = &defaultExcludeMasterFromStandardLB } // Enable outbound SNAT by default. if config.DisableOutboundSNAT == nil { config.DisableOutboundSNAT = &defaultDisableOutboundSNAT } } else { if config.DisableOutboundSNAT != nil && *config.DisableOutboundSNAT { return nil, fmt.Errorf(\"disableOutboundSNAT should only set when loadBalancerSku is standard\") } </ins> } azClientConfig := &azClientConfig{", "positive_passages": [{"docid": "doc-en-kubernetes-f91ac3317a925ac3a02c50dc39021d458d6020da9f69361ec2732a68459b1b7c", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: is the recommended way to configure the outbound networks together with Azure standard loadbalancer (SLB). However, for load balancer rules are disabled by default. That means all frontend IPs would be used as the SNAT IPs for virtual machines, according to . This would introduce troubles for various security scenarios, as there's no way to get a stable list of egress IPs. Azure cloud provider should support this scenario, and disable the outbound SNAT when outbound rules are configured by provisioning tools. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Others: /kind bug /sig azure /priority critical-urgent", "commid": "kubernetes_issue_75281", "tokennum": 247}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1589ddf4b71c85d1946eb2f83f74b3601802b189c3e3ade57e069d71c4e61724", "query": "} } <del> func TestValidateCustomResource(t *testing.T) { type args struct { schema apiextensions.JSONSchemaProps object interface{} </del> <ins> func stripIntOrStringType(x interface{}) interface{} { switch x := x.(type) { case map[string]interface{}: if t, found := x[\"type\"]; found { switch t := t.(type) { case []interface{}: if len(t) == 2 && t[0] == \"integer\" && t[1] == \"string\" && x[\"x-kubernetes-int-or-string\"] == true { delete(x, \"type\") } } } for k := range x { x[k] = stripIntOrStringType(x[k]) } return x case []interface{}: for i := range x { x[i] = stripIntOrStringType(x[i]) } return x default: return x </ins> } <ins> } func TestValidateCustomResource(t *testing.T) { </ins> tests := []struct { <del> name    string args    args wantErr bool </del> <ins> name           string schema         apiextensions.JSONSchemaProps objects        []interface{} failingObjects []interface{} </ins> }{ <del> // TODO: make more complete {\"!nullable against non-null\", args{ apiextensions.JSONSchemaProps{ </del> <ins> {name: \"!nullable\", schema: apiextensions.JSONSchemaProps{ </ins> Properties: map[string]apiextensions.JSONSchemaProps{ \"field\": { Type:     \"object\",", "positive_passages": [{"docid": "doc-en-kubernetes-42eca355948acd2923f06d9ab50c5116c5afebe4d73334e949a0d732f7352d29", "text": "The server-side validation does not check the type of values with . Create a CRD like: Then create a CR: It is not rejected, but should because must not be a boolean.", "commid": "kubernetes_issue_78817", "tokennum": 40}], "negative_passages": []}
{"query_id": "q-en-kubernetes-158c8d7e6cb42cdd012f531cc85d44007eca034e605ad73690e686b4a4edd627", "query": "{d: 8 * 24 * time.Hour, want: \"8d\"}, {d: 8*24*time.Hour + 23*time.Hour, want: \"8d\"}, {d: 2*365*24*time.Hour - time.Millisecond, want: \"729d\"}, <del> {d: 2 * 365 * 24 * time.Hour, want: \"2y0d\"}, {d: 2*365*24*time.Hour + 23*time.Hour, want: \"2y0d\"}, {d: 3 * 365 * 24 * time.Hour, want: \"3y0d\"}, </del> <ins> {d: 2 * 365 * 24 * time.Hour, want: \"2y\"}, {d: 2*365*24*time.Hour + 23*time.Hour, want: \"2y\"}, {d: 2*365*24*time.Hour + 23*time.Hour + 59*time.Minute, want: \"2y\"}, {d: 2*365*24*time.Hour + 24*time.Hour - time.Millisecond, want: \"2y\"}, {d: 2*365*24*time.Hour + 24*time.Hour, want: \"2y1d\"}, {d: 3 * 365 * 24 * time.Hour, want: \"3y\"}, {d: 4 * 365 * 24 * time.Hour, want: \"4y\"}, {d: 5 * 365 * 24 * time.Hour, want: \"5y\"}, {d: 6 * 365 * 24 * time.Hour, want: \"6y\"}, {d: 7 * 365 * 24 * time.Hour, want: \"7y\"}, </ins> {d: 8*365*24*time.Hour - time.Millisecond, want: \"7y364d\"}, {d: 8 * 365 * 24 * time.Hour, want: \"8y\"}, {d: 8*365*24*time.Hour + 364*24*time.Hour, want: \"8y\"},", "positive_passages": [{"docid": "doc-en-kubernetes-c52a82aeae83a0ba9ff68393d2821e656f88f6d5fbc5e134627056e17acb1808", "text": "What happened: When the duration is exactly 2 years or 3 years, human readable duration is returned as or . But when the duration is exactly 4 years, 5 years, etc, the human readable duration is returned as , , etc. What you expected to happen: The format of an exact year should be consistent. Remove when duration is an exact year: should be should be Check other years... 4, 5, 6, 7... not sure if they also have the problem. How to reproduce it (as minimally and precisely as possible): Because this is time-dependent, it can be difficult to reproduce via the CLI, but you can see the problem illustrated in which shows the current behavior: The and test cases should be changed to want and , and the code should be changed to make that pass. Anything else we need to know?: Note, this is not a problem when the duration is exactly 1 year because the human readable duration is still shown in days. So nothing needs to change to handle the case of exactly 1 year. Environment: Kubernetes version (use ): 1.18 Cloud provider or hardware configuration: n/a OS (e.g: ): n/a Kernel (e.g. ): n/a Install tools: n/a Network plugin and version (if this is a network-related bug): n/a Others: n/a\n/sig api-machinery\n/good-first-issue\nThis request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /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\nCould I pick this up as my first issue?\nAbsolutely. Just use to assign it to yourself.\nAlso I just updated the issue description. Check the other exact years 4, 5, 6, 7 because they might also have the problem, I can't remember. I know 8 and beyond don't have the problem because it just stops showing days after 8 years.\n/assign bitscuit\nmight recall a related PR?", "commid": "kubernetes_issue_89960", "tokennum": 475}], "negative_passages": []}
{"query_id": "q-en-kubernetes-158c8d7e6cb42cdd012f531cc85d44007eca034e605ad73690e686b4a4edd627", "query": "{d: 8 * 24 * time.Hour, want: \"8d\"}, {d: 8*24*time.Hour + 23*time.Hour, want: \"8d\"}, {d: 2*365*24*time.Hour - time.Millisecond, want: \"729d\"}, <del> {d: 2 * 365 * 24 * time.Hour, want: \"2y0d\"}, {d: 2*365*24*time.Hour + 23*time.Hour, want: \"2y0d\"}, {d: 3 * 365 * 24 * time.Hour, want: \"3y0d\"}, </del> <ins> {d: 2 * 365 * 24 * time.Hour, want: \"2y\"}, {d: 2*365*24*time.Hour + 23*time.Hour, want: \"2y\"}, {d: 2*365*24*time.Hour + 23*time.Hour + 59*time.Minute, want: \"2y\"}, {d: 2*365*24*time.Hour + 24*time.Hour - time.Millisecond, want: \"2y\"}, {d: 2*365*24*time.Hour + 24*time.Hour, want: \"2y1d\"}, {d: 3 * 365 * 24 * time.Hour, want: \"3y\"}, {d: 4 * 365 * 24 * time.Hour, want: \"4y\"}, {d: 5 * 365 * 24 * time.Hour, want: \"5y\"}, {d: 6 * 365 * 24 * time.Hour, want: \"6y\"}, {d: 7 * 365 * 24 * time.Hour, want: \"7y\"}, </ins> {d: 8*365*24*time.Hour - time.Millisecond, want: \"7y364d\"}, {d: 8 * 365 * 24 * time.Hour, want: \"8y\"}, {d: 8*365*24*time.Hour + 364*24*time.Hour, want: \"8y\"},", "positive_passages": [{"docid": "doc-en-kubernetes-f6c1495fe924460d9eb2ac0fa6ac2f987b00b8ce0493b8b416038d6dd8a8b830", "text": "(also, I have to leave the pedantic note: a year isn't always 365 days, so it's surprising to me to see the abbreviation exists at all)\nI can't find it. Maybe I was remembering\nYeah it was probably that one. At first I had the tests and the fix. But it sat for a while. I changed it to just the tests of existing behavior so it could be approved more easily. Then I made this issue for the fix but decided it would probably be a good first time issue for someone instead of me doing it.\nso should leap years be considered by the code?\nThere's no way to know how long a year is without knowing the date, so it's not a good unit--in the abstract, there's no way to know if it's a leap year or not. The go language deliberately omits it IIRC. Henry Li <:\nWhat's the intention of HumanDuration? From what I've seen, it is just an approximation of a timestamp solely for humans to understand, so assuming 365 days per year sounds about right to me. This issue is about consistency though, so it could be solved the other way. Instead of abbreviating when it's an exact year (2y, 3y, etc.), exact years could just all have 0d (2y0d, 3y0d, etc.)\nI think it is just used for a ballpark duration. It loses accuracy as the duration increases anyway because it changes the units. I guess my intention for opening the issue was to make it consistent with itself. For example it doesn't say 2d0h or 2h0m, so it should not say 2y0d.\n(FTR I agree that Xy0d looks worse than Xy.) Brian Pursley <:\nHi I have made the required changes. Shall I raise the PR if you haven't started working in it ?\nalready assigned it, so I think it would be good to let him submit the PR, unless he unassigns or does not submit a PR in a reasonable amount of time.\nThanks I was planning on submitting the PR over the weekend\nHello, I am a first timer in open source contribution community. I think I made the required changes for that issue. However, I don't know how assignment rules work.", "commid": "kubernetes_issue_89960", "tokennum": 495}], "negative_passages": []}
{"query_id": "q-en-kubernetes-159a322885435d6f98172a3b8f6e9f8bda38012e8e4d69750d0f676946b7548a", "query": "# Wait for last batch of jobs kube::util::wait-for-jobs || { <del> echo -e \"${color_red}Some commands failed.${color_norm}\" >&2 </del> <ins> code=$? echo -e \"${color_red}Failed to create firewall rule.${color_norm}\" >&2 exit $code </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-99c81b4f57584ea95d5f96a4bd9eeeb1b9aeab22e948ca7c4386b5070fb15e2e", "text": "Kubernetes e2e suite [It] [sig-network] Firewall rule should have correct firewall rules for e2e cluster See also a similar cluster with the same test failing: /kind failing-test /kind flake /sig network\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_111580", "tokennum": 141}], "negative_passages": []}
{"query_id": "q-en-kubernetes-159ce8c52fd64953ea98f6015041ff31bd4cdcaf10ab19accf8a63b63a21ec31", "query": "framework.SkipUnlessProviderIs(\"gke\") nsFlag := fmt.Sprintf(\"--namespace=%v\", ns) podJson := readTestFileOrDie(kubectlInPodFilename) <ins> // Replace the host path to kubectl in json podString := strings.Replace(string(podJson), \"$KUBECTL_PATH\", framework.TestContext.KubectlPath, 1) </ins> By(\"validating api verions\") <del> framework.RunKubectlOrDieInput(string(podJson), \"create\", \"-f\", \"-\", nsFlag) </del> <ins> framework.RunKubectlOrDieInput(podString, \"create\", \"-f\", \"-\", nsFlag) </ins> err := wait.PollImmediate(time.Second, time.Minute, func() (bool, error) { output := framework.RunKubectlOrDie(\"get\", \"pods/kubectl-in-pod\", nsFlag) if strings.Contains(output, \"Running\") {", "positive_passages": [{"docid": "doc-en-kubernetes-30073b5bdd6536f3426706d62259848d2143e49f7e7d427f9e7ac1b4ee8d409d", "text": "https://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes", "commid": "kubernetes_issue_36586", "tokennum": 633}], "negative_passages": []}
{"query_id": "q-en-kubernetes-159ce8c52fd64953ea98f6015041ff31bd4cdcaf10ab19accf8a63b63a21ec31", "query": "framework.SkipUnlessProviderIs(\"gke\") nsFlag := fmt.Sprintf(\"--namespace=%v\", ns) podJson := readTestFileOrDie(kubectlInPodFilename) <ins> // Replace the host path to kubectl in json podString := strings.Replace(string(podJson), \"$KUBECTL_PATH\", framework.TestContext.KubectlPath, 1) </ins> By(\"validating api verions\") <del> framework.RunKubectlOrDieInput(string(podJson), \"create\", \"-f\", \"-\", nsFlag) </del> <ins> framework.RunKubectlOrDieInput(podString, \"create\", \"-f\", \"-\", nsFlag) </ins> err := wait.PollImmediate(time.Second, time.Minute, func() (bool, error) { output := framework.RunKubectlOrDie(\"get\", \"pods/kubectl-in-pod\", nsFlag) if strings.Contains(output, \"Running\") {", "positive_passages": [{"docid": "doc-en-kubernetes-190b617a6f6f5bf58cdcd7e3b6ef0448e95fbe4e5f55ef7f7041e83808b7f11a", "text": "e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nAre you the correct assignee for this? If so, can you please give an update. If not, can you please reassign it to the correct person. CC\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nYes, I guess so. I'm looking into it.", "commid": "kubernetes_issue_36586", "tokennum": 517}], "negative_passages": []}
{"query_id": "q-en-kubernetes-159ce8c52fd64953ea98f6015041ff31bd4cdcaf10ab19accf8a63b63a21ec31", "query": "framework.SkipUnlessProviderIs(\"gke\") nsFlag := fmt.Sprintf(\"--namespace=%v\", ns) podJson := readTestFileOrDie(kubectlInPodFilename) <ins> // Replace the host path to kubectl in json podString := strings.Replace(string(podJson), \"$KUBECTL_PATH\", framework.TestContext.KubectlPath, 1) </ins> By(\"validating api verions\") <del> framework.RunKubectlOrDieInput(string(podJson), \"create\", \"-f\", \"-\", nsFlag) </del> <ins> framework.RunKubectlOrDieInput(podString, \"create\", \"-f\", \"-\", nsFlag) </ins> err := wait.PollImmediate(time.Second, time.Minute, func() (bool, error) { output := framework.RunKubectlOrDie(\"get\", \"pods/kubectl-in-pod\", nsFlag) if strings.Contains(output, \"Running\") {", "positive_passages": [{"docid": "doc-en-kubernetes-dd35fe5a7b4eb5003d2805a282d33ab299b7be8f45ced73e66ae92981d37585e", "text": "https://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nWe need to get this fixed soon and picked up in release-1.5 since it is consistently red in\nack i have a PR currently running\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nIf you found the root cause, we will close my pending PR that printing out some debug info. What is the PR # of the commit you mentioned above?", "commid": "kubernetes_issue_36586", "tokennum": 470}], "negative_passages": []}
{"query_id": "q-en-kubernetes-159ce8c52fd64953ea98f6015041ff31bd4cdcaf10ab19accf8a63b63a21ec31", "query": "framework.SkipUnlessProviderIs(\"gke\") nsFlag := fmt.Sprintf(\"--namespace=%v\", ns) podJson := readTestFileOrDie(kubectlInPodFilename) <ins> // Replace the host path to kubectl in json podString := strings.Replace(string(podJson), \"$KUBECTL_PATH\", framework.TestContext.KubectlPath, 1) </ins> By(\"validating api verions\") <del> framework.RunKubectlOrDieInput(string(podJson), \"create\", \"-f\", \"-\", nsFlag) </del> <ins> framework.RunKubectlOrDieInput(podString, \"create\", \"-f\", \"-\", nsFlag) </ins> err := wait.PollImmediate(time.Second, time.Minute, func() (bool, error) { output := framework.RunKubectlOrDie(\"get\", \"pods/kubectl-in-pod\", nsFlag) if strings.Contains(output, \"Running\") {", "positive_passages": [{"docid": "doc-en-kubernetes-34e45dcd30e91b287f55b34ca0f7c874b506aed582f8cf03d9c09b8eddbaff00", "text": "https://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\n: here it is\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nWe timeout waiting for pod sometimes. Is it reasonable to use a longer timeout? Use for in that test.\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\n: sure thing, do you want to do that in a fresh PR?\nI updated my pending PR .\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}", "commid": "kubernetes_issue_36586", "tokennum": 397}], "negative_passages": []}
{"query_id": "q-en-kubernetes-159f96c3ff81f0439d45ec73ab19ef535fb69031517310f1d60f4284b3119732", "query": "podLabels := map[string]string{\"name\": \"nginx\"} replicas := 1 Logf(\"Creating simple deployment %s\", deploymentName) <del> _, err := c.Deployments(ns).Create(newDeployment(deploymentName, replicas, podLabels, \"nginx\", \"nginx\")) </del> <ins> _, err := c.Deployments(ns).Create(newDeployment(deploymentName, replicas, podLabels, \"nginx\", \"nginx\", extensions.RollingUpdateDeploymentStrategyType)) </ins> Expect(err).NotTo(HaveOccurred()) defer func() { deployment, err := c.Deployments(ns).Get(deploymentName)", "positive_passages": [{"docid": "doc-en-kubernetes-ceb20554e653f6657baad1bbb36c40e66d8a76887956e3c674b77febc82d4455", "text": "There's some practical limit on the number of concurrent access tokens that can be used in a Kubernetes cluster before it begins to spend all of its time in the authn stack verifying them. Absent fixes to it was < 500; with the fixes linked there it's still not infinitely scalable-- I still hit (what I believe to be) with ~ 5k unique tokens @ ~700QPS. This request is to this dimension an official name & definition, and list it with others, e.g. here: it it have a useful value (I think it should be 10k) /kind bug /sig scalability\n/cc\noh and 4. add tests which verify it is as high as believed.\ncc since projected tokens will increase the number of unique tokens\n/sig auth\nLRUs are not good at scaling and sharding has some major pitfalls as pointed out. I would suggest that we try to drop the LRU cache for successful authentication results in the token cache. The main benefit of using an LRU here is bound cache size. Entries in the token cache have a fast expiration independent of the LRU policy. The records probably take up O(2kb) (guesstimate) of memory. Given that these are successful attempts with presumably valid tokens, I don't think we are getting any benefit from the LRU. If we don't have a constraint on fixed cache size, we can back the token cache with a sync.Map and run a single background goroutine to periodically walk the map and remove expired entries. This would fix the problematic locking and eviction due to nonuniform distribution of tokens over shards. The failure cache is less important and we don't cache failures by default. If we consider this the \"slowpath\", we can probably leave it as. If that's not good enough, we have a couple options (with various tradeoffs) to improve it.\nIf off by default is not enough, more reasoning why the failed cache is not super useful: it might help with an accidental DoS but it doesn't prevent anything actively malicious DoS. I think we can focus our improvements on the success cache.\n/assign He is already working on adding an explicit test for it.\nhas taken it over and is actively working on this. Unfortunately, I cannot assign this issue to him as he's not a k8s member yet\nIt's not closed - all testes must be submitted and appropriate documentation must be\nThanks everyone!!", "commid": "kubernetes_issue_83375", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-15a36e4cb37f3774b4e5d6f4bc30cfbb91fdbf3f9ce9f18f9691211baad69c33", "query": "} return parameters, nil default: <ins> sort.Slice(objs, func(i, j int) bool { obj1, obj2 := objs[i].(*resourcev1alpha2.ResourceClassParameters), objs[j].(*resourcev1alpha2.ResourceClassParameters) if obj1 == nil || obj2 == nil { return false } return obj1.Name < obj2.Name }) </ins> return nil, statusError(logger, fmt.Errorf(\"multiple generated class parameters for %s.%s %s found: %s\", class.ParametersRef.Kind, class.ParametersRef.APIGroup, klog.KRef(class.Namespace, class.ParametersRef.Name), klog.KObjSlice(objs))) } }", "positive_passages": [{"docid": "doc-en-kubernetes-16e9d6242dd147113f7225a4b24c8c9581a1b180a6b05f0edc47ba4e0c49bde0", "text": "master-blocking: ci-kubernetes-unit It starts flaking today 30-05-2024 The test fail is This failure may be caused by the error message's order sensitivity. The error message's order of Resource Classes versus is different. N/A /sig node /sig scheduling\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/remove-sig testing /sig scheduling (sig testing doesn't own all of the unit tests, just test frameworks, tooling, CI infra, etc) This appears to be a flake in scheduler unit tests which would be sig scheduling ( )\n.. and it appears to be DRA specific subset of scheduling so /sig node as well\nFYI - looks like this is happening every 3-6 hours give or take. Yesterday it was every six hours and today it seems to be every 3-4 hours. Looking into it a bit more, it looks like it may just be an issue with a connection via the test while it's trying to hit the server. I don't think the test itself is failing, I think the connection to the server is failing. ! CC\nHey All - hope you're well. Michael here from the Release Signal team. Just wanted to touch base and make sure we're good to go for the cut on the 4th. CC /sig-node", "commid": "kubernetes_issue_125221", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-15ac2e60d16b760309acde7248e001022ec7de4fc074d451a056ce642f5c6c9a", "query": "ExitCode: 5, }, }, <del> map[string]error{\"with-reason\": testErrorReason, \"succeed\": testErrorReason}, []api.ContainerStatus{}, map[string]api.ContainerState{ </del> <ins> reasons:     map[string]error{\"with-reason\": testErrorReason, \"succeed\": testErrorReason}, oldStatuses: []api.ContainerStatus{}, expectedState: map[string]api.ContainerState{ </ins> \"without-reason\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID,", "positive_passages": [{"docid": "doc-en-kubernetes-b4459e221a04f6723f7b97c6a9d43d61c0d65417b08d143223c7057699636055", "text": "is this a Node bug? cc as next oncall to follow up on this.\nThis is a node bug due to init containers\nI may need help debugging - I see:\nSo I think the problem is in the error case - we're not properly recording that the start failed, and the next time we come in we somehow think the first container succeeded. I'll add some debugging to see if we can't recreate it.\nLet's discuss on instead.", "commid": "kubernetes_issue_25879", "tokennum": 102}], "negative_passages": []}
{"query_id": "q-en-kubernetes-15ac2e60d16b760309acde7248e001022ec7de4fc074d451a056ce642f5c6c9a", "query": "ExitCode: 5, }, }, <del> map[string]error{\"with-reason\": testErrorReason, \"succeed\": testErrorReason}, []api.ContainerStatus{}, map[string]api.ContainerState{ </del> <ins> reasons:     map[string]error{\"with-reason\": testErrorReason, \"succeed\": testErrorReason}, oldStatuses: []api.ContainerStatus{}, expectedState: map[string]api.ContainerState{ </ins> \"without-reason\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID,", "positive_passages": [{"docid": "doc-en-kubernetes-dcc88d1d89328d1da3366de828afcd8ab0373228cc4437ea655e2cda79030f86", "text": "Kubelet issues a docker inspect call after creating a container, but for very short lived containers there is a window in which they could exit before being inspected in the docker manager. If the container PID is 0, we should check the ExitCode and other relevant fields and handle them appropriately. [1] This is the suspected cause of several flakes: /cc\nlooking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: I'd expect the second one to not have run in this case? Node logs:\nInit containers have an implicit assumption that container statuses include results of previous SyncPod invocations. If that's not the case we may need to fix that (or at least mitigate it). On May 18, 2016, at 8:28 PM, Prashanth B wrote: looking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: May 18 15:58:33.380: INFO: pod-init--1d4b-11e6-80a4- started at 2016-05-18T15:58:04-07:00 (2+1 container statuses recorded) May 18 15:58:33.380: INFO: Init container init1 ready: false, restart count 0 May 18 15:58:33.380: INFO: Init container init2 ready: true, restart count 0 I'd expect the second one to not have run in this case? Node logs: \u2014 You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub\nThis should be true. Is there any evidence that suggests the opposite? only shows conflicting view of whether init1 has run.\nIf the container exits already and it's not an infra container, kubelet should not error out. Although even if it does, I failed to see how this could affect the readiness of the init container without checking the code further.", "commid": "kubernetes_issue_25844", "tokennum": 487}], "negative_passages": []}
{"query_id": "q-en-kubernetes-15ac2e60d16b760309acde7248e001022ec7de4fc074d451a056ce642f5c6c9a", "query": "ExitCode: 5, }, }, <del> map[string]error{\"with-reason\": testErrorReason, \"succeed\": testErrorReason}, []api.ContainerStatus{}, map[string]api.ContainerState{ </del> <ins> reasons:     map[string]error{\"with-reason\": testErrorReason, \"succeed\": testErrorReason}, oldStatuses: []api.ContainerStatus{}, expectedState: map[string]api.ContainerState{ </ins> \"without-reason\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID,", "positive_passages": [{"docid": "doc-en-kubernetes-ade5deee53831749acf4a20dbe39f9ef1836656ae43e40b0bb8594efa4e81e92", "text": "Each syncPod invocation, we inspect the list of init container in order looking for lastTerminationState. There could be a bug in that logic, or if we didn't get the full status, we might make a bad decision. When determining which container to run next, we always look for the last init container in the chain that has success, then run the next container (unless the pod is RestartNever). , Yu-Ju Hong wrote:\nSaw this flake again. How do we verify that container status is not lost between syn pods?\n... between calls to syncPods\nThe second sync clearly saw the init1 container, and decided to launch init2. See \"InitContainersToKeep\" in the message below.\ncontainers to keep can include failed containers. , Yu-Ju Hong wrote:\nDiscussed on slack. In summary, the problem has to do with how we convert the kubecontainer.PodStatus to the api.PodStatus. If a container is terminated, the function makes the decisions: the pod restart policy is \"Always\", and there is a \"failure reason\" recorded for the given container, this means the pod worker tried to (re)start the container but failed. Set the state to \"Waiting\" and populate the reason. , the container state is simply \"terminated\". Init containers don't obey the restart policy like regular containers, and the logic will need to be amended to work with them. is working on a PR. In addition to that, kubelet should not error out if a user container exited before it could apply the oom score (which is best effort in this case). fixes that.\nAhh, thanks for digging into the issue. This is the exact the concern I had when I reviewed the initial implementation of init container, which blocks pr for a while. I even asked to help me verify this case, unfortunately we didn't reproduce the issue back then. :-(\nI wish I'd seen the flakes in the runs prior to merge.\nWe didn't notice this until we started running the tests against docker v1.11.1, which is much faster and hit the race condition differently.\nI suppose that's a good thing...\nIt is hard to reproduce this.", "commid": "kubernetes_issue_25844", "tokennum": 482}], "negative_passages": []}
{"query_id": "q-en-kubernetes-15ac2e60d16b760309acde7248e001022ec7de4fc074d451a056ce642f5c6c9a", "query": "ExitCode: 5, }, }, <del> map[string]error{\"with-reason\": testErrorReason, \"succeed\": testErrorReason}, []api.ContainerStatus{}, map[string]api.ContainerState{ </del> <ins> reasons:     map[string]error{\"with-reason\": testErrorReason, \"succeed\": testErrorReason}, oldStatuses: []api.ContainerStatus{}, expectedState: map[string]api.ContainerState{ </ins> \"without-reason\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID,", "positive_passages": [{"docid": "doc-en-kubernetes-0814a4e75b48cf2d27d20141c180e04fbc9b55d5398cce31b037f460c93acb1b", "text": "The extra check of last terminated container in your initial code makes me nervous, but we couldn't reproduce it due to that small race windows until we have a faster docker running on the node. :-)\nI got \"Pods should invoke init containers on a RestartAlways pod\" flake (referenced from ): Logs:\nAll the fixes went in. Please reopen this issue if you see any more flakes.", "commid": "kubernetes_issue_25844", "tokennum": 90}], "negative_passages": []}
{"query_id": "q-en-kubernetes-15d193f9cafcd1662b769adeb174e242dbbba2375b19a57041adfd40c9159ada", "query": "// be sure to unset environment variable https_proxy (if exported) before testing, otherwise the testing will fail unexpectedly. func TestRoundTripSocks5AndNewConnection(t *testing.T) { <del> t.Skip(\"Flake https://issues.k8s.io/107708\") </del> localhostPool := localhostCertPool(t) for _, redirect := range []bool{false, true} {", "positive_passages": [{"docid": "doc-en-kubernetes-631bc5da562ebc33bd49790f3078648639a2126878c5fc7773cd8143bd3bdf27", "text": "TestRoundTripSocks5AndNewConnection Disabled by No response No response No response /sig\nThere are no sig labels on this issue. Please add an appropriate label by using one of the following commands: - Please see the for a listing of the SIGs, working groups, and committees available. <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\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nthere is a race shutting down the socks5 server", "commid": "kubernetes_issue_107766", "tokennum": 198}], "negative_passages": []}
{"query_id": "q-en-kubernetes-15d36c83b20b960cab6624bab196ab42b7da2fb7c638168f08ad95a8e476b005", "query": "input           *v1.Node want            bool }{ <ins> {want: false, input: &v1.Node{}}, {want: true, input: &v1.Node{Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionTrue}}}}}, {want: false, input: &v1.Node{Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionFalse}}}}}, {want: true, input: &v1.Node{Spec: v1.NodeSpec{Unschedulable: true}, Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionTrue}}}}}, </ins> {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{}}}}, {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{labelNodeRoleMaster: \"\"}}}}, {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{labelNodeRoleExcludeBalancer: \"\"}}}},", "positive_passages": [{"docid": "doc-en-kubernetes-932c798c1f1bc917ff850ea55bf430820901f4817711595aba278a9098d6e82b", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: What happened: In order to migrate to a new version of kubernetes on GKE. I cordoned(Kubectl cordon <node) all nodes in the old node pool(1.8.9) in order to drain the node pool(pods on the node) with an intention to cause the pods to run on a new version of the node pool(1.10.2). As soon as I cordoned all the nodes in the old node pool, it caused the downtime of ingress(nginx). The nginx controller pods where running fine on the cordoned node pool. But the cordon caused the nodes to be removed from the target pool of ingress load balancer. Below are the documents that suggest the above same method that I followed as best practice for zero downtime upgrade. 1). 2). What you expected to happen: I expected \"kubectl cordon <node\" not to have the node/s removed from the target pool of the loadbalancer because the nginx controller pods where running absolutely fine on these nodes. How to reproduce it (as minimally and precisely as possible): 1).Cordon all the nodes in an old node pool that runs nginx controller. Anything else we need to know?: Environment: Kubernetes version (use ): 1.10.2 Cloud provider or hardware configuration: GKE OS (e.g. from /etc/os-release): Container OS Kernel (e.g. ): 4.14.22+ Install tools: Others: Cordon causes to remove the nodes from the target pool of the ingress load balancer. The health checks fail on the nodes of the target pool, which should not be the case. Because the nginx controller pods run fine on these nodes.\nTechnically, this isn't a Kubernetes bug as this is working as intended; however, it does beg the question why we remove unschedulable nodes if they're marked as ready since we perform the to determine LB backend nodes. is it scheduable? is it not a master? is it not marked for exclusion? is it marked as ready?", "commid": "kubernetes_issue_65013", "tokennum": 511}], "negative_passages": []}
{"query_id": "q-en-kubernetes-15d36c83b20b960cab6624bab196ab42b7da2fb7c638168f08ad95a8e476b005", "query": "input           *v1.Node want            bool }{ <ins> {want: false, input: &v1.Node{}}, {want: true, input: &v1.Node{Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionTrue}}}}}, {want: false, input: &v1.Node{Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionFalse}}}}}, {want: true, input: &v1.Node{Spec: v1.NodeSpec{Unschedulable: true}, Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionTrue}}}}}, </ins> {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{}}}}, {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{labelNodeRoleMaster: \"\"}}}}, {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{labelNodeRoleExcludeBalancer: \"\"}}}},", "positive_passages": [{"docid": "doc-en-kubernetes-3337d8d773bd260e0255505bc31356b49bc0519e69eafd73453232de84478830", "text": "If any of those are a no, then it'll be removed from the pool on the next sync. Perhaps someone from can shed some light. /sig network\ncc This problem extends beyond GCP/ingress controller and to anyone using pools to upgrade nodes. A typical workflow I see is you'd cordon a node pool so as you drain each node the pods don't go to another node in the pool that'll shortly be drained as well. The current logic does not support that and complicates cluster administration because cordoning does not respect PDB's.\n/remove-sig apps /remove-sig gcp (since the service controller falls under sig networking)\nThose labels are not set on the issue: <detailsIn response to : /remove-sig apps /remove-sig gcp 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\nRef I thought a general practice for draining the old pool is to move over one node at a time in a rolling fashion. Shouldn't there always be certain backend pods being able to receive & serve traffic? cc\nWRT draining, it is recommended to do it one node at a time ; however, in real world scenarios doing it one node at a time can cause a lot of avoidable container churn if you don't cordon off the nodes you at least plan to drain so that pods aren't being scheduled on a node you'll be draining after the next one. According to the comments in the service controller it seems the unschedulable part exists because it was how we differentiated masters in the past; however, we have labels for that now. We also have the service exclusion label (can't find when/if that'll be promoted though as i don't think there's a ticket on it).\nI'm having problems with this issue as well. The fact that nodes are removed from target pools when cordoned means that I sometimes get brief interruptions of the traffic to a service when I cordon a node. I'm guessing the node isn't gracefully removed from the load balancer which results in some traffic being cut off trying to route through the recently cordoned node. The same problem occasionally happens when deleting nodes / node pools or when the cluster autoscaler deletes a node. We are running GKE ver. 1.10.2-gke.1.", "commid": "kubernetes_issue_65013", "tokennum": 523}], "negative_passages": []}
{"query_id": "q-en-kubernetes-15d36c83b20b960cab6624bab196ab42b7da2fb7c638168f08ad95a8e476b005", "query": "input           *v1.Node want            bool }{ <ins> {want: false, input: &v1.Node{}}, {want: true, input: &v1.Node{Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionTrue}}}}}, {want: false, input: &v1.Node{Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionFalse}}}}}, {want: true, input: &v1.Node{Spec: v1.NodeSpec{Unschedulable: true}, Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionTrue}}}}}, </ins> {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{}}}}, {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{labelNodeRoleMaster: \"\"}}}}, {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{labelNodeRoleExcludeBalancer: \"\"}}}},", "positive_passages": [{"docid": "doc-en-kubernetes-434e849b429a310bf0eaaee7ac5356c43a18352f5a8ac7f41c382993cffab77f", "text": "Our best defence against these issue have so far been to limit node changes as much as possible and not use any auto scaling.\nI've posted a question regarding this issue in SO some weeks before it was created. The suggested action was to use node taints () instead of cordon, that way nodes will still be marked as .\nThank you for the link, it Certainly helped. Perhaps, if thats the case(as mentioned in the accepted answer of the above link), then to cordon all the nodes of old node pools should not be a recommended action, at least in the GKE upgrade docs.\nonly says: And I can't find what more it does in the documentation. So I would expect that it has exactly the same behaviour as a taint. Why is removing running pods from the balancer working as intended? If it isn't a bug then the documentation is certainly unclear in this regard.\nThis just caused a major outage for us too. I agree with the previous posts, while this may be working as the code intended, it does not follow the patterns and documentation k8s provides. When I cordon a node it should not impact the traffic going to the node or any pods on it. I should be able to gradually remove traffic by draining nodes/pods and respecting PDBs.\nthis issue touches on the fact we are removing masters as well and inadvertently removing cordoned nodes. The logic in the service controller mentions we only filter out unschedulable nodes since that's how masters were setup.\nWe wanted to replace all of the kubernetes cluster nodes to different node instance types, so we started off by cordoning all of the nodes, but it surprisingly caused an outage for us. As pointed out, the only documentation around cordoning is , which I took to mean that new pods can not be scheduled on those nodes. It was surprising behavior to find out that, not only does it not allow new pods to be scheduled on those nodes, but that it also causes the service controller to remove unschedulable nodes from load balancing pools. I understand that it's working as intended, but if that was also documented as part of the cordon operation, I would have been able to avoid an outage.\nI finally caught up to this bug. Fun one. I agree that this is working-as-intended and that it stinks. We can do better.", "commid": "kubernetes_issue_65013", "tokennum": 496}], "negative_passages": []}
{"query_id": "q-en-kubernetes-15d36c83b20b960cab6624bab196ab42b7da2fb7c638168f08ad95a8e476b005", "query": "input           *v1.Node want            bool }{ <ins> {want: false, input: &v1.Node{}}, {want: true, input: &v1.Node{Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionTrue}}}}}, {want: false, input: &v1.Node{Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionFalse}}}}}, {want: true, input: &v1.Node{Spec: v1.NodeSpec{Unschedulable: true}, Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionTrue}}}}}, </ins> {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{}}}}, {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{labelNodeRoleMaster: \"\"}}}}, {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{labelNodeRoleExcludeBalancer: \"\"}}}},", "positive_passages": [{"docid": "doc-en-kubernetes-33075f048c6031b18ea2c4d42a5821aded2e74dadef5a72c2d24382b09d40a2a", "text": "As a short-term workaround, you can taint the nodes before cordoning one-by-one. That will stop new work from arriving, but will leave old work there. If we agree on an appropriately named taint, we can have nginx tolerate it by default. Am I missing any reason why this would not work? If that flies, we should fix docs ( those are GCP docs). I am happy to help with that. Longer term maybe we can do something smarter. I am not sure what that would be, just now. Ideas?\nIs there any reason we can't just leave the nodes in the load balancer pool when the node is cordoned? And when the pods are terminated the nodes can be removed? I may be missing some context here?\nThe presumption is that a node that is unschedulable is going away, or needs some other repair. Using it as a target for load-balancers means there could be sessions routed THROUGH that node. Even as the pods are drained. Right up until the node suddenly dies, causing an outage of a different flavor. What should really happen is that a node which becomes unschedulable starts draining connections. Once all the pods are moved off, the node can be removed from the pool entirely. I don't think any cloud providers, even GCP, handle this just right today. David Radcliffe <:\nWait, if you brought up a new nodepool, all those new nodes should be in the TargetPool. Cordoning the old nodepool should only terminate the existing connections, new connections should be fine. Something doesn't add up...\nWas this using\nYes\nRight, well, that explains it. So even draining won't do what you want - you need new connections to be allowed until you have capacity in the new pool. The good news is that you can do this entirely yourself, with taints. We just need nginx to tolerate the taint, which you can also specify yourself. The only real alternative I see would be, as you said, to leave nodes in the LB pool until the node dies. Given that we never specified this, it is probably different on every provider, which would make it hard to change (especially if the provider already provides clean drains while unschedulable).", "commid": "kubernetes_issue_65013", "tokennum": 481}], "negative_passages": []}
{"query_id": "q-en-kubernetes-15d36c83b20b960cab6624bab196ab42b7da2fb7c638168f08ad95a8e476b005", "query": "input           *v1.Node want            bool }{ <ins> {want: false, input: &v1.Node{}}, {want: true, input: &v1.Node{Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionTrue}}}}}, {want: false, input: &v1.Node{Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionFalse}}}}}, {want: true, input: &v1.Node{Spec: v1.NodeSpec{Unschedulable: true}, Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionTrue}}}}}, </ins> {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{}}}}, {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{labelNodeRoleMaster: \"\"}}}}, {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{labelNodeRoleExcludeBalancer: \"\"}}}},", "positive_passages": [{"docid": "doc-en-kubernetes-971dd5a381fee05df7a732c55096ac94f03e1a58bc9cf8aa911af5dca195b6a4", "text": "IIUC, we don't want new pods to land on the tainted/cordoned nodes. In that case, we can place \"NoSchedule\" taint on the nodes. We don't need any tolerations on nginx. This will prevent new instances of nginx from landing on the tainted nodes, but the existing ones will keep running there.\nIssues 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\n/remove-lifecycle stale\nThis just surprised us also. I understand the technical reasons behind it but the command name and associated documentation is misleading. To me it isn't intuitive that the command does not remove compute (pods) but does remove some networking. I would expect cordon to keep new pods from getting scheduled to it and keep it from getting to new services/ELBs/etc. The command would then cause pods to be removed and also take the node out of networking paths. Almost need a new state for a node of that is clearly defined.\nMy main issue is with the docs, and also GKE docs. They should explain this pitfall. After I got aware of the issue I understand why it works as it does. A simple workaround is to taint the nodes you are going to rotate first.\nJust chiming in; We as a GKE customer have today been bitten by this issue in production. The documentation of (in the context of GKE) is not extensive enough so we could be aware of this issue. This should be addressed. Luckily the outage was not severe because we were using the node-by-node approach (and accepted the container churn this would cause). We explicitly took this approach because our previous nodepool upgrade was a total outage also caused by in a different way. (for those interested in our total outage, not related to this issue): Due to the fact that also results in the re-calculating the amount of schedulable nodes and thus scaled the amount of pods in our cluster (in our case: from 110 back to 2) resulting for us in major DNS outage internally.", "commid": "kubernetes_issue_65013", "tokennum": 491}], "negative_passages": []}
{"query_id": "q-en-kubernetes-15d36c83b20b960cab6624bab196ab42b7da2fb7c638168f08ad95a8e476b005", "query": "input           *v1.Node want            bool }{ <ins> {want: false, input: &v1.Node{}}, {want: true, input: &v1.Node{Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionTrue}}}}}, {want: false, input: &v1.Node{Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionFalse}}}}}, {want: true, input: &v1.Node{Spec: v1.NodeSpec{Unschedulable: true}, Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionTrue}}}}}, </ins> {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{}}}}, {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{labelNodeRoleMaster: \"\"}}}}, {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{labelNodeRoleExcludeBalancer: \"\"}}}},", "positive_passages": [{"docid": "doc-en-kubernetes-e282766302629c93406295497fcf5631aa302acfa1c106d008828355db43428f", "text": "Be warned that for a nodepool upgrade can have a lot of unwanted & unexpected side effects.\nIt looks like this happens only to AWS and GCP but not on Azure? Can anyone confirm this? I just tested in both AWS and Azure, and while I see logs like in AWS Kubernetes, I do not see any logs like that in Azure. Is it intended? If so isn't behavior different for each cloud provider? i.e.) cordoning a node in AWS Kubernetes prevents loadbalancer from routing traffic to the affected node but cordoning a node in Azure Kubernetes will still let the loadbalancer route traffic to the affected node. Is it intentional?\nBesides running a test like the above, how would I determine what the behavior is on AWS? I haven't found anything in the node administration docs or the Service that would imply that would shift traffic away from a Pod. In fact, the doc for explicitly states, emphasis mine: If I hadn't come across this Issue due to reports from GKE, I suppose it would only have been a matter of time until we had a high-impact production outage. There's a disconnect between Kubernetes API and the LoadBalancer as to whether Pods running on a 'd node are Ready. From all the docs I've seen, I would expect that either a) would evict Pods over to a Node before setting the instance as , or b) LoadBalancer would not equate with\nHi All, What approaches people using too workaround this? From reading the comments I was hoping to follow the custom taint approach. However, I've noticed executes a cordon making it difficult to drain the node safely with this approach.\nI was lucky in that I experienced this issue while cordoning our testing environment, so we didn't experience a production outage. I think what I'm going to try is the following... it's going to be time-consuming but I think it's the safest bet. Double the number of nodes in the server group to bring online the new nodes first Place a custom taint on each \"legacy\" node As you said, executes a first, so that's a no-go. This is the time-consuming part... for each \"legacy\" node I am going to each pod, and let my PDBs take care of maintaining minimum number of pods. I'm hopeful to try this approach this afternoon, I'll comment back here if I do!", "commid": "kubernetes_issue_65013", "tokennum": 535}], "negative_passages": []}
{"query_id": "q-en-kubernetes-15d36c83b20b960cab6624bab196ab42b7da2fb7c638168f08ad95a8e476b005", "query": "input           *v1.Node want            bool }{ <ins> {want: false, input: &v1.Node{}}, {want: true, input: &v1.Node{Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionTrue}}}}}, {want: false, input: &v1.Node{Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionFalse}}}}}, {want: true, input: &v1.Node{Spec: v1.NodeSpec{Unschedulable: true}, Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionTrue}}}}}, </ins> {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{}}}}, {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{labelNodeRoleMaster: \"\"}}}}, {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{labelNodeRoleExcludeBalancer: \"\"}}}},", "positive_passages": [{"docid": "doc-en-kubernetes-e2e1ecb80d8f290360c9ff319629a62c8ce0008d9f4455b71f27e28e2654d975", "text": "Same as myself! Pity neither of us have a story for Since my comment this morning I've been trying a few approaches, I've ended up with the following: Create a new node pool of equal size in GKE with the upgraded kube version Set the current node pool to not be able to grow beyond its current size - if your using regional nodes this can be annoying, let it bring up new nodes anyways and just have them taint as NoSchedule straight away Taint all old node pool nodes with NoSchedule Go through each old node pool node executing a taint of NoExecute which will cause the node to drain and go onto available nodes i.e. your newly provisioned node pool Ensure your nginx ingress is deployed with tolerances:\nHi All, I'm at a bit of a loss on this one. I've started using custom taints to drain the nodes without getting them removed from the load balancer. My application can hold a HTTP connection open for up to 600 seconds. I'm using nginx as a daemonset, have it configured with a keepalive timeout of 620s, and have . I drain the application first using a taint on each node. I have nginx on each node tolerate this taint and remove it separately at a later point using a different taint. I'm waiting 660s between drains of each node for each taint to ensure nothing is dropped - this all works fine as expected. However, once I kill the node pool or do a kubectl drain after the node is empty of all my stuff plus nginx ingress I start seeing connection issues. I'm a bit lost where to go at debugging them, best guess is something to do with kube-proxy. Can anyone shed some light on this? is there anything on the Google Layer 4 load balancer I'm missing here? Is there some way to correctly drain kube-proxy (or does that even make sense?)\nThis doesn't address the network issues you're seeing, but for those trying to \"roll their own cordon\" using taints: Using a NoExecute taint to \"drain\" the node won't be orderly and won't respect any PDBs. You want to replicate the logic from which tries to do evictions of every pod in a loop. (I realize this is a burdensome idea, but it is also the safest idea.)", "commid": "kubernetes_issue_65013", "tokennum": 515}], "negative_passages": []}
{"query_id": "q-en-kubernetes-15d36c83b20b960cab6624bab196ab42b7da2fb7c638168f08ad95a8e476b005", "query": "input           *v1.Node want            bool }{ <ins> {want: false, input: &v1.Node{}}, {want: true, input: &v1.Node{Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionTrue}}}}}, {want: false, input: &v1.Node{Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionFalse}}}}}, {want: true, input: &v1.Node{Spec: v1.NodeSpec{Unschedulable: true}, Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionTrue}}}}}, </ins> {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{}}}}, {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{labelNodeRoleMaster: \"\"}}}}, {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{labelNodeRoleExcludeBalancer: \"\"}}}},", "positive_passages": [{"docid": "doc-en-kubernetes-11147f85e8d1488f3d03a6c51d3d3b27940ae8960669e7fe9226d15b33379ba5", "text": "To add on to ,: One approach that does not use node taints to force migrate, is to change for the requirements of your app. A change in node selector (e.g. based on instance type), along with a PDB (e.g. 66% / out of 3 replicas availability) should migrate you over fine. This worked out better for me than to drain or add taints to nodes to force push apps out. After the migration completes, you should be able to the nodes, and delete the node pool. FWIW, I too saw connection issues during load testing of a migration, and at least on my setup it was due to using an AWS NLB for the NGINX Ingress Controller. Switching to a classic ELB instead worked, as the NGINX LB Service seems to hit some sort of by my accounts when using NLBs. self-plug: I happened to recently cover a similar topic in a that you may find relevant. Hope it helps\nFor better or worse, for in my case pods that are behind an ingress resource are using node affinity to preferably not schedule them onto the same node. Originally this was done to ensure traffic is balanced across the different nginx ingresses. It has had a positive affect in this case too. Very interesting! Thank you for sharing, I'm not sure that swapping out the Layer4 GCE load balancer is an option here, but you have me thinking. I'm wondering if the TCP keepalive between the LB and nginx is potentially keeping connections open. , and suggest that there may be a 600 second TCP keepalive going on. Will retest doing a sleep of 620s after nginx removal and before node drain.\nHas anyone come up with a strategy to safely move workloads between two pools? Reading this bug, it seems there's no way to reliably do this without causing an outage if you follow the recommendation of + . In my case I'm not using an nginx ingress but services with type . From what I can see, adding to a node causes the Service Controller to consider the node not ready and thus removes it from a target group. This would mean that between and there is no way to add a taint to the node that will leave it in the LB until it's drained.", "commid": "kubernetes_issue_65013", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-15d36c83b20b960cab6624bab196ab42b7da2fb7c638168f08ad95a8e476b005", "query": "input           *v1.Node want            bool }{ <ins> {want: false, input: &v1.Node{}}, {want: true, input: &v1.Node{Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionTrue}}}}}, {want: false, input: &v1.Node{Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionFalse}}}}}, {want: true, input: &v1.Node{Spec: v1.NodeSpec{Unschedulable: true}, Status: v1.NodeStatus{Conditions: []v1.NodeCondition{{Type: v1.NodeReady, Status: v1.ConditionTrue}}}}}, </ins> {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{}}}}, {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{labelNodeRoleMaster: \"\"}}}}, {want: true, input: &v1.Node{Status: validNodeStatus, ObjectMeta: metav1.ObjectMeta{Labels: map[string]string{labelNodeRoleExcludeBalancer: \"\"}}}},", "positive_passages": [{"docid": "doc-en-kubernetes-badabe4a617de62187355502ba8431d2071284df2978e7fc5a1318bb9d8c5a02", "text": "Using doesn't work in this case since the thing I'm draining might just come back and I'm not sure if the service controller will still consider the node ready in that case, but I believe it does. The one strategy I can think of is using labels on the node and an anti-affinity on the pod. You'd then add the label to a node that would push the pod away and then delete the pod. As long as the anti affinity uses this should be safe to do in preparation of a migration. Once the pods have been deleted you could then the nodes.\nIssues 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\n/lifecycle frozen /remove-lifecycle stale /remove-lifecycle rotten\n- As I mentioned in I set up a script that first taints all nodes in the old node pool and then cordon+taint one by one node. If your ingress services are redundant this should work well.\nIs there a plan for cordon behavior to improve on GCP? We have relied on this behavior for years on our AWS clusters and it was very surprising to find out.\nThis is a bug with service load balancers - not something we should document. We defined a label in that cluster admins can use - Unschedulable has nothing to do with SLB inclusion. which is beta and on by default in 1.19.\nDisagree. Unschedulable means \"no new workloads\". It has nothing to do with existing workloads, that is why we have drain (but we should have something in kube that communicates nodes are draining). I have opened to remove this check - we have an alternate approach now and the old logic is wrong (the comment in the code even says \"this is for masters!\" and that's wrong now too as part of the kep).\nA node status condition?\nPossibly, or a taint, or a label. Something concrete.\n/milestone v1.19", "commid": "kubernetes_issue_65013", "tokennum": 469}], "negative_passages": []}
{"query_id": "q-en-kubernetes-15dae06ea01e80b6ea1ffe6de547e9a0febc892f491f07dc6ef87a7dfb5d1503", "query": "hasPVC = true pvc, err := pl.PVCLister.PersistentVolumeClaims(pod.Namespace).Get(pvcName) if err != nil { <del> // The error has already enough context (\"persistentvolumeclaim \"myclaim\" not found\") </del> <ins> // The error usually has already enough context (\"persistentvolumeclaim \"myclaim\" not found\"), // but we can do better for generic ephemeral inline volumes where that situation // is normal directly after creating a pod. if ephemeral && apierrors.IsNotFound(err) { err = fmt.Errorf(\"waiting for ephemeral volume controller to create the persistentvolumeclaim %q\", pvcName) } </ins> return hasPVC, err }", "positive_passages": [{"docid": "doc-en-kubernetes-31eecfa3591815d34ddfcff16c3269edcba1de74efc4a8809ac7fe48d40e0f43", "text": "When using a generic ephemeral volume, the volume binder in kube-scheduler typically processes a new pod before the generic volume controller in kube-controller-manager has a chance to create the PVC. This leads to events for pods using generic ephemeral volumes: It would be nice to suppress these warnings for a short while (duration to be determined) after the pod creation. Later they should be emitted because then they indicate that the generic volume controller isn't working properly. This makes nicer to use.\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig storage", "commid": "kubernetes_issue_104525", "tokennum": 198}], "negative_passages": []}
{"query_id": "q-en-kubernetes-15dcd39f83fd264bc1d2a7e2310be602c712240373efaf9b5bf052fd04ad2176", "query": "Name: \"foo\", }, Data: map[string][]byte{ <del> v1.DockerConfigKey: secretDataNoEmail, </del> <ins> v1.DockerConfigJsonKey: secretDataNoEmail, </ins> }, <del> Type: v1.SecretTypeDockercfg, </del> <ins> Type: v1.SecretTypeDockerConfigJson, </ins> }, expectErr: false, },", "positive_passages": [{"docid": "doc-en-kubernetes-4279a6f285666ec67ce8924ca9393c19176af7de5707dd42a5f4c239ba12ead2", "text": "/kind bug We're having trouble retrieving images from a private registry on DockerCloud. For nearly a year the following has worked flawlessly. Last Friday I pulled down the 1.9.0 CLI (via brew) and since then have not been able to access any image in a private registry on DockerCloud. I've tried this on 10+ brand new clusters created with kops v1.8.0. The Kubernetes cluster version have been 1.8.0, 1.8.4, 1.8.5 and 1.9.0 (which is not supported by kops yet) and all exhibit the same problem. We create the secret as such: And verify it using: Which yields: And create a test service with with these contents: The pod fails immediatly with: I've reviewed the 1.9.0 release notes and nothing jumps out as the root cause. For reference I've tried putting quotes around the value when creating the secret to no avail. I've also tried prefixing the value with , so the full value would read: also to no avail. Environment: Kubernetes version: Cloud provider and installation info: AWS cluster built with Kops 1.8.0, using (to isolate this issue) nearly the default settings for everything.\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI have same problem, and I \"solved\" it creating a docker-registry secret in an old kubernetes version and pasting it on new kubernetes\nI'm recently (I know it worked perfectly about last month) facing issues with as well. For me it ended in a similar manner saying: I was able to confirm, that this is a kubernetes CLI related issue and not end user. Based on and this I was able to create properly formatted auth information looking like this: . When encoding this one-liner using (MacOS workstation) and apply like this works fine and images can be pulled from private repository again.", "commid": "kubernetes_issue_57427", "tokennum": 466}], "negative_passages": []}
{"query_id": "q-en-kubernetes-15dcd39f83fd264bc1d2a7e2310be602c712240373efaf9b5bf052fd04ad2176", "query": "Name: \"foo\", }, Data: map[string][]byte{ <del> v1.DockerConfigKey: secretDataNoEmail, </del> <ins> v1.DockerConfigJsonKey: secretDataNoEmail, </ins> }, <del> Type: v1.SecretTypeDockercfg, </del> <ins> Type: v1.SecretTypeDockerConfigJson, </ins> }, expectErr: false, },", "positive_passages": [{"docid": "doc-en-kubernetes-784638a373a6d25c569537512411337ba05226e31cffa99d23b394dffb534564", "text": "However this breaks all automation and can't be considered as solution Confirmed working with kubectl 1.8.5 and server 1.8.4 (guess 1.7.9 as well)\nlooks like there's an extra \"auths\" element when adding the secret using 1.9 kubectl\nAdded in /assign\nMany thanks for the quick fix on this. Any idea when this might get rolled out? Also, it might be a good idea if this was to the known issue list for v1.9.0. It would have saved us a bunch of time trying to track down the root cause. Just trying to make sure no one else needs to do the same.\nlinking to the \"v1.9.0 known issues\" list\nack, asking Mehdy since he is the patch manager for v1.9 branch. Mehdy, any idea when we can ship 1.9.1 with this fix?\nworkarounds for folks until 1.9.1 is released: if you have a .dockerconfigjson for your private registry already, you can manually specify the type and data key (e.g. ) if you don't have a .dockerconfigjson file already, you can fix up the secret produced by manually: the type from to the data key from to the modified secret with\n1 will be released tomorrow\nI can confirm solution works, thanks so much!\nI am still having issues in 1.9.1. This worked in the 1.8.x branches: results in the following error:\nyou have to remove the gitlab-registry secret before you can apply an update... type is immutable, and the fix in 1.9.1 required changing the type of the secret", "commid": "kubernetes_issue_57427", "tokennum": 370}], "negative_passages": []}
{"query_id": "q-en-kubernetes-164ff27d1ff29eacca5fe5c286baccfff808bc9d8c5fc190c67cd4f5c67bc182", "query": ") func (c *FakeEvictions) Evict(eviction *policy.Eviction) error { <del> action := core.GetActionImpl{} action.Verb = \"post\" </del> <ins> action := core.CreateActionImpl{} action.Verb = \"create\" </ins> action.Namespace = c.ns action.Resource = schema.GroupVersionResource{Group: \"\", Version: \"\", Resource: \"pods\"} action.Subresource = \"eviction\" <ins> action.Object = eviction </ins> _, err := c.Fake.Invokes(action, eviction) return err }", "positive_passages": [{"docid": "doc-en-kubernetes-82d56ce8e3638d906303613bbb222b7918f374f3f5d17197cc57429b2467d07d", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: I'm trying to test Eviction functionality in my program, but running into some inconsistencies around how Evictions are handled in the fake SimpleClient in the client-go testing functionality. Most notably, creates a different from , and both are missing information. issues a with set to (seems to be the only Fake that has this mismatch) on the subresource of . It is missing all the extra information in the eviction, i.e. the . issues a on the subresource of the resource. This is wrong, because aren't created, they're only posted and handled immediately. The Action is missing a Namespace. What you expected to happen: I want to be able to add my own reactor to the SimpleClient to handle this special case. I propose we change both cases to a with set to the . This will ensure it's not handled by the current SimpleClient ObjectReaction, and makes it so users can implement whatever they want themselves. I'd be happy to make a PR with these changes. How to reproduce it (as minimally and precisely as possible): Output: Environment: git revision of : <!-- DO NOT EDIT BELOW THIS LINE --/kind bug\nPOST requests are create requests. It doesn't matter if the object is persisted or not.\n/sig api-machinery\ncc", "commid": "kubernetes_issue_71598", "tokennum": 330}], "negative_passages": []}
{"query_id": "q-en-kubernetes-165d6b7fbdcc3b204497cd802bb5674798ae1a56d7e689c3e6344fc9282f7772", "query": "export PATH=${GOPATH}/bin:${PWD}/third_party/etcd:/usr/local/go/bin:${PATH} <del> go get github.com/tools/godep && godep version go get github.com/jstemmer/go-junit-report </del> <ins> retry go get github.com/tools/godep && godep version retry go get github.com/jstemmer/go-junit-report </ins> # Enable the Go race detector. export KUBE_RACE=-race", "positive_passages": [{"docid": "doc-en-kubernetes-bbec53075a30148d3cbdbc5512f8af7c37c0a3695f84aff12aac6489eaa4282e", "text": "Not sure if this concided with a Jenkins restart.\nNot sure what we can do about this. Retry a few times?\nGitHub seemed to hiccup last night and fail a bunch of our builds. I'm not sure a retry would've helped, unless we kept retrying for many minutes.\nThis is the sort of thing that just happens occasionally. We've seen this a lot in OpenShift CI runs. I'm not sure there's much you can do other than try to avoid external network access (e.g. bake tools into the VM image).\nIt seems to have occurred twice in the last 12h so retry w/ timeout can't hurt?\nIt can't hurt... but it may or may not help depending on the extent of the external issue\nIf the problem is really bad, we could toss it somewhere on GCS?\nLooks like it failed on : We should probably put this in a retry loop or else do something more fancy", "commid": "kubernetes_issue_21887", "tokennum": 212}], "negative_passages": []}
{"query_id": "q-en-kubernetes-16919705cc83937feb1476042ad63ad575007eeab24ab8cd89c82a6941db7463", "query": "// it is not used by Convert() other than storing it in the scope. // Not safe for objects with cyclic references! func (c *Converter) Convert(src, dest interface{}, flags FieldMatchingFlags, meta *Meta) error { <ins> return c.doConversion(src, dest, flags, meta, c.convert) } // DefaultConvert will translate src to dest if it knows how. Both must be pointers. // No conversion func is used. If the default copying mechanism // doesn't work on this type pair, an error will be returned. // Read the comments on the various FieldMatchingFlags constants to understand // what the 'flags' parameter does. // 'meta' is given to allow you to pass information to conversion functions, // it is not used by DefaultConvert() other than storing it in the scope. // Not safe for objects with cyclic references! func (c *Converter) DefaultConvert(src, dest interface{}, flags FieldMatchingFlags, meta *Meta) error { return c.doConversion(src, dest, flags, meta, c.defaultConvert) } type conversionFunc func(sv, dv reflect.Value, scope *scope) error func (c *Converter) doConversion(src, dest interface{}, flags FieldMatchingFlags, meta *Meta, f conversionFunc) error { </ins> dv, err := EnforcePtr(dest) if err != nil { return err", "positive_passages": [{"docid": "doc-en-kubernetes-518f837785f17a5fd9706a6c0a0614adac703d65f6bb6045d79a025795dcb97b", "text": "Files storing latest versions for minors are not updated since infix was to the version string. Example Similar issues can be found in 1.25 and 1.24 builds (last 1.23 build infix so it has not happened there yet): I expect the files to be overwritten with newer version of the build. Manually run build job for one of the minors. No response Not related. Not related. No response No response No response No response\nI believe this may be also responsible for breaking kubemark tests: since they fail due to version mismatch\n/sig release\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority high 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\nThanks for raising the issue! /cc who is working on before\nI assume this will be fixed automatically with the next patches, because then we would compare with . Anyway, I think we should fix that intermediately by manually updating the version markers to match their correct version. I did that now for the bucket\nWe had to update the versions markers again, because those were pointing to two commits earlier and didn't include the Go updates. The latest version markers are: v1.24.12-35+ v1.25.8-37+ v1.26.3-41+\nlatest-1.27 has been affected by this as well. I updated it manually to v1.27.0-9+. See this thread for more details:\n/triage accepted\nThis should be fixed now, closing it. Feel free to reopen if we missed anything.\nThis issue is still present, see this Slack thread for more details: /reopen\nReopened this issue. <detailsIn response to : This issue is still present, see this Slack thread for more details: /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nWe have a similar situation with latest-1.28 which is currently pointing to: . This is one commit before the release commit: ! It's mostly like that the release step didn't update version markers, we should look into this.", "commid": "kubernetes_issue_117115", "tokennum": 486}], "negative_passages": []}
{"query_id": "q-en-kubernetes-16919705cc83937feb1476042ad63ad575007eeab24ab8cd89c82a6941db7463", "query": "// it is not used by Convert() other than storing it in the scope. // Not safe for objects with cyclic references! func (c *Converter) Convert(src, dest interface{}, flags FieldMatchingFlags, meta *Meta) error { <ins> return c.doConversion(src, dest, flags, meta, c.convert) } // DefaultConvert will translate src to dest if it knows how. Both must be pointers. // No conversion func is used. If the default copying mechanism // doesn't work on this type pair, an error will be returned. // Read the comments on the various FieldMatchingFlags constants to understand // what the 'flags' parameter does. // 'meta' is given to allow you to pass information to conversion functions, // it is not used by DefaultConvert() other than storing it in the scope. // Not safe for objects with cyclic references! func (c *Converter) DefaultConvert(src, dest interface{}, flags FieldMatchingFlags, meta *Meta) error { return c.doConversion(src, dest, flags, meta, c.defaultConvert) } type conversionFunc func(sv, dv reflect.Value, scope *scope) error func (c *Converter) doConversion(src, dest interface{}, flags FieldMatchingFlags, meta *Meta, f conversionFunc) error { </ins> dv, err := EnforcePtr(dest) if err != nil { return err", "positive_passages": [{"docid": "doc-en-kubernetes-5a00e106d863b6b2d6ffe122805a64f76a2709c3a46b9a75024b175401623671", "text": "As of now, I'm going to manually update this version marker to unblock 1.28.1 patch release. I'll also take a look into this. /assign\nThe PR that fixed this issue got reverted so this is still relevant: /reopen\nReopened this issue. <detailsIn response to : The PR that fixed this issue got reverted so this is still relevant: /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nWe're running into this issue again with stable-1.29 marker. It's currently pointing to which is It should instead point to I'm going to manually change it following the same procedure as the last time. Version marker updated to\nThis issue is labeled with but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release. You can: Confirm that this issue is still relevant with (org members only) Deprioritize it with or Close this issue with For more details on the triage process, see /remove-triage accepted\n/triage accepted\nSame issue for 1.30, where I had to update the version marker manually again.", "commid": "kubernetes_issue_117115", "tokennum": 278}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1692f3879767da1c316d04a949b5dbb5e65d53d19d8a2524bb8823905a97dc32", "query": "FindBoundSatsified:   false, }, eventReason: \"FailedScheduling\", <del> expectError: makePredicateError(\"1 VolumeBindingNoMatch, 1 VolumeNodeAffinityConflict\"), </del> <ins> expectError: makePredicateError(\"1 node(s) didn't find available persistent volumes to bind, 1 node(s) had volume node affinity conflict\"), </ins> }, \"unbound,found-matches\": { volumeBinderConfig: &persistentvolume.FakeVolumeBinderConfig{", "positive_passages": [{"docid": "doc-en-kubernetes-10c13016eb5239afc7a330cfdab91dbf78232a49f2993f71669df735dbb939e1", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature The is not user friendly. There has been to make it better, but we still print in the pending message. We should change these errors to a more human readable message. For example, should be changed to something like . /sig scheduling", "commid": "kubernetes_issue_58546", "tokennum": 91}], "negative_passages": []}
{"query_id": "q-en-kubernetes-16a60bdd0ab6ada6bbe9a26d79c3fcd68ab36716a4aa2aec0b0bd67d4f9c1221", "query": "} // localhostCert was generated from crypto/tls/generate_cert.go with the following command: <del> //     go run generate_cert.go  --rsa-bits 512 --host 127.0.0.1,::1,example.com --ca --start-date \"Jan 1 00:00:00 1970\" --duration=1000000h </del> <ins> //     go run generate_cert.go  --rsa-bits 1024 --host 127.0.0.1,::1,example.com --ca --start-date \"Jan 1 00:00:00 1970\" --duration=1000000h </ins> var localhostCert = []byte(`-----BEGIN CERTIFICATE----- <del> MIIBjzCCATmgAwIBAgIRAKpi2WmTcFrVjxrl5n5YDUEwDQYJKoZIhvcNAQELBQAw EjEQMA4GA1UEChMHQWNtZSBDbzAgFw03MDAxMDEwMDAwMDBaGA8yMDg0MDEyOTE2 MDAwMFowEjEQMA4GA1UEChMHQWNtZSBDbzBcMA0GCSqGSIb3DQEBAQUAA0sAMEgC QQC9fEbRszP3t14Gr4oahV7zFObBI4TfA5i7YnlMXeLinb7MnvT4bkfOJzE6zktn 59zP7UiHs3l4YOuqrjiwM413AgMBAAGjaDBmMA4GA1UdDwEB/wQEAwICpDATBgNV HSUEDDAKBggrBgEFBQcDATAPBgNVHRMBAf8EBTADAQH/MC4GA1UdEQQnMCWCC2V4 YW1wbGUuY29thwR/AAABhxAAAAAAAAAAAAAAAAAAAAABMA0GCSqGSIb3DQEBCwUA A0EAUsVE6KMnza/ZbodLlyeMzdo7EM/5nb5ywyOxgIOCf0OOLHsPS9ueGLQX9HEG //yjTXuhNcUugExIjM/AIwAZPQ== </del> <ins> MIICEzCCAXygAwIBAgIQRWyrLzhq/urpj7m6uPiMgjANBgkqhkiG9w0BAQsFADAS MRAwDgYDVQQKEwdBY21lIENvMCAXDTcwMDEwMTAwMDAwMFoYDzIwODQwMTI5MTYw MDAwWjASMRAwDgYDVQQKEwdBY21lIENvMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCB iQKBgQDjSYON17r13esbCFoS9l4xTBjqCqw7O4QWuTi7jBJHhU7wJ2TxCHuMO/3L s8PE700nz5ryfnIu/5P/8wGVYOj27ixAWTNFgAyHW62q5i4uCD2VlOQrCZoEOsw6 a0hiDsnam63yW1nc/UK96Y3Yvmb7B6t34tAQ2MigoUeYwoKsPwIDAQABo2gwZjAO BgNVHQ8BAf8EBAMCAqQwEwYDVR0lBAwwCgYIKwYBBQUHAwEwDwYDVR0TAQH/BAUw AwEB/zAuBgNVHREEJzAlggtleGFtcGxlLmNvbYcEfwAAAYcQAAAAAAAAAAAAAAAA AAAAATANBgkqhkiG9w0BAQsFAAOBgQAyyXwM2Up1i7/pLB+crSnH/TJnwhfwSVMZ vAlDgYkGEb8YLc2K+sYqRRiwLuKivDck1xRH6vx3ENxmoX+SOIWVG8amXmqqFifh G+i1AqOdHggw/UCu0uog8OZablbKxnbkBYlnnaOpNC492nnniIqm1ztVygKprMu3 7YCl3ybB5Q== </ins> -----END CERTIFICATE-----`) // localhostKey is the private key for localhostCert. var localhostKey = []byte(`-----BEGIN RSA PRIVATE KEY----- <del> MIIBOwIBAAJBAL18RtGzM/e3XgavihqFXvMU5sEjhN8DmLtieUxd4uKdvsye9Phu R84nMTrOS2fn3M/tSIezeXhg66quOLAzjXcCAwEAAQJBAKcRxH9wuglYLBdI/0OT BLzfWPZCEw1vZmMR2FF1Fm8nkNOVDPleeVGTWoOEcYYlQbpTmkGSxJ6ya+hqRi6x goECIQDx3+X49fwpL6B5qpJIJMyZBSCuMhH4B7JevhGGFENi3wIhAMiNJN5Q3UkL IuSvv03kaPR5XVQ99/UeEetUgGvBcABpAiBJSBzVITIVCGkGc7d+RCf49KTCIklv bGWObufAR8Ni4QIgWpILjW8dkGg8GOUZ0zaNA6Nvt6TIv2UWGJ4v5PoV98kCIQDx rIiZs5QbKdycsv9gQJzwQAogC8o04X3Zz3dsoX+h4A== </del> <ins> MIICdgIBADANBgkqhkiG9w0BAQEFAASCAmAwggJcAgEAAoGBAONJg43XuvXd6xsI WhL2XjFMGOoKrDs7hBa5OLuMEkeFTvAnZPEIe4w7/cuzw8TvTSfPmvJ+ci7/k//z AZVg6PbuLEBZM0WADIdbrarmLi4IPZWU5CsJmgQ6zDprSGIOydqbrfJbWdz9Qr3p jdi+ZvsHq3fi0BDYyKChR5jCgqw/AgMBAAECgYEA1qHVWV0fcI7gNebtKHr++A6k eF8bxdOuKMdAi9r6aA+7O434BKW+Be+g+3wGozJX6gBikhxWN4uid1FDbYzWcJFB i6RHGnHkxm7DifKIXF+cHUAiQhE1W5nwy5aays8B5Kc9eC+a/m9bpxWGRY00tq6x +WhWEUF3fPbGOqnktgECQQD3RmqraDbhvMo3CcghB63TQncafTIiNPmJPXK1uZcy CtGRdb1cF2TJXPO+ukUYQEltG2MP+m7Ds0XL1SsPtGd1AkEA606M/BPdaAs0MZIt u0eH+9Q3Pxp0UqX7Ro2Q4NDWmj6wcqY1E0zeWR4V8XSwbLoiw7GJdqRrL0GSgHQT wPjCYwJAbtCV2T8Y6U0r6kJt969zTOvKaIqWvxGyiriJAbuscHa8uE1lkTHCryMC 8QSVFmso/MZ7PJvkq7tZmiFr7NvSSQJATEwCBtJiHhRT7ibZ0TnWa99ZsopfYVUU bsIEUgElNIpTKDmgSAvKpNbOgqY1dmu8TfvI+MFDR+VZHXGF3jJKxQJAOoMB6VH/ SDNYVyHKU57OA5F8qgnIr+4OWPLtK3khbplpc4kkdBE5OJTDRKXJr+oSZDDe2elI wsDf21paAlthnA== </ins> -----END RSA PRIVATE KEY-----`)", "positive_passages": [{"docid": "doc-en-kubernetes-c0ae7c5a9b926980f7fbe5b2efcf245b830bbe6bb1b2519b4aac2b3a38b48ce6", "text": "Golang 1.13 uses TLS 1.13 by default (opt-out), which introduces RSA-PSS. RSA-PSS does not work with keys that are too small. The issue was uncovered during Fedora mass rebuild which uses Golang 1.13: See /sig api-machinery\nWhat is the failure mode if a smaller key is used?\n/sig auth /sig scalability\n/sub", "commid": "kubernetes_issue_80733", "tokennum": 90}], "negative_passages": []}
{"query_id": "q-en-kubernetes-16b5d66e99ca662616cef7bcb96f1ab6f214d1f1bdabfb8f5000c6ada3737d57", "query": "<del> /* Copyright 2022 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package plugin import ( \"context\" \"errors\" \"fmt\" \"net\" \"sync\" \"time\" \"google.golang.org/grpc\" \"google.golang.org/grpc/connectivity\" \"google.golang.org/grpc/credentials/insecure\" utilversion \"k8s.io/apimachinery/pkg/util/version\" \"k8s.io/klog/v2\" drapb \"k8s.io/kubelet/pkg/apis/dra/v1alpha4\" ) // NewDRAPluginClient returns a wrapper around those gRPC methods of a DRA // driver kubelet plugin which need to be called by kubelet. The wrapper // handles gRPC connection management and logging. Connections are reused // across different NewDRAPluginClient calls. func NewDRAPluginClient(pluginName string) (*Plugin, error) { if pluginName == \"\" { return nil, fmt.Errorf(\"plugin name is empty\") } existingPlugin := draPlugins.get(pluginName) if existingPlugin == nil { return nil, fmt.Errorf(\"plugin name %s not found in the list of registered DRA plugins\", pluginName) } return existingPlugin, nil } type Plugin struct { backgroundCtx context.Context cancel        func(cause error) mutex                   sync.Mutex conn                    *grpc.ClientConn endpoint                string highestSupportedVersion *utilversion.Version clientCallTimeout       time.Duration } func (p *Plugin) getOrCreateGRPCConn() (*grpc.ClientConn, error) { p.mutex.Lock() defer p.mutex.Unlock() if p.conn != nil { return p.conn, nil } ctx := p.backgroundCtx logger := klog.FromContext(ctx) network := \"unix\" logger.V(4).Info(\"Creating new gRPC connection\", \"protocol\", network, \"endpoint\", p.endpoint) // grpc.Dial is deprecated. grpc.NewClient should be used instead. // For now this gets ignored because this function is meant to establish // the connection, with the one second timeout below. Perhaps that // approach should be reconsidered? //nolint:staticcheck conn, err := grpc.Dial( p.endpoint, grpc.WithTransportCredentials(insecure.NewCredentials()), grpc.WithContextDialer(func(ctx context.Context, target string) (net.Conn, error) { return (&net.Dialer{}).DialContext(ctx, network, target) }), ) if err != nil { return nil, err } ctx, cancel := context.WithTimeout(context.Background(), time.Second) defer cancel() if ok := conn.WaitForStateChange(ctx, connectivity.Connecting); !ok { return nil, errors.New(\"timed out waiting for gRPC connection to be ready\") } p.conn = conn return p.conn, nil } func (p *Plugin) NodePrepareResources( ctx context.Context, req *drapb.NodePrepareResourcesRequest, opts ...grpc.CallOption, ) (*drapb.NodePrepareResourcesResponse, error) { logger := klog.FromContext(ctx) logger.V(4).Info(\"Calling NodePrepareResources rpc\", \"request\", req) conn, err := p.getOrCreateGRPCConn() if err != nil { return nil, err } ctx, cancel := context.WithTimeout(ctx, p.clientCallTimeout) defer cancel() nodeClient := drapb.NewNodeClient(conn) response, err := nodeClient.NodePrepareResources(ctx, req) logger.V(4).Info(\"Done calling NodePrepareResources rpc\", \"response\", response, \"err\", err) return response, err } func (p *Plugin) NodeUnprepareResources( ctx context.Context, req *drapb.NodeUnprepareResourcesRequest, opts ...grpc.CallOption, ) (*drapb.NodeUnprepareResourcesResponse, error) { logger := klog.FromContext(ctx) logger.V(4).Info(\"Calling NodeUnprepareResource rpc\", \"request\", req) conn, err := p.getOrCreateGRPCConn() if err != nil { return nil, err } ctx, cancel := context.WithTimeout(ctx, p.clientCallTimeout) defer cancel() nodeClient := drapb.NewNodeClient(conn) response, err := nodeClient.NodeUnprepareResources(ctx, req) logger.V(4).Info(\"Done calling NodeUnprepareResources rpc\", \"response\", response, \"err\", err) return response, err } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-e1c6f7407b346df6fb6212f23a2f930e04198e198bb03b9cff5041967802082d", "text": "The PR above moved everything related to into because that was where most of the code already was, but didn't renamed the files to avoid a larger diff and merge conflicts. Once is merged, we can do the renaming. Code clarity. /sig node\n/triage accepted /priority important-soon\n/assign\na PR can be created for this now.\nwill do", "commid": "kubernetes_issue_125924", "tokennum": 75}], "negative_passages": []}
{"query_id": "q-en-kubernetes-16b9ae08fdff462dca80a1c40ef51684e3a57f3ed002b1d02cd060fb634eb957", "query": "// EnvVarSource represents a source for the value of an EnvVar. message EnvVarSource { <del> // Selects a field of the pod: supports metadata.name, metadata.namespace, metadata.labels, metadata.annotations, </del> <ins> // Selects a field of the pod: supports metadata.name, metadata.namespace, `metadata.labels['<KEY>']`, `metadata.annotations['<KEY>']`, </ins> // spec.nodeName, spec.serviceAccountName, status.hostIP, status.podIP, status.podIPs. // +optional optional ObjectFieldSelector fieldRef = 1;", "positive_passages": [{"docid": "doc-en-kubernetes-5018642be16ab87784521fef6d356d625aa306ba1fff6efc2d4048e42ef1a94c", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: When I tried to create a pod with env variables referencing to annotations: What you expected to happen: Should Proceed. As in It stated is a valid option How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.18.2 Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig docs\nThe API docs need to be updated to indicate the correct supported values. See for correct values\nYou are a lifesaver. Thank you!\n/assign I can try to update the api documentation", "commid": "kubernetes_issue_91165", "tokennum": 215}], "negative_passages": []}
{"query_id": "q-en-kubernetes-16c817bdff953306cd5855fc41716c7ad58048ba0611fde9ff1d46fa2c7b1a7d", "query": "allErrs = append(allErrs, apivalidation.ValidateObjectMeta(&obj.ObjectMeta, false, ValidateThirdPartyResourceName, field.NewPath(\"metadata\"))...) versions := sets.String{} <ins> if len(obj.Versions) == 0 { allErrs = append(allErrs, field.Required(field.NewPath(\"versions\"), \"must specify at least one version\")) } </ins> for ix := range obj.Versions { version := &obj.Versions[ix] if len(version.Name) == 0 {", "positive_passages": [{"docid": "doc-en-kubernetes-65858ef6270e846dbad645a3cdb03be72308acbcbd2d437380bbe522248f5825", "text": "FYI. Currently the field of TPR is marked as which is wrong, actually if you try to create a TPR with empty versions, it will cause api server panic. Versions should be necessary field of TPR, we should validate this somehow.", "commid": "kubernetes_issue_36991", "tokennum": 52}], "negative_passages": []}
{"query_id": "q-en-kubernetes-16f547a4a38d8449d7bfab91d54e990c2a34ecc57f1bbc1e4b39ad5d6f7a4d4d", "query": "} else if exists { glog.Infof(\"Deleting old LB for previously uncached service %s whose endpoint %s doesn't match the service's desired IPs %v\", namespacedName, endpoint, service.Spec.PublicIPs) <del> if err := s.ensureLBDeleted(service); err != nil { </del> <ins> if err := s.balancer.EnsureTCPLoadBalancerDeleted(s.loadBalancerName(service), s.zone.Region); err != nil { </ins> return err, retryable } }", "positive_passages": [{"docid": "doc-en-kubernetes-9fca6378f8b8df6d20b226b62d39deddc0dd6ba6166f0f70fb99239f64c63f5d", "text": "All of our external load balancer tests failed for the better part of a day due to the GCE project that our tests run in hitting its quota for number of target pools. While the target pools have been deleted, the fact that we hit our quota indicates that there must be a leak somewhere, and we need to plug it.\nFor reference, the previous issue was\nCould the leakage be related to ? The quota exhaustion occurred about 22 hrs after that.\nI'd guess that this is due to GetTCPLoadBalancer returning that the load balancer doesn't exist if the forwarding rule is gone, ignoring the target pool, while the service controller considers its deleting done if the cloud provider says that the load balancer doesn't exist. I that logic to the cloud provider because the other implementations of DeleteTCPLoadBalancer weren't/won't be idempotent in the sense of returning ok if the LB doesn't exist. To fix it, we'll either need to make sure all Delete implementations are idempotent and remove the Get call in the controller, or add a method along the lines of IsTCPLoadBalancerDeleted to ask the cloud provider whether all pieces of it have been completely cleaned up. We can't make GetTCPLoadBalancer check that because it's relied on to tell us whether or not the balancer is fully created.\nCopying over my commentary from on why the GKE e2e tests are leaking so many forwarding rules and target pools vs the GCE tests:\nIs there a way for the services test to wait for the service controller to clean up the external resources before finishing (without just doing a sleep)?\nNot without polling GCE directly for whether the resources still exist, although that may be worth it as a workaround. What would be perfect is that clean-up-all-cloud-provider-resources API method that we talked about a couple months ago.\nCan we not perhaps use GCE namespaces or projects as a cheap way of getting this here?\nI don't believe so. We can't use projects due to the fact that projects can't be programatically created (they're intended to be long-lived). I'm not aware of anything along the lines of a GCE namespace other than networks, which won't work because target pools and forwarding rules unfortunately don't seem to be scoped to networks.", "commid": "kubernetes_issue_7753", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-16f547a4a38d8449d7bfab91d54e990c2a34ecc57f1bbc1e4b39ad5d6f7a4d4d", "query": "} else if exists { glog.Infof(\"Deleting old LB for previously uncached service %s whose endpoint %s doesn't match the service's desired IPs %v\", namespacedName, endpoint, service.Spec.PublicIPs) <del> if err := s.ensureLBDeleted(service); err != nil { </del> <ins> if err := s.balancer.EnsureTCPLoadBalancerDeleted(s.loadBalancerName(service), s.zone.Region); err != nil { </ins> return err, retryable } }", "positive_passages": [{"docid": "doc-en-kubernetes-d79b213781c20847fbb47c058c0afaba60ed2f1d9f5b51e77a0a4cda944c52e0", "text": "The target pool leak in the code might be fixed, but the forwarding rule + target pool leak from deleting GKE clusters too quickly is certainly still happening. Reopening for the sake of that half of the issue.\nCan we just add a short sleep to jenkins after the last test has run before it deletes anything?\nYes, you could add a sleep to Ginkgo's AfterEachSuite(): But I'd be concerned about what the upper bound on the sleep period is. Can we get the tests and code in sync with a 1 minute latency here? (e.g. if the controller garbage collects every 60 seconds, then the test only needs to sleep for 60 sec?) And add a BEEG comment to the test's sleep config noting that increasing the sleep time will not improve things, otherwise I'm pretty sure that someone noting flakes in this test in future will think \"maybe I should just increase the sleep period a little bit.\"\nActually, thinking about this a little more, it would be better to put the \"sleep\" logic in the k8s master teardown procedure (i.e. not in the e2e tests or in Jenkins), because otherwise users are going to run into the same resource leakage problems as we are. So master deletion blocks on cleanup of backend cloud resources.\nThere's no way to block master deletion from the master itself. The test framework (or user) just pulls the rug out from underneath the master. See\nRobby's right -- is the real solution to this, but until we have that the best we can do is to have the wait happen elsewhere. The options seem to be: GKE itself Ginkgo's post-testing logic Jenkins' teardown logic I don't like putting it in GKE, because arbitrarily slowing down our API makes for a poor experience for the majority of people that don't still have resources being deleted. I'm not eager to put it in Gingko either, since won't that sleep also take effect whenever anyone runs an e2e test locally against a dev cluster? Putting it in the Jenkins logic makes the most sense to me. I'll send a PR and cc you.\nWe may also want to change the kube-down logic to bring down the master and then nodes in parallel to both speed it up and more closely resemble GKE's teardown logic.\nI've deleted the old forwarding rules and target pools from the project.", "commid": "kubernetes_issue_7753", "tokennum": 530}], "negative_passages": []}
{"query_id": "q-en-kubernetes-16f547a4a38d8449d7bfab91d54e990c2a34ecc57f1bbc1e4b39ad5d6f7a4d4d", "query": "} else if exists { glog.Infof(\"Deleting old LB for previously uncached service %s whose endpoint %s doesn't match the service's desired IPs %v\", namespacedName, endpoint, service.Spec.PublicIPs) <del> if err := s.ensureLBDeleted(service); err != nil { </del> <ins> if err := s.balancer.EnsureTCPLoadBalancerDeleted(s.loadBalancerName(service), s.zone.Region); err != nil { </ins> return err, retryable } }", "positive_passages": [{"docid": "doc-en-kubernetes-6b81898435dc239c0c98669b4836ce5b1423be788127f142aa9eb15c198137cf", "text": "I'll periodically check to see whether anything is leaked after this point. I apologize if the deletions affected any running tests - everything looked to only be from GKE and parallel e2e runs.", "commid": "kubernetes_issue_7753", "tokennum": 42}], "negative_passages": []}
{"query_id": "q-en-kubernetes-170a01e8c577f683cdc2b1f9936d1c1d45a7c50e75b3a1a2e8cbd891f28c87d3", "query": "}, \"../examples/openshift-origin\": { \"openshift-origin-namespace\": &api.Namespace{}, <del> \"openshift-controller\":       &api.ReplicationController{}, </del> <ins> \"openshift-controller\":       &extensions.Deployment{}, </ins> \"openshift-service\":          &api.Service{}, <del> \"etcd-controller\":            &api.ReplicationController{}, </del> <ins> \"etcd-controller\":            &extensions.Deployment{}, </ins> \"etcd-service\":               &api.Service{}, <del> \"etcd-discovery-controller\":  &api.ReplicationController{}, </del> <ins> \"etcd-discovery-controller\":  &extensions.Deployment{}, </ins> \"etcd-discovery-service\":     &api.Service{}, \"secret\":                     nil, },", "positive_passages": [{"docid": "doc-en-kubernetes-970debf69dc4e7e663c051298279ebf93b58654f6c393d8683796c73cb4f1c74", "text": "Kubernetes version (use ): Environment: Cloud provider or hardware configuration: Vagrant OS (e.g. from /etc/os-release): CoreOS Kernel (e.g. ):Install tools: Vagrant & Others: What happened: What you expected to happen: Success How to reproduce it (as minimally and precisely as possible): Followed instructions at Tried to run Received: Anything else do we need to know: From googling, it seems several of the fields in the config are for when using OpenShift origin. But creating the replication controller is a prerequisite to launching OpenShift Origin. Chicken & egg problem.", "commid": "kubernetes_issue_39575", "tokennum": 138}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1719f8b5484dfc629f70b6ffffdab030df7896d0598f7417cff1da05b6362a47", "query": "return time.Since(start).Seconds() } <del> func newPodAndContainerCollector(containerCache kubecontainer.RuntimeCache) *podAndContainerCollector { return &podAndContainerCollector{ containerCache: containerCache, } } // Custom collector for current pod and container counts. type podAndContainerCollector struct { // Cache for accessing information about running containers. containerCache kubecontainer.RuntimeCache } // TODO(vmarmol): Split by source? var ( runningPodCountDesc = prometheus.NewDesc( prometheus.BuildFQName(\"\", KubeletSubsystem, \"running_pod_count\"), \"Number of pods currently running\", nil, nil) runningContainerCountDesc = prometheus.NewDesc( prometheus.BuildFQName(\"\", KubeletSubsystem, \"running_container_count\"), \"Number of containers currently running\", nil, nil) ) // Describe implements Prometheus' Describe method from the Collector interface. It sends all // available descriptions to the provided channel and retunrs once the last description has been sent. func (pc *podAndContainerCollector) Describe(ch chan<- *prometheus.Desc) { ch <- runningPodCountDesc ch <- runningContainerCountDesc } // Collect implements Prometheus' Collect method from the Collector interface. It's called by the Prometheus // registry when collecting metrics. func (pc *podAndContainerCollector) Collect(ch chan<- prometheus.Metric) { runningPods, err := pc.containerCache.GetPods() if err != nil { klog.Warningf(\"Failed to get running container information while collecting metrics: %v\", err) return } runningContainers := 0 for _, p := range runningPods { runningContainers += len(p.Containers) } ch <- prometheus.MustNewConstMetric( runningPodCountDesc, prometheus.GaugeValue, float64(len(runningPods))) ch <- prometheus.MustNewConstMetric( runningContainerCountDesc, prometheus.GaugeValue, float64(runningContainers)) } </del> const configMapAPIPathFmt = \"/api/v1/namespaces/%s/configmaps/%s\" func configLabels(source *corev1.NodeConfigSource) (map[string]string, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-3f173d1022a4408031efac17c8299f04d835794ab8a77d69bb7667b0107a08bf", "text": "Some kubelet metrics use non-standard prometheus collectors unnecessarily. Specifically, we have which can be simple gauges. Since we cannot migrate non-standard prometheus collectors using the internal metrics stability framework, we will need to convert these metrics into standard prometheus variants. /sig instrumentation /assign\nGitHub didn't allow me to assign the following users: solodov. Note that only and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : Some kubelet metrics use non-standard prometheus collectors unnecessarily. Specifically, we have which can be simple gauges. Since we cannot migrate non-standard prometheus collectors using the internal metrics stability framework, we will need to convert these metrics into standard prometheus variants. /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\nrecommends that we generate those metrics in the GenericPLEG during the relist. We can generate the data directly from the pods call there ().\nI would be interested to work on this issue if no one else is working on it currently\nGo for it!\n/assign", "commid": "kubernetes_issue_79286", "tokennum": 282}], "negative_passages": []}
{"query_id": "q-en-kubernetes-173e530b12bfad8383a781f77920c7e34b4f696c4579484cbb87ceb517989970", "query": "} for n := range visitedNamespaces { <ins> if len(o.Namespace) != 0 && n != o.Namespace { continue } </ins> for _, m := range namespacedRESTMappings { if err := p.prune(n, m); err != nil { return fmt.Errorf(\"error pruning namespaced object %v: %v\", m.GroupVersionKind, err)", "positive_passages": [{"docid": "doc-en-kubernetes-55af5a538910186290479e8a37adc800d26766e6d09583162f76a512f0433ab7", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Actually, the parameter depends to all namespaces in the cluster. Filtering is only possible with labels. When running the should only depend on the objects defined in . Why is this needed: A typical use-case is having one repository and namespace per project. When working with declarative objects it should be possible to remove objects and get them pruned like having them described in the respository. This would also help when renaming objects within the repository - which actually needs a manual on the host for the old objects. This even could be a better solution for the problem described in\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig api-machinery\ncc\n/assign\nGitHub didn't allow me to assign the following users: Liujingfang1. Note that only and repo collaborators can be assigned and that 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\nWe have been aware of the issues in prune and we want to improve it. Recently we opened a for improving pruning in . With the proposed solution, the problem from current will be fixed.\nIssues 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\n/remove-lifecycle stale\nIssues 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 .", "commid": "kubernetes_issue_74414", "tokennum": 481}], "negative_passages": []}
{"query_id": "q-en-kubernetes-173e530b12bfad8383a781f77920c7e34b4f696c4579484cbb87ceb517989970", "query": "} for n := range visitedNamespaces { <ins> if len(o.Namespace) != 0 && n != o.Namespace { continue } </ins> for _, m := range namespacedRESTMappings { if err := p.prune(n, m); err != nil { return fmt.Errorf(\"error pruning namespaced object %v: %v\", m.GroupVersionKind, err)", "positive_passages": [{"docid": "doc-en-kubernetes-cb54288fa32d0be96e99fcb10abda15ff9759ea2461e12485115b7e51b53055d", "text": "/lifecycle stale\n/remove-lifecycle stale\nI just deleted a bunch of things in another team's namespace (:blush:). I'd would love to have this feature. I had been using dry-run in another context, but then forgot to check it again after switching contexts.\nIs there any workaround for this? I want to prune resources within a single namespace only.\nWe're still working on improving prune, the current mechanism is broken enough that we don't recommend people us it.\nAlso look like it's been fixed recently.\nCan someone confirm if this is implemented? I tried using this feature with kubectl 1.18.2, which has , yet as with previous versions kubectl it returned an error about pruning a nonNamespaced object of kind Namespace.\nI assume the problem is that \"Namespace\" is a non-namespaced resource, and therefore is not filtered by namespace, so gets deleted by \"prune\". As a workaround it's possible to manually pass a (whitelist of resources allowed to be deleted), and not include \"Namespace\" in it: The list of resources is taken from .\nWould wrapping this loop with achieve the same result?", "commid": "kubernetes_issue_74414", "tokennum": 262}], "negative_passages": []}
{"query_id": "q-en-kubernetes-175a72f7779ce771517cdda80a1df996c7f7b24a80fee8e95ce6259e52892489", "query": "}, { \"ImportPath\": \"github.com/evanphx/json-patch\", <del> \"Rev\": \"ed7cfbae1fffc071f71e068df27bf4f0521402d8\" </del> <ins> \"Rev\": \"94e38aa1586e8a6c8a75770bddf5ff84c48a106b\" </ins> }, { \"ImportPath\": \"github.com/exponent-io/jsonpath\",", "positive_passages": [{"docid": "doc-en-kubernetes-e51351c05e6844b765acf34eaa6a0653d5a4e3452baed4722f32f9c5caa3ece5", "text": "/kind bug What happened: Wrote a that returned a faulty json patch which specified an our of range index (e.G. when there is only one container). This resulted in the apiserver crashing. Stacktrace: What you expected to happen: No crash /sig-api-machinery\n/sig api-machinery\nThis maybe a bug in . I will follow this question.\nThis bug had been fixed in PR: you can checkout it.\nThanks for your comment but I don't think the linked PR fixed the issue, as it got merged almost a year ago and I am running Kube 1.10.1 which does contain that patch but still panics. Just from quickly looking at the code I the linked PR I believe there are two things wrong: The check if the index is valid only happens when a negative index was given should be\nOnce the PR of is merged I will update kubernetes.\n/kind bug", "commid": "kubernetes_issue_64291", "tokennum": 194}], "negative_passages": []}
{"query_id": "q-en-kubernetes-178839fbadd70ae05e0be8a1e599c78cff07dba5aaca0ebf34ca0e9d34509b8b", "query": "if (endpoints.subsets != null && !endpoints.subsets.isEmpty()){ for (Subset subset : endpoints.subsets) { for (Address address : subset.addresses) { <del> list.add(InetAddress.getByName(address.IP)); </del> <ins> list.add(InetAddress.getByName(address.ip)); </ins> } } } <del> } </del> <ins> logger.info(\"Available endpoints: \" + list); } else { logger.warn(\"Endpoints are not available\"); } </ins> } catch (IOException | NoSuchAlgorithmException | KeyManagementException ex) { logger.warn(\"Request to kubernetes apiserver failed\", ex); }", "positive_passages": [{"docid": "doc-en-kubernetes-600b05087b3e5a02baef82de4ad7a72820fecd2de58582bba171390ab13fae8d", "text": "The namespace seems to be hard coded :\ncc:\nThanks. We can improve it after v1 release.", "commid": "kubernetes_issue_10034", "tokennum": 22}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1793ee6282fb7d20c2b74d733976a9cd25f5ad5281bc45ff811888068801da6e", "query": "// +k8s:deepcopy-gen=package <del> package testing </del> <ins> package testing // import \"k8s.io/apimachinery/pkg/runtime/serializer/testing\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-460ceb7b52a1ab0cadc1b29d7eee5cc1013b8d23be9bca0d145119ffcf7b27c6", "text": "Look at one of the directories under (Please don't pick more than one directory for one PR as it will cause issues for reviewers) Find all the files named (example find -name ) See the following link it has a this tells tools how this package needs to be imported. So we should ensure that each has an import Add a description appropriate to the package (similar to the one below) Look through sub directories and see if there are any other important directories that are likely to be used by outside users and add a Why are we doing this? We perfer to use vanity urls instead of directly using to refer to code, so this helps ensure that tools honor our wish. See It would be good to have some package level documentation since these directories under staging/ are meant to be for use by folks outside of kubernetes github org. /good-first-issue\n/kind documentation /sig architecture\ncurrently working my through Not going to use / assign since there could be a number of PRs for this issue.\n/lifecycle active /good-first-issue edit: hmm..\nThis request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /lifecycle active /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\nMay I try on\nIIUC this means that there needs to be a even at the root of the repo? Then how does work? :thinking:\nHi , can I make a PR for this directory ?\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_68231", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1793ee6282fb7d20c2b74d733976a9cd25f5ad5281bc45ff811888068801da6e", "query": "// +k8s:deepcopy-gen=package <del> package testing </del> <ins> package testing // import \"k8s.io/apimachinery/pkg/runtime/serializer/testing\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-5f31f1c27d7198dc83b313154ff681043a8b41e17eb5d3ddf32cd84bc023f931", "text": "/lifecycle rotten\nI guess this is still not done, was supposed to partially fix this issue. /reopen\nReopened this issue. <detailsIn response to : I guess this is still not done, was supposed to partially fix this 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\n/remove-lifecycle rotten /area code-organization", "commid": "kubernetes_issue_68231", "tokennum": 93}], "negative_passages": []}
{"query_id": "q-en-kubernetes-17aac51bd5d3ca94cbd65c689c1358ccf2de4272d82c027b2ed62744eedf1ffa", "query": "\"k8s.io/api/core/v1\" settings \"k8s.io/api/settings/v1alpha1\" <ins> \"k8s.io/apimachinery/pkg/api/errors\" </ins> metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/labels\" \"k8s.io/apimachinery/pkg/watch\"", "positive_passages": [{"docid": "doc-en-kubernetes-fe3f123845ebc52583ef0b18b019ca5c9cf0487720bfc7eeadb38f7ce5aa77c7", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: is consistently failing because of PodPreset feature tests, which require settings/v1alpha1, which is no longer enabled by default What you expected to happen: . How to reproduce it (as minimally and precisely as possible): . Anything else we need to know?: This was caused by and kubernetes/test-infra Environment: . Kubernetes version (use ): . Cloud provider or hardware configuration**: . OS (e.g. from /etc/os-release): . Kernel (e.g. ): . Install tools: . Others: .\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig service-catalog\ndoes the alpha CI job enable alpha API versions?\nfile has \"AllAlpha=true\" Maybe would be better?", "commid": "kubernetes_issue_53079", "tokennum": 293}], "negative_passages": []}
{"query_id": "q-en-kubernetes-17cdb26d723ca314f52fe4a75a9df95812af1228ee59b2991bfe724cbc6d079c", "query": "testCase.modifyRest(storage) } <del> err := storage.tryDefaultValidateServiceClusterIPFields(&testCase.svc) </del> <ins> err := storage.tryDefaultValidateServiceClusterIPFields(testCase.oldSvc, &testCase.svc) </ins> if err != nil && !testCase.expectError { t.Fatalf(\"error %v was not expected\", err) }", "positive_passages": [{"docid": "doc-en-kubernetes-572d0164a11730b1ec949ed970afee14cdb12823b4b7a698fae66a86d82f748e", "text": "1) start with a single stack cluster 2) create a PreferDualStack service 3) configure API server with a 2nd service CIDR 4) Confirm the above service is not dual-stack 5) Add a label to the above service 6) Observe that the service becomes dual-stack I think the correct answer is to have a \"repair loop\" that upgrades (and downgrades!) PreferDualStack Services to match the config. I think this is a GA blocker.\n/triage accepted The current thought is: of type with are special new breed of api objects that I don't think we have any similar precedent in the apis, i could be wrong. Their behavior is tied to how the cluster is configured. Thus their behavior must change as the cluster behavior change. a way the user is stating . If it is cluster then i am good with two ClusterIPs. If it is single stack cluster then I am also good with a single ClusterIP. One can assume that if the user was ok was with getting a additional IP when possible then they must be ok with taking it away when it is no longer possible. Based on the above I believe best course of action is create a new repair loop or piggyback on any of the existing (or better: fix it in rest stack during list and get calls). The new logic takes care of matching to the .\nreproducer and regression test if somebody takes this, feel free to add it\nack - Scheduled to tackle 3rd week of May. Will definitely include that patch.", "commid": "kubernetes_issue_101681", "tokennum": 322}], "negative_passages": []}
{"query_id": "q-en-kubernetes-17d43853462c9a2dedc13b51674f18e4e3f50161ebc610133cd070a23a4ad051", "query": "type multiGroupVersioner struct { target             schema.GroupVersion acceptedGroupKinds []schema.GroupKind <ins> coerce             bool </ins> } // NewMultiGroupVersioner returns the provided group version for any kind that matches one of the provided group kinds.", "positive_passages": [{"docid": "doc-en-kubernetes-7ee140198c665b218e0dfb7e3cd2f2624912887cfcfab5f30828d12c6130aa35", "text": "What happened: Set up a HA cluster with 1.9 and 1.10 API servers (occurs on any apiserver skew boundary where a cohabitating resource's storage version changed groups) Observed errors when modifying workload objects: when modified via the 1.10 server, saw this error in the 1.9 server: when modified via the 1.9 server, saw this error in the 1.10 server: When this error was encountered, all watchers for the resource in question would be dropped and have to re-establish, and the internal watchers feeding the watch cache would drop and re-establish What you expected to happen: Watch events from all supported storage versions are processed correctly How to reproduce it (as minimally and precisely as possible): Start a server from master (for inspectability, store in json). With Create a deployment (e.g. kube-dns in kube-system) Establish a watch via extensions (kubectl get deployments.extensions --all-namespaces -w) Establish a watch via apps (kubectl get --all-namespaces -w) Tail the kube-apiserver log Change the apps/v1 deployment in etcd to extensions/v1beta1: Observer client watches drop and server log errors: Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: /sig api-machinery /cc /priority critical-urgent\nerror is triggered by this returning false: constructed here: the info about expected cohabitating groups is not included in the list of acceptable inputs", "commid": "kubernetes_issue_73478", "tokennum": 368}], "negative_passages": []}
{"query_id": "q-en-kubernetes-17dfa8b63183135c62429b65a3ff62c93a116978ac68f015b9192b8735715001", "query": "// while making decisions. BalanceAttachedNodeVolumes featuregate.Feature = \"BalanceAttachedNodeVolumes\" <del> // owner: @kevtaylor // alpha: v1.14 // beta: v1.15 // ga: v1.17 // // Allow subpath environment variable substitution // Only applicable if the VolumeSubpath feature is also enabled VolumeSubpathEnvExpansion featuregate.Feature = \"VolumeSubpathEnvExpansion\" </del> // owner: @vladimirvivien // alpha: v1.11 // beta:  v1.14", "positive_passages": [{"docid": "doc-en-kubernetes-a166ddd65322b2b4c2d8cbe35891249f4d033568413f3b77fc1f46ee1d1ee8b8", "text": "/kind cleanup /sig storage /sig node Description: Feature gate VolumeSubpathEnvExpansion was GA in 1.17 and is marked for removal in 1.19 Related Issues: GA Release:\n/assign\n/cc", "commid": "kubernetes_issue_89519", "tokennum": 48}], "negative_passages": []}
{"query_id": "q-en-kubernetes-17ff7a75a9db9e4ca6bc70a7ec1d793ea1974b069ef8822fa0a7e286df6efebc", "query": "legacyregistry.MustRegister(CgroupManagerDuration) legacyregistry.MustRegister(PodWorkerStartDuration) legacyregistry.MustRegister(ContainersPerPodCount) <del> legacyregistry.RawMustRegister(newPodAndContainerCollector(containerCache)) </del> legacyregistry.MustRegister(PLEGRelistDuration) legacyregistry.MustRegister(PLEGDiscardEvents) legacyregistry.MustRegister(PLEGRelistInterval)", "positive_passages": [{"docid": "doc-en-kubernetes-3f173d1022a4408031efac17c8299f04d835794ab8a77d69bb7667b0107a08bf", "text": "Some kubelet metrics use non-standard prometheus collectors unnecessarily. Specifically, we have which can be simple gauges. Since we cannot migrate non-standard prometheus collectors using the internal metrics stability framework, we will need to convert these metrics into standard prometheus variants. /sig instrumentation /assign\nGitHub didn't allow me to assign the following users: solodov. Note that only and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : Some kubelet metrics use non-standard prometheus collectors unnecessarily. Specifically, we have which can be simple gauges. Since we cannot migrate non-standard prometheus collectors using the internal metrics stability framework, we will need to convert these metrics into standard prometheus variants. /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\nrecommends that we generate those metrics in the GenericPLEG during the relist. We can generate the data directly from the pods call there ().\nI would be interested to work on this issue if no one else is working on it currently\nGo for it!\n/assign", "commid": "kubernetes_issue_79286", "tokennum": 282}], "negative_passages": []}
{"query_id": "q-en-kubernetes-182e647ca66ce6caa006ed411b395cb25d5be03667e62db9fd654f71dd0eb9a1", "query": "}, } podWithHook := getPodWithHook(\"pod-with-prestop-https-hook\", imageutils.GetPauseImageName(), lifecycle) <ins> // make sure we spawn the test pod on the same node as the webserver. nodeSelection := e2epod.NodeSelection{} e2epod.SetAffinity(&nodeSelection, targetNode) e2epod.SetNodeSelection(&podWithHook.Spec, nodeSelection) </ins> testPodWithHook(podWithHook) }) })", "positive_passages": [{"docid": "doc-en-kubernetes-52b8d78c627cb5787b11bea8197d2293333b64736fbbbb287954cc79911301a5", "text": "release-master-informing: capz-windows-containerd-masterKubernetes e2e suite: [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop https hook properly [MinimumKubeletVersion:1.23] [NodeConformance] Kubernetes e2e suite: [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart https hook properly [MinimumKubeletVersion:1.23] [NodeConformance] Both the tests have been failing during most of the runs since 20th October Kubernetes e2e suite: [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop https hook properly [MinimumKubeletVersion:1.23] [NodeConformance] | 1m6s -- | -- {Oct 31 18:42:02.425: Timed out after 30.001s. Expected <errors.errorString | 0xc0015283b0: { s: \"failed to match regexp \"GET /echo?msg=prestop\" in output \"I1031 18:41:06. 8988 ] Started HTTP server on port 9090nI1031 18:41:06. 8988 ] Started UDP server on port 9091n\"\", } to be nil failed (0xc000f1d000) +0x469 () +0x335} Kubernetes e2e suite: [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart https hook properly [MinimumKubeletVersion:1.23] [NodeConformance] | 5m11s -- | -- {Oct 31 19:05:50.205: timed out while waiting for pod container-lifecycle-hook-6892/pod-with-poststart-https-hook to be running and ready failed (PodClient).CreateSync(0xc000eb5920, 0x22?) +0x94 (0xc0045e8c00) +0x73 () +0x325} No response_ /sig windows cc\n/triage accepted /cc\nThese failures happen also with Kubernetes master + containerd master with Flannel CNI. Testgrid link:\nI figured out why these new failures appear.", "commid": "kubernetes_issue_113479", "tokennum": 564}], "negative_passages": []}
{"query_id": "q-en-kubernetes-182e647ca66ce6caa006ed411b395cb25d5be03667e62db9fd654f71dd0eb9a1", "query": "}, } podWithHook := getPodWithHook(\"pod-with-prestop-https-hook\", imageutils.GetPauseImageName(), lifecycle) <ins> // make sure we spawn the test pod on the same node as the webserver. nodeSelection := e2epod.NodeSelection{} e2epod.SetAffinity(&nodeSelection, targetNode) e2epod.SetNodeSelection(&podWithHook.Spec, nodeSelection) </ins> testPodWithHook(podWithHook) }) })", "positive_passages": [{"docid": "doc-en-kubernetes-468407671b0c3bb4dc0cf6c503c02539c6d31cfb69250c40c5c81f059af779f1", "text": "I've submitted the fix via PR\nThis issue is also affecting 1.25 tests: If possible, we should cherry-pick to the release-1.25 branch once it's merged on master.", "commid": "kubernetes_issue_113479", "tokennum": 42}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1891bcb12c59dcdbb4f92661962a4302ef94bfa3a994f5b20a2032dc03217495", "query": "func main() { klog.InitFlags(nil) if err := app.Run(); err != nil { <del> fmt.Fprintf(os.Stderr, \"error: %vn\", err) </del> os.Exit(1) } <del> os.Exit(0) </del> }", "positive_passages": [{"docid": "doc-en-kubernetes-0b2213d42768c43adcb1b4f15cf67b8722c82d28c3ec9792f5837d41705eb847", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: kubectl version --client=yes command is giving the following error message. Error message is repeated at the start and the end and also containing programming jargon Error: invalid argument \"yes\" for \"--client\" flag: strconv.ParseBool: parsing \"yes\": invalid syntax Examples: Print the client and server versions for the current context kubectl version Options: --client=false: Client version only (no server required). -o, --output='': One of 'yaml' or 'json'. --short=false: Print just the version number. Usage: kubectl version [flags] [options] Use \"kubectl options\" for a list of global command-line options (applies to all commands). invalid argument \"yes\" for \"--client\" flag: strconv.ParseBool: parsing \"yes\": invalid syntax What you expected to happen: The error message can be improved with one of the two variants invalid argument \"yes\" for \"--client\" flag Examples: Print the client and server versions for the current context kubectl version Options: --client=false: Client version only (no server required). -o, --output='': One of 'yaml' or 'json'. --short=false: Print just the version number. Usage: kubectl version [flags] [options] Use \"kubectl options\" for a list of global command-line options (applies to all commands). (or) Invalid argument \"yes\" for \"--client\" flag How to reproduce it (as minimally and precisely as possible): Run the command kubectl version --client=yes Anything else we need to know?: Environment: Kubernetes version (use ): 1.15 Cloud provider or hardware configuration: AWS OS (e.g: ): Amazon Linux Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig cli\nHi Thanks for posting this issue! It turns out that this duplicate output has been in kubectl, and all the other cli cmds, since . This should be fixed by , and hopefully we can cherry pick it back to at least .", "commid": "kubernetes_issue_79454", "tokennum": 560}], "negative_passages": []}
{"query_id": "q-en-kubernetes-18a6bc79f92c14618ddad561f179eb9622f81a9d935449e666c0ea2a1b866867", "query": "glog.V(4).Infof(\"Pod %s deleted.\", pod.Name) if d := dc.getDeploymentForPod(pod); d != nil && d.Spec.Strategy.Type == extensions.RecreateDeploymentStrategyType { // Sync if this Deployment now has no more Pods. <del> rsList, err := dc.getReplicaSetsForDeployment(d) </del> <ins> rsList, err := util.ListReplicaSets(d, util.RsListFromClient(dc.client)) </ins> if err != nil { return }", "positive_passages": [{"docid": "doc-en-kubernetes-2f9c6224492589431ce544bf6b6edab10c3ff06174d612eb6875bebaba0cb87e", "text": "IMO it feels like a bad practice to have mutating resource handlers. The deletePod handler is used for queueing a Recreate deployment once it has no pods running. It should merely look at the ReplicaSets that have owner refs as opposed to using dc.getReplicaSetsForDeployment. The orphaning/adoption dance is already happening inside the reconcilation loop.\nI'd like to work on this\nfeel free to grab it. I can't assign the issue to you so I'll add myself; ping me on the PR when you have one.", "commid": "kubernetes_issue_46933", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-18bb6e3dc3203f351dbdc9bcd95190486b4cd69262f5530f27a34e45ef25a378", "query": "namespace := nsObj.(*api.Namespace) // upon first request to delete, we switch the phase to start namespace termination <del> if namespace.DeletionTimestamp == nil { </del> <ins> if namespace.DeletionTimestamp.IsZero() { </ins> now := util.Now() namespace.DeletionTimestamp = &now namespace.Status.Phase = api.NamespaceTerminating", "positive_passages": [{"docid": "doc-en-kubernetes-859a8b847337ca2cf9879726f3bdb71f0db5559ee2589591ceae612e41f71a1b", "text": "There is a funny subtle behvaiour in get namespaces, in which if i call more than one time, it seems that the removal from Terminating state is accelarated. It seems this might indicate a bug, or maybe its not a bug and the eventual semantics of is a little funny sometimes. in any case, here's what we are seeing : 1) when i delete a namespace the first time usning kubectl, we get a state change to . that is correct, of course. 2) but ... if make the call a second time, then the same status line is immediately removed from . Expected behaviour : A second call to \"kubectl delete ...\" shouldn't have any effect on the timing of removal of a namespace from 'Terminating' state*... So i guess there is some \"eventual consistency\" subtle bug that is resolved by repeated calls to\nsuggests this may not be e bug, maybe its just the etcd eventual deleter thingy.\nLooks to definitely be a bug. The 2nd delete seems to have interrupted the delete process and artifacts (like events) from the namespace still exist in etcd.\ninvestigating...\noops, see the error, will submit a fix.\nI have a fix, but need a test case, will submit PR tomorrow AM", "commid": "kubernetes_issue_6633", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-18ce2dae1dc166c8cc8aa1fe4d00f804dab2b1ade07771ee9bd92ca63f48c5bc", "query": "<del> 2.50 </del> <ins> 2.51 </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-496d6605c1619bb131a3d458a58442cd69b560a8ee63a4aeca6bff6594949a24", "text": "The test image currently uses as its BASEIMAGE: Per , v3.12 reached end of support on 2022-05-01 and is no longer receiving regular bugfixes or security fixes. Current versions of the image appear vulnerable to known CVEs as a result. I don't know if a fix is quite as simple as just The image's base should be an in-support version which is maintained with at least security fixes. No response <details</details<details</details<details</details<details</details<details</details<details</details\n/sig testing\nis like that, but then there are 2 additional steps the changes the image that has been built with the postsubmit job the repo to use the new image More detail in If you want to try, please make sure you are going to follow up with all the steps, you can see other promotions PRs too /help\nThis 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 : is like that, but then there are 2 additional steps promote the image that has been built with the postsubmit job update the repo to use the new image </details\nThank you for this information! Is the manual and of images described in that same document something that you would consider a prerequisite for a proposed change like this? Or is it safe to assume that the automated PR test bucket(s) would provide sufficient test coverage?\nI always trust the CI system\nGood enough for me! Leading off with\n/triage accepted", "commid": "kubernetes_issue_124377", "tokennum": 441}], "negative_passages": []}
{"query_id": "q-en-kubernetes-18d494f48c94c862bad39168282ce62f3aa6063a22fa606b2e67fd37a40c28c8", "query": "} output, err := json.Marshal(agg) require.NoError(t, err) <del> // Content-type is \"aggregated\" discovery format. w.Header().Set(\"Content-Type\", AcceptV2Beta1) </del> <ins> // Content-Type is \"aggregated\" discovery format. Add extra parameter // to ensure we are resilient to these extra parameters. w.Header().Set(\"Content-Type\", AcceptV2Beta1+\"; charset=utf-8\") </ins> w.WriteHeader(http.StatusOK) w.Write(output) }))", "positive_passages": [{"docid": "doc-en-kubernetes-3257ecff81fbc60fa2a8f982346c462089eb7c896f62cce1d4e02ff6df66d913", "text": "We are using (and ) to interact with Kubernetes clusters behind a couple of proxy layers. One of these proxies completes the headers to include character encoding details. This was working fine until recently, when client-go/kubectl have started to fail when interacting with the discovery API. It seems that a recent change has made kubectl more restrictive of the content-type that it expects. I suspect that it is related to this commit: For example, this is an error from a kubectl command: We can of course try to fix it on our end, removing that charset information. However, it is a valid content-type and the way kubectl is handling the content-type there seems like it is relying on implementation details of kube-apiserver (that it does not add metadata to the content-type). I propose to fix this issue in , by properly parsing and handling the content-type.\ncc /kind regression /kind bug /sig api-machinery /priority important-soon looks like the switch statement in downloadLegacy() needs to be more tolerant of the variety of content-types it can get from a server (including text/plain or no content-type if old servers could have returned that...)\n/transfer kubernetes/kubernetes\nSomething went wrong or the destination repo kubernetes/kubernetes/kubernetes does not exist. <detailsIn response to : /transfer kubernetes/kubernetes 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\n/transfer kubernetes\nYep, the string comparison for the content-type is flimsy, let's address that. Thanks for the report!\n/assign\n/triage accepted\n/cc\nThe fix is being cherry-picked back to: : :", "commid": "kubernetes_issue_117562", "tokennum": 408}], "negative_passages": []}
{"query_id": "q-en-kubernetes-18dad9d8c15f9d18fa999f23cf91d4e1a49c247d6cab2f6e7abefdc33cc34b22", "query": "expectedErrMsg:      fmt.Errorf(\"getError\"), }, { <del> name:                \"NodeAddresses should report error if VMSS instanceID is invalid\", nodeName:            \"vm123456\", metadataName:        \"vmss_$123\", vmType:              vmTypeVMSS, useInstanceMetadata: true, expectedErrMsg:      fmt.Errorf(\"failed to parse VMSS instanceID %q: strconv.ParseInt: parsing %q: invalid syntax\", \"$123\", \"$123\"), }, { </del> name:                \"NodeAddresses should report error if cloud.vmSet is nil\", nodeName:            \"vm1\", vmType:              vmTypeStandard,", "positive_passages": [{"docid": "doc-en-kubernetes-93c0a615d6725c12b66abb2dead01e17ca700d451119b1467d3edce68f73a013", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: If computer name prefix does not match VMSS name, then Azure cloud provider will use VMSS API instead of using metadata service data. This leads to throttling, because every affected kubelet is making API requests. What you expected to happen: Azure cloud provider should use metadata service data instead of calling VMSS API when instance is current. How to reproduce it (as minimally and precisely as possible): Set computer name prefix of the VMSS to something different than default. You should observe Azure provider making requests to the VMSS API rather than using metadata service, which leads to throttling if you have multiple kubelets with this bug. Anything else we need to know?: This is bug was introduced by - returns false even if instance is current, because it expects node name to match VMSS name + instance id, however node name is derived from the computer-name-prefix which can be different than VMSS name. Node name should be matched against , not against . Environment: Kubernetes version (use ): 1.18.x and higher Cloud provider or hardware configuration: azure /sig cloud-provider\n/sig cloud-provider\n/area provider/azure\nCC\n/remove-sig cloud-provider /sig cloud-provider (trying to remove the label)\n/sig cloud-provider\nThanks for the reporting. Unfortunately, computer name prefix is not included in IMDS, so it can't be used without VMSS API for constructing the NodeName. Would check what could we do to workaround the issue.\nCan you memorize the computer name prefix in the first request to the Azure API and then use it for the isCurrentInstance check?\nopened to fix the issue. Would you like to have a look?\nI can confirm that your change should fix the problem I reported. Do you know if your fix will be to 1.18.x?\nis working on the cherry pick\nThank you for quick fix!", "commid": "kubernetes_issue_92733", "tokennum": 464}], "negative_passages": []}
{"query_id": "q-en-kubernetes-18f9618c778150d76aafd3c190c22bfce615c10766290f1e2040cf7e11c798b1", "query": "// GetOldReplicaSets returns the old replica sets targeted by the given Deployment; get PodList and ReplicaSetList from client interface. // Note that the first set of old replica sets doesn't include the ones with no pods, and the second set of old replica sets include all old replica sets. func GetOldReplicaSets(deployment *extensions.Deployment, c clientset.Interface) ([]*extensions.ReplicaSet, []*extensions.ReplicaSet, error) { <del> rsList, err := ListReplicaSets(deployment, rsListFromClient(c)) </del> <ins> rsList, err := ListReplicaSets(deployment, RsListFromClient(c)) </ins> if err != nil { return nil, nil, err }", "positive_passages": [{"docid": "doc-en-kubernetes-2f9c6224492589431ce544bf6b6edab10c3ff06174d612eb6875bebaba0cb87e", "text": "IMO it feels like a bad practice to have mutating resource handlers. The deletePod handler is used for queueing a Recreate deployment once it has no pods running. It should merely look at the ReplicaSets that have owner refs as opposed to using dc.getReplicaSetsForDeployment. The orphaning/adoption dance is already happening inside the reconcilation loop.\nI'd like to work on this\nfeel free to grab it. I can't assign the issue to you so I'll add myself; ping me on the PR when you have one.", "commid": "kubernetes_issue_46933", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-191b1c6e240deecdaef2959cae94cea9cd35b084c1c95b38d84ba2293a7377ad", "query": "klog.V(3).Infof(\"Pod %q is terminated, but some containers have not been cleaned up: %s\", format.Pod(pod), statusStr) return false } <del> // pod's sandboxes should be deleted if len(runtimeStatus.SandboxStatuses) > 0 { var sandboxStr string for _, sandbox := range runtimeStatus.SandboxStatuses { sandboxStr += fmt.Sprintf(\"%+v \", *sandbox) } klog.V(3).Infof(\"Pod %q is terminated, but some pod sandboxes have not been cleaned up: %s\", format.Pod(pod), sandboxStr) return false } </del> if kl.podVolumesExist(pod.UID) && !kl.keepTerminatedPodVolumes { // We shouldn't delete pods whose volumes have not been cleaned up if we are not keeping terminated pod volumes klog.V(3).Infof(\"Pod %q is terminated, but some volumes have not been cleaned up\", format.Pod(pod))", "positive_passages": [{"docid": "doc-en-kubernetes-59e10ac9f842c5137d16434532387dd09ba10f619a9264b3e368e8bd51bb44b7", "text": "What happened: It's most visible in the test <img width=\"323\" alt=\"Screen Shot 2020-05-20 at 6 09 10 PM\" src=\"https://user-\"It shows up in kind, kube- and kops jobs The regression was introduced somewhere within , possible culprits are: (FYI (FYI (FYI There are more tests affected, just not as prominently (visually inspecting ) [sig-apps] StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications with PVCs [sig-apps] StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance] [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Inline-volume (default fs)] volumes should store data [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data I wasn't sure whether to tag this as kind/regression or not, I'll leave that up to or someone /sig node /sig api-machimery /sig scheduling\nThe label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : What happened: It's most visible in the test (FYI (FYI (FYI StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications with PVCs [sig-apps] StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance] [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Inline-volume (default fs)] volumes should store data [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data /sig api-machimery /sig scheduling 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.", "commid": "kubernetes_issue_91316", "tokennum": 506}], "negative_passages": []}
{"query_id": "q-en-kubernetes-191b1c6e240deecdaef2959cae94cea9cd35b084c1c95b38d84ba2293a7377ad", "query": "klog.V(3).Infof(\"Pod %q is terminated, but some containers have not been cleaned up: %s\", format.Pod(pod), statusStr) return false } <del> // pod's sandboxes should be deleted if len(runtimeStatus.SandboxStatuses) > 0 { var sandboxStr string for _, sandbox := range runtimeStatus.SandboxStatuses { sandboxStr += fmt.Sprintf(\"%+v \", *sandbox) } klog.V(3).Infof(\"Pod %q is terminated, but some pod sandboxes have not been cleaned up: %s\", format.Pod(pod), sandboxStr) return false } </del> if kl.podVolumesExist(pod.UID) && !kl.keepTerminatedPodVolumes { // We shouldn't delete pods whose volumes have not been cleaned up if we are not keeping terminated pod volumes klog.V(3).Infof(\"Pod %q is terminated, but some volumes have not been cleaned up\", format.Pod(pod))", "positive_passages": [{"docid": "doc-en-kubernetes-aa1ca8a6c4f552108d5e4f5627cf5341a0bb7748f7b82e510f647cbc02b0a76b", "text": "</details\n/cc\nwill increase the time for deletion of pod and it should be expected because currently pod is deleted from apiserver before removing the sandbox container but after this fix pod will be deleted from the apiserver only after deleting the sandbox container.\n/remove-sig scheduling doesn't affect scheduling running time at all.\nYeah, is almost definitely the culprit. Last time we changed that code path, it also caused a regression. The degradation in performance is expected, but a 5x slowdown is definitely larger than it should be.\ndo we know if that's because the status used by the path is stale, or if removing sandboxes is actually that slow?\nif there's not a quick fix, should we revert and bring it back in once the root issue is understood?\nI think a revert is appropriate in this case.\nok, I'll open it\nopen at\nI agree with that 5x is something which shouldn't happen and i can take a look on why thats happening and that might require changing the way how the sandbox is currently deleted which is only during GC.", "commid": "kubernetes_issue_91316", "tokennum": 237}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1969e7b0ed97b7dc9507e59561ea2c05aa055a68861018da48e6b8a139c6112e", "query": "} for key, cluster := range config.Clusters { if len(cluster.CertificateAuthorityData) > 0 { <del> cluster.CertificateAuthorityData = redactedBytes </del> <ins> cluster.CertificateAuthorityData = dataOmittedBytes </ins> } config.Clusters[key] = cluster }", "positive_passages": [{"docid": "doc-en-kubernetes-397ec6d3ebe6b2748109f44339689e34d7c15d3a74b9e08d5b86ed108288f149", "text": "Is this a BUG REPORT or FEATURE REQUEST?: What happened: shows: The use of \"REDACTED\" for a CA here is misleading, since it's a public certificate that is not a secret. What you expected to happen: I expected to see the full CA in pem format (like when you cat ) or something like \"SUPPRESSED\" or \"TRUNCATED\" How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Nope Environment: Kubernetes version (use ):Cloud provider or hardware configuration:OS (e.g. from /etc/os-release):Kernel (e.g. ):\n(for thoughts)\nReiterating the mentions to trigger a notification: <detailsIn response to : (for thoughts) 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\nuse you can see the complete certificate authority data\nHey Thank you - I have tracking that . The point of this issue is that at best it's a bad UX; at worst it's a miseducation on pki. \"REDACTED\" isn't the right word here\nIf there are multiple clusters displaying certificates, the configuration will be too long, so this switch is turned off by default. But we can add an example to help use. thanks\nHey I don't personally view truncation the responsibility of the CLI... users can pipe things to a pager if they really care. That being said, I'm not concerned about the length. The issue is purely about the word choice of \"REDACTED\". The term means: The use of the term \"REDACTED\" in the output implies that a CA public key is remove for security when (as you've pointed out) it is removed for truncation. Truncation and redaction are fundamentally different things, and k8s is misusing the word redacted for this use case.\nNot quite a bug, but I think you're right a better term could be used there as it is a public key, not a private key. /remove-kind bug\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close.", "commid": "kubernetes_issue_61573", "tokennum": 495}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1969e7b0ed97b7dc9507e59561ea2c05aa055a68861018da48e6b8a139c6112e", "query": "} for key, cluster := range config.Clusters { if len(cluster.CertificateAuthorityData) > 0 { <del> cluster.CertificateAuthorityData = redactedBytes </del> <ins> cluster.CertificateAuthorityData = dataOmittedBytes </ins> } config.Clusters[key] = cluster }", "positive_passages": [{"docid": "doc-en-kubernetes-be8602378a7d778cfbc76bff14bb786f501b2719d8c237c227cdd36827d468ae", "text": "If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale I'm not sure what I need to do here. This was marked as a feature. Do you need something more from me?\nWe are waiting for someone to fix this.\n/remove-good-first-issue I don't think this fits our definition of a :\nSo I have to keep replying to the comment bot every 30 days so it doesn't get auto-closed? That feels... odd\nthanks for the education :) unfortunately other issues are higher priority and no one has stepped up to fix this. The autocloser is a form of bug bankruptcy that keeps our issue load in check. The contribex special interest group is definitely open to feedback on the bot.\nThe biggest hurdle in this is that Kubernetes is using some base64 trickery to display the string (basically setting the certificate data to the decoded bytes from ). We can change this to or but not (it has to be a valid base64 encoded string). I tried exploring multiple options for the text, but I couldn't find a suitable one. Given that we already print the user tokens and other credentials this is a bit weird. Should we redact those too? Is it okay if we print the CA certificate instead of truncating it?\nI can't help but laugh at: I'm not wed to any particular name. I also have no problem displaying the entire certificate. The crux of the issue is that a CA public key is not secret or sensitive. It's a public key\nI agree. The issue is with the constraints imposed by how this is implemented currently. I tried to come up with a suitable string (given the constraint) and couldn't find anything acceptable... The only suitable option that worked for me is . I personally prefer to print the CA certificate since we are already printing user tokens and client certs that are actual secrets.\nI agree. Who do we need to get in agreement that printing the full CA is the best path forward?\nthe data is not omitted for security purposes, but to make the output more readable. see REDACTED is misleading... it should probably be \"elided\" or \"...\"\nyou can run to view full content\nthat's the crux of this issue - REDACTED is misleading.", "commid": "kubernetes_issue_61573", "tokennum": 520}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1969e7b0ed97b7dc9507e59561ea2c05aa055a68861018da48e6b8a139c6112e", "query": "} for key, cluster := range config.Clusters { if len(cluster.CertificateAuthorityData) > 0 { <del> cluster.CertificateAuthorityData = redactedBytes </del> <ins> cluster.CertificateAuthorityData = dataOmittedBytes </ins> } config.Clusters[key] = cluster }", "positive_passages": [{"docid": "doc-en-kubernetes-0c20cfda2a4143b97ca34085e4ba4933a2256b4cc12b09ed01e77387d3b1e642", "text": "However, pointed out that other \"long\" fields are still completely printed in plain text such as client certs, so I think we need to revisit the \"readability\" argument. What do you think?\nthey are not... client cert/key are elided in the same way for the same reason: something like \"++data+omitted++\" could be better If the intent of config view without --raw specified is to be readable (which it currently is), printing many extremely long fields isn't great\nHmm what about: I'm pretty sure that would give us a valid b64 string (8+12=20%4=0) and it would subtly hint that the data isn't a secret.\nOnly valid characters are . And adding a prefix from the certificate only complicates things. is a suitable usable option. I'll submit a PR to continue the discussion there.", "commid": "kubernetes_issue_61573", "tokennum": 195}], "negative_passages": []}
{"query_id": "q-en-kubernetes-197132e8ca758b376e4c8ad202116a2717dba5c6fa7530881349fe5b48d82385", "query": "} return result, autorest.DetailedError{ StatusCode: http.StatusNotFound, <del> Message:    \"Not such PIP\", </del> <ins> Message:    \"No such PIP\", } } func (fAPC *fakeAzurePIPClient) GetVirtualMachineScaleSetPublicIPAddress(ctx context.Context, resourceGroupName string, virtualMachineScaleSetName string, virtualmachineIndex string, networkInterfaceName string, IPConfigurationName string, publicIPAddressName string, expand string) (result network.PublicIPAddress, err error) { fAPC.mutex.Lock() defer fAPC.mutex.Unlock() if _, ok := fAPC.FakeStore[resourceGroupName]; ok { if entity, ok := fAPC.FakeStore[resourceGroupName][publicIPAddressName]; ok { return entity, nil } } return result, autorest.DetailedError{ StatusCode: http.StatusNotFound, Message:    \"No such PIP\", </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-c62a800befd6b705c74ea2036c66907711f830c03e53ca86df0e2014d6541d16", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Node external IP of azure VMSS cannot be obtained when cloud-controller-manager is enabled. Corresponding logs are shown as follows:\n/sig azure\n/milestone v1.16", "commid": "kubernetes_issue_80014", "tokennum": 92}], "negative_passages": []}
{"query_id": "q-en-kubernetes-199b3fc25acc1ed338c0af7da4af87e80e87ca5992cde2d772a033f524a0375f", "query": "oldPVC.Status.Conditions = nil newPVC.Status.Conditions = nil <ins> // TODO(apelisse): We don't have a good mechanism to // verify that only the things that should have changed // have changed. Ignore it for now. oldPVC.ObjectMeta.ManagedFields = nil newPVC.ObjectMeta.ManagedFields = nil </ins> // ensure no metadata changed. nodes should not be able to relabel, add finalizers/owners, etc if !apiequality.Semantic.DeepEqual(oldPVC, newPVC) { return admission.NewForbidden(a, fmt.Errorf(\"node %q is not allowed to update fields other than status.capacity and status.conditions: %v\", nodeName, diff.ObjectReflectDiff(oldPVC, newPVC)))", "positive_passages": [{"docid": "doc-en-kubernetes-2c5e5762130beb36422dea9bedde0f0f5452416204c98eb7971e6661a493007b", "text": "Alpha environment tests are failing - The root cause of the tests failing in alpha environment appears to be: So basically kubelet is not allowed to update PVC. Which is weird. Need to investigate further. Also for multizone environment - This line looks weird from e2e: So the deployment is straight up not getting started. /sig storage /assign\nFor multizone failure it looks like the pod has a node selector that conflicts with the zone where the PV was provisioned\nI think failures on alpha cluster is related to generated api code: Obviously none of the PVC patch code sets this stuff and yet is showing up in object diff. I am wondering why. cc\n/wg apply /cc\nIt looks like we may have to reset field before comparing PVCs for admitting them as well.\nYeah, server side apply has an alpha feature to kube-apiserver that allows to track ownership of fields. This is what you see in the managedFields field. It\u2019s automatically when objects are modified. If you want to compare your object against a staticly compiled expected object, you should be emptying/setting the managedField to nil.\nthis is the code in question: Thing is, we don't actually want the kubelet taking ownership of any fields other than the one it changed. If we nil out the managed field for the comparison, that allows the kubelet to mess with managedFields in any way it wants to\ncan you pick this up to fix failure in alpha clusters? Reading last comment - it doesn't seem like a storage issue.\n/unassign /assign\n/milestone v1.14 We're entering and this looks relevant to the 1.14 release. Please if I am incorrect\nWe don't have a good way to do what is suggesting now, so I suspect we will have to default to ignore this field specifically when comparing (by setting it to null on both sides), at least for now.\nwill you be able to submit a PR to fix this?\nAs per /remove-sig storage /sig api-machinery\nSure, I'll try to send a pr this morning", "commid": "kubernetes_issue_74049", "tokennum": 438}], "negative_passages": []}
{"query_id": "q-en-kubernetes-19a64adcee875b6494337655c8a92b74091f56e65df9654ffebb6260adf18134", "query": "//FilenameParam(enforceNamespace, o.Filenames...). FilenameParam(enforceNamespace, &o.FilenameOptions). Flatten() <del> if !o.Local { </del> <ins> if !cmdutil.GetDryRunFlag(cmd) { </ins> builder = builder. SelectorParam(o.Selector). ResourceTypeOrNameArgs(o.All, args...).", "positive_passages": [{"docid": "doc-en-kubernetes-f45c12318e35043c65362c27e361ee13adfef369e183f2b4f0557c11353bd9e9", "text": "from https://k8s-\nReally suspect this is\nThis is putting us into test-go post-commit run is broken\ncc:\nmarked this p0 - if a fix isn't easy let's try to identify what introduced this and revert.\nThis flake on: 2016-10-30 07:19 PDT First instance: : It is flaking frequently, blocking PRs from getting merged, and slowing the submit queue ( at 75%). As on-call, I'm going to try and identify the cluprit and revert. Can use all help in doing so.\ncan you investigate whether your additional tests could cause this (by breaking the deployment of those pods, for instance) , Saad Ali wrote:\nPR looks most suspect to me. It mucked with , and the errors we are seeing in each of the failures is related to : That PR was merged at Oct 30, 2016, 6:18 AM PDT and the first flake in was at Oct 30, 2016, 7:19 AM PDT. Thoughts? CC\nI'm going to initiate a revert of to see if that fixes the issue\nIMO we can just change the flaky test to not get pods but some other resources, such as deployments. We can't really expect to clean up pods immediately.\nI'm going to proceed with revert (). Please feel free to send a follow up PR to handle this more gracefully.\nGoing to leave this opened until we have a few hours of runs with the revert. Want to verify, with some degree of certainty, that the revert took care of this flake.\nWe had 15 green runs of in a row. Considering this flake fixed.", "commid": "kubernetes_issue_35898", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-19c714a61b96a695ee1b6c0f20f47202bd5ea5a7d6f762b3c72f7d312148b918", "query": "// pod setup jobKeyForget  bool restartCounts []int32 <ins> podPhase      v1.PodPhase </ins> // expectations expectedActive          int32", "positive_passages": [{"docid": "doc-en-kubernetes-57b8eab4723f670b6603d9bfb82377ab99cdb5a96c17a18501cc8d4284272435", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: I create a job with initcontainer with restartPolicy : when the initContainer exec failed and it will be restarted, the pod Phase will be pending all the time. but in JobController, the only care the running pod. So this pod will be always restarted. What you expected to happen: when restart count to backoffLimit, the job failed. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig apps\n/assign", "commid": "kubernetes_issue_77644", "tokennum": 220}], "negative_passages": []}
{"query_id": "q-en-kubernetes-19e8b18121bb34cf9dcde34fdec7c6dc05eb61fa35dad516f3a0db662d54e059", "query": "roleRef: kind: Role name: external-attacher-cfg <ins> apiGroup: rbac.authorization.k8s.io </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-3a5f8f6fae70577f1cbce129e8b4c7178012c138aa12442a5305f077f7f55297", "text": "xref: When running the GCE PD CSI Driver against all dynamic provisioning tests from this PR: We encounter the following test failures that need to be resolved: /kind bug /sig storage /cc\nSo it seems that the flag is getting passed all the way through to the driver and it is behaving as we would expect it to in terms of mounting. All the correct commands are being run: When exec-ing into the gce-pd-driver container we can observe that the mounted point is indeed read only. However, when viewed from the host node's perspective the mount is still read write. And therefore since the subpath folder is created by the host, the folder is still being created successfully which fails the test. This behavior suggests that is either not properly propagating the read only option on remount, or not properly remounting at all. I can't figure out how to \"view mount events\" if that's even possible, some help would be appreciated if anyone is aware of how to do that. That would help me narrrow down which of those two options is happening. I have also attempted (from inside the gce pd driver container) to unmount the point (successful) and bind mount it back with the readonly option directly (not using remount trick, still unsuccessful). Suggesting that maybe it is the that is not being mount propagated and not a problem with in particular. /cc\n/assign\n/milestone v1.13 /priority important-soon", "commid": "kubernetes_issue_70549", "tokennum": 314}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1a0624d2331d698504311bc0b090d891ce95a0426f78de843135ce16cf8ccb04", "query": "// Create the controller and run it until we close stop. stop := make(chan struct{}) <ins> defer close(stop) </ins> go framework.New(cfg).Run(stop) // Let's add a few objects to the source. <del> for _, name := range []string{\"a-hello\", \"b-controller\", \"c-framework\"} { </del> <ins> testIDs := []string{\"a-hello\", \"b-controller\", \"c-framework\"} for _, name := range testIDs { </ins> // Note that these pods are not valid-- the fake source doesn't // call validation or anything. source.Add(&api.Pod{ObjectMeta: api.ObjectMeta{Name: name}}) } // Let's wait for the controller to process the things we just added. <del> time.Sleep(500 * time.Millisecond) close(stop) </del> <ins> outputSet := util.StringSet{} for i := 0; i < len(testIDs); i++ { outputSet.Insert(<-deletionCounter) } </ins> <del> outputSetLock.Lock() </del> for _, key := range outputSet.List() { fmt.Println(key) }", "positive_passages": [{"docid": "doc-en-kubernetes-20ba07f969c78351406740c712da4b4d48c539c847c31f97f90729edba71a7c4", "text": "From shippable, I noticed there are several failed cases, for example, E0413 17:34:38. ] watch of *api.Pod ended with: Stop requested --- FAIL: Example (0.61s) got: want: a-hello b-controller c-framework FAIL coverage: 85.9% of statements FAIL 7.652s cc/\nanother example:\nah-- this is a different thing. I will fix this, too.\nI'm seeing this from an unrelated change\nYeah I think that's the one I expected to see.", "commid": "kubernetes_issue_6777", "tokennum": 121}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1a15a652466800ee3347160a78f7acf512eaa8f66472e096167a5f1b47de4541", "query": "\"bytes\" \"fmt\" \"reflect\" <ins> \"regexp\" </ins> \"strings\" \"testing\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-6d76348628664e8e1283688eb2571b9c9ddbeb679dd9d941b90f8deb0741d5d7", "text": "Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see ): No What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): describe psp Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST Kubernetes version (use ): Environment: Doesn't matter. What happened: doesn't show PSP's fields: What you expected to happen: All PSP fields should be shown. How to reproduce it (as minimally and precisely as possible):\nIf you're agree with that than I (or :) ) could implement it.\nyes, improve the describer. Look at the scc describer for formatting.\nany ideas which SIG should own PSP?\nIn this case it should be sig-cli /sig cli\nyeah, this is cli related. I'd go with sig-auth for actual behavior.", "commid": "kubernetes_issue_43757", "tokennum": 222}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1a2885d47956bc0f91ec0053e8b599a14db5dc957b6080196efa2da95f2398df", "query": "// ValidateCSIDriverUpdate validates a CSIDriver. func ValidateCSIDriverUpdate(new, old *storage.CSIDriver) field.ErrorList { allErrs := apivalidation.ValidateObjectMetaUpdate(&new.ObjectMeta, &old.ObjectMeta, field.NewPath(\"metadata\")) <ins> allErrs = append(allErrs, validateCSIDriverSpec(&new.Spec, field.NewPath(\"spec\"))...) </ins> // immutable fields should not be mutated. allErrs = append(allErrs, apimachineryvalidation.ValidateImmutableField(new.Spec.AttachRequired, old.Spec.AttachRequired, field.NewPath(\"spec\", \"attachedRequired\"))...) allErrs = append(allErrs, apimachineryvalidation.ValidateImmutableField(new.Spec.FSGroupPolicy, old.Spec.FSGroupPolicy, field.NewPath(\"spec\", \"fsGroupPolicy\"))...) allErrs = append(allErrs, apimachineryvalidation.ValidateImmutableField(new.Spec.PodInfoOnMount, old.Spec.PodInfoOnMount, field.NewPath(\"spec\", \"podInfoOnMount\"))...) allErrs = append(allErrs, apimachineryvalidation.ValidateImmutableField(new.Spec.VolumeLifecycleModes, old.Spec.VolumeLifecycleModes, field.NewPath(\"spec\", \"volumeLifecycleModes\"))...) <del> allErrs = append(allErrs, apimachineryvalidation.ValidateImmutableField(new.Spec.StorageCapacity, old.Spec.StorageCapacity, field.NewPath(\"spec\", \"storageCapacity\"))...) </del> allErrs = append(allErrs, validateTokenRequests(new.Spec.TokenRequests, field.NewPath(\"spec\", \"tokenRequests\"))...) return allErrs", "positive_passages": [{"docid": "doc-en-kubernetes-cdccab911562ccfffce851739652bcccdbeabc99e62d699c46baa58ef67f3bbe", "text": "Up to 1.21, that field is immutable. That means in practice, a CSIDriver object has to be deleted and then re-created with a different value instead. Mutation via delete/created is unnecessarily complex and as the only consumer of that field (the kube-scheduler) can handle mutation just fine (it'll always ask the informer cache for the current value), it's better to allow mutation.\n/sig storage /assign\nThis is independent of allowing other fields to become mutable, but that might also make sense.\n/triage accepted", "commid": "kubernetes_issue_100089", "tokennum": 125}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1a97b2803ed1429a86cdec69a9bf9abd3cca1bb46931bb32284d42bce3bfea77", "query": "<ins> apiVersion: v1beta3 kind: LimitRange metadata: name: limits spec: limits: - default: cpu: 100m memory: 512Mi type: Container </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-b9774b02da3d7547dcc6ec82c6d1246d6586e28e6fe16ad58f3c28b2558ac905", "text": "Resource quota example is missing readme. Was it once there and was accidentally deleted?\nI wrote something up in Origin repo I need to repurpose for Kubernetes. Sent from my iPhone", "commid": "kubernetes_issue_8749", "tokennum": 41}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1aaa73658753c8d693f1cf0a432d9b92398d7c84e2f9925dbb24e91f889347a2", "query": "\"github.com/google/gofuzz\" ) <ins> func TestConverter_DefaultConvert(t *testing.T) { type A struct { Foo string Baz int } type B struct { Bar string Baz int } c := NewConverter() c.Debug = t c.NameFunc = func(t reflect.Type) string { return \"MyType\" } // Ensure conversion funcs can call DefaultConvert to get default behavior, // then fixup remaining fields manually err := c.Register(func(in *A, out *B, s Scope) error { if err := s.DefaultConvert(in, out, IgnoreMissingFields); err != nil { return err } out.Bar = in.Foo return nil }) if err != nil { t.Fatalf(\"unexpected error %v\", err) } x := A{\"hello, intrepid test reader!\", 3} y := B{} err = c.Convert(&x, &y, 0, nil) if err != nil { t.Fatalf(\"unexpected error %v\", err) } if e, a := x.Foo, y.Bar; e != a { t.Errorf(\"expected %v, got %v\", e, a) } if e, a := x.Baz, y.Baz; e != a { t.Errorf(\"expected %v, got %v\", e, a) } } </ins> func TestConverter_CallsRegisteredFunctions(t *testing.T) { type A struct { Foo string", "positive_passages": [{"docid": "doc-en-kubernetes-518f837785f17a5fd9706a6c0a0614adac703d65f6bb6045d79a025795dcb97b", "text": "Files storing latest versions for minors are not updated since infix was to the version string. Example Similar issues can be found in 1.25 and 1.24 builds (last 1.23 build infix so it has not happened there yet): I expect the files to be overwritten with newer version of the build. Manually run build job for one of the minors. No response Not related. Not related. No response No response No response No response\nI believe this may be also responsible for breaking kubemark tests: since they fail due to version mismatch\n/sig release\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority high 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\nThanks for raising the issue! /cc who is working on before\nI assume this will be fixed automatically with the next patches, because then we would compare with . Anyway, I think we should fix that intermediately by manually updating the version markers to match their correct version. I did that now for the bucket\nWe had to update the versions markers again, because those were pointing to two commits earlier and didn't include the Go updates. The latest version markers are: v1.24.12-35+ v1.25.8-37+ v1.26.3-41+\nlatest-1.27 has been affected by this as well. I updated it manually to v1.27.0-9+. See this thread for more details:\n/triage accepted\nThis should be fixed now, closing it. Feel free to reopen if we missed anything.\nThis issue is still present, see this Slack thread for more details: /reopen\nReopened this issue. <detailsIn response to : This issue is still present, see this Slack thread for more details: /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nWe have a similar situation with latest-1.28 which is currently pointing to: . This is one commit before the release commit: ! It's mostly like that the release step didn't update version markers, we should look into this.", "commid": "kubernetes_issue_117115", "tokennum": 486}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1aaa73658753c8d693f1cf0a432d9b92398d7c84e2f9925dbb24e91f889347a2", "query": "\"github.com/google/gofuzz\" ) <ins> func TestConverter_DefaultConvert(t *testing.T) { type A struct { Foo string Baz int } type B struct { Bar string Baz int } c := NewConverter() c.Debug = t c.NameFunc = func(t reflect.Type) string { return \"MyType\" } // Ensure conversion funcs can call DefaultConvert to get default behavior, // then fixup remaining fields manually err := c.Register(func(in *A, out *B, s Scope) error { if err := s.DefaultConvert(in, out, IgnoreMissingFields); err != nil { return err } out.Bar = in.Foo return nil }) if err != nil { t.Fatalf(\"unexpected error %v\", err) } x := A{\"hello, intrepid test reader!\", 3} y := B{} err = c.Convert(&x, &y, 0, nil) if err != nil { t.Fatalf(\"unexpected error %v\", err) } if e, a := x.Foo, y.Bar; e != a { t.Errorf(\"expected %v, got %v\", e, a) } if e, a := x.Baz, y.Baz; e != a { t.Errorf(\"expected %v, got %v\", e, a) } } </ins> func TestConverter_CallsRegisteredFunctions(t *testing.T) { type A struct { Foo string", "positive_passages": [{"docid": "doc-en-kubernetes-5a00e106d863b6b2d6ffe122805a64f76a2709c3a46b9a75024b175401623671", "text": "As of now, I'm going to manually update this version marker to unblock 1.28.1 patch release. I'll also take a look into this. /assign\nThe PR that fixed this issue got reverted so this is still relevant: /reopen\nReopened this issue. <detailsIn response to : The PR that fixed this issue got reverted so this is still relevant: /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nWe're running into this issue again with stable-1.29 marker. It's currently pointing to which is It should instead point to I'm going to manually change it following the same procedure as the last time. Version marker updated to\nThis issue is labeled with but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release. You can: Confirm that this issue is still relevant with (org members only) Deprioritize it with or Close this issue with For more details on the triage process, see /remove-triage accepted\n/triage accepted\nSame issue for 1.30, where I had to update the version marker manually again.", "commid": "kubernetes_issue_117115", "tokennum": 278}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1ae44cfc5ed424c1af5afdee0b4ac7b8f0492f87a6bdb3e86356c0432a97d5b8", "query": "package remote import ( <ins> \"os\" </ins> \"testing\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-a55cc9cf23a1aa66af6ba96638da8c1361b9b34938bf9fbe2ee98dcb858f1383", "text": "Which jobs are flaking: periodics-kubernetes-bazel-test Which test(s) are flaking: //pkg/kubelet/cri/remote TestVersion Testgrid link: Reason for failure: Error: Received unexpected error: rpc error: code = Unavailable desc = transport is closing panic: runtime error: invalid memory address or nil pointer dereference [recovered] panic: runtime error: invalid memory address or nil pointer dereference Anything else we need to know: To reproduce with stress: go test -race -c ./pkg/kubelet/cri/remote stress - TestVersion Detailed logs\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig testing\nI 'll give it a see and fix it :)\n/assign\n/remove-sig testing SIG node owns their unit tests. SIG testing owns the framework, infrastructure, etc.\n/sig node", "commid": "kubernetes_issue_96950", "tokennum": 277}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1b33fed19f7ef15b640606726c76c5869145649cdb356928e732a50e9f6cfb9c", "query": "\"testing\" \"github.com/GoogleCloudPlatform/kubernetes/pkg/api\" <ins> \"github.com/GoogleCloudPlatform/kubernetes/pkg/util\" </ins> ) func TestNamespaceStrategy(t *testing.T) {", "positive_passages": [{"docid": "doc-en-kubernetes-859a8b847337ca2cf9879726f3bdb71f0db5559ee2589591ceae612e41f71a1b", "text": "There is a funny subtle behvaiour in get namespaces, in which if i call more than one time, it seems that the removal from Terminating state is accelarated. It seems this might indicate a bug, or maybe its not a bug and the eventual semantics of is a little funny sometimes. in any case, here's what we are seeing : 1) when i delete a namespace the first time usning kubectl, we get a state change to . that is correct, of course. 2) but ... if make the call a second time, then the same status line is immediately removed from . Expected behaviour : A second call to \"kubectl delete ...\" shouldn't have any effect on the timing of removal of a namespace from 'Terminating' state*... So i guess there is some \"eventual consistency\" subtle bug that is resolved by repeated calls to\nsuggests this may not be e bug, maybe its just the etcd eventual deleter thingy.\nLooks to definitely be a bug. The 2nd delete seems to have interrupted the delete process and artifacts (like events) from the namespace still exist in etcd.\ninvestigating...\noops, see the error, will submit a fix.\nI have a fix, but need a test case, will submit PR tomorrow AM", "commid": "kubernetes_issue_6633", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1b35d6083434fc17e65853be19d37f2c51553ed9f09eb75daac77301bfae7638", "query": "\"\":            \"ServicePort contains information on service's port.\", \"name\":        \"The name of this port within the service. This must be a DNS_LABEL. All ports within a ServiceSpec must have unique names. When considering the endpoints for a Service, this must match the 'name' field in the EndpointPort. Optional if only one ServicePort is defined on this service.\", \"protocol\":    \"The IP protocol for this port. Supports \"TCP\", \"UDP\", and \"SCTP\". Default is TCP.\", <del> \"appProtocol\": \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and http://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.\", </del> <ins> \"appProtocol\": \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.\", </ins> \"port\":        \"The port that will be exposed by this service.\", \"targetPort\":  \"Number or name of the port to access on the pods targeted by the service. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME. If this is a string, it will be looked up as a named port in the target Pod's container ports. If this is not specified, the value of the 'port' field is used (an identity map). This field is ignored for services with clusterIP=None, and should be omitted or set equal to the 'port' field. More info: https://kubernetes.io/docs/concepts/services-networking/service/#defining-a-service\", \"nodePort\":    \"The port on each node on which this service is exposed when type is NodePort or LoadBalancer.  Usually assigned by the system. If a value is specified, in-range, and not in use it will be used, otherwise the operation will fail.  If not specified, a port will be allocated if this Service requires one.  If this field is specified when creating a Service which does not need it, creation will fail. This field will be wiped when updating a Service to no longer need it (e.g. changing type from NodePort to ClusterIP). More info: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport\",", "positive_passages": [{"docid": "doc-en-kubernetes-3e7e95e6f142ca39e6e3ca0b78c3932bd6cbdfdc898eed9d3ffda27d28f904c7", "text": "We should make the change in PR API reference links to should use HTTPS, not HTTP Visit h and look at the IANA hyperlinks Once this fix is made, a PR to is needed to update the docs (by autogenerating them). This typically would be deferred until the next Kubernetes release. v1.23 not applicable not applicable not applicable not applicable not applicable\n/sig docs\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI opened this issue so that someone else can open a new PR that is equivalent to .\n/retitle Update links to IANA for Service Name and Transport Protocol Port Number Registry\nI would like to work on this issue. May I assign it to myself?\nAnyone - including you - is welcome to work on this issue! So long as you've you can open a pull request to propose a fix.\nThanks\n/assign\nI have made the PR. I hope this works. If not then will be happy to do the necessary changes.\nHad to close the previous PR because of issues, here is the new one I made.", "commid": "kubernetes_issue_106980", "tokennum": 300}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1b997de440c7ec0b7adc683ade11ea5d89693371a6688f05854b6261e5ba8a59", "query": "errCh.SendErrorWithCancel(err, cancel) return } <ins> klog.V(2).InfoS(\"Preemptor Pod preempted victim Pod\", \"preemptor\", klog.KObj(pod), \"victim\", klog.KObj(victim), \"node\", c.Name()) </ins> } fh.EventRecorder().Eventf(victim, pod, v1.EventTypeNormal, \"Preempted\", \"Preempting\", \"Preempted by a pod on node %v\", c.Name()) }", "positive_passages": [{"docid": "doc-en-kubernetes-8b547b0918354692a878225113bae9a07e658398c400349efcb40fc715b52424", "text": "A V(2) log line that includes preemption details (preemptee and preemptor), somewhere here We used to have most of this information as part of the logging for Events. But we removed the preemptor from it as a security measure Logs can have pod names.\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scheduling\n/help\nThis 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 : /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\n/assign\n/help-remove", "commid": "kubernetes_issue_117210", "tokennum": 334}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1bb34495b1d041d5d95e073f59088059ce3d68f35de964beecd12f72511b1d16", "query": "} interval := time.NewTicker(time.Millisecond * 500) defer interval.Stop() <del> done := make(chan bool, 1) </del> <ins> done := make(chan bool) </ins> go func() { time.Sleep(time.Minute * 2) <del> done <- true </del> <ins> close(done) </ins> }() for { select {", "positive_passages": [{"docid": "doc-en-kubernetes-f2910a5a7757744dd88700c551fb3f5fe81db92c4ae532e768f1444ef3ba7b10", "text": "It's at line 111 When the server stopped before timeout, the first goroutine will be block on because the receiver in the second goroutine is not exist. Changing to a buffered one may fix it. no goroutine leaks run related test with leak checker No response <detailsdev </details<detailsunknown </details<details</details<details</details<details</details<details</details\n/sig api-machinery\n/assign /triage accepted\n/cc\nIt should close the channel rather than write to it, that's the easiest fix", "commid": "kubernetes_issue_114070", "tokennum": 125}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1bde64669f769ed37fafcf1b23f4ffbddd943dbca215a117669f3a8962fbefc9", "query": "CLUSTER_DIR?=$(shell pwd)/../../../cluster/ <del> BASEIMAGE=debian:stable-slim TEMP_DIR:=$(shell mktemp -d -t conformanceXXXXXX) </del> <ins> # This is defined in root Makefile, but some build contexts do not refer to them KUBE_BASE_IMAGE_REGISTRY?=k8s.gcr.io ifeq ($(ARCH),amd64) BASEIMAGE?=${KUBE_BASE_IMAGE_REGISTRY}/build-image/debian-base:v2.1.3 else BASEIMAGE?=${KUBE_BASE_IMAGE_REGISTRY}/build-image/debian-base-${ARCH}:v2.1.3 endif RUNNERIMAGE?=gcr.io/distroless/base:latest TEMP_DIR:=$(shell mktemp -d -t conformance-XXXXXX) </ins> all: build", "positive_passages": [{"docid": "doc-en-kubernetes-b6e1a63eb087c1fdbaf4f20789cf4dc422d7eb3a250658bf836af9dda6b010da", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be modified: image to be based on anything other than Docker Hub sourced Why is this needed: With Docker Hub rate-limit policy in-place, we probably should consider removing this dependency to stay in sync with other base images in Kubernetes project. Folks building their own binaries (i.e. with ) might run into this as well. Notes: Prior discussion happened on An idea from is to use the should probably be renamed to avoid confusion with k/release (h/t Currently, is set to , so migrating to may not be a drop-in move However, , so maybe we don't have to start from scratch /sig testing /area conformance /sig release (cc'ing because builds conformance image, though my quick search seem to show there isn't any build pipelines referencing )\n/assign\ndo we still want to do this? I read somewhere that the images built in Google Cloud are being mirrored from Docker Hub, right? This would mean that the API rate limiting will not hit us any more.\nWomp yeah I think DockerHub rate limit is not really the big motivator at this point. However, I think I still want to consider using distroless / go-runner to build and produce conformance image to reduce the noise from CVE scanning done in downstream places. What do you think?\nYeah I think this seems a valuable addition. Are you planning to work on this issue? :)\nI will, though probably won't start until next week. If you have ideas and would like to start early feel free to go for it! Otherwise, I'd be happy to work on and deliver this.\nThank you Wilson! Feel free to ping again if you need any assistance. /assign\n/triage accepted\none thing I need a little help with is to find a reference for using go-runner image that's used everywhere -- the one that I've found is inside conformance directory which seems to be different from what everyone else is using\nWe maintain a go-runner in k/release:\noops, I forgot to get back on this last week -- I meant to say that I need a reference for image which I can use as , so something like on Dockerfile. Is that a possible thing to do?", "commid": "kubernetes_issue_96692", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1bde64669f769ed37fafcf1b23f4ffbddd943dbca215a117669f3a8962fbefc9", "query": "CLUSTER_DIR?=$(shell pwd)/../../../cluster/ <del> BASEIMAGE=debian:stable-slim TEMP_DIR:=$(shell mktemp -d -t conformanceXXXXXX) </del> <ins> # This is defined in root Makefile, but some build contexts do not refer to them KUBE_BASE_IMAGE_REGISTRY?=k8s.gcr.io ifeq ($(ARCH),amd64) BASEIMAGE?=${KUBE_BASE_IMAGE_REGISTRY}/build-image/debian-base:v2.1.3 else BASEIMAGE?=${KUBE_BASE_IMAGE_REGISTRY}/build-image/debian-base-${ARCH}:v2.1.3 endif RUNNERIMAGE?=gcr.io/distroless/base:latest TEMP_DIR:=$(shell mktemp -d -t conformance-XXXXXX) </ins> all: build", "positive_passages": [{"docid": "doc-en-kubernetes-5d193977829c25729bf0cf7e65192f8c845e68df9f65fd9e6c218e9e5725e8bf", "text": "after searching around, I found this -- going to try and use and see how it works :smile:\nStarted a PR -- plenty of things I'd like to be discussed but we should probably have the discussions there\nIssues 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\n/remove-lifecycle stale there is work in progress", "commid": "kubernetes_issue_96692", "tokennum": 118}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1bf0b4f5bc66df537127c15c02c298e9b0d17b745ad0fc2b6f28c1dbac707eae", "query": "\"command\":                  \"Entrypoint array. Not executed within a shell. The container image's ENTRYPOINT is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container's environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. \"$$(VAR_NAME)\" will produce the string literal \"$(VAR_NAME)\". Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell\", \"args\":                     \"Arguments to the entrypoint. The container image's CMD is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container's environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. \"$$(VAR_NAME)\" will produce the string literal \"$(VAR_NAME)\". Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell\", \"workingDir\":               \"Container's working directory. If not specified, the container runtime's default will be used, which might be configured in the container image. Cannot be updated.\", <del> \"ports\":                    \"List of ports to expose from the container. Exposing a port here gives the system additional information about the network connections a container uses, but is primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default \"0.0.0.0\" address inside a container will be accessible from the network. Cannot be updated.\", </del> <ins> \"ports\":                    \"List of ports to expose from the container. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default \"0.0.0.0\" address inside a container will be accessible from the network. Modifying this array with strategic merge patch may corrupt the data. For more information See https://github.com/kubernetes/kubernetes/issues/108255. Cannot be updated.\", </ins> \"envFrom\":                  \"List of sources to populate environment variables in the container. The keys defined within a source must be a C_IDENTIFIER. All invalid keys will be reported as an event when the container is starting. When a key exists in multiple sources, the value associated with the last source will take precedence. Values defined by an Env with a duplicate key will take precedence. Cannot be updated.\", \"env\":                      \"List of environment variables to set in the container. Cannot be updated.\", \"resources\":                \"Compute Resources required by this container. Cannot be updated. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/\",", "positive_passages": [{"docid": "doc-en-kubernetes-754763163ccf179fd132c393411aa2d267e649990c98a81bb38938ec6debc8b2", "text": "The comments in says that : However there are several cases where this is false : When using a Service with a targetPort that references a name in the ports arrays of the pod. Some software (ab)uses this API to get which ports are used (See Although unfixable, my goal is to fix the documentation so other people don't have the same problem). The Azure Load Balancer implementation does this for instance. Some other network/security software might use this information. Also, is it possible to document/reference the above issue in the comment ? Since it is described as informational I expected for the network to work without this information. But it's definitely not the case. Not needed since it's mostly a doc issue. I'm interested in contributing this patch but would like some feedbacks before doing it. :) <details</details<details</details<details</details<details</details<details</details<details</details\n/sig network\n/triage accepted -- thoughts? I believe the doc are due for a refresh.\nI'd take this one. /assign\nI didn't see that you wanted to do this patch, I am very sorry and now I unassign it. /unassign\nNo worries But I'm still not sure where / what to add. Should I only fix the part saying it is only informational ? Is there anything else ? (cc\nThe 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]:\n/remove-lifecycle stale", "commid": "kubernetes_issue_108255", "tokennum": 435}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1c067fcda6fb2f7494ed129125533874bd7515489bb612cfc69c0e71aa58ae40", "query": "} } } <ins> // Providing HardPodAffinitySymmetricWeight in the policy config is the new and preferred way of providing the value. // Give it higher precedence than scheduler CLI configuration when it is provided. if policy.HardPodAffinitySymmetricWeight != 0 { f.hardPodAffinitySymmetricWeight = policy.HardPodAffinitySymmetricWeight } </ins> return f.CreateFromKeys(predicateKeys, priorityKeys, extenders) }", "positive_passages": [{"docid": "doc-en-kubernetes-88466bc637a805045217da94feabbdbd3df0ba52cd0d9904e95d3984c4cf4efa", "text": "( noticed this) HardPodAffinitySymmetricWeight should be in the , not in KubeSchedulerConfiguration If/when fixing this, we need to be careful to do it in a backward-compatilble way.\nDo you mean ? It seems scheduler policy config's args can not passed to FitPredicates; it need to update related interface. For the : mark to be deprecated and set scheduler policy config to HardPodAffinitySymmetricWeight if policy config is empty.\nAre you working on this? if no, I can take it.\n, nop; please go ahead.\n/ / / , When reviewing the PR, there's one question on : the default value of is 1, which means the weight (1) will always add to priorities if term matched (), does it our expectation? And the user has to set it to 0 to disable it. IMO, the default value of should be 0.\nThe value 1 (instead of 0) was chosen so that if you say A must run with B, there is an automatic preference that B should run with A. This seems like reasonable behavior.\nThanks very much; reasonable case to me. But it seems we can not disable it: if set to 0, the default funcs will set it to default (1); similar result to un-set. Anyway, no user complain this now :).", "commid": "kubernetes_issue_43845", "tokennum": 306}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1c159164c2ff532cc41aab424f5fd9a6af30cb8a8dc554b65bd3cf0bb14253bf", "query": "\"time\" \"github.com/golang/glog\" <del> \"github.com/golang/protobuf/proto\" </del> cadvisorfs \"github.com/google/cadvisor/fs\" cadvisorapiv2 \"github.com/google/cadvisor/info/v2\"", "positive_passages": [{"docid": "doc-en-kubernetes-739981494c57aaeb7141fd974134e4440eb950badca5a937fa4552d94ec1af8a", "text": "In , we merged a work around for heapster panic We should get rid of the work around after heapster version is updated. /cc /cc\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close", "commid": "kubernetes_issue_55280", "tokennum": 224}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1c332197dbbae7092624413e87e895876b29a4fe86c7bf95439de2607966e476", "query": "runtimeapi \"k8s.io/kubernetes/pkg/kubelet/api/v1alpha1/runtime\" kubecontainer \"k8s.io/kubernetes/pkg/kubelet/container\" <ins> \"k8s.io/kubernetes/pkg/kubelet/dockertools\" </ins> \"k8s.io/kubernetes/pkg/kubelet/qos\" \"k8s.io/kubernetes/pkg/kubelet/types\" )", "positive_passages": [{"docid": "doc-en-kubernetes-2c477631a31f290ae271a7ca0a83a97399cbf63c4cfd883674b6ddce7387fc19", "text": "What happened: Latest kubelet + Windows Docker version 1.14.0-dev refused to start any containers, error output: \"invalid option: Windows does not support MemorySwap\" How to reproduce it (as minimally and precisely as possible): It's always reproducible with Windows Docker 1.14.0-dev + latest kubelet code base. Anything else do we need to know: It didn't happen for Windows Docker 1.12.2-cs2-ws-beta. The reason behind the issue was because new code was for Windows Docker to check Resources parameters, it doesn't accept a non-zero value for MemorySwap: But kubelet was default to set an unlimited (-1) value. The issue was gone in my setup after applied a private fix to disable MemorySwap by set it to zero for Windows.", "commid": "kubernetes_issue_39003", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1c68c99716640fff1a696b455aa1a2dc954c3b2f61e9da749b79f37697f7f166", "query": "capabilities.Setup(kcfg.AllowPrivileged, privilegedSources, 0) credentialprovider.SetPreferredDockercfgPath(kcfg.RootDirectory) <ins> glog.V(2).Infof(\"Using root directory: %v\", kcfg.RootDirectory) </ins> builder := kcfg.Builder if builder == nil {", "positive_passages": [{"docid": "doc-en-kubernetes-ca640d6faf4286189814f4ad1e01c7d7710200569bbe8ad0dc1acda128b91391", "text": "During the startup process of kubelet, we have Since we have following Code segment 1 and 2 seems dup to me. Am i getting this wrong?", "commid": "kubernetes_issue_25345", "tokennum": 32}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1c6fb4877dd0b569c39092e2e5718983b07eecf78ea1fb646e27c85166341a49", "query": "cluster/addons/fluentd-elasticsearch/es-image cluster/images/etcd/attachlease <ins> cluster/images/etcd/rollback </ins> cmd/gendocs cmd/genkubedocs cmd/genman", "positive_passages": [{"docid": "doc-en-kubernetes-6208b2974deee3332ab4020708350835523c141c61d79e5104e4c7dba961daa5", "text": "ci-kubernetes-e2e-gce-device-plugin-gpu.Overall ci-kubernetes-e2e-gce-device-plugin-gpu.Pod kubetest.Up Intermittently since 02/23 No response No response /sig testing /sig release\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/cc /sig node BTW, would you help to confirm if this is a release cut blocker? We plan to release 1.30.0-alpha.3 on Tuesday 27th February 2024.\nIt passed! Maybe it was some infra issues?\nFailed again. /sig k8s-infra\nMany recreating of nodes in log.\nThis is caused by infra flaky.\nThe problem is\nThis job only runs one test and GPU instances are hard to find we don\u2019t need many of those instances for this job, can we please change this job to only use 2 workers?\n/cc\ntests failed in a recent run. It failed the first time. The Job failure now changed to test case failing today. It failed 4 times in a row.\n/assign\nI launched a test run, logged into the master node and took the kubeconfig and found the following: Relevant bit\nLink some related updates recently on this job.\nThe error above in is weird to me. It said No firmware image found . In successful run before, like (02-27), there are no such failure logs. failure in only kubelet log shows the pod crashed and restarted for many times. No pod log or containerd log.\nAfter , the CI is not always failing now and 4 in a row.\n/close\nClosing 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\n/reopen as keeps flaking\nReopened this issue. <detailsIn response to : /reopen as keeps flaking Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_123491", "tokennum": 511}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1c6fb4877dd0b569c39092e2e5718983b07eecf78ea1fb646e27c85166341a49", "query": "cluster/addons/fluentd-elasticsearch/es-image cluster/images/etcd/attachlease <ins> cluster/images/etcd/rollback </ins> cmd/gendocs cmd/genkubedocs cmd/genman", "positive_passages": [{"docid": "doc-en-kubernetes-93e6b458b8ba607e02020a8718331e5d8d90eb2c8daf949aa5e83a98cf741ed8", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThe problem is different with the failure after the revert. We(release signal team) plan to open an issue for the flake later. (Probably, we should open that one and then close on behalf of that new issue later.)\nFeel free to close it then. However, it failed 3 times out of last 4 runs. It's more a failure than a flake in my opinion. If doesn't help/ not appropriate, I'd suggest to revert installer and image changes\ncomment is clear about the root cause, we have a problem installing the drivers, can you redirect this issue if you think is a bug?\nAfter was merged, there are 6 failure in last 24 run. Tab stats: 8 of 10 (80.0%) recent columns passed (258 of 262 or 98.5% cells) The Flaky rate is lower.", "commid": "kubernetes_issue_123491", "tokennum": 202}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1c7888aa19ca6dcfdc2e964f6ff52b119f3e198434841b1758af69fff91af64f", "query": "return \"\" } <ins> func podID(element interface{}) string { el := element.(*model.Sample) return fmt.Sprintf(\"%s::%s\", el.Metric[\"namespace\"], el.Metric[\"pod\"]) } </ins> func containerID(element interface{}) string { el := element.(*model.Sample) return fmt.Sprintf(\"%s::%s::%s\", el.Metric[\"namespace\"], el.Metric[\"pod\"], el.Metric[\"container\"])", "positive_passages": [{"docid": "doc-en-kubernetes-cef38c378015a3c37c6ee1632d82c03243825979d637fc81c55115a5c8a6f392", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: Which test(s) are failing: Since when has it been failing: Testgrid link: Reason for failure: Anything else we need to know: Introduced in /cc /sig node /assign /milestone v1.20\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_96568", "tokennum": 165}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1cfa3d6b74b9d2949fafb341be3cd4ddbd4a201f56a7d3e48667e2a1e328622a", "query": "if err != nil { return err } <del> stat, err := framework.RunKubectl(namespace, \"create\", \"-f\", adapterURL) </del> <ins> stat, err := framework.RunKubectl(\"\", \"create\", \"-f\", adapterURL) </ins> framework.Logf(stat) return err } <del> func createClusterAdminBinding(namespace string) error { </del> <ins> func createClusterAdminBinding() error { </ins> stdout, stderr, err := framework.RunCmd(\"gcloud\", \"config\", \"get-value\", \"core/account\") if err != nil { framework.Logf(stderr)", "positive_passages": [{"docid": "doc-en-kubernetes-cecee0a132f84dbf6d5783d328e94b49c8666ebba8eef4ded1687e53b0451e97", "text": "/kind failing-test <!-- If this is a flake, please add: /kind flake --/sig autoscaling Looks like it just started happening today (@ 2020-09-15 03:54:19 +0000 UTC) !\ncc the namespace from the provided object \"kube-system\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=kube-system' to perform this operation. the namespace from the provided object \"custom-metrics\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=custom-metrics' to perform this operation. the namespace from the provided object \"custom-metrics\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=custom-metrics' to perform this operation.\nrelated fix:\nNo I don't think that's the fix for this (that is just a little cleanup). Actually I think we have to delete namespace parameter in line : Because before , the will have no actually effect. But now with the change of , it will have namespace : at the end of the command. But the namespace in yaml file is which is different from . We should not have parameter when applying from file because this test didn't have before, right? Related PR:\n/assign", "commid": "kubernetes_issue_94809", "tokennum": 318}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1d0272a813f80cbbe866b4bb182bf1453b5079823f357fc3f392bb7655e2003c", "query": "nominatedPodToNode: make(map[ktypes.UID]string), } } <ins> // MakeNextPodFunc returns a function to retrieve the next pod from a given // scheduling queue func MakeNextPodFunc(queue SchedulingQueue) func() *v1.Pod { return func() *v1.Pod { pod, err := queue.Pop() if err == nil { klog.V(4).Infof(\"About to try and schedule pod %v/%v\", pod.Namespace, pod.Name) return pod } klog.Errorf(\"Error while retrieving next pod from scheduling queue: %v\", err) return nil } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-90b5ca2d1baaaaa2aa124277e8c3fdace970eae885ff81aa4062d924fde9dbb7", "text": "PLEASE COORDINATE WITH SIG-SCHEDULING BEFORE WORKING ON THIS ISSUE. We want to avoid the situation where two people accidentally start work on the same fix. Main tracking issue: The method of is a simple wrapper around . It should be converted into a simple closure instead of being a method. i.e. we should have, (code is in ) /sig scheduling /kind cleanup /help\nI'd like to take this task. /assign /remove-help\nThanks, go for it! :smile:", "commid": "kubernetes_issue_72546", "tokennum": 104}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1d2ba0de50b30199d2062fed9979b7dcb51a8580c218f38d5a6e01b4fd1ced60", "query": "} t.Logf(\"rs._internal.apps -> rs.v1.apps\") <del> data, err := runtime.Encode(extGroup.Codec(), rs) </del> <ins> data, err := runtime.Encode(extCodec, rs) </ins> if err != nil { t.Fatalf(\"unexpected encoding error: %v\", err) }", "positive_passages": [{"docid": "doc-en-kubernetes-fe4a53f9c12ffb58184de5c048a5217a0a9a95660f59883741a14147feb2210e", "text": "Execute make test WHAT=./pkg/api/testing/ And it failed with information: /kind failing-test\n/sig api-machinery\nwhat's the urgency of fixing this? Is it a release blocker?\ni don't see it as a release blocker. but the problem is in client-go, so it's important to get fixed.", "commid": "kubernetes_issue_71369", "tokennum": 78}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1d4069f6348660f69f505c91a1e0245996afe7bb5eb07851958562ec8ccc3160", "query": "return volumetypes.NewOperationContext(eventErr, detailedErr, migrated) } <del> klog.Infof(deviceToDetach.GenerateMsgDetailed(\"UnmountDevice succeeded\", \"\")) </del> <ins> klog.Info(deviceToDetach.GenerateMsgDetailed(\"UnmountDevice succeeded\", \"\")) </ins> // Update actual state of world markDeviceUnmountedErr := actualStateOfWorld.MarkDeviceAsUnmounted(", "positive_passages": [{"docid": "doc-en-kubernetes-d71ca3fa6a0d8529c7a86525f4c578d8692c435e96ab7540a0643bb36519a584", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --I0726 15:05:12. ] UnmountDevice succeeded for volume \"volume-name\" %!(EXTRA string=UnmountDevice succeeded for volume \"volume-name\" (UniqueName: \"fake-plugin/fake-device1\") on node \"mynodename\" ) Here at the same time, simple, detail information is returned and formatting problems are caused. No format error. For example, only datail is returned. Found from running Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others: /good-first-issue\nThis request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! --#### What happened: I0726 15:05:12. ] UnmountDevice succeeded for volume \"volume-name\" %!(EXTRA string=UnmountDevice succeeded for volume \"volume-name\" (UniqueName: \"fake-plugin/fake-device1\") on node \"mynodename\" ) #### What you expected to happen: No format error. For example, only datail is returned. #### How to reproduce it (as minimally and precisely as possible): Found from running Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others: 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\n/triage accepted /sig instrumentation /wg structured-logging\nSeems like caused by , this line still not in structured logging, we need to handle these messages.", "commid": "kubernetes_issue_103907", "tokennum": 533}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1d4069f6348660f69f505c91a1e0245996afe7bb5eb07851958562ec8ccc3160", "query": "return volumetypes.NewOperationContext(eventErr, detailedErr, migrated) } <del> klog.Infof(deviceToDetach.GenerateMsgDetailed(\"UnmountDevice succeeded\", \"\")) </del> <ins> klog.Info(deviceToDetach.GenerateMsgDetailed(\"UnmountDevice succeeded\", \"\")) </ins> // Update actual state of world markDeviceUnmountedErr := actualStateOfWorld.MarkDeviceAsUnmounted(", "positive_passages": [{"docid": "doc-en-kubernetes-c360b40c66141d5646d0351669bbca5e7c3c6ba302e184cee03898eed6d86ac9", "text": "I don\u2019t know if this package will be accepted for structured log migration. It seems that only kubelet is required now.\n/assign\nI think it\u2018s only kubelet required too.\nHi, sorry about that I didn't realize that you assigned yourself to this issue. Hope is helpful for this issue.\nThe 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]:\nThe 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]:\n/cc\nInteresting. I'm running the same test locally: And I'm not finding the same log output issue there. Can anyone else see it on (master)?\nit's quite likely that the source code line changed. Search for \"EXTRA string\" instead.\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue.", "commid": "kubernetes_issue_103907", "tokennum": 501}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1d4069f6348660f69f505c91a1e0245996afe7bb5eb07851958562ec8ccc3160", "query": "return volumetypes.NewOperationContext(eventErr, detailedErr, migrated) } <del> klog.Infof(deviceToDetach.GenerateMsgDetailed(\"UnmountDevice succeeded\", \"\")) </del> <ins> klog.Info(deviceToDetach.GenerateMsgDetailed(\"UnmountDevice succeeded\", \"\")) </ins> // Update actual state of world markDeviceUnmountedErr := actualStateOfWorld.MarkDeviceAsUnmounted(", "positive_passages": [{"docid": "doc-en-kubernetes-ce988bfc6ad2fcc73f6949053dcba493aabc2a4f61d6f09e0644b61d62fb522f", "text": "<detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_103907", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1d80e0084ac27b8e3026e8bead0f21c8acfa62f02e04b37d09577a28e0e1dc6e", "query": "return types.NewErr(\"composited variable %q fails to compile: %v\", a.name, a.result.Error) } <del> v, details, err := a.result.Program.Eval(a.activation) </del> <ins> v, details, err := a.result.Program.ContextEval(a.context, a.activation) </ins> if details == nil { return types.NewErr(\"unable to get evaluation details of variable %q\", a.name) }", "positive_passages": [{"docid": "doc-en-kubernetes-11cf454c594ad6f800f58a0212c358c898b7772cd85a5cbba9749540b6918b99", "text": "In We should be using ConteaxtEval for evaluation. Use ContextEval for cel evaluation n/a No response <details</details<details</details<details</details<details</details<details</details<details</details\n/assign /triage accepted /sig api-machinery", "commid": "kubernetes_issue_121623", "tokennum": 68}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1d865256c98a5104a154aef1c2519977c97a0b9d5a125274c7d6801698316579", "query": "}, }, Command: []string{\"/bin/sh\"}, <del> Args:    []string{\"-c\", \"python ./data_download.py && time -p python ./wide_deep.py --model_type=wide_deep --train_epochs=300 --epochs_between_evals=300 --batch_size=32561\"}, </del> <ins> Args:    []string{\"-c\", \"time -p python ./wide_deep.py --model_type=wide_deep --train_epochs=300 --epochs_between_evals=300 --batch_size=32561\"}, </ins> } containers = append(containers, ctn)", "positive_passages": [{"docid": "doc-en-kubernetes-18a84ca90a3e633f3a3a09fc3ce20a2ee5a77d52c40aa5d987ef95b0afbf9b00", "text": "E2eNode Suite.[sig-node] Node Performance Testing [Serial] [Slow] Run node performance testing with pre-defined workloads TensorFlow workload From the testgrid, it has been 1/2 flaky since the start of history (03/20/2022) and has been failing constantly (0/2) since 04/01/2022 No response /sig node\n/triage accepted /priority important-soon\nThe failing test seems to be expecting GPU on machine and the image seems to be broken. I tried the image manually: Logs:\n/assign as discussed at SIG Node CI meeting, can you please take a look? I see that pod is now running for couple minutes and then stops. I wonder if this is something environment related - maybe pod was evicted or something. I doesn't seem to be able to repro the failure of the pod locally\nGitHub didn't allow me to assign the following users: xmcqueen. 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\nThis is no longer a flake. It has failed every run since the start of June. Locally this test runs perfectly with a legit correct local run of the test suite code, doing the full tensorflow run of 300 epochs. The failure in the testgrid job seems to be fast (173 sec to build and fail, locally its 160 sec before it starts the tensorflow pod). I wonder if there's a blocked port or something from the data initializing python program. It needs access to: . Here's the command it runs: Is it feasible to add debugging code, like a pre-check for that http port? It would be good to at least force it to fail with a meaningful error message.\nNote that HEAD is now at image version 1.2, and it is still failing per . The successful local runs of the test mentioned above used image version 1.2.", "commid": "kubernetes_issue_109295", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1d865256c98a5104a154aef1c2519977c97a0b9d5a125274c7d6801698316579", "query": "}, }, Command: []string{\"/bin/sh\"}, <del> Args:    []string{\"-c\", \"python ./data_download.py && time -p python ./wide_deep.py --model_type=wide_deep --train_epochs=300 --epochs_between_evals=300 --batch_size=32561\"}, </del> <ins> Args:    []string{\"-c\", \"time -p python ./wide_deep.py --model_type=wide_deep --train_epochs=300 --epochs_between_evals=300 --batch_size=32561\"}, </ins> } containers = append(containers, ctn)", "positive_passages": [{"docid": "doc-en-kubernetes-924fdb64dda3a1d51367c5f2ba44327b61b51dcf8cc0ad56f75173d2dbe65d92", "text": "Locally image version 1.1 does produce the cuda/GPU error shown above by :\nMore info is needed to find the RC for this test failure. I've put in a PR to get the test framework to preserve the container logs when the pod fails.\nThe pod logs show that it is timing out on an http connection, and it looks like it's the one where it tries to download the test data set for the tensorflow run. You can see it . Search down to . The data_download script in the image attempts to pull down a dataset from: . That url is live and healthy, so they might be blocking the gcloud.\nThis test depending on that external data doesn't look quite right :/\nI'm discussing this test with sig-testing. I'll post an update later.\nTalked to from sig-testing: he's contacting the remote to see if they are blocking us, because it looks like they are is pulling the script from a that is So I see three choices: upgrade this thing to a more recent edition delete it grab everything that's needed to run this and keep it in-house <- clear winner here what do you think: Maybe the folks over at sig-testing have a place to store the artifacts in-house? They are not massive (about 10MB see below) Size of data about 10MB: the tools and libs for the tensorflow run: the training and eval files for the testrun:\nHere's a relevant issue in a related k8s repo about using/not using docker registries: Registries used in k/k CI should be on Kubernetes Community infra\nlooks good for the subject of putting up a new docker image containing the deps. This seems feasible and effective. I'd prefer it to deleting the test. I'll discuss it a bit more with a few others, but this seems like the way to go forward with this. TBS, I plan to take the above listed test requirements, and build a docker image containing all that is needed, and reset the test to pull the new docker image.\nI've got some Dockerfile changes to fix this. I've tested it locally with no network and it does the full 300 epochs. PR coming soon.\nIs it worth pushing up 182 files to get this green? It is about 6M of python, and 5M of a test dataset.", "commid": "kubernetes_issue_109295", "tokennum": 515}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1d865256c98a5104a154aef1c2519977c97a0b9d5a125274c7d6801698316579", "query": "}, }, Command: []string{\"/bin/sh\"}, <del> Args:    []string{\"-c\", \"python ./data_download.py && time -p python ./wide_deep.py --model_type=wide_deep --train_epochs=300 --epochs_between_evals=300 --batch_size=32561\"}, </del> <ins> Args:    []string{\"-c\", \"time -p python ./wide_deep.py --model_type=wide_deep --train_epochs=300 --epochs_between_evals=300 --batch_size=32561\"}, </ins> } containers = append(containers, ctn)", "positive_passages": [{"docid": "doc-en-kubernetes-1089cbe285cd80c5b6feae67c8fda7b5283b08a5d4cab211d1adc2743664a2e8", "text": "Its all stashed away in the to get the docker image to contain the prereqs. It is selected subdirectories of the quite old archived version (v1.9.0) of the code from here: current version v2.7.2 and two small test data sets from here:\nOK I got it down to 43 files, including the 2 datasets. That's the drivers and the datasets and the libs they need. It all gets packed into the docker image.\nquick question - is there another repository that is under sig-node that can host this image?\nTo be clear, the test's docker image is currently in a repo, the : This PR adds artifacts to an existing docker image in the above repo.\nI've cancelled the above PR. I'll try to get something else going.\nThere has been a decent amount of discussion in slack relating to handling the test's required artifacts. The solution that seems best is to get some practical version of the test requirements into locally owned and controlled storage, so the endpoints that provide access to the assets will at least be under internal control. This is not code, and is not under development. It is a static dataset, that is now stored in an offsite archive, and will not require maintenance. The datasets are published with the \"\": (see bottom right) \"This allows for the sharing and adaptation of the datasets for any purpose, provided that the appropriate credit is given.\" Here are some links to the dataset and where its hosted: https://archive-\nI'd like to get the dataset that holds the test data (about 650k) hosted in GCS where I can get it via http. With that change it is expected that the test will go green. The failures show it is failing when it tries to download the artifact from the uncontrolled remote endpoint. Somebody, please help me get this artifact into an internally controlled server. Thanks\nWas the idea of downloading this only on image creation in dockerfile rejected?\nThanks for the reminder I did not fairly evaluate that proposal. I just jumped to my earlier proposal. Thinking about this proposal I see that it would mean downloading the test data for inclusion into the docker image, while the image's test driver tooling is built to pull down the dataset itself from a remote.", "commid": "kubernetes_issue_109295", "tokennum": 504}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1d865256c98a5104a154aef1c2519977c97a0b9d5a125274c7d6801698316579", "query": "}, }, Command: []string{\"/bin/sh\"}, <del> Args:    []string{\"-c\", \"python ./data_download.py && time -p python ./wide_deep.py --model_type=wide_deep --train_epochs=300 --epochs_between_evals=300 --batch_size=32561\"}, </del> <ins> Args:    []string{\"-c\", \"time -p python ./wide_deep.py --model_type=wide_deep --train_epochs=300 --epochs_between_evals=300 --batch_size=32561\"}, </ins> } containers = append(containers, ctn)", "positive_passages": [{"docid": "doc-en-kubernetes-1e0a13eacbc2a35a9de3ea0888ffa655ef37373231443eb0a06d10729155f72f", "text": "That is a simple change to handle, while simply re-hosting the artifact on GCS would require only changing the endpoint. Also building the docker would probably still require network access to the artifact, which would probably require us to put it somewhere anyway. I assume, putting it into the docker image would best be done by downloading the test data artifact from somewhere. Would we then be storing the artifact twice - once in the docker image, and once in a locally controlled endpoint? If the docker build server has unrestricted access to the artifact, this proposal would be good. I don't have access to the servers to run tests. However, I could put up an RB for the Dockerfile to try it out. This is probably worth the effort. I'll get an PR going for trying to pull down the remote test-data artifact from the image build server, and bunde it into the docker image, and I'll link it to this ticket.\nthank you. We do not change the image for a long time, so downloading it once would likely be enough. Once it is self-contained, it is even better for the continuous perf runs in tests.\n/reopen\nYou can't reopen an issue/PR unless you authored it or you are a collaborator. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nCurrently the image builds for the first arch (amd64) but fails when it enters the cross compiling phase (arm64) and specifically when it tries to do apt installs from within the qemu-*-static emulator: The other images in node-perf fail to build in the same way. The jessie-dnsutils image build fails to build in the same way. I have tried pulling in newer base images up to buster, but it did not fix the problem. -Start focusing on the version of qemu. - qemu is version locked in the Makefile and has not changed in two years. There was an and the images were building at that time.", "commid": "kubernetes_issue_109295", "tokennum": 507}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1d865256c98a5104a154aef1c2519977c97a0b9d5a125274c7d6801698316579", "query": "}, }, Command: []string{\"/bin/sh\"}, <del> Args:    []string{\"-c\", \"python ./data_download.py && time -p python ./wide_deep.py --model_type=wide_deep --train_epochs=300 --epochs_between_evals=300 --batch_size=32561\"}, </del> <ins> Args:    []string{\"-c\", \"time -p python ./wide_deep.py --model_type=wide_deep --train_epochs=300 --epochs_between_evals=300 --batch_size=32561\"}, </ins> } containers = append(containers, ctn)", "positive_passages": [{"docid": "doc-en-kubernetes-21583406d11cc50f0d960b70331655967f38b78788b3327204ea9b4d500f4be7", "text": "Try to find clues over there.\nI tried pinning many relevant versions of from but none helped. Here's a clue: This ugly hack gets it past the observed error:\nNote the previous PR was missing an important change, but I do not see any feasible way that could explain the current problem with failing, so I have not felt any urgency to put up a PR for it. FTR I need to bump the VERSION. I did not bump the version in I thought maybe the CI would bump it automatically.\nThere's an image version in . Its still pulling the old version and failing. Bump it from 1.2 to 1.3. So one more commit is needed.\nThe new image is present and runs perfectly. Tested it on local linux and in google cloud: It ran to completion. Note the new image URL. Its NOT the same as the old one:\npodspec references the image Here's the . tf-wide-deep's url is built The above has staging in it. . Its already built and pushed to staging. It must be promoted when this new version number goes out.\nFTR: My \"testing\" above did not catch the current problem because I did not run the full e2e_test binary. I only tested the image via a . AND I should have read way back at the beginning.\nLocal run of : has to change too.\nLocal test using the published 1.3 image run the standard way was successful with the above: ran the test successfully. So promote the image per bump the image version in the e2e test manifest change the\nAfter the image promotion is merged, there's STILL one more commit coming: bump the image version in the e2e test manifest change the\nits promoted and is found at the expected url local containerd cleared out local test was rerun pulling from the new prod registry local test using that new registry passes\nits fixed. the test is green again.", "commid": "kubernetes_issue_109295", "tokennum": 399}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1da11707c3bb8173d40db4538de19d1a01374e5306926e5e5b75402d110818f9", "query": "serviceLister:                           serviceLister, serviceHasSynced:                        serviceHasSynced, nodeLister:                              nodeLister, <ins> nodeHasSynced:                           nodeHasSynced, </ins> masterServiceNamespace:                  masterServiceNamespace, streamingConnectionIdleTimeout:          kubeCfg.StreamingConnectionIdleTimeout.Duration, recorder:                                kubeDeps.Recorder,", "positive_passages": [{"docid": "doc-en-kubernetes-8476bba8e23a7ed885cd34c1077ce17dbf12901ac7ae9725333264f6ea8cfdae", "text": "What happened: A deployment is created that uses a after the cluster master is created but before the cluster worker nodes are fully initialized. During the initialization of the worker nodes, the nodes are temporarily available for scheduling without the necessary label to match the deployment's node selector. Depending on how long the nodes are available for scheduling without the necessary node labels for the deployment, the scheduler will start to spam with cluster with pods in status. This spamming stops once the worker nodes are fully initialized and the pods are scheduled successful. The exact timing of all of this is TBD. What you expected to happen: Pods in status are annoying and require manual cleanup. It would be preferred that the scheduler avoid this an simply issue warning events. How to reproduce it (as minimally and precisely as possible): See issue description. Anything else we need to know?: No. Environment: Kubernetes version (use ): 1.18.3 Cloud provider or hardware configuration: IBM Cloud Kubernetes Service OS (e.g: ): Ubuntu 18.04.4 LTS Kernel (e.g. ): 4.15.0-96-generic Install tools: Managed service install Network plugin and version (if this is a network-related bug): N/A Others: N/A\nRelated to and\n/sig scheduling\nby spamming are you referring to scheduler logs? also, why are the nodes not labelled from the get go?\nJust to confirm, all the pods in question are still in Pending state, yes? If the pods are in pending state, all of them will get scheduled eventually once the nodes get their labels.\nThe pods are not in state. They are actually in state. The pods eventually get scheduled but we are left with anywhere from a few to dozens of these state pods. Also, we are looking at labeling the nodes via kubelet flags to see if that helps.\n/remove-kind bug\nAfter we add some retry logic and wait time in this problem can be solved: As you can see this function returns initial node as the first request failed.\nI also get hit by this, when single controller node gets rebooted and scheduler starts as static container before kubelet becomes ready.", "commid": "kubernetes_issue_92067", "tokennum": 465}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1da11707c3bb8173d40db4538de19d1a01374e5306926e5e5b75402d110818f9", "query": "serviceLister:                           serviceLister, serviceHasSynced:                        serviceHasSynced, nodeLister:                              nodeLister, <ins> nodeHasSynced:                           nodeHasSynced, </ins> masterServiceNamespace:                  masterServiceNamespace, streamingConnectionIdleTimeout:          kubeCfg.StreamingConnectionIdleTimeout.Duration, recorder:                                kubeDeps.Recorder,", "positive_passages": [{"docid": "doc-en-kubernetes-6c53201dbb91d52a8ade960092a5ed582f4d35e33a53b75d555d15ae815dc25c", "text": "Can be cleaned up with:\n/sig node\nthe spam cycle is this loop: \"pod create, pod schedule, worker reject, pod failed\" -- we don't have a lot of protection in higher level workload controllers to handle pods that fail at kubelet admission time versus pods that just dont create due to quota/admission. in general, is the spam causing any other stability issues? is pod gc pruning the pods?\nI wonder if we can do a trick in node lister to mitigate any race condition here...\nwe could maybe do something similar to to ensure node lister has synced...\nhacking on option to ensure if kubelet has a node lister with a valid kube client, we wait for it to sync at least once here which should mitigate this issue. see:\nWe noticed the problem on the OLM pod which is managed by the OLM operator. Right or wrong, the operator does not like seeing the pod go to status and no longer reconciles the pod. The end result is that manual intervention (i.e. pod deletion) is required to fix the problem.\nsure... i would have thought the pod is failed in that instance and reached a terminal state. either way, i am looking at what i can do to mitigate this.\nThe problem persists in our environment as well, and the workaround cited above will not do anymore. Is there something in the works for this one?\nIssues 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\n/remove-lifecycle stale", "commid": "kubernetes_issue_92067", "tokennum": 383}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1db90df26f4e08311e9dfb3902a264434011d2b86cde9a8874d6f3dc6629f041", "query": "# Post-condition: Only the default kubernetes services exist kube::test::get_object_assert services \"{{range.items}}{{$id_field}}:{{end}}\" 'kubernetes:' <ins> ### Create deployent and service # Pre-condition: no deployment exists kube::test::wait_object_assert deployment \"{{range.items}}{{$id_field}}:{{end}}\" '' # Command kubectl run testmetadata --image=nginx --replicas=2 --port=80 --expose --service-overrides='{ \"metadata\": { \"annotations\": { \"zone-context\": \"home\" } } } ' # Check result kube::test::get_object_assert deployment \"{{range.items}}{{$id_field}}:{{end}}\" 'testmetadata:' kube::test::get_object_assert 'service testmetadata' \"{{.metadata.annotations}}\" \"map[zone-context:home]\" ### Expose deployment as a new service # Command kubectl expose deployment testmetadata  --port=1000 --target-port=80 --type=NodePort --name=exposemetadata --overrides='{ \"metadata\": { \"annotations\": { \"zone-context\": \"work\" } } } ' # Check result kube::test::get_object_assert 'service exposemetadata' \"{{.metadata.annotations}}\" \"map[zone-context:work]\" # Clean-Up # Command kubectl delete service exposemetadata testmetadata \"${kube_flags[@]}\" if [[ \"${WAIT_FOR_DELETION:-}\" == \"true\" ]]; then kube::test::wait_object_assert services \"{{range.items}}{{$id_field}}:{{end}}\" 'kubernetes:' fi kubectl delete deployment testmetadata \"${kube_flags[@]}\" if [[ \"${WAIT_FOR_DELETION:-}\" == \"true\" ]]; then kube::test::wait_object_assert deployment \"{{range.items}}{{$id_field}}:{{end}}\" '' fi </ins> set +o nounset set +o errexit }", "positive_passages": [{"docid": "doc-en-kubernetes-fc07b6eddbb9d1c63170ff68b48220d761822f4a0e8799d7065a14dbb9d41309", "text": "Hey Guys , I try to use the option --override with kubectl expose . First i did this and it work : Now i want to add another service with kubectl expose and this command does not work I have this error If i remove --overrides the command work . `\n/sig cli\nexpose tries to convert version from \"v1\" to \"_internal\" which is not registered. This is the reason that the function doesn't works. == \"\" 316 if inline := cmdutil.GetFlagString(cmd, \"overrides\"); len(inline) 0 { 317 object, err = cmdutil.Merge(scheme.Codecs.LegacyCodec(scheme.Scheme.PrioritizedVersionsAllGroups()...), object, inline) 318 if err != nil { 319 return err 320 } 321 } === 156 // LegacyCodec encodes output to a given API versions, and decodes output into the internal form from 157 // any recognized source. The returned codec will always encode output to JSON. If a type is not 158 // found in the list of versions an error will be returned. 159 // 160 // This method is deprecated - clients and servers should negotiate a serializer by mime-type and 161 // invoke CodecForVersions. Callers that need only to read data should use UniversalDecoder(). 162 // 163 // TODO: make this call exist only in pkg/api, and initialize it with the set of default versions. 164 // All other callers will be forced to request a Codec directly. 165 func (f CodecFactory) LegacyCodec(version ) runtime.Codec { 166 return versioning.NewDefaultingCodecForScheme(f.scheme, f.legacySerializer, f.universal, schema.GroupVersions(version), runtime.InternalGroupVersioner) 167 }\nkubectl help expose Expose a resource as a new Kubernetes service. Possible resources include (case insensitive): pod (po), service (svc), replicationcontroller (rc), deployment (deploy), replicaset (rs) In order to control the scope, I only register them as un-versioned type in the fix.", "commid": "kubernetes_issue_73077", "tokennum": 521}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1dddf422da740eba1d7aa20c0df6a2c62a8914a379c5e46dae5d1943affde45a", "query": "} output, err := json.Marshal(agg) require.NoError(t, err) <del> // Content-type is \"aggregated\" discovery format. w.Header().Set(\"Content-Type\", AcceptV2Beta1) </del> <ins> // Content-type is \"aggregated\" discovery format. Add extra parameter // to ensure we are resilient to these extra parameters. w.Header().Set(\"Content-Type\", AcceptV2Beta1+\"; charset=utf-8\") </ins> w.WriteHeader(status) w.Write(output) }))", "positive_passages": [{"docid": "doc-en-kubernetes-3257ecff81fbc60fa2a8f982346c462089eb7c896f62cce1d4e02ff6df66d913", "text": "We are using (and ) to interact with Kubernetes clusters behind a couple of proxy layers. One of these proxies completes the headers to include character encoding details. This was working fine until recently, when client-go/kubectl have started to fail when interacting with the discovery API. It seems that a recent change has made kubectl more restrictive of the content-type that it expects. I suspect that it is related to this commit: For example, this is an error from a kubectl command: We can of course try to fix it on our end, removing that charset information. However, it is a valid content-type and the way kubectl is handling the content-type there seems like it is relying on implementation details of kube-apiserver (that it does not add metadata to the content-type). I propose to fix this issue in , by properly parsing and handling the content-type.\ncc /kind regression /kind bug /sig api-machinery /priority important-soon looks like the switch statement in downloadLegacy() needs to be more tolerant of the variety of content-types it can get from a server (including text/plain or no content-type if old servers could have returned that...)\n/transfer kubernetes/kubernetes\nSomething went wrong or the destination repo kubernetes/kubernetes/kubernetes does not exist. <detailsIn response to : /transfer kubernetes/kubernetes 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\n/transfer kubernetes\nYep, the string comparison for the content-type is flimsy, let's address that. Thanks for the report!\n/assign\n/triage accepted\n/cc\nThe fix is being cherry-picked back to: : :", "commid": "kubernetes_issue_117562", "tokennum": 408}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1e30e61f1a18654df6781dcc87bfef6e847bb3275d7d5406ead10770bf25b592", "query": "if kl.kubeClient == nil { return kl.initialNode(context.TODO()) } <ins> // if we have a valid kube client, we wait for initial lister to sync if !kl.nodeHasSynced() { err := wait.PollImmediate(time.Second, maxWaitForAPIServerSync, func() (bool, error) { return kl.nodeHasSynced(), nil }) if err != nil { return nil, fmt.Errorf(\"nodes have not yet been read at least once, cannot construct node object\") } } </ins> return kl.nodeLister.Get(string(kl.nodeName)) }", "positive_passages": [{"docid": "doc-en-kubernetes-8476bba8e23a7ed885cd34c1077ce17dbf12901ac7ae9725333264f6ea8cfdae", "text": "What happened: A deployment is created that uses a after the cluster master is created but before the cluster worker nodes are fully initialized. During the initialization of the worker nodes, the nodes are temporarily available for scheduling without the necessary label to match the deployment's node selector. Depending on how long the nodes are available for scheduling without the necessary node labels for the deployment, the scheduler will start to spam with cluster with pods in status. This spamming stops once the worker nodes are fully initialized and the pods are scheduled successful. The exact timing of all of this is TBD. What you expected to happen: Pods in status are annoying and require manual cleanup. It would be preferred that the scheduler avoid this an simply issue warning events. How to reproduce it (as minimally and precisely as possible): See issue description. Anything else we need to know?: No. Environment: Kubernetes version (use ): 1.18.3 Cloud provider or hardware configuration: IBM Cloud Kubernetes Service OS (e.g: ): Ubuntu 18.04.4 LTS Kernel (e.g. ): 4.15.0-96-generic Install tools: Managed service install Network plugin and version (if this is a network-related bug): N/A Others: N/A\nRelated to and\n/sig scheduling\nby spamming are you referring to scheduler logs? also, why are the nodes not labelled from the get go?\nJust to confirm, all the pods in question are still in Pending state, yes? If the pods are in pending state, all of them will get scheduled eventually once the nodes get their labels.\nThe pods are not in state. They are actually in state. The pods eventually get scheduled but we are left with anywhere from a few to dozens of these state pods. Also, we are looking at labeling the nodes via kubelet flags to see if that helps.\n/remove-kind bug\nAfter we add some retry logic and wait time in this problem can be solved: As you can see this function returns initial node as the first request failed.\nI also get hit by this, when single controller node gets rebooted and scheduler starts as static container before kubelet becomes ready.", "commid": "kubernetes_issue_92067", "tokennum": 465}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1e30e61f1a18654df6781dcc87bfef6e847bb3275d7d5406ead10770bf25b592", "query": "if kl.kubeClient == nil { return kl.initialNode(context.TODO()) } <ins> // if we have a valid kube client, we wait for initial lister to sync if !kl.nodeHasSynced() { err := wait.PollImmediate(time.Second, maxWaitForAPIServerSync, func() (bool, error) { return kl.nodeHasSynced(), nil }) if err != nil { return nil, fmt.Errorf(\"nodes have not yet been read at least once, cannot construct node object\") } } </ins> return kl.nodeLister.Get(string(kl.nodeName)) }", "positive_passages": [{"docid": "doc-en-kubernetes-6c53201dbb91d52a8ade960092a5ed582f4d35e33a53b75d555d15ae815dc25c", "text": "Can be cleaned up with:\n/sig node\nthe spam cycle is this loop: \"pod create, pod schedule, worker reject, pod failed\" -- we don't have a lot of protection in higher level workload controllers to handle pods that fail at kubelet admission time versus pods that just dont create due to quota/admission. in general, is the spam causing any other stability issues? is pod gc pruning the pods?\nI wonder if we can do a trick in node lister to mitigate any race condition here...\nwe could maybe do something similar to to ensure node lister has synced...\nhacking on option to ensure if kubelet has a node lister with a valid kube client, we wait for it to sync at least once here which should mitigate this issue. see:\nWe noticed the problem on the OLM pod which is managed by the OLM operator. Right or wrong, the operator does not like seeing the pod go to status and no longer reconciles the pod. The end result is that manual intervention (i.e. pod deletion) is required to fix the problem.\nsure... i would have thought the pod is failed in that instance and reached a terminal state. either way, i am looking at what i can do to mitigate this.\nThe problem persists in our environment as well, and the workaround cited above will not do anymore. Is there something in the works for this one?\nIssues 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\n/remove-lifecycle stale", "commid": "kubernetes_issue_92067", "tokennum": 383}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1e96f6415f93c0ed3c0a9c99b7733df5fb68ee8764bd8a1ec67fe5a615232fce", "query": "for _, tc := range testCases { t.Run(tc.name, func(t *testing.T) { defer featuregatetesting.SetFeatureGateDuringTest(t, utilfeature.DefaultFeatureGate, features.LoadBalancerIPMode, tc.ipModeEnabled)() <del> s := core.LoadBalancerStatus{} tc.tweakLBStatus(&s) errs := ValidateLoadBalancerStatus(&s, field.NewPath(\"status\")) </del> <ins> defer featuregatetesting.SetFeatureGateDuringTest(t, utilfeature.DefaultFeatureGate, features.AllowServiceLBStatusOnNonLB, tc.nonLBAllowed)() status := core.LoadBalancerStatus{} tc.tweakLBStatus(&status) spec := core.ServiceSpec{Type: core.ServiceTypeLoadBalancer} if tc.tweakSvcSpec != nil { tc.tweakSvcSpec(&spec) } errs := ValidateLoadBalancerStatus(&status, field.NewPath(\"status\"), &spec) </ins> if len(errs) != tc.numErrs { t.Errorf(\"Unexpected error list for case %q(expected:%v got %v) - Errors:n %v\", tc.name, tc.numErrs, len(errs), errs.ToAggregate()) }", "positive_passages": [{"docid": "doc-en-kubernetes-e021a9a686a92d83ba285392c70089f3a0813200ee010fb06825ed96dc15cfdb", "text": "xref I think this may be one of the few cases where we can actually change the behavior in a \"breaking\" way. User creates service with , is empty Controller or user updates the status subresource, sets (not wiped or validated, should be) User updates in any way, is wiped It's clear that the is not meant to be set when is not \"LoadBalancer\". The question is: 1) Fail validation? 2) Silently discard the value? 3) Warn and then discard the value? 4) Just warn and leave it. Because we allowed it in the past, but it is so volatile, I lean towards 3. and - the people most familair with this type. Edit: PrepareForUpdate() runs before warnings. So: (1) is easy (2) is easy (4) is slightly less easy than (2) (3) is slightly less easy than (4)\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nOMG change it to clusterIP as expected Status is wiped update status as ClusterIP ... and if I edit the service back to loadbalancer it keeps the status??\n/kind bug\n/retitle Service can be set when !=\nWe talked about this one at the SIG Network meeting today. suggested we use the feature gate for deprecation option to phase the current (problematic) functionality out.\n/triage accept\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /triage accept 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", "commid": "kubernetes_issue_119700", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1ea5aa727a07988def3af37d5a6ff9d572aab4bd85221f1483d6a1587f3ab3d5", "query": "expectError: false, }, { <del> name: \"subpath-mounting-unix-socket\", </del> <ins> name: \"mount-unix-socket\", </ins> prepare: func(base string) ([]string, string, string, error) { volpath, subpathMount := getTestPaths(base) mounts := []string{subpathMount}", "positive_passages": [{"docid": "doc-en-kubernetes-ea06bb5e10f9c1a3c6e6bdd4b05e49a63cf7c6313178f3d65784c243007cbe65", "text": "Subpath unix socket tests can flake because of long socket path. On Linux the path limit should be 108 chars or less. /sig storage", "commid": "kubernetes_issue_61844", "tokennum": 31}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1ea9ba6d97db8b82c4fe5bbe0060c77e678be6271f8a4fce3563b429cdea8b60", "query": "<ins> # Rollback workflow Build it in this directory. Make sure you have etcd dependency ready. Last time we use etcd v3.0.7. ``` $ go build . ``` Run it: ``` $ ./rollback2 --data-dir $ETCD_DATA_DIR --ttl 1h ``` This will rollback KV pairs from v3 into v2. If a key was attached to a lease before, it will be created with given TTL (default to 1h). On success, it will print at the end: ``` Finished successfully ``` Repeat this on all etcd members. You can do simple check on keys (if any exists): ``` etcdctl ls / ``` Important Note ------ This tool isn't recommended to use if any problem comes up in etcd3 backend. Please report bugs and we will fix it soon. If it's still preferred to run this tool, please backup all your data beforehand. This tool will also back up datadir to same path with \".rollback.backup\" suffix. Caveats: - The tool doesn't preserve versions of keys. - If any v2 data exists before rollback, they will be wiped out. - v3 data only exists in the backup after successful rollback. [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/cluster/images/etcd/rollback/README.md?pixel)]() </ins>  No newline at end of file", "positive_passages": [{"docid": "doc-en-kubernetes-6208b2974deee3332ab4020708350835523c141c61d79e5104e4c7dba961daa5", "text": "ci-kubernetes-e2e-gce-device-plugin-gpu.Overall ci-kubernetes-e2e-gce-device-plugin-gpu.Pod kubetest.Up Intermittently since 02/23 No response No response /sig testing /sig release\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/cc /sig node BTW, would you help to confirm if this is a release cut blocker? We plan to release 1.30.0-alpha.3 on Tuesday 27th February 2024.\nIt passed! Maybe it was some infra issues?\nFailed again. /sig k8s-infra\nMany recreating of nodes in log.\nThis is caused by infra flaky.\nThe problem is\nThis job only runs one test and GPU instances are hard to find we don\u2019t need many of those instances for this job, can we please change this job to only use 2 workers?\n/cc\ntests failed in a recent run. It failed the first time. The Job failure now changed to test case failing today. It failed 4 times in a row.\n/assign\nI launched a test run, logged into the master node and took the kubeconfig and found the following: Relevant bit\nLink some related updates recently on this job.\nThe error above in is weird to me. It said No firmware image found . In successful run before, like (02-27), there are no such failure logs. failure in only kubelet log shows the pod crashed and restarted for many times. No pod log or containerd log.\nAfter , the CI is not always failing now and 4 in a row.\n/close\nClosing 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\n/reopen as keeps flaking\nReopened this issue. <detailsIn response to : /reopen as keeps flaking Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_123491", "tokennum": 511}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1ea9ba6d97db8b82c4fe5bbe0060c77e678be6271f8a4fce3563b429cdea8b60", "query": "<ins> # Rollback workflow Build it in this directory. Make sure you have etcd dependency ready. Last time we use etcd v3.0.7. ``` $ go build . ``` Run it: ``` $ ./rollback2 --data-dir $ETCD_DATA_DIR --ttl 1h ``` This will rollback KV pairs from v3 into v2. If a key was attached to a lease before, it will be created with given TTL (default to 1h). On success, it will print at the end: ``` Finished successfully ``` Repeat this on all etcd members. You can do simple check on keys (if any exists): ``` etcdctl ls / ``` Important Note ------ This tool isn't recommended to use if any problem comes up in etcd3 backend. Please report bugs and we will fix it soon. If it's still preferred to run this tool, please backup all your data beforehand. This tool will also back up datadir to same path with \".rollback.backup\" suffix. Caveats: - The tool doesn't preserve versions of keys. - If any v2 data exists before rollback, they will be wiped out. - v3 data only exists in the backup after successful rollback. [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/cluster/images/etcd/rollback/README.md?pixel)]() </ins>  No newline at end of file", "positive_passages": [{"docid": "doc-en-kubernetes-93e6b458b8ba607e02020a8718331e5d8d90eb2c8daf949aa5e83a98cf741ed8", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThe problem is different with the failure after the revert. We(release signal team) plan to open an issue for the flake later. (Probably, we should open that one and then close on behalf of that new issue later.)\nFeel free to close it then. However, it failed 3 times out of last 4 runs. It's more a failure than a flake in my opinion. If doesn't help/ not appropriate, I'd suggest to revert installer and image changes\ncomment is clear about the root cause, we have a problem installing the drivers, can you redirect this issue if you think is a bug?\nAfter was merged, there are 6 failure in last 24 run. Tab stats: 8 of 10 (80.0%) recent columns passed (258 of 262 or 98.5% cells) The Flaky rate is lower.", "commid": "kubernetes_issue_123491", "tokennum": 202}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1ecf1608a2f660b88bf044a5ed4a368c473fb9e56256ef196e584eea7e456bcd", "query": "return nil case watch.Error: <del> watcher.Stop() watcherClosed = true // start another cycle return c.waitForVolumeDetachmentInternal(volumeHandle, attachID, timer, timeout) </del> <ins> klog.Warningf(\"waitForVolumeDetachmentInternal received watch error: %v\", event) </ins> } case <-timer.C:", "positive_passages": [{"docid": "doc-en-kubernetes-bf4acf56a8324d5d9229417a25d2febc989c56201f9f4bdce8fffe7a46728546", "text": "A CSI plugin that the 1.10 controller manager can't detect (which could occur in a number of scenarios, such as when a rollout is being performed or a node is evacuated) seems to retry without backoff. In this case, I have a pod referencing a PVC -PV that references my CSI plugin, but no controller plugin running. The controller is probing every 100ms continuously for a single volume attachment. The controller should backoff. Have not tested with higher numbers of pods, but in a busy system this could cause the controller manager to burn CPU. Also, there isn't actually a great error telling the user why the probing is happening (I knew in this case, but an admin likely has no idea).\n/assign\nIssues 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\n/remove-lifecycle stale /milestone v1.14 adding it to next milestone as per if it doesn't make it then it can be further moved\nas KEP has been moved, unless an exception is made, /milestone v1.15\nthe linked kep above is unrelated to this issue. This is a bug and I don't think it needs an associated enhancement\nsorry, got diverted by the comments on that KEP. /milestone v1.14\nHello from Bug Triage Shadow . I'd like to remind that code freeze is coming in 3 days (Friday, 8th March). Is this still planned to be fixed for 1.14?\nWe have not been tracking this for 1.14. /assign can you help triage and see if this is still an issue and if there is a quick fix?\nI can't reproduce the issue, do you remember what you did? From the logs it seems that Watch channel consistently returns so new is called recursively (beware, 1.10 code, but it's very similar in master): Can it produce fairly stable 100ms delay between calls? Anyway, this is not usual code path, watcher does not return in most cases.", "commid": "kubernetes_issue_64952", "tokennum": 478}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1ecf1608a2f660b88bf044a5ed4a368c473fb9e56256ef196e584eea7e456bcd", "query": "return nil case watch.Error: <del> watcher.Stop() watcherClosed = true // start another cycle return c.waitForVolumeDetachmentInternal(volumeHandle, attachID, timer, timeout) </del> <ins> klog.Warningf(\"waitForVolumeDetachmentInternal received watch error: %v\", event) </ins> } case <-timer.C:", "positive_passages": [{"docid": "doc-en-kubernetes-386907f979b2ab6cc28dd5590343cbf2830e874540a448be35232bf4673dff7e", "text": "if I read the code correctly, such recursive must end up with timeout - caller does not care about return value and caller's watch probably won't return anything useful. Is there a reason why we don't return error? This will kick in exponential backoff in A/D controller.\nclearing the milestone for tracking purposes to let the fix land in its own time /milestone clear\nIssues 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\nI found the error would happen when a pv is attahing(volumeattachment has created) and the csi-attacher is deleted at the same time. Then the log would print so frequently (because of recursion).\nis this fixed by ?\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nClosing 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", "commid": "kubernetes_issue_64952", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1f11128a15e96669c49a4c5d0d1e8a28cb35d187992e96a556ad7e9808926b11", "query": "return utilfile.FileExists(pathname) } <ins> func (mounter *Mounter) EvalHostSymlinks(pathname string) (string, error) { return filepath.EvalSymlinks(pathname) } </ins> // formatAndMount uses unix utils to format and mount the given disk func (mounter *SafeFormatAndMount) formatAndMount(source string, target string, fstype string, options []string) error { readOnly := false", "positive_passages": [{"docid": "doc-en-kubernetes-226c0928db9d5aa6f1446838b8788eb7c60cd41b1b8246f4bd1a4e2614bb7834", "text": "/kind bug Using , if a block device is symlinked to the discovery directory e.g. , then MapVolume will fail with since the containerized kubelet cannot see the path on host. is mounted by containerized kubelet, so if before we try to map the device we set devicePath to the evaluation of symlink and end up with a devicePath of , containerized kubelet will see the device and successfully map the device. Are there any issues with this solution? This is on Kubernetes 1.10\n/sig storage\nah yes containerized kubelet has many issues when dealing with symlinks. Check out Mounter.GetMode(), it calls a nsenter EvalSymlinks which should be able to do what you need. But actually, one thing to consider, is do you need to do the losetup on the host, or does inside the container work?\nYes it appears to work from inside the container, on the host I run which disappears after I delete the pod using the device. My understanding of running losetup in MapVolume is not that great but I suppose that as long as that /dev/loop0 is created we are fine. Thanks for the quick response, I'll create a PR using that function and tag you\nDoes it create it on the host or in the containerized kubelet? What happens when containerized kubelet is restarted? The purpose of losetup is to do \"refcounting\" on the block device to prevent possible naming collisions when devices are attached/detached under unhealthy conditions. Ie, if a device showed up as /dev/sdb and you gave that to a pod, and then for some reason it become unhealthy and disappeared (while the pod is still running), another device (maybe even another volume type) could get attached to the node and reuse /dev/sdb. Now the pod has access to a device it's not supposed to. With filesystem volumes, the refcounting is done with mount points, but for block device, loopback is the equivalent.\nIt is created on the host (and also visible in the container), and stays around through restart. I understand now, thank you.\nActually after I restart it becomes /vdb instead of /dev/vdb in the losetup output, idk what that is about.", "commid": "kubernetes_issue_65445", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1f11128a15e96669c49a4c5d0d1e8a28cb35d187992e96a556ad7e9808926b11", "query": "return utilfile.FileExists(pathname) } <ins> func (mounter *Mounter) EvalHostSymlinks(pathname string) (string, error) { return filepath.EvalSymlinks(pathname) } </ins> // formatAndMount uses unix utils to format and mount the given disk func (mounter *SafeFormatAndMount) formatAndMount(source string, target string, fstype string, options []string) error { readOnly := false", "positive_passages": [{"docid": "doc-en-kubernetes-e6271b0ba1dda755d5bb536a727016a621c7c29c599386bc1e9c22a230980cbf", "text": "There is no such thing as /vdb and /dev/vdb is still intact of course. Seems inconsequential since it is disappearing after all pods using the device are deleted, i.e. it's still serving as a refcounter", "commid": "kubernetes_issue_65445", "tokennum": 55}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1f292eff4a150c8153ee5d17ebd30896f89d8e50b11bc52ecf291fa996879900", "query": "`, inhibitDelayMax.Seconds()) logindOverridePath := filepath.Join(logindConfigDirectory, kubeletLogindConf) <del> if err := ioutil.WriteFile(logindOverridePath, []byte(inhibitOverride), 0755); err != nil { </del> <ins> if err := ioutil.WriteFile(logindOverridePath, []byte(inhibitOverride), 0644); err != nil { </ins> return fmt.Errorf(\"failed writing logind shutdown inhibit override file %v: %v\", logindOverridePath, err) }", "positive_passages": [{"docid": "doc-en-kubernetes-a0c3ad6976551b855a45933e19f845be402e9fd035bccb2466a57a10d2f14bed", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: ! What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.20.1 Cloud provider or hardware configuration: OS (e.g: ): 7 Kernel (e.g. ): Linux zsm-test-2 3.10.0-1160.11.1.el7.x8664 SMP Fri Dec 18 16:34:56 UTC 2020 x8664 x8664 x86_64 GNU/Linux Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig node\n/triage accepted /priority backlog", "commid": "kubernetes_issue_97949", "tokennum": 209}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1f66b900d4836acf4845c5eb7520e75092722b43e27815c2ab4633011906053a", "query": "kubectl get services \"${kube_flags[@]}\" kubectl get services \"service-${version}-test\" \"${kube_flags[@]}\" kubectl delete service frontend \"${kube_flags[@]}\" <ins> servicesbefore=\"$(kubectl get services  -o template -t \"{{ len .items }}\" \"${kube_flags[@]}\")\" kubectl create -f examples/guestbook/frontend-service.json \"${kube_flags[@]}\" kubectl create -f examples/guestbook/redis-slave-service.json \"${kube_flags[@]}\" kubectl delete services frontend redisslave # delete multiple services at once servicesafter=\"$(kubectl get services  -o template -t \"{{ len .items }}\" \"${kube_flags[@]}\")\" [ \"$((${servicesafter} - ${servicesbefore}))\" -eq 0 ] </ins> kube::log::status \"Testing kubectl(${version}:replicationcontrollers)\" kubectl get replicationcontrollers \"${kube_flags[@]}\"", "positive_passages": [{"docid": "doc-en-kubernetes-8781beaf9cecb5a2a5891763e358d97bbb8efac5ebba9fc986604965efa0dda5", "text": "Currently, it could not delete multiple pods at once, need to delete them one by one, it's very inconvenient if I have tons of pods to delete. Unlike docker, docker can multiple stop/rm containers/images at once.\nThis is possible using label selectors as of , which is better if you have tons of pods.\nI agree that using label selector is better to delete all of pods under the label. But to delete multile pods at once is still usable: I just want to delete 1/2 pods under the label, label selector will not work selector could not span over other selectors or pods Another reason is docker rm/stop x y z works, I will wonder why kubectl cannot. This is not urgent, but I hope it can be implemented.\nI agree. Thanks for the suggestion.\nWould this be a suitable task for someone new to k8s development? If so, I'd be willing to take a look at this, if someone could provide a couple of hints where to start.\nFurther to my last message, I have a functional work in progress I would like to share, if anyone is interested?\nPRs are welcome. See\nYes, this is a reasonable place to start. Since its in the client, you won't get much orientation to the core server code, but it will be a good place to orient to the client side API. There us also prior art that you can model off of. The kubectl create ... command already supports multiple resources. A good command to adapter would be the 'label' command. You can find it in Many thanks in advance! Brendan On Feb 19, 2015 8:21 AM, \"Eric Tune\" wrote:", "commid": "kubernetes_issue_3050", "tokennum": 364}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1fa9035e638ede560050d8a5da83c627e14919b83eb0ca785495a4786d63d9c0", "query": "} func getFitPredicateFunctions(names sets.String, args PluginFactoryArgs) (map[string]predicates.FitPredicate, error) { <del> schedulerFactoryMutex.Lock() defer schedulerFactoryMutex.Unlock() </del> <ins> schedulerFactoryMutex.RLock() defer schedulerFactoryMutex.RUnlock() </ins> fitPredicates := map[string]predicates.FitPredicate{} for _, name := range names.List() {", "positive_passages": [{"docid": "doc-en-kubernetes-a3c7d28dcea4cbdaac9e2be0d7d2d60e791f1250fe870aa2d2d4769d84db6cae", "text": "What would you like to be : Currently Mutex lock is acquired in for accessing different maps. Some functions only read map entry: We can utilize RWMutex where the above function acquires read lock. Why is this needed: For concurrent calls to IsFitPredicateRegistered / IsPriorityFunctionRegistered, read lock would lower contention.\n/sig scheduling\nfunctions getFitPredicateFunctions, getPriorityFunctionConfigs, ListRegisteredFitPredicates, ListRegisteredPriorityFunctions and GetAlgorithmProvider can also use read lock.\nI happened to raise earlier today. Anyone can finish resting ones.\nGood to know,\nThanks for raising this ! My PR covered and . Feel free to raise another PR to cover others.\nOnce is merged, I will send my PR thanks\nit's merged now.", "commid": "kubernetes_issue_76248", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1fafec356b8a617bf803f8cff69fb8a4a2c05e182ec873c373f2af5a8895bdee", "query": "func (b *Builder) ResourceTypeAndNameArgs(args ...string) *Builder { switch len(args) { case 2: <del> b.name = args[1] </del> <ins> b.names = append(b.names, args[1]) </ins> b.ResourceTypes(SplitResourceArgument(args[0])...) case 0: default:", "positive_passages": [{"docid": "doc-en-kubernetes-8781beaf9cecb5a2a5891763e358d97bbb8efac5ebba9fc986604965efa0dda5", "text": "Currently, it could not delete multiple pods at once, need to delete them one by one, it's very inconvenient if I have tons of pods to delete. Unlike docker, docker can multiple stop/rm containers/images at once.\nThis is possible using label selectors as of , which is better if you have tons of pods.\nI agree that using label selector is better to delete all of pods under the label. But to delete multile pods at once is still usable: I just want to delete 1/2 pods under the label, label selector will not work selector could not span over other selectors or pods Another reason is docker rm/stop x y z works, I will wonder why kubectl cannot. This is not urgent, but I hope it can be implemented.\nI agree. Thanks for the suggestion.\nWould this be a suitable task for someone new to k8s development? If so, I'd be willing to take a look at this, if someone could provide a couple of hints where to start.\nFurther to my last message, I have a functional work in progress I would like to share, if anyone is interested?\nPRs are welcome. See\nYes, this is a reasonable place to start. Since its in the client, you won't get much orientation to the core server code, but it will be a good place to orient to the client side API. There us also prior art that you can model off of. The kubectl create ... command already supports multiple resources. A good command to adapter would be the 'label' command. You can find it in Many thanks in advance! Brendan On Feb 19, 2015 8:21 AM, \"Eric Tune\" wrote:", "commid": "kubernetes_issue_3050", "tokennum": 364}], "negative_passages": []}
{"query_id": "q-en-kubernetes-1ffef005e47295e4d1295d17e44e0ce43d8f2b77e746e865716d9e6bd5b4c900", "query": "$ make get ../../../kubectl.sh get pods Running: ../../../../cluster/gce/../../_output/dockerized/bin/linux/amd64/kubectl get pods <del> POD                                    CONTAINER(S)            IMAGE(S)                           HOST                                                            LABELS                       STATUS 7e1c7ce6-9764-11e4-898c-42010af03582   kibana-logging          kubernetes/kibana                  kubernetes-minion-3.c.kubernetes-elk.internal/130.211.129.169   name=kibana-logging          Running synthetic-logger-0.25lps-pod           synth-lgr               ubuntu:14.04                       kubernetes-minion-2.c.kubernetes-elk.internal/146.148.41.87     name=synth-logging-source    Running synthetic-logger-10lps-pod             synth-lgr               ubuntu:14.04                       kubernetes-minion-1.c.kubernetes-elk.internal/146.148.42.44     name=synth-logging-source    Running influx-grafana                         influxdb                kubernetes/heapster_influxdb       kubernetes-minion-3.c.kubernetes-elk.internal/130.211.129.169   name=influxdb                Running grafana                 kubernetes/heapster_grafana elasticsearch           elasticsearch heapster                               heapster                kubernetes/heapster                kubernetes-minion-2.c.kubernetes-elk.internal/146.148.41.87     name=heapster                Running 67cfcb1f-9764-11e4-898c-42010af03582   etcd                    quay.io/coreos/etcd:latest         kubernetes-minion-3.c.kubernetes-elk.internal/130.211.129.169   k8s-app=skydns               Running kube2sky                kubernetes/kube2sky:1.0 skydns                  kubernetes/skydns:2014-12-23-001 6ba20338-9764-11e4-898c-42010af03582   elasticsearch-logging   elasticsearch                      kubernetes-minion-3.c.kubernetes-elk.internal/130.211.129.169   name=elasticsearch-logging   Running ../../../cluster/kubectl.sh get replicationControllers Running: ../../../cluster/../cluster/gce/../../_output/dockerized/bin/linux/amd64/kubectl get replicationControllers CONTROLLER                         CONTAINER(S)            IMAGE(S)                           SELECTOR                     REPLICAS skydns                             etcd                    quay.io/coreos/etcd:latest         k8s-app=skydns               1 kube2sky                kubernetes/kube2sky:1.0 skydns                  kubernetes/skydns:2014-12-23-001 elasticsearch-logging-controller   elasticsearch-logging   elasticsearch                      name=elasticsearch-logging   1 kibana-logging-controller          kibana-logging          kubernetes/kibana                  name=kibana-logging          1 ../../.../kubectl.sh get services Running: ../../../cluster/../cluster/gce/../../_output/dockerized/bin/linux/amd64/kubectl get services NAME                    LABELS                                    SELECTOR                     IP                  PORT kubernetes-ro           component=apiserver,provider=kubernetes   <none>                       10.0.83.3           80 kubernetes              component=apiserver,provider=kubernetes   <none>                       10.0.79.4           443 influx-master           <none>                                    name=influxdb                10.0.232.223        8085 skydns                  k8s-app=skydns                            k8s-app=skydns               10.0.0.10           53 elasticsearch-logging   <none>                                    name=elasticsearch-logging   10.0.25.103         9200 kibana-logging          <none>                                    name=kibana-logging          10.0.208.114        5601 </del> <ins> POD                                            IP            CONTAINER(S)              IMAGE(S)                                                                            HOST                                    LABELS                                                              STATUS    CREATED      MESSAGE elasticsearch-logging-f0smz                    10.244.2.3                                                                                                                  kubernetes-minion-ilqx/104.197.8.214    kubernetes.io/cluster-service=true,name=elasticsearch-logging       Running   5 hours elasticsearch-logging     gcr.io/google_containers/elasticsearch:1.0                                                                                                                                                      Running   5 hours etcd-server-kubernetes-master                                                                                                                                              kubernetes-master/                      <none>                                                              Running   5 hours etcd-container            gcr.io/google_containers/etcd:2.0.9                                                                                                                                                             Running   5 hours fluentd-elasticsearch-kubernetes-minion-7s1y   10.244.0.2                                                                                                                  kubernetes-minion-7s1y/23.236.54.97     <none>                                                              Running   5 hours fluentd-elasticsearch     gcr.io/google_containers/fluentd-elasticsearch:1.5                                                                                                                                              Running   5 hours fluentd-elasticsearch-kubernetes-minion-cfs6   10.244.1.2                                                                                                                  kubernetes-minion-cfs6/104.154.61.231   <none>                                                              Running   5 hours fluentd-elasticsearch     gcr.io/google_containers/fluentd-elasticsearch:1.5                                                                                                                                              Running   5 hours fluentd-elasticsearch-kubernetes-minion-ilqx   10.244.2.2                                                                                                                  kubernetes-minion-ilqx/104.197.8.214    <none>                                                              Running   5 hours fluentd-elasticsearch     gcr.io/google_containers/fluentd-elasticsearch:1.5                                                                                                                                              Running   5 hours fluentd-elasticsearch-kubernetes-minion-x8gx   10.244.3.2                                                                                                                  kubernetes-minion-x8gx/104.154.47.83    <none>                                                              Running   5 hours fluentd-elasticsearch     gcr.io/google_containers/fluentd-elasticsearch:1.5                                                                                                                                              Running   5 hours kibana-logging-cwe0b                           10.244.1.3                                                                                                                  kubernetes-minion-cfs6/104.154.61.231   kubernetes.io/cluster-service=true,name=kibana-logging              Running   5 hours kibana-logging            gcr.io/google_containers/kibana:1.2                                                                                                                                                             Running   5 hours kube-apiserver-kubernetes-master                                                                                                                                           kubernetes-master/                      <none>                                                              Running   5 hours kube-apiserver            gcr.io/google_containers/kube-apiserver:f0c332fc2582927ec27d24965572d4b0                                                                                                                        Running   5 hours kube-controller-manager-kubernetes-master                                                                                                                                  kubernetes-master/                      <none>                                                              Running   5 hours kube-controller-manager   gcr.io/google_containers/kube-controller-manager:6729154dfd4e2a19752bdf9ceff8464c                                                                                                               Running   5 hours kube-dns-swd4n                                 10.244.3.5                                                                                                                  kubernetes-minion-x8gx/104.154.47.83    k8s-app=kube-dns,kubernetes.io/cluster-service=true,name=kube-dns   Running   5 hours kube2sky                  gcr.io/google_containers/kube2sky:1.2                                                                                                                                                           Running   5 hours etcd                      quay.io/coreos/etcd:v2.0.3                                                                                                                                                                      Running   5 hours skydns                    gcr.io/google_containers/skydns:2015-03-11-001                                                                                                                                                  Running   5 hours kube-scheduler-kubernetes-master                                                                                                                                           kubernetes-master/                      <none>                                                              Running   5 hours kube-scheduler            gcr.io/google_containers/kube-scheduler:ec9d2092f754211cc5ab3a5162c05fc1                                                                                                                        Running   5 hours monitoring-heapster-controller-zpjj1           10.244.3.3                                                                                                                  kubernetes-minion-x8gx/104.154.47.83    kubernetes.io/cluster-service=true,name=heapster                    Running   5 hours heapster                  gcr.io/google_containers/heapster:v0.10.0                                                                                                                                                       Running   5 hours monitoring-influx-grafana-controller-dqan4     10.244.3.4                                                                                                                  kubernetes-minion-x8gx/104.154.47.83    kubernetes.io/cluster-service=true,name=influxGrafana               Running   5 hours grafana                   gcr.io/google_containers/heapster_grafana:v0.6                                                                                                                                                  Running   5 hours influxdb                  gcr.io/google_containers/heapster_influxdb:v0.3                                                                                                                                                 Running   5 hours synthetic-logger-0.25lps-pod                   10.244.0.7                                                                                                                  kubernetes-minion-7s1y/23.236.54.97     name=synth-logging-source                                           Running   19 minutes synth-lgr                 ubuntu:14.04                                                                                                                                                                                    Running   19 minutes synthetic-logger-10lps-pod                     10.244.3.14                                                                                                                 kubernetes-minion-x8gx/104.154.47.83    name=synth-logging-source                                           Running   19 minutes synth-lgr                 ubuntu:14.04                                                                                                                                                                                    Running   19 minutes ../../_output/local/bin/linux/amd64/kubectl get replicationControllers CONTROLLER                             CONTAINER(S)            IMAGE(S)                                          SELECTOR                     REPLICAS elasticsearch-logging                  elasticsearch-logging   gcr.io/google_containers/elasticsearch:1.0        name=elasticsearch-logging   1 kibana-logging                         kibana-logging          gcr.io/google_containers/kibana:1.2               name=kibana-logging          1 kube-dns                               etcd                    quay.io/coreos/etcd:v2.0.3                        k8s-app=kube-dns             1 kube2sky                gcr.io/google_containers/kube2sky:1.2 skydns                  gcr.io/google_containers/skydns:2015-03-11-001 monitoring-heapster-controller         heapster                gcr.io/google_containers/heapster:v0.10.0         name=heapster                1 monitoring-influx-grafana-controller   influxdb                gcr.io/google_containers/heapster_influxdb:v0.3   name=influxGrafana           1 grafana                 gcr.io/google_containers/heapster_grafana:v0.6 ../../_output/local/bin/linux/amd64/kubectl get services NAME                     LABELS                                                              SELECTOR                     IP(S)          PORT(S) elasticsearch-logging    kubernetes.io/cluster-service=true,name=elasticsearch-logging       name=elasticsearch-logging   10.0.251.221   9200/TCP kibana-logging           kubernetes.io/cluster-service=true,name=kibana-logging              name=kibana-logging          10.0.188.118   5601/TCP kube-dns                 k8s-app=kube-dns,kubernetes.io/cluster-service=true,name=kube-dns   k8s-app=kube-dns             10.0.0.10      53/UDP kubernetes               component=apiserver,provider=kubernetes                             <none>                       10.0.0.2       443/TCP kubernetes-ro            component=apiserver,provider=kubernetes                             <none>                       10.0.0.1       80/TCP monitoring-grafana       kubernetes.io/cluster-service=true,name=grafana                     name=influxGrafana           10.0.254.202   80/TCP monitoring-heapster      kubernetes.io/cluster-service=true,name=heapster                    name=heapster                10.0.19.214    80/TCP monitoring-influxdb      name=influxGrafana                                                  name=influxGrafana           10.0.198.71    80/TCP monitoring-influxdb-ui   name=influxGrafana                                                  name=influxGrafana           10.0.109.66    80/TCP </ins> ``` The `net` rule in the Makefile will report information about the Elasticsearch and Kibana services including the public IP addresses of each service. ``` $ make net ../../../kubectl.sh get services elasticsearch-logging -o json <del> current-context: \"kubernetes-satnam_kubernetes\" Running: ../../../../cluster/gce/../../_output/dockerized/bin/linux/amd64/kubectl get services elasticsearch-logging -o json </del> <ins> current-context: \"lithe-cocoa-92103_kubernetes\" Running: ../../_output/local/bin/linux/amd64/kubectl get services elasticsearch-logging -o json </ins> { \"kind\": \"Service\", <del> \"id\": \"elasticsearch-logging\", \"uid\": \"e5bf0a51-b87f-11e4-bd62-42010af01267\", \"creationTimestamp\": \"2015-02-19T21:40:18Z\", \"selfLink\": \"/api/v1beta1/services/elasticsearch-logging?namespace=default\", \"resourceVersion\": 68, \"apiVersion\": \"v1beta1\", \"namespace\": \"default\", \"port\": 9200, \"protocol\": \"TCP\", \"labels\": { \"name\": \"elasticsearch-logging\" </del> <ins> \"apiVersion\": \"v1beta3\", \"metadata\": { \"name\": \"elasticsearch-logging\", \"namespace\": \"default\", \"selfLink\": \"/api/v1beta3/namespaces/default/services/elasticsearch-logging\", \"uid\": \"9dc7290f-f358-11e4-a58e-42010af09a93\", \"resourceVersion\": \"28\", \"creationTimestamp\": \"2015-05-05T18:57:45Z\", \"labels\": { \"kubernetes.io/cluster-service\": \"true\", \"name\": \"elasticsearch-logging\" } </ins> }, <del> \"selector\": { \"name\": \"elasticsearch-logging\" </del> <ins> \"spec\": { \"ports\": [ { \"name\": \"\", \"protocol\": \"TCP\", \"port\": 9200, \"targetPort\": \"es-port\" } ], \"selector\": { \"name\": \"elasticsearch-logging\" }, \"portalIP\": \"10.0.251.221\", \"sessionAffinity\": \"None\" </ins> }, <del> \"createExternalLoadBalancer\": true, \"publicIPs\": [ \"104.154.81.135\" ], \"containerPort\": 9200, \"portalIP\": \"10.0.58.62\", \"sessionAffinity\": \"None\" </del> <ins> \"status\": {} </ins> } <del> ../../../kubectl.sh get services kibana-logging -o json current-context: \"kubernetes-satnam_kubernetes\" Running: ../../../../cluster/gce/../../_output/dockerized/bin/linux/amd64/kubectl get services kibana-logging -o json </del> <ins> current-context: \"lithe-cocoa-92103_kubernetes\" Running: ../../_output/local/bin/linux/amd64/kubectl get services kibana-logging -o json </ins> { \"kind\": \"Service\", <del> \"id\": \"kibana-logging\", \"uid\": \"e5bd4617-b87f-11e4-bd62-42010af01267\", \"creationTimestamp\": \"2015-02-19T21:40:18Z\", \"selfLink\": \"/api/v1beta1/services/kibana-logging?namespace=default\", \"resourceVersion\": 67, \"apiVersion\": \"v1beta1\", \"namespace\": \"default\", \"port\": 5601, \"protocol\": \"TCP\", \"labels\": { \"name\": \"kibana-logging\" </del> <ins> \"apiVersion\": \"v1beta3\", \"metadata\": { \"name\": \"kibana-logging\", \"namespace\": \"default\", \"selfLink\": \"/api/v1beta3/namespaces/default/services/kibana-logging\", \"uid\": \"9dc6f856-f358-11e4-a58e-42010af09a93\", \"resourceVersion\": \"31\", \"creationTimestamp\": \"2015-05-05T18:57:45Z\", \"labels\": { \"kubernetes.io/cluster-service\": \"true\", \"name\": \"kibana-logging\" } </ins> }, <del> \"selector\": { \"name\": \"kibana-logging\" </del> <ins> \"spec\": { \"ports\": [ { \"name\": \"\", \"protocol\": \"TCP\", \"port\": 5601, \"targetPort\": \"kibana-port\" } ], \"selector\": { \"name\": \"kibana-logging\" }, \"portalIP\": \"10.0.188.118\", \"sessionAffinity\": \"None\" </ins> }, <del> \"createExternalLoadBalancer\": true, \"publicIPs\": [ \"104.154.91.224\" ], \"containerPort\": 80, \"portalIP\": \"10.0.124.153\", \"sessionAffinity\": \"None\" </del> <ins> \"status\": {} </ins> } ``` <del> For this example the Elasticsearch service is running at `http://104.154.81.135:9200`. </del> <ins> To find the URLs to access the Elasticsearch and Kibana viewer, ``` $ kubectl cluster-info Kubernetes master is running at https://130.211.122.180 elasticsearch-logging is running at https://130.211.122.180/api/v1beta3/proxy/namespaces/default/services/elasticsearch-logging kibana-logging is running at https://130.211.122.180/api/v1beta3/proxy/namespaces/default/services/kibana-logging kube-dns is running at https://130.211.122.180/api/v1beta3/proxy/namespaces/default/services/kube-dns grafana is running at https://130.211.122.180/api/v1beta3/proxy/namespaces/default/services/monitoring-grafana heapster is running at https://130.211.122.180/api/v1beta3/proxy/namespaces/default/services/monitoring-heapster ``` To find the user name and password to access the URLs, ``` $ kubectl config view apiVersion: v1 clusters: - cluster: certificate-authority-data: REDACTED server: https://130.211.122.180 name: lithe-cocoa-92103_kubernetes contexts: - context: cluster: lithe-cocoa-92103_kubernetes user: lithe-cocoa-92103_kubernetes name: lithe-cocoa-92103_kubernetes current-context: lithe-cocoa-92103_kubernetes kind: Config preferences: {} users: - name: lithe-cocoa-92103_kubernetes user: client-certificate-data: REDACTED client-key-data: REDACTED token: 65rZW78y8HxmXXtSXuUw9DbP4FLjHi4b - name: lithe-cocoa-92103_kubernetes-basic-auth user: password: h5M0FtVXXflBSdI7 username: admin ``` Access the Elasticsearch service at URL `https://130.211.122.180/api/v1beta3/proxy/namespaces/default/services/elasticsearch-logging`, use the user name 'admin' and password 'h5M0FtVXXflBSdI7', </ins> ``` <del> $ curl http://104.154.81.135:9200 </del> { \"status\" : 200, <del> \"name\" : \"Wombat\", \"cluster_name\" : \"elasticsearch\", </del> <ins> \"name\" : \"Major Mapleleaf\", \"cluster_name\" : \"kubernetes_logging\", </ins> \"version\" : { \"number\" : \"1.4.4\", \"build_hash\" : \"c88f77ffc81301dfa9dfd81ca2232f09588bd512\",", "positive_passages": [{"docid": "doc-en-kubernetes-bc75029de49571476e249812075ff7ffff85fb8014f5cfe5e32228962baa98b2", "text": "Hi , I followed the instructions in examples/logging-demo, and there was no \"external IP\" field for elasticsearch-logging or kibana-logging, as shown below: I start up my cluster via cluster/kube- Did I miss something or is it a bug? Thanks.\nCorrect. This demo does not create an ELB so there is no external IP address. Access is via service proxy at the master. Type: and you should see the URLs for Elasticsearch and Kibana.\nplease let us know whether: a. Satnam's comment resolves your issue b. the demo should be updated to prevent this misunderstanding c. the issue isn't resolved Thank you!\nYes, Satnam's comment resolve the issue. I updated the demo in .\nAwesome, thanks for sending the patch! We'll discuss there. Always fantastic to have docs updated regularly by folks trying them.", "commid": "kubernetes_issue_7818", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2001ed9cebd868a45b35804b626f643da85b11a5a8a1c9ebfaa9bd104d7937b7", "query": "pod := makeLocalPodFunc(config, testVol, nodeName) pod, err := config.client.CoreV1().Pods(config.ns).Create(pod) Expect(err).NotTo(HaveOccurred()) <del> err = framework.WaitForPodRunningInNamespace(config.client, pod) Expect(err).To(HaveOccurred()) checkPodEvents(config, pod.Name, ep) </del> <ins> err = framework.WaitForPodNameUnschedulableInNamespace(config.client, pod.Name, pod.Namespace) Expect(err).NotTo(HaveOccurred()) </ins> cleanupLocalVolumes(config, []*localTestVolume{testVol}) }", "positive_passages": [{"docid": "doc-en-kubernetes-9df8e5ba2e9f919d9bec92d550979c4e420a21d16e91da208714cd0aae742f47", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /assign What happened: The tests are failing again because the scheduler messages have changed yet again. I'm going to remove the check for the exact messages because this is at least the 3rd time this has happened. Instead depend on unit/integration tests to check for specific failures. Also there's no need for these tests to run across all types of local volumes because it's just testing the scheduler part.", "commid": "kubernetes_issue_59369", "tokennum": 123}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2021b3a19299fbb79856088736edcf5a90bd608fd007709cb79a0eaedf0cd23b", "query": "// Checks whether stores for all clusters form the lists (and only these) are there and // are synced. func (fs *federatedStoreImpl) ClustersSynced(clusters []*federation_api.Cluster) bool { <del> fs.federatedInformer.Lock() defer fs.federatedInformer.Unlock() if len(fs.federatedInformer.targetInformers) != len(clusters) { </del> <ins> // Get the list of informers to check under a lock and check it outside. okSoFar, informersToCheck := func() (bool, []informer) { fs.federatedInformer.Lock() defer fs.federatedInformer.Unlock() if len(fs.federatedInformer.targetInformers) != len(clusters) { return false, []informer{} } informersToCheck := make([]informer, 0, len(clusters)) for _, cluster := range clusters { if targetInformer, found := fs.federatedInformer.targetInformers[cluster.Name]; found { informersToCheck = append(informersToCheck, targetInformer) } else { return false, []informer{} } } return true, informersToCheck }() if !okSoFar { </ins> return false } <del> for _, cluster := range clusters { if targetInformer, found := fs.federatedInformer.targetInformers[cluster.Name]; found { if !targetInformer.controller.HasSynced() { return false } } else { </del> <ins> for _, informerToCheck := range informersToCheck { if !informerToCheck.controller.HasSynced() { </ins> return false } }", "positive_passages": [{"docid": "doc-en-kubernetes-59d4410d28b628c1be3d77bd9cd1cfdd4f523921f65910962a77fbec070a39e8", "text": "https://k8s- Failed: TestNamespaceController {namespace}", "commid": "kubernetes_issue_30855", "tokennum": 20}], "negative_passages": []}
{"query_id": "q-en-kubernetes-20449776cd7fb5b6a76b89f0f014a2fa25fa328d5c6de83a015c4fcf2a781c58", "query": "package dns <del> import ( \"fmt\" \"os\" \"testing\" ) </del> var ( defaultResolvConf = \"/etc/resolv.conf\" // configurer.getHostDNSConfig is faked on Windows, while it is not faked on Linux. fakeGetHostDNSConfigCustom = getHostDNSConfig ) <del> // getResolvConf returns a temporary resolv.conf file containing the testHostNameserver nameserver and // testHostDomain search field, and a cleanup function for the temporary file. func getResolvConf(t *testing.T) (string, func()) { resolvConfContent := []byte(fmt.Sprintf(\"nameserver %snsearch %sn\", testHostNameserver, testHostDomain)) tmpfile, err := os.CreateTemp(\"\", \"tmpResolvConf\") if err != nil { t.Fatal(err) } cleanup := func() { os.Remove(tmpfile.Name()) } if _, err := tmpfile.Write(resolvConfContent); err != nil { cleanup() t.Fatal(err) } if err := tmpfile.Close(); err != nil { cleanup() t.Fatal(err) } return tmpfile.Name(), cleanup } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-5e93ba1a338583c6193506912a68a67fcc908451a37c483694071bc120df2bcb", "text": "When a --resolv-conf (DNS resolver config) is passed to kubelet on a Windows node, the config content is used as part of sandbox initialization (through getHostDNSConfig()). Now with the recent changes (), it seems now to fail with an error like: E0315 10:22:16. 4764 ] \"Error syncing pod, skipping\" err=\"failed to \"CreatePodSandbox\" for \"img-pull-(-b40a-459d-9033-)\" with CreatePodSandboxError: \"Failed to generate sandbox config for pod \"img-pull-(-b40a-459d-9033-)\": Unexpected resolver config value: \"C:etckubernetescni\". Expected \"\" or \"Host\".\"\" pod=\"img-puller-3842/img-pull-\" podUID=-b40a-459d-9033- This is showing on all the runs of GCE testgrid (latest): Reading/using the passed resolv config on Windows Run a Windows pool with DNS resolv config being set as part of kubelet params. No response_ 27 alpha.3 1.27 beta.0 master <detailsGCE </details<details</details<details</details<details</details<details</details\n/triage accepted /milestone v1.27 /sig node /sig network\n/sig windows /cc\n/priority criticial-urgent as this is likely a release blocking\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority criticial-urgent 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\n/priority critical-urgent\nHmm, so you're setting the [1]. This PR introduced the capability to read the DNS config options from the Windows host registries while removing the capability to read from a file, introducing a regression. I've sent a PR addressing this issue: [1]\nIs the file you are pointing to a UNIX-style or something else?\nWas the file changing the behavior of the node?", "commid": "kubernetes_issue_116782", "tokennum": 565}], "negative_passages": []}
{"query_id": "q-en-kubernetes-20449776cd7fb5b6a76b89f0f014a2fa25fa328d5c6de83a015c4fcf2a781c58", "query": "package dns <del> import ( \"fmt\" \"os\" \"testing\" ) </del> var ( defaultResolvConf = \"/etc/resolv.conf\" // configurer.getHostDNSConfig is faked on Windows, while it is not faked on Linux. fakeGetHostDNSConfigCustom = getHostDNSConfig ) <del> // getResolvConf returns a temporary resolv.conf file containing the testHostNameserver nameserver and // testHostDomain search field, and a cleanup function for the temporary file. func getResolvConf(t *testing.T) (string, func()) { resolvConfContent := []byte(fmt.Sprintf(\"nameserver %snsearch %sn\", testHostNameserver, testHostDomain)) tmpfile, err := os.CreateTemp(\"\", \"tmpResolvConf\") if err != nil { t.Fatal(err) } cleanup := func() { os.Remove(tmpfile.Name()) } if _, err := tmpfile.Write(resolvConfContent); err != nil { cleanup() t.Fatal(err) } if err := tmpfile.Close(); err != nil { cleanup() t.Fatal(err) } return tmpfile.Name(), cleanup } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-a55794e1d2c420cf7484c297920657922704eb45d045ae8237364febdd60d634", "text": "Yeah, what used on GCE/GKE, seems to be a Linux-like conf, eg: nameserver 10.128.0.1 search c.<project_name.internal google.internal ` We haven't tried to remove from kubelet to see the behavior.\nThis Issue/PR has been marked as release blocker. Please have the fix merged by eod today otherwise the feature has to be reverted. For the Issue/PR owner: please have a revert/feature disable PR open today in case the fix failed to get in. Thank you! See the -- Kubernetes 1.27 release manager\nI opened up a revert PR in case this PR does not merge by code freeze.\nThanks for the resolution! both 2019 and 2022 grids seems to be back to green now!\nThanks for confirming! I opened to ensure gets updated too", "commid": "kubernetes_issue_116782", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-20644f7f031ef6c8714dc2df2cab74c03aea4af1b81f26171d757f8b2fc3c201", "query": "return nil } <ins> // collectServiceNodePorts returns nodePorts specified in the Service. // Please note that: //   1. same nodePort with *same* protocol will be duplicated as it is //   2. same nodePort with *different* protocol will be deduplicated </ins> func collectServiceNodePorts(service *corev1.Service) []int { <del> servicePorts := []int{} for i := range service.Spec.Ports { servicePort := &service.Spec.Ports[i] if servicePort.NodePort != 0 { servicePorts = append(servicePorts, int(servicePort.NodePort)) </del> <ins> var servicePorts []int // map from nodePort to set of protocols seen := make(map[int]sets.String) for _, port := range service.Spec.Ports { nodePort := int(port.NodePort) if nodePort == 0 { continue } proto := string(port.Protocol) s := seen[nodePort] if s == nil { // have not seen this nodePort before s = sets.NewString(proto) servicePorts = append(servicePorts, nodePort) } else if s.Has(proto) { // same nodePort with same protocol servicePorts = append(servicePorts, nodePort) } else { // same nodePort with different protocol s.Insert(proto) </ins> } <ins> seen[nodePort] = s </ins> } <del> if service.Spec.HealthCheckNodePort != 0 { servicePorts = append(servicePorts, int(service.Spec.HealthCheckNodePort)) </del> <ins> healthPort := int(service.Spec.HealthCheckNodePort) if healthPort != 0 { s := seen[healthPort] // TODO: is it safe to assume the protocol is always TCP? if s == nil || s.Has(string(corev1.ProtocolTCP)) { servicePorts = append(servicePorts, healthPort) } </ins> } return servicePorts", "positive_passages": [{"docid": "doc-en-kubernetes-8c9ebf4e41021efd0692132f5b2f5e7ec08451127a302fc405c42cb972b9ed2e", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: I created several Workloads which require up to ten ports for both UDP and TCP protocol. Now my logs get spammed with . What you expected to happen: should consider -combination instead of only . How to reproduce it (as minimally and precisely as possible): Deploy any service with a node-port with both protocols, e.g.: Anything else we need to know?: This was already acknowledged by here: However, as this thread addresses a different bug and seems kind of stuck, i'd like to suggest that this might be addressed in a new context. Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Deployed via Rancher v2.4.3\n/sig api-machinery\n/remove-sig api-machinery /sig network\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nHow did you get into this situation? The allocator should not have granted the same node port twice?\nOh right, that issue. The only real way out is to de-allocate the NodePorts and then re-allocate them, I think\nAs this happens for all of my ports in the said Production Application (the one where my log gets spammed) as well as complete fresh installation (where i verified the bug), i think there's no \"way out\" except fixing the bug. As said, for me it's necessary to assign both protocols to the same port. This might be a niche-use-case, but checking the it's actually very likely for ports to allow tcp AND udp. I'm not sure about the history of this, but it might be that issue was the origin, which was adressed in PR (\"Allow services which use same port, different protocol to use the same nodePort for both\"). But this PR doesn't contain the adjustment of the said , so still considers the behaviour as invalid, while it's actually allowed and supported.", "commid": "kubernetes_issue_91404", "tokennum": 498}], "negative_passages": []}
{"query_id": "q-en-kubernetes-20644f7f031ef6c8714dc2df2cab74c03aea4af1b81f26171d757f8b2fc3c201", "query": "return nil } <ins> // collectServiceNodePorts returns nodePorts specified in the Service. // Please note that: //   1. same nodePort with *same* protocol will be duplicated as it is //   2. same nodePort with *different* protocol will be deduplicated </ins> func collectServiceNodePorts(service *corev1.Service) []int { <del> servicePorts := []int{} for i := range service.Spec.Ports { servicePort := &service.Spec.Ports[i] if servicePort.NodePort != 0 { servicePorts = append(servicePorts, int(servicePort.NodePort)) </del> <ins> var servicePorts []int // map from nodePort to set of protocols seen := make(map[int]sets.String) for _, port := range service.Spec.Ports { nodePort := int(port.NodePort) if nodePort == 0 { continue } proto := string(port.Protocol) s := seen[nodePort] if s == nil { // have not seen this nodePort before s = sets.NewString(proto) servicePorts = append(servicePorts, nodePort) } else if s.Has(proto) { // same nodePort with same protocol servicePorts = append(servicePorts, nodePort) } else { // same nodePort with different protocol s.Insert(proto) </ins> } <ins> seen[nodePort] = s </ins> } <del> if service.Spec.HealthCheckNodePort != 0 { servicePorts = append(servicePorts, int(service.Spec.HealthCheckNodePort)) </del> <ins> healthPort := int(service.Spec.HealthCheckNodePort) if healthPort != 0 { s := seen[healthPort] // TODO: is it safe to assume the protocol is always TCP? if s == nil || s.Has(string(corev1.ProtocolTCP)) { servicePorts = append(servicePorts, healthPort) } </ins> } return servicePorts", "positive_passages": [{"docid": "doc-en-kubernetes-33f53ed726ab1a89c68c77aae3b932484545b038842bda14047a639f615b725d", "text": "/assign\nAhh, I thought you meant that you had accidentally been allocated the same nodePorts and I was very confused when you said \"all of them\". I have reproduced this issue, and I can see it by inspection. The obvious fix would be to collect ports split by protocol, but I think that's not right since we don't store it split. An even simpler fix would be for to build a . Then for each protocol, for each port, build that contains all the port numbers, but remove any duplicates ONLY IF they are duplicated across protocols. Duplicates in the same protocol should be retained (to report an error later). I don't have time to tackle this tonight (and write a test), but it seems like a good bug.\nperhaps I can fix this problem /assign\nthings may be a little more complicated. Right now the is not aware of the protocol of the port so I guess simply rewriting function to return is not enough, the port allocator will still return on same node port even with different protocol. perhaps we need to refactor the to make it protocol-aware.\nI don't think we need to do make the allocator be protocol aware. IIRC we allow you to use the same nodeport on different protocols ONLY within a single service. This means (I think) that we can do hyper-local deduplication as we collect the nodeports for each service. If we find the same nodeport number with different protocols, just remove the duplicates because it is allowed. I.e. a service that looks like: return - deduped. if ANY OTHER service tried to use it would be an error at the \"rebuilt\" allocator Likewise if a single Service claims to use the same nodeport number more than once on the same protocol, it should be an error: return - NOT deduped.\nobviously, we want a great unit test here :P\nah got it! thanks for your detailed explanation!\nHi! I have filed a PR to resolve this issue, could you take a look?", "commid": "kubernetes_issue_91404", "tokennum": 428}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2067bd7357eed4575c725412c6b550bb8971334bfbddd59e1c36142533433575", "query": "if [[ ${ENABLE_METADATA_CONCEALMENT:-} == \"true\" ]]; then # Put the necessary label on the node so the daemonset gets scheduled. NODE_LABELS=\"${NODE_LABELS},cloud.google.com/metadata-proxy-ready=true\" <del> # TODO(liggitt): remove this in v1.16 NODE_LABELS=\"${NODE_LABELS},beta.kubernetes.io/metadata-proxy-ready=true\" </del> # Add to the provider custom variables. PROVIDER_VARS=\"${PROVIDER_VARS:-} ENABLE_METADATA_CONCEALMENT METADATA_CONCEALMENT_NO_FIREWALL\" fi", "positive_passages": [{"docid": "doc-en-kubernetes-2c9ef8984ebaf899659836b925069334113c910fc47ebe0516a7d659674f044a", "text": "xref In 1.16: change the metadata-proxy addon to use change the kube-proxy addon to use change the masq-agent addon to use stop setting , , and in kube-up\nHey I'm trying to start to contribute to kubernetes and this seem to be an easy task. Can I help with this one?", "commid": "kubernetes_issue_75050", "tokennum": 77}], "negative_passages": []}
{"query_id": "q-en-kubernetes-20755b820b118943e8b6c0684954dd80a58967530b05fce7fe84efc68f2288dc", "query": "} } <del> // TODO: remove when storage.k8s.io/v1beta1 is removed. func newBetaStorageClass(t testsuites.StorageClassTest, suffix string) *storagev1beta1.StorageClass { pluginName := t.Provisioner if pluginName == \"\" { pluginName = getDefaultPluginName() } if suffix == \"\" { suffix = \"default\" } return &storagev1beta1.StorageClass{ TypeMeta: metav1.TypeMeta{ Kind: \"StorageClass\", }, ObjectMeta: metav1.ObjectMeta{ GenerateName: suffix + \"-\", }, Provisioner: pluginName, Parameters:  t.Parameters, } } </del> func startGlusterDpServerPod(c clientset.Interface, ns string) *v1.Pod { podClient := c.CoreV1().Pods(ns)", "positive_passages": [{"docid": "doc-en-kubernetes-e2f4fe7b99012f8e7173e2f6c46ef5707967f19510033d4b6b03e3a31c7298f0", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --ci-kubernetes-e2e-gci-gce-slow [sig-storage] Dynamic Provisioning DynamicProvisioner [Slow] should provision storage with different parameters 5/13 https://k8s- v1beta1.StorageClass got removed in We should remove the v1beta1 test.\n/assign can you help take a look?\n/triage accepted\n/sig storage\nI run the test with the latest from master without removing the beta test and it failed with a different error before getting to the beta test part: Do you have any idea what would've happened in my setup? I redeployed k/k using master HEAD\nFor this testcase: I saw that the provisioned PD has a size of 1.5Gi according to kubernetes: And in gcloud It's really interesting that the test was expecting 2Gi to be created, is this something that was changed recently?\nThe logs you posted are showing pd csi as the provisioner. Were you testing with the intree driver or csi driver? The CSI driver should to the nearest Gb. I believe intree does the .\nI think I did intree because I didn't send as an argument in my command: It's interesting that the PVC has this annotation too:\nmmm something interesting about my setup is that I created the cluster with CSIMigration turned on Do you think that might be forcing the usage of ?\nYes likely. Try with CSIMigration off and see if that helps. If so, then this potentially seems like a rounding bug with the csi driver\nThanks I tried with and it did indeed round up to 2Gi.", "commid": "kubernetes_issue_102076", "tokennum": 373}], "negative_passages": []}
{"query_id": "q-en-kubernetes-207d42c5ead8381ec2fd086dd06c787fee7e6106138653455528c48dc87e51a4", "query": "<ins> /* Copyright 2019 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package etcd import ( \"context\" \"encoding/json\" \"testing\" \"time\" \"k8s.io/api/core/v1\" \"k8s.io/apimachinery/pkg/api/meta\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/apis/meta/v1/unstructured\" \"k8s.io/apimachinery/pkg/runtime/schema\" \"k8s.io/apimachinery/pkg/util/sets\" \"k8s.io/apimachinery/pkg/watch\" \"k8s.io/client-go/dynamic\" \"k8s.io/kubernetes/cmd/kube-apiserver/app/options\" ) // TestCrossGroupStorage tests to make sure that all objects stored in an expected location in etcd can be converted/read. func TestCrossGroupStorage(t *testing.T) { master := StartRealMasterOrDie(t, func(opts *options.ServerRunOptions) { // force enable all resources so we can check storage. // TODO: drop these once we stop allowing them to be served. opts.APIEnablement.RuntimeConfig[\"extensions/v1beta1/deployments\"] = \"true\" opts.APIEnablement.RuntimeConfig[\"extensions/v1beta1/daemonsets\"] = \"true\" opts.APIEnablement.RuntimeConfig[\"extensions/v1beta1/replicasets\"] = \"true\" opts.APIEnablement.RuntimeConfig[\"extensions/v1beta1/podsecuritypolicies\"] = \"true\" opts.APIEnablement.RuntimeConfig[\"extensions/v1beta1/networkpolicies\"] = \"true\" }) defer master.Cleanup() etcdStorageData := GetEtcdStorageData() crossGroupResources := map[schema.GroupVersionKind][]Resource{} master.Client.CoreV1().Namespaces().Create(&v1.Namespace{ObjectMeta: metav1.ObjectMeta{Name: testNamespace}}) // Group by persisted GVK for _, resourceToPersist := range master.Resources { gvk := resourceToPersist.Mapping.GroupVersionKind data, exists := etcdStorageData[resourceToPersist.Mapping.Resource] if !exists { continue } storageGVK := gvk if data.ExpectedGVK != nil { storageGVK = *data.ExpectedGVK } crossGroupResources[storageGVK] = append(crossGroupResources[storageGVK], resourceToPersist) } // Clear any without cross-group sources for gvk, resources := range crossGroupResources { groups := sets.NewString() for _, resource := range resources { groups.Insert(resource.Mapping.GroupVersionKind.Group) } if len(groups) < 2 { delete(crossGroupResources, gvk) } } if len(crossGroupResources) == 0 { // Sanity check t.Fatal(\"no cross-group resources found\") } // Test all potential cross-group sources can be watched and fetched from all other sources for gvk, resources := range crossGroupResources { t.Run(gvk.String(), func(t *testing.T) { // use the first one to create the initial object resource := resources[0] // compute namespace ns := \"\" if resource.Mapping.Scope.Name() == meta.RESTScopeNameNamespace { ns = testNamespace } data := etcdStorageData[resource.Mapping.Resource] // create object resourceClient, obj, err := JSONToUnstructured(data.Stub, ns, resource.Mapping, master.Dynamic) if err != nil { t.Fatal(err) } actual, err := resourceClient.Create(obj, metav1.CreateOptions{}) if err != nil { t.Fatal(err) } name := actual.GetName() // Set up clients, versioned data, and watches for all versions var ( clients       = map[schema.GroupVersionResource]dynamic.ResourceInterface{} versionedData = map[schema.GroupVersionResource]*unstructured.Unstructured{} watches       = map[schema.GroupVersionResource]watch.Interface{} ) for _, resource := range resources { clients[resource.Mapping.Resource] = master.Dynamic.Resource(resource.Mapping.Resource).Namespace(ns) versionedData[resource.Mapping.Resource], err = clients[resource.Mapping.Resource].Get(name, metav1.GetOptions{}) if err != nil { t.Fatalf(\"error finding resource via %s: %v\", resource.Mapping.Resource.GroupVersion().String(), err) } watches[resource.Mapping.Resource], err = clients[resource.Mapping.Resource].Watch(metav1.ListOptions{ResourceVersion: actual.GetResourceVersion()}) if err != nil { t.Fatalf(\"error opening watch via %s: %v\", resource.Mapping.Resource.GroupVersion().String(), err) } } for _, resource := range resources { // clear out the things cleared in etcd versioned := versionedData[resource.Mapping.Resource] versioned.SetResourceVersion(\"\") versioned.SetSelfLink(\"\") versionedJSON, err := versioned.MarshalJSON() if err != nil { t.Error(err) continue } // Update in etcd if _, err := master.KV.Put(context.Background(), data.ExpectedEtcdPath, string(versionedJSON)); err != nil { t.Error(err) continue } t.Logf(\"wrote %s to etcd\", resource.Mapping.Resource.GroupVersion().String()) // Ensure everyone gets a watch event with the right version for watchResource, watcher := range watches { select { case event, ok := <-watcher.ResultChan(): if !ok { t.Fatalf(\"watch of %s closed in response to persisting %s\", watchResource.GroupVersion().String(), resource.Mapping.Resource.GroupVersion().String()) } if event.Type != watch.Modified { eventJSON, _ := json.Marshal(event) t.Errorf(\"unexpected watch event sent to watch of %s in response to persisting %s: %s\", watchResource.GroupVersion().String(), resource.Mapping.Resource.GroupVersion().String(), string(eventJSON)) continue } if event.Object.GetObjectKind().GroupVersionKind().GroupVersion() != watchResource.GroupVersion() { t.Errorf(\"unexpected group version object sent to watch of %s in response to persisting %s: %#v\", watchResource.GroupVersion().String(), resource.Mapping.Resource.GroupVersion().String(), event.Object) continue } t.Logf(\"     received event for %s\", watchResource.GroupVersion().String()) case <-time.After(30 * time.Second): t.Errorf(\"timed out waiting for watch event for %s in response to persisting %s\", watchResource.GroupVersion().String(), resource.Mapping.Resource.GroupVersion().String()) continue } } // Ensure everyone can do a direct get and gets the right version for clientResource, client := range clients { obj, err := client.Get(name, metav1.GetOptions{}) if err != nil { t.Errorf(\"error looking up %s after persisting %s\", clientResource.GroupVersion().String(), resource.Mapping.Resource.GroupVersion().String()) continue } if obj.GetObjectKind().GroupVersionKind().GroupVersion() != clientResource.GroupVersion() { t.Errorf(\"unexpected group version retrieved from %s after persisting %s: %#v\", clientResource.GroupVersion().String(), resource.Mapping.Resource.GroupVersion().String(), obj) continue } t.Logf(\"     fetched object for %s\", clientResource.GroupVersion().String()) } } }) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-7ee140198c665b218e0dfb7e3cd2f2624912887cfcfab5f30828d12c6130aa35", "text": "What happened: Set up a HA cluster with 1.9 and 1.10 API servers (occurs on any apiserver skew boundary where a cohabitating resource's storage version changed groups) Observed errors when modifying workload objects: when modified via the 1.10 server, saw this error in the 1.9 server: when modified via the 1.9 server, saw this error in the 1.10 server: When this error was encountered, all watchers for the resource in question would be dropped and have to re-establish, and the internal watchers feeding the watch cache would drop and re-establish What you expected to happen: Watch events from all supported storage versions are processed correctly How to reproduce it (as minimally and precisely as possible): Start a server from master (for inspectability, store in json). With Create a deployment (e.g. kube-dns in kube-system) Establish a watch via extensions (kubectl get deployments.extensions --all-namespaces -w) Establish a watch via apps (kubectl get --all-namespaces -w) Tail the kube-apiserver log Change the apps/v1 deployment in etcd to extensions/v1beta1: Observer client watches drop and server log errors: Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: /sig api-machinery /cc /priority critical-urgent\nerror is triggered by this returning false: constructed here: the info about expected cohabitating groups is not included in the list of acceptable inputs", "commid": "kubernetes_issue_73478", "tokennum": 368}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2082ac15f6072b35699360e69a19216dee7be2563d9dd8a7b08f9c84789ac4c5", "query": "import ( \"net/http\" <ins> \"os\" </ins> \"path/filepath\" \"github.com/gregjones/httpcache\"", "positive_passages": [{"docid": "doc-en-kubernetes-30e07950978ed617c12104c8342559dfe477718ba7eb61f98c21f95bb37c1439", "text": "In kubectl v1.8.0+, schema info is cached in the location specified by (defaulting to ), written with world-writeable permissions (rw-rw-rw-). If is specified and pointed at a different location accessible to other users/groups, the written files may be modified by other users/groups and disrupt the kubectl invocation. CVSS score: CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N (3.3, low) What versions are affected? kubectl v1.8.0+ What configurations are affected? Invocations that point at world-writeable locations Impact Malformed responses written to the cache directory can disrupt the kubectl invocation Workaround Use the default location in the $HOME directory or point it at a directory that is only accessible to desired users/groups. (original description follows) ==== What happened: The files inside of \".kube/http-cache\" are world writeable (rw-rw-rw-). While the default for these files appears to be the home directory, using the \"--cache-dir\" flag could put these files into a place where world writeable files would allow any user / process to modify the cache files. Modification of the cache files could influence the kubectl utility in a negative way for other users. What you expected to happen: Apply stricter file permissions to the http-cache files. How to reproduce it (as minimally and precisely as possible): Run any generic kubectl command which is successful and then list the cache directory $ kubectl get pods --all-namespaces $ ls -la Anything else we need to know?", "commid": "kubernetes_issue_76676", "tokennum": 398}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2082ac15f6072b35699360e69a19216dee7be2563d9dd8a7b08f9c84789ac4c5", "query": "import ( \"net/http\" <ins> \"os\" </ins> \"path/filepath\" \"github.com/gregjones/httpcache\"", "positive_passages": [{"docid": "doc-en-kubernetes-03c8940a04bf023e0d3632a105949b7e85efda694ffafea56ecb99998a766122", "text": ": I estimate this is a low severity security issue with a CVSS score of \"3.3 / CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N\" - Environment: Linux Kubernetes version (use kubectl version):Client Version: version.Info{Major:\"1\", Minor:\"12\", GitVersion:\"v1.12.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2019-02-26T12:49:28Z\", GoVersion:\"go1.10.8\", Compiler:\"gc\", Platform:\"linux/amd64\"} Server Version: version.Info{Major:\"1\", Minor:\"12\", GitVersion:\"v1.12.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2019-02-26T12:49:28Z\", GoVersion:\"go1.10.8\", Compiler:\"gc\", Platform:\"linux/amd64\"} Cloud provider or hardware configuration: AWS. Running kube api server in hyperkube. OS (e.g: cat /etc/os-release): NAME=\"CentOS Linux\" VERSION=\"7.1808 (Core)\" ID=\"centos\" IDLIKE=\"rhel fedora\" VERSIONID=\"7\" PRETTYNAME=\"CentOS Linux 7.1808 (Core)\" ANSICOLOR=\"0;31\" CPENAME=\"cpe:/o:centos:centos:7\" HOMEURL=\"\" BUGREPORTURL=\"\" CENTOSMANTISBTPROJECT=\"CentOS-7\" CENTOSMANTISBTPROJECTVERSION=\"7\" REDHATSUPPORTPRODUCT=\"centos\" REDHATSUPPORTPRODUCTVERSION=\"7\" OSTREEVERSION=7.1808 Kernel (e.g. uname -a): Linux hackit.internal 3.10.0-862.11.6.el7.x8664 SMP Tue Aug 14 21:49:04 UTC 2018 x8664 x8664 x86_64 GNU/Linux Install tools: Manual installation. Others: n/a\n/sig product-security\nClosing this issue. <detailsIn response to : if you think this is serious, send an email thanks!", "commid": "kubernetes_issue_76676", "tokennum": 565}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2082ac15f6072b35699360e69a19216dee7be2563d9dd8a7b08f9c84789ac4c5", "query": "import ( \"net/http\" <ins> \"os\" </ins> \"path/filepath\" \"github.com/gregjones/httpcache\"", "positive_passages": [{"docid": "doc-en-kubernetes-5f4971cee99e57062ae7961121de35cc677214a3e6ca77682b093e74b00a9b30", "text": "</details\nAdjusted the CVSS score to to indicate user interaction is required (since they must specify a non-default cache option pointed at a shared writeable location)\nThere are two places this should be done: PathPerm and FilePerm should be set here: the temp file and final file should have stricter permissions (probably 0660) here:\n/cc\n/help\nThis request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\n/assign I would like to work on release-1.9, as I just made a hot fix for our team's k8s version of 1.9.\nGitHub didn't allow me to assign the following users: yuchengwu. Note that only and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign I would like to work on release-1.9, as I just made a hot fix for our team's k8s version of 1.9. 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\nhelp fixing this is welcome, though it would only be fixed in releases 1.12+, per\n/label official-cve-feed (Related to kubernetes/sig-security)", "commid": "kubernetes_issue_76676", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2084b574a2d8820dba17cf7241bdf20ff36ed91808a88f77c50375eaa907ae0c", "query": "wg.Add(2) go func() { <del> defer h.t.Logf(\"Server read close, host=%s\", req.Host) </del> defer wg.Done() <ins> defer h.t.Logf(\"Server read close, host=%s\", req.Host) </ins> io.Copy(conn, sconn) }() go func() { <del> defer h.t.Logf(\"Server write close, host=%s\", req.Host) </del> defer wg.Done() <ins> defer h.t.Logf(\"Server write close, host=%s\", req.Host) </ins> io.Copy(sconn, conn) }()", "positive_passages": [{"docid": "doc-en-kubernetes-27809a3a2eb2b85924d4f4faf65a841d86c20af577cb16fb38fbd54d281dded1", "text": "release-master-blocking ci-kubernetes- Sub-tests: - ! 2023-01-20 09:17:28 +0000 UTC TestRoundTripSocks5AndNewConnection/proxiedwithvalidauth-https(invalidhostname+InsecureSkipVerify)TestRoundTripSocks5AndNewConnection/proxiedwithvalidauth-http /sig api-machinery cc\n/assign /triage accepted Will be fixed by Thanks for noticing, great report by the way", "commid": "kubernetes_issue_115232", "tokennum": 116}], "negative_passages": []}
{"query_id": "q-en-kubernetes-208fa6b82243bf60716077cd0a0fc447913c0a72d6e846bb88a846509eab05cd", "query": "package main import ( <del> \"fmt\" </del> \"os\" \"k8s.io/klog\"", "positive_passages": [{"docid": "doc-en-kubernetes-0b2213d42768c43adcb1b4f15cf67b8722c82d28c3ec9792f5837d41705eb847", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: kubectl version --client=yes command is giving the following error message. Error message is repeated at the start and the end and also containing programming jargon Error: invalid argument \"yes\" for \"--client\" flag: strconv.ParseBool: parsing \"yes\": invalid syntax Examples: Print the client and server versions for the current context kubectl version Options: --client=false: Client version only (no server required). -o, --output='': One of 'yaml' or 'json'. --short=false: Print just the version number. Usage: kubectl version [flags] [options] Use \"kubectl options\" for a list of global command-line options (applies to all commands). invalid argument \"yes\" for \"--client\" flag: strconv.ParseBool: parsing \"yes\": invalid syntax What you expected to happen: The error message can be improved with one of the two variants invalid argument \"yes\" for \"--client\" flag Examples: Print the client and server versions for the current context kubectl version Options: --client=false: Client version only (no server required). -o, --output='': One of 'yaml' or 'json'. --short=false: Print just the version number. Usage: kubectl version [flags] [options] Use \"kubectl options\" for a list of global command-line options (applies to all commands). (or) Invalid argument \"yes\" for \"--client\" flag How to reproduce it (as minimally and precisely as possible): Run the command kubectl version --client=yes Anything else we need to know?: Environment: Kubernetes version (use ): 1.15 Cloud provider or hardware configuration: AWS OS (e.g: ): Amazon Linux Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig cli\nHi Thanks for posting this issue! It turns out that this duplicate output has been in kubectl, and all the other cli cmds, since . This should be fixed by , and hopefully we can cherry pick it back to at least .", "commid": "kubernetes_issue_79454", "tokennum": 560}], "negative_passages": []}
{"query_id": "q-en-kubernetes-209a4c2f7c9a35aa8cecfcf12667d1271da908875771ee01d637239a8c436db7", "query": "// Updates from all sources AllSource = \"*\" <del> // Used for ConfigMirrorAnnotationKey. MirrorType = \"mirror\" </del> NamespaceDefault = api.NamespaceDefault )", "positive_passages": [{"docid": "doc-en-kubernetes-8bc8d69d49aedfb4a9bf3991de80f7c339e96bfbefe5b1f250dae70fa0393729", "text": "See for more context. Currently, kubelet compares the spec of a mirror pod (created via apiserver) with that of a static pod (config stored as a file) to decide whether the two are considered identical. If they differ, kubelet would delete the mirror pod and re-create it with the correct spec. Due to the fact that apiserver may set default values for some fields in the spec of the mirror pod, the specs could deviate undesirably. To avoid problems like this, we can store the config of a static pod as an annotation in the mirror pod, and compare the static pod with the annotation.\nWould a hash of the config be sufficient if we're only going to compare? The whole spec would generally be more useful, but I wonder if that is too much data to put in an annotation.\nThis seems totally reasonable to me, but I'm still desperately curious why you can't just bypass defaulting when you generate mirror pod from static pod? (i.e. just use the static pod's configuration verbatim)\nIt's not kubelet who applies the default values here. The admission plugin was only run at the apiserver, and to bypass that, you have to ask apiserver to treat mirror pods differently and potentially at multiple places.\nOn May 22, 2015 10:38 AM, \"Yu-Ju Hong\" wrote: Understood, but is it really multiple places? If so then I agree it's a bad idea. Otherwise it might be worth considering as an alternative.\nIt's untenable for Kubelet to assume to know/circumvent all fields that will be set by other entities: admission control, defaulting, late initialization, auto-something, whatever. It needs to obey the same rules as other clients.\nI don't understand why you would ever want to apply any of the things you mentioned to static pods. Static pods should be copied verbatim into the mirror pods, right? That's what I'm proposing.\nWhat if the master is updated before the kubelet, and the master adds a new API field with a default value?\nThat case should be discussed in\nI agree that mirror pod should reflect the true status of the static pod running on the node, and no default values should be set in this case.", "commid": "kubernetes_issue_8683", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-209a4c2f7c9a35aa8cecfcf12667d1271da908875771ee01d637239a8c436db7", "query": "// Updates from all sources AllSource = \"*\" <del> // Used for ConfigMirrorAnnotationKey. MirrorType = \"mirror\" </del> NamespaceDefault = api.NamespaceDefault )", "positive_passages": [{"docid": "doc-en-kubernetes-0491e123884f0f20f50d0a788bca7a6a29e2fa08227703a00221ecbd3bcf483c", "text": "However, I think it'd be harder to implement this way since, as stated above, that there are many things to circumvent in the apiserver itself. It could also be harder to keep this special case from being broken by a yet another new feature/plugin. Keeping the hash of the config in the annotation seems like a good compromise even though it may not reflect the true status 100% accurately. I think this is acceptable. What do you think?\nSure, if you think the annotation approach is easier, I would go with that. I guess in the case Brian mentoined (master adds a new API field with a default value), you would not update the mirror pod, because the static pod definition has not changed?\nYes, a hash would be sufficient.\nIt shouldn't be necessary to update the mirror pod in the case that a new default field was updated, because that field should be populated automatically by the apiserver on decode from etcd.\nWe should fix this so we don't have this problem again in 1.2.", "commid": "kubernetes_issue_8683", "tokennum": 226}], "negative_passages": []}
{"query_id": "q-en-kubernetes-20ba5885de8567ca531b4577af02a555e32ae50637d3355dbd5ccede895f46df", "query": "}) } } <ins> func TestMicroTimeUnmarshalJSONAndProtoEqual(t *testing.T) { cases := []struct { name   string input  MicroTime result bool }{ {\"nanosecond level precision\", UnixMicro(123, 123123123), true}, {\"microsecond level precision\", UnixMicro(123, 123123000), true}, } for _, c := range cases { t.Run(c.name, func(t *testing.T) { jsonData, err := c.input.MarshalJSON() if err != nil { t.Fatalf(\"Failed to marshal input to JSON: '%v': %v\", c.input, err) } protoData, err := c.input.Marshal() if err != nil { t.Fatalf(\"Failed to marshal input to proto: '%v': %v\", c.input, err) } var tJSON, tProto MicroTime if err = tJSON.UnmarshalJSON(jsonData); err != nil { t.Fatalf(\"Failed to unmarshal JSON: '%v': %v\", jsonData, err) } if err = tProto.Unmarshal(protoData); err != nil { t.Fatalf(\"Failed to unmarshal proto: '%v': %v\", protoData, err) } result := tJSON.Equal(&tProto) if result != c.result { t.Errorf(\"Failed equality test for '%v': expected %+v, got %+v\", c.input, c.result, result) } }) } } func TestMicroTimeProtoUnmarshalRaw(t *testing.T) { cases := []struct { name     string input    []byte expected MicroTime }{ // input is generated by Timestamp{123, 123123123}.Marshal() {\"nanosecond level precision\", []byte{8, 123, 16, 179, 235, 218, 58}, UnixMicro(123, 123123000)}, // input is generated by Timestamp{123, 123123000}.Marshal() {\"microsecond level precision\", []byte{8, 123, 16, 184, 234, 218, 58}, UnixMicro(123, 123123000)}, } for _, c := range cases { t.Run(c.name, func(t *testing.T) { var actual MicroTime if err := actual.Unmarshal(c.input); err != nil { t.Fatalf(\"Failed to unmarshal proto: '%v': %v\", c.input, err) } if !actual.Equal(&c.expected) { t.Errorf(\"Failed unmarshal from nanosecond-precise raw for '%v': expected %+v, got %+v\", c.input, c.expected, actual) } }) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-56cd908854c413b8fe52b6acbb170713ddc1a064a7bd9d42b4a3ba81ae7efcaf", "text": "Found some error logs when sending series events to apiserver: seems the later eventTime differed from the first one in series events After investigation, I found the problem was in the marshal. MicroTime is supposed to work on microsecond level precision, but init with nanosecond level precision, in this case, generates microsecond level precision data and generates nanosecond level precision, so when unmarshalled, the new time is not considered the exactly same as the original time (they are different at nanosecond level) MicroTime marshal should work at same precision for json and proto, so unmarshal can generate the exactly same MicroTime result: This causes the series events won't be updated on api-server after created master <details</details<details</details<details</details<details</details<details</details\n/sig api-machinery\n/assign\nGood catch... we'd probably need to truncate to microseconds when marshaling and unmarshaling proto to ensure any already persisted data is fixed up when read. Something like this:\nThanks for advice, going to send a PR soon", "commid": "kubernetes_issue_111928", "tokennum": 247}], "negative_passages": []}
{"query_id": "q-en-kubernetes-20c2115c51612a9a0f77edaf49488e2efc8a474deed3a4fa5de90fc63a2d357d", "query": "// DiskIsAttached checks if a disk is attached to the given node. // Assumption: If node doesn't exist, disk is not attached to the node. <del> DiskIsAttached(volPath string, nodeName k8stypes.NodeName) (bool, error) </del> <ins> DiskIsAttached(volPath string, nodeName k8stypes.NodeName) (bool, string, error) </ins> // DisksAreAttached checks if a list disks are attached to the given node. // Assumption: If node doesn't exist, disks are not attached to the node.", "positive_passages": [{"docid": "doc-en-kubernetes-e1df151812a738ca8d7e9f97519d671c643638f3ca9d9400cc430f5f7a7d204c", "text": "When user creates a static PV using folder name in path: on vSAN backed datastore then detach disk does not work because check fails - The code expects folder name to be UUID but it does not and hence it determines disk is not attached to the node and hence no detach is ever performed. /sig storage cc", "commid": "kubernetes_issue_95121", "tokennum": 68}], "negative_passages": []}
{"query_id": "q-en-kubernetes-211b6f396954d907f6360abfd575066df68ba296add27e1d080b8facd977f2b9", "query": "} // Step 3: If the container logs directory does not exist, create it. <del> if _, err := os.Stat(containerLogsDir); err != nil { if err := kl.os.MkdirAll(containerLogsDir, 0755); err != nil { glog.Errorf(\"Failed to create directory %q: %v\", containerLogsDir, err) </del> <ins> if _, err := os.Stat(ContainerLogsDir); err != nil { if err := kl.os.MkdirAll(ContainerLogsDir, 0755); err != nil { glog.Errorf(\"Failed to create directory %q: %v\", ContainerLogsDir, err) </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-0ad427ca9c00c618017f4be9fb19a1df6f4ab39ddc68f128fc109eb4d0409cbf", "text": "Cluster logging assumes kubelet stores container log at a specific directory with specific name. Currently the path is: After the CRI work, the path will be: However, we don't have test coverage for this. We don't even know whether the log files are there or not. We should add a node e2e test for this, basically: 1) Create a container which prints logs 2) Check whether the expected log file is created. 3) Check whether the logs are collected in the file as expected. And it would be better to launch a pod to do the check instead of accessing local file system directly, which makes containerizing easier. /cc because you are collecting missing test. /cc\nI will try to add a node-e2e test there\nI think it's ok to add this for CRI. But there maybe problems on today's interface for rkt. If I'm not wrong, rkt does't store logs at same location with docker. cc/ Is this true?\nThanks! :)\nAfter gets merged, we need to update the test to verify the cri log path.", "commid": "kubernetes_issue_34661", "tokennum": 234}], "negative_passages": []}
{"query_id": "q-en-kubernetes-212cfe3f98ddeb9e62d410627435edd27ded28d6c7ecbe0928ecf24f07248075", "query": "apiServiceLister listers.APIServiceLister apiServiceSynced cache.InformerSynced <del> // serviceLister is used to get the IP to create the transport for serviceLister  v1listers.ServiceLister servicesSynced cache.InformerSynced </del> // To allow injection for testing. syncFn func(key string) error queue workqueue.RateLimitingInterface } <del> func NewAPIServiceRegistrationController(apiServiceInformer informers.APIServiceInformer, serviceInformer v1informers.ServiceInformer, apiHandlerManager APIHandlerManager) *APIServiceRegistrationController { </del> <ins> func NewAPIServiceRegistrationController(apiServiceInformer informers.APIServiceInformer, apiHandlerManager APIHandlerManager) *APIServiceRegistrationController { </ins> c := &APIServiceRegistrationController{ apiHandlerManager: apiHandlerManager, apiServiceLister:  apiServiceInformer.Lister(), apiServiceSynced:  apiServiceInformer.Informer().HasSynced, <del> serviceLister:     serviceInformer.Lister(), servicesSynced:    serviceInformer.Informer().HasSynced, </del> queue:             workqueue.NewNamedRateLimitingQueue(workqueue.DefaultControllerRateLimiter(), \"APIServiceRegistrationController\"), }", "positive_passages": [{"docid": "doc-en-kubernetes-89e8d863e20723ba6498e9abf897dd4e49e26cad02c0dde0a4957b2eb3151e69", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Currently APIServiceRegistrationController watch service change and find the related APIServices related if any. Then it AddAPIService/RemoveAPIService for APIAggregator. I dig into the kube-aggregator and find it no need totally, because update APIServices status when related service or endpoint change. So if does not watch services, it will not miss any event for APIServices. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/cc\n/kind enhancement /sig api-machinery\n/assign\nthat does not follow. AvailableConditionController modifies the APIService object. APIServiceRegistrationController must still watch the APIService objects to observe those changes.\noh, I misread the description. You're saying APIServiceRegistrationController doesn't need to watch v1.Service objects", "commid": "kubernetes_issue_57836", "tokennum": 300}], "negative_passages": []}
{"query_id": "q-en-kubernetes-21503dff10bbde6433e81a7d6785891088641408bc5dce5ab3a805582765b809", "query": "if err != nil { t.Fatalf(\"unexpected error %v\", err) } err = c.Convert(&A{}, &C{}, 0, nil) if err == nil { t.Errorf(\"unexpected non-error\")", "positive_passages": [{"docid": "doc-en-kubernetes-518f837785f17a5fd9706a6c0a0614adac703d65f6bb6045d79a025795dcb97b", "text": "Files storing latest versions for minors are not updated since infix was to the version string. Example Similar issues can be found in 1.25 and 1.24 builds (last 1.23 build infix so it has not happened there yet): I expect the files to be overwritten with newer version of the build. Manually run build job for one of the minors. No response Not related. Not related. No response No response No response No response\nI believe this may be also responsible for breaking kubemark tests: since they fail due to version mismatch\n/sig release\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority high 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\nThanks for raising the issue! /cc who is working on before\nI assume this will be fixed automatically with the next patches, because then we would compare with . Anyway, I think we should fix that intermediately by manually updating the version markers to match their correct version. I did that now for the bucket\nWe had to update the versions markers again, because those were pointing to two commits earlier and didn't include the Go updates. The latest version markers are: v1.24.12-35+ v1.25.8-37+ v1.26.3-41+\nlatest-1.27 has been affected by this as well. I updated it manually to v1.27.0-9+. See this thread for more details:\n/triage accepted\nThis should be fixed now, closing it. Feel free to reopen if we missed anything.\nThis issue is still present, see this Slack thread for more details: /reopen\nReopened this issue. <detailsIn response to : This issue is still present, see this Slack thread for more details: /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nWe have a similar situation with latest-1.28 which is currently pointing to: . This is one commit before the release commit: ! It's mostly like that the release step didn't update version markers, we should look into this.", "commid": "kubernetes_issue_117115", "tokennum": 486}], "negative_passages": []}
{"query_id": "q-en-kubernetes-21503dff10bbde6433e81a7d6785891088641408bc5dce5ab3a805582765b809", "query": "if err != nil { t.Fatalf(\"unexpected error %v\", err) } err = c.Convert(&A{}, &C{}, 0, nil) if err == nil { t.Errorf(\"unexpected non-error\")", "positive_passages": [{"docid": "doc-en-kubernetes-5a00e106d863b6b2d6ffe122805a64f76a2709c3a46b9a75024b175401623671", "text": "As of now, I'm going to manually update this version marker to unblock 1.28.1 patch release. I'll also take a look into this. /assign\nThe PR that fixed this issue got reverted so this is still relevant: /reopen\nReopened this issue. <detailsIn response to : The PR that fixed this issue got reverted so this is still relevant: /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nWe're running into this issue again with stable-1.29 marker. It's currently pointing to which is It should instead point to I'm going to manually change it following the same procedure as the last time. Version marker updated to\nThis issue is labeled with but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release. You can: Confirm that this issue is still relevant with (org members only) Deprioritize it with or Close this issue with For more details on the triage process, see /remove-triage accepted\n/triage accepted\nSame issue for 1.30, where I had to update the version marker manually again.", "commid": "kubernetes_issue_117115", "tokennum": 278}], "negative_passages": []}
{"query_id": "q-en-kubernetes-215daaa443ac04ded78101329a37955d1ceb03b013bf1bd108b7989e8ae951e6", "query": "<del> kind: ReplicationController apiVersion: v1 </del> <ins> apiVersion: extensions/v1beta1 kind: Deployment </ins> metadata: name: etcd-discovery <del> creationTimestamp: </del> spec: strategy: type: Recreate <del> resources: {} triggers: - type: ConfigChange </del> replicas: 1 selector: <del> name: etcd-discovery </del> <ins> matchLabels: name: etcd-discovery </ins> template: metadata: <del> creationTimestamp: </del> labels: name: etcd-discovery spec:", "positive_passages": [{"docid": "doc-en-kubernetes-970debf69dc4e7e663c051298279ebf93b58654f6c393d8683796c73cb4f1c74", "text": "Kubernetes version (use ): Environment: Cloud provider or hardware configuration: Vagrant OS (e.g. from /etc/os-release): CoreOS Kernel (e.g. ):Install tools: Vagrant & Others: What happened: What you expected to happen: Success How to reproduce it (as minimally and precisely as possible): Followed instructions at Tried to run Received: Anything else do we need to know: From googling, it seems several of the fields in the config are for when using OpenShift origin. But creating the replication controller is a prerequisite to launching OpenShift Origin. Chicken & egg problem.", "commid": "kubernetes_issue_39575", "tokennum": 138}], "negative_passages": []}
{"query_id": "q-en-kubernetes-217bad504aaadadbf0caaf6967eb7c10dc16a6bf03c32792de7c5bb5ea57373d", "query": "bashExec, exitCode, err) } } <del> gomega.Expect(err).To(gomega.HaveOccurred(), \"%q should fail with exit code %d, but exit without error\", bashExec, exitCode) </del> <ins> framework.ExpectError(err, \"%q should fail with exit code %d, but exit without error\", bashExec, exitCode) </ins> } // KubeletCommand performs `start`, `restart`, or `stop` on the kubelet running on the node of the target pod and waits", "positive_passages": [{"docid": "doc-en-kubernetes-c082543f1889f90c5ee780d309eeb8f41ee57a7e9e8bb6b6fe7c2e4381ff48af", "text": "What happened: After fixing golint failures under (now still in progress), we need to put for each and . Then common error checking code has become like: We can replace this code with which is more readable and easy to be understood what the code does. Now we have following e2e test directories which can be replaced: [x] test/e2e/apimachinery/ () [x] test/e2e/apps/ () [x] test/e2e/auth/ () [x] test/e2e/common/ () [x] test/e2e/node/ () [x] test/e2e/storage/ () [x] () [x] () [x] () [x] () [x] () [x] () [x] [x] test/e2e/storage/persistentvolumes- [x] () [x] () [x] [x] [x] [x] [x] ()\n/sig testing /kind cleanup\n/assign PR will be submitted soon.\nFix the following in\nFix in\nFix in\nHi, maybe I could take files beneath test/e2e/storage/vsphere/\noops, I'm finished and prepare for PR.\nThank you That's OK\nFix the following in\n/assign\nAll related PRs were merged. I think this ticket can be closed. BTW, should we also replace to ?\nThanks for your work. thing is managed with We are almost finishing the work also :-)\n/remove-kind bug\nI found in these files. I'm working on :\nI can work to the following item.", "commid": "kubernetes_issue_77706", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2184649ac33f69d2ac29e41cca9412e80e7223e9b981c4c74d8eb3d58bd68c64", "query": "e2eservice \"k8s.io/kubernetes/test/e2e/framework/service\" e2eskipper \"k8s.io/kubernetes/test/e2e/framework/skipper\" testutil \"k8s.io/kubernetes/test/utils\" <ins> imageutils \"k8s.io/kubernetes/test/utils/image\" </ins> utilpointer \"k8s.io/utils/pointer\" )", "positive_passages": [{"docid": "doc-en-kubernetes-cea21dfbf74ea26aea8b8fcc0c8d9d3e2b3e4488cd9f6d30773b87652fe6e220", "text": "[x] Original approval issue: [x] Test pr: [x] Two weeks soak end date: 19 November 2020 This issue is created to allow edit by /wip /hold According to this APIsnoop query, there are still some remaining Deployment endpoints which are untested. a Deployment with a static label the Deployment with a new Label and updated data the Deployment to ensure it's patched all Deployments in all Namespaces find the Deployment(1) ensure that the Deployment is found and is patched Namespaced Deployment(1) via a Collection with a LabelSelector Discover useragents: List endpoints hit by the test: Display endpoint coverage change: If a test with these calls gets merged, test coverage will go up by 5 points* This test is also created with the goal of conformance promotion.\n/sig testing /sig architecture /area conformance\nBobyMcbobs commented in original Issue: Unsure if the endpoint replaceAppsV1NamespacedDeploymentStatus is able to be hit. When this endpoint is attempted to be updated the data after retrieving the update resource doesn't reflect the values in the update\n/assign\nWhen using the appv1.Deployment structure instead of maps of interfaces to build the structure in a patch of the Deployment, this error comes up. Still in progress yment-static\":\"true\"}: does not match template , spec.selector: Invalid value: \"null\": field is immutable]\nreplaceAppsV1NamespacedDeploymentStatus to test. Increase cover by 1 Endpoint\n/reopen PR reverted by due to flaky test\nReopened this issue. <detailsIn response to : /reopen PR reverted by due to flaky test 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\nIssues 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\n/reopen Soaking, ready for promotion 19 November 2020\nReopened this issue. <detailsIn response to : /reopen Soaking, ready for promotion 19 November 2020 Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_90916", "tokennum": 522}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2184649ac33f69d2ac29e41cca9412e80e7223e9b981c4c74d8eb3d58bd68c64", "query": "e2eservice \"k8s.io/kubernetes/test/e2e/framework/service\" e2eskipper \"k8s.io/kubernetes/test/e2e/framework/skipper\" testutil \"k8s.io/kubernetes/test/utils\" <ins> imageutils \"k8s.io/kubernetes/test/utils/image\" </ins> utilpointer \"k8s.io/utils/pointer\" )", "positive_passages": [{"docid": "doc-en-kubernetes-ff9ccf83336a9bf28b0576a991dfda56392cc48f280c272644ff154877b8104d", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/remove-lifecycle stale\n/triage accepted\n/merged", "commid": "kubernetes_issue_90916", "tokennum": 34}], "negative_passages": []}
{"query_id": "q-en-kubernetes-21a0487a65b5071921fb9cdae2d2bafa73ebdbf2783df2c1e6fd147a47ae50ae", "query": "// if you set fire time at X, you can get the bookmark within (X-1,X+1) period. // This is NOT thread-safe. type watcherBookmarkTimeBuckets struct { <ins> lock            sync.Mutex </ins> watchersBuckets map[int64][]*cacheWatcher startBucketID   int64 clock           clock.Clock", "positive_passages": [{"docid": "doc-en-kubernetes-c66c9bab938b839459ac01dfd08140ea19c2b9a1199fe50a2b49f94fd9cbbbfb", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: I try to backport bookmark feature to our internal branch. When I enable bookmark feature, apiserver leaks memory. I spend some time to dig the root cause and find the bookmarkWatchers of service cacher is keep increasing. I am not sure if it exists at upstream code. Please let me know if it is ok at latest code. What you expected to happen: Avoid memory leaking How to reproduce it (as minimally and precisely as possible): a cluster. not update service. will find kube-apiserver's memory keep increasing. Anything else we need to know?: Kubelet will watch service with bookmark, and add a watcher to bookmarkWatchers. and service init resource version is 0 Without updating service, we cannot update \"lastProcessedResourceVersion\", it will keep 0, bookmarkTimer branch will always be continued. As a result, it cannot trigger popExpiredWatchers, so the service watcher will keep increasing every watching. Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig scalability PLAT :)\nHow about making this change ?\n- can you also please take a look?\nAgree with u. That's same way I fix in our branch. But I wanna hear the suggestion of and .\n! With the same bugfix wrote above, we can see the memory not increasing any more.\nGiven that watch-bookmarks doesn't create any additional go-routines (well, creates 1, but cannot leak them), it has to leak the data. The only data that can be leaked is exactly bookmarkWatchers. So I looked into the code and got into exactly the same conclusion - that we must be leaking watchers for resources that aren't changing. The fix as above makes sense (though we also need a unit test for it).\nThanks a lot.\nhas the fix by\nThanks for reporting the bug, I will look at this day later. In addition, also need to think carefully about whether need to send a bookmark when there are no events at all.\ncc", "commid": "kubernetes_issue_80690", "tokennum": 531}], "negative_passages": []}
{"query_id": "q-en-kubernetes-21d43009be64457f394da32805722837fb85588127d725bfa675030e463968ba", "query": "return true, err } <ins> // scaleDownOldRCsForRecreate scales down old rcs when deployment strategy is \"Recreate\" func (dc *DeploymentController) scaleDownOldRCsForRecreate(oldRCs []*api.ReplicationController, deployment extensions.Deployment) (bool, error) { scaled := false for _, rc := range oldRCs { // Scaling not required. if rc.Spec.Replicas == 0 { continue } _, err := dc.scaleRCAndRecordEvent(rc, 0, deployment) if err != nil { return false, err } scaled = true } return scaled, nil } // scaleUpNewRCForRecreate scales up new rc when deployment strategy is \"Recreate\" func (dc *DeploymentController) scaleUpNewRCForRecreate(newRC *api.ReplicationController, deployment extensions.Deployment) (bool, error) { if newRC.Spec.Replicas == deployment.Spec.Replicas { // Scaling not required. return false, nil } _, err := dc.scaleRCAndRecordEvent(newRC, deployment.Spec.Replicas, deployment) return true, err } </ins> func (dc *DeploymentController) updateDeploymentStatus(allRCs []*api.ReplicationController, newRC *api.ReplicationController, deployment extensions.Deployment) error { totalReplicas := deploymentutil.GetReplicaCountForRCs(allRCs) updatedReplicas := deploymentutil.GetReplicaCountForRCs([]*api.ReplicationController{newRC})", "positive_passages": [{"docid": "doc-en-kubernetes-ceb20554e653f6657baad1bbb36c40e66d8a76887956e3c674b77febc82d4455", "text": "There's some practical limit on the number of concurrent access tokens that can be used in a Kubernetes cluster before it begins to spend all of its time in the authn stack verifying them. Absent fixes to it was < 500; with the fixes linked there it's still not infinitely scalable-- I still hit (what I believe to be) with ~ 5k unique tokens @ ~700QPS. This request is to this dimension an official name & definition, and list it with others, e.g. here: it it have a useful value (I think it should be 10k) /kind bug /sig scalability\n/cc\noh and 4. add tests which verify it is as high as believed.\ncc since projected tokens will increase the number of unique tokens\n/sig auth\nLRUs are not good at scaling and sharding has some major pitfalls as pointed out. I would suggest that we try to drop the LRU cache for successful authentication results in the token cache. The main benefit of using an LRU here is bound cache size. Entries in the token cache have a fast expiration independent of the LRU policy. The records probably take up O(2kb) (guesstimate) of memory. Given that these are successful attempts with presumably valid tokens, I don't think we are getting any benefit from the LRU. If we don't have a constraint on fixed cache size, we can back the token cache with a sync.Map and run a single background goroutine to periodically walk the map and remove expired entries. This would fix the problematic locking and eviction due to nonuniform distribution of tokens over shards. The failure cache is less important and we don't cache failures by default. If we consider this the \"slowpath\", we can probably leave it as. If that's not good enough, we have a couple options (with various tradeoffs) to improve it.\nIf off by default is not enough, more reasoning why the failed cache is not super useful: it might help with an accidental DoS but it doesn't prevent anything actively malicious DoS. I think we can focus our improvements on the success cache.\n/assign He is already working on adding an explicit test for it.\nhas taken it over and is actively working on this. Unfortunately, I cannot assign this issue to him as he's not a k8s member yet\nIt's not closed - all testes must be submitted and appropriate documentation must be\nThanks everyone!!", "commid": "kubernetes_issue_83375", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-21d4f32548e506e334f13d139742dfebdb5143d941807ecd1c011423ca564773", "query": "Describe(\"guestbook\", func() { var guestbookPath = filepath.Join(testContext.RepoRoot, \"examples/guestbook\") <del> if testContext.Provider != \"gce\" && testContext.Provider != \"gke\" { By(fmt.Sprintf(\"Skipping guestbook, uses createExternalLoadBalancer, a (gce|gke) feature\")) } </del> It(\"should create and stop a working application\", func() { <ins> if !providerIs(\"gce\", \"gke\") { By(fmt.Sprintf(\"Skipping guestbook, uses createExternalLoadBalancer, a (gce|gke) feature\")) return } </ins> defer cleanup(guestbookPath, frontendSelector, redisMasterSelector, redisSlaveSelector) By(\"creating all guestbook components\")", "positive_passages": [{"docid": "doc-en-kubernetes-5702d542be386cac9e4333778515fd94620fcdb52c66d8dfc11487da78971dda", "text": "I noticed while running e2e tests locally that some tests were apparently being incorrectly skipped: I checked, and this is also true for our Jenkins runs. Currently it looks like and have this bug, though only the former actually skips the test, I think. The issue appears to be that the code inside the top-level in these files is being run before the testContext struct is filled out (and before is even called), and so testContext.Provider is empty. I'm not immediately sure what the proper fix is; I'm also worried that there might be other things broken by the fact that these blocks are called before initialization is complete. We also probably investigate if there is a better way to mark these tests as skipped; right now, there's no indication in the test report (, Jenkins test report, etc) that these tests were skipped.\nI merged and which tried to disable these tests for non-{gke,gce} but apparently didn't follow-up and verify that they were still running on our platforms. /cc\nSeems easy enough to fix. I'll have a PR out to fix this before Monday.", "commid": "kubernetes_issue_7008", "tokennum": 242}], "negative_passages": []}
{"query_id": "q-en-kubernetes-21db8d4104d4f04d72022923b78f10aaf8faa330906cb5818b1fda9667cb3c44", "query": "\"//staging/src/k8s.io/apimachinery/pkg/util/intstr:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/util/rand:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/util/sets:go_default_library\", <ins> \"//staging/src/k8s.io/apimachinery/pkg/util/strategicpatch:go_default_library\", </ins> \"//staging/src/k8s.io/apimachinery/pkg/util/uuid:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/util/version:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/util/wait:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-07b454797aabeff00bf033fc34fa4c22bd06966ba8574ac0fa868459bacbceea", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: What happened: Testgrid: https://k8s-\n/assign\nThe test's assumption about test parameter is wrong. Previously it assumed the group name is the same across all zones, but they are different in regional clusters. Looking into using node taints as the permanent fix, as suggested by the TODO comment in the test.\nHm I think taint based evictions is still an alpha feature.\nOK. I propose the following solution: Get the zone of Schedule the StatefulSet pod to that zone using node affinity; wait for the pod to run Remove the node affinity from StatefulSet Delete\nCan it be simplified? Schedule the pod Figure out which zone that pod got scheduled in Delete the instance group of that zone\nUnfortunately I don't know of a good way to look up the instance group given the zone, since there could be instance groups from multiple clusters in the same project\nHow about: Schedule the pod Figure out the zone Taint all the nodes in the zone Kill the pod\nTaint with NoSchedule? yeah that sounds good", "commid": "kubernetes_issue_69005", "tokennum": 267}], "negative_passages": []}
{"query_id": "q-en-kubernetes-21f921969f0d4dfc592aceadceba3bf91413c5fd9364d3b30e36bcce31afdbdf", "query": "return state } <ins> func updateRunningPodAndContainerMetrics(pods []*kubecontainer.Pod) { // Set the number of running pods in the parameter metrics.RunningPodCount.Set(float64(len(pods))) // intermediate map to store the count of each \"container_state\" containerStateCount := make(map[string]int) for _, pod := range pods { containers := pod.Containers for _, container := range containers { // update the corresponding \"container_state\" in map to set value for the gaugeVec metrics containerStateCount[string(container.State)]++ } } for key, value := range containerStateCount { metrics.RunningContainerCount.WithLabelValues(key).Set(float64(value)) } } </ins> func (pr podRecords) getOld(id types.UID) *kubecontainer.Pod { r, ok := pr[id] if !ok {", "positive_passages": [{"docid": "doc-en-kubernetes-3f173d1022a4408031efac17c8299f04d835794ab8a77d69bb7667b0107a08bf", "text": "Some kubelet metrics use non-standard prometheus collectors unnecessarily. Specifically, we have which can be simple gauges. Since we cannot migrate non-standard prometheus collectors using the internal metrics stability framework, we will need to convert these metrics into standard prometheus variants. /sig instrumentation /assign\nGitHub didn't allow me to assign the following users: solodov. Note that only and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : Some kubelet metrics use non-standard prometheus collectors unnecessarily. Specifically, we have which can be simple gauges. Since we cannot migrate non-standard prometheus collectors using the internal metrics stability framework, we will need to convert these metrics into standard prometheus variants. /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\nrecommends that we generate those metrics in the GenericPLEG during the relist. We can generate the data directly from the pods call there ().\nI would be interested to work on this issue if no one else is working on it currently\nGo for it!\n/assign", "commid": "kubernetes_issue_79286", "tokennum": 282}], "negative_passages": []}
{"query_id": "q-en-kubernetes-22075ee8db928af6e05bb1f2463fc2ab28cab6c7192dfe50d6f6e23844bf5fa4", "query": "// Volume is added to asw. Because attach operation fails, volume should not be reported as attached to the node. waitForVolumeAddedToNode(t, generatedVolumeName, nodeName1, asw) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <del> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw) </del> <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw, volumeAttachedCheckTimeout) </ins> // When volume is added to the node, it is set to mounted by default. Then the status will be updated by checking node status VolumeInUse. // Without this, the delete operation will be delayed due to mounted status", "positive_passages": [{"docid": "doc-en-kubernetes-dc8aac09a0e4bb26f9dc5f50aef7f845ea9d7c4b925d34b9f6eda044925f80f5", "text": "TestRunOneVolumeDetachFailNodeWithReadWriteOnce 4 times since 03-19 23:00 PDT, intermittently ! https://k8s- Still investigating whether this is a tolerable flake or not with more history than testgrid view, or otherwise would appreciate input from anyone with expertise in this test, especially as regards to whether this should be a blocker for tomorrows beta cut. maybe: /sig storage /sig testing\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nis already open for this, looks like it is attempting to fix it\nthank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. /close\nClosing this issue. <detailsIn response to : thank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. 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", "commid": "kubernetes_issue_116774", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-22075ee8db928af6e05bb1f2463fc2ab28cab6c7192dfe50d6f6e23844bf5fa4", "query": "// Volume is added to asw. Because attach operation fails, volume should not be reported as attached to the node. waitForVolumeAddedToNode(t, generatedVolumeName, nodeName1, asw) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <del> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw) </del> <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw, volumeAttachedCheckTimeout) </ins> // When volume is added to the node, it is set to mounted by default. Then the status will be updated by checking node status VolumeInUse. // Without this, the delete operation will be delayed due to mounted status", "positive_passages": [{"docid": "doc-en-kubernetes-aef7ec00dc93616f97177ca3d23f28217445848b34c429e5746962ea28329f43", "text": "pull-kubernetes-unit TestRunOneVolumeDetachFailNodeWithReadWriteOnce Jan 7th, 2022 Check volume <fake-plugin/volume-nameis reported as attached to node <fail-detach-node, got false, expected true No response_ /sig storage\n/cc\nthis is the top unit test flake according to\ncc\nThe 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]:\nI think this test is no longer flaky by checking the test grid, close it now.\nUnfortunately this does still seem to be flaky: Here was the output from : /reopen\nReopened this issue. <detailsIn response to : Unfortunately this does still seem to be flaky: 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\n/remove-lifecycle stale\nstill the case\nHow about adding some logging to help troubleshoot this? I looked at it a little, but it is hard to tell which part of the test is failing. PR\n/\nThis is still happening\n/triage accepted\nFrom the logs, in the OneVolumeDetachFailNodeWithReadWriteOnce test, succeeded, but the next verification failed. In verifyVolumeAttachedToNode, the attachState is from calling and within asw, it calls . In verifyVolumeReportedAsAttachedToNode, the volumes are obtained from calling , it seems that the node is not in asw.nodesToUpdateStatusFor at this step. Cannot reproduce locally. I tried to run the test 100 times locally with debug.Stack()... 3 * 100 times all passed.\nTried to run stress test on my linux machine as well but still cannot reproduce. Command: Result: Also tried running n process in parallel. Command: Result:\nIt seems like it happens more frequently.", "commid": "kubernetes_issue_107414", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-22075ee8db928af6e05bb1f2463fc2ab28cab6c7192dfe50d6f6e23844bf5fa4", "query": "// Volume is added to asw. Because attach operation fails, volume should not be reported as attached to the node. waitForVolumeAddedToNode(t, generatedVolumeName, nodeName1, asw) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <del> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw) </del> <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw, volumeAttachedCheckTimeout) </ins> // When volume is added to the node, it is set to mounted by default. Then the status will be updated by checking node status VolumeInUse. // Without this, the delete operation will be delayed due to mounted status", "positive_passages": [{"docid": "doc-en-kubernetes-62e47fd83b7fc1cc39259be1688a9f133b9cd2dc48247eb5d858fae7fd13955b", "text": "But I may have no time to dig into the cause. Let's see.\ncc as the test author.\nThe problem is that this test has a lot of dependency on the sleeps that are hardcoded with a very narrow scope, but our CI seems to be able to stress it much more. As soon as you slightly change one of the sleep duration it starts to flake locally The test can not make an assumption that timing is perfect, even more in the sub second range can someone in sig-storage review this test and make it less dependant on those tight sleeps?\nAccording to most failures, it failed at Line 660. Let me run some stress locally. with 250ms sleep with 100ms sleep\nI agree this test case is too brittle due to its specific timing dependencies. To fix this, I suggest reworking the test case to: 1) Add retry with timeout to wait for final conditions 2) Remove the intermediate timing-based state transition checks. Instead, we can keep track of state transitions in the Fakes and validate those stats. wdyt?\nFriendly ping from 1.27 CI Signal that this test is still a noisy flake on the master-blocking dashboard as CI Signal has flagged it in and", "commid": "kubernetes_issue_107414", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-226506a7022711190ffa06504cb00559dfb4084519de3cb199d650fa0df3af56", "query": "if err != nil { return currentRevision, updateRevision, currentStatus, err } <del> // update the set's status err = ssc.updateStatefulSetStatus(ctx, set, currentStatus) if err != nil { return currentRevision, updateRevision, currentStatus, err } klog.V(4).InfoS(\"StatefulSet pod status\", \"statefulSet\", klog.KObj(set), \"replicas\", currentStatus.Replicas, \"readyReplicas\", currentStatus.ReadyReplicas, \"currentReplicas\", currentStatus.CurrentReplicas, \"updatedReplicas\", currentStatus.UpdatedReplicas) </del> klog.V(4).InfoS(\"StatefulSet revisions\", \"statefulSet\", klog.KObj(set), \"currentRevision\", currentStatus.CurrentRevision,", "positive_passages": [{"docid": "doc-en-kubernetes-0cad02d163e61aff3cc2c1257b68701a42fb1145e0b51f6816fd9a85adca78e6", "text": "I create a ResourceQuota with two pods limit in my namespace. Then, I create a statefuleSet with 3 replicas. As expected, two pods are created successfully, and the third pod failed to create. But, the ReadyReplicas is not 2 ,but 1. The ReadyReplicas is correct 1Create a ResourceQuota with two pods limit in a new namespace. 2Create a statefulSet with 3 replicas 3Check if the ReadyReplicas of statefulSet matchs the number of stateful running pods. 1According to the logic of the statefulSet controller, new pod created in current sync is not be immediately counted into the ReadyReplicas. 2Failure to create pod will cause to return error, then skip updating status. <details</details<details</details<detailskind v1.23.3 </details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig apps\n/assign", "commid": "kubernetes_issue_108837", "tokennum": 302}], "negative_passages": []}
{"query_id": "q-en-kubernetes-227975a1ffa1439cc65c32a4ec429edf602bac0423f92f1b0ac316490bd9d585", "query": "} } <ins> if oldCRD.UID != newCRD.UID { r.removeStorage_locked(oldCRD.UID) } </ins> storageMap := r.customStorage.Load().(crdStorageMap) oldInfo, found := storageMap[newCRD.UID] if !found {", "positive_passages": [{"docid": "doc-en-kubernetes-16c95be4925a0d298a67709c93efbb137b71325e5e3041edcf306d6572e4ae65", "text": "Which jobs are failing: pull-kubernetes-integration Which test(s) are failing: TestWebhookConverterWithDefaulting /assign /priority important-soon /area custom-resources /sig api-machinery /kind flake /milestone v1.16\n/cc\nseveral of the webhook converter tests have similar flakes. it looks like the wait for storage version to become effective times out occasionally Rare flakes seen in all of these tests: TestWebhookConverterWithWatchCache/nontrivial-converter TestWebhookConverterWithWatchCache/metadata-mutating-converter TestWebhookConverterWithDefaulting/metadata-mutating-converter TestWebhookConverterWithWatchCache/noop-converter TestWebhookConverterWithDefaulting/empty-response TestWebhookConverterWithoutWatchCache/nontrivial-converter/check-2 TestWebhookConverterWithoutWatchCache/noop-converter/check-0/v1beta2 TestWebhookConverterWithoutWatchCache/nontrivial-converter/check-0/v1beta2\ncc\nYikes, I\u2019ll sort it out.\niiuc sending an empty patch gets short-circuited and doesn't bump CR generation, even if the storage version gets changed, which means we do not re-write to etcd and go through the encoding path this would be racing and doing noop's if the first pass of didn't get the expected storage version I will send a fix to make the patch do actual mutation\nIt doesn't bump generation, but the bytes to persist in etcd would still be different if the storage version had changed, so they should persist. You can verify that by changing the storage version on a CRD yourself, do an empty patch, and see if the resourceVersion changes.\nyou're right. Generation is for non-metadata change only, and the RV changes. I queried etcd locally and the apiVersion did change for an empty patch (sidetracking: another observation is after changing the storage version (say v1 -v2; noop convertor), empty-patching v2 endpoint would bump generation, while empty-patching v1 endpoint wouldn't)\nanother theory: our cached storage strategy could be stale if the CRD informer merges multiple events together (e.g. the informer does a re-list).", "commid": "kubernetes_issue_78913", "tokennum": 546}], "negative_passages": []}
{"query_id": "q-en-kubernetes-227975a1ffa1439cc65c32a4ec429edf602bac0423f92f1b0ac316490bd9d585", "query": "} } <ins> if oldCRD.UID != newCRD.UID { r.removeStorage_locked(oldCRD.UID) } </ins> storageMap := r.customStorage.Load().(crdStorageMap) oldInfo, found := storageMap[newCRD.UID] if !found {", "positive_passages": [{"docid": "doc-en-kubernetes-4d6bef5a272bfef04fa7527d92c495ee5b0e5d06d06a593b8089b98a3b84ddb9", "text": "Two scenarios: -create-update events merged into an update event: strategy with UID:a was created on demand for CRD Foo Foo was deleted and recreated strategy with UID:b was created on demand for the new Foo new Foo got updated (e.g. switching storage version) the strategy with UID:b is supposed to be deleted and , to reflect the last update. But if the CRD informer merges the delete-create-update events into , the strategy with UID:a will be deleted, but the strategy with UID:b won't. -update events merged into a create event: strategy with UID:a was created on demand for CRD Foo Foo was updated (e.g. switching storage version) the strategy with UID:a is supposed to be deleted and , to reflect the last update. But if the CRD informer merges the create-update events into , the strategy with UID:a won't be deleted (as we don't react on create events). another race found in , which could happen in a single update.\nI think I :", "commid": "kubernetes_issue_78913", "tokennum": 234}], "negative_passages": []}
{"query_id": "q-en-kubernetes-22a2cca52a6e1f190ab0f4d8f87d4b92a76781c61208933507ba609ec6168ec4", "query": "// this is ok because we know exactly how we want to be serialized TypeMeta: metav1.TypeMeta{APIVersion: batchv1.SchemeGroupVersion.String(), Kind: \"Job\"}, ObjectMeta: metav1.ObjectMeta{ <del> Name:        o.Name, Annotations: annotations, Labels:      cronJob.Spec.JobTemplate.Labels, OwnerReferences: []metav1.OwnerReference{ { APIVersion: batchv1.SchemeGroupVersion.String(), Kind:       \"CronJob\", Name:       cronJob.GetName(), UID:        cronJob.GetUID(), }, }, </del> <ins> Name:            o.Name, Annotations:     annotations, Labels:          cronJob.Spec.JobTemplate.Labels, OwnerReferences: []metav1.OwnerReference{*metav1.NewControllerRef(cronJob, batchv1.SchemeGroupVersion.WithKind(\"CronJob\"))}, </ins> }, Spec: cronJob.Spec.JobTemplate.Spec, }", "positive_passages": [{"docid": "doc-en-kubernetes-d1a3d40c65839848acfb179492aae28f1dc063c7e214fb748a3d51efaf88302e", "text": "Given a cronjob created with a scedule of \"0 6 *\" that failed at last run (status.lastSuccessfulTime is now \"before\" status.lastScheduleTime). Then I trigger the cronjob by hand and this jobs ends successfully. However status.lastSuccessfulTime is not updated, thus making it difficult to monitor failed cronjobs. status.lastSuccessfulTime should be updated with a timestamp of the succeeded job endTime Install the attached files: Wait until cronjob has actually trigged, test with to see that lastScheduleTime and lastSuccessfulTime are populated ok (as expected). Then apply the fail config-map, now the job will not complete OK: Again wait until cronjob has trigged automatically, observe to see that lastScheduleTime is updated but lastSuccessfulTime is not. Then apply the \"OK\" configmap and then create the job by hand: when the job has finished and completed ok, observe that lastSuccessfulTime is still not updated. Wait until next schedule and observe that the field is now updated. No response <details</details<detailsTested on kind cluster on Mac </details<details</details<details</details<details</details<details</details\nHad to upload the files as .txt files as github wouldn't accept .yaml or .yml files\n(Double-check: I may read wrong messagess ) /sig apps\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : When I tried without the prefix in the job name, the status is updated. /sig apps /area job not sure if this is a bug or an expected behavior. 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\n/area workload-api/cronjob\nI have just tested in my kind cluster and neither with the same naming pattern as the normal jobs (which apparently isn't epoch) or with epoch - this will not trigger a update of the field. I have also tested it on another cluster (rke2 based) and here I'm not able to get the field updated no matter which naming pattern I use.\nSorry for the mistake. I can repro the problem you have and not related to the prefix. /cc\n/assign\n/remove-sig apps /sig cli\n/triage accepted", "commid": "kubernetes_issue_118276", "tokennum": 550}], "negative_passages": []}
{"query_id": "q-en-kubernetes-22b5661b97ea2dcd4cad39292301de8544b9969580d9481d2c2994a9c28d5473", "query": "v1 \"k8s.io/api/core/v1\" \"k8s.io/apimachinery/pkg/types\" <ins> \"k8s.io/apimachinery/pkg/util/wait\" </ins> \"k8s.io/kubernetes/pkg/kubelet/cm\" \"k8s.io/kubernetes/pkg/kubelet/config\" kubecontainer \"k8s.io/kubernetes/pkg/kubelet/container\"", "positive_passages": [{"docid": "doc-en-kubernetes-8476bba8e23a7ed885cd34c1077ce17dbf12901ac7ae9725333264f6ea8cfdae", "text": "What happened: A deployment is created that uses a after the cluster master is created but before the cluster worker nodes are fully initialized. During the initialization of the worker nodes, the nodes are temporarily available for scheduling without the necessary label to match the deployment's node selector. Depending on how long the nodes are available for scheduling without the necessary node labels for the deployment, the scheduler will start to spam with cluster with pods in status. This spamming stops once the worker nodes are fully initialized and the pods are scheduled successful. The exact timing of all of this is TBD. What you expected to happen: Pods in status are annoying and require manual cleanup. It would be preferred that the scheduler avoid this an simply issue warning events. How to reproduce it (as minimally and precisely as possible): See issue description. Anything else we need to know?: No. Environment: Kubernetes version (use ): 1.18.3 Cloud provider or hardware configuration: IBM Cloud Kubernetes Service OS (e.g: ): Ubuntu 18.04.4 LTS Kernel (e.g. ): 4.15.0-96-generic Install tools: Managed service install Network plugin and version (if this is a network-related bug): N/A Others: N/A\nRelated to and\n/sig scheduling\nby spamming are you referring to scheduler logs? also, why are the nodes not labelled from the get go?\nJust to confirm, all the pods in question are still in Pending state, yes? If the pods are in pending state, all of them will get scheduled eventually once the nodes get their labels.\nThe pods are not in state. They are actually in state. The pods eventually get scheduled but we are left with anywhere from a few to dozens of these state pods. Also, we are looking at labeling the nodes via kubelet flags to see if that helps.\n/remove-kind bug\nAfter we add some retry logic and wait time in this problem can be solved: As you can see this function returns initial node as the first request failed.\nI also get hit by this, when single controller node gets rebooted and scheduler starts as static container before kubelet becomes ready.", "commid": "kubernetes_issue_92067", "tokennum": 465}], "negative_passages": []}
{"query_id": "q-en-kubernetes-22b5661b97ea2dcd4cad39292301de8544b9969580d9481d2c2994a9c28d5473", "query": "v1 \"k8s.io/api/core/v1\" \"k8s.io/apimachinery/pkg/types\" <ins> \"k8s.io/apimachinery/pkg/util/wait\" </ins> \"k8s.io/kubernetes/pkg/kubelet/cm\" \"k8s.io/kubernetes/pkg/kubelet/config\" kubecontainer \"k8s.io/kubernetes/pkg/kubelet/container\"", "positive_passages": [{"docid": "doc-en-kubernetes-6c53201dbb91d52a8ade960092a5ed582f4d35e33a53b75d555d15ae815dc25c", "text": "Can be cleaned up with:\n/sig node\nthe spam cycle is this loop: \"pod create, pod schedule, worker reject, pod failed\" -- we don't have a lot of protection in higher level workload controllers to handle pods that fail at kubelet admission time versus pods that just dont create due to quota/admission. in general, is the spam causing any other stability issues? is pod gc pruning the pods?\nI wonder if we can do a trick in node lister to mitigate any race condition here...\nwe could maybe do something similar to to ensure node lister has synced...\nhacking on option to ensure if kubelet has a node lister with a valid kube client, we wait for it to sync at least once here which should mitigate this issue. see:\nWe noticed the problem on the OLM pod which is managed by the OLM operator. Right or wrong, the operator does not like seeing the pod go to status and no longer reconciles the pod. The end result is that manual intervention (i.e. pod deletion) is required to fix the problem.\nsure... i would have thought the pod is failed in that instance and reached a terminal state. either way, i am looking at what i can do to mitigate this.\nThe problem persists in our environment as well, and the workaround cited above will not do anymore. Is there something in the works for this one?\nIssues 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\n/remove-lifecycle stale", "commid": "kubernetes_issue_92067", "tokennum": 383}], "negative_passages": []}
{"query_id": "q-en-kubernetes-22c54e70c15e60ee2f8bc2703efc613c945cdccdcb777a997def9c42bd158427", "query": "expected: &batchv1.Job{ TypeMeta: metav1.TypeMeta{APIVersion: batchv1.SchemeGroupVersion.String(), Kind: \"Job\"}, ObjectMeta: metav1.ObjectMeta{ <del> Name:        jobName, Annotations: map[string]string{\"cronjob.kubernetes.io/instantiate\": \"manual\"}, OwnerReferences: []metav1.OwnerReference{ { APIVersion: batchv1.SchemeGroupVersion.String(), Kind:       \"CronJob\", Name:       cronJob.GetName(), UID:        cronJob.GetUID(), }, }, </del> <ins> Name:            jobName, Annotations:     map[string]string{\"cronjob.kubernetes.io/instantiate\": \"manual\"}, OwnerReferences: []metav1.OwnerReference{*metav1.NewControllerRef(cronJob, batchv1.SchemeGroupVersion.WithKind(\"CronJob\"))}, </ins> }, Spec: batchv1.JobSpec{ Template: corev1.PodTemplateSpec{", "positive_passages": [{"docid": "doc-en-kubernetes-d1a3d40c65839848acfb179492aae28f1dc063c7e214fb748a3d51efaf88302e", "text": "Given a cronjob created with a scedule of \"0 6 *\" that failed at last run (status.lastSuccessfulTime is now \"before\" status.lastScheduleTime). Then I trigger the cronjob by hand and this jobs ends successfully. However status.lastSuccessfulTime is not updated, thus making it difficult to monitor failed cronjobs. status.lastSuccessfulTime should be updated with a timestamp of the succeeded job endTime Install the attached files: Wait until cronjob has actually trigged, test with to see that lastScheduleTime and lastSuccessfulTime are populated ok (as expected). Then apply the fail config-map, now the job will not complete OK: Again wait until cronjob has trigged automatically, observe to see that lastScheduleTime is updated but lastSuccessfulTime is not. Then apply the \"OK\" configmap and then create the job by hand: when the job has finished and completed ok, observe that lastSuccessfulTime is still not updated. Wait until next schedule and observe that the field is now updated. No response <details</details<detailsTested on kind cluster on Mac </details<details</details<details</details<details</details<details</details\nHad to upload the files as .txt files as github wouldn't accept .yaml or .yml files\n(Double-check: I may read wrong messagess ) /sig apps\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : When I tried without the prefix in the job name, the status is updated. /sig apps /area job not sure if this is a bug or an expected behavior. 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\n/area workload-api/cronjob\nI have just tested in my kind cluster and neither with the same naming pattern as the normal jobs (which apparently isn't epoch) or with epoch - this will not trigger a update of the field. I have also tested it on another cluster (rke2 based) and here I'm not able to get the field updated no matter which naming pattern I use.\nSorry for the mistake. I can repro the problem you have and not related to the prefix. /cc\n/assign\n/remove-sig apps /sig cli\n/triage accepted", "commid": "kubernetes_issue_118276", "tokennum": 550}], "negative_passages": []}
{"query_id": "q-en-kubernetes-22d5e863d96424ae2918182fcc76eb4996f65a5e68f23c2c74620a6fe334a0e7", "query": "s.GenericAPIServer.Handler.NonGoRestfulMux.Handle(\"/apis\", apisHandler) s.GenericAPIServer.Handler.NonGoRestfulMux.UnlistedHandle(\"/apis/\", apisHandler) <del> apiserviceRegistrationController := NewAPIServiceRegistrationController(informerFactory.Apiregistration().InternalVersion().APIServices(), c.GenericConfig.SharedInformerFactory.Core().V1().Services(), s) </del> <ins> apiserviceRegistrationController := NewAPIServiceRegistrationController(informerFactory.Apiregistration().InternalVersion().APIServices(), s) </ins> availableController := statuscontrollers.NewAvailableConditionController( informerFactory.Apiregistration().InternalVersion().APIServices(), c.GenericConfig.SharedInformerFactory.Core().V1().Services(),", "positive_passages": [{"docid": "doc-en-kubernetes-89e8d863e20723ba6498e9abf897dd4e49e26cad02c0dde0a4957b2eb3151e69", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Currently APIServiceRegistrationController watch service change and find the related APIServices related if any. Then it AddAPIService/RemoveAPIService for APIAggregator. I dig into the kube-aggregator and find it no need totally, because update APIServices status when related service or endpoint change. So if does not watch services, it will not miss any event for APIServices. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/cc\n/kind enhancement /sig api-machinery\n/assign\nthat does not follow. AvailableConditionController modifies the APIService object. APIServiceRegistrationController must still watch the APIService objects to observe those changes.\noh, I misread the description. You're saying APIServiceRegistrationController doesn't need to watch v1.Service objects", "commid": "kubernetes_issue_57836", "tokennum": 300}], "negative_passages": []}
{"query_id": "q-en-kubernetes-230b3ccde0be7d719a9a3b20815bad8813f210ff595448496f5b2e60b237b4b4", "query": "<ins> <!-- BEGIN MUNGE: UNVERSIONED_WARNING --> <!-- BEGIN STRIP_FOR_RELEASE --> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <h2>PLEASE NOTE: This document applies to the HEAD of the source tree</h2> If you are using a released version of Kubernetes, you should refer to the docs that go with that version. <strong> The latest 1.0.x release of this document can be found [here](http://releases.k8s.io/release-1.0/docs/devel/adding-an-APIGroup.md). Documentation for other releases can be found at [releases.k8s.io](http://releases.k8s.io). </strong> -- <!-- END STRIP_FOR_RELEASE --> <!-- END MUNGE: UNVERSIONED_WARNING --> Adding an API Group =============== This document includes the steps to add an API group. You may also want to take a look at PR [#16621](https://github.com/kubernetes/kubernetes/pull/16621) and PR [#13146](https://github.com/kubernetes/kubernetes/pull/13146), which add API groups. Please also read about [API conventions](api-conventions.md) and [API changes](api_changes.md) before adding an API group. ### Your core group package: We plan on improving the way the types are factored in the future; see [#16062](https://github.com/kubernetes/kubernetes/pull/16062) for the directions in which this might evolve. 1. Create a folder in pkg/apis to hold you group. Create types.go in pkg/apis/`<group>`/ and pkg/apis/`<group>`/`<version>`/ to define API objects in your group; 2. Create pkg/apis/`<group>`/{register.go, `<version>`/register.go} to register this group's API objects to the encoding/decoding scheme (e.g., [pkg/apis/extensions/register.go](../../pkg/apis/extensions/register.go) and [pkg/apis/extensions/v1beta1/register.go](../../pkg/apis/extensions/v1beta1/register.go); 3. Add a pkg/apis/`<group>`/install/install.go, which is responsible for adding the group to the `latest` package, so that other packages can access the group's meta through `latest.Group`. You probably only need to change the name of group and version in the [example](../../pkg/apis/extensions/install/install.go)). You need to import this `install` package in {pkg/master, pkg/client/unversioned, cmd/kube-version-change}/import_known_versions.go, if you want to make your group accessible to other packages in the kube-apiserver binary, binaries that uses the client package, or the kube-version-change tool. Step 2 and 3 are mechanical, we plan on autogenerate these using the cmd/libs/go2idl/ tool. ### Scripts changes and auto-generated code: 1. Generate conversions and deep-copies: 1. Add your \"group/\" or \"group/version\" into hack/after-build/{update-generated-conversions.sh, update-generated-deep-copies.sh, verify-generated-conversions.sh, verify-generated-deep-copies.sh}; 2. Run hack/update-generated-conversions.sh, hack/update-generated-deep-copies.sh. 2. Generate files for Ugorji codec: 1. Touch types.generated.go in pkg/apis/`<group>`{/, `<version>`}; 2. Run hack/update-codecgen.sh. ### Client (optional): We are overhauling pkg/client, so this section might be outdated; see [#15730](https://github.com/kubernetes/kubernetes/pull/15730) for how the client package might evolve. Currently, to add your group to the client package, you need to 1. Create pkg/client/unversioned/`<group>`.go, define a group client interface and implement the client. You can take pkg/client/unversioned/extensions.go as a reference. 2. Add the group client interface to the `Interface` in pkg/client/unversioned/client.go and add method to fetch the interface. Again, you can take how we add the Extensions group there as an example. 3. If you need to support the group in kubectl, you'll also need to modify pkg/kubectl/cmd/util/factory.go. ### Make the group/version selectable in unit tests (optional): 1. Add your group in pkg/api/testapi/testapi.go, then you can access the group in tests through testapi.`<group>`; 2. Add your \"group/version\" to `KUBE_API_VERSIONS` and `KUBE_TEST_API_VERSIONS` in hack/test-go.sh. <!-- BEGIN MUNGE: GENERATED_ANALYTICS --> [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/adding-an-APIGroup.md?pixel)]() <!-- END MUNGE: GENERATED_ANALYTICS --> </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-f256e345b7b51b103065fba025a54804b2fa9969c4fe88ae4c8d8670e2ed79f1", "text": "AFAIK, we don't have a documentation on how to add a new API group. Currently we have and that try to add a new API group. I will draft a guide to ease the future endeavor of adding groups. And probably by writing this guide, I will see how can we make the API group machinery easier to use. cc", "commid": "kubernetes_issue_16626", "tokennum": 70}], "negative_passages": []}
{"query_id": "q-en-kubernetes-231f42e716de7cff047514924c7d838007ada0188f38ccfbe935000e3482ef18", "query": "} // prepare kube clients. <del> client, leaderElectionClient, eventClient, err := createClients(c.ComponentConfig.ClientConnection, o.Master) </del> <ins> client, leaderElectionClient, eventClient, err := createClients(c.ComponentConfig.ClientConnection, o.Master, c.ComponentConfig.LeaderElection.RenewDeadline.Duration) </ins> if err != nil { return nil, err }", "positive_passages": [{"docid": "doc-en-kubernetes-638d244f4d44257351ae4786f705d88f47a0e12c74ce71a459164cb07c9c1943", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: kube-cm kube-scheduler does not exit when kube-apiserver suspended What you expected to happen: kube-cm kube-scheduler should exit after LeaderElector stops leading How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/sig api-machinery /kind bug\n/assign\n/cc", "commid": "kubernetes_issue_65090", "tokennum": 179}], "negative_passages": []}
{"query_id": "q-en-kubernetes-237058740670cd75109ff8d5362d71f4917da5b9fde602722c70b4cca7601200", "query": "v1 \"k8s.io/api/core/v1\" apierrors \"k8s.io/apimachinery/pkg/api/errors\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" <ins> unstructuredv1 \"k8s.io/apimachinery/pkg/apis/meta/v1/unstructured\" </ins> \"k8s.io/apimachinery/pkg/labels\" <ins> \"k8s.io/apimachinery/pkg/runtime\" \"k8s.io/apimachinery/pkg/runtime/schema\" </ins> \"k8s.io/apimachinery/pkg/types\" \"k8s.io/apimachinery/pkg/util/intstr\" \"k8s.io/apimachinery/pkg/util/wait\" \"k8s.io/apimachinery/pkg/watch\" <ins> \"k8s.io/client-go/dynamic\" </ins> clientset \"k8s.io/client-go/kubernetes\" appsclient \"k8s.io/client-go/kubernetes/typed/apps/v1\" watchtools \"k8s.io/client-go/tools/watch\"", "positive_passages": [{"docid": "doc-en-kubernetes-cea21dfbf74ea26aea8b8fcc0c8d9d3e2b3e4488cd9f6d30773b87652fe6e220", "text": "[x] Original approval issue: [x] Test pr: [x] Two weeks soak end date: 19 November 2020 This issue is created to allow edit by /wip /hold According to this APIsnoop query, there are still some remaining Deployment endpoints which are untested. a Deployment with a static label the Deployment with a new Label and updated data the Deployment to ensure it's patched all Deployments in all Namespaces find the Deployment(1) ensure that the Deployment is found and is patched Namespaced Deployment(1) via a Collection with a LabelSelector Discover useragents: List endpoints hit by the test: Display endpoint coverage change: If a test with these calls gets merged, test coverage will go up by 5 points* This test is also created with the goal of conformance promotion.\n/sig testing /sig architecture /area conformance\nBobyMcbobs commented in original Issue: Unsure if the endpoint replaceAppsV1NamespacedDeploymentStatus is able to be hit. When this endpoint is attempted to be updated the data after retrieving the update resource doesn't reflect the values in the update\n/assign\nWhen using the appv1.Deployment structure instead of maps of interfaces to build the structure in a patch of the Deployment, this error comes up. Still in progress yment-static\":\"true\"}: does not match template , spec.selector: Invalid value: \"null\": field is immutable]\nreplaceAppsV1NamespacedDeploymentStatus to test. Increase cover by 1 Endpoint\n/reopen PR reverted by due to flaky test\nReopened this issue. <detailsIn response to : /reopen PR reverted by due to flaky test 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\nIssues 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\n/reopen Soaking, ready for promotion 19 November 2020\nReopened this issue. <detailsIn response to : /reopen Soaking, ready for promotion 19 November 2020 Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_90916", "tokennum": 522}], "negative_passages": []}
{"query_id": "q-en-kubernetes-237058740670cd75109ff8d5362d71f4917da5b9fde602722c70b4cca7601200", "query": "v1 \"k8s.io/api/core/v1\" apierrors \"k8s.io/apimachinery/pkg/api/errors\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" <ins> unstructuredv1 \"k8s.io/apimachinery/pkg/apis/meta/v1/unstructured\" </ins> \"k8s.io/apimachinery/pkg/labels\" <ins> \"k8s.io/apimachinery/pkg/runtime\" \"k8s.io/apimachinery/pkg/runtime/schema\" </ins> \"k8s.io/apimachinery/pkg/types\" \"k8s.io/apimachinery/pkg/util/intstr\" \"k8s.io/apimachinery/pkg/util/wait\" \"k8s.io/apimachinery/pkg/watch\" <ins> \"k8s.io/client-go/dynamic\" </ins> clientset \"k8s.io/client-go/kubernetes\" appsclient \"k8s.io/client-go/kubernetes/typed/apps/v1\" watchtools \"k8s.io/client-go/tools/watch\"", "positive_passages": [{"docid": "doc-en-kubernetes-ff9ccf83336a9bf28b0576a991dfda56392cc48f280c272644ff154877b8104d", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/remove-lifecycle stale\n/triage accepted\n/merged", "commid": "kubernetes_issue_90916", "tokennum": 34}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2380359e98d8af8bbad0f6d2f06b6bf6fb7304e2f55e97a89abaeed49b42be6e", "query": "deploymentReplicas := 4 deploymentImage := \"gcr.io/google_samples/gb-redisslave:v1\" deploymentMinReadySeconds := 5 <ins> deploymentStrategyType := extensions.RollingUpdateDeploymentStrategyType </ins> Logf(\"Creating deployment %s\", deploymentName) <del> newDeployment := newDeployment(deploymentName, deploymentReplicas, deploymentPodLabels, deploymentImageName, deploymentImage) </del> <ins> newDeployment := newDeployment(deploymentName, deploymentReplicas, deploymentPodLabels, deploymentImageName, deploymentImage, deploymentStrategyType) </ins> newDeployment.Spec.Strategy.RollingUpdate = &extensions.RollingUpdateDeployment{ MaxUnavailable:  intstr.FromInt(1), MaxSurge:        intstr.FromInt(1),", "positive_passages": [{"docid": "doc-en-kubernetes-ceb20554e653f6657baad1bbb36c40e66d8a76887956e3c674b77febc82d4455", "text": "There's some practical limit on the number of concurrent access tokens that can be used in a Kubernetes cluster before it begins to spend all of its time in the authn stack verifying them. Absent fixes to it was < 500; with the fixes linked there it's still not infinitely scalable-- I still hit (what I believe to be) with ~ 5k unique tokens @ ~700QPS. This request is to this dimension an official name & definition, and list it with others, e.g. here: it it have a useful value (I think it should be 10k) /kind bug /sig scalability\n/cc\noh and 4. add tests which verify it is as high as believed.\ncc since projected tokens will increase the number of unique tokens\n/sig auth\nLRUs are not good at scaling and sharding has some major pitfalls as pointed out. I would suggest that we try to drop the LRU cache for successful authentication results in the token cache. The main benefit of using an LRU here is bound cache size. Entries in the token cache have a fast expiration independent of the LRU policy. The records probably take up O(2kb) (guesstimate) of memory. Given that these are successful attempts with presumably valid tokens, I don't think we are getting any benefit from the LRU. If we don't have a constraint on fixed cache size, we can back the token cache with a sync.Map and run a single background goroutine to periodically walk the map and remove expired entries. This would fix the problematic locking and eviction due to nonuniform distribution of tokens over shards. The failure cache is less important and we don't cache failures by default. If we consider this the \"slowpath\", we can probably leave it as. If that's not good enough, we have a couple options (with various tradeoffs) to improve it.\nIf off by default is not enough, more reasoning why the failed cache is not super useful: it might help with an accidental DoS but it doesn't prevent anything actively malicious DoS. I think we can focus our improvements on the success cache.\n/assign He is already working on adding an explicit test for it.\nhas taken it over and is actively working on this. Unfortunately, I cannot assign this issue to him as he's not a k8s member yet\nIt's not closed - all testes must be submitted and appropriate documentation must be\nThanks everyone!!", "commid": "kubernetes_issue_83375", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-23af934366386aa1ebc539fdf638c5f6e4ffccf8556b72575bdda50d819f02f2", "query": "vSphereInstance) } klog.V(4).Infof(\"DiskIsAttached result: %v and error: %q, for volume: %q\", attached, err, volPath) <del> return attached, err </del> <ins> return attached, volPath, err </ins> } requestTime := time.Now() <del> isAttached, err := diskIsAttachedInternal(volPath, nodeName) </del> <ins> isAttached, newVolumePath, err := diskIsAttachedInternal(volPath, nodeName) </ins> if err != nil { if vclib.IsManagedObjectNotFoundError(err) { err = vs.nodeManager.RediscoverNode(nodeName) if err == vclib.ErrNoVMFound { isAttached, err = false, nil } else if err == nil { <del> isAttached, err = diskIsAttachedInternal(volPath, nodeName) </del> <ins> isAttached, newVolumePath, err = diskIsAttachedInternal(volPath, nodeName) </ins> } } } vclib.RecordvSphereMetric(vclib.OperationDiskIsAttached, requestTime, err) <del> return isAttached, err </del> <ins> return isAttached, newVolumePath, err </ins> } // DisksAreAttached returns if disks are attached to the VM using controllers supported by the plugin.", "positive_passages": [{"docid": "doc-en-kubernetes-e1df151812a738ca8d7e9f97519d671c643638f3ca9d9400cc430f5f7a7d204c", "text": "When user creates a static PV using folder name in path: on vSAN backed datastore then detach disk does not work because check fails - The code expects folder name to be UUID but it does not and hence it determines disk is not attached to the node and hence no detach is ever performed. /sig storage cc", "commid": "kubernetes_issue_95121", "tokennum": 68}], "negative_passages": []}
{"query_id": "q-en-kubernetes-23c0ce065df448931d282eaa0c577999f9b506c33f3009ba83c7bc2ef008f522", "query": "if m.dynamicTemplate { go wait.Forever(func() { // check if the current template matches what we last requested <del> if !reflect.DeepEqual(m.getLastRequest(), m.getTemplate()) { </del> <ins> if !m.certSatisfiesTemplate() && !reflect.DeepEqual(m.getLastRequest(), m.getTemplate()) { </ins> // if the template is different, queue up an interrupt of the rotation deadline loop. // if we've requested a CSR that matches the new template by the time the interrupt is handled, the interrupt is disregarded. templateChanged <- struct{}{}", "positive_passages": [{"docid": "doc-en-kubernetes-8be37f8ebf3b929ba13e3d88ac8f62b2b24f9ed008212f39c0aaa7e2ec850c18", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: I'm testing the new option in kubernetes 1.12 and it seems that kubelet always requests the signing of a new CSR and tries to rotate the certificates when it is started. This is happening even though there's a valid (brand new) certificate on disk issued by kube-controller-manager. From what I can tell, this is happening because kubelet implements and is set after a successful certificate rotation, but is never persisted to disk. If kubelet is restarted, then the last requested CSR is nil. What you expected to happen: Ideally, kubelet should only request the signing of a new CSR if it doesn't already have a serving certificate or it's about to expire. How to reproduce it (as minimally and precisely as possible): Restart a kubelet instance that had it's serving certificate issued by kube-controller-manager Check and see that it requested the signing of a new CSR Anything else we need to know?: kubelet is being run with . , , and are all omitted to use the default values. The TLS bootstrapping for client certificates is currently not being used--just the bootstrapping for serving certificates. Environment: Kubernetes version: v1.12.0 - built from source at the tag () Cloud provider or hardware configuration: Bare metal OS: CentOS 7.5.1804 Kernel: Install tools: Custom RPMs built from this git repo with no additional patches Others:\n/sig node\n/sig auth\nNot sure if this is the ideal fix, but I've patched it so that it compares the current CSR template to the last requested template only if it doesn't already match the current cert.\ncc\nthanks for the proposed fix. I think it looks good. Could you send a PR? We should also remove entirely and only look at current cert and template. does that sound reasonable?\nSure thing, I'd be happy to do that. EDIT: I will submit a PR after approval from my employer.\nI think that's probably ok, as long as it checks everything we include in the template and we consider a certificate missing anything we request to be cause for re-requesting another cert (an issuer couldn't choose to issue a cert that drops some SANs and us not request another cert) left some comments in\nThis regression is a frequent flyer.", "commid": "kubernetes_issue_69471", "tokennum": 523}], "negative_passages": []}
{"query_id": "q-en-kubernetes-23c0ce065df448931d282eaa0c577999f9b506c33f3009ba83c7bc2ef008f522", "query": "if m.dynamicTemplate { go wait.Forever(func() { // check if the current template matches what we last requested <del> if !reflect.DeepEqual(m.getLastRequest(), m.getTemplate()) { </del> <ins> if !m.certSatisfiesTemplate() && !reflect.DeepEqual(m.getLastRequest(), m.getTemplate()) { </ins> // if the template is different, queue up an interrupt of the rotation deadline loop. // if we've requested a CSR that matches the new template by the time the interrupt is handled, the interrupt is disregarded. templateChanged <- struct{}{}", "positive_passages": [{"docid": "doc-en-kubernetes-1b55ad000b296f12b046608a2d187d8503e900f5b67dbcaa87fc7ef8e9366d19", "text": "I'd love to see an integration test that would catch this (but that shouldn't block a fix).\nThanks for the comments! Now that I have the CLA signed, I'll address those and submit a PR.\nJust submitted the PR:", "commid": "kubernetes_issue_69471", "tokennum": 53}], "negative_passages": []}
{"query_id": "q-en-kubernetes-23d179b9394b5fb854f811e123c5a4a433a78f83f90eb513ededfb997aac4db6", "query": "// The name of this port. All ports in an EndpointSlice must have a unique // name. If the EndpointSlice is dervied from a Kubernetes service, this // corresponds to the Service.ports[].name. <del> // Name must either be an empty string or pass IANA_SVC_NAME validation: // * must be no more than 15 characters long // * may contain only [-a-z0-9] // * must contain at least one letter [a-z] // * it must not start or end with a hyphen, nor contain adjacent hyphens </del> <ins> // Name must either be an empty string or pass DNS_LABEL validation: // * must be no more than 63 characters long. // * must consist of lower case alphanumeric characters or '-'. // * must start and end with an alphanumeric character. </ins> // Default is empty string. optional string name = 1;", "positive_passages": [{"docid": "doc-en-kubernetes-b73bb51cef5016ee2dcd80aae4248808fec811a4dad3a3b7abbba7673a446c48", "text": "What happened: No endpoints created in the EndpointSlice for my service due to the port on the service being too long. Logs show: EndpointSlice created has no endpoint: What you expected to happen: Service that works with Endpoints should work with EndpointSlice. If this is intentional, it should be clearly documented How to reproduce it (as minimally and precisely as possible): Create a service with a long port name Environment: Kubernetes version (use ): 1.16 Cloud provider or hardware configuration: kind\n/sig networking\nThe label(s) cannot be applied. These labels are supported: <detailsIn response to : /sig networking 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\n/sig network These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by vllry. \u200d\nFor a rough measure of impact, Istio had 5 ports that were over this limit (and many more that were right at 15 characters), so I suspect it may not be terribly rare.\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nThis needs to be resolved before endpointslices graduate from alpha\n/assign\n/remove-triage unresolved", "commid": "kubernetes_issue_84388", "tokennum": 292}], "negative_passages": []}
{"query_id": "q-en-kubernetes-23eb88d97b40d0ae1504cffb57d02607ac42bc7c675cd87d8fcda8af21247bad", "query": "nodeStatusUpdateRetry = 5 // Location of container logs. <del> containerLogsDir = \"/var/log/containers\" </del> <ins> ContainerLogsDir = \"/var/log/containers\" </ins> // max backoff period, exported for the e2e test MaxContainerBackOff = 300 * time.Second", "positive_passages": [{"docid": "doc-en-kubernetes-0ad427ca9c00c618017f4be9fb19a1df6f4ab39ddc68f128fc109eb4d0409cbf", "text": "Cluster logging assumes kubelet stores container log at a specific directory with specific name. Currently the path is: After the CRI work, the path will be: However, we don't have test coverage for this. We don't even know whether the log files are there or not. We should add a node e2e test for this, basically: 1) Create a container which prints logs 2) Check whether the expected log file is created. 3) Check whether the logs are collected in the file as expected. And it would be better to launch a pod to do the check instead of accessing local file system directly, which makes containerizing easier. /cc because you are collecting missing test. /cc\nI will try to add a node-e2e test there\nI think it's ok to add this for CRI. But there maybe problems on today's interface for rkt. If I'm not wrong, rkt does't store logs at same location with docker. cc/ Is this true?\nThanks! :)\nAfter gets merged, we need to update the test to verify the cri log path.", "commid": "kubernetes_issue_34661", "tokennum": 234}], "negative_passages": []}
{"query_id": "q-en-kubernetes-23edfd63d9569787daa8761fd2787a8136331f5e77fb0657cd12c71fc3a1b8dc", "query": "\"//vendor/k8s.io/apiserver/pkg/server:go_default_library\", \"//vendor/k8s.io/apiserver/pkg/util/feature:go_default_library\", \"//vendor/k8s.io/apiserver/pkg/util/proxy:go_default_library\", <del> \"//vendor/k8s.io/client-go/informers/core/v1:go_default_library\", </del> \"//vendor/k8s.io/client-go/listers/core/v1:go_default_library\", \"//vendor/k8s.io/client-go/pkg/version:go_default_library\", \"//vendor/k8s.io/client-go/rest:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-89e8d863e20723ba6498e9abf897dd4e49e26cad02c0dde0a4957b2eb3151e69", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Currently APIServiceRegistrationController watch service change and find the related APIServices related if any. Then it AddAPIService/RemoveAPIService for APIAggregator. I dig into the kube-aggregator and find it no need totally, because update APIServices status when related service or endpoint change. So if does not watch services, it will not miss any event for APIServices. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/cc\n/kind enhancement /sig api-machinery\n/assign\nthat does not follow. AvailableConditionController modifies the APIService object. APIServiceRegistrationController must still watch the APIService objects to observe those changes.\noh, I misread the description. You're saying APIServiceRegistrationController doesn't need to watch v1.Service objects", "commid": "kubernetes_issue_57836", "tokennum": 300}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2447668b6a46c88f66763cdedce17f3c5dde1f5dbe6d890d99dc4a422a651af8", "query": "\"//pkg/util/metrics:go_default_library\", \"//staging/src/k8s.io/api/apps/v1:go_default_library\", \"//staging/src/k8s.io/api/core/v1:go_default_library\", <ins> \"//staging/src/k8s.io/apimachinery/pkg/api/equality:go_default_library\", </ins> \"//staging/src/k8s.io/apimachinery/pkg/api/errors:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/apis/meta/v1:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/labels:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-56dc15a3fe2161c6cf8927a51d2d0dce03fea80f01ef1e0345dcc3ca50d1379f", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: a cluster, And node1 with resource 1 DaemonSet, request resource 4 run , There is no pod created. resource to the node: run , There is still no pod created. What you expected to happen: In step 5, There is one pod created. How to reproduce it (as minimally and precisely as possible): see above description Anything else we need to know?: Environment: Kubernetes version (use ):1.10.5 Cloud provider or hardware configuration: OS (e.g. from /etc/os-release):CentOS7 Kernel (e.g. ): Install tools: Others: /sig app\nxref\nThanks! is not work here! Because: DaemonSetsController didn't watch the changes.(we use to updateNode.) we restart kubelet, The DaemonSetsController watch the changes, but it seems that the node info is not updated, and still failed to create pod:\nI found it is a bug here, ignore the changes. I made a fix , PTAL! Thanks!\nAny workarounds for old cluster versions? Up: looks like in my case helped but after some delay.\n, which version of k8s are you using? If it's sunset, you have to merge the pr yourself :). I think restart kubelet trigger delete/add to make sure it sync .\nSorry, I didn't say\nI think we still support 1.12 for now :) let's cherry pick it if not and wait for next 1.12 release.", "commid": "kubernetes_issue_67225", "tokennum": 342}], "negative_passages": []}
{"query_id": "q-en-kubernetes-24c607558d148f20e1452c09e2b008066d2dff8070467035baf18934f58516fe", "query": "}, } <ins> func addOrUpdateUnschedulablePod(p *PriorityQueue, pod *v1.Pod) { p.lock.Lock() defer p.lock.Unlock() p.unschedulableQ.addOrUpdate(pod) } func getUnschedulablePod(p *PriorityQueue, pod *v1.Pod) *v1.Pod { p.lock.Lock() defer p.lock.Unlock() return p.unschedulableQ.get(pod) } </ins> func TestPriorityQueue_Add(t *testing.T) { q := NewPriorityQueue(nil) if err := q.Add(&medPriorityPod); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-e059cd0647305d70a174ce6bffb9584a993a023526be428075760ddef27cc3b0", "text": "Which jobs are failing: pull-kubernetes-bazel-test Which test(s) are failing: bazel test //pkg/scheduler/internal/queue:godefaulttest Since when has it been failing: Testgrid link: Reason for failure: WARNING: DATA RACE Read at 0x00c000230db0 by goroutine 47: runtime.mapiterinit() +0x0 (PriorityQueue).flushUnschedulableQLeftover() +0x17a (PriorityQueue).flushUnschedulableQLeftover-fm() +0x41 () +0x61 () +0xce () +0x5a Previous write at 0x00c000230db0 by goroutine 45: runtime.mapassignfaststr() +0x0 (UnschedulablePodsMap).addOrUpdate() +0x30e () +0x601 testing.tRunner() +0x162 Goroutine 47 (running) created at: (PriorityQueue).run() +0x172 () +0xe0b () +0x50 () +0x5a5 testing.tRunner() +0x162 Goroutine 45 (running) created at: testing.(T).Run() +0x659 testing.runTests.func1() +0xa8 testing.tRunner() +0x162 testing.runTests() +0x4ee testing.(M).Run() +0x2ee () bazel-out/k8- +0x2fb Anything else we need to know: I'm very sorry about that. UnschedulablePodsMap is not thread-safe. In , lock will be acquired before operating UnschedulablePodsMap. But in , lock isn\u2018t be acquired. In the previous case, only a single thread runs so it's ok. But after add goroutine , there will be data race. So I need to acquire lock before operating UnschedulablePodsMap.\n/sig testing /sig scheduling", "commid": "kubernetes_issue_73021", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2505e054c903067ca99c77e6e3584e259186c215964dfcd1840305a90123c6d4", "query": "func NewManager(topology []cadvisorapi.Node, topologyPolicyName string, topologyScopeName string, topologyPolicyOptions map[string]string) (Manager, error) { klog.InfoS(\"Creating topology manager with policy per scope\", \"topologyPolicyName\", topologyPolicyName, \"topologyScopeName\", topologyScopeName) <ins> // When policy is none, the scope is not relevant, so we can short circuit here. if topologyPolicyName == PolicyNone { return &manager{scope: NewNoneScope()}, nil } </ins> opts, err := NewPolicyOptions(topologyPolicyOptions) if err != nil { return nil, err", "positive_passages": [{"docid": "doc-en-kubernetes-4d10931e14d2065e9a15e6880eb555f03f2fd6b09352947daeddff0435b576bc", "text": "Follow up from: See details there. When is , there is no need to discover the NUMA topology. /sig node /priority backlog /kind feature /help-wanted\n/cc\n/triage accepted\nI would like to take this up also can I get more brief information about it? code review comments from asking that inside the NewManager() implementation, we need to skip NewPolicyOptions and NewNUMAInfo but when the NumaTopology comes kubelet issue also comes. I need some more information to start with this!\n/cc\nWhen there is no topology manger policy specified, NewManager should be a no-op. Just skip all checks.\nExactly. Just to add: we may need few iterations over the change to get a clean flow in the call.\n/assign", "commid": "kubernetes_issue_116391", "tokennum": 166}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2514bf7ae6e42fd2780ecd79f406b66922d7eaa054ceefee1fb51e1dd17ab0eb", "query": "kubectl set resources deployment nginx --limits=cpu=0,memory=0 --requests=cpu=0,memory=0 # Print the result (in yaml format) of updating nginx container limits from a local, without hitting the server <del> kubectl set resources -f path/to/file.yaml --limits=cpu=200m,memory=512Mi --local -o yaml`) </del> <ins> kubectl set resources -f path/to/file.yaml --limits=cpu=200m,memory=512Mi --dry-run -o yaml`) </ins> ) // ResourcesOptions is the start of the data required to perform the operation. As new fields are added, add them here instead of", "positive_passages": [{"docid": "doc-en-kubernetes-f45c12318e35043c65362c27e361ee13adfef369e183f2b4f0557c11353bd9e9", "text": "from https://k8s-\nReally suspect this is\nThis is putting us into test-go post-commit run is broken\ncc:\nmarked this p0 - if a fix isn't easy let's try to identify what introduced this and revert.\nThis flake on: 2016-10-30 07:19 PDT First instance: : It is flaking frequently, blocking PRs from getting merged, and slowing the submit queue ( at 75%). As on-call, I'm going to try and identify the cluprit and revert. Can use all help in doing so.\ncan you investigate whether your additional tests could cause this (by breaking the deployment of those pods, for instance) , Saad Ali wrote:\nPR looks most suspect to me. It mucked with , and the errors we are seeing in each of the failures is related to : That PR was merged at Oct 30, 2016, 6:18 AM PDT and the first flake in was at Oct 30, 2016, 7:19 AM PDT. Thoughts? CC\nI'm going to initiate a revert of to see if that fixes the issue\nIMO we can just change the flaky test to not get pods but some other resources, such as deployments. We can't really expect to clean up pods immediately.\nI'm going to proceed with revert (). Please feel free to send a follow up PR to handle this more gracefully.\nGoing to leave this opened until we have a few hours of runs with the revert. Want to verify, with some degree of certainty, that the revert took care of this flake.\nWe had 15 green runs of in a row. Considering this flake fixed.", "commid": "kubernetes_issue_35898", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-25313f326a7a31e92ea1dc4417bd732416065bb5d65f80e1a14c2a716a8b43be", "query": "Spec: v1.PodSpec{ Containers: []v1.Container{ { <del> Name:  name, Image: \"gcr.io/google_containers/busybox:1.24\", VolumeMounts: []v1.VolumeMount{ { Name:      \"tmpfs\", MountPath: \"/tmp\", }, }, Command: cmd, }, }, RestartPolicy: v1.RestartPolicyNever, Volumes: []v1.Volume{ { Name:         \"tmpfs\", VolumeSource: v1.VolumeSource{HostPath: &v1.HostPathVolumeSource{Path: \"/tmp\"}}, </del> <ins> Name:      name, Image:     image, Lifecycle: lifecycle, </ins> }, }, },", "positive_passages": [{"docid": "doc-en-kubernetes-523d59ec5104a53f44aa3efaa79fa37e525dbabb537793d9e95c31ff14a3e1c1", "text": "The prestop and poststart exec tests volume mount /tmp from the host and attempt to create a file there from inside the pod. This is blocked by selinux. Failure:\nwe need to have a mechanism to say that a test should not be run if selinux is enabled (if legitimately required) or fix each test (where appropriate)", "commid": "kubernetes_issue_42905", "tokennum": 76}], "negative_passages": []}
{"query_id": "q-en-kubernetes-254c879e7f77a8c7a9e7d8da5e4e55b35da6c445bb024fcec71befca23204603", "query": "gvr(\"\", \"v1\", \"pods\"):                                                          `{\"metadata\": {\"deletionTimestamp\": \"2020-01-01T00:00:00Z\", \"ownerReferences\":[]}, \"spec\": {\"containers\": [{\"image\": \"` + image2 + `\", \"name\": \"container7\"}]}}`, gvr(\"\", \"v1\", \"replicationcontrollers\"):                                        `{\"spec\": {\"selector\": {\"new\": \"stuff2\"}}}`, gvr(\"\", \"v1\", \"resourcequotas\"):                                                `{\"spec\": {\"hard\": {\"cpu\": \"25M\"}}}`, <del> gvr(\"\", \"v1\", \"services\"):                                                      `{\"spec\": {\"externalName\": \"service2name\"}}`, </del> <ins> gvr(\"\", \"v1\", \"services\"):                                                      `{\"spec\": {\"type\": \"ClusterIP\"}}`, </ins> gvr(\"apps\", \"v1\", \"daemonsets\"):                                                `{\"spec\": {\"template\": {\"spec\": {\"containers\": [{\"image\": \"` + image2 + `\", \"name\": \"container6\"}]}}}}`, gvr(\"apps\", \"v1\", \"deployments\"):                                               `{\"metadata\": {\"labels\": {\"a\":\"c\"}}, \"spec\": {\"template\": {\"spec\": {\"containers\": [{\"image\": \"` + image2 + `\", \"name\": \"container6\"}]}}}}`, gvr(\"apps\", \"v1\", \"replicasets\"):                                               `{\"spec\": {\"template\": {\"spec\": {\"containers\": [{\"image\": \"` + image2 + `\", \"name\": \"container4\"}]}}}}`,", "positive_passages": [{"docid": "doc-en-kubernetes-e021a9a686a92d83ba285392c70089f3a0813200ee010fb06825ed96dc15cfdb", "text": "xref I think this may be one of the few cases where we can actually change the behavior in a \"breaking\" way. User creates service with , is empty Controller or user updates the status subresource, sets (not wiped or validated, should be) User updates in any way, is wiped It's clear that the is not meant to be set when is not \"LoadBalancer\". The question is: 1) Fail validation? 2) Silently discard the value? 3) Warn and then discard the value? 4) Just warn and leave it. Because we allowed it in the past, but it is so volatile, I lean towards 3. and - the people most familair with this type. Edit: PrepareForUpdate() runs before warnings. So: (1) is easy (2) is easy (4) is slightly less easy than (2) (3) is slightly less easy than (4)\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nOMG change it to clusterIP as expected Status is wiped update status as ClusterIP ... and if I edit the service back to loadbalancer it keeps the status??\n/kind bug\n/retitle Service can be set when !=\nWe talked about this one at the SIG Network meeting today. suggested we use the feature gate for deprecation option to phase the current (problematic) functionality out.\n/triage accept\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /triage accept 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", "commid": "kubernetes_issue_119700", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-255282f40d44d129192b496f16d682aef94e674b4638305619204466bc66900f", "query": "genericfeatures.APIResponseCompression: {Default: true, PreRelease: featuregate.Beta}, <ins> genericfeatures.APIServerIdentity: {Default: true, PreRelease: featuregate.Beta}, genericfeatures.APIServerTracing: {Default: true, PreRelease: featuregate.Beta}, genericfeatures.ConsistentListFromCache: {Default: false, PreRelease: featuregate.Alpha}, genericfeatures.CustomResourceValidationExpressions: {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.31 genericfeatures.EfficientWatchResumption: {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, </ins> genericfeatures.KMSv1: {Default: false, PreRelease: featuregate.Deprecated}, genericfeatures.KMSv2: {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.31 genericfeatures.KMSv2KDF: {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.31 <del> genericfeatures.ValidatingAdmissionPolicy: {Default: false, PreRelease: featuregate.Beta}, genericfeatures.CustomResourceValidationExpressions: {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.31 </del> genericfeatures.OpenAPIEnums: {Default: true, PreRelease: featuregate.Beta}, <ins> genericfeatures.RemainingItemCount: {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, </ins> genericfeatures.ServerSideApply: {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.29 genericfeatures.ServerSideFieldValidation: {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.29 <ins> genericfeatures.StorageVersionAPI: {Default: false, PreRelease: featuregate.Alpha}, genericfeatures.StorageVersionHash: {Default: true, PreRelease: featuregate.Beta}, </ins> genericfeatures.StructuredAuthenticationConfiguration: {Default: false, PreRelease: featuregate.Alpha}, genericfeatures.StructuredAuthorizationConfiguration: {Default: false, PreRelease: featuregate.Alpha}, genericfeatures.UnauthenticatedHTTP2DOSMitigation: {Default: true, PreRelease: featuregate.Beta}, <ins> genericfeatures.ValidatingAdmissionPolicy: {Default: false, PreRelease: featuregate.Beta}, genericfeatures.WatchBookmark: {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, genericfeatures.WatchList: {Default: false, PreRelease: featuregate.Alpha}, </ins> genericfeatures.ZeroLimitedNominalConcurrencyShares: {Default: false, PreRelease: featuregate.Beta}, // inherited features from apiextensions-apiserver, relisted here to get a conflict if it is changed", "positive_passages": [{"docid": "doc-en-kubernetes-6eb9bac2f3074e091af4e33eda553e3139bfcfe5ecf153737d95dc4605072155", "text": "This avoids drift between Kubernetes components and allows for cluster management tools that pass uniform feature gates to all components. xref:\n/assign\nHey I f you stuck anywhere. Please free to involve me in this.", "commid": "kubernetes_issue_121613", "tokennum": 45}], "negative_passages": []}
{"query_id": "q-en-kubernetes-256b6072bd53b92049ad52ad2009a1ffc0d2b13e8983dd81ed777904226a3f66", "query": "return NewDelayingQueueWithCustomClock(clock.RealClock{}, \"\") } <ins> // NewDelayingQueueWithCustomQueue constructs a new workqueue with ability to // inject custom queue Interface instead of the default one func NewDelayingQueueWithCustomQueue(q Interface, name string) DelayingInterface { return newDelayingQueue(clock.RealClock{}, q, name) } </ins> // NewNamedDelayingQueue constructs a new named workqueue with delayed queuing ability func NewNamedDelayingQueue(name string) DelayingInterface { return NewDelayingQueueWithCustomClock(clock.RealClock{}, name)", "positive_passages": [{"docid": "doc-en-kubernetes-4f192dd202c02f7ffbf9fec50f8a461695dfaeb54dc2c0d9c429922f335d948f", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Current constructors: Could we export a new constructor like to inject custom queue. Why is this needed: In my project, i want to create a with a custom queue based on workqueue.Interface but have no way to do that.\n/sig api-machinery\nthanks for the issue! We've reviewed it in the bug triage, and the consensus was that to ask you to send a PR with this and discuss it there. Would you be able to do it? thanks!\nYes, i will do that.", "commid": "kubernetes_issue_89247", "tokennum": 132}], "negative_passages": []}
{"query_id": "q-en-kubernetes-258374fb96a4a9f09ed47fa71578906f9329a354ba0fe4e9906a6bf49489512f", "query": "echo \"COPY nsswitch.conf /etc/\" >> \"${docker_file_path}\" fi <del> # provide `--pull` argument to `docker build` if `KUBE_BUILD_PULL_LATEST_IMAGES` # is set to y or Y; otherwise try to build the image without forcefully # pulling the latest base image. local -a docker_build_opts=() if [[ \"${KUBE_BUILD_PULL_LATEST_IMAGES}\" =~ [yY] ]]; then docker_build_opts+=(\"--pull\") fi \"${DOCKER[@]}\" build \"${docker_build_opts[@]}\" -q -t \"${docker_image_tag}\" \"${docker_build_path}\" >/dev/null </del> <ins> \"${DOCKER[@]}\" build ${docker_build_opts} -q -t \"${docker_image_tag}\" \"${docker_build_path}\" >/dev/null </ins> # If we are building an official/alpha/beta release we want to keep # docker images and tag them appropriately. local -r release_docker_image_tag=\"${KUBE_DOCKER_REGISTRY-$docker_registry}/${binary_name}-${arch}:${KUBE_DOCKER_IMAGE_TAG-$docker_tag}\"", "positive_passages": [{"docid": "doc-en-kubernetes-5881ca0980b851b5719338c7fae783dda8e5f4172ff43857090ef00a488ce809", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: when I run , found bound variable err. What you expected to happen: Build success How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ):Linux paasn1 4.14.78-300.el7.Centos.x8664 SMP Sat Jan 5 15:49:43 CST 2019 x8664 x8664 x8664 GNU/Linux Install tools: Network plugin and version (if this is a network-related bug): Others: GNU bash version 4.2.46(2)-release (x8664-redhat-linux-gnu) Copyright (C) 2011 Free Software Foundation, Inc.\n/sig release", "commid": "kubernetes_issue_82962", "tokennum": 236}], "negative_passages": []}
{"query_id": "q-en-kubernetes-25971ad607f122b8d7a1ed1f5fea1e6c4195ad65bb3406126c008073d6bbc675", "query": "t.Errorf(\"unexpected object: %v\", rc2) t.FailNow() } <del> if test.expectPullPolicy != rc2.Spec.Template.Spec.InitContainers[0].ImagePullPolicy { t.Errorf(\"expected ImagePullPolicy: %s, got: %s\", test.expectPullPolicy, rc2.Spec.Template.Spec.InitContainers[0].ImagePullPolicy, ) </del> <ins> if err := assertInitContainers(rc2.Spec.Template.Spec.InitContainers, test.expected, test.validators); err != nil { t.Errorf(\"test %v failed: %v\", test.name, err) </ins> } } }", "positive_passages": [{"docid": "doc-en-kubernetes-c7797df648733fdf9e156246e323d8c03549ac9a3ca2ad30e283629a87abe7ee", "text": "What happened: kubelet doesn't seem to be able to manage containers started with CRI-O any more I'm testing kubelet + CRI-O on an Ubuntu 18.04 server installation, inside a qemu/kvm VM managed by Vagrant (see ), in order to be able to test k8s + KubeVirt + KataContainers, which are all compatible with CRI-O kubelet will obsess on starting new containers, which looks like and endless process, and the cluster never gets ready. For instance here are some syslogs : What you expected to happen: It used to work (see asciinema recording at ) a few days ago, but I fear some recent changes broke it. How to reproduce it (as minimally and precisely as possible): Testing with vagrant up --provider=libvirt on Linux with a clone of that commit: vagrant ssh into the VM and ps -edf f or tail -f /var/log/syslog would do... Anything else we need to know?: Environment: Kubernetes version (use ):Cloud provider or hardware configuration: qemu/kvm VM +OS (e.g: ): Ubuntu 18.04.2 LTS Kernel (e.g. ): Linux kubernetes-vagrant-01 4.15.0-48-generic -Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x8664 x8664 x8664 GNU/Linux Install tools: kubeadm as in Network plugin and version (if this is a network-related bug): Others:\n/sig node\nI can confirm this. If I start cri-o from a systemd service it fails with the above mentioned error message. Starting crio with without systemd works just fine. systemd file:\nThanks for your detailed report :) Just want to do some quick version confirming - you've been using k8s 1.14.1 both when it did and did not work? Any other version changes?\nNot sure for before, when it used to work, but according to the asciinema recording mentioned above (), it seems the same. However, not sure for CRI-O, underlying OS stuff (systemd, kernel, etc.). Sorry.\nI was looking for some information for days. I have exactly the same issue when I use podman + systemd on 18.04.2.", "commid": "kubernetes_issue_77615", "tokennum": 541}], "negative_passages": []}
{"query_id": "q-en-kubernetes-25971ad607f122b8d7a1ed1f5fea1e6c4195ad65bb3406126c008073d6bbc675", "query": "t.Errorf(\"unexpected object: %v\", rc2) t.FailNow() } <del> if test.expectPullPolicy != rc2.Spec.Template.Spec.InitContainers[0].ImagePullPolicy { t.Errorf(\"expected ImagePullPolicy: %s, got: %s\", test.expectPullPolicy, rc2.Spec.Template.Spec.InitContainers[0].ImagePullPolicy, ) </del> <ins> if err := assertInitContainers(rc2.Spec.Template.Spec.InitContainers, test.expected, test.validators); err != nil { t.Errorf(\"test %v failed: %v\", test.name, err) </ins> } } }", "positive_passages": [{"docid": "doc-en-kubernetes-dca27e474f7f12153e878b1f27ed663eb17fd42e2832a567b0d652b26f30c566", "text": "It is the same for both 14.15 and 14.18 kernels. Podman without systemd runs fine. Podman with systemd fails at runc with the same error podman[]: open /dev/stderr: no such device or address podman[]: NAME: runc - Open Container Initiative runtime podman[]: runc is a command line client for running applications packaged according to ... podman[]: time=\"2019-05-11T13:04:59-07:00\" level=error msg=\"open /dev/stderr: no such device or addressn\" podman[]: open /dev/stderr: no such device or address\nI've tried to reproduce it on 18.04.2 using Podman from but I am not able to reproduce it. Do you have any reproducer? How did you install Podman?\nI used ceph unit files to run ceph in podman rather than docker. Systemd unit successfully starts docker but fails with podman. I can successfully run the same podman container run command from the command line. How were you trying to replicate this? Can you post your unit file?\nHi, I'am having the same problem with Kubernetes with CRI-O. After joining a second worker node it fails to start flannel. gives the following error: What I've tried: Installing previous version of Kubernetes (from to ) Installing previous version of crio (from to ) Building runc myself from their github page and selecting this in the Running it on Ubunut 18.04.2 Issue: (the one giuseppe linked)\nI wonder if the issue is with systemd and runc. In both cases, crio and podman, I see runc help output which tells me that something is not being passed to runc that it needs.\nI've only used so it is different than your test and you confirmed it works from the CLI for you as well. Could you share your service file so I test it?\nI've tried systemd and cgroupfs but no luck so far.\nso it seems that runc fails to re-open . That seems like a runc issue, as it doesn't really need to reopen it. To fix the failure, you could use something like:\nJust an example.", "commid": "kubernetes_issue_77615", "tokennum": 504}], "negative_passages": []}
{"query_id": "q-en-kubernetes-25971ad607f122b8d7a1ed1f5fea1e6c4195ad65bb3406126c008073d6bbc675", "query": "t.Errorf(\"unexpected object: %v\", rc2) t.FailNow() } <del> if test.expectPullPolicy != rc2.Spec.Template.Spec.InitContainers[0].ImagePullPolicy { t.Errorf(\"expected ImagePullPolicy: %s, got: %s\", test.expectPullPolicy, rc2.Spec.Template.Spec.InitContainers[0].ImagePullPolicy, ) </del> <ins> if err := assertInitContainers(rc2.Spec.Template.Spec.InitContainers, test.expected, test.validators); err != nil { t.Errorf(\"test %v failed: %v\", test.name, err) </ins> } } }", "positive_passages": [{"docid": "doc-en-kubernetes-1a33d9e403b3728be8b8de7e79372d00143f16de361084780a7a026e224a4dd2", "text": "I use ceph-ansible to install cluster so it may need to install additional daemons like mon before running mgr but the error, in this case, should be different, [Unit] Description=Ceph Manager [Service] EnvironmentFile=-/etc/environment ExecStartPre=-/usr/bin/podman stop ceph-mgr-storage2n1-la ExecStartPre=-/usr/bin/podman rm ceph-mgr-storage2n1-la ExecStart=/usr/bin/podman run --rm --net=host  --memory=16G  --cpus=4  -v /var/lib/ceph:/var/lib/ceph:z  -v /etc/ceph:/etc/ceph:z  -v /var/run/ceph:/var/run/ceph:z  -v /etc/localtime:/etc/localtime:ro  -e CLUSTER=ceph  -e CEPHDAEMON=MGR  -e CONTAINERIMAGE=  {{ cephmgrdockerextraenv }}  --name=ceph-mgr-storage2n1-la  ExecStopPost=-/usr/bin/podman stop ceph-mgr-storage2n1-la Restart=always RestartSec=10s TimeoutStartSec=120 TimeoutStopSec=15 [Install] WantedBy=multi- delighted <:\nBTW, I projectatomic ppa and used apt-get -y podman to install. My podman version is 1.3.0 Sasha Litvak \u2014 You are receiving this because you commented. Reply to this email directly, view it on GitHub , or mute the thread\nCorrected file.", "commid": "kubernetes_issue_77615", "tokennum": 404}], "negative_passages": []}
{"query_id": "q-en-kubernetes-25971ad607f122b8d7a1ed1f5fea1e6c4195ad65bb3406126c008073d6bbc675", "query": "t.Errorf(\"unexpected object: %v\", rc2) t.FailNow() } <del> if test.expectPullPolicy != rc2.Spec.Template.Spec.InitContainers[0].ImagePullPolicy { t.Errorf(\"expected ImagePullPolicy: %s, got: %s\", test.expectPullPolicy, rc2.Spec.Template.Spec.InitContainers[0].ImagePullPolicy, ) </del> <ins> if err := assertInitContainers(rc2.Spec.Template.Spec.InitContainers, test.expected, test.validators); err != nil { t.Errorf(\"test %v failed: %v\", test.name, err) </ins> } } }", "positive_passages": [{"docid": "doc-en-kubernetes-bae004f13a06f51a77aaeb8de64c7434d457cced5ee158b56a68659aa46bb958", "text": "[Unit] Description=Ceph Manager [Service] EnvironmentFile=-/etc/environment ExecStartPre=-/usr/bin/podman stop ceph-mgr-storage2n1-la ExecStartPre=-/usr/bin/podman rm ceph-mgr-storage2n1-la ExecStart=/usr/bin/podman run --rm --net=host  --memory=16G  --cpus=4  -v /var/lib/ceph:/var/lib/ceph:z  -v /etc/ceph:/etc/ceph:z  -v /var/run/ceph:/var/run/ceph:z  -v /etc/localtime:/etc/localtime:ro  -e CLUSTER=ceph  -e CEPHDAEMON=MGR  -e CONTAINERIMAGE=  --name=ceph-mgr-storage2n1-la  ExecStopPost=-/usr/bin/podman stop ceph-mgr-storage2n1-la Restart=always RestartSec=10s TimeoutStartSec=120 TimeoutStopSec=15 [Install] WantedBy=multi- Giuseppe Scrivano <:\nWould it have an effect system wide? Can I add it to a unit file or unit override instead? Giuseppe Scrivano <:\nyes, I think it is better to add it only to the unit file\nWhy would runc work outside of systemd? And if it needs stderr, giving it Null in settings will redirect stderr to Null I presume? On Tue, May 14, 2019, 9:46 AM Giuseppe Scrivano <:\nRunning into same issues on Ubuntu 18.04.2 using cri-o-1.13 via PPA.\nPR here: opencontainers/runc\nUntil it is avaialble with project atomic and such, can I use a null workaround? Giuseppe Scrivano <:\nyes, but you will lose anything written to stderr. You could probably also use a file, like\nWhat about actually mounting dev and using /dev/stderr ? On Tue, May 14, 2019, 3:11 PM Giuseppe Scrivano <:\nis a symlink to . It is present, the issue here is that is a socket. The fix for runc got merged, could you use an updated runc?\nI tried apt update/upgrade and restarting crio, but I'm still getting the issue.", "commid": "kubernetes_issue_77615", "tokennum": 570}], "negative_passages": []}
{"query_id": "q-en-kubernetes-25971ad607f122b8d7a1ed1f5fea1e6c4195ad65bb3406126c008073d6bbc675", "query": "t.Errorf(\"unexpected object: %v\", rc2) t.FailNow() } <del> if test.expectPullPolicy != rc2.Spec.Template.Spec.InitContainers[0].ImagePullPolicy { t.Errorf(\"expected ImagePullPolicy: %s, got: %s\", test.expectPullPolicy, rc2.Spec.Template.Spec.InitContainers[0].ImagePullPolicy, ) </del> <ins> if err := assertInitContainers(rc2.Spec.Template.Spec.InitContainers, test.expected, test.validators); err != nil { t.Errorf(\"test %v failed: %v\", test.name, err) </ins> } } }", "positive_passages": [{"docid": "doc-en-kubernetes-a9af1b8339c2af3d5a8899da2b8916e4bc8194e1229dc4a9dc77c862af07f4a9", "text": "Could it be that crio's runc is not updated yet? Edit Build new runc from and it is working now. Think crio hasn't updated it yet with their repository.\nI'm running this version from PPA repo for ubuntu and it fails: could you point to version/commit or whatever helps identify the fixed version/snapshot ? Thanks in advance.\nat the moment it is only fixed upstream. You'd need to build runc manually\nIs there a version of the package on ppa we can downgrade to? On Wed, May 15, 2019, 4:35 AM Giuseppe Scrivano <:\ncould we update the runc version in the PPA repo?\nThank you. I seem them built but nut pushed to ppa yet.\nshould be available now.. let me know..\ncri-o-runc (1.0.0-rc6-1~dev~ubuntu18.04~ppa42) bionic; urgency=medium autobuilt -- Lokesh Mandvekar (Bot) <, 15 May 2019 16:54:40 +0000\nThank you, everyone, for a quick turn around. Quick testing showed that fix is working, but more testing is needed. Lokesh Mandvekar <:\nI confirm my initial tests with seem to confirm the regression is fixed. Many thanks\nI also confirm the fix working for podman. Olivier Berger <:", "commid": "kubernetes_issue_77615", "tokennum": 305}], "negative_passages": []}
{"query_id": "q-en-kubernetes-25971ad607f122b8d7a1ed1f5fea1e6c4195ad65bb3406126c008073d6bbc675", "query": "t.Errorf(\"unexpected object: %v\", rc2) t.FailNow() } <del> if test.expectPullPolicy != rc2.Spec.Template.Spec.InitContainers[0].ImagePullPolicy { t.Errorf(\"expected ImagePullPolicy: %s, got: %s\", test.expectPullPolicy, rc2.Spec.Template.Spec.InitContainers[0].ImagePullPolicy, ) </del> <ins> if err := assertInitContainers(rc2.Spec.Template.Spec.InitContainers, test.expected, test.validators); err != nil { t.Errorf(\"test %v failed: %v\", test.name, err) </ins> } } }", "positive_passages": [{"docid": "doc-en-kubernetes-c1c167f97d0d68a2d507d0d919d58cd680ff8ed576e3225c7b24d703a964bd61", "text": "<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.--Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see ): No What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): initContainers imagePullPolicy initContainers required value Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT <!-- If this is a BUG REPORT, please: Fill in as much of the template below as you can. If you leave out information, we can't help you as well. If this is a FEATURE REQUEST, please: Describe in detail the feature/behavior/change you'd like to see. In both cases, be ready for followup questions, and please respond in a timely manner. If we can't reproduce a bug or think a feature already exists, we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why. --Kubernetes version (use ): Environment: Cloud provider or hardware configuration: GCE OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: cluster/kube- Others: What happened: When trying to create either a ReplicaSet or Replication Controller whose Pod template contains an Init Container, the validation fails saying is a required value. What you expected to happen: The create should succeed and the Init Container should receive a default . How to reproduce it (as minimally and precisely as possible): Try to create either of the following: ReplicaSet Replication Controller Anything else do we need to know: If I add to the Init Container in the ReplicaSet or Replication Controller Pod template, the create succeeds. When I create an Init Container without in a StatefulSet Pod template, it succeeds. When I create an Init Container without in a bare Pod, it succeeds:\nLooks like defaulting not being applied on server? That is probably due to removing defaulting from convert. Surprised we didn't catch this earlier\nSome values still not being defaulted\n, I'm going to create a PR if none works on it.\nWe decode from bytes, set defaults and then convert; but for init containers, we delay the decode from \"decode phase\" to \"convert phase\" at .", "commid": "kubernetes_issue_38542", "tokennum": 524}], "negative_passages": []}
{"query_id": "q-en-kubernetes-25971ad607f122b8d7a1ed1f5fea1e6c4195ad65bb3406126c008073d6bbc675", "query": "t.Errorf(\"unexpected object: %v\", rc2) t.FailNow() } <del> if test.expectPullPolicy != rc2.Spec.Template.Spec.InitContainers[0].ImagePullPolicy { t.Errorf(\"expected ImagePullPolicy: %s, got: %s\", test.expectPullPolicy, rc2.Spec.Template.Spec.InitContainers[0].ImagePullPolicy, ) </del> <ins> if err := assertInitContainers(rc2.Spec.Template.Spec.InitContainers, test.expected, test.validators); err != nil { t.Errorf(\"test %v failed: %v\", test.name, err) </ins> } } }", "positive_passages": [{"docid": "doc-en-kubernetes-69dbac4fd7f4ee2d4feb0af6994cc2f74e65b4d3465b8e0c7014cfb5909cea9b", "text": "The defaults has been handled for initContainer at . /cc I'm working to find a solution for that; if any suggestion, please let me know.\nWould this bug affect the deletion of jobs with an init-container? I ran into this bug and adjusted my manifest to add the pull policy to the init-container. However, I now cannot delete said job claiming a field is immutable. Example:\n, not sure now. Let me check it,\nSame error here with version 1.5.1, 1.5.2 The Job \"grafana-import-dashboards\" is invalid: [0].imagePullPolicy: Required value With this setup: kubectl apply -f monitoring Not working even if I specify a pullpolicy in the yaml. If I roll back to 1.4.7, it is working. Thank you. Greg.\nany updates on a PR to address this issue? Is anyone from able to pick this issue up otherwise?\n, here's the latest status: there's is a PR to generate for each Object (), it works for Object (Pod, Job) now but List; I'm working to make it generating for List.\nWhy would you need List to work? No client side logic should be decoding lists except as a generic submission.\nThe List tests are failed in . There's no for List, so no code to decode init-container annotation, e.g. of should call 's recursively.\nThanks for the update\n+1\nAny update on this? I still getting this issue with the last version of 1.5.3 on GKE?\nping for the comments? should we merge the PR for 1.5?\n, there's a PR () that handled that issue; but we're discussing not to merge it because initContainers had been moved to fields, and fields is the recommended way to use since 1.6. But I'd like to get & 's comments on 1.5.\nThis is still an issue in 1.5.3 when using annotations: Without the deployment would not be accepted\nping & :).\ni dont think this is fixed in 1.5 I just encountered this bug on 1.5.3\n, yes, the PR is NOT merged to any branch, so the issue is still here. I'll create a PR for 1.5.\nHi Anyone help this issue.", "commid": "kubernetes_issue_38542", "tokennum": 520}], "negative_passages": []}
{"query_id": "q-en-kubernetes-25971ad607f122b8d7a1ed1f5fea1e6c4195ad65bb3406126c008073d6bbc675", "query": "t.Errorf(\"unexpected object: %v\", rc2) t.FailNow() } <del> if test.expectPullPolicy != rc2.Spec.Template.Spec.InitContainers[0].ImagePullPolicy { t.Errorf(\"expected ImagePullPolicy: %s, got: %s\", test.expectPullPolicy, rc2.Spec.Template.Spec.InitContainers[0].ImagePullPolicy, ) </del> <ins> if err := assertInitContainers(rc2.Spec.Template.Spec.InitContainers, test.expected, test.validators); err != nil { t.Errorf(\"test %v failed: %v\", test.name, err) </ins> } } }", "positive_passages": [{"docid": "doc-en-kubernetes-cd1dc8216bffde40e45195a0aceb1bbd0c560296ad557f563dafcf3df89eeea5", "text": "#cat mongo- apiVersion: v1 kind: Pod metadata: labels: name: mongo-svc-a name: mongo-deployment spec: replicas: 1 template: metadata: labels: name: mongo spec: containers: image: mongo name: mongo ports: name: mongo containerPort: hostPort: volumeMounts: mountPath: \"/data/db\" name: mongopv volumes: name: mongopv persistentVolumeClaim: claimName: mongopvc When i want create mongo db container by using this file folowing error is occured. The Pod \"mongo-deployment\" is invalid:spec.containers: Required value\n, it seems there're two here, please remove the first one and have a try.\nHi my kubectl binary is configured at ubuntu 16.04 machine.", "commid": "kubernetes_issue_38542", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-25971ad607f122b8d7a1ed1f5fea1e6c4195ad65bb3406126c008073d6bbc675", "query": "t.Errorf(\"unexpected object: %v\", rc2) t.FailNow() } <del> if test.expectPullPolicy != rc2.Spec.Template.Spec.InitContainers[0].ImagePullPolicy { t.Errorf(\"expected ImagePullPolicy: %s, got: %s\", test.expectPullPolicy, rc2.Spec.Template.Spec.InitContainers[0].ImagePullPolicy, ) </del> <ins> if err := assertInitContainers(rc2.Spec.Template.Spec.InitContainers, test.expected, test.validators); err != nil { t.Errorf(\"test %v failed: %v\", test.name, err) </ins> } } }", "positive_passages": [{"docid": "doc-en-kubernetes-7c77a1e7ea84d582b899fa6b8d7216504334c47e064fb8eaad5c523c3bc66a32", "text": "NAME LABELS STATUS 10.1 Ready,SchedulingDisabled 10.2 10.1.10.2 Ready 10.3 Ready apiVersion: v1 kind: Node metadata: creationTimestamp: 2017-03-03T14:41:52Z labels: 10.1.10.1 name: 10.1.10.1 resourceVersion: \"\" selfLink: /api/v1/nodes/10.1.10.1 uid: -001f-11e7-8e83- spec: externalID: 10.1.10.1 status: addresses: address: 10.1.10.1 type: LegacyHostIP address: 10.1.10.1 type: InternalIP capacity: cpu: \"2\" memory: 4041352Ki pods: \"110\" conditions: lastHeartbeatTime: 2017-04-05T18:58:42Z lastTransitionTime: 2017-03-03T14:41:52Z message: kubelet has sufficient disk space available reason: KubeletHasSufficientDisk status: \"False\" type: OutOfDisk lastHeartbeatTime: 2017-04-05T18:58:42Z lastTransitionTime: 2017-04-05T15:27:52Z message: kubelet is posting ready status reason: KubeletReady status: \"True\" type: Ready nodeInfo: bootID: -6124-4ac7-ab96- containerRuntimeVersion: docker://1.12.6 kernelVersion: 4.9.16-coreos-r1 kubeProxyVersion: v1.2.4+coreos.1 kubeletVersion: v1.2.4+coreos.1 machineID: osImage: Container Linux by CoreOS 1298.7.0 (Ladybug) systemUUID: C3FD9852-2DFB-21F4-CE07-2597A746D99D When i create pv for creation pod is shows pv is pending. Please give any suggestions.....\nIs there solution of this problem with version 2.7. Still facing the same. what exactly expectation of helm upgrade --install relname chartsdirectory is is expected to work on first time installation in case with CI/CD Pipelines.", "commid": "kubernetes_issue_38542", "tokennum": 511}], "negative_passages": []}
{"query_id": "q-en-kubernetes-25f3fdcff06f5417d62219d49d4bdfff9cbe2ac20d48e725985a2c2d73ac095d", "query": "package dockertools import ( <del> \"bufio\" </del> \"bytes\" \"errors\" \"fmt\"", "positive_passages": [{"docid": "doc-en-kubernetes-65bf469670180d69e57fdc1a820a8f2f435cec685a9975e90f226dd126851fba", "text": "As far as I can tell, container liveness probes of type exec flat out don't work against clusters built at head. I had the kubelet always log the output of the exec'ed command, and it's always empty no matter what I exec, causing the probe to fail since it requires the output to be equal to the string \"ok\". If you want to test it, try adding a liveness probe of this form to any container: I also tried these lovely forms, to more closely match the liveness example under examples/: On the plus side, this may be an opportunistic time to switch over to\nThe reason that the e2e test for exec liveness probes hasn't caught this is that it only tests that containers are restarted when they fail liveness probes. It doesn't test that containers aren't restarted when their liveness checks should be succeeding. The e2e test's exec'ed commands also only ever produced empty output, rather than the expected \"fail\" output.\nIs it possible to include this in a new pre-release, since it fixes a bug in health checking? I see it merged in master and I'm wondering what the policy is of releasing new code in a separate (0.16.*) release.", "commid": "kubernetes_issue_7618", "tokennum": 275}], "negative_passages": []}
{"query_id": "q-en-kubernetes-26001b82068678a5265ab8f4d4004fe4242c7e269484d8b43c62dbaad3e54a99", "query": "\"github.com/golang/glog\" \"k8s.io/api/core/v1\" <del> clientv1 \"k8s.io/api/core/v1\" </del> metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/runtime\" \"k8s.io/apimachinery/pkg/types\" \"k8s.io/client-go/tools/record\" runtimeapi \"k8s.io/kubernetes/pkg/kubelet/apis/cri/v1alpha1/runtime\" <del> \"k8s.io/kubernetes/pkg/kubelet/events\" </del> \"k8s.io/kubernetes/pkg/kubelet/util/format\" \"k8s.io/kubernetes/pkg/kubelet/util/ioutils\" hashutil \"k8s.io/kubernetes/pkg/util/hash\"", "positive_passages": [{"docid": "doc-en-kubernetes-b0087f3d33811f5a8bf21a1757c4fff7aaef7add29731940c9c3bd61ec9b29c4", "text": "Is this a BUG REPORT or FEATURE REQUEST?: What happened: Now the and has been consistent in by PR . There is no need to convert v1.ObjectReference to clientv1.ObjectReference in . What you expected to happen: Remove this function and cleanup the codes which call this function. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?:\nThere are no sig labels on this issue. Please by:<br(1) mentioning a sig: <bre.g., for API Machinery<br(2) specifying the label manually: <bre.g., for sig/scalability<br<brNote: method (1) will trigger a notification to the team. You can find the team list and label list\nWill submit the cleanup after PR merged.\n/sig api-machinery\n/sub", "commid": "kubernetes_issue_48747", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2651108ada4f46e74e95aef5644cce8dd5e4ace23bc3645dbcfacd87b1ba87db", "query": "// Score is a list of plugins that should be invoked when ranking nodes that have passed the filtering phase. Score *PluginSet `json:\"score,omitempty\"` <del> // NormalizeScore is a list of plugins that should be invoked after the scoring phase to normalize scores. NormalizeScore *PluginSet `json:\"normalizeScore,omitempty\"` </del> // Reserve is a list of plugins invoked when reserving a node to run the pod. Reserve *PluginSet `json:\"reserve,omitempty\"`", "positive_passages": [{"docid": "doc-en-kubernetes-65d9c28fb77fe0bb882df060209fc22bf399af9c3b9dfe5829b0e5a45dc20b3d", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Consolidate ) into Score plugin set in config API. Why is this needed: NormalizeScore extension point is implemented in . We decided to treat NormalizeScore as an \"optional\" step of Score plugin, see . However, we deferred the removal of due to API review delays. Now that PR was merged. We can start the actual removal from the API and start the API review process. /sig scheduling\n/assign", "commid": "kubernetes_issue_80908", "tokennum": 113}], "negative_passages": []}
{"query_id": "q-en-kubernetes-267d15d8df7d801a58779dd334102220c8e0795c2c46a651b0a4732e4ee485ad", "query": "runtime.ReallyCrash = s.ReallyCrashForTesting rand.Seed(time.Now().UTC().UnixNano()) <del> credentialprovider.SetPreferredDockercfgPath(s.RootDirectory) glog.V(2).Infof(\"Using root directory: %v\", s.RootDirectory) </del> // TODO(vmarmol): Do this through container config. oomAdjuster := kcfg.OOMAdjuster if err := oomAdjuster.ApplyOOMScoreAdj(0, int(s.OOMScoreAdj)); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-ca640d6faf4286189814f4ad1e01c7d7710200569bbe8ad0dc1acda128b91391", "text": "During the startup process of kubelet, we have Since we have following Code segment 1 and 2 seems dup to me. Am i getting this wrong?", "commid": "kubernetes_issue_25345", "tokennum": 32}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2680d9666e7e5fc51ec95e98fa3e10e045e84b823074265b6c41b266ebbdc55b", "query": "<ins> /* Copyright 2014 The Kubernetes Authors All rights reserved. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package e2e import ( \"encoding/json\" \"fmt\" \"time\" \"github.com/GoogleCloudPlatform/kubernetes/pkg/api\" \"github.com/GoogleCloudPlatform/kubernetes/pkg/client\" \"github.com/GoogleCloudPlatform/kubernetes/pkg/util/wait\" . \"github.com/onsi/ginkgo\" ) // partially cloned from webserver.go type State struct { Received map[string]int } func testPreStop(c *client.Client, ns string) { // This is the server that will receive the preStop notification podDescr := &api.Pod{ ObjectMeta: api.ObjectMeta{ Name: \"server\", }, Spec: api.PodSpec{ Containers: []api.Container{ { Name:  \"server\", Image: \"gcr.io/google_containers/nettest:1.3\", Ports: []api.ContainerPort{{ContainerPort: 8080}}, }, }, }, } By(fmt.Sprintf(\"Creating server pod %s in namespace %s\", podDescr.Name, ns)) _, err := c.Pods(ns).Create(podDescr) expectNoError(err, fmt.Sprintf(\"creating pod %s\", podDescr.Name)) // At the end of the test, clean up by removing the pod. defer func() { By(\"Deleting the server pod\") c.Pods(ns).Delete(podDescr.Name, nil) }() By(\"Waiting for pods to come up.\") err = waitForPodRunningInNamespace(c, podDescr.Name, ns) expectNoError(err, \"waiting for server pod to start\") val := \"{\"Source\": \"prestop\"}\" podOut, err := c.Pods(ns).Get(podDescr.Name) expectNoError(err, \"getting pod info\") preStopDescr := &api.Pod{ ObjectMeta: api.ObjectMeta{ Name: \"tester\", }, Spec: api.PodSpec{ Containers: []api.Container{ { Name:    \"tester\", Image:   \"busybox\", Command: []string{\"sleep\", \"600\"}, Lifecycle: &api.Lifecycle{ PreStop: &api.Handler{ Exec: &api.ExecAction{ Command: []string{ \"wget\", \"-O-\", \"--post-data=\" + val, fmt.Sprintf(\"http://%s:8080/write\", podOut.Status.PodIP), }, }, }, }, }, }, }, } By(fmt.Sprintf(\"Creating tester pod %s in namespace %s\", podDescr.Name, ns)) _, err = c.Pods(ns).Create(preStopDescr) expectNoError(err, fmt.Sprintf(\"creating pod %s\", preStopDescr.Name)) deletePreStop := true // At the end of the test, clean up by removing the pod. defer func() { if deletePreStop { By(\"Deleting the tester pod\") c.Pods(ns).Delete(preStopDescr.Name, nil) } }() err = waitForPodRunningInNamespace(c, preStopDescr.Name, ns) expectNoError(err, \"waiting for tester pod to start\") // Delete the pod with the preStop handler. By(\"Deleting pre-stop pod\") if err := c.Pods(ns).Delete(preStopDescr.Name, nil); err == nil { deletePreStop = false } expectNoError(err, fmt.Sprintf(\"deleting pod: %s\", preStopDescr.Name)) // Validate that the server received the web poke. err = wait.Poll(time.Second*5, time.Second*60, func() (bool, error) { if body, err := c.Get(). Namespace(ns).Prefix(\"proxy\"). Resource(\"pods\"). Name(podDescr.Name). Suffix(\"read\"). DoRaw(); err != nil { By(fmt.Sprintf(\"Error validating prestop: %v\", err)) } else { state := State{} err := json.Unmarshal(body, &state) if err != nil { Logf(\"Error parsing: %v\", err) return false, nil } if state.Received[\"prestop\"] != 0 { return true, nil } Logf(\"Saw: %s\", string(body)) } return false, nil }) expectNoError(err, \"validating pre-stop.\") } var _ = Describe(\"PreStop\", func() { f := NewFramework(\"prestop\") It(\"should call prestop when killing a pod\", func() { testPreStop(f.Client, f.Namespace.Name) }) }) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-2d8b9ac51e195a52880b5015da51ade673286a0fb623e49df0244ac4dfec5669", "text": "PreStop in Lifecycle is a very excited feature that I want it so much. With it, I can do some clean work before killing the Pod/Container, for example, I need this container stop receiving requests first, then complete processing its requests already received before it is killed. However It does not work as PostStop now. And I have checked the latest code and found it is still not implemented. Could anyone give a time point on it?\nSorry, prestop hasn't been implemented yet. See discussion in .\nI'll implement it once is finished\nthanks, I will also subscribe\n/subscribe\nMoved to post-1.0\nPR is in flight.\nwas merged. We should add an e2e test, though.\nTried by E2E, it works! And it can be closed. Well done.", "commid": "kubernetes_issue_7091", "tokennum": 170}], "negative_passages": []}
{"query_id": "q-en-kubernetes-268194a9c777c8d494871d4cf61d20185026adf554baef7e98b9928ceeb64457", "query": "} func TestDeleteOrEvict(t *testing.T) { <del> for _, evictionSupported := range []bool{true, false} { evictionSupported := evictionSupported t.Run(fmt.Sprintf(\"evictionSupported=%v\", evictionSupported), func(t *testing.T) { h := &Helper{ Out:                os.Stdout, GracePeriodSeconds: 10, } // Create 4 pods, and try to remove the first 2 var expectedEvictions []policyv1beta1.Eviction var create []runtime.Object deletePods := []corev1.Pod{} for i := 1; i <= 4; i++ { pod := &corev1.Pod{} pod.Name = fmt.Sprintf(\"mypod-%d\", i) pod.Namespace = \"default\" </del> <ins> tests := []struct { description       string evictionSupported bool disableEviction   bool }{ { description:       \"eviction supported/enabled\", evictionSupported: true, disableEviction:   false, }, { description:       \"eviction unsupported/disabled\", evictionSupported: false, disableEviction:   false, }, { description:       \"eviction supported/disabled\", evictionSupported: true, disableEviction:   true, }, { description:       \"eviction unsupported/disabled\", evictionSupported: false, disableEviction:   false, }, } for _, tc := range tests { t.Run(tc.description, func(t *testing.T) { h := &Helper{ Out:                os.Stdout, GracePeriodSeconds: 10, } </ins> <del> create = append(create, pod) if i <= 2 { deletePods = append(deletePods, *pod) </del> <ins> // Create 4 pods, and try to remove the first 2 var expectedEvictions []policyv1beta1.Eviction var create []runtime.Object deletePods := []corev1.Pod{} for i := 1; i <= 4; i++ { pod := &corev1.Pod{} pod.Name = fmt.Sprintf(\"mypod-%d\", i) pod.Namespace = \"default\" </ins> <del> if evictionSupported { eviction := policyv1beta1.Eviction{} eviction.Kind = \"Eviction\" eviction.APIVersion = \"policy/v1\" eviction.Namespace = pod.Namespace eviction.Name = pod.Name </del> <ins> create = append(create, pod) if i <= 2 { deletePods = append(deletePods, *pod) </ins> <del> gracePeriodSeconds := int64(h.GracePeriodSeconds) eviction.DeleteOptions = &metav1.DeleteOptions{ GracePeriodSeconds: &gracePeriodSeconds, } </del> <ins> if tc.evictionSupported && !tc.disableEviction { eviction := policyv1beta1.Eviction{} eviction.Kind = \"Eviction\" eviction.APIVersion = \"policy/v1\" eviction.Namespace = pod.Namespace eviction.Name = pod.Name </ins> <del> expectedEvictions = append(expectedEvictions, eviction) </del> <ins> gracePeriodSeconds := int64(h.GracePeriodSeconds) eviction.DeleteOptions = &metav1.DeleteOptions{ GracePeriodSeconds: &gracePeriodSeconds, </ins> } <ins> expectedEvictions = append(expectedEvictions, eviction) </ins> } } <ins> } </ins> <del> // Build the fake client k := fake.NewSimpleClientset(create...) if evictionSupported { addEvictionSupport(t, k) } h.Client = k </del> <ins> // Build the fake client k := fake.NewSimpleClientset(create...) if tc.evictionSupported { addEvictionSupport(t, k) } h.Client = k h.DisableEviction = tc.disableEviction // Do the eviction if err := h.DeleteOrEvictPods(deletePods); err != nil { t.Fatalf(\"error from DeleteOrEvictPods: %v\", err) } </ins> <del> // Do the eviction if err := h.DeleteOrEvictPods(deletePods); err != nil { t.Fatalf(\"error from DeleteOrEvictPods: %v\", err) </del> <ins> // Test that other pods are still there var remainingPods []string { podList, err := k.CoreV1().Pods(\"\").List(metav1.ListOptions{}) if err != nil { t.Fatalf(\"error listing pods: %v\", err) </ins> } <del> // Test that other pods are still there var remainingPods []string { podList, err := k.CoreV1().Pods(\"\").List(metav1.ListOptions{}) if err != nil { t.Fatalf(\"error listing pods: %v\", err) } for _, pod := range podList.Items { remainingPods = append(remainingPods, pod.Namespace+\"/\"+pod.Name) } sort.Strings(remainingPods) } expected := []string{\"default/mypod-3\", \"default/mypod-4\"} if !reflect.DeepEqual(remainingPods, expected) { t.Errorf(\"unexpected remaining pods after DeleteOrEvictPods; actual %v; expected %v\", remainingPods, expected) </del> <ins> for _, pod := range podList.Items { remainingPods = append(remainingPods, pod.Namespace+\"/\"+pod.Name) </ins> } <ins> sort.Strings(remainingPods) } expected := []string{\"default/mypod-3\", \"default/mypod-4\"} if !reflect.DeepEqual(remainingPods, expected) { t.Errorf(\"%s: unexpected remaining pods after DeleteOrEvictPods; actual %v; expected %v\", tc.description, remainingPods, expected) } </ins> <del> // Test that pods were evicted as expected var actualEvictions []policyv1beta1.Eviction for _, action := range k.Actions() { if action.GetVerb() != \"create\" || action.GetResource().Resource != \"pods\" || action.GetSubresource() != \"eviction\" { continue } eviction := *action.(ktest.CreateAction).GetObject().(*policyv1beta1.Eviction) actualEvictions = append(actualEvictions, eviction) } sort.Slice(actualEvictions, func(i, j int) bool { return actualEvictions[i].Name < actualEvictions[j].Name }) if !reflect.DeepEqual(actualEvictions, expectedEvictions) { t.Errorf(\"unexpected evictions; actual %v; expected %v\", actualEvictions, expectedEvictions) </del> <ins> // Test that pods were evicted as expected var actualEvictions []policyv1beta1.Eviction for _, action := range k.Actions() { if action.GetVerb() != \"create\" || action.GetResource().Resource != \"pods\" || action.GetSubresource() != \"eviction\" { continue </ins> } <ins> eviction := *action.(ktest.CreateAction).GetObject().(*policyv1beta1.Eviction) actualEvictions = append(actualEvictions, eviction) } sort.Slice(actualEvictions, func(i, j int) bool { return actualEvictions[i].Name < actualEvictions[j].Name </ins> }) <ins> if !reflect.DeepEqual(actualEvictions, expectedEvictions) { t.Errorf(\"%s: unexpected evictions; actual %v; expected %v\", tc.description, actualEvictions, expectedEvictions) } }) </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-1de7ff63e7ce8b64bf52f2105a2efc7375b6d0f9c29fe56834b2956453e0280d", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Allow to have an additional flag (e.g. or ) to allow a to drain pods off a node, even if they violate PodDisruptionBudgets Why is this needed: There are times where you want to drain pods off a node even if violating a PDB. For example, if you are running a one-worker node kubernetes cluster (not minikube), and you want to upgrade it. Or, like me, you are running a test cluster and want to scale down to zero nodes when you're not going to be using the cluster for a while in order to save costs. If that worker node has a deployment with a PDB, then will get stuck as it cannot get rid of the pod while respecting the PDB, which is expected; but in this case, it is a hindrance. Adding the switch will allow users to explicitly acknowledge that they want to ignore the PDBs (and accept the corresponding downtime for an application/service)\n/sig node\n+1\n+1 Our company offers Kubernetes as PaaS. We manage Kubernetes, including IaaS OS updates and if a customer does not specify the PDB correctly, we are not able to drain the node for the OS updates. A flag would be werry helpfull for our use case.\n+1\n/active\nI have created to address this. This is a pretty simple implementation, but I think it achieves the desired results. A suitable workflow would be: 1) Configure you component to use drain as normal 2) After some timeout, run drain with --disable-eviction option.\nI'll wait until the PR is merged and released before testing, but if I understand right, it would require me do this, right? If so, I think it would be better if we did it a different way and have one call, something like this: Where implies that if the drain is still running after this time, switch to the mode without having to call kubectl again\nI think that would require a sizeable refactor or add a great deal of complexity to the code, the same could be achieved with In practical terms, I'm focused on automatic node remediation via destroying the node and getting a new one. The timeout would be very large, the drain library is blocking, so I want it to fail quickly and requeue.", "commid": "kubernetes_issue_83307", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-268194a9c777c8d494871d4cf61d20185026adf554baef7e98b9928ceeb64457", "query": "} func TestDeleteOrEvict(t *testing.T) { <del> for _, evictionSupported := range []bool{true, false} { evictionSupported := evictionSupported t.Run(fmt.Sprintf(\"evictionSupported=%v\", evictionSupported), func(t *testing.T) { h := &Helper{ Out:                os.Stdout, GracePeriodSeconds: 10, } // Create 4 pods, and try to remove the first 2 var expectedEvictions []policyv1beta1.Eviction var create []runtime.Object deletePods := []corev1.Pod{} for i := 1; i <= 4; i++ { pod := &corev1.Pod{} pod.Name = fmt.Sprintf(\"mypod-%d\", i) pod.Namespace = \"default\" </del> <ins> tests := []struct { description       string evictionSupported bool disableEviction   bool }{ { description:       \"eviction supported/enabled\", evictionSupported: true, disableEviction:   false, }, { description:       \"eviction unsupported/disabled\", evictionSupported: false, disableEviction:   false, }, { description:       \"eviction supported/disabled\", evictionSupported: true, disableEviction:   true, }, { description:       \"eviction unsupported/disabled\", evictionSupported: false, disableEviction:   false, }, } for _, tc := range tests { t.Run(tc.description, func(t *testing.T) { h := &Helper{ Out:                os.Stdout, GracePeriodSeconds: 10, } </ins> <del> create = append(create, pod) if i <= 2 { deletePods = append(deletePods, *pod) </del> <ins> // Create 4 pods, and try to remove the first 2 var expectedEvictions []policyv1beta1.Eviction var create []runtime.Object deletePods := []corev1.Pod{} for i := 1; i <= 4; i++ { pod := &corev1.Pod{} pod.Name = fmt.Sprintf(\"mypod-%d\", i) pod.Namespace = \"default\" </ins> <del> if evictionSupported { eviction := policyv1beta1.Eviction{} eviction.Kind = \"Eviction\" eviction.APIVersion = \"policy/v1\" eviction.Namespace = pod.Namespace eviction.Name = pod.Name </del> <ins> create = append(create, pod) if i <= 2 { deletePods = append(deletePods, *pod) </ins> <del> gracePeriodSeconds := int64(h.GracePeriodSeconds) eviction.DeleteOptions = &metav1.DeleteOptions{ GracePeriodSeconds: &gracePeriodSeconds, } </del> <ins> if tc.evictionSupported && !tc.disableEviction { eviction := policyv1beta1.Eviction{} eviction.Kind = \"Eviction\" eviction.APIVersion = \"policy/v1\" eviction.Namespace = pod.Namespace eviction.Name = pod.Name </ins> <del> expectedEvictions = append(expectedEvictions, eviction) </del> <ins> gracePeriodSeconds := int64(h.GracePeriodSeconds) eviction.DeleteOptions = &metav1.DeleteOptions{ GracePeriodSeconds: &gracePeriodSeconds, </ins> } <ins> expectedEvictions = append(expectedEvictions, eviction) </ins> } } <ins> } </ins> <del> // Build the fake client k := fake.NewSimpleClientset(create...) if evictionSupported { addEvictionSupport(t, k) } h.Client = k </del> <ins> // Build the fake client k := fake.NewSimpleClientset(create...) if tc.evictionSupported { addEvictionSupport(t, k) } h.Client = k h.DisableEviction = tc.disableEviction // Do the eviction if err := h.DeleteOrEvictPods(deletePods); err != nil { t.Fatalf(\"error from DeleteOrEvictPods: %v\", err) } </ins> <del> // Do the eviction if err := h.DeleteOrEvictPods(deletePods); err != nil { t.Fatalf(\"error from DeleteOrEvictPods: %v\", err) </del> <ins> // Test that other pods are still there var remainingPods []string { podList, err := k.CoreV1().Pods(\"\").List(metav1.ListOptions{}) if err != nil { t.Fatalf(\"error listing pods: %v\", err) </ins> } <del> // Test that other pods are still there var remainingPods []string { podList, err := k.CoreV1().Pods(\"\").List(metav1.ListOptions{}) if err != nil { t.Fatalf(\"error listing pods: %v\", err) } for _, pod := range podList.Items { remainingPods = append(remainingPods, pod.Namespace+\"/\"+pod.Name) } sort.Strings(remainingPods) } expected := []string{\"default/mypod-3\", \"default/mypod-4\"} if !reflect.DeepEqual(remainingPods, expected) { t.Errorf(\"unexpected remaining pods after DeleteOrEvictPods; actual %v; expected %v\", remainingPods, expected) </del> <ins> for _, pod := range podList.Items { remainingPods = append(remainingPods, pod.Namespace+\"/\"+pod.Name) </ins> } <ins> sort.Strings(remainingPods) } expected := []string{\"default/mypod-3\", \"default/mypod-4\"} if !reflect.DeepEqual(remainingPods, expected) { t.Errorf(\"%s: unexpected remaining pods after DeleteOrEvictPods; actual %v; expected %v\", tc.description, remainingPods, expected) } </ins> <del> // Test that pods were evicted as expected var actualEvictions []policyv1beta1.Eviction for _, action := range k.Actions() { if action.GetVerb() != \"create\" || action.GetResource().Resource != \"pods\" || action.GetSubresource() != \"eviction\" { continue } eviction := *action.(ktest.CreateAction).GetObject().(*policyv1beta1.Eviction) actualEvictions = append(actualEvictions, eviction) } sort.Slice(actualEvictions, func(i, j int) bool { return actualEvictions[i].Name < actualEvictions[j].Name }) if !reflect.DeepEqual(actualEvictions, expectedEvictions) { t.Errorf(\"unexpected evictions; actual %v; expected %v\", actualEvictions, expectedEvictions) </del> <ins> // Test that pods were evicted as expected var actualEvictions []policyv1beta1.Eviction for _, action := range k.Actions() { if action.GetVerb() != \"create\" || action.GetResource().Resource != \"pods\" || action.GetSubresource() != \"eviction\" { continue </ins> } <ins> eviction := *action.(ktest.CreateAction).GetObject().(*policyv1beta1.Eviction) actualEvictions = append(actualEvictions, eviction) } sort.Slice(actualEvictions, func(i, j int) bool { return actualEvictions[i].Name < actualEvictions[j].Name </ins> }) <ins> if !reflect.DeepEqual(actualEvictions, expectedEvictions) { t.Errorf(\"%s: unexpected evictions; actual %v; expected %v\", tc.description, actualEvictions, expectedEvictions) } }) </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-b7bae32dd27973078cd1b23d1dbdce25c736eb34a86ee68bc51d78045bb08cfb", "text": "I'm going to be performing the calculation of when it's appropriate to evict/delete outside of the drain library, and I suspect most will be as well, so there's not really a great incentive to do it in the drain library itself IMO.\nThat's all good, I have no issue using the flag as long as does error out and return a non-zero code as expected (there's been a few times where it seems to error out, but still return 0)", "commid": "kubernetes_issue_83307", "tokennum": 105}], "negative_passages": []}
{"query_id": "q-en-kubernetes-268b76d614de2c8d974e06bf7118eb52a39fe654dc93e88fa1ac1869d2779cdf", "query": "# TODO update to dns role once we have one. ${KUBECTL} --kubeconfig=\"${CERT_DIR}/admin.kubeconfig\" create clusterrolebinding system:kube-dns --clusterrole=cluster-admin --serviceaccount=kube-system:default <del> # use kubectl to create kubedns rc and service </del> <ins> # use kubectl to create kubedns deployment and service </ins> ${KUBECTL} --kubeconfig=\"${CERT_DIR}/admin.kubeconfig\" --namespace=kube-system create -f kubedns-deployment.yaml ${KUBECTL} --kubeconfig=\"${CERT_DIR}/admin.kubeconfig\" --namespace=kube-system create -f kubedns-svc.yaml <del> echo \"Kube-dns rc and service successfully deployed.\" </del> <ins> echo \"Kube-dns deployment and service successfully deployed.\" </ins> rm  kubedns-deployment.yaml kubedns-svc.yaml fi }", "positive_passages": [{"docid": "doc-en-kubernetes-970debf69dc4e7e663c051298279ebf93b58654f6c393d8683796c73cb4f1c74", "text": "Kubernetes version (use ): Environment: Cloud provider or hardware configuration: Vagrant OS (e.g. from /etc/os-release): CoreOS Kernel (e.g. ):Install tools: Vagrant & Others: What happened: What you expected to happen: Success How to reproduce it (as minimally and precisely as possible): Followed instructions at Tried to run Received: Anything else do we need to know: From googling, it seems several of the fields in the config are for when using OpenShift origin. But creating the replication controller is a prerequisite to launching OpenShift Origin. Chicken & egg problem.", "commid": "kubernetes_issue_39575", "tokennum": 138}], "negative_passages": []}
{"query_id": "q-en-kubernetes-269058c37b6990225f1fe87bc33385cdba6c668210960187cc3c0b9de435d0dc", "query": "} } } <ins> func TestApiserverMetricsPods(t *testing.T) { callOrDie := func(_ interface{}, err error) { if err != nil { t.Fatalf(\"unexpected error: %v\", err) } } makePod := func(labelValue string) *v1.Pod { return &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name:   \"foo\", Labels: map[string]string{\"foo\": labelValue}, }, Spec: v1.PodSpec{ Containers: []v1.Container{ { Name:  \"container\", Image: \"image\", }, }, }, } } _, server, closeFn := framework.RunAMaster(framework.NewMasterConfig()) defer closeFn() client, err := clientset.NewForConfig(&restclient.Config{Host: server.URL, QPS: -1}) if err != nil { t.Fatalf(\"Error in create clientset: %v\", err) } c := client.CoreV1().Pods(metav1.NamespaceDefault) for _, tc := range []struct { name     string executor func() want string }{ { name: \"create pod\", executor: func() { callOrDie(c.Create(context.TODO(), makePod(\"foo\"), metav1.CreateOptions{})) }, want: `apiserver_request_total{code=\"201\", component=\"apiserver\", contentType=\"application/json\", dry_run=\"\", group=\"\", resource=\"pods\", scope=\"resource\", subresource=\"\", verb=\"POST\", version=\"v1\"}`, }, { name: \"update pod\", executor: func() { callOrDie(c.Update(context.TODO(), makePod(\"bar\"), metav1.UpdateOptions{})) }, want: `apiserver_request_total{code=\"200\", component=\"apiserver\", contentType=\"application/json\", dry_run=\"\", group=\"\", resource=\"pods\", scope=\"resource\", subresource=\"\", verb=\"PUT\", version=\"v1\"}`, }, { name: \"update pod status\", executor: func() { callOrDie(c.UpdateStatus(context.TODO(), makePod(\"bar\"), metav1.UpdateOptions{})) }, want: `apiserver_request_total{code=\"200\", component=\"apiserver\", contentType=\"application/json\", dry_run=\"\", group=\"\", resource=\"pods\", scope=\"resource\", subresource=\"status\", verb=\"PUT\", version=\"v1\"}`, }, { name: \"get pod\", executor: func() { callOrDie(c.Get(context.TODO(), \"foo\", metav1.GetOptions{})) }, want: `apiserver_request_total{code=\"200\", component=\"apiserver\", contentType=\"application/json\", dry_run=\"\", group=\"\", resource=\"pods\", scope=\"resource\", subresource=\"\", verb=\"GET\", version=\"v1\"}`, }, { name: \"list pod\", executor: func() { callOrDie(c.List(context.TODO(), metav1.ListOptions{})) }, want: `apiserver_request_total{code=\"200\", component=\"apiserver\", contentType=\"application/json\", dry_run=\"\", group=\"\", resource=\"pods\", scope=\"namespace\", subresource=\"\", verb=\"LIST\", version=\"v1\"}`, }, { name: \"delete pod\", executor: func() { callOrDie(nil, c.Delete(context.TODO(), \"foo\", metav1.DeleteOptions{})) }, want: `apiserver_request_total{code=\"200\", component=\"apiserver\", contentType=\"application/json\", dry_run=\"\", group=\"\", resource=\"pods\", scope=\"resource\", subresource=\"\", verb=\"DELETE\", version=\"v1\"}`, }, } { t.Run(tc.name, func(t *testing.T) { baseSamples, err := getSamples(server) if err != nil { t.Fatal(err) } tc.executor() updatedSamples, err := getSamples(server) if err != nil { t.Fatal(err) } newSamples := diffMetrics(updatedSamples, baseSamples) found := false for _, sample := range newSamples { if sample.Metric.String() == tc.want { found = true break } } if !found { t.Fatalf(\"could not find metric for API call >%s< among samples >%+v<\", tc.name, newSamples) } }) } } func TestApiserverMetricsNamespaces(t *testing.T) { callOrDie := func(_ interface{}, err error) { if err != nil { t.Fatalf(\"unexpected error: %v\", err) } } makeNamespace := func(labelValue string) *v1.Namespace { return &v1.Namespace{ ObjectMeta: metav1.ObjectMeta{ Name:   \"foo\", Labels: map[string]string{\"foo\": labelValue}, }, } } _, server, closeFn := framework.RunAMaster(framework.NewMasterConfig()) defer closeFn() client, err := clientset.NewForConfig(&restclient.Config{Host: server.URL, QPS: -1}) if err != nil { t.Fatalf(\"Error in create clientset: %v\", err) } c := client.CoreV1().Namespaces() for _, tc := range []struct { name     string executor func() want string }{ { name: \"create namespace\", executor: func() { callOrDie(c.Create(context.TODO(), makeNamespace(\"foo\"), metav1.CreateOptions{})) }, want: `apiserver_request_total{code=\"201\", component=\"apiserver\", contentType=\"application/json\", dry_run=\"\", group=\"\", resource=\"namespaces\", scope=\"resource\", subresource=\"\", verb=\"POST\", version=\"v1\"}`, }, { name: \"update namespace\", executor: func() { callOrDie(c.Update(context.TODO(), makeNamespace(\"bar\"), metav1.UpdateOptions{})) }, want: `apiserver_request_total{code=\"200\", component=\"apiserver\", contentType=\"application/json\", dry_run=\"\", group=\"\", resource=\"namespaces\", scope=\"resource\", subresource=\"\", verb=\"PUT\", version=\"v1\"}`, }, { name: \"update namespace status\", executor: func() { callOrDie(c.UpdateStatus(context.TODO(), makeNamespace(\"bar\"), metav1.UpdateOptions{})) }, want: `apiserver_request_total{code=\"200\", component=\"apiserver\", contentType=\"application/json\", dry_run=\"\", group=\"\", resource=\"namespaces\", scope=\"resource\", subresource=\"status\", verb=\"PUT\", version=\"v1\"}`, }, { name: \"get namespace\", executor: func() { callOrDie(c.Get(context.TODO(), \"foo\", metav1.GetOptions{})) }, want: `apiserver_request_total{code=\"200\", component=\"apiserver\", contentType=\"application/json\", dry_run=\"\", group=\"\", resource=\"namespaces\", scope=\"resource\", subresource=\"\", verb=\"GET\", version=\"v1\"}`, }, { name: \"list namespace\", executor: func() { callOrDie(c.List(context.TODO(), metav1.ListOptions{})) }, want: `apiserver_request_total{code=\"200\", component=\"apiserver\", contentType=\"application/json\", dry_run=\"\", group=\"\", resource=\"namespaces\", scope=\"cluster\", subresource=\"\", verb=\"LIST\", version=\"v1\"}`, }, { name: \"delete namespace\", executor: func() { callOrDie(nil, c.Delete(context.TODO(), \"foo\", metav1.DeleteOptions{})) }, want: `apiserver_request_total{code=\"200\", component=\"apiserver\", contentType=\"application/json\", dry_run=\"\", group=\"\", resource=\"namespaces\", scope=\"resource\", subresource=\"\", verb=\"DELETE\", version=\"v1\"}`, }, } { t.Run(tc.name, func(t *testing.T) { baseSamples, err := getSamples(server) if err != nil { t.Fatal(err) } tc.executor() updatedSamples, err := getSamples(server) if err != nil { t.Fatal(err) } newSamples := diffMetrics(updatedSamples, baseSamples) found := false for _, sample := range newSamples { if sample.Metric.String() == tc.want { found = true break } } if !found { t.Fatalf(\"could not find metric for API call >%s< among samples >%+v<\", tc.name, newSamples) } }) } } func getSamples(s *httptest.Server) (model.Samples, error) { metrics, err := scrapeMetrics(s) if err != nil { return nil, err } samples, ok := metrics[\"apiserver_request_total\"] if !ok { return nil, errors.New(\"apiserver_request_total doesn't exist\") } return samples, nil } func diffMetrics(newSamples model.Samples, oldSamples model.Samples) model.Samples { samplesDiff := model.Samples{} for _, sample := range newSamples { if !sampleExistsInSamples(sample, oldSamples) { samplesDiff = append(samplesDiff, sample) } } return samplesDiff } func sampleExistsInSamples(s *model.Sample, samples model.Samples) bool { for _, sample := range samples { if sample.Equal(s) { return true } } return false } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-0ebc3a18530206d54bf966306c4d4d56c4fb7ca61cedeffe6a0cab2bf1fe76ea", "text": "In we discovered a bug where kube-apiserver metrics were being incorrectly reported (GET vs LIST problem). In this was addressed together with test exercising that proper metrics are exposed. However, this test isn't ideal because if params wouldn't be swapped, it wouldn't catch them. We should ideally develop a lower-level unit test for mapping url paths to exact values of labels/parameters. /sig apimachinery\nThe label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : In we discovered a bug where kube-apiserver metrics were being incorrectly reported (GET vs LIST problem). In this was addressed together with test exercising that proper metrics are exposed. We should ideally develop a lower-level unit test for mapping url paths to exact values of labels/parameters. 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\n/sig api-machinery\nare you planning on sending a fix for this one too? Thanks!\nNot very soon - if someone else could help with it, it would be great.\n/assign\n/triage accepted\ncc", "commid": "kubernetes_issue_95636", "tokennum": 258}], "negative_passages": []}
{"query_id": "q-en-kubernetes-269168ce5e2f88bbc09eb63ad5741a655840fd0a311ed73523b5bf5aea3a42ef", "query": "manager.nodeStore.Add(c.oldNode) c.ds.Spec.UpdateStrategy = *strategy manager.dsStore.Add(c.ds) <del> syncAndValidateDaemonSets(t, manager, c.ds, podControl, 0, 0, 0) </del> <ins> expectedEvents := 0 if c.expectedEventsFunc != nil { expectedEvents = c.expectedEventsFunc(strategy.Type) } syncAndValidateDaemonSets(t, manager, c.ds, podControl, 0, 0, expectedEvents) </ins> manager.enqueueDaemonSet = func(ds *apps.DaemonSet) { if ds.Name == \"ds\" {", "positive_passages": [{"docid": "doc-en-kubernetes-56dc15a3fe2161c6cf8927a51d2d0dce03fea80f01ef1e0345dcc3ca50d1379f", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: a cluster, And node1 with resource 1 DaemonSet, request resource 4 run , There is no pod created. resource to the node: run , There is still no pod created. What you expected to happen: In step 5, There is one pod created. How to reproduce it (as minimally and precisely as possible): see above description Anything else we need to know?: Environment: Kubernetes version (use ):1.10.5 Cloud provider or hardware configuration: OS (e.g. from /etc/os-release):CentOS7 Kernel (e.g. ): Install tools: Others: /sig app\nxref\nThanks! is not work here! Because: DaemonSetsController didn't watch the changes.(we use to updateNode.) we restart kubelet, The DaemonSetsController watch the changes, but it seems that the node info is not updated, and still failed to create pod:\nI found it is a bug here, ignore the changes. I made a fix , PTAL! Thanks!\nAny workarounds for old cluster versions? Up: looks like in my case helped but after some delay.\n, which version of k8s are you using? If it's sunset, you have to merge the pr yourself :). I think restart kubelet trigger delete/add to make sure it sync .\nSorry, I didn't say\nI think we still support 1.12 for now :) let's cherry pick it if not and wait for next 1.12 release.", "commid": "kubernetes_issue_67225", "tokennum": 342}], "negative_passages": []}
{"query_id": "q-en-kubernetes-26b6104f95b1d1c3a782bf95a1cf63b24de84e36a6e4fb51e504c9b3b55acce0", "query": "return fmt.Errorf(\"size of file %s is %d, expected %d\", fpath, size, expectSize) } <del> By(\"verifying file content\") // use `grep ... -f` rather than the expected content in a variable to reduce logging rtnstr, err = podExec(pod, fmt.Sprintf(\"grep -c -m1 -f %s %s\", dd_input, fpath)) </del> <ins> By(\"verifying file hash\") rtnstr, err = podExec(pod, fmt.Sprintf(\"md5sum %s | cut -d' ' -f1\", fpath)) </ins> if err != nil { <del> return fmt.Errorf(\"unable to test file content via `grep %s`: %v\", fpath, err) </del> <ins> return fmt.Errorf(\"unable to test file hash via `md5sum %s`: %v\", fpath, err) </ins> } <del> foundCnt, err := strconv.Atoi(strings.TrimSuffix(rtnstr, \"n\")) if err != nil { return fmt.Errorf(\"unable to convert string %q to int: %v\", rtnstr, err) </del> <ins> actualHash := strings.TrimSuffix(rtnstr, \"n\") expectedHash, ok := md5hashes[expectSize] if !ok { return fmt.Errorf(\"File hash is unknown for file size %d. Was a new file size added to the test suite?\", expectSize) </ins> } <del> if foundCnt == 0 { rtnstr, err = podExec(pod, fmt.Sprintf(\"cat %s\", dd_input)) if err != nil || len(rtnstr) == 0 { return fmt.Errorf(\"string not found in file %s and unable to read dd's input file %s: %v\", fpath, dd_input, err) } return fmt.Errorf(\"string %q not found in file %s\", rtnstr, fpath) </del> <ins> if actualHash != expectedHash { return fmt.Errorf(\"MD5 hash is incorrect for file %s with size %d. Expected: `%s`; Actual: `%s`\", fpath, expectSize, expectedHash, actualHash) </ins> } return nil", "positive_passages": [{"docid": "doc-en-kubernetes-540712d0b27ee7f52d7d02bd3719013304c1ce42c6b5d8b93c3ee3671a9c1c7c", "text": "The \"Volume plugin streaming [Slow] NFS should write files of various sizes, verify size, validate content\" e2e test is failing on our 2k-node gce clusters (https://k8s-) with the following error: cc\nCould you take a look into it or reassign as apt? This is part of the correctness suite and large cluster tests are release-blocking.\n/assign\nis this run using the kubemark environment? I'll also take a look. It could be that the commands this test needs to execute may not work with kubemark. /assign\ncc\nNo, this is not kubemark. This is on a real 2000-node cluster.\nAlso all other volume-related e2e tests are passing, except this one.\nLooking at the log I see that the nfs test fails trying to verify the test file's content. The test exec's into the nfs client pod and executes: The return code from above is 127. The test then deletes the nfs client pod calling which works. The nfs-server pod is deleted in the AfterEach. For some reason the reported error is 137 but the returned err 127. The same command is exec'd for all of the tested storage plugins so not sure why it's failing just for nfs. Error 127 might be \"command not found\".\nThe other strange thing is that it's only failing in this suite and not the others.\nWhen I look at the kubelet log, I see the exec command coming through: I also see these suspicious kubelet soon afterwards: So I think the grep command is causing the node to run out of memory and get evicted. I think we can fix this either by: Making the grep command more memory efficient. I'm guessing it's reading the whole file into memory or, Make this test Serial so that it doesn't run in parallel with other pods, since it consumes a lot of memory.\nAn unrelated issue, is that the node allocatable feature didn't actually evict the pod. Instead this pod got a system OOM kill. /cc\nrelated to the memcg notifications, not node allocatable. Thanks!\nany theories why we see this only for the nfs-io tests, and not the glusterfs-io test for instance?\nthe gluster test didn't run on this in this suite.", "commid": "kubernetes_issue_51717", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-26b6104f95b1d1c3a782bf95a1cf63b24de84e36a6e4fb51e504c9b3b55acce0", "query": "return fmt.Errorf(\"size of file %s is %d, expected %d\", fpath, size, expectSize) } <del> By(\"verifying file content\") // use `grep ... -f` rather than the expected content in a variable to reduce logging rtnstr, err = podExec(pod, fmt.Sprintf(\"grep -c -m1 -f %s %s\", dd_input, fpath)) </del> <ins> By(\"verifying file hash\") rtnstr, err = podExec(pod, fmt.Sprintf(\"md5sum %s | cut -d' ' -f1\", fpath)) </ins> if err != nil { <del> return fmt.Errorf(\"unable to test file content via `grep %s`: %v\", fpath, err) </del> <ins> return fmt.Errorf(\"unable to test file hash via `md5sum %s`: %v\", fpath, err) </ins> } <del> foundCnt, err := strconv.Atoi(strings.TrimSuffix(rtnstr, \"n\")) if err != nil { return fmt.Errorf(\"unable to convert string %q to int: %v\", rtnstr, err) </del> <ins> actualHash := strings.TrimSuffix(rtnstr, \"n\") expectedHash, ok := md5hashes[expectSize] if !ok { return fmt.Errorf(\"File hash is unknown for file size %d. Was a new file size added to the test suite?\", expectSize) </ins> } <del> if foundCnt == 0 { rtnstr, err = podExec(pod, fmt.Sprintf(\"cat %s\", dd_input)) if err != nil || len(rtnstr) == 0 { return fmt.Errorf(\"string not found in file %s and unable to read dd's input file %s: %v\", fpath, dd_input, err) } return fmt.Errorf(\"string %q not found in file %s\", rtnstr, fpath) </del> <ins> if actualHash != expectedHash { return fmt.Errorf(\"MD5 hash is incorrect for file %s with size %d. Expected: `%s`; Actual: `%s`\", fpath, expectSize, expectedHash, actualHash) </ins> } return nil", "positive_passages": [{"docid": "doc-en-kubernetes-fd4ca8cfd935058701597731533334687f2913bf0b9d409a83f3ac801f0182e1", "text": "I'm suspecting that the reason why we didn't see a problem with this test on other suites is that the load could be higher here. I've asked to see if we can reduce the memory usage of the grep call.\npointed out that there are no newlines in the generated file, so when grep is called it could buffer the entire file in memory. Adding a newline at the end of the dd input file should do it.\n/priority critical-urgent\n[MILESTONENOTIFIER] Milestone Labels Complete Issue label settings: sig/scalability sig/storage: Issue will be escalated to these SIGs if needed. priority/critical-urgent: Never automatically move out of a release milestone; continually escalate to contributor and SIG through all available channels. kind/bug: Fixes a bug discovered during the current release. <detailsAdditional instructions available <a href=\"\"here</a</details\nIt seems like even if the generated file is broken up by newlines, grep could still use on the order of hundreds of MB of memory for a 100MiB file (even with the -m1 and -F options). We could check the file line by line, but it would take a long time. A better solution would be to check the MD5 file hash. It's fast and uses little memory. The expected hashes will be hard-coded into the test, and if different file sizes are in the future, a hash needs to be computed and as well.\nThanks a lot for fixing this!\nRef", "commid": "kubernetes_issue_51717", "tokennum": 322}], "negative_passages": []}
{"query_id": "q-en-kubernetes-26b846990403b97c9c21025d0e36fa3de226d0eb0bff364fb6ec147e1409f6ca", "query": "\"crypto/x509\" \"crypto/x509/pkix\" \"fmt\" <ins> \"net\" </ins> \"strings\" \"testing\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-8be37f8ebf3b929ba13e3d88ac8f62b2b24f9ed008212f39c0aaa7e2ec850c18", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: I'm testing the new option in kubernetes 1.12 and it seems that kubelet always requests the signing of a new CSR and tries to rotate the certificates when it is started. This is happening even though there's a valid (brand new) certificate on disk issued by kube-controller-manager. From what I can tell, this is happening because kubelet implements and is set after a successful certificate rotation, but is never persisted to disk. If kubelet is restarted, then the last requested CSR is nil. What you expected to happen: Ideally, kubelet should only request the signing of a new CSR if it doesn't already have a serving certificate or it's about to expire. How to reproduce it (as minimally and precisely as possible): Restart a kubelet instance that had it's serving certificate issued by kube-controller-manager Check and see that it requested the signing of a new CSR Anything else we need to know?: kubelet is being run with . , , and are all omitted to use the default values. The TLS bootstrapping for client certificates is currently not being used--just the bootstrapping for serving certificates. Environment: Kubernetes version: v1.12.0 - built from source at the tag () Cloud provider or hardware configuration: Bare metal OS: CentOS 7.5.1804 Kernel: Install tools: Custom RPMs built from this git repo with no additional patches Others:\n/sig node\n/sig auth\nNot sure if this is the ideal fix, but I've patched it so that it compares the current CSR template to the last requested template only if it doesn't already match the current cert.\ncc\nthanks for the proposed fix. I think it looks good. Could you send a PR? We should also remove entirely and only look at current cert and template. does that sound reasonable?\nSure thing, I'd be happy to do that. EDIT: I will submit a PR after approval from my employer.\nI think that's probably ok, as long as it checks everything we include in the template and we consider a certificate missing anything we request to be cause for re-requesting another cert (an issuer couldn't choose to issue a cert that drops some SANs and us not request another cert) left some comments in\nThis regression is a frequent flyer.", "commid": "kubernetes_issue_69471", "tokennum": 523}], "negative_passages": []}
{"query_id": "q-en-kubernetes-26b846990403b97c9c21025d0e36fa3de226d0eb0bff364fb6ec147e1409f6ca", "query": "\"crypto/x509\" \"crypto/x509/pkix\" \"fmt\" <ins> \"net\" </ins> \"strings\" \"testing\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-1b55ad000b296f12b046608a2d187d8503e900f5b67dbcaa87fc7ef8e9366d19", "text": "I'd love to see an integration test that would catch this (but that shouldn't block a fix).\nThanks for the comments! Now that I have the CLA signed, I'll address those and submit a PR.\nJust submitted the PR:", "commid": "kubernetes_issue_69471", "tokennum": 53}], "negative_passages": []}
{"query_id": "q-en-kubernetes-26eb553f2c46386aebc767f178dc3c1ed2dc025ecacf97f8b72a938ec63151d0", "query": "unmanagedNodes:         sets.NewString(), routeCIDRs:             map[string]string{}, resourceRequestBackoff: resourceRequestBackoff, <del> DisksClient:                     newAzDisksClient(azClientConfig), SnapshotsClient:                 newSnapshotsClient(azClientConfig), RoutesClient:                    newAzRoutesClient(azClientConfig), SubnetsClient:                   newAzSubnetsClient(azClientConfig), InterfacesClient:                newAzInterfacesClient(azClientConfig), RouteTablesClient:               newAzRouteTablesClient(azClientConfig), LoadBalancerClient:              newAzLoadBalancersClient(azClientConfig), SecurityGroupsClient:            newAzSecurityGroupsClient(azClientConfig), StorageAccountClient:            newAzStorageAccountClient(azClientConfig), VirtualMachinesClient:           newAzVirtualMachinesClient(azClientConfig), PublicIPAddressesClient:         newAzPublicIPAddressesClient(azClientConfig), VirtualMachineSizesClient:       newAzVirtualMachineSizesClient(azClientConfig), VirtualMachineScaleSetsClient:   newAzVirtualMachineScaleSetsClient(azClientConfig), VirtualMachineScaleSetVMsClient: newAzVirtualMachineScaleSetVMsClient(azClientConfig), FileClient:                      &azureFileClient{env: *env}, </del> } az.metadata, err = NewInstanceMetadataService(metadataURL) if err != nil { return nil, err } <ins> // No credentials provided, InstanceMetadataService would be used for getting Azure resources. // Note that this only applies to Kubelet, controller-manager should configure credentials for managing Azure resources. if servicePrincipalToken == nil { return &az, nil } // Initialize Azure clients. azClientConfig := &azClientConfig{ subscriptionID:                 config.SubscriptionID, resourceManagerEndpoint:        env.ResourceManagerEndpoint, servicePrincipalToken:          servicePrincipalToken, rateLimiterReader:              operationPollRateLimiter, rateLimiterWriter:              operationPollRateLimiterWrite, CloudProviderBackoffRetries:    config.CloudProviderBackoffRetries, CloudProviderBackoffDuration:   config.CloudProviderBackoffDuration, ShouldOmitCloudProviderBackoff: config.shouldOmitCloudProviderBackoff(), } az.DisksClient = newAzDisksClient(azClientConfig) az.SnapshotsClient = newSnapshotsClient(azClientConfig) az.RoutesClient = newAzRoutesClient(azClientConfig) az.SubnetsClient = newAzSubnetsClient(azClientConfig) az.InterfacesClient = newAzInterfacesClient(azClientConfig) az.RouteTablesClient = newAzRouteTablesClient(azClientConfig) az.LoadBalancerClient = newAzLoadBalancersClient(azClientConfig) az.SecurityGroupsClient = newAzSecurityGroupsClient(azClientConfig) az.StorageAccountClient = newAzStorageAccountClient(azClientConfig) az.VirtualMachinesClient = newAzVirtualMachinesClient(azClientConfig) az.PublicIPAddressesClient = newAzPublicIPAddressesClient(azClientConfig) az.VirtualMachineSizesClient = newAzVirtualMachineSizesClient(azClientConfig) az.VirtualMachineScaleSetsClient = newAzVirtualMachineScaleSetsClient(azClientConfig) az.VirtualMachineScaleSetVMsClient = newAzVirtualMachineScaleSetVMsClient(azClientConfig) az.FileClient = &azureFileClient{env: *env} </ins> if az.MaximumLoadBalancerRuleCount == 0 { az.MaximumLoadBalancerRuleCount = maximumLoadBalancerRuleCount }", "positive_passages": [{"docid": "doc-en-kubernetes-effe9bff1df2586252b385cbf4a7cacd04cb77f4739ff9c987e63818f9dc1c82", "text": "Currently there is no way to run without any identity (be it service principal or E/MSI). In reality code running on a worker node can use via - and only via - without the need to access ARM. Here is the proposed change a new mode authN = this mode, is basically telling the cloud provider to work any identity, this means only IMDS calls is allowed. This mode can be detected from if no SPN set and both MSI settings are set to . to use a config map within the cluster. This config map can be loaded on the cluster statically. or created - if not existent - in that then only is used in The net new result of the above is users bootstrapping clusters can configure the worker node to use without any identity on said worker nodes.\n/sig azure These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by \u200d\nIn-tree AzureDisk volume plugin is also depending on Azure credential to fetch lun id. we should figure out how to solve it without credential\nfetch disk lun id is also a dependency in kubelet code now, after my investigation, it could be removed on Linux node, while it cannot be removed on Windows node, need to change the k/k upstream code, there is a discussion on going here: , let' wait for the discussion result.\nFor Linux: 1- use IMDS my understanding is new api versions will have the disk/lun pairs. 2- don't use arm for the return of is the second parameter passed to . For Windows: I don't understand the dep on ARM for this. The above still apply, we just need to find a way to encode the value as ut return from that allow us to find the disk by on a windows machine. might be a good source for this. Ideally speaking. The value should be the same. But i will leave it for you to decide.\ncould be a good idea since currently it's a LUN num returned by Attach() and then it could be changed to the windows disk num, I will make the code change on v1.15 later, thanks for discussion.\nUpdate: PR would remove the VM API calls when getting the LUN number for AzureDisk.", "commid": "kubernetes_issue_77309", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-271d157e92fb45dda5c0749760992b06ad3d10e576a755bda34ebb5e38455481", "query": "{utiliptables.TableNAT, kubePostroutingChain, utiliptables.ChainPostrouting, \"kubernetes postrouting rules\", nil}, } <ins> var iptablesEnsureChains = []struct { table utiliptables.Table chain utiliptables.Chain }{ {utiliptables.TableNAT, KubeMarkDropChain}, } </ins> var iptablesCleanupOnlyChains = []iptablesJumpChain{} // CleanupLeftovers removes all iptables rules and chains created by the Proxier", "positive_passages": [{"docid": "doc-en-kubernetes-6cbf7dcb5e6486cb532532a59cda0ac4f93a00ec9c96bc20136b3a20d89cc61b", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: ci-kubernetes-e2e-gci-gce-ipvs Which test(s) are failing: [sig-network] Services should only allow access from service loadbalancer source ranges [Slow] Testgrid link: https://k8s- Reason for failure: Anything else we need to know: The test is failing consistently, however, there is also test that is failing a lot but not always, may it be related?\n/sig-network /area ipvs /cc /help wanted\n/sig network\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/assign\n/remove-triage unresolved\nHi, , turnout this is because mark drop rule in be deleted, I raied a pr to fix this issue, PTAL. : )\n/close as duplicate of\nClosing this issue. <detailsIn response to : /close as duplicate of 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\n/reopen this was affecting ipvs only before , let's keep it open until we verify is not failing anymore\nReopened this issue. <detailsIn response to : /reopen this was affecting ipvs only before , let's keep it open until we verify is not failing anymore 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\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign Ok I tested this out with kind in ipvs-mode with metallb. In iptables mode I had zero failures but ipvs does not pass at all during the timeout window. This is likely due to", "commid": "kubernetes_issue_94356", "tokennum": 488}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2738a0c35769a59828729142b5bb6eb9f9c2ee00fb2fc08dae91621e2cf5b50d", "query": "# This file creates a standard build environment for building cross # platform go binary for the architecture kubernetes cares about. <del> FROM golang:1.8.3 </del> <ins> FROM golang:1.9.1 </ins> ENV GOARM 7 ENV KUBE_DYNAMIC_CROSSPLATFORMS ", "positive_passages": [{"docid": "doc-en-kubernetes-1b1e05089c93c6eb59b848626d58302483d33d2f2e5531ac5b621da204277493", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind feature This is a followup on , but for Go 1.9 We should do the same kind of testing now to possibly catch bugs in either Go or Kubernetes when doing this kind of dependency version bump. Ideally we'd have automated tests against Go tip (), but we don't have that at the moment, so we have to do it kind of manually. We should also decide which k8s version we should target. k8s v1.8 or v1.9? What Go versions have been used so far? Kubernetes v1.7.0 - go1.8.3 Kubernetes v1.6.0 - go1.7.5 Kubernetes v1.5.0 - go1.7.4 Kubernetes v1.4.0 - go1.6.3 Kubernetes v1.3.0 - go1.6.2 Kubernetes v1.2.0 - go1.4.2 Seems like the trend has been to stay on the same Go version for two releases and then bump. That'd mean we'd switch to Go1.9 in k8s v1.9 Everyone happy with that? Or is there any reason for us to go start using go1.9 in k8s v1.8? In any case, we should indeed start testing go1.9 out now... cc\nLet me know if you find any bugs\nFWIW pretty tight to code-freeze I would prefer punting out a cycle fwiw.\nI don't think we're that close to code freeze given that we have 5 (of 8) weeks left in this coding cycle But I'm happy to defer this to v1.9 if others think that. I guess the main reason for a bump would be scalability goals, but I'm not sure we have the need to expand above 5000 (and that Go would be the bottleneck in that case) for v1.8\nmade the Go benchmarks 9% faster with 15% larger binaries. I'm interested to see how that affects our numbers.\nmid-stack inlining was not included in Go 1.9. It made the compiler too slow. It's being targeted to Go 1.10 now instead, after some compiler optimization work.\nOh, thanks for the correction!", "commid": "kubernetes_issue_49484", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2738a0c35769a59828729142b5bb6eb9f9c2ee00fb2fc08dae91621e2cf5b50d", "query": "# This file creates a standard build environment for building cross # platform go binary for the architecture kubernetes cares about. <del> FROM golang:1.8.3 </del> <ins> FROM golang:1.9.1 </ins> ENV GOARM 7 ENV KUBE_DYNAMIC_CROSSPLATFORMS ", "positive_passages": [{"docid": "doc-en-kubernetes-018b01245292fe1977b7eec8bea53846947ed737ea149d849054911d63924f58", "text": "Regardless, we need to run the scalability tests against the RC so we can report issues earlier-- the last upgrade was particularly painful because of an HTTP regression that we caught way too late.\nyeah. I filed for that now\nyeah, my recollection is that the Go releases usually occur too late in our release cadence and end up getting bumped to the next Kubernetes release. (Also we inevitably find something wrong, though testing RCs would help with that. Though I'm not sure anyone has cycles to test RCs and fix all of the issues that do come up.)\nBased on our current time frame, it looks like go1.9 support will have to slip to k8s 1.9. is open to dig into and start things testing, but there's a number of things that have to move.. I'll try to document those this time around to help with future go version bumps. So far: bazel build rules needed to be updated to support go1.9 () bazel version possibly needs to be updated? some of our custom bazel rules broke\nWhen done, we should update this:\n/priority important-soon\nUpdating the dependency is blocked pending bazel 0.6.0 - .\nCan we upgrade to 0.6.0 now? Does bazel 0.6.0 have multiarch support btw?\nWe can't update to depend on bazel 0.6.0+ until we can figure out how to support different versions of the bazelbuild and kubekins-e2e images in PR jobs in prow based on what branch is being tested. cc\nNoting that we're working on branching jobs, is testing one option here:\n[MILESTONENOTIFIER] Milestone Issue Current <details open<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts. : New functionality.", "commid": "kubernetes_issue_49484", "tokennum": 416}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2738a0c35769a59828729142b5bb6eb9f9c2ee00fb2fc08dae91621e2cf5b50d", "query": "# This file creates a standard build environment for building cross # platform go binary for the architecture kubernetes cares about. <del> FROM golang:1.8.3 </del> <ins> FROM golang:1.9.1 </ins> ENV GOARM 7 ENV KUBE_DYNAMIC_CROSSPLATFORMS ", "positive_passages": [{"docid": "doc-en-kubernetes-69273b286facac9ab246a3deb71fa6e24d55618a503d411a1618742e8a027c28", "text": "</details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details\nI approved this for v1.9, this is something we definitely want in order to keep up with Go (and for improved performance)\nwe're starting to use the forked images now /cc this should be more feasible very soon Edit: test-infra jobs have also been using bazel 0.6 (now 0.6.1) / a recent rules_go to soak things a bit\nWe've identified a failing test as a result of the WIP PR to upgrade the codebase to go1.9: The admission webhook test fails with certificate errors under go1.9.1, but runs successfully under go1.8.3. cc: who wanted to be alerted to potential bugs\n- please see for a possible fix", "commid": "kubernetes_issue_49484", "tokennum": 212}], "negative_passages": []}
{"query_id": "q-en-kubernetes-27512f094f5379a4fdcac193ebff36191a45814adc033f92320ff7907b950c9d", "query": "\"//staging/src/k8s.io/client-go/tools/leaderelection:go_default_library\", \"//staging/src/k8s.io/component-base/cli/flag:go_default_library\", \"//staging/src/k8s.io/component-base/cli/globalflag:go_default_library\", <ins> \"//staging/src/k8s.io/component-base/logs:go_default_library\", </ins> \"//staging/src/k8s.io/component-base/metrics/legacyregistry:go_default_library\", \"//staging/src/k8s.io/component-base/version:go_default_library\", \"//staging/src/k8s.io/component-base/version/verflag:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-1ae4374d89f67ace7ae0a669d00ed1569d20a542da5564faf73570670010978e", "text": "What would you like to be : Support dynamically set log level for kube-scheduler, is blocked on node controller approval, but we can move forward with a scheduler only change. /sig scheduling\n/help\n/assign /remove-help\ndo you have a PR for this one?\nI submitted the PR.", "commid": "kubernetes_issue_83783", "tokennum": 65}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2780e1b99760e095836500cffd9a5e3cfc51e442d1226f0e2e92f2ae95347489", "query": "\"//pkg/kubelet/types:go_default_library\", \"//pkg/volume:go_default_library\", \"//vendor/github.com/golang/glog:go_default_library\", <del> \"//vendor/github.com/golang/protobuf/proto:go_default_library\", </del> \"//vendor/github.com/google/cadvisor/fs:go_default_library\", \"//vendor/github.com/google/cadvisor/info/v1:go_default_library\", \"//vendor/github.com/google/cadvisor/info/v2:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-739981494c57aaeb7141fd974134e4440eb950badca5a937fa4552d94ec1af8a", "text": "In , we merged a work around for heapster panic We should get rid of the work around after heapster version is updated. /cc /cc\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close", "commid": "kubernetes_issue_55280", "tokennum": 224}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2798527047d5d3dab13151744fbec19f87eddda3040636a2b91178e744705aa2", "query": "// NewNonInteractiveDeferredLoadingClientConfig creates a ConfigClientClientConfig using the passed context name func NewNonInteractiveDeferredLoadingClientConfig(loader ClientConfigLoader, overrides *ConfigOverrides) ClientConfig { <del> return &DeferredLoadingClientConfig{loader: loader, overrides: overrides, icc: inClusterClientConfig{}} </del> <ins> return &DeferredLoadingClientConfig{loader: loader, overrides: overrides, icc: &inClusterClientConfig{overrides: overrides}} </ins> } // NewInteractiveDeferredLoadingClientConfig creates a ConfigClientClientConfig using the passed context name and the fallback auth reader func NewInteractiveDeferredLoadingClientConfig(loader ClientConfigLoader, overrides *ConfigOverrides, fallbackReader io.Reader) ClientConfig { <del> return &DeferredLoadingClientConfig{loader: loader, overrides: overrides, icc: inClusterClientConfig{}, fallbackReader: fallbackReader} </del> <ins> return &DeferredLoadingClientConfig{loader: loader, overrides: overrides, icc: &inClusterClientConfig{overrides: overrides}, fallbackReader: fallbackReader} </ins> } func (config *DeferredLoadingClientConfig) createClientConfig() (ClientConfig, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-4e19a56e8ccacbab4546f622baecdb0b8ef30250430c55f8bcdc4de99b100cd2", "text": "Found in openshift, but I'm pretty sure the codepaths are the same. That means the token is getting ignored and in-cluster config is being used in preference to flags.\nIs a similar issue?\nYep, kind of regression.\nSigh.\nYes, most likely the same cause.\nI'm on it.\nUnit test :)\nProbably will want to cherrypick this into 1.5.\nWIP in", "commid": "kubernetes_issue_38834", "tokennum": 89}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2798e273503503b616b3b9c2a85774ac4dec6cc31b67f7309f3c7b73395f4bc9", "query": "} func (sched *Scheduler) addPodToSchedulingQueue(obj interface{}) { <del> if err := sched.SchedulingQueue.Add(obj.(*v1.Pod)); err != nil { </del> <ins> pod := obj.(*v1.Pod) klog.V(3).Infof(\"add event for unscheduled pod %s/%s\", pod.Namespace, pod.Name) if err := sched.SchedulingQueue.Add(pod); err != nil { </ins> utilruntime.HandleError(fmt.Errorf(\"unable to queue %T: %v\", obj, err)) } }", "positive_passages": [{"docid": "doc-en-kubernetes-671a12759d851f1b99028bc477360c418e1157a45a2e814ff1c5c1cdd09da36a", "text": "This helps debugging scheduler's behavior, currently we don't have logs that indicate when the scheduler first saw a pod or a node. The log level should be v=3. /sig scheduling /cc\nDo you mean add logging for callbacks in ?\nyes, at least for add and delete events\nSure, I can also give this pr, before tomorrow\n/assign\nWe actually have one v=2 log line for a Node being to the cache's tree: But it's probably good to keep this one.", "commid": "kubernetes_issue_87524", "tokennum": 111}], "negative_passages": []}
{"query_id": "q-en-kubernetes-27f62daa9220fb6b09f9157b2af70de4e0ac599b001569f6a5fbd5f2460cb994", "query": "``` Just call `make` to regenerate the diagrams. <ins> ## Building with Docker If you are on a Mac or your pip install is messed up, you can easily build with docker. ``` make docker ``` The first run will be slow but things should be fast after that. To clean up the docker containers that are created (and other cruft that is left around) you can run `make docker-clean`. If you are using boot2docker and get warnings about clock skew (or if things aren't building for some reason) then you can fix that up with `make fix-clock-skew`. ## Automatically rebuild on file changes If you have the fswatch utility installed, you can have it monitor the file system and automatically rebuild when files have changed.  Just do a `make watch`. </ins>  No newline at end of file", "positive_passages": [{"docid": "doc-en-kubernetes-3871d24647a528f2ff7df25634241fd3cde165662602f0e95a0cba53fe987aee", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug /priority failing-test /area test-infra What happened: job is failing. See https://k8s- https://k8s- https://k8s- https://k8s- What you expected to happen: test should pass\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/assign\nReiterating the mentions to trigger a notification: <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\nI'm guessing that something got messed up in the bazel cache when reverting from 0.5.2 to 0.4.5. I'm not sure how best to fix.\nHow about updating everything to bazel 0.5.3 at once? I know you're trying to do a step-by-step approach to avoid breakages, but I suspect it will be cheaper to just deal with a brief outage while we update? (aka update the bazelbuild image to 0.5.3 and then merge your PR with updated and working BUILD rules?)\nthere's at least one other issue I've discovered with the latest go rules - the binary no longer works, due to changes introduced in that might be arguably better (at least everything still builds?), though it's frustrating that it makes things more broken in a different way.", "commid": "kubernetes_issue_49844", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2858fcd7f036256f16bc0ca221aa77f842520b00f76fa9005fc619b161e2524d", "query": "\"testing\" \"github.com/prometheus/common/model\" v1 \"k8s.io/api/core/v1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/runtime/schema\"", "positive_passages": [{"docid": "doc-en-kubernetes-0ebc3a18530206d54bf966306c4d4d56c4fb7ca61cedeffe6a0cab2bf1fe76ea", "text": "In we discovered a bug where kube-apiserver metrics were being incorrectly reported (GET vs LIST problem). In this was addressed together with test exercising that proper metrics are exposed. However, this test isn't ideal because if params wouldn't be swapped, it wouldn't catch them. We should ideally develop a lower-level unit test for mapping url paths to exact values of labels/parameters. /sig apimachinery\nThe label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : In we discovered a bug where kube-apiserver metrics were being incorrectly reported (GET vs LIST problem). In this was addressed together with test exercising that proper metrics are exposed. We should ideally develop a lower-level unit test for mapping url paths to exact values of labels/parameters. 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\n/sig api-machinery\nare you planning on sending a fix for this one too? Thanks!\nNot very soon - if someone else could help with it, it would be great.\n/assign\n/triage accepted\ncc", "commid": "kubernetes_issue_95636", "tokennum": 258}], "negative_passages": []}
{"query_id": "q-en-kubernetes-285a40825e280c75c8474c12cbf6fad783d418ebd8e5016ca7e0e06fe62706b9", "query": "// Nodeports need SNAT, unless they're local. // ipset call <del> var nodePortSet *IPSet </del> <ins> var ( nodePortSet *IPSet entries     []*utilipset.Entry ) </ins> switch protocol { case \"tcp\": nodePortSet = proxier.ipsetList[kubeNodePortSetTCP] <del> entry = &utilipset.Entry{ </del> <ins> entries = []*utilipset.Entry{{ </ins> // No need to provide ip info Port:     svcInfo.NodePort(), Protocol: protocol, SetType:  utilipset.BitmapPort, <del> } </del> <ins> }} </ins> case \"udp\": nodePortSet = proxier.ipsetList[kubeNodePortSetUDP] <del> entry = &utilipset.Entry{ </del> <ins> entries = []*utilipset.Entry{{ </ins> // No need to provide ip info Port:     svcInfo.NodePort(), Protocol: protocol, SetType:  utilipset.BitmapPort, <del> } </del> <ins> }} </ins> case \"sctp\": nodePortSet = proxier.ipsetList[kubeNodePortSetSCTP] <del> entry = &utilipset.Entry{ IP:       proxier.nodeIP.String(), Port:     svcInfo.NodePort(), Protocol: protocol, SetType:  utilipset.HashIPPort, </del> <ins> // Since hash ip:port is used for SCTP, all the nodeIPs to be used in the SCTP ipset entries. entries = []*utilipset.Entry{} for _, nodeIP := range nodeIPs { entries = append(entries, &utilipset.Entry{ IP:       nodeIP.String(), Port:     svcInfo.NodePort(), Protocol: protocol, SetType:  utilipset.HashIPPort, }) </ins> } default: // It should never hit klog.Errorf(\"Unsupported protocol type: %s\", protocol) } if nodePortSet != nil { <del> if valid := nodePortSet.validateEntry(entry); !valid { klog.Errorf(\"%s\", fmt.Sprintf(EntryInvalidErr, entry, nodePortSet.Name)) </del> <ins> entryInvalidErr := false for _, entry := range entries { if valid := nodePortSet.validateEntry(entry); !valid { klog.Errorf(\"%s\", fmt.Sprintf(EntryInvalidErr, entry, nodePortSet.Name)) entryInvalidErr = true break } nodePortSet.activeEntries.Insert(entry.String()) } if entryInvalidErr { </ins> continue } <del> nodePortSet.activeEntries.Insert(entry.String()) </del> } // Add externaltrafficpolicy=local type nodeport entry", "positive_passages": [{"docid": "doc-en-kubernetes-dd58629e743b6e4eeaad6ce708921acac15734ca4e62ad8f92d2c296b406f940", "text": "What happened: SCTP nodeport service is not working for all IPs present in the node when ipvs is enabled. It is working only for node's InternalIP. What you expected to happen: SCTP nodeport service must work for all ips present in the node when ipvs is enabled. How to reproduce it (as minimally and precisely as possible): Create a kubernetes cluster with at least one node having multiple interfaces with different IPs. Start an SCTP server deployment. Then create a nodeport service for the same. Now try to reach the service using all the IPs present in that node. The service will be accessible only via node's InternalIP not any other IPs. Environment: Kubernetes version: v1.15.2 OS: ubuntu 18.04 Kernel: 4.15.0-54-generic Network plugin and version (if this is a network-related bug): ipset version v6.34\n/sig network /area kube-proxy /area ipvs\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/remove-triage unresolved", "commid": "kubernetes_issue_81474", "tokennum": 251}], "negative_passages": []}
{"query_id": "q-en-kubernetes-287387c9dd85c57bd6325e492c15b617476c333d2707b90598fd6d2715e0e3e0", "query": "package apimachinery import ( <ins> \"encoding/json\" </ins> \"fmt\" \"strings\" \"sync\"", "positive_passages": [{"docid": "doc-en-kubernetes-1e3d5f814d3d1cd0ae92f2f9adc262569d0e3418b95dbcb250b25bdb3821fc75", "text": "This issue proposes the writing of a new test for the API endpoint with the intention of promoting it to Conformance. This issue contains a very masic mock test in order to start the conversation about what a good e2e test would look like for this endpoint. The code below is verified to be hitting the intended endpoint, show as per the queries in APIsnoop's live view of the cluster's audit logs. According to this query, there is only one API endpoint which is for Namespace that isn't being covered. We selected patchCoreV1Namespace to write a test for. Dependencies: The mock test: If a test with these calls is build and merged, conformance will go up by 1 endpoint.\n/sig testing /sig architecture /area conformance", "commid": "kubernetes_issue_86051", "tokennum": 169}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2898552b529676ca28a37180fe2ef85cf2184f47eda68d0f2474c404768b90d7", "query": "glog.V(4).Infof(\"Deleting %q\", castObj.Name) c.enqueue(castObj) } <del> // there aren't very many apiservices, just check them all. func (c *APIServiceRegistrationController) getAPIServicesFor(service *v1.Service) []*apiregistration.APIService { var ret []*apiregistration.APIService apiServiceList, _ := c.apiServiceLister.List(labels.Everything()) for _, apiService := range apiServiceList { if apiService.Spec.Service == nil { continue } if apiService.Spec.Service.Namespace == service.Namespace && apiService.Spec.Service.Name == service.Name { ret = append(ret, apiService) } } return ret } // TODO, think of a way to avoid checking on every service manipulation func (c *APIServiceRegistrationController) addService(obj interface{}) { for _, apiService := range c.getAPIServicesFor(obj.(*v1.Service)) { c.enqueue(apiService) } } func (c *APIServiceRegistrationController) updateService(obj, _ interface{}) { for _, apiService := range c.getAPIServicesFor(obj.(*v1.Service)) { c.enqueue(apiService) } } func (c *APIServiceRegistrationController) deleteService(obj interface{}) { castObj, ok := obj.(*v1.Service) if !ok { tombstone, ok := obj.(cache.DeletedFinalStateUnknown) if !ok { glog.Errorf(\"Couldn't get object from tombstone %#v\", obj) return } castObj, ok = tombstone.Obj.(*v1.Service) if !ok { glog.Errorf(\"Tombstone contained object that is not expected %#v\", obj) return } } for _, apiService := range c.getAPIServicesFor(castObj) { c.enqueue(apiService) } } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-89e8d863e20723ba6498e9abf897dd4e49e26cad02c0dde0a4957b2eb3151e69", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Currently APIServiceRegistrationController watch service change and find the related APIServices related if any. Then it AddAPIService/RemoveAPIService for APIAggregator. I dig into the kube-aggregator and find it no need totally, because update APIServices status when related service or endpoint change. So if does not watch services, it will not miss any event for APIServices. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/cc\n/kind enhancement /sig api-machinery\n/assign\nthat does not follow. AvailableConditionController modifies the APIService object. APIServiceRegistrationController must still watch the APIService objects to observe those changes.\noh, I misread the description. You're saying APIServiceRegistrationController doesn't need to watch v1.Service objects", "commid": "kubernetes_issue_57836", "tokennum": 300}], "negative_passages": []}
{"query_id": "q-en-kubernetes-28e43dcb5387297afad0b948e7912997e49ba88a09fa840a15ed0a86f659743e", "query": "// GetNewReplicaSet returns a replica set that matches the intent of the given deployment; get ReplicaSetList from client interface. // Returns nil if the new replica set doesn't exist yet. func GetNewReplicaSet(deployment *extensions.Deployment, c clientset.Interface) (*extensions.ReplicaSet, error) { <del> rsList, err := ListReplicaSets(deployment, rsListFromClient(c)) </del> <ins> rsList, err := ListReplicaSets(deployment, RsListFromClient(c)) </ins> if err != nil { return nil, err } return FindNewReplicaSet(deployment, rsList) } <del> // rsListFromClient returns an rsListFunc that wraps the given client. func rsListFromClient(c clientset.Interface) rsListFunc { </del> <ins> // RsListFromClient returns an rsListFunc that wraps the given client. func RsListFromClient(c clientset.Interface) RsListFunc { </ins> return func(namespace string, options metav1.ListOptions) ([]*extensions.ReplicaSet, error) { rsList, err := c.Extensions().ReplicaSets(namespace).List(options) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-2f9c6224492589431ce544bf6b6edab10c3ff06174d612eb6875bebaba0cb87e", "text": "IMO it feels like a bad practice to have mutating resource handlers. The deletePod handler is used for queueing a Recreate deployment once it has no pods running. It should merely look at the ReplicaSets that have owner refs as opposed to using dc.getReplicaSetsForDeployment. The orphaning/adoption dance is already happening inside the reconcilation loop.\nI'd like to work on this\nfeel free to grab it. I can't assign the issue to you so I'll add myself; ping me on the PR when you have one.", "commid": "kubernetes_issue_46933", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-290e1f86d17f0fd7e8280e01679bf55910fc2aa2bb24adfa0f6b667d37dcad3c", "query": "<del> apiVersion: extensions/v1beta1 </del> <ins> apiVersion: networking.k8s.io/v1beta1 </ins> kind: Ingress metadata: name: hostname spec: backend: serviceName: hostname <del> servicePort: 80 </del>  No newline at end of file <ins> servicePort: 80 </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-bb7c21eb048735f6a80e177a210d26530b5959539babed9d56a66ccfff61adf4", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: Which test(s) are failing: Since when has it been failing: Testgrid link: https://k8s- Reason for failure: Anything else we need to know: /cc /milestone v1.19 /priority important-soon /sig network\nRef:\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nmy fu points me to this commit [] Fix multiple conversion tests that belongs to this PR , that seems related can you confirm if that PR is causing this test to fail? (should we gate on this test?)\nYes, that PR is related to the failure. The test utility is trying to convert extensions/v1beta1 data read from various files directly to a go type. This was never a valid thing to do, and happened to silently succeed because the two structs had an identical structure. This is exactly the type of bug was designed to flush out\nthe correct fix is to update the test/e2e/testing- files to\n/assign\nIt was my PR that broke this - I can also fix that.\nThanks, o it was the commit that was good but the test that was wrong :upsidedownface: , At least I got right the commit :sweat_smile:\nis out for review (talked with offline, he was aware that I'll send that out)", "commid": "kubernetes_issue_90451", "tokennum": 318}], "negative_passages": []}
{"query_id": "q-en-kubernetes-29318b9df9fe421a915f613ba22b638c1bf77c5b00d3bbf2889d40839e5f2729", "query": "for k, v := range pod.Annotations { copyPod.Annotations[k] = v } <del> copyPod.Annotations[kubetypes.ConfigMirrorAnnotationKey] = kubetypes.MirrorType </del> <ins> copyPod.Annotations[kubetypes.ConfigMirrorAnnotationKey] = getPodHash(pod) </ins> _, err := mc.apiserverClient.Pods(copyPod.Namespace).Create(&copyPod) return err", "positive_passages": [{"docid": "doc-en-kubernetes-8bc8d69d49aedfb4a9bf3991de80f7c339e96bfbefe5b1f250dae70fa0393729", "text": "See for more context. Currently, kubelet compares the spec of a mirror pod (created via apiserver) with that of a static pod (config stored as a file) to decide whether the two are considered identical. If they differ, kubelet would delete the mirror pod and re-create it with the correct spec. Due to the fact that apiserver may set default values for some fields in the spec of the mirror pod, the specs could deviate undesirably. To avoid problems like this, we can store the config of a static pod as an annotation in the mirror pod, and compare the static pod with the annotation.\nWould a hash of the config be sufficient if we're only going to compare? The whole spec would generally be more useful, but I wonder if that is too much data to put in an annotation.\nThis seems totally reasonable to me, but I'm still desperately curious why you can't just bypass defaulting when you generate mirror pod from static pod? (i.e. just use the static pod's configuration verbatim)\nIt's not kubelet who applies the default values here. The admission plugin was only run at the apiserver, and to bypass that, you have to ask apiserver to treat mirror pods differently and potentially at multiple places.\nOn May 22, 2015 10:38 AM, \"Yu-Ju Hong\" wrote: Understood, but is it really multiple places? If so then I agree it's a bad idea. Otherwise it might be worth considering as an alternative.\nIt's untenable for Kubelet to assume to know/circumvent all fields that will be set by other entities: admission control, defaulting, late initialization, auto-something, whatever. It needs to obey the same rules as other clients.\nI don't understand why you would ever want to apply any of the things you mentioned to static pods. Static pods should be copied verbatim into the mirror pods, right? That's what I'm proposing.\nWhat if the master is updated before the kubelet, and the master adds a new API field with a default value?\nThat case should be discussed in\nI agree that mirror pod should reflect the true status of the static pod running on the node, and no default values should be set in this case.", "commid": "kubernetes_issue_8683", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-29318b9df9fe421a915f613ba22b638c1bf77c5b00d3bbf2889d40839e5f2729", "query": "for k, v := range pod.Annotations { copyPod.Annotations[k] = v } <del> copyPod.Annotations[kubetypes.ConfigMirrorAnnotationKey] = kubetypes.MirrorType </del> <ins> copyPod.Annotations[kubetypes.ConfigMirrorAnnotationKey] = getPodHash(pod) </ins> _, err := mc.apiserverClient.Pods(copyPod.Namespace).Create(&copyPod) return err", "positive_passages": [{"docid": "doc-en-kubernetes-0491e123884f0f20f50d0a788bca7a6a29e2fa08227703a00221ecbd3bcf483c", "text": "However, I think it'd be harder to implement this way since, as stated above, that there are many things to circumvent in the apiserver itself. It could also be harder to keep this special case from being broken by a yet another new feature/plugin. Keeping the hash of the config in the annotation seems like a good compromise even though it may not reflect the true status 100% accurately. I think this is acceptable. What do you think?\nSure, if you think the annotation approach is easier, I would go with that. I guess in the case Brian mentoined (master adds a new API field with a default value), you would not update the mirror pod, because the static pod definition has not changed?\nYes, a hash would be sufficient.\nIt shouldn't be necessary to update the mirror pod in the case that a new default field was updated, because that field should be populated automatically by the apiserver on decode from etcd.\nWe should fix this so we don't have this problem again in 1.2.", "commid": "kubernetes_issue_8683", "tokennum": 226}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2993ad445c08d13d635032edd42d20b932d63972bd11eb85614aa2247eaa9d21", "query": "node, victims, nominatedPodsToClear, err := sched.config.Algorithm.Preempt(preemptor, sched.config.NodeLister, scheduleErr) if err != nil { <del> klog.Errorf(\"Error preempting victims to make room for %v/%v.\", preemptor.Namespace, preemptor.Name) </del> <ins> klog.Errorf(\"Error preempting victims to make room for %v/%v: %v\", preemptor.Namespace, preemptor.Name, err) </ins> return \"\", err } var nodeName = \"\"", "positive_passages": [{"docid": "doc-en-kubernetes-f39360e36dc13c7f3c135efe81c665373563851402d40604cca632c72aed6a7c", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Default scheduler crash if scheduler extender filter returns a not found node What you expected to happen: Default scheduler just should consider the not found node as not an candidate, instead of crash itself (panic). How to reproduce it (as minimally and precisely as possible): cluster only have 1 node: 0.0.0.1 scheduler extender (with nodeCacheCapable enabled) filter accidentally returns a candidate node: 0.0.0.2 scheduler recieved the candidate nodes: 0.0.0.2 from scheduler extender, but got below error: The is SuggestedHost: filteredNodes[0].Name: Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig scheduling", "commid": "kubernetes_issue_79640", "tokennum": 261}], "negative_passages": []}
{"query_id": "q-en-kubernetes-29a912dd0d30992d4c6777e412708c20fd1f08ad8232a0866175c0119777b774", "query": "}) } <ins> // PodSecurityPolicyDescriber generates information about a PodSecurityPolicy. type PodSecurityPolicyDescriber struct { clientset.Interface } func (d *PodSecurityPolicyDescriber) Describe(namespace, name string, describerSettings printers.DescriberSettings) (string, error) { psp, err := d.Extensions().PodSecurityPolicies().Get(name, metav1.GetOptions{}) if err != nil { return \"\", err } return describePodSecurityPolicy(psp) } func describePodSecurityPolicy(psp *extensions.PodSecurityPolicy) (string, error) { return tabbedString(func(out io.Writer) error { w := NewPrefixWriter(out) w.Write(LEVEL_0, \"Name:t%sn\", psp.Name) w.Write(LEVEL_0, \"nSettings:n\") w.Write(LEVEL_1, \"Allow Privileged:t%tn\", psp.Spec.Privileged) w.Write(LEVEL_1, \"Default Add Capabilities:t%vn\", capsToString(psp.Spec.DefaultAddCapabilities)) w.Write(LEVEL_1, \"Required Drop Capabilities:t%sn\", capsToString(psp.Spec.RequiredDropCapabilities)) w.Write(LEVEL_1, \"Allowed Capabilities:t%sn\", capsToString(psp.Spec.AllowedCapabilities)) w.Write(LEVEL_1, \"Allowed Volume Types:t%sn\", fsTypeToString(psp.Spec.Volumes)) w.Write(LEVEL_1, \"Allow Host Network:t%tn\", psp.Spec.HostNetwork) w.Write(LEVEL_1, \"Allow Host Ports:t%sn\", hostPortRangeToString(psp.Spec.HostPorts)) w.Write(LEVEL_1, \"Allow Host PID:t%tn\", psp.Spec.HostPID) w.Write(LEVEL_1, \"Allow Host IPC:t%tn\", psp.Spec.HostIPC) w.Write(LEVEL_1, \"Read Only Root Filesystem:t%vn\", psp.Spec.ReadOnlyRootFilesystem) w.Write(LEVEL_1, \"SELinux Context Strategy: %stn\", string(psp.Spec.SELinux.Rule)) var user, role, seLinuxType, level string if psp.Spec.SELinux.SELinuxOptions != nil { user = psp.Spec.SELinux.SELinuxOptions.User role = psp.Spec.SELinux.SELinuxOptions.Role seLinuxType = psp.Spec.SELinux.SELinuxOptions.Type level = psp.Spec.SELinux.SELinuxOptions.Level } w.Write(LEVEL_2, \"User:t%sn\", stringOrNone(user)) w.Write(LEVEL_2, \"Role:t%sn\", stringOrNone(role)) w.Write(LEVEL_2, \"Type:t%sn\", stringOrNone(seLinuxType)) w.Write(LEVEL_2, \"Level:t%sn\", stringOrNone(level)) w.Write(LEVEL_1, \"Run As User Strategy: %stn\", string(psp.Spec.RunAsUser.Rule)) w.Write(LEVEL_2, \"Ranges:t%sn\", userIDRangeToString(psp.Spec.RunAsUser.Ranges)) w.Write(LEVEL_1, \"FSGroup Strategy: %stn\", string(psp.Spec.FSGroup.Rule)) w.Write(LEVEL_2, \"Ranges:t%sn\", groupIDRangeToString(psp.Spec.FSGroup.Ranges)) w.Write(LEVEL_1, \"Supplemental Groups Strategy: %stn\", string(psp.Spec.SupplementalGroups.Rule)) w.Write(LEVEL_2, \"Ranges:t%sn\", groupIDRangeToString(psp.Spec.SupplementalGroups.Ranges)) return nil }) } func stringOrAll(s string) string { if len(s) > 0 { return s } return \"*\" } func stringOrNone(s string) string { if len(s) > 0 { return s } return \"<none>\" } func fsTypeToString(volumes []extensions.FSType) string { strVolumes := []string{} for _, v := range volumes { strVolumes = append(strVolumes, string(v)) } return stringOrNone(strings.Join(strVolumes, \",\")) } func hostPortRangeToString(ranges []extensions.HostPortRange) string { formattedString := \"\" if ranges != nil { strRanges := []string{} for _, r := range ranges { strRanges = append(strRanges, fmt.Sprintf(\"%d-%d\", r.Min, r.Max)) } formattedString = strings.Join(strRanges, \",\") } return stringOrNone(formattedString) } func userIDRangeToString(ranges []extensions.UserIDRange) string { formattedString := \"\" if ranges != nil { strRanges := []string{} for _, r := range ranges { strRanges = append(strRanges, fmt.Sprintf(\"%d-%d\", r.Min, r.Max)) } formattedString = strings.Join(strRanges, \",\") } return stringOrNone(formattedString) } func groupIDRangeToString(ranges []extensions.GroupIDRange) string { formattedString := \"\" if ranges != nil { strRanges := []string{} for _, r := range ranges { strRanges = append(strRanges, fmt.Sprintf(\"%d-%d\", r.Min, r.Max)) } formattedString = strings.Join(strRanges, \",\") } return stringOrNone(formattedString) } func capsToString(caps []api.Capability) string { formattedString := \"\" if caps != nil { strCaps := []string{} for _, c := range caps { strCaps = append(strCaps, string(c)) } formattedString = strings.Join(strCaps, \",\") } return stringOrNone(formattedString) } </ins> // newErrNoDescriber creates a new ErrNoDescriber with the names of the provided types. func newErrNoDescriber(types ...reflect.Type) error { names := make([]string, 0, len(types))", "positive_passages": [{"docid": "doc-en-kubernetes-6d76348628664e8e1283688eb2571b9c9ddbeb679dd9d941b90f8deb0741d5d7", "text": "Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see ): No What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): describe psp Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST Kubernetes version (use ): Environment: Doesn't matter. What happened: doesn't show PSP's fields: What you expected to happen: All PSP fields should be shown. How to reproduce it (as minimally and precisely as possible):\nIf you're agree with that than I (or :) ) could implement it.\nyes, improve the describer. Look at the scc describer for formatting.\nany ideas which SIG should own PSP?\nIn this case it should be sig-cli /sig cli\nyeah, this is cli related. I'd go with sig-auth for actual behavior.", "commid": "kubernetes_issue_43757", "tokennum": 222}], "negative_passages": []}
{"query_id": "q-en-kubernetes-29ad0ed9eda1bf1ef6a60e1452ab272ffb32160d08160a2c8396de4e3b885024", "query": "\"description\": \"ServicePort contains information on service's port.\", \"properties\": { \"appProtocol\": { <del> \"description\": \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and http://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol. This is a beta field that is guarded by the ServiceAppProtocol feature gate and enabled by default.\", </del> <ins> \"description\": \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol. This is a beta field that is guarded by the ServiceAppProtocol feature gate and enabled by default.\", </ins> \"type\": \"string\" }, \"name\": {", "positive_passages": [{"docid": "doc-en-kubernetes-3e7e95e6f142ca39e6e3ca0b78c3932bd6cbdfdc898eed9d3ffda27d28f904c7", "text": "We should make the change in PR API reference links to should use HTTPS, not HTTP Visit h and look at the IANA hyperlinks Once this fix is made, a PR to is needed to update the docs (by autogenerating them). This typically would be deferred until the next Kubernetes release. v1.23 not applicable not applicable not applicable not applicable not applicable\n/sig docs\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI opened this issue so that someone else can open a new PR that is equivalent to .\n/retitle Update links to IANA for Service Name and Transport Protocol Port Number Registry\nI would like to work on this issue. May I assign it to myself?\nAnyone - including you - is welcome to work on this issue! So long as you've you can open a pull request to propose a fix.\nThanks\n/assign\nI have made the PR. I hope this works. If not then will be happy to do the necessary changes.\nHad to close the previous PR because of issues, here is the new one I made.", "commid": "kubernetes_issue_106980", "tokennum": 300}], "negative_passages": []}
{"query_id": "q-en-kubernetes-29cc55ca31fa87d8f0e624ffb35097645ba03ad675c5a2b7168587b35c19b619", "query": "// Read retrieves data with the given \"key\" from CycleState. If the key is not // present an error is returned. <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Read(key StateKey) (StateData, error) { <ins> c.mx.RLock() defer c.mx.RUnlock() </ins> if v, ok := c.storage[key]; ok { return v, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-43588246e28947764a0f8a5c9c5b1d76a5819a8eaa1c439f79abd429269822c0", "text": "What happened: kube-scheduler () crashes due to a panic while running : The race condition is triggered when an out-of-tree plugin, that writes to during its Filter phase, is registered through . Access to in general happens from a single goroutine and there are no practical concurrency issues, with the exception of the phase, that parallelizes calls for each node across plugins: A quick glance at the tip of the branch seems to indicate the bug is still present there. What you expected to happen: Ideally access to should be synchronized everywhere for correctness, including by all in-tree plugins, since there are no guarantees about how will call multiple plugins concurrently. It seems to me it is something that was considered at some point, given that has methods. Sadly, almost no in-tree plugins are synchronizing access. For now, I will try to work around the problem by doing a single write to during and storing a data bag structure where I will write state into during (with proper synchronization), instead of writing to directly. How to reproduce it (as minimally and precisely as possible): Install a scheduler plugin that writes to during its phase. In-tree (builtin) plugins are not synchronizing their access to . Environment: Kubernetes version (use ): v1.18.8 Cloud provider or hardware configuration: linux-amd64 (AWS) OS (e.g: ): Ubuntu 18.04.5 LTS (Bionic Beaver) Others: custom kube-scheduler binary built with an out-of-tree plugin using\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scheduling\nAFAICT all in-tree plugins write to the cycle state in PreFilter and then only read from cycle state in Filter. So this shouldn't be a problem with in-tree plugins as concurrent read access should be fine during RunFilterPlugins. But since your out-of-tree plugin writes in Filter, I can see why this can be a problem.", "commid": "kubernetes_issue_95887", "tokennum": 515}], "negative_passages": []}
{"query_id": "q-en-kubernetes-29cc55ca31fa87d8f0e624ffb35097645ba03ad675c5a2b7168587b35c19b619", "query": "// Read retrieves data with the given \"key\" from CycleState. If the key is not // present an error is returned. <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Read(key StateKey) (StateData, error) { <ins> c.mx.RLock() defer c.mx.RUnlock() </ins> if v, ok := c.storage[key]; ok { return v, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-278036efba637c2a6a49330142a64ca8f7b65a0d21755fde24824f9c473a00c9", "text": "Aside from adding Lock/Unlock in in-tree plugin, offering mutual exclusion on each key as a built-in feature within CycleState could be an alternative solution. This way, reads from in-tree plugins during Filter wouldn't interfere with writes during Filter from out-of-tree plugins.\ncc\nshould we change the Read/Write CycleState methods to be thread safe?\nAdding locks without a proper justification would just increase the latency. could you clarify your use case? Why do you need to write anything during Filter?\nyeah, we should measure it, but I don't expect it to have significant effect...\nAdding locks without a proper justification would just increase the latency. Without contention (which is the case with in-tree plugins), I don't think this is a concern.\nAdapting source from : source: essentially, 11.3 ns/Lock-Unlock pair\nI remember locks showing up in profiling for PreScore/Score for certain plugins. Although I have to admit that the accesses were not properly implemented. I'd like to hear an answer for before doing any experiments.\n+1 to that I'd also like to understand the motivations / requirements of mutating CycleState in Filter().\nMy particular use-case is that we have resources being dynamically to/removed from Nodes, and those resources need to be allocated (and tracked) in the scheduling loop. Technically I could pre-compute all the available dynamic resources for all Nodes at the phase, and snapshot it, but that would require me to pre-compute everything for all Nodes on all scheduling cycles. Instead, what I'm currently doing is computing what dynamic resources can be utilized on-demand during the phase (kind of a lazy loading of dynamic resources for each pair), and saving state of what extra resources were considered during for each Node that was evaluated. Then, later in the scheduler plugin can lock-in the exact dynamic resources for the particular Node that was selected. I understand the concern with adding extra synchronization overhead without a real need. Even if my use-case is not good enough to justify it, there is another argument for it: technically, the lack of access synchronization on violates the . Even if in the end we decide synchronizing all access is not worth the overhead (for correctness), I would strongly encourage better documentation saying which plugin phases are allowed to modify , and perhaps even forcing a snapshot-read-only copy of to be used by plugins.\nUsing the scheduler to track resources is not a good idea.", "commid": "kubernetes_issue_95887", "tokennum": 539}], "negative_passages": []}
{"query_id": "q-en-kubernetes-29cc55ca31fa87d8f0e624ffb35097645ba03ad675c5a2b7168587b35c19b619", "query": "// Read retrieves data with the given \"key\" from CycleState. If the key is not // present an error is returned. <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Read(key StateKey) (StateData, error) { <ins> c.mx.RLock() defer c.mx.RUnlock() </ins> if v, ok := c.storage[key]; ok { return v, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-b826aaa34ec054d9cc587ce8587a04002d4daa70694ce73071b413f1bf7ba0c6", "text": "The scheduler should be stateless. Can't you track the resources with an external controller or with a device plugin and making it part of the Node spec?\nthere may be some misunderstanding in my poor choice of words. What I mean by \"tracking\" is that the scheduler needs to track usage and availability of these extra per-Node resources, to be able to allocate them during placement/scheduling. Exactly the same it does with volumes, cpus, memory, ephemeral disk, etc Doing computations in a controller outside of the scheduling loop would be similar to \"precomputing\" these resources. In my particular use case I chose a different way because: introduces another point of failure, if the external controller stops pre-computing extra resources and publishing them somewhere (CRD, Node spec, etc) scheduling halts (at least scheduling on these extra resources) Node resources in my use case are volatile (they are coming and going frequently), and the extra latency by an extra controller (vs doing all computations right in the scheduling loop) may be problematic for my use case. Even if you consider my use case not enough to add proper synchronization to , I'd still encourage making it explicit what scheduling phases are allowed to modify it (and even passing in a snapshot read-only version of to phases that are not expected to update it), to avoid confusion and race conditions.\nOk, if you are not tracking the existence of resources in the scheduler, I wouldn't suggest the external controller. Still, have you considered the device plugin framework? That way, the default kube-scheduler could keep track of resources usage. Otherwise, I still don't see why you would need to update the CycleState during Filter. As its name indicates, CycleState only lives during a scheduling cycle.\nRegardless of the correctness of usage of CycleState to do what wants, I still think we need to do at least one of the following: that writing to CycleState during Filter will lead to data races, a read-only CycleState to Filter plugins (whether we do this at the interface level or if we simply drop Write requests during Filter is an implementation detail), or make CycleState concurrency safe CycleState as it exists right now allows plugin authors to shoot themselves in the foot IMO.\nI'm leaning towards 1, but it's fair to continue the discussion before deciding.\nCan you run the \"controller\" as a goroutine along with your scheduler plugin?", "commid": "kubernetes_issue_95887", "tokennum": 520}], "negative_passages": []}
{"query_id": "q-en-kubernetes-29cc55ca31fa87d8f0e624ffb35097645ba03ad675c5a2b7168587b35c19b619", "query": "// Read retrieves data with the given \"key\" from CycleState. If the key is not // present an error is returned. <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Read(key StateKey) (StateData, error) { <ins> c.mx.RLock() defer c.mx.RUnlock() </ins> if v, ok := c.storage[key]; ok { return v, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-038a628d524f09c8393af798b6053a1fded9e84e2c01785ad258fb86c8d6d618", "text": "So it's not an external controller binary, and hence don't introduce another point of failure. It's pretty like how the default scheduler manages its internal cache. But note that cache is only needed when you need a more efficient data structure. If a {key:value} map is good enough, spinning up a XYZInformer and obtain the latest XYZ resource on-demand is the most recommended way. I think it quite depends on how you design the internal XYZ cache. For example, it should only tweak the cache in an incremental manner - in other words, unchanged resource will be kept unmodified. You can check out the \"doubly-pointer snapshot\" of scheduler's cache. With above said, if I understand your case correctly, you may need to build a sophisticated XYZ cache, which runs in a separate goroutine and responds to your XYZ resource changes. And then upon each scheduling cycle, take a snapshot (may needs a specific snapshotting algorithm) in PreFilter() and WRITE to CycleState, and then in Filter() READ from CycleState. My personal option is to suggest all plugin developers to read from CycleState in Filter().\nnailed it. What you describe is almost exactly what I\u2019m doing today. There are some details particular to my use case (e.g. just tracking current state with an informer and an incremental cache is not enough, because there\u2019s some logic involved in deciding if currently available resources are usable by each pair, and I currently do that computation in as pairs are evaluated). In any case, I just wanted to share my use case to provide some color, but I don\u2019t want what I\u2019m doing distracting us from the more important questions, mentioned by above. My personal preference would be as a very short term next step, then when someone has cycles to do it. I would be OK with punting on until a more strong need shows up.\nNote that limiting to only reading from works for me, as long as I can still read my own data structure from it and do writes on it (i.e. don\u2019t deepclone for the phase).\nalso adds overhead (from copying the state, which can be very expensive).\nCould implement just by changing the interface passed to (e.g. ). That wouldn\u2019t be backwards compatible, but very cheap.", "commid": "kubernetes_issue_95887", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-29cc55ca31fa87d8f0e624ffb35097645ba03ad675c5a2b7168587b35c19b619", "query": "// Read retrieves data with the given \"key\" from CycleState. If the key is not // present an error is returned. <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Read(key StateKey) (StateData, error) { <ins> c.mx.RLock() defer c.mx.RUnlock() </ins> if v, ok := c.storage[key]; ok { return v, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-73e2408e2bea0ec3fe3177e8a87291d57a052eb7c05f546c204ec27aefee3293", "text": "I guess that would work in the sense that you cannot change the high level values of the CycleState map, but you could still override what's inside them, if they have pointers. But maybe that's ok.\nbut you could still override what's inside them, if they have pointers. But maybe that's ok. yeah, if it was pointers and if the underlying data needed to be modified, I'd imagine it would have its own Lock/Unlock semantics\nfor such implementation, the only remaining concern is backwards compatibility. So I would leave that decision to who leads the scheduling-plugins repo.\nI rethink 's original problem a little bit: the original racing issue occurs when reading CycleState in in-tree plugins, this indicates one of the (out-of-tree) plugins is (over)writing the most high-level value of the CycleState map. But if we control the locking inside the out-of-tree plugin, and mutate that particular in-place, that would be good enough? Case 3 in the above program demonstrates the correct way to manipulate the specific out-of-tree state. Let me know your thoughts. If it resolves 's concern, we don't need to make any change on the Filter() interface.\nCase 3 is how I am working around the problem today to avoid the race. I write a \"data bag\" once into top level in , then only modify my own inner structure (with proper locking) in , without doing any further modifications to directly (top level) in . That is acceptable, but I'd encourage you to consider making the interface (and documentation) more explicit for plugins, so they avoid the mistake of writing directly into . Without changing anything (no documentation, no readonly interface), it is pretty easy for a plugin to use in a way that you don't want to support.\nThanks for confirming that. Yes, documenting it, or(and) publishing examples would be quite helpful to clarify the semantics. As a wrap-up: a keyed value can be read from CycleState, literally , in any phase. It's always race-free.", "commid": "kubernetes_issue_95887", "tokennum": 455}], "negative_passages": []}
{"query_id": "q-en-kubernetes-29cc55ca31fa87d8f0e624ffb35097645ba03ad675c5a2b7168587b35c19b619", "query": "// Read retrieves data with the given \"key\" from CycleState. If the key is not // present an error is returned. <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Read(key StateKey) (StateData, error) { <ins> c.mx.RLock() defer c.mx.RUnlock() </ins> if v, ok := c.storage[key]; ok { return v, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-3be32b87589c297c7c2842b086ef786e82de3563d7c057c1ca18b1f858ccd170", "text": "if you want to mutate the top-level keyed value in CycleState, if it's a phase that CycleState is accessed consecutively, such as PreFilter, PreScore, it's safe to mutate CycleState in any manner if it's a phase that CycleState is accessed parallelly, to be race-free, (for now) you only have 1 option: keep the keyed value's pointer unchanged, and use an internal lock to mutate that pointer obj [TBD] we may come up with changes to add read locks to all in-tree plugins when reading values from CycleState, so that the out-of-tree plugin can surround its mutating logic between and - th mutating logic thereby can be any style Any thoughts on the TBD item? I would assume read locks wouldn't cost too much.\nFor now, I think the documentation is correct, it clearly says Read() and Write() are not thread-safe: The key thing here is whether in-tree plugin should use RLock/RUnlock or not. If yes, out-of-tree plugins can be freed to use Lock/Unlock. (see the TBD item in the previous comment)\nI like the TBD, and optimizing for correctness in how in-tree plugins are accessing . I understand the concern with synchronization overhead, but I would be really surprised if it is the bottleneck in scheduling code.\nIt can be, when you have 5k-nodes clusters, or bigger.\nI don't think it will be expensive, a rlock should be equivalent to an atomic add operation (basically it increments the number of readers). As a comparison, looking up the state from the map is likely to be more expensive.\nOf course we are assuming no contention in the default plugins.\nThis is my impression as well. A vanilla version of scheduler doesn't impose write lock in Filter() and Score(), so should be good.\nWe can always see with the benchmarks and revert if its not negligible.\nI will run the benchmarks to see if there is perf downgrade. /assign\nIssues 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\n/remove-lifecycle stale This is still relevant, yes?", "commid": "kubernetes_issue_95887", "tokennum": 535}], "negative_passages": []}
{"query_id": "q-en-kubernetes-29cc55ca31fa87d8f0e624ffb35097645ba03ad675c5a2b7168587b35c19b619", "query": "// Read retrieves data with the given \"key\" from CycleState. If the key is not // present an error is returned. <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Read(key StateKey) (StateData, error) { <ins> c.mx.RLock() defer c.mx.RUnlock() </ins> if v, ok := c.storage[key]; ok { return v, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-bcac7b47c31a3bdcd9ddd71bfacab7dca4a98e08ad1188f8a89f61b6d0a63d38", "text": "IIUC the volumebinding plugin has been fixed, but external plugins can still shoot themselves in the foot.\n/priority backlog\nYes. I'm working on this, late this week I will send out a PR along with perf test result.", "commid": "kubernetes_issue_95887", "tokennum": 53}], "negative_passages": []}
{"query_id": "q-en-kubernetes-29d3000b1c61d5cc8a6a262939249245b4bbe901dffef43c7587c9b61e54e5e7", "query": "// returned. func (adapter *EndpointsAdapter) Create(namespace string, endpoints *corev1.Endpoints) (*corev1.Endpoints, error) { endpoints, err := adapter.endpointClient.Endpoints(namespace).Create(endpoints) <del> if err == nil && adapter.endpointSliceClient != nil { _, err = adapter.ensureEndpointSliceFromEndpoints(namespace, endpoints) </del> <ins> if err == nil { err = adapter.EnsureEndpointSliceFromEndpoints(namespace, endpoints) </ins> } return endpoints, err }", "positive_passages": [{"docid": "doc-en-kubernetes-12f7047d8d873a7d6bac7023fc38517c350449071b3fe2b6d53f3ea14de5351f", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: EndpointSlice for masters was not created after enabling EndpointSlice on a pre-existing cluster. Only those EndpointSlices managed by kube-controller-manager were created. What you expected to happen: EndpointSlice for masters should be created after enabling EndpointSlice on a pre-existing cluster, the same as the EndpointSlices managed by kube-controller-manager. How to reproduce it (as minimally and precisely as possible): kubeadm to create a cluster: the EndpointSlice feature by editing the kube-apiserver, kube-controller-manager, kube-proxy manifest kube-apiserver and kube-controller-manager is restarted, the EndpointSlice in namespace will be missing. Anything else we need to know?: Environment: Kubernetes version (use ):Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools:Network plugin and version (if this is a network-related bug): Others:\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/remove-triage unresolved /assign", "commid": "kubernetes_issue_84419", "tokennum": 307}], "negative_passages": []}
{"query_id": "q-en-kubernetes-29ea7fe9b13e8aefa663ee778415add4ef8aa63519bcb6452fe4efd20a176b71", "query": "} func (f *FakeMounter) IsNotMountPoint(dir string) (bool, error) { <del> return IsNotMountPoint(f, dir) </del> <ins> return isNotMountPoint(f, dir) </ins> } func (f *FakeMounter) IsLikelyNotMountPoint(file string) (bool, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-4bcfc015d2b9d9fa1e84475a3e08fb9ef8299b4e5f821f790188ad7bdae6ecbc", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: There's , and . The former is used by local and nfs volume plugins, while the latter is used by , which is also used by local and nfs volume plugins. What you expected to happen: Can we consolidate these? This is really confusing and could easily be the source of bugs. <!-- DO NOT EDIT BELOW THIS LINE --/kind cleanup\ncc\n/assign I'd like to clean up code.", "commid": "kubernetes_issue_72387", "tokennum": 133}], "negative_passages": []}
{"query_id": "q-en-kubernetes-29fb8829b9d1fd257ef3dc59bfc80f22ca8f8b126071f9af06fae9f3b0807298", "query": "CLUSTER_IP_RANGE=\"${CONTAINER_SUBNET}\" fi <ins> # If enabled kube-controller-manager will be started with the --enable-hostpath-provisioner flag ENABLE_HOSTPATH_PROVISIONER=\"${ENABLE_HOSTPATH_PROVISIONER:-true}\" </ins> # OpenContrail networking plugin specific settings OPENCONTRAIL_TAG=\"${OPENCONTRAIL_TAG:-R2.20}\" OPENCONTRAIL_KUBERNETES_TAG=\"${OPENCONTRAIL_KUBERNETES_TAG:-master}\"", "positive_passages": [{"docid": "doc-en-kubernetes-ef45ff070b2c05a069c3f77b9a64e0bfff59d1f717362ac04203c879e5a7b68c", "text": "feature request Enables easier testing for pv/pvc, and all derivatives like pet sets. The only alternative is to use manually created pv of local type. I have time to work on it myself and created this feature to collect feedback/ideas on what provider should be enabled by default.\nSince this was merged should we close this issue?", "commid": "kubernetes_issue_32119", "tokennum": 67}], "negative_passages": []}
{"query_id": "q-en-kubernetes-29fce90aee316a5d21e13eb93dc1e8959e34d8e4315b66812ca3ecc683b6cbb4", "query": "}, }, }, <del> }) </del> <ins> }, true) </ins> }) // The following tests for remote command execution and port forwarding are", "positive_passages": [{"docid": "doc-en-kubernetes-65bf469670180d69e57fdc1a820a8f2f435cec685a9975e90f226dd126851fba", "text": "As far as I can tell, container liveness probes of type exec flat out don't work against clusters built at head. I had the kubelet always log the output of the exec'ed command, and it's always empty no matter what I exec, causing the probe to fail since it requires the output to be equal to the string \"ok\". If you want to test it, try adding a liveness probe of this form to any container: I also tried these lovely forms, to more closely match the liveness example under examples/: On the plus side, this may be an opportunistic time to switch over to\nThe reason that the e2e test for exec liveness probes hasn't caught this is that it only tests that containers are restarted when they fail liveness probes. It doesn't test that containers aren't restarted when their liveness checks should be succeeding. The e2e test's exec'ed commands also only ever produced empty output, rather than the expected \"fail\" output.\nIs it possible to include this in a new pre-release, since it fixes a bug in health checking? I see it merged in master and I'm wondering what the policy is of releasing new code in a separate (0.16.*) release.", "commid": "kubernetes_issue_7618", "tokennum": 275}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2a2195e369771997843fd927b58d7ec2ca049a799edd65ef4732cf374512caa6", "query": "importmap = \"k8s.io/kubernetes/vendor/k8s.io/apiserver/pkg/server/healthz\", importpath = \"k8s.io/apiserver/pkg/server/healthz\", deps = [ <ins> \"//staging/src/k8s.io/apimachinery/pkg/util/sets:go_default_library\", </ins> \"//staging/src/k8s.io/apimachinery/pkg/util/wait:go_default_library\", \"//vendor/k8s.io/klog:go_default_library\", ],", "positive_passages": [{"docid": "doc-en-kubernetes-01cc291fb1d6afeae9b284d60dd407b578a72d26e4c50043cbdf654c92184c45", "text": "What would you like to be : Add support to the kube-apiserver so that we can disable health-checks via query params. Why is this needed: Currently, the healthz endpoint is inflexible in that any and all health checks are currently executed when the endpoint is hit. Since the kube-apiserver only currently supports a liveness check, this means all persistent health check failures will eventually result in a kubelet driven restart. However, this may not be desirable behavior if you have additional monitoring services layered on top of your control plane. For instance, take the etcd failure from the perspective of the kube-apiserver. Currently, persistent failures during the etcd health check from the api-server healthz endpoint will cause the kube-apiserver to be restarted. This sometimes helps (in the case of a faulty etcd-client connection) but also can be detrimental (the kube-apiserver restarts until the etcd cluster is functioning, then the kube-apiserver bombards the etcd cluster with requests to update local caches, saturating the etcd cluster with requests, causing it to timeout on its own liveness probes and trigger a kubelet-driven restart). Let's say that we could now disable etcd from our liveness health check. Then if we had an external monitoring service, we could ask independently ask etcd if it was healthy and we could also ask the kube-apiserver if it thought etcd was unhealthy. Based on the combination of those answers, we could enable more intelligent responses to certain situation, like restarting the kube-apiserver when it thought etcd was unhealthy but etcd was actually reporting as healthy but not doing so when etcd was actually unhealthy. This feature is backwards-compatible and opt-in. There would be no impact to existing behavior unless these query params are actually used. /sig api-machinery /kind feature\n/cc\nSGTM\n/assign", "commid": "kubernetes_issue_70591", "tokennum": 432}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2a45e11622b2551d6eac6ae5bb2e80781867110c72753de45664d95963dfaa81", "query": "} } } <ins> func TestPredicatesRegistered(t *testing.T) { var functionNames []string // Files and directories which predicates may be referenced targetFiles := []string{ \"./../../algorithmprovider/defaults/defaults.go\", // Default algorithm \"./../../factory/plugins.go\",                     // Registered in init() \"./../../../../../pkg/\",                          // kubernetes/pkg, often used by kubelet or controller } // List all golang source files under ./predicates/, excluding test files and sub-directories. files, err := codeinspector.GetSourceCodeFiles(\".\") if err != nil { t.Errorf(\"unexpected error: %v when listing files in current directory\", err) } // Get all public predicates in files. for _, filePath := range files { functions, err := codeinspector.GetPublicFunctions(filePath) if err == nil { functionNames = append(functionNames, functions...) } else { t.Errorf(\"unexpected error when parsing %s\", filePath) } } // Check if all public predicates are referenced in target files. for _, functionName := range functionNames { args := []string{\"-rl\", functionName} args = append(args, targetFiles...) err := exec.Command(\"grep\", args...).Run() if err != nil { switch err.Error() { case \"exit status 2\": t.Errorf(\"unexpected error when checking %s\", functionName) case \"exit status 1\": t.Errorf(\"predicate %s is implemented as public but seems not registered or used in any other place\", functionName) } } } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-3229e3f28f67afa9ddea85d9d31a50803c261e0ae30f76f950060d1790215e64", "text": "I just noticed you forgot to register the image locality priority function in in I also missed it when I reviewed your PR. I have fixed this in . But it would be great if you could figure out a mechanism that would ensure that all predicate/priority functions that are tested (you can assume they will always live under ) are registered, and fail the test if not. That will allow us to prevent this mistake in the future.\nThanks! Will fix this soon!\nSeems need to wait for in before I send PR? Otherwise this test will always fail ...", "commid": "kubernetes_issue_21236", "tokennum": 114}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2a4de7710deb02723dc25c53bd930d9fb6686493f4d6efcbd1c164d222f93fab", "query": "if [ ! -w $(dirname `which gcloud`) ]; then sudo_prefix=\"sudo\" fi <del> ${sudo_prefix} gcloud ${gcloud_prompt:-} components update alpha || true ${sudo_prefix} gcloud ${gcloud_prompt:-} components update beta || true ${sudo_prefix} gcloud ${gcloud_prompt:-} components update ${CMD_GROUP:-} || true ${sudo_prefix} gcloud ${gcloud_prompt:-} components update kubectl|| true </del> <ins> ${sudo_prefix} gcloud ${gcloud_prompt:-} components install alpha || true ${sudo_prefix} gcloud ${gcloud_prompt:-} components install beta || true ${sudo_prefix} gcloud ${gcloud_prompt:-} components install kubectl|| true </ins> ${sudo_prefix} gcloud ${gcloud_prompt:-} components update || true }", "positive_passages": [{"docid": "doc-en-kubernetes-e853f94b17b31c823d86645df008663c9942e2f2dd039e3926420121cf6b1093", "text": "This is really annoying because it requires me to interact with my shell while running up / down whereas before the commands just ran to completion on their own.", "commid": "kubernetes_issue_18374", "tokennum": 30}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2a58c21b146c955ade49a0b06594fdb9be925274d63cd90901d40f4b70b49753", "query": "// Initialize passes a Kubernetes clientBuilder interface to the cloud provider func (vs *VSphere) Initialize(clientBuilder cloudprovider.ControllerClientBuilder, stop <-chan struct{}) { vs.kubeClient = clientBuilder.ClientOrDie(\"vsphere-legacy-cloud-provider\") <ins> vs.nodeManager.SetNodeGetter(vs.kubeClient.CoreV1()) </ins> } // Initialize Node Informers", "positive_passages": [{"docid": "doc-en-kubernetes-b9a7a79272b4f05e986ec052f9f8348c60cffedf2d99a44ddafb98b4101b558f", "text": "I am enabling CSI migration on a vSphere cluster. A node was fully drained, all its Pods are deleted, but just before KCM detaches in-tree vSphere volume volumes from it, KCM restarts. A new KCM starts, sees attached volumes in that are not needed by any Pod on the node and calls vSphere in-tree volume plugin . The in-tree vSphere volume plugin + cloud provider marks the volume as detached right away, without reaching to vCenter API. The volume remains attached forever. I don't think it's related to CSI migration, IMO a regular node drain + KCM restart at the same time can cause the same issue. KCM logs: The in-tree cloud provider has a and from it. It apparently has not processed all nodes at the time A/D controller tries to detach the node. The in-tree vSphere volume plugin + cloud provider detaches the volume in vCenter. That's really tricky, it's very hard / impossible to reproduce on a real cluster. I had to inject errors to Detach() in-tree volume call, so they fail until KCM is restarted. Newly started KCM would detach the volume just fine (no error would be injected there), but marks the volume as detached right away. For the record (and search-ability), the CSI driver that tries to attach the volume to another node complains either: Or: cc It could be somewhat related to , however, not all cases of can be related to KCM restart. As I mentioned above, it's very hard/impossible to synchronize KCM restart with draining a node in a real cluster. <details</details<detailsvSphere 7.0.3 </details<details</details<detailsOpenShift </details<detailsCRI-O </details<details</details\n/sig storage\nTried just moving a Pod between nodes without CSI migration involved + restarting KCM when the volume is still attached to the old node. In-tree volume plugin on the new node says:\n/assign\nWhat CSI driver version and K8s version are you testing with?\nKubernetes is 1.25 and CSI driver is 2.7, still, I think it's not releated to the CSI driver, it's KCM who marks the in-tree volume as detached due to not populated node cache.", "commid": "kubernetes_issue_117091", "tokennum": 517}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2a58c21b146c955ade49a0b06594fdb9be925274d63cd90901d40f4b70b49753", "query": "// Initialize passes a Kubernetes clientBuilder interface to the cloud provider func (vs *VSphere) Initialize(clientBuilder cloudprovider.ControllerClientBuilder, stop <-chan struct{}) { vs.kubeClient = clientBuilder.ClientOrDie(\"vsphere-legacy-cloud-provider\") <ins> vs.nodeManager.SetNodeGetter(vs.kubeClient.CoreV1()) </ins> } // Initialize Node Informers", "positive_passages": [{"docid": "doc-en-kubernetes-27c84c169fad17ff032040ca08c7bb73c7215213dd29c5491da1ee415abb2a33", "text": "/assign\n/triage accepted\nI found an easier way how to reproduce this without extra code in KCM: a StatefulSet with 1 Pod that uses 1 PVC. the node where the Pod runs. down kube-controller-manager to zero (not really possible for me) or kill all kube-controller-manager Pods. This will cause new KCM processes to wait for leader election. In my env. this gives me ~30 seconds for the next step. Delete the Pod. A new one will be scheduled on a different node (because the current node is cordoned) + there is no KCM running at this time that would detach the volume from the old node. KCM wins its leader election, sees a volume attached to a node where it is not needed -it calls of the volume plugin. VSphere cloud provider does not have its caches populated yet (= this bug) -the volume is not detached, but returns success.\ndangling attach does not help here. The volume is still attached to the old node even after ~10 minutes. fails with and not with . I can see there is a lot of dangling attach code in the cloud provider, but I did not debug further.", "commid": "kubernetes_issue_117091", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2a8219d4d22c730eb202480a507940396324017f9bfc5340333a6845ed7fbbcc", "query": "return allErrs } <ins> func ValidateNoNewFinalizers(newFinalizers []string, oldFinalizers []string, fldPath *field.Path) field.ErrorList { const newFinalizersErrorMsg string = `no new finalizers can be added if the object is being deleted` allErrs := field.ErrorList{} extra := sets.NewString(newFinalizers...).Difference(sets.NewString(oldFinalizers...)) if len(extra) != 0 { allErrs = append(allErrs, field.Forbidden(fldPath, fmt.Sprintf(\"no new finalizers can be added if the object is being deleted, found new finalizers %#v\", extra.List()))) } return allErrs } </ins> func validateVolumes(volumes []api.Volume, fldPath *field.Path) (sets.String, field.ErrorList) { allErrs := field.ErrorList{}", "positive_passages": [{"docid": "doc-en-kubernetes-fc09a9ef1f5e957552c4803f2a8d5445e8992bd48fceb2f6d692294e4122c44c", "text": "says \"If the deletionTimestamp of the object is non-nil, entries in this list can only be removed.\". can you elucidate if I am assuming this does something different than reality\nThis is garbage collection finalizer field, not the namespace finalizer field that that new field was inspired from On Thursday, September 8, 2016, Tim Hockin wrote:\nI don't parse that - is this not a general-purpose \"refcount\" thing? It seems to work that way, except not as documented\nThis is a general purpose field and it should work like Tim thinks it should work. can you take a look at this when you don't have anything pressing for 1.4?\nThe namespace finalizer should switch to using this field if it is currently doing something else.\nI'm adding validation rule to prevent adding finalizers if deletionTimestamps is set. I'm still investigating why it can't be removed. This bug is strange.\nActually I guess it's a bug. It uses patch, and patch doesn't work on list of simple type, is a list of string.\nYep, it's a bug. I used to remove one finalizer and it worked as expected. I think this is a known bug of , we don't have a way to specify the mergekey of a list of simple type.\nIs there a bug open for this? Frankly, if is going to fail for things like this, we should not be offering it as a feature, or it should use PUT rather than PATCH , Chao Xu wrote:\nCreated cannot use PUT, because it's doing a three way merge (current state, last configuration, current configuration).\nThese are intended for automated use, not human use, so kubectl edit not working is just unfortunate, not a blocker. Although it's really unfortunate that PATCH is so broken. , Chao Xu wrote:\nWhy does need to be 3-way? I don't think that is the semantic a user would expect from an edit operation AT ALL. It certainly surprised ME. WRT automated vs human - if PATCH doesn't work (worse - says it succeeded but didn't) for some class of fields, then PATCH doesn't work, and we should not support it. Full stop. It's going to end up causing someone an outage. These are not necessarily related to this bug, but I'd call them pretty serious flaws.", "commid": "kubernetes_issue_32339", "tokennum": 515}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2a8219d4d22c730eb202480a507940396324017f9bfc5340333a6845ed7fbbcc", "query": "return allErrs } <ins> func ValidateNoNewFinalizers(newFinalizers []string, oldFinalizers []string, fldPath *field.Path) field.ErrorList { const newFinalizersErrorMsg string = `no new finalizers can be added if the object is being deleted` allErrs := field.ErrorList{} extra := sets.NewString(newFinalizers...).Difference(sets.NewString(oldFinalizers...)) if len(extra) != 0 { allErrs = append(allErrs, field.Forbidden(fldPath, fmt.Sprintf(\"no new finalizers can be added if the object is being deleted, found new finalizers %#v\", extra.List()))) } return allErrs } </ins> func validateVolumes(volumes []api.Volume, fldPath *field.Path) (sets.String, field.ErrorList) { allErrs := field.ErrorList{}", "positive_passages": [{"docid": "doc-en-kubernetes-9d31dc444c003a67666d57a34035c70818d4ce333ea6367245ecb1f620bc17fd", "text": ", Daniel Smith wrote:\nDiscussed in real life. PATCH works, it's just that there are certain operations you cannot express using the strategicmerge patch syntax. I was wrong. is building . So perhaps it uses PATCH over PUT due to the efficiency.\nFWIW, I printed out the patch generated by when I removed one finalizer. The patch is empty, i.e., \"{}\".\n, Chao Xu wrote: Well, no, if there are operations that can not be represented, it really DOESN'T work. I still think it should not use PUT, but I bet Brian can prove me wrong.", "commid": "kubernetes_issue_32339", "tokennum": 129}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2a8f5b61bd0aab7ea0c63abc4cbb6d78568fd3eba022578474f83cbf191a028b", "query": "Fail(fmt.Sprintf(format, a...), 1) } <ins> func providerIs(providers ...string) bool { if testContext.Provider == \"\" { Fail(\"testContext.Provider is not defined\") } for _, provider := range providers { if strings.ToLower(provider) == strings.ToLower(testContext.Provider) { return true } } return false } </ins> type podCondition func(pod *api.Pod) (bool, error) func waitForPodCondition(c *client.Client, ns, podName, desc string, condition podCondition) error {", "positive_passages": [{"docid": "doc-en-kubernetes-5702d542be386cac9e4333778515fd94620fcdb52c66d8dfc11487da78971dda", "text": "I noticed while running e2e tests locally that some tests were apparently being incorrectly skipped: I checked, and this is also true for our Jenkins runs. Currently it looks like and have this bug, though only the former actually skips the test, I think. The issue appears to be that the code inside the top-level in these files is being run before the testContext struct is filled out (and before is even called), and so testContext.Provider is empty. I'm not immediately sure what the proper fix is; I'm also worried that there might be other things broken by the fact that these blocks are called before initialization is complete. We also probably investigate if there is a better way to mark these tests as skipped; right now, there's no indication in the test report (, Jenkins test report, etc) that these tests were skipped.\nI merged and which tried to disable these tests for non-{gke,gce} but apparently didn't follow-up and verify that they were still running on our platforms. /cc\nSeems easy enough to fix. I'll have a PR out to fix this before Monday.", "commid": "kubernetes_issue_7008", "tokennum": 242}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2aa3cf97f31440d38d4d0c00bbb273a4d4faf92c1339f01468e6e47e3535e794", "query": "} } <del> var reinvocationMarkerFixture = &corev1.Pod{ ObjectMeta: metav1.ObjectMeta{ Namespace: \"default\", Name:      \"marker\", }, Spec: corev1.PodSpec{ Containers: []v1.Container{{ Name:  \"fake-name\", Image: \"fakeimage\", }}, }, </del> <ins> func newReinvocationMarkerFixture(namespace string) *corev1.Pod { return &corev1.Pod{ ObjectMeta: metav1.ObjectMeta{ Namespace: namespace, Name:      \"marker\", Labels: map[string]string{ \"marker\": \"true\", }, }, Spec: corev1.PodSpec{ Containers: []v1.Container{{ Name:  \"fake-name\", Image: \"fakeimage\", }}, }, } </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-ddb9bacde18c9f97d2ebd4306efde2d358d8075e932023fee86edf729006549a", "text": "Which jobs are failing: Which test(s) are failing: Since when has it been failing: Testgrid link: Reason for failure: Anything else we need to know: /sig api-machinery /assign\n/cc\nwant to take a look at the audit event issue first? I can dig in after that if issues remain.\nyes, I'm looking at the audit event issue now\nactually the failure message suggests that the missing audit log is caused by unexpected admission invocation: I think it's unrelated to auditing Note that there are two tests named \"no reinvocation of webhook B when in-tree or prior webhook mutations\" :( and from the audit log (), it also suggests that the test is hitting a wrong endpoint\nThanks I'll dig in.", "commid": "kubernetes_issue_82693", "tokennum": 163}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2b4b0536535d8a0f536c649427f0f55c17b3d39e2aadba21d4e9b64af94d0939", "query": "InitContainers: []v1.Container{ { Image: image.GetE2EImage(), <del> Name:  podName, </del> <ins> Name:  \"init-container\", </ins> Command: []string{ \"powershell.exe\", \"-Command\",", "positive_passages": [{"docid": "doc-en-kubernetes-e89d62bf4b636217c9a329c55c70299ddc99e1e546e8bf63873df452671a65c2", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: aks-engine-azure-windows-master-containerd-serial-slow Which test(s) are failing: [sig-windows] [Feature:Windows] Kubelet-Stats [Serial] Kubelet stats collection for Windows nodes when running 10 pods should return within 10 seconds Since when has it been failing: Unknown. Testgrid link: Reason for failure: The test spawns 10 pods with the same pod name, which contains multiple containers with the same container name. Because of this, the test fails. Logs: Anything else we need to know:\n/sig windows These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by vllry. \u200d", "commid": "kubernetes_issue_91677", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2b9a330e6d97f060759ca9ef35bc932e46b14df554d862047c444904f4742be9", "query": "MUST succeed. It MUST succeed when deleting the Deployment. release: v1.20 file: test/e2e/apps/deployment.go <ins> - testname: Deployment, status sub-resource codename: '[sig-apps] Deployment should validate Deployment Status endpoints [Conformance]' description: When a Deployment is created it MUST succeed. Attempt to read, update and patch its status sub-resource; all mutating sub-resource operations MUST be visible to subsequent reads. release: v1.22 file: test/e2e/apps/deployment.go </ins> - testname: 'PodDisruptionBudget: list and delete collection' codename: '[sig-apps] DisruptionController Listing PodDisruptionBudgets for all namespaces should list and delete a collection of PodDisruptionBudgets [Conformance]'", "positive_passages": [{"docid": "doc-en-kubernetes-7b39b114e3f8b25c65861c9c397d758891e478151ec492017dfbfbc72cee16e3", "text": "[X] Test PR: kuberenetes/kubernetes [x] Two weeks soak end date: 1 July 2021 [x] Test promotion PR: kubernetes/kubernetes According to this APIsnoop query, there are still some remaining StatefulSet endpoints which are untested. Create a watch to track deployment events. Create a deployment with a static label. Confirm that the pods are running. Get the deployment status. Parse the response and confirm that the deployment status conditions can be listed. Update the deployment status. Confirm via the watch that the status has been updated. Patch the deployment status. Confirm via the watch that the status has been patched. Using an existing as a template for a new for deployment lifecycle test. This query shows the endpoints hit within a short period of running the e2e test If a test with these calls gets merged, test coverage will go up by 1 point This test is also created with the goal of conformance promotion. /sig apps /sig testing /sig architecture /area conformance\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_102258", "tokennum": 359}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2bb6f68add060cca6ac2644e12f14b5033d959c7046e932cba01aca100d8570b", "query": "rc=1 fi <ins> # ensure all generic features are added in alphabetic order lines=$(git grep 'genericfeatures[.].*:' -- pkg/features/kube_features.go) sorted_lines=$(echo \"$lines\" | sort -f) if [[ \"$lines\" != \"$sorted_lines\" ]]; then echo \"Generic features in pkg/features/kube_features.go not sorted\" >&2 echo >&2 echo \"Expected:\" >&2 echo \"$sorted_lines\" >&2 echo >&2 echo \"Got:\" >&2 echo \"$lines\" >&2 rc=1 fi </ins> exit $rc", "positive_passages": [{"docid": "doc-en-kubernetes-6eb9bac2f3074e091af4e33eda553e3139bfcfe5ecf153737d95dc4605072155", "text": "This avoids drift between Kubernetes components and allows for cluster management tools that pass uniform feature gates to all components. xref:\n/assign\nHey I f you stuck anywhere. Please free to involve me in this.", "commid": "kubernetes_issue_121613", "tokennum": 45}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2bca6ee29cb3996a3963a7665ca806b9a92aa874199c2b0dff8bdf5d96e879db", "query": "mu.Unlock() } <ins> if !concreteOp.SkipWaitToCompletion { // SkipWaitToCompletion=false indicates this step has waited for the Pods to be scheduled. // So we reset the metrics in global registry; otherwise metrics gathered in this step // will be carried over to next step. legacyregistry.Reset() } </ins> case *churnOp: var namespace string if concreteOp.Namespace != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-43f40e78041c5b4f7b71fe448bfb25306103aa8e8278b5a81de2f92cd8b688c4", "text": "In the new scheduler performance testing framework, (bool) is provided to benchmark performance of pods created in an \"operator\": (L11 below) However, the initialized Pods created in L5~L7 seem to be also benchmarked, although it doesn't specify . (please see the reproduce steps below). I think it's b/c once scheduler starts, the associated Prometheus artifacts are also up, and it's a single in-memory datastore. So no matter we start to collect the metric in which step, the prometheus data is already up-to-date. In the above workload config, the final data have benchmarked 1500 pods instead of 1000 pods. I guess it won't work either if running in the pod initialization step or not. Unless we manage a breakpoint at the end of each step, and calculate delta histogram for the step that specifies . Pods created in step without are not benchmarked. Apply the following diff: And then run: You will get an output sth. like: /sig scheduling\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nCould you please help confirm if it's an issue?\ncc\nUnfortunately, does not apply for metrics gathered from . As you mentioned. The default gatherer collects all metrics produced by the scheduler. It's the scheduler itself who knows pod specs and would have to decide which pods will get ignored when updating metrics. The question is if computing metrics for a subset of pods processed by the scheduler is a valid use case.\nThis is probably what we want. Is something like that possible ?\nI think being able to absolutely ignore certain pods for metrics is an overkill.\nThe use case is to ignore the pods created in steps that don't specify , so as to collect the Pod metrics create at particular step(s) (). Otherwise, the semantics of option is quite misleading. Nope, that's not the intention. We don't need to target certain pods, like using label selector or whatever. Just as I mentioned, measure pods created at particular steps.", "commid": "kubernetes_issue_99218", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2bca6ee29cb3996a3963a7665ca806b9a92aa874199c2b0dff8bdf5d96e879db", "query": "mu.Unlock() } <ins> if !concreteOp.SkipWaitToCompletion { // SkipWaitToCompletion=false indicates this step has waited for the Pods to be scheduled. // So we reset the metrics in global registry; otherwise metrics gathered in this step // will be carried over to next step. legacyregistry.Reset() } </ins> case *churnOp: var namespace string if concreteOp.Namespace != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-a8b513dba6e655a29138693e1746ea6f16e628420cb4b4aca138e84f0ed453fc", "text": "I would do something like the following: if a step has collectMetrics:false, we wait for them to finish scheduling, and then we take a snapshot of the histogram. Then for the next step that has collectMetrics:true, we take the diff with the latest snapshot to report the results. This might not be perfect, as we don't control if the metrics have finished syncing when we take the snapshot. But I think that's fine. Would doing this be possible? Now, if we have steps that run in parallel, one with collectMetrics:false and another with collectMetrics:true, then this doesn't work. Note that I don't know the details of how the gatherer works.\nThat adheres to what I have in my mind - we can only manage this on client side. I think it's fine. As we are already fetching the \"snapshot\" when pods get scheduled when equals true. True. An alternative is to design the case to be like: the step with to employ Pods that are all unschedulable, and then specify a custom metric \"schedulere2eschedulingdurationseconds[result=\"unschedulable\"]\" to target a particular histogram instead of all histograms (default option) inside a histogramVec. Note this can only be possible when and some subsequent changes get in place.\nWe might just call Histogram.Clear() method which will clear what has been collected so far at the end of phase: Assuming individual phases have no pods in common and each phase can clear metrics without affecting other phases. Though, as said, it will work only for serial case.\nWDYT\nI'm afraid doesn't work. That was my initial thought as well, but no luck. I guess it's b/c, theoretically, we cannot reset a metric on the server side - Promoetheus' model doesn't support this. But let me know if I miss anything.\nThe performance tests assume all the metrics all gathered and accessed in the same binary. As long as that's the case, works.", "commid": "kubernetes_issue_99218", "tokennum": 457}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2bca6ee29cb3996a3963a7665ca806b9a92aa874199c2b0dff8bdf5d96e879db", "query": "mu.Unlock() } <ins> if !concreteOp.SkipWaitToCompletion { // SkipWaitToCompletion=false indicates this step has waited for the Pods to be scheduled. // So we reset the metrics in global registry; otherwise metrics gathered in this step // will be carried over to next step. legacyregistry.Reset() } </ins> case *churnOp: var namespace string if concreteOp.Namespace != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-c977cd9286b4a197ec98b02fe65342de07359c1835b69599916b95554e8a5e53", "text": "We already call in the code:\nThat was my understanding as well, but no luck :( Here is a diff to call in case when \"concreteOp.CollectMetrics\" is false: <details<summaryDiff:</summary<p</p</detailsAnd below is the output - it's still 1500 (500 init pods plus 1000 measured pods) instead of 1000 being benchmarked: <details<summaryOutput:</summary<p</p</details\nAlso, if you run the tests and together, the result proves doesn't work as expected:\nBut I do find a way to fix this: .", "commid": "kubernetes_issue_99218", "tokennum": 136}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2bd3742bf5df1c30813af81abbd4b971968e462ac6f11bdcd10631af66509492", "query": "} func (az *Cloud) getIPForMachine(nodeName types.NodeName) (string, error) { <ins> az.operationPollRateLimiter.Accept() </ins> machine, exists, err := az.getVirtualMachine(nodeName) if !exists { return \"\", cloudprovider.InstanceNotFound", "positive_passages": [{"docid": "doc-en-kubernetes-0f3fba1dceb9c94d1a19ea07536eb93382a47fa8d74b43be2f3310b5be7e4348", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: In certain large cluster scenarios we would like to anticipate kubelet behavior hitting request limits, and backoff in response. E.g., What you expected to happen: This is a request for add'l backoff coverage, so nothing surprising. How to reproduce it (as minimally and precisely as possible): Build a cluster with as many nodes as your subscription will support on azure until kubelet behavior contributes to backend API request limits. Environment: Kubernetes version (use ): and Cloud provider or hardware configuration**: azure OS (e.g. from /etc/os-release): Ubuntu 16.04.2 LTS (Xenial Xerus) Kernel (e.g. ): Linux k8s-pool7--7 4.4.0-83-generic -Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x8664 x8664 x86_64 GNU/Linux Install tools: acs-engine Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig azure", "commid": "kubernetes_issue_48971", "tokennum": 358}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2bee126518a941d4d2be7cffcb625875665c055b56637e5c6dd1b9cf2e5f8e07", "query": "cmd.Flags().DurationVar(&o.drainer.Timeout, \"timeout\", o.drainer.Timeout, \"The length of time to wait before giving up, zero means infinite\") cmd.Flags().StringVarP(&o.drainer.Selector, \"selector\", \"l\", o.drainer.Selector, \"Selector (label query) to filter on\") cmd.Flags().StringVarP(&o.drainer.PodSelector, \"pod-selector\", \"\", o.drainer.PodSelector, \"Label selector to filter pods on the node\") <ins> cmd.Flags().BoolVar(&o.drainer.DisableEviction, \"disable-eviction\", o.drainer.DisableEviction, \"Force drain to use delete, even if eviction is supported. This will bypass checking PodDisruptionBudgets, use with caution.\") </ins> cmdutil.AddDryRunFlag(cmd) return cmd", "positive_passages": [{"docid": "doc-en-kubernetes-1de7ff63e7ce8b64bf52f2105a2efc7375b6d0f9c29fe56834b2956453e0280d", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Allow to have an additional flag (e.g. or ) to allow a to drain pods off a node, even if they violate PodDisruptionBudgets Why is this needed: There are times where you want to drain pods off a node even if violating a PDB. For example, if you are running a one-worker node kubernetes cluster (not minikube), and you want to upgrade it. Or, like me, you are running a test cluster and want to scale down to zero nodes when you're not going to be using the cluster for a while in order to save costs. If that worker node has a deployment with a PDB, then will get stuck as it cannot get rid of the pod while respecting the PDB, which is expected; but in this case, it is a hindrance. Adding the switch will allow users to explicitly acknowledge that they want to ignore the PDBs (and accept the corresponding downtime for an application/service)\n/sig node\n+1\n+1 Our company offers Kubernetes as PaaS. We manage Kubernetes, including IaaS OS updates and if a customer does not specify the PDB correctly, we are not able to drain the node for the OS updates. A flag would be werry helpfull for our use case.\n+1\n/active\nI have created to address this. This is a pretty simple implementation, but I think it achieves the desired results. A suitable workflow would be: 1) Configure you component to use drain as normal 2) After some timeout, run drain with --disable-eviction option.\nI'll wait until the PR is merged and released before testing, but if I understand right, it would require me do this, right? If so, I think it would be better if we did it a different way and have one call, something like this: Where implies that if the drain is still running after this time, switch to the mode without having to call kubectl again\nI think that would require a sizeable refactor or add a great deal of complexity to the code, the same could be achieved with In practical terms, I'm focused on automatic node remediation via destroying the node and getting a new one. The timeout would be very large, the drain library is blocking, so I want it to fail quickly and requeue.", "commid": "kubernetes_issue_83307", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2bee126518a941d4d2be7cffcb625875665c055b56637e5c6dd1b9cf2e5f8e07", "query": "cmd.Flags().DurationVar(&o.drainer.Timeout, \"timeout\", o.drainer.Timeout, \"The length of time to wait before giving up, zero means infinite\") cmd.Flags().StringVarP(&o.drainer.Selector, \"selector\", \"l\", o.drainer.Selector, \"Selector (label query) to filter on\") cmd.Flags().StringVarP(&o.drainer.PodSelector, \"pod-selector\", \"\", o.drainer.PodSelector, \"Label selector to filter pods on the node\") <ins> cmd.Flags().BoolVar(&o.drainer.DisableEviction, \"disable-eviction\", o.drainer.DisableEviction, \"Force drain to use delete, even if eviction is supported. This will bypass checking PodDisruptionBudgets, use with caution.\") </ins> cmdutil.AddDryRunFlag(cmd) return cmd", "positive_passages": [{"docid": "doc-en-kubernetes-b7bae32dd27973078cd1b23d1dbdce25c736eb34a86ee68bc51d78045bb08cfb", "text": "I'm going to be performing the calculation of when it's appropriate to evict/delete outside of the drain library, and I suspect most will be as well, so there's not really a great incentive to do it in the drain library itself IMO.\nThat's all good, I have no issue using the flag as long as does error out and return a non-zero code as expected (there's been a few times where it seems to error out, but still return 0)", "commid": "kubernetes_issue_83307", "tokennum": 105}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2bffd891062c804488e28110e1edec716550273b558a301184448b5dd7fa9f37", "query": "measurePods: 1000 - name: SchedulingMigratedInTreePVs <del> featureGates: CSIMigrationAWS: true </del> workloadTemplate: - opcode: createNodes countParam: $initNodes", "positive_passages": [{"docid": "doc-en-kubernetes-b7b38d259f42f0ebfbd04619ac113fee642398eea52ecd5ecf726aec11aad321", "text": "https://perf- /kind failing-test <!-- If this is a flake, please add: /kind flake --/sig scheduling <!-- Please assign a SIG using: /sig SIG-NAME --\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/cc\nThe goleak check was in\ncc\ncc\nAt least didn't fail with a goroutine leak. It failed because of:\nGood to see it's not a regression. Let me raise a PR to see whether is the only culprit.\nEven if it's not the only culprit, I wouldn't think this is a regression, but rather a consequence of the fact that we didn't use goleak before.\nit's just coincidental gets merged at the same timing of the goleak check PR. In other words, the scheduler perf test would also fail if the goleak PR didn't go in.\nThis can be solved by removing this line", "commid": "kubernetes_issue_116359", "tokennum": 289}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2c07d0ab5e9a372e22f84d08ec61afa76da6d3e9f6807812d9ef5a0a1af7a35b", "query": "import ( goflag \"flag\" <del> \"fmt\" </del> \"math/rand\" \"os\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-0b2213d42768c43adcb1b4f15cf67b8722c82d28c3ec9792f5837d41705eb847", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: kubectl version --client=yes command is giving the following error message. Error message is repeated at the start and the end and also containing programming jargon Error: invalid argument \"yes\" for \"--client\" flag: strconv.ParseBool: parsing \"yes\": invalid syntax Examples: Print the client and server versions for the current context kubectl version Options: --client=false: Client version only (no server required). -o, --output='': One of 'yaml' or 'json'. --short=false: Print just the version number. Usage: kubectl version [flags] [options] Use \"kubectl options\" for a list of global command-line options (applies to all commands). invalid argument \"yes\" for \"--client\" flag: strconv.ParseBool: parsing \"yes\": invalid syntax What you expected to happen: The error message can be improved with one of the two variants invalid argument \"yes\" for \"--client\" flag Examples: Print the client and server versions for the current context kubectl version Options: --client=false: Client version only (no server required). -o, --output='': One of 'yaml' or 'json'. --short=false: Print just the version number. Usage: kubectl version [flags] [options] Use \"kubectl options\" for a list of global command-line options (applies to all commands). (or) Invalid argument \"yes\" for \"--client\" flag How to reproduce it (as minimally and precisely as possible): Run the command kubectl version --client=yes Anything else we need to know?: Environment: Kubernetes version (use ): 1.15 Cloud provider or hardware configuration: AWS OS (e.g: ): Amazon Linux Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig cli\nHi Thanks for posting this issue! It turns out that this duplicate output has been in kubectl, and all the other cli cmds, since . This should be fixed by , and hopefully we can cherry pick it back to at least .", "commid": "kubernetes_issue_79454", "tokennum": 560}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2c208104c97c8b81c50afee1b425609277a1096555ed1595aaade235312d73d1", "query": "//CredentialsManager credentialManager *SecretCredentialManager <ins> nodeLister corelisters.NodeLister nodeGetter coreclients.NodesGetter </ins> // Mutexes registeredNodesLock   sync.RWMutex nodeInfoLock          sync.RWMutex", "positive_passages": [{"docid": "doc-en-kubernetes-b9a7a79272b4f05e986ec052f9f8348c60cffedf2d99a44ddafb98b4101b558f", "text": "I am enabling CSI migration on a vSphere cluster. A node was fully drained, all its Pods are deleted, but just before KCM detaches in-tree vSphere volume volumes from it, KCM restarts. A new KCM starts, sees attached volumes in that are not needed by any Pod on the node and calls vSphere in-tree volume plugin . The in-tree vSphere volume plugin + cloud provider marks the volume as detached right away, without reaching to vCenter API. The volume remains attached forever. I don't think it's related to CSI migration, IMO a regular node drain + KCM restart at the same time can cause the same issue. KCM logs: The in-tree cloud provider has a and from it. It apparently has not processed all nodes at the time A/D controller tries to detach the node. The in-tree vSphere volume plugin + cloud provider detaches the volume in vCenter. That's really tricky, it's very hard / impossible to reproduce on a real cluster. I had to inject errors to Detach() in-tree volume call, so they fail until KCM is restarted. Newly started KCM would detach the volume just fine (no error would be injected there), but marks the volume as detached right away. For the record (and search-ability), the CSI driver that tries to attach the volume to another node complains either: Or: cc It could be somewhat related to , however, not all cases of can be related to KCM restart. As I mentioned above, it's very hard/impossible to synchronize KCM restart with draining a node in a real cluster. <details</details<detailsvSphere 7.0.3 </details<details</details<detailsOpenShift </details<detailsCRI-O </details<details</details\n/sig storage\nTried just moving a Pod between nodes without CSI migration involved + restarting KCM when the volume is still attached to the old node. In-tree volume plugin on the new node says:\n/assign\nWhat CSI driver version and K8s version are you testing with?\nKubernetes is 1.25 and CSI driver is 2.7, still, I think it's not releated to the CSI driver, it's KCM who marks the in-tree volume as detached due to not populated node cache.", "commid": "kubernetes_issue_117091", "tokennum": 517}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2c208104c97c8b81c50afee1b425609277a1096555ed1595aaade235312d73d1", "query": "//CredentialsManager credentialManager *SecretCredentialManager <ins> nodeLister corelisters.NodeLister nodeGetter coreclients.NodesGetter </ins> // Mutexes registeredNodesLock   sync.RWMutex nodeInfoLock          sync.RWMutex", "positive_passages": [{"docid": "doc-en-kubernetes-27c84c169fad17ff032040ca08c7bb73c7215213dd29c5491da1ee415abb2a33", "text": "/assign\n/triage accepted\nI found an easier way how to reproduce this without extra code in KCM: a StatefulSet with 1 Pod that uses 1 PVC. the node where the Pod runs. down kube-controller-manager to zero (not really possible for me) or kill all kube-controller-manager Pods. This will cause new KCM processes to wait for leader election. In my env. this gives me ~30 seconds for the next step. Delete the Pod. A new one will be scheduled on a different node (because the current node is cordoned) + there is no KCM running at this time that would detach the volume from the old node. KCM wins its leader election, sees a volume attached to a node where it is not needed -it calls of the volume plugin. VSphere cloud provider does not have its caches populated yet (= this bug) -the volume is not detached, but returns success.\ndangling attach does not help here. The volume is still attached to the old node even after ~10 minutes. fails with and not with . I can see there is a lot of dangling attach code in the cloud provider, but I did not debug further.", "commid": "kubernetes_issue_117091", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2c3bfb2e0e316e72c114d72f9ff1e63f78b3efac17354a2c188abe1ce908c749", "query": "klog.Errorf(\"cannot convert to *v1.Pod: %v\", t) return } <ins> klog.V(3).Infof(\"delete event for scheduled pod %s/%s \", pod.Namespace, pod.Name) </ins> // NOTE: Updates must be written to scheduler cache before invalidating // equivalence cache, because we could snapshot equivalence cache after the // invalidation and then snapshot the cache itself. If the cache is", "positive_passages": [{"docid": "doc-en-kubernetes-671a12759d851f1b99028bc477360c418e1157a45a2e814ff1c5c1cdd09da36a", "text": "This helps debugging scheduler's behavior, currently we don't have logs that indicate when the scheduler first saw a pod or a node. The log level should be v=3. /sig scheduling /cc\nDo you mean add logging for callbacks in ?\nyes, at least for add and delete events\nSure, I can also give this pr, before tomorrow\n/assign\nWe actually have one v=2 log line for a Node being to the cache's tree: But it's probably good to keep this one.", "commid": "kubernetes_issue_87524", "tokennum": 111}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2c486f7e048f9ef2fb214fc46208e15ec418bdb47e1c7740a61ec01f49576479", "query": "<ins> /* Copyright 2014 Google Inc. All rights reserved. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package cloudcfg import ( \"bytes\" \"encoding/json\" \"reflect\" \"testing\" \"gopkg.in/v1/yaml\" ) func TestYAMLPrinterPrint(t *testing.T) { type testStruct struct { Key        string         `yaml:\"Key\" json:\"Key\"` Map        map[string]int `yaml:\"Map\" json:\"Map\"` StringList []string       `yaml:\"StringList\" json:\"StringList\"` IntList    []int          `yaml:\"IntList\" json:\"IntList\"` } testData := testStruct{ \"testValue\", map[string]int{\"TestSubkey\": 1}, []string{\"a\", \"b\", \"c\"}, []int{1, 2, 3}, } printer := &YAMLPrinter{} buf := bytes.NewBuffer([]byte{}) err := printer.Print([]byte(\"invalidJSON\"), buf) if err == nil { t.Error(\"Error: didn't fail on invalid JSON data\") } jTestData, err := json.Marshal(&testData) if err != nil { t.Fatal(\"Unexpected error: couldn't marshal test data\") } err = printer.Print(jTestData, buf) if err != nil { t.Fatal(err) } var poutput testStruct err = yaml.Unmarshal(buf.Bytes(), &poutput) if err != nil { t.Fatal(err) } if !reflect.DeepEqual(testData, poutput) { t.Error(\"Test data and unmarshaled data are not equal\") } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-51464d59b43813ee63ecd6a7cc1e9bc3f70587ec972f984ff4e8cbc7ca42cbef", "text": "When trying to use against a containerized kubernetes cluster (i.e. deployed following ) I get the following errors: This is simply because the command is missing in the hyperkube container image. I will be creating a PR with a fix shortly.\nmayukh istioctl manifest apply --set profile=demo Detected that your cluster does not support third party JWT authentication. Falling back to less secure first party JWT. See for details. Istio core installed Istiod installed Egress gateways installed Ingress gateways installed Addons installed Installation complete mayukh istio version istio: command not found mayukh kubectl -n istio-system get svc prometheus NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE prometheus ClusterIP 10.101.216.106 <none9090/TCP 20m mayukh kubectl -n istio-system get svc grafana NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE grafana ClusterIP 10.97.41.187 <none3000/TCP 21m mayukh -n istio-system get pod -l app=grafana -o jsonpath='{.items[0]}') 3000:3000 & [1] mayukh Forwarding from 127.0.0.1:3000 -3000 Forwarding from [::1]:3000 -3000 Handling connection for 3000 Handling connection for 3000 E0601 00:12:20. ] an error occurred forwarding 3000 -3000: error forwarding port 3000 to pod 6277818d8d58b0b6d52d07c776f1e930860a60466790efbaf9460a380ea497ad, uid : unable to do port forwarding: socat not found E0601 00:12:20. ] an error occurred forwarding 3000 -3000: error forwarding port 3000 to pod 6277818d8d58b0b6d52d07c776f1e930860a60466790efbaf9460a380ea497ad, uid : unable to do port forwarding: socat not found Handling connection for 3000 E0601 00:12:20. ]", "commid": "kubernetes_issue_17157", "tokennum": 508}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2c486f7e048f9ef2fb214fc46208e15ec418bdb47e1c7740a61ec01f49576479", "query": "<ins> /* Copyright 2014 Google Inc. All rights reserved. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package cloudcfg import ( \"bytes\" \"encoding/json\" \"reflect\" \"testing\" \"gopkg.in/v1/yaml\" ) func TestYAMLPrinterPrint(t *testing.T) { type testStruct struct { Key        string         `yaml:\"Key\" json:\"Key\"` Map        map[string]int `yaml:\"Map\" json:\"Map\"` StringList []string       `yaml:\"StringList\" json:\"StringList\"` IntList    []int          `yaml:\"IntList\" json:\"IntList\"` } testData := testStruct{ \"testValue\", map[string]int{\"TestSubkey\": 1}, []string{\"a\", \"b\", \"c\"}, []int{1, 2, 3}, } printer := &YAMLPrinter{} buf := bytes.NewBuffer([]byte{}) err := printer.Print([]byte(\"invalidJSON\"), buf) if err == nil { t.Error(\"Error: didn't fail on invalid JSON data\") } jTestData, err := json.Marshal(&testData) if err != nil { t.Fatal(\"Unexpected error: couldn't marshal test data\") } err = printer.Print(jTestData, buf) if err != nil { t.Fatal(err) } var poutput testStruct err = yaml.Unmarshal(buf.Bytes(), &poutput) if err != nil { t.Fatal(err) } if !reflect.DeepEqual(testData, poutput) { t.Error(\"Test data and unmarshaled data are not equal\") } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-9a13ac1022f69644bf5dad66fc5e8ceee3107a26196b6aa329c239c5fd026072", "text": "an error occurred forwarding 3000 -3000: error forwarding port 3000 to pod 6277818d8d58b0b6d52d07c776f1e930860a60466790efbaf9460a380ea497ad, uid : unable to do port forwarding: socat not found Handling connection for 3000 Handling connection for 3000", "commid": "kubernetes_issue_17157", "tokennum": 87}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2c688ee6efd2ff9a134420a1a21f92e3db118ca2fef7bf7cff6941cbb3300d1f", "query": "// address is required. if len(spec.ServerAddressByClientCIDRs) == 0 { allErrs = append(allErrs, field.Required(fieldPath.Child(\"serverAddressByClientCIDRs\"), \"\")) <ins> } else { for i, address := range spec.ServerAddressByClientCIDRs { idxPath := fieldPath.Child(\"serverAddressByClientCIDRs\").Index(i) if len(address.ClientCIDR) > 0 { if _, _, err := net.ParseCIDR(address.ClientCIDR); err != nil { allErrs = append(allErrs, field.Invalid(idxPath.Child(\"clientCIDR\"), address.ClientCIDR, fmt.Sprintf(\"must be a valid CIDR: %v\", err))) } } } </ins> } return allErrs }", "positive_passages": [{"docid": "doc-en-kubernetes-9ef34f91f24cf25c8ee57899ba28766272335d7f286e3495efa44b9480fef2d3", "text": "Right now it is possible to add a cluster for which it won't be possible to create a client. For example client-related code does: while validation checks only: cc:\nswitching this to 1.6 as it's too late for 1.5. ok? (please switch it right back if you disagree)\nNot a release blocker for 1.7.\nare you interested in fixing this?\nof course, will do that.\n[MILESTONENOTIFIER] Milestone Removed Important: This issue was missing labels required for the v1.8 milestone for more than 7 days: kind: Must specify exactly one of [, , ]. priority: Must specify exactly one of [, , ]. Removing it from the milestone. <detailsAdditional instructions available <a href=\"\"here</aThe commands available for adding these labels are documented <a href=\"\"here</a</details", "commid": "kubernetes_issue_29911", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2c76c23dce4f095b9ac3be23c0031e80bc759773efd7e7f98457f300159bb0a5", "query": "<del> // +build !cgo !linux </del> <ins> // +build !linux </ins> /* Copyright 2015 The Kubernetes Authors.", "positive_passages": [{"docid": "doc-en-kubernetes-5266c57682848ccf4bbfd7d438a66f7fa505006f21647746bff2e69ab7956c41", "text": "In cluster/saltbase/salt/kube-proxy/kube-proxy.manifest, we have this: But kube-proxy also has a flag. Is there a reason to use the approach instead of using the flag? cc as you wrote the code, in\n/cc who's working on moving kube-proxy to a DaemonSet\nIn general, oomscoreadj is not expected to be directly updated by pods and kubelet is expected to manage it. If kube-proxy runs in the Guaranteed QoS class, then it's OOM score adj will be set to a low number. Until that happens, kube-proxy process may want to be shielded from OOM kills to an extent (this matters only when kube-proxy's memory usage memory request) Meanwhile, it does not make sense to have two means to configure the same thing. I'll let decide which option he prefers and sunset the other option.\nThanks for clarifying. At this point, I prefer to use the built-in flag instead of relying on composing bash commands. Sent for this.", "commid": "kubernetes_issue_51083", "tokennum": 231}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2ca85d83715504c69148862e000f0e6c6890aad388519e5b7fd20dbb70a38b1d", "query": "CPU utilization for the pod will not be defined and the autoscaler will not take any action. Further details of the autoscaling algorithm are given [here](../design/horizontal-pod-autoscaler.md#autoscaling-algorithm). <ins> Autoscaler uses heapster to collect CPU utilization. Therefore, it is required to deploy heapster monitoring in your cluster for autoscaling to work. </ins> Autoscaler accesses corresponding replication controller or deployment by scale sub-resource. Scale is an interface which allows to dynamically set the number of replicas and to learn the current state of them. More details on scale sub-resource can be found [here](../design/horizontal-pod-autoscaler.md#scale-subresource).", "positive_passages": [{"docid": "doc-en-kubernetes-0f2f59a4098799df231d0f4ddd6804f8b020392d4e4aa17c98fa7a6b4bb4eccd", "text": "The heapster needs to be installed if end user want to use autoscaler feature, we should mention this in document.", "commid": "kubernetes_issue_17466", "tokennum": 25}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2cbc5b3a3d15907e7beeb65f6a563557026cd29c13530fd9bbb978cd4d120897", "query": "func prepareSubpathTarget(mounter Interface, subpath Subpath) (bool, string, error) { // Early check for already bind-mounted subpath. bindPathTarget := getSubpathBindTarget(subpath) <del> notMount, err := IsNotMountPoint(mounter, bindPathTarget) </del> <ins> notMount, err := mounter.IsNotMountPoint(bindPathTarget) </ins> if err != nil { if !os.IsNotExist(err) { return false, \"\", fmt.Errorf(\"error checking path %s for mount: %s\", bindPathTarget, err)", "positive_passages": [{"docid": "doc-en-kubernetes-4bcfc015d2b9d9fa1e84475a3e08fb9ef8299b4e5f821f790188ad7bdae6ecbc", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: There's , and . The former is used by local and nfs volume plugins, while the latter is used by , which is also used by local and nfs volume plugins. What you expected to happen: Can we consolidate these? This is really confusing and could easily be the source of bugs. <!-- DO NOT EDIT BELOW THIS LINE --/kind cleanup\ncc\n/assign I'd like to clean up code.", "commid": "kubernetes_issue_72387", "tokennum": 133}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2cbdc2cb78a46a7d12cb3538e974c6cb788416578d6cab74feb697579cfae0bc", "query": "[[constraint]] name = \"github.com/modern-go/reflect2\" <del> version = \"1.0.0\" </del> <ins> version = \"1.0.1\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-0d085a3ee589d9a38ade8c650d9534110265a809ec41b82f41ce81cebea870e6", "text": "is a library yet is is instead of release tag. Please consider vendoring by tag whenever possible. Thanks.\nWe vendored it that way because the commit that fixed a bug (which we needed to be fixed and vendored back in) was This was merged on June 13. The release 1.1.4 () was released on July 1. If we want to update it to 1.1.4, I believe it should be fine. Between the commit we have vendored right now and the latest release, there are only three commits: adds tests merges (?) the case-sensitive fix - I'm not really sure what this commit is doing. fixes renaming when naming strategy is set (looks fine). Also, there are also no licensing changes. opinions?\n/sig api-machinery\n+1 to what said, it was a fire drill and 1.11.0 release was in trouble. Though in hind sight, we should have opened a issue to track that. something better to do next time. cc\nI'm indifferent to updating this. I'm okay with moving up if it doesn't break anything, or I'm fine with leaving things as is. We don't require deps to match semver. We can version out any commit in a deps tree, as we rely on our vendored copy.\nIt is always a good idea to match semver and it should be a default policy. Even if it doesn't matter to you, it should, because it is a best practice. Moreover downstream it matters much more as dependencies may be un-vendored in favour of tested re-usable packages.\n/cc\nIssues 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\nSomeone please take care of this or bot will eventually close this valid issue without action...\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_66422", "tokennum": 501}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2cbdc2cb78a46a7d12cb3538e974c6cb788416578d6cab74feb697579cfae0bc", "query": "[[constraint]] name = \"github.com/modern-go/reflect2\" <del> version = \"1.0.0\" </del> <ins> version = \"1.0.1\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-3d634ec524d1253e3e5f3f0b99b6d74925e6b15b79d6d989e49b255bf837eee0", "text": "/lifecycle rotten\n/lifecycle rotten\n/remove-lifecycle rotten PR open (thanks,\noops! sorry, I meant to remove it. thanks!\nThanks.\nplease do feel free to open issues/prs of this sort early in the release cycle, so we can work through things needed well before the milestones/freeze etc. we are getting some heat about updating dependencies and we kind of settled on some guidelines here: if you think that needs updating, we could definitely debate that as well :) (on a PR against that doc)\nit have nothing to do with release cycle or justification for upgrade if/when dependency has been vendored incorrectly. It is basically a vendoring bug. No debate is necessary although that kind of issues usually meet some resistance and even hostility here... Bugs are filed when they are discovered, regardless of release cycle. It would be wrong to sit on the bug without reporting it in order to synchronise with release cycle.", "commid": "kubernetes_issue_66422", "tokennum": 200}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2cf7a7938161786550a8a4b636fc5d4c20ddad13464a0c5da2fc3af4ce8d640f", "query": "\"description\": \"ServicePort contains information on service's port.\", \"properties\": { \"appProtocol\": { <del> \"description\": \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and http://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.\", </del> <ins> \"description\": \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.\", </ins> \"type\": \"string\" }, \"name\": {", "positive_passages": [{"docid": "doc-en-kubernetes-3e7e95e6f142ca39e6e3ca0b78c3932bd6cbdfdc898eed9d3ffda27d28f904c7", "text": "We should make the change in PR API reference links to should use HTTPS, not HTTP Visit h and look at the IANA hyperlinks Once this fix is made, a PR to is needed to update the docs (by autogenerating them). This typically would be deferred until the next Kubernetes release. v1.23 not applicable not applicable not applicable not applicable not applicable\n/sig docs\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI opened this issue so that someone else can open a new PR that is equivalent to .\n/retitle Update links to IANA for Service Name and Transport Protocol Port Number Registry\nI would like to work on this issue. May I assign it to myself?\nAnyone - including you - is welcome to work on this issue! So long as you've you can open a pull request to propose a fix.\nThanks\n/assign\nI have made the PR. I hope this works. If not then will be happy to do the necessary changes.\nHad to close the previous PR because of issues, here is the new one I made.", "commid": "kubernetes_issue_106980", "tokennum": 300}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2d272a10f8bb4ac3456171cc46fd3faad0e2283dbf796295360d8f3472fb1a0b", "query": "CreateTCPLoadBalancer(name, region string, externalIP net.IP, ports []int, hosts []string, affinityType api.AffinityType) (string, error) // UpdateTCPLoadBalancer updates hosts under the specified load balancer. UpdateTCPLoadBalancer(name, region string, hosts []string) error <del> // DeleteTCPLoadBalancer deletes a specified load balancer. DeleteTCPLoadBalancer(name, region string) error </del> <ins> // EnsureTCPLoadBalancerDeleted deletes the specified load balancer if it // exists, returning nil if the load balancer specified either didn't exist or // was successfully deleted. // This construction is useful because many cloud providers' load balancers // have multiple underlying components, meaning a Get could say that the LB // doesn't exist even if some part of it is still laying around. EnsureTCPLoadBalancerDeleted(name, region string) error </ins> } // Instances is an abstract, pluggable interface for sets of instances.", "positive_passages": [{"docid": "doc-en-kubernetes-9fca6378f8b8df6d20b226b62d39deddc0dd6ba6166f0f70fb99239f64c63f5d", "text": "All of our external load balancer tests failed for the better part of a day due to the GCE project that our tests run in hitting its quota for number of target pools. While the target pools have been deleted, the fact that we hit our quota indicates that there must be a leak somewhere, and we need to plug it.\nFor reference, the previous issue was\nCould the leakage be related to ? The quota exhaustion occurred about 22 hrs after that.\nI'd guess that this is due to GetTCPLoadBalancer returning that the load balancer doesn't exist if the forwarding rule is gone, ignoring the target pool, while the service controller considers its deleting done if the cloud provider says that the load balancer doesn't exist. I that logic to the cloud provider because the other implementations of DeleteTCPLoadBalancer weren't/won't be idempotent in the sense of returning ok if the LB doesn't exist. To fix it, we'll either need to make sure all Delete implementations are idempotent and remove the Get call in the controller, or add a method along the lines of IsTCPLoadBalancerDeleted to ask the cloud provider whether all pieces of it have been completely cleaned up. We can't make GetTCPLoadBalancer check that because it's relied on to tell us whether or not the balancer is fully created.\nCopying over my commentary from on why the GKE e2e tests are leaking so many forwarding rules and target pools vs the GCE tests:\nIs there a way for the services test to wait for the service controller to clean up the external resources before finishing (without just doing a sleep)?\nNot without polling GCE directly for whether the resources still exist, although that may be worth it as a workaround. What would be perfect is that clean-up-all-cloud-provider-resources API method that we talked about a couple months ago.\nCan we not perhaps use GCE namespaces or projects as a cheap way of getting this here?\nI don't believe so. We can't use projects due to the fact that projects can't be programatically created (they're intended to be long-lived). I'm not aware of anything along the lines of a GCE namespace other than networks, which won't work because target pools and forwarding rules unfortunately don't seem to be scoped to networks.", "commid": "kubernetes_issue_7753", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2d272a10f8bb4ac3456171cc46fd3faad0e2283dbf796295360d8f3472fb1a0b", "query": "CreateTCPLoadBalancer(name, region string, externalIP net.IP, ports []int, hosts []string, affinityType api.AffinityType) (string, error) // UpdateTCPLoadBalancer updates hosts under the specified load balancer. UpdateTCPLoadBalancer(name, region string, hosts []string) error <del> // DeleteTCPLoadBalancer deletes a specified load balancer. DeleteTCPLoadBalancer(name, region string) error </del> <ins> // EnsureTCPLoadBalancerDeleted deletes the specified load balancer if it // exists, returning nil if the load balancer specified either didn't exist or // was successfully deleted. // This construction is useful because many cloud providers' load balancers // have multiple underlying components, meaning a Get could say that the LB // doesn't exist even if some part of it is still laying around. EnsureTCPLoadBalancerDeleted(name, region string) error </ins> } // Instances is an abstract, pluggable interface for sets of instances.", "positive_passages": [{"docid": "doc-en-kubernetes-d79b213781c20847fbb47c058c0afaba60ed2f1d9f5b51e77a0a4cda944c52e0", "text": "The target pool leak in the code might be fixed, but the forwarding rule + target pool leak from deleting GKE clusters too quickly is certainly still happening. Reopening for the sake of that half of the issue.\nCan we just add a short sleep to jenkins after the last test has run before it deletes anything?\nYes, you could add a sleep to Ginkgo's AfterEachSuite(): But I'd be concerned about what the upper bound on the sleep period is. Can we get the tests and code in sync with a 1 minute latency here? (e.g. if the controller garbage collects every 60 seconds, then the test only needs to sleep for 60 sec?) And add a BEEG comment to the test's sleep config noting that increasing the sleep time will not improve things, otherwise I'm pretty sure that someone noting flakes in this test in future will think \"maybe I should just increase the sleep period a little bit.\"\nActually, thinking about this a little more, it would be better to put the \"sleep\" logic in the k8s master teardown procedure (i.e. not in the e2e tests or in Jenkins), because otherwise users are going to run into the same resource leakage problems as we are. So master deletion blocks on cleanup of backend cloud resources.\nThere's no way to block master deletion from the master itself. The test framework (or user) just pulls the rug out from underneath the master. See\nRobby's right -- is the real solution to this, but until we have that the best we can do is to have the wait happen elsewhere. The options seem to be: GKE itself Ginkgo's post-testing logic Jenkins' teardown logic I don't like putting it in GKE, because arbitrarily slowing down our API makes for a poor experience for the majority of people that don't still have resources being deleted. I'm not eager to put it in Gingko either, since won't that sleep also take effect whenever anyone runs an e2e test locally against a dev cluster? Putting it in the Jenkins logic makes the most sense to me. I'll send a PR and cc you.\nWe may also want to change the kube-down logic to bring down the master and then nodes in parallel to both speed it up and more closely resemble GKE's teardown logic.\nI've deleted the old forwarding rules and target pools from the project.", "commid": "kubernetes_issue_7753", "tokennum": 530}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2d272a10f8bb4ac3456171cc46fd3faad0e2283dbf796295360d8f3472fb1a0b", "query": "CreateTCPLoadBalancer(name, region string, externalIP net.IP, ports []int, hosts []string, affinityType api.AffinityType) (string, error) // UpdateTCPLoadBalancer updates hosts under the specified load balancer. UpdateTCPLoadBalancer(name, region string, hosts []string) error <del> // DeleteTCPLoadBalancer deletes a specified load balancer. DeleteTCPLoadBalancer(name, region string) error </del> <ins> // EnsureTCPLoadBalancerDeleted deletes the specified load balancer if it // exists, returning nil if the load balancer specified either didn't exist or // was successfully deleted. // This construction is useful because many cloud providers' load balancers // have multiple underlying components, meaning a Get could say that the LB // doesn't exist even if some part of it is still laying around. EnsureTCPLoadBalancerDeleted(name, region string) error </ins> } // Instances is an abstract, pluggable interface for sets of instances.", "positive_passages": [{"docid": "doc-en-kubernetes-6b81898435dc239c0c98669b4836ce5b1423be788127f142aa9eb15c198137cf", "text": "I'll periodically check to see whether anything is leaked after this point. I apologize if the deletions affected any running tests - everything looked to only be from GKE and parallel e2e runs.", "commid": "kubernetes_issue_7753", "tokennum": 42}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2d2f1c2619fff3273edbe63acf0a168664d71b4b9ebe1918b1f536f5933f7fed", "query": "command: - /bin/sh - -c <del> - echo -998 > /proc/$$$/oom_score_adj && kube-proxy {{kubeconfig}} {{cluster_cidr}} --resource-container=\"\" {{params}} 1>>/var/log/kube-proxy.log 2>&1 </del> <ins> - kube-proxy {{kubeconfig}} {{cluster_cidr}} --resource-container=\"\" --oom-score-adj=-998 {{params}} 1>>/var/log/kube-proxy.log 2>&1 </ins> {{container_env}} {{kube_cache_mutation_detector_env_name}} {{kube_cache_mutation_detector_env_value}}", "positive_passages": [{"docid": "doc-en-kubernetes-5266c57682848ccf4bbfd7d438a66f7fa505006f21647746bff2e69ab7956c41", "text": "In cluster/saltbase/salt/kube-proxy/kube-proxy.manifest, we have this: But kube-proxy also has a flag. Is there a reason to use the approach instead of using the flag? cc as you wrote the code, in\n/cc who's working on moving kube-proxy to a DaemonSet\nIn general, oomscoreadj is not expected to be directly updated by pods and kubelet is expected to manage it. If kube-proxy runs in the Guaranteed QoS class, then it's OOM score adj will be set to a low number. Until that happens, kube-proxy process may want to be shielded from OOM kills to an extent (this matters only when kube-proxy's memory usage memory request) Meanwhile, it does not make sense to have two means to configure the same thing. I'll let decide which option he prefers and sunset the other option.\nThanks for clarifying. At this point, I prefer to use the built-in flag instead of relying on composing bash commands. Sent for this.", "commid": "kubernetes_issue_51083", "tokennum": 231}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2d4b1c492aed525ad82d7b35b3ee48579c3b9e6eb2ab5a645b0c66cc8532e57b", "query": "}) /* <del> Testname: allowPrivilegeEscalation=false. Description: Configuring the allowPrivilegeEscalation to false, does not allow the privilege escalation operation. A container is configured with allowPrivilegeEscalation=false and a given uid (1000) which is not 0. When the container is run, the container is run using uid=1000. This test is marked LinuxOnly since Windows does not support running as UID / GID, or privilege escalation. </del> <ins> Release : v1.15 Testname: Security Context, allowPrivilegeEscalation=false. Description: Configuring the allowPrivilegeEscalation to false, does not allow the privilege escalation operation. A container is configured with allowPrivilegeEscalation=false and a given uid (1000) which is not 0. When the container is run, container's output MUST match with expected output verifying container ran with given uid i.e. uid=1000. [LinuxOnly]: This test is marked LinuxOnly since Windows does not support running as UID / GID, or privilege escalation. </ins> */ <del> It(\"should not allow privilege escalation when false [LinuxOnly] [NodeConformance]\", func() { </del> <ins> framework.ConformanceIt(\"should not allow privilege escalation when false [LinuxOnly] [NodeConformance]\", func() { </ins> podName := \"alpine-nnp-false-\" + string(uuid.NewUUID()) apeFalse := false if err := createAndMatchOutput(podName, \"Effective uid: 1000\", &apeFalse, 1000); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-f8a45a347ca0a58053d8639059bb6be0a8ec66e1196dbd0290c02922abc9dcd2", "text": "/kind cleanup /area conformance /area test /sig node /sig testing /sig architecture /assign /assign We have a number of tests that only have the tag that may make sense as tests, we should identify whether these tests cases meet (or could meet) the . We should open PR's to promote these if so. I would advise starting with the test/common cases\nGitHub didn't allow me to assign the following users: mgdevstack, mkurylec. Note that only and repo collaborators can be assigned. For more information please see <detailsIn response to : /kind cleanup /area conformance /area test /sig node /sig testing /sig architecture /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\n/assign\nThe tests in test/e2enode don't actually get run as part of Conformance as near as I can tell. If we want to run them as part of conformance, they need to be migrated into test/e2e/common. Some of the tests in e2enode may not be able to be ported over because they assume a level access we don't have in a conformance environment.\nregarding this testcase: [sig-storage] HostPath should support r/w [NodeConformance]: It uses hostPath and privileged=true, to read/write from /tmp folder. Which would you suggest is the best orientation to overcome the privilege mode setting and allow its promotion?\n/assign\nRegarding , the suite runs the test only if the kubelet configuration was required to have the QOS (cgroups-per-qos) enabled. This configuration for the kubelet is selected at the time the cluster is set up. Looking for where this might be configured found: where is set to true. For other settings it is also configured to true. where is set to true. BUT also found where it is mentioned that the flag is no longer available. Questions: would it be ok to promote this test to be conformance, even it can be skipped based on configuration of the cluster? And not supported in the containerized kubelet?\nI would consider cgroups to be an implementation detail that Conformance shouldn't be verifying\nIt uses hostPath and privileged=true, to read/write from /tmp folder.", "commid": "kubernetes_issue_66875", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2d4b1c492aed525ad82d7b35b3ee48579c3b9e6eb2ab5a645b0c66cc8532e57b", "query": "}) /* <del> Testname: allowPrivilegeEscalation=false. Description: Configuring the allowPrivilegeEscalation to false, does not allow the privilege escalation operation. A container is configured with allowPrivilegeEscalation=false and a given uid (1000) which is not 0. When the container is run, the container is run using uid=1000. This test is marked LinuxOnly since Windows does not support running as UID / GID, or privilege escalation. </del> <ins> Release : v1.15 Testname: Security Context, allowPrivilegeEscalation=false. Description: Configuring the allowPrivilegeEscalation to false, does not allow the privilege escalation operation. A container is configured with allowPrivilegeEscalation=false and a given uid (1000) which is not 0. When the container is run, container's output MUST match with expected output verifying container ran with given uid i.e. uid=1000. [LinuxOnly]: This test is marked LinuxOnly since Windows does not support running as UID / GID, or privilege escalation. </ins> */ <del> It(\"should not allow privilege escalation when false [LinuxOnly] [NodeConformance]\", func() { </del> <ins> framework.ConformanceIt(\"should not allow privilege escalation when false [LinuxOnly] [NodeConformance]\", func() { </ins> podName := \"alpine-nnp-false-\" + string(uuid.NewUUID()) apeFalse := false if err := createAndMatchOutput(podName, \"Effective uid: 1000\", &apeFalse, 1000); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-b0f7522fd47a7c9f3d30009b5f18d7b37ba2aa8723a4c0ef112b90078054f0fc", "text": "Which would you suggest is the best orientation to overcome the privilege mode setting and allow its promotion? Michelle Au If my understanding is correct, on some platforms, writing to /tmp requires privileged. I don't see a way to to remove that requirement.\nIf my understanding is correct, on some platforms, writing to /tmp requires privileged. I don't see a way to to remove that requirement. Yeah writing to host doesn't seem like a thing we can expect of conformance tests. I wonder if it makes sense to tag this test with something to denote the requirement, ie: I see some tests in test/e2e_node use\nThe hostpath tests in already have a comment explaining this. Maybe the comment should be updated to be more clear that that is the reason why we can't add it to conformance.\nThat's /tmp on the host or in the container filesystem?\n/tmp on the host\nping what else remains to be done before we close this out? I am guessing that we want to close , is there anything beyond that?\nOnce tests under (issue- ) and are promoted we are good to close this issue. Short update for reference- None of [NodeConformance] tests from \"test/e2e_node\" seems eligible for [Conformance] promotion at this moment due to node level dependencies. Remaining [NodeConformance] tests from \"test/e2e\" has following status - Waiting for to be closed and then below tests would be promoted to Conformance Needs to be Promoted Can not be promoted to Conformance as //Slow by design Can not be promoted due to Node level dependency\nIssues 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\n/remove-lifecycle stale\n/lifecycle frozen\n/assign", "commid": "kubernetes_issue_66875", "tokennum": 428}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2d4c0fbb30abe3949169075e589c8289a804000ef8b9336c980b3271b6c6745a", "query": "t.Run(test.name, func(t *testing.T) { serviceName := types.NamespacedName{Namespace: \"default\", Name: \"myservice\"} <del> sgList, err := c.buildELBSecurityGroupList(serviceName, \"aid\", test.extraSGsAnnotation) </del> <ins> sgList, err := c.buildELBSecurityGroupList(serviceName, \"aid\", test.annotations) </ins> assert.NoError(t, err, \"buildELBSecurityGroupList failed\") extraSGs := sgList[1:] assert.True(t, sets.NewString(test.expectedSGs...).Equal(sets.NewString(extraSGs...)),", "positive_passages": [{"docid": "doc-en-kubernetes-f0769863fab39b633cda95f4d162dbe6bf42638a791c88a2a3acb41bb68633b3", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature /sig aws What happened: In k8s 1.7, when creating a service of type LoadBalancer, K8S creates the ELB and a Security Group for it. For these resources, it adds a tag, constructed dynamically, containing the cluster id: \"${cluster_id}\" with the value \"true\" What you expected to happen: We'd like to have also a statically named tag , as it was in 1.5 (\"KubernetesCluster\") with the value of the cluster id. How to reproduce it (as minimally and precisely as possible): Running on AWS cloud provider, create a service of type LoadBalancer. Anything else we need to know?: The reason for what we expect is that we have tight security constraints that require us to fine tune the IAM policies for the Instance profiles that the controllers use. With a statically named tag we were able, in 1.5, to restrict the permissions in the IAM policy to act only on the k8s managed resources (ELBs, security groups). Here is the relevant part of the IAM policy: With a dynamically named tag we are not able to do this any more as AWS IAM doesn't support something like: We are sharing the Instance Profiles among different k8s clusters, hence the \"\" in the value of the tag. Environment: Kubernetes version (use ):Cloud provider or hardware configuration*: AWS OS (e.g. from /etc/os-release):Kernel (e.g. ):Install tools: kube-aws Others:\nReiterating the mentions to trigger a notification: <detailsIn response to : <!-- This form is for bug reports and feature requests ONLY! -- /sig aws In k8s 1.7, when creating a service of type LoadBalancer, K8S creates the ELB and a Security Group for it. For these resources, it adds a tag, constructed dynamically, containing the cluster id: \"${cluster_id}\" with the value \"true\" We'd like to have also a statically named tag , as it was in 1.5 (\"KubernetesCluster\") with the value of the cluster id. Running on AWS cloud provider, create a service of type LoadBalancer.", "commid": "kubernetes_issue_53489", "tokennum": 543}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2d4c0fbb30abe3949169075e589c8289a804000ef8b9336c980b3271b6c6745a", "query": "t.Run(test.name, func(t *testing.T) { serviceName := types.NamespacedName{Namespace: \"default\", Name: \"myservice\"} <del> sgList, err := c.buildELBSecurityGroupList(serviceName, \"aid\", test.extraSGsAnnotation) </del> <ins> sgList, err := c.buildELBSecurityGroupList(serviceName, \"aid\", test.annotations) </ins> assert.NoError(t, err, \"buildELBSecurityGroupList failed\") extraSGs := sgList[1:] assert.True(t, sets.NewString(test.expectedSGs...).Equal(sets.NewString(extraSGs...)),", "positive_passages": [{"docid": "doc-en-kubernetes-a01a3c41e631760f28b69af73c7e0688234151a20f7dd4b67642a3c81f6b4dfa", "text": "The reason for what we expect is that we have tight security constraints that require us to fine tune the IAM policies for the Instance profiles that the controllers use. With a statically named tag we were able, in 1.5, to restrict the permissions in the IAM policy to act only on the k8s managed resources (ELBs, security groups). Here is the relevant part of the IAM policy: Environment: Kubernetes version (use ):OS (e.g. from /etc/os-release):Others: </details\nI believe they are moving away from the tag since there are many resources that can be shared by multiple clusters. could you use an annotation?\nWe removed the condition in roles in the end. Thank you for your suggestion.\nThat annotation affects the ELB but not any security groups that are created. can you please reopen this? You reported a real issue, and even if it no longer affects you, it needs to be tracked and fixed.\nIndeed, this might be a feature that someone else would need.\nIn fact, this is a feature I need!\nFood for thought: should we propagate the tags on the ELB to the SG, or should we introduce an annotation for the SG specifically?", "commid": "kubernetes_issue_53489", "tokennum": 265}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2d58bc425e2c158b9a2a1b143d0008a67bce2cf5e3f56952a0161b818d90418a", "query": "// are set to 0. func completeRollingUpdate(set *apps.StatefulSet, status *apps.StatefulSetStatus) { if set.Spec.UpdateStrategy.Type == apps.RollingUpdateStatefulSetStrategyType && <del> status.UpdatedReplicas == status.Replicas && status.ReadyReplicas == status.Replicas { </del> <ins> status.UpdatedReplicas == *set.Spec.Replicas && status.ReadyReplicas == *set.Spec.Replicas && status.Replicas == *set.Spec.Replicas { </ins> status.CurrentReplicas = status.UpdatedReplicas status.CurrentRevision = status.UpdateRevision }", "positive_passages": [{"docid": "doc-en-kubernetes-cbff279a5a2209254c6527f41e3183737e33b6607a7e6fb4945b04f53611a022", "text": "My application is clustered and I have 2 pods running. I am using a rolling upgrade strategy and my partitioning number is 1. First I need to upgrade the pod with the ordinal number 1 so I triggered that upgrade with partitioning number 1 and my upgrade gets completed. After this, my pod having the ordinal number 0 gets restarted and it's automatically upgraded to a new image. This is not an expected behavior because still, my partition number is 1 and pod-0 should come up with an older image only. I am facing this issue for the v1.27 cluster. Prior to this, it was working fine. pod-0 should not upgrade to new image until I upgrade the partition number to 0.a Do helm install and upgrade pod-1 only keeping partition number to 1. No response <detailsconsole $ cat /etc/os-release $ uname -a C:wmic os get Caption, Version, BuildNumber, OSArchitecture </details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig/api-machinery\n/sig apps /sig storage\nHi, Can someone suggest here? As this is introduced in my setup after the v1.27 upgrade? Is there any change in partition logic?\nThis can be reproduced by using the said STS. 1 - Deploy STS using attached that has a replica count is 2 and updatingstrategy.rolling.partition as 1. 2 - Do edit STS and update the image to 1.15. This will upgrade, pod-1 with image 1.15. 3 - Next delete the pod pod-0 and check that POD-0 came up with a new image which is not the expected behavior. POD 0 should not be updated to a new image until the partition is changed to 0. We have noticed this behavior change in v1.27.", "commid": "kubernetes_issue_119685", "tokennum": 476}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2d58bc425e2c158b9a2a1b143d0008a67bce2cf5e3f56952a0161b818d90418a", "query": "// are set to 0. func completeRollingUpdate(set *apps.StatefulSet, status *apps.StatefulSetStatus) { if set.Spec.UpdateStrategy.Type == apps.RollingUpdateStatefulSetStrategyType && <del> status.UpdatedReplicas == status.Replicas && status.ReadyReplicas == status.Replicas { </del> <ins> status.UpdatedReplicas == *set.Spec.Replicas && status.ReadyReplicas == *set.Spec.Replicas && status.Replicas == *set.Spec.Replicas { </ins> status.CurrentReplicas = status.UpdatedReplicas status.CurrentRevision = status.UpdateRevision }", "positive_passages": [{"docid": "doc-en-kubernetes-78482ca8aa8474337677389890aeefe9bf7c97cdeab333d3d2b330616683b55b", "text": "Pla suggest : apiVersion: v1 kind: Service metadata: name: nginx labels: app: nginx spec: ports: port: 80 name: web clusterIP: None selector: app: nginx apiVersion: apps/v1 kind: StatefulSet metadata: name: web-am spec: updateStrategy: type: RollingUpdate rollingUpdate: partition: 1 serviceName: \"nginx\" replicas: 2 selector: matchLabels: app: nginx template: metadata: labels: app: nginx spec: containers: name: nginx args: /bin/sh -c sleep 30;touch /tmp/healthy; sleep 3600 image: nginx:1.14.2 ports: containerPort: 80 name: web", "commid": "kubernetes_issue_119685", "tokennum": 170}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2da9c5047ff5958a2b240aa981775e40454a467efe67e42c43d9035ad7a47260", "query": "}) }) <del> Context(\"when pod using local volume with non-existant path\", func() { ep := &eventPatterns{ reason:  \"FailedMount\", pattern: make([]string, 2)} ep.pattern = append(ep.pattern, \"MountVolume.SetUp failed\") ep.pattern = append(ep.pattern, \"does not exist\") It(\"should not be able to mount\", func() { testVol := &localTestVolume{ node:            config.node0, hostDir:         \"/non-existent/location/nowhere\", localVolumeType: testVolType, } By(\"Creating local PVC and PV\") createLocalPVCsPVs(config, []*localTestVolume{testVol}, testMode) pod, err := createLocalPod(config, testVol) Expect(err).To(HaveOccurred()) checkPodEvents(config, pod.Name, ep) verifyLocalVolume(config, testVol) cleanupLocalPVCsPVs(config, []*localTestVolume{testVol}) }) }) </del> <ins> }) } </ins> <del> Context(\"when pod's node is different from PV's NodeAffinity\", func() { </del> <ins> Context(\"when local volume cannot be mounted [Slow]\", func() { // TODO: // - make the pod create timeout shorter // - check for these errors in unit tests intead It(\"should fail mount due to non-existant path\", func() { ep := &eventPatterns{ reason:  \"FailedMount\", pattern: make([]string, 2)} ep.pattern = append(ep.pattern, \"MountVolume.SetUp failed\") ep.pattern = append(ep.pattern, \"does not exist\") testVol := &localTestVolume{ node:            config.node0, hostDir:         \"/non-existent/location/nowhere\", localVolumeType: DirectoryLocalVolumeType, } By(\"Creating local PVC and PV\") createLocalPVCsPVs(config, []*localTestVolume{testVol}, immediateMode) pod, err := createLocalPod(config, testVol) Expect(err).To(HaveOccurred()) checkPodEvents(config, pod.Name, ep) verifyLocalVolume(config, testVol) cleanupLocalPVCsPVs(config, []*localTestVolume{testVol}) }) </ins> <del> BeforeEach(func() { if len(config.nodes) < 2 { framework.Skipf(\"Runs only when number of nodes >= 2\") } }) </del> <ins> It(\"should fail mount due to wrong node\", func() { if len(config.nodes) < 2 { framework.Skipf(\"Runs only when number of nodes >= 2\") } </ins> <del> ep := &eventPatterns{ reason:  \"FailedScheduling\", pattern: make([]string, 2)} ep.pattern = append(ep.pattern, \"MatchNodeSelector\") ep.pattern = append(ep.pattern, \"VolumeNodeAffinityConflict\") </del> <ins> ep := &eventPatterns{ reason:  \"FailedMount\", pattern: make([]string, 2)} ep.pattern = append(ep.pattern, \"NodeSelectorTerm\") ep.pattern = append(ep.pattern, \"MountVolume.NodeAffinity check failed\") </ins> <del> It(\"should not be able to mount due to different NodeAffinity\", func() { testPodWithNodeName(config, testVolType, ep, config.nodes[1].Name, makeLocalPodWithNodeAffinity, testMode) }) </del> <ins> testVols := setupLocalVolumesPVCsPVs(config, DirectoryLocalVolumeType, config.node0, 1, immediateMode) testVol := testVols[0] </ins> <del> It(\"should not be able to mount due to different NodeSelector\", func() { testPodWithNodeName(config, testVolType, ep, config.nodes[1].Name, makeLocalPodWithNodeSelector, testMode) }) </del> <ins> pod := makeLocalPodWithNodeName(config, testVol, config.nodes[1].Name) pod, err := config.client.CoreV1().Pods(config.ns).Create(pod) Expect(err).NotTo(HaveOccurred()) </ins> <del> }) </del> <ins> err = framework.WaitForPodNameRunningInNamespace(config.client, pod.Name, pod.Namespace) Expect(err).To(HaveOccurred()) checkPodEvents(config, pod.Name, ep) </ins> <del> Context(\"when pod's node is different from PV's NodeName\", func() { </del> <ins> cleanupLocalVolumes(config, []*localTestVolume{testVol}) }) }) </ins> <del> BeforeEach(func() { if len(config.nodes) < 2 { framework.Skipf(\"Runs only when number of nodes >= 2\") } }) </del> <ins> Context(\"when pod's node is different from PV's NodeAffinity\", func() { var ( testVol    *localTestVolume volumeType localVolumeType ) BeforeEach(func() { if len(config.nodes) < 2 { framework.Skipf(\"Runs only when number of nodes >= 2\") } </ins> <del> ep := &eventPatterns{ reason:  \"FailedMount\", pattern: make([]string, 2)} ep.pattern = append(ep.pattern, \"NodeSelectorTerm\") ep.pattern = append(ep.pattern, \"MountVolume.NodeAffinity check failed\") </del> <ins> volumeType = DirectoryLocalVolumeType setupStorageClass(config, &immediateMode) testVols := setupLocalVolumesPVCsPVs(config, volumeType, config.node0, 1, immediateMode) testVol = testVols[0] }) </ins> <del> It(\"should not be able to mount due to different NodeName\", func() { testPodWithNodeName(config, testVolType, ep, config.nodes[1].Name, makeLocalPodWithNodeName, testMode) }) }) </del> <ins> AfterEach(func() { cleanupLocalVolumes(config, []*localTestVolume{testVol}) cleanupStorageClass(config) </ins> }) <del> } </del> <ins> It(\"should not be able to mount due to different NodeAffinity\", func() { testPodWithNodeConflict(config, volumeType, config.nodes[1].Name, makeLocalPodWithNodeAffinity, immediateMode) }) It(\"should not be able to mount due to different NodeSelector\", func() { testPodWithNodeConflict(config, volumeType, config.nodes[1].Name, makeLocalPodWithNodeSelector, immediateMode) }) }) </ins> Context(\"when using local volume provisioner\", func() { var volumePath string", "positive_passages": [{"docid": "doc-en-kubernetes-9df8e5ba2e9f919d9bec92d550979c4e420a21d16e91da208714cd0aae742f47", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /assign What happened: The tests are failing again because the scheduler messages have changed yet again. I'm going to remove the check for the exact messages because this is at least the 3rd time this has happened. Instead depend on unit/integration tests to check for specific failures. Also there's no need for these tests to run across all types of local volumes because it's just testing the scheduler part.", "commid": "kubernetes_issue_59369", "tokennum": 123}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2db5aecfdcf37282dc75d51314398feb1fbd301303a00cbe03d0eac989d21bf8", "query": "scheme := runtime.NewScheme() scheme.AddKnownTypes(cmResource.GroupVersion(), &v1.ConfigMap{}) codecs := serializer.NewCodecFactory(scheme) <del> o := NewFieldManagedObjectTracker(scheme, codecs.UniversalDecoder(), fakeTypeConverter) </del> <ins> o := NewFieldManagedObjectTracker(scheme, codecs.UniversalDecoder(), configMapTypeConverter(scheme)) </ins> reaction := ObjectReaction(o) action := NewCreateAction(cmResource, \"default\", &v1.ConfigMap{", "positive_passages": [{"docid": "doc-en-kubernetes-29db4d0749071d4e54a9083e12a93fb8b6b43cd54c28626ec2efc45861483a16", "text": "Smoke tests run by publishing-bot on client-go master are failing Ref for failure logs: Tests defined for client-go, after publishing, Since commit No response As part of , when module is used from within the staging directory, can be used by traversing to the parent directory. But once the module is made as a separate repository as part of publishing, then traversing to repository using path will not work. No response /sig-api-machinery\n/sig api-machinery\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /sig api-machinery 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\nLooking\nI'll remove the swagger file dependency, I don't think we strictly need it.\n/triage accepted", "commid": "kubernetes_issue_125704", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2dc822a0d2ce95b46ddd1d56a31024cf77b33534dfd9e81ec9a859f39739651a", "query": "minRequestTimeout:       minRequestTimeout, } crdInformer.Informer().AddEventHandler(cache.ResourceEventHandlerFuncs{ <ins> AddFunc:    ret.createCustomResourceDefinition, </ins> UpdateFunc: ret.updateCustomResourceDefinition, DeleteFunc: func(obj interface{}) { ret.removeDeadStorage()", "positive_passages": [{"docid": "doc-en-kubernetes-16c95be4925a0d298a67709c93efbb137b71325e5e3041edcf306d6572e4ae65", "text": "Which jobs are failing: pull-kubernetes-integration Which test(s) are failing: TestWebhookConverterWithDefaulting /assign /priority important-soon /area custom-resources /sig api-machinery /kind flake /milestone v1.16\n/cc\nseveral of the webhook converter tests have similar flakes. it looks like the wait for storage version to become effective times out occasionally Rare flakes seen in all of these tests: TestWebhookConverterWithWatchCache/nontrivial-converter TestWebhookConverterWithWatchCache/metadata-mutating-converter TestWebhookConverterWithDefaulting/metadata-mutating-converter TestWebhookConverterWithWatchCache/noop-converter TestWebhookConverterWithDefaulting/empty-response TestWebhookConverterWithoutWatchCache/nontrivial-converter/check-2 TestWebhookConverterWithoutWatchCache/noop-converter/check-0/v1beta2 TestWebhookConverterWithoutWatchCache/nontrivial-converter/check-0/v1beta2\ncc\nYikes, I\u2019ll sort it out.\niiuc sending an empty patch gets short-circuited and doesn't bump CR generation, even if the storage version gets changed, which means we do not re-write to etcd and go through the encoding path this would be racing and doing noop's if the first pass of didn't get the expected storage version I will send a fix to make the patch do actual mutation\nIt doesn't bump generation, but the bytes to persist in etcd would still be different if the storage version had changed, so they should persist. You can verify that by changing the storage version on a CRD yourself, do an empty patch, and see if the resourceVersion changes.\nyou're right. Generation is for non-metadata change only, and the RV changes. I queried etcd locally and the apiVersion did change for an empty patch (sidetracking: another observation is after changing the storage version (say v1 -v2; noop convertor), empty-patching v2 endpoint would bump generation, while empty-patching v1 endpoint wouldn't)\nanother theory: our cached storage strategy could be stale if the CRD informer merges multiple events together (e.g. the informer does a re-list).", "commid": "kubernetes_issue_78913", "tokennum": 546}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2dc822a0d2ce95b46ddd1d56a31024cf77b33534dfd9e81ec9a859f39739651a", "query": "minRequestTimeout:       minRequestTimeout, } crdInformer.Informer().AddEventHandler(cache.ResourceEventHandlerFuncs{ <ins> AddFunc:    ret.createCustomResourceDefinition, </ins> UpdateFunc: ret.updateCustomResourceDefinition, DeleteFunc: func(obj interface{}) { ret.removeDeadStorage()", "positive_passages": [{"docid": "doc-en-kubernetes-4d6bef5a272bfef04fa7527d92c495ee5b0e5d06d06a593b8089b98a3b84ddb9", "text": "Two scenarios: -create-update events merged into an update event: strategy with UID:a was created on demand for CRD Foo Foo was deleted and recreated strategy with UID:b was created on demand for the new Foo new Foo got updated (e.g. switching storage version) the strategy with UID:b is supposed to be deleted and , to reflect the last update. But if the CRD informer merges the delete-create-update events into , the strategy with UID:a will be deleted, but the strategy with UID:b won't. -update events merged into a create event: strategy with UID:a was created on demand for CRD Foo Foo was updated (e.g. switching storage version) the strategy with UID:a is supposed to be deleted and , to reflect the last update. But if the CRD informer merges the create-update events into , the strategy with UID:a won't be deleted (as we don't react on create events). another race found in , which could happen in a single update.\nI think I :", "commid": "kubernetes_issue_78913", "tokennum": 234}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2df4c5ccc157eada278ac2f135e0c37c30a65e9a8931c0857e2bccd11d1ed9c2", "query": "\"httpGet\": { \"host\": \"127.0.0.1\", \"port\": 8080, <del> \"path\": \"/healthz\" </del> <ins> \"path\": \"/healthz?exclude=etcd\" </ins> }, \"initialDelaySeconds\": {{liveness_probe_initial_delay}}, \"timeoutSeconds\": 15 }, <ins> \"readinessProbe\": { \"httpGet\": { \"host\": \"127.0.0.1\", \"port\": 8080, \"path\": \"/healthz\" }, \"timeoutSeconds\": 15 }, </ins> \"ports\":[ { \"name\": \"https\", \"containerPort\": {{secure_port}},", "positive_passages": [{"docid": "doc-en-kubernetes-01cc291fb1d6afeae9b284d60dd407b578a72d26e4c50043cbdf654c92184c45", "text": "What would you like to be : Add support to the kube-apiserver so that we can disable health-checks via query params. Why is this needed: Currently, the healthz endpoint is inflexible in that any and all health checks are currently executed when the endpoint is hit. Since the kube-apiserver only currently supports a liveness check, this means all persistent health check failures will eventually result in a kubelet driven restart. However, this may not be desirable behavior if you have additional monitoring services layered on top of your control plane. For instance, take the etcd failure from the perspective of the kube-apiserver. Currently, persistent failures during the etcd health check from the api-server healthz endpoint will cause the kube-apiserver to be restarted. This sometimes helps (in the case of a faulty etcd-client connection) but also can be detrimental (the kube-apiserver restarts until the etcd cluster is functioning, then the kube-apiserver bombards the etcd cluster with requests to update local caches, saturating the etcd cluster with requests, causing it to timeout on its own liveness probes and trigger a kubelet-driven restart). Let's say that we could now disable etcd from our liveness health check. Then if we had an external monitoring service, we could ask independently ask etcd if it was healthy and we could also ask the kube-apiserver if it thought etcd was unhealthy. Based on the combination of those answers, we could enable more intelligent responses to certain situation, like restarting the kube-apiserver when it thought etcd was unhealthy but etcd was actually reporting as healthy but not doing so when etcd was actually unhealthy. This feature is backwards-compatible and opt-in. There would be no impact to existing behavior unless these query params are actually used. /sig api-machinery /kind feature\n/cc\nSGTM\n/assign", "commid": "kubernetes_issue_70591", "tokennum": 432}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2e4a5ddca8a70cffd9a581af7bb1a2e8ec75a3c132bc4bbbd1cb54880ec9537c", "query": "func TestPodContainerDeviceAllocation(t *testing.T) { flag.Set(\"alsologtostderr\", fmt.Sprintf(\"%t\", true)) <del> var logLevel string flag.StringVar(&logLevel, \"logLevel\", \"4\", \"test\") flag.Lookup(\"v\").Value.Set(logLevel) </del> res1 := TestResource{ resourceName:     \"domain1.com/resource1\", resourceQuantity: *resource.NewQuantity(int64(2), resource.DecimalSI),", "positive_passages": [{"docid": "doc-en-kubernetes-3e8f9b25d1f3d96c25ea3e7b882f872baf67d41cad6a3bbcf2df0e192dbdfda5", "text": "This is not 100% reproducable in my cluster. There is 20% chance of failing in my environment.\n/area hw-accelerators mentioned a root cause that might be due to unit tests sharing the same Unix socket and interfering with each others. cc\nCan you please share latest commit id of your code base using ?\nThanks very much, can you try the follow command please:\n/assign\nThe latest commit id of my code base:\nI found this is not 100% reproducable in my cluster. There is 20% chance of failing in my environment.\nResult of go test command:\n/sig scheduling\nThanks!\nHi, does these unit tests pass with PR\nI run 100 times without failure.\nGood to here that, Nice work! Thanks!", "commid": "kubernetes_issue_58281", "tokennum": 154}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2e573d80625dbf40e7621d022aa8f1c4bfee9da58f1c5635791bea2fbe1f0344", "query": "timeoutCtx, timeoutCancel := context.WithTimeout(ctx, le.config.RenewDeadline) defer timeoutCancel() err := wait.PollImmediateUntil(le.config.RetryPeriod, func() (bool, error) { <del> return le.tryAcquireOrRenew(), nil </del> <ins> done := make(chan bool, 1) go func() { defer close(done) done <- le.tryAcquireOrRenew() }() select { case <-timeoutCtx.Done(): return false, fmt.Errorf(\"failed to tryAcquireOrRenew %s\", timeoutCtx.Err()) case result := <-done: return result, nil } </ins> }, timeoutCtx.Done()) le.maybeReportTransition() desc := le.config.Lock.Describe() if err == nil {", "positive_passages": [{"docid": "doc-en-kubernetes-638d244f4d44257351ae4786f705d88f47a0e12c74ce71a459164cb07c9c1943", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: kube-cm kube-scheduler does not exit when kube-apiserver suspended What you expected to happen: kube-cm kube-scheduler should exit after LeaderElector stops leading How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/sig api-machinery /kind bug\n/assign\n/cc", "commid": "kubernetes_issue_65090", "tokennum": 179}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2e6a389d2ac786185fd3cac5016250b463531b3b91fd5205cf2517b3baab5201", "query": "out.Filter = (*v1alpha1.PluginSet)(unsafe.Pointer(in.Filter)) out.PostFilter = (*v1alpha1.PluginSet)(unsafe.Pointer(in.PostFilter)) out.Score = (*v1alpha1.PluginSet)(unsafe.Pointer(in.Score)) <del> out.NormalizeScore = (*v1alpha1.PluginSet)(unsafe.Pointer(in.NormalizeScore)) </del> out.Reserve = (*v1alpha1.PluginSet)(unsafe.Pointer(in.Reserve)) out.Permit = (*v1alpha1.PluginSet)(unsafe.Pointer(in.Permit)) out.PreBind = (*v1alpha1.PluginSet)(unsafe.Pointer(in.PreBind))", "positive_passages": [{"docid": "doc-en-kubernetes-65d9c28fb77fe0bb882df060209fc22bf399af9c3b9dfe5829b0e5a45dc20b3d", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Consolidate ) into Score plugin set in config API. Why is this needed: NormalizeScore extension point is implemented in . We decided to treat NormalizeScore as an \"optional\" step of Score plugin, see . However, we deferred the removal of due to API review delays. Now that PR was merged. We can start the actual removal from the API and start the API review process. /sig scheduling\n/assign", "commid": "kubernetes_issue_80908", "tokennum": 113}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2e7a6836ebdd5be7c247a4aabbc614f5a9025bb0dabcf3492021d7b553742d05", "query": "// +k8s:deepcopy-gen=package <del> package testing </del> <ins> package testing // import \"k8s.io/apiserver/pkg/endpoints/testing\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-460ceb7b52a1ab0cadc1b29d7eee5cc1013b8d23be9bca0d145119ffcf7b27c6", "text": "Look at one of the directories under (Please don't pick more than one directory for one PR as it will cause issues for reviewers) Find all the files named (example find -name ) See the following link it has a this tells tools how this package needs to be imported. So we should ensure that each has an import Add a description appropriate to the package (similar to the one below) Look through sub directories and see if there are any other important directories that are likely to be used by outside users and add a Why are we doing this? We perfer to use vanity urls instead of directly using to refer to code, so this helps ensure that tools honor our wish. See It would be good to have some package level documentation since these directories under staging/ are meant to be for use by folks outside of kubernetes github org. /good-first-issue\n/kind documentation /sig architecture\ncurrently working my through Not going to use / assign since there could be a number of PRs for this issue.\n/lifecycle active /good-first-issue edit: hmm..\nThis request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /lifecycle active /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\nMay I try on\nIIUC this means that there needs to be a even at the root of the repo? Then how does work? :thinking:\nHi , can I make a PR for this directory ?\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_68231", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2e7a6836ebdd5be7c247a4aabbc614f5a9025bb0dabcf3492021d7b553742d05", "query": "// +k8s:deepcopy-gen=package <del> package testing </del> <ins> package testing // import \"k8s.io/apiserver/pkg/endpoints/testing\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-5f31f1c27d7198dc83b313154ff681043a8b41e17eb5d3ddf32cd84bc023f931", "text": "/lifecycle rotten\nI guess this is still not done, was supposed to partially fix this issue. /reopen\nReopened this issue. <detailsIn response to : I guess this is still not done, was supposed to partially fix this 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\n/remove-lifecycle rotten /area code-organization", "commid": "kubernetes_issue_68231", "tokennum": 93}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2e7e61e4522cca6281faaaa63212035c24979aa0c38638aaf96b1d3f50d2473b", "query": "return nameservers, searches, options, utilerrors.NewAggregate(allErrors) } <ins> // Reads a resolv.conf-like file and returns the DNS config options from it. // Returns an empty DNSConfig if the given resolverConfigFile is an empty string. func getDNSConfig(resolverConfigFile string) (*runtimeapi.DNSConfig, error) { var hostDNS, hostSearch, hostOptions []string // Get host DNS settings if resolverConfigFile != \"\" { f, err := os.Open(resolverConfigFile) if err != nil { klog.ErrorS(err, \"Could not open resolv conf file.\") return nil, err } defer f.Close() hostDNS, hostSearch, hostOptions, err = parseResolvConf(f) if err != nil { err := fmt.Errorf(\"Encountered error while parsing resolv conf file. Error: %w\", err) klog.ErrorS(err, \"Could not parse resolv conf file.\") return nil, err } } return &runtimeapi.DNSConfig{ Servers:  hostDNS, Searches: hostSearch, Options:  hostOptions, }, nil } </ins> func getPodDNSType(pod *v1.Pod) (podDNSType, error) { dnsPolicy := pod.Spec.DNSPolicy switch dnsPolicy {", "positive_passages": [{"docid": "doc-en-kubernetes-5e93ba1a338583c6193506912a68a67fcc908451a37c483694071bc120df2bcb", "text": "When a --resolv-conf (DNS resolver config) is passed to kubelet on a Windows node, the config content is used as part of sandbox initialization (through getHostDNSConfig()). Now with the recent changes (), it seems now to fail with an error like: E0315 10:22:16. 4764 ] \"Error syncing pod, skipping\" err=\"failed to \"CreatePodSandbox\" for \"img-pull-(-b40a-459d-9033-)\" with CreatePodSandboxError: \"Failed to generate sandbox config for pod \"img-pull-(-b40a-459d-9033-)\": Unexpected resolver config value: \"C:etckubernetescni\". Expected \"\" or \"Host\".\"\" pod=\"img-puller-3842/img-pull-\" podUID=-b40a-459d-9033- This is showing on all the runs of GCE testgrid (latest): Reading/using the passed resolv config on Windows Run a Windows pool with DNS resolv config being set as part of kubelet params. No response_ 27 alpha.3 1.27 beta.0 master <detailsGCE </details<details</details<details</details<details</details<details</details\n/triage accepted /milestone v1.27 /sig node /sig network\n/sig windows /cc\n/priority criticial-urgent as this is likely a release blocking\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority criticial-urgent 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\n/priority critical-urgent\nHmm, so you're setting the [1]. This PR introduced the capability to read the DNS config options from the Windows host registries while removing the capability to read from a file, introducing a regression. I've sent a PR addressing this issue: [1]\nIs the file you are pointing to a UNIX-style or something else?\nWas the file changing the behavior of the node?", "commid": "kubernetes_issue_116782", "tokennum": 565}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2e7e61e4522cca6281faaaa63212035c24979aa0c38638aaf96b1d3f50d2473b", "query": "return nameservers, searches, options, utilerrors.NewAggregate(allErrors) } <ins> // Reads a resolv.conf-like file and returns the DNS config options from it. // Returns an empty DNSConfig if the given resolverConfigFile is an empty string. func getDNSConfig(resolverConfigFile string) (*runtimeapi.DNSConfig, error) { var hostDNS, hostSearch, hostOptions []string // Get host DNS settings if resolverConfigFile != \"\" { f, err := os.Open(resolverConfigFile) if err != nil { klog.ErrorS(err, \"Could not open resolv conf file.\") return nil, err } defer f.Close() hostDNS, hostSearch, hostOptions, err = parseResolvConf(f) if err != nil { err := fmt.Errorf(\"Encountered error while parsing resolv conf file. Error: %w\", err) klog.ErrorS(err, \"Could not parse resolv conf file.\") return nil, err } } return &runtimeapi.DNSConfig{ Servers:  hostDNS, Searches: hostSearch, Options:  hostOptions, }, nil } </ins> func getPodDNSType(pod *v1.Pod) (podDNSType, error) { dnsPolicy := pod.Spec.DNSPolicy switch dnsPolicy {", "positive_passages": [{"docid": "doc-en-kubernetes-a55794e1d2c420cf7484c297920657922704eb45d045ae8237364febdd60d634", "text": "Yeah, what used on GCE/GKE, seems to be a Linux-like conf, eg: nameserver 10.128.0.1 search c.<project_name.internal google.internal ` We haven't tried to remove from kubelet to see the behavior.\nThis Issue/PR has been marked as release blocker. Please have the fix merged by eod today otherwise the feature has to be reverted. For the Issue/PR owner: please have a revert/feature disable PR open today in case the fix failed to get in. Thank you! See the -- Kubernetes 1.27 release manager\nI opened up a revert PR in case this PR does not merge by code freeze.\nThanks for the resolution! both 2019 and 2022 grids seems to be back to green now!\nThanks for confirming! I opened to ensure gets updated too", "commid": "kubernetes_issue_116782", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2ec442f23b082a559d33dff264eab2147ef2ba01632e3344394462e719ce911b", "query": "// if nodeAffinity.RequiredDuringSchedulingRequiredDuringExecution != nil { // \tnodeSelectorTerms := nodeAffinity.RequiredDuringSchedulingRequiredDuringExecution.NodeSelectorTerms // \tglog.V(10).Infof(\"Match for RequiredDuringSchedulingRequiredDuringExecution node selector terms %+v\", nodeSelectorTerms) <del> // \tnodeAffinityMatches = NodeMatchesNodeSelectorTerms(node, nodeSelectorTerms) </del> <ins> // \tnodeAffinityMatches = nodeMatchesNodeSelectorTerms(node, nodeSelectorTerms) </ins> // } // Match node selector for requiredDuringSchedulingIgnoredDuringExecution. if nodeAffinity.RequiredDuringSchedulingIgnoredDuringExecution != nil { nodeSelectorTerms := nodeAffinity.RequiredDuringSchedulingIgnoredDuringExecution.NodeSelectorTerms glog.V(10).Infof(\"Match for RequiredDuringSchedulingIgnoredDuringExecution node selector terms %+v\", nodeSelectorTerms) <del> nodeAffinityMatches = nodeAffinityMatches && NodeMatchesNodeSelectorTerms(node, nodeSelectorTerms) </del> <ins> nodeAffinityMatches = nodeAffinityMatches && nodeMatchesNodeSelectorTerms(node, nodeSelectorTerms) </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-3229e3f28f67afa9ddea85d9d31a50803c261e0ae30f76f950060d1790215e64", "text": "I just noticed you forgot to register the image locality priority function in in I also missed it when I reviewed your PR. I have fixed this in . But it would be great if you could figure out a mechanism that would ensure that all predicate/priority functions that are tested (you can assume they will always live under ) are registered, and fail the test if not. That will allow us to prevent this mistake in the future.\nThanks! Will fix this soon!\nSeems need to wait for in before I send PR? Otherwise this test will always fail ...", "commid": "kubernetes_issue_21236", "tokennum": 114}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2ed4d9b5e156808c3490220e5dd2f5b91e7b88864f31bec3e17d21f5e33c287b", "query": "} } <ins> func TestAttacherWaitForAttach(t *testing.T) { tests := []struct { name             string driver           string makeAttachment   func() *storage.VolumeAttachment expectedAttachID string expectError      bool }{ { name:   \"successful attach\", driver: \"attachable\", makeAttachment: func() *storage.VolumeAttachment { testAttachID := getAttachmentName(\"test-vol\", \"attachable\", \"node\") successfulAttachment := makeTestAttachment(testAttachID, \"node\", \"test-pv\") successfulAttachment.Status.Attached = true return successfulAttachment }, expectedAttachID: getAttachmentName(\"test-vol\", \"attachable\", \"node\"), expectError:      false, }, { name:        \"failed attach\", driver:      \"attachable\", expectError: true, }, } for _, test := range tests { t.Run(test.name, func(t *testing.T) { plug, _, tmpDir, _ := newTestWatchPlugin(t, nil) defer os.RemoveAll(tmpDir) attacher, err := plug.NewAttacher() if err != nil { t.Fatalf(\"failed to create new attacher: %v\", err) } csiAttacher := attacher.(*csiAttacher) spec := volume.NewSpecFromPersistentVolume(makeTestPV(\"test-pv\", 10, test.driver, \"test-vol\"), false) if test.makeAttachment != nil { attachment := test.makeAttachment() _, err = csiAttacher.k8s.StorageV1beta1().VolumeAttachments().Create(attachment) if err != nil { t.Fatalf(\"failed to create VolumeAttachment: %v\", err) } gotAttachment, err := csiAttacher.k8s.StorageV1beta1().VolumeAttachments().Get(attachment.Name, meta.GetOptions{}) if err != nil { t.Fatalf(\"failed to get created VolumeAttachment: %v\", err) } t.Logf(\"created test VolumeAttachment %+v\", gotAttachment) } attachID, err := csiAttacher.WaitForAttach(spec, \"\", nil, time.Second) if err != nil && !test.expectError { t.Errorf(\"Unexpected error: %s\", err) } if err == nil && test.expectError { t.Errorf(\"Expected error, got none\") } if attachID != test.expectedAttachID { t.Errorf(\"Expected attachID %q, got %q\", test.expectedAttachID, attachID) } }) } } </ins> func TestAttacherWaitForVolumeAttachment(t *testing.T) { nodeName := \"test-node\" testCases := []struct {", "positive_passages": [{"docid": "doc-en-kubernetes-2aac55d80f27da70e775c33573d217f00c9becbbc11daa530f1576640fc1582a", "text": "The test flakes very occasionally. Below are the findings of the circumstances of the flake. During two pods are created in quick succession. The test flakes when the second Pod fails to come up. The second pod fails to come up with error: Upon exploring the logs we discovered that there was only 1 Attach call made at the beginning, and one Detach call upon timeout of the test [See timestamps]: We tracked down the error to the likely culprit in func : based on the error message returned. This is likely caused by (string) being empty [uncomfirmed], which is what the Kubelet would get from the DevicePath field on the Node object. This DevicePath field is normally on Attach and removed on Detach of the volume. The DevicePath is clearly present on the Node when the first pod is being brought up. But it is possible that it is somehow missing or not able to be retrieved by the time the second Pod is starting up (and continues to be unavailable exhausting the 15m timeout on the test) even though no Detach operation was performed on the volume in the meantime (according to logs). We are currently unable to reproduce this flake on command and did all analysis based on logs from the two flakes we saw naturally occur in the 100s of runs performed of the test. This flake was originally seen in and the test logs can be found here: https://k8s- Environment: GCE Kubernetes version (use ):Cloud provider or hardware configuration: GCP OS (e.g. from /etc/os-release):Kernel (e.g. ): /kind flake /kind bug /sig storage /cc\nIssues 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\n/remove-lifecycle stale A check in triage shows that this failing test is still a problem, and in fact has become more of a problem since October 4th. Has there been any progress on a fix?", "commid": "kubernetes_issue_65246", "tokennum": 474}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2ed4d9b5e156808c3490220e5dd2f5b91e7b88864f31bec3e17d21f5e33c287b", "query": "} } <ins> func TestAttacherWaitForAttach(t *testing.T) { tests := []struct { name             string driver           string makeAttachment   func() *storage.VolumeAttachment expectedAttachID string expectError      bool }{ { name:   \"successful attach\", driver: \"attachable\", makeAttachment: func() *storage.VolumeAttachment { testAttachID := getAttachmentName(\"test-vol\", \"attachable\", \"node\") successfulAttachment := makeTestAttachment(testAttachID, \"node\", \"test-pv\") successfulAttachment.Status.Attached = true return successfulAttachment }, expectedAttachID: getAttachmentName(\"test-vol\", \"attachable\", \"node\"), expectError:      false, }, { name:        \"failed attach\", driver:      \"attachable\", expectError: true, }, } for _, test := range tests { t.Run(test.name, func(t *testing.T) { plug, _, tmpDir, _ := newTestWatchPlugin(t, nil) defer os.RemoveAll(tmpDir) attacher, err := plug.NewAttacher() if err != nil { t.Fatalf(\"failed to create new attacher: %v\", err) } csiAttacher := attacher.(*csiAttacher) spec := volume.NewSpecFromPersistentVolume(makeTestPV(\"test-pv\", 10, test.driver, \"test-vol\"), false) if test.makeAttachment != nil { attachment := test.makeAttachment() _, err = csiAttacher.k8s.StorageV1beta1().VolumeAttachments().Create(attachment) if err != nil { t.Fatalf(\"failed to create VolumeAttachment: %v\", err) } gotAttachment, err := csiAttacher.k8s.StorageV1beta1().VolumeAttachments().Get(attachment.Name, meta.GetOptions{}) if err != nil { t.Fatalf(\"failed to get created VolumeAttachment: %v\", err) } t.Logf(\"created test VolumeAttachment %+v\", gotAttachment) } attachID, err := csiAttacher.WaitForAttach(spec, \"\", nil, time.Second) if err != nil && !test.expectError { t.Errorf(\"Unexpected error: %s\", err) } if err == nil && test.expectError { t.Errorf(\"Expected error, got none\") } if attachID != test.expectedAttachID { t.Errorf(\"Expected attachID %q, got %q\", test.expectedAttachID, attachID) } }) } } </ins> func TestAttacherWaitForVolumeAttachment(t *testing.T) { nodeName := \"test-node\" testCases := []struct {", "positive_passages": [{"docid": "doc-en-kubernetes-2e50b6735500133e652390e8c295dea37c7d3b52bec7ef89ae580efb33be52fd", "text": "/priority important-soon\n/assign for triage\nWe should find the root cause and fix for 1.13\n/assign Patrick can you PTAL at what is causing flakiness in this test.\nI will have a look. Right now the log output of the sidecar containers and the CSI driver are not captured, which makes debugging a bit hard. In PR I am adding code which includes those message in the test log. Let me finish that PR and once it is merged, debugging the next test flake might provide some better insight into what went wrong.\nHey, this issue is considered a blocker for 1.13beta. Is there anything we can do to get it resolved sooner, so that it doesn't delay beta next week?\nis trying to instrument the e2e tests to get logs from the csi driver containers so that we can debug. He has tried running the test locally ~100 times and didn't see it flake.\nhere's one recent one you can check out:\nMichelle Au <: I had a look, but something is odd about that one. The error for the second pod is there: But under there is no further information about node bootstrap-e2e-gce-mz-minion-group-3kn6. Shouldn't that be available?\n\"Patrick Ohly\" Here's a better example where the kublet log with the error is available: That one also has the log of the external-attacher, but that doesn't tell me much. I'm now comparing a \"bad\" run with a \"good\" local run. One observation is that in the \"good\" run, operationExecutor.UnmountDevice is completed before the second usage, including the \"Volume detached for volume\" step in Then operationExecutor.VerifyControllerAttachedVolume is done again for the second pod, exactly as it was done for the first: In the \"bad\" run, operationExecutor.MountVolume is invoked before that \"Volume detached for volume\" and then runs with an empty device path, without going through VerifyControllerAttachedVolume again: So to me it looks like a race between two conflicting operations. Does that make sense? How to fix it is less obvious. The relevant code seems to be this in Any suggestions?\nThis seems inline with the observations that made initially. We should trace where DevicePath is getting set.", "commid": "kubernetes_issue_65246", "tokennum": 520}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2ed4d9b5e156808c3490220e5dd2f5b91e7b88864f31bec3e17d21f5e33c287b", "query": "} } <ins> func TestAttacherWaitForAttach(t *testing.T) { tests := []struct { name             string driver           string makeAttachment   func() *storage.VolumeAttachment expectedAttachID string expectError      bool }{ { name:   \"successful attach\", driver: \"attachable\", makeAttachment: func() *storage.VolumeAttachment { testAttachID := getAttachmentName(\"test-vol\", \"attachable\", \"node\") successfulAttachment := makeTestAttachment(testAttachID, \"node\", \"test-pv\") successfulAttachment.Status.Attached = true return successfulAttachment }, expectedAttachID: getAttachmentName(\"test-vol\", \"attachable\", \"node\"), expectError:      false, }, { name:        \"failed attach\", driver:      \"attachable\", expectError: true, }, } for _, test := range tests { t.Run(test.name, func(t *testing.T) { plug, _, tmpDir, _ := newTestWatchPlugin(t, nil) defer os.RemoveAll(tmpDir) attacher, err := plug.NewAttacher() if err != nil { t.Fatalf(\"failed to create new attacher: %v\", err) } csiAttacher := attacher.(*csiAttacher) spec := volume.NewSpecFromPersistentVolume(makeTestPV(\"test-pv\", 10, test.driver, \"test-vol\"), false) if test.makeAttachment != nil { attachment := test.makeAttachment() _, err = csiAttacher.k8s.StorageV1beta1().VolumeAttachments().Create(attachment) if err != nil { t.Fatalf(\"failed to create VolumeAttachment: %v\", err) } gotAttachment, err := csiAttacher.k8s.StorageV1beta1().VolumeAttachments().Get(attachment.Name, meta.GetOptions{}) if err != nil { t.Fatalf(\"failed to get created VolumeAttachment: %v\", err) } t.Logf(\"created test VolumeAttachment %+v\", gotAttachment) } attachID, err := csiAttacher.WaitForAttach(spec, \"\", nil, time.Second) if err != nil && !test.expectError { t.Errorf(\"Unexpected error: %s\", err) } if err == nil && test.expectError { t.Errorf(\"Expected error, got none\") } if attachID != test.expectedAttachID { t.Errorf(\"Expected attachID %q, got %q\", test.expectedAttachID, attachID) } }) } } </ins> func TestAttacherWaitForVolumeAttachment(t *testing.T) { nodeName := \"test-node\" testCases := []struct {", "positive_passages": [{"docid": "doc-en-kubernetes-50ecdb83cd1167eaf5e0774965d35fc15510d148142317b954cbbba2a849431a", "text": "Could there be a race with AD controller or external attacher if they try to detach the volume? is another race around this area. Unclear if it's the same yet.\nMichelle Au <: No idea. Even if it isn't, it's at least related to the same piece of code. Probably worth fixing both together. Can we get someone who has worked in this area to fix these issues? Today is the first day that I've ever seen this code, so I'm a bit afraid that it'll take me a long time to get it right, and I'm worried about regressions.\nI've asked to help investigate\nIt is not a blocker for beta or freeze. Can be addressed in stabilization. Let's keep the 1.13 tag on it. And based on progress by stabilization we can reassess if it is even a 1.13 blocker (at this point I don't believe it is).\nThe in the actual state of the world gets reset during unmounting:\nThat removes the device path looks wrong to me. I've submitted PR which changes that. Let's see how much that breaks...\n/assign The conclusion in the CSI working group was that while my analysis and the resulting fix might be correct, further debugging and a second pair of eyes would be good. Let me reassign, because I have done what I could for this issue.\nThe RT considers this a blocker now, because flakes are happening often enough to interfere with getting clear signal on several jobs. Even if the underlying problem isn't that serious.\n/assign I will help triage as well.\nAck Thanks\nInstead of which may have negative side effects for non-CSI volumes, let's do this instead: Modify the CSI method in to ignore the passed in (which is populated from devicePath. Instead let's have that method generate the from scratch, e.g. attachID := getAttachmentName(volID, driverName, string(nodeName)) This will remove any CSI dependency on devicePath and not effect other volume plugins.\nI am trying to twist my head around the code. IMO it affects also AWS that uses devicePath stored in and it should be reproducible there too. So far I was unsuccessful. In the logs it's clearly visible that UnmountDevice succeeded. So why kubelet continues with MountVolume instead of MountDevice? That's wrong.", "commid": "kubernetes_issue_65246", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2ed4d9b5e156808c3490220e5dd2f5b91e7b88864f31bec3e17d21f5e33c287b", "query": "} } <ins> func TestAttacherWaitForAttach(t *testing.T) { tests := []struct { name             string driver           string makeAttachment   func() *storage.VolumeAttachment expectedAttachID string expectError      bool }{ { name:   \"successful attach\", driver: \"attachable\", makeAttachment: func() *storage.VolumeAttachment { testAttachID := getAttachmentName(\"test-vol\", \"attachable\", \"node\") successfulAttachment := makeTestAttachment(testAttachID, \"node\", \"test-pv\") successfulAttachment.Status.Attached = true return successfulAttachment }, expectedAttachID: getAttachmentName(\"test-vol\", \"attachable\", \"node\"), expectError:      false, }, { name:        \"failed attach\", driver:      \"attachable\", expectError: true, }, } for _, test := range tests { t.Run(test.name, func(t *testing.T) { plug, _, tmpDir, _ := newTestWatchPlugin(t, nil) defer os.RemoveAll(tmpDir) attacher, err := plug.NewAttacher() if err != nil { t.Fatalf(\"failed to create new attacher: %v\", err) } csiAttacher := attacher.(*csiAttacher) spec := volume.NewSpecFromPersistentVolume(makeTestPV(\"test-pv\", 10, test.driver, \"test-vol\"), false) if test.makeAttachment != nil { attachment := test.makeAttachment() _, err = csiAttacher.k8s.StorageV1beta1().VolumeAttachments().Create(attachment) if err != nil { t.Fatalf(\"failed to create VolumeAttachment: %v\", err) } gotAttachment, err := csiAttacher.k8s.StorageV1beta1().VolumeAttachments().Get(attachment.Name, meta.GetOptions{}) if err != nil { t.Fatalf(\"failed to get created VolumeAttachment: %v\", err) } t.Logf(\"created test VolumeAttachment %+v\", gotAttachment) } attachID, err := csiAttacher.WaitForAttach(spec, \"\", nil, time.Second) if err != nil && !test.expectError { t.Errorf(\"Unexpected error: %s\", err) } if err == nil && test.expectError { t.Errorf(\"Expected error, got none\") } if attachID != test.expectedAttachID { t.Errorf(\"Expected attachID %q, got %q\", test.expectedAttachID, attachID) } }) } } </ins> func TestAttacherWaitForVolumeAttachment(t *testing.T) { nodeName := \"test-node\" testCases := []struct {", "positive_passages": [{"docid": "doc-en-kubernetes-d22ef691d33dfaf1e5b5dad591a3014f6fd8d0e62064752134a5c7ffdbfdc8ce", "text": "A workaround in CSI volume plugin won't really help here, it will work only for drivers without .\nI finally reproduced it on AWS with a long sleep in : Steps to reproduce (with the hack above): a pod with a volume the pod. Wait until is called. a new pod with the same volume. - checks that the volume is still attached and the device is still mounted and enqueues an operation to mount the volume. When finishes, starts and 1) uses empty and 2) calls on volume that's not DeviceMounted.\nFix: Any idea how to test it for real? Fake CSI plugin with slow NodeUnstage would be the best, however we don't have one.\nI'm going to work on a targeted fix for CSI. We can continue to pursue fixing aws in-tree separately.\nPR to fix csi is here:\nwhat are the final set of PRs pending for this? , and ?\nOnly is needed to fix this particular test failure.\ncan you please confirm if we are going to fix this using or ?\nI discussed with offline, he has some suggestions for that I am investigating. I think we will want both PRs eventually, although only one of them will be needed to fix the CSI test for now. Since it's his off hours, I will continue working on today.\nAre we talking 1.13 for as well?\nReopening this since we are seeing consistent failures in latest runs. We also see one more test fail in the job with same error. Failing job https://k8s- Failing Tests [sig-storage] [Serial] CSI Volumes CSI plugin test using CSI driver: gcePD [Serial] should provision storage [sig-storage] [Serial] CSI Volumes CSI plugin test using CSI driver: hostPath [Serial] should provision storage Error This is now 1.13 release blocking.\n/priority critical-urgent /kind failing-test\n/remove-priority important-soon\nI think this is a different issue and could be due to the fact that CSI is intentionally not backwards compatible between 1.12 and 1.13. We may need to enhance the test to figure out what version the cluster is on and launch appropriate versions of the CSI driver.\n\"intentionally not backwards compatible\" -- is there a writeup for the release notes and release announcement for this change?", "commid": "kubernetes_issue_65246", "tokennum": 488}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2ed4d9b5e156808c3490220e5dd2f5b91e7b88864f31bec3e17d21f5e33c287b", "query": "} } <ins> func TestAttacherWaitForAttach(t *testing.T) { tests := []struct { name             string driver           string makeAttachment   func() *storage.VolumeAttachment expectedAttachID string expectError      bool }{ { name:   \"successful attach\", driver: \"attachable\", makeAttachment: func() *storage.VolumeAttachment { testAttachID := getAttachmentName(\"test-vol\", \"attachable\", \"node\") successfulAttachment := makeTestAttachment(testAttachID, \"node\", \"test-pv\") successfulAttachment.Status.Attached = true return successfulAttachment }, expectedAttachID: getAttachmentName(\"test-vol\", \"attachable\", \"node\"), expectError:      false, }, { name:        \"failed attach\", driver:      \"attachable\", expectError: true, }, } for _, test := range tests { t.Run(test.name, func(t *testing.T) { plug, _, tmpDir, _ := newTestWatchPlugin(t, nil) defer os.RemoveAll(tmpDir) attacher, err := plug.NewAttacher() if err != nil { t.Fatalf(\"failed to create new attacher: %v\", err) } csiAttacher := attacher.(*csiAttacher) spec := volume.NewSpecFromPersistentVolume(makeTestPV(\"test-pv\", 10, test.driver, \"test-vol\"), false) if test.makeAttachment != nil { attachment := test.makeAttachment() _, err = csiAttacher.k8s.StorageV1beta1().VolumeAttachments().Create(attachment) if err != nil { t.Fatalf(\"failed to create VolumeAttachment: %v\", err) } gotAttachment, err := csiAttacher.k8s.StorageV1beta1().VolumeAttachments().Get(attachment.Name, meta.GetOptions{}) if err != nil { t.Fatalf(\"failed to get created VolumeAttachment: %v\", err) } t.Logf(\"created test VolumeAttachment %+v\", gotAttachment) } attachID, err := csiAttacher.WaitForAttach(spec, \"\", nil, time.Second) if err != nil && !test.expectError { t.Errorf(\"Unexpected error: %s\", err) } if err == nil && test.expectError { t.Errorf(\"Expected error, got none\") } if attachID != test.expectedAttachID { t.Errorf(\"Expected attachID %q, got %q\", test.expectedAttachID, attachID) } }) } } </ins> func TestAttacherWaitForVolumeAttachment(t *testing.T) { nodeName := \"test-node\" testCases := []struct {", "positive_passages": [{"docid": "doc-en-kubernetes-532bee311f9ca5785c50bc17dbae5c7650ea95f95b647a2552dbb2ae250d0a88", "text": "Yes has the release note\nthanks, I'll also call it to the Release Notes lead's attention\nwhat does it mean from the user impact perspective for CSI to not be backward compatible with 1.12? can you please point me to any discussions on this behavior for 1.13?\nKubernetes v1.13 speaks CSI v1.0 and no longer understands CSI v0.x. Any CSI drivers deployed on previous versions of Kubernetes speaking CSI v0.x must removed, updated to be CSI 1.0 compatible, and redeployed on the on Kubernetes v1.13. If only the master is upgraded to 1.13 (and nodes are 1.12 or earlier) older drivers will continue to work. When nodes are upgraded to 1.13, then older drivers will stop working. I will capture this in detail in the \"Action Required\" section.\nIm tracking these upgrade test failures elsewhere: They are not related to this original issue, the flaky test referenced by this issue should have been solved by and for non CSI /close\nClosing this issue. <detailsIn response to : Im tracking these upgrade test failures elsewhere: They are not related to this original issue, the flaky test referenced by this issue should have been solved 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\nas FYI to call this out clearly in the Release notes.", "commid": "kubernetes_issue_65246", "tokennum": 312}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2ed83e725cf9d363ab334bf9a5336f56f2d9bc7e0271efc453b62f771a51b631", "query": "package gce import ( <ins> \"net/http\" \"net/http/httptest\" </ins> \"reflect\" \"testing\" compute \"google.golang.org/api/compute/v1\" <ins> \"k8s.io/kubernetes/pkg/util/flowcontrol\" </ins> \"k8s.io/kubernetes/pkg/util/rand\" <ins> utiltesting \"k8s.io/kubernetes/pkg/util/testing\" </ins> ) func TestGetRegion(t *testing.T) {", "positive_passages": [{"docid": "doc-en-kubernetes-599cbd9914ac52a34ee08ac617d1f4bd774f52f2d5bdcb07fa1a0e76f7194545", "text": "On a large cluster, the routecontroller basically makes O(n) requests all at once, and most of them error out with \"Rate Limit Exceeded\". We then wait for operations to complete on the ones that did stick, and damn the rest, they'll be caught next reconcile (which is a while). In fact, in some cases it appears we're spamming hard enough to get rate limited by the upper-level API DOS protections and seeing something akin to , e.g.: We can do better than this!\nc.f. , which is the other leg of this problem\nI took a look into code and it seems that we are doing full reconciliation every 10s. If we need to create 2000 routes at the beginning it seems to frequently. I think that we need to: first compute how many routes we have to create based on that try to spread them over some time to reduce possibility of causing 'rate limit exceeded' I will try to put some small PR together as a starting point.\nI'm reopening this one, since this doesn't seem to be solved. So basically something strange is happening here. With PR we have 10/s limit on API calls send to GCE. And we are still rate-limitted. However, according to documentation we are allowed for 20/s: So something either doesn't work or is weird.\nWhat is super interesting from the logs of recent run: It starts to creating routes: After 2 minutes from that, we are hitting \"Rate limit Exceeded\" for the first time: And only after 9 minutes we create the first route ever. The second one is created after 15 minutes, and from that point we create a number of them So it seems that nothing useful is happening for the first 2 minutes, and then between 3m30 and 9m30\nOK - so I think that what is happening is that all controllers are sharing GCE interface (and thuse they have common throttling). So if one controller is generating a lot of API calls, then other controllers may be throttled. has a hypothesis that it may be caused by nodecontroller.\nOne thing my PR didn't address (because it was late): Now we have some obnoxious differences in logging when you go to make a request, because the versus could actually be absorbing a fair amount of ratelimiter.", "commid": "kubernetes_issue_26119", "tokennum": 488}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2ed83e725cf9d363ab334bf9a5336f56f2d9bc7e0271efc453b62f771a51b631", "query": "package gce import ( <ins> \"net/http\" \"net/http/httptest\" </ins> \"reflect\" \"testing\" compute \"google.golang.org/api/compute/v1\" <ins> \"k8s.io/kubernetes/pkg/util/flowcontrol\" </ins> \"k8s.io/kubernetes/pkg/util/rand\" <ins> utiltesting \"k8s.io/kubernetes/pkg/util/testing\" </ins> ) func TestGetRegion(t *testing.T) {", "positive_passages": [{"docid": "doc-en-kubernetes-bf24c8733a67a958496376416be2eb636c6e4bfb94999815173220461c93fd0c", "text": "It could before because of the operation rate limiter and operation polling anyways, but now could be worse.\n- yes I'm aware of that. And probably this is exactly the case here.\nI got fooled by that - I guess we should fix it somehow.\nOne approach to fixing it is a similar approach to the operation polling code, but in the : warn if we ratelimited for more than N seconds (and dump the request or something? not clear how to clarify what we were sending).\nI found something else - Kubelet is also building GCE interface: We have 2000 kubelets, so if all of them send multiple requests to GCE, we may hit limits.\nAny idea in what circumstances Kubelet will contact cloud provider?\nHmm - it seems it contacts GCE exactly once at the beginning. So it doesn't explain much.\nI think it's only here: I've rarely seen GCE ratelimit readonly calls, in practice, and kubelets come up pretty well staggered.\nOK - so with logs that I , it is pretty clear that we are very heavily throttled on GCE api calls. In particular, when I was running 1000-node cluster, I see lines where we were throttle for 1m30. I'm pretty sure it's significantly higher in 2000-node cluster. I'm going to investigate a bit more where all those reuqests come from.\nActually - it seems that we have a pretty big problem here. Basically, Kubelet seems to send a lot of requests to GCE. So to clarify: every time Kubelet is updating NodeStatus (so every 10s by default) it is sending an API call to GCE to get it's not addresses: that means, that if we have 2000 nodes, kubelets generate 200 QPS to GCE (which is significantly more than we can afford) We should think how to solve this issue, but I think the options are: increasing QPS quota or calling GCE only once per X statusUpdates.\nThe second issue is that we are throttled at the controller level too, and this one I'm tryin to understand right now.", "commid": "kubernetes_issue_26119", "tokennum": 457}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2ed83e725cf9d363ab334bf9a5336f56f2d9bc7e0271efc453b62f771a51b631", "query": "package gce import ( <ins> \"net/http\" \"net/http/httptest\" </ins> \"reflect\" \"testing\" compute \"google.golang.org/api/compute/v1\" <ins> \"k8s.io/kubernetes/pkg/util/flowcontrol\" </ins> \"k8s.io/kubernetes/pkg/util/rand\" <ins> utiltesting \"k8s.io/kubernetes/pkg/util/testing\" </ins> ) func TestGetRegion(t *testing.T) {", "positive_passages": [{"docid": "doc-en-kubernetes-b1dad1b374e4c58d925d9fef62d9846d5e0e5eda04aecdd78a124036a36cf31c", "text": "- that said, any rate-limitting on our side, will not solve the kubelet-related problem\nHmm - actually looking into implementation it seems that NodeAddresses are only contacting metadata server, so I'm not longer that convinced...\nAlso, I think that important thing is that a single call to GCE API can translate to multiple api calls to GCE. In particular - CreateRoute translates to: get instance insert route a bunch of getOperation (until this is finished)\nOK - so I think that what is happening here is that since CreateRoute translates to: get instance insert route a bunch of getOperations That means that if we call say 2000 CreateRoute() at the same time, all of them will try to issue: getInstance at the beginning. So we will quickly accumulate 2000 GET requests in the queue. Once they are processed, we generate the \"POST route\" then for any processed. So It's kind of expected what is happening here. So getting back to the Zach`s PR - I think that throttling POST and GET and OPERATION calls separate is kind of good idea in general.\nBut I still don't really understand why do we get \"RateLimitExceeded\". Is that because of Kubelets?\nI think that one problem we have at the RouteController level is that if CreateRoute fails, we simply don't react on it. And we will wait at least 5 minutes before even retrying it. We should add some retries at the route controller level too. I will send out some short PR for it.\nBut I still don't understand why do we get those \"RateLimitExceeded\" error\nOK - so as an update. In GCE, we have a separate rate-limit for number of in-flight CreateRoute call per project. is supposed to address this issue.\nOK - so this one is actually fixed. I mean that it is still long, but currently it's purely blocked on GCE.\nAs a comment - we have an internal bug for it already.", "commid": "kubernetes_issue_26119", "tokennum": 438}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2eda084ecb25b594e923a9f1e4a72c64945109105af7662dd45b827669ac9170", "query": "if err != nil { assert.NoErrorf(t, err, \"unable to create temp file\") } stdoutBuf := &bytes.Buffer{} stderrBuf := &bytes.Buffer{} containerID := \"fake-container-id\"", "positive_passages": [{"docid": "doc-en-kubernetes-d28453dfc6bcf829133f35627fac482c86b9caf8a20943cea67f030688a8c436", "text": "Runs k8s with master golang: test Failure was observed on Aug 25th, it is passing after that. However it can be reproduced with stress tool. No response No response It is failing on both ppc and x86 architectures. Steps to reproduce: up golang tip version. clone kubernetes master /sig testing\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\nit is a sig node test, sig testing charter is not about doing or maintain tests, we need to remove that old mindset of having a QA department, that is not how software development works or should work :) Besides, thanks for spotting it and submittn a patch /sig node /remove-sig testing\nFlaky in\nmerging this PR will fix the issue", "commid": "kubernetes_issue_121564", "tokennum": 237}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2ef1fe16c8de0656f8469dcafcde90ca7177dbf8a16a0bc13845a7e93f501182", "query": "} // writeLogs writes logs into stdout, stderr. <del> func (w *logWriter) write(msg *logMessage) error { </del> <ins> func (w *logWriter) write(msg *logMessage, addPrefix bool) error { </ins> if msg.timestamp.Before(w.opts.since) { // Skip the line because it's older than since return nil } line := msg.log <del> if w.opts.timestamp { </del> <ins> if w.opts.timestamp && addPrefix { </ins> prefix := append([]byte(msg.timestamp.Format(timeFormatOut)), delimiter[0]) line = append(prefix, line...) }", "positive_passages": [{"docid": "doc-en-kubernetes-1611cacb700fc7bde4bed341ff7dc392aeb6c35e6c0f63ce6a10b84981e8d04a", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Docker has a hardcoded 16K limit on log line length, which splits lines longer than that into multiple messages in the log file. in , however, doesn't account for this when is set to and prints the timestamp in front of every entry in the log file instead of every logical line. This leads to random timestamps appearing in the middle of log lines, potentially breaking the applications that parse these logs. What you expected to happen: inserts timestamps once per logical line, so original log data is preserved. Alternatively, allow API to request the logs in a sane format like JSON, which would allow merging the lines back and combining them with the timestamps more intelligently on the application side. How to reproduce it (as minimally and precisely as possible): Create : apiVersion: v1 kind: Pod metadata: name: log-lines spec: containers: name: main image: busybox command: ['sh', '-c', 'while sleep 1; do echo -n ; for i in $(seq 1 ); do echo -n A; done; echo ; done'] Start the pod with Fetch the logs with , or using the API () Observe random timestamps inserted in the middle of the log lines. Environment: Kubernetes version (use ):\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI will work on it. /sig cli /remove-sig node\nThe logs are being corrupted by the API endpoint in kubelet, so shouldn't it be in scope of SIG node?\nThe log is not corrupted by k8s. The same log could be got using \"docker container logs -t CONTAINERID\" I think you should post your requirement to Docker.", "commid": "kubernetes_issue_77603", "tokennum": 465}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2ef1fe16c8de0656f8469dcafcde90ca7177dbf8a16a0bc13845a7e93f501182", "query": "} // writeLogs writes logs into stdout, stderr. <del> func (w *logWriter) write(msg *logMessage) error { </del> <ins> func (w *logWriter) write(msg *logMessage, addPrefix bool) error { </ins> if msg.timestamp.Before(w.opts.since) { // Skip the line because it's older than since return nil } line := msg.log <del> if w.opts.timestamp { </del> <ins> if w.opts.timestamp && addPrefix { </ins> prefix := append([]byte(msg.timestamp.Format(timeFormatOut)), delimiter[0]) line = append(prefix, line...) }", "positive_passages": [{"docid": "doc-en-kubernetes-495f248c0af4a1a8db07569505db46eac9f11be4907de183bc6923cd7882b142", "text": "Please refer following code Line 50 ~ 52 if config.Timestamps { logLine = append([]byte(msg.Timestamp.Format(jsonmessage.RFC3339NanoFixed)+\" \"), logLine...) }\nkubelet doesn't rely on Docker when reading logs, it reads the files itself (see the code linked in the issue). I don't think Docker would change the forced line splitting (see for example), so this should be fixed in Kubernetes.\nYour are right and kubelet read log file from host such as /var/log/pods/pods/NAMESPACEPOD-NAMExxx/....(JSON format) I will post a PR for it. /remove-sig cli /sig node\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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 .", "commid": "kubernetes_issue_77603", "tokennum": 539}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2ef1fe16c8de0656f8469dcafcde90ca7177dbf8a16a0bc13845a7e93f501182", "query": "} // writeLogs writes logs into stdout, stderr. <del> func (w *logWriter) write(msg *logMessage) error { </del> <ins> func (w *logWriter) write(msg *logMessage, addPrefix bool) error { </ins> if msg.timestamp.Before(w.opts.since) { // Skip the line because it's older than since return nil } line := msg.log <del> if w.opts.timestamp { </del> <ins> if w.opts.timestamp && addPrefix { </ins> prefix := append([]byte(msg.timestamp.Format(timeFormatOut)), delimiter[0]) line = append(prefix, line...) }", "positive_passages": [{"docid": "doc-en-kubernetes-2f614c9ad06da31fe9313a5b2eaea6d6901d55cba8508cf5ebe57105d301c4f6", "text": "Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\nStale 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\nI saw the attempt fixing this but it was scary (echo this comment: ). I suggested a way it may be improved. Also the proposed fix didn't introduce any e2e tests to validate that runtime behavior is not changed and runtimes keep the no-newline-on-splitted-log logic. are you or anybody on this thread are still interested to work on this? Please re-open if so. Meanwhile closing this ahead of bot doing it because the inactivity. /close\nClosing this issue. <detailsIn response to : I saw the attempt fixing this but it was scary (echo this comment: ). I suggested a way it may be improved. Also the proposed fix didn't introduce any e2e tests to validate that runtime behavior is not changed and runtimes keep the no-newline-on-splitted-log logic. Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_77603", "tokennum": 493}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2ef1fe16c8de0656f8469dcafcde90ca7177dbf8a16a0bc13845a7e93f501182", "query": "} // writeLogs writes logs into stdout, stderr. <del> func (w *logWriter) write(msg *logMessage) error { </del> <ins> func (w *logWriter) write(msg *logMessage, addPrefix bool) error { </ins> if msg.timestamp.Before(w.opts.since) { // Skip the line because it's older than since return nil } line := msg.log <del> if w.opts.timestamp { </del> <ins> if w.opts.timestamp && addPrefix { </ins> prefix := append([]byte(msg.timestamp.Format(timeFormatOut)), delimiter[0]) line = append(prefix, line...) }", "positive_passages": [{"docid": "doc-en-kubernetes-2e8714433462894a36e35ec9c24fb7c5a56d0558d2953a09bb86920b184c167e", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nYou can't reopen an issue/PR unless you authored it or you are a collaborator. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/remove-lifecycle rotten /reopen will fix it.\nReopened this issue. <detailsIn response to : /remove-lifecycle rotten /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/triage accepted\nThe Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.", "commid": "kubernetes_issue_77603", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2ef1fe16c8de0656f8469dcafcde90ca7177dbf8a16a0bc13845a7e93f501182", "query": "} // writeLogs writes logs into stdout, stderr. <del> func (w *logWriter) write(msg *logMessage) error { </del> <ins> func (w *logWriter) write(msg *logMessage, addPrefix bool) error { </ins> if msg.timestamp.Before(w.opts.since) { // Skip the line because it's older than since return nil } line := msg.log <del> if w.opts.timestamp { </del> <ins> if w.opts.timestamp && addPrefix { </ins> prefix := append([]byte(msg.timestamp.Format(timeFormatOut)), delimiter[0]) line = append(prefix, line...) }", "positive_passages": [{"docid": "doc-en-kubernetes-422d52914e9725e7355cb5e937e13c24e15f273f63951d92fe52d86a167487cb", "text": "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]:\nThe 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]:\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_77603", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2ef1fe16c8de0656f8469dcafcde90ca7177dbf8a16a0bc13845a7e93f501182", "query": "} // writeLogs writes logs into stdout, stderr. <del> func (w *logWriter) write(msg *logMessage) error { </del> <ins> func (w *logWriter) write(msg *logMessage, addPrefix bool) error { </ins> if msg.timestamp.Before(w.opts.since) { // Skip the line because it's older than since return nil } line := msg.log <del> if w.opts.timestamp { </del> <ins> if w.opts.timestamp && addPrefix { </ins> prefix := append([]byte(msg.timestamp.Format(timeFormatOut)), delimiter[0]) line = append(prefix, line...) }", "positive_passages": [{"docid": "doc-en-kubernetes-0e28d298340708e57a780633dba41fa2a744d19c9ab3d061a118f6b1e6c3d902", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI received a bug report about this issue. The root cause is that the buffer reads up to a new line. If the line is greater than 4096 bytes and '--timestamps' is turrned on the kubelet will write the timestamp and the partial log line. We will need to refactor the ReadLogs function to allow for a partial line read.", "commid": "kubernetes_issue_77603", "tokennum": 104}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2efe1506faddd22c9f3e952ce0348d89809254da8f8c21bf0e811faa86de9ac2", "query": "// in node status. By calling this function (GetVolumesToReportAttached), node status should be updated, and the volume // will not need to be updated until new changes are applied (detach is triggered again) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <del> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw) </del> <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw, volumeAttachedCheckTimeout) </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-dc8aac09a0e4bb26f9dc5f50aef7f845ea9d7c4b925d34b9f6eda044925f80f5", "text": "TestRunOneVolumeDetachFailNodeWithReadWriteOnce 4 times since 03-19 23:00 PDT, intermittently ! https://k8s- Still investigating whether this is a tolerable flake or not with more history than testgrid view, or otherwise would appreciate input from anyone with expertise in this test, especially as regards to whether this should be a blocker for tomorrows beta cut. maybe: /sig storage /sig testing\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nis already open for this, looks like it is attempting to fix it\nthank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. /close\nClosing this issue. <detailsIn response to : thank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. 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", "commid": "kubernetes_issue_116774", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2efe1506faddd22c9f3e952ce0348d89809254da8f8c21bf0e811faa86de9ac2", "query": "// in node status. By calling this function (GetVolumesToReportAttached), node status should be updated, and the volume // will not need to be updated until new changes are applied (detach is triggered again) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <del> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw) </del> <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw, volumeAttachedCheckTimeout) </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-aef7ec00dc93616f97177ca3d23f28217445848b34c429e5746962ea28329f43", "text": "pull-kubernetes-unit TestRunOneVolumeDetachFailNodeWithReadWriteOnce Jan 7th, 2022 Check volume <fake-plugin/volume-nameis reported as attached to node <fail-detach-node, got false, expected true No response_ /sig storage\n/cc\nthis is the top unit test flake according to\ncc\nThe 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]:\nI think this test is no longer flaky by checking the test grid, close it now.\nUnfortunately this does still seem to be flaky: Here was the output from : /reopen\nReopened this issue. <detailsIn response to : Unfortunately this does still seem to be flaky: 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\n/remove-lifecycle stale\nstill the case\nHow about adding some logging to help troubleshoot this? I looked at it a little, but it is hard to tell which part of the test is failing. PR\n/\nThis is still happening\n/triage accepted\nFrom the logs, in the OneVolumeDetachFailNodeWithReadWriteOnce test, succeeded, but the next verification failed. In verifyVolumeAttachedToNode, the attachState is from calling and within asw, it calls . In verifyVolumeReportedAsAttachedToNode, the volumes are obtained from calling , it seems that the node is not in asw.nodesToUpdateStatusFor at this step. Cannot reproduce locally. I tried to run the test 100 times locally with debug.Stack()... 3 * 100 times all passed.\nTried to run stress test on my linux machine as well but still cannot reproduce. Command: Result: Also tried running n process in parallel. Command: Result:\nIt seems like it happens more frequently.", "commid": "kubernetes_issue_107414", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2efe1506faddd22c9f3e952ce0348d89809254da8f8c21bf0e811faa86de9ac2", "query": "// in node status. By calling this function (GetVolumesToReportAttached), node status should be updated, and the volume // will not need to be updated until new changes are applied (detach is triggered again) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <del> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw) </del> <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw, volumeAttachedCheckTimeout) </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-62e47fd83b7fc1cc39259be1688a9f133b9cd2dc48247eb5d858fae7fd13955b", "text": "But I may have no time to dig into the cause. Let's see.\ncc as the test author.\nThe problem is that this test has a lot of dependency on the sleeps that are hardcoded with a very narrow scope, but our CI seems to be able to stress it much more. As soon as you slightly change one of the sleep duration it starts to flake locally The test can not make an assumption that timing is perfect, even more in the sub second range can someone in sig-storage review this test and make it less dependant on those tight sleeps?\nAccording to most failures, it failed at Line 660. Let me run some stress locally. with 250ms sleep with 100ms sleep\nI agree this test case is too brittle due to its specific timing dependencies. To fix this, I suggest reworking the test case to: 1) Add retry with timeout to wait for final conditions 2) Remove the intermediate timing-based state transition checks. Instead, we can keep track of state transitions in the Fakes and validate those stats. wdyt?\nFriendly ping from 1.27 CI Signal that this test is still a noisy flake on the master-blocking dashboard as CI Signal has flagged it in and", "commid": "kubernetes_issue_107414", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2f1dfce6af80261f312f4da284e389cdd710fc4e958bcd17e7b86c481d7b3b40", "query": "{\"name\" : \"BalancedResourceAllocation\", \"weight\" : 1}, {\"name\" : \"ServiceSpreadingPriority\", \"weight\" : 1}, {\"name\" : \"EqualPriority\", \"weight\" : 1} <del> ] </del> <ins> ], \"hardPodAffinitySymmetricWeight\" : 10 </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-88466bc637a805045217da94feabbdbd3df0ba52cd0d9904e95d3984c4cf4efa", "text": "( noticed this) HardPodAffinitySymmetricWeight should be in the , not in KubeSchedulerConfiguration If/when fixing this, we need to be careful to do it in a backward-compatilble way.\nDo you mean ? It seems scheduler policy config's args can not passed to FitPredicates; it need to update related interface. For the : mark to be deprecated and set scheduler policy config to HardPodAffinitySymmetricWeight if policy config is empty.\nAre you working on this? if no, I can take it.\n, nop; please go ahead.\n/ / / , When reviewing the PR, there's one question on : the default value of is 1, which means the weight (1) will always add to priorities if term matched (), does it our expectation? And the user has to set it to 0 to disable it. IMO, the default value of should be 0.\nThe value 1 (instead of 0) was chosen so that if you say A must run with B, there is an automatic preference that B should run with A. This seems like reasonable behavior.\nThanks very much; reasonable case to me. But it seems we can not disable it: if set to 0, the default funcs will set it to default (1); similar result to un-set. Anyway, no user complain this now :).", "commid": "kubernetes_issue_43845", "tokennum": 306}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2f71fb7009dc20d8d58c2d365593cfa672d5c4eb60a86fcb05b73f3481fa6cf4", "query": "numErrs: 0, }, { <ins> name: \"invalid duplicate targetports (number with same protocol)\", tweakSvc: func(s *api.Service) { s.Spec.Type = api.ServiceTypeClusterIP s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"q\", Port: 1, Protocol: \"TCP\", TargetPort: intstr.FromInt(8080)}) s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"r\", Port: 2, Protocol: \"TCP\", TargetPort: intstr.FromInt(8080)}) }, numErrs: 1, }, { name: \"invalid duplicate targetports (name with same protocol)\", tweakSvc: func(s *api.Service) { s.Spec.Type = api.ServiceTypeClusterIP s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"q\", Port: 1, Protocol: \"TCP\", TargetPort: intstr.FromString(\"http\")}) s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"r\", Port: 2, Protocol: \"TCP\", TargetPort: intstr.FromString(\"http\")}) }, numErrs: 1, }, { name: \"valid duplicate targetports (number with different protocols)\", tweakSvc: func(s *api.Service) { s.Spec.Type = api.ServiceTypeClusterIP s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"q\", Port: 1, Protocol: \"TCP\", TargetPort: intstr.FromInt(8080)}) s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"r\", Port: 2, Protocol: \"UDP\", TargetPort: intstr.FromInt(8080)}) }, numErrs: 0, }, { name: \"valid duplicate targetports (name with different protocols)\", tweakSvc: func(s *api.Service) { s.Spec.Type = api.ServiceTypeClusterIP s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"q\", Port: 1, Protocol: \"TCP\", TargetPort: intstr.FromString(\"http\")}) s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"r\", Port: 2, Protocol: \"UDP\", TargetPort: intstr.FromString(\"http\")}) }, numErrs: 0, }, { </ins> name: \"valid type - cluster\", tweakSvc: func(s *api.Service) { s.Spec.Type = api.ServiceTypeClusterIP", "positive_passages": [{"docid": "doc-en-kubernetes-aa91440105d9e0a880514623ff11a0ea2fc9d1181a696540d8af19c86c926acb", "text": "It is possible to express a Service where multiple front-side ports target the same back-side port. This is not very useful and may cause trouble for implementations of Services. `\njust for the purpose of clarity, are you requesting that duplicate targetPorts should be rejected or the opposite? PS: I am new to Kubernetes so please pardon the dumb question :)\nI think that should probably be rejected at validation unless we have a good reason WHY we need that.\nAye aye, thanks for the clarificiation!\n/assign\nGitHub didn't allow me to assign the following users: xiangpengzhao. Note that only can be assigned. <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\nwhat problems did this cause with services? This change broke backwards compatibility for services that depended on this feature. For example, lets take the load balancer service The load balancer here terminates SSL so the backend is always port 80; however, you want to make sure you support both protocols so having the same targetPort here is a valid use case.\nThis is an interesting (ab)use of Service. Not really what I had in mind - the LB in a Service is generally assumed to be L4. I'll try to dredge up the issues that this was causing.\nFYI, the does non layer4 things as well.\nOne issue is that this REQUIRES connection tracking when we otherwise might not need it. Consider two ServicePorts: my-service:80 mys-service:443 Let's say we map both services to a backend on port 8080, but we pass-through the VIP, so the pod sees packets as dest = my-service:8080. We MUST conntrack this VIP because we don't know whether to map the src port to 80 or 443. If service backends have unique TargetPorts, then we wouldn't have this issue. Port rewrites are at worst stateless, and at best can engage direct-return mode (no rewrites). It's worth noting that the PR which fixes this, which is proposed for revert, doesn't quite go far enough. It prevents a Service from using a given number twice and from using a given name twice, but not from using a number and a name that resolves to that number.", "commid": "kubernetes_issue_47222", "tokennum": 515}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2f71fb7009dc20d8d58c2d365593cfa672d5c4eb60a86fcb05b73f3481fa6cf4", "query": "numErrs: 0, }, { <ins> name: \"invalid duplicate targetports (number with same protocol)\", tweakSvc: func(s *api.Service) { s.Spec.Type = api.ServiceTypeClusterIP s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"q\", Port: 1, Protocol: \"TCP\", TargetPort: intstr.FromInt(8080)}) s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"r\", Port: 2, Protocol: \"TCP\", TargetPort: intstr.FromInt(8080)}) }, numErrs: 1, }, { name: \"invalid duplicate targetports (name with same protocol)\", tweakSvc: func(s *api.Service) { s.Spec.Type = api.ServiceTypeClusterIP s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"q\", Port: 1, Protocol: \"TCP\", TargetPort: intstr.FromString(\"http\")}) s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"r\", Port: 2, Protocol: \"TCP\", TargetPort: intstr.FromString(\"http\")}) }, numErrs: 1, }, { name: \"valid duplicate targetports (number with different protocols)\", tweakSvc: func(s *api.Service) { s.Spec.Type = api.ServiceTypeClusterIP s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"q\", Port: 1, Protocol: \"TCP\", TargetPort: intstr.FromInt(8080)}) s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"r\", Port: 2, Protocol: \"UDP\", TargetPort: intstr.FromInt(8080)}) }, numErrs: 0, }, { name: \"valid duplicate targetports (name with different protocols)\", tweakSvc: func(s *api.Service) { s.Spec.Type = api.ServiceTypeClusterIP s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"q\", Port: 1, Protocol: \"TCP\", TargetPort: intstr.FromString(\"http\")}) s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"r\", Port: 2, Protocol: \"UDP\", TargetPort: intstr.FromString(\"http\")}) }, numErrs: 0, }, { </ins> name: \"valid type - cluster\", tweakSvc: func(s *api.Service) { s.Spec.Type = api.ServiceTypeClusterIP", "positive_passages": [{"docid": "doc-en-kubernetes-4a483a3c82b1bc41aa37a9f41461962211ab2500ff27fab076c9dbd88f68a578", "text": "That is a much trickier (impossible to do statically) proposition. :( Kind of a mess for getting high-perf Service networking.\nwas this an issue that came up during performance testing or IRL?\nAnyone has a workaround to deal with this? I think there is a lot of people using AWS ELBs on this way\nif your use-case is Ingress, then you can set . This should avoid generating the invalid Service spec. Obviously, you will lose the redirect behavior.\nThis is not an abuse of Service, but a quite common and wide-adopted pattern, especially in the AWS world.\nyou can't re-open an issue/PR unless you authored it or you are assigned to it. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nyou can't re-open an issue/PR unless you authored it or you are assigned to it. <detailsIn response to : /assign /reopen for further discussion 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\n/reopen for further discussion.\nI suspect we should probably revert the original PR. While I understand it might not have been the intention for Services, if I understand this correctly then it's a breaking change to a v1 API. Can we at least point to any documentation that indicates this was a code bug rather than a supported behavior?\nSentiment on today's sig call was that we should revert the original commit, since it broke lots of users, and then revisit to see if there's another solution.\nFYI: the revert PR is\nIssues 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\nStale 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 .", "commid": "kubernetes_issue_47222", "tokennum": 495}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2f71fb7009dc20d8d58c2d365593cfa672d5c4eb60a86fcb05b73f3481fa6cf4", "query": "numErrs: 0, }, { <ins> name: \"invalid duplicate targetports (number with same protocol)\", tweakSvc: func(s *api.Service) { s.Spec.Type = api.ServiceTypeClusterIP s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"q\", Port: 1, Protocol: \"TCP\", TargetPort: intstr.FromInt(8080)}) s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"r\", Port: 2, Protocol: \"TCP\", TargetPort: intstr.FromInt(8080)}) }, numErrs: 1, }, { name: \"invalid duplicate targetports (name with same protocol)\", tweakSvc: func(s *api.Service) { s.Spec.Type = api.ServiceTypeClusterIP s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"q\", Port: 1, Protocol: \"TCP\", TargetPort: intstr.FromString(\"http\")}) s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"r\", Port: 2, Protocol: \"TCP\", TargetPort: intstr.FromString(\"http\")}) }, numErrs: 1, }, { name: \"valid duplicate targetports (number with different protocols)\", tweakSvc: func(s *api.Service) { s.Spec.Type = api.ServiceTypeClusterIP s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"q\", Port: 1, Protocol: \"TCP\", TargetPort: intstr.FromInt(8080)}) s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"r\", Port: 2, Protocol: \"UDP\", TargetPort: intstr.FromInt(8080)}) }, numErrs: 0, }, { name: \"valid duplicate targetports (name with different protocols)\", tweakSvc: func(s *api.Service) { s.Spec.Type = api.ServiceTypeClusterIP s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"q\", Port: 1, Protocol: \"TCP\", TargetPort: intstr.FromString(\"http\")}) s.Spec.Ports = append(s.Spec.Ports, api.ServicePort{Name: \"r\", Port: 2, Protocol: \"UDP\", TargetPort: intstr.FromString(\"http\")}) }, numErrs: 0, }, { </ins> name: \"valid type - cluster\", tweakSvc: func(s *api.Service) { s.Spec.Type = api.ServiceTypeClusterIP", "positive_passages": [{"docid": "doc-en-kubernetes-c9520d012b388262634de2c95cda13e5277a086c4973e0f847d3a162dd04c237", "text": "Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close", "commid": "kubernetes_issue_47222", "tokennum": 78}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2f894dbc8003b4e91421b7ccb30bce275186633f85a32d8cd76f3a5b5ce777ff", "query": "MASTER_IP=\"\" MINION_IPS=\"\" <ins> KUBECTL_PATH=${KUBE_ROOT}/cluster/ubuntu/binaries/kubectl </ins> # Assumed Vars: #   KUBE_ROOT function test-build-release {", "positive_passages": [{"docid": "doc-en-kubernetes-6ad186288ef256533240c5bfccb6ba92929a47585cc346f791c0fbaeeb93c979", "text": "Though I have successfully installed kubernetes via :smiley: , still want to point out this doc missing the step to install . Thus, if user just follow the guide in the doc without having much knowledge about kubernetes, he/she would get error \"It looks as if you don't have a compiled kubectl binary\" during the step of . Manually install kubectl on at least master node should be necessary (suggest to let user also install on minion node for convenience), any way, the installation step is .\nI forget to mention that.I will update the doc this tuned\nI update the scripts in pr , you can try it now. I copied the kubectl binary from the kubernetes release and put it in , so there is no extra step for user to manually download . Actually, in the first version of ubuntu k8s deployment, I copied the to every node, but I think it is an overhead, so I removed it.I think this is just enough.\nDoc update : Move the kubectl into the PATH, it may need sudo privilege so I decide not do for the user.\nHave the same issue, please update the doc ASAP.\nGreat job :+1:\nAlso ran into this bug after recklessly running ( instead of ) :)", "commid": "kubernetes_issue_8373", "tokennum": 276}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2f8ca2de51486d0fe4e0aa407ddd578f4a27e7eb894a84625d48dc6a575bc831", "query": "pluginapi.RegisterDevicePluginServer(m.server, m) go m.server.Serve(sock) <del> // Wait till grpc server is ready. for i := 0; i < 10; i++ { services := m.server.GetServiceInfo() if len(services) > 0 { break } time.Sleep(1 * time.Second) </del> <ins> _, conn, err := dial(m.socket) if err != nil { return err </ins> } <ins> conn.Close() </ins> log.Println(\"Starting to serve on\", m.socket) return nil", "positive_passages": [{"docid": "doc-en-kubernetes-3e8f9b25d1f3d96c25ea3e7b882f872baf67d41cad6a3bbcf2df0e192dbdfda5", "text": "This is not 100% reproducable in my cluster. There is 20% chance of failing in my environment.\n/area hw-accelerators mentioned a root cause that might be due to unit tests sharing the same Unix socket and interfering with each others. cc\nCan you please share latest commit id of your code base using ?\nThanks very much, can you try the follow command please:\n/assign\nThe latest commit id of my code base:\nI found this is not 100% reproducable in my cluster. There is 20% chance of failing in my environment.\nResult of go test command:\n/sig scheduling\nThanks!\nHi, does these unit tests pass with PR\nI run 100 times without failure.\nGood to here that, Nice work! Thanks!", "commid": "kubernetes_issue_58281", "tokennum": 154}], "negative_passages": []}
{"query_id": "q-en-kubernetes-2fa3f0d066d2651904a6ba3b4e3674310fa17a90bb0ce1f2b3f3bb3d594d2e41", "query": "return c.check(r) } <ins> // getExcludedChecks extracts the health check names to be excluded from the query param func getExcludedChecks(r *http.Request) sets.String { checks, found := r.URL.Query()[\"exclude\"] if found { return sets.NewString(checks...) } return sets.NewString() } </ins> // handleRootHealthz returns an http.HandlerFunc that serves the provided checks. func handleRootHealthz(checks ...HealthzChecker) http.HandlerFunc { return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) { failed := false <ins> excluded := getExcludedChecks(r) </ins> var verboseOut bytes.Buffer for _, check := range checks { <ins> // no-op the check if we've specified we want to exclude the check if excluded.Has(check.Name()) { excluded.Delete(check.Name()) fmt.Fprintf(&verboseOut, \"[+]%v excluded: okn\", check.Name()) continue } </ins> if err := check.Check(r); err != nil { // don't include the error since this endpoint is public.  If someone wants more detail // they should have explicit permission to the detailed checks.", "positive_passages": [{"docid": "doc-en-kubernetes-01cc291fb1d6afeae9b284d60dd407b578a72d26e4c50043cbdf654c92184c45", "text": "What would you like to be : Add support to the kube-apiserver so that we can disable health-checks via query params. Why is this needed: Currently, the healthz endpoint is inflexible in that any and all health checks are currently executed when the endpoint is hit. Since the kube-apiserver only currently supports a liveness check, this means all persistent health check failures will eventually result in a kubelet driven restart. However, this may not be desirable behavior if you have additional monitoring services layered on top of your control plane. For instance, take the etcd failure from the perspective of the kube-apiserver. Currently, persistent failures during the etcd health check from the api-server healthz endpoint will cause the kube-apiserver to be restarted. This sometimes helps (in the case of a faulty etcd-client connection) but also can be detrimental (the kube-apiserver restarts until the etcd cluster is functioning, then the kube-apiserver bombards the etcd cluster with requests to update local caches, saturating the etcd cluster with requests, causing it to timeout on its own liveness probes and trigger a kubelet-driven restart). Let's say that we could now disable etcd from our liveness health check. Then if we had an external monitoring service, we could ask independently ask etcd if it was healthy and we could also ask the kube-apiserver if it thought etcd was unhealthy. Based on the combination of those answers, we could enable more intelligent responses to certain situation, like restarting the kube-apiserver when it thought etcd was unhealthy but etcd was actually reporting as healthy but not doing so when etcd was actually unhealthy. This feature is backwards-compatible and opt-in. There would be no impact to existing behavior unless these query params are actually used. /sig api-machinery /kind feature\n/cc\nSGTM\n/assign", "commid": "kubernetes_issue_70591", "tokennum": 432}], "negative_passages": []}
{"query_id": "q-en-kubernetes-303a059b91b2663b4d81aa537984724b34f1d55f48702944031ae88fedb34e9e", "query": "// Score is a list of plugins that should be invoked when ranking nodes that have passed the filtering phase. Score *PluginSet <del> // NormalizeScore is a list of plugins that should be invoked after the scoring phase to normalize scores. NormalizeScore *PluginSet </del> // Reserve is a list of plugins invoked when reserving a node to run the pod. Reserve *PluginSet", "positive_passages": [{"docid": "doc-en-kubernetes-65d9c28fb77fe0bb882df060209fc22bf399af9c3b9dfe5829b0e5a45dc20b3d", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Consolidate ) into Score plugin set in config API. Why is this needed: NormalizeScore extension point is implemented in . We decided to treat NormalizeScore as an \"optional\" step of Score plugin, see . However, we deferred the removal of due to API review delays. Now that PR was merged. We can start the actual removal from the API and start the API review process. /sig scheduling\n/assign", "commid": "kubernetes_issue_80908", "tokennum": 113}], "negative_passages": []}
{"query_id": "q-en-kubernetes-304fddf5a53f36ed52ec99d407b40ffa69205cac344d63d312c9934ccea99292", "query": "}) nc.leaseLister = leaseInformer.Lister() <del> nc.leaseInformerSynced = leaseInformer.Informer().HasSynced </del> <ins> if utilfeature.DefaultFeatureGate.Enabled(features.NodeLease) { nc.leaseInformerSynced = leaseInformer.Informer().HasSynced } else { // Always indicate that lease is synced to prevent syncing lease. nc.leaseInformerSynced = func() bool { return true } } </ins> nc.nodeLister = nodeInformer.Lister() nc.nodeInformerSynced = nodeInformer.Informer().HasSynced", "positive_passages": [{"docid": "doc-en-kubernetes-09aa0bcb31564b73405d3dff3c57f03e717ee20452470641ef888656e6997574", "text": "Reboot tests have been failing since 10/12 Dashboard: https://k8s- Sample Failure: https://k8s- This test failure will block 1.13 beta, so please let's fix it before then. Thanks! /sig cluster-lifecycle /kind failing-test /priority important-soon\nNote: this failure is similar to but is not the same failure, according to This is a consistent failure rather than a flake, and all nodes are failing to reboot. It's also been failing consistently since 10/11. /cc\nCopying my notes here: Looking at one recent test run: The test failed because kubelet never became \"not ready\": When looking at one of the kubelet logs, I do see that kubelet had problems making Node updates to the api server: Errors continue until kubelet is restarted 8 minutes later (the test times out at 2 minutes):\nSo it seems like even though kubelet is unable to update its Node status, the Node is still showing up as Ready\nAdding sig-node to this discussion: /sig node\nI'm trying to repro on a dev 1.11/1.12 cluster so we can get master logs for the node controller\n/cc adding from sig-node\n/assign\nwas the only PR that went in during that time (if we don't count infra or gke changes). This PR touches the node controller and changes the node heartbeat, so it could be the culprit. I was able to grab the logs from the mater was it was still up. Snippet from the kube-controller- showed a lot of error: The PR author is out for a couple of days, so he cannot investigate. I can look at it later today maybe. If anyone from GKE wants to help, I can send you all the logs.\nThe node controller doesn't seem to be working at all as it wasn't marking the nodes not ready. suggested that the api group may not have been whitelisted in GKE, so I checked and that seemed to be true. We can whitelist it, but for an alpha feature, it should not be properly gated and not affect production. We can revert PR to unblock release, and wait for to re-submit a patched PR. /cc\nThanks for debugging this! Just got time to take a quick look. Does it mean should also be put behind the feature gate?", "commid": "kubernetes_issue_69786", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-304fddf5a53f36ed52ec99d407b40ffa69205cac344d63d312c9934ccea99292", "query": "}) nc.leaseLister = leaseInformer.Lister() <del> nc.leaseInformerSynced = leaseInformer.Informer().HasSynced </del> <ins> if utilfeature.DefaultFeatureGate.Enabled(features.NodeLease) { nc.leaseInformerSynced = leaseInformer.Informer().HasSynced } else { // Always indicate that lease is synced to prevent syncing lease. nc.leaseInformerSynced = func() bool { return true } } </ins> nc.nodeLister = nodeInformer.Lister() nc.nodeInformerSynced = nodeInformer.Informer().HasSynced", "positive_passages": [{"docid": "doc-en-kubernetes-7034e0c54621f512a943c26e586b687e71244f1a626e4d5c092896b001f68abd", "text": "I think reverting is a good option to unblock stuff. - creating listed may not be necessary, but setting HasSynced is (so if we have to put it after feature gate, we should put both).\nIs there any guideline on how to revert my original PR ? I haven't done it before. Just revert in my fork and submit a new PR? I also just put up a fix PR . I am fine with either submitting the fix PR or revert my original PR first.\n/reopen /assign I will manually close this after verifying the bots.\nReopening this issue. <detailsIn response to : /reopen /assign I will manually close this after verifying the bots. 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\nThis is passing in the latest test run. Thanks for the quick turnaround\nNice! Closing this now. /close\nClosing this issue. <detailsIn response to : Nice! Closing this now. /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", "commid": "kubernetes_issue_69786", "tokennum": 261}], "negative_passages": []}
{"query_id": "q-en-kubernetes-30bb2256ab855e3fa51af69ccd55a53f6024279d2fb5cbcec2b9b7a7a3026a2f", "query": "func TestIsCurrentInstance(t *testing.T) { cloud := &Cloud{ Config: Config{ <del> VMType: vmTypeVMSS, </del> <ins> VMType: vmTypeStandard, </ins> }, } testcases := []struct {", "positive_passages": [{"docid": "doc-en-kubernetes-93c0a615d6725c12b66abb2dead01e17ca700d451119b1467d3edce68f73a013", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: If computer name prefix does not match VMSS name, then Azure cloud provider will use VMSS API instead of using metadata service data. This leads to throttling, because every affected kubelet is making API requests. What you expected to happen: Azure cloud provider should use metadata service data instead of calling VMSS API when instance is current. How to reproduce it (as minimally and precisely as possible): Set computer name prefix of the VMSS to something different than default. You should observe Azure provider making requests to the VMSS API rather than using metadata service, which leads to throttling if you have multiple kubelets with this bug. Anything else we need to know?: This is bug was introduced by - returns false even if instance is current, because it expects node name to match VMSS name + instance id, however node name is derived from the computer-name-prefix which can be different than VMSS name. Node name should be matched against , not against . Environment: Kubernetes version (use ): 1.18.x and higher Cloud provider or hardware configuration: azure /sig cloud-provider\n/sig cloud-provider\n/area provider/azure\nCC\n/remove-sig cloud-provider /sig cloud-provider (trying to remove the label)\n/sig cloud-provider\nThanks for the reporting. Unfortunately, computer name prefix is not included in IMDS, so it can't be used without VMSS API for constructing the NodeName. Would check what could we do to workaround the issue.\nCan you memorize the computer name prefix in the first request to the Azure API and then use it for the isCurrentInstance check?\nopened to fix the issue. Would you like to have a look?\nI can confirm that your change should fix the problem I reported. Do you know if your fix will be to 1.18.x?\nis working on the cherry pick\nThank you for quick fix!", "commid": "kubernetes_issue_92733", "tokennum": 464}], "negative_passages": []}
{"query_id": "q-en-kubernetes-30bcfced3d39e0cc43e96b72eed597f0d92f9e0d9c06080904cfd3761abeba92", "query": "parameters[k] = v.(string) } } <ins> if snapshotProvider, ok := snapshotClass.Object[\"driver\"]; ok { snapshotter = snapshotProvider.(string) } </ins> } return testsuites.GetSnapshotClass(snapshotter, parameters, ns, suffix)", "positive_passages": [{"docid": "doc-en-kubernetes-51cd929448b3f8fa92237306f83461a030cd5dfe6702e988f5001cdfbd724eae", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: On running kubetest with external storage driver option with driver name \"\", encountered error of flag redefinition. The issue happens because: As part of this patch , a flag is defined for number of inline volumes. The driver name is used to construct the flag name. Thus, when running tests on an externally provided driver (in this instance the Persistent Disk CSI driver) with driver name \"\", a redefinition error happens since the ephemeral test suite code path is executed once for and once for External PD CSI driver. [example run command: kubetest --test --check-version-skew=false --testargs=\"-- --storage.testdriver=/path/to/gcp-compute-persistent-disk-csi-driver/test/k8s-integration/config/test-\" Test config looks something like this: { StorageClass: FromFile: ... SnapshotClass: FromFile: ... DriverInfo: Name: ... } ] What you expected to happen: Test should run and succeed. How to reproduce it (as minimally and precisely as possible): Use an test-, with driver name as \"\", and run kubetest with focus as \"External.Storage\" kubetest --test --check-version-skew=false --testargs=\"-- --storage.testdriver=/path/to/gcp-compute-persistent-disk-csi-driver/test/k8s-integration/config/test-\" Anything else we need to know?: Possible fixes options: , (), when using a FromFile or FromExistingClassName option to pass in SnapshotClass information, pickup the provisioner name from the class definition's \"driver\" field. the flag which has a dependency on driver names. (need to understand the impact of removing the command line flag) Environment: Kubernetes version (use ): latest master Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig storage\n/assign Do you know why this parameter is set as a flag and not a part of the ?\nTo me, is something that defines what the driver can do. This flag is about what the test does and not related to driver capabilities.", "commid": "kubernetes_issue_90868", "tokennum": 582}], "negative_passages": []}
{"query_id": "q-en-kubernetes-30bcfced3d39e0cc43e96b72eed597f0d92f9e0d9c06080904cfd3761abeba92", "query": "parameters[k] = v.(string) } } <ins> if snapshotProvider, ok := snapshotClass.Object[\"driver\"]; ok { snapshotter = snapshotProvider.(string) } </ins> } return testsuites.GetSnapshotClass(snapshotter, parameters, ns, suffix)", "positive_passages": [{"docid": "doc-en-kubernetes-270b31a5e196f61611ca75afa5bbde1923e891fb5ac161d33aa5adc26b5fc154", "text": "Making it depend on the driver name was probably unnecessary. A single flag for all incarnations of that test probably would have been sufficient and thus better (\"keep it simple, stupid!\" - the stupid being me here...). It also shouldn't have used the global flag set. In other words:\n/reopen I don't really want to get into the habit of defining per test case flags in There are thousands of test cases and it would be unwieldy to discover all the flags available and understand how to use them. What factors would influence how many volumes you want the test to create? Can we just hardcode a value in the test case?\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThe defaults must be usable so that users do not need to understand them. The flags can be discovered with - not ideal, but at least they show up. That's effectively what the default value for the flag does. This is a way to to run a custom stress test: the default is so low, it just tests that the feature works. By increasing it as high as the underlying CSI driver and storage system supports, one can run this (and potentially other tests) as part of stress testing. Not sure whether it's worth supporting this. It seemed worthwhile at the time, and better than hard-coding just one value.\nThe bigger issue is: how do users of the test suite actually learn what tests they run and what those tests do? I suspect the answer to that is simply \"read the source\", in which case they'll also find the knobs that can be used to tweak testing.\nSince increasing the parameter depends on the csi driver/storage system, then I would recommending splitting this up into 2 test cases: 1) test basic functionality 2) test stress scenario, and add the parameter to the driver test config similarly to other stress tests:\nAt least for the storage tests, because we are intending that they be run externally, having all the tunables in one place I think makes it easier to discover.\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close.", "commid": "kubernetes_issue_90868", "tokennum": 496}], "negative_passages": []}
{"query_id": "q-en-kubernetes-30bcfced3d39e0cc43e96b72eed597f0d92f9e0d9c06080904cfd3761abeba92", "query": "parameters[k] = v.(string) } } <ins> if snapshotProvider, ok := snapshotClass.Object[\"driver\"]; ok { snapshotter = snapshotProvider.(string) } </ins> } return testsuites.GetSnapshotClass(snapshotter, parameters, ns, suffix)", "positive_passages": [{"docid": "doc-en-kubernetes-25193f95a984c83e59d3bf61132d542700dd22032bd8c1cb3f7d9def5d988f52", "text": "If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten\nIssues 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\n/remove-lifecycle stale /help\nThis request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /remove-lifecycle stale /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\nIssues 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\n/remove-lifecycle stale\nI saw that the flag was removed in , I think we can close this one if doesn't apply anymore\n/close The flag was removed in #diff-20517805986874f69e3254bed93d59996d5a6fd571a70ab8120736ded5aafa24\nYou can't close an active issue/PR unless you authored it or you are a collaborator. <detailsIn response to : /close The flag was removed in #diff-20517805986874f69e3254bed93d59996d5a6fd571a70ab8120736ded5aafa24 </details\n/close\nClosing this issue.", "commid": "kubernetes_issue_90868", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-30bcfced3d39e0cc43e96b72eed597f0d92f9e0d9c06080904cfd3761abeba92", "query": "parameters[k] = v.(string) } } <ins> if snapshotProvider, ok := snapshotClass.Object[\"driver\"]; ok { snapshotter = snapshotProvider.(string) } </ins> } return testsuites.GetSnapshotClass(snapshotter, parameters, ns, suffix)", "positive_passages": [{"docid": "doc-en-kubernetes-51e228a10e330c9cdfe0846a8842785d5f11851661581fda232b614aedbd5649", "text": "<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", "commid": "kubernetes_issue_90868", "tokennum": 41}], "negative_passages": []}
{"query_id": "q-en-kubernetes-30c11151990ccce499ac1ad6947a662fd442dc3b5a31fda2d5b087dba1c7e7d1", "query": "}) // TODO: add tests that cover deployment.Spec.MinReadySeconds once we solved clock-skew issues // See https://github.com/kubernetes/kubernetes/issues/29229 <ins> ginkgo.It(\"should run the lifecycle of a Deployment\", func() { deploymentResource := schema.GroupVersionResource{Group: \"apps\", Version: \"v1\", Resource: \"deployments\"} testNamespaceName := f.Namespace.Name testDeploymentName := \"test-deployment\" testDeploymentInitialImage := imageutils.GetE2EImage(imageutils.Agnhost) testDeploymentPatchImage := imageutils.GetE2EImage(imageutils.Pause) testDeploymentUpdateImage := imageutils.GetE2EImage(imageutils.Httpd) testDeploymentDefaultReplicas := int32(3) testDeploymentMinimumReplicas := int32(1) testDeploymentNoReplicas := int32(0) testDeploymentLabels := map[string]string{\"test-deployment-static\": \"true\"} testDeploymentLabelsFlat := \"test-deployment-static=true\" testDeploymentLabelSelectors := metav1.LabelSelector{ MatchLabels: testDeploymentLabels, } w := &cache.ListWatch{ WatchFunc: func(options metav1.ListOptions) (watch.Interface, error) { options.LabelSelector = testDeploymentLabelsFlat return f.ClientSet.AppsV1().Deployments(testNamespaceName).Watch(context.TODO(), options) }, } deploymentsList, err := f.ClientSet.AppsV1().Deployments(\"\").List(context.TODO(), metav1.ListOptions{LabelSelector: testDeploymentLabelsFlat}) framework.ExpectNoError(err, \"failed to list Deployments\") ginkgo.By(\"creating a Deployment\") testDeployment := appsv1.Deployment{ ObjectMeta: metav1.ObjectMeta{ Name:   testDeploymentName, Labels: map[string]string{\"test-deployment-static\": \"true\"}, }, Spec: appsv1.DeploymentSpec{ Replicas: &testDeploymentDefaultReplicas, Selector: &testDeploymentLabelSelectors, Template: v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Labels: testDeploymentLabelSelectors.MatchLabels, }, Spec: v1.PodSpec{ Containers: []v1.Container{{ Name:  testDeploymentName, Image: testDeploymentInitialImage, }}, }, }, }, } _, err = f.ClientSet.AppsV1().Deployments(testNamespaceName).Create(context.TODO(), &testDeployment, metav1.CreateOptions{}) framework.ExpectNoError(err, \"failed to create Deployment %v in namespace %v\", testDeploymentName, testNamespaceName) ginkgo.By(\"waiting for Deployment to be created\") ctx, cancel := context.WithTimeout(context.Background(), 30*time.Second) defer cancel() _, err = watchtools.Until(ctx, deploymentsList.ResourceVersion, w, func(event watch.Event) (bool, error) { switch event.Type { case watch.Added: if deployment, ok := event.Object.(*appsv1.Deployment); ok { found := deployment.ObjectMeta.Name == testDeployment.Name && deployment.Labels[\"test-deployment-static\"] == \"true\" return found, nil } default: framework.Logf(\"observed event type %v\", event.Type) } return false, nil }) framework.ExpectNoError(err, \"failed to see %v event\", watch.Added) ginkgo.By(\"waiting for all Replicas to be Ready\") ctx, cancel = context.WithTimeout(context.Background(), 30*time.Second) defer cancel() _, err = watchtools.Until(ctx, deploymentsList.ResourceVersion, w, func(event watch.Event) (bool, error) { if deployment, ok := event.Object.(*appsv1.Deployment); ok { found := deployment.ObjectMeta.Name == testDeployment.Name && deployment.Labels[\"test-deployment-static\"] == \"true\" && deployment.Status.AvailableReplicas == testDeploymentDefaultReplicas && deployment.Status.ReadyReplicas == testDeploymentDefaultReplicas return found, nil } return false, nil }) framework.ExpectNoError(err, \"failed to see replicas of %v in namespace %v scale to requested amount of %v\", testDeployment.Name, testNamespaceName, testDeploymentDefaultReplicas) ginkgo.By(\"patching the Deployment\") deploymentPatch, err := json.Marshal(map[string]interface{}{ \"metadata\": map[string]interface{}{ \"labels\": map[string]string{\"test-deployment\": \"patched\"}, }, \"spec\": map[string]interface{}{ \"replicas\": testDeploymentMinimumReplicas, \"template\": map[string]interface{}{ \"spec\": map[string]interface{}{ \"containers\": [1]map[string]interface{}{{ \"name\":    testDeploymentName, \"image\":   testDeploymentPatchImage, \"command\": []string{\"/bin/sleep\", \"100000\"}, }}, }, }, }, }) framework.ExpectNoError(err, \"failed to Marshal Deployment JSON patch\") _, err = f.ClientSet.AppsV1().Deployments(testNamespaceName).Patch(context.TODO(), testDeploymentName, types.StrategicMergePatchType, []byte(deploymentPatch), metav1.PatchOptions{}) framework.ExpectNoError(err, \"failed to patch Deployment\") ctx, cancel = context.WithTimeout(context.Background(), 30*time.Second) defer cancel() _, err = watchtools.Until(ctx, deploymentsList.ResourceVersion, w, func(event watch.Event) (bool, error) { switch event.Type { case watch.Modified: if deployment, ok := event.Object.(*appsv1.Deployment); ok { found := deployment.ObjectMeta.Name == testDeployment.Name && deployment.Labels[\"test-deployment-static\"] == \"true\" return found, nil } default: framework.Logf(\"observed event type %v\", event.Type) } return false, nil }) framework.ExpectNoError(err, \"failed to see %v event\", watch.Modified) ginkgo.By(\"waiting for Replicas to scale\") ctx, cancel = context.WithTimeout(context.Background(), 30*time.Second) defer cancel() _, err = watchtools.Until(ctx, deploymentsList.ResourceVersion, w, func(event watch.Event) (bool, error) { if deployment, ok := event.Object.(*appsv1.Deployment); ok { found := deployment.ObjectMeta.Name == testDeployment.Name && deployment.Labels[\"test-deployment-static\"] == \"true\" && deployment.Status.AvailableReplicas == testDeploymentMinimumReplicas && deployment.Status.ReadyReplicas == testDeploymentMinimumReplicas && deployment.Spec.Template.Spec.Containers[0].Image == testDeploymentPatchImage return found, nil } return false, nil }) framework.ExpectNoError(err, \"failed to see replicas of %v in namespace %v scale to requested amount of %v\", testDeployment.Name, testNamespaceName, testDeploymentMinimumReplicas) ginkgo.By(\"listing Deployments\") deploymentsList, err = f.ClientSet.AppsV1().Deployments(\"\").List(context.TODO(), metav1.ListOptions{LabelSelector: testDeploymentLabelsFlat}) framework.ExpectNoError(err, \"failed to list Deployments\") foundDeployment := false for _, deploymentItem := range deploymentsList.Items { if deploymentItem.ObjectMeta.Name == testDeploymentName && deploymentItem.ObjectMeta.Namespace == testNamespaceName && deploymentItem.ObjectMeta.Labels[\"test-deployment-static\"] == \"true\" { foundDeployment = true break } } framework.ExpectEqual(foundDeployment, true, \"unable to find the Deployment in list\", deploymentsList) ginkgo.By(\"updating the Deployment\") testDeploymentUpdate := testDeployment testDeploymentUpdate.ObjectMeta.Labels[\"test-deployment\"] = \"updated\" testDeploymentUpdate.Spec.Template.Spec.Containers[0].Image = testDeploymentUpdateImage testDeploymentDefaultReplicasPointer := &testDeploymentDefaultReplicas testDeploymentUpdate.Spec.Replicas = testDeploymentDefaultReplicasPointer testDeploymentUpdateUnstructuredMap, err := runtime.DefaultUnstructuredConverter.ToUnstructured(&testDeploymentUpdate) framework.ExpectNoError(err, \"failed to convert to unstructured\") testDeploymentUpdateUnstructured := unstructuredv1.Unstructured{ Object: testDeploymentUpdateUnstructuredMap, } // currently this hasn't been able to hit the endpoint replaceAppsV1NamespacedDeploymentStatus _, err = dc.Resource(deploymentResource).Namespace(testNamespaceName).Update(context.TODO(), &testDeploymentUpdateUnstructured, metav1.UpdateOptions{}) //, \"status\") framework.ExpectNoError(err, \"failed to update the DeploymentStatus\") ctx, cancel = context.WithTimeout(context.Background(), 30*time.Second) defer cancel() _, err = watchtools.Until(ctx, deploymentsList.ResourceVersion, w, func(event watch.Event) (bool, error) { switch event.Type { case watch.Modified: if deployment, ok := event.Object.(*appsv1.Deployment); ok { found := deployment.ObjectMeta.Name == testDeployment.Name && deployment.Labels[\"test-deployment-static\"] == \"true\" return found, nil } default: framework.Logf(\"observed event type %v\", event.Type) } return false, nil }) framework.ExpectNoError(err, \"failed to see %v event\", watch.Modified) ginkgo.By(\"fetching the DeploymentStatus\") deploymentGetUnstructured, err := dc.Resource(deploymentResource).Namespace(testNamespaceName).Get(context.TODO(), testDeploymentName, metav1.GetOptions{}, \"status\") framework.ExpectNoError(err, \"failed to fetch the Deployment\") deploymentGet := appsv1.Deployment{} err = runtime.DefaultUnstructuredConverter.FromUnstructured(deploymentGetUnstructured.Object, &deploymentGet) framework.ExpectNoError(err, \"failed to convert the unstructured response to a Deployment\") framework.ExpectEqual(deploymentGet.Spec.Template.Spec.Containers[0].Image, testDeploymentUpdateImage, \"failed to update image\") framework.ExpectEqual(deploymentGet.ObjectMeta.Labels[\"test-deployment\"], \"updated\", \"failed to update labels\") ctx, cancel = context.WithTimeout(context.Background(), 30*time.Second) defer cancel() _, err = watchtools.Until(ctx, deploymentsList.ResourceVersion, w, func(event watch.Event) (bool, error) { if deployment, ok := event.Object.(*appsv1.Deployment); ok { found := deployment.ObjectMeta.Name == testDeployment.Name && deployment.Labels[\"test-deployment-static\"] == \"true\" && deployment.Status.AvailableReplicas == testDeploymentDefaultReplicas && deployment.Status.ReadyReplicas == testDeploymentDefaultReplicas return found, nil } return false, nil }) framework.ExpectNoError(err, \"failed to see replicas of %v in namespace %v scale to requested amount of %v\", testDeployment.Name, testNamespaceName, testDeploymentDefaultReplicas) ginkgo.By(\"patching the DeploymentStatus\") deploymentStatusPatch, err := json.Marshal(map[string]interface{}{ \"metadata\": map[string]interface{}{ \"labels\": map[string]string{\"test-deployment\": \"patched-status\"}, }, \"status\": map[string]interface{}{ \"readyReplicas\": testDeploymentNoReplicas, }, }) framework.ExpectNoError(err, \"failed to Marshal Deployment JSON patch\") dc.Resource(deploymentResource).Namespace(testNamespaceName).Patch(context.TODO(), testDeploymentName, types.StrategicMergePatchType, []byte(deploymentStatusPatch), metav1.PatchOptions{}, \"status\") ctx, cancel = context.WithTimeout(context.Background(), 30*time.Second) defer cancel() _, err = watchtools.Until(ctx, deploymentsList.ResourceVersion, w, func(event watch.Event) (bool, error) { switch event.Type { case watch.Modified: if deployment, ok := event.Object.(*appsv1.Deployment); ok { found := deployment.ObjectMeta.Name == testDeployment.Name && deployment.Labels[\"test-deployment-static\"] == \"true\" return found, nil } default: framework.Logf(\"observed event type %v\", event.Type) } return false, nil }) framework.ExpectNoError(err, \"failed to see %v event\", watch.Modified) ginkgo.By(\"fetching the DeploymentStatus\") deploymentGetUnstructured, err = dc.Resource(deploymentResource).Namespace(testNamespaceName).Get(context.TODO(), testDeploymentName, metav1.GetOptions{}, \"status\") framework.ExpectNoError(err, \"failed to fetch the DeploymentStatus\") deploymentGet = appsv1.Deployment{} err = runtime.DefaultUnstructuredConverter.FromUnstructured(deploymentGetUnstructured.Object, &deploymentGet) framework.ExpectNoError(err, \"failed to convert the unstructured response to a Deployment\") framework.ExpectEqual(deploymentGet.Spec.Template.Spec.Containers[0].Image, testDeploymentUpdateImage, \"failed to update image\") framework.ExpectEqual(deploymentGet.ObjectMeta.Labels[\"test-deployment\"], \"updated\", \"failed to update labels\") ctx, cancel = context.WithTimeout(context.Background(), 30*time.Second) defer cancel() _, err = watchtools.Until(ctx, deploymentsList.ResourceVersion, w, func(event watch.Event) (bool, error) { if deployment, ok := event.Object.(*appsv1.Deployment); ok { found := deployment.ObjectMeta.Name == testDeployment.Name && deployment.Labels[\"test-deployment-static\"] == \"true\" && deployment.Status.AvailableReplicas == testDeploymentDefaultReplicas && deployment.Status.ReadyReplicas == testDeploymentDefaultReplicas && deployment.Spec.Template.Spec.Containers[0].Image == testDeploymentUpdateImage return found, nil } return false, nil }) framework.ExpectNoError(err, \"failed to see replicas of %v in namespace %v scale to requested amount of %v\", testDeployment.Name, testNamespaceName, testDeploymentDefaultReplicas) ginkgo.By(\"deleting the Deployment\") err = f.ClientSet.AppsV1().Deployments(testNamespaceName).DeleteCollection(context.TODO(), metav1.DeleteOptions{}, metav1.ListOptions{LabelSelector: testDeploymentLabelsFlat}) framework.ExpectNoError(err, \"failed to delete Deployment via collection\") ctx, cancel = context.WithTimeout(context.Background(), 30*time.Second) defer cancel() _, err = watchtools.Until(ctx, deploymentsList.ResourceVersion, w, func(event watch.Event) (bool, error) { switch event.Type { case watch.Deleted: if deployment, ok := event.Object.(*appsv1.Deployment); ok { found := deployment.ObjectMeta.Name == testDeployment.Name && deployment.Labels[\"test-deployment-static\"] == \"true\" return found, nil } default: framework.Logf(\"observed event type %v\", event.Type) } return false, nil }) framework.ExpectNoError(err, \"failed to see %v event\", watch.Deleted) }) </ins> }) func failureTrap(c clientset.Interface, ns string) {", "positive_passages": [{"docid": "doc-en-kubernetes-cea21dfbf74ea26aea8b8fcc0c8d9d3e2b3e4488cd9f6d30773b87652fe6e220", "text": "[x] Original approval issue: [x] Test pr: [x] Two weeks soak end date: 19 November 2020 This issue is created to allow edit by /wip /hold According to this APIsnoop query, there are still some remaining Deployment endpoints which are untested. a Deployment with a static label the Deployment with a new Label and updated data the Deployment to ensure it's patched all Deployments in all Namespaces find the Deployment(1) ensure that the Deployment is found and is patched Namespaced Deployment(1) via a Collection with a LabelSelector Discover useragents: List endpoints hit by the test: Display endpoint coverage change: If a test with these calls gets merged, test coverage will go up by 5 points* This test is also created with the goal of conformance promotion.\n/sig testing /sig architecture /area conformance\nBobyMcbobs commented in original Issue: Unsure if the endpoint replaceAppsV1NamespacedDeploymentStatus is able to be hit. When this endpoint is attempted to be updated the data after retrieving the update resource doesn't reflect the values in the update\n/assign\nWhen using the appv1.Deployment structure instead of maps of interfaces to build the structure in a patch of the Deployment, this error comes up. Still in progress yment-static\":\"true\"}: does not match template , spec.selector: Invalid value: \"null\": field is immutable]\nreplaceAppsV1NamespacedDeploymentStatus to test. Increase cover by 1 Endpoint\n/reopen PR reverted by due to flaky test\nReopened this issue. <detailsIn response to : /reopen PR reverted by due to flaky test 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\nIssues 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\n/reopen Soaking, ready for promotion 19 November 2020\nReopened this issue. <detailsIn response to : /reopen Soaking, ready for promotion 19 November 2020 Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_90916", "tokennum": 522}], "negative_passages": []}
{"query_id": "q-en-kubernetes-30c11151990ccce499ac1ad6947a662fd442dc3b5a31fda2d5b087dba1c7e7d1", "query": "}) // TODO: add tests that cover deployment.Spec.MinReadySeconds once we solved clock-skew issues // See https://github.com/kubernetes/kubernetes/issues/29229 <ins> ginkgo.It(\"should run the lifecycle of a Deployment\", func() { deploymentResource := schema.GroupVersionResource{Group: \"apps\", Version: \"v1\", Resource: \"deployments\"} testNamespaceName := f.Namespace.Name testDeploymentName := \"test-deployment\" testDeploymentInitialImage := imageutils.GetE2EImage(imageutils.Agnhost) testDeploymentPatchImage := imageutils.GetE2EImage(imageutils.Pause) testDeploymentUpdateImage := imageutils.GetE2EImage(imageutils.Httpd) testDeploymentDefaultReplicas := int32(3) testDeploymentMinimumReplicas := int32(1) testDeploymentNoReplicas := int32(0) testDeploymentLabels := map[string]string{\"test-deployment-static\": \"true\"} testDeploymentLabelsFlat := \"test-deployment-static=true\" testDeploymentLabelSelectors := metav1.LabelSelector{ MatchLabels: testDeploymentLabels, } w := &cache.ListWatch{ WatchFunc: func(options metav1.ListOptions) (watch.Interface, error) { options.LabelSelector = testDeploymentLabelsFlat return f.ClientSet.AppsV1().Deployments(testNamespaceName).Watch(context.TODO(), options) }, } deploymentsList, err := f.ClientSet.AppsV1().Deployments(\"\").List(context.TODO(), metav1.ListOptions{LabelSelector: testDeploymentLabelsFlat}) framework.ExpectNoError(err, \"failed to list Deployments\") ginkgo.By(\"creating a Deployment\") testDeployment := appsv1.Deployment{ ObjectMeta: metav1.ObjectMeta{ Name:   testDeploymentName, Labels: map[string]string{\"test-deployment-static\": \"true\"}, }, Spec: appsv1.DeploymentSpec{ Replicas: &testDeploymentDefaultReplicas, Selector: &testDeploymentLabelSelectors, Template: v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Labels: testDeploymentLabelSelectors.MatchLabels, }, Spec: v1.PodSpec{ Containers: []v1.Container{{ Name:  testDeploymentName, Image: testDeploymentInitialImage, }}, }, }, }, } _, err = f.ClientSet.AppsV1().Deployments(testNamespaceName).Create(context.TODO(), &testDeployment, metav1.CreateOptions{}) framework.ExpectNoError(err, \"failed to create Deployment %v in namespace %v\", testDeploymentName, testNamespaceName) ginkgo.By(\"waiting for Deployment to be created\") ctx, cancel := context.WithTimeout(context.Background(), 30*time.Second) defer cancel() _, err = watchtools.Until(ctx, deploymentsList.ResourceVersion, w, func(event watch.Event) (bool, error) { switch event.Type { case watch.Added: if deployment, ok := event.Object.(*appsv1.Deployment); ok { found := deployment.ObjectMeta.Name == testDeployment.Name && deployment.Labels[\"test-deployment-static\"] == \"true\" return found, nil } default: framework.Logf(\"observed event type %v\", event.Type) } return false, nil }) framework.ExpectNoError(err, \"failed to see %v event\", watch.Added) ginkgo.By(\"waiting for all Replicas to be Ready\") ctx, cancel = context.WithTimeout(context.Background(), 30*time.Second) defer cancel() _, err = watchtools.Until(ctx, deploymentsList.ResourceVersion, w, func(event watch.Event) (bool, error) { if deployment, ok := event.Object.(*appsv1.Deployment); ok { found := deployment.ObjectMeta.Name == testDeployment.Name && deployment.Labels[\"test-deployment-static\"] == \"true\" && deployment.Status.AvailableReplicas == testDeploymentDefaultReplicas && deployment.Status.ReadyReplicas == testDeploymentDefaultReplicas return found, nil } return false, nil }) framework.ExpectNoError(err, \"failed to see replicas of %v in namespace %v scale to requested amount of %v\", testDeployment.Name, testNamespaceName, testDeploymentDefaultReplicas) ginkgo.By(\"patching the Deployment\") deploymentPatch, err := json.Marshal(map[string]interface{}{ \"metadata\": map[string]interface{}{ \"labels\": map[string]string{\"test-deployment\": \"patched\"}, }, \"spec\": map[string]interface{}{ \"replicas\": testDeploymentMinimumReplicas, \"template\": map[string]interface{}{ \"spec\": map[string]interface{}{ \"containers\": [1]map[string]interface{}{{ \"name\":    testDeploymentName, \"image\":   testDeploymentPatchImage, \"command\": []string{\"/bin/sleep\", \"100000\"}, }}, }, }, }, }) framework.ExpectNoError(err, \"failed to Marshal Deployment JSON patch\") _, err = f.ClientSet.AppsV1().Deployments(testNamespaceName).Patch(context.TODO(), testDeploymentName, types.StrategicMergePatchType, []byte(deploymentPatch), metav1.PatchOptions{}) framework.ExpectNoError(err, \"failed to patch Deployment\") ctx, cancel = context.WithTimeout(context.Background(), 30*time.Second) defer cancel() _, err = watchtools.Until(ctx, deploymentsList.ResourceVersion, w, func(event watch.Event) (bool, error) { switch event.Type { case watch.Modified: if deployment, ok := event.Object.(*appsv1.Deployment); ok { found := deployment.ObjectMeta.Name == testDeployment.Name && deployment.Labels[\"test-deployment-static\"] == \"true\" return found, nil } default: framework.Logf(\"observed event type %v\", event.Type) } return false, nil }) framework.ExpectNoError(err, \"failed to see %v event\", watch.Modified) ginkgo.By(\"waiting for Replicas to scale\") ctx, cancel = context.WithTimeout(context.Background(), 30*time.Second) defer cancel() _, err = watchtools.Until(ctx, deploymentsList.ResourceVersion, w, func(event watch.Event) (bool, error) { if deployment, ok := event.Object.(*appsv1.Deployment); ok { found := deployment.ObjectMeta.Name == testDeployment.Name && deployment.Labels[\"test-deployment-static\"] == \"true\" && deployment.Status.AvailableReplicas == testDeploymentMinimumReplicas && deployment.Status.ReadyReplicas == testDeploymentMinimumReplicas && deployment.Spec.Template.Spec.Containers[0].Image == testDeploymentPatchImage return found, nil } return false, nil }) framework.ExpectNoError(err, \"failed to see replicas of %v in namespace %v scale to requested amount of %v\", testDeployment.Name, testNamespaceName, testDeploymentMinimumReplicas) ginkgo.By(\"listing Deployments\") deploymentsList, err = f.ClientSet.AppsV1().Deployments(\"\").List(context.TODO(), metav1.ListOptions{LabelSelector: testDeploymentLabelsFlat}) framework.ExpectNoError(err, \"failed to list Deployments\") foundDeployment := false for _, deploymentItem := range deploymentsList.Items { if deploymentItem.ObjectMeta.Name == testDeploymentName && deploymentItem.ObjectMeta.Namespace == testNamespaceName && deploymentItem.ObjectMeta.Labels[\"test-deployment-static\"] == \"true\" { foundDeployment = true break } } framework.ExpectEqual(foundDeployment, true, \"unable to find the Deployment in list\", deploymentsList) ginkgo.By(\"updating the Deployment\") testDeploymentUpdate := testDeployment testDeploymentUpdate.ObjectMeta.Labels[\"test-deployment\"] = \"updated\" testDeploymentUpdate.Spec.Template.Spec.Containers[0].Image = testDeploymentUpdateImage testDeploymentDefaultReplicasPointer := &testDeploymentDefaultReplicas testDeploymentUpdate.Spec.Replicas = testDeploymentDefaultReplicasPointer testDeploymentUpdateUnstructuredMap, err := runtime.DefaultUnstructuredConverter.ToUnstructured(&testDeploymentUpdate) framework.ExpectNoError(err, \"failed to convert to unstructured\") testDeploymentUpdateUnstructured := unstructuredv1.Unstructured{ Object: testDeploymentUpdateUnstructuredMap, } // currently this hasn't been able to hit the endpoint replaceAppsV1NamespacedDeploymentStatus _, err = dc.Resource(deploymentResource).Namespace(testNamespaceName).Update(context.TODO(), &testDeploymentUpdateUnstructured, metav1.UpdateOptions{}) //, \"status\") framework.ExpectNoError(err, \"failed to update the DeploymentStatus\") ctx, cancel = context.WithTimeout(context.Background(), 30*time.Second) defer cancel() _, err = watchtools.Until(ctx, deploymentsList.ResourceVersion, w, func(event watch.Event) (bool, error) { switch event.Type { case watch.Modified: if deployment, ok := event.Object.(*appsv1.Deployment); ok { found := deployment.ObjectMeta.Name == testDeployment.Name && deployment.Labels[\"test-deployment-static\"] == \"true\" return found, nil } default: framework.Logf(\"observed event type %v\", event.Type) } return false, nil }) framework.ExpectNoError(err, \"failed to see %v event\", watch.Modified) ginkgo.By(\"fetching the DeploymentStatus\") deploymentGetUnstructured, err := dc.Resource(deploymentResource).Namespace(testNamespaceName).Get(context.TODO(), testDeploymentName, metav1.GetOptions{}, \"status\") framework.ExpectNoError(err, \"failed to fetch the Deployment\") deploymentGet := appsv1.Deployment{} err = runtime.DefaultUnstructuredConverter.FromUnstructured(deploymentGetUnstructured.Object, &deploymentGet) framework.ExpectNoError(err, \"failed to convert the unstructured response to a Deployment\") framework.ExpectEqual(deploymentGet.Spec.Template.Spec.Containers[0].Image, testDeploymentUpdateImage, \"failed to update image\") framework.ExpectEqual(deploymentGet.ObjectMeta.Labels[\"test-deployment\"], \"updated\", \"failed to update labels\") ctx, cancel = context.WithTimeout(context.Background(), 30*time.Second) defer cancel() _, err = watchtools.Until(ctx, deploymentsList.ResourceVersion, w, func(event watch.Event) (bool, error) { if deployment, ok := event.Object.(*appsv1.Deployment); ok { found := deployment.ObjectMeta.Name == testDeployment.Name && deployment.Labels[\"test-deployment-static\"] == \"true\" && deployment.Status.AvailableReplicas == testDeploymentDefaultReplicas && deployment.Status.ReadyReplicas == testDeploymentDefaultReplicas return found, nil } return false, nil }) framework.ExpectNoError(err, \"failed to see replicas of %v in namespace %v scale to requested amount of %v\", testDeployment.Name, testNamespaceName, testDeploymentDefaultReplicas) ginkgo.By(\"patching the DeploymentStatus\") deploymentStatusPatch, err := json.Marshal(map[string]interface{}{ \"metadata\": map[string]interface{}{ \"labels\": map[string]string{\"test-deployment\": \"patched-status\"}, }, \"status\": map[string]interface{}{ \"readyReplicas\": testDeploymentNoReplicas, }, }) framework.ExpectNoError(err, \"failed to Marshal Deployment JSON patch\") dc.Resource(deploymentResource).Namespace(testNamespaceName).Patch(context.TODO(), testDeploymentName, types.StrategicMergePatchType, []byte(deploymentStatusPatch), metav1.PatchOptions{}, \"status\") ctx, cancel = context.WithTimeout(context.Background(), 30*time.Second) defer cancel() _, err = watchtools.Until(ctx, deploymentsList.ResourceVersion, w, func(event watch.Event) (bool, error) { switch event.Type { case watch.Modified: if deployment, ok := event.Object.(*appsv1.Deployment); ok { found := deployment.ObjectMeta.Name == testDeployment.Name && deployment.Labels[\"test-deployment-static\"] == \"true\" return found, nil } default: framework.Logf(\"observed event type %v\", event.Type) } return false, nil }) framework.ExpectNoError(err, \"failed to see %v event\", watch.Modified) ginkgo.By(\"fetching the DeploymentStatus\") deploymentGetUnstructured, err = dc.Resource(deploymentResource).Namespace(testNamespaceName).Get(context.TODO(), testDeploymentName, metav1.GetOptions{}, \"status\") framework.ExpectNoError(err, \"failed to fetch the DeploymentStatus\") deploymentGet = appsv1.Deployment{} err = runtime.DefaultUnstructuredConverter.FromUnstructured(deploymentGetUnstructured.Object, &deploymentGet) framework.ExpectNoError(err, \"failed to convert the unstructured response to a Deployment\") framework.ExpectEqual(deploymentGet.Spec.Template.Spec.Containers[0].Image, testDeploymentUpdateImage, \"failed to update image\") framework.ExpectEqual(deploymentGet.ObjectMeta.Labels[\"test-deployment\"], \"updated\", \"failed to update labels\") ctx, cancel = context.WithTimeout(context.Background(), 30*time.Second) defer cancel() _, err = watchtools.Until(ctx, deploymentsList.ResourceVersion, w, func(event watch.Event) (bool, error) { if deployment, ok := event.Object.(*appsv1.Deployment); ok { found := deployment.ObjectMeta.Name == testDeployment.Name && deployment.Labels[\"test-deployment-static\"] == \"true\" && deployment.Status.AvailableReplicas == testDeploymentDefaultReplicas && deployment.Status.ReadyReplicas == testDeploymentDefaultReplicas && deployment.Spec.Template.Spec.Containers[0].Image == testDeploymentUpdateImage return found, nil } return false, nil }) framework.ExpectNoError(err, \"failed to see replicas of %v in namespace %v scale to requested amount of %v\", testDeployment.Name, testNamespaceName, testDeploymentDefaultReplicas) ginkgo.By(\"deleting the Deployment\") err = f.ClientSet.AppsV1().Deployments(testNamespaceName).DeleteCollection(context.TODO(), metav1.DeleteOptions{}, metav1.ListOptions{LabelSelector: testDeploymentLabelsFlat}) framework.ExpectNoError(err, \"failed to delete Deployment via collection\") ctx, cancel = context.WithTimeout(context.Background(), 30*time.Second) defer cancel() _, err = watchtools.Until(ctx, deploymentsList.ResourceVersion, w, func(event watch.Event) (bool, error) { switch event.Type { case watch.Deleted: if deployment, ok := event.Object.(*appsv1.Deployment); ok { found := deployment.ObjectMeta.Name == testDeployment.Name && deployment.Labels[\"test-deployment-static\"] == \"true\" return found, nil } default: framework.Logf(\"observed event type %v\", event.Type) } return false, nil }) framework.ExpectNoError(err, \"failed to see %v event\", watch.Deleted) }) </ins> }) func failureTrap(c clientset.Interface, ns string) {", "positive_passages": [{"docid": "doc-en-kubernetes-ff9ccf83336a9bf28b0576a991dfda56392cc48f280c272644ff154877b8104d", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/remove-lifecycle stale\n/triage accepted\n/merged", "commid": "kubernetes_issue_90916", "tokennum": 34}], "negative_passages": []}
{"query_id": "q-en-kubernetes-30e446c9ddbdfdf4f737e04894b02b588104e46eb61dd8212fa65fa8607c0d53", "query": "// Makes sure the security group exists. // For multi-cluster isolation, name must be globally unique, for example derived from the service UUID. <ins> // Additional tags can be specified </ins> // Returns the security group id or error <del> func (c *Cloud) ensureSecurityGroup(name string, description string) (string, error) { </del> <ins> func (c *Cloud) ensureSecurityGroup(name string, description string, additionalTags map[string]string) (string, error) { </ins> groupID := \"\" attempt := 0 for {", "positive_passages": [{"docid": "doc-en-kubernetes-f0769863fab39b633cda95f4d162dbe6bf42638a791c88a2a3acb41bb68633b3", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature /sig aws What happened: In k8s 1.7, when creating a service of type LoadBalancer, K8S creates the ELB and a Security Group for it. For these resources, it adds a tag, constructed dynamically, containing the cluster id: \"${cluster_id}\" with the value \"true\" What you expected to happen: We'd like to have also a statically named tag , as it was in 1.5 (\"KubernetesCluster\") with the value of the cluster id. How to reproduce it (as minimally and precisely as possible): Running on AWS cloud provider, create a service of type LoadBalancer. Anything else we need to know?: The reason for what we expect is that we have tight security constraints that require us to fine tune the IAM policies for the Instance profiles that the controllers use. With a statically named tag we were able, in 1.5, to restrict the permissions in the IAM policy to act only on the k8s managed resources (ELBs, security groups). Here is the relevant part of the IAM policy: With a dynamically named tag we are not able to do this any more as AWS IAM doesn't support something like: We are sharing the Instance Profiles among different k8s clusters, hence the \"\" in the value of the tag. Environment: Kubernetes version (use ):Cloud provider or hardware configuration*: AWS OS (e.g. from /etc/os-release):Kernel (e.g. ):Install tools: kube-aws Others:\nReiterating the mentions to trigger a notification: <detailsIn response to : <!-- This form is for bug reports and feature requests ONLY! -- /sig aws In k8s 1.7, when creating a service of type LoadBalancer, K8S creates the ELB and a Security Group for it. For these resources, it adds a tag, constructed dynamically, containing the cluster id: \"${cluster_id}\" with the value \"true\" We'd like to have also a statically named tag , as it was in 1.5 (\"KubernetesCluster\") with the value of the cluster id. Running on AWS cloud provider, create a service of type LoadBalancer.", "commid": "kubernetes_issue_53489", "tokennum": 543}], "negative_passages": []}
{"query_id": "q-en-kubernetes-30e446c9ddbdfdf4f737e04894b02b588104e46eb61dd8212fa65fa8607c0d53", "query": "// Makes sure the security group exists. // For multi-cluster isolation, name must be globally unique, for example derived from the service UUID. <ins> // Additional tags can be specified </ins> // Returns the security group id or error <del> func (c *Cloud) ensureSecurityGroup(name string, description string) (string, error) { </del> <ins> func (c *Cloud) ensureSecurityGroup(name string, description string, additionalTags map[string]string) (string, error) { </ins> groupID := \"\" attempt := 0 for {", "positive_passages": [{"docid": "doc-en-kubernetes-a01a3c41e631760f28b69af73c7e0688234151a20f7dd4b67642a3c81f6b4dfa", "text": "The reason for what we expect is that we have tight security constraints that require us to fine tune the IAM policies for the Instance profiles that the controllers use. With a statically named tag we were able, in 1.5, to restrict the permissions in the IAM policy to act only on the k8s managed resources (ELBs, security groups). Here is the relevant part of the IAM policy: Environment: Kubernetes version (use ):OS (e.g. from /etc/os-release):Others: </details\nI believe they are moving away from the tag since there are many resources that can be shared by multiple clusters. could you use an annotation?\nWe removed the condition in roles in the end. Thank you for your suggestion.\nThat annotation affects the ELB but not any security groups that are created. can you please reopen this? You reported a real issue, and even if it no longer affects you, it needs to be tracked and fixed.\nIndeed, this might be a feature that someone else would need.\nIn fact, this is a feature I need!\nFood for thought: should we propagate the tags on the ELB to the SG, or should we introduce an annotation for the SG specifically?", "commid": "kubernetes_issue_53489", "tokennum": 265}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3113178345a4149f0419e8fb2f89dd0ae0a875b91dc6c267d1b8e52915e10142", "query": "err := esController.syncService(fmt.Sprintf(\"%s/%s\", namespace, missingServiceName)) <del> // Since the service doesn't exist, we should get a not found error assert.NotNil(t, err, \"Expected no error syncing service\") assert.Equal(t, err.Error(), \"service \"notthere\" not found\") </del> <ins> // nil should be returned when the service doesn't exist assert.Nil(t, err, \"Expected no error syncing service\") </ins> // That should mean no client actions were performed assert.Len(t, client.Actions(), 0)", "positive_passages": [{"docid": "doc-en-kubernetes-0786e42c64621bc4d095c4e71177424c568ccfa7fdb0651a37698d341e1aa584", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: This requires 1.16 alpha feature: Endpoint Slices being enabled. After deleting a , EndpointSliceController kept enqueuing the service after syncing it successfully, until its retry budget exceeded. And the logs are misleading by indicating something wrong happened while the cleanup has been executed successfully: What you expected to happen: The deletion should be triggered only once and there should be no warning and error logs if the cleanup is successfully. How to reproduce it (as minimally and precisely as possible): Endpoint Slices feature a then delete it. kube-controller-manager logs, there would be repeated logs. Anything else we need to know?: Environment: Kubernetes version (use ):Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\nThere are no sig labels on this issue. Please add a sig label by either: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. See the . The in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals. <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\n/assign\n/assign", "commid": "kubernetes_issue_82995", "tokennum": 384}], "negative_passages": []}
{"query_id": "q-en-kubernetes-31193288258fee76a48a170644cc613a75dea9d3538d3115465a1f5ecf8a7a34", "query": "} } <del> if klog.V(4).Enabled() { </del> <ins> if klog.V(10).Enabled() { </ins> for i := range result { klog.InfoS(\"Calculated node's final score for pod\", \"pod\", klog.KObj(pod), \"node\", result[i].Name, \"score\", result[i].Score) }", "positive_passages": [{"docid": "doc-en-kubernetes-008ca2b69bf6f84855aa7fc74e613d0733365e6cd47dcc25c8f18519fbaaf463", "text": "Scheduler throughput drops significantly in http://perf- ! After , seems to be the curlspirit.\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/priority critical-urgent /sig scheduling /sig scalability", "commid": "kubernetes_issue_99913", "tokennum": 125}], "negative_passages": []}
{"query_id": "q-en-kubernetes-312ce29c3dadad20bcaf55cde48f6d971d32b6e7da8458872a06e151dffbce5f", "query": "ginkgo.Context(\"once the node is setup\", func() { ginkgo.It(\"container runtime's oom-score-adj should be -999\", func() { runtimePids, err := getPidsForProcess(framework.TestContext.ContainerRuntimeProcessName, framework.TestContext.ContainerRuntimePidFile) <del> gomega.Expect(err).To(gomega.BeNil(), \"failed to get list of container runtime pids\") </del> <ins> framework.ExpectNoError(err, \"failed to get list of container runtime pids\") </ins> for _, pid := range runtimePids { gomega.Eventually(func() error { return validateOOMScoreAdjSetting(pid, -999)", "positive_passages": [{"docid": "doc-en-kubernetes-4d7af6d1d5d1ba0c7ab59da9ea13925b54c282d46d48402ebb3f5409fd2b1204", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: kubernetes/node-problem-detector/node-problem-detector-ci: ci-npd-e2e-node See the Which test(s) are failing: [] NodeProblemDetector [NodeFeature:NodeProblemDetector] [] SystemLogMonitor should generate node condition and events for corresponding errors Since when has it been failing: Dec 03. was at 19:50 PST, was at 21:51 PST. Testgrid link: https://k8s- Reason for failure: Apparently is the culprit. Anything else we need to know: This is likely caused by some library upgrade. Nothing big.\n/sig node\n/assign\nSeems like the failure is caused by . /cc /cc /cc /cc\n/priority critical-urgent\nThe particular bug I care about has been fixed in . I'm gonna still work on submitting , as the same error should also be affecting a few other tests.", "commid": "kubernetes_issue_85933", "tokennum": 235}], "negative_passages": []}
{"query_id": "q-en-kubernetes-31523b44bbb1bb48f38e257fe239a885088cdef398e5538e62dedf69dfb641f0", "query": "} // Status indicates the result of running a plugin. It consists of a code, a <del> // message, (optionally) an error and an plugin name it fails by. When the status // code is not `Success`, the reasons should explain why. </del> <ins> // message, (optionally) an error and an plugin name it fails by. // When the status code is not Success, the reasons should explain why. // And, when code is Success, all the other fields should be empty. </ins> // NOTE: A nil Status is also considered as Success. type Status struct { code    Code", "positive_passages": [{"docid": "doc-en-kubernetes-886e866c35ce4d0e6b72ae097ad54b4a91c03df05db27917345e0b92fff76268", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --AppendReason panic when status is nil. Some plugins return nil to mean success. (Or, shouldn't be used on success status? I use field as a reason for why it is success.) not panic or describe this behaviour on the document\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scheduling /assign I think there are some solutions we can take. just add this behaviour to AppendReason document. (most easy solution) Status when status is nil, like below. all plugins not to return nil when success (hard way..) I support the second idea.\nI'd expect (and in fact it is) the caller to be responsible to ensure the status is not nil: The 2nd option may work, but semantically should be called by a non-success status.\nHi OK, I see :) I created the small PR to describe that reason field is for non-success status. Please take a look", "commid": "kubernetes_issue_103737", "tokennum": 329}], "negative_passages": []}
{"query_id": "q-en-kubernetes-318023309a74e5810b1a744a27dc248736ab4d0899c6e07f2ccbc9ed7445740d", "query": "return false, output, nil } } <ins> // getRbdImageInfo try to get rbdImageInfo from deviceMountPath. func getRbdImageInfo(deviceMountPath string) (*rbdImageInfo, error) { deviceMountedPathSeps := strings.Split(filepath.Base(deviceMountPath), \"-image-\") if len(deviceMountedPathSeps) != 2 { return nil, fmt.Errorf(\"Can't found devicePath for %s \", deviceMountPath) } return &rbdImageInfo{ pool: deviceMountedPathSeps[0], name: deviceMountedPathSeps[1], }, nil } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-504dcfb92cdb541009bacf4c1b680d2ebe053bb62fdf81ca10ac728d32628e43", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: Pod was deleted successfully but there is still a lock on the ceph image. I find two logs,one for that lock not removed and another for that lock removed. I find that there are little difference between them. the log that lock not removed: and the log that lock removed: What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.6.7 Cloud provider or hardware configuration**: OS (e.g. from /etc/os-release): centos7 Kernel (e.g. ): 3.10.0-327.el7.x86_64 Install tools: Others:\n/sig storage\nError 16 is EBUSY. similar to\nwere you running kubelet with cadvisor on?\n/assign\nyes, every kubelet run with cadvisor,and i know what code 16 represent for,but i still don't know the reason, is this a bug? How can i avoid this kind of situation from happening,thank you\nIt is probably related to\nWe see some other case may cause , kubelet run with nodeexporter and nodeexporter is deployed by k8s daemonset with -v /:/rootfs:ro (mount kubelet host rootfs into nodeexporter container). rbd device is mounted before nodeexporter started, because k8s 1.6.7 not support mount propagation, when the rbd plugin unmount /dev/rbd0 on the host namespace, the mount info will still leave over in node_exporter container namespace, may cause . hope this would help\nthanks, does the problem persist if node_exporter stops collecting filesystem metrics?\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with .", "commid": "kubernetes_issue_54214", "tokennum": 513}], "negative_passages": []}
{"query_id": "q-en-kubernetes-318023309a74e5810b1a744a27dc248736ab4d0899c6e07f2ccbc9ed7445740d", "query": "return false, output, nil } } <ins> // getRbdImageInfo try to get rbdImageInfo from deviceMountPath. func getRbdImageInfo(deviceMountPath string) (*rbdImageInfo, error) { deviceMountedPathSeps := strings.Split(filepath.Base(deviceMountPath), \"-image-\") if len(deviceMountedPathSeps) != 2 { return nil, fmt.Errorf(\"Can't found devicePath for %s \", deviceMountPath) } return &rbdImageInfo{ pool: deviceMountedPathSeps[0], name: deviceMountedPathSeps[1], }, nil } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-e58e0280341e2b39cd2fb25afc5193b55cba235066305ff633e2c34889e5eefe", "text": "Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nI'm experiencing this issue. From what I can read above, if the rbd mount happens before the node_exporter starts; we'll always experience status 16?\nWe're getting this issue. This is because the mounted volume is mounted on Cadvisor container too. So the /dev/rbdX file is still in use. But still didn't find any solution to fix.\nrbd volume will stuck when failed as will always returen\nMy solution: container use a volumeMount. make a script file to be executed every a minute:", "commid": "kubernetes_issue_54214", "tokennum": 220}], "negative_passages": []}
{"query_id": "q-en-kubernetes-31a7eaa80511f7d14c9e4b533d024f92e875d05c6187e680bca1af8e1e61d7f4", "query": "return \"\", fmt.Errorf(\"created security group, but id was not returned: %s\", name) } <del> err := c.tagging.createTags(c.ec2, groupID, ResourceLifecycleOwned, nil) </del> <ins> err := c.tagging.createTags(c.ec2, groupID, ResourceLifecycleOwned, additionalTags) </ins> if err != nil { // If we retry, ensureClusterTags will recover from this - it // will add the missing tags.  We could delete the security", "positive_passages": [{"docid": "doc-en-kubernetes-f0769863fab39b633cda95f4d162dbe6bf42638a791c88a2a3acb41bb68633b3", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature /sig aws What happened: In k8s 1.7, when creating a service of type LoadBalancer, K8S creates the ELB and a Security Group for it. For these resources, it adds a tag, constructed dynamically, containing the cluster id: \"${cluster_id}\" with the value \"true\" What you expected to happen: We'd like to have also a statically named tag , as it was in 1.5 (\"KubernetesCluster\") with the value of the cluster id. How to reproduce it (as minimally and precisely as possible): Running on AWS cloud provider, create a service of type LoadBalancer. Anything else we need to know?: The reason for what we expect is that we have tight security constraints that require us to fine tune the IAM policies for the Instance profiles that the controllers use. With a statically named tag we were able, in 1.5, to restrict the permissions in the IAM policy to act only on the k8s managed resources (ELBs, security groups). Here is the relevant part of the IAM policy: With a dynamically named tag we are not able to do this any more as AWS IAM doesn't support something like: We are sharing the Instance Profiles among different k8s clusters, hence the \"\" in the value of the tag. Environment: Kubernetes version (use ):Cloud provider or hardware configuration*: AWS OS (e.g. from /etc/os-release):Kernel (e.g. ):Install tools: kube-aws Others:\nReiterating the mentions to trigger a notification: <detailsIn response to : <!-- This form is for bug reports and feature requests ONLY! -- /sig aws In k8s 1.7, when creating a service of type LoadBalancer, K8S creates the ELB and a Security Group for it. For these resources, it adds a tag, constructed dynamically, containing the cluster id: \"${cluster_id}\" with the value \"true\" We'd like to have also a statically named tag , as it was in 1.5 (\"KubernetesCluster\") with the value of the cluster id. Running on AWS cloud provider, create a service of type LoadBalancer.", "commid": "kubernetes_issue_53489", "tokennum": 543}], "negative_passages": []}
{"query_id": "q-en-kubernetes-31a7eaa80511f7d14c9e4b533d024f92e875d05c6187e680bca1af8e1e61d7f4", "query": "return \"\", fmt.Errorf(\"created security group, but id was not returned: %s\", name) } <del> err := c.tagging.createTags(c.ec2, groupID, ResourceLifecycleOwned, nil) </del> <ins> err := c.tagging.createTags(c.ec2, groupID, ResourceLifecycleOwned, additionalTags) </ins> if err != nil { // If we retry, ensureClusterTags will recover from this - it // will add the missing tags.  We could delete the security", "positive_passages": [{"docid": "doc-en-kubernetes-a01a3c41e631760f28b69af73c7e0688234151a20f7dd4b67642a3c81f6b4dfa", "text": "The reason for what we expect is that we have tight security constraints that require us to fine tune the IAM policies for the Instance profiles that the controllers use. With a statically named tag we were able, in 1.5, to restrict the permissions in the IAM policy to act only on the k8s managed resources (ELBs, security groups). Here is the relevant part of the IAM policy: Environment: Kubernetes version (use ):OS (e.g. from /etc/os-release):Others: </details\nI believe they are moving away from the tag since there are many resources that can be shared by multiple clusters. could you use an annotation?\nWe removed the condition in roles in the end. Thank you for your suggestion.\nThat annotation affects the ELB but not any security groups that are created. can you please reopen this? You reported a real issue, and even if it no longer affects you, it needs to be tracked and fixed.\nIndeed, this might be a feature that someone else would need.\nIn fact, this is a feature I need!\nFood for thought: should we propagate the tags on the ELB to the SG, or should we introduce an annotation for the SG specifically?", "commid": "kubernetes_issue_53489", "tokennum": 265}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3213574cc641de0acf4fd6f427885099b917a706a1c2a7527106b0de680b5ac8", "query": "\"context\" \"fmt\" \"math/rand\" <del> \"sort\" </del> \"sync\" \"sync/atomic\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-008ca2b69bf6f84855aa7fc74e613d0733365e6cd47dcc25c8f18519fbaaf463", "text": "Scheduler throughput drops significantly in http://perf- ! After , seems to be the curlspirit.\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/priority critical-urgent /sig scheduling /sig scalability", "commid": "kubernetes_issue_99913", "tokennum": 125}], "negative_passages": []}
{"query_id": "q-en-kubernetes-322dcfd43c3da1d3b8584df754f853b504ce70faf08a1a2d70938cdcb2baefdf", "query": "} }) }) <ins> ginkgo.Context(\"PriorityClass endpoints\", func() { var cs clientset.Interface f := framework.NewDefaultFramework(\"sched-preemption-path\") var pcs []*schedulingv1.PriorityClass ginkgo.BeforeEach(func() { cs = f.ClientSet // Create 2 PriorityClass: p1, p2. for i := 1; i <= 2; i++ { name, val := fmt.Sprintf(\"p%d\", i), int32(i) pc, err := cs.SchedulingV1().PriorityClasses().Create(context.TODO(), &schedulingv1.PriorityClass{ObjectMeta: metav1.ObjectMeta{Name: name}, Value: val}, metav1.CreateOptions{}) if err != nil { framework.Logf(\"Failed to create priority '%v/%v'. Reason: %v. Msg: %v\", name, val, apierrors.ReasonForError(err), err) } framework.ExpectEqual(err == nil || apierrors.IsAlreadyExists(err), true) pcs = append(pcs, pc) } }) ginkgo.AfterEach(func() { // Print out additional info if tests failed. if ginkgo.CurrentGinkgoTestDescription().Failed { // List existing PriorityClasses. priorityList, err := cs.SchedulingV1().PriorityClasses().List(context.TODO(), metav1.ListOptions{}) if err != nil { framework.Logf(\"Unable to list PriorityClasses: %v\", err) } else { framework.Logf(\"List existing PriorityClasses:\") for _, p := range priorityList.Items { framework.Logf(\"%v/%v created at %v\", p.Name, p.Value, p.CreationTimestamp) } } } // Cannot run collection deletion which would delete all system level priority classes. for _, pc := range pcs { err := cs.SchedulingV1().PriorityClasses().Delete(context.TODO(), pc.Name, *metav1.NewDeleteOptions(0)) framework.ExpectNoError(err) } }) ginkgo.It(\"verify PriorityClass endpoints can be operated with different HTTP methods\", func() { // 1. Patch/Update on immutable fields will fail. pcCopy := pcs[0].DeepCopy() pcCopy.Value = pcCopy.Value * 10 err := patchPriorityClass(cs, pcs[0], pcCopy) framework.ExpectError(err, \"expect a patch error on an immutable field\") framework.Logf(\"%v\", err) pcCopy = pcs[1].DeepCopy() pcCopy.Value = pcCopy.Value * 10 _, err = cs.SchedulingV1().PriorityClasses().Update(context.TODO(), pcCopy, metav1.UpdateOptions{}) framework.ExpectError(err, \"expect an update error on an immutable field\") framework.Logf(\"%v\", err) // 2. Patch/Update on mutable fields will succeed. newDesc := \"updated description\" pcCopy = pcs[0].DeepCopy() pcCopy.Description = newDesc err = patchPriorityClass(cs, pcs[0], pcCopy) framework.ExpectNoError(err) pcCopy = pcs[1].DeepCopy() pcCopy.Description = newDesc _, err = cs.SchedulingV1().PriorityClasses().Update(context.TODO(), pcCopy, metav1.UpdateOptions{}) framework.ExpectNoError(err) // 3. List existing PriorityClasses. _, err = cs.SchedulingV1().PriorityClasses().List(context.TODO(), metav1.ListOptions{}) framework.ExpectNoError(err) // 4. Verify fields of updated PriorityClasses. for _, pc := range pcs { livePC, err := cs.SchedulingV1().PriorityClasses().Get(context.TODO(), pc.Name, metav1.GetOptions{}) framework.ExpectNoError(err) framework.ExpectEqual(livePC.Value, pc.Value) framework.ExpectEqual(livePC.Description, newDesc) } }) }) </ins> }) type pauseRSConfig struct {", "positive_passages": [{"docid": "doc-en-kubernetes-3bda2fba5ce2ad90b89601bf2aa62ec37353e4edef7a62972ac2a85cc1aff832", "text": "The following PriorityClass endpoints was Promoted it 1.14 without Conformance tests, and remain untested: replace-, read-, patch-, list-, delete-collection- SchedulingV1PriorityClass According to this APIsnoop query, there are still some remaining PriorityClass endpoints which are untested. with this query you can filter untested endpoints by their category and eligiblity for conformance. e.g below shows a query to find all conformance eligible untested,stable,core endpoints ! createSchedulingV1PriorityClass deleteSchedulingV1PriorityClass Promoted to Conformance 1.19 with /sig testing /sig architecture /area conformance\nIs the ultimiate goal to use conformance tests to explicitly issue all CRUD requests against PriorityClass? And, is equivalent to \"update PriorityClass\"?\nall APIs must have Conformance tests unless they are not eligible for Conformance due to the There is other APIGroups that have both Replace and Update as endpoints. That is the prerogative of the SIG to decide.\ncan you please point us to similar conformance tests used for core objects such as pods and nodes?\nThis is a life cycle test for Create, List, Update, Patch, DeleteCollection More can be found in the test/e2e folder. Also look for examples on the Conformance at previously Promoted Conformance test Reach out if we can help with more information on our approach to Conformance testing.\nI remembered about this PR. Last week a few lines of code was to cover the last of the \"Lease\" endpoint group for conformance. The one file contain the Conformance tests for the complete life cycle of Lease endpoints.\n/assign I will work on it.\n/reopen Will monitor in test grid to move to Conformance after 2 weeks soak.\nReopened this issue. <detailsIn response to : /reopen Will monitor in test grid to move to Conformance after 2 weeks soak. </details\n/triage accepted", "commid": "kubernetes_issue_94954", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3233c751ea2287fbdb5ff8e6f3e80c3d9f3435eb9a9a927a5d5fb9424f685f09", "query": "\"enableHttps\": false, \"nodeCacheCapable\": false } <del> ] </del> <ins> ], \"hardPodAffinitySymmetricWeight\" : 10 </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-88466bc637a805045217da94feabbdbd3df0ba52cd0d9904e95d3984c4cf4efa", "text": "( noticed this) HardPodAffinitySymmetricWeight should be in the , not in KubeSchedulerConfiguration If/when fixing this, we need to be careful to do it in a backward-compatilble way.\nDo you mean ? It seems scheduler policy config's args can not passed to FitPredicates; it need to update related interface. For the : mark to be deprecated and set scheduler policy config to HardPodAffinitySymmetricWeight if policy config is empty.\nAre you working on this? if no, I can take it.\n, nop; please go ahead.\n/ / / , When reviewing the PR, there's one question on : the default value of is 1, which means the weight (1) will always add to priorities if term matched (), does it our expectation? And the user has to set it to 0 to disable it. IMO, the default value of should be 0.\nThe value 1 (instead of 0) was chosen so that if you say A must run with B, there is an automatic preference that B should run with A. This seems like reasonable behavior.\nThanks very much; reasonable case to me. But it seems we can not disable it: if set to 0, the default funcs will set it to default (1); similar result to un-set. Anyway, no user complain this now :).", "commid": "kubernetes_issue_43845", "tokennum": 306}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3240861ff9ba9338377fe408d0cf7e2ad32c684f2b293788073c5d8bff91e333", "query": "// StoreCertsInSecrets is alpha in v1.8 StoreCertsInSecrets = \"StoreCertsInSecrets\" <ins> // SupportIPVSProxyMode is alpha in v1.8 SupportIPVSProxyMode = \"SupportIPVSProxyMode\" </ins> ) <del> var v190 = version.MustParseSemantic(\"v1.9.0\") </del> <ins> var v190 = version.MustParseSemantic(\"v1.9.0-alpha.1\") </ins> // InitFeatureGates are the default feature gates for the init command var InitFeatureGates = FeatureList{ <del> SelfHosting:         {FeatureSpec: utilfeature.FeatureSpec{Default: false, PreRelease: utilfeature.Beta}}, StoreCertsInSecrets: {FeatureSpec: utilfeature.FeatureSpec{Default: false, PreRelease: utilfeature.Alpha}}, HighAvailability:    {FeatureSpec: utilfeature.FeatureSpec{Default: false, PreRelease: utilfeature.Alpha}, MinimumVersion: v190}, </del> <ins> SelfHosting:          {FeatureSpec: utilfeature.FeatureSpec{Default: false, PreRelease: utilfeature.Beta}}, StoreCertsInSecrets:  {FeatureSpec: utilfeature.FeatureSpec{Default: false, PreRelease: utilfeature.Alpha}}, HighAvailability:     {FeatureSpec: utilfeature.FeatureSpec{Default: false, PreRelease: utilfeature.Alpha}, MinimumVersion: v190}, SupportIPVSProxyMode: {FeatureSpec: utilfeature.FeatureSpec{Default: false, PreRelease: utilfeature.Alpha}, MinimumVersion: v190}, </ins> } // Feature represents a feature being gated", "positive_passages": [{"docid": "doc-en-kubernetes-fdf6c8e5598e80992f62cef52eca112e7ba1d532fe8ace89dc932a5edac53dea", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: Currently, IPVS proxier does not run any e2e test cases. What you expected to happen: I think it's important to create test suite for IPVS in upstream CI which will help a lot in moving IPVS existing alpha. Anything else we need to know?: Let's work together. /sig network\nSelf /assign\nThere are to ways to do this work: , but doesn't support any kube-proxy config right now, so I had this pr , and also, need support it too, see this pr: kubernetes/kubernetes-anywhere build cluster. See this pr: kubernetes/test-infra The second way is much easier and faster, but I was told they gonna deprecated the , so in the long term, we still need and 's support. If anybody have better way or have some suggestion about this, please let me know, I'll be really appreciate, Thanks.", "commid": "kubernetes_issue_52834", "tokennum": 247}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3247e0c632e1bddc85b674c38b0bf23adef9035e3f13dba3df8d99ed48ef0f6f", "query": "} } <ins> // CloneTLSConfig returns a tls.Config with all exported fields except SessionTicketsDisabled and SessionTicketKey copied. // This makes it safe to call CloneTLSConfig on a config in active use by a server. // TODO: replace with tls.Config#Clone when we move to go1.8 func CloneTLSConfig(cfg *tls.Config) *tls.Config { if cfg == nil { return &tls.Config{} } return &tls.Config{ Rand:                     cfg.Rand, Time:                     cfg.Time, Certificates:             cfg.Certificates, NameToCertificate:        cfg.NameToCertificate, GetCertificate:           cfg.GetCertificate, RootCAs:                  cfg.RootCAs, NextProtos:               cfg.NextProtos, ServerName:               cfg.ServerName, ClientAuth:               cfg.ClientAuth, ClientCAs:                cfg.ClientCAs, InsecureSkipVerify:       cfg.InsecureSkipVerify, CipherSuites:             cfg.CipherSuites, PreferServerCipherSuites: cfg.PreferServerCipherSuites, ClientSessionCache:       cfg.ClientSessionCache, MinVersion:               cfg.MinVersion, MaxVersion:               cfg.MaxVersion, CurvePreferences:         cfg.CurvePreferences, } } </ins> func TLSClientConfig(transport http.RoundTripper) (*tls.Config, error) { if transport == nil { return nil, nil", "positive_passages": [{"docid": "doc-en-kubernetes-01f8727bc339d7af9aee90f0167a90af1aad001fdd8330c2abd8f77d4ae97abe", "text": "When the master dials nodes, it is mutating the tlsConfig held by the master kubelet client, to add a server name. That means if two different nodes are dialed from a master started with , x509 verification will fail for the second one. Introduced in\nthis is a regression from 1.3 and breaks pod logs/exec/attach and node proxying on installations that use\nWe probably need to review that PR and look to see if any other deliberate copies were flagged incorrectly by govet.\nInstallations that depend on secure trust from externally provided kubelet server certs are the highest security rings. If we don't fix this we need to tell anyone using this flag not to upgrade until we release 1.4.1.\nthe rest of the changes in the govet cleanup PR looked fine to me. fix for this issue is in\nSince we are telling folks they have to upgrade to kubectl 1.4.0 for rollingupdate to work it would definitely be a confusing message to say other folks should not upgrade to 1.4.0 at all.\nIf the fix is merged into master by this afternoon, lets discuss whether or not we should cherrypick it - e.g. risks involved, how we can manually qa to verify nothing else was broken, etc.\nRisk involved: If you are using a secure cluster (defined as ensuring no one can MITM your nodes and masters) and you upgrade to 1.4.0 and it does not include this fix - you are broken.\nWhat is the likelihood of interactions with other code? Is it possible this fix could introduce a breaking change to something else? Has the fix been manually verified? Are we confident that this will fully fixes the issue (vs other edge cases exist for secure clusters that this doesn't catch). Ideally I would like to see this cherrypicked into 1.4 this evening and then cut a new beta that includes it.\nNone. The single line that is currently broken was changed. The rest is a new function (with no side effects), and tests. No, it restores the original intent of the TLS config copy, and tests cover the cases we are using this with (secure, insecure, custom dialer) Yes. I swept for the same issue elsewhere and didn't find any issues. We test with a fully secured master-kubelet setup in Openshift and got a clean test run with this fix applied.\nSGTM. Thanks for fixing this.", "commid": "kubernetes_issue_33140", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3268eee9a9e14645cef60ad06a341ac0d9ad7f886e8e0d0a066f51ffe8c5770d", "query": "fs.DurationVar(&s.ShutdownDelayDuration, \"shutdown-delay-duration\", s.ShutdownDelayDuration, \"\"+ \"Time to delay the termination. During that time the server keeps serving requests normally and /healthz \"+ <del> \"returns success, but /readzy immediately returns failure. Graceful termination starts after this delay \"+ </del> <ins> \"returns success, but /readyz immediately returns failure. Graceful termination starts after this delay \"+ </ins> \"has elapsed. This can be used to allow load balancer to stop sending traffic to this server.\") utilfeature.DefaultMutableFeatureGate.AddFlag(fs)", "positive_passages": [{"docid": "doc-en-kubernetes-4d6e11fe929d479b5781c3745eba5f47af0a9520890604cfcfab06d0bbf7fee5", "text": "What happened: has a typo, (should be ) This also shows up in the rendered documentation. What you expected to happen: Documentation has correct path for readyz endpoint. How to reproduce it (as minimally and precisely as possible): Easiest to see this wrong in the source code, I think. Anything else we need to know?: Environment: Kubernetes version (use ): v1.16 Cloud provider or hardware configuration: not applicable OS (e.g: ): not applicable Kernel (e.g. ): not applicable Install tools: Network plugin and version (if this is a network-related bug): Others: /sig docs /kind bug /priority backlog", "commid": "kubernetes_issue_83120", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-326ff19840eace31d81b1eb7dec78d22c5a88b9c03dbb275c2abf87d9e56bf02", "query": "// unicode code point can be up to 4 bytes long) strWithMaxLength.MaxElements = zeroIfNegative(*s.MaxLength()) * 4 } else { <del> strWithMaxLength.MaxElements = estimateMaxStringLengthPerRequest(s) </del> <ins> if len(s.Enum()) > 0 { strWithMaxLength.MaxElements = estimateMaxStringEnumLength(s) } else { strWithMaxLength.MaxElements = estimateMaxStringLengthPerRequest(s) } </ins> } return strWithMaxLength case \"boolean\":", "positive_passages": [{"docid": "doc-en-kubernetes-d87f35a9862b77934b500147b1ec4bb0e958c531e2fdcae282b21499e2f51131", "text": "pointed out to me that a CEL x-kubernetes-validations rule in a CRD was hitting the estimated cost limit when performing a simple \"string has prefix\" check on an en enum field. Putting a limit in the OpenAPI of the enum string field fixed the problem, but having to add a limit like this is counter-intuitive and unnecessary, since the allowed enum values already make the max allowed length obvious. The apiserver automatically computes the max length of an enum as the length of the longest allowed enum value. I believe we already refuse evaluate CEL rules on values that fail OpenAPI value validation, since we rely in the value validations to establish all length limits. I haven't tested it locally, but something like this should work (given enough nested arrays): As a workaround, one can manually set on the string enum, e.g.: 25+ All No response No response No response No response\n/sig api-machinery /triage accepted /assign\n/assign\nI wasn't sure if we special-cased the maxLength / maxItems / maxProperties failures, or if all openapi validation had to pass before we started messing with CEL evaluation\nit looks like we currently special-case specific openapi errors that short-circuit CEL validation, I'm not sure an enum validation failure would currently prevent evaluation:\nThe enum err is converted to () error which is not short-circuit here. But for defaulting case, all error would be short-circuit. I would suggest to add error into the blockingErr list to short-circuit CEL validation. Would this make sense?\nyeah, that sounds good if we're going to rely on it to catch things that are longer than the maximum length enum value", "commid": "kubernetes_issue_119511", "tokennum": 383}], "negative_passages": []}
{"query_id": "q-en-kubernetes-328cb6bbdb1c035c0b632fb6ba80a8616540a70e0758db99fb7ebd2a3bc608b5", "query": "\"fmt\" \"reflect\" \"strings\" <ins> \"testing\" </ins> \"time\" apiextensions \"k8s.io/apiextensions-apiserver/pkg/client/clientset/clientset\"", "positive_passages": [{"docid": "doc-en-kubernetes-a36678f387087dd8252401a5249426873ced2ebb26644cae4efea96ce80ca1f6", "text": "reported that conformance testing with the latest version of sonobuoy against a version 1.29.0-alpha.3 cluster fails on the support the 1.17 Sample API Server using the current Aggregator test: , related to I found the reason why the test is working fine in Kubernetes CI jobs but fails with sonobuoy is because the service account used by sonobuoy \"sonobuoy-serviceaccount\" doesn't have read permission of the non-resource url \"/\", which is used by the test to confirm the removal of group path: The permission of \"sonobuoy-serviceaccount\" is as below: There may be two ways to fix it: the RBAC rule of sonobuoy to include \"get\" of \"/\". However, could other test runners encounter this issue? Is there a doc listing the required permissions for running e2e tests? the e2e to skip checking the removal of the group path if the service account doesn't have permission to access the root path. Which way do we usually prefer? Running e2e with sonobuoy should succeed. a v1.29.0-alpha.3 cluster. No response <details</details<details</details<details</details<details</details<details</details<details</details\nimplemented this solution.\n/sig api-machinery\nthank you for opening this issue and working on a solution. I'm probably not the right person to decide on which solution is preferred. From my perspective, either solution is fine.\nNote: Sonobuoy is not owned by any Kubernetes SIG. At most it is between SIG Architecture and the CNCF to choose whether to recommend it for running tests. SIG Testing owns the e2e image that sonobuoy can be used to schedule but not sonobuoy. IMHO this is a bug in running the tests via a pod, which is not how we develop the tests (they're run outside the cluster, by a cluster admin account typically). I would say 1) is the correct answer. xref: /sig architecture /sig testing /triage accepted cc\nthanks for your comment. I guess 1) means non of the existing sonobuoy versions can pass K8s conformance test against a cluster 1.29.0-alpha3, as the RBAC rule is hardcoded.", "commid": "kubernetes_issue_121985", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-328cb6bbdb1c035c0b632fb6ba80a8616540a70e0758db99fb7ebd2a3bc608b5", "query": "\"fmt\" \"reflect\" \"strings\" <ins> \"testing\" </ins> \"time\" apiextensions \"k8s.io/apiextensions-apiserver/pkg/client/clientset/clientset\"", "positive_passages": [{"docid": "doc-en-kubernetes-4545476cbce0605bfe46d5a01c41b8f4cf7b5ac07772bfb1748611bc506e90ef", "text": "I will file an issue to sonobuoy first.\nquestion here is what are the set of client permissions required to run the conformance suite? perhaps a level of access or a more granular recommendation should be documented. what is your take on the root path requirement as approver for: EDIT: slack thread:\nI agree, we already require e.g. privileged pods for a long time in conformance tests and we should make it clear that we expect a highly privileged client.\n+1 for what is saying, that we should expect that the user running the tests has required permissions. These tests are not built for being run unprivileged.\ni wanted to PR the admin note in our conformance docs under sig-arch, but then i saw this: so broke this guarantee. sounds like SIG Arch needs to comment.\nThis statement surprises me. Root discovery is one of the least-privileged permissions you can have on a cluster. For years this was even open for unauthorized users on the internet (if your api endpoint has been exposed). In other words, just add the permission. While thinking about it, it is surprising that the user in question does not have this access already. Don't we allow that for every authorized user?\nIn contrast, I hope that lots of privileged operations are tested by conformance today. If we don't test things like admission webhooks for example, we have much bigger problems. And admission webhooks are basically equivalent to cluster-admin.\nthat is outdated, we use hostNetwork pods one some of the tests IIRC\nlooks like we don't. before this ticket, i was under the impression that the conformance suite already requires admin and that all testers (like Sonobuoy) use admin level credentials. it is non-privileged (e.g., does not require root on nodes, access to raw network interfaces, or cluster admin permissions) looks like we may have to change that sentence completely.\nWould have expected it here: The PR in question explicitly fixes the result returned by . If that is part of conformance (IMO it should), every conformance test needs access it obviously. Whether we require admin, or we add it manually, either would work.", "commid": "kubernetes_issue_121985", "tokennum": 474}], "negative_passages": []}
{"query_id": "q-en-kubernetes-328cb6bbdb1c035c0b632fb6ba80a8616540a70e0758db99fb7ebd2a3bc608b5", "query": "\"fmt\" \"reflect\" \"strings\" <ins> \"testing\" </ins> \"time\" apiextensions \"k8s.io/apiextensions-apiserver/pkg/client/clientset/clientset\"", "positive_passages": [{"docid": "doc-en-kubernetes-06abc1218304c92779dae2744e33107a4d26263c1c54e4453f3f92a1949c2aa2", "text": "adding to milestone and making release blocking ... we should not release 1.29 in a state that the most commonly used conformance tool will fail\nIMO we should clarify the state and go fix the tool, but we should keep the test and we should NOT add skip. Conformance docs are not a release artifact, and sonobuoy release lifecycle is not a conformance artifact. If we can't get sonobuoy working in a reasonable time, we already know the tests can be run by scheduling the image (which is ours) directly with kubectl instead and we can document that in the upstream conformance docs. We need to fix the for this image: ,%20master%20(dev) And it should probably be to release-blocking in the future.\nit looks like the e2e change made in was not consciously made part of conformance, it was just trying to functionally test the bugfix being made. For 1.29, I think we should revert the change to and make an integration test that validates the fix instead. We can revisit whether content of is part of conformance or not for 1.30\nI opened to revert the e2e change and move the functional test to an integration test\nFiled to try to get the image job passing again.\nWe probably need another issue to track 1.30 follow-up?\nIf no one has done it, I could create another issue and follow up with the items that have been discussed here: outdated privilege requirement in commonly used conformance tools like sonobuoy aware of the required priviledge to avoid similar situations in the future. permission of GET \"/\" to authorized users via the role for root discovery.", "commid": "kubernetes_issue_121985", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-32e47cd19e82eae8042c6317680feb55068a7575dbbefbdcde9a2cfc6e6b4099", "query": "// createClients creates a kube client and an event client from the given config and masterOverride. // TODO remove masterOverride when CLI flags are removed. <del> func createClients(config componentconfig.ClientConnectionConfiguration, masterOverride string) (clientset.Interface, clientset.Interface, v1core.EventsGetter, error) { </del> <ins> func createClients(config componentconfig.ClientConnectionConfiguration, masterOverride string, timeout time.Duration) (clientset.Interface, clientset.Interface, v1core.EventsGetter, error) { </ins> if len(config.KubeConfigFile) == 0 && len(masterOverride) == 0 { glog.Warningf(\"Neither --kubeconfig nor --master was specified. Using default API client. This might not work.\") }", "positive_passages": [{"docid": "doc-en-kubernetes-638d244f4d44257351ae4786f705d88f47a0e12c74ce71a459164cb07c9c1943", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: kube-cm kube-scheduler does not exit when kube-apiserver suspended What you expected to happen: kube-cm kube-scheduler should exit after LeaderElector stops leading How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/sig api-machinery /kind bug\n/assign\n/cc", "commid": "kubernetes_issue_65090", "tokennum": 179}], "negative_passages": []}
{"query_id": "q-en-kubernetes-32f38cc2b8d61b792b97eeed93107598b448826d4196cf58c452e1ab0ba12b2d", "query": "currentBucketID := t.clock.Now().Unix() // There should be one or two elements in almost all cases expiredWatchers := make([][]*cacheWatcher, 0, 2) <ins> t.lock.Lock() defer t.lock.Unlock() </ins> for ; t.startBucketID <= currentBucketID; t.startBucketID++ { if watchers, ok := t.watchersBuckets[t.startBucketID]; ok { delete(t.watchersBuckets, t.startBucketID)", "positive_passages": [{"docid": "doc-en-kubernetes-c66c9bab938b839459ac01dfd08140ea19c2b9a1199fe50a2b49f94fd9cbbbfb", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: I try to backport bookmark feature to our internal branch. When I enable bookmark feature, apiserver leaks memory. I spend some time to dig the root cause and find the bookmarkWatchers of service cacher is keep increasing. I am not sure if it exists at upstream code. Please let me know if it is ok at latest code. What you expected to happen: Avoid memory leaking How to reproduce it (as minimally and precisely as possible): a cluster. not update service. will find kube-apiserver's memory keep increasing. Anything else we need to know?: Kubelet will watch service with bookmark, and add a watcher to bookmarkWatchers. and service init resource version is 0 Without updating service, we cannot update \"lastProcessedResourceVersion\", it will keep 0, bookmarkTimer branch will always be continued. As a result, it cannot trigger popExpiredWatchers, so the service watcher will keep increasing every watching. Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig scalability PLAT :)\nHow about making this change ?\n- can you also please take a look?\nAgree with u. That's same way I fix in our branch. But I wanna hear the suggestion of and .\n! With the same bugfix wrote above, we can see the memory not increasing any more.\nGiven that watch-bookmarks doesn't create any additional go-routines (well, creates 1, but cannot leak them), it has to leak the data. The only data that can be leaked is exactly bookmarkWatchers. So I looked into the code and got into exactly the same conclusion - that we must be leaking watchers for resources that aren't changing. The fix as above makes sense (though we also need a unit test for it).\nThanks a lot.\nhas the fix by\nThanks for reporting the bug, I will look at this day later. In addition, also need to think carefully about whether need to send a bookmark when there are no events at all.\ncc", "commid": "kubernetes_issue_80690", "tokennum": 531}], "negative_passages": []}
{"query_id": "q-en-kubernetes-32f62ef17e1f38e178718d918861823aed4dfa9aff54f5cd9f441155b9d6320e", "query": "}, }, }, <ins> \"invalid extended resource requirement without limit\": { expectedError: \"Limit must be set\", spec: core.Pod{ ObjectMeta: metav1.ObjectMeta{Name: \"123\", Namespace: \"ns\"}, Spec: core.PodSpec{ Containers: []core.Container{ { Name:            \"invalid\", Image:           \"image\", ImagePullPolicy: \"IfNotPresent\", Resources: core.ResourceRequirements{ Requests: core.ResourceList{ core.ResourceName(\"example.com/a\"): resource.MustParse(\"2\"), }, }, }, }, RestartPolicy: core.RestartPolicyAlways, DNSPolicy:     core.DNSClusterFirst, }, }, }, </ins> \"invalid fractional extended resource in container request\": { expectedError: \"must be an integer\", spec: core.Pod{", "positive_passages": [{"docid": "doc-en-kubernetes-f35278f93af61e186544e4223e8223254ed1c96c2a29c22b72803675d1a55703", "text": "/kind bug /sig node /area hw-accelerators What happened: In devices are allocated from a function called . This function inspects only container resource limits, ignoring container resource requests. This is a usability problem because it is valid to omit limits for extended resources. If limit is omitted for a device resource, then the scheduler properly places the pod with respect to available node resources. However, the device manager never dispatches to the device plugin for that resource. The result is that the user application cannot access the requested device from inside the container. What you expected to happen: Following the documented behavior of extended resources, I expected that specifying a container resource request for a device would cause the device subsystem to properly configure access for my workload. How to reproduce it (as minimally and precisely as possible): Launch an alpha GKE cluster with GPU support enabled. Attempt to run any program that accesses the GPU from a container where the resource is specified in requests but omitted from limits. Environment: Kubernetes version (use ): v1.8+ Cloud provider or hardware configuration: device plugins enabled, devices available.\nRelated issue:\ncc\n/assign\nFYI. The said issue has been fixed in . There are several valid cases when requesting extended resources: The user can specify 'limits' only. The API server will automatically set 'requests' to be equal to 'limits'. The user specify 'limits' and 'requests', and they are equal. The user specify 'requests' only. We can either reject the request saying that 'limits' must be set, or implicitly treat 'limits' as equal to 'requests'.\nHi went with to begin since it was ready to go and smaller (easier to revert if necessary.) Hopefully it's easy to rebase your work on top of that. Sorry for the inconvenience.\nI feel the documented behavior is incorrect. The original intention was to always require for extended resources until we have better APIs to express bursting scenarios. I vote for fixing the documentation and fixing the validation logic and having kubelet use limits only.\n/reopen", "commid": "kubernetes_issue_57276", "tokennum": 447}], "negative_passages": []}
{"query_id": "q-en-kubernetes-331a9ad6edb5ac1539f728cd48dc76bc9d0d4498fd85e716a79ad228728c20f9", "query": "e26fc85d14a1d3dc25569831acc06919673c545a kube::util::go_install_from_commit  github.com/bazelbuild/rules_go/go/tools/gazelle/gazelle  <del> a280fbac1a0a4c67b0eee660b4fd1b3db7c9f058 </del> <ins> c72631a220406c4fae276861ee286aaec82c5af2 </ins> touch \"${KUBE_ROOT}/vendor/BUILD\"", "positive_passages": [{"docid": "doc-en-kubernetes-1b1e05089c93c6eb59b848626d58302483d33d2f2e5531ac5b621da204277493", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind feature This is a followup on , but for Go 1.9 We should do the same kind of testing now to possibly catch bugs in either Go or Kubernetes when doing this kind of dependency version bump. Ideally we'd have automated tests against Go tip (), but we don't have that at the moment, so we have to do it kind of manually. We should also decide which k8s version we should target. k8s v1.8 or v1.9? What Go versions have been used so far? Kubernetes v1.7.0 - go1.8.3 Kubernetes v1.6.0 - go1.7.5 Kubernetes v1.5.0 - go1.7.4 Kubernetes v1.4.0 - go1.6.3 Kubernetes v1.3.0 - go1.6.2 Kubernetes v1.2.0 - go1.4.2 Seems like the trend has been to stay on the same Go version for two releases and then bump. That'd mean we'd switch to Go1.9 in k8s v1.9 Everyone happy with that? Or is there any reason for us to go start using go1.9 in k8s v1.8? In any case, we should indeed start testing go1.9 out now... cc\nLet me know if you find any bugs\nFWIW pretty tight to code-freeze I would prefer punting out a cycle fwiw.\nI don't think we're that close to code freeze given that we have 5 (of 8) weeks left in this coding cycle But I'm happy to defer this to v1.9 if others think that. I guess the main reason for a bump would be scalability goals, but I'm not sure we have the need to expand above 5000 (and that Go would be the bottleneck in that case) for v1.8\nmade the Go benchmarks 9% faster with 15% larger binaries. I'm interested to see how that affects our numbers.\nmid-stack inlining was not included in Go 1.9. It made the compiler too slow. It's being targeted to Go 1.10 now instead, after some compiler optimization work.\nOh, thanks for the correction!", "commid": "kubernetes_issue_49484", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-331a9ad6edb5ac1539f728cd48dc76bc9d0d4498fd85e716a79ad228728c20f9", "query": "e26fc85d14a1d3dc25569831acc06919673c545a kube::util::go_install_from_commit  github.com/bazelbuild/rules_go/go/tools/gazelle/gazelle  <del> a280fbac1a0a4c67b0eee660b4fd1b3db7c9f058 </del> <ins> c72631a220406c4fae276861ee286aaec82c5af2 </ins> touch \"${KUBE_ROOT}/vendor/BUILD\"", "positive_passages": [{"docid": "doc-en-kubernetes-018b01245292fe1977b7eec8bea53846947ed737ea149d849054911d63924f58", "text": "Regardless, we need to run the scalability tests against the RC so we can report issues earlier-- the last upgrade was particularly painful because of an HTTP regression that we caught way too late.\nyeah. I filed for that now\nyeah, my recollection is that the Go releases usually occur too late in our release cadence and end up getting bumped to the next Kubernetes release. (Also we inevitably find something wrong, though testing RCs would help with that. Though I'm not sure anyone has cycles to test RCs and fix all of the issues that do come up.)\nBased on our current time frame, it looks like go1.9 support will have to slip to k8s 1.9. is open to dig into and start things testing, but there's a number of things that have to move.. I'll try to document those this time around to help with future go version bumps. So far: bazel build rules needed to be updated to support go1.9 () bazel version possibly needs to be updated? some of our custom bazel rules broke\nWhen done, we should update this:\n/priority important-soon\nUpdating the dependency is blocked pending bazel 0.6.0 - .\nCan we upgrade to 0.6.0 now? Does bazel 0.6.0 have multiarch support btw?\nWe can't update to depend on bazel 0.6.0+ until we can figure out how to support different versions of the bazelbuild and kubekins-e2e images in PR jobs in prow based on what branch is being tested. cc\nNoting that we're working on branching jobs, is testing one option here:\n[MILESTONENOTIFIER] Milestone Issue Current <details open<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts. : New functionality.", "commid": "kubernetes_issue_49484", "tokennum": 416}], "negative_passages": []}
{"query_id": "q-en-kubernetes-331a9ad6edb5ac1539f728cd48dc76bc9d0d4498fd85e716a79ad228728c20f9", "query": "e26fc85d14a1d3dc25569831acc06919673c545a kube::util::go_install_from_commit  github.com/bazelbuild/rules_go/go/tools/gazelle/gazelle  <del> a280fbac1a0a4c67b0eee660b4fd1b3db7c9f058 </del> <ins> c72631a220406c4fae276861ee286aaec82c5af2 </ins> touch \"${KUBE_ROOT}/vendor/BUILD\"", "positive_passages": [{"docid": "doc-en-kubernetes-69273b286facac9ab246a3deb71fa6e24d55618a503d411a1618742e8a027c28", "text": "</details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details\nI approved this for v1.9, this is something we definitely want in order to keep up with Go (and for improved performance)\nwe're starting to use the forked images now /cc this should be more feasible very soon Edit: test-infra jobs have also been using bazel 0.6 (now 0.6.1) / a recent rules_go to soak things a bit\nWe've identified a failing test as a result of the WIP PR to upgrade the codebase to go1.9: The admission webhook test fails with certificate errors under go1.9.1, but runs successfully under go1.8.3. cc: who wanted to be alerted to potential bugs\n- please see for a possible fix", "commid": "kubernetes_issue_49484", "tokennum": 212}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3332ab3ccef4bdba8fdead76dcfcd7588e1ac36ab98a02b2e8692209dd55a802", "query": "if err := p.Unmarshal(data); err != nil { return err } <del> m.Time = time.Unix(p.Seconds, int64(p.Nanos)).Local() </del> <ins> // truncate precision to microseconds to match JSON marshaling/unmarshaling truncatedNanoseconds := time.Duration(p.Nanos).Truncate(time.Microsecond) m.Time = time.Unix(p.Seconds, int64(truncatedNanoseconds)).Local() </ins> return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-56cd908854c413b8fe52b6acbb170713ddc1a064a7bd9d42b4a3ba81ae7efcaf", "text": "Found some error logs when sending series events to apiserver: seems the later eventTime differed from the first one in series events After investigation, I found the problem was in the marshal. MicroTime is supposed to work on microsecond level precision, but init with nanosecond level precision, in this case, generates microsecond level precision data and generates nanosecond level precision, so when unmarshalled, the new time is not considered the exactly same as the original time (they are different at nanosecond level) MicroTime marshal should work at same precision for json and proto, so unmarshal can generate the exactly same MicroTime result: This causes the series events won't be updated on api-server after created master <details</details<details</details<details</details<details</details<details</details\n/sig api-machinery\n/assign\nGood catch... we'd probably need to truncate to microseconds when marshaling and unmarshaling proto to ensure any already persisted data is fixed up when read. Something like this:\nThanks for advice, going to send a PR soon", "commid": "kubernetes_issue_111928", "tokennum": 247}], "negative_passages": []}
{"query_id": "q-en-kubernetes-334d8ab20573459bb5c66ae46f0152525c2ca777e814f0cb4819d75fbf4317f0", "query": "podName := \"statscollectiontest-\" + string(uuid.NewUUID()) pod := v1.Pod{ ObjectMeta: metav1.ObjectMeta{ <del> Name: podName, </del> <ins> Name: fmt.Sprintf(\"%s-%d\", podName, i), </ins> Labels: map[string]string{ \"name\":    podName, \"testapp\": \"stats-collection\",", "positive_passages": [{"docid": "doc-en-kubernetes-e89d62bf4b636217c9a329c55c70299ddc99e1e546e8bf63873df452671a65c2", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: aks-engine-azure-windows-master-containerd-serial-slow Which test(s) are failing: [sig-windows] [Feature:Windows] Kubelet-Stats [Serial] Kubelet stats collection for Windows nodes when running 10 pods should return within 10 seconds Since when has it been failing: Unknown. Testgrid link: Reason for failure: The test spawns 10 pods with the same pod name, which contains multiple containers with the same container name. Because of this, the test fails. Logs: Anything else we need to know:\n/sig windows These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by vllry. \u200d", "commid": "kubernetes_issue_91677", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3357bd62a2ed339303a348caf3f545697e78515fab11f10650c4c06dd6788376", "query": "w = crlf.NewCRLFWriter(w) } <del> results.header.writeTo(w) </del> <ins> if addHeader { results.header.writeTo(w) } </ins> if !containsError { if err := printer.PrintObj(objToEdit, w); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-1ecb677d90f8210e5dc6b2a237f898f5f4f944a4f983b5bfcd84eaf55dd52c98", "text": "Recently I was experimenting with changing for a Golang pre-purposed faux editor when editing resources when I noticed that it couldn't be marshaled. Upon inspecting the output JSON I noticed it had the same comments that the default yaml version has. Valid JSON cannot have comments. Since the comment also gives warning / error information upon saving it must be decided where to put that in the JSON output. Perhaps a new JSON property?\nMaybe just not save the comments as part of the json to get rid of the warning, but still should them?\nIs this a 1.2 thing? I do not see any errors when running the two commands. I made an edit in one run, and did not make an edit in a separate run. Maybe I don't understand the problem that is seen.\nthere isn't a kubernetes error that is shown, the issue is that the output JSON that kubernetes generates is actually invalid JSON due to the comments at the top. This caused errors when I was trying to unmarshal that JSON in another project.\nOkay. Got it. The editor is being very strict about json having no comments.\nIt's not only about editor, it's simply part of language specification. Explanation for this: IMO if we want to use format, we should comply with it's standard. Also currently used sign for comments is unusual in javascript world, from which json evolved. In this world comments are marked in \"C++ like\" style (what in early days of JSON was also supported), i mean using and . So IMO in time of converting into JSON - we should strip such comments (I would prefer that), or they should be in some documented and specific to kubernetes way into JSON object.", "commid": "kubernetes_issue_29524", "tokennum": 377}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3372c0dd9d039e595f5ac78aac4703241d99cf4337c1990deb41ff6873b6fa36", "query": "<ins> //go:build !ignore_autogenerated // +build !ignore_autogenerated /* Copyright The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ // Code generated by openapi-gen. DO NOT EDIT. // This file was autogenerated by openapi-gen. Do not edit it manually! package openapi import ( v1 \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1\" v1beta1 \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1\" resource \"k8s.io/apimachinery/pkg/api/resource\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" intstr \"k8s.io/apimachinery/pkg/util/intstr\" common \"k8s.io/kube-openapi/pkg/common\" spec \"k8s.io/kube-openapi/pkg/validation/spec\" ) func GetOpenAPIDefinitions(ref common.ReferenceCallback) map[string]common.OpenAPIDefinition { return map[string]common.OpenAPIDefinition{ \"k8s.io/api/admissionregistration/v1.MutatingWebhook\":                                             schema_k8sio_api_admissionregistration_v1_MutatingWebhook(ref), \"k8s.io/api/admissionregistration/v1.MutatingWebhookConfiguration\":                                schema_k8sio_api_admissionregistration_v1_MutatingWebhookConfiguration(ref), \"k8s.io/api/admissionregistration/v1.MutatingWebhookConfigurationList\":                            schema_k8sio_api_admissionregistration_v1_MutatingWebhookConfigurationList(ref), \"k8s.io/api/admissionregistration/v1.Rule\":                                                        schema_k8sio_api_admissionregistration_v1_Rule(ref), \"k8s.io/api/admissionregistration/v1.RuleWithOperations\":                                          schema_k8sio_api_admissionregistration_v1_RuleWithOperations(ref), \"k8s.io/api/admissionregistration/v1.ServiceReference\":                                            schema_k8sio_api_admissionregistration_v1_ServiceReference(ref), \"k8s.io/api/admissionregistration/v1.ValidatingWebhook\":                                           schema_k8sio_api_admissionregistration_v1_ValidatingWebhook(ref), \"k8s.io/api/admissionregistration/v1.ValidatingWebhookConfiguration\":                              schema_k8sio_api_admissionregistration_v1_ValidatingWebhookConfiguration(ref), \"k8s.io/api/admissionregistration/v1.ValidatingWebhookConfigurationList\":                          schema_k8sio_api_admissionregistration_v1_ValidatingWebhookConfigurationList(ref), \"k8s.io/api/admissionregistration/v1.WebhookClientConfig\":                                         schema_k8sio_api_admissionregistration_v1_WebhookClientConfig(ref), \"k8s.io/api/admissionregistration/v1beta1.MutatingWebhook\":                                        schema_k8sio_api_admissionregistration_v1beta1_MutatingWebhook(ref), \"k8s.io/api/admissionregistration/v1beta1.MutatingWebhookConfiguration\":                           schema_k8sio_api_admissionregistration_v1beta1_MutatingWebhookConfiguration(ref), \"k8s.io/api/admissionregistration/v1beta1.MutatingWebhookConfigurationList\":                       schema_k8sio_api_admissionregistration_v1beta1_MutatingWebhookConfigurationList(ref), \"k8s.io/api/admissionregistration/v1beta1.Rule\":                                                   schema_k8sio_api_admissionregistration_v1beta1_Rule(ref), \"k8s.io/api/admissionregistration/v1beta1.RuleWithOperations\":                                     schema_k8sio_api_admissionregistration_v1beta1_RuleWithOperations(ref), \"k8s.io/api/admissionregistration/v1beta1.ServiceReference\":                                       schema_k8sio_api_admissionregistration_v1beta1_ServiceReference(ref), \"k8s.io/api/admissionregistration/v1beta1.ValidatingWebhook\":                                      schema_k8sio_api_admissionregistration_v1beta1_ValidatingWebhook(ref), \"k8s.io/api/admissionregistration/v1beta1.ValidatingWebhookConfiguration\":                         schema_k8sio_api_admissionregistration_v1beta1_ValidatingWebhookConfiguration(ref), \"k8s.io/api/admissionregistration/v1beta1.ValidatingWebhookConfigurationList\":                     schema_k8sio_api_admissionregistration_v1beta1_ValidatingWebhookConfigurationList(ref), \"k8s.io/api/admissionregistration/v1beta1.WebhookClientConfig\":                                    schema_k8sio_api_admissionregistration_v1beta1_WebhookClientConfig(ref), \"k8s.io/api/apiserverinternal/v1alpha1.ServerStorageVersion\":                                      schema_k8sio_api_apiserverinternal_v1alpha1_ServerStorageVersion(ref), \"k8s.io/api/apiserverinternal/v1alpha1.StorageVersion\":                                            schema_k8sio_api_apiserverinternal_v1alpha1_StorageVersion(ref), \"k8s.io/api/apiserverinternal/v1alpha1.StorageVersionCondition\":                                   schema_k8sio_api_apiserverinternal_v1alpha1_StorageVersionCondition(ref), \"k8s.io/api/apiserverinternal/v1alpha1.StorageVersionList\":                                        schema_k8sio_api_apiserverinternal_v1alpha1_StorageVersionList(ref), \"k8s.io/api/apiserverinternal/v1alpha1.StorageVersionSpec\":                                        schema_k8sio_api_apiserverinternal_v1alpha1_StorageVersionSpec(ref), \"k8s.io/api/apiserverinternal/v1alpha1.StorageVersionStatus\":                                      schema_k8sio_api_apiserverinternal_v1alpha1_StorageVersionStatus(ref), \"k8s.io/api/apps/v1.ControllerRevision\":                                                           schema_k8sio_api_apps_v1_ControllerRevision(ref), \"k8s.io/api/apps/v1.ControllerRevisionList\":                                                       schema_k8sio_api_apps_v1_ControllerRevisionList(ref), \"k8s.io/api/apps/v1.DaemonSet\":                                                                    schema_k8sio_api_apps_v1_DaemonSet(ref), \"k8s.io/api/apps/v1.DaemonSetCondition\":                                                           schema_k8sio_api_apps_v1_DaemonSetCondition(ref), \"k8s.io/api/apps/v1.DaemonSetList\":                                                                schema_k8sio_api_apps_v1_DaemonSetList(ref), \"k8s.io/api/apps/v1.DaemonSetSpec\":                                                                schema_k8sio_api_apps_v1_DaemonSetSpec(ref), \"k8s.io/api/apps/v1.DaemonSetStatus\":                                                              schema_k8sio_api_apps_v1_DaemonSetStatus(ref), \"k8s.io/api/apps/v1.DaemonSetUpdateStrategy\":                                                      schema_k8sio_api_apps_v1_DaemonSetUpdateStrategy(ref), \"k8s.io/api/apps/v1.Deployment\":                                                                   schema_k8sio_api_apps_v1_Deployment(ref), \"k8s.io/api/apps/v1.DeploymentCondition\":                                                          schema_k8sio_api_apps_v1_DeploymentCondition(ref), \"k8s.io/api/apps/v1.DeploymentList\":                                                               schema_k8sio_api_apps_v1_DeploymentList(ref), \"k8s.io/api/apps/v1.DeploymentSpec\":                                                               schema_k8sio_api_apps_v1_DeploymentSpec(ref), \"k8s.io/api/apps/v1.DeploymentStatus\":                                                             schema_k8sio_api_apps_v1_DeploymentStatus(ref), \"k8s.io/api/apps/v1.DeploymentStrategy\":                                                           schema_k8sio_api_apps_v1_DeploymentStrategy(ref), \"k8s.io/api/apps/v1.ReplicaSet\":                                                                   schema_k8sio_api_apps_v1_ReplicaSet(ref), \"k8s.io/api/apps/v1.ReplicaSetCondition\":                                                          schema_k8sio_api_apps_v1_ReplicaSetCondition(ref), \"k8s.io/api/apps/v1.ReplicaSetList\":                                                               schema_k8sio_api_apps_v1_ReplicaSetList(ref), \"k8s.io/api/apps/v1.ReplicaSetSpec\":                                                               schema_k8sio_api_apps_v1_ReplicaSetSpec(ref), \"k8s.io/api/apps/v1.ReplicaSetStatus\":                                                             schema_k8sio_api_apps_v1_ReplicaSetStatus(ref), \"k8s.io/api/apps/v1.RollingUpdateDaemonSet\":                                                       schema_k8sio_api_apps_v1_RollingUpdateDaemonSet(ref), \"k8s.io/api/apps/v1.RollingUpdateDeployment\":                                                      schema_k8sio_api_apps_v1_RollingUpdateDeployment(ref), \"k8s.io/api/apps/v1.RollingUpdateStatefulSetStrategy\":                                             schema_k8sio_api_apps_v1_RollingUpdateStatefulSetStrategy(ref), \"k8s.io/api/apps/v1.StatefulSet\":                                                                  schema_k8sio_api_apps_v1_StatefulSet(ref), \"k8s.io/api/apps/v1.StatefulSetCondition\":                                                         schema_k8sio_api_apps_v1_StatefulSetCondition(ref), \"k8s.io/api/apps/v1.StatefulSetList\":                                                              schema_k8sio_api_apps_v1_StatefulSetList(ref), \"k8s.io/api/apps/v1.StatefulSetPersistentVolumeClaimRetentionPolicy\":                              schema_k8sio_api_apps_v1_StatefulSetPersistentVolumeClaimRetentionPolicy(ref), \"k8s.io/api/apps/v1.StatefulSetSpec\":                                                              schema_k8sio_api_apps_v1_StatefulSetSpec(ref), \"k8s.io/api/apps/v1.StatefulSetStatus\":                                                            schema_k8sio_api_apps_v1_StatefulSetStatus(ref), \"k8s.io/api/apps/v1.StatefulSetUpdateStrategy\":                                                    schema_k8sio_api_apps_v1_StatefulSetUpdateStrategy(ref), \"k8s.io/api/apps/v1beta1.ControllerRevision\":                                                      schema_k8sio_api_apps_v1beta1_ControllerRevision(ref), \"k8s.io/api/apps/v1beta1.ControllerRevisionList\":                                                  schema_k8sio_api_apps_v1beta1_ControllerRevisionList(ref), \"k8s.io/api/apps/v1beta1.Deployment\":                                                              schema_k8sio_api_apps_v1beta1_Deployment(ref), \"k8s.io/api/apps/v1beta1.DeploymentCondition\":                                                     schema_k8sio_api_apps_v1beta1_DeploymentCondition(ref), \"k8s.io/api/apps/v1beta1.DeploymentList\":                                                          schema_k8sio_api_apps_v1beta1_DeploymentList(ref), \"k8s.io/api/apps/v1beta1.DeploymentRollback\":                                                      schema_k8sio_api_apps_v1beta1_DeploymentRollback(ref), \"k8s.io/api/apps/v1beta1.DeploymentSpec\":                                                          schema_k8sio_api_apps_v1beta1_DeploymentSpec(ref), \"k8s.io/api/apps/v1beta1.DeploymentStatus\":                                                        schema_k8sio_api_apps_v1beta1_DeploymentStatus(ref), \"k8s.io/api/apps/v1beta1.DeploymentStrategy\":                                                      schema_k8sio_api_apps_v1beta1_DeploymentStrategy(ref), \"k8s.io/api/apps/v1beta1.RollbackConfig\":                                                          schema_k8sio_api_apps_v1beta1_RollbackConfig(ref), \"k8s.io/api/apps/v1beta1.RollingUpdateDeployment\":                                                 schema_k8sio_api_apps_v1beta1_RollingUpdateDeployment(ref), \"k8s.io/api/apps/v1beta1.RollingUpdateStatefulSetStrategy\":                                        schema_k8sio_api_apps_v1beta1_RollingUpdateStatefulSetStrategy(ref), \"k8s.io/api/apps/v1beta1.Scale\":                                                                   schema_k8sio_api_apps_v1beta1_Scale(ref), \"k8s.io/api/apps/v1beta1.ScaleSpec\":                                                               schema_k8sio_api_apps_v1beta1_ScaleSpec(ref), \"k8s.io/api/apps/v1beta1.ScaleStatus\":                                                             schema_k8sio_api_apps_v1beta1_ScaleStatus(ref), \"k8s.io/api/apps/v1beta1.StatefulSet\":                                                             schema_k8sio_api_apps_v1beta1_StatefulSet(ref), \"k8s.io/api/apps/v1beta1.StatefulSetCondition\":                                                    schema_k8sio_api_apps_v1beta1_StatefulSetCondition(ref), \"k8s.io/api/apps/v1beta1.StatefulSetList\":                                                         schema_k8sio_api_apps_v1beta1_StatefulSetList(ref), \"k8s.io/api/apps/v1beta1.StatefulSetPersistentVolumeClaimRetentionPolicy\":                         schema_k8sio_api_apps_v1beta1_StatefulSetPersistentVolumeClaimRetentionPolicy(ref), \"k8s.io/api/apps/v1beta1.StatefulSetSpec\":                                                         schema_k8sio_api_apps_v1beta1_StatefulSetSpec(ref), \"k8s.io/api/apps/v1beta1.StatefulSetStatus\":                                                       schema_k8sio_api_apps_v1beta1_StatefulSetStatus(ref), \"k8s.io/api/apps/v1beta1.StatefulSetUpdateStrategy\":                                               schema_k8sio_api_apps_v1beta1_StatefulSetUpdateStrategy(ref), \"k8s.io/api/apps/v1beta2.ControllerRevision\":                                                      schema_k8sio_api_apps_v1beta2_ControllerRevision(ref), \"k8s.io/api/apps/v1beta2.ControllerRevisionList\":                                                  schema_k8sio_api_apps_v1beta2_ControllerRevisionList(ref), \"k8s.io/api/apps/v1beta2.DaemonSet\":                                                               schema_k8sio_api_apps_v1beta2_DaemonSet(ref), \"k8s.io/api/apps/v1beta2.DaemonSetCondition\":                                                      schema_k8sio_api_apps_v1beta2_DaemonSetCondition(ref), \"k8s.io/api/apps/v1beta2.DaemonSetList\":                                                           schema_k8sio_api_apps_v1beta2_DaemonSetList(ref), \"k8s.io/api/apps/v1beta2.DaemonSetSpec\":                                                           schema_k8sio_api_apps_v1beta2_DaemonSetSpec(ref), \"k8s.io/api/apps/v1beta2.DaemonSetStatus\":                                                         schema_k8sio_api_apps_v1beta2_DaemonSetStatus(ref), \"k8s.io/api/apps/v1beta2.DaemonSetUpdateStrategy\":                                                 schema_k8sio_api_apps_v1beta2_DaemonSetUpdateStrategy(ref), \"k8s.io/api/apps/v1beta2.Deployment\":                                                              schema_k8sio_api_apps_v1beta2_Deployment(ref), \"k8s.io/api/apps/v1beta2.DeploymentCondition\":                                                     schema_k8sio_api_apps_v1beta2_DeploymentCondition(ref), \"k8s.io/api/apps/v1beta2.DeploymentList\":                                                          schema_k8sio_api_apps_v1beta2_DeploymentList(ref), \"k8s.io/api/apps/v1beta2.DeploymentSpec\":                                                          schema_k8sio_api_apps_v1beta2_DeploymentSpec(ref), \"k8s.io/api/apps/v1beta2.DeploymentStatus\":                                                        schema_k8sio_api_apps_v1beta2_DeploymentStatus(ref), \"k8s.io/api/apps/v1beta2.DeploymentStrategy\":                                                      schema_k8sio_api_apps_v1beta2_DeploymentStrategy(ref), \"k8s.io/api/apps/v1beta2.ReplicaSet\":                                                              schema_k8sio_api_apps_v1beta2_ReplicaSet(ref), \"k8s.io/api/apps/v1beta2.ReplicaSetCondition\":                                                     schema_k8sio_api_apps_v1beta2_ReplicaSetCondition(ref), \"k8s.io/api/apps/v1beta2.ReplicaSetList\":                                                          schema_k8sio_api_apps_v1beta2_ReplicaSetList(ref), \"k8s.io/api/apps/v1beta2.ReplicaSetSpec\":                                                          schema_k8sio_api_apps_v1beta2_ReplicaSetSpec(ref), \"k8s.io/api/apps/v1beta2.ReplicaSetStatus\":                                                        schema_k8sio_api_apps_v1beta2_ReplicaSetStatus(ref), \"k8s.io/api/apps/v1beta2.RollingUpdateDaemonSet\":                                                  schema_k8sio_api_apps_v1beta2_RollingUpdateDaemonSet(ref), \"k8s.io/api/apps/v1beta2.RollingUpdateDeployment\":                                                 schema_k8sio_api_apps_v1beta2_RollingUpdateDeployment(ref), \"k8s.io/api/apps/v1beta2.RollingUpdateStatefulSetStrategy\":                                        schema_k8sio_api_apps_v1beta2_RollingUpdateStatefulSetStrategy(ref), \"k8s.io/api/apps/v1beta2.Scale\":                                                                   schema_k8sio_api_apps_v1beta2_Scale(ref), \"k8s.io/api/apps/v1beta2.ScaleSpec\":                                                               schema_k8sio_api_apps_v1beta2_ScaleSpec(ref), \"k8s.io/api/apps/v1beta2.ScaleStatus\":                                                             schema_k8sio_api_apps_v1beta2_ScaleStatus(ref), \"k8s.io/api/apps/v1beta2.StatefulSet\":                                                             schema_k8sio_api_apps_v1beta2_StatefulSet(ref), \"k8s.io/api/apps/v1beta2.StatefulSetCondition\":                                                    schema_k8sio_api_apps_v1beta2_StatefulSetCondition(ref), \"k8s.io/api/apps/v1beta2.StatefulSetList\":                                                         schema_k8sio_api_apps_v1beta2_StatefulSetList(ref), \"k8s.io/api/apps/v1beta2.StatefulSetPersistentVolumeClaimRetentionPolicy\":                         schema_k8sio_api_apps_v1beta2_StatefulSetPersistentVolumeClaimRetentionPolicy(ref), \"k8s.io/api/apps/v1beta2.StatefulSetSpec\":                                                         schema_k8sio_api_apps_v1beta2_StatefulSetSpec(ref), \"k8s.io/api/apps/v1beta2.StatefulSetStatus\":                                                       schema_k8sio_api_apps_v1beta2_StatefulSetStatus(ref), \"k8s.io/api/apps/v1beta2.StatefulSetUpdateStrategy\":                                               schema_k8sio_api_apps_v1beta2_StatefulSetUpdateStrategy(ref), \"k8s.io/api/authentication/v1.BoundObjectReference\":                                               schema_k8sio_api_authentication_v1_BoundObjectReference(ref), \"k8s.io/api/authentication/v1.TokenRequest\":                                                       schema_k8sio_api_authentication_v1_TokenRequest(ref), \"k8s.io/api/authentication/v1.TokenRequestSpec\":                                                   schema_k8sio_api_authentication_v1_TokenRequestSpec(ref), \"k8s.io/api/authentication/v1.TokenRequestStatus\":                                                 schema_k8sio_api_authentication_v1_TokenRequestStatus(ref), \"k8s.io/api/authentication/v1.TokenReview\":                                                        schema_k8sio_api_authentication_v1_TokenReview(ref), \"k8s.io/api/authentication/v1.TokenReviewSpec\":                                                    schema_k8sio_api_authentication_v1_TokenReviewSpec(ref), \"k8s.io/api/authentication/v1.TokenReviewStatus\":                                                  schema_k8sio_api_authentication_v1_TokenReviewStatus(ref), \"k8s.io/api/authentication/v1.UserInfo\":                                                           schema_k8sio_api_authentication_v1_UserInfo(ref), \"k8s.io/api/authentication/v1beta1.TokenReview\":                                                   schema_k8sio_api_authentication_v1beta1_TokenReview(ref), \"k8s.io/api/authentication/v1beta1.TokenReviewSpec\":                                               schema_k8sio_api_authentication_v1beta1_TokenReviewSpec(ref), \"k8s.io/api/authentication/v1beta1.TokenReviewStatus\":                                             schema_k8sio_api_authentication_v1beta1_TokenReviewStatus(ref), \"k8s.io/api/authentication/v1beta1.UserInfo\":                                                      schema_k8sio_api_authentication_v1beta1_UserInfo(ref), \"k8s.io/api/authorization/v1.LocalSubjectAccessReview\":                                            schema_k8sio_api_authorization_v1_LocalSubjectAccessReview(ref), \"k8s.io/api/authorization/v1.NonResourceAttributes\":                                               schema_k8sio_api_authorization_v1_NonResourceAttributes(ref), \"k8s.io/api/authorization/v1.NonResourceRule\":                                                     schema_k8sio_api_authorization_v1_NonResourceRule(ref), \"k8s.io/api/authorization/v1.ResourceAttributes\":                                                  schema_k8sio_api_authorization_v1_ResourceAttributes(ref), \"k8s.io/api/authorization/v1.ResourceRule\":                                                        schema_k8sio_api_authorization_v1_ResourceRule(ref), \"k8s.io/api/authorization/v1.SelfSubjectAccessReview\":                                             schema_k8sio_api_authorization_v1_SelfSubjectAccessReview(ref), \"k8s.io/api/authorization/v1.SelfSubjectAccessReviewSpec\":                                         schema_k8sio_api_authorization_v1_SelfSubjectAccessReviewSpec(ref), \"k8s.io/api/authorization/v1.SelfSubjectRulesReview\":                                              schema_k8sio_api_authorization_v1_SelfSubjectRulesReview(ref), \"k8s.io/api/authorization/v1.SelfSubjectRulesReviewSpec\":                                          schema_k8sio_api_authorization_v1_SelfSubjectRulesReviewSpec(ref), \"k8s.io/api/authorization/v1.SubjectAccessReview\":                                                 schema_k8sio_api_authorization_v1_SubjectAccessReview(ref), \"k8s.io/api/authorization/v1.SubjectAccessReviewSpec\":                                             schema_k8sio_api_authorization_v1_SubjectAccessReviewSpec(ref), \"k8s.io/api/authorization/v1.SubjectAccessReviewStatus\":                                           schema_k8sio_api_authorization_v1_SubjectAccessReviewStatus(ref), \"k8s.io/api/authorization/v1.SubjectRulesReviewStatus\":                                            schema_k8sio_api_authorization_v1_SubjectRulesReviewStatus(ref), \"k8s.io/api/authorization/v1beta1.LocalSubjectAccessReview\":                                       schema_k8sio_api_authorization_v1beta1_LocalSubjectAccessReview(ref), \"k8s.io/api/authorization/v1beta1.NonResourceAttributes\":                                          schema_k8sio_api_authorization_v1beta1_NonResourceAttributes(ref), \"k8s.io/api/authorization/v1beta1.NonResourceRule\":                                                schema_k8sio_api_authorization_v1beta1_NonResourceRule(ref), \"k8s.io/api/authorization/v1beta1.ResourceAttributes\":                                             schema_k8sio_api_authorization_v1beta1_ResourceAttributes(ref), \"k8s.io/api/authorization/v1beta1.ResourceRule\":                                                   schema_k8sio_api_authorization_v1beta1_ResourceRule(ref), \"k8s.io/api/authorization/v1beta1.SelfSubjectAccessReview\":                                        schema_k8sio_api_authorization_v1beta1_SelfSubjectAccessReview(ref), \"k8s.io/api/authorization/v1beta1.SelfSubjectAccessReviewSpec\":                                    schema_k8sio_api_authorization_v1beta1_SelfSubjectAccessReviewSpec(ref), \"k8s.io/api/authorization/v1beta1.SelfSubjectRulesReview\":                                         schema_k8sio_api_authorization_v1beta1_SelfSubjectRulesReview(ref), \"k8s.io/api/authorization/v1beta1.SelfSubjectRulesReviewSpec\":                                     schema_k8sio_api_authorization_v1beta1_SelfSubjectRulesReviewSpec(ref), \"k8s.io/api/authorization/v1beta1.SubjectAccessReview\":                                            schema_k8sio_api_authorization_v1beta1_SubjectAccessReview(ref), \"k8s.io/api/authorization/v1beta1.SubjectAccessReviewSpec\":                                        schema_k8sio_api_authorization_v1beta1_SubjectAccessReviewSpec(ref), \"k8s.io/api/authorization/v1beta1.SubjectAccessReviewStatus\":                                      schema_k8sio_api_authorization_v1beta1_SubjectAccessReviewStatus(ref), \"k8s.io/api/authorization/v1beta1.SubjectRulesReviewStatus\":                                       schema_k8sio_api_authorization_v1beta1_SubjectRulesReviewStatus(ref), \"k8s.io/api/autoscaling/v1.ContainerResourceMetricSource\":                                         schema_k8sio_api_autoscaling_v1_ContainerResourceMetricSource(ref), \"k8s.io/api/autoscaling/v1.ContainerResourceMetricStatus\":                                         schema_k8sio_api_autoscaling_v1_ContainerResourceMetricStatus(ref), \"k8s.io/api/autoscaling/v1.CrossVersionObjectReference\":                                           schema_k8sio_api_autoscaling_v1_CrossVersionObjectReference(ref), \"k8s.io/api/autoscaling/v1.ExternalMetricSource\":                                                  schema_k8sio_api_autoscaling_v1_ExternalMetricSource(ref), \"k8s.io/api/autoscaling/v1.ExternalMetricStatus\":                                                  schema_k8sio_api_autoscaling_v1_ExternalMetricStatus(ref), \"k8s.io/api/autoscaling/v1.HorizontalPodAutoscaler\":                                               schema_k8sio_api_autoscaling_v1_HorizontalPodAutoscaler(ref), \"k8s.io/api/autoscaling/v1.HorizontalPodAutoscalerCondition\":                                      schema_k8sio_api_autoscaling_v1_HorizontalPodAutoscalerCondition(ref), \"k8s.io/api/autoscaling/v1.HorizontalPodAutoscalerList\":                                           schema_k8sio_api_autoscaling_v1_HorizontalPodAutoscalerList(ref), \"k8s.io/api/autoscaling/v1.HorizontalPodAutoscalerSpec\":                                           schema_k8sio_api_autoscaling_v1_HorizontalPodAutoscalerSpec(ref), \"k8s.io/api/autoscaling/v1.HorizontalPodAutoscalerStatus\":                                         schema_k8sio_api_autoscaling_v1_HorizontalPodAutoscalerStatus(ref), \"k8s.io/api/autoscaling/v1.MetricSpec\":                                                            schema_k8sio_api_autoscaling_v1_MetricSpec(ref), \"k8s.io/api/autoscaling/v1.MetricStatus\":                                                          schema_k8sio_api_autoscaling_v1_MetricStatus(ref), \"k8s.io/api/autoscaling/v1.ObjectMetricSource\":                                                    schema_k8sio_api_autoscaling_v1_ObjectMetricSource(ref), \"k8s.io/api/autoscaling/v1.ObjectMetricStatus\":                                                    schema_k8sio_api_autoscaling_v1_ObjectMetricStatus(ref), \"k8s.io/api/autoscaling/v1.PodsMetricSource\":                                                      schema_k8sio_api_autoscaling_v1_PodsMetricSource(ref), \"k8s.io/api/autoscaling/v1.PodsMetricStatus\":                                                      schema_k8sio_api_autoscaling_v1_PodsMetricStatus(ref), \"k8s.io/api/autoscaling/v1.ResourceMetricSource\":                                                  schema_k8sio_api_autoscaling_v1_ResourceMetricSource(ref), \"k8s.io/api/autoscaling/v1.ResourceMetricStatus\":                                                  schema_k8sio_api_autoscaling_v1_ResourceMetricStatus(ref), \"k8s.io/api/autoscaling/v1.Scale\":                                                                 schema_k8sio_api_autoscaling_v1_Scale(ref), \"k8s.io/api/autoscaling/v1.ScaleSpec\":                                                             schema_k8sio_api_autoscaling_v1_ScaleSpec(ref), \"k8s.io/api/autoscaling/v1.ScaleStatus\":                                                           schema_k8sio_api_autoscaling_v1_ScaleStatus(ref), \"k8s.io/api/autoscaling/v2.ContainerResourceMetricSource\":                                         schema_k8sio_api_autoscaling_v2_ContainerResourceMetricSource(ref), \"k8s.io/api/autoscaling/v2.ContainerResourceMetricStatus\":                                         schema_k8sio_api_autoscaling_v2_ContainerResourceMetricStatus(ref), \"k8s.io/api/autoscaling/v2.CrossVersionObjectReference\":                                           schema_k8sio_api_autoscaling_v2_CrossVersionObjectReference(ref), \"k8s.io/api/autoscaling/v2.ExternalMetricSource\":                                                  schema_k8sio_api_autoscaling_v2_ExternalMetricSource(ref), \"k8s.io/api/autoscaling/v2.ExternalMetricStatus\":                                                  schema_k8sio_api_autoscaling_v2_ExternalMetricStatus(ref), \"k8s.io/api/autoscaling/v2.HPAScalingPolicy\":                                                      schema_k8sio_api_autoscaling_v2_HPAScalingPolicy(ref), \"k8s.io/api/autoscaling/v2.HPAScalingRules\":                                                       schema_k8sio_api_autoscaling_v2_HPAScalingRules(ref), \"k8s.io/api/autoscaling/v2.HorizontalPodAutoscaler\":                                               schema_k8sio_api_autoscaling_v2_HorizontalPodAutoscaler(ref), \"k8s.io/api/autoscaling/v2.HorizontalPodAutoscalerBehavior\":                                       schema_k8sio_api_autoscaling_v2_HorizontalPodAutoscalerBehavior(ref), \"k8s.io/api/autoscaling/v2.HorizontalPodAutoscalerCondition\":                                      schema_k8sio_api_autoscaling_v2_HorizontalPodAutoscalerCondition(ref), \"k8s.io/api/autoscaling/v2.HorizontalPodAutoscalerList\":                                           schema_k8sio_api_autoscaling_v2_HorizontalPodAutoscalerList(ref), \"k8s.io/api/autoscaling/v2.HorizontalPodAutoscalerSpec\":                                           schema_k8sio_api_autoscaling_v2_HorizontalPodAutoscalerSpec(ref), \"k8s.io/api/autoscaling/v2.HorizontalPodAutoscalerStatus\":                                         schema_k8sio_api_autoscaling_v2_HorizontalPodAutoscalerStatus(ref), \"k8s.io/api/autoscaling/v2.MetricIdentifier\":                                                      schema_k8sio_api_autoscaling_v2_MetricIdentifier(ref), \"k8s.io/api/autoscaling/v2.MetricSpec\":                                                            schema_k8sio_api_autoscaling_v2_MetricSpec(ref), \"k8s.io/api/autoscaling/v2.MetricStatus\":                                                          schema_k8sio_api_autoscaling_v2_MetricStatus(ref), \"k8s.io/api/autoscaling/v2.MetricTarget\":                                                          schema_k8sio_api_autoscaling_v2_MetricTarget(ref), \"k8s.io/api/autoscaling/v2.MetricValueStatus\":                                                     schema_k8sio_api_autoscaling_v2_MetricValueStatus(ref), \"k8s.io/api/autoscaling/v2.ObjectMetricSource\":                                                    schema_k8sio_api_autoscaling_v2_ObjectMetricSource(ref), \"k8s.io/api/autoscaling/v2.ObjectMetricStatus\":                                                    schema_k8sio_api_autoscaling_v2_ObjectMetricStatus(ref), \"k8s.io/api/autoscaling/v2.PodsMetricSource\":                                                      schema_k8sio_api_autoscaling_v2_PodsMetricSource(ref), \"k8s.io/api/autoscaling/v2.PodsMetricStatus\":                                                      schema_k8sio_api_autoscaling_v2_PodsMetricStatus(ref), \"k8s.io/api/autoscaling/v2.ResourceMetricSource\":                                                  schema_k8sio_api_autoscaling_v2_ResourceMetricSource(ref), \"k8s.io/api/autoscaling/v2.ResourceMetricStatus\":                                                  schema_k8sio_api_autoscaling_v2_ResourceMetricStatus(ref), \"k8s.io/api/autoscaling/v2beta1.ContainerResourceMetricSource\":                                    schema_k8sio_api_autoscaling_v2beta1_ContainerResourceMetricSource(ref), \"k8s.io/api/autoscaling/v2beta1.ContainerResourceMetricStatus\":                                    schema_k8sio_api_autoscaling_v2beta1_ContainerResourceMetricStatus(ref), \"k8s.io/api/autoscaling/v2beta1.CrossVersionObjectReference\":                                      schema_k8sio_api_autoscaling_v2beta1_CrossVersionObjectReference(ref), \"k8s.io/api/autoscaling/v2beta1.ExternalMetricSource\":                                             schema_k8sio_api_autoscaling_v2beta1_ExternalMetricSource(ref), \"k8s.io/api/autoscaling/v2beta1.ExternalMetricStatus\":                                             schema_k8sio_api_autoscaling_v2beta1_ExternalMetricStatus(ref), \"k8s.io/api/autoscaling/v2beta1.HorizontalPodAutoscaler\":                                          schema_k8sio_api_autoscaling_v2beta1_HorizontalPodAutoscaler(ref), \"k8s.io/api/autoscaling/v2beta1.HorizontalPodAutoscalerCondition\":                                 schema_k8sio_api_autoscaling_v2beta1_HorizontalPodAutoscalerCondition(ref), \"k8s.io/api/autoscaling/v2beta1.HorizontalPodAutoscalerList\":                                      schema_k8sio_api_autoscaling_v2beta1_HorizontalPodAutoscalerList(ref), \"k8s.io/api/autoscaling/v2beta1.HorizontalPodAutoscalerSpec\":                                      schema_k8sio_api_autoscaling_v2beta1_HorizontalPodAutoscalerSpec(ref), \"k8s.io/api/autoscaling/v2beta1.HorizontalPodAutoscalerStatus\":                                    schema_k8sio_api_autoscaling_v2beta1_HorizontalPodAutoscalerStatus(ref), \"k8s.io/api/autoscaling/v2beta1.MetricSpec\":                                                       schema_k8sio_api_autoscaling_v2beta1_MetricSpec(ref), \"k8s.io/api/autoscaling/v2beta1.MetricStatus\":                                                     schema_k8sio_api_autoscaling_v2beta1_MetricStatus(ref), \"k8s.io/api/autoscaling/v2beta1.ObjectMetricSource\":                                               schema_k8sio_api_autoscaling_v2beta1_ObjectMetricSource(ref), \"k8s.io/api/autoscaling/v2beta1.ObjectMetricStatus\":                                               schema_k8sio_api_autoscaling_v2beta1_ObjectMetricStatus(ref), \"k8s.io/api/autoscaling/v2beta1.PodsMetricSource\":                                                 schema_k8sio_api_autoscaling_v2beta1_PodsMetricSource(ref), \"k8s.io/api/autoscaling/v2beta1.PodsMetricStatus\":                                                 schema_k8sio_api_autoscaling_v2beta1_PodsMetricStatus(ref), \"k8s.io/api/autoscaling/v2beta1.ResourceMetricSource\":                                             schema_k8sio_api_autoscaling_v2beta1_ResourceMetricSource(ref), \"k8s.io/api/autoscaling/v2beta1.ResourceMetricStatus\":                                             schema_k8sio_api_autoscaling_v2beta1_ResourceMetricStatus(ref), \"k8s.io/api/autoscaling/v2beta2.ContainerResourceMetricSource\":                                    schema_k8sio_api_autoscaling_v2beta2_ContainerResourceMetricSource(ref), \"k8s.io/api/autoscaling/v2beta2.ContainerResourceMetricStatus\":                                    schema_k8sio_api_autoscaling_v2beta2_ContainerResourceMetricStatus(ref), \"k8s.io/api/autoscaling/v2beta2.CrossVersionObjectReference\":                                      schema_k8sio_api_autoscaling_v2beta2_CrossVersionObjectReference(ref), \"k8s.io/api/autoscaling/v2beta2.ExternalMetricSource\":                                             schema_k8sio_api_autoscaling_v2beta2_ExternalMetricSource(ref), \"k8s.io/api/autoscaling/v2beta2.ExternalMetricStatus\":                                             schema_k8sio_api_autoscaling_v2beta2_ExternalMetricStatus(ref), \"k8s.io/api/autoscaling/v2beta2.HPAScalingPolicy\":                                                 schema_k8sio_api_autoscaling_v2beta2_HPAScalingPolicy(ref), \"k8s.io/api/autoscaling/v2beta2.HPAScalingRules\":                                                  schema_k8sio_api_autoscaling_v2beta2_HPAScalingRules(ref), \"k8s.io/api/autoscaling/v2beta2.HorizontalPodAutoscaler\":                                          schema_k8sio_api_autoscaling_v2beta2_HorizontalPodAutoscaler(ref), \"k8s.io/api/autoscaling/v2beta2.HorizontalPodAutoscalerBehavior\":                                  schema_k8sio_api_autoscaling_v2beta2_HorizontalPodAutoscalerBehavior(ref), \"k8s.io/api/autoscaling/v2beta2.HorizontalPodAutoscalerCondition\":                                 schema_k8sio_api_autoscaling_v2beta2_HorizontalPodAutoscalerCondition(ref), \"k8s.io/api/autoscaling/v2beta2.HorizontalPodAutoscalerList\":                                      schema_k8sio_api_autoscaling_v2beta2_HorizontalPodAutoscalerList(ref), \"k8s.io/api/autoscaling/v2beta2.HorizontalPodAutoscalerSpec\":                                      schema_k8sio_api_autoscaling_v2beta2_HorizontalPodAutoscalerSpec(ref), \"k8s.io/api/autoscaling/v2beta2.HorizontalPodAutoscalerStatus\":                                    schema_k8sio_api_autoscaling_v2beta2_HorizontalPodAutoscalerStatus(ref), \"k8s.io/api/autoscaling/v2beta2.MetricIdentifier\":                                                 schema_k8sio_api_autoscaling_v2beta2_MetricIdentifier(ref), \"k8s.io/api/autoscaling/v2beta2.MetricSpec\":                                                       schema_k8sio_api_autoscaling_v2beta2_MetricSpec(ref), \"k8s.io/api/autoscaling/v2beta2.MetricStatus\":                                                     schema_k8sio_api_autoscaling_v2beta2_MetricStatus(ref), \"k8s.io/api/autoscaling/v2beta2.MetricTarget\":                                                     schema_k8sio_api_autoscaling_v2beta2_MetricTarget(ref), \"k8s.io/api/autoscaling/v2beta2.MetricValueStatus\":                                                schema_k8sio_api_autoscaling_v2beta2_MetricValueStatus(ref), \"k8s.io/api/autoscaling/v2beta2.ObjectMetricSource\":                                               schema_k8sio_api_autoscaling_v2beta2_ObjectMetricSource(ref), \"k8s.io/api/autoscaling/v2beta2.ObjectMetricStatus\":                                               schema_k8sio_api_autoscaling_v2beta2_ObjectMetricStatus(ref), \"k8s.io/api/autoscaling/v2beta2.PodsMetricSource\":                                                 schema_k8sio_api_autoscaling_v2beta2_PodsMetricSource(ref), \"k8s.io/api/autoscaling/v2beta2.PodsMetricStatus\":                                                 schema_k8sio_api_autoscaling_v2beta2_PodsMetricStatus(ref), \"k8s.io/api/autoscaling/v2beta2.ResourceMetricSource\":                                             schema_k8sio_api_autoscaling_v2beta2_ResourceMetricSource(ref), \"k8s.io/api/autoscaling/v2beta2.ResourceMetricStatus\":                                             schema_k8sio_api_autoscaling_v2beta2_ResourceMetricStatus(ref), \"k8s.io/api/batch/v1.CronJob\":                                                                     schema_k8sio_api_batch_v1_CronJob(ref), \"k8s.io/api/batch/v1.CronJobList\":                                                                 schema_k8sio_api_batch_v1_CronJobList(ref), \"k8s.io/api/batch/v1.CronJobSpec\":                                                                 schema_k8sio_api_batch_v1_CronJobSpec(ref), \"k8s.io/api/batch/v1.CronJobStatus\":                                                               schema_k8sio_api_batch_v1_CronJobStatus(ref), \"k8s.io/api/batch/v1.Job\":                                                                         schema_k8sio_api_batch_v1_Job(ref), \"k8s.io/api/batch/v1.JobCondition\":                                                                schema_k8sio_api_batch_v1_JobCondition(ref), \"k8s.io/api/batch/v1.JobList\":                                                                     schema_k8sio_api_batch_v1_JobList(ref), \"k8s.io/api/batch/v1.JobSpec\":                                                                     schema_k8sio_api_batch_v1_JobSpec(ref), \"k8s.io/api/batch/v1.JobStatus\":                                                                   schema_k8sio_api_batch_v1_JobStatus(ref), \"k8s.io/api/batch/v1.JobTemplateSpec\":                                                             schema_k8sio_api_batch_v1_JobTemplateSpec(ref), \"k8s.io/api/batch/v1.UncountedTerminatedPods\":                                                     schema_k8sio_api_batch_v1_UncountedTerminatedPods(ref), \"k8s.io/api/batch/v1beta1.CronJob\":                                                                schema_k8sio_api_batch_v1beta1_CronJob(ref), \"k8s.io/api/batch/v1beta1.CronJobList\":                                                            schema_k8sio_api_batch_v1beta1_CronJobList(ref), \"k8s.io/api/batch/v1beta1.CronJobSpec\":                                                            schema_k8sio_api_batch_v1beta1_CronJobSpec(ref), \"k8s.io/api/batch/v1beta1.CronJobStatus\":                                                          schema_k8sio_api_batch_v1beta1_CronJobStatus(ref), \"k8s.io/api/batch/v1beta1.JobTemplate\":                                                            schema_k8sio_api_batch_v1beta1_JobTemplate(ref), \"k8s.io/api/batch/v1beta1.JobTemplateSpec\":                                                        schema_k8sio_api_batch_v1beta1_JobTemplateSpec(ref), \"k8s.io/api/certificates/v1.CertificateSigningRequest\":                                            schema_k8sio_api_certificates_v1_CertificateSigningRequest(ref), \"k8s.io/api/certificates/v1.CertificateSigningRequestCondition\":                                   schema_k8sio_api_certificates_v1_CertificateSigningRequestCondition(ref), \"k8s.io/api/certificates/v1.CertificateSigningRequestList\":                                        schema_k8sio_api_certificates_v1_CertificateSigningRequestList(ref), \"k8s.io/api/certificates/v1.CertificateSigningRequestSpec\":                                        schema_k8sio_api_certificates_v1_CertificateSigningRequestSpec(ref), \"k8s.io/api/certificates/v1.CertificateSigningRequestStatus\":                                      schema_k8sio_api_certificates_v1_CertificateSigningRequestStatus(ref), \"k8s.io/api/certificates/v1beta1.CertificateSigningRequest\":                                       schema_k8sio_api_certificates_v1beta1_CertificateSigningRequest(ref), \"k8s.io/api/certificates/v1beta1.CertificateSigningRequestCondition\":                              schema_k8sio_api_certificates_v1beta1_CertificateSigningRequestCondition(ref), \"k8s.io/api/certificates/v1beta1.CertificateSigningRequestList\":                                   schema_k8sio_api_certificates_v1beta1_CertificateSigningRequestList(ref), \"k8s.io/api/certificates/v1beta1.CertificateSigningRequestSpec\":                                   schema_k8sio_api_certificates_v1beta1_CertificateSigningRequestSpec(ref), \"k8s.io/api/certificates/v1beta1.CertificateSigningRequestStatus\":                                 schema_k8sio_api_certificates_v1beta1_CertificateSigningRequestStatus(ref), \"k8s.io/api/coordination/v1.Lease\":                                                                schema_k8sio_api_coordination_v1_Lease(ref), \"k8s.io/api/coordination/v1.LeaseList\":                                                            schema_k8sio_api_coordination_v1_LeaseList(ref), \"k8s.io/api/coordination/v1.LeaseSpec\":                                                            schema_k8sio_api_coordination_v1_LeaseSpec(ref), \"k8s.io/api/coordination/v1beta1.Lease\":                                                           schema_k8sio_api_coordination_v1beta1_Lease(ref), \"k8s.io/api/coordination/v1beta1.LeaseList\":                                                       schema_k8sio_api_coordination_v1beta1_LeaseList(ref), \"k8s.io/api/coordination/v1beta1.LeaseSpec\":                                                       schema_k8sio_api_coordination_v1beta1_LeaseSpec(ref), \"k8s.io/api/core/v1.AWSElasticBlockStoreVolumeSource\":                                             schema_k8sio_api_core_v1_AWSElasticBlockStoreVolumeSource(ref), \"k8s.io/api/core/v1.Affinity\":                                                                     schema_k8sio_api_core_v1_Affinity(ref), \"k8s.io/api/core/v1.AttachedVolume\":                                                               schema_k8sio_api_core_v1_AttachedVolume(ref), \"k8s.io/api/core/v1.AvoidPods\":                                                                    schema_k8sio_api_core_v1_AvoidPods(ref), \"k8s.io/api/core/v1.AzureDiskVolumeSource\":                                                        schema_k8sio_api_core_v1_AzureDiskVolumeSource(ref), \"k8s.io/api/core/v1.AzureFilePersistentVolumeSource\":                                              schema_k8sio_api_core_v1_AzureFilePersistentVolumeSource(ref), \"k8s.io/api/core/v1.AzureFileVolumeSource\":                                                        schema_k8sio_api_core_v1_AzureFileVolumeSource(ref), \"k8s.io/api/core/v1.Binding\":                                                                      schema_k8sio_api_core_v1_Binding(ref), \"k8s.io/api/core/v1.CSIPersistentVolumeSource\":                                                    schema_k8sio_api_core_v1_CSIPersistentVolumeSource(ref), \"k8s.io/api/core/v1.CSIVolumeSource\":                                                              schema_k8sio_api_core_v1_CSIVolumeSource(ref), \"k8s.io/api/core/v1.Capabilities\":                                                                 schema_k8sio_api_core_v1_Capabilities(ref), \"k8s.io/api/core/v1.CephFSPersistentVolumeSource\":                                                 schema_k8sio_api_core_v1_CephFSPersistentVolumeSource(ref), \"k8s.io/api/core/v1.CephFSVolumeSource\":                                                           schema_k8sio_api_core_v1_CephFSVolumeSource(ref), \"k8s.io/api/core/v1.CinderPersistentVolumeSource\":                                                 schema_k8sio_api_core_v1_CinderPersistentVolumeSource(ref), \"k8s.io/api/core/v1.CinderVolumeSource\":                                                           schema_k8sio_api_core_v1_CinderVolumeSource(ref), \"k8s.io/api/core/v1.ClientIPConfig\":                                                               schema_k8sio_api_core_v1_ClientIPConfig(ref), \"k8s.io/api/core/v1.ComponentCondition\":                                                           schema_k8sio_api_core_v1_ComponentCondition(ref), \"k8s.io/api/core/v1.ComponentStatus\":                                                              schema_k8sio_api_core_v1_ComponentStatus(ref), \"k8s.io/api/core/v1.ComponentStatusList\":                                                          schema_k8sio_api_core_v1_ComponentStatusList(ref), \"k8s.io/api/core/v1.ConfigMap\":                                                                    schema_k8sio_api_core_v1_ConfigMap(ref), \"k8s.io/api/core/v1.ConfigMapEnvSource\":                                                           schema_k8sio_api_core_v1_ConfigMapEnvSource(ref), \"k8s.io/api/core/v1.ConfigMapKeySelector\":                                                         schema_k8sio_api_core_v1_ConfigMapKeySelector(ref), \"k8s.io/api/core/v1.ConfigMapList\":                                                                schema_k8sio_api_core_v1_ConfigMapList(ref), \"k8s.io/api/core/v1.ConfigMapNodeConfigSource\":                                                    schema_k8sio_api_core_v1_ConfigMapNodeConfigSource(ref), \"k8s.io/api/core/v1.ConfigMapProjection\":                                                          schema_k8sio_api_core_v1_ConfigMapProjection(ref), \"k8s.io/api/core/v1.ConfigMapVolumeSource\":                                                        schema_k8sio_api_core_v1_ConfigMapVolumeSource(ref), \"k8s.io/api/core/v1.Container\":                                                                    schema_k8sio_api_core_v1_Container(ref), \"k8s.io/api/core/v1.ContainerImage\":                                                               schema_k8sio_api_core_v1_ContainerImage(ref), \"k8s.io/api/core/v1.ContainerPort\":                                                                schema_k8sio_api_core_v1_ContainerPort(ref), \"k8s.io/api/core/v1.ContainerState\":                                                               schema_k8sio_api_core_v1_ContainerState(ref), \"k8s.io/api/core/v1.ContainerStateRunning\":                                                        schema_k8sio_api_core_v1_ContainerStateRunning(ref), \"k8s.io/api/core/v1.ContainerStateTerminated\":                                                     schema_k8sio_api_core_v1_ContainerStateTerminated(ref), \"k8s.io/api/core/v1.ContainerStateWaiting\":                                                        schema_k8sio_api_core_v1_ContainerStateWaiting(ref), \"k8s.io/api/core/v1.ContainerStatus\":                                                              schema_k8sio_api_core_v1_ContainerStatus(ref), \"k8s.io/api/core/v1.DaemonEndpoint\":                                                               schema_k8sio_api_core_v1_DaemonEndpoint(ref), \"k8s.io/api/core/v1.DownwardAPIProjection\":                                                        schema_k8sio_api_core_v1_DownwardAPIProjection(ref), \"k8s.io/api/core/v1.DownwardAPIVolumeFile\":                                                        schema_k8sio_api_core_v1_DownwardAPIVolumeFile(ref), \"k8s.io/api/core/v1.DownwardAPIVolumeSource\":                                                      schema_k8sio_api_core_v1_DownwardAPIVolumeSource(ref), \"k8s.io/api/core/v1.EmptyDirVolumeSource\":                                                         schema_k8sio_api_core_v1_EmptyDirVolumeSource(ref), \"k8s.io/api/core/v1.EndpointAddress\":                                                              schema_k8sio_api_core_v1_EndpointAddress(ref), \"k8s.io/api/core/v1.EndpointPort\":                                                                 schema_k8sio_api_core_v1_EndpointPort(ref), \"k8s.io/api/core/v1.EndpointSubset\":                                                               schema_k8sio_api_core_v1_EndpointSubset(ref), \"k8s.io/api/core/v1.Endpoints\":                                                                    schema_k8sio_api_core_v1_Endpoints(ref), \"k8s.io/api/core/v1.EndpointsList\":                                                                schema_k8sio_api_core_v1_EndpointsList(ref), \"k8s.io/api/core/v1.EnvFromSource\":                                                                schema_k8sio_api_core_v1_EnvFromSource(ref), \"k8s.io/api/core/v1.EnvVar\":                                                                       schema_k8sio_api_core_v1_EnvVar(ref), \"k8s.io/api/core/v1.EnvVarSource\":                                                                 schema_k8sio_api_core_v1_EnvVarSource(ref), \"k8s.io/api/core/v1.EphemeralContainer\":                                                           schema_k8sio_api_core_v1_EphemeralContainer(ref), \"k8s.io/api/core/v1.EphemeralContainerCommon\":                                                     schema_k8sio_api_core_v1_EphemeralContainerCommon(ref), \"k8s.io/api/core/v1.EphemeralVolumeSource\":                                                        schema_k8sio_api_core_v1_EphemeralVolumeSource(ref), \"k8s.io/api/core/v1.Event\":                                                                        schema_k8sio_api_core_v1_Event(ref), \"k8s.io/api/core/v1.EventList\":                                                                    schema_k8sio_api_core_v1_EventList(ref), \"k8s.io/api/core/v1.EventSeries\":                                                                  schema_k8sio_api_core_v1_EventSeries(ref), \"k8s.io/api/core/v1.EventSource\":                                                                  schema_k8sio_api_core_v1_EventSource(ref), \"k8s.io/api/core/v1.ExecAction\":                                                                   schema_k8sio_api_core_v1_ExecAction(ref), \"k8s.io/api/core/v1.FCVolumeSource\":                                                               schema_k8sio_api_core_v1_FCVolumeSource(ref), \"k8s.io/api/core/v1.FlexPersistentVolumeSource\":                                                   schema_k8sio_api_core_v1_FlexPersistentVolumeSource(ref), \"k8s.io/api/core/v1.FlexVolumeSource\":                                                             schema_k8sio_api_core_v1_FlexVolumeSource(ref), \"k8s.io/api/core/v1.FlockerVolumeSource\":                                                          schema_k8sio_api_core_v1_FlockerVolumeSource(ref), \"k8s.io/api/core/v1.GCEPersistentDiskVolumeSource\":                                                schema_k8sio_api_core_v1_GCEPersistentDiskVolumeSource(ref), \"k8s.io/api/core/v1.GRPCAction\":                                                                   schema_k8sio_api_core_v1_GRPCAction(ref), \"k8s.io/api/core/v1.GitRepoVolumeSource\":                                                          schema_k8sio_api_core_v1_GitRepoVolumeSource(ref), \"k8s.io/api/core/v1.GlusterfsPersistentVolumeSource\":                                              schema_k8sio_api_core_v1_GlusterfsPersistentVolumeSource(ref), \"k8s.io/api/core/v1.GlusterfsVolumeSource\":                                                        schema_k8sio_api_core_v1_GlusterfsVolumeSource(ref), \"k8s.io/api/core/v1.HTTPGetAction\":                                                                schema_k8sio_api_core_v1_HTTPGetAction(ref), \"k8s.io/api/core/v1.HTTPHeader\":                                                                   schema_k8sio_api_core_v1_HTTPHeader(ref), \"k8s.io/api/core/v1.HostAlias\":                                                                    schema_k8sio_api_core_v1_HostAlias(ref), \"k8s.io/api/core/v1.HostPathVolumeSource\":                                                         schema_k8sio_api_core_v1_HostPathVolumeSource(ref), \"k8s.io/api/core/v1.ISCSIPersistentVolumeSource\":                                                  schema_k8sio_api_core_v1_ISCSIPersistentVolumeSource(ref), \"k8s.io/api/core/v1.ISCSIVolumeSource\":                                                            schema_k8sio_api_core_v1_ISCSIVolumeSource(ref), \"k8s.io/api/core/v1.KeyToPath\":                                                                    schema_k8sio_api_core_v1_KeyToPath(ref), \"k8s.io/api/core/v1.Lifecycle\":                                                                    schema_k8sio_api_core_v1_Lifecycle(ref), \"k8s.io/api/core/v1.LifecycleHandler\":                                                             schema_k8sio_api_core_v1_LifecycleHandler(ref), \"k8s.io/api/core/v1.LimitRange\":                                                                   schema_k8sio_api_core_v1_LimitRange(ref), \"k8s.io/api/core/v1.LimitRangeItem\":                                                               schema_k8sio_api_core_v1_LimitRangeItem(ref), \"k8s.io/api/core/v1.LimitRangeList\":                                                               schema_k8sio_api_core_v1_LimitRangeList(ref), \"k8s.io/api/core/v1.LimitRangeSpec\":                                                               schema_k8sio_api_core_v1_LimitRangeSpec(ref), \"k8s.io/api/core/v1.List\":                                                                         schema_k8sio_api_core_v1_List(ref), \"k8s.io/api/core/v1.LoadBalancerIngress\":                                                          schema_k8sio_api_core_v1_LoadBalancerIngress(ref), \"k8s.io/api/core/v1.LoadBalancerStatus\":                                                           schema_k8sio_api_core_v1_LoadBalancerStatus(ref), \"k8s.io/api/core/v1.LocalObjectReference\":                                                         schema_k8sio_api_core_v1_LocalObjectReference(ref), \"k8s.io/api/core/v1.LocalVolumeSource\":                                                            schema_k8sio_api_core_v1_LocalVolumeSource(ref), \"k8s.io/api/core/v1.NFSVolumeSource\":                                                              schema_k8sio_api_core_v1_NFSVolumeSource(ref), \"k8s.io/api/core/v1.Namespace\":                                                                    schema_k8sio_api_core_v1_Namespace(ref), \"k8s.io/api/core/v1.NamespaceCondition\":                                                           schema_k8sio_api_core_v1_NamespaceCondition(ref), \"k8s.io/api/core/v1.NamespaceList\":                                                                schema_k8sio_api_core_v1_NamespaceList(ref), \"k8s.io/api/core/v1.NamespaceSpec\":                                                                schema_k8sio_api_core_v1_NamespaceSpec(ref), \"k8s.io/api/core/v1.NamespaceStatus\":                                                              schema_k8sio_api_core_v1_NamespaceStatus(ref), \"k8s.io/api/core/v1.Node\":                                                                         schema_k8sio_api_core_v1_Node(ref), \"k8s.io/api/core/v1.NodeAddress\":                                                                  schema_k8sio_api_core_v1_NodeAddress(ref), \"k8s.io/api/core/v1.NodeAffinity\":                                                                 schema_k8sio_api_core_v1_NodeAffinity(ref), \"k8s.io/api/core/v1.NodeCondition\":                                                                schema_k8sio_api_core_v1_NodeCondition(ref), \"k8s.io/api/core/v1.NodeConfigSource\":                                                             schema_k8sio_api_core_v1_NodeConfigSource(ref), \"k8s.io/api/core/v1.NodeConfigStatus\":                                                             schema_k8sio_api_core_v1_NodeConfigStatus(ref), \"k8s.io/api/core/v1.NodeDaemonEndpoints\":                                                          schema_k8sio_api_core_v1_NodeDaemonEndpoints(ref), \"k8s.io/api/core/v1.NodeList\":                                                                     schema_k8sio_api_core_v1_NodeList(ref), \"k8s.io/api/core/v1.NodeProxyOptions\":                                                             schema_k8sio_api_core_v1_NodeProxyOptions(ref), \"k8s.io/api/core/v1.NodeResources\":                                                                schema_k8sio_api_core_v1_NodeResources(ref), \"k8s.io/api/core/v1.NodeSelector\":                                                                 schema_k8sio_api_core_v1_NodeSelector(ref), \"k8s.io/api/core/v1.NodeSelectorRequirement\":                                                      schema_k8sio_api_core_v1_NodeSelectorRequirement(ref), \"k8s.io/api/core/v1.NodeSelectorTerm\":                                                             schema_k8sio_api_core_v1_NodeSelectorTerm(ref), \"k8s.io/api/core/v1.NodeSpec\":                                                                     schema_k8sio_api_core_v1_NodeSpec(ref), \"k8s.io/api/core/v1.NodeStatus\":                                                                   schema_k8sio_api_core_v1_NodeStatus(ref), \"k8s.io/api/core/v1.NodeSystemInfo\":                                                               schema_k8sio_api_core_v1_NodeSystemInfo(ref), \"k8s.io/api/core/v1.ObjectFieldSelector\":                                                          schema_k8sio_api_core_v1_ObjectFieldSelector(ref), \"k8s.io/api/core/v1.ObjectReference\":                                                              schema_k8sio_api_core_v1_ObjectReference(ref), \"k8s.io/api/core/v1.PersistentVolume\":                                                             schema_k8sio_api_core_v1_PersistentVolume(ref), \"k8s.io/api/core/v1.PersistentVolumeClaim\":                                                        schema_k8sio_api_core_v1_PersistentVolumeClaim(ref), \"k8s.io/api/core/v1.PersistentVolumeClaimCondition\":                                               schema_k8sio_api_core_v1_PersistentVolumeClaimCondition(ref), \"k8s.io/api/core/v1.PersistentVolumeClaimList\":                                                    schema_k8sio_api_core_v1_PersistentVolumeClaimList(ref), \"k8s.io/api/core/v1.PersistentVolumeClaimSpec\":                                                    schema_k8sio_api_core_v1_PersistentVolumeClaimSpec(ref), \"k8s.io/api/core/v1.PersistentVolumeClaimStatus\":                                                  schema_k8sio_api_core_v1_PersistentVolumeClaimStatus(ref), \"k8s.io/api/core/v1.PersistentVolumeClaimTemplate\":                                                schema_k8sio_api_core_v1_PersistentVolumeClaimTemplate(ref), \"k8s.io/api/core/v1.PersistentVolumeClaimVolumeSource\":                                            schema_k8sio_api_core_v1_PersistentVolumeClaimVolumeSource(ref), \"k8s.io/api/core/v1.PersistentVolumeList\":                                                         schema_k8sio_api_core_v1_PersistentVolumeList(ref), \"k8s.io/api/core/v1.PersistentVolumeSource\":                                                       schema_k8sio_api_core_v1_PersistentVolumeSource(ref), \"k8s.io/api/core/v1.PersistentVolumeSpec\":                                                         schema_k8sio_api_core_v1_PersistentVolumeSpec(ref), \"k8s.io/api/core/v1.PersistentVolumeStatus\":                                                       schema_k8sio_api_core_v1_PersistentVolumeStatus(ref), \"k8s.io/api/core/v1.PhotonPersistentDiskVolumeSource\":                                             schema_k8sio_api_core_v1_PhotonPersistentDiskVolumeSource(ref), \"k8s.io/api/core/v1.Pod\":                                                                          schema_k8sio_api_core_v1_Pod(ref), \"k8s.io/api/core/v1.PodAffinity\":                                                                  schema_k8sio_api_core_v1_PodAffinity(ref), \"k8s.io/api/core/v1.PodAffinityTerm\":                                                              schema_k8sio_api_core_v1_PodAffinityTerm(ref), \"k8s.io/api/core/v1.PodAntiAffinity\":                                                              schema_k8sio_api_core_v1_PodAntiAffinity(ref), \"k8s.io/api/core/v1.PodAttachOptions\":                                                             schema_k8sio_api_core_v1_PodAttachOptions(ref), \"k8s.io/api/core/v1.PodCondition\":                                                                 schema_k8sio_api_core_v1_PodCondition(ref), \"k8s.io/api/core/v1.PodDNSConfig\":                                                                 schema_k8sio_api_core_v1_PodDNSConfig(ref), \"k8s.io/api/core/v1.PodDNSConfigOption\":                                                           schema_k8sio_api_core_v1_PodDNSConfigOption(ref), \"k8s.io/api/core/v1.PodExecOptions\":                                                               schema_k8sio_api_core_v1_PodExecOptions(ref), \"k8s.io/api/core/v1.PodIP\":                                                                        schema_k8sio_api_core_v1_PodIP(ref), \"k8s.io/api/core/v1.PodList\":                                                                      schema_k8sio_api_core_v1_PodList(ref), \"k8s.io/api/core/v1.PodLogOptions\":                                                                schema_k8sio_api_core_v1_PodLogOptions(ref), \"k8s.io/api/core/v1.PodOS\":                                                                        schema_k8sio_api_core_v1_PodOS(ref), \"k8s.io/api/core/v1.PodPortForwardOptions\":                                                        schema_k8sio_api_core_v1_PodPortForwardOptions(ref), \"k8s.io/api/core/v1.PodProxyOptions\":                                                              schema_k8sio_api_core_v1_PodProxyOptions(ref), \"k8s.io/api/core/v1.PodReadinessGate\":                                                             schema_k8sio_api_core_v1_PodReadinessGate(ref), \"k8s.io/api/core/v1.PodSecurityContext\":                                                           schema_k8sio_api_core_v1_PodSecurityContext(ref), \"k8s.io/api/core/v1.PodSignature\":                                                                 schema_k8sio_api_core_v1_PodSignature(ref), \"k8s.io/api/core/v1.PodSpec\":                                                                      schema_k8sio_api_core_v1_PodSpec(ref), \"k8s.io/api/core/v1.PodStatus\":                                                                    schema_k8sio_api_core_v1_PodStatus(ref), \"k8s.io/api/core/v1.PodStatusResult\":                                                              schema_k8sio_api_core_v1_PodStatusResult(ref), \"k8s.io/api/core/v1.PodTemplate\":                                                                  schema_k8sio_api_core_v1_PodTemplate(ref), \"k8s.io/api/core/v1.PodTemplateList\":                                                              schema_k8sio_api_core_v1_PodTemplateList(ref), \"k8s.io/api/core/v1.PodTemplateSpec\":                                                              schema_k8sio_api_core_v1_PodTemplateSpec(ref), \"k8s.io/api/core/v1.PortStatus\":                                                                   schema_k8sio_api_core_v1_PortStatus(ref), \"k8s.io/api/core/v1.PortworxVolumeSource\":                                                         schema_k8sio_api_core_v1_PortworxVolumeSource(ref), \"k8s.io/api/core/v1.PreferAvoidPodsEntry\":                                                         schema_k8sio_api_core_v1_PreferAvoidPodsEntry(ref), \"k8s.io/api/core/v1.PreferredSchedulingTerm\":                                                      schema_k8sio_api_core_v1_PreferredSchedulingTerm(ref), \"k8s.io/api/core/v1.Probe\":                                                                        schema_k8sio_api_core_v1_Probe(ref), \"k8s.io/api/core/v1.ProbeHandler\":                                                                 schema_k8sio_api_core_v1_ProbeHandler(ref), \"k8s.io/api/core/v1.ProjectedVolumeSource\":                                                        schema_k8sio_api_core_v1_ProjectedVolumeSource(ref), \"k8s.io/api/core/v1.QuobyteVolumeSource\":                                                          schema_k8sio_api_core_v1_QuobyteVolumeSource(ref), \"k8s.io/api/core/v1.RBDPersistentVolumeSource\":                                                    schema_k8sio_api_core_v1_RBDPersistentVolumeSource(ref), \"k8s.io/api/core/v1.RBDVolumeSource\":                                                              schema_k8sio_api_core_v1_RBDVolumeSource(ref), \"k8s.io/api/core/v1.RangeAllocation\":                                                              schema_k8sio_api_core_v1_RangeAllocation(ref), \"k8s.io/api/core/v1.ReplicationController\":                                                        schema_k8sio_api_core_v1_ReplicationController(ref), \"k8s.io/api/core/v1.ReplicationControllerCondition\":                                               schema_k8sio_api_core_v1_ReplicationControllerCondition(ref), \"k8s.io/api/core/v1.ReplicationControllerList\":                                                    schema_k8sio_api_core_v1_ReplicationControllerList(ref), \"k8s.io/api/core/v1.ReplicationControllerSpec\":                                                    schema_k8sio_api_core_v1_ReplicationControllerSpec(ref), \"k8s.io/api/core/v1.ReplicationControllerStatus\":                                                  schema_k8sio_api_core_v1_ReplicationControllerStatus(ref), \"k8s.io/api/core/v1.ResourceFieldSelector\":                                                        schema_k8sio_api_core_v1_ResourceFieldSelector(ref), \"k8s.io/api/core/v1.ResourceQuota\":                                                                schema_k8sio_api_core_v1_ResourceQuota(ref), \"k8s.io/api/core/v1.ResourceQuotaList\":                                                            schema_k8sio_api_core_v1_ResourceQuotaList(ref), \"k8s.io/api/core/v1.ResourceQuotaSpec\":                                                            schema_k8sio_api_core_v1_ResourceQuotaSpec(ref), \"k8s.io/api/core/v1.ResourceQuotaStatus\":                                                          schema_k8sio_api_core_v1_ResourceQuotaStatus(ref), \"k8s.io/api/core/v1.ResourceRequirements\":                                                         schema_k8sio_api_core_v1_ResourceRequirements(ref), \"k8s.io/api/core/v1.SELinuxOptions\":                                                               schema_k8sio_api_core_v1_SELinuxOptions(ref), \"k8s.io/api/core/v1.ScaleIOPersistentVolumeSource\":                                                schema_k8sio_api_core_v1_ScaleIOPersistentVolumeSource(ref), \"k8s.io/api/core/v1.ScaleIOVolumeSource\":                                                          schema_k8sio_api_core_v1_ScaleIOVolumeSource(ref), \"k8s.io/api/core/v1.ScopeSelector\":                                                                schema_k8sio_api_core_v1_ScopeSelector(ref), \"k8s.io/api/core/v1.ScopedResourceSelectorRequirement\":                                            schema_k8sio_api_core_v1_ScopedResourceSelectorRequirement(ref), \"k8s.io/api/core/v1.SeccompProfile\":                                                               schema_k8sio_api_core_v1_SeccompProfile(ref), \"k8s.io/api/core/v1.Secret\":                                                                       schema_k8sio_api_core_v1_Secret(ref), \"k8s.io/api/core/v1.SecretEnvSource\":                                                              schema_k8sio_api_core_v1_SecretEnvSource(ref), \"k8s.io/api/core/v1.SecretKeySelector\":                                                            schema_k8sio_api_core_v1_SecretKeySelector(ref), \"k8s.io/api/core/v1.SecretList\":                                                                   schema_k8sio_api_core_v1_SecretList(ref), \"k8s.io/api/core/v1.SecretProjection\":                                                             schema_k8sio_api_core_v1_SecretProjection(ref), \"k8s.io/api/core/v1.SecretReference\":                                                              schema_k8sio_api_core_v1_SecretReference(ref), \"k8s.io/api/core/v1.SecretVolumeSource\":                                                           schema_k8sio_api_core_v1_SecretVolumeSource(ref), \"k8s.io/api/core/v1.SecurityContext\":                                                              schema_k8sio_api_core_v1_SecurityContext(ref), \"k8s.io/api/core/v1.SerializedReference\":                                                          schema_k8sio_api_core_v1_SerializedReference(ref), \"k8s.io/api/core/v1.Service\":                                                                      schema_k8sio_api_core_v1_Service(ref), \"k8s.io/api/core/v1.ServiceAccount\":                                                               schema_k8sio_api_core_v1_ServiceAccount(ref), \"k8s.io/api/core/v1.ServiceAccountList\":                                                           schema_k8sio_api_core_v1_ServiceAccountList(ref), \"k8s.io/api/core/v1.ServiceAccountTokenProjection\":                                                schema_k8sio_api_core_v1_ServiceAccountTokenProjection(ref), \"k8s.io/api/core/v1.ServiceList\":                                                                  schema_k8sio_api_core_v1_ServiceList(ref), \"k8s.io/api/core/v1.ServicePort\":                                                                  schema_k8sio_api_core_v1_ServicePort(ref), \"k8s.io/api/core/v1.ServiceProxyOptions\":                                                          schema_k8sio_api_core_v1_ServiceProxyOptions(ref), \"k8s.io/api/core/v1.ServiceSpec\":                                                                  schema_k8sio_api_core_v1_ServiceSpec(ref), \"k8s.io/api/core/v1.ServiceStatus\":                                                                schema_k8sio_api_core_v1_ServiceStatus(ref), \"k8s.io/api/core/v1.SessionAffinityConfig\":                                                        schema_k8sio_api_core_v1_SessionAffinityConfig(ref), \"k8s.io/api/core/v1.StorageOSPersistentVolumeSource\":                                              schema_k8sio_api_core_v1_StorageOSPersistentVolumeSource(ref), \"k8s.io/api/core/v1.StorageOSVolumeSource\":                                                        schema_k8sio_api_core_v1_StorageOSVolumeSource(ref), \"k8s.io/api/core/v1.Sysctl\":                                                                       schema_k8sio_api_core_v1_Sysctl(ref), \"k8s.io/api/core/v1.TCPSocketAction\":                                                              schema_k8sio_api_core_v1_TCPSocketAction(ref), \"k8s.io/api/core/v1.Taint\":                                                                        schema_k8sio_api_core_v1_Taint(ref), \"k8s.io/api/core/v1.Toleration\":                                                                   schema_k8sio_api_core_v1_Toleration(ref), \"k8s.io/api/core/v1.TopologySelectorLabelRequirement\":                                             schema_k8sio_api_core_v1_TopologySelectorLabelRequirement(ref), \"k8s.io/api/core/v1.TopologySelectorTerm\":                                                         schema_k8sio_api_core_v1_TopologySelectorTerm(ref), \"k8s.io/api/core/v1.TopologySpreadConstraint\":                                                     schema_k8sio_api_core_v1_TopologySpreadConstraint(ref), \"k8s.io/api/core/v1.TypedLocalObjectReference\":                                                    schema_k8sio_api_core_v1_TypedLocalObjectReference(ref), \"k8s.io/api/core/v1.Volume\":                                                                       schema_k8sio_api_core_v1_Volume(ref), \"k8s.io/api/core/v1.VolumeDevice\":                                                                 schema_k8sio_api_core_v1_VolumeDevice(ref), \"k8s.io/api/core/v1.VolumeMount\":                                                                  schema_k8sio_api_core_v1_VolumeMount(ref), \"k8s.io/api/core/v1.VolumeNodeAffinity\":                                                           schema_k8sio_api_core_v1_VolumeNodeAffinity(ref), \"k8s.io/api/core/v1.VolumeProjection\":                                                             schema_k8sio_api_core_v1_VolumeProjection(ref), \"k8s.io/api/core/v1.VolumeSource\":                                                                 schema_k8sio_api_core_v1_VolumeSource(ref), \"k8s.io/api/core/v1.VsphereVirtualDiskVolumeSource\":                                               schema_k8sio_api_core_v1_VsphereVirtualDiskVolumeSource(ref), \"k8s.io/api/core/v1.WeightedPodAffinityTerm\":                                                      schema_k8sio_api_core_v1_WeightedPodAffinityTerm(ref), \"k8s.io/api/core/v1.WindowsSecurityContextOptions\":                                                schema_k8sio_api_core_v1_WindowsSecurityContextOptions(ref), \"k8s.io/api/discovery/v1.Endpoint\":                                                                schema_k8sio_api_discovery_v1_Endpoint(ref), \"k8s.io/api/discovery/v1.EndpointConditions\":                                                      schema_k8sio_api_discovery_v1_EndpointConditions(ref), \"k8s.io/api/discovery/v1.EndpointHints\":                                                           schema_k8sio_api_discovery_v1_EndpointHints(ref), \"k8s.io/api/discovery/v1.EndpointPort\":                                                            schema_k8sio_api_discovery_v1_EndpointPort(ref), \"k8s.io/api/discovery/v1.EndpointSlice\":                                                           schema_k8sio_api_discovery_v1_EndpointSlice(ref), \"k8s.io/api/discovery/v1.EndpointSliceList\":                                                       schema_k8sio_api_discovery_v1_EndpointSliceList(ref), \"k8s.io/api/discovery/v1.ForZone\":                                                                 schema_k8sio_api_discovery_v1_ForZone(ref), \"k8s.io/api/discovery/v1beta1.Endpoint\":                                                           schema_k8sio_api_discovery_v1beta1_Endpoint(ref), \"k8s.io/api/discovery/v1beta1.EndpointConditions\":                                                 schema_k8sio_api_discovery_v1beta1_EndpointConditions(ref), \"k8s.io/api/discovery/v1beta1.EndpointHints\":                                                      schema_k8sio_api_discovery_v1beta1_EndpointHints(ref), \"k8s.io/api/discovery/v1beta1.EndpointPort\":                                                       schema_k8sio_api_discovery_v1beta1_EndpointPort(ref), \"k8s.io/api/discovery/v1beta1.EndpointSlice\":                                                      schema_k8sio_api_discovery_v1beta1_EndpointSlice(ref), \"k8s.io/api/discovery/v1beta1.EndpointSliceList\":                                                  schema_k8sio_api_discovery_v1beta1_EndpointSliceList(ref), \"k8s.io/api/discovery/v1beta1.ForZone\":                                                            schema_k8sio_api_discovery_v1beta1_ForZone(ref), \"k8s.io/api/events/v1.Event\":                                                                      schema_k8sio_api_events_v1_Event(ref), \"k8s.io/api/events/v1.EventList\":                                                                  schema_k8sio_api_events_v1_EventList(ref), \"k8s.io/api/events/v1.EventSeries\":                                                                schema_k8sio_api_events_v1_EventSeries(ref), \"k8s.io/api/events/v1beta1.Event\":                                                                 schema_k8sio_api_events_v1beta1_Event(ref), \"k8s.io/api/events/v1beta1.EventList\":                                                             schema_k8sio_api_events_v1beta1_EventList(ref), \"k8s.io/api/events/v1beta1.EventSeries\":                                                           schema_k8sio_api_events_v1beta1_EventSeries(ref), \"k8s.io/api/extensions/v1beta1.AllowedCSIDriver\":                                                  schema_k8sio_api_extensions_v1beta1_AllowedCSIDriver(ref), \"k8s.io/api/extensions/v1beta1.AllowedFlexVolume\":                                                 schema_k8sio_api_extensions_v1beta1_AllowedFlexVolume(ref), \"k8s.io/api/extensions/v1beta1.AllowedHostPath\":                                                   schema_k8sio_api_extensions_v1beta1_AllowedHostPath(ref), \"k8s.io/api/extensions/v1beta1.DaemonSet\":                                                         schema_k8sio_api_extensions_v1beta1_DaemonSet(ref), \"k8s.io/api/extensions/v1beta1.DaemonSetCondition\":                                                schema_k8sio_api_extensions_v1beta1_DaemonSetCondition(ref), \"k8s.io/api/extensions/v1beta1.DaemonSetList\":                                                     schema_k8sio_api_extensions_v1beta1_DaemonSetList(ref), \"k8s.io/api/extensions/v1beta1.DaemonSetSpec\":                                                     schema_k8sio_api_extensions_v1beta1_DaemonSetSpec(ref), \"k8s.io/api/extensions/v1beta1.DaemonSetStatus\":                                                   schema_k8sio_api_extensions_v1beta1_DaemonSetStatus(ref), \"k8s.io/api/extensions/v1beta1.DaemonSetUpdateStrategy\":                                           schema_k8sio_api_extensions_v1beta1_DaemonSetUpdateStrategy(ref), \"k8s.io/api/extensions/v1beta1.Deployment\":                                                        schema_k8sio_api_extensions_v1beta1_Deployment(ref), \"k8s.io/api/extensions/v1beta1.DeploymentCondition\":                                               schema_k8sio_api_extensions_v1beta1_DeploymentCondition(ref), \"k8s.io/api/extensions/v1beta1.DeploymentList\":                                                    schema_k8sio_api_extensions_v1beta1_DeploymentList(ref), \"k8s.io/api/extensions/v1beta1.DeploymentRollback\":                                                schema_k8sio_api_extensions_v1beta1_DeploymentRollback(ref), \"k8s.io/api/extensions/v1beta1.DeploymentSpec\":                                                    schema_k8sio_api_extensions_v1beta1_DeploymentSpec(ref), \"k8s.io/api/extensions/v1beta1.DeploymentStatus\":                                                  schema_k8sio_api_extensions_v1beta1_DeploymentStatus(ref), \"k8s.io/api/extensions/v1beta1.DeploymentStrategy\":                                                schema_k8sio_api_extensions_v1beta1_DeploymentStrategy(ref), \"k8s.io/api/extensions/v1beta1.FSGroupStrategyOptions\":                                            schema_k8sio_api_extensions_v1beta1_FSGroupStrategyOptions(ref), \"k8s.io/api/extensions/v1beta1.HTTPIngressPath\":                                                   schema_k8sio_api_extensions_v1beta1_HTTPIngressPath(ref), \"k8s.io/api/extensions/v1beta1.HTTPIngressRuleValue\":                                              schema_k8sio_api_extensions_v1beta1_HTTPIngressRuleValue(ref), \"k8s.io/api/extensions/v1beta1.HostPortRange\":                                                     schema_k8sio_api_extensions_v1beta1_HostPortRange(ref), \"k8s.io/api/extensions/v1beta1.IDRange\":                                                           schema_k8sio_api_extensions_v1beta1_IDRange(ref), \"k8s.io/api/extensions/v1beta1.IPBlock\":                                                           schema_k8sio_api_extensions_v1beta1_IPBlock(ref), \"k8s.io/api/extensions/v1beta1.Ingress\":                                                           schema_k8sio_api_extensions_v1beta1_Ingress(ref), \"k8s.io/api/extensions/v1beta1.IngressBackend\":                                                    schema_k8sio_api_extensions_v1beta1_IngressBackend(ref), \"k8s.io/api/extensions/v1beta1.IngressList\":                                                       schema_k8sio_api_extensions_v1beta1_IngressList(ref), \"k8s.io/api/extensions/v1beta1.IngressRule\":                                                       schema_k8sio_api_extensions_v1beta1_IngressRule(ref), \"k8s.io/api/extensions/v1beta1.IngressRuleValue\":                                                  schema_k8sio_api_extensions_v1beta1_IngressRuleValue(ref), \"k8s.io/api/extensions/v1beta1.IngressSpec\":                                                       schema_k8sio_api_extensions_v1beta1_IngressSpec(ref), \"k8s.io/api/extensions/v1beta1.IngressStatus\":                                                     schema_k8sio_api_extensions_v1beta1_IngressStatus(ref), \"k8s.io/api/extensions/v1beta1.IngressTLS\":                                                        schema_k8sio_api_extensions_v1beta1_IngressTLS(ref), \"k8s.io/api/extensions/v1beta1.NetworkPolicy\":                                                     schema_k8sio_api_extensions_v1beta1_NetworkPolicy(ref), \"k8s.io/api/extensions/v1beta1.NetworkPolicyEgressRule\":                                           schema_k8sio_api_extensions_v1beta1_NetworkPolicyEgressRule(ref), \"k8s.io/api/extensions/v1beta1.NetworkPolicyIngressRule\":                                          schema_k8sio_api_extensions_v1beta1_NetworkPolicyIngressRule(ref), \"k8s.io/api/extensions/v1beta1.NetworkPolicyList\":                                                 schema_k8sio_api_extensions_v1beta1_NetworkPolicyList(ref), \"k8s.io/api/extensions/v1beta1.NetworkPolicyPeer\":                                                 schema_k8sio_api_extensions_v1beta1_NetworkPolicyPeer(ref), \"k8s.io/api/extensions/v1beta1.NetworkPolicyPort\":                                                 schema_k8sio_api_extensions_v1beta1_NetworkPolicyPort(ref), \"k8s.io/api/extensions/v1beta1.NetworkPolicySpec\":                                                 schema_k8sio_api_extensions_v1beta1_NetworkPolicySpec(ref), \"k8s.io/api/extensions/v1beta1.PodSecurityPolicy\":                                                 schema_k8sio_api_extensions_v1beta1_PodSecurityPolicy(ref), \"k8s.io/api/extensions/v1beta1.PodSecurityPolicyList\":                                             schema_k8sio_api_extensions_v1beta1_PodSecurityPolicyList(ref), \"k8s.io/api/extensions/v1beta1.PodSecurityPolicySpec\":                                             schema_k8sio_api_extensions_v1beta1_PodSecurityPolicySpec(ref), \"k8s.io/api/extensions/v1beta1.ReplicaSet\":                                                        schema_k8sio_api_extensions_v1beta1_ReplicaSet(ref), \"k8s.io/api/extensions/v1beta1.ReplicaSetCondition\":                                               schema_k8sio_api_extensions_v1beta1_ReplicaSetCondition(ref), \"k8s.io/api/extensions/v1beta1.ReplicaSetList\":                                                    schema_k8sio_api_extensions_v1beta1_ReplicaSetList(ref), \"k8s.io/api/extensions/v1beta1.ReplicaSetSpec\":                                                    schema_k8sio_api_extensions_v1beta1_ReplicaSetSpec(ref), \"k8s.io/api/extensions/v1beta1.ReplicaSetStatus\":                                                  schema_k8sio_api_extensions_v1beta1_ReplicaSetStatus(ref), \"k8s.io/api/extensions/v1beta1.RollbackConfig\":                                                    schema_k8sio_api_extensions_v1beta1_RollbackConfig(ref), \"k8s.io/api/extensions/v1beta1.RollingUpdateDaemonSet\":                                            schema_k8sio_api_extensions_v1beta1_RollingUpdateDaemonSet(ref), \"k8s.io/api/extensions/v1beta1.RollingUpdateDeployment\":                                           schema_k8sio_api_extensions_v1beta1_RollingUpdateDeployment(ref), \"k8s.io/api/extensions/v1beta1.RunAsGroupStrategyOptions\":                                         schema_k8sio_api_extensions_v1beta1_RunAsGroupStrategyOptions(ref), \"k8s.io/api/extensions/v1beta1.RunAsUserStrategyOptions\":                                          schema_k8sio_api_extensions_v1beta1_RunAsUserStrategyOptions(ref), \"k8s.io/api/extensions/v1beta1.RuntimeClassStrategyOptions\":                                       schema_k8sio_api_extensions_v1beta1_RuntimeClassStrategyOptions(ref), \"k8s.io/api/extensions/v1beta1.SELinuxStrategyOptions\":                                            schema_k8sio_api_extensions_v1beta1_SELinuxStrategyOptions(ref), \"k8s.io/api/extensions/v1beta1.Scale\":                                                             schema_k8sio_api_extensions_v1beta1_Scale(ref), \"k8s.io/api/extensions/v1beta1.ScaleSpec\":                                                         schema_k8sio_api_extensions_v1beta1_ScaleSpec(ref), \"k8s.io/api/extensions/v1beta1.ScaleStatus\":                                                       schema_k8sio_api_extensions_v1beta1_ScaleStatus(ref), \"k8s.io/api/extensions/v1beta1.SupplementalGroupsStrategyOptions\":                                 schema_k8sio_api_extensions_v1beta1_SupplementalGroupsStrategyOptions(ref), \"k8s.io/api/flowcontrol/v1alpha1.FlowDistinguisherMethod\":                                         schema_k8sio_api_flowcontrol_v1alpha1_FlowDistinguisherMethod(ref), \"k8s.io/api/flowcontrol/v1alpha1.FlowSchema\":                                                      schema_k8sio_api_flowcontrol_v1alpha1_FlowSchema(ref), \"k8s.io/api/flowcontrol/v1alpha1.FlowSchemaCondition\":                                             schema_k8sio_api_flowcontrol_v1alpha1_FlowSchemaCondition(ref), \"k8s.io/api/flowcontrol/v1alpha1.FlowSchemaList\":                                                  schema_k8sio_api_flowcontrol_v1alpha1_FlowSchemaList(ref), \"k8s.io/api/flowcontrol/v1alpha1.FlowSchemaSpec\":                                                  schema_k8sio_api_flowcontrol_v1alpha1_FlowSchemaSpec(ref), \"k8s.io/api/flowcontrol/v1alpha1.FlowSchemaStatus\":                                                schema_k8sio_api_flowcontrol_v1alpha1_FlowSchemaStatus(ref), \"k8s.io/api/flowcontrol/v1alpha1.GroupSubject\":                                                    schema_k8sio_api_flowcontrol_v1alpha1_GroupSubject(ref), \"k8s.io/api/flowcontrol/v1alpha1.LimitResponse\":                                                   schema_k8sio_api_flowcontrol_v1alpha1_LimitResponse(ref), \"k8s.io/api/flowcontrol/v1alpha1.LimitedPriorityLevelConfiguration\":                               schema_k8sio_api_flowcontrol_v1alpha1_LimitedPriorityLevelConfiguration(ref), \"k8s.io/api/flowcontrol/v1alpha1.NonResourcePolicyRule\":                                           schema_k8sio_api_flowcontrol_v1alpha1_NonResourcePolicyRule(ref), \"k8s.io/api/flowcontrol/v1alpha1.PolicyRulesWithSubjects\":                                         schema_k8sio_api_flowcontrol_v1alpha1_PolicyRulesWithSubjects(ref), \"k8s.io/api/flowcontrol/v1alpha1.PriorityLevelConfiguration\":                                      schema_k8sio_api_flowcontrol_v1alpha1_PriorityLevelConfiguration(ref), \"k8s.io/api/flowcontrol/v1alpha1.PriorityLevelConfigurationCondition\":                             schema_k8sio_api_flowcontrol_v1alpha1_PriorityLevelConfigurationCondition(ref), \"k8s.io/api/flowcontrol/v1alpha1.PriorityLevelConfigurationList\":                                  schema_k8sio_api_flowcontrol_v1alpha1_PriorityLevelConfigurationList(ref), \"k8s.io/api/flowcontrol/v1alpha1.PriorityLevelConfigurationReference\":                             schema_k8sio_api_flowcontrol_v1alpha1_PriorityLevelConfigurationReference(ref), \"k8s.io/api/flowcontrol/v1alpha1.PriorityLevelConfigurationSpec\":                                  schema_k8sio_api_flowcontrol_v1alpha1_PriorityLevelConfigurationSpec(ref), \"k8s.io/api/flowcontrol/v1alpha1.PriorityLevelConfigurationStatus\":                                schema_k8sio_api_flowcontrol_v1alpha1_PriorityLevelConfigurationStatus(ref), \"k8s.io/api/flowcontrol/v1alpha1.QueuingConfiguration\":                                            schema_k8sio_api_flowcontrol_v1alpha1_QueuingConfiguration(ref), \"k8s.io/api/flowcontrol/v1alpha1.ResourcePolicyRule\":                                              schema_k8sio_api_flowcontrol_v1alpha1_ResourcePolicyRule(ref), \"k8s.io/api/flowcontrol/v1alpha1.ServiceAccountSubject\":                                           schema_k8sio_api_flowcontrol_v1alpha1_ServiceAccountSubject(ref), \"k8s.io/api/flowcontrol/v1alpha1.Subject\":                                                         schema_k8sio_api_flowcontrol_v1alpha1_Subject(ref), \"k8s.io/api/flowcontrol/v1alpha1.UserSubject\":                                                     schema_k8sio_api_flowcontrol_v1alpha1_UserSubject(ref), \"k8s.io/api/flowcontrol/v1beta1.FlowDistinguisherMethod\":                                          schema_k8sio_api_flowcontrol_v1beta1_FlowDistinguisherMethod(ref), \"k8s.io/api/flowcontrol/v1beta1.FlowSchema\":                                                       schema_k8sio_api_flowcontrol_v1beta1_FlowSchema(ref), \"k8s.io/api/flowcontrol/v1beta1.FlowSchemaCondition\":                                              schema_k8sio_api_flowcontrol_v1beta1_FlowSchemaCondition(ref), \"k8s.io/api/flowcontrol/v1beta1.FlowSchemaList\":                                                   schema_k8sio_api_flowcontrol_v1beta1_FlowSchemaList(ref), \"k8s.io/api/flowcontrol/v1beta1.FlowSchemaSpec\":                                                   schema_k8sio_api_flowcontrol_v1beta1_FlowSchemaSpec(ref), \"k8s.io/api/flowcontrol/v1beta1.FlowSchemaStatus\":                                                 schema_k8sio_api_flowcontrol_v1beta1_FlowSchemaStatus(ref), \"k8s.io/api/flowcontrol/v1beta1.GroupSubject\":                                                     schema_k8sio_api_flowcontrol_v1beta1_GroupSubject(ref), \"k8s.io/api/flowcontrol/v1beta1.LimitResponse\":                                                    schema_k8sio_api_flowcontrol_v1beta1_LimitResponse(ref), \"k8s.io/api/flowcontrol/v1beta1.LimitedPriorityLevelConfiguration\":                                schema_k8sio_api_flowcontrol_v1beta1_LimitedPriorityLevelConfiguration(ref), \"k8s.io/api/flowcontrol/v1beta1.NonResourcePolicyRule\":                                            schema_k8sio_api_flowcontrol_v1beta1_NonResourcePolicyRule(ref), \"k8s.io/api/flowcontrol/v1beta1.PolicyRulesWithSubjects\":                                          schema_k8sio_api_flowcontrol_v1beta1_PolicyRulesWithSubjects(ref), \"k8s.io/api/flowcontrol/v1beta1.PriorityLevelConfiguration\":                                       schema_k8sio_api_flowcontrol_v1beta1_PriorityLevelConfiguration(ref), \"k8s.io/api/flowcontrol/v1beta1.PriorityLevelConfigurationCondition\":                              schema_k8sio_api_flowcontrol_v1beta1_PriorityLevelConfigurationCondition(ref), \"k8s.io/api/flowcontrol/v1beta1.PriorityLevelConfigurationList\":                                   schema_k8sio_api_flowcontrol_v1beta1_PriorityLevelConfigurationList(ref), \"k8s.io/api/flowcontrol/v1beta1.PriorityLevelConfigurationReference\":                              schema_k8sio_api_flowcontrol_v1beta1_PriorityLevelConfigurationReference(ref), \"k8s.io/api/flowcontrol/v1beta1.PriorityLevelConfigurationSpec\":                                   schema_k8sio_api_flowcontrol_v1beta1_PriorityLevelConfigurationSpec(ref), \"k8s.io/api/flowcontrol/v1beta1.PriorityLevelConfigurationStatus\":                                 schema_k8sio_api_flowcontrol_v1beta1_PriorityLevelConfigurationStatus(ref), \"k8s.io/api/flowcontrol/v1beta1.QueuingConfiguration\":                                             schema_k8sio_api_flowcontrol_v1beta1_QueuingConfiguration(ref), \"k8s.io/api/flowcontrol/v1beta1.ResourcePolicyRule\":                                               schema_k8sio_api_flowcontrol_v1beta1_ResourcePolicyRule(ref), \"k8s.io/api/flowcontrol/v1beta1.ServiceAccountSubject\":                                            schema_k8sio_api_flowcontrol_v1beta1_ServiceAccountSubject(ref), \"k8s.io/api/flowcontrol/v1beta1.Subject\":                                                          schema_k8sio_api_flowcontrol_v1beta1_Subject(ref), \"k8s.io/api/flowcontrol/v1beta1.UserSubject\":                                                      schema_k8sio_api_flowcontrol_v1beta1_UserSubject(ref), \"k8s.io/api/flowcontrol/v1beta2.FlowDistinguisherMethod\":                                          schema_k8sio_api_flowcontrol_v1beta2_FlowDistinguisherMethod(ref), \"k8s.io/api/flowcontrol/v1beta2.FlowSchema\":                                                       schema_k8sio_api_flowcontrol_v1beta2_FlowSchema(ref), \"k8s.io/api/flowcontrol/v1beta2.FlowSchemaCondition\":                                              schema_k8sio_api_flowcontrol_v1beta2_FlowSchemaCondition(ref), \"k8s.io/api/flowcontrol/v1beta2.FlowSchemaList\":                                                   schema_k8sio_api_flowcontrol_v1beta2_FlowSchemaList(ref), \"k8s.io/api/flowcontrol/v1beta2.FlowSchemaSpec\":                                                   schema_k8sio_api_flowcontrol_v1beta2_FlowSchemaSpec(ref), \"k8s.io/api/flowcontrol/v1beta2.FlowSchemaStatus\":                                                 schema_k8sio_api_flowcontrol_v1beta2_FlowSchemaStatus(ref), \"k8s.io/api/flowcontrol/v1beta2.GroupSubject\":                                                     schema_k8sio_api_flowcontrol_v1beta2_GroupSubject(ref), \"k8s.io/api/flowcontrol/v1beta2.LimitResponse\":                                                    schema_k8sio_api_flowcontrol_v1beta2_LimitResponse(ref), \"k8s.io/api/flowcontrol/v1beta2.LimitedPriorityLevelConfiguration\":                                schema_k8sio_api_flowcontrol_v1beta2_LimitedPriorityLevelConfiguration(ref), \"k8s.io/api/flowcontrol/v1beta2.NonResourcePolicyRule\":                                            schema_k8sio_api_flowcontrol_v1beta2_NonResourcePolicyRule(ref), \"k8s.io/api/flowcontrol/v1beta2.PolicyRulesWithSubjects\":                                          schema_k8sio_api_flowcontrol_v1beta2_PolicyRulesWithSubjects(ref), \"k8s.io/api/flowcontrol/v1beta2.PriorityLevelConfiguration\":                                       schema_k8sio_api_flowcontrol_v1beta2_PriorityLevelConfiguration(ref), \"k8s.io/api/flowcontrol/v1beta2.PriorityLevelConfigurationCondition\":                              schema_k8sio_api_flowcontrol_v1beta2_PriorityLevelConfigurationCondition(ref), \"k8s.io/api/flowcontrol/v1beta2.PriorityLevelConfigurationList\":                                   schema_k8sio_api_flowcontrol_v1beta2_PriorityLevelConfigurationList(ref), \"k8s.io/api/flowcontrol/v1beta2.PriorityLevelConfigurationReference\":                              schema_k8sio_api_flowcontrol_v1beta2_PriorityLevelConfigurationReference(ref), \"k8s.io/api/flowcontrol/v1beta2.PriorityLevelConfigurationSpec\":                                   schema_k8sio_api_flowcontrol_v1beta2_PriorityLevelConfigurationSpec(ref), \"k8s.io/api/flowcontrol/v1beta2.PriorityLevelConfigurationStatus\":                                 schema_k8sio_api_flowcontrol_v1beta2_PriorityLevelConfigurationStatus(ref), \"k8s.io/api/flowcontrol/v1beta2.QueuingConfiguration\":                                             schema_k8sio_api_flowcontrol_v1beta2_QueuingConfiguration(ref), \"k8s.io/api/flowcontrol/v1beta2.ResourcePolicyRule\":                                               schema_k8sio_api_flowcontrol_v1beta2_ResourcePolicyRule(ref), \"k8s.io/api/flowcontrol/v1beta2.ServiceAccountSubject\":                                            schema_k8sio_api_flowcontrol_v1beta2_ServiceAccountSubject(ref), \"k8s.io/api/flowcontrol/v1beta2.Subject\":                                                          schema_k8sio_api_flowcontrol_v1beta2_Subject(ref), \"k8s.io/api/flowcontrol/v1beta2.UserSubject\":                                                      schema_k8sio_api_flowcontrol_v1beta2_UserSubject(ref), \"k8s.io/api/imagepolicy/v1alpha1.ImageReview\":                                                     schema_k8sio_api_imagepolicy_v1alpha1_ImageReview(ref), \"k8s.io/api/imagepolicy/v1alpha1.ImageReviewContainerSpec\":                                        schema_k8sio_api_imagepolicy_v1alpha1_ImageReviewContainerSpec(ref), \"k8s.io/api/imagepolicy/v1alpha1.ImageReviewSpec\":                                                 schema_k8sio_api_imagepolicy_v1alpha1_ImageReviewSpec(ref), \"k8s.io/api/imagepolicy/v1alpha1.ImageReviewStatus\":                                               schema_k8sio_api_imagepolicy_v1alpha1_ImageReviewStatus(ref), \"k8s.io/api/networking/v1.HTTPIngressPath\":                                                        schema_k8sio_api_networking_v1_HTTPIngressPath(ref), \"k8s.io/api/networking/v1.HTTPIngressRuleValue\":                                                   schema_k8sio_api_networking_v1_HTTPIngressRuleValue(ref), \"k8s.io/api/networking/v1.IPBlock\":                                                                schema_k8sio_api_networking_v1_IPBlock(ref), \"k8s.io/api/networking/v1.Ingress\":                                                                schema_k8sio_api_networking_v1_Ingress(ref), \"k8s.io/api/networking/v1.IngressBackend\":                                                         schema_k8sio_api_networking_v1_IngressBackend(ref), \"k8s.io/api/networking/v1.IngressClass\":                                                           schema_k8sio_api_networking_v1_IngressClass(ref), \"k8s.io/api/networking/v1.IngressClassList\":                                                       schema_k8sio_api_networking_v1_IngressClassList(ref), \"k8s.io/api/networking/v1.IngressClassParametersReference\":                                        schema_k8sio_api_networking_v1_IngressClassParametersReference(ref), \"k8s.io/api/networking/v1.IngressClassSpec\":                                                       schema_k8sio_api_networking_v1_IngressClassSpec(ref), \"k8s.io/api/networking/v1.IngressList\":                                                            schema_k8sio_api_networking_v1_IngressList(ref), \"k8s.io/api/networking/v1.IngressRule\":                                                            schema_k8sio_api_networking_v1_IngressRule(ref), \"k8s.io/api/networking/v1.IngressRuleValue\":                                                       schema_k8sio_api_networking_v1_IngressRuleValue(ref), \"k8s.io/api/networking/v1.IngressServiceBackend\":                                                  schema_k8sio_api_networking_v1_IngressServiceBackend(ref), \"k8s.io/api/networking/v1.IngressSpec\":                                                            schema_k8sio_api_networking_v1_IngressSpec(ref), \"k8s.io/api/networking/v1.IngressStatus\":                                                          schema_k8sio_api_networking_v1_IngressStatus(ref), \"k8s.io/api/networking/v1.IngressTLS\":                                                             schema_k8sio_api_networking_v1_IngressTLS(ref), \"k8s.io/api/networking/v1.NetworkPolicy\":                                                          schema_k8sio_api_networking_v1_NetworkPolicy(ref), \"k8s.io/api/networking/v1.NetworkPolicyEgressRule\":                                                schema_k8sio_api_networking_v1_NetworkPolicyEgressRule(ref), \"k8s.io/api/networking/v1.NetworkPolicyIngressRule\":                                               schema_k8sio_api_networking_v1_NetworkPolicyIngressRule(ref), \"k8s.io/api/networking/v1.NetworkPolicyList\":                                                      schema_k8sio_api_networking_v1_NetworkPolicyList(ref), \"k8s.io/api/networking/v1.NetworkPolicyPeer\":                                                      schema_k8sio_api_networking_v1_NetworkPolicyPeer(ref), \"k8s.io/api/networking/v1.NetworkPolicyPort\":                                                      schema_k8sio_api_networking_v1_NetworkPolicyPort(ref), \"k8s.io/api/networking/v1.NetworkPolicySpec\":                                                      schema_k8sio_api_networking_v1_NetworkPolicySpec(ref), \"k8s.io/api/networking/v1.ServiceBackendPort\":                                                     schema_k8sio_api_networking_v1_ServiceBackendPort(ref), \"k8s.io/api/networking/v1beta1.HTTPIngressPath\":                                                   schema_k8sio_api_networking_v1beta1_HTTPIngressPath(ref), \"k8s.io/api/networking/v1beta1.HTTPIngressRuleValue\":                                              schema_k8sio_api_networking_v1beta1_HTTPIngressRuleValue(ref), \"k8s.io/api/networking/v1beta1.Ingress\":                                                           schema_k8sio_api_networking_v1beta1_Ingress(ref), \"k8s.io/api/networking/v1beta1.IngressBackend\":                                                    schema_k8sio_api_networking_v1beta1_IngressBackend(ref), \"k8s.io/api/networking/v1beta1.IngressClass\":                                                      schema_k8sio_api_networking_v1beta1_IngressClass(ref), \"k8s.io/api/networking/v1beta1.IngressClassList\":                                                  schema_k8sio_api_networking_v1beta1_IngressClassList(ref), \"k8s.io/api/networking/v1beta1.IngressClassParametersReference\":                                   schema_k8sio_api_networking_v1beta1_IngressClassParametersReference(ref), \"k8s.io/api/networking/v1beta1.IngressClassSpec\":                                                  schema_k8sio_api_networking_v1beta1_IngressClassSpec(ref), \"k8s.io/api/networking/v1beta1.IngressList\":                                                       schema_k8sio_api_networking_v1beta1_IngressList(ref), \"k8s.io/api/networking/v1beta1.IngressRule\":                                                       schema_k8sio_api_networking_v1beta1_IngressRule(ref), \"k8s.io/api/networking/v1beta1.IngressRuleValue\":                                                  schema_k8sio_api_networking_v1beta1_IngressRuleValue(ref), \"k8s.io/api/networking/v1beta1.IngressSpec\":                                                       schema_k8sio_api_networking_v1beta1_IngressSpec(ref), \"k8s.io/api/networking/v1beta1.IngressStatus\":                                                     schema_k8sio_api_networking_v1beta1_IngressStatus(ref), \"k8s.io/api/networking/v1beta1.IngressTLS\":                                                        schema_k8sio_api_networking_v1beta1_IngressTLS(ref), \"k8s.io/api/node/v1.Overhead\":                                                                     schema_k8sio_api_node_v1_Overhead(ref), \"k8s.io/api/node/v1.RuntimeClass\":                                                                 schema_k8sio_api_node_v1_RuntimeClass(ref), \"k8s.io/api/node/v1.RuntimeClassList\":                                                             schema_k8sio_api_node_v1_RuntimeClassList(ref), \"k8s.io/api/node/v1.Scheduling\":                                                                   schema_k8sio_api_node_v1_Scheduling(ref), \"k8s.io/api/node/v1alpha1.Overhead\":                                                               schema_k8sio_api_node_v1alpha1_Overhead(ref), \"k8s.io/api/node/v1alpha1.RuntimeClass\":                                                           schema_k8sio_api_node_v1alpha1_RuntimeClass(ref), \"k8s.io/api/node/v1alpha1.RuntimeClassList\":                                                       schema_k8sio_api_node_v1alpha1_RuntimeClassList(ref), \"k8s.io/api/node/v1alpha1.RuntimeClassSpec\":                                                       schema_k8sio_api_node_v1alpha1_RuntimeClassSpec(ref), \"k8s.io/api/node/v1alpha1.Scheduling\":                                                             schema_k8sio_api_node_v1alpha1_Scheduling(ref), \"k8s.io/api/node/v1beta1.Overhead\":                                                                schema_k8sio_api_node_v1beta1_Overhead(ref), \"k8s.io/api/node/v1beta1.RuntimeClass\":                                                            schema_k8sio_api_node_v1beta1_RuntimeClass(ref), \"k8s.io/api/node/v1beta1.RuntimeClassList\":                                                        schema_k8sio_api_node_v1beta1_RuntimeClassList(ref), \"k8s.io/api/node/v1beta1.Scheduling\":                                                              schema_k8sio_api_node_v1beta1_Scheduling(ref), \"k8s.io/api/policy/v1.Eviction\":                                                                   schema_k8sio_api_policy_v1_Eviction(ref), \"k8s.io/api/policy/v1.PodDisruptionBudget\":                                                        schema_k8sio_api_policy_v1_PodDisruptionBudget(ref), \"k8s.io/api/policy/v1.PodDisruptionBudgetList\":                                                    schema_k8sio_api_policy_v1_PodDisruptionBudgetList(ref), \"k8s.io/api/policy/v1.PodDisruptionBudgetSpec\":                                                    schema_k8sio_api_policy_v1_PodDisruptionBudgetSpec(ref), \"k8s.io/api/policy/v1.PodDisruptionBudgetStatus\":                                                  schema_k8sio_api_policy_v1_PodDisruptionBudgetStatus(ref), \"k8s.io/api/policy/v1beta1.AllowedCSIDriver\":                                                      schema_k8sio_api_policy_v1beta1_AllowedCSIDriver(ref), \"k8s.io/api/policy/v1beta1.AllowedFlexVolume\":                                                     schema_k8sio_api_policy_v1beta1_AllowedFlexVolume(ref), \"k8s.io/api/policy/v1beta1.AllowedHostPath\":                                                       schema_k8sio_api_policy_v1beta1_AllowedHostPath(ref), \"k8s.io/api/policy/v1beta1.Eviction\":                                                              schema_k8sio_api_policy_v1beta1_Eviction(ref), \"k8s.io/api/policy/v1beta1.FSGroupStrategyOptions\":                                                schema_k8sio_api_policy_v1beta1_FSGroupStrategyOptions(ref), \"k8s.io/api/policy/v1beta1.HostPortRange\":                                                         schema_k8sio_api_policy_v1beta1_HostPortRange(ref), \"k8s.io/api/policy/v1beta1.IDRange\":                                                               schema_k8sio_api_policy_v1beta1_IDRange(ref), \"k8s.io/api/policy/v1beta1.PodDisruptionBudget\":                                                   schema_k8sio_api_policy_v1beta1_PodDisruptionBudget(ref), \"k8s.io/api/policy/v1beta1.PodDisruptionBudgetList\":                                               schema_k8sio_api_policy_v1beta1_PodDisruptionBudgetList(ref), \"k8s.io/api/policy/v1beta1.PodDisruptionBudgetSpec\":                                               schema_k8sio_api_policy_v1beta1_PodDisruptionBudgetSpec(ref), \"k8s.io/api/policy/v1beta1.PodDisruptionBudgetStatus\":                                             schema_k8sio_api_policy_v1beta1_PodDisruptionBudgetStatus(ref), \"k8s.io/api/policy/v1beta1.PodSecurityPolicy\":                                                     schema_k8sio_api_policy_v1beta1_PodSecurityPolicy(ref), \"k8s.io/api/policy/v1beta1.PodSecurityPolicyList\":                                                 schema_k8sio_api_policy_v1beta1_PodSecurityPolicyList(ref), \"k8s.io/api/policy/v1beta1.PodSecurityPolicySpec\":                                                 schema_k8sio_api_policy_v1beta1_PodSecurityPolicySpec(ref), \"k8s.io/api/policy/v1beta1.RunAsGroupStrategyOptions\":                                             schema_k8sio_api_policy_v1beta1_RunAsGroupStrategyOptions(ref), \"k8s.io/api/policy/v1beta1.RunAsUserStrategyOptions\":                                              schema_k8sio_api_policy_v1beta1_RunAsUserStrategyOptions(ref), \"k8s.io/api/policy/v1beta1.RuntimeClassStrategyOptions\":                                           schema_k8sio_api_policy_v1beta1_RuntimeClassStrategyOptions(ref), \"k8s.io/api/policy/v1beta1.SELinuxStrategyOptions\":                                                schema_k8sio_api_policy_v1beta1_SELinuxStrategyOptions(ref), \"k8s.io/api/policy/v1beta1.SupplementalGroupsStrategyOptions\":                                     schema_k8sio_api_policy_v1beta1_SupplementalGroupsStrategyOptions(ref), \"k8s.io/api/rbac/v1.AggregationRule\":                                                              schema_k8sio_api_rbac_v1_AggregationRule(ref), \"k8s.io/api/rbac/v1.ClusterRole\":                                                                  schema_k8sio_api_rbac_v1_ClusterRole(ref), \"k8s.io/api/rbac/v1.ClusterRoleBinding\":                                                           schema_k8sio_api_rbac_v1_ClusterRoleBinding(ref), \"k8s.io/api/rbac/v1.ClusterRoleBindingList\":                                                       schema_k8sio_api_rbac_v1_ClusterRoleBindingList(ref), \"k8s.io/api/rbac/v1.ClusterRoleList\":                                                              schema_k8sio_api_rbac_v1_ClusterRoleList(ref), \"k8s.io/api/rbac/v1.PolicyRule\":                                                                   schema_k8sio_api_rbac_v1_PolicyRule(ref), \"k8s.io/api/rbac/v1.Role\":                                                                         schema_k8sio_api_rbac_v1_Role(ref), \"k8s.io/api/rbac/v1.RoleBinding\":                                                                  schema_k8sio_api_rbac_v1_RoleBinding(ref), \"k8s.io/api/rbac/v1.RoleBindingList\":                                                              schema_k8sio_api_rbac_v1_RoleBindingList(ref), \"k8s.io/api/rbac/v1.RoleList\":                                                                     schema_k8sio_api_rbac_v1_RoleList(ref), \"k8s.io/api/rbac/v1.RoleRef\":                                                                      schema_k8sio_api_rbac_v1_RoleRef(ref), \"k8s.io/api/rbac/v1.Subject\":                                                                      schema_k8sio_api_rbac_v1_Subject(ref), \"k8s.io/api/rbac/v1alpha1.AggregationRule\":                                                        schema_k8sio_api_rbac_v1alpha1_AggregationRule(ref), \"k8s.io/api/rbac/v1alpha1.ClusterRole\":                                                            schema_k8sio_api_rbac_v1alpha1_ClusterRole(ref), \"k8s.io/api/rbac/v1alpha1.ClusterRoleBinding\":                                                     schema_k8sio_api_rbac_v1alpha1_ClusterRoleBinding(ref), \"k8s.io/api/rbac/v1alpha1.ClusterRoleBindingList\":                                                 schema_k8sio_api_rbac_v1alpha1_ClusterRoleBindingList(ref), \"k8s.io/api/rbac/v1alpha1.ClusterRoleList\":                                                        schema_k8sio_api_rbac_v1alpha1_ClusterRoleList(ref), \"k8s.io/api/rbac/v1alpha1.PolicyRule\":                                                             schema_k8sio_api_rbac_v1alpha1_PolicyRule(ref), \"k8s.io/api/rbac/v1alpha1.Role\":                                                                   schema_k8sio_api_rbac_v1alpha1_Role(ref), \"k8s.io/api/rbac/v1alpha1.RoleBinding\":                                                            schema_k8sio_api_rbac_v1alpha1_RoleBinding(ref), \"k8s.io/api/rbac/v1alpha1.RoleBindingList\":                                                        schema_k8sio_api_rbac_v1alpha1_RoleBindingList(ref), \"k8s.io/api/rbac/v1alpha1.RoleList\":                                                               schema_k8sio_api_rbac_v1alpha1_RoleList(ref), \"k8s.io/api/rbac/v1alpha1.RoleRef\":                                                                schema_k8sio_api_rbac_v1alpha1_RoleRef(ref), \"k8s.io/api/rbac/v1alpha1.Subject\":                                                                schema_k8sio_api_rbac_v1alpha1_Subject(ref), \"k8s.io/api/rbac/v1beta1.AggregationRule\":                                                         schema_k8sio_api_rbac_v1beta1_AggregationRule(ref), \"k8s.io/api/rbac/v1beta1.ClusterRole\":                                                             schema_k8sio_api_rbac_v1beta1_ClusterRole(ref), \"k8s.io/api/rbac/v1beta1.ClusterRoleBinding\":                                                      schema_k8sio_api_rbac_v1beta1_ClusterRoleBinding(ref), \"k8s.io/api/rbac/v1beta1.ClusterRoleBindingList\":                                                  schema_k8sio_api_rbac_v1beta1_ClusterRoleBindingList(ref), \"k8s.io/api/rbac/v1beta1.ClusterRoleList\":                                                         schema_k8sio_api_rbac_v1beta1_ClusterRoleList(ref), \"k8s.io/api/rbac/v1beta1.PolicyRule\":                                                              schema_k8sio_api_rbac_v1beta1_PolicyRule(ref), \"k8s.io/api/rbac/v1beta1.Role\":                                                                    schema_k8sio_api_rbac_v1beta1_Role(ref), \"k8s.io/api/rbac/v1beta1.RoleBinding\":                                                             schema_k8sio_api_rbac_v1beta1_RoleBinding(ref), \"k8s.io/api/rbac/v1beta1.RoleBindingList\":                                                         schema_k8sio_api_rbac_v1beta1_RoleBindingList(ref), \"k8s.io/api/rbac/v1beta1.RoleList\":                                                                schema_k8sio_api_rbac_v1beta1_RoleList(ref), \"k8s.io/api/rbac/v1beta1.RoleRef\":                                                                 schema_k8sio_api_rbac_v1beta1_RoleRef(ref), \"k8s.io/api/rbac/v1beta1.Subject\":                                                                 schema_k8sio_api_rbac_v1beta1_Subject(ref), \"k8s.io/api/scheduling/v1.PriorityClass\":                                                          schema_k8sio_api_scheduling_v1_PriorityClass(ref), \"k8s.io/api/scheduling/v1.PriorityClassList\":                                                      schema_k8sio_api_scheduling_v1_PriorityClassList(ref), \"k8s.io/api/scheduling/v1alpha1.PriorityClass\":                                                    schema_k8sio_api_scheduling_v1alpha1_PriorityClass(ref), \"k8s.io/api/scheduling/v1alpha1.PriorityClassList\":                                                schema_k8sio_api_scheduling_v1alpha1_PriorityClassList(ref), \"k8s.io/api/scheduling/v1beta1.PriorityClass\":                                                     schema_k8sio_api_scheduling_v1beta1_PriorityClass(ref), \"k8s.io/api/scheduling/v1beta1.PriorityClassList\":                                                 schema_k8sio_api_scheduling_v1beta1_PriorityClassList(ref), \"k8s.io/api/storage/v1.CSIDriver\":                                                                 schema_k8sio_api_storage_v1_CSIDriver(ref), \"k8s.io/api/storage/v1.CSIDriverList\":                                                             schema_k8sio_api_storage_v1_CSIDriverList(ref), \"k8s.io/api/storage/v1.CSIDriverSpec\":                                                             schema_k8sio_api_storage_v1_CSIDriverSpec(ref), \"k8s.io/api/storage/v1.CSINode\":                                                                   schema_k8sio_api_storage_v1_CSINode(ref), \"k8s.io/api/storage/v1.CSINodeDriver\":                                                             schema_k8sio_api_storage_v1_CSINodeDriver(ref), \"k8s.io/api/storage/v1.CSINodeList\":                                                               schema_k8sio_api_storage_v1_CSINodeList(ref), \"k8s.io/api/storage/v1.CSINodeSpec\":                                                               schema_k8sio_api_storage_v1_CSINodeSpec(ref), \"k8s.io/api/storage/v1.StorageClass\":                                                              schema_k8sio_api_storage_v1_StorageClass(ref), \"k8s.io/api/storage/v1.StorageClassList\":                                                          schema_k8sio_api_storage_v1_StorageClassList(ref), \"k8s.io/api/storage/v1.TokenRequest\":                                                              schema_k8sio_api_storage_v1_TokenRequest(ref), \"k8s.io/api/storage/v1.VolumeAttachment\":                                                          schema_k8sio_api_storage_v1_VolumeAttachment(ref), \"k8s.io/api/storage/v1.VolumeAttachmentList\":                                                      schema_k8sio_api_storage_v1_VolumeAttachmentList(ref), \"k8s.io/api/storage/v1.VolumeAttachmentSource\":                                                    schema_k8sio_api_storage_v1_VolumeAttachmentSource(ref), \"k8s.io/api/storage/v1.VolumeAttachmentSpec\":                                                      schema_k8sio_api_storage_v1_VolumeAttachmentSpec(ref), \"k8s.io/api/storage/v1.VolumeAttachmentStatus\":                                                    schema_k8sio_api_storage_v1_VolumeAttachmentStatus(ref), \"k8s.io/api/storage/v1.VolumeError\":                                                               schema_k8sio_api_storage_v1_VolumeError(ref), \"k8s.io/api/storage/v1.VolumeNodeResources\":                                                       schema_k8sio_api_storage_v1_VolumeNodeResources(ref), \"k8s.io/api/storage/v1alpha1.CSIStorageCapacity\":                                                  schema_k8sio_api_storage_v1alpha1_CSIStorageCapacity(ref), \"k8s.io/api/storage/v1alpha1.CSIStorageCapacityList\":                                              schema_k8sio_api_storage_v1alpha1_CSIStorageCapacityList(ref), \"k8s.io/api/storage/v1alpha1.VolumeAttachment\":                                                    schema_k8sio_api_storage_v1alpha1_VolumeAttachment(ref), \"k8s.io/api/storage/v1alpha1.VolumeAttachmentList\":                                                schema_k8sio_api_storage_v1alpha1_VolumeAttachmentList(ref), \"k8s.io/api/storage/v1alpha1.VolumeAttachmentSource\":                                              schema_k8sio_api_storage_v1alpha1_VolumeAttachmentSource(ref), \"k8s.io/api/storage/v1alpha1.VolumeAttachmentSpec\":                                                schema_k8sio_api_storage_v1alpha1_VolumeAttachmentSpec(ref), \"k8s.io/api/storage/v1alpha1.VolumeAttachmentStatus\":                                              schema_k8sio_api_storage_v1alpha1_VolumeAttachmentStatus(ref), \"k8s.io/api/storage/v1alpha1.VolumeError\":                                                         schema_k8sio_api_storage_v1alpha1_VolumeError(ref), \"k8s.io/api/storage/v1beta1.CSIDriver\":                                                            schema_k8sio_api_storage_v1beta1_CSIDriver(ref), \"k8s.io/api/storage/v1beta1.CSIDriverList\":                                                        schema_k8sio_api_storage_v1beta1_CSIDriverList(ref), \"k8s.io/api/storage/v1beta1.CSIDriverSpec\":                                                        schema_k8sio_api_storage_v1beta1_CSIDriverSpec(ref), \"k8s.io/api/storage/v1beta1.CSINode\":                                                              schema_k8sio_api_storage_v1beta1_CSINode(ref), \"k8s.io/api/storage/v1beta1.CSINodeDriver\":                                                        schema_k8sio_api_storage_v1beta1_CSINodeDriver(ref), \"k8s.io/api/storage/v1beta1.CSINodeList\":                                                          schema_k8sio_api_storage_v1beta1_CSINodeList(ref), \"k8s.io/api/storage/v1beta1.CSINodeSpec\":                                                          schema_k8sio_api_storage_v1beta1_CSINodeSpec(ref), \"k8s.io/api/storage/v1beta1.CSIStorageCapacity\":                                                   schema_k8sio_api_storage_v1beta1_CSIStorageCapacity(ref), \"k8s.io/api/storage/v1beta1.CSIStorageCapacityList\":                                               schema_k8sio_api_storage_v1beta1_CSIStorageCapacityList(ref), \"k8s.io/api/storage/v1beta1.StorageClass\":                                                         schema_k8sio_api_storage_v1beta1_StorageClass(ref), \"k8s.io/api/storage/v1beta1.StorageClassList\":                                                     schema_k8sio_api_storage_v1beta1_StorageClassList(ref), \"k8s.io/api/storage/v1beta1.TokenRequest\":                                                         schema_k8sio_api_storage_v1beta1_TokenRequest(ref), \"k8s.io/api/storage/v1beta1.VolumeAttachment\":                                                     schema_k8sio_api_storage_v1beta1_VolumeAttachment(ref), \"k8s.io/api/storage/v1beta1.VolumeAttachmentList\":                                                 schema_k8sio_api_storage_v1beta1_VolumeAttachmentList(ref), \"k8s.io/api/storage/v1beta1.VolumeAttachmentSource\":                                               schema_k8sio_api_storage_v1beta1_VolumeAttachmentSource(ref), \"k8s.io/api/storage/v1beta1.VolumeAttachmentSpec\":                                                 schema_k8sio_api_storage_v1beta1_VolumeAttachmentSpec(ref), \"k8s.io/api/storage/v1beta1.VolumeAttachmentStatus\":                                               schema_k8sio_api_storage_v1beta1_VolumeAttachmentStatus(ref), \"k8s.io/api/storage/v1beta1.VolumeError\":                                                          schema_k8sio_api_storage_v1beta1_VolumeError(ref), \"k8s.io/api/storage/v1beta1.VolumeNodeResources\":                                                  schema_k8sio_api_storage_v1beta1_VolumeNodeResources(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.ConversionRequest\":                      schema_pkg_apis_apiextensions_v1_ConversionRequest(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.ConversionResponse\":                     schema_pkg_apis_apiextensions_v1_ConversionResponse(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.ConversionReview\":                       schema_pkg_apis_apiextensions_v1_ConversionReview(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceColumnDefinition\":         schema_pkg_apis_apiextensions_v1_CustomResourceColumnDefinition(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceConversion\":               schema_pkg_apis_apiextensions_v1_CustomResourceConversion(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinition\":               schema_pkg_apis_apiextensions_v1_CustomResourceDefinition(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinitionCondition\":      schema_pkg_apis_apiextensions_v1_CustomResourceDefinitionCondition(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinitionList\":           schema_pkg_apis_apiextensions_v1_CustomResourceDefinitionList(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinitionNames\":          schema_pkg_apis_apiextensions_v1_CustomResourceDefinitionNames(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinitionSpec\":           schema_pkg_apis_apiextensions_v1_CustomResourceDefinitionSpec(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinitionStatus\":         schema_pkg_apis_apiextensions_v1_CustomResourceDefinitionStatus(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinitionVersion\":        schema_pkg_apis_apiextensions_v1_CustomResourceDefinitionVersion(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceSubresourceScale\":         schema_pkg_apis_apiextensions_v1_CustomResourceSubresourceScale(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceSubresourceStatus\":        schema_pkg_apis_apiextensions_v1_CustomResourceSubresourceStatus(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceSubresources\":             schema_pkg_apis_apiextensions_v1_CustomResourceSubresources(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceValidation\":               schema_pkg_apis_apiextensions_v1_CustomResourceValidation(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.ExternalDocumentation\":                  schema_pkg_apis_apiextensions_v1_ExternalDocumentation(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSON\":                                   schema_pkg_apis_apiextensions_v1_JSON(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaProps\":                        schema_pkg_apis_apiextensions_v1_JSONSchemaProps(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaPropsOrArray\":                 schema_pkg_apis_apiextensions_v1_JSONSchemaPropsOrArray(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaPropsOrBool\":                  schema_pkg_apis_apiextensions_v1_JSONSchemaPropsOrBool(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaPropsOrStringArray\":           schema_pkg_apis_apiextensions_v1_JSONSchemaPropsOrStringArray(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.ServiceReference\":                       schema_pkg_apis_apiextensions_v1_ServiceReference(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.ValidationRule\":                         schema_pkg_apis_apiextensions_v1_ValidationRule(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.WebhookClientConfig\":                    schema_pkg_apis_apiextensions_v1_WebhookClientConfig(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.WebhookConversion\":                      schema_pkg_apis_apiextensions_v1_WebhookConversion(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.ConversionRequest\":                 schema_pkg_apis_apiextensions_v1beta1_ConversionRequest(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.ConversionResponse\":                schema_pkg_apis_apiextensions_v1beta1_ConversionResponse(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.ConversionReview\":                  schema_pkg_apis_apiextensions_v1beta1_ConversionReview(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceColumnDefinition\":    schema_pkg_apis_apiextensions_v1beta1_CustomResourceColumnDefinition(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceConversion\":          schema_pkg_apis_apiextensions_v1beta1_CustomResourceConversion(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinition\":          schema_pkg_apis_apiextensions_v1beta1_CustomResourceDefinition(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinitionCondition\": schema_pkg_apis_apiextensions_v1beta1_CustomResourceDefinitionCondition(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinitionList\":      schema_pkg_apis_apiextensions_v1beta1_CustomResourceDefinitionList(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinitionNames\":     schema_pkg_apis_apiextensions_v1beta1_CustomResourceDefinitionNames(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinitionSpec\":      schema_pkg_apis_apiextensions_v1beta1_CustomResourceDefinitionSpec(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinitionStatus\":    schema_pkg_apis_apiextensions_v1beta1_CustomResourceDefinitionStatus(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinitionVersion\":   schema_pkg_apis_apiextensions_v1beta1_CustomResourceDefinitionVersion(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceSubresourceScale\":    schema_pkg_apis_apiextensions_v1beta1_CustomResourceSubresourceScale(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceSubresourceStatus\":   schema_pkg_apis_apiextensions_v1beta1_CustomResourceSubresourceStatus(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceSubresources\":        schema_pkg_apis_apiextensions_v1beta1_CustomResourceSubresources(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceValidation\":          schema_pkg_apis_apiextensions_v1beta1_CustomResourceValidation(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.ExternalDocumentation\":             schema_pkg_apis_apiextensions_v1beta1_ExternalDocumentation(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSON\":                              schema_pkg_apis_apiextensions_v1beta1_JSON(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaProps\":                   schema_pkg_apis_apiextensions_v1beta1_JSONSchemaProps(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaPropsOrArray\":            schema_pkg_apis_apiextensions_v1beta1_JSONSchemaPropsOrArray(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaPropsOrBool\":             schema_pkg_apis_apiextensions_v1beta1_JSONSchemaPropsOrBool(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaPropsOrStringArray\":      schema_pkg_apis_apiextensions_v1beta1_JSONSchemaPropsOrStringArray(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.ServiceReference\":                  schema_pkg_apis_apiextensions_v1beta1_ServiceReference(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.ValidationRule\":                    schema_pkg_apis_apiextensions_v1beta1_ValidationRule(ref), \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.WebhookClientConfig\":               schema_pkg_apis_apiextensions_v1beta1_WebhookClientConfig(ref), \"k8s.io/apimachinery/pkg/api/resource.Quantity\":                                                   schema_apimachinery_pkg_api_resource_Quantity(ref), \"k8s.io/apimachinery/pkg/api/resource.int64Amount\":                                                schema_apimachinery_pkg_api_resource_int64Amount(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.APIGroup\":                                                   schema_pkg_apis_meta_v1_APIGroup(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.APIGroupList\":                                               schema_pkg_apis_meta_v1_APIGroupList(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.APIResource\":                                                schema_pkg_apis_meta_v1_APIResource(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.APIResourceList\":                                            schema_pkg_apis_meta_v1_APIResourceList(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.APIVersions\":                                                schema_pkg_apis_meta_v1_APIVersions(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.ApplyOptions\":                                               schema_pkg_apis_meta_v1_ApplyOptions(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.Condition\":                                                  schema_pkg_apis_meta_v1_Condition(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.CreateOptions\":                                              schema_pkg_apis_meta_v1_CreateOptions(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.DeleteOptions\":                                              schema_pkg_apis_meta_v1_DeleteOptions(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\":                                                   schema_pkg_apis_meta_v1_Duration(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.FieldsV1\":                                                   schema_pkg_apis_meta_v1_FieldsV1(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.GetOptions\":                                                 schema_pkg_apis_meta_v1_GetOptions(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.GroupKind\":                                                  schema_pkg_apis_meta_v1_GroupKind(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.GroupResource\":                                              schema_pkg_apis_meta_v1_GroupResource(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.GroupVersion\":                                               schema_pkg_apis_meta_v1_GroupVersion(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.GroupVersionForDiscovery\":                                   schema_pkg_apis_meta_v1_GroupVersionForDiscovery(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.GroupVersionKind\":                                           schema_pkg_apis_meta_v1_GroupVersionKind(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.GroupVersionResource\":                                       schema_pkg_apis_meta_v1_GroupVersionResource(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.InternalEvent\":                                              schema_pkg_apis_meta_v1_InternalEvent(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\":                                              schema_pkg_apis_meta_v1_LabelSelector(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelectorRequirement\":                                   schema_pkg_apis_meta_v1_LabelSelectorRequirement(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.List\":                                                       schema_pkg_apis_meta_v1_List(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\":                                                   schema_pkg_apis_meta_v1_ListMeta(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.ListOptions\":                                                schema_pkg_apis_meta_v1_ListOptions(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.ManagedFieldsEntry\":                                         schema_pkg_apis_meta_v1_ManagedFieldsEntry(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\":                                                  schema_pkg_apis_meta_v1_MicroTime(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\":                                                 schema_pkg_apis_meta_v1_ObjectMeta(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.OwnerReference\":                                             schema_pkg_apis_meta_v1_OwnerReference(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.PartialObjectMetadata\":                                      schema_pkg_apis_meta_v1_PartialObjectMetadata(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.PartialObjectMetadataList\":                                  schema_pkg_apis_meta_v1_PartialObjectMetadataList(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.Patch\":                                                      schema_pkg_apis_meta_v1_Patch(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.PatchOptions\":                                               schema_pkg_apis_meta_v1_PatchOptions(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.Preconditions\":                                              schema_pkg_apis_meta_v1_Preconditions(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.RootPaths\":                                                  schema_pkg_apis_meta_v1_RootPaths(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.ServerAddressByClientCIDR\":                                  schema_pkg_apis_meta_v1_ServerAddressByClientCIDR(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.Status\":                                                     schema_pkg_apis_meta_v1_Status(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.StatusCause\":                                                schema_pkg_apis_meta_v1_StatusCause(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.StatusDetails\":                                              schema_pkg_apis_meta_v1_StatusDetails(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.Table\":                                                      schema_pkg_apis_meta_v1_Table(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.TableColumnDefinition\":                                      schema_pkg_apis_meta_v1_TableColumnDefinition(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.TableOptions\":                                               schema_pkg_apis_meta_v1_TableOptions(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.TableRow\":                                                   schema_pkg_apis_meta_v1_TableRow(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.TableRowCondition\":                                          schema_pkg_apis_meta_v1_TableRowCondition(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\":                                                       schema_pkg_apis_meta_v1_Time(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.Timestamp\":                                                  schema_pkg_apis_meta_v1_Timestamp(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.TypeMeta\":                                                   schema_pkg_apis_meta_v1_TypeMeta(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.UpdateOptions\":                                              schema_pkg_apis_meta_v1_UpdateOptions(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1.WatchEvent\":                                                 schema_pkg_apis_meta_v1_WatchEvent(ref), \"k8s.io/apimachinery/pkg/apis/meta/v1beta1.PartialObjectMetadataList\":                             schema_pkg_apis_meta_v1beta1_PartialObjectMetadataList(ref), \"k8s.io/apimachinery/pkg/runtime.RawExtension\":                                                    schema_k8sio_apimachinery_pkg_runtime_RawExtension(ref), \"k8s.io/apimachinery/pkg/runtime.TypeMeta\":                                                        schema_k8sio_apimachinery_pkg_runtime_TypeMeta(ref), \"k8s.io/apimachinery/pkg/runtime.Unknown\":                                                         schema_k8sio_apimachinery_pkg_runtime_Unknown(ref), \"k8s.io/apimachinery/pkg/util/intstr.IntOrString\":                                                 schema_apimachinery_pkg_util_intstr_IntOrString(ref), \"k8s.io/apimachinery/pkg/version.Info\":                                                            schema_k8sio_apimachinery_pkg_version_Info(ref), \"k8s.io/apiserver/pkg/apis/audit/v1.Event\":                                                        schema_pkg_apis_audit_v1_Event(ref), \"k8s.io/apiserver/pkg/apis/audit/v1.EventList\":                                                    schema_pkg_apis_audit_v1_EventList(ref), \"k8s.io/apiserver/pkg/apis/audit/v1.GroupResources\":                                               schema_pkg_apis_audit_v1_GroupResources(ref), \"k8s.io/apiserver/pkg/apis/audit/v1.ObjectReference\":                                              schema_pkg_apis_audit_v1_ObjectReference(ref), \"k8s.io/apiserver/pkg/apis/audit/v1.Policy\":                                                       schema_pkg_apis_audit_v1_Policy(ref), \"k8s.io/apiserver/pkg/apis/audit/v1.PolicyList\":                                                   schema_pkg_apis_audit_v1_PolicyList(ref), \"k8s.io/apiserver/pkg/apis/audit/v1.PolicyRule\":                                                   schema_pkg_apis_audit_v1_PolicyRule(ref), \"k8s.io/apiserver/pkg/apis/audit/v1alpha1.Event\":                                                  schema_pkg_apis_audit_v1alpha1_Event(ref), \"k8s.io/apiserver/pkg/apis/audit/v1alpha1.EventList\":                                              schema_pkg_apis_audit_v1alpha1_EventList(ref), \"k8s.io/apiserver/pkg/apis/audit/v1alpha1.GroupResources\":                                         schema_pkg_apis_audit_v1alpha1_GroupResources(ref), \"k8s.io/apiserver/pkg/apis/audit/v1alpha1.ObjectReference\":                                        schema_pkg_apis_audit_v1alpha1_ObjectReference(ref), \"k8s.io/apiserver/pkg/apis/audit/v1alpha1.Policy\":                                                 schema_pkg_apis_audit_v1alpha1_Policy(ref), \"k8s.io/apiserver/pkg/apis/audit/v1alpha1.PolicyList\":                                             schema_pkg_apis_audit_v1alpha1_PolicyList(ref), \"k8s.io/apiserver/pkg/apis/audit/v1alpha1.PolicyRule\":                                             schema_pkg_apis_audit_v1alpha1_PolicyRule(ref), \"k8s.io/apiserver/pkg/apis/audit/v1beta1.Event\":                                                   schema_pkg_apis_audit_v1beta1_Event(ref), \"k8s.io/apiserver/pkg/apis/audit/v1beta1.EventList\":                                               schema_pkg_apis_audit_v1beta1_EventList(ref), \"k8s.io/apiserver/pkg/apis/audit/v1beta1.GroupResources\":                                          schema_pkg_apis_audit_v1beta1_GroupResources(ref), \"k8s.io/apiserver/pkg/apis/audit/v1beta1.ObjectReference\":                                         schema_pkg_apis_audit_v1beta1_ObjectReference(ref), \"k8s.io/apiserver/pkg/apis/audit/v1beta1.Policy\":                                                  schema_pkg_apis_audit_v1beta1_Policy(ref), \"k8s.io/apiserver/pkg/apis/audit/v1beta1.PolicyList\":                                              schema_pkg_apis_audit_v1beta1_PolicyList(ref), \"k8s.io/apiserver/pkg/apis/audit/v1beta1.PolicyRule\":                                              schema_pkg_apis_audit_v1beta1_PolicyRule(ref), \"k8s.io/client-go/pkg/apis/clientauthentication/v1.Cluster\":                                       schema_pkg_apis_clientauthentication_v1_Cluster(ref), \"k8s.io/client-go/pkg/apis/clientauthentication/v1.ExecCredential\":                                schema_pkg_apis_clientauthentication_v1_ExecCredential(ref), \"k8s.io/client-go/pkg/apis/clientauthentication/v1.ExecCredentialSpec\":                            schema_pkg_apis_clientauthentication_v1_ExecCredentialSpec(ref), \"k8s.io/client-go/pkg/apis/clientauthentication/v1.ExecCredentialStatus\":                          schema_pkg_apis_clientauthentication_v1_ExecCredentialStatus(ref), \"k8s.io/client-go/pkg/apis/clientauthentication/v1alpha1.ExecCredential\":                          schema_pkg_apis_clientauthentication_v1alpha1_ExecCredential(ref), \"k8s.io/client-go/pkg/apis/clientauthentication/v1alpha1.ExecCredentialSpec\":                      schema_pkg_apis_clientauthentication_v1alpha1_ExecCredentialSpec(ref), \"k8s.io/client-go/pkg/apis/clientauthentication/v1alpha1.ExecCredentialStatus\":                    schema_pkg_apis_clientauthentication_v1alpha1_ExecCredentialStatus(ref), \"k8s.io/client-go/pkg/apis/clientauthentication/v1alpha1.Response\":                                schema_pkg_apis_clientauthentication_v1alpha1_Response(ref), \"k8s.io/client-go/pkg/apis/clientauthentication/v1beta1.Cluster\":                                  schema_pkg_apis_clientauthentication_v1beta1_Cluster(ref), \"k8s.io/client-go/pkg/apis/clientauthentication/v1beta1.ExecCredential\":                           schema_pkg_apis_clientauthentication_v1beta1_ExecCredential(ref), \"k8s.io/client-go/pkg/apis/clientauthentication/v1beta1.ExecCredentialSpec\":                       schema_pkg_apis_clientauthentication_v1beta1_ExecCredentialSpec(ref), \"k8s.io/client-go/pkg/apis/clientauthentication/v1beta1.ExecCredentialStatus\":                     schema_pkg_apis_clientauthentication_v1beta1_ExecCredentialStatus(ref), \"k8s.io/cloud-provider/config/v1alpha1.CloudControllerManagerConfiguration\":                       schema_k8sio_cloud_provider_config_v1alpha1_CloudControllerManagerConfiguration(ref), \"k8s.io/cloud-provider/config/v1alpha1.CloudProviderConfiguration\":                                schema_k8sio_cloud_provider_config_v1alpha1_CloudProviderConfiguration(ref), \"k8s.io/cloud-provider/config/v1alpha1.KubeCloudSharedConfiguration\":                              schema_k8sio_cloud_provider_config_v1alpha1_KubeCloudSharedConfiguration(ref), \"k8s.io/controller-manager/config/v1alpha1.ControllerLeaderConfiguration\":                         schema_k8sio_controller_manager_config_v1alpha1_ControllerLeaderConfiguration(ref), \"k8s.io/controller-manager/config/v1alpha1.GenericControllerManagerConfiguration\":                 schema_k8sio_controller_manager_config_v1alpha1_GenericControllerManagerConfiguration(ref), \"k8s.io/controller-manager/config/v1alpha1.LeaderMigrationConfiguration\":                          schema_k8sio_controller_manager_config_v1alpha1_LeaderMigrationConfiguration(ref), \"k8s.io/controller-manager/config/v1beta1.ControllerLeaderConfiguration\":                          schema_k8sio_controller_manager_config_v1beta1_ControllerLeaderConfiguration(ref), \"k8s.io/controller-manager/config/v1beta1.LeaderMigrationConfiguration\":                           schema_k8sio_controller_manager_config_v1beta1_LeaderMigrationConfiguration(ref), \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1.APIService\":                                   schema_pkg_apis_apiregistration_v1_APIService(ref), \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1.APIServiceCondition\":                          schema_pkg_apis_apiregistration_v1_APIServiceCondition(ref), \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1.APIServiceList\":                               schema_pkg_apis_apiregistration_v1_APIServiceList(ref), \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1.APIServiceSpec\":                               schema_pkg_apis_apiregistration_v1_APIServiceSpec(ref), \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1.APIServiceStatus\":                             schema_pkg_apis_apiregistration_v1_APIServiceStatus(ref), \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1.ServiceReference\":                             schema_pkg_apis_apiregistration_v1_ServiceReference(ref), \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1beta1.APIService\":                              schema_pkg_apis_apiregistration_v1beta1_APIService(ref), \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1beta1.APIServiceCondition\":                     schema_pkg_apis_apiregistration_v1beta1_APIServiceCondition(ref), \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1beta1.APIServiceList\":                          schema_pkg_apis_apiregistration_v1beta1_APIServiceList(ref), \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1beta1.APIServiceSpec\":                          schema_pkg_apis_apiregistration_v1beta1_APIServiceSpec(ref), \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1beta1.APIServiceStatus\":                        schema_pkg_apis_apiregistration_v1beta1_APIServiceStatus(ref), \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1beta1.ServiceReference\":                        schema_pkg_apis_apiregistration_v1beta1_ServiceReference(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.AttachDetachControllerConfiguration\":              schema_k8sio_kube_controller_manager_config_v1alpha1_AttachDetachControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.CSRSigningConfiguration\":                          schema_k8sio_kube_controller_manager_config_v1alpha1_CSRSigningConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.CSRSigningControllerConfiguration\":                schema_k8sio_kube_controller_manager_config_v1alpha1_CSRSigningControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.CronJobControllerConfiguration\":                   schema_k8sio_kube_controller_manager_config_v1alpha1_CronJobControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.DaemonSetControllerConfiguration\":                 schema_k8sio_kube_controller_manager_config_v1alpha1_DaemonSetControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.DeploymentControllerConfiguration\":                schema_k8sio_kube_controller_manager_config_v1alpha1_DeploymentControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.DeprecatedControllerConfiguration\":                schema_k8sio_kube_controller_manager_config_v1alpha1_DeprecatedControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.EndpointControllerConfiguration\":                  schema_k8sio_kube_controller_manager_config_v1alpha1_EndpointControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.EndpointSliceControllerConfiguration\":             schema_k8sio_kube_controller_manager_config_v1alpha1_EndpointSliceControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.EndpointSliceMirroringControllerConfiguration\":    schema_k8sio_kube_controller_manager_config_v1alpha1_EndpointSliceMirroringControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.EphemeralVolumeControllerConfiguration\":           schema_k8sio_kube_controller_manager_config_v1alpha1_EphemeralVolumeControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.GarbageCollectorControllerConfiguration\":          schema_k8sio_kube_controller_manager_config_v1alpha1_GarbageCollectorControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.GroupResource\":                                    schema_k8sio_kube_controller_manager_config_v1alpha1_GroupResource(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.HPAControllerConfiguration\":                       schema_k8sio_kube_controller_manager_config_v1alpha1_HPAControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.JobControllerConfiguration\":                       schema_k8sio_kube_controller_manager_config_v1alpha1_JobControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.KubeControllerManagerConfiguration\":               schema_k8sio_kube_controller_manager_config_v1alpha1_KubeControllerManagerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.NamespaceControllerConfiguration\":                 schema_k8sio_kube_controller_manager_config_v1alpha1_NamespaceControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.NodeIPAMControllerConfiguration\":                  schema_k8sio_kube_controller_manager_config_v1alpha1_NodeIPAMControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.NodeLifecycleControllerConfiguration\":             schema_k8sio_kube_controller_manager_config_v1alpha1_NodeLifecycleControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.PersistentVolumeBinderControllerConfiguration\":    schema_k8sio_kube_controller_manager_config_v1alpha1_PersistentVolumeBinderControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.PersistentVolumeRecyclerConfiguration\":            schema_k8sio_kube_controller_manager_config_v1alpha1_PersistentVolumeRecyclerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.PodGCControllerConfiguration\":                     schema_k8sio_kube_controller_manager_config_v1alpha1_PodGCControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.ReplicaSetControllerConfiguration\":                schema_k8sio_kube_controller_manager_config_v1alpha1_ReplicaSetControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.ReplicationControllerConfiguration\":               schema_k8sio_kube_controller_manager_config_v1alpha1_ReplicationControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.ResourceQuotaControllerConfiguration\":             schema_k8sio_kube_controller_manager_config_v1alpha1_ResourceQuotaControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.SAControllerConfiguration\":                        schema_k8sio_kube_controller_manager_config_v1alpha1_SAControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.StatefulSetControllerConfiguration\":               schema_k8sio_kube_controller_manager_config_v1alpha1_StatefulSetControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.TTLAfterFinishedControllerConfiguration\":          schema_k8sio_kube_controller_manager_config_v1alpha1_TTLAfterFinishedControllerConfiguration(ref), \"k8s.io/kube-controller-manager/config/v1alpha1.VolumeConfiguration\":                              schema_k8sio_kube_controller_manager_config_v1alpha1_VolumeConfiguration(ref), \"k8s.io/kube-proxy/config/v1alpha1.KubeProxyConfiguration\":                                        schema_k8sio_kube_proxy_config_v1alpha1_KubeProxyConfiguration(ref), \"k8s.io/kube-proxy/config/v1alpha1.KubeProxyConntrackConfiguration\":                               schema_k8sio_kube_proxy_config_v1alpha1_KubeProxyConntrackConfiguration(ref), \"k8s.io/kube-proxy/config/v1alpha1.KubeProxyIPTablesConfiguration\":                                schema_k8sio_kube_proxy_config_v1alpha1_KubeProxyIPTablesConfiguration(ref), \"k8s.io/kube-proxy/config/v1alpha1.KubeProxyIPVSConfiguration\":                                    schema_k8sio_kube_proxy_config_v1alpha1_KubeProxyIPVSConfiguration(ref), \"k8s.io/kube-proxy/config/v1alpha1.KubeProxyWinkernelConfiguration\":                               schema_k8sio_kube_proxy_config_v1alpha1_KubeProxyWinkernelConfiguration(ref), \"k8s.io/kube-scheduler/config/v1beta2.DefaultPreemptionArgs\":                                      schema_k8sio_kube_scheduler_config_v1beta2_DefaultPreemptionArgs(ref), \"k8s.io/kube-scheduler/config/v1beta2.Extender\":                                                   schema_k8sio_kube_scheduler_config_v1beta2_Extender(ref), \"k8s.io/kube-scheduler/config/v1beta2.ExtenderManagedResource\":                                    schema_k8sio_kube_scheduler_config_v1beta2_ExtenderManagedResource(ref), \"k8s.io/kube-scheduler/config/v1beta2.ExtenderTLSConfig\":                                          schema_k8sio_kube_scheduler_config_v1beta2_ExtenderTLSConfig(ref), \"k8s.io/kube-scheduler/config/v1beta2.InterPodAffinityArgs\":                                       schema_k8sio_kube_scheduler_config_v1beta2_InterPodAffinityArgs(ref), \"k8s.io/kube-scheduler/config/v1beta2.KubeSchedulerConfiguration\":                                 schema_k8sio_kube_scheduler_config_v1beta2_KubeSchedulerConfiguration(ref), \"k8s.io/kube-scheduler/config/v1beta2.KubeSchedulerProfile\":                                       schema_k8sio_kube_scheduler_config_v1beta2_KubeSchedulerProfile(ref), \"k8s.io/kube-scheduler/config/v1beta2.NodeAffinityArgs\":                                           schema_k8sio_kube_scheduler_config_v1beta2_NodeAffinityArgs(ref), \"k8s.io/kube-scheduler/config/v1beta2.NodeResourcesBalancedAllocationArgs\":                        schema_k8sio_kube_scheduler_config_v1beta2_NodeResourcesBalancedAllocationArgs(ref), \"k8s.io/kube-scheduler/config/v1beta2.NodeResourcesFitArgs\":                                       schema_k8sio_kube_scheduler_config_v1beta2_NodeResourcesFitArgs(ref), \"k8s.io/kube-scheduler/config/v1beta2.Plugin\":                                                     schema_k8sio_kube_scheduler_config_v1beta2_Plugin(ref), \"k8s.io/kube-scheduler/config/v1beta2.PluginConfig\":                                               schema_k8sio_kube_scheduler_config_v1beta2_PluginConfig(ref), \"k8s.io/kube-scheduler/config/v1beta2.PluginSet\":                                                  schema_k8sio_kube_scheduler_config_v1beta2_PluginSet(ref), \"k8s.io/kube-scheduler/config/v1beta2.Plugins\":                                                    schema_k8sio_kube_scheduler_config_v1beta2_Plugins(ref), \"k8s.io/kube-scheduler/config/v1beta2.PodTopologySpreadArgs\":                                      schema_k8sio_kube_scheduler_config_v1beta2_PodTopologySpreadArgs(ref), \"k8s.io/kube-scheduler/config/v1beta2.RequestedToCapacityRatioParam\":                              schema_k8sio_kube_scheduler_config_v1beta2_RequestedToCapacityRatioParam(ref), \"k8s.io/kube-scheduler/config/v1beta2.ResourceSpec\":                                               schema_k8sio_kube_scheduler_config_v1beta2_ResourceSpec(ref), \"k8s.io/kube-scheduler/config/v1beta2.ScoringStrategy\":                                            schema_k8sio_kube_scheduler_config_v1beta2_ScoringStrategy(ref), \"k8s.io/kube-scheduler/config/v1beta2.UtilizationShapePoint\":                                      schema_k8sio_kube_scheduler_config_v1beta2_UtilizationShapePoint(ref), \"k8s.io/kube-scheduler/config/v1beta2.VolumeBindingArgs\":                                          schema_k8sio_kube_scheduler_config_v1beta2_VolumeBindingArgs(ref), \"k8s.io/kube-scheduler/config/v1beta3.DefaultPreemptionArgs\":                                      schema_k8sio_kube_scheduler_config_v1beta3_DefaultPreemptionArgs(ref), \"k8s.io/kube-scheduler/config/v1beta3.Extender\":                                                   schema_k8sio_kube_scheduler_config_v1beta3_Extender(ref), \"k8s.io/kube-scheduler/config/v1beta3.ExtenderManagedResource\":                                    schema_k8sio_kube_scheduler_config_v1beta3_ExtenderManagedResource(ref), \"k8s.io/kube-scheduler/config/v1beta3.ExtenderTLSConfig\":                                          schema_k8sio_kube_scheduler_config_v1beta3_ExtenderTLSConfig(ref), \"k8s.io/kube-scheduler/config/v1beta3.InterPodAffinityArgs\":                                       schema_k8sio_kube_scheduler_config_v1beta3_InterPodAffinityArgs(ref), \"k8s.io/kube-scheduler/config/v1beta3.KubeSchedulerConfiguration\":                                 schema_k8sio_kube_scheduler_config_v1beta3_KubeSchedulerConfiguration(ref), \"k8s.io/kube-scheduler/config/v1beta3.KubeSchedulerProfile\":                                       schema_k8sio_kube_scheduler_config_v1beta3_KubeSchedulerProfile(ref), \"k8s.io/kube-scheduler/config/v1beta3.NodeAffinityArgs\":                                           schema_k8sio_kube_scheduler_config_v1beta3_NodeAffinityArgs(ref), \"k8s.io/kube-scheduler/config/v1beta3.NodeResourcesBalancedAllocationArgs\":                        schema_k8sio_kube_scheduler_config_v1beta3_NodeResourcesBalancedAllocationArgs(ref), \"k8s.io/kube-scheduler/config/v1beta3.NodeResourcesFitArgs\":                                       schema_k8sio_kube_scheduler_config_v1beta3_NodeResourcesFitArgs(ref), \"k8s.io/kube-scheduler/config/v1beta3.Plugin\":                                                     schema_k8sio_kube_scheduler_config_v1beta3_Plugin(ref), \"k8s.io/kube-scheduler/config/v1beta3.PluginConfig\":                                               schema_k8sio_kube_scheduler_config_v1beta3_PluginConfig(ref), \"k8s.io/kube-scheduler/config/v1beta3.PluginSet\":                                                  schema_k8sio_kube_scheduler_config_v1beta3_PluginSet(ref), \"k8s.io/kube-scheduler/config/v1beta3.Plugins\":                                                    schema_k8sio_kube_scheduler_config_v1beta3_Plugins(ref), \"k8s.io/kube-scheduler/config/v1beta3.PodTopologySpreadArgs\":                                      schema_k8sio_kube_scheduler_config_v1beta3_PodTopologySpreadArgs(ref), \"k8s.io/kube-scheduler/config/v1beta3.RequestedToCapacityRatioParam\":                              schema_k8sio_kube_scheduler_config_v1beta3_RequestedToCapacityRatioParam(ref), \"k8s.io/kube-scheduler/config/v1beta3.ResourceSpec\":                                               schema_k8sio_kube_scheduler_config_v1beta3_ResourceSpec(ref), \"k8s.io/kube-scheduler/config/v1beta3.ScoringStrategy\":                                            schema_k8sio_kube_scheduler_config_v1beta3_ScoringStrategy(ref), \"k8s.io/kube-scheduler/config/v1beta3.UtilizationShapePoint\":                                      schema_k8sio_kube_scheduler_config_v1beta3_UtilizationShapePoint(ref), \"k8s.io/kube-scheduler/config/v1beta3.VolumeBindingArgs\":                                          schema_k8sio_kube_scheduler_config_v1beta3_VolumeBindingArgs(ref), \"k8s.io/kubelet/config/v1alpha1.CredentialProvider\":                                               schema_k8sio_kubelet_config_v1alpha1_CredentialProvider(ref), \"k8s.io/kubelet/config/v1alpha1.CredentialProviderConfig\":                                         schema_k8sio_kubelet_config_v1alpha1_CredentialProviderConfig(ref), \"k8s.io/kubelet/config/v1alpha1.ExecEnvVar\":                                                       schema_k8sio_kubelet_config_v1alpha1_ExecEnvVar(ref), \"k8s.io/kubelet/config/v1beta1.KubeletAnonymousAuthentication\":                                    schema_k8sio_kubelet_config_v1beta1_KubeletAnonymousAuthentication(ref), \"k8s.io/kubelet/config/v1beta1.KubeletAuthentication\":                                             schema_k8sio_kubelet_config_v1beta1_KubeletAuthentication(ref), \"k8s.io/kubelet/config/v1beta1.KubeletAuthorization\":                                              schema_k8sio_kubelet_config_v1beta1_KubeletAuthorization(ref), \"k8s.io/kubelet/config/v1beta1.KubeletConfiguration\":                                              schema_k8sio_kubelet_config_v1beta1_KubeletConfiguration(ref), \"k8s.io/kubelet/config/v1beta1.KubeletWebhookAuthentication\":                                      schema_k8sio_kubelet_config_v1beta1_KubeletWebhookAuthentication(ref), \"k8s.io/kubelet/config/v1beta1.KubeletWebhookAuthorization\":                                       schema_k8sio_kubelet_config_v1beta1_KubeletWebhookAuthorization(ref), \"k8s.io/kubelet/config/v1beta1.KubeletX509Authentication\":                                         schema_k8sio_kubelet_config_v1beta1_KubeletX509Authentication(ref), \"k8s.io/kubelet/config/v1beta1.MemoryReservation\":                                                 schema_k8sio_kubelet_config_v1beta1_MemoryReservation(ref), \"k8s.io/kubelet/config/v1beta1.MemorySwapConfiguration\":                                           schema_k8sio_kubelet_config_v1beta1_MemorySwapConfiguration(ref), \"k8s.io/kubelet/config/v1beta1.SerializedNodeConfigSource\":                                        schema_k8sio_kubelet_config_v1beta1_SerializedNodeConfigSource(ref), \"k8s.io/kubelet/config/v1beta1.ShutdownGracePeriodByPodPriority\":                                  schema_k8sio_kubelet_config_v1beta1_ShutdownGracePeriodByPodPriority(ref), \"k8s.io/kubernetes/pkg/apis/abac/v1beta1.Policy\":                                                  schema_pkg_apis_abac_v1beta1_Policy(ref), \"k8s.io/kubernetes/pkg/apis/abac/v1beta1.PolicySpec\":                                              schema_pkg_apis_abac_v1beta1_PolicySpec(ref), \"k8s.io/metrics/pkg/apis/custom_metrics/v1beta1.MetricListOptions\":                                schema_pkg_apis_custom_metrics_v1beta1_MetricListOptions(ref), \"k8s.io/metrics/pkg/apis/custom_metrics/v1beta1.MetricValue\":                                      schema_pkg_apis_custom_metrics_v1beta1_MetricValue(ref), \"k8s.io/metrics/pkg/apis/custom_metrics/v1beta1.MetricValueList\":                                  schema_pkg_apis_custom_metrics_v1beta1_MetricValueList(ref), \"k8s.io/metrics/pkg/apis/custom_metrics/v1beta2.MetricIdentifier\":                                 schema_pkg_apis_custom_metrics_v1beta2_MetricIdentifier(ref), \"k8s.io/metrics/pkg/apis/custom_metrics/v1beta2.MetricListOptions\":                                schema_pkg_apis_custom_metrics_v1beta2_MetricListOptions(ref), \"k8s.io/metrics/pkg/apis/custom_metrics/v1beta2.MetricValue\":                                      schema_pkg_apis_custom_metrics_v1beta2_MetricValue(ref), \"k8s.io/metrics/pkg/apis/custom_metrics/v1beta2.MetricValueList\":                                  schema_pkg_apis_custom_metrics_v1beta2_MetricValueList(ref), \"k8s.io/metrics/pkg/apis/external_metrics/v1beta1.ExternalMetricValue\":                            schema_pkg_apis_external_metrics_v1beta1_ExternalMetricValue(ref), \"k8s.io/metrics/pkg/apis/external_metrics/v1beta1.ExternalMetricValueList\":                        schema_pkg_apis_external_metrics_v1beta1_ExternalMetricValueList(ref), \"k8s.io/metrics/pkg/apis/metrics/v1alpha1.ContainerMetrics\":                                       schema_pkg_apis_metrics_v1alpha1_ContainerMetrics(ref), \"k8s.io/metrics/pkg/apis/metrics/v1alpha1.NodeMetrics\":                                            schema_pkg_apis_metrics_v1alpha1_NodeMetrics(ref), \"k8s.io/metrics/pkg/apis/metrics/v1alpha1.NodeMetricsList\":                                        schema_pkg_apis_metrics_v1alpha1_NodeMetricsList(ref), \"k8s.io/metrics/pkg/apis/metrics/v1alpha1.PodMetrics\":                                             schema_pkg_apis_metrics_v1alpha1_PodMetrics(ref), \"k8s.io/metrics/pkg/apis/metrics/v1alpha1.PodMetricsList\":                                         schema_pkg_apis_metrics_v1alpha1_PodMetricsList(ref), \"k8s.io/metrics/pkg/apis/metrics/v1beta1.ContainerMetrics\":                                        schema_pkg_apis_metrics_v1beta1_ContainerMetrics(ref), \"k8s.io/metrics/pkg/apis/metrics/v1beta1.NodeMetrics\":                                             schema_pkg_apis_metrics_v1beta1_NodeMetrics(ref), \"k8s.io/metrics/pkg/apis/metrics/v1beta1.NodeMetricsList\":                                         schema_pkg_apis_metrics_v1beta1_NodeMetricsList(ref), \"k8s.io/metrics/pkg/apis/metrics/v1beta1.PodMetrics\":                                              schema_pkg_apis_metrics_v1beta1_PodMetrics(ref), \"k8s.io/metrics/pkg/apis/metrics/v1beta1.PodMetricsList\":                                          schema_pkg_apis_metrics_v1beta1_PodMetricsList(ref), } } func schema_k8sio_api_admissionregistration_v1_MutatingWebhook(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MutatingWebhook describes an admission webhook and the resources and operations it applies to.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"The name of the admission webhook. Name should be fully qualified, e.g., imagepolicy.kubernetes.io, where \"imagepolicy\" is the name of the webhook, and kubernetes.io is the name of the organization. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"clientConfig\": { SchemaProps: spec.SchemaProps{ Description: \"ClientConfig defines how to communicate with the hook. Required\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/admissionregistration/v1.WebhookClientConfig\"), }, }, \"rules\": { SchemaProps: spec.SchemaProps{ Description: \"Rules describes what operations on what resources/subresources the webhook cares about. The webhook cares about an operation if it matches _any_ Rule. However, in order to prevent ValidatingAdmissionWebhooks and MutatingAdmissionWebhooks from putting the cluster in a state which cannot be recovered from without completely disabling the plugin, ValidatingAdmissionWebhooks and MutatingAdmissionWebhooks are never called on admission requests for ValidatingWebhookConfiguration and MutatingWebhookConfiguration objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/admissionregistration/v1.RuleWithOperations\"), }, }, }, }, }, \"failurePolicy\": { SchemaProps: spec.SchemaProps{ Description: \"FailurePolicy defines how unrecognized errors from the admission endpoint are handled - allowed values are Ignore or Fail. Defaults to Fail.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"matchPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"matchPolicy defines how the \"rules\" list is used to match incoming requests. Allowed values are \"Exact\" or \"Equivalent\".nn- Exact: match a request only if it exactly matches a specified rule. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, but \"rules\" only included `apiGroups:[\"apps\"], apiVersions:[\"v1\"], resources: [\"deployments\"]`, a request to apps/v1beta1 or extensions/v1beta1 would not be sent to the webhook.nn- Equivalent: match a request if modifies a resource listed in rules, even via another API group or version. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, and \"rules\" only included `apiGroups:[\"apps\"], apiVersions:[\"v1\"], resources: [\"deployments\"]`, a request to apps/v1beta1 or extensions/v1beta1 would be converted to apps/v1 and sent to the webhook.nnDefaults to \"Equivalent\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"namespaceSelector\": { SchemaProps: spec.SchemaProps{ Description: \"NamespaceSelector decides whether to run the webhook on an object based on whether the namespace for that object matches the selector. If the object itself is a namespace, the matching is performed on object.metadata.labels. If the object is another cluster scoped resource, it never skips the webhook.nnFor example, to run the webhook on any objects whose namespace is not associated with \"runlevel\" of \"0\" or \"1\";  you will set the selector as follows: \"namespaceSelector\": {n  \"matchExpressions\": [n    {n      \"key\": \"runlevel\",n      \"operator\": \"NotIn\",n      \"values\": [n        \"0\",n        \"1\"n      ]n    }n  ]n}nnIf instead you want to only run the webhook on any objects whose namespace is associated with the \"environment\" of \"prod\" or \"staging\"; you will set the selector as follows: \"namespaceSelector\": {n  \"matchExpressions\": [n    {n      \"key\": \"environment\",n      \"operator\": \"In\",n      \"values\": [n        \"prod\",n        \"staging\"n      ]n    }n  ]n}nnSee https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/ for more examples of label selectors.nnDefault to the empty LabelSelector, which matches everything.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"objectSelector\": { SchemaProps: spec.SchemaProps{ Description: \"ObjectSelector decides whether to run the webhook based on if the object has matching labels. objectSelector is evaluated against both the oldObject and newObject that would be sent to the webhook, and is considered to match if either object matches the selector. A null object (oldObject in the case of create, or newObject in the case of delete) or an object that cannot have labels (like a DeploymentRollback or a PodProxyOptions object) is not considered to match. Use the object selector only if the webhook is opt-in, because end users may skip the admission webhook by setting the labels. Default to the empty LabelSelector, which matches everything.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"sideEffects\": { SchemaProps: spec.SchemaProps{ Description: \"SideEffects states whether this webhook has side effects. Acceptable values are: None, NoneOnDryRun (webhooks created via v1beta1 may also specify Some or Unknown). Webhooks with side effects MUST implement a reconciliation system, since a request may be rejected by a future step in the admission chain and the side effects therefore need to be undone. Requests with the dryRun attribute will be auto-rejected if they match a webhook with sideEffects == Unknown or Some.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"timeoutSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"TimeoutSeconds specifies the timeout for this webhook. After the timeout passes, the webhook call will be ignored or the API call will fail based on the failure policy. The timeout value must be between 1 and 30 seconds. Default to 10 seconds.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"admissionReviewVersions\": { SchemaProps: spec.SchemaProps{ Description: \"AdmissionReviewVersions is an ordered list of preferred `AdmissionReview` versions the Webhook expects. API server will try to use first version in the list which it supports. If none of the versions specified in this list supported by API server, validation will fail for this object. If a persisted webhook configuration specifies allowed versions and does not include any versions known to the API Server, calls to the webhook will fail and be subject to the failure policy.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"reinvocationPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"reinvocationPolicy indicates whether this webhook should be called multiple times as part of a single admission evaluation. Allowed values are \"Never\" and \"IfNeeded\".nnNever: the webhook will not be called more than once in a single admission evaluation.nnIfNeeded: the webhook will be called at least one additional time as part of the admission evaluation if the object being admitted is modified by other admission plugins after the initial webhook call. Webhooks that specify this option *must* be idempotent, able to process objects they previously admitted. Note: * the number of additional invocations is not guaranteed to be exactly one. * if additional invocations result in further modifications to the object, webhooks are not guaranteed to be invoked again. * webhooks that use this option may be reordered to minimize the number of additional invocations. * to validate an object after all mutations are guaranteed complete, use a validating admission webhook instead.nnDefaults to \"Never\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"clientConfig\", \"sideEffects\", \"admissionReviewVersions\"}, }, }, Dependencies: []string{ \"k8s.io/api/admissionregistration/v1.RuleWithOperations\", \"k8s.io/api/admissionregistration/v1.WebhookClientConfig\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_admissionregistration_v1_MutatingWebhookConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MutatingWebhookConfiguration describes the configuration of and admission webhook that accept or reject and may change the object.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object metadata; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"webhooks\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"name\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Webhooks is a list of webhooks and the affected resources and operations.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/admissionregistration/v1.MutatingWebhook\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/admissionregistration/v1.MutatingWebhook\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_admissionregistration_v1_MutatingWebhookConfigurationList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MutatingWebhookConfigurationList is a list of MutatingWebhookConfiguration.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of MutatingWebhookConfiguration.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/admissionregistration/v1.MutatingWebhookConfiguration\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/admissionregistration/v1.MutatingWebhookConfiguration\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_admissionregistration_v1_Rule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Rule is a tuple of APIGroups, APIVersion, and Resources.It is recommended to make sure that all the tuple expansions are valid.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"apiGroups\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroups is the API groups the resources belong to. '*' is all groups. If '*' is present, the length of the slice must be one. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"apiVersions\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersions is the API versions the resources belong to. '*' is all versions. If '*' is present, the length of the slice must be one. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"Resources is a list of resources this rule applies to.nnFor example: 'pods' means pods. 'pods/log' means the log subresource of pods. '*' means all resources, but not subresources. 'pods/*' means all subresources of pods. '*/scale' means all scale subresources. '*/*' means all resources and their subresources.nnIf wildcard is present, the validation rule will ensure resources do not overlap with each other.nnDepending on the enclosing object, subresources might not be allowed. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"scope\": { SchemaProps: spec.SchemaProps{ Description: \"scope specifies the scope of this rule. Valid values are \"Cluster\", \"Namespaced\", and \"*\" \"Cluster\" means that only cluster-scoped resources will match this rule. Namespace API objects are cluster-scoped. \"Namespaced\" means that only namespaced resources will match this rule. \"*\" means that there are no scope restrictions. Subresources match the scope of their parent resource. Default is \"*\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_admissionregistration_v1_RuleWithOperations(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RuleWithOperations is a tuple of Operations and Resources. It is recommended to make sure that all the tuple expansions are valid.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"operations\": { SchemaProps: spec.SchemaProps{ Description: \"Operations is the operations the admission hook cares about - CREATE, UPDATE, DELETE, CONNECT or * for all of those operations and any future admission operations that are added. If '*' is present, the length of the slice must be one. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"apiGroups\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroups is the API groups the resources belong to. '*' is all groups. If '*' is present, the length of the slice must be one. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"apiVersions\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersions is the API versions the resources belong to. '*' is all versions. If '*' is present, the length of the slice must be one. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"Resources is a list of resources this rule applies to.nnFor example: 'pods' means pods. 'pods/log' means the log subresource of pods. '*' means all resources, but not subresources. 'pods/*' means all subresources of pods. '*/scale' means all scale subresources. '*/*' means all resources and their subresources.nnIf wildcard is present, the validation rule will ensure resources do not overlap with each other.nnDepending on the enclosing object, subresources might not be allowed. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"scope\": { SchemaProps: spec.SchemaProps{ Description: \"scope specifies the scope of this rule. Valid values are \"Cluster\", \"Namespaced\", and \"*\" \"Cluster\" means that only cluster-scoped resources will match this rule. Namespace API objects are cluster-scoped. \"Namespaced\" means that only namespaced resources will match this rule. \"*\" means that there are no scope restrictions. Subresources match the scope of their parent resource. Default is \"*\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_admissionregistration_v1_ServiceReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ServiceReference holds a reference to Service.legacy.k8s.io\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"`namespace` is the namespace of the service. Required\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"`name` is the name of the service. Required\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"path\": { SchemaProps: spec.SchemaProps{ Description: \"`path` is an optional URL path which will be sent in any request to this service.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"port\": { SchemaProps: spec.SchemaProps{ Description: \"If specified, the port on the service that hosting webhook. Default to 443 for backward compatibility. `port` should be a valid port number (1-65535, inclusive).\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"namespace\", \"name\"}, }, }, } } func schema_k8sio_api_admissionregistration_v1_ValidatingWebhook(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ValidatingWebhook describes an admission webhook and the resources and operations it applies to.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"The name of the admission webhook. Name should be fully qualified, e.g., imagepolicy.kubernetes.io, where \"imagepolicy\" is the name of the webhook, and kubernetes.io is the name of the organization. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"clientConfig\": { SchemaProps: spec.SchemaProps{ Description: \"ClientConfig defines how to communicate with the hook. Required\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/admissionregistration/v1.WebhookClientConfig\"), }, }, \"rules\": { SchemaProps: spec.SchemaProps{ Description: \"Rules describes what operations on what resources/subresources the webhook cares about. The webhook cares about an operation if it matches _any_ Rule. However, in order to prevent ValidatingAdmissionWebhooks and MutatingAdmissionWebhooks from putting the cluster in a state which cannot be recovered from without completely disabling the plugin, ValidatingAdmissionWebhooks and MutatingAdmissionWebhooks are never called on admission requests for ValidatingWebhookConfiguration and MutatingWebhookConfiguration objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/admissionregistration/v1.RuleWithOperations\"), }, }, }, }, }, \"failurePolicy\": { SchemaProps: spec.SchemaProps{ Description: \"FailurePolicy defines how unrecognized errors from the admission endpoint are handled - allowed values are Ignore or Fail. Defaults to Fail.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"matchPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"matchPolicy defines how the \"rules\" list is used to match incoming requests. Allowed values are \"Exact\" or \"Equivalent\".nn- Exact: match a request only if it exactly matches a specified rule. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, but \"rules\" only included `apiGroups:[\"apps\"], apiVersions:[\"v1\"], resources: [\"deployments\"]`, a request to apps/v1beta1 or extensions/v1beta1 would not be sent to the webhook.nn- Equivalent: match a request if modifies a resource listed in rules, even via another API group or version. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, and \"rules\" only included `apiGroups:[\"apps\"], apiVersions:[\"v1\"], resources: [\"deployments\"]`, a request to apps/v1beta1 or extensions/v1beta1 would be converted to apps/v1 and sent to the webhook.nnDefaults to \"Equivalent\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"namespaceSelector\": { SchemaProps: spec.SchemaProps{ Description: \"NamespaceSelector decides whether to run the webhook on an object based on whether the namespace for that object matches the selector. If the object itself is a namespace, the matching is performed on object.metadata.labels. If the object is another cluster scoped resource, it never skips the webhook.nnFor example, to run the webhook on any objects whose namespace is not associated with \"runlevel\" of \"0\" or \"1\";  you will set the selector as follows: \"namespaceSelector\": {n  \"matchExpressions\": [n    {n      \"key\": \"runlevel\",n      \"operator\": \"NotIn\",n      \"values\": [n        \"0\",n        \"1\"n      ]n    }n  ]n}nnIf instead you want to only run the webhook on any objects whose namespace is associated with the \"environment\" of \"prod\" or \"staging\"; you will set the selector as follows: \"namespaceSelector\": {n  \"matchExpressions\": [n    {n      \"key\": \"environment\",n      \"operator\": \"In\",n      \"values\": [n        \"prod\",n        \"staging\"n      ]n    }n  ]n}nnSee https://kubernetes.io/docs/concepts/overview/working-with-objects/labels for more examples of label selectors.nnDefault to the empty LabelSelector, which matches everything.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"objectSelector\": { SchemaProps: spec.SchemaProps{ Description: \"ObjectSelector decides whether to run the webhook based on if the object has matching labels. objectSelector is evaluated against both the oldObject and newObject that would be sent to the webhook, and is considered to match if either object matches the selector. A null object (oldObject in the case of create, or newObject in the case of delete) or an object that cannot have labels (like a DeploymentRollback or a PodProxyOptions object) is not considered to match. Use the object selector only if the webhook is opt-in, because end users may skip the admission webhook by setting the labels. Default to the empty LabelSelector, which matches everything.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"sideEffects\": { SchemaProps: spec.SchemaProps{ Description: \"SideEffects states whether this webhook has side effects. Acceptable values are: None, NoneOnDryRun (webhooks created via v1beta1 may also specify Some or Unknown). Webhooks with side effects MUST implement a reconciliation system, since a request may be rejected by a future step in the admission chain and the side effects therefore need to be undone. Requests with the dryRun attribute will be auto-rejected if they match a webhook with sideEffects == Unknown or Some.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"timeoutSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"TimeoutSeconds specifies the timeout for this webhook. After the timeout passes, the webhook call will be ignored or the API call will fail based on the failure policy. The timeout value must be between 1 and 30 seconds. Default to 10 seconds.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"admissionReviewVersions\": { SchemaProps: spec.SchemaProps{ Description: \"AdmissionReviewVersions is an ordered list of preferred `AdmissionReview` versions the Webhook expects. API server will try to use first version in the list which it supports. If none of the versions specified in this list supported by API server, validation will fail for this object. If a persisted webhook configuration specifies allowed versions and does not include any versions known to the API Server, calls to the webhook will fail and be subject to the failure policy.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"name\", \"clientConfig\", \"sideEffects\", \"admissionReviewVersions\"}, }, }, Dependencies: []string{ \"k8s.io/api/admissionregistration/v1.RuleWithOperations\", \"k8s.io/api/admissionregistration/v1.WebhookClientConfig\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_admissionregistration_v1_ValidatingWebhookConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ValidatingWebhookConfiguration describes the configuration of and admission webhook that accept or reject and object without changing it.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object metadata; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"webhooks\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"name\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Webhooks is a list of webhooks and the affected resources and operations.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/admissionregistration/v1.ValidatingWebhook\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/admissionregistration/v1.ValidatingWebhook\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_admissionregistration_v1_ValidatingWebhookConfigurationList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ValidatingWebhookConfigurationList is a list of ValidatingWebhookConfiguration.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of ValidatingWebhookConfiguration.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/admissionregistration/v1.ValidatingWebhookConfiguration\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/admissionregistration/v1.ValidatingWebhookConfiguration\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_admissionregistration_v1_WebhookClientConfig(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"WebhookClientConfig contains the information to make a TLS connection with the webhook\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"url\": { SchemaProps: spec.SchemaProps{ Description: \"`url` gives the location of the webhook, in standard URL form (`scheme://host:port/path`). Exactly one of `url` or `service` must be specified.nnThe `host` should not refer to a service running in the cluster; use the `service` field instead. The host might be resolved via external DNS in some apiservers (e.g., `kube-apiserver` cannot resolve in-cluster DNS as that would be a layering violation). `host` may also be an IP address.nnPlease note that using `localhost` or `127.0.0.1` as a `host` is risky unless you take great care to run this webhook on all hosts which run an apiserver which might need to make calls to this webhook. Such installs are likely to be non-portable, i.e., not easy to turn up in a new cluster.nnThe scheme must be \"https\"; the URL must begin with \"https://\".nnA path is optional, and if present may be any string permissible in a URL. You may use the path to pass an arbitrary string to the webhook, for example, a cluster identifier.nnAttempting to use a user or basic auth e.g. \"user:password@\" is not allowed. Fragments (\"#...\") and query parameters (\"?...\") are not allowed, either.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"service\": { SchemaProps: spec.SchemaProps{ Description: \"`service` is a reference to the service for this webhook. Either `service` or `url` must be specified.nnIf the webhook is running within the cluster, then you should use `service`.\", Ref:         ref(\"k8s.io/api/admissionregistration/v1.ServiceReference\"), }, }, \"caBundle\": { SchemaProps: spec.SchemaProps{ Description: \"`caBundle` is a PEM encoded CA bundle which will be used to validate the webhook's server certificate. If unspecified, system trust roots on the apiserver are used.\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/admissionregistration/v1.ServiceReference\"}, } } func schema_k8sio_api_admissionregistration_v1beta1_MutatingWebhook(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MutatingWebhook describes an admission webhook and the resources and operations it applies to.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"The name of the admission webhook. Name should be fully qualified, e.g., imagepolicy.kubernetes.io, where \"imagepolicy\" is the name of the webhook, and kubernetes.io is the name of the organization. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"clientConfig\": { SchemaProps: spec.SchemaProps{ Description: \"ClientConfig defines how to communicate with the hook. Required\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/admissionregistration/v1beta1.WebhookClientConfig\"), }, }, \"rules\": { SchemaProps: spec.SchemaProps{ Description: \"Rules describes what operations on what resources/subresources the webhook cares about. The webhook cares about an operation if it matches _any_ Rule. However, in order to prevent ValidatingAdmissionWebhooks and MutatingAdmissionWebhooks from putting the cluster in a state which cannot be recovered from without completely disabling the plugin, ValidatingAdmissionWebhooks and MutatingAdmissionWebhooks are never called on admission requests for ValidatingWebhookConfiguration and MutatingWebhookConfiguration objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/admissionregistration/v1beta1.RuleWithOperations\"), }, }, }, }, }, \"failurePolicy\": { SchemaProps: spec.SchemaProps{ Description: \"FailurePolicy defines how unrecognized errors from the admission endpoint are handled - allowed values are Ignore or Fail. Defaults to Ignore.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"matchPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"matchPolicy defines how the \"rules\" list is used to match incoming requests. Allowed values are \"Exact\" or \"Equivalent\".nn- Exact: match a request only if it exactly matches a specified rule. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, but \"rules\" only included `apiGroups:[\"apps\"], apiVersions:[\"v1\"], resources: [\"deployments\"]`, a request to apps/v1beta1 or extensions/v1beta1 would not be sent to the webhook.nn- Equivalent: match a request if modifies a resource listed in rules, even via another API group or version. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, and \"rules\" only included `apiGroups:[\"apps\"], apiVersions:[\"v1\"], resources: [\"deployments\"]`, a request to apps/v1beta1 or extensions/v1beta1 would be converted to apps/v1 and sent to the webhook.nnDefaults to \"Exact\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"namespaceSelector\": { SchemaProps: spec.SchemaProps{ Description: \"NamespaceSelector decides whether to run the webhook on an object based on whether the namespace for that object matches the selector. If the object itself is a namespace, the matching is performed on object.metadata.labels. If the object is another cluster scoped resource, it never skips the webhook.nnFor example, to run the webhook on any objects whose namespace is not associated with \"runlevel\" of \"0\" or \"1\";  you will set the selector as follows: \"namespaceSelector\": {n  \"matchExpressions\": [n    {n      \"key\": \"runlevel\",n      \"operator\": \"NotIn\",n      \"values\": [n        \"0\",n        \"1\"n      ]n    }n  ]n}nnIf instead you want to only run the webhook on any objects whose namespace is associated with the \"environment\" of \"prod\" or \"staging\"; you will set the selector as follows: \"namespaceSelector\": {n  \"matchExpressions\": [n    {n      \"key\": \"environment\",n      \"operator\": \"In\",n      \"values\": [n        \"prod\",n        \"staging\"n      ]n    }n  ]n}nnSee https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/ for more examples of label selectors.nnDefault to the empty LabelSelector, which matches everything.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"objectSelector\": { SchemaProps: spec.SchemaProps{ Description: \"ObjectSelector decides whether to run the webhook based on if the object has matching labels. objectSelector is evaluated against both the oldObject and newObject that would be sent to the webhook, and is considered to match if either object matches the selector. A null object (oldObject in the case of create, or newObject in the case of delete) or an object that cannot have labels (like a DeploymentRollback or a PodProxyOptions object) is not considered to match. Use the object selector only if the webhook is opt-in, because end users may skip the admission webhook by setting the labels. Default to the empty LabelSelector, which matches everything.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"sideEffects\": { SchemaProps: spec.SchemaProps{ Description: \"SideEffects states whether this webhook has side effects. Acceptable values are: Unknown, None, Some, NoneOnDryRun Webhooks with side effects MUST implement a reconciliation system, since a request may be rejected by a future step in the admission chain and the side effects therefore need to be undone. Requests with the dryRun attribute will be auto-rejected if they match a webhook with sideEffects == Unknown or Some. Defaults to Unknown.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"timeoutSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"TimeoutSeconds specifies the timeout for this webhook. After the timeout passes, the webhook call will be ignored or the API call will fail based on the failure policy. The timeout value must be between 1 and 30 seconds. Default to 30 seconds.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"admissionReviewVersions\": { SchemaProps: spec.SchemaProps{ Description: \"AdmissionReviewVersions is an ordered list of preferred `AdmissionReview` versions the Webhook expects. API server will try to use first version in the list which it supports. If none of the versions specified in this list supported by API server, validation will fail for this object. If a persisted webhook configuration specifies allowed versions and does not include any versions known to the API Server, calls to the webhook will fail and be subject to the failure policy. Default to `['v1beta1']`.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"reinvocationPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"reinvocationPolicy indicates whether this webhook should be called multiple times as part of a single admission evaluation. Allowed values are \"Never\" and \"IfNeeded\".nnNever: the webhook will not be called more than once in a single admission evaluation.nnIfNeeded: the webhook will be called at least one additional time as part of the admission evaluation if the object being admitted is modified by other admission plugins after the initial webhook call. Webhooks that specify this option *must* be idempotent, able to process objects they previously admitted. Note: * the number of additional invocations is not guaranteed to be exactly one. * if additional invocations result in further modifications to the object, webhooks are not guaranteed to be invoked again. * webhooks that use this option may be reordered to minimize the number of additional invocations. * to validate an object after all mutations are guaranteed complete, use a validating admission webhook instead.nnDefaults to \"Never\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"clientConfig\"}, }, }, Dependencies: []string{ \"k8s.io/api/admissionregistration/v1beta1.RuleWithOperations\", \"k8s.io/api/admissionregistration/v1beta1.WebhookClientConfig\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_admissionregistration_v1beta1_MutatingWebhookConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MutatingWebhookConfiguration describes the configuration of and admission webhook that accept or reject and may change the object. Deprecated in v1.16, planned for removal in v1.19. Use admissionregistration.k8s.io/v1 MutatingWebhookConfiguration instead.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object metadata; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"webhooks\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"name\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Webhooks is a list of webhooks and the affected resources and operations.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/admissionregistration/v1beta1.MutatingWebhook\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/admissionregistration/v1beta1.MutatingWebhook\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_admissionregistration_v1beta1_MutatingWebhookConfigurationList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MutatingWebhookConfigurationList is a list of MutatingWebhookConfiguration.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of MutatingWebhookConfiguration.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/admissionregistration/v1beta1.MutatingWebhookConfiguration\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/admissionregistration/v1beta1.MutatingWebhookConfiguration\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_admissionregistration_v1beta1_Rule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Rule is a tuple of APIGroups, APIVersion, and Resources.It is recommended to make sure that all the tuple expansions are valid.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"apiGroups\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroups is the API groups the resources belong to. '*' is all groups. If '*' is present, the length of the slice must be one. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"apiVersions\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersions is the API versions the resources belong to. '*' is all versions. If '*' is present, the length of the slice must be one. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"Resources is a list of resources this rule applies to.nnFor example: 'pods' means pods. 'pods/log' means the log subresource of pods. '*' means all resources, but not subresources. 'pods/*' means all subresources of pods. '*/scale' means all scale subresources. '*/*' means all resources and their subresources.nnIf wildcard is present, the validation rule will ensure resources do not overlap with each other.nnDepending on the enclosing object, subresources might not be allowed. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"scope\": { SchemaProps: spec.SchemaProps{ Description: \"scope specifies the scope of this rule. Valid values are \"Cluster\", \"Namespaced\", and \"*\" \"Cluster\" means that only cluster-scoped resources will match this rule. Namespace API objects are cluster-scoped. \"Namespaced\" means that only namespaced resources will match this rule. \"*\" means that there are no scope restrictions. Subresources match the scope of their parent resource. Default is \"*\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_admissionregistration_v1beta1_RuleWithOperations(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RuleWithOperations is a tuple of Operations and Resources. It is recommended to make sure that all the tuple expansions are valid.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"operations\": { SchemaProps: spec.SchemaProps{ Description: \"Operations is the operations the admission hook cares about - CREATE, UPDATE, DELETE, CONNECT or * for all of those operations and any future admission operations that are added. If '*' is present, the length of the slice must be one. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"apiGroups\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroups is the API groups the resources belong to. '*' is all groups. If '*' is present, the length of the slice must be one. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"apiVersions\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersions is the API versions the resources belong to. '*' is all versions. If '*' is present, the length of the slice must be one. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"Resources is a list of resources this rule applies to.nnFor example: 'pods' means pods. 'pods/log' means the log subresource of pods. '*' means all resources, but not subresources. 'pods/*' means all subresources of pods. '*/scale' means all scale subresources. '*/*' means all resources and their subresources.nnIf wildcard is present, the validation rule will ensure resources do not overlap with each other.nnDepending on the enclosing object, subresources might not be allowed. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"scope\": { SchemaProps: spec.SchemaProps{ Description: \"scope specifies the scope of this rule. Valid values are \"Cluster\", \"Namespaced\", and \"*\" \"Cluster\" means that only cluster-scoped resources will match this rule. Namespace API objects are cluster-scoped. \"Namespaced\" means that only namespaced resources will match this rule. \"*\" means that there are no scope restrictions. Subresources match the scope of their parent resource. Default is \"*\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_admissionregistration_v1beta1_ServiceReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ServiceReference holds a reference to Service.legacy.k8s.io\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"`namespace` is the namespace of the service. Required\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"`name` is the name of the service. Required\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"path\": { SchemaProps: spec.SchemaProps{ Description: \"`path` is an optional URL path which will be sent in any request to this service.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"port\": { SchemaProps: spec.SchemaProps{ Description: \"If specified, the port on the service that hosting webhook. Default to 443 for backward compatibility. `port` should be a valid port number (1-65535, inclusive).\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"namespace\", \"name\"}, }, }, } } func schema_k8sio_api_admissionregistration_v1beta1_ValidatingWebhook(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ValidatingWebhook describes an admission webhook and the resources and operations it applies to.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"The name of the admission webhook. Name should be fully qualified, e.g., imagepolicy.kubernetes.io, where \"imagepolicy\" is the name of the webhook, and kubernetes.io is the name of the organization. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"clientConfig\": { SchemaProps: spec.SchemaProps{ Description: \"ClientConfig defines how to communicate with the hook. Required\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/admissionregistration/v1beta1.WebhookClientConfig\"), }, }, \"rules\": { SchemaProps: spec.SchemaProps{ Description: \"Rules describes what operations on what resources/subresources the webhook cares about. The webhook cares about an operation if it matches _any_ Rule. However, in order to prevent ValidatingAdmissionWebhooks and MutatingAdmissionWebhooks from putting the cluster in a state which cannot be recovered from without completely disabling the plugin, ValidatingAdmissionWebhooks and MutatingAdmissionWebhooks are never called on admission requests for ValidatingWebhookConfiguration and MutatingWebhookConfiguration objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/admissionregistration/v1beta1.RuleWithOperations\"), }, }, }, }, }, \"failurePolicy\": { SchemaProps: spec.SchemaProps{ Description: \"FailurePolicy defines how unrecognized errors from the admission endpoint are handled - allowed values are Ignore or Fail. Defaults to Ignore.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"matchPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"matchPolicy defines how the \"rules\" list is used to match incoming requests. Allowed values are \"Exact\" or \"Equivalent\".nn- Exact: match a request only if it exactly matches a specified rule. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, but \"rules\" only included `apiGroups:[\"apps\"], apiVersions:[\"v1\"], resources: [\"deployments\"]`, a request to apps/v1beta1 or extensions/v1beta1 would not be sent to the webhook.nn- Equivalent: match a request if modifies a resource listed in rules, even via another API group or version. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, and \"rules\" only included `apiGroups:[\"apps\"], apiVersions:[\"v1\"], resources: [\"deployments\"]`, a request to apps/v1beta1 or extensions/v1beta1 would be converted to apps/v1 and sent to the webhook.nnDefaults to \"Exact\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"namespaceSelector\": { SchemaProps: spec.SchemaProps{ Description: \"NamespaceSelector decides whether to run the webhook on an object based on whether the namespace for that object matches the selector. If the object itself is a namespace, the matching is performed on object.metadata.labels. If the object is another cluster scoped resource, it never skips the webhook.nnFor example, to run the webhook on any objects whose namespace is not associated with \"runlevel\" of \"0\" or \"1\";  you will set the selector as follows: \"namespaceSelector\": {n  \"matchExpressions\": [n    {n      \"key\": \"runlevel\",n      \"operator\": \"NotIn\",n      \"values\": [n        \"0\",n        \"1\"n      ]n    }n  ]n}nnIf instead you want to only run the webhook on any objects whose namespace is associated with the \"environment\" of \"prod\" or \"staging\"; you will set the selector as follows: \"namespaceSelector\": {n  \"matchExpressions\": [n    {n      \"key\": \"environment\",n      \"operator\": \"In\",n      \"values\": [n        \"prod\",n        \"staging\"n      ]n    }n  ]n}nnSee https://kubernetes.io/docs/concepts/overview/working-with-objects/labels for more examples of label selectors.nnDefault to the empty LabelSelector, which matches everything.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"objectSelector\": { SchemaProps: spec.SchemaProps{ Description: \"ObjectSelector decides whether to run the webhook based on if the object has matching labels. objectSelector is evaluated against both the oldObject and newObject that would be sent to the webhook, and is considered to match if either object matches the selector. A null object (oldObject in the case of create, or newObject in the case of delete) or an object that cannot have labels (like a DeploymentRollback or a PodProxyOptions object) is not considered to match. Use the object selector only if the webhook is opt-in, because end users may skip the admission webhook by setting the labels. Default to the empty LabelSelector, which matches everything.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"sideEffects\": { SchemaProps: spec.SchemaProps{ Description: \"SideEffects states whether this webhook has side effects. Acceptable values are: Unknown, None, Some, NoneOnDryRun Webhooks with side effects MUST implement a reconciliation system, since a request may be rejected by a future step in the admission chain and the side effects therefore need to be undone. Requests with the dryRun attribute will be auto-rejected if they match a webhook with sideEffects == Unknown or Some. Defaults to Unknown.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"timeoutSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"TimeoutSeconds specifies the timeout for this webhook. After the timeout passes, the webhook call will be ignored or the API call will fail based on the failure policy. The timeout value must be between 1 and 30 seconds. Default to 30 seconds.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"admissionReviewVersions\": { SchemaProps: spec.SchemaProps{ Description: \"AdmissionReviewVersions is an ordered list of preferred `AdmissionReview` versions the Webhook expects. API server will try to use first version in the list which it supports. If none of the versions specified in this list supported by API server, validation will fail for this object. If a persisted webhook configuration specifies allowed versions and does not include any versions known to the API Server, calls to the webhook will fail and be subject to the failure policy. Default to `['v1beta1']`.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"name\", \"clientConfig\"}, }, }, Dependencies: []string{ \"k8s.io/api/admissionregistration/v1beta1.RuleWithOperations\", \"k8s.io/api/admissionregistration/v1beta1.WebhookClientConfig\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_admissionregistration_v1beta1_ValidatingWebhookConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ValidatingWebhookConfiguration describes the configuration of and admission webhook that accept or reject and object without changing it. Deprecated in v1.16, planned for removal in v1.19. Use admissionregistration.k8s.io/v1 ValidatingWebhookConfiguration instead.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object metadata; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"webhooks\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"name\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Webhooks is a list of webhooks and the affected resources and operations.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/admissionregistration/v1beta1.ValidatingWebhook\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/admissionregistration/v1beta1.ValidatingWebhook\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_admissionregistration_v1beta1_ValidatingWebhookConfigurationList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ValidatingWebhookConfigurationList is a list of ValidatingWebhookConfiguration.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of ValidatingWebhookConfiguration.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/admissionregistration/v1beta1.ValidatingWebhookConfiguration\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/admissionregistration/v1beta1.ValidatingWebhookConfiguration\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_admissionregistration_v1beta1_WebhookClientConfig(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"WebhookClientConfig contains the information to make a TLS connection with the webhook\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"url\": { SchemaProps: spec.SchemaProps{ Description: \"`url` gives the location of the webhook, in standard URL form (`scheme://host:port/path`). Exactly one of `url` or `service` must be specified.nnThe `host` should not refer to a service running in the cluster; use the `service` field instead. The host might be resolved via external DNS in some apiservers (e.g., `kube-apiserver` cannot resolve in-cluster DNS as that would be a layering violation). `host` may also be an IP address.nnPlease note that using `localhost` or `127.0.0.1` as a `host` is risky unless you take great care to run this webhook on all hosts which run an apiserver which might need to make calls to this webhook. Such installs are likely to be non-portable, i.e., not easy to turn up in a new cluster.nnThe scheme must be \"https\"; the URL must begin with \"https://\".nnA path is optional, and if present may be any string permissible in a URL. You may use the path to pass an arbitrary string to the webhook, for example, a cluster identifier.nnAttempting to use a user or basic auth e.g. \"user:password@\" is not allowed. Fragments (\"#...\") and query parameters (\"?...\") are not allowed, either.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"service\": { SchemaProps: spec.SchemaProps{ Description: \"`service` is a reference to the service for this webhook. Either `service` or `url` must be specified.nnIf the webhook is running within the cluster, then you should use `service`.\", Ref:         ref(\"k8s.io/api/admissionregistration/v1beta1.ServiceReference\"), }, }, \"caBundle\": { SchemaProps: spec.SchemaProps{ Description: \"`caBundle` is a PEM encoded CA bundle which will be used to validate the webhook's server certificate. If unspecified, system trust roots on the apiserver are used.\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/admissionregistration/v1beta1.ServiceReference\"}, } } func schema_k8sio_api_apiserverinternal_v1alpha1_ServerStorageVersion(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"An API server instance reports the version it can decode and the version it encodes objects to when persisting objects in the backend.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"apiServerID\": { SchemaProps: spec.SchemaProps{ Description: \"The ID of the reporting API server.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"encodingVersion\": { SchemaProps: spec.SchemaProps{ Description: \"The API server encodes the object to this version when persisting it in the backend (e.g., etcd).\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"decodableVersions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"The API server can decode objects encoded in these versions. The encodingVersion must be included in the decodableVersions.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, } } func schema_k8sio_api_apiserverinternal_v1alpha1_StorageVersion(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"n Storage version of a specific resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"The name is <group>.<resource>.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec is an empty spec. It is here to comply with Kubernetes API style.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apiserverinternal/v1alpha1.StorageVersionSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"API server instances report the version they can decode and the version they encode objects to when persisting objects in the backend.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apiserverinternal/v1alpha1.StorageVersionStatus\"), }, }, }, Required: []string{\"spec\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/api/apiserverinternal/v1alpha1.StorageVersionSpec\", \"k8s.io/api/apiserverinternal/v1alpha1.StorageVersionStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_apiserverinternal_v1alpha1_StorageVersionCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Describes the state of the storageVersion at a certain point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of the condition.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"If set, this represents the .metadata.generation that the condition was set based upon.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"Last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"The reason for the condition's last transition.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"A human readable message indicating details about the transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\", \"reason\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_apiserverinternal_v1alpha1_StorageVersionList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"A list of StorageVersions.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items holds a list of StorageVersion\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apiserverinternal/v1alpha1.StorageVersion\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/apiserverinternal/v1alpha1.StorageVersion\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_apiserverinternal_v1alpha1_StorageVersionSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StorageVersionSpec is an empty spec.\", Type:        []string{\"object\"}, }, }, } } func schema_k8sio_api_apiserverinternal_v1alpha1_StorageVersionStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"API server instances report the versions they can decode and the version they encode objects to when persisting objects in the backend.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"storageVersions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"apiServerID\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"The reported versions per API server instance.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apiserverinternal/v1alpha1.ServerStorageVersion\"), }, }, }, }, }, \"commonEncodingVersion\": { SchemaProps: spec.SchemaProps{ Description: \"If all API server instances agree on the same encoding storage version, then this field is set to that version. Otherwise this field is left empty. API servers should finish updating its storageVersionStatus entry before serving write operations, so that this field will be in sync with the reality.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"type\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"The latest available observations of the storageVersion's state.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apiserverinternal/v1alpha1.StorageVersionCondition\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apiserverinternal/v1alpha1.ServerStorageVersion\", \"k8s.io/api/apiserverinternal/v1alpha1.StorageVersionCondition\"}, } } func schema_k8sio_api_apps_v1_ControllerRevision(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ControllerRevision implements an immutable snapshot of state data. Clients are responsible for serializing and deserializing the objects that contain their internal state. Once a ControllerRevision has been successfully created, it can not be updated. The API Server will fail validation of all requests that attempt to mutate the Data field. ControllerRevisions may, however, be deleted. Note that, due to its use by both the DaemonSet and StatefulSet controllers for update and rollback, this object is beta. However, it may be subject to name and representation changes in future releases, and clients should not depend on its stability. It is primarily for internal use by controllers.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"data\": { SchemaProps: spec.SchemaProps{ Description: \"Data is the serialized representation of the state.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/runtime.RawExtension\"), }, }, \"revision\": { SchemaProps: spec.SchemaProps{ Description: \"Revision indicates the revision of the state represented by Data.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int64\", }, }, }, Required: []string{\"revision\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\", \"k8s.io/apimachinery/pkg/runtime.RawExtension\"}, } } func schema_k8sio_api_apps_v1_ControllerRevisionList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ControllerRevisionList is a resource containing a list of ControllerRevision objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of ControllerRevisions\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1.ControllerRevision\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1.ControllerRevision\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_apps_v1_DaemonSet(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DaemonSet represents the configuration of a daemon set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"The desired behavior of this daemon set. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1.DaemonSetSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"The current status of this daemon set. This data may be out of date by some window of time. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1.DaemonSetStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1.DaemonSetSpec\", \"k8s.io/api/apps/v1.DaemonSetStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_apps_v1_DaemonSetCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DaemonSetCondition describes the state of a DaemonSet at a certain point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of DaemonSet condition.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"Last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"The reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"A human readable message indicating details about the transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_apps_v1_DaemonSetList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DaemonSetList is a collection of daemon sets.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"A list of daemon sets.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1.DaemonSet\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1.DaemonSet\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_apps_v1_DaemonSetSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DaemonSetSpec is the specification of a daemon set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"A label query over pods that are managed by the daemon set. Must match in order to be controlled. It must match the pod template's labels. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"template\": { SchemaProps: spec.SchemaProps{ Description: \"An object that describes the pod that will be created. The DaemonSet will create exactly one copy of this pod on every node that matches the template's node selector (or on every node if no node selector is specified). More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodTemplateSpec\"), }, }, \"updateStrategy\": { SchemaProps: spec.SchemaProps{ Description: \"An update strategy to replace existing DaemonSet pods with new pods.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1.DaemonSetUpdateStrategy\"), }, }, \"minReadySeconds\": { SchemaProps: spec.SchemaProps{ Description: \"The minimum number of seconds for which a newly created DaemonSet pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready).\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"revisionHistoryLimit\": { SchemaProps: spec.SchemaProps{ Description: \"The number of old history to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. Defaults to 10.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"selector\", \"template\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1.DaemonSetUpdateStrategy\", \"k8s.io/api/core/v1.PodTemplateSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_apps_v1_DaemonSetStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DaemonSetStatus represents the current status of a daemon set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"currentNumberScheduled\": { SchemaProps: spec.SchemaProps{ Description: \"The number of nodes that are running at least 1 daemon pod and are supposed to run the daemon pod. More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"numberMisscheduled\": { SchemaProps: spec.SchemaProps{ Description: \"The number of nodes that are running the daemon pod, but are not supposed to run the daemon pod. More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"desiredNumberScheduled\": { SchemaProps: spec.SchemaProps{ Description: \"The total number of nodes that should be running the daemon pod (including nodes correctly running the daemon pod). More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"numberReady\": { SchemaProps: spec.SchemaProps{ Description: \"numberReady is the number of nodes that should be running the daemon pod and have one or more of the daemon pod running with a Ready Condition.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"The most recent generation observed by the daemon set controller.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"updatedNumberScheduled\": { SchemaProps: spec.SchemaProps{ Description: \"The total number of nodes that are running updated daemon pod\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"numberAvailable\": { SchemaProps: spec.SchemaProps{ Description: \"The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and available (ready for at least spec.minReadySeconds)\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"numberUnavailable\": { SchemaProps: spec.SchemaProps{ Description: \"The number of nodes that should be running the daemon pod and have none of the daemon pod running and available (ready for at least spec.minReadySeconds)\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"collisionCount\": { SchemaProps: spec.SchemaProps{ Description: \"Count of hash collisions for the DaemonSet. The DaemonSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Represents the latest available observations of a DaemonSet's current state.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1.DaemonSetCondition\"), }, }, }, }, }, }, Required: []string{\"currentNumberScheduled\", \"numberMisscheduled\", \"desiredNumberScheduled\", \"numberReady\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1.DaemonSetCondition\"}, } } func schema_k8sio_api_apps_v1_DaemonSetUpdateStrategy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DaemonSetUpdateStrategy is a struct used to control the update strategy for a DaemonSet.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of daemon set update. Can be \"RollingUpdate\" or \"OnDelete\". Default is RollingUpdate.nnPossible enum values:n - `\"OnDelete\"` Replace the old daemons only when it's killedn - `\"RollingUpdate\"` Replace the old daemons by new ones using rolling update i.e replace them on each node one after the other.\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"OnDelete\", \"RollingUpdate\"}}, }, \"rollingUpdate\": { SchemaProps: spec.SchemaProps{ Description: \"Rolling update config params. Present only if type = \"RollingUpdate\".\", Ref:         ref(\"k8s.io/api/apps/v1.RollingUpdateDaemonSet\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1.RollingUpdateDaemonSet\"}, } } func schema_k8sio_api_apps_v1_Deployment(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Deployment enables declarative updates for Pods and ReplicaSets.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the desired behavior of the Deployment.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1.DeploymentSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Most recently observed status of the Deployment.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1.DeploymentStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1.DeploymentSpec\", \"k8s.io/api/apps/v1.DeploymentStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_apps_v1_DeploymentCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentCondition describes the state of a deployment at a certain point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of deployment condition.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastUpdateTime\": { SchemaProps: spec.SchemaProps{ Description: \"The last time this condition was updated.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"Last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"The reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"A human readable message indicating details about the transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_apps_v1_DeploymentList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentList is a list of Deployments.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of Deployments.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1.Deployment\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1.Deployment\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_apps_v1_DeploymentSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentSpec is the specification of the desired behavior of the Deployment.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"Number of desired pods. This is a pointer to distinguish between explicit zero and not specified. Defaults to 1.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"Label selector for pods. Existing ReplicaSets whose pods are selected by this will be the ones affected by this deployment. It must match the pod template's labels.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"template\": { SchemaProps: spec.SchemaProps{ Description: \"Template describes the pods that will be created.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodTemplateSpec\"), }, }, \"strategy\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-strategy\": \"retainKeys\", }, }, SchemaProps: spec.SchemaProps{ Description: \"The deployment strategy to use to replace existing pods with new ones.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1.DeploymentStrategy\"), }, }, \"minReadySeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"revisionHistoryLimit\": { SchemaProps: spec.SchemaProps{ Description: \"The number of old ReplicaSets to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. Defaults to 10.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"paused\": { SchemaProps: spec.SchemaProps{ Description: \"Indicates that the deployment is paused.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"progressDeadlineSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"The maximum time in seconds for a deployment to make progress before it is considered to be failed. The deployment controller will continue to process failed deployments and a condition with a ProgressDeadlineExceeded reason will be surfaced in the deployment status. Note that progress will not be estimated during the time a deployment is paused. Defaults to 600s.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"selector\", \"template\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1.DeploymentStrategy\", \"k8s.io/api/core/v1.PodTemplateSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_apps_v1_DeploymentStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentStatus is the most recently observed status of the Deployment.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"The generation observed by the deployment controller.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of non-terminated pods targeted by this deployment (their labels match the selector).\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"updatedReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of non-terminated pods targeted by this deployment that have the desired template spec.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"readyReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"readyReplicas is the number of pods targeted by this Deployment with a Ready Condition.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"availableReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of available pods (ready for at least minReadySeconds) targeted by this deployment.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"unavailableReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of unavailable pods targeted by this deployment. This is the total number of pods that are still required for the deployment to have 100% available capacity. They may either be pods that are running but not yet available or pods that still have not been created.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Represents the latest available observations of a deployment's current state.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1.DeploymentCondition\"), }, }, }, }, }, \"collisionCount\": { SchemaProps: spec.SchemaProps{ Description: \"Count of hash collisions for the Deployment. The Deployment controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ReplicaSet.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1.DeploymentCondition\"}, } } func schema_k8sio_api_apps_v1_DeploymentStrategy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentStrategy describes how to replace existing pods with new ones.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of deployment. Can be \"Recreate\" or \"RollingUpdate\". Default is RollingUpdate.nnPossible enum values:n - `\"Recreate\"` Kill all existing pods before creating new ones.n - `\"RollingUpdate\"` Replace the old ReplicaSets by new one using rolling update i.e gradually scale down the old ReplicaSets and scale up the new one.\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"Recreate\", \"RollingUpdate\"}}, }, \"rollingUpdate\": { SchemaProps: spec.SchemaProps{ Description: \"Rolling update config params. Present only if DeploymentStrategyType = RollingUpdate.\", Ref:         ref(\"k8s.io/api/apps/v1.RollingUpdateDeployment\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1.RollingUpdateDeployment\"}, } } func schema_k8sio_api_apps_v1_ReplicaSet(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicaSet ensures that a specified number of pod replicas are running at any given time.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"If the Labels of a ReplicaSet are empty, they are defaulted to be the same as the Pod(s) that the ReplicaSet manages. Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec defines the specification of the desired behavior of the ReplicaSet. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1.ReplicaSetSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is the most recently observed status of the ReplicaSet. This data may be out of date by some window of time. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1.ReplicaSetStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1.ReplicaSetSpec\", \"k8s.io/api/apps/v1.ReplicaSetStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_apps_v1_ReplicaSetCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicaSetCondition describes the state of a replica set at a certain point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of replica set condition.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"The last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"The reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"A human readable message indicating details about the transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_apps_v1_ReplicaSetList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicaSetList is a collection of ReplicaSets.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of ReplicaSets. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1.ReplicaSet\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1.ReplicaSet\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_apps_v1_ReplicaSetSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicaSetSpec is the specification of a ReplicaSet.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"Replicas is the number of desired replicas. This is a pointer to distinguish between explicit zero and unspecified. Defaults to 1. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/#what-is-a-replicationcontroller\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"minReadySeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"Selector is a label query over pods that should match the replica count. Label keys and values that must match in order to be controlled by this replica set. It must match the pod template's labels. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"template\": { SchemaProps: spec.SchemaProps{ Description: \"Template is the object that describes the pod that will be created if insufficient replicas are detected. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodTemplateSpec\"), }, }, }, Required: []string{\"selector\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PodTemplateSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_apps_v1_ReplicaSetStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicaSetStatus represents the current status of a ReplicaSet.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"Replicas is the most recently oberved number of replicas. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/#what-is-a-replicationcontroller\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"fullyLabeledReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"The number of pods that have labels matching the labels of the pod template of the replicaset.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"readyReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"readyReplicas is the number of pods targeted by this ReplicaSet with a Ready Condition.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"availableReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"The number of available replicas (ready for at least minReadySeconds) for this replica set.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"ObservedGeneration reflects the generation of the most recently observed ReplicaSet.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Represents the latest available observations of a replica set's current state.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1.ReplicaSetCondition\"), }, }, }, }, }, }, Required: []string{\"replicas\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1.ReplicaSetCondition\"}, } } func schema_k8sio_api_apps_v1_RollingUpdateDaemonSet(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Spec to control the desired behavior of daemon set rolling update.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"maxUnavailable\": { SchemaProps: spec.SchemaProps{ Description: \"The maximum number of DaemonSet pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of total number of DaemonSet pods at the start of the update (ex: 10%). Absolute number is calculated from percentage by rounding up. This cannot be 0 if MaxSurge is 0 Default value is 1. Example: when this is set to 30%, at most 30% of the total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their pods stopped for an update at any given time. The update starts by stopping at most 30% of those DaemonSet pods and then brings up new DaemonSet pods in their place. Once the new pods are available, it then proceeds onto other DaemonSet pods, thus ensuring that at least 70% of original number of DaemonSet pods are available at all times during the update.\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, \"maxSurge\": { SchemaProps: spec.SchemaProps{ Description: \"The maximum number of nodes with an existing available DaemonSet pod that can have an updated DaemonSet pod during during an update. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up to a minimum of 1. Default value is 0. Example: when this is set to 30%, at most 30% of the total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their a new pod created before the old pod is marked as deleted. The update starts by launching new pods on 30% of nodes. Once an updated pod is available (Ready for at least minReadySeconds) the old DaemonSet pod on that node is marked deleted. If the old pod becomes unavailable for any reason (Ready transitions to false, is evicted, or is drained) an updated pod is immediatedly created on that node without considering surge limits. Allowing surge implies the possibility that the resources consumed by the daemonset on any given node can double if the readiness check fails, and so resource intensive daemonsets should take into account that they may cause evictions during disruption. This is beta field and enabled/disabled by DaemonSetUpdateSurge feature gate.\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"}, } } func schema_k8sio_api_apps_v1_RollingUpdateDeployment(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Spec to control the desired behavior of rolling update.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"maxUnavailable\": { SchemaProps: spec.SchemaProps{ Description: \"The maximum number of pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). Absolute number is calculated from percentage by rounding down. This can not be 0 if MaxSurge is 0. Defaults to 25%. Example: when this is set to 30%, the old ReplicaSet can be scaled down to 70% of desired pods immediately when the rolling update starts. Once new pods are ready, old ReplicaSet can be scaled down further, followed by scaling up the new ReplicaSet, ensuring that the total number of pods available at all times during the update is at least 70% of desired pods.\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, \"maxSurge\": { SchemaProps: spec.SchemaProps{ Description: \"The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. Defaults to 25%. Example: when this is set to 30%, the new ReplicaSet can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new ReplicaSet can be scaled up further, ensuring that total number of pods running at any time during the update is at most 130% of desired pods.\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"}, } } func schema_k8sio_api_apps_v1_RollingUpdateStatefulSetStrategy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RollingUpdateStatefulSetStrategy is used to communicate parameter for RollingUpdateStatefulSetStrategyType.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"partition\": { SchemaProps: spec.SchemaProps{ Description: \"Partition indicates the ordinal at which the StatefulSet should be partitioned. Default value is 0.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_k8sio_api_apps_v1_StatefulSet(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StatefulSet represents a set of pods with consistent identities. Identities are defined as:n - Network: A single stable DNS and hostname.n - Storage: As many VolumeClaims as requested.nThe StatefulSet guarantees that a given network identity will always map to the same storage identity.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec defines the desired identities of pods in this set.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1.StatefulSetSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is the current status of Pods in this StatefulSet. This data may be out of date by some window of time.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1.StatefulSetStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1.StatefulSetSpec\", \"k8s.io/api/apps/v1.StatefulSetStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_apps_v1_StatefulSetCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StatefulSetCondition describes the state of a statefulset at a certain point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of statefulset condition.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"Last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"The reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"A human readable message indicating details about the transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_apps_v1_StatefulSetList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StatefulSetList is a collection of StatefulSets.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of stateful sets.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1.StatefulSet\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1.StatefulSet\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_apps_v1_StatefulSetPersistentVolumeClaimRetentionPolicy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StatefulSetPersistentVolumeClaimRetentionPolicy describes the policy used for PVCs created from the StatefulSet VolumeClaimTemplates.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"whenDeleted\": { SchemaProps: spec.SchemaProps{ Description: \"WhenDeleted specifies what happens to PVCs created from StatefulSet VolumeClaimTemplates when the StatefulSet is deleted. The default policy of `Retain` causes PVCs to not be affected by StatefulSet deletion. The `Delete` policy causes those PVCs to be deleted.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"whenScaled\": { SchemaProps: spec.SchemaProps{ Description: \"WhenScaled specifies what happens to PVCs created from StatefulSet VolumeClaimTemplates when the StatefulSet is scaled down. The default policy of `Retain` causes PVCs to not be affected by a scaledown. The `Delete` policy causes the associated PVCs for any excess pods above the replica count to be deleted.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_apps_v1_StatefulSetSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"A StatefulSetSpec is the specification of a StatefulSet.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"replicas is the desired number of replicas of the given Template. These are replicas in the sense that they are instantiations of the same Template, but individual replicas also have a consistent identity. If unspecified, defaults to 1.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"selector is a label query over pods that should match the replica count. It must match the pod template's labels. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"template\": { SchemaProps: spec.SchemaProps{ Description: \"template is the object that describes the pod that will be created if insufficient replicas are detected. Each pod stamped out by the StatefulSet will fulfill this Template, but have a unique identity from the rest of the StatefulSet.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodTemplateSpec\"), }, }, \"volumeClaimTemplates\": { SchemaProps: spec.SchemaProps{ Description: \"volumeClaimTemplates is a list of claims that pods are allowed to reference. The StatefulSet controller is responsible for mapping network identities to claims in a way that maintains the identity of a pod. Every claim in this list must have at least one matching (by name) volumeMount in one container in the template. A claim in this list takes precedence over any volumes in the template, with the same name.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.PersistentVolumeClaim\"), }, }, }, }, }, \"serviceName\": { SchemaProps: spec.SchemaProps{ Description: \"serviceName is the name of the service that governs this StatefulSet. This service must exist before the StatefulSet, and is responsible for the network identity of the set. Pods get DNS/hostnames that follow the pattern: pod-specific-string.serviceName.default.svc.cluster.local where \"pod-specific-string\" is managed by the StatefulSet controller.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"podManagementPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"podManagementPolicy controls how pods are created during initial scale up, when replacing pods on nodes, or when scaling down. The default policy is `OrderedReady`, where pods are created in increasing order (pod-0, then pod-1, etc) and the controller will wait until each pod is ready before continuing. When scaling down, the pods are removed in the opposite order. The alternative policy is `Parallel` which will create pods in parallel to match the desired scale without waiting, and on scale down will delete all pods at once.nnPossible enum values:n - `\"OrderedReady\"` will create pods in strictly increasing order on scale up and strictly decreasing order on scale down, progressing only when the previous pod is ready or terminated. At most one pod will be changed at any time.n - `\"Parallel\"` will create and delete pods as soon as the stateful set replica count is changed, and will not wait for pods to be ready or complete termination.\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"OrderedReady\", \"Parallel\"}}, }, \"updateStrategy\": { SchemaProps: spec.SchemaProps{ Description: \"updateStrategy indicates the StatefulSetUpdateStrategy that will be employed to update Pods in the StatefulSet when a revision is made to Template.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1.StatefulSetUpdateStrategy\"), }, }, \"revisionHistoryLimit\": { SchemaProps: spec.SchemaProps{ Description: \"revisionHistoryLimit is the maximum number of revisions that will be maintained in the StatefulSet's revision history. The revision history consists of all revisions not represented by a currently applied StatefulSetSpec version. The default value is 10.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"minReadySeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Minimum number of seconds for which a newly created pod should be ready without any of its container crashing for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready) This is an alpha field and requires enabling StatefulSetMinReadySeconds feature gate.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"persistentVolumeClaimRetentionPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"persistentVolumeClaimRetentionPolicy describes the lifecycle of persistent volume claims created from volumeClaimTemplates. By default, all persistent volume claims are created as needed and retained until manually deleted. This policy allows the lifecycle to be altered, for example by deleting persistent volume claims when their stateful set is deleted, or when their pod is scaled down. This requires the StatefulSetAutoDeletePVC feature gate to be enabled, which is alpha.  +optional\", Ref:         ref(\"k8s.io/api/apps/v1.StatefulSetPersistentVolumeClaimRetentionPolicy\"), }, }, }, Required: []string{\"selector\", \"template\", \"serviceName\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1.StatefulSetPersistentVolumeClaimRetentionPolicy\", \"k8s.io/api/apps/v1.StatefulSetUpdateStrategy\", \"k8s.io/api/core/v1.PersistentVolumeClaim\", \"k8s.io/api/core/v1.PodTemplateSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_apps_v1_StatefulSetStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StatefulSetStatus represents the current state of a StatefulSet.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"observedGeneration is the most recent generation observed for this StatefulSet. It corresponds to the StatefulSet's generation, which is updated on mutation by the API Server.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"replicas is the number of Pods created by the StatefulSet controller.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"readyReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"readyReplicas is the number of pods created for this StatefulSet with a Ready Condition.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"currentReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"currentReplicas is the number of Pods created by the StatefulSet controller from the StatefulSet version indicated by currentRevision.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"updatedReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"updatedReplicas is the number of Pods created by the StatefulSet controller from the StatefulSet version indicated by updateRevision.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"currentRevision\": { SchemaProps: spec.SchemaProps{ Description: \"currentRevision, if not empty, indicates the version of the StatefulSet used to generate Pods in the sequence [0,currentReplicas).\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"updateRevision\": { SchemaProps: spec.SchemaProps{ Description: \"updateRevision, if not empty, indicates the version of the StatefulSet used to generate Pods in the sequence [replicas-updatedReplicas,replicas)\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"collisionCount\": { SchemaProps: spec.SchemaProps{ Description: \"collisionCount is the count of hash collisions for the StatefulSet. The StatefulSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Represents the latest available observations of a statefulset's current state.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1.StatefulSetCondition\"), }, }, }, }, }, \"availableReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of available pods (ready for at least minReadySeconds) targeted by this statefulset. This is a beta field and enabled/disabled by StatefulSetMinReadySeconds feature gate.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"replicas\", \"availableReplicas\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1.StatefulSetCondition\"}, } } func schema_k8sio_api_apps_v1_StatefulSetUpdateStrategy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StatefulSetUpdateStrategy indicates the strategy that the StatefulSet controller will use to perform updates. It includes any additional parameters necessary to perform the update for the indicated strategy.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type indicates the type of the StatefulSetUpdateStrategy. Default is RollingUpdate.nnPossible enum values:n - `\"OnDelete\"` triggers the legacy behavior. Version tracking and ordered rolling restarts are disabled. Pods are recreated from the StatefulSetSpec when they are manually deleted. When a scale operation is performed with this strategy,specification version indicated by the StatefulSet's currentRevision.n - `\"RollingUpdate\"` indicates that update will be applied to all Pods in the StatefulSet with respect to the StatefulSet ordering constraints. When a scale operation is performed with this strategy, new Pods will be created from the specification version indicated by the StatefulSet's updateRevision.\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"OnDelete\", \"RollingUpdate\"}}, }, \"rollingUpdate\": { SchemaProps: spec.SchemaProps{ Description: \"RollingUpdate is used to communicate parameters when Type is RollingUpdateStatefulSetStrategyType.\", Ref:         ref(\"k8s.io/api/apps/v1.RollingUpdateStatefulSetStrategy\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1.RollingUpdateStatefulSetStrategy\"}, } } func schema_k8sio_api_apps_v1beta1_ControllerRevision(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED - This group version of ControllerRevision is deprecated by apps/v1beta2/ControllerRevision. See the release notes for more information. ControllerRevision implements an immutable snapshot of state data. Clients are responsible for serializing and deserializing the objects that contain their internal state. Once a ControllerRevision has been successfully created, it can not be updated. The API Server will fail validation of all requests that attempt to mutate the Data field. ControllerRevisions may, however, be deleted. Note that, due to its use by both the DaemonSet and StatefulSet controllers for update and rollback, this object is beta. However, it may be subject to name and representation changes in future releases, and clients should not depend on its stability. It is primarily for internal use by controllers.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"data\": { SchemaProps: spec.SchemaProps{ Description: \"Data is the serialized representation of the state.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/runtime.RawExtension\"), }, }, \"revision\": { SchemaProps: spec.SchemaProps{ Description: \"Revision indicates the revision of the state represented by Data.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int64\", }, }, }, Required: []string{\"revision\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\", \"k8s.io/apimachinery/pkg/runtime.RawExtension\"}, } } func schema_k8sio_api_apps_v1beta1_ControllerRevisionList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ControllerRevisionList is a resource containing a list of ControllerRevision objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of ControllerRevisions\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1beta1.ControllerRevision\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta1.ControllerRevision\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_apps_v1beta1_Deployment(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED - This group version of Deployment is deprecated by apps/v1beta2/Deployment. See the release notes for more information. Deployment enables declarative updates for Pods and ReplicaSets.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the desired behavior of the Deployment.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta1.DeploymentSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Most recently observed status of the Deployment.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta1.DeploymentStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta1.DeploymentSpec\", \"k8s.io/api/apps/v1beta1.DeploymentStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_apps_v1beta1_DeploymentCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentCondition describes the state of a deployment at a certain point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of deployment condition.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastUpdateTime\": { SchemaProps: spec.SchemaProps{ Description: \"The last time this condition was updated.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"Last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"The reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"A human readable message indicating details about the transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_apps_v1beta1_DeploymentList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentList is a list of Deployments.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of Deployments.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1beta1.Deployment\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta1.Deployment\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_apps_v1beta1_DeploymentRollback(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED. DeploymentRollback stores the information required to rollback a deployment.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Required: This must match the Name of a deployment.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"updatedAnnotations\": { SchemaProps: spec.SchemaProps{ Description: \"The annotations to be updated to a deployment\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"rollbackTo\": { SchemaProps: spec.SchemaProps{ Description: \"The config of this deployment rollback.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta1.RollbackConfig\"), }, }, }, Required: []string{\"name\", \"rollbackTo\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta1.RollbackConfig\"}, } } func schema_k8sio_api_apps_v1beta1_DeploymentSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentSpec is the specification of the desired behavior of the Deployment.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"Number of desired pods. This is a pointer to distinguish between explicit zero and not specified. Defaults to 1.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"Label selector for pods. Existing ReplicaSets whose pods are selected by this will be the ones affected by this deployment.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"template\": { SchemaProps: spec.SchemaProps{ Description: \"Template describes the pods that will be created.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodTemplateSpec\"), }, }, \"strategy\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-strategy\": \"retainKeys\", }, }, SchemaProps: spec.SchemaProps{ Description: \"The deployment strategy to use to replace existing pods with new ones.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta1.DeploymentStrategy\"), }, }, \"minReadySeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"revisionHistoryLimit\": { SchemaProps: spec.SchemaProps{ Description: \"The number of old ReplicaSets to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. Defaults to 2.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"paused\": { SchemaProps: spec.SchemaProps{ Description: \"Indicates that the deployment is paused.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"rollbackTo\": { SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED. The config this deployment is rolling back to. Will be cleared after rollback is done.\", Ref:         ref(\"k8s.io/api/apps/v1beta1.RollbackConfig\"), }, }, \"progressDeadlineSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"The maximum time in seconds for a deployment to make progress before it is considered to be failed. The deployment controller will continue to process failed deployments and a condition with a ProgressDeadlineExceeded reason will be surfaced in the deployment status. Note that progress will not be estimated during the time a deployment is paused. Defaults to 600s.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"template\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta1.DeploymentStrategy\", \"k8s.io/api/apps/v1beta1.RollbackConfig\", \"k8s.io/api/core/v1.PodTemplateSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_apps_v1beta1_DeploymentStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentStatus is the most recently observed status of the Deployment.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"The generation observed by the deployment controller.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of non-terminated pods targeted by this deployment (their labels match the selector).\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"updatedReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of non-terminated pods targeted by this deployment that have the desired template spec.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"readyReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"readyReplicas is the number of pods targeted by this Deployment controller with a Ready Condition.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"availableReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of available pods (ready for at least minReadySeconds) targeted by this deployment.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"unavailableReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of unavailable pods targeted by this deployment. This is the total number of pods that are still required for the deployment to have 100% available capacity. They may either be pods that are running but not yet available or pods that still have not been created.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Represents the latest available observations of a deployment's current state.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1beta1.DeploymentCondition\"), }, }, }, }, }, \"collisionCount\": { SchemaProps: spec.SchemaProps{ Description: \"Count of hash collisions for the Deployment. The Deployment controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ReplicaSet.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta1.DeploymentCondition\"}, } } func schema_k8sio_api_apps_v1beta1_DeploymentStrategy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentStrategy describes how to replace existing pods with new ones.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of deployment. Can be \"Recreate\" or \"RollingUpdate\". Default is RollingUpdate.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"rollingUpdate\": { SchemaProps: spec.SchemaProps{ Description: \"Rolling update config params. Present only if DeploymentStrategyType = RollingUpdate.\", Ref:         ref(\"k8s.io/api/apps/v1beta1.RollingUpdateDeployment\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta1.RollingUpdateDeployment\"}, } } func schema_k8sio_api_apps_v1beta1_RollbackConfig(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"revision\": { SchemaProps: spec.SchemaProps{ Description: \"The revision to rollback to. If set to 0, rollback to the last revision.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, }, }, }, } } func schema_k8sio_api_apps_v1beta1_RollingUpdateDeployment(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Spec to control the desired behavior of rolling update.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"maxUnavailable\": { SchemaProps: spec.SchemaProps{ Description: \"The maximum number of pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). Absolute number is calculated from percentage by rounding down. This can not be 0 if MaxSurge is 0. Defaults to 25%. Example: when this is set to 30%, the old ReplicaSet can be scaled down to 70% of desired pods immediately when the rolling update starts. Once new pods are ready, old ReplicaSet can be scaled down further, followed by scaling up the new ReplicaSet, ensuring that the total number of pods available at all times during the update is at least 70% of desired pods.\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, \"maxSurge\": { SchemaProps: spec.SchemaProps{ Description: \"The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. Defaults to 25%. Example: when this is set to 30%, the new ReplicaSet can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new ReplicaSet can be scaled up further, ensuring that total number of pods running at any time during the update is at most 130% of desired pods.\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"}, } } func schema_k8sio_api_apps_v1beta1_RollingUpdateStatefulSetStrategy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RollingUpdateStatefulSetStrategy is used to communicate parameter for RollingUpdateStatefulSetStrategyType.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"partition\": { SchemaProps: spec.SchemaProps{ Description: \"Partition indicates the ordinal at which the StatefulSet should be partitioned.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_k8sio_api_apps_v1beta1_Scale(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Scale represents a scaling request for a resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object metadata; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"defines the behavior of the scale. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta1.ScaleSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"current status of the scale. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status. Read-only.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta1.ScaleStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta1.ScaleSpec\", \"k8s.io/api/apps/v1beta1.ScaleStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_apps_v1beta1_ScaleSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ScaleSpec describes the attributes of a scale subresource\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"desired number of instances for the scaled object.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_k8sio_api_apps_v1beta1_ScaleStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ScaleStatus represents the current status of a scale subresource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"actual number of observed instances of the scaled object.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"label query over pods that should match the replicas count. More info: http://kubernetes.io/docs/user-guide/labels#label-selectors\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"targetSelector\": { SchemaProps: spec.SchemaProps{ Description: \"label selector for pods that should match the replicas count. This is a serializated version of both map-based and more expressive set-based selectors. This is done to avoid introspection in the clients. The string will be in the same format as the query-param syntax. If the target type only supports map-based selectors, both this field and map-based selector field are populated. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"replicas\"}, }, }, } } func schema_k8sio_api_apps_v1beta1_StatefulSet(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED - This group version of StatefulSet is deprecated by apps/v1beta2/StatefulSet. See the release notes for more information. StatefulSet represents a set of pods with consistent identities. Identities are defined as:n - Network: A single stable DNS and hostname.n - Storage: As many VolumeClaims as requested.nThe StatefulSet guarantees that a given network identity will always map to the same storage identity.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec defines the desired identities of pods in this set.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta1.StatefulSetSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is the current status of Pods in this StatefulSet. This data may be out of date by some window of time.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta1.StatefulSetStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta1.StatefulSetSpec\", \"k8s.io/api/apps/v1beta1.StatefulSetStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_apps_v1beta1_StatefulSetCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StatefulSetCondition describes the state of a statefulset at a certain point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of statefulset condition.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"Last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"The reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"A human readable message indicating details about the transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_apps_v1beta1_StatefulSetList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StatefulSetList is a collection of StatefulSets.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1beta1.StatefulSet\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta1.StatefulSet\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_apps_v1beta1_StatefulSetPersistentVolumeClaimRetentionPolicy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StatefulSetPersistentVolumeClaimRetentionPolicy describes the policy used for PVCs created from the StatefulSet VolumeClaimTemplates.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"whenDeleted\": { SchemaProps: spec.SchemaProps{ Description: \"WhenDeleted specifies what happens to PVCs created from StatefulSet VolumeClaimTemplates when the StatefulSet is deleted. The default policy of `Retain` causes PVCs to not be affected by StatefulSet deletion. The `Delete` policy causes those PVCs to be deleted.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"whenScaled\": { SchemaProps: spec.SchemaProps{ Description: \"WhenScaled specifies what happens to PVCs created from StatefulSet VolumeClaimTemplates when the StatefulSet is scaled down. The default policy of `Retain` causes PVCs to not be affected by a scaledown. The `Delete` policy causes the associated PVCs for any excess pods above the replica count to be deleted.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_apps_v1beta1_StatefulSetSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"A StatefulSetSpec is the specification of a StatefulSet.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"replicas is the desired number of replicas of the given Template. These are replicas in the sense that they are instantiations of the same Template, but individual replicas also have a consistent identity. If unspecified, defaults to 1.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"selector is a label query over pods that should match the replica count. If empty, defaulted to labels on the pod template. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"template\": { SchemaProps: spec.SchemaProps{ Description: \"template is the object that describes the pod that will be created if insufficient replicas are detected. Each pod stamped out by the StatefulSet will fulfill this Template, but have a unique identity from the rest of the StatefulSet.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodTemplateSpec\"), }, }, \"volumeClaimTemplates\": { SchemaProps: spec.SchemaProps{ Description: \"volumeClaimTemplates is a list of claims that pods are allowed to reference. The StatefulSet controller is responsible for mapping network identities to claims in a way that maintains the identity of a pod. Every claim in this list must have at least one matching (by name) volumeMount in one container in the template. A claim in this list takes precedence over any volumes in the template, with the same name.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.PersistentVolumeClaim\"), }, }, }, }, }, \"serviceName\": { SchemaProps: spec.SchemaProps{ Description: \"serviceName is the name of the service that governs this StatefulSet. This service must exist before the StatefulSet, and is responsible for the network identity of the set. Pods get DNS/hostnames that follow the pattern: pod-specific-string.serviceName.default.svc.cluster.local where \"pod-specific-string\" is managed by the StatefulSet controller.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"podManagementPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"podManagementPolicy controls how pods are created during initial scale up, when replacing pods on nodes, or when scaling down. The default policy is `OrderedReady`, where pods are created in increasing order (pod-0, then pod-1, etc) and the controller will wait until each pod is ready before continuing. When scaling down, the pods are removed in the opposite order. The alternative policy is `Parallel` which will create pods in parallel to match the desired scale without waiting, and on scale down will delete all pods at once.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"updateStrategy\": { SchemaProps: spec.SchemaProps{ Description: \"updateStrategy indicates the StatefulSetUpdateStrategy that will be employed to update Pods in the StatefulSet when a revision is made to Template.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta1.StatefulSetUpdateStrategy\"), }, }, \"revisionHistoryLimit\": { SchemaProps: spec.SchemaProps{ Description: \"revisionHistoryLimit is the maximum number of revisions that will be maintained in the StatefulSet's revision history. The revision history consists of all revisions not represented by a currently applied StatefulSetSpec version. The default value is 10.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"minReadySeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Minimum number of seconds for which a newly created pod should be ready without any of its container crashing for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready) This is an alpha field and requires enabling StatefulSetMinReadySeconds feature gate.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"persistentVolumeClaimRetentionPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"PersistentVolumeClaimRetentionPolicy describes the policy used for PVCs created from the StatefulSet VolumeClaimTemplates. This requires the StatefulSetAutoDeletePVC feature gate to be enabled, which is alpha.\", Ref:         ref(\"k8s.io/api/apps/v1beta1.StatefulSetPersistentVolumeClaimRetentionPolicy\"), }, }, }, Required: []string{\"template\", \"serviceName\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta1.StatefulSetPersistentVolumeClaimRetentionPolicy\", \"k8s.io/api/apps/v1beta1.StatefulSetUpdateStrategy\", \"k8s.io/api/core/v1.PersistentVolumeClaim\", \"k8s.io/api/core/v1.PodTemplateSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_apps_v1beta1_StatefulSetStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StatefulSetStatus represents the current state of a StatefulSet.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"observedGeneration is the most recent generation observed for this StatefulSet. It corresponds to the StatefulSet's generation, which is updated on mutation by the API Server.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"replicas is the number of Pods created by the StatefulSet controller.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"readyReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"readyReplicas is the number of pods created by this StatefulSet controller with a Ready Condition.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"currentReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"currentReplicas is the number of Pods created by the StatefulSet controller from the StatefulSet version indicated by currentRevision.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"updatedReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"updatedReplicas is the number of Pods created by the StatefulSet controller from the StatefulSet version indicated by updateRevision.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"currentRevision\": { SchemaProps: spec.SchemaProps{ Description: \"currentRevision, if not empty, indicates the version of the StatefulSet used to generate Pods in the sequence [0,currentReplicas).\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"updateRevision\": { SchemaProps: spec.SchemaProps{ Description: \"updateRevision, if not empty, indicates the version of the StatefulSet used to generate Pods in the sequence [replicas-updatedReplicas,replicas)\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"collisionCount\": { SchemaProps: spec.SchemaProps{ Description: \"collisionCount is the count of hash collisions for the StatefulSet. The StatefulSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Represents the latest available observations of a statefulset's current state.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1beta1.StatefulSetCondition\"), }, }, }, }, }, \"availableReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of available pods (ready for at least minReadySeconds) targeted by this StatefulSet. This is a beta field and enabled/disabled by StatefulSetMinReadySeconds feature gate.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"replicas\", \"availableReplicas\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta1.StatefulSetCondition\"}, } } func schema_k8sio_api_apps_v1beta1_StatefulSetUpdateStrategy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StatefulSetUpdateStrategy indicates the strategy that the StatefulSet controller will use to perform updates. It includes any additional parameters necessary to perform the update for the indicated strategy.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type indicates the type of the StatefulSetUpdateStrategy.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"rollingUpdate\": { SchemaProps: spec.SchemaProps{ Description: \"RollingUpdate is used to communicate parameters when Type is RollingUpdateStatefulSetStrategyType.\", Ref:         ref(\"k8s.io/api/apps/v1beta1.RollingUpdateStatefulSetStrategy\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta1.RollingUpdateStatefulSetStrategy\"}, } } func schema_k8sio_api_apps_v1beta2_ControllerRevision(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED - This group version of ControllerRevision is deprecated by apps/v1/ControllerRevision. See the release notes for more information. ControllerRevision implements an immutable snapshot of state data. Clients are responsible for serializing and deserializing the objects that contain their internal state. Once a ControllerRevision has been successfully created, it can not be updated. The API Server will fail validation of all requests that attempt to mutate the Data field. ControllerRevisions may, however, be deleted. Note that, due to its use by both the DaemonSet and StatefulSet controllers for update and rollback, this object is beta. However, it may be subject to name and representation changes in future releases, and clients should not depend on its stability. It is primarily for internal use by controllers.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"data\": { SchemaProps: spec.SchemaProps{ Description: \"Data is the serialized representation of the state.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/runtime.RawExtension\"), }, }, \"revision\": { SchemaProps: spec.SchemaProps{ Description: \"Revision indicates the revision of the state represented by Data.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int64\", }, }, }, Required: []string{\"revision\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\", \"k8s.io/apimachinery/pkg/runtime.RawExtension\"}, } } func schema_k8sio_api_apps_v1beta2_ControllerRevisionList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ControllerRevisionList is a resource containing a list of ControllerRevision objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of ControllerRevisions\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1beta2.ControllerRevision\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.ControllerRevision\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_apps_v1beta2_DaemonSet(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED - This group version of DaemonSet is deprecated by apps/v1/DaemonSet. See the release notes for more information. DaemonSet represents the configuration of a daemon set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"The desired behavior of this daemon set. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta2.DaemonSetSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"The current status of this daemon set. This data may be out of date by some window of time. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta2.DaemonSetStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.DaemonSetSpec\", \"k8s.io/api/apps/v1beta2.DaemonSetStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_apps_v1beta2_DaemonSetCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DaemonSetCondition describes the state of a DaemonSet at a certain point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of DaemonSet condition.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"Last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"The reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"A human readable message indicating details about the transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_apps_v1beta2_DaemonSetList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DaemonSetList is a collection of daemon sets.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"A list of daemon sets.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1beta2.DaemonSet\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.DaemonSet\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_apps_v1beta2_DaemonSetSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DaemonSetSpec is the specification of a daemon set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"A label query over pods that are managed by the daemon set. Must match in order to be controlled. It must match the pod template's labels. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"template\": { SchemaProps: spec.SchemaProps{ Description: \"An object that describes the pod that will be created. The DaemonSet will create exactly one copy of this pod on every node that matches the template's node selector (or on every node if no node selector is specified). More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodTemplateSpec\"), }, }, \"updateStrategy\": { SchemaProps: spec.SchemaProps{ Description: \"An update strategy to replace existing DaemonSet pods with new pods.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta2.DaemonSetUpdateStrategy\"), }, }, \"minReadySeconds\": { SchemaProps: spec.SchemaProps{ Description: \"The minimum number of seconds for which a newly created DaemonSet pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready).\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"revisionHistoryLimit\": { SchemaProps: spec.SchemaProps{ Description: \"The number of old history to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. Defaults to 10.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"selector\", \"template\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.DaemonSetUpdateStrategy\", \"k8s.io/api/core/v1.PodTemplateSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_apps_v1beta2_DaemonSetStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DaemonSetStatus represents the current status of a daemon set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"currentNumberScheduled\": { SchemaProps: spec.SchemaProps{ Description: \"The number of nodes that are running at least 1 daemon pod and are supposed to run the daemon pod. More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"numberMisscheduled\": { SchemaProps: spec.SchemaProps{ Description: \"The number of nodes that are running the daemon pod, but are not supposed to run the daemon pod. More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"desiredNumberScheduled\": { SchemaProps: spec.SchemaProps{ Description: \"The total number of nodes that should be running the daemon pod (including nodes correctly running the daemon pod). More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"numberReady\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of nodes that should be running the daemon pod and have one or more of the daemon pod running with a Ready Condition by passing the readinessProbe.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"The most recent generation observed by the daemon set controller.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"updatedNumberScheduled\": { SchemaProps: spec.SchemaProps{ Description: \"The total number of nodes that are running updated daemon pod\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"numberAvailable\": { SchemaProps: spec.SchemaProps{ Description: \"The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and available (ready for at least spec.minReadySeconds)\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"numberUnavailable\": { SchemaProps: spec.SchemaProps{ Description: \"The number of nodes that should be running the daemon pod and have none of the daemon pod running and available (ready for at least spec.minReadySeconds)\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"collisionCount\": { SchemaProps: spec.SchemaProps{ Description: \"Count of hash collisions for the DaemonSet. The DaemonSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Represents the latest available observations of a DaemonSet's current state.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1beta2.DaemonSetCondition\"), }, }, }, }, }, }, Required: []string{\"currentNumberScheduled\", \"numberMisscheduled\", \"desiredNumberScheduled\", \"numberReady\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.DaemonSetCondition\"}, } } func schema_k8sio_api_apps_v1beta2_DaemonSetUpdateStrategy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DaemonSetUpdateStrategy is a struct used to control the update strategy for a DaemonSet.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of daemon set update. Can be \"RollingUpdate\" or \"OnDelete\". Default is RollingUpdate.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"rollingUpdate\": { SchemaProps: spec.SchemaProps{ Description: \"Rolling update config params. Present only if type = \"RollingUpdate\".\", Ref:         ref(\"k8s.io/api/apps/v1beta2.RollingUpdateDaemonSet\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.RollingUpdateDaemonSet\"}, } } func schema_k8sio_api_apps_v1beta2_Deployment(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED - This group version of Deployment is deprecated by apps/v1/Deployment. See the release notes for more information. Deployment enables declarative updates for Pods and ReplicaSets.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the desired behavior of the Deployment.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta2.DeploymentSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Most recently observed status of the Deployment.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta2.DeploymentStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.DeploymentSpec\", \"k8s.io/api/apps/v1beta2.DeploymentStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_apps_v1beta2_DeploymentCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentCondition describes the state of a deployment at a certain point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of deployment condition.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastUpdateTime\": { SchemaProps: spec.SchemaProps{ Description: \"The last time this condition was updated.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"Last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"The reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"A human readable message indicating details about the transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_apps_v1beta2_DeploymentList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentList is a list of Deployments.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of Deployments.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1beta2.Deployment\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.Deployment\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_apps_v1beta2_DeploymentSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentSpec is the specification of the desired behavior of the Deployment.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"Number of desired pods. This is a pointer to distinguish between explicit zero and not specified. Defaults to 1.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"Label selector for pods. Existing ReplicaSets whose pods are selected by this will be the ones affected by this deployment. It must match the pod template's labels.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"template\": { SchemaProps: spec.SchemaProps{ Description: \"Template describes the pods that will be created.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodTemplateSpec\"), }, }, \"strategy\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-strategy\": \"retainKeys\", }, }, SchemaProps: spec.SchemaProps{ Description: \"The deployment strategy to use to replace existing pods with new ones.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta2.DeploymentStrategy\"), }, }, \"minReadySeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"revisionHistoryLimit\": { SchemaProps: spec.SchemaProps{ Description: \"The number of old ReplicaSets to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. Defaults to 10.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"paused\": { SchemaProps: spec.SchemaProps{ Description: \"Indicates that the deployment is paused.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"progressDeadlineSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"The maximum time in seconds for a deployment to make progress before it is considered to be failed. The deployment controller will continue to process failed deployments and a condition with a ProgressDeadlineExceeded reason will be surfaced in the deployment status. Note that progress will not be estimated during the time a deployment is paused. Defaults to 600s.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"selector\", \"template\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.DeploymentStrategy\", \"k8s.io/api/core/v1.PodTemplateSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_apps_v1beta2_DeploymentStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentStatus is the most recently observed status of the Deployment.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"The generation observed by the deployment controller.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of non-terminated pods targeted by this deployment (their labels match the selector).\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"updatedReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of non-terminated pods targeted by this deployment that have the desired template spec.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"readyReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"readyReplicas is the number of pods targeted by this Deployment controller with a Ready Condition.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"availableReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of available pods (ready for at least minReadySeconds) targeted by this deployment.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"unavailableReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of unavailable pods targeted by this deployment. This is the total number of pods that are still required for the deployment to have 100% available capacity. They may either be pods that are running but not yet available or pods that still have not been created.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Represents the latest available observations of a deployment's current state.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1beta2.DeploymentCondition\"), }, }, }, }, }, \"collisionCount\": { SchemaProps: spec.SchemaProps{ Description: \"Count of hash collisions for the Deployment. The Deployment controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ReplicaSet.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.DeploymentCondition\"}, } } func schema_k8sio_api_apps_v1beta2_DeploymentStrategy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentStrategy describes how to replace existing pods with new ones.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of deployment. Can be \"Recreate\" or \"RollingUpdate\". Default is RollingUpdate.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"rollingUpdate\": { SchemaProps: spec.SchemaProps{ Description: \"Rolling update config params. Present only if DeploymentStrategyType = RollingUpdate.\", Ref:         ref(\"k8s.io/api/apps/v1beta2.RollingUpdateDeployment\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.RollingUpdateDeployment\"}, } } func schema_k8sio_api_apps_v1beta2_ReplicaSet(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED - This group version of ReplicaSet is deprecated by apps/v1/ReplicaSet. See the release notes for more information. ReplicaSet ensures that a specified number of pod replicas are running at any given time.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"If the Labels of a ReplicaSet are empty, they are defaulted to be the same as the Pod(s) that the ReplicaSet manages. Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec defines the specification of the desired behavior of the ReplicaSet. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta2.ReplicaSetSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is the most recently observed status of the ReplicaSet. This data may be out of date by some window of time. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta2.ReplicaSetStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.ReplicaSetSpec\", \"k8s.io/api/apps/v1beta2.ReplicaSetStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_apps_v1beta2_ReplicaSetCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicaSetCondition describes the state of a replica set at a certain point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of replica set condition.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"The last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"The reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"A human readable message indicating details about the transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_apps_v1beta2_ReplicaSetList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicaSetList is a collection of ReplicaSets.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of ReplicaSets. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1beta2.ReplicaSet\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.ReplicaSet\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_apps_v1beta2_ReplicaSetSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicaSetSpec is the specification of a ReplicaSet.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"Replicas is the number of desired replicas. This is a pointer to distinguish between explicit zero and unspecified. Defaults to 1. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/#what-is-a-replicationcontroller\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"minReadySeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"Selector is a label query over pods that should match the replica count. Label keys and values that must match in order to be controlled by this replica set. It must match the pod template's labels. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"template\": { SchemaProps: spec.SchemaProps{ Description: \"Template is the object that describes the pod that will be created if insufficient replicas are detected. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodTemplateSpec\"), }, }, }, Required: []string{\"selector\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PodTemplateSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_apps_v1beta2_ReplicaSetStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicaSetStatus represents the current status of a ReplicaSet.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"Replicas is the most recently oberved number of replicas. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/#what-is-a-replicationcontroller\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"fullyLabeledReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"The number of pods that have labels matching the labels of the pod template of the replicaset.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"readyReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"readyReplicas is the number of pods targeted by this ReplicaSet controller with a Ready Condition.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"availableReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"The number of available replicas (ready for at least minReadySeconds) for this replica set.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"ObservedGeneration reflects the generation of the most recently observed ReplicaSet.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Represents the latest available observations of a replica set's current state.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1beta2.ReplicaSetCondition\"), }, }, }, }, }, }, Required: []string{\"replicas\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.ReplicaSetCondition\"}, } } func schema_k8sio_api_apps_v1beta2_RollingUpdateDaemonSet(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Spec to control the desired behavior of daemon set rolling update.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"maxUnavailable\": { SchemaProps: spec.SchemaProps{ Description: \"The maximum number of DaemonSet pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of total number of DaemonSet pods at the start of the update (ex: 10%). Absolute number is calculated from percentage by rounding up. This cannot be 0 if MaxSurge is 0 Default value is 1. Example: when this is set to 30%, at most 30% of the total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their pods stopped for an update at any given time. The update starts by stopping at most 30% of those DaemonSet pods and then brings up new DaemonSet pods in their place. Once the new pods are available, it then proceeds onto other DaemonSet pods, thus ensuring that at least 70% of original number of DaemonSet pods are available at all times during the update.\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, \"maxSurge\": { SchemaProps: spec.SchemaProps{ Description: \"The maximum number of nodes with an existing available DaemonSet pod that can have an updated DaemonSet pod during during an update. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up to a minimum of 1. Default value is 0. Example: when this is set to 30%, at most 30% of the total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their a new pod created before the old pod is marked as deleted. The update starts by launching new pods on 30% of nodes. Once an updated pod is available (Ready for at least minReadySeconds) the old DaemonSet pod on that node is marked deleted. If the old pod becomes unavailable for any reason (Ready transitions to false, is evicted, or is drained) an updated pod is immediatedly created on that node without considering surge limits. Allowing surge implies the possibility that the resources consumed by the daemonset on any given node can double if the readiness check fails, and so resource intensive daemonsets should take into account that they may cause evictions during disruption. This is beta field and enabled/disabled by DaemonSetUpdateSurge feature gate.\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"}, } } func schema_k8sio_api_apps_v1beta2_RollingUpdateDeployment(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Spec to control the desired behavior of rolling update.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"maxUnavailable\": { SchemaProps: spec.SchemaProps{ Description: \"The maximum number of pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). Absolute number is calculated from percentage by rounding down. This can not be 0 if MaxSurge is 0. Defaults to 25%. Example: when this is set to 30%, the old ReplicaSet can be scaled down to 70% of desired pods immediately when the rolling update starts. Once new pods are ready, old ReplicaSet can be scaled down further, followed by scaling up the new ReplicaSet, ensuring that the total number of pods available at all times during the update is at least 70% of desired pods.\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, \"maxSurge\": { SchemaProps: spec.SchemaProps{ Description: \"The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. Defaults to 25%. Example: when this is set to 30%, the new ReplicaSet can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new ReplicaSet can be scaled up further, ensuring that total number of pods running at any time during the update is at most 130% of desired pods.\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"}, } } func schema_k8sio_api_apps_v1beta2_RollingUpdateStatefulSetStrategy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RollingUpdateStatefulSetStrategy is used to communicate parameter for RollingUpdateStatefulSetStrategyType.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"partition\": { SchemaProps: spec.SchemaProps{ Description: \"Partition indicates the ordinal at which the StatefulSet should be partitioned. Default value is 0.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_k8sio_api_apps_v1beta2_Scale(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Scale represents a scaling request for a resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object metadata; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"defines the behavior of the scale. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta2.ScaleSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"current status of the scale. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status. Read-only.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta2.ScaleStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.ScaleSpec\", \"k8s.io/api/apps/v1beta2.ScaleStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_apps_v1beta2_ScaleSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ScaleSpec describes the attributes of a scale subresource\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"desired number of instances for the scaled object.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_k8sio_api_apps_v1beta2_ScaleStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ScaleStatus represents the current status of a scale subresource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"actual number of observed instances of the scaled object.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"selector\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"label query over pods that should match the replicas count. More info: http://kubernetes.io/docs/user-guide/labels#label-selectors\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"targetSelector\": { SchemaProps: spec.SchemaProps{ Description: \"label selector for pods that should match the replicas count. This is a serializated version of both map-based and more expressive set-based selectors. This is done to avoid introspection in the clients. The string will be in the same format as the query-param syntax. If the target type only supports map-based selectors, both this field and map-based selector field are populated. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"replicas\"}, }, }, } } func schema_k8sio_api_apps_v1beta2_StatefulSet(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED - This group version of StatefulSet is deprecated by apps/v1/StatefulSet. See the release notes for more information. StatefulSet represents a set of pods with consistent identities. Identities are defined as:n - Network: A single stable DNS and hostname.n - Storage: As many VolumeClaims as requested.nThe StatefulSet guarantees that a given network identity will always map to the same storage identity.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec defines the desired identities of pods in this set.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta2.StatefulSetSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is the current status of Pods in this StatefulSet. This data may be out of date by some window of time.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta2.StatefulSetStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.StatefulSetSpec\", \"k8s.io/api/apps/v1beta2.StatefulSetStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_apps_v1beta2_StatefulSetCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StatefulSetCondition describes the state of a statefulset at a certain point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of statefulset condition.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"Last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"The reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"A human readable message indicating details about the transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_apps_v1beta2_StatefulSetList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StatefulSetList is a collection of StatefulSets.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1beta2.StatefulSet\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.StatefulSet\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_apps_v1beta2_StatefulSetPersistentVolumeClaimRetentionPolicy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StatefulSetPersistentVolumeClaimRetentionPolicy describes the policy used for PVCs created from the StatefulSet VolumeClaimTemplates.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"whenDeleted\": { SchemaProps: spec.SchemaProps{ Description: \"WhenDeleted specifies what happens to PVCs created from StatefulSet VolumeClaimTemplates when the StatefulSet is deleted. The default policy of `Retain` causes PVCs to not be affected by StatefulSet deletion. The `Delete` policy causes those PVCs to be deleted.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"whenScaled\": { SchemaProps: spec.SchemaProps{ Description: \"WhenScaled specifies what happens to PVCs created from StatefulSet VolumeClaimTemplates when the StatefulSet is scaled down. The default policy of `Retain` causes PVCs to not be affected by a scaledown. The `Delete` policy causes the associated PVCs for any excess pods above the replica count to be deleted.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_apps_v1beta2_StatefulSetSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"A StatefulSetSpec is the specification of a StatefulSet.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"replicas is the desired number of replicas of the given Template. These are replicas in the sense that they are instantiations of the same Template, but individual replicas also have a consistent identity. If unspecified, defaults to 1.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"selector is a label query over pods that should match the replica count. It must match the pod template's labels. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"template\": { SchemaProps: spec.SchemaProps{ Description: \"template is the object that describes the pod that will be created if insufficient replicas are detected. Each pod stamped out by the StatefulSet will fulfill this Template, but have a unique identity from the rest of the StatefulSet.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodTemplateSpec\"), }, }, \"volumeClaimTemplates\": { SchemaProps: spec.SchemaProps{ Description: \"volumeClaimTemplates is a list of claims that pods are allowed to reference. The StatefulSet controller is responsible for mapping network identities to claims in a way that maintains the identity of a pod. Every claim in this list must have at least one matching (by name) volumeMount in one container in the template. A claim in this list takes precedence over any volumes in the template, with the same name.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.PersistentVolumeClaim\"), }, }, }, }, }, \"serviceName\": { SchemaProps: spec.SchemaProps{ Description: \"serviceName is the name of the service that governs this StatefulSet. This service must exist before the StatefulSet, and is responsible for the network identity of the set. Pods get DNS/hostnames that follow the pattern: pod-specific-string.serviceName.default.svc.cluster.local where \"pod-specific-string\" is managed by the StatefulSet controller.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"podManagementPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"podManagementPolicy controls how pods are created during initial scale up, when replacing pods on nodes, or when scaling down. The default policy is `OrderedReady`, where pods are created in increasing order (pod-0, then pod-1, etc) and the controller will wait until each pod is ready before continuing. When scaling down, the pods are removed in the opposite order. The alternative policy is `Parallel` which will create pods in parallel to match the desired scale without waiting, and on scale down will delete all pods at once.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"updateStrategy\": { SchemaProps: spec.SchemaProps{ Description: \"updateStrategy indicates the StatefulSetUpdateStrategy that will be employed to update Pods in the StatefulSet when a revision is made to Template.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/apps/v1beta2.StatefulSetUpdateStrategy\"), }, }, \"revisionHistoryLimit\": { SchemaProps: spec.SchemaProps{ Description: \"revisionHistoryLimit is the maximum number of revisions that will be maintained in the StatefulSet's revision history. The revision history consists of all revisions not represented by a currently applied StatefulSetSpec version. The default value is 10.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"minReadySeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Minimum number of seconds for which a newly created pod should be ready without any of its container crashing for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready) This is an alpha field and requires enabling StatefulSetMinReadySeconds feature gate.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"persistentVolumeClaimRetentionPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"PersistentVolumeClaimRetentionPolicy describes the policy used for PVCs created from the StatefulSet VolumeClaimTemplates. This requires the StatefulSetAutoDeletePVC feature gate to be enabled, which is alpha.\", Ref:         ref(\"k8s.io/api/apps/v1beta2.StatefulSetPersistentVolumeClaimRetentionPolicy\"), }, }, }, Required: []string{\"selector\", \"template\", \"serviceName\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.StatefulSetPersistentVolumeClaimRetentionPolicy\", \"k8s.io/api/apps/v1beta2.StatefulSetUpdateStrategy\", \"k8s.io/api/core/v1.PersistentVolumeClaim\", \"k8s.io/api/core/v1.PodTemplateSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_apps_v1beta2_StatefulSetStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StatefulSetStatus represents the current state of a StatefulSet.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"observedGeneration is the most recent generation observed for this StatefulSet. It corresponds to the StatefulSet's generation, which is updated on mutation by the API Server.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"replicas is the number of Pods created by the StatefulSet controller.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"readyReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"readyReplicas is the number of pods created by this StatefulSet controller with a Ready Condition.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"currentReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"currentReplicas is the number of Pods created by the StatefulSet controller from the StatefulSet version indicated by currentRevision.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"updatedReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"updatedReplicas is the number of Pods created by the StatefulSet controller from the StatefulSet version indicated by updateRevision.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"currentRevision\": { SchemaProps: spec.SchemaProps{ Description: \"currentRevision, if not empty, indicates the version of the StatefulSet used to generate Pods in the sequence [0,currentReplicas).\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"updateRevision\": { SchemaProps: spec.SchemaProps{ Description: \"updateRevision, if not empty, indicates the version of the StatefulSet used to generate Pods in the sequence [replicas-updatedReplicas,replicas)\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"collisionCount\": { SchemaProps: spec.SchemaProps{ Description: \"collisionCount is the count of hash collisions for the StatefulSet. The StatefulSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Represents the latest available observations of a statefulset's current state.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/apps/v1beta2.StatefulSetCondition\"), }, }, }, }, }, \"availableReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of available pods (ready for at least minReadySeconds) targeted by this StatefulSet. This is a beta field and enabled/disabled by StatefulSetMinReadySeconds feature gate.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"replicas\", \"availableReplicas\"}, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.StatefulSetCondition\"}, } } func schema_k8sio_api_apps_v1beta2_StatefulSetUpdateStrategy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StatefulSetUpdateStrategy indicates the strategy that the StatefulSet controller will use to perform updates. It includes any additional parameters necessary to perform the update for the indicated strategy.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type indicates the type of the StatefulSetUpdateStrategy. Default is RollingUpdate.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"rollingUpdate\": { SchemaProps: spec.SchemaProps{ Description: \"RollingUpdate is used to communicate parameters when Type is RollingUpdateStatefulSetStrategyType.\", Ref:         ref(\"k8s.io/api/apps/v1beta2.RollingUpdateStatefulSetStrategy\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/apps/v1beta2.RollingUpdateStatefulSetStrategy\"}, } } func schema_k8sio_api_authentication_v1_BoundObjectReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"BoundObjectReference is a reference to an object that a token is bound to.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind of the referent. Valid kinds are 'Pod' and 'Secret'.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"API version of the referent.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the referent.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"uid\": { SchemaProps: spec.SchemaProps{ Description: \"UID of the referent.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_authentication_v1_TokenRequest(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TokenRequest requests a token for a given service account.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec holds information about the request being evaluated\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authentication/v1.TokenRequestSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is filled in by the server and indicates whether the token can be authenticated.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authentication/v1.TokenRequestStatus\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/authentication/v1.TokenRequestSpec\", \"k8s.io/api/authentication/v1.TokenRequestStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_authentication_v1_TokenRequestSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TokenRequestSpec contains client provided parameters of a token request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"audiences\": { SchemaProps: spec.SchemaProps{ Description: \"Audiences are the intendend audiences of the token. A recipient of a token must identitfy themself with an identifier in the list of audiences of the token, and otherwise should reject the token. A token issued for multiple audiences may be used to authenticate against any of the audiences listed but implies a high degree of trust between the target audiences.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"expirationSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"ExpirationSeconds is the requested duration of validity of the request. The token issuer may return a token with a different validity duration so a client needs to check the 'expiration' field in a response.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"boundObjectRef\": { SchemaProps: spec.SchemaProps{ Description: \"BoundObjectRef is a reference to an object that the token will be bound to. The token will only be valid for as long as the bound object exists. NOTE: The API server's TokenReview endpoint will validate the BoundObjectRef, but other audiences may not. Keep ExpirationSeconds small if you want prompt revocation.\", Ref:         ref(\"k8s.io/api/authentication/v1.BoundObjectReference\"), }, }, }, Required: []string{\"audiences\"}, }, }, Dependencies: []string{ \"k8s.io/api/authentication/v1.BoundObjectReference\"}, } } func schema_k8sio_api_authentication_v1_TokenRequestStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TokenRequestStatus is the result of a token request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"token\": { SchemaProps: spec.SchemaProps{ Description: \"Token is the opaque bearer token.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"expirationTimestamp\": { SchemaProps: spec.SchemaProps{ Description: \"ExpirationTimestamp is the time of expiration of the returned token.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, }, Required: []string{\"token\", \"expirationTimestamp\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_authentication_v1_TokenReview(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TokenReview attempts to authenticate a token to a known user. Note: TokenReview requests may be cached by the webhook token authenticator plugin in the kube-apiserver.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec holds information about the request being evaluated\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authentication/v1.TokenReviewSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is filled in by the server and indicates whether the request can be authenticated.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authentication/v1.TokenReviewStatus\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/authentication/v1.TokenReviewSpec\", \"k8s.io/api/authentication/v1.TokenReviewStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_authentication_v1_TokenReviewSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TokenReviewSpec is a description of the token authentication request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"token\": { SchemaProps: spec.SchemaProps{ Description: \"Token is the opaque bearer token.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"audiences\": { SchemaProps: spec.SchemaProps{ Description: \"Audiences is a list of the identifiers that the resource server presented with the token identifies as. Audience-aware token authenticators will verify that the token was intended for at least one of the audiences in this list. If no audiences are provided, the audience will default to the audience of the Kubernetes apiserver.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, } } func schema_k8sio_api_authentication_v1_TokenReviewStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TokenReviewStatus is the result of the token authentication request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"authenticated\": { SchemaProps: spec.SchemaProps{ Description: \"Authenticated indicates that the token was associated with a known user.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"user\": { SchemaProps: spec.SchemaProps{ Description: \"User is the UserInfo associated with the provided token.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authentication/v1.UserInfo\"), }, }, \"audiences\": { SchemaProps: spec.SchemaProps{ Description: \"Audiences are audience identifiers chosen by the authenticator that are compatible with both the TokenReview and token. An identifier is any identifier in the intersection of the TokenReviewSpec audiences and the token's audiences. A client of the TokenReview API that sets the spec.audiences field should validate that a compatible audience identifier is returned in the status.audiences field to ensure that the TokenReview server is audience aware. If a TokenReview returns an empty status.audience field where status.authenticated is \"true\", the token is valid against the audience of the Kubernetes API server.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"error\": { SchemaProps: spec.SchemaProps{ Description: \"Error indicates that the token couldn't be checked\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/authentication/v1.UserInfo\"}, } } func schema_k8sio_api_authentication_v1_UserInfo(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"UserInfo holds the information about the user needed to implement the user.Info interface.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"username\": { SchemaProps: spec.SchemaProps{ Description: \"The name that uniquely identifies this user among all active users.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"uid\": { SchemaProps: spec.SchemaProps{ Description: \"A unique value that identifies this user across time. If this user is deleted and another user by the same name is added, they will have different UIDs.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"groups\": { SchemaProps: spec.SchemaProps{ Description: \"The names of groups this user is a part of.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"extra\": { SchemaProps: spec.SchemaProps{ Description: \"Any additional information provided by the authenticator.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, }, }, }, } } func schema_k8sio_api_authentication_v1beta1_TokenReview(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TokenReview attempts to authenticate a token to a known user. Note: TokenReview requests may be cached by the webhook token authenticator plugin in the kube-apiserver.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec holds information about the request being evaluated\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authentication/v1beta1.TokenReviewSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is filled in by the server and indicates whether the token can be authenticated.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authentication/v1beta1.TokenReviewStatus\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/authentication/v1beta1.TokenReviewSpec\", \"k8s.io/api/authentication/v1beta1.TokenReviewStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_authentication_v1beta1_TokenReviewSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TokenReviewSpec is a description of the token authentication request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"token\": { SchemaProps: spec.SchemaProps{ Description: \"Token is the opaque bearer token.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"audiences\": { SchemaProps: spec.SchemaProps{ Description: \"Audiences is a list of the identifiers that the resource server presented with the token identifies as. Audience-aware token authenticators will verify that the token was intended for at least one of the audiences in this list. If no audiences are provided, the audience will default to the audience of the Kubernetes apiserver.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, } } func schema_k8sio_api_authentication_v1beta1_TokenReviewStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TokenReviewStatus is the result of the token authentication request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"authenticated\": { SchemaProps: spec.SchemaProps{ Description: \"Authenticated indicates that the token was associated with a known user.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"user\": { SchemaProps: spec.SchemaProps{ Description: \"User is the UserInfo associated with the provided token.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authentication/v1beta1.UserInfo\"), }, }, \"audiences\": { SchemaProps: spec.SchemaProps{ Description: \"Audiences are audience identifiers chosen by the authenticator that are compatible with both the TokenReview and token. An identifier is any identifier in the intersection of the TokenReviewSpec audiences and the token's audiences. A client of the TokenReview API that sets the spec.audiences field should validate that a compatible audience identifier is returned in the status.audiences field to ensure that the TokenReview server is audience aware. If a TokenReview returns an empty status.audience field where status.authenticated is \"true\", the token is valid against the audience of the Kubernetes API server.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"error\": { SchemaProps: spec.SchemaProps{ Description: \"Error indicates that the token couldn't be checked\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/authentication/v1beta1.UserInfo\"}, } } func schema_k8sio_api_authentication_v1beta1_UserInfo(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"UserInfo holds the information about the user needed to implement the user.Info interface.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"username\": { SchemaProps: spec.SchemaProps{ Description: \"The name that uniquely identifies this user among all active users.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"uid\": { SchemaProps: spec.SchemaProps{ Description: \"A unique value that identifies this user across time. If this user is deleted and another user by the same name is added, they will have different UIDs.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"groups\": { SchemaProps: spec.SchemaProps{ Description: \"The names of groups this user is a part of.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"extra\": { SchemaProps: spec.SchemaProps{ Description: \"Any additional information provided by the authenticator.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, }, }, }, } } func schema_k8sio_api_authorization_v1_LocalSubjectAccessReview(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LocalSubjectAccessReview checks whether or not a user or group can perform an action in a given namespace. Having a namespace scoped resource makes it much easier to grant namespace scoped policy that includes permissions checking.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec holds information about the request being evaluated.  spec.namespace must be equal to the namespace you made the request against.  If empty, it is defaulted.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authorization/v1.SubjectAccessReviewSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is filled in by the server and indicates whether the request is allowed or not\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authorization/v1.SubjectAccessReviewStatus\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/authorization/v1.SubjectAccessReviewSpec\", \"k8s.io/api/authorization/v1.SubjectAccessReviewStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_authorization_v1_NonResourceAttributes(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NonResourceAttributes includes the authorization attributes available for non-resource requests to the Authorizer interface\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"path\": { SchemaProps: spec.SchemaProps{ Description: \"Path is the URL path of the request\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"verb\": { SchemaProps: spec.SchemaProps{ Description: \"Verb is the standard HTTP verb\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_authorization_v1_NonResourceRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NonResourceRule holds information that describes a rule for the non-resource\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"verbs\": { SchemaProps: spec.SchemaProps{ Description: \"Verb is a list of kubernetes non-resource API verbs, like: get, post, put, delete, patch, head, options.  \"*\" means all.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"nonResourceURLs\": { SchemaProps: spec.SchemaProps{ Description: \"NonResourceURLs is a set of partial urls that a user should have access to.  *s are allowed, but only as the full, final step in the path.  \"*\" means all.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"verbs\"}, }, }, } } func schema_k8sio_api_authorization_v1_ResourceAttributes(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceAttributes includes the authorization attributes available for resource requests to the Authorizer interface\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"Namespace is the namespace of the action being requested.  Currently, there is no distinction between no namespace and all namespaces \"\" (empty) is defaulted for LocalSubjectAccessReviews \"\" (empty) is empty for cluster-scoped resources \"\" (empty) means \"all\" for namespace scoped resources from a SubjectAccessReview or SelfSubjectAccessReview\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"verb\": { SchemaProps: spec.SchemaProps{ Description: \"Verb is a kubernetes resource API verb, like: get, list, watch, create, update, delete, proxy.  \"*\" means all.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"group\": { SchemaProps: spec.SchemaProps{ Description: \"Group is the API Group of the Resource.  \"*\" means all.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"version\": { SchemaProps: spec.SchemaProps{ Description: \"Version is the API Version of the Resource.  \"*\" means all.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resource\": { SchemaProps: spec.SchemaProps{ Description: \"Resource is one of the existing resource types.  \"*\" means all.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"subresource\": { SchemaProps: spec.SchemaProps{ Description: \"Subresource is one of the existing resource types.  \"\" means none.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the name of the resource being requested for a \"get\" or deleted for a \"delete\". \"\" (empty) means all.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_authorization_v1_ResourceRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceRule is the list of actions the subject is allowed to perform on resources. The list ordering isn't significant, may contain duplicates, and possibly be incomplete.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"verbs\": { SchemaProps: spec.SchemaProps{ Description: \"Verb is a list of kubernetes resource API verbs, like: get, list, watch, create, update, delete, proxy.  \"*\" means all.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"apiGroups\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroups is the name of the APIGroup that contains the resources.  If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed.  \"*\" means all.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"Resources is a list of resources this rule applies to.  \"*\" means all in the specified apiGroups.n \"*/foo\" represents the subresource 'foo' for all resources in the specified apiGroups.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resourceNames\": { SchemaProps: spec.SchemaProps{ Description: \"ResourceNames is an optional white list of names that the rule applies to.  An empty set means that everything is allowed.  \"*\" means all.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"verbs\"}, }, }, } } func schema_k8sio_api_authorization_v1_SelfSubjectAccessReview(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SelfSubjectAccessReview checks whether or the current user can perform an action.  Not filling in a spec.namespace means \"in all namespaces\".  Self is a special case, because users should always be able to check whether they can perform an action\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec holds information about the request being evaluated.  user and groups must be empty\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authorization/v1.SelfSubjectAccessReviewSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is filled in by the server and indicates whether the request is allowed or not\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authorization/v1.SubjectAccessReviewStatus\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/authorization/v1.SelfSubjectAccessReviewSpec\", \"k8s.io/api/authorization/v1.SubjectAccessReviewStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_authorization_v1_SelfSubjectAccessReviewSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SelfSubjectAccessReviewSpec is a description of the access request.  Exactly one of ResourceAuthorizationAttributes and NonResourceAuthorizationAttributes must be set\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"resourceAttributes\": { SchemaProps: spec.SchemaProps{ Description: \"ResourceAuthorizationAttributes describes information for a resource access request\", Ref:         ref(\"k8s.io/api/authorization/v1.ResourceAttributes\"), }, }, \"nonResourceAttributes\": { SchemaProps: spec.SchemaProps{ Description: \"NonResourceAttributes describes information for a non-resource access request\", Ref:         ref(\"k8s.io/api/authorization/v1.NonResourceAttributes\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/authorization/v1.NonResourceAttributes\", \"k8s.io/api/authorization/v1.ResourceAttributes\"}, } } func schema_k8sio_api_authorization_v1_SelfSubjectRulesReview(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SelfSubjectRulesReview enumerates the set of actions the current user can perform within a namespace. The returned list of actions may be incomplete depending on the server's authorization mode, and any errors experienced during the evaluation. SelfSubjectRulesReview should be used by UIs to show/hide actions, or to quickly let an end user reason about their permissions. It should NOT Be used by external systems to drive authorization decisions as this raises confused deputy, cache lifetime/revocation, and correctness concerns. SubjectAccessReview, and LocalAccessReview are the correct way to defer authorization decisions to the API server.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec holds information about the request being evaluated.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authorization/v1.SelfSubjectRulesReviewSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is filled in by the server and indicates the set of actions a user can perform.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authorization/v1.SubjectRulesReviewStatus\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/authorization/v1.SelfSubjectRulesReviewSpec\", \"k8s.io/api/authorization/v1.SubjectRulesReviewStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_authorization_v1_SelfSubjectRulesReviewSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SelfSubjectRulesReviewSpec defines the specification for SelfSubjectRulesReview.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"Namespace to evaluate rules for. Required.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_authorization_v1_SubjectAccessReview(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SubjectAccessReview checks whether or not a user or group can perform an action.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec holds information about the request being evaluated\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authorization/v1.SubjectAccessReviewSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is filled in by the server and indicates whether the request is allowed or not\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authorization/v1.SubjectAccessReviewStatus\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/authorization/v1.SubjectAccessReviewSpec\", \"k8s.io/api/authorization/v1.SubjectAccessReviewStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_authorization_v1_SubjectAccessReviewSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SubjectAccessReviewSpec is a description of the access request.  Exactly one of ResourceAuthorizationAttributes and NonResourceAuthorizationAttributes must be set\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"resourceAttributes\": { SchemaProps: spec.SchemaProps{ Description: \"ResourceAuthorizationAttributes describes information for a resource access request\", Ref:         ref(\"k8s.io/api/authorization/v1.ResourceAttributes\"), }, }, \"nonResourceAttributes\": { SchemaProps: spec.SchemaProps{ Description: \"NonResourceAttributes describes information for a non-resource access request\", Ref:         ref(\"k8s.io/api/authorization/v1.NonResourceAttributes\"), }, }, \"user\": { SchemaProps: spec.SchemaProps{ Description: \"User is the user you're testing for. If you specify \"User\" but not \"Groups\", then is it interpreted as \"What if User were not a member of any groups\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"groups\": { SchemaProps: spec.SchemaProps{ Description: \"Groups is the groups you're testing for.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"extra\": { SchemaProps: spec.SchemaProps{ Description: \"Extra corresponds to the user.Info.GetExtra() method from the authenticator.  Since that is input to the authorizer it needs a reflection here.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, \"uid\": { SchemaProps: spec.SchemaProps{ Description: \"UID information about the requesting user.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/authorization/v1.NonResourceAttributes\", \"k8s.io/api/authorization/v1.ResourceAttributes\"}, } } func schema_k8sio_api_authorization_v1_SubjectAccessReviewStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SubjectAccessReviewStatus\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"allowed\": { SchemaProps: spec.SchemaProps{ Description: \"Allowed is required. True if the action would be allowed, false otherwise.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"denied\": { SchemaProps: spec.SchemaProps{ Description: \"Denied is optional. True if the action would be denied, otherwise false. If both allowed is false and denied is false, then the authorizer has no opinion on whether to authorize the action. Denied may not be true if Allowed is true.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"Reason is optional.  It indicates why a request was allowed or denied.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"evaluationError\": { SchemaProps: spec.SchemaProps{ Description: \"EvaluationError is an indication that some error occurred during the authorization check. It is entirely possible to get an error and be able to continue determine authorization status in spite of it. For instance, RBAC can be missing a role, but enough roles are still present and bound to reason about the request.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"allowed\"}, }, }, } } func schema_k8sio_api_authorization_v1_SubjectRulesReviewStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SubjectRulesReviewStatus contains the result of a rules check. This check can be incomplete depending on the set of authorizers the server is configured with and any errors experienced during evaluation. Because authorization rules are additive, if a rule appears in a list it's safe to assume the subject has that permission, even if that list is incomplete.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"resourceRules\": { SchemaProps: spec.SchemaProps{ Description: \"ResourceRules is the list of actions the subject is allowed to perform on resources. The list ordering isn't significant, may contain duplicates, and possibly be incomplete.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/authorization/v1.ResourceRule\"), }, }, }, }, }, \"nonResourceRules\": { SchemaProps: spec.SchemaProps{ Description: \"NonResourceRules is the list of actions the subject is allowed to perform on non-resources. The list ordering isn't significant, may contain duplicates, and possibly be incomplete.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/authorization/v1.NonResourceRule\"), }, }, }, }, }, \"incomplete\": { SchemaProps: spec.SchemaProps{ Description: \"Incomplete is true when the rules returned by this call are incomplete. This is most commonly encountered when an authorizer, such as an external authorizer, doesn't support rules evaluation.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"evaluationError\": { SchemaProps: spec.SchemaProps{ Description: \"EvaluationError can appear in combination with Rules. It indicates an error occurred during rule evaluation, such as an authorizer that doesn't support rule evaluation, and that ResourceRules and/or NonResourceRules may be incomplete.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"resourceRules\", \"nonResourceRules\", \"incomplete\"}, }, }, Dependencies: []string{ \"k8s.io/api/authorization/v1.NonResourceRule\", \"k8s.io/api/authorization/v1.ResourceRule\"}, } } func schema_k8sio_api_authorization_v1beta1_LocalSubjectAccessReview(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LocalSubjectAccessReview checks whether or not a user or group can perform an action in a given namespace. Having a namespace scoped resource makes it much easier to grant namespace scoped policy that includes permissions checking.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec holds information about the request being evaluated.  spec.namespace must be equal to the namespace you made the request against.  If empty, it is defaulted.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authorization/v1beta1.SubjectAccessReviewSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is filled in by the server and indicates whether the request is allowed or not\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authorization/v1beta1.SubjectAccessReviewStatus\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/authorization/v1beta1.SubjectAccessReviewSpec\", \"k8s.io/api/authorization/v1beta1.SubjectAccessReviewStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_authorization_v1beta1_NonResourceAttributes(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NonResourceAttributes includes the authorization attributes available for non-resource requests to the Authorizer interface\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"path\": { SchemaProps: spec.SchemaProps{ Description: \"Path is the URL path of the request\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"verb\": { SchemaProps: spec.SchemaProps{ Description: \"Verb is the standard HTTP verb\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_authorization_v1beta1_NonResourceRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NonResourceRule holds information that describes a rule for the non-resource\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"verbs\": { SchemaProps: spec.SchemaProps{ Description: \"Verb is a list of kubernetes non-resource API verbs, like: get, post, put, delete, patch, head, options.  \"*\" means all.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"nonResourceURLs\": { SchemaProps: spec.SchemaProps{ Description: \"NonResourceURLs is a set of partial urls that a user should have access to.  *s are allowed, but only as the full, final step in the path.  \"*\" means all.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"verbs\"}, }, }, } } func schema_k8sio_api_authorization_v1beta1_ResourceAttributes(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceAttributes includes the authorization attributes available for resource requests to the Authorizer interface\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"Namespace is the namespace of the action being requested.  Currently, there is no distinction between no namespace and all namespaces \"\" (empty) is defaulted for LocalSubjectAccessReviews \"\" (empty) is empty for cluster-scoped resources \"\" (empty) means \"all\" for namespace scoped resources from a SubjectAccessReview or SelfSubjectAccessReview\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"verb\": { SchemaProps: spec.SchemaProps{ Description: \"Verb is a kubernetes resource API verb, like: get, list, watch, create, update, delete, proxy.  \"*\" means all.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"group\": { SchemaProps: spec.SchemaProps{ Description: \"Group is the API Group of the Resource.  \"*\" means all.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"version\": { SchemaProps: spec.SchemaProps{ Description: \"Version is the API Version of the Resource.  \"*\" means all.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resource\": { SchemaProps: spec.SchemaProps{ Description: \"Resource is one of the existing resource types.  \"*\" means all.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"subresource\": { SchemaProps: spec.SchemaProps{ Description: \"Subresource is one of the existing resource types.  \"\" means none.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the name of the resource being requested for a \"get\" or deleted for a \"delete\". \"\" (empty) means all.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_authorization_v1beta1_ResourceRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceRule is the list of actions the subject is allowed to perform on resources. The list ordering isn't significant, may contain duplicates, and possibly be incomplete.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"verbs\": { SchemaProps: spec.SchemaProps{ Description: \"Verb is a list of kubernetes resource API verbs, like: get, list, watch, create, update, delete, proxy.  \"*\" means all.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"apiGroups\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroups is the name of the APIGroup that contains the resources.  If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed.  \"*\" means all.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"Resources is a list of resources this rule applies to.  \"*\" means all in the specified apiGroups.n \"*/foo\" represents the subresource 'foo' for all resources in the specified apiGroups.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resourceNames\": { SchemaProps: spec.SchemaProps{ Description: \"ResourceNames is an optional white list of names that the rule applies to.  An empty set means that everything is allowed.  \"*\" means all.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"verbs\"}, }, }, } } func schema_k8sio_api_authorization_v1beta1_SelfSubjectAccessReview(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SelfSubjectAccessReview checks whether or the current user can perform an action.  Not filling in a spec.namespace means \"in all namespaces\".  Self is a special case, because users should always be able to check whether they can perform an action\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec holds information about the request being evaluated.  user and groups must be empty\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authorization/v1beta1.SelfSubjectAccessReviewSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is filled in by the server and indicates whether the request is allowed or not\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authorization/v1beta1.SubjectAccessReviewStatus\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/authorization/v1beta1.SelfSubjectAccessReviewSpec\", \"k8s.io/api/authorization/v1beta1.SubjectAccessReviewStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_authorization_v1beta1_SelfSubjectAccessReviewSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SelfSubjectAccessReviewSpec is a description of the access request.  Exactly one of ResourceAuthorizationAttributes and NonResourceAuthorizationAttributes must be set\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"resourceAttributes\": { SchemaProps: spec.SchemaProps{ Description: \"ResourceAuthorizationAttributes describes information for a resource access request\", Ref:         ref(\"k8s.io/api/authorization/v1beta1.ResourceAttributes\"), }, }, \"nonResourceAttributes\": { SchemaProps: spec.SchemaProps{ Description: \"NonResourceAttributes describes information for a non-resource access request\", Ref:         ref(\"k8s.io/api/authorization/v1beta1.NonResourceAttributes\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/authorization/v1beta1.NonResourceAttributes\", \"k8s.io/api/authorization/v1beta1.ResourceAttributes\"}, } } func schema_k8sio_api_authorization_v1beta1_SelfSubjectRulesReview(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SelfSubjectRulesReview enumerates the set of actions the current user can perform within a namespace. The returned list of actions may be incomplete depending on the server's authorization mode, and any errors experienced during the evaluation. SelfSubjectRulesReview should be used by UIs to show/hide actions, or to quickly let an end user reason about their permissions. It should NOT Be used by external systems to drive authorization decisions as this raises confused deputy, cache lifetime/revocation, and correctness concerns. SubjectAccessReview, and LocalAccessReview are the correct way to defer authorization decisions to the API server.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec holds information about the request being evaluated.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authorization/v1beta1.SelfSubjectRulesReviewSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is filled in by the server and indicates the set of actions a user can perform.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authorization/v1beta1.SubjectRulesReviewStatus\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/authorization/v1beta1.SelfSubjectRulesReviewSpec\", \"k8s.io/api/authorization/v1beta1.SubjectRulesReviewStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_authorization_v1beta1_SelfSubjectRulesReviewSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SelfSubjectRulesReviewSpec defines the specification for SelfSubjectRulesReview.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"Namespace to evaluate rules for. Required.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_authorization_v1beta1_SubjectAccessReview(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SubjectAccessReview checks whether or not a user or group can perform an action.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec holds information about the request being evaluated\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authorization/v1beta1.SubjectAccessReviewSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is filled in by the server and indicates whether the request is allowed or not\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authorization/v1beta1.SubjectAccessReviewStatus\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/authorization/v1beta1.SubjectAccessReviewSpec\", \"k8s.io/api/authorization/v1beta1.SubjectAccessReviewStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_authorization_v1beta1_SubjectAccessReviewSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SubjectAccessReviewSpec is a description of the access request.  Exactly one of ResourceAuthorizationAttributes and NonResourceAuthorizationAttributes must be set\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"resourceAttributes\": { SchemaProps: spec.SchemaProps{ Description: \"ResourceAuthorizationAttributes describes information for a resource access request\", Ref:         ref(\"k8s.io/api/authorization/v1beta1.ResourceAttributes\"), }, }, \"nonResourceAttributes\": { SchemaProps: spec.SchemaProps{ Description: \"NonResourceAttributes describes information for a non-resource access request\", Ref:         ref(\"k8s.io/api/authorization/v1beta1.NonResourceAttributes\"), }, }, \"user\": { SchemaProps: spec.SchemaProps{ Description: \"User is the user you're testing for. If you specify \"User\" but not \"Group\", then is it interpreted as \"What if User were not a member of any groups\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"group\": { SchemaProps: spec.SchemaProps{ Description: \"Groups is the groups you're testing for.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"extra\": { SchemaProps: spec.SchemaProps{ Description: \"Extra corresponds to the user.Info.GetExtra() method from the authenticator.  Since that is input to the authorizer it needs a reflection here.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, \"uid\": { SchemaProps: spec.SchemaProps{ Description: \"UID information about the requesting user.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/authorization/v1beta1.NonResourceAttributes\", \"k8s.io/api/authorization/v1beta1.ResourceAttributes\"}, } } func schema_k8sio_api_authorization_v1beta1_SubjectAccessReviewStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SubjectAccessReviewStatus\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"allowed\": { SchemaProps: spec.SchemaProps{ Description: \"Allowed is required. True if the action would be allowed, false otherwise.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"denied\": { SchemaProps: spec.SchemaProps{ Description: \"Denied is optional. True if the action would be denied, otherwise false. If both allowed is false and denied is false, then the authorizer has no opinion on whether to authorize the action. Denied may not be true if Allowed is true.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"Reason is optional.  It indicates why a request was allowed or denied.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"evaluationError\": { SchemaProps: spec.SchemaProps{ Description: \"EvaluationError is an indication that some error occurred during the authorization check. It is entirely possible to get an error and be able to continue determine authorization status in spite of it. For instance, RBAC can be missing a role, but enough roles are still present and bound to reason about the request.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"allowed\"}, }, }, } } func schema_k8sio_api_authorization_v1beta1_SubjectRulesReviewStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SubjectRulesReviewStatus contains the result of a rules check. This check can be incomplete depending on the set of authorizers the server is configured with and any errors experienced during evaluation. Because authorization rules are additive, if a rule appears in a list it's safe to assume the subject has that permission, even if that list is incomplete.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"resourceRules\": { SchemaProps: spec.SchemaProps{ Description: \"ResourceRules is the list of actions the subject is allowed to perform on resources. The list ordering isn't significant, may contain duplicates, and possibly be incomplete.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/authorization/v1beta1.ResourceRule\"), }, }, }, }, }, \"nonResourceRules\": { SchemaProps: spec.SchemaProps{ Description: \"NonResourceRules is the list of actions the subject is allowed to perform on non-resources. The list ordering isn't significant, may contain duplicates, and possibly be incomplete.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/authorization/v1beta1.NonResourceRule\"), }, }, }, }, }, \"incomplete\": { SchemaProps: spec.SchemaProps{ Description: \"Incomplete is true when the rules returned by this call are incomplete. This is most commonly encountered when an authorizer, such as an external authorizer, doesn't support rules evaluation.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"evaluationError\": { SchemaProps: spec.SchemaProps{ Description: \"EvaluationError can appear in combination with Rules. It indicates an error occurred during rule evaluation, such as an authorizer that doesn't support rule evaluation, and that ResourceRules and/or NonResourceRules may be incomplete.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"resourceRules\", \"nonResourceRules\", \"incomplete\"}, }, }, Dependencies: []string{ \"k8s.io/api/authorization/v1beta1.NonResourceRule\", \"k8s.io/api/authorization/v1beta1.ResourceRule\"}, } } func schema_k8sio_api_autoscaling_v1_ContainerResourceMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ContainerResourceMetricSource indicates how to scale on a resource metric known to Kubernetes, as specified in the requests and limits, describing a single container in each of the pods of the current scale target(e.g. CPU or memory). The values will be averaged together before being compared to the target. Such metrics are built into Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source. Only one \"target\" type should be set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the name of the resource in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"targetAverageUtilization\": { SchemaProps: spec.SchemaProps{ Description: \"targetAverageUtilization is the target value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"targetAverageValue\": { SchemaProps: spec.SchemaProps{ Description: \"targetAverageValue is the target value of the average of the resource metric across all relevant pods, as a raw value (instead of as a percentage of the request), similar to the \"pods\" metric source type.\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"container\": { SchemaProps: spec.SchemaProps{ Description: \"container is the name of the container in the pods of the scaling target.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"container\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_autoscaling_v1_ContainerResourceMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ContainerResourceMetricStatus indicates the current value of a resource metric known to Kubernetes, as specified in requests and limits, describing a single container in each pod in the current scale target (e.g. CPU or memory).  Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the name of the resource in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"currentAverageUtilization\": { SchemaProps: spec.SchemaProps{ Description: \"currentAverageUtilization is the current value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods.  It will only be present if `targetAverageValue` was set in the corresponding metric specification.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"currentAverageValue\": { SchemaProps: spec.SchemaProps{ Description: \"currentAverageValue is the current value of the average of the resource metric across all relevant pods, as a raw value (instead of as a percentage of the request), similar to the \"pods\" metric source type. It will always be set, regardless of the corresponding metric specification.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"container\": { SchemaProps: spec.SchemaProps{ Description: \"container is the name of the container in the pods of the scaling taget\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"currentAverageValue\", \"container\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_autoscaling_v1_CrossVersionObjectReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CrossVersionObjectReference contains enough information to let you identify the referred resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\"\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the referent; More info: http://kubernetes.io/docs/user-guide/identifiers#names\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"API version of the referent\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"kind\", \"name\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, } } func schema_k8sio_api_autoscaling_v1_ExternalMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExternalMetricSource indicates how to scale on a metric not associated with any Kubernetes object (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metricName\": { SchemaProps: spec.SchemaProps{ Description: \"metricName is the name of the metric in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metricSelector\": { SchemaProps: spec.SchemaProps{ Description: \"metricSelector is used to identify a specific time series within a given metric.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"targetValue\": { SchemaProps: spec.SchemaProps{ Description: \"targetValue is the target value of the metric (as a quantity). Mutually exclusive with TargetAverageValue.\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"targetAverageValue\": { SchemaProps: spec.SchemaProps{ Description: \"targetAverageValue is the target per-pod value of global metric (as a quantity). Mutually exclusive with TargetValue.\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, Required: []string{\"metricName\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_autoscaling_v1_ExternalMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExternalMetricStatus indicates the current value of a global metric not associated with any Kubernetes object.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metricName\": { SchemaProps: spec.SchemaProps{ Description: \"metricName is the name of a metric used for autoscaling in metric system.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metricSelector\": { SchemaProps: spec.SchemaProps{ Description: \"metricSelector is used to identify a specific time series within a given metric.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"currentValue\": { SchemaProps: spec.SchemaProps{ Description: \"currentValue is the current value of the metric (as a quantity)\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"currentAverageValue\": { SchemaProps: spec.SchemaProps{ Description: \"currentAverageValue is the current value of metric averaged over autoscaled pods.\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, Required: []string{\"metricName\", \"currentValue\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_autoscaling_v1_HorizontalPodAutoscaler(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"configuration of a horizontal pod autoscaler.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"behaviour of autoscaler. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v1.HorizontalPodAutoscalerSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"current information about the autoscaler.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v1.HorizontalPodAutoscalerStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v1.HorizontalPodAutoscalerSpec\", \"k8s.io/api/autoscaling/v1.HorizontalPodAutoscalerStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_autoscaling_v1_HorizontalPodAutoscalerCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerCondition describes the state of a HorizontalPodAutoscaler at a certain point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type describes the current condition\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"status is the status of the condition (True, False, Unknown)\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"lastTransitionTime is the last time the condition transitioned from one status to another\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"reason is the reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"message is a human-readable explanation containing details about the transition\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_autoscaling_v1_HorizontalPodAutoscalerList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"list of horizontal pod autoscaler objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"list of horizontal pod autoscaler objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/autoscaling/v1.HorizontalPodAutoscaler\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v1.HorizontalPodAutoscaler\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_autoscaling_v1_HorizontalPodAutoscalerSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"specification of a horizontal pod autoscaler.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"scaleTargetRef\": { SchemaProps: spec.SchemaProps{ Description: \"reference to scaled resource; horizontal pod autoscaler will learn the current resource consumption and will set the desired number of pods by using its Scale subresource.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v1.CrossVersionObjectReference\"), }, }, \"minReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"minReplicas is the lower limit for the number of replicas to which the autoscaler can scale down.  It defaults to 1 pod.  minReplicas is allowed to be 0 if the alpha feature gate HPAScaleToZero is enabled and at least one Object or External metric is configured.  Scaling is active as long as at least one metric value is available.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"maxReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"upper limit for the number of pods that can be set by the autoscaler; cannot be smaller than MinReplicas.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"targetCPUUtilizationPercentage\": { SchemaProps: spec.SchemaProps{ Description: \"target average CPU utilization (represented as a percentage of requested CPU) over all the pods; if not specified the default autoscaling policy will be used.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"scaleTargetRef\", \"maxReplicas\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v1.CrossVersionObjectReference\"}, } } func schema_k8sio_api_autoscaling_v1_HorizontalPodAutoscalerStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"current status of a horizontal pod autoscaler\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"most recent generation observed by this autoscaler.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"lastScaleTime\": { SchemaProps: spec.SchemaProps{ Description: \"last time the HorizontalPodAutoscaler scaled the number of pods; used by the autoscaler to control how often the number of pods is changed.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"currentReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"current number of replicas of pods managed by this autoscaler.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"desiredReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"desired number of replicas of pods managed by this autoscaler.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"currentCPUUtilizationPercentage\": { SchemaProps: spec.SchemaProps{ Description: \"current average CPU utilization over all pods, represented as a percentage of requested CPU, e.g. 70 means that an average pod is using now 70% of its requested CPU.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"currentReplicas\", \"desiredReplicas\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_autoscaling_v1_MetricSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricSpec specifies how to scale based on a single metric (only `type` and one other matching field should be set at once).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type is the type of metric source.  It should be one of \"ContainerResource\", \"External\", \"Object\", \"Pods\" or \"Resource\", each mapping to a matching field in the object. Note: \"ContainerResource\" type is available on when the feature-gate HPAContainerMetrics is enablednnPossible enum values:n - `\"ContainerResource\"` is a resource metric known to Kubernetes, as specified in requests and limits, describing a single container in each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics (the \"pods\" source).n - `\"External\"` is a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).n - `\"Object\"` is a metric describing a kubernetes object (for example, hits-per-second on an Ingress object).n - `\"Pods\"` is a metric describing each pod in the current scale target (for example, transactions-processed-per-second). The values will be averaged together before being compared to the target value.n - `\"Resource\"` is a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics (the \"pods\" source).\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"ContainerResource\", \"External\", \"Object\", \"Pods\", \"Resource\"}}, }, \"object\": { SchemaProps: spec.SchemaProps{ Description: \"object refers to a metric describing a single kubernetes object (for example, hits-per-second on an Ingress object).\", Ref:         ref(\"k8s.io/api/autoscaling/v1.ObjectMetricSource\"), }, }, \"pods\": { SchemaProps: spec.SchemaProps{ Description: \"pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second).  The values will be averaged together before being compared to the target value.\", Ref:         ref(\"k8s.io/api/autoscaling/v1.PodsMetricSource\"), }, }, \"resource\": { SchemaProps: spec.SchemaProps{ Description: \"resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Ref:         ref(\"k8s.io/api/autoscaling/v1.ResourceMetricSource\"), }, }, \"containerResource\": { SchemaProps: spec.SchemaProps{ Description: \"container resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing a single container in each pod of the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source. This is an alpha feature and can be enabled by the HPAContainerMetrics feature flag.\", Ref:         ref(\"k8s.io/api/autoscaling/v1.ContainerResourceMetricSource\"), }, }, \"external\": { SchemaProps: spec.SchemaProps{ Description: \"external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).\", Ref:         ref(\"k8s.io/api/autoscaling/v1.ExternalMetricSource\"), }, }, }, Required: []string{\"type\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v1.ContainerResourceMetricSource\", \"k8s.io/api/autoscaling/v1.ExternalMetricSource\", \"k8s.io/api/autoscaling/v1.ObjectMetricSource\", \"k8s.io/api/autoscaling/v1.PodsMetricSource\", \"k8s.io/api/autoscaling/v1.ResourceMetricSource\"}, } } func schema_k8sio_api_autoscaling_v1_MetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricStatus describes the last-read state of a single metric.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type is the type of metric source.  It will be one of \"ContainerResource\", \"External\", \"Object\", \"Pods\" or \"Resource\", each corresponds to a matching field in the object. Note: \"ContainerResource\" type is available on when the feature-gate HPAContainerMetrics is enablednnPossible enum values:n - `\"ContainerResource\"` is a resource metric known to Kubernetes, as specified in requests and limits, describing a single container in each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics (the \"pods\" source).n - `\"External\"` is a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).n - `\"Object\"` is a metric describing a kubernetes object (for example, hits-per-second on an Ingress object).n - `\"Pods\"` is a metric describing each pod in the current scale target (for example, transactions-processed-per-second). The values will be averaged together before being compared to the target value.n - `\"Resource\"` is a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics (the \"pods\" source).\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"ContainerResource\", \"External\", \"Object\", \"Pods\", \"Resource\"}}, }, \"object\": { SchemaProps: spec.SchemaProps{ Description: \"object refers to a metric describing a single kubernetes object (for example, hits-per-second on an Ingress object).\", Ref:         ref(\"k8s.io/api/autoscaling/v1.ObjectMetricStatus\"), }, }, \"pods\": { SchemaProps: spec.SchemaProps{ Description: \"pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second).  The values will be averaged together before being compared to the target value.\", Ref:         ref(\"k8s.io/api/autoscaling/v1.PodsMetricStatus\"), }, }, \"resource\": { SchemaProps: spec.SchemaProps{ Description: \"resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Ref:         ref(\"k8s.io/api/autoscaling/v1.ResourceMetricStatus\"), }, }, \"containerResource\": { SchemaProps: spec.SchemaProps{ Description: \"container resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing a single container in each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Ref:         ref(\"k8s.io/api/autoscaling/v1.ContainerResourceMetricStatus\"), }, }, \"external\": { SchemaProps: spec.SchemaProps{ Description: \"external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).\", Ref:         ref(\"k8s.io/api/autoscaling/v1.ExternalMetricStatus\"), }, }, }, Required: []string{\"type\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v1.ContainerResourceMetricStatus\", \"k8s.io/api/autoscaling/v1.ExternalMetricStatus\", \"k8s.io/api/autoscaling/v1.ObjectMetricStatus\", \"k8s.io/api/autoscaling/v1.PodsMetricStatus\", \"k8s.io/api/autoscaling/v1.ResourceMetricStatus\"}, } } func schema_k8sio_api_autoscaling_v1_ObjectMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ObjectMetricSource indicates how to scale on a metric describing a kubernetes object (for example, hits-per-second on an Ingress object).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"target\": { SchemaProps: spec.SchemaProps{ Description: \"target is the described Kubernetes object.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v1.CrossVersionObjectReference\"), }, }, \"metricName\": { SchemaProps: spec.SchemaProps{ Description: \"metricName is the name of the metric in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"targetValue\": { SchemaProps: spec.SchemaProps{ Description: \"targetValue is the target value of the metric (as a quantity).\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"selector is the string-encoded form of a standard kubernetes label selector for the given metric. When set, it is passed as an additional parameter to the metrics server for more specific metrics scoping When unset, just the metricName will be used to gather metrics.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"averageValue\": { SchemaProps: spec.SchemaProps{ Description: \"averageValue is the target value of the average of the metric across all relevant pods (as a quantity)\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, Required: []string{\"target\", \"metricName\", \"targetValue\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v1.CrossVersionObjectReference\", \"k8s.io/apimachinery/pkg/api/resource.Quantity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_autoscaling_v1_ObjectMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ObjectMetricStatus indicates the current value of a metric describing a kubernetes object (for example, hits-per-second on an Ingress object).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"target\": { SchemaProps: spec.SchemaProps{ Description: \"target is the described Kubernetes object.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v1.CrossVersionObjectReference\"), }, }, \"metricName\": { SchemaProps: spec.SchemaProps{ Description: \"metricName is the name of the metric in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"currentValue\": { SchemaProps: spec.SchemaProps{ Description: \"currentValue is the current value of the metric (as a quantity).\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"selector is the string-encoded form of a standard kubernetes label selector for the given metric When set in the ObjectMetricSource, it is passed as an additional parameter to the metrics server for more specific metrics scoping. When unset, just the metricName will be used to gather metrics.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"averageValue\": { SchemaProps: spec.SchemaProps{ Description: \"averageValue is the current value of the average of the metric across all relevant pods (as a quantity)\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, Required: []string{\"target\", \"metricName\", \"currentValue\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v1.CrossVersionObjectReference\", \"k8s.io/apimachinery/pkg/api/resource.Quantity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_autoscaling_v1_PodsMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodsMetricSource indicates how to scale on a metric describing each pod in the current scale target (for example, transactions-processed-per-second). The values will be averaged together before being compared to the target value.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metricName\": { SchemaProps: spec.SchemaProps{ Description: \"metricName is the name of the metric in question\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"targetAverageValue\": { SchemaProps: spec.SchemaProps{ Description: \"targetAverageValue is the target value of the average of the metric across all relevant pods (as a quantity)\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"selector is the string-encoded form of a standard kubernetes label selector for the given metric When set, it is passed as an additional parameter to the metrics server for more specific metrics scoping When unset, just the metricName will be used to gather metrics.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, }, Required: []string{\"metricName\", \"targetAverageValue\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_autoscaling_v1_PodsMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodsMetricStatus indicates the current value of a metric describing each pod in the current scale target (for example, transactions-processed-per-second).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metricName\": { SchemaProps: spec.SchemaProps{ Description: \"metricName is the name of the metric in question\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"currentAverageValue\": { SchemaProps: spec.SchemaProps{ Description: \"currentAverageValue is the current value of the average of the metric across all relevant pods (as a quantity)\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"selector is the string-encoded form of a standard kubernetes label selector for the given metric When set in the PodsMetricSource, it is passed as an additional parameter to the metrics server for more specific metrics scoping. When unset, just the metricName will be used to gather metrics.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, }, Required: []string{\"metricName\", \"currentAverageValue\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_autoscaling_v1_ResourceMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceMetricSource indicates how to scale on a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory).  The values will be averaged together before being compared to the target.  Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.  Only one \"target\" type should be set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the name of the resource in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"targetAverageUtilization\": { SchemaProps: spec.SchemaProps{ Description: \"targetAverageUtilization is the target value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"targetAverageValue\": { SchemaProps: spec.SchemaProps{ Description: \"targetAverageValue is the target value of the average of the resource metric across all relevant pods, as a raw value (instead of as a percentage of the request), similar to the \"pods\" metric source type.\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, Required: []string{\"name\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_autoscaling_v1_ResourceMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceMetricStatus indicates the current value of a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory).  Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the name of the resource in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"currentAverageUtilization\": { SchemaProps: spec.SchemaProps{ Description: \"currentAverageUtilization is the current value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods.  It will only be present if `targetAverageValue` was set in the corresponding metric specification.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"currentAverageValue\": { SchemaProps: spec.SchemaProps{ Description: \"currentAverageValue is the current value of the average of the resource metric across all relevant pods, as a raw value (instead of as a percentage of the request), similar to the \"pods\" metric source type. It will always be set, regardless of the corresponding metric specification.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, Required: []string{\"name\", \"currentAverageValue\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_autoscaling_v1_Scale(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Scale represents a scaling request for a resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object metadata; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"defines the behavior of the scale. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v1.ScaleSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"current status of the scale. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status. Read-only.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v1.ScaleStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v1.ScaleSpec\", \"k8s.io/api/autoscaling/v1.ScaleStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_autoscaling_v1_ScaleSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ScaleSpec describes the attributes of a scale subresource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"desired number of instances for the scaled object.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_k8sio_api_autoscaling_v1_ScaleStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ScaleStatus represents the current status of a scale subresource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"actual number of observed instances of the scaled object.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"label query over pods that should match the replicas count. This is same as the label selector but in the string format to avoid introspection by clients. The string will be in the same format as the query-param syntax. More info about label selectors: http://kubernetes.io/docs/user-guide/labels#label-selectors\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"replicas\"}, }, }, } } func schema_k8sio_api_autoscaling_v2_ContainerResourceMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ContainerResourceMetricSource indicates how to scale on a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory).  The values will be averaged together before being compared to the target.  Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.  Only one \"target\" type should be set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the name of the resource in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"target\": { SchemaProps: spec.SchemaProps{ Description: \"target specifies the target value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.MetricTarget\"), }, }, \"container\": { SchemaProps: spec.SchemaProps{ Description: \"container is the name of the container in the pods of the scaling target\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"target\", \"container\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2.MetricTarget\"}, } } func schema_k8sio_api_autoscaling_v2_ContainerResourceMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ContainerResourceMetricStatus indicates the current value of a resource metric known to Kubernetes, as specified in requests and limits, describing a single container in each pod in the current scale target (e.g. CPU or memory).  Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the name of the resource in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"current\": { SchemaProps: spec.SchemaProps{ Description: \"current contains the current value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.MetricValueStatus\"), }, }, \"container\": { SchemaProps: spec.SchemaProps{ Description: \"Container is the name of the container in the pods of the scaling target\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"current\", \"container\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2.MetricValueStatus\"}, } } func schema_k8sio_api_autoscaling_v2_CrossVersionObjectReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CrossVersionObjectReference contains enough information to let you identify the referred resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\"\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the referent; More info: http://kubernetes.io/docs/user-guide/identifiers#names\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"API version of the referent\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"kind\", \"name\"}, }, }, } } func schema_k8sio_api_autoscaling_v2_ExternalMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExternalMetricSource indicates how to scale on a metric not associated with any Kubernetes object (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metric\": { SchemaProps: spec.SchemaProps{ Description: \"metric identifies the target metric by name and selector\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.MetricIdentifier\"), }, }, \"target\": { SchemaProps: spec.SchemaProps{ Description: \"target specifies the target value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.MetricTarget\"), }, }, }, Required: []string{\"metric\", \"target\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2.MetricIdentifier\", \"k8s.io/api/autoscaling/v2.MetricTarget\"}, } } func schema_k8sio_api_autoscaling_v2_ExternalMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExternalMetricStatus indicates the current value of a global metric not associated with any Kubernetes object.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metric\": { SchemaProps: spec.SchemaProps{ Description: \"metric identifies the target metric by name and selector\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.MetricIdentifier\"), }, }, \"current\": { SchemaProps: spec.SchemaProps{ Description: \"current contains the current value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.MetricValueStatus\"), }, }, }, Required: []string{\"metric\", \"current\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2.MetricIdentifier\", \"k8s.io/api/autoscaling/v2.MetricValueStatus\"}, } } func schema_k8sio_api_autoscaling_v2_HPAScalingPolicy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HPAScalingPolicy is a single policy which must hold true for a specified past interval.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type is used to specify the scaling policy.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"value\": { SchemaProps: spec.SchemaProps{ Description: \"Value contains the amount of change which is permitted by the policy. It must be greater than zero\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"periodSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"PeriodSeconds specifies the window of time for which the policy should hold true. PeriodSeconds must be greater than zero and less than or equal to 1800 (30 min).\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"type\", \"value\", \"periodSeconds\"}, }, }, } } func schema_k8sio_api_autoscaling_v2_HPAScalingRules(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HPAScalingRules configures the scaling behavior for one direction. These Rules are applied after calculating DesiredReplicas from metrics for the HPA. They can limit the scaling velocity by specifying scaling policies. They can prevent flapping by specifying the stabilization window, so that the number of replicas is not set instantly, instead, the safest value from the stabilization window is chosen.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"stabilizationWindowSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"StabilizationWindowSeconds is the number of seconds for which past recommendations should be considered while scaling up or scaling down. StabilizationWindowSeconds must be greater than or equal to zero and less than or equal to 3600 (one hour). If not set, use the default values: - For scale up: 0 (i.e. no stabilization is done). - For scale down: 300 (i.e. the stabilization window is 300 seconds long).\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"selectPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"selectPolicy is used to specify which policy should be used. If not set, the default value Max is used.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"policies\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"policies is a list of potential scaling polices which can be used during scaling. At least one policy must be specified, otherwise the HPAScalingRules will be discarded as invalid\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/autoscaling/v2.HPAScalingPolicy\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2.HPAScalingPolicy\"}, } } func schema_k8sio_api_autoscaling_v2_HorizontalPodAutoscaler(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscaler is the configuration for a horizontal pod autoscaler, which automatically manages the replica count of any resource implementing the scale subresource based on the metrics specified.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"metadata is the standard object metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"spec is the specification for the behaviour of the autoscaler. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.HorizontalPodAutoscalerSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"status is the current information about the autoscaler.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.HorizontalPodAutoscalerStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2.HorizontalPodAutoscalerSpec\", \"k8s.io/api/autoscaling/v2.HorizontalPodAutoscalerStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_autoscaling_v2_HorizontalPodAutoscalerBehavior(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerBehavior configures the scaling behavior of the target in both Up and Down directions (scaleUp and scaleDown fields respectively).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"scaleUp\": { SchemaProps: spec.SchemaProps{ Description: \"scaleUp is scaling policy for scaling Up. If not set, the default value is the higher of:n  * increase no more than 4 pods per 60 secondsn  * double the number of pods per 60 secondsnNo stabilization is used.\", Ref:         ref(\"k8s.io/api/autoscaling/v2.HPAScalingRules\"), }, }, \"scaleDown\": { SchemaProps: spec.SchemaProps{ Description: \"scaleDown is scaling policy for scaling Down. If not set, the default value is to allow to scale down to minReplicas pods, with a 300 second stabilization window (i.e., the highest recommendation for the last 300sec is used).\", Ref:         ref(\"k8s.io/api/autoscaling/v2.HPAScalingRules\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2.HPAScalingRules\"}, } } func schema_k8sio_api_autoscaling_v2_HorizontalPodAutoscalerCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerCondition describes the state of a HorizontalPodAutoscaler at a certain point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type describes the current condition\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"status is the status of the condition (True, False, Unknown)\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"lastTransitionTime is the last time the condition transitioned from one status to another\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"reason is the reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"message is a human-readable explanation containing details about the transition\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_autoscaling_v2_HorizontalPodAutoscalerList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerList is a list of horizontal pod autoscaler objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"metadata is the standard list metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is the list of horizontal pod autoscaler objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/autoscaling/v2.HorizontalPodAutoscaler\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2.HorizontalPodAutoscaler\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_autoscaling_v2_HorizontalPodAutoscalerSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerSpec describes the desired functionality of the HorizontalPodAutoscaler.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"scaleTargetRef\": { SchemaProps: spec.SchemaProps{ Description: \"scaleTargetRef points to the target resource to scale, and is used to the pods for which metrics should be collected, as well as to actually change the replica count.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.CrossVersionObjectReference\"), }, }, \"minReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"minReplicas is the lower limit for the number of replicas to which the autoscaler can scale down.  It defaults to 1 pod.  minReplicas is allowed to be 0 if the alpha feature gate HPAScaleToZero is enabled and at least one Object or External metric is configured.  Scaling is active as long as at least one metric value is available.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"maxReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"maxReplicas is the upper limit for the number of replicas to which the autoscaler can scale up. It cannot be less that minReplicas.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"metrics\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"metrics contains the specifications for which to use to calculate the desired replica count (the maximum replica count across all metrics will be used).  The desired replica count is calculated multiplying the ratio between the target value and the current value by the current number of pods.  Ergo, metrics used must decrease as the pod count is increased, and vice-versa.  See the individual metric source types for more information about how each type of metric must respond. If not set, the default metric will be set to 80% average CPU utilization.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/autoscaling/v2.MetricSpec\"), }, }, }, }, }, \"behavior\": { SchemaProps: spec.SchemaProps{ Description: \"behavior configures the scaling behavior of the target in both Up and Down directions (scaleUp and scaleDown fields respectively). If not set, the default HPAScalingRules for scale up and scale down are used.\", Ref:         ref(\"k8s.io/api/autoscaling/v2.HorizontalPodAutoscalerBehavior\"), }, }, }, Required: []string{\"scaleTargetRef\", \"maxReplicas\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2.CrossVersionObjectReference\", \"k8s.io/api/autoscaling/v2.HorizontalPodAutoscalerBehavior\", \"k8s.io/api/autoscaling/v2.MetricSpec\"}, } } func schema_k8sio_api_autoscaling_v2_HorizontalPodAutoscalerStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerStatus describes the current status of a horizontal pod autoscaler.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"observedGeneration is the most recent generation observed by this autoscaler.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"lastScaleTime\": { SchemaProps: spec.SchemaProps{ Description: \"lastScaleTime is the last time the HorizontalPodAutoscaler scaled the number of pods, used by the autoscaler to control how often the number of pods is changed.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"currentReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"currentReplicas is current number of replicas of pods managed by this autoscaler, as last seen by the autoscaler.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"desiredReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"desiredReplicas is the desired number of replicas of pods managed by this autoscaler, as last calculated by the autoscaler.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"currentMetrics\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"currentMetrics is the last read state of the metrics used by this autoscaler.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/autoscaling/v2.MetricStatus\"), }, }, }, }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"type\", }, \"x-kubernetes-list-type\":       \"map\", \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"conditions is the set of conditions required for this autoscaler to scale its target, and indicates whether or not those conditions are met.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/autoscaling/v2.HorizontalPodAutoscalerCondition\"), }, }, }, }, }, }, Required: []string{\"desiredReplicas\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2.HorizontalPodAutoscalerCondition\", \"k8s.io/api/autoscaling/v2.MetricStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_autoscaling_v2_MetricIdentifier(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricIdentifier defines the name and optionally selector for a metric\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the name of the given metric\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"selector is the string-encoded form of a standard kubernetes label selector for the given metric When set, it is passed as an additional parameter to the metrics server for more specific metrics scoping. When unset, just the metricName will be used to gather metrics.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, }, Required: []string{\"name\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_autoscaling_v2_MetricSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricSpec specifies how to scale based on a single metric (only `type` and one other matching field should be set at once).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type is the type of metric source.  It should be one of \"ContainerResource\", \"External\", \"Object\", \"Pods\" or \"Resource\", each mapping to a matching field in the object. Note: \"ContainerResource\" type is available on when the feature-gate HPAContainerMetrics is enabled\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"object\": { SchemaProps: spec.SchemaProps{ Description: \"object refers to a metric describing a single kubernetes object (for example, hits-per-second on an Ingress object).\", Ref:         ref(\"k8s.io/api/autoscaling/v2.ObjectMetricSource\"), }, }, \"pods\": { SchemaProps: spec.SchemaProps{ Description: \"pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second).  The values will be averaged together before being compared to the target value.\", Ref:         ref(\"k8s.io/api/autoscaling/v2.PodsMetricSource\"), }, }, \"resource\": { SchemaProps: spec.SchemaProps{ Description: \"resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Ref:         ref(\"k8s.io/api/autoscaling/v2.ResourceMetricSource\"), }, }, \"containerResource\": { SchemaProps: spec.SchemaProps{ Description: \"containerResource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing a single container in each pod of the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source. This is an alpha feature and can be enabled by the HPAContainerMetrics feature flag.\", Ref:         ref(\"k8s.io/api/autoscaling/v2.ContainerResourceMetricSource\"), }, }, \"external\": { SchemaProps: spec.SchemaProps{ Description: \"external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).\", Ref:         ref(\"k8s.io/api/autoscaling/v2.ExternalMetricSource\"), }, }, }, Required: []string{\"type\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2.ContainerResourceMetricSource\", \"k8s.io/api/autoscaling/v2.ExternalMetricSource\", \"k8s.io/api/autoscaling/v2.ObjectMetricSource\", \"k8s.io/api/autoscaling/v2.PodsMetricSource\", \"k8s.io/api/autoscaling/v2.ResourceMetricSource\"}, } } func schema_k8sio_api_autoscaling_v2_MetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricStatus describes the last-read state of a single metric.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type is the type of metric source.  It will be one of \"ContainerResource\", \"External\", \"Object\", \"Pods\" or \"Resource\", each corresponds to a matching field in the object. Note: \"ContainerResource\" type is available on when the feature-gate HPAContainerMetrics is enabled\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"object\": { SchemaProps: spec.SchemaProps{ Description: \"object refers to a metric describing a single kubernetes object (for example, hits-per-second on an Ingress object).\", Ref:         ref(\"k8s.io/api/autoscaling/v2.ObjectMetricStatus\"), }, }, \"pods\": { SchemaProps: spec.SchemaProps{ Description: \"pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second).  The values will be averaged together before being compared to the target value.\", Ref:         ref(\"k8s.io/api/autoscaling/v2.PodsMetricStatus\"), }, }, \"resource\": { SchemaProps: spec.SchemaProps{ Description: \"resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Ref:         ref(\"k8s.io/api/autoscaling/v2.ResourceMetricStatus\"), }, }, \"containerResource\": { SchemaProps: spec.SchemaProps{ Description: \"container resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing a single container in each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Ref:         ref(\"k8s.io/api/autoscaling/v2.ContainerResourceMetricStatus\"), }, }, \"external\": { SchemaProps: spec.SchemaProps{ Description: \"external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).\", Ref:         ref(\"k8s.io/api/autoscaling/v2.ExternalMetricStatus\"), }, }, }, Required: []string{\"type\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2.ContainerResourceMetricStatus\", \"k8s.io/api/autoscaling/v2.ExternalMetricStatus\", \"k8s.io/api/autoscaling/v2.ObjectMetricStatus\", \"k8s.io/api/autoscaling/v2.PodsMetricStatus\", \"k8s.io/api/autoscaling/v2.ResourceMetricStatus\"}, } } func schema_k8sio_api_autoscaling_v2_MetricTarget(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricTarget defines the target value, average value, or average utilization of a specific metric\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type represents whether the metric type is Utilization, Value, or AverageValue\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"value\": { SchemaProps: spec.SchemaProps{ Description: \"value is the target value of the metric (as a quantity).\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"averageValue\": { SchemaProps: spec.SchemaProps{ Description: \"averageValue is the target value of the average of the metric across all relevant pods (as a quantity)\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"averageUtilization\": { SchemaProps: spec.SchemaProps{ Description: \"averageUtilization is the target value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods. Currently only valid for Resource metric source type\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"type\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_autoscaling_v2_MetricValueStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricValueStatus holds the current value for a metric\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"value\": { SchemaProps: spec.SchemaProps{ Description: \"value is the current value of the metric (as a quantity).\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"averageValue\": { SchemaProps: spec.SchemaProps{ Description: \"averageValue is the current value of the average of the metric across all relevant pods (as a quantity)\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"averageUtilization\": { SchemaProps: spec.SchemaProps{ Description: \"currentAverageUtilization is the current value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_autoscaling_v2_ObjectMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ObjectMetricSource indicates how to scale on a metric describing a kubernetes object (for example, hits-per-second on an Ingress object).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"describedObject\": { SchemaProps: spec.SchemaProps{ Description: \"describedObject specifies the descriptions of a object,such as kind,name apiVersion\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.CrossVersionObjectReference\"), }, }, \"target\": { SchemaProps: spec.SchemaProps{ Description: \"target specifies the target value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.MetricTarget\"), }, }, \"metric\": { SchemaProps: spec.SchemaProps{ Description: \"metric identifies the target metric by name and selector\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.MetricIdentifier\"), }, }, }, Required: []string{\"describedObject\", \"target\", \"metric\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2.CrossVersionObjectReference\", \"k8s.io/api/autoscaling/v2.MetricIdentifier\", \"k8s.io/api/autoscaling/v2.MetricTarget\"}, } } func schema_k8sio_api_autoscaling_v2_ObjectMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ObjectMetricStatus indicates the current value of a metric describing a kubernetes object (for example, hits-per-second on an Ingress object).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metric\": { SchemaProps: spec.SchemaProps{ Description: \"metric identifies the target metric by name and selector\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.MetricIdentifier\"), }, }, \"current\": { SchemaProps: spec.SchemaProps{ Description: \"current contains the current value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.MetricValueStatus\"), }, }, \"describedObject\": { SchemaProps: spec.SchemaProps{ Description: \"DescribedObject specifies the descriptions of a object,such as kind,name apiVersion\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.CrossVersionObjectReference\"), }, }, }, Required: []string{\"metric\", \"current\", \"describedObject\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2.CrossVersionObjectReference\", \"k8s.io/api/autoscaling/v2.MetricIdentifier\", \"k8s.io/api/autoscaling/v2.MetricValueStatus\"}, } } func schema_k8sio_api_autoscaling_v2_PodsMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodsMetricSource indicates how to scale on a metric describing each pod in the current scale target (for example, transactions-processed-per-second). The values will be averaged together before being compared to the target value.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metric\": { SchemaProps: spec.SchemaProps{ Description: \"metric identifies the target metric by name and selector\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.MetricIdentifier\"), }, }, \"target\": { SchemaProps: spec.SchemaProps{ Description: \"target specifies the target value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.MetricTarget\"), }, }, }, Required: []string{\"metric\", \"target\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2.MetricIdentifier\", \"k8s.io/api/autoscaling/v2.MetricTarget\"}, } } func schema_k8sio_api_autoscaling_v2_PodsMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodsMetricStatus indicates the current value of a metric describing each pod in the current scale target (for example, transactions-processed-per-second).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metric\": { SchemaProps: spec.SchemaProps{ Description: \"metric identifies the target metric by name and selector\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.MetricIdentifier\"), }, }, \"current\": { SchemaProps: spec.SchemaProps{ Description: \"current contains the current value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.MetricValueStatus\"), }, }, }, Required: []string{\"metric\", \"current\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2.MetricIdentifier\", \"k8s.io/api/autoscaling/v2.MetricValueStatus\"}, } } func schema_k8sio_api_autoscaling_v2_ResourceMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceMetricSource indicates how to scale on a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory).  The values will be averaged together before being compared to the target.  Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.  Only one \"target\" type should be set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the name of the resource in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"target\": { SchemaProps: spec.SchemaProps{ Description: \"target specifies the target value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.MetricTarget\"), }, }, }, Required: []string{\"name\", \"target\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2.MetricTarget\"}, } } func schema_k8sio_api_autoscaling_v2_ResourceMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceMetricStatus indicates the current value of a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory).  Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the name of the resource in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"current\": { SchemaProps: spec.SchemaProps{ Description: \"current contains the current value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2.MetricValueStatus\"), }, }, }, Required: []string{\"name\", \"current\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2.MetricValueStatus\"}, } } func schema_k8sio_api_autoscaling_v2beta1_ContainerResourceMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ContainerResourceMetricSource indicates how to scale on a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory).  The values will be averaged together before being compared to the target.  Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.  Only one \"target\" type should be set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the name of the resource in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"targetAverageUtilization\": { SchemaProps: spec.SchemaProps{ Description: \"targetAverageUtilization is the target value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"targetAverageValue\": { SchemaProps: spec.SchemaProps{ Description: \"targetAverageValue is the target value of the average of the resource metric across all relevant pods, as a raw value (instead of as a percentage of the request), similar to the \"pods\" metric source type.\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"container\": { SchemaProps: spec.SchemaProps{ Description: \"container is the name of the container in the pods of the scaling target\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"container\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_autoscaling_v2beta1_ContainerResourceMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ContainerResourceMetricStatus indicates the current value of a resource metric known to Kubernetes, as specified in requests and limits, describing a single container in each pod in the current scale target (e.g. CPU or memory).  Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the name of the resource in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"currentAverageUtilization\": { SchemaProps: spec.SchemaProps{ Description: \"currentAverageUtilization is the current value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods.  It will only be present if `targetAverageValue` was set in the corresponding metric specification.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"currentAverageValue\": { SchemaProps: spec.SchemaProps{ Description: \"currentAverageValue is the current value of the average of the resource metric across all relevant pods, as a raw value (instead of as a percentage of the request), similar to the \"pods\" metric source type. It will always be set, regardless of the corresponding metric specification.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"container\": { SchemaProps: spec.SchemaProps{ Description: \"container is the name of the container in the pods of the scaling target\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"currentAverageValue\", \"container\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_autoscaling_v2beta1_CrossVersionObjectReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CrossVersionObjectReference contains enough information to let you identify the referred resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\"\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the referent; More info: http://kubernetes.io/docs/user-guide/identifiers#names\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"API version of the referent\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"kind\", \"name\"}, }, }, } } func schema_k8sio_api_autoscaling_v2beta1_ExternalMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExternalMetricSource indicates how to scale on a metric not associated with any Kubernetes object (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster). Exactly one \"target\" type should be set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metricName\": { SchemaProps: spec.SchemaProps{ Description: \"metricName is the name of the metric in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metricSelector\": { SchemaProps: spec.SchemaProps{ Description: \"metricSelector is used to identify a specific time series within a given metric.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"targetValue\": { SchemaProps: spec.SchemaProps{ Description: \"targetValue is the target value of the metric (as a quantity). Mutually exclusive with TargetAverageValue.\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"targetAverageValue\": { SchemaProps: spec.SchemaProps{ Description: \"targetAverageValue is the target per-pod value of global metric (as a quantity). Mutually exclusive with TargetValue.\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, Required: []string{\"metricName\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_autoscaling_v2beta1_ExternalMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExternalMetricStatus indicates the current value of a global metric not associated with any Kubernetes object.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metricName\": { SchemaProps: spec.SchemaProps{ Description: \"metricName is the name of a metric used for autoscaling in metric system.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metricSelector\": { SchemaProps: spec.SchemaProps{ Description: \"metricSelector is used to identify a specific time series within a given metric.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"currentValue\": { SchemaProps: spec.SchemaProps{ Description: \"currentValue is the current value of the metric (as a quantity)\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"currentAverageValue\": { SchemaProps: spec.SchemaProps{ Description: \"currentAverageValue is the current value of metric averaged over autoscaled pods.\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, Required: []string{\"metricName\", \"currentValue\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_autoscaling_v2beta1_HorizontalPodAutoscaler(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscaler is the configuration for a horizontal pod autoscaler, which automatically manages the replica count of any resource implementing the scale subresource based on the metrics specified.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"metadata is the standard object metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"spec is the specification for the behaviour of the autoscaler. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta1.HorizontalPodAutoscalerSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"status is the current information about the autoscaler.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta1.HorizontalPodAutoscalerStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta1.HorizontalPodAutoscalerSpec\", \"k8s.io/api/autoscaling/v2beta1.HorizontalPodAutoscalerStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_autoscaling_v2beta1_HorizontalPodAutoscalerCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerCondition describes the state of a HorizontalPodAutoscaler at a certain point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type describes the current condition\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"status is the status of the condition (True, False, Unknown)\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"lastTransitionTime is the last time the condition transitioned from one status to another\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"reason is the reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"message is a human-readable explanation containing details about the transition\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_autoscaling_v2beta1_HorizontalPodAutoscalerList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscaler is a list of horizontal pod autoscaler objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"metadata is the standard list metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is the list of horizontal pod autoscaler objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/autoscaling/v2beta1.HorizontalPodAutoscaler\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta1.HorizontalPodAutoscaler\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_autoscaling_v2beta1_HorizontalPodAutoscalerSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerSpec describes the desired functionality of the HorizontalPodAutoscaler.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"scaleTargetRef\": { SchemaProps: spec.SchemaProps{ Description: \"scaleTargetRef points to the target resource to scale, and is used to the pods for which metrics should be collected, as well as to actually change the replica count.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta1.CrossVersionObjectReference\"), }, }, \"minReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"minReplicas is the lower limit for the number of replicas to which the autoscaler can scale down.  It defaults to 1 pod.  minReplicas is allowed to be 0 if the alpha feature gate HPAScaleToZero is enabled and at least one Object or External metric is configured.  Scaling is active as long as at least one metric value is available.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"maxReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"maxReplicas is the upper limit for the number of replicas to which the autoscaler can scale up. It cannot be less that minReplicas.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"metrics\": { SchemaProps: spec.SchemaProps{ Description: \"metrics contains the specifications for which to use to calculate the desired replica count (the maximum replica count across all metrics will be used).  The desired replica count is calculated multiplying the ratio between the target value and the current value by the current number of pods.  Ergo, metrics used must decrease as the pod count is increased, and vice-versa.  See the individual metric source types for more information about how each type of metric must respond.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/autoscaling/v2beta1.MetricSpec\"), }, }, }, }, }, }, Required: []string{\"scaleTargetRef\", \"maxReplicas\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta1.CrossVersionObjectReference\", \"k8s.io/api/autoscaling/v2beta1.MetricSpec\"}, } } func schema_k8sio_api_autoscaling_v2beta1_HorizontalPodAutoscalerStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerStatus describes the current status of a horizontal pod autoscaler.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"observedGeneration is the most recent generation observed by this autoscaler.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"lastScaleTime\": { SchemaProps: spec.SchemaProps{ Description: \"lastScaleTime is the last time the HorizontalPodAutoscaler scaled the number of pods, used by the autoscaler to control how often the number of pods is changed.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"currentReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"currentReplicas is current number of replicas of pods managed by this autoscaler, as last seen by the autoscaler.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"desiredReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"desiredReplicas is the desired number of replicas of pods managed by this autoscaler, as last calculated by the autoscaler.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"currentMetrics\": { SchemaProps: spec.SchemaProps{ Description: \"currentMetrics is the last read state of the metrics used by this autoscaler.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/autoscaling/v2beta1.MetricStatus\"), }, }, }, }, }, \"conditions\": { SchemaProps: spec.SchemaProps{ Description: \"conditions is the set of conditions required for this autoscaler to scale its target, and indicates whether or not those conditions are met.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/autoscaling/v2beta1.HorizontalPodAutoscalerCondition\"), }, }, }, }, }, }, Required: []string{\"currentReplicas\", \"desiredReplicas\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta1.HorizontalPodAutoscalerCondition\", \"k8s.io/api/autoscaling/v2beta1.MetricStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_autoscaling_v2beta1_MetricSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricSpec specifies how to scale based on a single metric (only `type` and one other matching field should be set at once).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type is the type of metric source.  It should be one of \"ContainerResource\", \"External\", \"Object\", \"Pods\" or \"Resource\", each mapping to a matching field in the object. Note: \"ContainerResource\" type is available on when the feature-gate HPAContainerMetrics is enabled\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"object\": { SchemaProps: spec.SchemaProps{ Description: \"object refers to a metric describing a single kubernetes object (for example, hits-per-second on an Ingress object).\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta1.ObjectMetricSource\"), }, }, \"pods\": { SchemaProps: spec.SchemaProps{ Description: \"pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second).  The values will be averaged together before being compared to the target value.\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta1.PodsMetricSource\"), }, }, \"resource\": { SchemaProps: spec.SchemaProps{ Description: \"resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta1.ResourceMetricSource\"), }, }, \"containerResource\": { SchemaProps: spec.SchemaProps{ Description: \"container resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing a single container in each pod of the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source. This is an alpha feature and can be enabled by the HPAContainerMetrics feature flag.\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta1.ContainerResourceMetricSource\"), }, }, \"external\": { SchemaProps: spec.SchemaProps{ Description: \"external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta1.ExternalMetricSource\"), }, }, }, Required: []string{\"type\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta1.ContainerResourceMetricSource\", \"k8s.io/api/autoscaling/v2beta1.ExternalMetricSource\", \"k8s.io/api/autoscaling/v2beta1.ObjectMetricSource\", \"k8s.io/api/autoscaling/v2beta1.PodsMetricSource\", \"k8s.io/api/autoscaling/v2beta1.ResourceMetricSource\"}, } } func schema_k8sio_api_autoscaling_v2beta1_MetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricStatus describes the last-read state of a single metric.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type is the type of metric source.  It will be one of \"ContainerResource\", \"External\", \"Object\", \"Pods\" or \"Resource\", each corresponds to a matching field in the object. Note: \"ContainerResource\" type is available on when the feature-gate HPAContainerMetrics is enabled\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"object\": { SchemaProps: spec.SchemaProps{ Description: \"object refers to a metric describing a single kubernetes object (for example, hits-per-second on an Ingress object).\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta1.ObjectMetricStatus\"), }, }, \"pods\": { SchemaProps: spec.SchemaProps{ Description: \"pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second).  The values will be averaged together before being compared to the target value.\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta1.PodsMetricStatus\"), }, }, \"resource\": { SchemaProps: spec.SchemaProps{ Description: \"resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta1.ResourceMetricStatus\"), }, }, \"containerResource\": { SchemaProps: spec.SchemaProps{ Description: \"container resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing a single container in each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta1.ContainerResourceMetricStatus\"), }, }, \"external\": { SchemaProps: spec.SchemaProps{ Description: \"external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta1.ExternalMetricStatus\"), }, }, }, Required: []string{\"type\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta1.ContainerResourceMetricStatus\", \"k8s.io/api/autoscaling/v2beta1.ExternalMetricStatus\", \"k8s.io/api/autoscaling/v2beta1.ObjectMetricStatus\", \"k8s.io/api/autoscaling/v2beta1.PodsMetricStatus\", \"k8s.io/api/autoscaling/v2beta1.ResourceMetricStatus\"}, } } func schema_k8sio_api_autoscaling_v2beta1_ObjectMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ObjectMetricSource indicates how to scale on a metric describing a kubernetes object (for example, hits-per-second on an Ingress object).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"target\": { SchemaProps: spec.SchemaProps{ Description: \"target is the described Kubernetes object.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta1.CrossVersionObjectReference\"), }, }, \"metricName\": { SchemaProps: spec.SchemaProps{ Description: \"metricName is the name of the metric in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"targetValue\": { SchemaProps: spec.SchemaProps{ Description: \"targetValue is the target value of the metric (as a quantity).\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"selector is the string-encoded form of a standard kubernetes label selector for the given metric When set, it is passed as an additional parameter to the metrics server for more specific metrics scoping When unset, just the metricName will be used to gather metrics.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"averageValue\": { SchemaProps: spec.SchemaProps{ Description: \"averageValue is the target value of the average of the metric across all relevant pods (as a quantity)\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, Required: []string{\"target\", \"metricName\", \"targetValue\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta1.CrossVersionObjectReference\", \"k8s.io/apimachinery/pkg/api/resource.Quantity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_autoscaling_v2beta1_ObjectMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ObjectMetricStatus indicates the current value of a metric describing a kubernetes object (for example, hits-per-second on an Ingress object).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"target\": { SchemaProps: spec.SchemaProps{ Description: \"target is the described Kubernetes object.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta1.CrossVersionObjectReference\"), }, }, \"metricName\": { SchemaProps: spec.SchemaProps{ Description: \"metricName is the name of the metric in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"currentValue\": { SchemaProps: spec.SchemaProps{ Description: \"currentValue is the current value of the metric (as a quantity).\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"selector is the string-encoded form of a standard kubernetes label selector for the given metric When set in the ObjectMetricSource, it is passed as an additional parameter to the metrics server for more specific metrics scoping. When unset, just the metricName will be used to gather metrics.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"averageValue\": { SchemaProps: spec.SchemaProps{ Description: \"averageValue is the current value of the average of the metric across all relevant pods (as a quantity)\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, Required: []string{\"target\", \"metricName\", \"currentValue\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta1.CrossVersionObjectReference\", \"k8s.io/apimachinery/pkg/api/resource.Quantity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_autoscaling_v2beta1_PodsMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodsMetricSource indicates how to scale on a metric describing each pod in the current scale target (for example, transactions-processed-per-second). The values will be averaged together before being compared to the target value.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metricName\": { SchemaProps: spec.SchemaProps{ Description: \"metricName is the name of the metric in question\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"targetAverageValue\": { SchemaProps: spec.SchemaProps{ Description: \"targetAverageValue is the target value of the average of the metric across all relevant pods (as a quantity)\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"selector is the string-encoded form of a standard kubernetes label selector for the given metric When set, it is passed as an additional parameter to the metrics server for more specific metrics scoping When unset, just the metricName will be used to gather metrics.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, }, Required: []string{\"metricName\", \"targetAverageValue\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_autoscaling_v2beta1_PodsMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodsMetricStatus indicates the current value of a metric describing each pod in the current scale target (for example, transactions-processed-per-second).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metricName\": { SchemaProps: spec.SchemaProps{ Description: \"metricName is the name of the metric in question\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"currentAverageValue\": { SchemaProps: spec.SchemaProps{ Description: \"currentAverageValue is the current value of the average of the metric across all relevant pods (as a quantity)\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"selector is the string-encoded form of a standard kubernetes label selector for the given metric When set in the PodsMetricSource, it is passed as an additional parameter to the metrics server for more specific metrics scoping. When unset, just the metricName will be used to gather metrics.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, }, Required: []string{\"metricName\", \"currentAverageValue\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_autoscaling_v2beta1_ResourceMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceMetricSource indicates how to scale on a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory).  The values will be averaged together before being compared to the target.  Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.  Only one \"target\" type should be set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the name of the resource in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"targetAverageUtilization\": { SchemaProps: spec.SchemaProps{ Description: \"targetAverageUtilization is the target value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"targetAverageValue\": { SchemaProps: spec.SchemaProps{ Description: \"targetAverageValue is the target value of the average of the resource metric across all relevant pods, as a raw value (instead of as a percentage of the request), similar to the \"pods\" metric source type.\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, Required: []string{\"name\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_autoscaling_v2beta1_ResourceMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceMetricStatus indicates the current value of a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory).  Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the name of the resource in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"currentAverageUtilization\": { SchemaProps: spec.SchemaProps{ Description: \"currentAverageUtilization is the current value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods.  It will only be present if `targetAverageValue` was set in the corresponding metric specification.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"currentAverageValue\": { SchemaProps: spec.SchemaProps{ Description: \"currentAverageValue is the current value of the average of the resource metric across all relevant pods, as a raw value (instead of as a percentage of the request), similar to the \"pods\" metric source type. It will always be set, regardless of the corresponding metric specification.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, Required: []string{\"name\", \"currentAverageValue\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_autoscaling_v2beta2_ContainerResourceMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ContainerResourceMetricSource indicates how to scale on a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory).  The values will be averaged together before being compared to the target.  Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.  Only one \"target\" type should be set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the name of the resource in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"target\": { SchemaProps: spec.SchemaProps{ Description: \"target specifies the target value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.MetricTarget\"), }, }, \"container\": { SchemaProps: spec.SchemaProps{ Description: \"container is the name of the container in the pods of the scaling target\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"target\", \"container\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta2.MetricTarget\"}, } } func schema_k8sio_api_autoscaling_v2beta2_ContainerResourceMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ContainerResourceMetricStatus indicates the current value of a resource metric known to Kubernetes, as specified in requests and limits, describing a single container in each pod in the current scale target (e.g. CPU or memory).  Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the name of the resource in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"current\": { SchemaProps: spec.SchemaProps{ Description: \"current contains the current value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.MetricValueStatus\"), }, }, \"container\": { SchemaProps: spec.SchemaProps{ Description: \"Container is the name of the container in the pods of the scaling target\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"current\", \"container\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta2.MetricValueStatus\"}, } } func schema_k8sio_api_autoscaling_v2beta2_CrossVersionObjectReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CrossVersionObjectReference contains enough information to let you identify the referred resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\"\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the referent; More info: http://kubernetes.io/docs/user-guide/identifiers#names\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"API version of the referent\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"kind\", \"name\"}, }, }, } } func schema_k8sio_api_autoscaling_v2beta2_ExternalMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExternalMetricSource indicates how to scale on a metric not associated with any Kubernetes object (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metric\": { SchemaProps: spec.SchemaProps{ Description: \"metric identifies the target metric by name and selector\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.MetricIdentifier\"), }, }, \"target\": { SchemaProps: spec.SchemaProps{ Description: \"target specifies the target value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.MetricTarget\"), }, }, }, Required: []string{\"metric\", \"target\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta2.MetricIdentifier\", \"k8s.io/api/autoscaling/v2beta2.MetricTarget\"}, } } func schema_k8sio_api_autoscaling_v2beta2_ExternalMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExternalMetricStatus indicates the current value of a global metric not associated with any Kubernetes object.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metric\": { SchemaProps: spec.SchemaProps{ Description: \"metric identifies the target metric by name and selector\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.MetricIdentifier\"), }, }, \"current\": { SchemaProps: spec.SchemaProps{ Description: \"current contains the current value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.MetricValueStatus\"), }, }, }, Required: []string{\"metric\", \"current\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta2.MetricIdentifier\", \"k8s.io/api/autoscaling/v2beta2.MetricValueStatus\"}, } } func schema_k8sio_api_autoscaling_v2beta2_HPAScalingPolicy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HPAScalingPolicy is a single policy which must hold true for a specified past interval.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type is used to specify the scaling policy.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"value\": { SchemaProps: spec.SchemaProps{ Description: \"Value contains the amount of change which is permitted by the policy. It must be greater than zero\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"periodSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"PeriodSeconds specifies the window of time for which the policy should hold true. PeriodSeconds must be greater than zero and less than or equal to 1800 (30 min).\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"type\", \"value\", \"periodSeconds\"}, }, }, } } func schema_k8sio_api_autoscaling_v2beta2_HPAScalingRules(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HPAScalingRules configures the scaling behavior for one direction. These Rules are applied after calculating DesiredReplicas from metrics for the HPA. They can limit the scaling velocity by specifying scaling policies. They can prevent flapping by specifying the stabilization window, so that the number of replicas is not set instantly, instead, the safest value from the stabilization window is chosen.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"stabilizationWindowSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"StabilizationWindowSeconds is the number of seconds for which past recommendations should be considered while scaling up or scaling down. StabilizationWindowSeconds must be greater than or equal to zero and less than or equal to 3600 (one hour). If not set, use the default values: - For scale up: 0 (i.e. no stabilization is done). - For scale down: 300 (i.e. the stabilization window is 300 seconds long).\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"selectPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"selectPolicy is used to specify which policy should be used. If not set, the default value MaxPolicySelect is used.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"policies\": { SchemaProps: spec.SchemaProps{ Description: \"policies is a list of potential scaling polices which can be used during scaling. At least one policy must be specified, otherwise the HPAScalingRules will be discarded as invalid\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/autoscaling/v2beta2.HPAScalingPolicy\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta2.HPAScalingPolicy\"}, } } func schema_k8sio_api_autoscaling_v2beta2_HorizontalPodAutoscaler(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscaler is the configuration for a horizontal pod autoscaler, which automatically manages the replica count of any resource implementing the scale subresource based on the metrics specified.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"metadata is the standard object metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"spec is the specification for the behaviour of the autoscaler. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.HorizontalPodAutoscalerSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"status is the current information about the autoscaler.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.HorizontalPodAutoscalerStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta2.HorizontalPodAutoscalerSpec\", \"k8s.io/api/autoscaling/v2beta2.HorizontalPodAutoscalerStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_autoscaling_v2beta2_HorizontalPodAutoscalerBehavior(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerBehavior configures the scaling behavior of the target in both Up and Down directions (scaleUp and scaleDown fields respectively).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"scaleUp\": { SchemaProps: spec.SchemaProps{ Description: \"scaleUp is scaling policy for scaling Up. If not set, the default value is the higher of:n  * increase no more than 4 pods per 60 secondsn  * double the number of pods per 60 secondsnNo stabilization is used.\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.HPAScalingRules\"), }, }, \"scaleDown\": { SchemaProps: spec.SchemaProps{ Description: \"scaleDown is scaling policy for scaling Down. If not set, the default value is to allow to scale down to minReplicas pods, with a 300 second stabilization window (i.e., the highest recommendation for the last 300sec is used).\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.HPAScalingRules\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta2.HPAScalingRules\"}, } } func schema_k8sio_api_autoscaling_v2beta2_HorizontalPodAutoscalerCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerCondition describes the state of a HorizontalPodAutoscaler at a certain point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type describes the current condition\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"status is the status of the condition (True, False, Unknown)\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"lastTransitionTime is the last time the condition transitioned from one status to another\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"reason is the reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"message is a human-readable explanation containing details about the transition\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_autoscaling_v2beta2_HorizontalPodAutoscalerList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerList is a list of horizontal pod autoscaler objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"metadata is the standard list metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is the list of horizontal pod autoscaler objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/autoscaling/v2beta2.HorizontalPodAutoscaler\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta2.HorizontalPodAutoscaler\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_autoscaling_v2beta2_HorizontalPodAutoscalerSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerSpec describes the desired functionality of the HorizontalPodAutoscaler.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"scaleTargetRef\": { SchemaProps: spec.SchemaProps{ Description: \"scaleTargetRef points to the target resource to scale, and is used to the pods for which metrics should be collected, as well as to actually change the replica count.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.CrossVersionObjectReference\"), }, }, \"minReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"minReplicas is the lower limit for the number of replicas to which the autoscaler can scale down.  It defaults to 1 pod.  minReplicas is allowed to be 0 if the alpha feature gate HPAScaleToZero is enabled and at least one Object or External metric is configured.  Scaling is active as long as at least one metric value is available.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"maxReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"maxReplicas is the upper limit for the number of replicas to which the autoscaler can scale up. It cannot be less that minReplicas.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"metrics\": { SchemaProps: spec.SchemaProps{ Description: \"metrics contains the specifications for which to use to calculate the desired replica count (the maximum replica count across all metrics will be used).  The desired replica count is calculated multiplying the ratio between the target value and the current value by the current number of pods.  Ergo, metrics used must decrease as the pod count is increased, and vice-versa.  See the individual metric source types for more information about how each type of metric must respond. If not set, the default metric will be set to 80% average CPU utilization.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/autoscaling/v2beta2.MetricSpec\"), }, }, }, }, }, \"behavior\": { SchemaProps: spec.SchemaProps{ Description: \"behavior configures the scaling behavior of the target in both Up and Down directions (scaleUp and scaleDown fields respectively). If not set, the default HPAScalingRules for scale up and scale down are used.\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.HorizontalPodAutoscalerBehavior\"), }, }, }, Required: []string{\"scaleTargetRef\", \"maxReplicas\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta2.CrossVersionObjectReference\", \"k8s.io/api/autoscaling/v2beta2.HorizontalPodAutoscalerBehavior\", \"k8s.io/api/autoscaling/v2beta2.MetricSpec\"}, } } func schema_k8sio_api_autoscaling_v2beta2_HorizontalPodAutoscalerStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerStatus describes the current status of a horizontal pod autoscaler.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"observedGeneration is the most recent generation observed by this autoscaler.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"lastScaleTime\": { SchemaProps: spec.SchemaProps{ Description: \"lastScaleTime is the last time the HorizontalPodAutoscaler scaled the number of pods, used by the autoscaler to control how often the number of pods is changed.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"currentReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"currentReplicas is current number of replicas of pods managed by this autoscaler, as last seen by the autoscaler.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"desiredReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"desiredReplicas is the desired number of replicas of pods managed by this autoscaler, as last calculated by the autoscaler.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"currentMetrics\": { SchemaProps: spec.SchemaProps{ Description: \"currentMetrics is the last read state of the metrics used by this autoscaler.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/autoscaling/v2beta2.MetricStatus\"), }, }, }, }, }, \"conditions\": { SchemaProps: spec.SchemaProps{ Description: \"conditions is the set of conditions required for this autoscaler to scale its target, and indicates whether or not those conditions are met.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/autoscaling/v2beta2.HorizontalPodAutoscalerCondition\"), }, }, }, }, }, }, Required: []string{\"currentReplicas\", \"desiredReplicas\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta2.HorizontalPodAutoscalerCondition\", \"k8s.io/api/autoscaling/v2beta2.MetricStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_autoscaling_v2beta2_MetricIdentifier(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricIdentifier defines the name and optionally selector for a metric\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the name of the given metric\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"selector is the string-encoded form of a standard kubernetes label selector for the given metric When set, it is passed as an additional parameter to the metrics server for more specific metrics scoping. When unset, just the metricName will be used to gather metrics.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, }, Required: []string{\"name\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_autoscaling_v2beta2_MetricSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricSpec specifies how to scale based on a single metric (only `type` and one other matching field should be set at once).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type is the type of metric source.  It should be one of \"ContainerResource\", \"External\", \"Object\", \"Pods\" or \"Resource\", each mapping to a matching field in the object. Note: \"ContainerResource\" type is available on when the feature-gate HPAContainerMetrics is enabled\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"object\": { SchemaProps: spec.SchemaProps{ Description: \"object refers to a metric describing a single kubernetes object (for example, hits-per-second on an Ingress object).\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.ObjectMetricSource\"), }, }, \"pods\": { SchemaProps: spec.SchemaProps{ Description: \"pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second).  The values will be averaged together before being compared to the target value.\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.PodsMetricSource\"), }, }, \"resource\": { SchemaProps: spec.SchemaProps{ Description: \"resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.ResourceMetricSource\"), }, }, \"containerResource\": { SchemaProps: spec.SchemaProps{ Description: \"container resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing a single container in each pod of the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source. This is an alpha feature and can be enabled by the HPAContainerMetrics feature flag.\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.ContainerResourceMetricSource\"), }, }, \"external\": { SchemaProps: spec.SchemaProps{ Description: \"external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.ExternalMetricSource\"), }, }, }, Required: []string{\"type\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta2.ContainerResourceMetricSource\", \"k8s.io/api/autoscaling/v2beta2.ExternalMetricSource\", \"k8s.io/api/autoscaling/v2beta2.ObjectMetricSource\", \"k8s.io/api/autoscaling/v2beta2.PodsMetricSource\", \"k8s.io/api/autoscaling/v2beta2.ResourceMetricSource\"}, } } func schema_k8sio_api_autoscaling_v2beta2_MetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricStatus describes the last-read state of a single metric.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type is the type of metric source.  It will be one of \"ContainerResource\", \"External\", \"Object\", \"Pods\" or \"Resource\", each corresponds to a matching field in the object. Note: \"ContainerResource\" type is available on when the feature-gate HPAContainerMetrics is enabled\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"object\": { SchemaProps: spec.SchemaProps{ Description: \"object refers to a metric describing a single kubernetes object (for example, hits-per-second on an Ingress object).\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.ObjectMetricStatus\"), }, }, \"pods\": { SchemaProps: spec.SchemaProps{ Description: \"pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second).  The values will be averaged together before being compared to the target value.\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.PodsMetricStatus\"), }, }, \"resource\": { SchemaProps: spec.SchemaProps{ Description: \"resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.ResourceMetricStatus\"), }, }, \"containerResource\": { SchemaProps: spec.SchemaProps{ Description: \"container resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing a single container in each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.ContainerResourceMetricStatus\"), }, }, \"external\": { SchemaProps: spec.SchemaProps{ Description: \"external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).\", Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.ExternalMetricStatus\"), }, }, }, Required: []string{\"type\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta2.ContainerResourceMetricStatus\", \"k8s.io/api/autoscaling/v2beta2.ExternalMetricStatus\", \"k8s.io/api/autoscaling/v2beta2.ObjectMetricStatus\", \"k8s.io/api/autoscaling/v2beta2.PodsMetricStatus\", \"k8s.io/api/autoscaling/v2beta2.ResourceMetricStatus\"}, } } func schema_k8sio_api_autoscaling_v2beta2_MetricTarget(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricTarget defines the target value, average value, or average utilization of a specific metric\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type represents whether the metric type is Utilization, Value, or AverageValue\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"value\": { SchemaProps: spec.SchemaProps{ Description: \"value is the target value of the metric (as a quantity).\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"averageValue\": { SchemaProps: spec.SchemaProps{ Description: \"averageValue is the target value of the average of the metric across all relevant pods (as a quantity)\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"averageUtilization\": { SchemaProps: spec.SchemaProps{ Description: \"averageUtilization is the target value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods. Currently only valid for Resource metric source type\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"type\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_autoscaling_v2beta2_MetricValueStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricValueStatus holds the current value for a metric\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"value\": { SchemaProps: spec.SchemaProps{ Description: \"value is the current value of the metric (as a quantity).\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"averageValue\": { SchemaProps: spec.SchemaProps{ Description: \"averageValue is the current value of the average of the metric across all relevant pods (as a quantity)\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"averageUtilization\": { SchemaProps: spec.SchemaProps{ Description: \"currentAverageUtilization is the current value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_autoscaling_v2beta2_ObjectMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ObjectMetricSource indicates how to scale on a metric describing a kubernetes object (for example, hits-per-second on an Ingress object).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"describedObject\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/autoscaling/v2beta2.CrossVersionObjectReference\"), }, }, \"target\": { SchemaProps: spec.SchemaProps{ Description: \"target specifies the target value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.MetricTarget\"), }, }, \"metric\": { SchemaProps: spec.SchemaProps{ Description: \"metric identifies the target metric by name and selector\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.MetricIdentifier\"), }, }, }, Required: []string{\"describedObject\", \"target\", \"metric\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta2.CrossVersionObjectReference\", \"k8s.io/api/autoscaling/v2beta2.MetricIdentifier\", \"k8s.io/api/autoscaling/v2beta2.MetricTarget\"}, } } func schema_k8sio_api_autoscaling_v2beta2_ObjectMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ObjectMetricStatus indicates the current value of a metric describing a kubernetes object (for example, hits-per-second on an Ingress object).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metric\": { SchemaProps: spec.SchemaProps{ Description: \"metric identifies the target metric by name and selector\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.MetricIdentifier\"), }, }, \"current\": { SchemaProps: spec.SchemaProps{ Description: \"current contains the current value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.MetricValueStatus\"), }, }, \"describedObject\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/autoscaling/v2beta2.CrossVersionObjectReference\"), }, }, }, Required: []string{\"metric\", \"current\", \"describedObject\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta2.CrossVersionObjectReference\", \"k8s.io/api/autoscaling/v2beta2.MetricIdentifier\", \"k8s.io/api/autoscaling/v2beta2.MetricValueStatus\"}, } } func schema_k8sio_api_autoscaling_v2beta2_PodsMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodsMetricSource indicates how to scale on a metric describing each pod in the current scale target (for example, transactions-processed-per-second). The values will be averaged together before being compared to the target value.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metric\": { SchemaProps: spec.SchemaProps{ Description: \"metric identifies the target metric by name and selector\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.MetricIdentifier\"), }, }, \"target\": { SchemaProps: spec.SchemaProps{ Description: \"target specifies the target value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.MetricTarget\"), }, }, }, Required: []string{\"metric\", \"target\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta2.MetricIdentifier\", \"k8s.io/api/autoscaling/v2beta2.MetricTarget\"}, } } func schema_k8sio_api_autoscaling_v2beta2_PodsMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodsMetricStatus indicates the current value of a metric describing each pod in the current scale target (for example, transactions-processed-per-second).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metric\": { SchemaProps: spec.SchemaProps{ Description: \"metric identifies the target metric by name and selector\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.MetricIdentifier\"), }, }, \"current\": { SchemaProps: spec.SchemaProps{ Description: \"current contains the current value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.MetricValueStatus\"), }, }, }, Required: []string{\"metric\", \"current\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta2.MetricIdentifier\", \"k8s.io/api/autoscaling/v2beta2.MetricValueStatus\"}, } } func schema_k8sio_api_autoscaling_v2beta2_ResourceMetricSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceMetricSource indicates how to scale on a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory).  The values will be averaged together before being compared to the target.  Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.  Only one \"target\" type should be set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the name of the resource in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"target\": { SchemaProps: spec.SchemaProps{ Description: \"target specifies the target value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.MetricTarget\"), }, }, }, Required: []string{\"name\", \"target\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta2.MetricTarget\"}, } } func schema_k8sio_api_autoscaling_v2beta2_ResourceMetricStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceMetricStatus indicates the current value of a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory).  Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the \"pods\" source.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the name of the resource in question.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"current\": { SchemaProps: spec.SchemaProps{ Description: \"current contains the current value for the given metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/autoscaling/v2beta2.MetricValueStatus\"), }, }, }, Required: []string{\"name\", \"current\"}, }, }, Dependencies: []string{ \"k8s.io/api/autoscaling/v2beta2.MetricValueStatus\"}, } } func schema_k8sio_api_batch_v1_CronJob(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CronJob represents the configuration of a single cron job.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the desired behavior of a cron job, including the schedule. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/batch/v1.CronJobSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Current status of a cron job. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/batch/v1.CronJobStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/batch/v1.CronJobSpec\", \"k8s.io/api/batch/v1.CronJobStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_batch_v1_CronJobList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CronJobList is a collection of cron jobs.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is the list of CronJobs.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/batch/v1.CronJob\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/batch/v1.CronJob\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_batch_v1_CronJobSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CronJobSpec describes how the job execution will look like and when it will actually run.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"schedule\": { SchemaProps: spec.SchemaProps{ Description: \"The schedule in Cron format, see https://en.wikipedia.org/wiki/Cron.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"startingDeadlineSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Optional deadline in seconds for starting the job if it misses scheduled time for any reason.  Missed jobs executions will be counted as failed ones.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"concurrencyPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies how to treat concurrent executions of a Job. Valid values are: - \"Allow\" (default): allows CronJobs to run concurrently; - \"Forbid\": forbids concurrent runs, skipping next run if previous run hasn't finished yet; - \"Replace\": cancels currently running job and replaces it with a new onennPossible enum values:n - `\"Allow\"` allows CronJobs to run concurrently.n - `\"Forbid\"` forbids concurrent runs, skipping next run if previous hasn't finished yet.n - `\"Replace\"` cancels currently running job and replaces it with a new one.\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"Allow\", \"Forbid\", \"Replace\"}}, }, \"suspend\": { SchemaProps: spec.SchemaProps{ Description: \"This flag tells the controller to suspend subsequent executions, it does not apply to already started executions.  Defaults to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"jobTemplate\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies the job that will be created when executing a CronJob.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/batch/v1.JobTemplateSpec\"), }, }, \"successfulJobsHistoryLimit\": { SchemaProps: spec.SchemaProps{ Description: \"The number of successful finished jobs to retain. Value must be non-negative integer. Defaults to 3.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"failedJobsHistoryLimit\": { SchemaProps: spec.SchemaProps{ Description: \"The number of failed finished jobs to retain. Value must be non-negative integer. Defaults to 1.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"schedule\", \"jobTemplate\"}, }, }, Dependencies: []string{ \"k8s.io/api/batch/v1.JobTemplateSpec\"}, } } func schema_k8sio_api_batch_v1_CronJobStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CronJobStatus represents the current state of a cron job.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"active\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"A list of pointers to currently running jobs.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.ObjectReference\"), }, }, }, }, }, \"lastScheduleTime\": { SchemaProps: spec.SchemaProps{ Description: \"Information when was the last time the job was successfully scheduled.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"lastSuccessfulTime\": { SchemaProps: spec.SchemaProps{ Description: \"Information when was the last time the job successfully completed.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ObjectReference\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_batch_v1_Job(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Job represents the configuration of a single job.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the desired behavior of a job. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/batch/v1.JobSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Current status of a job. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/batch/v1.JobStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/batch/v1.JobSpec\", \"k8s.io/api/batch/v1.JobStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_batch_v1_JobCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"JobCondition describes current state of a job.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of job condition, Complete or Failed.nnPossible enum values:n - `\"Complete\"` means the job has completed its execution.n - `\"Failed\"` means the job has failed its execution.n - `\"Suspended\"` means the job has been suspended.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"Complete\", \"Failed\", \"Suspended\"}}, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastProbeTime\": { SchemaProps: spec.SchemaProps{ Description: \"Last time the condition was checked.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"Last time the condition transit from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"(brief) reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"Human readable message indicating details about last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_batch_v1_JobList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"JobList is a collection of jobs.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is the list of Jobs.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/batch/v1.Job\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/batch/v1.Job\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_batch_v1_JobSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"JobSpec describes how the job execution will look like.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"parallelism\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies the maximum desired number of pods the job should run at any given time. The actual number of pods running in steady state will be less than this number when ((.spec.completions - .status.successful) < .spec.parallelism), i.e. when the work left to do is less than max parallelism. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"completions\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies the desired number of successfully finished pods the job should be run with.  Setting to nil means that the success of any pod signals the success of all pods, and allows parallelism to have any positive value.  Setting to 1 means that parallelism is limited to 1 and the success of that pod signals the success of the job. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"activeDeadlineSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies the duration in seconds relative to the startTime that the job may be continuously active before the system tries to terminate it; value must be positive integer. If a Job is suspended (at creation or through an update), this timer will effectively be stopped and reset when the Job is resumed again.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"backoffLimit\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies the number of retries before marking this job failed. Defaults to 6\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"A label query over pods that should match the pod count. Normally, the system sets this field for you. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"manualSelector\": { SchemaProps: spec.SchemaProps{ Description: \"manualSelector controls generation of pod labels and pod selectors. Leave `manualSelector` unset unless you are certain what you are doing. When false or unset, the system pick labels unique to this job and appends those labels to the pod template.  When true, the user is responsible for picking unique labels and specifying the selector.  Failure to pick a unique label may cause this and other jobs to not function correctly.  However, You may see `manualSelector=true` in jobs that were created with the old `extensions/v1beta1` API. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/#specifying-your-own-pod-selector\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"template\": { SchemaProps: spec.SchemaProps{ Description: \"Describes the pod that will be created when executing a job. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodTemplateSpec\"), }, }, \"ttlSecondsAfterFinished\": { SchemaProps: spec.SchemaProps{ Description: \"ttlSecondsAfterFinished limits the lifetime of a Job that has finished execution (either Complete or Failed). If this field is set, ttlSecondsAfterFinished after the Job finishes, it is eligible to be automatically deleted. When the Job is being deleted, its lifecycle guarantees (e.g. finalizers) will be honored. If this field is unset, the Job won't be automatically deleted. If this field is set to zero, the Job becomes eligible to be deleted immediately after it finishes.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"completionMode\": { SchemaProps: spec.SchemaProps{ Description: \"CompletionMode specifies how Pod completions are tracked. It can be `NonIndexed` (default) or `Indexed`.nn`NonIndexed` means that the Job is considered complete when there have been .spec.completions successfully completed Pods. Each Pod completion is homologous to each other.nn`Indexed` means that the Pods of a Job get an associated completion index from 0 to (.spec.completions - 1), available in the annotation batch.kubernetes.io/job-completion-index. The Job is considered complete when there is one successfully completed Pod for each index. When value is `Indexed`, .spec.completions must be specified and `.spec.parallelism` must be less than or equal to 10^5. In addition, The Pod name takes the form `$(job-name)-$(index)-$(random-string)`, the Pod hostname takes the form `$(job-name)-$(index)`.nnThis field is beta-level. More completion modes can be added in the future. If the Job controller observes a mode that it doesn't recognize, the controller skips updates for the Job.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"suspend\": { SchemaProps: spec.SchemaProps{ Description: \"Suspend specifies whether the Job controller should create Pods or not. If a Job is created with suspend set to true, no Pods are created by the Job controller. If a Job is suspended after creation (i.e. the flag goes from false to true), the Job controller will delete all active Pods associated with this Job. Users must design their workload to gracefully handle this. Suspending a Job will reset the StartTime field of the Job, effectively resetting the ActiveDeadlineSeconds timer too. Defaults to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"template\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PodTemplateSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_batch_v1_JobStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"JobStatus represents the current state of a Job.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\":       \"atomic\", \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"The latest available observations of an object's current state. When a Job fails, one of the conditions will have type \"Failed\" and status true. When a Job is suspended, one of the conditions will have type \"Suspended\" and status true; when the Job is resumed, the status of this condition will become false. When a Job is completed, one of the conditions will have type \"Complete\" and status true. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/batch/v1.JobCondition\"), }, }, }, }, }, \"startTime\": { SchemaProps: spec.SchemaProps{ Description: \"Represents time when the job controller started processing a job. When a Job is created in the suspended state, this field is not set until the first time it is resumed. This field is reset every time a Job is resumed from suspension. It is represented in RFC3339 form and is in UTC.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"completionTime\": { SchemaProps: spec.SchemaProps{ Description: \"Represents time when the job was completed. It is not guaranteed to be set in happens-before order across separate operations. It is represented in RFC3339 form and is in UTC. The completion time is only set when the job finishes successfully.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"active\": { SchemaProps: spec.SchemaProps{ Description: \"The number of pending and running pods.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"succeeded\": { SchemaProps: spec.SchemaProps{ Description: \"The number of pods which reached phase Succeeded.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"failed\": { SchemaProps: spec.SchemaProps{ Description: \"The number of pods which reached phase Failed.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"completedIndexes\": { SchemaProps: spec.SchemaProps{ Description: \"CompletedIndexes holds the completed indexes when .spec.completionMode = \"Indexed\" in a text format. The indexes are represented as decimal integers separated by commas. The numbers are listed in increasing order. Three or more consecutive numbers are compressed and represented by the first and last element of the series, separated by a hyphen. For example, if the completed indexes are 1, 3, 4, 5 and 7, they are represented as \"1,3-5,7\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"uncountedTerminatedPods\": { SchemaProps: spec.SchemaProps{ Description: \"UncountedTerminatedPods holds the UIDs of Pods that have terminated but the job controller hasn't yet accounted for in the status counters.nnThe job controller creates pods with a finalizer. When a pod terminates (succeeded or failed), the controller does three steps to account for it in the job status: (1) Add the pod UID to the arrays in this field. (2) Remove the pod finalizer. (3) Remove the pod UID from the arrays while increasing the correspondingn    counter.nnThis field is beta-level. The job controller only makes use of this field when the feature gate JobTrackingWithFinalizers is enabled (enabled by default). Old jobs might not be tracked using this field, in which case the field remains null.\", Ref:         ref(\"k8s.io/api/batch/v1.UncountedTerminatedPods\"), }, }, \"ready\": { SchemaProps: spec.SchemaProps{ Description: \"The number of pods which have a Ready condition.nnThis field is alpha-level. The job controller populates the field when the feature gate JobReadyPods is enabled (disabled by default).\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/batch/v1.JobCondition\", \"k8s.io/api/batch/v1.UncountedTerminatedPods\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_batch_v1_JobTemplateSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"JobTemplateSpec describes the data a Job should have when created from a template\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata of the jobs created from this template. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the desired behavior of the job. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/batch/v1.JobSpec\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/batch/v1.JobSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_batch_v1_UncountedTerminatedPods(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"UncountedTerminatedPods holds UIDs of Pods that have terminated but haven't been accounted in Job status counters.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"succeeded\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Succeeded holds UIDs of succeeded Pods.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"failed\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Failed holds UIDs of failed Pods.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, } } func schema_k8sio_api_batch_v1beta1_CronJob(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CronJob represents the configuration of a single cron job.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the desired behavior of a cron job, including the schedule. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/batch/v1beta1.CronJobSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Current status of a cron job. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/batch/v1beta1.CronJobStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/batch/v1beta1.CronJobSpec\", \"k8s.io/api/batch/v1beta1.CronJobStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_batch_v1beta1_CronJobList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CronJobList is a collection of cron jobs.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is the list of CronJobs.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/batch/v1beta1.CronJob\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/batch/v1beta1.CronJob\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_batch_v1beta1_CronJobSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CronJobSpec describes how the job execution will look like and when it will actually run.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"schedule\": { SchemaProps: spec.SchemaProps{ Description: \"The schedule in Cron format, see https://en.wikipedia.org/wiki/Cron.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"startingDeadlineSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Optional deadline in seconds for starting the job if it misses scheduled time for any reason.  Missed jobs executions will be counted as failed ones.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"concurrencyPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies how to treat concurrent executions of a Job. Valid values are: - \"Allow\" (default): allows CronJobs to run concurrently; - \"Forbid\": forbids concurrent runs, skipping next run if previous run hasn't finished yet; - \"Replace\": cancels currently running job and replaces it with a new one\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"suspend\": { SchemaProps: spec.SchemaProps{ Description: \"This flag tells the controller to suspend subsequent executions, it does not apply to already started executions.  Defaults to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"jobTemplate\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies the job that will be created when executing a CronJob.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/batch/v1beta1.JobTemplateSpec\"), }, }, \"successfulJobsHistoryLimit\": { SchemaProps: spec.SchemaProps{ Description: \"The number of successful finished jobs to retain. This is a pointer to distinguish between explicit zero and not specified. Defaults to 3.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"failedJobsHistoryLimit\": { SchemaProps: spec.SchemaProps{ Description: \"The number of failed finished jobs to retain. This is a pointer to distinguish between explicit zero and not specified. Defaults to 1.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"schedule\", \"jobTemplate\"}, }, }, Dependencies: []string{ \"k8s.io/api/batch/v1beta1.JobTemplateSpec\"}, } } func schema_k8sio_api_batch_v1beta1_CronJobStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CronJobStatus represents the current state of a cron job.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"active\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"A list of pointers to currently running jobs.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.ObjectReference\"), }, }, }, }, }, \"lastScheduleTime\": { SchemaProps: spec.SchemaProps{ Description: \"Information when was the last time the job was successfully scheduled.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"lastSuccessfulTime\": { SchemaProps: spec.SchemaProps{ Description: \"Information when was the last time the job successfully completed.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ObjectReference\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_batch_v1beta1_JobTemplate(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"JobTemplate describes a template for creating copies of a predefined pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"template\": { SchemaProps: spec.SchemaProps{ Description: \"Defines jobs that will be created from this template. https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/batch/v1beta1.JobTemplateSpec\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/batch/v1beta1.JobTemplateSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_batch_v1beta1_JobTemplateSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"JobTemplateSpec describes the data a Job should have when created from a template\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata of the jobs created from this template. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the desired behavior of the job. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/batch/v1.JobSpec\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/batch/v1.JobSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_certificates_v1_CertificateSigningRequest(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CertificateSigningRequest objects provide a mechanism to obtain x509 certificates by submitting a certificate signing request, and having it asynchronously approved and issued.nnKubelets use this API to obtain:n 1. client certificates to authenticate to kube-apiserver (with the \"kubernetes.io/kube-apiserver-client-kubelet\" signerName).n 2. serving certificates for TLS endpoints kube-apiserver can connect to securely (with the \"kubernetes.io/kubelet-serving\" signerName).nnThis API can be used to request client certificates to authenticate to kube-apiserver (with the \"kubernetes.io/kube-apiserver-client\" signerName), or to obtain certificates from custom non-Kubernetes signers.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"spec contains the certificate request, and is immutable after creation. Only the request, signerName, expirationSeconds, and usages fields can be set on creation. Other fields are derived by Kubernetes and cannot be modified by users.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/certificates/v1.CertificateSigningRequestSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"status contains information about whether the request is approved or denied, and the certificate issued by the signer, or the failure condition indicating signer failure.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/certificates/v1.CertificateSigningRequestStatus\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/certificates/v1.CertificateSigningRequestSpec\", \"k8s.io/api/certificates/v1.CertificateSigningRequestStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_certificates_v1_CertificateSigningRequestCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CertificateSigningRequestCondition describes a condition of a CertificateSigningRequest object\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type of the condition. Known conditions are \"Approved\", \"Denied\", and \"Failed\".nnAn \"Approved\" condition is added via the /approval subresource, indicating the request was approved and should be issued by the signer.nnA \"Denied\" condition is added via the /approval subresource, indicating the request was denied and should not be issued by the signer.nnA \"Failed\" condition is added via the /status subresource, indicating the signer failed to issue the certificate.nnApproved and Denied conditions are mutually exclusive. Approved, Denied, and Failed conditions cannot be removed once added.nnOnly one condition of a given type is allowed.nnPossible enum values:n - `\"Approved\"` Approved indicates the request was approved and should be issued by the signer.n - `\"Denied\"` Denied indicates the request was denied and should not be issued by the signer.n - `\"Failed\"` Failed indicates the signer failed to issue the certificate.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"Approved\", \"Denied\", \"Failed\"}}, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"status of the condition, one of True, False, Unknown. Approved, Denied, and Failed conditions may not be \"False\" or \"Unknown\".\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"reason indicates a brief reason for the request state\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"message contains a human readable message with details about the request state\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastUpdateTime\": { SchemaProps: spec.SchemaProps{ Description: \"lastUpdateTime is the time of the last update to this condition\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"lastTransitionTime is the time the condition last transitioned from one status to another. If unset, when a new condition type is added or an existing condition's status is changed, the server defaults this to the current time.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_certificates_v1_CertificateSigningRequestList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CertificateSigningRequestList is a collection of CertificateSigningRequest objects\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is a collection of CertificateSigningRequest objects\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/certificates/v1.CertificateSigningRequest\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/certificates/v1.CertificateSigningRequest\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_certificates_v1_CertificateSigningRequestSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CertificateSigningRequestSpec contains the certificate request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"request\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"request contains an x509 certificate signing request encoded in a \"CERTIFICATE REQUEST\" PEM block. When serialized as JSON or YAML, the data is additionally base64-encoded.\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, \"signerName\": { SchemaProps: spec.SchemaProps{ Description: \"signerName indicates the requested signer, and is a qualified name.nnList/watch requests for CertificateSigningRequests can filter on this field using a \"spec.signerName=NAME\" fieldSelector.nnWell-known Kubernetes signers are:n 1. \"kubernetes.io/kube-apiserver-client\": issues client certificates that can be used to authenticate to kube-apiserver.n  Requests for this signer are never auto-approved by kube-controller-manager, can be issued by the \"csrsigning\" controller in kube-controller-manager.n 2. \"kubernetes.io/kube-apiserver-client-kubelet\": issues client certificates that kubelets use to authenticate to kube-apiserver.n  Requests for this signer can be auto-approved by the \"csrapproving\" controller in kube-controller-manager, and can be issued by the \"csrsigning\" controller in kube-controller-manager.n 3. \"kubernetes.io/kubelet-serving\" issues serving certificates that kubelets use to serve TLS endpoints, which kube-apiserver can connect to securely.n  Requests for this signer are never auto-approved by kube-controller-manager, and can be issued by the \"csrsigning\" controller in kube-controller-manager.nnMore details are available at https://k8s.io/docs/reference/access-authn-authz/certificate-signing-requests/#kubernetes-signersnnCustom signerNames can also be specified. The signer defines:n 1. Trust distribution: how trust (CA bundles) are distributed.n 2. Permitted subjects: and behavior when a disallowed subject is requested.n 3. Required, permitted, or forbidden x509 extensions in the request (including whether subjectAltNames are allowed, which types, restrictions on allowed values) and behavior when a disallowed extension is requested.n 4. Required, permitted, or forbidden key usages / extended key usages.n 5. Expiration/certificate lifetime: whether it is fixed by the signer, configurable by the admin.n 6. Whether or not requests for CA certificates are allowed.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"expirationSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"expirationSeconds is the requested duration of validity of the issued certificate. The certificate signer may issue a certificate with a different validity duration so a client must check the delta between the notBefore and and notAfter fields in the issued certificate to determine the actual duration.nnThe v1.22+ in-tree implementations of the well-known Kubernetes signers will honor this field as long as the requested duration is not greater than the maximum duration they will honor per the --cluster-signing-duration CLI flag to the Kubernetes controller manager.nnCertificate signers may not honor this field for various reasons:nn  1. Old signer that is unaware of the field (such as the in-treen     implementations prior to v1.22)n  2. Signer whose configured maximum is shorter than the requested durationn  3. Signer whose configured minimum is longer than the requested durationnnThe minimum valid value for expirationSeconds is 600, i.e. 10 minutes.nnAs of v1.22, this field is beta and is controlled via the CSRDuration feature gate.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"usages\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"usages specifies a set of key usages requested in the issued certificate.nnRequests for TLS client certificates typically request: \"digital signature\", \"key encipherment\", \"client auth\".nnRequests for TLS serving certificates typically request: \"key encipherment\", \"digital signature\", \"server auth\".nnValid values are:n \"signing\", \"digital signature\", \"content commitment\",n \"key encipherment\", \"key agreement\", \"data encipherment\",n \"cert sign\", \"crl sign\", \"encipher only\", \"decipher only\", \"any\",n \"server auth\", \"client auth\",n \"code signing\", \"email protection\", \"s/mime\",n \"ipsec end system\", \"ipsec tunnel\", \"ipsec user\",n \"timestamping\", \"ocsp signing\", \"microsoft sgc\", \"netscape sgc\"\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"username\": { SchemaProps: spec.SchemaProps{ Description: \"username contains the name of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"uid\": { SchemaProps: spec.SchemaProps{ Description: \"uid contains the uid of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"groups\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"groups contains group membership of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"extra\": { SchemaProps: spec.SchemaProps{ Description: \"extra contains extra attributes of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, }, Required: []string{\"request\", \"signerName\"}, }, }, } } func schema_k8sio_api_certificates_v1_CertificateSigningRequestStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CertificateSigningRequestStatus contains conditions used to indicate approved/denied/failed status of the request, and the issued certificate.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"type\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"conditions applied to the request. Known conditions are \"Approved\", \"Denied\", and \"Failed\".\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/certificates/v1.CertificateSigningRequestCondition\"), }, }, }, }, }, \"certificate\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"certificate is populated with an issued certificate by the signer after an Approved condition is present. This field is set via the /status subresource. Once populated, this field is immutable.nnIf the certificate signing request is denied, a condition of type \"Denied\" is added and this field remains empty. If the signer cannot issue the certificate, a condition of type \"Failed\" is added and this field remains empty.nnValidation requirements:n 1. certificate must contain one or more PEM blocks.n 2. All PEM blocks must have the \"CERTIFICATE\" label, contain no headers, and the encoded datan  must be a BER-encoded ASN.1 Certificate structure as described in section 4 of RFC5280.n 3. Non-PEM content may appear before or after the \"CERTIFICATE\" PEM blocks and is unvalidated,n  to allow for explanatory text as described in section 5.2 of RFC7468.nnIf more than one PEM block is present, and the definition of the requested spec.signerName does not indicate otherwise, the first block is the issued certificate, and subsequent blocks should be treated as intermediate certificates and presented in TLS handshakes.nnThe certificate is encoded in PEM format.nnWhen serialized as JSON or YAML, the data is additionally base64-encoded, so it consists of:nn    base64(n    -----BEGIN CERTIFICATE-----n    ...n    -----END CERTIFICATE-----n    )\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/certificates/v1.CertificateSigningRequestCondition\"}, } } func schema_k8sio_api_certificates_v1beta1_CertificateSigningRequest(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Describes a certificate signing request\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"spec contains the certificate request, and is immutable after creation. Only the request, signerName, expirationSeconds, and usages fields can be set on creation. Other fields are derived by Kubernetes and cannot be modified by users.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/certificates/v1beta1.CertificateSigningRequestSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Derived information about the request.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/certificates/v1beta1.CertificateSigningRequestStatus\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/certificates/v1beta1.CertificateSigningRequestSpec\", \"k8s.io/api/certificates/v1beta1.CertificateSigningRequestStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_certificates_v1beta1_CertificateSigningRequestCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type of the condition. Known conditions include \"Approved\", \"Denied\", and \"Failed\".\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown. Approved, Denied, and Failed conditions may not be \"False\" or \"Unknown\". Defaults to \"True\". If unset, should be treated as \"True\".\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"brief reason for the request state\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"human readable message with details about the request state\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastUpdateTime\": { SchemaProps: spec.SchemaProps{ Description: \"timestamp for the last update to this condition\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"lastTransitionTime is the time the condition last transitioned from one status to another. If unset, when a new condition type is added or an existing condition's status is changed, the server defaults this to the current time.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, }, Required: []string{\"type\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_certificates_v1beta1_CertificateSigningRequestList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/certificates/v1beta1.CertificateSigningRequest\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/certificates/v1beta1.CertificateSigningRequest\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_certificates_v1beta1_CertificateSigningRequestSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CertificateSigningRequestSpec contains the certificate request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"request\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Base64-encoded PKCS#10 CSR data\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, \"signerName\": { SchemaProps: spec.SchemaProps{ Description: \"Requested signer for the request. It is a qualified name in the form: `scope-hostname.io/name`. If empty, it will be defaulted:n 1. If it's a kubelet client certificate, it is assignedn    \"kubernetes.io/kube-apiserver-client-kubelet\".n 2. If it's a kubelet serving certificate, it is assignedn    \"kubernetes.io/kubelet-serving\".n 3. Otherwise, it is assigned \"kubernetes.io/legacy-unknown\".nDistribution of trust for signers happens out of band. You can select on this field using `spec.signerName`.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"expirationSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"expirationSeconds is the requested duration of validity of the issued certificate. The certificate signer may issue a certificate with a different validity duration so a client must check the delta between the notBefore and and notAfter fields in the issued certificate to determine the actual duration.nnThe v1.22+ in-tree implementations of the well-known Kubernetes signers will honor this field as long as the requested duration is not greater than the maximum duration they will honor per the --cluster-signing-duration CLI flag to the Kubernetes controller manager.nnCertificate signers may not honor this field for various reasons:nn  1. Old signer that is unaware of the field (such as the in-treen     implementations prior to v1.22)n  2. Signer whose configured maximum is shorter than the requested durationn  3. Signer whose configured minimum is longer than the requested durationnnThe minimum valid value for expirationSeconds is 600, i.e. 10 minutes.nnAs of v1.22, this field is beta and is controlled via the CSRDuration feature gate.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"usages\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"allowedUsages specifies a set of usage contexts the key will be valid for. See: https://tools.ietf.org/html/rfc5280#section-4.2.1.3n     https://tools.ietf.org/html/rfc5280#section-4.2.1.12nValid values are:n \"signing\",n \"digital signature\",n \"content commitment\",n \"key encipherment\",n \"key agreement\",n \"data encipherment\",n \"cert sign\",n \"crl sign\",n \"encipher only\",n \"decipher only\",n \"any\",n \"server auth\",n \"client auth\",n \"code signing\",n \"email protection\",n \"s/mime\",n \"ipsec end system\",n \"ipsec tunnel\",n \"ipsec user\",n \"timestamping\",n \"ocsp signing\",n \"microsoft sgc\",n \"netscape sgc\"\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"username\": { SchemaProps: spec.SchemaProps{ Description: \"Information about the requesting user. See user.Info interface for details.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"uid\": { SchemaProps: spec.SchemaProps{ Description: \"UID information about the requesting user. See user.Info interface for details.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"groups\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Group information about the requesting user. See user.Info interface for details.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"extra\": { SchemaProps: spec.SchemaProps{ Description: \"Extra information about the requesting user. See user.Info interface for details.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, }, Required: []string{\"request\"}, }, }, } } func schema_k8sio_api_certificates_v1beta1_CertificateSigningRequestStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, Properties: map[string]spec.Schema{ \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"type\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Conditions applied to the request, such as approval or denial.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/certificates/v1beta1.CertificateSigningRequestCondition\"), }, }, }, }, }, \"certificate\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"If request was approved, the controller will place the issued certificate here.\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/certificates/v1beta1.CertificateSigningRequestCondition\"}, } } func schema_k8sio_api_coordination_v1_Lease(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Lease defines a lease concept.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the Lease. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/coordination/v1.LeaseSpec\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/coordination/v1.LeaseSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_coordination_v1_LeaseList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LeaseList is a list of Lease objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of schema objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/coordination/v1.Lease\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/coordination/v1.Lease\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_coordination_v1_LeaseSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LeaseSpec is a specification of a Lease.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"holderIdentity\": { SchemaProps: spec.SchemaProps{ Description: \"holderIdentity contains the identity of the holder of a current lease.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"leaseDurationSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"leaseDurationSeconds is a duration that candidates for a lease need to wait to force acquire it. This is measure against time of last observed RenewTime.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"acquireTime\": { SchemaProps: spec.SchemaProps{ Description: \"acquireTime is a time when the current lease was acquired.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"), }, }, \"renewTime\": { SchemaProps: spec.SchemaProps{ Description: \"renewTime is a time when the current holder of a lease has last updated the lease.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"), }, }, \"leaseTransitions\": { SchemaProps: spec.SchemaProps{ Description: \"leaseTransitions is the number of transitions of a lease between holders.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"}, } } func schema_k8sio_api_coordination_v1beta1_Lease(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Lease defines a lease concept.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the Lease. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/coordination/v1beta1.LeaseSpec\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/coordination/v1beta1.LeaseSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_coordination_v1beta1_LeaseList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LeaseList is a list of Lease objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of schema objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/coordination/v1beta1.Lease\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/coordination/v1beta1.Lease\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_coordination_v1beta1_LeaseSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LeaseSpec is a specification of a Lease.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"holderIdentity\": { SchemaProps: spec.SchemaProps{ Description: \"holderIdentity contains the identity of the holder of a current lease.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"leaseDurationSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"leaseDurationSeconds is a duration that candidates for a lease need to wait to force acquire it. This is measure against time of last observed RenewTime.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"acquireTime\": { SchemaProps: spec.SchemaProps{ Description: \"acquireTime is a time when the current lease was acquired.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"), }, }, \"renewTime\": { SchemaProps: spec.SchemaProps{ Description: \"renewTime is a time when the current holder of a lease has last updated the lease.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"), }, }, \"leaseTransitions\": { SchemaProps: spec.SchemaProps{ Description: \"leaseTransitions is the number of transitions of a lease between holders.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"}, } } func schema_k8sio_api_core_v1_AWSElasticBlockStoreVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a Persistent Disk resource in AWS.nnAn AWS EBS disk must exist before mounting to a container. The disk must also be in the same AWS zone as the kubelet. An AWS EBS disk can only be mounted as read/write once. AWS EBS volumes support ownership management and SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"volumeID\": { SchemaProps: spec.SchemaProps{ Description: \"volumeID is unique ID of the persistent disk resource in AWS (Amazon EBS volume). More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType is the filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"partition\": { SchemaProps: spec.SchemaProps{ Description: \"partition is the partition in the volume that you want to mount. If omitted, the default is to mount by volume name. Examples: For volume /dev/sda1, you specify the partition as \"1\". Similarly, the volume partition for /dev/sda is \"0\" (or you can leave the property empty).\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly value true will force the readOnly setting in VolumeMounts. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"volumeID\"}, }, }, } } func schema_k8sio_api_core_v1_Affinity(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Affinity is a group of affinity scheduling rules.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"nodeAffinity\": { SchemaProps: spec.SchemaProps{ Description: \"Describes node affinity scheduling rules for the pod.\", Ref:         ref(\"k8s.io/api/core/v1.NodeAffinity\"), }, }, \"podAffinity\": { SchemaProps: spec.SchemaProps{ Description: \"Describes pod affinity scheduling rules (e.g. co-locate this pod in the same node, zone, etc. as some other pod(s)).\", Ref:         ref(\"k8s.io/api/core/v1.PodAffinity\"), }, }, \"podAntiAffinity\": { SchemaProps: spec.SchemaProps{ Description: \"Describes pod anti-affinity scheduling rules (e.g. avoid putting this pod in the same node, zone, etc. as some other pod(s)).\", Ref:         ref(\"k8s.io/api/core/v1.PodAntiAffinity\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.NodeAffinity\", \"k8s.io/api/core/v1.PodAffinity\", \"k8s.io/api/core/v1.PodAntiAffinity\"}, } } func schema_k8sio_api_core_v1_AttachedVolume(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"AttachedVolume describes a volume attached to a node\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the attached volume\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"devicePath\": { SchemaProps: spec.SchemaProps{ Description: \"DevicePath represents the device path where the volume should be available\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"devicePath\"}, }, }, } } func schema_k8sio_api_core_v1_AvoidPods(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"AvoidPods describes pods that should avoid this node. This is the value for a Node annotation with key scheduler.alpha.kubernetes.io/preferAvoidPods and will eventually become a field of NodeStatus.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"preferAvoidPods\": { SchemaProps: spec.SchemaProps{ Description: \"Bounded-sized list of signatures of pods that should avoid this node, sorted in timestamp order from oldest to newest. Size of the slice is unspecified.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.PreferAvoidPodsEntry\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PreferAvoidPodsEntry\"}, } } func schema_k8sio_api_core_v1_AzureDiskVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"AzureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"diskName\": { SchemaProps: spec.SchemaProps{ Description: \"diskName is the Name of the data disk in the blob storage\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"diskURI\": { SchemaProps: spec.SchemaProps{ Description: \"diskURI is the URI of data disk in the blob storage\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"cachingMode\": { SchemaProps: spec.SchemaProps{ Description: \"cachingMode is the Host Caching mode: None, Read Only, Read Write.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType is Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"kind expected values are Shared: multiple blob disks per storage account  Dedicated: single blob disk per storage account  Managed: azure managed data disk (only in managed availability set). defaults to shared\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"diskName\", \"diskURI\"}, }, }, } } func schema_k8sio_api_core_v1_AzureFilePersistentVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"AzureFile represents an Azure File Service mount on the host and bind mount to the pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"secretName\": { SchemaProps: spec.SchemaProps{ Description: \"secretName is the name of secret that contains Azure Storage Account Name and Key\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"shareName\": { SchemaProps: spec.SchemaProps{ Description: \"shareName is the azure Share Name\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"secretNamespace\": { SchemaProps: spec.SchemaProps{ Description: \"secretNamespace is the namespace of the secret that contains Azure Storage Account Name and Key default is the same as the Pod\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"secretName\", \"shareName\"}, }, }, } } func schema_k8sio_api_core_v1_AzureFileVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"AzureFile represents an Azure File Service mount on the host and bind mount to the pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"secretName\": { SchemaProps: spec.SchemaProps{ Description: \"secretName is the  name of secret that contains Azure Storage Account Name and Key\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"shareName\": { SchemaProps: spec.SchemaProps{ Description: \"shareName is the azure share Name\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"secretName\", \"shareName\"}, }, }, } } func schema_k8sio_api_core_v1_Binding(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Binding ties one object to another; for example, a pod is bound to a node by a scheduler. Deprecated in 1.7, please use the bindings subresource of pods instead.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"target\": { SchemaProps: spec.SchemaProps{ Description: \"The target object that you want to bind to the standard object.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.ObjectReference\"), }, }, }, Required: []string{\"target\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ObjectReference\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_CSIPersistentVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents storage that is managed by an external CSI volume driver (Beta feature)\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"driver\": { SchemaProps: spec.SchemaProps{ Description: \"driver is the name of the driver to use for this volume. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"volumeHandle\": { SchemaProps: spec.SchemaProps{ Description: \"volumeHandle is the unique volume name returned by the CSI volume plugin\u2019s CreateVolume to refer to the volume on all subsequent calls. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly value to pass to ControllerPublishVolumeRequest. Defaults to false (read/write).\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType to mount. Must be a filesystem type supported by the host operating system. Ex. \"ext4\", \"xfs\", \"ntfs\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"volumeAttributes\": { SchemaProps: spec.SchemaProps{ Description: \"volumeAttributes of the volume to publish.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"controllerPublishSecretRef\": { SchemaProps: spec.SchemaProps{ Description: \"controllerPublishSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI ControllerPublishVolume and ControllerUnpublishVolume calls. This field is optional, and may be empty if no secret is required. If the secret object contains more than one secret, all secrets are passed.\", Ref:         ref(\"k8s.io/api/core/v1.SecretReference\"), }, }, \"nodeStageSecretRef\": { SchemaProps: spec.SchemaProps{ Description: \"nodeStageSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI NodeStageVolume and NodeStageVolume and NodeUnstageVolume calls. This field is optional, and may be empty if no secret is required. If the secret object contains more than one secret, all secrets are passed.\", Ref:         ref(\"k8s.io/api/core/v1.SecretReference\"), }, }, \"nodePublishSecretRef\": { SchemaProps: spec.SchemaProps{ Description: \"nodePublishSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI NodePublishVolume and NodeUnpublishVolume calls. This field is optional, and may be empty if no secret is required. If the secret object contains more than one secret, all secrets are passed.\", Ref:         ref(\"k8s.io/api/core/v1.SecretReference\"), }, }, \"controllerExpandSecretRef\": { SchemaProps: spec.SchemaProps{ Description: \"controllerExpandSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI ControllerExpandVolume call. This is an alpha field and requires enabling ExpandCSIVolumes feature gate. This field is optional, and may be empty if no secret is required. If the secret object contains more than one secret, all secrets are passed.\", Ref:         ref(\"k8s.io/api/core/v1.SecretReference\"), }, }, }, Required: []string{\"driver\", \"volumeHandle\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.SecretReference\"}, } } func schema_k8sio_api_core_v1_CSIVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a source location of a volume to mount, managed by an external CSI driver\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"driver\": { SchemaProps: spec.SchemaProps{ Description: \"driver is the name of the CSI driver that handles this volume. Consult with your admin for the correct name as registered in the cluster.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly specifies a read-only configuration for the volume. Defaults to false (read/write).\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType to mount. Ex. \"ext4\", \"xfs\", \"ntfs\". If not provided, the empty value is passed to the associated CSI driver which will determine the default filesystem to apply.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"volumeAttributes\": { SchemaProps: spec.SchemaProps{ Description: \"volumeAttributes stores driver-specific properties that are passed to the CSI driver. Consult your driver's documentation for supported values.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"nodePublishSecretRef\": { SchemaProps: spec.SchemaProps{ Description: \"nodePublishSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI NodePublishVolume and NodeUnpublishVolume calls. This field is optional, and  may be empty if no secret is required. If the secret object contains more than one secret, all secret references are passed.\", Ref:         ref(\"k8s.io/api/core/v1.LocalObjectReference\"), }, }, }, Required: []string{\"driver\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.LocalObjectReference\"}, } } func schema_k8sio_api_core_v1_Capabilities(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Adds and removes POSIX capabilities from running containers.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"add\": { SchemaProps: spec.SchemaProps{ Description: \"Added capabilities\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"drop\": { SchemaProps: spec.SchemaProps{ Description: \"Removed capabilities\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, } } func schema_k8sio_api_core_v1_CephFSPersistentVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a Ceph Filesystem mount that lasts the lifetime of a pod Cephfs volumes do not support ownership management or SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"monitors\": { SchemaProps: spec.SchemaProps{ Description: \"monitors is Required: Monitors is a collection of Ceph monitors More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"path\": { SchemaProps: spec.SchemaProps{ Description: \"path is Optional: Used as the mounted root, rather than the full Ceph tree, default is /\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"user\": { SchemaProps: spec.SchemaProps{ Description: \"user is Optional: User is the rados user name, default is admin More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"secretFile\": { SchemaProps: spec.SchemaProps{ Description: \"secretFile is Optional: SecretFile is the path to key ring for User, default is /etc/ceph/user.secret More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"secretRef\": { SchemaProps: spec.SchemaProps{ Description: \"secretRef is Optional: SecretRef is reference to the authentication secret for User, default is empty. More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it\", Ref:         ref(\"k8s.io/api/core/v1.SecretReference\"), }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly is Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"monitors\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.SecretReference\"}, } } func schema_k8sio_api_core_v1_CephFSVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a Ceph Filesystem mount that lasts the lifetime of a pod Cephfs volumes do not support ownership management or SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"monitors\": { SchemaProps: spec.SchemaProps{ Description: \"monitors is Required: Monitors is a collection of Ceph monitors More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"path\": { SchemaProps: spec.SchemaProps{ Description: \"path is Optional: Used as the mounted root, rather than the full Ceph tree, default is /\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"user\": { SchemaProps: spec.SchemaProps{ Description: \"user is optional: User is the rados user name, default is admin More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"secretFile\": { SchemaProps: spec.SchemaProps{ Description: \"secretFile is Optional: SecretFile is the path to key ring for User, default is /etc/ceph/user.secret More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"secretRef\": { SchemaProps: spec.SchemaProps{ Description: \"secretRef is Optional: SecretRef is reference to the authentication secret for User, default is empty. More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it\", Ref:         ref(\"k8s.io/api/core/v1.LocalObjectReference\"), }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly is Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"monitors\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.LocalObjectReference\"}, } } func schema_k8sio_api_core_v1_CinderPersistentVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a cinder volume resource in Openstack. A Cinder volume must exist before mounting to a container. The volume must also be in the same region as the kubelet. Cinder volumes support ownership management and SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"volumeID\": { SchemaProps: spec.SchemaProps{ Description: \"volumeID used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType Filesystem type to mount. Must be a filesystem type supported by the host operating system. Examples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified. More info: https://examples.k8s.io/mysql-cinder-pd/README.md\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly is Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"secretRef\": { SchemaProps: spec.SchemaProps{ Description: \"secretRef is Optional: points to a secret object containing parameters used to connect to OpenStack.\", Ref:         ref(\"k8s.io/api/core/v1.SecretReference\"), }, }, }, Required: []string{\"volumeID\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.SecretReference\"}, } } func schema_k8sio_api_core_v1_CinderVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a cinder volume resource in Openstack. A Cinder volume must exist before mounting to a container. The volume must also be in the same region as the kubelet. Cinder volumes support ownership management and SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"volumeID\": { SchemaProps: spec.SchemaProps{ Description: \"volumeID used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Examples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified. More info: https://examples.k8s.io/mysql-cinder-pd/README.md\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"secretRef\": { SchemaProps: spec.SchemaProps{ Description: \"secretRef is optional: points to a secret object containing parameters used to connect to OpenStack.\", Ref:         ref(\"k8s.io/api/core/v1.LocalObjectReference\"), }, }, }, Required: []string{\"volumeID\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.LocalObjectReference\"}, } } func schema_k8sio_api_core_v1_ClientIPConfig(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ClientIPConfig represents the configurations of Client IP based session affinity.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"timeoutSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"timeoutSeconds specifies the seconds of ClientIP type session sticky time. The value must be >0 && <=86400(for 1 day) if ServiceAffinity == \"ClientIP\". Default value is 10800(for 3 hours).\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_k8sio_api_core_v1_ComponentCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Information about the condition of a component.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of condition for a component. Valid value: \"Healthy\"\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition for a component. Valid values for \"Healthy\": \"True\", \"False\", or \"Unknown\".\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"Message about the condition for a component. For example, information about a health check.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"error\": { SchemaProps: spec.SchemaProps{ Description: \"Condition error code for a component. For example, a health check error code.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, } } func schema_k8sio_api_core_v1_ComponentStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ComponentStatus (and ComponentStatusList) holds the cluster validation info. Deprecated: This API is deprecated in v1.19+\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"List of component conditions observed\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.ComponentCondition\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ComponentCondition\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_ComponentStatusList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Status of all the conditions for the component as a list of ComponentStatus objects. Deprecated: This API is deprecated in v1.19+\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of ComponentStatus objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.ComponentStatus\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ComponentStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_core_v1_ConfigMap(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ConfigMap holds configuration data for pods to consume.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"immutable\": { SchemaProps: spec.SchemaProps{ Description: \"Immutable, if set to true, ensures that data stored in the ConfigMap cannot be updated (only object metadata can be modified). If not set to true, the field can be modified at any time. Defaulted to nil.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"data\": { SchemaProps: spec.SchemaProps{ Description: \"Data contains the configuration data. Each key must consist of alphanumeric characters, '-', '_' or '.'. Values with non-UTF-8 byte sequences must use the BinaryData field. The keys stored in Data must not overlap with the keys in the BinaryData field, this is enforced during validation process.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"binaryData\": { SchemaProps: spec.SchemaProps{ Description: \"BinaryData contains the binary data. Each key must consist of alphanumeric characters, '-', '_' or '.'. BinaryData can contain byte sequences that are not in the UTF-8 range. The keys stored in BinaryData must not overlap with the ones in the Data field, this is enforced during validation process. Using this field will require 1.10+ apiserver and kubelet.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"byte\", }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_ConfigMapEnvSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ConfigMapEnvSource selects a ConfigMap to populate the environment variables with.nnThe contents of the target ConfigMap's Data field will represent the key-value pairs as environment variables.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"optional\": { SchemaProps: spec.SchemaProps{ Description: \"Specify whether the ConfigMap must be defined\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_core_v1_ConfigMapKeySelector(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Selects a key from a ConfigMap.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"key\": { SchemaProps: spec.SchemaProps{ Description: \"The key to select.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"optional\": { SchemaProps: spec.SchemaProps{ Description: \"Specify whether the ConfigMap or its key must be defined\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"key\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, } } func schema_k8sio_api_core_v1_ConfigMapList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ConfigMapList is a resource containing a list of ConfigMap objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of ConfigMaps.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.ConfigMap\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ConfigMap\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_core_v1_ConfigMapNodeConfigSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ConfigMapNodeConfigSource contains the information to reference a ConfigMap as a config source for the Node. This API is deprecated since 1.22: https://git.k8s.io/enhancements/keps/sig-node/281-dynamic-kubelet-configuration\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"Namespace is the metadata.namespace of the referenced ConfigMap. This field is required in all cases.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the metadata.name of the referenced ConfigMap. This field is required in all cases.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"uid\": { SchemaProps: spec.SchemaProps{ Description: \"UID is the metadata.UID of the referenced ConfigMap. This field is forbidden in Node.Spec, and required in Node.Status.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resourceVersion\": { SchemaProps: spec.SchemaProps{ Description: \"ResourceVersion is the metadata.ResourceVersion of the referenced ConfigMap. This field is forbidden in Node.Spec, and required in Node.Status.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"kubeletConfigKey\": { SchemaProps: spec.SchemaProps{ Description: \"KubeletConfigKey declares which key of the referenced ConfigMap corresponds to the KubeletConfiguration structure This field is required in all cases.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"namespace\", \"name\", \"kubeletConfigKey\"}, }, }, } } func schema_k8sio_api_core_v1_ConfigMapProjection(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Adapts a ConfigMap into a projected volume.nnThe contents of the target ConfigMap's Data field will be presented in a projected volume as files using the keys in the Data field as the file names, unless the items element is populated with specific mappings of keys to paths. Note that this is identical to a configmap volume source without the default mode.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items if unspecified, each key-value pair in the Data field of the referenced ConfigMap will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the ConfigMap, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.KeyToPath\"), }, }, }, }, }, \"optional\": { SchemaProps: spec.SchemaProps{ Description: \"optional specify whether the ConfigMap or its keys must be defined\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.KeyToPath\"}, } } func schema_k8sio_api_core_v1_ConfigMapVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Adapts a ConfigMap into a volume.nnThe contents of the target ConfigMap's Data field will be presented in a volume as files using the keys in the Data field as the file names, unless the items element is populated with specific mappings of keys to paths. ConfigMap volumes support ownership management and SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items if unspecified, each key-value pair in the Data field of the referenced ConfigMap will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the ConfigMap, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.KeyToPath\"), }, }, }, }, }, \"defaultMode\": { SchemaProps: spec.SchemaProps{ Description: \"defaultMode is optional: mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"optional\": { SchemaProps: spec.SchemaProps{ Description: \"optional specify whether the ConfigMap or its keys must be defined\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.KeyToPath\"}, } } func schema_k8sio_api_core_v1_Container(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"A single application container that you want to run within a pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the container specified as a DNS_LABEL. Each container in a pod must have a unique name (DNS_LABEL). Cannot be updated.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"image\": { SchemaProps: spec.SchemaProps{ Description: \"Container image name. More info: https://kubernetes.io/docs/concepts/containers/images This field is optional to allow higher level config management to default or override container images in workload controllers like Deployments and StatefulSets.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"command\": { SchemaProps: spec.SchemaProps{ Description: \"Entrypoint array. Not executed within a shell. The container image's ENTRYPOINT is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container's environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. \"$$(VAR_NAME)\" will produce the string literal \"$(VAR_NAME)\". Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"args\": { SchemaProps: spec.SchemaProps{ Description: \"Arguments to the entrypoint. The container image's CMD is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container's environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. \"$$(VAR_NAME)\" will produce the string literal \"$(VAR_NAME)\". Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"workingDir\": { SchemaProps: spec.SchemaProps{ Description: \"Container's working directory. If not specified, the container runtime's default will be used, which might be configured in the container image. Cannot be updated.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ports\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"containerPort\", \"protocol\", }, \"x-kubernetes-list-type\":       \"map\", \"x-kubernetes-patch-merge-key\": \"containerPort\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"List of ports to expose from the container. Exposing a port here gives the system additional information about the network connections a container uses, but is primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default \"0.0.0.0\" address inside a container will be accessible from the network. Cannot be updated.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.ContainerPort\"), }, }, }, }, }, \"envFrom\": { SchemaProps: spec.SchemaProps{ Description: \"List of sources to populate environment variables in the container. The keys defined within a source must be a C_IDENTIFIER. All invalid keys will be reported as an event when the container is starting. When a key exists in multiple sources, the value associated with the last source will take precedence. Values defined by an Env with a duplicate key will take precedence. Cannot be updated.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.EnvFromSource\"), }, }, }, }, }, \"env\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"name\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"List of environment variables to set in the container. Cannot be updated.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.EnvVar\"), }, }, }, }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"Compute Resources required by this container. Cannot be updated. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.ResourceRequirements\"), }, }, \"volumeMounts\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"mountPath\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Pod volumes to mount into the container's filesystem. Cannot be updated.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.VolumeMount\"), }, }, }, }, }, \"volumeDevices\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"devicePath\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"volumeDevices is the list of block devices to be used by the container.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.VolumeDevice\"), }, }, }, }, }, \"livenessProbe\": { SchemaProps: spec.SchemaProps{ Description: \"Periodic probe of container liveness. Container will be restarted if the probe fails. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes\", Ref:         ref(\"k8s.io/api/core/v1.Probe\"), }, }, \"readinessProbe\": { SchemaProps: spec.SchemaProps{ Description: \"Periodic probe of container service readiness. Container will be removed from service endpoints if the probe fails. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes\", Ref:         ref(\"k8s.io/api/core/v1.Probe\"), }, }, \"startupProbe\": { SchemaProps: spec.SchemaProps{ Description: \"StartupProbe indicates that the Pod has successfully initialized. If specified, no other probes are executed until this completes successfully. If this probe fails, the Pod will be restarted, just as if the livenessProbe failed. This can be used to provide different probe parameters at the beginning of a Pod's lifecycle, when it might take a long time to load data or warm a cache, than during steady-state operation. This cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes\", Ref:         ref(\"k8s.io/api/core/v1.Probe\"), }, }, \"lifecycle\": { SchemaProps: spec.SchemaProps{ Description: \"Actions that the management system should take in response to container lifecycle events. Cannot be updated.\", Ref:         ref(\"k8s.io/api/core/v1.Lifecycle\"), }, }, \"terminationMessagePath\": { SchemaProps: spec.SchemaProps{ Description: \"Optional: Path at which the file to which the container's termination message will be written is mounted into the container's filesystem. Message written is intended to be brief final status, such as an assertion failure message. Will be truncated by the node if greater than 4096 bytes. The total message length across all containers will be limited to 12kb. Defaults to /dev/termination-log. Cannot be updated.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"terminationMessagePolicy\": { SchemaProps: spec.SchemaProps{ Description: \"Indicate how the termination message should be populated. File will use the contents of terminationMessagePath to populate the container status message on both success and failure. FallbackToLogsOnError will use the last chunk of container log output if the termination message file is empty and the container exited with an error. The log output is limited to 2048 bytes or 80 lines, whichever is smaller. Defaults to File. Cannot be updated.nnPossible enum values:n - `\"FallbackToLogsOnError\"` will read the most recent contents of the container logs for the container status message when the container exits with an error and the terminationMessagePath has no contents.n - `\"File\"` is the default behavior and will set the container status message to the contents of the container's terminationMessagePath when the container exits.\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"FallbackToLogsOnError\", \"File\"}}, }, \"imagePullPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise. Cannot be updated. More info: https://kubernetes.io/docs/concepts/containers/images#updating-imagesnnPossible enum values:n - `\"Always\"` means that kubelet always attempts to pull the latest image. Container will fail If the pull fails.n - `\"IfNotPresent\"` means that kubelet pulls if the image isn't present on disk. Container will fail if the image isn't present and the pull fails.n - `\"Never\"` means that kubelet never pulls an image, but only uses a local image. Container will fail if the image isn't present\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"Always\", \"IfNotPresent\", \"Never\"}}, }, \"securityContext\": { SchemaProps: spec.SchemaProps{ Description: \"SecurityContext defines the security options the container should be run with. If set, the fields of SecurityContext override the equivalent fields of PodSecurityContext. More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/\", Ref:         ref(\"k8s.io/api/core/v1.SecurityContext\"), }, }, \"stdin\": { SchemaProps: spec.SchemaProps{ Description: \"Whether this container should allocate a buffer for stdin in the container runtime. If this is not set, reads from stdin in the container will always result in EOF. Default is false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"stdinOnce\": { SchemaProps: spec.SchemaProps{ Description: \"Whether the container runtime should close the stdin channel after it has been opened by a single attach. When stdin is true the stdin stream will remain open across multiple attach sessions. If stdinOnce is set to true, stdin is opened on container start, is empty until the first client attaches to stdin, and then remains open and accepts data until the client disconnects, at which time stdin is closed and remains closed until the container is restarted. If this flag is false, a container processes that reads from stdin will never receive an EOF. Default is false\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"tty\": { SchemaProps: spec.SchemaProps{ Description: \"Whether this container should allocate a TTY for itself, also requires 'stdin' to be true. Default is false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"name\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ContainerPort\", \"k8s.io/api/core/v1.EnvFromSource\", \"k8s.io/api/core/v1.EnvVar\", \"k8s.io/api/core/v1.Lifecycle\", \"k8s.io/api/core/v1.Probe\", \"k8s.io/api/core/v1.ResourceRequirements\", \"k8s.io/api/core/v1.SecurityContext\", \"k8s.io/api/core/v1.VolumeDevice\", \"k8s.io/api/core/v1.VolumeMount\"}, } } func schema_k8sio_api_core_v1_ContainerImage(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Describe a container image\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"names\": { SchemaProps: spec.SchemaProps{ Description: \"Names by which this image is known. e.g. [\"k8s.gcr.io/hyperkube:v1.0.7\", \"dockerhub.io/google_containers/hyperkube:v1.0.7\"]\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"sizeBytes\": { SchemaProps: spec.SchemaProps{ Description: \"The size of the image in bytes.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, }, }, }, } } func schema_k8sio_api_core_v1_ContainerPort(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ContainerPort represents a network port in a single container.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"If specified, this must be an IANA_SVC_NAME and unique within the pod. Each named port in a pod must have a unique name. Name for the port that can be referred to by services.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"hostPort\": { SchemaProps: spec.SchemaProps{ Description: \"Number of port to expose on the host. If specified, this must be a valid port number, 0 < x < 65536. If HostNetwork is specified, this must match ContainerPort. Most containers do not need this.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"containerPort\": { SchemaProps: spec.SchemaProps{ Description: \"Number of port to expose on the pod's IP address. This must be a valid port number, 0 < x < 65536.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"protocol\": { SchemaProps: spec.SchemaProps{ Description: \"Protocol for port. Must be UDP, TCP, or SCTP. Defaults to \"TCP\".nnPossible enum values:n - `\"SCTP\"` is the SCTP protocol.n - `\"TCP\"` is the TCP protocol.n - `\"UDP\"` is the UDP protocol.\", Default:     \"TCP\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"SCTP\", \"TCP\", \"UDP\"}}, }, \"hostIP\": { SchemaProps: spec.SchemaProps{ Description: \"What host IP to bind the external port to.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"containerPort\"}, }, }, } } func schema_k8sio_api_core_v1_ContainerState(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ContainerState holds a possible state of container. Only one of its members may be specified. If none of them is specified, the default one is ContainerStateWaiting.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"waiting\": { SchemaProps: spec.SchemaProps{ Description: \"Details about a waiting container\", Ref:         ref(\"k8s.io/api/core/v1.ContainerStateWaiting\"), }, }, \"running\": { SchemaProps: spec.SchemaProps{ Description: \"Details about a running container\", Ref:         ref(\"k8s.io/api/core/v1.ContainerStateRunning\"), }, }, \"terminated\": { SchemaProps: spec.SchemaProps{ Description: \"Details about a terminated container\", Ref:         ref(\"k8s.io/api/core/v1.ContainerStateTerminated\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ContainerStateRunning\", \"k8s.io/api/core/v1.ContainerStateTerminated\", \"k8s.io/api/core/v1.ContainerStateWaiting\"}, } } func schema_k8sio_api_core_v1_ContainerStateRunning(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ContainerStateRunning is a running state of a container.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"startedAt\": { SchemaProps: spec.SchemaProps{ Description: \"Time at which the container was last (re-)started\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_core_v1_ContainerStateTerminated(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ContainerStateTerminated is a terminated state of a container.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"exitCode\": { SchemaProps: spec.SchemaProps{ Description: \"Exit status from the last termination of the container\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"signal\": { SchemaProps: spec.SchemaProps{ Description: \"Signal from the last termination of the container\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"(brief) reason from the last termination of the container\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"Message regarding the last termination of the container\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"startedAt\": { SchemaProps: spec.SchemaProps{ Description: \"Time at which previous execution of the container started\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"finishedAt\": { SchemaProps: spec.SchemaProps{ Description: \"Time at which the container last terminated\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"containerID\": { SchemaProps: spec.SchemaProps{ Description: \"Container's ID in the format '<type>://<container_id>'\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"exitCode\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_core_v1_ContainerStateWaiting(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ContainerStateWaiting is a waiting state of a container.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"(brief) reason the container is not yet running.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"Message regarding why the container is not yet running.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_core_v1_ContainerStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ContainerStatus contains details for the current status of this container.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"This must be a DNS_LABEL. Each container in a pod must have a unique name. Cannot be updated.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"state\": { SchemaProps: spec.SchemaProps{ Description: \"Details about the container's current condition.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.ContainerState\"), }, }, \"lastState\": { SchemaProps: spec.SchemaProps{ Description: \"Details about the container's last termination condition.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.ContainerState\"), }, }, \"ready\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies whether the container has passed its readiness probe.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"restartCount\": { SchemaProps: spec.SchemaProps{ Description: \"The number of times the container has been restarted.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"image\": { SchemaProps: spec.SchemaProps{ Description: \"The image the container is running. More info: https://kubernetes.io/docs/concepts/containers/images.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"imageID\": { SchemaProps: spec.SchemaProps{ Description: \"ImageID of the container's image.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"containerID\": { SchemaProps: spec.SchemaProps{ Description: \"Container's ID in the format '<type>://<container_id>'.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"started\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies whether the container has passed its startup probe. Initialized as false, becomes true after startupProbe is considered successful. Resets to false when the container is restarted, or if kubelet loses state temporarily. Is always true when no startupProbe is defined.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"ready\", \"restartCount\", \"image\", \"imageID\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ContainerState\"}, } } func schema_k8sio_api_core_v1_DaemonEndpoint(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DaemonEndpoint contains information about a single Daemon endpoint.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"Port\": { SchemaProps: spec.SchemaProps{ Description: \"Port number of the given endpoint.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"Port\"}, }, }, } } func schema_k8sio_api_core_v1_DownwardAPIProjection(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents downward API info for projecting into a projected volume. Note that this is identical to a downwardAPI volume source without the default mode.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of DownwardAPIVolume file\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.DownwardAPIVolumeFile\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.DownwardAPIVolumeFile\"}, } } func schema_k8sio_api_core_v1_DownwardAPIVolumeFile(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DownwardAPIVolumeFile represents information to create the file containing the pod field\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"path\": { SchemaProps: spec.SchemaProps{ Description: \"Required: Path is  the relative path name of the file to be created. Must not be absolute or contain the '..' path. Must be utf-8 encoded. The first item of the relative path must not start with '..'\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fieldRef\": { SchemaProps: spec.SchemaProps{ Description: \"Required: Selects a field of the pod: only annotations, labels, name and namespace are supported.\", Ref:         ref(\"k8s.io/api/core/v1.ObjectFieldSelector\"), }, }, \"resourceFieldRef\": { SchemaProps: spec.SchemaProps{ Description: \"Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, requests.cpu and requests.memory) are currently supported.\", Ref:         ref(\"k8s.io/api/core/v1.ResourceFieldSelector\"), }, }, \"mode\": { SchemaProps: spec.SchemaProps{ Description: \"Optional: mode bits used to set permissions on this file, must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"path\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ObjectFieldSelector\", \"k8s.io/api/core/v1.ResourceFieldSelector\"}, } } func schema_k8sio_api_core_v1_DownwardAPIVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DownwardAPIVolumeSource represents a volume containing downward API info. Downward API volumes support ownership management and SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of downward API volume file\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.DownwardAPIVolumeFile\"), }, }, }, }, }, \"defaultMode\": { SchemaProps: spec.SchemaProps{ Description: \"Optional: mode bits to use on created files by default. Must be a Optional: mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.DownwardAPIVolumeFile\"}, } } func schema_k8sio_api_core_v1_EmptyDirVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents an empty directory for a pod. Empty directory volumes support ownership management and SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"medium\": { SchemaProps: spec.SchemaProps{ Description: \"medium represents what type of storage medium should back this directory. The default is \"\" which means to use the node's default medium. Must be an empty string (default) or Memory. More info: https://kubernetes.io/docs/concepts/storage/volumes#emptydir\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"sizeLimit\": { SchemaProps: spec.SchemaProps{ Description: \"sizeLimit is the total amount of local storage required for this EmptyDir volume. The size limit is also applicable for memory medium. The maximum usage on memory medium EmptyDir would be the minimum value between the SizeLimit specified here and the sum of memory limits of all containers in a pod. The default is nil which means that the limit is undefined. More info: http://kubernetes.io/docs/user-guide/volumes#emptydir\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_core_v1_EndpointAddress(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EndpointAddress is a tuple that describes single IP address.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ip\": { SchemaProps: spec.SchemaProps{ Description: \"The IP of this endpoint. May not be loopback (127.0.0.0/8), link-local (169.254.0.0/16), or link-local multicast ((224.0.0.0/24). IPv6 is also accepted but not fully supported on all platforms. Also, certain kubernetes components, like kube-proxy, are not IPv6 ready.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"hostname\": { SchemaProps: spec.SchemaProps{ Description: \"The Hostname of this endpoint\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"nodeName\": { SchemaProps: spec.SchemaProps{ Description: \"Optional: Node hosting this endpoint. This can be used to determine endpoints local to a node.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"targetRef\": { SchemaProps: spec.SchemaProps{ Description: \"Reference to object providing the endpoint.\", Ref:         ref(\"k8s.io/api/core/v1.ObjectReference\"), }, }, }, Required: []string{\"ip\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ObjectReference\"}, } } func schema_k8sio_api_core_v1_EndpointPort(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EndpointPort is a tuple that describes a single port.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"The name of this port.  This must match the 'name' field in the corresponding ServicePort. Must be a DNS_LABEL. Optional only if one port is defined.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"port\": { SchemaProps: spec.SchemaProps{ Description: \"The port number of the endpoint.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"protocol\": { SchemaProps: spec.SchemaProps{ Description: \"The IP protocol for this port. Must be UDP, TCP, or SCTP. Default is TCP.nnPossible enum values:n - `\"SCTP\"` is the SCTP protocol.n - `\"TCP\"` is the TCP protocol.n - `\"UDP\"` is the UDP protocol.\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"SCTP\", \"TCP\", \"UDP\"}}, }, \"appProtocol\": { SchemaProps: spec.SchemaProps{ Description: \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"port\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, } } func schema_k8sio_api_core_v1_EndpointSubset(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EndpointSubset is a group of addresses with a common set of ports. The expanded set of endpoints is the Cartesian product of Addresses x Ports. For example, given:n  {n    Addresses: [{\"ip\": \"10.10.1.1\"}, {\"ip\": \"10.10.2.2\"}],n    Ports:     [{\"name\": \"a\", \"port\": 8675}, {\"name\": \"b\", \"port\": 309}]n  }nThe resulting set of endpoints can be viewed as:n    a: [ 10.10.1.1:8675, 10.10.2.2:8675 ],n    b: [ 10.10.1.1:309, 10.10.2.2:309 ]\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"addresses\": { SchemaProps: spec.SchemaProps{ Description: \"IP addresses which offer the related ports that are marked as ready. These endpoints should be considered safe for load balancers and clients to utilize.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.EndpointAddress\"), }, }, }, }, }, \"notReadyAddresses\": { SchemaProps: spec.SchemaProps{ Description: \"IP addresses which offer the related ports but are not currently marked as ready because they have not yet finished starting, have recently failed a readiness check, or have recently failed a liveness check.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.EndpointAddress\"), }, }, }, }, }, \"ports\": { SchemaProps: spec.SchemaProps{ Description: \"Port numbers available on the related IP addresses.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.EndpointPort\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.EndpointAddress\", \"k8s.io/api/core/v1.EndpointPort\"}, } } func schema_k8sio_api_core_v1_Endpoints(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Endpoints is a collection of endpoints that implement the actual service. Example:n  Name: \"mysvc\",n  Subsets: [n    {n      Addresses: [{\"ip\": \"10.10.1.1\"}, {\"ip\": \"10.10.2.2\"}],n      Ports: [{\"name\": \"a\", \"port\": 8675}, {\"name\": \"b\", \"port\": 309}]n    },n    {n      Addresses: [{\"ip\": \"10.10.3.3\"}],n      Ports: [{\"name\": \"a\", \"port\": 93}, {\"name\": \"b\", \"port\": 76}]n    },n ]\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"subsets\": { SchemaProps: spec.SchemaProps{ Description: \"The set of all endpoints is the union of all subsets. Addresses are placed into subsets according to the IPs they share. A single address with multiple ports, some of which are ready and some of which are not (because they come from different containers) will result in the address being displayed in different subsets for the different ports. No address will appear in both Addresses and NotReadyAddresses in the same subset. Sets of addresses and ports that comprise a service.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.EndpointSubset\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.EndpointSubset\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_EndpointsList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EndpointsList is a list of endpoints.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of endpoints.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.Endpoints\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.Endpoints\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_core_v1_EnvFromSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EnvFromSource represents the source of a set of ConfigMaps\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"prefix\": { SchemaProps: spec.SchemaProps{ Description: \"An optional identifier to prepend to each key in the ConfigMap. Must be a C_IDENTIFIER.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"configMapRef\": { SchemaProps: spec.SchemaProps{ Description: \"The ConfigMap to select from\", Ref:         ref(\"k8s.io/api/core/v1.ConfigMapEnvSource\"), }, }, \"secretRef\": { SchemaProps: spec.SchemaProps{ Description: \"The Secret to select from\", Ref:         ref(\"k8s.io/api/core/v1.SecretEnvSource\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ConfigMapEnvSource\", \"k8s.io/api/core/v1.SecretEnvSource\"}, } } func schema_k8sio_api_core_v1_EnvVar(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EnvVar represents an environment variable present in a Container.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the environment variable. Must be a C_IDENTIFIER.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"value\": { SchemaProps: spec.SchemaProps{ Description: \"Variable references $(VAR_NAME) are expanded using the previously defined environment variables in the container and any service environment variables. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. \"$$(VAR_NAME)\" will produce the string literal \"$(VAR_NAME)\". Escaped references will never be expanded, regardless of whether the variable exists or not. Defaults to \"\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"valueFrom\": { SchemaProps: spec.SchemaProps{ Description: \"Source for the environment variable's value. Cannot be used if value is not empty.\", Ref:         ref(\"k8s.io/api/core/v1.EnvVarSource\"), }, }, }, Required: []string{\"name\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.EnvVarSource\"}, } } func schema_k8sio_api_core_v1_EnvVarSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EnvVarSource represents a source for the value of an EnvVar.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"fieldRef\": { SchemaProps: spec.SchemaProps{ Description: \"Selects a field of the pod: supports metadata.name, metadata.namespace, `metadata.labels['<KEY>']`, `metadata.annotations['<KEY>']`, spec.nodeName, spec.serviceAccountName, status.hostIP, status.podIP, status.podIPs.\", Ref:         ref(\"k8s.io/api/core/v1.ObjectFieldSelector\"), }, }, \"resourceFieldRef\": { SchemaProps: spec.SchemaProps{ Description: \"Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, limits.ephemeral-storage, requests.cpu, requests.memory and requests.ephemeral-storage) are currently supported.\", Ref:         ref(\"k8s.io/api/core/v1.ResourceFieldSelector\"), }, }, \"configMapKeyRef\": { SchemaProps: spec.SchemaProps{ Description: \"Selects a key of a ConfigMap.\", Ref:         ref(\"k8s.io/api/core/v1.ConfigMapKeySelector\"), }, }, \"secretKeyRef\": { SchemaProps: spec.SchemaProps{ Description: \"Selects a key of a secret in the pod's namespace\", Ref:         ref(\"k8s.io/api/core/v1.SecretKeySelector\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ConfigMapKeySelector\", \"k8s.io/api/core/v1.ObjectFieldSelector\", \"k8s.io/api/core/v1.ResourceFieldSelector\", \"k8s.io/api/core/v1.SecretKeySelector\"}, } } func schema_k8sio_api_core_v1_EphemeralContainer(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"An EphemeralContainer is a temporary container that you may add to an existing Pod for user-initiated activities such as debugging. Ephemeral containers have no resource or scheduling guarantees, and they will not be restarted when they exit or when a Pod is removed or restarted. The kubelet may evict a Pod if an ephemeral container causes the Pod to exceed its resource allocation.nnTo add an ephemeral container, use the ephemeralcontainers subresource of an existing Pod. Ephemeral containers may not be removed or restarted.nnThis is a beta feature available on clusters that haven't disabled the EphemeralContainers feature gate.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the ephemeral container specified as a DNS_LABEL. This name must be unique among all containers, init containers and ephemeral containers.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"image\": { SchemaProps: spec.SchemaProps{ Description: \"Container image name. More info: https://kubernetes.io/docs/concepts/containers/images\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"command\": { SchemaProps: spec.SchemaProps{ Description: \"Entrypoint array. Not executed within a shell. The image's ENTRYPOINT is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container's environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. \"$$(VAR_NAME)\" will produce the string literal \"$(VAR_NAME)\". Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"args\": { SchemaProps: spec.SchemaProps{ Description: \"Arguments to the entrypoint. The image's CMD is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container's environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. \"$$(VAR_NAME)\" will produce the string literal \"$(VAR_NAME)\". Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"workingDir\": { SchemaProps: spec.SchemaProps{ Description: \"Container's working directory. If not specified, the container runtime's default will be used, which might be configured in the container image. Cannot be updated.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ports\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"containerPort\", \"protocol\", }, \"x-kubernetes-list-type\":       \"map\", \"x-kubernetes-patch-merge-key\": \"containerPort\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Ports are not allowed for ephemeral containers.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.ContainerPort\"), }, }, }, }, }, \"envFrom\": { SchemaProps: spec.SchemaProps{ Description: \"List of sources to populate environment variables in the container. The keys defined within a source must be a C_IDENTIFIER. All invalid keys will be reported as an event when the container is starting. When a key exists in multiple sources, the value associated with the last source will take precedence. Values defined by an Env with a duplicate key will take precedence. Cannot be updated.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.EnvFromSource\"), }, }, }, }, }, \"env\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"name\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"List of environment variables to set in the container. Cannot be updated.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.EnvVar\"), }, }, }, }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"Resources are not allowed for ephemeral containers. Ephemeral containers use spare resources already allocated to the pod.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.ResourceRequirements\"), }, }, \"volumeMounts\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"mountPath\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Pod volumes to mount into the container's filesystem. Subpath mounts are not allowed for ephemeral containers. Cannot be updated.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.VolumeMount\"), }, }, }, }, }, \"volumeDevices\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"devicePath\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"volumeDevices is the list of block devices to be used by the container.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.VolumeDevice\"), }, }, }, }, }, \"livenessProbe\": { SchemaProps: spec.SchemaProps{ Description: \"Probes are not allowed for ephemeral containers.\", Ref:         ref(\"k8s.io/api/core/v1.Probe\"), }, }, \"readinessProbe\": { SchemaProps: spec.SchemaProps{ Description: \"Probes are not allowed for ephemeral containers.\", Ref:         ref(\"k8s.io/api/core/v1.Probe\"), }, }, \"startupProbe\": { SchemaProps: spec.SchemaProps{ Description: \"Probes are not allowed for ephemeral containers.\", Ref:         ref(\"k8s.io/api/core/v1.Probe\"), }, }, \"lifecycle\": { SchemaProps: spec.SchemaProps{ Description: \"Lifecycle is not allowed for ephemeral containers.\", Ref:         ref(\"k8s.io/api/core/v1.Lifecycle\"), }, }, \"terminationMessagePath\": { SchemaProps: spec.SchemaProps{ Description: \"Optional: Path at which the file to which the container's termination message will be written is mounted into the container's filesystem. Message written is intended to be brief final status, such as an assertion failure message. Will be truncated by the node if greater than 4096 bytes. The total message length across all containers will be limited to 12kb. Defaults to /dev/termination-log. Cannot be updated.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"terminationMessagePolicy\": { SchemaProps: spec.SchemaProps{ Description: \"Indicate how the termination message should be populated. File will use the contents of terminationMessagePath to populate the container status message on both success and failure. FallbackToLogsOnError will use the last chunk of container log output if the termination message file is empty and the container exited with an error. The log output is limited to 2048 bytes or 80 lines, whichever is smaller. Defaults to File. Cannot be updated.nnPossible enum values:n - `\"FallbackToLogsOnError\"` will read the most recent contents of the container logs for the container status message when the container exits with an error and the terminationMessagePath has no contents.n - `\"File\"` is the default behavior and will set the container status message to the contents of the container's terminationMessagePath when the container exits.\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"FallbackToLogsOnError\", \"File\"}}, }, \"imagePullPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise. Cannot be updated. More info: https://kubernetes.io/docs/concepts/containers/images#updating-imagesnnPossible enum values:n - `\"Always\"` means that kubelet always attempts to pull the latest image. Container will fail If the pull fails.n - `\"IfNotPresent\"` means that kubelet pulls if the image isn't present on disk. Container will fail if the image isn't present and the pull fails.n - `\"Never\"` means that kubelet never pulls an image, but only uses a local image. Container will fail if the image isn't present\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"Always\", \"IfNotPresent\", \"Never\"}}, }, \"securityContext\": { SchemaProps: spec.SchemaProps{ Description: \"Optional: SecurityContext defines the security options the ephemeral container should be run with. If set, the fields of SecurityContext override the equivalent fields of PodSecurityContext.\", Ref:         ref(\"k8s.io/api/core/v1.SecurityContext\"), }, }, \"stdin\": { SchemaProps: spec.SchemaProps{ Description: \"Whether this container should allocate a buffer for stdin in the container runtime. If this is not set, reads from stdin in the container will always result in EOF. Default is false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"stdinOnce\": { SchemaProps: spec.SchemaProps{ Description: \"Whether the container runtime should close the stdin channel after it has been opened by a single attach. When stdin is true the stdin stream will remain open across multiple attach sessions. If stdinOnce is set to true, stdin is opened on container start, is empty until the first client attaches to stdin, and then remains open and accepts data until the client disconnects, at which time stdin is closed and remains closed until the container is restarted. If this flag is false, a container processes that reads from stdin will never receive an EOF. Default is false\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"tty\": { SchemaProps: spec.SchemaProps{ Description: \"Whether this container should allocate a TTY for itself, also requires 'stdin' to be true. Default is false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"targetContainerName\": { SchemaProps: spec.SchemaProps{ Description: \"If set, the name of the container from PodSpec that this ephemeral container targets. The ephemeral container will be run in the namespaces (IPC, PID, etc) of this container. If not set then the ephemeral container uses the namespaces configured in the Pod spec.nnThe container runtime must implement support for this feature. If the runtime does not support namespace targeting then the result of setting this field is undefined.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ContainerPort\", \"k8s.io/api/core/v1.EnvFromSource\", \"k8s.io/api/core/v1.EnvVar\", \"k8s.io/api/core/v1.Lifecycle\", \"k8s.io/api/core/v1.Probe\", \"k8s.io/api/core/v1.ResourceRequirements\", \"k8s.io/api/core/v1.SecurityContext\", \"k8s.io/api/core/v1.VolumeDevice\", \"k8s.io/api/core/v1.VolumeMount\"}, } } func schema_k8sio_api_core_v1_EphemeralContainerCommon(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EphemeralContainerCommon is a copy of all fields in Container to be inlined in EphemeralContainer. This separate type allows easy conversion from EphemeralContainer to Container and allows separate documentation for the fields of EphemeralContainer. When a new field is added to Container it must be added here as well.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the ephemeral container specified as a DNS_LABEL. This name must be unique among all containers, init containers and ephemeral containers.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"image\": { SchemaProps: spec.SchemaProps{ Description: \"Container image name. More info: https://kubernetes.io/docs/concepts/containers/images\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"command\": { SchemaProps: spec.SchemaProps{ Description: \"Entrypoint array. Not executed within a shell. The image's ENTRYPOINT is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container's environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. \"$$(VAR_NAME)\" will produce the string literal \"$(VAR_NAME)\". Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"args\": { SchemaProps: spec.SchemaProps{ Description: \"Arguments to the entrypoint. The image's CMD is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container's environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. \"$$(VAR_NAME)\" will produce the string literal \"$(VAR_NAME)\". Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"workingDir\": { SchemaProps: spec.SchemaProps{ Description: \"Container's working directory. If not specified, the container runtime's default will be used, which might be configured in the container image. Cannot be updated.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ports\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"containerPort\", \"protocol\", }, \"x-kubernetes-list-type\":       \"map\", \"x-kubernetes-patch-merge-key\": \"containerPort\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Ports are not allowed for ephemeral containers.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.ContainerPort\"), }, }, }, }, }, \"envFrom\": { SchemaProps: spec.SchemaProps{ Description: \"List of sources to populate environment variables in the container. The keys defined within a source must be a C_IDENTIFIER. All invalid keys will be reported as an event when the container is starting. When a key exists in multiple sources, the value associated with the last source will take precedence. Values defined by an Env with a duplicate key will take precedence. Cannot be updated.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.EnvFromSource\"), }, }, }, }, }, \"env\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"name\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"List of environment variables to set in the container. Cannot be updated.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.EnvVar\"), }, }, }, }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"Resources are not allowed for ephemeral containers. Ephemeral containers use spare resources already allocated to the pod.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.ResourceRequirements\"), }, }, \"volumeMounts\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"mountPath\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Pod volumes to mount into the container's filesystem. Subpath mounts are not allowed for ephemeral containers. Cannot be updated.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.VolumeMount\"), }, }, }, }, }, \"volumeDevices\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"devicePath\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"volumeDevices is the list of block devices to be used by the container.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.VolumeDevice\"), }, }, }, }, }, \"livenessProbe\": { SchemaProps: spec.SchemaProps{ Description: \"Probes are not allowed for ephemeral containers.\", Ref:         ref(\"k8s.io/api/core/v1.Probe\"), }, }, \"readinessProbe\": { SchemaProps: spec.SchemaProps{ Description: \"Probes are not allowed for ephemeral containers.\", Ref:         ref(\"k8s.io/api/core/v1.Probe\"), }, }, \"startupProbe\": { SchemaProps: spec.SchemaProps{ Description: \"Probes are not allowed for ephemeral containers.\", Ref:         ref(\"k8s.io/api/core/v1.Probe\"), }, }, \"lifecycle\": { SchemaProps: spec.SchemaProps{ Description: \"Lifecycle is not allowed for ephemeral containers.\", Ref:         ref(\"k8s.io/api/core/v1.Lifecycle\"), }, }, \"terminationMessagePath\": { SchemaProps: spec.SchemaProps{ Description: \"Optional: Path at which the file to which the container's termination message will be written is mounted into the container's filesystem. Message written is intended to be brief final status, such as an assertion failure message. Will be truncated by the node if greater than 4096 bytes. The total message length across all containers will be limited to 12kb. Defaults to /dev/termination-log. Cannot be updated.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"terminationMessagePolicy\": { SchemaProps: spec.SchemaProps{ Description: \"Indicate how the termination message should be populated. File will use the contents of terminationMessagePath to populate the container status message on both success and failure. FallbackToLogsOnError will use the last chunk of container log output if the termination message file is empty and the container exited with an error. The log output is limited to 2048 bytes or 80 lines, whichever is smaller. Defaults to File. Cannot be updated.nnPossible enum values:n - `\"FallbackToLogsOnError\"` will read the most recent contents of the container logs for the container status message when the container exits with an error and the terminationMessagePath has no contents.n - `\"File\"` is the default behavior and will set the container status message to the contents of the container's terminationMessagePath when the container exits.\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"FallbackToLogsOnError\", \"File\"}}, }, \"imagePullPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise. Cannot be updated. More info: https://kubernetes.io/docs/concepts/containers/images#updating-imagesnnPossible enum values:n - `\"Always\"` means that kubelet always attempts to pull the latest image. Container will fail If the pull fails.n - `\"IfNotPresent\"` means that kubelet pulls if the image isn't present on disk. Container will fail if the image isn't present and the pull fails.n - `\"Never\"` means that kubelet never pulls an image, but only uses a local image. Container will fail if the image isn't present\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"Always\", \"IfNotPresent\", \"Never\"}}, }, \"securityContext\": { SchemaProps: spec.SchemaProps{ Description: \"Optional: SecurityContext defines the security options the ephemeral container should be run with. If set, the fields of SecurityContext override the equivalent fields of PodSecurityContext.\", Ref:         ref(\"k8s.io/api/core/v1.SecurityContext\"), }, }, \"stdin\": { SchemaProps: spec.SchemaProps{ Description: \"Whether this container should allocate a buffer for stdin in the container runtime. If this is not set, reads from stdin in the container will always result in EOF. Default is false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"stdinOnce\": { SchemaProps: spec.SchemaProps{ Description: \"Whether the container runtime should close the stdin channel after it has been opened by a single attach. When stdin is true the stdin stream will remain open across multiple attach sessions. If stdinOnce is set to true, stdin is opened on container start, is empty until the first client attaches to stdin, and then remains open and accepts data until the client disconnects, at which time stdin is closed and remains closed until the container is restarted. If this flag is false, a container processes that reads from stdin will never receive an EOF. Default is false\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"tty\": { SchemaProps: spec.SchemaProps{ Description: \"Whether this container should allocate a TTY for itself, also requires 'stdin' to be true. Default is false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"name\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ContainerPort\", \"k8s.io/api/core/v1.EnvFromSource\", \"k8s.io/api/core/v1.EnvVar\", \"k8s.io/api/core/v1.Lifecycle\", \"k8s.io/api/core/v1.Probe\", \"k8s.io/api/core/v1.ResourceRequirements\", \"k8s.io/api/core/v1.SecurityContext\", \"k8s.io/api/core/v1.VolumeDevice\", \"k8s.io/api/core/v1.VolumeMount\"}, } } func schema_k8sio_api_core_v1_EphemeralVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents an ephemeral volume that is handled by a normal storage driver.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"volumeClaimTemplate\": { SchemaProps: spec.SchemaProps{ Description: \"Will be used to create a stand-alone PVC to provision the volume. The pod in which this EphemeralVolumeSource is embedded will be the owner of the PVC, i.e. the PVC will be deleted together with the pod.  The name of the PVC will be `<pod name>-<volume name>` where `<volume name>` is the name from the `PodSpec.Volumes` array entry. Pod validation will reject the pod if the concatenated name is not valid for a PVC (for example, too long).nnAn existing PVC with that name that is not owned by the pod will *not* be used for the pod to avoid using an unrelated volume by mistake. Starting the pod is then blocked until the unrelated PVC is removed. If such a pre-created PVC is meant to be used by the pod, the PVC has to updated with an owner reference to the pod once the pod exists. Normally this should not be necessary, but it may be useful when manually reconstructing a broken cluster.nnThis field is read-only and no changes will be made by Kubernetes to the PVC after it has been created.nnRequired, must not be nil.\", Ref:         ref(\"k8s.io/api/core/v1.PersistentVolumeClaimTemplate\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PersistentVolumeClaimTemplate\"}, } } func schema_k8sio_api_core_v1_Event(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Event is a report of an event somewhere in the cluster.  Events have a limited retention time and triggers and messages may evolve with time.  Event consumers should not rely on the timing of an event with a given Reason reflecting a consistent underlying trigger, or the continued existence of events with that Reason.  Events should be treated as informative, best-effort, supplemental data.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"involvedObject\": { SchemaProps: spec.SchemaProps{ Description: \"The object that this event is about.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.ObjectReference\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"This should be a short, machine understandable string that gives the reason for the transition into the object's current status.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"A human-readable description of the status of this operation.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"source\": { SchemaProps: spec.SchemaProps{ Description: \"The component reporting this event. Should be a short machine understandable string.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.EventSource\"), }, }, \"firstTimestamp\": { SchemaProps: spec.SchemaProps{ Description: \"The time at which the event was first recorded. (Time of server receipt is in TypeMeta.)\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"lastTimestamp\": { SchemaProps: spec.SchemaProps{ Description: \"The time at which the most recent occurrence of this event was recorded.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"count\": { SchemaProps: spec.SchemaProps{ Description: \"The number of times this event has occurred.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of this event (Normal, Warning), new types could be added in the future\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"eventTime\": { SchemaProps: spec.SchemaProps{ Description: \"Time when this Event was first observed.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"), }, }, \"series\": { SchemaProps: spec.SchemaProps{ Description: \"Data about the Event series this event represents or nil if it's a singleton Event.\", Ref:         ref(\"k8s.io/api/core/v1.EventSeries\"), }, }, \"action\": { SchemaProps: spec.SchemaProps{ Description: \"What action was taken/failed regarding to the Regarding object.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"related\": { SchemaProps: spec.SchemaProps{ Description: \"Optional secondary object for more complex actions.\", Ref:         ref(\"k8s.io/api/core/v1.ObjectReference\"), }, }, \"reportingComponent\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the controller that emitted this Event, e.g. `kubernetes.io/kubelet`.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"reportingInstance\": { SchemaProps: spec.SchemaProps{ Description: \"ID of the controller instance, e.g. `kubelet-xyzf`.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"metadata\", \"involvedObject\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.EventSeries\", \"k8s.io/api/core/v1.EventSource\", \"k8s.io/api/core/v1.ObjectReference\", \"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_core_v1_EventList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EventList is a list of events.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of events\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.Event\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.Event\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_core_v1_EventSeries(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EventSeries contain information on series of events, i.e. thing that was/is happening continuously for some time.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"count\": { SchemaProps: spec.SchemaProps{ Description: \"Number of occurrences in this series up to the last heartbeat time\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"lastObservedTime\": { SchemaProps: spec.SchemaProps{ Description: \"Time of the last occurrence observed\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"}, } } func schema_k8sio_api_core_v1_EventSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EventSource contains information for an event.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"component\": { SchemaProps: spec.SchemaProps{ Description: \"Component from which the event is generated.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"host\": { SchemaProps: spec.SchemaProps{ Description: \"Node name on which the event is generated.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_core_v1_ExecAction(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExecAction describes a \"run in container\" action.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"command\": { SchemaProps: spec.SchemaProps{ Description: \"Command is the command line to execute inside the container, the working directory for the command  is root ('/') in the container's filesystem. The command is simply exec'd, it is not run inside a shell, so traditional shell instructions ('|', etc) won't work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, } } func schema_k8sio_api_core_v1_FCVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a Fibre Channel volume. Fibre Channel volumes can only be mounted as read/write once. Fibre Channel volumes support ownership management and SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"targetWWNs\": { SchemaProps: spec.SchemaProps{ Description: \"targetWWNs is Optional: FC target worldwide names (WWNs)\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"lun\": { SchemaProps: spec.SchemaProps{ Description: \"lun is Optional: FC target lun number\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly is Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"wwids\": { SchemaProps: spec.SchemaProps{ Description: \"wwids Optional: FC volume world wide identifiers (wwids) Either wwids or combination of targetWWNs and lun must be set, but not both simultaneously.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, } } func schema_k8sio_api_core_v1_FlexPersistentVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlexPersistentVolumeSource represents a generic persistent volume resource that is provisioned/attached using an exec based plugin.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"driver\": { SchemaProps: spec.SchemaProps{ Description: \"driver is the name of the driver to use for this volume.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType is the Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. \"ext4\", \"xfs\", \"ntfs\". The default filesystem depends on FlexVolume script.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"secretRef\": { SchemaProps: spec.SchemaProps{ Description: \"secretRef is Optional: SecretRef is reference to the secret object containing sensitive information to pass to the plugin scripts. This may be empty if no secret object is specified. If the secret object contains more than one secret, all secrets are passed to the plugin scripts.\", Ref:         ref(\"k8s.io/api/core/v1.SecretReference\"), }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly is Optional: defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"options\": { SchemaProps: spec.SchemaProps{ Description: \"options is Optional: this field holds extra command options if any.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"driver\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.SecretReference\"}, } } func schema_k8sio_api_core_v1_FlexVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"driver\": { SchemaProps: spec.SchemaProps{ Description: \"driver is the name of the driver to use for this volume.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. \"ext4\", \"xfs\", \"ntfs\". The default filesystem depends on FlexVolume script.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"secretRef\": { SchemaProps: spec.SchemaProps{ Description: \"secretRef is Optional: secretRef is reference to the secret object containing sensitive information to pass to the plugin scripts. This may be empty if no secret object is specified. If the secret object contains more than one secret, all secrets are passed to the plugin scripts.\", Ref:         ref(\"k8s.io/api/core/v1.LocalObjectReference\"), }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly is Optional: defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"options\": { SchemaProps: spec.SchemaProps{ Description: \"options is Optional: this field holds extra command options if any.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"driver\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.LocalObjectReference\"}, } } func schema_k8sio_api_core_v1_FlockerVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a Flocker volume mounted by the Flocker agent. One and only one of datasetName and datasetUUID should be set. Flocker volumes do not support ownership management or SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"datasetName\": { SchemaProps: spec.SchemaProps{ Description: \"datasetName is Name of the dataset stored as metadata -> name on the dataset for Flocker should be considered as deprecated\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"datasetUUID\": { SchemaProps: spec.SchemaProps{ Description: \"datasetUUID is the UUID of the dataset. This is unique identifier of a Flocker dataset\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_core_v1_GCEPersistentDiskVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a Persistent Disk resource in Google Compute Engine.nnA GCE PD must exist before mounting to a container. The disk must also be in the same GCE project and zone as the kubelet. A GCE PD can only be mounted as read/write once or read-only many times. GCE PDs support ownership management and SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"pdName\": { SchemaProps: spec.SchemaProps{ Description: \"pdName is unique name of the PD resource in GCE. Used to identify the disk in GCE. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType is filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"partition\": { SchemaProps: spec.SchemaProps{ Description: \"partition is the partition in the volume that you want to mount. If omitted, the default is to mount by volume name. Examples: For volume /dev/sda1, you specify the partition as \"1\". Similarly, the volume partition for /dev/sda is \"0\" (or you can leave the property empty). More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"pdName\"}, }, }, } } func schema_k8sio_api_core_v1_GRPCAction(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, Properties: map[string]spec.Schema{ \"port\": { SchemaProps: spec.SchemaProps{ Description: \"Port number of the gRPC service. Number must be in the range 1 to 65535.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"service\": { SchemaProps: spec.SchemaProps{ Description: \"Service is the name of the service to place in the gRPC HealthCheckRequest (see https://github.com/grpc/grpc/blob/master/doc/health-checking.md).nnIf this is not specified, the default behavior is defined by gRPC.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"port\"}, }, }, } } func schema_k8sio_api_core_v1_GitRepoVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a volume that is populated with the contents of a git repository. Git repo volumes do not support ownership management. Git repo volumes support SELinux relabeling.nnDEPRECATED: GitRepo is deprecated. To provision a container with a git repo, mount an EmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir into the Pod's container.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"repository\": { SchemaProps: spec.SchemaProps{ Description: \"repository is the URL\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"revision\": { SchemaProps: spec.SchemaProps{ Description: \"revision is the commit hash for the specified revision.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"directory\": { SchemaProps: spec.SchemaProps{ Description: \"directory is the target directory name. Must not contain or start with '..'.  If '.' is supplied, the volume directory will be the git repository.  Otherwise, if specified, the volume will contain the git repository in the subdirectory with the given name.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"repository\"}, }, }, } } func schema_k8sio_api_core_v1_GlusterfsPersistentVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a Glusterfs mount that lasts the lifetime of a pod. Glusterfs volumes do not support ownership management or SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"endpoints\": { SchemaProps: spec.SchemaProps{ Description: \"endpoints is the endpoint name that details Glusterfs topology. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"path\": { SchemaProps: spec.SchemaProps{ Description: \"path is the Glusterfs volume path. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly here will force the Glusterfs volume to be mounted with read-only permissions. Defaults to false. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"endpointsNamespace\": { SchemaProps: spec.SchemaProps{ Description: \"endpointsNamespace is the namespace that contains Glusterfs endpoint. If this field is empty, the EndpointNamespace defaults to the same namespace as the bound PVC. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"endpoints\", \"path\"}, }, }, } } func schema_k8sio_api_core_v1_GlusterfsVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a Glusterfs mount that lasts the lifetime of a pod. Glusterfs volumes do not support ownership management or SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"endpoints\": { SchemaProps: spec.SchemaProps{ Description: \"endpoints is the endpoint name that details Glusterfs topology. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"path\": { SchemaProps: spec.SchemaProps{ Description: \"path is the Glusterfs volume path. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly here will force the Glusterfs volume to be mounted with read-only permissions. Defaults to false. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"endpoints\", \"path\"}, }, }, } } func schema_k8sio_api_core_v1_HTTPGetAction(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HTTPGetAction describes an action based on HTTP Get requests.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"path\": { SchemaProps: spec.SchemaProps{ Description: \"Path to access on the HTTP server.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"port\": { SchemaProps: spec.SchemaProps{ Description: \"Name or number of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, \"host\": { SchemaProps: spec.SchemaProps{ Description: \"Host name to connect to, defaults to the pod IP. You probably want to set \"Host\" in httpHeaders instead.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"scheme\": { SchemaProps: spec.SchemaProps{ Description: \"Scheme to use for connecting to the host. Defaults to HTTP.nnPossible enum values:n - `\"HTTP\"` means that the scheme used will be http://n - `\"HTTPS\"` means that the scheme used will be https://\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"HTTP\", \"HTTPS\"}}, }, \"httpHeaders\": { SchemaProps: spec.SchemaProps{ Description: \"Custom headers to set in the request. HTTP allows repeated headers.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.HTTPHeader\"), }, }, }, }, }, }, Required: []string{\"port\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.HTTPHeader\", \"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"}, } } func schema_k8sio_api_core_v1_HTTPHeader(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HTTPHeader describes a custom header to be used in HTTP probes\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"The header field name\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"value\": { SchemaProps: spec.SchemaProps{ Description: \"The header field value\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"value\"}, }, }, } } func schema_k8sio_api_core_v1_HostAlias(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HostAlias holds the mapping between IP and hostnames that will be injected as an entry in the pod's hosts file.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ip\": { SchemaProps: spec.SchemaProps{ Description: \"IP address of the host file entry.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"hostnames\": { SchemaProps: spec.SchemaProps{ Description: \"Hostnames for the above IP address.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, } } func schema_k8sio_api_core_v1_HostPathVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a host path mapped into a pod. Host path volumes do not support ownership management or SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"path\": { SchemaProps: spec.SchemaProps{ Description: \"path of the directory on the host. If the path is a symlink, it will follow the link to the real path. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type for HostPath Volume Defaults to \"\" More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"path\"}, }, }, } } func schema_k8sio_api_core_v1_ISCSIPersistentVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ISCSIPersistentVolumeSource represents an ISCSI disk. ISCSI volumes can only be mounted as read/write once. ISCSI volumes support ownership management and SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"targetPortal\": { SchemaProps: spec.SchemaProps{ Description: \"targetPortal is iSCSI Target Portal. The Portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260).\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"iqn\": { SchemaProps: spec.SchemaProps{ Description: \"iqn is Target iSCSI Qualified Name.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lun\": { SchemaProps: spec.SchemaProps{ Description: \"lun is iSCSI Target Lun number.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"iscsiInterface\": { SchemaProps: spec.SchemaProps{ Description: \"iscsiInterface is the interface Name that uses an iSCSI transport. Defaults to 'default' (tcp).\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType is the filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#iscsi\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"portals\": { SchemaProps: spec.SchemaProps{ Description: \"portals is the iSCSI Target Portal List. The Portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260).\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"chapAuthDiscovery\": { SchemaProps: spec.SchemaProps{ Description: \"chapAuthDiscovery defines whether support iSCSI Discovery CHAP authentication\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"chapAuthSession\": { SchemaProps: spec.SchemaProps{ Description: \"chapAuthSession defines whether support iSCSI Session CHAP authentication\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"secretRef\": { SchemaProps: spec.SchemaProps{ Description: \"secretRef is the CHAP Secret for iSCSI target and initiator authentication\", Ref:         ref(\"k8s.io/api/core/v1.SecretReference\"), }, }, \"initiatorName\": { SchemaProps: spec.SchemaProps{ Description: \"initiatorName is the custom iSCSI Initiator Name. If initiatorName is specified with iscsiInterface simultaneously, new iSCSI interface <target portal>:<volume name> will be created for the connection.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"targetPortal\", \"iqn\", \"lun\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.SecretReference\"}, } } func schema_k8sio_api_core_v1_ISCSIVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents an ISCSI disk. ISCSI volumes can only be mounted as read/write once. ISCSI volumes support ownership management and SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"targetPortal\": { SchemaProps: spec.SchemaProps{ Description: \"targetPortal is iSCSI Target Portal. The Portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260).\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"iqn\": { SchemaProps: spec.SchemaProps{ Description: \"iqn is the target iSCSI Qualified Name.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lun\": { SchemaProps: spec.SchemaProps{ Description: \"lun represents iSCSI Target Lun number.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"iscsiInterface\": { SchemaProps: spec.SchemaProps{ Description: \"iscsiInterface is the interface Name that uses an iSCSI transport. Defaults to 'default' (tcp).\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType is the filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#iscsi\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"portals\": { SchemaProps: spec.SchemaProps{ Description: \"portals is the iSCSI Target Portal List. The portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260).\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"chapAuthDiscovery\": { SchemaProps: spec.SchemaProps{ Description: \"chapAuthDiscovery defines whether support iSCSI Discovery CHAP authentication\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"chapAuthSession\": { SchemaProps: spec.SchemaProps{ Description: \"chapAuthSession defines whether support iSCSI Session CHAP authentication\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"secretRef\": { SchemaProps: spec.SchemaProps{ Description: \"secretRef is the CHAP Secret for iSCSI target and initiator authentication\", Ref:         ref(\"k8s.io/api/core/v1.LocalObjectReference\"), }, }, \"initiatorName\": { SchemaProps: spec.SchemaProps{ Description: \"initiatorName is the custom iSCSI Initiator Name. If initiatorName is specified with iscsiInterface simultaneously, new iSCSI interface <target portal>:<volume name> will be created for the connection.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"targetPortal\", \"iqn\", \"lun\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.LocalObjectReference\"}, } } func schema_k8sio_api_core_v1_KeyToPath(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Maps a string key to a path within a volume.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"key\": { SchemaProps: spec.SchemaProps{ Description: \"key is the key to project.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"path\": { SchemaProps: spec.SchemaProps{ Description: \"path is the relative path of the file to map the key to. May not be an absolute path. May not contain the path element '..'. May not start with the string '..'.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"mode\": { SchemaProps: spec.SchemaProps{ Description: \"mode is Optional: mode bits used to set permissions on this file. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"key\", \"path\"}, }, }, } } func schema_k8sio_api_core_v1_Lifecycle(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Lifecycle describes actions that the management system should take in response to container lifecycle events. For the PostStart and PreStop lifecycle handlers, management of the container blocks until the action is complete, unless the container process fails, in which case the handler is aborted.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"postStart\": { SchemaProps: spec.SchemaProps{ Description: \"PostStart is called immediately after a container is created. If the handler fails, the container is terminated and restarted according to its restart policy. Other management of the container blocks until the hook completes. More info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks\", Ref:         ref(\"k8s.io/api/core/v1.LifecycleHandler\"), }, }, \"preStop\": { SchemaProps: spec.SchemaProps{ Description: \"PreStop is called immediately before a container is terminated due to an API request or management event such as liveness/startup probe failure, preemption, resource contention, etc. The handler is not called if the container crashes or exits. The Pod's termination grace period countdown begins before the PreStop hook is executed. Regardless of the outcome of the handler, the container will eventually terminate within the Pod's termination grace period (unless delayed by finalizers). Other management of the container blocks until the hook completes or until the termination grace period is reached. More info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks\", Ref:         ref(\"k8s.io/api/core/v1.LifecycleHandler\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.LifecycleHandler\"}, } } func schema_k8sio_api_core_v1_LifecycleHandler(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LifecycleHandler defines a specific action that should be taken in a lifecycle hook. One and only one of the fields, except TCPSocket must be specified.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"exec\": { SchemaProps: spec.SchemaProps{ Description: \"Exec specifies the action to take.\", Ref:         ref(\"k8s.io/api/core/v1.ExecAction\"), }, }, \"httpGet\": { SchemaProps: spec.SchemaProps{ Description: \"HTTPGet specifies the http request to perform.\", Ref:         ref(\"k8s.io/api/core/v1.HTTPGetAction\"), }, }, \"tcpSocket\": { SchemaProps: spec.SchemaProps{ Description: \"Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept for the backward compatibility. There are no validation of this field and lifecycle hooks will fail in runtime when tcp handler is specified.\", Ref:         ref(\"k8s.io/api/core/v1.TCPSocketAction\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ExecAction\", \"k8s.io/api/core/v1.HTTPGetAction\", \"k8s.io/api/core/v1.TCPSocketAction\"}, } } func schema_k8sio_api_core_v1_LimitRange(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LimitRange sets resource usage limits for each kind of resource in a Namespace.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec defines the limits enforced. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.LimitRangeSpec\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.LimitRangeSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_LimitRangeItem(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LimitRangeItem defines a min/max usage limit for any resource that matches on kind.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of resource that this limit applies to.nnPossible enum values:n - `\"Container\"` Limit that applies to all containers in a namespacen - `\"PersistentVolumeClaim\"` Limit that applies to all persistent volume claims in a namespacen - `\"Pod\"` Limit that applies to all pods in a namespace\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"Container\", \"PersistentVolumeClaim\", \"Pod\"}}, }, \"max\": { SchemaProps: spec.SchemaProps{ Description: \"Max usage constraints on this kind by resource name.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, \"min\": { SchemaProps: spec.SchemaProps{ Description: \"Min usage constraints on this kind by resource name.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, \"default\": { SchemaProps: spec.SchemaProps{ Description: \"Default resource requirement limit value by resource name if resource limit is omitted.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, \"defaultRequest\": { SchemaProps: spec.SchemaProps{ Description: \"DefaultRequest is the default resource requirement request value by resource name if resource request is omitted.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, \"maxLimitRequestRatio\": { SchemaProps: spec.SchemaProps{ Description: \"MaxLimitRequestRatio if specified, the named resource must have a request and limit that are both non-zero where limit divided by request is less than or equal to the enumerated value; this represents the max burst for the named resource.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, }, Required: []string{\"type\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_core_v1_LimitRangeList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LimitRangeList is a list of LimitRange items.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of LimitRange objects. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.LimitRange\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.LimitRange\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_core_v1_LimitRangeSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LimitRangeSpec defines a min/max usage limit for resources that match on kind.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"limits\": { SchemaProps: spec.SchemaProps{ Description: \"Limits is the list of LimitRangeItem objects that are enforced.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.LimitRangeItem\"), }, }, }, }, }, }, Required: []string{\"limits\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.LimitRangeItem\"}, } } func schema_k8sio_api_core_v1_List(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"List holds a list of objects, which may not be known by the server.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of objects\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/runtime.RawExtension\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/apimachinery/pkg/runtime.RawExtension\"}, } } func schema_k8sio_api_core_v1_LoadBalancerIngress(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LoadBalancerIngress represents the status of a load-balancer ingress point: traffic intended for the service should be sent to an ingress point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ip\": { SchemaProps: spec.SchemaProps{ Description: \"IP is set for load-balancer ingress points that are IP based (typically GCE or OpenStack load-balancers)\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"hostname\": { SchemaProps: spec.SchemaProps{ Description: \"Hostname is set for load-balancer ingress points that are DNS based (typically AWS load-balancers)\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ports\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Ports is a list of records of service ports If used, every port defined in the service should have an entry in it\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.PortStatus\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PortStatus\"}, } } func schema_k8sio_api_core_v1_LoadBalancerStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LoadBalancerStatus represents the status of a load-balancer.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ingress\": { SchemaProps: spec.SchemaProps{ Description: \"Ingress is a list containing ingress points for the load-balancer. Traffic intended for the service should be sent to these ingress points.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.LoadBalancerIngress\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.LoadBalancerIngress\"}, } } func schema_k8sio_api_core_v1_LocalObjectReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, } } func schema_k8sio_api_core_v1_LocalVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Local represents directly-attached storage with node affinity (Beta feature)\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"path\": { SchemaProps: spec.SchemaProps{ Description: \"path of the full path to the volume on the node. It can be either a directory or block device (disk, partition, ...).\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType is the filesystem type to mount. It applies only when the Path is a block device. Must be a filesystem type supported by the host operating system. Ex. \"ext4\", \"xfs\", \"ntfs\". The default value is to auto-select a filesystem if unspecified.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"path\"}, }, }, } } func schema_k8sio_api_core_v1_NFSVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents an NFS mount that lasts the lifetime of a pod. NFS volumes do not support ownership management or SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"server\": { SchemaProps: spec.SchemaProps{ Description: \"server is the hostname or IP address of the NFS server. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"path\": { SchemaProps: spec.SchemaProps{ Description: \"path that is exported by the NFS server. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly here will force the NFS export to be mounted with read-only permissions. Defaults to false. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"server\", \"path\"}, }, }, } } func schema_k8sio_api_core_v1_Namespace(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Namespace provides a scope for Names. Use of multiple namespaces is optional.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec defines the behavior of the Namespace. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.NamespaceSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status describes the current status of a Namespace. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.NamespaceStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.NamespaceSpec\", \"k8s.io/api/core/v1.NamespaceStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_NamespaceCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NamespaceCondition contains details about state of namespace.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of namespace controller condition.nnPossible enum values:n - `\"NamespaceContentRemaining\"` contains information about resources remaining in a namespace.n - `\"NamespaceDeletionContentFailure\"` contains information about namespace deleter errors during deletion of resources.n - `\"NamespaceDeletionDiscoveryFailure\"` contains information about namespace deleter errors during resource discovery.n - `\"NamespaceDeletionGroupVersionParsingFailure\"` contains information about namespace deleter errors parsing GV for legacy types.n - `\"NamespaceFinalizersRemaining\"` contains information about which finalizers are on resources remaining in a namespace.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"NamespaceContentRemaining\", \"NamespaceDeletionContentFailure\", \"NamespaceDeletionDiscoveryFailure\", \"NamespaceDeletionGroupVersionParsingFailure\", \"NamespaceFinalizersRemaining\"}}, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_core_v1_NamespaceList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NamespaceList is a list of Namespaces.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of Namespace objects in the list. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.Namespace\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.Namespace\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_core_v1_NamespaceSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NamespaceSpec describes the attributes on a Namespace.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"finalizers\": { SchemaProps: spec.SchemaProps{ Description: \"Finalizers is an opaque list of values that must be empty to permanently remove object from storage. More info: https://kubernetes.io/docs/tasks/administer-cluster/namespaces/\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, } } func schema_k8sio_api_core_v1_NamespaceStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NamespaceStatus is information about the current status of a Namespace.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"phase\": { SchemaProps: spec.SchemaProps{ Description: \"Phase is the current lifecycle phase of the namespace. More info: https://kubernetes.io/docs/tasks/administer-cluster/namespaces/nnPossible enum values:n - `\"Active\"` means the namespace is available for use in the systemn - `\"Terminating\"` means the namespace is undergoing graceful termination\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"Active\", \"Terminating\"}}, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Represents the latest available observations of a namespace's current state.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.NamespaceCondition\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.NamespaceCondition\"}, } } func schema_k8sio_api_core_v1_Node(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Node is a worker node in Kubernetes. Each node will have a unique identifier in the cache (i.e. in etcd).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec defines the behavior of a node. https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.NodeSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Most recently observed status of the node. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.NodeStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.NodeSpec\", \"k8s.io/api/core/v1.NodeStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_NodeAddress(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeAddress contains information for the node's address.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Node address type, one of Hostname, ExternalIP or InternalIP.nnPossible enum values:n - `\"ExternalDNS\"` identifies a DNS name which resolves to an IP address which has the characteristics of a NodeExternalIP. The IP it resolves to may or may not be a listed NodeExternalIP address.n - `\"ExternalIP\"` identifies an IP address which is, in some way, intended to be more usable from outside the cluster then an internal IP, though no specific semantics are defined. It may be a globally routable IP, though it is not required to be. External IPs may be assigned directly to an interface on the node, like a NodeInternalIP, or alternatively, packets sent to the external IP may be NAT'ed to an internal node IP rather than being delivered directly (making the IP less efficient for node-to-node traffic than a NodeInternalIP).n - `\"Hostname\"` identifies a name of the node. Although every node can be assumed to have a NodeAddress of this type, its exact syntax and semantics are not defined, and are not consistent between different clusters.n - `\"InternalDNS\"` identifies a DNS name which resolves to an IP address which has the characteristics of a NodeInternalIP. The IP it resolves to may or may not be a listed NodeInternalIP address.n - `\"InternalIP\"` identifies an IP address which is assigned to one of the node's network interfaces. Every node should have at least one address of this type. An internal IP is normally expected to be reachable from every other node, but may not be visible to hosts outside the cluster. By default it is assumed that kube-apiserver can reach node internal IPs, though it is possible to configure clusters where this is not the case. NodeInternalIP is the default type of node IP, and does not necessarily imply that the IP is ONLY reachable internally. If a node has multiple internal IPs, no specific semantics are assigned to the additional IPs.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"ExternalDNS\", \"ExternalIP\", \"Hostname\", \"InternalDNS\", \"InternalIP\"}}, }, \"address\": { SchemaProps: spec.SchemaProps{ Description: \"The node address.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"address\"}, }, }, } } func schema_k8sio_api_core_v1_NodeAffinity(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Node affinity is a group of node affinity scheduling rules.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"requiredDuringSchedulingIgnoredDuringExecution\": { SchemaProps: spec.SchemaProps{ Description: \"If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to an update), the system may or may not try to eventually evict the pod from its node.\", Ref:         ref(\"k8s.io/api/core/v1.NodeSelector\"), }, }, \"preferredDuringSchedulingIgnoredDuringExecution\": { SchemaProps: spec.SchemaProps{ Description: \"The scheduler will prefer to schedule pods to nodes that satisfy the affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding \"weight\" to the sum if the node matches the corresponding matchExpressions; the node(s) with the highest sum are the most preferred.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.PreferredSchedulingTerm\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.NodeSelector\", \"k8s.io/api/core/v1.PreferredSchedulingTerm\"}, } } func schema_k8sio_api_core_v1_NodeCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeCondition contains condition information for a node.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of node condition.nnPossible enum values:n - `\"DiskPressure\"` means the kubelet is under pressure due to insufficient available disk.n - `\"MemoryPressure\"` means the kubelet is under pressure due to insufficient available memory.n - `\"NetworkUnavailable\"` means that network for the node is not correctly configured.n - `\"PIDPressure\"` means the kubelet is under pressure due to insufficient available PID.n - `\"Ready\"` means kubelet is healthy and ready to accept pods.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"DiskPressure\", \"MemoryPressure\", \"NetworkUnavailable\", \"PIDPressure\", \"Ready\"}}, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastHeartbeatTime\": { SchemaProps: spec.SchemaProps{ Description: \"Last time we got an update on a given condition.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"Last time the condition transit from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"(brief) reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"Human readable message indicating details about last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_core_v1_NodeConfigSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeConfigSource specifies a source of node configuration. Exactly one subfield (excluding metadata) must be non-nil. This API is deprecated since 1.22\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"configMap\": { SchemaProps: spec.SchemaProps{ Description: \"ConfigMap is a reference to a Node's ConfigMap\", Ref:         ref(\"k8s.io/api/core/v1.ConfigMapNodeConfigSource\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ConfigMapNodeConfigSource\"}, } } func schema_k8sio_api_core_v1_NodeConfigStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeConfigStatus describes the status of the config assigned by Node.Spec.ConfigSource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"assigned\": { SchemaProps: spec.SchemaProps{ Description: \"Assigned reports the checkpointed config the node will try to use. When Node.Spec.ConfigSource is updated, the node checkpoints the associated config payload to local disk, along with a record indicating intended config. The node refers to this record to choose its config checkpoint, and reports this record in Assigned. Assigned only updates in the status after the record has been checkpointed to disk. When the Kubelet is restarted, it tries to make the Assigned config the Active config by loading and validating the checkpointed payload identified by Assigned.\", Ref:         ref(\"k8s.io/api/core/v1.NodeConfigSource\"), }, }, \"active\": { SchemaProps: spec.SchemaProps{ Description: \"Active reports the checkpointed config the node is actively using. Active will represent either the current version of the Assigned config, or the current LastKnownGood config, depending on whether attempting to use the Assigned config results in an error.\", Ref:         ref(\"k8s.io/api/core/v1.NodeConfigSource\"), }, }, \"lastKnownGood\": { SchemaProps: spec.SchemaProps{ Description: \"LastKnownGood reports the checkpointed config the node will fall back to when it encounters an error attempting to use the Assigned config. The Assigned config becomes the LastKnownGood config when the node determines that the Assigned config is stable and correct. This is currently implemented as a 10-minute soak period starting when the local record of Assigned config is updated. If the Assigned config is Active at the end of this period, it becomes the LastKnownGood. Note that if Spec.ConfigSource is reset to nil (use local defaults), the LastKnownGood is also immediately reset to nil, because the local default config is always assumed good. You should not make assumptions about the node's method of determining config stability and correctness, as this may change or become configurable in the future.\", Ref:         ref(\"k8s.io/api/core/v1.NodeConfigSource\"), }, }, \"error\": { SchemaProps: spec.SchemaProps{ Description: \"Error describes any problems reconciling the Spec.ConfigSource to the Active config. Errors may occur, for example, attempting to checkpoint Spec.ConfigSource to the local Assigned record, attempting to checkpoint the payload associated with Spec.ConfigSource, attempting to load or validate the Assigned config, etc. Errors may occur at different points while syncing config. Earlier errors (e.g. download or checkpointing errors) will not result in a rollback to LastKnownGood, and may resolve across Kubelet retries. Later errors (e.g. loading or validating a checkpointed config) will result in a rollback to LastKnownGood. In the latter case, it is usually possible to resolve the error by fixing the config assigned in Spec.ConfigSource. You can find additional information for debugging by searching the error message in the Kubelet log. Error is a human-readable description of the error state; machines can check whether or not Error is empty, but should not rely on the stability of the Error text across Kubelet versions.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.NodeConfigSource\"}, } } func schema_k8sio_api_core_v1_NodeDaemonEndpoints(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeDaemonEndpoints lists ports opened by daemons running on the Node.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kubeletEndpoint\": { SchemaProps: spec.SchemaProps{ Description: \"Endpoint on which Kubelet is listening.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.DaemonEndpoint\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.DaemonEndpoint\"}, } } func schema_k8sio_api_core_v1_NodeList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeList is the whole list of all Nodes which have been registered with master.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of nodes\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.Node\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.Node\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_core_v1_NodeProxyOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeProxyOptions is the query options to a Node's proxy call.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"path\": { SchemaProps: spec.SchemaProps{ Description: \"Path is the URL path to use for the current proxy request to node.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_core_v1_NodeResources(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeResources is an object for conveying resource information about a node. see https://kubernetes.io/docs/concepts/architecture/nodes/#capacity for more details.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"Capacity\": { SchemaProps: spec.SchemaProps{ Description: \"Capacity represents the available resources of a node\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, }, Required: []string{\"Capacity\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_core_v1_NodeSelector(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"A node selector represents the union of the results of one or more label queries over a set of nodes; that is, it represents the OR of the selectors represented by the node selector terms.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"nodeSelectorTerms\": { SchemaProps: spec.SchemaProps{ Description: \"Required. A list of node selector terms. The terms are ORed.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.NodeSelectorTerm\"), }, }, }, }, }, }, Required: []string{\"nodeSelectorTerms\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.NodeSelectorTerm\"}, } } func schema_k8sio_api_core_v1_NodeSelectorRequirement(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"A node selector requirement is a selector that contains values, a key, and an operator that relates the key and values.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"key\": { SchemaProps: spec.SchemaProps{ Description: \"The label key that the selector applies to.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"operator\": { SchemaProps: spec.SchemaProps{ Description: \"Represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist. Gt, and Lt.nnPossible enum values:n - `\"DoesNotExist\"`n - `\"Exists\"`n - `\"Gt\"`n - `\"In\"`n - `\"Lt\"`n - `\"NotIn\"`\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"DoesNotExist\", \"Exists\", \"Gt\", \"In\", \"Lt\", \"NotIn\"}}, }, \"values\": { SchemaProps: spec.SchemaProps{ Description: \"An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. If the operator is Gt or Lt, the values array must have a single element, which will be interpreted as an integer. This array is replaced during a strategic merge patch.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"key\", \"operator\"}, }, }, } } func schema_k8sio_api_core_v1_NodeSelectorTerm(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"A null or empty node selector term matches no objects. The requirements of them are ANDed. The TopologySelectorTerm type implements a subset of the NodeSelectorTerm.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"matchExpressions\": { SchemaProps: spec.SchemaProps{ Description: \"A list of node selector requirements by node's labels.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.NodeSelectorRequirement\"), }, }, }, }, }, \"matchFields\": { SchemaProps: spec.SchemaProps{ Description: \"A list of node selector requirements by node's fields.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.NodeSelectorRequirement\"), }, }, }, }, }, }, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.NodeSelectorRequirement\"}, } } func schema_k8sio_api_core_v1_NodeSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeSpec describes the attributes that a node is created with.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"podCIDR\": { SchemaProps: spec.SchemaProps{ Description: \"PodCIDR represents the pod IP range assigned to the node.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"podCIDRs\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-strategy\": \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"podCIDRs represents the IP ranges assigned to the node for usage by Pods on that node. If this field is specified, the 0th entry must match the podCIDR field. It may contain at most 1 value for each of IPv4 and IPv6.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"providerID\": { SchemaProps: spec.SchemaProps{ Description: \"ID of the node assigned by the cloud provider in the format: <ProviderName>://<ProviderSpecificNodeID>\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"unschedulable\": { SchemaProps: spec.SchemaProps{ Description: \"Unschedulable controls node schedulability of new pods. By default, node is schedulable. More info: https://kubernetes.io/docs/concepts/nodes/node/#manual-node-administration\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"taints\": { SchemaProps: spec.SchemaProps{ Description: \"If specified, the node's taints.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.Taint\"), }, }, }, }, }, \"configSource\": { SchemaProps: spec.SchemaProps{ Description: \"Deprecated: Previously used to specify the source of the node's configuration for the DynamicKubeletConfig feature. This feature is removed from Kubelets as of 1.24 and will be fully removed in 1.26.\", Ref:         ref(\"k8s.io/api/core/v1.NodeConfigSource\"), }, }, \"externalID\": { SchemaProps: spec.SchemaProps{ Description: \"Deprecated. Not all kubelets will set this field. Remove field after 1.13. see: https://issues.k8s.io/61966\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.NodeConfigSource\", \"k8s.io/api/core/v1.Taint\"}, } } func schema_k8sio_api_core_v1_NodeStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeStatus is information about the current status of a node.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"capacity\": { SchemaProps: spec.SchemaProps{ Description: \"Capacity represents the total resources of a node. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#capacity\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, \"allocatable\": { SchemaProps: spec.SchemaProps{ Description: \"Allocatable represents the resources of a node that are available for scheduling. Defaults to Capacity.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, \"phase\": { SchemaProps: spec.SchemaProps{ Description: \"NodePhase is the recently observed lifecycle phase of the node. More info: https://kubernetes.io/docs/concepts/nodes/node/#phase The field is never populated, and now is deprecated.nnPossible enum values:n - `\"Pending\"` means the node has been created/added by the system, but not configured.n - `\"Running\"` means the node has been configured and has Kubernetes components running.n - `\"Terminated\"` means the node has been removed from the cluster.\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"Pending\", \"Running\", \"Terminated\"}}, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Conditions is an array of current observed node conditions. More info: https://kubernetes.io/docs/concepts/nodes/node/#condition\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.NodeCondition\"), }, }, }, }, }, \"addresses\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"List of addresses reachable to the node. Queried from cloud provider, if available. More info: https://kubernetes.io/docs/concepts/nodes/node/#addresses Note: This field is declared as mergeable, but the merge key is not sufficiently unique, which can cause data corruption when it is merged. Callers should instead use a full-replacement patch. See http://pr.k8s.io/79391 for an example.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.NodeAddress\"), }, }, }, }, }, \"daemonEndpoints\": { SchemaProps: spec.SchemaProps{ Description: \"Endpoints of daemons running on the Node.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.NodeDaemonEndpoints\"), }, }, \"nodeInfo\": { SchemaProps: spec.SchemaProps{ Description: \"Set of ids/uuids to uniquely identify the node. More info: https://kubernetes.io/docs/concepts/nodes/node/#info\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.NodeSystemInfo\"), }, }, \"images\": { SchemaProps: spec.SchemaProps{ Description: \"List of container images on this node\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.ContainerImage\"), }, }, }, }, }, \"volumesInUse\": { SchemaProps: spec.SchemaProps{ Description: \"List of attachable volumes in use (mounted) by the node.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"volumesAttached\": { SchemaProps: spec.SchemaProps{ Description: \"List of volumes that are attached to the node.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.AttachedVolume\"), }, }, }, }, }, \"config\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the config assigned to the node via the dynamic Kubelet config feature.\", Ref:         ref(\"k8s.io/api/core/v1.NodeConfigStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.AttachedVolume\", \"k8s.io/api/core/v1.ContainerImage\", \"k8s.io/api/core/v1.NodeAddress\", \"k8s.io/api/core/v1.NodeCondition\", \"k8s.io/api/core/v1.NodeConfigStatus\", \"k8s.io/api/core/v1.NodeDaemonEndpoints\", \"k8s.io/api/core/v1.NodeSystemInfo\", \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_core_v1_NodeSystemInfo(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeSystemInfo is a set of ids/uuids to uniquely identify the node.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"machineID\": { SchemaProps: spec.SchemaProps{ Description: \"MachineID reported by the node. For unique machine identification in the cluster this field is preferred. Learn more from man(5) machine-id: http://man7.org/linux/man-pages/man5/machine-id.5.html\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"systemUUID\": { SchemaProps: spec.SchemaProps{ Description: \"SystemUUID reported by the node. For unique machine identification MachineID is preferred. This field is specific to Red Hat hosts https://access.redhat.com/documentation/en-us/red_hat_subscription_management/1/html/rhsm/uuid\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"bootID\": { SchemaProps: spec.SchemaProps{ Description: \"Boot ID reported by the node.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"kernelVersion\": { SchemaProps: spec.SchemaProps{ Description: \"Kernel Version reported by the node from 'uname -r' (e.g. 3.16.0-0.bpo.4-amd64).\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"osImage\": { SchemaProps: spec.SchemaProps{ Description: \"OS Image reported by the node from /etc/os-release (e.g. Debian GNU/Linux 7 (wheezy)).\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"containerRuntimeVersion\": { SchemaProps: spec.SchemaProps{ Description: \"ContainerRuntime Version reported by the node through runtime remote API (e.g. docker://1.5.0).\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"kubeletVersion\": { SchemaProps: spec.SchemaProps{ Description: \"Kubelet Version reported by the node.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"kubeProxyVersion\": { SchemaProps: spec.SchemaProps{ Description: \"KubeProxy Version reported by the node.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"operatingSystem\": { SchemaProps: spec.SchemaProps{ Description: \"The Operating System reported by the node\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"architecture\": { SchemaProps: spec.SchemaProps{ Description: \"The Architecture reported by the node\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"machineID\", \"systemUUID\", \"bootID\", \"kernelVersion\", \"osImage\", \"containerRuntimeVersion\", \"kubeletVersion\", \"kubeProxyVersion\", \"operatingSystem\", \"architecture\"}, }, }, } } func schema_k8sio_api_core_v1_ObjectFieldSelector(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ObjectFieldSelector selects an APIVersioned field of an object.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"Version of the schema the FieldPath is written in terms of, defaults to \"v1\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fieldPath\": { SchemaProps: spec.SchemaProps{ Description: \"Path of the field to select in the specified API version.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"fieldPath\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, } } func schema_k8sio_api_core_v1_ObjectReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ObjectReference contains enough information to let you inspect or modify the referred object.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"uid\": { SchemaProps: spec.SchemaProps{ Description: \"UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"API version of the referent.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resourceVersion\": { SchemaProps: spec.SchemaProps{ Description: \"Specific resourceVersion to which this reference is made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fieldPath\": { SchemaProps: spec.SchemaProps{ Description: \"If referring to a piece of an object instead of an entire object, this string should contain a valid JSON/Go field access statement, such as desiredState.manifest.containers[2]. For example, if the object reference is to a container within a pod, this would take on a value like: \"spec.containers{name}\" (where \"name\" refers to the name of the container that triggered the event) or if no container name is specified \"spec.containers[2]\" (container with index 2 in this pod). This syntax is chosen only to have some well-defined way of referencing a part of an object.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, } } func schema_k8sio_api_core_v1_PersistentVolume(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PersistentVolume (PV) is a storage resource provisioned by an administrator. It is analogous to a node. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"spec defines a specification of a persistent volume owned by the cluster. Provisioned by an administrator. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistent-volumes\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PersistentVolumeSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"status represents the current information/status for the persistent volume. Populated by the system. Read-only. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistent-volumes\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PersistentVolumeStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PersistentVolumeSpec\", \"k8s.io/api/core/v1.PersistentVolumeStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_PersistentVolumeClaim(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PersistentVolumeClaim is a user's request for and claim to a persistent volume\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"spec defines the desired characteristics of a volume requested by a pod author. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PersistentVolumeClaimSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"status represents the current information/status of a persistent volume claim. Read-only. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PersistentVolumeClaimStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PersistentVolumeClaimSpec\", \"k8s.io/api/core/v1.PersistentVolumeClaimStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_PersistentVolumeClaimCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PersistentVolumeClaimCondition contails details about state of pvc\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"nnnPossible enum values:n - `\"FileSystemResizePending\"` - controller resize is finished and a file system resize is pending on noden - `\"Resizing\"` - a user trigger resize of pvc has been started\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"FileSystemResizePending\", \"Resizing\"}}, }, \"status\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, \"lastProbeTime\": { SchemaProps: spec.SchemaProps{ Description: \"lastProbeTime is the time we probed the condition.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"lastTransitionTime is the time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"reason is a unique, this should be a short, machine understandable string that gives the reason for condition's last transition. If it reports \"ResizeStarted\" that means the underlying persistent volume is being resized.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"message is the human-readable message indicating details about last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_core_v1_PersistentVolumeClaimList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PersistentVolumeClaimList is a list of PersistentVolumeClaim items.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is a list of persistent volume claims. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.PersistentVolumeClaim\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PersistentVolumeClaim\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_core_v1_PersistentVolumeClaimSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PersistentVolumeClaimSpec describes the common attributes of storage devices and allows a Source for provider-specific attributes\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"accessModes\": { SchemaProps: spec.SchemaProps{ Description: \"accessModes contains the desired access modes the volume should have. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#access-modes-1\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"selector is a label query over volumes to consider for binding.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"resources represents the minimum resources the volume should have. If RecoverVolumeExpansionFailure feature is enabled users are allowed to specify resource requirements that are lower than previous value but must still be higher than capacity recorded in the status field of the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#resources\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.ResourceRequirements\"), }, }, \"volumeName\": { SchemaProps: spec.SchemaProps{ Description: \"volumeName is the binding reference to the PersistentVolume backing this claim.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"storageClassName\": { SchemaProps: spec.SchemaProps{ Description: \"storageClassName is the name of the StorageClass required by the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#class-1\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"volumeMode\": { SchemaProps: spec.SchemaProps{ Description: \"volumeMode defines what type of volume is required by the claim. Value of Filesystem is implied when not included in claim spec.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"dataSource\": { SchemaProps: spec.SchemaProps{ Description: \"dataSource field can be used to specify either: * An existing VolumeSnapshot object (snapshot.storage.k8s.io/VolumeSnapshot) * An existing PVC (PersistentVolumeClaim) If the provisioner or an external controller can support the specified data source, it will create a new volume based on the contents of the specified data source. If the AnyVolumeDataSource feature gate is enabled, this field will always have the same contents as the DataSourceRef field.\", Ref:         ref(\"k8s.io/api/core/v1.TypedLocalObjectReference\"), }, }, \"dataSourceRef\": { SchemaProps: spec.SchemaProps{ Description: \"dataSourceRef specifies the object from which to populate the volume with data, if a non-empty volume is desired. This may be any local object from a non-empty API group (non core object) or a PersistentVolumeClaim object. When this field is specified, volume binding will only succeed if the type of the specified object matches some installed volume populator or dynamic provisioner. This field will replace the functionality of the DataSource field and as such if both fields are non-empty, they must have the same value. For backwards compatibility, both fields (DataSource and DataSourceRef) will be set to the same value automatically if one of them is empty and the other is non-empty. There are two important differences between DataSource and DataSourceRef: * While DataSource only allows two specific types of objects, DataSourceRefn  allows any non-core object, as well as PersistentVolumeClaim objects.n* While DataSource ignores disallowed values (dropping them), DataSourceRefn  preserves all values, and generates an error if a disallowed value isn  specified.n(Alpha) Using this field requires the AnyVolumeDataSource feature gate to be enabled.\", Ref:         ref(\"k8s.io/api/core/v1.TypedLocalObjectReference\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ResourceRequirements\", \"k8s.io/api/core/v1.TypedLocalObjectReference\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_core_v1_PersistentVolumeClaimStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PersistentVolumeClaimStatus is the current status of a persistent volume claim.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"phase\": { SchemaProps: spec.SchemaProps{ Description: \"phase represents the current phase of PersistentVolumeClaim.nnPossible enum values:n - `\"Bound\"` used for PersistentVolumeClaims that are boundn - `\"Lost\"` used for PersistentVolumeClaims that lost their underlying PersistentVolume. The claim was bound to a PersistentVolume and this volume does not exist any longer and all data on it was lost.n - `\"Pending\"` used for PersistentVolumeClaims that are not yet bound\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"Bound\", \"Lost\", \"Pending\"}}, }, \"accessModes\": { SchemaProps: spec.SchemaProps{ Description: \"accessModes contains the actual access modes the volume backing the PVC has. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#access-modes-1\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"capacity\": { SchemaProps: spec.SchemaProps{ Description: \"capacity represents the actual resources of the underlying volume.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"conditions is the current Condition of persistent volume claim. If underlying persistent volume is being resized then the Condition will be set to 'ResizeStarted'.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.PersistentVolumeClaimCondition\"), }, }, }, }, }, \"allocatedResources\": { SchemaProps: spec.SchemaProps{ Description: \"allocatedResources is the storage resource within AllocatedResources tracks the capacity allocated to a PVC. It may be larger than the actual capacity when a volume expansion operation is requested. For storage quota, the larger value from allocatedResources and PVC.spec.resources is used. If allocatedResources is not set, PVC.spec.resources alone is used for quota calculation. If a volume expansion capacity request is lowered, allocatedResources is only lowered if there are no expansion operations in progress and if the actual volume capacity is equal or lower than the requested capacity. This is an alpha field and requires enabling RecoverVolumeExpansionFailure feature.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, \"resizeStatus\": { SchemaProps: spec.SchemaProps{ Description: \"resizeStatus stores status of resize operation. ResizeStatus is not set by default but when expansion is complete resizeStatus is set to empty string by resize controller or kubelet. This is an alpha field and requires enabling RecoverVolumeExpansionFailure feature.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PersistentVolumeClaimCondition\", \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_core_v1_PersistentVolumeClaimTemplate(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PersistentVolumeClaimTemplate is used to produce PersistentVolumeClaim objects as part of an EphemeralVolumeSource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"May contain labels and annotations that will be copied into the PVC when creating it. No other fields are allowed and will be rejected during validation.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"The specification for the PersistentVolumeClaim. The entire content is copied unchanged into the PVC that gets created from this template. The same fields as in a PersistentVolumeClaim are also valid here.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PersistentVolumeClaimSpec\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PersistentVolumeClaimSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_PersistentVolumeClaimVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PersistentVolumeClaimVolumeSource references the user's PVC in the same namespace. This volume finds the bound PV and mounts that volume for the pod. A PersistentVolumeClaimVolumeSource is, essentially, a wrapper around another type of volume that is owned by someone else (the system).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"claimName\": { SchemaProps: spec.SchemaProps{ Description: \"claimName is the name of a PersistentVolumeClaim in the same namespace as the pod using this volume. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly Will force the ReadOnly setting in VolumeMounts. Default false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"claimName\"}, }, }, } } func schema_k8sio_api_core_v1_PersistentVolumeList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PersistentVolumeList is a list of PersistentVolume items.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is a list of persistent volumes. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.PersistentVolume\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PersistentVolume\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_core_v1_PersistentVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PersistentVolumeSource is similar to VolumeSource but meant for the administrator who creates PVs. Exactly one of its members must be set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"gcePersistentDisk\": { SchemaProps: spec.SchemaProps{ Description: \"gcePersistentDisk represents a GCE Disk resource that is attached to a kubelet's host machine and then exposed to the pod. Provisioned by an admin. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk\", Ref:         ref(\"k8s.io/api/core/v1.GCEPersistentDiskVolumeSource\"), }, }, \"awsElasticBlockStore\": { SchemaProps: spec.SchemaProps{ Description: \"awsElasticBlockStore represents an AWS Disk resource that is attached to a kubelet's host machine and then exposed to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore\", Ref:         ref(\"k8s.io/api/core/v1.AWSElasticBlockStoreVolumeSource\"), }, }, \"hostPath\": { SchemaProps: spec.SchemaProps{ Description: \"hostPath represents a directory on the host. Provisioned by a developer or tester. This is useful for single-node development and testing only! On-host storage is not supported in any way and WILL NOT WORK in a multi-node cluster. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath\", Ref:         ref(\"k8s.io/api/core/v1.HostPathVolumeSource\"), }, }, \"glusterfs\": { SchemaProps: spec.SchemaProps{ Description: \"glusterfs represents a Glusterfs volume that is attached to a host and exposed to the pod. Provisioned by an admin. More info: https://examples.k8s.io/volumes/glusterfs/README.md\", Ref:         ref(\"k8s.io/api/core/v1.GlusterfsPersistentVolumeSource\"), }, }, \"nfs\": { SchemaProps: spec.SchemaProps{ Description: \"nfs represents an NFS mount on the host. Provisioned by an admin. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs\", Ref:         ref(\"k8s.io/api/core/v1.NFSVolumeSource\"), }, }, \"rbd\": { SchemaProps: spec.SchemaProps{ Description: \"rbd represents a Rados Block Device mount on the host that shares a pod's lifetime. More info: https://examples.k8s.io/volumes/rbd/README.md\", Ref:         ref(\"k8s.io/api/core/v1.RBDPersistentVolumeSource\"), }, }, \"iscsi\": { SchemaProps: spec.SchemaProps{ Description: \"iscsi represents an ISCSI Disk resource that is attached to a kubelet's host machine and then exposed to the pod. Provisioned by an admin.\", Ref:         ref(\"k8s.io/api/core/v1.ISCSIPersistentVolumeSource\"), }, }, \"cinder\": { SchemaProps: spec.SchemaProps{ Description: \"cinder represents a cinder volume attached and mounted on kubelets host machine. More info: https://examples.k8s.io/mysql-cinder-pd/README.md\", Ref:         ref(\"k8s.io/api/core/v1.CinderPersistentVolumeSource\"), }, }, \"cephfs\": { SchemaProps: spec.SchemaProps{ Description: \"cephFS represents a Ceph FS mount on the host that shares a pod's lifetime\", Ref:         ref(\"k8s.io/api/core/v1.CephFSPersistentVolumeSource\"), }, }, \"fc\": { SchemaProps: spec.SchemaProps{ Description: \"fc represents a Fibre Channel resource that is attached to a kubelet's host machine and then exposed to the pod.\", Ref:         ref(\"k8s.io/api/core/v1.FCVolumeSource\"), }, }, \"flocker\": { SchemaProps: spec.SchemaProps{ Description: \"flocker represents a Flocker volume attached to a kubelet's host machine and exposed to the pod for its usage. This depends on the Flocker control service being running\", Ref:         ref(\"k8s.io/api/core/v1.FlockerVolumeSource\"), }, }, \"flexVolume\": { SchemaProps: spec.SchemaProps{ Description: \"flexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin.\", Ref:         ref(\"k8s.io/api/core/v1.FlexPersistentVolumeSource\"), }, }, \"azureFile\": { SchemaProps: spec.SchemaProps{ Description: \"azureFile represents an Azure File Service mount on the host and bind mount to the pod.\", Ref:         ref(\"k8s.io/api/core/v1.AzureFilePersistentVolumeSource\"), }, }, \"vsphereVolume\": { SchemaProps: spec.SchemaProps{ Description: \"vsphereVolume represents a vSphere volume attached and mounted on kubelets host machine\", Ref:         ref(\"k8s.io/api/core/v1.VsphereVirtualDiskVolumeSource\"), }, }, \"quobyte\": { SchemaProps: spec.SchemaProps{ Description: \"quobyte represents a Quobyte mount on the host that shares a pod's lifetime\", Ref:         ref(\"k8s.io/api/core/v1.QuobyteVolumeSource\"), }, }, \"azureDisk\": { SchemaProps: spec.SchemaProps{ Description: \"azureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.\", Ref:         ref(\"k8s.io/api/core/v1.AzureDiskVolumeSource\"), }, }, \"photonPersistentDisk\": { SchemaProps: spec.SchemaProps{ Description: \"photonPersistentDisk represents a PhotonController persistent disk attached and mounted on kubelets host machine\", Ref:         ref(\"k8s.io/api/core/v1.PhotonPersistentDiskVolumeSource\"), }, }, \"portworxVolume\": { SchemaProps: spec.SchemaProps{ Description: \"portworxVolume represents a portworx volume attached and mounted on kubelets host machine\", Ref:         ref(\"k8s.io/api/core/v1.PortworxVolumeSource\"), }, }, \"scaleIO\": { SchemaProps: spec.SchemaProps{ Description: \"scaleIO represents a ScaleIO persistent volume attached and mounted on Kubernetes nodes.\", Ref:         ref(\"k8s.io/api/core/v1.ScaleIOPersistentVolumeSource\"), }, }, \"local\": { SchemaProps: spec.SchemaProps{ Description: \"local represents directly-attached storage with node affinity\", Ref:         ref(\"k8s.io/api/core/v1.LocalVolumeSource\"), }, }, \"storageos\": { SchemaProps: spec.SchemaProps{ Description: \"storageOS represents a StorageOS volume that is attached to the kubelet's host machine and mounted into the pod More info: https://examples.k8s.io/volumes/storageos/README.md\", Ref:         ref(\"k8s.io/api/core/v1.StorageOSPersistentVolumeSource\"), }, }, \"csi\": { SchemaProps: spec.SchemaProps{ Description: \"csi represents storage that is handled by an external CSI driver (Beta feature).\", Ref:         ref(\"k8s.io/api/core/v1.CSIPersistentVolumeSource\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.AWSElasticBlockStoreVolumeSource\", \"k8s.io/api/core/v1.AzureDiskVolumeSource\", \"k8s.io/api/core/v1.AzureFilePersistentVolumeSource\", \"k8s.io/api/core/v1.CSIPersistentVolumeSource\", \"k8s.io/api/core/v1.CephFSPersistentVolumeSource\", \"k8s.io/api/core/v1.CinderPersistentVolumeSource\", \"k8s.io/api/core/v1.FCVolumeSource\", \"k8s.io/api/core/v1.FlexPersistentVolumeSource\", \"k8s.io/api/core/v1.FlockerVolumeSource\", \"k8s.io/api/core/v1.GCEPersistentDiskVolumeSource\", \"k8s.io/api/core/v1.GlusterfsPersistentVolumeSource\", \"k8s.io/api/core/v1.HostPathVolumeSource\", \"k8s.io/api/core/v1.ISCSIPersistentVolumeSource\", \"k8s.io/api/core/v1.LocalVolumeSource\", \"k8s.io/api/core/v1.NFSVolumeSource\", \"k8s.io/api/core/v1.PhotonPersistentDiskVolumeSource\", \"k8s.io/api/core/v1.PortworxVolumeSource\", \"k8s.io/api/core/v1.QuobyteVolumeSource\", \"k8s.io/api/core/v1.RBDPersistentVolumeSource\", \"k8s.io/api/core/v1.ScaleIOPersistentVolumeSource\", \"k8s.io/api/core/v1.StorageOSPersistentVolumeSource\", \"k8s.io/api/core/v1.VsphereVirtualDiskVolumeSource\"}, } } func schema_k8sio_api_core_v1_PersistentVolumeSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PersistentVolumeSpec is the specification of a persistent volume.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"capacity\": { SchemaProps: spec.SchemaProps{ Description: \"capacity is the description of the persistent volume's resources and capacity. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#capacity\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, \"gcePersistentDisk\": { SchemaProps: spec.SchemaProps{ Description: \"gcePersistentDisk represents a GCE Disk resource that is attached to a kubelet's host machine and then exposed to the pod. Provisioned by an admin. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk\", Ref:         ref(\"k8s.io/api/core/v1.GCEPersistentDiskVolumeSource\"), }, }, \"awsElasticBlockStore\": { SchemaProps: spec.SchemaProps{ Description: \"awsElasticBlockStore represents an AWS Disk resource that is attached to a kubelet's host machine and then exposed to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore\", Ref:         ref(\"k8s.io/api/core/v1.AWSElasticBlockStoreVolumeSource\"), }, }, \"hostPath\": { SchemaProps: spec.SchemaProps{ Description: \"hostPath represents a directory on the host. Provisioned by a developer or tester. This is useful for single-node development and testing only! On-host storage is not supported in any way and WILL NOT WORK in a multi-node cluster. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath\", Ref:         ref(\"k8s.io/api/core/v1.HostPathVolumeSource\"), }, }, \"glusterfs\": { SchemaProps: spec.SchemaProps{ Description: \"glusterfs represents a Glusterfs volume that is attached to a host and exposed to the pod. Provisioned by an admin. More info: https://examples.k8s.io/volumes/glusterfs/README.md\", Ref:         ref(\"k8s.io/api/core/v1.GlusterfsPersistentVolumeSource\"), }, }, \"nfs\": { SchemaProps: spec.SchemaProps{ Description: \"nfs represents an NFS mount on the host. Provisioned by an admin. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs\", Ref:         ref(\"k8s.io/api/core/v1.NFSVolumeSource\"), }, }, \"rbd\": { SchemaProps: spec.SchemaProps{ Description: \"rbd represents a Rados Block Device mount on the host that shares a pod's lifetime. More info: https://examples.k8s.io/volumes/rbd/README.md\", Ref:         ref(\"k8s.io/api/core/v1.RBDPersistentVolumeSource\"), }, }, \"iscsi\": { SchemaProps: spec.SchemaProps{ Description: \"iscsi represents an ISCSI Disk resource that is attached to a kubelet's host machine and then exposed to the pod. Provisioned by an admin.\", Ref:         ref(\"k8s.io/api/core/v1.ISCSIPersistentVolumeSource\"), }, }, \"cinder\": { SchemaProps: spec.SchemaProps{ Description: \"cinder represents a cinder volume attached and mounted on kubelets host machine. More info: https://examples.k8s.io/mysql-cinder-pd/README.md\", Ref:         ref(\"k8s.io/api/core/v1.CinderPersistentVolumeSource\"), }, }, \"cephfs\": { SchemaProps: spec.SchemaProps{ Description: \"cephFS represents a Ceph FS mount on the host that shares a pod's lifetime\", Ref:         ref(\"k8s.io/api/core/v1.CephFSPersistentVolumeSource\"), }, }, \"fc\": { SchemaProps: spec.SchemaProps{ Description: \"fc represents a Fibre Channel resource that is attached to a kubelet's host machine and then exposed to the pod.\", Ref:         ref(\"k8s.io/api/core/v1.FCVolumeSource\"), }, }, \"flocker\": { SchemaProps: spec.SchemaProps{ Description: \"flocker represents a Flocker volume attached to a kubelet's host machine and exposed to the pod for its usage. This depends on the Flocker control service being running\", Ref:         ref(\"k8s.io/api/core/v1.FlockerVolumeSource\"), }, }, \"flexVolume\": { SchemaProps: spec.SchemaProps{ Description: \"flexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin.\", Ref:         ref(\"k8s.io/api/core/v1.FlexPersistentVolumeSource\"), }, }, \"azureFile\": { SchemaProps: spec.SchemaProps{ Description: \"azureFile represents an Azure File Service mount on the host and bind mount to the pod.\", Ref:         ref(\"k8s.io/api/core/v1.AzureFilePersistentVolumeSource\"), }, }, \"vsphereVolume\": { SchemaProps: spec.SchemaProps{ Description: \"vsphereVolume represents a vSphere volume attached and mounted on kubelets host machine\", Ref:         ref(\"k8s.io/api/core/v1.VsphereVirtualDiskVolumeSource\"), }, }, \"quobyte\": { SchemaProps: spec.SchemaProps{ Description: \"quobyte represents a Quobyte mount on the host that shares a pod's lifetime\", Ref:         ref(\"k8s.io/api/core/v1.QuobyteVolumeSource\"), }, }, \"azureDisk\": { SchemaProps: spec.SchemaProps{ Description: \"azureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.\", Ref:         ref(\"k8s.io/api/core/v1.AzureDiskVolumeSource\"), }, }, \"photonPersistentDisk\": { SchemaProps: spec.SchemaProps{ Description: \"photonPersistentDisk represents a PhotonController persistent disk attached and mounted on kubelets host machine\", Ref:         ref(\"k8s.io/api/core/v1.PhotonPersistentDiskVolumeSource\"), }, }, \"portworxVolume\": { SchemaProps: spec.SchemaProps{ Description: \"portworxVolume represents a portworx volume attached and mounted on kubelets host machine\", Ref:         ref(\"k8s.io/api/core/v1.PortworxVolumeSource\"), }, }, \"scaleIO\": { SchemaProps: spec.SchemaProps{ Description: \"scaleIO represents a ScaleIO persistent volume attached and mounted on Kubernetes nodes.\", Ref:         ref(\"k8s.io/api/core/v1.ScaleIOPersistentVolumeSource\"), }, }, \"local\": { SchemaProps: spec.SchemaProps{ Description: \"local represents directly-attached storage with node affinity\", Ref:         ref(\"k8s.io/api/core/v1.LocalVolumeSource\"), }, }, \"storageos\": { SchemaProps: spec.SchemaProps{ Description: \"storageOS represents a StorageOS volume that is attached to the kubelet's host machine and mounted into the pod More info: https://examples.k8s.io/volumes/storageos/README.md\", Ref:         ref(\"k8s.io/api/core/v1.StorageOSPersistentVolumeSource\"), }, }, \"csi\": { SchemaProps: spec.SchemaProps{ Description: \"csi represents storage that is handled by an external CSI driver (Beta feature).\", Ref:         ref(\"k8s.io/api/core/v1.CSIPersistentVolumeSource\"), }, }, \"accessModes\": { SchemaProps: spec.SchemaProps{ Description: \"accessModes contains all ways the volume can be mounted. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#access-modes\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"claimRef\": { SchemaProps: spec.SchemaProps{ Description: \"claimRef is part of a bi-directional binding between PersistentVolume and PersistentVolumeClaim. Expected to be non-nil when bound. claim.VolumeName is the authoritative bind between PV and PVC. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#binding\", Ref:         ref(\"k8s.io/api/core/v1.ObjectReference\"), }, }, \"persistentVolumeReclaimPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"persistentVolumeReclaimPolicy defines what happens to a persistent volume when released from its claim. Valid options are Retain (default for manually created PersistentVolumes), Delete (default for dynamically provisioned PersistentVolumes), and Recycle (deprecated). Recycle must be supported by the volume plugin underlying this PersistentVolume. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#reclaimingnnPossible enum values:n - `\"Delete\"` means the volume will be deleted from Kubernetes on release from its claim. The volume plugin must support Deletion.n - `\"Recycle\"` means the volume will be recycled back into the pool of unbound persistent volumes on release from its claim. The volume plugin must support Recycling.n - `\"Retain\"` means the volume will be left in its current phase (Released) for manual reclamation by the administrator. The default policy is Retain.\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"Delete\", \"Recycle\", \"Retain\"}}, }, \"storageClassName\": { SchemaProps: spec.SchemaProps{ Description: \"storageClassName is the name of StorageClass to which this persistent volume belongs. Empty value means that this volume does not belong to any StorageClass.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"mountOptions\": { SchemaProps: spec.SchemaProps{ Description: \"mountOptions is the list of mount options, e.g. [\"ro\", \"soft\"]. Not validated - mount will simply fail if one is invalid. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#mount-options\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"volumeMode\": { SchemaProps: spec.SchemaProps{ Description: \"volumeMode defines if a volume is intended to be used with a formatted filesystem or to remain in raw block state. Value of Filesystem is implied when not included in spec.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"nodeAffinity\": { SchemaProps: spec.SchemaProps{ Description: \"nodeAffinity defines constraints that limit what nodes this volume can be accessed from. This field influences the scheduling of pods that use this volume.\", Ref:         ref(\"k8s.io/api/core/v1.VolumeNodeAffinity\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.AWSElasticBlockStoreVolumeSource\", \"k8s.io/api/core/v1.AzureDiskVolumeSource\", \"k8s.io/api/core/v1.AzureFilePersistentVolumeSource\", \"k8s.io/api/core/v1.CSIPersistentVolumeSource\", \"k8s.io/api/core/v1.CephFSPersistentVolumeSource\", \"k8s.io/api/core/v1.CinderPersistentVolumeSource\", \"k8s.io/api/core/v1.FCVolumeSource\", \"k8s.io/api/core/v1.FlexPersistentVolumeSource\", \"k8s.io/api/core/v1.FlockerVolumeSource\", \"k8s.io/api/core/v1.GCEPersistentDiskVolumeSource\", \"k8s.io/api/core/v1.GlusterfsPersistentVolumeSource\", \"k8s.io/api/core/v1.HostPathVolumeSource\", \"k8s.io/api/core/v1.ISCSIPersistentVolumeSource\", \"k8s.io/api/core/v1.LocalVolumeSource\", \"k8s.io/api/core/v1.NFSVolumeSource\", \"k8s.io/api/core/v1.ObjectReference\", \"k8s.io/api/core/v1.PhotonPersistentDiskVolumeSource\", \"k8s.io/api/core/v1.PortworxVolumeSource\", \"k8s.io/api/core/v1.QuobyteVolumeSource\", \"k8s.io/api/core/v1.RBDPersistentVolumeSource\", \"k8s.io/api/core/v1.ScaleIOPersistentVolumeSource\", \"k8s.io/api/core/v1.StorageOSPersistentVolumeSource\", \"k8s.io/api/core/v1.VolumeNodeAffinity\", \"k8s.io/api/core/v1.VsphereVirtualDiskVolumeSource\", \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_core_v1_PersistentVolumeStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PersistentVolumeStatus is the current status of a persistent volume.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"phase\": { SchemaProps: spec.SchemaProps{ Description: \"phase indicates if a volume is available, bound to a claim, or released by a claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#phasennPossible enum values:n - `\"Available\"` used for PersistentVolumes that are not yet bound Available volumes are held by the binder and matched to PersistentVolumeClaimsn - `\"Bound\"` used for PersistentVolumes that are boundn - `\"Failed\"` used for PersistentVolumes that failed to be correctly recycled or deleted after being released from a claimn - `\"Pending\"` used for PersistentVolumes that are not availablen - `\"Released\"` used for PersistentVolumes where the bound PersistentVolumeClaim was deleted released volumes must be recycled before becoming available again this phase is used by the persistent volume claim binder to signal to another process to reclaim the resource\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"Available\", \"Bound\", \"Failed\", \"Pending\", \"Released\"}}, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"message is a human-readable message indicating details about why the volume is in this state.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"reason is a brief CamelCase string that describes any failure and is meant for machine parsing and tidy display in the CLI.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_core_v1_PhotonPersistentDiskVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a Photon Controller persistent disk resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"pdID\": { SchemaProps: spec.SchemaProps{ Description: \"pdID is the ID that identifies Photon Controller persistent disk\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"pdID\"}, }, }, } } func schema_k8sio_api_core_v1_Pod(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Pod is a collection of containers that can run on a host. This resource is created by clients and scheduled onto hosts.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the desired behavior of the pod. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Most recently observed status of the pod. This data may not be up to date. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PodSpec\", \"k8s.io/api/core/v1.PodStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_PodAffinity(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Pod affinity is a group of inter pod affinity scheduling rules.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"requiredDuringSchedulingIgnoredDuringExecution\": { SchemaProps: spec.SchemaProps{ Description: \"If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.PodAffinityTerm\"), }, }, }, }, }, \"preferredDuringSchedulingIgnoredDuringExecution\": { SchemaProps: spec.SchemaProps{ Description: \"The scheduler will prefer to schedule pods to nodes that satisfy the affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding \"weight\" to the sum if the node has pods which matches the corresponding podAffinityTerm; the node(s) with the highest sum are the most preferred.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.WeightedPodAffinityTerm\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PodAffinityTerm\", \"k8s.io/api/core/v1.WeightedPodAffinityTerm\"}, } } func schema_k8sio_api_core_v1_PodAffinityTerm(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Defines a set of pods (namely those matching the labelSelector relative to the given namespace(s)) that this pod should be co-located (affinity) or not co-located (anti-affinity) with, where co-located is defined as running on a node whose value of the label with key <topologyKey> matches that of any node on which a pod of the set of pods is running\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"labelSelector\": { SchemaProps: spec.SchemaProps{ Description: \"A label query over a set of resources, in this case pods.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"namespaces\": { SchemaProps: spec.SchemaProps{ Description: \"namespaces specifies a static list of namespace names that the term applies to. The term is applied to the union of the namespaces listed in this field and the ones selected by namespaceSelector. null or empty namespaces list and null namespaceSelector means \"this pod's namespace\".\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"topologyKey\": { SchemaProps: spec.SchemaProps{ Description: \"This pod should be co-located (affinity) or not co-located (anti-affinity) with the pods matching the labelSelector in the specified namespaces, where co-located is defined as running on a node whose value of the label with key topologyKey matches that of any node on which any of the selected pods is running. Empty topologyKey is not allowed.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"namespaceSelector\": { SchemaProps: spec.SchemaProps{ Description: \"A label query over the set of namespaces that the term applies to. The term is applied to the union of the namespaces selected by this field and the ones listed in the namespaces field. null selector and null or empty namespaces list means \"this pod's namespace\". An empty selector ({}) matches all namespaces.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, }, Required: []string{\"topologyKey\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_core_v1_PodAntiAffinity(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Pod anti affinity is a group of inter pod anti affinity scheduling rules.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"requiredDuringSchedulingIgnoredDuringExecution\": { SchemaProps: spec.SchemaProps{ Description: \"If the anti-affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the anti-affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.PodAffinityTerm\"), }, }, }, }, }, \"preferredDuringSchedulingIgnoredDuringExecution\": { SchemaProps: spec.SchemaProps{ Description: \"The scheduler will prefer to schedule pods to nodes that satisfy the anti-affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling anti-affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding \"weight\" to the sum if the node has pods which matches the corresponding podAffinityTerm; the node(s) with the highest sum are the most preferred.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.WeightedPodAffinityTerm\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PodAffinityTerm\", \"k8s.io/api/core/v1.WeightedPodAffinityTerm\"}, } } func schema_k8sio_api_core_v1_PodAttachOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodAttachOptions is the query options to a Pod's remote attach call.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"stdin\": { SchemaProps: spec.SchemaProps{ Description: \"Stdin if true, redirects the standard input stream of the pod for this call. Defaults to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"stdout\": { SchemaProps: spec.SchemaProps{ Description: \"Stdout if true indicates that stdout is to be redirected for the attach call. Defaults to true.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"stderr\": { SchemaProps: spec.SchemaProps{ Description: \"Stderr if true indicates that stderr is to be redirected for the attach call. Defaults to true.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"tty\": { SchemaProps: spec.SchemaProps{ Description: \"TTY if true indicates that a tty will be allocated for the attach call. This is passed through the container runtime so the tty is allocated on the worker node by the container runtime. Defaults to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"container\": { SchemaProps: spec.SchemaProps{ Description: \"The container in which to execute the command. Defaults to only container if there is only one container in the pod.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_core_v1_PodCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodCondition contains details for the current condition of this pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type is the type of the condition. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-conditionsnnPossible enum values:n - `\"ContainersReady\"` indicates whether all containers in the pod are ready.n - `\"Initialized\"` means that all init containers in the pod have started successfully.n - `\"PodScheduled\"` represents status of the scheduling process for this pod.n - `\"Ready\"` means the pod is able to service requests and should be added to the load balancing pools of all matching services.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"ContainersReady\", \"Initialized\", \"PodScheduled\", \"Ready\"}}, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is the status of the condition. Can be True, False, Unknown. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-conditions\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastProbeTime\": { SchemaProps: spec.SchemaProps{ Description: \"Last time we probed the condition.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"Last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"Unique, one-word, CamelCase reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"Human-readable message indicating details about last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_core_v1_PodDNSConfig(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodDNSConfig defines the DNS parameters of a pod in addition to those generated from DNSPolicy.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"nameservers\": { SchemaProps: spec.SchemaProps{ Description: \"A list of DNS name server IP addresses. This will be appended to the base nameservers generated from DNSPolicy. Duplicated nameservers will be removed.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"searches\": { SchemaProps: spec.SchemaProps{ Description: \"A list of DNS search domains for host-name lookup. This will be appended to the base search paths generated from DNSPolicy. Duplicated search paths will be removed.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"options\": { SchemaProps: spec.SchemaProps{ Description: \"A list of DNS resolver options. This will be merged with the base options generated from DNSPolicy. Duplicated entries will be removed. Resolution options given in Options will override those that appear in the base DNSPolicy.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.PodDNSConfigOption\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PodDNSConfigOption\"}, } } func schema_k8sio_api_core_v1_PodDNSConfigOption(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodDNSConfigOption defines DNS resolver options of a pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Required.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"value\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, }, }, }, } } func schema_k8sio_api_core_v1_PodExecOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodExecOptions is the query options to a Pod's remote exec call.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"stdin\": { SchemaProps: spec.SchemaProps{ Description: \"Redirect the standard input stream of the pod for this call. Defaults to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"stdout\": { SchemaProps: spec.SchemaProps{ Description: \"Redirect the standard output stream of the pod for this call.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"stderr\": { SchemaProps: spec.SchemaProps{ Description: \"Redirect the standard error stream of the pod for this call.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"tty\": { SchemaProps: spec.SchemaProps{ Description: \"TTY if true indicates that a tty will be allocated for the exec call. Defaults to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"container\": { SchemaProps: spec.SchemaProps{ Description: \"Container in which to execute the command. Defaults to only container if there is only one container in the pod.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"command\": { SchemaProps: spec.SchemaProps{ Description: \"Command is the remote command to execute. argv array. Not executed within a shell.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"command\"}, }, }, } } func schema_k8sio_api_core_v1_PodIP(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IP address information for entries in the (plural) PodIPs field. Each entry includes:n   IP: An IP address allocated to the pod. Routable at least within the cluster.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ip\": { SchemaProps: spec.SchemaProps{ Description: \"ip is an IP address (IPv4 or IPv6) assigned to the pod\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_core_v1_PodList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodList is a list of Pods.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of pods. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.Pod\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.Pod\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_core_v1_PodLogOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodLogOptions is the query options for a Pod's logs REST call.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"container\": { SchemaProps: spec.SchemaProps{ Description: \"The container for which to stream logs. Defaults to only container if there is one container in the pod.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"follow\": { SchemaProps: spec.SchemaProps{ Description: \"Follow the log stream of the pod. Defaults to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"previous\": { SchemaProps: spec.SchemaProps{ Description: \"Return previous terminated container logs. Defaults to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"sinceSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"A relative time in seconds before the current time from which to show logs. If this value precedes the time a pod was started, only logs since the pod start will be returned. If this value is in the future, no logs will be returned. Only one of sinceSeconds or sinceTime may be specified.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"sinceTime\": { SchemaProps: spec.SchemaProps{ Description: \"An RFC3339 timestamp from which to show logs. If this value precedes the time a pod was started, only logs since the pod start will be returned. If this value is in the future, no logs will be returned. Only one of sinceSeconds or sinceTime may be specified.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"timestamps\": { SchemaProps: spec.SchemaProps{ Description: \"If true, add an RFC3339 or RFC3339Nano timestamp at the beginning of every line of log output. Defaults to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"tailLines\": { SchemaProps: spec.SchemaProps{ Description: \"If set, the number of lines from the end of the logs to show. If not specified, logs are shown from the creation of the container or sinceSeconds or sinceTime\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"limitBytes\": { SchemaProps: spec.SchemaProps{ Description: \"If set, the number of bytes to read from the server before terminating the log output. This may not display a complete final line of logging, and may return slightly more or slightly less than the specified limit.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"insecureSkipTLSVerifyBackend\": { SchemaProps: spec.SchemaProps{ Description: \"insecureSkipTLSVerifyBackend indicates that the apiserver should not confirm the validity of the serving certificate of the backend it is connecting to.  This will make the HTTPS connection between the apiserver and the backend insecure. This means the apiserver cannot verify the log data it is receiving came from the real kubelet.  If the kubelet is configured to verify the apiserver's TLS credentials, it does not mean the connection to the real kubelet is vulnerable to a man in the middle attack (e.g. an attacker could not intercept the actual log data coming from the real kubelet).\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_core_v1_PodOS(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodOS defines the OS parameters of a pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the name of the operating system. The currently supported values are linux and windows. Additional value may be defined in future and can be one of: https://github.com/opencontainers/runtime-spec/blob/master/config.md#platform-specific-configuration Clients should expect to handle additional values and treat unrecognized values in this field as os: null\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_api_core_v1_PodPortForwardOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodPortForwardOptions is the query options to a Pod's port forward call when using WebSockets. The `port` query parameter must specify the port or ports (comma separated) to forward over. Port forwarding over SPDY does not use these options. It requires the port to be passed in the `port` header as part of request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ports\": { SchemaProps: spec.SchemaProps{ Description: \"List of ports to forward Required when using WebSockets\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: 0, Type:    []string{\"integer\"}, Format:  \"int32\", }, }, }, }, }, }, }, }, } } func schema_k8sio_api_core_v1_PodProxyOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodProxyOptions is the query options to a Pod's proxy call.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"path\": { SchemaProps: spec.SchemaProps{ Description: \"Path is the URL path to use for the current proxy request to pod.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_core_v1_PodReadinessGate(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodReadinessGate contains the reference to a pod condition\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"conditionType\": { SchemaProps: spec.SchemaProps{ Description: \"ConditionType refers to a condition in the pod's condition list with matching type.nnPossible enum values:n - `\"ContainersReady\"` indicates whether all containers in the pod are ready.n - `\"Initialized\"` means that all init containers in the pod have started successfully.n - `\"PodScheduled\"` represents status of the scheduling process for this pod.n - `\"Ready\"` means the pod is able to service requests and should be added to the load balancing pools of all matching services.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"ContainersReady\", \"Initialized\", \"PodScheduled\", \"Ready\"}}, }, }, Required: []string{\"conditionType\"}, }, }, } } func schema_k8sio_api_core_v1_PodSecurityContext(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodSecurityContext holds pod-level security attributes and common container settings. Some fields are also present in container.securityContext.  Field values of container.securityContext take precedence over field values of PodSecurityContext.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"seLinuxOptions\": { SchemaProps: spec.SchemaProps{ Description: \"The SELinux context to be applied to all containers. If unspecified, the container runtime will allocate a random SELinux context for each container.  May also be set in SecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container. Note that this field cannot be set when spec.os.name is windows.\", Ref:         ref(\"k8s.io/api/core/v1.SELinuxOptions\"), }, }, \"windowsOptions\": { SchemaProps: spec.SchemaProps{ Description: \"The Windows specific settings applied to all containers. If unspecified, the options within a container's SecurityContext will be used. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is linux.\", Ref:         ref(\"k8s.io/api/core/v1.WindowsSecurityContextOptions\"), }, }, \"runAsUser\": { SchemaProps: spec.SchemaProps{ Description: \"The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified. May also be set in SecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container. Note that this field cannot be set when spec.os.name is windows.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"runAsGroup\": { SchemaProps: spec.SchemaProps{ Description: \"The GID to run the entrypoint of the container process. Uses runtime default if unset. May also be set in SecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container. Note that this field cannot be set when spec.os.name is windows.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"runAsNonRoot\": { SchemaProps: spec.SchemaProps{ Description: \"Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed. May also be set in SecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"supplementalGroups\": { SchemaProps: spec.SchemaProps{ Description: \"A list of groups applied to the first process run in each container, in addition to the container's primary GID.  If unspecified, no groups will be added to any container. Note that this field cannot be set when spec.os.name is windows.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: 0, Type:    []string{\"integer\"}, Format:  \"int64\", }, }, }, }, }, \"fsGroup\": { SchemaProps: spec.SchemaProps{ Description: \"A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to change the ownership of that volume to be owned by the pod:nn1. The owning GID will be the FSGroup 2. The setgid bit is set (new files created in the volume will be owned by FSGroup) 3. The permission bits are OR'd with rw-rw----nnIf unset, the Kubelet will not modify the ownership and permissions of any volume. Note that this field cannot be set when spec.os.name is windows.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"sysctls\": { SchemaProps: spec.SchemaProps{ Description: \"Sysctls hold a list of namespaced sysctls used for the pod. Pods with unsupported sysctls (by the container runtime) might fail to launch. Note that this field cannot be set when spec.os.name is windows.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.Sysctl\"), }, }, }, }, }, \"fsGroupChangePolicy\": { SchemaProps: spec.SchemaProps{ Description: \"fsGroupChangePolicy defines behavior of changing ownership and permission of the volume before being exposed inside Pod. This field will only apply to volume types which support fsGroup based ownership(and permissions). It will have no effect on ephemeral volume types such as: secret, configmaps and emptydir. Valid values are \"OnRootMismatch\" and \"Always\". If not specified, \"Always\" is used. Note that this field cannot be set when spec.os.name is windows.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"seccompProfile\": { SchemaProps: spec.SchemaProps{ Description: \"The seccomp options to use by the containers in this pod. Note that this field cannot be set when spec.os.name is windows.\", Ref:         ref(\"k8s.io/api/core/v1.SeccompProfile\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.SELinuxOptions\", \"k8s.io/api/core/v1.SeccompProfile\", \"k8s.io/api/core/v1.Sysctl\", \"k8s.io/api/core/v1.WindowsSecurityContextOptions\"}, } } func schema_k8sio_api_core_v1_PodSignature(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Describes the class of pods that should avoid this node. Exactly one field should be set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"podController\": { SchemaProps: spec.SchemaProps{ Description: \"Reference to controller whose pods should avoid this node.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.OwnerReference\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.OwnerReference\"}, } } func schema_k8sio_api_core_v1_PodSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodSpec is a description of a pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"volumes\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"name\", \"x-kubernetes-patch-strategy\":  \"merge,retainKeys\", }, }, SchemaProps: spec.SchemaProps{ Description: \"List of volumes that can be mounted by containers belonging to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.Volume\"), }, }, }, }, }, \"initContainers\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"name\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"List of initialization containers belonging to the pod. Init containers are executed in order prior to containers being started. If any init container fails, the pod is considered to have failed and is handled according to its restartPolicy. The name for an init container or normal container must be unique among all containers. Init containers may not have Lifecycle actions, Readiness probes, Liveness probes, or Startup probes. The resourceRequirements of an init container are taken into account during scheduling by finding the highest request/limit for each resource type, and then using the max of of that value or the sum of the normal containers. Limits are applied to init containers in a similar fashion. Init containers cannot currently be added or removed. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.Container\"), }, }, }, }, }, \"containers\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"name\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"List of containers belonging to the pod. Containers cannot currently be added or removed. There must be at least one container in a Pod. Cannot be updated.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.Container\"), }, }, }, }, }, \"ephemeralContainers\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"name\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"List of ephemeral containers run in this pod. Ephemeral containers may be run in an existing pod to perform user-initiated actions such as debugging. This list cannot be specified when creating a pod, and it cannot be modified by updating the pod spec. In order to add an ephemeral container to an existing pod, use the pod's ephemeralcontainers subresource. This field is beta-level and available on clusters that haven't disabled the EphemeralContainers feature gate.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.EphemeralContainer\"), }, }, }, }, }, \"restartPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"Restart policy for all containers within the pod. One of Always, OnFailure, Never. Default to Always. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policynnPossible enum values:n - `\"Always\"`n - `\"Never\"`n - `\"OnFailure\"`\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"Always\", \"Never\", \"OnFailure\"}}, }, \"terminationGracePeriodSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Optional duration in seconds the pod needs to terminate gracefully. May be decreased in delete request. Value must be non-negative integer. The value zero indicates stop immediately via the kill signal (no opportunity to shut down). If this value is nil, the default grace period will be used instead. The grace period is the duration in seconds after the processes running in the pod are sent a termination signal and the time when the processes are forcibly halted with a kill signal. Set this value longer than the expected cleanup time for your process. Defaults to 30 seconds.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"activeDeadlineSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Optional duration in seconds the pod may be active on the node relative to StartTime before the system will actively try to mark it failed and kill associated containers. Value must be a positive integer.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"dnsPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"Set DNS policy for the pod. Defaults to \"ClusterFirst\". Valid values are 'ClusterFirstWithHostNet', 'ClusterFirst', 'Default' or 'None'. DNS parameters given in DNSConfig will be merged with the policy selected with DNSPolicy. To have DNS options set along with hostNetwork, you have to specify DNS policy explicitly to 'ClusterFirstWithHostNet'.nnPossible enum values:n - `\"ClusterFirst\"` indicates that the pod should use cluster DNS first unless hostNetwork is true, if it is available, then fall back on the default (as determined by kubelet) DNS settings.n - `\"ClusterFirstWithHostNet\"` indicates that the pod should use cluster DNS first, if it is available, then fall back on the default (as determined by kubelet) DNS settings.n - `\"Default\"` indicates that the pod should use the default (as determined by kubelet) DNS settings.n - `\"None\"` indicates that the pod should use empty DNS settings. DNS parameters such as nameservers and search paths should be defined via DNSConfig.\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"ClusterFirst\", \"ClusterFirstWithHostNet\", \"Default\", \"None\"}}, }, \"nodeSelector\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"NodeSelector is a selector which must be true for the pod to fit on a node. Selector which must match a node's labels for the pod to be scheduled on that node. More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"serviceAccountName\": { SchemaProps: spec.SchemaProps{ Description: \"ServiceAccountName is the name of the ServiceAccount to use to run this pod. More info: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"serviceAccount\": { SchemaProps: spec.SchemaProps{ Description: \"DeprecatedServiceAccount is a depreciated alias for ServiceAccountName. Deprecated: Use serviceAccountName instead.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"automountServiceAccountToken\": { SchemaProps: spec.SchemaProps{ Description: \"AutomountServiceAccountToken indicates whether a service account token should be automatically mounted.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"nodeName\": { SchemaProps: spec.SchemaProps{ Description: \"NodeName is a request to schedule this pod onto a specific node. If it is non-empty, the scheduler simply schedules this pod onto that node, assuming that it fits resource requirements.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"hostNetwork\": { SchemaProps: spec.SchemaProps{ Description: \"Host networking requested for this pod. Use the host's network namespace. If this option is set, the ports that will be used must be specified. Default to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"hostPID\": { SchemaProps: spec.SchemaProps{ Description: \"Use the host's pid namespace. Optional: Default to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"hostIPC\": { SchemaProps: spec.SchemaProps{ Description: \"Use the host's ipc namespace. Optional: Default to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"shareProcessNamespace\": { SchemaProps: spec.SchemaProps{ Description: \"Share a single process namespace between all of the containers in a pod. When this is set containers will be able to view and signal processes from other containers in the same pod, and the first process in each container will not be assigned PID 1. HostPID and ShareProcessNamespace cannot both be set. Optional: Default to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"securityContext\": { SchemaProps: spec.SchemaProps{ Description: \"SecurityContext holds pod-level security attributes and common container settings. Optional: Defaults to empty.  See type description for default values of each field.\", Ref:         ref(\"k8s.io/api/core/v1.PodSecurityContext\"), }, }, \"imagePullSecrets\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"name\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"ImagePullSecrets is an optional list of references to secrets in the same namespace to use for pulling any of the images used by this PodSpec. If specified, these secrets will be passed to individual puller implementations for them to use. For example, in the case of docker, only DockerConfig type secrets are honored. More info: https://kubernetes.io/docs/concepts/containers/images#specifying-imagepullsecrets-on-a-pod\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.LocalObjectReference\"), }, }, }, }, }, \"hostname\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies the hostname of the Pod If not specified, the pod's hostname will be set to a system-defined value.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"subdomain\": { SchemaProps: spec.SchemaProps{ Description: \"If specified, the fully qualified Pod hostname will be \"<hostname>.<subdomain>.<pod namespace>.svc.<cluster domain>\". If not specified, the pod will not have a domainname at all.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"affinity\": { SchemaProps: spec.SchemaProps{ Description: \"If specified, the pod's scheduling constraints\", Ref:         ref(\"k8s.io/api/core/v1.Affinity\"), }, }, \"schedulerName\": { SchemaProps: spec.SchemaProps{ Description: \"If specified, the pod will be dispatched by specified scheduler. If not specified, the pod will be dispatched by default scheduler.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"tolerations\": { SchemaProps: spec.SchemaProps{ Description: \"If specified, the pod's tolerations.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.Toleration\"), }, }, }, }, }, \"hostAliases\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"ip\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"HostAliases is an optional list of hosts and IPs that will be injected into the pod's hosts file if specified. This is only valid for non-hostNetwork pods.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.HostAlias\"), }, }, }, }, }, \"priorityClassName\": { SchemaProps: spec.SchemaProps{ Description: \"If specified, indicates the pod's priority. \"system-node-critical\" and \"system-cluster-critical\" are two special keywords which indicate the highest priorities with the former being the highest priority. Any other name must be defined by creating a PriorityClass object with that name. If not specified, the pod priority will be default or zero if there is no default.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"priority\": { SchemaProps: spec.SchemaProps{ Description: \"The priority value. Various system components use this field to find the priority of the pod. When Priority Admission Controller is enabled, it prevents users from setting this field. The admission controller populates this field from PriorityClassName. The higher the value, the higher the priority.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"dnsConfig\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy.\", Ref:         ref(\"k8s.io/api/core/v1.PodDNSConfig\"), }, }, \"readinessGates\": { SchemaProps: spec.SchemaProps{ Description: \"If specified, all readiness gates will be evaluated for pod readiness. A pod is ready when all its containers are ready AND all conditions specified in the readiness gates have status equal to \"True\" More info: https://git.k8s.io/enhancements/keps/sig-network/580-pod-readiness-gates\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.PodReadinessGate\"), }, }, }, }, }, \"runtimeClassName\": { SchemaProps: spec.SchemaProps{ Description: \"RuntimeClassName refers to a RuntimeClass object in the node.k8s.io group, which should be used to run this pod.  If no RuntimeClass resource matches the named class, the pod will not be run. If unset or empty, the \"legacy\" RuntimeClass will be used, which is an implicit class with an empty definition that uses the default runtime handler. More info: https://git.k8s.io/enhancements/keps/sig-node/585-runtime-class\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"enableServiceLinks\": { SchemaProps: spec.SchemaProps{ Description: \"EnableServiceLinks indicates whether information about services should be injected into pod's environment variables, matching the syntax of Docker links. Optional: Defaults to true.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"preemptionPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"PreemptionPolicy is the Policy for preempting pods with lower priority. One of Never, PreemptLowerPriority. Defaults to PreemptLowerPriority if unset.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"overhead\": { SchemaProps: spec.SchemaProps{ Description: \"Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. This field will be autopopulated at admission time by the RuntimeClass admission controller. If the RuntimeClass admission controller is enabled, overhead must not be set in Pod create requests. The RuntimeClass admission controller will reject Pod create requests which have the overhead already set. If RuntimeClass is configured and selected in the PodSpec, Overhead will be set to the value defined in the corresponding RuntimeClass, otherwise it will remain unset and treated as zero. More info: https://git.k8s.io/enhancements/keps/sig-node/688-pod-overhead/README.md This field is beta-level as of Kubernetes v1.18, and is only honored by servers that enable the PodOverhead feature.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, \"topologySpreadConstraints\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"topologyKey\", \"whenUnsatisfiable\", }, \"x-kubernetes-list-type\":       \"map\", \"x-kubernetes-patch-merge-key\": \"topologyKey\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"TopologySpreadConstraints describes how a group of pods ought to spread across topology domains. Scheduler will schedule pods in a way which abides by the constraints. All topologySpreadConstraints are ANDed.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.TopologySpreadConstraint\"), }, }, }, }, }, \"setHostnameAsFQDN\": { SchemaProps: spec.SchemaProps{ Description: \"If true the pod's hostname will be configured as the pod's FQDN, rather than the leaf name (the default). In Linux containers, this means setting the FQDN in the hostname field of the kernel (the nodename field of struct utsname). In Windows containers, this means setting the registry value of hostname for the registry key HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters to FQDN. If a pod does not have FQDN, this has no effect. Default to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"os\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies the OS of the containers in the pod. Some pod and container fields are restricted if this is set.nnIf the OS field is set to linux, the following fields must be unset: -securityContext.windowsOptionsnnIf the OS field is set to windows, following fields must be unset: - spec.hostPID - spec.hostIPC - spec.securityContext.seLinuxOptions - spec.securityContext.seccompProfile - spec.securityContext.fsGroup - spec.securityContext.fsGroupChangePolicy - spec.securityContext.sysctls - spec.shareProcessNamespace - spec.securityContext.runAsUser - spec.securityContext.runAsGroup - spec.securityContext.supplementalGroups - spec.containers[*].securityContext.seLinuxOptions - spec.containers[*].securityContext.seccompProfile - spec.containers[*].securityContext.capabilities - spec.containers[*].securityContext.readOnlyRootFilesystem - spec.containers[*].securityContext.privileged - spec.containers[*].securityContext.allowPrivilegeEscalation - spec.containers[*].securityContext.procMount - spec.containers[*].securityContext.runAsUser - spec.containers[*].securityContext.runAsGroup This is an alpha field and requires the IdentifyPodOS feature\", Ref:         ref(\"k8s.io/api/core/v1.PodOS\"), }, }, }, Required: []string{\"containers\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.Affinity\", \"k8s.io/api/core/v1.Container\", \"k8s.io/api/core/v1.EphemeralContainer\", \"k8s.io/api/core/v1.HostAlias\", \"k8s.io/api/core/v1.LocalObjectReference\", \"k8s.io/api/core/v1.PodDNSConfig\", \"k8s.io/api/core/v1.PodOS\", \"k8s.io/api/core/v1.PodReadinessGate\", \"k8s.io/api/core/v1.PodSecurityContext\", \"k8s.io/api/core/v1.Toleration\", \"k8s.io/api/core/v1.TopologySpreadConstraint\", \"k8s.io/api/core/v1.Volume\", \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_core_v1_PodStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodStatus represents information about the status of a pod. Status may trail the actual state of a system, especially if the node that hosts the pod cannot contact the control plane.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"phase\": { SchemaProps: spec.SchemaProps{ Description: \"The phase of a Pod is a simple, high-level summary of where the Pod is in its lifecycle. The conditions array, the reason and message fields, and the individual container status arrays contain more detail about the pod's status. There are five possible phase values:nnPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.nnMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phasennPossible enum values:n - `\"Failed\"` means that all containers in the pod have terminated, and at least one container has terminated in a failure (exited with a non-zero exit code or was stopped by the system).n - `\"Pending\"` means the pod has been accepted by the system, but one or more of the containers has not been started. This includes time before being bound to a node, as well as time spent pulling images onto the host.n - `\"Running\"` means the pod has been bound to a node and all of the containers have been started. At least one container is still running or is in the process of being restarted.n - `\"Succeeded\"` means that all containers in the pod have voluntarily terminated with a container exit code of 0, and the system is not going to restart any of these containers.n - `\"Unknown\"` means that for some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod. Deprecated: It isn't being set since 2015 (74da3b14b0c0f658b3bb8d2def5094686d0e9095)\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"Failed\", \"Pending\", \"Running\", \"Succeeded\", \"Unknown\"}}, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Current service state of pod. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-conditions\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.PodCondition\"), }, }, }, }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"A human readable message indicating details about why the pod is in this condition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"A brief CamelCase message indicating details about why the pod is in this state. e.g. 'Evicted'\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"nominatedNodeName\": { SchemaProps: spec.SchemaProps{ Description: \"nominatedNodeName is set only when this pod preempts other pods on the node, but it cannot be scheduled right away as preemption victims receive their graceful termination periods. This field does not guarantee that the pod will be scheduled on this node. Scheduler may decide to place the pod elsewhere if other nodes become available sooner. Scheduler may also decide to give the resources on this node to a higher priority pod that is created after preemption. As a result, this field may be different than PodSpec.nodeName when the pod is scheduled.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"hostIP\": { SchemaProps: spec.SchemaProps{ Description: \"IP address of the host to which the pod is assigned. Empty if not yet scheduled.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"podIP\": { SchemaProps: spec.SchemaProps{ Description: \"IP address allocated to the pod. Routable at least within the cluster. Empty if not yet allocated.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"podIPs\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"ip\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"podIPs holds the IP addresses allocated to the pod. If this field is specified, the 0th entry must match the podIP field. Pods may be allocated at most 1 value for each of IPv4 and IPv6. This list is empty if no IPs have been allocated yet.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.PodIP\"), }, }, }, }, }, \"startTime\": { SchemaProps: spec.SchemaProps{ Description: \"RFC 3339 date and time at which the object was acknowledged by the Kubelet. This is before the Kubelet pulled the container image(s) for the pod.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"initContainerStatuses\": { SchemaProps: spec.SchemaProps{ Description: \"The list has one entry per init container in the manifest. The most recent successful init container will have ready = true, the most recently started container will have startTime set. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-and-container-status\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.ContainerStatus\"), }, }, }, }, }, \"containerStatuses\": { SchemaProps: spec.SchemaProps{ Description: \"The list has one entry per container in the manifest. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-and-container-status\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.ContainerStatus\"), }, }, }, }, }, \"qosClass\": { SchemaProps: spec.SchemaProps{ Description: \"The Quality of Service (QOS) classification assigned to the pod based on resource requirements See PodQOSClass type for available QOS classes More info: https://git.k8s.io/community/contributors/design-proposals/node/resource-qos.mdnnPossible enum values:n - `\"BestEffort\"` is the BestEffort qos class.n - `\"Burstable\"` is the Burstable qos class.n - `\"Guaranteed\"` is the Guaranteed qos class.\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"BestEffort\", \"Burstable\", \"Guaranteed\"}}, }, \"ephemeralContainerStatuses\": { SchemaProps: spec.SchemaProps{ Description: \"Status for any ephemeral containers that have run in this pod. This field is beta-level and available on clusters that haven't disabled the EphemeralContainers feature gate.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.ContainerStatus\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ContainerStatus\", \"k8s.io/api/core/v1.PodCondition\", \"k8s.io/api/core/v1.PodIP\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_core_v1_PodStatusResult(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodStatusResult is a wrapper for PodStatus returned by kubelet that can be encode/decoded\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Most recently observed status of the pod. This data may not be up to date. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PodStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_PodTemplate(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodTemplate describes a template for creating copies of a predefined pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"template\": { SchemaProps: spec.SchemaProps{ Description: \"Template defines the pods that will be created from this pod template. https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodTemplateSpec\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PodTemplateSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_PodTemplateList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodTemplateList is a list of PodTemplates.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of pod templates\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.PodTemplate\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PodTemplate\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_core_v1_PodTemplateSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodTemplateSpec describes the data a pod should have when created from a template\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the desired behavior of the pod. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodSpec\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PodSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_PortStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, Properties: map[string]spec.Schema{ \"port\": { SchemaProps: spec.SchemaProps{ Description: \"Port is the port number of the service port of which status is recorded here\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"protocol\": { SchemaProps: spec.SchemaProps{ Description: \"Protocol is the protocol of the service port of which status is recorded here The supported values are: \"TCP\", \"UDP\", \"SCTP\"nnPossible enum values:n - `\"SCTP\"` is the SCTP protocol.n - `\"TCP\"` is the TCP protocol.n - `\"UDP\"` is the UDP protocol.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"SCTP\", \"TCP\", \"UDP\"}}, }, \"error\": { SchemaProps: spec.SchemaProps{ Description: \"Error is to record the problem with the service port The format of the error shall comply with the following rules: - built-in error values shall be specified in this file and those shall usen  CamelCase namesn- cloud provider specific error values must have names that comply with then  format foo.example.com/CamelCase.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"port\", \"protocol\"}, }, }, } } func schema_k8sio_api_core_v1_PortworxVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PortworxVolumeSource represents a Portworx volume resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"volumeID\": { SchemaProps: spec.SchemaProps{ Description: \"volumeID uniquely identifies a Portworx volume\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fSType represents the filesystem type to mount Must be a filesystem type supported by the host operating system. Ex. \"ext4\", \"xfs\". Implicitly inferred to be \"ext4\" if unspecified.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"volumeID\"}, }, }, } } func schema_k8sio_api_core_v1_PreferAvoidPodsEntry(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Describes a class of pods that should avoid this node.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"podSignature\": { SchemaProps: spec.SchemaProps{ Description: \"The class of pods.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodSignature\"), }, }, \"evictionTime\": { SchemaProps: spec.SchemaProps{ Description: \"Time at which this entry was added to the list.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"(brief) reason why this entry was added to the list.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"Human readable message indicating why this entry was added to the list.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"podSignature\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PodSignature\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_core_v1_PreferredSchedulingTerm(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"An empty preferred scheduling term matches all objects with implicit weight 0 (i.e. it's a no-op). A null preferred scheduling term matches no objects (i.e. is also a no-op).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"weight\": { SchemaProps: spec.SchemaProps{ Description: \"Weight associated with matching the corresponding nodeSelectorTerm, in the range 1-100.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"preference\": { SchemaProps: spec.SchemaProps{ Description: \"A node selector term, associated with the corresponding weight.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.NodeSelectorTerm\"), }, }, }, Required: []string{\"weight\", \"preference\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.NodeSelectorTerm\"}, } } func schema_k8sio_api_core_v1_Probe(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Probe describes a health check to be performed against a container to determine whether it is alive or ready to receive traffic.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"exec\": { SchemaProps: spec.SchemaProps{ Description: \"Exec specifies the action to take.\", Ref:         ref(\"k8s.io/api/core/v1.ExecAction\"), }, }, \"httpGet\": { SchemaProps: spec.SchemaProps{ Description: \"HTTPGet specifies the http request to perform.\", Ref:         ref(\"k8s.io/api/core/v1.HTTPGetAction\"), }, }, \"tcpSocket\": { SchemaProps: spec.SchemaProps{ Description: \"TCPSocket specifies an action involving a TCP port.\", Ref:         ref(\"k8s.io/api/core/v1.TCPSocketAction\"), }, }, \"grpc\": { SchemaProps: spec.SchemaProps{ Description: \"GRPC specifies an action involving a GRPC port. This is an alpha field and requires enabling GRPCContainerProbe feature gate.\", Ref:         ref(\"k8s.io/api/core/v1.GRPCAction\"), }, }, \"initialDelaySeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Number of seconds after the container has started before liveness probes are initiated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"timeoutSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Number of seconds after which the probe times out. Defaults to 1 second. Minimum value is 1. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"periodSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"How often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"successThreshold\": { SchemaProps: spec.SchemaProps{ Description: \"Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"failureThreshold\": { SchemaProps: spec.SchemaProps{ Description: \"Minimum consecutive failures for the probe to be considered failed after having succeeded. Defaults to 3. Minimum value is 1.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"terminationGracePeriodSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Optional duration in seconds the pod needs to terminate gracefully upon probe failure. The grace period is the duration in seconds after the processes running in the pod are sent a termination signal and the time when the processes are forcibly halted with a kill signal. Set this value longer than the expected cleanup time for your process. If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this value overrides the value provided by the pod spec. Value must be non-negative integer. The value zero indicates stop immediately via the kill signal (no opportunity to shut down). This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ExecAction\", \"k8s.io/api/core/v1.GRPCAction\", \"k8s.io/api/core/v1.HTTPGetAction\", \"k8s.io/api/core/v1.TCPSocketAction\"}, } } func schema_k8sio_api_core_v1_ProbeHandler(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ProbeHandler defines a specific action that should be taken in a probe. One and only one of the fields must be specified.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"exec\": { SchemaProps: spec.SchemaProps{ Description: \"Exec specifies the action to take.\", Ref:         ref(\"k8s.io/api/core/v1.ExecAction\"), }, }, \"httpGet\": { SchemaProps: spec.SchemaProps{ Description: \"HTTPGet specifies the http request to perform.\", Ref:         ref(\"k8s.io/api/core/v1.HTTPGetAction\"), }, }, \"tcpSocket\": { SchemaProps: spec.SchemaProps{ Description: \"TCPSocket specifies an action involving a TCP port.\", Ref:         ref(\"k8s.io/api/core/v1.TCPSocketAction\"), }, }, \"grpc\": { SchemaProps: spec.SchemaProps{ Description: \"GRPC specifies an action involving a GRPC port. This is an alpha field and requires enabling GRPCContainerProbe feature gate.\", Ref:         ref(\"k8s.io/api/core/v1.GRPCAction\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ExecAction\", \"k8s.io/api/core/v1.GRPCAction\", \"k8s.io/api/core/v1.HTTPGetAction\", \"k8s.io/api/core/v1.TCPSocketAction\"}, } } func schema_k8sio_api_core_v1_ProjectedVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a projected volume source\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"sources\": { SchemaProps: spec.SchemaProps{ Description: \"sources is the list of volume projections\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.VolumeProjection\"), }, }, }, }, }, \"defaultMode\": { SchemaProps: spec.SchemaProps{ Description: \"defaultMode are the mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.VolumeProjection\"}, } } func schema_k8sio_api_core_v1_QuobyteVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a Quobyte mount that lasts the lifetime of a pod. Quobyte volumes do not support ownership management or SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"registry\": { SchemaProps: spec.SchemaProps{ Description: \"registry represents a single or multiple Quobyte Registry services specified as a string as host:port pair (multiple entries are separated with commas) which acts as the central registry for volumes\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"volume\": { SchemaProps: spec.SchemaProps{ Description: \"volume is a string that references an already created Quobyte volume by name.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly here will force the Quobyte volume to be mounted with read-only permissions. Defaults to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"user\": { SchemaProps: spec.SchemaProps{ Description: \"user to map volume access to Defaults to serivceaccount user\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"group\": { SchemaProps: spec.SchemaProps{ Description: \"group to map volume access to Default is no group\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"tenant\": { SchemaProps: spec.SchemaProps{ Description: \"tenant owning the given Quobyte volume in the Backend Used with dynamically provisioned Quobyte volumes, value is set by the plugin\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"registry\", \"volume\"}, }, }, } } func schema_k8sio_api_core_v1_RBDPersistentVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a Rados Block Device mount that lasts the lifetime of a pod. RBD volumes support ownership management and SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"monitors\": { SchemaProps: spec.SchemaProps{ Description: \"monitors is a collection of Ceph monitors. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"image\": { SchemaProps: spec.SchemaProps{ Description: \"image is the rados image name. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType is the filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#rbd\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"pool\": { SchemaProps: spec.SchemaProps{ Description: \"pool is the rados pool name. Default is rbd. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"user\": { SchemaProps: spec.SchemaProps{ Description: \"user is the rados user name. Default is admin. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"keyring\": { SchemaProps: spec.SchemaProps{ Description: \"keyring is the path to key ring for RBDUser. Default is /etc/ceph/keyring. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"secretRef\": { SchemaProps: spec.SchemaProps{ Description: \"secretRef is name of the authentication secret for RBDUser. If provided overrides keyring. Default is nil. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it\", Ref:         ref(\"k8s.io/api/core/v1.SecretReference\"), }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"monitors\", \"image\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.SecretReference\"}, } } func schema_k8sio_api_core_v1_RBDVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a Rados Block Device mount that lasts the lifetime of a pod. RBD volumes support ownership management and SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"monitors\": { SchemaProps: spec.SchemaProps{ Description: \"monitors is a collection of Ceph monitors. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"image\": { SchemaProps: spec.SchemaProps{ Description: \"image is the rados image name. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType is the filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#rbd\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"pool\": { SchemaProps: spec.SchemaProps{ Description: \"pool is the rados pool name. Default is rbd. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"user\": { SchemaProps: spec.SchemaProps{ Description: \"user is the rados user name. Default is admin. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"keyring\": { SchemaProps: spec.SchemaProps{ Description: \"keyring is the path to key ring for RBDUser. Default is /etc/ceph/keyring. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"secretRef\": { SchemaProps: spec.SchemaProps{ Description: \"secretRef is name of the authentication secret for RBDUser. If provided overrides keyring. Default is nil. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it\", Ref:         ref(\"k8s.io/api/core/v1.LocalObjectReference\"), }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"monitors\", \"image\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.LocalObjectReference\"}, } } func schema_k8sio_api_core_v1_RangeAllocation(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RangeAllocation is not a public type.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"range\": { SchemaProps: spec.SchemaProps{ Description: \"Range is string that identifies the range represented by 'data'.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"data\": { SchemaProps: spec.SchemaProps{ Description: \"Data is a bit array containing all allocated addresses in the previous segment.\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, }, Required: []string{\"range\", \"data\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_ReplicationController(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicationController represents the configuration of a replication controller.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"If the Labels of a ReplicationController are empty, they are defaulted to be the same as the Pod(s) that the replication controller manages. Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec defines the specification of the desired behavior of the replication controller. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.ReplicationControllerSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is the most recently observed status of the replication controller. This data may be out of date by some window of time. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.ReplicationControllerStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ReplicationControllerSpec\", \"k8s.io/api/core/v1.ReplicationControllerStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_ReplicationControllerCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicationControllerCondition describes the state of a replication controller at a certain point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of replication controller condition.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"The last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"The reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"A human readable message indicating details about the transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_core_v1_ReplicationControllerList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicationControllerList is a collection of replication controllers.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of replication controllers. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.ReplicationController\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ReplicationController\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_core_v1_ReplicationControllerSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicationControllerSpec is the specification of a replication controller.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"Replicas is the number of desired replicas. This is a pointer to distinguish between explicit zero and unspecified. Defaults to 1. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#what-is-a-replicationcontroller\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"minReadySeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"selector\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Selector is a label query over pods that should match the Replicas count. If Selector is empty, it is defaulted to the labels present on the Pod template. Label keys and values that must match in order to be controlled by this replication controller, if empty defaulted to labels on Pod template. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"template\": { SchemaProps: spec.SchemaProps{ Description: \"Template is the object that describes the pod that will be created if insufficient replicas are detected. This takes precedence over a TemplateRef. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template\", Ref:         ref(\"k8s.io/api/core/v1.PodTemplateSpec\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PodTemplateSpec\"}, } } func schema_k8sio_api_core_v1_ReplicationControllerStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicationControllerStatus represents the current status of a replication controller.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"Replicas is the most recently oberved number of replicas. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#what-is-a-replicationcontroller\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"fullyLabeledReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"The number of pods that have labels matching the labels of the pod template of the replication controller.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"readyReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"The number of ready replicas for this replication controller.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"availableReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"The number of available replicas (ready for at least minReadySeconds) for this replication controller.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"ObservedGeneration reflects the generation of the most recently observed replication controller.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Represents the latest available observations of a replication controller's current state.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.ReplicationControllerCondition\"), }, }, }, }, }, }, Required: []string{\"replicas\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ReplicationControllerCondition\"}, } } func schema_k8sio_api_core_v1_ResourceFieldSelector(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceFieldSelector represents container resources (cpu, memory) and their output format\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"containerName\": { SchemaProps: spec.SchemaProps{ Description: \"Container name: required for volumes, optional for env vars\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resource\": { SchemaProps: spec.SchemaProps{ Description: \"Required: resource to select\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"divisor\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies the output format of the exposed resources, defaults to \"1\"\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, Required: []string{\"resource\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_core_v1_ResourceQuota(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceQuota sets aggregate quota restrictions enforced per namespace\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec defines the desired quota. https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.ResourceQuotaSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status defines the actual enforced quota and its current usage. https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.ResourceQuotaStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ResourceQuotaSpec\", \"k8s.io/api/core/v1.ResourceQuotaStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_ResourceQuotaList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceQuotaList is a list of ResourceQuota items.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of ResourceQuota objects. More info: https://kubernetes.io/docs/concepts/policy/resource-quotas/\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.ResourceQuota\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ResourceQuota\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_core_v1_ResourceQuotaSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceQuotaSpec defines the desired hard limits to enforce for Quota.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"hard\": { SchemaProps: spec.SchemaProps{ Description: \"hard is the set of desired hard limits for each named resource. More info: https://kubernetes.io/docs/concepts/policy/resource-quotas/\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, \"scopes\": { SchemaProps: spec.SchemaProps{ Description: \"A collection of filters that must match each object tracked by a quota. If not specified, the quota matches all objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"scopeSelector\": { SchemaProps: spec.SchemaProps{ Description: \"scopeSelector is also a collection of filters like scopes that must match each object tracked by a quota but expressed using ScopeSelectorOperator in combination with possible values. For a resource to match, both scopes AND scopeSelector (if specified in spec), must be matched.\", Ref:         ref(\"k8s.io/api/core/v1.ScopeSelector\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ScopeSelector\", \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_core_v1_ResourceQuotaStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceQuotaStatus defines the enforced hard limits and observed use.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"hard\": { SchemaProps: spec.SchemaProps{ Description: \"Hard is the set of enforced hard limits for each named resource. More info: https://kubernetes.io/docs/concepts/policy/resource-quotas/\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, \"used\": { SchemaProps: spec.SchemaProps{ Description: \"Used is the current observed total usage of the resource in the namespace.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_core_v1_ResourceRequirements(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceRequirements describes the compute resource requirements.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"limits\": { SchemaProps: spec.SchemaProps{ Description: \"Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, \"requests\": { SchemaProps: spec.SchemaProps{ Description: \"Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_core_v1_SELinuxOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SELinuxOptions are the labels to be applied to the container\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"user\": { SchemaProps: spec.SchemaProps{ Description: \"User is a SELinux user label that applies to the container.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"role\": { SchemaProps: spec.SchemaProps{ Description: \"Role is a SELinux role label that applies to the container.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type is a SELinux type label that applies to the container.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"level\": { SchemaProps: spec.SchemaProps{ Description: \"Level is SELinux level label that applies to the container.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_core_v1_ScaleIOPersistentVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ScaleIOPersistentVolumeSource represents a persistent ScaleIO volume\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"gateway\": { SchemaProps: spec.SchemaProps{ Description: \"gateway is the host address of the ScaleIO API Gateway.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"system\": { SchemaProps: spec.SchemaProps{ Description: \"system is the name of the storage system as configured in ScaleIO.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"secretRef\": { SchemaProps: spec.SchemaProps{ Description: \"secretRef references to the secret for ScaleIO user and other sensitive information. If this is not provided, Login operation will fail.\", Ref:         ref(\"k8s.io/api/core/v1.SecretReference\"), }, }, \"sslEnabled\": { SchemaProps: spec.SchemaProps{ Description: \"sslEnabled is the flag to enable/disable SSL communication with Gateway, default false\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"protectionDomain\": { SchemaProps: spec.SchemaProps{ Description: \"protectionDomain is the name of the ScaleIO Protection Domain for the configured storage.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"storagePool\": { SchemaProps: spec.SchemaProps{ Description: \"storagePool is the ScaleIO Storage Pool associated with the protection domain.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"storageMode\": { SchemaProps: spec.SchemaProps{ Description: \"storageMode indicates whether the storage for a volume should be ThickProvisioned or ThinProvisioned. Default is ThinProvisioned.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"volumeName\": { SchemaProps: spec.SchemaProps{ Description: \"volumeName is the name of a volume already created in the ScaleIO system that is associated with this volume source.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. \"ext4\", \"xfs\", \"ntfs\". Default is \"xfs\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"gateway\", \"system\", \"secretRef\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.SecretReference\"}, } } func schema_k8sio_api_core_v1_ScaleIOVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ScaleIOVolumeSource represents a persistent ScaleIO volume\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"gateway\": { SchemaProps: spec.SchemaProps{ Description: \"gateway is the host address of the ScaleIO API Gateway.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"system\": { SchemaProps: spec.SchemaProps{ Description: \"system is the name of the storage system as configured in ScaleIO.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"secretRef\": { SchemaProps: spec.SchemaProps{ Description: \"secretRef references to the secret for ScaleIO user and other sensitive information. If this is not provided, Login operation will fail.\", Ref:         ref(\"k8s.io/api/core/v1.LocalObjectReference\"), }, }, \"sslEnabled\": { SchemaProps: spec.SchemaProps{ Description: \"sslEnabled Flag enable/disable SSL communication with Gateway, default false\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"protectionDomain\": { SchemaProps: spec.SchemaProps{ Description: \"protectionDomain is the name of the ScaleIO Protection Domain for the configured storage.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"storagePool\": { SchemaProps: spec.SchemaProps{ Description: \"storagePool is the ScaleIO Storage Pool associated with the protection domain.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"storageMode\": { SchemaProps: spec.SchemaProps{ Description: \"storageMode indicates whether the storage for a volume should be ThickProvisioned or ThinProvisioned. Default is ThinProvisioned.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"volumeName\": { SchemaProps: spec.SchemaProps{ Description: \"volumeName is the name of a volume already created in the ScaleIO system that is associated with this volume source.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. \"ext4\", \"xfs\", \"ntfs\". Default is \"xfs\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"gateway\", \"system\", \"secretRef\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.LocalObjectReference\"}, } } func schema_k8sio_api_core_v1_ScopeSelector(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"A scope selector represents the AND of the selectors represented by the scoped-resource selector requirements.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"matchExpressions\": { SchemaProps: spec.SchemaProps{ Description: \"A list of scope selector requirements by scope of the resources.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.ScopedResourceSelectorRequirement\"), }, }, }, }, }, }, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ScopedResourceSelectorRequirement\"}, } } func schema_k8sio_api_core_v1_ScopedResourceSelectorRequirement(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"A scoped-resource selector requirement is a selector that contains values, a scope name, and an operator that relates the scope name and values.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"scopeName\": { SchemaProps: spec.SchemaProps{ Description: \"The name of the scope that the selector applies to.nnPossible enum values:n - `\"BestEffort\"` Match all pod objects that have best effort quality of servicen - `\"CrossNamespacePodAffinity\"` Match all pod objects that have cross-namespace pod (anti)affinity mentioned.n - `\"NotBestEffort\"` Match all pod objects that do not have best effort quality of servicen - `\"NotTerminating\"` Match all pod objects where spec.activeDeadlineSeconds is niln - `\"PriorityClass\"` Match all pod objects that have priority class mentionedn - `\"Terminating\"` Match all pod objects where spec.activeDeadlineSeconds >=0\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"BestEffort\", \"CrossNamespacePodAffinity\", \"NotBestEffort\", \"NotTerminating\", \"PriorityClass\", \"Terminating\"}}, }, \"operator\": { SchemaProps: spec.SchemaProps{ Description: \"Represents a scope's relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist.nnPossible enum values:n - `\"DoesNotExist\"`n - `\"Exists\"`n - `\"In\"`n - `\"NotIn\"`\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"DoesNotExist\", \"Exists\", \"In\", \"NotIn\"}}, }, \"values\": { SchemaProps: spec.SchemaProps{ Description: \"An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"scopeName\", \"operator\"}, }, }, } } func schema_k8sio_api_core_v1_SeccompProfile(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SeccompProfile defines a pod/container's seccomp profile settings. Only one profile source may be set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type indicates which kind of seccomp profile will be applied. Valid options are:nnLocalhost - a profile defined in a file on the node should be used. RuntimeDefault - the container runtime default profile should be used. Unconfined - no profile should be applied.nnPossible enum values:n - `\"Localhost\"` indicates a profile defined in a file on the node should be used. The file's location relative to <kubelet-root-dir>/seccomp.n - `\"RuntimeDefault\"` represents the default container runtime seccomp profile.n - `\"Unconfined\"` indicates no seccomp profile is applied (A.K.A. unconfined).\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"Localhost\", \"RuntimeDefault\", \"Unconfined\"}}, }, \"localhostProfile\": { SchemaProps: spec.SchemaProps{ Description: \"localhostProfile indicates a profile defined in a file on the node should be used. The profile must be preconfigured on the node to work. Must be a descending path, relative to the kubelet's configured seccomp profile location. Must only be set if type is \"Localhost\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-unions\": []interface{}{ map[string]interface{}{ \"discriminator\": \"type\", \"fields-to-discriminateBy\": map[string]interface{}{ \"localhostProfile\": \"LocalhostProfile\", }, }, }, }, }, }, } } func schema_k8sio_api_core_v1_Secret(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Secret holds secret data of a certain type. The total bytes of the values in the Data field must be less than MaxSecretSize bytes.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"immutable\": { SchemaProps: spec.SchemaProps{ Description: \"Immutable, if set to true, ensures that data stored in the Secret cannot be updated (only object metadata can be modified). If not set to true, the field can be modified at any time. Defaulted to nil.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"data\": { SchemaProps: spec.SchemaProps{ Description: \"Data contains the secret data. Each key must consist of alphanumeric characters, '-', '_' or '.'. The serialized form of the secret data is a base64 encoded string, representing the arbitrary (possibly non-string) data value here. Described in https://tools.ietf.org/html/rfc4648#section-4\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"byte\", }, }, }, }, }, \"stringData\": { SchemaProps: spec.SchemaProps{ Description: \"stringData allows specifying non-binary secret data in string form. It is provided as a write-only input field for convenience. All keys and values are merged into the data field on write, overwriting any existing values. The stringData field is never output when reading from the API.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Used to facilitate programmatic handling of secret data. More info: https://kubernetes.io/docs/concepts/configuration/secret/#secret-types\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_SecretEnvSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SecretEnvSource selects a Secret to populate the environment variables with.nnThe contents of the target Secret's Data field will represent the key-value pairs as environment variables.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"optional\": { SchemaProps: spec.SchemaProps{ Description: \"Specify whether the Secret must be defined\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_core_v1_SecretKeySelector(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SecretKeySelector selects a key of a Secret.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"key\": { SchemaProps: spec.SchemaProps{ Description: \"The key of the secret to select from.  Must be a valid secret key.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"optional\": { SchemaProps: spec.SchemaProps{ Description: \"Specify whether the Secret or its key must be defined\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"key\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, } } func schema_k8sio_api_core_v1_SecretList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SecretList is a list of Secret.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of secret objects. More info: https://kubernetes.io/docs/concepts/configuration/secret\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.Secret\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.Secret\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_core_v1_SecretProjection(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Adapts a secret into a projected volume.nnThe contents of the target Secret's Data field will be presented in a projected volume as files using the keys in the Data field as the file names. Note that this is identical to a secret volume source without the default mode.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items if unspecified, each key-value pair in the Data field of the referenced Secret will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the Secret, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.KeyToPath\"), }, }, }, }, }, \"optional\": { SchemaProps: spec.SchemaProps{ Description: \"optional field specify whether the Secret or its key must be defined\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.KeyToPath\"}, } } func schema_k8sio_api_core_v1_SecretReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SecretReference represents a Secret Reference. It has enough information to retrieve secret in any namespace\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is unique within a namespace to reference a secret resource.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"namespace defines the space within which the secret name must be unique.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, } } func schema_k8sio_api_core_v1_SecretVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Adapts a Secret into a volume.nnThe contents of the target Secret's Data field will be presented in a volume as files using the keys in the Data field as the file names. Secret volumes support ownership management and SELinux relabeling.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"secretName\": { SchemaProps: spec.SchemaProps{ Description: \"secretName is the name of the secret in the pod's namespace to use. More info: https://kubernetes.io/docs/concepts/storage/volumes#secret\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items If unspecified, each key-value pair in the Data field of the referenced Secret will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the Secret, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.KeyToPath\"), }, }, }, }, }, \"defaultMode\": { SchemaProps: spec.SchemaProps{ Description: \"defaultMode is Optional: mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"optional\": { SchemaProps: spec.SchemaProps{ Description: \"optional field specify whether the Secret or its keys must be defined\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.KeyToPath\"}, } } func schema_k8sio_api_core_v1_SecurityContext(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SecurityContext holds security configuration that will be applied to a container. Some fields are present in both SecurityContext and PodSecurityContext.  When both are set, the values in SecurityContext take precedence.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"capabilities\": { SchemaProps: spec.SchemaProps{ Description: \"The capabilities to add/drop when running containers. Defaults to the default set of capabilities granted by the container runtime. Note that this field cannot be set when spec.os.name is windows.\", Ref:         ref(\"k8s.io/api/core/v1.Capabilities\"), }, }, \"privileged\": { SchemaProps: spec.SchemaProps{ Description: \"Run container in privileged mode. Processes in privileged containers are essentially equivalent to root on the host. Defaults to false. Note that this field cannot be set when spec.os.name is windows.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"seLinuxOptions\": { SchemaProps: spec.SchemaProps{ Description: \"The SELinux context to be applied to the container. If unspecified, the container runtime will allocate a random SELinux context for each container.  May also be set in PodSecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is windows.\", Ref:         ref(\"k8s.io/api/core/v1.SELinuxOptions\"), }, }, \"windowsOptions\": { SchemaProps: spec.SchemaProps{ Description: \"The Windows specific settings applied to all containers. If unspecified, the options from the PodSecurityContext will be used. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is linux.\", Ref:         ref(\"k8s.io/api/core/v1.WindowsSecurityContextOptions\"), }, }, \"runAsUser\": { SchemaProps: spec.SchemaProps{ Description: \"The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified. May also be set in PodSecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is windows.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"runAsGroup\": { SchemaProps: spec.SchemaProps{ Description: \"The GID to run the entrypoint of the container process. Uses runtime default if unset. May also be set in PodSecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is windows.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"runAsNonRoot\": { SchemaProps: spec.SchemaProps{ Description: \"Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed. May also be set in PodSecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"readOnlyRootFilesystem\": { SchemaProps: spec.SchemaProps{ Description: \"Whether this container has a read-only root filesystem. Default is false. Note that this field cannot be set when spec.os.name is windows.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"allowPrivilegeEscalation\": { SchemaProps: spec.SchemaProps{ Description: \"AllowPrivilegeEscalation controls whether a process can gain more privileges than its parent process. This bool directly controls if the no_new_privs flag will be set on the container process. AllowPrivilegeEscalation is true always when the container is: 1) run as Privileged 2) has CAP_SYS_ADMIN Note that this field cannot be set when spec.os.name is windows.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"procMount\": { SchemaProps: spec.SchemaProps{ Description: \"procMount denotes the type of proc mount to use for the containers. The default is DefaultProcMount which uses the container runtime defaults for readonly paths and masked paths. This requires the ProcMountType feature flag to be enabled. Note that this field cannot be set when spec.os.name is windows.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"seccompProfile\": { SchemaProps: spec.SchemaProps{ Description: \"The seccomp options to use by this container. If seccomp options are provided at both the pod & container level, the container options override the pod options. Note that this field cannot be set when spec.os.name is windows.\", Ref:         ref(\"k8s.io/api/core/v1.SeccompProfile\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.Capabilities\", \"k8s.io/api/core/v1.SELinuxOptions\", \"k8s.io/api/core/v1.SeccompProfile\", \"k8s.io/api/core/v1.WindowsSecurityContextOptions\"}, } } func schema_k8sio_api_core_v1_SerializedReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SerializedReference is a reference to serialized object.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"reference\": { SchemaProps: spec.SchemaProps{ Description: \"The reference to an object in the system.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.ObjectReference\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ObjectReference\"}, } } func schema_k8sio_api_core_v1_Service(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Service is a named abstraction of software service (for example, mysql) consisting of local port (for example 3306) that the proxy listens on, and the selector that determines which pods will answer requests sent through the proxy.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec defines the behavior of a service. https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.ServiceSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Most recently observed status of the service. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.ServiceStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ServiceSpec\", \"k8s.io/api/core/v1.ServiceStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_ServiceAccount(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ServiceAccount binds together: * a name, understood by users, and perhaps by peripheral systems, for an identity * a principal that can be authenticated and authorized * a set of secrets\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"secrets\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"name\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Secrets is a list of the secrets in the same namespace that pods running using this ServiceAccount are allowed to use. Pods are only limited to this list if this service account has a \"kubernetes.io/enforce-mountable-secrets\" annotation set to \"true\". This field should not be used to find auto-generated service account token secrets for use outside of pods. Instead, tokens can be requested directly using the TokenRequest API, or service account token secrets can be manually created. More info: https://kubernetes.io/docs/concepts/configuration/secret\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.ObjectReference\"), }, }, }, }, }, \"imagePullSecrets\": { SchemaProps: spec.SchemaProps{ Description: \"ImagePullSecrets is a list of references to secrets in the same namespace to use for pulling any images in pods that reference this ServiceAccount. ImagePullSecrets are distinct from Secrets because Secrets can be mounted in the pod, but ImagePullSecrets are only accessed by the kubelet. More info: https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.LocalObjectReference\"), }, }, }, }, }, \"automountServiceAccountToken\": { SchemaProps: spec.SchemaProps{ Description: \"AutomountServiceAccountToken indicates whether pods running as this service account should have an API token automatically mounted. Can be overridden at the pod level.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.LocalObjectReference\", \"k8s.io/api/core/v1.ObjectReference\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_core_v1_ServiceAccountList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ServiceAccountList is a list of ServiceAccount objects\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of ServiceAccounts. More info: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.ServiceAccount\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ServiceAccount\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_core_v1_ServiceAccountTokenProjection(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ServiceAccountTokenProjection represents a projected service account token volume. This projection can be used to insert a service account token into the pods runtime filesystem for use against APIs (Kubernetes API Server or otherwise).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"audience\": { SchemaProps: spec.SchemaProps{ Description: \"audience is the intended audience of the token. A recipient of a token must identify itself with an identifier specified in the audience of the token, and otherwise should reject the token. The audience defaults to the identifier of the apiserver.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"expirationSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"expirationSeconds is the requested duration of validity of the service account token. As the token approaches expiration, the kubelet volume plugin will proactively rotate the service account token. The kubelet will start trying to rotate the token if the token is older than 80 percent of its time to live or if the token is older than 24 hours.Defaults to 1 hour and must be at least 10 minutes.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"path\": { SchemaProps: spec.SchemaProps{ Description: \"path is the path relative to the mount point of the file to project the token into.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"path\"}, }, }, } } func schema_k8sio_api_core_v1_ServiceList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ServiceList holds a list of services.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of services\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.Service\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.Service\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_core_v1_ServicePort(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ServicePort contains information on service's port.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"The name of this port within the service. This must be a DNS_LABEL. All ports within a ServiceSpec must have unique names. When considering the endpoints for a Service, this must match the 'name' field in the EndpointPort. Optional if only one ServicePort is defined on this service.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"protocol\": { SchemaProps: spec.SchemaProps{ Description: \"The IP protocol for this port. Supports \"TCP\", \"UDP\", and \"SCTP\". Default is TCP.nnPossible enum values:n - `\"SCTP\"` is the SCTP protocol.n - `\"TCP\"` is the TCP protocol.n - `\"UDP\"` is the UDP protocol.\", Default:     \"TCP\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"SCTP\", \"TCP\", \"UDP\"}}, }, \"appProtocol\": { SchemaProps: spec.SchemaProps{ Description: \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"port\": { SchemaProps: spec.SchemaProps{ Description: \"The port that will be exposed by this service.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"targetPort\": { SchemaProps: spec.SchemaProps{ Description: \"Number or name of the port to access on the pods targeted by the service. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME. If this is a string, it will be looked up as a named port in the target Pod's container ports. If this is not specified, the value of the 'port' field is used (an identity map). This field is ignored for services with clusterIP=None, and should be omitted or set equal to the 'port' field. More info: https://kubernetes.io/docs/concepts/services-networking/service/#defining-a-service\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, \"nodePort\": { SchemaProps: spec.SchemaProps{ Description: \"The port on each node on which this service is exposed when type is NodePort or LoadBalancer.  Usually assigned by the system. If a value is specified, in-range, and not in use it will be used, otherwise the operation will fail.  If not specified, a port will be allocated if this Service requires one.  If this field is specified when creating a Service which does not need it, creation will fail. This field will be wiped when updating a Service to no longer need it (e.g. changing type from NodePort to ClusterIP). More info: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"port\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"}, } } func schema_k8sio_api_core_v1_ServiceProxyOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ServiceProxyOptions is the query options to a Service's proxy call.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"path\": { SchemaProps: spec.SchemaProps{ Description: \"Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_core_v1_ServiceSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ServiceSpec describes the attributes that a user creates on a service.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ports\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"port\", \"protocol\", }, \"x-kubernetes-list-type\":       \"map\", \"x-kubernetes-patch-merge-key\": \"port\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"The list of ports that are exposed by this service. More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.ServicePort\"), }, }, }, }, }, \"selector\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Route service traffic to pods with label keys and values matching this selector. If empty or not present, the service is assumed to have an external process managing its endpoints, which Kubernetes will not modify. Only applies to types ClusterIP, NodePort, and LoadBalancer. Ignored if type is ExternalName. More info: https://kubernetes.io/docs/concepts/services-networking/service/\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"clusterIP\": { SchemaProps: spec.SchemaProps{ Description: \"clusterIP is the IP address of the service and is usually assigned randomly. If an address is specified manually, is in-range (as per system configuration), and is not in use, it will be allocated to the service; otherwise creation of the service will fail. This field may not be changed through updates unless the type field is also being changed to ExternalName (which requires this field to be blank) or the type field is being changed from ExternalName (in which case this field may optionally be specified, as describe above).  Valid values are \"None\", empty string (\"\"), or a valid IP address. Setting this to \"None\" makes a \"headless service\" (no virtual IP), which is useful when direct endpoint connections are preferred and proxying is not required.  Only applies to types ClusterIP, NodePort, and LoadBalancer. If this field is specified when creating a Service of type ExternalName, creation will fail. This field will be wiped when updating a Service to type ExternalName. More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"clusterIPs\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"ClusterIPs is a list of IP addresses assigned to this service, and are usually assigned randomly.  If an address is specified manually, is in-range (as per system configuration), and is not in use, it will be allocated to the service; otherwise creation of the service will fail. This field may not be changed through updates unless the type field is also being changed to ExternalName (which requires this field to be empty) or the type field is being changed from ExternalName (in which case this field may optionally be specified, as describe above).  Valid values are \"None\", empty string (\"\"), or a valid IP address.  Setting this to \"None\" makes a \"headless service\" (no virtual IP), which is useful when direct endpoint connections are preferred and proxying is not required.  Only applies to types ClusterIP, NodePort, and LoadBalancer. If this field is specified when creating a Service of type ExternalName, creation will fail. This field will be wiped when updating a Service to type ExternalName.  If this field is not specified, it will be initialized from the clusterIP field.  If this field is specified, clients must ensure that clusterIPs[0] and clusterIP have the same value.nnThis field may hold a maximum of two entries (dual-stack IPs, in either order). These IPs must correspond to the values of the ipFamilies field. Both clusterIPs and ipFamilies are governed by the ipFamilyPolicy field. More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type determines how the Service is exposed. Defaults to ClusterIP. Valid options are ExternalName, ClusterIP, NodePort, and LoadBalancer. \"ClusterIP\" allocates a cluster-internal IP address for load-balancing to endpoints. Endpoints are determined by the selector or if that is not specified, by manual construction of an Endpoints object or EndpointSlice objects. If clusterIP is \"None\", no virtual IP is allocated and the endpoints are published as a set of endpoints rather than a virtual IP. \"NodePort\" builds on ClusterIP and allocates a port on every node which routes to the same endpoints as the clusterIP. \"LoadBalancer\" builds on NodePort and creates an external load-balancer (if supported in the current cloud) which routes to the same endpoints as the clusterIP. \"ExternalName\" aliases this service to the specified externalName. Several other fields do not apply to ExternalName services. More info: https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-typesnnPossible enum values:n - `\"ClusterIP\"` means a service will only be accessible inside the cluster, via the cluster IP.n - `\"ExternalName\"` means a service consists of only a reference to an external name that kubedns or equivalent will return as a CNAME record, with no exposing or proxying of any pods involved.n - `\"LoadBalancer\"` means a service will be exposed via an external load balancer (if the cloud provider supports it), in addition to 'NodePort' type.n - `\"NodePort\"` means a service will be exposed on one port of every node, in addition to 'ClusterIP' type.\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"ClusterIP\", \"ExternalName\", \"LoadBalancer\", \"NodePort\"}}, }, \"externalIPs\": { SchemaProps: spec.SchemaProps{ Description: \"externalIPs is a list of IP addresses for which nodes in the cluster will also accept traffic for this service.  These IPs are not managed by Kubernetes.  The user is responsible for ensuring that traffic arrives at a node with this IP.  A common example is external load-balancers that are not part of the Kubernetes system.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"sessionAffinity\": { SchemaProps: spec.SchemaProps{ Description: \"Supports \"ClientIP\" and \"None\". Used to maintain session affinity. Enable client IP based session affinity. Must be ClientIP or None. Defaults to None. More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxiesnnPossible enum values:n - `\"ClientIP\"` is the Client IP based.n - `\"None\"` - no session affinity.\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"ClientIP\", \"None\"}}, }, \"loadBalancerIP\": { SchemaProps: spec.SchemaProps{ Description: \"Only applies to Service Type: LoadBalancer. This feature depends on whether the underlying cloud-provider supports specifying the loadBalancerIP when a load balancer is created. This field will be ignored if the cloud-provider does not support the feature. Deprecated: This field was under-specified and its meaning varies across implementations, and it cannot support dual-stack. As of Kubernetes v1.24, users are encouraged to use implementation-specific annotations when available. This field may be removed in a future API version.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"loadBalancerSourceRanges\": { SchemaProps: spec.SchemaProps{ Description: \"If specified and supported by the platform, this will restrict traffic through the cloud-provider load-balancer will be restricted to the specified client IPs. This field will be ignored if the cloud-provider does not support the feature.\" More info: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"externalName\": { SchemaProps: spec.SchemaProps{ Description: \"externalName is the external reference that discovery mechanisms will return as an alias for this service (e.g. a DNS CNAME record). No proxying will be involved.  Must be a lowercase RFC-1123 hostname (https://tools.ietf.org/html/rfc1123) and requires `type` to be \"ExternalName\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"externalTrafficPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"externalTrafficPolicy denotes if this Service desires to route external traffic to node-local or cluster-wide endpoints. \"Local\" preserves the client source IP and avoids a second hop for LoadBalancer and Nodeport type services, but risks potentially imbalanced traffic spreading. \"Cluster\" obscures the client source IP and may cause a second hop to another node, but should have good overall load-spreading.nnPossible enum values:n - `\"Cluster\"` specifies node-global (legacy) behavior.n - `\"Local\"` specifies node-local endpoints behavior.\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"Cluster\", \"Local\"}}, }, \"healthCheckNodePort\": { SchemaProps: spec.SchemaProps{ Description: \"healthCheckNodePort specifies the healthcheck nodePort for the service. This only applies when type is set to LoadBalancer and externalTrafficPolicy is set to Local. If a value is specified, is in-range, and is not in use, it will be used.  If not specified, a value will be automatically allocated.  External systems (e.g. load-balancers) can use this port to determine if a given node holds endpoints for this service or not.  If this field is specified when creating a Service which does not need it, creation will fail. This field will be wiped when updating a Service to no longer need it (e.g. changing type).\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"publishNotReadyAddresses\": { SchemaProps: spec.SchemaProps{ Description: \"publishNotReadyAddresses indicates that any agent which deals with endpoints for this Service should disregard any indications of ready/not-ready. The primary use case for setting this field is for a StatefulSet's Headless Service to propagate SRV DNS records for its Pods for the purpose of peer discovery. The Kubernetes controllers that generate Endpoints and EndpointSlice resources for Services interpret this to mean that all endpoints are considered \"ready\" even if the Pods themselves are not. Agents which consume only Kubernetes generated endpoints through the Endpoints or EndpointSlice resources can safely assume this behavior.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"sessionAffinityConfig\": { SchemaProps: spec.SchemaProps{ Description: \"sessionAffinityConfig contains the configurations of session affinity.\", Ref:         ref(\"k8s.io/api/core/v1.SessionAffinityConfig\"), }, }, \"ipFamilies\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"IPFamilies is a list of IP families (e.g. IPv4, IPv6) assigned to this service. This field is usually assigned automatically based on cluster configuration and the ipFamilyPolicy field. If this field is specified manually, the requested family is available in the cluster, and ipFamilyPolicy allows it, it will be used; otherwise creation of the service will fail. This field is conditionally mutable: it allows for adding or removing a secondary IP family, but it does not allow changing the primary IP family of the Service. Valid values are \"IPv4\" and \"IPv6\".  This field only applies to Services of types ClusterIP, NodePort, and LoadBalancer, and does apply to \"headless\" services. This field will be wiped when updating a Service to type ExternalName.nnThis field may hold a maximum of two entries (dual-stack families, in either order).  These families must correspond to the values of the clusterIPs field, if specified. Both clusterIPs and ipFamilies are governed by the ipFamilyPolicy field.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"ipFamilyPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"IPFamilyPolicy represents the dual-stack-ness requested or required by this Service. If there is no value provided, then this field will be set to SingleStack. Services can be \"SingleStack\" (a single IP family), \"PreferDualStack\" (two IP families on dual-stack configured clusters or a single IP family on single-stack clusters), or \"RequireDualStack\" (two IP families on dual-stack configured clusters, otherwise fail). The ipFamilies and clusterIPs fields depend on the value of this field. This field will be wiped when updating a service to type ExternalName.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"allocateLoadBalancerNodePorts\": { SchemaProps: spec.SchemaProps{ Description: \"allocateLoadBalancerNodePorts defines if NodePorts will be automatically allocated for services with type LoadBalancer.  Default is \"true\". It may be set to \"false\" if the cluster load-balancer does not rely on NodePorts.  If the caller requests specific NodePorts (by specifying a value), those requests will be respected, regardless of this field. This field may only be set for services with type LoadBalancer and will be cleared if the type is changed to any other type.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"loadBalancerClass\": { SchemaProps: spec.SchemaProps{ Description: \"loadBalancerClass is the class of the load balancer implementation this Service belongs to. If specified, the value of this field must be a label-style identifier, with an optional prefix, e.g. \"internal-vip\" or \"example.com/internal-vip\". Unprefixed names are reserved for end-users. This field can only be set when the Service type is 'LoadBalancer'. If not set, the default load balancer implementation is used, today this is typically done through the cloud provider integration, but should apply for any default implementation. If set, it is assumed that a load balancer implementation is watching for Services with a matching class. Any default load balancer implementation (e.g. cloud providers) should ignore Services that set this field. This field can only be set when creating or updating a Service to type 'LoadBalancer'. Once set, it can not be changed. This field will be wiped when a service is updated to a non 'LoadBalancer' type.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"internalTrafficPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"InternalTrafficPolicy specifies if the cluster internal traffic should be routed to all endpoints or node-local endpoints only. \"Cluster\" routes internal traffic to a Service to all endpoints. \"Local\" routes traffic to node-local endpoints only, traffic is dropped if no node-local endpoints are ready. The default value is \"Cluster\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ServicePort\", \"k8s.io/api/core/v1.SessionAffinityConfig\"}, } } func schema_k8sio_api_core_v1_ServiceStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ServiceStatus represents the current status of a service.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"loadBalancer\": { SchemaProps: spec.SchemaProps{ Description: \"LoadBalancer contains the current status of the load-balancer, if one is present.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.LoadBalancerStatus\"), }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"type\", }, \"x-kubernetes-list-type\":       \"map\", \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Current service state\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Condition\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.LoadBalancerStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Condition\"}, } } func schema_k8sio_api_core_v1_SessionAffinityConfig(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SessionAffinityConfig represents the configurations of session affinity.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"clientIP\": { SchemaProps: spec.SchemaProps{ Description: \"clientIP contains the configurations of Client IP based session affinity.\", Ref:         ref(\"k8s.io/api/core/v1.ClientIPConfig\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ClientIPConfig\"}, } } func schema_k8sio_api_core_v1_StorageOSPersistentVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a StorageOS persistent volume resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"volumeName\": { SchemaProps: spec.SchemaProps{ Description: \"volumeName is the human-readable name of the StorageOS volume.  Volume names are only unique within a namespace.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"volumeNamespace\": { SchemaProps: spec.SchemaProps{ Description: \"volumeNamespace specifies the scope of the volume within StorageOS.  If no namespace is specified then the Pod's namespace will be used.  This allows the Kubernetes name scoping to be mirrored within StorageOS for tighter integration. Set VolumeName to any name to override the default behaviour. Set to \"default\" if you are not using namespaces within StorageOS. Namespaces that do not pre-exist within StorageOS will be created.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"secretRef\": { SchemaProps: spec.SchemaProps{ Description: \"secretRef specifies the secret to use for obtaining the StorageOS API credentials.  If not specified, default values will be attempted.\", Ref:         ref(\"k8s.io/api/core/v1.ObjectReference\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ObjectReference\"}, } } func schema_k8sio_api_core_v1_StorageOSVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a StorageOS persistent volume resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"volumeName\": { SchemaProps: spec.SchemaProps{ Description: \"volumeName is the human-readable name of the StorageOS volume.  Volume names are only unique within a namespace.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"volumeNamespace\": { SchemaProps: spec.SchemaProps{ Description: \"volumeNamespace specifies the scope of the volume within StorageOS.  If no namespace is specified then the Pod's namespace will be used.  This allows the Kubernetes name scoping to be mirrored within StorageOS for tighter integration. Set VolumeName to any name to override the default behaviour. Set to \"default\" if you are not using namespaces within StorageOS. Namespaces that do not pre-exist within StorageOS will be created.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"secretRef\": { SchemaProps: spec.SchemaProps{ Description: \"secretRef specifies the secret to use for obtaining the StorageOS API credentials.  If not specified, default values will be attempted.\", Ref:         ref(\"k8s.io/api/core/v1.LocalObjectReference\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.LocalObjectReference\"}, } } func schema_k8sio_api_core_v1_Sysctl(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Sysctl defines a kernel parameter to be set\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of a property to set\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"value\": { SchemaProps: spec.SchemaProps{ Description: \"Value of a property to set\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"value\"}, }, }, } } func schema_k8sio_api_core_v1_TCPSocketAction(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TCPSocketAction describes an action based on opening a socket\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"port\": { SchemaProps: spec.SchemaProps{ Description: \"Number or name of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, \"host\": { SchemaProps: spec.SchemaProps{ Description: \"Optional: Host name to connect to, defaults to the pod IP.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"port\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"}, } } func schema_k8sio_api_core_v1_Taint(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"The node this Taint is attached to has the \"effect\" on any pod that does not tolerate the Taint.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"key\": { SchemaProps: spec.SchemaProps{ Description: \"Required. The taint key to be applied to a node.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"value\": { SchemaProps: spec.SchemaProps{ Description: \"The taint value corresponding to the taint key.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"effect\": { SchemaProps: spec.SchemaProps{ Description: \"Required. The effect of the taint on pods that do not tolerate the taint. Valid effects are NoSchedule, PreferNoSchedule and NoExecute.nnPossible enum values:n - `\"NoExecute\"` Evict any already-running pods that do not tolerate the taint. Currently enforced by NodeController.n - `\"NoSchedule\"` Do not allow new pods to schedule onto the node unless they tolerate the taint, but allow all pods submitted to Kubelet without going through the scheduler to start, and allow all already-running pods to continue running. Enforced by the scheduler.n - `\"PreferNoSchedule\"` Like TaintEffectNoSchedule, but the scheduler tries not to schedule new pods onto the node, rather than prohibiting new pods from scheduling onto the node entirely. Enforced by the scheduler.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"NoExecute\", \"NoSchedule\", \"PreferNoSchedule\"}}, }, \"timeAdded\": { SchemaProps: spec.SchemaProps{ Description: \"TimeAdded represents the time at which the taint was added. It is only written for NoExecute taints.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, }, Required: []string{\"key\", \"effect\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_core_v1_Toleration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"The pod this Toleration is attached to tolerates any taint that matches the triple <key,value,effect> using the matching operator <operator>.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"key\": { SchemaProps: spec.SchemaProps{ Description: \"Key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"operator\": { SchemaProps: spec.SchemaProps{ Description: \"Operator represents a key's relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.nnPossible enum values:n - `\"Equal\"`n - `\"Exists\"`\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"Equal\", \"Exists\"}}, }, \"value\": { SchemaProps: spec.SchemaProps{ Description: \"Value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"effect\": { SchemaProps: spec.SchemaProps{ Description: \"Effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.nnPossible enum values:n - `\"NoExecute\"` Evict any already-running pods that do not tolerate the taint. Currently enforced by NodeController.n - `\"NoSchedule\"` Do not allow new pods to schedule onto the node unless they tolerate the taint, but allow all pods submitted to Kubelet without going through the scheduler to start, and allow all already-running pods to continue running. Enforced by the scheduler.n - `\"PreferNoSchedule\"` Like TaintEffectNoSchedule, but the scheduler tries not to schedule new pods onto the node, rather than prohibiting new pods from scheduling onto the node entirely. Enforced by the scheduler.\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"NoExecute\", \"NoSchedule\", \"PreferNoSchedule\"}}, }, \"tolerationSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"TolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, }, }, }, } } func schema_k8sio_api_core_v1_TopologySelectorLabelRequirement(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"A topology selector requirement is a selector that matches given label. This is an alpha feature and may change in the future.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"key\": { SchemaProps: spec.SchemaProps{ Description: \"The label key that the selector applies to.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"values\": { SchemaProps: spec.SchemaProps{ Description: \"An array of string values. One value must match the label to be selected. Each entry in Values is ORed.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"key\", \"values\"}, }, }, } } func schema_k8sio_api_core_v1_TopologySelectorTerm(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"A topology selector term represents the result of label queries. A null or empty topology selector term matches no objects. The requirements of them are ANDed. It provides a subset of functionality as NodeSelectorTerm. This is an alpha feature and may change in the future.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"matchLabelExpressions\": { SchemaProps: spec.SchemaProps{ Description: \"A list of topology selector requirements by labels.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.TopologySelectorLabelRequirement\"), }, }, }, }, }, }, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.TopologySelectorLabelRequirement\"}, } } func schema_k8sio_api_core_v1_TopologySpreadConstraint(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TopologySpreadConstraint specifies how to spread matching pods among the given topology.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"maxSkew\": { SchemaProps: spec.SchemaProps{ Description: \"MaxSkew describes the degree to which pods may be unevenly distributed. When `whenUnsatisfiable=DoNotSchedule`, it is the maximum permitted difference between the number of matching pods in the target topology and the global minimum. For example, in a 3-zone cluster, MaxSkew is set to 1, and pods with the same labelSelector spread as 1/1/0: | zone1 | zone2 | zone3 | |   P   |   P   |       | - if MaxSkew is 1, incoming pod can only be scheduled to zone3 to become 1/1/1; scheduling it onto zone1(zone2) would make the ActualSkew(2-0) on zone1(zone2) violate MaxSkew(1). - if MaxSkew is 2, incoming pod can be scheduled onto any zone. When `whenUnsatisfiable=ScheduleAnyway`, it is used to give higher precedence to topologies that satisfy it. It's a required field. Default value is 1 and 0 is not allowed.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"topologyKey\": { SchemaProps: spec.SchemaProps{ Description: \"TopologyKey is the key of node labels. Nodes that have a label with this key and identical values are considered to be in the same topology. We consider each <key, value> as a \"bucket\", and try to put balanced number of pods into each bucket. It's a required field.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"whenUnsatisfiable\": { SchemaProps: spec.SchemaProps{ Description: \"WhenUnsatisfiable indicates how to deal with a pod if it doesn't satisfy the spread constraint. - DoNotSchedule (default) tells the scheduler not to schedule it. - ScheduleAnyway tells the scheduler to schedule the pod in any location,n  but giving higher precedence to topologies that would help reduce then  skew.nA constraint is considered \"Unsatisfiable\" for an incoming pod if and only if every possible node assignment for that pod would violate \"MaxSkew\" on some topology. For example, in a 3-zone cluster, MaxSkew is set to 1, and pods with the same labelSelector spread as 3/1/1: | zone1 | zone2 | zone3 | | P P P |   P   |   P   | If WhenUnsatisfiable is set to DoNotSchedule, incoming pod can only be scheduled to zone2(zone3) to become 3/2/1(3/1/2) as ActualSkew(2-1) on zone2(zone3) satisfies MaxSkew(1). In other words, the cluster can still be imbalanced, but scheduler won't make it *more* imbalanced. It's a required field.nnPossible enum values:n - `\"DoNotSchedule\"` instructs the scheduler not to schedule the pod when constraints are not satisfied.n - `\"ScheduleAnyway\"` instructs the scheduler to schedule the pod even if constraints are not satisfied.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"DoNotSchedule\", \"ScheduleAnyway\"}}, }, \"labelSelector\": { SchemaProps: spec.SchemaProps{ Description: \"LabelSelector is used to find matching pods. Pods that match this label selector are counted to determine the number of pods in their corresponding topology domain.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, }, Required: []string{\"maxSkew\", \"topologyKey\", \"whenUnsatisfiable\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_core_v1_TypedLocalObjectReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TypedLocalObjectReference contains enough information to let you locate the typed referenced object inside the same namespace.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"apiGroup\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroup is the group for the resource being referenced. If APIGroup is not specified, the specified Kind must be in the core API group. For any other third-party types, APIGroup is required.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is the type of resource being referenced\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the name of resource being referenced\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"kind\", \"name\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, } } func schema_k8sio_api_core_v1_Volume(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Volume represents a named volume in a pod that may be accessed by any container in the pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name of the volume. Must be a DNS_LABEL and unique within the pod. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"hostPath\": { SchemaProps: spec.SchemaProps{ Description: \"hostPath represents a pre-existing file or directory on the host machine that is directly exposed to the container. This is generally used for system agents or other privileged things that are allowed to see the host machine. Most containers will NOT need this. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath\", Ref:         ref(\"k8s.io/api/core/v1.HostPathVolumeSource\"), }, }, \"emptyDir\": { SchemaProps: spec.SchemaProps{ Description: \"emptyDir represents a temporary directory that shares a pod's lifetime. More info: https://kubernetes.io/docs/concepts/storage/volumes#emptydir\", Ref:         ref(\"k8s.io/api/core/v1.EmptyDirVolumeSource\"), }, }, \"gcePersistentDisk\": { SchemaProps: spec.SchemaProps{ Description: \"gcePersistentDisk represents a GCE Disk resource that is attached to a kubelet's host machine and then exposed to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk\", Ref:         ref(\"k8s.io/api/core/v1.GCEPersistentDiskVolumeSource\"), }, }, \"awsElasticBlockStore\": { SchemaProps: spec.SchemaProps{ Description: \"awsElasticBlockStore represents an AWS Disk resource that is attached to a kubelet's host machine and then exposed to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore\", Ref:         ref(\"k8s.io/api/core/v1.AWSElasticBlockStoreVolumeSource\"), }, }, \"gitRepo\": { SchemaProps: spec.SchemaProps{ Description: \"gitRepo represents a git repository at a particular revision. DEPRECATED: GitRepo is deprecated. To provision a container with a git repo, mount an EmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir into the Pod's container.\", Ref:         ref(\"k8s.io/api/core/v1.GitRepoVolumeSource\"), }, }, \"secret\": { SchemaProps: spec.SchemaProps{ Description: \"secret represents a secret that should populate this volume. More info: https://kubernetes.io/docs/concepts/storage/volumes#secret\", Ref:         ref(\"k8s.io/api/core/v1.SecretVolumeSource\"), }, }, \"nfs\": { SchemaProps: spec.SchemaProps{ Description: \"nfs represents an NFS mount on the host that shares a pod's lifetime More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs\", Ref:         ref(\"k8s.io/api/core/v1.NFSVolumeSource\"), }, }, \"iscsi\": { SchemaProps: spec.SchemaProps{ Description: \"iscsi represents an ISCSI Disk resource that is attached to a kubelet's host machine and then exposed to the pod. More info: https://examples.k8s.io/volumes/iscsi/README.md\", Ref:         ref(\"k8s.io/api/core/v1.ISCSIVolumeSource\"), }, }, \"glusterfs\": { SchemaProps: spec.SchemaProps{ Description: \"glusterfs represents a Glusterfs mount on the host that shares a pod's lifetime. More info: https://examples.k8s.io/volumes/glusterfs/README.md\", Ref:         ref(\"k8s.io/api/core/v1.GlusterfsVolumeSource\"), }, }, \"persistentVolumeClaim\": { SchemaProps: spec.SchemaProps{ Description: \"persistentVolumeClaimVolumeSource represents a reference to a PersistentVolumeClaim in the same namespace. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims\", Ref:         ref(\"k8s.io/api/core/v1.PersistentVolumeClaimVolumeSource\"), }, }, \"rbd\": { SchemaProps: spec.SchemaProps{ Description: \"rbd represents a Rados Block Device mount on the host that shares a pod's lifetime. More info: https://examples.k8s.io/volumes/rbd/README.md\", Ref:         ref(\"k8s.io/api/core/v1.RBDVolumeSource\"), }, }, \"flexVolume\": { SchemaProps: spec.SchemaProps{ Description: \"flexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin.\", Ref:         ref(\"k8s.io/api/core/v1.FlexVolumeSource\"), }, }, \"cinder\": { SchemaProps: spec.SchemaProps{ Description: \"cinder represents a cinder volume attached and mounted on kubelets host machine. More info: https://examples.k8s.io/mysql-cinder-pd/README.md\", Ref:         ref(\"k8s.io/api/core/v1.CinderVolumeSource\"), }, }, \"cephfs\": { SchemaProps: spec.SchemaProps{ Description: \"cephFS represents a Ceph FS mount on the host that shares a pod's lifetime\", Ref:         ref(\"k8s.io/api/core/v1.CephFSVolumeSource\"), }, }, \"flocker\": { SchemaProps: spec.SchemaProps{ Description: \"flocker represents a Flocker volume attached to a kubelet's host machine. This depends on the Flocker control service being running\", Ref:         ref(\"k8s.io/api/core/v1.FlockerVolumeSource\"), }, }, \"downwardAPI\": { SchemaProps: spec.SchemaProps{ Description: \"downwardAPI represents downward API about the pod that should populate this volume\", Ref:         ref(\"k8s.io/api/core/v1.DownwardAPIVolumeSource\"), }, }, \"fc\": { SchemaProps: spec.SchemaProps{ Description: \"fc represents a Fibre Channel resource that is attached to a kubelet's host machine and then exposed to the pod.\", Ref:         ref(\"k8s.io/api/core/v1.FCVolumeSource\"), }, }, \"azureFile\": { SchemaProps: spec.SchemaProps{ Description: \"azureFile represents an Azure File Service mount on the host and bind mount to the pod.\", Ref:         ref(\"k8s.io/api/core/v1.AzureFileVolumeSource\"), }, }, \"configMap\": { SchemaProps: spec.SchemaProps{ Description: \"configMap represents a configMap that should populate this volume\", Ref:         ref(\"k8s.io/api/core/v1.ConfigMapVolumeSource\"), }, }, \"vsphereVolume\": { SchemaProps: spec.SchemaProps{ Description: \"vsphereVolume represents a vSphere volume attached and mounted on kubelets host machine\", Ref:         ref(\"k8s.io/api/core/v1.VsphereVirtualDiskVolumeSource\"), }, }, \"quobyte\": { SchemaProps: spec.SchemaProps{ Description: \"quobyte represents a Quobyte mount on the host that shares a pod's lifetime\", Ref:         ref(\"k8s.io/api/core/v1.QuobyteVolumeSource\"), }, }, \"azureDisk\": { SchemaProps: spec.SchemaProps{ Description: \"azureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.\", Ref:         ref(\"k8s.io/api/core/v1.AzureDiskVolumeSource\"), }, }, \"photonPersistentDisk\": { SchemaProps: spec.SchemaProps{ Description: \"photonPersistentDisk represents a PhotonController persistent disk attached and mounted on kubelets host machine\", Ref:         ref(\"k8s.io/api/core/v1.PhotonPersistentDiskVolumeSource\"), }, }, \"projected\": { SchemaProps: spec.SchemaProps{ Description: \"projected items for all in one resources secrets, configmaps, and downward API\", Ref:         ref(\"k8s.io/api/core/v1.ProjectedVolumeSource\"), }, }, \"portworxVolume\": { SchemaProps: spec.SchemaProps{ Description: \"portworxVolume represents a portworx volume attached and mounted on kubelets host machine\", Ref:         ref(\"k8s.io/api/core/v1.PortworxVolumeSource\"), }, }, \"scaleIO\": { SchemaProps: spec.SchemaProps{ Description: \"scaleIO represents a ScaleIO persistent volume attached and mounted on Kubernetes nodes.\", Ref:         ref(\"k8s.io/api/core/v1.ScaleIOVolumeSource\"), }, }, \"storageos\": { SchemaProps: spec.SchemaProps{ Description: \"storageOS represents a StorageOS volume attached and mounted on Kubernetes nodes.\", Ref:         ref(\"k8s.io/api/core/v1.StorageOSVolumeSource\"), }, }, \"csi\": { SchemaProps: spec.SchemaProps{ Description: \"csi (Container Storage Interface) represents ephemeral storage that is handled by certain external CSI drivers (Beta feature).\", Ref:         ref(\"k8s.io/api/core/v1.CSIVolumeSource\"), }, }, \"ephemeral\": { SchemaProps: spec.SchemaProps{ Description: \"ephemeral represents a volume that is handled by a cluster storage driver. The volume's lifecycle is tied to the pod that defines it - it will be created before the pod starts, and deleted when the pod is removed.nnUse this if: a) the volume is only needed while the pod runs, b) features of normal volumes like restoring from snapshot or capacityn   tracking are needed,nc) the storage driver is specified through a storage class, and d) the storage driver supports dynamic volume provisioning throughn   a PersistentVolumeClaim (see EphemeralVolumeSource for moren   information on the connection between this volume typen   and PersistentVolumeClaim).nnUse PersistentVolumeClaim or one of the vendor-specific APIs for volumes that persist for longer than the lifecycle of an individual pod.nnUse CSI for light-weight local ephemeral volumes if the CSI driver is meant to be used that way - see the documentation of the driver for more information.nnA pod can use both types of ephemeral volumes and persistent volumes at the same time.\", Ref:         ref(\"k8s.io/api/core/v1.EphemeralVolumeSource\"), }, }, }, Required: []string{\"name\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.AWSElasticBlockStoreVolumeSource\", \"k8s.io/api/core/v1.AzureDiskVolumeSource\", \"k8s.io/api/core/v1.AzureFileVolumeSource\", \"k8s.io/api/core/v1.CSIVolumeSource\", \"k8s.io/api/core/v1.CephFSVolumeSource\", \"k8s.io/api/core/v1.CinderVolumeSource\", \"k8s.io/api/core/v1.ConfigMapVolumeSource\", \"k8s.io/api/core/v1.DownwardAPIVolumeSource\", \"k8s.io/api/core/v1.EmptyDirVolumeSource\", \"k8s.io/api/core/v1.EphemeralVolumeSource\", \"k8s.io/api/core/v1.FCVolumeSource\", \"k8s.io/api/core/v1.FlexVolumeSource\", \"k8s.io/api/core/v1.FlockerVolumeSource\", \"k8s.io/api/core/v1.GCEPersistentDiskVolumeSource\", \"k8s.io/api/core/v1.GitRepoVolumeSource\", \"k8s.io/api/core/v1.GlusterfsVolumeSource\", \"k8s.io/api/core/v1.HostPathVolumeSource\", \"k8s.io/api/core/v1.ISCSIVolumeSource\", \"k8s.io/api/core/v1.NFSVolumeSource\", \"k8s.io/api/core/v1.PersistentVolumeClaimVolumeSource\", \"k8s.io/api/core/v1.PhotonPersistentDiskVolumeSource\", \"k8s.io/api/core/v1.PortworxVolumeSource\", \"k8s.io/api/core/v1.ProjectedVolumeSource\", \"k8s.io/api/core/v1.QuobyteVolumeSource\", \"k8s.io/api/core/v1.RBDVolumeSource\", \"k8s.io/api/core/v1.ScaleIOVolumeSource\", \"k8s.io/api/core/v1.SecretVolumeSource\", \"k8s.io/api/core/v1.StorageOSVolumeSource\", \"k8s.io/api/core/v1.VsphereVirtualDiskVolumeSource\"}, } } func schema_k8sio_api_core_v1_VolumeDevice(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"volumeDevice describes a mapping of a raw block device within a container.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name must match the name of a persistentVolumeClaim in the pod\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"devicePath\": { SchemaProps: spec.SchemaProps{ Description: \"devicePath is the path inside of the container that the device will be mapped to.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"devicePath\"}, }, }, } } func schema_k8sio_api_core_v1_VolumeMount(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeMount describes a mounting of a Volume within a container.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"This must match the Name of a Volume.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"Mounted read-only if true, read-write otherwise (false or unspecified). Defaults to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"mountPath\": { SchemaProps: spec.SchemaProps{ Description: \"Path within the container at which the volume should be mounted.  Must not contain ':'.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"subPath\": { SchemaProps: spec.SchemaProps{ Description: \"Path within the volume from which the container's volume should be mounted. Defaults to \"\" (volume's root).\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"mountPropagation\": { SchemaProps: spec.SchemaProps{ Description: \"mountPropagation determines how mounts are propagated from the host to container and the other way around. When not set, MountPropagationNone is used. This field is beta in 1.10.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"subPathExpr\": { SchemaProps: spec.SchemaProps{ Description: \"Expanded path within the volume from which the container's volume should be mounted. Behaves similarly to SubPath but environment variable references $(VAR_NAME) are expanded using the container's environment. Defaults to \"\" (volume's root). SubPathExpr and SubPath are mutually exclusive.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"mountPath\"}, }, }, } } func schema_k8sio_api_core_v1_VolumeNodeAffinity(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeNodeAffinity defines constraints that limit what nodes this volume can be accessed from.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"required\": { SchemaProps: spec.SchemaProps{ Description: \"required specifies hard node constraints that must be met.\", Ref:         ref(\"k8s.io/api/core/v1.NodeSelector\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.NodeSelector\"}, } } func schema_k8sio_api_core_v1_VolumeProjection(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Projection that may be projected along with other supported volume types\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"secret\": { SchemaProps: spec.SchemaProps{ Description: \"secret information about the secret data to project\", Ref:         ref(\"k8s.io/api/core/v1.SecretProjection\"), }, }, \"downwardAPI\": { SchemaProps: spec.SchemaProps{ Description: \"downwardAPI information about the downwardAPI data to project\", Ref:         ref(\"k8s.io/api/core/v1.DownwardAPIProjection\"), }, }, \"configMap\": { SchemaProps: spec.SchemaProps{ Description: \"configMap information about the configMap data to project\", Ref:         ref(\"k8s.io/api/core/v1.ConfigMapProjection\"), }, }, \"serviceAccountToken\": { SchemaProps: spec.SchemaProps{ Description: \"serviceAccountToken is information about the serviceAccountToken data to project\", Ref:         ref(\"k8s.io/api/core/v1.ServiceAccountTokenProjection\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ConfigMapProjection\", \"k8s.io/api/core/v1.DownwardAPIProjection\", \"k8s.io/api/core/v1.SecretProjection\", \"k8s.io/api/core/v1.ServiceAccountTokenProjection\"}, } } func schema_k8sio_api_core_v1_VolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents the source of a volume to mount. Only one of its members may be specified.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"hostPath\": { SchemaProps: spec.SchemaProps{ Description: \"hostPath represents a pre-existing file or directory on the host machine that is directly exposed to the container. This is generally used for system agents or other privileged things that are allowed to see the host machine. Most containers will NOT need this. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath\", Ref:         ref(\"k8s.io/api/core/v1.HostPathVolumeSource\"), }, }, \"emptyDir\": { SchemaProps: spec.SchemaProps{ Description: \"emptyDir represents a temporary directory that shares a pod's lifetime. More info: https://kubernetes.io/docs/concepts/storage/volumes#emptydir\", Ref:         ref(\"k8s.io/api/core/v1.EmptyDirVolumeSource\"), }, }, \"gcePersistentDisk\": { SchemaProps: spec.SchemaProps{ Description: \"gcePersistentDisk represents a GCE Disk resource that is attached to a kubelet's host machine and then exposed to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk\", Ref:         ref(\"k8s.io/api/core/v1.GCEPersistentDiskVolumeSource\"), }, }, \"awsElasticBlockStore\": { SchemaProps: spec.SchemaProps{ Description: \"awsElasticBlockStore represents an AWS Disk resource that is attached to a kubelet's host machine and then exposed to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore\", Ref:         ref(\"k8s.io/api/core/v1.AWSElasticBlockStoreVolumeSource\"), }, }, \"gitRepo\": { SchemaProps: spec.SchemaProps{ Description: \"gitRepo represents a git repository at a particular revision. DEPRECATED: GitRepo is deprecated. To provision a container with a git repo, mount an EmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir into the Pod's container.\", Ref:         ref(\"k8s.io/api/core/v1.GitRepoVolumeSource\"), }, }, \"secret\": { SchemaProps: spec.SchemaProps{ Description: \"secret represents a secret that should populate this volume. More info: https://kubernetes.io/docs/concepts/storage/volumes#secret\", Ref:         ref(\"k8s.io/api/core/v1.SecretVolumeSource\"), }, }, \"nfs\": { SchemaProps: spec.SchemaProps{ Description: \"nfs represents an NFS mount on the host that shares a pod's lifetime More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs\", Ref:         ref(\"k8s.io/api/core/v1.NFSVolumeSource\"), }, }, \"iscsi\": { SchemaProps: spec.SchemaProps{ Description: \"iscsi represents an ISCSI Disk resource that is attached to a kubelet's host machine and then exposed to the pod. More info: https://examples.k8s.io/volumes/iscsi/README.md\", Ref:         ref(\"k8s.io/api/core/v1.ISCSIVolumeSource\"), }, }, \"glusterfs\": { SchemaProps: spec.SchemaProps{ Description: \"glusterfs represents a Glusterfs mount on the host that shares a pod's lifetime. More info: https://examples.k8s.io/volumes/glusterfs/README.md\", Ref:         ref(\"k8s.io/api/core/v1.GlusterfsVolumeSource\"), }, }, \"persistentVolumeClaim\": { SchemaProps: spec.SchemaProps{ Description: \"persistentVolumeClaimVolumeSource represents a reference to a PersistentVolumeClaim in the same namespace. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims\", Ref:         ref(\"k8s.io/api/core/v1.PersistentVolumeClaimVolumeSource\"), }, }, \"rbd\": { SchemaProps: spec.SchemaProps{ Description: \"rbd represents a Rados Block Device mount on the host that shares a pod's lifetime. More info: https://examples.k8s.io/volumes/rbd/README.md\", Ref:         ref(\"k8s.io/api/core/v1.RBDVolumeSource\"), }, }, \"flexVolume\": { SchemaProps: spec.SchemaProps{ Description: \"flexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin.\", Ref:         ref(\"k8s.io/api/core/v1.FlexVolumeSource\"), }, }, \"cinder\": { SchemaProps: spec.SchemaProps{ Description: \"cinder represents a cinder volume attached and mounted on kubelets host machine. More info: https://examples.k8s.io/mysql-cinder-pd/README.md\", Ref:         ref(\"k8s.io/api/core/v1.CinderVolumeSource\"), }, }, \"cephfs\": { SchemaProps: spec.SchemaProps{ Description: \"cephFS represents a Ceph FS mount on the host that shares a pod's lifetime\", Ref:         ref(\"k8s.io/api/core/v1.CephFSVolumeSource\"), }, }, \"flocker\": { SchemaProps: spec.SchemaProps{ Description: \"flocker represents a Flocker volume attached to a kubelet's host machine. This depends on the Flocker control service being running\", Ref:         ref(\"k8s.io/api/core/v1.FlockerVolumeSource\"), }, }, \"downwardAPI\": { SchemaProps: spec.SchemaProps{ Description: \"downwardAPI represents downward API about the pod that should populate this volume\", Ref:         ref(\"k8s.io/api/core/v1.DownwardAPIVolumeSource\"), }, }, \"fc\": { SchemaProps: spec.SchemaProps{ Description: \"fc represents a Fibre Channel resource that is attached to a kubelet's host machine and then exposed to the pod.\", Ref:         ref(\"k8s.io/api/core/v1.FCVolumeSource\"), }, }, \"azureFile\": { SchemaProps: spec.SchemaProps{ Description: \"azureFile represents an Azure File Service mount on the host and bind mount to the pod.\", Ref:         ref(\"k8s.io/api/core/v1.AzureFileVolumeSource\"), }, }, \"configMap\": { SchemaProps: spec.SchemaProps{ Description: \"configMap represents a configMap that should populate this volume\", Ref:         ref(\"k8s.io/api/core/v1.ConfigMapVolumeSource\"), }, }, \"vsphereVolume\": { SchemaProps: spec.SchemaProps{ Description: \"vsphereVolume represents a vSphere volume attached and mounted on kubelets host machine\", Ref:         ref(\"k8s.io/api/core/v1.VsphereVirtualDiskVolumeSource\"), }, }, \"quobyte\": { SchemaProps: spec.SchemaProps{ Description: \"quobyte represents a Quobyte mount on the host that shares a pod's lifetime\", Ref:         ref(\"k8s.io/api/core/v1.QuobyteVolumeSource\"), }, }, \"azureDisk\": { SchemaProps: spec.SchemaProps{ Description: \"azureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.\", Ref:         ref(\"k8s.io/api/core/v1.AzureDiskVolumeSource\"), }, }, \"photonPersistentDisk\": { SchemaProps: spec.SchemaProps{ Description: \"photonPersistentDisk represents a PhotonController persistent disk attached and mounted on kubelets host machine\", Ref:         ref(\"k8s.io/api/core/v1.PhotonPersistentDiskVolumeSource\"), }, }, \"projected\": { SchemaProps: spec.SchemaProps{ Description: \"projected items for all in one resources secrets, configmaps, and downward API\", Ref:         ref(\"k8s.io/api/core/v1.ProjectedVolumeSource\"), }, }, \"portworxVolume\": { SchemaProps: spec.SchemaProps{ Description: \"portworxVolume represents a portworx volume attached and mounted on kubelets host machine\", Ref:         ref(\"k8s.io/api/core/v1.PortworxVolumeSource\"), }, }, \"scaleIO\": { SchemaProps: spec.SchemaProps{ Description: \"scaleIO represents a ScaleIO persistent volume attached and mounted on Kubernetes nodes.\", Ref:         ref(\"k8s.io/api/core/v1.ScaleIOVolumeSource\"), }, }, \"storageos\": { SchemaProps: spec.SchemaProps{ Description: \"storageOS represents a StorageOS volume attached and mounted on Kubernetes nodes.\", Ref:         ref(\"k8s.io/api/core/v1.StorageOSVolumeSource\"), }, }, \"csi\": { SchemaProps: spec.SchemaProps{ Description: \"csi (Container Storage Interface) represents ephemeral storage that is handled by certain external CSI drivers (Beta feature).\", Ref:         ref(\"k8s.io/api/core/v1.CSIVolumeSource\"), }, }, \"ephemeral\": { SchemaProps: spec.SchemaProps{ Description: \"ephemeral represents a volume that is handled by a cluster storage driver. The volume's lifecycle is tied to the pod that defines it - it will be created before the pod starts, and deleted when the pod is removed.nnUse this if: a) the volume is only needed while the pod runs, b) features of normal volumes like restoring from snapshot or capacityn   tracking are needed,nc) the storage driver is specified through a storage class, and d) the storage driver supports dynamic volume provisioning throughn   a PersistentVolumeClaim (see EphemeralVolumeSource for moren   information on the connection between this volume typen   and PersistentVolumeClaim).nnUse PersistentVolumeClaim or one of the vendor-specific APIs for volumes that persist for longer than the lifecycle of an individual pod.nnUse CSI for light-weight local ephemeral volumes if the CSI driver is meant to be used that way - see the documentation of the driver for more information.nnA pod can use both types of ephemeral volumes and persistent volumes at the same time.\", Ref:         ref(\"k8s.io/api/core/v1.EphemeralVolumeSource\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.AWSElasticBlockStoreVolumeSource\", \"k8s.io/api/core/v1.AzureDiskVolumeSource\", \"k8s.io/api/core/v1.AzureFileVolumeSource\", \"k8s.io/api/core/v1.CSIVolumeSource\", \"k8s.io/api/core/v1.CephFSVolumeSource\", \"k8s.io/api/core/v1.CinderVolumeSource\", \"k8s.io/api/core/v1.ConfigMapVolumeSource\", \"k8s.io/api/core/v1.DownwardAPIVolumeSource\", \"k8s.io/api/core/v1.EmptyDirVolumeSource\", \"k8s.io/api/core/v1.EphemeralVolumeSource\", \"k8s.io/api/core/v1.FCVolumeSource\", \"k8s.io/api/core/v1.FlexVolumeSource\", \"k8s.io/api/core/v1.FlockerVolumeSource\", \"k8s.io/api/core/v1.GCEPersistentDiskVolumeSource\", \"k8s.io/api/core/v1.GitRepoVolumeSource\", \"k8s.io/api/core/v1.GlusterfsVolumeSource\", \"k8s.io/api/core/v1.HostPathVolumeSource\", \"k8s.io/api/core/v1.ISCSIVolumeSource\", \"k8s.io/api/core/v1.NFSVolumeSource\", \"k8s.io/api/core/v1.PersistentVolumeClaimVolumeSource\", \"k8s.io/api/core/v1.PhotonPersistentDiskVolumeSource\", \"k8s.io/api/core/v1.PortworxVolumeSource\", \"k8s.io/api/core/v1.ProjectedVolumeSource\", \"k8s.io/api/core/v1.QuobyteVolumeSource\", \"k8s.io/api/core/v1.RBDVolumeSource\", \"k8s.io/api/core/v1.ScaleIOVolumeSource\", \"k8s.io/api/core/v1.SecretVolumeSource\", \"k8s.io/api/core/v1.StorageOSVolumeSource\", \"k8s.io/api/core/v1.VsphereVirtualDiskVolumeSource\"}, } } func schema_k8sio_api_core_v1_VsphereVirtualDiskVolumeSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Represents a vSphere volume resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"volumePath\": { SchemaProps: spec.SchemaProps{ Description: \"volumePath is the path that identifies vSphere volume vmdk\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fsType\": { SchemaProps: spec.SchemaProps{ Description: \"fsType is filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"storagePolicyName\": { SchemaProps: spec.SchemaProps{ Description: \"storagePolicyName is the storage Policy Based Management (SPBM) profile name.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"storagePolicyID\": { SchemaProps: spec.SchemaProps{ Description: \"storagePolicyID is the storage Policy Based Management (SPBM) profile ID associated with the StoragePolicyName.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"volumePath\"}, }, }, } } func schema_k8sio_api_core_v1_WeightedPodAffinityTerm(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"The weights of all of the matched WeightedPodAffinityTerm fields are added per-node to find the most preferred node(s)\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"weight\": { SchemaProps: spec.SchemaProps{ Description: \"weight associated with matching the corresponding podAffinityTerm, in the range 1-100.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"podAffinityTerm\": { SchemaProps: spec.SchemaProps{ Description: \"Required. A pod affinity term, associated with the corresponding weight.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodAffinityTerm\"), }, }, }, Required: []string{\"weight\", \"podAffinityTerm\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PodAffinityTerm\"}, } } func schema_k8sio_api_core_v1_WindowsSecurityContextOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"WindowsSecurityContextOptions contain Windows-specific options and credentials.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"gmsaCredentialSpecName\": { SchemaProps: spec.SchemaProps{ Description: \"GMSACredentialSpecName is the name of the GMSA credential spec to use.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"gmsaCredentialSpec\": { SchemaProps: spec.SchemaProps{ Description: \"GMSACredentialSpec is where the GMSA admission webhook (https://github.com/kubernetes-sigs/windows-gmsa) inlines the contents of the GMSA credential spec named by the GMSACredentialSpecName field.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"runAsUserName\": { SchemaProps: spec.SchemaProps{ Description: \"The UserName in Windows to run the entrypoint of the container process. Defaults to the user specified in image metadata if unspecified. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"hostProcess\": { SchemaProps: spec.SchemaProps{ Description: \"HostProcess determines if a container should be run as a 'Host Process' container. This field is alpha-level and will only be honored by components that enable the WindowsHostProcessContainers feature flag. Setting this field without the feature flag will result in errors when validating the Pod. All of a Pod's containers must have the same effective HostProcess value (it is not allowed to have a mix of HostProcess containers and non-HostProcess containers).  In addition, if HostProcess is true then HostNetwork must also be set to true.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_discovery_v1_Endpoint(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Endpoint represents a single logical \"backend\" implementing a service.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"addresses\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"addresses of this endpoint. The contents of this field are interpreted according to the corresponding EndpointSlice addressType field. Consumers must handle different types of addresses in the context of their own capabilities. This must contain at least one address but no more than 100. These are all assumed to be fungible and clients may choose to only use the first element. Refer to: https://issue.k8s.io/106267\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"conditions\": { SchemaProps: spec.SchemaProps{ Description: \"conditions contains information about the current status of the endpoint.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/discovery/v1.EndpointConditions\"), }, }, \"hostname\": { SchemaProps: spec.SchemaProps{ Description: \"hostname of this endpoint. This field may be used by consumers of endpoints to distinguish endpoints from each other (e.g. in DNS names). Multiple endpoints which use the same hostname should be considered fungible (e.g. multiple A values in DNS). Must be lowercase and pass DNS Label (RFC 1123) validation.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"targetRef\": { SchemaProps: spec.SchemaProps{ Description: \"targetRef is a reference to a Kubernetes object that represents this endpoint.\", Ref:         ref(\"k8s.io/api/core/v1.ObjectReference\"), }, }, \"deprecatedTopology\": { SchemaProps: spec.SchemaProps{ Description: \"deprecatedTopology contains topology information part of the v1beta1 API. This field is deprecated, and will be removed when the v1beta1 API is removed (no sooner than kubernetes v1.24).  While this field can hold values, it is not writable through the v1 API, and any attempts to write to it will be silently ignored. Topology information can be found in the zone and nodeName fields instead.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"nodeName\": { SchemaProps: spec.SchemaProps{ Description: \"nodeName represents the name of the Node hosting this endpoint. This can be used to determine endpoints local to a Node. This field can be enabled with the EndpointSliceNodeName feature gate.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"zone\": { SchemaProps: spec.SchemaProps{ Description: \"zone is the name of the Zone this endpoint exists in.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"hints\": { SchemaProps: spec.SchemaProps{ Description: \"hints contains information associated with how an endpoint should be consumed.\", Ref:         ref(\"k8s.io/api/discovery/v1.EndpointHints\"), }, }, }, Required: []string{\"addresses\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ObjectReference\", \"k8s.io/api/discovery/v1.EndpointConditions\", \"k8s.io/api/discovery/v1.EndpointHints\"}, } } func schema_k8sio_api_discovery_v1_EndpointConditions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EndpointConditions represents the current condition of an endpoint.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ready\": { SchemaProps: spec.SchemaProps{ Description: \"ready indicates that this endpoint is prepared to receive traffic, according to whatever system is managing the endpoint. A nil value indicates an unknown state. In most cases consumers should interpret this unknown state as ready. For compatibility reasons, ready should never be \"true\" for terminating endpoints.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"serving\": { SchemaProps: spec.SchemaProps{ Description: \"serving is identical to ready except that it is set regardless of the terminating state of endpoints. This condition should be set to true for a ready endpoint that is terminating. If nil, consumers should defer to the ready condition. This field can be enabled with the EndpointSliceTerminatingCondition feature gate.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"terminating\": { SchemaProps: spec.SchemaProps{ Description: \"terminating indicates that this endpoint is terminating. A nil value indicates an unknown state. Consumers should interpret this unknown state to mean that the endpoint is not terminating. This field can be enabled with the EndpointSliceTerminatingCondition feature gate.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_discovery_v1_EndpointHints(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EndpointHints provides hints describing how an endpoint should be consumed.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"forZones\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"forZones indicates the zone(s) this endpoint should be consumed by to enable topology aware routing.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/discovery/v1.ForZone\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/discovery/v1.ForZone\"}, } } func schema_k8sio_api_discovery_v1_EndpointPort(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EndpointPort represents a Port used by an EndpointSlice\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"The name of this port. All ports in an EndpointSlice must have a unique name. If the EndpointSlice is dervied from a Kubernetes service, this corresponds to the Service.ports[].name. Name must either be an empty string or pass DNS_LABEL validation: * must be no more than 63 characters long. * must consist of lower case alphanumeric characters or '-'. * must start and end with an alphanumeric character. Default is empty string.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"protocol\": { SchemaProps: spec.SchemaProps{ Description: \"The IP protocol for this port. Must be UDP, TCP, or SCTP. Default is TCP.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"port\": { SchemaProps: spec.SchemaProps{ Description: \"The port number of the endpoint. If this is not specified, ports are not restricted and must be interpreted in the context of the specific consumer.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"appProtocol\": { SchemaProps: spec.SchemaProps{ Description: \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, } } func schema_k8sio_api_discovery_v1_EndpointSlice(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EndpointSlice represents a subset of the endpoints that implement a service. For a given service there may be multiple EndpointSlice objects, selected by labels, which must be joined to produce the full set of endpoints.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"addressType\": { SchemaProps: spec.SchemaProps{ Description: \"addressType specifies the type of address carried by this EndpointSlice. All addresses in this slice must be the same type. This field is immutable after creation. The following address types are currently supported: * IPv4: Represents an IPv4 Address. * IPv6: Represents an IPv6 Address. * FQDN: Represents a Fully Qualified Domain Name.nnPossible enum values:n - `\"FQDN\"` represents a FQDN.n - `\"IPv4\"` represents an IPv4 Address.n - `\"IPv6\"` represents an IPv6 Address.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", Enum:        []interface{}{\"FQDN\", \"IPv4\", \"IPv6\"}}, }, \"endpoints\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"endpoints is a list of unique endpoints in this slice. Each slice may include a maximum of 1000 endpoints.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/discovery/v1.Endpoint\"), }, }, }, }, }, \"ports\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"ports specifies the list of network ports exposed by each endpoint in this slice. Each port must have a unique name. When ports is empty, it indicates that there are no defined ports. When a port is defined with a nil port value, it indicates \"all ports\". Each slice may include a maximum of 100 ports.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/discovery/v1.EndpointPort\"), }, }, }, }, }, }, Required: []string{\"addressType\", \"endpoints\"}, }, }, Dependencies: []string{ \"k8s.io/api/discovery/v1.Endpoint\", \"k8s.io/api/discovery/v1.EndpointPort\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_discovery_v1_EndpointSliceList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EndpointSliceList represents a list of endpoint slices\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of endpoint slices\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/discovery/v1.EndpointSlice\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/discovery/v1.EndpointSlice\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_discovery_v1_ForZone(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ForZone provides information about which zones should consume this endpoint.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name represents the name of the zone.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_api_discovery_v1beta1_Endpoint(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Endpoint represents a single logical \"backend\" implementing a service.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"addresses\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"addresses of this endpoint. The contents of this field are interpreted according to the corresponding EndpointSlice addressType field. Consumers must handle different types of addresses in the context of their own capabilities. This must contain at least one address but no more than 100. These are all assumed to be fungible and clients may choose to only use the first element. Refer to: https://issue.k8s.io/106267\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"conditions\": { SchemaProps: spec.SchemaProps{ Description: \"conditions contains information about the current status of the endpoint.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/discovery/v1beta1.EndpointConditions\"), }, }, \"hostname\": { SchemaProps: spec.SchemaProps{ Description: \"hostname of this endpoint. This field may be used by consumers of endpoints to distinguish endpoints from each other (e.g. in DNS names). Multiple endpoints which use the same hostname should be considered fungible (e.g. multiple A values in DNS). Must be lowercase and pass DNS Label (RFC 1123) validation.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"targetRef\": { SchemaProps: spec.SchemaProps{ Description: \"targetRef is a reference to a Kubernetes object that represents this endpoint.\", Ref:         ref(\"k8s.io/api/core/v1.ObjectReference\"), }, }, \"topology\": { SchemaProps: spec.SchemaProps{ Description: \"topology contains arbitrary topology information associated with the endpoint. These key/value pairs must conform with the label format. https://kubernetes.io/docs/concepts/overview/working-with-objects/labels Topology may include a maximum of 16 key/value pairs. This includes, but is not limited to the following well known keys: * kubernetes.io/hostname: the value indicates the hostname of the noden  where the endpoint is located. This should match the correspondingn  node label.n* topology.kubernetes.io/zone: the value indicates the zone where then  endpoint is located. This should match the corresponding node label.n* topology.kubernetes.io/region: the value indicates the region where then  endpoint is located. This should match the corresponding node label.nThis field is deprecated and will be removed in future api versions.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"nodeName\": { SchemaProps: spec.SchemaProps{ Description: \"nodeName represents the name of the Node hosting this endpoint. This can be used to determine endpoints local to a Node. This field can be enabled with the EndpointSliceNodeName feature gate.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"hints\": { SchemaProps: spec.SchemaProps{ Description: \"hints contains information associated with how an endpoint should be consumed.\", Ref:         ref(\"k8s.io/api/discovery/v1beta1.EndpointHints\"), }, }, }, Required: []string{\"addresses\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ObjectReference\", \"k8s.io/api/discovery/v1beta1.EndpointConditions\", \"k8s.io/api/discovery/v1beta1.EndpointHints\"}, } } func schema_k8sio_api_discovery_v1beta1_EndpointConditions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EndpointConditions represents the current condition of an endpoint.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ready\": { SchemaProps: spec.SchemaProps{ Description: \"ready indicates that this endpoint is prepared to receive traffic, according to whatever system is managing the endpoint. A nil value indicates an unknown state. In most cases consumers should interpret this unknown state as ready. For compatibility reasons, ready should never be \"true\" for terminating endpoints.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"serving\": { SchemaProps: spec.SchemaProps{ Description: \"serving is identical to ready except that it is set regardless of the terminating state of endpoints. This condition should be set to true for a ready endpoint that is terminating. If nil, consumers should defer to the ready condition. This field can be enabled with the EndpointSliceTerminatingCondition feature gate.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"terminating\": { SchemaProps: spec.SchemaProps{ Description: \"terminating indicates that this endpoint is terminating. A nil value indicates an unknown state. Consumers should interpret this unknown state to mean that the endpoint is not terminating. This field can be enabled with the EndpointSliceTerminatingCondition feature gate.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_discovery_v1beta1_EndpointHints(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EndpointHints provides hints describing how an endpoint should be consumed.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"forZones\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"forZones indicates the zone(s) this endpoint should be consumed by to enable topology aware routing. May contain a maximum of 8 entries.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/discovery/v1beta1.ForZone\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/discovery/v1beta1.ForZone\"}, } } func schema_k8sio_api_discovery_v1beta1_EndpointPort(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EndpointPort represents a Port used by an EndpointSlice\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"The name of this port. All ports in an EndpointSlice must have a unique name. If the EndpointSlice is dervied from a Kubernetes service, this corresponds to the Service.ports[].name. Name must either be an empty string or pass DNS_LABEL validation: * must be no more than 63 characters long. * must consist of lower case alphanumeric characters or '-'. * must start and end with an alphanumeric character. Default is empty string.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"protocol\": { SchemaProps: spec.SchemaProps{ Description: \"The IP protocol for this port. Must be UDP, TCP, or SCTP. Default is TCP.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"port\": { SchemaProps: spec.SchemaProps{ Description: \"The port number of the endpoint. If this is not specified, ports are not restricted and must be interpreted in the context of the specific consumer.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"appProtocol\": { SchemaProps: spec.SchemaProps{ Description: \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_discovery_v1beta1_EndpointSlice(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EndpointSlice represents a subset of the endpoints that implement a service. For a given service there may be multiple EndpointSlice objects, selected by labels, which must be joined to produce the full set of endpoints.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"addressType\": { SchemaProps: spec.SchemaProps{ Description: \"addressType specifies the type of address carried by this EndpointSlice. All addresses in this slice must be the same type. This field is immutable after creation. The following address types are currently supported: * IPv4: Represents an IPv4 Address. * IPv6: Represents an IPv6 Address. * FQDN: Represents a Fully Qualified Domain Name.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"endpoints\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"endpoints is a list of unique endpoints in this slice. Each slice may include a maximum of 1000 endpoints.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/discovery/v1beta1.Endpoint\"), }, }, }, }, }, \"ports\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"ports specifies the list of network ports exposed by each endpoint in this slice. Each port must have a unique name. When ports is empty, it indicates that there are no defined ports. When a port is defined with a nil port value, it indicates \"all ports\". Each slice may include a maximum of 100 ports.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/discovery/v1beta1.EndpointPort\"), }, }, }, }, }, }, Required: []string{\"addressType\", \"endpoints\"}, }, }, Dependencies: []string{ \"k8s.io/api/discovery/v1beta1.Endpoint\", \"k8s.io/api/discovery/v1beta1.EndpointPort\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_discovery_v1beta1_EndpointSliceList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EndpointSliceList represents a list of endpoint slices\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of endpoint slices\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/discovery/v1beta1.EndpointSlice\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/discovery/v1beta1.EndpointSlice\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_discovery_v1beta1_ForZone(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ForZone provides information about which zones should consume this endpoint.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name represents the name of the zone.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_api_events_v1_Event(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Event is a report of an event somewhere in the cluster. It generally denotes some state change in the system. Events have a limited retention time and triggers and messages may evolve with time.  Event consumers should not rely on the timing of an event with a given Reason reflecting a consistent underlying trigger, or the continued existence of events with that Reason.  Events should be treated as informative, best-effort, supplemental data.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"eventTime\": { SchemaProps: spec.SchemaProps{ Description: \"eventTime is the time when this Event was first observed. It is required.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"), }, }, \"series\": { SchemaProps: spec.SchemaProps{ Description: \"series is data about the Event series this event represents or nil if it's a singleton Event.\", Ref:         ref(\"k8s.io/api/events/v1.EventSeries\"), }, }, \"reportingController\": { SchemaProps: spec.SchemaProps{ Description: \"reportingController is the name of the controller that emitted this Event, e.g. `kubernetes.io/kubelet`. This field cannot be empty for new Events.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"reportingInstance\": { SchemaProps: spec.SchemaProps{ Description: \"reportingInstance is the ID of the controller instance, e.g. `kubelet-xyzf`. This field cannot be empty for new Events and it can have at most 128 characters.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"action\": { SchemaProps: spec.SchemaProps{ Description: \"action is what action was taken/failed regarding to the regarding object. It is machine-readable. This field cannot be empty for new Events and it can have at most 128 characters.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"reason is why the action was taken. It is human-readable. This field cannot be empty for new Events and it can have at most 128 characters.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"regarding\": { SchemaProps: spec.SchemaProps{ Description: \"regarding contains the object this Event is about. In most cases it's an Object reporting controller implements, e.g. ReplicaSetController implements ReplicaSets and this event is emitted because it acts on some changes in a ReplicaSet object.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.ObjectReference\"), }, }, \"related\": { SchemaProps: spec.SchemaProps{ Description: \"related is the optional secondary object for more complex actions. E.g. when regarding object triggers a creation or deletion of related object.\", Ref:         ref(\"k8s.io/api/core/v1.ObjectReference\"), }, }, \"note\": { SchemaProps: spec.SchemaProps{ Description: \"note is a human-readable description of the status of this operation. Maximal length of the note is 1kB, but libraries should be prepared to handle values up to 64kB.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type is the type of this event (Normal, Warning), new types could be added in the future. It is machine-readable. This field cannot be empty for new Events.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"deprecatedSource\": { SchemaProps: spec.SchemaProps{ Description: \"deprecatedSource is the deprecated field assuring backward compatibility with core.v1 Event type.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.EventSource\"), }, }, \"deprecatedFirstTimestamp\": { SchemaProps: spec.SchemaProps{ Description: \"deprecatedFirstTimestamp is the deprecated field assuring backward compatibility with core.v1 Event type.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"deprecatedLastTimestamp\": { SchemaProps: spec.SchemaProps{ Description: \"deprecatedLastTimestamp is the deprecated field assuring backward compatibility with core.v1 Event type.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"deprecatedCount\": { SchemaProps: spec.SchemaProps{ Description: \"deprecatedCount is the deprecated field assuring backward compatibility with core.v1 Event type.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"eventTime\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.EventSource\", \"k8s.io/api/core/v1.ObjectReference\", \"k8s.io/api/events/v1.EventSeries\", \"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_events_v1_EventList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EventList is a list of Event objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is a list of schema objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/events/v1.Event\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/events/v1.Event\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_events_v1_EventSeries(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EventSeries contain information on series of events, i.e. thing that was/is happening continuously for some time. How often to update the EventSeries is up to the event reporters. The default event reporter in \"k8s.io/client-go/tools/events/event_broadcaster.go\" shows how this struct is updated on heartbeats and can guide customized reporter implementations.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"count\": { SchemaProps: spec.SchemaProps{ Description: \"count is the number of occurrences in this series up to the last heartbeat time.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"lastObservedTime\": { SchemaProps: spec.SchemaProps{ Description: \"lastObservedTime is the time when last Event from the series was seen before last heartbeat.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"), }, }, }, Required: []string{\"count\", \"lastObservedTime\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"}, } } func schema_k8sio_api_events_v1beta1_Event(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Event is a report of an event somewhere in the cluster. It generally denotes some state change in the system. Events have a limited retention time and triggers and messages may evolve with time.  Event consumers should not rely on the timing of an event with a given Reason reflecting a consistent underlying trigger, or the continued existence of events with that Reason.  Events should be treated as informative, best-effort, supplemental data.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"eventTime\": { SchemaProps: spec.SchemaProps{ Description: \"eventTime is the time when this Event was first observed. It is required.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"), }, }, \"series\": { SchemaProps: spec.SchemaProps{ Description: \"series is data about the Event series this event represents or nil if it's a singleton Event.\", Ref:         ref(\"k8s.io/api/events/v1beta1.EventSeries\"), }, }, \"reportingController\": { SchemaProps: spec.SchemaProps{ Description: \"reportingController is the name of the controller that emitted this Event, e.g. `kubernetes.io/kubelet`. This field cannot be empty for new Events.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"reportingInstance\": { SchemaProps: spec.SchemaProps{ Description: \"reportingInstance is the ID of the controller instance, e.g. `kubelet-xyzf`. This field cannot be empty for new Events and it can have at most 128 characters.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"action\": { SchemaProps: spec.SchemaProps{ Description: \"action is what action was taken/failed regarding to the regarding object. It is machine-readable. This field can have at most 128 characters.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"reason is why the action was taken. It is human-readable. This field can have at most 128 characters.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"regarding\": { SchemaProps: spec.SchemaProps{ Description: \"regarding contains the object this Event is about. In most cases it's an Object reporting controller implements, e.g. ReplicaSetController implements ReplicaSets and this event is emitted because it acts on some changes in a ReplicaSet object.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.ObjectReference\"), }, }, \"related\": { SchemaProps: spec.SchemaProps{ Description: \"related is the optional secondary object for more complex actions. E.g. when regarding object triggers a creation or deletion of related object.\", Ref:         ref(\"k8s.io/api/core/v1.ObjectReference\"), }, }, \"note\": { SchemaProps: spec.SchemaProps{ Description: \"note is a human-readable description of the status of this operation. Maximal length of the note is 1kB, but libraries should be prepared to handle values up to 64kB.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type is the type of this event (Normal, Warning), new types could be added in the future. It is machine-readable.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"deprecatedSource\": { SchemaProps: spec.SchemaProps{ Description: \"deprecatedSource is the deprecated field assuring backward compatibility with core.v1 Event type.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.EventSource\"), }, }, \"deprecatedFirstTimestamp\": { SchemaProps: spec.SchemaProps{ Description: \"deprecatedFirstTimestamp is the deprecated field assuring backward compatibility with core.v1 Event type.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"deprecatedLastTimestamp\": { SchemaProps: spec.SchemaProps{ Description: \"deprecatedLastTimestamp is the deprecated field assuring backward compatibility with core.v1 Event type.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"deprecatedCount\": { SchemaProps: spec.SchemaProps{ Description: \"deprecatedCount is the deprecated field assuring backward compatibility with core.v1 Event type.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"eventTime\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.EventSource\", \"k8s.io/api/core/v1.ObjectReference\", \"k8s.io/api/events/v1beta1.EventSeries\", \"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_events_v1beta1_EventList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EventList is a list of Event objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is a list of schema objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/events/v1beta1.Event\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/events/v1beta1.Event\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_events_v1beta1_EventSeries(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EventSeries contain information on series of events, i.e. thing that was/is happening continuously for some time.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"count\": { SchemaProps: spec.SchemaProps{ Description: \"count is the number of occurrences in this series up to the last heartbeat time.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"lastObservedTime\": { SchemaProps: spec.SchemaProps{ Description: \"lastObservedTime is the time when last Event from the series was seen before last heartbeat.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"), }, }, }, Required: []string{\"count\", \"lastObservedTime\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"}, } } func schema_k8sio_api_extensions_v1beta1_AllowedCSIDriver(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"AllowedCSIDriver represents a single inline CSI Driver that is allowed to be used.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the registered name of the CSI driver\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_api_extensions_v1beta1_AllowedFlexVolume(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"AllowedFlexVolume represents a single Flexvolume that is allowed to be used. Deprecated: use AllowedFlexVolume from policy API Group instead.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"driver\": { SchemaProps: spec.SchemaProps{ Description: \"driver is the name of the Flexvolume driver.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"driver\"}, }, }, } } func schema_k8sio_api_extensions_v1beta1_AllowedHostPath(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"AllowedHostPath defines the host volume conditions that will be enabled by a policy for pods to use. It requires the path prefix to be defined. Deprecated: use AllowedHostPath from policy API Group instead.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"pathPrefix\": { SchemaProps: spec.SchemaProps{ Description: \"pathPrefix is the path prefix that the host volume must match. It does not support `*`. Trailing slashes are trimmed when validating the path prefix with a host path.nnExamples: `/foo` would allow `/foo`, `/foo/` and `/foo/bar` `/foo` would not allow `/food` or `/etc/foo`\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"when set to true, will allow host volumes matching the pathPrefix only if all volume mounts are readOnly.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_extensions_v1beta1_DaemonSet(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED - This group version of DaemonSet is deprecated by apps/v1beta2/DaemonSet. See the release notes for more information. DaemonSet represents the configuration of a daemon set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"The desired behavior of this daemon set. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.DaemonSetSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"The current status of this daemon set. This data may be out of date by some window of time. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.DaemonSetStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.DaemonSetSpec\", \"k8s.io/api/extensions/v1beta1.DaemonSetStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_extensions_v1beta1_DaemonSetCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DaemonSetCondition describes the state of a DaemonSet at a certain point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of DaemonSet condition.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"Last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"The reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"A human readable message indicating details about the transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_extensions_v1beta1_DaemonSetList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DaemonSetList is a collection of daemon sets.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"A list of daemon sets.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.DaemonSet\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.DaemonSet\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_extensions_v1beta1_DaemonSetSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DaemonSetSpec is the specification of a daemon set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"A label query over pods that are managed by the daemon set. Must match in order to be controlled. If empty, defaulted to labels on Pod template. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"template\": { SchemaProps: spec.SchemaProps{ Description: \"An object that describes the pod that will be created. The DaemonSet will create exactly one copy of this pod on every node that matches the template's node selector (or on every node if no node selector is specified). More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodTemplateSpec\"), }, }, \"updateStrategy\": { SchemaProps: spec.SchemaProps{ Description: \"An update strategy to replace existing DaemonSet pods with new pods.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.DaemonSetUpdateStrategy\"), }, }, \"minReadySeconds\": { SchemaProps: spec.SchemaProps{ Description: \"The minimum number of seconds for which a newly created DaemonSet pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready).\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"templateGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED. A sequence number representing a specific generation of the template. Populated by the system. It can be set only during the creation.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"revisionHistoryLimit\": { SchemaProps: spec.SchemaProps{ Description: \"The number of old history to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. Defaults to 10.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"template\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PodTemplateSpec\", \"k8s.io/api/extensions/v1beta1.DaemonSetUpdateStrategy\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_extensions_v1beta1_DaemonSetStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DaemonSetStatus represents the current status of a daemon set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"currentNumberScheduled\": { SchemaProps: spec.SchemaProps{ Description: \"The number of nodes that are running at least 1 daemon pod and are supposed to run the daemon pod. More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"numberMisscheduled\": { SchemaProps: spec.SchemaProps{ Description: \"The number of nodes that are running the daemon pod, but are not supposed to run the daemon pod. More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"desiredNumberScheduled\": { SchemaProps: spec.SchemaProps{ Description: \"The total number of nodes that should be running the daemon pod (including nodes correctly running the daemon pod). More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"numberReady\": { SchemaProps: spec.SchemaProps{ Description: \"The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and ready.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"The most recent generation observed by the daemon set controller.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"updatedNumberScheduled\": { SchemaProps: spec.SchemaProps{ Description: \"The total number of nodes that are running updated daemon pod\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"numberAvailable\": { SchemaProps: spec.SchemaProps{ Description: \"The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and available (ready for at least spec.minReadySeconds)\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"numberUnavailable\": { SchemaProps: spec.SchemaProps{ Description: \"The number of nodes that should be running the daemon pod and have none of the daemon pod running and available (ready for at least spec.minReadySeconds)\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"collisionCount\": { SchemaProps: spec.SchemaProps{ Description: \"Count of hash collisions for the DaemonSet. The DaemonSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Represents the latest available observations of a DaemonSet's current state.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.DaemonSetCondition\"), }, }, }, }, }, }, Required: []string{\"currentNumberScheduled\", \"numberMisscheduled\", \"desiredNumberScheduled\", \"numberReady\"}, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.DaemonSetCondition\"}, } } func schema_k8sio_api_extensions_v1beta1_DaemonSetUpdateStrategy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DaemonSetUpdateStrategy indicates the strategy that the DaemonSet controller will use to perform updates. It includes any additional parameters necessary to perform the update for the indicated strategy.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of daemon set update. Can be \"RollingUpdate\" or \"OnDelete\". Default is OnDelete.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"rollingUpdate\": { SchemaProps: spec.SchemaProps{ Description: \"Rolling update config params. Present only if type = \"RollingUpdate\".\", Ref:         ref(\"k8s.io/api/extensions/v1beta1.RollingUpdateDaemonSet\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.RollingUpdateDaemonSet\"}, } } func schema_k8sio_api_extensions_v1beta1_Deployment(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED - This group version of Deployment is deprecated by apps/v1beta2/Deployment. See the release notes for more information. Deployment enables declarative updates for Pods and ReplicaSets.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the desired behavior of the Deployment.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.DeploymentSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Most recently observed status of the Deployment.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.DeploymentStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.DeploymentSpec\", \"k8s.io/api/extensions/v1beta1.DeploymentStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_extensions_v1beta1_DeploymentCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentCondition describes the state of a deployment at a certain point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of deployment condition.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastUpdateTime\": { SchemaProps: spec.SchemaProps{ Description: \"The last time this condition was updated.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"Last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"The reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"A human readable message indicating details about the transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_extensions_v1beta1_DeploymentList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentList is a list of Deployments.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of Deployments.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.Deployment\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.Deployment\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_extensions_v1beta1_DeploymentRollback(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED. DeploymentRollback stores the information required to rollback a deployment.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Required: This must match the Name of a deployment.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"updatedAnnotations\": { SchemaProps: spec.SchemaProps{ Description: \"The annotations to be updated to a deployment\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"rollbackTo\": { SchemaProps: spec.SchemaProps{ Description: \"The config of this deployment rollback.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.RollbackConfig\"), }, }, }, Required: []string{\"name\", \"rollbackTo\"}, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.RollbackConfig\"}, } } func schema_k8sio_api_extensions_v1beta1_DeploymentSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentSpec is the specification of the desired behavior of the Deployment.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"Number of desired pods. This is a pointer to distinguish between explicit zero and not specified. Defaults to 1.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"Label selector for pods. Existing ReplicaSets whose pods are selected by this will be the ones affected by this deployment.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"template\": { SchemaProps: spec.SchemaProps{ Description: \"Template describes the pods that will be created.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodTemplateSpec\"), }, }, \"strategy\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-strategy\": \"retainKeys\", }, }, SchemaProps: spec.SchemaProps{ Description: \"The deployment strategy to use to replace existing pods with new ones.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.DeploymentStrategy\"), }, }, \"minReadySeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"revisionHistoryLimit\": { SchemaProps: spec.SchemaProps{ Description: \"The number of old ReplicaSets to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. This is set to the max value of int32 (i.e. 2147483647) by default, which means \"retaining all old ReplicaSets\".\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"paused\": { SchemaProps: spec.SchemaProps{ Description: \"Indicates that the deployment is paused and will not be processed by the deployment controller.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"rollbackTo\": { SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED. The config this deployment is rolling back to. Will be cleared after rollback is done.\", Ref:         ref(\"k8s.io/api/extensions/v1beta1.RollbackConfig\"), }, }, \"progressDeadlineSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"The maximum time in seconds for a deployment to make progress before it is considered to be failed. The deployment controller will continue to process failed deployments and a condition with a ProgressDeadlineExceeded reason will be surfaced in the deployment status. Note that progress will not be estimated during the time a deployment is paused. This is set to the max value of int32 (i.e. 2147483647) by default, which means \"no deadline\".\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"template\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PodTemplateSpec\", \"k8s.io/api/extensions/v1beta1.DeploymentStrategy\", \"k8s.io/api/extensions/v1beta1.RollbackConfig\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_extensions_v1beta1_DeploymentStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentStatus is the most recently observed status of the Deployment.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"The generation observed by the deployment controller.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of non-terminated pods targeted by this deployment (their labels match the selector).\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"updatedReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of non-terminated pods targeted by this deployment that have the desired template spec.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"readyReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of ready pods targeted by this deployment.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"availableReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of available pods (ready for at least minReadySeconds) targeted by this deployment.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"unavailableReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"Total number of unavailable pods targeted by this deployment. This is the total number of pods that are still required for the deployment to have 100% available capacity. They may either be pods that are running but not yet available or pods that still have not been created.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Represents the latest available observations of a deployment's current state.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.DeploymentCondition\"), }, }, }, }, }, \"collisionCount\": { SchemaProps: spec.SchemaProps{ Description: \"Count of hash collisions for the Deployment. The Deployment controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ReplicaSet.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.DeploymentCondition\"}, } } func schema_k8sio_api_extensions_v1beta1_DeploymentStrategy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentStrategy describes how to replace existing pods with new ones.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of deployment. Can be \"Recreate\" or \"RollingUpdate\". Default is RollingUpdate.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"rollingUpdate\": { SchemaProps: spec.SchemaProps{ Description: \"Rolling update config params. Present only if DeploymentStrategyType = RollingUpdate.\", Ref:         ref(\"k8s.io/api/extensions/v1beta1.RollingUpdateDeployment\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.RollingUpdateDeployment\"}, } } func schema_k8sio_api_extensions_v1beta1_FSGroupStrategyOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FSGroupStrategyOptions defines the strategy type and options used to create the strategy. Deprecated: use FSGroupStrategyOptions from policy API Group instead.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"rule\": { SchemaProps: spec.SchemaProps{ Description: \"rule is the strategy that will dictate what FSGroup is used in the SecurityContext.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ranges\": { SchemaProps: spec.SchemaProps{ Description: \"ranges are the allowed ranges of fs groups.  If you would like to force a single fs group then supply a single range with the same start and end. Required for MustRunAs.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.IDRange\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.IDRange\"}, } } func schema_k8sio_api_extensions_v1beta1_HTTPIngressPath(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HTTPIngressPath associates a path with a backend. Incoming urls matching the path are forwarded to the backend.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"path\": { SchemaProps: spec.SchemaProps{ Description: \"Path is matched against the path of an incoming request. Currently it can contain characters disallowed from the conventional \"path\" part of a URL as defined by RFC 3986. Paths must begin with a '/'. When unspecified, all paths from incoming requests are matched.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"pathType\": { SchemaProps: spec.SchemaProps{ Description: \"PathType determines the interpretation of the Path matching. PathType can be one of the following values: * Exact: Matches the URL path exactly. * Prefix: Matches based on a URL path prefix split by '/'. Matching isn  done on a path element by element basis. A path element refers is then  list of labels in the path split by the '/' separator. A request is an  match for path p if every p is an element-wise prefix of p of then  request path. Note that if the last element of the path is a substringn  of the last element in request path, it is not a match (e.g. /foo/barn  matches /foo/bar/baz, but does not match /foo/barbaz).n* ImplementationSpecific: Interpretation of the Path matching is up ton  the IngressClass. Implementations can treat this as a separate PathTypen  or treat it identically to Prefix or Exact path types.nImplementations are required to support all path types. Defaults to ImplementationSpecific.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"backend\": { SchemaProps: spec.SchemaProps{ Description: \"Backend defines the referenced service endpoint to which the traffic will be forwarded to.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.IngressBackend\"), }, }, }, Required: []string{\"backend\"}, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.IngressBackend\"}, } } func schema_k8sio_api_extensions_v1beta1_HTTPIngressRuleValue(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HTTPIngressRuleValue is a list of http selectors pointing to backends. In the example: http://<host>/<path>?<searchpart> -> backend where where parts of the url correspond to RFC 3986, this resource will be used to match against everything after the last '/' and before the first '?' or '#'.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"paths\": { SchemaProps: spec.SchemaProps{ Description: \"A collection of paths that map requests to backends.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.HTTPIngressPath\"), }, }, }, }, }, }, Required: []string{\"paths\"}, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.HTTPIngressPath\"}, } } func schema_k8sio_api_extensions_v1beta1_HostPortRange(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HostPortRange defines a range of host ports that will be enabled by a policy for pods to use.  It requires both the start and end to be defined. Deprecated: use HostPortRange from policy API Group instead.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"min\": { SchemaProps: spec.SchemaProps{ Description: \"min is the start of the range, inclusive.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"max\": { SchemaProps: spec.SchemaProps{ Description: \"max is the end of the range, inclusive.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"min\", \"max\"}, }, }, } } func schema_k8sio_api_extensions_v1beta1_IDRange(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IDRange provides a min/max of an allowed range of IDs. Deprecated: use IDRange from policy API Group instead.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"min\": { SchemaProps: spec.SchemaProps{ Description: \"min is the start of the range, inclusive.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"max\": { SchemaProps: spec.SchemaProps{ Description: \"max is the end of the range, inclusive.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int64\", }, }, }, Required: []string{\"min\", \"max\"}, }, }, } } func schema_k8sio_api_extensions_v1beta1_IPBlock(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED 1.9 - This group version of IPBlock is deprecated by networking/v1/IPBlock. IPBlock describes a particular CIDR (Ex. \"192.168.1.1/24\",\"2001:db9::/64\") that is allowed to the pods matched by a NetworkPolicySpec's podSelector. The except entry describes CIDRs that should not be included within this rule.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"cidr\": { SchemaProps: spec.SchemaProps{ Description: \"CIDR is a string representing the IP Block Valid examples are \"192.168.1.1/24\" or \"2001:db9::/64\"\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"except\": { SchemaProps: spec.SchemaProps{ Description: \"Except is a slice of CIDRs that should not be included within an IP Block Valid examples are \"192.168.1.1/24\" or \"2001:db9::/64\" Except values will be rejected if they are outside the CIDR range\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"cidr\"}, }, }, } } func schema_k8sio_api_extensions_v1beta1_Ingress(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Ingress is a collection of rules that allow inbound connections to reach the endpoints defined by a backend. An Ingress can be configured to give services externally-reachable urls, load balance traffic, terminate SSL, offer name based virtual hosting etc. DEPRECATED - This group version of Ingress is deprecated by networking.k8s.io/v1beta1 Ingress. See the release notes for more information.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec is the desired state of the Ingress. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.IngressSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is the current state of the Ingress. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.IngressStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.IngressSpec\", \"k8s.io/api/extensions/v1beta1.IngressStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_extensions_v1beta1_IngressBackend(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressBackend describes all endpoints for a given service and port.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"serviceName\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies the name of the referenced service.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"servicePort\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies the port of the referenced service.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, \"resource\": { SchemaProps: spec.SchemaProps{ Description: \"Resource is an ObjectRef to another Kubernetes resource in the namespace of the Ingress object. If resource is specified, serviceName and servicePort must not be specified.\", Ref:         ref(\"k8s.io/api/core/v1.TypedLocalObjectReference\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.TypedLocalObjectReference\", \"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"}, } } func schema_k8sio_api_extensions_v1beta1_IngressList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressList is a collection of Ingress.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of Ingress.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.Ingress\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.Ingress\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_extensions_v1beta1_IngressRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressRule represents the rules mapping the paths under a specified host to the related backend services. Incoming requests are first evaluated for a host match, then routed to the backend associated with the matching IngressRuleValue.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"host\": { SchemaProps: spec.SchemaProps{ Description: \"Host is the fully qualified domain name of a network host, as defined by RFC 3986. Note the following deviations from the \"host\" part of the URI as defined in RFC 3986: 1. IPs are not allowed. Currently an IngressRuleValue can only apply ton   the IP in the Spec of the parent Ingress.n2. The `:` delimiter is not respected because ports are not allowed.nt  Currently the port of an Ingress is implicitly :80 for http andnt  :443 for https.nBoth these may change in the future. Incoming requests are matched against the host before the IngressRuleValue. If the host is unspecified, the Ingress routes all traffic based on the specified IngressRuleValue.nnHost can be \"precise\" which is a domain name without the terminating dot of a network host (e.g. \"foo.bar.com\") or \"wildcard\", which is a domain name prefixed with a single wildcard label (e.g. \"*.foo.com\"). The wildcard character '*' must appear by itself as the first DNS label and matches only a single label. You cannot have a wildcard label by itself (e.g. Host == \"*\"). Requests will be matched against the Host field in the following way: 1. If Host is precise, the request matches this rule if the http host header is equal to Host. 2. If Host is a wildcard, then the request matches this rule if the http host header is to equal to the suffix (removing the first label) of the wildcard rule.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"http\": { SchemaProps: spec.SchemaProps{ Description: \"http is a list of http selectors pointing to backends. A path is matched against the path of an incoming request. Currently it can contain characters disallowed from the conventional \"path\" part of a URL as defined by RFC 3986. Paths must begin with a '/'. A backend defines the referenced service endpoint to which the traffic will be forwarded to.\", Ref:         ref(\"k8s.io/api/extensions/v1beta1.HTTPIngressRuleValue\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.HTTPIngressRuleValue\"}, } } func schema_k8sio_api_extensions_v1beta1_IngressRuleValue(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressRuleValue represents a rule to apply against incoming requests. If the rule is satisfied, the request is routed to the specified backend. Currently mixing different types of rules in a single Ingress is disallowed, so exactly one of the following must be set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"http\": { SchemaProps: spec.SchemaProps{ Description: \"http is a list of http selectors pointing to backends. A path is matched against the path of an incoming request. Currently it can contain characters disallowed from the conventional \"path\" part of a URL as defined by RFC 3986. Paths must begin with a '/'. A backend defines the referenced service endpoint to which the traffic will be forwarded to.\", Ref:         ref(\"k8s.io/api/extensions/v1beta1.HTTPIngressRuleValue\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.HTTPIngressRuleValue\"}, } } func schema_k8sio_api_extensions_v1beta1_IngressSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressSpec describes the Ingress the user wishes to exist.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ingressClassName\": { SchemaProps: spec.SchemaProps{ Description: \"IngressClassName is the name of the IngressClass cluster resource. The associated IngressClass defines which controller will implement the resource. This replaces the deprecated `kubernetes.io/ingress.class` annotation. For backwards compatibility, when that annotation is set, it must be given precedence over this field. The controller may emit a warning if the field and annotation have different values. Implementations of this API should ignore Ingresses without a class specified. An IngressClass resource may be marked as default, which can be used to set a default value for this field. For more information, refer to the IngressClass documentation.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"backend\": { SchemaProps: spec.SchemaProps{ Description: \"A default backend capable of servicing requests that don't match any rule. At least one of 'backend' or 'rules' must be specified. This field is optional to allow the loadbalancer controller or defaulting logic to specify a global default.\", Ref:         ref(\"k8s.io/api/extensions/v1beta1.IngressBackend\"), }, }, \"tls\": { SchemaProps: spec.SchemaProps{ Description: \"TLS configuration. Currently the Ingress only supports a single TLS port, 443. If multiple members of this list specify different hosts, they will be multiplexed on the same port according to the hostname specified through the SNI TLS extension, if the ingress controller fulfilling the ingress supports SNI.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.IngressTLS\"), }, }, }, }, }, \"rules\": { SchemaProps: spec.SchemaProps{ Description: \"A list of host rules used to configure the Ingress. If unspecified, or no rule matches, all traffic is sent to the default backend.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.IngressRule\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.IngressBackend\", \"k8s.io/api/extensions/v1beta1.IngressRule\", \"k8s.io/api/extensions/v1beta1.IngressTLS\"}, } } func schema_k8sio_api_extensions_v1beta1_IngressStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressStatus describe the current state of the Ingress.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"loadBalancer\": { SchemaProps: spec.SchemaProps{ Description: \"LoadBalancer contains the current status of the load-balancer.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.LoadBalancerStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.LoadBalancerStatus\"}, } } func schema_k8sio_api_extensions_v1beta1_IngressTLS(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressTLS describes the transport layer security associated with an Ingress.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"hosts\": { SchemaProps: spec.SchemaProps{ Description: \"Hosts are a list of hosts included in the TLS certificate. The values in this list must match the name/s used in the tlsSecret. Defaults to the wildcard host setting for the loadbalancer controller fulfilling this Ingress, if left unspecified.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"secretName\": { SchemaProps: spec.SchemaProps{ Description: \"SecretName is the name of the secret used to terminate SSL traffic on 443. Field is left optional to allow SSL routing based on SNI hostname alone. If the SNI host in a listener conflicts with the \"Host\" header field used by an IngressRule, the SNI host is used for termination and value of the Host header is used for routing.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_extensions_v1beta1_NetworkPolicy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED 1.9 - This group version of NetworkPolicy is deprecated by networking/v1/NetworkPolicy. NetworkPolicy describes what network traffic is allowed for a set of Pods\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the desired behavior for this NetworkPolicy.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.NetworkPolicySpec\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.NetworkPolicySpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_extensions_v1beta1_NetworkPolicyEgressRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED 1.9 - This group version of NetworkPolicyEgressRule is deprecated by networking/v1/NetworkPolicyEgressRule. NetworkPolicyEgressRule describes a particular set of traffic that is allowed out of pods matched by a NetworkPolicySpec's podSelector. The traffic must match both ports and to. This type is beta-level in 1.8\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ports\": { SchemaProps: spec.SchemaProps{ Description: \"List of destination ports for outgoing traffic. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.NetworkPolicyPort\"), }, }, }, }, }, \"to\": { SchemaProps: spec.SchemaProps{ Description: \"List of destinations for outgoing traffic of pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all destinations (traffic not restricted by destination). If this field is present and contains at least one item, this rule allows traffic only if the traffic matches at least one item in the to list.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.NetworkPolicyPeer\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.NetworkPolicyPeer\", \"k8s.io/api/extensions/v1beta1.NetworkPolicyPort\"}, } } func schema_k8sio_api_extensions_v1beta1_NetworkPolicyIngressRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED 1.9 - This group version of NetworkPolicyIngressRule is deprecated by networking/v1/NetworkPolicyIngressRule. This NetworkPolicyIngressRule matches traffic if and only if the traffic matches both ports AND from.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ports\": { SchemaProps: spec.SchemaProps{ Description: \"List of ports which should be made accessible on the pods selected for this rule. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.NetworkPolicyPort\"), }, }, }, }, }, \"from\": { SchemaProps: spec.SchemaProps{ Description: \"List of sources which should be able to access the pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all sources (traffic not restricted by source). If this field is present and contains at least one item, this rule allows traffic only if the traffic matches at least one item in the from list.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.NetworkPolicyPeer\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.NetworkPolicyPeer\", \"k8s.io/api/extensions/v1beta1.NetworkPolicyPort\"}, } } func schema_k8sio_api_extensions_v1beta1_NetworkPolicyList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED 1.9 - This group version of NetworkPolicyList is deprecated by networking/v1/NetworkPolicyList. Network Policy List is a list of NetworkPolicy objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of schema objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.NetworkPolicy\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.NetworkPolicy\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_extensions_v1beta1_NetworkPolicyPeer(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED 1.9 - This group version of NetworkPolicyPeer is deprecated by networking/v1/NetworkPolicyPeer.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"podSelector\": { SchemaProps: spec.SchemaProps{ Description: \"This is a label selector which selects Pods. This field follows standard label selector semantics; if present but empty, it selects all pods.nnIf NamespaceSelector is also set, then the NetworkPolicyPeer as a whole selects the Pods matching PodSelector in the Namespaces selected by NamespaceSelector. Otherwise it selects the Pods matching PodSelector in the policy's own Namespace.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"namespaceSelector\": { SchemaProps: spec.SchemaProps{ Description: \"Selects Namespaces using cluster-scoped labels. This field follows standard label selector semantics; if present but empty, it selects all namespaces.nnIf PodSelector is also set, then the NetworkPolicyPeer as a whole selects the Pods matching PodSelector in the Namespaces selected by NamespaceSelector. Otherwise it selects all Pods in the Namespaces selected by NamespaceSelector.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"ipBlock\": { SchemaProps: spec.SchemaProps{ Description: \"IPBlock defines policy on a particular IPBlock. If this field is set then neither of the other fields can be.\", Ref:         ref(\"k8s.io/api/extensions/v1beta1.IPBlock\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.IPBlock\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_extensions_v1beta1_NetworkPolicyPort(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED 1.9 - This group version of NetworkPolicyPort is deprecated by networking/v1/NetworkPolicyPort.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"protocol\": { SchemaProps: spec.SchemaProps{ Description: \"Optional.  The protocol (TCP, UDP, or SCTP) which traffic must match. If not specified, this field defaults to TCP.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"port\": { SchemaProps: spec.SchemaProps{ Description: \"The port on the given protocol. This can either be a numerical or named port on a pod. If this field is not provided, this matches all port names and numbers. If present, only traffic on the specified protocol AND port will be matched.\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, \"endPort\": { SchemaProps: spec.SchemaProps{ Description: \"If set, indicates that the range of ports from port to endPort, inclusive, should be allowed by the policy. This field cannot be defined if the port field is not defined or if the port field is defined as a named (string) port. The endPort must be equal or greater than port. This feature is in Beta state and is enabled by default. It can be disabled using the Feature Gate \"NetworkPolicyEndPort\".\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"}, } } func schema_k8sio_api_extensions_v1beta1_NetworkPolicySpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED 1.9 - This group version of NetworkPolicySpec is deprecated by networking/v1/NetworkPolicySpec.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"podSelector\": { SchemaProps: spec.SchemaProps{ Description: \"Selects the pods to which this NetworkPolicy object applies.  The array of ingress rules is applied to any pods selected by this field. Multiple network policies can select the same set of pods.  In this case, the ingress rules for each are combined additively. This field is NOT optional and follows standard label selector semantics. An empty podSelector matches all pods in this namespace.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"ingress\": { SchemaProps: spec.SchemaProps{ Description: \"List of ingress rules to be applied to the selected pods. Traffic is allowed to a pod if there are no NetworkPolicies selecting the pod OR if the traffic source is the pod's local node, OR if the traffic matches at least one ingress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy does not allow any traffic (and serves solely to ensure that the pods it selects are isolated by default).\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.NetworkPolicyIngressRule\"), }, }, }, }, }, \"egress\": { SchemaProps: spec.SchemaProps{ Description: \"List of egress rules to be applied to the selected pods. Outgoing traffic is allowed if there are no NetworkPolicies selecting the pod (and cluster policy otherwise allows the traffic), OR if the traffic matches at least one egress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy limits all outgoing traffic (and serves solely to ensure that the pods it selects are isolated by default). This field is beta-level in 1.8\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.NetworkPolicyEgressRule\"), }, }, }, }, }, \"policyTypes\": { SchemaProps: spec.SchemaProps{ Description: \"List of rule types that the NetworkPolicy relates to. Valid options are [\"Ingress\"], [\"Egress\"], or [\"Ingress\", \"Egress\"]. If this field is not specified, it will default based on the existence of Ingress or Egress rules; policies that contain an Egress section are assumed to affect Egress, and all policies (whether or not they contain an Ingress section) are assumed to affect Ingress. If you want to write an egress-only policy, you must explicitly specify policyTypes [ \"Egress\" ]. Likewise, if you want to write a policy that specifies that no egress is allowed, you must specify a policyTypes value that include \"Egress\" (since such a policy would not include an Egress section and would otherwise default to just [ \"Ingress\" ]). This field is beta-level in 1.8\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"podSelector\"}, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.NetworkPolicyEgressRule\", \"k8s.io/api/extensions/v1beta1.NetworkPolicyIngressRule\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_extensions_v1beta1_PodSecurityPolicy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodSecurityPolicy governs the ability to make requests that affect the Security Context that will be applied to a pod and container. Deprecated: use PodSecurityPolicy from policy API Group instead.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"spec defines the policy enforced.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.PodSecurityPolicySpec\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.PodSecurityPolicySpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_extensions_v1beta1_PodSecurityPolicyList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodSecurityPolicyList is a list of PodSecurityPolicy objects. Deprecated: use PodSecurityPolicyList from policy API Group instead.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is a list of schema objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.PodSecurityPolicy\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.PodSecurityPolicy\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_extensions_v1beta1_PodSecurityPolicySpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodSecurityPolicySpec defines the policy enforced. Deprecated: use PodSecurityPolicySpec from policy API Group instead.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"privileged\": { SchemaProps: spec.SchemaProps{ Description: \"privileged determines if a pod can request to be run as privileged.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"defaultAddCapabilities\": { SchemaProps: spec.SchemaProps{ Description: \"defaultAddCapabilities is the default set of capabilities that will be added to the container unless the pod spec specifically drops the capability.  You may not list a capability in both defaultAddCapabilities and requiredDropCapabilities. Capabilities added here are implicitly allowed, and need not be included in the allowedCapabilities list.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"requiredDropCapabilities\": { SchemaProps: spec.SchemaProps{ Description: \"requiredDropCapabilities are the capabilities that will be dropped from the container.  These are required to be dropped and cannot be added.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"allowedCapabilities\": { SchemaProps: spec.SchemaProps{ Description: \"allowedCapabilities is a list of capabilities that can be requested to add to the container. Capabilities in this field may be added at the pod author's discretion. You must not list a capability in both allowedCapabilities and requiredDropCapabilities.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"volumes\": { SchemaProps: spec.SchemaProps{ Description: \"volumes is an allowlist of volume plugins. Empty indicates that no volumes may be used. To allow all volumes you may use '*'.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"hostNetwork\": { SchemaProps: spec.SchemaProps{ Description: \"hostNetwork determines if the policy allows the use of HostNetwork in the pod spec.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"hostPorts\": { SchemaProps: spec.SchemaProps{ Description: \"hostPorts determines which host port ranges are allowed to be exposed.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.HostPortRange\"), }, }, }, }, }, \"hostPID\": { SchemaProps: spec.SchemaProps{ Description: \"hostPID determines if the policy allows the use of HostPID in the pod spec.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"hostIPC\": { SchemaProps: spec.SchemaProps{ Description: \"hostIPC determines if the policy allows the use of HostIPC in the pod spec.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"seLinux\": { SchemaProps: spec.SchemaProps{ Description: \"seLinux is the strategy that will dictate the allowable labels that may be set.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.SELinuxStrategyOptions\"), }, }, \"runAsUser\": { SchemaProps: spec.SchemaProps{ Description: \"runAsUser is the strategy that will dictate the allowable RunAsUser values that may be set.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.RunAsUserStrategyOptions\"), }, }, \"runAsGroup\": { SchemaProps: spec.SchemaProps{ Description: \"RunAsGroup is the strategy that will dictate the allowable RunAsGroup values that may be set. If this field is omitted, the pod's RunAsGroup can take any value. This field requires the RunAsGroup feature gate to be enabled.\", Ref:         ref(\"k8s.io/api/extensions/v1beta1.RunAsGroupStrategyOptions\"), }, }, \"supplementalGroups\": { SchemaProps: spec.SchemaProps{ Description: \"supplementalGroups is the strategy that will dictate what supplemental groups are used by the SecurityContext.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.SupplementalGroupsStrategyOptions\"), }, }, \"fsGroup\": { SchemaProps: spec.SchemaProps{ Description: \"fsGroup is the strategy that will dictate what fs group is used by the SecurityContext.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.FSGroupStrategyOptions\"), }, }, \"readOnlyRootFilesystem\": { SchemaProps: spec.SchemaProps{ Description: \"readOnlyRootFilesystem when set to true will force containers to run with a read only root file system.  If the container specifically requests to run with a non-read only root file system the PSP should deny the pod. If set to false the container may run with a read only root file system if it wishes but it will not be forced to.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"defaultAllowPrivilegeEscalation\": { SchemaProps: spec.SchemaProps{ Description: \"defaultAllowPrivilegeEscalation controls the default setting for whether a process can gain more privileges than its parent process.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"allowPrivilegeEscalation\": { SchemaProps: spec.SchemaProps{ Description: \"allowPrivilegeEscalation determines if a pod can request to allow privilege escalation. If unspecified, defaults to true.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"allowedHostPaths\": { SchemaProps: spec.SchemaProps{ Description: \"allowedHostPaths is an allowlist of host paths. Empty indicates that all host paths may be used.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.AllowedHostPath\"), }, }, }, }, }, \"allowedFlexVolumes\": { SchemaProps: spec.SchemaProps{ Description: \"allowedFlexVolumes is an allowlist of Flexvolumes.  Empty or nil indicates that all Flexvolumes may be used.  This parameter is effective only when the usage of the Flexvolumes is allowed in the \"volumes\" field.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.AllowedFlexVolume\"), }, }, }, }, }, \"allowedCSIDrivers\": { SchemaProps: spec.SchemaProps{ Description: \"AllowedCSIDrivers is an allowlist of inline CSI drivers that must be explicitly set to be embedded within a pod spec. An empty value indicates that any CSI driver can be used for inline ephemeral volumes.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.AllowedCSIDriver\"), }, }, }, }, }, \"allowedUnsafeSysctls\": { SchemaProps: spec.SchemaProps{ Description: \"allowedUnsafeSysctls is a list of explicitly allowed unsafe sysctls, defaults to none. Each entry is either a plain sysctl name or ends in \"*\" in which case it is considered as a prefix of allowed sysctls. Single * means all unsafe sysctls are allowed. Kubelet has to allowlist all unsafe sysctls explicitly to avoid rejection.nnExamples: e.g. \"foo/*\" allows \"foo/bar\", \"foo/baz\", etc. e.g. \"foo.*\" allows \"foo.bar\", \"foo.baz\", etc.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"forbiddenSysctls\": { SchemaProps: spec.SchemaProps{ Description: \"forbiddenSysctls is a list of explicitly forbidden sysctls, defaults to none. Each entry is either a plain sysctl name or ends in \"*\" in which case it is considered as a prefix of forbidden sysctls. Single * means all sysctls are forbidden.nnExamples: e.g. \"foo/*\" forbids \"foo/bar\", \"foo/baz\", etc. e.g. \"foo.*\" forbids \"foo.bar\", \"foo.baz\", etc.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"allowedProcMountTypes\": { SchemaProps: spec.SchemaProps{ Description: \"AllowedProcMountTypes is an allowlist of allowed ProcMountTypes. Empty or nil indicates that only the DefaultProcMountType may be used. This requires the ProcMountType feature flag to be enabled.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"runtimeClass\": { SchemaProps: spec.SchemaProps{ Description: \"runtimeClass is the strategy that will dictate the allowable RuntimeClasses for a pod. If this field is omitted, the pod's runtimeClassName field is unrestricted. Enforcement of this field depends on the RuntimeClass feature gate being enabled.\", Ref:         ref(\"k8s.io/api/extensions/v1beta1.RuntimeClassStrategyOptions\"), }, }, }, Required: []string{\"seLinux\", \"runAsUser\", \"supplementalGroups\", \"fsGroup\"}, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.AllowedCSIDriver\", \"k8s.io/api/extensions/v1beta1.AllowedFlexVolume\", \"k8s.io/api/extensions/v1beta1.AllowedHostPath\", \"k8s.io/api/extensions/v1beta1.FSGroupStrategyOptions\", \"k8s.io/api/extensions/v1beta1.HostPortRange\", \"k8s.io/api/extensions/v1beta1.RunAsGroupStrategyOptions\", \"k8s.io/api/extensions/v1beta1.RunAsUserStrategyOptions\", \"k8s.io/api/extensions/v1beta1.RuntimeClassStrategyOptions\", \"k8s.io/api/extensions/v1beta1.SELinuxStrategyOptions\", \"k8s.io/api/extensions/v1beta1.SupplementalGroupsStrategyOptions\"}, } } func schema_k8sio_api_extensions_v1beta1_ReplicaSet(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED - This group version of ReplicaSet is deprecated by apps/v1beta2/ReplicaSet. See the release notes for more information. ReplicaSet ensures that a specified number of pod replicas are running at any given time.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"If the Labels of a ReplicaSet are empty, they are defaulted to be the same as the Pod(s) that the ReplicaSet manages. Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec defines the specification of the desired behavior of the ReplicaSet. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.ReplicaSetSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is the most recently observed status of the ReplicaSet. This data may be out of date by some window of time. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.ReplicaSetStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.ReplicaSetSpec\", \"k8s.io/api/extensions/v1beta1.ReplicaSetStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_extensions_v1beta1_ReplicaSetCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicaSetCondition describes the state of a replica set at a certain point.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of replica set condition.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"The last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"The reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"A human readable message indicating details about the transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_extensions_v1beta1_ReplicaSetList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicaSetList is a collection of ReplicaSets.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of ReplicaSets. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.ReplicaSet\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.ReplicaSet\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_extensions_v1beta1_ReplicaSetSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicaSetSpec is the specification of a ReplicaSet.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"Replicas is the number of desired replicas. This is a pointer to distinguish between explicit zero and unspecified. Defaults to 1. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/#what-is-a-replicationcontroller\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"minReadySeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"Selector is a label query over pods that should match the replica count. If the selector is empty, it is defaulted to the labels present on the pod template. Label keys and values that must match in order to be controlled by this replica set. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"template\": { SchemaProps: spec.SchemaProps{ Description: \"Template is the object that describes the pod that will be created if insufficient replicas are detected. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.PodTemplateSpec\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PodTemplateSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_extensions_v1beta1_ReplicaSetStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicaSetStatus represents the current status of a ReplicaSet.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"Replicas is the most recently oberved number of replicas. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/#what-is-a-replicationcontroller\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"fullyLabeledReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"The number of pods that have labels matching the labels of the pod template of the replicaset.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"readyReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"The number of ready replicas for this replica set.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"availableReplicas\": { SchemaProps: spec.SchemaProps{ Description: \"The number of available replicas (ready for at least minReadySeconds) for this replica set.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"ObservedGeneration reflects the generation of the most recently observed ReplicaSet.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Represents the latest available observations of a replica set's current state.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.ReplicaSetCondition\"), }, }, }, }, }, }, Required: []string{\"replicas\"}, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.ReplicaSetCondition\"}, } } func schema_k8sio_api_extensions_v1beta1_RollbackConfig(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"revision\": { SchemaProps: spec.SchemaProps{ Description: \"The revision to rollback to. If set to 0, rollback to the last revision.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, }, }, }, } } func schema_k8sio_api_extensions_v1beta1_RollingUpdateDaemonSet(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Spec to control the desired behavior of daemon set rolling update.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"maxUnavailable\": { SchemaProps: spec.SchemaProps{ Description: \"The maximum number of DaemonSet pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of total number of DaemonSet pods at the start of the update (ex: 10%). Absolute number is calculated from percentage by rounding up. This cannot be 0 if MaxSurge is 0 Default value is 1. Example: when this is set to 30%, at most 30% of the total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their pods stopped for an update at any given time. The update starts by stopping at most 30% of those DaemonSet pods and then brings up new DaemonSet pods in their place. Once the new pods are available, it then proceeds onto other DaemonSet pods, thus ensuring that at least 70% of original number of DaemonSet pods are available at all times during the update.\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, \"maxSurge\": { SchemaProps: spec.SchemaProps{ Description: \"The maximum number of nodes with an existing available DaemonSet pod that can have an updated DaemonSet pod during during an update. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up to a minimum of 1. Default value is 0. Example: when this is set to 30%, at most 30% of the total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their a new pod created before the old pod is marked as deleted. The update starts by launching new pods on 30% of nodes. Once an updated pod is available (Ready for at least minReadySeconds) the old DaemonSet pod on that node is marked deleted. If the old pod becomes unavailable for any reason (Ready transitions to false, is evicted, or is drained) an updated pod is immediatedly created on that node without considering surge limits. Allowing surge implies the possibility that the resources consumed by the daemonset on any given node can double if the readiness check fails, and so resource intensive daemonsets should take into account that they may cause evictions during disruption. This is an alpha field and requires enabling DaemonSetUpdateSurge feature gate.\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"}, } } func schema_k8sio_api_extensions_v1beta1_RollingUpdateDeployment(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Spec to control the desired behavior of rolling update.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"maxUnavailable\": { SchemaProps: spec.SchemaProps{ Description: \"The maximum number of pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). Absolute number is calculated from percentage by rounding down. This can not be 0 if MaxSurge is 0. By default, a fixed value of 1 is used. Example: when this is set to 30%, the old RC can be scaled down to 70% of desired pods immediately when the rolling update starts. Once new pods are ready, old RC can be scaled down further, followed by scaling up the new RC, ensuring that the total number of pods available at all times during the update is at least 70% of desired pods.\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, \"maxSurge\": { SchemaProps: spec.SchemaProps{ Description: \"The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. By default, a value of 1 is used. Example: when this is set to 30%, the new RC can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new RC can be scaled up further, ensuring that total number of pods running at any time during the update is at most 130% of desired pods.\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"}, } } func schema_k8sio_api_extensions_v1beta1_RunAsGroupStrategyOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RunAsGroupStrategyOptions defines the strategy type and any options used to create the strategy. Deprecated: use RunAsGroupStrategyOptions from policy API Group instead.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"rule\": { SchemaProps: spec.SchemaProps{ Description: \"rule is the strategy that will dictate the allowable RunAsGroup values that may be set.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ranges\": { SchemaProps: spec.SchemaProps{ Description: \"ranges are the allowed ranges of gids that may be used. If you would like to force a single gid then supply a single range with the same start and end. Required for MustRunAs.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.IDRange\"), }, }, }, }, }, }, Required: []string{\"rule\"}, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.IDRange\"}, } } func schema_k8sio_api_extensions_v1beta1_RunAsUserStrategyOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RunAsUserStrategyOptions defines the strategy type and any options used to create the strategy. Deprecated: use RunAsUserStrategyOptions from policy API Group instead.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"rule\": { SchemaProps: spec.SchemaProps{ Description: \"rule is the strategy that will dictate the allowable RunAsUser values that may be set.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ranges\": { SchemaProps: spec.SchemaProps{ Description: \"ranges are the allowed ranges of uids that may be used. If you would like to force a single uid then supply a single range with the same start and end. Required for MustRunAs.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.IDRange\"), }, }, }, }, }, }, Required: []string{\"rule\"}, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.IDRange\"}, } } func schema_k8sio_api_extensions_v1beta1_RuntimeClassStrategyOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RuntimeClassStrategyOptions define the strategy that will dictate the allowable RuntimeClasses for a pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"allowedRuntimeClassNames\": { SchemaProps: spec.SchemaProps{ Description: \"allowedRuntimeClassNames is an allowlist of RuntimeClass names that may be specified on a pod. A value of \"*\" means that any RuntimeClass name is allowed, and must be the only item in the list. An empty list requires the RuntimeClassName field to be unset.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"defaultRuntimeClassName\": { SchemaProps: spec.SchemaProps{ Description: \"defaultRuntimeClassName is the default RuntimeClassName to set on the pod. The default MUST be allowed by the allowedRuntimeClassNames list. A value of nil does not mutate the Pod.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"allowedRuntimeClassNames\"}, }, }, } } func schema_k8sio_api_extensions_v1beta1_SELinuxStrategyOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SELinuxStrategyOptions defines the strategy type and any options used to create the strategy. Deprecated: use SELinuxStrategyOptions from policy API Group instead.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"rule\": { SchemaProps: spec.SchemaProps{ Description: \"rule is the strategy that will dictate the allowable labels that may be set.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"seLinuxOptions\": { SchemaProps: spec.SchemaProps{ Description: \"seLinuxOptions required to run as; required for MustRunAs More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/\", Ref:         ref(\"k8s.io/api/core/v1.SELinuxOptions\"), }, }, }, Required: []string{\"rule\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.SELinuxOptions\"}, } } func schema_k8sio_api_extensions_v1beta1_Scale(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"represents a scaling request for a resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object metadata; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"defines the behavior of the scale. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.ScaleSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"current status of the scale. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status. Read-only.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/extensions/v1beta1.ScaleStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.ScaleSpec\", \"k8s.io/api/extensions/v1beta1.ScaleStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_extensions_v1beta1_ScaleSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"describes the attributes of a scale subresource\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"desired number of instances for the scaled object.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_k8sio_api_extensions_v1beta1_ScaleStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"represents the current status of a scale subresource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"replicas\": { SchemaProps: spec.SchemaProps{ Description: \"actual number of observed instances of the scaled object.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"selector\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"label query over pods that should match the replicas count. More info: http://kubernetes.io/docs/user-guide/labels#label-selectors\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"targetSelector\": { SchemaProps: spec.SchemaProps{ Description: \"label selector for pods that should match the replicas count. This is a serializated version of both map-based and more expressive set-based selectors. This is done to avoid introspection in the clients. The string will be in the same format as the query-param syntax. If the target type only supports map-based selectors, both this field and map-based selector field are populated. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"replicas\"}, }, }, } } func schema_k8sio_api_extensions_v1beta1_SupplementalGroupsStrategyOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SupplementalGroupsStrategyOptions defines the strategy type and options used to create the strategy. Deprecated: use SupplementalGroupsStrategyOptions from policy API Group instead.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"rule\": { SchemaProps: spec.SchemaProps{ Description: \"rule is the strategy that will dictate what supplemental groups is used in the SecurityContext.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ranges\": { SchemaProps: spec.SchemaProps{ Description: \"ranges are the allowed ranges of supplemental groups.  If you would like to force a single supplemental group then supply a single range with the same start and end. Required for MustRunAs.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/extensions/v1beta1.IDRange\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/extensions/v1beta1.IDRange\"}, } } func schema_k8sio_api_flowcontrol_v1alpha1_FlowDistinguisherMethod(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlowDistinguisherMethod specifies the method of a flow distinguisher.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"`type` is the type of flow distinguisher method The supported types are \"ByUser\" and \"ByNamespace\". Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1alpha1_FlowSchema(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlowSchema defines the schema of a group of flows. Note that a flow is made up of a set of inbound API requests with similar attributes and is identified by a pair of strings: the name of the FlowSchema and a \"flow distinguisher\".\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"`metadata` is the standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"`spec` is the specification of the desired behavior of a FlowSchema. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/flowcontrol/v1alpha1.FlowSchemaSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"`status` is the current status of a FlowSchema. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/flowcontrol/v1alpha1.FlowSchemaStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1alpha1.FlowSchemaSpec\", \"k8s.io/api/flowcontrol/v1alpha1.FlowSchemaStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_flowcontrol_v1alpha1_FlowSchemaCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlowSchemaCondition describes conditions for a FlowSchema.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"`type` is the type of the condition. Required.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"`status` is the status of the condition. Can be True, False, Unknown. Required.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"`lastTransitionTime` is the last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"`reason` is a unique, one-word, CamelCase reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"`message` is a human-readable message indicating details about last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_flowcontrol_v1alpha1_FlowSchemaList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlowSchemaList is a list of FlowSchema objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"`metadata` is the standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"`items` is a list of FlowSchemas.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1alpha1.FlowSchema\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1alpha1.FlowSchema\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_flowcontrol_v1alpha1_FlowSchemaSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlowSchemaSpec describes how the FlowSchema's specification looks like.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"priorityLevelConfiguration\": { SchemaProps: spec.SchemaProps{ Description: \"`priorityLevelConfiguration` should reference a PriorityLevelConfiguration in the cluster. If the reference cannot be resolved, the FlowSchema will be ignored and marked as invalid in its status. Required.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/flowcontrol/v1alpha1.PriorityLevelConfigurationReference\"), }, }, \"matchingPrecedence\": { SchemaProps: spec.SchemaProps{ Description: \"`matchingPrecedence` is used to choose among the FlowSchemas that match a given request. The chosen FlowSchema is among those with the numerically lowest (which we take to be logically highest) MatchingPrecedence.  Each MatchingPrecedence value must be ranged in [1,10000]. Note that if the precedence is not specified, it will be set to 1000 as default.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"distinguisherMethod\": { SchemaProps: spec.SchemaProps{ Description: \"`distinguisherMethod` defines how to compute the flow distinguisher for requests that match this schema. `nil` specifies that the distinguisher is disabled and thus will always be the empty string.\", Ref:         ref(\"k8s.io/api/flowcontrol/v1alpha1.FlowDistinguisherMethod\"), }, }, \"rules\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`rules` describes which requests will match this flow schema. This FlowSchema matches a request if and only if at least one member of rules matches the request. if it is an empty slice, there will be no requests matching the FlowSchema.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1alpha1.PolicyRulesWithSubjects\"), }, }, }, }, }, }, Required: []string{\"priorityLevelConfiguration\"}, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1alpha1.FlowDistinguisherMethod\", \"k8s.io/api/flowcontrol/v1alpha1.PolicyRulesWithSubjects\", \"k8s.io/api/flowcontrol/v1alpha1.PriorityLevelConfigurationReference\"}, } } func schema_k8sio_api_flowcontrol_v1alpha1_FlowSchemaStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlowSchemaStatus represents the current state of a FlowSchema.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"type\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`conditions` is a list of the current states of FlowSchema.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1alpha1.FlowSchemaCondition\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1alpha1.FlowSchemaCondition\"}, } } func schema_k8sio_api_flowcontrol_v1alpha1_GroupSubject(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"GroupSubject holds detailed information for group-kind subject.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the user group that matches, or \"*\" to match all user groups. See https://github.com/kubernetes/apiserver/blob/master/pkg/authentication/user/user.go for some well-known group names. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1alpha1_LimitResponse(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LimitResponse defines how to handle requests that can not be executed right now.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"`type` is \"Queue\" or \"Reject\". \"Queue\" means that requests that can not be executed upon arrival are held in a queue until they can be executed or a queuing limit is reached. \"Reject\" means that requests that can not be executed upon arrival are rejected. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"queuing\": { SchemaProps: spec.SchemaProps{ Description: \"`queuing` holds the configuration parameters for queuing. This field may be non-empty only if `type` is `\"Queue\"`.\", Ref:         ref(\"k8s.io/api/flowcontrol/v1alpha1.QueuingConfiguration\"), }, }, }, Required: []string{\"type\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-unions\": []interface{}{ map[string]interface{}{ \"discriminator\": \"type\", \"fields-to-discriminateBy\": map[string]interface{}{ \"queuing\": \"Queuing\", }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1alpha1.QueuingConfiguration\"}, } } func schema_k8sio_api_flowcontrol_v1alpha1_LimitedPriorityLevelConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LimitedPriorityLevelConfiguration specifies how to handle requests that are subject to limits. It addresses two issues:n * How are requests for this priority level limited?n * What should be done with requests that exceed the limit?\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"assuredConcurrencyShares\": { SchemaProps: spec.SchemaProps{ Description: \"`assuredConcurrencyShares` (ACS) configures the execution limit, which is a limit on the number of requests of this priority level that may be exeucting at a given time.  ACS must be a positive number. The server's concurrency limit (SCL) is divided among the concurrency-controlled priority levels in proportion to their assured concurrency shares. This produces the assured concurrency value (ACV) --- the number of requests that may be executing at a time --- for each such priority level:nn            ACV(l) = ceil( SCL * ACS(l) / ( sum[priority levels k] ACS(k) ) )nnbigger numbers of ACS mean more reserved concurrent requests (at the expense of every other PL). This field has a default value of 30.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"limitResponse\": { SchemaProps: spec.SchemaProps{ Description: \"`limitResponse` indicates what to do with requests that can not be executed right now\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/flowcontrol/v1alpha1.LimitResponse\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1alpha1.LimitResponse\"}, } } func schema_k8sio_api_flowcontrol_v1alpha1_NonResourcePolicyRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NonResourcePolicyRule is a predicate that matches non-resource requests according to their verb and the target non-resource URL. A NonResourcePolicyRule matches a request if and only if both (a) at least one member of verbs matches the request and (b) at least one member of nonResourceURLs matches the request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"verbs\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`verbs` is a list of matching verbs and may not be empty. \"*\" matches all verbs. If it is present, it must be the only entry. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"nonResourceURLs\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`nonResourceURLs` is a set of url prefixes that a user should have access to and may not be empty. For example:n  - \"/healthz\" is legaln  - \"/hea*\" is illegaln  - \"/hea\" is legal but matches nothingn  - \"/hea/*\" also matches nothingn  - \"/healthz/*\" matches all per-component health checks.n\"*\" matches all non-resource urls. if it is present, it must be the only entry. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"verbs\", \"nonResourceURLs\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1alpha1_PolicyRulesWithSubjects(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PolicyRulesWithSubjects prescribes a test that applies to a request to an apiserver. The test considers the subject making the request, the verb being requested, and the resource to be acted upon. This PolicyRulesWithSubjects matches a request if and only if both (a) at least one member of subjects matches the request and (b) at least one member of resourceRules or nonResourceRules matches the request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"subjects\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"subjects is the list of normal user, serviceaccount, or group that this rule cares about. There must be at least one member in this slice. A slice that includes both the system:authenticated and system:unauthenticated user groups matches every request. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1alpha1.Subject\"), }, }, }, }, }, \"resourceRules\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`resourceRules` is a slice of ResourcePolicyRules that identify matching requests according to their verb and the target resource. At least one of `resourceRules` and `nonResourceRules` has to be non-empty.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1alpha1.ResourcePolicyRule\"), }, }, }, }, }, \"nonResourceRules\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`nonResourceRules` is a list of NonResourcePolicyRules that identify matching requests according to their verb and the target non-resource URL.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1alpha1.NonResourcePolicyRule\"), }, }, }, }, }, }, Required: []string{\"subjects\"}, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1alpha1.NonResourcePolicyRule\", \"k8s.io/api/flowcontrol/v1alpha1.ResourcePolicyRule\", \"k8s.io/api/flowcontrol/v1alpha1.Subject\"}, } } func schema_k8sio_api_flowcontrol_v1alpha1_PriorityLevelConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityLevelConfiguration represents the configuration of a priority level.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"`metadata` is the standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"`spec` is the specification of the desired behavior of a \"request-priority\". More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/flowcontrol/v1alpha1.PriorityLevelConfigurationSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"`status` is the current status of a \"request-priority\". More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/flowcontrol/v1alpha1.PriorityLevelConfigurationStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1alpha1.PriorityLevelConfigurationSpec\", \"k8s.io/api/flowcontrol/v1alpha1.PriorityLevelConfigurationStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_flowcontrol_v1alpha1_PriorityLevelConfigurationCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityLevelConfigurationCondition defines the condition of priority level.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"`type` is the type of the condition. Required.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"`status` is the status of the condition. Can be True, False, Unknown. Required.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"`lastTransitionTime` is the last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"`reason` is a unique, one-word, CamelCase reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"`message` is a human-readable message indicating details about last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_flowcontrol_v1alpha1_PriorityLevelConfigurationList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityLevelConfigurationList is a list of PriorityLevelConfiguration objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"`metadata` is the standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"`items` is a list of request-priorities.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1alpha1.PriorityLevelConfiguration\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1alpha1.PriorityLevelConfiguration\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_flowcontrol_v1alpha1_PriorityLevelConfigurationReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityLevelConfigurationReference contains information that points to the \"request-priority\" being used.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"`name` is the name of the priority level configuration being referenced Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1alpha1_PriorityLevelConfigurationSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityLevelConfigurationSpec specifies the configuration of a priority level.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"`type` indicates whether this priority level is subject to limitation on request execution.  A value of `\"Exempt\"` means that requests of this priority level are not subject to a limit (and thus are never queued) and do not detract from the capacity made available to other priority levels.  A value of `\"Limited\"` means that (a) requests of this priority level _are_ subject to limits and (b) some of the server's limited capacity is made available exclusively to this priority level. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"limited\": { SchemaProps: spec.SchemaProps{ Description: \"`limited` specifies how requests are handled for a Limited priority level. This field must be non-empty if and only if `type` is `\"Limited\"`.\", Ref:         ref(\"k8s.io/api/flowcontrol/v1alpha1.LimitedPriorityLevelConfiguration\"), }, }, }, Required: []string{\"type\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-unions\": []interface{}{ map[string]interface{}{ \"discriminator\": \"type\", \"fields-to-discriminateBy\": map[string]interface{}{ \"limited\": \"Limited\", }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1alpha1.LimitedPriorityLevelConfiguration\"}, } } func schema_k8sio_api_flowcontrol_v1alpha1_PriorityLevelConfigurationStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityLevelConfigurationStatus represents the current state of a \"request-priority\".\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"type\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`conditions` is the current state of \"request-priority\".\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1alpha1.PriorityLevelConfigurationCondition\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1alpha1.PriorityLevelConfigurationCondition\"}, } } func schema_k8sio_api_flowcontrol_v1alpha1_QueuingConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"QueuingConfiguration holds the configuration parameters for queuing\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"queues\": { SchemaProps: spec.SchemaProps{ Description: \"`queues` is the number of queues for this priority level. The queues exist independently at each apiserver. The value must be positive.  Setting it to 1 effectively precludes shufflesharding and thus makes the distinguisher method of associated flow schemas irrelevant.  This field has a default value of 64.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"handSize\": { SchemaProps: spec.SchemaProps{ Description: \"`handSize` is a small positive number that configures the shuffle sharding of requests into queues.  When enqueuing a request at this priority level the request's flow identifier (a string pair) is hashed and the hash value is used to shuffle the list of queues and deal a hand of the size specified here.  The request is put into one of the shortest queues in that hand. `handSize` must be no larger than `queues`, and should be significantly smaller (so that a few heavy flows do not saturate most of the queues).  See the user-facing documentation for more extensive guidance on setting this field.  This field has a default value of 8.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"queueLengthLimit\": { SchemaProps: spec.SchemaProps{ Description: \"`queueLengthLimit` is the maximum number of requests allowed to be waiting in a given queue of this priority level at a time; excess requests are rejected.  This value must be positive.  If not specified, it will be defaulted to 50.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_k8sio_api_flowcontrol_v1alpha1_ResourcePolicyRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourcePolicyRule is a predicate that matches some resource requests, testing the request's verb and the target resource. A ResourcePolicyRule matches a resource request if and only if: (a) at least one member of verbs matches the request, (b) at least one member of apiGroups matches the request, (c) at least one member of resources matches the request, and (d) either (d1) the request does not specify a namespace (i.e., `Namespace==\"\"`) and clusterScope is true or (d2) the request specifies a namespace and least one member of namespaces matches the request's namespace.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"verbs\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`verbs` is a list of matching verbs and may not be empty. \"*\" matches all verbs and, if present, must be the only entry. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"apiGroups\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`apiGroups` is a list of matching API groups and may not be empty. \"*\" matches all API groups and, if present, must be the only entry. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resources\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`resources` is a list of matching resources (i.e., lowercase and plural) with, if desired, subresource.  For example, [ \"services\", \"nodes/status\" ].  This list may not be empty. \"*\" matches all resources and, if present, must be the only entry. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"clusterScope\": { SchemaProps: spec.SchemaProps{ Description: \"`clusterScope` indicates whether to match requests that do not specify a namespace (which happens either because the resource is not namespaced or the request targets all namespaces). If this field is omitted or false then the `namespaces` field must contain a non-empty list.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"namespaces\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`namespaces` is a list of target namespaces that restricts matches.  A request that specifies a target namespace matches only if either (a) this list contains that target namespace or (b) this list contains \"*\".  Note that \"*\" matches any specified namespace but does not match a request that _does not specify_ a namespace (see the `clusterScope` field for that). This list may be empty, but only if `clusterScope` is true.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"verbs\", \"apiGroups\", \"resources\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1alpha1_ServiceAccountSubject(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ServiceAccountSubject holds detailed information for service-account-kind subject.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"`namespace` is the namespace of matching ServiceAccount objects. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"`name` is the name of matching ServiceAccount objects, or \"*\" to match regardless of name. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"namespace\", \"name\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1alpha1_Subject(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Subject matches the originator of a request, as identified by the request authentication system. There are three ways of matching an originator; by user, group, or service account.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"`kind` indicates which one of the other fields is non-empty. Required\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"user\": { SchemaProps: spec.SchemaProps{ Description: \"`user` matches based on username.\", Ref:         ref(\"k8s.io/api/flowcontrol/v1alpha1.UserSubject\"), }, }, \"group\": { SchemaProps: spec.SchemaProps{ Description: \"`group` matches based on user group name.\", Ref:         ref(\"k8s.io/api/flowcontrol/v1alpha1.GroupSubject\"), }, }, \"serviceAccount\": { SchemaProps: spec.SchemaProps{ Description: \"`serviceAccount` matches ServiceAccounts.\", Ref:         ref(\"k8s.io/api/flowcontrol/v1alpha1.ServiceAccountSubject\"), }, }, }, Required: []string{\"kind\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-unions\": []interface{}{ map[string]interface{}{ \"discriminator\": \"kind\", \"fields-to-discriminateBy\": map[string]interface{}{ \"group\":          \"Group\", \"serviceAccount\": \"ServiceAccount\", \"user\":           \"User\", }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1alpha1.GroupSubject\", \"k8s.io/api/flowcontrol/v1alpha1.ServiceAccountSubject\", \"k8s.io/api/flowcontrol/v1alpha1.UserSubject\"}, } } func schema_k8sio_api_flowcontrol_v1alpha1_UserSubject(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"UserSubject holds detailed information for user-kind subject.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"`name` is the username that matches, or \"*\" to match all usernames. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1beta1_FlowDistinguisherMethod(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlowDistinguisherMethod specifies the method of a flow distinguisher.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"`type` is the type of flow distinguisher method The supported types are \"ByUser\" and \"ByNamespace\". Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1beta1_FlowSchema(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlowSchema defines the schema of a group of flows. Note that a flow is made up of a set of inbound API requests with similar attributes and is identified by a pair of strings: the name of the FlowSchema and a \"flow distinguisher\".\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"`metadata` is the standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"`spec` is the specification of the desired behavior of a FlowSchema. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/flowcontrol/v1beta1.FlowSchemaSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"`status` is the current status of a FlowSchema. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/flowcontrol/v1beta1.FlowSchemaStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta1.FlowSchemaSpec\", \"k8s.io/api/flowcontrol/v1beta1.FlowSchemaStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_flowcontrol_v1beta1_FlowSchemaCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlowSchemaCondition describes conditions for a FlowSchema.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"`type` is the type of the condition. Required.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"`status` is the status of the condition. Can be True, False, Unknown. Required.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"`lastTransitionTime` is the last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"`reason` is a unique, one-word, CamelCase reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"`message` is a human-readable message indicating details about last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_flowcontrol_v1beta1_FlowSchemaList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlowSchemaList is a list of FlowSchema objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"`metadata` is the standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"`items` is a list of FlowSchemas.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1beta1.FlowSchema\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta1.FlowSchema\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_flowcontrol_v1beta1_FlowSchemaSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlowSchemaSpec describes how the FlowSchema's specification looks like.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"priorityLevelConfiguration\": { SchemaProps: spec.SchemaProps{ Description: \"`priorityLevelConfiguration` should reference a PriorityLevelConfiguration in the cluster. If the reference cannot be resolved, the FlowSchema will be ignored and marked as invalid in its status. Required.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/flowcontrol/v1beta1.PriorityLevelConfigurationReference\"), }, }, \"matchingPrecedence\": { SchemaProps: spec.SchemaProps{ Description: \"`matchingPrecedence` is used to choose among the FlowSchemas that match a given request. The chosen FlowSchema is among those with the numerically lowest (which we take to be logically highest) MatchingPrecedence.  Each MatchingPrecedence value must be ranged in [1,10000]. Note that if the precedence is not specified, it will be set to 1000 as default.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"distinguisherMethod\": { SchemaProps: spec.SchemaProps{ Description: \"`distinguisherMethod` defines how to compute the flow distinguisher for requests that match this schema. `nil` specifies that the distinguisher is disabled and thus will always be the empty string.\", Ref:         ref(\"k8s.io/api/flowcontrol/v1beta1.FlowDistinguisherMethod\"), }, }, \"rules\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`rules` describes which requests will match this flow schema. This FlowSchema matches a request if and only if at least one member of rules matches the request. if it is an empty slice, there will be no requests matching the FlowSchema.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1beta1.PolicyRulesWithSubjects\"), }, }, }, }, }, }, Required: []string{\"priorityLevelConfiguration\"}, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta1.FlowDistinguisherMethod\", \"k8s.io/api/flowcontrol/v1beta1.PolicyRulesWithSubjects\", \"k8s.io/api/flowcontrol/v1beta1.PriorityLevelConfigurationReference\"}, } } func schema_k8sio_api_flowcontrol_v1beta1_FlowSchemaStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlowSchemaStatus represents the current state of a FlowSchema.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"type\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`conditions` is a list of the current states of FlowSchema.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1beta1.FlowSchemaCondition\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta1.FlowSchemaCondition\"}, } } func schema_k8sio_api_flowcontrol_v1beta1_GroupSubject(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"GroupSubject holds detailed information for group-kind subject.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the user group that matches, or \"*\" to match all user groups. See https://github.com/kubernetes/apiserver/blob/master/pkg/authentication/user/user.go for some well-known group names. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1beta1_LimitResponse(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LimitResponse defines how to handle requests that can not be executed right now.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"`type` is \"Queue\" or \"Reject\". \"Queue\" means that requests that can not be executed upon arrival are held in a queue until they can be executed or a queuing limit is reached. \"Reject\" means that requests that can not be executed upon arrival are rejected. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"queuing\": { SchemaProps: spec.SchemaProps{ Description: \"`queuing` holds the configuration parameters for queuing. This field may be non-empty only if `type` is `\"Queue\"`.\", Ref:         ref(\"k8s.io/api/flowcontrol/v1beta1.QueuingConfiguration\"), }, }, }, Required: []string{\"type\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-unions\": []interface{}{ map[string]interface{}{ \"discriminator\": \"type\", \"fields-to-discriminateBy\": map[string]interface{}{ \"queuing\": \"Queuing\", }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta1.QueuingConfiguration\"}, } } func schema_k8sio_api_flowcontrol_v1beta1_LimitedPriorityLevelConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LimitedPriorityLevelConfiguration specifies how to handle requests that are subject to limits. It addresses two issues:n * How are requests for this priority level limited?n * What should be done with requests that exceed the limit?\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"assuredConcurrencyShares\": { SchemaProps: spec.SchemaProps{ Description: \"`assuredConcurrencyShares` (ACS) configures the execution limit, which is a limit on the number of requests of this priority level that may be exeucting at a given time.  ACS must be a positive number. The server's concurrency limit (SCL) is divided among the concurrency-controlled priority levels in proportion to their assured concurrency shares. This produces the assured concurrency value (ACV) --- the number of requests that may be executing at a time --- for each such priority level:nn            ACV(l) = ceil( SCL * ACS(l) / ( sum[priority levels k] ACS(k) ) )nnbigger numbers of ACS mean more reserved concurrent requests (at the expense of every other PL). This field has a default value of 30.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"limitResponse\": { SchemaProps: spec.SchemaProps{ Description: \"`limitResponse` indicates what to do with requests that can not be executed right now\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/flowcontrol/v1beta1.LimitResponse\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta1.LimitResponse\"}, } } func schema_k8sio_api_flowcontrol_v1beta1_NonResourcePolicyRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NonResourcePolicyRule is a predicate that matches non-resource requests according to their verb and the target non-resource URL. A NonResourcePolicyRule matches a request if and only if both (a) at least one member of verbs matches the request and (b) at least one member of nonResourceURLs matches the request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"verbs\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`verbs` is a list of matching verbs and may not be empty. \"*\" matches all verbs. If it is present, it must be the only entry. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"nonResourceURLs\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`nonResourceURLs` is a set of url prefixes that a user should have access to and may not be empty. For example:n  - \"/healthz\" is legaln  - \"/hea*\" is illegaln  - \"/hea\" is legal but matches nothingn  - \"/hea/*\" also matches nothingn  - \"/healthz/*\" matches all per-component health checks.n\"*\" matches all non-resource urls. if it is present, it must be the only entry. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"verbs\", \"nonResourceURLs\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1beta1_PolicyRulesWithSubjects(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PolicyRulesWithSubjects prescribes a test that applies to a request to an apiserver. The test considers the subject making the request, the verb being requested, and the resource to be acted upon. This PolicyRulesWithSubjects matches a request if and only if both (a) at least one member of subjects matches the request and (b) at least one member of resourceRules or nonResourceRules matches the request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"subjects\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"subjects is the list of normal user, serviceaccount, or group that this rule cares about. There must be at least one member in this slice. A slice that includes both the system:authenticated and system:unauthenticated user groups matches every request. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1beta1.Subject\"), }, }, }, }, }, \"resourceRules\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`resourceRules` is a slice of ResourcePolicyRules that identify matching requests according to their verb and the target resource. At least one of `resourceRules` and `nonResourceRules` has to be non-empty.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1beta1.ResourcePolicyRule\"), }, }, }, }, }, \"nonResourceRules\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`nonResourceRules` is a list of NonResourcePolicyRules that identify matching requests according to their verb and the target non-resource URL.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1beta1.NonResourcePolicyRule\"), }, }, }, }, }, }, Required: []string{\"subjects\"}, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta1.NonResourcePolicyRule\", \"k8s.io/api/flowcontrol/v1beta1.ResourcePolicyRule\", \"k8s.io/api/flowcontrol/v1beta1.Subject\"}, } } func schema_k8sio_api_flowcontrol_v1beta1_PriorityLevelConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityLevelConfiguration represents the configuration of a priority level.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"`metadata` is the standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"`spec` is the specification of the desired behavior of a \"request-priority\". More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/flowcontrol/v1beta1.PriorityLevelConfigurationSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"`status` is the current status of a \"request-priority\". More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/flowcontrol/v1beta1.PriorityLevelConfigurationStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta1.PriorityLevelConfigurationSpec\", \"k8s.io/api/flowcontrol/v1beta1.PriorityLevelConfigurationStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_flowcontrol_v1beta1_PriorityLevelConfigurationCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityLevelConfigurationCondition defines the condition of priority level.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"`type` is the type of the condition. Required.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"`status` is the status of the condition. Can be True, False, Unknown. Required.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"`lastTransitionTime` is the last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"`reason` is a unique, one-word, CamelCase reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"`message` is a human-readable message indicating details about last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_flowcontrol_v1beta1_PriorityLevelConfigurationList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityLevelConfigurationList is a list of PriorityLevelConfiguration objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"`metadata` is the standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"`items` is a list of request-priorities.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1beta1.PriorityLevelConfiguration\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta1.PriorityLevelConfiguration\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_flowcontrol_v1beta1_PriorityLevelConfigurationReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityLevelConfigurationReference contains information that points to the \"request-priority\" being used.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"`name` is the name of the priority level configuration being referenced Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1beta1_PriorityLevelConfigurationSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityLevelConfigurationSpec specifies the configuration of a priority level.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"`type` indicates whether this priority level is subject to limitation on request execution.  A value of `\"Exempt\"` means that requests of this priority level are not subject to a limit (and thus are never queued) and do not detract from the capacity made available to other priority levels.  A value of `\"Limited\"` means that (a) requests of this priority level _are_ subject to limits and (b) some of the server's limited capacity is made available exclusively to this priority level. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"limited\": { SchemaProps: spec.SchemaProps{ Description: \"`limited` specifies how requests are handled for a Limited priority level. This field must be non-empty if and only if `type` is `\"Limited\"`.\", Ref:         ref(\"k8s.io/api/flowcontrol/v1beta1.LimitedPriorityLevelConfiguration\"), }, }, }, Required: []string{\"type\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-unions\": []interface{}{ map[string]interface{}{ \"discriminator\": \"type\", \"fields-to-discriminateBy\": map[string]interface{}{ \"limited\": \"Limited\", }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta1.LimitedPriorityLevelConfiguration\"}, } } func schema_k8sio_api_flowcontrol_v1beta1_PriorityLevelConfigurationStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityLevelConfigurationStatus represents the current state of a \"request-priority\".\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"type\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`conditions` is the current state of \"request-priority\".\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1beta1.PriorityLevelConfigurationCondition\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta1.PriorityLevelConfigurationCondition\"}, } } func schema_k8sio_api_flowcontrol_v1beta1_QueuingConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"QueuingConfiguration holds the configuration parameters for queuing\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"queues\": { SchemaProps: spec.SchemaProps{ Description: \"`queues` is the number of queues for this priority level. The queues exist independently at each apiserver. The value must be positive.  Setting it to 1 effectively precludes shufflesharding and thus makes the distinguisher method of associated flow schemas irrelevant.  This field has a default value of 64.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"handSize\": { SchemaProps: spec.SchemaProps{ Description: \"`handSize` is a small positive number that configures the shuffle sharding of requests into queues.  When enqueuing a request at this priority level the request's flow identifier (a string pair) is hashed and the hash value is used to shuffle the list of queues and deal a hand of the size specified here.  The request is put into one of the shortest queues in that hand. `handSize` must be no larger than `queues`, and should be significantly smaller (so that a few heavy flows do not saturate most of the queues).  See the user-facing documentation for more extensive guidance on setting this field.  This field has a default value of 8.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"queueLengthLimit\": { SchemaProps: spec.SchemaProps{ Description: \"`queueLengthLimit` is the maximum number of requests allowed to be waiting in a given queue of this priority level at a time; excess requests are rejected.  This value must be positive.  If not specified, it will be defaulted to 50.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_k8sio_api_flowcontrol_v1beta1_ResourcePolicyRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourcePolicyRule is a predicate that matches some resource requests, testing the request's verb and the target resource. A ResourcePolicyRule matches a resource request if and only if: (a) at least one member of verbs matches the request, (b) at least one member of apiGroups matches the request, (c) at least one member of resources matches the request, and (d) either (d1) the request does not specify a namespace (i.e., `Namespace==\"\"`) and clusterScope is true or (d2) the request specifies a namespace and least one member of namespaces matches the request's namespace.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"verbs\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`verbs` is a list of matching verbs and may not be empty. \"*\" matches all verbs and, if present, must be the only entry. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"apiGroups\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`apiGroups` is a list of matching API groups and may not be empty. \"*\" matches all API groups and, if present, must be the only entry. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resources\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`resources` is a list of matching resources (i.e., lowercase and plural) with, if desired, subresource.  For example, [ \"services\", \"nodes/status\" ].  This list may not be empty. \"*\" matches all resources and, if present, must be the only entry. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"clusterScope\": { SchemaProps: spec.SchemaProps{ Description: \"`clusterScope` indicates whether to match requests that do not specify a namespace (which happens either because the resource is not namespaced or the request targets all namespaces). If this field is omitted or false then the `namespaces` field must contain a non-empty list.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"namespaces\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`namespaces` is a list of target namespaces that restricts matches.  A request that specifies a target namespace matches only if either (a) this list contains that target namespace or (b) this list contains \"*\".  Note that \"*\" matches any specified namespace but does not match a request that _does not specify_ a namespace (see the `clusterScope` field for that). This list may be empty, but only if `clusterScope` is true.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"verbs\", \"apiGroups\", \"resources\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1beta1_ServiceAccountSubject(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ServiceAccountSubject holds detailed information for service-account-kind subject.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"`namespace` is the namespace of matching ServiceAccount objects. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"`name` is the name of matching ServiceAccount objects, or \"*\" to match regardless of name. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"namespace\", \"name\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1beta1_Subject(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Subject matches the originator of a request, as identified by the request authentication system. There are three ways of matching an originator; by user, group, or service account.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"`kind` indicates which one of the other fields is non-empty. Required\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"user\": { SchemaProps: spec.SchemaProps{ Description: \"`user` matches based on username.\", Ref:         ref(\"k8s.io/api/flowcontrol/v1beta1.UserSubject\"), }, }, \"group\": { SchemaProps: spec.SchemaProps{ Description: \"`group` matches based on user group name.\", Ref:         ref(\"k8s.io/api/flowcontrol/v1beta1.GroupSubject\"), }, }, \"serviceAccount\": { SchemaProps: spec.SchemaProps{ Description: \"`serviceAccount` matches ServiceAccounts.\", Ref:         ref(\"k8s.io/api/flowcontrol/v1beta1.ServiceAccountSubject\"), }, }, }, Required: []string{\"kind\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-unions\": []interface{}{ map[string]interface{}{ \"discriminator\": \"kind\", \"fields-to-discriminateBy\": map[string]interface{}{ \"group\":          \"Group\", \"serviceAccount\": \"ServiceAccount\", \"user\":           \"User\", }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta1.GroupSubject\", \"k8s.io/api/flowcontrol/v1beta1.ServiceAccountSubject\", \"k8s.io/api/flowcontrol/v1beta1.UserSubject\"}, } } func schema_k8sio_api_flowcontrol_v1beta1_UserSubject(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"UserSubject holds detailed information for user-kind subject.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"`name` is the username that matches, or \"*\" to match all usernames. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1beta2_FlowDistinguisherMethod(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlowDistinguisherMethod specifies the method of a flow distinguisher.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"`type` is the type of flow distinguisher method The supported types are \"ByUser\" and \"ByNamespace\". Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1beta2_FlowSchema(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlowSchema defines the schema of a group of flows. Note that a flow is made up of a set of inbound API requests with similar attributes and is identified by a pair of strings: the name of the FlowSchema and a \"flow distinguisher\".\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"`metadata` is the standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"`spec` is the specification of the desired behavior of a FlowSchema. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/flowcontrol/v1beta2.FlowSchemaSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"`status` is the current status of a FlowSchema. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/flowcontrol/v1beta2.FlowSchemaStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta2.FlowSchemaSpec\", \"k8s.io/api/flowcontrol/v1beta2.FlowSchemaStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_flowcontrol_v1beta2_FlowSchemaCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlowSchemaCondition describes conditions for a FlowSchema.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"`type` is the type of the condition. Required.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"`status` is the status of the condition. Can be True, False, Unknown. Required.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"`lastTransitionTime` is the last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"`reason` is a unique, one-word, CamelCase reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"`message` is a human-readable message indicating details about last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_flowcontrol_v1beta2_FlowSchemaList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlowSchemaList is a list of FlowSchema objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"`metadata` is the standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"`items` is a list of FlowSchemas.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1beta2.FlowSchema\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta2.FlowSchema\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_flowcontrol_v1beta2_FlowSchemaSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlowSchemaSpec describes how the FlowSchema's specification looks like.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"priorityLevelConfiguration\": { SchemaProps: spec.SchemaProps{ Description: \"`priorityLevelConfiguration` should reference a PriorityLevelConfiguration in the cluster. If the reference cannot be resolved, the FlowSchema will be ignored and marked as invalid in its status. Required.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/flowcontrol/v1beta2.PriorityLevelConfigurationReference\"), }, }, \"matchingPrecedence\": { SchemaProps: spec.SchemaProps{ Description: \"`matchingPrecedence` is used to choose among the FlowSchemas that match a given request. The chosen FlowSchema is among those with the numerically lowest (which we take to be logically highest) MatchingPrecedence.  Each MatchingPrecedence value must be ranged in [1,10000]. Note that if the precedence is not specified, it will be set to 1000 as default.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"distinguisherMethod\": { SchemaProps: spec.SchemaProps{ Description: \"`distinguisherMethod` defines how to compute the flow distinguisher for requests that match this schema. `nil` specifies that the distinguisher is disabled and thus will always be the empty string.\", Ref:         ref(\"k8s.io/api/flowcontrol/v1beta2.FlowDistinguisherMethod\"), }, }, \"rules\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`rules` describes which requests will match this flow schema. This FlowSchema matches a request if and only if at least one member of rules matches the request. if it is an empty slice, there will be no requests matching the FlowSchema.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1beta2.PolicyRulesWithSubjects\"), }, }, }, }, }, }, Required: []string{\"priorityLevelConfiguration\"}, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta2.FlowDistinguisherMethod\", \"k8s.io/api/flowcontrol/v1beta2.PolicyRulesWithSubjects\", \"k8s.io/api/flowcontrol/v1beta2.PriorityLevelConfigurationReference\"}, } } func schema_k8sio_api_flowcontrol_v1beta2_FlowSchemaStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FlowSchemaStatus represents the current state of a FlowSchema.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"type\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`conditions` is a list of the current states of FlowSchema.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1beta2.FlowSchemaCondition\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta2.FlowSchemaCondition\"}, } } func schema_k8sio_api_flowcontrol_v1beta2_GroupSubject(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"GroupSubject holds detailed information for group-kind subject.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the user group that matches, or \"*\" to match all user groups. See https://github.com/kubernetes/apiserver/blob/master/pkg/authentication/user/user.go for some well-known group names. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1beta2_LimitResponse(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LimitResponse defines how to handle requests that can not be executed right now.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"`type` is \"Queue\" or \"Reject\". \"Queue\" means that requests that can not be executed upon arrival are held in a queue until they can be executed or a queuing limit is reached. \"Reject\" means that requests that can not be executed upon arrival are rejected. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"queuing\": { SchemaProps: spec.SchemaProps{ Description: \"`queuing` holds the configuration parameters for queuing. This field may be non-empty only if `type` is `\"Queue\"`.\", Ref:         ref(\"k8s.io/api/flowcontrol/v1beta2.QueuingConfiguration\"), }, }, }, Required: []string{\"type\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-unions\": []interface{}{ map[string]interface{}{ \"discriminator\": \"type\", \"fields-to-discriminateBy\": map[string]interface{}{ \"queuing\": \"Queuing\", }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta2.QueuingConfiguration\"}, } } func schema_k8sio_api_flowcontrol_v1beta2_LimitedPriorityLevelConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LimitedPriorityLevelConfiguration specifies how to handle requests that are subject to limits. It addresses two issues:n * How are requests for this priority level limited?n * What should be done with requests that exceed the limit?\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"assuredConcurrencyShares\": { SchemaProps: spec.SchemaProps{ Description: \"`assuredConcurrencyShares` (ACS) configures the execution limit, which is a limit on the number of requests of this priority level that may be exeucting at a given time.  ACS must be a positive number. The server's concurrency limit (SCL) is divided among the concurrency-controlled priority levels in proportion to their assured concurrency shares. This produces the assured concurrency value (ACV) --- the number of requests that may be executing at a time --- for each such priority level:nn            ACV(l) = ceil( SCL * ACS(l) / ( sum[priority levels k] ACS(k) ) )nnbigger numbers of ACS mean more reserved concurrent requests (at the expense of every other PL). This field has a default value of 30.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"limitResponse\": { SchemaProps: spec.SchemaProps{ Description: \"`limitResponse` indicates what to do with requests that can not be executed right now\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/flowcontrol/v1beta2.LimitResponse\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta2.LimitResponse\"}, } } func schema_k8sio_api_flowcontrol_v1beta2_NonResourcePolicyRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NonResourcePolicyRule is a predicate that matches non-resource requests according to their verb and the target non-resource URL. A NonResourcePolicyRule matches a request if and only if both (a) at least one member of verbs matches the request and (b) at least one member of nonResourceURLs matches the request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"verbs\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`verbs` is a list of matching verbs and may not be empty. \"*\" matches all verbs. If it is present, it must be the only entry. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"nonResourceURLs\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`nonResourceURLs` is a set of url prefixes that a user should have access to and may not be empty. For example:n  - \"/healthz\" is legaln  - \"/hea*\" is illegaln  - \"/hea\" is legal but matches nothingn  - \"/hea/*\" also matches nothingn  - \"/healthz/*\" matches all per-component health checks.n\"*\" matches all non-resource urls. if it is present, it must be the only entry. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"verbs\", \"nonResourceURLs\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1beta2_PolicyRulesWithSubjects(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PolicyRulesWithSubjects prescribes a test that applies to a request to an apiserver. The test considers the subject making the request, the verb being requested, and the resource to be acted upon. This PolicyRulesWithSubjects matches a request if and only if both (a) at least one member of subjects matches the request and (b) at least one member of resourceRules or nonResourceRules matches the request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"subjects\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"subjects is the list of normal user, serviceaccount, or group that this rule cares about. There must be at least one member in this slice. A slice that includes both the system:authenticated and system:unauthenticated user groups matches every request. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1beta2.Subject\"), }, }, }, }, }, \"resourceRules\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`resourceRules` is a slice of ResourcePolicyRules that identify matching requests according to their verb and the target resource. At least one of `resourceRules` and `nonResourceRules` has to be non-empty.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1beta2.ResourcePolicyRule\"), }, }, }, }, }, \"nonResourceRules\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`nonResourceRules` is a list of NonResourcePolicyRules that identify matching requests according to their verb and the target non-resource URL.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1beta2.NonResourcePolicyRule\"), }, }, }, }, }, }, Required: []string{\"subjects\"}, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta2.NonResourcePolicyRule\", \"k8s.io/api/flowcontrol/v1beta2.ResourcePolicyRule\", \"k8s.io/api/flowcontrol/v1beta2.Subject\"}, } } func schema_k8sio_api_flowcontrol_v1beta2_PriorityLevelConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityLevelConfiguration represents the configuration of a priority level.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"`metadata` is the standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"`spec` is the specification of the desired behavior of a \"request-priority\". More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/flowcontrol/v1beta2.PriorityLevelConfigurationSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"`status` is the current status of a \"request-priority\". More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/flowcontrol/v1beta2.PriorityLevelConfigurationStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta2.PriorityLevelConfigurationSpec\", \"k8s.io/api/flowcontrol/v1beta2.PriorityLevelConfigurationStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_flowcontrol_v1beta2_PriorityLevelConfigurationCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityLevelConfigurationCondition defines the condition of priority level.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"`type` is the type of the condition. Required.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"`status` is the status of the condition. Can be True, False, Unknown. Required.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"`lastTransitionTime` is the last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"`reason` is a unique, one-word, CamelCase reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"`message` is a human-readable message indicating details about last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_flowcontrol_v1beta2_PriorityLevelConfigurationList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityLevelConfigurationList is a list of PriorityLevelConfiguration objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"`metadata` is the standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"`items` is a list of request-priorities.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1beta2.PriorityLevelConfiguration\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta2.PriorityLevelConfiguration\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_flowcontrol_v1beta2_PriorityLevelConfigurationReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityLevelConfigurationReference contains information that points to the \"request-priority\" being used.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"`name` is the name of the priority level configuration being referenced Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1beta2_PriorityLevelConfigurationSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityLevelConfigurationSpec specifies the configuration of a priority level.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"`type` indicates whether this priority level is subject to limitation on request execution.  A value of `\"Exempt\"` means that requests of this priority level are not subject to a limit (and thus are never queued) and do not detract from the capacity made available to other priority levels.  A value of `\"Limited\"` means that (a) requests of this priority level _are_ subject to limits and (b) some of the server's limited capacity is made available exclusively to this priority level. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"limited\": { SchemaProps: spec.SchemaProps{ Description: \"`limited` specifies how requests are handled for a Limited priority level. This field must be non-empty if and only if `type` is `\"Limited\"`.\", Ref:         ref(\"k8s.io/api/flowcontrol/v1beta2.LimitedPriorityLevelConfiguration\"), }, }, }, Required: []string{\"type\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-unions\": []interface{}{ map[string]interface{}{ \"discriminator\": \"type\", \"fields-to-discriminateBy\": map[string]interface{}{ \"limited\": \"Limited\", }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta2.LimitedPriorityLevelConfiguration\"}, } } func schema_k8sio_api_flowcontrol_v1beta2_PriorityLevelConfigurationStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityLevelConfigurationStatus represents the current state of a \"request-priority\".\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"type\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`conditions` is the current state of \"request-priority\".\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/flowcontrol/v1beta2.PriorityLevelConfigurationCondition\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta2.PriorityLevelConfigurationCondition\"}, } } func schema_k8sio_api_flowcontrol_v1beta2_QueuingConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"QueuingConfiguration holds the configuration parameters for queuing\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"queues\": { SchemaProps: spec.SchemaProps{ Description: \"`queues` is the number of queues for this priority level. The queues exist independently at each apiserver. The value must be positive.  Setting it to 1 effectively precludes shufflesharding and thus makes the distinguisher method of associated flow schemas irrelevant.  This field has a default value of 64.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"handSize\": { SchemaProps: spec.SchemaProps{ Description: \"`handSize` is a small positive number that configures the shuffle sharding of requests into queues.  When enqueuing a request at this priority level the request's flow identifier (a string pair) is hashed and the hash value is used to shuffle the list of queues and deal a hand of the size specified here.  The request is put into one of the shortest queues in that hand. `handSize` must be no larger than `queues`, and should be significantly smaller (so that a few heavy flows do not saturate most of the queues).  See the user-facing documentation for more extensive guidance on setting this field.  This field has a default value of 8.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"queueLengthLimit\": { SchemaProps: spec.SchemaProps{ Description: \"`queueLengthLimit` is the maximum number of requests allowed to be waiting in a given queue of this priority level at a time; excess requests are rejected.  This value must be positive.  If not specified, it will be defaulted to 50.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_k8sio_api_flowcontrol_v1beta2_ResourcePolicyRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourcePolicyRule is a predicate that matches some resource requests, testing the request's verb and the target resource. A ResourcePolicyRule matches a resource request if and only if: (a) at least one member of verbs matches the request, (b) at least one member of apiGroups matches the request, (c) at least one member of resources matches the request, and (d) either (d1) the request does not specify a namespace (i.e., `Namespace==\"\"`) and clusterScope is true or (d2) the request specifies a namespace and least one member of namespaces matches the request's namespace.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"verbs\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`verbs` is a list of matching verbs and may not be empty. \"*\" matches all verbs and, if present, must be the only entry. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"apiGroups\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`apiGroups` is a list of matching API groups and may not be empty. \"*\" matches all API groups and, if present, must be the only entry. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resources\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`resources` is a list of matching resources (i.e., lowercase and plural) with, if desired, subresource.  For example, [ \"services\", \"nodes/status\" ].  This list may not be empty. \"*\" matches all resources and, if present, must be the only entry. Required.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"clusterScope\": { SchemaProps: spec.SchemaProps{ Description: \"`clusterScope` indicates whether to match requests that do not specify a namespace (which happens either because the resource is not namespaced or the request targets all namespaces). If this field is omitted or false then the `namespaces` field must contain a non-empty list.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"namespaces\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"`namespaces` is a list of target namespaces that restricts matches.  A request that specifies a target namespace matches only if either (a) this list contains that target namespace or (b) this list contains \"*\".  Note that \"*\" matches any specified namespace but does not match a request that _does not specify_ a namespace (see the `clusterScope` field for that). This list may be empty, but only if `clusterScope` is true.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"verbs\", \"apiGroups\", \"resources\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1beta2_ServiceAccountSubject(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ServiceAccountSubject holds detailed information for service-account-kind subject.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"`namespace` is the namespace of matching ServiceAccount objects. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"`name` is the name of matching ServiceAccount objects, or \"*\" to match regardless of name. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"namespace\", \"name\"}, }, }, } } func schema_k8sio_api_flowcontrol_v1beta2_Subject(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Subject matches the originator of a request, as identified by the request authentication system. There are three ways of matching an originator; by user, group, or service account.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"`kind` indicates which one of the other fields is non-empty. Required\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"user\": { SchemaProps: spec.SchemaProps{ Description: \"`user` matches based on username.\", Ref:         ref(\"k8s.io/api/flowcontrol/v1beta2.UserSubject\"), }, }, \"group\": { SchemaProps: spec.SchemaProps{ Description: \"`group` matches based on user group name.\", Ref:         ref(\"k8s.io/api/flowcontrol/v1beta2.GroupSubject\"), }, }, \"serviceAccount\": { SchemaProps: spec.SchemaProps{ Description: \"`serviceAccount` matches ServiceAccounts.\", Ref:         ref(\"k8s.io/api/flowcontrol/v1beta2.ServiceAccountSubject\"), }, }, }, Required: []string{\"kind\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-unions\": []interface{}{ map[string]interface{}{ \"discriminator\": \"kind\", \"fields-to-discriminateBy\": map[string]interface{}{ \"group\":          \"Group\", \"serviceAccount\": \"ServiceAccount\", \"user\":           \"User\", }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/flowcontrol/v1beta2.GroupSubject\", \"k8s.io/api/flowcontrol/v1beta2.ServiceAccountSubject\", \"k8s.io/api/flowcontrol/v1beta2.UserSubject\"}, } } func schema_k8sio_api_flowcontrol_v1beta2_UserSubject(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"UserSubject holds detailed information for user-kind subject.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"`name` is the username that matches, or \"*\" to match all usernames. Required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_api_imagepolicy_v1alpha1_ImageReview(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ImageReview checks if the set of images in a pod are allowed.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec holds information about the pod being evaluated\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/imagepolicy/v1alpha1.ImageReviewSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is filled in by the backend and indicates whether the pod should be allowed.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/imagepolicy/v1alpha1.ImageReviewStatus\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/imagepolicy/v1alpha1.ImageReviewSpec\", \"k8s.io/api/imagepolicy/v1alpha1.ImageReviewStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_imagepolicy_v1alpha1_ImageReviewContainerSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ImageReviewContainerSpec is a description of a container within the pod creation request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"image\": { SchemaProps: spec.SchemaProps{ Description: \"This can be in the form image:tag or image@SHA:012345679abcdef.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_imagepolicy_v1alpha1_ImageReviewSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ImageReviewSpec is a description of the pod creation request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"containers\": { SchemaProps: spec.SchemaProps{ Description: \"Containers is a list of a subset of the information in each container of the Pod being created.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/imagepolicy/v1alpha1.ImageReviewContainerSpec\"), }, }, }, }, }, \"annotations\": { SchemaProps: spec.SchemaProps{ Description: \"Annotations is a list of key-value pairs extracted from the Pod's annotations. It only includes keys which match the pattern `*.image-policy.k8s.io/*`. It is up to each webhook backend to determine how to interpret these annotations, if at all.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"Namespace is the namespace the pod is being created in.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/imagepolicy/v1alpha1.ImageReviewContainerSpec\"}, } } func schema_k8sio_api_imagepolicy_v1alpha1_ImageReviewStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ImageReviewStatus is the result of the review for the pod creation request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"allowed\": { SchemaProps: spec.SchemaProps{ Description: \"Allowed indicates that all images were allowed to be run.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"Reason should be empty unless Allowed is false in which case it may contain a short description of what is wrong.  Kubernetes may truncate excessively long errors when displaying to the user.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"auditAnnotations\": { SchemaProps: spec.SchemaProps{ Description: \"AuditAnnotations will be added to the attributes object of the admission controller request using 'AddAnnotation'.  The keys should be prefix-less (i.e., the admission controller will add an appropriate prefix).\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"allowed\"}, }, }, } } func schema_k8sio_api_networking_v1_HTTPIngressPath(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HTTPIngressPath associates a path with a backend. Incoming urls matching the path are forwarded to the backend.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"path\": { SchemaProps: spec.SchemaProps{ Description: \"Path is matched against the path of an incoming request. Currently it can contain characters disallowed from the conventional \"path\" part of a URL as defined by RFC 3986. Paths must begin with a '/' and must be present when using PathType with value \"Exact\" or \"Prefix\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"pathType\": { SchemaProps: spec.SchemaProps{ Description: \"PathType determines the interpretation of the Path matching. PathType can be one of the following values: * Exact: Matches the URL path exactly. * Prefix: Matches based on a URL path prefix split by '/'. Matching isn  done on a path element by element basis. A path element refers is then  list of labels in the path split by the '/' separator. A request is an  match for path p if every p is an element-wise prefix of p of then  request path. Note that if the last element of the path is a substringn  of the last element in request path, it is not a match (e.g. /foo/barn  matches /foo/bar/baz, but does not match /foo/barbaz).n* ImplementationSpecific: Interpretation of the Path matching is up ton  the IngressClass. Implementations can treat this as a separate PathTypen  or treat it identically to Prefix or Exact path types.nImplementations are required to support all path types.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"backend\": { SchemaProps: spec.SchemaProps{ Description: \"Backend defines the referenced service endpoint to which the traffic will be forwarded to.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/networking/v1.IngressBackend\"), }, }, }, Required: []string{\"pathType\", \"backend\"}, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1.IngressBackend\"}, } } func schema_k8sio_api_networking_v1_HTTPIngressRuleValue(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HTTPIngressRuleValue is a list of http selectors pointing to backends. In the example: http://<host>/<path>?<searchpart> -> backend where where parts of the url correspond to RFC 3986, this resource will be used to match against everything after the last '/' and before the first '?' or '#'.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"paths\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"A collection of paths that map requests to backends.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/networking/v1.HTTPIngressPath\"), }, }, }, }, }, }, Required: []string{\"paths\"}, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1.HTTPIngressPath\"}, } } func schema_k8sio_api_networking_v1_IPBlock(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IPBlock describes a particular CIDR (Ex. \"192.168.1.1/24\",\"2001:db9::/64\") that is allowed to the pods matched by a NetworkPolicySpec's podSelector. The except entry describes CIDRs that should not be included within this rule.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"cidr\": { SchemaProps: spec.SchemaProps{ Description: \"CIDR is a string representing the IP Block Valid examples are \"192.168.1.1/24\" or \"2001:db9::/64\"\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"except\": { SchemaProps: spec.SchemaProps{ Description: \"Except is a slice of CIDRs that should not be included within an IP Block Valid examples are \"192.168.1.1/24\" or \"2001:db9::/64\" Except values will be rejected if they are outside the CIDR range\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"cidr\"}, }, }, } } func schema_k8sio_api_networking_v1_Ingress(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Ingress is a collection of rules that allow inbound connections to reach the endpoints defined by a backend. An Ingress can be configured to give services externally-reachable urls, load balance traffic, terminate SSL, offer name based virtual hosting etc.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec is the desired state of the Ingress. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/networking/v1.IngressSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is the current state of the Ingress. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/networking/v1.IngressStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1.IngressSpec\", \"k8s.io/api/networking/v1.IngressStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_networking_v1_IngressBackend(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressBackend describes all endpoints for a given service and port.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"service\": { SchemaProps: spec.SchemaProps{ Description: \"Service references a Service as a Backend. This is a mutually exclusive setting with \"Resource\".\", Ref:         ref(\"k8s.io/api/networking/v1.IngressServiceBackend\"), }, }, \"resource\": { SchemaProps: spec.SchemaProps{ Description: \"Resource is an ObjectRef to another Kubernetes resource in the namespace of the Ingress object. If resource is specified, a service.Name and service.Port must not be specified. This is a mutually exclusive setting with \"Service\".\", Ref:         ref(\"k8s.io/api/core/v1.TypedLocalObjectReference\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.TypedLocalObjectReference\", \"k8s.io/api/networking/v1.IngressServiceBackend\"}, } } func schema_k8sio_api_networking_v1_IngressClass(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressClass represents the class of the Ingress, referenced by the Ingress Spec. The `ingressclass.kubernetes.io/is-default-class` annotation can be used to indicate that an IngressClass should be considered default. When a single IngressClass resource has this annotation set to true, new Ingress resources without a class specified will be assigned this default class.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec is the desired state of the IngressClass. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/networking/v1.IngressClassSpec\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1.IngressClassSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_networking_v1_IngressClassList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressClassList is a collection of IngressClasses.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of IngressClasses.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/networking/v1.IngressClass\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1.IngressClass\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_networking_v1_IngressClassParametersReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressClassParametersReference identifies an API object. This can be used to specify a cluster or namespace-scoped resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"apiGroup\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroup is the group for the resource being referenced. If APIGroup is not specified, the specified Kind must be in the core API group. For any other third-party types, APIGroup is required.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is the type of resource being referenced.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the name of resource being referenced.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"scope\": { SchemaProps: spec.SchemaProps{ Description: \"Scope represents if this refers to a cluster or namespace scoped resource. This may be set to \"Cluster\" (default) or \"Namespace\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"Namespace is the namespace of the resource being referenced. This field is required when scope is set to \"Namespace\" and must be unset when scope is set to \"Cluster\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"kind\", \"name\"}, }, }, } } func schema_k8sio_api_networking_v1_IngressClassSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressClassSpec provides information about the class of an Ingress.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"controller\": { SchemaProps: spec.SchemaProps{ Description: \"Controller refers to the name of the controller that should handle this class. This allows for different \"flavors\" that are controlled by the same controller. For example, you may have different Parameters for the same implementing controller. This should be specified as a domain-prefixed path no more than 250 characters in length, e.g. \"acme.io/ingress-controller\". This field is immutable.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"parameters\": { SchemaProps: spec.SchemaProps{ Description: \"Parameters is a link to a custom resource containing additional configuration for the controller. This is optional if the controller does not require extra parameters.\", Ref:         ref(\"k8s.io/api/networking/v1.IngressClassParametersReference\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1.IngressClassParametersReference\"}, } } func schema_k8sio_api_networking_v1_IngressList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressList is a collection of Ingress.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of Ingress.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/networking/v1.Ingress\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1.Ingress\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_networking_v1_IngressRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressRule represents the rules mapping the paths under a specified host to the related backend services. Incoming requests are first evaluated for a host match, then routed to the backend associated with the matching IngressRuleValue.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"host\": { SchemaProps: spec.SchemaProps{ Description: \"Host is the fully qualified domain name of a network host, as defined by RFC 3986. Note the following deviations from the \"host\" part of the URI as defined in RFC 3986: 1. IPs are not allowed. Currently an IngressRuleValue can only apply ton   the IP in the Spec of the parent Ingress.n2. The `:` delimiter is not respected because ports are not allowed.nt  Currently the port of an Ingress is implicitly :80 for http andnt  :443 for https.nBoth these may change in the future. Incoming requests are matched against the host before the IngressRuleValue. If the host is unspecified, the Ingress routes all traffic based on the specified IngressRuleValue.nnHost can be \"precise\" which is a domain name without the terminating dot of a network host (e.g. \"foo.bar.com\") or \"wildcard\", which is a domain name prefixed with a single wildcard label (e.g. \"*.foo.com\"). The wildcard character '*' must appear by itself as the first DNS label and matches only a single label. You cannot have a wildcard label by itself (e.g. Host == \"*\"). Requests will be matched against the Host field in the following way: 1. If Host is precise, the request matches this rule if the http host header is equal to Host. 2. If Host is a wildcard, then the request matches this rule if the http host header is to equal to the suffix (removing the first label) of the wildcard rule.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"http\": { SchemaProps: spec.SchemaProps{ Ref: ref(\"k8s.io/api/networking/v1.HTTPIngressRuleValue\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1.HTTPIngressRuleValue\"}, } } func schema_k8sio_api_networking_v1_IngressRuleValue(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressRuleValue represents a rule to apply against incoming requests. If the rule is satisfied, the request is routed to the specified backend. Currently mixing different types of rules in a single Ingress is disallowed, so exactly one of the following must be set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"http\": { SchemaProps: spec.SchemaProps{ Ref: ref(\"k8s.io/api/networking/v1.HTTPIngressRuleValue\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1.HTTPIngressRuleValue\"}, } } func schema_k8sio_api_networking_v1_IngressServiceBackend(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressServiceBackend references a Kubernetes Service as a Backend.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the referenced service. The service must exist in the same namespace as the Ingress object.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"port\": { SchemaProps: spec.SchemaProps{ Description: \"Port of the referenced service. A port name or port number is required for a IngressServiceBackend.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/networking/v1.ServiceBackendPort\"), }, }, }, Required: []string{\"name\"}, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1.ServiceBackendPort\"}, } } func schema_k8sio_api_networking_v1_IngressSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressSpec describes the Ingress the user wishes to exist.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ingressClassName\": { SchemaProps: spec.SchemaProps{ Description: \"IngressClassName is the name of the IngressClass cluster resource. The associated IngressClass defines which controller will implement the resource. This replaces the deprecated `kubernetes.io/ingress.class` annotation. For backwards compatibility, when that annotation is set, it must be given precedence over this field. The controller may emit a warning if the field and annotation have different values. Implementations of this API should ignore Ingresses without a class specified. An IngressClass resource may be marked as default, which can be used to set a default value for this field. For more information, refer to the IngressClass documentation.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"defaultBackend\": { SchemaProps: spec.SchemaProps{ Description: \"DefaultBackend is the backend that should handle requests that don't match any rule. If Rules are not specified, DefaultBackend must be specified. If DefaultBackend is not set, the handling of requests that do not match any of the rules will be up to the Ingress controller.\", Ref:         ref(\"k8s.io/api/networking/v1.IngressBackend\"), }, }, \"tls\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"TLS configuration. Currently the Ingress only supports a single TLS port, 443. If multiple members of this list specify different hosts, they will be multiplexed on the same port according to the hostname specified through the SNI TLS extension, if the ingress controller fulfilling the ingress supports SNI.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/networking/v1.IngressTLS\"), }, }, }, }, }, \"rules\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"A list of host rules used to configure the Ingress. If unspecified, or no rule matches, all traffic is sent to the default backend.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/networking/v1.IngressRule\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1.IngressBackend\", \"k8s.io/api/networking/v1.IngressRule\", \"k8s.io/api/networking/v1.IngressTLS\"}, } } func schema_k8sio_api_networking_v1_IngressStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressStatus describe the current state of the Ingress.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"loadBalancer\": { SchemaProps: spec.SchemaProps{ Description: \"LoadBalancer contains the current status of the load-balancer.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.LoadBalancerStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.LoadBalancerStatus\"}, } } func schema_k8sio_api_networking_v1_IngressTLS(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressTLS describes the transport layer security associated with an Ingress.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"hosts\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Hosts are a list of hosts included in the TLS certificate. The values in this list must match the name/s used in the tlsSecret. Defaults to the wildcard host setting for the loadbalancer controller fulfilling this Ingress, if left unspecified.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"secretName\": { SchemaProps: spec.SchemaProps{ Description: \"SecretName is the name of the secret used to terminate TLS traffic on port 443. Field is left optional to allow TLS routing based on SNI hostname alone. If the SNI host in a listener conflicts with the \"Host\" header field used by an IngressRule, the SNI host is used for termination and value of the Host header is used for routing.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_networking_v1_NetworkPolicy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NetworkPolicy describes what network traffic is allowed for a set of Pods\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the desired behavior for this NetworkPolicy.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/networking/v1.NetworkPolicySpec\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1.NetworkPolicySpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_networking_v1_NetworkPolicyEgressRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NetworkPolicyEgressRule describes a particular set of traffic that is allowed out of pods matched by a NetworkPolicySpec's podSelector. The traffic must match both ports and to. This type is beta-level in 1.8\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ports\": { SchemaProps: spec.SchemaProps{ Description: \"List of destination ports for outgoing traffic. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/networking/v1.NetworkPolicyPort\"), }, }, }, }, }, \"to\": { SchemaProps: spec.SchemaProps{ Description: \"List of destinations for outgoing traffic of pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all destinations (traffic not restricted by destination). If this field is present and contains at least one item, this rule allows traffic only if the traffic matches at least one item in the to list.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/networking/v1.NetworkPolicyPeer\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1.NetworkPolicyPeer\", \"k8s.io/api/networking/v1.NetworkPolicyPort\"}, } } func schema_k8sio_api_networking_v1_NetworkPolicyIngressRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NetworkPolicyIngressRule describes a particular set of traffic that is allowed to the pods matched by a NetworkPolicySpec's podSelector. The traffic must match both ports and from.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ports\": { SchemaProps: spec.SchemaProps{ Description: \"List of ports which should be made accessible on the pods selected for this rule. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/networking/v1.NetworkPolicyPort\"), }, }, }, }, }, \"from\": { SchemaProps: spec.SchemaProps{ Description: \"List of sources which should be able to access the pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all sources (traffic not restricted by source). If this field is present and contains at least one item, this rule allows traffic only if the traffic matches at least one item in the from list.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/networking/v1.NetworkPolicyPeer\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1.NetworkPolicyPeer\", \"k8s.io/api/networking/v1.NetworkPolicyPort\"}, } } func schema_k8sio_api_networking_v1_NetworkPolicyList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NetworkPolicyList is a list of NetworkPolicy objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of schema objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/networking/v1.NetworkPolicy\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1.NetworkPolicy\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_networking_v1_NetworkPolicyPeer(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NetworkPolicyPeer describes a peer to allow traffic to/from. Only certain combinations of fields are allowed\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"podSelector\": { SchemaProps: spec.SchemaProps{ Description: \"This is a label selector which selects Pods. This field follows standard label selector semantics; if present but empty, it selects all pods.nnIf NamespaceSelector is also set, then the NetworkPolicyPeer as a whole selects the Pods matching PodSelector in the Namespaces selected by NamespaceSelector. Otherwise it selects the Pods matching PodSelector in the policy's own Namespace.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"namespaceSelector\": { SchemaProps: spec.SchemaProps{ Description: \"Selects Namespaces using cluster-scoped labels. This field follows standard label selector semantics; if present but empty, it selects all namespaces.nnIf PodSelector is also set, then the NetworkPolicyPeer as a whole selects the Pods matching PodSelector in the Namespaces selected by NamespaceSelector. Otherwise it selects all Pods in the Namespaces selected by NamespaceSelector.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"ipBlock\": { SchemaProps: spec.SchemaProps{ Description: \"IPBlock defines policy on a particular IPBlock. If this field is set then neither of the other fields can be.\", Ref:         ref(\"k8s.io/api/networking/v1.IPBlock\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1.IPBlock\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_networking_v1_NetworkPolicyPort(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NetworkPolicyPort describes a port to allow traffic on\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"protocol\": { SchemaProps: spec.SchemaProps{ Description: \"The protocol (TCP, UDP, or SCTP) which traffic must match. If not specified, this field defaults to TCP.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"port\": { SchemaProps: spec.SchemaProps{ Description: \"The port on the given protocol. This can either be a numerical or named port on a pod. If this field is not provided, this matches all port names and numbers. If present, only traffic on the specified protocol AND port will be matched.\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, \"endPort\": { SchemaProps: spec.SchemaProps{ Description: \"If set, indicates that the range of ports from port to endPort, inclusive, should be allowed by the policy. This field cannot be defined if the port field is not defined or if the port field is defined as a named (string) port. The endPort must be equal or greater than port. This feature is in Beta state and is enabled by default. It can be disabled using the Feature Gate \"NetworkPolicyEndPort\".\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"}, } } func schema_k8sio_api_networking_v1_NetworkPolicySpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NetworkPolicySpec provides the specification of a NetworkPolicy\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"podSelector\": { SchemaProps: spec.SchemaProps{ Description: \"Selects the pods to which this NetworkPolicy object applies. The array of ingress rules is applied to any pods selected by this field. Multiple network policies can select the same set of pods. In this case, the ingress rules for each are combined additively. This field is NOT optional and follows standard label selector semantics. An empty podSelector matches all pods in this namespace.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"ingress\": { SchemaProps: spec.SchemaProps{ Description: \"List of ingress rules to be applied to the selected pods. Traffic is allowed to a pod if there are no NetworkPolicies selecting the pod (and cluster policy otherwise allows the traffic), OR if the traffic source is the pod's local node, OR if the traffic matches at least one ingress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy does not allow any traffic (and serves solely to ensure that the pods it selects are isolated by default)\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/networking/v1.NetworkPolicyIngressRule\"), }, }, }, }, }, \"egress\": { SchemaProps: spec.SchemaProps{ Description: \"List of egress rules to be applied to the selected pods. Outgoing traffic is allowed if there are no NetworkPolicies selecting the pod (and cluster policy otherwise allows the traffic), OR if the traffic matches at least one egress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy limits all outgoing traffic (and serves solely to ensure that the pods it selects are isolated by default). This field is beta-level in 1.8\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/networking/v1.NetworkPolicyEgressRule\"), }, }, }, }, }, \"policyTypes\": { SchemaProps: spec.SchemaProps{ Description: \"List of rule types that the NetworkPolicy relates to. Valid options are [\"Ingress\"], [\"Egress\"], or [\"Ingress\", \"Egress\"]. If this field is not specified, it will default based on the existence of Ingress or Egress rules; policies that contain an Egress section are assumed to affect Egress, and all policies (whether or not they contain an Ingress section) are assumed to affect Ingress. If you want to write an egress-only policy, you must explicitly specify policyTypes [ \"Egress\" ]. Likewise, if you want to write a policy that specifies that no egress is allowed, you must specify a policyTypes value that include \"Egress\" (since such a policy would not include an Egress section and would otherwise default to just [ \"Ingress\" ]). This field is beta-level in 1.8\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"podSelector\"}, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1.NetworkPolicyEgressRule\", \"k8s.io/api/networking/v1.NetworkPolicyIngressRule\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_networking_v1_ServiceBackendPort(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ServiceBackendPort is the service port being referenced.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the name of the port on the Service. This is a mutually exclusive setting with \"Number\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"number\": { SchemaProps: spec.SchemaProps{ Description: \"Number is the numerical port number (e.g. 80) on the Service. This is a mutually exclusive setting with \"Name\".\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_k8sio_api_networking_v1beta1_HTTPIngressPath(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HTTPIngressPath associates a path with a backend. Incoming urls matching the path are forwarded to the backend.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"path\": { SchemaProps: spec.SchemaProps{ Description: \"Path is matched against the path of an incoming request. Currently it can contain characters disallowed from the conventional \"path\" part of a URL as defined by RFC 3986. Paths must begin with a '/' and must be present when using PathType with value \"Exact\" or \"Prefix\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"pathType\": { SchemaProps: spec.SchemaProps{ Description: \"PathType determines the interpretation of the Path matching. PathType can be one of the following values: * Exact: Matches the URL path exactly. * Prefix: Matches based on a URL path prefix split by '/'. Matching isn  done on a path element by element basis. A path element refers is then  list of labels in the path split by the '/' separator. A request is an  match for path p if every p is an element-wise prefix of p of then  request path. Note that if the last element of the path is a substringn  of the last element in request path, it is not a match (e.g. /foo/barn  matches /foo/bar/baz, but does not match /foo/barbaz).n* ImplementationSpecific: Interpretation of the Path matching is up ton  the IngressClass. Implementations can treat this as a separate PathTypen  or treat it identically to Prefix or Exact path types.nImplementations are required to support all path types. Defaults to ImplementationSpecific.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"backend\": { SchemaProps: spec.SchemaProps{ Description: \"Backend defines the referenced service endpoint to which the traffic will be forwarded to.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/networking/v1beta1.IngressBackend\"), }, }, }, Required: []string{\"backend\"}, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1beta1.IngressBackend\"}, } } func schema_k8sio_api_networking_v1beta1_HTTPIngressRuleValue(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HTTPIngressRuleValue is a list of http selectors pointing to backends. In the example: http://<host>/<path>?<searchpart> -> backend where where parts of the url correspond to RFC 3986, this resource will be used to match against everything after the last '/' and before the first '?' or '#'.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"paths\": { SchemaProps: spec.SchemaProps{ Description: \"A collection of paths that map requests to backends.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/networking/v1beta1.HTTPIngressPath\"), }, }, }, }, }, }, Required: []string{\"paths\"}, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1beta1.HTTPIngressPath\"}, } } func schema_k8sio_api_networking_v1beta1_Ingress(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Ingress is a collection of rules that allow inbound connections to reach the endpoints defined by a backend. An Ingress can be configured to give services externally-reachable urls, load balance traffic, terminate SSL, offer name based virtual hosting etc.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec is the desired state of the Ingress. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/networking/v1beta1.IngressSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is the current state of the Ingress. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/networking/v1beta1.IngressStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1beta1.IngressSpec\", \"k8s.io/api/networking/v1beta1.IngressStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_networking_v1beta1_IngressBackend(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressBackend describes all endpoints for a given service and port.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"serviceName\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies the name of the referenced service.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"servicePort\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies the port of the referenced service.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, \"resource\": { SchemaProps: spec.SchemaProps{ Description: \"Resource is an ObjectRef to another Kubernetes resource in the namespace of the Ingress object. If resource is specified, serviceName and servicePort must not be specified.\", Ref:         ref(\"k8s.io/api/core/v1.TypedLocalObjectReference\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.TypedLocalObjectReference\", \"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"}, } } func schema_k8sio_api_networking_v1beta1_IngressClass(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressClass represents the class of the Ingress, referenced by the Ingress Spec. The `ingressclass.kubernetes.io/is-default-class` annotation can be used to indicate that an IngressClass should be considered default. When a single IngressClass resource has this annotation set to true, new Ingress resources without a class specified will be assigned this default class.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec is the desired state of the IngressClass. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/networking/v1beta1.IngressClassSpec\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1beta1.IngressClassSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_networking_v1beta1_IngressClassList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressClassList is a collection of IngressClasses.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of IngressClasses.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/networking/v1beta1.IngressClass\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1beta1.IngressClass\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_networking_v1beta1_IngressClassParametersReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressClassParametersReference identifies an API object. This can be used to specify a cluster or namespace-scoped resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"apiGroup\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroup is the group for the resource being referenced. If APIGroup is not specified, the specified Kind must be in the core API group. For any other third-party types, APIGroup is required.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is the type of resource being referenced.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the name of resource being referenced.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"scope\": { SchemaProps: spec.SchemaProps{ Description: \"Scope represents if this refers to a cluster or namespace scoped resource. This may be set to \"Cluster\" (default) or \"Namespace\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"Namespace is the namespace of the resource being referenced. This field is required when scope is set to \"Namespace\" and must be unset when scope is set to \"Cluster\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"kind\", \"name\", \"scope\"}, }, }, } } func schema_k8sio_api_networking_v1beta1_IngressClassSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressClassSpec provides information about the class of an Ingress.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"controller\": { SchemaProps: spec.SchemaProps{ Description: \"Controller refers to the name of the controller that should handle this class. This allows for different \"flavors\" that are controlled by the same controller. For example, you may have different Parameters for the same implementing controller. This should be specified as a domain-prefixed path no more than 250 characters in length, e.g. \"acme.io/ingress-controller\". This field is immutable.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"parameters\": { SchemaProps: spec.SchemaProps{ Description: \"Parameters is a link to a custom resource containing additional configuration for the controller. This is optional if the controller does not require extra parameters.\", Ref:         ref(\"k8s.io/api/networking/v1beta1.IngressClassParametersReference\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1beta1.IngressClassParametersReference\"}, } } func schema_k8sio_api_networking_v1beta1_IngressList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressList is a collection of Ingress.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of Ingress.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/networking/v1beta1.Ingress\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1beta1.Ingress\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_networking_v1beta1_IngressRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressRule represents the rules mapping the paths under a specified host to the related backend services. Incoming requests are first evaluated for a host match, then routed to the backend associated with the matching IngressRuleValue.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"host\": { SchemaProps: spec.SchemaProps{ Description: \"Host is the fully qualified domain name of a network host, as defined by RFC 3986. Note the following deviations from the \"host\" part of the URI as defined in RFC 3986: 1. IPs are not allowed. Currently an IngressRuleValue can only apply ton   the IP in the Spec of the parent Ingress.n2. The `:` delimiter is not respected because ports are not allowed.nt  Currently the port of an Ingress is implicitly :80 for http andnt  :443 for https.nBoth these may change in the future. Incoming requests are matched against the host before the IngressRuleValue. If the host is unspecified, the Ingress routes all traffic based on the specified IngressRuleValue.nnHost can be \"precise\" which is a domain name without the terminating dot of a network host (e.g. \"foo.bar.com\") or \"wildcard\", which is a domain name prefixed with a single wildcard label (e.g. \"*.foo.com\"). The wildcard character '*' must appear by itself as the first DNS label and matches only a single label. You cannot have a wildcard label by itself (e.g. Host == \"*\"). Requests will be matched against the Host field in the following way: 1. If Host is precise, the request matches this rule if the http host header is equal to Host. 2. If Host is a wildcard, then the request matches this rule if the http host header is to equal to the suffix (removing the first label) of the wildcard rule.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"http\": { SchemaProps: spec.SchemaProps{ Ref: ref(\"k8s.io/api/networking/v1beta1.HTTPIngressRuleValue\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1beta1.HTTPIngressRuleValue\"}, } } func schema_k8sio_api_networking_v1beta1_IngressRuleValue(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressRuleValue represents a rule to apply against incoming requests. If the rule is satisfied, the request is routed to the specified backend. Currently mixing different types of rules in a single Ingress is disallowed, so exactly one of the following must be set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"http\": { SchemaProps: spec.SchemaProps{ Ref: ref(\"k8s.io/api/networking/v1beta1.HTTPIngressRuleValue\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1beta1.HTTPIngressRuleValue\"}, } } func schema_k8sio_api_networking_v1beta1_IngressSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressSpec describes the Ingress the user wishes to exist.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ingressClassName\": { SchemaProps: spec.SchemaProps{ Description: \"IngressClassName is the name of the IngressClass cluster resource. The associated IngressClass defines which controller will implement the resource. This replaces the deprecated `kubernetes.io/ingress.class` annotation. For backwards compatibility, when that annotation is set, it must be given precedence over this field. The controller may emit a warning if the field and annotation have different values. Implementations of this API should ignore Ingresses without a class specified. An IngressClass resource may be marked as default, which can be used to set a default value for this field. For more information, refer to the IngressClass documentation.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"backend\": { SchemaProps: spec.SchemaProps{ Description: \"A default backend capable of servicing requests that don't match any rule. At least one of 'backend' or 'rules' must be specified. This field is optional to allow the loadbalancer controller or defaulting logic to specify a global default.\", Ref:         ref(\"k8s.io/api/networking/v1beta1.IngressBackend\"), }, }, \"tls\": { SchemaProps: spec.SchemaProps{ Description: \"TLS configuration. Currently the Ingress only supports a single TLS port, 443. If multiple members of this list specify different hosts, they will be multiplexed on the same port according to the hostname specified through the SNI TLS extension, if the ingress controller fulfilling the ingress supports SNI.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/networking/v1beta1.IngressTLS\"), }, }, }, }, }, \"rules\": { SchemaProps: spec.SchemaProps{ Description: \"A list of host rules used to configure the Ingress. If unspecified, or no rule matches, all traffic is sent to the default backend.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/networking/v1beta1.IngressRule\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/networking/v1beta1.IngressBackend\", \"k8s.io/api/networking/v1beta1.IngressRule\", \"k8s.io/api/networking/v1beta1.IngressTLS\"}, } } func schema_k8sio_api_networking_v1beta1_IngressStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressStatus describe the current state of the Ingress.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"loadBalancer\": { SchemaProps: spec.SchemaProps{ Description: \"LoadBalancer contains the current status of the load-balancer.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.LoadBalancerStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.LoadBalancerStatus\"}, } } func schema_k8sio_api_networking_v1beta1_IngressTLS(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IngressTLS describes the transport layer security associated with an Ingress.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"hosts\": { SchemaProps: spec.SchemaProps{ Description: \"Hosts are a list of hosts included in the TLS certificate. The values in this list must match the name/s used in the tlsSecret. Defaults to the wildcard host setting for the loadbalancer controller fulfilling this Ingress, if left unspecified.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"secretName\": { SchemaProps: spec.SchemaProps{ Description: \"SecretName is the name of the secret used to terminate TLS traffic on port 443. Field is left optional to allow TLS routing based on SNI hostname alone. If the SNI host in a listener conflicts with the \"Host\" header field used by an IngressRule, the SNI host is used for termination and value of the Host header is used for routing.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_node_v1_Overhead(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Overhead structure represents the resource overhead associated with running a pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"podFixed\": { SchemaProps: spec.SchemaProps{ Description: \"PodFixed represents the fixed resource overhead associated with running a pod.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_node_v1_RuntimeClass(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RuntimeClass defines a class of container runtime supported in the cluster. The RuntimeClass is used to determine which container runtime is used to run all containers in a pod. RuntimeClasses are manually defined by a user or cluster provisioner, and referenced in the PodSpec. The Kubelet is responsible for resolving the RuntimeClassName reference before running the pod.  For more details, see https://kubernetes.io/docs/concepts/containers/runtime-class/\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"handler\": { SchemaProps: spec.SchemaProps{ Description: \"Handler specifies the underlying runtime and configuration that the CRI implementation will use to handle pods of this class. The possible values are specific to the node & CRI configuration.  It is assumed that all handlers are available on every node, and handlers of the same name are equivalent on every node. For example, a handler called \"runc\" might specify that the runc OCI runtime (using native Linux containers) will be used to run the containers in a pod. The Handler must be lowercase, conform to the DNS Label (RFC 1123) requirements, and is immutable.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"overhead\": { SchemaProps: spec.SchemaProps{ Description: \"Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, seen https://kubernetes.io/docs/concepts/scheduling-eviction/pod-overhead/nThis field is in beta starting v1.18 and is only honored by servers that enable the PodOverhead feature.\", Ref:         ref(\"k8s.io/api/node/v1.Overhead\"), }, }, \"scheduling\": { SchemaProps: spec.SchemaProps{ Description: \"Scheduling holds the scheduling constraints to ensure that pods running with this RuntimeClass are scheduled to nodes that support it. If scheduling is nil, this RuntimeClass is assumed to be supported by all nodes.\", Ref:         ref(\"k8s.io/api/node/v1.Scheduling\"), }, }, }, Required: []string{\"handler\"}, }, }, Dependencies: []string{ \"k8s.io/api/node/v1.Overhead\", \"k8s.io/api/node/v1.Scheduling\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_node_v1_RuntimeClassList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RuntimeClassList is a list of RuntimeClass objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of schema objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/node/v1.RuntimeClass\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/node/v1.RuntimeClass\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_node_v1_Scheduling(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Scheduling specifies the scheduling constraints for nodes supporting a RuntimeClass.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"nodeSelector\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"nodeSelector lists labels that must be present on nodes that support this RuntimeClass. Pods using this RuntimeClass can only be scheduled to a node matched by this selector. The RuntimeClass nodeSelector is merged with a pod's existing nodeSelector. Any conflicts will cause the pod to be rejected in admission.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"tolerations\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"tolerations are appended (excluding duplicates) to pods running with this RuntimeClass during admission, effectively unioning the set of nodes tolerated by the pod and the RuntimeClass.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.Toleration\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.Toleration\"}, } } func schema_k8sio_api_node_v1alpha1_Overhead(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Overhead structure represents the resource overhead associated with running a pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"podFixed\": { SchemaProps: spec.SchemaProps{ Description: \"PodFixed represents the fixed resource overhead associated with running a pod.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_node_v1alpha1_RuntimeClass(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RuntimeClass defines a class of container runtime supported in the cluster. The RuntimeClass is used to determine which container runtime is used to run all containers in a pod. RuntimeClasses are (currently) manually defined by a user or cluster provisioner, and referenced in the PodSpec. The Kubelet is responsible for resolving the RuntimeClassName reference before running the pod.  For more details, see https://git.k8s.io/enhancements/keps/sig-node/585-runtime-class\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the RuntimeClass More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/node/v1alpha1.RuntimeClassSpec\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/node/v1alpha1.RuntimeClassSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_node_v1alpha1_RuntimeClassList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RuntimeClassList is a list of RuntimeClass objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of schema objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/node/v1alpha1.RuntimeClass\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/node/v1alpha1.RuntimeClass\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_node_v1alpha1_RuntimeClassSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RuntimeClassSpec is a specification of a RuntimeClass. It contains parameters that are required to describe the RuntimeClass to the Container Runtime Interface (CRI) implementation, as well as any other components that need to understand how the pod will be run. The RuntimeClassSpec is immutable.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"runtimeHandler\": { SchemaProps: spec.SchemaProps{ Description: \"RuntimeHandler specifies the underlying runtime and configuration that the CRI implementation will use to handle pods of this class. The possible values are specific to the node & CRI configuration.  It is assumed that all handlers are available on every node, and handlers of the same name are equivalent on every node. For example, a handler called \"runc\" might specify that the runc OCI runtime (using native Linux containers) will be used to run the containers in a pod. The RuntimeHandler must be lowercase, conform to the DNS Label (RFC 1123) requirements, and is immutable.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"overhead\": { SchemaProps: spec.SchemaProps{ Description: \"Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see https://git.k8s.io/enhancements/keps/sig-node/688-pod-overhead/README.md This field is beta-level as of Kubernetes v1.18, and is only honored by servers that enable the PodOverhead feature.\", Ref:         ref(\"k8s.io/api/node/v1alpha1.Overhead\"), }, }, \"scheduling\": { SchemaProps: spec.SchemaProps{ Description: \"Scheduling holds the scheduling constraints to ensure that pods running with this RuntimeClass are scheduled to nodes that support it. If scheduling is nil, this RuntimeClass is assumed to be supported by all nodes.\", Ref:         ref(\"k8s.io/api/node/v1alpha1.Scheduling\"), }, }, }, Required: []string{\"runtimeHandler\"}, }, }, Dependencies: []string{ \"k8s.io/api/node/v1alpha1.Overhead\", \"k8s.io/api/node/v1alpha1.Scheduling\"}, } } func schema_k8sio_api_node_v1alpha1_Scheduling(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Scheduling specifies the scheduling constraints for nodes supporting a RuntimeClass.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"nodeSelector\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"nodeSelector lists labels that must be present on nodes that support this RuntimeClass. Pods using this RuntimeClass can only be scheduled to a node matched by this selector. The RuntimeClass nodeSelector is merged with a pod's existing nodeSelector. Any conflicts will cause the pod to be rejected in admission.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"tolerations\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"tolerations are appended (excluding duplicates) to pods running with this RuntimeClass during admission, effectively unioning the set of nodes tolerated by the pod and the RuntimeClass.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.Toleration\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.Toleration\"}, } } func schema_k8sio_api_node_v1beta1_Overhead(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Overhead structure represents the resource overhead associated with running a pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"podFixed\": { SchemaProps: spec.SchemaProps{ Description: \"PodFixed represents the fixed resource overhead associated with running a pod.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_api_node_v1beta1_RuntimeClass(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RuntimeClass defines a class of container runtime supported in the cluster. The RuntimeClass is used to determine which container runtime is used to run all containers in a pod. RuntimeClasses are (currently) manually defined by a user or cluster provisioner, and referenced in the PodSpec. The Kubelet is responsible for resolving the RuntimeClassName reference before running the pod.  For more details, see https://git.k8s.io/enhancements/keps/sig-node/585-runtime-class\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"handler\": { SchemaProps: spec.SchemaProps{ Description: \"Handler specifies the underlying runtime and configuration that the CRI implementation will use to handle pods of this class. The possible values are specific to the node & CRI configuration.  It is assumed that all handlers are available on every node, and handlers of the same name are equivalent on every node. For example, a handler called \"runc\" might specify that the runc OCI runtime (using native Linux containers) will be used to run the containers in a pod. The Handler must be lowercase, conform to the DNS Label (RFC 1123) requirements, and is immutable.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"overhead\": { SchemaProps: spec.SchemaProps{ Description: \"Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see https://git.k8s.io/enhancements/keps/sig-node/688-pod-overhead/README.md This field is beta-level as of Kubernetes v1.18, and is only honored by servers that enable the PodOverhead feature.\", Ref:         ref(\"k8s.io/api/node/v1beta1.Overhead\"), }, }, \"scheduling\": { SchemaProps: spec.SchemaProps{ Description: \"Scheduling holds the scheduling constraints to ensure that pods running with this RuntimeClass are scheduled to nodes that support it. If scheduling is nil, this RuntimeClass is assumed to be supported by all nodes.\", Ref:         ref(\"k8s.io/api/node/v1beta1.Scheduling\"), }, }, }, Required: []string{\"handler\"}, }, }, Dependencies: []string{ \"k8s.io/api/node/v1beta1.Overhead\", \"k8s.io/api/node/v1beta1.Scheduling\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_node_v1beta1_RuntimeClassList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RuntimeClassList is a list of RuntimeClass objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of schema objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/node/v1beta1.RuntimeClass\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/node/v1beta1.RuntimeClass\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_node_v1beta1_Scheduling(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Scheduling specifies the scheduling constraints for nodes supporting a RuntimeClass.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"nodeSelector\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"nodeSelector lists labels that must be present on nodes that support this RuntimeClass. Pods using this RuntimeClass can only be scheduled to a node matched by this selector. The RuntimeClass nodeSelector is merged with a pod's existing nodeSelector. Any conflicts will cause the pod to be rejected in admission.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"tolerations\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"tolerations are appended (excluding duplicates) to pods running with this RuntimeClass during admission, effectively unioning the set of nodes tolerated by the pod and the RuntimeClass.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.Toleration\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.Toleration\"}, } } func schema_k8sio_api_policy_v1_Eviction(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Eviction evicts a pod from its node subject to certain policies and safety constraints. This is a subresource of Pod.  A request to cause such an eviction is created by POSTing to .../pods/<pod name>/evictions.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"ObjectMeta describes the pod that is being evicted.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"deleteOptions\": { SchemaProps: spec.SchemaProps{ Description: \"DeleteOptions may be provided\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.DeleteOptions\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.DeleteOptions\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_policy_v1_PodDisruptionBudget(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodDisruptionBudget is an object to define the max disruption that can be caused to a collection of pods\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the desired behavior of the PodDisruptionBudget.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/policy/v1.PodDisruptionBudgetSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Most recently observed status of the PodDisruptionBudget.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/policy/v1.PodDisruptionBudgetStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/policy/v1.PodDisruptionBudgetSpec\", \"k8s.io/api/policy/v1.PodDisruptionBudgetStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_policy_v1_PodDisruptionBudgetList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodDisruptionBudgetList is a collection of PodDisruptionBudgets.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of PodDisruptionBudgets\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/policy/v1.PodDisruptionBudget\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/policy/v1.PodDisruptionBudget\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_policy_v1_PodDisruptionBudgetSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodDisruptionBudgetSpec is a description of a PodDisruptionBudget.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"minAvailable\": { SchemaProps: spec.SchemaProps{ Description: \"An eviction is allowed if at least \"minAvailable\" pods selected by \"selector\" will still be available after the eviction, i.e. even in the absence of the evicted pod.  So for example you can prevent all voluntary evictions by specifying \"100%\".\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, \"selector\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-strategy\": \"replace\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Label query over pods whose evictions are managed by the disruption budget. A null selector will match no pods, while an empty ({}) selector will select all pods within the namespace.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"maxUnavailable\": { SchemaProps: spec.SchemaProps{ Description: \"An eviction is allowed if at most \"maxUnavailable\" pods selected by \"selector\" are unavailable after the eviction, i.e. even in absence of the evicted pod. For example, one can prevent all voluntary evictions by specifying 0. This is a mutually exclusive setting with \"minAvailable\".\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\", \"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"}, } } func schema_k8sio_api_policy_v1_PodDisruptionBudgetStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodDisruptionBudgetStatus represents information about the status of a PodDisruptionBudget. Status may trail the actual state of a system.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"Most recent generation observed when updating this PDB status. DisruptionsAllowed and other status information is valid only if observedGeneration equals to PDB's object generation.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"disruptedPods\": { SchemaProps: spec.SchemaProps{ Description: \"DisruptedPods contains information about pods whose eviction was processed by the API server eviction subresource handler but has not yet been observed by the PodDisruptionBudget controller. A pod will be in this map from the time when the API server processed the eviction request to the time when the pod is seen by PDB controller as having been marked for deletion (or after a timeout). The key in the map is the name of the pod and the value is the time when the API server processed the eviction request. If the deletion didn't occur and a pod is still there it will be removed from the list automatically by PodDisruptionBudget controller after some time. If everything goes smooth this map should be empty for the most of the time. Large number of entries in the map may indicate problems with pod deletions.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, }, }, }, \"disruptionsAllowed\": { SchemaProps: spec.SchemaProps{ Description: \"Number of pod disruptions that are currently allowed.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"currentHealthy\": { SchemaProps: spec.SchemaProps{ Description: \"current number of healthy pods\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"desiredHealthy\": { SchemaProps: spec.SchemaProps{ Description: \"minimum desired number of healthy pods\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"expectedPods\": { SchemaProps: spec.SchemaProps{ Description: \"total number of pods counted by this disruption budget\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"type\", }, \"x-kubernetes-list-type\":       \"map\", \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Conditions contain conditions for PDB. The disruption controller sets the DisruptionAllowed condition. The following are known values for the reason field (additional reasons could be added in the future): - SyncFailed: The controller encountered an error and wasn't able to computen              the number of allowed disruptions. Therefore no disruptions aren              allowed and the status of the condition will be False.n- InsufficientPods: The number of pods are either at or below the numbern                    required by the PodDisruptionBudget. No disruptions aren                    allowed and the status of the condition will be False.n- SufficientPods: There are more pods than required by the PodDisruptionBudget.n                  The condition will be True, and the number of allowedn                  disruptions are provided by the disruptionsAllowed property.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Condition\"), }, }, }, }, }, }, Required: []string{\"disruptionsAllowed\", \"currentHealthy\", \"desiredHealthy\", \"expectedPods\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Condition\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_policy_v1beta1_AllowedCSIDriver(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"AllowedCSIDriver represents a single inline CSI Driver that is allowed to be used.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the registered name of the CSI driver\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_api_policy_v1beta1_AllowedFlexVolume(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"AllowedFlexVolume represents a single Flexvolume that is allowed to be used.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"driver\": { SchemaProps: spec.SchemaProps{ Description: \"driver is the name of the Flexvolume driver.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"driver\"}, }, }, } } func schema_k8sio_api_policy_v1beta1_AllowedHostPath(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"AllowedHostPath defines the host volume conditions that will be enabled by a policy for pods to use. It requires the path prefix to be defined.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"pathPrefix\": { SchemaProps: spec.SchemaProps{ Description: \"pathPrefix is the path prefix that the host volume must match. It does not support `*`. Trailing slashes are trimmed when validating the path prefix with a host path.nnExamples: `/foo` would allow `/foo`, `/foo/` and `/foo/bar` `/foo` would not allow `/food` or `/etc/foo`\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readOnly\": { SchemaProps: spec.SchemaProps{ Description: \"when set to true, will allow host volumes matching the pathPrefix only if all volume mounts are readOnly.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_api_policy_v1beta1_Eviction(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Eviction evicts a pod from its node subject to certain policies and safety constraints. This is a subresource of Pod.  A request to cause such an eviction is created by POSTing to .../pods/<pod name>/evictions.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"ObjectMeta describes the pod that is being evicted.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"deleteOptions\": { SchemaProps: spec.SchemaProps{ Description: \"DeleteOptions may be provided\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.DeleteOptions\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.DeleteOptions\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_policy_v1beta1_FSGroupStrategyOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FSGroupStrategyOptions defines the strategy type and options used to create the strategy.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"rule\": { SchemaProps: spec.SchemaProps{ Description: \"rule is the strategy that will dictate what FSGroup is used in the SecurityContext.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ranges\": { SchemaProps: spec.SchemaProps{ Description: \"ranges are the allowed ranges of fs groups.  If you would like to force a single fs group then supply a single range with the same start and end. Required for MustRunAs.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/policy/v1beta1.IDRange\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/policy/v1beta1.IDRange\"}, } } func schema_k8sio_api_policy_v1beta1_HostPortRange(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HostPortRange defines a range of host ports that will be enabled by a policy for pods to use.  It requires both the start and end to be defined.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"min\": { SchemaProps: spec.SchemaProps{ Description: \"min is the start of the range, inclusive.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"max\": { SchemaProps: spec.SchemaProps{ Description: \"max is the end of the range, inclusive.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"min\", \"max\"}, }, }, } } func schema_k8sio_api_policy_v1beta1_IDRange(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IDRange provides a min/max of an allowed range of IDs.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"min\": { SchemaProps: spec.SchemaProps{ Description: \"min is the start of the range, inclusive.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"max\": { SchemaProps: spec.SchemaProps{ Description: \"max is the end of the range, inclusive.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int64\", }, }, }, Required: []string{\"min\", \"max\"}, }, }, } } func schema_k8sio_api_policy_v1beta1_PodDisruptionBudget(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodDisruptionBudget is an object to define the max disruption that can be caused to a collection of pods\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the desired behavior of the PodDisruptionBudget.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/policy/v1beta1.PodDisruptionBudgetSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Most recently observed status of the PodDisruptionBudget.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/policy/v1beta1.PodDisruptionBudgetStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/policy/v1beta1.PodDisruptionBudgetSpec\", \"k8s.io/api/policy/v1beta1.PodDisruptionBudgetStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_policy_v1beta1_PodDisruptionBudgetList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodDisruptionBudgetList is a collection of PodDisruptionBudgets.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items list individual PodDisruptionBudget objects\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/policy/v1beta1.PodDisruptionBudget\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/policy/v1beta1.PodDisruptionBudget\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_policy_v1beta1_PodDisruptionBudgetSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodDisruptionBudgetSpec is a description of a PodDisruptionBudget.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"minAvailable\": { SchemaProps: spec.SchemaProps{ Description: \"An eviction is allowed if at least \"minAvailable\" pods selected by \"selector\" will still be available after the eviction, i.e. even in the absence of the evicted pod.  So for example you can prevent all voluntary evictions by specifying \"100%\".\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"Label query over pods whose evictions are managed by the disruption budget. A null selector selects no pods. An empty selector ({}) also selects no pods, which differs from standard behavior of selecting all pods. In policy/v1, an empty selector will select all pods in the namespace.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"maxUnavailable\": { SchemaProps: spec.SchemaProps{ Description: \"An eviction is allowed if at most \"maxUnavailable\" pods selected by \"selector\" are unavailable after the eviction, i.e. even in absence of the evicted pod. For example, one can prevent all voluntary evictions by specifying 0. This is a mutually exclusive setting with \"minAvailable\".\", Ref:         ref(\"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\", \"k8s.io/apimachinery/pkg/util/intstr.IntOrString\"}, } } func schema_k8sio_api_policy_v1beta1_PodDisruptionBudgetStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodDisruptionBudgetStatus represents information about the status of a PodDisruptionBudget. Status may trail the actual state of a system.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"Most recent generation observed when updating this PDB status. DisruptionsAllowed and other status information is valid only if observedGeneration equals to PDB's object generation.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"disruptedPods\": { SchemaProps: spec.SchemaProps{ Description: \"DisruptedPods contains information about pods whose eviction was processed by the API server eviction subresource handler but has not yet been observed by the PodDisruptionBudget controller. A pod will be in this map from the time when the API server processed the eviction request to the time when the pod is seen by PDB controller as having been marked for deletion (or after a timeout). The key in the map is the name of the pod and the value is the time when the API server processed the eviction request. If the deletion didn't occur and a pod is still there it will be removed from the list automatically by PodDisruptionBudget controller after some time. If everything goes smooth this map should be empty for the most of the time. Large number of entries in the map may indicate problems with pod deletions.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, }, }, }, \"disruptionsAllowed\": { SchemaProps: spec.SchemaProps{ Description: \"Number of pod disruptions that are currently allowed.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"currentHealthy\": { SchemaProps: spec.SchemaProps{ Description: \"current number of healthy pods\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"desiredHealthy\": { SchemaProps: spec.SchemaProps{ Description: \"minimum desired number of healthy pods\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"expectedPods\": { SchemaProps: spec.SchemaProps{ Description: \"total number of pods counted by this disruption budget\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"type\", }, \"x-kubernetes-list-type\":       \"map\", \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Conditions contain conditions for PDB. The disruption controller sets the DisruptionAllowed condition. The following are known values for the reason field (additional reasons could be added in the future): - SyncFailed: The controller encountered an error and wasn't able to computen              the number of allowed disruptions. Therefore no disruptions aren              allowed and the status of the condition will be False.n- InsufficientPods: The number of pods are either at or below the numbern                    required by the PodDisruptionBudget. No disruptions aren                    allowed and the status of the condition will be False.n- SufficientPods: There are more pods than required by the PodDisruptionBudget.n                  The condition will be True, and the number of allowedn                  disruptions are provided by the disruptionsAllowed property.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Condition\"), }, }, }, }, }, }, Required: []string{\"disruptionsAllowed\", \"currentHealthy\", \"desiredHealthy\", \"expectedPods\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Condition\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_policy_v1beta1_PodSecurityPolicy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodSecurityPolicy governs the ability to make requests that affect the Security Context that will be applied to a pod and container. Deprecated in 1.21.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"spec defines the policy enforced.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/policy/v1beta1.PodSecurityPolicySpec\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/policy/v1beta1.PodSecurityPolicySpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_policy_v1beta1_PodSecurityPolicyList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodSecurityPolicyList is a list of PodSecurityPolicy objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is a list of schema objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/policy/v1beta1.PodSecurityPolicy\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/policy/v1beta1.PodSecurityPolicy\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_policy_v1beta1_PodSecurityPolicySpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodSecurityPolicySpec defines the policy enforced.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"privileged\": { SchemaProps: spec.SchemaProps{ Description: \"privileged determines if a pod can request to be run as privileged.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"defaultAddCapabilities\": { SchemaProps: spec.SchemaProps{ Description: \"defaultAddCapabilities is the default set of capabilities that will be added to the container unless the pod spec specifically drops the capability.  You may not list a capability in both defaultAddCapabilities and requiredDropCapabilities. Capabilities added here are implicitly allowed, and need not be included in the allowedCapabilities list.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"requiredDropCapabilities\": { SchemaProps: spec.SchemaProps{ Description: \"requiredDropCapabilities are the capabilities that will be dropped from the container.  These are required to be dropped and cannot be added.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"allowedCapabilities\": { SchemaProps: spec.SchemaProps{ Description: \"allowedCapabilities is a list of capabilities that can be requested to add to the container. Capabilities in this field may be added at the pod author's discretion. You must not list a capability in both allowedCapabilities and requiredDropCapabilities.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"volumes\": { SchemaProps: spec.SchemaProps{ Description: \"volumes is an allowlist of volume plugins. Empty indicates that no volumes may be used. To allow all volumes you may use '*'.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"hostNetwork\": { SchemaProps: spec.SchemaProps{ Description: \"hostNetwork determines if the policy allows the use of HostNetwork in the pod spec.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"hostPorts\": { SchemaProps: spec.SchemaProps{ Description: \"hostPorts determines which host port ranges are allowed to be exposed.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/policy/v1beta1.HostPortRange\"), }, }, }, }, }, \"hostPID\": { SchemaProps: spec.SchemaProps{ Description: \"hostPID determines if the policy allows the use of HostPID in the pod spec.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"hostIPC\": { SchemaProps: spec.SchemaProps{ Description: \"hostIPC determines if the policy allows the use of HostIPC in the pod spec.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"seLinux\": { SchemaProps: spec.SchemaProps{ Description: \"seLinux is the strategy that will dictate the allowable labels that may be set.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/policy/v1beta1.SELinuxStrategyOptions\"), }, }, \"runAsUser\": { SchemaProps: spec.SchemaProps{ Description: \"runAsUser is the strategy that will dictate the allowable RunAsUser values that may be set.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/policy/v1beta1.RunAsUserStrategyOptions\"), }, }, \"runAsGroup\": { SchemaProps: spec.SchemaProps{ Description: \"RunAsGroup is the strategy that will dictate the allowable RunAsGroup values that may be set. If this field is omitted, the pod's RunAsGroup can take any value. This field requires the RunAsGroup feature gate to be enabled.\", Ref:         ref(\"k8s.io/api/policy/v1beta1.RunAsGroupStrategyOptions\"), }, }, \"supplementalGroups\": { SchemaProps: spec.SchemaProps{ Description: \"supplementalGroups is the strategy that will dictate what supplemental groups are used by the SecurityContext.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/policy/v1beta1.SupplementalGroupsStrategyOptions\"), }, }, \"fsGroup\": { SchemaProps: spec.SchemaProps{ Description: \"fsGroup is the strategy that will dictate what fs group is used by the SecurityContext.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/policy/v1beta1.FSGroupStrategyOptions\"), }, }, \"readOnlyRootFilesystem\": { SchemaProps: spec.SchemaProps{ Description: \"readOnlyRootFilesystem when set to true will force containers to run with a read only root file system.  If the container specifically requests to run with a non-read only root file system the PSP should deny the pod. If set to false the container may run with a read only root file system if it wishes but it will not be forced to.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"defaultAllowPrivilegeEscalation\": { SchemaProps: spec.SchemaProps{ Description: \"defaultAllowPrivilegeEscalation controls the default setting for whether a process can gain more privileges than its parent process.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"allowPrivilegeEscalation\": { SchemaProps: spec.SchemaProps{ Description: \"allowPrivilegeEscalation determines if a pod can request to allow privilege escalation. If unspecified, defaults to true.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"allowedHostPaths\": { SchemaProps: spec.SchemaProps{ Description: \"allowedHostPaths is an allowlist of host paths. Empty indicates that all host paths may be used.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/policy/v1beta1.AllowedHostPath\"), }, }, }, }, }, \"allowedFlexVolumes\": { SchemaProps: spec.SchemaProps{ Description: \"allowedFlexVolumes is an allowlist of Flexvolumes.  Empty or nil indicates that all Flexvolumes may be used.  This parameter is effective only when the usage of the Flexvolumes is allowed in the \"volumes\" field.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/policy/v1beta1.AllowedFlexVolume\"), }, }, }, }, }, \"allowedCSIDrivers\": { SchemaProps: spec.SchemaProps{ Description: \"AllowedCSIDrivers is an allowlist of inline CSI drivers that must be explicitly set to be embedded within a pod spec. An empty value indicates that any CSI driver can be used for inline ephemeral volumes. This is a beta field, and is only honored if the API server enables the CSIInlineVolume feature gate.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/policy/v1beta1.AllowedCSIDriver\"), }, }, }, }, }, \"allowedUnsafeSysctls\": { SchemaProps: spec.SchemaProps{ Description: \"allowedUnsafeSysctls is a list of explicitly allowed unsafe sysctls, defaults to none. Each entry is either a plain sysctl name or ends in \"*\" in which case it is considered as a prefix of allowed sysctls. Single * means all unsafe sysctls are allowed. Kubelet has to allowlist all allowed unsafe sysctls explicitly to avoid rejection.nnExamples: e.g. \"foo/*\" allows \"foo/bar\", \"foo/baz\", etc. e.g. \"foo.*\" allows \"foo.bar\", \"foo.baz\", etc.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"forbiddenSysctls\": { SchemaProps: spec.SchemaProps{ Description: \"forbiddenSysctls is a list of explicitly forbidden sysctls, defaults to none. Each entry is either a plain sysctl name or ends in \"*\" in which case it is considered as a prefix of forbidden sysctls. Single * means all sysctls are forbidden.nnExamples: e.g. \"foo/*\" forbids \"foo/bar\", \"foo/baz\", etc. e.g. \"foo.*\" forbids \"foo.bar\", \"foo.baz\", etc.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"allowedProcMountTypes\": { SchemaProps: spec.SchemaProps{ Description: \"AllowedProcMountTypes is an allowlist of allowed ProcMountTypes. Empty or nil indicates that only the DefaultProcMountType may be used. This requires the ProcMountType feature flag to be enabled.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"runtimeClass\": { SchemaProps: spec.SchemaProps{ Description: \"runtimeClass is the strategy that will dictate the allowable RuntimeClasses for a pod. If this field is omitted, the pod's runtimeClassName field is unrestricted. Enforcement of this field depends on the RuntimeClass feature gate being enabled.\", Ref:         ref(\"k8s.io/api/policy/v1beta1.RuntimeClassStrategyOptions\"), }, }, }, Required: []string{\"seLinux\", \"runAsUser\", \"supplementalGroups\", \"fsGroup\"}, }, }, Dependencies: []string{ \"k8s.io/api/policy/v1beta1.AllowedCSIDriver\", \"k8s.io/api/policy/v1beta1.AllowedFlexVolume\", \"k8s.io/api/policy/v1beta1.AllowedHostPath\", \"k8s.io/api/policy/v1beta1.FSGroupStrategyOptions\", \"k8s.io/api/policy/v1beta1.HostPortRange\", \"k8s.io/api/policy/v1beta1.RunAsGroupStrategyOptions\", \"k8s.io/api/policy/v1beta1.RunAsUserStrategyOptions\", \"k8s.io/api/policy/v1beta1.RuntimeClassStrategyOptions\", \"k8s.io/api/policy/v1beta1.SELinuxStrategyOptions\", \"k8s.io/api/policy/v1beta1.SupplementalGroupsStrategyOptions\"}, } } func schema_k8sio_api_policy_v1beta1_RunAsGroupStrategyOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RunAsGroupStrategyOptions defines the strategy type and any options used to create the strategy.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"rule\": { SchemaProps: spec.SchemaProps{ Description: \"rule is the strategy that will dictate the allowable RunAsGroup values that may be set.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ranges\": { SchemaProps: spec.SchemaProps{ Description: \"ranges are the allowed ranges of gids that may be used. If you would like to force a single gid then supply a single range with the same start and end. Required for MustRunAs.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/policy/v1beta1.IDRange\"), }, }, }, }, }, }, Required: []string{\"rule\"}, }, }, Dependencies: []string{ \"k8s.io/api/policy/v1beta1.IDRange\"}, } } func schema_k8sio_api_policy_v1beta1_RunAsUserStrategyOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RunAsUserStrategyOptions defines the strategy type and any options used to create the strategy.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"rule\": { SchemaProps: spec.SchemaProps{ Description: \"rule is the strategy that will dictate the allowable RunAsUser values that may be set.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ranges\": { SchemaProps: spec.SchemaProps{ Description: \"ranges are the allowed ranges of uids that may be used. If you would like to force a single uid then supply a single range with the same start and end. Required for MustRunAs.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/policy/v1beta1.IDRange\"), }, }, }, }, }, }, Required: []string{\"rule\"}, }, }, Dependencies: []string{ \"k8s.io/api/policy/v1beta1.IDRange\"}, } } func schema_k8sio_api_policy_v1beta1_RuntimeClassStrategyOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RuntimeClassStrategyOptions define the strategy that will dictate the allowable RuntimeClasses for a pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"allowedRuntimeClassNames\": { SchemaProps: spec.SchemaProps{ Description: \"allowedRuntimeClassNames is an allowlist of RuntimeClass names that may be specified on a pod. A value of \"*\" means that any RuntimeClass name is allowed, and must be the only item in the list. An empty list requires the RuntimeClassName field to be unset.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"defaultRuntimeClassName\": { SchemaProps: spec.SchemaProps{ Description: \"defaultRuntimeClassName is the default RuntimeClassName to set on the pod. The default MUST be allowed by the allowedRuntimeClassNames list. A value of nil does not mutate the Pod.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"allowedRuntimeClassNames\"}, }, }, } } func schema_k8sio_api_policy_v1beta1_SELinuxStrategyOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SELinuxStrategyOptions defines the strategy type and any options used to create the strategy.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"rule\": { SchemaProps: spec.SchemaProps{ Description: \"rule is the strategy that will dictate the allowable labels that may be set.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"seLinuxOptions\": { SchemaProps: spec.SchemaProps{ Description: \"seLinuxOptions required to run as; required for MustRunAs More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/\", Ref:         ref(\"k8s.io/api/core/v1.SELinuxOptions\"), }, }, }, Required: []string{\"rule\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.SELinuxOptions\"}, } } func schema_k8sio_api_policy_v1beta1_SupplementalGroupsStrategyOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SupplementalGroupsStrategyOptions defines the strategy type and options used to create the strategy.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"rule\": { SchemaProps: spec.SchemaProps{ Description: \"rule is the strategy that will dictate what supplemental groups is used in the SecurityContext.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ranges\": { SchemaProps: spec.SchemaProps{ Description: \"ranges are the allowed ranges of supplemental groups.  If you would like to force a single supplemental group then supply a single range with the same start and end. Required for MustRunAs.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/policy/v1beta1.IDRange\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/policy/v1beta1.IDRange\"}, } } func schema_k8sio_api_rbac_v1_AggregationRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"AggregationRule describes how to locate ClusterRoles to aggregate into the ClusterRole\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"clusterRoleSelectors\": { SchemaProps: spec.SchemaProps{ Description: \"ClusterRoleSelectors holds a list of selectors which will be used to find ClusterRoles and create the rules. If any of the selectors match, then the ClusterRole's permissions will be added\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_rbac_v1_ClusterRole(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ClusterRole is a cluster level, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding or ClusterRoleBinding.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"rules\": { SchemaProps: spec.SchemaProps{ Description: \"Rules holds all the PolicyRules for this ClusterRole\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1.PolicyRule\"), }, }, }, }, }, \"aggregationRule\": { SchemaProps: spec.SchemaProps{ Description: \"AggregationRule is an optional field that describes how to build the Rules for this ClusterRole. If AggregationRule is set, then the Rules are controller managed and direct changes to Rules will be stomped by the controller.\", Ref:         ref(\"k8s.io/api/rbac/v1.AggregationRule\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1.AggregationRule\", \"k8s.io/api/rbac/v1.PolicyRule\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_rbac_v1_ClusterRoleBinding(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ClusterRoleBinding references a ClusterRole, but not contain it.  It can reference a ClusterRole in the global namespace, and adds who information via Subject.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"subjects\": { SchemaProps: spec.SchemaProps{ Description: \"Subjects holds references to the objects the role applies to.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1.Subject\"), }, }, }, }, }, \"roleRef\": { SchemaProps: spec.SchemaProps{ Description: \"RoleRef can only reference a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/rbac/v1.RoleRef\"), }, }, }, Required: []string{\"roleRef\"}, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1.RoleRef\", \"k8s.io/api/rbac/v1.Subject\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_rbac_v1_ClusterRoleBindingList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ClusterRoleBindingList is a collection of ClusterRoleBindings\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of ClusterRoleBindings\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1.ClusterRoleBinding\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1.ClusterRoleBinding\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_rbac_v1_ClusterRoleList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ClusterRoleList is a collection of ClusterRoles\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of ClusterRoles\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1.ClusterRole\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1.ClusterRole\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_rbac_v1_PolicyRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PolicyRule holds information that describes a policy rule, but does not contain information about who the rule applies to or which namespace the rule applies to.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"verbs\": { SchemaProps: spec.SchemaProps{ Description: \"Verbs is a list of Verbs that apply to ALL the ResourceKinds contained in this rule. '*' represents all verbs.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"apiGroups\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroups is the name of the APIGroup that contains the resources.  If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"Resources is a list of resources this rule applies to. '*' represents all resources.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resourceNames\": { SchemaProps: spec.SchemaProps{ Description: \"ResourceNames is an optional white list of names that the rule applies to.  An empty set means that everything is allowed.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"nonResourceURLs\": { SchemaProps: spec.SchemaProps{ Description: \"NonResourceURLs is a set of partial urls that a user should have access to.  *s are allowed, but only as the full, final step in the path Since non-resource URLs are not namespaced, this field is only applicable for ClusterRoles referenced from a ClusterRoleBinding. Rules can either apply to API resources (such as \"pods\" or \"secrets\") or non-resource URL paths (such as \"/api\"),  but not both.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"verbs\"}, }, }, } } func schema_k8sio_api_rbac_v1_Role(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Role is a namespaced, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"rules\": { SchemaProps: spec.SchemaProps{ Description: \"Rules holds all the PolicyRules for this Role\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1.PolicyRule\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1.PolicyRule\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_rbac_v1_RoleBinding(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RoleBinding references a role, but does not contain it.  It can reference a Role in the same namespace or a ClusterRole in the global namespace. It adds who information via Subjects and namespace information by which namespace it exists in.  RoleBindings in a given namespace only have effect in that namespace.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"subjects\": { SchemaProps: spec.SchemaProps{ Description: \"Subjects holds references to the objects the role applies to.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1.Subject\"), }, }, }, }, }, \"roleRef\": { SchemaProps: spec.SchemaProps{ Description: \"RoleRef can reference a Role in the current namespace or a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/rbac/v1.RoleRef\"), }, }, }, Required: []string{\"roleRef\"}, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1.RoleRef\", \"k8s.io/api/rbac/v1.Subject\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_rbac_v1_RoleBindingList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RoleBindingList is a collection of RoleBindings\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of RoleBindings\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1.RoleBinding\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1.RoleBinding\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_rbac_v1_RoleList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RoleList is a collection of Roles\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of Roles\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1.Role\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1.Role\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_rbac_v1_RoleRef(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RoleRef contains information that points to the role being used\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"apiGroup\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroup is the group for the resource being referenced\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is the type of resource being referenced\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the name of resource being referenced\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"apiGroup\", \"kind\", \"name\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, } } func schema_k8sio_api_rbac_v1_Subject(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Subject contains a reference to the object or user identities a role binding applies to.  This can either hold a direct API object reference, or a value for non-objects such as user and group names.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind of object being referenced. Values defined by this API group are \"User\", \"Group\", and \"ServiceAccount\". If the Authorizer does not recognized the kind value, the Authorizer should report an error.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiGroup\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroup holds the API group of the referenced subject. Defaults to \"\" for ServiceAccount subjects. Defaults to \"rbac.authorization.k8s.io\" for User and Group subjects.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the object being referenced.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"Namespace of the referenced object.  If the object kind is non-namespace, such as \"User\" or \"Group\", and this value is not empty the Authorizer should report an error.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"kind\", \"name\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, } } func schema_k8sio_api_rbac_v1alpha1_AggregationRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"AggregationRule describes how to locate ClusterRoles to aggregate into the ClusterRole\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"clusterRoleSelectors\": { SchemaProps: spec.SchemaProps{ Description: \"ClusterRoleSelectors holds a list of selectors which will be used to find ClusterRoles and create the rules. If any of the selectors match, then the ClusterRole's permissions will be added\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_rbac_v1alpha1_ClusterRole(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ClusterRole is a cluster level, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding or ClusterRoleBinding. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 ClusterRole, and will no longer be served in v1.22.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"rules\": { SchemaProps: spec.SchemaProps{ Description: \"Rules holds all the PolicyRules for this ClusterRole\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1alpha1.PolicyRule\"), }, }, }, }, }, \"aggregationRule\": { SchemaProps: spec.SchemaProps{ Description: \"AggregationRule is an optional field that describes how to build the Rules for this ClusterRole. If AggregationRule is set, then the Rules are controller managed and direct changes to Rules will be stomped by the controller.\", Ref:         ref(\"k8s.io/api/rbac/v1alpha1.AggregationRule\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1alpha1.AggregationRule\", \"k8s.io/api/rbac/v1alpha1.PolicyRule\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_rbac_v1alpha1_ClusterRoleBinding(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ClusterRoleBinding references a ClusterRole, but not contain it.  It can reference a ClusterRole in the global namespace, and adds who information via Subject. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 ClusterRoleBinding, and will no longer be served in v1.22.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"subjects\": { SchemaProps: spec.SchemaProps{ Description: \"Subjects holds references to the objects the role applies to.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1alpha1.Subject\"), }, }, }, }, }, \"roleRef\": { SchemaProps: spec.SchemaProps{ Description: \"RoleRef can only reference a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/rbac/v1alpha1.RoleRef\"), }, }, }, Required: []string{\"roleRef\"}, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1alpha1.RoleRef\", \"k8s.io/api/rbac/v1alpha1.Subject\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_rbac_v1alpha1_ClusterRoleBindingList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ClusterRoleBindingList is a collection of ClusterRoleBindings. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 ClusterRoleBindings, and will no longer be served in v1.22.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of ClusterRoleBindings\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1alpha1.ClusterRoleBinding\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1alpha1.ClusterRoleBinding\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_rbac_v1alpha1_ClusterRoleList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ClusterRoleList is a collection of ClusterRoles. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 ClusterRoles, and will no longer be served in v1.22.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of ClusterRoles\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1alpha1.ClusterRole\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1alpha1.ClusterRole\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_rbac_v1alpha1_PolicyRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PolicyRule holds information that describes a policy rule, but does not contain information about who the rule applies to or which namespace the rule applies to.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"verbs\": { SchemaProps: spec.SchemaProps{ Description: \"Verbs is a list of Verbs that apply to ALL the ResourceKinds contained in this rule. '*' represents all verbs.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"apiGroups\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroups is the name of the APIGroup that contains the resources.  If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"Resources is a list of resources this rule applies to. '*' represents all resources.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resourceNames\": { SchemaProps: spec.SchemaProps{ Description: \"ResourceNames is an optional white list of names that the rule applies to.  An empty set means that everything is allowed.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"nonResourceURLs\": { SchemaProps: spec.SchemaProps{ Description: \"NonResourceURLs is a set of partial urls that a user should have access to.  *s are allowed, but only as the full, final step in the path Since non-resource URLs are not namespaced, this field is only applicable for ClusterRoles referenced from a ClusterRoleBinding. Rules can either apply to API resources (such as \"pods\" or \"secrets\") or non-resource URL paths (such as \"/api\"),  but not both.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"verbs\"}, }, }, } } func schema_k8sio_api_rbac_v1alpha1_Role(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Role is a namespaced, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 Role, and will no longer be served in v1.22.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"rules\": { SchemaProps: spec.SchemaProps{ Description: \"Rules holds all the PolicyRules for this Role\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1alpha1.PolicyRule\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1alpha1.PolicyRule\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_rbac_v1alpha1_RoleBinding(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RoleBinding references a role, but does not contain it.  It can reference a Role in the same namespace or a ClusterRole in the global namespace. It adds who information via Subjects and namespace information by which namespace it exists in.  RoleBindings in a given namespace only have effect in that namespace. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 RoleBinding, and will no longer be served in v1.22.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"subjects\": { SchemaProps: spec.SchemaProps{ Description: \"Subjects holds references to the objects the role applies to.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1alpha1.Subject\"), }, }, }, }, }, \"roleRef\": { SchemaProps: spec.SchemaProps{ Description: \"RoleRef can reference a Role in the current namespace or a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/rbac/v1alpha1.RoleRef\"), }, }, }, Required: []string{\"roleRef\"}, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1alpha1.RoleRef\", \"k8s.io/api/rbac/v1alpha1.Subject\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_rbac_v1alpha1_RoleBindingList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RoleBindingList is a collection of RoleBindings Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 RoleBindingList, and will no longer be served in v1.22.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of RoleBindings\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1alpha1.RoleBinding\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1alpha1.RoleBinding\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_rbac_v1alpha1_RoleList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RoleList is a collection of Roles. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 RoleList, and will no longer be served in v1.22.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of Roles\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1alpha1.Role\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1alpha1.Role\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_rbac_v1alpha1_RoleRef(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RoleRef contains information that points to the role being used\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"apiGroup\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroup is the group for the resource being referenced\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is the type of resource being referenced\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the name of resource being referenced\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"apiGroup\", \"kind\", \"name\"}, }, }, } } func schema_k8sio_api_rbac_v1alpha1_Subject(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Subject contains a reference to the object or user identities a role binding applies to.  This can either hold a direct API object reference, or a value for non-objects such as user and group names.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind of object being referenced. Values defined by this API group are \"User\", \"Group\", and \"ServiceAccount\". If the Authorizer does not recognized the kind value, the Authorizer should report an error.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion holds the API group and version of the referenced subject. Defaults to \"v1\" for ServiceAccount subjects. Defaults to \"rbac.authorization.k8s.io/v1alpha1\" for User and Group subjects.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the object being referenced.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"Namespace of the referenced object.  If the object kind is non-namespace, such as \"User\" or \"Group\", and this value is not empty the Authorizer should report an error.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"kind\", \"name\"}, }, }, } } func schema_k8sio_api_rbac_v1beta1_AggregationRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"AggregationRule describes how to locate ClusterRoles to aggregate into the ClusterRole\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"clusterRoleSelectors\": { SchemaProps: spec.SchemaProps{ Description: \"ClusterRoleSelectors holds a list of selectors which will be used to find ClusterRoles and create the rules. If any of the selectors match, then the ClusterRole's permissions will be added\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_k8sio_api_rbac_v1beta1_ClusterRole(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ClusterRole is a cluster level, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding or ClusterRoleBinding. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 ClusterRole, and will no longer be served in v1.22.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"rules\": { SchemaProps: spec.SchemaProps{ Description: \"Rules holds all the PolicyRules for this ClusterRole\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1beta1.PolicyRule\"), }, }, }, }, }, \"aggregationRule\": { SchemaProps: spec.SchemaProps{ Description: \"AggregationRule is an optional field that describes how to build the Rules for this ClusterRole. If AggregationRule is set, then the Rules are controller managed and direct changes to Rules will be stomped by the controller.\", Ref:         ref(\"k8s.io/api/rbac/v1beta1.AggregationRule\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1beta1.AggregationRule\", \"k8s.io/api/rbac/v1beta1.PolicyRule\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_rbac_v1beta1_ClusterRoleBinding(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ClusterRoleBinding references a ClusterRole, but not contain it.  It can reference a ClusterRole in the global namespace, and adds who information via Subject. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 ClusterRoleBinding, and will no longer be served in v1.22.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"subjects\": { SchemaProps: spec.SchemaProps{ Description: \"Subjects holds references to the objects the role applies to.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1beta1.Subject\"), }, }, }, }, }, \"roleRef\": { SchemaProps: spec.SchemaProps{ Description: \"RoleRef can only reference a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/rbac/v1beta1.RoleRef\"), }, }, }, Required: []string{\"roleRef\"}, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1beta1.RoleRef\", \"k8s.io/api/rbac/v1beta1.Subject\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_rbac_v1beta1_ClusterRoleBindingList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ClusterRoleBindingList is a collection of ClusterRoleBindings. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 ClusterRoleBindingList, and will no longer be served in v1.22.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of ClusterRoleBindings\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1beta1.ClusterRoleBinding\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1beta1.ClusterRoleBinding\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_rbac_v1beta1_ClusterRoleList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ClusterRoleList is a collection of ClusterRoles. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 ClusterRoles, and will no longer be served in v1.22.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of ClusterRoles\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1beta1.ClusterRole\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1beta1.ClusterRole\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_rbac_v1beta1_PolicyRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PolicyRule holds information that describes a policy rule, but does not contain information about who the rule applies to or which namespace the rule applies to.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"verbs\": { SchemaProps: spec.SchemaProps{ Description: \"Verbs is a list of Verbs that apply to ALL the ResourceKinds contained in this rule. '*' represents all verbs.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"apiGroups\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroups is the name of the APIGroup that contains the resources.  If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"Resources is a list of resources this rule applies to.  '*' represents all resources in the specified apiGroups. '*/foo' represents the subresource 'foo' for all resources in the specified apiGroups.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resourceNames\": { SchemaProps: spec.SchemaProps{ Description: \"ResourceNames is an optional white list of names that the rule applies to.  An empty set means that everything is allowed.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"nonResourceURLs\": { SchemaProps: spec.SchemaProps{ Description: \"NonResourceURLs is a set of partial urls that a user should have access to.  *s are allowed, but only as the full, final step in the path Since non-resource URLs are not namespaced, this field is only applicable for ClusterRoles referenced from a ClusterRoleBinding. Rules can either apply to API resources (such as \"pods\" or \"secrets\") or non-resource URL paths (such as \"/api\"),  but not both.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"verbs\"}, }, }, } } func schema_k8sio_api_rbac_v1beta1_Role(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Role is a namespaced, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 Role, and will no longer be served in v1.22.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"rules\": { SchemaProps: spec.SchemaProps{ Description: \"Rules holds all the PolicyRules for this Role\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1beta1.PolicyRule\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1beta1.PolicyRule\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_rbac_v1beta1_RoleBinding(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RoleBinding references a role, but does not contain it.  It can reference a Role in the same namespace or a ClusterRole in the global namespace. It adds who information via Subjects and namespace information by which namespace it exists in.  RoleBindings in a given namespace only have effect in that namespace. Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 RoleBinding, and will no longer be served in v1.22.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"subjects\": { SchemaProps: spec.SchemaProps{ Description: \"Subjects holds references to the objects the role applies to.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1beta1.Subject\"), }, }, }, }, }, \"roleRef\": { SchemaProps: spec.SchemaProps{ Description: \"RoleRef can reference a Role in the current namespace or a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/rbac/v1beta1.RoleRef\"), }, }, }, Required: []string{\"roleRef\"}, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1beta1.RoleRef\", \"k8s.io/api/rbac/v1beta1.Subject\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_rbac_v1beta1_RoleBindingList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RoleBindingList is a collection of RoleBindings Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 RoleBindingList, and will no longer be served in v1.22.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of RoleBindings\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1beta1.RoleBinding\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1beta1.RoleBinding\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_rbac_v1beta1_RoleList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RoleList is a collection of Roles Deprecated in v1.17 in favor of rbac.authorization.k8s.io/v1 RoleList, and will no longer be served in v1.22.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is a list of Roles\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/rbac/v1beta1.Role\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/rbac/v1beta1.Role\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_rbac_v1beta1_RoleRef(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RoleRef contains information that points to the role being used\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"apiGroup\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroup is the group for the resource being referenced\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is the type of resource being referenced\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the name of resource being referenced\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"apiGroup\", \"kind\", \"name\"}, }, }, } } func schema_k8sio_api_rbac_v1beta1_Subject(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Subject contains a reference to the object or user identities a role binding applies to.  This can either hold a direct API object reference, or a value for non-objects such as user and group names.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind of object being referenced. Values defined by this API group are \"User\", \"Group\", and \"ServiceAccount\". If the Authorizer does not recognized the kind value, the Authorizer should report an error.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiGroup\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroup holds the API group of the referenced subject. Defaults to \"\" for ServiceAccount subjects. Defaults to \"rbac.authorization.k8s.io\" for User and Group subjects.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the object being referenced.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"Namespace of the referenced object.  If the object kind is non-namespace, such as \"User\" or \"Group\", and this value is not empty the Authorizer should report an error.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"kind\", \"name\"}, }, }, } } func schema_k8sio_api_scheduling_v1_PriorityClass(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityClass defines mapping from a priority class name to the priority integer value. The value can be any valid integer.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"value\": { SchemaProps: spec.SchemaProps{ Description: \"The value of this priority class. This is the actual priority that pods receive when they have the name of this class in their pod spec.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"globalDefault\": { SchemaProps: spec.SchemaProps{ Description: \"globalDefault specifies whether this PriorityClass should be considered as the default priority for pods that do not have any priority class. Only one PriorityClass can be marked as `globalDefault`. However, if more than one PriorityClasses exists with their `globalDefault` field set to true, the smallest value of such global default PriorityClasses will be used as the default priority.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"description\": { SchemaProps: spec.SchemaProps{ Description: \"description is an arbitrary string that usually provides guidelines on when this priority class should be used.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"preemptionPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"PreemptionPolicy is the Policy for preempting pods with lower priority. One of Never, PreemptLowerPriority. Defaults to PreemptLowerPriority if unset.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"value\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_scheduling_v1_PriorityClassList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityClassList is a collection of priority classes.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is the list of PriorityClasses\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/scheduling/v1.PriorityClass\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/scheduling/v1.PriorityClass\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_scheduling_v1alpha1_PriorityClass(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED - This group version of PriorityClass is deprecated by scheduling.k8s.io/v1/PriorityClass. PriorityClass defines mapping from a priority class name to the priority integer value. The value can be any valid integer.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"value\": { SchemaProps: spec.SchemaProps{ Description: \"The value of this priority class. This is the actual priority that pods receive when they have the name of this class in their pod spec.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"globalDefault\": { SchemaProps: spec.SchemaProps{ Description: \"globalDefault specifies whether this PriorityClass should be considered as the default priority for pods that do not have any priority class. Only one PriorityClass can be marked as `globalDefault`. However, if more than one PriorityClasses exists with their `globalDefault` field set to true, the smallest value of such global default PriorityClasses will be used as the default priority.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"description\": { SchemaProps: spec.SchemaProps{ Description: \"description is an arbitrary string that usually provides guidelines on when this priority class should be used.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"preemptionPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"PreemptionPolicy is the Policy for preempting pods with lower priority. One of Never, PreemptLowerPriority. Defaults to PreemptLowerPriority if unset.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"value\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_scheduling_v1alpha1_PriorityClassList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityClassList is a collection of priority classes.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is the list of PriorityClasses\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/scheduling/v1alpha1.PriorityClass\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/scheduling/v1alpha1.PriorityClass\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_scheduling_v1beta1_PriorityClass(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED - This group version of PriorityClass is deprecated by scheduling.k8s.io/v1/PriorityClass. PriorityClass defines mapping from a priority class name to the priority integer value. The value can be any valid integer.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"value\": { SchemaProps: spec.SchemaProps{ Description: \"The value of this priority class. This is the actual priority that pods receive when they have the name of this class in their pod spec.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"globalDefault\": { SchemaProps: spec.SchemaProps{ Description: \"globalDefault specifies whether this PriorityClass should be considered as the default priority for pods that do not have any priority class. Only one PriorityClass can be marked as `globalDefault`. However, if more than one PriorityClasses exists with their `globalDefault` field set to true, the smallest value of such global default PriorityClasses will be used as the default priority.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"description\": { SchemaProps: spec.SchemaProps{ Description: \"description is an arbitrary string that usually provides guidelines on when this priority class should be used.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"preemptionPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"PreemptionPolicy is the Policy for preempting pods with lower priority. One of Never, PreemptLowerPriority. Defaults to PreemptLowerPriority if unset.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"value\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_scheduling_v1beta1_PriorityClassList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PriorityClassList is a collection of priority classes.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is the list of PriorityClasses\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/scheduling/v1beta1.PriorityClass\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/scheduling/v1beta1.PriorityClass\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_storage_v1_CSIDriver(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CSIDriver captures information about a Container Storage Interface (CSI) volume driver deployed on the cluster. Kubernetes attach detach controller uses this object to determine whether attach is required. Kubelet uses this object to determine whether pod information needs to be passed on mount. CSIDriver objects are non-namespaced.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object metadata. metadata.Name indicates the name of the CSI driver that this object refers to; it MUST be the same name returned by the CSI GetPluginName() call for that driver. The driver name must be 63 characters or less, beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with dashes (-), dots (.), and alphanumerics between. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the CSI Driver.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/storage/v1.CSIDriverSpec\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1.CSIDriverSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_storage_v1_CSIDriverList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CSIDriverList is a collection of CSIDriver objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is the list of CSIDriver\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/storage/v1.CSIDriver\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1.CSIDriver\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_storage_v1_CSIDriverSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CSIDriverSpec is the specification of a CSIDriver.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"attachRequired\": { SchemaProps: spec.SchemaProps{ Description: \"attachRequired indicates this CSI volume driver requires an attach operation (because it implements the CSI ControllerPublishVolume() method), and that the Kubernetes attach detach controller should call the attach volume interface which checks the volumeattachment status and waits until the volume is attached before proceeding to mounting. The CSI external-attacher coordinates with CSI volume driver and updates the volumeattachment status when the attach operation is complete. If the CSIDriverRegistry feature gate is enabled and the value is specified to false, the attach operation will be skipped. Otherwise the attach operation will be called.nnThis field is immutable.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"podInfoOnMount\": { SchemaProps: spec.SchemaProps{ Description: \"If set to true, podInfoOnMount indicates this CSI volume driver requires additional pod information (like podName, podUID, etc.) during mount operations. If set to false, pod information will not be passed on mount. Default is false. The CSI driver specifies podInfoOnMount as part of driver deployment. If true, Kubelet will pass pod information as VolumeContext in the CSI NodePublishVolume() calls. The CSI driver is responsible for parsing and validating the information passed in as VolumeContext. The following VolumeConext will be passed if podInfoOnMount is set to true. This list might grow, but the prefix will be used. \"csi.storage.k8s.io/pod.name\": pod.Name \"csi.storage.k8s.io/pod.namespace\": pod.Namespace \"csi.storage.k8s.io/pod.uid\": string(pod.UID) \"csi.storage.k8s.io/ephemeral\": \"true\" if the volume is an ephemeral inline volumen                                defined by a CSIVolumeSource, otherwise \"false\"nn\"csi.storage.k8s.io/ephemeral\" is a new feature in Kubernetes 1.16. It is only required for drivers which support both the \"Persistent\" and \"Ephemeral\" VolumeLifecycleMode. Other drivers can leave pod info disabled and/or ignore this field. As Kubernetes 1.15 doesn't support this field, drivers can only support one mode when deployed on such a cluster and the deployment determines which mode that is, for example via a command line parameter of the driver.nnThis field is immutable.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"volumeLifecycleModes\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"volumeLifecycleModes defines what kind of volumes this CSI volume driver supports. The default if the list is empty is \"Persistent\", which is the usage defined by the CSI specification and implemented in Kubernetes via the usual PV/PVC mechanism. The other mode is \"Ephemeral\". In this mode, volumes are defined inline inside the pod spec with CSIVolumeSource and their lifecycle is tied to the lifecycle of that pod. A driver has to be aware of this because it is only going to get a NodePublishVolume call for such a volume. For more information about implementing this mode, see https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html A driver can support one or more of these modes and more modes may be added in the future. This field is beta.nnThis field is immutable.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"storageCapacity\": { SchemaProps: spec.SchemaProps{ Description: \"If set to true, storageCapacity indicates that the CSI volume driver wants pod scheduling to consider the storage capacity that the driver deployment will report by creating CSIStorageCapacity objects with capacity information.nnThe check can be enabled immediately when deploying a driver. In that case, provisioning new volumes with late binding will pause until the driver deployment has published some suitable CSIStorageCapacity object.nnAlternatively, the driver can be deployed with the field unset or false and it can be flipped later when storage capacity information has been published.nnThis field was immutable in Kubernetes <= 1.22 and now is mutable.nnThis is a beta field and only available when the CSIStorageCapacity feature is enabled. The default is false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"fsGroupPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"Defines if the underlying volume supports changing ownership and permission of the volume before being mounted. Refer to the specific FSGroupPolicy values for additional details.nnThis field is immutable.nnDefaults to ReadWriteOnceWithFSType, which will examine each volume to determine if Kubernetes should modify ownership and permissions of the volume. With the default policy the defined fsGroup will only be applied if a fstype is defined and the volume's access mode contains ReadWriteOnce.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"tokenRequests\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"TokenRequests indicates the CSI driver needs pods' service account tokens it is mounting volume for to do necessary authentication. Kubelet will pass the tokens in VolumeContext in the CSI NodePublishVolume calls. The CSI driver should parse and validate the following VolumeContext: \"csi.storage.k8s.io/serviceAccount.tokens\": {n  \"<audience>\": {n    \"token\": <token>,n    \"expirationTimestamp\": <expiration timestamp in RFC3339>,n  },n  ...n}nnNote: Audience in each TokenRequest should be different and at most one token is empty string. To receive a new token after expiry, RequiresRepublish can be used to trigger NodePublishVolume periodically.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/storage/v1.TokenRequest\"), }, }, }, }, }, \"requiresRepublish\": { SchemaProps: spec.SchemaProps{ Description: \"RequiresRepublish indicates the CSI driver wants `NodePublishVolume` being periodically called to reflect any possible change in the mounted volume. This field defaults to false.nnNote: After a successful initial NodePublishVolume call, subsequent calls to NodePublishVolume should only update the contents of the volume. New mount points will not be seen by a running container.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1.TokenRequest\"}, } } func schema_k8sio_api_storage_v1_CSINode(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CSINode holds information about all CSI drivers installed on a node. CSI drivers do not need to create the CSINode object directly. As long as they use the node-driver-registrar sidecar container, the kubelet will automatically populate the CSINode object for the CSI driver as part of kubelet plugin registration. CSINode has the same name as a node. If the object is missing, it means either there are no CSI Drivers available on the node, or the Kubelet version is low enough that it doesn't create this object. CSINode has an OwnerReference that points to the corresponding node object.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"metadata.name must be the Kubernetes node name.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"spec is the specification of CSINode\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/storage/v1.CSINodeSpec\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1.CSINodeSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_storage_v1_CSINodeDriver(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CSINodeDriver holds information about the specification of one CSI driver installed on a node\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"This is the name of the CSI driver that this object refers to. This MUST be the same name returned by the CSI GetPluginName() call for that driver.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"nodeID\": { SchemaProps: spec.SchemaProps{ Description: \"nodeID of the node from the driver point of view. This field enables Kubernetes to communicate with storage systems that do not share the same nomenclature for nodes. For example, Kubernetes may refer to a given node as \"node1\", but the storage system may refer to the same node as \"nodeA\". When Kubernetes issues a command to the storage system to attach a volume to a specific node, it can use this field to refer to the node name using the ID that the storage system will understand, e.g. \"nodeA\" instead of \"node1\". This field is required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"topologyKeys\": { SchemaProps: spec.SchemaProps{ Description: \"topologyKeys is the list of keys supported by the driver. When a driver is initialized on a cluster, it provides a set of topology keys that it understands (e.g. \"company.com/zone\", \"company.com/region\"). When a driver is initialized on a node, it provides the same topology keys along with values. Kubelet will expose these topology keys as labels on its own node object. When Kubernetes does topology aware provisioning, it can use this list to determine which labels it should retrieve from the node object and pass back to the driver. It is possible for different nodes to use different topology keys. This can be empty if driver does not support topology.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"allocatable\": { SchemaProps: spec.SchemaProps{ Description: \"allocatable represents the volume resources of a node that are available for scheduling. This field is beta.\", Ref:         ref(\"k8s.io/api/storage/v1.VolumeNodeResources\"), }, }, }, Required: []string{\"name\", \"nodeID\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1.VolumeNodeResources\"}, } } func schema_k8sio_api_storage_v1_CSINodeList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CSINodeList is a collection of CSINode objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is the list of CSINode\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/storage/v1.CSINode\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1.CSINode\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_storage_v1_CSINodeSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CSINodeSpec holds information about the specification of all CSI drivers installed on a node\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"drivers\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"name\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"drivers is a list of information of all CSI Drivers existing on a node. If all drivers in the list are uninstalled, this can become empty.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/storage/v1.CSINodeDriver\"), }, }, }, }, }, }, Required: []string{\"drivers\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1.CSINodeDriver\"}, } } func schema_k8sio_api_storage_v1_StorageClass(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StorageClass describes the parameters for a class of storage for which PersistentVolumes can be dynamically provisioned.nnStorageClasses are non-namespaced; the name of the storage class according to etcd is in ObjectMeta.Name.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"provisioner\": { SchemaProps: spec.SchemaProps{ Description: \"Provisioner indicates the type of the provisioner.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"parameters\": { SchemaProps: spec.SchemaProps{ Description: \"Parameters holds the parameters for the provisioner that should create volumes of this storage class.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"reclaimPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"Dynamically provisioned PersistentVolumes of this storage class are created with this reclaimPolicy. Defaults to Delete.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"mountOptions\": { SchemaProps: spec.SchemaProps{ Description: \"Dynamically provisioned PersistentVolumes of this storage class are created with these mountOptions, e.g. [\"ro\", \"soft\"]. Not validated - mount of the PVs will simply fail if one is invalid.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"allowVolumeExpansion\": { SchemaProps: spec.SchemaProps{ Description: \"AllowVolumeExpansion shows whether the storage class allow volume expand\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"volumeBindingMode\": { SchemaProps: spec.SchemaProps{ Description: \"VolumeBindingMode indicates how PersistentVolumeClaims should be provisioned and bound.  When unset, VolumeBindingImmediate is used. This field is only honored by servers that enable the VolumeScheduling feature.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"allowedTopologies\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Restrict the node topologies where volumes can be dynamically provisioned. Each volume plugin defines its own supported topology specifications. An empty TopologySelectorTerm list means there is no topology restriction. This field is only honored by servers that enable the VolumeScheduling feature.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.TopologySelectorTerm\"), }, }, }, }, }, }, Required: []string{\"provisioner\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.TopologySelectorTerm\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_storage_v1_StorageClassList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StorageClassList is a collection of storage classes.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of StorageClasses\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/storage/v1.StorageClass\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1.StorageClass\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_storage_v1_TokenRequest(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TokenRequest contains parameters of a service account token.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"audience\": { SchemaProps: spec.SchemaProps{ Description: \"Audience is the intended audience of the token in \"TokenRequestSpec\". It will default to the audiences of kube apiserver.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"expirationSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"ExpirationSeconds is the duration of validity of the token in \"TokenRequestSpec\". It has the same default value of \"ExpirationSeconds\" in \"TokenRequestSpec\".\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, }, Required: []string{\"audience\"}, }, }, } } func schema_k8sio_api_storage_v1_VolumeAttachment(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeAttachment captures the intent to attach or detach the specified volume to/from the specified node.nnVolumeAttachment objects are non-namespaced.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the desired attach/detach volume behavior. Populated by the Kubernetes system.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/storage/v1.VolumeAttachmentSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the VolumeAttachment request. Populated by the entity completing the attach or detach operation, i.e. the external-attacher.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/storage/v1.VolumeAttachmentStatus\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1.VolumeAttachmentSpec\", \"k8s.io/api/storage/v1.VolumeAttachmentStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_storage_v1_VolumeAttachmentList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeAttachmentList is a collection of VolumeAttachment objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of VolumeAttachments\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/storage/v1.VolumeAttachment\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1.VolumeAttachment\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_storage_v1_VolumeAttachmentSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeAttachmentSource represents a volume that should be attached. Right now only PersistenVolumes can be attached via external attacher, in future we may allow also inline volumes in pods. Exactly one member can be set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"persistentVolumeName\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the persistent volume to attach.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"inlineVolumeSpec\": { SchemaProps: spec.SchemaProps{ Description: \"inlineVolumeSpec contains all the information necessary to attach a persistent volume defined by a pod's inline VolumeSource. This field is populated only for the CSIMigration feature. It contains translated fields from a pod's inline VolumeSource to a PersistentVolumeSpec. This field is beta-level and is only honored by servers that enabled the CSIMigration feature.\", Ref:         ref(\"k8s.io/api/core/v1.PersistentVolumeSpec\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PersistentVolumeSpec\"}, } } func schema_k8sio_api_storage_v1_VolumeAttachmentSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeAttachmentSpec is the specification of a VolumeAttachment request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"attacher\": { SchemaProps: spec.SchemaProps{ Description: \"Attacher indicates the name of the volume driver that MUST handle this request. This is the name returned by GetPluginName().\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"source\": { SchemaProps: spec.SchemaProps{ Description: \"Source represents the volume that should be attached.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/storage/v1.VolumeAttachmentSource\"), }, }, \"nodeName\": { SchemaProps: spec.SchemaProps{ Description: \"The node that the volume should be attached to.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"attacher\", \"source\", \"nodeName\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1.VolumeAttachmentSource\"}, } } func schema_k8sio_api_storage_v1_VolumeAttachmentStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeAttachmentStatus is the status of a VolumeAttachment request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"attached\": { SchemaProps: spec.SchemaProps{ Description: \"Indicates the volume is successfully attached. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"attachmentMetadata\": { SchemaProps: spec.SchemaProps{ Description: \"Upon successful attach, this field is populated with any information returned by the attach operation that must be passed into subsequent WaitForAttach or Mount calls. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"attachError\": { SchemaProps: spec.SchemaProps{ Description: \"The last error encountered during attach operation, if any. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.\", Ref:         ref(\"k8s.io/api/storage/v1.VolumeError\"), }, }, \"detachError\": { SchemaProps: spec.SchemaProps{ Description: \"The last error encountered during detach operation, if any. This field must only be set by the entity completing the detach operation, i.e. the external-attacher.\", Ref:         ref(\"k8s.io/api/storage/v1.VolumeError\"), }, }, }, Required: []string{\"attached\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1.VolumeError\"}, } } func schema_k8sio_api_storage_v1_VolumeError(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeError captures an error encountered during a volume operation.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"time\": { SchemaProps: spec.SchemaProps{ Description: \"Time the error was encountered.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"String detailing the error encountered during Attach or Detach operation. This string may be logged, so it should not contain sensitive information.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_storage_v1_VolumeNodeResources(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeNodeResources is a set of resource limits for scheduling of volumes.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"count\": { SchemaProps: spec.SchemaProps{ Description: \"Maximum number of unique volumes managed by the CSI driver that can be used on a node. A volume that is both attached and mounted on a node is considered to be used once, not twice. The same rule applies for a unique volume that is shared among multiple pods on the same node. If this field is not specified, then the supported number of volumes on this node is unbounded.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_k8sio_api_storage_v1alpha1_CSIStorageCapacity(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CSIStorageCapacity stores the result of one CSI GetCapacity call. For a given StorageClass, this describes the available capacity in a particular topology segment.  This can be used when considering where to instantiate new PersistentVolumes.nnFor example this can express things like: - StorageClass \"standard\" has \"1234 GiB\" available in \"topology.kubernetes.io/zone=us-east1\" - StorageClass \"localssd\" has \"10 GiB\" available in \"kubernetes.io/hostname=knode-abc123\"nnThe following three cases all imply that no capacity is available for a certain combination: - no object exists with suitable topology and storage class name - such an object exists, but the capacity is unset - such an object exists, but the capacity is zeronnThe producer of these objects can decide which approach is more suitable.nnThey are consumed by the kube-scheduler if the CSIStorageCapacity beta feature gate is enabled there and a CSI driver opts into capacity-aware scheduling with CSIDriver.StorageCapacity.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. The name has no particular meaning. It must be be a DNS subdomain (dots allowed, 253 characters). To ensure that there are no conflicts with other CSI drivers on the cluster, the recommendation is to use csisc-<uuid>, a generated name, or a reverse-domain name which ends with the unique CSI driver name.nnObjects are namespaced.nnMore info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"nodeTopology\": { SchemaProps: spec.SchemaProps{ Description: \"NodeTopology defines which nodes have access to the storage for which capacity was reported. If not set, the storage is not accessible from any node in the cluster. If empty, the storage is accessible from all nodes. This field is immutable.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"storageClassName\": { SchemaProps: spec.SchemaProps{ Description: \"The name of the StorageClass that the reported capacity applies to. It must meet the same requirements as the name of a StorageClass object (non-empty, DNS subdomain). If that object no longer exists, the CSIStorageCapacity object is obsolete and should be removed by its creator. This field is immutable.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"capacity\": { SchemaProps: spec.SchemaProps{ Description: \"Capacity is the value reported by the CSI driver in its GetCapacityResponse for a GetCapacityRequest with topology and parameters that match the previous fields.nnThe semantic is currently (CSI spec 1.2) defined as: The available capacity, in bytes, of the storage that can be used to provision volumes. If not set, that information is currently unavailable and treated like zero capacity.\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"maximumVolumeSize\": { SchemaProps: spec.SchemaProps{ Description: \"MaximumVolumeSize is the value reported by the CSI driver in its GetCapacityResponse for a GetCapacityRequest with topology and parameters that match the previous fields.nnThis is defined since CSI spec 1.4.0 as the largest size that may be used in a CreateVolumeRequest.capacity_range.required_bytes field to create a volume with the same parameters as those in GetCapacityRequest. The corresponding value in the Kubernetes API is ResourceRequirements.Requests in a volume claim.\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, Required: []string{\"storageClassName\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_storage_v1alpha1_CSIStorageCapacityList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CSIStorageCapacityList is a collection of CSIStorageCapacity objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"name\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Items is the list of CSIStorageCapacity objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/storage/v1alpha1.CSIStorageCapacity\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1alpha1.CSIStorageCapacity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_storage_v1alpha1_VolumeAttachment(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeAttachment captures the intent to attach or detach the specified volume to/from the specified node.nnVolumeAttachment objects are non-namespaced.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the desired attach/detach volume behavior. Populated by the Kubernetes system.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/storage/v1alpha1.VolumeAttachmentSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the VolumeAttachment request. Populated by the entity completing the attach or detach operation, i.e. the external-attacher.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/storage/v1alpha1.VolumeAttachmentStatus\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1alpha1.VolumeAttachmentSpec\", \"k8s.io/api/storage/v1alpha1.VolumeAttachmentStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_storage_v1alpha1_VolumeAttachmentList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeAttachmentList is a collection of VolumeAttachment objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of VolumeAttachments\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/storage/v1alpha1.VolumeAttachment\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1alpha1.VolumeAttachment\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_storage_v1alpha1_VolumeAttachmentSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeAttachmentSource represents a volume that should be attached. Right now only PersistenVolumes can be attached via external attacher, in future we may allow also inline volumes in pods. Exactly one member can be set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"persistentVolumeName\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the persistent volume to attach.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"inlineVolumeSpec\": { SchemaProps: spec.SchemaProps{ Description: \"inlineVolumeSpec contains all the information necessary to attach a persistent volume defined by a pod's inline VolumeSource. This field is populated only for the CSIMigration feature. It contains translated fields from a pod's inline VolumeSource to a PersistentVolumeSpec. This field is alpha-level and is only honored by servers that enabled the CSIMigration feature.\", Ref:         ref(\"k8s.io/api/core/v1.PersistentVolumeSpec\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PersistentVolumeSpec\"}, } } func schema_k8sio_api_storage_v1alpha1_VolumeAttachmentSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeAttachmentSpec is the specification of a VolumeAttachment request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"attacher\": { SchemaProps: spec.SchemaProps{ Description: \"Attacher indicates the name of the volume driver that MUST handle this request. This is the name returned by GetPluginName().\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"source\": { SchemaProps: spec.SchemaProps{ Description: \"Source represents the volume that should be attached.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/storage/v1alpha1.VolumeAttachmentSource\"), }, }, \"nodeName\": { SchemaProps: spec.SchemaProps{ Description: \"The node that the volume should be attached to.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"attacher\", \"source\", \"nodeName\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1alpha1.VolumeAttachmentSource\"}, } } func schema_k8sio_api_storage_v1alpha1_VolumeAttachmentStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeAttachmentStatus is the status of a VolumeAttachment request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"attached\": { SchemaProps: spec.SchemaProps{ Description: \"Indicates the volume is successfully attached. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"attachmentMetadata\": { SchemaProps: spec.SchemaProps{ Description: \"Upon successful attach, this field is populated with any information returned by the attach operation that must be passed into subsequent WaitForAttach or Mount calls. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"attachError\": { SchemaProps: spec.SchemaProps{ Description: \"The last error encountered during attach operation, if any. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.\", Ref:         ref(\"k8s.io/api/storage/v1alpha1.VolumeError\"), }, }, \"detachError\": { SchemaProps: spec.SchemaProps{ Description: \"The last error encountered during detach operation, if any. This field must only be set by the entity completing the detach operation, i.e. the external-attacher.\", Ref:         ref(\"k8s.io/api/storage/v1alpha1.VolumeError\"), }, }, }, Required: []string{\"attached\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1alpha1.VolumeError\"}, } } func schema_k8sio_api_storage_v1alpha1_VolumeError(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeError captures an error encountered during a volume operation.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"time\": { SchemaProps: spec.SchemaProps{ Description: \"Time the error was encountered.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"String detailing the error encountered during Attach or Detach operation. This string maybe logged, so it should not contain sensitive information.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_storage_v1beta1_CSIDriver(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CSIDriver captures information about a Container Storage Interface (CSI) volume driver deployed on the cluster. CSI drivers do not need to create the CSIDriver object directly. Instead they may use the cluster-driver-registrar sidecar container. When deployed with a CSI driver it automatically creates a CSIDriver object representing the driver. Kubernetes attach detach controller uses this object to determine whether attach is required. Kubelet uses this object to determine whether pod information needs to be passed on mount. CSIDriver objects are non-namespaced.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object metadata. metadata.Name indicates the name of the CSI driver that this object refers to; it MUST be the same name returned by the CSI GetPluginName() call for that driver. The driver name must be 63 characters or less, beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with dashes (-), dots (.), and alphanumerics between. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the CSI Driver.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/storage/v1beta1.CSIDriverSpec\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1beta1.CSIDriverSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_storage_v1beta1_CSIDriverList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CSIDriverList is a collection of CSIDriver objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is the list of CSIDriver\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/storage/v1beta1.CSIDriver\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1beta1.CSIDriver\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_storage_v1beta1_CSIDriverSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CSIDriverSpec is the specification of a CSIDriver.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"attachRequired\": { SchemaProps: spec.SchemaProps{ Description: \"attachRequired indicates this CSI volume driver requires an attach operation (because it implements the CSI ControllerPublishVolume() method), and that the Kubernetes attach detach controller should call the attach volume interface which checks the volumeattachment status and waits until the volume is attached before proceeding to mounting. The CSI external-attacher coordinates with CSI volume driver and updates the volumeattachment status when the attach operation is complete. If the CSIDriverRegistry feature gate is enabled and the value is specified to false, the attach operation will be skipped. Otherwise the attach operation will be called.nnThis field is immutable.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"podInfoOnMount\": { SchemaProps: spec.SchemaProps{ Description: \"If set to true, podInfoOnMount indicates this CSI volume driver requires additional pod information (like podName, podUID, etc.) during mount operations. If set to false, pod information will not be passed on mount. Default is false. The CSI driver specifies podInfoOnMount as part of driver deployment. If true, Kubelet will pass pod information as VolumeContext in the CSI NodePublishVolume() calls. The CSI driver is responsible for parsing and validating the information passed in as VolumeContext. The following VolumeConext will be passed if podInfoOnMount is set to true. This list might grow, but the prefix will be used. \"csi.storage.k8s.io/pod.name\": pod.Name \"csi.storage.k8s.io/pod.namespace\": pod.Namespace \"csi.storage.k8s.io/pod.uid\": string(pod.UID) \"csi.storage.k8s.io/ephemeral\": \"true\" if the volume is an ephemeral inline volumen                                defined by a CSIVolumeSource, otherwise \"false\"nn\"csi.storage.k8s.io/ephemeral\" is a new feature in Kubernetes 1.16. It is only required for drivers which support both the \"Persistent\" and \"Ephemeral\" VolumeLifecycleMode. Other drivers can leave pod info disabled and/or ignore this field. As Kubernetes 1.15 doesn't support this field, drivers can only support one mode when deployed on such a cluster and the deployment determines which mode that is, for example via a command line parameter of the driver.nnThis field is immutable.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"volumeLifecycleModes\": { SchemaProps: spec.SchemaProps{ Description: \"VolumeLifecycleModes defines what kind of volumes this CSI volume driver supports. The default if the list is empty is \"Persistent\", which is the usage defined by the CSI specification and implemented in Kubernetes via the usual PV/PVC mechanism. The other mode is \"Ephemeral\". In this mode, volumes are defined inline inside the pod spec with CSIVolumeSource and their lifecycle is tied to the lifecycle of that pod. A driver has to be aware of this because it is only going to get a NodePublishVolume call for such a volume. For more information about implementing this mode, see https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html A driver can support one or more of these modes and more modes may be added in the future.nnThis field is immutable.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"storageCapacity\": { SchemaProps: spec.SchemaProps{ Description: \"If set to true, storageCapacity indicates that the CSI volume driver wants pod scheduling to consider the storage capacity that the driver deployment will report by creating CSIStorageCapacity objects with capacity information.nnThe check can be enabled immediately when deploying a driver. In that case, provisioning new volumes with late binding will pause until the driver deployment has published some suitable CSIStorageCapacity object.nnAlternatively, the driver can be deployed with the field unset or false and it can be flipped later when storage capacity information has been published.nnThis field was immutable in Kubernetes <= 1.22 and now is mutable.nnThis is a beta field and only available when the CSIStorageCapacity feature is enabled. The default is false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"fsGroupPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"Defines if the underlying volume supports changing ownership and permission of the volume before being mounted. Refer to the specific FSGroupPolicy values for additional details.nnThis field is immutable.nnDefaults to ReadWriteOnceWithFSType, which will examine each volume to determine if Kubernetes should modify ownership and permissions of the volume. With the default policy the defined fsGroup will only be applied if a fstype is defined and the volume's access mode contains ReadWriteOnce.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"tokenRequests\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"TokenRequests indicates the CSI driver needs pods' service account tokens it is mounting volume for to do necessary authentication. Kubelet will pass the tokens in VolumeContext in the CSI NodePublishVolume calls. The CSI driver should parse and validate the following VolumeContext: \"csi.storage.k8s.io/serviceAccount.tokens\": {n  \"<audience>\": {n    \"token\": <token>,n    \"expirationTimestamp\": <expiration timestamp in RFC3339>,n  },n  ...n}nnNote: Audience in each TokenRequest should be different and at most one token is empty string. To receive a new token after expiry, RequiresRepublish can be used to trigger NodePublishVolume periodically.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/storage/v1beta1.TokenRequest\"), }, }, }, }, }, \"requiresRepublish\": { SchemaProps: spec.SchemaProps{ Description: \"RequiresRepublish indicates the CSI driver wants `NodePublishVolume` being periodically called to reflect any possible change in the mounted volume. This field defaults to false.nnNote: After a successful initial NodePublishVolume call, subsequent calls to NodePublishVolume should only update the contents of the volume. New mount points will not be seen by a running container.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1beta1.TokenRequest\"}, } } func schema_k8sio_api_storage_v1beta1_CSINode(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED - This group version of CSINode is deprecated by storage/v1/CSINode. See the release notes for more information. CSINode holds information about all CSI drivers installed on a node. CSI drivers do not need to create the CSINode object directly. As long as they use the node-driver-registrar sidecar container, the kubelet will automatically populate the CSINode object for the CSI driver as part of kubelet plugin registration. CSINode has the same name as a node. If the object is missing, it means either there are no CSI Drivers available on the node, or the Kubelet version is low enough that it doesn't create this object. CSINode has an OwnerReference that points to the corresponding node object.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"metadata.name must be the Kubernetes node name.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"spec is the specification of CSINode\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/storage/v1beta1.CSINodeSpec\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1beta1.CSINodeSpec\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_storage_v1beta1_CSINodeDriver(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CSINodeDriver holds information about the specification of one CSI driver installed on a node\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"This is the name of the CSI driver that this object refers to. This MUST be the same name returned by the CSI GetPluginName() call for that driver.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"nodeID\": { SchemaProps: spec.SchemaProps{ Description: \"nodeID of the node from the driver point of view. This field enables Kubernetes to communicate with storage systems that do not share the same nomenclature for nodes. For example, Kubernetes may refer to a given node as \"node1\", but the storage system may refer to the same node as \"nodeA\". When Kubernetes issues a command to the storage system to attach a volume to a specific node, it can use this field to refer to the node name using the ID that the storage system will understand, e.g. \"nodeA\" instead of \"node1\". This field is required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"topologyKeys\": { SchemaProps: spec.SchemaProps{ Description: \"topologyKeys is the list of keys supported by the driver. When a driver is initialized on a cluster, it provides a set of topology keys that it understands (e.g. \"company.com/zone\", \"company.com/region\"). When a driver is initialized on a node, it provides the same topology keys along with values. Kubelet will expose these topology keys as labels on its own node object. When Kubernetes does topology aware provisioning, it can use this list to determine which labels it should retrieve from the node object and pass back to the driver. It is possible for different nodes to use different topology keys. This can be empty if driver does not support topology.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"allocatable\": { SchemaProps: spec.SchemaProps{ Description: \"allocatable represents the volume resources of a node that are available for scheduling.\", Ref:         ref(\"k8s.io/api/storage/v1beta1.VolumeNodeResources\"), }, }, }, Required: []string{\"name\", \"nodeID\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1beta1.VolumeNodeResources\"}, } } func schema_k8sio_api_storage_v1beta1_CSINodeList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CSINodeList is a collection of CSINode objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items is the list of CSINode\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/storage/v1beta1.CSINode\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1beta1.CSINode\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_storage_v1beta1_CSINodeSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CSINodeSpec holds information about the specification of all CSI drivers installed on a node\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"drivers\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"name\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"drivers is a list of information of all CSI Drivers existing on a node. If all drivers in the list are uninstalled, this can become empty.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/storage/v1beta1.CSINodeDriver\"), }, }, }, }, }, }, Required: []string{\"drivers\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1beta1.CSINodeDriver\"}, } } func schema_k8sio_api_storage_v1beta1_CSIStorageCapacity(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CSIStorageCapacity stores the result of one CSI GetCapacity call. For a given StorageClass, this describes the available capacity in a particular topology segment.  This can be used when considering where to instantiate new PersistentVolumes.nnFor example this can express things like: - StorageClass \"standard\" has \"1234 GiB\" available in \"topology.kubernetes.io/zone=us-east1\" - StorageClass \"localssd\" has \"10 GiB\" available in \"kubernetes.io/hostname=knode-abc123\"nnThe following three cases all imply that no capacity is available for a certain combination: - no object exists with suitable topology and storage class name - such an object exists, but the capacity is unset - such an object exists, but the capacity is zeronnThe producer of these objects can decide which approach is more suitable.nnThey are consumed by the kube-scheduler if the CSIStorageCapacity beta feature gate is enabled there and a CSI driver opts into capacity-aware scheduling with CSIDriver.StorageCapacity.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. The name has no particular meaning. It must be be a DNS subdomain (dots allowed, 253 characters). To ensure that there are no conflicts with other CSI drivers on the cluster, the recommendation is to use csisc-<uuid>, a generated name, or a reverse-domain name which ends with the unique CSI driver name.nnObjects are namespaced.nnMore info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"nodeTopology\": { SchemaProps: spec.SchemaProps{ Description: \"NodeTopology defines which nodes have access to the storage for which capacity was reported. If not set, the storage is not accessible from any node in the cluster. If empty, the storage is accessible from all nodes. This field is immutable.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, \"storageClassName\": { SchemaProps: spec.SchemaProps{ Description: \"The name of the StorageClass that the reported capacity applies to. It must meet the same requirements as the name of a StorageClass object (non-empty, DNS subdomain). If that object no longer exists, the CSIStorageCapacity object is obsolete and should be removed by its creator. This field is immutable.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"capacity\": { SchemaProps: spec.SchemaProps{ Description: \"Capacity is the value reported by the CSI driver in its GetCapacityResponse for a GetCapacityRequest with topology and parameters that match the previous fields.nnThe semantic is currently (CSI spec 1.2) defined as: The available capacity, in bytes, of the storage that can be used to provision volumes. If not set, that information is currently unavailable and treated like zero capacity.\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"maximumVolumeSize\": { SchemaProps: spec.SchemaProps{ Description: \"MaximumVolumeSize is the value reported by the CSI driver in its GetCapacityResponse for a GetCapacityRequest with topology and parameters that match the previous fields.nnThis is defined since CSI spec 1.4.0 as the largest size that may be used in a CreateVolumeRequest.capacity_range.required_bytes field to create a volume with the same parameters as those in GetCapacityRequest. The corresponding value in the Kubernetes API is ResourceRequirements.Requests in a volume claim.\", Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, Required: []string{\"storageClassName\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_storage_v1beta1_CSIStorageCapacityList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CSIStorageCapacityList is a collection of CSIStorageCapacity objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"name\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Items is the list of CSIStorageCapacity objects.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/storage/v1beta1.CSIStorageCapacity\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1beta1.CSIStorageCapacity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_storage_v1beta1_StorageClass(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StorageClass describes the parameters for a class of storage for which PersistentVolumes can be dynamically provisioned.nnStorageClasses are non-namespaced; the name of the storage class according to etcd is in ObjectMeta.Name.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"provisioner\": { SchemaProps: spec.SchemaProps{ Description: \"Provisioner indicates the type of the provisioner.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"parameters\": { SchemaProps: spec.SchemaProps{ Description: \"Parameters holds the parameters for the provisioner that should create volumes of this storage class.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"reclaimPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"Dynamically provisioned PersistentVolumes of this storage class are created with this reclaimPolicy. Defaults to Delete.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"mountOptions\": { SchemaProps: spec.SchemaProps{ Description: \"Dynamically provisioned PersistentVolumes of this storage class are created with these mountOptions, e.g. [\"ro\", \"soft\"]. Not validated - mount of the PVs will simply fail if one is invalid.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"allowVolumeExpansion\": { SchemaProps: spec.SchemaProps{ Description: \"AllowVolumeExpansion shows whether the storage class allow volume expand\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"volumeBindingMode\": { SchemaProps: spec.SchemaProps{ Description: \"VolumeBindingMode indicates how PersistentVolumeClaims should be provisioned and bound.  When unset, VolumeBindingImmediate is used. This field is only honored by servers that enable the VolumeScheduling feature.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"allowedTopologies\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Restrict the node topologies where volumes can be dynamically provisioned. Each volume plugin defines its own supported topology specifications. An empty TopologySelectorTerm list means there is no topology restriction. This field is only honored by servers that enable the VolumeScheduling feature.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.TopologySelectorTerm\"), }, }, }, }, }, }, Required: []string{\"provisioner\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.TopologySelectorTerm\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_storage_v1beta1_StorageClassList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StorageClassList is a collection of storage classes.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of StorageClasses\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/storage/v1beta1.StorageClass\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1beta1.StorageClass\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_storage_v1beta1_TokenRequest(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TokenRequest contains parameters of a service account token.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"audience\": { SchemaProps: spec.SchemaProps{ Description: \"Audience is the intended audience of the token in \"TokenRequestSpec\". It will default to the audiences of kube apiserver.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"expirationSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"ExpirationSeconds is the duration of validity of the token in \"TokenRequestSpec\". It has the same default value of \"ExpirationSeconds\" in \"TokenRequestSpec\"\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, }, Required: []string{\"audience\"}, }, }, } } func schema_k8sio_api_storage_v1beta1_VolumeAttachment(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeAttachment captures the intent to attach or detach the specified volume to/from the specified node.nnVolumeAttachment objects are non-namespaced.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Specification of the desired attach/detach volume behavior. Populated by the Kubernetes system.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/storage/v1beta1.VolumeAttachmentSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the VolumeAttachment request. Populated by the entity completing the attach or detach operation, i.e. the external-attacher.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/storage/v1beta1.VolumeAttachmentStatus\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1beta1.VolumeAttachmentSpec\", \"k8s.io/api/storage/v1beta1.VolumeAttachmentStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_k8sio_api_storage_v1beta1_VolumeAttachmentList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeAttachmentList is a collection of VolumeAttachment objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of VolumeAttachments\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/storage/v1beta1.VolumeAttachment\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1beta1.VolumeAttachment\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_k8sio_api_storage_v1beta1_VolumeAttachmentSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeAttachmentSource represents a volume that should be attached. Right now only PersistenVolumes can be attached via external attacher, in future we may allow also inline volumes in pods. Exactly one member can be set.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"persistentVolumeName\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the persistent volume to attach.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"inlineVolumeSpec\": { SchemaProps: spec.SchemaProps{ Description: \"inlineVolumeSpec contains all the information necessary to attach a persistent volume defined by a pod's inline VolumeSource. This field is populated only for the CSIMigration feature. It contains translated fields from a pod's inline VolumeSource to a PersistentVolumeSpec. This field is beta-level and is only honored by servers that enabled the CSIMigration feature.\", Ref:         ref(\"k8s.io/api/core/v1.PersistentVolumeSpec\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.PersistentVolumeSpec\"}, } } func schema_k8sio_api_storage_v1beta1_VolumeAttachmentSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeAttachmentSpec is the specification of a VolumeAttachment request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"attacher\": { SchemaProps: spec.SchemaProps{ Description: \"Attacher indicates the name of the volume driver that MUST handle this request. This is the name returned by GetPluginName().\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"source\": { SchemaProps: spec.SchemaProps{ Description: \"Source represents the volume that should be attached.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/storage/v1beta1.VolumeAttachmentSource\"), }, }, \"nodeName\": { SchemaProps: spec.SchemaProps{ Description: \"The node that the volume should be attached to.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"attacher\", \"source\", \"nodeName\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1beta1.VolumeAttachmentSource\"}, } } func schema_k8sio_api_storage_v1beta1_VolumeAttachmentStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeAttachmentStatus is the status of a VolumeAttachment request.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"attached\": { SchemaProps: spec.SchemaProps{ Description: \"Indicates the volume is successfully attached. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"attachmentMetadata\": { SchemaProps: spec.SchemaProps{ Description: \"Upon successful attach, this field is populated with any information returned by the attach operation that must be passed into subsequent WaitForAttach or Mount calls. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"attachError\": { SchemaProps: spec.SchemaProps{ Description: \"The last error encountered during attach operation, if any. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.\", Ref:         ref(\"k8s.io/api/storage/v1beta1.VolumeError\"), }, }, \"detachError\": { SchemaProps: spec.SchemaProps{ Description: \"The last error encountered during detach operation, if any. This field must only be set by the entity completing the detach operation, i.e. the external-attacher.\", Ref:         ref(\"k8s.io/api/storage/v1beta1.VolumeError\"), }, }, }, Required: []string{\"attached\"}, }, }, Dependencies: []string{ \"k8s.io/api/storage/v1beta1.VolumeError\"}, } } func schema_k8sio_api_storage_v1beta1_VolumeError(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeError captures an error encountered during a volume operation.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"time\": { SchemaProps: spec.SchemaProps{ Description: \"Time the error was encountered.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"String detailing the error encountered during Attach or Detach operation. This string may be logged, so it should not contain sensitive information.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_api_storage_v1beta1_VolumeNodeResources(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeNodeResources is a set of resource limits for scheduling of volumes.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"count\": { SchemaProps: spec.SchemaProps{ Description: \"Maximum number of unique volumes managed by the CSI driver that can be used on a node. A volume that is both attached and mounted on a node is considered to be used once, not twice. The same rule applies for a unique volume that is shared among multiple pods on the same node. If this field is nil, then the supported number of volumes on this node is unbounded.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_pkg_apis_apiextensions_v1_ConversionRequest(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ConversionRequest describes the conversion request parameters.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"uid\": { SchemaProps: spec.SchemaProps{ Description: \"uid is an identifier for the individual request/response. It allows distinguishing instances of requests which are otherwise identical (parallel requests, etc). The UID is meant to track the round trip (request/response) between the Kubernetes API server and the webhook, not the user request. It is suitable for correlating log entries between the webhook and apiserver, for either auditing or debugging.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"desiredAPIVersion\": { SchemaProps: spec.SchemaProps{ Description: \"desiredAPIVersion is the version to convert given objects to. e.g. \"myapi.example.com/v1\"\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"objects\": { SchemaProps: spec.SchemaProps{ Description: \"objects is the list of custom resource objects to be converted.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/runtime.RawExtension\"), }, }, }, }, }, }, Required: []string{\"uid\", \"desiredAPIVersion\", \"objects\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/runtime.RawExtension\"}, } } func schema_pkg_apis_apiextensions_v1_ConversionResponse(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ConversionResponse describes a conversion response.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"uid\": { SchemaProps: spec.SchemaProps{ Description: \"uid is an identifier for the individual request/response. This should be copied over from the corresponding `request.uid`.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"convertedObjects\": { SchemaProps: spec.SchemaProps{ Description: \"convertedObjects is the list of converted version of `request.objects` if the `result` is successful, otherwise empty. The webhook is expected to set `apiVersion` of these objects to the `request.desiredAPIVersion`. The list must also have the same size as the input list with the same objects in the same order (equal kind, metadata.uid, metadata.name and metadata.namespace). The webhook is allowed to mutate labels and annotations. Any other change to the metadata is silently ignored.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/runtime.RawExtension\"), }, }, }, }, }, \"result\": { SchemaProps: spec.SchemaProps{ Description: \"result contains the result of conversion with extra details if the conversion failed. `result.status` determines if the conversion failed or succeeded. The `result.status` field is required and represents the success or failure of the conversion. A successful conversion must set `result.status` to `Success`. A failed conversion must set `result.status` to `Failure` and provide more details in `result.message` and return http status 200. The `result.message` will be used to construct an error message for the end user.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Status\"), }, }, }, Required: []string{\"uid\", \"convertedObjects\", \"result\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Status\", \"k8s.io/apimachinery/pkg/runtime.RawExtension\"}, } } func schema_pkg_apis_apiextensions_v1_ConversionReview(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ConversionReview describes a conversion request/response.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"request\": { SchemaProps: spec.SchemaProps{ Description: \"request describes the attributes for the conversion request.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.ConversionRequest\"), }, }, \"response\": { SchemaProps: spec.SchemaProps{ Description: \"response describes the attributes for the conversion response.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.ConversionResponse\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.ConversionRequest\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.ConversionResponse\"}, } } func schema_pkg_apis_apiextensions_v1_CustomResourceColumnDefinition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceColumnDefinition specifies a column for server side printing.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is a human readable name for the column.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type is an OpenAPI type definition for this column. See https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#data-types for details.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"format\": { SchemaProps: spec.SchemaProps{ Description: \"format is an optional OpenAPI type definition for this column. The 'name' format is applied to the primary identifier column to assist in clients identifying column is the resource name. See https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#data-types for details.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"description\": { SchemaProps: spec.SchemaProps{ Description: \"description is a human readable description of this column.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"priority\": { SchemaProps: spec.SchemaProps{ Description: \"priority is an integer defining the relative importance of this column compared to others. Lower numbers are considered higher priority. Columns that may be omitted in limited space scenarios should be given a priority greater than 0.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"jsonPath\": { SchemaProps: spec.SchemaProps{ Description: \"jsonPath is a simple JSON path (i.e. with array notation) which is evaluated against each custom resource to produce the value for this column.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"type\", \"jsonPath\"}, }, }, } } func schema_pkg_apis_apiextensions_v1_CustomResourceConversion(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceConversion describes how to convert different versions of a CR.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"strategy\": { SchemaProps: spec.SchemaProps{ Description: \"strategy specifies how custom resources are converted between versions. Allowed values are: - `None`: The converter only change the apiVersion and would not touch any other field in the custom resource. - `Webhook`: API Server will call to an external webhook to do the conversion. Additional informationn  is needed for this option. This requires spec.preserveUnknownFields to be false, and spec.conversion.webhook to be set.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"webhook\": { SchemaProps: spec.SchemaProps{ Description: \"webhook describes how to call the conversion webhook. Required when `strategy` is set to `Webhook`.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.WebhookConversion\"), }, }, }, Required: []string{\"strategy\"}, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.WebhookConversion\"}, } } func schema_pkg_apis_apiextensions_v1_CustomResourceDefinition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceDefinition represents a resource that should be exposed on the API server.  Its name MUST be in the format <.spec.name>.<.spec.group>.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"spec describes how the user wants the resources to appear\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinitionSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"status indicates the actual state of the CustomResourceDefinition\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinitionStatus\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinitionSpec\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinitionStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_pkg_apis_apiextensions_v1_CustomResourceDefinitionCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceDefinitionCondition contains details for the current condition of this pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type is the type of the condition. Types include Established, NamesAccepted and Terminating.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"status is the status of the condition. Can be True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"lastTransitionTime last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"reason is a unique, one-word, CamelCase reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"message is a human-readable message indicating details about last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_pkg_apis_apiextensions_v1_CustomResourceDefinitionList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceDefinitionList is a list of CustomResourceDefinition objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items list individual CustomResourceDefinition objects\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinition\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinition\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_pkg_apis_apiextensions_v1_CustomResourceDefinitionNames(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceDefinitionNames indicates the names to serve this CustomResourceDefinition\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"plural\": { SchemaProps: spec.SchemaProps{ Description: \"plural is the plural name of the resource to serve. The custom resources are served under `/apis/<group>/<version>/.../<plural>`. Must match the name of the CustomResourceDefinition (in the form `<names.plural>.<group>`). Must be all lowercase.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"singular\": { SchemaProps: spec.SchemaProps{ Description: \"singular is the singular name of the resource. It must be all lowercase. Defaults to lowercased `kind`.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"shortNames\": { SchemaProps: spec.SchemaProps{ Description: \"shortNames are short names for the resource, exposed in API discovery documents, and used by clients to support invocations like `kubectl get <shortname>`. It must be all lowercase.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"kind is the serialized kind of the resource. It is normally CamelCase and singular. Custom resource instances will use this value as the `kind` attribute in API calls.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"listKind\": { SchemaProps: spec.SchemaProps{ Description: \"listKind is the serialized kind of the list for this resource. Defaults to \"`kind`List\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"categories\": { SchemaProps: spec.SchemaProps{ Description: \"categories is a list of grouped resources this custom resource belongs to (e.g. 'all'). This is published in API discovery documents, and used by clients to support invocations like `kubectl get all`.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"plural\", \"kind\"}, }, }, } } func schema_pkg_apis_apiextensions_v1_CustomResourceDefinitionSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceDefinitionSpec describes how a user wants their resource to appear\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"group\": { SchemaProps: spec.SchemaProps{ Description: \"group is the API group of the defined custom resource. The custom resources are served under `/apis/<group>/...`. Must match the name of the CustomResourceDefinition (in the form `<names.plural>.<group>`).\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"names\": { SchemaProps: spec.SchemaProps{ Description: \"names specify the resource and kind names for the custom resource.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinitionNames\"), }, }, \"scope\": { SchemaProps: spec.SchemaProps{ Description: \"scope indicates whether the defined custom resource is cluster- or namespace-scoped. Allowed values are `Cluster` and `Namespaced`.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"versions\": { SchemaProps: spec.SchemaProps{ Description: \"versions is the list of all API versions of the defined custom resource. Version names are used to compute the order in which served versions are listed in API discovery. If the version string is \"kube-like\", it will sort above non \"kube-like\" version strings, which are ordered lexicographically. \"Kube-like\" versions start with a \"v\", then are followed by a number (the major version), then optionally the string \"alpha\" or \"beta\" and another number (the minor version). These are sorted first by GA > beta > alpha (where GA is a version with no suffix such as beta or alpha), and then by comparing major version, then minor version. An example sorted list of versions: v10, v2, v1, v11beta2, v10beta3, v3beta1, v12alpha1, v11alpha2, foo1, foo10.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinitionVersion\"), }, }, }, }, }, \"conversion\": { SchemaProps: spec.SchemaProps{ Description: \"conversion defines conversion settings for the CRD.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceConversion\"), }, }, \"preserveUnknownFields\": { SchemaProps: spec.SchemaProps{ Description: \"preserveUnknownFields indicates that object fields which are not specified in the OpenAPI schema should be preserved when persisting to storage. apiVersion, kind, metadata and known fields inside metadata are always preserved. This field is deprecated in favor of setting `x-preserve-unknown-fields` to true in `spec.versions[*].schema.openAPIV3Schema`. See https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/#pruning-versus-preserving-unknown-fields for details.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"group\", \"names\", \"scope\", \"versions\"}, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceConversion\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinitionNames\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinitionVersion\"}, } } func schema_pkg_apis_apiextensions_v1_CustomResourceDefinitionStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceDefinitionStatus indicates the state of the CustomResourceDefinition\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"type\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"conditions indicate state for particular aspects of a CustomResourceDefinition\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinitionCondition\"), }, }, }, }, }, \"acceptedNames\": { SchemaProps: spec.SchemaProps{ Description: \"acceptedNames are the names that are actually being used to serve discovery. They may be different than the names in spec.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinitionNames\"), }, }, \"storedVersions\": { SchemaProps: spec.SchemaProps{ Description: \"storedVersions lists all versions of CustomResources that were ever persisted. Tracking these versions allows a migration path for stored versions in etcd. The field is mutable so a migration controller can finish a migration to another version (ensuring no old objects are left in storage), and then remove the rest of the versions from this list. Versions may not be removed from `spec.versions` while they exist in this list.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinitionCondition\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceDefinitionNames\"}, } } func schema_pkg_apis_apiextensions_v1_CustomResourceDefinitionVersion(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceDefinitionVersion describes a version for CRD.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the version name, e.g. \u201cv1\u201d, \u201cv2beta1\u201d, etc. The custom resources are served under this version at `/apis/<group>/<version>/...` if `served` is true.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"served\": { SchemaProps: spec.SchemaProps{ Description: \"served is a flag enabling/disabling this version from being served via REST APIs\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"storage\": { SchemaProps: spec.SchemaProps{ Description: \"storage indicates this version should be used when persisting custom resources to storage. There must be exactly one version with storage=true.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"deprecated\": { SchemaProps: spec.SchemaProps{ Description: \"deprecated indicates this version of the custom resource API is deprecated. When set to true, API requests to this version receive a warning header in the server response. Defaults to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"deprecationWarning\": { SchemaProps: spec.SchemaProps{ Description: \"deprecationWarning overrides the default warning returned to API clients. May only be set when `deprecated` is true. The default warning indicates this version is deprecated and recommends use of the newest served version of equal or greater stability, if one exists.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"schema\": { SchemaProps: spec.SchemaProps{ Description: \"schema describes the schema used for validation, pruning, and defaulting of this version of the custom resource.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceValidation\"), }, }, \"subresources\": { SchemaProps: spec.SchemaProps{ Description: \"subresources specify what subresources this version of the defined custom resource have.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceSubresources\"), }, }, \"additionalPrinterColumns\": { SchemaProps: spec.SchemaProps{ Description: \"additionalPrinterColumns specifies additional columns returned in Table output. See https://kubernetes.io/docs/reference/using-api/api-concepts/#receiving-resources-as-tables for details. If no columns are specified, a single column displaying the age of the custom resource is used.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceColumnDefinition\"), }, }, }, }, }, }, Required: []string{\"name\", \"served\", \"storage\"}, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceColumnDefinition\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceSubresources\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceValidation\"}, } } func schema_pkg_apis_apiextensions_v1_CustomResourceSubresourceScale(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceSubresourceScale defines how to serve the scale subresource for CustomResources.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"specReplicasPath\": { SchemaProps: spec.SchemaProps{ Description: \"specReplicasPath defines the JSON path inside of a custom resource that corresponds to Scale `spec.replicas`. Only JSON paths without the array notation are allowed. Must be a JSON Path under `.spec`. If there is no value under the given path in the custom resource, the `/scale` subresource will return an error on GET.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"statusReplicasPath\": { SchemaProps: spec.SchemaProps{ Description: \"statusReplicasPath defines the JSON path inside of a custom resource that corresponds to Scale `status.replicas`. Only JSON paths without the array notation are allowed. Must be a JSON Path under `.status`. If there is no value under the given path in the custom resource, the `status.replicas` value in the `/scale` subresource will default to 0.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"labelSelectorPath\": { SchemaProps: spec.SchemaProps{ Description: \"labelSelectorPath defines the JSON path inside of a custom resource that corresponds to Scale `status.selector`. Only JSON paths without the array notation are allowed. Must be a JSON Path under `.status` or `.spec`. Must be set to work with HorizontalPodAutoscaler. The field pointed by this JSON path must be a string field (not a complex selector struct) which contains a serialized label selector in string form. More info: https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions#scale-subresource If there is no value under the given path in the custom resource, the `status.selector` value in the `/scale` subresource will default to the empty string.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"specReplicasPath\", \"statusReplicasPath\"}, }, }, } } func schema_pkg_apis_apiextensions_v1_CustomResourceSubresourceStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceSubresourceStatus defines how to serve the status subresource for CustomResources. Status is represented by the `.status` JSON path inside of a CustomResource. When set, * exposes a /status subresource for the custom resource * PUT requests to the /status subresource take a custom resource object, and ignore changes to anything except the status stanza * PUT/POST/PATCH requests to the custom resource ignore changes to the status stanza\", Type:        []string{\"object\"}, }, }, } } func schema_pkg_apis_apiextensions_v1_CustomResourceSubresources(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceSubresources defines the status and scale subresources for CustomResources.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"status\": { SchemaProps: spec.SchemaProps{ Description: \"status indicates the custom resource should serve a `/status` subresource. When enabled: 1. requests to the custom resource primary endpoint ignore changes to the `status` stanza of the object. 2. requests to the custom resource `/status` subresource ignore changes to anything other than the `status` stanza of the object.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceSubresourceStatus\"), }, }, \"scale\": { SchemaProps: spec.SchemaProps{ Description: \"scale indicates the custom resource should serve a `/scale` subresource that returns an `autoscaling/v1` Scale object.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceSubresourceScale\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceSubresourceScale\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.CustomResourceSubresourceStatus\"}, } } func schema_pkg_apis_apiextensions_v1_CustomResourceValidation(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceValidation is a list of validation methods for CustomResources.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"openAPIV3Schema\": { SchemaProps: spec.SchemaProps{ Description: \"openAPIV3Schema is the OpenAPI v3 schema to use for validation and pruning.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaProps\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaProps\"}, } } func schema_pkg_apis_apiextensions_v1_ExternalDocumentation(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExternalDocumentation allows referencing an external resource for extended documentation.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"description\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"url\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, }, }, }, } } func schema_pkg_apis_apiextensions_v1_JSON(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"JSON represents any valid JSON value. These types are supported: bool, int64, float64, string, []interface{}, map[string]interface{} and nil.\", Type:        v1.JSON{}.OpenAPISchemaType(), Format:      v1.JSON{}.OpenAPISchemaFormat(), }, }, } } func schema_pkg_apis_apiextensions_v1_JSONSchemaProps(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"JSONSchemaProps is a JSON-Schema following Specification Draft 4 (http://json-schema.org/).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"id\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"$schema\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"$ref\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"description\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"type\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"format\": { SchemaProps: spec.SchemaProps{ Description: \"format is an OpenAPI v3 format string. Unknown formats are ignored. The following formats are validated:nn- bsonobjectid: a bson object ID, i.e. a 24 characters hex string - uri: an URI as parsed by Golang net/url.ParseRequestURI - email: an email address as parsed by Golang net/mail.ParseAddress - hostname: a valid representation for an Internet host name, as defined by RFC 1034, section 3.1 [RFC1034]. - ipv4: an IPv4 IP as parsed by Golang net.ParseIP - ipv6: an IPv6 IP as parsed by Golang net.ParseIP - cidr: a CIDR as parsed by Golang net.ParseCIDR - mac: a MAC address as parsed by Golang net.ParseMAC - uuid: an UUID that allows uppercase defined by the regex (?i)^[0-9a-f]{8}-?[0-9a-f]{4}-?[0-9a-f]{4}-?[0-9a-f]{4}-?[0-9a-f]{12}$ - uuid3: an UUID3 that allows uppercase defined by the regex (?i)^[0-9a-f]{8}-?[0-9a-f]{4}-?3[0-9a-f]{3}-?[0-9a-f]{4}-?[0-9a-f]{12}$ - uuid4: an UUID4 that allows uppercase defined by the regex (?i)^[0-9a-f]{8}-?[0-9a-f]{4}-?4[0-9a-f]{3}-?[89ab][0-9a-f]{3}-?[0-9a-f]{12}$ - uuid5: an UUID5 that allows uppercase defined by the regex (?i)^[0-9a-f]{8}-?[0-9a-f]{4}-?5[0-9a-f]{3}-?[89ab][0-9a-f]{3}-?[0-9a-f]{12}$ - isbn: an ISBN10 or ISBN13 number string like \"0321751043\" or \"978-0321751041\" - isbn10: an ISBN10 number string like \"0321751043\" - isbn13: an ISBN13 number string like \"978-0321751041\" - creditcard: a credit card number defined by the regex ^(?:4[0-9]{12}(?:[0-9]{3})?|5[1-5][0-9]{14}|6(?:011|5[0-9][0-9])[0-9]{12}|3[47][0-9]{13}|3(?:0[0-5]|[68][0-9])[0-9]{11}|(?:2131|1800|35d{3})d{11})$ with any non digit characters mixed in - ssn: a U.S. social security number following the regex ^d{3}[- ]?d{2}[- ]?d{4}$ - hexcolor: an hexadecimal color code like \"#FFFFFF: following the regex ^#?([0-9a-fA-F]{3}|[0-9a-fA-F]{6})$ - rgbcolor: an RGB color code like rgb like \"rgb(255,255,2559\" - byte: base64 encoded binary data - password: any kind of string - date: a date string like \"2006-01-02\" as defined by full-date in RFC3339 - duration: a duration string like \"22 ns\" as parsed by Golang time.ParseDuration or compatible with Scala duration format - datetime: a date time string like \"2014-12-15T19:30:20.000Z\" as defined by date-time in RFC3339.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"title\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"default\": { SchemaProps: spec.SchemaProps{ Description: \"default is a default value for undefined object fields. Defaulting is a beta feature under the CustomResourceDefaulting feature gate. Defaulting requires spec.preserveUnknownFields to be false.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSON\"), }, }, \"maximum\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"number\"}, Format: \"double\", }, }, \"exclusiveMaximum\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"boolean\"}, Format: \"\", }, }, \"minimum\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"number\"}, Format: \"double\", }, }, \"exclusiveMinimum\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"boolean\"}, Format: \"\", }, }, \"maxLength\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"integer\"}, Format: \"int64\", }, }, \"minLength\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"integer\"}, Format: \"int64\", }, }, \"pattern\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"maxItems\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"integer\"}, Format: \"int64\", }, }, \"minItems\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"integer\"}, Format: \"int64\", }, }, \"uniqueItems\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"boolean\"}, Format: \"\", }, }, \"multipleOf\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"number\"}, Format: \"double\", }, }, \"enum\": { SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSON\"), }, }, }, }, }, \"maxProperties\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"integer\"}, Format: \"int64\", }, }, \"minProperties\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"integer\"}, Format: \"int64\", }, }, \"required\": { SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"items\": { SchemaProps: spec.SchemaProps{ Ref: ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaPropsOrArray\"), }, }, \"allOf\": { SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaProps\"), }, }, }, }, }, \"oneOf\": { SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaProps\"), }, }, }, }, }, \"anyOf\": { SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaProps\"), }, }, }, }, }, \"not\": { SchemaProps: spec.SchemaProps{ Ref: ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaProps\"), }, }, \"properties\": { SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaProps\"), }, }, }, }, }, \"additionalProperties\": { SchemaProps: spec.SchemaProps{ Ref: ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaPropsOrBool\"), }, }, \"patternProperties\": { SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaProps\"), }, }, }, }, }, \"dependencies\": { SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaPropsOrStringArray\"), }, }, }, }, }, \"additionalItems\": { SchemaProps: spec.SchemaProps{ Ref: ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaPropsOrBool\"), }, }, \"definitions\": { SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaProps\"), }, }, }, }, }, \"externalDocs\": { SchemaProps: spec.SchemaProps{ Ref: ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.ExternalDocumentation\"), }, }, \"example\": { SchemaProps: spec.SchemaProps{ Ref: ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSON\"), }, }, \"nullable\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"boolean\"}, Format: \"\", }, }, \"x-kubernetes-preserve-unknown-fields\": { SchemaProps: spec.SchemaProps{ Description: \"x-kubernetes-preserve-unknown-fields stops the API server decoding step from pruning fields which are not specified in the validation schema. This affects fields recursively, but switches back to normal pruning behaviour if nested properties or additionalProperties are specified in the schema. This can either be true or undefined. False is forbidden.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"x-kubernetes-embedded-resource\": { SchemaProps: spec.SchemaProps{ Description: \"x-kubernetes-embedded-resource defines that the value is an embedded Kubernetes runtime.Object, with TypeMeta and ObjectMeta. The type must be object. It is allowed to further restrict the embedded object. kind, apiVersion and metadata are validated automatically. x-kubernetes-preserve-unknown-fields is allowed to be true, but does not have to be if the object is fully specified (up to kind, apiVersion, metadata).\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"x-kubernetes-int-or-string\": { SchemaProps: spec.SchemaProps{ Description: \"x-kubernetes-int-or-string specifies that this value is either an integer or a string. If this is true, an empty type is allowed and type as child of anyOf is permitted if following one of the following patterns:nn1) anyOf:n   - type: integern   - type: stringn2) allOf:n   - anyOf:n     - type: integern     - type: stringn   - ... zero or more\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"x-kubernetes-list-map-keys\": { SchemaProps: spec.SchemaProps{ Description: \"x-kubernetes-list-map-keys annotates an array with the x-kubernetes-list-type `map` by specifying the keys used as the index of the map.nnThis tag MUST only be used on lists that have the \"x-kubernetes-list-type\" extension set to \"map\". Also, the values specified for this attribute must be a scalar typed field of the child structure (no nesting is supported).nnThe properties specified must either be required or have a default value, to ensure those properties are present for all list items.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"x-kubernetes-list-type\": { SchemaProps: spec.SchemaProps{ Description: \"x-kubernetes-list-type annotates an array to further describe its topology. This extension must only be used on lists and may have 3 possible values:nn1) `atomic`: the list is treated as a single entity, like a scalar.n     Atomic lists will be entirely replaced when updated. This extensionn     may be used on any type of list (struct, scalar, ...).n2) `set`:n     Sets are lists that must not have multiple items with the same value. Eachn     value must be a scalar, an object with x-kubernetes-map-type `atomic` or ann     array with x-kubernetes-list-type `atomic`.n3) `map`:n     These lists are like maps in that their elements have a non-index keyn     used to identify them. Order is preserved upon merge. The map tagn     must only be used on a list with elements of type object.nDefaults to atomic for arrays.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"x-kubernetes-map-type\": { SchemaProps: spec.SchemaProps{ Description: \"x-kubernetes-map-type annotates an object to further describe its topology. This extension must only be used when type is object and may have 2 possible values:nn1) `granular`:n     These maps are actual maps (key-value pairs) and each fields are independentn     from each other (they can each be manipulated by separate actors). This isn     the default behaviour for all maps.n2) `atomic`: the list is treated as a single entity, like a scalar.n     Atomic maps will be entirely replaced when updated.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"x-kubernetes-validations\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"rule\", }, \"x-kubernetes-list-type\":       \"map\", \"x-kubernetes-patch-merge-key\": \"rule\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"x-kubernetes-validations describes a list of validation rules written in the CEL expression language. This field is an alpha-level. Using this field requires the feature gate `CustomResourceValidationExpressions` to be enabled.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.ValidationRule\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.ExternalDocumentation\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSON\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaProps\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaPropsOrArray\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaPropsOrBool\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.JSONSchemaPropsOrStringArray\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.ValidationRule\"}, } } func schema_pkg_apis_apiextensions_v1_JSONSchemaPropsOrArray(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"JSONSchemaPropsOrArray represents a value that can either be a JSONSchemaProps or an array of JSONSchemaProps. Mainly here for serialization purposes.\", Type:        v1.JSONSchemaPropsOrArray{}.OpenAPISchemaType(), Format:      v1.JSONSchemaPropsOrArray{}.OpenAPISchemaFormat(), }, }, } } func schema_pkg_apis_apiextensions_v1_JSONSchemaPropsOrBool(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"JSONSchemaPropsOrBool represents JSONSchemaProps or a boolean value. Defaults to true for the boolean property.\", Type:        v1.JSONSchemaPropsOrBool{}.OpenAPISchemaType(), Format:      v1.JSONSchemaPropsOrBool{}.OpenAPISchemaFormat(), }, }, } } func schema_pkg_apis_apiextensions_v1_JSONSchemaPropsOrStringArray(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"JSONSchemaPropsOrStringArray represents a JSONSchemaProps or a string array.\", Type:        v1.JSONSchemaPropsOrStringArray{}.OpenAPISchemaType(), Format:      v1.JSONSchemaPropsOrStringArray{}.OpenAPISchemaFormat(), }, }, } } func schema_pkg_apis_apiextensions_v1_ServiceReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ServiceReference holds a reference to Service.legacy.k8s.io\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"namespace is the namespace of the service. Required\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the name of the service. Required\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"path\": { SchemaProps: spec.SchemaProps{ Description: \"path is an optional URL path at which the webhook will be contacted.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"port\": { SchemaProps: spec.SchemaProps{ Description: \"port is an optional service port at which the webhook will be contacted. `port` should be a valid port number (1-65535, inclusive). Defaults to 443 for backward compatibility.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"namespace\", \"name\"}, }, }, } } func schema_pkg_apis_apiextensions_v1_ValidationRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ValidationRule describes a validation rule written in the CEL expression language.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"rule\": { SchemaProps: spec.SchemaProps{ Description: \"Rule represents the expression which will be evaluated by CEL. ref: https://github.com/google/cel-spec The Rule is scoped to the location of the x-kubernetes-validations extension in the schema. The `self` variable in the CEL expression is bound to the scoped value. Example: - Rule scoped to the root of a resource with a status subresource: {\"rule\": \"self.status.actual <= self.spec.maxDesired\"}nnIf the Rule is scoped to an object with properties, the accessible properties of the object are field selectable via `self.field` and field presence can be checked via `has(self.field)`. Null valued fields are treated as absent fields in CEL expressions. If the Rule is scoped to an object with additionalProperties (i.e. a map) the value of the map are accessible via `self[mapKey]`, map containment can be checked via `mapKey in self` and all entries of the map are accessible via CEL macros and functions such as `self.all(...)`. If the Rule is scoped to an array, the elements of the array are accessible via `self[i]` and also by macros and functions. If the Rule is scoped to a scalar, `self` is bound to the scalar value. Examples: - Rule scoped to a map of objects: {\"rule\": \"self.components['Widget'].priority < 10\"} - Rule scoped to a list of integers: {\"rule\": \"self.values.all(value, value >= 0 && value < 100)\"} - Rule scoped to a string value: {\"rule\": \"self.startsWith('kube')\"}nnThe `apiVersion`, `kind`, `metadata.name` and `metadata.generateName` are always accessible from the root of the object and from any x-kubernetes-embedded-resource annotated objects. No other metadata properties are accessible.nnUnknown data preserved in custom resources via x-kubernetes-preserve-unknown-fields is not accessible in CEL expressions. This includes: - Unknown field values that are preserved by object schemas with x-kubernetes-preserve-unknown-fields. - Object properties where the property schema is of an \"unknown type\". An \"unknown type\" is recursively defined as:n  - A schema with no type and x-kubernetes-preserve-unknown-fields set to truen  - An array where the items schema is of an \"unknown type\"n  - An object where the additionalProperties schema is of an \"unknown type\"nnOnly property names of the form `[a-zA-Z_.-/][a-zA-Z0-9_.-/]*` are accessible. Accessible property names are escaped according to the following rules when accessed in the expression: - '__' escapes to '__underscores__' - '.' escapes to '__dot__' - '-' escapes to '__dash__' - '/' escapes to '__slash__' - Property names that exactly match a CEL RESERVED keyword escape to '__{keyword}__'. The keywords are:nt  \"true\", \"false\", \"null\", \"in\", \"as\", \"break\", \"const\", \"continue\", \"else\", \"for\", \"function\", \"if\",nt  \"import\", \"let\", \"loop\", \"package\", \"namespace\", \"return\".nExamples:n  - Rule accessing a property named \"namespace\": {\"rule\": \"self.__namespace__ > 0\"}n  - Rule accessing a property named \"x-prop\": {\"rule\": \"self.x__dash__prop > 0\"}n  - Rule accessing a property named \"redact__d\": {\"rule\": \"self.redact__underscores__d > 0\"}nnEquality on arrays with x-kubernetes-list-type of 'set' or 'map' ignores element order, i.e. [1, 2] == [2, 1]. Concatenation on arrays with x-kubernetes-list-type use the semantics of the list type:n  - 'set': `X + Y` performs a union where the array positions of all elements in `X` are preserved andn    non-intersecting elements in `Y` are appended, retaining their partial order.n  - 'map': `X + Y` performs a merge where the array positions of all keys in `X` are preserved but the valuesn    are overwritten by values in `Y` when the key sets of `X` and `Y` intersect. Elements in `Y` withn    non-intersecting keys are appended, retaining their partial order.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"Message represents the message displayed when validation fails. The message is required if the Rule contains line breaks. The message must not contain line breaks. If unset, the message is \"failed rule: {Rule}\". e.g. \"must be a URL with the host matching spec.host\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"rule\"}, }, }, } } func schema_pkg_apis_apiextensions_v1_WebhookClientConfig(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"WebhookClientConfig contains the information to make a TLS connection with the webhook.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"url\": { SchemaProps: spec.SchemaProps{ Description: \"url gives the location of the webhook, in standard URL form (`scheme://host:port/path`). Exactly one of `url` or `service` must be specified.nnThe `host` should not refer to a service running in the cluster; use the `service` field instead. The host might be resolved via external DNS in some apiservers (e.g., `kube-apiserver` cannot resolve in-cluster DNS as that would be a layering violation). `host` may also be an IP address.nnPlease note that using `localhost` or `127.0.0.1` as a `host` is risky unless you take great care to run this webhook on all hosts which run an apiserver which might need to make calls to this webhook. Such installs are likely to be non-portable, i.e., not easy to turn up in a new cluster.nnThe scheme must be \"https\"; the URL must begin with \"https://\".nnA path is optional, and if present may be any string permissible in a URL. You may use the path to pass an arbitrary string to the webhook, for example, a cluster identifier.nnAttempting to use a user or basic auth e.g. \"user:password@\" is not allowed. Fragments (\"#...\") and query parameters (\"?...\") are not allowed, either.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"service\": { SchemaProps: spec.SchemaProps{ Description: \"service is a reference to the service for this webhook. Either service or url must be specified.nnIf the webhook is running within the cluster, then you should use `service`.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.ServiceReference\"), }, }, \"caBundle\": { SchemaProps: spec.SchemaProps{ Description: \"caBundle is a PEM encoded CA bundle which will be used to validate the webhook's server certificate. If unspecified, system trust roots on the apiserver are used.\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.ServiceReference\"}, } } func schema_pkg_apis_apiextensions_v1_WebhookConversion(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"WebhookConversion describes how to call a conversion webhook\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"clientConfig\": { SchemaProps: spec.SchemaProps{ Description: \"clientConfig is the instructions for how to call the webhook if strategy is `Webhook`.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.WebhookClientConfig\"), }, }, \"conversionReviewVersions\": { SchemaProps: spec.SchemaProps{ Description: \"conversionReviewVersions is an ordered list of preferred `ConversionReview` versions the Webhook expects. The API server will use the first version in the list which it supports. If none of the versions specified in this list are supported by API server, conversion will fail for the custom resource. If a persisted Webhook configuration specifies allowed versions and does not include any versions known to the API Server, calls to the webhook will fail.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"conversionReviewVersions\"}, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1.WebhookClientConfig\"}, } } func schema_pkg_apis_apiextensions_v1beta1_ConversionRequest(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ConversionRequest describes the conversion request parameters.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"uid\": { SchemaProps: spec.SchemaProps{ Description: \"uid is an identifier for the individual request/response. It allows distinguishing instances of requests which are otherwise identical (parallel requests, etc). The UID is meant to track the round trip (request/response) between the Kubernetes API server and the webhook, not the user request. It is suitable for correlating log entries between the webhook and apiserver, for either auditing or debugging.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"desiredAPIVersion\": { SchemaProps: spec.SchemaProps{ Description: \"desiredAPIVersion is the version to convert given objects to. e.g. \"myapi.example.com/v1\"\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"objects\": { SchemaProps: spec.SchemaProps{ Description: \"objects is the list of custom resource objects to be converted.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/runtime.RawExtension\"), }, }, }, }, }, }, Required: []string{\"uid\", \"desiredAPIVersion\", \"objects\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/runtime.RawExtension\"}, } } func schema_pkg_apis_apiextensions_v1beta1_ConversionResponse(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ConversionResponse describes a conversion response.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"uid\": { SchemaProps: spec.SchemaProps{ Description: \"uid is an identifier for the individual request/response. This should be copied over from the corresponding `request.uid`.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"convertedObjects\": { SchemaProps: spec.SchemaProps{ Description: \"convertedObjects is the list of converted version of `request.objects` if the `result` is successful, otherwise empty. The webhook is expected to set `apiVersion` of these objects to the `request.desiredAPIVersion`. The list must also have the same size as the input list with the same objects in the same order (equal kind, metadata.uid, metadata.name and metadata.namespace). The webhook is allowed to mutate labels and annotations. Any other change to the metadata is silently ignored.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/runtime.RawExtension\"), }, }, }, }, }, \"result\": { SchemaProps: spec.SchemaProps{ Description: \"result contains the result of conversion with extra details if the conversion failed. `result.status` determines if the conversion failed or succeeded. The `result.status` field is required and represents the success or failure of the conversion. A successful conversion must set `result.status` to `Success`. A failed conversion must set `result.status` to `Failure` and provide more details in `result.message` and return http status 200. The `result.message` will be used to construct an error message for the end user.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Status\"), }, }, }, Required: []string{\"uid\", \"convertedObjects\", \"result\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Status\", \"k8s.io/apimachinery/pkg/runtime.RawExtension\"}, } } func schema_pkg_apis_apiextensions_v1beta1_ConversionReview(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ConversionReview describes a conversion request/response.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"request\": { SchemaProps: spec.SchemaProps{ Description: \"request describes the attributes for the conversion request.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.ConversionRequest\"), }, }, \"response\": { SchemaProps: spec.SchemaProps{ Description: \"response describes the attributes for the conversion response.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.ConversionResponse\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.ConversionRequest\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.ConversionResponse\"}, } } func schema_pkg_apis_apiextensions_v1beta1_CustomResourceColumnDefinition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceColumnDefinition specifies a column for server side printing.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is a human readable name for the column.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type is an OpenAPI type definition for this column. See https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#data-types for details.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"format\": { SchemaProps: spec.SchemaProps{ Description: \"format is an optional OpenAPI type definition for this column. The 'name' format is applied to the primary identifier column to assist in clients identifying column is the resource name. See https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#data-types for details.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"description\": { SchemaProps: spec.SchemaProps{ Description: \"description is a human readable description of this column.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"priority\": { SchemaProps: spec.SchemaProps{ Description: \"priority is an integer defining the relative importance of this column compared to others. Lower numbers are considered higher priority. Columns that may be omitted in limited space scenarios should be given a priority greater than 0.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"JSONPath\": { SchemaProps: spec.SchemaProps{ Description: \"JSONPath is a simple JSON path (i.e. with array notation) which is evaluated against each custom resource to produce the value for this column.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"type\", \"JSONPath\"}, }, }, } } func schema_pkg_apis_apiextensions_v1beta1_CustomResourceConversion(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceConversion describes how to convert different versions of a CR.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"strategy\": { SchemaProps: spec.SchemaProps{ Description: \"strategy specifies how custom resources are converted between versions. Allowed values are: - `None`: The converter only change the apiVersion and would not touch any other field in the custom resource. - `Webhook`: API Server will call to an external webhook to do the conversion. Additional informationn  is needed for this option. This requires spec.preserveUnknownFields to be false, and spec.conversion.webhookClientConfig to be set.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"webhookClientConfig\": { SchemaProps: spec.SchemaProps{ Description: \"webhookClientConfig is the instructions for how to call the webhook if strategy is `Webhook`. Required when `strategy` is set to `Webhook`.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.WebhookClientConfig\"), }, }, \"conversionReviewVersions\": { SchemaProps: spec.SchemaProps{ Description: \"conversionReviewVersions is an ordered list of preferred `ConversionReview` versions the Webhook expects. The API server will use the first version in the list which it supports. If none of the versions specified in this list are supported by API server, conversion will fail for the custom resource. If a persisted Webhook configuration specifies allowed versions and does not include any versions known to the API Server, calls to the webhook will fail. Defaults to `[\"v1beta1\"]`.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"strategy\"}, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.WebhookClientConfig\"}, } } func schema_pkg_apis_apiextensions_v1beta1_CustomResourceDefinition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceDefinition represents a resource that should be exposed on the API server.  Its name MUST be in the format <.spec.name>.<.spec.group>. Deprecated in v1.16, planned for removal in v1.22. Use apiextensions.k8s.io/v1 CustomResourceDefinition instead.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"spec describes how the user wants the resources to appear\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinitionSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"status indicates the actual state of the CustomResourceDefinition\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinitionStatus\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinitionSpec\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinitionStatus\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_pkg_apis_apiextensions_v1beta1_CustomResourceDefinitionCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceDefinitionCondition contains details for the current condition of this pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type is the type of the condition. Types include Established, NamesAccepted and Terminating.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"status is the status of the condition. Can be True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"lastTransitionTime last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"reason is a unique, one-word, CamelCase reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"message is a human-readable message indicating details about last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_pkg_apis_apiextensions_v1beta1_CustomResourceDefinitionList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceDefinitionList is a list of CustomResourceDefinition objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items list individual CustomResourceDefinition objects\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinition\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinition\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"}, } } func schema_pkg_apis_apiextensions_v1beta1_CustomResourceDefinitionNames(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceDefinitionNames indicates the names to serve this CustomResourceDefinition\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"plural\": { SchemaProps: spec.SchemaProps{ Description: \"plural is the plural name of the resource to serve. The custom resources are served under `/apis/<group>/<version>/.../<plural>`. Must match the name of the CustomResourceDefinition (in the form `<names.plural>.<group>`). Must be all lowercase.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"singular\": { SchemaProps: spec.SchemaProps{ Description: \"singular is the singular name of the resource. It must be all lowercase. Defaults to lowercased `kind`.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"shortNames\": { SchemaProps: spec.SchemaProps{ Description: \"shortNames are short names for the resource, exposed in API discovery documents, and used by clients to support invocations like `kubectl get <shortname>`. It must be all lowercase.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"kind is the serialized kind of the resource. It is normally CamelCase and singular. Custom resource instances will use this value as the `kind` attribute in API calls.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"listKind\": { SchemaProps: spec.SchemaProps{ Description: \"listKind is the serialized kind of the list for this resource. Defaults to \"`kind`List\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"categories\": { SchemaProps: spec.SchemaProps{ Description: \"categories is a list of grouped resources this custom resource belongs to (e.g. 'all'). This is published in API discovery documents, and used by clients to support invocations like `kubectl get all`.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"plural\", \"kind\"}, }, }, } } func schema_pkg_apis_apiextensions_v1beta1_CustomResourceDefinitionSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceDefinitionSpec describes how a user wants their resource to appear\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"group\": { SchemaProps: spec.SchemaProps{ Description: \"group is the API group of the defined custom resource. The custom resources are served under `/apis/<group>/...`. Must match the name of the CustomResourceDefinition (in the form `<names.plural>.<group>`).\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"version\": { SchemaProps: spec.SchemaProps{ Description: \"version is the API version of the defined custom resource. The custom resources are served under `/apis/<group>/<version>/...`. Must match the name of the first item in the `versions` list if `version` and `versions` are both specified. Optional if `versions` is specified. Deprecated: use `versions` instead.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"names\": { SchemaProps: spec.SchemaProps{ Description: \"names specify the resource and kind names for the custom resource.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinitionNames\"), }, }, \"scope\": { SchemaProps: spec.SchemaProps{ Description: \"scope indicates whether the defined custom resource is cluster- or namespace-scoped. Allowed values are `Cluster` and `Namespaced`. Default is `Namespaced`.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"validation\": { SchemaProps: spec.SchemaProps{ Description: \"validation describes the schema used for validation and pruning of the custom resource. If present, this validation schema is used to validate all versions. Top-level and per-version schemas are mutually exclusive.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceValidation\"), }, }, \"subresources\": { SchemaProps: spec.SchemaProps{ Description: \"subresources specify what subresources the defined custom resource has. If present, this field configures subresources for all versions. Top-level and per-version subresources are mutually exclusive.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceSubresources\"), }, }, \"versions\": { SchemaProps: spec.SchemaProps{ Description: \"versions is the list of all API versions of the defined custom resource. Optional if `version` is specified. The name of the first item in the `versions` list must match the `version` field if `version` and `versions` are both specified. Version names are used to compute the order in which served versions are listed in API discovery. If the version string is \"kube-like\", it will sort above non \"kube-like\" version strings, which are ordered lexicographically. \"Kube-like\" versions start with a \"v\", then are followed by a number (the major version), then optionally the string \"alpha\" or \"beta\" and another number (the minor version). These are sorted first by GA > beta > alpha (where GA is a version with no suffix such as beta or alpha), and then by comparing major version, then minor version. An example sorted list of versions: v10, v2, v1, v11beta2, v10beta3, v3beta1, v12alpha1, v11alpha2, foo1, foo10.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinitionVersion\"), }, }, }, }, }, \"additionalPrinterColumns\": { SchemaProps: spec.SchemaProps{ Description: \"additionalPrinterColumns specifies additional columns returned in Table output. See https://kubernetes.io/docs/reference/using-api/api-concepts/#receiving-resources-as-tables for details. If present, this field configures columns for all versions. Top-level and per-version columns are mutually exclusive. If no top-level or per-version columns are specified, a single column displaying the age of the custom resource is used.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceColumnDefinition\"), }, }, }, }, }, \"conversion\": { SchemaProps: spec.SchemaProps{ Description: \"conversion defines conversion settings for the CRD.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceConversion\"), }, }, \"preserveUnknownFields\": { SchemaProps: spec.SchemaProps{ Description: \"preserveUnknownFields indicates that object fields which are not specified in the OpenAPI schema should be preserved when persisting to storage. apiVersion, kind, metadata and known fields inside metadata are always preserved. If false, schemas must be defined for all versions. Defaults to true in v1beta for backwards compatibility. Deprecated: will be required to be false in v1. Preservation of unknown fields can be specified in the validation schema using the `x-kubernetes-preserve-unknown-fields: true` extension. See https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/#pruning-versus-preserving-unknown-fields for details.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"group\", \"names\", \"scope\"}, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceColumnDefinition\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceConversion\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinitionNames\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinitionVersion\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceSubresources\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceValidation\"}, } } func schema_pkg_apis_apiextensions_v1beta1_CustomResourceDefinitionStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceDefinitionStatus indicates the state of the CustomResourceDefinition\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"type\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"conditions indicate state for particular aspects of a CustomResourceDefinition\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinitionCondition\"), }, }, }, }, }, \"acceptedNames\": { SchemaProps: spec.SchemaProps{ Description: \"acceptedNames are the names that are actually being used to serve discovery. They may be different than the names in spec.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinitionNames\"), }, }, \"storedVersions\": { SchemaProps: spec.SchemaProps{ Description: \"storedVersions lists all versions of CustomResources that were ever persisted. Tracking these versions allows a migration path for stored versions in etcd. The field is mutable so a migration controller can finish a migration to another version (ensuring no old objects are left in storage), and then remove the rest of the versions from this list. Versions may not be removed from `spec.versions` while they exist in this list.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinitionCondition\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceDefinitionNames\"}, } } func schema_pkg_apis_apiextensions_v1beta1_CustomResourceDefinitionVersion(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceDefinitionVersion describes a version for CRD.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the version name, e.g. \u201cv1\u201d, \u201cv2beta1\u201d, etc. The custom resources are served under this version at `/apis/<group>/<version>/...` if `served` is true.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"served\": { SchemaProps: spec.SchemaProps{ Description: \"served is a flag enabling/disabling this version from being served via REST APIs\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"storage\": { SchemaProps: spec.SchemaProps{ Description: \"storage indicates this version should be used when persisting custom resources to storage. There must be exactly one version with storage=true.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"deprecated\": { SchemaProps: spec.SchemaProps{ Description: \"deprecated indicates this version of the custom resource API is deprecated. When set to true, API requests to this version receive a warning header in the server response. Defaults to false.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"deprecationWarning\": { SchemaProps: spec.SchemaProps{ Description: \"deprecationWarning overrides the default warning returned to API clients. May only be set when `deprecated` is true. The default warning indicates this version is deprecated and recommends use of the newest served version of equal or greater stability, if one exists.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"schema\": { SchemaProps: spec.SchemaProps{ Description: \"schema describes the schema used for validation and pruning of this version of the custom resource. Top-level and per-version schemas are mutually exclusive. Per-version schemas must not all be set to identical values (top-level validation schema should be used instead).\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceValidation\"), }, }, \"subresources\": { SchemaProps: spec.SchemaProps{ Description: \"subresources specify what subresources this version of the defined custom resource have. Top-level and per-version subresources are mutually exclusive. Per-version subresources must not all be set to identical values (top-level subresources should be used instead).\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceSubresources\"), }, }, \"additionalPrinterColumns\": { SchemaProps: spec.SchemaProps{ Description: \"additionalPrinterColumns specifies additional columns returned in Table output. See https://kubernetes.io/docs/reference/using-api/api-concepts/#receiving-resources-as-tables for details. Top-level and per-version columns are mutually exclusive. Per-version columns must not all be set to identical values (top-level columns should be used instead). If no top-level or per-version columns are specified, a single column displaying the age of the custom resource is used.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceColumnDefinition\"), }, }, }, }, }, }, Required: []string{\"name\", \"served\", \"storage\"}, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceColumnDefinition\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceSubresources\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceValidation\"}, } } func schema_pkg_apis_apiextensions_v1beta1_CustomResourceSubresourceScale(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceSubresourceScale defines how to serve the scale subresource for CustomResources.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"specReplicasPath\": { SchemaProps: spec.SchemaProps{ Description: \"specReplicasPath defines the JSON path inside of a custom resource that corresponds to Scale `spec.replicas`. Only JSON paths without the array notation are allowed. Must be a JSON Path under `.spec`. If there is no value under the given path in the custom resource, the `/scale` subresource will return an error on GET.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"statusReplicasPath\": { SchemaProps: spec.SchemaProps{ Description: \"statusReplicasPath defines the JSON path inside of a custom resource that corresponds to Scale `status.replicas`. Only JSON paths without the array notation are allowed. Must be a JSON Path under `.status`. If there is no value under the given path in the custom resource, the `status.replicas` value in the `/scale` subresource will default to 0.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"labelSelectorPath\": { SchemaProps: spec.SchemaProps{ Description: \"labelSelectorPath defines the JSON path inside of a custom resource that corresponds to Scale `status.selector`. Only JSON paths without the array notation are allowed. Must be a JSON Path under `.status` or `.spec`. Must be set to work with HorizontalPodAutoscaler. The field pointed by this JSON path must be a string field (not a complex selector struct) which contains a serialized label selector in string form. More info: https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions#scale-subresource If there is no value under the given path in the custom resource, the `status.selector` value in the `/scale` subresource will default to the empty string.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"specReplicasPath\", \"statusReplicasPath\"}, }, }, } } func schema_pkg_apis_apiextensions_v1beta1_CustomResourceSubresourceStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceSubresourceStatus defines how to serve the status subresource for CustomResources. Status is represented by the `.status` JSON path inside of a CustomResource. When set, * exposes a /status subresource for the custom resource * PUT requests to the /status subresource take a custom resource object, and ignore changes to anything except the status stanza * PUT/POST/PATCH requests to the custom resource ignore changes to the status stanza\", Type:        []string{\"object\"}, }, }, } } func schema_pkg_apis_apiextensions_v1beta1_CustomResourceSubresources(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceSubresources defines the status and scale subresources for CustomResources.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"status\": { SchemaProps: spec.SchemaProps{ Description: \"status indicates the custom resource should serve a `/status` subresource. When enabled: 1. requests to the custom resource primary endpoint ignore changes to the `status` stanza of the object. 2. requests to the custom resource `/status` subresource ignore changes to anything other than the `status` stanza of the object.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceSubresourceStatus\"), }, }, \"scale\": { SchemaProps: spec.SchemaProps{ Description: \"scale indicates the custom resource should serve a `/scale` subresource that returns an `autoscaling/v1` Scale object.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceSubresourceScale\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceSubresourceScale\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.CustomResourceSubresourceStatus\"}, } } func schema_pkg_apis_apiextensions_v1beta1_CustomResourceValidation(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CustomResourceValidation is a list of validation methods for CustomResources.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"openAPIV3Schema\": { SchemaProps: spec.SchemaProps{ Description: \"openAPIV3Schema is the OpenAPI v3 schema to use for validation and pruning.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaProps\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaProps\"}, } } func schema_pkg_apis_apiextensions_v1beta1_ExternalDocumentation(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExternalDocumentation allows referencing an external resource for extended documentation.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"description\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"url\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, }, }, }, } } func schema_pkg_apis_apiextensions_v1beta1_JSON(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"JSON represents any valid JSON value. These types are supported: bool, int64, float64, string, []interface{}, map[string]interface{} and nil.\", Type:        v1beta1.JSON{}.OpenAPISchemaType(), Format:      v1beta1.JSON{}.OpenAPISchemaFormat(), }, }, } } func schema_pkg_apis_apiextensions_v1beta1_JSONSchemaProps(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"JSONSchemaProps is a JSON-Schema following Specification Draft 4 (http://json-schema.org/).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"id\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"$schema\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"$ref\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"description\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"type\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"format\": { SchemaProps: spec.SchemaProps{ Description: \"format is an OpenAPI v3 format string. Unknown formats are ignored. The following formats are validated:nn- bsonobjectid: a bson object ID, i.e. a 24 characters hex string - uri: an URI as parsed by Golang net/url.ParseRequestURI - email: an email address as parsed by Golang net/mail.ParseAddress - hostname: a valid representation for an Internet host name, as defined by RFC 1034, section 3.1 [RFC1034]. - ipv4: an IPv4 IP as parsed by Golang net.ParseIP - ipv6: an IPv6 IP as parsed by Golang net.ParseIP - cidr: a CIDR as parsed by Golang net.ParseCIDR - mac: a MAC address as parsed by Golang net.ParseMAC - uuid: an UUID that allows uppercase defined by the regex (?i)^[0-9a-f]{8}-?[0-9a-f]{4}-?[0-9a-f]{4}-?[0-9a-f]{4}-?[0-9a-f]{12}$ - uuid3: an UUID3 that allows uppercase defined by the regex (?i)^[0-9a-f]{8}-?[0-9a-f]{4}-?3[0-9a-f]{3}-?[0-9a-f]{4}-?[0-9a-f]{12}$ - uuid4: an UUID4 that allows uppercase defined by the regex (?i)^[0-9a-f]{8}-?[0-9a-f]{4}-?4[0-9a-f]{3}-?[89ab][0-9a-f]{3}-?[0-9a-f]{12}$ - uuid5: an UUID5 that allows uppercase defined by the regex (?i)^[0-9a-f]{8}-?[0-9a-f]{4}-?5[0-9a-f]{3}-?[89ab][0-9a-f]{3}-?[0-9a-f]{12}$ - isbn: an ISBN10 or ISBN13 number string like \"0321751043\" or \"978-0321751041\" - isbn10: an ISBN10 number string like \"0321751043\" - isbn13: an ISBN13 number string like \"978-0321751041\" - creditcard: a credit card number defined by the regex ^(?:4[0-9]{12}(?:[0-9]{3})?|5[1-5][0-9]{14}|6(?:011|5[0-9][0-9])[0-9]{12}|3[47][0-9]{13}|3(?:0[0-5]|[68][0-9])[0-9]{11}|(?:2131|1800|35d{3})d{11})$ with any non digit characters mixed in - ssn: a U.S. social security number following the regex ^d{3}[- ]?d{2}[- ]?d{4}$ - hexcolor: an hexadecimal color code like \"#FFFFFF: following the regex ^#?([0-9a-fA-F]{3}|[0-9a-fA-F]{6})$ - rgbcolor: an RGB color code like rgb like \"rgb(255,255,2559\" - byte: base64 encoded binary data - password: any kind of string - date: a date string like \"2006-01-02\" as defined by full-date in RFC3339 - duration: a duration string like \"22 ns\" as parsed by Golang time.ParseDuration or compatible with Scala duration format - datetime: a date time string like \"2014-12-15T19:30:20.000Z\" as defined by date-time in RFC3339.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"title\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"default\": { SchemaProps: spec.SchemaProps{ Description: \"default is a default value for undefined object fields. Defaulting is a beta feature under the CustomResourceDefaulting feature gate. CustomResourceDefinitions with defaults must be created using the v1 (or newer) CustomResourceDefinition API.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSON\"), }, }, \"maximum\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"number\"}, Format: \"double\", }, }, \"exclusiveMaximum\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"boolean\"}, Format: \"\", }, }, \"minimum\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"number\"}, Format: \"double\", }, }, \"exclusiveMinimum\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"boolean\"}, Format: \"\", }, }, \"maxLength\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"integer\"}, Format: \"int64\", }, }, \"minLength\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"integer\"}, Format: \"int64\", }, }, \"pattern\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"maxItems\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"integer\"}, Format: \"int64\", }, }, \"minItems\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"integer\"}, Format: \"int64\", }, }, \"uniqueItems\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"boolean\"}, Format: \"\", }, }, \"multipleOf\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"number\"}, Format: \"double\", }, }, \"enum\": { SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSON\"), }, }, }, }, }, \"maxProperties\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"integer\"}, Format: \"int64\", }, }, \"minProperties\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"integer\"}, Format: \"int64\", }, }, \"required\": { SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"items\": { SchemaProps: spec.SchemaProps{ Ref: ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaPropsOrArray\"), }, }, \"allOf\": { SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaProps\"), }, }, }, }, }, \"oneOf\": { SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaProps\"), }, }, }, }, }, \"anyOf\": { SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaProps\"), }, }, }, }, }, \"not\": { SchemaProps: spec.SchemaProps{ Ref: ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaProps\"), }, }, \"properties\": { SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaProps\"), }, }, }, }, }, \"additionalProperties\": { SchemaProps: spec.SchemaProps{ Ref: ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaPropsOrBool\"), }, }, \"patternProperties\": { SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaProps\"), }, }, }, }, }, \"dependencies\": { SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaPropsOrStringArray\"), }, }, }, }, }, \"additionalItems\": { SchemaProps: spec.SchemaProps{ Ref: ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaPropsOrBool\"), }, }, \"definitions\": { SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaProps\"), }, }, }, }, }, \"externalDocs\": { SchemaProps: spec.SchemaProps{ Ref: ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.ExternalDocumentation\"), }, }, \"example\": { SchemaProps: spec.SchemaProps{ Ref: ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSON\"), }, }, \"nullable\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"boolean\"}, Format: \"\", }, }, \"x-kubernetes-preserve-unknown-fields\": { SchemaProps: spec.SchemaProps{ Description: \"x-kubernetes-preserve-unknown-fields stops the API server decoding step from pruning fields which are not specified in the validation schema. This affects fields recursively, but switches back to normal pruning behaviour if nested properties or additionalProperties are specified in the schema. This can either be true or undefined. False is forbidden.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"x-kubernetes-embedded-resource\": { SchemaProps: spec.SchemaProps{ Description: \"x-kubernetes-embedded-resource defines that the value is an embedded Kubernetes runtime.Object, with TypeMeta and ObjectMeta. The type must be object. It is allowed to further restrict the embedded object. kind, apiVersion and metadata are validated automatically. x-kubernetes-preserve-unknown-fields is allowed to be true, but does not have to be if the object is fully specified (up to kind, apiVersion, metadata).\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"x-kubernetes-int-or-string\": { SchemaProps: spec.SchemaProps{ Description: \"x-kubernetes-int-or-string specifies that this value is either an integer or a string. If this is true, an empty type is allowed and type as child of anyOf is permitted if following one of the following patterns:nn1) anyOf:n   - type: integern   - type: stringn2) allOf:n   - anyOf:n     - type: integern     - type: stringn   - ... zero or more\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"x-kubernetes-list-map-keys\": { SchemaProps: spec.SchemaProps{ Description: \"x-kubernetes-list-map-keys annotates an array with the x-kubernetes-list-type `map` by specifying the keys used as the index of the map.nnThis tag MUST only be used on lists that have the \"x-kubernetes-list-type\" extension set to \"map\". Also, the values specified for this attribute must be a scalar typed field of the child structure (no nesting is supported).nnThe properties specified must either be required or have a default value, to ensure those properties are present for all list items.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"x-kubernetes-list-type\": { SchemaProps: spec.SchemaProps{ Description: \"x-kubernetes-list-type annotates an array to further describe its topology. This extension must only be used on lists and may have 3 possible values:nn1) `atomic`: the list is treated as a single entity, like a scalar.n     Atomic lists will be entirely replaced when updated. This extensionn     may be used on any type of list (struct, scalar, ...).n2) `set`:n     Sets are lists that must not have multiple items with the same value. Eachn     value must be a scalar, an object with x-kubernetes-map-type `atomic` or ann     array with x-kubernetes-list-type `atomic`.n3) `map`:n     These lists are like maps in that their elements have a non-index keyn     used to identify them. Order is preserved upon merge. The map tagn     must only be used on a list with elements of type object.nDefaults to atomic for arrays.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"x-kubernetes-map-type\": { SchemaProps: spec.SchemaProps{ Description: \"x-kubernetes-map-type annotates an object to further describe its topology. This extension must only be used when type is object and may have 2 possible values:nn1) `granular`:n     These maps are actual maps (key-value pairs) and each fields are independentn     from each other (they can each be manipulated by separate actors). This isn     the default behaviour for all maps.n2) `atomic`: the list is treated as a single entity, like a scalar.n     Atomic maps will be entirely replaced when updated.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"x-kubernetes-validations\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"rule\", }, \"x-kubernetes-list-type\":       \"map\", \"x-kubernetes-patch-merge-key\": \"rule\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"x-kubernetes-validations describes a list of validation rules written in the CEL expression language. This field is an alpha-level. Using this field requires the feature gate `CustomResourceValidationExpressions` to be enabled.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.ValidationRule\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.ExternalDocumentation\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSON\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaProps\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaPropsOrArray\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaPropsOrBool\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.JSONSchemaPropsOrStringArray\", \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.ValidationRule\"}, } } func schema_pkg_apis_apiextensions_v1beta1_JSONSchemaPropsOrArray(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"JSONSchemaPropsOrArray represents a value that can either be a JSONSchemaProps or an array of JSONSchemaProps. Mainly here for serialization purposes.\", Type:        v1beta1.JSONSchemaPropsOrArray{}.OpenAPISchemaType(), Format:      v1beta1.JSONSchemaPropsOrArray{}.OpenAPISchemaFormat(), }, }, } } func schema_pkg_apis_apiextensions_v1beta1_JSONSchemaPropsOrBool(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"JSONSchemaPropsOrBool represents JSONSchemaProps or a boolean value. Defaults to true for the boolean property.\", Type:        v1beta1.JSONSchemaPropsOrBool{}.OpenAPISchemaType(), Format:      v1beta1.JSONSchemaPropsOrBool{}.OpenAPISchemaFormat(), }, }, } } func schema_pkg_apis_apiextensions_v1beta1_JSONSchemaPropsOrStringArray(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"JSONSchemaPropsOrStringArray represents a JSONSchemaProps or a string array.\", Type:        v1beta1.JSONSchemaPropsOrStringArray{}.OpenAPISchemaType(), Format:      v1beta1.JSONSchemaPropsOrStringArray{}.OpenAPISchemaFormat(), }, }, } } func schema_pkg_apis_apiextensions_v1beta1_ServiceReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ServiceReference holds a reference to Service.legacy.k8s.io\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"namespace is the namespace of the service. Required\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the name of the service. Required\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"path\": { SchemaProps: spec.SchemaProps{ Description: \"path is an optional URL path at which the webhook will be contacted.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"port\": { SchemaProps: spec.SchemaProps{ Description: \"port is an optional service port at which the webhook will be contacted. `port` should be a valid port number (1-65535, inclusive). Defaults to 443 for backward compatibility.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"namespace\", \"name\"}, }, }, } } func schema_pkg_apis_apiextensions_v1beta1_ValidationRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ValidationRule describes a validation rule written in the CEL expression language.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"rule\": { SchemaProps: spec.SchemaProps{ Description: \"Rule represents the expression which will be evaluated by CEL. ref: https://github.com/google/cel-spec The Rule is scoped to the location of the x-kubernetes-validations extension in the schema. The `self` variable in the CEL expression is bound to the scoped value. Example: - Rule scoped to the root of a resource with a status subresource: {\"rule\": \"self.status.actual <= self.spec.maxDesired\"}nnIf the Rule is scoped to an object with properties, the accessible properties of the object are field selectable via `self.field` and field presence can be checked via `has(self.field)`. Null valued fields are treated as absent fields in CEL expressions. If the Rule is scoped to an object with additionalProperties (i.e. a map) the value of the map are accessible via `self[mapKey]`, map containment can be checked via `mapKey in self` and all entries of the map are accessible via CEL macros and functions such as `self.all(...)`. If the Rule is scoped to an array, the elements of the array are accessible via `self[i]` and also by macros and functions. If the Rule is scoped to a scalar, `self` is bound to the scalar value. Examples: - Rule scoped to a map of objects: {\"rule\": \"self.components['Widget'].priority < 10\"} - Rule scoped to a list of integers: {\"rule\": \"self.values.all(value, value >= 0 && value < 100)\"} - Rule scoped to a string value: {\"rule\": \"self.startsWith('kube')\"}nnThe `apiVersion`, `kind`, `metadata.name` and `metadata.generateName` are always accessible from the root of the object and from any x-kubernetes-embedded-resource annotated objects. No other metadata properties are accessible.nnUnknown data preserved in custom resources via x-kubernetes-preserve-unknown-fields is not accessible in CEL expressions. This includes: - Unknown field values that are preserved by object schemas with x-kubernetes-preserve-unknown-fields. - Object properties where the property schema is of an \"unknown type\". An \"unknown type\" is recursively defined as:n  - A schema with no type and x-kubernetes-preserve-unknown-fields set to truen  - An array where the items schema is of an \"unknown type\"n  - An object where the additionalProperties schema is of an \"unknown type\"nnOnly property names of the form `[a-zA-Z_.-/][a-zA-Z0-9_.-/]*` are accessible. Accessible property names are escaped according to the following rules when accessed in the expression: - '__' escapes to '__underscores__' - '.' escapes to '__dot__' - '-' escapes to '__dash__' - '/' escapes to '__slash__' - Property names that exactly match a CEL RESERVED keyword escape to '__{keyword}__'. The keywords are:nt  \"true\", \"false\", \"null\", \"in\", \"as\", \"break\", \"const\", \"continue\", \"else\", \"for\", \"function\", \"if\",nt  \"import\", \"let\", \"loop\", \"package\", \"namespace\", \"return\".nExamples:n  - Rule accessing a property named \"namespace\": {\"rule\": \"self.__namespace__ > 0\"}n  - Rule accessing a property named \"x-prop\": {\"rule\": \"self.x__dash__prop > 0\"}n  - Rule accessing a property named \"redact__d\": {\"rule\": \"self.redact__underscores__d > 0\"}nnEquality on arrays with x-kubernetes-list-type of 'set' or 'map' ignores element order, i.e. [1, 2] == [2, 1]. Concatenation on arrays with x-kubernetes-list-type use the semantics of the list type:n  - 'set': `X + Y` performs a union where the array positions of all elements in `X` are preserved andn    non-intersecting elements in `Y` are appended, retaining their partial order.n  - 'map': `X + Y` performs a merge where the array positions of all keys in `X` are preserved but the valuesn    are overwritten by values in `Y` when the key sets of `X` and `Y` intersect. Elements in `Y` withn    non-intersecting keys are appended, retaining their partial order.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"Message represents the message displayed when validation fails. The message is required if the Rule contains line breaks. The message must not contain line breaks. If unset, the message is \"failed rule: {Rule}\". e.g. \"must be a URL with the host matching spec.host\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"rule\"}, }, }, } } func schema_pkg_apis_apiextensions_v1beta1_WebhookClientConfig(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"WebhookClientConfig contains the information to make a TLS connection with the webhook.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"url\": { SchemaProps: spec.SchemaProps{ Description: \"url gives the location of the webhook, in standard URL form (`scheme://host:port/path`). Exactly one of `url` or `service` must be specified.nnThe `host` should not refer to a service running in the cluster; use the `service` field instead. The host might be resolved via external DNS in some apiservers (e.g., `kube-apiserver` cannot resolve in-cluster DNS as that would be a layering violation). `host` may also be an IP address.nnPlease note that using `localhost` or `127.0.0.1` as a `host` is risky unless you take great care to run this webhook on all hosts which run an apiserver which might need to make calls to this webhook. Such installs are likely to be non-portable, i.e., not easy to turn up in a new cluster.nnThe scheme must be \"https\"; the URL must begin with \"https://\".nnA path is optional, and if present may be any string permissible in a URL. You may use the path to pass an arbitrary string to the webhook, for example, a cluster identifier.nnAttempting to use a user or basic auth e.g. \"user:password@\" is not allowed. Fragments (\"#...\") and query parameters (\"?...\") are not allowed, either.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"service\": { SchemaProps: spec.SchemaProps{ Description: \"service is a reference to the service for this webhook. Either service or url must be specified.nnIf the webhook is running within the cluster, then you should use `service`.\", Ref:         ref(\"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.ServiceReference\"), }, }, \"caBundle\": { SchemaProps: spec.SchemaProps{ Description: \"caBundle is a PEM encoded CA bundle which will be used to validate the webhook's server certificate. If unspecified, system trust roots on the apiserver are used.\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1beta1.ServiceReference\"}, } } func schema_apimachinery_pkg_api_resource_Quantity(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshaling in JSON and YAML, in addition to String() and AsInt64() accessors.nnThe serialization format is:nn<quantity>        ::= <signedNumber><suffix>n  (Note that <suffix> may be empty, from the \"\" case in <decimalSI>.)n<digit>           ::= 0 | 1 | ... | 9 <digits>          ::= <digit> | <digit><digits> <number>          ::= <digits> | <digits>.<digits> | <digits>. | .<digits> <sign>            ::= \"+\" | \"-\" <signedNumber>    ::= <number> | <sign><number> <suffix>          ::= <binarySI> | <decimalExponent> | <decimalSI> <binarySI>        ::= Ki | Mi | Gi | Ti | Pi | Ein  (International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)n<decimalSI>       ::= m | \"\" | k | M | G | T | P | En  (Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)n<decimalExponent> ::= \"e\" <signedNumber> | \"E\" <signedNumber>nnNo matter which of the three exponent forms is used, no quantity may represent a number greater than 2^63-1 in magnitude, nor may it have more than 3 decimal places. Numbers larger or more precise will be capped or rounded up. (E.g.: 0.1m will rounded up to 1m.) This may be extended in the future if we require larger or smaller quantities.nnWhen a Quantity is parsed from a string, it will remember the type of suffix it had, and will use the same type again when it is serialized.nnBefore serializing, Quantity will be put in \"canonical form\". This means that Exponent/suffix will be adjusted up or down (with a corresponding increase or decrease in Mantissa) such that:n  a. No precision is lostn  b. No fractional digits will be emittedn  c. The exponent (or suffix) is as large as possible.nThe sign will be omitted unless the number is negative.nnExamples:n  1.5 will be serialized as \"1500m\"n  1.5Gi will be serialized as \"1536Mi\"nnNote that the quantity will NEVER be internally represented by a floating point number. That is the whole point of this exercise.nnNon-canonical values will still parse as long as they are well formed, but will be re-emitted in their canonical form. (So always use canonical form, or don't diff.)nnThis format is intended to make it difficult to use these numbers without writing some sort of special handling code in the hopes that that will cause implementors to also use a fixed point implementation.\", Type:        resource.Quantity{}.OpenAPISchemaType(), Format:      resource.Quantity{}.OpenAPISchemaFormat(), }, }, } } func schema_apimachinery_pkg_api_resource_int64Amount(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"int64Amount represents a fixed precision numerator and arbitrary scale exponent. It is faster than operations on inf.Dec for values that can be represented as int64.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"value\": { SchemaProps: spec.SchemaProps{ Default: 0, Type:    []string{\"integer\"}, Format:  \"int64\", }, }, \"scale\": { SchemaProps: spec.SchemaProps{ Default: 0, Type:    []string{\"integer\"}, Format:  \"int32\", }, }, }, Required: []string{\"value\", \"scale\"}, }, }, } } func schema_pkg_apis_meta_v1_APIGroup(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"APIGroup contains the name, the supported versions, and the preferred version of a group.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the name of the group.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"versions\": { SchemaProps: spec.SchemaProps{ Description: \"versions are the versions supported in this group.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.GroupVersionForDiscovery\"), }, }, }, }, }, \"preferredVersion\": { SchemaProps: spec.SchemaProps{ Description: \"preferredVersion is the version preferred by the API server, which probably is the storage version.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.GroupVersionForDiscovery\"), }, }, \"serverAddressByClientCIDRs\": { SchemaProps: spec.SchemaProps{ Description: \"a map of client CIDR to server address that is serving this group. This is to help clients reach servers in the most network-efficient way possible. Clients can use the appropriate server address as per the CIDR that they match. In case of multiple matches, clients should use the longest matching CIDR. The server returns only those CIDRs that it thinks that the client can match. For example: the master will return an internal IP CIDR only, if the client reaches the server using an internal IP. Server looks at X-Forwarded-For header or X-Real-Ip header or request.RemoteAddr (in that order) to get the client IP.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ServerAddressByClientCIDR\"), }, }, }, }, }, }, Required: []string{\"name\", \"versions\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.GroupVersionForDiscovery\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ServerAddressByClientCIDR\"}, } } func schema_pkg_apis_meta_v1_APIGroupList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"APIGroupList is a list of APIGroup, to allow clients to discover the API at /apis.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"groups\": { SchemaProps: spec.SchemaProps{ Description: \"groups is a list of APIGroup.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.APIGroup\"), }, }, }, }, }, }, Required: []string{\"groups\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.APIGroup\"}, } } func schema_pkg_apis_meta_v1_APIResource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"APIResource specifies the name of a resource and whether it is namespaced.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the plural name of the resource.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"singularName\": { SchemaProps: spec.SchemaProps{ Description: \"singularName is the singular name of the resource.  This allows clients to handle plural and singular opaquely. The singularName is more correct for reporting status on a single item and both singular and plural are allowed from the kubectl CLI interface.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"namespaced\": { SchemaProps: spec.SchemaProps{ Description: \"namespaced indicates if a resource is namespaced or not.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"group\": { SchemaProps: spec.SchemaProps{ Description: \"group is the preferred group of the resource.  Empty implies the group of the containing resource list. For subresources, this may have a different value, for example: Scale\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"version\": { SchemaProps: spec.SchemaProps{ Description: \"version is the preferred version of the resource.  Empty implies the version of the containing resource list For subresources, this may have a different value, for example: v1 (while inside a v1beta1 version of the core resource's group)\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"kind is the kind for the resource (e.g. 'Foo' is the kind for a resource 'foo')\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"verbs\": { SchemaProps: spec.SchemaProps{ Description: \"verbs is a list of supported kube verbs (this includes get, list, watch, create, update, patch, delete, deletecollection, and proxy)\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"shortNames\": { SchemaProps: spec.SchemaProps{ Description: \"shortNames is a list of suggested short names of the resource.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"categories\": { SchemaProps: spec.SchemaProps{ Description: \"categories is a list of the grouped resources this resource belongs to (e.g. 'all')\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"storageVersionHash\": { SchemaProps: spec.SchemaProps{ Description: \"The hash value of the storage version, the version this resource is converted to when written to the data store. Value must be treated as opaque by clients. Only equality comparison on the value is valid. This is an alpha feature and may change or be removed in the future. The field is populated by the apiserver only if the StorageVersionHash feature gate is enabled. This field will remain optional even if it graduates.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"singularName\", \"namespaced\", \"kind\", \"verbs\"}, }, }, } } func schema_pkg_apis_meta_v1_APIResourceList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"APIResourceList is a list of APIResource, it is used to expose the name of the resources supported in a specific group and version, and if the resource is namespaced.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"groupVersion\": { SchemaProps: spec.SchemaProps{ Description: \"groupVersion is the group and version this APIResourceList is for.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"resources contains the name of the resources and if they are namespaced.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.APIResource\"), }, }, }, }, }, }, Required: []string{\"groupVersion\", \"resources\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.APIResource\"}, } } func schema_pkg_apis_meta_v1_APIVersions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"APIVersions lists the versions that are available, to allow clients to discover the API at /api, which is the root path of the legacy v1 API.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"versions\": { SchemaProps: spec.SchemaProps{ Description: \"versions are the api versions that are available.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"serverAddressByClientCIDRs\": { SchemaProps: spec.SchemaProps{ Description: \"a map of client CIDR to server address that is serving this group. This is to help clients reach servers in the most network-efficient way possible. Clients can use the appropriate server address as per the CIDR that they match. In case of multiple matches, clients should use the longest matching CIDR. The server returns only those CIDRs that it thinks that the client can match. For example: the master will return an internal IP CIDR only, if the client reaches the server using an internal IP. Server looks at X-Forwarded-For header or X-Real-Ip header or request.RemoteAddr (in that order) to get the client IP.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ServerAddressByClientCIDR\"), }, }, }, }, }, }, Required: []string{\"versions\", \"serverAddressByClientCIDRs\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ServerAddressByClientCIDR\"}, } } func schema_pkg_apis_meta_v1_ApplyOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ApplyOptions may be provided when applying an API object. FieldManager is required for apply requests. ApplyOptions is equivalent to PatchOptions. It is provided as a convenience with documentation that speaks specifically to how the options fields relate to apply.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"dryRun\": { SchemaProps: spec.SchemaProps{ Description: \"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"force\": { SchemaProps: spec.SchemaProps{ Description: \"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"fieldManager\": { SchemaProps: spec.SchemaProps{ Description: \"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"force\", \"fieldManager\"}, }, }, } } func schema_pkg_apis_meta_v1_Condition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Condition contains details for one aspect of the current state of this API Resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type of condition in CamelCase or in foo.example.com/CamelCase.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"observedGeneration\": { SchemaProps: spec.SchemaProps{ Description: \"observedGeneration represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"lastTransitionTime is the last time the condition transitioned from one status to another. This should be when the underlying condition changed.  If that is not known, then using the time when the API field changed is acceptable.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"reason contains a programmatic identifier indicating the reason for the condition's last transition. Producers of specific condition types may define expected values and meanings for this field, and whether the values are considered a guaranteed API. The value should be a CamelCase string. This field may not be empty.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"message is a human readable message indicating details about the transition. This may be an empty string.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\", \"lastTransitionTime\", \"reason\", \"message\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_pkg_apis_meta_v1_CreateOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CreateOptions may be provided when creating an API object.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"dryRun\": { SchemaProps: spec.SchemaProps{ Description: \"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"fieldManager\": { SchemaProps: spec.SchemaProps{ Description: \"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fieldValidation\": { SchemaProps: spec.SchemaProps{ Description: \"fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_pkg_apis_meta_v1_DeleteOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeleteOptions may be provided when deleting an API object.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"gracePeriodSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"preconditions\": { SchemaProps: spec.SchemaProps{ Description: \"Must be fulfilled before a deletion is carried out. If not possible, a 409 Conflict status will be returned.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Preconditions\"), }, }, \"orphanDependents\": { SchemaProps: spec.SchemaProps{ Description: \"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"propagationPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"dryRun\": { SchemaProps: spec.SchemaProps{ Description: \"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Preconditions\"}, } } func schema_pkg_apis_meta_v1_Duration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Duration is a wrapper around time.Duration which supports correct marshaling to YAML and JSON. In particular, it marshals into strings, which can be used as map keys in json.\", Type:        metav1.Duration{}.OpenAPISchemaType(), Format:      metav1.Duration{}.OpenAPISchemaFormat(), }, }, } } func schema_pkg_apis_meta_v1_FieldsV1(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"FieldsV1 stores a set of fields in a data structure like a Trie, in JSON format.nnEach key is either a '.' representing the field itself, and will always map to an empty set, or a string representing a sub-field or item. The string will follow one of these four formats: 'f:<name>', where <name> is the name of a field in a struct, or key in a map 'v:<value>', where <value> is the exact json formatted value of a list item 'i:<index>', where <index> is position of a item in a list 'k:<keys>', where <keys> is a map of  a list item's key fields to their unique values If a key maps to an empty Fields value, the field that key represents is part of the set.nnThe exact format is defined in sigs.k8s.io/structured-merge-diff\", Type:        []string{\"object\"}, }, }, } } func schema_pkg_apis_meta_v1_GetOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"GetOptions is the standard query options to the standard REST get call.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resourceVersion\": { SchemaProps: spec.SchemaProps{ Description: \"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.nnDefaults to unset\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_pkg_apis_meta_v1_GroupKind(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"GroupKind specifies a Group and a Kind, but does not force a version.  This is useful for identifying concepts during lookup stages without having partially valid types\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"group\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, \"kind\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, Required: []string{\"group\", \"kind\"}, }, }, } } func schema_pkg_apis_meta_v1_GroupResource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"GroupResource specifies a Group and a Resource, but does not force a version.  This is useful for identifying concepts during lookup stages without having partially valid types\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"group\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, \"resource\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, Required: []string{\"group\", \"resource\"}, }, }, } } func schema_pkg_apis_meta_v1_GroupVersion(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"GroupVersion contains the \"group\" and the \"version\", which uniquely identifies the API.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"group\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, \"version\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, Required: []string{\"group\", \"version\"}, }, }, } } func schema_pkg_apis_meta_v1_GroupVersionForDiscovery(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"GroupVersion contains the \"group/version\" and \"version\" string of a version. It is made a struct to keep extensibility.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"groupVersion\": { SchemaProps: spec.SchemaProps{ Description: \"groupVersion specifies the API group and version in the form \"group/version\"\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"version\": { SchemaProps: spec.SchemaProps{ Description: \"version specifies the version in the form of \"version\". This is to save the clients the trouble of splitting the GroupVersion.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"groupVersion\", \"version\"}, }, }, } } func schema_pkg_apis_meta_v1_GroupVersionKind(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"GroupVersionKind unambiguously identifies a kind.  It doesn't anonymously include GroupVersion to avoid automatic coercion.  It doesn't use a GroupVersion to avoid custom marshalling\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"group\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, \"version\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, \"kind\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, Required: []string{\"group\", \"version\", \"kind\"}, }, }, } } func schema_pkg_apis_meta_v1_GroupVersionResource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"GroupVersionResource unambiguously identifies a resource.  It doesn't anonymously include GroupVersion to avoid automatic coercion.  It doesn't use a GroupVersion to avoid custom marshalling\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"group\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, \"version\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, \"resource\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, Required: []string{\"group\", \"version\", \"resource\"}, }, }, } } func schema_pkg_apis_meta_v1_InternalEvent(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"InternalEvent makes watch.Event versioned\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"Type\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, \"Object\": { SchemaProps: spec.SchemaProps{ Description: \"Object is:n * If Type is Added or Modified: the new state of the object.n * If Type is Deleted: the state of the object immediately before deletion.n * If Type is Bookmark: the object (instance of a type being watched) wheren   only ResourceVersion field is set. On successful restart of watch from an   bookmark resourceVersion, client is guaranteed to not get repeat eventn   nor miss any events.n * If Type is Error: *api.Status is recommended; other types may make sensen   depending on context.\", Ref:         ref(\"k8s.io/apimachinery/pkg/runtime.Object\"), }, }, }, Required: []string{\"Type\", \"Object\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/runtime.Object\"}, } } func schema_pkg_apis_meta_v1_LabelSelector(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"A label selector is a label query over a set of resources. The result of matchLabels and matchExpressions are ANDed. An empty label selector matches all objects. A null label selector matches no objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"matchLabels\": { SchemaProps: spec.SchemaProps{ Description: \"matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is \"key\", the operator is \"In\", and the values array contains only \"value\". The requirements are ANDed.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"matchExpressions\": { SchemaProps: spec.SchemaProps{ Description: \"matchExpressions is a list of label selector requirements. The requirements are ANDed.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelectorRequirement\"), }, }, }, }, }, }, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelectorRequirement\"}, } } func schema_pkg_apis_meta_v1_LabelSelectorRequirement(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"A label selector requirement is a selector that contains values, a key, and an operator that relates the key and values.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"key\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"key\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"key is the label key that the selector applies to.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"operator\": { SchemaProps: spec.SchemaProps{ Description: \"operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"values\": { SchemaProps: spec.SchemaProps{ Description: \"values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"key\", \"operator\"}, }, }, } } func schema_pkg_apis_meta_v1_List(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"List holds a list of objects, which may not be known by the server.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of objects\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/runtime.RawExtension\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/apimachinery/pkg/runtime.RawExtension\"}, } } func schema_pkg_apis_meta_v1_ListMeta(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ListMeta describes metadata that synthetic resources must have, including lists and various status objects. A resource may have only one of {ObjectMeta, ListMeta}.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"selfLink\": { SchemaProps: spec.SchemaProps{ Description: \"Deprecated: selfLink is a legacy read-only field that is no longer populated by the system.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resourceVersion\": { SchemaProps: spec.SchemaProps{ Description: \"String that identifies the server's internal version of this object that can be used by clients to determine when objects have changed. Value must be treated as opaque by clients and passed unmodified back to the server. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"continue\": { SchemaProps: spec.SchemaProps{ Description: \"continue may be set if the user set a limit on the number of items returned, and indicates that the server has more data available. The value is opaque and may be used to issue another request to the endpoint that served this list to retrieve the next set of available objects. Continuing a consistent list may not be possible if the server configuration has changed or more than a few minutes have passed. The resourceVersion field returned when using this continue value will be identical to the value in the first response, unless you have received this token from an error message.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"remainingItemCount\": { SchemaProps: spec.SchemaProps{ Description: \"remainingItemCount is the number of subsequent items in the list which are not included in this list response. If the list request contained label or field selectors, then the number of remaining items is unknown and the field will be left unset and omitted during serialization. If the list is complete (either because it is not chunking or because this is the last chunk), then there are no more remaining items and this field will be left unset and omitted during serialization. Servers older than v1.15 do not set this field. The intended use of the remainingItemCount is *estimating* the size of a collection. Clients should not rely on the remainingItemCount to be set or to be exact.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, }, }, }, } } func schema_pkg_apis_meta_v1_ListOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ListOptions is the query options to a standard REST list call.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"labelSelector\": { SchemaProps: spec.SchemaProps{ Description: \"A selector to restrict the list of returned objects by their labels. Defaults to everything.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fieldSelector\": { SchemaProps: spec.SchemaProps{ Description: \"A selector to restrict the list of returned objects by their fields. Defaults to everything.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"watch\": { SchemaProps: spec.SchemaProps{ Description: \"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"allowWatchBookmarks\": { SchemaProps: spec.SchemaProps{ Description: \"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"resourceVersion\": { SchemaProps: spec.SchemaProps{ Description: \"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.nnDefaults to unset\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resourceVersionMatch\": { SchemaProps: spec.SchemaProps{ Description: \"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.nnDefaults to unset\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"timeoutSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"limit\": { SchemaProps: spec.SchemaProps{ Description: \"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.nnThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"continue\": { SchemaProps: spec.SchemaProps{ Description: \"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".nnThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_pkg_apis_meta_v1_ManagedFieldsEntry(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ManagedFieldsEntry is a workflow-id, a FieldSet and the group version of the resource that the fieldset applies to.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"manager\": { SchemaProps: spec.SchemaProps{ Description: \"Manager is an identifier of the workflow managing these fields.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"operation\": { SchemaProps: spec.SchemaProps{ Description: \"Operation is the type of operation which lead to this ManagedFieldsEntry being created. The only valid values for this field are 'Apply' and 'Update'.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the version of this resource that this field set applies to. The format is \"group/version\" just like the top-level APIVersion field. It is necessary to track the version of a field set because it cannot be automatically converted.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"time\": { SchemaProps: spec.SchemaProps{ Description: \"Time is the timestamp of when the ManagedFields entry was added. The timestamp will also be updated if a field is added, the manager changes any of the owned fields value or removes a field. The timestamp does not update when a field is removed from the entry because another manager took it over.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"fieldsType\": { SchemaProps: spec.SchemaProps{ Description: \"FieldsType is the discriminator for the different fields format and version. There is currently only one possible value: \"FieldsV1\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fieldsV1\": { SchemaProps: spec.SchemaProps{ Description: \"FieldsV1 holds the first JSON version format as described in the \"FieldsV1\" type.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.FieldsV1\"), }, }, \"subresource\": { SchemaProps: spec.SchemaProps{ Description: \"Subresource is the name of the subresource used to update that object, or empty string if the object was updated through the main resource. The value of this field is used to distinguish between managers, even if they share the same name. For example, a status update will be distinct from a regular update using the same manager name. Note that the APIVersion field is not related to the Subresource field and it always corresponds to the version of the main resource.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.FieldsV1\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_pkg_apis_meta_v1_MicroTime(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MicroTime is version of Time with microsecond level precision.\", Type:        metav1.MicroTime{}.OpenAPISchemaType(), Format:      metav1.MicroTime{}.OpenAPISchemaFormat(), }, }, } } func schema_pkg_apis_meta_v1_ObjectMeta(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ObjectMeta is metadata that all persisted resources must have, which includes all objects users must create.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name must be unique within a namespace. Is required when creating resources, although some resources may allow a client to request the generation of an appropriate name automatically. Name is primarily intended for creation idempotence and configuration definition. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/identifiers#names\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"generateName\": { SchemaProps: spec.SchemaProps{ Description: \"GenerateName is an optional prefix, used by the server, to generate a unique name ONLY IF the Name field has not been provided. If this field is used, the name returned to the client will be different than the name passed. This value will also be combined with a unique suffix. The provided value has the same validation rules as the Name field, and may be truncated by the length of the suffix required to make the value unique on the server.nnIf this field is specified and the generated name exists, the server will NOT return a 409 - instead, it will either return 201 Created or 500 with Reason ServerTimeout indicating a unique name could not be found in the time allotted, and the client should retry (optionally after the time indicated in the Retry-After header).nnApplied only if Name is not specified. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#idempotency\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"Namespace defines the space within which each name must be unique. An empty namespace is equivalent to the \"default\" namespace, but \"default\" is the canonical representation. Not all objects are required to be scoped to a namespace - the value of this field for those objects will be empty.nnMust be a DNS_LABEL. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/namespaces\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"selfLink\": { SchemaProps: spec.SchemaProps{ Description: \"Deprecated: selfLink is a legacy read-only field that is no longer populated by the system.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"uid\": { SchemaProps: spec.SchemaProps{ Description: \"UID is the unique in time and space value for this object. It is typically generated by the server on successful creation of a resource and is not allowed to change on PUT operations.nnPopulated by the system. Read-only. More info: http://kubernetes.io/docs/user-guide/identifiers#uids\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resourceVersion\": { SchemaProps: spec.SchemaProps{ Description: \"An opaque value that represents the internal version of this object that can be used by clients to determine when objects have changed. May be used for optimistic concurrency, change detection, and the watch operation on a resource or set of resources. Clients must treat these values as opaque and passed unmodified back to the server. They may only be valid for a particular resource or set of resources.nnPopulated by the system. Read-only. Value must be treated as opaque by clients and . More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"generation\": { SchemaProps: spec.SchemaProps{ Description: \"A sequence number representing a specific generation of the desired state. Populated by the system. Read-only.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"creationTimestamp\": { SchemaProps: spec.SchemaProps{ Description: \"CreationTimestamp is a timestamp representing the server time when this object was created. It is not guaranteed to be set in happens-before order across separate operations. Clients may not set this value. It is represented in RFC3339 form and is in UTC.nnPopulated by the system. Read-only. Null for lists. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"deletionTimestamp\": { SchemaProps: spec.SchemaProps{ Description: \"DeletionTimestamp is RFC 3339 date and time at which this resource will be deleted. This field is set by the server when a graceful deletion is requested by the user, and is not directly settable by a client. The resource is expected to be deleted (no longer visible from resource lists, and not reachable by name) after the time in this field, once the finalizers list is empty. As long as the finalizers list contains items, deletion is blocked. Once the deletionTimestamp is set, this value may not be unset or be set further into the future, although it may be shortened or the resource may be deleted prior to this time. For example, a user may request that a pod is deleted in 30 seconds. The Kubelet will react by sending a graceful termination signal to the containers in the pod. After that 30 seconds, the Kubelet will send a hard termination signal (SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after this timestamp, until an administrator or automated process can determine the resource is fully terminated. If not set, graceful deletion of the object has not been requested.nnPopulated by the system when a graceful deletion is requested. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"deletionGracePeriodSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"Number of seconds allowed for this object to gracefully terminate before it will be removed from the system. Only set when deletionTimestamp is also set. May only be shortened. Read-only.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"labels\": { SchemaProps: spec.SchemaProps{ Description: \"Map of string keys and values that can be used to organize and categorize (scope and select) objects. May match selectors of replication controllers and services. More info: http://kubernetes.io/docs/user-guide/labels\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"annotations\": { SchemaProps: spec.SchemaProps{ Description: \"Annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata. They are not queryable and should be preserved when modifying objects. More info: http://kubernetes.io/docs/user-guide/annotations\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"ownerReferences\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-merge-key\": \"uid\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"List of objects depended by this object. If ALL objects in the list have been deleted, this object will be garbage collected. If this object is managed by a controller, then an entry in this list will point to this controller, with the controller field set to true. There cannot be more than one managing controller.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.OwnerReference\"), }, }, }, }, }, \"finalizers\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-patch-strategy\": \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Must be empty before the object is deleted from the registry. Each entry is an identifier for the responsible component that will remove the entry from the list. If the deletionTimestamp of the object is non-nil, entries in this list can only be removed. Finalizers may be processed and removed in any order.  Order is NOT enforced because it introduces significant risk of stuck finalizers. finalizers is a shared field, any actor with permission can reorder it. If the finalizer list is processed in order, then this can lead to a situation in which the component responsible for the first finalizer in the list is waiting for a signal (field value, external system, or other) produced by a component responsible for a finalizer later in the list, resulting in a deadlock. Without enforced ordering finalizers are free to order amongst themselves and are not vulnerable to ordering changes in the list.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"clusterName\": { SchemaProps: spec.SchemaProps{ Description: \"The name of the cluster which the object belongs to. This is used to distinguish resources with same name and namespace in different clusters. This field is not set anywhere right now and apiserver is going to ignore it if set in create or update request.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"managedFields\": { SchemaProps: spec.SchemaProps{ Description: \"ManagedFields maps workflow-id and version to the set of fields that are managed by that workflow. This is mostly for internal housekeeping, and users typically shouldn't need to set or understand this field. A workflow can be the user's name, a controller's name, or the name of a specific apply path like \"ci-cd\". The set of fields is always in the version that the workflow used when modifying the object.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ManagedFieldsEntry\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ManagedFieldsEntry\", \"k8s.io/apimachinery/pkg/apis/meta/v1.OwnerReference\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_pkg_apis_meta_v1_OwnerReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"OwnerReference contains enough information to let you identify an owning object. An owning object must be in the same namespace as the dependent, or be cluster-scoped, so there is no namespace field.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"API version of the referent.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#names\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"uid\": { SchemaProps: spec.SchemaProps{ Description: \"UID of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#uids\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"controller\": { SchemaProps: spec.SchemaProps{ Description: \"If true, this reference points to the managing controller.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"blockOwnerDeletion\": { SchemaProps: spec.SchemaProps{ Description: \"If true, AND if the owner has the \"foregroundDeletion\" finalizer, then the owner cannot be deleted from the key-value store until this reference is removed. See https://kubernetes.io/docs/concepts/architecture/garbage-collection/#foreground-deletion for how the garbage collector interacts with this field and enforces the foreground deletion. Defaults to false. To set this field, a user needs \"delete\" permission of the owner, otherwise 422 (Unprocessable Entity) will be returned.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"apiVersion\", \"kind\", \"name\", \"uid\"}, }, VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-map-type\": \"atomic\", }, }, }, } } func schema_pkg_apis_meta_v1_PartialObjectMetadata(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PartialObjectMetadata is a generic representation of any object with ObjectMeta. It allows clients to get access to a particular ObjectMeta schema without knowing the details of the version.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"}, } } func schema_pkg_apis_meta_v1_PartialObjectMetadataList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PartialObjectMetadataList contains a list of objects containing only their metadata\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items contains each of the included items.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.PartialObjectMetadata\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/apimachinery/pkg/apis/meta/v1.PartialObjectMetadata\"}, } } func schema_pkg_apis_meta_v1_Patch(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Patch is provided to give a concrete name and type to the Kubernetes PATCH request body.\", Type:        []string{\"object\"}, }, }, } } func schema_pkg_apis_meta_v1_PatchOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PatchOptions may be provided when patching an API object. PatchOptions is meant to be a superset of UpdateOptions.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"dryRun\": { SchemaProps: spec.SchemaProps{ Description: \"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"force\": { SchemaProps: spec.SchemaProps{ Description: \"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"fieldManager\": { SchemaProps: spec.SchemaProps{ Description: \"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fieldValidation\": { SchemaProps: spec.SchemaProps{ Description: \"fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_pkg_apis_meta_v1_Preconditions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Preconditions must be fulfilled before an operation (update, delete, etc.) is carried out.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"uid\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies the target UID.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resourceVersion\": { SchemaProps: spec.SchemaProps{ Description: \"Specifies the target ResourceVersion\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_pkg_apis_meta_v1_RootPaths(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RootPaths lists the paths available at root. For example: \"/healthz\", \"/apis\".\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"paths\": { SchemaProps: spec.SchemaProps{ Description: \"paths are the paths available at root.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"paths\"}, }, }, } } func schema_pkg_apis_meta_v1_ServerAddressByClientCIDR(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ServerAddressByClientCIDR helps the client to determine the server address that they should use, depending on the clientCIDR that they match.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"clientCIDR\": { SchemaProps: spec.SchemaProps{ Description: \"The CIDR with which clients can match their IP to figure out the server address that they should use.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"serverAddress\": { SchemaProps: spec.SchemaProps{ Description: \"Address of this server, suitable for a client that matches the above CIDR. This can be a hostname, hostname:port, IP or IP:port.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"clientCIDR\", \"serverAddress\"}, }, }, } } func schema_pkg_apis_meta_v1_Status(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Status is a return value for calls that don't return other objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the operation. One of: \"Success\" or \"Failure\". More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"A human-readable description of the status of this operation.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"A machine-readable description of why this operation is in the \"Failure\" status. If this value is empty there is no information available. A Reason clarifies an HTTP status code but does not override it.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"details\": { SchemaProps: spec.SchemaProps{ Description: \"Extended data associated with the reason.  Each reason may define its own extended details. This field is optional and the data returned is not guaranteed to conform to any schema except that defined by the reason type.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.StatusDetails\"), }, }, \"code\": { SchemaProps: spec.SchemaProps{ Description: \"Suggested HTTP return code for this status, 0 if not set.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/apimachinery/pkg/apis/meta/v1.StatusDetails\"}, } } func schema_pkg_apis_meta_v1_StatusCause(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StatusCause provides more information about an api.Status failure, including cases when multiple errors are encountered.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"A machine-readable description of the cause of the error. If this value is empty there is no information available.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"A human-readable description of the cause of the error.  This field may be presented as-is to a reader.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"field\": { SchemaProps: spec.SchemaProps{ Description: \"The field of the resource that has caused this error, as named by its JSON serialization. May include dot and postfix notation for nested attributes. Arrays are zero-indexed.  Fields may appear more than once in an array of causes due to fields having multiple errors. Optional.nnExamples:n  \"name\" - the field \"name\" on the current resourcen  \"items[0].name\" - the field \"name\" on the first array entry in \"items\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_pkg_apis_meta_v1_StatusDetails(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StatusDetails is a set of additional properties that MAY be set by the server to provide additional information about a response. The Reason field of a Status object defines what attributes will be set. Clients must ignore fields that do not match the defined type of each attribute, and should assume that any attribute may be empty, invalid, or under defined.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"The name attribute of the resource associated with the status StatusReason (when there is a single name which can be described).\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"group\": { SchemaProps: spec.SchemaProps{ Description: \"The group attribute of the resource associated with the status StatusReason.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"The kind attribute of the resource associated with the status StatusReason. On some operations may differ from the requested resource Kind. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"uid\": { SchemaProps: spec.SchemaProps{ Description: \"UID of the resource. (when there is a single resource which can be described). More info: http://kubernetes.io/docs/user-guide/identifiers#uids\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"causes\": { SchemaProps: spec.SchemaProps{ Description: \"The Causes array includes more details associated with the StatusReason failure. Not all StatusReasons may provide detailed causes.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.StatusCause\"), }, }, }, }, }, \"retryAfterSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"If specified, the time in seconds before the operation should be retried. Some errors may indicate the client must take an alternate action - for those errors this field may indicate how long to wait before taking the alternate action.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.StatusCause\"}, } } func schema_pkg_apis_meta_v1_Table(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Table is a tabular representation of a set of API resources. The server transforms the object into a set of preferred columns for quickly reviewing the objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"columnDefinitions\": { SchemaProps: spec.SchemaProps{ Description: \"columnDefinitions describes each column in the returned items array. The number of cells per row will always match the number of column definitions.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.TableColumnDefinition\"), }, }, }, }, }, \"rows\": { SchemaProps: spec.SchemaProps{ Description: \"rows is the list of items in the table.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.TableRow\"), }, }, }, }, }, }, Required: []string{\"columnDefinitions\", \"rows\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/apimachinery/pkg/apis/meta/v1.TableColumnDefinition\", \"k8s.io/apimachinery/pkg/apis/meta/v1.TableRow\"}, } } func schema_pkg_apis_meta_v1_TableColumnDefinition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TableColumnDefinition contains information about a column returned in the Table.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is a human readable name for the column.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"type\": { SchemaProps: spec.SchemaProps{ Description: \"type is an OpenAPI type definition for this column, such as number, integer, string, or array. See https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#data-types for more.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"format\": { SchemaProps: spec.SchemaProps{ Description: \"format is an optional OpenAPI type modifier for this column. A format modifies the type and imposes additional rules, like date or time formatting for a string. The 'name' format is applied to the primary identifier column which has type 'string' to assist in clients identifying column is the resource name. See https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#data-types for more.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"description\": { SchemaProps: spec.SchemaProps{ Description: \"description is a human readable description of this column.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"priority\": { SchemaProps: spec.SchemaProps{ Description: \"priority is an integer defining the relative importance of this column compared to others. Lower numbers are considered higher priority. Columns that may be omitted in limited space scenarios should be given a higher priority.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"name\", \"type\", \"format\", \"description\", \"priority\"}, }, }, } } func schema_pkg_apis_meta_v1_TableOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TableOptions are used when a Table is requested by the caller.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"includeObject\": { SchemaProps: spec.SchemaProps{ Description: \"includeObject decides whether to include each object along with its columnar information. Specifying \"None\" will return no object, specifying \"Object\" will return the full object contents, and specifying \"Metadata\" (the default) will return the object's metadata in the PartialObjectMetadata kind in version v1beta1 of the meta.k8s.io API group.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_pkg_apis_meta_v1_TableRow(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TableRow is an individual row in a table.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"cells\": { SchemaProps: spec.SchemaProps{ Description: \"cells will be as wide as the column definitions array and may contain strings, numbers (float64 or int64), booleans, simple maps, lists, or null. See the type field of the column definition for a more detailed description.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Type:   []string{\"object\"}, Format: \"\", }, }, }, }, }, \"conditions\": { SchemaProps: spec.SchemaProps{ Description: \"conditions describe additional status of a row that are relevant for a human user. These conditions apply to the row, not to the object, and will be specific to table output. The only defined condition type is 'Completed', for a row that indicates a resource that has run to completion and can be given less visual priority.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.TableRowCondition\"), }, }, }, }, }, \"object\": { SchemaProps: spec.SchemaProps{ Description: \"This field contains the requested additional information about each object based on the includeObject policy when requesting the Table. If \"None\", this field is empty, if \"Object\" this will be the default serialization of the object for the current API version, and if \"Metadata\" (the default) will contain the object metadata. Check the returned kind and apiVersion of the object before parsing. The media type of the object will always match the enclosing list - if this as a JSON table, these will be JSON encoded objects.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/runtime.RawExtension\"), }, }, }, Required: []string{\"cells\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.TableRowCondition\", \"k8s.io/apimachinery/pkg/runtime.RawExtension\"}, } } func schema_pkg_apis_meta_v1_TableRowCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TableRowCondition allows a row to be marked with additional information.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type of row condition. The only defined value is 'Completed' indicating that the object this row represents has reached a completed state and may be given less visual priority than other rows. Clients are not required to honor any conditions but should be consistent where possible about handling the conditions.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status of the condition, one of True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"(brief) machine readable reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"Human readable message indicating details about last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, } } func schema_pkg_apis_meta_v1_Time(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Time is a wrapper around time.Time which supports correct marshaling to YAML and JSON.  Wrappers are provided for many of the factory methods that the time package offers.\", Type:        metav1.Time{}.OpenAPISchemaType(), Format:      metav1.Time{}.OpenAPISchemaFormat(), }, }, } } func schema_pkg_apis_meta_v1_Timestamp(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Timestamp is a struct that is equivalent to Time, but intended for protobuf marshalling/unmarshalling. It is generated into a serialization that matches Time. Do not use in Go structs.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"seconds\": { SchemaProps: spec.SchemaProps{ Description: \"Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z inclusive.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"nanos\": { SchemaProps: spec.SchemaProps{ Description: \"Non-negative fractions of a second at nanosecond resolution. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be from 0 to 999,999,999 inclusive. This field may be limited in precision depending on context.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"seconds\", \"nanos\"}, }, }, } } func schema_pkg_apis_meta_v1_TypeMeta(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TypeMeta describes an individual object in an API response or request with strings representing the type of the object and its API schema version. Structures that are versioned or persisted should inline TypeMeta.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_pkg_apis_meta_v1_UpdateOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"UpdateOptions may be provided when updating an API object. All fields in UpdateOptions should also be present in PatchOptions.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"dryRun\": { SchemaProps: spec.SchemaProps{ Description: \"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"fieldManager\": { SchemaProps: spec.SchemaProps{ Description: \"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"fieldValidation\": { SchemaProps: spec.SchemaProps{ Description: \"fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_pkg_apis_meta_v1_WatchEvent(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Event represents a single event to a watched resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, \"object\": { SchemaProps: spec.SchemaProps{ Description: \"Object is:n * If Type is Added or Modified: the new state of the object.n * If Type is Deleted: the state of the object immediately before deletion.n * If Type is Error: *Status is recommended; other types may make sensen   depending on context.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/runtime.RawExtension\"), }, }, }, Required: []string{\"type\", \"object\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/runtime.RawExtension\"}, } } func schema_pkg_apis_meta_v1beta1_PartialObjectMetadataList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PartialObjectMetadataList contains a list of objects containing only their metadata.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"items contains each of the included items.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.PartialObjectMetadata\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/apimachinery/pkg/apis/meta/v1.PartialObjectMetadata\"}, } } func schema_k8sio_apimachinery_pkg_runtime_RawExtension(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RawExtension is used to hold extensions in external versions.nnTo use this, make a field which has RawExtension as its type in your external, versioned struct, and Object in your internal struct. You also need to register your various plugin types.nn// Internal package: type MyAPIObject struct {ntruntime.TypeMeta `json:\",inline\"`ntMyPlugin runtime.Object `json:\"myPlugin\"`n} type PluginA struct {ntAOption string `json:\"aOption\"`n}nn// External package: type MyAPIObject struct {ntruntime.TypeMeta `json:\",inline\"`ntMyPlugin runtime.RawExtension `json:\"myPlugin\"`n} type PluginA struct {ntAOption string `json:\"aOption\"`n}nn// On the wire, the JSON will look something like this: {nt\"kind\":\"MyAPIObject\",nt\"apiVersion\":\"v1\",nt\"myPlugin\": {ntt\"kind\":\"PluginA\",ntt\"aOption\":\"foo\",nt},n}nnSo what happens? Decode first uses json or yaml to unmarshal the serialized data into your external MyAPIObject. That causes the raw JSON to be stored, but not unpacked. The next step is to copy (using pkg/conversion) into the internal struct. The runtime package's DefaultScheme has conversion functions installed which will unpack the JSON stored in RawExtension, turning it into the correct object type, and storing it in the Object. (TODO: In the case where the object is of an unknown type, a runtime.Unknown object will be created and stored.)\", Type:        []string{\"object\"}, }, }, } } func schema_k8sio_apimachinery_pkg_runtime_TypeMeta(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TypeMeta is shared by all top level objects. The proper way to use it is to inline it in your type, like this: type MyAwesomeAPIObject struct {n     runtime.TypeMeta    `json:\",inline\"`n     ... // other fieldsn} func (obj *MyAwesomeAPIObject) SetGroupVersionKind(gvk *metav1.GroupVersionKind) { metav1.UpdateTypeMeta(obj,gvk) }; GroupVersionKind() *GroupVersionKindnnTypeMeta is provided here for convenience. You may use it directly from this package or define your own with the same fields.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"apiVersion\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"kind\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, }, }, }, } } func schema_k8sio_apimachinery_pkg_runtime_Unknown(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Unknown allows api objects with unknown types to be passed-through. This can be used to deal with the API objects from a plug-in. Unknown objects still have functioning TypeMeta features-- kind, version, etc. metadata and field mutatation.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"apiVersion\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"kind\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"Raw\": { SchemaProps: spec.SchemaProps{ Description: \"Raw will hold the complete serialized object which couldn't be matched with a registered type. Most likely, nothing should be done with this except for passing it through the system.\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, \"ContentEncoding\": { SchemaProps: spec.SchemaProps{ Description: \"ContentEncoding is encoding used to encode 'Raw' data. Unspecified means no encoding.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ContentType\": { SchemaProps: spec.SchemaProps{ Description: \"ContentType  is serialization method used to serialize 'Raw'. Unspecified means ContentTypeJSON.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"Raw\", \"ContentEncoding\", \"ContentType\"}, }, }, } } func schema_apimachinery_pkg_util_intstr_IntOrString(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"IntOrString is a type that can hold an int32 or a string.  When used in JSON or YAML marshalling and unmarshalling, it produces or consumes the inner type.  This allows you to have, for example, a JSON field that can accept a name or number.\", Type:        intstr.IntOrString{}.OpenAPISchemaType(), Format:      intstr.IntOrString{}.OpenAPISchemaFormat(), }, }, } } func schema_k8sio_apimachinery_pkg_version_Info(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Info contains versioning information. how we'll want to distribute that information.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"major\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, \"minor\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, \"gitVersion\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, \"gitCommit\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, \"gitTreeState\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, \"buildDate\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, \"goVersion\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, \"compiler\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, \"platform\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, Required: []string{\"major\", \"minor\", \"gitVersion\", \"gitCommit\", \"gitTreeState\", \"buildDate\", \"goVersion\", \"compiler\", \"platform\"}, }, }, } } func schema_pkg_apis_audit_v1_Event(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Event captures all the information that can be included in an API audit log.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"level\": { SchemaProps: spec.SchemaProps{ Description: \"AuditLevel at which event was generated\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"auditID\": { SchemaProps: spec.SchemaProps{ Description: \"Unique audit ID, generated for each request.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"stage\": { SchemaProps: spec.SchemaProps{ Description: \"Stage of the request handling when this event instance was generated.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"requestURI\": { SchemaProps: spec.SchemaProps{ Description: \"RequestURI is the request URI as sent by the client to a server.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"verb\": { SchemaProps: spec.SchemaProps{ Description: \"Verb is the kubernetes verb associated with the request. For non-resource requests, this is the lower-cased HTTP method.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"user\": { SchemaProps: spec.SchemaProps{ Description: \"Authenticated user information.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authentication/v1.UserInfo\"), }, }, \"impersonatedUser\": { SchemaProps: spec.SchemaProps{ Description: \"Impersonated user information.\", Ref:         ref(\"k8s.io/api/authentication/v1.UserInfo\"), }, }, \"sourceIPs\": { SchemaProps: spec.SchemaProps{ Description: \"Source IPs, from where the request originated and intermediate proxies.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"userAgent\": { SchemaProps: spec.SchemaProps{ Description: \"UserAgent records the user agent string reported by the client. Note that the UserAgent is provided by the client, and must not be trusted.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"objectRef\": { SchemaProps: spec.SchemaProps{ Description: \"Object reference this request is targeted at. Does not apply for List-type requests, or non-resource requests.\", Ref:         ref(\"k8s.io/apiserver/pkg/apis/audit/v1.ObjectReference\"), }, }, \"responseStatus\": { SchemaProps: spec.SchemaProps{ Description: \"The response status, populated even when the ResponseObject is not a Status type. For successful responses, this will only include the Code and StatusSuccess. For non-status type error responses, this will be auto-populated with the error Message.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Status\"), }, }, \"requestObject\": { SchemaProps: spec.SchemaProps{ Description: \"API object from the request, in JSON format. The RequestObject is recorded as-is in the request (possibly re-encoded as JSON), prior to version conversion, defaulting, admission or merging. It is an external versioned object type, and may not be a valid object on its own. Omitted for non-resource requests.  Only logged at Request Level and higher.\", Ref:         ref(\"k8s.io/apimachinery/pkg/runtime.Unknown\"), }, }, \"responseObject\": { SchemaProps: spec.SchemaProps{ Description: \"API object returned in the response, in JSON. The ResponseObject is recorded after conversion to the external type, and serialized as JSON.  Omitted for non-resource requests.  Only logged at Response Level.\", Ref:         ref(\"k8s.io/apimachinery/pkg/runtime.Unknown\"), }, }, \"requestReceivedTimestamp\": { SchemaProps: spec.SchemaProps{ Description: \"Time the request reached the apiserver.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"), }, }, \"stageTimestamp\": { SchemaProps: spec.SchemaProps{ Description: \"Time the request reached current audit stage.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"), }, }, \"annotations\": { SchemaProps: spec.SchemaProps{ Description: \"Annotations is an unstructured key value map stored with an audit event that may be set by plugins invoked in the request serving chain, including authentication, authorization and admission plugins. Note that these annotations are for the audit event, and do not correspond to the metadata.annotations of the submitted object. Keys should uniquely identify the informing component to avoid name collisions (e.g. podsecuritypolicy.admission.k8s.io/policy). Values should be short. Annotations are included in the Metadata level.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"level\", \"auditID\", \"stage\", \"requestURI\", \"verb\", \"user\"}, }, }, Dependencies: []string{ \"k8s.io/api/authentication/v1.UserInfo\", \"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Status\", \"k8s.io/apimachinery/pkg/runtime.Unknown\", \"k8s.io/apiserver/pkg/apis/audit/v1.ObjectReference\"}, } } func schema_pkg_apis_audit_v1_EventList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EventList is a list of audit Events.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiserver/pkg/apis/audit/v1.Event\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/apiserver/pkg/apis/audit/v1.Event\"}, } } func schema_pkg_apis_audit_v1_GroupResources(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"GroupResources represents resource kinds in an API group.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"group\": { SchemaProps: spec.SchemaProps{ Description: \"Group is the name of the API group that contains the resources. The empty string represents the core API group.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"Resources is a list of resources this rule applies to.nnFor example: 'pods' matches pods. 'pods/log' matches the log subresource of pods. '*' matches all resources and their subresources. 'pods/*' matches all subresources of pods. '*/scale' matches all scale subresources.nnIf wildcard is present, the validation rule will ensure resources do not overlap with each other.nnAn empty list implies all resources and subresources in this API groups apply.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resourceNames\": { SchemaProps: spec.SchemaProps{ Description: \"ResourceNames is a list of resource instance names that the policy matches. Using this field requires Resources to be specified. An empty list implies that every instance of the resource is matched.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, } } func schema_pkg_apis_audit_v1_ObjectReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ObjectReference contains enough information to let you inspect or modify the referred object.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"resource\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"namespace\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"uid\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"apiGroup\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroup is the name of the API group that contains the referred object. The empty string represents the core API group.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion is the version of the API group that contains the referred object.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resourceVersion\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"subresource\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, }, }, }, } } func schema_pkg_apis_audit_v1_Policy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Policy defines the configuration of audit logging, and the rules for how different request categories are logged.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"ObjectMeta is included for interoperability with API infrastructure.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"rules\": { SchemaProps: spec.SchemaProps{ Description: \"Rules specify the audit Level a request should be recorded at. A request may match multiple rules, in which case the FIRST matching rule is used. The default audit level is None, but can be overridden by a catch-all rule at the end of the list. PolicyRules are strictly ordered.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiserver/pkg/apis/audit/v1.PolicyRule\"), }, }, }, }, }, \"omitStages\": { SchemaProps: spec.SchemaProps{ Description: \"OmitStages is a list of stages for which no events are created. Note that this can also be specified per rule in which case the union of both are omitted.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"omitManagedFields\": { SchemaProps: spec.SchemaProps{ Description: \"OmitManagedFields indicates whether to omit the managed fields of the request and response bodies from being written to the API audit log. This is used as a global default - a value of 'true' will omit the managed fileds, otherwise the managed fields will be included in the API audit log. Note that this can also be specified per rule in which case the value specified in a rule will override the global default.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"rules\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\", \"k8s.io/apiserver/pkg/apis/audit/v1.PolicyRule\"}, } } func schema_pkg_apis_audit_v1_PolicyList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PolicyList is a list of audit Policies.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiserver/pkg/apis/audit/v1.Policy\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/apiserver/pkg/apis/audit/v1.Policy\"}, } } func schema_pkg_apis_audit_v1_PolicyRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PolicyRule maps requests based off metadata to an audit Level. Requests must match the rules of every field (an intersection of rules).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"level\": { SchemaProps: spec.SchemaProps{ Description: \"The Level that requests matching this rule are recorded at.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"users\": { SchemaProps: spec.SchemaProps{ Description: \"The users (by authenticated user name) this rule applies to. An empty list implies every user.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"userGroups\": { SchemaProps: spec.SchemaProps{ Description: \"The user groups this rule applies to. A user is considered matching if it is a member of any of the UserGroups. An empty list implies every user group.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"verbs\": { SchemaProps: spec.SchemaProps{ Description: \"The verbs that match this rule. An empty list implies every verb.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"Resources that this rule matches. An empty list implies all kinds in all API groups.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiserver/pkg/apis/audit/v1.GroupResources\"), }, }, }, }, }, \"namespaces\": { SchemaProps: spec.SchemaProps{ Description: \"Namespaces that this rule matches. The empty string \"\" matches non-namespaced resources. An empty list implies every namespace.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"nonResourceURLs\": { SchemaProps: spec.SchemaProps{ Description: \"NonResourceURLs is a set of URL paths that should be audited. *s are allowed, but only as the full, final step in the path. Examples:n \"/metrics\" - Log requests for apiserver metricsn \"/healthz*\" - Log all health checks\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"omitStages\": { SchemaProps: spec.SchemaProps{ Description: \"OmitStages is a list of stages for which no events are created. Note that this can also be specified policy wide in which case the union of both are omitted. An empty list means no restrictions will apply.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"omitManagedFields\": { SchemaProps: spec.SchemaProps{ Description: \"OmitManagedFields indicates whether to omit the managed fields of the request and response bodies from being written to the API audit log. - a value of 'true' will drop the managed fields from the API audit log - a value of 'false' indicates that the managed fileds should be includedn  in the API audit lognNote that the value, if specified, in this rule will override the global default If a value is not specified then the global default specified in Policy.OmitManagedFields will stand.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"level\"}, }, }, Dependencies: []string{ \"k8s.io/apiserver/pkg/apis/audit/v1.GroupResources\"}, } } func schema_pkg_apis_audit_v1alpha1_Event(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED - This group version of Event is deprecated by audit.k8s.io/v1/Event. See the release notes for more information. Event captures all the information that can be included in an API audit log.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"ObjectMeta is included for interoperability with API infrastructure.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"level\": { SchemaProps: spec.SchemaProps{ Description: \"AuditLevel at which event was generated\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"timestamp\": { SchemaProps: spec.SchemaProps{ Description: \"Time the request reached the apiserver.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"auditID\": { SchemaProps: spec.SchemaProps{ Description: \"Unique audit ID, generated for each request.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"stage\": { SchemaProps: spec.SchemaProps{ Description: \"Stage of the request handling when this event instance was generated.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"requestURI\": { SchemaProps: spec.SchemaProps{ Description: \"RequestURI is the request URI as sent by the client to a server.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"verb\": { SchemaProps: spec.SchemaProps{ Description: \"Verb is the kubernetes verb associated with the request. For non-resource requests, this is the lower-cased HTTP method.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"user\": { SchemaProps: spec.SchemaProps{ Description: \"Authenticated user information.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authentication/v1.UserInfo\"), }, }, \"impersonatedUser\": { SchemaProps: spec.SchemaProps{ Description: \"Impersonated user information.\", Ref:         ref(\"k8s.io/api/authentication/v1.UserInfo\"), }, }, \"sourceIPs\": { SchemaProps: spec.SchemaProps{ Description: \"Source IPs, from where the request originated and intermediate proxies.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"userAgent\": { SchemaProps: spec.SchemaProps{ Description: \"UserAgent records the user agent string reported by the client. Note that the UserAgent is provided by the client, and must not be trusted.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"objectRef\": { SchemaProps: spec.SchemaProps{ Description: \"Object reference this request is targeted at. Does not apply for List-type requests, or non-resource requests.\", Ref:         ref(\"k8s.io/apiserver/pkg/apis/audit/v1alpha1.ObjectReference\"), }, }, \"responseStatus\": { SchemaProps: spec.SchemaProps{ Description: \"The response status, populated even when the ResponseObject is not a Status type. For successful responses, this will only include the Code and StatusSuccess. For non-status type error responses, this will be auto-populated with the error Message.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Status\"), }, }, \"requestObject\": { SchemaProps: spec.SchemaProps{ Description: \"API object from the request, in JSON format. The RequestObject is recorded as-is in the request (possibly re-encoded as JSON), prior to version conversion, defaulting, admission or merging. It is an external versioned object type, and may not be a valid object on its own. Omitted for non-resource requests.  Only logged at Request Level and higher.\", Ref:         ref(\"k8s.io/apimachinery/pkg/runtime.Unknown\"), }, }, \"responseObject\": { SchemaProps: spec.SchemaProps{ Description: \"API object returned in the response, in JSON. The ResponseObject is recorded after conversion to the external type, and serialized as JSON.  Omitted for non-resource requests.  Only logged at Response Level.\", Ref:         ref(\"k8s.io/apimachinery/pkg/runtime.Unknown\"), }, }, \"requestReceivedTimestamp\": { SchemaProps: spec.SchemaProps{ Description: \"Time the request reached the apiserver.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"), }, }, \"stageTimestamp\": { SchemaProps: spec.SchemaProps{ Description: \"Time the request reached current audit stage.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"), }, }, \"annotations\": { SchemaProps: spec.SchemaProps{ Description: \"Annotations is an unstructured key value map stored with an audit event that may be set by plugins invoked in the request serving chain, including authentication, authorization and admission plugins. Note that these annotations are for the audit event, and do not correspond to the metadata.annotations of the submitted object. Keys should uniquely identify the informing component to avoid name collisions (e.g. podsecuritypolicy.admission.k8s.io/policy). Values should be short. Annotations are included in the Metadata level.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"level\", \"timestamp\", \"auditID\", \"stage\", \"requestURI\", \"verb\", \"user\"}, }, }, Dependencies: []string{ \"k8s.io/api/authentication/v1.UserInfo\", \"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Status\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\", \"k8s.io/apimachinery/pkg/runtime.Unknown\", \"k8s.io/apiserver/pkg/apis/audit/v1alpha1.ObjectReference\"}, } } func schema_pkg_apis_audit_v1alpha1_EventList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EventList is a list of audit Events.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiserver/pkg/apis/audit/v1alpha1.Event\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/apiserver/pkg/apis/audit/v1alpha1.Event\"}, } } func schema_pkg_apis_audit_v1alpha1_GroupResources(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"GroupResources represents resource kinds in an API group.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"group\": { SchemaProps: spec.SchemaProps{ Description: \"Group is the name of the API group that contains the resources. The empty string represents the core API group.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"Resources is a list of resources this rule applies to.nnFor example: 'pods' matches pods. 'pods/log' matches the log subresource of pods. '*' matches all resources and their subresources. 'pods/*' matches all subresources of pods. '*/scale' matches all scale subresources.nnIf wildcard is present, the validation rule will ensure resources do not overlap with each other.nnAn empty list implies all resources and subresources in this API groups apply.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resourceNames\": { SchemaProps: spec.SchemaProps{ Description: \"ResourceNames is a list of resource instance names that the policy matches. Using this field requires Resources to be specified. An empty list implies that every instance of the resource is matched.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, } } func schema_pkg_apis_audit_v1alpha1_ObjectReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ObjectReference contains enough information to let you inspect or modify the referred object.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"resource\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"namespace\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"uid\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"resourceVersion\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"subresource\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, }, }, }, } } func schema_pkg_apis_audit_v1alpha1_Policy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED - This group version of Policy is deprecated by audit.k8s.io/v1/Policy. See the release notes for more information. Policy defines the configuration of audit logging, and the rules for how different request categories are logged.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"ObjectMeta is included for interoperability with API infrastructure.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"rules\": { SchemaProps: spec.SchemaProps{ Description: \"Rules specify the audit Level a request should be recorded at. A request may match multiple rules, in which case the FIRST matching rule is used. The default audit level is None, but can be overridden by a catch-all rule at the end of the list. PolicyRules are strictly ordered.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiserver/pkg/apis/audit/v1alpha1.PolicyRule\"), }, }, }, }, }, \"omitStages\": { SchemaProps: spec.SchemaProps{ Description: \"OmitStages is a list of stages for which no events are created. Note that this can also be specified per rule in which case the union of both are omitted.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"omitManagedFields\": { SchemaProps: spec.SchemaProps{ Description: \"OmitManagedFields indicates whether to omit the managed fields of the request and response bodies from being written to the API audit log. This is used as a global default - a value of 'true' will omit the managed fileds, otherwise the managed fields will be included in the API audit log. Note that this can also be specified per rule in which case the value specified in a rule will override the global default.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"rules\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\", \"k8s.io/apiserver/pkg/apis/audit/v1alpha1.PolicyRule\"}, } } func schema_pkg_apis_audit_v1alpha1_PolicyList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PolicyList is a list of audit Policies.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiserver/pkg/apis/audit/v1alpha1.Policy\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/apiserver/pkg/apis/audit/v1alpha1.Policy\"}, } } func schema_pkg_apis_audit_v1alpha1_PolicyRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PolicyRule maps requests based off metadata to an audit Level. Requests must match the rules of every field (an intersection of rules).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"level\": { SchemaProps: spec.SchemaProps{ Description: \"The Level that requests matching this rule are recorded at.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"users\": { SchemaProps: spec.SchemaProps{ Description: \"The users (by authenticated user name) this rule applies to. An empty list implies every user.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"userGroups\": { SchemaProps: spec.SchemaProps{ Description: \"The user groups this rule applies to. A user is considered matching if it is a member of any of the UserGroups. An empty list implies every user group.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"verbs\": { SchemaProps: spec.SchemaProps{ Description: \"The verbs that match this rule. An empty list implies every verb.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"Resources that this rule matches. An empty list implies all kinds in all API groups.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiserver/pkg/apis/audit/v1alpha1.GroupResources\"), }, }, }, }, }, \"namespaces\": { SchemaProps: spec.SchemaProps{ Description: \"Namespaces that this rule matches. The empty string \"\" matches non-namespaced resources. An empty list implies every namespace.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"nonResourceURLs\": { SchemaProps: spec.SchemaProps{ Description: \"NonResourceURLs is a set of URL paths that should be audited. *s are allowed, but only as the full, final step in the path. Examples:n \"/metrics\" - Log requests for apiserver metricsn \"/healthz*\" - Log all health checks\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"omitStages\": { SchemaProps: spec.SchemaProps{ Description: \"OmitStages is a list of stages for which no events are created. Note that this can also be specified policy wide in which case the union of both are omitted. An empty list means no restrictions will apply.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"omitManagedFields\": { SchemaProps: spec.SchemaProps{ Description: \"OmitManagedFields indicates whether to omit the managed fields of the request and response bodies from being written to the API audit log. - a value of 'true' will drop the managed fields from the API audit log - a value of 'false' indicates that the managed fileds should be includedn  in the API audit lognNote that the value, if specified, in this rule will override the global default If a value is not specified then the global default specified in Policy.OmitManagedFields will stand.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"level\"}, }, }, Dependencies: []string{ \"k8s.io/apiserver/pkg/apis/audit/v1alpha1.GroupResources\"}, } } func schema_pkg_apis_audit_v1beta1_Event(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED - This group version of Event is deprecated by audit.k8s.io/v1/Event. See the release notes for more information. Event captures all the information that can be included in an API audit log.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"ObjectMeta is included for interoperability with API infrastructure. DEPRECATED: Use StageTimestamp which supports micro second instead of ObjectMeta.CreateTimestamp and the rest of the object is not used\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"level\": { SchemaProps: spec.SchemaProps{ Description: \"AuditLevel at which event was generated\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"timestamp\": { SchemaProps: spec.SchemaProps{ Description: \"Time the request reached the apiserver. DEPRECATED: Use RequestReceivedTimestamp which supports micro second instead.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"auditID\": { SchemaProps: spec.SchemaProps{ Description: \"Unique audit ID, generated for each request.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"stage\": { SchemaProps: spec.SchemaProps{ Description: \"Stage of the request handling when this event instance was generated.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"requestURI\": { SchemaProps: spec.SchemaProps{ Description: \"RequestURI is the request URI as sent by the client to a server.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"verb\": { SchemaProps: spec.SchemaProps{ Description: \"Verb is the kubernetes verb associated with the request. For non-resource requests, this is the lower-cased HTTP method.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"user\": { SchemaProps: spec.SchemaProps{ Description: \"Authenticated user information.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/authentication/v1.UserInfo\"), }, }, \"impersonatedUser\": { SchemaProps: spec.SchemaProps{ Description: \"Impersonated user information.\", Ref:         ref(\"k8s.io/api/authentication/v1.UserInfo\"), }, }, \"sourceIPs\": { SchemaProps: spec.SchemaProps{ Description: \"Source IPs, from where the request originated and intermediate proxies.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"userAgent\": { SchemaProps: spec.SchemaProps{ Description: \"UserAgent records the user agent string reported by the client. Note that the UserAgent is provided by the client, and must not be trusted.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"objectRef\": { SchemaProps: spec.SchemaProps{ Description: \"Object reference this request is targeted at. Does not apply for List-type requests, or non-resource requests.\", Ref:         ref(\"k8s.io/apiserver/pkg/apis/audit/v1beta1.ObjectReference\"), }, }, \"responseStatus\": { SchemaProps: spec.SchemaProps{ Description: \"The response status, populated even when the ResponseObject is not a Status type. For successful responses, this will only include the Code and StatusSuccess. For non-status type error responses, this will be auto-populated with the error Message.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Status\"), }, }, \"requestObject\": { SchemaProps: spec.SchemaProps{ Description: \"API object from the request, in JSON format. The RequestObject is recorded as-is in the request (possibly re-encoded as JSON), prior to version conversion, defaulting, admission or merging. It is an external versioned object type, and may not be a valid object on its own. Omitted for non-resource requests.  Only logged at Request Level and higher.\", Ref:         ref(\"k8s.io/apimachinery/pkg/runtime.Unknown\"), }, }, \"responseObject\": { SchemaProps: spec.SchemaProps{ Description: \"API object returned in the response, in JSON. The ResponseObject is recorded after conversion to the external type, and serialized as JSON.  Omitted for non-resource requests.  Only logged at Response Level.\", Ref:         ref(\"k8s.io/apimachinery/pkg/runtime.Unknown\"), }, }, \"requestReceivedTimestamp\": { SchemaProps: spec.SchemaProps{ Description: \"Time the request reached the apiserver.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"), }, }, \"stageTimestamp\": { SchemaProps: spec.SchemaProps{ Description: \"Time the request reached current audit stage.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\"), }, }, \"annotations\": { SchemaProps: spec.SchemaProps{ Description: \"Annotations is an unstructured key value map stored with an audit event that may be set by plugins invoked in the request serving chain, including authentication, authorization and admission plugins. Note that these annotations are for the audit event, and do not correspond to the metadata.annotations of the submitted object. Keys should uniquely identify the informing component to avoid name collisions (e.g. podsecuritypolicy.admission.k8s.io/policy). Values should be short. Annotations are included in the Metadata level.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, Required: []string{\"level\", \"timestamp\", \"auditID\", \"stage\", \"requestURI\", \"verb\", \"user\"}, }, }, Dependencies: []string{ \"k8s.io/api/authentication/v1.UserInfo\", \"k8s.io/apimachinery/pkg/apis/meta/v1.MicroTime\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Status\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\", \"k8s.io/apimachinery/pkg/runtime.Unknown\", \"k8s.io/apiserver/pkg/apis/audit/v1beta1.ObjectReference\"}, } } func schema_pkg_apis_audit_v1beta1_EventList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EventList is a list of audit Events.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiserver/pkg/apis/audit/v1beta1.Event\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/apiserver/pkg/apis/audit/v1beta1.Event\"}, } } func schema_pkg_apis_audit_v1beta1_GroupResources(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"GroupResources represents resource kinds in an API group.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"group\": { SchemaProps: spec.SchemaProps{ Description: \"Group is the name of the API group that contains the resources. The empty string represents the core API group.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"Resources is a list of resources this rule applies to.nnFor example: 'pods' matches pods. 'pods/log' matches the log subresource of pods. '*' matches all resources and their subresources. 'pods/*' matches all subresources of pods. '*/scale' matches all scale subresources.nnIf wildcard is present, the validation rule will ensure resources do not overlap with each other.nnAn empty list implies all resources and subresources in this API groups apply.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resourceNames\": { SchemaProps: spec.SchemaProps{ Description: \"ResourceNames is a list of resource instance names that the policy matches. Using this field requires Resources to be specified. An empty list implies that every instance of the resource is matched.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, } } func schema_pkg_apis_audit_v1beta1_ObjectReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ObjectReference contains enough information to let you inspect or modify the referred object.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"resource\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"namespace\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"uid\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"apiGroup\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroup is the name of the API group that contains the referred object. The empty string represents the core API group.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion is the version of the API group that contains the referred object.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resourceVersion\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, \"subresource\": { SchemaProps: spec.SchemaProps{ Type:   []string{\"string\"}, Format: \"\", }, }, }, }, }, } } func schema_pkg_apis_audit_v1beta1_Policy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED - This group version of Policy is deprecated by audit.k8s.io/v1/Policy. See the release notes for more information. Policy defines the configuration of audit logging, and the rules for how different request categories are logged.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"ObjectMeta is included for interoperability with API infrastructure.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"rules\": { SchemaProps: spec.SchemaProps{ Description: \"Rules specify the audit Level a request should be recorded at. A request may match multiple rules, in which case the FIRST matching rule is used. The default audit level is None, but can be overridden by a catch-all rule at the end of the list. PolicyRules are strictly ordered.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiserver/pkg/apis/audit/v1beta1.PolicyRule\"), }, }, }, }, }, \"omitStages\": { SchemaProps: spec.SchemaProps{ Description: \"OmitStages is a list of stages for which no events are created. Note that this can also be specified per rule in which case the union of both are omitted.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"omitManagedFields\": { SchemaProps: spec.SchemaProps{ Description: \"OmitManagedFields indicates whether to omit the managed fields of the request and response bodies from being written to the API audit log. This is used as a global default - a value of 'true' will omit the managed fileds, otherwise the managed fields will be included in the API audit log. Note that this can also be specified per rule in which case the value specified in a rule will override the global default.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"rules\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\", \"k8s.io/apiserver/pkg/apis/audit/v1beta1.PolicyRule\"}, } } func schema_pkg_apis_audit_v1beta1_PolicyList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PolicyList is a list of audit Policies.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiserver/pkg/apis/audit/v1beta1.Policy\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/apiserver/pkg/apis/audit/v1beta1.Policy\"}, } } func schema_pkg_apis_audit_v1beta1_PolicyRule(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PolicyRule maps requests based off metadata to an audit Level. Requests must match the rules of every field (an intersection of rules).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"level\": { SchemaProps: spec.SchemaProps{ Description: \"The Level that requests matching this rule are recorded at.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"users\": { SchemaProps: spec.SchemaProps{ Description: \"The users (by authenticated user name) this rule applies to. An empty list implies every user.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"userGroups\": { SchemaProps: spec.SchemaProps{ Description: \"The user groups this rule applies to. A user is considered matching if it is a member of any of the UserGroups. An empty list implies every user group.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"verbs\": { SchemaProps: spec.SchemaProps{ Description: \"The verbs that match this rule. An empty list implies every verb.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"resources\": { SchemaProps: spec.SchemaProps{ Description: \"Resources that this rule matches. An empty list implies all kinds in all API groups.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apiserver/pkg/apis/audit/v1beta1.GroupResources\"), }, }, }, }, }, \"namespaces\": { SchemaProps: spec.SchemaProps{ Description: \"Namespaces that this rule matches. The empty string \"\" matches non-namespaced resources. An empty list implies every namespace.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"nonResourceURLs\": { SchemaProps: spec.SchemaProps{ Description: \"NonResourceURLs is a set of URL paths that should be audited. *s are allowed, but only as the full, final step in the path. Examples:n \"/metrics\" - Log requests for apiserver metricsn \"/healthz*\" - Log all health checks\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"omitStages\": { SchemaProps: spec.SchemaProps{ Description: \"OmitStages is a list of stages for which no events are created. Note that this can also be specified policy wide in which case the union of both are omitted. An empty list means no restrictions will apply.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"omitManagedFields\": { SchemaProps: spec.SchemaProps{ Description: \"OmitManagedFields indicates whether to omit the managed fields of the request and response bodies from being written to the API audit log. - a value of 'true' will drop the managed fields from the API audit log - a value of 'false' indicates that the managed fileds should be includedn  in the API audit lognNote that the value, if specified, in this rule will override the global default If a value is not specified then the global default specified in Policy.OmitManagedFields will stand.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"level\"}, }, }, Dependencies: []string{ \"k8s.io/apiserver/pkg/apis/audit/v1beta1.GroupResources\"}, } } func schema_pkg_apis_clientauthentication_v1_Cluster(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Cluster contains information to allow an exec plugin to communicate with the kubernetes cluster being authenticated to.nnTo ensure that this struct contains everything someone would need to communicate with a kubernetes cluster (just like they would via a kubeconfig), the fields should shadow \"k8s.io/client-go/tools/clientcmd/api/v1\".Cluster, with the exception of CertificateAuthority, since CA data will always be passed to the plugin as bytes.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"server\": { SchemaProps: spec.SchemaProps{ Description: \"Server is the address of the kubernetes cluster (https://hostname:port).\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"tls-server-name\": { SchemaProps: spec.SchemaProps{ Description: \"TLSServerName 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.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"insecure-skip-tls-verify\": { SchemaProps: spec.SchemaProps{ Description: \"InsecureSkipTLSVerify skips the validity check for the server's certificate. This will make your HTTPS connections insecure.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"certificate-authority-data\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"CAData contains PEM-encoded certificate authority certificates. If empty, system roots should be used.\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, \"proxy-url\": { SchemaProps: spec.SchemaProps{ Description: \"ProxyURL is the URL to the proxy to be used for all requests to this cluster.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"config\": { SchemaProps: spec.SchemaProps{ Description: \"Config holds additional config data that is specific to the exec plugin with regards to the cluster being authenticated to.nnThis data is sourced from the clientcmd Cluster object's extensions[client.authentication.k8s.io/exec] field:nnclusters: - name: my-clustern  cluster:n    ...n    extensions:n    - name: client.authentication.k8s.io/exec  # reserved extension name for per cluster exec confign      extension:n        audience: 06e3fbd18de8  # arbitrary confignnIn some environments, the user config may be exactly the same across many clusters (i.e. call this exec plugin) minus some details that are specific to each cluster such as the audience.  This field allows the per cluster config to be directly specified with the cluster info.  Using this field to store secret data is not recommended as one of the prime benefits of exec plugins is that no secrets need to be stored directly in the kubeconfig.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/runtime.RawExtension\"), }, }, }, Required: []string{\"server\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/runtime.RawExtension\"}, } } func schema_pkg_apis_clientauthentication_v1_ExecCredential(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExecCredential is used by exec-based plugins to communicate credentials to HTTP transports.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec holds information passed to the plugin by the transport.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/client-go/pkg/apis/clientauthentication/v1.ExecCredentialSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is filled in by the plugin and holds the credentials that the transport should use to contact the API.\", Ref:         ref(\"k8s.io/client-go/pkg/apis/clientauthentication/v1.ExecCredentialStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/client-go/pkg/apis/clientauthentication/v1.ExecCredentialSpec\", \"k8s.io/client-go/pkg/apis/clientauthentication/v1.ExecCredentialStatus\"}, } } func schema_pkg_apis_clientauthentication_v1_ExecCredentialSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExecCredentialSpec holds request and runtime specific information provided by the transport.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"cluster\": { SchemaProps: spec.SchemaProps{ Description: \"Cluster contains information to allow an exec plugin to communicate with the kubernetes cluster being authenticated to. Note that Cluster is non-nil only when provideClusterInfo is set to true in the exec provider config (i.e., ExecConfig.ProvideClusterInfo).\", Ref:         ref(\"k8s.io/client-go/pkg/apis/clientauthentication/v1.Cluster\"), }, }, \"interactive\": { SchemaProps: spec.SchemaProps{ Description: \"Interactive declares whether stdin has been passed to this exec plugin.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"interactive\"}, }, }, Dependencies: []string{ \"k8s.io/client-go/pkg/apis/clientauthentication/v1.Cluster\"}, } } func schema_pkg_apis_clientauthentication_v1_ExecCredentialStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExecCredentialStatus holds credentials for the transport to use.nnToken and ClientKeyData are sensitive fields. This data should only be transmitted in-memory between client and exec plugin process. Exec plugin itself should at least be protected via file permissions.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"expirationTimestamp\": { SchemaProps: spec.SchemaProps{ Description: \"ExpirationTimestamp indicates a time when the provided credentials expire.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"token\": { SchemaProps: spec.SchemaProps{ Description: \"Token is a bearer token used by the client for request authentication.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"clientCertificateData\": { SchemaProps: spec.SchemaProps{ Description: \"PEM-encoded client TLS certificates (including intermediates, if any).\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"clientKeyData\": { SchemaProps: spec.SchemaProps{ Description: \"PEM-encoded private key for the above certificate.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_pkg_apis_clientauthentication_v1alpha1_ExecCredential(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExecCredential is used by exec-based plugins to communicate credentials to HTTP transports.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec holds information passed to the plugin by the transport. This contains request and runtime specific information, such as if the session is interactive.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/client-go/pkg/apis/clientauthentication/v1alpha1.ExecCredentialSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is filled in by the plugin and holds the credentials that the transport should use to contact the API.\", Ref:         ref(\"k8s.io/client-go/pkg/apis/clientauthentication/v1alpha1.ExecCredentialStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/client-go/pkg/apis/clientauthentication/v1alpha1.ExecCredentialSpec\", \"k8s.io/client-go/pkg/apis/clientauthentication/v1alpha1.ExecCredentialStatus\"}, } } func schema_pkg_apis_clientauthentication_v1alpha1_ExecCredentialSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExecCredentialSpec holds request and runtime specific information provided by the transport.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"response\": { SchemaProps: spec.SchemaProps{ Description: \"Response is populated when the transport encounters HTTP status codes, such as 401, suggesting previous credentials were invalid.\", Ref:         ref(\"k8s.io/client-go/pkg/apis/clientauthentication/v1alpha1.Response\"), }, }, \"interactive\": { SchemaProps: spec.SchemaProps{ Description: \"Interactive is true when the transport detects the command is being called from an interactive prompt.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/client-go/pkg/apis/clientauthentication/v1alpha1.Response\"}, } } func schema_pkg_apis_clientauthentication_v1alpha1_ExecCredentialStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExecCredentialStatus holds credentials for the transport to use.nnToken and ClientKeyData are sensitive fields. This data should only be transmitted in-memory between client and exec plugin process. Exec plugin itself should at least be protected via file permissions.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"expirationTimestamp\": { SchemaProps: spec.SchemaProps{ Description: \"ExpirationTimestamp indicates a time when the provided credentials expire.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"token\": { SchemaProps: spec.SchemaProps{ Description: \"Token is a bearer token used by the client for request authentication.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"clientCertificateData\": { SchemaProps: spec.SchemaProps{ Description: \"PEM-encoded client TLS certificates (including intermediates, if any).\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"clientKeyData\": { SchemaProps: spec.SchemaProps{ Description: \"PEM-encoded private key for the above certificate.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_pkg_apis_clientauthentication_v1alpha1_Response(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Response defines metadata about a failed request, including HTTP status code and response headers.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"header\": { SchemaProps: spec.SchemaProps{ Description: \"Header holds HTTP headers returned by the server.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, \"code\": { SchemaProps: spec.SchemaProps{ Description: \"Code is the HTTP status code returned by the server.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_pkg_apis_clientauthentication_v1beta1_Cluster(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Cluster contains information to allow an exec plugin to communicate with the kubernetes cluster being authenticated to.nnTo ensure that this struct contains everything someone would need to communicate with a kubernetes cluster (just like they would via a kubeconfig), the fields should shadow \"k8s.io/client-go/tools/clientcmd/api/v1\".Cluster, with the exception of CertificateAuthority, since CA data will always be passed to the plugin as bytes.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"server\": { SchemaProps: spec.SchemaProps{ Description: \"Server is the address of the kubernetes cluster (https://hostname:port).\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"tls-server-name\": { SchemaProps: spec.SchemaProps{ Description: \"TLSServerName 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.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"insecure-skip-tls-verify\": { SchemaProps: spec.SchemaProps{ Description: \"InsecureSkipTLSVerify skips the validity check for the server's certificate. This will make your HTTPS connections insecure.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"certificate-authority-data\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"CAData contains PEM-encoded certificate authority certificates. If empty, system roots should be used.\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, \"proxy-url\": { SchemaProps: spec.SchemaProps{ Description: \"ProxyURL is the URL to the proxy to be used for all requests to this cluster.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"config\": { SchemaProps: spec.SchemaProps{ Description: \"Config holds additional config data that is specific to the exec plugin with regards to the cluster being authenticated to.nnThis data is sourced from the clientcmd Cluster object's extensions[client.authentication.k8s.io/exec] field:nnclusters: - name: my-clustern  cluster:n    ...n    extensions:n    - name: client.authentication.k8s.io/exec  # reserved extension name for per cluster exec confign      extension:n        audience: 06e3fbd18de8  # arbitrary confignnIn some environments, the user config may be exactly the same across many clusters (i.e. call this exec plugin) minus some details that are specific to each cluster such as the audience.  This field allows the per cluster config to be directly specified with the cluster info.  Using this field to store secret data is not recommended as one of the prime benefits of exec plugins is that no secrets need to be stored directly in the kubeconfig.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/runtime.RawExtension\"), }, }, }, Required: []string{\"server\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/runtime.RawExtension\"}, } } func schema_pkg_apis_clientauthentication_v1beta1_ExecCredential(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExecCredential is used by exec-based plugins to communicate credentials to HTTP transports.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec holds information passed to the plugin by the transport.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/client-go/pkg/apis/clientauthentication/v1beta1.ExecCredentialSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is filled in by the plugin and holds the credentials that the transport should use to contact the API.\", Ref:         ref(\"k8s.io/client-go/pkg/apis/clientauthentication/v1beta1.ExecCredentialStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/client-go/pkg/apis/clientauthentication/v1beta1.ExecCredentialSpec\", \"k8s.io/client-go/pkg/apis/clientauthentication/v1beta1.ExecCredentialStatus\"}, } } func schema_pkg_apis_clientauthentication_v1beta1_ExecCredentialSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExecCredentialSpec holds request and runtime specific information provided by the transport.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"cluster\": { SchemaProps: spec.SchemaProps{ Description: \"Cluster contains information to allow an exec plugin to communicate with the kubernetes cluster being authenticated to. Note that Cluster is non-nil only when provideClusterInfo is set to true in the exec provider config (i.e., ExecConfig.ProvideClusterInfo).\", Ref:         ref(\"k8s.io/client-go/pkg/apis/clientauthentication/v1beta1.Cluster\"), }, }, \"interactive\": { SchemaProps: spec.SchemaProps{ Description: \"Interactive declares whether stdin has been passed to this exec plugin.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"interactive\"}, }, }, Dependencies: []string{ \"k8s.io/client-go/pkg/apis/clientauthentication/v1beta1.Cluster\"}, } } func schema_pkg_apis_clientauthentication_v1beta1_ExecCredentialStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExecCredentialStatus holds credentials for the transport to use.nnToken and ClientKeyData are sensitive fields. This data should only be transmitted in-memory between client and exec plugin process. Exec plugin itself should at least be protected via file permissions.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"expirationTimestamp\": { SchemaProps: spec.SchemaProps{ Description: \"ExpirationTimestamp indicates a time when the provided credentials expire.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"token\": { SchemaProps: spec.SchemaProps{ Description: \"Token is a bearer token used by the client for request authentication.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"clientCertificateData\": { SchemaProps: spec.SchemaProps{ Description: \"PEM-encoded client TLS certificates (including intermediates, if any).\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"clientKeyData\": { SchemaProps: spec.SchemaProps{ Description: \"PEM-encoded private key for the above certificate.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_k8sio_cloud_provider_config_v1alpha1_CloudControllerManagerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"Generic\": { SchemaProps: spec.SchemaProps{ Description: \"Generic holds configuration for a generic controller-manager\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/controller-manager/config/v1alpha1.GenericControllerManagerConfiguration\"), }, }, \"KubeCloudShared\": { SchemaProps: spec.SchemaProps{ Description: \"KubeCloudSharedConfiguration holds configuration for shared related features both in cloud controller manager and kube-controller manager.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/cloud-provider/config/v1alpha1.KubeCloudSharedConfiguration\"), }, }, \"ServiceController\": { SchemaProps: spec.SchemaProps{ Description: \"ServiceControllerConfiguration holds configuration for ServiceController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/cloud-provider/controllers/service/config/v1alpha1.ServiceControllerConfiguration\"), }, }, \"NodeStatusUpdateFrequency\": { SchemaProps: spec.SchemaProps{ Description: \"NodeStatusUpdateFrequency is the frequency at which the controller updates nodes' status\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, }, Required: []string{\"Generic\", \"KubeCloudShared\", \"ServiceController\", \"NodeStatusUpdateFrequency\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\", \"k8s.io/cloud-provider/config/v1alpha1.KubeCloudSharedConfiguration\", \"k8s.io/cloud-provider/controllers/service/config/v1alpha1.ServiceControllerConfiguration\", \"k8s.io/controller-manager/config/v1alpha1.GenericControllerManagerConfiguration\"}, } } func schema_k8sio_cloud_provider_config_v1alpha1_CloudProviderConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CloudProviderConfiguration contains basically elements about cloud provider.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"Name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the provider for cloud services.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"CloudConfigFile\": { SchemaProps: spec.SchemaProps{ Description: \"cloudConfigFile is the path to the cloud provider configuration file.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"Name\", \"CloudConfigFile\"}, }, }, } } func schema_k8sio_cloud_provider_config_v1alpha1_KubeCloudSharedConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"KubeCloudSharedConfiguration contains elements shared by both kube-controller manager and cloud-controller manager, but not genericconfig.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"CloudProvider\": { SchemaProps: spec.SchemaProps{ Description: \"CloudProviderConfiguration holds configuration for CloudProvider related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/cloud-provider/config/v1alpha1.CloudProviderConfiguration\"), }, }, \"ExternalCloudVolumePlugin\": { SchemaProps: spec.SchemaProps{ Description: \"externalCloudVolumePlugin specifies the plugin to use when cloudProvider is \"external\". It is currently used by the in repo cloud providers to handle node and volume control in the KCM.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"UseServiceAccountCredentials\": { SchemaProps: spec.SchemaProps{ Description: \"useServiceAccountCredentials indicates whether controllers should be run with individual service account credentials.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"AllowUntaggedCloud\": { SchemaProps: spec.SchemaProps{ Description: \"run with untagged cloud instances\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"RouteReconciliationPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"routeReconciliationPeriod is the period for reconciling routes created for Nodes by cloud provider..\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"NodeMonitorPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"nodeMonitorPeriod is the period for syncing NodeStatus in NodeController.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"ClusterName\": { SchemaProps: spec.SchemaProps{ Description: \"clusterName is the instance prefix for the cluster.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ClusterCIDR\": { SchemaProps: spec.SchemaProps{ Description: \"clusterCIDR is CIDR Range for Pods in cluster.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"AllocateNodeCIDRs\": { SchemaProps: spec.SchemaProps{ Description: \"AllocateNodeCIDRs enables CIDRs for Pods to be allocated and, if ConfigureCloudRoutes is true, to be set on the cloud provider.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"CIDRAllocatorType\": { SchemaProps: spec.SchemaProps{ Description: \"CIDRAllocatorType determines what kind of pod CIDR allocator will be used.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ConfigureCloudRoutes\": { SchemaProps: spec.SchemaProps{ Description: \"configureCloudRoutes enables CIDRs allocated with allocateNodeCIDRs to be configured on the cloud provider.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"NodeSyncPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"nodeSyncPeriod is the period for syncing nodes from cloudprovider. Longer periods will result in fewer calls to cloud provider, but may delay addition of new nodes to cluster.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, }, Required: []string{\"CloudProvider\", \"ExternalCloudVolumePlugin\", \"UseServiceAccountCredentials\", \"AllowUntaggedCloud\", \"RouteReconciliationPeriod\", \"NodeMonitorPeriod\", \"ClusterName\", \"ClusterCIDR\", \"AllocateNodeCIDRs\", \"CIDRAllocatorType\", \"ConfigureCloudRoutes\", \"NodeSyncPeriod\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\", \"k8s.io/cloud-provider/config/v1alpha1.CloudProviderConfiguration\"}, } } func schema_k8sio_controller_manager_config_v1alpha1_ControllerLeaderConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ControllerLeaderConfiguration provides the configuration for a migrating leader lock.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the name of the controller being migrated E.g. service-controller, route-controller, cloud-node-controller, etc\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"component\": { SchemaProps: spec.SchemaProps{ Description: \"Component is the name of the component in which the controller should be running. E.g. kube-controller-manager, cloud-controller-manager, etc Or '*' meaning the controller can be run under any component that participates in the migration\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"component\"}, }, }, } } func schema_k8sio_controller_manager_config_v1alpha1_GenericControllerManagerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"GenericControllerManagerConfiguration holds configuration for a generic controller-manager.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"Port\": { SchemaProps: spec.SchemaProps{ Description: \"port is the port that the controller-manager's http service runs on.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"Address\": { SchemaProps: spec.SchemaProps{ Description: \"address is the IP address to serve on (set to 0.0.0.0 for all interfaces).\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"MinResyncPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"minResyncPeriod is the resync period in reflectors; will be random between minResyncPeriod and 2*minResyncPeriod.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"ClientConnection\": { SchemaProps: spec.SchemaProps{ Description: \"ClientConnection specifies the kubeconfig file and client connection settings for the proxy server to use when communicating with the apiserver.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/component-base/config/v1alpha1.ClientConnectionConfiguration\"), }, }, \"ControllerStartInterval\": { SchemaProps: spec.SchemaProps{ Description: \"How long to wait between starting controller managers\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"LeaderElection\": { SchemaProps: spec.SchemaProps{ Description: \"leaderElection defines the configuration of leader election client.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/component-base/config/v1alpha1.LeaderElectionConfiguration\"), }, }, \"Controllers\": { SchemaProps: spec.SchemaProps{ Description: \"Controllers is the list of controllers to enable or disable '*' means \"all enabled by default controllers\" 'foo' means \"enable 'foo'\" '-foo' means \"disable 'foo'\" first item for a particular name wins\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"Debugging\": { SchemaProps: spec.SchemaProps{ Description: \"DebuggingConfiguration holds configuration for Debugging related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/component-base/config/v1alpha1.DebuggingConfiguration\"), }, }, \"LeaderMigrationEnabled\": { SchemaProps: spec.SchemaProps{ Description: \"LeaderMigrationEnabled indicates whether Leader Migration should be enabled for the controller manager.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"LeaderMigration\": { SchemaProps: spec.SchemaProps{ Description: \"LeaderMigration holds the configuration for Leader Migration.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/controller-manager/config/v1alpha1.LeaderMigrationConfiguration\"), }, }, }, Required: []string{\"Port\", \"Address\", \"MinResyncPeriod\", \"ClientConnection\", \"ControllerStartInterval\", \"LeaderElection\", \"Controllers\", \"Debugging\", \"LeaderMigrationEnabled\", \"LeaderMigration\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\", \"k8s.io/component-base/config/v1alpha1.ClientConnectionConfiguration\", \"k8s.io/component-base/config/v1alpha1.DebuggingConfiguration\", \"k8s.io/component-base/config/v1alpha1.LeaderElectionConfiguration\", \"k8s.io/controller-manager/config/v1alpha1.LeaderMigrationConfiguration\"}, } } func schema_k8sio_controller_manager_config_v1alpha1_LeaderMigrationConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LeaderMigrationConfiguration provides versioned configuration for all migrating leader locks.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"leaderName\": { SchemaProps: spec.SchemaProps{ Description: \"LeaderName is the name of the leader election resource that protects the migration E.g. 1-20-KCM-to-1-21-CCM\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resourceLock\": { SchemaProps: spec.SchemaProps{ Description: \"ResourceLock indicates the resource object type that will be used to lock Should be \"leases\" or \"endpoints\"\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"controllerLeaders\": { SchemaProps: spec.SchemaProps{ Description: \"ControllerLeaders contains a list of migrating leader lock configurations\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/controller-manager/config/v1alpha1.ControllerLeaderConfiguration\"), }, }, }, }, }, }, Required: []string{\"leaderName\", \"resourceLock\", \"controllerLeaders\"}, }, }, Dependencies: []string{ \"k8s.io/controller-manager/config/v1alpha1.ControllerLeaderConfiguration\"}, } } func schema_k8sio_controller_manager_config_v1beta1_ControllerLeaderConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ControllerLeaderConfiguration provides the configuration for a migrating leader lock.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the name of the controller being migrated E.g. service-controller, route-controller, cloud-node-controller, etc\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"component\": { SchemaProps: spec.SchemaProps{ Description: \"Component is the name of the component in which the controller should be running. E.g. kube-controller-manager, cloud-controller-manager, etc Or '*' meaning the controller can be run under any component that participates in the migration\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"name\", \"component\"}, }, }, } } func schema_k8sio_controller_manager_config_v1beta1_LeaderMigrationConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"LeaderMigrationConfiguration provides versioned configuration for all migrating leader locks.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"leaderName\": { SchemaProps: spec.SchemaProps{ Description: \"LeaderName is the name of the leader election resource that protects the migration E.g. 1-20-KCM-to-1-21-CCM\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resourceLock\": { SchemaProps: spec.SchemaProps{ Description: \"ResourceLock indicates the resource object type that will be used to lock Should be \"leases\" or \"endpoints\"\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"controllerLeaders\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"ControllerLeaders contains a list of migrating leader lock configurations\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/controller-manager/config/v1beta1.ControllerLeaderConfiguration\"), }, }, }, }, }, }, Required: []string{\"leaderName\", \"resourceLock\", \"controllerLeaders\"}, }, }, Dependencies: []string{ \"k8s.io/controller-manager/config/v1beta1.ControllerLeaderConfiguration\"}, } } func schema_pkg_apis_apiregistration_v1_APIService(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"APIService represents a server for a particular GroupVersion. Name must be \"version.group\".\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec contains information for locating and communicating with a server\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1.APIServiceSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status contains derived information about an API server\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1.APIServiceStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\", \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1.APIServiceSpec\", \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1.APIServiceStatus\"}, } } func schema_pkg_apis_apiregistration_v1_APIServiceCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"APIServiceCondition describes the state of an APIService at a particular point\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type is the type of the condition.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is the status of the condition. Can be True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"Last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"Unique, one-word, CamelCase reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"Human-readable message indicating details about last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_pkg_apis_apiregistration_v1_APIServiceList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"APIServiceList is a list of APIService objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of APIService\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1.APIService\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1.APIService\"}, } } func schema_pkg_apis_apiregistration_v1_APIServiceSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"APIServiceSpec contains information for locating and communicating with a server. Only https is supported, though you are able to disable certificate verification.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"service\": { SchemaProps: spec.SchemaProps{ Description: \"Service is a reference to the service for this API server.  It must communicate on port 443. If the Service is nil, that means the handling for the API groupversion is handled locally on this server. The call will simply delegate to the normal handler chain to be fulfilled.\", Ref:         ref(\"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1.ServiceReference\"), }, }, \"group\": { SchemaProps: spec.SchemaProps{ Description: \"Group is the API group name this server hosts\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"version\": { SchemaProps: spec.SchemaProps{ Description: \"Version is the API version this server hosts.  For example, \"v1\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"insecureSkipTLSVerify\": { SchemaProps: spec.SchemaProps{ Description: \"InsecureSkipTLSVerify disables TLS certificate verification when communicating with this server. This is strongly discouraged.  You should use the CABundle instead.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"caBundle\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"CABundle is a PEM encoded CA bundle which will be used to validate an API server's serving certificate. If unspecified, system trust roots on the apiserver are used.\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, \"groupPriorityMinimum\": { SchemaProps: spec.SchemaProps{ Description: \"GroupPriorityMininum is the priority this group should have at least. Higher priority means that the group is preferred by clients over lower priority ones. Note that other versions of this group might specify even higher GroupPriorityMininum values such that the whole group gets a higher priority. The primary sort is based on GroupPriorityMinimum, ordered highest number to lowest (20 before 10). The secondary sort is based on the alphabetical comparison of the name of the object.  (v1.bar before v1.foo) We'd recommend something like: *.k8s.io (except extensions) at 18000 and PaaSes (OpenShift, Deis) are recommended to be in the 2000s\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"versionPriority\": { SchemaProps: spec.SchemaProps{ Description: \"VersionPriority controls the ordering of this API version inside of its group.  Must be greater than zero. The primary sort is based on VersionPriority, ordered highest to lowest (20 before 10). Since it's inside of a group, the number can be small, probably in the 10s. In case of equal version priorities, the version string will be used to compute the order inside a group. If the version string is \"kube-like\", it will sort above non \"kube-like\" version strings, which are ordered lexicographically. \"Kube-like\" versions start with a \"v\", then are followed by a number (the major version), then optionally the string \"alpha\" or \"beta\" and another number (the minor version). These are sorted first by GA > beta > alpha (where GA is a version with no suffix such as beta or alpha), and then by comparing major version, then minor version. An example sorted list of versions: v10, v2, v1, v11beta2, v10beta3, v3beta1, v12alpha1, v11alpha2, foo1, foo10.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"groupPriorityMinimum\", \"versionPriority\"}, }, }, Dependencies: []string{ \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1.ServiceReference\"}, } } func schema_pkg_apis_apiregistration_v1_APIServiceStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"APIServiceStatus contains derived information about an API server\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"type\", }, \"x-kubernetes-list-type\":       \"map\", \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Current service state of apiService.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1.APIServiceCondition\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1.APIServiceCondition\"}, } } func schema_pkg_apis_apiregistration_v1_ServiceReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ServiceReference holds a reference to Service.legacy.k8s.io\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"Namespace is the namespace of the service\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the name of the service\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"port\": { SchemaProps: spec.SchemaProps{ Description: \"If specified, the port on the service that hosting webhook. Default to 443 for backward compatibility. `port` should be a valid port number (1-65535, inclusive).\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_pkg_apis_apiregistration_v1beta1_APIService(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"APIService represents a server for a particular GroupVersion. Name must be \"version.group\".\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec contains information for locating and communicating with a server\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1beta1.APIServiceSpec\"), }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status contains derived information about an API server\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1beta1.APIServiceStatus\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\", \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1beta1.APIServiceSpec\", \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1beta1.APIServiceStatus\"}, } } func schema_pkg_apis_apiregistration_v1beta1_APIServiceCondition(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"APIServiceCondition describes the state of an APIService at a particular point\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type is the type of the condition.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"status\": { SchemaProps: spec.SchemaProps{ Description: \"Status is the status of the condition. Can be True, False, Unknown.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"lastTransitionTime\": { SchemaProps: spec.SchemaProps{ Description: \"Last time the condition transitioned from one status to another.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"reason\": { SchemaProps: spec.SchemaProps{ Description: \"Unique, one-word, CamelCase reason for the condition's last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"message\": { SchemaProps: spec.SchemaProps{ Description: \"Human-readable message indicating details about last transition.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"type\", \"status\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_pkg_apis_apiregistration_v1beta1_APIServiceList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"APIServiceList is a list of APIService objects.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"Items is the list of APIService\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1beta1.APIService\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1beta1.APIService\"}, } } func schema_pkg_apis_apiregistration_v1beta1_APIServiceSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"APIServiceSpec contains information for locating and communicating with a server. Only https is supported, though you are able to disable certificate verification.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"service\": { SchemaProps: spec.SchemaProps{ Description: \"Service is a reference to the service for this API server.  It must communicate on port 443. If the Service is nil, that means the handling for the API groupversion is handled locally on this server. The call will simply delegate to the normal handler chain to be fulfilled.\", Ref:         ref(\"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1beta1.ServiceReference\"), }, }, \"group\": { SchemaProps: spec.SchemaProps{ Description: \"Group is the API group name this server hosts\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"version\": { SchemaProps: spec.SchemaProps{ Description: \"Version is the API version this server hosts.  For example, \"v1\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"insecureSkipTLSVerify\": { SchemaProps: spec.SchemaProps{ Description: \"InsecureSkipTLSVerify disables TLS certificate verification when communicating with this server. This is strongly discouraged.  You should use the CABundle instead.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"caBundle\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"CABundle is a PEM encoded CA bundle which will be used to validate an API server's serving certificate. If unspecified, system trust roots on the apiserver are used.\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, \"groupPriorityMinimum\": { SchemaProps: spec.SchemaProps{ Description: \"GroupPriorityMininum is the priority this group should have at least. Higher priority means that the group is preferred by clients over lower priority ones. Note that other versions of this group might specify even higher GroupPriorityMininum values such that the whole group gets a higher priority. The primary sort is based on GroupPriorityMinimum, ordered highest number to lowest (20 before 10). The secondary sort is based on the alphabetical comparison of the name of the object.  (v1.bar before v1.foo) We'd recommend something like: *.k8s.io (except extensions) at 18000 and PaaSes (OpenShift, Deis) are recommended to be in the 2000s\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"versionPriority\": { SchemaProps: spec.SchemaProps{ Description: \"VersionPriority controls the ordering of this API version inside of its group.  Must be greater than zero. The primary sort is based on VersionPriority, ordered highest to lowest (20 before 10). Since it's inside of a group, the number can be small, probably in the 10s. In case of equal version priorities, the version string will be used to compute the order inside a group. If the version string is \"kube-like\", it will sort above non \"kube-like\" version strings, which are ordered lexicographically. \"Kube-like\" versions start with a \"v\", then are followed by a number (the major version), then optionally the string \"alpha\" or \"beta\" and another number (the minor version). These are sorted first by GA > beta > alpha (where GA is a version with no suffix such as beta or alpha), and then by comparing major version, then minor version. An example sorted list of versions: v10, v2, v1, v11beta2, v10beta3, v3beta1, v12alpha1, v11alpha2, foo1, foo10.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"groupPriorityMinimum\", \"versionPriority\"}, }, }, Dependencies: []string{ \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1beta1.ServiceReference\"}, } } func schema_pkg_apis_apiregistration_v1beta1_APIServiceStatus(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"APIServiceStatus contains derived information about an API server\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"conditions\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"type\", }, \"x-kubernetes-list-type\":       \"map\", \"x-kubernetes-patch-merge-key\": \"type\", \"x-kubernetes-patch-strategy\":  \"merge\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Current service state of apiService.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1beta1.APIServiceCondition\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/kube-aggregator/pkg/apis/apiregistration/v1beta1.APIServiceCondition\"}, } } func schema_pkg_apis_apiregistration_v1beta1_ServiceReference(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ServiceReference holds a reference to Service.legacy.k8s.io\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"Namespace is the namespace of the service\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the name of the service\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"port\": { SchemaProps: spec.SchemaProps{ Description: \"If specified, the port on the service that hosting webhook. Default to 443 for backward compatibility. `port` should be a valid port number (1-65535, inclusive).\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_AttachDetachControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"AttachDetachControllerConfiguration contains elements describing AttachDetachController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"DisableAttachDetachReconcilerSync\": { SchemaProps: spec.SchemaProps{ Description: \"Reconciler runs a periodic loop to reconcile the desired state of the with the actual state of the world by triggering attach detach operations. This flag enables or disables reconcile.  Is false by default, and thus enabled.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"ReconcilerSyncLoopPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"ReconcilerSyncLoopPeriod is the amount of time the reconciler sync states loop wait between successive executions. Is set to 5 sec by default.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, }, Required: []string{\"DisableAttachDetachReconcilerSync\", \"ReconcilerSyncLoopPeriod\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"}, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_CSRSigningConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CSRSigningConfiguration holds information about a particular CSR signer\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"CertFile\": { SchemaProps: spec.SchemaProps{ Description: \"certFile is the filename containing a PEM-encoded X509 CA certificate used to issue certificates\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"KeyFile\": { SchemaProps: spec.SchemaProps{ Description: \"keyFile is the filename containing a PEM-encoded RSA or ECDSA private key used to issue certificates\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"CertFile\", \"KeyFile\"}, }, }, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_CSRSigningControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CSRSigningControllerConfiguration contains elements describing CSRSigningController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ClusterSigningCertFile\": { SchemaProps: spec.SchemaProps{ Description: \"clusterSigningCertFile is the filename containing a PEM-encoded X509 CA certificate used to issue cluster-scoped certificates\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ClusterSigningKeyFile\": { SchemaProps: spec.SchemaProps{ Description: \"clusterSigningCertFile is the filename containing a PEM-encoded RSA or ECDSA private key used to issue cluster-scoped certificates\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"KubeletServingSignerConfiguration\": { SchemaProps: spec.SchemaProps{ Description: \"kubeletServingSignerConfiguration holds the certificate and key used to issue certificates for the kubernetes.io/kubelet-serving signer\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.CSRSigningConfiguration\"), }, }, \"KubeletClientSignerConfiguration\": { SchemaProps: spec.SchemaProps{ Description: \"kubeletClientSignerConfiguration holds the certificate and key used to issue certificates for the kubernetes.io/kube-apiserver-client-kubelet\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.CSRSigningConfiguration\"), }, }, \"KubeAPIServerClientSignerConfiguration\": { SchemaProps: spec.SchemaProps{ Description: \"kubeAPIServerClientSignerConfiguration holds the certificate and key used to issue certificates for the kubernetes.io/kube-apiserver-client\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.CSRSigningConfiguration\"), }, }, \"LegacyUnknownSignerConfiguration\": { SchemaProps: spec.SchemaProps{ Description: \"legacyUnknownSignerConfiguration holds the certificate and key used to issue certificates for the kubernetes.io/legacy-unknown\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.CSRSigningConfiguration\"), }, }, \"ClusterSigningDuration\": { SchemaProps: spec.SchemaProps{ Description: \"clusterSigningDuration is the max length of duration signed certificates will be given. Individual CSRs may request shorter certs by setting spec.expirationSeconds.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, }, Required: []string{\"ClusterSigningCertFile\", \"ClusterSigningKeyFile\", \"KubeletServingSignerConfiguration\", \"KubeletClientSignerConfiguration\", \"KubeAPIServerClientSignerConfiguration\", \"LegacyUnknownSignerConfiguration\", \"ClusterSigningDuration\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\", \"k8s.io/kube-controller-manager/config/v1alpha1.CSRSigningConfiguration\"}, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_CronJobControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CronJobControllerConfiguration contains elements describing CrongJob2Controller.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ConcurrentCronJobSyncs\": { SchemaProps: spec.SchemaProps{ Description: \"concurrentCronJobSyncs is the number of job objects that are allowed to sync concurrently. Larger number = more responsive jobs, but more CPU (and network) load.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"ConcurrentCronJobSyncs\"}, }, }, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_DaemonSetControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DaemonSetControllerConfiguration contains elements describing DaemonSetController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ConcurrentDaemonSetSyncs\": { SchemaProps: spec.SchemaProps{ Description: \"concurrentDaemonSetSyncs is the number of daemonset objects that are allowed to sync concurrently. Larger number = more responsive daemonset, but more CPU (and network) load.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"ConcurrentDaemonSetSyncs\"}, }, }, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_DeploymentControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeploymentControllerConfiguration contains elements describing DeploymentController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ConcurrentDeploymentSyncs\": { SchemaProps: spec.SchemaProps{ Description: \"concurrentDeploymentSyncs is the number of deployment objects that are allowed to sync concurrently. Larger number = more responsive deployments, but more CPU (and network) load.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"DeploymentControllerSyncPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"deploymentControllerSyncPeriod is the period for syncing the deployments.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, }, Required: []string{\"ConcurrentDeploymentSyncs\", \"DeploymentControllerSyncPeriod\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"}, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_DeprecatedControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DeprecatedControllerConfiguration contains elements be deprecated.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"DeletingPodsQPS\": { SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED: deletingPodsQps is the number of nodes per second on which pods are deleted in case of node failure.\", Default:     0, Type:        []string{\"number\"}, Format:      \"float\", }, }, \"DeletingPodsBurst\": { SchemaProps: spec.SchemaProps{ Description: \"DEPRECATED: deletingPodsBurst is the number of nodes on which pods are bursty deleted in case of node failure. For more details look into RateLimiter.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"RegisterRetryCount\": { SchemaProps: spec.SchemaProps{ Description: \"registerRetryCount is the number of retries for initial node registration. Retry interval equals node-sync-period.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"DeletingPodsQPS\", \"DeletingPodsBurst\", \"RegisterRetryCount\"}, }, }, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_EndpointControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EndpointControllerConfiguration contains elements describing EndpointController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ConcurrentEndpointSyncs\": { SchemaProps: spec.SchemaProps{ Description: \"concurrentEndpointSyncs is the number of endpoint syncing operations that will be done concurrently. Larger number = faster endpoint updating, but more CPU (and network) load.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"EndpointUpdatesBatchPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"EndpointUpdatesBatchPeriod describes the length of endpoint updates batching period. Processing of pod changes will be delayed by this duration to join them with potential upcoming updates and reduce the overall number of endpoints updates.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, }, Required: []string{\"ConcurrentEndpointSyncs\", \"EndpointUpdatesBatchPeriod\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"}, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_EndpointSliceControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EndpointSliceControllerConfiguration contains elements describing EndpointSliceController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ConcurrentServiceEndpointSyncs\": { SchemaProps: spec.SchemaProps{ Description: \"concurrentServiceEndpointSyncs is the number of service endpoint syncing operations that will be done concurrently. Larger number = faster endpoint slice updating, but more CPU (and network) load.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"MaxEndpointsPerSlice\": { SchemaProps: spec.SchemaProps{ Description: \"maxEndpointsPerSlice is the maximum number of endpoints that will be added to an EndpointSlice. More endpoints per slice will result in fewer and larger endpoint slices, but larger resources.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"EndpointUpdatesBatchPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"EndpointUpdatesBatchPeriod describes the length of endpoint updates batching period. Processing of pod changes will be delayed by this duration to join them with potential upcoming updates and reduce the overall number of endpoints updates.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, }, Required: []string{\"ConcurrentServiceEndpointSyncs\", \"MaxEndpointsPerSlice\", \"EndpointUpdatesBatchPeriod\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"}, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_EndpointSliceMirroringControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EndpointSliceMirroringControllerConfiguration contains elements describing EndpointSliceMirroringController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"MirroringConcurrentServiceEndpointSyncs\": { SchemaProps: spec.SchemaProps{ Description: \"mirroringConcurrentServiceEndpointSyncs is the number of service endpoint syncing operations that will be done concurrently. Larger number = faster endpoint slice updating, but more CPU (and network) load.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"MirroringMaxEndpointsPerSubset\": { SchemaProps: spec.SchemaProps{ Description: \"mirroringMaxEndpointsPerSubset is the maximum number of endpoints that will be mirrored to an EndpointSlice for an EndpointSubset.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"MirroringEndpointUpdatesBatchPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"mirroringEndpointUpdatesBatchPeriod can be used to batch EndpointSlice updates. All updates triggered by EndpointSlice changes will be delayed by up to 'mirroringEndpointUpdatesBatchPeriod'. If other addresses in the same Endpoints resource change in that period, they will be batched to a single EndpointSlice update. Default 0 value means that each Endpoints update triggers an EndpointSlice update.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, }, Required: []string{\"MirroringConcurrentServiceEndpointSyncs\", \"MirroringMaxEndpointsPerSubset\", \"MirroringEndpointUpdatesBatchPeriod\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"}, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_EphemeralVolumeControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"EphemeralVolumeControllerConfiguration contains elements describing EphemeralVolumeController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ConcurrentEphemeralVolumeSyncs\": { SchemaProps: spec.SchemaProps{ Description: \"ConcurrentEphemeralVolumeSyncseSyncs is the number of ephemeral volume syncing operations that will be done concurrently. Larger number = faster ephemeral volume updating, but more CPU (and network) load.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"ConcurrentEphemeralVolumeSyncs\"}, }, }, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_GarbageCollectorControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"GarbageCollectorControllerConfiguration contains elements describing GarbageCollectorController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"EnableGarbageCollector\": { SchemaProps: spec.SchemaProps{ Description: \"enables the generic garbage collector. MUST be synced with the corresponding flag of the kube-apiserver. WARNING: the generic garbage collector is an alpha feature.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"ConcurrentGCSyncs\": { SchemaProps: spec.SchemaProps{ Description: \"concurrentGCSyncs is the number of garbage collector workers that are allowed to sync concurrently.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"GCIgnoredResources\": { SchemaProps: spec.SchemaProps{ Description: \"gcIgnoredResources is the list of GroupResources that garbage collection should ignore.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-controller-manager/config/v1alpha1.GroupResource\"), }, }, }, }, }, }, Required: []string{\"EnableGarbageCollector\", \"ConcurrentGCSyncs\", \"GCIgnoredResources\"}, }, }, Dependencies: []string{ \"k8s.io/kube-controller-manager/config/v1alpha1.GroupResource\"}, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_GroupResource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"GroupResource describes an group resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"Group\": { SchemaProps: spec.SchemaProps{ Description: \"group is the group portion of the GroupResource.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"Resource\": { SchemaProps: spec.SchemaProps{ Description: \"resource is the resource portion of the GroupResource.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"Group\", \"Resource\"}, }, }, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_HPAControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"HPAControllerConfiguration contains elements describing HPAController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"HorizontalPodAutoscalerSyncPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerSyncPeriod is the period for syncing the number of pods in horizontal pod autoscaler.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"HorizontalPodAutoscalerUpscaleForbiddenWindow\": { SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerUpscaleForbiddenWindow is a period after which next upscale allowed.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"HorizontalPodAutoscalerDownscaleStabilizationWindow\": { SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerDowncaleStabilizationWindow is a period for which autoscaler will look backwards and not scale down below any recommendation it made during that period.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"HorizontalPodAutoscalerDownscaleForbiddenWindow\": { SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerDownscaleForbiddenWindow is a period after which next downscale allowed.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"HorizontalPodAutoscalerTolerance\": { SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerTolerance is the tolerance for when resource usage suggests upscaling/downscaling\", Default:     0, Type:        []string{\"number\"}, Format:      \"double\", }, }, \"HorizontalPodAutoscalerCPUInitializationPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerCPUInitializationPeriod is the period after pod start when CPU samples might be skipped.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"HorizontalPodAutoscalerInitialReadinessDelay\": { SchemaProps: spec.SchemaProps{ Description: \"HorizontalPodAutoscalerInitialReadinessDelay is period after pod start during which readiness changes are treated as readiness being set for the first time. The only effect of this is that HPA will disregard CPU samples from unready pods that had last readiness change during that period.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, }, Required: []string{\"HorizontalPodAutoscalerSyncPeriod\", \"HorizontalPodAutoscalerUpscaleForbiddenWindow\", \"HorizontalPodAutoscalerDownscaleStabilizationWindow\", \"HorizontalPodAutoscalerDownscaleForbiddenWindow\", \"HorizontalPodAutoscalerTolerance\", \"HorizontalPodAutoscalerCPUInitializationPeriod\", \"HorizontalPodAutoscalerInitialReadinessDelay\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"}, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_JobControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"JobControllerConfiguration contains elements describing JobController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ConcurrentJobSyncs\": { SchemaProps: spec.SchemaProps{ Description: \"concurrentJobSyncs is the number of job objects that are allowed to sync concurrently. Larger number = more responsive jobs, but more CPU (and network) load.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"ConcurrentJobSyncs\"}, }, }, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_KubeControllerManagerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"KubeControllerManagerConfiguration contains elements describing kube-controller manager.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"Generic\": { SchemaProps: spec.SchemaProps{ Description: \"Generic holds configuration for a generic controller-manager\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/controller-manager/config/v1alpha1.GenericControllerManagerConfiguration\"), }, }, \"KubeCloudShared\": { SchemaProps: spec.SchemaProps{ Description: \"KubeCloudSharedConfiguration holds configuration for shared related features both in cloud controller manager and kube-controller manager.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/cloud-provider/config/v1alpha1.KubeCloudSharedConfiguration\"), }, }, \"AttachDetachController\": { SchemaProps: spec.SchemaProps{ Description: \"AttachDetachControllerConfiguration holds configuration for AttachDetachController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.AttachDetachControllerConfiguration\"), }, }, \"CSRSigningController\": { SchemaProps: spec.SchemaProps{ Description: \"CSRSigningControllerConfiguration holds configuration for CSRSigningController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.CSRSigningControllerConfiguration\"), }, }, \"DaemonSetController\": { SchemaProps: spec.SchemaProps{ Description: \"DaemonSetControllerConfiguration holds configuration for DaemonSetController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.DaemonSetControllerConfiguration\"), }, }, \"DeploymentController\": { SchemaProps: spec.SchemaProps{ Description: \"DeploymentControllerConfiguration holds configuration for DeploymentController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.DeploymentControllerConfiguration\"), }, }, \"StatefulSetController\": { SchemaProps: spec.SchemaProps{ Description: \"StatefulSetControllerConfiguration holds configuration for StatefulSetController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.StatefulSetControllerConfiguration\"), }, }, \"DeprecatedController\": { SchemaProps: spec.SchemaProps{ Description: \"DeprecatedControllerConfiguration holds configuration for some deprecated features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.DeprecatedControllerConfiguration\"), }, }, \"EndpointController\": { SchemaProps: spec.SchemaProps{ Description: \"EndpointControllerConfiguration holds configuration for EndpointController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.EndpointControllerConfiguration\"), }, }, \"EndpointSliceController\": { SchemaProps: spec.SchemaProps{ Description: \"EndpointSliceControllerConfiguration holds configuration for EndpointSliceController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.EndpointSliceControllerConfiguration\"), }, }, \"EndpointSliceMirroringController\": { SchemaProps: spec.SchemaProps{ Description: \"EndpointSliceMirroringControllerConfiguration holds configuration for EndpointSliceMirroringController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.EndpointSliceMirroringControllerConfiguration\"), }, }, \"EphemeralVolumeController\": { SchemaProps: spec.SchemaProps{ Description: \"EphemeralVolumeControllerConfiguration holds configuration for EphemeralVolumeController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.EphemeralVolumeControllerConfiguration\"), }, }, \"GarbageCollectorController\": { SchemaProps: spec.SchemaProps{ Description: \"GarbageCollectorControllerConfiguration holds configuration for GarbageCollectorController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.GarbageCollectorControllerConfiguration\"), }, }, \"HPAController\": { SchemaProps: spec.SchemaProps{ Description: \"HPAControllerConfiguration holds configuration for HPAController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.HPAControllerConfiguration\"), }, }, \"JobController\": { SchemaProps: spec.SchemaProps{ Description: \"JobControllerConfiguration holds configuration for JobController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.JobControllerConfiguration\"), }, }, \"CronJobController\": { SchemaProps: spec.SchemaProps{ Description: \"CronJobControllerConfiguration holds configuration for CronJobController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.CronJobControllerConfiguration\"), }, }, \"NamespaceController\": { SchemaProps: spec.SchemaProps{ Description: \"NamespaceControllerConfiguration holds configuration for NamespaceController related features. NamespaceControllerConfiguration holds configuration for NamespaceController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.NamespaceControllerConfiguration\"), }, }, \"NodeIPAMController\": { SchemaProps: spec.SchemaProps{ Description: \"NodeIPAMControllerConfiguration holds configuration for NodeIPAMController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.NodeIPAMControllerConfiguration\"), }, }, \"NodeLifecycleController\": { SchemaProps: spec.SchemaProps{ Description: \"NodeLifecycleControllerConfiguration holds configuration for NodeLifecycleController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.NodeLifecycleControllerConfiguration\"), }, }, \"PersistentVolumeBinderController\": { SchemaProps: spec.SchemaProps{ Description: \"PersistentVolumeBinderControllerConfiguration holds configuration for PersistentVolumeBinderController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.PersistentVolumeBinderControllerConfiguration\"), }, }, \"PodGCController\": { SchemaProps: spec.SchemaProps{ Description: \"PodGCControllerConfiguration holds configuration for PodGCController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.PodGCControllerConfiguration\"), }, }, \"ReplicaSetController\": { SchemaProps: spec.SchemaProps{ Description: \"ReplicaSetControllerConfiguration holds configuration for ReplicaSet related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.ReplicaSetControllerConfiguration\"), }, }, \"ReplicationController\": { SchemaProps: spec.SchemaProps{ Description: \"ReplicationControllerConfiguration holds configuration for ReplicationController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.ReplicationControllerConfiguration\"), }, }, \"ResourceQuotaController\": { SchemaProps: spec.SchemaProps{ Description: \"ResourceQuotaControllerConfiguration holds configuration for ResourceQuotaController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.ResourceQuotaControllerConfiguration\"), }, }, \"SAController\": { SchemaProps: spec.SchemaProps{ Description: \"SAControllerConfiguration holds configuration for ServiceAccountController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.SAControllerConfiguration\"), }, }, \"ServiceController\": { SchemaProps: spec.SchemaProps{ Description: \"ServiceControllerConfiguration holds configuration for ServiceController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/cloud-provider/controllers/service/config/v1alpha1.ServiceControllerConfiguration\"), }, }, \"TTLAfterFinishedController\": { SchemaProps: spec.SchemaProps{ Description: \"TTLAfterFinishedControllerConfiguration holds configuration for TTLAfterFinishedController related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.TTLAfterFinishedControllerConfiguration\"), }, }, }, Required: []string{\"Generic\", \"KubeCloudShared\", \"AttachDetachController\", \"CSRSigningController\", \"DaemonSetController\", \"DeploymentController\", \"StatefulSetController\", \"DeprecatedController\", \"EndpointController\", \"EndpointSliceController\", \"EndpointSliceMirroringController\", \"EphemeralVolumeController\", \"GarbageCollectorController\", \"HPAController\", \"JobController\", \"CronJobController\", \"NamespaceController\", \"NodeIPAMController\", \"NodeLifecycleController\", \"PersistentVolumeBinderController\", \"PodGCController\", \"ReplicaSetController\", \"ReplicationController\", \"ResourceQuotaController\", \"SAController\", \"ServiceController\", \"TTLAfterFinishedController\"}, }, }, Dependencies: []string{ \"k8s.io/cloud-provider/config/v1alpha1.KubeCloudSharedConfiguration\", \"k8s.io/cloud-provider/controllers/service/config/v1alpha1.ServiceControllerConfiguration\", \"k8s.io/controller-manager/config/v1alpha1.GenericControllerManagerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.AttachDetachControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.CSRSigningControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.CronJobControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.DaemonSetControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.DeploymentControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.DeprecatedControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.EndpointControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.EndpointSliceControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.EndpointSliceMirroringControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.EphemeralVolumeControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.GarbageCollectorControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.HPAControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.JobControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.NamespaceControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.NodeIPAMControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.NodeLifecycleControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.PersistentVolumeBinderControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.PodGCControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.ReplicaSetControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.ReplicationControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.ResourceQuotaControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.SAControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.StatefulSetControllerConfiguration\", \"k8s.io/kube-controller-manager/config/v1alpha1.TTLAfterFinishedControllerConfiguration\"}, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_NamespaceControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NamespaceControllerConfiguration contains elements describing NamespaceController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"NamespaceSyncPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"namespaceSyncPeriod is the period for syncing namespace life-cycle updates.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"ConcurrentNamespaceSyncs\": { SchemaProps: spec.SchemaProps{ Description: \"concurrentNamespaceSyncs is the number of namespace objects that are allowed to sync concurrently.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"NamespaceSyncPeriod\", \"ConcurrentNamespaceSyncs\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"}, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_NodeIPAMControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeIPAMControllerConfiguration contains elements describing NodeIpamController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ServiceCIDR\": { SchemaProps: spec.SchemaProps{ Description: \"serviceCIDR is CIDR Range for Services in cluster.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"SecondaryServiceCIDR\": { SchemaProps: spec.SchemaProps{ Description: \"secondaryServiceCIDR is CIDR Range for Services in cluster. This is used in dual stack clusters. SecondaryServiceCIDR must be of different IP family than ServiceCIDR\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"NodeCIDRMaskSize\": { SchemaProps: spec.SchemaProps{ Description: \"NodeCIDRMaskSize is the mask size for node cidr in cluster.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"NodeCIDRMaskSizeIPv4\": { SchemaProps: spec.SchemaProps{ Description: \"NodeCIDRMaskSizeIPv4 is the mask size for node cidr in dual-stack cluster.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"NodeCIDRMaskSizeIPv6\": { SchemaProps: spec.SchemaProps{ Description: \"NodeCIDRMaskSizeIPv6 is the mask size for node cidr in dual-stack cluster.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"ServiceCIDR\", \"SecondaryServiceCIDR\", \"NodeCIDRMaskSize\", \"NodeCIDRMaskSizeIPv4\", \"NodeCIDRMaskSizeIPv6\"}, }, }, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_NodeLifecycleControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeLifecycleControllerConfiguration contains elements describing NodeLifecycleController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"EnableTaintManager\": { SchemaProps: spec.SchemaProps{ Description: \"If set to true enables NoExecute Taints and will evict all not-tolerating Pod running on Nodes tainted with this kind of Taints.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"NodeEvictionRate\": { SchemaProps: spec.SchemaProps{ Description: \"nodeEvictionRate is the number of nodes per second on which pods are deleted in case of node failure when a zone is healthy\", Default:     0, Type:        []string{\"number\"}, Format:      \"float\", }, }, \"SecondaryNodeEvictionRate\": { SchemaProps: spec.SchemaProps{ Description: \"secondaryNodeEvictionRate is the number of nodes per second on which pods are deleted in case of node failure when a zone is unhealthy\", Default:     0, Type:        []string{\"number\"}, Format:      \"float\", }, }, \"NodeStartupGracePeriod\": { SchemaProps: spec.SchemaProps{ Description: \"nodeStartupGracePeriod is the amount of time which we allow starting a node to be unresponsive before marking it unhealthy.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"NodeMonitorGracePeriod\": { SchemaProps: spec.SchemaProps{ Description: \"nodeMontiorGracePeriod is the amount of time which we allow a running node to be unresponsive before marking it unhealthy. Must be N times more than kubelet's nodeStatusUpdateFrequency, where N means number of retries allowed for kubelet to post node status.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"PodEvictionTimeout\": { SchemaProps: spec.SchemaProps{ Description: \"podEvictionTimeout is the grace period for deleting pods on failed nodes.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"LargeClusterSizeThreshold\": { SchemaProps: spec.SchemaProps{ Description: \"secondaryNodeEvictionRate is implicitly overridden to 0 for clusters smaller than or equal to largeClusterSizeThreshold\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"UnhealthyZoneThreshold\": { SchemaProps: spec.SchemaProps{ Description: \"Zone is treated as unhealthy in nodeEvictionRate and secondaryNodeEvictionRate when at least unhealthyZoneThreshold (no less than 3) of Nodes in the zone are NotReady\", Default:     0, Type:        []string{\"number\"}, Format:      \"float\", }, }, }, Required: []string{\"EnableTaintManager\", \"NodeEvictionRate\", \"SecondaryNodeEvictionRate\", \"NodeStartupGracePeriod\", \"NodeMonitorGracePeriod\", \"PodEvictionTimeout\", \"LargeClusterSizeThreshold\", \"UnhealthyZoneThreshold\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"}, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_PersistentVolumeBinderControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PersistentVolumeBinderControllerConfiguration contains elements describing PersistentVolumeBinderController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"PVClaimBinderSyncPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"pvClaimBinderSyncPeriod is the period for syncing persistent volumes and persistent volume claims.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"VolumeConfiguration\": { SchemaProps: spec.SchemaProps{ Description: \"volumeConfiguration holds configuration for volume related features.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.VolumeConfiguration\"), }, }, \"VolumeHostCIDRDenylist\": { SchemaProps: spec.SchemaProps{ Description: \"VolumeHostCIDRDenylist is a list of CIDRs that should not be reachable by the controller from plugins.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"VolumeHostAllowLocalLoopback\": { SchemaProps: spec.SchemaProps{ Description: \"VolumeHostAllowLocalLoopback indicates if local loopback hosts (127.0.0.1, etc) should be allowed from plugins.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"PVClaimBinderSyncPeriod\", \"VolumeConfiguration\", \"VolumeHostCIDRDenylist\", \"VolumeHostAllowLocalLoopback\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\", \"k8s.io/kube-controller-manager/config/v1alpha1.VolumeConfiguration\"}, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_PersistentVolumeRecyclerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PersistentVolumeRecyclerConfiguration contains elements describing persistent volume plugins.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"MaximumRetry\": { SchemaProps: spec.SchemaProps{ Description: \"maximumRetry is number of retries the PV recycler will execute on failure to recycle PV.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"MinimumTimeoutNFS\": { SchemaProps: spec.SchemaProps{ Description: \"minimumTimeoutNFS is the minimum ActiveDeadlineSeconds to use for an NFS Recycler pod.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"PodTemplateFilePathNFS\": { SchemaProps: spec.SchemaProps{ Description: \"podTemplateFilePathNFS is the file path to a pod definition used as a template for NFS persistent volume recycling\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"IncrementTimeoutNFS\": { SchemaProps: spec.SchemaProps{ Description: \"incrementTimeoutNFS is the increment of time added per Gi to ActiveDeadlineSeconds for an NFS scrubber pod.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"PodTemplateFilePathHostPath\": { SchemaProps: spec.SchemaProps{ Description: \"podTemplateFilePathHostPath is the file path to a pod definition used as a template for HostPath persistent volume recycling. This is for development and testing only and will not work in a multi-node cluster.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"MinimumTimeoutHostPath\": { SchemaProps: spec.SchemaProps{ Description: \"minimumTimeoutHostPath is the minimum ActiveDeadlineSeconds to use for a HostPath Recycler pod.  This is for development and testing only and will not work in a multi-node cluster.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"IncrementTimeoutHostPath\": { SchemaProps: spec.SchemaProps{ Description: \"incrementTimeoutHostPath is the increment of time added per Gi to ActiveDeadlineSeconds for a HostPath scrubber pod.  This is for development and testing only and will not work in a multi-node cluster.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"MaximumRetry\", \"MinimumTimeoutNFS\", \"PodTemplateFilePathNFS\", \"IncrementTimeoutNFS\", \"PodTemplateFilePathHostPath\", \"MinimumTimeoutHostPath\", \"IncrementTimeoutHostPath\"}, }, }, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_PodGCControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodGCControllerConfiguration contains elements describing PodGCController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"TerminatedPodGCThreshold\": { SchemaProps: spec.SchemaProps{ Description: \"terminatedPodGCThreshold is the number of terminated pods that can exist before the terminated pod garbage collector starts deleting terminated pods. If <= 0, the terminated pod garbage collector is disabled.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"TerminatedPodGCThreshold\"}, }, }, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_ReplicaSetControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicaSetControllerConfiguration contains elements describing ReplicaSetController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ConcurrentRSSyncs\": { SchemaProps: spec.SchemaProps{ Description: \"concurrentRSSyncs is the number of replica sets that are  allowed to sync concurrently. Larger number = more responsive replica  management, but more CPU (and network) load.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"ConcurrentRSSyncs\"}, }, }, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_ReplicationControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ReplicationControllerConfiguration contains elements describing ReplicationController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ConcurrentRCSyncs\": { SchemaProps: spec.SchemaProps{ Description: \"concurrentRCSyncs is the number of replication controllers that are allowed to sync concurrently. Larger number = more responsive replica management, but more CPU (and network) load.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"ConcurrentRCSyncs\"}, }, }, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_ResourceQuotaControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceQuotaControllerConfiguration contains elements describing ResourceQuotaController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ResourceQuotaSyncPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"resourceQuotaSyncPeriod is the period for syncing quota usage status in the system.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"ConcurrentResourceQuotaSyncs\": { SchemaProps: spec.SchemaProps{ Description: \"concurrentResourceQuotaSyncs is the number of resource quotas that are allowed to sync concurrently. Larger number = more responsive quota management, but more CPU (and network) load.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"ResourceQuotaSyncPeriod\", \"ConcurrentResourceQuotaSyncs\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"}, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_SAControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SAControllerConfiguration contains elements describing ServiceAccountController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ServiceAccountKeyFile\": { SchemaProps: spec.SchemaProps{ Description: \"serviceAccountKeyFile is the filename containing a PEM-encoded private RSA key used to sign service account tokens.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ConcurrentSATokenSyncs\": { SchemaProps: spec.SchemaProps{ Description: \"concurrentSATokenSyncs is the number of service account token syncing operations that will be done concurrently.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"RootCAFile\": { SchemaProps: spec.SchemaProps{ Description: \"rootCAFile is the root certificate authority will be included in service account's token secret. This must be a valid PEM-encoded CA bundle.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"ServiceAccountKeyFile\", \"ConcurrentSATokenSyncs\", \"RootCAFile\"}, }, }, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_StatefulSetControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"StatefulSetControllerConfiguration contains elements describing StatefulSetController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ConcurrentStatefulSetSyncs\": { SchemaProps: spec.SchemaProps{ Description: \"concurrentStatefulSetSyncs is the number of statefulset objects that are allowed to sync concurrently. Larger number = more responsive statefulsets, but more CPU (and network) load.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"ConcurrentStatefulSetSyncs\"}, }, }, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_TTLAfterFinishedControllerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"TTLAfterFinishedControllerConfiguration contains elements describing TTLAfterFinishedController.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"ConcurrentTTLSyncs\": { SchemaProps: spec.SchemaProps{ Description: \"concurrentTTLSyncs is the number of TTL-after-finished collector workers that are allowed to sync concurrently.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"ConcurrentTTLSyncs\"}, }, }, } } func schema_k8sio_kube_controller_manager_config_v1alpha1_VolumeConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeConfiguration contains *all* enumerated flags meant to configure all volume plugins. From this config, the controller-manager binary will create many instances of volume.VolumeConfig, each containing only the configuration needed for that plugin which are then passed to the appropriate plugin. The ControllerManager binary is the only part of the code which knows what plugins are supported and which flags correspond to each plugin.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"EnableHostPathProvisioning\": { SchemaProps: spec.SchemaProps{ Description: \"enableHostPathProvisioning enables HostPath PV provisioning when running without a cloud provider. This allows testing and development of provisioning features. HostPath provisioning is not supported in any way, won't work in a multi-node cluster, and should not be used for anything other than testing or development.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"EnableDynamicProvisioning\": { SchemaProps: spec.SchemaProps{ Description: \"enableDynamicProvisioning enables the provisioning of volumes when running within an environment that supports dynamic provisioning. Defaults to true.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"PersistentVolumeRecyclerConfiguration\": { SchemaProps: spec.SchemaProps{ Description: \"persistentVolumeRecyclerConfiguration holds configuration for persistent volume plugins.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-controller-manager/config/v1alpha1.PersistentVolumeRecyclerConfiguration\"), }, }, \"FlexVolumePluginDir\": { SchemaProps: spec.SchemaProps{ Description: \"volumePluginDir is the full path of the directory in which the flex volume plugin should search for additional third party volume plugins\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"EnableHostPathProvisioning\", \"EnableDynamicProvisioning\", \"PersistentVolumeRecyclerConfiguration\", \"FlexVolumePluginDir\"}, }, }, Dependencies: []string{ \"k8s.io/kube-controller-manager/config/v1alpha1.PersistentVolumeRecyclerConfiguration\"}, } } func schema_k8sio_kube_proxy_config_v1alpha1_KubeProxyConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"KubeProxyConfiguration contains everything necessary to configure the Kubernetes proxy server.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"featureGates\": { SchemaProps: spec.SchemaProps{ Description: \"featureGates is a map of feature names to bools that enable or disable alpha/experimental features.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: false, Type:    []string{\"boolean\"}, Format:  \"\", }, }, }, }, }, \"bindAddress\": { SchemaProps: spec.SchemaProps{ Description: \"bindAddress is the IP address for the proxy server to serve on (set to 0.0.0.0 for all interfaces)\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"healthzBindAddress\": { SchemaProps: spec.SchemaProps{ Description: \"healthzBindAddress is the IP address and port for the health check server to serve on, defaulting to 0.0.0.0:10256\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metricsBindAddress\": { SchemaProps: spec.SchemaProps{ Description: \"metricsBindAddress is the IP address and port for the metrics server to serve on, defaulting to 127.0.0.1:10249 (set to 0.0.0.0 for all interfaces)\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"bindAddressHardFail\": { SchemaProps: spec.SchemaProps{ Description: \"bindAddressHardFail, if true, kube-proxy will treat failure to bind to a port as fatal and exit\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"enableProfiling\": { SchemaProps: spec.SchemaProps{ Description: \"enableProfiling enables profiling via web interface on /debug/pprof handler. Profiling handlers will be handled by metrics server.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"clusterCIDR\": { SchemaProps: spec.SchemaProps{ Description: \"clusterCIDR is the CIDR range of the pods in the cluster. It is used to bridge traffic coming from outside of the cluster. If not provided, no off-cluster bridging will be performed.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"hostnameOverride\": { SchemaProps: spec.SchemaProps{ Description: \"hostnameOverride, if non-empty, will be used as the identity instead of the actual hostname.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"clientConnection\": { SchemaProps: spec.SchemaProps{ Description: \"clientConnection specifies the kubeconfig file and client connection settings for the proxy server to use when communicating with the apiserver.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/component-base/config/v1alpha1.ClientConnectionConfiguration\"), }, }, \"iptables\": { SchemaProps: spec.SchemaProps{ Description: \"iptables contains iptables-related configuration options.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-proxy/config/v1alpha1.KubeProxyIPTablesConfiguration\"), }, }, \"ipvs\": { SchemaProps: spec.SchemaProps{ Description: \"ipvs contains ipvs-related configuration options.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-proxy/config/v1alpha1.KubeProxyIPVSConfiguration\"), }, }, \"oomScoreAdj\": { SchemaProps: spec.SchemaProps{ Description: \"oomScoreAdj is the oom-score-adj value for kube-proxy process. Values must be within the range [-1000, 1000]\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"mode\": { SchemaProps: spec.SchemaProps{ Description: \"mode specifies which proxy mode to use.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"portRange\": { SchemaProps: spec.SchemaProps{ Description: \"portRange is the range of host ports (beginPort-endPort, inclusive) that may be consumed in order to proxy service traffic. If unspecified (0-0) then ports will be randomly chosen.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"udpIdleTimeout\": { SchemaProps: spec.SchemaProps{ Description: \"udpIdleTimeout is how long an idle UDP connection will be kept open (e.g. '250ms', '2s'). Must be greater than 0. Only applicable for proxyMode=userspace.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"conntrack\": { SchemaProps: spec.SchemaProps{ Description: \"conntrack contains conntrack-related configuration options.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-proxy/config/v1alpha1.KubeProxyConntrackConfiguration\"), }, }, \"configSyncPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"configSyncPeriod is how often configuration from the apiserver is refreshed. Must be greater than 0.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"nodePortAddresses\": { SchemaProps: spec.SchemaProps{ Description: \"nodePortAddresses is the --nodeport-addresses value for kube-proxy process. Values must be valid IP blocks. These values are as a parameter to select the interfaces where nodeport works. In case someone would like to expose a service on localhost for local visit and some other interfaces for particular purpose, a list of IP blocks would do that. If set it to \"127.0.0.0/8\", kube-proxy will only select the loopback interface for NodePort. If set it to a non-zero IP block, kube-proxy will filter that down to just the IPs that applied to the node. An empty string slice is meant to select all network interfaces.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"winkernel\": { SchemaProps: spec.SchemaProps{ Description: \"winkernel contains winkernel-related configuration options.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-proxy/config/v1alpha1.KubeProxyWinkernelConfiguration\"), }, }, \"showHiddenMetricsForVersion\": { SchemaProps: spec.SchemaProps{ Description: \"ShowHiddenMetricsForVersion is the version for which you want to show hidden metrics.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"detectLocalMode\": { SchemaProps: spec.SchemaProps{ Description: \"DetectLocalMode determines mode to use for detecting local traffic, defaults to LocalModeClusterCIDR\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, Required: []string{\"bindAddress\", \"healthzBindAddress\", \"metricsBindAddress\", \"bindAddressHardFail\", \"enableProfiling\", \"clusterCIDR\", \"hostnameOverride\", \"clientConnection\", \"iptables\", \"ipvs\", \"oomScoreAdj\", \"mode\", \"portRange\", \"udpIdleTimeout\", \"conntrack\", \"configSyncPeriod\", \"nodePortAddresses\", \"winkernel\", \"showHiddenMetricsForVersion\", \"detectLocalMode\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\", \"k8s.io/component-base/config/v1alpha1.ClientConnectionConfiguration\", \"k8s.io/kube-proxy/config/v1alpha1.KubeProxyConntrackConfiguration\", \"k8s.io/kube-proxy/config/v1alpha1.KubeProxyIPTablesConfiguration\", \"k8s.io/kube-proxy/config/v1alpha1.KubeProxyIPVSConfiguration\", \"k8s.io/kube-proxy/config/v1alpha1.KubeProxyWinkernelConfiguration\"}, } } func schema_k8sio_kube_proxy_config_v1alpha1_KubeProxyConntrackConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"KubeProxyConntrackConfiguration contains conntrack settings for the Kubernetes proxy server.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"maxPerCore\": { SchemaProps: spec.SchemaProps{ Description: \"maxPerCore is the maximum number of NAT connections to track per CPU core (0 to leave the limit as-is and ignore min).\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"min\": { SchemaProps: spec.SchemaProps{ Description: \"min is the minimum value of connect-tracking records to allocate, regardless of conntrackMaxPerCore (set maxPerCore=0 to leave the limit as-is).\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"tcpEstablishedTimeout\": { SchemaProps: spec.SchemaProps{ Description: \"tcpEstablishedTimeout is how long an idle TCP connection will be kept open (e.g. '2s').  Must be greater than 0 to set.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"tcpCloseWaitTimeout\": { SchemaProps: spec.SchemaProps{ Description: \"tcpCloseWaitTimeout is how long an idle conntrack entry in CLOSE_WAIT state will remain in the conntrack table. (e.g. '60s'). Must be greater than 0 to set.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, }, Required: []string{\"maxPerCore\", \"min\", \"tcpEstablishedTimeout\", \"tcpCloseWaitTimeout\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"}, } } func schema_k8sio_kube_proxy_config_v1alpha1_KubeProxyIPTablesConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"KubeProxyIPTablesConfiguration contains iptables-related configuration details for the Kubernetes proxy server.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"masqueradeBit\": { SchemaProps: spec.SchemaProps{ Description: \"masqueradeBit is the bit of the iptables fwmark space to use for SNAT if using the pure iptables proxy mode. Values must be within the range [0, 31].\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"masqueradeAll\": { SchemaProps: spec.SchemaProps{ Description: \"masqueradeAll tells kube-proxy to SNAT everything if using the pure iptables proxy mode.\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"syncPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"syncPeriod is the period that iptables rules are refreshed (e.g. '5s', '1m', '2h22m').  Must be greater than 0.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"minSyncPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"minSyncPeriod is the minimum period that iptables rules are refreshed (e.g. '5s', '1m', '2h22m').\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, }, Required: []string{\"masqueradeBit\", \"masqueradeAll\", \"syncPeriod\", \"minSyncPeriod\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"}, } } func schema_k8sio_kube_proxy_config_v1alpha1_KubeProxyIPVSConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"KubeProxyIPVSConfiguration contains ipvs-related configuration details for the Kubernetes proxy server.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"syncPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"syncPeriod is the period that ipvs rules are refreshed (e.g. '5s', '1m', '2h22m').  Must be greater than 0.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"minSyncPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"minSyncPeriod is the minimum period that ipvs rules are refreshed (e.g. '5s', '1m', '2h22m').\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"scheduler\": { SchemaProps: spec.SchemaProps{ Description: \"ipvs scheduler\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"excludeCIDRs\": { SchemaProps: spec.SchemaProps{ Description: \"excludeCIDRs is a list of CIDR's which the ipvs proxier should not touch when cleaning up ipvs services.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"strictARP\": { SchemaProps: spec.SchemaProps{ Description: \"strict ARP configure arp_ignore and arp_announce to avoid answering ARP queries from kube-ipvs0 interface\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"tcpTimeout\": { SchemaProps: spec.SchemaProps{ Description: \"tcpTimeout is the timeout value used for idle IPVS TCP sessions. The default value is 0, which preserves the current timeout value on the system.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"tcpFinTimeout\": { SchemaProps: spec.SchemaProps{ Description: \"tcpFinTimeout is the timeout value used for IPVS TCP sessions after receiving a FIN. The default value is 0, which preserves the current timeout value on the system.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"udpTimeout\": { SchemaProps: spec.SchemaProps{ Description: \"udpTimeout is the timeout value used for IPVS UDP packets. The default value is 0, which preserves the current timeout value on the system.\", Default:     0, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, }, Required: []string{\"syncPeriod\", \"minSyncPeriod\", \"scheduler\", \"excludeCIDRs\", \"strictARP\", \"tcpTimeout\", \"tcpFinTimeout\", \"udpTimeout\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"}, } } func schema_k8sio_kube_proxy_config_v1alpha1_KubeProxyWinkernelConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"KubeProxyWinkernelConfiguration contains Windows/HNS settings for the Kubernetes proxy server.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"networkName\": { SchemaProps: spec.SchemaProps{ Description: \"networkName is the name of the network kube-proxy will use to create endpoints and policies\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"sourceVip\": { SchemaProps: spec.SchemaProps{ Description: \"sourceVip is the IP address of the source VIP endoint used for NAT when loadbalancing\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"enableDSR\": { SchemaProps: spec.SchemaProps{ Description: \"enableDSR tells kube-proxy whether HNS policies should be created with DSR\", Default:     false, Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"networkName\", \"sourceVip\", \"enableDSR\"}, }, }, } } func schema_k8sio_kube_scheduler_config_v1beta2_DefaultPreemptionArgs(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DefaultPreemptionArgs holds arguments used to configure the DefaultPreemption plugin.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"minCandidateNodesPercentage\": { SchemaProps: spec.SchemaProps{ Description: \"MinCandidateNodesPercentage is the minimum number of candidates to shortlist when dry running preemption as a percentage of number of nodes. Must be in the range [0, 100]. Defaults to 10% of the cluster size if unspecified.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"minCandidateNodesAbsolute\": { SchemaProps: spec.SchemaProps{ Description: \"MinCandidateNodesAbsolute is the absolute minimum number of candidates to shortlist. The likely number of candidates enumerated for dry running preemption is given by the formula: numCandidates = max(numNodes * minCandidateNodesPercentage, minCandidateNodesAbsolute) We say \"likely\" because there are other factors such as PDB violations that play a role in the number of candidates shortlisted. Must be at least 0 nodes. Defaults to 100 nodes if unspecified.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_k8sio_kube_scheduler_config_v1beta2_Extender(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Extender 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.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"urlPrefix\": { SchemaProps: spec.SchemaProps{ Description: \"URLPrefix at which the extender is available\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"filterVerb\": { SchemaProps: spec.SchemaProps{ Description: \"Verb for the filter call, empty if not supported. This verb is appended to the URLPrefix when issuing the filter call to extender.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"preemptVerb\": { SchemaProps: spec.SchemaProps{ Description: \"Verb for the preempt call, empty if not supported. This verb is appended to the URLPrefix when issuing the preempt call to extender.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"prioritizeVerb\": { SchemaProps: spec.SchemaProps{ Description: \"Verb for the prioritize call, empty if not supported. This verb is appended to the URLPrefix when issuing the prioritize call to extender.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"weight\": { SchemaProps: spec.SchemaProps{ Description: \"The numeric multiplier for the node scores that the prioritize call generates. The weight should be a positive integer\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"bindVerb\": { SchemaProps: spec.SchemaProps{ Description: \"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.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"enableHTTPS\": { SchemaProps: spec.SchemaProps{ Description: \"EnableHTTPS specifies whether https should be used to communicate with the extender\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"tlsConfig\": { SchemaProps: spec.SchemaProps{ Description: \"TLSConfig specifies the transport layer security config\", Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta2.ExtenderTLSConfig\"), }, }, \"httpTimeout\": { SchemaProps: spec.SchemaProps{ Description: \"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.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"nodeCacheCapable\": { SchemaProps: spec.SchemaProps{ Description: \"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\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"managedResources\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"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 Bindn  (if the extender is the binder) phases iff the pod requests at leastn  one of the extended resources in this list. If empty or unspecified,n  all pods will be sent to this extender.n- If IgnoredByScheduler is set to true for a resource, kube-schedulern  will skip checking the resource in predicates.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta2.ExtenderManagedResource\"), }, }, }, }, }, \"ignorable\": { SchemaProps: spec.SchemaProps{ Description: \"Ignorable specifies if the extender is ignorable, i.e. scheduling should not fail when the extender returns an error or is not reachable.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"urlPrefix\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\", \"k8s.io/kube-scheduler/config/v1beta2.ExtenderManagedResource\", \"k8s.io/kube-scheduler/config/v1beta2.ExtenderTLSConfig\"}, } } func schema_k8sio_kube_scheduler_config_v1beta2_ExtenderManagedResource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExtenderManagedResource describes the arguments of extended resources managed by an extender.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the extended resource name.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ignoredByScheduler\": { SchemaProps: spec.SchemaProps{ Description: \"IgnoredByScheduler indicates whether kube-scheduler should ignore this resource when applying predicates.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_kube_scheduler_config_v1beta2_ExtenderTLSConfig(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExtenderTLSConfig contains settings to enable TLS with extender\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"insecure\": { SchemaProps: spec.SchemaProps{ Description: \"Server should be accessed without verifying the TLS certificate. For testing only.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"serverName\": { SchemaProps: spec.SchemaProps{ Description: \"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.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"certFile\": { SchemaProps: spec.SchemaProps{ Description: \"Server requires TLS client certificate authentication\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"keyFile\": { SchemaProps: spec.SchemaProps{ Description: \"Server requires TLS client certificate authentication\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"caFile\": { SchemaProps: spec.SchemaProps{ Description: \"Trusted root certificates for server\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"certData\": { SchemaProps: spec.SchemaProps{ Description: \"CertData holds PEM-encoded bytes (typically read from a client certificate file). CertData takes precedence over CertFile\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, \"keyData\": { SchemaProps: spec.SchemaProps{ Description: \"KeyData holds PEM-encoded bytes (typically read from a client certificate key file). KeyData takes precedence over KeyFile\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, \"caData\": { SchemaProps: spec.SchemaProps{ Description: \"CAData holds PEM-encoded bytes (typically read from a root certificates bundle). CAData takes precedence over CAFile\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, }, }, }, } } func schema_k8sio_kube_scheduler_config_v1beta2_InterPodAffinityArgs(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"InterPodAffinityArgs holds arguments used to configure the InterPodAffinity plugin.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"hardPodAffinityWeight\": { SchemaProps: spec.SchemaProps{ Description: \"HardPodAffinityWeight is the scoring weight for existing pods with a matching hard affinity to the incoming pod.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_k8sio_kube_scheduler_config_v1beta2_KubeSchedulerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"KubeSchedulerConfiguration configures a scheduler\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"parallelism\": { SchemaProps: spec.SchemaProps{ Description: \"Parallelism defines the amount of parallelism in algorithms for scheduling a Pods. Must be greater than 0. Defaults to 16\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"leaderElection\": { SchemaProps: spec.SchemaProps{ Description: \"LeaderElection defines the configuration of leader election client.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/component-base/config/v1alpha1.LeaderElectionConfiguration\"), }, }, \"clientConnection\": { SchemaProps: spec.SchemaProps{ Description: \"ClientConnection specifies the kubeconfig file and client connection settings for the proxy server to use when communicating with the apiserver.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/component-base/config/v1alpha1.ClientConnectionConfiguration\"), }, }, \"healthzBindAddress\": { SchemaProps: spec.SchemaProps{ Description: \"Note: Both HealthzBindAddress and MetricsBindAddress fields are deprecated. Only empty address or port 0 is allowed. Anything else will fail validation. HealthzBindAddress is the IP address and port for the health check server to serve on.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metricsBindAddress\": { SchemaProps: spec.SchemaProps{ Description: \"MetricsBindAddress is the IP address and port for the metrics server to serve on.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"enableProfiling\": { SchemaProps: spec.SchemaProps{ Description: \"enableProfiling enables profiling via web interface host:port/debug/pprof/\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"enableContentionProfiling\": { SchemaProps: spec.SchemaProps{ Description: \"enableContentionProfiling enables lock contention profiling, if enableProfiling is true.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"percentageOfNodesToScore\": { SchemaProps: spec.SchemaProps{ Description: \"PercentageOfNodesToScore is the percentage of all nodes that once found feasible for running a pod, the scheduler stops its search for more feasible nodes in the cluster. This helps improve scheduler's performance. Scheduler always tries to find at least \"minFeasibleNodesToFind\" feasible nodes no matter what the value of this flag is. Example: if the cluster size is 500 nodes and the value of this flag is 30, then scheduler stops finding further feasible nodes once it finds 150 feasible ones. When the value is 0, default percentage (5%--50% based on the size of the cluster) of the nodes will be scored.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"podInitialBackoffSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"PodInitialBackoffSeconds is the initial backoff for unschedulable pods. If specified, it must be greater than 0. If this value is null, the default value (1s) will be used.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"podMaxBackoffSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"PodMaxBackoffSeconds is the max backoff for unschedulable pods. If specified, it must be greater than podInitialBackoffSeconds. If this value is null, the default value (10s) will be used.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"profiles\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"schedulerName\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Profiles are scheduling profiles that kube-scheduler supports. Pods can choose to be scheduled under a particular profile by setting its associated scheduler name. Pods that don't specify any scheduler name are scheduled with the \"default-scheduler\" profile, if present here.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta2.KubeSchedulerProfile\"), }, }, }, }, }, \"extenders\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Extenders are the list of scheduler extenders, each holding the values of how to communicate with the extender. These extenders are shared by all scheduler profiles.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta2.Extender\"), }, }, }, }, }, }, Required: []string{\"leaderElection\", \"clientConnection\"}, }, }, Dependencies: []string{ \"k8s.io/component-base/config/v1alpha1.ClientConnectionConfiguration\", \"k8s.io/component-base/config/v1alpha1.LeaderElectionConfiguration\", \"k8s.io/kube-scheduler/config/v1beta2.Extender\", \"k8s.io/kube-scheduler/config/v1beta2.KubeSchedulerProfile\"}, } } func schema_k8sio_kube_scheduler_config_v1beta2_KubeSchedulerProfile(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"KubeSchedulerProfile is a scheduling profile.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"schedulerName\": { SchemaProps: spec.SchemaProps{ Description: \"SchedulerName is the name of the scheduler associated to this profile. If SchedulerName matches with the pod's \"spec.schedulerName\", then the pod is scheduled with this profile.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"plugins\": { SchemaProps: spec.SchemaProps{ Description: \"Plugins specify the set of plugins that should be enabled or disabled. Enabled plugins are the ones that should be enabled in addition to the default plugins. Disabled plugins are any of the default plugins that should be disabled. When no enabled or disabled plugin is specified for an extension point, default plugins for that extension point will be used if there is any. If a QueueSort plugin is specified, the same QueueSort Plugin and PluginConfig must be specified for all profiles.\", Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta2.Plugins\"), }, }, \"pluginConfig\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"name\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"PluginConfig is an optional set of custom plugin arguments for each plugin. Omitting config args for a plugin is equivalent to using the default config for that plugin.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta2.PluginConfig\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/kube-scheduler/config/v1beta2.PluginConfig\", \"k8s.io/kube-scheduler/config/v1beta2.Plugins\"}, } } func schema_k8sio_kube_scheduler_config_v1beta2_NodeAffinityArgs(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeAffinityArgs holds arguments to configure the NodeAffinity plugin.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"addedAffinity\": { SchemaProps: spec.SchemaProps{ Description: \"AddedAffinity is applied to all Pods additionally to the NodeAffinity specified in the PodSpec. That is, Nodes need to satisfy AddedAffinity AND .spec.NodeAffinity. AddedAffinity is empty by default (all Nodes match). When AddedAffinity is used, some Pods with affinity requirements that match a specific Node (such as Daemonset Pods) might remain unschedulable.\", Ref:         ref(\"k8s.io/api/core/v1.NodeAffinity\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.NodeAffinity\"}, } } func schema_k8sio_kube_scheduler_config_v1beta2_NodeResourcesBalancedAllocationArgs(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeResourcesBalancedAllocationArgs holds arguments used to configure NodeResourcesBalancedAllocation plugin.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resources\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"name\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Resources to be managed, the default is \"cpu\" and \"memory\" if not specified.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta2.ResourceSpec\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/kube-scheduler/config/v1beta2.ResourceSpec\"}, } } func schema_k8sio_kube_scheduler_config_v1beta2_NodeResourcesFitArgs(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeResourcesFitArgs holds arguments used to configure the NodeResourcesFit plugin.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ignoredResources\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"IgnoredResources is the list of resources that NodeResources fit filter should ignore. This doesn't apply to scoring.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"ignoredResourceGroups\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"IgnoredResourceGroups defines the list of resource groups that NodeResources fit filter should ignore. e.g. if group is [\"example.com\"], it will ignore all resource names that begin with \"example.com\", such as \"example.com/aaa\" and \"example.com/bbb\". A resource group name can't contain '/'. This doesn't apply to scoring.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"scoringStrategy\": { SchemaProps: spec.SchemaProps{ Description: \"ScoringStrategy selects the node resource scoring strategy. The default strategy is LeastAllocated with an equal \"cpu\" and \"memory\" weight.\", Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta2.ScoringStrategy\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/kube-scheduler/config/v1beta2.ScoringStrategy\"}, } } func schema_k8sio_kube_scheduler_config_v1beta2_Plugin(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Plugin specifies a plugin name and its weight when applicable. Weight is used only for Score plugins.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name defines the name of plugin\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"weight\": { SchemaProps: spec.SchemaProps{ Description: \"Weight defines the weight of plugin, only used for Score plugins.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_kube_scheduler_config_v1beta2_PluginConfig(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PluginConfig specifies arguments that should be passed to a plugin at the time of initialization. A plugin that is invoked at multiple extension points is initialized once. Args can have arbitrary structure. It is up to the plugin to process these Args.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name defines the name of plugin being configured\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"args\": { SchemaProps: spec.SchemaProps{ Description: \"Args defines the arguments passed to the plugins at the time of initialization. Args can have arbitrary structure.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/runtime.RawExtension\"), }, }, }, Required: []string{\"name\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/runtime.RawExtension\"}, } } func schema_k8sio_kube_scheduler_config_v1beta2_PluginSet(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PluginSet specifies enabled and disabled plugins for an extension point. If an array is empty, missing, or nil, default plugins at that extension point will be used.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"enabled\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Enabled specifies plugins that should be enabled in addition to default plugins. If the default plugin is also configured in the scheduler config file, the weight of plugin will be overridden accordingly. These are called after default plugins and in the same order specified here.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta2.Plugin\"), }, }, }, }, }, \"disabled\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"name\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Disabled specifies default plugins that should be disabled. When all default plugins need to be disabled, an array containing only one \"*\" should be provided.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta2.Plugin\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/kube-scheduler/config/v1beta2.Plugin\"}, } } func schema_k8sio_kube_scheduler_config_v1beta2_Plugins(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Plugins include multiple extension points. When specified, the list of plugins for a particular extension point are the only ones enabled. If an extension point is omitted from the config, then the default set of plugins is used for that extension point. Enabled plugins are called in the order specified here, after default plugins. If they need to be invoked before default plugins, default plugins must be disabled and re-enabled here in desired order.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"queueSort\": { SchemaProps: spec.SchemaProps{ Description: \"QueueSort is a list of plugins that should be invoked when sorting pods in the scheduling queue.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta2.PluginSet\"), }, }, \"preFilter\": { SchemaProps: spec.SchemaProps{ Description: \"PreFilter is a list of plugins that should be invoked at \"PreFilter\" extension point of the scheduling framework.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta2.PluginSet\"), }, }, \"filter\": { SchemaProps: spec.SchemaProps{ Description: \"Filter is a list of plugins that should be invoked when filtering out nodes that cannot run the Pod.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta2.PluginSet\"), }, }, \"postFilter\": { SchemaProps: spec.SchemaProps{ Description: \"PostFilter is a list of plugins that are invoked after filtering phase, but only when no feasible nodes were found for the pod.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta2.PluginSet\"), }, }, \"preScore\": { SchemaProps: spec.SchemaProps{ Description: \"PreScore is a list of plugins that are invoked before scoring.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta2.PluginSet\"), }, }, \"score\": { SchemaProps: spec.SchemaProps{ Description: \"Score is a list of plugins that should be invoked when ranking nodes that have passed the filtering phase.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta2.PluginSet\"), }, }, \"reserve\": { SchemaProps: spec.SchemaProps{ Description: \"Reserve is a list of plugins invoked when reserving/unreserving resources after a node is assigned to run the pod.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta2.PluginSet\"), }, }, \"permit\": { SchemaProps: spec.SchemaProps{ Description: \"Permit is a list of plugins that control binding of a Pod. These plugins can prevent or delay binding of a Pod.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta2.PluginSet\"), }, }, \"preBind\": { SchemaProps: spec.SchemaProps{ Description: \"PreBind is a list of plugins that should be invoked before a pod is bound.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta2.PluginSet\"), }, }, \"bind\": { SchemaProps: spec.SchemaProps{ Description: \"Bind is a list of plugins that should be invoked at \"Bind\" extension point of the scheduling framework. The scheduler call these plugins in order. Scheduler skips the rest of these plugins as soon as one returns success.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta2.PluginSet\"), }, }, \"postBind\": { SchemaProps: spec.SchemaProps{ Description: \"PostBind is a list of plugins that should be invoked after a pod is successfully bound.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta2.PluginSet\"), }, }, \"multiPoint\": { SchemaProps: spec.SchemaProps{ Description: \"MultiPoint is a simplified config section to enable plugins for all valid extension points.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta2.PluginSet\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/kube-scheduler/config/v1beta2.PluginSet\"}, } } func schema_k8sio_kube_scheduler_config_v1beta2_PodTopologySpreadArgs(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodTopologySpreadArgs holds arguments used to configure the PodTopologySpread plugin.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"defaultConstraints\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"DefaultConstraints defines topology spread constraints to be applied to Pods that don't define any in `pod.spec.topologySpreadConstraints`. `.defaultConstraints[*].labelSelectors` must be empty, as they are deduced from the Pod's membership to Services, ReplicationControllers, ReplicaSets or StatefulSets. When not empty, .defaultingType must be \"List\".\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.TopologySpreadConstraint\"), }, }, }, }, }, \"defaultingType\": { SchemaProps: spec.SchemaProps{ Description: \"DefaultingType determines how .defaultConstraints are deduced. Can be one of \"System\" or \"List\".nn- \"System\": Use kubernetes defined constraints that spread Pods amongn  Nodes and Zones.n- \"List\": Use constraints defined in .defaultConstraints.nnDefaults to \"System\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.TopologySpreadConstraint\"}, } } func schema_k8sio_kube_scheduler_config_v1beta2_RequestedToCapacityRatioParam(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RequestedToCapacityRatioParam define RequestedToCapacityRatio parameters\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"shape\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Shape is a list of points defining the scoring function shape.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta2.UtilizationShapePoint\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/kube-scheduler/config/v1beta2.UtilizationShapePoint\"}, } } func schema_k8sio_kube_scheduler_config_v1beta2_ResourceSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceSpec represents a single resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the resource.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"weight\": { SchemaProps: spec.SchemaProps{ Description: \"Weight of the resource.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_kube_scheduler_config_v1beta2_ScoringStrategy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ScoringStrategy define ScoringStrategyType for node resource plugin\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type selects which strategy to run.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resources\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"topologyKey\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Resources to consider when scoring. The default resource set includes \"cpu\" and \"memory\" with an equal weight. Allowed weights go from 1 to 100. Weight defaults to 1 if not specified or explicitly set to 0.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta2.ResourceSpec\"), }, }, }, }, }, \"requestedToCapacityRatio\": { SchemaProps: spec.SchemaProps{ Description: \"Arguments specific to RequestedToCapacityRatio strategy.\", Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta2.RequestedToCapacityRatioParam\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/kube-scheduler/config/v1beta2.RequestedToCapacityRatioParam\", \"k8s.io/kube-scheduler/config/v1beta2.ResourceSpec\"}, } } func schema_k8sio_kube_scheduler_config_v1beta2_UtilizationShapePoint(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"UtilizationShapePoint represents single point of priority function shape.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"utilization\": { SchemaProps: spec.SchemaProps{ Description: \"Utilization (x axis). Valid values are 0 to 100. Fully utilized node maps to 100.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"score\": { SchemaProps: spec.SchemaProps{ Description: \"Score assigned to given utilization (y axis). Valid values are 0 to 10.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"utilization\", \"score\"}, }, }, } } func schema_k8sio_kube_scheduler_config_v1beta2_VolumeBindingArgs(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeBindingArgs holds arguments used to configure the VolumeBinding plugin.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"bindTimeoutSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"BindTimeoutSeconds is the timeout in seconds in volume binding operation. Value must be non-negative integer. The value zero indicates no waiting. If this value is nil, the default value (600) will be used.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"shape\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Shape specifies the points defining the score function shape, which is used to score nodes based on the utilization of statically provisioned PVs. The utilization is calculated by dividing the total requested storage of the pod by the total capacity of feasible PVs on each node. Each point contains utilization (ranges from 0 to 100) and its associated score (ranges from 0 to 10). You can turn the priority by specifying different scores for different utilization numbers. The default shape points are: 1) 0 for 0 utilization 2) 10 for 100 utilization All points must be sorted in increasing order by utilization.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta2.UtilizationShapePoint\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/kube-scheduler/config/v1beta2.UtilizationShapePoint\"}, } } func schema_k8sio_kube_scheduler_config_v1beta3_DefaultPreemptionArgs(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"DefaultPreemptionArgs holds arguments used to configure the DefaultPreemption plugin.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"minCandidateNodesPercentage\": { SchemaProps: spec.SchemaProps{ Description: \"MinCandidateNodesPercentage is the minimum number of candidates to shortlist when dry running preemption as a percentage of number of nodes. Must be in the range [0, 100]. Defaults to 10% of the cluster size if unspecified.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"minCandidateNodesAbsolute\": { SchemaProps: spec.SchemaProps{ Description: \"MinCandidateNodesAbsolute is the absolute minimum number of candidates to shortlist. The likely number of candidates enumerated for dry running preemption is given by the formula: numCandidates = max(numNodes * minCandidateNodesPercentage, minCandidateNodesAbsolute) We say \"likely\" because there are other factors such as PDB violations that play a role in the number of candidates shortlisted. Must be at least 0 nodes. Defaults to 100 nodes if unspecified.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_k8sio_kube_scheduler_config_v1beta3_Extender(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Extender 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.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"urlPrefix\": { SchemaProps: spec.SchemaProps{ Description: \"URLPrefix at which the extender is available\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"filterVerb\": { SchemaProps: spec.SchemaProps{ Description: \"Verb for the filter call, empty if not supported. This verb is appended to the URLPrefix when issuing the filter call to extender.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"preemptVerb\": { SchemaProps: spec.SchemaProps{ Description: \"Verb for the preempt call, empty if not supported. This verb is appended to the URLPrefix when issuing the preempt call to extender.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"prioritizeVerb\": { SchemaProps: spec.SchemaProps{ Description: \"Verb for the prioritize call, empty if not supported. This verb is appended to the URLPrefix when issuing the prioritize call to extender.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"weight\": { SchemaProps: spec.SchemaProps{ Description: \"The numeric multiplier for the node scores that the prioritize call generates. The weight should be a positive integer\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"bindVerb\": { SchemaProps: spec.SchemaProps{ Description: \"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.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"enableHTTPS\": { SchemaProps: spec.SchemaProps{ Description: \"EnableHTTPS specifies whether https should be used to communicate with the extender\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"tlsConfig\": { SchemaProps: spec.SchemaProps{ Description: \"TLSConfig specifies the transport layer security config\", Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta3.ExtenderTLSConfig\"), }, }, \"httpTimeout\": { SchemaProps: spec.SchemaProps{ Description: \"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.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"nodeCacheCapable\": { SchemaProps: spec.SchemaProps{ Description: \"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\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"managedResources\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"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 Bindn  (if the extender is the binder) phases iff the pod requests at leastn  one of the extended resources in this list. If empty or unspecified,n  all pods will be sent to this extender.n- If IgnoredByScheduler is set to true for a resource, kube-schedulern  will skip checking the resource in predicates.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta3.ExtenderManagedResource\"), }, }, }, }, }, \"ignorable\": { SchemaProps: spec.SchemaProps{ Description: \"Ignorable specifies if the extender is ignorable, i.e. scheduling should not fail when the extender returns an error or is not reachable.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"urlPrefix\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\", \"k8s.io/kube-scheduler/config/v1beta3.ExtenderManagedResource\", \"k8s.io/kube-scheduler/config/v1beta3.ExtenderTLSConfig\"}, } } func schema_k8sio_kube_scheduler_config_v1beta3_ExtenderManagedResource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExtenderManagedResource describes the arguments of extended resources managed by an extender.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name is the extended resource name.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ignoredByScheduler\": { SchemaProps: spec.SchemaProps{ Description: \"IgnoredByScheduler indicates whether kube-scheduler should ignore this resource when applying predicates.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_kube_scheduler_config_v1beta3_ExtenderTLSConfig(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExtenderTLSConfig contains settings to enable TLS with extender\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"insecure\": { SchemaProps: spec.SchemaProps{ Description: \"Server should be accessed without verifying the TLS certificate. For testing only.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"serverName\": { SchemaProps: spec.SchemaProps{ Description: \"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.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"certFile\": { SchemaProps: spec.SchemaProps{ Description: \"Server requires TLS client certificate authentication\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"keyFile\": { SchemaProps: spec.SchemaProps{ Description: \"Server requires TLS client certificate authentication\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"caFile\": { SchemaProps: spec.SchemaProps{ Description: \"Trusted root certificates for server\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"certData\": { SchemaProps: spec.SchemaProps{ Description: \"CertData holds PEM-encoded bytes (typically read from a client certificate file). CertData takes precedence over CertFile\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, \"keyData\": { SchemaProps: spec.SchemaProps{ Description: \"KeyData holds PEM-encoded bytes (typically read from a client certificate key file). KeyData takes precedence over KeyFile\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, \"caData\": { SchemaProps: spec.SchemaProps{ Description: \"CAData holds PEM-encoded bytes (typically read from a root certificates bundle). CAData takes precedence over CAFile\", Type:        []string{\"string\"}, Format:      \"byte\", }, }, }, }, }, } } func schema_k8sio_kube_scheduler_config_v1beta3_InterPodAffinityArgs(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"InterPodAffinityArgs holds arguments used to configure the InterPodAffinity plugin.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"hardPodAffinityWeight\": { SchemaProps: spec.SchemaProps{ Description: \"HardPodAffinityWeight is the scoring weight for existing pods with a matching hard affinity to the incoming pod.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, }, }, } } func schema_k8sio_kube_scheduler_config_v1beta3_KubeSchedulerConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"KubeSchedulerConfiguration configures a scheduler\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"parallelism\": { SchemaProps: spec.SchemaProps{ Description: \"Parallelism defines the amount of parallelism in algorithms for scheduling a Pods. Must be greater than 0. Defaults to 16\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"leaderElection\": { SchemaProps: spec.SchemaProps{ Description: \"LeaderElection defines the configuration of leader election client.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/component-base/config/v1alpha1.LeaderElectionConfiguration\"), }, }, \"clientConnection\": { SchemaProps: spec.SchemaProps{ Description: \"ClientConnection specifies the kubeconfig file and client connection settings for the proxy server to use when communicating with the apiserver.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/component-base/config/v1alpha1.ClientConnectionConfiguration\"), }, }, \"enableProfiling\": { SchemaProps: spec.SchemaProps{ Description: \"enableProfiling enables profiling via web interface host:port/debug/pprof/\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"enableContentionProfiling\": { SchemaProps: spec.SchemaProps{ Description: \"enableContentionProfiling enables lock contention profiling, if enableProfiling is true.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"percentageOfNodesToScore\": { SchemaProps: spec.SchemaProps{ Description: \"PercentageOfNodesToScore is the percentage of all nodes that once found feasible for running a pod, the scheduler stops its search for more feasible nodes in the cluster. This helps improve scheduler's performance. Scheduler always tries to find at least \"minFeasibleNodesToFind\" feasible nodes no matter what the value of this flag is. Example: if the cluster size is 500 nodes and the value of this flag is 30, then scheduler stops finding further feasible nodes once it finds 150 feasible ones. When the value is 0, default percentage (5%--50% based on the size of the cluster) of the nodes will be scored.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"podInitialBackoffSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"PodInitialBackoffSeconds is the initial backoff for unschedulable pods. If specified, it must be greater than 0. If this value is null, the default value (1s) will be used.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"podMaxBackoffSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"PodMaxBackoffSeconds is the max backoff for unschedulable pods. If specified, it must be greater than podInitialBackoffSeconds. If this value is null, the default value (10s) will be used.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"profiles\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"schedulerName\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Profiles are scheduling profiles that kube-scheduler supports. Pods can choose to be scheduled under a particular profile by setting its associated scheduler name. Pods that don't specify any scheduler name are scheduled with the \"default-scheduler\" profile, if present here.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta3.KubeSchedulerProfile\"), }, }, }, }, }, \"extenders\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"set\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Extenders are the list of scheduler extenders, each holding the values of how to communicate with the extender. These extenders are shared by all scheduler profiles.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta3.Extender\"), }, }, }, }, }, }, Required: []string{\"leaderElection\", \"clientConnection\"}, }, }, Dependencies: []string{ \"k8s.io/component-base/config/v1alpha1.ClientConnectionConfiguration\", \"k8s.io/component-base/config/v1alpha1.LeaderElectionConfiguration\", \"k8s.io/kube-scheduler/config/v1beta3.Extender\", \"k8s.io/kube-scheduler/config/v1beta3.KubeSchedulerProfile\"}, } } func schema_k8sio_kube_scheduler_config_v1beta3_KubeSchedulerProfile(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"KubeSchedulerProfile is a scheduling profile.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"schedulerName\": { SchemaProps: spec.SchemaProps{ Description: \"SchedulerName is the name of the scheduler associated to this profile. If SchedulerName matches with the pod's \"spec.schedulerName\", then the pod is scheduled with this profile.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"plugins\": { SchemaProps: spec.SchemaProps{ Description: \"Plugins specify the set of plugins that should be enabled or disabled. Enabled plugins are the ones that should be enabled in addition to the default plugins. Disabled plugins are any of the default plugins that should be disabled. When no enabled or disabled plugin is specified for an extension point, default plugins for that extension point will be used if there is any. If a QueueSort plugin is specified, the same QueueSort Plugin and PluginConfig must be specified for all profiles.\", Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta3.Plugins\"), }, }, \"pluginConfig\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"name\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"PluginConfig is an optional set of custom plugin arguments for each plugin. Omitting config args for a plugin is equivalent to using the default config for that plugin.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta3.PluginConfig\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/kube-scheduler/config/v1beta3.PluginConfig\", \"k8s.io/kube-scheduler/config/v1beta3.Plugins\"}, } } func schema_k8sio_kube_scheduler_config_v1beta3_NodeAffinityArgs(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeAffinityArgs holds arguments to configure the NodeAffinity plugin.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"addedAffinity\": { SchemaProps: spec.SchemaProps{ Description: \"AddedAffinity is applied to all Pods additionally to the NodeAffinity specified in the PodSpec. That is, Nodes need to satisfy AddedAffinity AND .spec.NodeAffinity. AddedAffinity is empty by default (all Nodes match). When AddedAffinity is used, some Pods with affinity requirements that match a specific Node (such as Daemonset Pods) might remain unschedulable.\", Ref:         ref(\"k8s.io/api/core/v1.NodeAffinity\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.NodeAffinity\"}, } } func schema_k8sio_kube_scheduler_config_v1beta3_NodeResourcesBalancedAllocationArgs(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeResourcesBalancedAllocationArgs holds arguments used to configure NodeResourcesBalancedAllocation plugin.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resources\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"name\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Resources to be managed, the default is \"cpu\" and \"memory\" if not specified.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta3.ResourceSpec\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/kube-scheduler/config/v1beta3.ResourceSpec\"}, } } func schema_k8sio_kube_scheduler_config_v1beta3_NodeResourcesFitArgs(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeResourcesFitArgs holds arguments used to configure the NodeResourcesFit plugin.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"ignoredResources\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"IgnoredResources is the list of resources that NodeResources fit filter should ignore. This doesn't apply to scoring.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"ignoredResourceGroups\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"IgnoredResourceGroups defines the list of resource groups that NodeResources fit filter should ignore. e.g. if group is [\"example.com\"], it will ignore all resource names that begin with \"example.com\", such as \"example.com/aaa\" and \"example.com/bbb\". A resource group name can't contain '/'. This doesn't apply to scoring.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"scoringStrategy\": { SchemaProps: spec.SchemaProps{ Description: \"ScoringStrategy selects the node resource scoring strategy. The default strategy is LeastAllocated with an equal \"cpu\" and \"memory\" weight.\", Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta3.ScoringStrategy\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/kube-scheduler/config/v1beta3.ScoringStrategy\"}, } } func schema_k8sio_kube_scheduler_config_v1beta3_Plugin(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Plugin specifies a plugin name and its weight when applicable. Weight is used only for Score plugins.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name defines the name of plugin\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"weight\": { SchemaProps: spec.SchemaProps{ Description: \"Weight defines the weight of plugin, only used for Score plugins.\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_kube_scheduler_config_v1beta3_PluginConfig(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PluginConfig specifies arguments that should be passed to a plugin at the time of initialization. A plugin that is invoked at multiple extension points is initialized once. Args can have arbitrary structure. It is up to the plugin to process these Args.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name defines the name of plugin being configured\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"args\": { SchemaProps: spec.SchemaProps{ Description: \"Args defines the arguments passed to the plugins at the time of initialization. Args can have arbitrary structure.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/runtime.RawExtension\"), }, }, }, Required: []string{\"name\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/runtime.RawExtension\"}, } } func schema_k8sio_kube_scheduler_config_v1beta3_PluginSet(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PluginSet specifies enabled and disabled plugins for an extension point. If an array is empty, missing, or nil, default plugins at that extension point will be used.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"enabled\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Enabled specifies plugins that should be enabled in addition to default plugins. If the default plugin is also configured in the scheduler config file, the weight of plugin will be overridden accordingly. These are called after default plugins and in the same order specified here.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta3.Plugin\"), }, }, }, }, }, \"disabled\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"name\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Disabled specifies default plugins that should be disabled. When all default plugins need to be disabled, an array containing only one \"*\" should be provided.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta3.Plugin\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/kube-scheduler/config/v1beta3.Plugin\"}, } } func schema_k8sio_kube_scheduler_config_v1beta3_Plugins(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Plugins include multiple extension points. When specified, the list of plugins for a particular extension point are the only ones enabled. If an extension point is omitted from the config, then the default set of plugins is used for that extension point. Enabled plugins are called in the order specified here, after default plugins. If they need to be invoked before default plugins, default plugins must be disabled and re-enabled here in desired order.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"queueSort\": { SchemaProps: spec.SchemaProps{ Description: \"QueueSort is a list of plugins that should be invoked when sorting pods in the scheduling queue.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta3.PluginSet\"), }, }, \"preFilter\": { SchemaProps: spec.SchemaProps{ Description: \"PreFilter is a list of plugins that should be invoked at \"PreFilter\" extension point of the scheduling framework.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta3.PluginSet\"), }, }, \"filter\": { SchemaProps: spec.SchemaProps{ Description: \"Filter is a list of plugins that should be invoked when filtering out nodes that cannot run the Pod.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta3.PluginSet\"), }, }, \"postFilter\": { SchemaProps: spec.SchemaProps{ Description: \"PostFilter is a list of plugins that are invoked after filtering phase, but only when no feasible nodes were found for the pod.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta3.PluginSet\"), }, }, \"preScore\": { SchemaProps: spec.SchemaProps{ Description: \"PreScore is a list of plugins that are invoked before scoring.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta3.PluginSet\"), }, }, \"score\": { SchemaProps: spec.SchemaProps{ Description: \"Score is a list of plugins that should be invoked when ranking nodes that have passed the filtering phase.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta3.PluginSet\"), }, }, \"reserve\": { SchemaProps: spec.SchemaProps{ Description: \"Reserve is a list of plugins invoked when reserving/unreserving resources after a node is assigned to run the pod.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta3.PluginSet\"), }, }, \"permit\": { SchemaProps: spec.SchemaProps{ Description: \"Permit is a list of plugins that control binding of a Pod. These plugins can prevent or delay binding of a Pod.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta3.PluginSet\"), }, }, \"preBind\": { SchemaProps: spec.SchemaProps{ Description: \"PreBind is a list of plugins that should be invoked before a pod is bound.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta3.PluginSet\"), }, }, \"bind\": { SchemaProps: spec.SchemaProps{ Description: \"Bind is a list of plugins that should be invoked at \"Bind\" extension point of the scheduling framework. The scheduler call these plugins in order. Scheduler skips the rest of these plugins as soon as one returns success.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta3.PluginSet\"), }, }, \"postBind\": { SchemaProps: spec.SchemaProps{ Description: \"PostBind is a list of plugins that should be invoked after a pod is successfully bound.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta3.PluginSet\"), }, }, \"multiPoint\": { SchemaProps: spec.SchemaProps{ Description: \"MultiPoint is a simplified config section to enable plugins for all valid extension points. Plugins enabled through MultiPoint will automatically register for every individual extension point the plugin has implemented. Disabling a plugin through MultiPoint disables that behavior. The same is true for disabling \"*\" through MultiPoint (no default plugins will be automatically registered). Plugins can still be disabled through their individual extension points.nnIn terms of precedence, plugin config follows this basic hierarchyn  1. Specific extension pointsn  2. Explicitly configured MultiPoint pluginsn  3. The set of default plugins, as MultiPoint pluginsnThis implies that a higher precedence plugin will run first and overwrite any settings within MultiPoint. Explicitly user-configured plugins also take a higher precedence over default plugins. Within this hierarchy, an Enabled setting takes precedence over Disabled. For example, if a plugin is set in both `multiPoint.Enabled` and `multiPoint.Disabled`, the plugin will be enabled. Similarly, including `multiPoint.Disabled = '*'` and `multiPoint.Enabled = pluginA` will still register that specific plugin through MultiPoint. This follows the same behavior as all other extension point configurations.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta3.PluginSet\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/kube-scheduler/config/v1beta3.PluginSet\"}, } } func schema_k8sio_kube_scheduler_config_v1beta3_PodTopologySpreadArgs(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodTopologySpreadArgs holds arguments used to configure the PodTopologySpread plugin.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"defaultConstraints\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"DefaultConstraints defines topology spread constraints to be applied to Pods that don't define any in `pod.spec.topologySpreadConstraints`. `.defaultConstraints[*].labelSelectors` must be empty, as they are deduced from the Pod's membership to Services, ReplicationControllers, ReplicaSets or StatefulSets. When not empty, .defaultingType must be \"List\".\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.TopologySpreadConstraint\"), }, }, }, }, }, \"defaultingType\": { SchemaProps: spec.SchemaProps{ Description: \"DefaultingType determines how .defaultConstraints are deduced. Can be one of \"System\" or \"List\".nn- \"System\": Use kubernetes defined constraints that spread Pods amongn  Nodes and Zones.n- \"List\": Use constraints defined in .defaultConstraints.nnDefaults to \"System\".\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.TopologySpreadConstraint\"}, } } func schema_k8sio_kube_scheduler_config_v1beta3_RequestedToCapacityRatioParam(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"RequestedToCapacityRatioParam define RequestedToCapacityRatio parameters\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"shape\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Shape is a list of points defining the scoring function shape.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta3.UtilizationShapePoint\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/kube-scheduler/config/v1beta3.UtilizationShapePoint\"}, } } func schema_k8sio_kube_scheduler_config_v1beta3_ResourceSpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ResourceSpec represents a single resource.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Name of the resource.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"weight\": { SchemaProps: spec.SchemaProps{ Description: \"Weight of the resource.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, }, Required: []string{\"name\"}, }, }, } } func schema_k8sio_kube_scheduler_config_v1beta3_ScoringStrategy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ScoringStrategy define ScoringStrategyType for node resource plugin\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"type\": { SchemaProps: spec.SchemaProps{ Description: \"Type selects which strategy to run.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resources\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-map-keys\": []interface{}{ \"topologyKey\", }, \"x-kubernetes-list-type\": \"map\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Resources to consider when scoring. The default resource set includes \"cpu\" and \"memory\" with an equal weight. Allowed weights go from 1 to 100. Weight defaults to 1 if not specified or explicitly set to 0.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta3.ResourceSpec\"), }, }, }, }, }, \"requestedToCapacityRatio\": { SchemaProps: spec.SchemaProps{ Description: \"Arguments specific to RequestedToCapacityRatio strategy.\", Ref:         ref(\"k8s.io/kube-scheduler/config/v1beta3.RequestedToCapacityRatioParam\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/kube-scheduler/config/v1beta3.RequestedToCapacityRatioParam\", \"k8s.io/kube-scheduler/config/v1beta3.ResourceSpec\"}, } } func schema_k8sio_kube_scheduler_config_v1beta3_UtilizationShapePoint(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"UtilizationShapePoint represents single point of priority function shape.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"utilization\": { SchemaProps: spec.SchemaProps{ Description: \"Utilization (x axis). Valid values are 0 to 100. Fully utilized node maps to 100.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"score\": { SchemaProps: spec.SchemaProps{ Description: \"Score assigned to given utilization (y axis). Valid values are 0 to 10.\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, }, Required: []string{\"utilization\", \"score\"}, }, }, } } func schema_k8sio_kube_scheduler_config_v1beta3_VolumeBindingArgs(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"VolumeBindingArgs holds arguments used to configure the VolumeBinding plugin.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"bindTimeoutSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"BindTimeoutSeconds is the timeout in seconds in volume binding operation. Value must be non-negative integer. The value zero indicates no waiting. If this value is nil, the default value (600) will be used.\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"shape\": { VendorExtensible: spec.VendorExtensible{ Extensions: spec.Extensions{ \"x-kubernetes-list-type\": \"atomic\", }, }, SchemaProps: spec.SchemaProps{ Description: \"Shape specifies the points defining the score function shape, which is used to score nodes based on the utilization of statically provisioned PVs. The utilization is calculated by dividing the total requested storage of the pod by the total capacity of feasible PVs on each node. Each point contains utilization (ranges from 0 to 100) and its associated score (ranges from 0 to 10). You can turn the priority by specifying different scores for different utilization numbers. The default shape points are: 1) 0 for 0 utilization 2) 10 for 100 utilization All points must be sorted in increasing order by utilization.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kube-scheduler/config/v1beta3.UtilizationShapePoint\"), }, }, }, }, }, }, }, }, Dependencies: []string{ \"k8s.io/kube-scheduler/config/v1beta3.UtilizationShapePoint\"}, } } func schema_k8sio_kubelet_config_v1alpha1_CredentialProvider(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CredentialProvider represents an exec plugin to be invoked by the kubelet. The plugin is only invoked when an image being pulled matches the images handled by the plugin (see matchImages).\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the required name of the credential provider. It must match the name of the provider executable as seen by the kubelet. The executable must be in the kubelet's bin directory (set by the --image-credential-provider-bin-dir flag).\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"matchImages\": { SchemaProps: spec.SchemaProps{ Description: \"matchImages is a required list of strings used to match against images in order to determine if this provider should be invoked. If one of the strings matches the requested image from the kubelet, the plugin will be invoked and given a chance to provide credentials. Images are expected to contain the registry domain and URL path.nnEach entry in matchImages is a pattern which can optionally contain a port and a path. Globs can be used in the domain, but not in the port or the path. Globs are supported as subdomains like '*.k8s.io' or 'k8s.*.io', and top-level-domains such as 'k8s.*'. Matching partial subdomains like 'app*.k8s.io' is also supported. Each glob can only match a single subdomain segment, so *.io does not match *.k8s.io.nnA match exists between an image and a matchImage when all of the below are true: - Both contain the same number of domain parts and each part matches. - The URL path of an imageMatch must be a prefix of the target image URL path. - If the imageMatch contains a port, then the port must match in the image as well.nnExample values of matchImages:n  - 123456789.dkr.ecr.us-east-1.amazonaws.comn  - *.azurecr.ion  - gcr.ion  - *.*.registry.ion  - registry.io:8080/path\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"defaultCacheDuration\": { SchemaProps: spec.SchemaProps{ Description: \"defaultCacheDuration is the default duration the plugin will cache credentials in-memory if a cache duration is not provided in the plugin response. This field is required.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"Required input version of the exec CredentialProviderRequest. The returned CredentialProviderResponse MUST use the same encoding version as the input. Current supported values are: - credentialprovider.kubelet.k8s.io/v1alpha1\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"args\": { SchemaProps: spec.SchemaProps{ Description: \"Arguments to pass to the command when executing it.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"env\": { SchemaProps: spec.SchemaProps{ Description: \"Env defines additional environment variables to expose to the process. These are unioned with the host's environment, as well as variables client-go uses to pass argument to the plugin.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kubelet/config/v1alpha1.ExecEnvVar\"), }, }, }, }, }, }, Required: []string{\"name\", \"matchImages\", \"defaultCacheDuration\", \"apiVersion\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\", \"k8s.io/kubelet/config/v1alpha1.ExecEnvVar\"}, } } func schema_k8sio_kubelet_config_v1alpha1_CredentialProviderConfig(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"CredentialProviderConfig is the configuration containing information about each exec credential provider. Kubelet reads this configuration from disk and enables each provider as specified by the CredentialProvider type.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"providers\": { SchemaProps: spec.SchemaProps{ Description: \"providers is a list of credential provider plugins that will be enabled by the kubelet. Multiple providers may match against a single image, in which case credentials from all providers will be returned to the kubelet. If multiple providers are called for a single image, the results are combined. If providers return overlapping auth keys, the value from the provider earlier in this list is used.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kubelet/config/v1alpha1.CredentialProvider\"), }, }, }, }, }, }, Required: []string{\"providers\"}, }, }, Dependencies: []string{ \"k8s.io/kubelet/config/v1alpha1.CredentialProvider\"}, } } func schema_k8sio_kubelet_config_v1alpha1_ExecEnvVar(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExecEnvVar is used for setting environment variables when executing an exec-based credential plugin.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, \"value\": { SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, Required: []string{\"name\", \"value\"}, }, }, } } func schema_k8sio_kubelet_config_v1beta1_KubeletAnonymousAuthentication(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, Properties: map[string]spec.Schema{ \"enabled\": { SchemaProps: spec.SchemaProps{ Description: \"enabled allows anonymous requests to the kubelet server. Requests that are not rejected by another authentication method are treated as anonymous requests. Anonymous requests have a username of `system:anonymous`, and a group name of `system:unauthenticated`.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_kubelet_config_v1beta1_KubeletAuthentication(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, Properties: map[string]spec.Schema{ \"x509\": { SchemaProps: spec.SchemaProps{ Description: \"x509 contains settings related to x509 client certificate authentication.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kubelet/config/v1beta1.KubeletX509Authentication\"), }, }, \"webhook\": { SchemaProps: spec.SchemaProps{ Description: \"webhook contains settings related to webhook bearer token authentication.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kubelet/config/v1beta1.KubeletWebhookAuthentication\"), }, }, \"anonymous\": { SchemaProps: spec.SchemaProps{ Description: \"anonymous contains settings related to anonymous authentication.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kubelet/config/v1beta1.KubeletAnonymousAuthentication\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/kubelet/config/v1beta1.KubeletAnonymousAuthentication\", \"k8s.io/kubelet/config/v1beta1.KubeletWebhookAuthentication\", \"k8s.io/kubelet/config/v1beta1.KubeletX509Authentication\"}, } } func schema_k8sio_kubelet_config_v1beta1_KubeletAuthorization(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, Properties: map[string]spec.Schema{ \"mode\": { SchemaProps: spec.SchemaProps{ Description: \"mode is the authorization mode to apply to requests to the kubelet server. Valid values are `AlwaysAllow` and `Webhook`. Webhook mode uses the SubjectAccessReview API to determine authorization.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"webhook\": { SchemaProps: spec.SchemaProps{ Description: \"webhook contains settings related to Webhook authorization.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kubelet/config/v1beta1.KubeletWebhookAuthorization\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/kubelet/config/v1beta1.KubeletWebhookAuthorization\"}, } } func schema_k8sio_kubelet_config_v1beta1_KubeletConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"KubeletConfiguration contains the configuration for the Kubelet\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"enableServer\": { SchemaProps: spec.SchemaProps{ Description: \"enableServer enables Kubelet's secured server. Note: Kubelet's insecure port is controlled by the readOnlyPort option. Default: true\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"staticPodPath\": { SchemaProps: spec.SchemaProps{ Description: \"staticPodPath is the path to the directory containing local (static) pods to run, or the path to a single static pod file. Default: \"\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"syncFrequency\": { SchemaProps: spec.SchemaProps{ Description: \"syncFrequency is the max period between synchronizing running containers and config. Default: \"1m\"\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"fileCheckFrequency\": { SchemaProps: spec.SchemaProps{ Description: \"fileCheckFrequency is the duration between checking config files for new data. Default: \"20s\"\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"httpCheckFrequency\": { SchemaProps: spec.SchemaProps{ Description: \"httpCheckFrequency is the duration between checking http for new data. Default: \"20s\"\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"staticPodURL\": { SchemaProps: spec.SchemaProps{ Description: \"staticPodURL is the URL for accessing static pods to run. Default: \"\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"staticPodURLHeader\": { SchemaProps: spec.SchemaProps{ Description: \"staticPodURLHeader is a map of slices with HTTP headers to use when accessing the podURL. Default: nil\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, }, }, }, \"address\": { SchemaProps: spec.SchemaProps{ Description: \"address is the IP address for the Kubelet to serve on (set to 0.0.0.0 for all interfaces). Default: \"0.0.0.0\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"port\": { SchemaProps: spec.SchemaProps{ Description: \"port is the port for the Kubelet to serve on. The port number must be between 1 and 65535, inclusive. Default: 10250\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"readOnlyPort\": { SchemaProps: spec.SchemaProps{ Description: \"readOnlyPort is the read-only port for the Kubelet to serve on with no authentication/authorization. The port number must be between 1 and 65535, inclusive. Setting this field to 0 disables the read-only service. Default: 0 (disabled)\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"tlsCertFile\": { SchemaProps: spec.SchemaProps{ Description: \"tlsCertFile is the file containing x509 Certificate for HTTPS. (CA cert, if any, concatenated after server cert). If tlsCertFile and tlsPrivateKeyFile are not provided, a self-signed certificate and key are generated for the public address and saved to the directory passed to the Kubelet's --cert-dir flag. Default: \"\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"tlsPrivateKeyFile\": { SchemaProps: spec.SchemaProps{ Description: \"tlsPrivateKeyFile is the file containing x509 private key matching tlsCertFile. Default: \"\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"tlsCipherSuites\": { SchemaProps: spec.SchemaProps{ Description: \"tlsCipherSuites is the list of allowed cipher suites for the server. Values are from tls package constants (https://golang.org/pkg/crypto/tls/#pkg-constants). Default: nil\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"tlsMinVersion\": { SchemaProps: spec.SchemaProps{ Description: \"tlsMinVersion is the minimum TLS version supported. Values are from tls package constants (https://golang.org/pkg/crypto/tls/#pkg-constants). Default: \"\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"rotateCertificates\": { SchemaProps: spec.SchemaProps{ Description: \"rotateCertificates enables client certificate rotation. The Kubelet will request a new certificate from the certificates.k8s.io API. This requires an approver to approve the certificate signing requests. Default: false\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"serverTLSBootstrap\": { SchemaProps: spec.SchemaProps{ Description: \"serverTLSBootstrap enables server certificate bootstrap. Instead of self signing a serving certificate, the Kubelet will request a certificate from the 'certificates.k8s.io' API. This requires an approver to approve the certificate signing requests (CSR). The RotateKubeletServerCertificate feature must be enabled when setting this field. Default: false\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"authentication\": { SchemaProps: spec.SchemaProps{ Description: \"authentication specifies how requests to the Kubelet's server are authenticated. Defaults:n  anonymous:n    enabled: falsen  webhook:n    enabled: truen    cacheTTL: \"2m\"\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kubelet/config/v1beta1.KubeletAuthentication\"), }, }, \"authorization\": { SchemaProps: spec.SchemaProps{ Description: \"authorization specifies how requests to the Kubelet's server are authorized. Defaults:n  mode: Webhookn  webhook:n    cacheAuthorizedTTL: \"5m\"n    cacheUnauthorizedTTL: \"30s\"\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kubelet/config/v1beta1.KubeletAuthorization\"), }, }, \"registryPullQPS\": { SchemaProps: spec.SchemaProps{ Description: \"registryPullQPS is the limit of registry pulls per second. The value must not be a negative number. Setting it to 0 means no limit. Default: 5\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"registryBurst\": { SchemaProps: spec.SchemaProps{ Description: \"registryBurst is the maximum size of bursty pulls, temporarily allows pulls to burst to this number, while still not exceeding registryPullQPS. The value must not be a negative number. Only used if registryPullQPS is greater than 0. Default: 10\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"eventRecordQPS\": { SchemaProps: spec.SchemaProps{ Description: \"eventRecordQPS is the maximum event creations per second. If 0, there is no limit enforced. The value cannot be a negative number. Default: 5\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"eventBurst\": { SchemaProps: spec.SchemaProps{ Description: \"eventBurst is the maximum size of a burst of event creations, temporarily allows event creations to burst to this number, while still not exceeding eventRecordQPS. This field canot be a negative number and it is only used when eventRecordQPS > 0. Default: 10\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"enableDebuggingHandlers\": { SchemaProps: spec.SchemaProps{ Description: \"enableDebuggingHandlers enables server endpoints for log access and local running of containers and commands, including the exec, attach, logs, and portforward features. Default: true\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"enableContentionProfiling\": { SchemaProps: spec.SchemaProps{ Description: \"enableContentionProfiling enables lock contention profiling, if enableDebuggingHandlers is true. Default: false\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"healthzPort\": { SchemaProps: spec.SchemaProps{ Description: \"healthzPort is the port of the localhost healthz endpoint (set to 0 to disable). A valid number is between 1 and 65535. Default: 10248\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"healthzBindAddress\": { SchemaProps: spec.SchemaProps{ Description: \"healthzBindAddress is the IP address for the healthz server to serve on. Default: \"127.0.0.1\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"oomScoreAdj\": { SchemaProps: spec.SchemaProps{ Description: \"oomScoreAdj is The oom-score-adj value for kubelet process. Values must be within the range [-1000, 1000]. Default: -999\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"clusterDomain\": { SchemaProps: spec.SchemaProps{ Description: \"clusterDomain is the DNS domain for this cluster. If set, kubelet will configure all containers to search this domain in addition to the host's search domains. Default: \"\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"clusterDNS\": { SchemaProps: spec.SchemaProps{ Description: \"clusterDNS is a list of IP addresses for the cluster DNS server. If set, kubelet will configure all containers to use this for DNS resolution instead of the host's DNS servers. Default: nil\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"streamingConnectionIdleTimeout\": { SchemaProps: spec.SchemaProps{ Description: \"streamingConnectionIdleTimeout is the maximum time a streaming connection can be idle before the connection is automatically closed. Default: \"4h\"\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"nodeStatusUpdateFrequency\": { SchemaProps: spec.SchemaProps{ Description: \"nodeStatusUpdateFrequency is the frequency that kubelet computes node status. If node lease feature is not enabled, it is also the frequency that kubelet posts node status to master. Note: When node lease feature is not enabled, be cautious when changing the constant, it must work with nodeMonitorGracePeriod in nodecontroller. Default: \"10s\"\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"nodeStatusReportFrequency\": { SchemaProps: spec.SchemaProps{ Description: \"nodeStatusReportFrequency is the frequency that kubelet posts node status to master if node status does not change. Kubelet will ignore this frequency and post node status immediately if any change is detected. It is only used when node lease feature is enabled. nodeStatusReportFrequency's default value is 5m. But if nodeStatusUpdateFrequency is set explicitly, nodeStatusReportFrequency's default value will be set to nodeStatusUpdateFrequency for backward compatibility. Default: \"5m\"\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"nodeLeaseDurationSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"nodeLeaseDurationSeconds is the duration the Kubelet will set on its corresponding Lease. NodeLease provides an indicator of node health by having the Kubelet create and periodically renew a lease, named after the node, in the kube-node-lease namespace. If the lease expires, the node can be considered unhealthy. The lease is currently renewed every 10s, per KEP-0009. In the future, the lease renewal interval may be set based on the lease duration. The field value must be greater than 0. Default: 40\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"imageMinimumGCAge\": { SchemaProps: spec.SchemaProps{ Description: \"imageMinimumGCAge is the minimum age for an unused image before it is garbage collected. Default: \"2m\"\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"imageGCHighThresholdPercent\": { SchemaProps: spec.SchemaProps{ Description: \"imageGCHighThresholdPercent is the percent of disk usage after which image garbage collection is always run. The percent is calculated by dividing this field value by 100, so this field must be between 0 and 100, inclusive. When specified, the value must be greater than imageGCLowThresholdPercent. Default: 85\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"imageGCLowThresholdPercent\": { SchemaProps: spec.SchemaProps{ Description: \"imageGCLowThresholdPercent is the percent of disk usage before which image garbage collection is never run. Lowest disk usage to garbage collect to. The percent is calculated by dividing this field value by 100, so the field value must be between 0 and 100, inclusive. When specified, the value must be less than imageGCHighThresholdPercent. Default: 80\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"volumeStatsAggPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"volumeStatsAggPeriod is the frequency for calculating and caching volume disk usage for all pods. Default: \"1m\"\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"kubeletCgroups\": { SchemaProps: spec.SchemaProps{ Description: \"kubeletCgroups is the absolute name of cgroups to isolate the kubelet in Default: \"\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"systemCgroups\": { SchemaProps: spec.SchemaProps{ Description: \"systemCgroups is absolute name of cgroups in which to place all non-kernel processes that are not already in a container. Empty for no container. Rolling back the flag requires a reboot. The cgroupRoot must be specified if this field is not empty. Default: \"\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"cgroupRoot\": { SchemaProps: spec.SchemaProps{ Description: \"cgroupRoot is the root cgroup to use for pods. This is handled by the container runtime on a best effort basis.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"cgroupsPerQOS\": { SchemaProps: spec.SchemaProps{ Description: \"cgroupsPerQOS enable QoS based CGroup hierarchy: top level CGroups for QoS classes and all Burstable and BestEffort Pods are brought up under their specific top level QoS CGroup. Default: true\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"cgroupDriver\": { SchemaProps: spec.SchemaProps{ Description: \"cgroupDriver is the driver kubelet uses to manipulate CGroups on the host (cgroupfs or systemd). Default: \"cgroupfs\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"cpuManagerPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"cpuManagerPolicy is the name of the policy to use. Requires the CPUManager feature gate to be enabled. Default: \"None\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"cpuManagerPolicyOptions\": { SchemaProps: spec.SchemaProps{ Description: \"cpuManagerPolicyOptions is a set of key=value which tallows to set extra options to fine tune the behaviour of the cpu manager policies. Requires  both the \"CPUManager\" and \"CPUManagerPolicyOptions\" feature gates to be enabled. Default: nil\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"cpuManagerReconcilePeriod\": { SchemaProps: spec.SchemaProps{ Description: \"cpuManagerReconcilePeriod is the reconciliation period for the CPU Manager. Requires the CPUManager feature gate to be enabled. Default: \"10s\"\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"memoryManagerPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"memoryManagerPolicy is the name of the policy to use by memory manager. Requires the MemoryManager feature gate to be enabled. Default: \"none\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"topologyManagerPolicy\": { SchemaProps: spec.SchemaProps{ Description: \"topologyManagerPolicy is the name of the topology manager policy to use. Valid values include:nn- `restricted`: kubelet only allows pods with optimal NUMA node alignment forn  requested resources;n- `best-effort`: kubelet will favor pods with NUMA alignment of CPU and devicen  resources;n- `none`: kubelet has no knowledge of NUMA alignment of a pod's CPU and device resources. - `single-numa-node`: kubelet only allows pods with a single NUMA alignmentn  of CPU and device resources.nnPolicies other than \"none\" require the TopologyManager feature gate to be enabled. Default: \"none\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"topologyManagerScope\": { SchemaProps: spec.SchemaProps{ Description: \"topologyManagerScope represents the scope of topology hint generation that topology manager requests and hint providers generate. Valid values include:nn- `container`: topology policy is applied on a per-container basis. - `pod`: topology policy is applied on a per-pod basis.nn\"pod\" scope requires the TopologyManager feature gate to be enabled. Default: \"container\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"qosReserved\": { SchemaProps: spec.SchemaProps{ Description: \"qosReserved is a set of resource name to percentage pairs that specify the minimum percentage of a resource reserved for exclusive use by the guaranteed QoS tier. Currently supported resources: \"memory\" Requires the QOSReserved feature gate to be enabled. Default: nil\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"runtimeRequestTimeout\": { SchemaProps: spec.SchemaProps{ Description: \"runtimeRequestTimeout is the timeout for all runtime requests except long running requests - pull, logs, exec and attach. Default: \"2m\"\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"hairpinMode\": { SchemaProps: spec.SchemaProps{ Description: \"hairpinMode specifies how the Kubelet should configure the container bridge for hairpin packets. Setting this flag allows endpoints in a Service to loadbalance back to themselves if they should try to access their own Service. Values:nn- \"promiscuous-bridge\": make the container bridge promiscuous. - \"hairpin-veth\":       set the hairpin flag on container veth interfaces. - \"none\":               do nothing.nnGenerally, one must set `--hairpin-mode=hairpin-veth to` achieve hairpin NAT, because promiscuous-bridge assumes the existence of a container bridge named cbr0. Default: \"promiscuous-bridge\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"maxPods\": { SchemaProps: spec.SchemaProps{ Description: \"maxPods is the maximum number of Pods that can run on this Kubelet. The value must be a non-negative integer. Default: 110\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"podCIDR\": { SchemaProps: spec.SchemaProps{ Description: \"podCIDR is the CIDR to use for pod IP addresses, only used in standalone mode. In cluster mode, this is obtained from the control plane. Default: \"\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"podPidsLimit\": { SchemaProps: spec.SchemaProps{ Description: \"podPidsLimit is the maximum number of PIDs in any pod. Default: -1\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"resolvConf\": { SchemaProps: spec.SchemaProps{ Description: \"resolvConf is the resolver configuration file used as the basis for the container DNS resolution configuration. If set to the empty string, will override the default and effectively disable DNS lookups. Default: \"/etc/resolv.conf\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"runOnce\": { SchemaProps: spec.SchemaProps{ Description: \"runOnce causes the Kubelet to check the API server once for pods, run those in addition to the pods specified by static pod files, and exit. Default: false\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"cpuCFSQuota\": { SchemaProps: spec.SchemaProps{ Description: \"cpuCFSQuota enables CPU CFS quota enforcement for containers that specify CPU limits. Default: true\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"cpuCFSQuotaPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"cpuCFSQuotaPeriod is the CPU CFS quota period value, `cpu.cfs_period_us`. The value must be between 1 us and 1 second, inclusive. Requires the CustomCPUCFSQuotaPeriod feature gate to be enabled. Default: \"100ms\"\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"nodeStatusMaxImages\": { SchemaProps: spec.SchemaProps{ Description: \"nodeStatusMaxImages caps the number of images reported in Node.status.images. The value must be greater than -2. Note: If -1 is specified, no cap will be applied. If 0 is specified, no image is returned. Default: 50\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"maxOpenFiles\": { SchemaProps: spec.SchemaProps{ Description: \"maxOpenFiles is Number of files that can be opened by Kubelet process. The value must be a non-negative number. Default: 1000000\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"contentType\": { SchemaProps: spec.SchemaProps{ Description: \"contentType is contentType of requests sent to apiserver. Default: \"application/vnd.kubernetes.protobuf\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"kubeAPIQPS\": { SchemaProps: spec.SchemaProps{ Description: \"kubeAPIQPS is the QPS to use while talking with kubernetes apiserver. Default: 5\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"kubeAPIBurst\": { SchemaProps: spec.SchemaProps{ Description: \"kubeAPIBurst is the burst to allow while talking with kubernetes API server. This field cannot be a negative number. Default: 10\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"serializeImagePulls\": { SchemaProps: spec.SchemaProps{ Description: \"serializeImagePulls when enabled, tells the Kubelet to pull images one at a time. We recommend *not* changing the default value on nodes that run docker daemon with version  < 1.9 or an Aufs storage backend. Issue #10959 has more details. Default: true\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"evictionHard\": { SchemaProps: spec.SchemaProps{ Description: \"evictionHard is a map of signal names to quantities that defines hard eviction thresholds. For example: `{\"memory.available\": \"300Mi\"}`. To explicitly disable, pass a 0% or 100% threshold on an arbitrary resource. Default:n  memory.available:  \"100Mi\"n  nodefs.available:  \"10%\"n  nodefs.inodesFree: \"5%\"n  imagefs.available: \"15%\"\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"evictionSoft\": { SchemaProps: spec.SchemaProps{ Description: \"evictionSoft is a map of signal names to quantities that defines soft eviction thresholds. For example: `{\"memory.available\": \"300Mi\"}`. Default: nil\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"evictionSoftGracePeriod\": { SchemaProps: spec.SchemaProps{ Description: \"evictionSoftGracePeriod is a map of signal names to quantities that defines grace periods for each soft eviction signal. For example: `{\"memory.available\": \"30s\"}`. Default: nil\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"evictionPressureTransitionPeriod\": { SchemaProps: spec.SchemaProps{ Description: \"evictionPressureTransitionPeriod is the duration for which the kubelet has to wait before transitioning out of an eviction pressure condition. Default: \"5m\"\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"evictionMaxPodGracePeriod\": { SchemaProps: spec.SchemaProps{ Description: \"evictionMaxPodGracePeriod is the maximum allowed grace period (in seconds) to use when terminating pods in response to a soft eviction threshold being met. This value effectively caps the Pod's terminationGracePeriodSeconds value during soft evictions. Note: Due to issue #64530, the behavior has a bug where this value currently just overrides the grace period during soft eviction, which can increase the grace period from what is set on the Pod. This bug will be fixed in a future release. Default: 0\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"evictionMinimumReclaim\": { SchemaProps: spec.SchemaProps{ Description: \"evictionMinimumReclaim is a map of signal names to quantities that defines minimum reclaims, which describe the minimum amount of a given resource the kubelet will reclaim when performing a pod eviction while that resource is under pressure. For example: `{\"imagefs.available\": \"2Gi\"}`. Default: nil\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"podsPerCore\": { SchemaProps: spec.SchemaProps{ Description: \"podsPerCore is the maximum number of pods per core. Cannot exceed maxPods. The value must be a non-negative integer. If 0, there is no limit on the number of Pods. Default: 0\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"enableControllerAttachDetach\": { SchemaProps: spec.SchemaProps{ Description: \"enableControllerAttachDetach enables the Attach/Detach controller to manage attachment/detachment of volumes scheduled to this node, and disables kubelet from executing any attach/detach operations. Default: true\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"protectKernelDefaults\": { SchemaProps: spec.SchemaProps{ Description: \"protectKernelDefaults, if true, causes the Kubelet to error if kernel flags are not as it expects. Otherwise the Kubelet will attempt to modify kernel flags to match its expectation. Default: false\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"makeIPTablesUtilChains\": { SchemaProps: spec.SchemaProps{ Description: \"makeIPTablesUtilChains, if true, causes the Kubelet ensures a set of iptables rules are present on host. These rules will serve as utility rules for various components, e.g. kube-proxy. The rules will be created based on iptablesMasqueradeBit and iptablesDropBit. Default: true\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"iptablesMasqueradeBit\": { SchemaProps: spec.SchemaProps{ Description: \"iptablesMasqueradeBit is the bit of the iptables fwmark space to mark for SNAT. Values must be within the range [0, 31]. Must be different from other mark bits. Warning: Please match the value of the corresponding parameter in kube-proxy. Default: 14\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"iptablesDropBit\": { SchemaProps: spec.SchemaProps{ Description: \"iptablesDropBit is the bit of the iptables fwmark space to mark for dropping packets. Values must be within the range [0, 31]. Must be different from other mark bits. Default: 15\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"featureGates\": { SchemaProps: spec.SchemaProps{ Description: \"featureGates is a map of feature names to bools that enable or disable experimental features. This field modifies piecemeal the built-in default values from \"k8s.io/kubernetes/pkg/features/kube_features.go\". Default: nil\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: false, Type:    []string{\"boolean\"}, Format:  \"\", }, }, }, }, }, \"failSwapOn\": { SchemaProps: spec.SchemaProps{ Description: \"failSwapOn tells the Kubelet to fail to start if swap is enabled on the node. Default: true\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"memorySwap\": { SchemaProps: spec.SchemaProps{ Description: \"memorySwap configures swap memory available to container workloads.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kubelet/config/v1beta1.MemorySwapConfiguration\"), }, }, \"containerLogMaxSize\": { SchemaProps: spec.SchemaProps{ Description: \"containerLogMaxSize is a quantity defining the maximum size of the container log file before it is rotated. For example: \"5Mi\" or \"256Ki\". Default: \"10Mi\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"containerLogMaxFiles\": { SchemaProps: spec.SchemaProps{ Description: \"containerLogMaxFiles specifies the maximum number of container log files that can be present for a container. Default: 5\", Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"configMapAndSecretChangeDetectionStrategy\": { SchemaProps: spec.SchemaProps{ Description: \"configMapAndSecretChangeDetectionStrategy is a mode in which ConfigMap and Secret managers are running. Valid values include:nn- `Get`: kubelet fetches necessary objects directly from the API server; - `Cache`: kubelet uses TTL cache for object fetched from the API server; - `Watch`: kubelet uses watches to observe changes to objects that are in its interest.nnDefault: \"Watch\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"systemReserved\": { SchemaProps: spec.SchemaProps{ Description: \"systemReserved is a set of ResourceName=ResourceQuantity (e.g. cpu=200m,memory=150G) pairs that describe resources reserved for non-kubernetes components. Currently only cpu and memory are supported. See http://kubernetes.io/docs/user-guide/compute-resources for more detail. Default: nil\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"kubeReserved\": { SchemaProps: spec.SchemaProps{ Description: \"kubeReserved is a set of ResourceName=ResourceQuantity (e.g. cpu=200m,memory=150G) pairs that describe resources reserved for kubernetes system components. Currently cpu, memory and local storage for root file system are supported. See https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ for more details. Default: nil\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"reservedSystemCPUs\": { SchemaProps: spec.SchemaProps{ Description: \"The reservedSystemCPUs option specifies the CPU list reserved for the host level system threads and kubernetes related threads. This provide a \"static\" CPU list rather than the \"dynamic\" list by systemReserved and kubeReserved. This option does not support systemReservedCgroup or kubeReservedCgroup.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"showHiddenMetricsForVersion\": { SchemaProps: spec.SchemaProps{ Description: \"showHiddenMetricsForVersion is the previous version for which you want to show hidden metrics. Only the previous minor version is meaningful, other values will not be allowed. The format is `<major>.<minor>`, e.g.: `1.16`. The purpose of this format is make sure you have the opportunity to notice if the next release hides additional metrics, rather than being surprised when they are permanently removed in the release after that. Default: \"\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"systemReservedCgroup\": { SchemaProps: spec.SchemaProps{ Description: \"systemReservedCgroup helps the kubelet identify absolute name of top level CGroup used to enforce `systemReserved` compute resource reservation for OS system daemons. Refer to [Node Allocatable](https://git.k8s.io/community/contributors/design-proposals/node/node-allocatable.md) doc for more information. Default: \"\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"kubeReservedCgroup\": { SchemaProps: spec.SchemaProps{ Description: \"kubeReservedCgroup helps the kubelet identify absolute name of top level CGroup used to enforce `KubeReserved` compute resource reservation for Kubernetes node system daemons. Refer to [Node Allocatable](https://git.k8s.io/community/contributors/design-proposals/node/node-allocatable.md) doc for more information. Default: \"\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"enforceNodeAllocatable\": { SchemaProps: spec.SchemaProps{ Description: \"This flag specifies the various Node Allocatable enforcements that Kubelet needs to perform. This flag accepts a list of options. Acceptable options are `none`, `pods`, `system-reserved` and `kube-reserved`. If `none` is specified, no other options may be specified. When `system-reserved` is in the list, systemReservedCgroup must be specified. When `kube-reserved` is in the list, kubeReservedCgroup must be specified. This field is supported only when `cgroupsPerQOS` is set to true. Refer to [Node Allocatable](https://git.k8s.io/community/contributors/design-proposals/node/node-allocatable.md) for more information. Default: [\"pods\"]\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"allowedUnsafeSysctls\": { SchemaProps: spec.SchemaProps{ Description: \"A comma separated whitelist of unsafe sysctls or sysctl patterns (ending in `*`). Unsafe sysctl groups are `kernel.shm*`, `kernel.msg*`, `kernel.sem`, `fs.mqueue.*`, and `net.*`. For example: \"`kernel.msg*,net.ipv4.route.min_pmtu`\" Default: []\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"volumePluginDir\": { SchemaProps: spec.SchemaProps{ Description: \"volumePluginDir is the full path of the directory in which to search for additional third party volume plugins. Default: \"/usr/libexec/kubernetes/kubelet-plugins/volume/exec/\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"providerID\": { SchemaProps: spec.SchemaProps{ Description: \"providerID, if set, sets the unique ID of the instance that an external provider (i.e. cloudprovider) can use to identify a specific node. Default: \"\"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"kernelMemcgNotification\": { SchemaProps: spec.SchemaProps{ Description: \"kernelMemcgNotification, if set, instructs the the kubelet to integrate with the kernel memcg notification for determining if memory eviction thresholds are exceeded rather than polling. Default: false\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"logging\": { SchemaProps: spec.SchemaProps{ Description: \"logging specifies the options of logging. Refer to [Logs Options](https://github.com/kubernetes/component-base/blob/master/logs/options.go) for more information. Default:n  Format: text\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/component-base/config/v1alpha1.LoggingConfiguration\"), }, }, \"enableSystemLogHandler\": { SchemaProps: spec.SchemaProps{ Description: \"enableSystemLogHandler enables system logs via web interface host:port/logs/ Default: true\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"shutdownGracePeriod\": { SchemaProps: spec.SchemaProps{ Description: \"shutdownGracePeriod specifies the total duration that the node should delay the shutdown and total grace period for pod termination during a node shutdown. Default: \"0s\"\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"shutdownGracePeriodCriticalPods\": { SchemaProps: spec.SchemaProps{ Description: \"shutdownGracePeriodCriticalPods specifies the duration used to terminate critical pods during a node shutdown. This should be less than shutdownGracePeriod. For example, if shutdownGracePeriod=30s, and shutdownGracePeriodCriticalPods=10s, during a node shutdown the first 20 seconds would be reserved for gracefully terminating normal pods, and the last 10 seconds would be reserved for terminating critical pods. Default: \"0s\"\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"shutdownGracePeriodByPodPriority\": { SchemaProps: spec.SchemaProps{ Description: \"shutdownGracePeriodByPodPriority specifies the shutdown grace period for Pods based on their associated priority class value. When a shutdown request is received, the Kubelet will initiate shutdown on all pods running on the node with a grace period that depends on the priority of the pod, and then wait for all pods to exit. Each entry in the array represents the graceful shutdown time a pod with a priority class value that lies in the range of that value and the next higher entry in the list when the node is shutting down. For example, to allow critical pods 10s to shutdown, priority>=10000 pods 20s to shutdown, and all remaining pods 30s to shutdown.nnshutdownGracePeriodByPodPriority:n  - priority: 2000000000n    shutdownGracePeriodSeconds: 10n  - priority: 10000n    shutdownGracePeriodSeconds: 20n  - priority: 0n    shutdownGracePeriodSeconds: 30nnThe time the Kubelet will wait before exiting will at most be the maximum of all shutdownGracePeriodSeconds for each priority class range represented on the node. When all pods have exited or reached their grace periods, the Kubelet will release the shutdown inhibit lock. Requires the GracefulNodeShutdown feature gate to be enabled. This configuration must be empty if either ShutdownGracePeriod or ShutdownGracePeriodCriticalPods is set. Default: nil\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kubelet/config/v1beta1.ShutdownGracePeriodByPodPriority\"), }, }, }, }, }, \"reservedMemory\": { SchemaProps: spec.SchemaProps{ Description: \"reservedMemory specifies a comma-separated list of memory reservations for NUMA nodes. The parameter makes sense only in the context of the memory manager feature. The memory manager will not allocate reserved memory for container workloads. For example, if you have a NUMA0 with 10Gi of memory and the reservedMemory was specified to reserve 1Gi of memory at NUMA0, the memory manager will assume that only 9Gi is available for allocation. You can specify a different amount of NUMA node and memory types. You can omit this parameter at all, but you should be aware that the amount of reserved memory from all NUMA nodes should be equal to the amount of memory specified by the [node allocatable](https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable). If at least one node allocatable parameter has a non-zero value, you will need to specify at least one NUMA node. Also, avoid specifying:nn1. Duplicates, the same NUMA node, and memory type, but with a different value. 2. zero limits for any memory type. 3. NUMAs nodes IDs that do not exist under the machine. 4. memory types except for memory and hugepages-<size>nnDefault: nil\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/kubelet/config/v1beta1.MemoryReservation\"), }, }, }, }, }, \"enableProfilingHandler\": { SchemaProps: spec.SchemaProps{ Description: \"enableProfilingHandler enables profiling via web interface host:port/debug/pprof/ Default: true\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"enableDebugFlagsHandler\": { SchemaProps: spec.SchemaProps{ Description: \"enableDebugFlagsHandler enables flags endpoint via web interface host:port/debug/flags/v Default: true\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"seccompDefault\": { SchemaProps: spec.SchemaProps{ Description: \"SeccompDefault enables the use of `RuntimeDefault` as the default seccomp profile for all workloads. This requires the corresponding SeccompDefault feature gate to be enabled as well. Default: false\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"memoryThrottlingFactor\": { SchemaProps: spec.SchemaProps{ Description: \"MemoryThrottlingFactor specifies the factor multiplied by the memory limit or node allocatable memory when setting the cgroupv2 memory.high value to enforce MemoryQoS. Decreasing this factor will set lower high limit for container cgroups and put heavier reclaim pressure while increasing will put less reclaim pressure. See http://kep.k8s.io/2570 for more details. Default: 0.8\", Type:        []string{\"number\"}, Format:      \"double\", }, }, \"registerWithTaints\": { SchemaProps: spec.SchemaProps{ Description: \"registerWithTaints are an array of taints to add to a node object when the kubelet registers itself. This only takes effect when registerNode is true and upon the initial registration of the node. Default: nil\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/api/core/v1.Taint\"), }, }, }, }, }, \"registerNode\": { SchemaProps: spec.SchemaProps{ Description: \"registerNode enables automatic registration with the apiserver. Default: true\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.Taint\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\", \"k8s.io/component-base/config/v1alpha1.LoggingConfiguration\", \"k8s.io/kubelet/config/v1beta1.KubeletAuthentication\", \"k8s.io/kubelet/config/v1beta1.KubeletAuthorization\", \"k8s.io/kubelet/config/v1beta1.MemoryReservation\", \"k8s.io/kubelet/config/v1beta1.MemorySwapConfiguration\", \"k8s.io/kubelet/config/v1beta1.ShutdownGracePeriodByPodPriority\"}, } } func schema_k8sio_kubelet_config_v1beta1_KubeletWebhookAuthentication(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, Properties: map[string]spec.Schema{ \"enabled\": { SchemaProps: spec.SchemaProps{ Description: \"enabled allows bearer token authentication backed by the tokenreviews.authentication.k8s.io API.\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"cacheTTL\": { SchemaProps: spec.SchemaProps{ Description: \"cacheTTL enables caching of authentication results\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"}, } } func schema_k8sio_kubelet_config_v1beta1_KubeletWebhookAuthorization(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, Properties: map[string]spec.Schema{ \"cacheAuthorizedTTL\": { SchemaProps: spec.SchemaProps{ Description: \"cacheAuthorizedTTL is the duration to cache 'authorized' responses from the webhook authorizer.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"cacheUnauthorizedTTL\": { SchemaProps: spec.SchemaProps{ Description: \"cacheUnauthorizedTTL is the duration to cache 'unauthorized' responses from the webhook authorizer.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"}, } } func schema_k8sio_kubelet_config_v1beta1_KubeletX509Authentication(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, Properties: map[string]spec.Schema{ \"clientCAFile\": { SchemaProps: spec.SchemaProps{ Description: \"clientCAFile is the path to a PEM-encoded certificate bundle. If set, any request presenting a client certificate signed by one of the authorities in the bundle is authenticated with a username corresponding to the CommonName, and groups corresponding to the Organization in the client certificate.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_kubelet_config_v1beta1_MemoryReservation(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MemoryReservation specifies the memory reservation of different types for each NUMA node\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"numaNode\": { SchemaProps: spec.SchemaProps{ Default: 0, Type:    []string{\"integer\"}, Format:  \"int32\", }, }, \"limits\": { SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, }, Required: []string{\"numaNode\", \"limits\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_k8sio_kubelet_config_v1beta1_MemorySwapConfiguration(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Type: []string{\"object\"}, Properties: map[string]spec.Schema{ \"swapBehavior\": { SchemaProps: spec.SchemaProps{ Description: \"swapBehavior configures swap memory available to container workloads. May be one of \"\", \"LimitedSwap\": workload combined memory and swap usage cannot exceed pod memory limit \"UnlimitedSwap\": workloads can use unlimited swap, up to the allocatable limit.\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_k8sio_kubelet_config_v1beta1_SerializedNodeConfigSource(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"SerializedNodeConfigSource allows us to serialize v1.NodeConfigSource. This type is used internally by the Kubelet for tracking checkpointed dynamic configs. It exists in the kubeletconfig API group because it is classified as a versioned input to the Kubelet.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"source\": { SchemaProps: spec.SchemaProps{ Description: \"source is the source that we are serializing.\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.NodeConfigSource\"), }, }, }, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.NodeConfigSource\"}, } } func schema_k8sio_kubelet_config_v1beta1_ShutdownGracePeriodByPodPriority(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ShutdownGracePeriodByPodPriority specifies the shutdown grace period for Pods based on their associated priority class value\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"priority\": { SchemaProps: spec.SchemaProps{ Description: \"priority is the priority value associated with the shutdown grace period\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int32\", }, }, \"shutdownGracePeriodSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"shutdownGracePeriodSeconds is the shutdown grace period in seconds\", Default:     0, Type:        []string{\"integer\"}, Format:      \"int64\", }, }, }, Required: []string{\"priority\", \"shutdownGracePeriodSeconds\"}, }, }, } } func schema_pkg_apis_abac_v1beta1_Policy(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"Policy contains a single ABAC policy rule\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"spec\": { SchemaProps: spec.SchemaProps{ Description: \"Spec describes the policy rule\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/kubernetes/pkg/apis/abac/v1beta1.PolicySpec\"), }, }, }, Required: []string{\"spec\"}, }, }, Dependencies: []string{ \"k8s.io/kubernetes/pkg/apis/abac/v1beta1.PolicySpec\"}, } } func schema_pkg_apis_abac_v1beta1_PolicySpec(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PolicySpec contains the attributes for a policy rule\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"user\": { SchemaProps: spec.SchemaProps{ Description: \"User is the username this rule applies to. Either user or group is required to match the request. \"*\" matches all users.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"group\": { SchemaProps: spec.SchemaProps{ Description: \"Group is the group this rule applies to. Either user or group is required to match the request. \"*\" matches all groups.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"readonly\": { SchemaProps: spec.SchemaProps{ Description: \"Readonly matches readonly requests when true, and all requests when false\", Type:        []string{\"boolean\"}, Format:      \"\", }, }, \"apiGroup\": { SchemaProps: spec.SchemaProps{ Description: \"APIGroup is the name of an API group. APIGroup, Resource, and Namespace are required to match resource requests. \"*\" matches all API groups\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"resource\": { SchemaProps: spec.SchemaProps{ Description: \"Resource is the name of a resource. APIGroup, Resource, and Namespace are required to match resource requests. \"*\" matches all resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"namespace\": { SchemaProps: spec.SchemaProps{ Description: \"Namespace is the name of a namespace. APIGroup, Resource, and Namespace are required to match resource requests. \"*\" matches all namespaces (including unnamespaced requests)\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"nonResourcePath\": { SchemaProps: spec.SchemaProps{ Description: \"NonResourcePath matches non-resource request paths. \"*\" matches all paths \"/foo/*\" matches all subpaths of foo\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_pkg_apis_custom_metrics_v1beta1_MetricListOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricListOptions is used to select metrics by their label selectors\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"labelSelector\": { SchemaProps: spec.SchemaProps{ Description: \"A selector to restrict the list of returned objects by their labels. Defaults to everything.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metricLabelSelector\": { SchemaProps: spec.SchemaProps{ Description: \"A selector to restrict the list of returned metrics by their labels\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_pkg_apis_custom_metrics_v1beta1_MetricValue(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricValue is a metric value for some object\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"describedObject\": { SchemaProps: spec.SchemaProps{ Description: \"a reference to the described object\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.ObjectReference\"), }, }, \"metricName\": { SchemaProps: spec.SchemaProps{ Description: \"the name of the metric\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"timestamp\": { SchemaProps: spec.SchemaProps{ Description: \"indicates the time at which the metrics were produced\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"window\": { SchemaProps: spec.SchemaProps{ Description: \"indicates the window ([Timestamp-Window, Timestamp]) from which these metrics were calculated, when returning rate metrics calculated from cumulative metrics (or zero for non-calculated instantaneous metrics).\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"value\": { SchemaProps: spec.SchemaProps{ Description: \"the value of the metric for this\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"selector represents the label selector that could be used to select this metric, and will generally just be the selector passed in to the query used to fetch this metric. When left blank, only the metric's Name will be used to gather metrics.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, }, Required: []string{\"describedObject\", \"metricName\", \"timestamp\", \"value\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ObjectReference\", \"k8s.io/apimachinery/pkg/api/resource.Quantity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_pkg_apis_custom_metrics_v1beta1_MetricValueList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricValueList is a list of values for a given metric for some set of objects\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"the value of the metric across the described objects\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/metrics/pkg/apis/custom_metrics/v1beta1.MetricValue\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/metrics/pkg/apis/custom_metrics/v1beta1.MetricValue\"}, } } func schema_pkg_apis_custom_metrics_v1beta2_MetricIdentifier(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricIdentifier identifies a metric by name and, optionally, selector\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"name is the name of the given metric\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"selector\": { SchemaProps: spec.SchemaProps{ Description: \"selector represents the label selector that could be used to select this metric, and will generally just be the selector passed in to the query used to fetch this metric. When left blank, only the metric's Name will be used to gather metrics.\", Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"), }, }, }, Required: []string{\"name\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector\"}, } } func schema_pkg_apis_custom_metrics_v1beta2_MetricListOptions(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricListOptions is used to select metrics by their label selectors\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"labelSelector\": { SchemaProps: spec.SchemaProps{ Description: \"A selector to restrict the list of returned objects by their labels. Defaults to everything.\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metricLabelSelector\": { SchemaProps: spec.SchemaProps{ Description: \"A selector to restrict the list of returned metrics by their labels\", Type:        []string{\"string\"}, Format:      \"\", }, }, }, }, }, } } func schema_pkg_apis_custom_metrics_v1beta2_MetricValue(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricValue is the metric value for some object\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"describedObject\": { SchemaProps: spec.SchemaProps{ Description: \"a reference to the described object\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/api/core/v1.ObjectReference\"), }, }, \"metric\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/metrics/pkg/apis/custom_metrics/v1beta2.MetricIdentifier\"), }, }, \"timestamp\": { SchemaProps: spec.SchemaProps{ Description: \"indicates the time at which the metrics were produced\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"windowSeconds\": { SchemaProps: spec.SchemaProps{ Description: \"indicates the window ([Timestamp-Window, Timestamp]) from which these metrics were calculated, when returning rate metrics calculated from cumulative metrics (or zero for non-calculated instantaneous metrics).\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"value\": { SchemaProps: spec.SchemaProps{ Description: \"the value of the metric for this\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, Required: []string{\"describedObject\", \"metric\", \"timestamp\", \"value\"}, }, }, Dependencies: []string{ \"k8s.io/api/core/v1.ObjectReference\", \"k8s.io/apimachinery/pkg/api/resource.Quantity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\", \"k8s.io/metrics/pkg/apis/custom_metrics/v1beta2.MetricIdentifier\"}, } } func schema_pkg_apis_custom_metrics_v1beta2_MetricValueList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"MetricValueList is a list of values for a given metric for some set of objects\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"the value of the metric across the described objects\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/metrics/pkg/apis/custom_metrics/v1beta2.MetricValue\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/metrics/pkg/apis/custom_metrics/v1beta2.MetricValue\"}, } } func schema_pkg_apis_external_metrics_v1beta1_ExternalMetricValue(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExternalMetricValue is a metric value for external metric A single metric value is identified by metric name and a set of string labels. For one metric there can be multiple values with different sets of labels.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metricName\": { SchemaProps: spec.SchemaProps{ Description: \"the name of the metric\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metricLabels\": { SchemaProps: spec.SchemaProps{ Description: \"a set of labels that identify a single time series for the metric\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: \"\", Type:    []string{\"string\"}, Format:  \"\", }, }, }, }, }, \"timestamp\": { SchemaProps: spec.SchemaProps{ Description: \"indicates the time at which the metrics were produced\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"window\": { SchemaProps: spec.SchemaProps{ Description: \"indicates the window ([Timestamp-Window, Timestamp]) from which these metrics were calculated, when returning rate metrics calculated from cumulative metrics (or zero for non-calculated instantaneous metrics).\", Type:        []string{\"integer\"}, Format:      \"int64\", }, }, \"value\": { SchemaProps: spec.SchemaProps{ Description: \"the value of the metric\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, Required: []string{\"metricName\", \"metricLabels\", \"timestamp\", \"value\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_pkg_apis_external_metrics_v1beta1_ExternalMetricValueList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ExternalMetricValueList is a list of values for a given metric for some set labels\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"value of the metric matching a given set of labels\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/metrics/pkg/apis/external_metrics/v1beta1.ExternalMetricValue\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/metrics/pkg/apis/external_metrics/v1beta1.ExternalMetricValue\"}, } } func schema_pkg_apis_metrics_v1alpha1_ContainerMetrics(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ContainerMetrics sets resource usage metrics of a container.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Container name corresponding to the one from pod.spec.containers.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"usage\": { SchemaProps: spec.SchemaProps{ Description: \"The memory usage is the memory working set.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, }, Required: []string{\"name\", \"usage\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_pkg_apis_metrics_v1alpha1_NodeMetrics(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeMetrics sets resource usage metrics of a node.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"timestamp\": { SchemaProps: spec.SchemaProps{ Description: \"The following fields define time interval from which metrics were collected from the interval [Timestamp-Window, Timestamp].\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"window\": { SchemaProps: spec.SchemaProps{ Default: 0, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"usage\": { SchemaProps: spec.SchemaProps{ Description: \"The memory usage is the memory working set.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, }, Required: []string{\"timestamp\", \"window\", \"usage\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_pkg_apis_metrics_v1alpha1_NodeMetricsList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeMetricsList is a list of NodeMetrics.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of node metrics.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/metrics/pkg/apis/metrics/v1alpha1.NodeMetrics\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/metrics/pkg/apis/metrics/v1alpha1.NodeMetrics\"}, } } func schema_pkg_apis_metrics_v1alpha1_PodMetrics(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodMetrics sets resource usage metrics of a pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"timestamp\": { SchemaProps: spec.SchemaProps{ Description: \"The following fields define time interval from which metrics were collected from the interval [Timestamp-Window, Timestamp].\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"window\": { SchemaProps: spec.SchemaProps{ Default: 0, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"containers\": { SchemaProps: spec.SchemaProps{ Description: \"Metrics for all containers are collected within the same time window.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/metrics/pkg/apis/metrics/v1alpha1.ContainerMetrics\"), }, }, }, }, }, }, Required: []string{\"timestamp\", \"window\", \"containers\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\", \"k8s.io/metrics/pkg/apis/metrics/v1alpha1.ContainerMetrics\"}, } } func schema_pkg_apis_metrics_v1alpha1_PodMetricsList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodMetricsList is a list of PodMetrics.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of pod metrics.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/metrics/pkg/apis/metrics/v1alpha1.PodMetrics\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/metrics/pkg/apis/metrics/v1alpha1.PodMetrics\"}, } } func schema_pkg_apis_metrics_v1beta1_ContainerMetrics(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"ContainerMetrics sets resource usage metrics of a container.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"name\": { SchemaProps: spec.SchemaProps{ Description: \"Container name corresponding to the one from pod.spec.containers.\", Default:     \"\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"usage\": { SchemaProps: spec.SchemaProps{ Description: \"The memory usage is the memory working set.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, }, Required: []string{\"name\", \"usage\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\"}, } } func schema_pkg_apis_metrics_v1beta1_NodeMetrics(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeMetrics sets resource usage metrics of a node.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"timestamp\": { SchemaProps: spec.SchemaProps{ Description: \"The following fields define time interval from which metrics were collected from the interval [Timestamp-Window, Timestamp].\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"window\": { SchemaProps: spec.SchemaProps{ Default: 0, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"usage\": { SchemaProps: spec.SchemaProps{ Description: \"The memory usage is the memory working set.\", Type:        []string{\"object\"}, AdditionalProperties: &spec.SchemaOrBool{ Allows: true, Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/apimachinery/pkg/api/resource.Quantity\"), }, }, }, }, }, }, Required: []string{\"timestamp\", \"window\", \"usage\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/api/resource.Quantity\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"}, } } func schema_pkg_apis_metrics_v1beta1_NodeMetricsList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"NodeMetricsList is a list of NodeMetrics.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of node metrics.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/metrics/pkg/apis/metrics/v1beta1.NodeMetrics\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/metrics/pkg/apis/metrics/v1beta1.NodeMetrics\"}, } } func schema_pkg_apis_metrics_v1beta1_PodMetrics(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodMetrics sets resource usage metrics of a pod.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\"), }, }, \"timestamp\": { SchemaProps: spec.SchemaProps{ Description: \"The following fields define time interval from which metrics were collected from the interval [Timestamp-Window, Timestamp].\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Time\"), }, }, \"window\": { SchemaProps: spec.SchemaProps{ Default: 0, Ref:     ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\"), }, }, \"containers\": { SchemaProps: spec.SchemaProps{ Description: \"Metrics for all containers are collected within the same time window.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/metrics/pkg/apis/metrics/v1beta1.ContainerMetrics\"), }, }, }, }, }, }, Required: []string{\"timestamp\", \"window\", \"containers\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.Duration\", \"k8s.io/apimachinery/pkg/apis/meta/v1.ObjectMeta\", \"k8s.io/apimachinery/pkg/apis/meta/v1.Time\", \"k8s.io/metrics/pkg/apis/metrics/v1beta1.ContainerMetrics\"}, } } func schema_pkg_apis_metrics_v1beta1_PodMetricsList(ref common.ReferenceCallback) common.OpenAPIDefinition { return common.OpenAPIDefinition{ Schema: spec.Schema{ SchemaProps: spec.SchemaProps{ Description: \"PodMetricsList is a list of PodMetrics.\", Type:        []string{\"object\"}, Properties: map[string]spec.Schema{ \"kind\": { SchemaProps: spec.SchemaProps{ Description: \"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"apiVersion\": { SchemaProps: spec.SchemaProps{ Description: \"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\", Type:        []string{\"string\"}, Format:      \"\", }, }, \"metadata\": { SchemaProps: spec.SchemaProps{ Description: \"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\", Default:     map[string]interface{}{}, Ref:         ref(\"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\"), }, }, \"items\": { SchemaProps: spec.SchemaProps{ Description: \"List of pod metrics.\", Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{ SchemaProps: spec.SchemaProps{ Default: map[string]interface{}{}, Ref:     ref(\"k8s.io/metrics/pkg/apis/metrics/v1beta1.PodMetrics\"), }, }, }, }, }, }, Required: []string{\"items\"}, }, }, Dependencies: []string{ \"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta\", \"k8s.io/metrics/pkg/apis/metrics/v1beta1.PodMetrics\"}, } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-72f2121d9c00ea31717a3620ac148f7960937c4f1fc6a8c75433d9055d46cc48", "text": "Checked in: Not checked in: Can anyone explain why?\nones published outside k/k that are in libraries/modules expected to be usable without running custom code generation steps are checked in\nexample issue: there were similar issues with other instances\n/triage accepted\nI guess I am asking why not check in\noh, I'd be in favor of that :)\ndownstream users very often end up realizing that we warn folks not to use ( ) because they go looking for why this file is not checked in. This paper cut makes people realize that they are doing something that we don't want them to do. (not arguing for or against, just stating where this was effective before)\nI think the v0.0.0 local replace directives in accomplish similar things w.r.t. making people go digging about friction using k/k as a library", "commid": "kubernetes_issue_107625", "tokennum": 173}], "negative_passages": []}
{"query_id": "q-en-kubernetes-33bad4d67c765f2267bb77f00ef6c87bc458558744b18d9e6066a3f0d733687a", "query": "} func (m *NsenterMounter) IsNotMountPoint(dir string) (bool, error) { <del> return IsNotMountPoint(m, dir) </del> <ins> return isNotMountPoint(m, dir) </ins> } func (*NsenterMounter) IsMountPointMatch(mp MountPoint, dir string) bool {", "positive_passages": [{"docid": "doc-en-kubernetes-4bcfc015d2b9d9fa1e84475a3e08fb9ef8299b4e5f821f790188ad7bdae6ecbc", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: There's , and . The former is used by local and nfs volume plugins, while the latter is used by , which is also used by local and nfs volume plugins. What you expected to happen: Can we consolidate these? This is really confusing and could easily be the source of bugs. <!-- DO NOT EDIT BELOW THIS LINE --/kind cleanup\ncc\n/assign I'd like to clean up code.", "commid": "kubernetes_issue_72387", "tokennum": 133}], "negative_passages": []}
{"query_id": "q-en-kubernetes-342c9361c2e7d59880056f2a38de69224cce2ac350e8575c9d5f9dbbba6cff9c", "query": "func (c *FakeNamespaces) Create(namespace *api.Namespace) (*api.Namespace, error) { c.Fake.Actions = append(c.Fake.Actions, FakeAction{Action: \"create-namespace\"}) <del> return &api.Namespace{}, nil </del> <ins> return &api.Namespace{}, c.Fake.Err </ins> } func (c *FakeNamespaces) Update(namespace *api.Namespace) (*api.Namespace, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-c343f6e7b091e9b4529e6227acb6329e7535006eb05bcc59008c8d5d37213826", "text": "While running one of my soak tests I noticed the error message: I don't see why I should get this error message. Why should it matter if the namespace already exists? It was created as part of the service creation call just beforehand. And the second attempt to create this pod in exactly the same namespace works. Is this a bug?\nRunning a second time did not produce this error.\nI agree it should not matter. The error is produced there, and I suspect there were multiple concurrent calls being made that try to create a resource in a namespace that had not yet existed. We need to update the code in question to swallow the error if the namespace already exists.\nFYI - longer term, I would like to eliminate the use of autoprovision of namespace and require you to first create a namespace manually. what is there now is more to preserve existing behavior prior to namespace as object was introduced.", "commid": "kubernetes_issue_5873", "tokennum": 190}], "negative_passages": []}
{"query_id": "q-en-kubernetes-347c4aab79cbcf5c19b48c2a9956694e5a66d40abaca408070600c2fcbf03d60", "query": "if !skipAnyOf { for i := range v.AnyOf { <del> allErrs = append(allErrs, validateNestedValueValidation(&v.AnyOf[i], false, false, fldPath.Child(\"anyOf\").Index(i))...) </del> <ins> allErrs = append(allErrs, validateNestedValueValidation(&v.AnyOf[i], false, false, lvl, fldPath.Child(\"anyOf\").Index(i))...) </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-4be11de3bdb9e2a86ad3a19c4d6f5342db422d48e5979c118fca9ce077f64900", "text": "We allow CRD authors to write . Currently we don't restrict writing validation for , which means people can have . For example, people can have additive name constraints (require CR to be ) with the following schema: This brings us two questions: do we if \"metadata\" is included in the schema: simplest option is to publish standard metav1.ObjectMeta schema info, and use any CRD-specified \"metadata\" properties as additive validation (just like in-tree types do, publishing standard ObjectMeta schema info, and implementing type-specific name validation internally) alternatively, we can try merging user-specified metadata schema with the standard one. Technically people should only add extra validation to existing metadata properties (adding new fields to metadata won't work since they will be pruned by built-in validation first), but it's unclear to me how arbitrary people may want the metadata validation to be term question is whether to allow people specifying metadata validation at all, or just allow a subset (like name validation) in CRD v1 /sig api-machinery /area custom-resources cc\nWhat is the difference between these two? I mean the end result is the same right? The only thing that can be is validation. Nothing else works unless you are considering extensions?\nThe former means we drop/hide user-specified metadata schema when we publish CRD OpenAPI. We still validate user-specified constraints on server side, but client-side validation won't see them. The latter enables client-side user-specified metadata validation.\nIf it's possible to merge with standard metadata schema info, or at the cost of not publishing the standard schema. My inclination would be to publish the complete standard schema for metadata/apiVersion/kind, which we know is complete and accurate, and use and user-specified schema for those fields as addition validations server side", "commid": "kubernetes_issue_74620", "tokennum": 396}], "negative_passages": []}
{"query_id": "q-en-kubernetes-348e0110b31fe4703f0242478c2963e2c01e10241cfc3c35c107a67fd8a226ad", "query": "return err } <del> if pod.Status.Phase != api.PodRunning { return fmt.Errorf(\"pod %s is not running and cannot execute commands; current phase is %s\", p.PodName, pod.Status.Phase) } </del> containerName := p.ContainerName if len(containerName) == 0 { glog.V(4).Infof(\"defaulting container name to %s\", pod.Spec.Containers[0].Name)", "positive_passages": [{"docid": "doc-en-kubernetes-b8cb95fef1c3c524a6b804cd28cd2236820a76e473144ffd27898d08f0344824", "text": "Need to finish so the client allows you to select an init container, and verify the kubelet works correctly.\n(this is a nice intersection of new in 1.3, node and usability, if anyone wants to give it a shot. Pretty sure Clayton is busier than I am and I don't think I'll get to it)\nWill be happy to review any changes - should be fairly straightforward.\nYes, init containers are \"run to completion\" always. , harryz wrote:\nIIUC when the init containers of pod have not complete, the pod should be in status, which means will fail, if init containers run to completion, they will exit, still fail. I don't know what you mean exec should work on init containers?\nthe init container is still up and running even when the pod is in pending, we should be able to exec and debug why it's hung, for example.\nadd a straightforward exec implementation ptal.", "commid": "kubernetes_issue_25818", "tokennum": 207}], "negative_passages": []}
{"query_id": "q-en-kubernetes-349c4d3109c7cd5f0628bf860c434cf7e60271e36f53499510fa881c6f84820e", "query": "cadvisorapi \"github.com/google/cadvisor/info/v1\" cadvisorapiv2 \"github.com/google/cadvisor/info/v2\" <ins> \"github.com/stretchr/testify/assert\" </ins> \"k8s.io/kubernetes/pkg/api\" apierrors \"k8s.io/kubernetes/pkg/api/errors\" \"k8s.io/kubernetes/pkg/api/resource\"", "positive_passages": [{"docid": "doc-en-kubernetes-b4459e221a04f6723f7b97c6a9d43d61c0d65417b08d143223c7057699636055", "text": "is this a Node bug? cc as next oncall to follow up on this.\nThis is a node bug due to init containers\nI may need help debugging - I see:\nSo I think the problem is in the error case - we're not properly recording that the start failed, and the next time we come in we somehow think the first container succeeded. I'll add some debugging to see if we can't recreate it.\nLet's discuss on instead.", "commid": "kubernetes_issue_25879", "tokennum": 102}], "negative_passages": []}
{"query_id": "q-en-kubernetes-349c4d3109c7cd5f0628bf860c434cf7e60271e36f53499510fa881c6f84820e", "query": "cadvisorapi \"github.com/google/cadvisor/info/v1\" cadvisorapiv2 \"github.com/google/cadvisor/info/v2\" <ins> \"github.com/stretchr/testify/assert\" </ins> \"k8s.io/kubernetes/pkg/api\" apierrors \"k8s.io/kubernetes/pkg/api/errors\" \"k8s.io/kubernetes/pkg/api/resource\"", "positive_passages": [{"docid": "doc-en-kubernetes-dcc88d1d89328d1da3366de828afcd8ab0373228cc4437ea655e2cda79030f86", "text": "Kubelet issues a docker inspect call after creating a container, but for very short lived containers there is a window in which they could exit before being inspected in the docker manager. If the container PID is 0, we should check the ExitCode and other relevant fields and handle them appropriately. [1] This is the suspected cause of several flakes: /cc\nlooking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: I'd expect the second one to not have run in this case? Node logs:\nInit containers have an implicit assumption that container statuses include results of previous SyncPod invocations. If that's not the case we may need to fix that (or at least mitigate it). On May 18, 2016, at 8:28 PM, Prashanth B wrote: looking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: May 18 15:58:33.380: INFO: pod-init--1d4b-11e6-80a4- started at 2016-05-18T15:58:04-07:00 (2+1 container statuses recorded) May 18 15:58:33.380: INFO: Init container init1 ready: false, restart count 0 May 18 15:58:33.380: INFO: Init container init2 ready: true, restart count 0 I'd expect the second one to not have run in this case? Node logs: \u2014 You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub\nThis should be true. Is there any evidence that suggests the opposite? only shows conflicting view of whether init1 has run.\nIf the container exits already and it's not an infra container, kubelet should not error out. Although even if it does, I failed to see how this could affect the readiness of the init container without checking the code further.", "commid": "kubernetes_issue_25844", "tokennum": 487}], "negative_passages": []}
{"query_id": "q-en-kubernetes-349c4d3109c7cd5f0628bf860c434cf7e60271e36f53499510fa881c6f84820e", "query": "cadvisorapi \"github.com/google/cadvisor/info/v1\" cadvisorapiv2 \"github.com/google/cadvisor/info/v2\" <ins> \"github.com/stretchr/testify/assert\" </ins> \"k8s.io/kubernetes/pkg/api\" apierrors \"k8s.io/kubernetes/pkg/api/errors\" \"k8s.io/kubernetes/pkg/api/resource\"", "positive_passages": [{"docid": "doc-en-kubernetes-ade5deee53831749acf4a20dbe39f9ef1836656ae43e40b0bb8594efa4e81e92", "text": "Each syncPod invocation, we inspect the list of init container in order looking for lastTerminationState. There could be a bug in that logic, or if we didn't get the full status, we might make a bad decision. When determining which container to run next, we always look for the last init container in the chain that has success, then run the next container (unless the pod is RestartNever). , Yu-Ju Hong wrote:\nSaw this flake again. How do we verify that container status is not lost between syn pods?\n... between calls to syncPods\nThe second sync clearly saw the init1 container, and decided to launch init2. See \"InitContainersToKeep\" in the message below.\ncontainers to keep can include failed containers. , Yu-Ju Hong wrote:\nDiscussed on slack. In summary, the problem has to do with how we convert the kubecontainer.PodStatus to the api.PodStatus. If a container is terminated, the function makes the decisions: the pod restart policy is \"Always\", and there is a \"failure reason\" recorded for the given container, this means the pod worker tried to (re)start the container but failed. Set the state to \"Waiting\" and populate the reason. , the container state is simply \"terminated\". Init containers don't obey the restart policy like regular containers, and the logic will need to be amended to work with them. is working on a PR. In addition to that, kubelet should not error out if a user container exited before it could apply the oom score (which is best effort in this case). fixes that.\nAhh, thanks for digging into the issue. This is the exact the concern I had when I reviewed the initial implementation of init container, which blocks pr for a while. I even asked to help me verify this case, unfortunately we didn't reproduce the issue back then. :-(\nI wish I'd seen the flakes in the runs prior to merge.\nWe didn't notice this until we started running the tests against docker v1.11.1, which is much faster and hit the race condition differently.\nI suppose that's a good thing...\nIt is hard to reproduce this.", "commid": "kubernetes_issue_25844", "tokennum": 482}], "negative_passages": []}
{"query_id": "q-en-kubernetes-349c4d3109c7cd5f0628bf860c434cf7e60271e36f53499510fa881c6f84820e", "query": "cadvisorapi \"github.com/google/cadvisor/info/v1\" cadvisorapiv2 \"github.com/google/cadvisor/info/v2\" <ins> \"github.com/stretchr/testify/assert\" </ins> \"k8s.io/kubernetes/pkg/api\" apierrors \"k8s.io/kubernetes/pkg/api/errors\" \"k8s.io/kubernetes/pkg/api/resource\"", "positive_passages": [{"docid": "doc-en-kubernetes-0814a4e75b48cf2d27d20141c180e04fbc9b55d5398cce31b037f460c93acb1b", "text": "The extra check of last terminated container in your initial code makes me nervous, but we couldn't reproduce it due to that small race windows until we have a faster docker running on the node. :-)\nI got \"Pods should invoke init containers on a RestartAlways pod\" flake (referenced from ): Logs:\nAll the fixes went in. Please reopen this issue if you see any more flakes.", "commid": "kubernetes_issue_25844", "tokennum": 90}], "negative_passages": []}
{"query_id": "q-en-kubernetes-34b1db609893c9db6feccc836b1756e6def8007e666ec7bfe8a4573f8598272a", "query": "container_image( name = \"image\", <del> base = \"@debian_jessie//image\", </del> <ins> base = \"@distroless_base//image\", </ins> entrypoint = [\"/kubemark\"], files = [\"//cmd/kubemark\"], stamp = True,", "positive_passages": [{"docid": "doc-en-kubernetes-d99484417892d904a3f5edbb73fa06d2de654c460b279ad73f511e028afa6a6f", "text": "There are CVEs happening in different images - we already migrated Kubmeark from busybox in , but we should go one step further and migrate the base image to distroless. There are some things that would need to be changed mentioned here: /sig scalability\nCan I work on this? /assign\n/remove-help\n- sure that would be great.\nHi based on the discussion in , the kubemark image has dependency on and maybe more other utilities. So it seems impossible to migrate the base image to distroless? Or do we need something like debian-hyperkube-base?\nThe mount one we may get rid of - basically we should be able to switch to FakeMounter:", "commid": "kubernetes_issue_84284", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-34dbcebdf6287f1b6b0c1cc12aa62454efb514a5a6304012604c04caca4d0571", "query": "\"k8s.io/component-base/metrics\" \"k8s.io/klog/v2\" podutil \"k8s.io/kubernetes/pkg/api/v1/pod\" <del> \"k8s.io/kubernetes/pkg/apis/apps\" </del> kubecontainer \"k8s.io/kubernetes/pkg/kubelet/container\" \"k8s.io/kubernetes/pkg/kubelet/prober/results\" )", "positive_passages": [{"docid": "doc-en-kubernetes-8720ed8a574bdce7c104bd3a62cc93935fad36eef53bf2f2ff98186bbe4abc40", "text": "The metric used to report acutal pod in the label , but now I see the podname prefix only. The full pod name in the label, so I can trace the metric to the failing pod. Check raw api and verify the actual pod name with uids. <details</detailsAzure AKS <details</detailsNo response No response No response_\n/sig node\n/triage accepted /priority important-soon /cc As discussed this is a change in functionaloty that wasn't highlighted in release notes. Need to decide on what do do with it. I understand it's a change of functionality. what is the side effect of this for you? Does the label without last part not informational enough?\nI've been using the metric in my custom grafana dashboard that shows CPU, RAM, IO usage of pods with graph of increases in probes. If the apps are stable, the probe graph looks steadily. I can see if some irregularities in system metrics are influencing probes of respective pod. Also, if readiness probe is failing, the pod is removed from service, but is not restarted so I must have knowledge of pods with failing readiness probes. I attach the screenshot of my graph. ! So I'd welcome the possibility to pair the probes with exact pod and thank you for looking into it.\nare we thinking that this resulted in an undesirable change? Spologies for being a bit late to reply, I'm returning from a brief paternity leave staycation.\nThis issue is labeled with but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release. You can: Confirm that this issue is still relevant with (org members only) Deprioritize it with or Close this issue with For more details on the triage process, see /remove-triage accepted\nWell this is awkward... I still believe the actual behavior does not respect the intended idea...\nThis issue makes it hard to link probe metrics with right pods. The value of pod label in and are also inconsistent with how it is used in other kubelet metrics, see: vs Definitely a bug, regression since 1.25.\nI can't get anyone to look at the fix/revert: you may have better luck\n/milestone v1.28\ndiscussion in\nYou've pushed it through, congrats!", "commid": "kubernetes_issue_115766", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-34e02a5b7da66294cb151af0a44c835598af80991b68a79683dc0a8d48e622e2", "query": "legacyregistry.MustRegister(DeprecatedEvictionStatsAge) legacyregistry.MustRegister(DeprecatedDevicePluginRegistrationCount) legacyregistry.MustRegister(DeprecatedDevicePluginAllocationLatency) <ins> legacyregistry.MustRegister(RunningContainerCount) legacyregistry.MustRegister(RunningPodCount) </ins> if utilfeature.DefaultFeatureGate.Enabled(features.DynamicKubeletConfig) { legacyregistry.MustRegister(AssignedConfig) legacyregistry.MustRegister(ActiveConfig)", "positive_passages": [{"docid": "doc-en-kubernetes-3f173d1022a4408031efac17c8299f04d835794ab8a77d69bb7667b0107a08bf", "text": "Some kubelet metrics use non-standard prometheus collectors unnecessarily. Specifically, we have which can be simple gauges. Since we cannot migrate non-standard prometheus collectors using the internal metrics stability framework, we will need to convert these metrics into standard prometheus variants. /sig instrumentation /assign\nGitHub didn't allow me to assign the following users: solodov. Note that only and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : Some kubelet metrics use non-standard prometheus collectors unnecessarily. Specifically, we have which can be simple gauges. Since we cannot migrate non-standard prometheus collectors using the internal metrics stability framework, we will need to convert these metrics into standard prometheus variants. /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\nrecommends that we generate those metrics in the GenericPLEG during the relist. We can generate the data directly from the pods call there ().\nI would be interested to work on this issue if no one else is working on it currently\nGo for it!\n/assign", "commid": "kubernetes_issue_79286", "tokennum": 282}], "negative_passages": []}
{"query_id": "q-en-kubernetes-34eccb00d5bf9b5a048c81483bbb86767f3c72eff597896c1e51e280c35a75a3", "query": "apiVersion: v1 metadata: name: etcd <del> creationTimestamp: </del> labels: name: etcd spec:", "positive_passages": [{"docid": "doc-en-kubernetes-970debf69dc4e7e663c051298279ebf93b58654f6c393d8683796c73cb4f1c74", "text": "Kubernetes version (use ): Environment: Cloud provider or hardware configuration: Vagrant OS (e.g. from /etc/os-release): CoreOS Kernel (e.g. ):Install tools: Vagrant & Others: What happened: What you expected to happen: Success How to reproduce it (as minimally and precisely as possible): Followed instructions at Tried to run Received: Anything else do we need to know: From googling, it seems several of the fields in the config are for when using OpenShift origin. But creating the replication controller is a prerequisite to launching OpenShift Origin. Chicken & egg problem.", "commid": "kubernetes_issue_39575", "tokennum": 138}], "negative_passages": []}
{"query_id": "q-en-kubernetes-34f37d15d7a8f3ca09b4bf1299978ea7cd33e88eb42c78341b1d5832db8a7f6b", "query": "kubetypes.HTTPSource, &api.Pod{ ObjectMeta: api.ObjectMeta{ <del> UID:       \"111\", Name:      \"foo\" + \"-\" + hostname, Namespace: \"default\", SelfLink: getSelfLink(\"foo-\"+hostname, kubetypes.NamespaceDefault), </del> <ins> UID:         \"111\", Name:        \"foo\" + \"-\" + hostname, Namespace:   \"default\", Annotations: map[string]string{kubetypes.ConfigHashAnnotationKey: \"111\"}, SelfLink:    getSelfLink(\"foo-\"+hostname, kubetypes.NamespaceDefault), </ins> }, Spec: api.PodSpec{ NodeName:                      hostname,", "positive_passages": [{"docid": "doc-en-kubernetes-8bc8d69d49aedfb4a9bf3991de80f7c339e96bfbefe5b1f250dae70fa0393729", "text": "See for more context. Currently, kubelet compares the spec of a mirror pod (created via apiserver) with that of a static pod (config stored as a file) to decide whether the two are considered identical. If they differ, kubelet would delete the mirror pod and re-create it with the correct spec. Due to the fact that apiserver may set default values for some fields in the spec of the mirror pod, the specs could deviate undesirably. To avoid problems like this, we can store the config of a static pod as an annotation in the mirror pod, and compare the static pod with the annotation.\nWould a hash of the config be sufficient if we're only going to compare? The whole spec would generally be more useful, but I wonder if that is too much data to put in an annotation.\nThis seems totally reasonable to me, but I'm still desperately curious why you can't just bypass defaulting when you generate mirror pod from static pod? (i.e. just use the static pod's configuration verbatim)\nIt's not kubelet who applies the default values here. The admission plugin was only run at the apiserver, and to bypass that, you have to ask apiserver to treat mirror pods differently and potentially at multiple places.\nOn May 22, 2015 10:38 AM, \"Yu-Ju Hong\" wrote: Understood, but is it really multiple places? If so then I agree it's a bad idea. Otherwise it might be worth considering as an alternative.\nIt's untenable for Kubelet to assume to know/circumvent all fields that will be set by other entities: admission control, defaulting, late initialization, auto-something, whatever. It needs to obey the same rules as other clients.\nI don't understand why you would ever want to apply any of the things you mentioned to static pods. Static pods should be copied verbatim into the mirror pods, right? That's what I'm proposing.\nWhat if the master is updated before the kubelet, and the master adds a new API field with a default value?\nThat case should be discussed in\nI agree that mirror pod should reflect the true status of the static pod running on the node, and no default values should be set in this case.", "commid": "kubernetes_issue_8683", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-34f37d15d7a8f3ca09b4bf1299978ea7cd33e88eb42c78341b1d5832db8a7f6b", "query": "kubetypes.HTTPSource, &api.Pod{ ObjectMeta: api.ObjectMeta{ <del> UID:       \"111\", Name:      \"foo\" + \"-\" + hostname, Namespace: \"default\", SelfLink: getSelfLink(\"foo-\"+hostname, kubetypes.NamespaceDefault), </del> <ins> UID:         \"111\", Name:        \"foo\" + \"-\" + hostname, Namespace:   \"default\", Annotations: map[string]string{kubetypes.ConfigHashAnnotationKey: \"111\"}, SelfLink:    getSelfLink(\"foo-\"+hostname, kubetypes.NamespaceDefault), </ins> }, Spec: api.PodSpec{ NodeName:                      hostname,", "positive_passages": [{"docid": "doc-en-kubernetes-0491e123884f0f20f50d0a788bca7a6a29e2fa08227703a00221ecbd3bcf483c", "text": "However, I think it'd be harder to implement this way since, as stated above, that there are many things to circumvent in the apiserver itself. It could also be harder to keep this special case from being broken by a yet another new feature/plugin. Keeping the hash of the config in the annotation seems like a good compromise even though it may not reflect the true status 100% accurately. I think this is acceptable. What do you think?\nSure, if you think the annotation approach is easier, I would go with that. I guess in the case Brian mentoined (master adds a new API field with a default value), you would not update the mirror pod, because the static pod definition has not changed?\nYes, a hash would be sufficient.\nIt shouldn't be necessary to update the mirror pod in the case that a new default field was updated, because that field should be populated automatically by the apiserver on decode from etcd.\nWe should fix this so we don't have this problem again in 1.2.", "commid": "kubernetes_issue_8683", "tokennum": 226}], "negative_passages": []}
{"query_id": "q-en-kubernetes-35016b66d26f4ef184857bc4bd1bd7df6d843312248a0d521a249e285ec92d9b", "query": "test.TestDynamicProvisioning() } <del> // Run the last test with storage.k8s.io/v1beta1 on pvc if betaTest != nil { ginkgo.By(\"Testing \" + betaTest.Name + \" with beta volume provisioning\") betaClass := newBetaStorageClass(*betaTest, \"beta\") // create beta class manually betaClass, err := c.StorageV1beta1().StorageClasses().Create(context.TODO(), betaClass, metav1.CreateOptions{}) framework.ExpectNoError(err) defer deleteStorageClass(c, betaClass.Name) // fetch V1beta1 StorageClass as V1 object for the test class, err := c.StorageV1().StorageClasses().Get(context.TODO(), betaClass.Name, metav1.GetOptions{}) framework.ExpectNoError(err) betaTest.Client = c betaTest.Class = class betaTest.Claim = e2epv.MakePersistentVolumeClaim(e2epv.PersistentVolumeClaimConfig{ ClaimSize:        betaTest.ClaimSize, StorageClassName: &class.Name, VolumeMode:       &betaTest.VolumeMode, }, ns) betaTest.Claim.Spec.StorageClassName = &(class.Name) (*betaTest).TestDynamicProvisioning() } </del> }) ginkgo.It(\"should provision storage with non-default reclaim policy Retain\", func() {", "positive_passages": [{"docid": "doc-en-kubernetes-e2f4fe7b99012f8e7173e2f6c46ef5707967f19510033d4b6b03e3a31c7298f0", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --ci-kubernetes-e2e-gci-gce-slow [sig-storage] Dynamic Provisioning DynamicProvisioner [Slow] should provision storage with different parameters 5/13 https://k8s- v1beta1.StorageClass got removed in We should remove the v1beta1 test.\n/assign can you help take a look?\n/triage accepted\n/sig storage\nI run the test with the latest from master without removing the beta test and it failed with a different error before getting to the beta test part: Do you have any idea what would've happened in my setup? I redeployed k/k using master HEAD\nFor this testcase: I saw that the provisioned PD has a size of 1.5Gi according to kubernetes: And in gcloud It's really interesting that the test was expecting 2Gi to be created, is this something that was changed recently?\nThe logs you posted are showing pd csi as the provisioner. Were you testing with the intree driver or csi driver? The CSI driver should to the nearest Gb. I believe intree does the .\nI think I did intree because I didn't send as an argument in my command: It's interesting that the PVC has this annotation too:\nmmm something interesting about my setup is that I created the cluster with CSIMigration turned on Do you think that might be forcing the usage of ?\nYes likely. Try with CSIMigration off and see if that helps. If so, then this potentially seems like a rounding bug with the csi driver\nThanks I tried with and it did indeed round up to 2Gi.", "commid": "kubernetes_issue_102076", "tokennum": 373}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3513f85dac3a7920903be8eb6fcef92ce620a6a8caea40b3e1d09f7ba9913fe2", "query": "IP address. release: v1.9 file: test/e2e/common/pods.go <ins> - testname: Pods, completes the lifecycle of a Pod and the PodStatus codename: '[k8s.io] Pods should run through the lifecycle of Pods and PodStatus [Conformance]' description: A Pod is created with a static label which MUST succeed. It MUST succeed when patching the label and the pod data. When checking and replacing the PodStatus it MUST succeed. It MUST succeed when deleting the Pod. release: v1.20 file: test/e2e/common/pods.go </ins> - testname: Pods, remote command execution over websocket codename: '[k8s.io] Pods should support remote command execution over websockets [NodeConformance] [Conformance]'", "positive_passages": [{"docid": "doc-en-kubernetes-a4e08d4660e59e77b869eee3e8c161e5e01175b90d68e1077fd3e84d4f4d567b", "text": "[x] Original approval issue: - Reverted due to flakes [x] Two weeks soak end date: 20 November 2020 This issue is created to allow edit by /wip /hold According to this APIsnoop query, there are still some remaining Pod endpoints which are untested. a Pod with a static label the Pod with a new Label and updated data the Pod to ensure it's patched the Pod's status the Pod's status Ready condition to False the Pod's status to check if Ready is False all Pods in all Namespaces find the Pod(1) ensure that the Pod is found and is patched Namespaced Pod(1) via a Collection with a LabelSelector the Pod to check that it's deleted Discover useragents: List endpoints hit by the test: Display endpoint coverage change: If a test with these calls gets merged, test coverage will go up by 4 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance\n/reopen Test PR Merge Promotion PR to be created next\nReopened this issue. <detailsIn response to : /reopen Test PR Merge Promotion PR to be created next 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\nreverted by due to flaky test\nIssues 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\n/remove-lifecycle stale\n/reopen PR on test grid for 2 weeks before promotion to conformance\nReopened this issue. <detailsIn response to : /reopen PR on test grid for 2 weeks before promotion to conformance 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\n/triage accepted", "commid": "kubernetes_issue_90936", "tokennum": 449}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3542685ad49b859bacfd8519a0a49e179d869b194fda484b9e595a6bfcfb5c08", "query": "fi } <del> function kube::build::probe_address { # Apple has an ancient version of netcat with custom timeout flags.  This is # the best way I (jbeda) could find to test for that. local netcat if nc 2>&1 | grep -e 'apple' >/dev/null ; then netcat=\"nc -G 1\" else netcat=\"nc -w 1\" fi </del> <ins> function kube::build::rsync_probe { </ins> # Wait unil rsync is up and running. <del> if ! which nc >/dev/null ; then V=6 kube::log::info \"netcat not installed, waiting for 1s\" sleep 1 return 0 fi local tries=10 </del> <ins> local tries=20 </ins> while (( ${tries} > 0 )) ; do <del> if ${netcat} -z \"$1\" \"$2\" 2> /dev/null ; then </del> <ins> if rsync \"rsync://k8s@${1}:${2}/\"  --password-file=\"${LOCAL_OUTPUT_BUILD_CONTEXT}/rsyncd.password\"  &> /dev/null ; then </ins> return 0 fi tries=$(( ${tries} - 1))", "positive_passages": [{"docid": "doc-en-kubernetes-23c92439a8a6a56c88d16c6d832940b868e99c5934b866ad407565ebf4fae31b", "text": "https://k8s-\nI have a similar problem when I try to make release on my local desktop:\nRelated to .\nSimilar problem for :\nCan you open a new issue for your problem with information about your set up. Mac/Linux? Docker version? etc.\nPlease add details to (to be opened) issue. I suspect that is a different issue.\nNew issue:", "commid": "kubernetes_issue_34214", "tokennum": 79}], "negative_passages": []}
{"query_id": "q-en-kubernetes-354db570601e13fc384cb5144ecf95810d7bef21f789346140998874cde1e22c", "query": "echo \"ELASTICSEARCH_LOGGING_REPLICAS='${ELASTICSEARCH_LOGGING_REPLICAS:-1}'\" echo \"ENABLE_NODE_LOGGING='${ENABLE_NODE_LOGGING:-false}'\" echo \"ENABLE_CLUSTER_UI='${ENABLE_CLUSTER_UI}'\" <ins> echo \"ENABLE_HOSTPATH_PROVISIONER='${ENABLE_HOSTPATH_PROVISIONER:-false}'\" </ins> echo \"LOGGING_DESTINATION='${LOGGING_DESTINATION:-}'\" echo \"ENABLE_CLUSTER_DNS='${ENABLE_CLUSTER_DNS:-false}'\" echo \"DNS_SERVER_IP='${DNS_SERVER_IP:-}'\"", "positive_passages": [{"docid": "doc-en-kubernetes-ef45ff070b2c05a069c3f77b9a64e0bfff59d1f717362ac04203c879e5a7b68c", "text": "feature request Enables easier testing for pv/pvc, and all derivatives like pet sets. The only alternative is to use manually created pv of local type. I have time to work on it myself and created this feature to collect feedback/ideas on what provider should be enabled by default.\nSince this was merged should we close this issue?", "commid": "kubernetes_issue_32119", "tokennum": 67}], "negative_passages": []}
{"query_id": "q-en-kubernetes-35b8fb491be5496ff5e6a1d48f7f003b5c1296fd37792a8c07020786e7b4989f", "query": "// Never send a bookmark event if we did not see an event here, this is fine // because we don't provide any guarantees on sending bookmarks. if lastProcessedResourceVersion == 0 { <ins> // pop expired watchers in case there has been no update c.bookmarkWatchers.popExpiredWatchers() </ins> continue } bookmarkEvent := &watchCacheEvent{", "positive_passages": [{"docid": "doc-en-kubernetes-c66c9bab938b839459ac01dfd08140ea19c2b9a1199fe50a2b49f94fd9cbbbfb", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: I try to backport bookmark feature to our internal branch. When I enable bookmark feature, apiserver leaks memory. I spend some time to dig the root cause and find the bookmarkWatchers of service cacher is keep increasing. I am not sure if it exists at upstream code. Please let me know if it is ok at latest code. What you expected to happen: Avoid memory leaking How to reproduce it (as minimally and precisely as possible): a cluster. not update service. will find kube-apiserver's memory keep increasing. Anything else we need to know?: Kubelet will watch service with bookmark, and add a watcher to bookmarkWatchers. and service init resource version is 0 Without updating service, we cannot update \"lastProcessedResourceVersion\", it will keep 0, bookmarkTimer branch will always be continued. As a result, it cannot trigger popExpiredWatchers, so the service watcher will keep increasing every watching. Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig scalability PLAT :)\nHow about making this change ?\n- can you also please take a look?\nAgree with u. That's same way I fix in our branch. But I wanna hear the suggestion of and .\n! With the same bugfix wrote above, we can see the memory not increasing any more.\nGiven that watch-bookmarks doesn't create any additional go-routines (well, creates 1, but cannot leak them), it has to leak the data. The only data that can be leaked is exactly bookmarkWatchers. So I looked into the code and got into exactly the same conclusion - that we must be leaking watchers for resources that aren't changing. The fix as above makes sense (though we also need a unit test for it).\nThanks a lot.\nhas the fix by\nThanks for reporting the bug, I will look at this day later. In addition, also need to think carefully about whether need to send a bookmark when there are no events at all.\ncc", "commid": "kubernetes_issue_80690", "tokennum": 531}], "negative_passages": []}
{"query_id": "q-en-kubernetes-35e0a3b29594f9333b5e3817fc779e87008fca50794054005a061efef5be9903", "query": "\"where N means number of retries allowed for kubelet to post node status.\") fs.Float32Var(&o.NodeEvictionRate, \"node-eviction-rate\", 0.1, \"Number of nodes per second on which pods are deleted in case of node failure when a zone is healthy (see --unhealthy-zone-threshold for definition of healthy/unhealthy). Zone refers to entire cluster in non-multizone clusters.\") fs.Float32Var(&o.SecondaryNodeEvictionRate, \"secondary-node-eviction-rate\", 0.01, \"Number of nodes per second on which pods are deleted in case of node failure when a zone is unhealthy (see --unhealthy-zone-threshold for definition of healthy/unhealthy). Zone refers to entire cluster in non-multizone clusters. This value is implicitly overridden to 0 if the cluster size is smaller than --large-cluster-size-threshold.\") <del> fs.Int32Var(&o.LargeClusterSizeThreshold, \"large-cluster-size-threshold\", 50, fmt.Sprintf(\"Number of nodes from which %s treats the cluster as large for the eviction logic purposes. --secondary-node-eviction-rate is implicitly overridden to 0 for clusters this size or smaller.\", names.NodeLifecycleController)) </del> <ins> fs.Int32Var(&o.LargeClusterSizeThreshold, \"large-cluster-size-threshold\", 50, fmt.Sprintf(\"Number of nodes from which %s treats the cluster as large for the eviction logic purposes. --secondary-node-eviction-rate is implicitly overridden to 0 for clusters this size or smaller. Notice: If nodes reside in multiple zones, this threshold will be considered as zone node size threshold for each zone to determine node eviction rate independently.\", names.NodeLifecycleController)) </ins> fs.Float32Var(&o.UnhealthyZoneThreshold, \"unhealthy-zone-threshold\", 0.55, \"Fraction of Nodes in a zone which needs to be not Ready (minimum 3) for zone to be treated as unhealthy. \") }", "positive_passages": [{"docid": "doc-en-kubernetes-c2ab3144aef8ccfdc5bfa24e077aa0687e2812de3da5460311eb2f2561c37ff3", "text": "The arg large-cluster-size-threshold for kube-controller-manager works as zone size threshold when determining node eviction rate. If there are multiple zones, the description for arg stating \"cluster\" threshold would be missleading. ARG: Matched arg description Multiple zones cluster No response <details</details<details</details<details</details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig docs", "commid": "kubernetes_issue_119499", "tokennum": 184}], "negative_passages": []}
{"query_id": "q-en-kubernetes-35eca94cde7b60ab94f4d26a9c3590c2010412ecc148af4691d36e859ee4183d", "query": "// +optional optional string workingDir = 5; <del> // List of ports to expose from the container. Exposing a port here gives // the system additional information about the network connections a // container uses, but is primarily informational. Not specifying a port here </del> <ins> // List of ports to expose from the container. Not specifying a port here </ins> // DOES NOT prevent that port from being exposed. Any port which is // listening on the default \"0.0.0.0\" address inside a container will be // accessible from the network. <ins> // Modifying this array with strategic merge patch may corrupt the data. // For more information See https://github.com/kubernetes/kubernetes/issues/108255. </ins> // Cannot be updated. // +optional // +patchMergeKey=containerPort", "positive_passages": [{"docid": "doc-en-kubernetes-754763163ccf179fd132c393411aa2d267e649990c98a81bb38938ec6debc8b2", "text": "The comments in says that : However there are several cases where this is false : When using a Service with a targetPort that references a name in the ports arrays of the pod. Some software (ab)uses this API to get which ports are used (See Although unfixable, my goal is to fix the documentation so other people don't have the same problem). The Azure Load Balancer implementation does this for instance. Some other network/security software might use this information. Also, is it possible to document/reference the above issue in the comment ? Since it is described as informational I expected for the network to work without this information. But it's definitely not the case. Not needed since it's mostly a doc issue. I'm interested in contributing this patch but would like some feedbacks before doing it. :) <details</details<details</details<details</details<details</details<details</details<details</details\n/sig network\n/triage accepted -- thoughts? I believe the doc are due for a refresh.\nI'd take this one. /assign\nI didn't see that you wanted to do this patch, I am very sorry and now I unassign it. /unassign\nNo worries But I'm still not sure where / what to add. Should I only fix the part saying it is only informational ? Is there anything else ? (cc\nThe 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]:\n/remove-lifecycle stale", "commid": "kubernetes_issue_108255", "tokennum": 435}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3655b8fce8ba29c712d6a02c9e002600bd6802c76355f66745da10b259bbd5fd", "query": "} return ret } <del> func getPodLabelName(pod *v1.Pod) string { podName := pod.Name if pod.GenerateName != \"\" { podNameSlice := strings.Split(pod.Name, \"-\") podName = strings.Join(podNameSlice[:len(podNameSlice)-1], \"-\") if label, ok := pod.GetLabels()[apps.DefaultDeploymentUniqueLabelKey]; ok { podName = strings.ReplaceAll(podName, fmt.Sprintf(\"-%s\", label), \"\") } } return podName } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-8720ed8a574bdce7c104bd3a62cc93935fad36eef53bf2f2ff98186bbe4abc40", "text": "The metric used to report acutal pod in the label , but now I see the podname prefix only. The full pod name in the label, so I can trace the metric to the failing pod. Check raw api and verify the actual pod name with uids. <details</detailsAzure AKS <details</detailsNo response No response No response_\n/sig node\n/triage accepted /priority important-soon /cc As discussed this is a change in functionaloty that wasn't highlighted in release notes. Need to decide on what do do with it. I understand it's a change of functionality. what is the side effect of this for you? Does the label without last part not informational enough?\nI've been using the metric in my custom grafana dashboard that shows CPU, RAM, IO usage of pods with graph of increases in probes. If the apps are stable, the probe graph looks steadily. I can see if some irregularities in system metrics are influencing probes of respective pod. Also, if readiness probe is failing, the pod is removed from service, but is not restarted so I must have knowledge of pods with failing readiness probes. I attach the screenshot of my graph. ! So I'd welcome the possibility to pair the probes with exact pod and thank you for looking into it.\nare we thinking that this resulted in an undesirable change? Spologies for being a bit late to reply, I'm returning from a brief paternity leave staycation.\nThis issue is labeled with but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release. You can: Confirm that this issue is still relevant with (org members only) Deprioritize it with or Close this issue with For more details on the triage process, see /remove-triage accepted\nWell this is awkward... I still believe the actual behavior does not respect the intended idea...\nThis issue makes it hard to link probe metrics with right pods. The value of pod label in and are also inconsistent with how it is used in other kubelet metrics, see: vs Definitely a bug, regression since 1.25.\nI can't get anyone to look at the fix/revert: you may have better luck\n/milestone v1.28\ndiscussion in\nYou've pushed it through, congrats!", "commid": "kubernetes_issue_115766", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-36749558b5c0ed53eedb28025a1643878495b1cbc4777220d6d4c9f133705299", "query": "} // If the container logs directory does not exist, create it. <del> if _, err := os.Stat(containerLogsDir); err != nil { if err := kl.os.MkdirAll(containerLogsDir, 0755); err != nil { glog.Errorf(\"Failed to create directory %q: %v\", containerLogsDir, err) </del> <ins> if _, err := os.Stat(ContainerLogsDir); err != nil { if err := kl.os.MkdirAll(ContainerLogsDir, 0755); err != nil { glog.Errorf(\"Failed to create directory %q: %v\", ContainerLogsDir, err) </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-0ad427ca9c00c618017f4be9fb19a1df6f4ab39ddc68f128fc109eb4d0409cbf", "text": "Cluster logging assumes kubelet stores container log at a specific directory with specific name. Currently the path is: After the CRI work, the path will be: However, we don't have test coverage for this. We don't even know whether the log files are there or not. We should add a node e2e test for this, basically: 1) Create a container which prints logs 2) Check whether the expected log file is created. 3) Check whether the logs are collected in the file as expected. And it would be better to launch a pod to do the check instead of accessing local file system directly, which makes containerizing easier. /cc because you are collecting missing test. /cc\nI will try to add a node-e2e test there\nI think it's ok to add this for CRI. But there maybe problems on today's interface for rkt. If I'm not wrong, rkt does't store logs at same location with docker. cc/ Is this true?\nThanks! :)\nAfter gets merged, we need to update the test to verify the cri log path.", "commid": "kubernetes_issue_34661", "tokennum": 234}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3695384e62b2baf2d31d13f6dc1f2f767082472ed5aecee1c63d18514ef36611", "query": "// wait until new webhook is called the first time if err := wait.PollImmediate(time.Millisecond*5, wait.ForeverTestTimeout, func() (bool, error) { <del> _, err = client.CoreV1().Pods(\"default\").Patch(reinvocationMarkerFixture.Name, types.JSONPatchType, []byte(\"[]\")) </del> <ins> _, err = client.CoreV1().Pods(markerNs).Patch(marker.Name, types.JSONPatchType, []byte(\"[]\")) </ins> select { case <-upCh: return true, nil", "positive_passages": [{"docid": "doc-en-kubernetes-ddb9bacde18c9f97d2ebd4306efde2d358d8075e932023fee86edf729006549a", "text": "Which jobs are failing: Which test(s) are failing: Since when has it been failing: Testgrid link: Reason for failure: Anything else we need to know: /sig api-machinery /assign\n/cc\nwant to take a look at the audit event issue first? I can dig in after that if issues remain.\nyes, I'm looking at the audit event issue now\nactually the failure message suggests that the missing audit log is caused by unexpected admission invocation: I think it's unrelated to auditing Note that there are two tests named \"no reinvocation of webhook B when in-tree or prior webhook mutations\" :( and from the audit log (), it also suggests that the test is hitting a wrong endpoint\nThanks I'll dig in.", "commid": "kubernetes_issue_82693", "tokennum": 163}], "negative_passages": []}
{"query_id": "q-en-kubernetes-36cea03b6c0d18b42b316d857d137b1e6afbce0320660f7682c4e5fa621a10b0", "query": "<ins> # Development Guide # Releases and Official Builds Official releases are built in Docker containers.  Details are [here](build/README.md).  You can do simple builds and development with just a local Docker installation.  If want to build go locally outside of docker, please continue below. ## Go development environment Kubernetes is written in [Go](http://golang.org) programming language. If you haven't set up Go development environment, please follow [this instruction](http://golang.org/doc/code.html) to install go tool and set up GOPATH. Ensure your version of Go is at least 1.3. ## Put kubernetes into GOPATH We highly recommend to put kubernetes' code into your GOPATH. For example, the following commands will download kubernetes' code under the current user's GOPATH (Assuming there's only one directory in GOPATH.): ``` $ echo $GOPATH /home/user/goproj $ mkdir -p $GOPATH/src/github.com/GoogleCloudPlatform/ $ cd $GOPATH/src/github.com/GoogleCloudPlatform/ $ git clone git@github.com:GoogleCloudPlatform/kubernetes.git ``` The commands above will not work if there are more than one directory in ``$GOPATH``. (Obviously, clone your own fork of Kubernetes if you plan to do development.) ## godep and dependency management Kubernetes uses [godep](https://github.com/tools/godep) to manage dependencies. It is not strictly required for building Kubernetes but it is required when managing dependencies under the Godeps/ tree, and is required by a number of the build and test scripts. Please make sure that ``godep`` is installed and in your ``$PATH``. ### Installing godep There are many ways to build and host go binaries. Here is an easy way to get utilities like ```godep``` installed: 1. Ensure that [mercurial](http://mercurial.selenic.com/wiki/Download) is installed on your system. (some of godep's dependencies use the mercurial source control system).  Use ```apt-get install mercurial``` or ```yum install mercurial``` on Linux, or [brew.sh](http://brew.sh) on OS X, or download directly from mercurial. 2. Create a new GOPATH for your tools and install godep: ``` export GOPATH=$HOME/go-tools mkdir -p $GOPATH go get github.com/tools/godep ``` 3. Add $GOPATH/bin to your path. Typically you'd add this to your ~/.profile: ``` export GOPATH=$HOME/go-tools export PATH=$PATH:$GOPATH/bin ``` ### Using godep Here is a quick summary of `godep`.  `godep` helps manage third party dependencies by copying known versions into Godeps/_workspace.  You can use `godep` in three ways: 1. Use `godep` to call your `go` commands.  For example: `godep go test ./...` 2. Use `godep` to modify your `$GOPATH` so that other tools know where to find the dependencies.  Specifically: `export GOPATH=$GOPATH:$(godep path)` 3. Use `godep` to copy the saved versions of packages into your `$GOPATH`.  This is done with `godep restore`. We recommend using options #1 or #2. ## Hooks Before committing any changes, please link/copy these hooks into your .git directory. This will keep you from accidentally committing non-gofmt'd go code. ``` cd kubernetes ln -s hooks/prepare-commit-msg .git/hooks/prepare-commit-msg ln -s hooks/commit-msg .git/hooks/commit-msg ``` ## Unit tests ``` cd kubernetes hack/test-go.sh ``` Alternatively, you could also run: ``` cd kubernetes godep go test ./... ``` If you only want to run unit tests in one package, you could run ``godep go test`` under the package directory. For example, the following commands will run all unit tests in package kubelet: ``` $ cd kubernetes # step into kubernetes' directory. $ cd pkg/kubelet $ godep go test # some output from unit tests PASS ok      github.com/GoogleCloudPlatform/kubernetes/pkg/kubelet   0.317s ``` ## Coverage ``` cd kubernetes godep go tool cover -html=target/c.out ``` ## Integration tests You need an etcd somewhere in your PATH. To install etcd, run: ``` cd kubernetes hack/install-etcd.sh sudo ln -s $(pwd)/third_party/etcd/bin/etcd /usr/bin/etcd ``` ``` cd kubernetes hack/test-integration.sh ``` ## End-to-End tests You can run an end-to-end test which will bring up a master and two minions, perform some tests, and then tear everything down. Make sure you have followed the getting started steps for your chosen cloud platform (which might involve changing the `KUBERNETES_PROVIDER` environment variable to something other than \"gce\". ``` cd kubernetes hack/e2e-test.sh ``` Pressing control-C should result in an orderly shutdown but if something goes wrong and you still have some VMs running you can force a cleanup with the magical incantation: ``` hack/e2e-test.sh 1 1 1 ``` ## Testing out flaky tests [Instructions here](docs/devel/flaky-tests.md) ## Add/Update dependencies Kubernetes uses [godep](https://github.com/tools/godep) to manage dependencies. To add or update a package, please follow the instructions on [godep's document](https://github.com/tools/godep). To add a new package ``foo/bar``: - Make sure the kubernetes' root directory is in $GOPATH/github.com/GoogleCloudPlatform/kubernetes - Run ``godep restore`` to make sure you have all dependancies pulled. - Download foo/bar into the first directory in GOPATH: ``go get foo/bar``. - Change code in kubernetes to use ``foo/bar``. - Run ``godep save ./...`` under kubernetes' root directory. To update a package ``foo/bar``: - Make sure the kubernetes' root directory is in $GOPATH/github.com/GoogleCloudPlatform/kubernetes - Run ``godep restore`` to make sure you have all dependancies pulled. - Update the package with ``go get -u foo/bar``. - Change code in kubernetes accordingly if necessary. - Run ``godep update foo/bar`` under kubernetes' root directory. ## Keeping your development fork in sync One time after cloning your forked repo: ``` git remote add upstream https://github.com/GoogleCloudPlatform/kubernetes.git ``` Then each time you want to sync to upstream: ``` git fetch upstream git rebase upstream/master ``` ## Regenerating the API documentation ``` cd kubernetes/api sudo docker build -t kubernetes/raml2html . sudo docker run --name=\"docgen\" kubernetes/raml2html sudo docker cp docgen:/data/kubernetes.html . ``` View the API documentation using htmlpreview (works on your fork, too): ``` http://htmlpreview.github.io/?https://github.com/GoogleCloudPlatform/kubernetes/blob/master/api/kubernetes.html ``` </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-7c5448078f172c3dba4d1f6f6ed5d66f21d2fc0ea9dd38dbb1ed9b4cc49eea15", "text": "Right now, we have a mixture of user documentation and developer documentation in the top-level directory. We should make it easier to find a just user documentation. Step 1 would be to move developer documentation into a subdir like docs/development or something like that. User docs would stay in the top-level docs dir.\nmove to", "commid": "kubernetes_issue_1797", "tokennum": 71}], "negative_passages": []}
{"query_id": "q-en-kubernetes-36d1af981a2f7a57e56c0f0505737bcf02eee1720f902b1faa15386fba0c2527", "query": "if err != nil { return false, fmt.Errorf(\"got error while getting pod events: %s\", err) } <del> if len(events.Items) == 0 { return false, nil // no events have occurred yet </del> <ins> for _, event := range events.Items { if strings.Contains(event.Message, msg) { return true, nil } </ins> } <del> return strings.Contains(events.Items[0].Message, msg), nil </del> <ins> return false, nil </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-5b9acc75297a25b96aff671a444795dd08937bfc26a86f521e5dacf125ddfa55", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: gce-new-master-upgrade-cluster-new-parallel Which test(s) are failing: Varies, but all subpath failures, including: [sig-storage] CSI Volumes [Driver: csi-hostpath-v0] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath with backstepping is outside the volume [Slow] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath directory is outside the volume [Slow] [sig-storage] CSI Volumes [Driver: csi-hostpath-v0] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath file is outside the volume [Slow] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath file is outside the volume [Slow] ... and pretty much every other subpath test, but never all of them at once. There's also a few other storage tests failing, such as: [sig-storage] Volume expand [Slow] Verify if editing PVC allows resize [sig-storage] Detaching volumes should not work when mount is in progress Since when has it been failing: 11/22 Testgrid link: https://k8s- Reason for failure: These flakes started around the time that merged, but doesn't match up with the exact merge stamp, so it's probably coincidental. The subpath test failures seem to be mostly timeouts: ... so possibly this is just GCE fail. Anything else we need to know: This test job has always been flaky, with around a 40% failure rate. <!-- DO NOT EDIT BELOW THIS LINE --/kind flake /sig storage /priority important-soon cc\ncan you please help investigate this. It looks to me like the tests are flaking for and . I wonder if the v0 tests are racing with the non-v0 tests for something in this test?\nThe other tests including for the other CSI driver and non-CSI in-tree plugins are solid green which also makes me think this is a issue with the hostpath tests or driver.", "commid": "kubernetes_issue_71383", "tokennum": 534}], "negative_passages": []}
{"query_id": "q-en-kubernetes-36d1af981a2f7a57e56c0f0505737bcf02eee1720f902b1faa15386fba0c2527", "query": "if err != nil { return false, fmt.Errorf(\"got error while getting pod events: %s\", err) } <del> if len(events.Items) == 0 { return false, nil // no events have occurred yet </del> <ins> for _, event := range events.Items { if strings.Contains(event.Message, msg) { return true, nil } </ins> } <del> return strings.Contains(events.Items[0].Message, msg), nil </del> <ins> return false, nil </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-b96111816628bb5b6b036ae1cc6a1fd4cca373f6f47aaa901c194d255325d8fd", "text": "(just adding additional similar flakes here for tracking) Similar flakes in :\nadding to the milestone for triage since the flakes look new\nThese all 4 subpath tests call and it fails in finding a specific failed event by using . As uses to check if the specific error event happens, and , I guess that tests may flake if other failed event happens before the expected one. Also, already wait for the event, we might be able to delete  in . I will create a PR to fix above.\n/priority critical-urgent /remove-priority important-soon /milestone v1.13\nwhile we should update the test with your PR, I'm not sure if it's going to fix the failure. Looking at one failing test log, these are the events I see on the failing pod: So it seems to be failing before even reaching the subpath logic.\nTimeline of events: Test pod started getting processed by kubelet: It took a minute after the test pod was created for the csi driver to finish registering and mount to succeed, and then subpath event to trigger: So should address the issue. I was initially confused because the test logs didn't show the subpath event for some reason\nI opened up to investigate if 1 minute for csi plugin registration is expected\nI've a tracker issue for the complete list of storage flakes: This is so that we can track whether we're addressing most of the flakes with the subpath fixes, or if additional fixes are required.\nkeeping open until flakes are verified cleaned up\n/reopen Reopening this issue until we can verify the fix in CI\nAs of this morning we are seeing CSI \"subpath should fail\" flakes in the following job Multiple \"subpath should fail\" flakes in this slow job alone Multiple \"subpath should fail\" flakes in the 1.13 slow job, similar to master. The following 2 tests are flaky only in this upgrade job can you help us determine if these are cases are flaky tests that you are fixing or is there an underlying CSI bug that needs addressing?\nroot cause of this is a delay in an external sidecar containers and the tests not waiting long enough to accommodate the delay. There are no changes required in (outside of test) to handle this. These should not be 1.13 blocking. We'll continue to look in to getting them non-flaky today.", "commid": "kubernetes_issue_71383", "tokennum": 498}], "negative_passages": []}
{"query_id": "q-en-kubernetes-36d1af981a2f7a57e56c0f0505737bcf02eee1720f902b1faa15386fba0c2527", "query": "if err != nil { return false, fmt.Errorf(\"got error while getting pod events: %s\", err) } <del> if len(events.Items) == 0 { return false, nil // no events have occurred yet </del> <ins> for _, event := range events.Items { if strings.Contains(event.Message, msg) { return true, nil } </ins> } <del> return strings.Contains(events.Items[0].Message, msg), nil </del> <ins> return false, nil </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-bf7ca95c6d3fe47cf47149272c15b0cd4379bd169d397f0222144854aadb75e6", "text": "In the meantime, we can mark these tests as flaky to reduce the noise, if you'd like. looks like the same issue () is still being hit. See : And logs from (): We need to make the tests handle this condition more gracefully. The suggestion here is one possible solution.\nWould be good to capture this as a known issue in release notes.\nto followup on capturing this in Release notes\nper , can you create a targeted fix increasing the timeout? Looks like marking these tests as flaky will be difficult for 1.13, but if that doesn't fix it we will need to do that.\nShort term fix to bump the test timeout:\nAs per discussion in release burndown meeting, this is not a 1.13 blocker. please move this issue to 1.14 if there are no pending issues you are concerned about\nOk looks like the test still flaked. Looking at , the mount succeeded after a minute and proceeded to subpath processing, which (correctly) failed. However, for some resaon, the test is not seeing the subpath event and still failed after 4 minutes. On kubelet, subpath processing failed after a minute and generated the event: But the test doesn't see it for some reason, and still times out after 4 more minutes:\nI saw the same on CSI volume mount succeeded at: Kubelet correctly failed the pod because of subpath But test still failed: Because the test failed to find the pod event. This looks like a test issue. Not a 1.13 blocker.\ncan you PTAL at this\nIs there a way to check if events are overloaded and not able to handle new events? The MountVolume retries while the driver is not registered is very frequent and could have overloaded the event server.\nChecking for the existence of an event seems like the wrong way to test this. Would checking pod status alone be insufficient? Ultimately that is what we really care about.\nChecking for the specific event guarantees that we are failing with the correct error. But perhaps events are not reliable enough to depend on. Checking if the Pod never came up running would probably reduce the flakes but could potentially mask false negatives. cc for any thoughts.", "commid": "kubernetes_issue_71383", "tokennum": 461}], "negative_passages": []}
{"query_id": "q-en-kubernetes-36d1af981a2f7a57e56c0f0505737bcf02eee1720f902b1faa15386fba0c2527", "query": "if err != nil { return false, fmt.Errorf(\"got error while getting pod events: %s\", err) } <del> if len(events.Items) == 0 { return false, nil // no events have occurred yet </del> <ins> for _, event := range events.Items { if strings.Contains(event.Message, msg) { return true, nil } </ins> } <del> return strings.Contains(events.Items[0].Message, msg), nil </del> <ins> return false, nil </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-134801dda9ebcf7b8cdf97d148e6b55c98d4c0b9989e7755b1ae0bf2d394c600", "text": "Tests are still flaking and actually it seems like in general storage flakes in slow are flaking more since 11-21 or so: https://k8s- My theory is that the driver registration delay is causing a flood of events, which causes tests that check for events to fail. I think this is revealing multiple issues in both the tests and product, and we should work on fixing them all, although any one of the fixes should mitigate the test flakes: Driver registrar can sometimes take a minute to come up: Volume manager operation executor doesn't seem to be throttling retries or backing off: Tests should not rely on events: Tests should wait for CSI driver to be registered on all nodes before creating test pods:\nand have been merged and will address the biggest issues. has been backported to 1.13 already, backport is still pending.\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nClosing 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", "commid": "kubernetes_issue_71383", "tokennum": 441}], "negative_passages": []}
{"query_id": "q-en-kubernetes-36e3f623834c614bf70acd6ed2b621083616835c0e9704cb88976cb15e57606b", "query": "import ( \"bytes\" <ins> \"errors\" </ins> \"fmt\" \"math/rand\" \"net\"", "positive_passages": [{"docid": "doc-en-kubernetes-12565e8dbeb532aef2fc81c48820204edabd27cddb58e2c25eb51a8447b79e73", "text": "introduced somethng that really should be e2e tested.\nWould be nice to get this in in the 2 weeks we have after 1.2 branch cut, if no more flakes crop up (but I'm not too optimistic). Bumping to next-release.\n/sig network I'm assuming sig-network owns kube-proxy\nI thought I noted a change related to this recently, but I may be mistaken.\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\n/lifecycle frozen /remove-lifecycle stale\n/remove-lifecycle rotten\nGoing to try to take this on.\nthanks!\nI've had some trouble constructing a test for this. should I determine the timeout? There doesn't appear to be an existing mechanism for waiting for service creation. seem to time out rather than be refused - I'm confused by this, as it seems to be the opposite of the intended behavior.\ncan look at the endpoints + wait for longer than kube-proxy sync time. refused means packets got to their destination but there was nothing listening there. If traffic is blocked, then you will just get a timeout.\nI created a service with no matching pods to test manually outside of the e2e suite. # curl test-api curl: (7) Failed to connect to athena-api port 80: Connection timed out # curl --connect-timeout 8 test-api curl: (28) Connection timed out after 8000 milliseconds Looking back at original example in I see that I'm getting the \"before\" behaviour. An iptables REJECT should send a denial, not a timeout. Am I looking at the wrong thing here? To me this looks like a regression, but I don't think that's likely.", "commid": "kubernetes_issue_20767", "tokennum": 514}], "negative_passages": []}
{"query_id": "q-en-kubernetes-36e3f623834c614bf70acd6ed2b621083616835c0e9704cb88976cb15e57606b", "query": "import ( \"bytes\" <ins> \"errors\" </ins> \"fmt\" \"math/rand\" \"net\"", "positive_passages": [{"docid": "doc-en-kubernetes-075a02cd819ce7b09a20727c244a2aff5570644c9d21afadee17b14b07c37e5c", "text": "I have a cluster from HEAD as of 2 weeks ago: So indeed it seems to not work. If I hit that same service IP from the VM itself I immediately get curl: (7) Failed to connect to 10.0.199.54 port 80: Connection refused. If I insert an iptables jump to KUBE-SERVICES at the front of FORWARD, it correctly rejects. This seems in accordance with the iptables flowchart. I'll do some spelunking to see if there's a reason NOT to reject in this case. Vallery Lancey <:\nCan you check IPVS mode?\nThis is why we need tests. Sigh.\nProposed fix is - still needs your e2e :)\nThanks Tim, if I have time I\u2019ll get a PR up tonight.\nSure will check IPVS mode.\nBase on my test, IPVS has no such issue.", "commid": "kubernetes_issue_20767", "tokennum": 186}], "negative_passages": []}
{"query_id": "q-en-kubernetes-36f70a1d19735cbd6842492ce413e1207ccb4738a607e1b0a168f1b3bd2a0b04", "query": "<ins> //go:build !providerless // +build !providerless /* Copyright 2023 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package vsphere import ( \"testing\" v1 \"k8s.io/api/core/v1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/runtime\" \"k8s.io/client-go/informers\" \"k8s.io/client-go/kubernetes/fake\" \"k8s.io/legacy-cloud-providers/vsphere/vclib\" ) // Annotation used to distinguish nodes in node cache / informer / API server const nodeAnnotation = \"test\" func getNode(annotation string) *v1.Node { return &v1.Node{ ObjectMeta: metav1.ObjectMeta{ Name: \"node1\", Annotations: map[string]string{ nodeAnnotation: annotation, }, }, } } func TestGetNode(t *testing.T) { tests := []struct { name           string cachedNodes    []*v1.Node informerNodes  []*v1.Node // \"nil\" means that the NodeManager has no nodeLister apiServerNodes []*v1.Node // \"nil\" means that the NodeManager has no nodeGetter expectedNodeAnnotation string expectNotFound         bool }{ { name:           \"No cached node anywhere\", cachedNodes:    []*v1.Node{}, informerNodes:  []*v1.Node{}, apiServerNodes: []*v1.Node{}, expectNotFound: true, }, { name:           \"No lister & getter\", cachedNodes:    []*v1.Node{}, informerNodes:  nil, apiServerNodes: nil, expectNotFound: true, }, { name:                   \"cache is used first\", cachedNodes:            []*v1.Node{getNode(\"cache\")}, informerNodes:          []*v1.Node{getNode(\"informer\")}, apiServerNodes:         []*v1.Node{getNode(\"apiserver\")}, expectedNodeAnnotation: \"cache\", }, { name:                   \"informer is used second\", cachedNodes:            []*v1.Node{}, informerNodes:          []*v1.Node{getNode(\"informer\")}, apiServerNodes:         []*v1.Node{getNode(\"apiserver\")}, expectedNodeAnnotation: \"informer\", }, { name:                   \"API server is used last\", cachedNodes:            []*v1.Node{}, informerNodes:          []*v1.Node{}, apiServerNodes:         []*v1.Node{getNode(\"apiserver\")}, expectedNodeAnnotation: \"apiserver\", }, } for _, test := range tests { t.Run(test.name, func(t *testing.T) { // local NodeManager cache cache := make(map[string]*v1.Node) for _, node := range test.cachedNodes { cache[node.Name] = node } // Client with apiServerNodes objs := []runtime.Object{} for _, node := range test.apiServerNodes { objs = append(objs, node) } client := fake.NewSimpleClientset(objs...) nodeGetter := client.CoreV1() // Informer + nodeLister. Despite the client already has apiServerNodes, they won't appear in the // nodeLister, because the informer is never started. factory := informers.NewSharedInformerFactory(client, 0 /* no resync */) nodeInformer := factory.Core().V1().Nodes() for _, node := range test.informerNodes { nodeInformer.Informer().GetStore().Add(node) } nodeLister := nodeInformer.Lister() nodeManager := NodeManager{ registeredNodes: cache, } if test.informerNodes != nil { nodeManager.SetNodeLister(nodeLister) } if test.apiServerNodes != nil { nodeManager.SetNodeGetter(nodeGetter) } node, err := nodeManager.GetNode(\"node1\") if test.expectNotFound && err != vclib.ErrNoVMFound { t.Errorf(\"Expected NotFound error, got: %v\", err) } if !test.expectNotFound && err != nil { t.Errorf(\"Unexpected error: %s\", err) } if test.expectedNodeAnnotation != \"\" { if node.Annotations == nil { t.Errorf(\"Expected node with annotation %q, got nil\", test.expectedNodeAnnotation) } else { if ann := node.Annotations[nodeAnnotation]; ann != test.expectedNodeAnnotation { t.Errorf(\"Expected node with annotation %q, got %q\", test.expectedNodeAnnotation, ann) } } } }) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-b9a7a79272b4f05e986ec052f9f8348c60cffedf2d99a44ddafb98b4101b558f", "text": "I am enabling CSI migration on a vSphere cluster. A node was fully drained, all its Pods are deleted, but just before KCM detaches in-tree vSphere volume volumes from it, KCM restarts. A new KCM starts, sees attached volumes in that are not needed by any Pod on the node and calls vSphere in-tree volume plugin . The in-tree vSphere volume plugin + cloud provider marks the volume as detached right away, without reaching to vCenter API. The volume remains attached forever. I don't think it's related to CSI migration, IMO a regular node drain + KCM restart at the same time can cause the same issue. KCM logs: The in-tree cloud provider has a and from it. It apparently has not processed all nodes at the time A/D controller tries to detach the node. The in-tree vSphere volume plugin + cloud provider detaches the volume in vCenter. That's really tricky, it's very hard / impossible to reproduce on a real cluster. I had to inject errors to Detach() in-tree volume call, so they fail until KCM is restarted. Newly started KCM would detach the volume just fine (no error would be injected there), but marks the volume as detached right away. For the record (and search-ability), the CSI driver that tries to attach the volume to another node complains either: Or: cc It could be somewhat related to , however, not all cases of can be related to KCM restart. As I mentioned above, it's very hard/impossible to synchronize KCM restart with draining a node in a real cluster. <details</details<detailsvSphere 7.0.3 </details<details</details<detailsOpenShift </details<detailsCRI-O </details<details</details\n/sig storage\nTried just moving a Pod between nodes without CSI migration involved + restarting KCM when the volume is still attached to the old node. In-tree volume plugin on the new node says:\n/assign\nWhat CSI driver version and K8s version are you testing with?\nKubernetes is 1.25 and CSI driver is 2.7, still, I think it's not releated to the CSI driver, it's KCM who marks the in-tree volume as detached due to not populated node cache.", "commid": "kubernetes_issue_117091", "tokennum": 517}], "negative_passages": []}
{"query_id": "q-en-kubernetes-36f70a1d19735cbd6842492ce413e1207ccb4738a607e1b0a168f1b3bd2a0b04", "query": "<ins> //go:build !providerless // +build !providerless /* Copyright 2023 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package vsphere import ( \"testing\" v1 \"k8s.io/api/core/v1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/runtime\" \"k8s.io/client-go/informers\" \"k8s.io/client-go/kubernetes/fake\" \"k8s.io/legacy-cloud-providers/vsphere/vclib\" ) // Annotation used to distinguish nodes in node cache / informer / API server const nodeAnnotation = \"test\" func getNode(annotation string) *v1.Node { return &v1.Node{ ObjectMeta: metav1.ObjectMeta{ Name: \"node1\", Annotations: map[string]string{ nodeAnnotation: annotation, }, }, } } func TestGetNode(t *testing.T) { tests := []struct { name           string cachedNodes    []*v1.Node informerNodes  []*v1.Node // \"nil\" means that the NodeManager has no nodeLister apiServerNodes []*v1.Node // \"nil\" means that the NodeManager has no nodeGetter expectedNodeAnnotation string expectNotFound         bool }{ { name:           \"No cached node anywhere\", cachedNodes:    []*v1.Node{}, informerNodes:  []*v1.Node{}, apiServerNodes: []*v1.Node{}, expectNotFound: true, }, { name:           \"No lister & getter\", cachedNodes:    []*v1.Node{}, informerNodes:  nil, apiServerNodes: nil, expectNotFound: true, }, { name:                   \"cache is used first\", cachedNodes:            []*v1.Node{getNode(\"cache\")}, informerNodes:          []*v1.Node{getNode(\"informer\")}, apiServerNodes:         []*v1.Node{getNode(\"apiserver\")}, expectedNodeAnnotation: \"cache\", }, { name:                   \"informer is used second\", cachedNodes:            []*v1.Node{}, informerNodes:          []*v1.Node{getNode(\"informer\")}, apiServerNodes:         []*v1.Node{getNode(\"apiserver\")}, expectedNodeAnnotation: \"informer\", }, { name:                   \"API server is used last\", cachedNodes:            []*v1.Node{}, informerNodes:          []*v1.Node{}, apiServerNodes:         []*v1.Node{getNode(\"apiserver\")}, expectedNodeAnnotation: \"apiserver\", }, } for _, test := range tests { t.Run(test.name, func(t *testing.T) { // local NodeManager cache cache := make(map[string]*v1.Node) for _, node := range test.cachedNodes { cache[node.Name] = node } // Client with apiServerNodes objs := []runtime.Object{} for _, node := range test.apiServerNodes { objs = append(objs, node) } client := fake.NewSimpleClientset(objs...) nodeGetter := client.CoreV1() // Informer + nodeLister. Despite the client already has apiServerNodes, they won't appear in the // nodeLister, because the informer is never started. factory := informers.NewSharedInformerFactory(client, 0 /* no resync */) nodeInformer := factory.Core().V1().Nodes() for _, node := range test.informerNodes { nodeInformer.Informer().GetStore().Add(node) } nodeLister := nodeInformer.Lister() nodeManager := NodeManager{ registeredNodes: cache, } if test.informerNodes != nil { nodeManager.SetNodeLister(nodeLister) } if test.apiServerNodes != nil { nodeManager.SetNodeGetter(nodeGetter) } node, err := nodeManager.GetNode(\"node1\") if test.expectNotFound && err != vclib.ErrNoVMFound { t.Errorf(\"Expected NotFound error, got: %v\", err) } if !test.expectNotFound && err != nil { t.Errorf(\"Unexpected error: %s\", err) } if test.expectedNodeAnnotation != \"\" { if node.Annotations == nil { t.Errorf(\"Expected node with annotation %q, got nil\", test.expectedNodeAnnotation) } else { if ann := node.Annotations[nodeAnnotation]; ann != test.expectedNodeAnnotation { t.Errorf(\"Expected node with annotation %q, got %q\", test.expectedNodeAnnotation, ann) } } } }) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-27c84c169fad17ff032040ca08c7bb73c7215213dd29c5491da1ee415abb2a33", "text": "/assign\n/triage accepted\nI found an easier way how to reproduce this without extra code in KCM: a StatefulSet with 1 Pod that uses 1 PVC. the node where the Pod runs. down kube-controller-manager to zero (not really possible for me) or kill all kube-controller-manager Pods. This will cause new KCM processes to wait for leader election. In my env. this gives me ~30 seconds for the next step. Delete the Pod. A new one will be scheduled on a different node (because the current node is cordoned) + there is no KCM running at this time that would detach the volume from the old node. KCM wins its leader election, sees a volume attached to a node where it is not needed -it calls of the volume plugin. VSphere cloud provider does not have its caches populated yet (= this bug) -the volume is not detached, but returns success.\ndangling attach does not help here. The volume is still attached to the old node even after ~10 minutes. fails with and not with . I can see there is a lot of dangling attach code in the cloud provider, but I did not debug further.", "commid": "kubernetes_issue_117091", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-37080411293afd2ecb7943a7e88bfbc257be6cb9ad882a89e1b9bb9965229329", "query": "nodeName k8stypes.NodeName, isAttached bool, asw cache.ActualStateOfWorld, <ins> timeout time.Duration, </ins> ) { <del> result := false volumes := asw.GetVolumesToReportAttached(logger) for _, volume := range volumes[nodeName] { if volume.Name == volumeName { result = true </del> <ins> var result bool var lastErr error err := wait.PollUntilContextTimeout(context.TODO(), 50*time.Millisecond, timeout, false, func(context.Context) (done bool, err error) { volumes := asw.GetVolumesToReportAttached(logger) for _, volume := range volumes[nodeName] { if volume.Name == volumeName { result = true } </ins> } <del> } if result == isAttached { t.Logf(\"Volume <%v> is reported as attached to node <%v>: %v\", volumeName, nodeName, result) return </del> <ins> if result == isAttached { t.Logf(\"Volume <%v> is reported as attached to node <%v>: %v\", volumeName, nodeName, result) return true, nil } lastErr = fmt.Errorf(\"Check volume <%v> is reported as attached to node <%v>, got %v, expected %v\", volumeName, nodeName, result, isAttached) return false, nil }) if err != nil { t.Fatalf(\"last error: %q, wait timeout: %q\", lastErr, err.Error()) </ins> } <del> t.Fatalf(\"Check volume <%v> is reported as attached to node <%v>, got %v, expected %v\", volumeName, nodeName, result, isAttached) </del> }", "positive_passages": [{"docid": "doc-en-kubernetes-dc8aac09a0e4bb26f9dc5f50aef7f845ea9d7c4b925d34b9f6eda044925f80f5", "text": "TestRunOneVolumeDetachFailNodeWithReadWriteOnce 4 times since 03-19 23:00 PDT, intermittently ! https://k8s- Still investigating whether this is a tolerable flake or not with more history than testgrid view, or otherwise would appreciate input from anyone with expertise in this test, especially as regards to whether this should be a blocker for tomorrows beta cut. maybe: /sig storage /sig testing\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nis already open for this, looks like it is attempting to fix it\nthank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. /close\nClosing this issue. <detailsIn response to : thank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. 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", "commid": "kubernetes_issue_116774", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-37080411293afd2ecb7943a7e88bfbc257be6cb9ad882a89e1b9bb9965229329", "query": "nodeName k8stypes.NodeName, isAttached bool, asw cache.ActualStateOfWorld, <ins> timeout time.Duration, </ins> ) { <del> result := false volumes := asw.GetVolumesToReportAttached(logger) for _, volume := range volumes[nodeName] { if volume.Name == volumeName { result = true </del> <ins> var result bool var lastErr error err := wait.PollUntilContextTimeout(context.TODO(), 50*time.Millisecond, timeout, false, func(context.Context) (done bool, err error) { volumes := asw.GetVolumesToReportAttached(logger) for _, volume := range volumes[nodeName] { if volume.Name == volumeName { result = true } </ins> } <del> } if result == isAttached { t.Logf(\"Volume <%v> is reported as attached to node <%v>: %v\", volumeName, nodeName, result) return </del> <ins> if result == isAttached { t.Logf(\"Volume <%v> is reported as attached to node <%v>: %v\", volumeName, nodeName, result) return true, nil } lastErr = fmt.Errorf(\"Check volume <%v> is reported as attached to node <%v>, got %v, expected %v\", volumeName, nodeName, result, isAttached) return false, nil }) if err != nil { t.Fatalf(\"last error: %q, wait timeout: %q\", lastErr, err.Error()) </ins> } <del> t.Fatalf(\"Check volume <%v> is reported as attached to node <%v>, got %v, expected %v\", volumeName, nodeName, result, isAttached) </del> }", "positive_passages": [{"docid": "doc-en-kubernetes-aef7ec00dc93616f97177ca3d23f28217445848b34c429e5746962ea28329f43", "text": "pull-kubernetes-unit TestRunOneVolumeDetachFailNodeWithReadWriteOnce Jan 7th, 2022 Check volume <fake-plugin/volume-nameis reported as attached to node <fail-detach-node, got false, expected true No response_ /sig storage\n/cc\nthis is the top unit test flake according to\ncc\nThe 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]:\nI think this test is no longer flaky by checking the test grid, close it now.\nUnfortunately this does still seem to be flaky: Here was the output from : /reopen\nReopened this issue. <detailsIn response to : Unfortunately this does still seem to be flaky: 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\n/remove-lifecycle stale\nstill the case\nHow about adding some logging to help troubleshoot this? I looked at it a little, but it is hard to tell which part of the test is failing. PR\n/\nThis is still happening\n/triage accepted\nFrom the logs, in the OneVolumeDetachFailNodeWithReadWriteOnce test, succeeded, but the next verification failed. In verifyVolumeAttachedToNode, the attachState is from calling and within asw, it calls . In verifyVolumeReportedAsAttachedToNode, the volumes are obtained from calling , it seems that the node is not in asw.nodesToUpdateStatusFor at this step. Cannot reproduce locally. I tried to run the test 100 times locally with debug.Stack()... 3 * 100 times all passed.\nTried to run stress test on my linux machine as well but still cannot reproduce. Command: Result: Also tried running n process in parallel. Command: Result:\nIt seems like it happens more frequently.", "commid": "kubernetes_issue_107414", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-37080411293afd2ecb7943a7e88bfbc257be6cb9ad882a89e1b9bb9965229329", "query": "nodeName k8stypes.NodeName, isAttached bool, asw cache.ActualStateOfWorld, <ins> timeout time.Duration, </ins> ) { <del> result := false volumes := asw.GetVolumesToReportAttached(logger) for _, volume := range volumes[nodeName] { if volume.Name == volumeName { result = true </del> <ins> var result bool var lastErr error err := wait.PollUntilContextTimeout(context.TODO(), 50*time.Millisecond, timeout, false, func(context.Context) (done bool, err error) { volumes := asw.GetVolumesToReportAttached(logger) for _, volume := range volumes[nodeName] { if volume.Name == volumeName { result = true } </ins> } <del> } if result == isAttached { t.Logf(\"Volume <%v> is reported as attached to node <%v>: %v\", volumeName, nodeName, result) return </del> <ins> if result == isAttached { t.Logf(\"Volume <%v> is reported as attached to node <%v>: %v\", volumeName, nodeName, result) return true, nil } lastErr = fmt.Errorf(\"Check volume <%v> is reported as attached to node <%v>, got %v, expected %v\", volumeName, nodeName, result, isAttached) return false, nil }) if err != nil { t.Fatalf(\"last error: %q, wait timeout: %q\", lastErr, err.Error()) </ins> } <del> t.Fatalf(\"Check volume <%v> is reported as attached to node <%v>, got %v, expected %v\", volumeName, nodeName, result, isAttached) </del> }", "positive_passages": [{"docid": "doc-en-kubernetes-62e47fd83b7fc1cc39259be1688a9f133b9cd2dc48247eb5d858fae7fd13955b", "text": "But I may have no time to dig into the cause. Let's see.\ncc as the test author.\nThe problem is that this test has a lot of dependency on the sleeps that are hardcoded with a very narrow scope, but our CI seems to be able to stress it much more. As soon as you slightly change one of the sleep duration it starts to flake locally The test can not make an assumption that timing is perfect, even more in the sub second range can someone in sig-storage review this test and make it less dependant on those tight sleeps?\nAccording to most failures, it failed at Line 660. Let me run some stress locally. with 250ms sleep with 100ms sleep\nI agree this test case is too brittle due to its specific timing dependencies. To fix this, I suggest reworking the test case to: 1) Add retry with timeout to wait for final conditions 2) Remove the intermediate timing-based state transition checks. Instead, we can keep track of state transitions in the Fakes and validate those stats. wdyt?\nFriendly ping from 1.27 CI Signal that this test is still a noisy flake on the master-blocking dashboard as CI Signal has flagged it in and", "commid": "kubernetes_issue_107414", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3778c52dfb226afcaf17e6e0e1043e4b832633686daf9d1a355b0fa51e02215f", "query": "\"github.com/google/go-cmp/cmp\" \"k8s.io/apimachinery/pkg/util/json\" \"k8s.io/apimachinery/pkg/util/sets\" <ins> \"k8s.io/apimachinery/pkg/util/wait\" </ins> \"k8s.io/apimachinery/pkg/util/waitgroup\" auditinternal \"k8s.io/apiserver/pkg/apis/audit\" \"k8s.io/apiserver/pkg/audit\"", "positive_passages": [{"docid": "doc-en-kubernetes-00113afbb73b199bafe3ba83166412a7273f0dfa544fc7d4bd6466795076d1a7", "text": "<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI --Which jobs are flaking: bazel-test-master Which test(s) are flaking: gotest: Testgrid link: Reason for failure: Anything else we need to know: links to appreciated [Will update shortly] links to specific failures in spyglass appreciated <!-- Please see the deflaking doc () for more guidance! --/sig api-machinery\nThe label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : Which jobs are flaking: bazel-test-master Which test(s) are flaking: gotest: Testgrid link: Reason for failure: links to appreciatedlinks to specific failures in spyglass appreciated /sig api-machinary 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\n/sig api-machinery\n/assign /triage accepted\nFlaked twice ~2 weeks ago but now looking good: Since it's been relatively quiet, I'm going to go ahead and close this for now. /close\nClosing this issue. <detailsIn response to : Flaked twice ~2 weeks ago but now looking good: 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\n/reopen /assign I meet this test failure in And I can reproduce it with local stress testing. The reason is the same with\nReopened this issue. <detailsIn response to : /reopen /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", "commid": "kubernetes_issue_97312", "tokennum": 408}], "negative_passages": []}
{"query_id": "q-en-kubernetes-37c8ced5e63a4f696c6de8db5894c4c6f0c9cfcb540702a4305714dc4c1c4e1e", "query": "// ExcludeMasterFromStandardLB excludes master nodes from standard load balancer. // If not set, it will be default to true. ExcludeMasterFromStandardLB *bool `json:\"excludeMasterFromStandardLB\" yaml:\"excludeMasterFromStandardLB\"` <ins> // DisableOutboundSNAT disables the outbound SNAT for public load balancer rules. // It should only be set when loadBalancerSku is standard. If not set, it will be default to false. DisableOutboundSNAT *bool `json:\"disableOutboundSNAT\" yaml:\"disableOutboundSNAT\"` </ins> // Maximum allowed LoadBalancer Rule Count is the limit enforced by Azure Load balancer MaximumLoadBalancerRuleCount int `json:\"maximumLoadBalancerRuleCount\" yaml:\"maximumLoadBalancerRuleCount\"`", "positive_passages": [{"docid": "doc-en-kubernetes-f91ac3317a925ac3a02c50dc39021d458d6020da9f69361ec2732a68459b1b7c", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: is the recommended way to configure the outbound networks together with Azure standard loadbalancer (SLB). However, for load balancer rules are disabled by default. That means all frontend IPs would be used as the SNAT IPs for virtual machines, according to . This would introduce troubles for various security scenarios, as there's no way to get a stable list of egress IPs. Azure cloud provider should support this scenario, and disable the outbound SNAT when outbound rules are configured by provisioning tools. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Others: /kind bug /sig azure /priority critical-urgent", "commid": "kubernetes_issue_75281", "tokennum": 247}], "negative_passages": []}
{"query_id": "q-en-kubernetes-37cff65b112c33747f181640fcbeb47118d31e40bd87e396471f308759f26925", "query": "# Clean up kubectl delete jobs pi \"${kube_flags[@]}\" # Post-condition: no pods exist. <del> kube::test::get_object_assert pods \"{{range.items}}{{$id_field}}:{{end}}\" '' </del> <ins> kube::test::wait_object_assert pods \"{{range.items}}{{$id_field}}:{{end}}\" '' </ins> # Pre-Condition: no Deployment exists kube::test::get_object_assert deployment \"{{range.items}}{{$id_field}}:{{end}}\" ''", "positive_passages": [{"docid": "doc-en-kubernetes-aa932f22e6eeb52ad965f613ba00464d5c8654efa2d7218c3ea52d951e8f2500", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: pull-kubernetes-integration Which test(s) are failing: test-cmd runkubectlrun_tests Since when has it been failing: According to triage, the first failure was 2019-02-21 12:00 UTC Testgrid link: Reason for failure: Unknown Anything else we need to know: This may be a flake? I can't tell yet. The testgrid link is not a continuous failure, but it could be that not enough PR's have whatever change is causing the failure Triage link: It looks like it may be happening in CI as well\n/sig cli /priority critical-urgent /milestone v1.14\n/remove-kind failing-test /kind flake I can't see it consistently happening in CI, so it must be a flake?\nWhat I got when running locally...\nAnd I see the same thing in the build- for\nTrying to track down the first occurrence. I think there was an XML parsing error that was obscuring this that was fixed recently. Backtracking through pull-kubernetes-integration failures and visually inspecting them. - runkubectlruntests - 2019-02-22 15:45 PST - runkubectlruntests - 2019-02-21 01:13 PST - runkubectlrun_tests - 2019-02-20 16:50 PST ... and then I don't see this particular test failing during 02-19 or 02-18\nSo going by that, let's cast a net in commits that landed just prior to the earliest PR failure, and N hours prior\nSuspects - ~only because it touches nope, rolled back to right after this landed, no repro after 30 attempts - ~enables server side apply <-- this is my guess~ nope, rolled back to right after this landed, no repro after 30 attempts - reduce lock contention in watchcache\nthe test might be racy in the first place, maybe enabling the feature changes the time profile of the test.\nWelp, now that I have what I think is a local repro loop for this, and I'm bisecting, it's looking like the whole commit range I suspected is fine Looking closer, this particular test case is overly optimistic, it deletes a job and immediately gets pods expecting there to be none.", "commid": "kubernetes_issue_74431", "tokennum": 529}], "negative_passages": []}
{"query_id": "q-en-kubernetes-37cff65b112c33747f181640fcbeb47118d31e40bd87e396471f308759f26925", "query": "# Clean up kubectl delete jobs pi \"${kube_flags[@]}\" # Post-condition: no pods exist. <del> kube::test::get_object_assert pods \"{{range.items}}{{$id_field}}:{{end}}\" '' </del> <ins> kube::test::wait_object_assert pods \"{{range.items}}{{$id_field}}:{{end}}\" '' </ins> # Pre-Condition: no Deployment exists kube::test::get_object_assert deployment \"{{range.items}}{{$id_field}}:{{end}}\" ''", "positive_passages": [{"docid": "doc-en-kubernetes-c5cfc8410c7669697d22e2ec552cdc8ebab9bc4a4cb7d08b2ecda8ea1d48026b", "text": "I'd still like to nail down what timing change surface this before I go change the to a or using a different set of flags for the call\nWell, for some reason seems to be when the flakes started showing up\nI realize that the flake is hard to reproduce especially since it's hard to run specific tests in . You can comment a lot of the tests by playing with some of these shell scripts so that they mostly just run the test you want to run. if you do so, you might be able to run 10 or 20 times the test in a row at this PR and right before. I'm curious what the difference would be in term of flake rate.\nYeah that's what I've been doing. It's and specifically looks to be . Which has nothing directly to do with pods, so I guess it's just a matter of this slowing the apiserver down just enough to start tripping a poorly written test.\nFYI for the above. My plan for now is just to rewrite the test so it's more forgiving. But I wanted to confirm that it's expected / known that apiserver performance changed a bit as a result of this.\n/assign /assign\nWhat metric are you seeing suffer with that commit? There should be no impact.\nA racy test goes from flaking 0% of the time to flaking 10-20% of the time Jordan Liggitt <:\nflakes: It should probably use instead. The thing is, I can't get it to flake before. I hacked up test/cmd/legacy- to run just this, and none of the other test cases\nIt definitely should. I'll take a look at job-pod deletion propagation time before/after that commit, but there's nothing I can think of in that path a new networking API group would impact.", "commid": "kubernetes_issue_74431", "tokennum": 387}], "negative_passages": []}
{"query_id": "q-en-kubernetes-37dbeeb878bb011279b83d09f79af712fb3a9c48a142226d4c0440c3da688c97", "query": "for _, testcase := range testcases { t.Run(testcase.name, func(t *testing.T) { <del> buf := new(bytes.Buffer) errBuf := new(bytes.Buffer) </del> <ins> buf := new(buffer) errBuf := new(buffer) </ins> klog.SetOutputBySeverity(\"INFO\", buf) klog.SetOutputBySeverity(\"WARNING\", errBuf)", "positive_passages": [{"docid": "doc-en-kubernetes-59b9ae5b52e0b40199c236ff5490b403bebb933bd0751cd293a630848c9a0b07", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: What you expected to happen: No data races How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\nfor the record as we tend to lose the logs in the gcs bucket\n/sig instrumentation", "commid": "kubernetes_issue_98941", "tokennum": 247}], "negative_passages": []}
{"query_id": "q-en-kubernetes-37ee218c2d0cf1f54b8408dd441addd7f7155f78ac20449befa997ed1cfeb60c", "query": "// Flaky operation failures in an e2e test can be captured through this. flakeReport *FlakeReport <del> // To make sure that this framework cleans up after itself, no matter what, // we install a Cleanup action before each test and clear it after.  If we // should abort, the AfterSuite hook should run all Cleanup actions. cleanupHandle CleanupActionHandle </del> // afterEaches is a map of name to function to be called after each test.  These are not // cleared.  The call order is randomized so that no dependencies can grow between // the various afterEaches", "positive_passages": [{"docid": "doc-en-kubernetes-2e8b5198754cc6270240a247dfa503fa4a3eeae2d5481e425503db2c2c68474d", "text": "Here is a list of TODOs that could be fixed for Ginkgo migration from v1 to v2. [x] Lost the validation on the SIGDescribe: [x] Ginkgo V2 currently cannot get the number of specs that will run in , this might be fixed in the Ginkgo's minor release of V2 in the future. [x] <delGinkgo dry-run mode has dropped the test spec in V2 (), consider to switch back to use to generate test spec when the feature is ready in . </del--- This has been fixed in Ginkgo 2.1.4 [x] <delMigrate all the custom reporter in , should be lightweight and not sure where those custom reporters are used. </delFixed here: [x] Replace all the camel case flags to kebab case flags, e.g. to . [x] <delRemove the legacy e2e test binary's parameter and in 1.28, those parameters were used to manage report, this is no longer needed for Ginkgo v2. </delno longer needed. [x] upgrade vendor when is migrated to ginkgo v2, this will help to remove the dependency of - [x] <delrevisit to explore the possibility to cover the test in Ginkgo V2. </delfixed by [x] remove the workaround introduced in Ginkgo V1 ( is not called after hitting ^c): partially addressed by: , some cleanup needed for each sig before removing the hook entirely. I think has the pr to fix this entirely, but I cannot get the link for that, mark it as resolved. : [x] New work item (?): capture only a single output text output stream () in JUnit (this issue was resolved along with another one in ) [ ] Due to the junit format change, some tool which use to grab \"value\" directly cannot get the failure reason as what it does in v1. [x] Test failures are missing information since GinkgoV2 migration [ ] is clustering stack traces, not failure text () Address those leftovers if there is any update from Ginkgo in the future. see the relevant link on the each of the issues.", "commid": "kubernetes_issue_109744", "tokennum": 483}], "negative_passages": []}
{"query_id": "q-en-kubernetes-37ee218c2d0cf1f54b8408dd441addd7f7155f78ac20449befa997ed1cfeb60c", "query": "// Flaky operation failures in an e2e test can be captured through this. flakeReport *FlakeReport <del> // To make sure that this framework cleans up after itself, no matter what, // we install a Cleanup action before each test and clear it after.  If we // should abort, the AfterSuite hook should run all Cleanup actions. cleanupHandle CleanupActionHandle </del> // afterEaches is a map of name to function to be called after each test.  These are not // cleared.  The call order is randomized so that no dependencies can grow between // the various afterEaches", "positive_passages": [{"docid": "doc-en-kubernetes-c4753cc2146447a07d108ff02ffe6d67b2be2a6ba7adffaf5026d0a94c1c787a", "text": "No response_ <details</details<detailsall </details<details</details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig testing\n/cc\n/cc\nhello! I would like to work on this issues\nI think we cannot do anything now except the last two, and those two should be based on top of the:\nI would like to work on task 5 of this issue\nno problem, pls wait for an while until that PR got merged, then you can create a pr to fix those deprecated parameters.\nRegarding : searching for points out the places where the workaround is used and needs to be replaced once is solved.\nI just noticed this comment in\nseems like is not used in k/k, but in other sigs.\nhmm... I just grepped the test code, will push a pr to fix this.\n/open\n/re-open\nokay, this is not resolved actually, but I have no way to re-open it.\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n~ it seems that some more jobs needs to be adapted to not use parallel~ [repo][0]=kubernetes/test-infra~ ~ACTION REQUIRED: Ginkgo V2 doesn't accept go test's flags to parallelize Ginkgo specs, please switch to use or instead.~ Sorry for the noise, the flag is passed to kubetest, and it correctly translate it to , it is not the issue here\nnp, thanks for the update!\nNew work item (?): capture only a single output text output stream () in JUnit.\nupdated the issue, haven't got a chance to take a close look at the item though.\nThis should be resolved by \"open stdout\" now should only appear if a test intentionally records SpecReports.\nmark it as resolved.\nis this complete now?", "commid": "kubernetes_issue_109744", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-37ee218c2d0cf1f54b8408dd441addd7f7155f78ac20449befa997ed1cfeb60c", "query": "// Flaky operation failures in an e2e test can be captured through this. flakeReport *FlakeReport <del> // To make sure that this framework cleans up after itself, no matter what, // we install a Cleanup action before each test and clear it after.  If we // should abort, the AfterSuite hook should run all Cleanup actions. cleanupHandle CleanupActionHandle </del> // afterEaches is a map of name to function to be called after each test.  These are not // cleared.  The call order is randomized so that no dependencies can grow between // the various afterEaches", "positive_passages": [{"docid": "doc-en-kubernetes-138d08f1aeca8e81cbf8aa639b51baa29b1653208e0d897ccfc4810c9421dc3e", "text": ", Only two of them left, I need to follow this one, here is the issue for this one opened in the Ginkgo: I think this should be fixed in the third party tools instead of Kubernetes, if we agree with that, we can mark it as completed as well. For the first one, I will continue to follow until there is a update from Ginkgo's side, for the later one, there is no consensus yet IIUC, we can open a separate issue for that, I am gonna to close this one since there is no much thing we can do now. /close\nWe agreed to fix the tool, but had no issue open for it. I just created one:\nAnother issue for", "commid": "kubernetes_issue_109744", "tokennum": 149}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3806e88f8ab49e330a5f7f92e14e75207b7a345413e95228a0fbbc0d8beff2f9", "query": "if err != nil { t.Fatalf(\"Failed to create scheduler: %v\", err) } <ins> // Profiles </ins> profiles := make([]string, 0, len(s.Profiles)) for name := range s.Profiles { profiles = append(profiles, name)", "positive_passages": [{"docid": "doc-en-kubernetes-75719ce40debdc24665e0bd0c466c638c232f756949a78511459bd94dde06b58", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --here is supposed to be set through , but is not called from anywhere except tests, so always returns . should be set through here. Am I missing something? N/A None Kubernetes version (use ): master () Cloud provider or hardware configuration: N/A OS (e.g: ): N/A Kernel (e.g. ): N/A Install tools: N/A Network plugin and version (if this is a network-related bug): N/A Others: None\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scheduling\nThanks for pointing that out. The plumbing of extenders to the framework impact calling extenders on preemption. That seems to be a path not covered by tests end to end. Can you submit a PR to fix this? as you mentioned we need to pass the extenders on profile creation. We need to patch the fix back to v1.21 and v1.20 (the release where this was refactored). /cc\nI have submitted a PR for a fix.", "commid": "kubernetes_issue_102971", "tokennum": 348}], "negative_passages": []}
{"query_id": "q-en-kubernetes-381713c312f40c36135bacc77b1a4d473f78153112d86c31d0cb2fe88e9b243f", "query": "defaultPodResourcesPath    = \"/var/lib/kubelet/pod-resources\" defaultPodResourcesTimeout = 10 * time.Second defaultPodResourcesMaxSize = 1024 * 1024 * 16 // 16 Mb <ins> kubeletReadOnlyPort        = \"10255\" kubeletHealthCheckURL      = \"http://127.0.0.1:\" + kubeletReadOnlyPort + \"/healthz\" </ins> ) func getNodeSummary() (*stats.Summary, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-88c095cfe151193749adeb925825c9856381f9f8544c8822d93b8eb731e64566", "text": "ci-kubernetes-node-kubelet-serial-hugepages when start the pod with the resources requests that contain multiple hugepages resources should set correct hugetlb mount and limit under the container cgroup Unexpected error: \"pod ran to completion\", Multiple sizes huge pages is going to be graduated to GA, so having this test job fixed is quite important.\n/sig node\n/assign\n/triage accepted\n/cc\nI did a small analysis and I can see that the pod failed to start, I can not find any failure messages under the kubelet log, so it really hard to say why it failed.\nwere you able to reproduce it locally? btw, there is a \"right way\" to fix this - to fix dynamic update of a hugepage resources. This would eliminate need in a kubelet restart. There is even a PR for that: , we just need to make it working again.\nafter conversation with on slack I'd say we should stick to the current procedure - restarting kubelet when hugepages allocation changes. So, we should investigate why kubelet doesn't restart properly in this test case and fix it.\nNope, I failed to reproduce it locally, also under the CI, it does not appear often. The best thing will be to describe the pod in case if it failed, so we will see the reason.\nunder the code we have so from the log , I can see that the kubelet received the pod before the kubelet stopped, so the problem that pod dropped to Failed state because of the kubelet stop.\nSo some additional details, the one who responsible to restart the kubelet again, is the server service: restart the kubelet service are waiting for hugepages to be available are starting the pod server service restart the kubelet again because it was not healthy for too long - failed to start because of the kubelet restart\ngreat findings! Should we just stop the kubelet and let the server service to start it again? We can also check if the kubelet is restarted successfully before starting the pod.\nI tried it under the PR , also I unsure how can we check if the kubelet restarted successfully. All tests that I wrote before I checked if the node has NotReady state and waited until it will be Ready, but in case of the restart probably the node will always have Ready state because the time period is very short. I will continue to investigate and will check locally how can I fix it.", "commid": "kubernetes_issue_99402", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-381713c312f40c36135bacc77b1a4d473f78153112d86c31d0cb2fe88e9b243f", "query": "defaultPodResourcesPath    = \"/var/lib/kubelet/pod-resources\" defaultPodResourcesTimeout = 10 * time.Second defaultPodResourcesMaxSize = 1024 * 1024 * 16 // 16 Mb <ins> kubeletReadOnlyPort        = \"10255\" kubeletHealthCheckURL      = \"http://127.0.0.1:\" + kubeletReadOnlyPort + \"/healthz\" </ins> ) func getNodeSummary() (*stats.Summary, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-df5fd4d114576094d5b1a71b893d21a3e13b2c561e9313633a9dfbe243849634", "text": "So the only reliable solution that I found, it just trying to start the pod number of times. I tested it 5 times and the test passed. Can you please review\nCan we access kubelet service from hugepage test cases? If we can we can use its APIs like or to check if kubelet is ready after the restart. Overall I have a feeling of duplication test/e2enode/services functionality in This is a main reason for this and similar bugs I believe. It would be nice to get rid of this duplication if possible. That would nicely isolate kubelet service controls in one place and eliminate conflicts like this one. wdyt?\nnot really, the used mostly to start all needed components to emulate the cluster(not only the kubelet) and the test does not have access to it. I think you can separate the readiness check under the importable method, but it worth the separate PR.\nI updated the PR to check the healthiness of the kubelet and looks like it works just fine.\nthank you. it looks good to me so far. I'll add lgtm label when is merged and tests are all green.\nthe job is still flaky. can you reopen this issue?\nI opened a different one - , the issue can affect any job, not only the hugepages one.\nI can open a fix to W/A an issue(start the pod until it will succeed), it should fix all problems, WDYT?\ni think it's ok as a workaround, until is fixed\nwould it be better to wait until api server reports correct resource value before running the pod?\nWe are waiting for it, the problem that the scheduler and the kubelet see a different picture regarding resources requested by pods.\nok. In this case restarting the pod until it succeeds seems reasonable to me to fix the flakiness until is fixed.\nany progress on the workaround fix?", "commid": "kubernetes_issue_99402", "tokennum": 404}], "negative_passages": []}
{"query_id": "q-en-kubernetes-38c1787b9e947b3103f2ac63110da1c715d0e4c8c55286c2272fd404ab6fa3cc", "query": "} // if we're trying to hit the kube-apiserver and there wasn't an explicit config, use the in-cluster config <del> if server == \"kubernetes.default.svc\" { </del> <ins> if target == \"kubernetes.default.svc\" { </ins> // if we can find an in-cluster-config use that.  If we can't, fall through. inClusterConfig, err := rest.InClusterConfig() if err == nil {", "positive_passages": [{"docid": "doc-en-kubernetes-73496a383d34eb1ab5962a20be4dce66952c6d20058c4ff89ce94afc1cb5683d", "text": "We are getting the following error when the apiserver connects the webhook on localhost (configured via URL). We should only use the SSL tunnel for the connections to nodes when the webhooks are running as services. /sig api-machinery /kind bug /assign\n/close", "commid": "kubernetes_issue_58779", "tokennum": 64}], "negative_passages": []}
{"query_id": "q-en-kubernetes-38f2c460b7a46178a2142071559a72fb71787feabe6626bc6205bfeb0a6cb934", "query": "} } <ins> // printPodsMultiline prints multiple pods with a proper alignment. func printPodsMultiline(w PrefixWriter, title string, pods []api.Pod) { printPodsMultilineWithIndent(w, \"\", title, \"t\", pods) } // printPodsMultilineWithIndent prints multiple pods with a user-defined alignment. func printPodsMultilineWithIndent(w PrefixWriter, initialIndent, title, innerIndent string, pods []api.Pod) { w.Write(LEVEL_0, \"%s%s:%s\", initialIndent, title, innerIndent) if pods == nil || len(pods) == 0 { w.WriteLine(\"<none>\") return } // to print pods in the sorted order sort.Slice(pods, func(i, j int) bool { cmpKey := func(pod api.Pod) string { return pod.Name } return cmpKey(pods[i]) < cmpKey(pods[j]) }) for i, pod := range pods { if i != 0 { w.Write(LEVEL_0, \"%s\", initialIndent) w.Write(LEVEL_0, \"%s\", innerIndent) } w.Write(LEVEL_0, \"%sn\", pod.Name) } } </ins> // printPodTolerationsMultiline prints multiple tolerations with a proper alignment. func printPodTolerationsMultiline(w PrefixWriter, title string, tolerations []api.Toleration) { printTolerationsMultilineWithIndent(w, \"\", title, \"t\", tolerations)", "positive_passages": [{"docid": "doc-en-kubernetes-b97e647702b8859b86e9b0127fc694e7b8feffe09fe2ccd8837b28995c7af595", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: I need to know to which Pod(s) a PVC is being mounted to, without having to go through each Pod one by one checking the Volume mounts and the PersistentVolumeClaim. The kubectl describe pvc and get pvc, only tell you to which Persistent Volume the PVC is bound to, but not if is being used by a Pod(s) What you expected to happen: Add a new field in the describe or get that lists the pods that are using the PVC as a volume mount How to reproduce it (as minimally and precisely as possible): Have a PV/PVC bound and create a pod using a volume mount Anything else we need to know?: Not sure if this is only for Azure Disk, which is the Storage Class I am using. Environment: Kubernetes version (use ): 7 Cloud provider or hardware configuration: Azure OS (e.g. from /etc/os-release): Ubuntu 16.04 Kernel (e.g. ): 4 Install tools: Azure Kubernetes Services Others: -n/a\n/sig storage\n/sig cli\nI think the kubectl describe can just construct this on the fly. Another angle is should we add this information to PVC object itself\nThat will be great, as right now the only way to correlate a PVC to a Pod is via a \"describe\" on the Pod.\nI can work on a PR for this!\nGitHub didn't allow me to assign the following users: clandry94. Note that only and repo collaborators can be assigned. <detailsIn response to : I can work on 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\n+1 for the feature. cc\nHow to find \"what pods are using particular PVC through command line\"\n+1 for the feature.\nthis feature will be in Kubernetes 1.12\nok kubernetes 1.12 released, how to? which command?\nCan someone point to the documentation or paste command to get the pods which have the PVC in use\nsee the associated PR to see an example usage of this The line in should show it.\nWorkaround for the meantime:\nThanks , this workaround is great for those people who still use old kubernetes version.", "commid": "kubernetes_issue_65233", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-38f2c460b7a46178a2142071559a72fb71787feabe6626bc6205bfeb0a6cb934", "query": "} } <ins> // printPodsMultiline prints multiple pods with a proper alignment. func printPodsMultiline(w PrefixWriter, title string, pods []api.Pod) { printPodsMultilineWithIndent(w, \"\", title, \"t\", pods) } // printPodsMultilineWithIndent prints multiple pods with a user-defined alignment. func printPodsMultilineWithIndent(w PrefixWriter, initialIndent, title, innerIndent string, pods []api.Pod) { w.Write(LEVEL_0, \"%s%s:%s\", initialIndent, title, innerIndent) if pods == nil || len(pods) == 0 { w.WriteLine(\"<none>\") return } // to print pods in the sorted order sort.Slice(pods, func(i, j int) bool { cmpKey := func(pod api.Pod) string { return pod.Name } return cmpKey(pods[i]) < cmpKey(pods[j]) }) for i, pod := range pods { if i != 0 { w.Write(LEVEL_0, \"%s\", initialIndent) w.Write(LEVEL_0, \"%s\", innerIndent) } w.Write(LEVEL_0, \"%sn\", pod.Name) } } </ins> // printPodTolerationsMultiline prints multiple tolerations with a proper alignment. func printPodTolerationsMultiline(w PrefixWriter, title string, tolerations []api.Toleration) { printTolerationsMultilineWithIndent(w, \"\", title, \"t\", tolerations)", "positive_passages": [{"docid": "doc-en-kubernetes-d7becb5323d04fe79bf1f030fc587d9b0aefb9105f1724f943828245df0352e1", "text": "However it will meet an error if the pod have no volumes, so I improves it by adding a to check whether the volumes exists or not.\npython script to list pods with pvc in namespace(s): Is a part of a cli to set pods with velero/restic annotations. Hope it helps someone :)\nFor posterity... There is a Used By: field in the output of describe.\nclient-go didn't give this api... ,PodPVCIndex can solve the problem\nHi thanks worked for me ;) but I want to make it reverse my workarounds with adding after didn't worked do you have any ideas\n$ kubectl describe pvc -A Used\" Name: ocs-deviceset-lso-volumeset-0-data-1b45dn Namespace: openshift-storage StorageClass: lso-volumeset Used By: rook-ceph-osd-1--8fwpd Also useful ^\nthe reason it didn't work is because each return does, in point of fact, have a key defined for claimName. That key is just set to null value. So, what you'd actually want to do is test for nulls. As nice as answer is, it's a PITA to parse unstructured human-readable command output, as opposed to command output in a markup language that well known shell parsers like jq and yq can work with. Towards that end, because I had use of this, I came up with the following: That simple not null test at the end plucks out all your nulls. Obviously invert the last conditional if you want all the nulls, but you'll get all sorts of temp things that way that you probably won't care about.", "commid": "kubernetes_issue_65233", "tokennum": 387}], "negative_passages": []}
{"query_id": "q-en-kubernetes-393b8d4a6cf0a1c2d5e1445b62ca4abaead3cf19a0374773edaa69aaa28b5208", "query": "NoSnatTestProxy          = ImageConfig{e2eRegistry, \"no-snat-test-proxy\", \"1.0\", true} NWayHTTP                 = ImageConfig{e2eRegistry, \"n-way-http\", \"1.0\", true} // When these values are updated, also update cmd/kubelet/app/options/options.go <del> Pause               = ImageConfig{gcRegistry, \"pause\", \"3.0\", false} </del> <ins> Pause               = ImageConfig{gcRegistry, \"pause\", \"3.0\", true} </ins> Porter              = ImageConfig{e2eRegistry, \"porter\", \"1.0\", true} PortForwardTester   = ImageConfig{e2eRegistry, \"port-forward-tester\", \"1.0\", true} Redis               = ImageConfig{e2eRegistry, \"redis\", \"1.0\", true}", "positive_passages": [{"docid": "doc-en-kubernetes-b17ee1dc189a7b4f3a1873cc63d0b98225c1c3184abd41b75f3a03dd8e681b66", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: Failures - https://k8s- Part of pause is not used properly for tests for other arches than x86. As the current pause image is not a manifest image, so we need to use a different image for different archs like for , for etc.. With this, I'm using logs-generator from repo What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/sig testing\n/assign", "commid": "kubernetes_issue_57588", "tokennum": 189}], "negative_passages": []}
{"query_id": "q-en-kubernetes-394a8c1e3ce153172bcb23873187ce34ec33a6a816d48ad429da941cf452e8fc", "query": "import ( \"context\" \"fmt\" <del> \"strconv\" </del> <ins> \"os\" </ins> \"strings\" v1 \"k8s.io/api/core/v1\"", "positive_passages": [{"docid": "doc-en-kubernetes-93c0a615d6725c12b66abb2dead01e17ca700d451119b1467d3edce68f73a013", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: If computer name prefix does not match VMSS name, then Azure cloud provider will use VMSS API instead of using metadata service data. This leads to throttling, because every affected kubelet is making API requests. What you expected to happen: Azure cloud provider should use metadata service data instead of calling VMSS API when instance is current. How to reproduce it (as minimally and precisely as possible): Set computer name prefix of the VMSS to something different than default. You should observe Azure provider making requests to the VMSS API rather than using metadata service, which leads to throttling if you have multiple kubelets with this bug. Anything else we need to know?: This is bug was introduced by - returns false even if instance is current, because it expects node name to match VMSS name + instance id, however node name is derived from the computer-name-prefix which can be different than VMSS name. Node name should be matched against , not against . Environment: Kubernetes version (use ): 1.18.x and higher Cloud provider or hardware configuration: azure /sig cloud-provider\n/sig cloud-provider\n/area provider/azure\nCC\n/remove-sig cloud-provider /sig cloud-provider (trying to remove the label)\n/sig cloud-provider\nThanks for the reporting. Unfortunately, computer name prefix is not included in IMDS, so it can't be used without VMSS API for constructing the NodeName. Would check what could we do to workaround the issue.\nCan you memorize the computer name prefix in the first request to the Azure API and then use it for the isCurrentInstance check?\nopened to fix the issue. Would you like to have a look?\nI can confirm that your change should fix the problem I reported. Do you know if your fix will be to 1.18.x?\nis working on the cherry pick\nThank you for quick fix!", "commid": "kubernetes_issue_92733", "tokennum": 464}], "negative_passages": []}
{"query_id": "q-en-kubernetes-39b2deef9cd74f5120775ae32b4237153a265703e1e7d8cfc1723e83848a95a2", "query": "// list all pods to include the pods that don't match the rc's selector // anymore but has the stale controller ref. // TODO: Do the List and Filter in a single pass, or use an index. <del> pods, err := rm.podLister.Pods(rc.Namespace).List(labels.Everything()) </del> <ins> allPods, err := rm.podLister.Pods(rc.Namespace).List(labels.Everything()) </ins> if err != nil { return err } // Ignore inactive pods. var filteredPods []*v1.Pod <del> for _, pod := range pods { </del> <ins> for _, pod := range allPods { </ins> if controller.IsPodActive(pod) { filteredPods = append(filteredPods, pod) }", "positive_passages": [{"docid": "doc-en-kubernetes-38d52777560a5c6fb71d98b8b0953e61c4be2731ef4a377191b06cc53fcf6655", "text": "https://k8s- Failed: [] Network Partition [Disruptive] [Slow] [] [ReplicationController] should eagerly create replacement pod during network partition when termination grace is non-zero {Kubernetes e2e suite}\nhttps://k8s- seems to be the first failure here. It seems to have gone in with a bunch of RC/RS changes () cc/", "commid": "kubernetes_issue_37479", "tokennum": 88}], "negative_passages": []}
{"query_id": "q-en-kubernetes-39c1f2263fc5373756b095b922f8162b1339e139e749d61369ea1a6ab93ddbcd", "query": "\"time\" v1 \"k8s.io/api/core/v1\" <ins> apierrors \"k8s.io/apimachinery/pkg/api/errors\" </ins> metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/runtime\" utilfeature \"k8s.io/apiserver/pkg/util/feature\"", "positive_passages": [{"docid": "doc-en-kubernetes-31eecfa3591815d34ddfcff16c3269edcba1de74efc4a8809ac7fe48d40e0f43", "text": "When using a generic ephemeral volume, the volume binder in kube-scheduler typically processes a new pod before the generic volume controller in kube-controller-manager has a chance to create the PVC. This leads to events for pods using generic ephemeral volumes: It would be nice to suppress these warnings for a short while (duration to be determined) after the pod creation. Later they should be emitted because then they indicate that the generic volume controller isn't working properly. This makes nicer to use.\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig storage", "commid": "kubernetes_issue_104525", "tokennum": 198}], "negative_passages": []}
{"query_id": "q-en-kubernetes-39d4ac5cf7503e6c03ab41b7521cbe2c02fd6fc37cff0b6451766717059a7c8b", "query": "<ins> # See the OWNERS docs at https://go.k8s.io/owners approvers: - lavalamp - smarterclayton - deads2k - sttts - liggitt - caesarxuchao reviewers: - thockin - lavalamp - smarterclayton - wojtek-t - deads2k - derekwaynecarr - caesarxuchao - cheftako - mikedanese - liggitt - gmarek - sttts - ncdc - logicalhan - tallclair labels: - sig/api-machinery </ins>  No newline at end of file", "positive_passages": [{"docid": "doc-en-kubernetes-1e3d5f814d3d1cd0ae92f2f9adc262569d0e3418b95dbcb250b25bdb3821fc75", "text": "This issue proposes the writing of a new test for the API endpoint with the intention of promoting it to Conformance. This issue contains a very masic mock test in order to start the conversation about what a good e2e test would look like for this endpoint. The code below is verified to be hitting the intended endpoint, show as per the queries in APIsnoop's live view of the cluster's audit logs. According to this query, there is only one API endpoint which is for Namespace that isn't being covered. We selected patchCoreV1Namespace to write a test for. Dependencies: The mock test: If a test with these calls is build and merged, conformance will go up by 1 endpoint.\n/sig testing /sig architecture /area conformance", "commid": "kubernetes_issue_86051", "tokennum": 169}], "negative_passages": []}
{"query_id": "q-en-kubernetes-39deb8a05a025873f85f2a8ef0dcec1ce1fb5e65e9f08d5ccb45e1e63ac5087e", "query": "kubectl get pods \"${kube_flags[@]}\" -lname=redis-master | grep -q 'redis-master' [ ! $(delete pods --all pods -l name=redis-master) ]   # not --all and label selector together kubectl delete --all pods \"${kube_flags[@]}\" # --all remove all the pods <ins> kubectl create -f examples/guestbook/redis-master.json \"${kube_flags[@]}\" kubectl create -f examples/redis/redis-proxy.yaml \"${kube_flags[@]}\" kubectl get pods redis-master redis-proxy \"${kube_flags[@]}\" kubectl delete pods redis-master redis-proxy # delete multiple pods at once howmanypods=\"$(kubectl get pods  -o template -t \"{{ len .items }}\" \"${kube_flags[@]}\")\" [ \"$howmanypods\" -eq 0 ] kubectl create -f examples/guestbook/redis-master.json \"${kube_flags[@]}\" kubectl create -f examples/redis/redis-proxy.yaml \"${kube_flags[@]}\" kubectl stop pods redis-master redis-proxy # stop multiple pods at once </ins> howmanypods=\"$(kubectl get pods  -o template -t \"{{ len .items }}\" \"${kube_flags[@]}\")\" [ \"$howmanypods\" -eq 0 ]", "positive_passages": [{"docid": "doc-en-kubernetes-8781beaf9cecb5a2a5891763e358d97bbb8efac5ebba9fc986604965efa0dda5", "text": "Currently, it could not delete multiple pods at once, need to delete them one by one, it's very inconvenient if I have tons of pods to delete. Unlike docker, docker can multiple stop/rm containers/images at once.\nThis is possible using label selectors as of , which is better if you have tons of pods.\nI agree that using label selector is better to delete all of pods under the label. But to delete multile pods at once is still usable: I just want to delete 1/2 pods under the label, label selector will not work selector could not span over other selectors or pods Another reason is docker rm/stop x y z works, I will wonder why kubectl cannot. This is not urgent, but I hope it can be implemented.\nI agree. Thanks for the suggestion.\nWould this be a suitable task for someone new to k8s development? If so, I'd be willing to take a look at this, if someone could provide a couple of hints where to start.\nFurther to my last message, I have a functional work in progress I would like to share, if anyone is interested?\nPRs are welcome. See\nYes, this is a reasonable place to start. Since its in the client, you won't get much orientation to the core server code, but it will be a good place to orient to the client side API. There us also prior art that you can model off of. The kubectl create ... command already supports multiple resources. A good command to adapter would be the 'label' command. You can find it in Many thanks in advance! Brendan On Feb 19, 2015 8:21 AM, \"Eric Tune\" wrote:", "commid": "kubernetes_issue_3050", "tokennum": 364}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3a193e6556577f920437eec7801ca7a65a1d491f7fab01bae98e4115a12ccfe6", "query": "func (c *connection) RemoveStreams(streams ...httpstream.Stream) { c.streamLock.Lock() for _, stream := range streams { <del> delete(c.streams, stream.Identifier()) </del> <ins> // It may be possible that the provided stream is nil if timed out. if stream != nil { delete(c.streams, stream.Identifier()) } </ins> } c.streamLock.Unlock() }", "positive_passages": [{"docid": "doc-en-kubernetes-68fed35f8c13d4bb380046d0fa704085775461d797cc59667c2cdfcb32483bea", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --Since upgrading to Kubernetes v1.19.11 (from v1.19.10) we see occasional panics in kubelet related to portforward streams: This issue seem to be introduced with should not panic and crash. We have not been able to successfully force this to happen, but it has happened 41 times in the last 2 weeks across 7 clusters (~100 nodes). Kubernetes version (use ):Cloud provider or hardware configuration: Self managed clusters on AWS. OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others: /sig node /cc\nHey thank you for the report! :pray: Uhh, thats unfortunate. The panic occurs there on L101: It looks like because works. The stack trace indicates the same: A on is a no-op, so would not be harmful. does also not seem to be , a crash in would have been visible in the stack trace. It may be possible that something assigned to the stream interface. Which means a check for will return , but accessing its fields is causing a segmentation fault. This does not explain why the crash is not visible in the trace.\nWith a quick look at the streaming code it's likely to be triggered by a timeout in waiting for streams: If the above case is hit then it goes down to , and if the timeout occurs before then it means that either or And then it attempts to remove the streams where at least one is : So it probably makes sense to check for either before passing to or inside the method where it crashes. This theory lines up with our kubelet logs, where I can see this just before the panic (didn't notice before):\nThank you for the summary working on a fix in\n/triage accepted /assign\ndo you use dockershim within your cluster?\nYes, we still use dockershim.\nGood, that's also why the panic happens within the kubelet.\nJust to make sure I understand the scope of this issue, this only affects things like or other things that use the API, correct?\nExactly :+1:", "commid": "kubernetes_issue_102480", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3a27ae5ffaf72d35de3877969d9cfa5c9d4ad305dce1b4096d62d07ec6d41fd8", "query": "return nil, fmt.Errorf(\"failed to start container %q: %v\", r.ContainerId, err) } <del> ds.performPlatformSpecificContainerForContainer(r.ContainerId) </del> return &runtimeapi.StartContainerResponse{}, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-486ca0159276eedd0d2aa336961ee5fd6fb83d0ac97af7f3f9c8c863d43fcef2", "text": "What would you like to be : Periodically remove cleanupInfos for old containers from dockershim's map. One way of doing that would be to just forget about s older than say an hour, as they should always be short-lived. Why is this needed: introduced a new in-memory map for the dockershim, that could potentially (in pathological cases) cause memory leaks - for containers that use GMSA cred specs, get created successfully, but then never get started nor removed. This might be okay for the alpha release of the GMSA feature, but should be addressed in the beta. See\n/assign wk8\n/sig windows\n/milestone v1.15\ngot moved out. let's move this issue with it as well /milestone v1.16\nHello! I'm bug triage lead for the 1.16 release cycle and considering this issue is tagged for 1.16, but not updated for a long time, I'd like to check its status. The code freeze is starting on August 29th (about 1.5 weeks from now), which means that there should be a PR ready (and merged) until then. Do we still target this issue to be fixed for 1.16?\n: yup we'd love to have this in 1.16, still waiting for kind reviewers on :) ...", "commid": "kubernetes_issue_74843", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3a2f39f9abc333fc5d2af805bd7a4774965e2f6b5759e12c20950eedd1dd77f9", "query": "import ( corev1 \"k8s.io/api/core/v1\" discovery \"k8s.io/api/discovery/v1alpha1\" <ins> apiequality \"k8s.io/apimachinery/pkg/api/equality\" </ins> \"k8s.io/apimachinery/pkg/api/errors\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" corev1client \"k8s.io/client-go/kubernetes/typed/core/v1\"", "positive_passages": [{"docid": "doc-en-kubernetes-12f7047d8d873a7d6bac7023fc38517c350449071b3fe2b6d53f3ea14de5351f", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: EndpointSlice for masters was not created after enabling EndpointSlice on a pre-existing cluster. Only those EndpointSlices managed by kube-controller-manager were created. What you expected to happen: EndpointSlice for masters should be created after enabling EndpointSlice on a pre-existing cluster, the same as the EndpointSlices managed by kube-controller-manager. How to reproduce it (as minimally and precisely as possible): kubeadm to create a cluster: the EndpointSlice feature by editing the kube-apiserver, kube-controller-manager, kube-proxy manifest kube-apiserver and kube-controller-manager is restarted, the EndpointSlice in namespace will be missing. Anything else we need to know?: Environment: Kubernetes version (use ):Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools:Network plugin and version (if this is a network-related bug): Others:\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/remove-triage unresolved /assign", "commid": "kubernetes_issue_84419", "tokennum": 307}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3a33e50c320c2799dac0f2feda2a80c9a674d75bc917c41c5d194a7c694e56ba", "query": "fs.BoolVar(&o.config.IPVS.StrictARP, \"ipvs-strict-arp\", o.config.IPVS.StrictARP, \"Enable strict ARP by setting arp_ignore to 1 and arp_announce to 2\") fs.BoolVar(&o.config.IPTables.MasqueradeAll, \"masquerade-all\", o.config.IPTables.MasqueradeAll, \"If using the pure iptables proxy, SNAT all traffic sent via Service cluster IPs (this not commonly needed)\") <del> fs.BoolVar(&o.config.EnableProfiling, \"profiling\", o.config.EnableProfiling, \"If true enables profiling via web interface on /debug/pprof handler.\") </del> <ins> fs.BoolVar(&o.config.EnableProfiling, \"profiling\", o.config.EnableProfiling, \"If true enables profiling via web interface on /debug/pprof handler. This parameter is ignored if a config file is specified by --config.\") </ins> fs.Float32Var(&o.config.ClientConnection.QPS, \"kube-api-qps\", o.config.ClientConnection.QPS, \"QPS to use while talking with kubernetes apiserver\") <del> fs.Var(&o.config.DetectLocalMode, \"detect-local-mode\", \"Mode to use to detect local traffic\") </del> <ins> fs.Var(&o.config.DetectLocalMode, \"detect-local-mode\", \"Mode to use to detect local traffic. This parameter is ignored if a config file is specified by --config.\") </ins> } // NewOptions returns initialized Options", "positive_passages": [{"docid": "doc-en-kubernetes-d25af00145ce02f273723fdbada2e8cd6b506acebe2a7cb4f99e67bf0c6cc038", "text": "Start service with a config file without specifying the argument in the config file, instead, pass the value via the CLI args, the value is just ignored, for example, I have a config file as this, NOTE: I have not specified the in the config file, but give a value for the via the CLI, the proxy mode is still set as after the service is started. The reason for this is that CLI args is parsed before the loading of the config file, if the config file haven't specified the or leave it as empty, then it will be use the default value instead. Two choices from my side, Add a note somewhere, maybe where the option is defined, just say that the CLI args will be ignored when the config file is provided regardless the option is specified in the config file or not (this should be noted for lots of options). Merge the value passed from CLI with the config file if the option has an empty value, but we need to consider the backward compatibility. and check which mode is effective. No response_ vanilla deployment with code in the upstream. <details</details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig network Hey Tim, WDYT? /assign\nHeh, this is a recurrent topic :smile: , you did a great analysis: I think that explains here why merging flags and config overriding defaults is not a desirable option (the whole thread is worth reading) I'm in favor of documenting the behavior\nthanks for showing the earlier thread, I have created a simple PR to document this in the CLI option.", "commid": "kubernetes_issue_107156", "tokennum": 446}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3a82594211a06f6fec67d6eae9a610117792d864f482938a64a41e80434c9052", "query": "package priorities import ( <ins> \"os/exec\" </ins> \"reflect\" \"sort\" \"strconv\"", "positive_passages": [{"docid": "doc-en-kubernetes-3229e3f28f67afa9ddea85d9d31a50803c261e0ae30f76f950060d1790215e64", "text": "I just noticed you forgot to register the image locality priority function in in I also missed it when I reviewed your PR. I have fixed this in . But it would be great if you could figure out a mechanism that would ensure that all predicate/priority functions that are tested (you can assume they will always live under ) are registered, and fail the test if not. That will allow us to prevent this mistake in the future.\nThanks! Will fix this soon!\nSeems need to wait for in before I send PR? Otherwise this test will always fail ...", "commid": "kubernetes_issue_21236", "tokennum": 114}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3a8a687264efab730523d8ff5d11f9e6bbe8a9e26ff412babe5ee4238e3b7942", "query": "opencontrail_kubernetes_tag: '$(echo \"$OPENCONTRAIL_KUBERNETES_TAG\" | sed -e \"s/'/''/g\")' opencontrail_public_subnet: '$(echo \"$OPENCONTRAIL_PUBLIC_SUBNET\" | sed -e \"s/'/''/g\")' e2e_storage_test_environment: '$(echo \"$E2E_STORAGE_TEST_ENVIRONMENT\" | sed -e \"s/'/''/g\")' <ins> enable_hostpath_provisioner: '$(echo \"$ENABLE_HOSTPATH_PROVISIONER\" | sed -e \"s/'/''/g\")' </ins> EOF cat <<EOF >/etc/salt/minion.d/log-level-debug.conf", "positive_passages": [{"docid": "doc-en-kubernetes-ef45ff070b2c05a069c3f77b9a64e0bfff59d1f717362ac04203c879e5a7b68c", "text": "feature request Enables easier testing for pv/pvc, and all derivatives like pet sets. The only alternative is to use manually created pv of local type. I have time to work on it myself and created this feature to collect feedback/ideas on what provider should be enabled by default.\nSince this was merged should we close this issue?", "commid": "kubernetes_issue_32119", "tokennum": 67}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3a9e7acb7dceedac16a6506a18bbf04260c0eb4cb06fc96b5ad3cecdba2b2374", "query": "<ins> {% if pillar.get('enable_node_autoscaler', '').lower() == 'true' %} </ins> {% set params = pillar['autoscaler_mig_config'] -%} { \"kind\": \"Pod\",", "positive_passages": [{"docid": "doc-en-kubernetes-cafbbd3cd664270b9fbd0ce7e8faa35ad0e8800a7c5d7cdeb5164eec0f1b24f1", "text": "For some reason they stopped working and we even don't create manifest file for cluster autoscaler. I used the following command to start the cluster:\nIt's possible it's related to", "commid": "kubernetes_issue_26346", "tokennum": 40}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3ad5523a22e3455d08d1ac23d84b6067e349c6f2f6d45bade9d3a457d02dd2d1", "query": "// newAgnhostPod returns a pod that uses the agnhost image. The image's binary supports various subcommands // that behave the same, no matter the underlying OS. func newAgnhostPod(name string, args ...string) *v1.Pod { <ins> zero := int64(0) </ins> return &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name: name, }, Spec: v1.PodSpec{ <ins> TerminationGracePeriodSeconds: &zero, </ins> Containers: []v1.Container{ { Name:  \"agnhost\",", "positive_passages": [{"docid": "doc-en-kubernetes-7bfb1f284722c2f05aa84834ae56662d5ec19fb895a91cc774b04328b8cdc59d", "text": "Which jobs are flaking: ci-kubernetes-e2e-gce-scale-correctness Which test(s) are flaking: [sig-network] Services should be able to preserve UDP traffic when server pod cycles for a NodePort service Testgrid link: https://k8s- Reason for failure: /sig network /assign\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nCRI-O CI is also hitting this failure. We have been unable to reproduce locally. our CI runs on aws\nhmm, I only see 1 failure out of 4 and seems that the connectivity didn't work at all\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\n/assign\nGitHub didn't allow me to assign the following users: JacobTanenbaum. 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\n/cc Saw the test flaking recently: Wondering if this is just a timeout issue.", "commid": "kubernetes_issue_91236", "tokennum": 320}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3ad5523a22e3455d08d1ac23d84b6067e349c6f2f6d45bade9d3a457d02dd2d1", "query": "// newAgnhostPod returns a pod that uses the agnhost image. The image's binary supports various subcommands // that behave the same, no matter the underlying OS. func newAgnhostPod(name string, args ...string) *v1.Pod { <ins> zero := int64(0) </ins> return &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name: name, }, Spec: v1.PodSpec{ <ins> TerminationGracePeriodSeconds: &zero, </ins> Containers: []v1.Container{ { Name:  \"agnhost\",", "positive_passages": [{"docid": "doc-en-kubernetes-7ebfc2af23ebf8477a19d5b139a7e0f62f200d8158a5532a965c9eb49bf73a96", "text": "Maybe we can increase the timeout and/or switch to a TCP based test:\nthe test should use UDP, and UDP is unreliable by definition ... however is curious that most of the failures happen because it is not able to communicate with the first pod I think that is something that should be investigated, I've analyzed some occurences and it works fine for the second pod, however, the UDP losses should be totally random\nHi everyone, yeah so.. collecting some data on this... using a two node kind cluster, locally, with the antrea plugin, it passes using a 4 node AWS cluster with the antrea CNI plugin, it failed using a two node kidn cluster locally with calico, it passes So I guess the best reproducer is to run these tests, for now, in the cloud.... Now that I have a reproducer for this maybe can live debug it some time next wk with one of yall :)\nbear in mind that this test is connecting to a nodePort in the node IP, the test is functionally correct, it may be flaky due to the unreliable UDP nature or due to the pod scheduling, but if is failing constantly it has to be environmental.\nSecond failure after two weeks of green 5k runs:\nyep, :/ https://k8s-|UDP /assign\n/reopen I'm afraid this is going to be challenging :smile: The difference now is that we are testing NodePort and ClusterIP If both fail, we can blame the test for sure, If only NodePort fails, we need to check the job, if GCE or KIND If only ClusterIP fails, ... :thinking:\nReopened this issue. <detailsIn response to : /reopen I'm afraid this is going to be challenging :smile: 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\nWe're hitting this really frequently in 5k-node tests. So I started looking a little bit into that.", "commid": "kubernetes_issue_91236", "tokennum": 445}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3ad5523a22e3455d08d1ac23d84b6067e349c6f2f6d45bade9d3a457d02dd2d1", "query": "// newAgnhostPod returns a pod that uses the agnhost image. The image's binary supports various subcommands // that behave the same, no matter the underlying OS. func newAgnhostPod(name string, args ...string) *v1.Pod { <ins> zero := int64(0) </ins> return &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name: name, }, Spec: v1.PodSpec{ <ins> TerminationGracePeriodSeconds: &zero, </ins> Containers: []v1.Container{ { Name:  \"agnhost\",", "positive_passages": [{"docid": "doc-en-kubernetes-5846160d0947d31469e9f6af93fd879e379d05716d3adf8932316babb4b3ae6c", "text": "I don't have full understanding of what exactly is happening, but I already see a couple things that may be causing issues: when creating the first pod, you wait for corresponding endpoint for that being created; but that doesn't mean that kube-proxy was actually programmed correctly at that time (in general it isn't); given iptables programming is rate-limitted, it may easily happen that actually programming happens 10s+ later That explains some delays, but it doesn't explain e.g. this run: where iptables were programmed at but the test didn't respond until If someone more familiar with networking stuff could look into it, it would be great. - can you help triaging ^^ for deletions it's even worse, because you don't even wait for endpoints to be there (i.e. Endpoints can still contain the old pod when the test start pinging to look for the second one) So I claim that timeouts are visibly to low in this test, but I suspect it's not everything. I will send out the first PR that tries to improve it in couple minutes.\nthanks wojtek, have been slammed but Ill try to collect more data on it this wknd as well.\nIt seems that my PR didn't really help much. We should dig deeper, but I would need someone with more networking expertise to look a bit into\nActually - it seems only failures from one group are on non . So maybe that's actually related. The non-kind related ones look like:\nOK - for this one, I actually know what is happening - I will send out a PR with a fix for this too.\nfor the KIND jobs already increased the resource requests on some of the jobs, there are issues on KIND jobs with kube-proxy not able to take the iptables lock and not being able to create the iptables rules for the services until the next resync\nis to fix the flakes I mentioned above; all other flakes seem to be kind-oriented to me (which I'm not super familiar with).\nWe did not adjust the CPU on all jobs yet, pending how to manage that on prow ... I do see just a few other flakes at the bottom of the triage dashboard that look like timeouts instead.\nActually - almost all failures are effectively timeout. The top one that is is actually also a timeout. Didn't look into kind failures, but this may easily be related to iptables issues.", "commid": "kubernetes_issue_91236", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3ad5523a22e3455d08d1ac23d84b6067e349c6f2f6d45bade9d3a457d02dd2d1", "query": "// newAgnhostPod returns a pod that uses the agnhost image. The image's binary supports various subcommands // that behave the same, no matter the underlying OS. func newAgnhostPod(name string, args ...string) *v1.Pod { <ins> zero := int64(0) </ins> return &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name: name, }, Spec: v1.PodSpec{ <ins> TerminationGracePeriodSeconds: &zero, </ins> Containers: []v1.Container{ { Name:  \"agnhost\",", "positive_passages": [{"docid": "doc-en-kubernetes-0543f3a3993360bbed011d4060e35a21f3f79414d82ea25f247261ac2b705804", "text": "After my second deflaking PR, we seem to be in the stage where: tests are failing on dozens of different things (probably iptables-issues related) tests are failing only on NodePort tests on \"Failed to connecto to backend 1\" which it would be great if someone else could look into (kube-proxy seemed to be programmed correctly based on logs)\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\nThis has failed again - Linking to specific part of log where timeout occurred .... we see this\nSo reviewing the above logs note how in STEP: checking client pod connected to the backend 1 on Node IP 10.138.0.5 28 attempts are made all in the 25th second of the 2 minute at 11am Should this Step back off and wait a few seconds in between tries? So looking at this code we see the following\nFrom reading ... the intention expressed in the test code looks good to me. It is not clear to me why there is a mismatch between the 28 tries in the POD Client Logs and the expressed intention running the logContainsFn(podBackend1) every 5 seconds still digging ....\nwe are trying to catch one failure in this PR that has additional debugging, it dumps the conntrack table of the nodes on a failure\nfor those following the issue, we've extra debugging to the test so it dumps the whole conntrack table once it finish. We should look that there is NO stale entries, connections from the pod client to the deleted endpoint) and there is conntrack entries to the new endpoint from the pod client.\n- we have runs with the conntrack dump now, e.g. this one: would you be able to take a look into it?\nnot yet :/ , but I think tomorrow can have some time\ncc\nFor anyone reproducing this issue btw, you need a multinode k8s cluster (it isnt doable on kind i guess bc less likeliehood of network failures when running local) -\nCurious about two potential hypotheses to fix this, have we looked into either of these? 1) can we confirm that is turned on/off? 2) is it possible that scaling the number of coredns replicas could help ?", "commid": "kubernetes_issue_91236", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3ad5523a22e3455d08d1ac23d84b6067e349c6f2f6d45bade9d3a457d02dd2d1", "query": "// newAgnhostPod returns a pod that uses the agnhost image. The image's binary supports various subcommands // that behave the same, no matter the underlying OS. func newAgnhostPod(name string, args ...string) *v1.Pod { <ins> zero := int64(0) </ins> return &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name: name, }, Spec: v1.PodSpec{ <ins> TerminationGracePeriodSeconds: &zero, </ins> Containers: []v1.Container{ { Name:  \"agnhost\",", "positive_passages": [{"docid": "doc-en-kubernetes-66f25b05b1c90d93aad713cb7c943585d55afc690fe7a4f7e9fa0b7a5a5f23b1", "text": "3) Would simulating this in kind by overloading coredns be a possibility as a way to make a more reproducible bug model?\nregarding 1) kubeadm does not ship nodeLocalDNSCache I don't think GCE kube-up does by default either\nok, so now im curious about (2) - i.e. what if we just bumped coredns replica count?\ninteresting, :thinking: why do you think is a DNS thing? the netcat command that polls the services use the IP addresses not the hostname. I think that it has to be related to some iptables/conntrack race or similar,at least in KIND jobs we know that we have an iptables problem that affects network tests, that has to be fixed before this because it affect this test You can instrument the test locally with this and dump the state of iptables and conntrack on failure if you are able to reproduce it\ni figured DNS bc i believe its known that conntrack and DNS at scale can get very messy, right ?\none other curious thing about this test is that we only create 2 pods in the recycling event for the svc. that likely means that any real error is hidden by chance..... If we created a 3rd pod, then we might potentially double the failure rate thus making the flakyness go away and expose the real underlying issue .\nThere's an invocation of dumpConntrack(cs) here [sig-network] Conntrack should be able to preserve UDP traffic when server pod cycles for a ClusterIP service\nis updating the logging to run in an infinite loop ..\nThis is improving in KIND with the new changes we rolled out yesterday, let's see how it evolves this week\n- which changes ? Are you saying this is no longer reproducible on Kind?\nthere was a lot of noise in the CI signal, especially in KIND jobs due to the CNI portmap bug we finally solved yesterday now we should have a better signal and we can go to the bottom because probably the failure will be \"legit\" and not a consequence, so this comment should apply\nHi ! I ran this a few times on kind and it passed, but I see , so I'm going to try the loop approach you suggested. Here's what I'm using to test:\nquick note, <- potential motivation to possibly have runnable on some subset of tests in upstream eventually, i.e.", "commid": "kubernetes_issue_91236", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3ad5523a22e3455d08d1ac23d84b6067e349c6f2f6d45bade9d3a457d02dd2d1", "query": "// newAgnhostPod returns a pod that uses the agnhost image. The image's binary supports various subcommands // that behave the same, no matter the underlying OS. func newAgnhostPod(name string, args ...string) *v1.Pod { <ins> zero := int64(0) </ins> return &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name: name, }, Spec: v1.PodSpec{ <ins> TerminationGracePeriodSeconds: &zero, </ins> Containers: []v1.Container{ { Name:  \"agnhost\",", "positive_passages": [{"docid": "doc-en-kubernetes-deebb69aabcaf9005201c68e52f1f862e88c30f5231beaa0034b1d576abe9a4a", "text": "so we can do things like to reproduce this sort of thing. matt did you get around to the 'try-till-it-fails' scenario?\nI haven't been able to get it to fail on kind yet, -- 100 cycles and 0 failures on a three-node kind cluster! I'm letting the loop run for a few hours, will check back in when I have that data. Is it worth running this test on a non-kind environment?\nI ran for several hours on my mac, through 1144 iterations no error yet. My conclusion: this test isn't flaky on KinD. Possible next step: run a large number of iterations of the same test on a GKE cluster.\nFlakes on kind are also happening:\nnot many since the portmap fix on the 14th though ( / ) <img width=\"1111\" alt=\"Screen Shot 2020-07-23 at 11 45 46 PM\" src=\"https://user-\"\nAgree - it's much better than it was before.\nI was analyzing this failure, the problem is that kind jobs does not have verbosity enough in kube-proxy We can see that the packet was never replied, this is the NAT entry from client -nodePort in the node with the client This is the same flow, but in the node with the server and the pod-server-1 seems to be healthy we need more logs :eyeglasses:\nWe have an open ticket to bump those in CI, it's just been lost in the noise. We should still do that. Antonio Ojea <:\nIf you are busy just assign it to me, I'll need this verbosity soon :)\nIt's in the kind repo, shouldn't be too hard to find, we have ~60 open atm. Antonio Ojea <:\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\nI made another attempt to reproduce these failures locally on KinD, but still no success. Here's what I did: create a KinD cluster run two instances of sonobuoy at the same time This took ~4 hours to run; all the kube tests passed and sonobuoy reported all successes.", "commid": "kubernetes_issue_91236", "tokennum": 494}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3ad5523a22e3455d08d1ac23d84b6067e349c6f2f6d45bade9d3a457d02dd2d1", "query": "// newAgnhostPod returns a pod that uses the agnhost image. The image's binary supports various subcommands // that behave the same, no matter the underlying OS. func newAgnhostPod(name string, args ...string) *v1.Pod { <ins> zero := int64(0) </ins> return &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name: name, }, Spec: v1.PodSpec{ <ins> TerminationGracePeriodSeconds: &zero, </ins> Containers: []v1.Container{ { Name:  \"agnhost\",", "positive_passages": [{"docid": "doc-en-kubernetes-738ad9cb1373dead6b2f556ac241cd0c8a6cc7a0f09950111e765d9eb1dab68b", "text": "Would love to help out in reproing this, I'm at a loss for good next step so any suggestions welcome!\nthat's the problem with these flakes, they are not easy to repro, and with this low rate of failures it may be caused for combination of running tests, environmental problems (cpu, memory, ...) , ... I always start for checking the current failures and try to find patterns\nLet's take a look to one occurrence The tests fails because can't connect to the first pod If we check the code of the tests, we can see that it always uses the port as source port, we can use that to identify the nodePort assigned interesting thing here, we are source nating the pod ip, and we don't see any other conntrack entry The test verifies it has endpoints however, kube-proxy is using endpointlsices since this version but it has no entries so the iptables rules to forward the traffic are not there Seems we have to adapt this function in the e2e framework to use endpointslices cc: EDIT seems that this function is being used by all the network tests that can cause flakes if the endpoint is updated before the endpointslice (we switched recently kube-proxy to use the later)\nGreat catch. Ideally this function should validate if both Endpoint and appropriate EndpointSlice objects(s) exist.\nActually - let me take it and send a PR for it.\nis out for review\nInteresting failures here It fails to connect to the first pod\nHmm - I took a quick look at kube-proxy logs and these look fine to me....\nI clicked too fast, sorry ... I was looking at the wrong service and I though I've found something\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry.", "commid": "kubernetes_issue_91236", "tokennum": 416}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3ad5523a22e3455d08d1ac23d84b6067e349c6f2f6d45bade9d3a457d02dd2d1", "query": "// newAgnhostPod returns a pod that uses the agnhost image. The image's binary supports various subcommands // that behave the same, no matter the underlying OS. func newAgnhostPod(name string, args ...string) *v1.Pod { <ins> zero := int64(0) </ins> return &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name: name, }, Spec: v1.PodSpec{ <ins> TerminationGracePeriodSeconds: &zero, </ins> Containers: []v1.Container{ { Name:  \"agnhost\",", "positive_passages": [{"docid": "doc-en-kubernetes-7b1ee5acca525c6b88a5b6825056ab7c4df586768503c885715c9a87d944744a", "text": "\u200d\njust saw it as well\ncan you please add links to the job with the failures, I just merged new code to improve the logging 2 days ago\nok, here there is a new occurrence and with the new debug logs is easier to follow has unreplied conntrack entries: looking at the other side The iptables rules are there but no conntrack entries related to 10.244.2.32\nIn I revert PR with debug info as I think that it likely caused significant memory growth in scalability tests, but we have one run that has finished without being killed by OOMKiller (I increased memory limit for that jobs as a mitigation). Maybe logs from this run will be useful for debugging:\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\nTwo more flakes today:\nIt seems that the packet never gets DNATed in the receiving host, so it does not reach the pod in the node. There is the same test that is using ClusterIP instead of NodePort that is more reliable. This is being a tough one\n/triage accepted\nYesterday's flake - I don't think I'm seeing the log messages from the latest log PR you made ? Or are the prow logs not logging at a high-enough level?\nLogs are there, please bear with me: The error on the test is: click on the job failure and you'll see a larger output where you can see the server pod name and get the node where the pod is running: and the client-pod name and its node: and the flow we are looking for: with the node-name we can get the kube-proxy logs there, clicking in artifacts: and you can see the \"new\" conntrack log entries : and in the client: wow, there is a kernel bug there , can it be related? :thinking:\nwohoo - some progress :) I'm not an expert here, but I think it can be? Adding here - they may be able to confirm/reject the hypothesis.\nThis kernel panic may be a coincidence, maybe this is the reason\nAdding some recent failures:\nSpotted another flake today:\nAnother flake in the 5k job:", "commid": "kubernetes_issue_91236", "tokennum": 495}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3b12bf71ae16e57a7c1429e8ec2d468ed17825171f76ecba39072154c3b92ceb", "query": "// NewDelayingQueueWithCustomClock constructs a new named workqueue // with ability to inject real or fake clock for testing purposes func NewDelayingQueueWithCustomClock(clock clock.Clock, name string) DelayingInterface { <ins> return newDelayingQueue(clock, NewNamed(name), name) } func newDelayingQueue(clock clock.Clock, q Interface, name string) *delayingType { </ins> ret := &delayingType{ <del> Interface:       NewNamed(name), </del> <ins> Interface:       q, </ins> clock:           clock, heartbeat:       clock.NewTicker(maxWait), stopCh:          make(chan struct{}),", "positive_passages": [{"docid": "doc-en-kubernetes-4f192dd202c02f7ffbf9fec50f8a461695dfaeb54dc2c0d9c429922f335d948f", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Current constructors: Could we export a new constructor like to inject custom queue. Why is this needed: In my project, i want to create a with a custom queue based on workqueue.Interface but have no way to do that.\n/sig api-machinery\nthanks for the issue! We've reviewed it in the bug triage, and the consensus was that to ask you to send a PR with this and discuss it there. Would you be able to do it? thanks!\nYes, i will do that.", "commid": "kubernetes_issue_89247", "tokennum": 132}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3b6e760c6f509a43eadf028db07d7cdc800d79358f98e1a3685d4a571ea0c1e1", "query": "t.Errorf(\"Service must be namespace scoped\") } oldService := makeValidService() <del> newService := makeValidService() </del> <ins> oldService.Spec.Type = api.ServiceTypeLoadBalancer </ins> oldService.ResourceVersion = \"4\" <del> newService.ResourceVersion = \"4\" </del> <ins> oldService.Spec.SessionAffinity = \"None\" newService := oldService.DeepCopy() </ins> newService.Spec.SessionAffinity = \"ClientIP\" newService.Status = api.ServiceStatus{ LoadBalancer: api.LoadBalancerStatus{", "positive_passages": [{"docid": "doc-en-kubernetes-e021a9a686a92d83ba285392c70089f3a0813200ee010fb06825ed96dc15cfdb", "text": "xref I think this may be one of the few cases where we can actually change the behavior in a \"breaking\" way. User creates service with , is empty Controller or user updates the status subresource, sets (not wiped or validated, should be) User updates in any way, is wiped It's clear that the is not meant to be set when is not \"LoadBalancer\". The question is: 1) Fail validation? 2) Silently discard the value? 3) Warn and then discard the value? 4) Just warn and leave it. Because we allowed it in the past, but it is so volatile, I lean towards 3. and - the people most familair with this type. Edit: PrepareForUpdate() runs before warnings. So: (1) is easy (2) is easy (4) is slightly less easy than (2) (3) is slightly less easy than (4)\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nOMG change it to clusterIP as expected Status is wiped update status as ClusterIP ... and if I edit the service back to loadbalancer it keeps the status??\n/kind bug\n/retitle Service can be set when !=\nWe talked about this one at the SIG Network meeting today. suggested we use the feature gate for deprecation option to phase the current (problematic) functionality out.\n/triage accept\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /triage accept 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", "commid": "kubernetes_issue_119700", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3b8c4a7104affd77fac16ec273320359966b6dffecfe83488f6fec70b718bb4e", "query": "// +listType=map // +listMapKey=name // +optional <del> Variables []Variable `json:\"variables\" patchStrategy:\"merge\" patchMergeKey:\"name\" protobuf:\"bytes,7,rep,name=variables\"` </del> <ins> Variables []Variable `json:\"variables,omitempty\" patchStrategy:\"merge\" patchMergeKey:\"name\" protobuf:\"bytes,7,rep,name=variables\"` </ins> } type MatchCondition v1.MatchCondition", "positive_passages": [{"docid": "doc-en-kubernetes-f7dbb3a7bd33f39ed155e3c1ad6b8c55c94743d34cf8c863dee73b5ba5ef4403", "text": "spec.variables should be marked omitempty. I'm trying to create a validating admission policy that uses in v1.27 as follows: I'm setting : to \"Strict\" in CreateOptions so that the server will reject requests with unknown fields but it complains that the don't exist in v1.27 and it does make sense because this field was introduced in v1.28: I'm using a 1.28 client.\n/sig api-machinery\n/assign\n/assign /triage accepted\nThanks for raising this! /cc", "commid": "kubernetes_issue_120491", "tokennum": 117}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3bbba44e0b7a08df3a2efb9f94d643d4ab2d46844e3625755666c88a74a83d13", "query": "}, }, { <del> name: \"StorageCapacity changed\", </del> <ins> name: \"TokenRequests invalidated\", </ins> modify: func(new *storage.CSIDriver) { <del> new.Spec.StorageCapacity = &notStorageCapacity </del> <ins> new.Spec.TokenRequests = []storage.TokenRequest{{Audience: gcp}, {Audience: gcp}} </ins> }, }, { <del> name: \"TokenRequests invalidated\", </del> <ins> name: \"invalid nil StorageCapacity\", </ins> modify: func(new *storage.CSIDriver) { <del> new.Spec.TokenRequests = []storage.TokenRequest{{Audience: gcp}, {Audience: gcp}} </del> <ins> new.Spec.StorageCapacity = nil </ins> }, }, }", "positive_passages": [{"docid": "doc-en-kubernetes-cdccab911562ccfffce851739652bcccdbeabc99e62d699c46baa58ef67f3bbe", "text": "Up to 1.21, that field is immutable. That means in practice, a CSIDriver object has to be deleted and then re-created with a different value instead. Mutation via delete/created is unnecessarily complex and as the only consumer of that field (the kube-scheduler) can handle mutation just fine (it'll always ask the informer cache for the current value), it's better to allow mutation.\n/sig storage /assign\nThis is independent of allowing other fields to become mutable, but that might also make sense.\n/triage accepted", "commid": "kubernetes_issue_100089", "tokennum": 125}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3bcdf9ff834a20ba361c89b93741870f5fd805691865531ac7497c4c2873f372", "query": "return iface.Name, nil } <del> func setUpAllInterfaces() error { interfaces, err := net.Interfaces() if err != nil { return err } for _, netIf := range interfaces { setUpInterface(netIf.Name) // ignore errors } return nil } </del> func setUpInterface(ifName string) error { glog.V(3).Infof(\"Enabling hairpin on interface %s\", ifName) ifPath := path.Join(sysfsNetPath, ifName)", "positive_passages": [{"docid": "doc-en-kubernetes-1338c1265dc2da957b27c9fcf90bf88eaa9473c2ffb7e29c3dbb2785dec4e5f0", "text": "From another issue, said: DockerManager.SyncPod() calls the network Plugin and then sets hairpin mode unilaterally. This is wrong. We should either pass the bool down to here or else we should get rid of the default no-op plugin and use the non-existence of a plugin as a flag to control this. This should be a relatively easy one for people who want to contribute but don't know where to start.\nI volunteer myself to do this. Actually I have done something about kubernetes network plugin so guess I can do this. I will start to do this when I am on the office tomorrow.\nAwesome. I'd advise starting with a sketch so we can all make sure it is a good approach, before jumping in with both feet. , TonyAdo wrote:\nok, I will start with a sketch as soon as possible.\nI thought about this for a while: if we pass the bool down to here, of course we can check this flag, if it is set, we should set veth hairpin mode, but problem is that if user set this flag, but still use a custom network plugin just like you mentioned the ovs plugin, I am afraid we will still enable hairpin mode in all interfaces on this host, since we cannot find a peer interface. Is that correct?\nYeah, I think the better fix is to use the existence of a network plugin as an indicator. It sort of makes --configure-cbr0 redundant , TonyAdo wrote:\nok, I will try to get rid of the default no-op plugin and use the non-existence of a plugin as a flag to control this.\nI decided to use the existence of a network plugin as an indicator, also I will get ride of the no-op network plugin, I am not going to add new flag to kubelet structure, if the user don't specify network plugin name, the networkPlugin within kubelet will be which just means non-existence of a plugin, and we have to check the existence in the docker manager to avoid nil pointer exception also for setting, I think if a custom network plugin exists, kubelet should not do this. How about this? Should I open a PR?\nfyi, saw a hairpin pr today that might be related. ymmv.\nwhat do you think about this?\nWhat you described sounds right to me.", "commid": "kubernetes_issue_19766", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3bcdf9ff834a20ba361c89b93741870f5fd805691865531ac7497c4c2873f372", "query": "return iface.Name, nil } <del> func setUpAllInterfaces() error { interfaces, err := net.Interfaces() if err != nil { return err } for _, netIf := range interfaces { setUpInterface(netIf.Name) // ignore errors } return nil } </del> func setUpInterface(ifName string) error { glog.V(3).Infof(\"Enabling hairpin on interface %s\", ifName) ifPath := path.Join(sysfsNetPath, ifName)", "positive_passages": [{"docid": "doc-en-kubernetes-63d22d436297e1e341b6c3c9db0f8b916cd9a8fc746e2ad0128076b35b0cb5ac", "text": "I think the only way to see if there is some detail I am missing is to try it and see if anything pops up that would make this not work. , TonyAdo wrote:\nI need to check which part is responsible of what, but what if the hairpin package was just a utility package that should be called by the plugin if it needs to set this up? As long as it is single and simple function call, doing so would avoid adding extra logic here and fix the issue. This is valid only if the aim is to have a \"linux bridge plugin\", an \"OVS plugin\", etc.\nactually kubelet will call after get called, I think to make the network plugin can call hairpin package is not that easy, of course, I agree that network plugin should setup hairpin mode if it really needs, kubelet should not set hairpin mode unilaterally. Besides, kubelet is not going to provide an \"linux bridge plugin\" or \"OVS plugin\".\nthen the validity conditions of my comment are not met, so I see any simpler way. Thanks for checking! :)\nstill what do you think about disable hairpin completely and leave this to network plugin?\nor if there is a custom network plugin, we don't setup hairpin mode, only do this in default.\nCompletely? It will break my use case (and anyone using Apache Kafka).\nOnly by default is what I understood from the previous comments, and LGTM.\nReally sorry about that, but I really want to know are you using a kubelet network plugin in your use case? If no, I think we will still setup hairpin, as in default we will do this.\nI don't use any plugin, so it is ok if hairpin is set up by default.\nok, I think this will not break your use case.\nIt's not really the network plugin that needs hairpinmode though, it's the pure-iptables-based kube-proxy code. It's possible the proxying code could change again in the future in such a way that hairpinmode wouldn't be needed any more. So it seems wrong to put that code into the plugin. makes it so that we set hairpinmode on the veth if it's attached to a bridge, but just silently do nothing if it's not.", "commid": "kubernetes_issue_19766", "tokennum": 509}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3bcdf9ff834a20ba361c89b93741870f5fd805691865531ac7497c4c2873f372", "query": "return iface.Name, nil } <del> func setUpAllInterfaces() error { interfaces, err := net.Interfaces() if err != nil { return err } for _, netIf := range interfaces { setUpInterface(netIf.Name) // ignore errors } return nil } </del> func setUpInterface(ifName string) error { glog.V(3).Infof(\"Enabling hairpin on interface %s\", ifName) ifPath := path.Join(sysfsNetPath, ifName)", "positive_passages": [{"docid": "doc-en-kubernetes-3bf0b78c82438b679aab4fecf6e8905cfec517728c795c679dfaefb3dd282eea", "text": "(Yes, we currently set hairpinmode even if you're using the userspace proxier, but AFAIK it's not needed in that case.)\nIMHO... The proxy has the responsibility of service objects, while the kubelet is responsible of pod objects, including their networking. Also, the responsibility of hairpin must be at the same place as the code that creates the network interface, otherwise you have code managing a single object (the pod interface) spread over multiple programs, which will eventually lead to complex problems and a system harder to understand even for the end-user. Thus, it doesn't seems wrong to me that the kubelet does whatever is required to make the pod work in the environment of the cluster. While its true that the hairpin requirement is only for the proxy in iptables mode, a switch to this mode can happen at any time in the life of the cluster. And when it happens, its probably because the userland proxy becomes unresponsive, which means in a situation where the administrator is in a hurry to find a solution. Currently, you just change the proxy mode and restart the proxies. There's little chance the administrator will think about hairpin or restarting the kubelet in this case, so the kubelet should be reacting to this; which means the proxy and the kubelet of a given host should be able to communicate (AFAIK, this doesn't exist now). And all this is currently only to avoid setting up hairpin on the pod's port of standard Linux bridge.\nFeel sure I'm missing something but... The CNI bridge plugin now has a flag, so kubenet can use that. Having done that, we can set false when the plugin name is non-blank.\nIs this fixed now?\nI apologise for leaving a somewhat vague answer, but I have been in that code recently. I don't think it's fixed.\n, Bryan Boreham wrote:\nThanks for the PR. CNI Bridge plugin is expecting . Not . Hence the bridge plugin did not recognize it.\nEDIT 2016-12-09: The chain below was broken by , so the issue can be closed again (remain closed) I suggest this should be re-opened. The chain of calls is: sets to , e.g. when using CNI calls something goes wrong and it sets the mode on everything. An example of \"something goes wrong\":", "commid": "kubernetes_issue_19766", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3c01eb06751621e0f9aae9af42a9f113e38258515fea56412a95357537722637", "query": "} } <del> // RecommendedConfigOverrideFlags is a convenience method to return recommended flag names prefixed with a string of your choosing func RecommendedConfigOverrideFlags(prefix string) ConfigOverrideFlags { return ConfigOverrideFlags{ AuthOverrideFlags:    RecommendedAuthOverrideFlags(prefix), ClusterOverrideFlags: RecommendedClusterOverrideFlags(prefix), ContextOverrideFlags: RecommendedContextOverrideFlags(prefix), CurrentContext: FlagInfo{prefix + FlagContext, \"\", \"\", \"The name of the kubeconfig context to use\"}, Timeout:        FlagInfo{prefix + FlagTimeout, \"\", \"0\", \"The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests.\"}, } } </del> // RecommendedContextOverrideFlags is a convenience method to return recommended flag names prefixed with a string of your choosing func RecommendedContextOverrideFlags(prefix string) ContextOverrideFlags { return ContextOverrideFlags{", "positive_passages": [{"docid": "doc-en-kubernetes-4e19a56e8ccacbab4546f622baecdb0b8ef30250430c55f8bcdc4de99b100cd2", "text": "Found in openshift, but I'm pretty sure the codepaths are the same. That means the token is getting ignored and in-cluster config is being used in preference to flags.\nIs a similar issue?\nYep, kind of regression.\nSigh.\nYes, most likely the same cause.\nI'm on it.\nUnit test :)\nProbably will want to cherrypick this into 1.5.\nWIP in", "commid": "kubernetes_issue_38834", "tokennum": 89}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3c750decd1508e9c2b09c808bd1e2be32aaab25384b8a3029fad20fcdea5b3e9", "query": "\"//vendor/golang.org/x/oauth2/google:go_default_library\", \"//vendor/google.golang.org/api/compute/v1:go_default_library\", \"//vendor/google.golang.org/api/dns/v1:go_default_library\", <ins> \"//vendor/google.golang.org/api/googleapi:go_default_library\", </ins> \"//vendor/gopkg.in/gcfg.v1:go_default_library\", ], )", "positive_passages": [{"docid": "doc-en-kubernetes-2b4d325d4814fe81f2a99615b844cff823940de918e3b360e7f108b94b4fe81b", "text": "/kind bug What happened: walteraa [6:55 AM] Hi, The controller manager of the federation using Google cloud DNS is crashing, the log showed is that: the hyperkube command is that: I have created this in the Google DNS Someone knows why the DNS zone query is getting the 404 error?? :disappointed: What you expected to happen: It should have created the missing domain. How to reproduce it (as minimally and precisely as possible): As per above. Anything else we need to know?: Environment: Kubernetes version (use ): 1.7.4 Cloud provider or hardware configuration**: OpenStack (irrelevant) OS (e.g. from /etc/os-release): irrelevant Kernel (e.g. ): irrelevant Install tools: irrelevant Others: irrelevant\nThe bug is related to this: The above code assumes that the provider code returns no error but an empty list if the domain does not exist, but instead the provider returns a 404. Need to fix the provider and/or the above code.\n/sig federation\nI am unlikely to have time to work on this soon, so if anyone else wants to, go right ahead.\n/assign\nAn additional information: I have created a which is based on the credential JSON file created through instruction. After that, I have configured the Federation controller manager to mount this secret as a volume in the container and set the environment variable to the JSON file inside this volume. Before doing that, I was getting an authentication error so the google DNS provider couldn't be instantiated, and after doing the instructions that I mentioned before, this authentication error was solved but now I'm getting 404 error when Google DNS provider tries access the specified managed zone. The file that I have generated follow this structure:", "commid": "kubernetes_issue_51139", "tokennum": 376}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d117c6d496fac083391cb647f0b228758dbef37d83526c8d013cf8dd88a84dd", "query": "return ret } <del> // continuousEcho() uses the same connection for multiple requests, made to run as a goroutine so that // manipulations can be made to the service and backend pods while a connection is ongoing // it starts by sending a series of packets to establish conntrack entries and waits for a signal to keep // sending packts. It returns an error if the number of failed attempts is >= 5 func continuousEcho(host string, port int, timeout time.Duration, maxAttempts int, signal chan struct{}, errorChannel chan error) { defer ginkgo.GinkgoRecover() const threshold = 10 // Sanity check inputs, because it has happened.  These are the only things // that should hard fail the test - they are basically ASSERT()s. if host == \"\" { errorChannel <- fmt.Errorf(\"Got empty host for continuous echo (%s)\", host) return } if port == 0 { errorChannel <- fmt.Errorf(\"Got port ==0 for continuous echo (%d)\", port) return } hostPort := net.JoinHostPort(host, strconv.Itoa(port)) url := fmt.Sprintf(\"udp://%s\", hostPort) ret := UDPPokeResult{} con, err := net.Dial(\"udp\", hostPort) if err != nil { ret.Status = UDPError ret.Error = err errorChannel <- fmt.Errorf(\"Connection to %q failed: %v\", url, err) return } numErrors := 0 bufsize := len(strconv.Itoa(maxAttempts)) + 1 var buf = make([]byte, bufsize) for i := 0; i < maxAttempts; i++ { if i == threshold { framework.Logf(\"Continuous echo waiting for signal to continue\") <-signal if numErrors == threshold { errorChannel <- fmt.Errorf(\"continuous echo was not able to communicate with initial server pod\") return } } time.Sleep(1 * time.Second) err = con.SetDeadline(time.Now().Add(timeout)) if err != nil { ret.Status = UDPError ret.Error = err framework.Logf(\"Continuous echo (%q): %v\", url, err) numErrors++ continue } myRequest := fmt.Sprintf(\"echo %d\", i) _, err = con.Write([]byte(fmt.Sprintf(\"%sn\", myRequest))) if err != nil { ret.Error = err neterr, ok := err.(net.Error) if ok && neterr.Timeout() { ret.Status = UDPTimeout } else if strings.Contains(err.Error(), \"connection refused\") { ret.Status = UDPRefused } else { ret.Status = UDPError } numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } err = con.SetDeadline(time.Now().Add(timeout)) if err != nil { ret.Status = UDPError ret.Error = err numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } n, err := con.Read(buf) if err != nil { ret.Error = err neterr, ok := err.(net.Error) if ok && neterr.Timeout() { ret.Status = UDPTimeout } else if strings.Contains(err.Error(), \"connection refused\") { ret.Status = UDPRefused } else { ret.Status = UDPError } numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } ret.Response = buf[0:n] if string(ret.Response) != fmt.Sprintf(\"%d\", i) { ret.Status = UDPBadResponse ret.Error = fmt.Errorf(\"response does not match expected string: %q\", string(ret.Response)) framework.Logf(\"Continuous echo (%q): %v\", url, ret.Error) numErrors++ continue } ret.Status = UDPSuccess framework.Logf(\"Continuous echo(%q): success\", url) } err = nil if numErrors >= threshold { err = fmt.Errorf(\"Too many Errors in continuous echo\") } errorChannel <- err } </del> // testReachableUDP tests that the given host serves UDP on the given port. func testReachableUDP(host string, port int, timeout time.Duration) { pollfn := func() (bool, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-7bfb1f284722c2f05aa84834ae56662d5ec19fb895a91cc774b04328b8cdc59d", "text": "Which jobs are flaking: ci-kubernetes-e2e-gce-scale-correctness Which test(s) are flaking: [sig-network] Services should be able to preserve UDP traffic when server pod cycles for a NodePort service Testgrid link: https://k8s- Reason for failure: /sig network /assign\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nCRI-O CI is also hitting this failure. We have been unable to reproduce locally. our CI runs on aws\nhmm, I only see 1 failure out of 4 and seems that the connectivity didn't work at all\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\n/assign\nGitHub didn't allow me to assign the following users: JacobTanenbaum. 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\n/cc Saw the test flaking recently: Wondering if this is just a timeout issue.", "commid": "kubernetes_issue_91236", "tokennum": 320}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d117c6d496fac083391cb647f0b228758dbef37d83526c8d013cf8dd88a84dd", "query": "return ret } <del> // continuousEcho() uses the same connection for multiple requests, made to run as a goroutine so that // manipulations can be made to the service and backend pods while a connection is ongoing // it starts by sending a series of packets to establish conntrack entries and waits for a signal to keep // sending packts. It returns an error if the number of failed attempts is >= 5 func continuousEcho(host string, port int, timeout time.Duration, maxAttempts int, signal chan struct{}, errorChannel chan error) { defer ginkgo.GinkgoRecover() const threshold = 10 // Sanity check inputs, because it has happened.  These are the only things // that should hard fail the test - they are basically ASSERT()s. if host == \"\" { errorChannel <- fmt.Errorf(\"Got empty host for continuous echo (%s)\", host) return } if port == 0 { errorChannel <- fmt.Errorf(\"Got port ==0 for continuous echo (%d)\", port) return } hostPort := net.JoinHostPort(host, strconv.Itoa(port)) url := fmt.Sprintf(\"udp://%s\", hostPort) ret := UDPPokeResult{} con, err := net.Dial(\"udp\", hostPort) if err != nil { ret.Status = UDPError ret.Error = err errorChannel <- fmt.Errorf(\"Connection to %q failed: %v\", url, err) return } numErrors := 0 bufsize := len(strconv.Itoa(maxAttempts)) + 1 var buf = make([]byte, bufsize) for i := 0; i < maxAttempts; i++ { if i == threshold { framework.Logf(\"Continuous echo waiting for signal to continue\") <-signal if numErrors == threshold { errorChannel <- fmt.Errorf(\"continuous echo was not able to communicate with initial server pod\") return } } time.Sleep(1 * time.Second) err = con.SetDeadline(time.Now().Add(timeout)) if err != nil { ret.Status = UDPError ret.Error = err framework.Logf(\"Continuous echo (%q): %v\", url, err) numErrors++ continue } myRequest := fmt.Sprintf(\"echo %d\", i) _, err = con.Write([]byte(fmt.Sprintf(\"%sn\", myRequest))) if err != nil { ret.Error = err neterr, ok := err.(net.Error) if ok && neterr.Timeout() { ret.Status = UDPTimeout } else if strings.Contains(err.Error(), \"connection refused\") { ret.Status = UDPRefused } else { ret.Status = UDPError } numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } err = con.SetDeadline(time.Now().Add(timeout)) if err != nil { ret.Status = UDPError ret.Error = err numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } n, err := con.Read(buf) if err != nil { ret.Error = err neterr, ok := err.(net.Error) if ok && neterr.Timeout() { ret.Status = UDPTimeout } else if strings.Contains(err.Error(), \"connection refused\") { ret.Status = UDPRefused } else { ret.Status = UDPError } numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } ret.Response = buf[0:n] if string(ret.Response) != fmt.Sprintf(\"%d\", i) { ret.Status = UDPBadResponse ret.Error = fmt.Errorf(\"response does not match expected string: %q\", string(ret.Response)) framework.Logf(\"Continuous echo (%q): %v\", url, ret.Error) numErrors++ continue } ret.Status = UDPSuccess framework.Logf(\"Continuous echo(%q): success\", url) } err = nil if numErrors >= threshold { err = fmt.Errorf(\"Too many Errors in continuous echo\") } errorChannel <- err } </del> // testReachableUDP tests that the given host serves UDP on the given port. func testReachableUDP(host string, port int, timeout time.Duration) { pollfn := func() (bool, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-7ebfc2af23ebf8477a19d5b139a7e0f62f200d8158a5532a965c9eb49bf73a96", "text": "Maybe we can increase the timeout and/or switch to a TCP based test:\nthe test should use UDP, and UDP is unreliable by definition ... however is curious that most of the failures happen because it is not able to communicate with the first pod I think that is something that should be investigated, I've analyzed some occurences and it works fine for the second pod, however, the UDP losses should be totally random\nHi everyone, yeah so.. collecting some data on this... using a two node kind cluster, locally, with the antrea plugin, it passes using a 4 node AWS cluster with the antrea CNI plugin, it failed using a two node kidn cluster locally with calico, it passes So I guess the best reproducer is to run these tests, for now, in the cloud.... Now that I have a reproducer for this maybe can live debug it some time next wk with one of yall :)\nbear in mind that this test is connecting to a nodePort in the node IP, the test is functionally correct, it may be flaky due to the unreliable UDP nature or due to the pod scheduling, but if is failing constantly it has to be environmental.\nSecond failure after two weeks of green 5k runs:\nyep, :/ https://k8s-|UDP /assign\n/reopen I'm afraid this is going to be challenging :smile: The difference now is that we are testing NodePort and ClusterIP If both fail, we can blame the test for sure, If only NodePort fails, we need to check the job, if GCE or KIND If only ClusterIP fails, ... :thinking:\nReopened this issue. <detailsIn response to : /reopen I'm afraid this is going to be challenging :smile: 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\nWe're hitting this really frequently in 5k-node tests. So I started looking a little bit into that.", "commid": "kubernetes_issue_91236", "tokennum": 445}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d117c6d496fac083391cb647f0b228758dbef37d83526c8d013cf8dd88a84dd", "query": "return ret } <del> // continuousEcho() uses the same connection for multiple requests, made to run as a goroutine so that // manipulations can be made to the service and backend pods while a connection is ongoing // it starts by sending a series of packets to establish conntrack entries and waits for a signal to keep // sending packts. It returns an error if the number of failed attempts is >= 5 func continuousEcho(host string, port int, timeout time.Duration, maxAttempts int, signal chan struct{}, errorChannel chan error) { defer ginkgo.GinkgoRecover() const threshold = 10 // Sanity check inputs, because it has happened.  These are the only things // that should hard fail the test - they are basically ASSERT()s. if host == \"\" { errorChannel <- fmt.Errorf(\"Got empty host for continuous echo (%s)\", host) return } if port == 0 { errorChannel <- fmt.Errorf(\"Got port ==0 for continuous echo (%d)\", port) return } hostPort := net.JoinHostPort(host, strconv.Itoa(port)) url := fmt.Sprintf(\"udp://%s\", hostPort) ret := UDPPokeResult{} con, err := net.Dial(\"udp\", hostPort) if err != nil { ret.Status = UDPError ret.Error = err errorChannel <- fmt.Errorf(\"Connection to %q failed: %v\", url, err) return } numErrors := 0 bufsize := len(strconv.Itoa(maxAttempts)) + 1 var buf = make([]byte, bufsize) for i := 0; i < maxAttempts; i++ { if i == threshold { framework.Logf(\"Continuous echo waiting for signal to continue\") <-signal if numErrors == threshold { errorChannel <- fmt.Errorf(\"continuous echo was not able to communicate with initial server pod\") return } } time.Sleep(1 * time.Second) err = con.SetDeadline(time.Now().Add(timeout)) if err != nil { ret.Status = UDPError ret.Error = err framework.Logf(\"Continuous echo (%q): %v\", url, err) numErrors++ continue } myRequest := fmt.Sprintf(\"echo %d\", i) _, err = con.Write([]byte(fmt.Sprintf(\"%sn\", myRequest))) if err != nil { ret.Error = err neterr, ok := err.(net.Error) if ok && neterr.Timeout() { ret.Status = UDPTimeout } else if strings.Contains(err.Error(), \"connection refused\") { ret.Status = UDPRefused } else { ret.Status = UDPError } numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } err = con.SetDeadline(time.Now().Add(timeout)) if err != nil { ret.Status = UDPError ret.Error = err numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } n, err := con.Read(buf) if err != nil { ret.Error = err neterr, ok := err.(net.Error) if ok && neterr.Timeout() { ret.Status = UDPTimeout } else if strings.Contains(err.Error(), \"connection refused\") { ret.Status = UDPRefused } else { ret.Status = UDPError } numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } ret.Response = buf[0:n] if string(ret.Response) != fmt.Sprintf(\"%d\", i) { ret.Status = UDPBadResponse ret.Error = fmt.Errorf(\"response does not match expected string: %q\", string(ret.Response)) framework.Logf(\"Continuous echo (%q): %v\", url, ret.Error) numErrors++ continue } ret.Status = UDPSuccess framework.Logf(\"Continuous echo(%q): success\", url) } err = nil if numErrors >= threshold { err = fmt.Errorf(\"Too many Errors in continuous echo\") } errorChannel <- err } </del> // testReachableUDP tests that the given host serves UDP on the given port. func testReachableUDP(host string, port int, timeout time.Duration) { pollfn := func() (bool, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-5846160d0947d31469e9f6af93fd879e379d05716d3adf8932316babb4b3ae6c", "text": "I don't have full understanding of what exactly is happening, but I already see a couple things that may be causing issues: when creating the first pod, you wait for corresponding endpoint for that being created; but that doesn't mean that kube-proxy was actually programmed correctly at that time (in general it isn't); given iptables programming is rate-limitted, it may easily happen that actually programming happens 10s+ later That explains some delays, but it doesn't explain e.g. this run: where iptables were programmed at but the test didn't respond until If someone more familiar with networking stuff could look into it, it would be great. - can you help triaging ^^ for deletions it's even worse, because you don't even wait for endpoints to be there (i.e. Endpoints can still contain the old pod when the test start pinging to look for the second one) So I claim that timeouts are visibly to low in this test, but I suspect it's not everything. I will send out the first PR that tries to improve it in couple minutes.\nthanks wojtek, have been slammed but Ill try to collect more data on it this wknd as well.\nIt seems that my PR didn't really help much. We should dig deeper, but I would need someone with more networking expertise to look a bit into\nActually - it seems only failures from one group are on non . So maybe that's actually related. The non-kind related ones look like:\nOK - for this one, I actually know what is happening - I will send out a PR with a fix for this too.\nfor the KIND jobs already increased the resource requests on some of the jobs, there are issues on KIND jobs with kube-proxy not able to take the iptables lock and not being able to create the iptables rules for the services until the next resync\nis to fix the flakes I mentioned above; all other flakes seem to be kind-oriented to me (which I'm not super familiar with).\nWe did not adjust the CPU on all jobs yet, pending how to manage that on prow ... I do see just a few other flakes at the bottom of the triage dashboard that look like timeouts instead.\nActually - almost all failures are effectively timeout. The top one that is is actually also a timeout. Didn't look into kind failures, but this may easily be related to iptables issues.", "commid": "kubernetes_issue_91236", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d117c6d496fac083391cb647f0b228758dbef37d83526c8d013cf8dd88a84dd", "query": "return ret } <del> // continuousEcho() uses the same connection for multiple requests, made to run as a goroutine so that // manipulations can be made to the service and backend pods while a connection is ongoing // it starts by sending a series of packets to establish conntrack entries and waits for a signal to keep // sending packts. It returns an error if the number of failed attempts is >= 5 func continuousEcho(host string, port int, timeout time.Duration, maxAttempts int, signal chan struct{}, errorChannel chan error) { defer ginkgo.GinkgoRecover() const threshold = 10 // Sanity check inputs, because it has happened.  These are the only things // that should hard fail the test - they are basically ASSERT()s. if host == \"\" { errorChannel <- fmt.Errorf(\"Got empty host for continuous echo (%s)\", host) return } if port == 0 { errorChannel <- fmt.Errorf(\"Got port ==0 for continuous echo (%d)\", port) return } hostPort := net.JoinHostPort(host, strconv.Itoa(port)) url := fmt.Sprintf(\"udp://%s\", hostPort) ret := UDPPokeResult{} con, err := net.Dial(\"udp\", hostPort) if err != nil { ret.Status = UDPError ret.Error = err errorChannel <- fmt.Errorf(\"Connection to %q failed: %v\", url, err) return } numErrors := 0 bufsize := len(strconv.Itoa(maxAttempts)) + 1 var buf = make([]byte, bufsize) for i := 0; i < maxAttempts; i++ { if i == threshold { framework.Logf(\"Continuous echo waiting for signal to continue\") <-signal if numErrors == threshold { errorChannel <- fmt.Errorf(\"continuous echo was not able to communicate with initial server pod\") return } } time.Sleep(1 * time.Second) err = con.SetDeadline(time.Now().Add(timeout)) if err != nil { ret.Status = UDPError ret.Error = err framework.Logf(\"Continuous echo (%q): %v\", url, err) numErrors++ continue } myRequest := fmt.Sprintf(\"echo %d\", i) _, err = con.Write([]byte(fmt.Sprintf(\"%sn\", myRequest))) if err != nil { ret.Error = err neterr, ok := err.(net.Error) if ok && neterr.Timeout() { ret.Status = UDPTimeout } else if strings.Contains(err.Error(), \"connection refused\") { ret.Status = UDPRefused } else { ret.Status = UDPError } numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } err = con.SetDeadline(time.Now().Add(timeout)) if err != nil { ret.Status = UDPError ret.Error = err numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } n, err := con.Read(buf) if err != nil { ret.Error = err neterr, ok := err.(net.Error) if ok && neterr.Timeout() { ret.Status = UDPTimeout } else if strings.Contains(err.Error(), \"connection refused\") { ret.Status = UDPRefused } else { ret.Status = UDPError } numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } ret.Response = buf[0:n] if string(ret.Response) != fmt.Sprintf(\"%d\", i) { ret.Status = UDPBadResponse ret.Error = fmt.Errorf(\"response does not match expected string: %q\", string(ret.Response)) framework.Logf(\"Continuous echo (%q): %v\", url, ret.Error) numErrors++ continue } ret.Status = UDPSuccess framework.Logf(\"Continuous echo(%q): success\", url) } err = nil if numErrors >= threshold { err = fmt.Errorf(\"Too many Errors in continuous echo\") } errorChannel <- err } </del> // testReachableUDP tests that the given host serves UDP on the given port. func testReachableUDP(host string, port int, timeout time.Duration) { pollfn := func() (bool, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-0543f3a3993360bbed011d4060e35a21f3f79414d82ea25f247261ac2b705804", "text": "After my second deflaking PR, we seem to be in the stage where: tests are failing on dozens of different things (probably iptables-issues related) tests are failing only on NodePort tests on \"Failed to connecto to backend 1\" which it would be great if someone else could look into (kube-proxy seemed to be programmed correctly based on logs)\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\nThis has failed again - Linking to specific part of log where timeout occurred .... we see this\nSo reviewing the above logs note how in STEP: checking client pod connected to the backend 1 on Node IP 10.138.0.5 28 attempts are made all in the 25th second of the 2 minute at 11am Should this Step back off and wait a few seconds in between tries? So looking at this code we see the following\nFrom reading ... the intention expressed in the test code looks good to me. It is not clear to me why there is a mismatch between the 28 tries in the POD Client Logs and the expressed intention running the logContainsFn(podBackend1) every 5 seconds still digging ....\nwe are trying to catch one failure in this PR that has additional debugging, it dumps the conntrack table of the nodes on a failure\nfor those following the issue, we've extra debugging to the test so it dumps the whole conntrack table once it finish. We should look that there is NO stale entries, connections from the pod client to the deleted endpoint) and there is conntrack entries to the new endpoint from the pod client.\n- we have runs with the conntrack dump now, e.g. this one: would you be able to take a look into it?\nnot yet :/ , but I think tomorrow can have some time\ncc\nFor anyone reproducing this issue btw, you need a multinode k8s cluster (it isnt doable on kind i guess bc less likeliehood of network failures when running local) -\nCurious about two potential hypotheses to fix this, have we looked into either of these? 1) can we confirm that is turned on/off? 2) is it possible that scaling the number of coredns replicas could help ?", "commid": "kubernetes_issue_91236", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d117c6d496fac083391cb647f0b228758dbef37d83526c8d013cf8dd88a84dd", "query": "return ret } <del> // continuousEcho() uses the same connection for multiple requests, made to run as a goroutine so that // manipulations can be made to the service and backend pods while a connection is ongoing // it starts by sending a series of packets to establish conntrack entries and waits for a signal to keep // sending packts. It returns an error if the number of failed attempts is >= 5 func continuousEcho(host string, port int, timeout time.Duration, maxAttempts int, signal chan struct{}, errorChannel chan error) { defer ginkgo.GinkgoRecover() const threshold = 10 // Sanity check inputs, because it has happened.  These are the only things // that should hard fail the test - they are basically ASSERT()s. if host == \"\" { errorChannel <- fmt.Errorf(\"Got empty host for continuous echo (%s)\", host) return } if port == 0 { errorChannel <- fmt.Errorf(\"Got port ==0 for continuous echo (%d)\", port) return } hostPort := net.JoinHostPort(host, strconv.Itoa(port)) url := fmt.Sprintf(\"udp://%s\", hostPort) ret := UDPPokeResult{} con, err := net.Dial(\"udp\", hostPort) if err != nil { ret.Status = UDPError ret.Error = err errorChannel <- fmt.Errorf(\"Connection to %q failed: %v\", url, err) return } numErrors := 0 bufsize := len(strconv.Itoa(maxAttempts)) + 1 var buf = make([]byte, bufsize) for i := 0; i < maxAttempts; i++ { if i == threshold { framework.Logf(\"Continuous echo waiting for signal to continue\") <-signal if numErrors == threshold { errorChannel <- fmt.Errorf(\"continuous echo was not able to communicate with initial server pod\") return } } time.Sleep(1 * time.Second) err = con.SetDeadline(time.Now().Add(timeout)) if err != nil { ret.Status = UDPError ret.Error = err framework.Logf(\"Continuous echo (%q): %v\", url, err) numErrors++ continue } myRequest := fmt.Sprintf(\"echo %d\", i) _, err = con.Write([]byte(fmt.Sprintf(\"%sn\", myRequest))) if err != nil { ret.Error = err neterr, ok := err.(net.Error) if ok && neterr.Timeout() { ret.Status = UDPTimeout } else if strings.Contains(err.Error(), \"connection refused\") { ret.Status = UDPRefused } else { ret.Status = UDPError } numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } err = con.SetDeadline(time.Now().Add(timeout)) if err != nil { ret.Status = UDPError ret.Error = err numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } n, err := con.Read(buf) if err != nil { ret.Error = err neterr, ok := err.(net.Error) if ok && neterr.Timeout() { ret.Status = UDPTimeout } else if strings.Contains(err.Error(), \"connection refused\") { ret.Status = UDPRefused } else { ret.Status = UDPError } numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } ret.Response = buf[0:n] if string(ret.Response) != fmt.Sprintf(\"%d\", i) { ret.Status = UDPBadResponse ret.Error = fmt.Errorf(\"response does not match expected string: %q\", string(ret.Response)) framework.Logf(\"Continuous echo (%q): %v\", url, ret.Error) numErrors++ continue } ret.Status = UDPSuccess framework.Logf(\"Continuous echo(%q): success\", url) } err = nil if numErrors >= threshold { err = fmt.Errorf(\"Too many Errors in continuous echo\") } errorChannel <- err } </del> // testReachableUDP tests that the given host serves UDP on the given port. func testReachableUDP(host string, port int, timeout time.Duration) { pollfn := func() (bool, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-66f25b05b1c90d93aad713cb7c943585d55afc690fe7a4f7e9fa0b7a5a5f23b1", "text": "3) Would simulating this in kind by overloading coredns be a possibility as a way to make a more reproducible bug model?\nregarding 1) kubeadm does not ship nodeLocalDNSCache I don't think GCE kube-up does by default either\nok, so now im curious about (2) - i.e. what if we just bumped coredns replica count?\ninteresting, :thinking: why do you think is a DNS thing? the netcat command that polls the services use the IP addresses not the hostname. I think that it has to be related to some iptables/conntrack race or similar,at least in KIND jobs we know that we have an iptables problem that affects network tests, that has to be fixed before this because it affect this test You can instrument the test locally with this and dump the state of iptables and conntrack on failure if you are able to reproduce it\ni figured DNS bc i believe its known that conntrack and DNS at scale can get very messy, right ?\none other curious thing about this test is that we only create 2 pods in the recycling event for the svc. that likely means that any real error is hidden by chance..... If we created a 3rd pod, then we might potentially double the failure rate thus making the flakyness go away and expose the real underlying issue .\nThere's an invocation of dumpConntrack(cs) here [sig-network] Conntrack should be able to preserve UDP traffic when server pod cycles for a ClusterIP service\nis updating the logging to run in an infinite loop ..\nThis is improving in KIND with the new changes we rolled out yesterday, let's see how it evolves this week\n- which changes ? Are you saying this is no longer reproducible on Kind?\nthere was a lot of noise in the CI signal, especially in KIND jobs due to the CNI portmap bug we finally solved yesterday now we should have a better signal and we can go to the bottom because probably the failure will be \"legit\" and not a consequence, so this comment should apply\nHi ! I ran this a few times on kind and it passed, but I see , so I'm going to try the loop approach you suggested. Here's what I'm using to test:\nquick note, <- potential motivation to possibly have runnable on some subset of tests in upstream eventually, i.e.", "commid": "kubernetes_issue_91236", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d117c6d496fac083391cb647f0b228758dbef37d83526c8d013cf8dd88a84dd", "query": "return ret } <del> // continuousEcho() uses the same connection for multiple requests, made to run as a goroutine so that // manipulations can be made to the service and backend pods while a connection is ongoing // it starts by sending a series of packets to establish conntrack entries and waits for a signal to keep // sending packts. It returns an error if the number of failed attempts is >= 5 func continuousEcho(host string, port int, timeout time.Duration, maxAttempts int, signal chan struct{}, errorChannel chan error) { defer ginkgo.GinkgoRecover() const threshold = 10 // Sanity check inputs, because it has happened.  These are the only things // that should hard fail the test - they are basically ASSERT()s. if host == \"\" { errorChannel <- fmt.Errorf(\"Got empty host for continuous echo (%s)\", host) return } if port == 0 { errorChannel <- fmt.Errorf(\"Got port ==0 for continuous echo (%d)\", port) return } hostPort := net.JoinHostPort(host, strconv.Itoa(port)) url := fmt.Sprintf(\"udp://%s\", hostPort) ret := UDPPokeResult{} con, err := net.Dial(\"udp\", hostPort) if err != nil { ret.Status = UDPError ret.Error = err errorChannel <- fmt.Errorf(\"Connection to %q failed: %v\", url, err) return } numErrors := 0 bufsize := len(strconv.Itoa(maxAttempts)) + 1 var buf = make([]byte, bufsize) for i := 0; i < maxAttempts; i++ { if i == threshold { framework.Logf(\"Continuous echo waiting for signal to continue\") <-signal if numErrors == threshold { errorChannel <- fmt.Errorf(\"continuous echo was not able to communicate with initial server pod\") return } } time.Sleep(1 * time.Second) err = con.SetDeadline(time.Now().Add(timeout)) if err != nil { ret.Status = UDPError ret.Error = err framework.Logf(\"Continuous echo (%q): %v\", url, err) numErrors++ continue } myRequest := fmt.Sprintf(\"echo %d\", i) _, err = con.Write([]byte(fmt.Sprintf(\"%sn\", myRequest))) if err != nil { ret.Error = err neterr, ok := err.(net.Error) if ok && neterr.Timeout() { ret.Status = UDPTimeout } else if strings.Contains(err.Error(), \"connection refused\") { ret.Status = UDPRefused } else { ret.Status = UDPError } numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } err = con.SetDeadline(time.Now().Add(timeout)) if err != nil { ret.Status = UDPError ret.Error = err numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } n, err := con.Read(buf) if err != nil { ret.Error = err neterr, ok := err.(net.Error) if ok && neterr.Timeout() { ret.Status = UDPTimeout } else if strings.Contains(err.Error(), \"connection refused\") { ret.Status = UDPRefused } else { ret.Status = UDPError } numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } ret.Response = buf[0:n] if string(ret.Response) != fmt.Sprintf(\"%d\", i) { ret.Status = UDPBadResponse ret.Error = fmt.Errorf(\"response does not match expected string: %q\", string(ret.Response)) framework.Logf(\"Continuous echo (%q): %v\", url, ret.Error) numErrors++ continue } ret.Status = UDPSuccess framework.Logf(\"Continuous echo(%q): success\", url) } err = nil if numErrors >= threshold { err = fmt.Errorf(\"Too many Errors in continuous echo\") } errorChannel <- err } </del> // testReachableUDP tests that the given host serves UDP on the given port. func testReachableUDP(host string, port int, timeout time.Duration) { pollfn := func() (bool, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-deebb69aabcaf9005201c68e52f1f862e88c30f5231beaa0034b1d576abe9a4a", "text": "so we can do things like to reproduce this sort of thing. matt did you get around to the 'try-till-it-fails' scenario?\nI haven't been able to get it to fail on kind yet, -- 100 cycles and 0 failures on a three-node kind cluster! I'm letting the loop run for a few hours, will check back in when I have that data. Is it worth running this test on a non-kind environment?\nI ran for several hours on my mac, through 1144 iterations no error yet. My conclusion: this test isn't flaky on KinD. Possible next step: run a large number of iterations of the same test on a GKE cluster.\nFlakes on kind are also happening:\nnot many since the portmap fix on the 14th though ( / ) <img width=\"1111\" alt=\"Screen Shot 2020-07-23 at 11 45 46 PM\" src=\"https://user-\"\nAgree - it's much better than it was before.\nI was analyzing this failure, the problem is that kind jobs does not have verbosity enough in kube-proxy We can see that the packet was never replied, this is the NAT entry from client -nodePort in the node with the client This is the same flow, but in the node with the server and the pod-server-1 seems to be healthy we need more logs :eyeglasses:\nWe have an open ticket to bump those in CI, it's just been lost in the noise. We should still do that. Antonio Ojea <:\nIf you are busy just assign it to me, I'll need this verbosity soon :)\nIt's in the kind repo, shouldn't be too hard to find, we have ~60 open atm. Antonio Ojea <:\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\nI made another attempt to reproduce these failures locally on KinD, but still no success. Here's what I did: create a KinD cluster run two instances of sonobuoy at the same time This took ~4 hours to run; all the kube tests passed and sonobuoy reported all successes.", "commid": "kubernetes_issue_91236", "tokennum": 494}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d117c6d496fac083391cb647f0b228758dbef37d83526c8d013cf8dd88a84dd", "query": "return ret } <del> // continuousEcho() uses the same connection for multiple requests, made to run as a goroutine so that // manipulations can be made to the service and backend pods while a connection is ongoing // it starts by sending a series of packets to establish conntrack entries and waits for a signal to keep // sending packts. It returns an error if the number of failed attempts is >= 5 func continuousEcho(host string, port int, timeout time.Duration, maxAttempts int, signal chan struct{}, errorChannel chan error) { defer ginkgo.GinkgoRecover() const threshold = 10 // Sanity check inputs, because it has happened.  These are the only things // that should hard fail the test - they are basically ASSERT()s. if host == \"\" { errorChannel <- fmt.Errorf(\"Got empty host for continuous echo (%s)\", host) return } if port == 0 { errorChannel <- fmt.Errorf(\"Got port ==0 for continuous echo (%d)\", port) return } hostPort := net.JoinHostPort(host, strconv.Itoa(port)) url := fmt.Sprintf(\"udp://%s\", hostPort) ret := UDPPokeResult{} con, err := net.Dial(\"udp\", hostPort) if err != nil { ret.Status = UDPError ret.Error = err errorChannel <- fmt.Errorf(\"Connection to %q failed: %v\", url, err) return } numErrors := 0 bufsize := len(strconv.Itoa(maxAttempts)) + 1 var buf = make([]byte, bufsize) for i := 0; i < maxAttempts; i++ { if i == threshold { framework.Logf(\"Continuous echo waiting for signal to continue\") <-signal if numErrors == threshold { errorChannel <- fmt.Errorf(\"continuous echo was not able to communicate with initial server pod\") return } } time.Sleep(1 * time.Second) err = con.SetDeadline(time.Now().Add(timeout)) if err != nil { ret.Status = UDPError ret.Error = err framework.Logf(\"Continuous echo (%q): %v\", url, err) numErrors++ continue } myRequest := fmt.Sprintf(\"echo %d\", i) _, err = con.Write([]byte(fmt.Sprintf(\"%sn\", myRequest))) if err != nil { ret.Error = err neterr, ok := err.(net.Error) if ok && neterr.Timeout() { ret.Status = UDPTimeout } else if strings.Contains(err.Error(), \"connection refused\") { ret.Status = UDPRefused } else { ret.Status = UDPError } numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } err = con.SetDeadline(time.Now().Add(timeout)) if err != nil { ret.Status = UDPError ret.Error = err numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } n, err := con.Read(buf) if err != nil { ret.Error = err neterr, ok := err.(net.Error) if ok && neterr.Timeout() { ret.Status = UDPTimeout } else if strings.Contains(err.Error(), \"connection refused\") { ret.Status = UDPRefused } else { ret.Status = UDPError } numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } ret.Response = buf[0:n] if string(ret.Response) != fmt.Sprintf(\"%d\", i) { ret.Status = UDPBadResponse ret.Error = fmt.Errorf(\"response does not match expected string: %q\", string(ret.Response)) framework.Logf(\"Continuous echo (%q): %v\", url, ret.Error) numErrors++ continue } ret.Status = UDPSuccess framework.Logf(\"Continuous echo(%q): success\", url) } err = nil if numErrors >= threshold { err = fmt.Errorf(\"Too many Errors in continuous echo\") } errorChannel <- err } </del> // testReachableUDP tests that the given host serves UDP on the given port. func testReachableUDP(host string, port int, timeout time.Duration) { pollfn := func() (bool, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-738ad9cb1373dead6b2f556ac241cd0c8a6cc7a0f09950111e765d9eb1dab68b", "text": "Would love to help out in reproing this, I'm at a loss for good next step so any suggestions welcome!\nthat's the problem with these flakes, they are not easy to repro, and with this low rate of failures it may be caused for combination of running tests, environmental problems (cpu, memory, ...) , ... I always start for checking the current failures and try to find patterns\nLet's take a look to one occurrence The tests fails because can't connect to the first pod If we check the code of the tests, we can see that it always uses the port as source port, we can use that to identify the nodePort assigned interesting thing here, we are source nating the pod ip, and we don't see any other conntrack entry The test verifies it has endpoints however, kube-proxy is using endpointlsices since this version but it has no entries so the iptables rules to forward the traffic are not there Seems we have to adapt this function in the e2e framework to use endpointslices cc: EDIT seems that this function is being used by all the network tests that can cause flakes if the endpoint is updated before the endpointslice (we switched recently kube-proxy to use the later)\nGreat catch. Ideally this function should validate if both Endpoint and appropriate EndpointSlice objects(s) exist.\nActually - let me take it and send a PR for it.\nis out for review\nInteresting failures here It fails to connect to the first pod\nHmm - I took a quick look at kube-proxy logs and these look fine to me....\nI clicked too fast, sorry ... I was looking at the wrong service and I though I've found something\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry.", "commid": "kubernetes_issue_91236", "tokennum": 416}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d117c6d496fac083391cb647f0b228758dbef37d83526c8d013cf8dd88a84dd", "query": "return ret } <del> // continuousEcho() uses the same connection for multiple requests, made to run as a goroutine so that // manipulations can be made to the service and backend pods while a connection is ongoing // it starts by sending a series of packets to establish conntrack entries and waits for a signal to keep // sending packts. It returns an error if the number of failed attempts is >= 5 func continuousEcho(host string, port int, timeout time.Duration, maxAttempts int, signal chan struct{}, errorChannel chan error) { defer ginkgo.GinkgoRecover() const threshold = 10 // Sanity check inputs, because it has happened.  These are the only things // that should hard fail the test - they are basically ASSERT()s. if host == \"\" { errorChannel <- fmt.Errorf(\"Got empty host for continuous echo (%s)\", host) return } if port == 0 { errorChannel <- fmt.Errorf(\"Got port ==0 for continuous echo (%d)\", port) return } hostPort := net.JoinHostPort(host, strconv.Itoa(port)) url := fmt.Sprintf(\"udp://%s\", hostPort) ret := UDPPokeResult{} con, err := net.Dial(\"udp\", hostPort) if err != nil { ret.Status = UDPError ret.Error = err errorChannel <- fmt.Errorf(\"Connection to %q failed: %v\", url, err) return } numErrors := 0 bufsize := len(strconv.Itoa(maxAttempts)) + 1 var buf = make([]byte, bufsize) for i := 0; i < maxAttempts; i++ { if i == threshold { framework.Logf(\"Continuous echo waiting for signal to continue\") <-signal if numErrors == threshold { errorChannel <- fmt.Errorf(\"continuous echo was not able to communicate with initial server pod\") return } } time.Sleep(1 * time.Second) err = con.SetDeadline(time.Now().Add(timeout)) if err != nil { ret.Status = UDPError ret.Error = err framework.Logf(\"Continuous echo (%q): %v\", url, err) numErrors++ continue } myRequest := fmt.Sprintf(\"echo %d\", i) _, err = con.Write([]byte(fmt.Sprintf(\"%sn\", myRequest))) if err != nil { ret.Error = err neterr, ok := err.(net.Error) if ok && neterr.Timeout() { ret.Status = UDPTimeout } else if strings.Contains(err.Error(), \"connection refused\") { ret.Status = UDPRefused } else { ret.Status = UDPError } numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } err = con.SetDeadline(time.Now().Add(timeout)) if err != nil { ret.Status = UDPError ret.Error = err numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } n, err := con.Read(buf) if err != nil { ret.Error = err neterr, ok := err.(net.Error) if ok && neterr.Timeout() { ret.Status = UDPTimeout } else if strings.Contains(err.Error(), \"connection refused\") { ret.Status = UDPRefused } else { ret.Status = UDPError } numErrors++ framework.Logf(\"Continuous echo (%q): %v - %d errors seen so far\", url, err, numErrors) continue } ret.Response = buf[0:n] if string(ret.Response) != fmt.Sprintf(\"%d\", i) { ret.Status = UDPBadResponse ret.Error = fmt.Errorf(\"response does not match expected string: %q\", string(ret.Response)) framework.Logf(\"Continuous echo (%q): %v\", url, ret.Error) numErrors++ continue } ret.Status = UDPSuccess framework.Logf(\"Continuous echo(%q): success\", url) } err = nil if numErrors >= threshold { err = fmt.Errorf(\"Too many Errors in continuous echo\") } errorChannel <- err } </del> // testReachableUDP tests that the given host serves UDP on the given port. func testReachableUDP(host string, port int, timeout time.Duration) { pollfn := func() (bool, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-7b1ee5acca525c6b88a5b6825056ab7c4df586768503c885715c9a87d944744a", "text": "\u200d\njust saw it as well\ncan you please add links to the job with the failures, I just merged new code to improve the logging 2 days ago\nok, here there is a new occurrence and with the new debug logs is easier to follow has unreplied conntrack entries: looking at the other side The iptables rules are there but no conntrack entries related to 10.244.2.32\nIn I revert PR with debug info as I think that it likely caused significant memory growth in scalability tests, but we have one run that has finished without being killed by OOMKiller (I increased memory limit for that jobs as a mitigation). Maybe logs from this run will be useful for debugging:\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\nTwo more flakes today:\nIt seems that the packet never gets DNATed in the receiving host, so it does not reach the pod in the node. There is the same test that is using ClusterIP instead of NodePort that is more reliable. This is being a tough one\n/triage accepted\nYesterday's flake - I don't think I'm seeing the log messages from the latest log PR you made ? Or are the prow logs not logging at a high-enough level?\nLogs are there, please bear with me: The error on the test is: click on the job failure and you'll see a larger output where you can see the server pod name and get the node where the pod is running: and the client-pod name and its node: and the flow we are looking for: with the node-name we can get the kube-proxy logs there, clicking in artifacts: and you can see the \"new\" conntrack log entries : and in the client: wow, there is a kernel bug there , can it be related? :thinking:\nwohoo - some progress :) I'm not an expert here, but I think it can be? Adding here - they may be able to confirm/reject the hypothesis.\nThis kernel panic may be a coincidence, maybe this is the reason\nAdding some recent failures:\nSpotted another flake today:\nAnother flake in the 5k job:", "commid": "kubernetes_issue_91236", "tokennum": 495}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d36433b0a004468937813ba8af69af1e1388989dfb07a6b285f33a605bf1645", "query": "return fmt.Errorf(\"waiting for kubelet timed out\") } <del> func RestartApiserver(c discovery.ServerVersionInterface) error { </del> <ins> func RestartApiserver(cs clientset.Interface) error { </ins> // TODO: Make it work for all providers. if !ProviderIs(\"gce\", \"gke\", \"aws\") { return fmt.Errorf(\"unsupported provider: %s\", TestContext.Provider) } if ProviderIs(\"gce\", \"aws\") { <del> return sshRestartMaster() </del> <ins> initialRestartCount, err := getApiserverRestartCount(cs) if err != nil { return fmt.Errorf(\"failed to get apiserver's restart count: %v\", err) } if err := sshRestartMaster(); err != nil { return fmt.Errorf(\"failed to restart apiserver: %v\", err) } return waitForApiserverRestarted(cs, initialRestartCount) </ins> } // GKE doesn't allow ssh access, so use a same-version master // upgrade to teardown/recreate master. <del> v, err := c.ServerVersion() </del> <ins> v, err := cs.Discovery().ServerVersion() </ins> if err != nil { return err }", "positive_passages": [{"docid": "doc-en-kubernetes-45049cecee14166a5520f4dc4cbecae5a5a4a44f20c23557ee81cd45d6979f23", "text": "This test is failing in both gce serial suite: http://k8s- /sig network /priority failing-test /priority critical-urgent /kind bug /status approved-for-milestone cc /assign PTAL\nxref\n/milestone v1.10\nthis also fails in http://k8s-\nFailing to connect to Services at all. I can't even ping pod IPs:\nSo I can ping pods same-node and cross-node right up until it kills the apiserver. Rebooting fixes a given node. The apiserver demonstrably comes back - I can query it for info...\n- I could use help - have to shift attention soon.\nFWIW, I am testing on a Calico-enabled node\nI'll take a look at this as well.\nWeird, now even after a reboot, this condition is sticky. I have a cluster in this state, if you want to poke.\nugh, now it is resolved.\nI just repro'ed without the e2e - have a cluster, proved ping works, killed apiserver ping fails.\nInteresting - docker shows the pods not running, but apiserver says they are alive.\nUpdate: docker sees no running pods. API server thinks kubelet is running them. kubelet is getting \"\" from apiserver, even after kubelet restart.\nUpdate and recap: Bring up a cluster Run some pods Prove that pods are running and services work pkill -9 apiserver Wait. Watch kubelets \"lose\" pods that were assigned to them Observe that pods are not running and services do not work Observe that apiserver says the pods are running pkill -9 kubelet Observe that it is still broken kubectl delete one pod Observe that kubelet is fixed for that one pod, but not others Q: Why is kubelet not getting a full listing when it restarts?\nWhat exactly does it mean for it to be fixed for a deleted pod?\nKubelet started running the pod that was deleted - it got the update for that one.\nThe cluster I was testing was a week or 2 old. I built a cluster from HEAD and I can not repro - said the same. Is this test running against head of master?\nI also ran the test manually against my new cluster and it passed\nFWIW I was also unable to reproduce this yesterday on a cluster from HEAD.", "commid": "kubernetes_issue_60761", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d36433b0a004468937813ba8af69af1e1388989dfb07a6b285f33a605bf1645", "query": "return fmt.Errorf(\"waiting for kubelet timed out\") } <del> func RestartApiserver(c discovery.ServerVersionInterface) error { </del> <ins> func RestartApiserver(cs clientset.Interface) error { </ins> // TODO: Make it work for all providers. if !ProviderIs(\"gce\", \"gke\", \"aws\") { return fmt.Errorf(\"unsupported provider: %s\", TestContext.Provider) } if ProviderIs(\"gce\", \"aws\") { <del> return sshRestartMaster() </del> <ins> initialRestartCount, err := getApiserverRestartCount(cs) if err != nil { return fmt.Errorf(\"failed to get apiserver's restart count: %v\", err) } if err := sshRestartMaster(); err != nil { return fmt.Errorf(\"failed to restart apiserver: %v\", err) } return waitForApiserverRestarted(cs, initialRestartCount) </ins> } // GKE doesn't allow ssh access, so use a same-version master // upgrade to teardown/recreate master. <del> v, err := c.ServerVersion() </del> <ins> v, err := cs.Discovery().ServerVersion() </ins> if err != nil { return err }", "positive_passages": [{"docid": "doc-en-kubernetes-a335c4245d7a15c6e680ffd06bca4d469bc98515fa6a43286dbf7f7a3bfccc88", "text": "Did some investigations and had some findings for this specific failure: Traced down a bit on the history, the first occurrence was https://k8s- From the , seems suspicious because it modified . Also found reported a relevant symptom: The fix () for that was merged a day ago and may explained why we can't repro from HEAD anymore.\nnice, is this issue reproducible without the fix ()?\nSorry should have had confirmed this, bringing up a cluster now.\nQuick update: I was able to repro the same failure () from HEAD with reverted. Though this test is now flaky on some other errors: https://k8s- https://k8s- They all seem to failed while communicating with apiserver.\nThanks ! So fixed the issue and I am curious about what introduced the issue. Do you happen to know when did this test start to fail? Just trying to find out what went wrong in between. We have some other possibly related issues so finding out the root cause of this one would be super helpful.\n/assign\nThe first occurrence (for that exact failure) I noticed was https://k8s-, which happened on 2018-02-15 09:49 PST.\nYou all rock! I see a couple greens on it now, but still mostly red?\nThe test is now flaky mostly on creating an exec pod after restarting apiserver. Some sample failures: To elaborate a bit more, a snippet of the test procedure is: ssh to master and (sending a SIGTERM) Keep polling on /healthz on apiserver until 200 is returned. Create an exec pod for later steps (and failed on various erros --- EOF, connection refused, apiserver terminating). According to above test failures, my suspicion is that the test is assuming the apiserver is restarted too soon. It is possible that apiserver captured SIGTERM and did a graceful termination, so that polling on /healthz may succeed even in the termination phase. I'm not surprised trying to create a pod via a terminating apiserver will hit those errors. Could anyone confirme the SIGTERM theory?\nSpoke with folks, sounds like after SIGTERM apiserver does wait a bit for remaining requests to finish. I will take a stab to refine the test. cc\nSent .\nTest is now passing on gce but failing on gke.", "commid": "kubernetes_issue_60761", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d36433b0a004468937813ba8af69af1e1388989dfb07a6b285f33a605bf1645", "query": "return fmt.Errorf(\"waiting for kubelet timed out\") } <del> func RestartApiserver(c discovery.ServerVersionInterface) error { </del> <ins> func RestartApiserver(cs clientset.Interface) error { </ins> // TODO: Make it work for all providers. if !ProviderIs(\"gce\", \"gke\", \"aws\") { return fmt.Errorf(\"unsupported provider: %s\", TestContext.Provider) } if ProviderIs(\"gce\", \"aws\") { <del> return sshRestartMaster() </del> <ins> initialRestartCount, err := getApiserverRestartCount(cs) if err != nil { return fmt.Errorf(\"failed to get apiserver's restart count: %v\", err) } if err := sshRestartMaster(); err != nil { return fmt.Errorf(\"failed to restart apiserver: %v\", err) } return waitForApiserverRestarted(cs, initialRestartCount) </ins> } // GKE doesn't allow ssh access, so use a same-version master // upgrade to teardown/recreate master. <del> v, err := c.ServerVersion() </del> <ins> v, err := cs.Discovery().ServerVersion() </ins> if err != nil { return err }", "positive_passages": [{"docid": "doc-en-kubernetes-937105a0fb62d0b30f0dcf82865ffcd7dde374c2d2e0895384450ffe72527abd", "text": "Apparently we don't have a way to trigger apiserver restart on gke at this moment. Sending a PR to skip this test on gke.\n[MILESTONENOTIFIER] Milestone Issue Needs Attention Action required: During code freeze, issues in the milestone should be in progress. If this issue is not being actively worked on, please remove it from the milestone. If it is being worked on, please add the label so it can be tracked with other in-flight issues. Note: This issue is marked as , and must be updated every 1 day during code freeze. Example update: <details<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Never automatically move issue out of a release milestone; continually escalate to contributor and SIG through all available channels. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details\nCommented too quick. On gke we do a same-version master upgrade. Will send another fix :/", "commid": "kubernetes_issue_60761", "tokennum": 256}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d40c8dc2ec7ce64bce5466938a3d7137fc1e54a655d2f260d14f82f195e4d0a", "query": "return nil } <del> var redactedBytes []byte </del> <ins> var ( redactedBytes    []byte dataOmittedBytes []byte ) </ins> // Flatten redacts raw data entries from the config object for a human-readable view. func ShortenConfig(config *Config) {", "positive_passages": [{"docid": "doc-en-kubernetes-397ec6d3ebe6b2748109f44339689e34d7c15d3a74b9e08d5b86ed108288f149", "text": "Is this a BUG REPORT or FEATURE REQUEST?: What happened: shows: The use of \"REDACTED\" for a CA here is misleading, since it's a public certificate that is not a secret. What you expected to happen: I expected to see the full CA in pem format (like when you cat ) or something like \"SUPPRESSED\" or \"TRUNCATED\" How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Nope Environment: Kubernetes version (use ):Cloud provider or hardware configuration:OS (e.g. from /etc/os-release):Kernel (e.g. ):\n(for thoughts)\nReiterating the mentions to trigger a notification: <detailsIn response to : (for thoughts) 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\nuse you can see the complete certificate authority data\nHey Thank you - I have tracking that . The point of this issue is that at best it's a bad UX; at worst it's a miseducation on pki. \"REDACTED\" isn't the right word here\nIf there are multiple clusters displaying certificates, the configuration will be too long, so this switch is turned off by default. But we can add an example to help use. thanks\nHey I don't personally view truncation the responsibility of the CLI... users can pipe things to a pager if they really care. That being said, I'm not concerned about the length. The issue is purely about the word choice of \"REDACTED\". The term means: The use of the term \"REDACTED\" in the output implies that a CA public key is remove for security when (as you've pointed out) it is removed for truncation. Truncation and redaction are fundamentally different things, and k8s is misusing the word redacted for this use case.\nNot quite a bug, but I think you're right a better term could be used there as it is a public key, not a private key. /remove-kind bug\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close.", "commid": "kubernetes_issue_61573", "tokennum": 495}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d40c8dc2ec7ce64bce5466938a3d7137fc1e54a655d2f260d14f82f195e4d0a", "query": "return nil } <del> var redactedBytes []byte </del> <ins> var ( redactedBytes    []byte dataOmittedBytes []byte ) </ins> // Flatten redacts raw data entries from the config object for a human-readable view. func ShortenConfig(config *Config) {", "positive_passages": [{"docid": "doc-en-kubernetes-be8602378a7d778cfbc76bff14bb786f501b2719d8c237c227cdd36827d468ae", "text": "If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale I'm not sure what I need to do here. This was marked as a feature. Do you need something more from me?\nWe are waiting for someone to fix this.\n/remove-good-first-issue I don't think this fits our definition of a :\nSo I have to keep replying to the comment bot every 30 days so it doesn't get auto-closed? That feels... odd\nthanks for the education :) unfortunately other issues are higher priority and no one has stepped up to fix this. The autocloser is a form of bug bankruptcy that keeps our issue load in check. The contribex special interest group is definitely open to feedback on the bot.\nThe biggest hurdle in this is that Kubernetes is using some base64 trickery to display the string (basically setting the certificate data to the decoded bytes from ). We can change this to or but not (it has to be a valid base64 encoded string). I tried exploring multiple options for the text, but I couldn't find a suitable one. Given that we already print the user tokens and other credentials this is a bit weird. Should we redact those too? Is it okay if we print the CA certificate instead of truncating it?\nI can't help but laugh at: I'm not wed to any particular name. I also have no problem displaying the entire certificate. The crux of the issue is that a CA public key is not secret or sensitive. It's a public key\nI agree. The issue is with the constraints imposed by how this is implemented currently. I tried to come up with a suitable string (given the constraint) and couldn't find anything acceptable... The only suitable option that worked for me is . I personally prefer to print the CA certificate since we are already printing user tokens and client certs that are actual secrets.\nI agree. Who do we need to get in agreement that printing the full CA is the best path forward?\nthe data is not omitted for security purposes, but to make the output more readable. see REDACTED is misleading... it should probably be \"elided\" or \"...\"\nyou can run to view full content\nthat's the crux of this issue - REDACTED is misleading.", "commid": "kubernetes_issue_61573", "tokennum": 520}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d40c8dc2ec7ce64bce5466938a3d7137fc1e54a655d2f260d14f82f195e4d0a", "query": "return nil } <del> var redactedBytes []byte </del> <ins> var ( redactedBytes    []byte dataOmittedBytes []byte ) </ins> // Flatten redacts raw data entries from the config object for a human-readable view. func ShortenConfig(config *Config) {", "positive_passages": [{"docid": "doc-en-kubernetes-0c20cfda2a4143b97ca34085e4ba4933a2256b4cc12b09ed01e77387d3b1e642", "text": "However, pointed out that other \"long\" fields are still completely printed in plain text such as client certs, so I think we need to revisit the \"readability\" argument. What do you think?\nthey are not... client cert/key are elided in the same way for the same reason: something like \"++data+omitted++\" could be better If the intent of config view without --raw specified is to be readable (which it currently is), printing many extremely long fields isn't great\nHmm what about: I'm pretty sure that would give us a valid b64 string (8+12=20%4=0) and it would subtly hint that the data isn't a secret.\nOnly valid characters are . And adding a prefix from the certificate only complicates things. is a suitable usable option. I'll submit a PR to continue the discussion there.", "commid": "kubernetes_issue_61573", "tokennum": 195}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d695f1d2efc90a7c2026f46d6f53493e20f2196e8244c9a0359cecda44d10b0", "query": "// When specified, it should match one the container or initContainer // names in the pod template. // +optional <del> ContainerName *string `json:\"containerName\" protobuf:\"bytes,1,opt,name=containerName\"` </del> <ins> ContainerName *string `json:\"containerName,omitempty\" protobuf:\"bytes,1,opt,name=containerName\"` </ins> // Represents the relationship between the container exit code(s) and the // specified values. Containers completed with success (exit code 0) are", "positive_passages": [{"docid": "doc-en-kubernetes-f4d4b7c473a266ffc48b535d9080ecbdaed52af3a9bd64395678a7e260a39c7f", "text": "for a PodFailurePolicyRule. However, when trying to create a JobSet programmatically with a JobTemplate that defines a PodFailurePolicy rule for failing a job immediately if the failed pod had condition DisruptionTarget, I get a validation error indicating that cannot be null. I've tried using both and (with matching versions for package as well). Error: JobSet spec: JobTemplate passes validation. JobSet: applying example JobSet in the description of this issue. JobSet: and applying example JobSet in the description of this issue. No response 30 (tests on a kind cluster using kindest/node:v1.30.0) <details</details<details</details<details</details<details</details<details</details\nThere are no sig labels on this issue. Please add an appropriate label by using one of the following commands: - Please see the for a listing of the SIGs, working groups, and committees available. <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\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\ncc\n/assign\nI confirmed the issue, moreover, I see that when the JobSet webhook is disabled then it works ok, I think it must be the JobSet webhook which adds the \"onExitCodes\" field during deserializion /serialization step. I can also see that when I rebuild JobSet using kubernetes field \"onExitCodes\" with \"omitempty\", then it the JobSet creates ok. I will open a PR.", "commid": "kubernetes_issue_126040", "tokennum": 438}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d74f0a7a8c59513c0cac67df0fb810473118531bd3df4167ad849cfad9788c3", "query": "name = \"go_default_test\", size = \"large\", srcs = [ <ins> \"etcd_cross_group_test.go\", </ins> \"etcd_storage_path_test.go\", \"main_test.go\", ],", "positive_passages": [{"docid": "doc-en-kubernetes-7ee140198c665b218e0dfb7e3cd2f2624912887cfcfab5f30828d12c6130aa35", "text": "What happened: Set up a HA cluster with 1.9 and 1.10 API servers (occurs on any apiserver skew boundary where a cohabitating resource's storage version changed groups) Observed errors when modifying workload objects: when modified via the 1.10 server, saw this error in the 1.9 server: when modified via the 1.9 server, saw this error in the 1.10 server: When this error was encountered, all watchers for the resource in question would be dropped and have to re-establish, and the internal watchers feeding the watch cache would drop and re-establish What you expected to happen: Watch events from all supported storage versions are processed correctly How to reproduce it (as minimally and precisely as possible): Start a server from master (for inspectability, store in json). With Create a deployment (e.g. kube-dns in kube-system) Establish a watch via extensions (kubectl get deployments.extensions --all-namespaces -w) Establish a watch via apps (kubectl get --all-namespaces -w) Tail the kube-apiserver log Change the apps/v1 deployment in etcd to extensions/v1beta1: Observer client watches drop and server log errors: Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: /sig api-machinery /cc /priority critical-urgent\nerror is triggered by this returning false: constructed here: the info about expected cohabitating groups is not included in the list of acceptable inputs", "commid": "kubernetes_issue_73478", "tokennum": 368}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d7ade23bfc64d460b78da9a1a6a5c595815ef4a9c4754b2ea6e10bc4117d2b3", "query": "Expect(curHistory).NotTo(BeNil()) return curHistory } <ins> func waitFailedDaemonPodDeleted(c clientset.Interface, pod *v1.Pod) func() (bool, error) { return func() (bool, error) { if _, err := c.CoreV1().Pods(pod.Namespace).Get(pod.Name, metav1.GetOptions{}); err != nil { if errors.IsNotFound(err) { return true, nil } return false, fmt.Errorf(\"failed to get failed daemon pod %q: %v\", pod.Name, err) } return false, nil } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-da00f1cf1a24475bca3717ed24d8bd1cf5079c51cd54d6d4d01b160ed7cae851", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: DaemonSet has an e2e test running that has dubious purpose. What you expected to happen: The e2e test should be refactored and commented clearer as it will be part of the conformance.\nTo elaborate, we're concerned that the following may not actually ensure that DaemonSet recreates Failed Pods: For example, it seems possible that the Node might simply overwrite the Pod status with its own information if it hasn't yet seen the change to the Phase. Ideally, we should verify that the Pod UID we force to Failed no longer shows up in the DaemonSet's list of Pods after the DaemonSet becomes happy again.", "commid": "kubernetes_issue_59076", "tokennum": 150}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d801b95dd6099db09c59200bfe3796beafd992d73b09b769eed1e4056845101", "query": "func init() { sDec, _ := base64.StdEncoding.DecodeString(\"REDACTED+\") redactedBytes = []byte(string(sDec)) <ins> sDec, _ = base64.StdEncoding.DecodeString(\"DATA+OMITTED\") dataOmittedBytes = []byte(string(sDec)) </ins> } // IsConfigEmpty returns true if the config is empty.", "positive_passages": [{"docid": "doc-en-kubernetes-397ec6d3ebe6b2748109f44339689e34d7c15d3a74b9e08d5b86ed108288f149", "text": "Is this a BUG REPORT or FEATURE REQUEST?: What happened: shows: The use of \"REDACTED\" for a CA here is misleading, since it's a public certificate that is not a secret. What you expected to happen: I expected to see the full CA in pem format (like when you cat ) or something like \"SUPPRESSED\" or \"TRUNCATED\" How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Nope Environment: Kubernetes version (use ):Cloud provider or hardware configuration:OS (e.g. from /etc/os-release):Kernel (e.g. ):\n(for thoughts)\nReiterating the mentions to trigger a notification: <detailsIn response to : (for thoughts) 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\nuse you can see the complete certificate authority data\nHey Thank you - I have tracking that . The point of this issue is that at best it's a bad UX; at worst it's a miseducation on pki. \"REDACTED\" isn't the right word here\nIf there are multiple clusters displaying certificates, the configuration will be too long, so this switch is turned off by default. But we can add an example to help use. thanks\nHey I don't personally view truncation the responsibility of the CLI... users can pipe things to a pager if they really care. That being said, I'm not concerned about the length. The issue is purely about the word choice of \"REDACTED\". The term means: The use of the term \"REDACTED\" in the output implies that a CA public key is remove for security when (as you've pointed out) it is removed for truncation. Truncation and redaction are fundamentally different things, and k8s is misusing the word redacted for this use case.\nNot quite a bug, but I think you're right a better term could be used there as it is a public key, not a private key. /remove-kind bug\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close.", "commid": "kubernetes_issue_61573", "tokennum": 495}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d801b95dd6099db09c59200bfe3796beafd992d73b09b769eed1e4056845101", "query": "func init() { sDec, _ := base64.StdEncoding.DecodeString(\"REDACTED+\") redactedBytes = []byte(string(sDec)) <ins> sDec, _ = base64.StdEncoding.DecodeString(\"DATA+OMITTED\") dataOmittedBytes = []byte(string(sDec)) </ins> } // IsConfigEmpty returns true if the config is empty.", "positive_passages": [{"docid": "doc-en-kubernetes-be8602378a7d778cfbc76bff14bb786f501b2719d8c237c227cdd36827d468ae", "text": "If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale I'm not sure what I need to do here. This was marked as a feature. Do you need something more from me?\nWe are waiting for someone to fix this.\n/remove-good-first-issue I don't think this fits our definition of a :\nSo I have to keep replying to the comment bot every 30 days so it doesn't get auto-closed? That feels... odd\nthanks for the education :) unfortunately other issues are higher priority and no one has stepped up to fix this. The autocloser is a form of bug bankruptcy that keeps our issue load in check. The contribex special interest group is definitely open to feedback on the bot.\nThe biggest hurdle in this is that Kubernetes is using some base64 trickery to display the string (basically setting the certificate data to the decoded bytes from ). We can change this to or but not (it has to be a valid base64 encoded string). I tried exploring multiple options for the text, but I couldn't find a suitable one. Given that we already print the user tokens and other credentials this is a bit weird. Should we redact those too? Is it okay if we print the CA certificate instead of truncating it?\nI can't help but laugh at: I'm not wed to any particular name. I also have no problem displaying the entire certificate. The crux of the issue is that a CA public key is not secret or sensitive. It's a public key\nI agree. The issue is with the constraints imposed by how this is implemented currently. I tried to come up with a suitable string (given the constraint) and couldn't find anything acceptable... The only suitable option that worked for me is . I personally prefer to print the CA certificate since we are already printing user tokens and client certs that are actual secrets.\nI agree. Who do we need to get in agreement that printing the full CA is the best path forward?\nthe data is not omitted for security purposes, but to make the output more readable. see REDACTED is misleading... it should probably be \"elided\" or \"...\"\nyou can run to view full content\nthat's the crux of this issue - REDACTED is misleading.", "commid": "kubernetes_issue_61573", "tokennum": 520}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d801b95dd6099db09c59200bfe3796beafd992d73b09b769eed1e4056845101", "query": "func init() { sDec, _ := base64.StdEncoding.DecodeString(\"REDACTED+\") redactedBytes = []byte(string(sDec)) <ins> sDec, _ = base64.StdEncoding.DecodeString(\"DATA+OMITTED\") dataOmittedBytes = []byte(string(sDec)) </ins> } // IsConfigEmpty returns true if the config is empty.", "positive_passages": [{"docid": "doc-en-kubernetes-0c20cfda2a4143b97ca34085e4ba4933a2256b4cc12b09ed01e77387d3b1e642", "text": "However, pointed out that other \"long\" fields are still completely printed in plain text such as client certs, so I think we need to revisit the \"readability\" argument. What do you think?\nthey are not... client cert/key are elided in the same way for the same reason: something like \"++data+omitted++\" could be better If the intent of config view without --raw specified is to be readable (which it currently is), printing many extremely long fields isn't great\nHmm what about: I'm pretty sure that would give us a valid b64 string (8+12=20%4=0) and it would subtly hint that the data isn't a secret.\nOnly valid characters are . And adding a prefix from the certificate only complicates things. is a suitable usable option. I'll submit a PR to continue the discussion there.", "commid": "kubernetes_issue_61573", "tokennum": 195}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d9cf579c9e68813b246a605d6a561681be986a6feaf37f91b57a31f1b9652db", "query": "cachedService.service = service s.cache.set(namespacedName.String(), cachedService) case cache.Deleted: <del> err := s.ensureLBDeleted(service) </del> <ins> err := s.balancer.EnsureTCPLoadBalancerDeleted(s.loadBalancerName(service), s.zone.Region) </ins> if err != nil { return err, retryable }", "positive_passages": [{"docid": "doc-en-kubernetes-9fca6378f8b8df6d20b226b62d39deddc0dd6ba6166f0f70fb99239f64c63f5d", "text": "All of our external load balancer tests failed for the better part of a day due to the GCE project that our tests run in hitting its quota for number of target pools. While the target pools have been deleted, the fact that we hit our quota indicates that there must be a leak somewhere, and we need to plug it.\nFor reference, the previous issue was\nCould the leakage be related to ? The quota exhaustion occurred about 22 hrs after that.\nI'd guess that this is due to GetTCPLoadBalancer returning that the load balancer doesn't exist if the forwarding rule is gone, ignoring the target pool, while the service controller considers its deleting done if the cloud provider says that the load balancer doesn't exist. I that logic to the cloud provider because the other implementations of DeleteTCPLoadBalancer weren't/won't be idempotent in the sense of returning ok if the LB doesn't exist. To fix it, we'll either need to make sure all Delete implementations are idempotent and remove the Get call in the controller, or add a method along the lines of IsTCPLoadBalancerDeleted to ask the cloud provider whether all pieces of it have been completely cleaned up. We can't make GetTCPLoadBalancer check that because it's relied on to tell us whether or not the balancer is fully created.\nCopying over my commentary from on why the GKE e2e tests are leaking so many forwarding rules and target pools vs the GCE tests:\nIs there a way for the services test to wait for the service controller to clean up the external resources before finishing (without just doing a sleep)?\nNot without polling GCE directly for whether the resources still exist, although that may be worth it as a workaround. What would be perfect is that clean-up-all-cloud-provider-resources API method that we talked about a couple months ago.\nCan we not perhaps use GCE namespaces or projects as a cheap way of getting this here?\nI don't believe so. We can't use projects due to the fact that projects can't be programatically created (they're intended to be long-lived). I'm not aware of anything along the lines of a GCE namespace other than networks, which won't work because target pools and forwarding rules unfortunately don't seem to be scoped to networks.", "commid": "kubernetes_issue_7753", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d9cf579c9e68813b246a605d6a561681be986a6feaf37f91b57a31f1b9652db", "query": "cachedService.service = service s.cache.set(namespacedName.String(), cachedService) case cache.Deleted: <del> err := s.ensureLBDeleted(service) </del> <ins> err := s.balancer.EnsureTCPLoadBalancerDeleted(s.loadBalancerName(service), s.zone.Region) </ins> if err != nil { return err, retryable }", "positive_passages": [{"docid": "doc-en-kubernetes-d79b213781c20847fbb47c058c0afaba60ed2f1d9f5b51e77a0a4cda944c52e0", "text": "The target pool leak in the code might be fixed, but the forwarding rule + target pool leak from deleting GKE clusters too quickly is certainly still happening. Reopening for the sake of that half of the issue.\nCan we just add a short sleep to jenkins after the last test has run before it deletes anything?\nYes, you could add a sleep to Ginkgo's AfterEachSuite(): But I'd be concerned about what the upper bound on the sleep period is. Can we get the tests and code in sync with a 1 minute latency here? (e.g. if the controller garbage collects every 60 seconds, then the test only needs to sleep for 60 sec?) And add a BEEG comment to the test's sleep config noting that increasing the sleep time will not improve things, otherwise I'm pretty sure that someone noting flakes in this test in future will think \"maybe I should just increase the sleep period a little bit.\"\nActually, thinking about this a little more, it would be better to put the \"sleep\" logic in the k8s master teardown procedure (i.e. not in the e2e tests or in Jenkins), because otherwise users are going to run into the same resource leakage problems as we are. So master deletion blocks on cleanup of backend cloud resources.\nThere's no way to block master deletion from the master itself. The test framework (or user) just pulls the rug out from underneath the master. See\nRobby's right -- is the real solution to this, but until we have that the best we can do is to have the wait happen elsewhere. The options seem to be: GKE itself Ginkgo's post-testing logic Jenkins' teardown logic I don't like putting it in GKE, because arbitrarily slowing down our API makes for a poor experience for the majority of people that don't still have resources being deleted. I'm not eager to put it in Gingko either, since won't that sleep also take effect whenever anyone runs an e2e test locally against a dev cluster? Putting it in the Jenkins logic makes the most sense to me. I'll send a PR and cc you.\nWe may also want to change the kube-down logic to bring down the master and then nodes in parallel to both speed it up and more closely resemble GKE's teardown logic.\nI've deleted the old forwarding rules and target pools from the project.", "commid": "kubernetes_issue_7753", "tokennum": 530}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3d9cf579c9e68813b246a605d6a561681be986a6feaf37f91b57a31f1b9652db", "query": "cachedService.service = service s.cache.set(namespacedName.String(), cachedService) case cache.Deleted: <del> err := s.ensureLBDeleted(service) </del> <ins> err := s.balancer.EnsureTCPLoadBalancerDeleted(s.loadBalancerName(service), s.zone.Region) </ins> if err != nil { return err, retryable }", "positive_passages": [{"docid": "doc-en-kubernetes-6b81898435dc239c0c98669b4836ce5b1423be788127f142aa9eb15c198137cf", "text": "I'll periodically check to see whether anything is leaked after this point. I apologize if the deletions affected any running tests - everything looked to only be from GKE and parallel e2e runs.", "commid": "kubernetes_issue_7753", "tokennum": 42}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3dc125885958726fa1e684335d54312add4e2c1db78c2645b36de6ca09b2b7a4", "query": "sleep 5 <del> POD_LIST_1=$($KUBECFG '-template={{range.Items}}{{.Meta}} {{end}}' list pods) </del> <ins> POD_LIST_1=$($KUBECFG '-template={{range.Items}}{{.Name}} {{end}}' list pods) </ins> echo \"Pods running: ${POD_LIST_1}\" $KUBECFG stop redisSlaveController", "positive_passages": [{"docid": "doc-en-kubernetes-ee80683e4fc8d1f9267feeed119de250fd6d0c3f47227cc07d302319c50cf3e7", "text": "What happened: is a subdirectory of the btrfs subvolume . kubelet fails to start with the following error: What you expected to happen: kubelet starts normally and doesn't fail with an error message How to reproduce it (as minimally and precisely as possible): Install a system using btrfs as file system for / Create a sub-volume for /var Start kubelet (even in disconnected mode) Anything else we need to know?: This is a follow-up issue of and has been promoted to fatal from onward, before it was a warning PR to fix the issue is Environment: Kubernetes version (use ): forward Cloud provider or hardware configuration: both bare metal and virtual OS (e.g. from /etc/os-release): SUSE 12+ or openSUSE (Tumbleweed/Leap) Kernel (e.g. ): Install tools: SUSE/openSUSE rpm Others:\n/sig storage\nfixed by /close\nIf I may - adding some notes - it might be helpful for others, until I get the time to do some more detailed tests and report a bug. I still had issues with kubelet not starting, with the same error - (version 1.13.4) My btrfs setup is that btrfs root is mounted at /, then I have also a subvolume /var and in it a subvolume /var/lib. The issue for me I think comes from the fact that I do not have a flat btrfs setup () but a nested one, and as such, I have as a mountpoint ONLY the root directory. Manually adding a mount entry for /var (heh - I should probably have mounted /var/lib) in /etc/fstab made it work: /var btrfs rw,relatime,ssd,space_cache,subvolid=259,subvol=/var 0 0` Also, even without this additional \"intermediate\" mount point I think it should have been working. I wonder if in , the loop 'for !found {' isn't exiting a tiny bit too fast (without testing for the root mountpoint itself) . Maybe it should be something like:\nHas something changed in the code? Kubelet from kubernetes 1.20.1 is failing. Doing a mount as I described above fixes it.\nsee (open) and (closed) - apparently this was recently fixed (but isn't released yet).", "commid": "kubernetes_issue_65204", "tokennum": 533}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3e05af29702d148db4e6a1545065167531fa6aee515b87110ce4a03a3b79ca57", "query": "delete(objs, namespacedName) for _, w := range t.getWatches(gvr, ns) { <del> w.Delete(obj) </del> <ins> w.Delete(obj.DeepCopyObject()) </ins> } return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-097cec69e6f696ee556282ba1b462f036510b26986c7b0a8c41c6e03be57a385", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --Hello, Found a potential data race in testing. There is a test If we update it like this (we actually can do it ): If watcher updates received object we get a data race. No data race My suggestion: send copy of object here:\n/sig api-machinery\n/cc /triage accepted Do you remember if we fixed similar issues before?\nHi ,The code avoiding data race seems to already exist If you commented the code on above, the following test case will pass (because of data race), so I think there is no data race in the code : )\nHi Did you run my test with flag? Of course if I comment there will be data race. But let's take a look at: We store in and do with the same . So, watcher receives that is stored in map. we call we take the same from : Therefore, if watcher modifies received in another goroutine we have data race. Output:\nHi You're right ,thank you for solving my confusion. One solution could be to copy of , I will try to fix it.", "commid": "kubernetes_issue_103148", "tokennum": 276}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3e07fd49618edd8e3a295464c3f3471770a4315e885c875ebcb4c9a8abca3e56", "query": "}) It(\"should write files of various sizes, verify size, validate content\", func() { <del> fileSizes := []int64{1 * framework.MiB, 100 * framework.MiB} </del> <ins> fileSizes := []int64{fileSizeSmall, fileSizeMedium} </ins> err := testVolumeIO(f, cs, config, volSource, nil /*no secContext*/, testFile, fileSizes) Expect(err).NotTo(HaveOccurred()) })", "positive_passages": [{"docid": "doc-en-kubernetes-540712d0b27ee7f52d7d02bd3719013304c1ce42c6b5d8b93c3ee3671a9c1c7c", "text": "The \"Volume plugin streaming [Slow] NFS should write files of various sizes, verify size, validate content\" e2e test is failing on our 2k-node gce clusters (https://k8s-) with the following error: cc\nCould you take a look into it or reassign as apt? This is part of the correctness suite and large cluster tests are release-blocking.\n/assign\nis this run using the kubemark environment? I'll also take a look. It could be that the commands this test needs to execute may not work with kubemark. /assign\ncc\nNo, this is not kubemark. This is on a real 2000-node cluster.\nAlso all other volume-related e2e tests are passing, except this one.\nLooking at the log I see that the nfs test fails trying to verify the test file's content. The test exec's into the nfs client pod and executes: The return code from above is 127. The test then deletes the nfs client pod calling which works. The nfs-server pod is deleted in the AfterEach. For some reason the reported error is 137 but the returned err 127. The same command is exec'd for all of the tested storage plugins so not sure why it's failing just for nfs. Error 127 might be \"command not found\".\nThe other strange thing is that it's only failing in this suite and not the others.\nWhen I look at the kubelet log, I see the exec command coming through: I also see these suspicious kubelet soon afterwards: So I think the grep command is causing the node to run out of memory and get evicted. I think we can fix this either by: Making the grep command more memory efficient. I'm guessing it's reading the whole file into memory or, Make this test Serial so that it doesn't run in parallel with other pods, since it consumes a lot of memory.\nAn unrelated issue, is that the node allocatable feature didn't actually evict the pod. Instead this pod got a system OOM kill. /cc\nrelated to the memcg notifications, not node allocatable. Thanks!\nany theories why we see this only for the nfs-io tests, and not the glusterfs-io test for instance?\nthe gluster test didn't run on this in this suite.", "commid": "kubernetes_issue_51717", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3e07fd49618edd8e3a295464c3f3471770a4315e885c875ebcb4c9a8abca3e56", "query": "}) It(\"should write files of various sizes, verify size, validate content\", func() { <del> fileSizes := []int64{1 * framework.MiB, 100 * framework.MiB} </del> <ins> fileSizes := []int64{fileSizeSmall, fileSizeMedium} </ins> err := testVolumeIO(f, cs, config, volSource, nil /*no secContext*/, testFile, fileSizes) Expect(err).NotTo(HaveOccurred()) })", "positive_passages": [{"docid": "doc-en-kubernetes-fd4ca8cfd935058701597731533334687f2913bf0b9d409a83f3ac801f0182e1", "text": "I'm suspecting that the reason why we didn't see a problem with this test on other suites is that the load could be higher here. I've asked to see if we can reduce the memory usage of the grep call.\npointed out that there are no newlines in the generated file, so when grep is called it could buffer the entire file in memory. Adding a newline at the end of the dd input file should do it.\n/priority critical-urgent\n[MILESTONENOTIFIER] Milestone Labels Complete Issue label settings: sig/scalability sig/storage: Issue will be escalated to these SIGs if needed. priority/critical-urgent: Never automatically move out of a release milestone; continually escalate to contributor and SIG through all available channels. kind/bug: Fixes a bug discovered during the current release. <detailsAdditional instructions available <a href=\"\"here</a</details\nIt seems like even if the generated file is broken up by newlines, grep could still use on the order of hundreds of MB of memory for a 100MiB file (even with the -m1 and -F options). We could check the file line by line, but it would take a long time. A better solution would be to check the MD5 file hash. It's fast and uses little memory. The expected hashes will be hard-coded into the test, and if different file sizes are in the future, a hash needs to be computed and as well.\nThanks a lot for fixing this!\nRef", "commid": "kubernetes_issue_51717", "tokennum": 322}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3e474959bf65270473e4e43fabe22b08ac9be8145c1bf55d0993f4c76967fab5", "query": "<ins> /* Copyright 2016 The Kubernetes Authors All rights reserved. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package codeinspector import ( \"fmt\" \"go/ast\" \"go/parser\" \"go/token\" \"io/ioutil\" \"strings\" \"unicode\" ) // GetPublicFunctions lists all public functions (not methods) from a golang source file. func GetPublicFunctions(filePath string) ([]string, error) { var functionNames []string // Create the AST by parsing src. fset := token.NewFileSet() // positions are relative to fset f, err := parser.ParseFile(fset, filePath, nil, 0) if err != nil { return nil, fmt.Errorf(\"failed parse file to list functions: %v\", err) } // Inspect the AST and print all identifiers and literals. ast.Inspect(f, func(n ast.Node) bool { var s string switch x := n.(type) { case *ast.FuncDecl: s = x.Name.Name // It's a function (not method), and is public, record it. if x.Recv == nil && isPublic(s) { functionNames = append(functionNames, s) } } return true }) return functionNames, nil } // isPublic checks if a given string is a public function name. func isPublic(myString string) bool { a := []rune(myString) a[0] = unicode.ToUpper(a[0]) return myString == string(a) } // GetSourceCodeFiles lists golang source code files from directory, excluding sub-directory and tests files. func GetSourceCodeFiles(dir string) ([]string, error) { files, err := ioutil.ReadDir(dir) if err != nil { return nil, err } var filenames []string for _, file := range files { if strings.HasSuffix(file.Name(), \".go\") && !strings.HasSuffix(file.Name(), \"_test.go\") { filenames = append(filenames, file.Name()) } } return filenames, nil } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-3229e3f28f67afa9ddea85d9d31a50803c261e0ae30f76f950060d1790215e64", "text": "I just noticed you forgot to register the image locality priority function in in I also missed it when I reviewed your PR. I have fixed this in . But it would be great if you could figure out a mechanism that would ensure that all predicate/priority functions that are tested (you can assume they will always live under ) are registered, and fail the test if not. That will allow us to prevent this mistake in the future.\nThanks! Will fix this soon!\nSeems need to wait for in before I send PR? Otherwise this test will always fail ...", "commid": "kubernetes_issue_21236", "tokennum": 114}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3e708e0786301606b2891ccc96a71d9fb3cf156b4bfd5e8f74ffeb0840ddfc86", "query": "podSpec.EphemeralContainers = nil } <del> if (!utilfeature.DefaultFeatureGate.Enabled(features.VolumeSubpath) || !utilfeature.DefaultFeatureGate.Enabled(features.VolumeSubpathEnvExpansion)) && !subpathExprInUse(oldPodSpec) { // drop subpath env expansion from the pod if either of the subpath features is disabled and the old spec did not specify subpath env expansion </del> <ins> if !utilfeature.DefaultFeatureGate.Enabled(features.VolumeSubpath) && !subpathExprInUse(oldPodSpec) { // drop subpath env expansion from the pod if subpath feature is disabled and the old spec did not specify subpath env expansion </ins> VisitContainers(podSpec, AllContainers, func(c *api.Container, containerType ContainerType) bool { for i := range c.VolumeMounts { c.VolumeMounts[i].SubPathExpr = \"\"", "positive_passages": [{"docid": "doc-en-kubernetes-a166ddd65322b2b4c2d8cbe35891249f4d033568413f3b77fc1f46ee1d1ee8b8", "text": "/kind cleanup /sig storage /sig node Description: Feature gate VolumeSubpathEnvExpansion was GA in 1.17 and is marked for removal in 1.19 Related Issues: GA Release:\n/assign\n/cc", "commid": "kubernetes_issue_89519", "tokennum": 48}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3e7d33285515beb71f378ee4f904a5296c7bf1f8132cad4902eb91b856a3e553", "query": "}, { \"ImportPath\": \"github.com/json-iterator/go\", <del> \"Rev\": \"f2b4162afba35581b6d4a50d3b8f34e33c144682\" </del> <ins> \"Rev\": \"ab8a2e0c74be9d3be70b3184d9acc634935ded82\" </ins> }, { \"ImportPath\": \"github.com/mailru/easyjson/buffer\",", "positive_passages": [{"docid": "doc-en-kubernetes-0d085a3ee589d9a38ade8c650d9534110265a809ec41b82f41ce81cebea870e6", "text": "is a library yet is is instead of release tag. Please consider vendoring by tag whenever possible. Thanks.\nWe vendored it that way because the commit that fixed a bug (which we needed to be fixed and vendored back in) was This was merged on June 13. The release 1.1.4 () was released on July 1. If we want to update it to 1.1.4, I believe it should be fine. Between the commit we have vendored right now and the latest release, there are only three commits: adds tests merges (?) the case-sensitive fix - I'm not really sure what this commit is doing. fixes renaming when naming strategy is set (looks fine). Also, there are also no licensing changes. opinions?\n/sig api-machinery\n+1 to what said, it was a fire drill and 1.11.0 release was in trouble. Though in hind sight, we should have opened a issue to track that. something better to do next time. cc\nI'm indifferent to updating this. I'm okay with moving up if it doesn't break anything, or I'm fine with leaving things as is. We don't require deps to match semver. We can version out any commit in a deps tree, as we rely on our vendored copy.\nIt is always a good idea to match semver and it should be a default policy. Even if it doesn't matter to you, it should, because it is a best practice. Moreover downstream it matters much more as dependencies may be un-vendored in favour of tested re-usable packages.\n/cc\nIssues 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\nSomeone please take care of this or bot will eventually close this valid issue without action...\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_66422", "tokennum": 501}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3e7d33285515beb71f378ee4f904a5296c7bf1f8132cad4902eb91b856a3e553", "query": "}, { \"ImportPath\": \"github.com/json-iterator/go\", <del> \"Rev\": \"f2b4162afba35581b6d4a50d3b8f34e33c144682\" </del> <ins> \"Rev\": \"ab8a2e0c74be9d3be70b3184d9acc634935ded82\" </ins> }, { \"ImportPath\": \"github.com/mailru/easyjson/buffer\",", "positive_passages": [{"docid": "doc-en-kubernetes-3d634ec524d1253e3e5f3f0b99b6d74925e6b15b79d6d989e49b255bf837eee0", "text": "/lifecycle rotten\n/lifecycle rotten\n/remove-lifecycle rotten PR open (thanks,\noops! sorry, I meant to remove it. thanks!\nThanks.\nplease do feel free to open issues/prs of this sort early in the release cycle, so we can work through things needed well before the milestones/freeze etc. we are getting some heat about updating dependencies and we kind of settled on some guidelines here: if you think that needs updating, we could definitely debate that as well :) (on a PR against that doc)\nit have nothing to do with release cycle or justification for upgrade if/when dependency has been vendored incorrectly. It is basically a vendoring bug. No debate is necessary although that kind of issues usually meet some resistance and even hostility here... Bugs are filed when they are discovered, regardless of release cycle. It would be wrong to sit on the bug without reporting it in order to synchronise with release cycle.", "commid": "kubernetes_issue_66422", "tokennum": 200}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3e94399ce093f5d1fe1c51420304f430ba5eec86f56a6d0075a84d518ceff104", "query": "} } <ins> // estimateMaxStringLengthPerRequest estimates the maximum string length (in characters) // that has a set of enum values. // The result of the estimation is the length of the longest possible value. func estimateMaxStringEnumLength(s Schema) int64 { var maxLength int64 for _, v := range s.Enum() { if s, ok := v.(string); ok && int64(len(s)) > maxLength { maxLength = int64(len(s)) } } return maxLength } </ins> // estimateMaxArrayItemsPerRequest estimates the maximum number of array items with // the provided minimum serialized size that can fit into a single request. func estimateMaxArrayItemsFromMinSize(minSize int64) int64 {", "positive_passages": [{"docid": "doc-en-kubernetes-d87f35a9862b77934b500147b1ec4bb0e958c531e2fdcae282b21499e2f51131", "text": "pointed out to me that a CEL x-kubernetes-validations rule in a CRD was hitting the estimated cost limit when performing a simple \"string has prefix\" check on an en enum field. Putting a limit in the OpenAPI of the enum string field fixed the problem, but having to add a limit like this is counter-intuitive and unnecessary, since the allowed enum values already make the max allowed length obvious. The apiserver automatically computes the max length of an enum as the length of the longest allowed enum value. I believe we already refuse evaluate CEL rules on values that fail OpenAPI value validation, since we rely in the value validations to establish all length limits. I haven't tested it locally, but something like this should work (given enough nested arrays): As a workaround, one can manually set on the string enum, e.g.: 25+ All No response No response No response No response\n/sig api-machinery /triage accepted /assign\n/assign\nI wasn't sure if we special-cased the maxLength / maxItems / maxProperties failures, or if all openapi validation had to pass before we started messing with CEL evaluation\nit looks like we currently special-case specific openapi errors that short-circuit CEL validation, I'm not sure an enum validation failure would currently prevent evaluation:\nThe enum err is converted to () error which is not short-circuit here. But for defaulting case, all error would be short-circuit. I would suggest to add error into the blockingErr list to short-circuit CEL validation. Would this make sense?\nyeah, that sounds good if we're going to rely on it to catch things that are longer than the maximum length enum value", "commid": "kubernetes_issue_119511", "tokennum": 383}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3e96c220b5b5072c4585bf833eb74fd5f8444807684bd6bbc0ffdb95c6dfb606", "query": "All               bool Record            bool ChangeCause       string <del> Local             bool </del> Cmd               *cobra.Command Limits               string", "positive_passages": [{"docid": "doc-en-kubernetes-f45c12318e35043c65362c27e361ee13adfef369e183f2b4f0557c11353bd9e9", "text": "from https://k8s-\nReally suspect this is\nThis is putting us into test-go post-commit run is broken\ncc:\nmarked this p0 - if a fix isn't easy let's try to identify what introduced this and revert.\nThis flake on: 2016-10-30 07:19 PDT First instance: : It is flaking frequently, blocking PRs from getting merged, and slowing the submit queue ( at 75%). As on-call, I'm going to try and identify the cluprit and revert. Can use all help in doing so.\ncan you investigate whether your additional tests could cause this (by breaking the deployment of those pods, for instance) , Saad Ali wrote:\nPR looks most suspect to me. It mucked with , and the errors we are seeing in each of the failures is related to : That PR was merged at Oct 30, 2016, 6:18 AM PDT and the first flake in was at Oct 30, 2016, 7:19 AM PDT. Thoughts? CC\nI'm going to initiate a revert of to see if that fixes the issue\nIMO we can just change the flaky test to not get pods but some other resources, such as deployments. We can't really expect to clean up pods immediately.\nI'm going to proceed with revert (). Please feel free to send a follow up PR to handle this more gracefully.\nGoing to leave this opened until we have a few hours of runs with the revert. Want to verify, with some degree of certainty, that the revert took care of this flake.\nWe had 15 green runs of in a row. Considering this flake fixed.", "commid": "kubernetes_issue_35898", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3ea8e6a00150e14725ff3512f952ca375b1bb21babbe0d436c73d54e0d31ef44", "query": "w.Flush() if trackingWriter.Written == 0 && !o.IgnoreNotFound && len(allErrs) == 0 { // if we wrote no output, and had no errors, and are not ignoring NotFound, be sure we output something <del> noResourcesFoundFormat := fmt.Sprintf(\"No resources found in %s namespace.\", o.Namespace) fmt.Fprintln(o.ErrOut, noResourcesFoundFormat) </del> <ins> if !o.AllNamespaces { fmt.Fprintln(o.ErrOut, fmt.Sprintf(\"No resources found in %s namespace.\", o.Namespace)) } else { fmt.Fprintln(o.ErrOut, fmt.Sprintf(\"No resources found\")) } </ins> } return utilerrors.NewAggregate(allErrs) }", "positive_passages": [{"docid": "doc-en-kubernetes-c7d12b68f0527cb4211e1e8a31ccfe4349122b3159e0a706002c6b019cbf11bb", "text": "What happened: When running and no resource is found, kubectl returns , which is confusing, since we're trying to list instances of a cluster-scoped resource. What you expected to happen: When listing cluster-scoped resources, the message should either be or How to reproduce it (as minimally and precisely as possible): (assuming there are no ; can also try or similar) Environment: Kubernetes version (use ):\n/sig cli\n/reopen Reopening, because did not fix this issue. It only fixed , which also produced a misleading message, but that's not what this issue is about. This issue is about cluster-scoped resources, not about listing namespaced resources in all namespaces. Output of kubectl get with the changes from included:\nReopened this issue. <detailsIn response to : /reopen </details\n/assign\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nClosing 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\n/reopen This seems to be an error in the get code for kubectl, it looks like it tries to figure out if all the requested resources are namespaced and only then return specify the namespace in the output. This seems to be happening when we have only cluster-wide resources.", "commid": "kubernetes_issue_80855", "tokennum": 508}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3ea8e6a00150e14725ff3512f952ca375b1bb21babbe0d436c73d54e0d31ef44", "query": "w.Flush() if trackingWriter.Written == 0 && !o.IgnoreNotFound && len(allErrs) == 0 { // if we wrote no output, and had no errors, and are not ignoring NotFound, be sure we output something <del> noResourcesFoundFormat := fmt.Sprintf(\"No resources found in %s namespace.\", o.Namespace) fmt.Fprintln(o.ErrOut, noResourcesFoundFormat) </del> <ins> if !o.AllNamespaces { fmt.Fprintln(o.ErrOut, fmt.Sprintf(\"No resources found in %s namespace.\", o.Namespace)) } else { fmt.Fprintln(o.ErrOut, fmt.Sprintf(\"No resources found\")) } </ins> } return utilerrors.NewAggregate(allErrs) }", "positive_passages": [{"docid": "doc-en-kubernetes-1027112ca48a1952e66a5a235f8ecc4ced7e393fc603d44340ff46ba509184a5", "text": "You can't reopen an issue/PR unless you authored it or you are a collaborator. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nClosing 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", "commid": "kubernetes_issue_80855", "tokennum": 227}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3ebddb250af4e3be9e84dac9f3f3534464994edef726cc88f9b1beb3d00a50f9", "query": "podCopy := pod.DeepCopy() // NominatedNodeName is updated only if we are trying to set it, and the value is // different from the existing one. <del> if !podutil.UpdatePodCondition(&podCopy.Status, condition) && pod.Status.NominatedNodeName == nominatedNode { </del> <ins> if !podutil.UpdatePodCondition(&podCopy.Status, condition) && (len(nominatedNode) == 0 || pod.Status.NominatedNodeName == nominatedNode) { </ins> return nil } <del> podCopy.Status.NominatedNodeName = nominatedNode </del> <ins> if nominatedNode != \"\" { podCopy.Status.NominatedNodeName = nominatedNode } </ins> return patchPod(client, pod, podCopy) }", "positive_passages": [{"docid": "doc-en-kubernetes-0c3eca7956c73a24f455c71a58b712ce183e874d4a3e3eb9b913120c8a8ac10c", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: Conformance - GCE - master (ci-kubernetes-gce-conformance-latest) Which test(s) are failing: [sig-scheduling] SchedulerPreemption [Serial] PreemptionExecutionPath runs ReplicaSets to verify preemption running path [Conformance]Changes Since when has it been failing: 2020-06-08 22:27 PDT Testgrid link: Reason for failure: Regression by Anything else we need to know: /sig scheduling /priority critical-urgent\ncc/ /assign", "commid": "kubernetes_issue_91972", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3efd82158fb67c595278564e8dfeb1bbaf302933e6adc8d396834f3c58a8391f", "query": "<ins> <!-- BEGIN MUNGE: UNVERSIONED_WARNING --> <!-- BEGIN STRIP_FOR_RELEASE --> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <h2>PLEASE NOTE: This document applies to the HEAD of the source tree</h2> If you are using a released version of Kubernetes, you should refer to the docs that go with that version. <strong> The latest 1.0.x release of this document can be found [here](http://releases.k8s.io/release-1.0/docs/user-guide/kubectl-overview.md). Documentation for other releases can be found at [releases.k8s.io](http://releases.k8s.io). </strong> -- <!-- END STRIP_FOR_RELEASE --> <!-- END MUNGE: UNVERSIONED_WARNING --> # kubectl overview **Table of Contents** - [kubectl overview](#kubectl-overview) - [Overview](#overview) - [Common Operations](#common-operations) - [Kubectl Operations](#kubectl-operations) - [Resource Types](#resource-types) This overview is intended for anyone who wants to use `kubectl` command line tool to interact with Kubernetes cluster. Please remember that it is built for quick started with `kubectl`; for complete and detailed information, please refer to [kubectl](kubectl/kubectl.md). TODO: auto-generate this file to stay up with `kubectl` changes. Please see [#14177](https://github.com/kubernetes/kubernetes/pull/14177). ## Overview `kubectl` controls the Kubernetes cluster manager. The synopsis is: ``` kubectl [command] [TYPE] [NAME] [flags] ``` This specifies: - `command` is a certain operation performed on a given resource(s), such as `create`, `get`, `describe`, `delete` etc. - `TYPE` is the type of resource(s). Both singular and plural forms are accepted. For example, `node(s)`, `namespace(s)`, `pod(s)`, `replicationcontroller(s)`, `service(s)` etc. - `NAME` is the name of resource(s). `TYPE NAME` can be specified as `TYPE name1 name2` or `TYPE/name1 TYPE/name2`. `TYPE NAME` can also be specified by one or more file arguments: `-f file1 -f file2 ...`, [use YAML rather than JSON](config-best-practices.md) since YAML tends to be more user-friendly for config. - `flags` are used to provide more control information when running a command. For example, you can use `-s` or `--server` to specify the address and port of the Kubernetes API server. Command line flags override their corresponding default values and environment variables. [Use short flags sparingly, only for the most frequently used options](../devel/kubectl-conventions.md). Please use `kubectl help [command]` for detailed information about a command. Please refer to [kubectl](kubectl/kubectl.md) for a complete list of available commands and flags. ## Common Operations For explanation, here I gave some mostly often used `kubectl` command examples. Please replace sample names with actual values if you would like to try these commands. 1. `kubectl create` - Create a resource by filename or stdin // Create a service using the data in example-service.yaml. $ kubectl create -f example-service.yaml // Create a replication controller using the data in example-controller.yaml. $ kubectl create -f example-controller.yaml // Create objects whose definitions are in a directory. This looks for config objects in all .yaml, .yml, and .json files in <directory> and passes them to create. $ kubectl create -f <directory> 2. `kubectl get` - Display one or many resources // List all pods in ps output format. $ kubectl get pods // List all pods in ps output format with more information (such as node name). $ kubectl get pods -o wide // List a single replication controller with specified name in ps output format. You can use the alias 'rc' instead of 'replicationcontroller'. $ kubectl get replicationcontroller <rc-name> // List all replication controllers and services together in ps output format. $ kubectl get rc,services 3. `kubectl describe` - Show details of a specific resource or group of resources // Describe a node $ kubectl describe nodes <node-name> // Describe a pod $ kubectl describe pods/<pod-name> // Describe all pods managed by the replication controller <rc-name> // (rc-created pods get the name of the rc as a prefix in the pod the name). $ kubectl describe pods <rc-name> 4. `kubectl delete` - Delete resources by filenames, stdin, resources and names, or by resources and label selector // Delete a pod using the type and name specified in pod.yaml. $ kubectl delete -f pod.yaml // Delete pods and services with label name=<label-name>. $ kubectl delete pods,services -l name=<label-name> // Delete all pods $ kubectl delete pods --all 5. `kubectl exec` - Execute a command in a container // Get output from running 'date' from pod <pod-name>, using the first container by default. $ kubectl exec <pod-name> date // Get output from running 'date' in <container-name> from pod <pod-name>. $ kubectl exec <pod-name> -c <container-name> date // Get an interactive tty and run /bin/bash from pod <pod-name>, using the first container by default. $ kubectl exec -ti <pod-name> /bin/bash 6. `kubectl logs` - Print the logs for a container in a pod. // Returns snapshot of logs from pod <pod-name>. $ kubectl logs <pod-name> // Starts streaming of logs from pod <pod-name>, it is something like 'tail -f'. $ kubectl logs -f <pod-name> ## Kubectl Operations The following table describes all `kubectl` operations and their general synopsis: Operation       | Synopsis\t|       Description -------------------- | -------------------- | -------------------- annotate\t| `kubectl annotate [--overwrite] (-f FILENAME | TYPE NAME) KEY_1=VAL_1 ... KEY_N=VAL_N [--resource-version=version]` | Update the annotations on a resource api-versions\t| `kubectl api-versions` | Print available API versions attach\t\t| `kubectl attach POD -c CONTAINER` | Attach to a running container cluster-info\t| `kubectl cluster-info` | Display cluster info config\t\t| `kubectl config SUBCOMMAND` | Modifies kubeconfig files create\t\t| `kubectl create -f FILENAME` | Create a resource by filename or stdin delete\t\t| `kubectl delete ([-f FILENAME] | TYPE [(NAME | -l label | --all)])` | Delete resources by filenames, stdin, resources and names, or by resources and label selector describe\t| `kubectl describe (-f FILENAME | TYPE [NAME_PREFIX | -l label] | TYPE/NAME)` | Show details of a specific resource or group of resources edit\t\t| `kubectl edit (RESOURCE/NAME | -f FILENAME)` | Edit a resource on the server exec\t\t| `kubectl exec POD [-c CONTAINER] -- COMMAND [args...]` | Execute a command in a container expose\t\t| `kubectl expose (-f FILENAME | TYPE NAME) [--port=port] [--protocol=TCP|UDP] [--target-port=number-or-name] [--name=name] [----external-ip=external-ip-of-service] [--type=type]` | Take a replication controller, service or pod and expose it as a new Kubernetes Service get\t\t| `kubectl get [(-o|--output=)json|yaml|wide|go-template=...|go-template-file=...|jsonpath=...|jsonpath-file=...] (TYPE [NAME | -l label] | TYPE/NAME ...) [flags]` | Display one or many resources label\t\t| `kubectl label [--overwrite] (-f FILENAME | TYPE NAME) KEY_1=VAL_1 ... KEY_N=VAL_N [--resource-version=version]` | Update the labels on a resource logs\t\t| `kubectl logs [-f] [-p] POD [-c CONTAINER]` | Print the logs for a container in a pod namespace\t| `kubectl namespace [namespace]` | SUPERSEDED: Set and view the current Kubernetes namespace patch\t\t| `kubectl patch (-f FILENAME | TYPE NAME) -p PATCH` | Update field(s) of a resource by stdin port-forward\t| `kubectl port-forward POD [LOCAL_PORT:]REMOTE_PORT [...[LOCAL_PORT_N:]REMOTE_PORT_N]` | Forward one or more local ports to a pod proxy\t\t| `kubectl proxy [--port=PORT] [--www=static-dir] [--www-prefix=prefix] [--api-prefix=prefix]` | Run a proxy to the Kubernetes API server replace\t\t| `kubectl replace -f FILENAME` | Replace a resource by filename or stdin rolling-update\t| `kubectl rolling-update OLD_CONTROLLER_NAME ([NEW_CONTROLLER_NAME] --image=NEW_CONTAINER_IMAGE | -f NEW_CONTROLLER_SPEC)` | Perform a rolling update of the given ReplicationController run\t\t| `kubectl run NAME --image=image [--env=\"key=value\"] [--port=port] [--replicas=replicas] [--dry-run=bool] [--overrides=inline-json]` | Run a particular image on the cluster scale\t\t| `kubectl scale [--resource-version=version] [--current-replicas=count] --replicas=COUNT (-f FILENAME | TYPE NAME)` | Set a new size for a Replication Controller stop\t\t| `kubectl stop (-f FILENAME | TYPE (NAME | -l label | --all))` | Deprecated: Gracefully shut down a resource by name or filename version\t\t| `kubectl version` | Print the client and server version information ## Resource Types The `kubectl` supports the following resource types, and their abbreviated aliases: Resource Type\t| Abbreviated Alias -------------------- | -------------------- componentstatuses\t|\tcs events\t|\tev endpoints\t|\tep horizontalpodautoscalers\t|\thpa limitranges\t|\tlimits nodes\t|\tno namespaces\t|\tns pods\t|\tpo persistentvolumes\t|\tpv persistentvolumeclaims\t|\tpvc resourcequotas\t|\tquota replicationcontrollers\t|\trc daemonsets\t|\tds services\t|\tsvc <!-- BEGIN MUNGE: GENERATED_ANALYTICS --> [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl-overview.md?pixel)]() <!-- END MUNGE: GENERATED_ANALYTICS --> </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-ff400dc6754846fd0992db1028d6e5a3aef2be3cc27ba2c2792aa3874bf81494", "text": "Something like: cc\ncc\n- Can you please look at this issue since you're recently working on documentation?\nthanks for the reminder. I will take care of it.", "commid": "kubernetes_issue_11814", "tokennum": 34}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3efdca3d7f3f8a011b4c9c0e64c2312418fac47ef7639a403c56b324c2c90619", "query": "memoryUsage, err := strconv.ParseFloat(lines[0], 64) framework.ExpectNoError(err) <ins> var rssToken, inactiveFileToken string if isCgroupV2 { // Use Anon memory for RSS as cAdvisor on cgroupv2 // see https://github.com/google/cadvisor/blob/a9858972e75642c2b1914c8d5428e33e6392c08a/container/libcontainer/handler.go#L799 rssToken = \"anon\" inactiveFileToken = \"inactive_file\" } else { rssToken = \"total_rss\" inactiveFileToken = \"total_inactive_file\" } </ins> var totalInactiveFile float64 for _, line := range lines[1:] { tokens := strings.Split(line, \" \") <del> if tokens[0] == \"total_rss\" { </del> <ins> if tokens[0] == rssToken { </ins> rss, err = strconv.ParseFloat(tokens[1], 64) framework.ExpectNoError(err) } <del> if tokens[0] == \"total_inactive_file\" { </del> <ins> if tokens[0] == inactiveFileToken { </ins> totalInactiveFile, err = strconv.ParseFloat(tokens[1], 64) framework.ExpectNoError(err) }", "positive_passages": [{"docid": "doc-en-kubernetes-0c07e91eb7d66ee92c3b6d05f523cece58039dffcf1123c44ba752c30922deab", "text": "N/A [sig-node] NodeProblemDetector: N/A https://prow- Not cgroupv2 compatible when access cpu and memory data\n/sig node\nHi, can i work on this ?\nSure. Thanks\n/assign\n/triage accepted\n/priority important-soon\n/cc\nare you still working on this? Were you able to setup environment to repro the test failure? Let us know if you need any help. Thanks!\nSorry for the delay, I followed the wrong guide and ended up getting stuck. But now I have managed to set it up. Please give me few more days to work on it.\nThanks Feel free to reach out here or on slack if you need any help, thanks for working on this!\n/retitle Make nodeproblemdetector test cgroupv2 compatible\nFailing job:\nTestgrid:", "commid": "kubernetes_issue_105178", "tokennum": 180}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3f2345f0f9e0c7e497537e977ca89af11fa266b9e9fe1b2eec343b4dacf05b3d", "query": "// How long to wait for a log pod to be displayed const podLogTimeout = 45 * time.Second <del> // utility function for gomega Eventually func getPodLogs(c *client.Client, namespace, podName, containerName string) (string, error) { logs, err := c.Get().Resource(\"pods\").Namespace(namespace).Name(podName).SubResource(\"log\").Param(\"container\", containerName).Do().Raw() if err != nil { return \"\", err } if err == nil && strings.Contains(string(logs), \"Internal Error\") { return \"\", fmt.Errorf(\"Internal Error\") } return string(logs), err } </del> var _ = Describe(\"Downward API volume\", func() { f := NewFramework(\"downward-api\") It(\"should provide podname only [Conformance]\", func() {", "positive_passages": [{"docid": "doc-en-kubernetes-cf37b0ab7a08d0e2457507bc271b1cb7d1e13fbaee3773971363bc32ae71b35b", "text": "We are running heapster, dns server, kube-proxy etc. in kube-system namespace. Some e2e tests try to make sure all those kube-system pods are at ready state before firing the real tests, others just simply ingore them. But both cases might cause e2e flakiness when some of those kube-system containers are in crashloop, for example, for heapster crashloop, for influxdb crashloop, etc. When such cases happen, the developer doesn't have much information on why since the nodes might be teared down. We should watch those kube-system pods, and onContainerFailure, we should collect the related logs. One simple way is using kubectl logs <Pod<Container--previous cc/\nis this related enough to and that you can bundle it in?\nThe logs from the pods should be retrieved via the api server. This is different from the kubelet logs. I'll upload a PR for this.\nGreat job It will be very helpful for debugging.", "commid": "kubernetes_issue_20099", "tokennum": 229}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3f6102d1b028599c1511ce0cad7d949721237f0a591149ec2e02ea6510931d03", "query": "], library = \":go_default_library\", deps = [ <ins> \"//federation/apis/federation:go_default_library\", </ins> \"//federation/apis/federation/v1beta1:go_default_library\", \"//federation/client/clientset_generated/federation_clientset/fake:go_default_library\", \"//pkg/api:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-f29982137c07dadb3e257d7391e0d9b7bfd5f1ce8fdca72f798301cc159728a0", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: After labeling clusters in a Federation, when you type the field is empty. What you expected to happen: The fiels should contain information about the labels in the cluster How to reproduce it (as minimally and precisely as possible): a federation control pane in any Cloud Provider and any DNS provider your cluster: info aboyut the cluster with the flag: Note: if you describe it, you see the labels being : Environment: Kubernetes version (use ): 1.8.0 Cloud provider or hardware configuration**: anyone OS (e.g. from /etc/os-release): Ubuntu 16.04 Kernel (e.g. ): Linux Install tools: curl Others:\n/sig multicluster\nI'm working on it.", "commid": "kubernetes_issue_53729", "tokennum": 179}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3f9cf48897560087502c9fc20145c6bd87578c02d4e203879f6d77ab89a391dd", "query": "glog.Infof(\"Running tests for APIVersion: %s\", apiVersion) <del> manifestURL := ServeCachedManifestFile() apiServerURL, configFilePath := startComponents(manifestURL, apiVersion) </del> <ins> firstManifestURL := ServeCachedManifestFile(testPodSpecFile) secondManifestURL := ServeCachedManifestFile(testManifestFile) apiServerURL, configFilePath := startComponents(firstManifestURL, secondManifestURL, apiVersion) </ins> // Ok. we're good to go. glog.Infof(\"API Server started on %s\", apiServerURL)", "positive_passages": [{"docid": "doc-en-kubernetes-56027fa26048aea64718f2bd7d7c5d6f58ddca1472c1fc738c03141b6dea3ad6", "text": "Currently it assumes it can read ContainerManifest - it should try both\nWhy not hold on this until we have Kubelet-read-Pod in?\nAlso the HTTP source has the same problem.\nIt should read Pod. Changed the title.\nIdeally, I'd like all Pods created directly via Kubelet to be to etcd and surfaced via the API. If updates are made via the API, I'd like those to propagate back to the node. We can discuss whether the config file should be updated or ignored. At some point, I'd like Kubelet to persistently cache pods received from the apiserver, perhaps by just writing them all out as config files.\nis the issue to sync local pods back to apiserver.\nthis is somewhat related to other issues we talked about.\nDetail: We want locally specified pods to be able to use YAML config files, but we also want to rip YAML out of the API server . The config-file behavior should be as similar to the kubectl experience. Kubelet could use parts of the kubectl library to translate YAML to JSON. Vision: Eventually, I'd like Kubelet to use the apiserver library and support exactly the same Pod API as the master, at which time I'd like kubectl be able to create pods directly on Kubelets, as well as reading from config files. I also expect to have a per-node controller . I'd like to be able to use the per-node controller to update pods started via config files (or direct kubectl-kubelet pods), overriding those original files. For availability and self-hosting, we'll eventually need local checkpointing , ideally just using serialized JSON for each object. If Kubelet used apiserver, this could be done using a custom registry implementation.\nI think that is a prerequisite for it.\nIf noone picks it up, I'm going to start working on it tomorrow.\nthanks, wojtek-t\nfixed it for http channel", "commid": "kubernetes_issue_3372", "tokennum": 445}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3feb39c3f7e2878793e9de39945777fbfef3e77605194d0e74efb65b3f0775f1", "query": "// buildELBSecurityGroupList returns list of SecurityGroups which should be // attached to ELB created by a service. List always consist of at least <del> // 1 member which is an SG created for this service. Extra groups can be </del> <ins> // 1 member which is an SG created for this service or a SG from the Global config. Extra groups can be </ins> // specified via annotation func (c *Cloud) buildELBSecurityGroupList(serviceName types.NamespacedName, loadBalancerName, annotation string) ([]string, error) { var err error", "positive_passages": [{"docid": "doc-en-kubernetes-d6a2e132f72678770d8d41e08acf9f7359a4b887e33d930dbbc18ea7ecc9db7e", "text": "/kind bug What happened: When setting an elbSecurityGroup in for AWS, and deploying multiple services with differing ports, then the security group rules flap in AWS, causing services to become inaccessible (only one will be correctly configured at a time). What you expected to happen: I expect that the configured elbSecurityGroup's rules will not be touched at all. It must be pre-configured to permit access. Alternatively, all ports for all services are queried and managed together. How to reproduce it (as minimally and precisely as possible): See above. Anything else we need to know?: Most people are not running large clusters which may hit the AWS limits, so they won't use this option, nor see this issue. Environment: Kubernetes version (use ): 1.7.1 Cloud provider or hardware configuration**: AWS OS (e.g. from /etc/os-release): CentOS 7 Kernel (e.g. ): 4.10.13-1-ARCH Install tools: Custom Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig aws\nThis is fixed by", "commid": "kubernetes_issue_50105", "tokennum": 331}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3ff1b8d08100a08f3d19a06321feeddf479f63a137fb9563a2d32342ce18fd1e", "query": "if !apierrors.IsBadRequest(err) { t.Errorf(\"expected HTTP status: BadRequest, got: %#v\", apierrors.ReasonForError(err)) } <del> if err.Error() != expectedError { </del> <ins> if !strings.Contains(err.Error(), expectedError) { </ins> t.Errorf(\"expected %#v, got %#v\", expectedError, err.Error()) } }", "positive_passages": [{"docid": "doc-en-kubernetes-984aaf2876c4d4651f6765b291626bccfb7d6364087d7ebb11c97e2832c59ee5", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Below k8s UT fail when run with master-golang. TestCheckpointStateRestore/RestorecheckpointwithinvalidJSON error:=== RUN TestCheckpointStateRestore/RestorecheckpointwithinvalidJSON I1124 05:38:14. ] [cpumanager] initializing new in-memory state store unexpected error while creatng checkpointState: could not restore state from checkpoint: json: unexpected end of JSON input, please drain this node and delete the CPU manager checkpoint file \"/tmp/cpumanagerstatetest479660663/cpumanagercheckpointtest\" before restarting Kubelet --- FAIL: TestCheckpointStateRestore/RestorecheckpointwithinvalidJSON (0.00s) TestStrategicMergePatchInvalid error:=== RUN TestStrategicMergePatchInvalid expected \"invalid character 'b' looking for beginning of value\", got \"json: invalid character 'b' looking for beginning of value\" --- FAIL: TestStrategicMergePatchInvalid (0.00s) TestJSONPatch error:=== RUN TestJSONPatch invalid-syntax: expected error invalid character 'i' looking for beginning of value, but got json: invalid character 'i' looking for beginning of value --- FAIL: TestJSONPatch (0.00s) TestV4ErrorDecoder expandless error:=== RUN TestV4ErrorDecoder wrong error for message \"{\": want=\"error stream protocol error: unexpected end of JSON input in \"{\"\", got=\"error stream protocol error: json: unexpected end of JSON input in \"{\"\" --- FAIL: TestV4ErrorDecoder (0.00s What you expected to happen: The tests should pass with no error. How to reproduce it (as minimally and precisely as possible): a stable version of golang installed master go from upstream git clone cd go/src cd ../.. cp -r ./go /usr/local export PATH=/usr/local/go/bin:$PATH kubernetes repo and run the unit tests. () Anything else we need to know?: These failures are occurring due to mismatch of error messages between upstream go and the k8s tests.", "commid": "kubernetes_issue_96853", "tokennum": 597}], "negative_passages": []}
{"query_id": "q-en-kubernetes-3ff1b8d08100a08f3d19a06321feeddf479f63a137fb9563a2d32342ce18fd1e", "query": "if !apierrors.IsBadRequest(err) { t.Errorf(\"expected HTTP status: BadRequest, got: %#v\", apierrors.ReasonForError(err)) } <del> if err.Error() != expectedError { </del> <ins> if !strings.Contains(err.Error(), expectedError) { </ins> t.Errorf(\"expected %#v, got %#v\", expectedError, err.Error()) } }", "positive_passages": [{"docid": "doc-en-kubernetes-d960907779eeb813df14a2ea4a00c97f52784ded937dbf1c71e5b05391843c78", "text": "There is an addition \"json:\" prefix to SyntaxError messages after this below commit: Environment: Kubernetes version (use ): latest source code from upstream Cloud provider or hardware configuration: OS (e.g: ): \"CentOS Linux 8 (Core)\" Kernel (e.g. ): Linux rajalakshmi-workspace 4.18.0-193.19.1.el82.ppc64le SMP Mon Sep 14 14:48:04 UTC 2020 ppc64le ppc64le ppc64le GNU/Linux Install tools: [root go]# go version go version devel + Fri Nov 20 00:54:43 2020 +0000 linux/ppc64le [root go]# Network plugin and version (if this is a network-related bug): Others:\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig testing\nwill fix it in Go 1.16 as release-blocker.\nI would fix the test here to be more tolerant. exact string matches on error messages aren't really an API\u2026 I would not expect that to block the golang release\nAgree too, we can think about having a substring match to avoid these issues instead!\n/assign Lets see if we can fix this in the k8s tests", "commid": "kubernetes_issue_96853", "tokennum": 352}], "negative_passages": []}
{"query_id": "q-en-kubernetes-402a470f7dfd0801270ef55791c8b1d11ab39d8af3395fcd73b07cab5a0937e2", "query": "func mountToRootfs(m *configs.Mount, c *mountConfig) error { rootfs := c.root <del> mountLabel := c.label mountFd := c.fd dest, err := securejoin.SecureJoin(rootfs, m.Destination) if err != nil { return err } </del> <ins> // procfs and sysfs are special because we need to ensure they are actually // mounted on a specific path in a container without any funny business. </ins> switch m.Device { case \"proc\", \"sysfs\": // If the destination already exists and is not a directory, we bail <del> // out This is to avoid mounting through a symlink or similar -- which </del> <ins> // out. This is to avoid mounting through a symlink or similar -- which </ins> // has been a \"fun\" attack scenario in the past. // TODO: This won't be necessary once we switch to libpathrs and we can //       stop all of these symlink-exchange attacks. <ins> dest := filepath.Clean(m.Destination) if !strings.HasPrefix(dest, rootfs) { // Do not use securejoin as it resolves symlinks. dest = filepath.Join(rootfs, dest) } </ins> if fi, err := os.Lstat(dest); err != nil { if !os.IsNotExist(err) { return err } <del> } else if fi.Mode()&os.ModeDir == 0 { </del> <ins> } else if !fi.IsDir() { </ins> return fmt.Errorf(\"filesystem %q must be mounted on ordinary directory\", m.Device) } if err := os.MkdirAll(dest, 0o755); err != nil { return err } <del> // Selinux kernels do not support labeling of /proc or /sys </del> <ins> // Selinux kernels do not support labeling of /proc or /sys. </ins> return mountPropagate(m, rootfs, \"\", nil) <ins> } mountLabel := c.label mountFd := c.fd dest, err := securejoin.SecureJoin(rootfs, m.Destination) if err != nil { return err } switch m.Device { </ins> case \"mqueue\": if err := os.MkdirAll(dest, 0o755); err != nil { return err", "positive_passages": [{"docid": "doc-en-kubernetes-3a5f1791fd28a186fcf23c773fa97525e98fb83cc70e7098ac61d449614dcefb", "text": "opencontainers/runc has fixed three CVEs: Latest runc is pulled by k/k Check runc version in file No response n/a n/a <details</details<details</details<details</details<details</details\n/assign /sig security architecture release\n/triage accepted", "commid": "kubernetes_issue_117094", "tokennum": 68}], "negative_passages": []}
{"query_id": "q-en-kubernetes-40324b2e42b6f994c10ad56c6dba5b19804786d81e3edd7b91608649d26f0375", "query": "} } <ins> type buffer struct { b  bytes.Buffer rw sync.RWMutex } func (b *buffer) String() string { b.rw.RLock() defer b.rw.RUnlock() return b.b.String() } func (b *buffer) Write(p []byte) (n int, err error) { b.rw.Lock() defer b.rw.Unlock() return b.b.Write(p) } </ins> func TestSecretUpdated(t *testing.T) { datacenter := \"0.0.0.0\" secretName := \"vccreds\"", "positive_passages": [{"docid": "doc-en-kubernetes-59b9ae5b52e0b40199c236ff5490b403bebb933bd0751cd293a630848c9a0b07", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: What you expected to happen: No data races How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\nfor the record as we tend to lose the logs in the gcs bucket\n/sig instrumentation", "commid": "kubernetes_issue_98941", "tokennum": 247}], "negative_passages": []}
{"query_id": "q-en-kubernetes-407a7b6fa9b9b1179b0b05314bfd51c4b30da19e17b2efa5dc7292b3ea9bc452", "query": "// stopKubelet will kill the running kubelet, and returns a func that will restart the process again func stopKubelet() func() { kubeletServiceName := findRunningKubletServiceName() <del> stdout, err := exec.Command(\"sudo\", \"systemctl\", \"kill\", kubeletServiceName).CombinedOutput() </del> <ins> // reset the kubelet service start-limit-hit stdout, err := exec.Command(\"sudo\", \"systemctl\", \"reset-failed\", kubeletServiceName).CombinedOutput() framework.ExpectNoError(err, \"Failed to reset kubelet start-limit-hit with systemctl: %v, %v\", err, stdout) stdout, err = exec.Command(\"sudo\", \"systemctl\", \"kill\", kubeletServiceName).CombinedOutput() </ins> framework.ExpectNoError(err, \"Failed to stop kubelet with systemctl: %v, %v\", err, stdout) return func() { stdout, err := exec.Command(\"sudo\", \"systemctl\", \"start\", kubeletServiceName).CombinedOutput() framework.ExpectNoError(err, \"Failed to restart kubelet with systemctl: %v, %v\", err, stdout) } } <ins> func kubeletHealthCheck(url string) bool { insecureTransport := http.DefaultTransport.(*http.Transport).Clone() insecureTransport.TLSClientConfig = &tls.Config{InsecureSkipVerify: true} insecureHTTPClient := &http.Client{ Transport: insecureTransport, } req, err := http.NewRequest(\"HEAD\", url, nil) if err != nil { return false } req.Header.Set(\"Authorization\", fmt.Sprintf(\"Bearer %s\", framework.TestContext.BearerToken)) resp, err := insecureHTTPClient.Do(req) if err != nil { klog.Warningf(\"Health check on %q failed, error=%v\", url, err) } else if resp.StatusCode != http.StatusOK { klog.Warningf(\"Health check on %q failed, status=%d\", url, resp.StatusCode) } return err == nil && resp.StatusCode == http.StatusOK } </ins> func toCgroupFsName(cgroupName cm.CgroupName) string { if framework.TestContext.KubeletConfig.CgroupDriver == \"systemd\" { return cgroupName.ToSystemd()", "positive_passages": [{"docid": "doc-en-kubernetes-88c095cfe151193749adeb925825c9856381f9f8544c8822d93b8eb731e64566", "text": "ci-kubernetes-node-kubelet-serial-hugepages when start the pod with the resources requests that contain multiple hugepages resources should set correct hugetlb mount and limit under the container cgroup Unexpected error: \"pod ran to completion\", Multiple sizes huge pages is going to be graduated to GA, so having this test job fixed is quite important.\n/sig node\n/assign\n/triage accepted\n/cc\nI did a small analysis and I can see that the pod failed to start, I can not find any failure messages under the kubelet log, so it really hard to say why it failed.\nwere you able to reproduce it locally? btw, there is a \"right way\" to fix this - to fix dynamic update of a hugepage resources. This would eliminate need in a kubelet restart. There is even a PR for that: , we just need to make it working again.\nafter conversation with on slack I'd say we should stick to the current procedure - restarting kubelet when hugepages allocation changes. So, we should investigate why kubelet doesn't restart properly in this test case and fix it.\nNope, I failed to reproduce it locally, also under the CI, it does not appear often. The best thing will be to describe the pod in case if it failed, so we will see the reason.\nunder the code we have so from the log , I can see that the kubelet received the pod before the kubelet stopped, so the problem that pod dropped to Failed state because of the kubelet stop.\nSo some additional details, the one who responsible to restart the kubelet again, is the server service: restart the kubelet service are waiting for hugepages to be available are starting the pod server service restart the kubelet again because it was not healthy for too long - failed to start because of the kubelet restart\ngreat findings! Should we just stop the kubelet and let the server service to start it again? We can also check if the kubelet is restarted successfully before starting the pod.\nI tried it under the PR , also I unsure how can we check if the kubelet restarted successfully. All tests that I wrote before I checked if the node has NotReady state and waited until it will be Ready, but in case of the restart probably the node will always have Ready state because the time period is very short. I will continue to investigate and will check locally how can I fix it.", "commid": "kubernetes_issue_99402", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-407a7b6fa9b9b1179b0b05314bfd51c4b30da19e17b2efa5dc7292b3ea9bc452", "query": "// stopKubelet will kill the running kubelet, and returns a func that will restart the process again func stopKubelet() func() { kubeletServiceName := findRunningKubletServiceName() <del> stdout, err := exec.Command(\"sudo\", \"systemctl\", \"kill\", kubeletServiceName).CombinedOutput() </del> <ins> // reset the kubelet service start-limit-hit stdout, err := exec.Command(\"sudo\", \"systemctl\", \"reset-failed\", kubeletServiceName).CombinedOutput() framework.ExpectNoError(err, \"Failed to reset kubelet start-limit-hit with systemctl: %v, %v\", err, stdout) stdout, err = exec.Command(\"sudo\", \"systemctl\", \"kill\", kubeletServiceName).CombinedOutput() </ins> framework.ExpectNoError(err, \"Failed to stop kubelet with systemctl: %v, %v\", err, stdout) return func() { stdout, err := exec.Command(\"sudo\", \"systemctl\", \"start\", kubeletServiceName).CombinedOutput() framework.ExpectNoError(err, \"Failed to restart kubelet with systemctl: %v, %v\", err, stdout) } } <ins> func kubeletHealthCheck(url string) bool { insecureTransport := http.DefaultTransport.(*http.Transport).Clone() insecureTransport.TLSClientConfig = &tls.Config{InsecureSkipVerify: true} insecureHTTPClient := &http.Client{ Transport: insecureTransport, } req, err := http.NewRequest(\"HEAD\", url, nil) if err != nil { return false } req.Header.Set(\"Authorization\", fmt.Sprintf(\"Bearer %s\", framework.TestContext.BearerToken)) resp, err := insecureHTTPClient.Do(req) if err != nil { klog.Warningf(\"Health check on %q failed, error=%v\", url, err) } else if resp.StatusCode != http.StatusOK { klog.Warningf(\"Health check on %q failed, status=%d\", url, resp.StatusCode) } return err == nil && resp.StatusCode == http.StatusOK } </ins> func toCgroupFsName(cgroupName cm.CgroupName) string { if framework.TestContext.KubeletConfig.CgroupDriver == \"systemd\" { return cgroupName.ToSystemd()", "positive_passages": [{"docid": "doc-en-kubernetes-df5fd4d114576094d5b1a71b893d21a3e13b2c561e9313633a9dfbe243849634", "text": "So the only reliable solution that I found, it just trying to start the pod number of times. I tested it 5 times and the test passed. Can you please review\nCan we access kubelet service from hugepage test cases? If we can we can use its APIs like or to check if kubelet is ready after the restart. Overall I have a feeling of duplication test/e2enode/services functionality in This is a main reason for this and similar bugs I believe. It would be nice to get rid of this duplication if possible. That would nicely isolate kubelet service controls in one place and eliminate conflicts like this one. wdyt?\nnot really, the used mostly to start all needed components to emulate the cluster(not only the kubelet) and the test does not have access to it. I think you can separate the readiness check under the importable method, but it worth the separate PR.\nI updated the PR to check the healthiness of the kubelet and looks like it works just fine.\nthank you. it looks good to me so far. I'll add lgtm label when is merged and tests are all green.\nthe job is still flaky. can you reopen this issue?\nI opened a different one - , the issue can affect any job, not only the hugepages one.\nI can open a fix to W/A an issue(start the pod until it will succeed), it should fix all problems, WDYT?\ni think it's ok as a workaround, until is fixed\nwould it be better to wait until api server reports correct resource value before running the pod?\nWe are waiting for it, the problem that the scheduler and the kubelet see a different picture regarding resources requested by pods.\nok. In this case restarting the pod until it succeeds seems reasonable to me to fix the flakiness until is fixed.\nany progress on the workaround fix?", "commid": "kubernetes_issue_99402", "tokennum": 404}], "negative_passages": []}
{"query_id": "q-en-kubernetes-408cccef83bedd405a6ce0731b5bffe556039ccab07b2f4b0f44f0478d589918", "query": "handler = genericfilters.WithCORS(handler, c.CorsAllowedOriginList, nil, nil, nil, \"true\") <ins> // WithWarningRecorder must be wrapped by the timeout handler // to make the addition of warning headers threadsafe handler = genericapifilters.WithWarningRecorder(handler) </ins> // WithTimeoutForNonLongRunningRequests will call the rest of the request handling in a go-routine with the // context with deadline. The go-routine can keep running, while the timeout logic will return a timeout to the client. handler = genericfilters.WithTimeoutForNonLongRunningRequests(handler, c.LongRunningFunc)", "positive_passages": [{"docid": "doc-en-kubernetes-c00c4002c1ceb0f27a0d12e9f8008c8e3b435d9e5dbb0a6b5f62beaf7aea3677", "text": "I am doing v1.28.3 kube-apiserver testing in the test environment, and I often encounter kube-apiserver panic, especially when kube-apiserver call webhook fails. The following are the captured panic logs: and: kube-apiserver does not panic even if calling webhook times out or fails Deploy a webhook, remove the service corresponding to the webhook, and then create pods in batches to trigger webhook calls No response <details</details<detailsprivate cloud </details<details</details<details</details<details</details<details</details\n/sig api-machinery\nsomewhat related to\nThe scenarios that trigger panic are similar(the apiserver fails to call webhook), but the log shows that the location of panic is different.\n/assign For context of  Thank you. /triage accepted\nagain, full stack logs:\nI'll try to test the mr:\nLet me try to explain the panic - both goroutines are trying to write to the of the first goroutine: This request has timed out, and consequently the filter is trying to send a response to the caller. This is the client facing goroutine from the timeout filter. Note that the call to is protected by a mutex, that means that if the other goroutine is using the delegated object via the adapter, then this panic should not happen. second goroutine: let's check the other goroutine, it is also trying to write to the of the object: Now uses an unprotected version of the ResponseWriter object: The filter precedes the filter in the execution order, so the in is not using the thread safe implementation. This is the order today: one quick resolution is to move the after the timeout filter: , but there could be code that precedes that needs to write warning? Also note that the panic mentioned in is not as severe, it does not cause the apiserver to crash. For a more proper solution, i think we would want any thoughts?", "commid": "kubernetes_issue_122940", "tokennum": 443}], "negative_passages": []}
{"query_id": "q-en-kubernetes-408cccef83bedd405a6ce0731b5bffe556039ccab07b2f4b0f44f0478d589918", "query": "handler = genericfilters.WithCORS(handler, c.CorsAllowedOriginList, nil, nil, nil, \"true\") <ins> // WithWarningRecorder must be wrapped by the timeout handler // to make the addition of warning headers threadsafe handler = genericapifilters.WithWarningRecorder(handler) </ins> // WithTimeoutForNonLongRunningRequests will call the rest of the request handling in a go-routine with the // context with deadline. The go-routine can keep running, while the timeout logic will return a timeout to the client. handler = genericfilters.WithTimeoutForNonLongRunningRequests(handler, c.LongRunningFunc)", "positive_passages": [{"docid": "doc-en-kubernetes-f6276625b0df7e8b951a42b4ce484e48eb7715b4546658f042b200999787970a", "text": "/cc\nI tend to remove the timeout filter, the sooner the better, and I think the Apiserver panic is the P0-level bug, directly affecting the availability of the cluster I have cherry-picked and tested it in my cluster, and I still need to continue to observe for 1-2 days\nI opened a minimal WIP fix for the warning writer in since the timeout filter removal is a much bigger change to reason through\nthanks a lot, I will try to test and cherry-pick the above minimal WIP fix in\nsorry, I completely overlooked , I only saw and that looked too big to take safely right now I prefer to\nCan we backport the fix to 1.28?\nWhy 1.28 specifically? I'm not aware of anything that changed in 1.28 that made this more or less prevalent. If this meets backport criteria, going to all active branches could make sense (1.27+)", "commid": "kubernetes_issue_122940", "tokennum": 191}], "negative_passages": []}
{"query_id": "q-en-kubernetes-408d41342ff59f1fe86972d71f8cdcf6b3828cb1cac65b15efdeb103ded6b226", "query": "testRootDir := makeTempDirOrDie(\"kubelet_integ_1.\", \"\") configFilePath := makeTempDirOrDie(\"config\", testRootDir) glog.Infof(\"Using %s as root dir for kubelet #1\", testRootDir) <del> kcfg := kubeletapp.SimpleKubelet(cl, &fakeDocker1, machineList[0], testRootDir, manifestURL, \"127.0.0.1\", 10250, api.NamespaceDefault, empty_dir.ProbeVolumePlugins(), nil, cadvisorInterface, configFilePath) </del> <ins> kcfg := kubeletapp.SimpleKubelet(cl, &fakeDocker1, machineList[0], testRootDir, firstManifestURL, \"127.0.0.1\", 10250, api.NamespaceDefault, empty_dir.ProbeVolumePlugins(), nil, cadvisorInterface, configFilePath) </ins> kcfg.PodStatusUpdateFrequency = 1 * time.Second kubeletapp.RunKubelet(kcfg) // Kubelet (machine)", "positive_passages": [{"docid": "doc-en-kubernetes-56027fa26048aea64718f2bd7d7c5d6f58ddca1472c1fc738c03141b6dea3ad6", "text": "Currently it assumes it can read ContainerManifest - it should try both\nWhy not hold on this until we have Kubelet-read-Pod in?\nAlso the HTTP source has the same problem.\nIt should read Pod. Changed the title.\nIdeally, I'd like all Pods created directly via Kubelet to be to etcd and surfaced via the API. If updates are made via the API, I'd like those to propagate back to the node. We can discuss whether the config file should be updated or ignored. At some point, I'd like Kubelet to persistently cache pods received from the apiserver, perhaps by just writing them all out as config files.\nis the issue to sync local pods back to apiserver.\nthis is somewhat related to other issues we talked about.\nDetail: We want locally specified pods to be able to use YAML config files, but we also want to rip YAML out of the API server . The config-file behavior should be as similar to the kubectl experience. Kubelet could use parts of the kubectl library to translate YAML to JSON. Vision: Eventually, I'd like Kubelet to use the apiserver library and support exactly the same Pod API as the master, at which time I'd like kubectl be able to create pods directly on Kubelets, as well as reading from config files. I also expect to have a per-node controller . I'd like to be able to use the per-node controller to update pods started via config files (or direct kubectl-kubelet pods), overriding those original files. For availability and self-hosting, we'll eventually need local checkpointing , ideally just using serialized JSON for each object. If Kubelet used apiserver, this could be done using a custom registry implementation.\nI think that is a prerequisite for it.\nIf noone picks it up, I'm going to start working on it tomorrow.\nthanks, wojtek-t\nfixed it for http channel", "commid": "kubernetes_issue_3372", "tokennum": 445}], "negative_passages": []}
{"query_id": "q-en-kubernetes-40aa644f9e896a85fdb78ad4e9907f0b8165c7b56194cc1b7e48fcb49831bd10", "query": "\"regexp\" \"strings\" \"syscall\" <ins> \"github.com/golang/glog\" </ins> ) const MOUNT_MS_BIND = syscall.MS_BIND", "positive_passages": [{"docid": "doc-en-kubernetes-4cc03be8a4c78b1eefdd458c17e35e10d17eae1288a6e1bcb08b9d7d585d4633", "text": "07-02 and 13-02 No response No response /sig\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scalability\nI might be related to the npd.\nThe same test failures happening again on 25.02:\n/sig node\n/sig node /cc The restart of caused the flake. I also opened to track it in NPD repo.\nI missed this log. It is caused by oom. Adding some memory may help. I submitted to fix it. Does mean killing metrics-server?\n/remove-sig node Sorry, I misread the log. The NPD found the metric server is OOM. It is about the metrics server, not the NPD. Sorry for disturb. I may add some memory for metric-server and check why metric server memory changed. I heard that metrics server recently released a new version. I will check if it is related.\n/sig node\nOOM metrics shows the metric server is OOMed. This is odd, that only metrics-server-nanny is with a memory limit. It uses whose command is . metrics-server container has no memory limit, but it got killed by OOM. Does this indicate that the node is OOM? (edited)\nThe last run failed in node-problem-detector ContainerStateTerminated. I0227 05:03:31. ] PodStartupLatency: perc50: 14m29.018886827s, perc90: 28m44.625518807s, perc99: 32m2.19303496s; threshold 1h0m0s I0227 05:03:32. ]", "commid": "kubernetes_issue_123328", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-40aa644f9e896a85fdb78ad4e9907f0b8165c7b56194cc1b7e48fcb49831bd10", "query": "\"regexp\" \"strings\" \"syscall\" <ins> \"github.com/golang/glog\" </ins> ) const MOUNT_MS_BIND = syscall.MS_BIND", "positive_passages": [{"docid": "doc-en-kubernetes-a11072f45f81b280dea24734413173747c87bdd472ce068bad905ce856d1cb81", "text": "Loaded restart count threshold overrides: map[coredns:2 fluentd-gcp:999 konnectivity-agent:2 kube-controller-manager:1 kube-proxy:2 kube-scheduler:1 l7-lb-controller:1 metadata-proxy:2 prometheus-to-sd-exporter:2] I0227 05:03:32. ] ClusterOOMsTracker: gathering cluster OOMs tracking measurement E0227 05:03:32. ] TestMetrics: [action gather failed for SystemPodMetrics measurement: restart counts violation: RestartCount(node-problem-detector-tgl8h, node-problem-detector)=1, want <= 0; RestartCount(node-problem-detector-vpsmz, node-problem-detector)=1, want <= 0] I0227 05:03:32. ] Step \"[step: 29] gathering measurements\" ended W0227 05:03:32. ] Got errors during step execution: [measurement call TestMetrics - TestMetrics error: [action gather failed for SystemPodMetrics measurement: restart counts violation: RestartCount(node-problem-detector-tgl8h, node-problem-detector)=1, want <= 0; RestartCount(node-problem-detector-vpsmz, node-problem-detector)=1, want <= 0]] I0227 05:03:32. ] Waiting for the chaos monkey subroutine to end... I0227 05:03:32. ] Chaos monkey ended. I0227 05:03:32. ] I0227 05:03:32. ] Stopping DnsLookupLatency probe... I0227 05:03:47. ] Stopping InClusterNetworkLatency probe... I0227 05:04:22. ] Resources cleanup time: 50.539700215s E0227 05:04:22. ]\nE0227 05:04:22. ] Test Finished E0227 05:04:22. ] Test: E0227 05:04:22. ] Status: Fail E0227 05:04:22. ]", "commid": "kubernetes_issue_123328", "tokennum": 491}], "negative_passages": []}
{"query_id": "q-en-kubernetes-40aa644f9e896a85fdb78ad4e9907f0b8165c7b56194cc1b7e48fcb49831bd10", "query": "\"regexp\" \"strings\" \"syscall\" <ins> \"github.com/golang/glog\" </ins> ) const MOUNT_MS_BIND = syscall.MS_BIND", "positive_passages": [{"docid": "doc-en-kubernetes-8045aaa7c39478c40c58e17441fd375a472ca56f31885311d26bd40c11b2233d", "text": "Errors: [measurement call TestMetrics - TestMetrics error: [action gather failed for SystemPodMetrics measurement: restart counts violation: RestartCount(node-problem-detector-tgl8h, node-problem-detector)=1, want <= 0; RestartCount(node-problem-detector-vpsmz, node-problem-detector)=1, want <= 0]] E0227 05:04:22. ]\nI0227 05:04:22. ]\nI0227 05:04:22. ] Running testing/huge- I0227 05:04:22. ]", "commid": "kubernetes_issue_123328", "tokennum": 136}], "negative_passages": []}
{"query_id": "q-en-kubernetes-40c9c6e79791e19a011697fa36d1e3c18dc1b69ddf53c7438dade195d5d24d21", "query": "{ cfg: &kubeadmapi.MasterConfiguration{}, expected: api.Volume{ <del> Name: \"pki\", </del> <ins> Name: \"k8s\", </ins> VolumeSource: api.VolumeSource{ HostPath: &api.HostPathVolumeSource{ Path: kubeadmapi.GlobalEnvParams.KubernetesDir},", "positive_passages": [{"docid": "doc-en-kubernetes-aa0efe62d493b3611250d6c4d1b34c71d8fe0e732e78e4445af443d5c2b2f03c", "text": "<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.--What keywords did you search in Kubernetes issues before filing this one? controller /etc/ssl/certs kubeadm /etc/ssl/certs Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT <!-- If this is a BUG REPORT, please: Fill in as much of the template below as you can. If you leave out information, we can't help you as well. If this is a FEATURE REQUEST, please: Describe in detail the feature/behavior/change you'd like to see. In both cases, be ready for followup questions, and please respond in a timely manner. If we can't reproduce a bug or think a feature already exists, we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why. --Kubernetes version (use ): 5 custom built master I also use a custom built hyperkube image instead of the single app images for apiserver, controller, ... Environment: Cloud provider or hardware configuration: azure OS (e.g. from /etc/os-release): CentOS 7.2 Kernel (e.g. ): Linux ma-kub8ms0 3.10.0-327.36.3.el7.x8664 SMP Mon Oct 24 16:09:20 UTC 2016 x8664 x8664 x8664 GNU/Linux Install tools: kubeadm Others: deployed with Azure RM template and ansible What happened: controller is not able to do https, including calls to the Azure RM API What you expected to happen: https should work as usual How to reproduce it (as minimally and precisely as possible): Use kubeadm to install kubernetes on CentOS exec into the controller and try \"curl \" Anything else do we need to know: It looks like caused this issue. On CentOS, I see these files on the host OS: I suspect the symlinks to /etc/pki/... being the problem here, as they are not available inside the hyperkube Debian image. I also tried to verify this with It seems to not be based on Debian and thus gives a different error: I see 2 possible solutions: of host mounting /etc/ssl/certs into the controller pod, the ca certificates could be installed into the image.", "commid": "kubernetes_issue_36150", "tokennum": 529}], "negative_passages": []}
{"query_id": "q-en-kubernetes-40c9c6e79791e19a011697fa36d1e3c18dc1b69ddf53c7438dade195d5d24d21", "query": "{ cfg: &kubeadmapi.MasterConfiguration{}, expected: api.Volume{ <del> Name: \"pki\", </del> <ins> Name: \"k8s\", </ins> VolumeSource: api.VolumeSource{ HostPath: &api.HostPathVolumeSource{ Path: kubeadmapi.GlobalEnvParams.KubernetesDir},", "positive_passages": [{"docid": "doc-en-kubernetes-41c6565c36e0283a9e2054713b809a870281386c810e77c1faf5476befe20dbf", "text": "This is already done for hyperkube and would work out of the box when the host mount would be omitted. could try to figure out if /etc/pki should also be host mounted and add this to the controller manifest if required. I'd be happy to provide a fix by myself, I just need to know which solution you would prefer.\nSame problem seems to apply to the apiserver. Not sure however if it actually does https calls.\nimplements solution 2.\nThis issue was moved to kubernetes/kubeadm", "commid": "kubernetes_issue_36150", "tokennum": 111}], "negative_passages": []}
{"query_id": "q-en-kubernetes-40d6248e1fc2cf2915c4b81bf9a2d933ee43b1c189e876da9ada1783f36ccb16", "query": "go_test( name = \"go_default_test\", srcs = [ <ins> \"labels_test.go\", </ins> \"pod_update_test.go\", \"types_test.go\", ],", "positive_passages": [{"docid": "doc-en-kubernetes-672dc953e52a460d81d453213d4e2e634446d10e93c8bdf3e045ab9c2943abdc", "text": "This is a sub issue for\ncc can you please assign this to me? Thanks.\n, please create PR directly and cc to Tim for review.\n/sig node\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close", "commid": "kubernetes_issue_40780", "tokennum": 237}], "negative_passages": []}
{"query_id": "q-en-kubernetes-40fa4142e0548e86a6d144dc972d3c9f92d7a75d43cb9d81fea16e303f5a4432", "query": "// corresponding requests. func newCacheRoundTripper(cacheDir string, rt http.RoundTripper) http.RoundTripper { d := diskv.New(diskv.Options{ <ins> PathPerm: os.FileMode(0750), FilePerm: os.FileMode(0660), </ins> BasePath: cacheDir, TempDir:  filepath.Join(cacheDir, \".diskv-temp\"), })", "positive_passages": [{"docid": "doc-en-kubernetes-30e07950978ed617c12104c8342559dfe477718ba7eb61f98c21f95bb37c1439", "text": "In kubectl v1.8.0+, schema info is cached in the location specified by (defaulting to ), written with world-writeable permissions (rw-rw-rw-). If is specified and pointed at a different location accessible to other users/groups, the written files may be modified by other users/groups and disrupt the kubectl invocation. CVSS score: CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N (3.3, low) What versions are affected? kubectl v1.8.0+ What configurations are affected? Invocations that point at world-writeable locations Impact Malformed responses written to the cache directory can disrupt the kubectl invocation Workaround Use the default location in the $HOME directory or point it at a directory that is only accessible to desired users/groups. (original description follows) ==== What happened: The files inside of \".kube/http-cache\" are world writeable (rw-rw-rw-). While the default for these files appears to be the home directory, using the \"--cache-dir\" flag could put these files into a place where world writeable files would allow any user / process to modify the cache files. Modification of the cache files could influence the kubectl utility in a negative way for other users. What you expected to happen: Apply stricter file permissions to the http-cache files. How to reproduce it (as minimally and precisely as possible): Run any generic kubectl command which is successful and then list the cache directory $ kubectl get pods --all-namespaces $ ls -la Anything else we need to know?", "commid": "kubernetes_issue_76676", "tokennum": 398}], "negative_passages": []}
{"query_id": "q-en-kubernetes-40fa4142e0548e86a6d144dc972d3c9f92d7a75d43cb9d81fea16e303f5a4432", "query": "// corresponding requests. func newCacheRoundTripper(cacheDir string, rt http.RoundTripper) http.RoundTripper { d := diskv.New(diskv.Options{ <ins> PathPerm: os.FileMode(0750), FilePerm: os.FileMode(0660), </ins> BasePath: cacheDir, TempDir:  filepath.Join(cacheDir, \".diskv-temp\"), })", "positive_passages": [{"docid": "doc-en-kubernetes-03c8940a04bf023e0d3632a105949b7e85efda694ffafea56ecb99998a766122", "text": ": I estimate this is a low severity security issue with a CVSS score of \"3.3 / CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N\" - Environment: Linux Kubernetes version (use kubectl version):Client Version: version.Info{Major:\"1\", Minor:\"12\", GitVersion:\"v1.12.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2019-02-26T12:49:28Z\", GoVersion:\"go1.10.8\", Compiler:\"gc\", Platform:\"linux/amd64\"} Server Version: version.Info{Major:\"1\", Minor:\"12\", GitVersion:\"v1.12.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2019-02-26T12:49:28Z\", GoVersion:\"go1.10.8\", Compiler:\"gc\", Platform:\"linux/amd64\"} Cloud provider or hardware configuration: AWS. Running kube api server in hyperkube. OS (e.g: cat /etc/os-release): NAME=\"CentOS Linux\" VERSION=\"7.1808 (Core)\" ID=\"centos\" IDLIKE=\"rhel fedora\" VERSIONID=\"7\" PRETTYNAME=\"CentOS Linux 7.1808 (Core)\" ANSICOLOR=\"0;31\" CPENAME=\"cpe:/o:centos:centos:7\" HOMEURL=\"\" BUGREPORTURL=\"\" CENTOSMANTISBTPROJECT=\"CentOS-7\" CENTOSMANTISBTPROJECTVERSION=\"7\" REDHATSUPPORTPRODUCT=\"centos\" REDHATSUPPORTPRODUCTVERSION=\"7\" OSTREEVERSION=7.1808 Kernel (e.g. uname -a): Linux hackit.internal 3.10.0-862.11.6.el7.x8664 SMP Tue Aug 14 21:49:04 UTC 2018 x8664 x8664 x86_64 GNU/Linux Install tools: Manual installation. Others: n/a\n/sig product-security\nClosing this issue. <detailsIn response to : if you think this is serious, send an email thanks!", "commid": "kubernetes_issue_76676", "tokennum": 565}], "negative_passages": []}
{"query_id": "q-en-kubernetes-40fa4142e0548e86a6d144dc972d3c9f92d7a75d43cb9d81fea16e303f5a4432", "query": "// corresponding requests. func newCacheRoundTripper(cacheDir string, rt http.RoundTripper) http.RoundTripper { d := diskv.New(diskv.Options{ <ins> PathPerm: os.FileMode(0750), FilePerm: os.FileMode(0660), </ins> BasePath: cacheDir, TempDir:  filepath.Join(cacheDir, \".diskv-temp\"), })", "positive_passages": [{"docid": "doc-en-kubernetes-5f4971cee99e57062ae7961121de35cc677214a3e6ca77682b093e74b00a9b30", "text": "</details\nAdjusted the CVSS score to to indicate user interaction is required (since they must specify a non-default cache option pointed at a shared writeable location)\nThere are two places this should be done: PathPerm and FilePerm should be set here: the temp file and final file should have stricter permissions (probably 0660) here:\n/cc\n/help\nThis request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\n/assign I would like to work on release-1.9, as I just made a hot fix for our team's k8s version of 1.9.\nGitHub didn't allow me to assign the following users: yuchengwu. Note that only and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign I would like to work on release-1.9, as I just made a hot fix for our team's k8s version of 1.9. 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\nhelp fixing this is welcome, though it would only be fixed in releases 1.12+, per\n/label official-cve-feed (Related to kubernetes/sig-security)", "commid": "kubernetes_issue_76676", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4104a5e532b1b7e1aaba810dd585065d028257d1f0d047a4e52fc1dfcc94d840", "query": "// Create a usage object that is based on the quota resource version that will handle updates // by default, we preserve the past usage observation, and set hard to the current spec <del> usage := v1.ResourceQuota{ ObjectMeta: metav1.ObjectMeta{ Name:            resourceQuota.Name, Namespace:       resourceQuota.Namespace, ResourceVersion: resourceQuota.ResourceVersion, Labels:          resourceQuota.Labels, Annotations:     resourceQuota.Annotations}, Status: v1.ResourceQuotaStatus{ Hard: hardLimits, Used: used, }, </del> <ins> usage := resourceQuota.DeepCopy() usage.Status = v1.ResourceQuotaStatus{ Hard: hardLimits, Used: used, </ins> } dirty = dirty || !quota.Equals(usage.Status.Used, resourceQuota.Status.Used) // there was a change observed by this controller that requires we update quota if dirty { <del> _, err = rq.rqClient.ResourceQuotas(usage.Namespace).UpdateStatus(&usage) </del> <ins> _, err = rq.rqClient.ResourceQuotas(usage.Namespace).UpdateStatus(usage) </ins> return err } return nil", "positive_passages": [{"docid": "doc-en-kubernetes-9f1156fd8ea5be22a99955ab2508557bd1a6742b9b29a9f12fac2e60dab6df47", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: The section for my was stripped, but left for all other resource types What you expected to happen: should put my changes into the cluster as requested How to reproduce it (as minimally and precisely as possible): Here are the resources (Note you will need to change the ownerReference UID and name to some object that exists in your cluster) Observe applying misses out the for the : Observe doing this again updates it correctly: Anything else we need to know?: Environment: Kubernetes version (use ):Cloud provider or hardware configuration: minikube\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nTurns out, shutting down stops this from happening. After creating the object, it has the right ownerReference. On starting , it immediately removed the\n/assign\nfixed in\nThat was impressively fast! Thanks for the fix :)\ncc", "commid": "kubernetes_issue_70030", "tokennum": 227}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4108d4f4bfb4b6b2d760fd5f8d094c0fd05d0edb96ac9448636c4d137f134c37", "query": "attachdetachMutex.LockKey(string(nodeName)) defer attachdetachMutex.UnlockKey(string(nodeName)) <del> if err := detacher.vsphereVolumes.DetachDisk(volPath, nodeName); err != nil { </del> <ins> if err := detacher.vsphereVolumes.DetachDisk(newVolumePath, nodeName); err != nil { </ins> klog.Errorf(\"Error detaching volume %q: %v\", volPath, err) return err }", "positive_passages": [{"docid": "doc-en-kubernetes-e1df151812a738ca8d7e9f97519d671c643638f3ca9d9400cc430f5f7a7d204c", "text": "When user creates a static PV using folder name in path: on vSAN backed datastore then detach disk does not work because check fails - The code expects folder name to be UUID but it does not and hence it determines disk is not attached to the node and hence no detach is ever performed. /sig storage cc", "commid": "kubernetes_issue_95121", "tokennum": 68}], "negative_passages": []}
{"query_id": "q-en-kubernetes-411446b1c6fb40f56463abefbc7197db0a2448f1c71403d695a74e9b58db8e0f", "query": "registerMetrics.Do(func() { legacyregistry.MustRegister(etcdRequestLatency) legacyregistry.MustRegister(objectCounts) <ins> legacyregistry.MustRegister(etcdObjectCounts) </ins> legacyregistry.MustRegister(dbTotalSize) legacyregistry.MustRegister(etcdBookmarkCounts) legacyregistry.MustRegister(etcdLeaseObjectCounts) }) } <del> // UpdateObjectCount sets the etcd_object_counts metric. </del> <ins> // UpdateObjectCount sets the apiserver_storage_object_counts and etcd_object_counts (deprecated) metric. </ins> func UpdateObjectCount(resourcePrefix string, count int64) { objectCounts.WithLabelValues(resourcePrefix).Set(float64(count)) <ins> etcdObjectCounts.WithLabelValues(resourcePrefix).Set(float64(count)) </ins> } // RecordEtcdRequestLatency sets the etcd_request_duration_seconds metrics.", "positive_passages": [{"docid": "doc-en-kubernetes-49b5f1148571079e399a01da886ccfbbffa2370f5f5a5844a5ac847b772993f9", "text": "What would you like to be : We want to start migrating metrics which people depend on for operations to stable status. etcdobjectcounts was mentioned in a recent SIG meeting as a viable candidate. However, the 'etcd' prefix is not in line with stated metric conventions. SIG consensus determined that creating a new version of the metric with the metric name 'apiserverstorageobjectcounts' would be sufficient allow this metric to be promoted. We'd want to simultaneously deprecate 'etcdobjectcounts' (since it would be a duplicate) and remove it after the deprecation grace period window. /assign /cc\nGitHub didn't allow me to assign the following users: erain. 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 : What would you like to be : /cc 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\n/sig instrumentation api-machinery /cc\nAck. I am going to work on this.\n/assign /triage accepted\nIn the SIG api-machinery meeting today, we agreed that the stable version of this metric should be named 'apiserverstorageobject_count'\nThanks and will use in the PR. (And sorry for missing today's meeting - due to a conflict)", "commid": "kubernetes_issue_98270", "tokennum": 331}], "negative_passages": []}
{"query_id": "q-en-kubernetes-413c85b57f8986eaf45f64426d7ef1121ff3f484283874cec323d87423c38c95", "query": "return len(c1map) == 0 } <ins> func shouldIgnoreNodeUpdate(oldNode, curNode v1.Node) bool { if !nodeInSameCondition(oldNode.Status.Conditions, curNode.Status.Conditions) { return false } oldNode.ResourceVersion = curNode.ResourceVersion oldNode.Status.Conditions = curNode.Status.Conditions return apiequality.Semantic.DeepEqual(oldNode, curNode) } </ins> func (dsc *DaemonSetsController) updateNode(old, cur interface{}) { oldNode := old.(*v1.Node) curNode := cur.(*v1.Node) <del> if reflect.DeepEqual(oldNode.Labels, curNode.Labels) && reflect.DeepEqual(oldNode.Spec.Taints, curNode.Spec.Taints) && nodeInSameCondition(oldNode.Status.Conditions, curNode.Status.Conditions) { // If node labels, taints and condition didn't change, we can ignore this update. </del> <ins> if shouldIgnoreNodeUpdate(*oldNode, *curNode) { </ins> return }", "positive_passages": [{"docid": "doc-en-kubernetes-56dc15a3fe2161c6cf8927a51d2d0dce03fea80f01ef1e0345dcc3ca50d1379f", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: a cluster, And node1 with resource 1 DaemonSet, request resource 4 run , There is no pod created. resource to the node: run , There is still no pod created. What you expected to happen: In step 5, There is one pod created. How to reproduce it (as minimally and precisely as possible): see above description Anything else we need to know?: Environment: Kubernetes version (use ):1.10.5 Cloud provider or hardware configuration: OS (e.g. from /etc/os-release):CentOS7 Kernel (e.g. ): Install tools: Others: /sig app\nxref\nThanks! is not work here! Because: DaemonSetsController didn't watch the changes.(we use to updateNode.) we restart kubelet, The DaemonSetsController watch the changes, but it seems that the node info is not updated, and still failed to create pod:\nI found it is a bug here, ignore the changes. I made a fix , PTAL! Thanks!\nAny workarounds for old cluster versions? Up: looks like in my case helped but after some delay.\n, which version of k8s are you using? If it's sunset, you have to merge the pr yourself :). I think restart kubelet trigger delete/add to make sure it sync .\nSorry, I didn't say\nI think we still support 1.12 for now :) let's cherry pick it if not and wait for next 1.12 release.", "commid": "kubernetes_issue_67225", "tokennum": 342}], "negative_passages": []}
{"query_id": "q-en-kubernetes-41898da6e9393b17f6a2ab0a9f944a41f5720a1ac2c72635a4a5a7a906b4919f", "query": "timeout := time.Duration(3 * time.Second) ctx, cancel := context.WithTimeout(context.Background(), timeout) defer cancel() <del> scheme := runtime.NewScheme() </del> <ins> scheme := fake.NewTestScheme() </ins> metav1.AddMetaToScheme(scheme) informerReciveObjectCh := make(chan *metav1.PartialObjectMetadata, 1) objs := []runtime.Object{}", "positive_passages": [{"docid": "doc-en-kubernetes-d7e6fda1614d5720cc8c8b15824f08c5e880f7950d0c5cc5cd811c2fcceb82ab", "text": "Because of this scheme mutation, this leads to concurrent use of the same scheme to cause the program to panic. It would be ideal to do this in some concurrent safe manner or add a warning or similar\n/sig api-machinery\n/assign\n/assign /triage accepted", "commid": "kubernetes_issue_107823", "tokennum": 54}], "negative_passages": []}
{"query_id": "q-en-kubernetes-418f1b8b64f8b578c0f4ede841826858a597639685effa63e0af7e429b5127cb", "query": "} apiGroupList, resourcesByGV, failedGVs = SplitGroupsAndResources(aggregatedDiscovery) default: <del> return nil, nil, nil, fmt.Errorf(\"Unknown discovery response content-type: %s\", responseContentType) </del> <ins> // Default is unaggregated discovery v1. err = json.Unmarshal(body, apiGroupList) if err != nil { return nil, nil, nil, err } </ins> } return apiGroupList, resourcesByGV, failedGVs, nil } <ins> // isV2Beta1ContentType checks of the content-type string is both // \"application/json\" and contains the v2beta1 content-type params. // NOTE: This function is resilient to the ordering of the // content-type parameters, as well as parameters added by // intermediaries such as proxies or gateways. Examples: // //\t\"application/json; g=apidiscovery.k8s.io;v=v2beta1;as=APIGroupDiscoveryList\" = true //\t\"application/json; as=APIGroupDiscoveryList;v=v2beta1;g=apidiscovery.k8s.io\" = true //\t\"application/json; as=APIGroupDiscoveryList;v=v2beta1;g=apidiscovery.k8s.io;charset=utf-8\" = true //\t\"application/json\" = false //\t\"application/json; charset=UTF-8\" = false func isV2Beta1ContentType(contentType string) bool { base, params, err := mime.ParseMediaType(contentType) if err != nil { return false } return runtime.ContentTypeJSON == base && params[\"g\"] == \"apidiscovery.k8s.io\" && params[\"v\"] == \"v2beta1\" && params[\"as\"] == \"APIGroupDiscoveryList\" } </ins> // ServerGroups returns the supported groups, with information like supported versions and the // preferred version. func (d *DiscoveryClient) ServerGroups() (*metav1.APIGroupList, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-3257ecff81fbc60fa2a8f982346c462089eb7c896f62cce1d4e02ff6df66d913", "text": "We are using (and ) to interact with Kubernetes clusters behind a couple of proxy layers. One of these proxies completes the headers to include character encoding details. This was working fine until recently, when client-go/kubectl have started to fail when interacting with the discovery API. It seems that a recent change has made kubectl more restrictive of the content-type that it expects. I suspect that it is related to this commit: For example, this is an error from a kubectl command: We can of course try to fix it on our end, removing that charset information. However, it is a valid content-type and the way kubectl is handling the content-type there seems like it is relying on implementation details of kube-apiserver (that it does not add metadata to the content-type). I propose to fix this issue in , by properly parsing and handling the content-type.\ncc /kind regression /kind bug /sig api-machinery /priority important-soon looks like the switch statement in downloadLegacy() needs to be more tolerant of the variety of content-types it can get from a server (including text/plain or no content-type if old servers could have returned that...)\n/transfer kubernetes/kubernetes\nSomething went wrong or the destination repo kubernetes/kubernetes/kubernetes does not exist. <detailsIn response to : /transfer kubernetes/kubernetes 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\n/transfer kubernetes\nYep, the string comparison for the content-type is flimsy, let's address that. Thanks for the report!\n/assign\n/triage accepted\n/cc\nThe fix is being cherry-picked back to: : :", "commid": "kubernetes_issue_117562", "tokennum": 408}], "negative_passages": []}
{"query_id": "q-en-kubernetes-41a5f32c9cf0219dcdc6ba0c1c85c39e1d51677606b91686ee24a6b99e38756a", "query": "return machine, exists, err } <ins> // VirtualMachineClientGetWithRetry invokes az.VirtualMachinesClient.Get with exponential backoff retry func (az *Cloud) VirtualMachineClientGetWithRetry(resourceGroup, vmName string, types compute.InstanceViewTypes) (compute.VirtualMachine, error) { var machine compute.VirtualMachine err := wait.ExponentialBackoff(az.resourceRequestBackoff, func() (bool, error) { var retryErr error machine, retryErr = az.VirtualMachinesClient.Get(resourceGroup, vmName, types) if retryErr != nil { glog.Errorf(\"backoff: failure, will retry,err=%v\", retryErr) return false, nil } glog.V(2).Infof(\"backoff: success\") return true, nil }) return machine, err } // GetIPForMachineWithRetry invokes az.getIPForMachine with exponential backoff retry func (az *Cloud) GetIPForMachineWithRetry(name types.NodeName) (string, error) { var ip string err := wait.ExponentialBackoff(az.resourceRequestBackoff, func() (bool, error) { var retryErr error ip, retryErr = az.getIPForMachine(name) if retryErr != nil { glog.Errorf(\"backoff: failure, will retry,err=%v\", retryErr) return false, nil } glog.V(2).Infof(\"backoff: success\") return true, nil }) return ip, err } </ins> // CreateOrUpdateSGWithRetry invokes az.SecurityGroupsClient.CreateOrUpdate with exponential backoff retry func (az *Cloud) CreateOrUpdateSGWithRetry(sg network.SecurityGroup) error { return wait.ExponentialBackoff(az.resourceRequestBackoff, func() (bool, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-0f3fba1dceb9c94d1a19ea07536eb93382a47fa8d74b43be2f3310b5be7e4348", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: In certain large cluster scenarios we would like to anticipate kubelet behavior hitting request limits, and backoff in response. E.g., What you expected to happen: This is a request for add'l backoff coverage, so nothing surprising. How to reproduce it (as minimally and precisely as possible): Build a cluster with as many nodes as your subscription will support on azure until kubelet behavior contributes to backend API request limits. Environment: Kubernetes version (use ): and Cloud provider or hardware configuration**: azure OS (e.g. from /etc/os-release): Ubuntu 16.04.2 LTS (Xenial Xerus) Kernel (e.g. ): Linux k8s-pool7--7 4.4.0-83-generic -Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x8664 x8664 x86_64 GNU/Linux Install tools: acs-engine Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig azure", "commid": "kubernetes_issue_48971", "tokennum": 358}], "negative_passages": []}
{"query_id": "q-en-kubernetes-41b5179627ef86c9a91dbcf09a96b05e9c90723006afbea58ab7f45d27835300", "query": "<ins> # 3.1 * The pause container gains a signal handler to clean up orphaned zombie processes. ([#36853](https://prs.k8s.io/36853), [@verb](https://github.com/verb)) * `pause -v` will return build information for the pause binary. ([#56762](https://prs.k8s.io/56762), [@verb](https://github.com/verb)) # 3.0 * The pause container was rewritten entirely in C. ([#23009](https://prs.k8s.io/23009), [@uluyol](https://github.com/uluyol)) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-a834f77ddd825b3d04a660aa7c11d0734893e4dcde6e0d4a7399e3b3daf56428", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: the pause-amd64:3.0 image on has an empty schema2 manifest, which prevents is from being pulled by proxy/caches which only support V2 registries. What you expected to happen: Being able to pull ` using a V2 manifest compatible client. Anything else we need to know?: The proxy/cahce is requesting this\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nAfter talking with , he mentionned the following\nAFAIK, does not support well. After inspecting the image, you can find is still using manifest v1.\n/cc FYI\nIm not sure which exact version x sch\u00e9ma X is needed. What I know is that we can download through the proxy/cache all other Kubernetes kube-system images, only the pause image is giving us trouble. Therefore, I would say that having the image available using the same format as the other kube-system images would be the request here.\nYeah, we haven't updated the pause image in a while, since it doesn't really ever change. I'm not sure whether rebuilding + pushing over the existing tag is safe, or if we should bump to or something. thoughts?\nIf we do rebuilding/updating the image, that would help and a bunch of similar issues.\nit's better/save to go with new tag\nI didn't realize there were changes to the pause binary that were never actually deployed. It seems like we should probably just do that (and bump the tag).\nthat sounds great. Any idea when the existing 3.0 tag could be pushed again?\nWe shouldn't push over the 3.0 tag; we should push a 3.1 or 4.0 tag instead. I'm not sure who owns the pause container who should drive this. Maybe sig-node and/or\nIt seems like it should be sig-node. I'll look into it.\nThe new container has been built, can you test with\nIts working! thanks! I was able to pull it through our artifactory proxy , Lee Verberne <:\nexcellent, thanks for checking. /assign", "commid": "kubernetes_issue_56253", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-41b5179627ef86c9a91dbcf09a96b05e9c90723006afbea58ab7f45d27835300", "query": "<ins> # 3.1 * The pause container gains a signal handler to clean up orphaned zombie processes. ([#36853](https://prs.k8s.io/36853), [@verb](https://github.com/verb)) * `pause -v` will return build information for the pause binary. ([#56762](https://prs.k8s.io/56762), [@verb](https://github.com/verb)) # 3.0 * The pause container was rewritten entirely in C. ([#23009](https://prs.k8s.io/23009), [@uluyol](https://github.com/uluyol)) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-7628cd26f0dafa992a4ea43a6c68b9bcdbf056fca43ee32b40ab60cef4154c17", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: pause does not reap zombie processes using the default pause container provided by What you expected to happen: should include the up to date pause code to reap zombie processes when using docker = 1.13.1 found here How to reproduce it (as minimally and precisely as possible): a.out will leave a zombie process that is not cleaned up Anything else we need to know?: Building the pause container from master solves this issue Related: Environment: Kubernetes version (use ): 1.7.0+ Cloud provider or hardware configuration**: N/A OS (e.g. from /etc/os-release): CentOS 7 Kernel (e.g. ): 4.10.13+ Install tools: Others: docker = 1.13.1\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\ni get a simliar problem when i run crond service in pod container, every day it makes some [anacron] zombie progresses UID PID PPID C STIME TTY TIME CMD root 1 0 0 Nov14 ? 00:00:00 /pause root 7 0 0 Nov14 ? 00:00:00 /usr/local/bin/dumb-init /usr/lo root 13 7 0 Nov14 ? 00:00:00 nginx: master process /usr/local nobody 21 13 0 Nov14 ? 00:00:01 nginx: worker process nobody 22 13 0 Nov14 ? 00:00:07 nginx: worker process nobody 23 13 0 Nov14 ? 00:00:07 nginx: worker process nobody 24 13 0 Nov14 ? 00:00:05 nginx: worker process root 77 1 0 Nov14 ? 00:00:00 [anacron] root 1 0 00:01 ? 00:00:00 [anacron] <defunctroot 1 0 01:01 ? 00:00:00 [anacron] <defunctroot 1 0 02:01 ?", "commid": "kubernetes_issue_50865", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-41b5179627ef86c9a91dbcf09a96b05e9c90723006afbea58ab7f45d27835300", "query": "<ins> # 3.1 * The pause container gains a signal handler to clean up orphaned zombie processes. ([#36853](https://prs.k8s.io/36853), [@verb](https://github.com/verb)) * `pause -v` will return build information for the pause binary. ([#56762](https://prs.k8s.io/56762), [@verb](https://github.com/verb)) # 3.0 * The pause container was rewritten entirely in C. ([#23009](https://prs.k8s.io/23009), [@uluyol](https://github.com/uluyol)) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-6179feaaee46a15cd909bb088c82657b9b59fba8efdee1296995076588512032", "text": "00:00:00 [anacron] <defunctroot 1 0 03:01 ? 00:00:00 [anacron] <defunctroot 0 0 11:49 ? 00:00:00 /bin/bash root 0 1 19:15 ? 00:00:00 /bin/bash root 0 19:15 ? 00:00:00 ps -ef !\nDo we know why this was never resolved / was never deployed?\nI just fought through this issue with a rabbitmq helm chart. I had to custom build a pause container from master to fix it. The rabbitmq helm chart uses for its liveness checks. It's a thin wrapper around a call to the rabbitmq-server daemon, which is not PID 1 (/pause is PID 1). The rabbitmq-server process forks some children to do the work and then they exit. Since the pause-amd64:3.0 is not reaping, those processes stick around as zombies. The liveness check runs every 5 seconds. After about 4 hours, there are about 27K zombies and the node begins failing to launch new containers because it's starved for resources. The pause container built from current master fixes that behavior, no zombies at all in the container.\nThe plan is to build a new version of pause-amd64 and then update the image referenced by Kubernetes. This means the default image will change in the next Kubernetes release. We can make the new image available once the freeze lifts and we can merge .\nLooks like this made it into 1.10", "commid": "kubernetes_issue_50865", "tokennum": 336}], "negative_passages": []}
{"query_id": "q-en-kubernetes-41bd3dac3b588b5cffd6edfdbc78c1b12eee3a23ac1fb90a11187595aa309611", "query": "Spec: api.ServiceSpec{ Ports: []api.ServicePort{ { <del> Name:     \"default\", Protocol: api.Protocol(\"UDP\"), Port:     14, </del> <ins> Name:       \"default\", Protocol:   api.Protocol(\"UDP\"), Port:       14, TargetPort: util.NewIntOrStringFromInt(14), </ins> }, }, Selector: map[string]string{\"func\": \"stream\"}, Type:     api.ServiceTypeLoadBalancer, }, }, <del> expected: \"you will also need to explicitly open a firewall\", status:   200, </del> <ins> status: 200, </ins> }, }", "positive_passages": [{"docid": "doc-en-kubernetes-9d5ff2ec60db4b621aa04c218edf9e88ebba3dc541b6528b009593e479ccf9f2", "text": "This was broken by , and therefore broken in as well. Any fix should be offered as a cherry pick so \"make release\" is clean there.\nI went ahead and worked something up for this this morning, to get Shippable builds back on the rails.", "commid": "kubernetes_issue_11105", "tokennum": 53}], "negative_passages": []}
{"query_id": "q-en-kubernetes-41d25a233026a747dd19c4f68e2a228b48f0d367469dd6ee6db70dd3cfe4398a", "query": "func TestSecretForDockerRegistryGenerate(t *testing.T) { username, password, email, server := \"test-user\", \"test-password\", \"test-user@example.org\", \"https://index.docker.io/v1/\" <del> secretData, err := handleDockercfgContent(username, password, email, server) </del> <ins> secretData, err := handleDockerCfgJsonContent(username, password, email, server) </ins> if err != nil { t.Errorf(\"unexpected error: %v\", err) } <del> secretDataNoEmail, err := handleDockercfgContent(username, password, \"\", server) </del> <ins> secretDataNoEmail, err := handleDockerCfgJsonContent(username, password, \"\", server) </ins> if err != nil { t.Errorf(\"unexpected error: %v\", err) }", "positive_passages": [{"docid": "doc-en-kubernetes-4279a6f285666ec67ce8924ca9393c19176af7de5707dd42a5f4c239ba12ead2", "text": "/kind bug We're having trouble retrieving images from a private registry on DockerCloud. For nearly a year the following has worked flawlessly. Last Friday I pulled down the 1.9.0 CLI (via brew) and since then have not been able to access any image in a private registry on DockerCloud. I've tried this on 10+ brand new clusters created with kops v1.8.0. The Kubernetes cluster version have been 1.8.0, 1.8.4, 1.8.5 and 1.9.0 (which is not supported by kops yet) and all exhibit the same problem. We create the secret as such: And verify it using: Which yields: And create a test service with with these contents: The pod fails immediatly with: I've reviewed the 1.9.0 release notes and nothing jumps out as the root cause. For reference I've tried putting quotes around the value when creating the secret to no avail. I've also tried prefixing the value with , so the full value would read: also to no avail. Environment: Kubernetes version: Cloud provider and installation info: AWS cluster built with Kops 1.8.0, using (to isolate this issue) nearly the default settings for everything.\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI have same problem, and I \"solved\" it creating a docker-registry secret in an old kubernetes version and pasting it on new kubernetes\nI'm recently (I know it worked perfectly about last month) facing issues with as well. For me it ended in a similar manner saying: I was able to confirm, that this is a kubernetes CLI related issue and not end user. Based on and this I was able to create properly formatted auth information looking like this: . When encoding this one-liner using (MacOS workstation) and apply like this works fine and images can be pulled from private repository again.", "commid": "kubernetes_issue_57427", "tokennum": 466}], "negative_passages": []}
{"query_id": "q-en-kubernetes-41d25a233026a747dd19c4f68e2a228b48f0d367469dd6ee6db70dd3cfe4398a", "query": "func TestSecretForDockerRegistryGenerate(t *testing.T) { username, password, email, server := \"test-user\", \"test-password\", \"test-user@example.org\", \"https://index.docker.io/v1/\" <del> secretData, err := handleDockercfgContent(username, password, email, server) </del> <ins> secretData, err := handleDockerCfgJsonContent(username, password, email, server) </ins> if err != nil { t.Errorf(\"unexpected error: %v\", err) } <del> secretDataNoEmail, err := handleDockercfgContent(username, password, \"\", server) </del> <ins> secretDataNoEmail, err := handleDockerCfgJsonContent(username, password, \"\", server) </ins> if err != nil { t.Errorf(\"unexpected error: %v\", err) }", "positive_passages": [{"docid": "doc-en-kubernetes-784638a373a6d25c569537512411337ba05226e31cffa99d23b394dffb534564", "text": "However this breaks all automation and can't be considered as solution Confirmed working with kubectl 1.8.5 and server 1.8.4 (guess 1.7.9 as well)\nlooks like there's an extra \"auths\" element when adding the secret using 1.9 kubectl\nAdded in /assign\nMany thanks for the quick fix on this. Any idea when this might get rolled out? Also, it might be a good idea if this was to the known issue list for v1.9.0. It would have saved us a bunch of time trying to track down the root cause. Just trying to make sure no one else needs to do the same.\nlinking to the \"v1.9.0 known issues\" list\nack, asking Mehdy since he is the patch manager for v1.9 branch. Mehdy, any idea when we can ship 1.9.1 with this fix?\nworkarounds for folks until 1.9.1 is released: if you have a .dockerconfigjson for your private registry already, you can manually specify the type and data key (e.g. ) if you don't have a .dockerconfigjson file already, you can fix up the secret produced by manually: the type from to the data key from to the modified secret with\n1 will be released tomorrow\nI can confirm solution works, thanks so much!\nI am still having issues in 1.9.1. This worked in the 1.8.x branches: results in the following error:\nyou have to remove the gitlab-registry secret before you can apply an update... type is immutable, and the fix in 1.9.1 required changing the type of the secret", "commid": "kubernetes_issue_57427", "tokennum": 370}], "negative_passages": []}
{"query_id": "q-en-kubernetes-41e9f63aa088b03f70466764c3b7a0c69f35ad24914d6fff1533c7530dfc5ce7", "query": "} require.NoError(t, registerAPIService(ctx, client, groupVersion, service)) <del> defer func() { require.NoError(t, unregisterAPIService(ctx, client, groupVersion)) }() </del> <ins> groupVersions = append(groupVersions, groupVersion) </ins> } // Keep repeatedly fetching document from aggregator. // Check to see if it contains our service within a reasonable amount of time require.NoError(t, WaitForGroups(ctx, client, basicTestGroupWithFixup)) <ins> require.NoError(t, WaitForRootPaths(t, ctx, client, sets.New(\"/apis/\"+basicTestGroup.Name), nil)) // Unregister and ensure the group gets dropped from root paths for _, groupVersion := range groupVersions { require.NoError(t, unregisterAPIService(ctx, client, groupVersion)) } require.NoError(t, WaitForRootPaths(t, ctx, client, nil, sets.New(\"/apis/\"+basicTestGroup.Name))) </ins> } func runTestCases(t *testing.T, cases []testCase) {", "positive_passages": [{"docid": "doc-en-kubernetes-a36678f387087dd8252401a5249426873ced2ebb26644cae4efea96ce80ca1f6", "text": "reported that conformance testing with the latest version of sonobuoy against a version 1.29.0-alpha.3 cluster fails on the support the 1.17 Sample API Server using the current Aggregator test: , related to I found the reason why the test is working fine in Kubernetes CI jobs but fails with sonobuoy is because the service account used by sonobuoy \"sonobuoy-serviceaccount\" doesn't have read permission of the non-resource url \"/\", which is used by the test to confirm the removal of group path: The permission of \"sonobuoy-serviceaccount\" is as below: There may be two ways to fix it: the RBAC rule of sonobuoy to include \"get\" of \"/\". However, could other test runners encounter this issue? Is there a doc listing the required permissions for running e2e tests? the e2e to skip checking the removal of the group path if the service account doesn't have permission to access the root path. Which way do we usually prefer? Running e2e with sonobuoy should succeed. a v1.29.0-alpha.3 cluster. No response <details</details<details</details<details</details<details</details<details</details<details</details\nimplemented this solution.\n/sig api-machinery\nthank you for opening this issue and working on a solution. I'm probably not the right person to decide on which solution is preferred. From my perspective, either solution is fine.\nNote: Sonobuoy is not owned by any Kubernetes SIG. At most it is between SIG Architecture and the CNCF to choose whether to recommend it for running tests. SIG Testing owns the e2e image that sonobuoy can be used to schedule but not sonobuoy. IMHO this is a bug in running the tests via a pod, which is not how we develop the tests (they're run outside the cluster, by a cluster admin account typically). I would say 1) is the correct answer. xref: /sig architecture /sig testing /triage accepted cc\nthanks for your comment. I guess 1) means non of the existing sonobuoy versions can pass K8s conformance test against a cluster 1.29.0-alpha3, as the RBAC rule is hardcoded.", "commid": "kubernetes_issue_121985", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-41e9f63aa088b03f70466764c3b7a0c69f35ad24914d6fff1533c7530dfc5ce7", "query": "} require.NoError(t, registerAPIService(ctx, client, groupVersion, service)) <del> defer func() { require.NoError(t, unregisterAPIService(ctx, client, groupVersion)) }() </del> <ins> groupVersions = append(groupVersions, groupVersion) </ins> } // Keep repeatedly fetching document from aggregator. // Check to see if it contains our service within a reasonable amount of time require.NoError(t, WaitForGroups(ctx, client, basicTestGroupWithFixup)) <ins> require.NoError(t, WaitForRootPaths(t, ctx, client, sets.New(\"/apis/\"+basicTestGroup.Name), nil)) // Unregister and ensure the group gets dropped from root paths for _, groupVersion := range groupVersions { require.NoError(t, unregisterAPIService(ctx, client, groupVersion)) } require.NoError(t, WaitForRootPaths(t, ctx, client, nil, sets.New(\"/apis/\"+basicTestGroup.Name))) </ins> } func runTestCases(t *testing.T, cases []testCase) {", "positive_passages": [{"docid": "doc-en-kubernetes-4545476cbce0605bfe46d5a01c41b8f4cf7b5ac07772bfb1748611bc506e90ef", "text": "I will file an issue to sonobuoy first.\nquestion here is what are the set of client permissions required to run the conformance suite? perhaps a level of access or a more granular recommendation should be documented. what is your take on the root path requirement as approver for: EDIT: slack thread:\nI agree, we already require e.g. privileged pods for a long time in conformance tests and we should make it clear that we expect a highly privileged client.\n+1 for what is saying, that we should expect that the user running the tests has required permissions. These tests are not built for being run unprivileged.\ni wanted to PR the admin note in our conformance docs under sig-arch, but then i saw this: so broke this guarantee. sounds like SIG Arch needs to comment.\nThis statement surprises me. Root discovery is one of the least-privileged permissions you can have on a cluster. For years this was even open for unauthorized users on the internet (if your api endpoint has been exposed). In other words, just add the permission. While thinking about it, it is surprising that the user in question does not have this access already. Don't we allow that for every authorized user?\nIn contrast, I hope that lots of privileged operations are tested by conformance today. If we don't test things like admission webhooks for example, we have much bigger problems. And admission webhooks are basically equivalent to cluster-admin.\nthat is outdated, we use hostNetwork pods one some of the tests IIRC\nlooks like we don't. before this ticket, i was under the impression that the conformance suite already requires admin and that all testers (like Sonobuoy) use admin level credentials. it is non-privileged (e.g., does not require root on nodes, access to raw network interfaces, or cluster admin permissions) looks like we may have to change that sentence completely.\nWould have expected it here: The PR in question explicitly fixes the result returned by . If that is part of conformance (IMO it should), every conformance test needs access it obviously. Whether we require admin, or we add it manually, either would work.", "commid": "kubernetes_issue_121985", "tokennum": 474}], "negative_passages": []}
{"query_id": "q-en-kubernetes-41e9f63aa088b03f70466764c3b7a0c69f35ad24914d6fff1533c7530dfc5ce7", "query": "} require.NoError(t, registerAPIService(ctx, client, groupVersion, service)) <del> defer func() { require.NoError(t, unregisterAPIService(ctx, client, groupVersion)) }() </del> <ins> groupVersions = append(groupVersions, groupVersion) </ins> } // Keep repeatedly fetching document from aggregator. // Check to see if it contains our service within a reasonable amount of time require.NoError(t, WaitForGroups(ctx, client, basicTestGroupWithFixup)) <ins> require.NoError(t, WaitForRootPaths(t, ctx, client, sets.New(\"/apis/\"+basicTestGroup.Name), nil)) // Unregister and ensure the group gets dropped from root paths for _, groupVersion := range groupVersions { require.NoError(t, unregisterAPIService(ctx, client, groupVersion)) } require.NoError(t, WaitForRootPaths(t, ctx, client, nil, sets.New(\"/apis/\"+basicTestGroup.Name))) </ins> } func runTestCases(t *testing.T, cases []testCase) {", "positive_passages": [{"docid": "doc-en-kubernetes-06abc1218304c92779dae2744e33107a4d26263c1c54e4453f3f92a1949c2aa2", "text": "adding to milestone and making release blocking ... we should not release 1.29 in a state that the most commonly used conformance tool will fail\nIMO we should clarify the state and go fix the tool, but we should keep the test and we should NOT add skip. Conformance docs are not a release artifact, and sonobuoy release lifecycle is not a conformance artifact. If we can't get sonobuoy working in a reasonable time, we already know the tests can be run by scheduling the image (which is ours) directly with kubectl instead and we can document that in the upstream conformance docs. We need to fix the for this image: ,%20master%20(dev) And it should probably be to release-blocking in the future.\nit looks like the e2e change made in was not consciously made part of conformance, it was just trying to functionally test the bugfix being made. For 1.29, I think we should revert the change to and make an integration test that validates the fix instead. We can revisit whether content of is part of conformance or not for 1.30\nI opened to revert the e2e change and move the functional test to an integration test\nFiled to try to get the image job passing again.\nWe probably need another issue to track 1.30 follow-up?\nIf no one has done it, I could create another issue and follow up with the items that have been discussed here: outdated privilege requirement in commonly used conformance tools like sonobuoy aware of the required priviledge to avoid similar situations in the future. permission of GET \"/\" to authorized users via the role for root discovery.", "commid": "kubernetes_issue_121985", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-41eca6aa62720a1c353d5dffae2b312a913ba7f68dcb6c2cf2a6eb9a159287da", "query": "func TestCheckVolumeFSResize(t *testing.T) { mode := v1.PersistentVolumeFilesystem <del> pv := &v1.PersistentVolume{ ObjectMeta: metav1.ObjectMeta{ Name: \"dswp-test-volume-name\", </del> <ins> setCapacity := func(pv *v1.PersistentVolume, pvc *v1.PersistentVolumeClaim, capacity int) { pv.Spec.Capacity = volumeCapacity(capacity) pvc.Spec.Resources.Requests = volumeCapacity(capacity) } testcases := []struct { resize       func(*testing.T, *v1.PersistentVolume, *v1.PersistentVolumeClaim, *desiredStateOfWorldPopulator) verify       func(*testing.T, []v1.UniqueVolumeName, v1.UniqueVolumeName) enableResize bool readOnlyVol  bool }{ { // No resize request for volume, volumes in ASW shouldn't be marked as fsResizeRequired resize: func(*testing.T, *v1.PersistentVolume, *v1.PersistentVolumeClaim, *desiredStateOfWorldPopulator) { }, verify: func(t *testing.T, vols []v1.UniqueVolumeName, _ v1.UniqueVolumeName) { if len(vols) > 0 { t.Errorf(\"No resize request for any volumes, but found resize required volumes in ASW: %v\", vols) } }, enableResize: true, </ins> }, <del> Spec: v1.PersistentVolumeSpec{ PersistentVolumeSource: v1.PersistentVolumeSource{RBD: &v1.RBDPersistentVolumeSource{}}, Capacity:               volumeCapacity(1), ClaimRef:               &v1.ObjectReference{Namespace: \"ns\", Name: \"file-bound\"}, VolumeMode:             &mode, </del> <ins> { // Disable the feature gate, so volume shouldn't be marked as fsResizeRequired resize: func(_ *testing.T, pv *v1.PersistentVolume, pvc *v1.PersistentVolumeClaim, _ *desiredStateOfWorldPopulator) { setCapacity(pv, pvc, 2) }, verify: func(t *testing.T, vols []v1.UniqueVolumeName, _ v1.UniqueVolumeName) { if len(vols) > 0 { t.Errorf(\"Feature gate disabled, but found resize required volumes in ASW: %v\", vols) } }, enableResize: false, </ins> }, <del> } pvc := &v1.PersistentVolumeClaim{ Spec: v1.PersistentVolumeClaimSpec{ VolumeName: \"dswp-test-volume-name\", Resources: v1.ResourceRequirements{ Requests: volumeCapacity(1), </del> <ins> { // Make volume used as ReadOnly, so volume shouldn't be marked as fsResizeRequired resize: func(_ *testing.T, pv *v1.PersistentVolume, pvc *v1.PersistentVolumeClaim, _ *desiredStateOfWorldPopulator) { setCapacity(pv, pvc, 2) </ins> }, <ins> verify: func(t *testing.T, vols []v1.UniqueVolumeName, _ v1.UniqueVolumeName) { if len(vols) > 0 { t.Errorf(\"volume mounted as ReadOnly, but found resize required volumes in ASW: %v\", vols) } }, readOnlyVol:  true, enableResize: true, </ins> }, <del> Status: v1.PersistentVolumeClaimStatus{ Phase:    v1.ClaimBound, Capacity: volumeCapacity(1), </del> <ins> { // Clear ASW, so volume shouldn't be marked as fsResizeRequired because they are not mounted resize: func(_ *testing.T, pv *v1.PersistentVolume, pvc *v1.PersistentVolumeClaim, dswp *desiredStateOfWorldPopulator) { setCapacity(pv, pvc, 2) clearASW(dswp.actualStateOfWorld, dswp.desiredStateOfWorld, t) }, verify: func(t *testing.T, vols []v1.UniqueVolumeName, _ v1.UniqueVolumeName) { if len(vols) > 0 { t.Errorf(\"volume hasn't been mounted, but found resize required volumes in ASW: %v\", vols) } }, enableResize: true, </ins> }, <del> } dswp, fakePodManager, fakeDSW := createDswpWithVolume(t, pv, pvc) fakeASW := dswp.actualStateOfWorld // create pod containers := []v1.Container{ </del> { <del> VolumeMounts: []v1.VolumeMount{ { Name:      \"dswp-test-volume-name\", MountPath: \"/mnt\", }, </del> <ins> // volume in ASW should be marked as fsResizeRequired resize: func(_ *testing.T, pv *v1.PersistentVolume, pvc *v1.PersistentVolumeClaim, _ *desiredStateOfWorldPopulator) { setCapacity(pv, pvc, 2) }, verify: func(t *testing.T, vols []v1.UniqueVolumeName, volName v1.UniqueVolumeName) { if len(vols) == 0 { t.Fatalf(\"Request resize for volume, but volume in ASW hasn't been marked as fsResizeRequired\") } if len(vols) != 1 { t.Errorf(\"Some unexpected volumes are marked as fsResizeRequired: %v\", vols) } if vols[0] != volName { t.Fatalf(\"Mark wrong volume as fsResizeRequired: %s\", vols[0]) } </ins> }, <ins> enableResize: true, </ins> }, } <del> pod := createPodWithVolume(\"dswp-test-pod\", \"dswp-test-volume-name\", \"file-bound\", containers) uniquePodName := types.UniquePodName(pod.UID) uniqueVolumeName := v1.UniqueVolumeName(\"fake-plugin/\" + pod.Spec.Volumes[0].Name) fakePodManager.AddPod(pod) // Fill the dsw to contains volumes and pods. dswp.findAndAddNewPods() reconcileASW(fakeASW, fakeDSW, t) </del> <ins> for _, tc := range testcases { pv := &v1.PersistentVolume{ ObjectMeta: metav1.ObjectMeta{ Name: \"dswp-test-volume-name\", }, Spec: v1.PersistentVolumeSpec{ PersistentVolumeSource: v1.PersistentVolumeSource{RBD: &v1.RBDPersistentVolumeSource{}}, Capacity:               volumeCapacity(1), ClaimRef:               &v1.ObjectReference{Namespace: \"ns\", Name: \"file-bound\"}, VolumeMode:             &mode, }, } pvc := &v1.PersistentVolumeClaim{ Spec: v1.PersistentVolumeClaimSpec{ VolumeName: pv.Name, Resources: v1.ResourceRequirements{ Requests: pv.Spec.Capacity, }, }, Status: v1.PersistentVolumeClaimStatus{ Phase:    v1.ClaimBound, Capacity: pv.Spec.Capacity, }, } </ins> <del> // No resize request for volume, volumes in ASW shouldn't be marked as fsResizeRequired. defer featuregatetesting.SetFeatureGateDuringTest(t, utilfeature.DefaultFeatureGate, features.ExpandInUsePersistentVolumes, true)() resizeRequiredVolumes := reprocess(dswp, uniquePodName, fakeDSW, fakeASW) if len(resizeRequiredVolumes) > 0 { t.Fatalf(\"No resize request for any volumes, but found resize required volumes in ASW: %v\", resizeRequiredVolumes) } </del> <ins> dswp, fakePodManager, fakeDSW := createDswpWithVolume(t, pv, pvc) fakeASW := dswp.actualStateOfWorld // create pod containers := []v1.Container{ { VolumeMounts: []v1.VolumeMount{ { Name:      pv.Name, MountPath: \"/mnt\", ReadOnly:  tc.readOnlyVol, }, }, }, } pod := createPodWithVolume(\"dswp-test-pod\", \"dswp-test-volume-name\", \"file-bound\", containers) uniquePodName := types.UniquePodName(pod.UID) uniqueVolumeName := v1.UniqueVolumeName(\"fake-plugin/\" + pod.Spec.Volumes[0].Name) </ins> <del> // Add a resize request to volume. pv.Spec.Capacity = volumeCapacity(2) pvc.Spec.Resources.Requests = volumeCapacity(2) </del> <ins> fakePodManager.AddPod(pod) // Fill the dsw to contains volumes and pods. dswp.findAndAddNewPods() reconcileASW(fakeASW, fakeDSW, t) </ins> <del> // Disable the feature gate, so volume shouldn't be marked as fsResizeRequired. defer featuregatetesting.SetFeatureGateDuringTest(t, utilfeature.DefaultFeatureGate, features.ExpandInUsePersistentVolumes, false)() resizeRequiredVolumes = reprocess(dswp, uniquePodName, fakeDSW, fakeASW) if len(resizeRequiredVolumes) > 0 { t.Fatalf(\"Feature gate disabled, but found resize required volumes in ASW: %v\", resizeRequiredVolumes) } </del> <ins> func() { defer featuregatetesting.SetFeatureGateDuringTest(t, utilfeature.DefaultFeatureGate, features.ExpandInUsePersistentVolumes, tc.enableResize)() </ins> <del> // Make volume used as ReadOnly, so volume shouldn't be marked as fsResizeRequired. defer featuregatetesting.SetFeatureGateDuringTest(t, utilfeature.DefaultFeatureGate, features.ExpandInUsePersistentVolumes, true)() pod.Spec.Containers[0].VolumeMounts[0].ReadOnly = true resizeRequiredVolumes = reprocess(dswp, uniquePodName, fakeDSW, fakeASW) if len(resizeRequiredVolumes) > 0 { t.Fatalf(\"volume mounted as ReadOnly, but found resize required volumes in ASW: %v\", resizeRequiredVolumes) } </del> <ins> tc.resize(t, pv, pvc, dswp) </ins> <del> // Clear ASW, so volume shouldn't be marked as fsResizeRequired because they are not mounted. pod.Spec.Containers[0].VolumeMounts[0].ReadOnly = false clearASW(fakeASW, fakeDSW, t) resizeRequiredVolumes = reprocess(dswp, uniquePodName, fakeDSW, fakeASW) if len(resizeRequiredVolumes) > 0 { t.Fatalf(\"volume hasn't been mounted, but found resize required volumes in ASW: %v\", resizeRequiredVolumes) } </del> <ins> resizeRequiredVolumes := reprocess(dswp, uniquePodName, fakeDSW, fakeASW) </ins> <del> // volume in ASW should be marked as fsResizeRequired. reconcileASW(fakeASW, fakeDSW, t) resizeRequiredVolumes = reprocess(dswp, uniquePodName, fakeDSW, fakeASW) if len(resizeRequiredVolumes) == 0 { t.Fatalf(\"Request resize for volume, but volume in ASW hasn't been marked as fsResizeRequired\") } if len(resizeRequiredVolumes) != 1 { t.Fatalf(\"Some unexpected volumes are marked as fsResizeRequired: %v\", resizeRequiredVolumes) } if resizeRequiredVolumes[0] != uniqueVolumeName { t.Fatalf(\"Mark wrong volume as fsResizeRequired: %s\", resizeRequiredVolumes[0]) </del> <ins> tc.verify(t, resizeRequiredVolumes, uniqueVolumeName) }() </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-e2a306502c13953a6abed9b24a426f5781d6f68d679664b0ba9d46cde514bf5f", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: These test cases are very hard to follow because they keep toggling the feature gates on and off, and subsequent test cases depend on the behavior of the previous. <!-- DO NOT EDIT BELOW THIS LINE --/kind bug\n/assign\nIssues 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\n/remove-lifecycle-stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nClosing 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\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/remove-lifecycle rotten\n/help\nThis request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nHey, I'd like to take this if nobody is working on it\nHi thanks for volunteering! Let us know if you have any questions", "commid": "kubernetes_issue_71105", "tokennum": 525}], "negative_passages": []}
{"query_id": "q-en-kubernetes-41f46c93bd5771a09726e91664b0b0107924f25fe92702b072d1ad00f7cc8857", "query": "MINION_TAG=\"${INSTANCE_PREFIX}-minion\" MINION_NAMES=($(eval echo ${INSTANCE_PREFIX}-minion-{1..${NUM_MINIONS}})) MINION_IP_RANGES=($(eval echo \"10.245.{1..${NUM_MINIONS}}.0/24\")) <del> MINION_SCOPES=\"\" </del> <ins> MINION_SCOPES=\"storage-ro,compute-rw\" </ins> # Increase the sleep interval value if concerned about API rate limits. 3, in seconds, is the default. POLL_SLEEP_INTERVAL=3 PORTAL_NET=\"10.0.0.0/16\"", "positive_passages": [{"docid": "doc-en-kubernetes-4cc03be8a4c78b1eefdd458c17e35e10d17eae1288a6e1bcb08b9d7d585d4633", "text": "07-02 and 13-02 No response No response /sig\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scalability\nI might be related to the npd.\nThe same test failures happening again on 25.02:\n/sig node\n/sig node /cc The restart of caused the flake. I also opened to track it in NPD repo.\nI missed this log. It is caused by oom. Adding some memory may help. I submitted to fix it. Does mean killing metrics-server?\n/remove-sig node Sorry, I misread the log. The NPD found the metric server is OOM. It is about the metrics server, not the NPD. Sorry for disturb. I may add some memory for metric-server and check why metric server memory changed. I heard that metrics server recently released a new version. I will check if it is related.\n/sig node\nOOM metrics shows the metric server is OOMed. This is odd, that only metrics-server-nanny is with a memory limit. It uses whose command is . metrics-server container has no memory limit, but it got killed by OOM. Does this indicate that the node is OOM? (edited)\nThe last run failed in node-problem-detector ContainerStateTerminated. I0227 05:03:31. ] PodStartupLatency: perc50: 14m29.018886827s, perc90: 28m44.625518807s, perc99: 32m2.19303496s; threshold 1h0m0s I0227 05:03:32. ]", "commid": "kubernetes_issue_123328", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-41f46c93bd5771a09726e91664b0b0107924f25fe92702b072d1ad00f7cc8857", "query": "MINION_TAG=\"${INSTANCE_PREFIX}-minion\" MINION_NAMES=($(eval echo ${INSTANCE_PREFIX}-minion-{1..${NUM_MINIONS}})) MINION_IP_RANGES=($(eval echo \"10.245.{1..${NUM_MINIONS}}.0/24\")) <del> MINION_SCOPES=\"\" </del> <ins> MINION_SCOPES=\"storage-ro,compute-rw\" </ins> # Increase the sleep interval value if concerned about API rate limits. 3, in seconds, is the default. POLL_SLEEP_INTERVAL=3 PORTAL_NET=\"10.0.0.0/16\"", "positive_passages": [{"docid": "doc-en-kubernetes-a11072f45f81b280dea24734413173747c87bdd472ce068bad905ce856d1cb81", "text": "Loaded restart count threshold overrides: map[coredns:2 fluentd-gcp:999 konnectivity-agent:2 kube-controller-manager:1 kube-proxy:2 kube-scheduler:1 l7-lb-controller:1 metadata-proxy:2 prometheus-to-sd-exporter:2] I0227 05:03:32. ] ClusterOOMsTracker: gathering cluster OOMs tracking measurement E0227 05:03:32. ] TestMetrics: [action gather failed for SystemPodMetrics measurement: restart counts violation: RestartCount(node-problem-detector-tgl8h, node-problem-detector)=1, want <= 0; RestartCount(node-problem-detector-vpsmz, node-problem-detector)=1, want <= 0] I0227 05:03:32. ] Step \"[step: 29] gathering measurements\" ended W0227 05:03:32. ] Got errors during step execution: [measurement call TestMetrics - TestMetrics error: [action gather failed for SystemPodMetrics measurement: restart counts violation: RestartCount(node-problem-detector-tgl8h, node-problem-detector)=1, want <= 0; RestartCount(node-problem-detector-vpsmz, node-problem-detector)=1, want <= 0]] I0227 05:03:32. ] Waiting for the chaos monkey subroutine to end... I0227 05:03:32. ] Chaos monkey ended. I0227 05:03:32. ] I0227 05:03:32. ] Stopping DnsLookupLatency probe... I0227 05:03:47. ] Stopping InClusterNetworkLatency probe... I0227 05:04:22. ] Resources cleanup time: 50.539700215s E0227 05:04:22. ]\nE0227 05:04:22. ] Test Finished E0227 05:04:22. ] Test: E0227 05:04:22. ] Status: Fail E0227 05:04:22. ]", "commid": "kubernetes_issue_123328", "tokennum": 491}], "negative_passages": []}
{"query_id": "q-en-kubernetes-41f46c93bd5771a09726e91664b0b0107924f25fe92702b072d1ad00f7cc8857", "query": "MINION_TAG=\"${INSTANCE_PREFIX}-minion\" MINION_NAMES=($(eval echo ${INSTANCE_PREFIX}-minion-{1..${NUM_MINIONS}})) MINION_IP_RANGES=($(eval echo \"10.245.{1..${NUM_MINIONS}}.0/24\")) <del> MINION_SCOPES=\"\" </del> <ins> MINION_SCOPES=\"storage-ro,compute-rw\" </ins> # Increase the sleep interval value if concerned about API rate limits. 3, in seconds, is the default. POLL_SLEEP_INTERVAL=3 PORTAL_NET=\"10.0.0.0/16\"", "positive_passages": [{"docid": "doc-en-kubernetes-8045aaa7c39478c40c58e17441fd375a472ca56f31885311d26bd40c11b2233d", "text": "Errors: [measurement call TestMetrics - TestMetrics error: [action gather failed for SystemPodMetrics measurement: restart counts violation: RestartCount(node-problem-detector-tgl8h, node-problem-detector)=1, want <= 0; RestartCount(node-problem-detector-vpsmz, node-problem-detector)=1, want <= 0]] E0227 05:04:22. ]\nI0227 05:04:22. ]\nI0227 05:04:22. ] Running testing/huge- I0227 05:04:22. ]", "commid": "kubernetes_issue_123328", "tokennum": 136}], "negative_passages": []}
{"query_id": "q-en-kubernetes-42002e64c76f20f79f11ef971e2ac6fc2fb2313807a470289ee934dd902a1ea2", "query": ") // ValidateLoadBalancerStatus validates required fields on a LoadBalancerStatus <del> func ValidateLoadBalancerStatus(status *core.LoadBalancerStatus, fldPath *field.Path) field.ErrorList { </del> <ins> func ValidateLoadBalancerStatus(status *core.LoadBalancerStatus, fldPath *field.Path, spec *core.ServiceSpec) field.ErrorList { </ins> allErrs := field.ErrorList{} <del> for i, ingress := range status.Ingress { idxPath := fldPath.Child(\"ingress\").Index(i) if len(ingress.IP) > 0 { if isIP := (netutils.ParseIPSloppy(ingress.IP) != nil); !isIP { allErrs = append(allErrs, field.Invalid(idxPath.Child(\"ip\"), ingress.IP, \"must be a valid IP address\")) } } if utilfeature.DefaultFeatureGate.Enabled(features.LoadBalancerIPMode) && ingress.IPMode == nil { </del> <ins> ingrPath := fldPath.Child(\"ingress\") if !utilfeature.DefaultFeatureGate.Enabled(features.AllowServiceLBStatusOnNonLB) && spec.Type != core.ServiceTypeLoadBalancer && len(status.Ingress) != 0 { allErrs = append(allErrs, field.Forbidden(ingrPath, \"may only be used when `spec.type` is 'LoadBalancer'\")) } else { for i, ingress := range status.Ingress { idxPath := ingrPath.Index(i) </ins> if len(ingress.IP) > 0 { <del> allErrs = append(allErrs, field.Required(idxPath.Child(\"ipMode\"), \"must be specified when `ip` is set\")) </del> <ins> if isIP := (netutils.ParseIPSloppy(ingress.IP) != nil); !isIP { allErrs = append(allErrs, field.Invalid(idxPath.Child(\"ip\"), ingress.IP, \"must be a valid IP address\")) } </ins> } <del> } else if ingress.IPMode != nil && len(ingress.IP) == 0 { allErrs = append(allErrs, field.Forbidden(idxPath.Child(\"ipMode\"), \"may not be specified when `ip` is not set\")) } else if ingress.IPMode != nil && !supportedLoadBalancerIPMode.Has(string(*ingress.IPMode)) { allErrs = append(allErrs, field.NotSupported(idxPath.Child(\"ipMode\"), ingress.IPMode, supportedLoadBalancerIPMode.List())) } if len(ingress.Hostname) > 0 { for _, msg := range validation.IsDNS1123Subdomain(ingress.Hostname) { allErrs = append(allErrs, field.Invalid(idxPath.Child(\"hostname\"), ingress.Hostname, msg)) </del> <ins> if utilfeature.DefaultFeatureGate.Enabled(features.LoadBalancerIPMode) && ingress.IPMode == nil { if len(ingress.IP) > 0 { allErrs = append(allErrs, field.Required(idxPath.Child(\"ipMode\"), \"must be specified when `ip` is set\")) } } else if ingress.IPMode != nil && len(ingress.IP) == 0 { allErrs = append(allErrs, field.Forbidden(idxPath.Child(\"ipMode\"), \"may not be specified when `ip` is not set\")) } else if ingress.IPMode != nil && !supportedLoadBalancerIPMode.Has(string(*ingress.IPMode)) { allErrs = append(allErrs, field.NotSupported(idxPath.Child(\"ipMode\"), ingress.IPMode, supportedLoadBalancerIPMode.List())) </ins> } <del> if isIP := (netutils.ParseIPSloppy(ingress.Hostname) != nil); isIP { allErrs = append(allErrs, field.Invalid(idxPath.Child(\"hostname\"), ingress.Hostname, \"must be a DNS name, not an IP address\")) </del> <ins> if len(ingress.Hostname) > 0 { for _, msg := range validation.IsDNS1123Subdomain(ingress.Hostname) { allErrs = append(allErrs, field.Invalid(idxPath.Child(\"hostname\"), ingress.Hostname, msg)) } if isIP := (netutils.ParseIPSloppy(ingress.Hostname) != nil); isIP { allErrs = append(allErrs, field.Invalid(idxPath.Child(\"hostname\"), ingress.Hostname, \"must be a DNS name, not an IP address\")) } </ins> } } }", "positive_passages": [{"docid": "doc-en-kubernetes-e021a9a686a92d83ba285392c70089f3a0813200ee010fb06825ed96dc15cfdb", "text": "xref I think this may be one of the few cases where we can actually change the behavior in a \"breaking\" way. User creates service with , is empty Controller or user updates the status subresource, sets (not wiped or validated, should be) User updates in any way, is wiped It's clear that the is not meant to be set when is not \"LoadBalancer\". The question is: 1) Fail validation? 2) Silently discard the value? 3) Warn and then discard the value? 4) Just warn and leave it. Because we allowed it in the past, but it is so volatile, I lean towards 3. and - the people most familair with this type. Edit: PrepareForUpdate() runs before warnings. So: (1) is easy (2) is easy (4) is slightly less easy than (2) (3) is slightly less easy than (4)\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nOMG change it to clusterIP as expected Status is wiped update status as ClusterIP ... and if I edit the service back to loadbalancer it keeps the status??\n/kind bug\n/retitle Service can be set when !=\nWe talked about this one at the SIG Network meeting today. suggested we use the feature gate for deprecation option to phase the current (problematic) functionality out.\n/triage accept\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /triage accept 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", "commid": "kubernetes_issue_119700", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-42c079551a889d222996920bf41873496a42d559e8487fa316159c2aa301c763", "query": "} } <ins> func printStatusAndLogsForNotReadyPods(c *client.Client, oldPods, newPods []*api.Pod) { printFn := func(id, log string, err error, previous bool) { prefix := \"Retrieving log for container\" if previous { prefix = \"Retrieving log for the last terminated container\" } if err != nil { Logf(\"%s %s, err: %v:n%sn\", prefix, id, log) } else { Logf(\"%s %s:n%sn\", prefix, id, log) } } for _, oldPod := range oldPods { for _, p := range newPods { if p.Namespace != oldPod.Namespace || p.Name != oldPod.Name { continue } if ok, _ := podRunningReady(p); !ok { Logf(\"Status for not ready pod %s/%s: %+v\", p.Namespace, p.Name, p.Status) // Print the log of the containers if pod is not running and ready. for _, container := range p.Status.ContainerStatuses { cIdentifer := fmt.Sprintf(\"%s/%s/%s\", p.Namespace, p.Name, container.Name) log, err := getPodLogs(c, p.Namespace, p.Name, container.Name) printFn(cIdentifer, log, err, false) // Get log from the previous container. if container.RestartCount > 0 { printFn(cIdentifer, log, err, true) } } } break } } } </ins> // rebootNode takes node name on provider through the following steps using c: //  - ensures the node is ready //  - ensures all pods on the node are running and ready", "positive_passages": [{"docid": "doc-en-kubernetes-cf37b0ab7a08d0e2457507bc271b1cb7d1e13fbaee3773971363bc32ae71b35b", "text": "We are running heapster, dns server, kube-proxy etc. in kube-system namespace. Some e2e tests try to make sure all those kube-system pods are at ready state before firing the real tests, others just simply ingore them. But both cases might cause e2e flakiness when some of those kube-system containers are in crashloop, for example, for heapster crashloop, for influxdb crashloop, etc. When such cases happen, the developer doesn't have much information on why since the nodes might be teared down. We should watch those kube-system pods, and onContainerFailure, we should collect the related logs. One simple way is using kubectl logs <Pod<Container--previous cc/\nis this related enough to and that you can bundle it in?\nThe logs from the pods should be retrieved via the api server. This is different from the kubelet logs. I'll upload a PR for this.\nGreat job It will be very helpful for debugging.", "commid": "kubernetes_issue_20099", "tokennum": 229}], "negative_passages": []}
{"query_id": "q-en-kubernetes-43111ce15215608c4ab3b42238ef8d1ca6b69d3bc0a8e8476cf194664227430d", "query": "// parameters, you'll run out of stack space before anything useful happens. Convert(src, dest interface{}, flags FieldMatchingFlags) error <ins> // DefaultConvert performs the default conversion, without calling a conversion func // on the current stack frame. This makes it safe to call from a conversion func. DefaultConvert(src, dest interface{}, flags FieldMatchingFlags) error </ins> // SrcTags and DestTags contain the struct tags that src and dest had, respectively. // If the enclosing object was not a struct, then these will contain no tags, of course. SrcTag() reflect.StructTag", "positive_passages": [{"docid": "doc-en-kubernetes-518f837785f17a5fd9706a6c0a0614adac703d65f6bb6045d79a025795dcb97b", "text": "Files storing latest versions for minors are not updated since infix was to the version string. Example Similar issues can be found in 1.25 and 1.24 builds (last 1.23 build infix so it has not happened there yet): I expect the files to be overwritten with newer version of the build. Manually run build job for one of the minors. No response Not related. Not related. No response No response No response No response\nI believe this may be also responsible for breaking kubemark tests: since they fail due to version mismatch\n/sig release\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority high 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\nThanks for raising the issue! /cc who is working on before\nI assume this will be fixed automatically with the next patches, because then we would compare with . Anyway, I think we should fix that intermediately by manually updating the version markers to match their correct version. I did that now for the bucket\nWe had to update the versions markers again, because those were pointing to two commits earlier and didn't include the Go updates. The latest version markers are: v1.24.12-35+ v1.25.8-37+ v1.26.3-41+\nlatest-1.27 has been affected by this as well. I updated it manually to v1.27.0-9+. See this thread for more details:\n/triage accepted\nThis should be fixed now, closing it. Feel free to reopen if we missed anything.\nThis issue is still present, see this Slack thread for more details: /reopen\nReopened this issue. <detailsIn response to : This issue is still present, see this Slack thread for more details: /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nWe have a similar situation with latest-1.28 which is currently pointing to: . This is one commit before the release commit: ! It's mostly like that the release step didn't update version markers, we should look into this.", "commid": "kubernetes_issue_117115", "tokennum": 486}], "negative_passages": []}
{"query_id": "q-en-kubernetes-43111ce15215608c4ab3b42238ef8d1ca6b69d3bc0a8e8476cf194664227430d", "query": "// parameters, you'll run out of stack space before anything useful happens. Convert(src, dest interface{}, flags FieldMatchingFlags) error <ins> // DefaultConvert performs the default conversion, without calling a conversion func // on the current stack frame. This makes it safe to call from a conversion func. DefaultConvert(src, dest interface{}, flags FieldMatchingFlags) error </ins> // SrcTags and DestTags contain the struct tags that src and dest had, respectively. // If the enclosing object was not a struct, then these will contain no tags, of course. SrcTag() reflect.StructTag", "positive_passages": [{"docid": "doc-en-kubernetes-5a00e106d863b6b2d6ffe122805a64f76a2709c3a46b9a75024b175401623671", "text": "As of now, I'm going to manually update this version marker to unblock 1.28.1 patch release. I'll also take a look into this. /assign\nThe PR that fixed this issue got reverted so this is still relevant: /reopen\nReopened this issue. <detailsIn response to : The PR that fixed this issue got reverted so this is still relevant: /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nWe're running into this issue again with stable-1.29 marker. It's currently pointing to which is It should instead point to I'm going to manually change it following the same procedure as the last time. Version marker updated to\nThis issue is labeled with but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release. You can: Confirm that this issue is still relevant with (org members only) Deprioritize it with or Close this issue with For more details on the triage process, see /remove-triage accepted\n/triage accepted\nSame issue for 1.30, where I had to update the version marker manually again.", "commid": "kubernetes_issue_117115", "tokennum": 278}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4316117c3882f5047aa18ff5944fc759747a35fec29976001b5f8e82875f0ae6", "query": "return utilfile.FileExists(pathname) } <ins> // EvalHostSymlinks returns the path name after evaluating symlinks func (mounter *Mounter) EvalHostSymlinks(pathname string) (string, error) { return filepath.EvalSymlinks(pathname) } </ins> // check whether hostPath is within volume path // this func will lock all intermediate subpath directories, need to close handle outside of this func after container started func lockAndCheckSubPath(volumePath, hostPath string) ([]uintptr, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-226c0928db9d5aa6f1446838b8788eb7c60cd41b1b8246f4bd1a4e2614bb7834", "text": "/kind bug Using , if a block device is symlinked to the discovery directory e.g. , then MapVolume will fail with since the containerized kubelet cannot see the path on host. is mounted by containerized kubelet, so if before we try to map the device we set devicePath to the evaluation of symlink and end up with a devicePath of , containerized kubelet will see the device and successfully map the device. Are there any issues with this solution? This is on Kubernetes 1.10\n/sig storage\nah yes containerized kubelet has many issues when dealing with symlinks. Check out Mounter.GetMode(), it calls a nsenter EvalSymlinks which should be able to do what you need. But actually, one thing to consider, is do you need to do the losetup on the host, or does inside the container work?\nYes it appears to work from inside the container, on the host I run which disappears after I delete the pod using the device. My understanding of running losetup in MapVolume is not that great but I suppose that as long as that /dev/loop0 is created we are fine. Thanks for the quick response, I'll create a PR using that function and tag you\nDoes it create it on the host or in the containerized kubelet? What happens when containerized kubelet is restarted? The purpose of losetup is to do \"refcounting\" on the block device to prevent possible naming collisions when devices are attached/detached under unhealthy conditions. Ie, if a device showed up as /dev/sdb and you gave that to a pod, and then for some reason it become unhealthy and disappeared (while the pod is still running), another device (maybe even another volume type) could get attached to the node and reuse /dev/sdb. Now the pod has access to a device it's not supposed to. With filesystem volumes, the refcounting is done with mount points, but for block device, loopback is the equivalent.\nIt is created on the host (and also visible in the container), and stays around through restart. I understand now, thank you.\nActually after I restart it becomes /vdb instead of /dev/vdb in the losetup output, idk what that is about.", "commid": "kubernetes_issue_65445", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4316117c3882f5047aa18ff5944fc759747a35fec29976001b5f8e82875f0ae6", "query": "return utilfile.FileExists(pathname) } <ins> // EvalHostSymlinks returns the path name after evaluating symlinks func (mounter *Mounter) EvalHostSymlinks(pathname string) (string, error) { return filepath.EvalSymlinks(pathname) } </ins> // check whether hostPath is within volume path // this func will lock all intermediate subpath directories, need to close handle outside of this func after container started func lockAndCheckSubPath(volumePath, hostPath string) ([]uintptr, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-e6271b0ba1dda755d5bb536a727016a621c7c29c599386bc1e9c22a230980cbf", "text": "There is no such thing as /vdb and /dev/vdb is still intact of course. Seems inconsequential since it is disappearing after all pods using the device are deleted, i.e. it's still serving as a refcounter", "commid": "kubernetes_issue_65445", "tokennum": 55}], "negative_passages": []}
{"query_id": "q-en-kubernetes-432bd5b639184b08c0db0fff3ce866519f2b53caabbf5caebb96e18553f3d65f", "query": "endpointSlicesEnabled := utilfeature.DefaultFeatureGate.Enabled(features.EndpointSliceProxying) <ins> var incorrectAddresses []string nodePortAddresses, incorrectAddresses = utilproxy.FilterIncorrectCIDRVersion(nodePortAddresses, isIPv6) if len(incorrectAddresses) > 0 { klog.Warning(\"NodePortAddresses of wrong family; \", incorrectAddresses) } </ins> proxier := &Proxier{ portsMap:              make(map[utilproxy.LocalPort]utilproxy.Closeable), serviceMap:            make(proxy.ServiceMap),", "positive_passages": [{"docid": "doc-en-kubernetes-10e0800334eabc101ba3e719bde6addc76496fd00734e09bb571fcc5b6be7d48", "text": "What happened: In a dual-stack cluster when specifying both ipv6 and ipv4 addresses in the entries are inserted in ipvs for the ipv6 nodeports but with an invalid ipv4 address; The example shows the ipv4 loopback address but any ipv4 address in will cause a faulty entry. What you expected to happen: No ipv4 entry shall be inserted for the ipv6 nodeport. How to reproduce it (as minimally and precisely as possible): Configure with both ipv4 and ipv6 addresses Bring up a dual-stack cluster with proxy-mode Create a service with ipFamily:IPv6 Do Anything else we need to know?: Proxy-mode=iptables seems to work. With no ipv4 entries are inserted for ipv6 nodeports. In it is recommended to use but doing so makes kube-proxy enter rules for address (in addition to \"127.0.0.1\"). While these entries cause no harm they can't be used and should not be there. These entries are created for both proxy-mode \"iptables\" and \"ipvs\". This should not be handled in this issue but in another (new) issue if needed. Example; Environment: Kubernetes version (use ):Cloud provider or hardware configuration: Kvm's on Ubuntu OS (e.g: ): xcluster Kernel (e.g. ):Install tools: \"from scratch\" Network plugin and version (if this is a network-related bug): calico/cni:v3.12.0 Others: /sig network\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/area ipvs /area ipv6\n/remove-triage unresolved /assign I take this myself if no one objects.\nThe ipv4 address is obviously a ipv4-converted ipv6 from .\nAccording to the code here (), we may need to filter the before passing it to .\nLooks that that's it. Please go ahead and make a PR, or I can do it if you prefer. I will help test the PR of course. Here are some review comments right away; Use v1.IPFamily as param to the filter function rather than The filter function seem usable and generic and may be placed in some \"util\" package, but leave it as-is and let the maintainers decide that.\nHi feel free to send a PR please, as you have took this already :) I'd like to help review it!\nThe \"addresses\" are really CIDRs which make the fix even simpler.", "commid": "kubernetes_issue_89923", "tokennum": 576}], "negative_passages": []}
{"query_id": "q-en-kubernetes-432c0a75f6e7d161a38dbfcf4f68e850fe50967a5a48d0e55af87d31cf9f7a08", "query": "fi local -r src_dir=\"${KUBE_HOME}/kube-manifests/kubernetes/gci-trusty\" <del> if [[ -n \"${KUBE_USER:-}\" || ! -e /etc/srv/kubernetes/abac-authz-policy.jsonl ]]; then local -r abac_policy_json=\"${src_dir}/abac-authz-policy.jsonl\" remove-salt-config-comments \"${abac_policy_json}\" if [[ -n \"${KUBE_USER:-}\" ]]; then sed -i -e \"s/{{kube_user}}/${KUBE_USER}/g\" \"${abac_policy_json}\" else sed -i -e \"/{{kube_user}}/d\" \"${abac_policy_json}\" fi cp \"${abac_policy_json}\" /etc/srv/kubernetes/ fi </del> src_file=\"${src_dir}/kube-apiserver.manifest\" remove-salt-config-comments \"${src_file}\" # Evaluate variables.", "positive_passages": [{"docid": "doc-en-kubernetes-19a61d82ec14336213ef377c4e39e11807c2ce9673880ce3d82a192d5a783624", "text": "Typically, the dns and dashboard is in crash loop. Ref cc\nif you check the file, does it contain lines like ?\nPrevious comment is ref: from I'll copy that to container-linux as well.", "commid": "kubernetes_issue_39395", "tokennum": 44}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4365c17191a3c7ecdd591d6f31381287d325ba7bb250098bfc31aaae9f234e9c", "query": "SecurityOpt: fmtSecurityOpts, } <del> // There is no /etc/resolv.conf in Windows, DNS and DNSSearch options would have to be passed to Docker runtime instead if runtime.GOOS == \"windows\" { hc.DNS = opts.DNS hc.DNSSearch = opts.DNSSearch } </del> <ins> updateHostConfig(hc) </ins> // Set sysctls if requested if container.Name == PodInfraContainerName {", "positive_passages": [{"docid": "doc-en-kubernetes-2c477631a31f290ae271a7ca0a83a97399cbf63c4cfd883674b6ddce7387fc19", "text": "What happened: Latest kubelet + Windows Docker version 1.14.0-dev refused to start any containers, error output: \"invalid option: Windows does not support MemorySwap\" How to reproduce it (as minimally and precisely as possible): It's always reproducible with Windows Docker 1.14.0-dev + latest kubelet code base. Anything else do we need to know: It didn't happen for Windows Docker 1.12.2-cs2-ws-beta. The reason behind the issue was because new code was for Windows Docker to check Resources parameters, it doesn't accept a non-zero value for MemorySwap: But kubelet was default to set an unlimited (-1) value. The issue was gone in my setup after applied a private fix to disable MemorySwap by set it to zero for Windows.", "commid": "kubernetes_issue_39003", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-43982a424ea568c0b87027b7d272023ab41597a46694a24ad0c151d6969376d8", "query": "} _, err := createPodPreset(f.ClientSet, f.Namespace.Name, pip) <ins> if errors.IsNotFound(err) { framework.Skipf(\"podpresets requires k8s.io/api/settings/v1alpha1 to be enabled\") } </ins> Expect(err).NotTo(HaveOccurred()) By(\"creating the pod\")", "positive_passages": [{"docid": "doc-en-kubernetes-fe3f123845ebc52583ef0b18b019ca5c9cf0487720bfc7eeadb38f7ce5aa77c7", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: is consistently failing because of PodPreset feature tests, which require settings/v1alpha1, which is no longer enabled by default What you expected to happen: . How to reproduce it (as minimally and precisely as possible): . Anything else we need to know?: This was caused by and kubernetes/test-infra Environment: . Kubernetes version (use ): . Cloud provider or hardware configuration**: . OS (e.g. from /etc/os-release): . Kernel (e.g. ): . Install tools: . Others: .\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig service-catalog\ndoes the alpha CI job enable alpha API versions?\nfile has \"AllAlpha=true\" Maybe would be better?", "commid": "kubernetes_issue_53079", "tokennum": 293}], "negative_passages": []}
{"query_id": "q-en-kubernetes-43af45089f138c9db67a2362f9bd3a4e0653566412cffa1d4494bec5d87a6f7b", "query": "t.Fatalf(\"AddPod failed. Expected: <no error> Actual: <%v>\", podAddErr) } <del> time.Sleep(1000 * time.Millisecond) </del> // Volume is added to asw, volume should be reported as attached to the node. waitForVolumeAddedToNode(t, generatedVolumeName, nodeName1, asw) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <del> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw) </del> <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw, volumeAttachedCheckTimeout) </ins> // Delete the pod, but detach will fail dsw.DeletePod(types.UniquePodName(podName1), generatedVolumeName, nodeName1)", "positive_passages": [{"docid": "doc-en-kubernetes-dc8aac09a0e4bb26f9dc5f50aef7f845ea9d7c4b925d34b9f6eda044925f80f5", "text": "TestRunOneVolumeDetachFailNodeWithReadWriteOnce 4 times since 03-19 23:00 PDT, intermittently ! https://k8s- Still investigating whether this is a tolerable flake or not with more history than testgrid view, or otherwise would appreciate input from anyone with expertise in this test, especially as regards to whether this should be a blocker for tomorrows beta cut. maybe: /sig storage /sig testing\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nis already open for this, looks like it is attempting to fix it\nthank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. /close\nClosing this issue. <detailsIn response to : thank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. 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", "commid": "kubernetes_issue_116774", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-43af45089f138c9db67a2362f9bd3a4e0653566412cffa1d4494bec5d87a6f7b", "query": "t.Fatalf(\"AddPod failed. Expected: <no error> Actual: <%v>\", podAddErr) } <del> time.Sleep(1000 * time.Millisecond) </del> // Volume is added to asw, volume should be reported as attached to the node. waitForVolumeAddedToNode(t, generatedVolumeName, nodeName1, asw) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <del> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw) </del> <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw, volumeAttachedCheckTimeout) </ins> // Delete the pod, but detach will fail dsw.DeletePod(types.UniquePodName(podName1), generatedVolumeName, nodeName1)", "positive_passages": [{"docid": "doc-en-kubernetes-aef7ec00dc93616f97177ca3d23f28217445848b34c429e5746962ea28329f43", "text": "pull-kubernetes-unit TestRunOneVolumeDetachFailNodeWithReadWriteOnce Jan 7th, 2022 Check volume <fake-plugin/volume-nameis reported as attached to node <fail-detach-node, got false, expected true No response_ /sig storage\n/cc\nthis is the top unit test flake according to\ncc\nThe 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]:\nI think this test is no longer flaky by checking the test grid, close it now.\nUnfortunately this does still seem to be flaky: Here was the output from : /reopen\nReopened this issue. <detailsIn response to : Unfortunately this does still seem to be flaky: 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\n/remove-lifecycle stale\nstill the case\nHow about adding some logging to help troubleshoot this? I looked at it a little, but it is hard to tell which part of the test is failing. PR\n/\nThis is still happening\n/triage accepted\nFrom the logs, in the OneVolumeDetachFailNodeWithReadWriteOnce test, succeeded, but the next verification failed. In verifyVolumeAttachedToNode, the attachState is from calling and within asw, it calls . In verifyVolumeReportedAsAttachedToNode, the volumes are obtained from calling , it seems that the node is not in asw.nodesToUpdateStatusFor at this step. Cannot reproduce locally. I tried to run the test 100 times locally with debug.Stack()... 3 * 100 times all passed.\nTried to run stress test on my linux machine as well but still cannot reproduce. Command: Result: Also tried running n process in parallel. Command: Result:\nIt seems like it happens more frequently.", "commid": "kubernetes_issue_107414", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-43af45089f138c9db67a2362f9bd3a4e0653566412cffa1d4494bec5d87a6f7b", "query": "t.Fatalf(\"AddPod failed. Expected: <no error> Actual: <%v>\", podAddErr) } <del> time.Sleep(1000 * time.Millisecond) </del> // Volume is added to asw, volume should be reported as attached to the node. waitForVolumeAddedToNode(t, generatedVolumeName, nodeName1, asw) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <del> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw) </del> <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw, volumeAttachedCheckTimeout) </ins> // Delete the pod, but detach will fail dsw.DeletePod(types.UniquePodName(podName1), generatedVolumeName, nodeName1)", "positive_passages": [{"docid": "doc-en-kubernetes-62e47fd83b7fc1cc39259be1688a9f133b9cd2dc48247eb5d858fae7fd13955b", "text": "But I may have no time to dig into the cause. Let's see.\ncc as the test author.\nThe problem is that this test has a lot of dependency on the sleeps that are hardcoded with a very narrow scope, but our CI seems to be able to stress it much more. As soon as you slightly change one of the sleep duration it starts to flake locally The test can not make an assumption that timing is perfect, even more in the sub second range can someone in sig-storage review this test and make it less dependant on those tight sleeps?\nAccording to most failures, it failed at Line 660. Let me run some stress locally. with 250ms sleep with 100ms sleep\nI agree this test case is too brittle due to its specific timing dependencies. To fix this, I suggest reworking the test case to: 1) Add retry with timeout to wait for final conditions 2) Remove the intermediate timing-based state transition checks. Instead, we can keep track of state transitions in the Fakes and validate those stats. wdyt?\nFriendly ping from 1.27 CI Signal that this test is still a noisy flake on the master-blocking dashboard as CI Signal has flagged it in and", "commid": "kubernetes_issue_107414", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-43c17ca74868e539b32412b651870fff9923317e54743d6ffa6c76a4a78d905b", "query": "exit 2 fi <del> /opt/bin/etcdctl mk /coreos.com/network/config \"{\"Network\":\"${FLANNEL_NET}\", \"Backend\": {\"Type\": \"vxlan\"}}\" </del> <ins> /opt/bin/etcdctl mk /coreos.com/network/config \"{\"Network\":\"${FLANNEL_NET}\", \"Backend\": {\"Type\": \"vxlan\"}${FLANNEL_OTHER_NET_CONFIG}}\" </ins> attempt=$((attempt+1)) sleep 3 fi", "positive_passages": [{"docid": "doc-en-kubernetes-3bb3543c0323a70faea91ccc43a3eaf950d3e30c811cd93e021b94a126351841", "text": "and provide for configuring Flannel's parameter but none of the others listed in", "commid": "kubernetes_issue_19618", "tokennum": 20}], "negative_passages": []}
{"query_id": "q-en-kubernetes-443fab67406de499a6f3c4177a74faa92e30fb5df2dbf2c7b8cd01b97434db26", "query": "rm -rf \"${LOCAL_OUTPUT_BINPATH}\" mkdir -p \"${LOCAL_OUTPUT_BINPATH}\" <del> # Remove the container if it is left over from some previous aborted run \"${DOCKER[@]}\" rm -f -v \"${KUBE_BUILD_CONTAINER_NAME}\" >/dev/null 2>&1 || true </del> <ins> kube::build::destroy_container \"${KUBE_BUILD_CONTAINER_NAME}\" </ins> \"${docker_cmd[@]}\" bash -c \"cp -r ${REMOTE_OUTPUT_BINPATH} /tmp/bin;touch /tmp/finished;rm /tmp/bin/test_for_remote;/bin/sleep 600\" > /dev/null 2>&1 # Wait until binaries have finished coppying", "positive_passages": [{"docid": "doc-en-kubernetes-349c839c0314e1386e949c881af8735bbe6497abcf3a15697139e75deb1d1835", "text": "Github automatically adds a artifact to every release, which sounds very similar to the artifact that we generate as the release artifact. Assuming we don't have control over the naming or presence of the autogenerated source code artifact, I think we should consider renaming our published artifact to better disambiguate between the two.\nWe distribute most of our artifacts outside of GitHub. We should probably stop uploading this one entirely.\ncc\nWe've got a thread going on w/ Tim. /assign\ncan you please link so folks can follow the bread crumbs? ( cc )\n-- It's currently sensitive. Will share once there's an outcome.\nACK. thanks for the heads up\nI think it's safe to discuss openly at this point. We had a report that the sha512 hashes on our release artifacts were incorrect. We have confirmed that the mismatch was due to a bug in the release pipeline, and not malicious. This issue here was just a point of confusion that came out of that discussion.\nthanks !\n/assign\nGoing one step back since I think the exists for historical reasons: The client and server binaries were part of this bundle, which is not the case any more: So it seems that is mostly a collection of licenses and scripts. Do we really need it or may we cleanup some code paths and remove it completely?\n+1 to put the word out and remove it completely if no one depends on it.\nI'm not confident that CI is not using these versioned scripts, in fact i'm fairly sure that it is. However it would not be pulling it from github.\nThe 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]:\n/remove-lifecycle stale I think this remains as relevant as ever.\n/milestone v1.23\n/triage accepted\nHi and k8s 1.23 bug triage shadow here.", "commid": "kubernetes_issue_100460", "tokennum": 507}], "negative_passages": []}
{"query_id": "q-en-kubernetes-443fab67406de499a6f3c4177a74faa92e30fb5df2dbf2c7b8cd01b97434db26", "query": "rm -rf \"${LOCAL_OUTPUT_BINPATH}\" mkdir -p \"${LOCAL_OUTPUT_BINPATH}\" <del> # Remove the container if it is left over from some previous aborted run \"${DOCKER[@]}\" rm -f -v \"${KUBE_BUILD_CONTAINER_NAME}\" >/dev/null 2>&1 || true </del> <ins> kube::build::destroy_container \"${KUBE_BUILD_CONTAINER_NAME}\" </ins> \"${docker_cmd[@]}\" bash -c \"cp -r ${REMOTE_OUTPUT_BINPATH} /tmp/bin;touch /tmp/finished;rm /tmp/bin/test_for_remote;/bin/sleep 600\" > /dev/null 2>&1 # Wait until binaries have finished coppying", "positive_passages": [{"docid": "doc-en-kubernetes-dbd15f43daca5c062443bfb889f914327019b692ac2d45e387a4f7451b197946", "text": "There hasn't been any activity or linked PRs for this issue. Just wanted to check in to see if this is still on track for 1.23.\n/milestone v1.24\nHi I am part of the bug triage team for v1.24. We noticed that this issue hasn't been updated for a while. Just wanted to check if there is any work planned that would go into this.\nthis one keeps moving down the milestones. i don't see any activity since november. So kick the can down the road /milestone v1.25\nHi My name Hossein Salahi from Bug-Triage team. I am just checking to ensure if everything is on track for K8s 1.25. Thanks!\nThat's a question for or\nany remarks on that?\nthe release 1.25 bug triage Lead. I'm reaching out to see the status of this issue and if we are still targeting the current release. Also, kindly if you can update the priority so we can track it in the future.\nthis one keeps moving down the milestones yet again!. i don't see any activity since i moved this down the line. So kick the can down the road: /milestone clear (instead of v1.26 as this has been moving down the line for a few releases now)\nThe 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]:\n/remove-lifecycle stale\nWhat's the current status of this issue? Is there anything that we can do to move this forward?\nWe got new conversations going on during Kubecon on whether we should publish our release binaries on GitHub. Given that and I think we should rethink now what we publish on the release pages. I think we should start publishing all binaries for one. It is a common practice everywhere and I think users largely expect them to be there.", "commid": "kubernetes_issue_100460", "tokennum": 505}], "negative_passages": []}
{"query_id": "q-en-kubernetes-443fab67406de499a6f3c4177a74faa92e30fb5df2dbf2c7b8cd01b97434db26", "query": "rm -rf \"${LOCAL_OUTPUT_BINPATH}\" mkdir -p \"${LOCAL_OUTPUT_BINPATH}\" <del> # Remove the container if it is left over from some previous aborted run \"${DOCKER[@]}\" rm -f -v \"${KUBE_BUILD_CONTAINER_NAME}\" >/dev/null 2>&1 || true </del> <ins> kube::build::destroy_container \"${KUBE_BUILD_CONTAINER_NAME}\" </ins> \"${docker_cmd[@]}\" bash -c \"cp -r ${REMOTE_OUTPUT_BINPATH} /tmp/bin;touch /tmp/finished;rm /tmp/bin/test_for_remote;/bin/sleep 600\" > /dev/null 2>&1 # Wait until binaries have finished coppying", "positive_passages": [{"docid": "doc-en-kubernetes-63377ea8eda65aaaac09acc9ed7dd8461429e8729a6daebbb93d9c0997493c68", "text": "let's scope the issue to the actual \"Kubernetes Source Code\" tarball. We can still remove it from what I can see from the discussion.\nI agree with Removing the \"Kubernetes Source Code\" tarball should be as easy as removing this from krel: However, there are a few questions: is it safe to do so? I believe yes, because this \"Kubernetes Source Code\" tarball is pointing to the GCS bucket, and we'll still continue publishing that tarball to the bucket The link is also available in the changelog, so it's easy to find do we need any deprecation period? Considering the above two points, I don't think so. If you folks agree with that, I can go ahead and create a PR to update krel.\nI agree on that, let's drop an additional note on k-dev that others are aware of the change.\n/assign\nUpdate: An announcement to proceed with the removal of the \"Kubernetes Source Code\" artifact has been sent to k-dev: PR to remove this artifact from being published: Removal will go into effect starting the January patch releases.", "commid": "kubernetes_issue_100460", "tokennum": 245}], "negative_passages": []}
{"query_id": "q-en-kubernetes-44501edfe14669dd5a3ff9d73f09f0e9dc7324dd60e64c728fb909f254b55707", "query": "w.initialValue = results.Unknown } <del> podName := getPodLabelName(w.pod) </del> basicMetricLabels := metrics.Labels{ \"probe_type\": w.probeType.String(), \"container\":  w.container.Name, <del> \"pod\":        podName, </del> <ins> \"pod\":        w.pod.Name, </ins> \"namespace\":  w.pod.Namespace, \"pod_uid\":    string(w.pod.UID), }", "positive_passages": [{"docid": "doc-en-kubernetes-8720ed8a574bdce7c104bd3a62cc93935fad36eef53bf2f2ff98186bbe4abc40", "text": "The metric used to report acutal pod in the label , but now I see the podname prefix only. The full pod name in the label, so I can trace the metric to the failing pod. Check raw api and verify the actual pod name with uids. <details</detailsAzure AKS <details</detailsNo response No response No response_\n/sig node\n/triage accepted /priority important-soon /cc As discussed this is a change in functionaloty that wasn't highlighted in release notes. Need to decide on what do do with it. I understand it's a change of functionality. what is the side effect of this for you? Does the label without last part not informational enough?\nI've been using the metric in my custom grafana dashboard that shows CPU, RAM, IO usage of pods with graph of increases in probes. If the apps are stable, the probe graph looks steadily. I can see if some irregularities in system metrics are influencing probes of respective pod. Also, if readiness probe is failing, the pod is removed from service, but is not restarted so I must have knowledge of pods with failing readiness probes. I attach the screenshot of my graph. ! So I'd welcome the possibility to pair the probes with exact pod and thank you for looking into it.\nare we thinking that this resulted in an undesirable change? Spologies for being a bit late to reply, I'm returning from a brief paternity leave staycation.\nThis issue is labeled with but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release. You can: Confirm that this issue is still relevant with (org members only) Deprioritize it with or Close this issue with For more details on the triage process, see /remove-triage accepted\nWell this is awkward... I still believe the actual behavior does not respect the intended idea...\nThis issue makes it hard to link probe metrics with right pods. The value of pod label in and are also inconsistent with how it is used in other kubelet metrics, see: vs Definitely a bug, regression since 1.25.\nI can't get anyone to look at the fix/revert: you may have better luck\n/milestone v1.28\ndiscussion in\nYou've pushed it through, congrats!", "commid": "kubernetes_issue_115766", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-445e51478527d5b68801334d99e9c8d568c7597734c740313eaaca5af311038c", "query": "<ins> /* Copyright 2016 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package util import ( \"fmt\" \"reflect\" \"sync\" \"time\" federation_api \"k8s.io/kubernetes/federation/apis/federation/v1beta1\" federation_release_1_4 \"k8s.io/kubernetes/federation/client/clientset_generated/federation_release_1_4\" api \"k8s.io/kubernetes/pkg/api\" api_v1 \"k8s.io/kubernetes/pkg/api/v1\" \"k8s.io/kubernetes/pkg/client/cache\" \"k8s.io/kubernetes/pkg/client/restclient\" \"k8s.io/kubernetes/pkg/controller/framework\" pkg_runtime \"k8s.io/kubernetes/pkg/runtime\" \"k8s.io/kubernetes/pkg/watch\" \"github.com/golang/glog\" ) const ( clusterSyncPeriod = 10 * time.Minute userAgentName     = \"federation-service-controller\" ) // FederatedReadOnlyStore is an overlay over multiple stores created in federated clusters. type FederatedReadOnlyStore interface { // Returns all items in the store. List() ([]interface{}, error) // GetByKey returns the item stored under the given key in the specified cluster (if exist). GetByKey(clusterName string, key string) (interface{}, bool, error) // Returns the items stored under the given key in all clusters. GetFromAllClusters(key string) ([]interface{}, error) // Checks whether stores for all clusters form the lists (and only these) are there and // are synced. This is only a basic check whether the data inside of the store is usable. // It is not a full synchronization/locking mechanism it only tries to ensure that out-of-sync // issues occur less often.\tAll users of the interface should assume // that there may be significant delays in content updates of all kinds and write their // code that it doesn't break if something is slightly out-of-sync. ClustersSynced(clusters []*federation_api.Cluster) bool } // An interface to access federation members and clients. type FederationView interface { // GetClientsetForCluster returns a clientset for the cluster, if present. GetClientsetForCluster(clusterName string) (federation_release_1_4.Interface, error) // GetReadyClusers returns all clusters for which the sub-informers are run. GetReadyClusters() ([]*federation_api.Cluster, error) // GetReadyCluster returns the cluster with the given name, if found. GetReadyCluster(name string) (*federation_api.Cluster, bool, error) // ClustersSynced returns true if the view is synced (for the first time). ClustersSynced() bool } // A structure that combines an informer running agains federated api server and listening for cluster updates // with multiple Kubernetes API informers (called target informers) running against federation members. Whenever a new // cluster is added to the federation an informer is created for it using TargetInformerFactory. Infomrers are stoped // when a cluster is either put offline of deleted. It is assumed that some controller keeps an eye on the cluster list // and thus the clusters in ETCD are up to date. type FederatedInformer interface { FederationView // Returns a store created over all stores from target informers. GetTargetStore() FederatedReadOnlyStore // Starts all the processes. Start() // Stops all the processes inside the informer. Stop() } // A function that should be used to create an informer on the target object. Store should use // framework.DeletionHandlingMetaNamespaceKeyFunc as a keying function. type TargetInformerFactory func(*federation_api.Cluster, federation_release_1_4.Interface) (cache.Store, framework.ControllerInterface) // Builds a FederatedInformer for the given federation client and factory. func NewFederatedInformer(federationClient federation_release_1_4.Interface, targetInformerFactory TargetInformerFactory) FederatedInformer { federatedInformer := &federatedInformerImpl{ targetInformerFactory: targetInformerFactory, clientFactory: func(cluster *federation_api.Cluster) (federation_release_1_4.Interface, error) { clusterConfig, err := BuildClusterConfig(cluster) if err != nil && clusterConfig != nil { clientset := federation_release_1_4.NewForConfigOrDie(restclient.AddUserAgent(clusterConfig, userAgentName)) return clientset, nil } return nil, err }, targetInformers: make(map[string]informer), } federatedInformer.clusterInformer.store, federatedInformer.clusterInformer.controller = framework.NewInformer( &cache.ListWatch{ ListFunc: func(options api.ListOptions) (pkg_runtime.Object, error) { return federationClient.Federation().Clusters().List(options) }, WatchFunc: func(options api.ListOptions) (watch.Interface, error) { return federationClient.Federation().Clusters().Watch(options) }, }, &federation_api.Cluster{}, clusterSyncPeriod, framework.ResourceEventHandlerFuncs{ DeleteFunc: func(old interface{}) { oldCluster, ok := old.(*federation_api.Cluster) if ok { federatedInformer.deleteCluster(oldCluster) } }, AddFunc: func(cur interface{}) { curCluster, ok := cur.(*federation_api.Cluster) if ok && isClusterReady(curCluster) { federatedInformer.addCluster(curCluster) } }, UpdateFunc: func(old, cur interface{}) { oldCluster, ok := old.(*federation_api.Cluster) if !ok { return } curCluster, ok := cur.(*federation_api.Cluster) if !ok { return } if isClusterReady(oldCluster) != isClusterReady(curCluster) || !reflect.DeepEqual(oldCluster.Spec, curCluster.Spec) { federatedInformer.deleteCluster(oldCluster) if isClusterReady(curCluster) { federatedInformer.addCluster(curCluster) } } }, }, ) return federatedInformer } func isClusterReady(cluster *federation_api.Cluster) bool { for _, condition := range cluster.Status.Conditions { if condition.Type == federation_api.ClusterReady { if condition.Status == api_v1.ConditionTrue { return true } } } return false } type informer struct { controller framework.ControllerInterface store      cache.Store stopChan   chan struct{} } type federatedInformerImpl struct { sync.Mutex // Informer on federated clusters. clusterInformer informer // Target informers factory targetInformerFactory TargetInformerFactory // Structures returned by targetInformerFactory targetInformers map[string]informer // A function to build clients. clientFactory func(*federation_api.Cluster) (federation_release_1_4.Interface, error) } type federatedStoreImpl struct { federatedInformer *federatedInformerImpl } func (f *federatedInformerImpl) Stop() { f.Lock() defer f.Unlock() close(f.clusterInformer.stopChan) for _, informer := range f.targetInformers { close(informer.stopChan) } } func (f *federatedInformerImpl) Start() { f.Lock() defer f.Unlock() f.clusterInformer.stopChan = make(chan struct{}) go f.clusterInformer.controller.Run(f.clusterInformer.stopChan) } // GetClientsetForCluster returns a clientset for the cluster, if present. func (f *federatedInformerImpl) GetClientsetForCluster(clusterName string) (federation_release_1_4.Interface, error) { f.Lock() defer f.Unlock() return f.getClientsetForClusterUnlocked(clusterName) } func (f *federatedInformerImpl) getClientsetForClusterUnlocked(clusterName string) (federation_release_1_4.Interface, error) { // No locking needed. Will happen in f.GetCluster. if cluster, found, err := f.getReadyClusterUnlocked(clusterName); found && err == nil { return f.clientFactory(cluster) } else { if err != nil { return nil, err } } return nil, fmt.Errorf(\"cluster %s not found\", clusterName) } // GetReadyClusers returns all clusters for which the sub-informers are run. func (f *federatedInformerImpl) GetReadyClusters() ([]*federation_api.Cluster, error) { f.Lock() defer f.Unlock() items := f.clusterInformer.store.List() result := make([]*federation_api.Cluster, 0, len(items)) for _, item := range items { if cluster, ok := item.(*federation_api.Cluster); ok { if isClusterReady(cluster) { result = append(result, cluster) } } else { return nil, fmt.Errorf(\"wrong data in FederatedInformerImpl cluster store: %v\", item) } } return result, nil } // GetCluster returns the cluster with the given name, if found. func (f *federatedInformerImpl) GetReadyCluster(name string) (*federation_api.Cluster, bool, error) { f.Lock() defer f.Unlock() return f.getReadyClusterUnlocked(name) } func (f *federatedInformerImpl) getReadyClusterUnlocked(name string) (*federation_api.Cluster, bool, error) { if obj, exist, err := f.clusterInformer.store.GetByKey(name); exist && err == nil { if cluster, ok := obj.(*federation_api.Cluster); ok { if isClusterReady(cluster) { return cluster, true, nil } return nil, false, nil } return nil, false, fmt.Errorf(\"wrong data in FederatedInformerImpl cluster store: %v\", obj) } else { return nil, false, err } } // Synced returns true if the view is synced (for the first time) func (f *federatedInformerImpl) ClustersSynced() bool { f.Lock() defer f.Unlock() return f.clusterInformer.controller.HasSynced() } // Adds the given cluster to federated informer. func (f *federatedInformerImpl) addCluster(cluster *federation_api.Cluster) { f.Lock() defer f.Unlock() name := cluster.Name if client, err := f.getClientsetForClusterUnlocked(name); err == nil { store, controller := f.targetInformerFactory(cluster, client) targetInformer := informer{ controller: controller, store:      store, stopChan:   make(chan struct{}), } f.targetInformers[name] = targetInformer go targetInformer.controller.Run(targetInformer.stopChan) } else { // TODO: create also an event for cluster. glog.Errorf(\"Failed to create a client for cluster: %v\", err) } } // Removes the cluster from federated informer. func (f *federatedInformerImpl) deleteCluster(cluster *federation_api.Cluster) { f.Lock() defer f.Unlock() name := cluster.Name if targetInformer, found := f.targetInformers[name]; found { close(targetInformer.stopChan) } delete(f.targetInformers, name) } // Returns a store created over all stores from target informers. func (f *federatedInformerImpl) GetTargetStore() FederatedReadOnlyStore { return &federatedStoreImpl{ federatedInformer: f, } } // Returns all items in the store. func (fs *federatedStoreImpl) List() ([]interface{}, error) { fs.federatedInformer.Lock() defer fs.federatedInformer.Unlock() result := make([]interface{}, 0) for _, targetInformer := range fs.federatedInformer.targetInformers { values := targetInformer.store.List() result = append(result, values...) } return result, nil } // GetByKey returns the item stored under the given key in the specified cluster (if exist). func (fs *federatedStoreImpl) GetByKey(clusterName string, key string) (interface{}, bool, error) { fs.federatedInformer.Lock() defer fs.federatedInformer.Unlock() if targetInformer, found := fs.federatedInformer.targetInformers[clusterName]; found { return targetInformer.store.GetByKey(key) } return nil, false, nil } // Returns the items stored under the given key in all clusters. func (fs *federatedStoreImpl) GetFromAllClusters(key string) ([]interface{}, error) { fs.federatedInformer.Lock() defer fs.federatedInformer.Unlock() result := make([]interface{}, 0) for _, targetInformer := range fs.federatedInformer.targetInformers { value, exist, err := targetInformer.store.GetByKey(key) if err != nil { return nil, err } if exist { result = append(result, value) } } return result, nil } // GetKey for returns the key under which the item would be put in the store. func (fs *federatedStoreImpl) GetKeyFor(item interface{}) string { // TODO: support other keying functions. key, _ := framework.DeletionHandlingMetaNamespaceKeyFunc(item) return key } // Checks whether stores for all clusters form the lists (and only these) are there and // are synced. func (fs *federatedStoreImpl) ClustersSynced(clusters []*federation_api.Cluster) bool { fs.federatedInformer.Lock() defer fs.federatedInformer.Unlock() if len(fs.federatedInformer.targetInformers) != len(clusters) { return false } for _, cluster := range clusters { if targetInformer, found := fs.federatedInformer.targetInformers[cluster.Name]; found { if !targetInformer.controller.HasSynced() { return false } } else { return false } } return true } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-4f983686ce6cef6162dd147e0e53be05aced0afa9196140d2e8041aafeaab5cd", "text": "As discussed, similar patterns occur in many of the controller for federated objects. Lift this into a common library that can be used by all of the controllers. Open separate issues for each of the above, and track there. This can be the tracking issue over those.\nHi, , we have been starting develop work about cluster-controller and RS controller, so would you like to share me the plan about this work? Thanks.\nTracked in PR's referenced above. Closing this tracking issue.", "commid": "kubernetes_issue_29347", "tokennum": 99}], "negative_passages": []}
{"query_id": "q-en-kubernetes-446c0fe158a7ca6d4ebe84bb45be7b738d139e3cf5ad857da2ed3f68f90812c3", "query": "sched.Recorder.Eventf(victim, preemptor, v1.EventTypeNormal, \"Preempted\", \"Preempting\", \"Preempted by %v/%v on node %v\", preemptor.Namespace, preemptor.Name, nodeName) } <del> metrics.PreemptionVictims.Set(float64(len(victims))) </del> <ins> metrics.PreemptionVictims.Observe(float64(len(victims))) </ins> } // Clearing nominated pods should happen outside of \"if node != nil\". Node could // be nil when a pod with nominated node name is eligible to preempt again,", "positive_passages": [{"docid": "doc-en-kubernetes-747d699b97976a530bdb275e803e2be1bb68ac7168a6ff8b59806b000dbdf33f", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Change scheduler metric from Gauge to Histogram Why is this needed: is recorded for each preemption attempt. A histogram is better. /sig scheduling /help /good-first-issue\n/help /good-first-issue\nThis request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /help /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\nI can work on this issue.\n/assign\nI could work on this as well if doesn't have time to work on this.\nI am working on it, I will create the initial PR in less than a week. Sorry for the delay.", "commid": "kubernetes_issue_83464", "tokennum": 211}], "negative_passages": []}
{"query_id": "q-en-kubernetes-44879f612cdaf178b47b8d050f3bbf4b82d09541306148f9e2f988025ac4946b", "query": "var ( // Master nodes are not added to standard load balancer by default. defaultExcludeMasterFromStandardLB = true <ins> // Outbound SNAT is enabled by default. defaultDisableOutboundSNAT = false </ins> ) // Config holds the configuration parsed from the --cloud-config flag", "positive_passages": [{"docid": "doc-en-kubernetes-f91ac3317a925ac3a02c50dc39021d458d6020da9f69361ec2732a68459b1b7c", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: is the recommended way to configure the outbound networks together with Azure standard loadbalancer (SLB). However, for load balancer rules are disabled by default. That means all frontend IPs would be used as the SNAT IPs for virtual machines, according to . This would introduce troubles for various security scenarios, as there's no way to get a stable list of egress IPs. Azure cloud provider should support this scenario, and disable the outbound SNAT when outbound rules are configured by provisioning tools. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Others: /kind bug /sig azure /priority critical-urgent", "commid": "kubernetes_issue_75281", "tokennum": 247}], "negative_passages": []}
{"query_id": "q-en-kubernetes-44c8aec4c0b8c7f4c9ff5ed7d539a9636d76eb5dac1fae22515374cbebca981e", "query": "a.cachedCreds = newCreds // Only close all connections when TLS cert rotates. Token rotation doesn't // need the extra noise. <del> if a.onRotate != nil && oldCreds != nil && !reflect.DeepEqual(oldCreds.cert, a.cachedCreds.cert) { a.onRotate() </del> <ins> if len(a.onRotateList) > 0 && oldCreds != nil && !reflect.DeepEqual(oldCreds.cert, a.cachedCreds.cert) { for _, onRotate := range a.onRotateList { onRotate() } </ins> } return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-d5f405b98ac26e68bb52a403345cda18a0b690bbcb8385b5ec06372b302c6e2d", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Data race in client-go with below sample code: Data race: What you expected to happen: No data race How to reproduce it (as minimally and precisely as possible): Using above given sample code Kubernetes version (use ):Cloud provider or hardware configuration:OS (e.g: ): OSX\n/sig api-machinery\nI'd like to take it. /assign\n/remove-sig api-machinery /sig auth cli\nBug triage for release 1.17 here. Since this issue has been tagged for the milestone, we would like to check it's status. Code freeze is on Nov. 14. Will this issue be resolved before then?\nAnother reminder here that code freeze is in less than two weeks (Nov. 14). We will need to move this issue out of the milestone if isn't going to be resolved before then.", "commid": "kubernetes_issue_80269", "tokennum": 239}], "negative_passages": []}
{"query_id": "q-en-kubernetes-44de75c645c5d57298b260dba70f1f718a2560af341f79fe2123148d2aa2826b", "query": "releaseHugepages() ginkgo.By(\"restarting kubelet to pick up pre-allocated hugepages\") <del> restartKubelet() </del> <ins> // stop the kubelet and wait until the server will restart it automatically stopKubelet() </ins> waitForHugepages() })", "positive_passages": [{"docid": "doc-en-kubernetes-88c095cfe151193749adeb925825c9856381f9f8544c8822d93b8eb731e64566", "text": "ci-kubernetes-node-kubelet-serial-hugepages when start the pod with the resources requests that contain multiple hugepages resources should set correct hugetlb mount and limit under the container cgroup Unexpected error: \"pod ran to completion\", Multiple sizes huge pages is going to be graduated to GA, so having this test job fixed is quite important.\n/sig node\n/assign\n/triage accepted\n/cc\nI did a small analysis and I can see that the pod failed to start, I can not find any failure messages under the kubelet log, so it really hard to say why it failed.\nwere you able to reproduce it locally? btw, there is a \"right way\" to fix this - to fix dynamic update of a hugepage resources. This would eliminate need in a kubelet restart. There is even a PR for that: , we just need to make it working again.\nafter conversation with on slack I'd say we should stick to the current procedure - restarting kubelet when hugepages allocation changes. So, we should investigate why kubelet doesn't restart properly in this test case and fix it.\nNope, I failed to reproduce it locally, also under the CI, it does not appear often. The best thing will be to describe the pod in case if it failed, so we will see the reason.\nunder the code we have so from the log , I can see that the kubelet received the pod before the kubelet stopped, so the problem that pod dropped to Failed state because of the kubelet stop.\nSo some additional details, the one who responsible to restart the kubelet again, is the server service: restart the kubelet service are waiting for hugepages to be available are starting the pod server service restart the kubelet again because it was not healthy for too long - failed to start because of the kubelet restart\ngreat findings! Should we just stop the kubelet and let the server service to start it again? We can also check if the kubelet is restarted successfully before starting the pod.\nI tried it under the PR , also I unsure how can we check if the kubelet restarted successfully. All tests that I wrote before I checked if the node has NotReady state and waited until it will be Ready, but in case of the restart probably the node will always have Ready state because the time period is very short. I will continue to investigate and will check locally how can I fix it.", "commid": "kubernetes_issue_99402", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-44de75c645c5d57298b260dba70f1f718a2560af341f79fe2123148d2aa2826b", "query": "releaseHugepages() ginkgo.By(\"restarting kubelet to pick up pre-allocated hugepages\") <del> restartKubelet() </del> <ins> // stop the kubelet and wait until the server will restart it automatically stopKubelet() </ins> waitForHugepages() })", "positive_passages": [{"docid": "doc-en-kubernetes-df5fd4d114576094d5b1a71b893d21a3e13b2c561e9313633a9dfbe243849634", "text": "So the only reliable solution that I found, it just trying to start the pod number of times. I tested it 5 times and the test passed. Can you please review\nCan we access kubelet service from hugepage test cases? If we can we can use its APIs like or to check if kubelet is ready after the restart. Overall I have a feeling of duplication test/e2enode/services functionality in This is a main reason for this and similar bugs I believe. It would be nice to get rid of this duplication if possible. That would nicely isolate kubelet service controls in one place and eliminate conflicts like this one. wdyt?\nnot really, the used mostly to start all needed components to emulate the cluster(not only the kubelet) and the test does not have access to it. I think you can separate the readiness check under the importable method, but it worth the separate PR.\nI updated the PR to check the healthiness of the kubelet and looks like it works just fine.\nthank you. it looks good to me so far. I'll add lgtm label when is merged and tests are all green.\nthe job is still flaky. can you reopen this issue?\nI opened a different one - , the issue can affect any job, not only the hugepages one.\nI can open a fix to W/A an issue(start the pod until it will succeed), it should fix all problems, WDYT?\ni think it's ok as a workaround, until is fixed\nwould it be better to wait until api server reports correct resource value before running the pod?\nWe are waiting for it, the problem that the scheduler and the kubelet see a different picture regarding resources requested by pods.\nok. In this case restarting the pod until it succeeds seems reasonable to me to fix the flakiness until is fixed.\nany progress on the workaround fix?", "commid": "kubernetes_issue_99402", "tokennum": 404}], "negative_passages": []}
{"query_id": "q-en-kubernetes-451d67bcc3324e916a66e933c8d69271c7db65dfa489895c99f7a0154d400d1f", "query": "containers: - name: fluentd-cloud-logging image: gcr.io/google_containers/fluentd-gcp:1.6 <ins> resources: limits: cpu: 100m </ins> env: - name: \"FLUENTD_ARGS\" value: \"-qq\"", "positive_passages": [{"docid": "doc-en-kubernetes-76a1437b2e9419a405205d59af74d9b368790a08551fbd85b287efde2a056dcd", "text": "During debugging , I noticed that one of services pods: monitoring and logging pods stuck at pending sometimes forever: I logged into the node, and found the container is running happily on the node: Looks like status is never reported from kubelet. I checked kubelet log, then I found: Why we cannot delete mirror pod? and Created a new one? Because this regression, once we run into such state, the rest of test won't be triggered, and eventually timeout / failed.\nchecks those service pods in ready state, and prevent the test to run once it is pending. cc/ I think this is the real issue I talked to you earlier about PodStatus.\nI spoke to offline. For some reason, kubelet thinks the spec of the mirror pod does not match the static pod locally. It then decides to delete the mirror pod and recreate it, repeatedly. As a result of that, it slows down (due to the QPS limit?) reporting statuses of other pods. This can be reproduced by running the e2e \"Shell\" test. I am looking into why the specs would suddenly mismatch. Did any recent PR modified the pod spec in apiserver?\nThe recently introduced default cpu share limit was not there in the static pod, causing the difference between its spec and the mirror pod's.\nSeeing this as well. Makes the whole cluster slow and unusable for me. Sent from my iPhone\nIs there a desired fix for this?\nsaid she would add default resource limits to the static pod manifest files. If we go for that, I think it's reasonable to fail (not run the static pod) if resource limit is not specified. Also, the resource limits set in the mirror pods are not meaningful because kubelet creates containers based on the spec of the static pod. In general, static pods do not subject to any defaulting values applied at the apiserver.\nPretty sure that this is fixed by . Certainly testing against head since then works well for me. What version are you testing?\nwas fixing node status, and the problem had been around for a while. This issue is about pod status, which is still unfixed on head. These two are very different, and my cluster did include the fix :) This issue will slow down kubelet at times, but if you get lucky and the pod status (running) get sent out in time, the tests will still pass.", "commid": "kubernetes_issue_8642", "tokennum": 506}], "negative_passages": []}
{"query_id": "q-en-kubernetes-451d67bcc3324e916a66e933c8d69271c7db65dfa489895c99f7a0154d400d1f", "query": "containers: - name: fluentd-cloud-logging image: gcr.io/google_containers/fluentd-gcp:1.6 <ins> resources: limits: cpu: 100m </ins> env: - name: \"FLUENTD_ARGS\" value: \"-qq\"", "positive_passages": [{"docid": "doc-en-kubernetes-dbb34576173a9a8fefb5aa440567e5b808bc06b80f759ff3da54bf129fc77991", "text": "There is no way the issue is fixed by that PR. I am still seeing the issue on HEAD. The system gets worse the longer its up. I agree with the analysis of the issue in source PR Sent from my iPhone\nI am on this one, and here is proposed solution in my mind so far (not final yet since I haven't put too much thoughts into it yet): 1) For all our static pods I am going to update them with some initial cpu limit for now. This should quickly stop flakiness caused by this particular issue. 2) Next step is that for static pods, if there is no initial cpu limit, kubelet should refuse to run. Before I do this, I need to send an announcement to our container-vm users about this potential breakage for the in the future. Another potential fix is we can ignore resource changes when comparing if a mirror pod is updated or not. I think is proposed a similiar one earlier. But I had a concern with it: this is defeat the initial purpose we created mirror pods and sync back to master. So if one made some resource changes on the static pods, you have to always ssh-ed into the node to see if the new value applied or not. Also eventually (post 1.0) those mirrored pod's resource limit is going to be used by scheduler when calculating if user pods are fit or not, we need them to be accurated. Another concern is in the code implementation itself to distinuguish mirror pods future from rest of pods. I guess this shouldn't be the big issue here. Any more suggestions here? One puzzle I had is that why master component pods doesn't have issue at all. I manually restart kube-apiserver pod, still doesn't have the issue.\nDepending on time we could just remove the default limit from the limit range as a stop gap. Sent from my iPhone\nCan you just bypass defaulting at the apiserver when you create mirror pods? I can't think of any other solution that works in general and is easily maintainable. Approach 2 you described in the previous entry works if we are defaulting cpu limit, but breaks as soon as we default anything else.", "commid": "kubernetes_issue_8642", "tokennum": 459}], "negative_passages": []}
{"query_id": "q-en-kubernetes-451d67bcc3324e916a66e933c8d69271c7db65dfa489895c99f7a0154d400d1f", "query": "containers: - name: fluentd-cloud-logging image: gcr.io/google_containers/fluentd-gcp:1.6 <ins> resources: limits: cpu: 100m </ins> env: - name: \"FLUENTD_ARGS\" value: \"-qq\"", "positive_passages": [{"docid": "doc-en-kubernetes-f6117564d0d1387afeb4e79ddb55d47325739be1eed6d26971dac3a1b60079fd", "text": "Same problem with ignoring resource differences when comparing mirror pod to static pod -- as long as defaulting only touches resources, that works, but if we change it to touch other stuff, then it breaks.\nCommit I had can quickly fix current bleeding issue. Currently we only have master component pods and fluentd pod are file based by default. Master component pods doesn't create any issue now because mirror pods aren't created at the first place (due to recent change made by Also file-based pods will have issue only when its spec doesn't have initial value, and need to update (delete miss matched mirror pod, and recreate a new one). Please note that with my commit, everything is working even I manually update its cpu limit from 100m to 200m, there is no issue at all, and query pod shows accurate result with the new limit too: How badly we request all users using file-based pod feature providing default cpu limit for now? Eventually we want to get rid of file-based pods completely, also encouraging the user provides the initial resource limit is aligning with our direction in a long run anyway.\nJust to clarify, what I was suggesting was for a \"real fix\" not the temporary measure to stop the bleeding (which you already have in your PR). But what do you think of what I suggested as the longer-term fix? My point is that today, we default CPU, but in the future, we may default anything. It seems that the most maintainable fix is to just not do defaulting when creating mirror pod from static pod. Is that possible? I wonder if the reason manual update works (what you described in your last comment) is because we don't go through the defaulting when you do an update, only a create? (Though that sounds like a bug.) IMO we don't need CPU default right now, especially since we already have kubelet flag for limiting pods per machine (though unfortunately it's currently set to 100 because we haven't reconfigured the tests that intentionally run lots of pods per node, to override the flag. we can change the default to 30 and add an override mechanism if this is important.)\nComparing a config file with the live state and expecting them to match is doomed. The recommended approach is described by . Kubelet could store the config as an annotation in the mirror pod and compare with that.", "commid": "kubernetes_issue_8642", "tokennum": 504}], "negative_passages": []}
{"query_id": "q-en-kubernetes-451d67bcc3324e916a66e933c8d69271c7db65dfa489895c99f7a0154d400d1f", "query": "containers: - name: fluentd-cloud-logging image: gcr.io/google_containers/fluentd-gcp:1.6 <ins> resources: limits: cpu: 100m </ins> env: - name: \"FLUENTD_ARGS\" value: \"-qq\"", "positive_passages": [{"docid": "doc-en-kubernetes-335d12ba313aa19619a2c4b18ee4ddf7703e123f21840f5e77167fa2ece19bed", "text": "Does the scheduler favor nodes with the fewest pods even if they don't specify resources? LimitRange does cause that to happen.\nStoring the config as an annotation sounds good to me. Filed\nAlthough this issues was closed, it still appears in my environment\nSame here, this happens from time to time in our environments, is there a way to debug to find the root cause?", "commid": "kubernetes_issue_8642", "tokennum": 84}], "negative_passages": []}
{"query_id": "q-en-kubernetes-451fa37ea404b80e0bf92aee191a3634d5c3c6e295608abe452b0fc6a80341aa", "query": "// Determine if this is tagged as an Internal ELB internalELB := false internalAnnotation := apiService.Annotations[ServiceAnnotationLoadBalancerInternal] <del> if internalAnnotation != \"\" { </del> <ins> if internalAnnotation == \"false\" { internalELB = false } else if internalAnnotation != \"\" { </ins> internalELB = true }", "positive_passages": [{"docid": "doc-en-kubernetes-db8b10ac218e6b31cf143cad82d1c00f690bf029d07656bb83a6568343d76936", "text": "It's useful to have a helm chart that expose a value like . However, the annotation simply ignores , as seen in It's just checking that the value is not empty, so even if it's false - it'll try to create internal LB.\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\nGitHub didn't allow me to assign the following users: mcrute. Note that only and repo collaborators can be assigned. 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", "commid": "kubernetes_issue_69237", "tokennum": 182}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4523f688787ea72a5eee2a31a0921a8a91901ec4be3d23639647dc18b5f3c47c", "query": "for i, test := range tests { test.namespace.ObjectMeta.ResourceVersion = \"1\" test.oldNamespace.ObjectMeta.ResourceVersion = \"1\" <del> errs := ValidateNamespaceStatusUpdate(&test.oldNamespace, &test.namespace) </del> <ins> errs := ValidateNamespaceStatusUpdate(&test.namespace, &test.oldNamespace) </ins> if test.valid && len(errs) > 0 { t.Errorf(\"%d: Unexpected error: %v\", i, errs) t.Logf(\"%#v vs %#v\", test.oldNamespace.ObjectMeta, test.namespace.ObjectMeta)", "positive_passages": [{"docid": "doc-en-kubernetes-859a8b847337ca2cf9879726f3bdb71f0db5559ee2589591ceae612e41f71a1b", "text": "There is a funny subtle behvaiour in get namespaces, in which if i call more than one time, it seems that the removal from Terminating state is accelarated. It seems this might indicate a bug, or maybe its not a bug and the eventual semantics of is a little funny sometimes. in any case, here's what we are seeing : 1) when i delete a namespace the first time usning kubectl, we get a state change to . that is correct, of course. 2) but ... if make the call a second time, then the same status line is immediately removed from . Expected behaviour : A second call to \"kubectl delete ...\" shouldn't have any effect on the timing of removal of a namespace from 'Terminating' state*... So i guess there is some \"eventual consistency\" subtle bug that is resolved by repeated calls to\nsuggests this may not be e bug, maybe its just the etcd eventual deleter thingy.\nLooks to definitely be a bug. The 2nd delete seems to have interrupted the delete process and artifacts (like events) from the namespace still exist in etcd.\ninvestigating...\noops, see the error, will submit a fix.\nI have a fix, but need a test case, will submit PR tomorrow AM", "commid": "kubernetes_issue_6633", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-452a706cf53cc356105437790e5016c3d926759c016b802b4f1ebe760dd770f7", "query": "} func TestValidateSubpathMutuallyExclusive(t *testing.T) { <del> // Enable feature VolumeSubpathEnvExpansion and VolumeSubpath defer featuregatetesting.SetFeatureGateDuringTest(t, utilfeature.DefaultFeatureGate, features.VolumeSubpathEnvExpansion, true)() </del> <ins> // Enable feature VolumeSubpath </ins> defer featuregatetesting.SetFeatureGateDuringTest(t, utilfeature.DefaultFeatureGate, features.VolumeSubpath, true)() volumes := []core.Volume{", "positive_passages": [{"docid": "doc-en-kubernetes-a166ddd65322b2b4c2d8cbe35891249f4d033568413f3b77fc1f46ee1d1ee8b8", "text": "/kind cleanup /sig storage /sig node Description: Feature gate VolumeSubpathEnvExpansion was GA in 1.17 and is marked for removal in 1.19 Related Issues: GA Release:\n/assign\n/cc", "commid": "kubernetes_issue_89519", "tokennum": 48}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4537d9c45a7981997bc10fbbda6bb417f3b13aa96c271bd900f6aedf4e760de5", "query": "- user: root - name: /opt/cni - makedirs: True <del> - source: https://storage.googleapis.com/kubernetes-release/network-plugins/cni-09214926.tar.gz </del> <ins> - source: https://storage.googleapis.com/kubernetes-release/network-plugins/cni-42c4cb842dad606a84e93aad5a4484ded48e3046.tar.gz </ins> - tar_options: v <del> - source_hash: md5=58f8631f912dd88be6a0920775db7274 </del> <ins> - source_hash: md5=8cee1d59f01a27e8c2c10c120dce1e7d </ins> - archive_format: tar - if_missing: /opt/cni/bin", "positive_passages": [{"docid": "doc-en-kubernetes-3e2b7d9568ee0bf267de4bcdac04137844677bca3ba3f5eceb5026951de8c86d", "text": "Event for a pod: The cni plugins do exist at /opt/cni/bin. They cannot be executed and bash is complaining:\ncc\nI'm guessing this is a shared lib problem, since /usr/grte/v4/lib64/ld-linux-x86- doesn't exist on my gce vm. We should update docs to make it clear how someone would install manually (if they run into such problems again) and statically link (if the problem is indeed the shared lib) with something like Unsure how we'd support different GOOS (vend different tarballs vs checking in and building the plugin inline with our make scripts)\nuggh. These binaries need to be ultra-static or else we need to containerize them.\nEssentially doing would've prevented this bug :)\nAnd see for the CNI_ARGS problems\nalso , re ... however, I'm not too sure if your comment was mean to be on this ticket.\ncc\nI have a working version. I uploaded my cni binary with bug fix on GCS. change source to change sourcehash to Welcome to give it a try.\nAlso see problem:", "commid": "kubernetes_issue_23011", "tokennum": 252}], "negative_passages": []}
{"query_id": "q-en-kubernetes-453caf9feac845ae8179d4b780f5a16e12cbdb06e00f027a0fdc6dffbee0d07e", "query": "\"//staging/src/k8s.io/client-go/util/testing:go_default_library\", \"//staging/src/k8s.io/component-base/featuregate/testing:go_default_library\", \"//staging/src/k8s.io/component-base/version:go_default_library\", <del> \"//staging/src/k8s.io/cri-api/pkg/apis/runtime/v1alpha2:go_default_library\", </del> \"//vendor/github.com/google/cadvisor/info/v1:go_default_library\", \"//vendor/github.com/google/cadvisor/info/v2:go_default_library\", \"//vendor/github.com/stretchr/testify/assert:go_default_library\", \"//vendor/github.com/stretchr/testify/require:go_default_library\", \"//vendor/k8s.io/utils/mount:go_default_library\", <del> ], </del> <ins> ] + select({ \"@io_bazel_rules_go//go/platform:android\": [ \"//staging/src/k8s.io/cri-api/pkg/apis/runtime/v1alpha2:go_default_library\", ], \"@io_bazel_rules_go//go/platform:linux\": [ \"//staging/src/k8s.io/cri-api/pkg/apis/runtime/v1alpha2:go_default_library\", ], \"//conditions:default\": [], }), </ins> ) filegroup(", "positive_passages": [{"docid": "doc-en-kubernetes-59e10ac9f842c5137d16434532387dd09ba10f619a9264b3e368e8bd51bb44b7", "text": "What happened: It's most visible in the test <img width=\"323\" alt=\"Screen Shot 2020-05-20 at 6 09 10 PM\" src=\"https://user-\"It shows up in kind, kube- and kops jobs The regression was introduced somewhere within , possible culprits are: (FYI (FYI (FYI There are more tests affected, just not as prominently (visually inspecting ) [sig-apps] StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications with PVCs [sig-apps] StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance] [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Inline-volume (default fs)] volumes should store data [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data I wasn't sure whether to tag this as kind/regression or not, I'll leave that up to or someone /sig node /sig api-machimery /sig scheduling\nThe label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : What happened: It's most visible in the test (FYI (FYI (FYI StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications with PVCs [sig-apps] StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance] [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Inline-volume (default fs)] volumes should store data [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data /sig api-machimery /sig scheduling 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.", "commid": "kubernetes_issue_91316", "tokennum": 506}], "negative_passages": []}
{"query_id": "q-en-kubernetes-453caf9feac845ae8179d4b780f5a16e12cbdb06e00f027a0fdc6dffbee0d07e", "query": "\"//staging/src/k8s.io/client-go/util/testing:go_default_library\", \"//staging/src/k8s.io/component-base/featuregate/testing:go_default_library\", \"//staging/src/k8s.io/component-base/version:go_default_library\", <del> \"//staging/src/k8s.io/cri-api/pkg/apis/runtime/v1alpha2:go_default_library\", </del> \"//vendor/github.com/google/cadvisor/info/v1:go_default_library\", \"//vendor/github.com/google/cadvisor/info/v2:go_default_library\", \"//vendor/github.com/stretchr/testify/assert:go_default_library\", \"//vendor/github.com/stretchr/testify/require:go_default_library\", \"//vendor/k8s.io/utils/mount:go_default_library\", <del> ], </del> <ins> ] + select({ \"@io_bazel_rules_go//go/platform:android\": [ \"//staging/src/k8s.io/cri-api/pkg/apis/runtime/v1alpha2:go_default_library\", ], \"@io_bazel_rules_go//go/platform:linux\": [ \"//staging/src/k8s.io/cri-api/pkg/apis/runtime/v1alpha2:go_default_library\", ], \"//conditions:default\": [], }), </ins> ) filegroup(", "positive_passages": [{"docid": "doc-en-kubernetes-aa1ca8a6c4f552108d5e4f5627cf5341a0bb7748f7b82e510f647cbc02b0a76b", "text": "</details\n/cc\nwill increase the time for deletion of pod and it should be expected because currently pod is deleted from apiserver before removing the sandbox container but after this fix pod will be deleted from the apiserver only after deleting the sandbox container.\n/remove-sig scheduling doesn't affect scheduling running time at all.\nYeah, is almost definitely the culprit. Last time we changed that code path, it also caused a regression. The degradation in performance is expected, but a 5x slowdown is definitely larger than it should be.\ndo we know if that's because the status used by the path is stale, or if removing sandboxes is actually that slow?\nif there's not a quick fix, should we revert and bring it back in once the root issue is understood?\nI think a revert is appropriate in this case.\nok, I'll open it\nopen at\nI agree with that 5x is something which shouldn't happen and i can take a look on why thats happening and that might require changing the way how the sandbox is currently deleted which is only during GC.", "commid": "kubernetes_issue_91316", "tokennum": 237}], "negative_passages": []}
{"query_id": "q-en-kubernetes-456a16074a6c99cc150d1712641207dd4f0a8ec3ca42a22759d5d84b914a9862", "query": "} return nil, err } <ins> if !matchImageTagOrSHA(resp, image) { return nil, imageNotFoundError{ID: image} } </ins> return &resp, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-73e94f1f9679cf5fca554c149f1c357d9b16156cc7199a4d351eb3b22980b589", "text": "We had rather strange case today when after rolling update one of the kubelet's started wrong container. For this specific replicationcontroller we are using What happened was that after rolling-update when i started to debug the issue i discovered that one of the kubelet's did not pull the image: When looking into what image it actually started i saw: When checking from the actual node i saw this It seems that instead of starting myimage with tag 2208 kubelet started image tagged as 1393 since the docker image id starts with 2208.", "commid": "kubernetes_issue_30355", "tokennum": 119}], "negative_passages": []}
{"query_id": "q-en-kubernetes-45e0c7c96f7394099091ed1419384fd4fa4965594676cd10bc95d57159b40412", "query": "github.com/opencontainers/go-digest v1.0.0/go.mod h1:0JzlMkj0TRzQZfJkVvzbP0HBR3IKzErnv2BNG4W4MAM= github.com/opencontainers/image-spec v1.0.2 h1:9yCKha/T5XdGtO0q9Q9a6T5NUCsTn/DrBg0D7ufOcFM= github.com/opencontainers/image-spec v1.0.2/go.mod h1:BtxoFyWECRxE4U/7sNtV5W15zMzWCbyJoFRP3s7yZA0= <del> github.com/opencontainers/runc v1.1.4 h1:nRCz/8sKg6K6jgYAFLDlXzPeITBZJyX28DBVhWD+5dg= </del> github.com/opencontainers/runc v1.1.4/go.mod h1:1J5XiS+vdZ3wCyZybsuxXZWGrgSr8fFJHLXuG2PsnNg= <ins> github.com/opencontainers/runc v1.1.5 h1:L44KXEpKmfWDcS02aeGm8QNTFXTo2D+8MYGDIJ/GDEs= github.com/opencontainers/runc v1.1.5/go.mod h1:1J5XiS+vdZ3wCyZybsuxXZWGrgSr8fFJHLXuG2PsnNg= </ins> github.com/opencontainers/runtime-spec v1.0.2/go.mod h1:jwyrGlmzljRJv/Fgzds9SsS/C5hL+LL3ko9hs6T5lQ0= github.com/opencontainers/runtime-spec v1.0.3-0.20200929063507-e6143ca7d51d/go.mod h1:jwyrGlmzljRJv/Fgzds9SsS/C5hL+LL3ko9hs6T5lQ0= github.com/opencontainers/runtime-spec v1.0.3-0.20210326190908-1c3f411f0417/go.mod h1:jwyrGlmzljRJv/Fgzds9SsS/C5hL+LL3ko9hs6T5lQ0=", "positive_passages": [{"docid": "doc-en-kubernetes-3a5f1791fd28a186fcf23c773fa97525e98fb83cc70e7098ac61d449614dcefb", "text": "opencontainers/runc has fixed three CVEs: Latest runc is pulled by k/k Check runc version in file No response n/a n/a <details</details<details</details<details</details<details</details\n/assign /sig security architecture release\n/triage accepted", "commid": "kubernetes_issue_117094", "tokennum": 68}], "negative_passages": []}
{"query_id": "q-en-kubernetes-45ea7bb63b96eb792aed228dc7a8fcfc088731a6d0f5d925deee37756e48c689", "query": "<ins> /* Copyright 2023 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package plugin import ( \"testing\" \"github.com/stretchr/testify/assert\" v1 \"k8s.io/api/core/v1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" ) func getFakeNode() (*v1.Node, error) { return &v1.Node{ObjectMeta: metav1.ObjectMeta{Name: \"worker\"}}, nil } func TestRegistrationHandler_ValidatePlugin(t *testing.T) { newRegistrationHandler := func() *RegistrationHandler { return NewRegistrationHandler(nil, getFakeNode) } for _, test := range []struct { description string handler     func() *RegistrationHandler pluginName  string endpoint    string versions    []string shouldError bool }{ { description: \"no versions provided\", handler:     newRegistrationHandler, shouldError: true, }, { description: \"unsupported version\", handler:     newRegistrationHandler, versions:    []string{\"v2.0.0\"}, shouldError: true, }, { description: \"plugin already registered with a higher supported version\", handler: func() *RegistrationHandler { handler := newRegistrationHandler() if err := handler.RegisterPlugin(\"this-plugin-already-exists-and-has-a-long-name-so-it-doesnt-collide\", \"\", []string{\"v1.1.0\"}, nil); err != nil { t.Fatal(err) } return handler }, pluginName:  \"this-plugin-already-exists-and-has-a-long-name-so-it-doesnt-collide\", versions:    []string{\"v1.0.0\"}, shouldError: true, }, { description: \"should validate the plugin\", handler:     newRegistrationHandler, pluginName:  \"this-is-a-dummy-plugin-with-a-long-name-so-it-doesnt-collide\", versions:    []string{\"v1.3.0\"}, }, } { t.Run(test.description, func(t *testing.T) { handler := test.handler() err := handler.ValidatePlugin(test.pluginName, test.endpoint, test.versions) if test.shouldError { assert.Error(t, err) } else { assert.NoError(t, err) } }) } t.Cleanup(func() { handler := newRegistrationHandler() handler.DeRegisterPlugin(\"this-plugin-already-exists-and-has-a-long-name-so-it-doesnt-collide\") handler.DeRegisterPlugin(\"this-is-a-dummy-plugin-with-a-long-name-so-it-doesnt-collide\") }) } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-e1c6f7407b346df6fb6212f23a2f930e04198e198bb03b9cff5041967802082d", "text": "The PR above moved everything related to into because that was where most of the code already was, but didn't renamed the files to avoid a larger diff and merge conflicts. Once is merged, we can do the renaming. Code clarity. /sig node\n/triage accepted /priority important-soon\n/assign\na PR can be created for this now.\nwill do", "commid": "kubernetes_issue_125924", "tokennum": 75}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4610f2bcc7deee901873b72e4b9130164edff2d1668e47b9431900f1766f2229", "query": "var map_EndpointPort = map[string]string{ \"\":         \"EndpointPort represents a Port used by an EndpointSlice\", <del> \"name\":     \"The name of this port. All ports in an EndpointSlice must have a unique name. If the EndpointSlice is dervied from a Kubernetes service, this corresponds to the Service.ports[].name. Name must either be an empty string or pass IANA_SVC_NAME validation: * must be no more than 15 characters long * may contain only [-a-z0-9] * must contain at least one letter [a-z] * it must not start or end with a hyphen, nor contain adjacent hyphens Default is empty string.\", </del> <ins> \"name\":     \"The name of this port. All ports in an EndpointSlice must have a unique name. If the EndpointSlice is dervied from a Kubernetes service, this corresponds to the Service.ports[].name. Name must either be an empty string or pass DNS_LABEL validation: * must be no more than 63 characters long. * must consist of lower case alphanumeric characters or '-'. * must start and end with an alphanumeric character. Default is empty string.\", </ins> \"protocol\": \"The IP protocol for this port. Must be UDP, TCP, or SCTP. Default is TCP.\", \"port\":     \"The port number of the endpoint. If this is not specified, ports are not restricted and must be interpreted in the context of the specific consumer.\", }", "positive_passages": [{"docid": "doc-en-kubernetes-b73bb51cef5016ee2dcd80aae4248808fec811a4dad3a3b7abbba7673a446c48", "text": "What happened: No endpoints created in the EndpointSlice for my service due to the port on the service being too long. Logs show: EndpointSlice created has no endpoint: What you expected to happen: Service that works with Endpoints should work with EndpointSlice. If this is intentional, it should be clearly documented How to reproduce it (as minimally and precisely as possible): Create a service with a long port name Environment: Kubernetes version (use ): 1.16 Cloud provider or hardware configuration: kind\n/sig networking\nThe label(s) cannot be applied. These labels are supported: <detailsIn response to : /sig networking 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\n/sig network These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by vllry. \u200d\nFor a rough measure of impact, Istio had 5 ports that were over this limit (and many more that were right at 15 characters), so I suspect it may not be terribly rare.\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nThis needs to be resolved before endpointslices graduate from alpha\n/assign\n/remove-triage unresolved", "commid": "kubernetes_issue_84388", "tokennum": 292}], "negative_passages": []}
{"query_id": "q-en-kubernetes-464b259299165091540610265ff439082d84d420b9f59d18f0f7aaa8ea4c793a", "query": "\"github.com/GoogleCloudPlatform/kubernetes/pkg/admission\" \"github.com/GoogleCloudPlatform/kubernetes/pkg/api\" <ins> \"github.com/GoogleCloudPlatform/kubernetes/pkg/api/errors\" </ins> \"github.com/GoogleCloudPlatform/kubernetes/pkg/client\" \"github.com/GoogleCloudPlatform/kubernetes/pkg/client/cache\" )", "positive_passages": [{"docid": "doc-en-kubernetes-c343f6e7b091e9b4529e6227acb6329e7535006eb05bcc59008c8d5d37213826", "text": "While running one of my soak tests I noticed the error message: I don't see why I should get this error message. Why should it matter if the namespace already exists? It was created as part of the service creation call just beforehand. And the second attempt to create this pod in exactly the same namespace works. Is this a bug?\nRunning a second time did not produce this error.\nI agree it should not matter. The error is produced there, and I suspect there were multiple concurrent calls being made that try to create a resource in a namespace that had not yet existed. We need to update the code in question to swallow the error if the namespace already exists.\nFYI - longer term, I would like to eliminate the use of autoprovision of namespace and require you to first create a namespace manually. what is there now is more to preserve existing behavior prior to namespace as object was introduced.", "commid": "kubernetes_issue_5873", "tokennum": 190}], "negative_passages": []}
{"query_id": "q-en-kubernetes-46531a8b9f1e7cd4a4761ed0ba9d1fa5eed0f1ce9f09610badd3e1306d46950e", "query": "- name: config mountPath: /etc/config nodeSelector: <del> # TODO(liggitt): switch to node.kubernetes.io/masq-agent-ds-ready in 1.16 beta.kubernetes.io/masq-agent-ds-ready: \"true\" </del> <ins> node.kubernetes.io/masq-agent-ds-ready: \"true\" </ins> volumes: - name: config configMap:", "positive_passages": [{"docid": "doc-en-kubernetes-2c9ef8984ebaf899659836b925069334113c910fc47ebe0516a7d659674f044a", "text": "xref In 1.16: change the metadata-proxy addon to use change the kube-proxy addon to use change the masq-agent addon to use stop setting , , and in kube-up\nHey I'm trying to start to contribute to kubernetes and this seem to be an easy task. Can I help with this one?", "commid": "kubernetes_issue_75050", "tokennum": 77}], "negative_passages": []}
{"query_id": "q-en-kubernetes-467ae2f0ab912393343d7b4a25440ec5a0a27e59cd385f71df7550f45b04c431", "query": "// and updating Scale for any resource which implements the `scale` subresource, // as long as that subresource operates on a version of scale convertable to // autoscaling.Scale. <del> package scale </del> <ins> package scale // import \"k8s.io/client-go/scale\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-460ceb7b52a1ab0cadc1b29d7eee5cc1013b8d23be9bca0d145119ffcf7b27c6", "text": "Look at one of the directories under (Please don't pick more than one directory for one PR as it will cause issues for reviewers) Find all the files named (example find -name ) See the following link it has a this tells tools how this package needs to be imported. So we should ensure that each has an import Add a description appropriate to the package (similar to the one below) Look through sub directories and see if there are any other important directories that are likely to be used by outside users and add a Why are we doing this? We perfer to use vanity urls instead of directly using to refer to code, so this helps ensure that tools honor our wish. See It would be good to have some package level documentation since these directories under staging/ are meant to be for use by folks outside of kubernetes github org. /good-first-issue\n/kind documentation /sig architecture\ncurrently working my through Not going to use / assign since there could be a number of PRs for this issue.\n/lifecycle active /good-first-issue edit: hmm..\nThis request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /lifecycle active /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\nMay I try on\nIIUC this means that there needs to be a even at the root of the repo? Then how does work? :thinking:\nHi , can I make a PR for this directory ?\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_68231", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-467ae2f0ab912393343d7b4a25440ec5a0a27e59cd385f71df7550f45b04c431", "query": "// and updating Scale for any resource which implements the `scale` subresource, // as long as that subresource operates on a version of scale convertable to // autoscaling.Scale. <del> package scale </del> <ins> package scale // import \"k8s.io/client-go/scale\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-5f31f1c27d7198dc83b313154ff681043a8b41e17eb5d3ddf32cd84bc023f931", "text": "/lifecycle rotten\nI guess this is still not done, was supposed to partially fix this issue. /reopen\nReopened this issue. <detailsIn response to : I guess this is still not done, was supposed to partially fix this 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\n/remove-lifecycle rotten /area code-organization", "commid": "kubernetes_issue_68231", "tokennum": 93}], "negative_passages": []}
{"query_id": "q-en-kubernetes-469d90a0027521be7f34c93b119d7a460cfc9ca845b80a3804fd3868551580ae", "query": "Reject      = \"REJECT\" ToDest      = \"--to-destination \" Recent      = \"recent \" <ins> MatchSet    = \"--match-set \" </ins> ) type Rule map[string]string", "positive_passages": [{"docid": "doc-en-kubernetes-4b95e73f98faca5940a16ee2fccddf37ae93437213e073578ff34d76b732271f", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Service loadbalancer source range don't work in ipvs proxy mode. Which result in gci-gce-ipvs CI failed. http://k8s- How to reproduce it (as minimally and precisely as possible): In gce environment. a service with backend. service type to service util service external IP is specified. the service from pod inside and pod out of the . Environment: Kubernetes version (use ): master Cloud provider or hardware configuration: gce OS (e.g. from /etc/os-release): ubuntu Kernel (e.g. ): Install tools: cluster/kube- Others:\n/kind bug /sig network /label ipvs\n/area ipvs\nThe test seems to be flaky now. Can you take a look please?\nI don't know why, but I think this flaky have the similiar reason with other normal service-test cases, like Those flaky are pretty annoying, problem is, I have run those cases in my own environment many times, never fail... : ( But still, I'll do my best to find the reason.", "commid": "kubernetes_issue_61090", "tokennum": 264}], "negative_passages": []}
{"query_id": "q-en-kubernetes-46d2bbe914d072ff19e5d81852edb74c0d59c57395a0341b2efc8260620aef19", "query": "<del> apiVersion: extensions/v1beta1 </del> <ins> apiVersion: networking.k8s.io/v1beta1 </ins> kind: Ingress metadata: name: static-ip", "positive_passages": [{"docid": "doc-en-kubernetes-bb7c21eb048735f6a80e177a210d26530b5959539babed9d56a66ccfff61adf4", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: Which test(s) are failing: Since when has it been failing: Testgrid link: https://k8s- Reason for failure: Anything else we need to know: /cc /milestone v1.19 /priority important-soon /sig network\nRef:\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nmy fu points me to this commit [] Fix multiple conversion tests that belongs to this PR , that seems related can you confirm if that PR is causing this test to fail? (should we gate on this test?)\nYes, that PR is related to the failure. The test utility is trying to convert extensions/v1beta1 data read from various files directly to a go type. This was never a valid thing to do, and happened to silently succeed because the two structs had an identical structure. This is exactly the type of bug was designed to flush out\nthe correct fix is to update the test/e2e/testing- files to\n/assign\nIt was my PR that broke this - I can also fix that.\nThanks, o it was the commit that was good but the test that was wrong :upsidedownface: , At least I got right the commit :sweat_smile:\nis out for review (talked with offline, he was aware that I'll send that out)", "commid": "kubernetes_issue_90451", "tokennum": 318}], "negative_passages": []}
{"query_id": "q-en-kubernetes-46ecec888e764ba7285f1a33472c67d42956f8075484b8836deee95064ac9e09", "query": "<del> linux/amd64=alpine:3.12 linux/arm=arm32v6/alpine:3.12 linux/arm64=arm64v8/alpine:3.12 linux/ppc64le=ppc64le/alpine:3.12 linux/s390x=s390x/alpine:3.12 </del> <ins> linux/amd64=alpine:3.16 linux/arm=arm32v6/alpine:3.16 linux/arm64=arm64v8/alpine:3.16 linux/ppc64le=ppc64le/alpine:3.16 linux/s390x=s390x/alpine:3.16 </ins> windows/amd64/1809=REGISTRY/busybox:1.29-2-windows-amd64-1809 windows/amd64/ltsc2022=REGISTRY/busybox:1.29-2-windows-amd64-ltsc2022", "positive_passages": [{"docid": "doc-en-kubernetes-496d6605c1619bb131a3d458a58442cd69b560a8ee63a4aeca6bff6594949a24", "text": "The test image currently uses as its BASEIMAGE: Per , v3.12 reached end of support on 2022-05-01 and is no longer receiving regular bugfixes or security fixes. Current versions of the image appear vulnerable to known CVEs as a result. I don't know if a fix is quite as simple as just The image's base should be an in-support version which is maintained with at least security fixes. No response <details</details<details</details<details</details<details</details<details</details<details</details\n/sig testing\nis like that, but then there are 2 additional steps the changes the image that has been built with the postsubmit job the repo to use the new image More detail in If you want to try, please make sure you are going to follow up with all the steps, you can see other promotions PRs too /help\nThis 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 : is like that, but then there are 2 additional steps promote the image that has been built with the postsubmit job update the repo to use the new image </details\nThank you for this information! Is the manual and of images described in that same document something that you would consider a prerequisite for a proposed change like this? Or is it safe to assume that the automated PR test bucket(s) would provide sufficient test coverage?\nI always trust the CI system\nGood enough for me! Leading off with\n/triage accepted", "commid": "kubernetes_issue_124377", "tokennum": 441}], "negative_passages": []}
{"query_id": "q-en-kubernetes-47465fe8816417c02c40a19dfb97d753521676e0f20d2b2d300b96d801c88151", "query": "updateMeta(&podMeta, \"Pod\") setMeta := set.TypeMeta updateMeta(&setMeta, \"StatefulSet\") <del> policy := set.Spec.PersistentVolumeClaimRetentionPolicy </del> <ins> policy := getPersistentVolumeClaimRetentionPolicy(set) </ins> const retain = apps.RetainPersistentVolumeClaimRetentionPolicyType const delete = apps.DeletePersistentVolumeClaimRetentionPolicyType switch {", "positive_passages": [{"docid": "doc-en-kubernetes-0282c95c8ddc11607ba516e065f4121126017f786957d03a031978171c244a62", "text": "The replicas is 3 but just create 1 pod 'web-0' and one pvc, then kube-controller-manager panic happend. Should create 3 pod and 3 pvc add '--feature-gates=StatefulSetAutoDeletePVC=true' arg for kube-controller-manager, then create statefulset with 2 replicas and volumeClaimTemplates. No response <details</details<details</details<details</details<details</details<details</details<details</details\n/sig apps\nI can reproduce the issue and want to fix it. It seems like variables cause . /assign\n/triage accepted\nGreat find! Does this only happen on an upgraded cluster? I'll spin up a cluster and see if the e2e test catches this problem.\nThe e2e tests are still passing on a 1.24 cluster, so I suspect this is an upgrade problem. I wonder if there are other holes here.\nI installed the Kubernetes 1.25 cluster directly using and still reproduced this issue, so it was probably not caused by upgrading the cluster.\nInteresting. I thought that would set the policy to be non-nil. Let's keep this bug open after you submit your PR as I think something else is going on here---I don't think we should be seeing the null policy in the first place.\nI suspect that somewhere accidentally set it to nil, and I'll keep looking at this code.\nI tried the following (and also with parallel pod management), and it didn't seem to cause the panic. This was a 1.24 cluster, maybe this is only happening on head versions?\nI just tried this on a kind cluster running on k8s head, and the problem didn't seem to reproduce. But this was setting the feature flag default in I wonder----does the api server need to have the feature gate as well? That would explain why defaulting wasn't happening.\nAs far as I'm concerned,I just set the in kube-controller-manager manifests to reproduce this issue. I repeat the yaml used as follows: I tested that in statefulset yaml, setting or not would cause the component to panic. The panic logs are the same as above, so ignore them here.", "commid": "kubernetes_issue_113319", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-47465fe8816417c02c40a19dfb97d753521676e0f20d2b2d300b96d801c88151", "query": "updateMeta(&podMeta, \"Pod\") setMeta := set.TypeMeta updateMeta(&setMeta, \"StatefulSet\") <del> policy := set.Spec.PersistentVolumeClaimRetentionPolicy </del> <ins> policy := getPersistentVolumeClaimRetentionPolicy(set) </ins> const retain = apps.RetainPersistentVolumeClaimRetentionPolicyType const delete = apps.DeletePersistentVolumeClaimRetentionPolicyType switch {", "positive_passages": [{"docid": "doc-en-kubernetes-bacc559e7a05833801486ab81cebdf65b8969406a4ba99bead3e0d4a0613defb", "text": "statefulset with : The environment\nI believe you---this doesn't seem to be well-documented, but it's my understanding that you need to set the feature gate on all of the system components. Obviously failing to do so shouldn't cause a panic, so thank you again for finding & fixing this bug! Let me ask around to see what the expected behavior is. I know there may be skew between kubelets and master versions, but I didn't expect to have to deal with skew between master components.\nI read the code, and now I understand what you mean. This feature gate must be enabled in both the and components. We need to describe it in the to prevent someone from ignoring the component, which also needs to enable the feature gate.\nI don't think we need all the system components, like the component, right? I read the original KEP documentation. This feature gate only involves components and :\nI had a bit of discussion about this with others. Because upgrades don't occur atomically, any feature gate has to work regardless of how the other system components are configured (things shouldn't panic!). I suppose if the cluster administrator wants to track what needs to be enabled on each feature they can try to sequence which component has which feature gate. If it were me I'd try to make all the components consistent though.\nThis is certainly a method, but it is a bit more cumbersome for the administrator. It is best to have a place for the document to be queried by the administrator and avoid confusion. I don't think everyone is very familiar with the k8s mechanism. I suggest adding a partial description to this section of the : Before: After: I can submit this PR on .\nThis is going to be true of any api change. When you tried to use it with only adding the controller manager feature gate, I think you would be able to set the retain policy, but there wouldn't be any defaulting or validation (?).\nI've seen other feature gates that say what components are needed to enable it to use the new feature. For example: If it's not necessary, then I close .\nonly adding the controller manager feature gate, I think you would be able to set the retain policy, but there wouldn't be any defaulting or validation (?). I remember just enabling it in kube-controller-manager.", "commid": "kubernetes_issue_113319", "tokennum": 500}], "negative_passages": []}
{"query_id": "q-en-kubernetes-47465fe8816417c02c40a19dfb97d753521676e0f20d2b2d300b96d801c88151", "query": "updateMeta(&podMeta, \"Pod\") setMeta := set.TypeMeta updateMeta(&setMeta, \"StatefulSet\") <del> policy := set.Spec.PersistentVolumeClaimRetentionPolicy </del> <ins> policy := getPersistentVolumeClaimRetentionPolicy(set) </ins> const retain = apps.RetainPersistentVolumeClaimRetentionPolicyType const delete = apps.DeletePersistentVolumeClaimRetentionPolicyType switch {", "positive_passages": [{"docid": "doc-en-kubernetes-dc6539ce5e1daf74890724a45ab3f8f9d1791d28b0765a687405f604711fc05a", "text": "it using the retain policy, but the statefulset does not have the policy from output of (It should be the apiserver authentication forbids it)\nYeah I think that makes sense. Thanks for finding this issue! After your PR with the panic fix is submitted, I think we can close this?\nYes. I agree. /close\nClosing this issue. <detailsIn response to : Yes. I agree. 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", "commid": "kubernetes_issue_113319", "tokennum": 117}], "negative_passages": []}
{"query_id": "q-en-kubernetes-477c894487d373c542d8bbc366b0a7a3fb7f8615872bc06e8eae0f633a4cb2b0", "query": "if len(obj.Type) == 0 { obj.Nullable = false // because this does not roundtrip through go-openapi } <ins> if obj.XIntOrString { obj.Type = \"\" } </ins> }, func(obj *apiextensions.JSONSchemaPropsOrBool, c fuzz.Continue) { if c.RandBool() {", "positive_passages": [{"docid": "doc-en-kubernetes-42eca355948acd2923f06d9ab50c5116c5afebe4d73334e949a0d732f7352d29", "text": "The server-side validation does not check the type of values with . Create a CRD like: Then create a CR: It is not rejected, but should because must not be a boolean.", "commid": "kubernetes_issue_78817", "tokennum": 40}], "negative_passages": []}
{"query_id": "q-en-kubernetes-477c91e87749c6d80f210a863a937cc2c67ee9ac1232fd8d09500a1b429b2c34", "query": "client := http.Client{} request, err := http.NewRequest(\"PATCH\", server.URL+\"/api/version/namespaces/default/simple/\"+ID, bytes.NewReader([]byte(`{\"labels\":{\"foo\":\"bar\"}}`))) <del> request.Header.Set(\"Content-Type\", \"application/merge-patch+json\") </del> <ins> request.Header.Set(\"Content-Type\", \"application/merge-patch+json; charset=UTF-8\") </ins> _, err = client.Do(request) if err != nil { t.Errorf(\"unexpected error: %v\", err)", "positive_passages": [{"docid": "doc-en-kubernetes-c21754b57b54e9212f2cf7773a0f449c984b1bc5da8671633611701b2ce62a1e", "text": "Given a request with a Content-Type header set to , the server will respond with an error because it does not exactly match the existing strings. Some browsers (Firefox, see: ) will automatically add to a Content-Type header when making an XHR request.", "commid": "kubernetes_issue_14872", "tokennum": 56}], "negative_passages": []}
{"query_id": "q-en-kubernetes-47816e978d0f7a1210155e6c8fe2156e69154e3acd5af2ceabe7070204db1e54", "query": "\"tagline\" : \"You Know, for Search\" } ``` <del> Visiting the URL `http://104.154.91.224:5601` should show the Kibana viewer for the logging information stored in the Elasticsearch service running at `http://104.154.81.135:9200`. </del> <ins> Visiting the URL `https://130.211.122.180/api/v1beta3/proxy/namespaces/default/services/kibana-logging` should show the Kibana viewer for the logging information stored in the Elasticsearch service. </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-bc75029de49571476e249812075ff7ffff85fb8014f5cfe5e32228962baa98b2", "text": "Hi , I followed the instructions in examples/logging-demo, and there was no \"external IP\" field for elasticsearch-logging or kibana-logging, as shown below: I start up my cluster via cluster/kube- Did I miss something or is it a bug? Thanks.\nCorrect. This demo does not create an ELB so there is no external IP address. Access is via service proxy at the master. Type: and you should see the URLs for Elasticsearch and Kibana.\nplease let us know whether: a. Satnam's comment resolves your issue b. the demo should be updated to prevent this misunderstanding c. the issue isn't resolved Thank you!\nYes, Satnam's comment resolve the issue. I updated the demo in .\nAwesome, thanks for sending the patch! We'll discuss there. Always fantastic to have docs updated regularly by folks trying them.", "commid": "kubernetes_issue_7818", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-47c3bc2a552279fa00e4128901f7a007ad23a711a3912876544480accc195d94", "query": "} // Uses the same niceness level as cadvisor.fs does when running du // Uses -B 1 to always scale to a blocksize of 1 byte <del> out, err := exec.Command(\"nice\", \"-n\", \"19\", \"du\", \"-s\", \"-B\", \"1\", path).CombinedOutput() </del> <ins> out, err := exec.Command(\"nice\", \"-n\", \"19\", \"du\", \"-x\", \"-s\", \"-B\", \"1\", path).CombinedOutput() </ins> if err != nil { <del> return nil, fmt.Errorf(\"failed command 'du' ($ nice -n 19 du -s -B 1) on path %s with error %v\", path, err) </del> <ins> return nil, fmt.Errorf(\"failed command 'du' ($ nice -n 19 du -x -s -B 1) on path %s with error %v\", path, err) </ins> } used, err := resource.ParseQuantity(strings.Fields(string(out))[0]) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-1983b5ea5659683f3a4ba96803f2792373389d2c0ef10ffa2f957e3f76064a9d", "text": "I'm using K8S 1.10 and have a specific use case where I'm trying to use an emptyDir to share mounts between two containers in a pod. I'm using the MountPropagation feature successfully, but while debugging another issue I noticed that the node was running a very long running du command. Looking into the source I noted: Which runs du on any emptyDir, do measure disk usage. I recommend that in this case we should add the -x flag that will skip any mounted directories as they do not count against the file usage and would make these scans a lot faster. I could of course add a simple pull request for this but first wanted to see if this was known and on purpose. To reproduce bind mount/loop mount/device mount any large/slow directory into an emptyDir volume and watch as the du process slogs away Environment: Kubernetes 1.10 GKE <!-- DO NOT EDIT BELOW THIS LINE --/kind bug\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI think it makes sense to ignore submounts.\nIssues 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\n/remove-lifecycle stale\nIssues 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\ndo you still want to submit a PR to fix this? Thanks!\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_71012", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-47c3bc2a552279fa00e4128901f7a007ad23a711a3912876544480accc195d94", "query": "} // Uses the same niceness level as cadvisor.fs does when running du // Uses -B 1 to always scale to a blocksize of 1 byte <del> out, err := exec.Command(\"nice\", \"-n\", \"19\", \"du\", \"-s\", \"-B\", \"1\", path).CombinedOutput() </del> <ins> out, err := exec.Command(\"nice\", \"-n\", \"19\", \"du\", \"-x\", \"-s\", \"-B\", \"1\", path).CombinedOutput() </ins> if err != nil { <del> return nil, fmt.Errorf(\"failed command 'du' ($ nice -n 19 du -s -B 1) on path %s with error %v\", path, err) </del> <ins> return nil, fmt.Errorf(\"failed command 'du' ($ nice -n 19 du -x -s -B 1) on path %s with error %v\", path, err) </ins> } used, err := resource.ParseQuantity(strings.Fields(string(out))[0]) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-eea01b18436aabcf24011fc8d3531d9a102c009dd1b30b027c1434bcedaabd88", "text": "/lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nClosing 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", "commid": "kubernetes_issue_71012", "tokennum": 120}], "negative_passages": []}
{"query_id": "q-en-kubernetes-47dcfb3757aa65b051f15714fc56d6732970a3bc443353dca07e34c79d5cf4be", "query": "} } if test.disableAttach { <del> gomega.Expect(err).To(gomega.HaveOccurred(), \"Unexpected VolumeAttachment found\") </del> <ins> framework.ExpectError(err, \"Unexpected VolumeAttachment found\") </ins> } })", "positive_passages": [{"docid": "doc-en-kubernetes-c082543f1889f90c5ee780d309eeb8f41ee57a7e9e8bb6b6fe7c2e4381ff48af", "text": "What happened: After fixing golint failures under (now still in progress), we need to put for each and . Then common error checking code has become like: We can replace this code with which is more readable and easy to be understood what the code does. Now we have following e2e test directories which can be replaced: [x] test/e2e/apimachinery/ () [x] test/e2e/apps/ () [x] test/e2e/auth/ () [x] test/e2e/common/ () [x] test/e2e/node/ () [x] test/e2e/storage/ () [x] () [x] () [x] () [x] () [x] () [x] () [x] [x] test/e2e/storage/persistentvolumes- [x] () [x] () [x] [x] [x] [x] [x] ()\n/sig testing /kind cleanup\n/assign PR will be submitted soon.\nFix the following in\nFix in\nFix in\nHi, maybe I could take files beneath test/e2e/storage/vsphere/\noops, I'm finished and prepare for PR.\nThank you That's OK\nFix the following in\n/assign\nAll related PRs were merged. I think this ticket can be closed. BTW, should we also replace to ?\nThanks for your work. thing is managed with We are almost finishing the work also :-)\n/remove-kind bug\nI found in these files. I'm working on :\nI can work to the following item.", "commid": "kubernetes_issue_77706", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-47f887701195853bf8279d0146553b968de4c554bf44107091f82af6c5941375", "query": "action MUST be validated. release: v1.21 file: test/e2e/network/service.go <ins> - testname: Service, deletes a collection of services codename: '[sig-network] Services should delete a collection of services [Conformance]' description: Create three services with the required labels and ports. It MUST locate three services in the test namespace. It MUST succeed at deleting a collection of services via a label selector. It MUST locate only one service after deleting the service collection. release: v1.23 file: test/e2e/network/service.go </ins> - testname: Find Kubernetes Service in default Namespace codename: '[sig-network] Services should find a service from listing all namespaces [Conformance]'", "positive_passages": [{"docid": "doc-en-kubernetes-5e1e446ffee113a0fecf68600791d8062befcc769908a1fdd16ec9abcfdd9c85", "text": "[X] Two weeks soak end date: Nov 18 According to this APIsnoop query, there are still a remaining Service endpoint which is untested. A service resource didn&rsquo;t support endpoint until was merged. Create a watch to track service events Create a service with a static label. Confirm via the watch that the service was created. Delete the service via the service with the dynamic client with . Confirm via the watch that the service was deleted. The above steps have been implemented in the follwing . This query shows all the endpoints hit within a short period of running the above e2e test If a test with these calls gets merged, test coverage will go up by 1 point This test is also created with the goal of conformance promotion. /sig testing /sig network /area conformance\n/triage accepted\nWaiting on 2 week soak before promoting the test to conformance /reopen\nReopened this issue. <detailsIn response to : Waiting on 2 week soak before promoting the test to conformance /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_106032", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-47fc2bf1e4bcb566ff14c641abb7d8cbddc44a94368bc5a8a2e27f7723aac476", "query": "allErrs = append(allErrs, metavalidation.ValidateLabels(endpoint.Topology, topologyPath)...) if endpoint.Hostname != nil { <del> for _, msg := range validation.IsDNS1123Label(*endpoint.Hostname) { allErrs = append(allErrs, field.Invalid(idxPath.Child(\"hostname\"), *endpoint.Hostname, msg)) } </del> <ins> allErrs = append(allErrs, apivalidation.ValidateDNS1123Label(*endpoint.Hostname, idxPath.Child(\"hostname\"))...) </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-b73bb51cef5016ee2dcd80aae4248808fec811a4dad3a3b7abbba7673a446c48", "text": "What happened: No endpoints created in the EndpointSlice for my service due to the port on the service being too long. Logs show: EndpointSlice created has no endpoint: What you expected to happen: Service that works with Endpoints should work with EndpointSlice. If this is intentional, it should be clearly documented How to reproduce it (as minimally and precisely as possible): Create a service with a long port name Environment: Kubernetes version (use ): 1.16 Cloud provider or hardware configuration: kind\n/sig networking\nThe label(s) cannot be applied. These labels are supported: <detailsIn response to : /sig networking 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\n/sig network These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by vllry. \u200d\nFor a rough measure of impact, Istio had 5 ports that were over this limit (and many more that were right at 15 characters), so I suspect it may not be terribly rare.\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nThis needs to be resolved before endpointslices graduate from alpha\n/assign\n/remove-triage unresolved", "commid": "kubernetes_issue_84388", "tokennum": 292}], "negative_passages": []}
{"query_id": "q-en-kubernetes-480c578a70c385c4a31aa3b2f03cea53c276fbcba22e13088f675d78dfeae4f3", "query": "<ins> /* Copyright 2016 The Kubernetes Authors All rights reserved. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ // Code generated by protoc-gen-gogo. // source: k8s.io/kubernetes/pkg/apis/apps/v1alpha1/generated.proto // DO NOT EDIT! /* Package v1alpha1 is a generated protocol buffer package. It is generated from these files: k8s.io/kubernetes/pkg/apis/apps/v1alpha1/generated.proto It has these top-level messages: PetSet PetSetList PetSetSpec PetSetStatus */ package v1alpha1 import proto \"github.com/gogo/protobuf/proto\" import fmt \"fmt\" import math \"math\" import _ \"github.com/gogo/protobuf/gogoproto\" import _ \"k8s.io/kubernetes/pkg/api/resource\" import k8s_io_kubernetes_pkg_api_unversioned \"k8s.io/kubernetes/pkg/api/unversioned\" import k8s_io_kubernetes_pkg_api_v1 \"k8s.io/kubernetes/pkg/api/v1\" import _ \"k8s.io/kubernetes/pkg/util/intstr\" import io \"io\" // Reference imports to suppress errors if they are not otherwise used. var _ = proto.Marshal var _ = fmt.Errorf var _ = math.Inf func (m *PetSet) Reset()         { *m = PetSet{} } func (m *PetSet) String() string { return proto.CompactTextString(m) } func (*PetSet) ProtoMessage()    {} func (m *PetSetList) Reset()         { *m = PetSetList{} } func (m *PetSetList) String() string { return proto.CompactTextString(m) } func (*PetSetList) ProtoMessage()    {} func (m *PetSetSpec) Reset()         { *m = PetSetSpec{} } func (m *PetSetSpec) String() string { return proto.CompactTextString(m) } func (*PetSetSpec) ProtoMessage()    {} func (m *PetSetStatus) Reset()         { *m = PetSetStatus{} } func (m *PetSetStatus) String() string { return proto.CompactTextString(m) } func (*PetSetStatus) ProtoMessage()    {} func init() { proto.RegisterType((*PetSet)(nil), \"k8s.io.kubernetes.pkg.apis.apps.v1alpha1.PetSet\") proto.RegisterType((*PetSetList)(nil), \"k8s.io.kubernetes.pkg.apis.apps.v1alpha1.PetSetList\") proto.RegisterType((*PetSetSpec)(nil), \"k8s.io.kubernetes.pkg.apis.apps.v1alpha1.PetSetSpec\") proto.RegisterType((*PetSetStatus)(nil), \"k8s.io.kubernetes.pkg.apis.apps.v1alpha1.PetSetStatus\") } func (m *PetSet) Marshal() (data []byte, err error) { size := m.Size() data = make([]byte, size) n, err := m.MarshalTo(data) if err != nil { return nil, err } return data[:n], nil } func (m *PetSet) MarshalTo(data []byte) (int, error) { var i int _ = i var l int _ = l data[i] = 0xa i++ i = encodeVarintGenerated(data, i, uint64(m.ObjectMeta.Size())) n1, err := m.ObjectMeta.MarshalTo(data[i:]) if err != nil { return 0, err } i += n1 data[i] = 0x12 i++ i = encodeVarintGenerated(data, i, uint64(m.Spec.Size())) n2, err := m.Spec.MarshalTo(data[i:]) if err != nil { return 0, err } i += n2 data[i] = 0x1a i++ i = encodeVarintGenerated(data, i, uint64(m.Status.Size())) n3, err := m.Status.MarshalTo(data[i:]) if err != nil { return 0, err } i += n3 return i, nil } func (m *PetSetList) Marshal() (data []byte, err error) { size := m.Size() data = make([]byte, size) n, err := m.MarshalTo(data) if err != nil { return nil, err } return data[:n], nil } func (m *PetSetList) MarshalTo(data []byte) (int, error) { var i int _ = i var l int _ = l data[i] = 0xa i++ i = encodeVarintGenerated(data, i, uint64(m.ListMeta.Size())) n4, err := m.ListMeta.MarshalTo(data[i:]) if err != nil { return 0, err } i += n4 if len(m.Items) > 0 { for _, msg := range m.Items { data[i] = 0x12 i++ i = encodeVarintGenerated(data, i, uint64(msg.Size())) n, err := msg.MarshalTo(data[i:]) if err != nil { return 0, err } i += n } } return i, nil } func (m *PetSetSpec) Marshal() (data []byte, err error) { size := m.Size() data = make([]byte, size) n, err := m.MarshalTo(data) if err != nil { return nil, err } return data[:n], nil } func (m *PetSetSpec) MarshalTo(data []byte) (int, error) { var i int _ = i var l int _ = l if m.Replicas != nil { data[i] = 0x8 i++ i = encodeVarintGenerated(data, i, uint64(*m.Replicas)) } if m.Selector != nil { data[i] = 0x12 i++ i = encodeVarintGenerated(data, i, uint64(m.Selector.Size())) n5, err := m.Selector.MarshalTo(data[i:]) if err != nil { return 0, err } i += n5 } data[i] = 0x1a i++ i = encodeVarintGenerated(data, i, uint64(m.Template.Size())) n6, err := m.Template.MarshalTo(data[i:]) if err != nil { return 0, err } i += n6 if len(m.VolumeClaimTemplates) > 0 { for _, msg := range m.VolumeClaimTemplates { data[i] = 0x22 i++ i = encodeVarintGenerated(data, i, uint64(msg.Size())) n, err := msg.MarshalTo(data[i:]) if err != nil { return 0, err } i += n } } data[i] = 0x2a i++ i = encodeVarintGenerated(data, i, uint64(len(m.ServiceName))) i += copy(data[i:], m.ServiceName) return i, nil } func (m *PetSetStatus) Marshal() (data []byte, err error) { size := m.Size() data = make([]byte, size) n, err := m.MarshalTo(data) if err != nil { return nil, err } return data[:n], nil } func (m *PetSetStatus) MarshalTo(data []byte) (int, error) { var i int _ = i var l int _ = l if m.ObservedGeneration != nil { data[i] = 0x8 i++ i = encodeVarintGenerated(data, i, uint64(*m.ObservedGeneration)) } data[i] = 0x10 i++ i = encodeVarintGenerated(data, i, uint64(m.Replicas)) return i, nil } func encodeFixed64Generated(data []byte, offset int, v uint64) int { data[offset] = uint8(v) data[offset+1] = uint8(v >> 8) data[offset+2] = uint8(v >> 16) data[offset+3] = uint8(v >> 24) data[offset+4] = uint8(v >> 32) data[offset+5] = uint8(v >> 40) data[offset+6] = uint8(v >> 48) data[offset+7] = uint8(v >> 56) return offset + 8 } func encodeFixed32Generated(data []byte, offset int, v uint32) int { data[offset] = uint8(v) data[offset+1] = uint8(v >> 8) data[offset+2] = uint8(v >> 16) data[offset+3] = uint8(v >> 24) return offset + 4 } func encodeVarintGenerated(data []byte, offset int, v uint64) int { for v >= 1<<7 { data[offset] = uint8(v&0x7f | 0x80) v >>= 7 offset++ } data[offset] = uint8(v) return offset + 1 } func (m *PetSet) Size() (n int) { var l int _ = l l = m.ObjectMeta.Size() n += 1 + l + sovGenerated(uint64(l)) l = m.Spec.Size() n += 1 + l + sovGenerated(uint64(l)) l = m.Status.Size() n += 1 + l + sovGenerated(uint64(l)) return n } func (m *PetSetList) Size() (n int) { var l int _ = l l = m.ListMeta.Size() n += 1 + l + sovGenerated(uint64(l)) if len(m.Items) > 0 { for _, e := range m.Items { l = e.Size() n += 1 + l + sovGenerated(uint64(l)) } } return n } func (m *PetSetSpec) Size() (n int) { var l int _ = l if m.Replicas != nil { n += 1 + sovGenerated(uint64(*m.Replicas)) } if m.Selector != nil { l = m.Selector.Size() n += 1 + l + sovGenerated(uint64(l)) } l = m.Template.Size() n += 1 + l + sovGenerated(uint64(l)) if len(m.VolumeClaimTemplates) > 0 { for _, e := range m.VolumeClaimTemplates { l = e.Size() n += 1 + l + sovGenerated(uint64(l)) } } l = len(m.ServiceName) n += 1 + l + sovGenerated(uint64(l)) return n } func (m *PetSetStatus) Size() (n int) { var l int _ = l if m.ObservedGeneration != nil { n += 1 + sovGenerated(uint64(*m.ObservedGeneration)) } n += 1 + sovGenerated(uint64(m.Replicas)) return n } func sovGenerated(x uint64) (n int) { for { n++ x >>= 7 if x == 0 { break } } return n } func sozGenerated(x uint64) (n int) { return sovGenerated(uint64((x << 1) ^ uint64((int64(x) >> 63)))) } func (m *PetSet) Unmarshal(data []byte) error { l := len(data) iNdEx := 0 for iNdEx < l { preIndex := iNdEx var wire uint64 for shift := uint(0); ; shift += 7 { if shift >= 64 { return ErrIntOverflowGenerated } if iNdEx >= l { return io.ErrUnexpectedEOF } b := data[iNdEx] iNdEx++ wire |= (uint64(b) & 0x7F) << shift if b < 0x80 { break } } fieldNum := int32(wire >> 3) wireType := int(wire & 0x7) if wireType == 4 { return fmt.Errorf(\"proto: PetSet: wiretype end group for non-group\") } if fieldNum <= 0 { return fmt.Errorf(\"proto: PetSet: illegal tag %d (wire type %d)\", fieldNum, wire) } switch fieldNum { case 1: if wireType != 2 { return fmt.Errorf(\"proto: wrong wireType = %d for field ObjectMeta\", wireType) } var msglen int for shift := uint(0); ; shift += 7 { if shift >= 64 { return ErrIntOverflowGenerated } if iNdEx >= l { return io.ErrUnexpectedEOF } b := data[iNdEx] iNdEx++ msglen |= (int(b) & 0x7F) << shift if b < 0x80 { break } } if msglen < 0 { return ErrInvalidLengthGenerated } postIndex := iNdEx + msglen if postIndex > l { return io.ErrUnexpectedEOF } if err := m.ObjectMeta.Unmarshal(data[iNdEx:postIndex]); err != nil { return err } iNdEx = postIndex case 2: if wireType != 2 { return fmt.Errorf(\"proto: wrong wireType = %d for field Spec\", wireType) } var msglen int for shift := uint(0); ; shift += 7 { if shift >= 64 { return ErrIntOverflowGenerated } if iNdEx >= l { return io.ErrUnexpectedEOF } b := data[iNdEx] iNdEx++ msglen |= (int(b) & 0x7F) << shift if b < 0x80 { break } } if msglen < 0 { return ErrInvalidLengthGenerated } postIndex := iNdEx + msglen if postIndex > l { return io.ErrUnexpectedEOF } if err := m.Spec.Unmarshal(data[iNdEx:postIndex]); err != nil { return err } iNdEx = postIndex case 3: if wireType != 2 { return fmt.Errorf(\"proto: wrong wireType = %d for field Status\", wireType) } var msglen int for shift := uint(0); ; shift += 7 { if shift >= 64 { return ErrIntOverflowGenerated } if iNdEx >= l { return io.ErrUnexpectedEOF } b := data[iNdEx] iNdEx++ msglen |= (int(b) & 0x7F) << shift if b < 0x80 { break } } if msglen < 0 { return ErrInvalidLengthGenerated } postIndex := iNdEx + msglen if postIndex > l { return io.ErrUnexpectedEOF } if err := m.Status.Unmarshal(data[iNdEx:postIndex]); err != nil { return err } iNdEx = postIndex default: iNdEx = preIndex skippy, err := skipGenerated(data[iNdEx:]) if err != nil { return err } if skippy < 0 { return ErrInvalidLengthGenerated } if (iNdEx + skippy) > l { return io.ErrUnexpectedEOF } iNdEx += skippy } } if iNdEx > l { return io.ErrUnexpectedEOF } return nil } func (m *PetSetList) Unmarshal(data []byte) error { l := len(data) iNdEx := 0 for iNdEx < l { preIndex := iNdEx var wire uint64 for shift := uint(0); ; shift += 7 { if shift >= 64 { return ErrIntOverflowGenerated } if iNdEx >= l { return io.ErrUnexpectedEOF } b := data[iNdEx] iNdEx++ wire |= (uint64(b) & 0x7F) << shift if b < 0x80 { break } } fieldNum := int32(wire >> 3) wireType := int(wire & 0x7) if wireType == 4 { return fmt.Errorf(\"proto: PetSetList: wiretype end group for non-group\") } if fieldNum <= 0 { return fmt.Errorf(\"proto: PetSetList: illegal tag %d (wire type %d)\", fieldNum, wire) } switch fieldNum { case 1: if wireType != 2 { return fmt.Errorf(\"proto: wrong wireType = %d for field ListMeta\", wireType) } var msglen int for shift := uint(0); ; shift += 7 { if shift >= 64 { return ErrIntOverflowGenerated } if iNdEx >= l { return io.ErrUnexpectedEOF } b := data[iNdEx] iNdEx++ msglen |= (int(b) & 0x7F) << shift if b < 0x80 { break } } if msglen < 0 { return ErrInvalidLengthGenerated } postIndex := iNdEx + msglen if postIndex > l { return io.ErrUnexpectedEOF } if err := m.ListMeta.Unmarshal(data[iNdEx:postIndex]); err != nil { return err } iNdEx = postIndex case 2: if wireType != 2 { return fmt.Errorf(\"proto: wrong wireType = %d for field Items\", wireType) } var msglen int for shift := uint(0); ; shift += 7 { if shift >= 64 { return ErrIntOverflowGenerated } if iNdEx >= l { return io.ErrUnexpectedEOF } b := data[iNdEx] iNdEx++ msglen |= (int(b) & 0x7F) << shift if b < 0x80 { break } } if msglen < 0 { return ErrInvalidLengthGenerated } postIndex := iNdEx + msglen if postIndex > l { return io.ErrUnexpectedEOF } m.Items = append(m.Items, PetSet{}) if err := m.Items[len(m.Items)-1].Unmarshal(data[iNdEx:postIndex]); err != nil { return err } iNdEx = postIndex default: iNdEx = preIndex skippy, err := skipGenerated(data[iNdEx:]) if err != nil { return err } if skippy < 0 { return ErrInvalidLengthGenerated } if (iNdEx + skippy) > l { return io.ErrUnexpectedEOF } iNdEx += skippy } } if iNdEx > l { return io.ErrUnexpectedEOF } return nil } func (m *PetSetSpec) Unmarshal(data []byte) error { l := len(data) iNdEx := 0 for iNdEx < l { preIndex := iNdEx var wire uint64 for shift := uint(0); ; shift += 7 { if shift >= 64 { return ErrIntOverflowGenerated } if iNdEx >= l { return io.ErrUnexpectedEOF } b := data[iNdEx] iNdEx++ wire |= (uint64(b) & 0x7F) << shift if b < 0x80 { break } } fieldNum := int32(wire >> 3) wireType := int(wire & 0x7) if wireType == 4 { return fmt.Errorf(\"proto: PetSetSpec: wiretype end group for non-group\") } if fieldNum <= 0 { return fmt.Errorf(\"proto: PetSetSpec: illegal tag %d (wire type %d)\", fieldNum, wire) } switch fieldNum { case 1: if wireType != 0 { return fmt.Errorf(\"proto: wrong wireType = %d for field Replicas\", wireType) } var v int32 for shift := uint(0); ; shift += 7 { if shift >= 64 { return ErrIntOverflowGenerated } if iNdEx >= l { return io.ErrUnexpectedEOF } b := data[iNdEx] iNdEx++ v |= (int32(b) & 0x7F) << shift if b < 0x80 { break } } m.Replicas = &v case 2: if wireType != 2 { return fmt.Errorf(\"proto: wrong wireType = %d for field Selector\", wireType) } var msglen int for shift := uint(0); ; shift += 7 { if shift >= 64 { return ErrIntOverflowGenerated } if iNdEx >= l { return io.ErrUnexpectedEOF } b := data[iNdEx] iNdEx++ msglen |= (int(b) & 0x7F) << shift if b < 0x80 { break } } if msglen < 0 { return ErrInvalidLengthGenerated } postIndex := iNdEx + msglen if postIndex > l { return io.ErrUnexpectedEOF } if m.Selector == nil { m.Selector = &k8s_io_kubernetes_pkg_api_unversioned.LabelSelector{} } if err := m.Selector.Unmarshal(data[iNdEx:postIndex]); err != nil { return err } iNdEx = postIndex case 3: if wireType != 2 { return fmt.Errorf(\"proto: wrong wireType = %d for field Template\", wireType) } var msglen int for shift := uint(0); ; shift += 7 { if shift >= 64 { return ErrIntOverflowGenerated } if iNdEx >= l { return io.ErrUnexpectedEOF } b := data[iNdEx] iNdEx++ msglen |= (int(b) & 0x7F) << shift if b < 0x80 { break } } if msglen < 0 { return ErrInvalidLengthGenerated } postIndex := iNdEx + msglen if postIndex > l { return io.ErrUnexpectedEOF } if err := m.Template.Unmarshal(data[iNdEx:postIndex]); err != nil { return err } iNdEx = postIndex case 4: if wireType != 2 { return fmt.Errorf(\"proto: wrong wireType = %d for field VolumeClaimTemplates\", wireType) } var msglen int for shift := uint(0); ; shift += 7 { if shift >= 64 { return ErrIntOverflowGenerated } if iNdEx >= l { return io.ErrUnexpectedEOF } b := data[iNdEx] iNdEx++ msglen |= (int(b) & 0x7F) << shift if b < 0x80 { break } } if msglen < 0 { return ErrInvalidLengthGenerated } postIndex := iNdEx + msglen if postIndex > l { return io.ErrUnexpectedEOF } m.VolumeClaimTemplates = append(m.VolumeClaimTemplates, k8s_io_kubernetes_pkg_api_v1.PersistentVolumeClaim{}) if err := m.VolumeClaimTemplates[len(m.VolumeClaimTemplates)-1].Unmarshal(data[iNdEx:postIndex]); err != nil { return err } iNdEx = postIndex case 5: if wireType != 2 { return fmt.Errorf(\"proto: wrong wireType = %d for field ServiceName\", wireType) } var stringLen uint64 for shift := uint(0); ; shift += 7 { if shift >= 64 { return ErrIntOverflowGenerated } if iNdEx >= l { return io.ErrUnexpectedEOF } b := data[iNdEx] iNdEx++ stringLen |= (uint64(b) & 0x7F) << shift if b < 0x80 { break } } intStringLen := int(stringLen) if intStringLen < 0 { return ErrInvalidLengthGenerated } postIndex := iNdEx + intStringLen if postIndex > l { return io.ErrUnexpectedEOF } m.ServiceName = string(data[iNdEx:postIndex]) iNdEx = postIndex default: iNdEx = preIndex skippy, err := skipGenerated(data[iNdEx:]) if err != nil { return err } if skippy < 0 { return ErrInvalidLengthGenerated } if (iNdEx + skippy) > l { return io.ErrUnexpectedEOF } iNdEx += skippy } } if iNdEx > l { return io.ErrUnexpectedEOF } return nil } func (m *PetSetStatus) Unmarshal(data []byte) error { l := len(data) iNdEx := 0 for iNdEx < l { preIndex := iNdEx var wire uint64 for shift := uint(0); ; shift += 7 { if shift >= 64 { return ErrIntOverflowGenerated } if iNdEx >= l { return io.ErrUnexpectedEOF } b := data[iNdEx] iNdEx++ wire |= (uint64(b) & 0x7F) << shift if b < 0x80 { break } } fieldNum := int32(wire >> 3) wireType := int(wire & 0x7) if wireType == 4 { return fmt.Errorf(\"proto: PetSetStatus: wiretype end group for non-group\") } if fieldNum <= 0 { return fmt.Errorf(\"proto: PetSetStatus: illegal tag %d (wire type %d)\", fieldNum, wire) } switch fieldNum { case 1: if wireType != 0 { return fmt.Errorf(\"proto: wrong wireType = %d for field ObservedGeneration\", wireType) } var v int64 for shift := uint(0); ; shift += 7 { if shift >= 64 { return ErrIntOverflowGenerated } if iNdEx >= l { return io.ErrUnexpectedEOF } b := data[iNdEx] iNdEx++ v |= (int64(b) & 0x7F) << shift if b < 0x80 { break } } m.ObservedGeneration = &v case 2: if wireType != 0 { return fmt.Errorf(\"proto: wrong wireType = %d for field Replicas\", wireType) } m.Replicas = 0 for shift := uint(0); ; shift += 7 { if shift >= 64 { return ErrIntOverflowGenerated } if iNdEx >= l { return io.ErrUnexpectedEOF } b := data[iNdEx] iNdEx++ m.Replicas |= (int32(b) & 0x7F) << shift if b < 0x80 { break } } default: iNdEx = preIndex skippy, err := skipGenerated(data[iNdEx:]) if err != nil { return err } if skippy < 0 { return ErrInvalidLengthGenerated } if (iNdEx + skippy) > l { return io.ErrUnexpectedEOF } iNdEx += skippy } } if iNdEx > l { return io.ErrUnexpectedEOF } return nil } func skipGenerated(data []byte) (n int, err error) { l := len(data) iNdEx := 0 for iNdEx < l { var wire uint64 for shift := uint(0); ; shift += 7 { if shift >= 64 { return 0, ErrIntOverflowGenerated } if iNdEx >= l { return 0, io.ErrUnexpectedEOF } b := data[iNdEx] iNdEx++ wire |= (uint64(b) & 0x7F) << shift if b < 0x80 { break } } wireType := int(wire & 0x7) switch wireType { case 0: for shift := uint(0); ; shift += 7 { if shift >= 64 { return 0, ErrIntOverflowGenerated } if iNdEx >= l { return 0, io.ErrUnexpectedEOF } iNdEx++ if data[iNdEx-1] < 0x80 { break } } return iNdEx, nil case 1: iNdEx += 8 return iNdEx, nil case 2: var length int for shift := uint(0); ; shift += 7 { if shift >= 64 { return 0, ErrIntOverflowGenerated } if iNdEx >= l { return 0, io.ErrUnexpectedEOF } b := data[iNdEx] iNdEx++ length |= (int(b) & 0x7F) << shift if b < 0x80 { break } } iNdEx += length if length < 0 { return 0, ErrInvalidLengthGenerated } return iNdEx, nil case 3: for { var innerWire uint64 var start int = iNdEx for shift := uint(0); ; shift += 7 { if shift >= 64 { return 0, ErrIntOverflowGenerated } if iNdEx >= l { return 0, io.ErrUnexpectedEOF } b := data[iNdEx] iNdEx++ innerWire |= (uint64(b) & 0x7F) << shift if b < 0x80 { break } } innerWireType := int(innerWire & 0x7) if innerWireType == 4 { break } next, err := skipGenerated(data[start:]) if err != nil { return 0, err } iNdEx = start + next } return iNdEx, nil case 4: return iNdEx, nil case 5: iNdEx += 4 return iNdEx, nil default: return 0, fmt.Errorf(\"proto: illegal wireType %d\", wireType) } } panic(\"unreachable\") } var ( ErrInvalidLengthGenerated = fmt.Errorf(\"proto: negative length found during unmarshaling\") ErrIntOverflowGenerated   = fmt.Errorf(\"proto: integer overflow\") ) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-21b704a68514d2b400f1a4f479b12f48c6dc4bd890b9d4b14cffa5ee4c13d7d4", "text": "During\nany chance this is related to pass: https://k8s- fail: https://k8s- https://k8s-\nThis is because for some reason the submit queue rebuild didn't catch the flake before merging. Protobuf landed first, merging a new api object like petset should have failed.\nQuick fix is to rebuild the proto marshalers and push.\nAlso, hack/verify-generated- is broken, which probably is the root cause.\nLooking at it now\nThree problems: -generated-protobuf wasn't updated when we made update-generated-protobuf use docker, so it didn't fail out script was verifying the old API groups, not any of the new API groups that have been merged without protobuf serializations (although pkg/api/serialization_test should have failed, possibly the job didn't build with the latest master?), which caused the tests to fail\nSomething about the merge bot is broken - it merged without all the tests being green: . That's why this broke -\nSpawned since there is something wrong with update-generated-protobuf - will merge that to fix the failing test and then debug the generator in the morning.\nThe bot can race with pushes between when it starts testing and when it merges...", "commid": "kubernetes_issue_24579", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-481435c46332b5e397cca8a6a5f8a32d80a676ca11f145e355483d3592de146f", "query": "} // inClusterClientConfig makes a config that will work from within a kubernetes cluster container environment. <del> type inClusterClientConfig struct{} </del> <ins> // Can take options overrides for flags explicitly provided to the command inside the cluster container. type inClusterClientConfig struct { overrides               *ConfigOverrides inClusterConfigProvider func() (*restclient.Config, error) } </ins> <del> var _ ClientConfig = inClusterClientConfig{} </del> <ins> var _ ClientConfig = &inClusterClientConfig{} </ins> <del> func (inClusterClientConfig) RawConfig() (clientcmdapi.Config, error) { </del> <ins> func (config *inClusterClientConfig) RawConfig() (clientcmdapi.Config, error) { </ins> return clientcmdapi.Config{}, fmt.Errorf(\"inCluster environment config doesn't support multiple clusters\") } <del> func (inClusterClientConfig) ClientConfig() (*restclient.Config, error) { return restclient.InClusterConfig() </del> <ins> func (config *inClusterClientConfig) ClientConfig() (*restclient.Config, error) { if config.inClusterConfigProvider == nil { config.inClusterConfigProvider = restclient.InClusterConfig } icc, err := config.inClusterConfigProvider() if err != nil { return nil, err } // in-cluster configs only takes a host, token, or CA file // if any of them were individually provided, ovewrite anything else if config.overrides != nil { if server := config.overrides.ClusterInfo.Server; len(server) > 0 { icc.Host = server } if token := config.overrides.AuthInfo.Token; len(token) > 0 { icc.BearerToken = token } if certificateAuthorityFile := config.overrides.ClusterInfo.CertificateAuthority; len(certificateAuthorityFile) > 0 { icc.TLSClientConfig.CAFile = certificateAuthorityFile } } return icc, err </ins> } <del> func (inClusterClientConfig) Namespace() (string, bool, error) { </del> <ins> func (config *inClusterClientConfig) Namespace() (string, bool, error) { </ins> // This way assumes you've set the POD_NAMESPACE environment variable using the downward API. // This check has to be done first for backwards compatibility with the way InClusterConfig was originally set up if ns := os.Getenv(\"POD_NAMESPACE\"); ns != \"\" {", "positive_passages": [{"docid": "doc-en-kubernetes-4e19a56e8ccacbab4546f622baecdb0b8ef30250430c55f8bcdc4de99b100cd2", "text": "Found in openshift, but I'm pretty sure the codepaths are the same. That means the token is getting ignored and in-cluster config is being used in preference to flags.\nIs a similar issue?\nYep, kind of regression.\nSigh.\nYes, most likely the same cause.\nI'm on it.\nUnit test :)\nProbably will want to cherrypick this into 1.5.\nWIP in", "commid": "kubernetes_issue_38834", "tokennum": 89}], "negative_passages": []}
{"query_id": "q-en-kubernetes-481dd13ca4bb817a7f290f4ebe9308ab33df1a922b93c5a3384a239b9382fd14", "query": "\"The same PVC should be used after failover.\") By(\"verifying the container output has 2 lines, indicating the pod has been created twice using the same regional PD.\") <del> pod = getPod(c, ns, regionalPDLabels) </del> logs, err := framework.GetPodLogs(c, ns, pod.Name, \"\") Expect(err).NotTo(HaveOccurred(), \"Error getting logs from pod %s in namespace %s\", pod.Name, ns)", "positive_passages": [{"docid": "doc-en-kubernetes-07b454797aabeff00bf033fc34fa4c22bd06966ba8574ac0fa868459bacbceea", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: What happened: Testgrid: https://k8s-\n/assign\nThe test's assumption about test parameter is wrong. Previously it assumed the group name is the same across all zones, but they are different in regional clusters. Looking into using node taints as the permanent fix, as suggested by the TODO comment in the test.\nHm I think taint based evictions is still an alpha feature.\nOK. I propose the following solution: Get the zone of Schedule the StatefulSet pod to that zone using node affinity; wait for the pod to run Remove the node affinity from StatefulSet Delete\nCan it be simplified? Schedule the pod Figure out which zone that pod got scheduled in Delete the instance group of that zone\nUnfortunately I don't know of a good way to look up the instance group given the zone, since there could be instance groups from multiple clusters in the same project\nHow about: Schedule the pod Figure out the zone Taint all the nodes in the zone Kill the pod\nTaint with NoSchedule? yeah that sounds good", "commid": "kubernetes_issue_69005", "tokennum": 267}], "negative_passages": []}
{"query_id": "q-en-kubernetes-48325ec8ae577dc508542ea0245f810885ec945d7172bd12a2cc78ebdd05489d", "query": "package plugin import ( <ins> \"context\" \"fmt\" \"net\" \"os\" \"path/filepath\" \"sync\" </ins> \"testing\" \"github.com/stretchr/testify/assert\" <del> v1 \"k8s.io/api/core/v1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" </del> <ins> \"google.golang.org/grpc\" drapb \"k8s.io/kubelet/pkg/apis/dra/v1alpha4\" \"k8s.io/kubernetes/test/utils/ktesting\" </ins> ) <del> func getFakeNode() (*v1.Node, error) { return &v1.Node{ObjectMeta: metav1.ObjectMeta{Name: \"worker\"}}, nil </del> <ins> const ( v1alpha4Version = \"v1alpha4\" ) type fakeV1alpha4GRPCServer struct { drapb.UnimplementedNodeServer } var _ drapb.NodeServer = &fakeV1alpha4GRPCServer{} func (f *fakeV1alpha4GRPCServer) NodePrepareResources(ctx context.Context, in *drapb.NodePrepareResourcesRequest) (*drapb.NodePrepareResourcesResponse, error) { return &drapb.NodePrepareResourcesResponse{Claims: map[string]*drapb.NodePrepareResourceResponse{\"claim-uid\": { Devices: []*drapb.Device{ { RequestNames: []string{\"test-request\"}, CDIDeviceIDs: []string{\"test-cdi-id\"}, }, }, }}}, nil } func (f *fakeV1alpha4GRPCServer) NodeUnprepareResources(ctx context.Context, in *drapb.NodeUnprepareResourcesRequest) (*drapb.NodeUnprepareResourcesResponse, error) { return &drapb.NodeUnprepareResourcesResponse{}, nil } type tearDown func() func setupFakeGRPCServer(version string) (string, tearDown, error) { p, err := os.MkdirTemp(\"\", \"dra_plugin\") if err != nil { return \"\", nil, err } closeCh := make(chan struct{}) addr := filepath.Join(p, \"server.sock\") teardown := func() { close(closeCh) if err := os.RemoveAll(addr); err != nil { panic(err) } } listener, err := net.Listen(\"unix\", addr) if err != nil { teardown() return \"\", nil, err } s := grpc.NewServer() switch version { case v1alpha4Version: fakeGRPCServer := &fakeV1alpha4GRPCServer{} drapb.RegisterNodeServer(s, fakeGRPCServer) default: return \"\", nil, fmt.Errorf(\"unsupported version: %s\", version) } go func() { go func() { if err := s.Serve(listener); err != nil { panic(err) } }() <-closeCh s.GracefulStop() }() return addr, teardown, nil </ins> } <del> func TestRegistrationHandler_ValidatePlugin(t *testing.T) { newRegistrationHandler := func() *RegistrationHandler { return NewRegistrationHandler(nil, getFakeNode) </del> <ins> func TestGRPCConnIsReused(t *testing.T) { tCtx := ktesting.Init(t) addr, teardown, err := setupFakeGRPCServer(v1alpha4Version) if err != nil { t.Fatal(err) } defer teardown() reusedConns := make(map[*grpc.ClientConn]int) wg := sync.WaitGroup{} m := sync.Mutex{} p := &Plugin{ backgroundCtx:     tCtx, endpoint:          addr, clientCallTimeout: defaultClientCallTimeout, </ins> } <ins> conn, err := p.getOrCreateGRPCConn() defer func() { err := conn.Close() if err != nil { t.Error(err) } }() if err != nil { t.Fatal(err) } // ensure the plugin we are using is registered draPlugins.add(\"dummy-plugin\", p) defer draPlugins.delete(\"dummy-plugin\") // we call `NodePrepareResource` 2 times and check whether a new connection is created or the same is reused for i := 0; i < 2; i++ { wg.Add(1) go func() { defer wg.Done() client, err := NewDRAPluginClient(\"dummy-plugin\") if err != nil { t.Error(err) return } req := &drapb.NodePrepareResourcesRequest{ Claims: []*drapb.Claim{ { Namespace: \"dummy-namespace\", UID:       \"dummy-uid\", Name:      \"dummy-claim\", }, }, } _, err = client.NodePrepareResources(tCtx, req) assert.NoError(t, err) client.mutex.Lock() conn := client.conn client.mutex.Unlock() m.Lock() defer m.Unlock() reusedConns[conn]++ }() } wg.Wait() // We should have only one entry otherwise it means another gRPC connection has been created if len(reusedConns) != 1 { t.Errorf(\"expected length to be 1 but got %d\", len(reusedConns)) } if counter, ok := reusedConns[conn]; ok && counter != 2 { t.Errorf(\"expected counter to be 2 but got %d\", counter) } } func TestNewDRAPluginClient(t *testing.T) { </ins> for _, test := range []struct { description string <del> handler     func() *RegistrationHandler </del> <ins> setup       func(string) tearDown </ins> pluginName  string <del> endpoint    string versions    []string </del> shouldError bool }{ { <del> description: \"no versions provided\", handler:     newRegistrationHandler, </del> <ins> description: \"plugin name is empty\", setup: func(_ string) tearDown { return func() {} }, pluginName:  \"\", </ins> shouldError: true, }, { <del> description: \"unsupported version\", handler:     newRegistrationHandler, versions:    []string{\"v2.0.0\"}, </del> <ins> description: \"plugin name not found in the list\", setup: func(_ string) tearDown { return func() {} }, pluginName:  \"plugin-name-not-found-in-the-list\", </ins> shouldError: true, }, { <del> description: \"plugin already registered with a higher supported version\", handler: func() *RegistrationHandler { handler := newRegistrationHandler() if err := handler.RegisterPlugin(\"this-plugin-already-exists-and-has-a-long-name-so-it-doesnt-collide\", \"\", []string{\"v1.1.0\"}, nil); err != nil { t.Fatal(err) </del> <ins> description: \"plugin exists\", setup: func(name string) tearDown { draPlugins.add(name, &Plugin{}) return func() { draPlugins.delete(name) </ins> } <del> return handler </del> }, <del> pluginName:  \"this-plugin-already-exists-and-has-a-long-name-so-it-doesnt-collide\", versions:    []string{\"v1.0.0\"}, shouldError: true, }, { description: \"should validate the plugin\", handler:     newRegistrationHandler, pluginName:  \"this-is-a-dummy-plugin-with-a-long-name-so-it-doesnt-collide\", versions:    []string{\"v1.3.0\"}, </del> <ins> pluginName: \"dummy-plugin\", </ins> }, } { t.Run(test.description, func(t *testing.T) { <del> handler := test.handler() err := handler.ValidatePlugin(test.pluginName, test.endpoint, test.versions) </del> <ins> teardown := test.setup(test.pluginName) defer teardown() client, err := NewDRAPluginClient(test.pluginName) </ins> if test.shouldError { <ins> assert.Nil(t, client) </ins> assert.Error(t, err) } else { <ins> assert.NotNil(t, client) </ins> assert.Nil(t, err) } }) } <ins> } </ins> <del> t.Cleanup(func() { handler := newRegistrationHandler() handler.DeRegisterPlugin(\"this-plugin-already-exists-and-has-a-long-name-so-it-doesnt-collide\") handler.DeRegisterPlugin(\"this-is-a-dummy-plugin-with-a-long-name-so-it-doesnt-collide\") }) </del> <ins> func TestNodeUnprepareResources(t *testing.T) { for _, test := range []struct { description   string serverSetup   func(string) (string, tearDown, error) serverVersion string request       *drapb.NodeUnprepareResourcesRequest }{ { description:   \"server supports v1alpha4\", serverSetup:   setupFakeGRPCServer, serverVersion: v1alpha4Version, request:       &drapb.NodeUnprepareResourcesRequest{}, }, } { t.Run(test.description, func(t *testing.T) { tCtx := ktesting.Init(t) addr, teardown, err := setupFakeGRPCServer(test.serverVersion) if err != nil { t.Fatal(err) } defer teardown() p := &Plugin{ backgroundCtx:     tCtx, endpoint:          addr, clientCallTimeout: defaultClientCallTimeout, } conn, err := p.getOrCreateGRPCConn() defer func() { err := conn.Close() if err != nil { t.Error(err) } }() if err != nil { t.Fatal(err) } draPlugins.add(\"dummy-plugin\", p) defer draPlugins.delete(\"dummy-plugin\") client, err := NewDRAPluginClient(\"dummy-plugin\") if err != nil { t.Fatal(err) } _, err = client.NodeUnprepareResources(tCtx, test.request) if err != nil { t.Fatal(err) } }) } </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-e1c6f7407b346df6fb6212f23a2f930e04198e198bb03b9cff5041967802082d", "text": "The PR above moved everything related to into because that was where most of the code already was, but didn't renamed the files to avoid a larger diff and merge conflicts. Once is merged, we can do the renaming. Code clarity. /sig node\n/triage accepted /priority important-soon\n/assign\na PR can be created for this now.\nwill do", "commid": "kubernetes_issue_125924", "tokennum": 75}], "negative_passages": []}
{"query_id": "q-en-kubernetes-486babcaf81b450d59cc38b2c4da21387eeeb0112c1aee4c999e5ed564dbf14f", "query": "} } <del> func TestNominatedNodeCleanUpUponNodeDeletion(t *testing.T) { // Initialize scheduler. testCtx := initTest(t, \"preemption\") defer testutils.CleanupTest(t, testCtx) cs := testCtx.ClientSet defer cleanupPodsInNamespace(cs, t, testCtx.NS.Name) // Create a node with some resources and a label. nodeRes := &v1.ResourceList{ v1.ResourcePods:   *resource.NewQuantity(32, resource.DecimalSI), v1.ResourceCPU:    *resource.NewMilliQuantity(100, resource.DecimalSI), v1.ResourceMemory: *resource.NewQuantity(100, resource.DecimalSI), } nodeNames := []string{\"node1\", \"node2\"} for _, nodeName := range nodeNames { _, err := createNode(testCtx.ClientSet, nodeName, nodeRes) if err != nil { t.Fatalf(\"Error creating nodes: %v\", err) } } // Fill the cluster with one high-priority and one low-priority Pod. highPriPod, err := createPausePod(cs, mkPriorityPodWithGrace(testCtx, \"high-pod\", highPriority, 60)) if err != nil { t.Fatalf(\"Error creating high-priority pod: %v\", err) } // Make sure the pod is scheduled. if err := testutils.WaitForPodToSchedule(cs, highPriPod); err != nil { t.Fatalf(\"Pod %v/%v didn't get scheduled: %v\", highPriPod.Namespace, highPriPod.Name, err) } lowPriPod, err := createPausePod(cs, mkPriorityPodWithGrace(testCtx, \"low-pod\", lowPriority, 60)) if err != nil { t.Fatalf(\"Error creating low-priority pod: %v\", err) } // Make sure the pod is scheduled. if err := testutils.WaitForPodToSchedule(cs, lowPriPod); err != nil { t.Fatalf(\"Pod %v/%v didn't get scheduled: %v\", lowPriPod.Namespace, lowPriPod.Name, err) } // Create a medium-priority Pod. medPriPod, err := createPausePod(cs, mkPriorityPodWithGrace(testCtx, \"med-pod\", mediumPriority, 60)) if err != nil { t.Fatalf(\"Error creating med-priority pod: %v\", err) } // Check its nominatedNodeName field is set properly. if err := waitForNominatedNodeName(cs, medPriPod); err != nil { t.Fatalf(\"NominatedNodeName was not set for pod %v/%v: %v\", medPriPod.Namespace, medPriPod.Name, err) } // Get the live version of low and med pods. lowPriPod, _ = getPod(cs, lowPriPod.Name, lowPriPod.Namespace) medPriPod, _ = getPod(cs, medPriPod.Name, medPriPod.Namespace) want, got := lowPriPod.Spec.NodeName, medPriPod.Status.NominatedNodeName if want != got { t.Fatalf(\"Expect med-priority's nominatedNodeName to be %v, but got %v.\", want, got) } // Delete the node where med-priority pod is nominated to. cs.CoreV1().Nodes().Delete(context.TODO(), got, metav1.DeleteOptions{}) if err := wait.Poll(200*time.Millisecond, wait.ForeverTestTimeout, func() (bool, error) { _, err := cs.CoreV1().Nodes().Get(context.TODO(), got, metav1.GetOptions{}) if apierrors.IsNotFound(err) { return true, nil } return false, err }); err != nil { t.Fatalf(\"Node %v cannot be deleted: %v.\", got, err) } // Finally verify if med-priority pod's nominatedNodeName gets cleared. if err := wait.Poll(200*time.Millisecond, wait.ForeverTestTimeout, func() (bool, error) { pod, err := cs.CoreV1().Pods(medPriPod.Namespace).Get(context.TODO(), medPriPod.Name, metav1.GetOptions{}) if err != nil { t.Errorf(\"Error getting the medium priority pod info: %v\", err) } if len(pod.Status.NominatedNodeName) == 0 { return true, nil } return false, err }); err != nil { t.Errorf(\"The nominated node name of the medium priority pod was not cleared: %v\", err) } } </del> func mkMinAvailablePDB(name, namespace string, uid types.UID, minAvailable int, matchLabels map[string]string) *policy.PodDisruptionBudget { intMinAvailable := intstr.FromInt(minAvailable) return &policy.PodDisruptionBudget{", "positive_passages": [{"docid": "doc-en-kubernetes-0c3eca7956c73a24f455c71a58b712ce183e874d4a3e3eb9b913120c8a8ac10c", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: Conformance - GCE - master (ci-kubernetes-gce-conformance-latest) Which test(s) are failing: [sig-scheduling] SchedulerPreemption [Serial] PreemptionExecutionPath runs ReplicaSets to verify preemption running path [Conformance]Changes Since when has it been failing: 2020-06-08 22:27 PDT Testgrid link: Reason for failure: Regression by Anything else we need to know: /sig scheduling /priority critical-urgent\ncc/ /assign", "commid": "kubernetes_issue_91972", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-487bc7d30e8f8baa5234339c32a9bf770f8822ae94317766a41cb7c5739e9831", "query": "// +optional optional string imagePullPolicy = 14; <del> // Security options the pod should run with. </del> <ins> // SecurityContext defines the security options the container should be run with. // If set, the fields of SecurityContext override the equivalent fields of PodSecurityContext. </ins> // More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ // +optional optional SecurityContext securityContext = 15;", "positive_passages": [{"docid": "doc-en-kubernetes-2eefef1a83ddd783604f0989f7bcbb86ee11f3e15f09ced1fa06f0ad1ee322e6", "text": "What happened: states that Container.SecurityContext applies to a Pod, which can be misleading since we already have PodSecurityContext. What you expected to happen: Documentation states that it applies to container How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment:\n/sig api-machinery /kind documentation\n/cc\nIssues 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\nNot stale.\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten\nIssues 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\n/remove-lifecycle rotten\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nClosing 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", "commid": "kubernetes_issue_90634", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-48a353894265358f5dd25b1305911e3a8800bf102bd9b690eae3ba9dd32ad7e6", "query": "} if (opts.Watch || forceWatch) && rw != nil { <ins> glog.Infof(\"Started to log from %v for %v\", ctx, req.Request.URL.RequestURI()) </ins> watcher, err := rw.Watch(ctx, &opts) if err != nil { scope.err(err, res.ResponseWriter, req.Request)", "positive_passages": [{"docid": "doc-en-kubernetes-cc8f7dd240ce03e902a3a6988aef93cbe00593e0f5081bd8380b06a0a728c5de", "text": "Currently watches only log when they complete, which can make analyzing kube-apiserver log files a bit tricky. (did component x never start watching after that list or did apiserver shut down?)", "commid": "kubernetes_issue_16899", "tokennum": 43}], "negative_passages": []}
{"query_id": "q-en-kubernetes-48b410a4d56ebd58e8754fa9f9f8ad3641b19643d9e079afa47f89446f70f057", "query": "trap cleanup EXIT <del> while true; do read x; done </del> <ins> while true; do sleep 1; done </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-f20fc01164fcc89f452d8525b342f756ca92b86e0d081c91856f4194b395bf42", "text": "on the end of script there is a line: It produces high CPU load when it is run without tty. However it can be replaced with something like this:\nLooks like this has been fixed.", "commid": "kubernetes_issue_3101", "tokennum": 40}], "negative_passages": []}
{"query_id": "q-en-kubernetes-48ff853ff38139a948e4ce6bd92a1d9a92d2e96177bef66efecf123b143a29f5", "query": "in.Spec.InitContainers = values // Call defaulters explicitly until annotations are removed <del> for i := range in.Spec.InitContainers { c := &in.Spec.InitContainers[i] SetDefaults_Container(c) </del> <ins> tmpPodTemp := &PodTemplate{ Template: PodTemplateSpec{ Spec: PodSpec{ HostNetwork:    in.Spec.HostNetwork, InitContainers: values, }, }, </ins> } <ins> SetObjectDefaults_PodTemplate(tmpPodTemp) in.Spec.InitContainers = tmpPodTemp.Template.Spec.InitContainers </ins> } if err := autoConvert_v1_PodTemplateSpec_To_api_PodTemplateSpec(in, out, s); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-c7797df648733fdf9e156246e323d8c03549ac9a3ca2ad30e283629a87abe7ee", "text": "What happened: kubelet doesn't seem to be able to manage containers started with CRI-O any more I'm testing kubelet + CRI-O on an Ubuntu 18.04 server installation, inside a qemu/kvm VM managed by Vagrant (see ), in order to be able to test k8s + KubeVirt + KataContainers, which are all compatible with CRI-O kubelet will obsess on starting new containers, which looks like and endless process, and the cluster never gets ready. For instance here are some syslogs : What you expected to happen: It used to work (see asciinema recording at ) a few days ago, but I fear some recent changes broke it. How to reproduce it (as minimally and precisely as possible): Testing with vagrant up --provider=libvirt on Linux with a clone of that commit: vagrant ssh into the VM and ps -edf f or tail -f /var/log/syslog would do... Anything else we need to know?: Environment: Kubernetes version (use ):Cloud provider or hardware configuration: qemu/kvm VM +OS (e.g: ): Ubuntu 18.04.2 LTS Kernel (e.g. ): Linux kubernetes-vagrant-01 4.15.0-48-generic -Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x8664 x8664 x8664 GNU/Linux Install tools: kubeadm as in Network plugin and version (if this is a network-related bug): Others:\n/sig node\nI can confirm this. If I start cri-o from a systemd service it fails with the above mentioned error message. Starting crio with without systemd works just fine. systemd file:\nThanks for your detailed report :) Just want to do some quick version confirming - you've been using k8s 1.14.1 both when it did and did not work? Any other version changes?\nNot sure for before, when it used to work, but according to the asciinema recording mentioned above (), it seems the same. However, not sure for CRI-O, underlying OS stuff (systemd, kernel, etc.). Sorry.\nI was looking for some information for days. I have exactly the same issue when I use podman + systemd on 18.04.2.", "commid": "kubernetes_issue_77615", "tokennum": 541}], "negative_passages": []}
{"query_id": "q-en-kubernetes-48ff853ff38139a948e4ce6bd92a1d9a92d2e96177bef66efecf123b143a29f5", "query": "in.Spec.InitContainers = values // Call defaulters explicitly until annotations are removed <del> for i := range in.Spec.InitContainers { c := &in.Spec.InitContainers[i] SetDefaults_Container(c) </del> <ins> tmpPodTemp := &PodTemplate{ Template: PodTemplateSpec{ Spec: PodSpec{ HostNetwork:    in.Spec.HostNetwork, InitContainers: values, }, }, </ins> } <ins> SetObjectDefaults_PodTemplate(tmpPodTemp) in.Spec.InitContainers = tmpPodTemp.Template.Spec.InitContainers </ins> } if err := autoConvert_v1_PodTemplateSpec_To_api_PodTemplateSpec(in, out, s); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-dca27e474f7f12153e878b1f27ed663eb17fd42e2832a567b0d652b26f30c566", "text": "It is the same for both 14.15 and 14.18 kernels. Podman without systemd runs fine. Podman with systemd fails at runc with the same error podman[]: open /dev/stderr: no such device or address podman[]: NAME: runc - Open Container Initiative runtime podman[]: runc is a command line client for running applications packaged according to ... podman[]: time=\"2019-05-11T13:04:59-07:00\" level=error msg=\"open /dev/stderr: no such device or addressn\" podman[]: open /dev/stderr: no such device or address\nI've tried to reproduce it on 18.04.2 using Podman from but I am not able to reproduce it. Do you have any reproducer? How did you install Podman?\nI used ceph unit files to run ceph in podman rather than docker. Systemd unit successfully starts docker but fails with podman. I can successfully run the same podman container run command from the command line. How were you trying to replicate this? Can you post your unit file?\nHi, I'am having the same problem with Kubernetes with CRI-O. After joining a second worker node it fails to start flannel. gives the following error: What I've tried: Installing previous version of Kubernetes (from to ) Installing previous version of crio (from to ) Building runc myself from their github page and selecting this in the Running it on Ubunut 18.04.2 Issue: (the one giuseppe linked)\nI wonder if the issue is with systemd and runc. In both cases, crio and podman, I see runc help output which tells me that something is not being passed to runc that it needs.\nI've only used so it is different than your test and you confirmed it works from the CLI for you as well. Could you share your service file so I test it?\nI've tried systemd and cgroupfs but no luck so far.\nso it seems that runc fails to re-open . That seems like a runc issue, as it doesn't really need to reopen it. To fix the failure, you could use something like:\nJust an example.", "commid": "kubernetes_issue_77615", "tokennum": 504}], "negative_passages": []}
{"query_id": "q-en-kubernetes-48ff853ff38139a948e4ce6bd92a1d9a92d2e96177bef66efecf123b143a29f5", "query": "in.Spec.InitContainers = values // Call defaulters explicitly until annotations are removed <del> for i := range in.Spec.InitContainers { c := &in.Spec.InitContainers[i] SetDefaults_Container(c) </del> <ins> tmpPodTemp := &PodTemplate{ Template: PodTemplateSpec{ Spec: PodSpec{ HostNetwork:    in.Spec.HostNetwork, InitContainers: values, }, }, </ins> } <ins> SetObjectDefaults_PodTemplate(tmpPodTemp) in.Spec.InitContainers = tmpPodTemp.Template.Spec.InitContainers </ins> } if err := autoConvert_v1_PodTemplateSpec_To_api_PodTemplateSpec(in, out, s); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-1a33d9e403b3728be8b8de7e79372d00143f16de361084780a7a026e224a4dd2", "text": "I use ceph-ansible to install cluster so it may need to install additional daemons like mon before running mgr but the error, in this case, should be different, [Unit] Description=Ceph Manager [Service] EnvironmentFile=-/etc/environment ExecStartPre=-/usr/bin/podman stop ceph-mgr-storage2n1-la ExecStartPre=-/usr/bin/podman rm ceph-mgr-storage2n1-la ExecStart=/usr/bin/podman run --rm --net=host  --memory=16G  --cpus=4  -v /var/lib/ceph:/var/lib/ceph:z  -v /etc/ceph:/etc/ceph:z  -v /var/run/ceph:/var/run/ceph:z  -v /etc/localtime:/etc/localtime:ro  -e CLUSTER=ceph  -e CEPHDAEMON=MGR  -e CONTAINERIMAGE=  {{ cephmgrdockerextraenv }}  --name=ceph-mgr-storage2n1-la  ExecStopPost=-/usr/bin/podman stop ceph-mgr-storage2n1-la Restart=always RestartSec=10s TimeoutStartSec=120 TimeoutStopSec=15 [Install] WantedBy=multi- delighted <:\nBTW, I projectatomic ppa and used apt-get -y podman to install. My podman version is 1.3.0 Sasha Litvak \u2014 You are receiving this because you commented. Reply to this email directly, view it on GitHub , or mute the thread\nCorrected file.", "commid": "kubernetes_issue_77615", "tokennum": 404}], "negative_passages": []}
{"query_id": "q-en-kubernetes-48ff853ff38139a948e4ce6bd92a1d9a92d2e96177bef66efecf123b143a29f5", "query": "in.Spec.InitContainers = values // Call defaulters explicitly until annotations are removed <del> for i := range in.Spec.InitContainers { c := &in.Spec.InitContainers[i] SetDefaults_Container(c) </del> <ins> tmpPodTemp := &PodTemplate{ Template: PodTemplateSpec{ Spec: PodSpec{ HostNetwork:    in.Spec.HostNetwork, InitContainers: values, }, }, </ins> } <ins> SetObjectDefaults_PodTemplate(tmpPodTemp) in.Spec.InitContainers = tmpPodTemp.Template.Spec.InitContainers </ins> } if err := autoConvert_v1_PodTemplateSpec_To_api_PodTemplateSpec(in, out, s); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-bae004f13a06f51a77aaeb8de64c7434d457cced5ee158b56a68659aa46bb958", "text": "[Unit] Description=Ceph Manager [Service] EnvironmentFile=-/etc/environment ExecStartPre=-/usr/bin/podman stop ceph-mgr-storage2n1-la ExecStartPre=-/usr/bin/podman rm ceph-mgr-storage2n1-la ExecStart=/usr/bin/podman run --rm --net=host  --memory=16G  --cpus=4  -v /var/lib/ceph:/var/lib/ceph:z  -v /etc/ceph:/etc/ceph:z  -v /var/run/ceph:/var/run/ceph:z  -v /etc/localtime:/etc/localtime:ro  -e CLUSTER=ceph  -e CEPHDAEMON=MGR  -e CONTAINERIMAGE=  --name=ceph-mgr-storage2n1-la  ExecStopPost=-/usr/bin/podman stop ceph-mgr-storage2n1-la Restart=always RestartSec=10s TimeoutStartSec=120 TimeoutStopSec=15 [Install] WantedBy=multi- Giuseppe Scrivano <:\nWould it have an effect system wide? Can I add it to a unit file or unit override instead? Giuseppe Scrivano <:\nyes, I think it is better to add it only to the unit file\nWhy would runc work outside of systemd? And if it needs stderr, giving it Null in settings will redirect stderr to Null I presume? On Tue, May 14, 2019, 9:46 AM Giuseppe Scrivano <:\nRunning into same issues on Ubuntu 18.04.2 using cri-o-1.13 via PPA.\nPR here: opencontainers/runc\nUntil it is avaialble with project atomic and such, can I use a null workaround? Giuseppe Scrivano <:\nyes, but you will lose anything written to stderr. You could probably also use a file, like\nWhat about actually mounting dev and using /dev/stderr ? On Tue, May 14, 2019, 3:11 PM Giuseppe Scrivano <:\nis a symlink to . It is present, the issue here is that is a socket. The fix for runc got merged, could you use an updated runc?\nI tried apt update/upgrade and restarting crio, but I'm still getting the issue.", "commid": "kubernetes_issue_77615", "tokennum": 570}], "negative_passages": []}
{"query_id": "q-en-kubernetes-48ff853ff38139a948e4ce6bd92a1d9a92d2e96177bef66efecf123b143a29f5", "query": "in.Spec.InitContainers = values // Call defaulters explicitly until annotations are removed <del> for i := range in.Spec.InitContainers { c := &in.Spec.InitContainers[i] SetDefaults_Container(c) </del> <ins> tmpPodTemp := &PodTemplate{ Template: PodTemplateSpec{ Spec: PodSpec{ HostNetwork:    in.Spec.HostNetwork, InitContainers: values, }, }, </ins> } <ins> SetObjectDefaults_PodTemplate(tmpPodTemp) in.Spec.InitContainers = tmpPodTemp.Template.Spec.InitContainers </ins> } if err := autoConvert_v1_PodTemplateSpec_To_api_PodTemplateSpec(in, out, s); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-a9af1b8339c2af3d5a8899da2b8916e4bc8194e1229dc4a9dc77c862af07f4a9", "text": "Could it be that crio's runc is not updated yet? Edit Build new runc from and it is working now. Think crio hasn't updated it yet with their repository.\nI'm running this version from PPA repo for ubuntu and it fails: could you point to version/commit or whatever helps identify the fixed version/snapshot ? Thanks in advance.\nat the moment it is only fixed upstream. You'd need to build runc manually\nIs there a version of the package on ppa we can downgrade to? On Wed, May 15, 2019, 4:35 AM Giuseppe Scrivano <:\ncould we update the runc version in the PPA repo?\nThank you. I seem them built but nut pushed to ppa yet.\nshould be available now.. let me know..\ncri-o-runc (1.0.0-rc6-1~dev~ubuntu18.04~ppa42) bionic; urgency=medium autobuilt -- Lokesh Mandvekar (Bot) <, 15 May 2019 16:54:40 +0000\nThank you, everyone, for a quick turn around. Quick testing showed that fix is working, but more testing is needed. Lokesh Mandvekar <:\nI confirm my initial tests with seem to confirm the regression is fixed. Many thanks\nI also confirm the fix working for podman. Olivier Berger <:", "commid": "kubernetes_issue_77615", "tokennum": 305}], "negative_passages": []}
{"query_id": "q-en-kubernetes-48ff853ff38139a948e4ce6bd92a1d9a92d2e96177bef66efecf123b143a29f5", "query": "in.Spec.InitContainers = values // Call defaulters explicitly until annotations are removed <del> for i := range in.Spec.InitContainers { c := &in.Spec.InitContainers[i] SetDefaults_Container(c) </del> <ins> tmpPodTemp := &PodTemplate{ Template: PodTemplateSpec{ Spec: PodSpec{ HostNetwork:    in.Spec.HostNetwork, InitContainers: values, }, }, </ins> } <ins> SetObjectDefaults_PodTemplate(tmpPodTemp) in.Spec.InitContainers = tmpPodTemp.Template.Spec.InitContainers </ins> } if err := autoConvert_v1_PodTemplateSpec_To_api_PodTemplateSpec(in, out, s); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-c1c167f97d0d68a2d507d0d919d58cd680ff8ed576e3225c7b24d703a964bd61", "text": "<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.--Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see ): No What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): initContainers imagePullPolicy initContainers required value Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT <!-- If this is a BUG REPORT, please: Fill in as much of the template below as you can. If you leave out information, we can't help you as well. If this is a FEATURE REQUEST, please: Describe in detail the feature/behavior/change you'd like to see. In both cases, be ready for followup questions, and please respond in a timely manner. If we can't reproduce a bug or think a feature already exists, we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why. --Kubernetes version (use ): Environment: Cloud provider or hardware configuration: GCE OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: cluster/kube- Others: What happened: When trying to create either a ReplicaSet or Replication Controller whose Pod template contains an Init Container, the validation fails saying is a required value. What you expected to happen: The create should succeed and the Init Container should receive a default . How to reproduce it (as minimally and precisely as possible): Try to create either of the following: ReplicaSet Replication Controller Anything else do we need to know: If I add to the Init Container in the ReplicaSet or Replication Controller Pod template, the create succeeds. When I create an Init Container without in a StatefulSet Pod template, it succeeds. When I create an Init Container without in a bare Pod, it succeeds:\nLooks like defaulting not being applied on server? That is probably due to removing defaulting from convert. Surprised we didn't catch this earlier\nSome values still not being defaulted\n, I'm going to create a PR if none works on it.\nWe decode from bytes, set defaults and then convert; but for init containers, we delay the decode from \"decode phase\" to \"convert phase\" at .", "commid": "kubernetes_issue_38542", "tokennum": 524}], "negative_passages": []}
{"query_id": "q-en-kubernetes-48ff853ff38139a948e4ce6bd92a1d9a92d2e96177bef66efecf123b143a29f5", "query": "in.Spec.InitContainers = values // Call defaulters explicitly until annotations are removed <del> for i := range in.Spec.InitContainers { c := &in.Spec.InitContainers[i] SetDefaults_Container(c) </del> <ins> tmpPodTemp := &PodTemplate{ Template: PodTemplateSpec{ Spec: PodSpec{ HostNetwork:    in.Spec.HostNetwork, InitContainers: values, }, }, </ins> } <ins> SetObjectDefaults_PodTemplate(tmpPodTemp) in.Spec.InitContainers = tmpPodTemp.Template.Spec.InitContainers </ins> } if err := autoConvert_v1_PodTemplateSpec_To_api_PodTemplateSpec(in, out, s); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-69dbac4fd7f4ee2d4feb0af6994cc2f74e65b4d3465b8e0c7014cfb5909cea9b", "text": "The defaults has been handled for initContainer at . /cc I'm working to find a solution for that; if any suggestion, please let me know.\nWould this bug affect the deletion of jobs with an init-container? I ran into this bug and adjusted my manifest to add the pull policy to the init-container. However, I now cannot delete said job claiming a field is immutable. Example:\n, not sure now. Let me check it,\nSame error here with version 1.5.1, 1.5.2 The Job \"grafana-import-dashboards\" is invalid: [0].imagePullPolicy: Required value With this setup: kubectl apply -f monitoring Not working even if I specify a pullpolicy in the yaml. If I roll back to 1.4.7, it is working. Thank you. Greg.\nany updates on a PR to address this issue? Is anyone from able to pick this issue up otherwise?\n, here's the latest status: there's is a PR to generate for each Object (), it works for Object (Pod, Job) now but List; I'm working to make it generating for List.\nWhy would you need List to work? No client side logic should be decoding lists except as a generic submission.\nThe List tests are failed in . There's no for List, so no code to decode init-container annotation, e.g. of should call 's recursively.\nThanks for the update\n+1\nAny update on this? I still getting this issue with the last version of 1.5.3 on GKE?\nping for the comments? should we merge the PR for 1.5?\n, there's a PR () that handled that issue; but we're discussing not to merge it because initContainers had been moved to fields, and fields is the recommended way to use since 1.6. But I'd like to get & 's comments on 1.5.\nThis is still an issue in 1.5.3 when using annotations: Without the deployment would not be accepted\nping & :).\ni dont think this is fixed in 1.5 I just encountered this bug on 1.5.3\n, yes, the PR is NOT merged to any branch, so the issue is still here. I'll create a PR for 1.5.\nHi Anyone help this issue.", "commid": "kubernetes_issue_38542", "tokennum": 520}], "negative_passages": []}
{"query_id": "q-en-kubernetes-48ff853ff38139a948e4ce6bd92a1d9a92d2e96177bef66efecf123b143a29f5", "query": "in.Spec.InitContainers = values // Call defaulters explicitly until annotations are removed <del> for i := range in.Spec.InitContainers { c := &in.Spec.InitContainers[i] SetDefaults_Container(c) </del> <ins> tmpPodTemp := &PodTemplate{ Template: PodTemplateSpec{ Spec: PodSpec{ HostNetwork:    in.Spec.HostNetwork, InitContainers: values, }, }, </ins> } <ins> SetObjectDefaults_PodTemplate(tmpPodTemp) in.Spec.InitContainers = tmpPodTemp.Template.Spec.InitContainers </ins> } if err := autoConvert_v1_PodTemplateSpec_To_api_PodTemplateSpec(in, out, s); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-cd1dc8216bffde40e45195a0aceb1bbd0c560296ad557f563dafcf3df89eeea5", "text": "#cat mongo- apiVersion: v1 kind: Pod metadata: labels: name: mongo-svc-a name: mongo-deployment spec: replicas: 1 template: metadata: labels: name: mongo spec: containers: image: mongo name: mongo ports: name: mongo containerPort: hostPort: volumeMounts: mountPath: \"/data/db\" name: mongopv volumes: name: mongopv persistentVolumeClaim: claimName: mongopvc When i want create mongo db container by using this file folowing error is occured. The Pod \"mongo-deployment\" is invalid:spec.containers: Required value\n, it seems there're two here, please remove the first one and have a try.\nHi my kubectl binary is configured at ubuntu 16.04 machine.", "commid": "kubernetes_issue_38542", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-48ff853ff38139a948e4ce6bd92a1d9a92d2e96177bef66efecf123b143a29f5", "query": "in.Spec.InitContainers = values // Call defaulters explicitly until annotations are removed <del> for i := range in.Spec.InitContainers { c := &in.Spec.InitContainers[i] SetDefaults_Container(c) </del> <ins> tmpPodTemp := &PodTemplate{ Template: PodTemplateSpec{ Spec: PodSpec{ HostNetwork:    in.Spec.HostNetwork, InitContainers: values, }, }, </ins> } <ins> SetObjectDefaults_PodTemplate(tmpPodTemp) in.Spec.InitContainers = tmpPodTemp.Template.Spec.InitContainers </ins> } if err := autoConvert_v1_PodTemplateSpec_To_api_PodTemplateSpec(in, out, s); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-7c77a1e7ea84d582b899fa6b8d7216504334c47e064fb8eaad5c523c3bc66a32", "text": "NAME LABELS STATUS 10.1 Ready,SchedulingDisabled 10.2 10.1.10.2 Ready 10.3 Ready apiVersion: v1 kind: Node metadata: creationTimestamp: 2017-03-03T14:41:52Z labels: 10.1.10.1 name: 10.1.10.1 resourceVersion: \"\" selfLink: /api/v1/nodes/10.1.10.1 uid: -001f-11e7-8e83- spec: externalID: 10.1.10.1 status: addresses: address: 10.1.10.1 type: LegacyHostIP address: 10.1.10.1 type: InternalIP capacity: cpu: \"2\" memory: 4041352Ki pods: \"110\" conditions: lastHeartbeatTime: 2017-04-05T18:58:42Z lastTransitionTime: 2017-03-03T14:41:52Z message: kubelet has sufficient disk space available reason: KubeletHasSufficientDisk status: \"False\" type: OutOfDisk lastHeartbeatTime: 2017-04-05T18:58:42Z lastTransitionTime: 2017-04-05T15:27:52Z message: kubelet is posting ready status reason: KubeletReady status: \"True\" type: Ready nodeInfo: bootID: -6124-4ac7-ab96- containerRuntimeVersion: docker://1.12.6 kernelVersion: 4.9.16-coreos-r1 kubeProxyVersion: v1.2.4+coreos.1 kubeletVersion: v1.2.4+coreos.1 machineID: osImage: Container Linux by CoreOS 1298.7.0 (Ladybug) systemUUID: C3FD9852-2DFB-21F4-CE07-2597A746D99D When i create pv for creation pod is shows pv is pending. Please give any suggestions.....\nIs there solution of this problem with version 2.7. Still facing the same. what exactly expectation of helm upgrade --install relname chartsdirectory is is expected to work on first time installation in case with CI/CD Pipelines.", "commid": "kubernetes_issue_38542", "tokennum": 511}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4902a0e694d5ac9b03649ee98bea84195ff7dd47de9766daf6c3dbda26c4ef73", "query": "exit 1 fi <ins> if [ ${#errors_expect_error[@]} -ne 0 ]; then { echo \"Errors:\" for err in \"${errors_expect_error[@]}\"; do echo \"$err\" done echo echo 'The above files need to use framework.ExpectError(err) instead of ' echo 'Expect(err).To(HaveOccurred()) or gomega.Expect(err).To(gomega.HaveOccurred())' echo } >&2 exit 1 fi </ins> echo 'Congratulations!  All e2e test source files are valid.'", "positive_passages": [{"docid": "doc-en-kubernetes-c082543f1889f90c5ee780d309eeb8f41ee57a7e9e8bb6b6fe7c2e4381ff48af", "text": "What happened: After fixing golint failures under (now still in progress), we need to put for each and . Then common error checking code has become like: We can replace this code with which is more readable and easy to be understood what the code does. Now we have following e2e test directories which can be replaced: [x] test/e2e/apimachinery/ () [x] test/e2e/apps/ () [x] test/e2e/auth/ () [x] test/e2e/common/ () [x] test/e2e/node/ () [x] test/e2e/storage/ () [x] () [x] () [x] () [x] () [x] () [x] () [x] [x] test/e2e/storage/persistentvolumes- [x] () [x] () [x] [x] [x] [x] [x] ()\n/sig testing /kind cleanup\n/assign PR will be submitted soon.\nFix the following in\nFix in\nFix in\nHi, maybe I could take files beneath test/e2e/storage/vsphere/\noops, I'm finished and prepare for PR.\nThank you That's OK\nFix the following in\n/assign\nAll related PRs were merged. I think this ticket can be closed. BTW, should we also replace to ?\nThanks for your work. thing is managed with We are almost finishing the work also :-)\n/remove-kind bug\nI found in these files. I'm working on :\nI can work to the following item.", "commid": "kubernetes_issue_77706", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-490b2a0aea7e3c7ba6317eb7b709ce163197e1fcf0523c80bab869eddfb1050f", "query": "} } <del> _, err = client.CoreV1().Pods(\"default\").Create(reinvocationMarkerFixture) if err != nil { t.Fatal(err) } </del> for i, tt := range testCases { t.Run(tt.name, func(t *testing.T) { upCh := recorder.Reset() <del> ns := fmt.Sprintf(\"reinvoke-%d\", i) _, err = client.CoreV1().Namespaces().Create(&v1.Namespace{ObjectMeta: metav1.ObjectMeta{Name: ns}}) </del> <ins> testCaseID := strconv.Itoa(i) ns := \"reinvoke-\" + testCaseID nsLabels := map[string]string{\"test-case\": testCaseID} _, err = client.CoreV1().Namespaces().Create(&v1.Namespace{ObjectMeta: metav1.ObjectMeta{Name: ns, Labels: nsLabels}}) if err != nil { t.Fatal(err) } // Write markers to a separate namespace to avoid cross-talk markerNs := ns + \"-markers\" markerNsLabels := map[string]string{\"test-markers\": testCaseID} _, err = client.CoreV1().Namespaces().Create(&v1.Namespace{ObjectMeta: metav1.ObjectMeta{Name: markerNs, Labels: markerNsLabels}}) </ins> if err != nil { t.Fatal(err) } <ins> // Create a maker object to use to check for the webhook configurations to be ready. marker, err := client.CoreV1().Pods(markerNs).Create(newReinvocationMarkerFixture(markerNs)) if err != nil { t.Fatal(err) } fail := admissionv1beta1.Fail </ins> webhooks := []admissionv1beta1.MutatingWebhook{} for j, webhook := range tt.webhooks { <del> name := fmt.Sprintf(\"admission.integration.test.%d.%s\", j, strings.TrimPrefix(webhook.path, \"/\")) fail := admissionv1beta1.Fail </del> endpoint := webhookServer.URL + webhook.path <ins> name := fmt.Sprintf(\"admission.integration.test.%d.%s\", j, strings.TrimPrefix(webhook.path, \"/\")) </ins> webhooks = append(webhooks, admissionv1beta1.MutatingWebhook{ Name: name, ClientConfig: admissionv1beta1.WebhookClientConfig{", "positive_passages": [{"docid": "doc-en-kubernetes-ddb9bacde18c9f97d2ebd4306efde2d358d8075e932023fee86edf729006549a", "text": "Which jobs are failing: Which test(s) are failing: Since when has it been failing: Testgrid link: Reason for failure: Anything else we need to know: /sig api-machinery /assign\n/cc\nwant to take a look at the audit event issue first? I can dig in after that if issues remain.\nyes, I'm looking at the audit event issue now\nactually the failure message suggests that the missing audit log is caused by unexpected admission invocation: I think it's unrelated to auditing Note that there are two tests named \"no reinvocation of webhook B when in-tree or prior webhook mutations\" :( and from the audit log (), it also suggests that the test is hitting a wrong endpoint\nThanks I'll dig in.", "commid": "kubernetes_issue_82693", "tokennum": 163}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4915f8d77f840d5d1257e808ad509fcb9e370fbf029f72802bc8f3415e716c16", "query": "<ins> /* Copyright 2023 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package service import ( \"context\" \"net\" \"time\" \"google.golang.org/grpc\" \"k8s.io/klog/v2\" kmsapi \"k8s.io/kms/apis/v2alpha1\" ) // GRPCService is a gprc server that runs the kms v2 alpha 1 API. type GRPCService struct { addr    string timeout time.Duration server  *grpc.Server kmsService Service } var _ kmsapi.KeyManagementServiceServer = (*GRPCService)(nil) // NewGRPCService creates an instance of GRPCService. func NewGRPCService( address string, timeout time.Duration, kmsService Service, ) *GRPCService { klog.V(4).InfoS(\"KMS plugin configured\", \"address\", address, \"timeout\", timeout) return &GRPCService{ addr:       address, timeout:    timeout, kmsService: kmsService, } } // ListenAndServe accepts incoming connections on a Unix socket. It is a blocking method. // Returns non-nil error unless Close or Shutdown is called. func (s *GRPCService) ListenAndServe() error { ln, err := net.Listen(\"unix\", s.addr) if err != nil { return err } defer ln.Close() gs := grpc.NewServer( grpc.ConnectionTimeout(s.timeout), ) s.server = gs kmsapi.RegisterKeyManagementServiceServer(gs, s) klog.V(4).InfoS(\"kms plugin serving\", \"address\", s.addr) return gs.Serve(ln) } // Shutdown performs a grafecul shutdown. Doesn't accept new connections and // blocks until all pending  RPCs are finished. func (s *GRPCService) Shutdown() { klog.V(4).InfoS(\"kms plugin shutdown\", \"address\", s.addr) if s.server != nil { s.server.GracefulStop() } } // Close stops the server by closing all connections immediately and cancels // all active RPCs. func (s *GRPCService) Close() { klog.V(4).InfoS(\"kms plugin close\", \"address\", s.addr) if s.server != nil { s.server.Stop() } } // Status sends a status request to specified kms service. func (s *GRPCService) Status(ctx context.Context, _ *kmsapi.StatusRequest) (*kmsapi.StatusResponse, error) { res, err := s.kmsService.Status(ctx) if err != nil { return nil, err } return &kmsapi.StatusResponse{ Version: res.Version, Healthz: res.Healthz, KeyId:   res.KeyID, }, nil } // Decrypt sends a decryption request to specified kms service. func (s *GRPCService) Decrypt(ctx context.Context, req *kmsapi.DecryptRequest) (*kmsapi.DecryptResponse, error) { klog.V(4).InfoS(\"decrypt request received\", \"id\", req.Uid) plaintext, err := s.kmsService.Decrypt(ctx, req.Uid, &DecryptRequest{ Ciphertext:  req.Ciphertext, KeyID:       req.KeyId, Annotations: req.Annotations, }) if err != nil { return nil, err } return &kmsapi.DecryptResponse{ Plaintext: plaintext, }, nil } // Encrypt sends an encryption request to specified kms service. func (s *GRPCService) Encrypt(ctx context.Context, req *kmsapi.EncryptRequest) (*kmsapi.EncryptResponse, error) { klog.V(4).InfoS(\"encrypt request received\", \"id\", req.Uid) encRes, err := s.kmsService.Encrypt(ctx, req.Uid, req.Plaintext) if err != nil { return nil, err } return &kmsapi.EncryptResponse{ Ciphertext:  encRes.Ciphertext, KeyId:       encRes.KeyID, Annotations: encRes.Annotations, }, nil } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-82432c9a9613bf4aed980cc8db469ba43857eb8e48c1e0dd0f39492115206ab6", "text": "generation for local KEK based on counter; also rotate once a week even if the counter does not hit 2 million? using AES-GCM encryption of local KEK ref: The implementation would be to the directory.\n/sig auth /triage accepted\n/assign\nGitHub didn't allow me to assign the following users: ibihim. 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\n/assign\nthank you !\n/milestone v1.26\nHi bug-triage shadow team member for 1.26 here. Looks like this issue is in the 1.26 milestone, but has been moved to 1.27. Is there something else or should this issue go to 1.27 as well? Thank you!\nI just forgot to move this issue /milestone v1.27\n/reopen is the partial implementation.\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nMy suggestion on the reference implementation, after reading 's comments is like so... The GRPC server, which implements the expects an implementation that satisfies . The local key logic can be a middleware. So it expects a it can fallback to, if it doesn't know a key or needs to encrypt its own local KEK. So the local implementation would be need to: have a storage of s have a reference to the current in use (if we put it into the cache, it might vanish) have a reference to another , which should be the remote KMS. So the sub-stories could look like: write Middleware write Transformers that can get exhausted (by time, by usage) write 's storage write some dummy for remote KMS? I have some sketches of what I am talking about .", "commid": "kubernetes_issue_112859", "tokennum": 462}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4915f8d77f840d5d1257e808ad509fcb9e370fbf029f72802bc8f3415e716c16", "query": "<ins> /* Copyright 2023 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package service import ( \"context\" \"net\" \"time\" \"google.golang.org/grpc\" \"k8s.io/klog/v2\" kmsapi \"k8s.io/kms/apis/v2alpha1\" ) // GRPCService is a gprc server that runs the kms v2 alpha 1 API. type GRPCService struct { addr    string timeout time.Duration server  *grpc.Server kmsService Service } var _ kmsapi.KeyManagementServiceServer = (*GRPCService)(nil) // NewGRPCService creates an instance of GRPCService. func NewGRPCService( address string, timeout time.Duration, kmsService Service, ) *GRPCService { klog.V(4).InfoS(\"KMS plugin configured\", \"address\", address, \"timeout\", timeout) return &GRPCService{ addr:       address, timeout:    timeout, kmsService: kmsService, } } // ListenAndServe accepts incoming connections on a Unix socket. It is a blocking method. // Returns non-nil error unless Close or Shutdown is called. func (s *GRPCService) ListenAndServe() error { ln, err := net.Listen(\"unix\", s.addr) if err != nil { return err } defer ln.Close() gs := grpc.NewServer( grpc.ConnectionTimeout(s.timeout), ) s.server = gs kmsapi.RegisterKeyManagementServiceServer(gs, s) klog.V(4).InfoS(\"kms plugin serving\", \"address\", s.addr) return gs.Serve(ln) } // Shutdown performs a grafecul shutdown. Doesn't accept new connections and // blocks until all pending  RPCs are finished. func (s *GRPCService) Shutdown() { klog.V(4).InfoS(\"kms plugin shutdown\", \"address\", s.addr) if s.server != nil { s.server.GracefulStop() } } // Close stops the server by closing all connections immediately and cancels // all active RPCs. func (s *GRPCService) Close() { klog.V(4).InfoS(\"kms plugin close\", \"address\", s.addr) if s.server != nil { s.server.Stop() } } // Status sends a status request to specified kms service. func (s *GRPCService) Status(ctx context.Context, _ *kmsapi.StatusRequest) (*kmsapi.StatusResponse, error) { res, err := s.kmsService.Status(ctx) if err != nil { return nil, err } return &kmsapi.StatusResponse{ Version: res.Version, Healthz: res.Healthz, KeyId:   res.KeyID, }, nil } // Decrypt sends a decryption request to specified kms service. func (s *GRPCService) Decrypt(ctx context.Context, req *kmsapi.DecryptRequest) (*kmsapi.DecryptResponse, error) { klog.V(4).InfoS(\"decrypt request received\", \"id\", req.Uid) plaintext, err := s.kmsService.Decrypt(ctx, req.Uid, &DecryptRequest{ Ciphertext:  req.Ciphertext, KeyID:       req.KeyId, Annotations: req.Annotations, }) if err != nil { return nil, err } return &kmsapi.DecryptResponse{ Plaintext: plaintext, }, nil } // Encrypt sends an encryption request to specified kms service. func (s *GRPCService) Encrypt(ctx context.Context, req *kmsapi.EncryptRequest) (*kmsapi.EncryptResponse, error) { klog.V(4).InfoS(\"encrypt request received\", \"id\", req.Uid) encRes, err := s.kmsService.Encrypt(ctx, req.Uid, req.Plaintext) if err != nil { return nil, err } return &kmsapi.EncryptResponse{ Ciphertext:  encRes.Ciphertext, KeyId:       encRes.KeyID, Annotations: encRes.Annotations, }, nil } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-b75b4d558a76c05a2f299aa9e4208bfe14cbcf4125785eeef841ee037778035f", "text": "I would implement that in terms of the interface so that it can be used both in testing (via a local key) and in real code (by delegating to a HSM).\nHi bug-triage team member for 1.27 here. This issue is still open but has had no recent activity, and no active PRs. Is everything on track for the Code Freeze in March 14th? Thank you!\n/milestone clear\nCould be closed, right? :)\nWe still need metrics and tracing support for the reference implementation (though it is all a lot less important now).\n/retitle [KMSv2] Add metrics and tracing in for plugins\nThis is duplicate of /close\nClosing this issue. <detailsIn response to : This is duplicate of 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", "commid": "kubernetes_issue_112859", "tokennum": 192}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4947fed7c4a0646e80b5991a859d07a759d92c7b2c97eb6e03789dbd6327da67", "query": "set -o pipefail set -o xtrace <ins> retry() { for i in {1..5}; do \"$@\" && return 0 || sleep $i done \"$@\" } </ins> # Runs the unit and integration tests, producing JUnit-style XML test # reports in ${WORKSPACE}/artifacts. This script is intended to be run from # kubekins-test container with a kubernetes repo mapped in. See", "positive_passages": [{"docid": "doc-en-kubernetes-bbec53075a30148d3cbdbc5512f8af7c37c0a3695f84aff12aac6489eaa4282e", "text": "Not sure if this concided with a Jenkins restart.\nNot sure what we can do about this. Retry a few times?\nGitHub seemed to hiccup last night and fail a bunch of our builds. I'm not sure a retry would've helped, unless we kept retrying for many minutes.\nThis is the sort of thing that just happens occasionally. We've seen this a lot in OpenShift CI runs. I'm not sure there's much you can do other than try to avoid external network access (e.g. bake tools into the VM image).\nIt seems to have occurred twice in the last 12h so retry w/ timeout can't hurt?\nIt can't hurt... but it may or may not help depending on the extent of the external issue\nIf the problem is really bad, we could toss it somewhere on GCS?\nLooks like it failed on : We should probably put this in a retry loop or else do something more fancy", "commid": "kubernetes_issue_21887", "tokennum": 212}], "negative_passages": []}
{"query_id": "q-en-kubernetes-496cc39dcd83d99cb83e098fb559257edc7b870a65c27986e4fe95758c6e3f72", "query": "q := NewPriorityQueue(nil) q.Add(&medPriorityPod) // Add a couple of pods to the unschedulableQ. <del> q.unschedulableQ.addOrUpdate(&unschedulablePod) q.unschedulableQ.addOrUpdate(affinityPod) </del> <ins> addOrUpdateUnschedulablePod(q, &unschedulablePod) addOrUpdateUnschedulablePod(q, affinityPod) </ins> // Simulate addition of an assigned pod. The pod has matching labels for // affinityPod. So, affinityPod should go to activeQ. q.AssignedPodAdded(&labelPod) <del> if q.unschedulableQ.get(affinityPod) != nil { </del> <ins> if getUnschedulablePod(q, affinityPod) != nil { </ins> t.Error(\"affinityPod is still in the unschedulableQ.\") } if _, exists, _ := q.activeQ.Get(affinityPod); !exists { t.Error(\"affinityPod is not moved to activeQ.\") } // Check that the other pod is still in the unschedulableQ. <del> if q.unschedulableQ.get(&unschedulablePod) == nil { </del> <ins> if getUnschedulablePod(q, &unschedulablePod) == nil { </ins> t.Error(\"unschedulablePod is not in the unschedulableQ.\") } }", "positive_passages": [{"docid": "doc-en-kubernetes-e059cd0647305d70a174ce6bffb9584a993a023526be428075760ddef27cc3b0", "text": "Which jobs are failing: pull-kubernetes-bazel-test Which test(s) are failing: bazel test //pkg/scheduler/internal/queue:godefaulttest Since when has it been failing: Testgrid link: Reason for failure: WARNING: DATA RACE Read at 0x00c000230db0 by goroutine 47: runtime.mapiterinit() +0x0 (PriorityQueue).flushUnschedulableQLeftover() +0x17a (PriorityQueue).flushUnschedulableQLeftover-fm() +0x41 () +0x61 () +0xce () +0x5a Previous write at 0x00c000230db0 by goroutine 45: runtime.mapassignfaststr() +0x0 (UnschedulablePodsMap).addOrUpdate() +0x30e () +0x601 testing.tRunner() +0x162 Goroutine 47 (running) created at: (PriorityQueue).run() +0x172 () +0xe0b () +0x50 () +0x5a5 testing.tRunner() +0x162 Goroutine 45 (running) created at: testing.(T).Run() +0x659 testing.runTests.func1() +0xa8 testing.tRunner() +0x162 testing.runTests() +0x4ee testing.(M).Run() +0x2ee () bazel-out/k8- +0x2fb Anything else we need to know: I'm very sorry about that. UnschedulablePodsMap is not thread-safe. In , lock will be acquired before operating UnschedulablePodsMap. But in , lock isn\u2018t be acquired. In the previous case, only a single thread runs so it's ok. But after add goroutine , there will be data race. So I need to acquire lock before operating UnschedulablePodsMap.\n/sig testing /sig scheduling", "commid": "kubernetes_issue_73021", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-496de095dbd61aa881f139a35f827f2da0498d7976df91c2980017c1f56b8754", "query": "defer ws.Close() buf := &bytes.Buffer{} <del> for { var msg []byte if err := websocket.Message.Receive(ws, &msg); err != nil { if err == io.EOF { break </del> <ins> Eventually(func() error { for { var msg []byte if err := websocket.Message.Receive(ws, &msg); err != nil { if err == io.EOF { break } framework.Failf(\"Failed to read completely from websocket %s: %v\", url.String(), err) </ins> } <del> framework.Failf(\"Failed to read completely from websocket %s: %v\", url.String(), err) </del> <ins> if len(msg) == 0 { continue } if msg[0] != 1 { framework.Failf(\"Got message from server that didn't start with channel 1 (STDOUT): %v\", msg) } buf.Write(msg[1:]) </ins> } <del> if len(msg) == 0 { continue </del> <ins> if buf.Len() == 0 { return fmt.Errorf(\"Unexpected output from server\") </ins> } <del> if msg[0] != 1 { framework.Failf(\"Got message from server that didn't start with channel 1 (STDOUT): %v\", msg) </del> <ins> if !strings.Contains(buf.String(), \"nameserver\") { return fmt.Errorf(\"Expected to find 'nameserver' in %q\", buf.String()) </ins> } <del> buf.Write(msg[1:]) } if buf.Len() == 0 { framework.Failf(\"Unexpected output from server\") } if !strings.Contains(buf.String(), \"nameserver\") { framework.Failf(\"Expected to find 'nameserver' in %q\", buf.String()) } </del> <ins> return nil }, time.Minute, 10*time.Second).Should(BeNil()) </ins> }) It(\"should support retrieving logs from the container over websockets\", func() {", "positive_passages": [{"docid": "doc-en-kubernetes-0ee4ddd459987abc7d27aa8e986e315d7cf0d398b8e3fe4f5bf18ea9cc8fa8dc", "text": "https://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite}\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite}\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite}\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .", "commid": "kubernetes_issue_30567", "tokennum": 542}], "negative_passages": []}
{"query_id": "q-en-kubernetes-496de095dbd61aa881f139a35f827f2da0498d7976df91c2980017c1f56b8754", "query": "defer ws.Close() buf := &bytes.Buffer{} <del> for { var msg []byte if err := websocket.Message.Receive(ws, &msg); err != nil { if err == io.EOF { break </del> <ins> Eventually(func() error { for { var msg []byte if err := websocket.Message.Receive(ws, &msg); err != nil { if err == io.EOF { break } framework.Failf(\"Failed to read completely from websocket %s: %v\", url.String(), err) </ins> } <del> framework.Failf(\"Failed to read completely from websocket %s: %v\", url.String(), err) </del> <ins> if len(msg) == 0 { continue } if msg[0] != 1 { framework.Failf(\"Got message from server that didn't start with channel 1 (STDOUT): %v\", msg) } buf.Write(msg[1:]) </ins> } <del> if len(msg) == 0 { continue </del> <ins> if buf.Len() == 0 { return fmt.Errorf(\"Unexpected output from server\") </ins> } <del> if msg[0] != 1 { framework.Failf(\"Got message from server that didn't start with channel 1 (STDOUT): %v\", msg) </del> <ins> if !strings.Contains(buf.String(), \"nameserver\") { return fmt.Errorf(\"Expected to find 'nameserver' in %q\", buf.String()) </ins> } <del> buf.Write(msg[1:]) } if buf.Len() == 0 { framework.Failf(\"Unexpected output from server\") } if !strings.Contains(buf.String(), \"nameserver\") { framework.Failf(\"Expected to find 'nameserver' in %q\", buf.String()) } </del> <ins> return nil }, time.Minute, 10*time.Second).Should(BeNil()) </ins> }) It(\"should support retrieving logs from the container over websockets\", func() {", "positive_passages": [{"docid": "doc-en-kubernetes-fb627aaedb9842e8bb093b3b041ba36363dfd64edbe1bdb335141eb36555e82f", "text": "https://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite}\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite}\nThe test pod gets deleted by the test upon failure and so there is not enough information about the state of the test pod. I'm changing the test to not delete the pod and instead let the namespace deletion logic in the test framework handle deletions. I'm also increasing the pod lifetime from to a longer duration to avoid any possible race conditions in the test. The test will also retry if the logs output from the test pod does not contain non-space characters.", "commid": "kubernetes_issue_30567", "tokennum": 565}], "negative_passages": []}
{"query_id": "q-en-kubernetes-496de095dbd61aa881f139a35f827f2da0498d7976df91c2980017c1f56b8754", "query": "defer ws.Close() buf := &bytes.Buffer{} <del> for { var msg []byte if err := websocket.Message.Receive(ws, &msg); err != nil { if err == io.EOF { break </del> <ins> Eventually(func() error { for { var msg []byte if err := websocket.Message.Receive(ws, &msg); err != nil { if err == io.EOF { break } framework.Failf(\"Failed to read completely from websocket %s: %v\", url.String(), err) </ins> } <del> framework.Failf(\"Failed to read completely from websocket %s: %v\", url.String(), err) </del> <ins> if len(msg) == 0 { continue } if msg[0] != 1 { framework.Failf(\"Got message from server that didn't start with channel 1 (STDOUT): %v\", msg) } buf.Write(msg[1:]) </ins> } <del> if len(msg) == 0 { continue </del> <ins> if buf.Len() == 0 { return fmt.Errorf(\"Unexpected output from server\") </ins> } <del> if msg[0] != 1 { framework.Failf(\"Got message from server that didn't start with channel 1 (STDOUT): %v\", msg) </del> <ins> if !strings.Contains(buf.String(), \"nameserver\") { return fmt.Errorf(\"Expected to find 'nameserver' in %q\", buf.String()) </ins> } <del> buf.Write(msg[1:]) } if buf.Len() == 0 { framework.Failf(\"Unexpected output from server\") } if !strings.Contains(buf.String(), \"nameserver\") { framework.Failf(\"Expected to find 'nameserver' in %q\", buf.String()) } </del> <ins> return nil }, time.Minute, 10*time.Second).Should(BeNil()) </ins> }) It(\"should support retrieving logs from the container over websockets\", func() {", "positive_passages": [{"docid": "doc-en-kubernetes-eece27d155d201a0e15709c787b1cd71b8915e6d11b38f7ce2b38d06c62ffea6", "text": "I'm lowering the priority of this test once my changes go in and see if the flake re-appears.\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nI suspect a race between container starting up and the test querying the logs. I'm adding a retry in the test to avoid the race. Lowering the priority since I still don't suspect any kubelet bugs.\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite}\nhttps://k8s- Failed: [] Pods should support retrieving logs from the container over websockets {E2eNode Suite} Happened on a presubmit run in .", "commid": "kubernetes_issue_30567", "tokennum": 369}], "negative_passages": []}
{"query_id": "q-en-kubernetes-497aff69f23cfaa988115918b22aef0580c22dfbb472ebc4fcce62793b185ae0", "query": "FindBoundSatsified:   false, }, eventReason: \"FailedScheduling\", <del> expectError: makePredicateError(\"1 VolumeNodeAffinityConflict\"), </del> <ins> expectError: makePredicateError(\"1 node(s) had volume node affinity conflict\"), </ins> }, \"unbound,no-matches\": { volumeBinderConfig: &persistentvolume.FakeVolumeBinderConfig{", "positive_passages": [{"docid": "doc-en-kubernetes-10c13016eb5239afc7a330cfdab91dbf78232a49f2993f71669df735dbb939e1", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature The is not user friendly. There has been to make it better, but we still print in the pending message. We should change these errors to a more human readable message. For example, should be changed to something like . /sig scheduling", "commid": "kubernetes_issue_58546", "tokennum": 91}], "negative_passages": []}
{"query_id": "q-en-kubernetes-497c5b0a982d73a133eee69da91338d5b39eb6d717be0d3598b7423638bbd4f4", "query": "ginkgo.By(fmt.Sprintf(\"SSH'ing to %d nodes and running %s\", len(testhosts), testCase.cmd)) for _, host := range testhosts { <ins> ginkgo.By(fmt.Sprintf(\"SSH'ing host %s\", host)) </ins> result, err := e2essh.SSH(testCase.cmd, host, framework.TestContext.Provider) stdout, stderr := strings.TrimSpace(result.Stdout), strings.TrimSpace(result.Stderr) if err != testCase.expectedError {", "positive_passages": [{"docid": "doc-en-kubernetes-375711dd290c57e850707ef6745091e3080fe654060082beb69e30fe80db0e88", "text": "ci-kubernetes-e2e-gce-scale-correctness Kubernetes e2e suite: [sig-node] SSH should SSH to all nodes and run commands kubetest.Test Jul 10 14:01:51 UTC+0200 Kubernetes e2e suite: [sig-node] SSH should SSH to all nodes and run commands: more . Test /sig node\n/cc\n/triage accepted\nUhhh, this may help here\n/milestone v1.22\n/sig scalability FYI\nI got annoyed that I couldn't click through to see the other logs, so now you can, ref: (spyglass doesn't render build- because it's 500MB, and the limit for rendering is 100MB)\n/assign SIG Scalability chairs/TLs, please find someone to address or call this a non-release-blocking failure\nAssigning to current scalability oncall (): /assign\nThis is sig-node issue - should be addres by SIG-node folks. /sig node\nis being discussed as a fix for this and I'm not sure it's correct\nis it sig scalability's intent that 5k node clusters should support SSH?\nThe SSH test in question passes in the \"default\" job: So the fact that this failure is unique to a scalability job means to me that scalability needs to own at least some part of this\nI did a little bit of digging and ci-kubernetes-e2e-gce-scale-correctness uses option in kubetest, which according to seems to be setting KUBESSHBASTION env. So I believe this is main difference between our scalability job and \"default\".\nDebugging the test in and providing a fix there. The crictl host PR () is doing something different.", "commid": "kubernetes_issue_103688", "tokennum": 400}], "negative_passages": []}
{"query_id": "q-en-kubernetes-497e42d5cee95380a996a1edf0c64cd9e79fa77f0e3dde52f91874b1b203d73e", "query": "<del> apiVersion: extensions/v1beta1 </del> <ins> apiVersion: networking.k8s.io/v1beta1 </ins> kind: Ingress metadata: name: pre-shared-cert", "positive_passages": [{"docid": "doc-en-kubernetes-bb7c21eb048735f6a80e177a210d26530b5959539babed9d56a66ccfff61adf4", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: Which test(s) are failing: Since when has it been failing: Testgrid link: https://k8s- Reason for failure: Anything else we need to know: /cc /milestone v1.19 /priority important-soon /sig network\nRef:\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nmy fu points me to this commit [] Fix multiple conversion tests that belongs to this PR , that seems related can you confirm if that PR is causing this test to fail? (should we gate on this test?)\nYes, that PR is related to the failure. The test utility is trying to convert extensions/v1beta1 data read from various files directly to a go type. This was never a valid thing to do, and happened to silently succeed because the two structs had an identical structure. This is exactly the type of bug was designed to flush out\nthe correct fix is to update the test/e2e/testing- files to\n/assign\nIt was my PR that broke this - I can also fix that.\nThanks, o it was the commit that was good but the test that was wrong :upsidedownface: , At least I got right the commit :sweat_smile:\nis out for review (talked with offline, he was aware that I'll send that out)", "commid": "kubernetes_issue_90451", "tokennum": 318}], "negative_passages": []}
{"query_id": "q-en-kubernetes-497eaace1e80105629b4df313bb48300a519f943ad476b33c965fe0906a44b21", "query": "import ( \"fmt\" <ins> \"strings\" </ins> \"testing\" )", "positive_passages": [{"docid": "doc-en-kubernetes-984aaf2876c4d4651f6765b291626bccfb7d6364087d7ebb11c97e2832c59ee5", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Below k8s UT fail when run with master-golang. TestCheckpointStateRestore/RestorecheckpointwithinvalidJSON error:=== RUN TestCheckpointStateRestore/RestorecheckpointwithinvalidJSON I1124 05:38:14. ] [cpumanager] initializing new in-memory state store unexpected error while creatng checkpointState: could not restore state from checkpoint: json: unexpected end of JSON input, please drain this node and delete the CPU manager checkpoint file \"/tmp/cpumanagerstatetest479660663/cpumanagercheckpointtest\" before restarting Kubelet --- FAIL: TestCheckpointStateRestore/RestorecheckpointwithinvalidJSON (0.00s) TestStrategicMergePatchInvalid error:=== RUN TestStrategicMergePatchInvalid expected \"invalid character 'b' looking for beginning of value\", got \"json: invalid character 'b' looking for beginning of value\" --- FAIL: TestStrategicMergePatchInvalid (0.00s) TestJSONPatch error:=== RUN TestJSONPatch invalid-syntax: expected error invalid character 'i' looking for beginning of value, but got json: invalid character 'i' looking for beginning of value --- FAIL: TestJSONPatch (0.00s) TestV4ErrorDecoder expandless error:=== RUN TestV4ErrorDecoder wrong error for message \"{\": want=\"error stream protocol error: unexpected end of JSON input in \"{\"\", got=\"error stream protocol error: json: unexpected end of JSON input in \"{\"\" --- FAIL: TestV4ErrorDecoder (0.00s What you expected to happen: The tests should pass with no error. How to reproduce it (as minimally and precisely as possible): a stable version of golang installed master go from upstream git clone cd go/src cd ../.. cp -r ./go /usr/local export PATH=/usr/local/go/bin:$PATH kubernetes repo and run the unit tests. () Anything else we need to know?: These failures are occurring due to mismatch of error messages between upstream go and the k8s tests.", "commid": "kubernetes_issue_96853", "tokennum": 597}], "negative_passages": []}
{"query_id": "q-en-kubernetes-497eaace1e80105629b4df313bb48300a519f943ad476b33c965fe0906a44b21", "query": "import ( \"fmt\" <ins> \"strings\" </ins> \"testing\" )", "positive_passages": [{"docid": "doc-en-kubernetes-d960907779eeb813df14a2ea4a00c97f52784ded937dbf1c71e5b05391843c78", "text": "There is an addition \"json:\" prefix to SyntaxError messages after this below commit: Environment: Kubernetes version (use ): latest source code from upstream Cloud provider or hardware configuration: OS (e.g: ): \"CentOS Linux 8 (Core)\" Kernel (e.g. ): Linux rajalakshmi-workspace 4.18.0-193.19.1.el82.ppc64le SMP Mon Sep 14 14:48:04 UTC 2020 ppc64le ppc64le ppc64le GNU/Linux Install tools: [root go]# go version go version devel + Fri Nov 20 00:54:43 2020 +0000 linux/ppc64le [root go]# Network plugin and version (if this is a network-related bug): Others:\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig testing\nwill fix it in Go 1.16 as release-blocker.\nI would fix the test here to be more tolerant. exact string matches on error messages aren't really an API\u2026 I would not expect that to block the golang release\nAgree too, we can think about having a substring match to avoid these issues instead!\n/assign Lets see if we can fix this in the k8s tests", "commid": "kubernetes_issue_96853", "tokennum": 352}], "negative_passages": []}
{"query_id": "q-en-kubernetes-49ac6e2a8d890b23d5b546431f225c35995e5a6452fe78a76f10a0729c7c9561", "query": "ginkgo.Context(\"when gracefully shutting down with Pod priority\", func() { const ( <del> pollInterval           = 1 * time.Second podStatusUpdateTimeout = 10 * time.Second </del> <ins> pollInterval                 = 1 * time.Second podStatusUpdateTimeout       = 10 * time.Second priorityClassesCreateTimeout = 10 * time.Second </ins> ) var (", "positive_passages": [{"docid": "doc-en-kubernetes-bc1f56f76d806f780c64417014c4b072addf1f4df6d254dd55319774f349a24c", "text": "Flaked a couple of times on serial lane with the same error. Test is relatively new. This run only has the single test flake: /sig node /kind flake /cc\n/assign\nNew recent failures: /triage accepted", "commid": "kubernetes_issue_106664", "tokennum": 50}], "negative_passages": []}
{"query_id": "q-en-kubernetes-49ff8936875095178ec4f1ec9edeffc4308821d5f8b341173fa5243d29bf0104", "query": "// for the iSCSI connection. dirs2, err := io.ReadDir(sessionPath) if err != nil { <del> return nil, err </del> <ins> klog.Infof(\"Failed to process session %s, assuming this session is unavailable: %s\", sessionName, err) continue </ins> } for _, dir2 := range dirs2 { // Skip over files that aren't the connection", "positive_passages": [{"docid": "doc-en-kubernetes-2bba8e4fb458ddf612a1ae84873c0951878ae27f68765b5b6efc434715382796", "text": "If one target in multipath volume gets down and a pod that uses the volume is deleted and quickly recreated (e.g. by a Deployment), the new pod never starts. How to reproduce it (as minimally and precisely as possible): Deployment with single replica with one multipath iSCSI volume one target (e.g. switch the machine off). Multipath will mark appropriate path as failed: the deployment pod. will quickly start a new pod for the Deployment. new pod will be (or ) forever, What happened: Kubelet tries to WaitForAttach / SetUp volume for the new pod. The volume is still attached. Kubelet goes through all targets and tries to find out if it's logged in or not. Eventually it tries to read of the failed path and that returns error: What you expected to happen: Kubelet assumes that the path is failed / not logged in and tries to recover it. If it fails it continues with multipath with 2 available devices and 1 failed one. IMO, simple instead of will do its job just fine. /assign /sig storage cc for iSCSI expertise\nFix:", "commid": "kubernetes_issue_74305", "tokennum": 238}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4a0e748b6268c8cdac8821e5dddcb61664f3dda7afc5cb4898bd6c6e2e93b899", "query": "return nil } <ins> // hasServedCRDVersion returns true if the given version is in the list of CRD's versions and the Served flag is set. func hasServedCRDVersion(spec *apiextensions.CustomResourceDefinitionSpec, version string) bool { for _, v := range spec.Versions { if v.Name == version { return v.Served } } return false } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-16c95be4925a0d298a67709c93efbb137b71325e5e3041edcf306d6572e4ae65", "text": "Which jobs are failing: pull-kubernetes-integration Which test(s) are failing: TestWebhookConverterWithDefaulting /assign /priority important-soon /area custom-resources /sig api-machinery /kind flake /milestone v1.16\n/cc\nseveral of the webhook converter tests have similar flakes. it looks like the wait for storage version to become effective times out occasionally Rare flakes seen in all of these tests: TestWebhookConverterWithWatchCache/nontrivial-converter TestWebhookConverterWithWatchCache/metadata-mutating-converter TestWebhookConverterWithDefaulting/metadata-mutating-converter TestWebhookConverterWithWatchCache/noop-converter TestWebhookConverterWithDefaulting/empty-response TestWebhookConverterWithoutWatchCache/nontrivial-converter/check-2 TestWebhookConverterWithoutWatchCache/noop-converter/check-0/v1beta2 TestWebhookConverterWithoutWatchCache/nontrivial-converter/check-0/v1beta2\ncc\nYikes, I\u2019ll sort it out.\niiuc sending an empty patch gets short-circuited and doesn't bump CR generation, even if the storage version gets changed, which means we do not re-write to etcd and go through the encoding path this would be racing and doing noop's if the first pass of didn't get the expected storage version I will send a fix to make the patch do actual mutation\nIt doesn't bump generation, but the bytes to persist in etcd would still be different if the storage version had changed, so they should persist. You can verify that by changing the storage version on a CRD yourself, do an empty patch, and see if the resourceVersion changes.\nyou're right. Generation is for non-metadata change only, and the RV changes. I queried etcd locally and the apiVersion did change for an empty patch (sidetracking: another observation is after changing the storage version (say v1 -v2; noop convertor), empty-patching v2 endpoint would bump generation, while empty-patching v1 endpoint wouldn't)\nanother theory: our cached storage strategy could be stale if the CRD informer merges multiple events together (e.g. the informer does a re-list).", "commid": "kubernetes_issue_78913", "tokennum": 546}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4a0e748b6268c8cdac8821e5dddcb61664f3dda7afc5cb4898bd6c6e2e93b899", "query": "return nil } <ins> // hasServedCRDVersion returns true if the given version is in the list of CRD's versions and the Served flag is set. func hasServedCRDVersion(spec *apiextensions.CustomResourceDefinitionSpec, version string) bool { for _, v := range spec.Versions { if v.Name == version { return v.Served } } return false } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-4d6bef5a272bfef04fa7527d92c495ee5b0e5d06d06a593b8089b98a3b84ddb9", "text": "Two scenarios: -create-update events merged into an update event: strategy with UID:a was created on demand for CRD Foo Foo was deleted and recreated strategy with UID:b was created on demand for the new Foo new Foo got updated (e.g. switching storage version) the strategy with UID:b is supposed to be deleted and , to reflect the last update. But if the CRD informer merges the delete-create-update events into , the strategy with UID:a will be deleted, but the strategy with UID:b won't. -update events merged into a create event: strategy with UID:a was created on demand for CRD Foo Foo was updated (e.g. switching storage version) the strategy with UID:a is supposed to be deleted and , to reflect the last update. But if the CRD informer merges the create-update events into , the strategy with UID:a won't be deleted (as we don't react on create events). another race found in , which could happen in a single update.\nI think I :", "commid": "kubernetes_issue_78913", "tokennum": 234}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4a2854d89abd7f7d1b9520e2f4bd93925dcfd2bdd18b2d1b571c37a3d3a6d9e8", "query": "\"time\" utilnet \"k8s.io/apimachinery/pkg/util/net\" <ins> utilrand \"k8s.io/apimachinery/pkg/util/rand\" </ins> \"k8s.io/client-go/tools/cache\"", "positive_passages": [{"docid": "doc-en-kubernetes-c5b2d72b2e785256d7a2577807fdbd43ef000a4da594f69c949ac55e4186d114", "text": "[x] two weeks soak end date : 18 March 2021 According to this APIsnoop query, there are still some remaining RESOURCENAME endpoints which are untested. with this query you can filter untested endpoints by their category and eligiblity for conformance. e.g below shows a query to find all conformance eligible untested,stable,core endpoints Note: Community feedback for the e2e test has lead to a number of improvements including extending the test coverage to all outstanding endpoints listed above. As each endpoint is tested a &rsquo;watch&rsquo; confirms that the result is valid before testing the next endpoint. readCoreV1NamespacedServiceStatus (get /status) patchCoreV1NamespacedServiceStatus (patch /status) replaceCoreV1NamespacedServiceStatus (update /status) patchCoreV1NamespacedService Create a Service with a static label Patch the Service with a new label and updated data Get the Service to ensure it&rsquo;s patched Upate the Service with a new label and updated data Get the Service to ensure it&rsquo;s updated Delete Namespaced Service via a Collection with a LabelSelector This query by apisnoop shows that all outstanding endpoints as list at the start of this document have been hit by the e2e test. Note that the results do include other service endpoints that have been addressed in other conformance tests. If a test with these calls gets merged, test coverage will go up by 4 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance\nCan you please review the proposed test and advise if we could go ahead with a PR\n/assign\nIt looks like it's patching metadata and spec but not status?\nIssues 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\n/remove-lifecycle stale\nI've been retesting this mock test and apisnoop does log as been hit. From my testing below it looks like the patchStatus is working as expected or have I missed something?", "commid": "kubernetes_issue_94867", "tokennum": 517}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4a2854d89abd7f7d1b9520e2f4bd93925dcfd2bdd18b2d1b571c37a3d3a6d9e8", "query": "\"time\" utilnet \"k8s.io/apimachinery/pkg/util/net\" <ins> utilrand \"k8s.io/apimachinery/pkg/util/rand\" </ins> \"k8s.io/client-go/tools/cache\"", "positive_passages": [{"docid": "doc-en-kubernetes-6c98fb90bee2cd0d2fc404edc784deab934fddaa81022ed1883862c51f5dae6d", "text": "Using the following code before the patch request Gives this response Then after running the patch ServiceStatus Then running The response shows the patched changes.\nDuring the Conformance Meeting on 12th of January 2021, reviewed approach with Clayton, and we will start on the test PR this week!\n/reopen\nReopened this issue. <detailsIn response to : /reopen </details\n/triage accepted", "commid": "kubernetes_issue_94867", "tokennum": 79}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4a444828d4ad7e3c53833db101c272cf288652b2d6d32c50d2e4f4d3bf1f538f", "query": "// MinionList is a list of minions. type MinionList struct { JSONBase `json:\",inline\" yaml:\",inline\"` <del> Items    []Minion `json:\"minions,omitempty\" yaml:\"minions,omitempty\"` </del> <ins> Items    []Minion `json:\"items,omitempty\" yaml:\"items,omitempty\"` </ins> } // Binding is written by a scheduler to cause a pod to be bound to a host.", "positive_passages": [{"docid": "doc-en-kubernetes-a574ac2a261fa7b4cd59d0907178e287efcaa3989e734104cb2eecf5d89ff460", "text": "should have the JSON attribute name \"items\", not \"minions\"\nDoh! Fix now and break clients?\nDefine Items and Minions and use Convertors to resolve it?\nSure. I'll make a fix.", "commid": "kubernetes_issue_1101", "tokennum": 45}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4a463cc9ace21224e50a746e19e16b06fa6d6577f395c0e3f196e0019985b947", "query": "} func IsMirrorPod(pod *api.Pod) bool { <del> if value, ok := pod.Annotations[kubetypes.ConfigMirrorAnnotationKey]; !ok { return false } else { return value == kubetypes.MirrorType } </del> <ins> _, ok := pod.Annotations[kubetypes.ConfigMirrorAnnotationKey] return ok } func getHashFromMirrorPod(pod *api.Pod) (string, bool) { hash, ok := pod.Annotations[kubetypes.ConfigMirrorAnnotationKey] return hash, ok } func getPodHash(pod *api.Pod) string { // The annotation exists for all static pods. return pod.Annotations[kubetypes.ConfigHashAnnotationKey] </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-8bc8d69d49aedfb4a9bf3991de80f7c339e96bfbefe5b1f250dae70fa0393729", "text": "See for more context. Currently, kubelet compares the spec of a mirror pod (created via apiserver) with that of a static pod (config stored as a file) to decide whether the two are considered identical. If they differ, kubelet would delete the mirror pod and re-create it with the correct spec. Due to the fact that apiserver may set default values for some fields in the spec of the mirror pod, the specs could deviate undesirably. To avoid problems like this, we can store the config of a static pod as an annotation in the mirror pod, and compare the static pod with the annotation.\nWould a hash of the config be sufficient if we're only going to compare? The whole spec would generally be more useful, but I wonder if that is too much data to put in an annotation.\nThis seems totally reasonable to me, but I'm still desperately curious why you can't just bypass defaulting when you generate mirror pod from static pod? (i.e. just use the static pod's configuration verbatim)\nIt's not kubelet who applies the default values here. The admission plugin was only run at the apiserver, and to bypass that, you have to ask apiserver to treat mirror pods differently and potentially at multiple places.\nOn May 22, 2015 10:38 AM, \"Yu-Ju Hong\" wrote: Understood, but is it really multiple places? If so then I agree it's a bad idea. Otherwise it might be worth considering as an alternative.\nIt's untenable for Kubelet to assume to know/circumvent all fields that will be set by other entities: admission control, defaulting, late initialization, auto-something, whatever. It needs to obey the same rules as other clients.\nI don't understand why you would ever want to apply any of the things you mentioned to static pods. Static pods should be copied verbatim into the mirror pods, right? That's what I'm proposing.\nWhat if the master is updated before the kubelet, and the master adds a new API field with a default value?\nThat case should be discussed in\nI agree that mirror pod should reflect the true status of the static pod running on the node, and no default values should be set in this case.", "commid": "kubernetes_issue_8683", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4a463cc9ace21224e50a746e19e16b06fa6d6577f395c0e3f196e0019985b947", "query": "} func IsMirrorPod(pod *api.Pod) bool { <del> if value, ok := pod.Annotations[kubetypes.ConfigMirrorAnnotationKey]; !ok { return false } else { return value == kubetypes.MirrorType } </del> <ins> _, ok := pod.Annotations[kubetypes.ConfigMirrorAnnotationKey] return ok } func getHashFromMirrorPod(pod *api.Pod) (string, bool) { hash, ok := pod.Annotations[kubetypes.ConfigMirrorAnnotationKey] return hash, ok } func getPodHash(pod *api.Pod) string { // The annotation exists for all static pods. return pod.Annotations[kubetypes.ConfigHashAnnotationKey] </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-0491e123884f0f20f50d0a788bca7a6a29e2fa08227703a00221ecbd3bcf483c", "text": "However, I think it'd be harder to implement this way since, as stated above, that there are many things to circumvent in the apiserver itself. It could also be harder to keep this special case from being broken by a yet another new feature/plugin. Keeping the hash of the config in the annotation seems like a good compromise even though it may not reflect the true status 100% accurately. I think this is acceptable. What do you think?\nSure, if you think the annotation approach is easier, I would go with that. I guess in the case Brian mentoined (master adds a new API field with a default value), you would not update the mirror pod, because the static pod definition has not changed?\nYes, a hash would be sufficient.\nIt shouldn't be necessary to update the mirror pod in the case that a new default field was updated, because that field should be populated automatically by the apiserver on decode from etcd.\nWe should fix this so we don't have this problem again in 1.2.", "commid": "kubernetes_issue_8683", "tokennum": 226}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4aabeea88085eabb28ec0e920cb515888b245de7eb3973ad8ab11b3622fda32d", "query": "tester(unconfined) }) <del> By(\"Running a CAP_SYS_ADMIN pod\", func() { </del> <ins> By(\"Running a SYS_ADMIN pod\", func() { </ins> sysadmin := restrictedPod(f, \"sysadmin\") sysadmin.Spec.Containers[0].SecurityContext.Capabilities = &v1.Capabilities{ <del> Add: []v1.Capability{\"CAP_SYS_ADMIN\"}, </del> <ins> Add: []v1.Capability{\"SYS_ADMIN\"}, </ins> } sysadmin.Spec.Containers[0].SecurityContext.AllowPrivilegeEscalation = nil tester(sysadmin)", "positive_passages": [{"docid": "doc-en-kubernetes-ff21ac8c2a6c2ea4821e58492f0a8553d8a302a4afa86e4805bd139290e21fea", "text": "The pod security policy capability test is using wrong CAP format with prefix. In our document, we explicitly say: It fails for cri-containerd. I'll find out why it doesn't fail for Docker, maybe docker has handled it. But we should fix the test anyway.\nThere are no sig labels on this issue. Please add a sig label. <detailsA sig label can be by either: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. See the . The in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals 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", "commid": "kubernetes_issue_58901", "tokennum": 197}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4ac1789d15c9419586df0270849f9592bfa2acb618bdad2a9dd1d909b1965f5f", "query": "// General settings. fs.StringVar(&s.ContainerRuntime, \"container-runtime\", s.ContainerRuntime, \"The container runtime to use. Possible values: 'docker', 'remote'.\") fs.StringVar(&s.RuntimeCgroups, \"runtime-cgroups\", s.RuntimeCgroups, \"Optional absolute name of cgroups to create and run the runtime in.\") <del> _ = fs.Bool(\"redirect-container-streaming\", false, \"[REMOVED]\") // TODO: Delete in v1.22 fs.MarkDeprecated(\"redirect-container-streaming\", \"Container streaming redirection has been removed from the kubelet as of v1.20, and this flag will be removed in v1.22. For more details, see http://git.k8s.io/enhancements/keps/sig-node/20191205-container-streaming-requests.md\") </del> // Docker-specific settings. fs.StringVar(&s.DockershimRootDirectory, \"experimental-dockershim-root-directory\", s.DockershimRootDirectory, \"Path to the dockershim root directory.\")", "positive_passages": [{"docid": "doc-en-kubernetes-2a143cea40d48fac7382a327617b071e2fea640f42b4cdcb181da1800ffddc19", "text": "[ ] OWNERSALIASES:581: # conformance aliases [x] // More info: ~~ [x] // See [x] fs.MarkDeprecated(\"redirect-container-streaming\", \"Container streaming redirection has been removed from the kubelet as of v1.20, and this flag will be removed in v1.22. For more details, see \") [x] // More info: [x] // More info: ~~ [x] [x] [x] CHANGELOG/CHANGELOG-[scalability validation report]: ~~ [x] ALPHA stability level ) [x] ALPHA stability level ) [x] ALPHA stability level ) [x] ALPHA stability level ) [x] ALPHA stability level ) [x] ALPHA stability level ) [x] ALPHA stability level ) [x] ALPHA stability level ) [x] ALPHA stability level ) [x] ALPHA stability level ) [x] ALPHA stability level ) [x] ALPHA stability level ) [ ] link: [ ] link: Some needs to be regenerated\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/help\n/kind documentation\n/remove-kind bug\n/good-first-issue\n/assign I shall fix .\n/assign i'm working in\ni have create a pr for\ni see , you need\n/assign fixing\n/assign\n/assign CHANGELOG/CHANGELOG-\n/assign CHANGELOG/CHANGELOG- Edit : Link is already resolved, unassigning\n/assign CHANGELOG/CHANGELOG-\n/assign ,111\nSorry, already assigned\n/assign i will take\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n  is merged. Most KEP links are fixed. You may scan it again. fixed most of them.\n/sig architecture\n/assign I will work on and\n/remove-help", "commid": "kubernetes_issue_101008", "tokennum": 498}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4ac4e34c87528e1ca8b8b357633248223dfb4817110ad07d736f87c33a24b028", "query": "concurrencyLimit:            6, evalDuration:                time.Second * 20, expectedFair:                []bool{true}, <del> expectedFairnessMargin:      []float64{0.15}, </del> <ins> expectedFairnessMargin:      []float64{0.155}, </ins> expectAllRequests:           true, evalInqueueMetrics:          true, evalExecutingMetrics:        true,", "positive_passages": [{"docid": "doc-en-kubernetes-9989a24ad22361651b9b153ae59f4b05a7f4d39865c45b98092f106c43ae9e01", "text": "pull-kubernetes-unit TestDifferentWidths As far back as triage board history shows No response /sig api-machinery\n/cc /triage accepted\nThe 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]:\nThe 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]:\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_106579", "tokennum": 521}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4ac4e34c87528e1ca8b8b357633248223dfb4817110ad07d736f87c33a24b028", "query": "concurrencyLimit:            6, evalDuration:                time.Second * 20, expectedFair:                []bool{true}, <del> expectedFairnessMargin:      []float64{0.15}, </del> <ins> expectedFairnessMargin:      []float64{0.155}, </ins> expectAllRequests:           true, evalInqueueMetrics:          true, evalExecutingMetrics:        true,", "positive_passages": [{"docid": "doc-en-kubernetes-c8c180b3e6dad8fab04f5f208d5a3b3aff8479bb3125ba5ea96ea97ccc2bab4f", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nRunning into this one a fair bit in my PRs, opened as a possible fix\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue with Mark this issue as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close not-planned [1]:\nClosing this issue, marking it as \"Not Planned\". <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue with Mark this issue as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen I got this in --\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue with Mark this issue as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at .", "commid": "kubernetes_issue_106579", "tokennum": 504}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4ac4e34c87528e1ca8b8b357633248223dfb4817110ad07d736f87c33a24b028", "query": "concurrencyLimit:            6, evalDuration:                time.Second * 20, expectedFair:                []bool{true}, <del> expectedFairnessMargin:      []float64{0.15}, </del> <ins> expectedFairnessMargin:      []float64{0.155}, </ins> expectAllRequests:           true, evalInqueueMetrics:          true, evalExecutingMetrics:        true,", "positive_passages": [{"docid": "doc-en-kubernetes-6804092b9f9f291bd1b3f24d906e3547bfaa841487790436e20f51d6b5e5c17d", "text": "/close not-planned [1]:\nClosing this issue, marking it as \"Not Planned\". <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue with Mark this issue as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen Got this in\nReopened this issue. <detailsIn response to : /reopen Got this in </details\n/remove-lifecycle rotten", "commid": "kubernetes_issue_106579", "tokennum": 174}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4ae791cacef4332c0d3c2eb861ba88852692666561204eacb1a96b711857d3c7", "query": "return hist.GetSampleSum() / float64(hist.GetSampleCount()) } <del> // Clear clears all fields of the wrapped histogram func (hist *Histogram) Clear() { if hist.SampleCount != nil { *hist.SampleCount = 0 } if hist.SampleSum != nil { *hist.SampleSum = 0 } for _, b := range hist.Bucket { if b.CumulativeCount != nil { *b.CumulativeCount = 0 } } } </del> // Validate makes sure the wrapped histogram has all necessary fields set and with valid values. func (hist *Histogram) Validate() error { if hist.SampleCount == nil || hist.GetSampleCount() == 0 {", "positive_passages": [{"docid": "doc-en-kubernetes-43f40e78041c5b4f7b71fe448bfb25306103aa8e8278b5a81de2f92cd8b688c4", "text": "In the new scheduler performance testing framework, (bool) is provided to benchmark performance of pods created in an \"operator\": (L11 below) However, the initialized Pods created in L5~L7 seem to be also benchmarked, although it doesn't specify . (please see the reproduce steps below). I think it's b/c once scheduler starts, the associated Prometheus artifacts are also up, and it's a single in-memory datastore. So no matter we start to collect the metric in which step, the prometheus data is already up-to-date. In the above workload config, the final data have benchmarked 1500 pods instead of 1000 pods. I guess it won't work either if running in the pod initialization step or not. Unless we manage a breakpoint at the end of each step, and calculate delta histogram for the step that specifies . Pods created in step without are not benchmarked. Apply the following diff: And then run: You will get an output sth. like: /sig scheduling\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nCould you please help confirm if it's an issue?\ncc\nUnfortunately, does not apply for metrics gathered from . As you mentioned. The default gatherer collects all metrics produced by the scheduler. It's the scheduler itself who knows pod specs and would have to decide which pods will get ignored when updating metrics. The question is if computing metrics for a subset of pods processed by the scheduler is a valid use case.\nThis is probably what we want. Is something like that possible ?\nI think being able to absolutely ignore certain pods for metrics is an overkill.\nThe use case is to ignore the pods created in steps that don't specify , so as to collect the Pod metrics create at particular step(s) (). Otherwise, the semantics of option is quite misleading. Nope, that's not the intention. We don't need to target certain pods, like using label selector or whatever. Just as I mentioned, measure pods created at particular steps.", "commid": "kubernetes_issue_99218", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4ae791cacef4332c0d3c2eb861ba88852692666561204eacb1a96b711857d3c7", "query": "return hist.GetSampleSum() / float64(hist.GetSampleCount()) } <del> // Clear clears all fields of the wrapped histogram func (hist *Histogram) Clear() { if hist.SampleCount != nil { *hist.SampleCount = 0 } if hist.SampleSum != nil { *hist.SampleSum = 0 } for _, b := range hist.Bucket { if b.CumulativeCount != nil { *b.CumulativeCount = 0 } } } </del> // Validate makes sure the wrapped histogram has all necessary fields set and with valid values. func (hist *Histogram) Validate() error { if hist.SampleCount == nil || hist.GetSampleCount() == 0 {", "positive_passages": [{"docid": "doc-en-kubernetes-a8b513dba6e655a29138693e1746ea6f16e628420cb4b4aca138e84f0ed453fc", "text": "I would do something like the following: if a step has collectMetrics:false, we wait for them to finish scheduling, and then we take a snapshot of the histogram. Then for the next step that has collectMetrics:true, we take the diff with the latest snapshot to report the results. This might not be perfect, as we don't control if the metrics have finished syncing when we take the snapshot. But I think that's fine. Would doing this be possible? Now, if we have steps that run in parallel, one with collectMetrics:false and another with collectMetrics:true, then this doesn't work. Note that I don't know the details of how the gatherer works.\nThat adheres to what I have in my mind - we can only manage this on client side. I think it's fine. As we are already fetching the \"snapshot\" when pods get scheduled when equals true. True. An alternative is to design the case to be like: the step with to employ Pods that are all unschedulable, and then specify a custom metric \"schedulere2eschedulingdurationseconds[result=\"unschedulable\"]\" to target a particular histogram instead of all histograms (default option) inside a histogramVec. Note this can only be possible when and some subsequent changes get in place.\nWe might just call Histogram.Clear() method which will clear what has been collected so far at the end of phase: Assuming individual phases have no pods in common and each phase can clear metrics without affecting other phases. Though, as said, it will work only for serial case.\nWDYT\nI'm afraid doesn't work. That was my initial thought as well, but no luck. I guess it's b/c, theoretically, we cannot reset a metric on the server side - Promoetheus' model doesn't support this. But let me know if I miss anything.\nThe performance tests assume all the metrics all gathered and accessed in the same binary. As long as that's the case, works.", "commid": "kubernetes_issue_99218", "tokennum": 457}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4ae791cacef4332c0d3c2eb861ba88852692666561204eacb1a96b711857d3c7", "query": "return hist.GetSampleSum() / float64(hist.GetSampleCount()) } <del> // Clear clears all fields of the wrapped histogram func (hist *Histogram) Clear() { if hist.SampleCount != nil { *hist.SampleCount = 0 } if hist.SampleSum != nil { *hist.SampleSum = 0 } for _, b := range hist.Bucket { if b.CumulativeCount != nil { *b.CumulativeCount = 0 } } } </del> // Validate makes sure the wrapped histogram has all necessary fields set and with valid values. func (hist *Histogram) Validate() error { if hist.SampleCount == nil || hist.GetSampleCount() == 0 {", "positive_passages": [{"docid": "doc-en-kubernetes-c977cd9286b4a197ec98b02fe65342de07359c1835b69599916b95554e8a5e53", "text": "We already call in the code:\nThat was my understanding as well, but no luck :( Here is a diff to call in case when \"concreteOp.CollectMetrics\" is false: <details<summaryDiff:</summary<p</p</detailsAnd below is the output - it's still 1500 (500 init pods plus 1000 measured pods) instead of 1000 being benchmarked: <details<summaryOutput:</summary<p</p</details\nAlso, if you run the tests and together, the result proves doesn't work as expected:\nBut I do find a way to fix this: .", "commid": "kubernetes_issue_99218", "tokennum": 136}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4b0d00672ecbaad6257a8258690a3181bf4d24c579e619c1eb7ea698f701730e", "query": "<ins> /* Copyright 2019 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package runtime import ( \"testing\" \"k8s.io/apimachinery/pkg/runtime/schema\" ) func gv(group, version string) schema.GroupVersion { return schema.GroupVersion{Group: group, Version: version} } func gvk(group, version, kind string) schema.GroupVersionKind { return schema.GroupVersionKind{Group: group, Version: version, Kind: kind} } func gk(group, kind string) schema.GroupKind { return schema.GroupKind{Group: group, Kind: kind} } func TestCoercingMultiGroupVersioner(t *testing.T) { testcases := []struct { name           string target         schema.GroupVersion preferredKinds []schema.GroupKind kinds          []schema.GroupVersionKind expectKind     schema.GroupVersionKind }{ { name:           \"matched preferred group/kind\", target:         gv(\"mygroup\", \"__internal\"), preferredKinds: []schema.GroupKind{gk(\"mygroup\", \"Foo\"), gk(\"anothergroup\", \"Bar\")}, kinds:          []schema.GroupVersionKind{gvk(\"yetanother\", \"v1\", \"Baz\"), gvk(\"anothergroup\", \"v1\", \"Bar\")}, expectKind:     gvk(\"mygroup\", \"__internal\", \"Bar\"), }, { name:           \"matched preferred group\", target:         gv(\"mygroup\", \"__internal\"), preferredKinds: []schema.GroupKind{gk(\"mygroup\", \"\"), gk(\"anothergroup\", \"\")}, kinds:          []schema.GroupVersionKind{gvk(\"yetanother\", \"v1\", \"Baz\"), gvk(\"anothergroup\", \"v1\", \"Bar\")}, expectKind:     gvk(\"mygroup\", \"__internal\", \"Bar\"), }, { name:           \"no preferred group/kind match, uses first kind in list\", target:         gv(\"mygroup\", \"__internal\"), preferredKinds: []schema.GroupKind{gk(\"mygroup\", \"\"), gk(\"anothergroup\", \"\")}, kinds:          []schema.GroupVersionKind{gvk(\"yetanother\", \"v1\", \"Baz\"), gvk(\"yetanother\", \"v1\", \"Bar\")}, expectKind:     gvk(\"mygroup\", \"__internal\", \"Baz\"), }, } for _, tc := range testcases { t.Run(tc.name, func(t *testing.T) { v := NewCoercingMultiGroupVersioner(tc.target, tc.preferredKinds...) kind, ok := v.KindForGroupVersionKinds(tc.kinds) if !ok { t.Error(\"got no kind\") } if kind != tc.expectKind { t.Errorf(\"expected %#v, got %#v\", tc.expectKind, kind) } }) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-7ee140198c665b218e0dfb7e3cd2f2624912887cfcfab5f30828d12c6130aa35", "text": "What happened: Set up a HA cluster with 1.9 and 1.10 API servers (occurs on any apiserver skew boundary where a cohabitating resource's storage version changed groups) Observed errors when modifying workload objects: when modified via the 1.10 server, saw this error in the 1.9 server: when modified via the 1.9 server, saw this error in the 1.10 server: When this error was encountered, all watchers for the resource in question would be dropped and have to re-establish, and the internal watchers feeding the watch cache would drop and re-establish What you expected to happen: Watch events from all supported storage versions are processed correctly How to reproduce it (as minimally and precisely as possible): Start a server from master (for inspectability, store in json). With Create a deployment (e.g. kube-dns in kube-system) Establish a watch via extensions (kubectl get deployments.extensions --all-namespaces -w) Establish a watch via apps (kubectl get --all-namespaces -w) Tail the kube-apiserver log Change the apps/v1 deployment in etcd to extensions/v1beta1: Observer client watches drop and server log errors: Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: /sig api-machinery /cc /priority critical-urgent\nerror is triggered by this returning false: constructed here: the info about expected cohabitating groups is not included in the list of acceptable inputs", "commid": "kubernetes_issue_73478", "tokennum": 368}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4b43493298e864b0538e6ba916c0e165cc63d8d3f533cc6b270f3956b1e6727b", "query": "<del> v1.8.3-3 </del> <ins> v1.9.1-1 </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-1b1e05089c93c6eb59b848626d58302483d33d2f2e5531ac5b621da204277493", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind feature This is a followup on , but for Go 1.9 We should do the same kind of testing now to possibly catch bugs in either Go or Kubernetes when doing this kind of dependency version bump. Ideally we'd have automated tests against Go tip (), but we don't have that at the moment, so we have to do it kind of manually. We should also decide which k8s version we should target. k8s v1.8 or v1.9? What Go versions have been used so far? Kubernetes v1.7.0 - go1.8.3 Kubernetes v1.6.0 - go1.7.5 Kubernetes v1.5.0 - go1.7.4 Kubernetes v1.4.0 - go1.6.3 Kubernetes v1.3.0 - go1.6.2 Kubernetes v1.2.0 - go1.4.2 Seems like the trend has been to stay on the same Go version for two releases and then bump. That'd mean we'd switch to Go1.9 in k8s v1.9 Everyone happy with that? Or is there any reason for us to go start using go1.9 in k8s v1.8? In any case, we should indeed start testing go1.9 out now... cc\nLet me know if you find any bugs\nFWIW pretty tight to code-freeze I would prefer punting out a cycle fwiw.\nI don't think we're that close to code freeze given that we have 5 (of 8) weeks left in this coding cycle But I'm happy to defer this to v1.9 if others think that. I guess the main reason for a bump would be scalability goals, but I'm not sure we have the need to expand above 5000 (and that Go would be the bottleneck in that case) for v1.8\nmade the Go benchmarks 9% faster with 15% larger binaries. I'm interested to see how that affects our numbers.\nmid-stack inlining was not included in Go 1.9. It made the compiler too slow. It's being targeted to Go 1.10 now instead, after some compiler optimization work.\nOh, thanks for the correction!", "commid": "kubernetes_issue_49484", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4b43493298e864b0538e6ba916c0e165cc63d8d3f533cc6b270f3956b1e6727b", "query": "<del> v1.8.3-3 </del> <ins> v1.9.1-1 </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-018b01245292fe1977b7eec8bea53846947ed737ea149d849054911d63924f58", "text": "Regardless, we need to run the scalability tests against the RC so we can report issues earlier-- the last upgrade was particularly painful because of an HTTP regression that we caught way too late.\nyeah. I filed for that now\nyeah, my recollection is that the Go releases usually occur too late in our release cadence and end up getting bumped to the next Kubernetes release. (Also we inevitably find something wrong, though testing RCs would help with that. Though I'm not sure anyone has cycles to test RCs and fix all of the issues that do come up.)\nBased on our current time frame, it looks like go1.9 support will have to slip to k8s 1.9. is open to dig into and start things testing, but there's a number of things that have to move.. I'll try to document those this time around to help with future go version bumps. So far: bazel build rules needed to be updated to support go1.9 () bazel version possibly needs to be updated? some of our custom bazel rules broke\nWhen done, we should update this:\n/priority important-soon\nUpdating the dependency is blocked pending bazel 0.6.0 - .\nCan we upgrade to 0.6.0 now? Does bazel 0.6.0 have multiarch support btw?\nWe can't update to depend on bazel 0.6.0+ until we can figure out how to support different versions of the bazelbuild and kubekins-e2e images in PR jobs in prow based on what branch is being tested. cc\nNoting that we're working on branching jobs, is testing one option here:\n[MILESTONENOTIFIER] Milestone Issue Current <details open<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts. : New functionality.", "commid": "kubernetes_issue_49484", "tokennum": 416}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4b43493298e864b0538e6ba916c0e165cc63d8d3f533cc6b270f3956b1e6727b", "query": "<del> v1.8.3-3 </del> <ins> v1.9.1-1 </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-69273b286facac9ab246a3deb71fa6e24d55618a503d411a1618742e8a027c28", "text": "</details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details\nI approved this for v1.9, this is something we definitely want in order to keep up with Go (and for improved performance)\nwe're starting to use the forked images now /cc this should be more feasible very soon Edit: test-infra jobs have also been using bazel 0.6 (now 0.6.1) / a recent rules_go to soak things a bit\nWe've identified a failing test as a result of the WIP PR to upgrade the codebase to go1.9: The admission webhook test fails with certificate errors under go1.9.1, but runs successfully under go1.8.3. cc: who wanted to be alerted to potential bugs\n- please see for a possible fix", "commid": "kubernetes_issue_49484", "tokennum": 212}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4b575b1c0df097d3d6bbe8f23323aa3c062c69815f9ca6c1e1d569975ca2c8d1", "query": "configs[CheckMetadataConcealment] = Config{e2eRegistry, \"metadata-concealment\", \"1.2\"} configs[CudaVectorAdd] = Config{e2eRegistry, \"cuda-vector-add\", \"1.0\"} configs[CudaVectorAdd2] = Config{e2eRegistry, \"cuda-vector-add\", \"2.0\"} <del> configs[DebianIptables] = Config{buildImageRegistry, \"debian-iptables\", \"buster-v1.4.0\"} </del> <ins> configs[DebianIptables] = Config{buildImageRegistry, \"debian-iptables\", \"buster-v1.5.0\"} </ins> configs[EchoServer] = Config{e2eRegistry, \"echoserver\", \"2.2\"} configs[Etcd] = Config{gcRegistry, \"etcd\", \"3.4.13-0\"} configs[GlusterDynamicProvisioner] = Config{dockerGluster, \"glusterdynamic-provisioner\", \"v1.0\"}", "positive_passages": [{"docid": "doc-en-kubernetes-ee0826757468ea334f95c77509b257c3d392b6713b4311ba7afa125d642dcec9", "text": "The based container images for are shipped with the wrong architecture within the manifest if not amd64: Refers to We updated the images a few minutes ago to buster-v1.3.0, which are now ready to be used as base for the multi-architecture images. If the images contain the right architectures, then it may magically happen that the kube-proxy images are fixed, too. This is because we already use the build syntax for it: /cc\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig release", "commid": "kubernetes_issue_98229", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4b7e244a4f69988927b9915fb273c3f6cc12556416d4c786818fa2576f74ffb8", "query": "}, }, }, <ins> { name: \"node port service with protocol sctp on a node with multiple nodeIPs\", services: []*v1.Service{ makeTestService(\"ns1\", \"svc1\", func(svc *v1.Service) { svc.Spec.Type = \"NodePort\" svc.Spec.ClusterIP = \"10.20.30.41\" svc.Spec.Ports = []v1.ServicePort{{ Name:     \"p80\", Port:     int32(80), Protocol: v1.ProtocolSCTP, NodePort: int32(3001), }} }), }, endpoints: []*v1.Endpoints{ makeTestEndpoints(\"ns1\", \"svc1\", func(ept *v1.Endpoints) { ept.Subsets = []v1.EndpointSubset{{ Addresses: []v1.EndpointAddress{{ IP: \"10.180.0.1\", }}, Ports: []v1.EndpointPort{{ Name: \"p80\", Port: int32(80), }}, }} }), }, nodeIPs: []net.IP{ net.ParseIP(\"100.101.102.103\"), net.ParseIP(\"100.101.102.104\"), net.ParseIP(\"100.101.102.105\"), net.ParseIP(\"2001:db8::1:1\"), net.ParseIP(\"2001:db8::1:2\"), net.ParseIP(\"2001:db8::1:3\"), }, nodePortAddresses: []string{}, expectedIPVS: &ipvstest.FakeIPVS{ Services: map[ipvstest.ServiceKey]*utilipvs.VirtualServer{ { IP:       \"10.20.30.41\", Port:     80, Protocol: \"SCTP\", }: { Address:   net.ParseIP(\"10.20.30.41\"), Protocol:  \"SCTP\", Port:      uint16(80), Scheduler: \"rr\", }, { IP:       \"100.101.102.103\", Port:     3001, Protocol: \"SCTP\", }: { Address:   net.ParseIP(\"100.101.102.103\"), Protocol:  \"SCTP\", Port:      uint16(3001), Scheduler: \"rr\", }, { IP:       \"100.101.102.104\", Port:     3001, Protocol: \"SCTP\", }: { Address:   net.ParseIP(\"100.101.102.104\"), Protocol:  \"SCTP\", Port:      uint16(3001), Scheduler: \"rr\", }, { IP:       \"100.101.102.105\", Port:     3001, Protocol: \"SCTP\", }: { Address:   net.ParseIP(\"100.101.102.105\"), Protocol:  \"SCTP\", Port:      uint16(3001), Scheduler: \"rr\", }, { IP:       \"2001:db8::1:1\", Port:     3001, Protocol: \"SCTP\", }: { Address:   net.ParseIP(\"2001:db8::1:1\"), Protocol:  \"SCTP\", Port:      uint16(3001), Scheduler: \"rr\", }, { IP:       \"2001:db8::1:2\", Port:     3001, Protocol: \"SCTP\", }: { Address:   net.ParseIP(\"2001:db8::1:2\"), Protocol:  \"SCTP\", Port:      uint16(3001), Scheduler: \"rr\", }, { IP:       \"2001:db8::1:3\", Port:     3001, Protocol: \"SCTP\", }: { Address:   net.ParseIP(\"2001:db8::1:3\"), Protocol:  \"SCTP\", Port:      uint16(3001), Scheduler: \"rr\", }, }, Destinations: map[ipvstest.ServiceKey][]*utilipvs.RealServer{ { IP:       \"10.20.30.41\", Port:     80, Protocol: \"SCTP\", }: { { Address: net.ParseIP(\"10.180.0.1\"), Port:    uint16(80), Weight:  1, }, }, { IP:       \"100.101.102.103\", Port:     3001, Protocol: \"SCTP\", }: { { Address: net.ParseIP(\"10.180.0.1\"), Port:    uint16(80), Weight:  1, }, }, { IP:       \"100.101.102.104\", Port:     3001, Protocol: \"SCTP\", }: { { Address: net.ParseIP(\"10.180.0.1\"), Port:    uint16(80), Weight:  1, }, }, { IP:       \"100.101.102.105\", Port:     3001, Protocol: \"SCTP\", }: { { Address: net.ParseIP(\"10.180.0.1\"), Port:    uint16(80), Weight:  1, }, }, { IP:       \"2001:db8::1:1\", Port:     3001, Protocol: \"SCTP\", }: { { Address: net.ParseIP(\"10.180.0.1\"), Port:    uint16(80), Weight:  1, }, }, { IP:       \"2001:db8::1:2\", Port:     3001, Protocol: \"SCTP\", }: { { Address: net.ParseIP(\"10.180.0.1\"), Port:    uint16(80), Weight:  1, }, }, { IP:       \"2001:db8::1:3\", Port:     3001, Protocol: \"SCTP\", }: { { Address: net.ParseIP(\"10.180.0.1\"), Port:    uint16(80), Weight:  1, }, }, }, }, expectedIPSets: netlinktest.ExpectedIPSet{ kubeNodePortSetSCTP: { { IP:       \"100.101.102.103\", Port:     3001, Protocol: strings.ToLower(string(v1.ProtocolSCTP)), SetType:  utilipset.HashIPPort, }, { IP:       \"100.101.102.104\", Port:     3001, Protocol: strings.ToLower(string(v1.ProtocolSCTP)), SetType:  utilipset.HashIPPort, }, { IP:       \"100.101.102.105\", Port:     3001, Protocol: strings.ToLower(string(v1.ProtocolSCTP)), SetType:  utilipset.HashIPPort, }, { IP:       \"2001:db8::1:1\", Port:     3001, Protocol: strings.ToLower(string(v1.ProtocolSCTP)), SetType:  utilipset.HashIPPort, }, { IP:       \"2001:db8::1:2\", Port:     3001, Protocol: strings.ToLower(string(v1.ProtocolSCTP)), SetType:  utilipset.HashIPPort, }, { IP:       \"2001:db8::1:3\", Port:     3001, Protocol: strings.ToLower(string(v1.ProtocolSCTP)), SetType:  utilipset.HashIPPort, }, }, }, }, </ins> } for _, test := range tests {", "positive_passages": [{"docid": "doc-en-kubernetes-dd58629e743b6e4eeaad6ce708921acac15734ca4e62ad8f92d2c296b406f940", "text": "What happened: SCTP nodeport service is not working for all IPs present in the node when ipvs is enabled. It is working only for node's InternalIP. What you expected to happen: SCTP nodeport service must work for all ips present in the node when ipvs is enabled. How to reproduce it (as minimally and precisely as possible): Create a kubernetes cluster with at least one node having multiple interfaces with different IPs. Start an SCTP server deployment. Then create a nodeport service for the same. Now try to reach the service using all the IPs present in that node. The service will be accessible only via node's InternalIP not any other IPs. Environment: Kubernetes version: v1.15.2 OS: ubuntu 18.04 Kernel: 4.15.0-54-generic Network plugin and version (if this is a network-related bug): ipset version v6.34\n/sig network /area kube-proxy /area ipvs\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/remove-triage unresolved", "commid": "kubernetes_issue_81474", "tokennum": 251}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4baabd3b0850d356278c598613dfd94ed7ea2eeb31a45735bb0a9d84ac12a444", "query": "// The application protocol for this port. // This field follows standard Kubernetes label syntax. // Un-prefixed names are reserved for IANA standard service names (as per <del> // RFC-6335 and http://www.iana.org/assignments/service-names). </del> <ins> // RFC-6335 and https://www.iana.org/assignments/service-names). </ins> // Non-standard protocols should use prefixed names such as // mycompany.com/my-custom-protocol. // +optional", "positive_passages": [{"docid": "doc-en-kubernetes-3e7e95e6f142ca39e6e3ca0b78c3932bd6cbdfdc898eed9d3ffda27d28f904c7", "text": "We should make the change in PR API reference links to should use HTTPS, not HTTP Visit h and look at the IANA hyperlinks Once this fix is made, a PR to is needed to update the docs (by autogenerating them). This typically would be deferred until the next Kubernetes release. v1.23 not applicable not applicable not applicable not applicable not applicable\n/sig docs\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI opened this issue so that someone else can open a new PR that is equivalent to .\n/retitle Update links to IANA for Service Name and Transport Protocol Port Number Registry\nI would like to work on this issue. May I assign it to myself?\nAnyone - including you - is welcome to work on this issue! So long as you've you can open a pull request to propose a fix.\nThanks\n/assign\nI have made the PR. I hope this works. If not then will be happy to do the necessary changes.\nHad to close the previous PR because of issues, here is the new one I made.", "commid": "kubernetes_issue_106980", "tokennum": 300}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4bb9d79fd048482eaecc5f7b756e34b0dbbbd4b13e8aa133619f7ccf0277763a", "query": "&unversioned.APIGroup{}, &unversioned.APIResourceList{}, ) <ins> addDeepCopyFuncs(scheme) addDefaultingFuncs(scheme) addConversionFuncs(scheme) </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-5056a2515a29befdf589a74f13db031ed4142bbabfa8d2c37cafac2de4fccaea", "text": "I started the federation-apiserver and went to and got the following output: Expected: I should have got an empty v1.ServiceList Any idea on what we are doing wrong? Have you guys seen this error?\nI think your deep copiers or conversion functions are not getting registered properly. If you look at my change in , some places are inappropriately registering with api.Scheme instead of the passed in scheme. Maybe you have that problem or a similar one, since I think you guys copied some code. , Nikhil Jindal wrote:\nDeep copy generation was slightly broken as well - you may want to double check that they are registered. On May 23, 2016, at 5:50 PM, Daniel Smith wrote: I think your deep copiers or conversion functions are not getting registered properly. If you look at my change in , some places are inappropriately registering with api.Scheme instead of the passed in scheme. Maybe you have that problem or a similar one, since I think you guys copied some code. , Nikhil Jindal wrote: \u2014 You are receiving this because you are on a team that was mentioned. Reply to this email directly or view it on GitHub\nI got the same error with latest branch, as I was swamping on service controller, so I use a previous version and worked around it.\ndeep copies were indeed missing, but adding them hasnt fixed the issue. Will debug more. is my PR to add the deep copies cc Please feel free to file issues for any such problem you face. We need to fix all these issues. Its good if we know about them early. Thanks!\nfixes this", "commid": "kubernetes_issue_26111", "tokennum": 335}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4bd3c10f50921f43ea241e2b545dd52d2ab01b190e331de52244a9b23fab90db", "query": "for format := range columnsFormats { formats = append(formats, format) } <ins> sort.Strings(formats) </ins> return formats }", "positive_passages": [{"docid": "doc-en-kubernetes-38c129cdce20cdb2ede95770ab1d3483b461da6e2945915e074275e9575e4c1c", "text": "Similar to issue , building kubernetes1.23 resulted in 1 variation: builds should be fully determined by inputs on openSUSE or Debian, This bug was found while working on . <details23.0 </details<details</details<details</details<details</details<details</details<details</details\n/sig release /area build-release\n/assign\n/sig cli\n/triage accepted /assign", "commid": "kubernetes_issue_108245", "tokennum": 94}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4c3650be7443d76937fb70b3060eb20d8426b67cac17490194f6232b9aacd28c", "query": "// compute the context. Mutation is allowed. ValidatedPSPAnnotation is not taken into account. allowedPod, pspName, validationErrs, err := p.computeSecurityContext(ctx, a, pod, true, \"\") if err != nil { <del> return admission.NewForbidden(a, err) </del> <ins> return admission.NewForbidden(a, fmt.Errorf(\"PodSecurityPolicy: %w\", err)) </ins> } if allowedPod != nil { *pod = *allowedPod", "positive_passages": [{"docid": "doc-en-kubernetes-d654f914f6cdd0bd3bce5db6eb3c4ebef631bd8d2558ac9d591cab12ba724061", "text": "What happened: e2e tests detect whether PSP is enabled based on presence of PSP API objects. An addon that proactively includes a PSP in a manifest can trigger that detection and enable PSP-specific e2e tests that should not be run. What you expected to happen: In addition to detecting presence of PSP objects, consider dry-run creating a pod and verifying the annotation indicating the selected PSP policy is , indicating the admission plugin is active. /sig auth /assign", "commid": "kubernetes_issue_91463", "tokennum": 109}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4cab9d7b1f7e85ed0efcefa5a7a55063ccdf0209851fbed5d9c9e4f78193719c", "query": "\"k8s.io/apimachinery/pkg/types\" \"k8s.io/apimachinery/pkg/util/managedfields\" \"k8s.io/apimachinery/pkg/watch\" <del> \"k8s.io/kube-openapi/pkg/validation/spec\" </del> \"k8s.io/utils/ptr\" )", "positive_passages": [{"docid": "doc-en-kubernetes-29db4d0749071d4e54a9083e12a93fb8b6b43cd54c28626ec2efc45861483a16", "text": "Smoke tests run by publishing-bot on client-go master are failing Ref for failure logs: Tests defined for client-go, after publishing, Since commit No response As part of , when module is used from within the staging directory, can be used by traversing to the parent directory. But once the module is made as a separate repository as part of publishing, then traversing to repository using path will not work. No response /sig-api-machinery\n/sig api-machinery\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /sig api-machinery 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\nLooking\nI'll remove the swagger file dependency, I don't think we strictly need it.\n/triage accepted", "commid": "kubernetes_issue_125704", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4caf04a555f035630d866bcf729cca71ae53363b4c3031c130f9bb22c903c863", "query": "ginkgo.By(\"Ensuring resource quota status captures configMap creation\") usedResources = v1.ResourceList{} usedResources[v1.ResourceQuotas] = resource.MustParse(strconv.Itoa(c + 1)) <del> // we expect there to be two configmaps because each namespace will receive // a ca.crt configmap by default. // ref:https://github.com/kubernetes/kubernetes/pull/68812 </del> usedResources[v1.ResourceConfigMaps] = resource.MustParse(hardConfigMaps) err = waitForResourceQuota(f.ClientSet, f.Namespace.Name, quotaName, usedResources) framework.ExpectNoError(err)", "positive_passages": [{"docid": "doc-en-kubernetes-7efc22ed3a8fb290fc16a7b40edf13445187015d16976624a8ed8ba9d9def220", "text": "I ran conformance tests on a cluster that had a controller enabled that syncs a configmap across all clusters. It failed: Appears to be due to a 2 configmap limit: These clusters should pass conformance. This is a very common pattern (even Kubernetes itself does it!). I didn't run it myself, but apparently just install Istio and run the conformance suite. See for details Kubernetes version (use ): v1.20.2\n/assign\nmy guess is the CA configmap created by default in 1.20 exacerbated this issue. I agree the conformance test should make fewer assumptions about the cluster it is running in and should accomodate default configmaps. left a comment on the PR in flight for this. I'd like to see the change picked to 1.20 as well.\n/triage accepted /priority important-soon", "commid": "kubernetes_issue_100016", "tokennum": 195}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4d1599a956709cb982487c4a6c358e45a0e62d95555c2f24b93be95262e53b59", "query": "containerTopologyScope = \"container\" // podTopologyScope specifies the TopologyManagerScope per pod. podTopologyScope = \"pod\" <ins> // noneTopologyScope specifies the TopologyManagerScope when topologyPolicyName is none. noneTopologyScope = \"none\" </ins> ) type podTopologyHints map[string]map[string]TopologyHint", "positive_passages": [{"docid": "doc-en-kubernetes-4d10931e14d2065e9a15e6880eb555f03f2fd6b09352947daeddff0435b576bc", "text": "Follow up from: See details there. When is , there is no need to discover the NUMA topology. /sig node /priority backlog /kind feature /help-wanted\n/cc\n/triage accepted\nI would like to take this up also can I get more brief information about it? code review comments from asking that inside the NewManager() implementation, we need to skip NewPolicyOptions and NewNUMAInfo but when the NumaTopology comes kubelet issue also comes. I need some more information to start with this!\n/cc\nWhen there is no topology manger policy specified, NewManager should be a no-op. Just skip all checks.\nExactly. Just to add: we may need few iterations over the change to get a clean flow in the call.\n/assign", "commid": "kubernetes_issue_116391", "tokennum": 166}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4d216e62d6afe32a0d5bf39557443e64a2166d52f7319b89efb7f3fe281b50df", "query": "return } for _, pod := range podList.Items { <del> framework.Logf(\"Kubectl output:n%v\", framework.RunKubectlOrDie(\"log\", pod.Name, \"--namespace=kube-system\")) </del> <ins> framework.Logf(\"Kubectl output:n%v\", framework.RunKubectlOrDie(\"log\", pod.Name, \"--namespace=kube-system\", \"--container=heapster\")) </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-2d8398c9fce5250ef4305561c3c57f1d1339a0f7afa5a1e82fbf81794df0228c", "text": "https://k8s- It seems that when it takes a while, it tries to collect debug info. And that collection is flawed because kubectl needs a container for log collection when the pod has more than one container.", "commid": "kubernetes_issue_27452", "tokennum": 51}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4d31ae772d5456b144369dbed5774abebd7f2dacd40ceb00847500c341c2207e", "query": "By(fmt.Sprintf(\"Initial restart count of pod %s is %d\", podDescr.Name, initialRestartCount)) // Wait for at most 48 * 5 = 240s = 4 minutes until restartCount is incremented <del> pass := false </del> <ins> restarts := false </ins> for i := 0; i < 48; i++ { // Wait until restartCount is incremented. time.Sleep(5 * time.Second)", "positive_passages": [{"docid": "doc-en-kubernetes-65bf469670180d69e57fdc1a820a8f2f435cec685a9975e90f226dd126851fba", "text": "As far as I can tell, container liveness probes of type exec flat out don't work against clusters built at head. I had the kubelet always log the output of the exec'ed command, and it's always empty no matter what I exec, causing the probe to fail since it requires the output to be equal to the string \"ok\". If you want to test it, try adding a liveness probe of this form to any container: I also tried these lovely forms, to more closely match the liveness example under examples/: On the plus side, this may be an opportunistic time to switch over to\nThe reason that the e2e test for exec liveness probes hasn't caught this is that it only tests that containers are restarted when they fail liveness probes. It doesn't test that containers aren't restarted when their liveness checks should be succeeding. The e2e test's exec'ed commands also only ever produced empty output, rather than the expected \"fail\" output.\nIs it possible to include this in a new pre-release, since it fixes a bug in health checking? I see it merged in master and I'm wondering what the policy is of releasing new code in a separate (0.16.*) release.", "commid": "kubernetes_issue_7618", "tokennum": 275}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4dc3275367e11f5562004c8b1381ddb178173ded1fb822e1dd719149efc57524", "query": "old_storage_version=${test_data[4]} kube::log::status \"Verifying ${resource}/${namespace}/${name} has storage version ${old_storage_version} in etcd\" <del> curl -s http://${ETCD_HOST}:${ETCD_PORT}/v2/keys/registry/${resource}/${namespace}/${name} | grep ${old_storage_version} </del> <ins> curl -s http://${ETCD_HOST}:${ETCD_PORT}/v2/keys/${ETCD_PREFIX}/${resource}/${namespace}/${name} | grep ${old_storage_version} </ins> done killApiServer", "positive_passages": [{"docid": "doc-en-kubernetes-74ce4fea7378dc634ccb83a22893b6255fa243ed3e0b4f0e57320154ecc66caf", "text": "removed this test. We need to continue testing this. This wasn't about testing upgrades, the prefix has nothing to do with upgrades. It's just there so people can share etcd. We maybe don't need to double everything but we do need to make sure that keeps working.\nTo be honest - I think that what we was testing before didn't give us completely any information. We didn't testing what information we are storing in etcd and where. That said, if we had a hardcoded prefix somewhere in our code, we wouldn't discover it at all, and those tests would still be passing. We should have a test that is directly checking etcd contents. I think it should be possible to write a simple unit test for it. Will try to put something together next week.", "commid": "kubernetes_issue_26489", "tokennum": 167}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4df3b809265b898ae97976f38e0399d4e18a0f0972d78b011094da465d84e873", "query": "func (runner *runner) connectToFirewallD() { bus, err := runner.dbus.SystemBus() if err != nil { <del> glog.V(1).Info(\"Could not connect to D-Bus system bus: %s\", err) </del> <ins> glog.V(1).Infof(\"Could not connect to D-Bus system bus: %s\", err) </ins> return }", "positive_passages": [{"docid": "doc-en-kubernetes-70ca5b9393197b9c681e23f75e1621b021d66b70b0941bb143c6bb4d3bdbccb3", "text": "I0921 20:36:33. ] Could not connect to D-Bus system bus: %sdial unix /var/run/dbus/systembussocket: connect: no such file or directory", "commid": "kubernetes_issue_14300", "tokennum": 46}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4dfef973dfe6219bf75ad9f1a597b021cc15d58029e598568afe3ee670855b3e", "query": "} // validateValueValidation checks the value validation in a structural schema. <del> func validateValueValidation(v *ValueValidation, skipAnyOf, skipFirstAllOfAnyOf bool, fldPath *field.Path) field.ErrorList { </del> <ins> func validateValueValidation(v *ValueValidation, skipAnyOf, skipFirstAllOfAnyOf bool, lvl level, fldPath *field.Path) field.ErrorList { </ins> if v == nil { return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-4be11de3bdb9e2a86ad3a19c4d6f5342db422d48e5979c118fca9ce077f64900", "text": "We allow CRD authors to write . Currently we don't restrict writing validation for , which means people can have . For example, people can have additive name constraints (require CR to be ) with the following schema: This brings us two questions: do we if \"metadata\" is included in the schema: simplest option is to publish standard metav1.ObjectMeta schema info, and use any CRD-specified \"metadata\" properties as additive validation (just like in-tree types do, publishing standard ObjectMeta schema info, and implementing type-specific name validation internally) alternatively, we can try merging user-specified metadata schema with the standard one. Technically people should only add extra validation to existing metadata properties (adding new fields to metadata won't work since they will be pruned by built-in validation first), but it's unclear to me how arbitrary people may want the metadata validation to be term question is whether to allow people specifying metadata validation at all, or just allow a subset (like name validation) in CRD v1 /sig api-machinery /area custom-resources cc\nWhat is the difference between these two? I mean the end result is the same right? The only thing that can be is validation. Nothing else works unless you are considering extensions?\nThe former means we drop/hide user-specified metadata schema when we publish CRD OpenAPI. We still validate user-specified constraints on server side, but client-side validation won't see them. The latter enables client-side user-specified metadata validation.\nIf it's possible to merge with standard metadata schema info, or at the cost of not publishing the standard schema. My inclination would be to publish the complete standard schema for metadata/apiVersion/kind, which we know is complete and accurate, and use and user-specified schema for those fields as addition validations server side", "commid": "kubernetes_issue_74620", "tokennum": 396}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4e1cd949c5e171393c152470ec2391341c6eacf0b49b848a38c0401730d81015", "query": "WaitForCacheSync: func() bool { return cache.WaitForCacheSync(c.StopEverything, c.scheduledPodsHasSynced) }, <del> NextPod: func() *v1.Pod { return c.getNextPod() }, </del> <ins> NextPod:         internalqueue.MakeNextPodFunc(c.podQueue), </ins> Error:           c.MakeDefaultErrorFunc(podBackoff, c.podQueue), StopEverything:  c.StopEverything, VolumeBinder:    c.volumeBinder,", "positive_passages": [{"docid": "doc-en-kubernetes-90b5ca2d1baaaaa2aa124277e8c3fdace970eae885ff81aa4062d924fde9dbb7", "text": "PLEASE COORDINATE WITH SIG-SCHEDULING BEFORE WORKING ON THIS ISSUE. We want to avoid the situation where two people accidentally start work on the same fix. Main tracking issue: The method of is a simple wrapper around . It should be converted into a simple closure instead of being a method. i.e. we should have, (code is in ) /sig scheduling /kind cleanup /help\nI'd like to take this task. /assign /remove-help\nThanks, go for it! :smile:", "commid": "kubernetes_issue_72546", "tokennum": 104}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4e37581a88bb412847689e2a25b0a71d3199e6410e354c5a26099ab4f794177a", "query": "} function dump_nodes() { <del> local node_names </del> <ins> local node_names=() </ins> if [[ -n \"${1:-}\" ]]; then echo \"Dumping logs for nodes provided as args to dump_nodes() function\" node_names=( \"$@\" )", "positive_passages": [{"docid": "doc-en-kubernetes-764cede5d9efbc9aa0896bda8776a6a1986b2e142264cb7af9fd4363856aed51", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: In https://k8s- failed due to . Afterwards crashed as follows: What you expected to happen: Graceful exit.\n/assign", "commid": "kubernetes_issue_55675", "tokennum": 45}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4e394ca93acd8b7476554626542bb7e0296a8dae4affef58ef29b23de8c5b06a", "query": "package v1_test import ( <del> \"encoding/json\" </del> <ins> \"fmt\" </ins> \"reflect\" \"testing\"", "positive_passages": [{"docid": "doc-en-kubernetes-c7797df648733fdf9e156246e323d8c03549ac9a3ca2ad30e283629a87abe7ee", "text": "What happened: kubelet doesn't seem to be able to manage containers started with CRI-O any more I'm testing kubelet + CRI-O on an Ubuntu 18.04 server installation, inside a qemu/kvm VM managed by Vagrant (see ), in order to be able to test k8s + KubeVirt + KataContainers, which are all compatible with CRI-O kubelet will obsess on starting new containers, which looks like and endless process, and the cluster never gets ready. For instance here are some syslogs : What you expected to happen: It used to work (see asciinema recording at ) a few days ago, but I fear some recent changes broke it. How to reproduce it (as minimally and precisely as possible): Testing with vagrant up --provider=libvirt on Linux with a clone of that commit: vagrant ssh into the VM and ps -edf f or tail -f /var/log/syslog would do... Anything else we need to know?: Environment: Kubernetes version (use ):Cloud provider or hardware configuration: qemu/kvm VM +OS (e.g: ): Ubuntu 18.04.2 LTS Kernel (e.g. ): Linux kubernetes-vagrant-01 4.15.0-48-generic -Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x8664 x8664 x8664 GNU/Linux Install tools: kubeadm as in Network plugin and version (if this is a network-related bug): Others:\n/sig node\nI can confirm this. If I start cri-o from a systemd service it fails with the above mentioned error message. Starting crio with without systemd works just fine. systemd file:\nThanks for your detailed report :) Just want to do some quick version confirming - you've been using k8s 1.14.1 both when it did and did not work? Any other version changes?\nNot sure for before, when it used to work, but according to the asciinema recording mentioned above (), it seems the same. However, not sure for CRI-O, underlying OS stuff (systemd, kernel, etc.). Sorry.\nI was looking for some information for days. I have exactly the same issue when I use podman + systemd on 18.04.2.", "commid": "kubernetes_issue_77615", "tokennum": 541}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4e394ca93acd8b7476554626542bb7e0296a8dae4affef58ef29b23de8c5b06a", "query": "package v1_test import ( <del> \"encoding/json\" </del> <ins> \"fmt\" </ins> \"reflect\" \"testing\"", "positive_passages": [{"docid": "doc-en-kubernetes-dca27e474f7f12153e878b1f27ed663eb17fd42e2832a567b0d652b26f30c566", "text": "It is the same for both 14.15 and 14.18 kernels. Podman without systemd runs fine. Podman with systemd fails at runc with the same error podman[]: open /dev/stderr: no such device or address podman[]: NAME: runc - Open Container Initiative runtime podman[]: runc is a command line client for running applications packaged according to ... podman[]: time=\"2019-05-11T13:04:59-07:00\" level=error msg=\"open /dev/stderr: no such device or addressn\" podman[]: open /dev/stderr: no such device or address\nI've tried to reproduce it on 18.04.2 using Podman from but I am not able to reproduce it. Do you have any reproducer? How did you install Podman?\nI used ceph unit files to run ceph in podman rather than docker. Systemd unit successfully starts docker but fails with podman. I can successfully run the same podman container run command from the command line. How were you trying to replicate this? Can you post your unit file?\nHi, I'am having the same problem with Kubernetes with CRI-O. After joining a second worker node it fails to start flannel. gives the following error: What I've tried: Installing previous version of Kubernetes (from to ) Installing previous version of crio (from to ) Building runc myself from their github page and selecting this in the Running it on Ubunut 18.04.2 Issue: (the one giuseppe linked)\nI wonder if the issue is with systemd and runc. In both cases, crio and podman, I see runc help output which tells me that something is not being passed to runc that it needs.\nI've only used so it is different than your test and you confirmed it works from the CLI for you as well. Could you share your service file so I test it?\nI've tried systemd and cgroupfs but no luck so far.\nso it seems that runc fails to re-open . That seems like a runc issue, as it doesn't really need to reopen it. To fix the failure, you could use something like:\nJust an example.", "commid": "kubernetes_issue_77615", "tokennum": 504}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4e394ca93acd8b7476554626542bb7e0296a8dae4affef58ef29b23de8c5b06a", "query": "package v1_test import ( <del> \"encoding/json\" </del> <ins> \"fmt\" </ins> \"reflect\" \"testing\"", "positive_passages": [{"docid": "doc-en-kubernetes-1a33d9e403b3728be8b8de7e79372d00143f16de361084780a7a026e224a4dd2", "text": "I use ceph-ansible to install cluster so it may need to install additional daemons like mon before running mgr but the error, in this case, should be different, [Unit] Description=Ceph Manager [Service] EnvironmentFile=-/etc/environment ExecStartPre=-/usr/bin/podman stop ceph-mgr-storage2n1-la ExecStartPre=-/usr/bin/podman rm ceph-mgr-storage2n1-la ExecStart=/usr/bin/podman run --rm --net=host  --memory=16G  --cpus=4  -v /var/lib/ceph:/var/lib/ceph:z  -v /etc/ceph:/etc/ceph:z  -v /var/run/ceph:/var/run/ceph:z  -v /etc/localtime:/etc/localtime:ro  -e CLUSTER=ceph  -e CEPHDAEMON=MGR  -e CONTAINERIMAGE=  {{ cephmgrdockerextraenv }}  --name=ceph-mgr-storage2n1-la  ExecStopPost=-/usr/bin/podman stop ceph-mgr-storage2n1-la Restart=always RestartSec=10s TimeoutStartSec=120 TimeoutStopSec=15 [Install] WantedBy=multi- delighted <:\nBTW, I projectatomic ppa and used apt-get -y podman to install. My podman version is 1.3.0 Sasha Litvak \u2014 You are receiving this because you commented. Reply to this email directly, view it on GitHub , or mute the thread\nCorrected file.", "commid": "kubernetes_issue_77615", "tokennum": 404}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4e394ca93acd8b7476554626542bb7e0296a8dae4affef58ef29b23de8c5b06a", "query": "package v1_test import ( <del> \"encoding/json\" </del> <ins> \"fmt\" </ins> \"reflect\" \"testing\"", "positive_passages": [{"docid": "doc-en-kubernetes-bae004f13a06f51a77aaeb8de64c7434d457cced5ee158b56a68659aa46bb958", "text": "[Unit] Description=Ceph Manager [Service] EnvironmentFile=-/etc/environment ExecStartPre=-/usr/bin/podman stop ceph-mgr-storage2n1-la ExecStartPre=-/usr/bin/podman rm ceph-mgr-storage2n1-la ExecStart=/usr/bin/podman run --rm --net=host  --memory=16G  --cpus=4  -v /var/lib/ceph:/var/lib/ceph:z  -v /etc/ceph:/etc/ceph:z  -v /var/run/ceph:/var/run/ceph:z  -v /etc/localtime:/etc/localtime:ro  -e CLUSTER=ceph  -e CEPHDAEMON=MGR  -e CONTAINERIMAGE=  --name=ceph-mgr-storage2n1-la  ExecStopPost=-/usr/bin/podman stop ceph-mgr-storage2n1-la Restart=always RestartSec=10s TimeoutStartSec=120 TimeoutStopSec=15 [Install] WantedBy=multi- Giuseppe Scrivano <:\nWould it have an effect system wide? Can I add it to a unit file or unit override instead? Giuseppe Scrivano <:\nyes, I think it is better to add it only to the unit file\nWhy would runc work outside of systemd? And if it needs stderr, giving it Null in settings will redirect stderr to Null I presume? On Tue, May 14, 2019, 9:46 AM Giuseppe Scrivano <:\nRunning into same issues on Ubuntu 18.04.2 using cri-o-1.13 via PPA.\nPR here: opencontainers/runc\nUntil it is avaialble with project atomic and such, can I use a null workaround? Giuseppe Scrivano <:\nyes, but you will lose anything written to stderr. You could probably also use a file, like\nWhat about actually mounting dev and using /dev/stderr ? On Tue, May 14, 2019, 3:11 PM Giuseppe Scrivano <:\nis a symlink to . It is present, the issue here is that is a socket. The fix for runc got merged, could you use an updated runc?\nI tried apt update/upgrade and restarting crio, but I'm still getting the issue.", "commid": "kubernetes_issue_77615", "tokennum": 570}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4e394ca93acd8b7476554626542bb7e0296a8dae4affef58ef29b23de8c5b06a", "query": "package v1_test import ( <del> \"encoding/json\" </del> <ins> \"fmt\" </ins> \"reflect\" \"testing\"", "positive_passages": [{"docid": "doc-en-kubernetes-a9af1b8339c2af3d5a8899da2b8916e4bc8194e1229dc4a9dc77c862af07f4a9", "text": "Could it be that crio's runc is not updated yet? Edit Build new runc from and it is working now. Think crio hasn't updated it yet with their repository.\nI'm running this version from PPA repo for ubuntu and it fails: could you point to version/commit or whatever helps identify the fixed version/snapshot ? Thanks in advance.\nat the moment it is only fixed upstream. You'd need to build runc manually\nIs there a version of the package on ppa we can downgrade to? On Wed, May 15, 2019, 4:35 AM Giuseppe Scrivano <:\ncould we update the runc version in the PPA repo?\nThank you. I seem them built but nut pushed to ppa yet.\nshould be available now.. let me know..\ncri-o-runc (1.0.0-rc6-1~dev~ubuntu18.04~ppa42) bionic; urgency=medium autobuilt -- Lokesh Mandvekar (Bot) <, 15 May 2019 16:54:40 +0000\nThank you, everyone, for a quick turn around. Quick testing showed that fix is working, but more testing is needed. Lokesh Mandvekar <:\nI confirm my initial tests with seem to confirm the regression is fixed. Many thanks\nI also confirm the fix working for podman. Olivier Berger <:", "commid": "kubernetes_issue_77615", "tokennum": 305}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4e394ca93acd8b7476554626542bb7e0296a8dae4affef58ef29b23de8c5b06a", "query": "package v1_test import ( <del> \"encoding/json\" </del> <ins> \"fmt\" </ins> \"reflect\" \"testing\"", "positive_passages": [{"docid": "doc-en-kubernetes-c1c167f97d0d68a2d507d0d919d58cd680ff8ed576e3225c7b24d703a964bd61", "text": "<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.--Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see ): No What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): initContainers imagePullPolicy initContainers required value Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT <!-- If this is a BUG REPORT, please: Fill in as much of the template below as you can. If you leave out information, we can't help you as well. If this is a FEATURE REQUEST, please: Describe in detail the feature/behavior/change you'd like to see. In both cases, be ready for followup questions, and please respond in a timely manner. If we can't reproduce a bug or think a feature already exists, we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why. --Kubernetes version (use ): Environment: Cloud provider or hardware configuration: GCE OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: cluster/kube- Others: What happened: When trying to create either a ReplicaSet or Replication Controller whose Pod template contains an Init Container, the validation fails saying is a required value. What you expected to happen: The create should succeed and the Init Container should receive a default . How to reproduce it (as minimally and precisely as possible): Try to create either of the following: ReplicaSet Replication Controller Anything else do we need to know: If I add to the Init Container in the ReplicaSet or Replication Controller Pod template, the create succeeds. When I create an Init Container without in a StatefulSet Pod template, it succeeds. When I create an Init Container without in a bare Pod, it succeeds:\nLooks like defaulting not being applied on server? That is probably due to removing defaulting from convert. Surprised we didn't catch this earlier\nSome values still not being defaulted\n, I'm going to create a PR if none works on it.\nWe decode from bytes, set defaults and then convert; but for init containers, we delay the decode from \"decode phase\" to \"convert phase\" at .", "commid": "kubernetes_issue_38542", "tokennum": 524}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4e394ca93acd8b7476554626542bb7e0296a8dae4affef58ef29b23de8c5b06a", "query": "package v1_test import ( <del> \"encoding/json\" </del> <ins> \"fmt\" </ins> \"reflect\" \"testing\"", "positive_passages": [{"docid": "doc-en-kubernetes-69dbac4fd7f4ee2d4feb0af6994cc2f74e65b4d3465b8e0c7014cfb5909cea9b", "text": "The defaults has been handled for initContainer at . /cc I'm working to find a solution for that; if any suggestion, please let me know.\nWould this bug affect the deletion of jobs with an init-container? I ran into this bug and adjusted my manifest to add the pull policy to the init-container. However, I now cannot delete said job claiming a field is immutable. Example:\n, not sure now. Let me check it,\nSame error here with version 1.5.1, 1.5.2 The Job \"grafana-import-dashboards\" is invalid: [0].imagePullPolicy: Required value With this setup: kubectl apply -f monitoring Not working even if I specify a pullpolicy in the yaml. If I roll back to 1.4.7, it is working. Thank you. Greg.\nany updates on a PR to address this issue? Is anyone from able to pick this issue up otherwise?\n, here's the latest status: there's is a PR to generate for each Object (), it works for Object (Pod, Job) now but List; I'm working to make it generating for List.\nWhy would you need List to work? No client side logic should be decoding lists except as a generic submission.\nThe List tests are failed in . There's no for List, so no code to decode init-container annotation, e.g. of should call 's recursively.\nThanks for the update\n+1\nAny update on this? I still getting this issue with the last version of 1.5.3 on GKE?\nping for the comments? should we merge the PR for 1.5?\n, there's a PR () that handled that issue; but we're discussing not to merge it because initContainers had been moved to fields, and fields is the recommended way to use since 1.6. But I'd like to get & 's comments on 1.5.\nThis is still an issue in 1.5.3 when using annotations: Without the deployment would not be accepted\nping & :).\ni dont think this is fixed in 1.5 I just encountered this bug on 1.5.3\n, yes, the PR is NOT merged to any branch, so the issue is still here. I'll create a PR for 1.5.\nHi Anyone help this issue.", "commid": "kubernetes_issue_38542", "tokennum": 520}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4e394ca93acd8b7476554626542bb7e0296a8dae4affef58ef29b23de8c5b06a", "query": "package v1_test import ( <del> \"encoding/json\" </del> <ins> \"fmt\" </ins> \"reflect\" \"testing\"", "positive_passages": [{"docid": "doc-en-kubernetes-cd1dc8216bffde40e45195a0aceb1bbd0c560296ad557f563dafcf3df89eeea5", "text": "#cat mongo- apiVersion: v1 kind: Pod metadata: labels: name: mongo-svc-a name: mongo-deployment spec: replicas: 1 template: metadata: labels: name: mongo spec: containers: image: mongo name: mongo ports: name: mongo containerPort: hostPort: volumeMounts: mountPath: \"/data/db\" name: mongopv volumes: name: mongopv persistentVolumeClaim: claimName: mongopvc When i want create mongo db container by using this file folowing error is occured. The Pod \"mongo-deployment\" is invalid:spec.containers: Required value\n, it seems there're two here, please remove the first one and have a try.\nHi my kubectl binary is configured at ubuntu 16.04 machine.", "commid": "kubernetes_issue_38542", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4e394ca93acd8b7476554626542bb7e0296a8dae4affef58ef29b23de8c5b06a", "query": "package v1_test import ( <del> \"encoding/json\" </del> <ins> \"fmt\" </ins> \"reflect\" \"testing\"", "positive_passages": [{"docid": "doc-en-kubernetes-7c77a1e7ea84d582b899fa6b8d7216504334c47e064fb8eaad5c523c3bc66a32", "text": "NAME LABELS STATUS 10.1 Ready,SchedulingDisabled 10.2 10.1.10.2 Ready 10.3 Ready apiVersion: v1 kind: Node metadata: creationTimestamp: 2017-03-03T14:41:52Z labels: 10.1.10.1 name: 10.1.10.1 resourceVersion: \"\" selfLink: /api/v1/nodes/10.1.10.1 uid: -001f-11e7-8e83- spec: externalID: 10.1.10.1 status: addresses: address: 10.1.10.1 type: LegacyHostIP address: 10.1.10.1 type: InternalIP capacity: cpu: \"2\" memory: 4041352Ki pods: \"110\" conditions: lastHeartbeatTime: 2017-04-05T18:58:42Z lastTransitionTime: 2017-03-03T14:41:52Z message: kubelet has sufficient disk space available reason: KubeletHasSufficientDisk status: \"False\" type: OutOfDisk lastHeartbeatTime: 2017-04-05T18:58:42Z lastTransitionTime: 2017-04-05T15:27:52Z message: kubelet is posting ready status reason: KubeletReady status: \"True\" type: Ready nodeInfo: bootID: -6124-4ac7-ab96- containerRuntimeVersion: docker://1.12.6 kernelVersion: 4.9.16-coreos-r1 kubeProxyVersion: v1.2.4+coreos.1 kubeletVersion: v1.2.4+coreos.1 machineID: osImage: Container Linux by CoreOS 1298.7.0 (Ladybug) systemUUID: C3FD9852-2DFB-21F4-CE07-2597A746D99D When i create pv for creation pod is shows pv is pending. Please give any suggestions.....\nIs there solution of this problem with version 2.7. Still facing the same. what exactly expectation of helm upgrade --install relname chartsdirectory is is expected to work on first time installation in case with CI/CD Pipelines.", "commid": "kubernetes_issue_38542", "tokennum": 511}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4e3e33f18400c5396553d1ace3b4d355524ee5121f71770b3420f958e8a70166", "query": "configs[NginxNew] = Config{list.PromoterE2eRegistry, \"nginx\", \"1.15-2\"} configs[NodePerfNpbEp] = Config{list.PromoterE2eRegistry, \"node-perf/npb-ep\", \"1.2\"} configs[NodePerfNpbIs] = Config{list.PromoterE2eRegistry, \"node-perf/npb-is\", \"1.2\"} <del> configs[NodePerfTfWideDeep] = Config{list.PromoterE2eRegistry, \"node-perf/tf-wide-deep\", \"1.2\"} </del> <ins> configs[NodePerfTfWideDeep] = Config{list.PromoterE2eRegistry, \"node-perf/tf-wide-deep\", \"1.3\"} </ins> configs[Nonewprivs] = Config{list.PromoterE2eRegistry, \"nonewprivs\", \"1.3\"} configs[NonRoot] = Config{list.PromoterE2eRegistry, \"nonroot\", \"1.2\"} // Pause - when these values are updated, also update cmd/kubelet/app/options/container_runtime.go", "positive_passages": [{"docid": "doc-en-kubernetes-18a84ca90a3e633f3a3a09fc3ce20a2ee5a77d52c40aa5d987ef95b0afbf9b00", "text": "E2eNode Suite.[sig-node] Node Performance Testing [Serial] [Slow] Run node performance testing with pre-defined workloads TensorFlow workload From the testgrid, it has been 1/2 flaky since the start of history (03/20/2022) and has been failing constantly (0/2) since 04/01/2022 No response /sig node\n/triage accepted /priority important-soon\nThe failing test seems to be expecting GPU on machine and the image seems to be broken. I tried the image manually: Logs:\n/assign as discussed at SIG Node CI meeting, can you please take a look? I see that pod is now running for couple minutes and then stops. I wonder if this is something environment related - maybe pod was evicted or something. I doesn't seem to be able to repro the failure of the pod locally\nGitHub didn't allow me to assign the following users: xmcqueen. 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\nThis is no longer a flake. It has failed every run since the start of June. Locally this test runs perfectly with a legit correct local run of the test suite code, doing the full tensorflow run of 300 epochs. The failure in the testgrid job seems to be fast (173 sec to build and fail, locally its 160 sec before it starts the tensorflow pod). I wonder if there's a blocked port or something from the data initializing python program. It needs access to: . Here's the command it runs: Is it feasible to add debugging code, like a pre-check for that http port? It would be good to at least force it to fail with a meaningful error message.\nNote that HEAD is now at image version 1.2, and it is still failing per . The successful local runs of the test mentioned above used image version 1.2.", "commid": "kubernetes_issue_109295", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4e3e33f18400c5396553d1ace3b4d355524ee5121f71770b3420f958e8a70166", "query": "configs[NginxNew] = Config{list.PromoterE2eRegistry, \"nginx\", \"1.15-2\"} configs[NodePerfNpbEp] = Config{list.PromoterE2eRegistry, \"node-perf/npb-ep\", \"1.2\"} configs[NodePerfNpbIs] = Config{list.PromoterE2eRegistry, \"node-perf/npb-is\", \"1.2\"} <del> configs[NodePerfTfWideDeep] = Config{list.PromoterE2eRegistry, \"node-perf/tf-wide-deep\", \"1.2\"} </del> <ins> configs[NodePerfTfWideDeep] = Config{list.PromoterE2eRegistry, \"node-perf/tf-wide-deep\", \"1.3\"} </ins> configs[Nonewprivs] = Config{list.PromoterE2eRegistry, \"nonewprivs\", \"1.3\"} configs[NonRoot] = Config{list.PromoterE2eRegistry, \"nonroot\", \"1.2\"} // Pause - when these values are updated, also update cmd/kubelet/app/options/container_runtime.go", "positive_passages": [{"docid": "doc-en-kubernetes-924fdb64dda3a1d51367c5f2ba44327b61b51dcf8cc0ad56f75173d2dbe65d92", "text": "Locally image version 1.1 does produce the cuda/GPU error shown above by :\nMore info is needed to find the RC for this test failure. I've put in a PR to get the test framework to preserve the container logs when the pod fails.\nThe pod logs show that it is timing out on an http connection, and it looks like it's the one where it tries to download the test data set for the tensorflow run. You can see it . Search down to . The data_download script in the image attempts to pull down a dataset from: . That url is live and healthy, so they might be blocking the gcloud.\nThis test depending on that external data doesn't look quite right :/\nI'm discussing this test with sig-testing. I'll post an update later.\nTalked to from sig-testing: he's contacting the remote to see if they are blocking us, because it looks like they are is pulling the script from a that is So I see three choices: upgrade this thing to a more recent edition delete it grab everything that's needed to run this and keep it in-house <- clear winner here what do you think: Maybe the folks over at sig-testing have a place to store the artifacts in-house? They are not massive (about 10MB see below) Size of data about 10MB: the tools and libs for the tensorflow run: the training and eval files for the testrun:\nHere's a relevant issue in a related k8s repo about using/not using docker registries: Registries used in k/k CI should be on Kubernetes Community infra\nlooks good for the subject of putting up a new docker image containing the deps. This seems feasible and effective. I'd prefer it to deleting the test. I'll discuss it a bit more with a few others, but this seems like the way to go forward with this. TBS, I plan to take the above listed test requirements, and build a docker image containing all that is needed, and reset the test to pull the new docker image.\nI've got some Dockerfile changes to fix this. I've tested it locally with no network and it does the full 300 epochs. PR coming soon.\nIs it worth pushing up 182 files to get this green? It is about 6M of python, and 5M of a test dataset.", "commid": "kubernetes_issue_109295", "tokennum": 515}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4e3e33f18400c5396553d1ace3b4d355524ee5121f71770b3420f958e8a70166", "query": "configs[NginxNew] = Config{list.PromoterE2eRegistry, \"nginx\", \"1.15-2\"} configs[NodePerfNpbEp] = Config{list.PromoterE2eRegistry, \"node-perf/npb-ep\", \"1.2\"} configs[NodePerfNpbIs] = Config{list.PromoterE2eRegistry, \"node-perf/npb-is\", \"1.2\"} <del> configs[NodePerfTfWideDeep] = Config{list.PromoterE2eRegistry, \"node-perf/tf-wide-deep\", \"1.2\"} </del> <ins> configs[NodePerfTfWideDeep] = Config{list.PromoterE2eRegistry, \"node-perf/tf-wide-deep\", \"1.3\"} </ins> configs[Nonewprivs] = Config{list.PromoterE2eRegistry, \"nonewprivs\", \"1.3\"} configs[NonRoot] = Config{list.PromoterE2eRegistry, \"nonroot\", \"1.2\"} // Pause - when these values are updated, also update cmd/kubelet/app/options/container_runtime.go", "positive_passages": [{"docid": "doc-en-kubernetes-1089cbe285cd80c5b6feae67c8fda7b5283b08a5d4cab211d1adc2743664a2e8", "text": "Its all stashed away in the to get the docker image to contain the prereqs. It is selected subdirectories of the quite old archived version (v1.9.0) of the code from here: current version v2.7.2 and two small test data sets from here:\nOK I got it down to 43 files, including the 2 datasets. That's the drivers and the datasets and the libs they need. It all gets packed into the docker image.\nquick question - is there another repository that is under sig-node that can host this image?\nTo be clear, the test's docker image is currently in a repo, the : This PR adds artifacts to an existing docker image in the above repo.\nI've cancelled the above PR. I'll try to get something else going.\nThere has been a decent amount of discussion in slack relating to handling the test's required artifacts. The solution that seems best is to get some practical version of the test requirements into locally owned and controlled storage, so the endpoints that provide access to the assets will at least be under internal control. This is not code, and is not under development. It is a static dataset, that is now stored in an offsite archive, and will not require maintenance. The datasets are published with the \"\": (see bottom right) \"This allows for the sharing and adaptation of the datasets for any purpose, provided that the appropriate credit is given.\" Here are some links to the dataset and where its hosted: https://archive-\nI'd like to get the dataset that holds the test data (about 650k) hosted in GCS where I can get it via http. With that change it is expected that the test will go green. The failures show it is failing when it tries to download the artifact from the uncontrolled remote endpoint. Somebody, please help me get this artifact into an internally controlled server. Thanks\nWas the idea of downloading this only on image creation in dockerfile rejected?\nThanks for the reminder I did not fairly evaluate that proposal. I just jumped to my earlier proposal. Thinking about this proposal I see that it would mean downloading the test data for inclusion into the docker image, while the image's test driver tooling is built to pull down the dataset itself from a remote.", "commid": "kubernetes_issue_109295", "tokennum": 504}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4e3e33f18400c5396553d1ace3b4d355524ee5121f71770b3420f958e8a70166", "query": "configs[NginxNew] = Config{list.PromoterE2eRegistry, \"nginx\", \"1.15-2\"} configs[NodePerfNpbEp] = Config{list.PromoterE2eRegistry, \"node-perf/npb-ep\", \"1.2\"} configs[NodePerfNpbIs] = Config{list.PromoterE2eRegistry, \"node-perf/npb-is\", \"1.2\"} <del> configs[NodePerfTfWideDeep] = Config{list.PromoterE2eRegistry, \"node-perf/tf-wide-deep\", \"1.2\"} </del> <ins> configs[NodePerfTfWideDeep] = Config{list.PromoterE2eRegistry, \"node-perf/tf-wide-deep\", \"1.3\"} </ins> configs[Nonewprivs] = Config{list.PromoterE2eRegistry, \"nonewprivs\", \"1.3\"} configs[NonRoot] = Config{list.PromoterE2eRegistry, \"nonroot\", \"1.2\"} // Pause - when these values are updated, also update cmd/kubelet/app/options/container_runtime.go", "positive_passages": [{"docid": "doc-en-kubernetes-1e0a13eacbc2a35a9de3ea0888ffa655ef37373231443eb0a06d10729155f72f", "text": "That is a simple change to handle, while simply re-hosting the artifact on GCS would require only changing the endpoint. Also building the docker would probably still require network access to the artifact, which would probably require us to put it somewhere anyway. I assume, putting it into the docker image would best be done by downloading the test data artifact from somewhere. Would we then be storing the artifact twice - once in the docker image, and once in a locally controlled endpoint? If the docker build server has unrestricted access to the artifact, this proposal would be good. I don't have access to the servers to run tests. However, I could put up an RB for the Dockerfile to try it out. This is probably worth the effort. I'll get an PR going for trying to pull down the remote test-data artifact from the image build server, and bunde it into the docker image, and I'll link it to this ticket.\nthank you. We do not change the image for a long time, so downloading it once would likely be enough. Once it is self-contained, it is even better for the continuous perf runs in tests.\n/reopen\nYou can't reopen an issue/PR unless you authored it or you are a collaborator. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nCurrently the image builds for the first arch (amd64) but fails when it enters the cross compiling phase (arm64) and specifically when it tries to do apt installs from within the qemu-*-static emulator: The other images in node-perf fail to build in the same way. The jessie-dnsutils image build fails to build in the same way. I have tried pulling in newer base images up to buster, but it did not fix the problem. -Start focusing on the version of qemu. - qemu is version locked in the Makefile and has not changed in two years. There was an and the images were building at that time.", "commid": "kubernetes_issue_109295", "tokennum": 507}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4e3e33f18400c5396553d1ace3b4d355524ee5121f71770b3420f958e8a70166", "query": "configs[NginxNew] = Config{list.PromoterE2eRegistry, \"nginx\", \"1.15-2\"} configs[NodePerfNpbEp] = Config{list.PromoterE2eRegistry, \"node-perf/npb-ep\", \"1.2\"} configs[NodePerfNpbIs] = Config{list.PromoterE2eRegistry, \"node-perf/npb-is\", \"1.2\"} <del> configs[NodePerfTfWideDeep] = Config{list.PromoterE2eRegistry, \"node-perf/tf-wide-deep\", \"1.2\"} </del> <ins> configs[NodePerfTfWideDeep] = Config{list.PromoterE2eRegistry, \"node-perf/tf-wide-deep\", \"1.3\"} </ins> configs[Nonewprivs] = Config{list.PromoterE2eRegistry, \"nonewprivs\", \"1.3\"} configs[NonRoot] = Config{list.PromoterE2eRegistry, \"nonroot\", \"1.2\"} // Pause - when these values are updated, also update cmd/kubelet/app/options/container_runtime.go", "positive_passages": [{"docid": "doc-en-kubernetes-21583406d11cc50f0d960b70331655967f38b78788b3327204ea9b4d500f4be7", "text": "Try to find clues over there.\nI tried pinning many relevant versions of from but none helped. Here's a clue: This ugly hack gets it past the observed error:\nNote the previous PR was missing an important change, but I do not see any feasible way that could explain the current problem with failing, so I have not felt any urgency to put up a PR for it. FTR I need to bump the VERSION. I did not bump the version in I thought maybe the CI would bump it automatically.\nThere's an image version in . Its still pulling the old version and failing. Bump it from 1.2 to 1.3. So one more commit is needed.\nThe new image is present and runs perfectly. Tested it on local linux and in google cloud: It ran to completion. Note the new image URL. Its NOT the same as the old one:\npodspec references the image Here's the . tf-wide-deep's url is built The above has staging in it. . Its already built and pushed to staging. It must be promoted when this new version number goes out.\nFTR: My \"testing\" above did not catch the current problem because I did not run the full e2e_test binary. I only tested the image via a . AND I should have read way back at the beginning.\nLocal run of : has to change too.\nLocal test using the published 1.3 image run the standard way was successful with the above: ran the test successfully. So promote the image per bump the image version in the e2e test manifest change the\nAfter the image promotion is merged, there's STILL one more commit coming: bump the image version in the e2e test manifest change the\nits promoted and is found at the expected url local containerd cleared out local test was rerun pulling from the new prod registry local test using that new registry passes\nits fixed. the test is green again.", "commid": "kubernetes_issue_109295", "tokennum": 399}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4e68d2e05ed579fd7e99b7a33cc8c5f8ba10d3db6e26a1b3b2a27ccee7b54d7c", "query": "} if inline := cmdutil.GetFlagString(cmd, \"overrides\"); len(inline) > 0 { <del> object, err = cmdutil.Merge(scheme.Codecs.LegacyCodec(scheme.Scheme.PrioritizedVersionsAllGroups()...), object, inline) </del> <ins> codec := runtime.NewCodec(scheme.DefaultJSONEncoder(), scheme.Codecs.UniversalDecoder(scheme.Scheme.PrioritizedVersionsAllGroups()...)) object, err = cmdutil.Merge(codec, object, inline) </ins> if err != nil { return err }", "positive_passages": [{"docid": "doc-en-kubernetes-fc07b6eddbb9d1c63170ff68b48220d761822f4a0e8799d7065a14dbb9d41309", "text": "Hey Guys , I try to use the option --override with kubectl expose . First i did this and it work : Now i want to add another service with kubectl expose and this command does not work I have this error If i remove --overrides the command work . `\n/sig cli\nexpose tries to convert version from \"v1\" to \"_internal\" which is not registered. This is the reason that the function doesn't works. == \"\" 316 if inline := cmdutil.GetFlagString(cmd, \"overrides\"); len(inline) 0 { 317 object, err = cmdutil.Merge(scheme.Codecs.LegacyCodec(scheme.Scheme.PrioritizedVersionsAllGroups()...), object, inline) 318 if err != nil { 319 return err 320 } 321 } === 156 // LegacyCodec encodes output to a given API versions, and decodes output into the internal form from 157 // any recognized source. The returned codec will always encode output to JSON. If a type is not 158 // found in the list of versions an error will be returned. 159 // 160 // This method is deprecated - clients and servers should negotiate a serializer by mime-type and 161 // invoke CodecForVersions. Callers that need only to read data should use UniversalDecoder(). 162 // 163 // TODO: make this call exist only in pkg/api, and initialize it with the set of default versions. 164 // All other callers will be forced to request a Codec directly. 165 func (f CodecFactory) LegacyCodec(version ) runtime.Codec { 166 return versioning.NewDefaultingCodecForScheme(f.scheme, f.legacySerializer, f.universal, schema.GroupVersions(version), runtime.InternalGroupVersioner) 167 }\nkubectl help expose Expose a resource as a new Kubernetes service. Possible resources include (case insensitive): pod (po), service (svc), replicationcontroller (rc), deployment (deploy), replicaset (rs) In order to control the scope, I only register them as un-versioned type in the fix.", "commid": "kubernetes_issue_73077", "tokennum": 521}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4e7aa4a381e9aea985e13e10c9c967008a0103029737fd980eec6c1087541eb8", "query": "\"strings\" \"time\" <ins> \"encoding/json\" </ins> appsv1 \"k8s.io/api/apps/v1\" \"k8s.io/api/core/v1\" storage \"k8s.io/api/storage/v1\" \"k8s.io/apimachinery/pkg/api/resource\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/labels\" <ins> \"k8s.io/apimachinery/pkg/types\" </ins> \"k8s.io/apimachinery/pkg/util/sets\" <ins> \"k8s.io/apimachinery/pkg/util/strategicpatch\" \"k8s.io/apimachinery/pkg/util/wait\" </ins> clientset \"k8s.io/client-go/kubernetes\" podutil \"k8s.io/kubernetes/pkg/api/v1/pod\" \"k8s.io/kubernetes/pkg/kubelet/apis\" kubeletapis \"k8s.io/kubernetes/pkg/kubelet/apis\" \"k8s.io/kubernetes/pkg/volume/util\" \"k8s.io/kubernetes/test/e2e/framework\" <del> \"k8s.io/kubernetes/test/e2e/framework/providers/gce\" </del> \"k8s.io/kubernetes/test/e2e/storage/testsuites\" \"k8s.io/kubernetes/test/e2e/storage/utils\" imageutils \"k8s.io/kubernetes/test/utils/image\"", "positive_passages": [{"docid": "doc-en-kubernetes-07b454797aabeff00bf033fc34fa4c22bd06966ba8574ac0fa868459bacbceea", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: What happened: Testgrid: https://k8s-\n/assign\nThe test's assumption about test parameter is wrong. Previously it assumed the group name is the same across all zones, but they are different in regional clusters. Looking into using node taints as the permanent fix, as suggested by the TODO comment in the test.\nHm I think taint based evictions is still an alpha feature.\nOK. I propose the following solution: Get the zone of Schedule the StatefulSet pod to that zone using node affinity; wait for the pod to run Remove the node affinity from StatefulSet Delete\nCan it be simplified? Schedule the pod Figure out which zone that pod got scheduled in Delete the instance group of that zone\nUnfortunately I don't know of a good way to look up the instance group given the zone, since there could be instance groups from multiple clusters in the same project\nHow about: Schedule the pod Figure out the zone Taint all the nodes in the zone Kill the pod\nTaint with NoSchedule? yeah that sounds good", "commid": "kubernetes_issue_69005", "tokennum": 267}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4e7abfdb19bc742161d38b85d4d0d8db14b6218dbe5c58e9bae83d6982b47fbc", "query": "return c.restConfig, nil } <ins> func (c *fakeAuthenticationInfoResolver) ClientConfigForService(serviceName, serviceNamespace string) (*rest.Config, error) { atomic.AddInt32(c.cachedCount, 1) return c.restConfig, nil } </ins> func newMatchEverythingRules() []registrationv1beta1.RuleWithOperations { return []registrationv1beta1.RuleWithOperations{{ Operations: []registrationv1beta1.OperationType{registrationv1beta1.OperationAll},", "positive_passages": [{"docid": "doc-en-kubernetes-73496a383d34eb1ab5962a20be4dce66952c6d20058c4ff89ce94afc1cb5683d", "text": "We are getting the following error when the apiserver connects the webhook on localhost (configured via URL). We should only use the SSL tunnel for the connections to nodes when the webhooks are running as services. /sig api-machinery /kind bug /assign\n/close", "commid": "kubernetes_issue_58779", "tokennum": 64}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4ea54e43772aa981ad20d5ec14b1717f37413a2e433650ff81af05f047a4d7d5", "query": "// Create a security group for the load balancer sgName := \"k8s-elb-\" + loadBalancerName sgDescription := fmt.Sprintf(\"Security group for Kubernetes ELB %s (%v)\", loadBalancerName, serviceName) <del> securityGroupID, err = c.ensureSecurityGroup(sgName, sgDescription) </del> <ins> securityGroupID, err = c.ensureSecurityGroup(sgName, sgDescription, getLoadBalancerAdditionalTags(annotations)) </ins> if err != nil { glog.Errorf(\"Error creating load balancer security group: %q\", err) return nil, err", "positive_passages": [{"docid": "doc-en-kubernetes-f0769863fab39b633cda95f4d162dbe6bf42638a791c88a2a3acb41bb68633b3", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature /sig aws What happened: In k8s 1.7, when creating a service of type LoadBalancer, K8S creates the ELB and a Security Group for it. For these resources, it adds a tag, constructed dynamically, containing the cluster id: \"${cluster_id}\" with the value \"true\" What you expected to happen: We'd like to have also a statically named tag , as it was in 1.5 (\"KubernetesCluster\") with the value of the cluster id. How to reproduce it (as minimally and precisely as possible): Running on AWS cloud provider, create a service of type LoadBalancer. Anything else we need to know?: The reason for what we expect is that we have tight security constraints that require us to fine tune the IAM policies for the Instance profiles that the controllers use. With a statically named tag we were able, in 1.5, to restrict the permissions in the IAM policy to act only on the k8s managed resources (ELBs, security groups). Here is the relevant part of the IAM policy: With a dynamically named tag we are not able to do this any more as AWS IAM doesn't support something like: We are sharing the Instance Profiles among different k8s clusters, hence the \"\" in the value of the tag. Environment: Kubernetes version (use ):Cloud provider or hardware configuration*: AWS OS (e.g. from /etc/os-release):Kernel (e.g. ):Install tools: kube-aws Others:\nReiterating the mentions to trigger a notification: <detailsIn response to : <!-- This form is for bug reports and feature requests ONLY! -- /sig aws In k8s 1.7, when creating a service of type LoadBalancer, K8S creates the ELB and a Security Group for it. For these resources, it adds a tag, constructed dynamically, containing the cluster id: \"${cluster_id}\" with the value \"true\" We'd like to have also a statically named tag , as it was in 1.5 (\"KubernetesCluster\") with the value of the cluster id. Running on AWS cloud provider, create a service of type LoadBalancer.", "commid": "kubernetes_issue_53489", "tokennum": 543}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4ea54e43772aa981ad20d5ec14b1717f37413a2e433650ff81af05f047a4d7d5", "query": "// Create a security group for the load balancer sgName := \"k8s-elb-\" + loadBalancerName sgDescription := fmt.Sprintf(\"Security group for Kubernetes ELB %s (%v)\", loadBalancerName, serviceName) <del> securityGroupID, err = c.ensureSecurityGroup(sgName, sgDescription) </del> <ins> securityGroupID, err = c.ensureSecurityGroup(sgName, sgDescription, getLoadBalancerAdditionalTags(annotations)) </ins> if err != nil { glog.Errorf(\"Error creating load balancer security group: %q\", err) return nil, err", "positive_passages": [{"docid": "doc-en-kubernetes-a01a3c41e631760f28b69af73c7e0688234151a20f7dd4b67642a3c81f6b4dfa", "text": "The reason for what we expect is that we have tight security constraints that require us to fine tune the IAM policies for the Instance profiles that the controllers use. With a statically named tag we were able, in 1.5, to restrict the permissions in the IAM policy to act only on the k8s managed resources (ELBs, security groups). Here is the relevant part of the IAM policy: Environment: Kubernetes version (use ):OS (e.g. from /etc/os-release):Others: </details\nI believe they are moving away from the tag since there are many resources that can be shared by multiple clusters. could you use an annotation?\nWe removed the condition in roles in the end. Thank you for your suggestion.\nThat annotation affects the ELB but not any security groups that are created. can you please reopen this? You reported a real issue, and even if it no longer affects you, it needs to be tracked and fixed.\nIndeed, this might be a feature that someone else would need.\nIn fact, this is a feature I need!\nFood for thought: should we propagate the tags on the ELB to the SG, or should we introduce an annotation for the SG specifically?", "commid": "kubernetes_issue_53489", "tokennum": 265}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4eb396044987b94a7b28c5f918235203ab16001b053e86c8decaa054b5dba729", "query": "// NewKubeRegistry creates a new vanilla Registry without any Collectors // pre-registered. func NewKubeRegistry() KubeRegistry { <del> r := newKubeRegistry(version.Get()) </del> <ins> r := newKubeRegistry(BuildVersion()) </ins> return r }", "positive_passages": [{"docid": "doc-en-kubernetes-b57bf0f1b2dd71c1293d1dafb95c6e51debc5c1d26878053edb8d335b76a3a11", "text": "What would you like to be : Once a metric be deprecated, we should update the unit test accordingly if there is any. We need to work out a way for a unit test freely select codebase version, and also should make sure the unit test won't fail in the subsequent release. Why is this needed: Deprecated also needs to be protected. /sig instrumentation /assign", "commid": "kubernetes_issue_86292", "tokennum": 81}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4ece8f981e5016b56c8530fac3e36d475b39549461d5e8eccc6410ab89efdef0", "query": "// Returns true if and only if changes were made // The security group must already exist func (c *Cloud) setSecurityGroupIngress(securityGroupID string, permissions IPPermissionSet) (bool, error) { <ins> // We do not want to make changes to the Global defined SG if securityGroupID == c.cfg.Global.ElbSecurityGroup { return false, nil } </ins> group, err := c.findSecurityGroup(securityGroupID) if err != nil { glog.Warningf(\"Error retrieving security group %q\", err)", "positive_passages": [{"docid": "doc-en-kubernetes-d6a2e132f72678770d8d41e08acf9f7359a4b887e33d930dbbc18ea7ecc9db7e", "text": "/kind bug What happened: When setting an elbSecurityGroup in for AWS, and deploying multiple services with differing ports, then the security group rules flap in AWS, causing services to become inaccessible (only one will be correctly configured at a time). What you expected to happen: I expect that the configured elbSecurityGroup's rules will not be touched at all. It must be pre-configured to permit access. Alternatively, all ports for all services are queried and managed together. How to reproduce it (as minimally and precisely as possible): See above. Anything else we need to know?: Most people are not running large clusters which may hit the AWS limits, so they won't use this option, nor see this issue. Environment: Kubernetes version (use ): 1.7.1 Cloud provider or hardware configuration**: AWS OS (e.g. from /etc/os-release): CentOS 7 Kernel (e.g. ): 4.10.13-1-ARCH Install tools: Custom Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig aws\nThis is fixed by", "commid": "kubernetes_issue_50105", "tokennum": 331}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4f066e1ef1219d8400b200e9240cc51649f113dc853472d51a8c46601b646fba", "query": "// Next, we compare the current list of endpoints with the list of master IP keys formatCorrect, ipCorrect, portsCorrect := checkEndpointSubsetFormatWithLease(e, masterIPs, endpointPorts, reconcilePorts) if formatCorrect && ipCorrect && portsCorrect { <del> return nil </del> <ins> return r.epAdapter.EnsureEndpointSliceFromEndpoints(corev1.NamespaceDefault, e) </ins> } if !formatCorrect {", "positive_passages": [{"docid": "doc-en-kubernetes-12f7047d8d873a7d6bac7023fc38517c350449071b3fe2b6d53f3ea14de5351f", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: EndpointSlice for masters was not created after enabling EndpointSlice on a pre-existing cluster. Only those EndpointSlices managed by kube-controller-manager were created. What you expected to happen: EndpointSlice for masters should be created after enabling EndpointSlice on a pre-existing cluster, the same as the EndpointSlices managed by kube-controller-manager. How to reproduce it (as minimally and precisely as possible): kubeadm to create a cluster: the EndpointSlice feature by editing the kube-apiserver, kube-controller-manager, kube-proxy manifest kube-apiserver and kube-controller-manager is restarted, the EndpointSlice in namespace will be missing. Anything else we need to know?: Environment: Kubernetes version (use ):Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools:Network plugin and version (if this is a network-related bug): Others:\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/remove-triage unresolved /assign", "commid": "kubernetes_issue_84419", "tokennum": 307}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4f39664e31dc941bfda4ef0dd8c5f6ce5080304f058e8696b18463730cba6a5f", "query": "local stack_skip=\"${3:-0}\" stack_skip=$((stack_skip + 1)) <del> # Always print the error message, regardless of KUBE_VERBOSE value kube::log::error \"${message}\" # Additional debug information printed if KUBE_VERBOSE is 4 or greater </del> if [[ ${KUBE_VERBOSE} -ge 4 ]]; then local source_file=${BASH_SOURCE[${stack_skip}]} local source_line=${BASH_LINENO[$((stack_skip - 1))]}", "positive_passages": [{"docid": "doc-en-kubernetes-8a699a775e3a74244069706b35bb820e7902d476b6f1b85f7c2dea06c82b6838", "text": "appears to have been trying to improve the logging in e2e test runs, but it seems to have affected much more than that, and now when a build fails, it logs so many useless messages that you have to scroll back to see why your compile actually failed. before: after: /assign cc (re )\nGitHub didn't allow me to assign the following users: oxxenix. Note that only with read permissions, 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 : appears to have been trying to improve the logging in e2e test runs, but it seems to have affected much more than that, and now when a build fails, it logs so many useless messages that you have to scroll back to see why your compile actually failed. after: /assign cc (re ) 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\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nthanks for tracking this down. I agree that the additional error message is distracting and would like to see implemented differently so that it's not shown for manual invocations.\n/sig release\ndo you have any tips or recommendations how to implement it differently? Thanks\nIt looks like that extra ouput is a from . I'd suggest to either revert or strip BASHCOMMAND from the error message if it's not that useful.\nIt looks like what you wanted in is the location and time stamp (\"The update now displays both the specific location of the error in the code and a timestamp.\"), which is what we also get from the calltree after \"make build\". I would revert and then investigate why that shorter calltree is not shown after an E2E test failure. Keeping the calltree around as in Dan's \"before\" seems reasonable to me.", "commid": "kubernetes_issue_123133", "tokennum": 504}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4f39664e31dc941bfda4ef0dd8c5f6ce5080304f058e8696b18463730cba6a5f", "query": "local stack_skip=\"${3:-0}\" stack_skip=$((stack_skip + 1)) <del> # Always print the error message, regardless of KUBE_VERBOSE value kube::log::error \"${message}\" # Additional debug information printed if KUBE_VERBOSE is 4 or greater </del> if [[ ${KUBE_VERBOSE} -ge 4 ]]; then local source_file=${BASH_SOURCE[${stack_skip}]} local source_line=${BASH_LINENO[$((stack_skip - 1))]}", "positive_passages": [{"docid": "doc-en-kubernetes-fa3ce91d012c93a689f31707fcd49f25a383e5fcb317370a874f6097508c39c9", "text": "It shows a little bit more location info with the change. Here is how failure looks like with the change (but without BASH_COMMAND: and without the change:\nI mean, the call tree is pretty useless in the \"compile error\" case... if your problem is that the code doesn't compile, you don't need to be told what part of the build scripts it is that invokes . It's just that before it was a small amount of useless output that was easy to ignore, whereas now it's a lot of useless output, which completely pushes the useful output offscreen. But IMO, \"no backtrace\" would be nicer than \"short backtrace\"... (I realize there are probably other cases where the backtrace is useful, and I'm not saying we should get rid of it in those cases, whatever they are.)\nI agree, stack trace for compilation errors is quite useless. Unfortunately a lot of targets 'make test-e2e-node' included, build binaries, so we can't easily show traceback in one case and don't show in another. Removing BASH_COMMAND from the output looks like a good trade-off to me, though. It has a little bit more info(sometimes usefull) about callstack and less verbose than currently. I'm also ok with reverting and investigating later.\n/assign", "commid": "kubernetes_issue_123133", "tokennum": 298}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4f5d687e97f3b47522ecf5dc690ce728d640e80ca1c3f5c70ca301cce6269c7f", "query": "if err != nil { return nil, err } <ins> // Fall back to ARM API if the address is empty string. // TODO: this is a workaround because IMDS is not stable enough. // It should be removed after IMDS fixing the issue. if strings.TrimSpace(ipAddress.PrivateIP) == \"\" { return addressGetter(name) } // Use ip address got from instance metadata. </ins> addresses := []v1.NodeAddress{ {Type: v1.NodeInternalIP, Address: ipAddress.PrivateIP}, {Type: v1.NodeHostName, Address: string(name)},", "positive_passages": [{"docid": "doc-en-kubernetes-f24559fc73906a9ab29b78f7d758564488c283b5a15c64d8dd22134579e26576", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: /sig azure What happened: The internal IP address is got from instance metadata. I suspect the instance metadata may not be stable, e.g. it has undocumented rate limits (refer ). Cross refer What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:", "commid": "kubernetes_issue_69075", "tokennum": 167}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4f81abdda706697f31a515b10e565e4ed4e2cd3390a01dc9d46256a93ad68aeb", "query": "// ValidateServiceStatusUpdate tests if required fields in the Service are set when updating status. func ValidateServiceStatusUpdate(service, oldService *core.Service) field.ErrorList { allErrs := ValidateObjectMetaUpdate(&service.ObjectMeta, &oldService.ObjectMeta, field.NewPath(\"metadata\")) <del> allErrs = append(allErrs, ValidateLoadBalancerStatus(&service.Status.LoadBalancer, field.NewPath(\"status\", \"loadBalancer\"))...) </del> <ins> allErrs = append(allErrs, ValidateLoadBalancerStatus(&service.Status.LoadBalancer, field.NewPath(\"status\", \"loadBalancer\"), &service.Spec)...) </ins> return allErrs }", "positive_passages": [{"docid": "doc-en-kubernetes-e021a9a686a92d83ba285392c70089f3a0813200ee010fb06825ed96dc15cfdb", "text": "xref I think this may be one of the few cases where we can actually change the behavior in a \"breaking\" way. User creates service with , is empty Controller or user updates the status subresource, sets (not wiped or validated, should be) User updates in any way, is wiped It's clear that the is not meant to be set when is not \"LoadBalancer\". The question is: 1) Fail validation? 2) Silently discard the value? 3) Warn and then discard the value? 4) Just warn and leave it. Because we allowed it in the past, but it is so volatile, I lean towards 3. and - the people most familair with this type. Edit: PrepareForUpdate() runs before warnings. So: (1) is easy (2) is easy (4) is slightly less easy than (2) (3) is slightly less easy than (4)\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nOMG change it to clusterIP as expected Status is wiped update status as ClusterIP ... and if I edit the service back to loadbalancer it keeps the status??\n/kind bug\n/retitle Service can be set when !=\nWe talked about this one at the SIG Network meeting today. suggested we use the feature gate for deprecation option to phase the current (problematic) functionality out.\n/triage accept\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /triage accept 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", "commid": "kubernetes_issue_119700", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4f8c80e3666911d4c74f13bc3b5e8460ab02e03c2f2d91ecc8dfabca5d7e4ecb", "query": "testKubelet := newTestKubelet(t) kl := testKubelet.kubelet kl.nodeLister = testNodeLister{nodes: []api.Node{ <del> {ObjectMeta: api.ObjectMeta{Name: \"testnode\", Labels: map[string]string{\"key\": \"B\"}}}, </del> <ins> {ObjectMeta: api.ObjectMeta{Name: testKubeletHostname, Labels: map[string]string{\"key\": \"B\"}}}, </ins> }} testKubelet.fakeCadvisor.On(\"MachineInfo\").Return(&cadvisorApi.MachineInfo{}, nil) testKubelet.fakeCadvisor.On(\"DockerImagesFsInfo\").Return(cadvisorApiv2.FsInfo{}, nil)", "positive_passages": [{"docid": "doc-en-kubernetes-d16ca614c05197aa8b2652e3bf008c3a9a5ce41d960188a2ba3459b13d8b1102", "text": "Looks like some kubelet unit tests perform a lookupIp which ends up depending on the health of the local resolver. Specifically has this failing: Which leads to the test in: And we recently swapped out the node names from testnode to 127.0.0.1, so probably the culprit?\n/ref\nInteresting. I did swap out the node names in the unit test as part of to be 127.0.0.1, party because I thought that it wouldn't have any problems resolving during unit tests.\n/cc", "commid": "kubernetes_issue_8549", "tokennum": 113}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4f8c80e3666911d4c74f13bc3b5e8460ab02e03c2f2d91ecc8dfabca5d7e4ecb", "query": "testKubelet := newTestKubelet(t) kl := testKubelet.kubelet kl.nodeLister = testNodeLister{nodes: []api.Node{ <del> {ObjectMeta: api.ObjectMeta{Name: \"testnode\", Labels: map[string]string{\"key\": \"B\"}}}, </del> <ins> {ObjectMeta: api.ObjectMeta{Name: testKubeletHostname, Labels: map[string]string{\"key\": \"B\"}}}, </ins> }} testKubelet.fakeCadvisor.On(\"MachineInfo\").Return(&cadvisorApi.MachineInfo{}, nil) testKubelet.fakeCadvisor.On(\"DockerImagesFsInfo\").Return(cadvisorApiv2.FsInfo{}, nil)", "positive_passages": [{"docid": "doc-en-kubernetes-4a4c75dd985aaeba56d487bbde17d68f0425afc5d7e1167fdf1a1abcb97cd0b6", "text": "cc\nWhat is the environment where you are running the tests? They pass for me on my mac, a linux box, and shippable seems to be passing them as well.\nI couldn 't reproduce the failure either.\nI'm out right now; i'll try them when i get back. For the record, I run hack/test- Paul Morie wrote:\nAhem FTR This acronym is going to go quad-plat Paul Morie wrote:\nI ran on both platforms and saw the tests pass.\nI'm still seeing it. Won't have bandwidth to dig in personally until tomorrow.\nseeing a similar failure after a git pull\nI knew I wasn't crazy\nenvironment: fedora 21, golang: 1.4, docker: 1.6\nI think I see the problem. When I set the node name to in the test I was assuming it would parse as a valid ip address and not end up at the LookupIP call. But only the node name (and not the kubelet hostname) is being set (except in my new test where I ) so it's trying to do a lookup. Do you think you could test just changing the default hostname from \"testnode\" to \"127.0.0.1\" and see if that fixes it for you?\nTrying now\nI still get failures but no panic / threaddump.\ngist coming\nthis looks like again?\nGood that it isn't panicing any longer. I can dig into the test failures tomorrow (I think it should be relatively simple to resolve).\ncool, thanks for looking\nPasses in master now for me. Closing.\nFYI, they will break again once goes in, and then we can merge my PR to see if that fixes it for you.\n:+1:\nis in -- are these tests breaking again?\nI just rebased which I think will fix them.\nThey are breaking again.\nis on it.", "commid": "kubernetes_issue_8522", "tokennum": 407}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4fab3e8522035e75ffe554d48485ba54c9e39052ce127d23763041f94663e9bb", "query": "} } <ins> func TestMinionRESTWithHealthCheck(t *testing.T) { minionRegistry := registrytest.NewMinionRegistry([]string{}, api.NodeResources{}) minionHealthRegistry := HealthyRegistry{ delegate: minionRegistry, client:   &notMinion{minion: \"m1\"}, } ms := NewREST(&minionHealthRegistry) ctx := api.NewContext() c, err := ms.Create(ctx, &api.Minion{ObjectMeta: api.ObjectMeta{Name: \"m1\"}}) if err != nil { t.Errorf(\"insert failed\") } result := <-c if m, ok := result.Object.(*api.Minion); !ok || m.Name != \"m1\" { t.Errorf(\"insert return value was weird: %#v\", result) } if _, err := ms.Get(ctx, \"m1\"); err == nil { t.Errorf(\"node is unhealthy, expect no result from apiserver\") } } </ins> func contains(nodes *api.MinionList, nodeID string) bool { for _, node := range nodes.Items { if node.Name == nodeID {", "positive_passages": [{"docid": "doc-en-kubernetes-30529ae066bc3d8742ebaf2b5d541b47e2e9d65d08ef4d2580a588e88b337906", "text": "apiserver reports creation failure if a node is not ready (unhealthy, or kubelet is not ready), but the api object is already stored in master. extracted from and A short term solution is to have health_registry check node health upon creation, not just on retrieving. Or ignore unhealthy node. A long term solution might fall into the interface revamp\nWhy can't apiserver accept an unhealthy minion.\nWhat's the point of having an unhealthy minion that we'll never be able to use? One reason I can think of is that the minion can later becomes healthy and thus a valid node in k8s. But for now, as we don't have the ability to handle unhealthy node, delegate the responsibility to user makes more sense. However, I admit the title is misleading. What I really what to convey is that kubernetes currently allow registrying unhealthy node, by storing it in RESTStorage. But the create operation reports fail because the node can't pass health checking. I don't think this is the right behavior. We can either return success and do health check later, or return failure and do not store it. (i prefer the latter one for the above reason).\nI tend to think that we should accept unhealthy minions - minions may go in and out of health, or go up and down at any time - so trying ensure health at registration time seems like a fruitless effort since we have to handle the error cases anyway.\nI've no problem with accepting unhealthy minions, and I agree with your point. The real problem here is that the apiserver returns an inconsistent status. For example, if I have an unhealthy minion that I want to registry. From user's perspective, the registration fails, because apiserver returns an error (resource not found). So I retry, but apiserver returns failure again; this time, the error is resource already exists, no matter the minion is healthy or not.\n- yes, we should remove the health check as part of the registration and just report success. agree there is inconsistency.\n+1 On Nov 7, 2014 8:48 AM, \"Derek Carr\" wrote:\nSeems like it's a clients responsibility to warn the user that a node might not be available prior to it being , but the the master's responsibility to assume that all properly specified nodes are reachable before making decisions regarding using a node.", "commid": "kubernetes_issue_2192", "tokennum": 533}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4fab3e8522035e75ffe554d48485ba54c9e39052ce127d23763041f94663e9bb", "query": "} } <ins> func TestMinionRESTWithHealthCheck(t *testing.T) { minionRegistry := registrytest.NewMinionRegistry([]string{}, api.NodeResources{}) minionHealthRegistry := HealthyRegistry{ delegate: minionRegistry, client:   &notMinion{minion: \"m1\"}, } ms := NewREST(&minionHealthRegistry) ctx := api.NewContext() c, err := ms.Create(ctx, &api.Minion{ObjectMeta: api.ObjectMeta{Name: \"m1\"}}) if err != nil { t.Errorf(\"insert failed\") } result := <-c if m, ok := result.Object.(*api.Minion); !ok || m.Name != \"m1\" { t.Errorf(\"insert return value was weird: %#v\", result) } if _, err := ms.Get(ctx, \"m1\"); err == nil { t.Errorf(\"node is unhealthy, expect no result from apiserver\") } } </ins> func contains(nodes *api.MinionList, nodeID string) bool { for _, node := range nodes.Items { if node.Name == nodeID {", "positive_passages": [{"docid": "doc-en-kubernetes-7568b4abf7e2f804d9652dc70d160bdc940baf27110dcb02262716f8b93b0df2", "text": "There's very little difference between an admin stopping a VM without clearing Kube and adding a node to the cluster prior to it being fully reachable (I think).\n\"clients responsibility\" ? if we enable kubectl to create minions, it would be kubectl who should check if the minion is reachable and complain? I'm not sure what 'client' means. (but I agree 100%, don't report failure adding a minion just because it isn't reachable)\nnode controller plugin should also give warning", "commid": "kubernetes_issue_2192", "tokennum": 117}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4fadf89fecb9066a77c7d7c041085683420e5fd347aff512821c19608960a959", "query": "defer backendServer.Close() defer func() { <del> if called != tc.ExpectCalled { </del> <ins> if called := atomic.LoadInt32(&timesCalled) > 0; called != tc.ExpectCalled { </ins> t.Errorf(\"%s: expected called=%v, got %v\", tcName, tc.ExpectCalled, called) } }()", "positive_passages": [{"docid": "doc-en-kubernetes-dde8d0812f4d036029fc33418cfa6f164f8f025662aa48e3db09b87dd15763e4", "text": "There are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig api-machinery", "commid": "kubernetes_issue_49413", "tokennum": 102}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4fb13084229a53108221cf754065944b11361544c839f047082b767d835d4c9e", "query": "#     sleep 4 #     i=$[$i+1] #   done <del> apiVersion: v1beta1 </del> <ins> apiVersion: v1beta3 </ins> kind: Pod <del> id: synthetic-logger-10lps-pod desiredState: manifest: version: v1beta1 id: synth-logger-10lps containers: - name: synth-lgr image: ubuntu:14.04 command: [\"bash\", \"-c\", \"i=\"0\"; while true; do echo -n \"`hostname`: $i: \"; date --rfc-3339 ns; sleep 0.1; i=$[$i+1]; done\"] labels: name: synth-logging-source </del> <ins> metadata: creationTimestamp: null labels: name: synth-logging-source name: synthetic-logger-10lps-pod spec: containers: - args: - bash - -c - 'i=\"0\"; while true; do echo -n \"`hostname`: $i: \"; date --rfc-3339 ns; sleep 0.1; i=$[$i+1]; done' image: ubuntu:14.04 name: synth-lgr </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-bc75029de49571476e249812075ff7ffff85fb8014f5cfe5e32228962baa98b2", "text": "Hi , I followed the instructions in examples/logging-demo, and there was no \"external IP\" field for elasticsearch-logging or kibana-logging, as shown below: I start up my cluster via cluster/kube- Did I miss something or is it a bug? Thanks.\nCorrect. This demo does not create an ELB so there is no external IP address. Access is via service proxy at the master. Type: and you should see the URLs for Elasticsearch and Kibana.\nplease let us know whether: a. Satnam's comment resolves your issue b. the demo should be updated to prevent this misunderstanding c. the issue isn't resolved Thank you!\nYes, Satnam's comment resolve the issue. I updated the demo in .\nAwesome, thanks for sending the patch! We'll discuss there. Always fantastic to have docs updated regularly by folks trying them.", "commid": "kubernetes_issue_7818", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4fc1901c978ddadeada0e4482416bf2242f52bab833618b3df3be6d7c4e30f2c", "query": "return err } <del> // GetDiskLun finds the lun on the host that the vhd is attached to, given a vhd's diskName and diskURI func (ss *scaleSet) GetDiskLun(diskName, diskURI string, nodeName types.NodeName) (int32, error) { </del> <ins> // GetDataDisks gets a list of data disks attached to the node. func (ss *scaleSet) GetDataDisks(nodeName types.NodeName) ([]compute.DataDisk, error) { </ins> _, _, vm, err := ss.getVmssVM(string(nodeName)) if err != nil { <del> return -1, err </del> <ins> return nil, err </ins> } <del> disks := *vm.StorageProfile.DataDisks for _, disk := range disks { if disk.Lun != nil && (disk.Name != nil && diskName != \"\" && *disk.Name == diskName) || (disk.Vhd != nil && disk.Vhd.URI != nil && diskURI != \"\" && *disk.Vhd.URI == diskURI) || (disk.ManagedDisk != nil && *disk.ManagedDisk.ID == diskURI) { // found the disk glog.V(4).Infof(\"azureDisk - find disk: lun %d name %q uri %q\", *disk.Lun, diskName, diskURI) return *disk.Lun, nil } } return -1, fmt.Errorf(\"Cannot find Lun for disk %s\", diskName) } // GetNextDiskLun searches all vhd attachment on the host and find unused lun // return -1 if all luns are used func (ss *scaleSet) GetNextDiskLun(nodeName types.NodeName) (int32, error) { _, _, vm, err := ss.getVmssVM(string(nodeName)) if err != nil { return -1, err } used := make([]bool, maxLUN) disks := *vm.StorageProfile.DataDisks for _, disk := range disks { if disk.Lun != nil { used[*disk.Lun] = true } } for k, v := range used { if !v { return int32(k), nil } } return -1, fmt.Errorf(\"All Luns are used\") } // DisksAreAttached checks if a list of volumes are attached to the node with the specified NodeName func (ss *scaleSet) DisksAreAttached(diskNames []string, nodeName types.NodeName) (map[string]bool, error) { attached := make(map[string]bool) for _, diskName := range diskNames { attached[diskName] = false } _, _, vm, err := ss.getVmssVM(string(nodeName)) if err != nil { if err == cloudprovider.InstanceNotFound { // if host doesn't exist, no need to detach glog.Warningf(\"azureDisk - Cannot find node %q, DisksAreAttached will assume disks %v are not attached to it.\", nodeName, diskNames) return attached, nil } return attached, err } disks := *vm.StorageProfile.DataDisks for _, disk := range disks { for _, diskName := range diskNames { if disk.Name != nil && diskName != \"\" && *disk.Name == diskName { attached[diskName] = true } } </del> <ins> if vm.StorageProfile.DataDisks == nil { return nil, nil </ins> } <del> return attached, nil </del> <ins> return *vm.StorageProfile.DataDisks, nil </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-6cfc50824280daf2f66f5e84f9a8c720c316cfa724f1e90fa02f306c798e5010", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind cleanup What happened: VirtualMachineScaleSetVM and VirtualMachine are different data structures (because of different API versions), so the disk attach operation seems duplicate between vm and vmss. That means although disk operations are in same logic, some duplication are still required now. They should use same api version in the future and should be merged into same code base, e.g. move sharing logic to Refer What you expected to happen: vmss and vm disk operations should share same code logic. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\nI have checked with currently we can\u2019t merge, e.g. following two structs are different since they using different sdk-for-azure versions. While in the end when sdk-for-azure version is upgraded, above two versions should be same and at that time, we should merge functions like \u2018AttachDisk\u2019, \u2018DetachDiskByName\u2019, 'GetDiskLun', GetNextDiskLun, DisksAreAttached", "commid": "kubernetes_issue_59736", "tokennum": 313}], "negative_passages": []}
{"query_id": "q-en-kubernetes-4fed9bab438f616a81f60cc449dd8bf07ab7c727e737685058e34d63b8e1473b", "query": "if err != nil { return err } <ins> if len(rsrc.Versions) == 0 { return fmt.Errorf(\"ThirdPartyResource %s has no defined versions\", rsrc.Name) } </ins> plural, _ := meta.KindToResource(unversioned.GroupVersionKind{ Group:   group, Version: rsrc.Versions[0].Name,", "positive_passages": [{"docid": "doc-en-kubernetes-65858ef6270e846dbad645a3cdb03be72308acbcbd2d437380bbe522248f5825", "text": "FYI. Currently the field of TPR is marked as which is wrong, actually if you try to create a TPR with empty versions, it will cause api server panic. Versions should be necessary field of TPR, we should validate this somehow.", "commid": "kubernetes_issue_36991", "tokennum": 52}], "negative_passages": []}
{"query_id": "q-en-kubernetes-501826fc405106fc0e2eee6b284f52a0e6dd924d9470e69991737ad714eb5739", "query": "return unmountedVolumes } <ins> func (asw *actualStateOfWorld) SyncReconstructedVolume(volumeName v1.UniqueVolumeName, podName volumetypes.UniquePodName, outerVolumeSpecName string) { asw.Lock() defer asw.Unlock() if volumeObj, volumeExists := asw.attachedVolumes[volumeName]; volumeExists { if podObj, podExists := volumeObj.mountedPods[podName]; podExists { if podObj.outerVolumeSpecName != outerVolumeSpecName { podObj.outerVolumeSpecName = outerVolumeSpecName asw.attachedVolumes[volumeName].mountedPods[podName] = podObj } } } } </ins> func (asw *actualStateOfWorld) newAttachedVolume( attachedVolume *attachedVolume) AttachedVolume { return AttachedVolume{", "positive_passages": [{"docid": "doc-en-kubernetes-95820dc44dfb57216fa4466fe0b08e35d101b3576d175fcc0793312a1c18dfad", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --We have even encountered such case that pod continuously reports \u201cUnable to attach or mount volumes for pod;...\u201d when kubelet restarted. The reasons are listed in details as below: , as result of apiserver instantaneous unstablility, dswp get pvc\u2018s pv spec failed, then the pvc volume does not be to dsw. , syncStates() lists all the volume directories locally, and recontructs the volume from local volume, if the volume isn't in dsw, it will put the recontructed volume to asw, but now the volume.OuterVolumeSpecName isn't correct. chance, at this time, In , the fail to pvc volume is to dsw again normally in reconcile() -mountAttachVolumes(), it compares dsw and asw by volume's innerVolumename, it's all the same. but it could not sense the OuterVolumeSpecName dismatch. so it will not re-mount again to update asw cache , it checks pod's volume attach or mount success by comparing volume.OuterVolumeSpecName and , but this pv'c OuterVolumeSpecName isn't correct in asw. so pod continuously reports \u201cUnable to attach or mount volumes for pod;...\u201d reconcile() could sense the reconstruct volume's dismatch to the dsw, then re-mount again to make volume cache consistency Kubernetes version (use ): 1.19.4 Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig node\n/triage accepted\n/assign\nCC\nI think this is a point that can be optimized. /cc\nI will give a fix for this\nThanks for reporting the issue, this innerSpecName and outerSpecName are confusing and cause issues. Please ping me for review when you have a fix. Thanks!\nPlease don't triage your own issues immediately, give someone else a chance to review them :( /sig storage\nokay, I know", "commid": "kubernetes_issue_103143", "tokennum": 528}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5029439eefc77871d6020e1da636d97ed0d8d697cb6a2838ec272634ed972dbc", "query": "// DetachDisk detaches the disk specified by vmDiskPath func (vm *VirtualMachine) DetachDisk(ctx context.Context, vmDiskPath string) error { <del> vmDiskPath = RemoveStorageClusterORFolderNameFromVDiskPath(vmDiskPath) </del> device, err := vm.getVirtualDeviceByPath(ctx, vmDiskPath) if err != nil { klog.Errorf(\"Disk ID not found for VM: %q with diskPath: %q\", vm.InventoryPath, vmDiskPath)", "positive_passages": [{"docid": "doc-en-kubernetes-e1df151812a738ca8d7e9f97519d671c643638f3ca9d9400cc430f5f7a7d204c", "text": "When user creates a static PV using folder name in path: on vSAN backed datastore then detach disk does not work because check fails - The code expects folder name to be UUID but it does not and hence it determines disk is not attached to the node and hence no detach is ever performed. /sig storage cc", "commid": "kubernetes_issue_95121", "tokennum": 68}], "negative_passages": []}
{"query_id": "q-en-kubernetes-50351b30c8b2042224189c4c77656beaf5f33f02c22ef389866bc6c70b9958a4", "query": "// satisfy the pod topology spread constraints. Hence it needs to preempt another low pod // to make the Pods spread like [<high>, <medium, low>]. runPausePod(f, mediumPodCfg) <del> e2epod.WaitForPodNotPending(cs, ns, mediumPodCfg.Name) </del> ginkgo.By(\"Verify there are 3 Pods left in this namespace\") wantPods := sets.NewString(\"high\", \"medium\", \"low\") <del> podList, err := cs.CoreV1().Pods(ns).List(context.TODO(), metav1.ListOptions{}) pods := podList.Items </del> <ins> var pods []v1.Pod // Wait until the number of pods stabilizes. Note that `medium` pod can get scheduled once the // second low priority pod is marked as terminating. // TODO: exact the wait.PollImmediate block to framework.WaitForNumberOfRunningPods. err := wait.PollImmediate(framework.Poll, framework.PollShortTimeout, func() (bool, error) { podList, err := cs.CoreV1().Pods(ns).List(context.TODO(), metav1.ListOptions{}) // ignore intermittent network error if err != nil { return false, nil } pods = podList.Items return len(pods) == 3, nil }) </ins> framework.ExpectNoError(err) <del> framework.ExpectEqual(len(pods), 3) </del> for _, pod := range pods { // Remove the ordinal index for low pod.", "positive_passages": [{"docid": "doc-en-kubernetes-d2133e059f55329e352d657a74769e784cffa355877b91f0fede5bbe2083c4fd", "text": "<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI --Which jobs are flaking: [sig-scheduling] SchedulerPreemption [Serial] PodTopologySpread Preemption validates proper pods are preempted Which test(s) are flaking: Testgrid link: Reason for failure: It's likely when the preemptor preempts low-priority pods, and gets running, the low-priority pods are still terminating. tries to wait for all low-priority pods to be totally deleted and do the final check. Anything else we need to know: links to appreciated links to specific failures in spyglass appreciated\n/sig scheduling /assign", "commid": "kubernetes_issue_88680", "tokennum": 169}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5095196fd76455ec237af885bcf70df1e1b7988961d8e2d1e84e47117855ade2", "query": "// applyPlatformSpecificDockerConfig applies platform-specific configurations to a dockertypes.ContainerCreateConfig struct. // The containerCleanupInfo struct it returns will be passed as is to performPlatformSpecificContainerCleanup <del> // after either: //   * the container creation has failed //   * the container has been successfully started //   * the container has been removed // whichever happens first. </del> <ins> // after either the container creation has failed or the container has been removed. </ins> func (ds *dockerService) applyPlatformSpecificDockerConfig(request *runtimeapi.CreateContainerRequest, createConfig *dockertypes.ContainerCreateConfig) (*containerCleanupInfo, error) { cleanupInfo := &containerCleanupInfo{}", "positive_passages": [{"docid": "doc-en-kubernetes-486ca0159276eedd0d2aa336961ee5fd6fb83d0ac97af7f3f9c8c863d43fcef2", "text": "What would you like to be : Periodically remove cleanupInfos for old containers from dockershim's map. One way of doing that would be to just forget about s older than say an hour, as they should always be short-lived. Why is this needed: introduced a new in-memory map for the dockershim, that could potentially (in pathological cases) cause memory leaks - for containers that use GMSA cred specs, get created successfully, but then never get started nor removed. This might be okay for the alpha release of the GMSA feature, but should be addressed in the beta. See\n/assign wk8\n/sig windows\n/milestone v1.15\ngot moved out. let's move this issue with it as well /milestone v1.16\nHello! I'm bug triage lead for the 1.16 release cycle and considering this issue is tagged for 1.16, but not updated for a long time, I'd like to check its status. The code freeze is starting on August 29th (about 1.5 weeks from now), which means that there should be a PR ready (and merged) until then. Do we still target this issue to be fixed for 1.16?\n: yup we'd love to have this in 1.16, still waiting for kind reviewers on :) ...", "commid": "kubernetes_issue_74843", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-50e13d61eba1a90973b7a8a15336d0853f022952e4eaea242723b1d75d68d6b1", "query": "return } <ins> func isHostRunningCgroupV2(f *framework.Framework, host string) bool { result, err := e2essh.SSH(\"stat -fc %T /sys/fs/cgroup/\", host, framework.TestContext.Provider) framework.ExpectNoError(err) framework.ExpectEqual(result.Code, 0) // 0x63677270 == CGROUP2_SUPER_MAGIC // https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html return strings.Contains(result.Stdout, \"cgroup2\") || strings.Contains(result.Stdout, \"0x63677270\") } </ins> func getNpdPodStat(f *framework.Framework, nodeName string) (cpuUsage, rss, workingSet float64) { summary, err := e2ekubelet.GetStatsSummary(f.ClientSet, nodeName) framework.ExpectNoError(err)", "positive_passages": [{"docid": "doc-en-kubernetes-0c07e91eb7d66ee92c3b6d05f523cece58039dffcf1123c44ba752c30922deab", "text": "N/A [sig-node] NodeProblemDetector: N/A https://prow- Not cgroupv2 compatible when access cpu and memory data\n/sig node\nHi, can i work on this ?\nSure. Thanks\n/assign\n/triage accepted\n/priority important-soon\n/cc\nare you still working on this? Were you able to setup environment to repro the test failure? Let us know if you need any help. Thanks!\nSorry for the delay, I followed the wrong guide and ended up getting stuck. But now I have managed to set it up. Please give me few more days to work on it.\nThanks Feel free to reach out here or on slack if you need any help, thanks for working on this!\n/retitle Make nodeproblemdetector test cgroupv2 compatible\nFailing job:\nTestgrid:", "commid": "kubernetes_issue_105178", "tokennum": 180}], "negative_passages": []}
{"query_id": "q-en-kubernetes-50e34dbdfa074989caefec4d1422fdc38bfac7d62813c9d120913b116441eb40", "query": "} // Add volume to desired state of world <del> _, err = dswp.desiredStateOfWorld.AddPodToVolume( </del> <ins> uniqueVolumeName, err := dswp.desiredStateOfWorld.AddPodToVolume( </ins> uniquePodName, pod, volumeSpec, podVolume.Name, volumeGidValue) if err != nil { klog.ErrorS(err, \"Failed to add volume to desiredStateOfWorld\", \"pod\", klog.KObj(pod), \"volumeName\", podVolume.Name, \"volumeSpecName\", volumeSpec.Name())", "positive_passages": [{"docid": "doc-en-kubernetes-95820dc44dfb57216fa4466fe0b08e35d101b3576d175fcc0793312a1c18dfad", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --We have even encountered such case that pod continuously reports \u201cUnable to attach or mount volumes for pod;...\u201d when kubelet restarted. The reasons are listed in details as below: , as result of apiserver instantaneous unstablility, dswp get pvc\u2018s pv spec failed, then the pvc volume does not be to dsw. , syncStates() lists all the volume directories locally, and recontructs the volume from local volume, if the volume isn't in dsw, it will put the recontructed volume to asw, but now the volume.OuterVolumeSpecName isn't correct. chance, at this time, In , the fail to pvc volume is to dsw again normally in reconcile() -mountAttachVolumes(), it compares dsw and asw by volume's innerVolumename, it's all the same. but it could not sense the OuterVolumeSpecName dismatch. so it will not re-mount again to update asw cache , it checks pod's volume attach or mount success by comparing volume.OuterVolumeSpecName and , but this pv'c OuterVolumeSpecName isn't correct in asw. so pod continuously reports \u201cUnable to attach or mount volumes for pod;...\u201d reconcile() could sense the reconstruct volume's dismatch to the dsw, then re-mount again to make volume cache consistency Kubernetes version (use ): 1.19.4 Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig node\n/triage accepted\n/assign\nCC\nI think this is a point that can be optimized. /cc\nI will give a fix for this\nThanks for reporting the issue, this innerSpecName and outerSpecName are confusing and cause issues. Please ping me for review when you have a fix. Thanks!\nPlease don't triage your own issues immediately, give someone else a chance to review them :( /sig storage\nokay, I know", "commid": "kubernetes_issue_103143", "tokennum": 528}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5170f5a1d063e4899c679a04c657bb8a17bb4b1291290ff07964a8c13f493182", "query": "\"io/ioutil\" \"os\" \"reflect\" <ins> \"strings\" </ins> \"testing\" \"github.com/imdario/mergo\" <del> \"k8s.io/kubernetes/pkg/client/restclient\" </del> clientcmdapi \"k8s.io/kubernetes/pkg/client/unversioned/clientcmd/api\" )", "positive_passages": [{"docid": "doc-en-kubernetes-f651131826f05881213cb9e37bd90a3c65eb2d3012bfdb53d9a39fc66f409d28", "text": "In 1.1, if you specify \"current-context: i-do-not-exist\" in a kubeconfig, and there's no matching context by that name in the contexts, kubelet silently uses what I assume is either an empty or a default configuration. This can result in hilarity like wondering why your kubelet isn't using the TLS settings you provided, and spending several hours debugging the whole stack only to discover that you typo'd current-context :). It would be better if kubelet and other users of errored out on such a misconfiguration, to make the failure obvious and trivial.\ncc\nI think kubelet silently uses an empty configuration. Guess we should give a waring here.\nDid you start to work on this?\nBelow is related code: can you confirm this? Besides if we want to log a waring in kubelet, we may need to get in kubelet.\ncc\ncc\nI believe kubelet already uses . Adding a check in that current context exists if specified sounds like the right approach.\nAre there any backwards compatibility implications here? would this break users who have existing configs (that fallback to default namespace)? , Jeff Lowdermilk wrote:\nI think kubelet directly use not . Also already checks whether the user-specified current context exists, the problem is that if not exist, we just skip. We need to do something if the current context not exist, like log a warning.\nErroring on a specified and bad seems reasonable. If it is not specified and there's only one option, I don't think we should fail.\nyeap, the case is that user specify the but not exist, in such case we should just fail.\nIf no one is working on this I can take it.\nI think this is the root cause. Basically we should error on this not exist context. If you have extra bandwidth, please go ahead :)\nThis is related to - the defaulting is what allows us to continue. When that merges, only kubectl will have the \"use localhost:8080\" as defaulting.", "commid": "kubernetes_issue_21062", "tokennum": 453}], "negative_passages": []}
{"query_id": "q-en-kubernetes-51bbd77076a9564d5ea6ba2d43ab96ecbd50c3cad61418190683694829d5e355", "query": "hosts := []string{} for _, n := range nodelist.Items { for _, addr := range n.Status.Addresses { <del> if addr.Type == addrType { </del> <ins> if addr.Type == addrType && addr.Address != \"\" { </ins> hosts = append(hosts, addr.Address) break }", "positive_passages": [{"docid": "doc-en-kubernetes-3fbd6fe4c52deabe3c900459c29c36a04807fdd1453263d11d2244d21f4a4f4a", "text": "Public IPs are expensive resources. Given that we're running scalability tests on 5k-node clusters, we are unnecessarily consuming 5k IPs which is a lot. We should switch our tests so that nodes have only private IP addresses. We are going to do that by configuring NAT so that nodes can talk to outside world (e.g. to download image from dockerhub). But that also requires changing some correctness tests which assume public IPs.\nTo summarize recent work: setting up private gce clusters with nat, feature is gated via the env test and dashboard with correctness tests on gce private cluster - https://k8s- 27 tests fail on fixing the tests - should fix majority of them\nIssues 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\n/remove-lifecycle stale /lifecycle frozen\n- is there anything missing to be done here?\nNo, we can close this one. It was done long time ago. Thanks for catching /close\nClosing this issue. <detailsIn response to : No, we can close this one. It was done long time ago. Thanks for catching 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", "commid": "kubernetes_issue_76374", "tokennum": 335}], "negative_passages": []}
{"query_id": "q-en-kubernetes-51f0e5389e55c3403487e645dcbda348c0658435aa3034fa93a549f559d1920d", "query": "setMaxElements:   42, expectedSetCost:  8, }, <ins> { name:             \"enums with maxLength equals to the longest possible value\", schemaGenerator:  genEnumWithRuleAndValues(\"self.contains('A')\", \"A\", \"B\", \"C\", \"LongValue\"), expectedCalcCost: 2, setMaxElements:   1000, expectedSetCost:  401, }, </ins> } for _, testCase := range cases { t.Run(testCase.name, func(t *testing.T) {", "positive_passages": [{"docid": "doc-en-kubernetes-d87f35a9862b77934b500147b1ec4bb0e958c531e2fdcae282b21499e2f51131", "text": "pointed out to me that a CEL x-kubernetes-validations rule in a CRD was hitting the estimated cost limit when performing a simple \"string has prefix\" check on an en enum field. Putting a limit in the OpenAPI of the enum string field fixed the problem, but having to add a limit like this is counter-intuitive and unnecessary, since the allowed enum values already make the max allowed length obvious. The apiserver automatically computes the max length of an enum as the length of the longest allowed enum value. I believe we already refuse evaluate CEL rules on values that fail OpenAPI value validation, since we rely in the value validations to establish all length limits. I haven't tested it locally, but something like this should work (given enough nested arrays): As a workaround, one can manually set on the string enum, e.g.: 25+ All No response No response No response No response\n/sig api-machinery /triage accepted /assign\n/assign\nI wasn't sure if we special-cased the maxLength / maxItems / maxProperties failures, or if all openapi validation had to pass before we started messing with CEL evaluation\nit looks like we currently special-case specific openapi errors that short-circuit CEL validation, I'm not sure an enum validation failure would currently prevent evaluation:\nThe enum err is converted to () error which is not short-circuit here. But for defaulting case, all error would be short-circuit. I would suggest to add error into the blockingErr list to short-circuit CEL validation. Would this make sense?\nyeah, that sounds good if we're going to rely on it to catch things that are longer than the maximum length enum value", "commid": "kubernetes_issue_119511", "tokennum": 383}], "negative_passages": []}
{"query_id": "q-en-kubernetes-526f7f53990dc292b643c28160c7416d34feca611a8a06ecf38a21aead0e211b", "query": "--allow \"tcp:3389\" & fi fi <ins> kube::util::wait-for-jobs || { code=$? echo -e \"${color_red}Failed to create firewall rules.${color_norm}\" >&2 exit $code } </ins> } function expand-default-subnetwork() {", "positive_passages": [{"docid": "doc-en-kubernetes-99c81b4f57584ea95d5f96a4bd9eeeb1b9aeab22e948ca7c4386b5070fb15e2e", "text": "Kubernetes e2e suite [It] [sig-network] Firewall rule should have correct firewall rules for e2e cluster See also a similar cluster with the same test failing: /kind failing-test /kind flake /sig network\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_111580", "tokennum": 141}], "negative_passages": []}
{"query_id": "q-en-kubernetes-52740fa1a436fe1f8f9498693045961b87b34c8fc5f3f1b35ed639093611d5a5", "query": "WorkingDir string `gcfg:\"working-dir\"` // Soap round tripper count (retries = RoundTripper - 1) RoundTripperCount uint `gcfg:\"soap-roundtrip-count\"` <del> // Deprecated as the virtual machines will be automatically discovered. </del> <ins> // Is required on the controller-manager if it does not run on a VMware machine </ins> // VMUUID is the VM Instance UUID of virtual machine which can be retrieved from instanceUuid // property in VmConfigInfo, or also set as vc.uuid in VMX file. // If not set, will be fetched from the machine via sysfs (requires root)", "positive_passages": [{"docid": "doc-en-kubernetes-4b4094f56c55cfa490f4fdbec1ba6d40dc83e208d3fe25d4f173459fce063c48", "text": "Is this a BUG REPORT or FEATURE REQUEST?: What happened: Currently the vsphere cloud provider blocks the controller-manager from running if its running on a non-vmware host, because it reads and checks if its content starts with . What you expected to happen: The controller manager to start How to reproduce it (as minimally and precisely as possible): Start a on a non-vmware environment with the flags set Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/sig vmware\ncan you please share some more context- Why do you want vSphere cloud provider to work with non-vmware host (I believe you mean ESXi)? Where is this requirement coming from.\nWe are building a Kubernetes cluster management solution which does Kubernetes in Kubernetes and works by creating the control planes in one cluster, then creating worker instances on one of the supported platforms, among them vsphere. Currently the cluster hosting the control planes (We call it seed cluster) has to run on ESXi, otherwise the controller-manager crashes. Having the check in place for the Kubelets is completely fine and definitely makes sense, but for the controller-manager it should IMHO not be required.", "commid": "kubernetes_issue_65145", "tokennum": 300}], "negative_passages": []}
{"query_id": "q-en-kubernetes-52817c8519fe40c88f58fb826244009bc22e2b2f4e5cb87925350f8f17c148c9", "query": "stdoutBuf := bytes.NewBuffer(nil) stderrBuf := bytes.NewBuffer(nil) w := newLogWriter(stdoutBuf, stderrBuf, &LogOptions{since: test.since, timestamp: test.timestamp, bytes: -1}) <del> err := w.write(msg) </del> <ins> err := w.write(msg, true) </ins> assert.NoError(t, err) assert.Equal(t, test.expectStdout, stdoutBuf.String()) assert.Equal(t, test.expectStderr, stderrBuf.String())", "positive_passages": [{"docid": "doc-en-kubernetes-1611cacb700fc7bde4bed341ff7dc392aeb6c35e6c0f63ce6a10b84981e8d04a", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Docker has a hardcoded 16K limit on log line length, which splits lines longer than that into multiple messages in the log file. in , however, doesn't account for this when is set to and prints the timestamp in front of every entry in the log file instead of every logical line. This leads to random timestamps appearing in the middle of log lines, potentially breaking the applications that parse these logs. What you expected to happen: inserts timestamps once per logical line, so original log data is preserved. Alternatively, allow API to request the logs in a sane format like JSON, which would allow merging the lines back and combining them with the timestamps more intelligently on the application side. How to reproduce it (as minimally and precisely as possible): Create : apiVersion: v1 kind: Pod metadata: name: log-lines spec: containers: name: main image: busybox command: ['sh', '-c', 'while sleep 1; do echo -n ; for i in $(seq 1 ); do echo -n A; done; echo ; done'] Start the pod with Fetch the logs with , or using the API () Observe random timestamps inserted in the middle of the log lines. Environment: Kubernetes version (use ):\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI will work on it. /sig cli /remove-sig node\nThe logs are being corrupted by the API endpoint in kubelet, so shouldn't it be in scope of SIG node?\nThe log is not corrupted by k8s. The same log could be got using \"docker container logs -t CONTAINERID\" I think you should post your requirement to Docker.", "commid": "kubernetes_issue_77603", "tokennum": 465}], "negative_passages": []}
{"query_id": "q-en-kubernetes-52817c8519fe40c88f58fb826244009bc22e2b2f4e5cb87925350f8f17c148c9", "query": "stdoutBuf := bytes.NewBuffer(nil) stderrBuf := bytes.NewBuffer(nil) w := newLogWriter(stdoutBuf, stderrBuf, &LogOptions{since: test.since, timestamp: test.timestamp, bytes: -1}) <del> err := w.write(msg) </del> <ins> err := w.write(msg, true) </ins> assert.NoError(t, err) assert.Equal(t, test.expectStdout, stdoutBuf.String()) assert.Equal(t, test.expectStderr, stderrBuf.String())", "positive_passages": [{"docid": "doc-en-kubernetes-495f248c0af4a1a8db07569505db46eac9f11be4907de183bc6923cd7882b142", "text": "Please refer following code Line 50 ~ 52 if config.Timestamps { logLine = append([]byte(msg.Timestamp.Format(jsonmessage.RFC3339NanoFixed)+\" \"), logLine...) }\nkubelet doesn't rely on Docker when reading logs, it reads the files itself (see the code linked in the issue). I don't think Docker would change the forced line splitting (see for example), so this should be fixed in Kubernetes.\nYour are right and kubelet read log file from host such as /var/log/pods/pods/NAMESPACEPOD-NAMExxx/....(JSON format) I will post a PR for it. /remove-sig cli /sig node\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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 .", "commid": "kubernetes_issue_77603", "tokennum": 539}], "negative_passages": []}
{"query_id": "q-en-kubernetes-52817c8519fe40c88f58fb826244009bc22e2b2f4e5cb87925350f8f17c148c9", "query": "stdoutBuf := bytes.NewBuffer(nil) stderrBuf := bytes.NewBuffer(nil) w := newLogWriter(stdoutBuf, stderrBuf, &LogOptions{since: test.since, timestamp: test.timestamp, bytes: -1}) <del> err := w.write(msg) </del> <ins> err := w.write(msg, true) </ins> assert.NoError(t, err) assert.Equal(t, test.expectStdout, stdoutBuf.String()) assert.Equal(t, test.expectStderr, stderrBuf.String())", "positive_passages": [{"docid": "doc-en-kubernetes-2f614c9ad06da31fe9313a5b2eaea6d6901d55cba8508cf5ebe57105d301c4f6", "text": "Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\nStale 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\nI saw the attempt fixing this but it was scary (echo this comment: ). I suggested a way it may be improved. Also the proposed fix didn't introduce any e2e tests to validate that runtime behavior is not changed and runtimes keep the no-newline-on-splitted-log logic. are you or anybody on this thread are still interested to work on this? Please re-open if so. Meanwhile closing this ahead of bot doing it because the inactivity. /close\nClosing this issue. <detailsIn response to : I saw the attempt fixing this but it was scary (echo this comment: ). I suggested a way it may be improved. Also the proposed fix didn't introduce any e2e tests to validate that runtime behavior is not changed and runtimes keep the no-newline-on-splitted-log logic. Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_77603", "tokennum": 493}], "negative_passages": []}
{"query_id": "q-en-kubernetes-52817c8519fe40c88f58fb826244009bc22e2b2f4e5cb87925350f8f17c148c9", "query": "stdoutBuf := bytes.NewBuffer(nil) stderrBuf := bytes.NewBuffer(nil) w := newLogWriter(stdoutBuf, stderrBuf, &LogOptions{since: test.since, timestamp: test.timestamp, bytes: -1}) <del> err := w.write(msg) </del> <ins> err := w.write(msg, true) </ins> assert.NoError(t, err) assert.Equal(t, test.expectStdout, stdoutBuf.String()) assert.Equal(t, test.expectStderr, stderrBuf.String())", "positive_passages": [{"docid": "doc-en-kubernetes-2e8714433462894a36e35ec9c24fb7c5a56d0558d2953a09bb86920b184c167e", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nYou can't reopen an issue/PR unless you authored it or you are a collaborator. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/remove-lifecycle rotten /reopen will fix it.\nReopened this issue. <detailsIn response to : /remove-lifecycle rotten /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/triage accepted\nThe Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.", "commid": "kubernetes_issue_77603", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-52817c8519fe40c88f58fb826244009bc22e2b2f4e5cb87925350f8f17c148c9", "query": "stdoutBuf := bytes.NewBuffer(nil) stderrBuf := bytes.NewBuffer(nil) w := newLogWriter(stdoutBuf, stderrBuf, &LogOptions{since: test.since, timestamp: test.timestamp, bytes: -1}) <del> err := w.write(msg) </del> <ins> err := w.write(msg, true) </ins> assert.NoError(t, err) assert.Equal(t, test.expectStdout, stdoutBuf.String()) assert.Equal(t, test.expectStderr, stderrBuf.String())", "positive_passages": [{"docid": "doc-en-kubernetes-422d52914e9725e7355cb5e937e13c24e15f273f63951d92fe52d86a167487cb", "text": "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]:\nThe 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]:\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_77603", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-52817c8519fe40c88f58fb826244009bc22e2b2f4e5cb87925350f8f17c148c9", "query": "stdoutBuf := bytes.NewBuffer(nil) stderrBuf := bytes.NewBuffer(nil) w := newLogWriter(stdoutBuf, stderrBuf, &LogOptions{since: test.since, timestamp: test.timestamp, bytes: -1}) <del> err := w.write(msg) </del> <ins> err := w.write(msg, true) </ins> assert.NoError(t, err) assert.Equal(t, test.expectStdout, stdoutBuf.String()) assert.Equal(t, test.expectStderr, stderrBuf.String())", "positive_passages": [{"docid": "doc-en-kubernetes-0e28d298340708e57a780633dba41fa2a744d19c9ab3d061a118f6b1e6c3d902", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI received a bug report about this issue. The root cause is that the buffer reads up to a new line. If the line is greater than 4096 bytes and '--timestamps' is turrned on the kubelet will write the timestamp and the partial log line. We will need to refactor the ReadLogs function to allow for a partial line read.", "commid": "kubernetes_issue_77603", "tokennum": 104}], "negative_passages": []}
{"query_id": "q-en-kubernetes-528c131df334d9c9279028f3e679c742aae0c926036781e1612da4732e24fcf6", "query": "} func (npm *nominatedPodMap) update(oldPod, newPod *v1.Pod) { <ins> // In some cases, an Update event with no \"NominatedNode\" present is received right // after a node(\"NominatedNode\") is reserved for this pod in memory. // In this case, we need to keep reserving the NominatedNode when updating the pod pointer. nodeName := \"\" // We won't fall into below `if` block if the Update event represents: // (1) NominatedNode info is added // (2) NominatedNode info is updated // (3) NominatedNode info is removed if NominatedNodeName(oldPod) == \"\" && NominatedNodeName(newPod) == \"\" { if nnn, ok := npm.nominatedPodToNode[oldPod.UID]; ok { // This is the only case we should continue reserving the NominatedNode nodeName = nnn } } </ins> // We update irrespective of the nominatedNodeName changed or not, to ensure // that pod pointer is updated. npm.delete(oldPod) <del> npm.add(newPod, \"\") </del> <ins> npm.add(newPod, nodeName) </ins> } func (npm *nominatedPodMap) podsForNode(nodeName string) []*v1.Pod {", "positive_passages": [{"docid": "doc-en-kubernetes-ae59c93f5ca20c2f0ee388defa733f31196c86b878735630d5ec3d27a9cb2b0a", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: Which test(s) are failing: kubernetes/test/integration/scheduler.TestPreemptionRaces Since when has it been failing: Not exactly known. The flake rate is not high. That's probably why it has not received attention. Testgrid link: Reason for failure: Logs are currently unaccessible. Test grid returns an error when clicking on the failed instances. Anything else we need to know: /sig scheduling /label help-wanted\nLet me try to fix it. /assign /remove-help\nThese are the last 4 failure log in . Although The flake rate is not high, but the fail point is same. I will try to solve this error based on this information.\nThis is currently the flakiest test for the flakiest PR job for kubernetes/kubernetes\n/remove-kind failing-test /kind flake /priority important-soon /milestone v1.15\nI will try to work out a PR if is not working on it.\nSure, you can take over it if you want. And It is strange about the flake in . I ran about 3,000 times on a local machine, but never failed. :joy: I also can help you to do someting ~\nIndeed, flaky tests are usually difficult to repro and debug.. A heads-up: I seem to have found the root cause. I'm working on a solution and will raise a PR after thorough testing.\nthis is still flaking (e.g. )\nI will take another look.\nThere are two additional flakes since the one reported on May 20: It's no longer that flaky , but the PR I gave earlier proved not to be a thorough solution but mitigation. I may not be able to continue looking into it in the next couple of weeks. Anyone is in interested, feel free to take it.\nLast failure was 4 days ago. will continue observing and see if it clears out /milestone v1.16\nBeen observing this one for a bit and it seems like its getting better Other than some failures a couple days ago it has been stable. Will keep an eye for a couple more days to make sure.\nSeems to have stabilized. /close\nClosing this issue. <detailsIn response to : Seems to have stabilized.", "commid": "kubernetes_issue_74931", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-528c131df334d9c9279028f3e679c742aae0c926036781e1612da4732e24fcf6", "query": "} func (npm *nominatedPodMap) update(oldPod, newPod *v1.Pod) { <ins> // In some cases, an Update event with no \"NominatedNode\" present is received right // after a node(\"NominatedNode\") is reserved for this pod in memory. // In this case, we need to keep reserving the NominatedNode when updating the pod pointer. nodeName := \"\" // We won't fall into below `if` block if the Update event represents: // (1) NominatedNode info is added // (2) NominatedNode info is updated // (3) NominatedNode info is removed if NominatedNodeName(oldPod) == \"\" && NominatedNodeName(newPod) == \"\" { if nnn, ok := npm.nominatedPodToNode[oldPod.UID]; ok { // This is the only case we should continue reserving the NominatedNode nodeName = nnn } } </ins> // We update irrespective of the nominatedNodeName changed or not, to ensure // that pod pointer is updated. npm.delete(oldPod) <del> npm.add(newPod, \"\") </del> <ins> npm.add(newPod, nodeName) </ins> } func (npm *nominatedPodMap) podsForNode(nodeName string) []*v1.Pod {", "positive_passages": [{"docid": "doc-en-kubernetes-e3284e7ec3b2451465766c8140397c9c53c5b3fcbbfbb2dd0841fe99eeb55acf", "text": "/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", "commid": "kubernetes_issue_74931", "tokennum": 35}], "negative_passages": []}
{"query_id": "q-en-kubernetes-52d7cff0cb39a861336e429c72e6c8225fef70688fd60d1a3f9bf08166ec0909", "query": "// ListRegisteredPriorityFunctions returns the registered priority functions. func ListRegisteredPriorityFunctions() []string { <del> schedulerFactoryMutex.Lock() defer schedulerFactoryMutex.Unlock() </del> <ins> schedulerFactoryMutex.RLock() defer schedulerFactoryMutex.RUnlock() </ins> var names []string for name := range priorityFunctionMap {", "positive_passages": [{"docid": "doc-en-kubernetes-a3c7d28dcea4cbdaac9e2be0d7d2d60e791f1250fe870aa2d2d4769d84db6cae", "text": "What would you like to be : Currently Mutex lock is acquired in for accessing different maps. Some functions only read map entry: We can utilize RWMutex where the above function acquires read lock. Why is this needed: For concurrent calls to IsFitPredicateRegistered / IsPriorityFunctionRegistered, read lock would lower contention.\n/sig scheduling\nfunctions getFitPredicateFunctions, getPriorityFunctionConfigs, ListRegisteredFitPredicates, ListRegisteredPriorityFunctions and GetAlgorithmProvider can also use read lock.\nI happened to raise earlier today. Anyone can finish resting ones.\nGood to know,\nThanks for raising this ! My PR covered and . Feel free to raise another PR to cover others.\nOnce is merged, I will send my PR thanks\nit's merged now.", "commid": "kubernetes_issue_76248", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-52fcfbd57004797122bff061220df57223172da5a11b583f491199c8465debdc", "query": "#   google         - Heapster, Google Cloud Monitoring, and Google Cloud Logging #   googleinfluxdb - Enable influxdb and google (except GCM) #   standalone     - Heapster only. Metrics available via Heapster REST API. <del> ENABLE_CLUSTER_MONITORING=\"${KUBE_ENABLE_CLUSTER_MONITORING:-googleinfluxdb}\" </del> <ins> ENABLE_CLUSTER_MONITORING=\"${KUBE_ENABLE_CLUSTER_MONITORING:-influxdb}\" </ins> # Optional: Enable node logging. ENABLE_NODE_LOGGING=\"${KUBE_ENABLE_NODE_LOGGING:-true}\"", "positive_passages": [{"docid": "doc-en-kubernetes-42a2dcc81f7ae4dc8763c9cd41f1b3c90a02e5ad103b4424eb3978e5cae8304c", "text": "Heapster pod: And logs: cc p0 for triage\nDid the required node scope change?\nIts either the API on the console or monitoring write scopes on the node. , Mike Danese wrote:\nI think this affects only GCE\nI will fix this issue since is on vacation.\nNeed to cherry pick so i'll leave open\nis out for review.\nhas been closed and the cherrypick here () has been merged so I'm closing this issue. Thanks everyone for the debugging.", "commid": "kubernetes_issue_16201", "tokennum": 104}], "negative_passages": []}
{"query_id": "q-en-kubernetes-53002220b235fdeea4555235d2b0fa1362fb31743ece39e062846fcf488ff3f4", "query": "want      []string } testFn := func(test *testcase, t *testing.T) { <del> SortControllerRevisions(test.revisions) for i := range test.revisions { if test.revisions[i].Name != test.want[i] { t.Errorf(\"%s: want %s at %d got %s\", test.name, test.want[i], i, test.revisions[i].Name) </del> <ins> t.Run(test.name, func(t *testing.T) { SortControllerRevisions(test.revisions) for i := range test.revisions { if test.revisions[i].Name != test.want[i] { t.Errorf(\"%s: want %s at %d got %s\", test.name, test.want[i], i, test.revisions[i].Name) } </ins> } <del> } </del> <ins> }) </ins> } ss1 := newStatefulSet(3, \"ss1\", types.UID(\"ss1\"), map[string]string{\"foo\": \"bar\"}) ss1.Status.CollisionCount = new(int32)", "positive_passages": [{"docid": "doc-en-kubernetes-4d5dc3f2fd1aa2418695125e98dd263b9bbd4b25db7ea8b25723d335bfe8c79b", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Statefulsets are sometimes continually rolling pods and I don't know why statefulset created: storageclass referenced: kubectl describe statefulset statefulset-test: As you can see from the above describe, the pod in the statefulset has been restarted a lot of times. Observing the created pod, 1) The pod comes up ready 2) immediately transitions to terminating 3) Is terminated 4) A new pod is created 5) Go back to (1) (repeats forever) Despite no updates to the statefulset spec ocurring. Making a change to the statefulset template (for example a trivial change adding a nonsense annotation) stops the rolling and fixes the issue When this statefulset was created, there was a mutating webhook enabled. After the observed pod rolling. I disabled this by making its configuration invalid and making it non required, and the rolling persisted. The status of the statefulset: : You can see that there is a discrepency between currentRevision and updateRevision. currentRevision: statefulset-test- updateRevision: statefulset-test- A short while later the status is changed to contain currentRevision: statefulset-test- updateRevision: statefulset-test- This change happened at Sun Apr 1 19:48:48 2018 Presumably after the rollout of statefulset-test- is complete.", "commid": "kubernetes_issue_61998", "tokennum": 342}], "negative_passages": []}
{"query_id": "q-en-kubernetes-53002220b235fdeea4555235d2b0fa1362fb31743ece39e062846fcf488ff3f4", "query": "want      []string } testFn := func(test *testcase, t *testing.T) { <del> SortControllerRevisions(test.revisions) for i := range test.revisions { if test.revisions[i].Name != test.want[i] { t.Errorf(\"%s: want %s at %d got %s\", test.name, test.want[i], i, test.revisions[i].Name) </del> <ins> t.Run(test.name, func(t *testing.T) { SortControllerRevisions(test.revisions) for i := range test.revisions { if test.revisions[i].Name != test.want[i] { t.Errorf(\"%s: want %s at %d got %s\", test.name, test.want[i], i, test.revisions[i].Name) } </ins> } <del> } </del> <ins> }) </ins> } ss1 := newStatefulSet(3, \"ss1\", types.UID(\"ss1\"), map[string]string{\"foo\": \"bar\"}) ss1.Status.CollisionCount = new(int32)", "positive_passages": [{"docid": "doc-en-kubernetes-25284c3702a45280c2a40fae68a3ba4d1c026c9e5d96ab43c2dee09fe3985aa0", "text": "Here are all the controllerrevisions from above: kubectl get controllerrevision statefulset-test- -o yaml kubectl get controllerrevision statefulset-test- -o yaml: kubectl get controllerrevision statefulset-test- -o yaml: The differences between the above controllerrevisions are insignificant (the hash, the creation timestamp, the name, the resource version, the uid, the self link) Interestingly all these controllerrevisions were created very close together in time shortly after I created the statefulset The current controllerrevisions are After watching the state change for a while, it actually seems like the statefulset is just cycling through the updateRevision being one of the above 10 controllerrevisions Leaders during this time From kube-controller-manager logs during this time, here is one excerpt: The error sync in there is suspicous, and as you can see the controllerrevisions are changing in the logs I have the full logs from a 5 minute window on either side of the above if necessary. The reason I'm inclined to think this is a kubernetes bug is that any update to the statefulset template fixes the problem. How to reproduce it (as minimally and precisely as possible): Not really sure. Worth just trying to create the above statefulset (requires creating the I tried deleting and recreating the above statefulset and it didn't happen, so something flaky is going on Anything else we need to know?: kubernetes 1.9.3 (client and server) cloud provider: aws\n/sig apps\nI realize this will probably need some further debugging, happy to get some direction\nConsistent repro: Create a statefulset that creates a controllerrevision whose hash is between max int32 and max uint32 (this shouldn't be that hard to do, possibly a 50/50 chance of this). Manually create a controllerrevision identical to the first (same revision), incrementing both the name and hash by one. See that the statefulset controller will continually switch which controller revision should be the target of the statefulset.\nDue to the issue fixed here: , under some circumstances controllerrevisions whose revision is the same were being considered equal.", "commid": "kubernetes_issue_61998", "tokennum": 496}], "negative_passages": []}
{"query_id": "q-en-kubernetes-53002220b235fdeea4555235d2b0fa1362fb31743ece39e062846fcf488ff3f4", "query": "want      []string } testFn := func(test *testcase, t *testing.T) { <del> SortControllerRevisions(test.revisions) for i := range test.revisions { if test.revisions[i].Name != test.want[i] { t.Errorf(\"%s: want %s at %d got %s\", test.name, test.want[i], i, test.revisions[i].Name) </del> <ins> t.Run(test.name, func(t *testing.T) { SortControllerRevisions(test.revisions) for i := range test.revisions { if test.revisions[i].Name != test.want[i] { t.Errorf(\"%s: want %s at %d got %s\", test.name, test.want[i], i, test.revisions[i].Name) } </ins> } <del> } </del> <ins> }) </ins> } ss1 := newStatefulSet(3, \"ss1\", types.UID(\"ss1\"), map[string]string{\"foo\": \"bar\"}) ss1.Status.CollisionCount = new(int32)", "positive_passages": [{"docid": "doc-en-kubernetes-59ace9008f72ca5d82f22a23445c41e6f5a4a98690d88922022af0dc9f3faebe", "text": "This ends up causing this bug to manifest as follows: ListRevisions finds many controllerrevisions with the same revision (unclear how this state happens, but it can happen) The sort here randomly sorts them Due to the linked bug , FindEqualRevisions incorrectly finds that all these controller revisions are equal to the proposed udpate. The updateRevision selects the last revision found here Therefore, updateRevision, is randomly selected and causes the bug. This fixes the immediate issue, but the sort should probably be made stable (i.e not just look at the revision number, perhaps just consider the hash for tie breakers)\nAs an update, fixing the equality check will not be sufficient because it is possible for multiple controller revisions to be created that are actually equal, including the same hash, that have the same revision number. I believe the fix will need to be equal controllerrevisions with the same revision number from being created sort the controllerrevisions so that the controllerrevision that is the target of the statefulset is stable\nIssues 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\n/remove-lifecycle stale\nping I use the K8S which version is 1.11.4 and encounter the same problem. I want to reproduce the problem and find your way: Manually create a controllerrevision identical to the first (same revision), incrementing both the name and hash by one. Could you tell me how to mannually create a same controllerrevision identical to the first? Thanks in anvance.", "commid": "kubernetes_issue_61998", "tokennum": 374}], "negative_passages": []}
{"query_id": "q-en-kubernetes-53203b8e74f208257e4c0108d4e7c75311724dfde1bba98cde5e3cad82dcd744", "query": "l.migrationCheck.validateMigrationVolumeOpCounts() } <del> ginkgo.It(\"should write files of various sizes, verify size, validate content [Slow][LinuxOnly]\", func() { </del> <ins> ginkgo.It(\"should write files of various sizes, verify size, validate content [Slow]\", func() { </ins> init() defer cleanup()", "positive_passages": [{"docid": "doc-en-kubernetes-2598e11fb35075705c3572da278160109a38df575ea6022e29df9bb46aaee489", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --ci-kubernetes-e2e-gci-gce-serial (gce-cos-master-serial) Four tests: Kubernetes e2e suite.[sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly] Kubernetes e2e suite.[sig-storage] In-tree Volumes [Driver: hostPath] [Testpattern: Inline-volume (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly] Kubernetes e2e suite.[sig-storage] In-tree Volumes [Driver: hostPathSymlink] [Testpattern: Inline-volume (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly] Kubernetes e2e suite.[sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should unmount if pod is force deleted while kubelet is down [Disruptive][Slow][LinuxOnly] is failing since June 29th 2021 (but the first failure was different than more recent ones). Commit , infra commit , . Other three tests are failing since July 9th 2021. Commit , infra commit , . Testgrid: https://k8s- Prow history: For CSI Volumes: For In-tree Volumes: There is another open issues for failing tests in this job: Failures reported there are about missing metrics, and were occuring before unmounting problems. So I opened a new issue, even though it's the same SIG. These tests don't look related to me, but I don't have enough context, maybe they somehow are. /sig storage /kind failing-test /milestone 1.22\nYou must be a member of the GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.", "commid": "kubernetes_issue_103651", "tokennum": 533}], "negative_passages": []}
{"query_id": "q-en-kubernetes-53203b8e74f208257e4c0108d4e7c75311724dfde1bba98cde5e3cad82dcd744", "query": "l.migrationCheck.validateMigrationVolumeOpCounts() } <del> ginkgo.It(\"should write files of various sizes, verify size, validate content [Slow][LinuxOnly]\", func() { </del> <ins> ginkgo.It(\"should write files of various sizes, verify size, validate content [Slow]\", func() { </ins> init() defer cleanup()", "positive_passages": [{"docid": "doc-en-kubernetes-fc6065ba1a9951ec296be8e3d5eed3592b7f58a8cbf0f7d83f44e7e6b4d2f288", "text": "<detailsIn response to : <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --ci-kubernetes-e2e-gci-gce-serial (gce-cos-master-serial) Four tests: Testgrid: https://k8s- Prow history: For CSI Volumes: For In-tree Volumes: #### Anything else we need to know: /kind failing-test /milestone 1.22 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\n/milestone v1.22\n/cc\n/cc (my close/reopen yesterday was accidental, sorry)\nI can take a look /assign\nThe non-subpath counterpart of this test is passing: These tests seem to use the default storageclass, whereas failing tests use in-tree hostpath and csi-hostpath\nThe CSI ones are failing because the hostpath driver never received a NodeUnstage (whereas it did in passing tests), causing the driver to error on volume deletion.\nIn the failed run kubelet has this error: which seems to have prevented kubelet from triggering a UnmountDevice. This error didn't exist in a successful run.\nHostpath driver can run with and without support for attach. Do you know which mode is enabled for this test?\nBetween the last passing time and when the test started failing, are there any PRs merged that look suspicious?\nAccording to csi-attacher logs, attach is disabled for both the good run and the failing run. Haven't spotted any obvious PRs so far, but I did find this: in the successful run, the log message for the successful is this: and the failed run: so the reconstructed volume names are somehow different. Checking reconstruction logic\nThis merged 12 days ago and was a pretty big change to pod lifecycle and could have trickling impact to volume manager. Does the timing of test failure match?\nThere is also this reconstruction fix that merged yesterday and seems related to outer vs inner spec name. I don't know if that will help fix this issue:\ncc\nLast successful run started at 7/8 17:49 PT, first failing run started at 7/9 2:23 PT.", "commid": "kubernetes_issue_103651", "tokennum": 491}], "negative_passages": []}
{"query_id": "q-en-kubernetes-53203b8e74f208257e4c0108d4e7c75311724dfde1bba98cde5e3cad82dcd744", "query": "l.migrationCheck.validateMigrationVolumeOpCounts() } <del> ginkgo.It(\"should write files of various sizes, verify size, validate content [Slow][LinuxOnly]\", func() { </del> <ins> ginkgo.It(\"should write files of various sizes, verify size, validate content [Slow]\", func() { </ins> init() defer cleanup()", "positive_passages": [{"docid": "doc-en-kubernetes-9f1333b0e960fd7acd243a96166fc71cf5883a52e7407e5f9400e1f08c54d3cf", "text": "was merged at 7/8 16:48 PT, so it's possible (if there's a delay in picking up master) Also this is in the failing kubelet logs but not in the successful one: I0720 18:20:42. ] \"Reconciler sync states: could not find volume information in desired state, clean up the mount points\" podName=-e508-45c2-8509- volumeSpecName=\"pvc--a615-4e89-afe8-\"\nFrom , the newly introduced log message here exists in the failing kubelet logs but not the successful one:\nFailures starting 07/08: /sig node for visibility\nI think caused the failures. Before after kubelet restarts, pod will still be in desired state (even through it is in terminating state), so that clean up mounts can be done completely. I think now, terminating pods will not be back to desired state, but reconstruction to actual state cannot completely clean up mounts. I am testing it about this.\nIs there a reason why reconstruction to actual state cannot clean up mounts? Note that a pod can be force deleted at any time, so a terminating pod that is force deleted would still have to be capable of being cleaned up (it won't be in desired state)? (note too that the expectation of the changes in is that terminating and fully terminated and \"never seen before\" should all completely equivalent from the perspective of other loops in the kubelet) If I understand you correctly, is this an existing bug that we're now triggering consistently?\nWe have both \"grace pod deletion\" and \"force pod deletion\" test cases that are failing.\nThere were a couple of key changes to volume loops in : Roughly before was \"it looks like it's got no running containers\", and after my change is \"we are going to be stopping all the containers from now on\". So this change meant that once a pod starts terminating, we are in \"tearing down mode\" and so my understanding of this method was that \"any pod where containers are being torn down is not in the desired state of the world\".", "commid": "kubernetes_issue_103651", "tokennum": 455}], "negative_passages": []}
{"query_id": "q-en-kubernetes-53203b8e74f208257e4c0108d4e7c75311724dfde1bba98cde5e3cad82dcd744", "query": "l.migrationCheck.validateMigrationVolumeOpCounts() } <del> ginkgo.It(\"should write files of various sizes, verify size, validate content [Slow][LinuxOnly]\", func() { </del> <ins> ginkgo.It(\"should write files of various sizes, verify size, validate content [Slow]\", func() { </ins> init() defer cleanup()", "positive_passages": [{"docid": "doc-en-kubernetes-015fa24d1e5eab79f6c5c1e5c14379be6e8185c1f089267f0bfc29a8792fef5f", "text": "After a restart, we would definitely not add a pod back that was in terminating state into desired state of the world, but \"restart + this change\" should be roughly equivalent to \"restart and force delete while restart is processing\" The other change was in which changed a live CRI read (which was trying to enforce that the dsowp is synchronized with the pod worker) into a threadsafe check against the pod worker directly (the pod worker can provide authoritative answers to \"this pod has no running containers\" now). The latter change seems less likely to impact you.\nThank you for the details! I think your change is making the right change, but unfortunately some of volume management still have issues, and so the tests rely on some behaviors that is not very right (pod volume is back to desired state even after it is in terminating) The cleanup mount currently does not have the logic to clean up global mount point if the volume plugin sets it up. I am still testing more and will share more details.\nis this a release blocker?\nYes, this impacts volume cleanup if kubelet restarts for any reason.\nOn a kube-up cluster running the latest master against the latest e2e binary, I was able to reproduce the in-tree failures but not the CSI ones for some reason. Will focus on in-tree failures for the time being\n/triage accepted\nmarking release-blocker per note on slack:\n/priority critical-urgent (once upon a time we used to not ship a release if any priority/critical-urgent issues were open, not sure if we decided to stop doing that)\nWe were able to find the trigger for the CSI failures - on 6/29 there was a change in the hostpath driver test manifest, and the driver's is enabled. This makes the driver return an error instead of only logging a warning message on if the volume isn't unstaged properly. IIUC there's a long standing issue that reconstruction doesn't handle node unstage. could you confirm? If that's the case, then these CSI failures are not release blocking. Furthermore, the CSI test with graceful delete started to fail on 7/9 because of since graceful and force deletes are now considered the same from the point of view of the volume manager. cc\nWhen that check was enabled, I don't think we realized it would impact the reconstruction path; it was enabled to validate a different issue.", "commid": "kubernetes_issue_103651", "tokennum": 504}], "negative_passages": []}
{"query_id": "q-en-kubernetes-53203b8e74f208257e4c0108d4e7c75311724dfde1bba98cde5e3cad82dcd744", "query": "l.migrationCheck.validateMigrationVolumeOpCounts() } <del> ginkgo.It(\"should write files of various sizes, verify size, validate content [Slow][LinuxOnly]\", func() { </del> <ins> ginkgo.It(\"should write files of various sizes, verify size, validate content [Slow]\", func() { </ins> init() defer cleanup()", "positive_passages": [{"docid": "doc-en-kubernetes-f86a5554f8df185db14256e7a7df5d445e052035a06405a03d3d05e494e0b68d", "text": "Are we running into the issue that reconstruction of staging directories isn't supported () OR is it that our reconstruction path requires drivers to have real mount points ()? Either way since both are known gaps with reconstruction, I think it makes sense to to disable the flag until we can address those issues.\nI was looking at this today too, trying to understand the underlying cause. That is why the failures are being reported now, but the part that I didn't understand is why NodeUnstageVolume is not being called for these volumes. In this instance: The DeleteVolume request fails because a staged path is still present: And in the kubelet log, NodeUnpublishVolume is called Then we hit this error: And NodeUnstageVolume is never called for this volume (same for other failures I looked at) so DeleteVolume keeps failing. So I think you're right that it's triggered by reconstruction, and it looks similar to , except in this case the restart happened before NodeUnpublishVolume.\nAnd it's probably not since the test uses a PVC\nWill look deeper into why UnmountDevice wasn't issued as well, but some update on the in-tree tests: the force delete test is skipped for the in-tree hostpath CSI driver because of Graceful tests are now failing as well because they behave like force tests due to\nI don't think the issue is related to PVC or not. I think it's related to drivers that do not actually mount devices as a separate filesystem than the root.\nThere are three possible flows during kubelet restart pod gracefully delete case, the pod still exists (it is not considered as terminated in function isPodTerminated(); note that this logic has some changes after , see , so pod volume will be back to desired state, and reconciler will try to set up volume and fill in actual state. When pod volume is finally deleted from desired state, reconciler will trigger teardown with information from actual state to unpublish and unstage volume. pod is forcefully deleted, pod volume will not be in desired state. If volume reconstruction succeeds (be able to reconstruct volume spec), volume will be back into actual state. Then reconciler will trigger teardown with information from actual state to unpublish and unstage volume (this part is similar to case 1).", "commid": "kubernetes_issue_103651", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-53203b8e74f208257e4c0108d4e7c75311724dfde1bba98cde5e3cad82dcd744", "query": "l.migrationCheck.validateMigrationVolumeOpCounts() } <del> ginkgo.It(\"should write files of various sizes, verify size, validate content [Slow][LinuxOnly]\", func() { </del> <ins> ginkgo.It(\"should write files of various sizes, verify size, validate content [Slow]\", func() { </ins> init() defer cleanup()", "positive_passages": [{"docid": "doc-en-kubernetes-0adb5aef0ac6855d53f98480f83c42da417641735fd51e124c8667d192575ced", "text": "last case is reconstruction failed (in this csi-host-path test, reconstruction will fail due to issue related to , it fail to check mount point for csi hostpath driver because it is using a bind mount of the same device ). In this case, reconciler will try to clean up mounts directly, but only published volume path, not the staged volume path (this logic is not implemented due to missing information). As a workaround, we can now disable check-volume-lifecycle if it does not cause other issues. Then we will work on to make sure csi-host-path driver can pass volume mountpoint check during reconstruction.\nThis issue is now mitigated with merged. There are two longer-term issues that are isolated to hostpath plugins (and maybe other plugins that are similar in behavior, perhaps emptydir and similar?): related to IsLikelyNotMountPoint as mentioned. Because these don't impact the core volume machinery and are not regressions, this issue doesn't need to be release blocking. We'll close this issue once (2) is tracked.\nis the IsLikelyNotMountPoint issue\nafter is merged, two csi-hostpath driver subpath test can pass, and two in-tree driver gracefully delete tests were skipped. https://k8s-\ncan you please cherry-pick to release-1.22 branch?\nOpened cherry-pick, please review:\n- what is the plan for reenabling them?\ncherry-pick merged!\nCheng and I will work on solving IsLikelyNotMountPoint issue for hostpath drivers. That should allow test to pass and we can enable them.\nCan this be removed from the milestone now that the workarounds have been merged, while leaving this issue open to track further work?\nWe can use existing issue to track the real fix. /close\nClosing this issue. <detailsIn response to : We can use existing issue to track the real fix. 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", "commid": "kubernetes_issue_103651", "tokennum": 438}], "negative_passages": []}
{"query_id": "q-en-kubernetes-532058bb01883d7dfa86bbe6f0ac481d1b356d3cbf5d782f90e599eefc430bf4", "query": "} }) <del> ginkgo.It(\"should function for pod-Service(hostNetwork): udp\", func() { config := e2enetwork.NewNetworkingTestConfig(f, e2enetwork.EndpointsUseHostNetwork) ginkgo.By(fmt.Sprintf(\"dialing(udp) %v --> %v:%v (config.clusterIP)\", config.TestContainerPod.Name, config.ClusterIP, e2enetwork.ClusterUDPPort)) err := config.DialFromTestContainer(\"udp\", config.ClusterIP, e2enetwork.ClusterUDPPort, config.MaxTries, 0, config.EndpointHostnames()) if err != nil { framework.Failf(\"failed dialing endpoint, %v\", err) } ginkgo.By(fmt.Sprintf(\"dialing(udp) %v --> %v:%v (nodeIP)\", config.TestContainerPod.Name, config.NodeIP, config.NodeUDPPort)) err = config.DialFromTestContainer(\"udp\", config.NodeIP, config.NodeUDPPort, config.MaxTries, 0, config.EndpointHostnames()) if err != nil { framework.Failf(\"failed dialing endpoint, %v\", err) } }) </del> // if the endpoints pods use hostNetwork, several tests can't run in parallel // because the pods will try to acquire the same port in the host. // We run the test in serial, to avoid port conflicts.", "positive_passages": [{"docid": "doc-en-kubernetes-15fd873e113c2b87c10057fb05584532c0b0add34bb5504a54b7699060ebd74c", "text": "<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI --ci-kubernetes-e2e-gce-cos-k8sbeta-default Networking Granular Checks: Services should function for service endpoints using hostNetwork Triage looks like it's mostly flaking on this job only: Examples /sig network <!-- Please see the deflaking doc () for more guidance! --\n/milestone v1.21 (marking in the current milestone until we get confirmation whether it is relevant to the release or not)\nSlack Thread:\n/assign\nThis is fixed by , let's wait some runs to confirm before closing\n/milestone clear (since this has been deemed to be non release-blocking)\n/triage accepted\n/close\nClosing this issue. <detailsIn response to : This is fixed by , let's wait some runs to confirm before closing 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", "commid": "kubernetes_issue_100890", "tokennum": 243}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5340f7fe75f5a50a5fa411acc49d2426d7bc371346fae30aa4541d5f626ac852", "query": "} else { handler = restfulGetResource(getter, exporter, reqScope) } <del> handler = metrics.InstrumentRouteFunc(action.Verb, resource, subresource, namespaceScope, handler) </del> <ins> if needOverride { // need change the reported verb handler = metrics.InstrumentRouteFunc(verbOverrider.OverrideMetricsVerb(action.Verb), resource, subresource, namespaceScope, handler) } else { handler = metrics.InstrumentRouteFunc(action.Verb, resource, subresource, namespaceScope, handler) } </ins> if a.enableAPIResponseCompression { handler = genericfilters.RestfulWithCompression(handler, a.group.Context) }", "positive_passages": [{"docid": "doc-en-kubernetes-818250efc38f3e1e4f69f5ba9f53826c59d17d9aa3970f389bfaed5f09e5cc10", "text": "Is this a BUG REPORT or FEATURE REQUEST?: What happened: use kubectl search log with follow option get api latency (apiserverrequestlatenciessummary{quantile=\"0.99\",resource=\"pods\",verb=\"GET\"} )high to give a alert in my cluster. the apiserver log is below and we can see it costs 1m25s. What you expected to happen: do not make this api latency account in getting pod request api latency How to reproduce it (as minimally and precisely as possible): use kubectl to search a pod log with follow option long enough and you will get this metric apiserverrequestlatenciessummary{quantile=\"0.99\",resource=\"pods\",verb=\"GET\"} higher than the ordinary case. Anything else we need to know?: I am happy to fix it. Environment: Kubernetes version (use ): 1.6 Cloud provider or hardware configuration**: bare-metal OS (e.g. from /etc/os-release): ubuntu 16.04 Kernel (e.g. ): 4.4 Install tools: kubeadm Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig API Machinery\n/area apiserver\n/sig api-machinery\n/assign Thanks... looking forward to your PR!\nfixed with PTAL", "commid": "kubernetes_issue_49998", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-539e853bf14ca5c13f517b8cb011a8c72a1b1622ee2a7ab95c5470f4e1d5b687", "query": "case \"get\": // Return an existing (matching) node on get. return &api.Node{ <del> ObjectMeta: api.ObjectMeta{Name: \"127.0.0.1\"}, Spec:       api.NodeSpec{ExternalID: \"127.0.0.1\"}, </del> <ins> ObjectMeta: api.ObjectMeta{Name: testKubeletHostname}, Spec:       api.NodeSpec{ExternalID: testKubeletHostname}, </ins> }, nil default: return nil, fmt.Errorf(\"no reaction implemented for %s\", action.Action)", "positive_passages": [{"docid": "doc-en-kubernetes-d16ca614c05197aa8b2652e3bf008c3a9a5ce41d960188a2ba3459b13d8b1102", "text": "Looks like some kubelet unit tests perform a lookupIp which ends up depending on the health of the local resolver. Specifically has this failing: Which leads to the test in: And we recently swapped out the node names from testnode to 127.0.0.1, so probably the culprit?\n/ref\nInteresting. I did swap out the node names in the unit test as part of to be 127.0.0.1, party because I thought that it wouldn't have any problems resolving during unit tests.\n/cc", "commid": "kubernetes_issue_8549", "tokennum": 113}], "negative_passages": []}
{"query_id": "q-en-kubernetes-539e853bf14ca5c13f517b8cb011a8c72a1b1622ee2a7ab95c5470f4e1d5b687", "query": "case \"get\": // Return an existing (matching) node on get. return &api.Node{ <del> ObjectMeta: api.ObjectMeta{Name: \"127.0.0.1\"}, Spec:       api.NodeSpec{ExternalID: \"127.0.0.1\"}, </del> <ins> ObjectMeta: api.ObjectMeta{Name: testKubeletHostname}, Spec:       api.NodeSpec{ExternalID: testKubeletHostname}, </ins> }, nil default: return nil, fmt.Errorf(\"no reaction implemented for %s\", action.Action)", "positive_passages": [{"docid": "doc-en-kubernetes-4a4c75dd985aaeba56d487bbde17d68f0425afc5d7e1167fdf1a1abcb97cd0b6", "text": "cc\nWhat is the environment where you are running the tests? They pass for me on my mac, a linux box, and shippable seems to be passing them as well.\nI couldn 't reproduce the failure either.\nI'm out right now; i'll try them when i get back. For the record, I run hack/test- Paul Morie wrote:\nAhem FTR This acronym is going to go quad-plat Paul Morie wrote:\nI ran on both platforms and saw the tests pass.\nI'm still seeing it. Won't have bandwidth to dig in personally until tomorrow.\nseeing a similar failure after a git pull\nI knew I wasn't crazy\nenvironment: fedora 21, golang: 1.4, docker: 1.6\nI think I see the problem. When I set the node name to in the test I was assuming it would parse as a valid ip address and not end up at the LookupIP call. But only the node name (and not the kubelet hostname) is being set (except in my new test where I ) so it's trying to do a lookup. Do you think you could test just changing the default hostname from \"testnode\" to \"127.0.0.1\" and see if that fixes it for you?\nTrying now\nI still get failures but no panic / threaddump.\ngist coming\nthis looks like again?\nGood that it isn't panicing any longer. I can dig into the test failures tomorrow (I think it should be relatively simple to resolve).\ncool, thanks for looking\nPasses in master now for me. Closing.\nFYI, they will break again once goes in, and then we can merge my PR to see if that fixes it for you.\n:+1:\nis in -- are these tests breaking again?\nI just rebased which I think will fix them.\nThey are breaking again.\nis on it.", "commid": "kubernetes_issue_8522", "tokennum": 407}], "negative_passages": []}
{"query_id": "q-en-kubernetes-53ac2f174d1ef4a4cc133d1aabd8237a913ff8e3d9040ba97a27458f25206549", "query": "function save-logs() { local -r node_name=\"${1}\" local -r dir=\"${2}\" <del> local files=\"${3} ${common_logfiles}\" </del> <ins> local files=\"${3}\" </ins> if [[ \"${KUBERNETES_PROVIDER}\" == \"gce\" || \"${KUBERNETES_PROVIDER}\" == \"gke\" ]]; then files=\"${files} ${gce_logfiles}\" fi if [[ \"${KUBERNETES_PROVIDER}\" == \"aws\" ]]; then files=\"${files} ${aws_logfiles}\" fi if ssh-to-node \"${node_name}\" \"sudo systemctl status kubelet.service\" &> /dev/null; then ssh-to-node \"${node_name}\" \"sudo journalctl --output=cat -u kubelet.service\" > \"${dir}/kubelet.log\" || true ssh-to-node \"${node_name}\" \"sudo journalctl --output=cat -u docker.service\" > \"${dir}/docker.log\" || true <ins> ssh-to-node \"${node_name}\" \"sudo journalctl --output=cat -k\" > \"${dir}/kern.log\" || true </ins> else <del> files=\"${files} ${initd_logfiles} ${supervisord_logfiles}\" </del> <ins> files=\"${kern_logfile} ${files} ${initd_logfiles} ${supervisord_logfiles}\" </ins> fi copy-logs-from-node \"${node_name}\" \"${dir}\" \"${files}\" }", "positive_passages": [{"docid": "doc-en-kubernetes-125faf475ef5c9fadc127cee08d3d538bc2825eff7d3fd81be9f088e2d4a0dbf", "text": "Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see ): No What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): \"LRUExpireCache\" Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT What happened: requires write lock since needs to manipulate its list to track recently used item. Currently it uses read lock so it may introduce race condition. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else do we need to know:\nThis was fixed in", "commid": "kubernetes_issue_31081", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-53c577a84ce702877b9fcb21675e9184e097b2a0e24eb6c3e5b6d5bc46c1e3a8", "query": "return checkMirrorPodDisappear(ctx, f.ClientSet, pod.Name, pod.Namespace) }, f.Timeouts.PodDelete, f.Timeouts.Poll).Should(gomega.BeNil()) }) <del> // Regression test for an extended scenario for https://issues.k8s.io/123980 ginkgo.It(\"should evict running pods that do not meet the affinity after the kubelet restart\", func(ctx context.Context) { nodeLabelKey := string(uuid.NewUUID()) nodeLabelValueRequired := string(uuid.NewUUID()) podName := \"affinity-pod\" + string(uuid.NewUUID()) nodeName := getNodeName(ctx, f) ginkgo.By(fmt.Sprintf(\"Adding node label for node (%s) to satisify pod (%s/%s) affinity\", nodeName, f.Namespace.Name, podName)) e2enode.AddOrUpdateLabelOnNode(f.ClientSet, nodeName, nodeLabelKey, nodeLabelValueRequired) ginkgo.DeferCleanup(func() { e2enode.RemoveLabelOffNode(f.ClientSet, nodeName, nodeLabelKey) }) pod := e2epod.MustMixinRestrictedPodSecurity(&v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name:      podName, Namespace: f.Namespace.Name, }, Spec: v1.PodSpec{ Affinity: &v1.Affinity{ NodeAffinity: &v1.NodeAffinity{ RequiredDuringSchedulingIgnoredDuringExecution: &v1.NodeSelector{ NodeSelectorTerms: []v1.NodeSelectorTerm{ { MatchExpressions: []v1.NodeSelectorRequirement{ { Key:      nodeLabelKey, Operator: v1.NodeSelectorOpIn, Values:   []string{nodeLabelValueRequired}, }, }, }, }, }, }, }, Containers: []v1.Container{ { Name:  podName, Image: imageutils.GetPauseImageName(), }, }, }, }) // Create the pod bound to the node. It will start, but will be rejected after kubelet restart. ginkgo.By(fmt.Sprintf(\"Creating a pod (%s/%s)\", f.Namespace.Name, podName)) e2epod.NewPodClient(f).Create(ctx, pod) ginkgo.By(fmt.Sprintf(\"Waiting for the pod (%s/%s) to be running\", f.Namespace.Name, pod.Name)) err := e2epod.WaitForPodNameRunningInNamespace(ctx, f.ClientSet, pod.Name, f.Namespace.Name) framework.ExpectNoError(err, \"Failed to await for the pod to be running: (%v/%v)\", f.Namespace.Name, pod.Name) // Remove node label e2enode.RemoveLabelOffNode(f.ClientSet, nodeName, nodeLabelKey) ginkgo.By(\"Restart the kubelet\") restartKubelet(true) gomega.Eventually(ctx, func() bool { return kubeletHealthCheck(kubeletHealthCheckURL) }, recoverTimeout, f.Timeouts.Poll). Should(gomega.BeTrueBecause(\"kubelet should be healthy after restart\")) // Pod should be terminated, maybe not immediately, should allow a few seconds for the kubelet to kill the pod // after kubelet restart, pod admission denied, kubelet will reject the pod and kill container. gomega.Eventually(ctx, func() bool { pod, err = e2epod.NewPodClient(f).Get(ctx, podName, metav1.GetOptions{}) framework.ExpectNoError(err) // pod is in a final state, the following are the behaviors of pods after kubelet restarted: // 1. kubelet `canAdmitPod` reject pod by reason Pod admission denied by nodeAffinity // 2. kubelet stop/kill container // the final state of the pod is related to the kill container. // if an error occurs in the preStop of the container or the exitCode is not 0, // the phase is PodFailed. if the exitCode of the StopContainer is 0, the phase is PodSucceeded. // in this case, stop and kill container is successful(exitCode 0), the pod phase should be PodSucceeded. return pod.Status.Phase == v1.PodSucceeded }, recoverTimeout, f.Timeouts.Poll).Should(gomega.BeTrueBecause(\"Pod %s not terminated: %s\", pod.Name, pod.Status.Phase)) }) </del> }) })", "positive_passages": [{"docid": "doc-en-kubernetes-07f06081dfd955758ffddc873b3e99f4b39044981ac813b4bb5583f8c899d069", "text": "/kind failing-test <!-- If this is a flake, please add: /kind flake --/sig node\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n<img width=\"1312\" alt=\"image\" src=\"\"\nThis looks like a test you a few days ago: /assign Can you look into these failures?\nGitHub didn't allow me to assign the following users: chengjoey. Note that only with read permissions, 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 : This looks like a test you a few days ago: 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\n/reopen\nYou can't reopen an issue/PR unless you authored it or you are a collaborator. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nAs mentioned in the previous comments, there should be only one expected state in the end. From the logs of these failed tests, after stopping the container, the phase changes to Failed. I think this does not meet expectations.\nThanks to for revert my previous PR. I think the pod final state should always be in one state. From the current e2e test results, the final state may be Succeed or Failed, seems pod.Status.Phase is empty. I think this seems to be wrong. I will study whether the node status (sufficient memory) and other factors interfere with the final state. Thanks again to for his help.", "commid": "kubernetes_issue_127374", "tokennum": 463}], "negative_passages": []}
{"query_id": "q-en-kubernetes-53c577a84ce702877b9fcb21675e9184e097b2a0e24eb6c3e5b6d5bc46c1e3a8", "query": "return checkMirrorPodDisappear(ctx, f.ClientSet, pod.Name, pod.Namespace) }, f.Timeouts.PodDelete, f.Timeouts.Poll).Should(gomega.BeNil()) }) <del> // Regression test for an extended scenario for https://issues.k8s.io/123980 ginkgo.It(\"should evict running pods that do not meet the affinity after the kubelet restart\", func(ctx context.Context) { nodeLabelKey := string(uuid.NewUUID()) nodeLabelValueRequired := string(uuid.NewUUID()) podName := \"affinity-pod\" + string(uuid.NewUUID()) nodeName := getNodeName(ctx, f) ginkgo.By(fmt.Sprintf(\"Adding node label for node (%s) to satisify pod (%s/%s) affinity\", nodeName, f.Namespace.Name, podName)) e2enode.AddOrUpdateLabelOnNode(f.ClientSet, nodeName, nodeLabelKey, nodeLabelValueRequired) ginkgo.DeferCleanup(func() { e2enode.RemoveLabelOffNode(f.ClientSet, nodeName, nodeLabelKey) }) pod := e2epod.MustMixinRestrictedPodSecurity(&v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name:      podName, Namespace: f.Namespace.Name, }, Spec: v1.PodSpec{ Affinity: &v1.Affinity{ NodeAffinity: &v1.NodeAffinity{ RequiredDuringSchedulingIgnoredDuringExecution: &v1.NodeSelector{ NodeSelectorTerms: []v1.NodeSelectorTerm{ { MatchExpressions: []v1.NodeSelectorRequirement{ { Key:      nodeLabelKey, Operator: v1.NodeSelectorOpIn, Values:   []string{nodeLabelValueRequired}, }, }, }, }, }, }, }, Containers: []v1.Container{ { Name:  podName, Image: imageutils.GetPauseImageName(), }, }, }, }) // Create the pod bound to the node. It will start, but will be rejected after kubelet restart. ginkgo.By(fmt.Sprintf(\"Creating a pod (%s/%s)\", f.Namespace.Name, podName)) e2epod.NewPodClient(f).Create(ctx, pod) ginkgo.By(fmt.Sprintf(\"Waiting for the pod (%s/%s) to be running\", f.Namespace.Name, pod.Name)) err := e2epod.WaitForPodNameRunningInNamespace(ctx, f.ClientSet, pod.Name, f.Namespace.Name) framework.ExpectNoError(err, \"Failed to await for the pod to be running: (%v/%v)\", f.Namespace.Name, pod.Name) // Remove node label e2enode.RemoveLabelOffNode(f.ClientSet, nodeName, nodeLabelKey) ginkgo.By(\"Restart the kubelet\") restartKubelet(true) gomega.Eventually(ctx, func() bool { return kubeletHealthCheck(kubeletHealthCheckURL) }, recoverTimeout, f.Timeouts.Poll). Should(gomega.BeTrueBecause(\"kubelet should be healthy after restart\")) // Pod should be terminated, maybe not immediately, should allow a few seconds for the kubelet to kill the pod // after kubelet restart, pod admission denied, kubelet will reject the pod and kill container. gomega.Eventually(ctx, func() bool { pod, err = e2epod.NewPodClient(f).Get(ctx, podName, metav1.GetOptions{}) framework.ExpectNoError(err) // pod is in a final state, the following are the behaviors of pods after kubelet restarted: // 1. kubelet `canAdmitPod` reject pod by reason Pod admission denied by nodeAffinity // 2. kubelet stop/kill container // the final state of the pod is related to the kill container. // if an error occurs in the preStop of the container or the exitCode is not 0, // the phase is PodFailed. if the exitCode of the StopContainer is 0, the phase is PodSucceeded. // in this case, stop and kill container is successful(exitCode 0), the pod phase should be PodSucceeded. return pod.Status.Phase == v1.PodSucceeded }, recoverTimeout, f.Timeouts.Poll).Should(gomega.BeTrueBecause(\"Pod %s not terminated: %s\", pod.Name, pod.Status.Phase)) }) </del> }) })", "positive_passages": [{"docid": "doc-en-kubernetes-6e565094763832d3a5d1ad0e1b54421c02a01afeb800549a53740a06212edac2", "text": "Add the log with phase \"Succeed\": The normal update status steps are 1-2-3-4, but the result of failure tests is that step 2 is executed last, which seems a bit strange. Because phase is empty\nfeel free to reopen the PR. But let's make sure to run the tests that this reported as failing before we merge. Thank you for your help on improving test coverage!\nThe links to the failed E2E tests in the overview of this issue all show the Pod phase as , but is there a link available somewhere for cases where it's empty string?\nIn fact, these failed tests are all empty strings, because not terminated: should be followed by phase Because my original test was written like this as I commented earlier, different order of updating status may lead to different final state\nThe Pod's final state is shown as in the dumped result immediately after the test fails. The referenced inside - is that coming from the Pod information fetched within ? Could it be that it's showing up as an empty string because it's not able to access the value externally?\nIn the tests submitted previously, and in my local(minnikube) tests, the pod status will change from to again see this log step 3 So I think the order of state changes affects the final result, and this is not very stable\nI think this is a separate issue, so as I mentioned in , I thought it might be fine to wait for either the or phase. However, after looking at , it seems that we may need to resolve this unstable final result first. WDYT?\nIf we can explain different results, it is fine. I don't want unexplained check for either condition in our tests", "commid": "kubernetes_issue_127374", "tokennum": 356}], "negative_passages": []}
{"query_id": "q-en-kubernetes-53c5bc6641c6246ffcb90e998db914cf6073610a7a1a310c14c688aaa52607b6", "query": "}, &api.Pod{ ObjectMeta: api.ObjectMeta{ <del> UID:       \"222\", Name:      \"bar\" + \"-\" + hostname, Namespace: \"default\", SelfLink: getSelfLink(\"bar-\"+hostname, kubetypes.NamespaceDefault), </del> <ins> UID:         \"222\", Name:        \"bar\" + \"-\" + hostname, Namespace:   \"default\", Annotations: map[string]string{kubetypes.ConfigHashAnnotationKey: \"222\"}, SelfLink:    getSelfLink(\"bar-\"+hostname, kubetypes.NamespaceDefault), </ins> }, Spec: api.PodSpec{ NodeName:                      hostname,", "positive_passages": [{"docid": "doc-en-kubernetes-8bc8d69d49aedfb4a9bf3991de80f7c339e96bfbefe5b1f250dae70fa0393729", "text": "See for more context. Currently, kubelet compares the spec of a mirror pod (created via apiserver) with that of a static pod (config stored as a file) to decide whether the two are considered identical. If they differ, kubelet would delete the mirror pod and re-create it with the correct spec. Due to the fact that apiserver may set default values for some fields in the spec of the mirror pod, the specs could deviate undesirably. To avoid problems like this, we can store the config of a static pod as an annotation in the mirror pod, and compare the static pod with the annotation.\nWould a hash of the config be sufficient if we're only going to compare? The whole spec would generally be more useful, but I wonder if that is too much data to put in an annotation.\nThis seems totally reasonable to me, but I'm still desperately curious why you can't just bypass defaulting when you generate mirror pod from static pod? (i.e. just use the static pod's configuration verbatim)\nIt's not kubelet who applies the default values here. The admission plugin was only run at the apiserver, and to bypass that, you have to ask apiserver to treat mirror pods differently and potentially at multiple places.\nOn May 22, 2015 10:38 AM, \"Yu-Ju Hong\" wrote: Understood, but is it really multiple places? If so then I agree it's a bad idea. Otherwise it might be worth considering as an alternative.\nIt's untenable for Kubelet to assume to know/circumvent all fields that will be set by other entities: admission control, defaulting, late initialization, auto-something, whatever. It needs to obey the same rules as other clients.\nI don't understand why you would ever want to apply any of the things you mentioned to static pods. Static pods should be copied verbatim into the mirror pods, right? That's what I'm proposing.\nWhat if the master is updated before the kubelet, and the master adds a new API field with a default value?\nThat case should be discussed in\nI agree that mirror pod should reflect the true status of the static pod running on the node, and no default values should be set in this case.", "commid": "kubernetes_issue_8683", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-53c5bc6641c6246ffcb90e998db914cf6073610a7a1a310c14c688aaa52607b6", "query": "}, &api.Pod{ ObjectMeta: api.ObjectMeta{ <del> UID:       \"222\", Name:      \"bar\" + \"-\" + hostname, Namespace: \"default\", SelfLink: getSelfLink(\"bar-\"+hostname, kubetypes.NamespaceDefault), </del> <ins> UID:         \"222\", Name:        \"bar\" + \"-\" + hostname, Namespace:   \"default\", Annotations: map[string]string{kubetypes.ConfigHashAnnotationKey: \"222\"}, SelfLink:    getSelfLink(\"bar-\"+hostname, kubetypes.NamespaceDefault), </ins> }, Spec: api.PodSpec{ NodeName:                      hostname,", "positive_passages": [{"docid": "doc-en-kubernetes-0491e123884f0f20f50d0a788bca7a6a29e2fa08227703a00221ecbd3bcf483c", "text": "However, I think it'd be harder to implement this way since, as stated above, that there are many things to circumvent in the apiserver itself. It could also be harder to keep this special case from being broken by a yet another new feature/plugin. Keeping the hash of the config in the annotation seems like a good compromise even though it may not reflect the true status 100% accurately. I think this is acceptable. What do you think?\nSure, if you think the annotation approach is easier, I would go with that. I guess in the case Brian mentoined (master adds a new API field with a default value), you would not update the mirror pod, because the static pod definition has not changed?\nYes, a hash would be sufficient.\nIt shouldn't be necessary to update the mirror pod in the case that a new default field was updated, because that field should be populated automatically by the apiserver on decode from etcd.\nWe should fix this so we don't have this problem again in 1.2.", "commid": "kubernetes_issue_8683", "tokennum": 226}], "negative_passages": []}
{"query_id": "q-en-kubernetes-53f1c232f67be637b6694e294409450bde97591b890305b00b195e69127aa594", "query": "apiVersion: v1 metadata: name: etcd-discovery <del> creationTimestamp: </del> labels: name: etcd-discovery spec:", "positive_passages": [{"docid": "doc-en-kubernetes-970debf69dc4e7e663c051298279ebf93b58654f6c393d8683796c73cb4f1c74", "text": "Kubernetes version (use ): Environment: Cloud provider or hardware configuration: Vagrant OS (e.g. from /etc/os-release): CoreOS Kernel (e.g. ):Install tools: Vagrant & Others: What happened: What you expected to happen: Success How to reproduce it (as minimally and precisely as possible): Followed instructions at Tried to run Received: Anything else do we need to know: From googling, it seems several of the fields in the config are for when using OpenShift origin. But creating the replication controller is a prerequisite to launching OpenShift Origin. Chicken & egg problem.", "commid": "kubernetes_issue_39575", "tokennum": 138}], "negative_passages": []}
{"query_id": "q-en-kubernetes-544f813af334db3ce53e6330fba708f3380990f9d8eae32d3ce0b13b66f1cf30", "query": "} ginkgo.By(fmt.Sprintf(\"Create node foo by user: %v\", asUser)) _, err := c.CoreV1().Nodes().Create(context.TODO(), node, metav1.CreateOptions{}) <ins> // NOTE: If the test fails and a new node IS created, we need to delete it. If we don't, we'd have // a zombie node in a NotReady state which will delay further tests since we're waiting for all // tests to be in the Ready state. defer func() { f.ClientSet.CoreV1().Nodes().Delete(context.TODO(), node.Name, metav1.DeleteOptions{}) }() </ins> framework.ExpectEqual(apierrors.IsForbidden(err), true) })", "positive_passages": [{"docid": "doc-en-kubernetes-8d17c7d91073b6e9465f606fb5c09d3baa0515bf8daa4489f4a84c8a2afde410", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: N/A Which test(s) are failing: [sig-auth] [Feature:NodeAuthorizer] A node shouldn't be able to create another node Since when has it been failing: N/A Testgrid link: N/A Reason for failure: The test creates a new ` node, but it does not delete it after the test ends: kubectl get nodes NAME STATUS ROLES AGE VERSION 1954k8s000 Ready agent 24d v1.14.1 1954k8s001 Ready agent 24d v1.14.1 foo NotReady <none4m3s k8s-master--0 Ready master 24d v1.14.1 Anything else we need to know: /sig testing\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with .", "commid": "kubernetes_issue_78861", "tokennum": 511}], "negative_passages": []}
{"query_id": "q-en-kubernetes-544f813af334db3ce53e6330fba708f3380990f9d8eae32d3ce0b13b66f1cf30", "query": "} ginkgo.By(fmt.Sprintf(\"Create node foo by user: %v\", asUser)) _, err := c.CoreV1().Nodes().Create(context.TODO(), node, metav1.CreateOptions{}) <ins> // NOTE: If the test fails and a new node IS created, we need to delete it. If we don't, we'd have // a zombie node in a NotReady state which will delay further tests since we're waiting for all // tests to be in the Ready state. defer func() { f.ClientSet.CoreV1().Nodes().Delete(context.TODO(), node.Name, metav1.DeleteOptions{}) }() </ins> framework.ExpectEqual(apierrors.IsForbidden(err), true) })", "positive_passages": [{"docid": "doc-en-kubernetes-c380167759ca032d9ef1dc01b836b766174a5602fdd6643d76ef74667022d120", "text": "Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nClosing 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", "commid": "kubernetes_issue_78861", "tokennum": 92}], "negative_passages": []}
{"query_id": "q-en-kubernetes-54629e34041a92a3195a23da1fe8ecef3c9f76f3dfa5647eef05c6e2cbcb580a", "query": "if err != nil { return nil, err } <ins> errors := ds.performPlatformSpecificContainerForContainer(r.ContainerId) if len(errors) != 0 { return nil, fmt.Errorf(\"failed to run platform-specific clean ups for container %q: %v\", r.ContainerId, errors) } </ins> err = ds.client.RemoveContainer(r.ContainerId, dockertypes.ContainerRemoveOptions{RemoveVolumes: true, Force: true}) if err != nil { return nil, fmt.Errorf(\"failed to remove container %q: %v\", r.ContainerId, err) } return &runtimeapi.RemoveContainerResponse{}, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-486ca0159276eedd0d2aa336961ee5fd6fb83d0ac97af7f3f9c8c863d43fcef2", "text": "What would you like to be : Periodically remove cleanupInfos for old containers from dockershim's map. One way of doing that would be to just forget about s older than say an hour, as they should always be short-lived. Why is this needed: introduced a new in-memory map for the dockershim, that could potentially (in pathological cases) cause memory leaks - for containers that use GMSA cred specs, get created successfully, but then never get started nor removed. This might be okay for the alpha release of the GMSA feature, but should be addressed in the beta. See\n/assign wk8\n/sig windows\n/milestone v1.15\ngot moved out. let's move this issue with it as well /milestone v1.16\nHello! I'm bug triage lead for the 1.16 release cycle and considering this issue is tagged for 1.16, but not updated for a long time, I'd like to check its status. The code freeze is starting on August 29th (about 1.5 weeks from now), which means that there should be a PR ready (and merged) until then. Do we still target this issue to be fixed for 1.16?\n: yup we'd love to have this in 1.16, still waiting for kind reviewers on :) ...", "commid": "kubernetes_issue_74843", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-54793bd71f6a698b26b9ae8bc160c227b3ba2bd344710609eb83e516b08b5ea4", "query": "bash -c \"${common_commands}\" diff -ruN \"${output_dir}/upstream\" \"${output_dir}/patch\" >\"${diff_file}\" || true <ins> if [[ -t 1 ]]; then  # Attached to a terminal? less \"${diff_file}\" fi </ins> echo echo \"  *** Diff saved in ${diff_file} ***\"", "positive_passages": [{"docid": "doc-en-kubernetes-799a55cc839cd2ff4d6d16e3e37eb2f6d3baf0c870165e5d680f29079df92f3e", "text": "and show that we run this job every few minutes, but it never passes. I'm going to send out a PR to disable this job until someone has the time to investigate and resolve.\nIt's failing before tests even start:\nAt this point I don't think it's a flake, we needed flannel for a release and it's less important now so I'm not investigating why the cluster isn't coming up soon. I do believe if the cluster comes up a majority if not all of the tests will pass, and the ones that don't will flake for known reasons.", "commid": "kubernetes_issue_24520", "tokennum": 128}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5497c01f5abf144fdf36358526e86190553872eaab9e820ccca412656170856e", "query": "\"type\": \"string\" }, \"ports\": { <del> \"description\": \"List of ports to expose from the container. Exposing a port here gives the system additional information about the network connections a container uses, but is primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default \"0.0.0.0\" address inside a container will be accessible from the network. Cannot be updated.\", </del> <ins> \"description\": \"List of ports to expose from the container. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default \"0.0.0.0\" address inside a container will be accessible from the network. Modifying this array with strategic merge patch may corrupt the data. For more information See https://github.com/kubernetes/kubernetes/issues/108255. Cannot be updated.\", </ins> \"items\": { \"allOf\": [ {", "positive_passages": [{"docid": "doc-en-kubernetes-754763163ccf179fd132c393411aa2d267e649990c98a81bb38938ec6debc8b2", "text": "The comments in says that : However there are several cases where this is false : When using a Service with a targetPort that references a name in the ports arrays of the pod. Some software (ab)uses this API to get which ports are used (See Although unfixable, my goal is to fix the documentation so other people don't have the same problem). The Azure Load Balancer implementation does this for instance. Some other network/security software might use this information. Also, is it possible to document/reference the above issue in the comment ? Since it is described as informational I expected for the network to work without this information. But it's definitely not the case. Not needed since it's mostly a doc issue. I'm interested in contributing this patch but would like some feedbacks before doing it. :) <details</details<details</details<details</details<details</details<details</details<details</details\n/sig network\n/triage accepted -- thoughts? I believe the doc are due for a refresh.\nI'd take this one. /assign\nI didn't see that you wanted to do this patch, I am very sorry and now I unassign it. /unassign\nNo worries But I'm still not sure where / what to add. Should I only fix the part saying it is only informational ? Is there anything else ? (cc\nThe 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]:\n/remove-lifecycle stale", "commid": "kubernetes_issue_108255", "tokennum": 435}], "negative_passages": []}
{"query_id": "q-en-kubernetes-54ae05a93453d5828d9cb0fcc62d9ce1e8af2c9df4a3b559e1cba98cfa50d57e", "query": "if err != nil { t.Fatalf(\"unexpected error: %v\", err) } <ins> } func TestDeleteNamespaceWithIncompleteFinalizers(t *testing.T) { now := util.Now() fakeEtcdClient, helper := newHelper(t) fakeEtcdClient.ChangeIndex = 1 fakeEtcdClient.Data[\"/registry/namespaces/foo\"] = tools.EtcdResponseWithError{ R: &etcd.Response{ Node: &etcd.Node{ Value: runtime.EncodeOrDie(latest.Codec, &api.Namespace{ ObjectMeta: api.ObjectMeta{ Name:              \"foo\", DeletionTimestamp: &now, }, Spec: api.NamespaceSpec{ Finalizers: []api.FinalizerName{api.FinalizerKubernetes}, }, Status: api.NamespaceStatus{Phase: api.NamespaceActive}, }), ModifiedIndex: 1, CreatedIndex:  1, }, }, } storage, _, _ := NewStorage(helper) _, err := storage.Delete(api.NewDefaultContext(), \"foo\", nil) if err == nil { t.Fatalf(\"expected error: %v\", err) } } </ins> <del> // TODO: when we add life-cycle, this will go to Terminating, and then we need to test Terminating to gone </del> <ins> func TestDeleteNamespaceWithCompleteFinalizers(t *testing.T) { now := util.Now() fakeEtcdClient, helper := newHelper(t) fakeEtcdClient.ChangeIndex = 1 fakeEtcdClient.Data[\"/registry/namespaces/foo\"] = tools.EtcdResponseWithError{ R: &etcd.Response{ Node: &etcd.Node{ Value: runtime.EncodeOrDie(latest.Codec, &api.Namespace{ ObjectMeta: api.ObjectMeta{ Name:              \"foo\", DeletionTimestamp: &now, }, Spec: api.NamespaceSpec{ Finalizers: []api.FinalizerName{}, }, Status: api.NamespaceStatus{Phase: api.NamespaceActive}, }), ModifiedIndex: 1, CreatedIndex:  1, }, }, } storage, _, _ := NewStorage(helper) _, err := storage.Delete(api.NewDefaultContext(), \"foo\", nil) if err != nil { t.Fatalf(\"unexpected error: %v\", err) } </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-859a8b847337ca2cf9879726f3bdb71f0db5559ee2589591ceae612e41f71a1b", "text": "There is a funny subtle behvaiour in get namespaces, in which if i call more than one time, it seems that the removal from Terminating state is accelarated. It seems this might indicate a bug, or maybe its not a bug and the eventual semantics of is a little funny sometimes. in any case, here's what we are seeing : 1) when i delete a namespace the first time usning kubectl, we get a state change to . that is correct, of course. 2) but ... if make the call a second time, then the same status line is immediately removed from . Expected behaviour : A second call to \"kubectl delete ...\" shouldn't have any effect on the timing of removal of a namespace from 'Terminating' state*... So i guess there is some \"eventual consistency\" subtle bug that is resolved by repeated calls to\nsuggests this may not be e bug, maybe its just the etcd eventual deleter thingy.\nLooks to definitely be a bug. The 2nd delete seems to have interrupted the delete process and artifacts (like events) from the namespace still exist in etcd.\ninvestigating...\noops, see the error, will submit a fix.\nI have a fix, but need a test case, will submit PR tomorrow AM", "commid": "kubernetes_issue_6633", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-54b2bcd915c84f3ee7e0490fe242dd69f8569d9dfeb3b70597c8c4b5f807715f", "query": "\"kind\": \"Service\", \"apiVersion\": \"v1beta3\", \"metadata\": { <del> \"name\": \"my-service\", </del> <ins> \"name\": \"my-service\" </ins> }, \"spec\": { \"selector\": {", "positive_passages": [{"docid": "doc-en-kubernetes-5e2660950cda0f785263613d5dae344eb16f84b548bf3bbe07f6c94efec5b686", "text": "The \"service\" file in this document contains a trailing comma on the line ' \"name\": \"my-service\", ` and thus kubectl fails to parse it properly.", "commid": "kubernetes_issue_8938", "tokennum": 41}], "negative_passages": []}
{"query_id": "q-en-kubernetes-54ba1bf5d59d0e82c86b99d4defd9317886063bd58ecd9f20ce18b55d6e36396", "query": "// during \"reserve\" extension point or later. func (mc CommunicatingPlugin) Unreserve(ctx context.Context, state *framework.CycleState, pod *v1.Pod, nodeName string) { if pod.Name == \"my-test-pod\" { <del> state.Lock() </del> // The pod is at the end of its lifecycle -- let's clean up the allocated // resources. In this case, our clean up is simply deleting the key written // in the Reserve operation. state.Delete(framework.StateKey(pod.Name)) <del> state.Unlock() </del> } }", "positive_passages": [{"docid": "doc-en-kubernetes-43588246e28947764a0f8a5c9c5b1d76a5819a8eaa1c439f79abd429269822c0", "text": "What happened: kube-scheduler () crashes due to a panic while running : The race condition is triggered when an out-of-tree plugin, that writes to during its Filter phase, is registered through . Access to in general happens from a single goroutine and there are no practical concurrency issues, with the exception of the phase, that parallelizes calls for each node across plugins: A quick glance at the tip of the branch seems to indicate the bug is still present there. What you expected to happen: Ideally access to should be synchronized everywhere for correctness, including by all in-tree plugins, since there are no guarantees about how will call multiple plugins concurrently. It seems to me it is something that was considered at some point, given that has methods. Sadly, almost no in-tree plugins are synchronizing access. For now, I will try to work around the problem by doing a single write to during and storing a data bag structure where I will write state into during (with proper synchronization), instead of writing to directly. How to reproduce it (as minimally and precisely as possible): Install a scheduler plugin that writes to during its phase. In-tree (builtin) plugins are not synchronizing their access to . Environment: Kubernetes version (use ): v1.18.8 Cloud provider or hardware configuration: linux-amd64 (AWS) OS (e.g: ): Ubuntu 18.04.5 LTS (Bionic Beaver) Others: custom kube-scheduler binary built with an out-of-tree plugin using\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scheduling\nAFAICT all in-tree plugins write to the cycle state in PreFilter and then only read from cycle state in Filter. So this shouldn't be a problem with in-tree plugins as concurrent read access should be fine during RunFilterPlugins. But since your out-of-tree plugin writes in Filter, I can see why this can be a problem.", "commid": "kubernetes_issue_95887", "tokennum": 515}], "negative_passages": []}
{"query_id": "q-en-kubernetes-54ba1bf5d59d0e82c86b99d4defd9317886063bd58ecd9f20ce18b55d6e36396", "query": "// during \"reserve\" extension point or later. func (mc CommunicatingPlugin) Unreserve(ctx context.Context, state *framework.CycleState, pod *v1.Pod, nodeName string) { if pod.Name == \"my-test-pod\" { <del> state.Lock() </del> // The pod is at the end of its lifecycle -- let's clean up the allocated // resources. In this case, our clean up is simply deleting the key written // in the Reserve operation. state.Delete(framework.StateKey(pod.Name)) <del> state.Unlock() </del> } }", "positive_passages": [{"docid": "doc-en-kubernetes-278036efba637c2a6a49330142a64ca8f7b65a0d21755fde24824f9c473a00c9", "text": "Aside from adding Lock/Unlock in in-tree plugin, offering mutual exclusion on each key as a built-in feature within CycleState could be an alternative solution. This way, reads from in-tree plugins during Filter wouldn't interfere with writes during Filter from out-of-tree plugins.\ncc\nshould we change the Read/Write CycleState methods to be thread safe?\nAdding locks without a proper justification would just increase the latency. could you clarify your use case? Why do you need to write anything during Filter?\nyeah, we should measure it, but I don't expect it to have significant effect...\nAdding locks without a proper justification would just increase the latency. Without contention (which is the case with in-tree plugins), I don't think this is a concern.\nAdapting source from : source: essentially, 11.3 ns/Lock-Unlock pair\nI remember locks showing up in profiling for PreScore/Score for certain plugins. Although I have to admit that the accesses were not properly implemented. I'd like to hear an answer for before doing any experiments.\n+1 to that I'd also like to understand the motivations / requirements of mutating CycleState in Filter().\nMy particular use-case is that we have resources being dynamically to/removed from Nodes, and those resources need to be allocated (and tracked) in the scheduling loop. Technically I could pre-compute all the available dynamic resources for all Nodes at the phase, and snapshot it, but that would require me to pre-compute everything for all Nodes on all scheduling cycles. Instead, what I'm currently doing is computing what dynamic resources can be utilized on-demand during the phase (kind of a lazy loading of dynamic resources for each pair), and saving state of what extra resources were considered during for each Node that was evaluated. Then, later in the scheduler plugin can lock-in the exact dynamic resources for the particular Node that was selected. I understand the concern with adding extra synchronization overhead without a real need. Even if my use-case is not good enough to justify it, there is another argument for it: technically, the lack of access synchronization on violates the . Even if in the end we decide synchronizing all access is not worth the overhead (for correctness), I would strongly encourage better documentation saying which plugin phases are allowed to modify , and perhaps even forcing a snapshot-read-only copy of to be used by plugins.\nUsing the scheduler to track resources is not a good idea.", "commid": "kubernetes_issue_95887", "tokennum": 539}], "negative_passages": []}
{"query_id": "q-en-kubernetes-54ba1bf5d59d0e82c86b99d4defd9317886063bd58ecd9f20ce18b55d6e36396", "query": "// during \"reserve\" extension point or later. func (mc CommunicatingPlugin) Unreserve(ctx context.Context, state *framework.CycleState, pod *v1.Pod, nodeName string) { if pod.Name == \"my-test-pod\" { <del> state.Lock() </del> // The pod is at the end of its lifecycle -- let's clean up the allocated // resources. In this case, our clean up is simply deleting the key written // in the Reserve operation. state.Delete(framework.StateKey(pod.Name)) <del> state.Unlock() </del> } }", "positive_passages": [{"docid": "doc-en-kubernetes-b826aaa34ec054d9cc587ce8587a04002d4daa70694ce73071b413f1bf7ba0c6", "text": "The scheduler should be stateless. Can't you track the resources with an external controller or with a device plugin and making it part of the Node spec?\nthere may be some misunderstanding in my poor choice of words. What I mean by \"tracking\" is that the scheduler needs to track usage and availability of these extra per-Node resources, to be able to allocate them during placement/scheduling. Exactly the same it does with volumes, cpus, memory, ephemeral disk, etc Doing computations in a controller outside of the scheduling loop would be similar to \"precomputing\" these resources. In my particular use case I chose a different way because: introduces another point of failure, if the external controller stops pre-computing extra resources and publishing them somewhere (CRD, Node spec, etc) scheduling halts (at least scheduling on these extra resources) Node resources in my use case are volatile (they are coming and going frequently), and the extra latency by an extra controller (vs doing all computations right in the scheduling loop) may be problematic for my use case. Even if you consider my use case not enough to add proper synchronization to , I'd still encourage making it explicit what scheduling phases are allowed to modify it (and even passing in a snapshot read-only version of to phases that are not expected to update it), to avoid confusion and race conditions.\nOk, if you are not tracking the existence of resources in the scheduler, I wouldn't suggest the external controller. Still, have you considered the device plugin framework? That way, the default kube-scheduler could keep track of resources usage. Otherwise, I still don't see why you would need to update the CycleState during Filter. As its name indicates, CycleState only lives during a scheduling cycle.\nRegardless of the correctness of usage of CycleState to do what wants, I still think we need to do at least one of the following: that writing to CycleState during Filter will lead to data races, a read-only CycleState to Filter plugins (whether we do this at the interface level or if we simply drop Write requests during Filter is an implementation detail), or make CycleState concurrency safe CycleState as it exists right now allows plugin authors to shoot themselves in the foot IMO.\nI'm leaning towards 1, but it's fair to continue the discussion before deciding.\nCan you run the \"controller\" as a goroutine along with your scheduler plugin?", "commid": "kubernetes_issue_95887", "tokennum": 520}], "negative_passages": []}
{"query_id": "q-en-kubernetes-54ba1bf5d59d0e82c86b99d4defd9317886063bd58ecd9f20ce18b55d6e36396", "query": "// during \"reserve\" extension point or later. func (mc CommunicatingPlugin) Unreserve(ctx context.Context, state *framework.CycleState, pod *v1.Pod, nodeName string) { if pod.Name == \"my-test-pod\" { <del> state.Lock() </del> // The pod is at the end of its lifecycle -- let's clean up the allocated // resources. In this case, our clean up is simply deleting the key written // in the Reserve operation. state.Delete(framework.StateKey(pod.Name)) <del> state.Unlock() </del> } }", "positive_passages": [{"docid": "doc-en-kubernetes-038a628d524f09c8393af798b6053a1fded9e84e2c01785ad258fb86c8d6d618", "text": "So it's not an external controller binary, and hence don't introduce another point of failure. It's pretty like how the default scheduler manages its internal cache. But note that cache is only needed when you need a more efficient data structure. If a {key:value} map is good enough, spinning up a XYZInformer and obtain the latest XYZ resource on-demand is the most recommended way. I think it quite depends on how you design the internal XYZ cache. For example, it should only tweak the cache in an incremental manner - in other words, unchanged resource will be kept unmodified. You can check out the \"doubly-pointer snapshot\" of scheduler's cache. With above said, if I understand your case correctly, you may need to build a sophisticated XYZ cache, which runs in a separate goroutine and responds to your XYZ resource changes. And then upon each scheduling cycle, take a snapshot (may needs a specific snapshotting algorithm) in PreFilter() and WRITE to CycleState, and then in Filter() READ from CycleState. My personal option is to suggest all plugin developers to read from CycleState in Filter().\nnailed it. What you describe is almost exactly what I\u2019m doing today. There are some details particular to my use case (e.g. just tracking current state with an informer and an incremental cache is not enough, because there\u2019s some logic involved in deciding if currently available resources are usable by each pair, and I currently do that computation in as pairs are evaluated). In any case, I just wanted to share my use case to provide some color, but I don\u2019t want what I\u2019m doing distracting us from the more important questions, mentioned by above. My personal preference would be as a very short term next step, then when someone has cycles to do it. I would be OK with punting on until a more strong need shows up.\nNote that limiting to only reading from works for me, as long as I can still read my own data structure from it and do writes on it (i.e. don\u2019t deepclone for the phase).\nalso adds overhead (from copying the state, which can be very expensive).\nCould implement just by changing the interface passed to (e.g. ). That wouldn\u2019t be backwards compatible, but very cheap.", "commid": "kubernetes_issue_95887", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-54ba1bf5d59d0e82c86b99d4defd9317886063bd58ecd9f20ce18b55d6e36396", "query": "// during \"reserve\" extension point or later. func (mc CommunicatingPlugin) Unreserve(ctx context.Context, state *framework.CycleState, pod *v1.Pod, nodeName string) { if pod.Name == \"my-test-pod\" { <del> state.Lock() </del> // The pod is at the end of its lifecycle -- let's clean up the allocated // resources. In this case, our clean up is simply deleting the key written // in the Reserve operation. state.Delete(framework.StateKey(pod.Name)) <del> state.Unlock() </del> } }", "positive_passages": [{"docid": "doc-en-kubernetes-73e2408e2bea0ec3fe3177e8a87291d57a052eb7c05f546c204ec27aefee3293", "text": "I guess that would work in the sense that you cannot change the high level values of the CycleState map, but you could still override what's inside them, if they have pointers. But maybe that's ok.\nbut you could still override what's inside them, if they have pointers. But maybe that's ok. yeah, if it was pointers and if the underlying data needed to be modified, I'd imagine it would have its own Lock/Unlock semantics\nfor such implementation, the only remaining concern is backwards compatibility. So I would leave that decision to who leads the scheduling-plugins repo.\nI rethink 's original problem a little bit: the original racing issue occurs when reading CycleState in in-tree plugins, this indicates one of the (out-of-tree) plugins is (over)writing the most high-level value of the CycleState map. But if we control the locking inside the out-of-tree plugin, and mutate that particular in-place, that would be good enough? Case 3 in the above program demonstrates the correct way to manipulate the specific out-of-tree state. Let me know your thoughts. If it resolves 's concern, we don't need to make any change on the Filter() interface.\nCase 3 is how I am working around the problem today to avoid the race. I write a \"data bag\" once into top level in , then only modify my own inner structure (with proper locking) in , without doing any further modifications to directly (top level) in . That is acceptable, but I'd encourage you to consider making the interface (and documentation) more explicit for plugins, so they avoid the mistake of writing directly into . Without changing anything (no documentation, no readonly interface), it is pretty easy for a plugin to use in a way that you don't want to support.\nThanks for confirming that. Yes, documenting it, or(and) publishing examples would be quite helpful to clarify the semantics. As a wrap-up: a keyed value can be read from CycleState, literally , in any phase. It's always race-free.", "commid": "kubernetes_issue_95887", "tokennum": 455}], "negative_passages": []}
{"query_id": "q-en-kubernetes-54ba1bf5d59d0e82c86b99d4defd9317886063bd58ecd9f20ce18b55d6e36396", "query": "// during \"reserve\" extension point or later. func (mc CommunicatingPlugin) Unreserve(ctx context.Context, state *framework.CycleState, pod *v1.Pod, nodeName string) { if pod.Name == \"my-test-pod\" { <del> state.Lock() </del> // The pod is at the end of its lifecycle -- let's clean up the allocated // resources. In this case, our clean up is simply deleting the key written // in the Reserve operation. state.Delete(framework.StateKey(pod.Name)) <del> state.Unlock() </del> } }", "positive_passages": [{"docid": "doc-en-kubernetes-3be32b87589c297c7c2842b086ef786e82de3563d7c057c1ca18b1f858ccd170", "text": "if you want to mutate the top-level keyed value in CycleState, if it's a phase that CycleState is accessed consecutively, such as PreFilter, PreScore, it's safe to mutate CycleState in any manner if it's a phase that CycleState is accessed parallelly, to be race-free, (for now) you only have 1 option: keep the keyed value's pointer unchanged, and use an internal lock to mutate that pointer obj [TBD] we may come up with changes to add read locks to all in-tree plugins when reading values from CycleState, so that the out-of-tree plugin can surround its mutating logic between and - th mutating logic thereby can be any style Any thoughts on the TBD item? I would assume read locks wouldn't cost too much.\nFor now, I think the documentation is correct, it clearly says Read() and Write() are not thread-safe: The key thing here is whether in-tree plugin should use RLock/RUnlock or not. If yes, out-of-tree plugins can be freed to use Lock/Unlock. (see the TBD item in the previous comment)\nI like the TBD, and optimizing for correctness in how in-tree plugins are accessing . I understand the concern with synchronization overhead, but I would be really surprised if it is the bottleneck in scheduling code.\nIt can be, when you have 5k-nodes clusters, or bigger.\nI don't think it will be expensive, a rlock should be equivalent to an atomic add operation (basically it increments the number of readers). As a comparison, looking up the state from the map is likely to be more expensive.\nOf course we are assuming no contention in the default plugins.\nThis is my impression as well. A vanilla version of scheduler doesn't impose write lock in Filter() and Score(), so should be good.\nWe can always see with the benchmarks and revert if its not negligible.\nI will run the benchmarks to see if there is perf downgrade. /assign\nIssues 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\n/remove-lifecycle stale This is still relevant, yes?", "commid": "kubernetes_issue_95887", "tokennum": 535}], "negative_passages": []}
{"query_id": "q-en-kubernetes-54ba1bf5d59d0e82c86b99d4defd9317886063bd58ecd9f20ce18b55d6e36396", "query": "// during \"reserve\" extension point or later. func (mc CommunicatingPlugin) Unreserve(ctx context.Context, state *framework.CycleState, pod *v1.Pod, nodeName string) { if pod.Name == \"my-test-pod\" { <del> state.Lock() </del> // The pod is at the end of its lifecycle -- let's clean up the allocated // resources. In this case, our clean up is simply deleting the key written // in the Reserve operation. state.Delete(framework.StateKey(pod.Name)) <del> state.Unlock() </del> } }", "positive_passages": [{"docid": "doc-en-kubernetes-bcac7b47c31a3bdcd9ddd71bfacab7dca4a98e08ad1188f8a89f61b6d0a63d38", "text": "IIUC the volumebinding plugin has been fixed, but external plugins can still shoot themselves in the foot.\n/priority backlog\nYes. I'm working on this, late this week I will send out a PR along with perf test result.", "commid": "kubernetes_issue_95887", "tokennum": 53}], "negative_passages": []}
{"query_id": "q-en-kubernetes-54d4bf400f0f13a6f7bbcaea607d27c37566fa1530e10ec4fb17634a33965f20", "query": "### Negative caching <del> The `denial` cache TTL has been reduced to the minimum of 5 seconds [here](https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/dns/nodelocaldns/nodelocaldns.yaml#L37). In the unlikely event that this impacts performance, setting this TTL to a higher value make help alleviate issues, but be aware that operations that rely on DNS polling for orchestration may fail (for example operators with StatefulSets). </del> <ins> The `denial` cache TTL has been reduced to the minimum of 5 seconds [here](https://github.com/kubernetes/kubernetes/blob/a38ed2c5ceedf682cbc19442aac5224ae6e10eaa/cluster/addons/dns/nodelocaldns/nodelocaldns.yaml#L61). In the unlikely event that this impacts performance, setting this TTL to a higher value make help alleviate issues, but be aware that operations that rely on DNS polling for orchestration may fail (for example operators with StatefulSets). </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-ffd505027484e14846d7eca4dd46da75100eeb1e560f155a9f5f3a05b8321559", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --This is probably just a documentation / example issue. I'm a real noob so I can just tell this is an issue, but I can't fix the docs through a PR, otherwise I'd do it happily. Hope it's not a dupe. Following the guide at with IPVS. Using the following script: This generates the following YAML (only the interesting part): You see that the line has an extra comma. It's instead of (extra comma after second argument) This generates the following log: Removing the extra comma fixes everything. Setup a cluster with Kube-DNS IPVS mode Generate the nodelocaldns Deploy the manifest Pods are crashing Kubernetes version v1.21.0 Cloud provider or hardware configuration: Bare Metal with HA setup (behind an external LB, Kube-proxy as IPVS) OS (e.g: ): CentOS Linux 8 Kernel (e.g. ): Linux 4.18.0-240.10.1.el83.x8664 SMP Mon Jan 18 17:05:51 UTC 2021 x8664 x8664 x86_64 GNU/LinuxInstall tools: none, a classic kubeadm initNetwork plugin and version (if this is a network-related bug): Not relevant, but Canal (Calico + Flannel) Others: nothing. Love you all for making K8S. Thank you a billion times.\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig docs\n, it seems like that don't get a value return. i saw command in Can you try this again and check if can kubedns get a value?\n/area dns /sig network /assign Documentation here is not changed since Sep 2019 and needs to be updated as well.", "commid": "kubernetes_issue_101339", "tokennum": 514}], "negative_passages": []}
{"query_id": "q-en-kubernetes-54d4bf400f0f13a6f7bbcaea607d27c37566fa1530e10ec4fb17634a33965f20", "query": "### Negative caching <del> The `denial` cache TTL has been reduced to the minimum of 5 seconds [here](https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/dns/nodelocaldns/nodelocaldns.yaml#L37). In the unlikely event that this impacts performance, setting this TTL to a higher value make help alleviate issues, but be aware that operations that rely on DNS polling for orchestration may fail (for example operators with StatefulSets). </del> <ins> The `denial` cache TTL has been reduced to the minimum of 5 seconds [here](https://github.com/kubernetes/kubernetes/blob/a38ed2c5ceedf682cbc19442aac5224ae6e10eaa/cluster/addons/dns/nodelocaldns/nodelocaldns.yaml#L61). In the unlikely event that this impacts performance, setting this TTL to a higher value make help alleviate issues, but be aware that operations that rely on DNS polling for orchestration may fail (for example operators with StatefulSets). </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-d83335fcac537a45eafa3dfd42630478844385174c0958db0174f56a0ffa2f73", "text": "Dual-stack and ipv6 are used more widely now.\nI do get a value, but is replaced with as the extra comma doesn't seem to be replaced.\n/assign", "commid": "kubernetes_issue_101339", "tokennum": 38}], "negative_passages": []}
{"query_id": "q-en-kubernetes-54f8619f2ce1b23bc9473cfd04b8c7e9502001e8c6b90414f2f54ed899e60365", "query": "}) } <ins> // waitForRCPodToDisappear returns nil if the pod from the given replication controller (described by rcName) no longer exists. // In case of failure or too long waiting time, an error is returned. func waitForRCPodToDisappear(c *client.Client, ns, rcName, podName string) error { label := labels.SelectorFromSet(labels.Set(map[string]string{\"name\": rcName})) return waitForPodToDisappear(c, ns, podName, label, 20*time.Second, 5*time.Minute) } </ins> // waitForService waits until the service appears (exist == true), or disappears (exist == false) func waitForService(c *client.Client, namespace, name string, exist bool, interval, timeout time.Duration) error { err := wait.Poll(interval, timeout, func() (bool, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-57d83ef880aa3c3668480a2a99a63d94dfed9404bcfb6c9db559f5ee8b331861", "text": "More detail can be seen in e2e test\ncc\n, Marek Grabowski wrote:\nyou are running an older version of the test. can you get the latest and try again ? This test had not failed at all yesterday in our automated test runs yesterday. Closing issue for now.\nThis failure depends on if the pod is really deleted and kube-proxy (the test container on) catch that the endpoint is deleted in 5s . After sending \"delete pod\" request for 5s, if the pod was still there and kube-proxy still contains this endpoints(this may happen under pressure), hit test can still detect 5 endpoints. At least we should ensure the pod was deleted. Anyway, I think will be helpful to this test. What do you think?\nIt doesn't matter if the pod is actually deleted or not. We just care that kube-proxy thinks that it should not be part of the service endpoint. Having said that, it still doesn't hurt to do the check that you are doing. I will assign your PR to myself and review it. In the meantime, can you rebase your PR ?\nThanks for your review. The PR is up to date.\nFailed twice today in kubernetes-e2e-gce-parallel\nOne more today. The error message is not very helpful.\n18:28:37 STEP: dialing(http) endpointPodIP:endpointHttpPort from node1 18:28:37 STEP: Dialing from node. command:for i in ' wc -l This is the point where the test fails. Am looking into it. We need to have more tries, we just do seq (1 1), instead of seq (6 6). this is causing flakiness.\nFixed by PR", "commid": "kubernetes_issue_14342", "tokennum": 372}], "negative_passages": []}
{"query_id": "q-en-kubernetes-54fbd2d1f5d7308a7d9c0757a250f7dc6544bbe50e57ad3ca55c662fff5a372e", "query": "\"name\":        \"The name of this port.  This must match the 'name' field in the corresponding ServicePort. Must be a DNS_LABEL. Optional only if one port is defined.\", \"port\":        \"The port number of the endpoint.\", \"protocol\":    \"The IP protocol for this port. Must be UDP, TCP, or SCTP. Default is TCP.\", <del> \"appProtocol\": \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and http://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.\", </del> <ins> \"appProtocol\": \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.\", </ins> } func (EndpointPort) SwaggerDoc() map[string]string {", "positive_passages": [{"docid": "doc-en-kubernetes-3e7e95e6f142ca39e6e3ca0b78c3932bd6cbdfdc898eed9d3ffda27d28f904c7", "text": "We should make the change in PR API reference links to should use HTTPS, not HTTP Visit h and look at the IANA hyperlinks Once this fix is made, a PR to is needed to update the docs (by autogenerating them). This typically would be deferred until the next Kubernetes release. v1.23 not applicable not applicable not applicable not applicable not applicable\n/sig docs\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI opened this issue so that someone else can open a new PR that is equivalent to .\n/retitle Update links to IANA for Service Name and Transport Protocol Port Number Registry\nI would like to work on this issue. May I assign it to myself?\nAnyone - including you - is welcome to work on this issue! So long as you've you can open a pull request to propose a fix.\nThanks\n/assign\nI have made the PR. I hope this works. If not then will be happy to do the necessary changes.\nHad to close the previous PR because of issues, here is the new one I made.", "commid": "kubernetes_issue_106980", "tokennum": 300}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5530ad254027c90e2a7f4086fa4e3485e6973a421d0523a414f7e8087d18744a", "query": "}, []string{\"operation\", \"type\"}, ) <ins> etcdObjectCounts = compbasemetrics.NewGaugeVec( &compbasemetrics.GaugeOpts{ Name:              \"etcd_object_counts\", DeprecatedVersion: \"1.21.0\", Help:              \"Number of stored objects at the time of last check split by kind. This metric is replaced by apiserver_storage_object_counts.\", StabilityLevel:    compbasemetrics.ALPHA, }, []string{\"resource\"}, ) </ins> objectCounts = compbasemetrics.NewGaugeVec( &compbasemetrics.GaugeOpts{ <del> Name:           \"etcd_object_counts\", </del> <ins> Name:           \"apiserver_storage_object_counts\", </ins> Help:           \"Number of stored objects at the time of last check split by kind.\", <del> StabilityLevel: compbasemetrics.ALPHA, </del> <ins> StabilityLevel: compbasemetrics.STABLE, </ins> }, []string{\"resource\"}, )", "positive_passages": [{"docid": "doc-en-kubernetes-49b5f1148571079e399a01da886ccfbbffa2370f5f5a5844a5ac847b772993f9", "text": "What would you like to be : We want to start migrating metrics which people depend on for operations to stable status. etcdobjectcounts was mentioned in a recent SIG meeting as a viable candidate. However, the 'etcd' prefix is not in line with stated metric conventions. SIG consensus determined that creating a new version of the metric with the metric name 'apiserverstorageobjectcounts' would be sufficient allow this metric to be promoted. We'd want to simultaneously deprecate 'etcdobjectcounts' (since it would be a duplicate) and remove it after the deprecation grace period window. /assign /cc\nGitHub didn't allow me to assign the following users: erain. 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 : What would you like to be : /cc 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\n/sig instrumentation api-machinery /cc\nAck. I am going to work on this.\n/assign /triage accepted\nIn the SIG api-machinery meeting today, we agreed that the stable version of this metric should be named 'apiserverstorageobject_count'\nThanks and will use in the PR. (And sorry for missing today's meeting - due to a conflict)", "commid": "kubernetes_issue_98270", "tokennum": 331}], "negative_passages": []}
{"query_id": "q-en-kubernetes-554b584bd7dd2413e24450abbdca28b19b8b3807bcee0706ca926975e4e6275d", "query": "Status:     status, } } <ins> func TestPrioritiesRegistered(t *testing.T) { var functionNames []string // Files and directories which priorities may be referenced targetFiles := []string{ \"./../../algorithmprovider/defaults/defaults.go\", // Default algorithm \"./../../factory/plugins.go\",                     // Registered in init() } // List all golang source files under ./priorities/, excluding test files and sub-directories. files, err := codeinspector.GetSourceCodeFiles(\".\") if err != nil { t.Errorf(\"unexpected error: %v when listing files in current directory\", err) } // Get all public priorities in files. for _, filePath := range files { functions, err := codeinspector.GetPublicFunctions(filePath) if err == nil { functionNames = append(functionNames, functions...) } else { t.Errorf(\"unexpected error when parsing %s\", filePath) } } // Check if all public priorities are referenced in target files. for _, functionName := range functionNames { args := []string{\"-rl\", functionName} args = append(args, targetFiles...) err := exec.Command(\"grep\", args...).Run() if err != nil { switch err.Error() { case \"exit status 2\": t.Errorf(\"unexpected error when checking %s\", functionName) case \"exit status 1\": t.Errorf(\"priority %s is implemented as public but seems not registered or used in any other place\", functionName) } } } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-3229e3f28f67afa9ddea85d9d31a50803c261e0ae30f76f950060d1790215e64", "text": "I just noticed you forgot to register the image locality priority function in in I also missed it when I reviewed your PR. I have fixed this in . But it would be great if you could figure out a mechanism that would ensure that all predicate/priority functions that are tested (you can assume they will always live under ) are registered, and fail the test if not. That will allow us to prevent this mistake in the future.\nThanks! Will fix this soon!\nSeems need to wait for in before I send PR? Otherwise this test will always fail ...", "commid": "kubernetes_issue_21236", "tokennum": 114}], "negative_passages": []}
{"query_id": "q-en-kubernetes-555210586c074f6777944574c07886a890eb6d90f2fcc56156ac728f6587bdcc", "query": "} return parameters, nil default: <ins> sort.Slice(objs, func(i, j int) bool { obj1, obj2 := objs[i].(*resourcev1alpha2.ResourceClaimParameters), objs[j].(*resourcev1alpha2.ResourceClaimParameters) if obj1 == nil || obj2 == nil { return false } return obj1.Name < obj2.Name }) </ins> return nil, statusError(logger, fmt.Errorf(\"multiple generated claim parameters for %s.%s %s found: %s\", claim.Spec.ParametersRef.Kind, claim.Spec.ParametersRef.APIGroup, klog.KRef(claim.Namespace, claim.Spec.ParametersRef.Name), klog.KObjSlice(objs))) } }", "positive_passages": [{"docid": "doc-en-kubernetes-16e9d6242dd147113f7225a4b24c8c9581a1b180a6b05f0edc47ba4e0c49bde0", "text": "master-blocking: ci-kubernetes-unit It starts flaking today 30-05-2024 The test fail is This failure may be caused by the error message's order sensitivity. The error message's order of Resource Classes versus is different. N/A /sig node /sig scheduling\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/remove-sig testing /sig scheduling (sig testing doesn't own all of the unit tests, just test frameworks, tooling, CI infra, etc) This appears to be a flake in scheduler unit tests which would be sig scheduling ( )\n.. and it appears to be DRA specific subset of scheduling so /sig node as well\nFYI - looks like this is happening every 3-6 hours give or take. Yesterday it was every six hours and today it seems to be every 3-4 hours. Looking into it a bit more, it looks like it may just be an issue with a connection via the test while it's trying to hit the server. I don't think the test itself is failing, I think the connection to the server is failing. ! CC\nHey All - hope you're well. Michael here from the Release Signal team. Just wanted to touch base and make sure we're good to go for the cut on the 4th. CC /sig-node", "commid": "kubernetes_issue_125221", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-560c0004b45db80d2e276702e7752dcf4c732af802ad719be7239ce6399a6237", "query": "\"PD\" \"ServiceAccounts\" \"Networkingsshouldsfunctionsforsintra-podscommunication\"  # possibly causing Ginkgo to get stuck, issue: #13485 <ins> \"Services.*identicallysnamed\" # error waiting for reachability, issue: #16285 </ins> ) # Tests that should not run on soak cluster.", "positive_passages": [{"docid": "doc-en-kubernetes-a9637d9c1e2cf914512c87528401900f91ad84dba7ec541c905d0670e6dfc824", "text": "Blocking merges, P0\nLooks like this e2e code hasn't changed since .\nUgh. What changed is that we moved it off teh flaky list. Perhaps wrongly so. , Stephen Milner wrote:\nAh, I see. removed a number of e2e service items from variables. Relevant here:\nthe test is actually still running \" Services should serve identically named services in different namespaces on different load-balancers\" is running green.. Saad's fix where we correctly wait for GCE operations to complete, is checked in. Closing this issue.\nLooks like this test is failing forever in and\nSomehow I lost this one. Will look at it ASAP , Janet Kuo wrote:\nThe problem is that this test depends on the api proxy which doesn't do UDP, as far as I can tell, so it could never have worked when UDP support was . I will see what I can do to rectify.\nFixed test is - it's a doozy.\nI've asked oncall to move this to the head of the queue. It's hard to figure out existing flakes when the test driving them has been totally changed. I want to re-examine all flakes after tghis\nis in. I am going to close a few issues and wait for reoccurence, which is to be handled P(-1)", "commid": "kubernetes_issue_16285", "tokennum": 288}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5648b270d50d750b6b9756c341ac44663cbd925e24d002f3e4af814d22987f63", "query": "err = e2epod.WaitForPodContainerStarted(f.ClientSet, f.Namespace.Name, p.Name, 0, framework.PodStartTimeout) framework.ExpectNoError(err) <del> startedTime := time.Now() </del> // We assume the pod became ready when the container became ready. This // is true for a single container pod. err = e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, p.Name, f.Namespace.Name, framework.PodStartTimeout) framework.ExpectNoError(err) <del> readyTime := time.Now() </del> p, err = podClient.Get(context.TODO(), p.Name, metav1.GetOptions{}) framework.ExpectNoError(err)", "positive_passages": [{"docid": "doc-en-kubernetes-17394de51a0297c3b5009d62fc651309bc0945a0e851cb08a887385f3706124d", "text": "<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI --Seems to be impacting a few KIND jobs on the master branch the most, but also assorted other jobs see the triage link above Reported by Sample failure: /sig node <!-- Please see the deflaking doc () for more guidance! --\nxref probing tests\n/assign ref /triage accepted\nThanks Elana, still trying today... Does anyone know if we can use the kubelet logs in e2e tests?\nNot very portably in cluster e2e tests at least. Maybe in node_e2e instead.\nHave you considered that the issue is not with the test but with the underlying code in kubelet like detailed in this issue Like detailed in the issue I can reliably reproduce (on k8s 1.18) the startup probe passing within a few seconds, but the container is only marked as ready after about a minute.\nthere is already a fix in the 1.21 release for that (part of a bigger PR): And actually this test was to verify that part of the code, but unfortunately sometimes it doesn't respond as quick as it should (but never on my PC, only in ci/cd tests)...\nSome recent flakes:\none of the most common flakes in kind jobs currently failures like: Mar 25 17:03:42.508: Pod became ready in 42.007286524s, more than 5s after startupProbe succeeded. It means that the delay readiness probes were not initiated immediately after startup finished.\nMaybe we could speed up the review on\nThank you I will take a look. I'm making a pass through flakes tonight trying to identify if anything is on kind's end\nI don't think it's kind... since running on my PC with kind it works 100%, I think the issue is either the resources... or contention in the queue as mentioned to in the comment\n/milestone v1.22\ncommented on PR with the suggested fix\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository.", "commid": "kubernetes_issue_99979", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5648b270d50d750b6b9756c341ac44663cbd925e24d002f3e4af814d22987f63", "query": "err = e2epod.WaitForPodContainerStarted(f.ClientSet, f.Namespace.Name, p.Name, 0, framework.PodStartTimeout) framework.ExpectNoError(err) <del> startedTime := time.Now() </del> // We assume the pod became ready when the container became ready. This // is true for a single container pod. err = e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, p.Name, f.Namespace.Name, framework.PodStartTimeout) framework.ExpectNoError(err) <del> readyTime := time.Now() </del> p, err = podClient.Get(context.TODO(), p.Name, metav1.GetOptions{}) framework.ExpectNoError(err)", "positive_passages": [{"docid": "doc-en-kubernetes-e379199dcc10ef545e6719d9fd62c8045ba08caeee0b4e30e1a8cba90abc8ed8", "text": "</details\nYeah...\nThanks for your great work in keeping things in check\nFYI\nI have (finally) understood what's happening, and I can even explain why the deflake made things worse... Please have a look at the sleep before the worker starts to process probes: So, you have to remember that we have one worker per pod and per probe, and since we have these probe settings for the test: We have (PeriodSeconds=10) starting sometimes immediately (if the Kubelet has started since more than 10s) or after a quick sleep of rand10s. On the contrary, will likely sleep most of the time for rand60s. This causes a delay in the processing of notifications: If we are lucky, this delay is less than 5s and the test passes: Now you can understand why the deflaked settings were actually worse:\nThe reason I didn't spot these was that I usually start my cluster once for all and iterate on the tests... so the kubelet had plenty of time to start and I never ended in that sleep.\nFor the solution, I suggest we either remove the sleep completely, or we find something that would make all 3 probe workers start at the same time to avoid sync issues... For the record, I was able to spot this issue thanks to the following log error (because the channel was overflowing): What do you think ?\nI have found another issue in that code: If has already ran (and failed), we go to L245 and don't probe via and therefore wait for the next tick, making the test fail.\nThis seems consistent with what I found when I was adding e2es for the new probe-level termination grace period and why I did my timing math the way I did.\n/reopen I don't think this is fixed, I just hit it again and gubernator is still showing plenty of flakes:\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nhow to check the exact commit used for each test?", "commid": "kubernetes_issue_99979", "tokennum": 462}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5648b270d50d750b6b9756c341ac44663cbd925e24d002f3e4af814d22987f63", "query": "err = e2epod.WaitForPodContainerStarted(f.ClientSet, f.Namespace.Name, p.Name, 0, framework.PodStartTimeout) framework.ExpectNoError(err) <del> startedTime := time.Now() </del> // We assume the pod became ready when the container became ready. This // is true for a single container pod. err = e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, p.Name, f.Namespace.Name, framework.PodStartTimeout) framework.ExpectNoError(err) <del> readyTime := time.Now() </del> p, err = podClient.Get(context.TODO(), p.Name, metav1.GetOptions{}) framework.ExpectNoError(err)", "positive_passages": [{"docid": "doc-en-kubernetes-1225e4b3fb518feb838b0b4898217ee9b18190e72a1e6684a1b960954bc011fd", "text": "For instance, I am not sure (from the name) that should include my latest fix...\nIn your PR the fix wasn't there:\nyou may send cherry-pick to 1.21 for which is using kubelet 1.21, not 1.22.\nis using kubelet. Cherry-pick to 1.20 may be needed as well.\nI have found this one that failed even with the fix: corresponding to:\nI don't know what could explain this atm... but it seems we still have delay propagating container statuses.\nIn the job artifacts there are multiple places with this info including the clone records/logs, and In testgrid it's a row.\nyeah afaict since the tests ran on my PR after your fix was merged into master, it showed the flake was still present :( Prow will always use the latest master when running CI.\nSorry for doubting what you said... I was probably in deny and hoped this annoyance was fixed once for all :(\nPlan: we'll see if Clayton's pod lifecycle refactor and/or the jitter refactor for probes affects this.\nClayton's PR jitter refactor\nsince isn't (likely) coming to 1.22 we could cut off 90% of flakes by increasing to 15s delay:\nit seems it fails even after merging so let's continue our discussion on slack\nthis is not a regression, our suggestion is not block release on it. feel free to remove the milestone\n/milestone v1.23\nIn Kubelet maybe, but in the flakiness of the e2e tests it was. Unfortunately we can't easily explore the current state :/\nIn the release blocking jobs the frequency is not horrible now, so unblocking is probably fine, it is not as bad as it was. Outside of the release cycle this is still the flakiest test in some jobs, see e.g. where it's the only flake source we have on record currently.\nif we end up needing it, we have a timing/period adjustment PR we can take that should help with the flakiness with", "commid": "kubernetes_issue_99979", "tokennum": 451}], "negative_passages": []}
{"query_id": "q-en-kubernetes-567786d13e9797f55a9ee626746fb9fb464046680797077b3d691bfdf3d24060", "query": "} } <del> func TestDeletePodForNotExistingNode(t *testing.T) { </del> <ins> func TestDeleteUnscheduledPodForNotExistingNode(t *testing.T) { </ins> for _, f := range []bool{true, false} { defer utilfeaturetesting.SetFeatureGateDuringTest(t, utilfeature.DefaultFeatureGate, features.ScheduleDaemonSetPods, f)() for _, strategy := range updateStrategies() {", "positive_passages": [{"docid": "doc-en-kubernetes-2bd3e1d9e94a5358a6c2d5b4c6b5864c879bb8cabae55e6531ce8f2da7e1ce93", "text": "What happened: Occasionally we get a Daemonset stuck with less Current replicas than Desired, causing a Daemonset sync tends to fix it, e.g (add a new node). This happens to all our Daemonsets. I'm using fluentd as an example. There are no Daemonsets pods in pending nor are there any errors when describing the Daemonset What you expected to happen: The Daemonset Pod to be scheduled How to reproduce it (as minimally and precisely as possible): Reproducing this state is very tricky, I've had the most success by terminating nodes in our ASG causing a new one to come up. However I think I've identified why this is happening. The issue appears to be related to daemonset Pod deletion, a Pod gets deleted causing to trigger, this lowers the expectations by as expected. The delete pod event then triggers a sync of the daemonset, in which it finds which involves fetching pods from the informer cache This is somehow returning the deleted pod. You can see in the logs here thinks that it needs to delete the pod that was deleted. It is also setting the expectation back to after the delete pod event previously lowered it by 1. At this point you're stuck as the function can't get past this line As the expectation can not be satisfied as syncNodes set it back to and there's nothing it to get it back to . So I believe this is what's causing us to get less replicas than expected, the function is stuck due to the expectation so it can't perform a full sync to schedule the new pods. There's also not much to trigger a new sync once the expectation has expired until a new node comes up or one goes down. Environment: Kubernetes version (use ):Cloud provider or hardware configuration: AWS OS (e.g: ):Kernel (e.g. ):\n/sig apps\nI investigated this as much as I could without getting some external input, it feels like it's some kind of race condition in the informer cache. If anyone has ideas of if places to dig deeper that would be handy.\nReiterating the mentions to trigger a notification: <detailsIn response to : I investigated this as much as I could without getting some external input, it feels like it's some kind of race condition in the informer cache. If anyone has ideas of if places to dig deeper that would be handy.", "commid": "kubernetes_issue_75836", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-567786d13e9797f55a9ee626746fb9fb464046680797077b3d691bfdf3d24060", "query": "} } <del> func TestDeletePodForNotExistingNode(t *testing.T) { </del> <ins> func TestDeleteUnscheduledPodForNotExistingNode(t *testing.T) { </ins> for _, f := range []bool{true, false} { defer utilfeaturetesting.SetFeatureGateDuringTest(t, utilfeature.DefaultFeatureGate, features.ScheduleDaemonSetPods, f)() for _, strategy := range updateStrategies() {", "positive_passages": [{"docid": "doc-en-kubernetes-cf3a9a922f150fcd06b37026fcb1a4fe5fd4fd3de4493928a0abbcee85e2e3a6", "text": "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\nThis problem is definitely related to node termination, it's trying to delete the already deleted pod from the node that's been terminated. The problem seems to go away if is set, I think although this kind of race condition may have always been possible, it's being frequently caused via Which is finding the non-existent pod in the pod cache and seeing that it is assigned to a non-running node, resulting in a request to delete the non-existent pod. cc\nReiterating the mentions to trigger a notification: <detailsIn response to : This problem is definitely related to node termination, it's trying to delete the already deleted pod from the node that's been terminated. 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\n/assign could you please take a look at this? It seems that it is related to the code you in .\nThanks for reporting the bug. Bug was introduced in which deleting pods without nodes. There is race condition between removing pod from cache and listing pods for DaemonSet. Bug occurs during following scenario: is deleted. for node is deleted by PodGCController. handler is executed by informer () set is to queue by delete handler () is processed and pods are taken from cache before deleted pod is removed. for deleted pod is not found so we add deleted pod to podsToDelete list (). are set to del:1() succeeds as pod is not found(). are never met so we need to wait till expectations expire. As fix I will send a change to so only pods that can't be deleted by PodGCController are deleted by DaemonSet controller.", "commid": "kubernetes_issue_75836", "tokennum": 399}], "negative_passages": []}
{"query_id": "q-en-kubernetes-567e9a787c6c30f77e581a78503baa45044bc34b24a774b1c0657ba7cb20031c", "query": "return plugin.getFakeVolume(&plugin.Attachers), nil } <ins> func (plugin *FakeVolumePlugin) GetAttachers() (Attachers []*FakeVolume) { plugin.RLock() defer plugin.RUnlock() return plugin.Attachers } </ins> func (plugin *FakeVolumePlugin) GetNewAttacherCallCount() int { plugin.RLock() defer plugin.RUnlock()", "positive_passages": [{"docid": "doc-en-kubernetes-8eb466904f09832d9690a82d180fa467ae255966eba3f5f112ba1d2e4e87f745", "text": "Looks like similar issue with\nThat's the PV controller this is the attach controller, thus separate issues.", "commid": "kubernetes_issue_26377", "tokennum": 21}], "negative_passages": []}
{"query_id": "q-en-kubernetes-56931736f632f9679012371ef7f0bde1fe3fb28f5e7841053d7129a08d6109f4", "query": "defaultBurst = 300 AcceptV1 = runtime.ContentTypeJSON <del> // Aggregated discovery content-type (currently v2beta1). NOTE: Currently, we are assuming the order // for \"g\", \"v\", and \"as\" from the server. We can only compare this string if we can make that assumption. </del> <ins> // Aggregated discovery content-type (v2beta1). NOTE: content-type parameters // MUST be ordered (g, v, as) for server in \"Accept\" header (BUT we are resilient // to ordering when comparing returned values in \"Content-Type\" header). </ins> AcceptV2Beta1 = runtime.ContentTypeJSON + \";\" + \"g=apidiscovery.k8s.io;v=v2beta1;as=APIGroupDiscoveryList\" // Prioritize aggregated discovery by placing first in the order of discovery accept types. acceptDiscoveryFormats = AcceptV2Beta1 + \",\" + AcceptV1", "positive_passages": [{"docid": "doc-en-kubernetes-3257ecff81fbc60fa2a8f982346c462089eb7c896f62cce1d4e02ff6df66d913", "text": "We are using (and ) to interact with Kubernetes clusters behind a couple of proxy layers. One of these proxies completes the headers to include character encoding details. This was working fine until recently, when client-go/kubectl have started to fail when interacting with the discovery API. It seems that a recent change has made kubectl more restrictive of the content-type that it expects. I suspect that it is related to this commit: For example, this is an error from a kubectl command: We can of course try to fix it on our end, removing that charset information. However, it is a valid content-type and the way kubectl is handling the content-type there seems like it is relying on implementation details of kube-apiserver (that it does not add metadata to the content-type). I propose to fix this issue in , by properly parsing and handling the content-type.\ncc /kind regression /kind bug /sig api-machinery /priority important-soon looks like the switch statement in downloadLegacy() needs to be more tolerant of the variety of content-types it can get from a server (including text/plain or no content-type if old servers could have returned that...)\n/transfer kubernetes/kubernetes\nSomething went wrong or the destination repo kubernetes/kubernetes/kubernetes does not exist. <detailsIn response to : /transfer kubernetes/kubernetes 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\n/transfer kubernetes\nYep, the string comparison for the content-type is flimsy, let's address that. Thanks for the report!\n/assign\n/triage accepted\n/cc\nThe fix is being cherry-picked back to: : :", "commid": "kubernetes_issue_117562", "tokennum": 408}], "negative_passages": []}
{"query_id": "q-en-kubernetes-56b5496a0381a88a8a6f08286a4bfff1888b302b118f72acab2a71d6bf353af6", "query": "readyEps := 0 notReadyEps := 0 <del> for i := range pods { // TODO: Do we need to copy here? pod := &(*pods[i]) </del> <ins> for _, pod := range pods { </ins> for i := range service.Spec.Ports { servicePort := &service.Spec.Ports[i]", "positive_passages": [{"docid": "doc-en-kubernetes-6b435dc960bb767c2bbe1807b1f897013b6c97adbc3485d977e3c4a83f87c11f", "text": "Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see ): No. Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST in we have that perform unnecessary shallow copy on pods () : we get the pods from the cache i think we do not mutate the pods (i.e only reading values) so we can avoid this deepCopy i think.\n/assign\n/remove-kind enhancement /kind technical-debt\nThat's actually a shallow copy\n- I'm sorry i was thinking about another issue while filing this one.. I will update the issue, Thanks.\n/sig network", "commid": "kubernetes_issue_46703", "tokennum": 141}], "negative_passages": []}
{"query_id": "q-en-kubernetes-56bc789172b3761f6664748d89733f31ab3a56b39352996332ceb948ab769e28", "query": "# CNI plugins - name: \"cni\" <del> version: 0.8.7 </del> <ins> version: 0.9.1 </ins> refPaths: - path: cluster/gce/gci/configure.sh match: DEFAULT_CNI_VERSION=", "positive_passages": [{"docid": "doc-en-kubernetes-dfff84e3b11879758919fecc393710655267c5015ee34e69e71565465ba5db90", "text": "The latest release of CNI plugins is , but we still have . I'll attempt to create a PR for this based on the .\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig network\n- assigning to you :)", "commid": "kubernetes_issue_102311", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-56cbe84d0c60c05a93376b326a80b34f5b3864dca23bc0f8a8be6a189837883f", "query": "framework.SkipUnlessProviderIs(\"gce\", \"gke\") // Testing a 1.7 version of the sample-apiserver <del> TestSampleAPIServer(f, \"gcr.io/kubernetes-e2e-test-images/k8s-aggregator-sample-apiserver-amd64:1.7\", \"sample-system\") </del> <ins> TestSampleAPIServer(f, \"gcr.io/kubernetes-e2e-test-images/k8s-aggregator-sample-apiserver-amd64:1.7v2\", \"sample-system\") </ins> }) })", "positive_passages": [{"docid": "doc-en-kubernetes-6e9547d1b77f5f5e67275f7358d2b648055755d378e63a99679bc29fa4f8a944", "text": "1 tests failed, 11 jobs failed, 241 builds failed. Failure stats cover 1 day time range '17 Aug 2017 22:57 UTC' to '18 Aug 2017 22:57 UTC'.\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\nSeeing this failure on the e2e release-master-blocking https://k8s- Example failure https://k8s- Looks like an RBAC issue cc\nthis is currently blocking the alpha.3 release\nlooks like this new test was by in which was merged about 6 days ago and is failing consistently\nThis has started failing again on our GKE test suite https://k8s- https://k8s- cc\n[MILESTONENOTIFIER] Milestone Labels Complete Issue label settings: sig/api-machinery: Issue will be escalated to these SIGs if needed. priority/critical-urgent: Never automatically move out of a release milestone; continually escalate to contributor and SIG through all available channels. kind/bug: Fixes a bug discovered during the current release. <detailsAdditional instructions available <a href=\"\"here</aThe commands available for adding these labels are documented <a href=\"\"here</a</details\n/assign\nSeems to be flaking now with the error: https://k8s-\n- we need to determine (today if possible) if this is truly release blocking. If so, please add the release-blocker label. And, if not, how do we best continue work on this for 1.8.x/1.9.0?\nthis test has two passes and four failures on the same commit I'm seeing gke-specific authz grants in that test that are incorrect: That commit removed the wait for the authz grant to become effective (which can lead to flakes), and granted superuser permissions to all users, which is incorrect and invalidates any other authz-related tests run in parallel with this test\ncc\nI can add the wait back.", "commid": "kubernetes_issue_50945", "tokennum": 509}], "negative_passages": []}
{"query_id": "q-en-kubernetes-56cbe84d0c60c05a93376b326a80b34f5b3864dca23bc0f8a8be6a189837883f", "query": "framework.SkipUnlessProviderIs(\"gce\", \"gke\") // Testing a 1.7 version of the sample-apiserver <del> TestSampleAPIServer(f, \"gcr.io/kubernetes-e2e-test-images/k8s-aggregator-sample-apiserver-amd64:1.7\", \"sample-system\") </del> <ins> TestSampleAPIServer(f, \"gcr.io/kubernetes-e2e-test-images/k8s-aggregator-sample-apiserver-amd64:1.7v2\", \"sample-system\") </ins> }) })", "positive_passages": [{"docid": "doc-en-kubernetes-44c35af259d5583c472df6fa7f370aa48aa2c399176d09a89c981e3feb3444e5", "text": "edit: and fix the test given admin to all authenticated users.\nActually after staring at this test for about half an hour I can't figure out what different users exist or what permissions they're being granted. ClientSet, InternalClientset, and AggregatorClient are all initialized from the same config so I don't see how one would be able to create an RBAC binding but another would fail later. any thoughts here?\nI honestly think the gke specific BindClusterRole is a red-herring. It is needed so the client has permission to perform one of the setup steps. (I think it was either to create the wardler cluster role or to bind that role to the anonymous user) Once that setup step is complete we no longer need the that cluster role bound and so I don't think its related.\nThe gke authorizer allows the \u201cbind\u201d verb, so the client can create a binding to the cluster-admin. It cannot create a role directly unless it has permissions via RBAC. Since we don\u2019t have a way to determine the username associated with , binding to all authenticated users is what was done as a workaround.\nI agree that the point at which the tests are failing indicate that the previous authorization issues are not the cause.\n/open\n/reopen\nSo a lot more information to work with now but the error is still occurring. I am still looking into this.\nany update on the investigation?\nFriendly v1.8 release team ping. This failure still seems to be happening, is this actively being worked? Does this need to be in the v1.8 milestone?", "commid": "kubernetes_issue_50945", "tokennum": 342}], "negative_passages": []}
{"query_id": "q-en-kubernetes-56d38b520ee2fc419cc1513ae11284f85ac615e81caa440d49c8fdca426aa775", "query": "\"io/ioutil\" \"net\" \"path/filepath\" <ins> \"time\" </ins> cadvisorapiv1 \"github.com/google/cadvisor/info/v1\" cadvisorv2 \"github.com/google/cadvisor/info/v2\"", "positive_passages": [{"docid": "doc-en-kubernetes-8476bba8e23a7ed885cd34c1077ce17dbf12901ac7ae9725333264f6ea8cfdae", "text": "What happened: A deployment is created that uses a after the cluster master is created but before the cluster worker nodes are fully initialized. During the initialization of the worker nodes, the nodes are temporarily available for scheduling without the necessary label to match the deployment's node selector. Depending on how long the nodes are available for scheduling without the necessary node labels for the deployment, the scheduler will start to spam with cluster with pods in status. This spamming stops once the worker nodes are fully initialized and the pods are scheduled successful. The exact timing of all of this is TBD. What you expected to happen: Pods in status are annoying and require manual cleanup. It would be preferred that the scheduler avoid this an simply issue warning events. How to reproduce it (as minimally and precisely as possible): See issue description. Anything else we need to know?: No. Environment: Kubernetes version (use ): 1.18.3 Cloud provider or hardware configuration: IBM Cloud Kubernetes Service OS (e.g: ): Ubuntu 18.04.4 LTS Kernel (e.g. ): 4.15.0-96-generic Install tools: Managed service install Network plugin and version (if this is a network-related bug): N/A Others: N/A\nRelated to and\n/sig scheduling\nby spamming are you referring to scheduler logs? also, why are the nodes not labelled from the get go?\nJust to confirm, all the pods in question are still in Pending state, yes? If the pods are in pending state, all of them will get scheduled eventually once the nodes get their labels.\nThe pods are not in state. They are actually in state. The pods eventually get scheduled but we are left with anywhere from a few to dozens of these state pods. Also, we are looking at labeling the nodes via kubelet flags to see if that helps.\n/remove-kind bug\nAfter we add some retry logic and wait time in this problem can be solved: As you can see this function returns initial node as the first request failed.\nI also get hit by this, when single controller node gets rebooted and scheduler starts as static container before kubelet becomes ready.", "commid": "kubernetes_issue_92067", "tokennum": 465}], "negative_passages": []}
{"query_id": "q-en-kubernetes-56d38b520ee2fc419cc1513ae11284f85ac615e81caa440d49c8fdca426aa775", "query": "\"io/ioutil\" \"net\" \"path/filepath\" <ins> \"time\" </ins> cadvisorapiv1 \"github.com/google/cadvisor/info/v1\" cadvisorv2 \"github.com/google/cadvisor/info/v2\"", "positive_passages": [{"docid": "doc-en-kubernetes-6c53201dbb91d52a8ade960092a5ed582f4d35e33a53b75d555d15ae815dc25c", "text": "Can be cleaned up with:\n/sig node\nthe spam cycle is this loop: \"pod create, pod schedule, worker reject, pod failed\" -- we don't have a lot of protection in higher level workload controllers to handle pods that fail at kubelet admission time versus pods that just dont create due to quota/admission. in general, is the spam causing any other stability issues? is pod gc pruning the pods?\nI wonder if we can do a trick in node lister to mitigate any race condition here...\nwe could maybe do something similar to to ensure node lister has synced...\nhacking on option to ensure if kubelet has a node lister with a valid kube client, we wait for it to sync at least once here which should mitigate this issue. see:\nWe noticed the problem on the OLM pod which is managed by the OLM operator. Right or wrong, the operator does not like seeing the pod go to status and no longer reconciles the pod. The end result is that manual intervention (i.e. pod deletion) is required to fix the problem.\nsure... i would have thought the pod is failed in that instance and reached a terminal state. either way, i am looking at what i can do to mitigate this.\nThe problem persists in our environment as well, and the workaround cited above will not do anymore. Is there something in the works for this one?\nIssues 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\n/remove-lifecycle stale", "commid": "kubernetes_issue_92067", "tokennum": 383}], "negative_passages": []}
{"query_id": "q-en-kubernetes-56dbcbda8b317d88bda99208dd165d87b0e0d280727a2a0e75bb7a199e4b2ab7", "query": "<ins> # On Collaborative Development Kubernetes is open source, but many of the people working on it do so as their day job.  In order to avoid forcing people to be \"at work\" effectively 24/7, we want to establish some semi-formal protocols around development.  Hopefully these rules make things go more smoothly.  If you find that this is not the case, please complain loudly. ## Patches welcome First and foremost: as a potential contributor, your changes and ideas are welcome at any hour of the day or night, weekdays, weekends, and holidays.  Please do not ever hesitate to ask a question or send a PR. ## Timezones and calendars For the time being, most of the people working on this project are in the US and on Pacific time.  Any times mentioned henceforth will refer to this timezone.  Any references to \"work days\" will refer to the US calendar. ## Code reviews All changes must be code reviewed.  For non-maintainers this is obvious, since you can't commit anyway.  But even for maintainers, we want all changes to get at least one review, preferably from someone who knows the areas the change touches.  For non-trivial changes we may want two reviewers.  The primary reviewer will make this decision and nominate a second reviewer, if needed.  Except for trivial changes, PRs should sit for at least a 2 hours to allow for wider review. Most PRs will find reviewers organically.  If a maintainer intends to be the primary reviewer of a PR they should set themselves as the assignee on GitHub and say so in a reply to the PR.  Only the primary reviewer of a change should actually do the merge, except in rare cases (e.g. they are unavailable in a reasonable timeframe). If a PR has gone 2 work days without an owner emerging, please poke the PR thread and ask for a reviewer to be assigned. Except for rare cases, such as trivial changes (e.g. typos, comments) or emergencies (e.g. broken builds), maintainers should not merge their own changes. Expect reviewers to request that you avoid [common go style mistakes](https://code.google.com/p/go-wiki/wiki/CodeReviewComments) in your PRs. ## Assigned reviews Maintainers can assign reviews to other maintainers, when appropriate. The assignee becomes the shepherd for that PR and is responsible for merging the PR once they are satisfied with it or else closing it.  The assignee might request reviews from non-maintainers. ## Merge hours Maintainers will do merges between the hours of 7:00 am Monday and 7:00 pm (19:00h) Friday.  PRs that arrive over the weekend or on holidays will only be merged if there is a very good reason for it and if the code review requirements have been met. There may be discussion an even approvals granted outside of the above hours, but merges will generally be deferred. ## Holds Any maintainer or core contributor who wants to review a PR but does not have time immediately may put a hold on a PR simply by saying so on the PR discussion and offering an ETA measured in single-digit days at most.  Any PR that has a hold shall not be merged until the person who requested the hold acks the review, withdraws their hold, or is overruled by a preponderance of maintainers. </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-7c5448078f172c3dba4d1f6f6ed5d66f21d2fc0ea9dd38dbb1ed9b4cc49eea15", "text": "Right now, we have a mixture of user documentation and developer documentation in the top-level directory. We should make it easier to find a just user documentation. Step 1 would be to move developer documentation into a subdir like docs/development or something like that. User docs would stay in the top-level docs dir.\nmove to", "commid": "kubernetes_issue_1797", "tokennum": 71}], "negative_passages": []}
{"query_id": "q-en-kubernetes-571ee7a4513ff13ac1a6add674e596945fd8383798b677da575f5d9967088b24", "query": "pod.Status.ContainerStatuses = test.oldStatuses podStatus.ContainerStatuses = test.statuses apiStatus := kubelet.generateAPIPodStatus(pod, podStatus) <del> verifyStatus(t, i, apiStatus, test.expectedState, test.expectedLastTerminationState) </del> <ins> assert.NoError(t, verifyContainerStatuses(apiStatus.ContainerStatuses, test.expectedState, test.expectedLastTerminationState), \"case %d\", i) } // Everything should be the same for init containers for i, test := range tests { kubelet.reasonCache = NewReasonCache() for n, e := range test.reasons { kubelet.reasonCache.add(pod.UID, n, e, \"\") } pod.Spec.InitContainers = test.containers pod.Status.InitContainerStatuses = test.oldStatuses podStatus.ContainerStatuses = test.statuses apiStatus := kubelet.generateAPIPodStatus(pod, podStatus) expectedState := test.expectedState if test.expectedInitState != nil { expectedState = test.expectedInitState } assert.NoError(t, verifyContainerStatuses(apiStatus.InitContainerStatuses, expectedState, test.expectedLastTerminationState), \"case %d\", i) } } // Test generateAPIPodStatus with different restart policies. func TestGenerateAPIPodStatusWithDifferentRestartPolicies(t *testing.T) { testErrorReason := fmt.Errorf(\"test-error\") emptyContainerID := (&kubecontainer.ContainerID{}).String() testKubelet := newTestKubelet(t) kubelet := testKubelet.kubelet pod := podWithUidNameNs(\"12345678\", \"foo\", \"new\") containers := []api.Container{{Name: \"succeed\"}, {Name: \"failed\"}} podStatus := &kubecontainer.PodStatus{ ID:        pod.UID, Name:      pod.Name, Namespace: pod.Namespace, ContainerStatuses: []*kubecontainer.ContainerStatus{ { Name:     \"succeed\", State:    kubecontainer.ContainerStateExited, ExitCode: 0, }, { Name:     \"failed\", State:    kubecontainer.ContainerStateExited, ExitCode: 1, }, { Name:     \"succeed\", State:    kubecontainer.ContainerStateExited, ExitCode: 2, }, { Name:     \"failed\", State:    kubecontainer.ContainerStateExited, ExitCode: 3, }, }, } kubelet.reasonCache.add(pod.UID, \"succeed\", testErrorReason, \"\") kubelet.reasonCache.add(pod.UID, \"failed\", testErrorReason, \"\") for c, test := range []struct { restartPolicy                api.RestartPolicy expectedState                map[string]api.ContainerState expectedLastTerminationState map[string]api.ContainerState // Only set expectedInitState when it is different from expectedState expectedInitState map[string]api.ContainerState // Only set expectedInitLastTerminationState when it is different from expectedLastTerminationState expectedInitLastTerminationState map[string]api.ContainerState }{ { restartPolicy: api.RestartPolicyNever, expectedState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    0, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID, }}, }, expectedLastTerminationState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    2, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    3, ContainerID: emptyContainerID, }}, }, }, { restartPolicy: api.RestartPolicyOnFailure, expectedState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    0, ContainerID: emptyContainerID, }}, \"failed\": {Waiting: &api.ContainerStateWaiting{Reason: testErrorReason.Error()}}, }, expectedLastTerminationState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    2, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID, }}, }, }, { restartPolicy: api.RestartPolicyAlways, expectedState: map[string]api.ContainerState{ \"succeed\": {Waiting: &api.ContainerStateWaiting{Reason: testErrorReason.Error()}}, \"failed\":  {Waiting: &api.ContainerStateWaiting{Reason: testErrorReason.Error()}}, }, expectedLastTerminationState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    0, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID, }}, }, // If the init container is terminated with exit code 0, it won't be restarted even when the // restart policy is RestartAlways. expectedInitState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    0, ContainerID: emptyContainerID, }}, \"failed\": {Waiting: &api.ContainerStateWaiting{Reason: testErrorReason.Error()}}, }, expectedInitLastTerminationState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    2, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID, }}, }, }, } { pod.Spec.RestartPolicy = test.restartPolicy // Test normal containers pod.Spec.Containers = containers apiStatus := kubelet.generateAPIPodStatus(pod, podStatus) expectedState, expectedLastTerminationState := test.expectedState, test.expectedLastTerminationState assert.NoError(t, verifyContainerStatuses(apiStatus.ContainerStatuses, expectedState, expectedLastTerminationState), \"case %d\", c) pod.Spec.Containers = nil // Test init containers pod.Spec.InitContainers = containers apiStatus = kubelet.generateAPIPodStatus(pod, podStatus) if test.expectedInitState != nil { expectedState = test.expectedInitState } if test.expectedInitLastTerminationState != nil { expectedLastTerminationState = test.expectedInitLastTerminationState } assert.NoError(t, verifyContainerStatuses(apiStatus.InitContainerStatuses, expectedState, expectedLastTerminationState), \"case %d\", c) pod.Spec.InitContainers = nil </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-b4459e221a04f6723f7b97c6a9d43d61c0d65417b08d143223c7057699636055", "text": "is this a Node bug? cc as next oncall to follow up on this.\nThis is a node bug due to init containers\nI may need help debugging - I see:\nSo I think the problem is in the error case - we're not properly recording that the start failed, and the next time we come in we somehow think the first container succeeded. I'll add some debugging to see if we can't recreate it.\nLet's discuss on instead.", "commid": "kubernetes_issue_25879", "tokennum": 102}], "negative_passages": []}
{"query_id": "q-en-kubernetes-571ee7a4513ff13ac1a6add674e596945fd8383798b677da575f5d9967088b24", "query": "pod.Status.ContainerStatuses = test.oldStatuses podStatus.ContainerStatuses = test.statuses apiStatus := kubelet.generateAPIPodStatus(pod, podStatus) <del> verifyStatus(t, i, apiStatus, test.expectedState, test.expectedLastTerminationState) </del> <ins> assert.NoError(t, verifyContainerStatuses(apiStatus.ContainerStatuses, test.expectedState, test.expectedLastTerminationState), \"case %d\", i) } // Everything should be the same for init containers for i, test := range tests { kubelet.reasonCache = NewReasonCache() for n, e := range test.reasons { kubelet.reasonCache.add(pod.UID, n, e, \"\") } pod.Spec.InitContainers = test.containers pod.Status.InitContainerStatuses = test.oldStatuses podStatus.ContainerStatuses = test.statuses apiStatus := kubelet.generateAPIPodStatus(pod, podStatus) expectedState := test.expectedState if test.expectedInitState != nil { expectedState = test.expectedInitState } assert.NoError(t, verifyContainerStatuses(apiStatus.InitContainerStatuses, expectedState, test.expectedLastTerminationState), \"case %d\", i) } } // Test generateAPIPodStatus with different restart policies. func TestGenerateAPIPodStatusWithDifferentRestartPolicies(t *testing.T) { testErrorReason := fmt.Errorf(\"test-error\") emptyContainerID := (&kubecontainer.ContainerID{}).String() testKubelet := newTestKubelet(t) kubelet := testKubelet.kubelet pod := podWithUidNameNs(\"12345678\", \"foo\", \"new\") containers := []api.Container{{Name: \"succeed\"}, {Name: \"failed\"}} podStatus := &kubecontainer.PodStatus{ ID:        pod.UID, Name:      pod.Name, Namespace: pod.Namespace, ContainerStatuses: []*kubecontainer.ContainerStatus{ { Name:     \"succeed\", State:    kubecontainer.ContainerStateExited, ExitCode: 0, }, { Name:     \"failed\", State:    kubecontainer.ContainerStateExited, ExitCode: 1, }, { Name:     \"succeed\", State:    kubecontainer.ContainerStateExited, ExitCode: 2, }, { Name:     \"failed\", State:    kubecontainer.ContainerStateExited, ExitCode: 3, }, }, } kubelet.reasonCache.add(pod.UID, \"succeed\", testErrorReason, \"\") kubelet.reasonCache.add(pod.UID, \"failed\", testErrorReason, \"\") for c, test := range []struct { restartPolicy                api.RestartPolicy expectedState                map[string]api.ContainerState expectedLastTerminationState map[string]api.ContainerState // Only set expectedInitState when it is different from expectedState expectedInitState map[string]api.ContainerState // Only set expectedInitLastTerminationState when it is different from expectedLastTerminationState expectedInitLastTerminationState map[string]api.ContainerState }{ { restartPolicy: api.RestartPolicyNever, expectedState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    0, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID, }}, }, expectedLastTerminationState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    2, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    3, ContainerID: emptyContainerID, }}, }, }, { restartPolicy: api.RestartPolicyOnFailure, expectedState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    0, ContainerID: emptyContainerID, }}, \"failed\": {Waiting: &api.ContainerStateWaiting{Reason: testErrorReason.Error()}}, }, expectedLastTerminationState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    2, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID, }}, }, }, { restartPolicy: api.RestartPolicyAlways, expectedState: map[string]api.ContainerState{ \"succeed\": {Waiting: &api.ContainerStateWaiting{Reason: testErrorReason.Error()}}, \"failed\":  {Waiting: &api.ContainerStateWaiting{Reason: testErrorReason.Error()}}, }, expectedLastTerminationState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    0, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID, }}, }, // If the init container is terminated with exit code 0, it won't be restarted even when the // restart policy is RestartAlways. expectedInitState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    0, ContainerID: emptyContainerID, }}, \"failed\": {Waiting: &api.ContainerStateWaiting{Reason: testErrorReason.Error()}}, }, expectedInitLastTerminationState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    2, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID, }}, }, }, } { pod.Spec.RestartPolicy = test.restartPolicy // Test normal containers pod.Spec.Containers = containers apiStatus := kubelet.generateAPIPodStatus(pod, podStatus) expectedState, expectedLastTerminationState := test.expectedState, test.expectedLastTerminationState assert.NoError(t, verifyContainerStatuses(apiStatus.ContainerStatuses, expectedState, expectedLastTerminationState), \"case %d\", c) pod.Spec.Containers = nil // Test init containers pod.Spec.InitContainers = containers apiStatus = kubelet.generateAPIPodStatus(pod, podStatus) if test.expectedInitState != nil { expectedState = test.expectedInitState } if test.expectedInitLastTerminationState != nil { expectedLastTerminationState = test.expectedInitLastTerminationState } assert.NoError(t, verifyContainerStatuses(apiStatus.InitContainerStatuses, expectedState, expectedLastTerminationState), \"case %d\", c) pod.Spec.InitContainers = nil </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-dcc88d1d89328d1da3366de828afcd8ab0373228cc4437ea655e2cda79030f86", "text": "Kubelet issues a docker inspect call after creating a container, but for very short lived containers there is a window in which they could exit before being inspected in the docker manager. If the container PID is 0, we should check the ExitCode and other relevant fields and handle them appropriately. [1] This is the suspected cause of several flakes: /cc\nlooking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: I'd expect the second one to not have run in this case? Node logs:\nInit containers have an implicit assumption that container statuses include results of previous SyncPod invocations. If that's not the case we may need to fix that (or at least mitigate it). On May 18, 2016, at 8:28 PM, Prashanth B wrote: looking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: May 18 15:58:33.380: INFO: pod-init--1d4b-11e6-80a4- started at 2016-05-18T15:58:04-07:00 (2+1 container statuses recorded) May 18 15:58:33.380: INFO: Init container init1 ready: false, restart count 0 May 18 15:58:33.380: INFO: Init container init2 ready: true, restart count 0 I'd expect the second one to not have run in this case? Node logs: \u2014 You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub\nThis should be true. Is there any evidence that suggests the opposite? only shows conflicting view of whether init1 has run.\nIf the container exits already and it's not an infra container, kubelet should not error out. Although even if it does, I failed to see how this could affect the readiness of the init container without checking the code further.", "commid": "kubernetes_issue_25844", "tokennum": 487}], "negative_passages": []}
{"query_id": "q-en-kubernetes-571ee7a4513ff13ac1a6add674e596945fd8383798b677da575f5d9967088b24", "query": "pod.Status.ContainerStatuses = test.oldStatuses podStatus.ContainerStatuses = test.statuses apiStatus := kubelet.generateAPIPodStatus(pod, podStatus) <del> verifyStatus(t, i, apiStatus, test.expectedState, test.expectedLastTerminationState) </del> <ins> assert.NoError(t, verifyContainerStatuses(apiStatus.ContainerStatuses, test.expectedState, test.expectedLastTerminationState), \"case %d\", i) } // Everything should be the same for init containers for i, test := range tests { kubelet.reasonCache = NewReasonCache() for n, e := range test.reasons { kubelet.reasonCache.add(pod.UID, n, e, \"\") } pod.Spec.InitContainers = test.containers pod.Status.InitContainerStatuses = test.oldStatuses podStatus.ContainerStatuses = test.statuses apiStatus := kubelet.generateAPIPodStatus(pod, podStatus) expectedState := test.expectedState if test.expectedInitState != nil { expectedState = test.expectedInitState } assert.NoError(t, verifyContainerStatuses(apiStatus.InitContainerStatuses, expectedState, test.expectedLastTerminationState), \"case %d\", i) } } // Test generateAPIPodStatus with different restart policies. func TestGenerateAPIPodStatusWithDifferentRestartPolicies(t *testing.T) { testErrorReason := fmt.Errorf(\"test-error\") emptyContainerID := (&kubecontainer.ContainerID{}).String() testKubelet := newTestKubelet(t) kubelet := testKubelet.kubelet pod := podWithUidNameNs(\"12345678\", \"foo\", \"new\") containers := []api.Container{{Name: \"succeed\"}, {Name: \"failed\"}} podStatus := &kubecontainer.PodStatus{ ID:        pod.UID, Name:      pod.Name, Namespace: pod.Namespace, ContainerStatuses: []*kubecontainer.ContainerStatus{ { Name:     \"succeed\", State:    kubecontainer.ContainerStateExited, ExitCode: 0, }, { Name:     \"failed\", State:    kubecontainer.ContainerStateExited, ExitCode: 1, }, { Name:     \"succeed\", State:    kubecontainer.ContainerStateExited, ExitCode: 2, }, { Name:     \"failed\", State:    kubecontainer.ContainerStateExited, ExitCode: 3, }, }, } kubelet.reasonCache.add(pod.UID, \"succeed\", testErrorReason, \"\") kubelet.reasonCache.add(pod.UID, \"failed\", testErrorReason, \"\") for c, test := range []struct { restartPolicy                api.RestartPolicy expectedState                map[string]api.ContainerState expectedLastTerminationState map[string]api.ContainerState // Only set expectedInitState when it is different from expectedState expectedInitState map[string]api.ContainerState // Only set expectedInitLastTerminationState when it is different from expectedLastTerminationState expectedInitLastTerminationState map[string]api.ContainerState }{ { restartPolicy: api.RestartPolicyNever, expectedState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    0, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID, }}, }, expectedLastTerminationState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    2, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    3, ContainerID: emptyContainerID, }}, }, }, { restartPolicy: api.RestartPolicyOnFailure, expectedState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    0, ContainerID: emptyContainerID, }}, \"failed\": {Waiting: &api.ContainerStateWaiting{Reason: testErrorReason.Error()}}, }, expectedLastTerminationState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    2, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID, }}, }, }, { restartPolicy: api.RestartPolicyAlways, expectedState: map[string]api.ContainerState{ \"succeed\": {Waiting: &api.ContainerStateWaiting{Reason: testErrorReason.Error()}}, \"failed\":  {Waiting: &api.ContainerStateWaiting{Reason: testErrorReason.Error()}}, }, expectedLastTerminationState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    0, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID, }}, }, // If the init container is terminated with exit code 0, it won't be restarted even when the // restart policy is RestartAlways. expectedInitState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    0, ContainerID: emptyContainerID, }}, \"failed\": {Waiting: &api.ContainerStateWaiting{Reason: testErrorReason.Error()}}, }, expectedInitLastTerminationState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    2, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID, }}, }, }, } { pod.Spec.RestartPolicy = test.restartPolicy // Test normal containers pod.Spec.Containers = containers apiStatus := kubelet.generateAPIPodStatus(pod, podStatus) expectedState, expectedLastTerminationState := test.expectedState, test.expectedLastTerminationState assert.NoError(t, verifyContainerStatuses(apiStatus.ContainerStatuses, expectedState, expectedLastTerminationState), \"case %d\", c) pod.Spec.Containers = nil // Test init containers pod.Spec.InitContainers = containers apiStatus = kubelet.generateAPIPodStatus(pod, podStatus) if test.expectedInitState != nil { expectedState = test.expectedInitState } if test.expectedInitLastTerminationState != nil { expectedLastTerminationState = test.expectedInitLastTerminationState } assert.NoError(t, verifyContainerStatuses(apiStatus.InitContainerStatuses, expectedState, expectedLastTerminationState), \"case %d\", c) pod.Spec.InitContainers = nil </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-ade5deee53831749acf4a20dbe39f9ef1836656ae43e40b0bb8594efa4e81e92", "text": "Each syncPod invocation, we inspect the list of init container in order looking for lastTerminationState. There could be a bug in that logic, or if we didn't get the full status, we might make a bad decision. When determining which container to run next, we always look for the last init container in the chain that has success, then run the next container (unless the pod is RestartNever). , Yu-Ju Hong wrote:\nSaw this flake again. How do we verify that container status is not lost between syn pods?\n... between calls to syncPods\nThe second sync clearly saw the init1 container, and decided to launch init2. See \"InitContainersToKeep\" in the message below.\ncontainers to keep can include failed containers. , Yu-Ju Hong wrote:\nDiscussed on slack. In summary, the problem has to do with how we convert the kubecontainer.PodStatus to the api.PodStatus. If a container is terminated, the function makes the decisions: the pod restart policy is \"Always\", and there is a \"failure reason\" recorded for the given container, this means the pod worker tried to (re)start the container but failed. Set the state to \"Waiting\" and populate the reason. , the container state is simply \"terminated\". Init containers don't obey the restart policy like regular containers, and the logic will need to be amended to work with them. is working on a PR. In addition to that, kubelet should not error out if a user container exited before it could apply the oom score (which is best effort in this case). fixes that.\nAhh, thanks for digging into the issue. This is the exact the concern I had when I reviewed the initial implementation of init container, which blocks pr for a while. I even asked to help me verify this case, unfortunately we didn't reproduce the issue back then. :-(\nI wish I'd seen the flakes in the runs prior to merge.\nWe didn't notice this until we started running the tests against docker v1.11.1, which is much faster and hit the race condition differently.\nI suppose that's a good thing...\nIt is hard to reproduce this.", "commid": "kubernetes_issue_25844", "tokennum": 482}], "negative_passages": []}
{"query_id": "q-en-kubernetes-571ee7a4513ff13ac1a6add674e596945fd8383798b677da575f5d9967088b24", "query": "pod.Status.ContainerStatuses = test.oldStatuses podStatus.ContainerStatuses = test.statuses apiStatus := kubelet.generateAPIPodStatus(pod, podStatus) <del> verifyStatus(t, i, apiStatus, test.expectedState, test.expectedLastTerminationState) </del> <ins> assert.NoError(t, verifyContainerStatuses(apiStatus.ContainerStatuses, test.expectedState, test.expectedLastTerminationState), \"case %d\", i) } // Everything should be the same for init containers for i, test := range tests { kubelet.reasonCache = NewReasonCache() for n, e := range test.reasons { kubelet.reasonCache.add(pod.UID, n, e, \"\") } pod.Spec.InitContainers = test.containers pod.Status.InitContainerStatuses = test.oldStatuses podStatus.ContainerStatuses = test.statuses apiStatus := kubelet.generateAPIPodStatus(pod, podStatus) expectedState := test.expectedState if test.expectedInitState != nil { expectedState = test.expectedInitState } assert.NoError(t, verifyContainerStatuses(apiStatus.InitContainerStatuses, expectedState, test.expectedLastTerminationState), \"case %d\", i) } } // Test generateAPIPodStatus with different restart policies. func TestGenerateAPIPodStatusWithDifferentRestartPolicies(t *testing.T) { testErrorReason := fmt.Errorf(\"test-error\") emptyContainerID := (&kubecontainer.ContainerID{}).String() testKubelet := newTestKubelet(t) kubelet := testKubelet.kubelet pod := podWithUidNameNs(\"12345678\", \"foo\", \"new\") containers := []api.Container{{Name: \"succeed\"}, {Name: \"failed\"}} podStatus := &kubecontainer.PodStatus{ ID:        pod.UID, Name:      pod.Name, Namespace: pod.Namespace, ContainerStatuses: []*kubecontainer.ContainerStatus{ { Name:     \"succeed\", State:    kubecontainer.ContainerStateExited, ExitCode: 0, }, { Name:     \"failed\", State:    kubecontainer.ContainerStateExited, ExitCode: 1, }, { Name:     \"succeed\", State:    kubecontainer.ContainerStateExited, ExitCode: 2, }, { Name:     \"failed\", State:    kubecontainer.ContainerStateExited, ExitCode: 3, }, }, } kubelet.reasonCache.add(pod.UID, \"succeed\", testErrorReason, \"\") kubelet.reasonCache.add(pod.UID, \"failed\", testErrorReason, \"\") for c, test := range []struct { restartPolicy                api.RestartPolicy expectedState                map[string]api.ContainerState expectedLastTerminationState map[string]api.ContainerState // Only set expectedInitState when it is different from expectedState expectedInitState map[string]api.ContainerState // Only set expectedInitLastTerminationState when it is different from expectedLastTerminationState expectedInitLastTerminationState map[string]api.ContainerState }{ { restartPolicy: api.RestartPolicyNever, expectedState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    0, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID, }}, }, expectedLastTerminationState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    2, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    3, ContainerID: emptyContainerID, }}, }, }, { restartPolicy: api.RestartPolicyOnFailure, expectedState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    0, ContainerID: emptyContainerID, }}, \"failed\": {Waiting: &api.ContainerStateWaiting{Reason: testErrorReason.Error()}}, }, expectedLastTerminationState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    2, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID, }}, }, }, { restartPolicy: api.RestartPolicyAlways, expectedState: map[string]api.ContainerState{ \"succeed\": {Waiting: &api.ContainerStateWaiting{Reason: testErrorReason.Error()}}, \"failed\":  {Waiting: &api.ContainerStateWaiting{Reason: testErrorReason.Error()}}, }, expectedLastTerminationState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    0, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID, }}, }, // If the init container is terminated with exit code 0, it won't be restarted even when the // restart policy is RestartAlways. expectedInitState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    0, ContainerID: emptyContainerID, }}, \"failed\": {Waiting: &api.ContainerStateWaiting{Reason: testErrorReason.Error()}}, }, expectedInitLastTerminationState: map[string]api.ContainerState{ \"succeed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    2, ContainerID: emptyContainerID, }}, \"failed\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID, }}, }, }, } { pod.Spec.RestartPolicy = test.restartPolicy // Test normal containers pod.Spec.Containers = containers apiStatus := kubelet.generateAPIPodStatus(pod, podStatus) expectedState, expectedLastTerminationState := test.expectedState, test.expectedLastTerminationState assert.NoError(t, verifyContainerStatuses(apiStatus.ContainerStatuses, expectedState, expectedLastTerminationState), \"case %d\", c) pod.Spec.Containers = nil // Test init containers pod.Spec.InitContainers = containers apiStatus = kubelet.generateAPIPodStatus(pod, podStatus) if test.expectedInitState != nil { expectedState = test.expectedInitState } if test.expectedInitLastTerminationState != nil { expectedLastTerminationState = test.expectedInitLastTerminationState } assert.NoError(t, verifyContainerStatuses(apiStatus.InitContainerStatuses, expectedState, expectedLastTerminationState), \"case %d\", c) pod.Spec.InitContainers = nil </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-0814a4e75b48cf2d27d20141c180e04fbc9b55d5398cce31b037f460c93acb1b", "text": "The extra check of last terminated container in your initial code makes me nervous, but we couldn't reproduce it due to that small race windows until we have a faster docker running on the node. :-)\nI got \"Pods should invoke init containers on a RestartAlways pod\" flake (referenced from ): Logs:\nAll the fixes went in. Please reopen this issue if you see any more flakes.", "commid": "kubernetes_issue_25844", "tokennum": 90}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5749562a999dd60af238f73e28f8414df70230290516a9fa683e666e449109eb", "query": "func TestRegisterExistingNodeWithApiserver(t *testing.T) { testKubelet := newTestKubelet(t) kubelet := testKubelet.kubelet <del> kubelet.hostname = \"127.0.0.1\" </del> kubeClient := testKubelet.fakeKubeClient kubeClient.ReactFn = func(action testclient.FakeAction) (runtime.Object, error) { segments := strings.Split(action.Action, \"-\")", "positive_passages": [{"docid": "doc-en-kubernetes-d16ca614c05197aa8b2652e3bf008c3a9a5ce41d960188a2ba3459b13d8b1102", "text": "Looks like some kubelet unit tests perform a lookupIp which ends up depending on the health of the local resolver. Specifically has this failing: Which leads to the test in: And we recently swapped out the node names from testnode to 127.0.0.1, so probably the culprit?\n/ref\nInteresting. I did swap out the node names in the unit test as part of to be 127.0.0.1, party because I thought that it wouldn't have any problems resolving during unit tests.\n/cc", "commid": "kubernetes_issue_8549", "tokennum": 113}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5749562a999dd60af238f73e28f8414df70230290516a9fa683e666e449109eb", "query": "func TestRegisterExistingNodeWithApiserver(t *testing.T) { testKubelet := newTestKubelet(t) kubelet := testKubelet.kubelet <del> kubelet.hostname = \"127.0.0.1\" </del> kubeClient := testKubelet.fakeKubeClient kubeClient.ReactFn = func(action testclient.FakeAction) (runtime.Object, error) { segments := strings.Split(action.Action, \"-\")", "positive_passages": [{"docid": "doc-en-kubernetes-4a4c75dd985aaeba56d487bbde17d68f0425afc5d7e1167fdf1a1abcb97cd0b6", "text": "cc\nWhat is the environment where you are running the tests? They pass for me on my mac, a linux box, and shippable seems to be passing them as well.\nI couldn 't reproduce the failure either.\nI'm out right now; i'll try them when i get back. For the record, I run hack/test- Paul Morie wrote:\nAhem FTR This acronym is going to go quad-plat Paul Morie wrote:\nI ran on both platforms and saw the tests pass.\nI'm still seeing it. Won't have bandwidth to dig in personally until tomorrow.\nseeing a similar failure after a git pull\nI knew I wasn't crazy\nenvironment: fedora 21, golang: 1.4, docker: 1.6\nI think I see the problem. When I set the node name to in the test I was assuming it would parse as a valid ip address and not end up at the LookupIP call. But only the node name (and not the kubelet hostname) is being set (except in my new test where I ) so it's trying to do a lookup. Do you think you could test just changing the default hostname from \"testnode\" to \"127.0.0.1\" and see if that fixes it for you?\nTrying now\nI still get failures but no panic / threaddump.\ngist coming\nthis looks like again?\nGood that it isn't panicing any longer. I can dig into the test failures tomorrow (I think it should be relatively simple to resolve).\ncool, thanks for looking\nPasses in master now for me. Closing.\nFYI, they will break again once goes in, and then we can merge my PR to see if that fixes it for you.\n:+1:\nis in -- are these tests breaking again?\nI just rebased which I think will fix them.\nThey are breaking again.\nis on it.", "commid": "kubernetes_issue_8522", "tokennum": 407}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5765858ad7ac60327254a71e4b388f99d89e116aabaf3172efb74839a2fc7222", "query": "// Handle the containers failed to be started, which should be in Waiting state. for _, container := range containers { <ins> if isInitContainer { // If the init container is terminated with exit code 0, it won't be restarted. // TODO(random-liu): Handle this in a cleaner way. s := podStatus.FindContainerStatusByName(container.Name) if s != nil && s.State == kubecontainer.ContainerStateExited && s.ExitCode == 0 { continue } } </ins> // If a container should be restarted in next syncpod, it is *Waiting*. if !kubecontainer.ShouldContainerBeRestarted(&container, pod, podStatus) { continue", "positive_passages": [{"docid": "doc-en-kubernetes-b4459e221a04f6723f7b97c6a9d43d61c0d65417b08d143223c7057699636055", "text": "is this a Node bug? cc as next oncall to follow up on this.\nThis is a node bug due to init containers\nI may need help debugging - I see:\nSo I think the problem is in the error case - we're not properly recording that the start failed, and the next time we come in we somehow think the first container succeeded. I'll add some debugging to see if we can't recreate it.\nLet's discuss on instead.", "commid": "kubernetes_issue_25879", "tokennum": 102}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5765858ad7ac60327254a71e4b388f99d89e116aabaf3172efb74839a2fc7222", "query": "// Handle the containers failed to be started, which should be in Waiting state. for _, container := range containers { <ins> if isInitContainer { // If the init container is terminated with exit code 0, it won't be restarted. // TODO(random-liu): Handle this in a cleaner way. s := podStatus.FindContainerStatusByName(container.Name) if s != nil && s.State == kubecontainer.ContainerStateExited && s.ExitCode == 0 { continue } } </ins> // If a container should be restarted in next syncpod, it is *Waiting*. if !kubecontainer.ShouldContainerBeRestarted(&container, pod, podStatus) { continue", "positive_passages": [{"docid": "doc-en-kubernetes-dcc88d1d89328d1da3366de828afcd8ab0373228cc4437ea655e2cda79030f86", "text": "Kubelet issues a docker inspect call after creating a container, but for very short lived containers there is a window in which they could exit before being inspected in the docker manager. If the container PID is 0, we should check the ExitCode and other relevant fields and handle them appropriately. [1] This is the suspected cause of several flakes: /cc\nlooking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: I'd expect the second one to not have run in this case? Node logs:\nInit containers have an implicit assumption that container statuses include results of previous SyncPod invocations. If that's not the case we may need to fix that (or at least mitigate it). On May 18, 2016, at 8:28 PM, Prashanth B wrote: looking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: May 18 15:58:33.380: INFO: pod-init--1d4b-11e6-80a4- started at 2016-05-18T15:58:04-07:00 (2+1 container statuses recorded) May 18 15:58:33.380: INFO: Init container init1 ready: false, restart count 0 May 18 15:58:33.380: INFO: Init container init2 ready: true, restart count 0 I'd expect the second one to not have run in this case? Node logs: \u2014 You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub\nThis should be true. Is there any evidence that suggests the opposite? only shows conflicting view of whether init1 has run.\nIf the container exits already and it's not an infra container, kubelet should not error out. Although even if it does, I failed to see how this could affect the readiness of the init container without checking the code further.", "commid": "kubernetes_issue_25844", "tokennum": 487}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5765858ad7ac60327254a71e4b388f99d89e116aabaf3172efb74839a2fc7222", "query": "// Handle the containers failed to be started, which should be in Waiting state. for _, container := range containers { <ins> if isInitContainer { // If the init container is terminated with exit code 0, it won't be restarted. // TODO(random-liu): Handle this in a cleaner way. s := podStatus.FindContainerStatusByName(container.Name) if s != nil && s.State == kubecontainer.ContainerStateExited && s.ExitCode == 0 { continue } } </ins> // If a container should be restarted in next syncpod, it is *Waiting*. if !kubecontainer.ShouldContainerBeRestarted(&container, pod, podStatus) { continue", "positive_passages": [{"docid": "doc-en-kubernetes-ade5deee53831749acf4a20dbe39f9ef1836656ae43e40b0bb8594efa4e81e92", "text": "Each syncPod invocation, we inspect the list of init container in order looking for lastTerminationState. There could be a bug in that logic, or if we didn't get the full status, we might make a bad decision. When determining which container to run next, we always look for the last init container in the chain that has success, then run the next container (unless the pod is RestartNever). , Yu-Ju Hong wrote:\nSaw this flake again. How do we verify that container status is not lost between syn pods?\n... between calls to syncPods\nThe second sync clearly saw the init1 container, and decided to launch init2. See \"InitContainersToKeep\" in the message below.\ncontainers to keep can include failed containers. , Yu-Ju Hong wrote:\nDiscussed on slack. In summary, the problem has to do with how we convert the kubecontainer.PodStatus to the api.PodStatus. If a container is terminated, the function makes the decisions: the pod restart policy is \"Always\", and there is a \"failure reason\" recorded for the given container, this means the pod worker tried to (re)start the container but failed. Set the state to \"Waiting\" and populate the reason. , the container state is simply \"terminated\". Init containers don't obey the restart policy like regular containers, and the logic will need to be amended to work with them. is working on a PR. In addition to that, kubelet should not error out if a user container exited before it could apply the oom score (which is best effort in this case). fixes that.\nAhh, thanks for digging into the issue. This is the exact the concern I had when I reviewed the initial implementation of init container, which blocks pr for a while. I even asked to help me verify this case, unfortunately we didn't reproduce the issue back then. :-(\nI wish I'd seen the flakes in the runs prior to merge.\nWe didn't notice this until we started running the tests against docker v1.11.1, which is much faster and hit the race condition differently.\nI suppose that's a good thing...\nIt is hard to reproduce this.", "commid": "kubernetes_issue_25844", "tokennum": 482}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5765858ad7ac60327254a71e4b388f99d89e116aabaf3172efb74839a2fc7222", "query": "// Handle the containers failed to be started, which should be in Waiting state. for _, container := range containers { <ins> if isInitContainer { // If the init container is terminated with exit code 0, it won't be restarted. // TODO(random-liu): Handle this in a cleaner way. s := podStatus.FindContainerStatusByName(container.Name) if s != nil && s.State == kubecontainer.ContainerStateExited && s.ExitCode == 0 { continue } } </ins> // If a container should be restarted in next syncpod, it is *Waiting*. if !kubecontainer.ShouldContainerBeRestarted(&container, pod, podStatus) { continue", "positive_passages": [{"docid": "doc-en-kubernetes-0814a4e75b48cf2d27d20141c180e04fbc9b55d5398cce31b037f460c93acb1b", "text": "The extra check of last terminated container in your initial code makes me nervous, but we couldn't reproduce it due to that small race windows until we have a faster docker running on the node. :-)\nI got \"Pods should invoke init containers on a RestartAlways pod\" flake (referenced from ): Logs:\nAll the fixes went in. Please reopen this issue if you see any more flakes.", "commid": "kubernetes_issue_25844", "tokennum": 90}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5765d6343e6fe9d07f240791343fec09f7880c9e759dd9a30367586af9170be0", "query": "} /* <del> Release : v1.12 Testname: Security Context: runAsUser (id:65534) Description: Container created with runAsUser option, passing an id (id:65534) uses that given id when running the container. This test is marked LinuxOnly since Windows does not support running as UID / GID. </del> <ins> Release : v1.15 Testname: Security Context, runAsUser=65534 Description: Container is created with runAsUser option by passing uid 65534 to run as unpriviledged user. Pod MUST be in Succeeded phase. [LinuxOnly]: This test is marked as LinuxOnly since Windows does not support running as UID / GID. </ins> */ <del> It(\"should run the container with uid 65534 [LinuxOnly] [NodeConformance]\", func() { </del> <ins> framework.ConformanceIt(\"should run the container with uid 65534 [LinuxOnly] [NodeConformance]\", func() { </ins> createAndWaitUserPod(65534) }) /* <del> Release : v1.12 Testname: Security Context: runAsUser (id:0) Description: Container created with runAsUser option, passing an id (id:0) uses that given id when running the container. This test is marked LinuxOnly since Windows does not support running as UID / GID. </del> <ins> Release : v1.15 Testname: Security Context, runAsUser=0 Description: Container is created with runAsUser option by passing uid 0 to run as root priviledged user. Pod MUST be in Succeeded phase. This e2e can not be promoted to Conformance because a Conformant platform may not allow to run containers with 'uid 0' or running privileged operations. [LinuxOnly]: This test is marked as LinuxOnly since Windows does not support running as UID / GID. </ins> */ It(\"should run the container with uid 0 [LinuxOnly] [NodeConformance]\", func() { createAndWaitUserPod(0)", "positive_passages": [{"docid": "doc-en-kubernetes-f8a45a347ca0a58053d8639059bb6be0a8ec66e1196dbd0290c02922abc9dcd2", "text": "/kind cleanup /area conformance /area test /sig node /sig testing /sig architecture /assign /assign We have a number of tests that only have the tag that may make sense as tests, we should identify whether these tests cases meet (or could meet) the . We should open PR's to promote these if so. I would advise starting with the test/common cases\nGitHub didn't allow me to assign the following users: mgdevstack, mkurylec. Note that only and repo collaborators can be assigned. For more information please see <detailsIn response to : /kind cleanup /area conformance /area test /sig node /sig testing /sig architecture /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\n/assign\nThe tests in test/e2enode don't actually get run as part of Conformance as near as I can tell. If we want to run them as part of conformance, they need to be migrated into test/e2e/common. Some of the tests in e2enode may not be able to be ported over because they assume a level access we don't have in a conformance environment.\nregarding this testcase: [sig-storage] HostPath should support r/w [NodeConformance]: It uses hostPath and privileged=true, to read/write from /tmp folder. Which would you suggest is the best orientation to overcome the privilege mode setting and allow its promotion?\n/assign\nRegarding , the suite runs the test only if the kubelet configuration was required to have the QOS (cgroups-per-qos) enabled. This configuration for the kubelet is selected at the time the cluster is set up. Looking for where this might be configured found: where is set to true. For other settings it is also configured to true. where is set to true. BUT also found where it is mentioned that the flag is no longer available. Questions: would it be ok to promote this test to be conformance, even it can be skipped based on configuration of the cluster? And not supported in the containerized kubelet?\nI would consider cgroups to be an implementation detail that Conformance shouldn't be verifying\nIt uses hostPath and privileged=true, to read/write from /tmp folder.", "commid": "kubernetes_issue_66875", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5765d6343e6fe9d07f240791343fec09f7880c9e759dd9a30367586af9170be0", "query": "} /* <del> Release : v1.12 Testname: Security Context: runAsUser (id:65534) Description: Container created with runAsUser option, passing an id (id:65534) uses that given id when running the container. This test is marked LinuxOnly since Windows does not support running as UID / GID. </del> <ins> Release : v1.15 Testname: Security Context, runAsUser=65534 Description: Container is created with runAsUser option by passing uid 65534 to run as unpriviledged user. Pod MUST be in Succeeded phase. [LinuxOnly]: This test is marked as LinuxOnly since Windows does not support running as UID / GID. </ins> */ <del> It(\"should run the container with uid 65534 [LinuxOnly] [NodeConformance]\", func() { </del> <ins> framework.ConformanceIt(\"should run the container with uid 65534 [LinuxOnly] [NodeConformance]\", func() { </ins> createAndWaitUserPod(65534) }) /* <del> Release : v1.12 Testname: Security Context: runAsUser (id:0) Description: Container created with runAsUser option, passing an id (id:0) uses that given id when running the container. This test is marked LinuxOnly since Windows does not support running as UID / GID. </del> <ins> Release : v1.15 Testname: Security Context, runAsUser=0 Description: Container is created with runAsUser option by passing uid 0 to run as root priviledged user. Pod MUST be in Succeeded phase. This e2e can not be promoted to Conformance because a Conformant platform may not allow to run containers with 'uid 0' or running privileged operations. [LinuxOnly]: This test is marked as LinuxOnly since Windows does not support running as UID / GID. </ins> */ It(\"should run the container with uid 0 [LinuxOnly] [NodeConformance]\", func() { createAndWaitUserPod(0)", "positive_passages": [{"docid": "doc-en-kubernetes-b0f7522fd47a7c9f3d30009b5f18d7b37ba2aa8723a4c0ef112b90078054f0fc", "text": "Which would you suggest is the best orientation to overcome the privilege mode setting and allow its promotion? Michelle Au If my understanding is correct, on some platforms, writing to /tmp requires privileged. I don't see a way to to remove that requirement.\nIf my understanding is correct, on some platforms, writing to /tmp requires privileged. I don't see a way to to remove that requirement. Yeah writing to host doesn't seem like a thing we can expect of conformance tests. I wonder if it makes sense to tag this test with something to denote the requirement, ie: I see some tests in test/e2e_node use\nThe hostpath tests in already have a comment explaining this. Maybe the comment should be updated to be more clear that that is the reason why we can't add it to conformance.\nThat's /tmp on the host or in the container filesystem?\n/tmp on the host\nping what else remains to be done before we close this out? I am guessing that we want to close , is there anything beyond that?\nOnce tests under (issue- ) and are promoted we are good to close this issue. Short update for reference- None of [NodeConformance] tests from \"test/e2e_node\" seems eligible for [Conformance] promotion at this moment due to node level dependencies. Remaining [NodeConformance] tests from \"test/e2e\" has following status - Waiting for to be closed and then below tests would be promoted to Conformance Needs to be Promoted Can not be promoted to Conformance as //Slow by design Can not be promoted due to Node level dependency\nIssues 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\n/remove-lifecycle stale\n/lifecycle frozen\n/assign", "commid": "kubernetes_issue_66875", "tokennum": 428}], "negative_passages": []}
{"query_id": "q-en-kubernetes-57964512d36716ef7d0fea65e16c561e29bc5265043e40afd85708689006fbed", "query": "srcs = [ \"alpha.go\", \"annotate.go\", <ins> \"apiresources.go\", </ins> \"apiversions.go\", \"apply.go\", \"apply_edit_last_applied.go\",", "positive_passages": [{"docid": "doc-en-kubernetes-3c17ea4b4f4a9bb23915ee9fbb41703ef0532ac00becc05b8dda4d23a9ea9da2", "text": "As the RBAC role need to be related to resources. I think we could use a command to get the supported resources. ref to\nThis would be cool.\nI thought we a command that listed resources in the discover doc a long time ago.\nis just the versions, but principle is the same. We want to list all the types, their resources, and tie that back to \"explain\".\nWhat's the best way to determine this information currently? I'm having difficulty figuring out the exact set of permissions (and how they would be written in an RBAC role) for any given kubectl command. The documentation for this right now is split across multiple places and certain things are not explained at all. Specifically, it's difficult to determine which \"API verb\" is used for which operations. Take as an example. It's unclear if the way to allow this is to use the \"proxy\" subresource of a pod or service with \"get\"/\"create\"/etc. verbs, or to use the \"proxy\" verb with the resource (pod, service) directly. is a similar case. The almost works for this purpose, but it's still difficult. Operations for a given resource are grouped into categories like write, read, status, and proxy, but these things don't obviously correlate with API verbs. Again, proxy is especially confusing as there is no mention of a proxy \"verb\". The API operations are only shown using their HTTP verbs. One thing that could help on this document would be a section on the right column under \"kubectl command\" that shows exactly the rule needed in an RBAC role to allow this command via kubectl. And even then, that assumes an exact 1-to-1 mapping between API endpoints and kubectl commands, which I doubt is always the case. (For example, port fowarding to a pod seems to require both a GET on the pod resource and a CREATE on a port forward subresource.) There also needs to be better documentation about how this information could have been determined in the first place. I've resorted to manually looking through API requests made with but even then it's difficult to figure out. Amusingly, I was the one who wrote which is referenced in the original issue description (as well as the table explaining verbs in ).", "commid": "kubernetes_issue_42932", "tokennum": 494}], "negative_passages": []}
{"query_id": "q-en-kubernetes-57964512d36716ef7d0fea65e16c561e29bc5265043e40afd85708689006fbed", "query": "srcs = [ \"alpha.go\", \"annotate.go\", <ins> \"apiresources.go\", </ins> \"apiversions.go\", \"apply.go\", \"apply_edit_last_applied.go\",", "positive_passages": [{"docid": "doc-en-kubernetes-20fd632aaf82ba3efee7609ebeda29ca6df3199abf73ef8bcfe417660974a0ce", "text": "tl;dr: It's too difficult right now to go from \"I want a user to be able to run \" to \"here is the RBAC rule to use for that\" for any case where there isn't a specific example shown in the docs.\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nIt seem that relative PR stop updated. If this issue still valuable, i will help fix it\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close", "commid": "kubernetes_issue_42932", "tokennum": 279}], "negative_passages": []}
{"query_id": "q-en-kubernetes-58309873e8f237c1d75ea5028283534cd2880873563fdca39be6e674447b1d47", "query": "if [[ ${GOOS} == \"windows\" ]]; then bin=\"${bin}.exe\" fi <del> CGO_ENABLED=0 go build -installsuffix cgo -o \"${output_path}/${bin}\"  </del> <ins> go build -o \"${output_path}/${bin}\"  </ins> \"${goflags[@]:+${goflags[@]}}\"  -ldflags \"${version_ldflags}\"  \"${binary}\" done else <del> CGO_ENABLED=0 go install -installsuffix cgo \"${goflags[@]:+${goflags[@]}}\"  </del> <ins> go install \"${goflags[@]:+${goflags[@]}}\"  </ins> -ldflags \"${version_ldflags}\"  \"${binaries[@]}\" fi", "positive_passages": [{"docid": "doc-en-kubernetes-6be393fdfa676676e2c2a919450eea6e64e7299e61f3fdbea996cf6d1af38cd8", "text": "We've seen this a few times on GCE now, and I saw it flake on now as well (cc\ncc Victor integrated cadvisor into the kubelet. I wonder if a fake version of cadvisor gets integrated into kubelet in the case of builds.\nI noticed this first on GCE. (FWIW, GKE uses the same binaries as GCE.)\nJenkins shows the following four changes for the GCE build where this test started consistently failing: Commit by mattmoor Enable usage of a \"json key\" for authenticating with Commit by dbsmith Add a system modeler to scheduler Commit by dawnchen Convert RestartPolicy to string for v1beta3. Commit by abshah Build statically linked binaryies. With the change to go 1.4, we probably were generating dynamically linked binaries accidentally.\nIf I had to guess, I would take a stab and say it was , . cc\nFeel free to revert by 5pm if no fix.\nI believe and are correct, makes the build not use cgo which places a fake cAdvisor in the binary and that fails. Looking into the fix.\nis out, it is a revert of the old one along with a plan for not needing static binaries.", "commid": "kubernetes_issue_5517", "tokennum": 266}], "negative_passages": []}
{"query_id": "q-en-kubernetes-58662a5122d3152d2fbb43a63310c53efd2c9e0f78db29d63370da8bec27bce5", "query": "// +k8s:deepcopy-gen=package <del> package testing </del> <ins> package testing // import \"k8s.io/apimachinery/pkg/runtime/testing\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-460ceb7b52a1ab0cadc1b29d7eee5cc1013b8d23be9bca0d145119ffcf7b27c6", "text": "Look at one of the directories under (Please don't pick more than one directory for one PR as it will cause issues for reviewers) Find all the files named (example find -name ) See the following link it has a this tells tools how this package needs to be imported. So we should ensure that each has an import Add a description appropriate to the package (similar to the one below) Look through sub directories and see if there are any other important directories that are likely to be used by outside users and add a Why are we doing this? We perfer to use vanity urls instead of directly using to refer to code, so this helps ensure that tools honor our wish. See It would be good to have some package level documentation since these directories under staging/ are meant to be for use by folks outside of kubernetes github org. /good-first-issue\n/kind documentation /sig architecture\ncurrently working my through Not going to use / assign since there could be a number of PRs for this issue.\n/lifecycle active /good-first-issue edit: hmm..\nThis request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /lifecycle active /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\nMay I try on\nIIUC this means that there needs to be a even at the root of the repo? Then how does work? :thinking:\nHi , can I make a PR for this directory ?\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_68231", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-58662a5122d3152d2fbb43a63310c53efd2c9e0f78db29d63370da8bec27bce5", "query": "// +k8s:deepcopy-gen=package <del> package testing </del> <ins> package testing // import \"k8s.io/apimachinery/pkg/runtime/testing\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-5f31f1c27d7198dc83b313154ff681043a8b41e17eb5d3ddf32cd84bc023f931", "text": "/lifecycle rotten\nI guess this is still not done, was supposed to partially fix this issue. /reopen\nReopened this issue. <detailsIn response to : I guess this is still not done, was supposed to partially fix this 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\n/remove-lifecycle rotten /area code-organization", "commid": "kubernetes_issue_68231", "tokennum": 93}], "negative_passages": []}
{"query_id": "q-en-kubernetes-586d4e5bda1015b03871fd1a80bd3a69a6ce8d4fd43be5fde9e48fd1696845bb", "query": "} fn := func() error { <del> if !p.Quiet && stderr != nil { fmt.Fprintln(stderr, \"If you don't see a command prompt, try pressing enter.\") } </del> restClient, err := restclient.RESTClientFor(p.Config) if err != nil { return err", "positive_passages": [{"docid": "doc-en-kubernetes-cf7ef9edd7e31f4b8286dd6738f8e55df1658c21b56557082b0f1b4070aed850", "text": "First, the formatting. Second, \"init-ctr-demo_demos\" is an internal artifact, not fit for human-facing errors. Third, the container DOES exist, it's just in a terminating state.\nThe formatting issue should be fixed by . Regarding to the pod name, I think is better. As for the pod name, the error message is from the HTTP response of kubelet server. I've looked at the code, functions defined in interface are using ($podName_podNamespace) to identify a pod. Without spiting the parameter into two separated parameters, it could be tricky to change the output format of an error message. Personally I would prefer to change the signatures, but I don't know if we are planing to do it. In order to improve the readability, I a client-side check for pod status. See .", "commid": "kubernetes_issue_56450", "tokennum": 184}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5891a553b763786ca965f35fb043ac2f8a11ebb55c4890ae10ff8d1d2a0dbd52", "query": "return v.target.WithKind(src.Kind), true } } <ins> if v.coerce && len(kinds) > 0 { return v.target.WithKind(kinds[0].Kind), true } </ins> return schema.GroupVersionKind{}, false }", "positive_passages": [{"docid": "doc-en-kubernetes-7ee140198c665b218e0dfb7e3cd2f2624912887cfcfab5f30828d12c6130aa35", "text": "What happened: Set up a HA cluster with 1.9 and 1.10 API servers (occurs on any apiserver skew boundary where a cohabitating resource's storage version changed groups) Observed errors when modifying workload objects: when modified via the 1.10 server, saw this error in the 1.9 server: when modified via the 1.9 server, saw this error in the 1.10 server: When this error was encountered, all watchers for the resource in question would be dropped and have to re-establish, and the internal watchers feeding the watch cache would drop and re-establish What you expected to happen: Watch events from all supported storage versions are processed correctly How to reproduce it (as minimally and precisely as possible): Start a server from master (for inspectability, store in json). With Create a deployment (e.g. kube-dns in kube-system) Establish a watch via extensions (kubectl get deployments.extensions --all-namespaces -w) Establish a watch via apps (kubectl get --all-namespaces -w) Tail the kube-apiserver log Change the apps/v1 deployment in etcd to extensions/v1beta1: Observer client watches drop and server log errors: Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: /sig api-machinery /cc /priority critical-urgent\nerror is triggered by this returning false: constructed here: the info about expected cohabitating groups is not included in the list of acceptable inputs", "commid": "kubernetes_issue_73478", "tokennum": 368}], "negative_passages": []}
{"query_id": "q-en-kubernetes-58cfa79db15c0869c9d140c472c12933cb529008f1a39edb0c8cb31a44324efd", "query": "framework.ExpectNotEqual(len(list.Groups), 0, \"Missing APIGroups\") for _, group := range list.Groups { <ins> if strings.HasSuffix(group.Name, \".example.com\") { // ignore known example dynamic API groups that are added/removed during the e2e test run continue } </ins> framework.Logf(\"Checking APIGroup: %v\", group.Name) // locate APIGroup endpoint", "positive_passages": [{"docid": "doc-en-kubernetes-d1e994e5749edcd07edbd0f19c7df9185dabd2833b25fd1731e4d47ccf8dce07", "text": "<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI --Which jobs are flaking: pull-kubernetes-e2e-gce Which test(s) are flaking: Discovery should validate PreferredVersion for each APIGroup Testgrid link: Reason for failure: The test does not handle API groups which are or removed dynamically during the run of the test. Just because an API group is present in at the beginning of the test does not mean or will be present by the end of the test. This is particularly true for the dynamic/custom-resource API groups registered/unregistered during the e2e test run /sig api-machinery /assign\nmitigation opened at\nSaw this today in It seems to happen relatively often Likely due to the CRD created in: Should the ValidatingAdmissionPolicy test CRD have its group name template changed to match the existing test exclusion for groups ending in /cc", "commid": "kubernetes_issue_93215", "tokennum": 222}], "negative_passages": []}
{"query_id": "q-en-kubernetes-59034e49b7eaf1b05febc6724155e6838a183334eb05cee23896bb0778b2d7ad", "query": "namespace quota. The creation MUST fail release: v1.15 file: test/e2e/apps/rc.go <ins> - testname: Replication Controller, lifecycle codename: '[sig-apps] ReplicationController should test the lifecycle of a ReplicationController [Conformance]' description: A Replication Controller (RC) is created, read, patched, and deleted with verification. release: v1.20 file: test/e2e/apps/rc.go </ins> - testname: StatefulSet, Burst Scaling codename: '[sig-apps] StatefulSet [k8s.io] Basic StatefulSet functionality [StatefulSetBasic] Burst scaling should run to completion even with unhealthy pods [Slow] [Conformance]'", "positive_passages": [{"docid": "doc-en-kubernetes-04298a57bb6bbadab2ae389c253044418da070e519876e8a987add6c4a3d1714", "text": "[x] Original approval issue: Start 9 June 2020 3 Flakes No Flakes for 2 weeks According to this APIsnoop query, there are still some remaining ReplicationController endpoints which are untested. a ReplicationController with a static label the ReplicationController with a new Label and updated data the ReplicationController's status /Scale the ReplicationController's Replica count to 2 Replicas the ReplicationController the ReplicationController's Status all ReplicationControllers in all Namespaces find the ReplicationControllers(1) ensure that the ReplicationController is found and is patched Namespaced ReplicationControllers(1) via a Collection with a LabelSelector Discover useragents: See all endpoints hit from this test Display test coverage change If a test with these calls gets merged, test coverage will go up by 7 points This test is also created with the goal of conformance promotion.\n/sig testing /sig architecture /area conformance\nCan you please add in PR\n/reopen Merged. Promotion to be created\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nIssues 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\n/remove-lifecycle stale", "commid": "kubernetes_issue_90881", "tokennum": 354}], "negative_passages": []}
{"query_id": "q-en-kubernetes-591b42be501c5c6f3178ec5fd9df9fb0edb5be05eaf769147a567cd3d5fdb4e2", "query": "\"k8s.io/kubernetes/test/e2e/framework\" ) <del> const minFileSize = 1 * framework.MiB </del> <ins> const ( minFileSize = 1 * framework.MiB fileSizeSmall  = 1 * framework.MiB fileSizeMedium = 100 * framework.MiB fileSizeLarge  = 1 * framework.GiB ) // MD5 hashes of the test file corresponding to each file size. // Test files are generated in testVolumeIO() // If test file generation algorithm changes, these must be recomputed. var md5hashes = map[int64]string{ fileSizeSmall:  \"5c34c2813223a7ca05a3c2f38c0d1710\", fileSizeMedium: \"f2fa202b1ffeedda5f3a58bd1ae81104\", fileSizeLarge:  \"8d763edc71bd16217664793b5a15e403\", } </ins> // Return the plugin's client pod spec. Use an InitContainer to setup the file i/o test env. func makePodSpec(config framework.VolumeTestConfig, dir, initCmd string, volsrc v1.VolumeSource, podSecContext *v1.PodSecurityContext) *v1.Pod {", "positive_passages": [{"docid": "doc-en-kubernetes-540712d0b27ee7f52d7d02bd3719013304c1ce42c6b5d8b93c3ee3671a9c1c7c", "text": "The \"Volume plugin streaming [Slow] NFS should write files of various sizes, verify size, validate content\" e2e test is failing on our 2k-node gce clusters (https://k8s-) with the following error: cc\nCould you take a look into it or reassign as apt? This is part of the correctness suite and large cluster tests are release-blocking.\n/assign\nis this run using the kubemark environment? I'll also take a look. It could be that the commands this test needs to execute may not work with kubemark. /assign\ncc\nNo, this is not kubemark. This is on a real 2000-node cluster.\nAlso all other volume-related e2e tests are passing, except this one.\nLooking at the log I see that the nfs test fails trying to verify the test file's content. The test exec's into the nfs client pod and executes: The return code from above is 127. The test then deletes the nfs client pod calling which works. The nfs-server pod is deleted in the AfterEach. For some reason the reported error is 137 but the returned err 127. The same command is exec'd for all of the tested storage plugins so not sure why it's failing just for nfs. Error 127 might be \"command not found\".\nThe other strange thing is that it's only failing in this suite and not the others.\nWhen I look at the kubelet log, I see the exec command coming through: I also see these suspicious kubelet soon afterwards: So I think the grep command is causing the node to run out of memory and get evicted. I think we can fix this either by: Making the grep command more memory efficient. I'm guessing it's reading the whole file into memory or, Make this test Serial so that it doesn't run in parallel with other pods, since it consumes a lot of memory.\nAn unrelated issue, is that the node allocatable feature didn't actually evict the pod. Instead this pod got a system OOM kill. /cc\nrelated to the memcg notifications, not node allocatable. Thanks!\nany theories why we see this only for the nfs-io tests, and not the glusterfs-io test for instance?\nthe gluster test didn't run on this in this suite.", "commid": "kubernetes_issue_51717", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-591b42be501c5c6f3178ec5fd9df9fb0edb5be05eaf769147a567cd3d5fdb4e2", "query": "\"k8s.io/kubernetes/test/e2e/framework\" ) <del> const minFileSize = 1 * framework.MiB </del> <ins> const ( minFileSize = 1 * framework.MiB fileSizeSmall  = 1 * framework.MiB fileSizeMedium = 100 * framework.MiB fileSizeLarge  = 1 * framework.GiB ) // MD5 hashes of the test file corresponding to each file size. // Test files are generated in testVolumeIO() // If test file generation algorithm changes, these must be recomputed. var md5hashes = map[int64]string{ fileSizeSmall:  \"5c34c2813223a7ca05a3c2f38c0d1710\", fileSizeMedium: \"f2fa202b1ffeedda5f3a58bd1ae81104\", fileSizeLarge:  \"8d763edc71bd16217664793b5a15e403\", } </ins> // Return the plugin's client pod spec. Use an InitContainer to setup the file i/o test env. func makePodSpec(config framework.VolumeTestConfig, dir, initCmd string, volsrc v1.VolumeSource, podSecContext *v1.PodSecurityContext) *v1.Pod {", "positive_passages": [{"docid": "doc-en-kubernetes-fd4ca8cfd935058701597731533334687f2913bf0b9d409a83f3ac801f0182e1", "text": "I'm suspecting that the reason why we didn't see a problem with this test on other suites is that the load could be higher here. I've asked to see if we can reduce the memory usage of the grep call.\npointed out that there are no newlines in the generated file, so when grep is called it could buffer the entire file in memory. Adding a newline at the end of the dd input file should do it.\n/priority critical-urgent\n[MILESTONENOTIFIER] Milestone Labels Complete Issue label settings: sig/scalability sig/storage: Issue will be escalated to these SIGs if needed. priority/critical-urgent: Never automatically move out of a release milestone; continually escalate to contributor and SIG through all available channels. kind/bug: Fixes a bug discovered during the current release. <detailsAdditional instructions available <a href=\"\"here</a</details\nIt seems like even if the generated file is broken up by newlines, grep could still use on the order of hundreds of MB of memory for a 100MiB file (even with the -m1 and -F options). We could check the file line by line, but it would take a long time. A better solution would be to check the MD5 file hash. It's fast and uses little memory. The expected hashes will be hard-coded into the test, and if different file sizes are in the future, a hash needs to be computed and as well.\nThanks a lot for fixing this!\nRef", "commid": "kubernetes_issue_51717", "tokennum": 322}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5942d75cfa7a69c14666ad6f951408012954c803e0aba5e4fe1bb36b924946d7", "query": "Command:       getSchedulerCommand(cfg), LivenessProbe: componentProbe(10251, \"/healthz\"), Resources:     componentResources(\"100m\"), <ins> Env:           getProxyEnvVars(), </ins> }), }", "positive_passages": [{"docid": "doc-en-kubernetes-dc3be6ce7b42d453edf0753a2cf7546d061a63c2e475384cc9c94a48a05e7f4a", "text": "Is this a request for help? No What keywords did you search in Kubernetes issues before filing this one? http proxy, httpproxy, httpsproxy, AWS, kubeadm, kubectl, cloud-provider Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT Kubernetes version (use ): v1.4.4 Environment: Cloud provider or hardware configuration: kubeadm on EC2 instances on AWS OS (e.g. from /etc/os-release): Ubuntu 16.04.1 LTS Kernel (e.g. ): Linux ip-10-0-133-99 4.4.0-45-generic -Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x8664 x8664 x8664 GNU/Linux Install tools: kubeadm Others: httpproxy, httpsproxy and noproxy set in /etc/environment, Docker config as well on startup scripts that run What happened: won't complete and gets stuck on it's first deployment. When one looks through the logs it shows that the pods are downloading fine but we are stuck due to the kube-controller-manager continually crashing as it can't contact AWS. Elsewhere in kubernetes I see references to and if the AWS cloud provider could use that it would be able to connect as well. From the POD if I manually set httpproxy and httpsproxy and no_proxy I am able to use the AWS CLI without any issues. What you expected to happen: I would expect to successfully complete and use the environment proxies set up on the system so as not to depend on a default Internet Gateway being connected to the VPC just for AWS access. How to reproduce it (as minimally and precisely as possible): Set up a public VPC with Squid set up as a proxy Set up a private VPC peered to the public VPC Set up a master node and run Set up a regular node and run will never fully initialize. If you remove the --cloud-provider aws` then it will complete and nodes will register. Anything else do we need to know:\nwhat do you have in proxy variables ? (env | grep -i proxy) it tries to connect to (tcp 176.32.118.53:443) directly. You're expecting to connect there via proxy ? then do you have something like in your no_proxy ?", "commid": "kubernetes_issue_36573", "tokennum": 535}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5942d75cfa7a69c14666ad6f951408012954c803e0aba5e4fe1bb36b924946d7", "query": "Command:       getSchedulerCommand(cfg), LivenessProbe: componentProbe(10251, \"/healthz\"), Resources:     componentResources(\"100m\"), <ins> Env:           getProxyEnvVars(), </ins> }), }", "positive_passages": [{"docid": "doc-en-kubernetes-984a2b369276e3156e0990106838472387b6975b0768d694bc54d8f6e19402d4", "text": "Unfortunately on the pod itself for the the environment variables aren't passed through. As this is created using I don't have control over the pod definition. So basically none of the *_proxy variables are set inside the pod in the docker image, however if I and export the variables and try to wget that URL it works. Basically I'm hoping we can update to respect and pass the environment variables down to the system pods if they exist, eg, add: Without it I can't stand up a cluster with AWS integration on a completely private VPC and for such a small change it would make a rather big difference.\nok, so request is actually to pass proxy variables into containers. interesting. I'll check how it can be done. BTW, for noproxy value in your example: things like 10.0.0.0/8 would not work on 99% of software that respects noproxy variable. it must be always exact IP match.\nyou're right that what I'm actually asking for is to pass proxy variables through either from a commandline setting on kubeadm or pick it up from /etc/environment or shell environment that launches kubeadm. I didn't realize it till I dug in to try and think about how one might go about fixing this. At first I thought we would just pick up the variables from the system environment but then I realized kube-controller-manager is deployed in a container and so we'd need to update the yaml file that launches it to contain the environment variables. As I'd like to go to production with this soon hopefully this is a small change that can be .\nThis issue was moved to kubernetes/kubeadm", "commid": "kubernetes_issue_36573", "tokennum": 362}], "negative_passages": []}
{"query_id": "q-en-kubernetes-596fdc8c33d803e087eb5d5c7220aea26a38f8c655b92e1a0897868cf1ddab00", "query": "}, } <ins> // deep copy before reconciler runs to avoid data race. pvWithSize := pv.DeepCopy() </ins> volumePluginMgr, fakePlugin := volumetesting.GetTestKubeletVolumePluginMgr(t) dsw := cache.NewDesiredStateOfWorld(volumePluginMgr) asw := cache.NewActualStateOfWorld(nodeName, volumePluginMgr)", "positive_passages": [{"docid": "doc-en-kubernetes-d047193f0eb4348dad25266c8f06cc7d0100df3011e6281006c74e70d78d442e", "text": "<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI --pull-kubernetes-unit : (PR with no go code changes, should not have failed any unit tests) links to appreciated links to specific failures in spyglass appreciated <!-- Please see the deflaking doc () for more guidance! --/sig storage\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assigne\n/assign\n/assign tried to fix it in", "commid": "kubernetes_issue_99815", "tokennum": 196}], "negative_passages": []}
{"query_id": "q-en-kubernetes-59b1bf3a0d6c069a47f96cc6cf4b9f97c858aa72c6cbf51f80bd73fdd2a5d598", "query": "local -r known_tokens_csv=\"${auth_dir}/known_tokens.csv\" if [[ ! -e \"${known_tokens_csv}\" ]]; then echo \"${KUBE_BEARER_TOKEN},admin,admin\" > \"${known_tokens_csv}\" <del> echo \"${KUBELET_TOKEN},kubelet,kubelet\" >> \"${known_tokens_csv}\" echo \"${KUBE_PROXY_TOKEN},kube_proxy,kube_proxy\" >> \"${known_tokens_csv}\" </del> <ins> echo \"${KUBE_CONTROLLER_MANAGER_TOKEN},system:kube-controller-manager,uid:system:kube-controller-manager\" >> \"${known_tokens_csv}\" echo \"${KUBELET_TOKEN},system:node:node-name,uid:kubelet,system:nodes\" >> \"${known_tokens_csv}\" echo \"${KUBE_PROXY_TOKEN},system:kube-proxy,uid:kube_proxy\" >> \"${known_tokens_csv}\" </ins> fi local use_cloud_config=\"false\" cat <<EOF >/etc/gce.conf", "positive_passages": [{"docid": "doc-en-kubernetes-19a61d82ec14336213ef377c4e39e11807c2ce9673880ce3d82a192d5a783624", "text": "Typically, the dns and dashboard is in crash loop. Ref cc\nif you check the file, does it contain lines like ?\nPrevious comment is ref: from I'll copy that to container-linux as well.", "commid": "kubernetes_issue_39395", "tokennum": 44}], "negative_passages": []}
{"query_id": "q-en-kubernetes-59bb03d4f6a01deae2b4f74d4d9a51bddb8918587b02c0fc33f9f92b181b6a41", "query": "func (c *FakePods) Evict(eviction *policy.Eviction) error { action := core.CreateActionImpl{} action.Verb = \"create\" <ins> action.Namespace = c.ns </ins> action.Resource = podsResource action.Subresource = \"eviction\" action.Object = eviction", "positive_passages": [{"docid": "doc-en-kubernetes-82d56ce8e3638d906303613bbb222b7918f374f3f5d17197cc57429b2467d07d", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: I'm trying to test Eviction functionality in my program, but running into some inconsistencies around how Evictions are handled in the fake SimpleClient in the client-go testing functionality. Most notably, creates a different from , and both are missing information. issues a with set to (seems to be the only Fake that has this mismatch) on the subresource of . It is missing all the extra information in the eviction, i.e. the . issues a on the subresource of the resource. This is wrong, because aren't created, they're only posted and handled immediately. The Action is missing a Namespace. What you expected to happen: I want to be able to add my own reactor to the SimpleClient to handle this special case. I propose we change both cases to a with set to the . This will ensure it's not handled by the current SimpleClient ObjectReaction, and makes it so users can implement whatever they want themselves. I'd be happy to make a PR with these changes. How to reproduce it (as minimally and precisely as possible): Output: Environment: git revision of : <!-- DO NOT EDIT BELOW THIS LINE --/kind bug\nPOST requests are create requests. It doesn't matter if the object is persisted or not.\n/sig api-machinery\ncc", "commid": "kubernetes_issue_71598", "tokennum": 330}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5a55ac028837b8a6c82be0aa52ef2a6fc4914dfcba452b22f2abe8f3f97a0b27", "query": "fs.BoolVar(&s.EnableLogsHandler, \"enable-logs-handler\", s.EnableLogsHandler, \"If true, install a /logs handler for the apiserver logs.\") <ins> fs.MarkDeprecated(\"enable-logs-handler\", \"This flag will be removed in v1.19\") </ins> // Deprecated in release 1.9 fs.StringVar(&s.SSHUser, \"ssh-user\", s.SSHUser,", "positive_passages": [{"docid": "doc-en-kubernetes-b8a87f76b1813a17eca6bab9ea27ea64d02dfa7ec03a7ba6217cccf0eba27cf6", "text": "What would you like to be : Deprecate the flag which enables exposing logs of apiserver. Why is this needed: As per , in order to disable accessing apiserver logs in the future, we need to deprecate the current default and wait for the requisite time period.\n/sig api-machinery\n/assign\nI'm in favor of deprecating this. It's potentially disruptive, I think an email blast to kubernetes-dev would be a good idea.\nThanks , I have posted in kubernetes-dev mailing list.\nI'm also in favor of removing this functionality from the apiserver. Since this is GA behavior, the deprecation period would be 12 months.\ncc", "commid": "kubernetes_issue_77515", "tokennum": 155}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5a6f0954ec3a23b41a230a0bc98baf84cdd3503f3d0cc97a6b817c0da545c6f8", "query": "<ins> #!/bin/bash # Copyright 2017 The Kubernetes Authors. # # Licensed under the Apache License, Version 2.0 (the \"License\"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # #     http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an \"AS IS\" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. # Sets up FlexVolume drivers on GCE COS instances using mounting utilities packaged in a Google # Container Registry image. # The user-provided FlexVolume driver(s) must be under /flexvolume of the image filesystem. # For example, the driver k8s/nfs must be located at /flexvolume/k8s~nfs/nfs . # # This script should be used on a clean instance, with no FlexVolume installed. # Should not be run on instances with an existing full or partial installation. # Upon failure, the script will clean up the partial installation automatically. # # Must be executed under /home/kubernetes/bin with sudo. # Warning: kubelet will be restarted upon successful execution. set -o errexit set -o nounset set -o pipefail MOUNTER_IMAGE=${1:-} MOUNTER_PATH=/home/kubernetes/flexvolume_mounter VOLUME_PLUGIN_DIR=/etc/srv/kubernetes/kubelet-plugins/volume/exec usage() { echo \"usage: $0 imagename[:tag]\" echo \"    imagename  Name of a Container Registry image. By default the latest image is used.\" echo \"    :tag       Container Registry image tag.\" exit 1 } if [ -z ${MOUNTER_IMAGE} ]; then echo \"ERROR: No Container Registry mounter image is specified.\" echo usage fi # Unmounts a mount point lazily. If a mount point does not exist, continue silently, # and without error. umount_silent() { umount -l $1 &> /dev/null || /bin/true } # Waits for kubelet to restart for 1 minute. kubelet_wait() { timeout=60 kubelet_readonly_port=10255 until [[ $timeout -eq 0 ]]; do printf \".\" if [[ $( curl -s http://localhost:${kubelet_readonly_port}/healthz ) == \"ok\" ]]; then return 0 fi sleep 1 timeout=$(( timeout-1 )) done # Timed out waiting for kubelet to become healthy. return 1 } flex_clean() { echo echo \"An error has occurred. Cleaning up...\" echo umount_silent ${VOLUME_PLUGIN_DIR} rm -rf ${VOLUME_PLUGIN_DIR} umount_silent ${MOUNTER_PATH}/var/lib/kubelet umount_silent ${MOUNTER_PATH} rm -rf ${MOUNTER_PATH} if [ -n ${IMAGE_URL:-} ]; then docker rmi -f ${IMAGE_URL} &> /dev/null || /bin/true fi if [ -n ${MOUNTER_DEFAULT_NAME:-} ]; then docker rm -f ${MOUNTER_DEFAULT_NAME} &> /dev/null || /bin/true fi } trap flex_clean ERR # Generates a bash script that wraps all calls to the actual driver inside mount utilities # in the chroot environment. Kubelet sees this script as the FlexVolume driver. generate_chroot_wrapper() { if [ ! -d ${MOUNTER_PATH}/flexvolume ]; then echo \"Failed to set up FlexVolume driver: cannot find directory '/flexvolume' in the mount utility image.\" exit 1 fi for driver_dir in ${MOUNTER_PATH}/flexvolume/*; do if [ -d \"$driver_dir\" ]; then filecount=$(ls -1 $driver_dir | wc -l) if [ $filecount -gt 1 ]; then echo \"ERROR: Expected 1 file in the FlexVolume directory but found $filecount.\" exit 1 fi driver_file=$( ls $driver_dir | head -n 1 ) # driver_path points to the actual driver inside the mount utility image, # relative to image root. # wrapper_path is the wrapper script location, which is known to kubelet. driver_path=flexvolume/$( basename $driver_dir )/${driver_file} wrapper_dir=${VOLUME_PLUGIN_DIR}/$( basename $driver_dir ) wrapper_path=${wrapper_dir}/${driver_file} mkdir -p $wrapper_dir cat >$wrapper_path <<EOF #!/bin/bash chroot ${MOUNTER_PATH} ${driver_path} \"$@\" EOF chmod 755 $wrapper_path echo \"FlexVolume driver installed at ${wrapper_path}\" fi done } echo echo \"Importing mount utility image from Container Registry...\" echo METADATA=http://metadata.google.internal/computeMetadata/v1 SVC_ACCT_ENDPOINT=$METADATA/instance/service-accounts/default ACCESS_TOKEN=$(curl -s -H 'Metadata-Flavor: Google' $SVC_ACCT_ENDPOINT/token | cut -d'\"' -f 4) PROJECT_ID=$(curl -s -H 'Metadata-Flavor: Google' $METADATA/project/project-id) IMAGE_URL=gcr.io/${PROJECT_ID}/${MOUNTER_IMAGE} MOUNTER_DEFAULT_NAME=flexvolume_mounter sudo -u ${SUDO_USER} docker login -u _token -p $ACCESS_TOKEN https://gcr.io > /dev/null sudo -u ${SUDO_USER} docker run --name=${MOUNTER_DEFAULT_NAME} ${IMAGE_URL} docker export ${MOUNTER_DEFAULT_NAME} > /tmp/${MOUNTER_DEFAULT_NAME}.tar docker rm ${MOUNTER_DEFAULT_NAME} > /dev/null docker rmi ${IMAGE_URL} > /dev/null echo echo \"Loading mount utilities onto this instance...\" echo mkdir ${MOUNTER_PATH} tar xf /tmp/${MOUNTER_DEFAULT_NAME}.tar -C ${MOUNTER_PATH} # Bind the kubelet directory to one under flexvolume_mounter mkdir ${MOUNTER_PATH}/var/lib/kubelet mount --rbind /var/lib/kubelet/ ${MOUNTER_PATH}/var/lib/kubelet mount --make-rshared ${MOUNTER_PATH}/var/lib/kubelet # Remount the flexvolume_mounter environment with /dev enabled. mount --bind ${MOUNTER_PATH} ${MOUNTER_PATH} mount -o remount,dev,exec ${MOUNTER_PATH} echo echo \"Setting up FlexVolume driver...\" echo mkdir -p ${VOLUME_PLUGIN_DIR} mount --bind ${VOLUME_PLUGIN_DIR} ${VOLUME_PLUGIN_DIR} mount -o remount,exec ${VOLUME_PLUGIN_DIR} generate_chroot_wrapper echo echo \"Restarting Kubelet...\" echo systemctl restart kubelet.service kubelet_wait if [ $? -eq 0 ]; then echo echo \"FlexVolume is ready.\" else echo \"ERROR: Timed out after 1 minute waiting for kubelet restart.\" fi </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-a8f749d2105324b41eb33d6f0298d70067479a2b892424afb06eaf9d08e1bf7a", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Today there are many obstacles preventing users from setting up FlexVolume on a GCE COS image easily. The default FlexVolume driver directory is not writable. Custom mount utilities can't be installed. Solutions exist for these problems but they are time-consuming to execute manually. On top of these, there are also the common FlexVolume pain points such as manual driver and mount utilities installation, and manually restarting kubelet. Ideally all these tasks should be automated, making it a quick and simple experience to have custom out-of-tree volume plugins. Is this a BUG REPORT or FEATURE REQUEST?: FEATURE REQUEST /kind feature\nThere are no sig labels on this issue. Please by:<br(1) mentioning a sig: <bre.g., for API Machinery<br(2) specifying the label manually: <bre.g., for sig/scalability<br<brNote: method (1) will trigger a notification to the team. You can find the team list and label list\n/sig storage\n/assign", "commid": "kubernetes_issue_48626", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5a7cad29c29061012c0d7f2631146efa44d2dd44667791cfc6d878daab8d2c13", "query": "ContainerID: emptyContainerID, }}, }, <del> map[string]api.ContainerState{ </del> <ins> expectedLastTerminationState: map[string]api.ContainerState{ </ins> \"without-reason\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    3, ContainerID: emptyContainerID,", "positive_passages": [{"docid": "doc-en-kubernetes-b4459e221a04f6723f7b97c6a9d43d61c0d65417b08d143223c7057699636055", "text": "is this a Node bug? cc as next oncall to follow up on this.\nThis is a node bug due to init containers\nI may need help debugging - I see:\nSo I think the problem is in the error case - we're not properly recording that the start failed, and the next time we come in we somehow think the first container succeeded. I'll add some debugging to see if we can't recreate it.\nLet's discuss on instead.", "commid": "kubernetes_issue_25879", "tokennum": 102}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5a7cad29c29061012c0d7f2631146efa44d2dd44667791cfc6d878daab8d2c13", "query": "ContainerID: emptyContainerID, }}, }, <del> map[string]api.ContainerState{ </del> <ins> expectedLastTerminationState: map[string]api.ContainerState{ </ins> \"without-reason\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    3, ContainerID: emptyContainerID,", "positive_passages": [{"docid": "doc-en-kubernetes-dcc88d1d89328d1da3366de828afcd8ab0373228cc4437ea655e2cda79030f86", "text": "Kubelet issues a docker inspect call after creating a container, but for very short lived containers there is a window in which they could exit before being inspected in the docker manager. If the container PID is 0, we should check the ExitCode and other relevant fields and handle them appropriately. [1] This is the suspected cause of several flakes: /cc\nlooking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: I'd expect the second one to not have run in this case? Node logs:\nInit containers have an implicit assumption that container statuses include results of previous SyncPod invocations. If that's not the case we may need to fix that (or at least mitigate it). On May 18, 2016, at 8:28 PM, Prashanth B wrote: looking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: May 18 15:58:33.380: INFO: pod-init--1d4b-11e6-80a4- started at 2016-05-18T15:58:04-07:00 (2+1 container statuses recorded) May 18 15:58:33.380: INFO: Init container init1 ready: false, restart count 0 May 18 15:58:33.380: INFO: Init container init2 ready: true, restart count 0 I'd expect the second one to not have run in this case? Node logs: \u2014 You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub\nThis should be true. Is there any evidence that suggests the opposite? only shows conflicting view of whether init1 has run.\nIf the container exits already and it's not an infra container, kubelet should not error out. Although even if it does, I failed to see how this could affect the readiness of the init container without checking the code further.", "commid": "kubernetes_issue_25844", "tokennum": 487}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5a7cad29c29061012c0d7f2631146efa44d2dd44667791cfc6d878daab8d2c13", "query": "ContainerID: emptyContainerID, }}, }, <del> map[string]api.ContainerState{ </del> <ins> expectedLastTerminationState: map[string]api.ContainerState{ </ins> \"without-reason\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    3, ContainerID: emptyContainerID,", "positive_passages": [{"docid": "doc-en-kubernetes-ade5deee53831749acf4a20dbe39f9ef1836656ae43e40b0bb8594efa4e81e92", "text": "Each syncPod invocation, we inspect the list of init container in order looking for lastTerminationState. There could be a bug in that logic, or if we didn't get the full status, we might make a bad decision. When determining which container to run next, we always look for the last init container in the chain that has success, then run the next container (unless the pod is RestartNever). , Yu-Ju Hong wrote:\nSaw this flake again. How do we verify that container status is not lost between syn pods?\n... between calls to syncPods\nThe second sync clearly saw the init1 container, and decided to launch init2. See \"InitContainersToKeep\" in the message below.\ncontainers to keep can include failed containers. , Yu-Ju Hong wrote:\nDiscussed on slack. In summary, the problem has to do with how we convert the kubecontainer.PodStatus to the api.PodStatus. If a container is terminated, the function makes the decisions: the pod restart policy is \"Always\", and there is a \"failure reason\" recorded for the given container, this means the pod worker tried to (re)start the container but failed. Set the state to \"Waiting\" and populate the reason. , the container state is simply \"terminated\". Init containers don't obey the restart policy like regular containers, and the logic will need to be amended to work with them. is working on a PR. In addition to that, kubelet should not error out if a user container exited before it could apply the oom score (which is best effort in this case). fixes that.\nAhh, thanks for digging into the issue. This is the exact the concern I had when I reviewed the initial implementation of init container, which blocks pr for a while. I even asked to help me verify this case, unfortunately we didn't reproduce the issue back then. :-(\nI wish I'd seen the flakes in the runs prior to merge.\nWe didn't notice this until we started running the tests against docker v1.11.1, which is much faster and hit the race condition differently.\nI suppose that's a good thing...\nIt is hard to reproduce this.", "commid": "kubernetes_issue_25844", "tokennum": 482}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5a7cad29c29061012c0d7f2631146efa44d2dd44667791cfc6d878daab8d2c13", "query": "ContainerID: emptyContainerID, }}, }, <del> map[string]api.ContainerState{ </del> <ins> expectedLastTerminationState: map[string]api.ContainerState{ </ins> \"without-reason\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    3, ContainerID: emptyContainerID,", "positive_passages": [{"docid": "doc-en-kubernetes-0814a4e75b48cf2d27d20141c180e04fbc9b55d5398cce31b037f460c93acb1b", "text": "The extra check of last terminated container in your initial code makes me nervous, but we couldn't reproduce it due to that small race windows until we have a faster docker running on the node. :-)\nI got \"Pods should invoke init containers on a RestartAlways pod\" flake (referenced from ): Logs:\nAll the fixes went in. Please reopen this issue if you see any more flakes.", "commid": "kubernetes_issue_25844", "tokennum": 90}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5a98336356865d685225d054320d98db2ff665115a9af42d932d3fa759deb44d", "query": "return err } <del> err = os.Chmod(f.Name(), 0755) </del> <ins> err = os.Chmod(f.Name(), 0660) </ins> if err != nil { return err }", "positive_passages": [{"docid": "doc-en-kubernetes-30e07950978ed617c12104c8342559dfe477718ba7eb61f98c21f95bb37c1439", "text": "In kubectl v1.8.0+, schema info is cached in the location specified by (defaulting to ), written with world-writeable permissions (rw-rw-rw-). If is specified and pointed at a different location accessible to other users/groups, the written files may be modified by other users/groups and disrupt the kubectl invocation. CVSS score: CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N (3.3, low) What versions are affected? kubectl v1.8.0+ What configurations are affected? Invocations that point at world-writeable locations Impact Malformed responses written to the cache directory can disrupt the kubectl invocation Workaround Use the default location in the $HOME directory or point it at a directory that is only accessible to desired users/groups. (original description follows) ==== What happened: The files inside of \".kube/http-cache\" are world writeable (rw-rw-rw-). While the default for these files appears to be the home directory, using the \"--cache-dir\" flag could put these files into a place where world writeable files would allow any user / process to modify the cache files. Modification of the cache files could influence the kubectl utility in a negative way for other users. What you expected to happen: Apply stricter file permissions to the http-cache files. How to reproduce it (as minimally and precisely as possible): Run any generic kubectl command which is successful and then list the cache directory $ kubectl get pods --all-namespaces $ ls -la Anything else we need to know?", "commid": "kubernetes_issue_76676", "tokennum": 398}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5a98336356865d685225d054320d98db2ff665115a9af42d932d3fa759deb44d", "query": "return err } <del> err = os.Chmod(f.Name(), 0755) </del> <ins> err = os.Chmod(f.Name(), 0660) </ins> if err != nil { return err }", "positive_passages": [{"docid": "doc-en-kubernetes-03c8940a04bf023e0d3632a105949b7e85efda694ffafea56ecb99998a766122", "text": ": I estimate this is a low severity security issue with a CVSS score of \"3.3 / CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N\" - Environment: Linux Kubernetes version (use kubectl version):Client Version: version.Info{Major:\"1\", Minor:\"12\", GitVersion:\"v1.12.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2019-02-26T12:49:28Z\", GoVersion:\"go1.10.8\", Compiler:\"gc\", Platform:\"linux/amd64\"} Server Version: version.Info{Major:\"1\", Minor:\"12\", GitVersion:\"v1.12.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2019-02-26T12:49:28Z\", GoVersion:\"go1.10.8\", Compiler:\"gc\", Platform:\"linux/amd64\"} Cloud provider or hardware configuration: AWS. Running kube api server in hyperkube. OS (e.g: cat /etc/os-release): NAME=\"CentOS Linux\" VERSION=\"7.1808 (Core)\" ID=\"centos\" IDLIKE=\"rhel fedora\" VERSIONID=\"7\" PRETTYNAME=\"CentOS Linux 7.1808 (Core)\" ANSICOLOR=\"0;31\" CPENAME=\"cpe:/o:centos:centos:7\" HOMEURL=\"\" BUGREPORTURL=\"\" CENTOSMANTISBTPROJECT=\"CentOS-7\" CENTOSMANTISBTPROJECTVERSION=\"7\" REDHATSUPPORTPRODUCT=\"centos\" REDHATSUPPORTPRODUCTVERSION=\"7\" OSTREEVERSION=7.1808 Kernel (e.g. uname -a): Linux hackit.internal 3.10.0-862.11.6.el7.x8664 SMP Tue Aug 14 21:49:04 UTC 2018 x8664 x8664 x86_64 GNU/Linux Install tools: Manual installation. Others: n/a\n/sig product-security\nClosing this issue. <detailsIn response to : if you think this is serious, send an email thanks!", "commid": "kubernetes_issue_76676", "tokennum": 565}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5a98336356865d685225d054320d98db2ff665115a9af42d932d3fa759deb44d", "query": "return err } <del> err = os.Chmod(f.Name(), 0755) </del> <ins> err = os.Chmod(f.Name(), 0660) </ins> if err != nil { return err }", "positive_passages": [{"docid": "doc-en-kubernetes-5f4971cee99e57062ae7961121de35cc677214a3e6ca77682b093e74b00a9b30", "text": "</details\nAdjusted the CVSS score to to indicate user interaction is required (since they must specify a non-default cache option pointed at a shared writeable location)\nThere are two places this should be done: PathPerm and FilePerm should be set here: the temp file and final file should have stricter permissions (probably 0660) here:\n/cc\n/help\nThis request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\n/assign I would like to work on release-1.9, as I just made a hot fix for our team's k8s version of 1.9.\nGitHub didn't allow me to assign the following users: yuchengwu. Note that only and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign I would like to work on release-1.9, as I just made a hot fix for our team's k8s version of 1.9. 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\nhelp fixing this is welcome, though it would only be fixed in releases 1.12+, per\n/label official-cve-feed (Related to kubernetes/sig-security)", "commid": "kubernetes_issue_76676", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5af2eb6482ac9f5316b474aa67217de05af91000c35e632289f0c5a5c66afd5e", "query": "return \"default\", false, nil } <del> func (inClusterClientConfig) ConfigAccess() ConfigAccess { </del> <ins> func (config *inClusterClientConfig) ConfigAccess() ConfigAccess { </ins> return NewDefaultClientConfigLoadingRules() } // Possible returns true if loading an inside-kubernetes-cluster is possible. <del> func (inClusterClientConfig) Possible() bool { </del> <ins> func (config *inClusterClientConfig) Possible() bool { </ins> fi, err := os.Stat(\"/var/run/secrets/kubernetes.io/serviceaccount/token\") return os.Getenv(\"KUBERNETES_SERVICE_HOST\") != \"\" && os.Getenv(\"KUBERNETES_SERVICE_PORT\") != \"\" &&", "positive_passages": [{"docid": "doc-en-kubernetes-4e19a56e8ccacbab4546f622baecdb0b8ef30250430c55f8bcdc4de99b100cd2", "text": "Found in openshift, but I'm pretty sure the codepaths are the same. That means the token is getting ignored and in-cluster config is being used in preference to flags.\nIs a similar issue?\nYep, kind of regression.\nSigh.\nYes, most likely the same cause.\nI'm on it.\nUnit test :)\nProbably will want to cherrypick this into 1.5.\nWIP in", "commid": "kubernetes_issue_38834", "tokennum": 89}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5b230dadce25356ea8bd61eb3160fe9d95755f5b0f3a13d18b2c151680b5a605", "query": "\"github.com/GoogleCloudPlatform/kubernetes/pkg/admission\" \"github.com/GoogleCloudPlatform/kubernetes/pkg/api\" <ins> \"github.com/GoogleCloudPlatform/kubernetes/pkg/api/errors\" </ins> \"github.com/GoogleCloudPlatform/kubernetes/pkg/api/latest\" \"github.com/GoogleCloudPlatform/kubernetes/pkg/api/meta\" \"github.com/GoogleCloudPlatform/kubernetes/pkg/client\"", "positive_passages": [{"docid": "doc-en-kubernetes-c343f6e7b091e9b4529e6227acb6329e7535006eb05bcc59008c8d5d37213826", "text": "While running one of my soak tests I noticed the error message: I don't see why I should get this error message. Why should it matter if the namespace already exists? It was created as part of the service creation call just beforehand. And the second attempt to create this pod in exactly the same namespace works. Is this a bug?\nRunning a second time did not produce this error.\nI agree it should not matter. The error is produced there, and I suspect there were multiple concurrent calls being made that try to create a resource in a namespace that had not yet existed. We need to update the code in question to swallow the error if the namespace already exists.\nFYI - longer term, I would like to eliminate the use of autoprovision of namespace and require you to first create a namespace manually. what is there now is more to preserve existing behavior prior to namespace as object was introduced.", "commid": "kubernetes_issue_5873", "tokennum": 190}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5b2ee3a7ed06fd2c63875d0d8038c7d5ddc1ee03958bc5268a2073fea1b993e1", "query": "function upload-resources() { swift post kubernetes --read-acl '.r:*,.rlistings' <del> echo \"[INFO] Upload ${KUBERNETES_RELEASE_TAR}\" swift upload kubernetes ${ROOT}/../../_output/release-tars/${KUBERNETES_RELEASE_TAR}  </del> <ins> locations=( \"${ROOT}/../../_output/release-tars/${KUBERNETES_RELEASE_TAR}\" \"${ROOT}/../../server/${KUBERNETES_RELEASE_TAR}\" ) RELEASE_TAR_LOCATION=$( (ls -t \"${locations[@]}\" 2>/dev/null || true) | head -1 ) RELEASE_TAR_PATH=$(dirname ${RELEASE_TAR_LOCATION}) echo \"[INFO] Uploading ${KUBERNETES_RELEASE_TAR}\" swift upload kubernetes ${RELEASE_TAR_PATH}/${KUBERNETES_RELEASE_TAR}  </ins> --object-name kubernetes-server.tar.gz <del> echo \"[INFO] Upload kubernetes-salt.tar.gz\" swift upload kubernetes ${ROOT}/../../_output/release-tars/kubernetes-salt.tar.gz  </del> <ins> echo \"[INFO] Uploading kubernetes-salt.tar.gz\" swift upload kubernetes ${RELEASE_TAR_PATH}/kubernetes-salt.tar.gz  </ins> --object-name kubernetes-salt.tar.gz }", "positive_passages": [{"docid": "doc-en-kubernetes-5b657ca63c8d65ac5d765363aee55755b3df3fe0d7e8c3dbff40d3d4f941f728", "text": "The path to the server tarball resolves to: is hardcoded, and does not exist in release builds (v1.3.0-beta.2) The file in question is located at: Correcting the path is a workaround for release builds\ncc\nHey, sorry about that. I think I got a fix, but I need your help to test it. I'm traveling and my cellular upload speeds are not so great. Please take a look at this and let me know if it solves the issue:", "commid": "kubernetes_issue_28205", "tokennum": 109}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5b62c370643fbb7d85fe854a168b233644641a60293d5b0c78b261b7d5945682", "query": "Import-Module -Force C:$Filename } <ins> # Returns true if the ENABLE_STACKDRIVER_WINDOWS or ENABLE_NODE_LOGGING field in kube_env is true. # $KubeEnv is a hash table containing the kube-env metadata keys+values. # ENABLE_NODE_LOGGING is used for legacy Stackdriver Logging, and will be deprecated (always set to False) # soon. ENABLE_STACKDRIVER_WINDOWS is added to indicate whether logging is enabled for windows nodes. function IsLoggingEnabled { param ( [parameter(Mandatory=$true)] [hashtable]$KubeEnv ) if ($KubeEnv.Contains('ENABLE_STACKDRIVER_WINDOWS') -and ` ($KubeEnv['ENABLE_STACKDRIVER_WINDOWS'] -eq 'true')) { return $true } elseif ($KubeEnv.Contains('ENABLE_NODE_LOGGING') -and ` ($KubeEnv['ENABLE_NODE_LOGGING'] -eq 'true')) { return $true } return $false } </ins> try { # Don't use FetchAndImport-ModuleFromMetadata for common.psm1 - the common # module includes variables and functions that any other function may depend", "positive_passages": [{"docid": "doc-en-kubernetes-c5ab0587303441aa15d1f99cf54443dd34979e6a47a9667d6d352ed63897253b", "text": "What happened: The stackdriver logging agent is installed and start running no matter logging is enabled/disabled in the cluster or not. What you expected to happen: Do not install and start the logging agent if logging is disabled.\n/sig windows\ncc", "commid": "kubernetes_issue_81299", "tokennum": 51}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5b8f8f669adfde5a772faf3515394437e03347272d7a7752fb4008208d3bb52f", "query": "\"-A\", string(kubeServicesChain), \"-m\", \"comment\", \"--comment\", proxier.ipsetList[kubeClusterIPSet].getComment(), \"-m\", \"set\", \"--match-set\", kubeClusterIPSet, <del> \"dst,dst\", </del> ) if proxier.masqueradeAll { <del> writeLine(proxier.natRules, append(args, \"-j\", string(KubeMarkMasqChain))...) </del> <ins> writeLine(proxier.natRules, append(args, \"dst,dst\", \"-j\", string(KubeMarkMasqChain))...) </ins> } else if len(proxier.clusterCIDR) > 0 { // This masquerades off-cluster traffic to a service VIP.  The idea // is that you can establish a static route for your Service range, // routing to any node, and that node will bridge into the Service // for you.  Since that might bounce off-node, we masquerade here. // If/when we support \"Local\" policy for VIPs, we should update this. <del> writeLine(proxier.natRules, append(args, \"! -s\", proxier.clusterCIDR, \"-j\", string(KubeMarkMasqChain))...) </del> <ins> writeLine(proxier.natRules, append(args, \"dst,dst\", \"! -s\", proxier.clusterCIDR, \"-j\", string(KubeMarkMasqChain))...) } else { // Masquerade all OUTPUT traffic coming from a service ip. // The kube dummy interface has all service VIPs assigned which // results in the service VIP being picked as the source IP to reach // a VIP. This leads to a connection from VIP:<random port> to // VIP:<service port>. // Always masquerading OUTPUT (node-originating) traffic with a VIP // source ip and service port destination fixes the outgoing connections. writeLine(proxier.natRules, append(args, \"src,dst\", \"-j\", string(KubeMarkMasqChain))...) </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-848285cc888dabd416033408eedbcc3ccb37536969c7e28abf4d6f0620c17a3f", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: When using IPVS and not natting (no cluster-cidr specified) requests from the host to service IPs are send with the service ip as the source ip. Let be the kubernetes API IP. Kubeproxy will set up with . This means that traffic from the host (which sees the ) will originate from (best matching ip/network). What you expected to happen: The source ip should be natted to the host ip. How to reproduce it (as minimally and precisely as possible): a ipvs based cluster any cluster-cidr from kube-proxy traffic to a service ip (e.g. http to the kubernetes api server) from the node / host network pod the outgoing interface looking for the service ip () Anything else we need to know?: Environment: Kubernetes version (use ):Cloud provider or hardware configuration: baremetal OS (e.g. from /etc/os-release): Kernel (e.g. ): (based on the Ubuntu 18.04 kernel) Install tools: custom repackaging of kubernetes release tarballs Others: /sig network\nWe have a similar issue in kube-router FWIW resolution is included in the issue\nAh nice, I reproduced the source IP selection on my local Ubuntu 18.04 without any kubernetes installed (use ip link add / ip addr add and then ping the new dummy IP / tcpdump lo). Might be related to the kernel version (4.15) as you couldn't reproduce it.... Changing the routing table would avoid an extra NAT rule. That sounds interesting but not doable without changing the kubernetes sources Murali Reddy < am Fr., 27. Apr. 2018, 14:06:\nlet me try with to reproduce. but its no brainer, this issue must be fixed.\ngetting closer... -CLUSTER-IP is only populated if masquerade-all or cluster-cidr is used: is no OUTPUT masquerading for service IPs if cluster-cidr is not specified (no branch matches): With cluster-cidr enabled I've saved the ipset.... I've disabled cluster-cidr and rebooted (to reset all iptables/ipset/...).", "commid": "kubernetes_issue_63241", "tokennum": 514}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5b8f8f669adfde5a772faf3515394437e03347272d7a7752fb4008208d3bb52f", "query": "\"-A\", string(kubeServicesChain), \"-m\", \"comment\", \"--comment\", proxier.ipsetList[kubeClusterIPSet].getComment(), \"-m\", \"set\", \"--match-set\", kubeClusterIPSet, <del> \"dst,dst\", </del> ) if proxier.masqueradeAll { <del> writeLine(proxier.natRules, append(args, \"-j\", string(KubeMarkMasqChain))...) </del> <ins> writeLine(proxier.natRules, append(args, \"dst,dst\", \"-j\", string(KubeMarkMasqChain))...) </ins> } else if len(proxier.clusterCIDR) > 0 { // This masquerades off-cluster traffic to a service VIP.  The idea // is that you can establish a static route for your Service range, // routing to any node, and that node will bridge into the Service // for you.  Since that might bounce off-node, we masquerade here. // If/when we support \"Local\" policy for VIPs, we should update this. <del> writeLine(proxier.natRules, append(args, \"! -s\", proxier.clusterCIDR, \"-j\", string(KubeMarkMasqChain))...) </del> <ins> writeLine(proxier.natRules, append(args, \"dst,dst\", \"! -s\", proxier.clusterCIDR, \"-j\", string(KubeMarkMasqChain))...) } else { // Masquerade all OUTPUT traffic coming from a service ip. // The kube dummy interface has all service VIPs assigned which // results in the service VIP being picked as the source IP to reach // a VIP. This leads to a connection from VIP:<random port> to // VIP:<service port>. // Always masquerading OUTPUT (node-originating) traffic with a VIP // source ip and service port destination fixes the outgoing connections. writeLine(proxier.natRules, append(args, \"src,dst\", \"-j\", string(KubeMarkMasqChain))...) </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-0a7db03e41de00a95766c0a4c19610d15de5901707836c1c2d0b18155d4ac469", "text": "I think the code should: Always populate Set a masquerade rule for service IPs (src == service IP should not happen on OUTPUT)\nHow to test this with a local cluster.... the node (install , & modprobe the modules , , , ). a new shell: define a service with manual external endpoints tcpdump on the outgoing interface of the node the service ip the tcpdump, it will show outgoing traffic from_ the service IP:\nCan you please take a look at this?\n/assign\nI assume this issue is related to some specific kernel versions? I just neither can't reproduce it nor can't see the failures in our test grid.\nI was aware of there is a PR() in flight, my team will evaluate the effects of that PR. But, please rebase the PR first, thanks!", "commid": "kubernetes_issue_63241", "tokennum": 178}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5b9761a96fcacf7e9a4917d99e33954e86cf1804c717ade4cc24698688b1f716", "query": "VolumeNFSServer     = ImageConfig{e2eRegistry, \"volume/nfs\", \"1.0\"} VolumeISCSIServer   = ImageConfig{e2eRegistry, \"volume/iscsi\", \"1.0\"} VolumeGlusterServer = ImageConfig{e2eRegistry, \"volume/gluster\", \"1.0\"} <del> VolumeRBDServer     = ImageConfig{e2eRegistry, \"volume/rbd\", \"1.0\"} </del> <ins> VolumeRBDServer     = ImageConfig{e2eRegistry, \"volume/rbd\", \"1.0.1\"} </ins> ) func GetE2EImage(image ImageConfig) string {", "positive_passages": [{"docid": "doc-en-kubernetes-086f2ac7dcab9c158ca481b0b58fae22976bc98ae146a7d10d5bef748052b70d", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: e2e tests which use RBD server image fail with What you expected to happen: These tests succeed. How to reproduce it (as minimally and precisely as possible): Run e2e tests which use RBD server image. Anything else we need to know?: /sig storage This issue is introduced by below commit: It change the base image from fedora 26 to fedora 28. In fedora 26, hostname command is installed as a dependency for  However, in fedora 28, it is not installed, as a result, this issue happens due to lack of hostname command. Environment: Kubernetes version (use ): k8s 1.12 alpha\nPlease see the difference of the behaviour between fedora 26 and 28. [Fedora26] [Fedora28]\nCould you help solving this issue? I assume the fix for the code would be as below, but I'm not familiar with the build and push process for the test image. ( in doesn't work.) So, I need your help to make further progress.\n(or) Both need to be run from directory\nThank you for letting me know it. It should be s/all-containers/all-container/, but it seems to work. I will test with above patch and above build commands, then make a PR, once I confirm that it works well.\nsorry typing from memory :)\nI need to ask you two more things: Do we need to increment the version for this image, like 1.0.1, even for this small change? (I guess that and test/images/volume/rbd/VERSION will need to be updated in this case.) How the image push process will be? Does it pushed by CI, if there are a change in the code or docker file, or do someone who have permission will push it manually?\ncreates below three docker images: Is my understanding right that to make each test access to each arch image, needs to be modified like below? (Without doing so, each test seems to keep trying to access to , without arch.)\nFor fedora28 image, just installing hostname doesn't seem to work well. Please see the log below and attached . I guess that this is due to the difference of ceph version, which will be beyond my beyond my expertise.", "commid": "kubernetes_issue_67269", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5b9761a96fcacf7e9a4917d99e33954e86cf1804c717ade4cc24698688b1f716", "query": "VolumeNFSServer     = ImageConfig{e2eRegistry, \"volume/nfs\", \"1.0\"} VolumeISCSIServer   = ImageConfig{e2eRegistry, \"volume/iscsi\", \"1.0\"} VolumeGlusterServer = ImageConfig{e2eRegistry, \"volume/gluster\", \"1.0\"} <del> VolumeRBDServer     = ImageConfig{e2eRegistry, \"volume/rbd\", \"1.0\"} </del> <ins> VolumeRBDServer     = ImageConfig{e2eRegistry, \"volume/rbd\", \"1.0.1\"} </ins> ) func GetE2EImage(image ImageConfig) string {", "positive_passages": [{"docid": "doc-en-kubernetes-77a7b6220df65aff10095b84f9a73f01dc0b39abd15f0db81cc810c0f75ed2d0", "text": "So, could you help debugging this issue? Meanwhile, I will try testing with the image by using fedora26 for workaround.\nI confirmed that below commit, which change the base image back to fedora 26, fix this issue. Please see the log . After I checked the image-, I come to think that by pushing the image, each image will be able to be pulled without -arch, so I guess the last parameter for ImageConfig should be false. (I couldn't test it in my environment.) I will fix the commit as so and make a PR once I confirm it. Also, if it will easy to fix with Fedora 28, I will wait for the actual fix and quit making a PR for the workaround.\nthanks yes, a quick fix is welcome, looking forward\nThank you for your comment. I will continue with the workaround. I saw a commit for deleting multi arch consideration. I rebased the patch to the commit and made a PR. Please review it.", "commid": "kubernetes_issue_67269", "tokennum": 212}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5bad42f0e4c66207f686339c91e9ec8c9f5545bdff22feeeb1e238cda1b8d1ae", "query": "importpath = \"k8s.io/component-base/metrics/testutil\", visibility = [\"//visibility:public\"], deps = [ <ins> \"//staging/src/k8s.io/apimachinery/pkg/version:go_default_library\", </ins> \"//staging/src/k8s.io/component-base/metrics:go_default_library\", \"//vendor/github.com/prometheus/client_golang/prometheus/testutil:go_default_library\", \"//vendor/github.com/prometheus/common/expfmt:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-b57bf0f1b2dd71c1293d1dafb95c6e51debc5c1d26878053edb8d335b76a3a11", "text": "What would you like to be : Once a metric be deprecated, we should update the unit test accordingly if there is any. We need to work out a way for a unit test freely select codebase version, and also should make sure the unit test won't fail in the subsequent release. Why is this needed: Deprecated also needs to be protected. /sig instrumentation /assign", "commid": "kubernetes_issue_86292", "tokennum": 81}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5bccbca72aaf3e561ce7f2b467de03b88267c90c5eb7270f20b51cd617876f69", "query": "// GetInstanceTypeByNodeName gets the instance type by node name. func (ss *scaleSet) GetInstanceTypeByNodeName(name string) (string, error) { <del> _, _, vm, err := ss.getVmssVM(name) </del> <ins> managedByAS, err := ss.isNodeManagedByAvailabilitySet(name) </ins> if err != nil { <del> if err == ErrorNotVmssInstance { glog.V(4).Infof(\"GetInstanceTypeByNodeName: node %q is managed by availability set\", name) // Retry with standard type because nodes are not managed by vmss. return ss.availabilitySet.GetInstanceTypeByNodeName(name) } </del> <ins> glog.Errorf(\"Failed to check isNodeManagedByAvailabilitySet: %v\", err) return \"\", err } if managedByAS { // vm is managed by availability set. return ss.availabilitySet.GetInstanceTypeByNodeName(name) } _, _, vm, err := ss.getVmssVM(name) if err != nil { </ins> return \"\", err }", "positive_passages": [{"docid": "doc-en-kubernetes-98264fae63e9d149f0171dd13218170b598f5e330429a04234e4c80f3d1b23d2", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: VMAS nodes are reporting error in vmss cluster (vmType set to vmss). What you expected to happen: Node should register correctly in the kubernetes cluster. How to reproduce it (as minimally and precisely as possible): Create a VMAS nodes inside vmss cluster. Anything else we need to know?: Environment: Kubernetes version (use ): master Cloud provider or hardware configuration: azure OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/sig azure", "commid": "kubernetes_issue_60185", "tokennum": 165}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5bdb878a76504e2bf239961639672bc380bb42b9bd2322c9afb7439331c98d3f", "query": "# Optional: Enable node logging. ENABLE_NODE_LOGGING=true LOGGING_DESTINATION=elasticsearch # options: elasticsearch, gcp <ins> # Don't require https for registries in our local RFC1918 network EXTRA_DOCKER_OPTS=\"--insecure-registry 10.0.0.0/8\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-142e8decd8d12f564814b0a08026ec0c2500ddcd8040f0182edc6a7f51b222f8", "text": "0/8 is with a company's intranet, so it can be insecure. This is similiar to \"For GCE, allow insecure registries anywhere in 10.0.0.0/8\" Thanks!\nLinking to and .\nThis was", "commid": "kubernetes_issue_2807", "tokennum": 55}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5bf8f1e14fdad38057fcb279ad75399548048f0f20c04c9ffdf161488440829c", "query": "<modelVersion>4.0.0</modelVersion> <groupId>io.k8s.cassandra</groupId> <artifactId>kubernetes-cassandra</artifactId> <del> <version>0.0.4</version> </del> <ins> <version>0.0.5</version> </ins> <build> <sourceDirectory>src</sourceDirectory> <plugins>", "positive_passages": [{"docid": "doc-en-kubernetes-82cb26acad9fc9df916ca73a6711809a93da9752a7947ed537b4183fa019f2e5", "text": "What would you like to be : There is a tab in the k8s perf dashaboard for the scheduler perf benchmarks, but it is showing nothing, we should fix that: http://perf- What this dashboard should be showing is multiple runs per day of We can run it every hour, and summarize the 24 runs of each day to show 50%, 90% and 99% percentile. Why is this needed: Having daily runs of the benchmarks is important to track performance regressions. /sig scheduling /assign /priority important-soon\nRef\n/cc\nThe ci job's config is at And one of failed logs could be found at I tried to reproduce it on my local machine(because I do not have Gloud credentials, I run the task directly in the container): However it works well on my local machine. It is so weird. It will be very appreciated if anyone could help reproduce it with Gloud credentials.\ncan you try and reach out to the test-infra people? ping them on the slack channel perhaps.\nyes, I have tried to get help from , he is busy now. I'll try more.\nWhile working on reproducing this in order to file a bug against test-infra folks I think I found a solution. Will send PRs shortly. /assign\n/retitle sig-scalability-benchmarks#scheduler fails consistently due to build issues\n/sig scalability Testgrid link: https://k8s- Error logs:\nA word about the solution, the job uses the deprecated script which is not supported anymore by test-infra oncall / folks. I've rewritten the job definition to use pod utilities and it started working (will require to get merged first).\nThanks\nThanks !", "commid": "kubernetes_issue_84186", "tokennum": 383}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5c1cc06492bafc26d6777b37484b3d518c341f6ad9a09f3a800dc2adccfbc3b8", "query": "# REVISION provides a version number fo this image and all it's bundled # artifacts. It should start at zero for each LATEST_ETCD_VERSION and increment # for each revision of this image at that etcd version. <del> REVISION?=2 </del> <ins> REVISION?=3 </ins> # IMAGE_TAG Uniquely identifies k8s.gcr.io/etcd docker image with a tag of the form \"<etcd-version>-<revision>\". IMAGE_TAG=$(LATEST_ETCD_VERSION)-$(REVISION)", "positive_passages": [{"docid": "doc-en-kubernetes-ee0826757468ea334f95c77509b257c3d392b6713b4311ba7afa125d642dcec9", "text": "The based container images for are shipped with the wrong architecture within the manifest if not amd64: Refers to We updated the images a few minutes ago to buster-v1.3.0, which are now ready to be used as base for the multi-architecture images. If the images contain the right architectures, then it may magically happen that the kube-proxy images are fixed, too. This is because we already use the build syntax for it: /cc\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig release", "commid": "kubernetes_issue_98229", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5c39dd0c6e3e4481d0cf45069a579211ad9a27c08d66001b7fb5549f3befc160", "query": "import ( \"context\" <ins> \"fmt\" </ins> \"testing\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-dc8aac09a0e4bb26f9dc5f50aef7f845ea9d7c4b925d34b9f6eda044925f80f5", "text": "TestRunOneVolumeDetachFailNodeWithReadWriteOnce 4 times since 03-19 23:00 PDT, intermittently ! https://k8s- Still investigating whether this is a tolerable flake or not with more history than testgrid view, or otherwise would appreciate input from anyone with expertise in this test, especially as regards to whether this should be a blocker for tomorrows beta cut. maybe: /sig storage /sig testing\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nis already open for this, looks like it is attempting to fix it\nthank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. /close\nClosing this issue. <detailsIn response to : thank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. 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", "commid": "kubernetes_issue_116774", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5c39dd0c6e3e4481d0cf45069a579211ad9a27c08d66001b7fb5549f3befc160", "query": "import ( \"context\" <ins> \"fmt\" </ins> \"testing\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-aef7ec00dc93616f97177ca3d23f28217445848b34c429e5746962ea28329f43", "text": "pull-kubernetes-unit TestRunOneVolumeDetachFailNodeWithReadWriteOnce Jan 7th, 2022 Check volume <fake-plugin/volume-nameis reported as attached to node <fail-detach-node, got false, expected true No response_ /sig storage\n/cc\nthis is the top unit test flake according to\ncc\nThe 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]:\nI think this test is no longer flaky by checking the test grid, close it now.\nUnfortunately this does still seem to be flaky: Here was the output from : /reopen\nReopened this issue. <detailsIn response to : Unfortunately this does still seem to be flaky: 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\n/remove-lifecycle stale\nstill the case\nHow about adding some logging to help troubleshoot this? I looked at it a little, but it is hard to tell which part of the test is failing. PR\n/\nThis is still happening\n/triage accepted\nFrom the logs, in the OneVolumeDetachFailNodeWithReadWriteOnce test, succeeded, but the next verification failed. In verifyVolumeAttachedToNode, the attachState is from calling and within asw, it calls . In verifyVolumeReportedAsAttachedToNode, the volumes are obtained from calling , it seems that the node is not in asw.nodesToUpdateStatusFor at this step. Cannot reproduce locally. I tried to run the test 100 times locally with debug.Stack()... 3 * 100 times all passed.\nTried to run stress test on my linux machine as well but still cannot reproduce. Command: Result: Also tried running n process in parallel. Command: Result:\nIt seems like it happens more frequently.", "commid": "kubernetes_issue_107414", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5c39dd0c6e3e4481d0cf45069a579211ad9a27c08d66001b7fb5549f3befc160", "query": "import ( \"context\" <ins> \"fmt\" </ins> \"testing\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-62e47fd83b7fc1cc39259be1688a9f133b9cd2dc48247eb5d858fae7fd13955b", "text": "But I may have no time to dig into the cause. Let's see.\ncc as the test author.\nThe problem is that this test has a lot of dependency on the sleeps that are hardcoded with a very narrow scope, but our CI seems to be able to stress it much more. As soon as you slightly change one of the sleep duration it starts to flake locally The test can not make an assumption that timing is perfect, even more in the sub second range can someone in sig-storage review this test and make it less dependant on those tight sleeps?\nAccording to most failures, it failed at Line 660. Let me run some stress locally. with 250ms sleep with 100ms sleep\nI agree this test case is too brittle due to its specific timing dependencies. To fix this, I suggest reworking the test case to: 1) Add retry with timeout to wait for final conditions 2) Remove the intermediate timing-based state transition checks. Instead, we can keep track of state transitions in the Fakes and validate those stats. wdyt?\nFriendly ping from 1.27 CI Signal that this test is still a noisy flake on the master-blocking dashboard as CI Signal has flagged it in and", "commid": "kubernetes_issue_107414", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5c3c1e736a833e197d9b4d734a8c5e496908800e11d7c5232f4718222db1c514", "query": "host_platform=$(kube::golang::host_platform) # Use eval to preserve embedded quoted strings. <del> local goflags goldflags gogcflags build_with_coverage </del> <ins> local goflags goldflags gogcflags </ins> eval \"goflags=(${GOFLAGS:-})\" goldflags=\"${GOLDFLAGS:-} $(kube::version::ldflags)\" gogcflags=\"${GOGCFLAGS:-}\" <del> build_with_coverage=\"${KUBE_BUILD_WITH_COVERAGE:-}\" </del> local -a targets=() local arg", "positive_passages": [{"docid": "doc-en-kubernetes-3d30f80339d7c67274e12c6190891fb695bbdad2c822e929f8e060cdf1647787", "text": "/kind cleanup /sig testing /priority important-longterm This is a followup issue to address the \"standard build globals\" nit on At the very least I think we shouldn't capture our custom env var. Also think it'd be worth documenting the assumed variables in a list, similar to\ncc\n/assign", "commid": "kubernetes_issue_68163", "tokennum": 69}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5c804f829db78e7c5bb20271e46925e4950674ababeb6b034ef811561bbbff8c", "query": "} } <ins> // This function is used canary updates and phased rolling updates of template modifications for partiton1 and delete pod-0 func deletingPodForRollingUpdatePartitionTest(ctx context.Context, f *framework.Framework, c clientset.Interface, ns string, ss *appsv1.StatefulSet) { setHTTPProbe(ss) ss.Spec.UpdateStrategy = appsv1.StatefulSetUpdateStrategy{ Type: appsv1.RollingUpdateStatefulSetStrategyType, RollingUpdate: func() *appsv1.RollingUpdateStatefulSetStrategy { return &appsv1.RollingUpdateStatefulSetStrategy{ Partition: pointer.Int32(1), } }(), } ss, err := c.AppsV1().StatefulSets(ns).Create(ctx, ss, metav1.CreateOptions{}) framework.ExpectNoError(err) e2estatefulset.WaitForRunningAndReady(ctx, c, *ss.Spec.Replicas, ss) ss = waitForStatus(ctx, c, ss) currentRevision, updateRevision := ss.Status.CurrentRevision, ss.Status.UpdateRevision gomega.Expect(currentRevision).To(gomega.Equal(updateRevision), fmt.Sprintf(\"StatefulSet %s/%s created with update revision %s not equal to current revision %s\", ss.Namespace, ss.Name, updateRevision, currentRevision)) pods := e2estatefulset.GetPodList(ctx, c, ss) for i := range pods.Items { gomega.Expect(pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel]).To(gomega.Equal(currentRevision), fmt.Sprintf(\"Pod %s/%s revision %s is not equal to currentRevision %s\", pods.Items[i].Namespace, pods.Items[i].Name, pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel], currentRevision)) } ginkgo.By(\"Adding finalizer for pod-0\") pod0name := getStatefulSetPodNameAtIndex(0, ss) pod0, err := c.CoreV1().Pods(ns).Get(ctx, pod0name, metav1.GetOptions{}) framework.ExpectNoError(err) pod0.Finalizers = append(pod0.Finalizers, testFinalizer) pod0, err = c.CoreV1().Pods(ss.Namespace).Update(ctx, pod0, metav1.UpdateOptions{}) framework.ExpectNoError(err) pods.Items[0] = *pod0 defer e2epod.NewPodClient(f).RemoveFinalizer(ctx, pod0.Name, testFinalizer) ginkgo.By(\"Updating image on StatefulSet\") newImage := NewWebserverImage oldImage := ss.Spec.Template.Spec.Containers[0].Image ginkgo.By(fmt.Sprintf(\"Updating stateful set template: update image from %s to %s\", oldImage, newImage)) gomega.Expect(oldImage).ToNot(gomega.Equal(newImage), \"Incorrect test setup: should update to a different image\") ss, err = updateStatefulSetWithRetries(ctx, c, ns, ss.Name, func(update *appsv1.StatefulSet) { update.Spec.Template.Spec.Containers[0].Image = newImage }) framework.ExpectNoError(err) ginkgo.By(\"Creating a new revision\") ss = waitForStatus(ctx, c, ss) currentRevision, updateRevision = ss.Status.CurrentRevision, ss.Status.UpdateRevision gomega.Expect(currentRevision).ToNot(gomega.Equal(updateRevision), \"Current revision should not equal update revision during rolling update\") ginkgo.By(\"Await for all replicas running, all are updated but pod-0\") e2estatefulset.WaitForState(ctx, c, ss, func(set2 *appsv1.StatefulSet, pods2 *v1.PodList) (bool, error) { ss = set2 pods = pods2 if ss.Status.UpdatedReplicas == *ss.Spec.Replicas-1 && ss.Status.Replicas == *ss.Spec.Replicas && ss.Status.ReadyReplicas == *ss.Spec.Replicas { // rolling updated is not completed, because replica 0 isn't ready return true, nil } return false, nil }) ginkgo.By(\"Verify pod images before pod-0 deletion and recreation\") for i := range pods.Items { if i < int(*ss.Spec.UpdateStrategy.RollingUpdate.Partition) { gomega.Expect(pods.Items[i].Spec.Containers[0].Image).To(gomega.Equal(oldImage), fmt.Sprintf(\"Pod %s/%s has image %s not equal to oldimage image %s\", pods.Items[i].Namespace, pods.Items[i].Name, pods.Items[i].Spec.Containers[0].Image, oldImage)) gomega.Expect(pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel]).To(gomega.Equal(currentRevision), fmt.Sprintf(\"Pod %s/%s has revision %s not equal to current revision %s\", pods.Items[i].Namespace, pods.Items[i].Name, pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel], currentRevision)) } else { gomega.Expect(pods.Items[i].Spec.Containers[0].Image).To(gomega.Equal(newImage), fmt.Sprintf(\"Pod %s/%s has image %s not equal to new image  %s\", pods.Items[i].Namespace, pods.Items[i].Name, pods.Items[i].Spec.Containers[0].Image, newImage)) gomega.Expect(pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel]).To(gomega.Equal(updateRevision), fmt.Sprintf(\"Pod %s/%s has revision %s not equal to new revision %s\", pods.Items[i].Namespace, pods.Items[i].Name, pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel], updateRevision)) } } ginkgo.By(\"Deleting the pod-0 so that kubelet terminates it and StatefulSet controller recreates it\") deleteStatefulPodAtIndex(ctx, c, 0, ss) ginkgo.By(\"Await for two replicas to be updated, while the pod-0 is not running\") e2estatefulset.WaitForState(ctx, c, ss, func(set2 *appsv1.StatefulSet, pods2 *v1.PodList) (bool, error) { ss = set2 pods = pods2 return ss.Status.ReadyReplicas == *ss.Spec.Replicas-1, nil }) ginkgo.By(fmt.Sprintf(\"Removing finalizer from pod-0 (%v/%v) to allow recreation\", pod0.Namespace, pod0.Name)) e2epod.NewPodClient(f).RemoveFinalizer(ctx, pod0.Name, testFinalizer) ginkgo.By(\"Await for recreation of pod-0, so that all replicas are running\") e2estatefulset.WaitForState(ctx, c, ss, func(set2 *appsv1.StatefulSet, pods2 *v1.PodList) (bool, error) { ss = set2 pods = pods2 return ss.Status.ReadyReplicas == *ss.Spec.Replicas, nil }) ginkgo.By(\"Verify pod images after pod-0 deletion and recreation\") pods = e2estatefulset.GetPodList(ctx, c, ss) for i := range pods.Items { if i < int(*ss.Spec.UpdateStrategy.RollingUpdate.Partition) { gomega.Expect(pods.Items[i].Spec.Containers[0].Image).To(gomega.Equal(oldImage), fmt.Sprintf(\"Pod %s/%s has image %s not equal to current image %s\", pods.Items[i].Namespace, pods.Items[i].Name, pods.Items[i].Spec.Containers[0].Image, oldImage)) gomega.Expect(pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel]).To(gomega.Equal(currentRevision), fmt.Sprintf(\"Pod %s/%s has revision %s not equal to current revision %s\", pods.Items[i].Namespace, pods.Items[i].Name, pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel], currentRevision)) } else { gomega.Expect(pods.Items[i].Spec.Containers[0].Image).To(gomega.Equal(newImage), fmt.Sprintf(\"Pod %s/%s has image %s not equal to new image  %s\", pods.Items[i].Namespace, pods.Items[i].Name, pods.Items[i].Spec.Containers[0].Image, newImage)) gomega.Expect(pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel]).To(gomega.Equal(updateRevision), fmt.Sprintf(\"Pod %s/%s has revision %s not equal to new revision %s\", pods.Items[i].Namespace, pods.Items[i].Name, pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel], updateRevision)) } } } </ins> // confirmStatefulPodCount asserts that the current number of Pods in ss is count, waiting up to timeout for ss to // scale to count. func confirmStatefulPodCount(ctx context.Context, c clientset.Interface, count int, ss *appsv1.StatefulSet, timeout time.Duration, hard bool) {", "positive_passages": [{"docid": "doc-en-kubernetes-cbff279a5a2209254c6527f41e3183737e33b6607a7e6fb4945b04f53611a022", "text": "My application is clustered and I have 2 pods running. I am using a rolling upgrade strategy and my partitioning number is 1. First I need to upgrade the pod with the ordinal number 1 so I triggered that upgrade with partitioning number 1 and my upgrade gets completed. After this, my pod having the ordinal number 0 gets restarted and it's automatically upgraded to a new image. This is not an expected behavior because still, my partition number is 1 and pod-0 should come up with an older image only. I am facing this issue for the v1.27 cluster. Prior to this, it was working fine. pod-0 should not upgrade to new image until I upgrade the partition number to 0.a Do helm install and upgrade pod-1 only keeping partition number to 1. No response <detailsconsole $ cat /etc/os-release $ uname -a C:wmic os get Caption, Version, BuildNumber, OSArchitecture </details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig/api-machinery\n/sig apps /sig storage\nHi, Can someone suggest here? As this is introduced in my setup after the v1.27 upgrade? Is there any change in partition logic?\nThis can be reproduced by using the said STS. 1 - Deploy STS using attached that has a replica count is 2 and updatingstrategy.rolling.partition as 1. 2 - Do edit STS and update the image to 1.15. This will upgrade, pod-1 with image 1.15. 3 - Next delete the pod pod-0 and check that POD-0 came up with a new image which is not the expected behavior. POD 0 should not be updated to a new image until the partition is changed to 0. We have noticed this behavior change in v1.27.", "commid": "kubernetes_issue_119685", "tokennum": 476}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5c804f829db78e7c5bb20271e46925e4950674ababeb6b034ef811561bbbff8c", "query": "} } <ins> // This function is used canary updates and phased rolling updates of template modifications for partiton1 and delete pod-0 func deletingPodForRollingUpdatePartitionTest(ctx context.Context, f *framework.Framework, c clientset.Interface, ns string, ss *appsv1.StatefulSet) { setHTTPProbe(ss) ss.Spec.UpdateStrategy = appsv1.StatefulSetUpdateStrategy{ Type: appsv1.RollingUpdateStatefulSetStrategyType, RollingUpdate: func() *appsv1.RollingUpdateStatefulSetStrategy { return &appsv1.RollingUpdateStatefulSetStrategy{ Partition: pointer.Int32(1), } }(), } ss, err := c.AppsV1().StatefulSets(ns).Create(ctx, ss, metav1.CreateOptions{}) framework.ExpectNoError(err) e2estatefulset.WaitForRunningAndReady(ctx, c, *ss.Spec.Replicas, ss) ss = waitForStatus(ctx, c, ss) currentRevision, updateRevision := ss.Status.CurrentRevision, ss.Status.UpdateRevision gomega.Expect(currentRevision).To(gomega.Equal(updateRevision), fmt.Sprintf(\"StatefulSet %s/%s created with update revision %s not equal to current revision %s\", ss.Namespace, ss.Name, updateRevision, currentRevision)) pods := e2estatefulset.GetPodList(ctx, c, ss) for i := range pods.Items { gomega.Expect(pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel]).To(gomega.Equal(currentRevision), fmt.Sprintf(\"Pod %s/%s revision %s is not equal to currentRevision %s\", pods.Items[i].Namespace, pods.Items[i].Name, pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel], currentRevision)) } ginkgo.By(\"Adding finalizer for pod-0\") pod0name := getStatefulSetPodNameAtIndex(0, ss) pod0, err := c.CoreV1().Pods(ns).Get(ctx, pod0name, metav1.GetOptions{}) framework.ExpectNoError(err) pod0.Finalizers = append(pod0.Finalizers, testFinalizer) pod0, err = c.CoreV1().Pods(ss.Namespace).Update(ctx, pod0, metav1.UpdateOptions{}) framework.ExpectNoError(err) pods.Items[0] = *pod0 defer e2epod.NewPodClient(f).RemoveFinalizer(ctx, pod0.Name, testFinalizer) ginkgo.By(\"Updating image on StatefulSet\") newImage := NewWebserverImage oldImage := ss.Spec.Template.Spec.Containers[0].Image ginkgo.By(fmt.Sprintf(\"Updating stateful set template: update image from %s to %s\", oldImage, newImage)) gomega.Expect(oldImage).ToNot(gomega.Equal(newImage), \"Incorrect test setup: should update to a different image\") ss, err = updateStatefulSetWithRetries(ctx, c, ns, ss.Name, func(update *appsv1.StatefulSet) { update.Spec.Template.Spec.Containers[0].Image = newImage }) framework.ExpectNoError(err) ginkgo.By(\"Creating a new revision\") ss = waitForStatus(ctx, c, ss) currentRevision, updateRevision = ss.Status.CurrentRevision, ss.Status.UpdateRevision gomega.Expect(currentRevision).ToNot(gomega.Equal(updateRevision), \"Current revision should not equal update revision during rolling update\") ginkgo.By(\"Await for all replicas running, all are updated but pod-0\") e2estatefulset.WaitForState(ctx, c, ss, func(set2 *appsv1.StatefulSet, pods2 *v1.PodList) (bool, error) { ss = set2 pods = pods2 if ss.Status.UpdatedReplicas == *ss.Spec.Replicas-1 && ss.Status.Replicas == *ss.Spec.Replicas && ss.Status.ReadyReplicas == *ss.Spec.Replicas { // rolling updated is not completed, because replica 0 isn't ready return true, nil } return false, nil }) ginkgo.By(\"Verify pod images before pod-0 deletion and recreation\") for i := range pods.Items { if i < int(*ss.Spec.UpdateStrategy.RollingUpdate.Partition) { gomega.Expect(pods.Items[i].Spec.Containers[0].Image).To(gomega.Equal(oldImage), fmt.Sprintf(\"Pod %s/%s has image %s not equal to oldimage image %s\", pods.Items[i].Namespace, pods.Items[i].Name, pods.Items[i].Spec.Containers[0].Image, oldImage)) gomega.Expect(pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel]).To(gomega.Equal(currentRevision), fmt.Sprintf(\"Pod %s/%s has revision %s not equal to current revision %s\", pods.Items[i].Namespace, pods.Items[i].Name, pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel], currentRevision)) } else { gomega.Expect(pods.Items[i].Spec.Containers[0].Image).To(gomega.Equal(newImage), fmt.Sprintf(\"Pod %s/%s has image %s not equal to new image  %s\", pods.Items[i].Namespace, pods.Items[i].Name, pods.Items[i].Spec.Containers[0].Image, newImage)) gomega.Expect(pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel]).To(gomega.Equal(updateRevision), fmt.Sprintf(\"Pod %s/%s has revision %s not equal to new revision %s\", pods.Items[i].Namespace, pods.Items[i].Name, pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel], updateRevision)) } } ginkgo.By(\"Deleting the pod-0 so that kubelet terminates it and StatefulSet controller recreates it\") deleteStatefulPodAtIndex(ctx, c, 0, ss) ginkgo.By(\"Await for two replicas to be updated, while the pod-0 is not running\") e2estatefulset.WaitForState(ctx, c, ss, func(set2 *appsv1.StatefulSet, pods2 *v1.PodList) (bool, error) { ss = set2 pods = pods2 return ss.Status.ReadyReplicas == *ss.Spec.Replicas-1, nil }) ginkgo.By(fmt.Sprintf(\"Removing finalizer from pod-0 (%v/%v) to allow recreation\", pod0.Namespace, pod0.Name)) e2epod.NewPodClient(f).RemoveFinalizer(ctx, pod0.Name, testFinalizer) ginkgo.By(\"Await for recreation of pod-0, so that all replicas are running\") e2estatefulset.WaitForState(ctx, c, ss, func(set2 *appsv1.StatefulSet, pods2 *v1.PodList) (bool, error) { ss = set2 pods = pods2 return ss.Status.ReadyReplicas == *ss.Spec.Replicas, nil }) ginkgo.By(\"Verify pod images after pod-0 deletion and recreation\") pods = e2estatefulset.GetPodList(ctx, c, ss) for i := range pods.Items { if i < int(*ss.Spec.UpdateStrategy.RollingUpdate.Partition) { gomega.Expect(pods.Items[i].Spec.Containers[0].Image).To(gomega.Equal(oldImage), fmt.Sprintf(\"Pod %s/%s has image %s not equal to current image %s\", pods.Items[i].Namespace, pods.Items[i].Name, pods.Items[i].Spec.Containers[0].Image, oldImage)) gomega.Expect(pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel]).To(gomega.Equal(currentRevision), fmt.Sprintf(\"Pod %s/%s has revision %s not equal to current revision %s\", pods.Items[i].Namespace, pods.Items[i].Name, pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel], currentRevision)) } else { gomega.Expect(pods.Items[i].Spec.Containers[0].Image).To(gomega.Equal(newImage), fmt.Sprintf(\"Pod %s/%s has image %s not equal to new image  %s\", pods.Items[i].Namespace, pods.Items[i].Name, pods.Items[i].Spec.Containers[0].Image, newImage)) gomega.Expect(pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel]).To(gomega.Equal(updateRevision), fmt.Sprintf(\"Pod %s/%s has revision %s not equal to new revision %s\", pods.Items[i].Namespace, pods.Items[i].Name, pods.Items[i].Labels[appsv1.StatefulSetRevisionLabel], updateRevision)) } } } </ins> // confirmStatefulPodCount asserts that the current number of Pods in ss is count, waiting up to timeout for ss to // scale to count. func confirmStatefulPodCount(ctx context.Context, c clientset.Interface, count int, ss *appsv1.StatefulSet, timeout time.Duration, hard bool) {", "positive_passages": [{"docid": "doc-en-kubernetes-78482ca8aa8474337677389890aeefe9bf7c97cdeab333d3d2b330616683b55b", "text": "Pla suggest : apiVersion: v1 kind: Service metadata: name: nginx labels: app: nginx spec: ports: port: 80 name: web clusterIP: None selector: app: nginx apiVersion: apps/v1 kind: StatefulSet metadata: name: web-am spec: updateStrategy: type: RollingUpdate rollingUpdate: partition: 1 serviceName: \"nginx\" replicas: 2 selector: matchLabels: app: nginx template: metadata: labels: app: nginx spec: containers: name: nginx args: /bin/sh -c sleep 30;touch /tmp/healthy; sleep 3600 image: nginx:1.14.2 ports: containerPort: 80 name: web", "commid": "kubernetes_issue_119685", "tokennum": 170}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5cc3b69a98daf1bba2564541bfc81f1fdef13a2a6bc1280eddbc043f0a9f54dc", "query": "\"restartPolicy\": \"Always\" } } <ins> {% endif %} </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-cafbbd3cd664270b9fbd0ce7e8faa35ad0e8800a7c5d7cdeb5164eec0f1b24f1", "text": "For some reason they stopped working and we even don't create manifest file for cluster autoscaler. I used the following command to start the cluster:\nIt's possible it's related to", "commid": "kubernetes_issue_26346", "tokennum": 40}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5cc9ae6170766f1b6152a513890c53ddb049c4499599013f6c555a135b28dc21", "query": "basename := filepath.Base(os.Args[0]) if err := commandFor(basename, hyperkubeCommand, allCommandFns).Execute(); err != nil { <del> fmt.Fprintf(os.Stderr, \"%vn\", err) </del> os.Exit(1) } }", "positive_passages": [{"docid": "doc-en-kubernetes-0b2213d42768c43adcb1b4f15cf67b8722c82d28c3ec9792f5837d41705eb847", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: kubectl version --client=yes command is giving the following error message. Error message is repeated at the start and the end and also containing programming jargon Error: invalid argument \"yes\" for \"--client\" flag: strconv.ParseBool: parsing \"yes\": invalid syntax Examples: Print the client and server versions for the current context kubectl version Options: --client=false: Client version only (no server required). -o, --output='': One of 'yaml' or 'json'. --short=false: Print just the version number. Usage: kubectl version [flags] [options] Use \"kubectl options\" for a list of global command-line options (applies to all commands). invalid argument \"yes\" for \"--client\" flag: strconv.ParseBool: parsing \"yes\": invalid syntax What you expected to happen: The error message can be improved with one of the two variants invalid argument \"yes\" for \"--client\" flag Examples: Print the client and server versions for the current context kubectl version Options: --client=false: Client version only (no server required). -o, --output='': One of 'yaml' or 'json'. --short=false: Print just the version number. Usage: kubectl version [flags] [options] Use \"kubectl options\" for a list of global command-line options (applies to all commands). (or) Invalid argument \"yes\" for \"--client\" flag How to reproduce it (as minimally and precisely as possible): Run the command kubectl version --client=yes Anything else we need to know?: Environment: Kubernetes version (use ): 1.15 Cloud provider or hardware configuration: AWS OS (e.g: ): Amazon Linux Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig cli\nHi Thanks for posting this issue! It turns out that this duplicate output has been in kubectl, and all the other cli cmds, since . This should be fixed by , and hopefully we can cherry pick it back to at least .", "commid": "kubernetes_issue_79454", "tokennum": 560}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5d1cb0594a7ee9541b3a418b81fb21a0927a414b404620010aac746a9457c809", "query": "} return true } <ins> // GetWindowsPath get a windows path func GetWindowsPath(path string) string { windowsPath := strings.Replace(path, \"/\", \"\", -1) if strings.HasPrefix(windowsPath, \"\") { windowsPath = \"c:\" + windowsPath } return windowsPath } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-295b16ebdca2097490863d761fa466b150fe770891272091eba588ee367ef882", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: I have tried FlexVolume on a Windows node, it does not work. I am now working on this feature now. Below is the FlexVolume initialization error What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.7.7 Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: /sig windows /assign\nDetailed steps about how to use flexvolume on Windows with this PR:\ncc:", "commid": "kubernetes_issue_56875", "tokennum": 183}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5d25b1dd3960caf7c1d04ba84371c63671b71e6509328f00dfc9416413e23325", "query": "// CheckEtcdServers will attempt to reach all etcd servers once. If any // can be reached, return true. func (con EtcdConnection) CheckEtcdServers() (done bool, err error) { <del> // Attempt to reach every Etcd server in order for _, serverURI := range con.ServerList { host, err := parseServerURI(serverURI) </del> <ins> // Attempt to reach every Etcd server randomly. serverNumber := len(con.ServerList) serverPerms := rand.Perm(serverNumber) for _, index := range serverPerms { host, err := parseServerURI(con.ServerList[index]) </ins> if err != nil { return false, err }", "positive_passages": [{"docid": "doc-en-kubernetes-cc18fa8624c9153eb5caf2824e8d5840bb7b2767a3286fa9c73b8b488eed7889", "text": "/kind bug What happened: Every time a health check is called on the APIServer via the endpoint, an etcd healthcheck is performed. However, as this just starts at the first server in the list passed to the apiserver binary all the healthchecks generate read load on a single etcd member. What you expected to happen: The first server that is checked should either increment (and wrap around) each time or be randomised to spread load around the cluster\n/assign\nI think a random check is ok.\n/sig api-machinery", "commid": "kubernetes_issue_61180", "tokennum": 117}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5d3ee6742b609219bbcea6603bbf791298833d5198d9d91a56ee8fafa372db46", "query": "} response, err := h.Client.Get(key, false, false) <del> if err != nil && !IsEtcdNotFound(err) { </del> <ins> if err != nil { if IsEtcdNotFound(err) { return nil } </ins> return err }", "positive_passages": [{"docid": "doc-en-kubernetes-9e98aee5fef5afc48ea03df9966a56409c15767acad0c30722b60251c7b487a9", "text": "With the move to running the kube-apiserver in a pod, I am getting errors of the form: The root null pointer is from this line: The line numbers in the stack are from my continuing debug of the original null pointer. We need to protect against a null pointer in this path, which appears to only be invoked when doing a list call that matches a single item based on field selector. Will submit a PR to address.\nWith proper line numbers:", "commid": "kubernetes_issue_6934", "tokennum": 97}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5d98b5dccb9509ca8d0bdfb67b6e15c16ed4a7753c80e3325ec0e19fe46263d7", "query": "echo \"ZONE='${ZONE}'\" echo \"MASTER_NAME='${MASTER_NAME}'\" echo \"MINION_IP_RANGE='${MINION_IP_RANGES[$i]}'\" <ins> echo \"EXTRA_DOCKER_OPTS='${EXTRA_DOCKER_OPTS}'\" </ins> echo \"ENABLE_DOCKER_REGISTRY_CACHE='${ENABLE_DOCKER_REGISTRY_CACHE:-false}'\" grep -v \"^#\" \"${KUBE_ROOT}/cluster/gce/templates/common.sh\" grep -v \"^#\" \"${KUBE_ROOT}/cluster/gce/templates/salt-minion.sh\"", "positive_passages": [{"docid": "doc-en-kubernetes-142e8decd8d12f564814b0a08026ec0c2500ddcd8040f0182edc6a7f51b222f8", "text": "0/8 is with a company's intranet, so it can be insecure. This is similiar to \"For GCE, allow insecure registries anywhere in 10.0.0.0/8\" Thanks!\nLinking to and .\nThis was", "commid": "kubernetes_issue_2807", "tokennum": 55}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5d9bbe1f2ac168a2790775d8f4af02fd1b7c7add9d5a5d7e87f1ddd3658964ed", "query": "return framework.NewStatus(framework.Error, \"pod cannot be nil\") } if pod.Name == \"my-test-pod\" { <del> state.Lock() </del> state.Write(framework.StateKey(pod.Name), &stateData{data: \"never bind\"}) <del> state.Unlock() </del> } return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-43588246e28947764a0f8a5c9c5b1d76a5819a8eaa1c439f79abd429269822c0", "text": "What happened: kube-scheduler () crashes due to a panic while running : The race condition is triggered when an out-of-tree plugin, that writes to during its Filter phase, is registered through . Access to in general happens from a single goroutine and there are no practical concurrency issues, with the exception of the phase, that parallelizes calls for each node across plugins: A quick glance at the tip of the branch seems to indicate the bug is still present there. What you expected to happen: Ideally access to should be synchronized everywhere for correctness, including by all in-tree plugins, since there are no guarantees about how will call multiple plugins concurrently. It seems to me it is something that was considered at some point, given that has methods. Sadly, almost no in-tree plugins are synchronizing access. For now, I will try to work around the problem by doing a single write to during and storing a data bag structure where I will write state into during (with proper synchronization), instead of writing to directly. How to reproduce it (as minimally and precisely as possible): Install a scheduler plugin that writes to during its phase. In-tree (builtin) plugins are not synchronizing their access to . Environment: Kubernetes version (use ): v1.18.8 Cloud provider or hardware configuration: linux-amd64 (AWS) OS (e.g: ): Ubuntu 18.04.5 LTS (Bionic Beaver) Others: custom kube-scheduler binary built with an out-of-tree plugin using\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scheduling\nAFAICT all in-tree plugins write to the cycle state in PreFilter and then only read from cycle state in Filter. So this shouldn't be a problem with in-tree plugins as concurrent read access should be fine during RunFilterPlugins. But since your out-of-tree plugin writes in Filter, I can see why this can be a problem.", "commid": "kubernetes_issue_95887", "tokennum": 515}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5d9bbe1f2ac168a2790775d8f4af02fd1b7c7add9d5a5d7e87f1ddd3658964ed", "query": "return framework.NewStatus(framework.Error, \"pod cannot be nil\") } if pod.Name == \"my-test-pod\" { <del> state.Lock() </del> state.Write(framework.StateKey(pod.Name), &stateData{data: \"never bind\"}) <del> state.Unlock() </del> } return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-278036efba637c2a6a49330142a64ca8f7b65a0d21755fde24824f9c473a00c9", "text": "Aside from adding Lock/Unlock in in-tree plugin, offering mutual exclusion on each key as a built-in feature within CycleState could be an alternative solution. This way, reads from in-tree plugins during Filter wouldn't interfere with writes during Filter from out-of-tree plugins.\ncc\nshould we change the Read/Write CycleState methods to be thread safe?\nAdding locks without a proper justification would just increase the latency. could you clarify your use case? Why do you need to write anything during Filter?\nyeah, we should measure it, but I don't expect it to have significant effect...\nAdding locks without a proper justification would just increase the latency. Without contention (which is the case with in-tree plugins), I don't think this is a concern.\nAdapting source from : source: essentially, 11.3 ns/Lock-Unlock pair\nI remember locks showing up in profiling for PreScore/Score for certain plugins. Although I have to admit that the accesses were not properly implemented. I'd like to hear an answer for before doing any experiments.\n+1 to that I'd also like to understand the motivations / requirements of mutating CycleState in Filter().\nMy particular use-case is that we have resources being dynamically to/removed from Nodes, and those resources need to be allocated (and tracked) in the scheduling loop. Technically I could pre-compute all the available dynamic resources for all Nodes at the phase, and snapshot it, but that would require me to pre-compute everything for all Nodes on all scheduling cycles. Instead, what I'm currently doing is computing what dynamic resources can be utilized on-demand during the phase (kind of a lazy loading of dynamic resources for each pair), and saving state of what extra resources were considered during for each Node that was evaluated. Then, later in the scheduler plugin can lock-in the exact dynamic resources for the particular Node that was selected. I understand the concern with adding extra synchronization overhead without a real need. Even if my use-case is not good enough to justify it, there is another argument for it: technically, the lack of access synchronization on violates the . Even if in the end we decide synchronizing all access is not worth the overhead (for correctness), I would strongly encourage better documentation saying which plugin phases are allowed to modify , and perhaps even forcing a snapshot-read-only copy of to be used by plugins.\nUsing the scheduler to track resources is not a good idea.", "commid": "kubernetes_issue_95887", "tokennum": 539}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5d9bbe1f2ac168a2790775d8f4af02fd1b7c7add9d5a5d7e87f1ddd3658964ed", "query": "return framework.NewStatus(framework.Error, \"pod cannot be nil\") } if pod.Name == \"my-test-pod\" { <del> state.Lock() </del> state.Write(framework.StateKey(pod.Name), &stateData{data: \"never bind\"}) <del> state.Unlock() </del> } return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-b826aaa34ec054d9cc587ce8587a04002d4daa70694ce73071b413f1bf7ba0c6", "text": "The scheduler should be stateless. Can't you track the resources with an external controller or with a device plugin and making it part of the Node spec?\nthere may be some misunderstanding in my poor choice of words. What I mean by \"tracking\" is that the scheduler needs to track usage and availability of these extra per-Node resources, to be able to allocate them during placement/scheduling. Exactly the same it does with volumes, cpus, memory, ephemeral disk, etc Doing computations in a controller outside of the scheduling loop would be similar to \"precomputing\" these resources. In my particular use case I chose a different way because: introduces another point of failure, if the external controller stops pre-computing extra resources and publishing them somewhere (CRD, Node spec, etc) scheduling halts (at least scheduling on these extra resources) Node resources in my use case are volatile (they are coming and going frequently), and the extra latency by an extra controller (vs doing all computations right in the scheduling loop) may be problematic for my use case. Even if you consider my use case not enough to add proper synchronization to , I'd still encourage making it explicit what scheduling phases are allowed to modify it (and even passing in a snapshot read-only version of to phases that are not expected to update it), to avoid confusion and race conditions.\nOk, if you are not tracking the existence of resources in the scheduler, I wouldn't suggest the external controller. Still, have you considered the device plugin framework? That way, the default kube-scheduler could keep track of resources usage. Otherwise, I still don't see why you would need to update the CycleState during Filter. As its name indicates, CycleState only lives during a scheduling cycle.\nRegardless of the correctness of usage of CycleState to do what wants, I still think we need to do at least one of the following: that writing to CycleState during Filter will lead to data races, a read-only CycleState to Filter plugins (whether we do this at the interface level or if we simply drop Write requests during Filter is an implementation detail), or make CycleState concurrency safe CycleState as it exists right now allows plugin authors to shoot themselves in the foot IMO.\nI'm leaning towards 1, but it's fair to continue the discussion before deciding.\nCan you run the \"controller\" as a goroutine along with your scheduler plugin?", "commid": "kubernetes_issue_95887", "tokennum": 520}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5d9bbe1f2ac168a2790775d8f4af02fd1b7c7add9d5a5d7e87f1ddd3658964ed", "query": "return framework.NewStatus(framework.Error, \"pod cannot be nil\") } if pod.Name == \"my-test-pod\" { <del> state.Lock() </del> state.Write(framework.StateKey(pod.Name), &stateData{data: \"never bind\"}) <del> state.Unlock() </del> } return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-038a628d524f09c8393af798b6053a1fded9e84e2c01785ad258fb86c8d6d618", "text": "So it's not an external controller binary, and hence don't introduce another point of failure. It's pretty like how the default scheduler manages its internal cache. But note that cache is only needed when you need a more efficient data structure. If a {key:value} map is good enough, spinning up a XYZInformer and obtain the latest XYZ resource on-demand is the most recommended way. I think it quite depends on how you design the internal XYZ cache. For example, it should only tweak the cache in an incremental manner - in other words, unchanged resource will be kept unmodified. You can check out the \"doubly-pointer snapshot\" of scheduler's cache. With above said, if I understand your case correctly, you may need to build a sophisticated XYZ cache, which runs in a separate goroutine and responds to your XYZ resource changes. And then upon each scheduling cycle, take a snapshot (may needs a specific snapshotting algorithm) in PreFilter() and WRITE to CycleState, and then in Filter() READ from CycleState. My personal option is to suggest all plugin developers to read from CycleState in Filter().\nnailed it. What you describe is almost exactly what I\u2019m doing today. There are some details particular to my use case (e.g. just tracking current state with an informer and an incremental cache is not enough, because there\u2019s some logic involved in deciding if currently available resources are usable by each pair, and I currently do that computation in as pairs are evaluated). In any case, I just wanted to share my use case to provide some color, but I don\u2019t want what I\u2019m doing distracting us from the more important questions, mentioned by above. My personal preference would be as a very short term next step, then when someone has cycles to do it. I would be OK with punting on until a more strong need shows up.\nNote that limiting to only reading from works for me, as long as I can still read my own data structure from it and do writes on it (i.e. don\u2019t deepclone for the phase).\nalso adds overhead (from copying the state, which can be very expensive).\nCould implement just by changing the interface passed to (e.g. ). That wouldn\u2019t be backwards compatible, but very cheap.", "commid": "kubernetes_issue_95887", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5d9bbe1f2ac168a2790775d8f4af02fd1b7c7add9d5a5d7e87f1ddd3658964ed", "query": "return framework.NewStatus(framework.Error, \"pod cannot be nil\") } if pod.Name == \"my-test-pod\" { <del> state.Lock() </del> state.Write(framework.StateKey(pod.Name), &stateData{data: \"never bind\"}) <del> state.Unlock() </del> } return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-73e2408e2bea0ec3fe3177e8a87291d57a052eb7c05f546c204ec27aefee3293", "text": "I guess that would work in the sense that you cannot change the high level values of the CycleState map, but you could still override what's inside them, if they have pointers. But maybe that's ok.\nbut you could still override what's inside them, if they have pointers. But maybe that's ok. yeah, if it was pointers and if the underlying data needed to be modified, I'd imagine it would have its own Lock/Unlock semantics\nfor such implementation, the only remaining concern is backwards compatibility. So I would leave that decision to who leads the scheduling-plugins repo.\nI rethink 's original problem a little bit: the original racing issue occurs when reading CycleState in in-tree plugins, this indicates one of the (out-of-tree) plugins is (over)writing the most high-level value of the CycleState map. But if we control the locking inside the out-of-tree plugin, and mutate that particular in-place, that would be good enough? Case 3 in the above program demonstrates the correct way to manipulate the specific out-of-tree state. Let me know your thoughts. If it resolves 's concern, we don't need to make any change on the Filter() interface.\nCase 3 is how I am working around the problem today to avoid the race. I write a \"data bag\" once into top level in , then only modify my own inner structure (with proper locking) in , without doing any further modifications to directly (top level) in . That is acceptable, but I'd encourage you to consider making the interface (and documentation) more explicit for plugins, so they avoid the mistake of writing directly into . Without changing anything (no documentation, no readonly interface), it is pretty easy for a plugin to use in a way that you don't want to support.\nThanks for confirming that. Yes, documenting it, or(and) publishing examples would be quite helpful to clarify the semantics. As a wrap-up: a keyed value can be read from CycleState, literally , in any phase. It's always race-free.", "commid": "kubernetes_issue_95887", "tokennum": 455}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5d9bbe1f2ac168a2790775d8f4af02fd1b7c7add9d5a5d7e87f1ddd3658964ed", "query": "return framework.NewStatus(framework.Error, \"pod cannot be nil\") } if pod.Name == \"my-test-pod\" { <del> state.Lock() </del> state.Write(framework.StateKey(pod.Name), &stateData{data: \"never bind\"}) <del> state.Unlock() </del> } return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-3be32b87589c297c7c2842b086ef786e82de3563d7c057c1ca18b1f858ccd170", "text": "if you want to mutate the top-level keyed value in CycleState, if it's a phase that CycleState is accessed consecutively, such as PreFilter, PreScore, it's safe to mutate CycleState in any manner if it's a phase that CycleState is accessed parallelly, to be race-free, (for now) you only have 1 option: keep the keyed value's pointer unchanged, and use an internal lock to mutate that pointer obj [TBD] we may come up with changes to add read locks to all in-tree plugins when reading values from CycleState, so that the out-of-tree plugin can surround its mutating logic between and - th mutating logic thereby can be any style Any thoughts on the TBD item? I would assume read locks wouldn't cost too much.\nFor now, I think the documentation is correct, it clearly says Read() and Write() are not thread-safe: The key thing here is whether in-tree plugin should use RLock/RUnlock or not. If yes, out-of-tree plugins can be freed to use Lock/Unlock. (see the TBD item in the previous comment)\nI like the TBD, and optimizing for correctness in how in-tree plugins are accessing . I understand the concern with synchronization overhead, but I would be really surprised if it is the bottleneck in scheduling code.\nIt can be, when you have 5k-nodes clusters, or bigger.\nI don't think it will be expensive, a rlock should be equivalent to an atomic add operation (basically it increments the number of readers). As a comparison, looking up the state from the map is likely to be more expensive.\nOf course we are assuming no contention in the default plugins.\nThis is my impression as well. A vanilla version of scheduler doesn't impose write lock in Filter() and Score(), so should be good.\nWe can always see with the benchmarks and revert if its not negligible.\nI will run the benchmarks to see if there is perf downgrade. /assign\nIssues 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\n/remove-lifecycle stale This is still relevant, yes?", "commid": "kubernetes_issue_95887", "tokennum": 535}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5d9bbe1f2ac168a2790775d8f4af02fd1b7c7add9d5a5d7e87f1ddd3658964ed", "query": "return framework.NewStatus(framework.Error, \"pod cannot be nil\") } if pod.Name == \"my-test-pod\" { <del> state.Lock() </del> state.Write(framework.StateKey(pod.Name), &stateData{data: \"never bind\"}) <del> state.Unlock() </del> } return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-bcac7b47c31a3bdcd9ddd71bfacab7dca4a98e08ad1188f8a89f61b6d0a63d38", "text": "IIUC the volumebinding plugin has been fixed, but external plugins can still shoot themselves in the foot.\n/priority backlog\nYes. I'm working on this, late this week I will send out a PR along with perf test result.", "commid": "kubernetes_issue_95887", "tokennum": 53}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5d9ce08e6493056a7a2f01fa74b3b16fb94d5f6fa5eb488c7997ca7e2c0780aa", "query": "Priorities []PriorityPolicy `json:\"priorities\"` // Holds the information to communicate with the extender(s) ExtenderConfigs []ExtenderConfig `json:\"extenders\"` <ins> // 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. HardPodAffinitySymmetricWeight int `json:\"hardPodAffinitySymmetricWeight\"` </ins> } type PredicatePolicy struct {", "positive_passages": [{"docid": "doc-en-kubernetes-88466bc637a805045217da94feabbdbd3df0ba52cd0d9904e95d3984c4cf4efa", "text": "( noticed this) HardPodAffinitySymmetricWeight should be in the , not in KubeSchedulerConfiguration If/when fixing this, we need to be careful to do it in a backward-compatilble way.\nDo you mean ? It seems scheduler policy config's args can not passed to FitPredicates; it need to update related interface. For the : mark to be deprecated and set scheduler policy config to HardPodAffinitySymmetricWeight if policy config is empty.\nAre you working on this? if no, I can take it.\n, nop; please go ahead.\n/ / / , When reviewing the PR, there's one question on : the default value of is 1, which means the weight (1) will always add to priorities if term matched (), does it our expectation? And the user has to set it to 0 to disable it. IMO, the default value of should be 0.\nThe value 1 (instead of 0) was chosen so that if you say A must run with B, there is an automatic preference that B should run with A. This seems like reasonable behavior.\nThanks very much; reasonable case to me. But it seems we can not disable it: if set to 0, the default funcs will set it to default (1); similar result to un-set. Anyway, no user complain this now :).", "commid": "kubernetes_issue_43845", "tokennum": 306}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5db7293da306e9e4c4a94428efa87290f10fc99dbd33049f5413c7d387bed691", "query": "} } <ins> // TestClusterIPLBInCreateDsrLoadBalancer tests, if the available endpoints are remote, // syncproxyrules only creates ClusterIP Loadbalancer and no NodePort, External IP or IngressIP // loadbalancers will be created. func TestClusterIPLBInCreateDsrLoadBalancer(t *testing.T) { syncPeriod := 30 * time.Second proxier := NewFakeProxier(syncPeriod, syncPeriod, clusterCIDR, \"testhost\", netutils.ParseIPSloppy(\"10.0.0.1\"), NETWORK_TYPE_OVERLAY) if proxier == nil { t.Error() } svcIP := \"10.20.30.41\" svcPort := 80 svcNodePort := 3001 svcPortName := proxy.ServicePortName{ NamespacedName: makeNSN(\"ns1\", \"svc1\"), Port:           \"p80\", Protocol:       v1.ProtocolTCP, } lbIP := \"11.21.31.41\" makeServiceMap(proxier, makeTestService(svcPortName.Namespace, svcPortName.Name, func(svc *v1.Service) { svc.Spec.Type = \"NodePort\" svc.Spec.ClusterIP = svcIP svc.Spec.ExternalTrafficPolicy = v1.ServiceExternalTrafficPolicyLocal svc.Spec.Ports = []v1.ServicePort{{ Name:     svcPortName.Port, Port:     int32(svcPort), Protocol: v1.ProtocolTCP, NodePort: int32(svcNodePort), }} svc.Status.LoadBalancer.Ingress = []v1.LoadBalancerIngress{{ IP: lbIP, }} }), ) tcpProtocol := v1.ProtocolTCP populateEndpointSlices(proxier, makeTestEndpointSlice(svcPortName.Namespace, svcPortName.Name, 1, func(eps *discovery.EndpointSlice) { eps.AddressType = discovery.AddressTypeIPv4 eps.Endpoints = []discovery.Endpoint{{ Addresses: []string{epIpAddressRemote}, NodeName:  pointer.StringPtr(\"testhost2\"), // This will make this endpoint as a remote endpoint }} eps.Ports = []discovery.EndpointPort{{ Name:     pointer.StringPtr(svcPortName.Port), Port:     pointer.Int32(int32(svcPort)), Protocol: &tcpProtocol, }} }), ) proxier.setInitialized(true) proxier.syncProxyRules() svc := proxier.svcPortMap[svcPortName] svcInfo, ok := svc.(*serviceInfo) if !ok { t.Errorf(\"Failed to cast serviceInfo %q\", svcPortName.String()) } else { // Checking ClusterIP Loadbalancer is created if svcInfo.hnsID != guid { t.Errorf(\"%v does not match %v\", svcInfo.hnsID, guid) } // Verifying NodePort Loadbalancer is not created if svcInfo.nodePorthnsID != \"\" { t.Errorf(\"NodePortHnsID %v is not empty.\", svcInfo.nodePorthnsID) } // Verifying ExternalIP Loadbalancer is not created for _, externalIP := range svcInfo.externalIPs { if externalIP.hnsID != \"\" { t.Errorf(\"ExternalLBID %v is not empty.\", externalIP.hnsID) } } // Verifying IngressIP Loadbalancer is not created for _, ingressIP := range svcInfo.loadBalancerIngressIPs { if ingressIP.hnsID != \"\" { t.Errorf(\"IngressLBID %v is not empty.\", ingressIP.hnsID) } } } } </ins> func TestEndpointSlice(t *testing.T) { syncPeriod := 30 * time.Second proxier := NewFakeProxier(syncPeriod, syncPeriod, clusterCIDR, \"testhost\", netutils.ParseIPSloppy(\"10.0.0.1\"), NETWORK_TYPE_OVERLAY)", "positive_passages": [{"docid": "doc-en-kubernetes-f554e53a2b0895170400ceeeb3f9d1f2002f8788d2419fe2262e5a5418c69b9b", "text": "I am tracking a changed behavior in networking with kubernetes 1.26. If I create a service of type externalTrafficPolicy: Local, and there are no local endpoints in a node, kube-proxy does not create hns loadbalancers for the clusterIP of that service. With kubernetes 1.25, it creates a loadbalancer for clusterIP (but not externalIP). This is the relevant log message: Looks like this comes with a result from a new function isAllEndpointsTerminating introduced in kubernetes 1.26. In Linux, we can still access clusterIP even if there are no local endpoints for the service. Thoughts? The end result is that in Windows, clients cannot access the clusterIP of such a service with there are no local endpoints.\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig windows\ncc\nDoes this issue occur when there are no local endpoints for a given service? If there is a local endpoint, then you can reach the service again, right?\n, Also let us know, do you have any InternalTrafficPolicy configured ?\nDoes this issue occur when there are no local endpoints for a given service? If there is a local endpoint, then you can reach the service again, right? That is correct , Also let us know, do you have any InternalTrafficPolicy configured ? We do not have that configured", "commid": "kubernetes_issue_115783", "tokennum": 376}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5df55c5d4296ef65620bc9ab5a6318e13c5933833aa80c2c659d689db733ed96", "query": "VolumeMounts:  volumeMounts, LivenessProbe: componentProbe(8080, \"/healthz\"), Resources:     componentResources(\"250m\"), <ins> Env:           getProxyEnvVars(), </ins> }, volumes...), kubeControllerManager: componentPod(api.Container{ Name:          kubeControllerManager,", "positive_passages": [{"docid": "doc-en-kubernetes-dc3be6ce7b42d453edf0753a2cf7546d061a63c2e475384cc9c94a48a05e7f4a", "text": "Is this a request for help? No What keywords did you search in Kubernetes issues before filing this one? http proxy, httpproxy, httpsproxy, AWS, kubeadm, kubectl, cloud-provider Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT Kubernetes version (use ): v1.4.4 Environment: Cloud provider or hardware configuration: kubeadm on EC2 instances on AWS OS (e.g. from /etc/os-release): Ubuntu 16.04.1 LTS Kernel (e.g. ): Linux ip-10-0-133-99 4.4.0-45-generic -Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x8664 x8664 x8664 GNU/Linux Install tools: kubeadm Others: httpproxy, httpsproxy and noproxy set in /etc/environment, Docker config as well on startup scripts that run What happened: won't complete and gets stuck on it's first deployment. When one looks through the logs it shows that the pods are downloading fine but we are stuck due to the kube-controller-manager continually crashing as it can't contact AWS. Elsewhere in kubernetes I see references to and if the AWS cloud provider could use that it would be able to connect as well. From the POD if I manually set httpproxy and httpsproxy and no_proxy I am able to use the AWS CLI without any issues. What you expected to happen: I would expect to successfully complete and use the environment proxies set up on the system so as not to depend on a default Internet Gateway being connected to the VPC just for AWS access. How to reproduce it (as minimally and precisely as possible): Set up a public VPC with Squid set up as a proxy Set up a private VPC peered to the public VPC Set up a master node and run Set up a regular node and run will never fully initialize. If you remove the --cloud-provider aws` then it will complete and nodes will register. Anything else do we need to know:\nwhat do you have in proxy variables ? (env | grep -i proxy) it tries to connect to (tcp 176.32.118.53:443) directly. You're expecting to connect there via proxy ? then do you have something like in your no_proxy ?", "commid": "kubernetes_issue_36573", "tokennum": 535}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5df55c5d4296ef65620bc9ab5a6318e13c5933833aa80c2c659d689db733ed96", "query": "VolumeMounts:  volumeMounts, LivenessProbe: componentProbe(8080, \"/healthz\"), Resources:     componentResources(\"250m\"), <ins> Env:           getProxyEnvVars(), </ins> }, volumes...), kubeControllerManager: componentPod(api.Container{ Name:          kubeControllerManager,", "positive_passages": [{"docid": "doc-en-kubernetes-984a2b369276e3156e0990106838472387b6975b0768d694bc54d8f6e19402d4", "text": "Unfortunately on the pod itself for the the environment variables aren't passed through. As this is created using I don't have control over the pod definition. So basically none of the *_proxy variables are set inside the pod in the docker image, however if I and export the variables and try to wget that URL it works. Basically I'm hoping we can update to respect and pass the environment variables down to the system pods if they exist, eg, add: Without it I can't stand up a cluster with AWS integration on a completely private VPC and for such a small change it would make a rather big difference.\nok, so request is actually to pass proxy variables into containers. interesting. I'll check how it can be done. BTW, for noproxy value in your example: things like 10.0.0.0/8 would not work on 99% of software that respects noproxy variable. it must be always exact IP match.\nyou're right that what I'm actually asking for is to pass proxy variables through either from a commandline setting on kubeadm or pick it up from /etc/environment or shell environment that launches kubeadm. I didn't realize it till I dug in to try and think about how one might go about fixing this. At first I thought we would just pick up the variables from the system environment but then I realized kube-controller-manager is deployed in a container and so we'd need to update the yaml file that launches it to contain the environment variables. As I'd like to go to production with this soon hopefully this is a small change that can be .\nThis issue was moved to kubernetes/kubeadm", "commid": "kubernetes_issue_36573", "tokennum": 362}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5e0f6b70415c72ccba9a0f7c0897dbdf8dee9d1d3ab2a7ad70c6fa4e67d60ccf", "query": ") const execInfoEnv = \"KUBERNETES_EXEC_INFO\" <ins> const onRotateListWarningLength = 1000 </ins> var scheme = runtime.NewScheme() var codecs = serializer.NewCodecFactory(scheme)", "positive_passages": [{"docid": "doc-en-kubernetes-d5f405b98ac26e68bb52a403345cda18a0b690bbcb8385b5ec06372b302c6e2d", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Data race in client-go with below sample code: Data race: What you expected to happen: No data race How to reproduce it (as minimally and precisely as possible): Using above given sample code Kubernetes version (use ):Cloud provider or hardware configuration:OS (e.g: ): OSX\n/sig api-machinery\nI'd like to take it. /assign\n/remove-sig api-machinery /sig auth cli\nBug triage for release 1.17 here. Since this issue has been tagged for the milestone, we would like to check it's status. Code freeze is on Nov. 14. Will this issue be resolved before then?\nAnother reminder here that code freeze is in less than two weeks (Nov. 14). We will need to move this issue out of the milestone if isn't going to be resolved before then.", "commid": "kubernetes_issue_80269", "tokennum": 239}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5e480e7463a8d598dadbd759232890a158363ef198430ae7d900099ef648b5ea", "query": "flagNames.InsecureSkipTLSVerify.BindBoolFlag(flags, &clusterInfo.InsecureSkipTLSVerify) } <del> // BindOverrideFlags is a convenience method to bind the specified flags to their associated variables func BindOverrideFlags(overrides *ConfigOverrides, flags *pflag.FlagSet, flagNames ConfigOverrideFlags) { BindAuthInfoFlags(&overrides.AuthInfo, flags, flagNames.AuthOverrideFlags) BindClusterFlags(&overrides.ClusterInfo, flags, flagNames.ClusterOverrideFlags) BindContextFlags(&overrides.Context, flags, flagNames.ContextOverrideFlags) flagNames.CurrentContext.BindStringFlag(flags, &overrides.CurrentContext) flagNames.Timeout.BindStringFlag(flags, &overrides.Timeout) } </del> // BindFlags is a convenience method to bind the specified flags to their associated variables func BindContextFlags(contextInfo *clientcmdapi.Context, flags *pflag.FlagSet, flagNames ContextOverrideFlags) { flagNames.ClusterName.BindStringFlag(flags, &contextInfo.Cluster)", "positive_passages": [{"docid": "doc-en-kubernetes-4e19a56e8ccacbab4546f622baecdb0b8ef30250430c55f8bcdc4de99b100cd2", "text": "Found in openshift, but I'm pretty sure the codepaths are the same. That means the token is getting ignored and in-cluster config is being used in preference to flags.\nIs a similar issue?\nYep, kind of regression.\nSigh.\nYes, most likely the same cause.\nI'm on it.\nUnit test :)\nProbably will want to cherrypick this into 1.5.\nWIP in", "commid": "kubernetes_issue_38834", "tokennum": 89}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5e615403699e0893fe2e47440ae80c698ab6c0377dbe0e60e218a97ec94f9dd2", "query": "\"github.com/golang/glog\" <del> \"k8s.io/api/core/v1\" </del> apierrors \"k8s.io/apimachinery/pkg/api/errors\" <del> \"k8s.io/apimachinery/pkg/labels\" </del> utilruntime \"k8s.io/apimachinery/pkg/util/runtime\" \"k8s.io/apimachinery/pkg/util/wait\" <del> v1informers \"k8s.io/client-go/informers/core/v1\" v1listers \"k8s.io/client-go/listers/core/v1\" </del> \"k8s.io/client-go/tools/cache\" \"k8s.io/client-go/util/workqueue\"", "positive_passages": [{"docid": "doc-en-kubernetes-89e8d863e20723ba6498e9abf897dd4e49e26cad02c0dde0a4957b2eb3151e69", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Currently APIServiceRegistrationController watch service change and find the related APIServices related if any. Then it AddAPIService/RemoveAPIService for APIAggregator. I dig into the kube-aggregator and find it no need totally, because update APIServices status when related service or endpoint change. So if does not watch services, it will not miss any event for APIServices. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/cc\n/kind enhancement /sig api-machinery\n/assign\nthat does not follow. AvailableConditionController modifies the APIService object. APIServiceRegistrationController must still watch the APIService objects to observe those changes.\noh, I misread the description. You're saying APIServiceRegistrationController doesn't need to watch v1.Service objects", "commid": "kubernetes_issue_57836", "tokennum": 300}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5e9af35bfc7bc84cce4e0d019c46bbd300cb0813d505b59118cdf0b1e18f6091", "query": "Endpoints: []discovery.Endpoint{}, }, }, <ins> \"bad-port-name-length\": { expectedErrors: 1, endpointSlice: &discovery.EndpointSlice{ ObjectMeta:  standardMeta, AddressType: addressTypePtr(discovery.AddressTypeIP), Ports: []discovery.EndpointPort{{ Name:     utilpointer.StringPtr(strings.Repeat(\"a\", 64)), Protocol: protocolPtr(api.ProtocolTCP), }}, Endpoints: []discovery.Endpoint{}, }, }, </ins> \"invalid-port-protocol\": { expectedErrors: 1, endpointSlice: &discovery.EndpointSlice{", "positive_passages": [{"docid": "doc-en-kubernetes-b73bb51cef5016ee2dcd80aae4248808fec811a4dad3a3b7abbba7673a446c48", "text": "What happened: No endpoints created in the EndpointSlice for my service due to the port on the service being too long. Logs show: EndpointSlice created has no endpoint: What you expected to happen: Service that works with Endpoints should work with EndpointSlice. If this is intentional, it should be clearly documented How to reproduce it (as minimally and precisely as possible): Create a service with a long port name Environment: Kubernetes version (use ): 1.16 Cloud provider or hardware configuration: kind\n/sig networking\nThe label(s) cannot be applied. These labels are supported: <detailsIn response to : /sig networking 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\n/sig network These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by vllry. \u200d\nFor a rough measure of impact, Istio had 5 ports that were over this limit (and many more that were right at 15 characters), so I suspect it may not be terribly rare.\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nThis needs to be resolved before endpointslices graduate from alpha\n/assign\n/remove-triage unresolved", "commid": "kubernetes_issue_84388", "tokennum": 292}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5ea080f8fea0f29375b1a0e7f008efedd902bf255a7ed23b734f33175ab943f6", "query": "\"spec\": { \"containers\": [{ \"name\": \"test-container\", <del> \"image\": \"gcr.io/google_containers/pause-amd64:3.0\" </del> <ins> \"image\": \"gcr.io/google_containers/pause-amd64:3.1\" </ins> }] } }", "positive_passages": [{"docid": "doc-en-kubernetes-a834f77ddd825b3d04a660aa7c11d0734893e4dcde6e0d4a7399e3b3daf56428", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: the pause-amd64:3.0 image on has an empty schema2 manifest, which prevents is from being pulled by proxy/caches which only support V2 registries. What you expected to happen: Being able to pull ` using a V2 manifest compatible client. Anything else we need to know?: The proxy/cahce is requesting this\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nAfter talking with , he mentionned the following\nAFAIK, does not support well. After inspecting the image, you can find is still using manifest v1.\n/cc FYI\nIm not sure which exact version x sch\u00e9ma X is needed. What I know is that we can download through the proxy/cache all other Kubernetes kube-system images, only the pause image is giving us trouble. Therefore, I would say that having the image available using the same format as the other kube-system images would be the request here.\nYeah, we haven't updated the pause image in a while, since it doesn't really ever change. I'm not sure whether rebuilding + pushing over the existing tag is safe, or if we should bump to or something. thoughts?\nIf we do rebuilding/updating the image, that would help and a bunch of similar issues.\nit's better/save to go with new tag\nI didn't realize there were changes to the pause binary that were never actually deployed. It seems like we should probably just do that (and bump the tag).\nthat sounds great. Any idea when the existing 3.0 tag could be pushed again?\nWe shouldn't push over the 3.0 tag; we should push a 3.1 or 4.0 tag instead. I'm not sure who owns the pause container who should drive this. Maybe sig-node and/or\nIt seems like it should be sig-node. I'll look into it.\nThe new container has been built, can you test with\nIts working! thanks! I was able to pull it through our artifactory proxy , Lee Verberne <:\nexcellent, thanks for checking. /assign", "commid": "kubernetes_issue_56253", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5ea080f8fea0f29375b1a0e7f008efedd902bf255a7ed23b734f33175ab943f6", "query": "\"spec\": { \"containers\": [{ \"name\": \"test-container\", <del> \"image\": \"gcr.io/google_containers/pause-amd64:3.0\" </del> <ins> \"image\": \"gcr.io/google_containers/pause-amd64:3.1\" </ins> }] } }", "positive_passages": [{"docid": "doc-en-kubernetes-7628cd26f0dafa992a4ea43a6c68b9bcdbf056fca43ee32b40ab60cef4154c17", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: pause does not reap zombie processes using the default pause container provided by What you expected to happen: should include the up to date pause code to reap zombie processes when using docker = 1.13.1 found here How to reproduce it (as minimally and precisely as possible): a.out will leave a zombie process that is not cleaned up Anything else we need to know?: Building the pause container from master solves this issue Related: Environment: Kubernetes version (use ): 1.7.0+ Cloud provider or hardware configuration**: N/A OS (e.g. from /etc/os-release): CentOS 7 Kernel (e.g. ): 4.10.13+ Install tools: Others: docker = 1.13.1\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\ni get a simliar problem when i run crond service in pod container, every day it makes some [anacron] zombie progresses UID PID PPID C STIME TTY TIME CMD root 1 0 0 Nov14 ? 00:00:00 /pause root 7 0 0 Nov14 ? 00:00:00 /usr/local/bin/dumb-init /usr/lo root 13 7 0 Nov14 ? 00:00:00 nginx: master process /usr/local nobody 21 13 0 Nov14 ? 00:00:01 nginx: worker process nobody 22 13 0 Nov14 ? 00:00:07 nginx: worker process nobody 23 13 0 Nov14 ? 00:00:07 nginx: worker process nobody 24 13 0 Nov14 ? 00:00:05 nginx: worker process root 77 1 0 Nov14 ? 00:00:00 [anacron] root 1 0 00:01 ? 00:00:00 [anacron] <defunctroot 1 0 01:01 ? 00:00:00 [anacron] <defunctroot 1 0 02:01 ?", "commid": "kubernetes_issue_50865", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5ea080f8fea0f29375b1a0e7f008efedd902bf255a7ed23b734f33175ab943f6", "query": "\"spec\": { \"containers\": [{ \"name\": \"test-container\", <del> \"image\": \"gcr.io/google_containers/pause-amd64:3.0\" </del> <ins> \"image\": \"gcr.io/google_containers/pause-amd64:3.1\" </ins> }] } }", "positive_passages": [{"docid": "doc-en-kubernetes-6179feaaee46a15cd909bb088c82657b9b59fba8efdee1296995076588512032", "text": "00:00:00 [anacron] <defunctroot 1 0 03:01 ? 00:00:00 [anacron] <defunctroot 0 0 11:49 ? 00:00:00 /bin/bash root 0 1 19:15 ? 00:00:00 /bin/bash root 0 19:15 ? 00:00:00 ps -ef !\nDo we know why this was never resolved / was never deployed?\nI just fought through this issue with a rabbitmq helm chart. I had to custom build a pause container from master to fix it. The rabbitmq helm chart uses for its liveness checks. It's a thin wrapper around a call to the rabbitmq-server daemon, which is not PID 1 (/pause is PID 1). The rabbitmq-server process forks some children to do the work and then they exit. Since the pause-amd64:3.0 is not reaping, those processes stick around as zombies. The liveness check runs every 5 seconds. After about 4 hours, there are about 27K zombies and the node begins failing to launch new containers because it's starved for resources. The pause container built from current master fixes that behavior, no zombies at all in the container.\nThe plan is to build a new version of pause-amd64 and then update the image referenced by Kubernetes. This means the default image will change in the next Kubernetes release. We can make the new image available once the freeze lifts and we can merge .\nLooks like this made it into 1.10", "commid": "kubernetes_issue_50865", "tokennum": 336}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5ee8123608a19a5d98183d1906a1386cdb03a3d4a3bfd6b38b96c5b23f1dfecc", "query": "} # k8s <del> KUBE_VERSION=${KUBE_VERSION:-\"1.1.4\"} </del> <ins> KUBE_VERSION=${KUBE_VERSION:-\"1.1.7\"} </ins> echo \"Prepare kubernetes ${KUBE_VERSION} release ...\" grep -q \"^${KUBE_VERSION}$\" binaries/.kubernetes 2>/dev/null || { curl -L https://github.com/kubernetes/kubernetes/releases/download/v${KUBE_VERSION}/kubernetes.tar.gz -o kubernetes.tar.gz", "positive_passages": [{"docid": "doc-en-kubernetes-c9a7a8de199b532837929cf19816bb31dfb902dab306b212a976e292dbb5b33e", "text": "download- refers to release 1.1.4 but the latest is 1.1.7\nResolved by PR", "commid": "kubernetes_issue_21039", "tokennum": 22}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5eff49486ba052786459583c8897095e6ce3880f004a1ff8f0ecab19b5861b4a", "query": "const ( csiNodeLimitUpdateTimeout  = 5 * time.Minute <del> csiPodUnschedulableTimeout = 2 * time.Minute </del> <ins> csiPodUnschedulableTimeout = 5 * time.Minute </ins> ) var _ = utils.SIGDescribe(\"CSI mock volume\", func() {", "positive_passages": [{"docid": "doc-en-kubernetes-1f9c3e5cc71a2eb982031bdc2376fc7ce9ffe73bb0100bc8df9e6d81af2040c4", "text": "Looks like CSI volume limit test is flaking. /sig storage /assign\nThis flake isn't happening in normal clusters, appears to be alpha only issue.", "commid": "kubernetes_issue_75070", "tokennum": 34}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5f00897bafe37025a7f727e570277102153195cf8de102fdfd2ce08a2859fd33", "query": "\"//staging/src/k8s.io/component-base/metrics:go_default_library\", \"//vendor/github.com/emicklei/go-restful:go_default_library\", \"//vendor/github.com/google/cadvisor/info/v1:go_default_library\", <ins> \"//vendor/github.com/pkg/errors:go_default_library\", </ins> \"//vendor/k8s.io/klog:go_default_library\", ], )", "positive_passages": [{"docid": "doc-en-kubernetes-2d86227263004d2306fadc99355cf0a88aac1d38d7e2576116201cd81e3141b9", "text": "What happened: In handler#handleSummary, return value from request.Request.ParseForm() is ignored. What you expected to happen: The error return should be checked.\n/sig node\nHi this seems to be easy to fix. Could I solve this?\nPlease go ahead.", "commid": "kubernetes_issue_90085", "tokennum": 62}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5f17ebf387b9c5829933399653790df061306a0667483bdbc7ebb26b66102bbf", "query": "return 0 } <del> func (ds *dockerService) getSecurityOpts(containerName string, sandboxConfig *runtimeapi.PodSandboxConfig, separator rune) ([]string, error) { hasSeccompSetting := false annotations := sandboxConfig.GetAnnotations() if _, ok := annotations[v1.SeccompContainerAnnotationKeyPrefix+containerName]; !ok { _, hasSeccompSetting = annotations[v1.SeccompPodAnnotationKey] } else { hasSeccompSetting = true </del> <ins> func (ds *dockerService) getSecurityOpts(seccompProfile string, separator rune) ([]string, error) { if seccompProfile != \"\" { glog.Warningf(\"seccomp annotations are not supported on windows\") </ins> } <del> if hasSeccompSetting { glog.Warningf(\"seccomp annotations found, but it is not supported on windows\") } </del> return nil, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-fc6177451e9ae3dd109f95c34ca28c9d9a0c4aae10f2acbc42a784aa55bc42f8", "text": "seems to belong to sig node PTAL and fix ASAP\n/assign as it seems like having something to do with", "commid": "kubernetes_issue_50675", "tokennum": 24}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5f27feedcfa768f0fad712cba99f6da0434976f66ea9d15345ed78f1708c054b", "query": "setHugepages() ginkgo.By(\"restarting kubelet to pick up pre-allocated hugepages\") <del> restartKubelet() </del> <ins> // stop the kubelet and wait until the server will restart it automatically stopKubelet() // wait until the kubelet health check will fail gomega.Eventually(func() bool { return kubeletHealthCheck(kubeletHealthCheckURL) }, time.Minute, time.Second).Should(gomega.BeFalse()) // wait until the kubelet health check will pass gomega.Eventually(func() bool { return kubeletHealthCheck(kubeletHealthCheckURL) }, 2*time.Minute, 10*time.Second).Should(gomega.BeTrue()) </ins> waitForHugepages()", "positive_passages": [{"docid": "doc-en-kubernetes-88c095cfe151193749adeb925825c9856381f9f8544c8822d93b8eb731e64566", "text": "ci-kubernetes-node-kubelet-serial-hugepages when start the pod with the resources requests that contain multiple hugepages resources should set correct hugetlb mount and limit under the container cgroup Unexpected error: \"pod ran to completion\", Multiple sizes huge pages is going to be graduated to GA, so having this test job fixed is quite important.\n/sig node\n/assign\n/triage accepted\n/cc\nI did a small analysis and I can see that the pod failed to start, I can not find any failure messages under the kubelet log, so it really hard to say why it failed.\nwere you able to reproduce it locally? btw, there is a \"right way\" to fix this - to fix dynamic update of a hugepage resources. This would eliminate need in a kubelet restart. There is even a PR for that: , we just need to make it working again.\nafter conversation with on slack I'd say we should stick to the current procedure - restarting kubelet when hugepages allocation changes. So, we should investigate why kubelet doesn't restart properly in this test case and fix it.\nNope, I failed to reproduce it locally, also under the CI, it does not appear often. The best thing will be to describe the pod in case if it failed, so we will see the reason.\nunder the code we have so from the log , I can see that the kubelet received the pod before the kubelet stopped, so the problem that pod dropped to Failed state because of the kubelet stop.\nSo some additional details, the one who responsible to restart the kubelet again, is the server service: restart the kubelet service are waiting for hugepages to be available are starting the pod server service restart the kubelet again because it was not healthy for too long - failed to start because of the kubelet restart\ngreat findings! Should we just stop the kubelet and let the server service to start it again? We can also check if the kubelet is restarted successfully before starting the pod.\nI tried it under the PR , also I unsure how can we check if the kubelet restarted successfully. All tests that I wrote before I checked if the node has NotReady state and waited until it will be Ready, but in case of the restart probably the node will always have Ready state because the time period is very short. I will continue to investigate and will check locally how can I fix it.", "commid": "kubernetes_issue_99402", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5f27feedcfa768f0fad712cba99f6da0434976f66ea9d15345ed78f1708c054b", "query": "setHugepages() ginkgo.By(\"restarting kubelet to pick up pre-allocated hugepages\") <del> restartKubelet() </del> <ins> // stop the kubelet and wait until the server will restart it automatically stopKubelet() // wait until the kubelet health check will fail gomega.Eventually(func() bool { return kubeletHealthCheck(kubeletHealthCheckURL) }, time.Minute, time.Second).Should(gomega.BeFalse()) // wait until the kubelet health check will pass gomega.Eventually(func() bool { return kubeletHealthCheck(kubeletHealthCheckURL) }, 2*time.Minute, 10*time.Second).Should(gomega.BeTrue()) </ins> waitForHugepages()", "positive_passages": [{"docid": "doc-en-kubernetes-df5fd4d114576094d5b1a71b893d21a3e13b2c561e9313633a9dfbe243849634", "text": "So the only reliable solution that I found, it just trying to start the pod number of times. I tested it 5 times and the test passed. Can you please review\nCan we access kubelet service from hugepage test cases? If we can we can use its APIs like or to check if kubelet is ready after the restart. Overall I have a feeling of duplication test/e2enode/services functionality in This is a main reason for this and similar bugs I believe. It would be nice to get rid of this duplication if possible. That would nicely isolate kubelet service controls in one place and eliminate conflicts like this one. wdyt?\nnot really, the used mostly to start all needed components to emulate the cluster(not only the kubelet) and the test does not have access to it. I think you can separate the readiness check under the importable method, but it worth the separate PR.\nI updated the PR to check the healthiness of the kubelet and looks like it works just fine.\nthank you. it looks good to me so far. I'll add lgtm label when is merged and tests are all green.\nthe job is still flaky. can you reopen this issue?\nI opened a different one - , the issue can affect any job, not only the hugepages one.\nI can open a fix to W/A an issue(start the pod until it will succeed), it should fix all problems, WDYT?\ni think it's ok as a workaround, until is fixed\nwould it be better to wait until api server reports correct resource value before running the pod?\nWe are waiting for it, the problem that the scheduler and the kubelet see a different picture regarding resources requested by pods.\nok. In this case restarting the pod until it succeeds seems reasonable to me to fix the flakiness until is fixed.\nany progress on the workaround fix?", "commid": "kubernetes_issue_99402", "tokennum": 404}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5f2fb841329d3cccb57bb3ba72f0a542792802bf1f1c84cc3829c59e5488753f", "query": "match: BASEIMAGE?=k8s.gcr.io/build-image/debian-base-s390x:[a-zA-Z]+-v((([0-9]+).([0-9]+).([0-9]+)(?:-([0-9a-zA-Z-]+(?:.[0-9a-zA-Z-]+)*))?)(?:+([0-9a-zA-Z-]+(?:.[0-9a-zA-Z-]+)*))?) - name: \"k8s.gcr.io/debian-iptables: dependents\" <del> version: buster-v1.4.0 </del> <ins> version: buster-v1.5.0 </ins> refPaths: - path: build/common.sh match: debian_iptables_version=", "positive_passages": [{"docid": "doc-en-kubernetes-ee0826757468ea334f95c77509b257c3d392b6713b4311ba7afa125d642dcec9", "text": "The based container images for are shipped with the wrong architecture within the manifest if not amd64: Refers to We updated the images a few minutes ago to buster-v1.3.0, which are now ready to be used as base for the multi-architecture images. If the images contain the right architectures, then it may magically happen that the kube-proxy images are fixed, too. This is because we already use the build syntax for it: /cc\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig release", "commid": "kubernetes_issue_98229", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5f540bbf7e040f408dc43a80c9f3ca895f19c2cfa1a894c707bc5819c73d2178", "query": "VolumePlugins:      volumePlugins(), TLSOptions:         nil, OOMAdjuster:        oom.NewFakeOOMAdjuster(), <del> Mounter:            mount.New(\"\" /* default mount path */), </del> <ins> Mounter:            &mount.FakeMounter{}, </ins> Subpather:          &subpath.FakeSubpath{}, HostUtil:           hostutil.NewFakeHostUtil(nil), }", "positive_passages": [{"docid": "doc-en-kubernetes-d99484417892d904a3f5edbb73fa06d2de654c460b279ad73f511e028afa6a6f", "text": "There are CVEs happening in different images - we already migrated Kubmeark from busybox in , but we should go one step further and migrate the base image to distroless. There are some things that would need to be changed mentioned here: /sig scalability\nCan I work on this? /assign\n/remove-help\n- sure that would be great.\nHi based on the discussion in , the kubemark image has dependency on and maybe more other utilities. So it seems impossible to migrate the base image to distroless? Or do we need something like debian-hyperkube-base?\nThe mount one we may get rid of - basically we should be able to switch to FakeMounter:", "commid": "kubernetes_issue_84284", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5f7d322b6c459fb675e211727e0a7483b50fca33567c7d1885d38c6e629a8264", "query": ")}, wantErr: \"duplicate profile with scheduler name \"foo\"\", }, <ins> { name: \"With extenders\", opts: []Option{ WithProfiles( schedulerapi.KubeSchedulerProfile{ SchedulerName: \"default-scheduler\", Plugins: &schedulerapi.Plugins{ QueueSort: schedulerapi.PluginSet{Enabled: []schedulerapi.Plugin{{Name: \"PrioritySort\"}}}, Bind:      schedulerapi.PluginSet{Enabled: []schedulerapi.Plugin{{Name: \"DefaultBinder\"}}}, }, }, ), WithExtenders( schedulerapi.Extender{ URLPrefix: \"http://extender.kube-system/\", }, ), }, wantProfiles:  []string{\"default-scheduler\"}, wantExtenders: []string{\"http://extender.kube-system/\"}, }, </ins> } for _, tc := range cases {", "positive_passages": [{"docid": "doc-en-kubernetes-75719ce40debdc24665e0bd0c466c638c232f756949a78511459bd94dde06b58", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --here is supposed to be set through , but is not called from anywhere except tests, so always returns . should be set through here. Am I missing something? N/A None Kubernetes version (use ): master () Cloud provider or hardware configuration: N/A OS (e.g: ): N/A Kernel (e.g. ): N/A Install tools: N/A Network plugin and version (if this is a network-related bug): N/A Others: None\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scheduling\nThanks for pointing that out. The plumbing of extenders to the framework impact calling extenders on preemption. That seems to be a path not covered by tests end to end. Can you submit a PR to fix this? as you mentioned we need to pass the extenders on profile creation. We need to patch the fix back to v1.21 and v1.20 (the release where this was refactored). /cc\nI have submitted a PR for a fix.", "commid": "kubernetes_issue_102971", "tokennum": 348}], "negative_passages": []}
{"query_id": "q-en-kubernetes-5fe8512897969566897ce405f8f7dfaddc6f6155e59ee1d18802d324cfec81d6", "query": "// Flush is part of Interface.  Currently we delete IPVS services one by one func (runner *runner) Flush() error { <del> vss, err := runner.GetVirtualServers() if err != nil { return err } for _, vs := range vss { err := runner.DeleteVirtualServer(vs) // TODO: aggregate errors? if err != nil { return err } } return nil </del> <ins> return runner.ipvsHandle.Flush() </ins> } // AddRealServer is part of Interface.", "positive_passages": [{"docid": "doc-en-kubernetes-13eba344b12142e2782a67745f08ac2e814f1785c70b127779bdac58248d8b7b", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: Currently, we flush ipvs services by deleting them one by one. That's because there was no flush API in libnetwork. Now, libnetwork supports flush API, I think it's time to rsync. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration**: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig network\n/area kube-proxy\n/assign", "commid": "kubernetes_issue_52070", "tokennum": 279}], "negative_passages": []}
{"query_id": "q-en-kubernetes-604d17a2c9df63227164276d22de278b9ced7181f0d3a5bc3b19980d69cb23a5", "query": "\"k8s.io/kubernetes/pkg/api/v1\" dockertypes \"github.com/docker/engine-api/types\" <ins> dockercontainer \"github.com/docker/engine-api/types/container\" </ins> ) <ins> // These two functions are OS specific (for now at least) func updateHostConfig(config *dockercontainer.HostConfig) { // There is no /etc/resolv.conf in Windows, DNS and DNSSearch options would have to be passed to Docker runtime instead hc.DNS = opts.DNS hc.DNSSearch = opts.DNSSearch // MemorySwap == -1 is not currently supported in Docker 1.14 on Windows // https://github.com/docker/docker/blob/master/daemon/daemon_windows.go#L175 hc.Resources.MemorySwap = 0 } func DefaultMemorySwap() int64 { return 0 } </ins> func getContainerIP(container *dockertypes.ContainerJSON) string { if container.NetworkSettings != nil { for _, network := range container.NetworkSettings.Networks {", "positive_passages": [{"docid": "doc-en-kubernetes-2c477631a31f290ae271a7ca0a83a97399cbf63c4cfd883674b6ddce7387fc19", "text": "What happened: Latest kubelet + Windows Docker version 1.14.0-dev refused to start any containers, error output: \"invalid option: Windows does not support MemorySwap\" How to reproduce it (as minimally and precisely as possible): It's always reproducible with Windows Docker 1.14.0-dev + latest kubelet code base. Anything else do we need to know: It didn't happen for Windows Docker 1.12.2-cs2-ws-beta. The reason behind the issue was because new code was for Windows Docker to check Resources parameters, it doesn't accept a non-zero value for MemorySwap: But kubelet was default to set an unlimited (-1) value. The issue was gone in my setup after applied a private fix to disable MemorySwap by set it to zero for Windows.", "commid": "kubernetes_issue_39003", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6055c240f51cce1ed523b72d44fc05ba58f20d883a93cd5dd51ac33892d3a18e", "query": "const ( DefaultEtcdPathPrefix = \"/registry\" <ins> globalTimeout         = time.Minute </ins> ) // StorageDestinations is a mapping from API group & resource to", "positive_passages": [{"docid": "doc-en-kubernetes-98dd9e78520525bf65ff2afc2de58a6375036f9264791def3d02921656a321fe", "text": "this job failed with It seems it is imssing some dependency The job history confirms it is totally broken Originally posted by in\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig testing", "commid": "kubernetes_issue_103738", "tokennum": 114}], "negative_passages": []}
{"query_id": "q-en-kubernetes-60776d769ad222723d51ae91a04a3683bfcc7859d13c379f455af2bbcdcd86d2", "query": "w.WriteHeader(http.StatusNotFound) } <del> func startComponents(manifestURL, apiVersion string) (string, string) { </del> <ins> func startComponents(firstManifestURL, secondManifestURL, apiVersion string) (string, string) { </ins> // Setup servers := []string{} glog.Infof(\"Creating etcd client pointing to %v\", servers)", "positive_passages": [{"docid": "doc-en-kubernetes-56027fa26048aea64718f2bd7d7c5d6f58ddca1472c1fc738c03141b6dea3ad6", "text": "Currently it assumes it can read ContainerManifest - it should try both\nWhy not hold on this until we have Kubelet-read-Pod in?\nAlso the HTTP source has the same problem.\nIt should read Pod. Changed the title.\nIdeally, I'd like all Pods created directly via Kubelet to be to etcd and surfaced via the API. If updates are made via the API, I'd like those to propagate back to the node. We can discuss whether the config file should be updated or ignored. At some point, I'd like Kubelet to persistently cache pods received from the apiserver, perhaps by just writing them all out as config files.\nis the issue to sync local pods back to apiserver.\nthis is somewhat related to other issues we talked about.\nDetail: We want locally specified pods to be able to use YAML config files, but we also want to rip YAML out of the API server . The config-file behavior should be as similar to the kubectl experience. Kubelet could use parts of the kubectl library to translate YAML to JSON. Vision: Eventually, I'd like Kubelet to use the apiserver library and support exactly the same Pod API as the master, at which time I'd like kubectl be able to create pods directly on Kubelets, as well as reading from config files. I also expect to have a per-node controller . I'd like to be able to use the per-node controller to update pods started via config files (or direct kubectl-kubelet pods), overriding those original files. For availability and self-hosting, we'll eventually need local checkpointing , ideally just using serialized JSON for each object. If Kubelet used apiserver, this could be done using a custom registry implementation.\nI think that is a prerequisite for it.\nIf noone picks it up, I'm going to start working on it tomorrow.\nthanks, wojtek-t\nfixed it for http channel", "commid": "kubernetes_issue_3372", "tokennum": 445}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6079718c006e3aab69e724b8c3e64944e4284cfa46309e78662154d4878da361", "query": "Priorities []PriorityPolicy // Holds the information to communicate with the extender(s) ExtenderConfigs []ExtenderConfig <ins> // 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. HardPodAffinitySymmetricWeight int </ins> } type PredicatePolicy struct {", "positive_passages": [{"docid": "doc-en-kubernetes-88466bc637a805045217da94feabbdbd3df0ba52cd0d9904e95d3984c4cf4efa", "text": "( noticed this) HardPodAffinitySymmetricWeight should be in the , not in KubeSchedulerConfiguration If/when fixing this, we need to be careful to do it in a backward-compatilble way.\nDo you mean ? It seems scheduler policy config's args can not passed to FitPredicates; it need to update related interface. For the : mark to be deprecated and set scheduler policy config to HardPodAffinitySymmetricWeight if policy config is empty.\nAre you working on this? if no, I can take it.\n, nop; please go ahead.\n/ / / , When reviewing the PR, there's one question on : the default value of is 1, which means the weight (1) will always add to priorities if term matched (), does it our expectation? And the user has to set it to 0 to disable it. IMO, the default value of should be 0.\nThe value 1 (instead of 0) was chosen so that if you say A must run with B, there is an automatic preference that B should run with A. This seems like reasonable behavior.\nThanks very much; reasonable case to me. But it seems we can not disable it: if set to 0, the default funcs will set it to default (1); similar result to un-set. Anyway, no user complain this now :).", "commid": "kubernetes_issue_43845", "tokennum": 306}], "negative_passages": []}
{"query_id": "q-en-kubernetes-607e84ced79aa2e76fd42d37a38cdd726e203cf299d4c370a9d77a45aac10bba", "query": "func addConversionFuncs(scheme *runtime.Scheme) { // Add non-generated conversion functions err := scheme.AddConversionFuncs( <del> v1.Convert_api_ServiceSpec_To_v1_ServiceSpec, </del> <ins> v1.Convert_v1_DeleteOptions_To_api_DeleteOptions, v1.Convert_api_DeleteOptions_To_v1_DeleteOptions, v1.Convert_v1_ExportOptions_To_api_ExportOptions, v1.Convert_api_ExportOptions_To_v1_ExportOptions, v1.Convert_v1_List_To_api_List, v1.Convert_api_List_To_v1_List, v1.Convert_v1_ListOptions_To_api_ListOptions, v1.Convert_api_ListOptions_To_v1_ListOptions, v1.Convert_v1_ObjectFieldSelector_To_api_ObjectFieldSelector, v1.Convert_api_ObjectFieldSelector_To_v1_ObjectFieldSelector, v1.Convert_v1_ObjectMeta_To_api_ObjectMeta, v1.Convert_api_ObjectMeta_To_v1_ObjectMeta, v1.Convert_v1_ObjectReference_To_api_ObjectReference, v1.Convert_api_ObjectReference_To_v1_ObjectReference, v1.Convert_v1_OwnerReference_To_api_OwnerReference, v1.Convert_api_OwnerReference_To_v1_OwnerReference, v1.Convert_v1_Service_To_api_Service, v1.Convert_api_Service_To_v1_Service, v1.Convert_v1_ServiceList_To_api_ServiceList, v1.Convert_api_ServiceList_To_v1_ServiceList, v1.Convert_v1_ServicePort_To_api_ServicePort, v1.Convert_api_ServicePort_To_v1_ServicePort, v1.Convert_v1_ServiceProxyOptions_To_api_ServiceProxyOptions, v1.Convert_api_ServiceProxyOptions_To_v1_ServiceProxyOptions, </ins> v1.Convert_v1_ServiceSpec_To_api_ServiceSpec, <ins> v1.Convert_api_ServiceSpec_To_v1_ServiceSpec, v1.Convert_v1_ServiceStatus_To_api_ServiceStatus, v1.Convert_api_ServiceStatus_To_v1_ServiceStatus, </ins> ) if err != nil { // If one of the conversion functions is malformed, detect it immediately.", "positive_passages": [{"docid": "doc-en-kubernetes-5056a2515a29befdf589a74f13db031ed4142bbabfa8d2c37cafac2de4fccaea", "text": "I started the federation-apiserver and went to and got the following output: Expected: I should have got an empty v1.ServiceList Any idea on what we are doing wrong? Have you guys seen this error?\nI think your deep copiers or conversion functions are not getting registered properly. If you look at my change in , some places are inappropriately registering with api.Scheme instead of the passed in scheme. Maybe you have that problem or a similar one, since I think you guys copied some code. , Nikhil Jindal wrote:\nDeep copy generation was slightly broken as well - you may want to double check that they are registered. On May 23, 2016, at 5:50 PM, Daniel Smith wrote: I think your deep copiers or conversion functions are not getting registered properly. If you look at my change in , some places are inappropriately registering with api.Scheme instead of the passed in scheme. Maybe you have that problem or a similar one, since I think you guys copied some code. , Nikhil Jindal wrote: \u2014 You are receiving this because you are on a team that was mentioned. Reply to this email directly or view it on GitHub\nI got the same error with latest branch, as I was swamping on service controller, so I use a previous version and worked around it.\ndeep copies were indeed missing, but adding them hasnt fixed the issue. Will debug more. is my PR to add the deep copies cc Please feel free to file issues for any such problem you face. We need to fix all these issues. Its good if we know about them early. Thanks!\nfixes this", "commid": "kubernetes_issue_26111", "tokennum": 335}], "negative_passages": []}
{"query_id": "q-en-kubernetes-60d573f37bcdd7e6396ea40e92bf155e97878cc820e5cb00e168464634b431da", "query": "\"os\" \"k8s.io/kubernetes/pkg/api\" <ins> \"k8s.io/kubernetes/pkg/api/meta\" </ins> \"k8s.io/kubernetes/pkg/api/unversioned\" \"k8s.io/kubernetes/pkg/apimachinery/registered\" \"k8s.io/kubernetes/pkg/kubectl\"", "positive_passages": [{"docid": "doc-en-kubernetes-e8aabcf3e5e99db1922665cc12fe15914953073d88b0bc68ff14545d188d9dd5", "text": "BUG REPORT When using with multiple files (like when referencing a directory in ), the json or yaml output is not a valid list format, and when fed to just the first file gets created. Kubernetes version (use ): latest master What happened: only the first file in directory gets created. What you expected to happen: all files in directory must be created. How to reproduce it (as minimally and precisely as possible):", "commid": "kubernetes_issue_36722", "tokennum": 92}], "negative_passages": []}
{"query_id": "q-en-kubernetes-60dcc1637cc784887d5b65d998c35a7579d0bcef58b8a0b3fd5395ab299864fa", "query": "} // DiskIsAttached returns if disk is attached to the VM using controllers supported by the plugin. <del> func (vs *VSphere) DiskIsAttached(volPath string, nodeName k8stypes.NodeName) (bool, error) { diskIsAttachedInternal := func(volPath string, nodeName k8stypes.NodeName) (bool, error) { </del> <ins> func (vs *VSphere) DiskIsAttached(volPath string, nodeName k8stypes.NodeName) (bool, string, error) { diskIsAttachedInternal := func(volPath string, nodeName k8stypes.NodeName) (bool, string, error) { </ins> var vSphereInstance string if nodeName == \"\" { vSphereInstance = vs.hostName", "positive_passages": [{"docid": "doc-en-kubernetes-e1df151812a738ca8d7e9f97519d671c643638f3ca9d9400cc430f5f7a7d204c", "text": "When user creates a static PV using folder name in path: on vSAN backed datastore then detach disk does not work because check fails - The code expects folder name to be UUID but it does not and hence it determines disk is not attached to the node and hence no detach is ever performed. /sig storage cc", "commid": "kubernetes_issue_95121", "tokennum": 68}], "negative_passages": []}
{"query_id": "q-en-kubernetes-60e5a96a572ecf008a23a9fe5c67e1cf774c180f4500ce77f61b78f75b085293", "query": "terminating := apiextensions.IsCRDConditionTrue(crd, apiextensions.Terminating) <del> crdInfo, err := r.getOrCreateServingInfoFor(crd) </del> <ins> crdInfo, err := r.getOrCreateServingInfoFor(crd.UID, crd.Name) if apierrors.IsNotFound(err) { r.delegate.ServeHTTP(w, req) return } </ins> if err != nil { http.Error(w, err.Error(), http.StatusInternalServerError) return } <ins> if !hasServedCRDVersion(crdInfo.spec, requestInfo.APIVersion) { r.delegate.ServeHTTP(w, req) return } </ins> verb := strings.ToUpper(requestInfo.Verb) resource := requestInfo.Resource", "positive_passages": [{"docid": "doc-en-kubernetes-16c95be4925a0d298a67709c93efbb137b71325e5e3041edcf306d6572e4ae65", "text": "Which jobs are failing: pull-kubernetes-integration Which test(s) are failing: TestWebhookConverterWithDefaulting /assign /priority important-soon /area custom-resources /sig api-machinery /kind flake /milestone v1.16\n/cc\nseveral of the webhook converter tests have similar flakes. it looks like the wait for storage version to become effective times out occasionally Rare flakes seen in all of these tests: TestWebhookConverterWithWatchCache/nontrivial-converter TestWebhookConverterWithWatchCache/metadata-mutating-converter TestWebhookConverterWithDefaulting/metadata-mutating-converter TestWebhookConverterWithWatchCache/noop-converter TestWebhookConverterWithDefaulting/empty-response TestWebhookConverterWithoutWatchCache/nontrivial-converter/check-2 TestWebhookConverterWithoutWatchCache/noop-converter/check-0/v1beta2 TestWebhookConverterWithoutWatchCache/nontrivial-converter/check-0/v1beta2\ncc\nYikes, I\u2019ll sort it out.\niiuc sending an empty patch gets short-circuited and doesn't bump CR generation, even if the storage version gets changed, which means we do not re-write to etcd and go through the encoding path this would be racing and doing noop's if the first pass of didn't get the expected storage version I will send a fix to make the patch do actual mutation\nIt doesn't bump generation, but the bytes to persist in etcd would still be different if the storage version had changed, so they should persist. You can verify that by changing the storage version on a CRD yourself, do an empty patch, and see if the resourceVersion changes.\nyou're right. Generation is for non-metadata change only, and the RV changes. I queried etcd locally and the apiVersion did change for an empty patch (sidetracking: another observation is after changing the storage version (say v1 -v2; noop convertor), empty-patching v2 endpoint would bump generation, while empty-patching v1 endpoint wouldn't)\nanother theory: our cached storage strategy could be stale if the CRD informer merges multiple events together (e.g. the informer does a re-list).", "commid": "kubernetes_issue_78913", "tokennum": 546}], "negative_passages": []}
{"query_id": "q-en-kubernetes-60e5a96a572ecf008a23a9fe5c67e1cf774c180f4500ce77f61b78f75b085293", "query": "terminating := apiextensions.IsCRDConditionTrue(crd, apiextensions.Terminating) <del> crdInfo, err := r.getOrCreateServingInfoFor(crd) </del> <ins> crdInfo, err := r.getOrCreateServingInfoFor(crd.UID, crd.Name) if apierrors.IsNotFound(err) { r.delegate.ServeHTTP(w, req) return } </ins> if err != nil { http.Error(w, err.Error(), http.StatusInternalServerError) return } <ins> if !hasServedCRDVersion(crdInfo.spec, requestInfo.APIVersion) { r.delegate.ServeHTTP(w, req) return } </ins> verb := strings.ToUpper(requestInfo.Verb) resource := requestInfo.Resource", "positive_passages": [{"docid": "doc-en-kubernetes-4d6bef5a272bfef04fa7527d92c495ee5b0e5d06d06a593b8089b98a3b84ddb9", "text": "Two scenarios: -create-update events merged into an update event: strategy with UID:a was created on demand for CRD Foo Foo was deleted and recreated strategy with UID:b was created on demand for the new Foo new Foo got updated (e.g. switching storage version) the strategy with UID:b is supposed to be deleted and , to reflect the last update. But if the CRD informer merges the delete-create-update events into , the strategy with UID:a will be deleted, but the strategy with UID:b won't. -update events merged into a create event: strategy with UID:a was created on demand for CRD Foo Foo was updated (e.g. switching storage version) the strategy with UID:a is supposed to be deleted and , to reflect the last update. But if the CRD informer merges the create-update events into , the strategy with UID:a won't be deleted (as we don't react on create events). another race found in , which could happen in a single update.\nI think I :", "commid": "kubernetes_issue_78913", "tokennum": 234}], "negative_passages": []}
{"query_id": "q-en-kubernetes-60edc5cdb535093766fc799fcbdc3badf1c4edae6eb182b7aca7d797b29d15b6", "query": "// Check that request <= limit. limitQuantity, exists := requirements.Limits[resourceName] if exists { <del> // For GPUs, not only requests can't exceed limits, they also can't be lower, i.e. must be equal. </del> <ins> // For non overcommitable resources, not only requests can't exceed limits, they also can't be lower, i.e. must be equal. </ins> if quantity.Cmp(limitQuantity) != 0 && !helper.IsOvercommitAllowed(resourceName) { allErrs = append(allErrs, field.Invalid(reqPath, quantity.String(), fmt.Sprintf(\"must be equal to %s limit\", resourceName))) } else if quantity.Cmp(limitQuantity) > 0 { allErrs = append(allErrs, field.Invalid(reqPath, quantity.String(), fmt.Sprintf(\"must be less than or equal to %s limit\", resourceName))) } <del> } else if resourceName == core.ResourceNvidiaGPU { allErrs = append(allErrs, field.Invalid(reqPath, quantity.String(), fmt.Sprintf(\"must be equal to %s request\", core.ResourceNvidiaGPU))) </del> <ins> } else if !helper.IsOvercommitAllowed(resourceName) { allErrs = append(allErrs, field.Required(limPath, \"Limit must be set for non overcommitable resources\")) </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-f35278f93af61e186544e4223e8223254ed1c96c2a29c22b72803675d1a55703", "text": "/kind bug /sig node /area hw-accelerators What happened: In devices are allocated from a function called . This function inspects only container resource limits, ignoring container resource requests. This is a usability problem because it is valid to omit limits for extended resources. If limit is omitted for a device resource, then the scheduler properly places the pod with respect to available node resources. However, the device manager never dispatches to the device plugin for that resource. The result is that the user application cannot access the requested device from inside the container. What you expected to happen: Following the documented behavior of extended resources, I expected that specifying a container resource request for a device would cause the device subsystem to properly configure access for my workload. How to reproduce it (as minimally and precisely as possible): Launch an alpha GKE cluster with GPU support enabled. Attempt to run any program that accesses the GPU from a container where the resource is specified in requests but omitted from limits. Environment: Kubernetes version (use ): v1.8+ Cloud provider or hardware configuration: device plugins enabled, devices available.\nRelated issue:\ncc\n/assign\nFYI. The said issue has been fixed in . There are several valid cases when requesting extended resources: The user can specify 'limits' only. The API server will automatically set 'requests' to be equal to 'limits'. The user specify 'limits' and 'requests', and they are equal. The user specify 'requests' only. We can either reject the request saying that 'limits' must be set, or implicitly treat 'limits' as equal to 'requests'.\nHi went with to begin since it was ready to go and smaller (easier to revert if necessary.) Hopefully it's easy to rebase your work on top of that. Sorry for the inconvenience.\nI feel the documented behavior is incorrect. The original intention was to always require for extended resources until we have better APIs to express bursting scenarios. I vote for fixing the documentation and fixing the validation logic and having kubelet use limits only.\n/reopen", "commid": "kubernetes_issue_57276", "tokennum": 447}], "negative_passages": []}
{"query_id": "q-en-kubernetes-60fbeb5986900225f6d38a6c035f1605a6dc560065c28816a49112704e5fdb22", "query": "return nil } <ins> func TestUpgradeServicePreferToDualStack(t *testing.T) { // Create an IPv4 only dual stack control-plane serviceCIDR := \"192.168.0.0/24\" defer featuregatetesting.SetFeatureGateDuringTest(t, utilfeature.DefaultFeatureGate, features.IPv6DualStack, true)() cfg := framework.NewIntegrationTestControlPlaneConfig() _, cidr, err := net.ParseCIDR(serviceCIDR) if err != nil { t.Fatalf(\"bad cidr: %v\", err) } cfg.ExtraConfig.ServiceIPRange = *cidr _, s, closeFn := framework.RunAnAPIServer(cfg) client := clientset.NewForConfigOrDie(&restclient.Config{Host: s.URL}) // Wait until the default \"kubernetes\" service is created. if err = wait.Poll(250*time.Millisecond, time.Minute, func() (bool, error) { _, err := client.CoreV1().Services(metav1.NamespaceDefault).Get(context.TODO(), \"kubernetes\", metav1.GetOptions{}) if err != nil && !apierrors.IsNotFound(err) { return false, err } return !apierrors.IsNotFound(err), nil }); err != nil { t.Fatalf(\"creating kubernetes service timed out\") } preferDualStack := v1.IPFamilyPolicyPreferDualStack svc := &v1.Service{ ObjectMeta: metav1.ObjectMeta{ Name: \"svc-prefer-dual\", }, Spec: v1.ServiceSpec{ Type:           v1.ServiceTypeClusterIP, ClusterIPs:     nil, IPFamilies:     nil, IPFamilyPolicy: &preferDualStack, Ports: []v1.ServicePort{ { Name:       \"svc-port-1\", Port:       443, TargetPort: intstr.IntOrString{IntVal: 443}, Protocol:   \"TCP\", }, }, }, } // create the service _, err = client.CoreV1().Services(metav1.NamespaceDefault).Create(context.TODO(), svc, metav1.CreateOptions{}) if err != nil { t.Fatalf(\"Unexpected error: %v\", err) } // validate the service was created correctly if it was not expected to fail svc, err = client.CoreV1().Services(metav1.NamespaceDefault).Get(context.TODO(), svc.Name, metav1.GetOptions{}) if err != nil { t.Fatalf(\"Unexpected error to get the service %s %v\", svc.Name, err) } if err := validateServiceAndClusterIPFamily(svc, []v1.IPFamily{v1.IPv4Protocol}); err != nil { t.Fatalf(\"Unexpected error validating the service %s %v\", svc.Name, err) } // reconfigure the apiserver to be dual-stack closeFn() secondaryServiceCIDR := \"2001:db8:1::/48\" _, secCidr, err := net.ParseCIDR(secondaryServiceCIDR) if err != nil { t.Fatalf(\"bad cidr: %v\", err) } cfg.ExtraConfig.SecondaryServiceIPRange = *secCidr _, s, closeFn = framework.RunAnAPIServer(cfg) defer closeFn() client = clientset.NewForConfigOrDie(&restclient.Config{Host: s.URL}) // Wait until the default \"kubernetes\" service is created. if err = wait.Poll(250*time.Millisecond, time.Minute, func() (bool, error) { _, err := client.CoreV1().Services(metav1.NamespaceDefault).Get(context.TODO(), \"kubernetes\", metav1.GetOptions{}) if err != nil && !apierrors.IsNotFound(err) { return false, err } return !apierrors.IsNotFound(err), nil }); err != nil { t.Fatalf(\"creating kubernetes service timed out\") } // validate the service was created correctly if it was not expected to fail svc, err = client.CoreV1().Services(metav1.NamespaceDefault).Get(context.TODO(), svc.Name, metav1.GetOptions{}) if err != nil { t.Fatalf(\"Unexpected error to get the service %s %v\", svc.Name, err) } // service should remain single stack if err = validateServiceAndClusterIPFamily(svc, []v1.IPFamily{v1.IPv4Protocol}); err != nil { t.Fatalf(\"Unexpected error validating the service %s %v\", svc.Name, err) } } func TestDowngradeServicePreferToDualStack(t *testing.T) { // Create a dual stack control-plane serviceCIDR := \"192.168.0.0/24\" secondaryServiceCIDR := \"2001:db8:1::/48\" defer featuregatetesting.SetFeatureGateDuringTest(t, utilfeature.DefaultFeatureGate, features.IPv6DualStack, true)() dualStackCfg := framework.NewIntegrationTestControlPlaneConfig() _, cidr, err := net.ParseCIDR(serviceCIDR) if err != nil { t.Fatalf(\"bad cidr: %v\", err) } dualStackCfg.ExtraConfig.ServiceIPRange = *cidr _, secCidr, err := net.ParseCIDR(secondaryServiceCIDR) if err != nil { t.Fatalf(\"bad cidr: %v\", err) } dualStackCfg.ExtraConfig.SecondaryServiceIPRange = *secCidr _, s, closeFn := framework.RunAnAPIServer(dualStackCfg) client := clientset.NewForConfigOrDie(&restclient.Config{Host: s.URL}) // Wait until the default \"kubernetes\" service is created. if err = wait.Poll(250*time.Millisecond, time.Minute, func() (bool, error) { _, err := client.CoreV1().Services(metav1.NamespaceDefault).Get(context.TODO(), \"kubernetes\", metav1.GetOptions{}) if err != nil && !apierrors.IsNotFound(err) { return false, err } return !apierrors.IsNotFound(err), nil }); err != nil { t.Fatalf(\"creating kubernetes service timed out\") } preferDualStack := v1.IPFamilyPolicyPreferDualStack svc := &v1.Service{ ObjectMeta: metav1.ObjectMeta{ Name: \"svc-prefer-dual01\", }, Spec: v1.ServiceSpec{ Type:           v1.ServiceTypeClusterIP, ClusterIPs:     nil, IPFamilies:     nil, IPFamilyPolicy: &preferDualStack, Ports: []v1.ServicePort{ { Name:       \"svc-port-1\", Port:       443, TargetPort: intstr.IntOrString{IntVal: 443}, Protocol:   \"TCP\", }, }, }, } // create the service _, err = client.CoreV1().Services(metav1.NamespaceDefault).Create(context.TODO(), svc, metav1.CreateOptions{}) if err != nil { t.Fatalf(\"Unexpected error: %v\", err) } // validate the service was created correctly if it was not expected to fail svc, err = client.CoreV1().Services(metav1.NamespaceDefault).Get(context.TODO(), svc.Name, metav1.GetOptions{}) if err != nil { t.Fatalf(\"Unexpected error to get the service %s %v\", svc.Name, err) } if err := validateServiceAndClusterIPFamily(svc, []v1.IPFamily{v1.IPv4Protocol, v1.IPv6Protocol}); err != nil { t.Fatalf(\"Unexpected error validating the service %s %v\", svc.Name, err) } // reconfigure the apiserver to be sinlge stack closeFn() // reset secondary var emptyCidr net.IPNet dualStackCfg.ExtraConfig.SecondaryServiceIPRange = emptyCidr _, s, closeFn = framework.RunAnAPIServer(dualStackCfg) defer closeFn() client = clientset.NewForConfigOrDie(&restclient.Config{Host: s.URL}) // Wait until the default \"kubernetes\" service is created. if err = wait.Poll(250*time.Millisecond, time.Minute, func() (bool, error) { _, err := client.CoreV1().Services(metav1.NamespaceDefault).Get(context.TODO(), \"kubernetes\", metav1.GetOptions{}) if err != nil && !apierrors.IsNotFound(err) { return false, err } return !apierrors.IsNotFound(err), nil }); err != nil { t.Fatalf(\"creating kubernetes service timed out\") } // validate the service is still there. svc, err = client.CoreV1().Services(metav1.NamespaceDefault).Get(context.TODO(), svc.Name, metav1.GetOptions{}) if err != nil { t.Fatalf(\"Unexpected error to get the service %s %v\", svc.Name, err) } // service should be single stack if err = validateServiceAndClusterIPFamily(svc, []v1.IPFamily{v1.IPv4Protocol, v1.IPv6Protocol}); err != nil { t.Fatalf(\"Unexpected error validating the service %s %v\", svc.Name, err) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-572d0164a11730b1ec949ed970afee14cdb12823b4b7a698fae66a86d82f748e", "text": "1) start with a single stack cluster 2) create a PreferDualStack service 3) configure API server with a 2nd service CIDR 4) Confirm the above service is not dual-stack 5) Add a label to the above service 6) Observe that the service becomes dual-stack I think the correct answer is to have a \"repair loop\" that upgrades (and downgrades!) PreferDualStack Services to match the config. I think this is a GA blocker.\n/triage accepted The current thought is: of type with are special new breed of api objects that I don't think we have any similar precedent in the apis, i could be wrong. Their behavior is tied to how the cluster is configured. Thus their behavior must change as the cluster behavior change. a way the user is stating . If it is cluster then i am good with two ClusterIPs. If it is single stack cluster then I am also good with a single ClusterIP. One can assume that if the user was ok was with getting a additional IP when possible then they must be ok with taking it away when it is no longer possible. Based on the above I believe best course of action is create a new repair loop or piggyback on any of the existing (or better: fix it in rest stack during list and get calls). The new logic takes care of matching to the .\nreproducer and regression test if somebody takes this, feel free to add it\nack - Scheduled to tackle 3rd week of May. Will definitely include that patch.", "commid": "kubernetes_issue_101681", "tokennum": 322}], "negative_passages": []}
{"query_id": "q-en-kubernetes-610be331e15420f5433b60ff8d2c504f7b27aa5012f7a95ae0374e9b600f3537", "query": "}) }) <ins> ginkgo.It(\"should ensure an IP overlapping both IPBlock.CIDR and IPBlock.Except is allowed [Feature:NetworkPolicy]\", func() { protocolUDP := v1.ProtocolUDP // Getting podServer's status to get podServer's IP, to create the CIDR with except clause podServerStatus, err := f.ClientSet.CoreV1().Pods(f.Namespace.Name).Get(context.TODO(), podServer.Name, metav1.GetOptions{}) if err != nil { framework.ExpectNoError(err, \"Error occurred while getting pod status.\") } podServerAllowCIDR := fmt.Sprintf(\"%s/24\", podServerStatus.Status.PodIP) podServerIP := fmt.Sprintf(\"%s/32\", podServerStatus.Status.PodIP) // Exclude podServer's IP with an Except clause podServerExceptList := []string{podServerIP} // Create NetworkPolicy which blocks access to podServer with except clause. policyAllowCIDRWithExceptServerPod := &networkingv1.NetworkPolicy{ ObjectMeta: metav1.ObjectMeta{ Namespace: f.Namespace.Name, Name:      \"deny-client-a-via-except-cidr-egress-rule\", }, Spec: networkingv1.NetworkPolicySpec{ // Apply this policy to the client. PodSelector: metav1.LabelSelector{ MatchLabels: map[string]string{ \"pod-name\": \"client-a\", }, }, PolicyTypes: []networkingv1.PolicyType{networkingv1.PolicyTypeEgress}, // Allow traffic to only one CIDR block except subnet which includes Server. Egress: []networkingv1.NetworkPolicyEgressRule{ { Ports: []networkingv1.NetworkPolicyPort{ // Allow DNS look-ups { Protocol: &protocolUDP, Port:     &intstr.IntOrString{Type: intstr.Int, IntVal: 53}, }, }, }, { To: []networkingv1.NetworkPolicyPeer{ { IPBlock: &networkingv1.IPBlock{ CIDR:   podServerAllowCIDR, Except: podServerExceptList, }, }, }, }, }, }, } policyAllowCIDRWithExceptServerPodObj, err := f.ClientSet.NetworkingV1().NetworkPolicies(f.Namespace.Name).Create(context.TODO(), policyAllowCIDRWithExceptServerPod, metav1.CreateOptions{}) framework.ExpectNoError(err, \"Error occurred while creating policy: policyAllowCIDRWithExceptServerPod.\") ginkgo.By(\"Creating client-a which should not be able to contact the server.\", func() { testCannotConnect(f, f.Namespace, \"client-a\", service, 80) }) // Create NetworkPolicy which allows access to the podServer using podServer's IP in allow CIDR. policyAllowCIDRServerPod := &networkingv1.NetworkPolicy{ ObjectMeta: metav1.ObjectMeta{ Namespace: f.Namespace.Name, Name:      \"allow-client-a-via-cidr-egress-rule\", }, Spec: networkingv1.NetworkPolicySpec{ // Apply this policy to the client. PodSelector: metav1.LabelSelector{ MatchLabels: map[string]string{ \"pod-name\": \"client-a\", }, }, PolicyTypes: []networkingv1.PolicyType{networkingv1.PolicyTypeEgress}, // Allow traffic to only one CIDR block which includes Server. Egress: []networkingv1.NetworkPolicyEgressRule{ { Ports: []networkingv1.NetworkPolicyPort{ // Allow DNS look-ups { Protocol: &protocolUDP, Port:     &intstr.IntOrString{Type: intstr.Int, IntVal: 53}, }, }, }, { To: []networkingv1.NetworkPolicyPeer{ { IPBlock: &networkingv1.IPBlock{ CIDR: podServerIP, }, }, }, }, }, }, } policyAllowCIDRServerPod, err = f.ClientSet.NetworkingV1().NetworkPolicies(f.Namespace.Name).Create(context.TODO(), policyAllowCIDRServerPod, metav1.CreateOptions{}) framework.ExpectNoError(err, \"Error occurred while creating policy: policyAllowCIDRServerPod.\") defer cleanupNetworkPolicy(f, policyAllowCIDRServerPod) ginkgo.By(\"Creating client-a which should now be able to contact the server.\", func() { testCanConnect(f, f.Namespace, \"client-a\", service, 80) }) ginkgo.By(\"Deleting the network policy with except podServer IP which disallows access to podServer.\") cleanupNetworkPolicy(f, policyAllowCIDRWithExceptServerPodObj) ginkgo.By(\"Creating client-a which should still be able to contact the server after deleting the network policy with except clause.\", func() { testCanConnect(f, f.Namespace, \"client-a\", service, 80) }) // Recreate the NetworkPolicy which contains the podServer's IP in the except list. policyAllowCIDRWithExceptServerPod, err = f.ClientSet.NetworkingV1().NetworkPolicies(f.Namespace.Name).Create(context.TODO(), policyAllowCIDRWithExceptServerPod, metav1.CreateOptions{}) framework.ExpectNoError(err, \"Error occurred while creating policy: policyAllowCIDRWithExceptServerPod.\") defer cleanupNetworkPolicy(f, policyAllowCIDRWithExceptServerPod) ginkgo.By(\"Creating client-a which should still be able to contact the server after recreating the network policy with except clause.\", func() { testCanConnect(f, f.Namespace, \"client-a\", service, 80) }) }) </ins> ginkgo.It(\"should enforce policies to check ingress and egress policies can be controlled independently based on PodSelector [Feature:NetworkPolicy]\", func() { var serviceA, serviceB *v1.Service var podA, podB *v1.Pod", "positive_passages": [{"docid": "doc-en-kubernetes-857a05f0056981db8f074277daa3916820903c2001d424633751ac4f757a1787", "text": "needs a test to ensure that clauses are implemented correctly. Specifically, that they are not implemented as \"deny\" rules. eg, given a client pod with IP , if you add a NetworkPolicy with: spec: ingress: from: ipBlock: cidr: 0.0.0.0/0 except: A.B.C.0/24 then it should block ingress from that pod. But if you then add a second policy with: spec: ingress: from: ipBlock: cidr: A.B.C.D/32 then it should reallow ingress from that pod. Then if you delete the first policy, ingress should still be allowed, and if you create the first policy again, ingress should still be allowed. (ie, the result does not depend on which order the two policies were created in). /sig network /priority important-longterm\nI can work on this as my first issue related to sig-network.\njust noticed this issue while working on a similar effort. since there was no activity for the past 2 months I pushed a PR for this scenario", "commid": "kubernetes_issue_83191", "tokennum": 236}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6112970c4a8d2d7086c631f704cab8c762d14fe080d9b66b81123df8de744fd8", "query": "<ins> /* Copyright 2017 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package util import ( \"os\" \"reflect\" \"strings\" \"testing\" \"time\" \"github.com/google/go-cmp/cmp\" v1 \"k8s.io/api/core/v1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" kubetypes \"k8s.io/apimachinery/pkg/types\" \"k8s.io/client-go/informers\" csitrans \"k8s.io/csi-translation-lib\" fakeframework \"k8s.io/kubernetes/pkg/scheduler/framework/fake\" \"k8s.io/kubernetes/pkg/volume/csimigration\" \"k8s.io/kubernetes/pkg/volume/fc\" utilfeature \"k8s.io/apiserver/pkg/util/feature\" \"k8s.io/client-go/kubernetes/fake\" utiltesting \"k8s.io/client-go/util/testing\" \"k8s.io/kubernetes/pkg/volume\" volumetest \"k8s.io/kubernetes/pkg/volume/testing\" ) const ( testHostName      = \"test-hostname\" socketPath        = \"/var/run/kmsplugin\" migratedVolume    = \"migrated-volume-name\" nonMigratedVolume = \"non-migrated-volume-name\" testNodeName      = \"test-node-name\" ) var ( dirOrCreate = v1.HostPathType(v1.HostPathDirectoryOrCreate) nodeName    = kubetypes.NodeName(testNodeName) hostPath    = &v1.HostPathVolumeSource{ Path: socketPath, Type: &dirOrCreate, } migratedObjectReference    = v1.ObjectReference{Namespace: \"default\", Name: \"migrated-pvc\"} nonMigratedObjectReference = v1.ObjectReference{Namespace: \"default\", Name: \"non-migrated-pvc\"} fsVolumeMode               = new(v1.PersistentVolumeMode) ) type vaTest struct { desc                 string createNodeName       kubetypes.NodeName pod                  *v1.Pod wantVolume           *v1.Volume wantPersistentVolume *v1.PersistentVolume wantErrorMessage     string } func Test_CreateVolumeSpec(t *testing.T) { for _, test := range []vaTest{ { desc:           \"inline volume type that does not support csi migration\", createNodeName: nodeName, pod: &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name:      \"kube-apiserver\", Namespace: \"default\", }, Spec: v1.PodSpec{ Volumes: []v1.Volume{ { Name: migratedVolume, VolumeSource: v1.VolumeSource{ HostPath: hostPath, }, }, }, }, }, wantVolume: &v1.Volume{ Name: migratedVolume, VolumeSource: v1.VolumeSource{ HostPath: hostPath, }, }, }, { desc:           \"inline volume type that supports csi migration\", createNodeName: nodeName, pod: &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name:      \"kube-apiserver\", Namespace: \"default\", }, Spec: v1.PodSpec{ Volumes: []v1.Volume{ { Name: migratedVolume, VolumeSource: v1.VolumeSource{ GCEPersistentDisk: &v1.GCEPersistentDiskVolumeSource{ PDName:    \"test-disk\", FSType:    \"ext4\", Partition: 0, ReadOnly:  false, }, }, }, }, }, }, wantPersistentVolume: &v1.PersistentVolume{ ObjectMeta: metav1.ObjectMeta{ Name: \"pd.csi.storage.gke.io-test-disk\", }, Spec: v1.PersistentVolumeSpec{ PersistentVolumeSource: v1.PersistentVolumeSource{ CSI: &v1.CSIPersistentVolumeSource{ Driver:           \"pd.csi.storage.gke.io\", VolumeHandle:     \"projects/UNSPECIFIED/zones/UNSPECIFIED/disks/test-disk\", FSType:           \"ext4\", ReadOnly:         false, VolumeAttributes: map[string]string{\"partition\": \"\"}, }, }, AccessModes: []v1.PersistentVolumeAccessMode{\"ReadWriteOnce\"}, VolumeMode:  fsVolumeMode, }, }, }, { desc:           \"pv type that does not support csi migration\", createNodeName: nodeName, pod: &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name:      \"kube-apiserver\", Namespace: \"default\", }, Spec: v1.PodSpec{ Volumes: []v1.Volume{ { Name: nonMigratedVolume, VolumeSource: v1.VolumeSource{ PersistentVolumeClaim: &v1.PersistentVolumeClaimVolumeSource{ ClaimName: \"non-migrated-pvc\", ReadOnly:  false, }, }, }, }, }, }, wantPersistentVolume: &v1.PersistentVolume{ ObjectMeta: metav1.ObjectMeta{ Name: nonMigratedVolume, }, Spec: v1.PersistentVolumeSpec{ PersistentVolumeSource: v1.PersistentVolumeSource{ ScaleIO: &v1.ScaleIOPersistentVolumeSource{}, }, ClaimRef: &nonMigratedObjectReference, }, }, }, { desc:           \"pv type that supports csi migration\", createNodeName: nodeName, pod: &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name:      \"kube-apiserver\", Namespace: \"default\", }, Spec: v1.PodSpec{ Volumes: []v1.Volume{ { Name: migratedVolume, VolumeSource: v1.VolumeSource{ PersistentVolumeClaim: &v1.PersistentVolumeClaimVolumeSource{ ClaimName: \"migrated-pvc\", ReadOnly:  false, }, }, }, }, }, }, wantPersistentVolume: &v1.PersistentVolume{ ObjectMeta: metav1.ObjectMeta{ Name: migratedVolume, }, Spec: v1.PersistentVolumeSpec{ PersistentVolumeSource: v1.PersistentVolumeSource{ CSI: &v1.CSIPersistentVolumeSource{ Driver:           \"pd.csi.storage.gke.io\", VolumeHandle:     \"projects/UNSPECIFIED/zones/UNSPECIFIED/disks/test-disk\", FSType:           \"ext4\", ReadOnly:         false, VolumeAttributes: map[string]string{\"partition\": \"\"}, }, }, ClaimRef: &migratedObjectReference, }, }, }, { desc:           \"CSINode not found for a volume type that supports csi migration\", createNodeName: kubetypes.NodeName(\"another-node\"), pod: &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name:      \"kube-apiserver\", Namespace: \"default\", }, Spec: v1.PodSpec{ Volumes: []v1.Volume{ { Name: migratedVolume, VolumeSource: v1.VolumeSource{ PersistentVolumeClaim: &v1.PersistentVolumeClaimVolumeSource{ ClaimName: \"migrated-pvc\", ReadOnly:  false, }, }, }, }, }, }, wantErrorMessage: \"csiNode \"another-node\" not found\", }, } { t.Run(test.desc, func(t *testing.T) { plugMgr, intreeToCSITranslator, csiTranslator, pvLister, pvcLister := setup(testNodeName, t) actualSpec, err := CreateVolumeSpec(test.pod.Spec.Volumes[0], test.pod, test.createNodeName, plugMgr, pvcLister, pvLister, intreeToCSITranslator, csiTranslator) if actualSpec == nil && (test.wantPersistentVolume != nil || test.wantVolume != nil) { t.Errorf(\"got volume spec is nil\") } if (len(test.wantErrorMessage) > 0 && err == nil) || (err != nil && !strings.Contains(err.Error(), test.wantErrorMessage)) { t.Errorf(\"got err %v, want err with message %v\", err, test.wantErrorMessage) } if test.wantPersistentVolume != nil { if actualSpec.PersistentVolume == nil { t.Errorf(\"gotVolumeWithCSIMigration is nil\") } gotVolumeWithCSIMigration := *actualSpec.PersistentVolume if gotVolumeWithCSIMigration.Name != test.wantPersistentVolume.Name { t.Errorf(\"got volume name is %v, want volume name is %v\", gotVolumeWithCSIMigration.Name, test.wantPersistentVolume.Name) } if !reflect.DeepEqual(gotVolumeWithCSIMigration.Spec, test.wantPersistentVolume.Spec) { t.Errorf(\"got volume.Spec and want.Spec diff is %s\", cmp.Diff(gotVolumeWithCSIMigration.Spec, test.wantPersistentVolume.Spec)) } } if test.wantVolume != nil { if actualSpec.Volume == nil { t.Errorf(\"gotVolume is nil\") } gotVolume := *actualSpec.Volume if !reflect.DeepEqual(gotVolume, *test.wantVolume) { t.Errorf(\"got volume and want diff is %s\", cmp.Diff(gotVolume, test.wantVolume)) } } }) } } func setup(nodeName string, t *testing.T) (*volume.VolumePluginMgr, csimigration.PluginManager, csitrans.CSITranslator, fakeframework.PersistentVolumeLister, fakeframework.PersistentVolumeClaimLister) { tmpDir, err := utiltesting.MkTmpdir(\"csi-test\") if err != nil { t.Fatalf(\"can't make a temp dir: %v\", err) } defer os.RemoveAll(tmpDir) *fsVolumeMode = v1.PersistentVolumeFilesystem csiTranslator := csitrans.New() intreeToCSITranslator := csimigration.NewPluginManager(csiTranslator, utilfeature.DefaultFeatureGate) kubeClient := fake.NewSimpleClientset() factory := informers.NewSharedInformerFactory(kubeClient, time.Minute) csiDriverInformer := factory.Storage().V1().CSIDrivers() csiDriverLister := csiDriverInformer.Lister() volumeAttachmentInformer := factory.Storage().V1().VolumeAttachments() volumeAttachmentLister := volumeAttachmentInformer.Lister() plugMgr := &volume.VolumePluginMgr{} fakeAttachDetachVolumeHost := volumetest.NewFakeAttachDetachVolumeHostWithCSINodeName(t, tmpDir, kubeClient, fc.ProbeVolumePlugins(), nodeName, csiDriverLister, volumeAttachmentLister, ) plugMgr.Host = fakeAttachDetachVolumeHost pvLister := fakeframework.PersistentVolumeLister{ { ObjectMeta: metav1.ObjectMeta{Name: migratedVolume}, Spec: v1.PersistentVolumeSpec{ PersistentVolumeSource: v1.PersistentVolumeSource{ GCEPersistentDisk: &v1.GCEPersistentDiskVolumeSource{ PDName:    \"test-disk\", FSType:    \"ext4\", Partition: 0, ReadOnly:  false, }, }, ClaimRef: &migratedObjectReference, }, }, { ObjectMeta: metav1.ObjectMeta{Name: nonMigratedVolume}, Spec: v1.PersistentVolumeSpec{ PersistentVolumeSource: v1.PersistentVolumeSource{ ScaleIO: &v1.ScaleIOPersistentVolumeSource{}, }, ClaimRef: &nonMigratedObjectReference, }, }, } pvcLister := fakeframework.PersistentVolumeClaimLister{ { ObjectMeta: metav1.ObjectMeta{Name: \"migrated-pvc\", Namespace: \"default\"}, Spec:       v1.PersistentVolumeClaimSpec{VolumeName: migratedVolume}, Status: v1.PersistentVolumeClaimStatus{ Phase: v1.ClaimBound, }, }, { ObjectMeta: metav1.ObjectMeta{Name: \"non-migrated-pvc\", Namespace: \"default\"}, Spec:       v1.PersistentVolumeClaimSpec{VolumeName: nonMigratedVolume}, Status: v1.PersistentVolumeClaimStatus{ Phase: v1.ClaimBound, }, }, } return plugMgr, intreeToCSITranslator, csiTranslator, pvLister, pvcLister } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-43fa70370952068e2f27033c41492113945a1e0b0ce47a43a47f5065969f2aa7", "text": "After the cluster was updated to enable PD CSI Driver, there was a race condition where AD Controller (kube-controller-manager) started to BEFORE the PD CSI Driver was up, thus AD Controller gave us the error Then AD Controller triggered the disk detach because the disk/volume was not populated in the desired state of world. Unfortunately the disk was in use during this detach and got corrupted. Since cluster upgrades can cause the controller manager and CSI drivers to start at different times, the AD controller needs to be more conservative when detaching We have not been able to reproduce this, it came up from a customer. /sig storage /assign <detailsk8s 1.23, CSI migration enabled </details<detailsGKE </details<details</details<details</details<details</details<details</details\n/triage accepted\nI think there's potentially two changes we should do: 1) for the initial DSW population, we should skip the check that if the csi driver is not installed. 2) in general, we should not skip volumes during dsw initial population if an error is returned. If we had some temporary api server error then that would cause volumes to not get to dsw and similar behavior happen. cc\nfor a repro, maybe you can try something like: a cluster with csi migration enabled (control plane + nodes) a pod with intree-volume and get it running the csi driver node daemonset. verify the driver is removed from CSINode kube-controller-manager\ncc\n/cc was trying to repro this, but on GKE with the managed driver which made it complicated.\nYeah maybe gce kube-up would be easier for a repro\nIf CSINode says that it has migrated GCP PD volume plugin to CSI, then IMO A/D controller should always attach GCP PD volumes to it using CSI, regardless if the CSI driver is present or not. In-tree volume plugin in the kubelet is disabled and can't mount any in-tree volumes anyway. To flip the migration feature gate / upgrade / downgrade kubelet, the cluster admin must drain the node first to make sure everything is detached. A/D controller should not see change of CSINode migration annotations with any volume attached to it.\n/priority important-soon\nAnother option could be to process these volumes anyways but add them to DSOW with migration status as \"uncertain\", so as they can be re-processed later.", "commid": "kubernetes_issue_115297", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6112970c4a8d2d7086c631f704cab8c762d14fe080d9b66b81123df8de744fd8", "query": "<ins> /* Copyright 2017 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package util import ( \"os\" \"reflect\" \"strings\" \"testing\" \"time\" \"github.com/google/go-cmp/cmp\" v1 \"k8s.io/api/core/v1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" kubetypes \"k8s.io/apimachinery/pkg/types\" \"k8s.io/client-go/informers\" csitrans \"k8s.io/csi-translation-lib\" fakeframework \"k8s.io/kubernetes/pkg/scheduler/framework/fake\" \"k8s.io/kubernetes/pkg/volume/csimigration\" \"k8s.io/kubernetes/pkg/volume/fc\" utilfeature \"k8s.io/apiserver/pkg/util/feature\" \"k8s.io/client-go/kubernetes/fake\" utiltesting \"k8s.io/client-go/util/testing\" \"k8s.io/kubernetes/pkg/volume\" volumetest \"k8s.io/kubernetes/pkg/volume/testing\" ) const ( testHostName      = \"test-hostname\" socketPath        = \"/var/run/kmsplugin\" migratedVolume    = \"migrated-volume-name\" nonMigratedVolume = \"non-migrated-volume-name\" testNodeName      = \"test-node-name\" ) var ( dirOrCreate = v1.HostPathType(v1.HostPathDirectoryOrCreate) nodeName    = kubetypes.NodeName(testNodeName) hostPath    = &v1.HostPathVolumeSource{ Path: socketPath, Type: &dirOrCreate, } migratedObjectReference    = v1.ObjectReference{Namespace: \"default\", Name: \"migrated-pvc\"} nonMigratedObjectReference = v1.ObjectReference{Namespace: \"default\", Name: \"non-migrated-pvc\"} fsVolumeMode               = new(v1.PersistentVolumeMode) ) type vaTest struct { desc                 string createNodeName       kubetypes.NodeName pod                  *v1.Pod wantVolume           *v1.Volume wantPersistentVolume *v1.PersistentVolume wantErrorMessage     string } func Test_CreateVolumeSpec(t *testing.T) { for _, test := range []vaTest{ { desc:           \"inline volume type that does not support csi migration\", createNodeName: nodeName, pod: &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name:      \"kube-apiserver\", Namespace: \"default\", }, Spec: v1.PodSpec{ Volumes: []v1.Volume{ { Name: migratedVolume, VolumeSource: v1.VolumeSource{ HostPath: hostPath, }, }, }, }, }, wantVolume: &v1.Volume{ Name: migratedVolume, VolumeSource: v1.VolumeSource{ HostPath: hostPath, }, }, }, { desc:           \"inline volume type that supports csi migration\", createNodeName: nodeName, pod: &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name:      \"kube-apiserver\", Namespace: \"default\", }, Spec: v1.PodSpec{ Volumes: []v1.Volume{ { Name: migratedVolume, VolumeSource: v1.VolumeSource{ GCEPersistentDisk: &v1.GCEPersistentDiskVolumeSource{ PDName:    \"test-disk\", FSType:    \"ext4\", Partition: 0, ReadOnly:  false, }, }, }, }, }, }, wantPersistentVolume: &v1.PersistentVolume{ ObjectMeta: metav1.ObjectMeta{ Name: \"pd.csi.storage.gke.io-test-disk\", }, Spec: v1.PersistentVolumeSpec{ PersistentVolumeSource: v1.PersistentVolumeSource{ CSI: &v1.CSIPersistentVolumeSource{ Driver:           \"pd.csi.storage.gke.io\", VolumeHandle:     \"projects/UNSPECIFIED/zones/UNSPECIFIED/disks/test-disk\", FSType:           \"ext4\", ReadOnly:         false, VolumeAttributes: map[string]string{\"partition\": \"\"}, }, }, AccessModes: []v1.PersistentVolumeAccessMode{\"ReadWriteOnce\"}, VolumeMode:  fsVolumeMode, }, }, }, { desc:           \"pv type that does not support csi migration\", createNodeName: nodeName, pod: &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name:      \"kube-apiserver\", Namespace: \"default\", }, Spec: v1.PodSpec{ Volumes: []v1.Volume{ { Name: nonMigratedVolume, VolumeSource: v1.VolumeSource{ PersistentVolumeClaim: &v1.PersistentVolumeClaimVolumeSource{ ClaimName: \"non-migrated-pvc\", ReadOnly:  false, }, }, }, }, }, }, wantPersistentVolume: &v1.PersistentVolume{ ObjectMeta: metav1.ObjectMeta{ Name: nonMigratedVolume, }, Spec: v1.PersistentVolumeSpec{ PersistentVolumeSource: v1.PersistentVolumeSource{ ScaleIO: &v1.ScaleIOPersistentVolumeSource{}, }, ClaimRef: &nonMigratedObjectReference, }, }, }, { desc:           \"pv type that supports csi migration\", createNodeName: nodeName, pod: &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name:      \"kube-apiserver\", Namespace: \"default\", }, Spec: v1.PodSpec{ Volumes: []v1.Volume{ { Name: migratedVolume, VolumeSource: v1.VolumeSource{ PersistentVolumeClaim: &v1.PersistentVolumeClaimVolumeSource{ ClaimName: \"migrated-pvc\", ReadOnly:  false, }, }, }, }, }, }, wantPersistentVolume: &v1.PersistentVolume{ ObjectMeta: metav1.ObjectMeta{ Name: migratedVolume, }, Spec: v1.PersistentVolumeSpec{ PersistentVolumeSource: v1.PersistentVolumeSource{ CSI: &v1.CSIPersistentVolumeSource{ Driver:           \"pd.csi.storage.gke.io\", VolumeHandle:     \"projects/UNSPECIFIED/zones/UNSPECIFIED/disks/test-disk\", FSType:           \"ext4\", ReadOnly:         false, VolumeAttributes: map[string]string{\"partition\": \"\"}, }, }, ClaimRef: &migratedObjectReference, }, }, }, { desc:           \"CSINode not found for a volume type that supports csi migration\", createNodeName: kubetypes.NodeName(\"another-node\"), pod: &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name:      \"kube-apiserver\", Namespace: \"default\", }, Spec: v1.PodSpec{ Volumes: []v1.Volume{ { Name: migratedVolume, VolumeSource: v1.VolumeSource{ PersistentVolumeClaim: &v1.PersistentVolumeClaimVolumeSource{ ClaimName: \"migrated-pvc\", ReadOnly:  false, }, }, }, }, }, }, wantErrorMessage: \"csiNode \"another-node\" not found\", }, } { t.Run(test.desc, func(t *testing.T) { plugMgr, intreeToCSITranslator, csiTranslator, pvLister, pvcLister := setup(testNodeName, t) actualSpec, err := CreateVolumeSpec(test.pod.Spec.Volumes[0], test.pod, test.createNodeName, plugMgr, pvcLister, pvLister, intreeToCSITranslator, csiTranslator) if actualSpec == nil && (test.wantPersistentVolume != nil || test.wantVolume != nil) { t.Errorf(\"got volume spec is nil\") } if (len(test.wantErrorMessage) > 0 && err == nil) || (err != nil && !strings.Contains(err.Error(), test.wantErrorMessage)) { t.Errorf(\"got err %v, want err with message %v\", err, test.wantErrorMessage) } if test.wantPersistentVolume != nil { if actualSpec.PersistentVolume == nil { t.Errorf(\"gotVolumeWithCSIMigration is nil\") } gotVolumeWithCSIMigration := *actualSpec.PersistentVolume if gotVolumeWithCSIMigration.Name != test.wantPersistentVolume.Name { t.Errorf(\"got volume name is %v, want volume name is %v\", gotVolumeWithCSIMigration.Name, test.wantPersistentVolume.Name) } if !reflect.DeepEqual(gotVolumeWithCSIMigration.Spec, test.wantPersistentVolume.Spec) { t.Errorf(\"got volume.Spec and want.Spec diff is %s\", cmp.Diff(gotVolumeWithCSIMigration.Spec, test.wantPersistentVolume.Spec)) } } if test.wantVolume != nil { if actualSpec.Volume == nil { t.Errorf(\"gotVolume is nil\") } gotVolume := *actualSpec.Volume if !reflect.DeepEqual(gotVolume, *test.wantVolume) { t.Errorf(\"got volume and want diff is %s\", cmp.Diff(gotVolume, test.wantVolume)) } } }) } } func setup(nodeName string, t *testing.T) (*volume.VolumePluginMgr, csimigration.PluginManager, csitrans.CSITranslator, fakeframework.PersistentVolumeLister, fakeframework.PersistentVolumeClaimLister) { tmpDir, err := utiltesting.MkTmpdir(\"csi-test\") if err != nil { t.Fatalf(\"can't make a temp dir: %v\", err) } defer os.RemoveAll(tmpDir) *fsVolumeMode = v1.PersistentVolumeFilesystem csiTranslator := csitrans.New() intreeToCSITranslator := csimigration.NewPluginManager(csiTranslator, utilfeature.DefaultFeatureGate) kubeClient := fake.NewSimpleClientset() factory := informers.NewSharedInformerFactory(kubeClient, time.Minute) csiDriverInformer := factory.Storage().V1().CSIDrivers() csiDriverLister := csiDriverInformer.Lister() volumeAttachmentInformer := factory.Storage().V1().VolumeAttachments() volumeAttachmentLister := volumeAttachmentInformer.Lister() plugMgr := &volume.VolumePluginMgr{} fakeAttachDetachVolumeHost := volumetest.NewFakeAttachDetachVolumeHostWithCSINodeName(t, tmpDir, kubeClient, fc.ProbeVolumePlugins(), nodeName, csiDriverLister, volumeAttachmentLister, ) plugMgr.Host = fakeAttachDetachVolumeHost pvLister := fakeframework.PersistentVolumeLister{ { ObjectMeta: metav1.ObjectMeta{Name: migratedVolume}, Spec: v1.PersistentVolumeSpec{ PersistentVolumeSource: v1.PersistentVolumeSource{ GCEPersistentDisk: &v1.GCEPersistentDiskVolumeSource{ PDName:    \"test-disk\", FSType:    \"ext4\", Partition: 0, ReadOnly:  false, }, }, ClaimRef: &migratedObjectReference, }, }, { ObjectMeta: metav1.ObjectMeta{Name: nonMigratedVolume}, Spec: v1.PersistentVolumeSpec{ PersistentVolumeSource: v1.PersistentVolumeSource{ ScaleIO: &v1.ScaleIOPersistentVolumeSource{}, }, ClaimRef: &nonMigratedObjectReference, }, }, } pvcLister := fakeframework.PersistentVolumeClaimLister{ { ObjectMeta: metav1.ObjectMeta{Name: \"migrated-pvc\", Namespace: \"default\"}, Spec:       v1.PersistentVolumeClaimSpec{VolumeName: migratedVolume}, Status: v1.PersistentVolumeClaimStatus{ Phase: v1.ClaimBound, }, }, { ObjectMeta: metav1.ObjectMeta{Name: \"non-migrated-pvc\", Namespace: \"default\"}, Spec:       v1.PersistentVolumeClaimSpec{VolumeName: nonMigratedVolume}, Status: v1.PersistentVolumeClaimStatus{ Phase: v1.ClaimBound, }, }, } return plugMgr, intreeToCSITranslator, csiTranslator, pvLister, pvcLister } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-8286ec57fa1e024ad026b2342f466cffd200140a0a95c9b64ae688331c52eb45", "text": "But surely it looks like might be easiest unless it has any downsides.\nThere wasn't a node update in this case---there was a control plane update which restarted the PD CSI driver, and it looks like the CSIDriver resource was updated or changed in some way which raced with the kube-controller-manager restart.\nIs there anyway we can know if the csi driver is up and running(like a health check ping) before populating DSW?\nWe use the CSINode registration to determine that. The discussion here I think is concluding that we should not use that as a criteria for adding the volume to DSW. We only need to check that CSI migration is enabled on the node.\n+1 we need to be very resilient against races, I think we have to assume a driver is in process of being installed at any point in the AD controller reconcilliation.\n/assign sunnylovestiramisu\nReproduced with the steps: In /var/log/kube-controller-\nTested with the and doing the reproduce steps above. The error of does not show up anymore. The error message still get logged in the kube-controller- for debugging purpose: Ran Ran On the GCP console, the disk is used by node: Ran I redeploy the pd-csi-driver and then make sure it is up and running. Ran", "commid": "kubernetes_issue_115297", "tokennum": 285}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6128cfaf4c3226ef11f674132f21b82019e864368030657127fda3144fef4d48", "query": "} func (mounter *Mounter) IsNotMountPoint(dir string) (bool, error) { <del> return IsNotMountPoint(mounter, dir) </del> <ins> return isNotMountPoint(mounter, dir) </ins> } // IsLikelyNotMountPoint determines if a directory is not a mountpoint.", "positive_passages": [{"docid": "doc-en-kubernetes-4bcfc015d2b9d9fa1e84475a3e08fb9ef8299b4e5f821f790188ad7bdae6ecbc", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: There's , and . The former is used by local and nfs volume plugins, while the latter is used by , which is also used by local and nfs volume plugins. What you expected to happen: Can we consolidate these? This is really confusing and could easily be the source of bugs. <!-- DO NOT EDIT BELOW THIS LINE --/kind cleanup\ncc\n/assign I'd like to clean up code.", "commid": "kubernetes_issue_72387", "tokennum": 133}], "negative_passages": []}
{"query_id": "q-en-kubernetes-61415bafbee1f3900c047dc4a6f3f444ef6b750ec57aea4185625695bb0cdd22", "query": "test/e2e/network/service_latency.go: \"should not be very high\" test/e2e/node/events.go: \"should be sent by kubelets and the scheduler about pods scheduling and running\" test/e2e/node/pods.go: \"should be submitted and removed\" <ins> test/e2e/node/pods.go: \"should be submitted and removed\" </ins> test/e2e/node/pre_stop.go: \"should call prestop when killing a pod\" test/e2e/scheduling/predicates.go: \"validates resource limits of pods that are allowed to run\" test/e2e/scheduling/predicates.go: \"validates that NodeSelector is respected if not matching\"", "positive_passages": [{"docid": "doc-en-kubernetes-30eea2f2891480afb1ab3afc376d0efcc64938c80ac22e3ecb844909d4b7762a", "text": "We need to fix this potentially flaky test and add it back to conformance suite. Please see discussion in Also waiting on:\ncc /sig testing\n/area conformance\n/cc\nIssues 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\n/remove-lifecycle stale\ncan we convert it to conformance now??\nOnce 1.15 opens up", "commid": "kubernetes_issue_68066", "tokennum": 132}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6150af03b9e0f817a431a4b69b94027c27054a5e1531378c67ab759852edd1ed", "query": "if [[ \"${KUBE_PROXY_DAEMONSET:-}\" == \"true\" && \"${master}\" != \"true\" ]]; then # Add kube-proxy daemonset label to node to avoid situation during cluster # upgrade/downgrade when there are two instances of kube-proxy running on a node. <del> # TODO(liggitt): drop beta.kubernetes.io/kube-proxy-ds-ready in 1.16 node_labels=\"node.kubernetes.io/kube-proxy-ds-ready=true,beta.kubernetes.io/kube-proxy-ds-ready=true\" </del> <ins> node_labels=\"node.kubernetes.io/kube-proxy-ds-ready=true\" </ins> fi if [[ -n \"${NODE_LABELS:-}\" ]]; then node_labels=\"${node_labels:+${node_labels},}${NODE_LABELS}\"", "positive_passages": [{"docid": "doc-en-kubernetes-2c9ef8984ebaf899659836b925069334113c910fc47ebe0516a7d659674f044a", "text": "xref In 1.16: change the metadata-proxy addon to use change the kube-proxy addon to use change the masq-agent addon to use stop setting , , and in kube-up\nHey I'm trying to start to contribute to kubernetes and this seem to be an easy task. Can I help with this one?", "commid": "kubernetes_issue_75050", "tokennum": 77}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6169c65d978fc6a2e238e109788e84fb88d52be183ec3fe3690447d850117f86", "query": "execAffinityTestForLBService(f, cs, svc) }) <del> // TODO: Get rid of [DisabledForLargeClusters] tag when issue #56138 is fixed. </del> // [LinuxOnly]: Windows does not support session affinity. <del> ginkgo.It(\"should be able to switch session affinity for LoadBalancer service with ESIPP on [Slow] [DisabledForLargeClusters] [LinuxOnly]\", func() { </del> <ins> ginkgo.It(\"should be able to switch session affinity for LoadBalancer service with ESIPP on [Slow] [LinuxOnly]\", func() { </ins> // L4 load balancer affinity `ClientIP` is not supported on AWS ELB. e2eskipper.SkipIfProviderIs(\"aws\")", "positive_passages": [{"docid": "doc-en-kubernetes-23d2f241356f8f089aacd04cb02b22714ea2023d38ddcb3dae2268a8e3824c6f", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug This is a followup from filed separately now that we're not tracking this as part of 1.9 release. The tests have been disabled with [DisabledForLargeClusters] tag for now, and this fact will be mentioned in the scalability validation report for v1.9. This issue tracks fixing the test so the tag can be removed and the test ran again in the large cluster. /assign /kind e2e-test-failure\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIs this e2e test still broken?\nSorry for the confusion here. Currently this e2e test is disabled on extra large cluster due to some scalability issues with the load balancer related components. At the moment the issues haven't been completely resolved yet.\nok, adding priority so that I know it's not a 1.13 blocker. /priority important-longterm\ncc - this is why the relevant tests for are not part of the e2e suite.\nThis issue is still valid --- some action items on top of my head: Figure out a plan to make service controller properly handle operations in parallel. Check on the status for cloud providers (especially GCP, which the test ran against) on handling large number of nodes as LB backends. /remove-triage unresolved\nIssues 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 .", "commid": "kubernetes_issue_56138", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6169c65d978fc6a2e238e109788e84fb88d52be183ec3fe3690447d850117f86", "query": "execAffinityTestForLBService(f, cs, svc) }) <del> // TODO: Get rid of [DisabledForLargeClusters] tag when issue #56138 is fixed. </del> // [LinuxOnly]: Windows does not support session affinity. <del> ginkgo.It(\"should be able to switch session affinity for LoadBalancer service with ESIPP on [Slow] [DisabledForLargeClusters] [LinuxOnly]\", func() { </del> <ins> ginkgo.It(\"should be able to switch session affinity for LoadBalancer service with ESIPP on [Slow] [LinuxOnly]\", func() { </ins> // L4 load balancer affinity `ClientIP` is not supported on AWS ELB. e2eskipper.SkipIfProviderIs(\"aws\")", "positive_passages": [{"docid": "doc-en-kubernetes-82e0e423f6c651003322d5e3ca8baa34b91f0522dd0c015fbde1e81f949704e6", "text": "/lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten /lifecycle frozen\n/reopen Reopening as is being reverted in\nReopened this issue. <detailsIn response to : /reopen Reopening as is being reverted in 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\nthese tests are flaking in xref\ncc since these were enabled by\nYeah - though these failures doesn't seem to be scale related, they seem to be test related to me. This basically means nodes without public ips: It's pretty much the same thing as (just for a different test). should be addressing these kinds of errors. [Not a release blocker for sure]\nBTW - has been opened directly for this one.\n... so since is closed, Can we close this and re-enable for large clusters ? (i.e. remove the Tag in that disables this test) ? I'm not up to speed on the history but 2 related notes I came across digging into related test today... 's a couple of TODOs in the code referencing this specific issue, but your above direct issue is now closed, so we can close this as well right?... And if so, we can remove the TODO on the test... -enabling the test ... not sure wether the timing is good right now (given that is open right now , which sparked my stumbling upon this issue :))\nWe tried to enable all of them and that caused us a bunch of issues and those had to be reverted: A couple tests were enabled later in: and those seem fine. The remaining (mostly session-affinity ones) had some issue, which so far we didn't have time to debug and I haven't heard a good explanation why those were failing. It's possible that they were improved with , but I doubt those would really cause the failures we've seen in the past. So until this is debugged (or at least understood) I'm reluctant to enabling them.", "commid": "kubernetes_issue_56138", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-61722917cc54b129eb3ae88be836ae5a09d7db29f43158ccee47e93f0e5156f6", "query": "// api.Registry.GroupOrDie(v1.GroupName).GroupVersions[0].String() is changed // to \"v1\"? <del> runtimeapi \"k8s.io/cri-api/pkg/apis/runtime/v1alpha2\" </del> _ \"k8s.io/kubernetes/pkg/apis/core/install\" \"k8s.io/kubernetes/pkg/features\" kubecontainer \"k8s.io/kubernetes/pkg/kubelet/container\"", "positive_passages": [{"docid": "doc-en-kubernetes-59e10ac9f842c5137d16434532387dd09ba10f619a9264b3e368e8bd51bb44b7", "text": "What happened: It's most visible in the test <img width=\"323\" alt=\"Screen Shot 2020-05-20 at 6 09 10 PM\" src=\"https://user-\"It shows up in kind, kube- and kops jobs The regression was introduced somewhere within , possible culprits are: (FYI (FYI (FYI There are more tests affected, just not as prominently (visually inspecting ) [sig-apps] StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications with PVCs [sig-apps] StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance] [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Inline-volume (default fs)] volumes should store data [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data I wasn't sure whether to tag this as kind/regression or not, I'll leave that up to or someone /sig node /sig api-machimery /sig scheduling\nThe label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : What happened: It's most visible in the test (FYI (FYI (FYI StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications with PVCs [sig-apps] StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance] [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Inline-volume (default fs)] volumes should store data [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data /sig api-machimery /sig scheduling 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.", "commid": "kubernetes_issue_91316", "tokennum": 506}], "negative_passages": []}
{"query_id": "q-en-kubernetes-61722917cc54b129eb3ae88be836ae5a09d7db29f43158ccee47e93f0e5156f6", "query": "// api.Registry.GroupOrDie(v1.GroupName).GroupVersions[0].String() is changed // to \"v1\"? <del> runtimeapi \"k8s.io/cri-api/pkg/apis/runtime/v1alpha2\" </del> _ \"k8s.io/kubernetes/pkg/apis/core/install\" \"k8s.io/kubernetes/pkg/features\" kubecontainer \"k8s.io/kubernetes/pkg/kubelet/container\"", "positive_passages": [{"docid": "doc-en-kubernetes-aa1ca8a6c4f552108d5e4f5627cf5341a0bb7748f7b82e510f647cbc02b0a76b", "text": "</details\n/cc\nwill increase the time for deletion of pod and it should be expected because currently pod is deleted from apiserver before removing the sandbox container but after this fix pod will be deleted from the apiserver only after deleting the sandbox container.\n/remove-sig scheduling doesn't affect scheduling running time at all.\nYeah, is almost definitely the culprit. Last time we changed that code path, it also caused a regression. The degradation in performance is expected, but a 5x slowdown is definitely larger than it should be.\ndo we know if that's because the status used by the path is stale, or if removing sandboxes is actually that slow?\nif there's not a quick fix, should we revert and bring it back in once the root issue is understood?\nI think a revert is appropriate in this case.\nok, I'll open it\nopen at\nI agree with that 5x is something which shouldn't happen and i can take a look on why thats happening and that might require changing the way how the sandbox is currently deleted which is only during GC.", "commid": "kubernetes_issue_91316", "tokennum": 237}], "negative_passages": []}
{"query_id": "q-en-kubernetes-617abdcf13ee290705324bba1f1ea8409f86064929f06b2d0cf26d26d0211a33", "query": "github.com/munnerz/goautoneg v0.0.0-20191010083416-a7dc8b61c822 github.com/onsi/ginkgo/v2 v2.9.1 github.com/onsi/gomega v1.27.4 <del> github.com/opencontainers/runc v1.1.4 </del> <ins> github.com/opencontainers/runc v1.1.5 </ins> github.com/opencontainers/selinux v1.10.0 github.com/pkg/errors v0.9.1 github.com/pmezard/go-difflib v1.0.0", "positive_passages": [{"docid": "doc-en-kubernetes-3a5f1791fd28a186fcf23c773fa97525e98fb83cc70e7098ac61d449614dcefb", "text": "opencontainers/runc has fixed three CVEs: Latest runc is pulled by k/k Check runc version in file No response n/a n/a <details</details<details</details<details</details<details</details\n/assign /sig security architecture release\n/triage accepted", "commid": "kubernetes_issue_117094", "tokennum": 68}], "negative_passages": []}
{"query_id": "q-en-kubernetes-619cf7a3c50317d47c5ffcfa4e9b6aa7d463838de801747bdefd2f13b033eb82", "query": "return \"\", err } <ins> // try and get canonical path for disk and if we can't throw error vmDiskPath, err = getcanonicalVolumePath(ctx, vm.Datacenter, vmDiskPath) if err != nil { klog.Errorf(\"failed to get canonical path for %s on node %s: %v\", vmDiskPath, convertToString(nodeName), err) return \"\", err } </ins> diskUUID, err = vm.AttachDisk(ctx, vmDiskPath, &vclib.VolumeOptions{SCSIControllerType: vclib.PVSCSIControllerType, StoragePolicyName: storagePolicyName}) if err != nil { klog.Errorf(\"Failed to attach disk: %s for node: %s. err: +%v\", vmDiskPath, convertToString(nodeName), err)", "positive_passages": [{"docid": "doc-en-kubernetes-e1df151812a738ca8d7e9f97519d671c643638f3ca9d9400cc430f5f7a7d204c", "text": "When user creates a static PV using folder name in path: on vSAN backed datastore then detach disk does not work because check fails - The code expects folder name to be UUID but it does not and hence it determines disk is not attached to the node and hence no detach is ever performed. /sig storage cc", "commid": "kubernetes_issue_95121", "tokennum": 68}], "negative_passages": []}
{"query_id": "q-en-kubernetes-61ed001609e2fbd480441bbad9e8a2ef0b47da6eb684571f1b0f1d3a1c01d1c7", "query": "} func (sched *Scheduler) updatePodInSchedulingQueue(oldObj, newObj interface{}) { <del> pod := newObj.(*v1.Pod) if sched.skipPodUpdate(pod) { </del> <ins> oldPod, newPod := oldObj.(*v1.Pod), newObj.(*v1.Pod) // Bypass update event that carries identical objects; otherwise, a duplicated // Pod may go through scheduling and cause unexpected behavior (see #96071). if oldPod.ResourceVersion == newPod.ResourceVersion { </ins> return } <del> if err := sched.SchedulingQueue.Update(oldObj.(*v1.Pod), pod); err != nil { </del> <ins> if sched.skipPodUpdate(newPod) { return } if err := sched.SchedulingQueue.Update(oldPod, newPod); err != nil { </ins> utilruntime.HandleError(fmt.Errorf(\"unable to update %T: %v\", newObj, err)) } }", "positive_passages": [{"docid": "doc-en-kubernetes-1ef380d0c9eaabcc31aac489962d126bda361dc7bef4fb0787ab2e17f956bc1c", "text": "Which jobs are failing: pull-kubernetes-integration Which test(s) are failing: TestPreemptionRaces Testgrid link: /sig scheduling /help\n/reopen I just saw this again\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nIssues 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\nSeems to be green: https://k8s-\nIt's still flaky on both master and PR testing: master: https://k8s- () PR testing: (). /reopen\nReopened this issue. <detailsIn response to : It's still flaky on both master and PR testing: PR testing: (). </details\nFrom the above two logs, I'm feeling that there is a \"phantom\" event (very likely of type Update by enforced resync) triggering the pod in the completed N<subth</subtest, to be still alive in the N+1<subth</subtest.\n/triage accepted working on a fix.\nIt would be great if we assign a different name to the Nth round test's preemptor pod. Currently, whatever this is Nth test, the preemptor pod is always called 'preemptor-pod'.", "commid": "kubernetes_issue_85031", "tokennum": 367}], "negative_passages": []}
{"query_id": "q-en-kubernetes-620aede4f2349dd52982e298122ef39d7b454a5570439281f4a43ebe5bf9cb01", "query": "ExitCode: 1, }, }, <del> map[string]error{}, []api.ContainerStatus{}, map[string]api.ContainerState{ </del> <ins> reasons:     map[string]error{}, oldStatuses: []api.ContainerStatus{}, expectedState: map[string]api.ContainerState{ </ins> \"running\": {Running: &api.ContainerStateRunning{ StartedAt: unversioned.NewTime(testTimestamp), }}, }, <del> map[string]api.ContainerState{ </del> <ins> expectedLastTerminationState: map[string]api.ContainerState{ </ins> \"running\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID,", "positive_passages": [{"docid": "doc-en-kubernetes-b4459e221a04f6723f7b97c6a9d43d61c0d65417b08d143223c7057699636055", "text": "is this a Node bug? cc as next oncall to follow up on this.\nThis is a node bug due to init containers\nI may need help debugging - I see:\nSo I think the problem is in the error case - we're not properly recording that the start failed, and the next time we come in we somehow think the first container succeeded. I'll add some debugging to see if we can't recreate it.\nLet's discuss on instead.", "commid": "kubernetes_issue_25879", "tokennum": 102}], "negative_passages": []}
{"query_id": "q-en-kubernetes-620aede4f2349dd52982e298122ef39d7b454a5570439281f4a43ebe5bf9cb01", "query": "ExitCode: 1, }, }, <del> map[string]error{}, []api.ContainerStatus{}, map[string]api.ContainerState{ </del> <ins> reasons:     map[string]error{}, oldStatuses: []api.ContainerStatus{}, expectedState: map[string]api.ContainerState{ </ins> \"running\": {Running: &api.ContainerStateRunning{ StartedAt: unversioned.NewTime(testTimestamp), }}, }, <del> map[string]api.ContainerState{ </del> <ins> expectedLastTerminationState: map[string]api.ContainerState{ </ins> \"running\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID,", "positive_passages": [{"docid": "doc-en-kubernetes-dcc88d1d89328d1da3366de828afcd8ab0373228cc4437ea655e2cda79030f86", "text": "Kubelet issues a docker inspect call after creating a container, but for very short lived containers there is a window in which they could exit before being inspected in the docker manager. If the container PID is 0, we should check the ExitCode and other relevant fields and handle them appropriately. [1] This is the suspected cause of several flakes: /cc\nlooking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: I'd expect the second one to not have run in this case? Node logs:\nInit containers have an implicit assumption that container statuses include results of previous SyncPod invocations. If that's not the case we may need to fix that (or at least mitigate it). On May 18, 2016, at 8:28 PM, Prashanth B wrote: looking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: May 18 15:58:33.380: INFO: pod-init--1d4b-11e6-80a4- started at 2016-05-18T15:58:04-07:00 (2+1 container statuses recorded) May 18 15:58:33.380: INFO: Init container init1 ready: false, restart count 0 May 18 15:58:33.380: INFO: Init container init2 ready: true, restart count 0 I'd expect the second one to not have run in this case? Node logs: \u2014 You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub\nThis should be true. Is there any evidence that suggests the opposite? only shows conflicting view of whether init1 has run.\nIf the container exits already and it's not an infra container, kubelet should not error out. Although even if it does, I failed to see how this could affect the readiness of the init container without checking the code further.", "commid": "kubernetes_issue_25844", "tokennum": 487}], "negative_passages": []}
{"query_id": "q-en-kubernetes-620aede4f2349dd52982e298122ef39d7b454a5570439281f4a43ebe5bf9cb01", "query": "ExitCode: 1, }, }, <del> map[string]error{}, []api.ContainerStatus{}, map[string]api.ContainerState{ </del> <ins> reasons:     map[string]error{}, oldStatuses: []api.ContainerStatus{}, expectedState: map[string]api.ContainerState{ </ins> \"running\": {Running: &api.ContainerStateRunning{ StartedAt: unversioned.NewTime(testTimestamp), }}, }, <del> map[string]api.ContainerState{ </del> <ins> expectedLastTerminationState: map[string]api.ContainerState{ </ins> \"running\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID,", "positive_passages": [{"docid": "doc-en-kubernetes-ade5deee53831749acf4a20dbe39f9ef1836656ae43e40b0bb8594efa4e81e92", "text": "Each syncPod invocation, we inspect the list of init container in order looking for lastTerminationState. There could be a bug in that logic, or if we didn't get the full status, we might make a bad decision. When determining which container to run next, we always look for the last init container in the chain that has success, then run the next container (unless the pod is RestartNever). , Yu-Ju Hong wrote:\nSaw this flake again. How do we verify that container status is not lost between syn pods?\n... between calls to syncPods\nThe second sync clearly saw the init1 container, and decided to launch init2. See \"InitContainersToKeep\" in the message below.\ncontainers to keep can include failed containers. , Yu-Ju Hong wrote:\nDiscussed on slack. In summary, the problem has to do with how we convert the kubecontainer.PodStatus to the api.PodStatus. If a container is terminated, the function makes the decisions: the pod restart policy is \"Always\", and there is a \"failure reason\" recorded for the given container, this means the pod worker tried to (re)start the container but failed. Set the state to \"Waiting\" and populate the reason. , the container state is simply \"terminated\". Init containers don't obey the restart policy like regular containers, and the logic will need to be amended to work with them. is working on a PR. In addition to that, kubelet should not error out if a user container exited before it could apply the oom score (which is best effort in this case). fixes that.\nAhh, thanks for digging into the issue. This is the exact the concern I had when I reviewed the initial implementation of init container, which blocks pr for a while. I even asked to help me verify this case, unfortunately we didn't reproduce the issue back then. :-(\nI wish I'd seen the flakes in the runs prior to merge.\nWe didn't notice this until we started running the tests against docker v1.11.1, which is much faster and hit the race condition differently.\nI suppose that's a good thing...\nIt is hard to reproduce this.", "commid": "kubernetes_issue_25844", "tokennum": 482}], "negative_passages": []}
{"query_id": "q-en-kubernetes-620aede4f2349dd52982e298122ef39d7b454a5570439281f4a43ebe5bf9cb01", "query": "ExitCode: 1, }, }, <del> map[string]error{}, []api.ContainerStatus{}, map[string]api.ContainerState{ </del> <ins> reasons:     map[string]error{}, oldStatuses: []api.ContainerStatus{}, expectedState: map[string]api.ContainerState{ </ins> \"running\": {Running: &api.ContainerStateRunning{ StartedAt: unversioned.NewTime(testTimestamp), }}, }, <del> map[string]api.ContainerState{ </del> <ins> expectedLastTerminationState: map[string]api.ContainerState{ </ins> \"running\": {Terminated: &api.ContainerStateTerminated{ ExitCode:    1, ContainerID: emptyContainerID,", "positive_passages": [{"docid": "doc-en-kubernetes-0814a4e75b48cf2d27d20141c180e04fbc9b55d5398cce31b037f460c93acb1b", "text": "The extra check of last terminated container in your initial code makes me nervous, but we couldn't reproduce it due to that small race windows until we have a faster docker running on the node. :-)\nI got \"Pods should invoke init containers on a RestartAlways pod\" flake (referenced from ): Logs:\nAll the fixes went in. Please reopen this issue if you see any more flakes.", "commid": "kubernetes_issue_25844", "tokennum": 90}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6225fc1174c6de99f250a88121747da3b5eefc17b4b19e87e0d1485ff89161ec", "query": "procGetNetworkParams = iphlpapidll.MustFindProc(\"GetNetworkParams\") ) <ins> func fileExists(filename string) (bool, error) { stat, err := os.Stat(filename) if os.IsNotExist(err) { return false, nil } if err != nil { return false, err } return stat.Mode().IsRegular(), nil } </ins> func getHostDNSConfig(resolverConfig string) (*runtimeapi.DNSConfig, error) { <del> if resolverConfig != \"\" && resolverConfig != hostResolvConf { err := fmt.Errorf(`Unexpected resolver config value: \"%s\". Expected \"\" or \"%s\".`, resolverConfig, hostResolvConf) </del> <ins> if resolverConfig == \"\" { // This handles \"\" by returning defaults. return getDNSConfig(resolverConfig) } isFile, err := fileExists(resolverConfig) if err != nil { err = fmt.Errorf(`Unexpected error while getting os.Stat for \"%s\" resolver config. Error: %w`, resolverConfig, err) </ins> klog.ErrorS(err, \"Cannot get host DNS Configuration.\") return nil, err } <ins> if isFile { // Get the DNS config from a resolv.conf-like file. return getDNSConfig(resolverConfig) } </ins> <del> var ( hostDNS, hostSearch []string err                 error ) </del> <ins> if resolverConfig != hostResolvConf { err := fmt.Errorf(`Unexpected resolver config value: \"%s\". Expected \"\", \"%s\", or a path to an existing resolv.conf file.`, resolverConfig, hostResolvConf) klog.ErrorS(err, \"Cannot get host DNS Configuration.\") return nil, err } // If we get here, the resolverConfig == hostResolvConf and that is not actually a file, so // it means to use the host settings. </ins> // Get host DNS settings <del> if resolverConfig == hostResolvConf { hostDNS, err = getDNSServerList() if err != nil { err = fmt.Errorf(\"Could not get the host's DNS Server List. Error: %w\", err) klog.ErrorS(err, \"Encountered error while getting host's DNS Server List.\") return nil, err } hostSearch, err = getDNSSuffixList() if err != nil { err = fmt.Errorf(\"Could not get the host's DNS Suffix List. Error: %w\", err) klog.ErrorS(err, \"Encountered error while getting host's DNS Suffix List.\") return nil, err } </del> <ins> hostDNS, err := getDNSServerList() if err != nil { err = fmt.Errorf(\"Could not get the host's DNS Server List. Error: %w\", err) klog.ErrorS(err, \"Encountered error while getting host's DNS Server List.\") return nil, err } hostSearch, err := getDNSSuffixList() if err != nil { err = fmt.Errorf(\"Could not get the host's DNS Suffix List. Error: %w\", err) klog.ErrorS(err, \"Encountered error while getting host's DNS Suffix List.\") return nil, err </ins> } return &runtimeapi.DNSConfig{ Servers:  hostDNS,", "positive_passages": [{"docid": "doc-en-kubernetes-5e93ba1a338583c6193506912a68a67fcc908451a37c483694071bc120df2bcb", "text": "When a --resolv-conf (DNS resolver config) is passed to kubelet on a Windows node, the config content is used as part of sandbox initialization (through getHostDNSConfig()). Now with the recent changes (), it seems now to fail with an error like: E0315 10:22:16. 4764 ] \"Error syncing pod, skipping\" err=\"failed to \"CreatePodSandbox\" for \"img-pull-(-b40a-459d-9033-)\" with CreatePodSandboxError: \"Failed to generate sandbox config for pod \"img-pull-(-b40a-459d-9033-)\": Unexpected resolver config value: \"C:etckubernetescni\". Expected \"\" or \"Host\".\"\" pod=\"img-puller-3842/img-pull-\" podUID=-b40a-459d-9033- This is showing on all the runs of GCE testgrid (latest): Reading/using the passed resolv config on Windows Run a Windows pool with DNS resolv config being set as part of kubelet params. No response_ 27 alpha.3 1.27 beta.0 master <detailsGCE </details<details</details<details</details<details</details<details</details\n/triage accepted /milestone v1.27 /sig node /sig network\n/sig windows /cc\n/priority criticial-urgent as this is likely a release blocking\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority criticial-urgent 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\n/priority critical-urgent\nHmm, so you're setting the [1]. This PR introduced the capability to read the DNS config options from the Windows host registries while removing the capability to read from a file, introducing a regression. I've sent a PR addressing this issue: [1]\nIs the file you are pointing to a UNIX-style or something else?\nWas the file changing the behavior of the node?", "commid": "kubernetes_issue_116782", "tokennum": 565}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6225fc1174c6de99f250a88121747da3b5eefc17b4b19e87e0d1485ff89161ec", "query": "procGetNetworkParams = iphlpapidll.MustFindProc(\"GetNetworkParams\") ) <ins> func fileExists(filename string) (bool, error) { stat, err := os.Stat(filename) if os.IsNotExist(err) { return false, nil } if err != nil { return false, err } return stat.Mode().IsRegular(), nil } </ins> func getHostDNSConfig(resolverConfig string) (*runtimeapi.DNSConfig, error) { <del> if resolverConfig != \"\" && resolverConfig != hostResolvConf { err := fmt.Errorf(`Unexpected resolver config value: \"%s\". Expected \"\" or \"%s\".`, resolverConfig, hostResolvConf) </del> <ins> if resolverConfig == \"\" { // This handles \"\" by returning defaults. return getDNSConfig(resolverConfig) } isFile, err := fileExists(resolverConfig) if err != nil { err = fmt.Errorf(`Unexpected error while getting os.Stat for \"%s\" resolver config. Error: %w`, resolverConfig, err) </ins> klog.ErrorS(err, \"Cannot get host DNS Configuration.\") return nil, err } <ins> if isFile { // Get the DNS config from a resolv.conf-like file. return getDNSConfig(resolverConfig) } </ins> <del> var ( hostDNS, hostSearch []string err                 error ) </del> <ins> if resolverConfig != hostResolvConf { err := fmt.Errorf(`Unexpected resolver config value: \"%s\". Expected \"\", \"%s\", or a path to an existing resolv.conf file.`, resolverConfig, hostResolvConf) klog.ErrorS(err, \"Cannot get host DNS Configuration.\") return nil, err } // If we get here, the resolverConfig == hostResolvConf and that is not actually a file, so // it means to use the host settings. </ins> // Get host DNS settings <del> if resolverConfig == hostResolvConf { hostDNS, err = getDNSServerList() if err != nil { err = fmt.Errorf(\"Could not get the host's DNS Server List. Error: %w\", err) klog.ErrorS(err, \"Encountered error while getting host's DNS Server List.\") return nil, err } hostSearch, err = getDNSSuffixList() if err != nil { err = fmt.Errorf(\"Could not get the host's DNS Suffix List. Error: %w\", err) klog.ErrorS(err, \"Encountered error while getting host's DNS Suffix List.\") return nil, err } </del> <ins> hostDNS, err := getDNSServerList() if err != nil { err = fmt.Errorf(\"Could not get the host's DNS Server List. Error: %w\", err) klog.ErrorS(err, \"Encountered error while getting host's DNS Server List.\") return nil, err } hostSearch, err := getDNSSuffixList() if err != nil { err = fmt.Errorf(\"Could not get the host's DNS Suffix List. Error: %w\", err) klog.ErrorS(err, \"Encountered error while getting host's DNS Suffix List.\") return nil, err </ins> } return &runtimeapi.DNSConfig{ Servers:  hostDNS,", "positive_passages": [{"docid": "doc-en-kubernetes-a55794e1d2c420cf7484c297920657922704eb45d045ae8237364febdd60d634", "text": "Yeah, what used on GCE/GKE, seems to be a Linux-like conf, eg: nameserver 10.128.0.1 search c.<project_name.internal google.internal ` We haven't tried to remove from kubelet to see the behavior.\nThis Issue/PR has been marked as release blocker. Please have the fix merged by eod today otherwise the feature has to be reverted. For the Issue/PR owner: please have a revert/feature disable PR open today in case the fix failed to get in. Thank you! See the -- Kubernetes 1.27 release manager\nI opened up a revert PR in case this PR does not merge by code freeze.\nThanks for the resolution! both 2019 and 2022 grids seems to be back to green now!\nThanks for confirming! I opened to ensure gets updated too", "commid": "kubernetes_issue_116782", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-622950245410adde9ed8e87a0ce692f6d6da8ce135a42e263272c5bd023f4470", "query": "kubeCfg.PodInfraContainerImage, float32(kubeCfg.RegistryPullQPS), int(kubeCfg.RegistryBurst), <del> containerLogsDir, </del> <ins> ContainerLogsDir, </ins> kubeDeps.OSInterface, klet.networkPlugin, klet,", "positive_passages": [{"docid": "doc-en-kubernetes-0ad427ca9c00c618017f4be9fb19a1df6f4ab39ddc68f128fc109eb4d0409cbf", "text": "Cluster logging assumes kubelet stores container log at a specific directory with specific name. Currently the path is: After the CRI work, the path will be: However, we don't have test coverage for this. We don't even know whether the log files are there or not. We should add a node e2e test for this, basically: 1) Create a container which prints logs 2) Check whether the expected log file is created. 3) Check whether the logs are collected in the file as expected. And it would be better to launch a pod to do the check instead of accessing local file system directly, which makes containerizing easier. /cc because you are collecting missing test. /cc\nI will try to add a node-e2e test there\nI think it's ok to add this for CRI. But there maybe problems on today's interface for rkt. If I'm not wrong, rkt does't store logs at same location with docker. cc/ Is this true?\nThanks! :)\nAfter gets merged, we need to update the test to verify the cri log path.", "commid": "kubernetes_issue_34661", "tokennum": 234}], "negative_passages": []}
{"query_id": "q-en-kubernetes-625e2f560075fb096bbf6f7b4cfbe08780a525c74b30e90acdde5705b24fb469", "query": "} return nil } <ins> // ClearEntriesForPortNAT uses the conntrack tool to delete the contrack entries // for connections specified by the {dest IP, port} pair. // Known issue: // https://github.com/kubernetes/kubernetes/issues/59368 func ClearEntriesForPortNAT(execer exec.Interface, dest string, port int, protocol v1.Protocol) error { if port <= 0 { return fmt.Errorf(\"Wrong port number. The port number must be greater then zero\") } parameters := parametersWithFamily(utilnet.IsIPv6String(dest), \"-D\", \"-p\", protoStr(protocol), \"--dport\", strconv.Itoa(port), \"--dst-nat\", dest) err := Exec(execer, parameters...) if err != nil && !strings.Contains(err.Error(), NoConnectionToDelete) { return fmt.Errorf(\"error deleting conntrack entries for UDP port: %d, error: %v\", port, err) } return nil } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-9e39524d0e4c89f1ddf9c516fe4e1c471a25826ee6b222abfe1f6c0cc213064c", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: BUG REPORT What happened: When deleting/recreating pods backing a UDP service, traffic from external senders stops flowing. What you expected to happen: Traffic would continue to flow to new pods. How to reproduce it (as minimally and precisely as possible): Based on reading of similar issues and commit messages it seems like this would be most noticable on high-volume UDP applications, statsd and syslog are good examples. a deployment and service for a UDP app. In my test case, this would be the container. an external node, create a small test script utilizing a statsd library such as pystatsd. The most important part is that the sender uses the same source-port for every packet sent. Ex: the sender. Install tcpdump into the pod and watch for incoming packets, example from the test case: the pod tcpdump in the newly created pod. Observe that no new matching packets are flowing. existing conntrack rules on all nodes in the cluster. You should see traffic start flowing to the pod again. example command for clearing conntrack rules on the nodes: Anything else we need to know?: I have tested this only on GKE-managed clusters that utilize google forwarding-rules for external LBs, but I believe the issue may be present on any platform where iptables mode for kube-proxy is used. Tested and verified on 1.8.6-gke.0 and 1.7.11-gke.1. Also tested with both Google Container-optimized OS and the Ubuntu-based node images. I have only test this on GKE It appears this was a known issue and should have been cleared up by: From my reading of , it seems as if the func should exec() to clear up UDP entries on service endpoint change, but the only place I see that func called is from syncProxyRules(). That func looks complex and possibly like it is only run occasionally and not on service/endpoint changes. Environment: Kubernetes version (use ): (Also tested on 1.7.11-gke.1) Cloud provider or hardware configuration: GKE-managed clusters, google cloud. OS (e.g.", "commid": "kubernetes_issue_59368", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-625e2f560075fb096bbf6f7b4cfbe08780a525c74b30e90acdde5705b24fb469", "query": "} return nil } <ins> // ClearEntriesForPortNAT uses the conntrack tool to delete the contrack entries // for connections specified by the {dest IP, port} pair. // Known issue: // https://github.com/kubernetes/kubernetes/issues/59368 func ClearEntriesForPortNAT(execer exec.Interface, dest string, port int, protocol v1.Protocol) error { if port <= 0 { return fmt.Errorf(\"Wrong port number. The port number must be greater then zero\") } parameters := parametersWithFamily(utilnet.IsIPv6String(dest), \"-D\", \"-p\", protoStr(protocol), \"--dport\", strconv.Itoa(port), \"--dst-nat\", dest) err := Exec(execer, parameters...) if err != nil && !strings.Contains(err.Error(), NoConnectionToDelete) { return fmt.Errorf(\"error deleting conntrack entries for UDP port: %d, error: %v\", port, err) } return nil } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-27a4c6cdabc82c95dde932bb7bf1e1865b5f691c3b3e7bf1ed0c71bfc361fddc", "text": "from /etc/os-release): tried both: and Kernel (e.g. ): and Install tools: Others:\n/sig network\nWe also ran into this in kubernetes v1.7.6 using OpenShift 3.7:\n~I believe this is the same as ~If so, it is fixed in 1.10: These are about HostPort, not NodePort, sorry for the noise.\nIssues 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\nIs there any other known workaround for this besides updating conntrack rules on the kube nodes? I tried deleting and recreating the service, but this didn't update the rules. When I restart the stream on the client side data flows correctly again (perhaps it's perceived as a new connection), but I have to restart the stream for each sender.\n/remove-lifecycle stale\nFWIW, this is not fixed in 1.10 - that fix was for HostPort, and this is still a bug for NodePort.\nI am seeing this issue in 1.11. I am using LoadBalancer type.\nhas been working on a fix for this, FYI.\nThis issue is extremely impactful for telephony protocols that rely on static source ip and source port. Any update on a possible workaround? I was thinking a potential workaround might be to reduce the UDP timeout to something really short so the stale conntrack entries go away faster. Or maybe there is a way to flush conntrack on the event of pod deletion? Edit: Removed stupid idea of a workaround to disable conntrack for UDP. Can't disable conntrack for UDP because it's used for DNAT from node to container.\nThe workaround is to not use NodePorts. Other kinds of services are already correct.\nnot sure what you mean. I am seeing the issue with a LoadBalancer type so it does not affect NodePorts only. As a workaround I have created a small python script that watches the K8s API for pod deletions and clears the related conntrack entries when that happens. I can share it when I get to work on Monday if you want to try it out.", "commid": "kubernetes_issue_59368", "tokennum": 535}], "negative_passages": []}
{"query_id": "q-en-kubernetes-625e2f560075fb096bbf6f7b4cfbe08780a525c74b30e90acdde5705b24fb469", "query": "} return nil } <ins> // ClearEntriesForPortNAT uses the conntrack tool to delete the contrack entries // for connections specified by the {dest IP, port} pair. // Known issue: // https://github.com/kubernetes/kubernetes/issues/59368 func ClearEntriesForPortNAT(execer exec.Interface, dest string, port int, protocol v1.Protocol) error { if port <= 0 { return fmt.Errorf(\"Wrong port number. The port number must be greater then zero\") } parameters := parametersWithFamily(utilnet.IsIPv6String(dest), \"-D\", \"-p\", protoStr(protocol), \"--dport\", strconv.Itoa(port), \"--dst-nat\", dest) err := Exec(execer, parameters...) if err != nil && !strings.Contains(err.Error(), NoConnectionToDelete) { return fmt.Errorf(\"error deleting conntrack entries for UDP port: %d, error: %v\", port, err) } return nil } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-956c9b1270ab4e0eb744fb5e7c207e8e7b7c0a49e83c634550198bfe9b333eeb", "text": "I've my script . Note that it's not tested much so don't use it in a production environment. Also it cleans up all conntrack entries for a deleted pod, not only the UDP related ones.\nWe are also seeing this issue with type loadbalancer. We are on 1.11. Our use-case is the following: multiple devices are sending to an aggreagator machine. This machine forwards the UDP packages to a loadBalancer in gcp. When debugging the service, I noticed the following: The traffic is assigned to one pod, and the packages are not loadbalanced (client and server are the same cfr use-case) When redeploying a new cluster, Conntrack is cleared on termination signal of the old pod. (client receives connection refused) red/black and highlander deployment strategies have the same effect. How would I expect this to be working then? New cluster is . Conntrack is cleared Data is routed to NEW pods old pods are terminated Best Regards, Tim\nI am seeing this exact same issue on our cluster which has k8s v1.14.5 . We have endpoint nginx pods backing a UDP service with nodeport. Suddenly one day we see traffic not hitting into nginx pod but reaching the node hosting the nginx pod. We could simulate the problem by restarting the nginx pods. I am assuming with this issue marked as closed; and having made its way into v1.14; we should not be seeing this. Would also like to point out; the one thing, in addition we have in the service is ExternalTrafficPolicy set to Local. Can anyone please guide/help on why we are seeing this in v.1.14.5 of our cluster.\nSeeing this with k8s v1.16.5", "commid": "kubernetes_issue_59368", "tokennum": 391}], "negative_passages": []}
{"query_id": "q-en-kubernetes-626d4e8710e4e16201ed04ec0a61abba19916e098c9ba880ebdcca8c64e3c368", "query": "importpath = \"k8s.io/kube-aggregator/pkg/apiserver\", deps = [ \"//vendor/github.com/golang/glog:go_default_library\", <del> \"//vendor/k8s.io/api/core/v1:go_default_library\", </del> \"//vendor/k8s.io/apimachinery/pkg/api/errors:go_default_library\", \"//vendor/k8s.io/apimachinery/pkg/apimachinery/announced:go_default_library\", \"//vendor/k8s.io/apimachinery/pkg/apimachinery/registered:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-89e8d863e20723ba6498e9abf897dd4e49e26cad02c0dde0a4957b2eb3151e69", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Currently APIServiceRegistrationController watch service change and find the related APIServices related if any. Then it AddAPIService/RemoveAPIService for APIAggregator. I dig into the kube-aggregator and find it no need totally, because update APIServices status when related service or endpoint change. So if does not watch services, it will not miss any event for APIServices. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/cc\n/kind enhancement /sig api-machinery\n/assign\nthat does not follow. AvailableConditionController modifies the APIService object. APIServiceRegistrationController must still watch the APIService objects to observe those changes.\noh, I misread the description. You're saying APIServiceRegistrationController doesn't need to watch v1.Service objects", "commid": "kubernetes_issue_57836", "tokennum": 300}], "negative_passages": []}
{"query_id": "q-en-kubernetes-628730e7e32e608a94b5373c744822174a53518792765440f5b7843587b6d1d2", "query": "if len(psp.Spec.AllowedFlexVolumes) > 0 { w.Write(LEVEL_1, \"Allowed FlexVolume Types:t%sn\", flexVolumesToString(psp.Spec.AllowedFlexVolumes)) } <ins> if len(psp.Spec.AllowedUnsafeSysctls) > 0 { w.Write(LEVEL_1, \"Allowed Unsafe Sysctls:t%sn\", sysctlsToString(psp.Spec.AllowedUnsafeSysctls)) } if len(psp.Spec.ForbiddenSysctls) > 0 { w.Write(LEVEL_1, \"Forbidden Sysctls:t%sn\", sysctlsToString(psp.Spec.ForbiddenSysctls)) } </ins> w.Write(LEVEL_1, \"Allow Host Network:t%tn\", psp.Spec.HostNetwork) w.Write(LEVEL_1, \"Allow Host Ports:t%sn\", hostPortRangeToString(psp.Spec.HostPorts)) w.Write(LEVEL_1, \"Allow Host PID:t%tn\", psp.Spec.HostPID)", "positive_passages": [{"docid": "doc-en-kubernetes-1c37f3b13ef66319b53623e24b4fece0550cb85e7e62ca9b694924c6c433e0c8", "text": "/kind bug What happened: does not show the description for the new field in What you expected to happen: should describe the new field. How to reproduce it (as minimally and precisely as possible): Environment: Kubernetes version (use ): master\n/sig auth\nGitHub didn't allow me to assign the following users: fanzhangio. Note that only and repo collaborators can be assigned. <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\nIf nobody has started yet, I wanna to pick it up.\nwas working on it AFAIR.\nIndeed. if you don't mind, I'd take over.", "commid": "kubernetes_issue_65181", "tokennum": 165}], "negative_passages": []}
{"query_id": "q-en-kubernetes-628df1e535f121983615554984159ddd3bf935334f00cc43451aa38260fc541e", "query": "// applyPlatformSpecificDockerConfig applies platform-specific configurations to a dockertypes.ContainerCreateConfig struct. // The containerCleanupInfo struct it returns will be passed as is to performPlatformSpecificContainerCleanup <del> // after either: //   * the container creation has failed //   * the container has been successfully started //   * the container has been removed // whichever happens first. </del> <ins> // after either the container creation has failed or the container has been removed. </ins> func (ds *dockerService) applyPlatformSpecificDockerConfig(*runtimeapi.CreateContainerRequest, *dockertypes.ContainerCreateConfig) (*containerCleanupInfo, error) { return nil, nil } // performPlatformSpecificContainerCleanup is responsible for doing any platform-specific cleanup <del> // after either: //   * the container creation has failed //   * the container has been successfully started //   * the container has been removed // whichever happens first. // Any errors it returns are simply logged, but do not prevent the container from being started or // removed. </del> <ins> // after either the container creation has failed or the container has been removed. </ins> func (ds *dockerService) performPlatformSpecificContainerCleanup(cleanupInfo *containerCleanupInfo) (errors []error) { return }", "positive_passages": [{"docid": "doc-en-kubernetes-486ca0159276eedd0d2aa336961ee5fd6fb83d0ac97af7f3f9c8c863d43fcef2", "text": "What would you like to be : Periodically remove cleanupInfos for old containers from dockershim's map. One way of doing that would be to just forget about s older than say an hour, as they should always be short-lived. Why is this needed: introduced a new in-memory map for the dockershim, that could potentially (in pathological cases) cause memory leaks - for containers that use GMSA cred specs, get created successfully, but then never get started nor removed. This might be okay for the alpha release of the GMSA feature, but should be addressed in the beta. See\n/assign wk8\n/sig windows\n/milestone v1.15\ngot moved out. let's move this issue with it as well /milestone v1.16\nHello! I'm bug triage lead for the 1.16 release cycle and considering this issue is tagged for 1.16, but not updated for a long time, I'd like to check its status. The code freeze is starting on August 29th (about 1.5 weeks from now), which means that there should be a PR ready (and merged) until then. Do we still target this issue to be fixed for 1.16?\n: yup we'd love to have this in 1.16, still waiting for kind reviewers on :) ...", "commid": "kubernetes_issue_74843", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-629213e341088499acbf47797f9f9bb1053a9019cff28136cec150bfc544241a", "query": "utilerrors \"k8s.io/apimachinery/pkg/util/errors\" serviceapi \"k8s.io/kubernetes/pkg/api/v1/service\" <ins> \"github.com/Azure/azure-sdk-for-go/arm/compute\" </ins> \"github.com/Azure/azure-sdk-for-go/arm/network\" \"github.com/Azure/go-autorest/autorest/to\" \"github.com/golang/glog\"", "positive_passages": [{"docid": "doc-en-kubernetes-0f3fba1dceb9c94d1a19ea07536eb93382a47fa8d74b43be2f3310b5be7e4348", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: In certain large cluster scenarios we would like to anticipate kubelet behavior hitting request limits, and backoff in response. E.g., What you expected to happen: This is a request for add'l backoff coverage, so nothing surprising. How to reproduce it (as minimally and precisely as possible): Build a cluster with as many nodes as your subscription will support on azure until kubelet behavior contributes to backend API request limits. Environment: Kubernetes version (use ): and Cloud provider or hardware configuration**: azure OS (e.g. from /etc/os-release): Ubuntu 16.04.2 LTS (Xenial Xerus) Kernel (e.g. ): Linux k8s-pool7--7 4.4.0-83-generic -Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x8664 x8664 x86_64 GNU/Linux Install tools: acs-engine Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig azure", "commid": "kubernetes_issue_48971", "tokennum": 358}], "negative_passages": []}
{"query_id": "q-en-kubernetes-62e2af84c42a2d1da5934d7473397d3695d64ca85144cbb525ac93b02a109716", "query": "fs.IntVar(&s.HardPodAffinitySymmetricWeight, \"hard-pod-affinity-symmetric-weight\", api.DefaultHardPodAffinitySymmetricWeight, \"RequiredDuringScheduling affinity is not symmetric, but there is an implicit PreferredDuringScheduling affinity rule corresponding \"+ \"to every RequiredDuringScheduling affinity rule. --hard-pod-affinity-symmetric-weight represents the weight of implicit PreferredDuringScheduling affinity rule.\") <ins> fs.MarkDeprecated(\"hard-pod-affinity-symmetric-weight\", \"This option was moved to the policy configuration file\") </ins> fs.StringVar(&s.FailureDomains, \"failure-domains\", api.DefaultFailureDomains, \"Indicate the \"all topologies\" set for an empty topologyKey when it's used for PreferredDuringScheduling pod anti-affinity.\") fs.MarkDeprecated(\"failure-domains\", \"Doesn't have any effect. Will be removed in future version.\") leaderelection.BindFlags(&s.LeaderElection, fs)", "positive_passages": [{"docid": "doc-en-kubernetes-88466bc637a805045217da94feabbdbd3df0ba52cd0d9904e95d3984c4cf4efa", "text": "( noticed this) HardPodAffinitySymmetricWeight should be in the , not in KubeSchedulerConfiguration If/when fixing this, we need to be careful to do it in a backward-compatilble way.\nDo you mean ? It seems scheduler policy config's args can not passed to FitPredicates; it need to update related interface. For the : mark to be deprecated and set scheduler policy config to HardPodAffinitySymmetricWeight if policy config is empty.\nAre you working on this? if no, I can take it.\n, nop; please go ahead.\n/ / / , When reviewing the PR, there's one question on : the default value of is 1, which means the weight (1) will always add to priorities if term matched (), does it our expectation? And the user has to set it to 0 to disable it. IMO, the default value of should be 0.\nThe value 1 (instead of 0) was chosen so that if you say A must run with B, there is an automatic preference that B should run with A. This seems like reasonable behavior.\nThanks very much; reasonable case to me. But it seems we can not disable it: if set to 0, the default funcs will set it to default (1); similar result to un-set. Anyway, no user complain this now :).", "commid": "kubernetes_issue_43845", "tokennum": 306}], "negative_passages": []}
{"query_id": "q-en-kubernetes-62ec76c0843556553e724754c59e5071ca5683af473dd4cc1cc23bf8c9785858", "query": "<del> <!-- BEGIN MUNGE: UNVERSIONED_WARNING --> <!-- BEGIN STRIP_FOR_RELEASE --> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <h2>PLEASE NOTE: This document applies to the HEAD of the source tree</h2> If you are using a released version of Kubernetes, you should refer to the docs that go with that version. Documentation for other releases can be found at [releases.k8s.io](http://releases.k8s.io). </strong> -- <!-- END STRIP_FOR_RELEASE --> <!-- END MUNGE: UNVERSIONED_WARNING --> # Generic Configuration Object ## Abstract This proposal proposes a new API resource, `ConfigMap`, that stores data used for the configuration of applications deployed on `Kubernetes`. The main focus points of this proposal are: * Dynamic distribution of configuration data to deployed applications. * Encapsulate configuration information and simplify `Kubernetes` deployments. * Create a flexible configuration model for `Kubernetes`. ## Motivation A `Secret`-like API resource is needed to store configuration data that pods can consume. Goals of this design: 1.  Describe a `ConfigMap` API resource 2.  Describe the semantics of consuming `ConfigMap` as environment variables 3.  Describe the semantics of consuming `ConfigMap` as files in a volume ## Use Cases 1. As a user, I want to be able to consume configuration data as environment variables 2. As a user, I want to be able to consume configuration data as files in a volume 3. As a user, I want my view of configuration data in files to be eventually consistent with changes to the data ### Consuming `ConfigMap` as Environment Variables Many programs read their configuration from environment variables.  `ConfigMap` should be possible to consume in environment variables.  The rough series of events for consuming `ConfigMap` this way is: 1. A `ConfigMap` object is created 2. A pod that consumes the configuration data via environment variables is created 3. The pod is scheduled onto a node 4. The kubelet retrieves the `ConfigMap` resource(s) referenced by the pod and starts the container processes with the appropriate data in environment variables ### Consuming `ConfigMap` in Volumes Many programs read their configuration from configuration files.  `ConfigMap` should be possible to consume in a volume.  The rough series of events for consuming `ConfigMap` this way is: 1. A `ConfigMap` object is created 2. A new pod using the `ConfigMap` via the volume plugin is created 3. The pod is scheduled onto a node 4. The Kubelet creates an instance of the volume plugin and calls its `Setup()` method 5. The volume plugin retrieves the `ConfigMap` resource(s) referenced by the pod and projects the appropriate data into the volume ### Consuming `ConfigMap`  Updates Any long-running system has configuration that is mutated over time.  Changes made to configuration data must be made visible to pods consuming data in volumes so that they can respond to those changes. The `resourceVersion` of the `ConfigMap` object will be updated by the API server every time the object is modified.  After an update, modifications will be made visible to the consumer container: 1. A `ConfigMap` object is created 2. A new pod using the `ConfigMap` via the volume plugin is created 3. The pod is scheduled onto a node 4. During the sync loop, the Kubelet creates an instance of the volume plugin and calls its `Setup()` method 5. The volume plugin retrieves the `ConfigMap` resource(s) referenced by the pod and projects the appropriate data into the volume 6. The `ConfigMap` referenced by the pod is updated 7. During the next iteration of the `syncLoop`, the Kubelet creates an instance of the volume plugin and calls its `Setup()` method 8. The volume plugin projects the updated data into the volume atomically It is the consuming pod's responsibility to make use of the updated data once it is made visible. Because environment variables cannot be updated without restarting a container, configuration data consumed in environment variables will not be updated. ### Advantages * Easy to consume in pods; consumer-agnostic * Configuration data is persistent and versioned * Consumers of configuration data in volumes can respond to changes in the data ## Proposed Design ### API Resource The `ConfigMap` resource will be added to the `extensions` API Group: ```go package api // ConfigMap holds configuration data for pods to consume. type ConfigMap struct { TypeMeta   `json:\",inline\"` ObjectMeta `json:\"metadata,omitempty\"` // Data contains the configuration data.  Each key must be a valid DNS_SUBDOMAIN or leading // dot followed by valid DNS_SUBDOMAIN. Data map[string]string `json:\"data,omitempty\"` } type ConfigMapList struct { TypeMeta `json:\",inline\"` ListMeta `json:\"metadata,omitempty\"` Items []ConfigMap `json:\"items\"` } ``` A `Registry` implementation for `ConfigMap` will be added to `pkg/registry/configmap`. ### Environment Variables The `EnvVarSource` will be extended with a new selector for `ConfigMap`: ```go package api // EnvVarSource represents a source for the value of an EnvVar. type EnvVarSource struct { // other fields omitted // Specifies a ConfigMap key ConfigMap *ConfigMapSelector `json:\"configMap,omitempty\"` } // ConfigMapSelector selects a key of a ConfigMap. type ConfigMapSelector struct { // The name of the ConfigMap to select a key from. ConfigMapName string `json:\"configMapName\"` // The key of the ConfigMap to select. Key string `json:\"key\"` } ``` ### Volume Source A new `ConfigMapVolumeSource` type of volume source containing the `ConfigMap` object will be added to the `VolumeSource` struct in the API: ```go package api type VolumeSource struct { // other fields omitted ConfigMap *ConfigMapVolumeSource `json:\"configMap,omitempty\"` } // ConfigMapVolumeSource represents a volume that holds configuration data type ConfigMapVolumeSource struct { // A list of configuration data keys to project into the volume in files Files []ConfigMapVolumeFile `json:\"files\"` } // ConfigMapVolumeFile represents a single file containing configuration data type ConfigMapVolumeFile struct { ConfigMapSelector `json:\",inline\"` // The relative path name of the file to be created. // Must not be absolute or contain the '..' path. Must be utf-8 encoded. // The first item of the relative path must not start with '..' Path string `json:\"path\"` } ``` **Note:** The update logic used in the downward API volume plug-in will be extracted and re-used in the volume plug-in for `ConfigMap`. ## Examples #### Consuming `ConfigMap` as Environment Variables ```yaml apiVersion: extensions/v1beta1 kind: ConfigMap metadata: name: etcd-env-config data: number_of_members: 1 initial_cluster_state: new initial_cluster_token: DUMMY_ETCD_INITIAL_CLUSTER_TOKEN discovery_token: DUMMY_ETCD_DISCOVERY_TOKEN discovery_url: http://etcd-discovery:2379 etcdctl_peers: http://etcd:2379 ``` This pod consumes the `ConfigMap` as environment variables: ```yaml apiVersion: v1 kind: Pod metadata: name: config-env-example spec: containers: - name: etcd image: openshift/etcd-20-centos7 ports: - containerPort: 2379 protocol: TCP - containerPort: 2380 protocol: TCP env: - name: ETCD_NUM_MEMBERS valueFrom: configMap: configMapName: etcd-env-config key: number_of_members - name: ETCD_INITIAL_CLUSTER_STATE valueFrom: configMap: configMapName: etcd-env-config key: initial_cluster_state - name: ETCD_DISCOVERY_TOKEN valueFrom: configMap: configMapName: etcd-env-config key: discovery_token - name: ETCD_DISCOVERY_URL valueFrom: configMap: configMapName: etcd-env-config key: discovery_url - name: ETCDCTL_PEERS valueFrom: configMap: configMapName: etcd-env-config key: etcdctl_peers ``` ### Consuming `ConfigMap` as Volumes `redis-volume-config` is intended to be used as a volume containing a config file: ```yaml apiVersion: extensions/v1beta1 kind: ConfigMap metadata: name: redis-volume-config data: redis.conf: \"pidfile /var/run/redis.pidnport6379ntcp-backlog 511n databases 1ntimeout 0n\" ``` The following pod consumes the `redis-volume-config` in a volume: ```yaml apiVersion: v1 kind: Pod metadata: name: config-volume-example spec: containers: - name: redis image: kubernetes/redis command: \"redis-server /mnt/config-map/etc/redis.conf\" ports: - containerPort: 6379 volumeMounts: - name: config-map-volume mountPath: /mnt/config-map volumes: - name: config-map-volume configMap: files: - path: \"etc/redis.conf\" configMapName: redis-volume-config key: redis.conf ``` ### Future Improvements In the future, we may add the ability to specify an init-container that can watch the volume contents for updates and respond to changes when they occur. <!-- BEGIN MUNGE: GENERATED_ANALYTICS --> [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/configmap.md?pixel)]() <!-- END MUNGE: GENERATED_ANALYTICS --> </del>", "positive_passages": [{"docid": "doc-en-kubernetes-ab39f39ee12e84e818aa9c92c6877733f255a4fad832176aa0525d5bb0051663", "text": "What happened: Visited It shows the release notes for v1.17 What you expected to happen: See the release notes for v1.18 How to reproduce it (as minimally and precisely as possible): Open in any browser or with curl\n/sig docs\n/assign", "commid": "kubernetes_issue_89598", "tokennum": 57}], "negative_passages": []}
{"query_id": "q-en-kubernetes-62fda47231171e9a41a7c7894c0628d6702a7caa56c47e06f6b5e96c373fd2ba", "query": "// Run begins watching and syncing daemon sets. func (dsc *DaemonSetsController) Run(workers int, stopCh <-chan struct{}) { defer util.HandleCrash() <ins> glog.Infof(\"Starting Daemon Sets controller manager\") controller.SyncAllPodsWithStore(dsc.kubeClient, dsc.podStore.Store) </ins> go dsc.dsController.Run(stopCh) go dsc.podController.Run(stopCh) go dsc.nodeController.Run(stopCh)", "positive_passages": [{"docid": "doc-en-kubernetes-b0a441a371f8db864bebc11c7303837af71a86244bb0f50ec81fe1d8a09d5c71", "text": "The test is in flaky suite and no one seems to care. We need an owner for this test. cc Last failure log:\ndo you think you can take a look at this?\nThis is happening because of a bad assumption. The assumption is: if the reflector's store is consistent with etcd, the store given back to clients of the framework.Controller is too. I'd really like a general fix applicable to all controllers for this problem, but fixing it just for the RCs is pretty easy. In more detail: This function reports when the reflector has listed from apiserver. But the store given to the reflector is the fifo of the framework.Controller. The store given back to the caller is still not consistent, and will not be till the framework.Controller puts all the objects from the fifo into the client state store (). The rc specific fix: Before starting the rc manager, seed the expectations store with an expectation like {rc:foo, adds: foo.Status.Replicas, deletes:0}. This will wait for status.Replicas number of ADD events till a timeout. The general fix: Somehow expose this through framework.Controller.HasSynced (clients don't care about the fifo anyway, shouldn't it just be an implementation detail?) ideas? cc'ing people who have written controllers that might be interested I don't think this (and generally anything flaky for 1 release) is a p0, I can fix it if you don't mind dealing with the flakes till I've cleared things off my plate. I'd be more than happy to review a fix.\nWell, it's a P0 because test is flaky. E.g last run:\n- did you have chance to look into it?\nThe \"DaemonRestart\" tests are still labeled at . I will send a PR to promote them.\nare you still planning to send aPR to promote the DaemonRestart tests out of flaky? I think this is the right thing to do.\nAck; sorry, I lost this in the muck.", "commid": "kubernetes_issue_17829", "tokennum": 444}], "negative_passages": []}
{"query_id": "q-en-kubernetes-62fe9de90eb340bf529cbe0e17b4f66ceeedebf0618fa419b4e9347d0a763e19", "query": "}) It(\"should write files of various sizes, verify size, validate content\", func() { <del> fileSizes := []int64{1 * framework.MiB, 100 * framework.MiB} </del> <ins> fileSizes := []int64{fileSizeSmall, fileSizeMedium} </ins> fsGroup := int64(1234) podSec := v1.PodSecurityContext{ FSGroup: &fsGroup,", "positive_passages": [{"docid": "doc-en-kubernetes-540712d0b27ee7f52d7d02bd3719013304c1ce42c6b5d8b93c3ee3671a9c1c7c", "text": "The \"Volume plugin streaming [Slow] NFS should write files of various sizes, verify size, validate content\" e2e test is failing on our 2k-node gce clusters (https://k8s-) with the following error: cc\nCould you take a look into it or reassign as apt? This is part of the correctness suite and large cluster tests are release-blocking.\n/assign\nis this run using the kubemark environment? I'll also take a look. It could be that the commands this test needs to execute may not work with kubemark. /assign\ncc\nNo, this is not kubemark. This is on a real 2000-node cluster.\nAlso all other volume-related e2e tests are passing, except this one.\nLooking at the log I see that the nfs test fails trying to verify the test file's content. The test exec's into the nfs client pod and executes: The return code from above is 127. The test then deletes the nfs client pod calling which works. The nfs-server pod is deleted in the AfterEach. For some reason the reported error is 137 but the returned err 127. The same command is exec'd for all of the tested storage plugins so not sure why it's failing just for nfs. Error 127 might be \"command not found\".\nThe other strange thing is that it's only failing in this suite and not the others.\nWhen I look at the kubelet log, I see the exec command coming through: I also see these suspicious kubelet soon afterwards: So I think the grep command is causing the node to run out of memory and get evicted. I think we can fix this either by: Making the grep command more memory efficient. I'm guessing it's reading the whole file into memory or, Make this test Serial so that it doesn't run in parallel with other pods, since it consumes a lot of memory.\nAn unrelated issue, is that the node allocatable feature didn't actually evict the pod. Instead this pod got a system OOM kill. /cc\nrelated to the memcg notifications, not node allocatable. Thanks!\nany theories why we see this only for the nfs-io tests, and not the glusterfs-io test for instance?\nthe gluster test didn't run on this in this suite.", "commid": "kubernetes_issue_51717", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-62fe9de90eb340bf529cbe0e17b4f66ceeedebf0618fa419b4e9347d0a763e19", "query": "}) It(\"should write files of various sizes, verify size, validate content\", func() { <del> fileSizes := []int64{1 * framework.MiB, 100 * framework.MiB} </del> <ins> fileSizes := []int64{fileSizeSmall, fileSizeMedium} </ins> fsGroup := int64(1234) podSec := v1.PodSecurityContext{ FSGroup: &fsGroup,", "positive_passages": [{"docid": "doc-en-kubernetes-fd4ca8cfd935058701597731533334687f2913bf0b9d409a83f3ac801f0182e1", "text": "I'm suspecting that the reason why we didn't see a problem with this test on other suites is that the load could be higher here. I've asked to see if we can reduce the memory usage of the grep call.\npointed out that there are no newlines in the generated file, so when grep is called it could buffer the entire file in memory. Adding a newline at the end of the dd input file should do it.\n/priority critical-urgent\n[MILESTONENOTIFIER] Milestone Labels Complete Issue label settings: sig/scalability sig/storage: Issue will be escalated to these SIGs if needed. priority/critical-urgent: Never automatically move out of a release milestone; continually escalate to contributor and SIG through all available channels. kind/bug: Fixes a bug discovered during the current release. <detailsAdditional instructions available <a href=\"\"here</a</details\nIt seems like even if the generated file is broken up by newlines, grep could still use on the order of hundreds of MB of memory for a 100MiB file (even with the -m1 and -F options). We could check the file line by line, but it would take a long time. A better solution would be to check the MD5 file hash. It's fast and uses little memory. The expected hashes will be hard-coded into the test, and if different file sizes are in the future, a hash needs to be computed and as well.\nThanks a lot for fixing this!\nRef", "commid": "kubernetes_issue_51717", "tokennum": 322}], "negative_passages": []}
{"query_id": "q-en-kubernetes-630c4d56343abe9d5052b745860bdf7ad23839937dd71ceee3228bbdb340d51f", "query": "(disk.ManagedDisk != nil && diskURI != \"\" && strings.EqualFold(*disk.ManagedDisk.ID, diskURI)) { // found the disk klog.V(2).Infof(\"azureDisk - detach disk: name %q uri %q\", diskName, diskURI) <del> disks[i].ToBeDetached = to.BoolPtr(true) </del> <ins> if strings.EqualFold(as.cloud.Environment.Name, \"AZURESTACKCLOUD\") { disks = append(disks[:i], disks[i+1:]...) } else { disks[i].ToBeDetached = to.BoolPtr(true) } </ins> bFoundDisk = true break }", "positive_passages": [{"docid": "doc-en-kubernetes-5bed2d3142dabe6e3fc7269ef850324d324032cbc87a456c8f2e9b79085fd590", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: flag is not supported on Azure Stack, should switch to use original way to remove a disk from data disk list, refer to for more details What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others: /kind bug /assign /priority important-soon /sig cloud-provider /area provider/azure", "commid": "kubernetes_issue_94886", "tokennum": 186}], "negative_passages": []}
{"query_id": "q-en-kubernetes-632406f1bac16cb044c1814620ff5c36b0e9a2f3d1a15cb63237a7b9085e04ea", "query": "klog.Errorf(\"cannot convert to *v1.Node: %v\", t) return } <ins> klog.V(3).Infof(\"delete event for node %q\", node.Name) </ins> // NOTE: Updates must be written to scheduler cache before invalidating // equivalence cache, because we could snapshot equivalence cache after the // invalidation and then snapshot the cache itself. If the cache is", "positive_passages": [{"docid": "doc-en-kubernetes-671a12759d851f1b99028bc477360c418e1157a45a2e814ff1c5c1cdd09da36a", "text": "This helps debugging scheduler's behavior, currently we don't have logs that indicate when the scheduler first saw a pod or a node. The log level should be v=3. /sig scheduling /cc\nDo you mean add logging for callbacks in ?\nyes, at least for add and delete events\nSure, I can also give this pr, before tomorrow\n/assign\nWe actually have one v=2 log line for a Node being to the cache's tree: But it's probably good to keep this one.", "commid": "kubernetes_issue_87524", "tokennum": 111}], "negative_passages": []}
{"query_id": "q-en-kubernetes-63599030d8572160dd248513336ef4f7abed60bb5e0354ae56f24e72b736b142", "query": "package fake <ins> import ( \"fmt\" \"k8s.io/apimachinery/pkg/util/rand\" ) </ins> const ( <del> defaultUnixEndpoint = \"unix:///tmp/kubelet_remote.sock\" </del> <ins> defaultUnixEndpoint = \"unix:///tmp/kubelet_remote_%v.sock\" </ins> ) // GenerateEndpoint generates a new unix socket server of grpc server. func GenerateEndpoint() (string, error) { <del> return defaultUnixEndpoint, nil </del> <ins> // use random int be a part fo file name return fmt.Sprintf(defaultUnixEndpoint, rand.Int()), nil </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-a55cc9cf23a1aa66af6ba96638da8c1361b9b34938bf9fbe2ee98dcb858f1383", "text": "Which jobs are flaking: periodics-kubernetes-bazel-test Which test(s) are flaking: //pkg/kubelet/cri/remote TestVersion Testgrid link: Reason for failure: Error: Received unexpected error: rpc error: code = Unavailable desc = transport is closing panic: runtime error: invalid memory address or nil pointer dereference [recovered] panic: runtime error: invalid memory address or nil pointer dereference Anything else we need to know: To reproduce with stress: go test -race -c ./pkg/kubelet/cri/remote stress - TestVersion Detailed logs\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig testing\nI 'll give it a see and fix it :)\n/assign\n/remove-sig testing SIG node owns their unit tests. SIG testing owns the framework, infrastructure, etc.\n/sig node", "commid": "kubernetes_issue_96950", "tokennum": 277}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6359e75e50828a8310dc919fcb98d20678167e99caf3705180fa88b000bcb5dc", "query": "return true, errors.New(\"not implemented\") } <ins> func (m *execMounter) EvalHostSymlinks(pathname string) (string, error) { return \"\", errors.New(\"not implemented\") } </ins> func (mounter *execMounter) PrepareSafeSubpath(subPath Subpath) (newHostPath string, cleanupAction func(), err error) { return subPath.Path, nil, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-226c0928db9d5aa6f1446838b8788eb7c60cd41b1b8246f4bd1a4e2614bb7834", "text": "/kind bug Using , if a block device is symlinked to the discovery directory e.g. , then MapVolume will fail with since the containerized kubelet cannot see the path on host. is mounted by containerized kubelet, so if before we try to map the device we set devicePath to the evaluation of symlink and end up with a devicePath of , containerized kubelet will see the device and successfully map the device. Are there any issues with this solution? This is on Kubernetes 1.10\n/sig storage\nah yes containerized kubelet has many issues when dealing with symlinks. Check out Mounter.GetMode(), it calls a nsenter EvalSymlinks which should be able to do what you need. But actually, one thing to consider, is do you need to do the losetup on the host, or does inside the container work?\nYes it appears to work from inside the container, on the host I run which disappears after I delete the pod using the device. My understanding of running losetup in MapVolume is not that great but I suppose that as long as that /dev/loop0 is created we are fine. Thanks for the quick response, I'll create a PR using that function and tag you\nDoes it create it on the host or in the containerized kubelet? What happens when containerized kubelet is restarted? The purpose of losetup is to do \"refcounting\" on the block device to prevent possible naming collisions when devices are attached/detached under unhealthy conditions. Ie, if a device showed up as /dev/sdb and you gave that to a pod, and then for some reason it become unhealthy and disappeared (while the pod is still running), another device (maybe even another volume type) could get attached to the node and reuse /dev/sdb. Now the pod has access to a device it's not supposed to. With filesystem volumes, the refcounting is done with mount points, but for block device, loopback is the equivalent.\nIt is created on the host (and also visible in the container), and stays around through restart. I understand now, thank you.\nActually after I restart it becomes /vdb instead of /dev/vdb in the losetup output, idk what that is about.", "commid": "kubernetes_issue_65445", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6359e75e50828a8310dc919fcb98d20678167e99caf3705180fa88b000bcb5dc", "query": "return true, errors.New(\"not implemented\") } <ins> func (m *execMounter) EvalHostSymlinks(pathname string) (string, error) { return \"\", errors.New(\"not implemented\") } </ins> func (mounter *execMounter) PrepareSafeSubpath(subPath Subpath) (newHostPath string, cleanupAction func(), err error) { return subPath.Path, nil, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-e6271b0ba1dda755d5bb536a727016a621c7c29c599386bc1e9c22a230980cbf", "text": "There is no such thing as /vdb and /dev/vdb is still intact of course. Seems inconsequential since it is disappearing after all pods using the device are deleted, i.e. it's still serving as a refcounter", "commid": "kubernetes_issue_65445", "tokennum": 55}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6390b3fd7342548749cf24fa921b501d67c9a944ca357799bd72e81b5db58295", "query": "Description: The command 'kubectl version' MUST return the major, minor versions,  GitCommit, etc of the Client and the Server that the kubectl is configured to connect to. */ framework.ConformanceIt(\"should check is all data is printed \", func() { <del> version := framework.RunKubectlOrDie(ns, \"version\") requiredItems := []string{\"Client Version:\", \"Server Version:\", \"Major:\", \"Minor:\", \"GitCommit:\"} </del> <ins> versionString := framework.RunKubectlOrDie(ns, \"version\") // we expect following values for: Major -> digit, Minor -> numeric followed by an optional '+',  GitCommit -> alphanumeric requiredItems := []string{\"Client Version: \", \"Server Version: \"} </ins> for _, item := range requiredItems { <del> if !strings.Contains(version, item) { framework.Failf(\"Required item %s not found in %s\", item, version) </del> <ins> if matched, _ := regexp.MatchString(item+`version.Info{Major:\"d\", Minor:\"d++?\", GitVersion:\"vd.d+.[dw-.+]+\", GitCommit:\"[0-9a-f]+\"`, versionString); !matched { framework.Failf(\"Item %s value is not valid in %sn\", item, versionString) </ins> } } })", "positive_passages": [{"docid": "doc-en-kubernetes-153297a62268f5892b05d52975dc41aef2505a641a424b2f4dec851bfaac7cd3", "text": "only check that the output includes the correct keys - they don't confirm that it has appropriate values. Doing full validation on the version data, or at least enough to catch null-string values, would guard against failures like the bad functionality seen in OpenSUSE's binaries, which have been shipping with many of the fields left completely blank (as I discovered ).\n/sig testing\n/remove-sig testing /sig cli Edit: testing owns the framework, binaries, infrastructure etc. for testing. SIG CLI is nominally responsible for their test cases.\nIf SIGs are responsible for their own testcases, then this touches test cases for api-machinery as well (I'm not sure what the non-CLI version of this is, but there's definitely a schema adherence test that should fail at the API level). /sig api-machinery\n/triage accepted /assign\nGitHub didn't allow me to assign the following users: SaiHarshaK. 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 : /triage accepted /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\n/assign", "commid": "kubernetes_issue_95297", "tokennum": 298}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6397ef63432ab62ac811d8d0722302e226ca00b70987307348e66041f37a38e9", "query": "// The first detach will be triggered after at least 50ms (maxWaitForUnmountDuration in test). // Right before detach operation is performed, the volume will be first removed from being reported // as attached on node status (RemoveVolumeFromReportAsAttached). After detach operation which is expected to fail, <del> // controller then added the volume back as attached. </del> <ins> // controller then treats the attachment as Uncertain. </ins> // Here it sleeps 100ms so that detach should be triggered already at this point. <del> // verifyVolumeReportedAsAttachedToNode will check volume is in the list of volume attached that needs to be updated // in node status. By calling this function (GetVolumesToReportAttached), node status should be updated, and the volume // will not need to be updated until new changes are applied (detach is triggered again) </del> time.Sleep(100 * time.Millisecond) <del> verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw, volumeAttachedCheckTimeout) </del> <ins> verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateUncertain, asw) verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, false, asw, volumeAttachedCheckTimeout) </ins> // Add a second pod which tries to attach the volume to the same node. <del> // After adding pod to the same node, detach will not be triggered any more. </del> <ins> // After adding pod to the same node, detach will not be triggered any more, // the volume gets attached and reported as attached to the node. </ins> generatedVolumeName, podAddErr = dsw.AddPod(types.UniquePodName(podName2), controllervolumetesting.NewPod(podName2, podName2), volumeSpec, nodeName1) if podAddErr != nil { t.Fatalf(\"AddPod failed. Expected: <no error> Actual: <%v>\", podAddErr)", "positive_passages": [{"docid": "doc-en-kubernetes-2a1f139ca790a16bd0882043a2e2916760e4c33264d1a31f1254bc354f4822db", "text": "After KCM restart, any Pod that reuses a volume that failed to detach gets stuck ContainerCreating with message: User \"system:node:ip-10-0-243-\" cannot get resource \"volumeattachments\" in API group \"\" at the cluster scope: no relationship found between node 'ip-10-0-243-' and this object See steps to reproduce below, it's quite a complex condition. It happens when a pod is restarted, a CSI driver \"busy\" (i.e. times out) + KCM restarted at a wrong time. Pods start just fine. a Pod that uses an attachable CSI volume. the Pod. Make sure it unmounts successfully, but any fails with a transient error, such as timeout. The external attacher continues to detach the volume at this point. kube-controller-manager (KCM) and start a new one. Wait for any leader election etc - it's important for the new KCM to populate A/D controller with no pod using the detaching volume. Let the A/D controller to observe detach error. a new Pod on the same node that uses the same volume. the CSI driver to detach the volume (i.e. stop injecting any transient errors). At this point: The external attacher succeeds detaching the volume, VolumeAttachment is deleted. The volume is marked as attached in node status (!!!) despite no VolumeAttachment exists. A/D controller does not even try to create a new VolumeAttachment, the volume is marked as attached in its Actual State of World (ASW). Kubelet tries to mount the volume, but WaitForAttach fails with: , basically forever. I created . The script expects that the cluster is created by , because it restarts KCM in the middle. It uses my hacked hostpath CSI driver to inject detach errors. Sources are at / the last commit(s) there. There are two issues that together lead to this situation: fails, , i.e. puts it back to . With the volume in , kubelet may try to mount it, while the external attacher tries to detach it. It is not as bad as it sounds, because kubelet can't read VolumeAttachment with the deletion timestamp and it will not call / of un-attached volume.", "commid": "kubernetes_issue_120571", "tokennum": 509}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6397ef63432ab62ac811d8d0722302e226ca00b70987307348e66041f37a38e9", "query": "// The first detach will be triggered after at least 50ms (maxWaitForUnmountDuration in test). // Right before detach operation is performed, the volume will be first removed from being reported // as attached on node status (RemoveVolumeFromReportAsAttached). After detach operation which is expected to fail, <del> // controller then added the volume back as attached. </del> <ins> // controller then treats the attachment as Uncertain. </ins> // Here it sleeps 100ms so that detach should be triggered already at this point. <del> // verifyVolumeReportedAsAttachedToNode will check volume is in the list of volume attached that needs to be updated // in node status. By calling this function (GetVolumesToReportAttached), node status should be updated, and the volume // will not need to be updated until new changes are applied (detach is triggered again) </del> time.Sleep(100 * time.Millisecond) <del> verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw, volumeAttachedCheckTimeout) </del> <ins> verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateUncertain, asw) verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, false, asw, volumeAttachedCheckTimeout) </ins> // Add a second pod which tries to attach the volume to the same node. <del> // After adding pod to the same node, detach will not be triggered any more. </del> <ins> // After adding pod to the same node, detach will not be triggered any more, // the volume gets attached and reported as attached to the node. </ins> generatedVolumeName, podAddErr = dsw.AddPod(types.UniquePodName(podName2), controllervolumetesting.NewPod(podName2, podName2), volumeSpec, nodeName1) if podAddErr != nil { t.Fatalf(\"AddPod failed. Expected: <no error> Actual: <%v>\", podAddErr)", "positive_passages": [{"docid": "doc-en-kubernetes-86a0f830cda4a62b3e964f9aa561f07fe82e259bc1038677353226e3d67190fe", "text": "KCM starts, all VolumeAttachments that don't have a Pod (that's good), but also (that's probably bad). When the newly started KCM re-tries to detach the volume and gets an error again, it marks the volume as fully attached (same as the previous point) and adds it to . Now the volume is both mounted + attached in ASW and A/D controller actually stops here and waits forever for kubelet to unmount the volume. <detailsToday's k/k master, </details<detailsNone </details<detailsN/A, it's KCM issue. </details<details, but seen in a downstream Kubernetes distro too. </details<details</details<details</details\n/sig storage\n/assign\n/triage accepted\nI have the same problem: Seems restart of Kubelet solves this problem. Kubernetes v1.25.13", "commid": "kubernetes_issue_120571", "tokennum": 208}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6398f05f53e21a4a003affb78bf401e649c93bdba2dce138c81d4ee0e0662ccf", "query": "eventRecorder := record.NewFakeRecorder(100) eventRecorder.IncludeObject = true <del> metadataClient := fakemetadata.NewSimpleMetadataClient(legacyscheme.Scheme) </del> <ins> metadataClient := fakemetadata.NewSimpleMetadataClient(fakemetadata.NewTestScheme()) </ins> tweakableRM := meta.NewDefaultRESTMapper(nil) tweakableRM.AddSpecific(", "positive_passages": [{"docid": "doc-en-kubernetes-d7e6fda1614d5720cc8c8b15824f08c5e880f7950d0c5cc5cd811c2fcceb82ab", "text": "Because of this scheme mutation, this leads to concurrent use of the same scheme to cause the program to panic. It would be ideal to do this in some concurrent safe manner or add a warning or similar\n/sig api-machinery\n/assign\n/assign /triage accepted", "commid": "kubernetes_issue_107823", "tokennum": 54}], "negative_passages": []}
{"query_id": "q-en-kubernetes-63ab684902c6393fb60627763290fe3fc53a3311863fe9c305a6362e3ad9c9d1", "query": "} labels[\"e2e-run\"] = string(RunId) <ins> // We don't use ObjectMeta.GenerateName feature, as in case of API call // failure we don't know whether the namespace was created and what is its // name. name, err := findAvailableNamespaceName(baseName, c) if err != nil { return nil, err } </ins> namespaceObj := &v1.Namespace{ ObjectMeta: metav1.ObjectMeta{ <del> GenerateName: fmt.Sprintf(\"e2e-tests-%v-\", baseName), Namespace:    \"\", Labels:       labels, </del> <ins> Name:      name, Namespace: \"\", Labels:    labels, </ins> }, Status: v1.NamespaceStatus{}, }", "positive_passages": [{"docid": "doc-en-kubernetes-754a337748c77aa830912aa5c369fd083977cc37177bb1280fd450d5c939bfe3", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: In the test failed due to namespace leakage: we created e2e-tests-load-30-nodepods-1-pfn9m, but never got response from api server (got 0-length response instead) we retried and created e2e-tests-load-30-nodepods-1-m9tq5 e2e-tests-load-30-nodepods-1-m9tq5 to f.namespacesToDelete and leaked -pfn9m next test case failed because e2e-tests-load-30-nodepods-1-pfn9m wasn't deleted. What you expected to happen: While it's unclear why we got 0-length response instead ( investigates that), we always can get error while the namespace was created (e.g. connection reset, timeout, io error). We should handle this case in retrying correctly. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.14.0-alpha.0.793+ Cloud provider or hardware configuration: gce OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: <!-- DO NOT EDIT BELOW THIS LINE --/kind bug\nThere are no sig labels on this issue. Please add a sig label by either: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. See the . The in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals. <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\n/cc", "commid": "kubernetes_issue_71697", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-63ac67d9710f04e408545c9f5a2187e4cf811d7a219491ce74de582a7364b638", "query": "if err := os.WriteFile(certFixturePath, certBuffer.Bytes(), 0644); err != nil { return nil, nil, fmt.Errorf(\"failed to write cert fixture to %s: %v\", certFixturePath, err) } <del> if err := os.WriteFile(keyFixturePath, keyBuffer.Bytes(), 0644); err != nil { </del> <ins> if err := os.WriteFile(keyFixturePath, keyBuffer.Bytes(), 0600); err != nil { </ins> return nil, nil, fmt.Errorf(\"failed to write key fixture to %s: %v\", certFixturePath, err) } }", "positive_passages": [{"docid": "doc-en-kubernetes-02478d007e8fb94d5569c598d90648b98c08e1979b9683524b76b29f0b58f1e9", "text": "Hello, the SRC folks asked that I file this publicly: In the client-go repo, , function creates a private key and stores it into a file with mode : Typically keys are created with more restrictive modes to prevent other users or services on the system from being able to copy them before the user fixes the permissions. Of course, if a more restrictive umask is in place, this may not be a big deal, but it's an extremely fickle piece of the environment to rely upon for security. It's better to be explicit. Thanks\n/kind bug Not sure if this is /sig api-machinery or /sig auth\nis this related to us?\nHi IMO, mode make sense for the key file. I would like to work on this, waiting for Thanks!!\n/triage accepted\n/assign\nThe 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]:\n/remove-lifecycle stale\n/lifecycle frozen /good-first-issue I think changing the code to use should be fine. Anyone is free to pick this up. Would be good to include a unit test.\nThis 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 : /lifecycle frozen /good-first-issue Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_110992", "tokennum": 505}], "negative_passages": []}
{"query_id": "q-en-kubernetes-63ac67d9710f04e408545c9f5a2187e4cf811d7a219491ce74de582a7364b638", "query": "if err := os.WriteFile(certFixturePath, certBuffer.Bytes(), 0644); err != nil { return nil, nil, fmt.Errorf(\"failed to write cert fixture to %s: %v\", certFixturePath, err) } <del> if err := os.WriteFile(keyFixturePath, keyBuffer.Bytes(), 0644); err != nil { </del> <ins> if err := os.WriteFile(keyFixturePath, keyBuffer.Bytes(), 0600); err != nil { </ins> return nil, nil, fmt.Errorf(\"failed to write key fixture to %s: %v\", certFixturePath, err) } }", "positive_passages": [{"docid": "doc-en-kubernetes-97af64e63f750f1585d6dae219445a2123c113559188cb8ace853ac6ec6d5ee9", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\nHello, this is my first ever open source contribution. I am trying to understand and get this fixed. Any suggestions would be helpful!\n/assign\n/assign", "commid": "kubernetes_issue_110992", "tokennum": 55}], "negative_passages": []}
{"query_id": "q-en-kubernetes-63d0d3e391df2c12d5b7850236f4660958c439c06b4f48ad892dcb141ad97a7e", "query": "\"//staging/src/k8s.io/cri-api/pkg/apis/testing:go_default_library\", \"//vendor/google.golang.org/grpc:go_default_library\", \"//vendor/k8s.io/utils/exec:go_default_library\", <del> ], </del> <ins> ] + select({ \"@io_bazel_rules_go//go/platform:aix\": [ \"//staging/src/k8s.io/apimachinery/pkg/util/rand:go_default_library\", ], \"@io_bazel_rules_go//go/platform:android\": [ \"//staging/src/k8s.io/apimachinery/pkg/util/rand:go_default_library\", ], \"@io_bazel_rules_go//go/platform:darwin\": [ \"//staging/src/k8s.io/apimachinery/pkg/util/rand:go_default_library\", ], \"@io_bazel_rules_go//go/platform:dragonfly\": [ \"//staging/src/k8s.io/apimachinery/pkg/util/rand:go_default_library\", ], \"@io_bazel_rules_go//go/platform:freebsd\": [ \"//staging/src/k8s.io/apimachinery/pkg/util/rand:go_default_library\", ], \"@io_bazel_rules_go//go/platform:illumos\": [ \"//staging/src/k8s.io/apimachinery/pkg/util/rand:go_default_library\", ], \"@io_bazel_rules_go//go/platform:ios\": [ \"//staging/src/k8s.io/apimachinery/pkg/util/rand:go_default_library\", ], \"@io_bazel_rules_go//go/platform:js\": [ \"//staging/src/k8s.io/apimachinery/pkg/util/rand:go_default_library\", ], \"@io_bazel_rules_go//go/platform:linux\": [ \"//staging/src/k8s.io/apimachinery/pkg/util/rand:go_default_library\", ], \"@io_bazel_rules_go//go/platform:nacl\": [ \"//staging/src/k8s.io/apimachinery/pkg/util/rand:go_default_library\", ], \"@io_bazel_rules_go//go/platform:netbsd\": [ \"//staging/src/k8s.io/apimachinery/pkg/util/rand:go_default_library\", ], \"@io_bazel_rules_go//go/platform:openbsd\": [ \"//staging/src/k8s.io/apimachinery/pkg/util/rand:go_default_library\", ], \"@io_bazel_rules_go//go/platform:plan9\": [ \"//staging/src/k8s.io/apimachinery/pkg/util/rand:go_default_library\", ], \"@io_bazel_rules_go//go/platform:solaris\": [ \"//staging/src/k8s.io/apimachinery/pkg/util/rand:go_default_library\", ], \"//conditions:default\": [], }), </ins> ) filegroup(", "positive_passages": [{"docid": "doc-en-kubernetes-a55cc9cf23a1aa66af6ba96638da8c1361b9b34938bf9fbe2ee98dcb858f1383", "text": "Which jobs are flaking: periodics-kubernetes-bazel-test Which test(s) are flaking: //pkg/kubelet/cri/remote TestVersion Testgrid link: Reason for failure: Error: Received unexpected error: rpc error: code = Unavailable desc = transport is closing panic: runtime error: invalid memory address or nil pointer dereference [recovered] panic: runtime error: invalid memory address or nil pointer dereference Anything else we need to know: To reproduce with stress: go test -race -c ./pkg/kubelet/cri/remote stress - TestVersion Detailed logs\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig testing\nI 'll give it a see and fix it :)\n/assign\n/remove-sig testing SIG node owns their unit tests. SIG testing owns the framework, infrastructure, etc.\n/sig node", "commid": "kubernetes_issue_96950", "tokennum": 277}], "negative_passages": []}
{"query_id": "q-en-kubernetes-63eb58428b481d1acdb569d945a415315555750065b4ba9424061982376b474d", "query": "gopkg.in/yaml.v3 v3.0.0-20200313102051-9f266ea9e77c/go.mod h1:K4uyk7z7BCEPqu6E+C64Yfv1cQ7kz7rIZviUmN+EgEM= honnef.co/go/tools v0.0.0-20190102054323-c2f93a96b099/go.mod h1:rf3lG4BRIbNafJWhAfAdb/ePZxsR/4RtNHQocxwk9r4= honnef.co/go/tools v0.0.0-20190523083050-ea95bdfd59fc/go.mod h1:rf3lG4BRIbNafJWhAfAdb/ePZxsR/4RtNHQocxwk9r4= <ins> k8s.io/klog/v2 v2.80.1 h1:atnLQ121W371wYYFawwYx1aEY2eUfs4l3J72wtgAwV4= k8s.io/klog/v2 v2.80.1/go.mod h1:y1WjHnz7Dj687irZUWR/WLkLc5N1YHtjLdmgWjndZn0= </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-82432c9a9613bf4aed980cc8db469ba43857eb8e48c1e0dd0f39492115206ab6", "text": "generation for local KEK based on counter; also rotate once a week even if the counter does not hit 2 million? using AES-GCM encryption of local KEK ref: The implementation would be to the directory.\n/sig auth /triage accepted\n/assign\nGitHub didn't allow me to assign the following users: ibihim. 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\n/assign\nthank you !\n/milestone v1.26\nHi bug-triage shadow team member for 1.26 here. Looks like this issue is in the 1.26 milestone, but has been moved to 1.27. Is there something else or should this issue go to 1.27 as well? Thank you!\nI just forgot to move this issue /milestone v1.27\n/reopen is the partial implementation.\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nMy suggestion on the reference implementation, after reading 's comments is like so... The GRPC server, which implements the expects an implementation that satisfies . The local key logic can be a middleware. So it expects a it can fallback to, if it doesn't know a key or needs to encrypt its own local KEK. So the local implementation would be need to: have a storage of s have a reference to the current in use (if we put it into the cache, it might vanish) have a reference to another , which should be the remote KMS. So the sub-stories could look like: write Middleware write Transformers that can get exhausted (by time, by usage) write 's storage write some dummy for remote KMS? I have some sketches of what I am talking about .", "commid": "kubernetes_issue_112859", "tokennum": 462}], "negative_passages": []}
{"query_id": "q-en-kubernetes-63eb58428b481d1acdb569d945a415315555750065b4ba9424061982376b474d", "query": "gopkg.in/yaml.v3 v3.0.0-20200313102051-9f266ea9e77c/go.mod h1:K4uyk7z7BCEPqu6E+C64Yfv1cQ7kz7rIZviUmN+EgEM= honnef.co/go/tools v0.0.0-20190102054323-c2f93a96b099/go.mod h1:rf3lG4BRIbNafJWhAfAdb/ePZxsR/4RtNHQocxwk9r4= honnef.co/go/tools v0.0.0-20190523083050-ea95bdfd59fc/go.mod h1:rf3lG4BRIbNafJWhAfAdb/ePZxsR/4RtNHQocxwk9r4= <ins> k8s.io/klog/v2 v2.80.1 h1:atnLQ121W371wYYFawwYx1aEY2eUfs4l3J72wtgAwV4= k8s.io/klog/v2 v2.80.1/go.mod h1:y1WjHnz7Dj687irZUWR/WLkLc5N1YHtjLdmgWjndZn0= </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-b75b4d558a76c05a2f299aa9e4208bfe14cbcf4125785eeef841ee037778035f", "text": "I would implement that in terms of the interface so that it can be used both in testing (via a local key) and in real code (by delegating to a HSM).\nHi bug-triage team member for 1.27 here. This issue is still open but has had no recent activity, and no active PRs. Is everything on track for the Code Freeze in March 14th? Thank you!\n/milestone clear\nCould be closed, right? :)\nWe still need metrics and tracing support for the reference implementation (though it is all a lot less important now).\n/retitle [KMSv2] Add metrics and tracing in for plugins\nThis is duplicate of /close\nClosing this issue. <detailsIn response to : This is duplicate of 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", "commid": "kubernetes_issue_112859", "tokennum": 192}], "negative_passages": []}
{"query_id": "q-en-kubernetes-63f9f4b3c8e0644fc80ef159d429eab7bc8703d29b692cc95d28ed4cd3dcde24", "query": "_, err = client.CoreV1().Pods(defaultNamespace).List(ctx, metav1.ListOptions{}) tt.assertErrFn(t, err) <del> err = os.WriteFile(apiServer.ServerOpts.Authentication.AuthenticationConfigFile, []byte(tt.newAuthConfigFn(t, oidcServer.URL(), string(caCert))), 0600) </del> <ins> // Create a temporary file tempFile, err := os.CreateTemp(\"\", \"tempfile\") require.NoError(t, err) defer func() { _ = tempFile.Close() }() // Write the new content to the temporary file _, err = tempFile.Write([]byte(tt.newAuthConfigFn(t, oidcServer.URL(), string(caCert)))) require.NoError(t, err) // Atomically replace the original file with the temporary file err = os.Rename(tempFile.Name(), apiServer.ServerOpts.Authentication.AuthenticationConfigFile) </ins> require.NoError(t, err) if tt.waitAfterConfigSwap {", "positive_passages": [{"docid": "doc-en-kubernetes-6a9e001ff60e5ca04752d0e51696e4d68773c676c7cdd69e5d88aa83e0129d5a", "text": "=== RUN TestStructuredAuthenticationConfigReload/oldinvalidconfigtonewvalidconfig first seen in 3/11 No response /sig api-machinery instrumentation\n/sig auth /remove-sig api-machinery instrumentation /triage accepted /assign", "commid": "kubernetes_issue_123855", "tokennum": 65}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6407ef9174bca7bea22a79b3af3f16442b67a0f815a0fe29c653152c378b5f15", "query": "} } <del> allErrs = append(allErrs, validateValueValidation(s.ValueValidation, skipAnyOf, skipFirstAllOfAnyOf, fldPath)...) </del> <ins> allErrs = append(allErrs, validateValueValidation(s.ValueValidation, skipAnyOf, skipFirstAllOfAnyOf, lvl, fldPath)...) </ins> if s.XEmbeddedResource && s.Type != \"object\" { if len(s.Type) == 0 {", "positive_passages": [{"docid": "doc-en-kubernetes-4be11de3bdb9e2a86ad3a19c4d6f5342db422d48e5979c118fca9ce077f64900", "text": "We allow CRD authors to write . Currently we don't restrict writing validation for , which means people can have . For example, people can have additive name constraints (require CR to be ) with the following schema: This brings us two questions: do we if \"metadata\" is included in the schema: simplest option is to publish standard metav1.ObjectMeta schema info, and use any CRD-specified \"metadata\" properties as additive validation (just like in-tree types do, publishing standard ObjectMeta schema info, and implementing type-specific name validation internally) alternatively, we can try merging user-specified metadata schema with the standard one. Technically people should only add extra validation to existing metadata properties (adding new fields to metadata won't work since they will be pruned by built-in validation first), but it's unclear to me how arbitrary people may want the metadata validation to be term question is whether to allow people specifying metadata validation at all, or just allow a subset (like name validation) in CRD v1 /sig api-machinery /area custom-resources cc\nWhat is the difference between these two? I mean the end result is the same right? The only thing that can be is validation. Nothing else works unless you are considering extensions?\nThe former means we drop/hide user-specified metadata schema when we publish CRD OpenAPI. We still validate user-specified constraints on server side, but client-side validation won't see them. The latter enables client-side user-specified metadata validation.\nIf it's possible to merge with standard metadata schema info, or at the cost of not publishing the standard schema. My inclination would be to publish the complete standard schema for metadata/apiVersion/kind, which we know is complete and accurate, and use and user-specified schema for those fields as addition validations server side", "commid": "kubernetes_issue_74620", "tokennum": 396}], "negative_passages": []}
{"query_id": "q-en-kubernetes-641546cfd5c9ec07847705d2bfd4e0c35829bc67daca08a064ca05d6e1734887", "query": "if err != nil { return fmt.Errorf(\"watch error:%v for volume %v\", err, volumeHandle) } <del> var watcherClosed bool ch := watcher.ResultChan() defer func() { if !watcherClosed { watcher.Stop() } }() </del> <ins> ch := watcher.ResultChan() defer watcher.Stop() </ins> for { select { case event, ok := <-ch:", "positive_passages": [{"docid": "doc-en-kubernetes-bf4acf56a8324d5d9229417a25d2febc989c56201f9f4bdce8fffe7a46728546", "text": "A CSI plugin that the 1.10 controller manager can't detect (which could occur in a number of scenarios, such as when a rollout is being performed or a node is evacuated) seems to retry without backoff. In this case, I have a pod referencing a PVC -PV that references my CSI plugin, but no controller plugin running. The controller is probing every 100ms continuously for a single volume attachment. The controller should backoff. Have not tested with higher numbers of pods, but in a busy system this could cause the controller manager to burn CPU. Also, there isn't actually a great error telling the user why the probing is happening (I knew in this case, but an admin likely has no idea).\n/assign\nIssues 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\n/remove-lifecycle stale /milestone v1.14 adding it to next milestone as per if it doesn't make it then it can be further moved\nas KEP has been moved, unless an exception is made, /milestone v1.15\nthe linked kep above is unrelated to this issue. This is a bug and I don't think it needs an associated enhancement\nsorry, got diverted by the comments on that KEP. /milestone v1.14\nHello from Bug Triage Shadow . I'd like to remind that code freeze is coming in 3 days (Friday, 8th March). Is this still planned to be fixed for 1.14?\nWe have not been tracking this for 1.14. /assign can you help triage and see if this is still an issue and if there is a quick fix?\nI can't reproduce the issue, do you remember what you did? From the logs it seems that Watch channel consistently returns so new is called recursively (beware, 1.10 code, but it's very similar in master): Can it produce fairly stable 100ms delay between calls? Anyway, this is not usual code path, watcher does not return in most cases.", "commid": "kubernetes_issue_64952", "tokennum": 478}], "negative_passages": []}
{"query_id": "q-en-kubernetes-641546cfd5c9ec07847705d2bfd4e0c35829bc67daca08a064ca05d6e1734887", "query": "if err != nil { return fmt.Errorf(\"watch error:%v for volume %v\", err, volumeHandle) } <del> var watcherClosed bool ch := watcher.ResultChan() defer func() { if !watcherClosed { watcher.Stop() } }() </del> <ins> ch := watcher.ResultChan() defer watcher.Stop() </ins> for { select { case event, ok := <-ch:", "positive_passages": [{"docid": "doc-en-kubernetes-386907f979b2ab6cc28dd5590343cbf2830e874540a448be35232bf4673dff7e", "text": "if I read the code correctly, such recursive must end up with timeout - caller does not care about return value and caller's watch probably won't return anything useful. Is there a reason why we don't return error? This will kick in exponential backoff in A/D controller.\nclearing the milestone for tracking purposes to let the fix land in its own time /milestone clear\nIssues 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\nI found the error would happen when a pv is attahing(volumeattachment has created) and the csi-attacher is deleted at the same time. Then the log would print so frequently (because of recursion).\nis this fixed by ?\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nClosing 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", "commid": "kubernetes_issue_64952", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-64348926d5386e5fd569284711718dcb27f5bd68083b620e895d6dc4cda1866c", "query": "<ins> FROM debian:jessie RUN apt-get update RUN apt-get -qy install python-seqdiag make curl WORKDIR /diagrams RUN curl -sLo DroidSansMono.ttf https://googlefontdirectory.googlecode.com/hg/apache/droidsansmono/DroidSansMono.ttf ADD . /diagrams CMD bash -c 'make >/dev/stderr && tar cf - *.png' </ins>  No newline at end of file", "positive_passages": [{"docid": "doc-en-kubernetes-3871d24647a528f2ff7df25634241fd3cde165662602f0e95a0cba53fe987aee", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug /priority failing-test /area test-infra What happened: job is failing. See https://k8s- https://k8s- https://k8s- https://k8s- What you expected to happen: test should pass\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/assign\nReiterating the mentions to trigger a notification: <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\nI'm guessing that something got messed up in the bazel cache when reverting from 0.5.2 to 0.4.5. I'm not sure how best to fix.\nHow about updating everything to bazel 0.5.3 at once? I know you're trying to do a step-by-step approach to avoid breakages, but I suspect it will be cheaper to just deal with a brief outage while we update? (aka update the bazelbuild image to 0.5.3 and then merge your PR with updated and working BUILD rules?)\nthere's at least one other issue I've discovered with the latest go rules - the binary no longer works, due to changes introduced in that might be arguably better (at least everything still builds?), though it's frustrating that it makes things more broken in a different way.", "commid": "kubernetes_issue_49844", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-64a3cfcaef8158c056f1028ad68ad5dacfeab06dbd510e87eefe0e5b11e9c4a5", "query": "export FAIL_ON_GCP_RESOURCE_LEAK=\"false\" - 'gce-flannel': description: 'Run E2E tests on GCE using Flannel and the latest successful build. This suite is quarantined in a dedicated project because Flannel integration is experimental.' <ins> disable_job: true  # Issue #24520 </ins> # We don't really care to enforce a timeout for flannel tests. Any performance issues will show up in the other GCE builders. # This suite is to continuously check that flannel + Kubernetes works. timeout: 120", "positive_passages": [{"docid": "doc-en-kubernetes-799a55cc839cd2ff4d6d16e3e37eb2f6d3baf0c870165e5d680f29079df92f3e", "text": "and show that we run this job every few minutes, but it never passes. I'm going to send out a PR to disable this job until someone has the time to investigate and resolve.\nIt's failing before tests even start:\nAt this point I don't think it's a flake, we needed flannel for a release and it's less important now so I'm not investigating why the cluster isn't coming up soon. I do believe if the cluster comes up a majority if not all of the tests will pass, and the ones that don't will flake for known reasons.", "commid": "kubernetes_issue_24520", "tokennum": 128}], "negative_passages": []}
{"query_id": "q-en-kubernetes-64aed225b31f5566fdcd522d235959dbfa6315616ecabcf577dc3ca95ee1f1d7", "query": "\"//pkg/api/v1/endpoints:go_default_library\", \"//staging/src/k8s.io/api/core/v1:go_default_library\", \"//staging/src/k8s.io/api/discovery/v1alpha1:go_default_library\", <ins> \"//staging/src/k8s.io/apimachinery/pkg/api/equality:go_default_library\", </ins> \"//staging/src/k8s.io/apimachinery/pkg/api/errors:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/apis/meta/v1:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/runtime:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-12f7047d8d873a7d6bac7023fc38517c350449071b3fe2b6d53f3ea14de5351f", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: EndpointSlice for masters was not created after enabling EndpointSlice on a pre-existing cluster. Only those EndpointSlices managed by kube-controller-manager were created. What you expected to happen: EndpointSlice for masters should be created after enabling EndpointSlice on a pre-existing cluster, the same as the EndpointSlices managed by kube-controller-manager. How to reproduce it (as minimally and precisely as possible): kubeadm to create a cluster: the EndpointSlice feature by editing the kube-apiserver, kube-controller-manager, kube-proxy manifest kube-apiserver and kube-controller-manager is restarted, the EndpointSlice in namespace will be missing. Anything else we need to know?: Environment: Kubernetes version (use ):Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools:Network plugin and version (if this is a network-related bug): Others:\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/remove-triage unresolved /assign", "commid": "kubernetes_issue_84419", "tokennum": 307}], "negative_passages": []}
{"query_id": "q-en-kubernetes-64b6ba010143fc7500330b7ddce2652bdfc939505cf55d3c75f97082eadd454f", "query": "$KUBECFG delete services/redismaster $KUBECFG delete pods/redis-master-2 <del> POD_LIST_2=$($KUBECFG '-template={{range.Items}}{{.Meta}} {{end}}' list pods) </del> <ins> POD_LIST_2=$($KUBECFG '-template={{range.Items}}{{.Name}} {{end}}' list pods) </ins> echo \"Pods running after shutdown: ${POD_LIST_2}\" exit 0", "positive_passages": [{"docid": "doc-en-kubernetes-ee80683e4fc8d1f9267feeed119de250fd6d0c3f47227cc07d302319c50cf3e7", "text": "What happened: is a subdirectory of the btrfs subvolume . kubelet fails to start with the following error: What you expected to happen: kubelet starts normally and doesn't fail with an error message How to reproduce it (as minimally and precisely as possible): Install a system using btrfs as file system for / Create a sub-volume for /var Start kubelet (even in disconnected mode) Anything else we need to know?: This is a follow-up issue of and has been promoted to fatal from onward, before it was a warning PR to fix the issue is Environment: Kubernetes version (use ): forward Cloud provider or hardware configuration: both bare metal and virtual OS (e.g. from /etc/os-release): SUSE 12+ or openSUSE (Tumbleweed/Leap) Kernel (e.g. ): Install tools: SUSE/openSUSE rpm Others:\n/sig storage\nfixed by /close\nIf I may - adding some notes - it might be helpful for others, until I get the time to do some more detailed tests and report a bug. I still had issues with kubelet not starting, with the same error - (version 1.13.4) My btrfs setup is that btrfs root is mounted at /, then I have also a subvolume /var and in it a subvolume /var/lib. The issue for me I think comes from the fact that I do not have a flat btrfs setup () but a nested one, and as such, I have as a mountpoint ONLY the root directory. Manually adding a mount entry for /var (heh - I should probably have mounted /var/lib) in /etc/fstab made it work: /var btrfs rw,relatime,ssd,space_cache,subvolid=259,subvol=/var 0 0` Also, even without this additional \"intermediate\" mount point I think it should have been working. I wonder if in , the loop 'for !found {' isn't exiting a tiny bit too fast (without testing for the root mountpoint itself) . Maybe it should be something like:\nHas something changed in the code? Kubelet from kubernetes 1.20.1 is failing. Doing a mount as I described above fixes it.\nsee (open) and (closed) - apparently this was recently fixed (but isn't released yet).", "commid": "kubernetes_issue_65204", "tokennum": 533}], "negative_passages": []}
{"query_id": "q-en-kubernetes-64e001cc52f5069c487c7bbc3fbe69afc497e2f48305b841ad5ca5792e9ff626", "query": "addBadCheck      bool }{ {\"?verbose\", \"[+]ping oknhealthz check passedn\", http.StatusOK, false}, <ins> {\"?exclude=dontexist\", \"ok\", http.StatusOK, false}, {\"?exclude=bad\", \"ok\", http.StatusOK, true}, {\"?verbose=true&exclude=bad\", \"[+]ping okn[+]bad excluded: oknhealthz check passedn\", http.StatusOK, true}, {\"?verbose=true&exclude=dontexist\", \"[+]ping oknwarn: some health checks cannot be excluded: no matches for \"dontexist\"nhealthz check passedn\", http.StatusOK, false}, </ins> {\"/ping\", \"ok\", http.StatusOK, false}, {\"\", \"ok\", http.StatusOK, false}, {\"?verbose\", \"[+]ping okn[-]bad failed: reason withheldnhealthz check failedn\", http.StatusInternalServerError, true},", "positive_passages": [{"docid": "doc-en-kubernetes-01cc291fb1d6afeae9b284d60dd407b578a72d26e4c50043cbdf654c92184c45", "text": "What would you like to be : Add support to the kube-apiserver so that we can disable health-checks via query params. Why is this needed: Currently, the healthz endpoint is inflexible in that any and all health checks are currently executed when the endpoint is hit. Since the kube-apiserver only currently supports a liveness check, this means all persistent health check failures will eventually result in a kubelet driven restart. However, this may not be desirable behavior if you have additional monitoring services layered on top of your control plane. For instance, take the etcd failure from the perspective of the kube-apiserver. Currently, persistent failures during the etcd health check from the api-server healthz endpoint will cause the kube-apiserver to be restarted. This sometimes helps (in the case of a faulty etcd-client connection) but also can be detrimental (the kube-apiserver restarts until the etcd cluster is functioning, then the kube-apiserver bombards the etcd cluster with requests to update local caches, saturating the etcd cluster with requests, causing it to timeout on its own liveness probes and trigger a kubelet-driven restart). Let's say that we could now disable etcd from our liveness health check. Then if we had an external monitoring service, we could ask independently ask etcd if it was healthy and we could also ask the kube-apiserver if it thought etcd was unhealthy. Based on the combination of those answers, we could enable more intelligent responses to certain situation, like restarting the kube-apiserver when it thought etcd was unhealthy but etcd was actually reporting as healthy but not doing so when etcd was actually unhealthy. This feature is backwards-compatible and opt-in. There would be no impact to existing behavior unless these query params are actually used. /sig api-machinery /kind feature\n/cc\nSGTM\n/assign", "commid": "kubernetes_issue_70591", "tokennum": 432}], "negative_passages": []}
{"query_id": "q-en-kubernetes-64e74624be6499077c6660754cbf34bbd86a3f51b4ba3cb8039e2c95980d3c58", "query": "Porter              = Config{e2eRegistry, \"porter\", \"1.0\"} PortForwardTester   = Config{e2eRegistry, \"port-forward-tester\", \"1.0\"} Redis               = Config{e2eRegistry, \"redis\", \"1.0\"} <del> ResourceConsumer    = Config{e2eRegistry, \"resource-consumer\", \"1.4\"} </del> <ins> ResourceConsumer    = Config{e2eRegistry, \"resource-consumer\", \"1.5\"} </ins> ResourceController  = Config{e2eRegistry, \"resource-consumer/controller\", \"1.0\"} ServeHostname       = Config{e2eRegistry, \"serve-hostname\", \"1.1\"} TestWebserver       = Config{e2eRegistry, \"test-webserver\", \"1.0\"}", "positive_passages": [{"docid": "doc-en-kubernetes-2d0ebe90b3c755e0edf33c6811bf431b4c51fd00f4f7b6a1d49649dd59cb487b", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: Used the endpoint /BumpMetric to create fake metrics for Prometheus. When I tried to curl /metrics I got the following response: Bad request. Not a POST request What you expected to happen: I expected to see something like this: # HELP info message. # TYPE gauge 0. How to reproduce it (as minimally and precisely as possible): Following the docs, after having it running inside kubernetes: Anything else we need to know?: Looks like introduced this by mistake. Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: <!-- DO NOT EDIT BELOW THIS LINE --/kind bug\n/sig testing", "commid": "kubernetes_issue_72403", "tokennum": 213}], "negative_passages": []}
{"query_id": "q-en-kubernetes-64f77bddadf74fb2432fbaf2bc1c467e47d7cf828e5ca436425ac45968697464", "query": "func (s *Controller) getNodeConditionPredicate() NodeConditionPredicate { return func(node *v1.Node) bool { <del> // We add the master to the node list, but its unschedulable.  So we use this to filter // the master. if node.Spec.Unschedulable { return false } </del> if s.legacyNodeRoleFeatureEnabled { // As of 1.6, we will taint the master, but not necessarily mark it unschedulable. // Recognize nodes labeled as master, and filter them also, as we were doing previously.", "positive_passages": [{"docid": "doc-en-kubernetes-932c798c1f1bc917ff850ea55bf430820901f4817711595aba278a9098d6e82b", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: What happened: In order to migrate to a new version of kubernetes on GKE. I cordoned(Kubectl cordon <node) all nodes in the old node pool(1.8.9) in order to drain the node pool(pods on the node) with an intention to cause the pods to run on a new version of the node pool(1.10.2). As soon as I cordoned all the nodes in the old node pool, it caused the downtime of ingress(nginx). The nginx controller pods where running fine on the cordoned node pool. But the cordon caused the nodes to be removed from the target pool of ingress load balancer. Below are the documents that suggest the above same method that I followed as best practice for zero downtime upgrade. 1). 2). What you expected to happen: I expected \"kubectl cordon <node\" not to have the node/s removed from the target pool of the loadbalancer because the nginx controller pods where running absolutely fine on these nodes. How to reproduce it (as minimally and precisely as possible): 1).Cordon all the nodes in an old node pool that runs nginx controller. Anything else we need to know?: Environment: Kubernetes version (use ): 1.10.2 Cloud provider or hardware configuration: GKE OS (e.g. from /etc/os-release): Container OS Kernel (e.g. ): 4.14.22+ Install tools: Others: Cordon causes to remove the nodes from the target pool of the ingress load balancer. The health checks fail on the nodes of the target pool, which should not be the case. Because the nginx controller pods run fine on these nodes.\nTechnically, this isn't a Kubernetes bug as this is working as intended; however, it does beg the question why we remove unschedulable nodes if they're marked as ready since we perform the to determine LB backend nodes. is it scheduable? is it not a master? is it not marked for exclusion? is it marked as ready?", "commid": "kubernetes_issue_65013", "tokennum": 511}], "negative_passages": []}
{"query_id": "q-en-kubernetes-64f77bddadf74fb2432fbaf2bc1c467e47d7cf828e5ca436425ac45968697464", "query": "func (s *Controller) getNodeConditionPredicate() NodeConditionPredicate { return func(node *v1.Node) bool { <del> // We add the master to the node list, but its unschedulable.  So we use this to filter // the master. if node.Spec.Unschedulable { return false } </del> if s.legacyNodeRoleFeatureEnabled { // As of 1.6, we will taint the master, but not necessarily mark it unschedulable. // Recognize nodes labeled as master, and filter them also, as we were doing previously.", "positive_passages": [{"docid": "doc-en-kubernetes-3337d8d773bd260e0255505bc31356b49bc0519e69eafd73453232de84478830", "text": "If any of those are a no, then it'll be removed from the pool on the next sync. Perhaps someone from can shed some light. /sig network\ncc This problem extends beyond GCP/ingress controller and to anyone using pools to upgrade nodes. A typical workflow I see is you'd cordon a node pool so as you drain each node the pods don't go to another node in the pool that'll shortly be drained as well. The current logic does not support that and complicates cluster administration because cordoning does not respect PDB's.\n/remove-sig apps /remove-sig gcp (since the service controller falls under sig networking)\nThose labels are not set on the issue: <detailsIn response to : /remove-sig apps /remove-sig gcp 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\nRef I thought a general practice for draining the old pool is to move over one node at a time in a rolling fashion. Shouldn't there always be certain backend pods being able to receive & serve traffic? cc\nWRT draining, it is recommended to do it one node at a time ; however, in real world scenarios doing it one node at a time can cause a lot of avoidable container churn if you don't cordon off the nodes you at least plan to drain so that pods aren't being scheduled on a node you'll be draining after the next one. According to the comments in the service controller it seems the unschedulable part exists because it was how we differentiated masters in the past; however, we have labels for that now. We also have the service exclusion label (can't find when/if that'll be promoted though as i don't think there's a ticket on it).\nI'm having problems with this issue as well. The fact that nodes are removed from target pools when cordoned means that I sometimes get brief interruptions of the traffic to a service when I cordon a node. I'm guessing the node isn't gracefully removed from the load balancer which results in some traffic being cut off trying to route through the recently cordoned node. The same problem occasionally happens when deleting nodes / node pools or when the cluster autoscaler deletes a node. We are running GKE ver. 1.10.2-gke.1.", "commid": "kubernetes_issue_65013", "tokennum": 523}], "negative_passages": []}
{"query_id": "q-en-kubernetes-64f77bddadf74fb2432fbaf2bc1c467e47d7cf828e5ca436425ac45968697464", "query": "func (s *Controller) getNodeConditionPredicate() NodeConditionPredicate { return func(node *v1.Node) bool { <del> // We add the master to the node list, but its unschedulable.  So we use this to filter // the master. if node.Spec.Unschedulable { return false } </del> if s.legacyNodeRoleFeatureEnabled { // As of 1.6, we will taint the master, but not necessarily mark it unschedulable. // Recognize nodes labeled as master, and filter them also, as we were doing previously.", "positive_passages": [{"docid": "doc-en-kubernetes-434e849b429a310bf0eaaee7ac5356c43a18352f5a8ac7f41c382993cffab77f", "text": "Our best defence against these issue have so far been to limit node changes as much as possible and not use any auto scaling.\nI've posted a question regarding this issue in SO some weeks before it was created. The suggested action was to use node taints () instead of cordon, that way nodes will still be marked as .\nThank you for the link, it Certainly helped. Perhaps, if thats the case(as mentioned in the accepted answer of the above link), then to cordon all the nodes of old node pools should not be a recommended action, at least in the GKE upgrade docs.\nonly says: And I can't find what more it does in the documentation. So I would expect that it has exactly the same behaviour as a taint. Why is removing running pods from the balancer working as intended? If it isn't a bug then the documentation is certainly unclear in this regard.\nThis just caused a major outage for us too. I agree with the previous posts, while this may be working as the code intended, it does not follow the patterns and documentation k8s provides. When I cordon a node it should not impact the traffic going to the node or any pods on it. I should be able to gradually remove traffic by draining nodes/pods and respecting PDBs.\nthis issue touches on the fact we are removing masters as well and inadvertently removing cordoned nodes. The logic in the service controller mentions we only filter out unschedulable nodes since that's how masters were setup.\nWe wanted to replace all of the kubernetes cluster nodes to different node instance types, so we started off by cordoning all of the nodes, but it surprisingly caused an outage for us. As pointed out, the only documentation around cordoning is , which I took to mean that new pods can not be scheduled on those nodes. It was surprising behavior to find out that, not only does it not allow new pods to be scheduled on those nodes, but that it also causes the service controller to remove unschedulable nodes from load balancing pools. I understand that it's working as intended, but if that was also documented as part of the cordon operation, I would have been able to avoid an outage.\nI finally caught up to this bug. Fun one. I agree that this is working-as-intended and that it stinks. We can do better.", "commid": "kubernetes_issue_65013", "tokennum": 496}], "negative_passages": []}
{"query_id": "q-en-kubernetes-64f77bddadf74fb2432fbaf2bc1c467e47d7cf828e5ca436425ac45968697464", "query": "func (s *Controller) getNodeConditionPredicate() NodeConditionPredicate { return func(node *v1.Node) bool { <del> // We add the master to the node list, but its unschedulable.  So we use this to filter // the master. if node.Spec.Unschedulable { return false } </del> if s.legacyNodeRoleFeatureEnabled { // As of 1.6, we will taint the master, but not necessarily mark it unschedulable. // Recognize nodes labeled as master, and filter them also, as we were doing previously.", "positive_passages": [{"docid": "doc-en-kubernetes-33075f048c6031b18ea2c4d42a5821aded2e74dadef5a72c2d24382b09d40a2a", "text": "As a short-term workaround, you can taint the nodes before cordoning one-by-one. That will stop new work from arriving, but will leave old work there. If we agree on an appropriately named taint, we can have nginx tolerate it by default. Am I missing any reason why this would not work? If that flies, we should fix docs ( those are GCP docs). I am happy to help with that. Longer term maybe we can do something smarter. I am not sure what that would be, just now. Ideas?\nIs there any reason we can't just leave the nodes in the load balancer pool when the node is cordoned? And when the pods are terminated the nodes can be removed? I may be missing some context here?\nThe presumption is that a node that is unschedulable is going away, or needs some other repair. Using it as a target for load-balancers means there could be sessions routed THROUGH that node. Even as the pods are drained. Right up until the node suddenly dies, causing an outage of a different flavor. What should really happen is that a node which becomes unschedulable starts draining connections. Once all the pods are moved off, the node can be removed from the pool entirely. I don't think any cloud providers, even GCP, handle this just right today. David Radcliffe <:\nWait, if you brought up a new nodepool, all those new nodes should be in the TargetPool. Cordoning the old nodepool should only terminate the existing connections, new connections should be fine. Something doesn't add up...\nWas this using\nYes\nRight, well, that explains it. So even draining won't do what you want - you need new connections to be allowed until you have capacity in the new pool. The good news is that you can do this entirely yourself, with taints. We just need nginx to tolerate the taint, which you can also specify yourself. The only real alternative I see would be, as you said, to leave nodes in the LB pool until the node dies. Given that we never specified this, it is probably different on every provider, which would make it hard to change (especially if the provider already provides clean drains while unschedulable).", "commid": "kubernetes_issue_65013", "tokennum": 481}], "negative_passages": []}
{"query_id": "q-en-kubernetes-64f77bddadf74fb2432fbaf2bc1c467e47d7cf828e5ca436425ac45968697464", "query": "func (s *Controller) getNodeConditionPredicate() NodeConditionPredicate { return func(node *v1.Node) bool { <del> // We add the master to the node list, but its unschedulable.  So we use this to filter // the master. if node.Spec.Unschedulable { return false } </del> if s.legacyNodeRoleFeatureEnabled { // As of 1.6, we will taint the master, but not necessarily mark it unschedulable. // Recognize nodes labeled as master, and filter them also, as we were doing previously.", "positive_passages": [{"docid": "doc-en-kubernetes-971dd5a381fee05df7a732c55096ac94f03e1a58bc9cf8aa911af5dca195b6a4", "text": "IIUC, we don't want new pods to land on the tainted/cordoned nodes. In that case, we can place \"NoSchedule\" taint on the nodes. We don't need any tolerations on nginx. This will prevent new instances of nginx from landing on the tainted nodes, but the existing ones will keep running there.\nIssues 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\n/remove-lifecycle stale\nThis just surprised us also. I understand the technical reasons behind it but the command name and associated documentation is misleading. To me it isn't intuitive that the command does not remove compute (pods) but does remove some networking. I would expect cordon to keep new pods from getting scheduled to it and keep it from getting to new services/ELBs/etc. The command would then cause pods to be removed and also take the node out of networking paths. Almost need a new state for a node of that is clearly defined.\nMy main issue is with the docs, and also GKE docs. They should explain this pitfall. After I got aware of the issue I understand why it works as it does. A simple workaround is to taint the nodes you are going to rotate first.\nJust chiming in; We as a GKE customer have today been bitten by this issue in production. The documentation of (in the context of GKE) is not extensive enough so we could be aware of this issue. This should be addressed. Luckily the outage was not severe because we were using the node-by-node approach (and accepted the container churn this would cause). We explicitly took this approach because our previous nodepool upgrade was a total outage also caused by in a different way. (for those interested in our total outage, not related to this issue): Due to the fact that also results in the re-calculating the amount of schedulable nodes and thus scaled the amount of pods in our cluster (in our case: from 110 back to 2) resulting for us in major DNS outage internally.", "commid": "kubernetes_issue_65013", "tokennum": 491}], "negative_passages": []}
{"query_id": "q-en-kubernetes-64f77bddadf74fb2432fbaf2bc1c467e47d7cf828e5ca436425ac45968697464", "query": "func (s *Controller) getNodeConditionPredicate() NodeConditionPredicate { return func(node *v1.Node) bool { <del> // We add the master to the node list, but its unschedulable.  So we use this to filter // the master. if node.Spec.Unschedulable { return false } </del> if s.legacyNodeRoleFeatureEnabled { // As of 1.6, we will taint the master, but not necessarily mark it unschedulable. // Recognize nodes labeled as master, and filter them also, as we were doing previously.", "positive_passages": [{"docid": "doc-en-kubernetes-e282766302629c93406295497fcf5631aa302acfa1c106d008828355db43428f", "text": "Be warned that for a nodepool upgrade can have a lot of unwanted & unexpected side effects.\nIt looks like this happens only to AWS and GCP but not on Azure? Can anyone confirm this? I just tested in both AWS and Azure, and while I see logs like in AWS Kubernetes, I do not see any logs like that in Azure. Is it intended? If so isn't behavior different for each cloud provider? i.e.) cordoning a node in AWS Kubernetes prevents loadbalancer from routing traffic to the affected node but cordoning a node in Azure Kubernetes will still let the loadbalancer route traffic to the affected node. Is it intentional?\nBesides running a test like the above, how would I determine what the behavior is on AWS? I haven't found anything in the node administration docs or the Service that would imply that would shift traffic away from a Pod. In fact, the doc for explicitly states, emphasis mine: If I hadn't come across this Issue due to reports from GKE, I suppose it would only have been a matter of time until we had a high-impact production outage. There's a disconnect between Kubernetes API and the LoadBalancer as to whether Pods running on a 'd node are Ready. From all the docs I've seen, I would expect that either a) would evict Pods over to a Node before setting the instance as , or b) LoadBalancer would not equate with\nHi All, What approaches people using too workaround this? From reading the comments I was hoping to follow the custom taint approach. However, I've noticed executes a cordon making it difficult to drain the node safely with this approach.\nI was lucky in that I experienced this issue while cordoning our testing environment, so we didn't experience a production outage. I think what I'm going to try is the following... it's going to be time-consuming but I think it's the safest bet. Double the number of nodes in the server group to bring online the new nodes first Place a custom taint on each \"legacy\" node As you said, executes a first, so that's a no-go. This is the time-consuming part... for each \"legacy\" node I am going to each pod, and let my PDBs take care of maintaining minimum number of pods. I'm hopeful to try this approach this afternoon, I'll comment back here if I do!", "commid": "kubernetes_issue_65013", "tokennum": 535}], "negative_passages": []}
{"query_id": "q-en-kubernetes-64f77bddadf74fb2432fbaf2bc1c467e47d7cf828e5ca436425ac45968697464", "query": "func (s *Controller) getNodeConditionPredicate() NodeConditionPredicate { return func(node *v1.Node) bool { <del> // We add the master to the node list, but its unschedulable.  So we use this to filter // the master. if node.Spec.Unschedulable { return false } </del> if s.legacyNodeRoleFeatureEnabled { // As of 1.6, we will taint the master, but not necessarily mark it unschedulable. // Recognize nodes labeled as master, and filter them also, as we were doing previously.", "positive_passages": [{"docid": "doc-en-kubernetes-e2e1ecb80d8f290360c9ff319629a62c8ce0008d9f4455b71f27e28e2654d975", "text": "Same as myself! Pity neither of us have a story for Since my comment this morning I've been trying a few approaches, I've ended up with the following: Create a new node pool of equal size in GKE with the upgraded kube version Set the current node pool to not be able to grow beyond its current size - if your using regional nodes this can be annoying, let it bring up new nodes anyways and just have them taint as NoSchedule straight away Taint all old node pool nodes with NoSchedule Go through each old node pool node executing a taint of NoExecute which will cause the node to drain and go onto available nodes i.e. your newly provisioned node pool Ensure your nginx ingress is deployed with tolerances:\nHi All, I'm at a bit of a loss on this one. I've started using custom taints to drain the nodes without getting them removed from the load balancer. My application can hold a HTTP connection open for up to 600 seconds. I'm using nginx as a daemonset, have it configured with a keepalive timeout of 620s, and have . I drain the application first using a taint on each node. I have nginx on each node tolerate this taint and remove it separately at a later point using a different taint. I'm waiting 660s between drains of each node for each taint to ensure nothing is dropped - this all works fine as expected. However, once I kill the node pool or do a kubectl drain after the node is empty of all my stuff plus nginx ingress I start seeing connection issues. I'm a bit lost where to go at debugging them, best guess is something to do with kube-proxy. Can anyone shed some light on this? is there anything on the Google Layer 4 load balancer I'm missing here? Is there some way to correctly drain kube-proxy (or does that even make sense?)\nThis doesn't address the network issues you're seeing, but for those trying to \"roll their own cordon\" using taints: Using a NoExecute taint to \"drain\" the node won't be orderly and won't respect any PDBs. You want to replicate the logic from which tries to do evictions of every pod in a loop. (I realize this is a burdensome idea, but it is also the safest idea.)", "commid": "kubernetes_issue_65013", "tokennum": 515}], "negative_passages": []}
{"query_id": "q-en-kubernetes-64f77bddadf74fb2432fbaf2bc1c467e47d7cf828e5ca436425ac45968697464", "query": "func (s *Controller) getNodeConditionPredicate() NodeConditionPredicate { return func(node *v1.Node) bool { <del> // We add the master to the node list, but its unschedulable.  So we use this to filter // the master. if node.Spec.Unschedulable { return false } </del> if s.legacyNodeRoleFeatureEnabled { // As of 1.6, we will taint the master, but not necessarily mark it unschedulable. // Recognize nodes labeled as master, and filter them also, as we were doing previously.", "positive_passages": [{"docid": "doc-en-kubernetes-11147f85e8d1488f3d03a6c51d3d3b27940ae8960669e7fe9226d15b33379ba5", "text": "To add on to ,: One approach that does not use node taints to force migrate, is to change for the requirements of your app. A change in node selector (e.g. based on instance type), along with a PDB (e.g. 66% / out of 3 replicas availability) should migrate you over fine. This worked out better for me than to drain or add taints to nodes to force push apps out. After the migration completes, you should be able to the nodes, and delete the node pool. FWIW, I too saw connection issues during load testing of a migration, and at least on my setup it was due to using an AWS NLB for the NGINX Ingress Controller. Switching to a classic ELB instead worked, as the NGINX LB Service seems to hit some sort of by my accounts when using NLBs. self-plug: I happened to recently cover a similar topic in a that you may find relevant. Hope it helps\nFor better or worse, for in my case pods that are behind an ingress resource are using node affinity to preferably not schedule them onto the same node. Originally this was done to ensure traffic is balanced across the different nginx ingresses. It has had a positive affect in this case too. Very interesting! Thank you for sharing, I'm not sure that swapping out the Layer4 GCE load balancer is an option here, but you have me thinking. I'm wondering if the TCP keepalive between the LB and nginx is potentially keeping connections open. , and suggest that there may be a 600 second TCP keepalive going on. Will retest doing a sleep of 620s after nginx removal and before node drain.\nHas anyone come up with a strategy to safely move workloads between two pools? Reading this bug, it seems there's no way to reliably do this without causing an outage if you follow the recommendation of + . In my case I'm not using an nginx ingress but services with type . From what I can see, adding to a node causes the Service Controller to consider the node not ready and thus removes it from a target group. This would mean that between and there is no way to add a taint to the node that will leave it in the LB until it's drained.", "commid": "kubernetes_issue_65013", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-64f77bddadf74fb2432fbaf2bc1c467e47d7cf828e5ca436425ac45968697464", "query": "func (s *Controller) getNodeConditionPredicate() NodeConditionPredicate { return func(node *v1.Node) bool { <del> // We add the master to the node list, but its unschedulable.  So we use this to filter // the master. if node.Spec.Unschedulable { return false } </del> if s.legacyNodeRoleFeatureEnabled { // As of 1.6, we will taint the master, but not necessarily mark it unschedulable. // Recognize nodes labeled as master, and filter them also, as we were doing previously.", "positive_passages": [{"docid": "doc-en-kubernetes-badabe4a617de62187355502ba8431d2071284df2978e7fc5a1318bb9d8c5a02", "text": "Using doesn't work in this case since the thing I'm draining might just come back and I'm not sure if the service controller will still consider the node ready in that case, but I believe it does. The one strategy I can think of is using labels on the node and an anti-affinity on the pod. You'd then add the label to a node that would push the pod away and then delete the pod. As long as the anti affinity uses this should be safe to do in preparation of a migration. Once the pods have been deleted you could then the nodes.\nIssues 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\n/lifecycle frozen /remove-lifecycle stale /remove-lifecycle rotten\n- As I mentioned in I set up a script that first taints all nodes in the old node pool and then cordon+taint one by one node. If your ingress services are redundant this should work well.\nIs there a plan for cordon behavior to improve on GCP? We have relied on this behavior for years on our AWS clusters and it was very surprising to find out.\nThis is a bug with service load balancers - not something we should document. We defined a label in that cluster admins can use - Unschedulable has nothing to do with SLB inclusion. which is beta and on by default in 1.19.\nDisagree. Unschedulable means \"no new workloads\". It has nothing to do with existing workloads, that is why we have drain (but we should have something in kube that communicates nodes are draining). I have opened to remove this check - we have an alternate approach now and the old logic is wrong (the comment in the code even says \"this is for masters!\" and that's wrong now too as part of the kep).\nA node status condition?\nPossibly, or a taint, or a label. Something concrete.\n/milestone v1.19", "commid": "kubernetes_issue_65013", "tokennum": 469}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6506af4b1254de9fc00ab6193ebe5ac0a049cc000f2f3e2e16c6b78409b17089", "query": "\"fmt\" \"net\" \"reflect\" <ins> \"sort\" </ins> \"strings\" \"testing\"", "positive_passages": [{"docid": "doc-en-kubernetes-dd58629e743b6e4eeaad6ce708921acac15734ca4e62ad8f92d2c296b406f940", "text": "What happened: SCTP nodeport service is not working for all IPs present in the node when ipvs is enabled. It is working only for node's InternalIP. What you expected to happen: SCTP nodeport service must work for all ips present in the node when ipvs is enabled. How to reproduce it (as minimally and precisely as possible): Create a kubernetes cluster with at least one node having multiple interfaces with different IPs. Start an SCTP server deployment. Then create a nodeport service for the same. Now try to reach the service using all the IPs present in that node. The service will be accessible only via node's InternalIP not any other IPs. Environment: Kubernetes version: v1.15.2 OS: ubuntu 18.04 Kernel: 4.15.0-54-generic Network plugin and version (if this is a network-related bug): ipset version v6.34\n/sig network /area kube-proxy /area ipvs\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/remove-triage unresolved", "commid": "kubernetes_issue_81474", "tokennum": 251}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6524534ae69e699a02e13769f85b0ee20d1717ab54db2b9092c209bd529349c8", "query": "return err } var ok bool <ins> // Handle filename input from stdin. The resource builder always returns an api.List // when creating resource(s) from a stream. if list, ok := obj.(*api.List); ok { if len(list.Items) > 1 { return cmdutil.UsageError(cmd, \"%s specifies multiple items\", filename) } obj = list.Items[0] } </ins> newRc, ok = obj.(*api.ReplicationController) if !ok { if _, kind, err := typer.ObjectVersionAndKind(obj); err == nil {", "positive_passages": [{"docid": "doc-en-kubernetes-54abd4c5b24af7b3b07bb9048a102e7524bce4cd2b3e4eeee922b6e64ea9d4ce", "text": "attemting to run throws and error with ERROR: Error: - does not specify a valid ReplicationController\nThe documentation is a little ambiguous, as the second example suggests that - should work but the Synopsis section does not. Could you either fix the documentation or the command?\nCalvin, can you post the contents of , and the schema of the original rc? There are some for the schema when providing a target from file, which may not be met.\nrunning works, I was interpreting the error message that it though - was a rc\nwill work for any object schema file. I.e, that is the same command you use to create a podreplicationcontroller from file. The type being created is determined by the contents of the file. Looking back at the code, the error you saw indicates that does not contain a replicationcontroller spec. If you can create it, that must mean it's something else; can you post/link the contents?\nyes I need to clean it up first\nThat looks like a valid rc spec, but the labels may be insufficient for rollingupdate. In order to do a rollingupdate you need to have a label to control the update. Typically this would be a \"version\" label. Example Basically the selector for the old and new rc must share at least one label key with a differing value. By the way, rollingupdate is currently getting a simplified version, which generates the new rc spec for you. This is wip that will be available in next week's GKE release. See\nah I see, I actually have a dynamic version in there so that will be easy to do thanks Jeff Lowdermilk wrote:\nso with an updated config still does not work while does work with the first one still erroring out with so likely my missing selector issue was an unrelated issue\nFrom your last comment, seems this is resolved. If you are still having trouble, lmk and I will reopen.\nstill not fixed because I can't do\nI'm pretty sure that's a piping issue with the wrapper command that likely doesn't occur if you use kubectl directly. Try Note that steps 1,2 will be unnecessary with the next gcloud release; you will be able to use kubectl directly after creating a cluster.\nWith cloudsdk 0.9.60, standalone kubectl works by default with GKE clusters.", "commid": "kubernetes_issue_7286", "tokennum": 504}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6524534ae69e699a02e13769f85b0ee20d1717ab54db2b9092c209bd529349c8", "query": "return err } var ok bool <ins> // Handle filename input from stdin. The resource builder always returns an api.List // when creating resource(s) from a stream. if list, ok := obj.(*api.List); ok { if len(list.Items) > 1 { return cmdutil.UsageError(cmd, \"%s specifies multiple items\", filename) } obj = list.Items[0] } </ins> newRc, ok = obj.(*api.ReplicationController) if !ok { if _, kind, err := typer.ObjectVersionAndKind(obj); err == nil {", "positive_passages": [{"docid": "doc-en-kubernetes-34e6555626ce71d3ee72ecabeeb61d74a5a04012a9d26021a4a4f8a40e19ef7f", "text": "The wrapper command is no longer needed and will be removed in a future release. Let me know if you have problems running against a GKE cluster.\nI am running across this issue with a recent build of .\nis still throwing errors with version 0.17 used directly (without wrapping)", "commid": "kubernetes_issue_7286", "tokennum": 58}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6548f62c957194401d7b2733ee9d292ef5b3edafa2b2bf6ecebb45ddefa1766a", "query": "roleRef: kind: Role name: external-provisioner-cfg <ins> apiGroup: rbac.authorization.k8s.io </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-3a5f8f6fae70577f1cbce129e8b4c7178012c138aa12442a5305f077f7f55297", "text": "xref: When running the GCE PD CSI Driver against all dynamic provisioning tests from this PR: We encounter the following test failures that need to be resolved: /kind bug /sig storage /cc\nSo it seems that the flag is getting passed all the way through to the driver and it is behaving as we would expect it to in terms of mounting. All the correct commands are being run: When exec-ing into the gce-pd-driver container we can observe that the mounted point is indeed read only. However, when viewed from the host node's perspective the mount is still read write. And therefore since the subpath folder is created by the host, the folder is still being created successfully which fails the test. This behavior suggests that is either not properly propagating the read only option on remount, or not properly remounting at all. I can't figure out how to \"view mount events\" if that's even possible, some help would be appreciated if anyone is aware of how to do that. That would help me narrrow down which of those two options is happening. I have also attempted (from inside the gce pd driver container) to unmount the point (successful) and bind mount it back with the readonly option directly (not using remount trick, still unsuccessful). Suggesting that maybe it is the that is not being mount propagated and not a problem with in particular. /cc\n/assign\n/milestone v1.13 /priority important-soon", "commid": "kubernetes_issue_70549", "tokennum": 314}], "negative_passages": []}
{"query_id": "q-en-kubernetes-654eefb3353139b76cce2a424b8cbbbc35a528429cc6ad9f86757bdc75c460a7", "query": "webhook_authn_config_volume=\"{\"name\": \"webhookauthnconfigmount\",\"hostPath\": {\"path\": \"/etc/gcp_authn.config\"}},\" fi <del> params+=\" --authorization-mode=ABAC\" </del> <ins> params+=\" --authorization-mode=RBAC\" </ins> local webhook_config_mount=\"\" local webhook_config_volume=\"\" if [[ -n \"${GCP_AUTHZ_URL:-}\" ]]; then", "positive_passages": [{"docid": "doc-en-kubernetes-19a61d82ec14336213ef377c4e39e11807c2ce9673880ce3d82a192d5a783624", "text": "Typically, the dns and dashboard is in crash loop. Ref cc\nif you check the file, does it contain lines like ?\nPrevious comment is ref: from I'll copy that to container-linux as well.", "commid": "kubernetes_issue_39395", "tokennum": 44}], "negative_passages": []}
{"query_id": "q-en-kubernetes-65816a4704722100b5944d5fe1a7a13e88dd51d9f1b27c2347341fcbc13ed7fd", "query": "} func TestList(t *testing.T) { <ins> scheme := NewTestScheme() metav1.AddMetaToScheme(scheme) </ins> client := NewSimpleMetadataClient(scheme, newPartialObjectMetadata(\"group/version\", \"TheKind\", \"ns-foo\", \"name-foo\"), newPartialObjectMetadata(\"group2/version\", \"TheKind\", \"ns-foo\", \"name2-foo\"),", "positive_passages": [{"docid": "doc-en-kubernetes-d7e6fda1614d5720cc8c8b15824f08c5e880f7950d0c5cc5cd811c2fcceb82ab", "text": "Because of this scheme mutation, this leads to concurrent use of the same scheme to cause the program to panic. It would be ideal to do this in some concurrent safe manner or add a warning or similar\n/sig api-machinery\n/assign\n/assign /triage accepted", "commid": "kubernetes_issue_107823", "tokennum": 54}], "negative_passages": []}
{"query_id": "q-en-kubernetes-65c90f19a9c121ce52fe69c92729db30a8ca0ab0dd973cfa47c34572e52f1411", "query": "if err != nil { t.Errorf(\"test case %s failed: %v\", tc.name, err) } <ins> watchError := tc.watcherError csiAttacher.waitSleepTime = 100 * time.Millisecond </ins> go func() { <ins> if watchError { errStatus := apierrs.NewInternalError(fmt.Errorf(\"we got an error\")).Status() fakeWatcher.Error(&errStatus) return } </ins> fakeWatcher.Delete(attachment) }() err = csiAttacher.Detach(volumeName, types.NodeName(nodeName))", "positive_passages": [{"docid": "doc-en-kubernetes-bf4acf56a8324d5d9229417a25d2febc989c56201f9f4bdce8fffe7a46728546", "text": "A CSI plugin that the 1.10 controller manager can't detect (which could occur in a number of scenarios, such as when a rollout is being performed or a node is evacuated) seems to retry without backoff. In this case, I have a pod referencing a PVC -PV that references my CSI plugin, but no controller plugin running. The controller is probing every 100ms continuously for a single volume attachment. The controller should backoff. Have not tested with higher numbers of pods, but in a busy system this could cause the controller manager to burn CPU. Also, there isn't actually a great error telling the user why the probing is happening (I knew in this case, but an admin likely has no idea).\n/assign\nIssues 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\n/remove-lifecycle stale /milestone v1.14 adding it to next milestone as per if it doesn't make it then it can be further moved\nas KEP has been moved, unless an exception is made, /milestone v1.15\nthe linked kep above is unrelated to this issue. This is a bug and I don't think it needs an associated enhancement\nsorry, got diverted by the comments on that KEP. /milestone v1.14\nHello from Bug Triage Shadow . I'd like to remind that code freeze is coming in 3 days (Friday, 8th March). Is this still planned to be fixed for 1.14?\nWe have not been tracking this for 1.14. /assign can you help triage and see if this is still an issue and if there is a quick fix?\nI can't reproduce the issue, do you remember what you did? From the logs it seems that Watch channel consistently returns so new is called recursively (beware, 1.10 code, but it's very similar in master): Can it produce fairly stable 100ms delay between calls? Anyway, this is not usual code path, watcher does not return in most cases.", "commid": "kubernetes_issue_64952", "tokennum": 478}], "negative_passages": []}
{"query_id": "q-en-kubernetes-65c90f19a9c121ce52fe69c92729db30a8ca0ab0dd973cfa47c34572e52f1411", "query": "if err != nil { t.Errorf(\"test case %s failed: %v\", tc.name, err) } <ins> watchError := tc.watcherError csiAttacher.waitSleepTime = 100 * time.Millisecond </ins> go func() { <ins> if watchError { errStatus := apierrs.NewInternalError(fmt.Errorf(\"we got an error\")).Status() fakeWatcher.Error(&errStatus) return } </ins> fakeWatcher.Delete(attachment) }() err = csiAttacher.Detach(volumeName, types.NodeName(nodeName))", "positive_passages": [{"docid": "doc-en-kubernetes-386907f979b2ab6cc28dd5590343cbf2830e874540a448be35232bf4673dff7e", "text": "if I read the code correctly, such recursive must end up with timeout - caller does not care about return value and caller's watch probably won't return anything useful. Is there a reason why we don't return error? This will kick in exponential backoff in A/D controller.\nclearing the milestone for tracking purposes to let the fix land in its own time /milestone clear\nIssues 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\nI found the error would happen when a pv is attahing(volumeattachment has created) and the csi-attacher is deleted at the same time. Then the log would print so frequently (because of recursion).\nis this fixed by ?\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nClosing 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", "commid": "kubernetes_issue_64952", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-65e7dd76a2314eee20d95c7492c7d6529e4ec0aca6cf928e5a0681803833ab63", "query": "var watcher *fsnotify.Watcher var parse parseFunc var stop bool <ins> isNewLine := true </ins> found := true writer := newLogWriter(stdout, stderr, opts) msg := &logMessage{}", "positive_passages": [{"docid": "doc-en-kubernetes-1611cacb700fc7bde4bed341ff7dc392aeb6c35e6c0f63ce6a10b84981e8d04a", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Docker has a hardcoded 16K limit on log line length, which splits lines longer than that into multiple messages in the log file. in , however, doesn't account for this when is set to and prints the timestamp in front of every entry in the log file instead of every logical line. This leads to random timestamps appearing in the middle of log lines, potentially breaking the applications that parse these logs. What you expected to happen: inserts timestamps once per logical line, so original log data is preserved. Alternatively, allow API to request the logs in a sane format like JSON, which would allow merging the lines back and combining them with the timestamps more intelligently on the application side. How to reproduce it (as minimally and precisely as possible): Create : apiVersion: v1 kind: Pod metadata: name: log-lines spec: containers: name: main image: busybox command: ['sh', '-c', 'while sleep 1; do echo -n ; for i in $(seq 1 ); do echo -n A; done; echo ; done'] Start the pod with Fetch the logs with , or using the API () Observe random timestamps inserted in the middle of the log lines. Environment: Kubernetes version (use ):\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI will work on it. /sig cli /remove-sig node\nThe logs are being corrupted by the API endpoint in kubelet, so shouldn't it be in scope of SIG node?\nThe log is not corrupted by k8s. The same log could be got using \"docker container logs -t CONTAINERID\" I think you should post your requirement to Docker.", "commid": "kubernetes_issue_77603", "tokennum": 465}], "negative_passages": []}
{"query_id": "q-en-kubernetes-65e7dd76a2314eee20d95c7492c7d6529e4ec0aca6cf928e5a0681803833ab63", "query": "var watcher *fsnotify.Watcher var parse parseFunc var stop bool <ins> isNewLine := true </ins> found := true writer := newLogWriter(stdout, stderr, opts) msg := &logMessage{}", "positive_passages": [{"docid": "doc-en-kubernetes-495f248c0af4a1a8db07569505db46eac9f11be4907de183bc6923cd7882b142", "text": "Please refer following code Line 50 ~ 52 if config.Timestamps { logLine = append([]byte(msg.Timestamp.Format(jsonmessage.RFC3339NanoFixed)+\" \"), logLine...) }\nkubelet doesn't rely on Docker when reading logs, it reads the files itself (see the code linked in the issue). I don't think Docker would change the forced line splitting (see for example), so this should be fixed in Kubernetes.\nYour are right and kubelet read log file from host such as /var/log/pods/pods/NAMESPACEPOD-NAMExxx/....(JSON format) I will post a PR for it. /remove-sig cli /sig node\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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 .", "commid": "kubernetes_issue_77603", "tokennum": 539}], "negative_passages": []}
{"query_id": "q-en-kubernetes-65e7dd76a2314eee20d95c7492c7d6529e4ec0aca6cf928e5a0681803833ab63", "query": "var watcher *fsnotify.Watcher var parse parseFunc var stop bool <ins> isNewLine := true </ins> found := true writer := newLogWriter(stdout, stderr, opts) msg := &logMessage{}", "positive_passages": [{"docid": "doc-en-kubernetes-2f614c9ad06da31fe9313a5b2eaea6d6901d55cba8508cf5ebe57105d301c4f6", "text": "Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\nStale 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\nI saw the attempt fixing this but it was scary (echo this comment: ). I suggested a way it may be improved. Also the proposed fix didn't introduce any e2e tests to validate that runtime behavior is not changed and runtimes keep the no-newline-on-splitted-log logic. are you or anybody on this thread are still interested to work on this? Please re-open if so. Meanwhile closing this ahead of bot doing it because the inactivity. /close\nClosing this issue. <detailsIn response to : I saw the attempt fixing this but it was scary (echo this comment: ). I suggested a way it may be improved. Also the proposed fix didn't introduce any e2e tests to validate that runtime behavior is not changed and runtimes keep the no-newline-on-splitted-log logic. Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_77603", "tokennum": 493}], "negative_passages": []}
{"query_id": "q-en-kubernetes-65e7dd76a2314eee20d95c7492c7d6529e4ec0aca6cf928e5a0681803833ab63", "query": "var watcher *fsnotify.Watcher var parse parseFunc var stop bool <ins> isNewLine := true </ins> found := true writer := newLogWriter(stdout, stderr, opts) msg := &logMessage{}", "positive_passages": [{"docid": "doc-en-kubernetes-2e8714433462894a36e35ec9c24fb7c5a56d0558d2953a09bb86920b184c167e", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nYou can't reopen an issue/PR unless you authored it or you are a collaborator. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/remove-lifecycle rotten /reopen will fix it.\nReopened this issue. <detailsIn response to : /remove-lifecycle rotten /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/triage accepted\nThe Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.", "commid": "kubernetes_issue_77603", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-65e7dd76a2314eee20d95c7492c7d6529e4ec0aca6cf928e5a0681803833ab63", "query": "var watcher *fsnotify.Watcher var parse parseFunc var stop bool <ins> isNewLine := true </ins> found := true writer := newLogWriter(stdout, stderr, opts) msg := &logMessage{}", "positive_passages": [{"docid": "doc-en-kubernetes-422d52914e9725e7355cb5e937e13c24e15f273f63951d92fe52d86a167487cb", "text": "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]:\nThe 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]:\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_77603", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-65e7dd76a2314eee20d95c7492c7d6529e4ec0aca6cf928e5a0681803833ab63", "query": "var watcher *fsnotify.Watcher var parse parseFunc var stop bool <ins> isNewLine := true </ins> found := true writer := newLogWriter(stdout, stderr, opts) msg := &logMessage{}", "positive_passages": [{"docid": "doc-en-kubernetes-0e28d298340708e57a780633dba41fa2a744d19c9ab3d061a118f6b1e6c3d902", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI received a bug report about this issue. The root cause is that the buffer reads up to a new line. If the line is greater than 4096 bytes and '--timestamps' is turrned on the kubelet will write the timestamp and the partial log line. We will need to refactor the ReadLogs function to allow for a partial line read.", "commid": "kubernetes_issue_77603", "tokennum": 104}], "negative_passages": []}
{"query_id": "q-en-kubernetes-660938dbcb689c10815d857f44eecac7a3d9fae6269cf6811e70ee267c5c7a60", "query": "restoredState, err := NewCheckpointState(testingDir, testingCheckpoint, tc.policyName, tc.initialContainers) if err != nil { if strings.TrimSpace(tc.expectedError) != \"\" { <del> tc.expectedError = \"could not restore state from checkpoint: \" + tc.expectedError if strings.HasPrefix(err.Error(), tc.expectedError) { </del> <ins> if strings.Contains(err.Error(), \"could not restore state from checkpoint\") && strings.Contains(err.Error(), tc.expectedError) { </ins> t.Logf(\"got expected error: %v\", err) return }", "positive_passages": [{"docid": "doc-en-kubernetes-984aaf2876c4d4651f6765b291626bccfb7d6364087d7ebb11c97e2832c59ee5", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Below k8s UT fail when run with master-golang. TestCheckpointStateRestore/RestorecheckpointwithinvalidJSON error:=== RUN TestCheckpointStateRestore/RestorecheckpointwithinvalidJSON I1124 05:38:14. ] [cpumanager] initializing new in-memory state store unexpected error while creatng checkpointState: could not restore state from checkpoint: json: unexpected end of JSON input, please drain this node and delete the CPU manager checkpoint file \"/tmp/cpumanagerstatetest479660663/cpumanagercheckpointtest\" before restarting Kubelet --- FAIL: TestCheckpointStateRestore/RestorecheckpointwithinvalidJSON (0.00s) TestStrategicMergePatchInvalid error:=== RUN TestStrategicMergePatchInvalid expected \"invalid character 'b' looking for beginning of value\", got \"json: invalid character 'b' looking for beginning of value\" --- FAIL: TestStrategicMergePatchInvalid (0.00s) TestJSONPatch error:=== RUN TestJSONPatch invalid-syntax: expected error invalid character 'i' looking for beginning of value, but got json: invalid character 'i' looking for beginning of value --- FAIL: TestJSONPatch (0.00s) TestV4ErrorDecoder expandless error:=== RUN TestV4ErrorDecoder wrong error for message \"{\": want=\"error stream protocol error: unexpected end of JSON input in \"{\"\", got=\"error stream protocol error: json: unexpected end of JSON input in \"{\"\" --- FAIL: TestV4ErrorDecoder (0.00s What you expected to happen: The tests should pass with no error. How to reproduce it (as minimally and precisely as possible): a stable version of golang installed master go from upstream git clone cd go/src cd ../.. cp -r ./go /usr/local export PATH=/usr/local/go/bin:$PATH kubernetes repo and run the unit tests. () Anything else we need to know?: These failures are occurring due to mismatch of error messages between upstream go and the k8s tests.", "commid": "kubernetes_issue_96853", "tokennum": 597}], "negative_passages": []}
{"query_id": "q-en-kubernetes-660938dbcb689c10815d857f44eecac7a3d9fae6269cf6811e70ee267c5c7a60", "query": "restoredState, err := NewCheckpointState(testingDir, testingCheckpoint, tc.policyName, tc.initialContainers) if err != nil { if strings.TrimSpace(tc.expectedError) != \"\" { <del> tc.expectedError = \"could not restore state from checkpoint: \" + tc.expectedError if strings.HasPrefix(err.Error(), tc.expectedError) { </del> <ins> if strings.Contains(err.Error(), \"could not restore state from checkpoint\") && strings.Contains(err.Error(), tc.expectedError) { </ins> t.Logf(\"got expected error: %v\", err) return }", "positive_passages": [{"docid": "doc-en-kubernetes-d960907779eeb813df14a2ea4a00c97f52784ded937dbf1c71e5b05391843c78", "text": "There is an addition \"json:\" prefix to SyntaxError messages after this below commit: Environment: Kubernetes version (use ): latest source code from upstream Cloud provider or hardware configuration: OS (e.g: ): \"CentOS Linux 8 (Core)\" Kernel (e.g. ): Linux rajalakshmi-workspace 4.18.0-193.19.1.el82.ppc64le SMP Mon Sep 14 14:48:04 UTC 2020 ppc64le ppc64le ppc64le GNU/Linux Install tools: [root go]# go version go version devel + Fri Nov 20 00:54:43 2020 +0000 linux/ppc64le [root go]# Network plugin and version (if this is a network-related bug): Others:\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig testing\nwill fix it in Go 1.16 as release-blocker.\nI would fix the test here to be more tolerant. exact string matches on error messages aren't really an API\u2026 I would not expect that to block the golang release\nAgree too, we can think about having a substring match to avoid these issues instead!\n/assign Lets see if we can fix this in the k8s tests", "commid": "kubernetes_issue_96853", "tokennum": 352}], "negative_passages": []}
{"query_id": "q-en-kubernetes-66113bdf876034e9e2c8d373dd59783ee05b89837729f55fdebb799a32b89b3a", "query": "} func getPriorityFunctionConfigs(names sets.String, args PluginFactoryArgs) ([]priorities.PriorityConfig, error) { <del> schedulerFactoryMutex.Lock() defer schedulerFactoryMutex.Unlock() </del> <ins> schedulerFactoryMutex.RLock() defer schedulerFactoryMutex.RUnlock() </ins> var configs []priorities.PriorityConfig for _, name := range names.List() {", "positive_passages": [{"docid": "doc-en-kubernetes-a3c7d28dcea4cbdaac9e2be0d7d2d60e791f1250fe870aa2d2d4769d84db6cae", "text": "What would you like to be : Currently Mutex lock is acquired in for accessing different maps. Some functions only read map entry: We can utilize RWMutex where the above function acquires read lock. Why is this needed: For concurrent calls to IsFitPredicateRegistered / IsPriorityFunctionRegistered, read lock would lower contention.\n/sig scheduling\nfunctions getFitPredicateFunctions, getPriorityFunctionConfigs, ListRegisteredFitPredicates, ListRegisteredPriorityFunctions and GetAlgorithmProvider can also use read lock.\nI happened to raise earlier today. Anyone can finish resting ones.\nGood to know,\nThanks for raising this ! My PR covered and . Feel free to raise another PR to cover others.\nOnce is merged, I will send my PR thanks\nit's merged now.", "commid": "kubernetes_issue_76248", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-664567d123f106680dee9042be58f63ef6fe1114423ea38ebce281f931320c10", "query": "cluster/saltbase/salt/kube-apiserver/kube-apiserver.manifest:{% set params = address + \" \" + storage_backend + \" \" + etcd_servers + \" \" + etcd_servers_overrides + \" \" + cloud_provider + \" \" + cloud_config + \" \" + runtime_config + \" \" + feature_gates + \" \" + admission_control + \" \" + target_ram_mb + \" \" + service_cluster_ip_range + \" \" + client_ca_file + basic_auth_file + \" \" + min_request_timeout + \" \" + enable_garbage_collector -%} cluster/saltbase/salt/kube-controller-manager/kube-controller-manager.manifest:{% set params = \"--master=127.0.0.1:8080\" + \" \" + cluster_name + \" \" + cluster_cidr + \" \" + allocate_node_cidrs + \" \" + service_cluster_ip_range + \" \" + terminated_pod_gc + \" \" + enable_garbage_collector + \" \" + cloud_provider  + \" \" + cloud_config + \" \" + service_account_key + \" \" + log_level + \" \" + root_ca_file -%} cluster/saltbase/salt/kube-controller-manager/kube-controller-manager.manifest:{% set params = params + \" \" + feature_gates -%} <ins> cluster/saltbase/salt/kube-controller-manager/kube-controller-manager.manifest:{% if pillar.get('enable_hostpath_provisioner', '').lower() == 'true' -%} </ins> cluster/saltbase/salt/kube-proxy/kube-proxy.manifest:  {% set api_servers_with_port = api_servers + \":6443\" -%} cluster/saltbase/salt/kube-proxy/kube-proxy.manifest:  {% set api_servers_with_port = api_servers -%} cluster/saltbase/salt/kube-proxy/kube-proxy.manifest:  {% set cluster_cidr=\" --cluster-cidr=\" + pillar['cluster_cidr'] %}", "positive_passages": [{"docid": "doc-en-kubernetes-ef45ff070b2c05a069c3f77b9a64e0bfff59d1f717362ac04203c879e5a7b68c", "text": "feature request Enables easier testing for pv/pvc, and all derivatives like pet sets. The only alternative is to use manually created pv of local type. I have time to work on it myself and created this feature to collect feedback/ideas on what provider should be enabled by default.\nSince this was merged should we close this issue?", "commid": "kubernetes_issue_32119", "tokennum": 67}], "negative_passages": []}
{"query_id": "q-en-kubernetes-664ed1e106a6b5968aa10f34c4b75735891cc450ff94571393135121f1b50b5d", "query": "volumeSpec: volumeSpec, // volume.volumeSpecName is actually InnerVolumeSpecName. It will not be used // for volume cleanup. <del> // TODO: in case pod is added back before reconciler starts to unmount, we can update this field from desired state information </del> <ins> // in case pod is added back to desired state, outerVolumeSpecName will be updated from dsw information. // See issue #103143 and its fix for details. </ins> outerVolumeSpecName: volume.volumeSpecName, pod:                 pod, deviceMounter:       deviceMounter,", "positive_passages": [{"docid": "doc-en-kubernetes-95820dc44dfb57216fa4466fe0b08e35d101b3576d175fcc0793312a1c18dfad", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --We have even encountered such case that pod continuously reports \u201cUnable to attach or mount volumes for pod;...\u201d when kubelet restarted. The reasons are listed in details as below: , as result of apiserver instantaneous unstablility, dswp get pvc\u2018s pv spec failed, then the pvc volume does not be to dsw. , syncStates() lists all the volume directories locally, and recontructs the volume from local volume, if the volume isn't in dsw, it will put the recontructed volume to asw, but now the volume.OuterVolumeSpecName isn't correct. chance, at this time, In , the fail to pvc volume is to dsw again normally in reconcile() -mountAttachVolumes(), it compares dsw and asw by volume's innerVolumename, it's all the same. but it could not sense the OuterVolumeSpecName dismatch. so it will not re-mount again to update asw cache , it checks pod's volume attach or mount success by comparing volume.OuterVolumeSpecName and , but this pv'c OuterVolumeSpecName isn't correct in asw. so pod continuously reports \u201cUnable to attach or mount volumes for pod;...\u201d reconcile() could sense the reconstruct volume's dismatch to the dsw, then re-mount again to make volume cache consistency Kubernetes version (use ): 1.19.4 Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig node\n/triage accepted\n/assign\nCC\nI think this is a point that can be optimized. /cc\nI will give a fix for this\nThanks for reporting the issue, this innerSpecName and outerSpecName are confusing and cause issues. Please ping me for review when you have a fix. Thanks!\nPlease don't triage your own issues immediately, give someone else a chance to review them :( /sig storage\nokay, I know", "commid": "kubernetes_issue_103143", "tokennum": 528}], "negative_passages": []}
{"query_id": "q-en-kubernetes-66796b3d3549c50dbde0e6d27acba79277a41bcd68a6d749274bb317fba80b3d", "query": "} func (s *podScope) Admit(pod *v1.Pod) lifecycle.PodAdmitResult { <del> // Exception - Policy : none if s.policy.Name() == PolicyNone { return s.admitPolicyNone(pod) } </del> bestHint, admit := s.calculateAffinity(pod) klog.InfoS(\"Best TopologyHint\", \"bestHint\", bestHint, \"pod\", klog.KObj(pod)) if !admit {", "positive_passages": [{"docid": "doc-en-kubernetes-4d10931e14d2065e9a15e6880eb555f03f2fd6b09352947daeddff0435b576bc", "text": "Follow up from: See details there. When is , there is no need to discover the NUMA topology. /sig node /priority backlog /kind feature /help-wanted\n/cc\n/triage accepted\nI would like to take this up also can I get more brief information about it? code review comments from asking that inside the NewManager() implementation, we need to skip NewPolicyOptions and NewNUMAInfo but when the NumaTopology comes kubelet issue also comes. I need some more information to start with this!\n/cc\nWhen there is no topology manger policy specified, NewManager should be a no-op. Just skip all checks.\nExactly. Just to add: we may need few iterations over the change to get a clean flow in the call.\n/assign", "commid": "kubernetes_issue_116391", "tokennum": 166}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6690d0fae4d4fa813ffadbff3fdefe00bd8e58361cf42fc9d278239b82e59e22", "query": "} func (e *PredicateFailureError) GetReason() string { <del> return e.PredicateName </del> <ins> return e.PredicateDesc </ins> } type FailureReason struct {", "positive_passages": [{"docid": "doc-en-kubernetes-10c13016eb5239afc7a330cfdab91dbf78232a49f2993f71669df735dbb939e1", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature The is not user friendly. There has been to make it better, but we still print in the pending message. We should change these errors to a more human readable message. For example, should be changed to something like . /sig scheduling", "commid": "kubernetes_issue_58546", "tokennum": 91}], "negative_passages": []}
{"query_id": "q-en-kubernetes-66db5386d5a73eed6d3c114455e92a28b1abdf210671e1af1af06a3470ef9d2d", "query": "fmt.Sprintf(\"%s::%s::%s\", f.Namespace.Name, pod1, \"busybox-container\"): boundedSample(10*e2evolume.Kb, 80*e2evolume.Mb), }), <del> \"pod_cpu_usage_seconds_total\": gstruct.MatchElements(containerID, gstruct.IgnoreExtras, gstruct.Elements{ </del> <ins> \"pod_cpu_usage_seconds_total\": gstruct.MatchElements(podID, gstruct.IgnoreExtras, gstruct.Elements{ </ins> fmt.Sprintf(\"%s::%s\", f.Namespace.Name, pod0): boundedSample(0, 100), fmt.Sprintf(\"%s::%s\", f.Namespace.Name, pod1): boundedSample(0, 100), }), <del> \"pod_memory_working_set_bytes\": gstruct.MatchAllElements(containerID, gstruct.Elements{ </del> <ins> \"pod_memory_working_set_bytes\": gstruct.MatchElements(podID, gstruct.IgnoreExtras, gstruct.Elements{ </ins> fmt.Sprintf(\"%s::%s\", f.Namespace.Name, pod0): boundedSample(10*e2evolume.Kb, 80*e2evolume.Mb), fmt.Sprintf(\"%s::%s\", f.Namespace.Name, pod1): boundedSample(10*e2evolume.Kb, 80*e2evolume.Mb), }),", "positive_passages": [{"docid": "doc-en-kubernetes-cef38c378015a3c37c6ee1632d82c03243825979d637fc81c55115a5c8a6f392", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: Which test(s) are failing: Since when has it been failing: Testgrid link: Reason for failure: Anything else we need to know: Introduced in /cc /sig node /assign /milestone v1.20\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_96568", "tokennum": 165}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6725aad88f41543ea8049e68051ebb74e6d2ef410ec3595b82ab4846a94e1c35", "query": "} } <del> var fakeTypeConverter = func() managedfields.TypeConverter { data, err := os.ReadFile(filepath.Join(strings.Repeat(\"..\"+string(filepath.Separator), 5), \"api\", \"openapi-spec\", \"swagger.json\")) </del> <ins> func configMapTypeConverter(scheme *runtime.Scheme) managedfields.TypeConverter { parser, err := typed.NewParser(configMapTypedSchema) </ins> if err != nil { <del> panic(err) </del> <ins> panic(fmt.Sprintf(\"Failed to parse schema: %v\", err)) </ins> } <del> swag := spec.Swagger{} if err := json.Unmarshal(data, &swag); err != nil { panic(err) } convertedDefs := map[string]*spec.Schema{} for k, v := range swag.Definitions { vCopy := v convertedDefs[k] = &vCopy } typeConverter, err := managedfields.NewTypeConverter(convertedDefs, false) if err != nil { panic(err) } return typeConverter }() </del> <ins> return TypeConverter{Scheme: scheme, TypeResolver: parser} } var configMapTypedSchema = typed.YAMLObject(`types: - name: io.k8s.api.core.v1.ConfigMap map: fields: - name: apiVersion type: scalar: string - name: data type: map: elementType: scalar: string - name: kind type: scalar: string - name: metadata type: namedType: io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta default: {} - name: io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta map: fields: - name: creationTimestamp type: namedType: io.k8s.apimachinery.pkg.apis.meta.v1.Time - name: managedFields type: list: elementType: namedType: io.k8s.apimachinery.pkg.apis.meta.v1.ManagedFieldsEntry elementRelationship: atomic - name: name type: scalar: string - name: namespace type: scalar: string - name: io.k8s.apimachinery.pkg.apis.meta.v1.ManagedFieldsEntry map: fields: - name: apiVersion type: scalar: string - name: fieldsType type: scalar: string - name: fieldsV1 type: namedType: io.k8s.apimachinery.pkg.apis.meta.v1.FieldsV1 - name: manager type: scalar: string - name: operation type: scalar: string - name: subresource type: scalar: string - name: time type: namedType: io.k8s.apimachinery.pkg.apis.meta.v1.Time - name: io.k8s.apimachinery.pkg.apis.meta.v1.FieldsV1 map: elementType: scalar: untyped list: elementType: namedType: __untyped_atomic_ elementRelationship: atomic map: elementType: namedType: __untyped_deduced_ elementRelationship: separable - name: io.k8s.apimachinery.pkg.apis.meta.v1.Time scalar: untyped - name: __untyped_deduced_ scalar: untyped list: elementType: namedType: __untyped_atomic_ elementRelationship: atomic map: elementType: namedType: __untyped_deduced_ elementRelationship: separable `) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-29db4d0749071d4e54a9083e12a93fb8b6b43cd54c28626ec2efc45861483a16", "text": "Smoke tests run by publishing-bot on client-go master are failing Ref for failure logs: Tests defined for client-go, after publishing, Since commit No response As part of , when module is used from within the staging directory, can be used by traversing to the parent directory. But once the module is made as a separate repository as part of publishing, then traversing to repository using path will not work. No response /sig-api-machinery\n/sig api-machinery\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /sig api-machinery 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\nLooking\nI'll remove the swagger file dependency, I don't think we strictly need it.\n/triage accepted", "commid": "kubernetes_issue_125704", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6728280f5063f3338a27804df24428e8258dc0ee4ab6d5624f37f1918c40f9d3", "query": "limiter.Forget(item) } } <ins> // WithMaxWaitRateLimiter have maxDelay which avoids waiting too long type WithMaxWaitRateLimiter struct { limiter  RateLimiter maxDelay time.Duration } func NewWithMaxWaitRateLimiter(limiter RateLimiter, maxDelay time.Duration) RateLimiter { return &WithMaxWaitRateLimiter{limiter: limiter, maxDelay: maxDelay} } func (w WithMaxWaitRateLimiter) When(item interface{}) time.Duration { delay := w.limiter.When(item) if delay > w.maxDelay { return w.maxDelay } return delay } func (w WithMaxWaitRateLimiter) Forget(item interface{}) { w.limiter.Forget(item) } func (w WithMaxWaitRateLimiter) NumRequeues(item interface{}) int { return w.limiter.NumRequeues(item) } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-6758a4fd9fc03e20cf227e8e04e978c36b819698b12d653642006e59891b2248", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --Currently when using it adds as one of the limiters. This does not work as intended because there is no immediate sleep following the call to the limiter as seen in which does work correctly. The issue with the in its current usage is there is no forget nor a sleep immediately following the call so if is called thousands of times in a row, the timeout grows very quickly with no max. For example, if a clusters has 10k secrets and those are all enqueued using the the will end up with a 16 min wait before the tail end of objects can be enqueued and processed. I would expect some max backoff to take affect. This can be seen at\n/sig api-machinery\n/cc /triage accepted\nit possible to set maxWaitingTime for BucketRateLimiter? when r.Limiter.Reserve().Delay() maxWaitingTime, the return of BucketRateLimiter When() is maxWaitingTime. defined is 1000ms / r.limit * MAXQPS(5000) this issue example (r.tokens = 100, r.limit = 10), if call When() times, the tail end of the object is enqueued waiting for 8.33 min. i'm not sure how to set the value of MAXQPS please help review it\nThe fix merged to close this issue does not fix the underlying issue with the DefaultControllerRateLimiter. The bucket is not being used correctly so this does not work as intended, please read my issue description again as to what is actually happening.\nis another fix needed to solve this issue?\nA token bucket rate limiter will only refill at the defined rate. If enough requeues are , it will take a long time for the refill rate to clear the queue. If a max wait is introduced, then requeues will be inserted into the queue faster than the refill rate of the token bucket rate limiter. A max wait will violate the token bucket rate limiter and we want token bucket rate limiting behavior.", "commid": "kubernetes_issue_104554", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-67a659abca4ac4dec1fcd5771d864ef70dbc89a93b63c78b15f2ab410d3a6be0", "query": "# # -M installs the master set +x <del> curl -L http://bootstrap.saltstack.com | sh -s -- -M -X </del> <ins> curl -L --connect-timeout 20 --retry 6 --retry-delay 10 http://bootstrap.saltstack.com | sh -s -- -M -X </ins> set -x echo $MASTER_HTPASSWD > /srv/salt/nginx/htpasswd", "positive_passages": [{"docid": "doc-en-kubernetes-9fcfa37c5fd88e21dae3cf641aefb45ac17c97dc04df9b3a60101bffeb7f8b4c", "text": "Failed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nthis appears to have always been broken, I'm going to disable the job for now. https://k8s-\nFailed: https://k8s- Run so broken it didn't make JUnit output!", "commid": "kubernetes_issue_34116", "tokennum": 556}], "negative_passages": []}
{"query_id": "q-en-kubernetes-67ac32aff4ae5e7eeacf3ada071acd6b41f2b580f2d861b759711f58587fefd8", "query": "kube::test::get_object_assert pods \"{{range.items}}{{$image_field}}:{{end}}\" 'changed-with-yaml:' ## Patch pod from JSON can change image # Command <del> kubectl patch \"${kube_flags[@]}\" -f test/fixtures/doc-yaml/admin/limitrange/valid-pod.yaml -p='{\"spec\":{\"containers\":[{\"name\": \"kubernetes-serve-hostname\", \"image\": \"gcr.io/google_containers/pause-amd64:3.0\"}]}}' # Post-condition: valid-pod POD has image gcr.io/google_containers/pause-amd64:3.0 kube::test::get_object_assert pods \"{{range.items}}{{$image_field}}:{{end}}\" 'gcr.io/google_containers/pause-amd64:3.0:' </del> <ins> kubectl patch \"${kube_flags[@]}\" -f test/fixtures/doc-yaml/admin/limitrange/valid-pod.yaml -p='{\"spec\":{\"containers\":[{\"name\": \"kubernetes-serve-hostname\", \"image\": \"gcr.io/google_containers/pause-amd64:3.1\"}]}}' # Post-condition: valid-pod POD has image gcr.io/google_containers/pause-amd64:3.1 kube::test::get_object_assert pods \"{{range.items}}{{$image_field}}:{{end}}\" 'gcr.io/google_containers/pause-amd64:3.1:' </ins> ## If resourceVersion is specified in the patch, it will be treated as a precondition, i.e., if the resourceVersion is different from that is stored in the server, the Patch should be rejected ERROR_FILE=\"${KUBE_TEMP}/conflict-error\"", "positive_passages": [{"docid": "doc-en-kubernetes-a834f77ddd825b3d04a660aa7c11d0734893e4dcde6e0d4a7399e3b3daf56428", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: the pause-amd64:3.0 image on has an empty schema2 manifest, which prevents is from being pulled by proxy/caches which only support V2 registries. What you expected to happen: Being able to pull ` using a V2 manifest compatible client. Anything else we need to know?: The proxy/cahce is requesting this\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nAfter talking with , he mentionned the following\nAFAIK, does not support well. After inspecting the image, you can find is still using manifest v1.\n/cc FYI\nIm not sure which exact version x sch\u00e9ma X is needed. What I know is that we can download through the proxy/cache all other Kubernetes kube-system images, only the pause image is giving us trouble. Therefore, I would say that having the image available using the same format as the other kube-system images would be the request here.\nYeah, we haven't updated the pause image in a while, since it doesn't really ever change. I'm not sure whether rebuilding + pushing over the existing tag is safe, or if we should bump to or something. thoughts?\nIf we do rebuilding/updating the image, that would help and a bunch of similar issues.\nit's better/save to go with new tag\nI didn't realize there were changes to the pause binary that were never actually deployed. It seems like we should probably just do that (and bump the tag).\nthat sounds great. Any idea when the existing 3.0 tag could be pushed again?\nWe shouldn't push over the 3.0 tag; we should push a 3.1 or 4.0 tag instead. I'm not sure who owns the pause container who should drive this. Maybe sig-node and/or\nIt seems like it should be sig-node. I'll look into it.\nThe new container has been built, can you test with\nIts working! thanks! I was able to pull it through our artifactory proxy , Lee Verberne <:\nexcellent, thanks for checking. /assign", "commid": "kubernetes_issue_56253", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-67ac32aff4ae5e7eeacf3ada071acd6b41f2b580f2d861b759711f58587fefd8", "query": "kube::test::get_object_assert pods \"{{range.items}}{{$image_field}}:{{end}}\" 'changed-with-yaml:' ## Patch pod from JSON can change image # Command <del> kubectl patch \"${kube_flags[@]}\" -f test/fixtures/doc-yaml/admin/limitrange/valid-pod.yaml -p='{\"spec\":{\"containers\":[{\"name\": \"kubernetes-serve-hostname\", \"image\": \"gcr.io/google_containers/pause-amd64:3.0\"}]}}' # Post-condition: valid-pod POD has image gcr.io/google_containers/pause-amd64:3.0 kube::test::get_object_assert pods \"{{range.items}}{{$image_field}}:{{end}}\" 'gcr.io/google_containers/pause-amd64:3.0:' </del> <ins> kubectl patch \"${kube_flags[@]}\" -f test/fixtures/doc-yaml/admin/limitrange/valid-pod.yaml -p='{\"spec\":{\"containers\":[{\"name\": \"kubernetes-serve-hostname\", \"image\": \"gcr.io/google_containers/pause-amd64:3.1\"}]}}' # Post-condition: valid-pod POD has image gcr.io/google_containers/pause-amd64:3.1 kube::test::get_object_assert pods \"{{range.items}}{{$image_field}}:{{end}}\" 'gcr.io/google_containers/pause-amd64:3.1:' </ins> ## If resourceVersion is specified in the patch, it will be treated as a precondition, i.e., if the resourceVersion is different from that is stored in the server, the Patch should be rejected ERROR_FILE=\"${KUBE_TEMP}/conflict-error\"", "positive_passages": [{"docid": "doc-en-kubernetes-7628cd26f0dafa992a4ea43a6c68b9bcdbf056fca43ee32b40ab60cef4154c17", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: pause does not reap zombie processes using the default pause container provided by What you expected to happen: should include the up to date pause code to reap zombie processes when using docker = 1.13.1 found here How to reproduce it (as minimally and precisely as possible): a.out will leave a zombie process that is not cleaned up Anything else we need to know?: Building the pause container from master solves this issue Related: Environment: Kubernetes version (use ): 1.7.0+ Cloud provider or hardware configuration**: N/A OS (e.g. from /etc/os-release): CentOS 7 Kernel (e.g. ): 4.10.13+ Install tools: Others: docker = 1.13.1\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\ni get a simliar problem when i run crond service in pod container, every day it makes some [anacron] zombie progresses UID PID PPID C STIME TTY TIME CMD root 1 0 0 Nov14 ? 00:00:00 /pause root 7 0 0 Nov14 ? 00:00:00 /usr/local/bin/dumb-init /usr/lo root 13 7 0 Nov14 ? 00:00:00 nginx: master process /usr/local nobody 21 13 0 Nov14 ? 00:00:01 nginx: worker process nobody 22 13 0 Nov14 ? 00:00:07 nginx: worker process nobody 23 13 0 Nov14 ? 00:00:07 nginx: worker process nobody 24 13 0 Nov14 ? 00:00:05 nginx: worker process root 77 1 0 Nov14 ? 00:00:00 [anacron] root 1 0 00:01 ? 00:00:00 [anacron] <defunctroot 1 0 01:01 ? 00:00:00 [anacron] <defunctroot 1 0 02:01 ?", "commid": "kubernetes_issue_50865", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-67ac32aff4ae5e7eeacf3ada071acd6b41f2b580f2d861b759711f58587fefd8", "query": "kube::test::get_object_assert pods \"{{range.items}}{{$image_field}}:{{end}}\" 'changed-with-yaml:' ## Patch pod from JSON can change image # Command <del> kubectl patch \"${kube_flags[@]}\" -f test/fixtures/doc-yaml/admin/limitrange/valid-pod.yaml -p='{\"spec\":{\"containers\":[{\"name\": \"kubernetes-serve-hostname\", \"image\": \"gcr.io/google_containers/pause-amd64:3.0\"}]}}' # Post-condition: valid-pod POD has image gcr.io/google_containers/pause-amd64:3.0 kube::test::get_object_assert pods \"{{range.items}}{{$image_field}}:{{end}}\" 'gcr.io/google_containers/pause-amd64:3.0:' </del> <ins> kubectl patch \"${kube_flags[@]}\" -f test/fixtures/doc-yaml/admin/limitrange/valid-pod.yaml -p='{\"spec\":{\"containers\":[{\"name\": \"kubernetes-serve-hostname\", \"image\": \"gcr.io/google_containers/pause-amd64:3.1\"}]}}' # Post-condition: valid-pod POD has image gcr.io/google_containers/pause-amd64:3.1 kube::test::get_object_assert pods \"{{range.items}}{{$image_field}}:{{end}}\" 'gcr.io/google_containers/pause-amd64:3.1:' </ins> ## If resourceVersion is specified in the patch, it will be treated as a precondition, i.e., if the resourceVersion is different from that is stored in the server, the Patch should be rejected ERROR_FILE=\"${KUBE_TEMP}/conflict-error\"", "positive_passages": [{"docid": "doc-en-kubernetes-6179feaaee46a15cd909bb088c82657b9b59fba8efdee1296995076588512032", "text": "00:00:00 [anacron] <defunctroot 1 0 03:01 ? 00:00:00 [anacron] <defunctroot 0 0 11:49 ? 00:00:00 /bin/bash root 0 1 19:15 ? 00:00:00 /bin/bash root 0 19:15 ? 00:00:00 ps -ef !\nDo we know why this was never resolved / was never deployed?\nI just fought through this issue with a rabbitmq helm chart. I had to custom build a pause container from master to fix it. The rabbitmq helm chart uses for its liveness checks. It's a thin wrapper around a call to the rabbitmq-server daemon, which is not PID 1 (/pause is PID 1). The rabbitmq-server process forks some children to do the work and then they exit. Since the pause-amd64:3.0 is not reaping, those processes stick around as zombies. The liveness check runs every 5 seconds. After about 4 hours, there are about 27K zombies and the node begins failing to launch new containers because it's starved for resources. The pause container built from current master fixes that behavior, no zombies at all in the container.\nThe plan is to build a new version of pause-amd64 and then update the image referenced by Kubernetes. This means the default image will change in the next Kubernetes release. We can make the new image available once the freeze lifts and we can merge .\nLooks like this made it into 1.10", "commid": "kubernetes_issue_50865", "tokennum": 336}], "negative_passages": []}
{"query_id": "q-en-kubernetes-67bd54c290f8eed4289386824ae26ef7c192eb784c4a7135ebde3cd6910c19e1", "query": "mkdir -p \"${DISCOVERY_ROOT_DIR}\" curl -kfsS -H 'Authorization: Bearer dummy_token' -H 'Accept: application/json;g=apidiscovery.k8s.io;v=v2;as=APIGroupDiscoveryList' \"https://${API_HOST}:${API_PORT}/apis\" | jq -S . > \"${DISCOVERY_ROOT_DIR}/aggregated_v2.json\" <del> # Deprecated, remove before v1.33 curl -kfsS -H 'Authorization: Bearer dummy_token' -H 'Accept: application/json;g=apidiscovery.k8s.io;v=v2beta1;as=APIGroupDiscoveryList' \"https://${API_HOST}:${API_PORT}/apis\" | jq -S . > \"${DISCOVERY_ROOT_DIR}/aggregated_v2beta1.json\" </del> kube::log::status \"Updating \" \"${OPENAPI_ROOT_DIR} for OpenAPI v2\" rm -f \"${OPENAPI_ROOT_DIR}/swagger.json\"", "positive_passages": [{"docid": "doc-en-kubernetes-1f38d50a57cfbeef9d8517599fecefb7d45971350552d6bdbc65534ca41945d0", "text": "Aggregated discovery v2beta1 fixtures should be removed. /sig api-machinery /triage accepted", "commid": "kubernetes_issue_127007", "tokennum": 22}], "negative_passages": []}
{"query_id": "q-en-kubernetes-67c7f87e4b643aa159846d1e748e600336cb8393b69a7e394aee540f916bb29b", "query": "return az.ExcludeMasterFromStandardLB != nil && *az.ExcludeMasterFromStandardLB } <ins> func (az *Cloud) disableLoadBalancerOutboundSNAT() bool { if !az.useStandardLoadBalancer() || az.DisableOutboundSNAT == nil { return false } return *az.DisableOutboundSNAT } </ins> // IsNodeUnmanaged returns true if the node is not managed by Azure cloud provider. // Those nodes includes on-prem or VMs from other clouds. They will not be added to load balancer // backends. Azure routes and managed disks are also not supported for them.", "positive_passages": [{"docid": "doc-en-kubernetes-f91ac3317a925ac3a02c50dc39021d458d6020da9f69361ec2732a68459b1b7c", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: is the recommended way to configure the outbound networks together with Azure standard loadbalancer (SLB). However, for load balancer rules are disabled by default. That means all frontend IPs would be used as the SNAT IPs for virtual machines, according to . This would introduce troubles for various security scenarios, as there's no way to get a stable list of egress IPs. Azure cloud provider should support this scenario, and disable the outbound SNAT when outbound rules are configured by provisioning tools. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Others: /kind bug /sig azure /priority critical-urgent", "commid": "kubernetes_issue_75281", "tokennum": 247}], "negative_passages": []}
{"query_id": "q-en-kubernetes-67cd0640b409436d66bca97c0af5b7848cafe2a5be4cf1d2a0f826ad3f2b02e7", "query": "}) <ins> ginkgo.It(\"should perform canary updates and phased rolling updates of template modifications for partiton1 and delete pod-0 without failing container\", func(ctx context.Context) { ginkgo.By(\"Creating a new StatefulSet without failing container\") ss := e2estatefulset.NewStatefulSet(\"ss2\", ns, headlessSvcName, 3, nil, nil, labels) deletingPodForRollingUpdatePartitionTest(ctx, f, c, ns, ss) }) ginkgo.It(\"should perform canary updates and phased rolling updates of template modifications for partiton1 and delete pod-0 with failing container\", func(ctx context.Context) { ginkgo.By(\"Creating a new StatefulSet with failing container\") ss := e2estatefulset.NewStatefulSet(\"ss3\", ns, headlessSvcName, 3, nil, nil, labels) ss.Spec.Template.Spec.Containers = append(ss.Spec.Template.Spec.Containers, v1.Container{ Name:    \"sleep-exit-with-1\", Image:   imageutils.GetE2EImage(imageutils.BusyBox), Command: []string{\"sh\", \"-c\"}, Args: []string{` echo \"Running in pod $POD_NAME\" _term(){ echo \"Received SIGTERM signal\" if [ \"${POD_NAME}\" = \"ss3-0\" ]; then exit 1 else exit 0 fi } trap _term SIGTERM while true; do echo \"Running in infinite loop in $POD_NAME\" sleep 1 done `, }, Env: []v1.EnvVar{ { Name: \"POD_NAME\", ValueFrom: &v1.EnvVarSource{ FieldRef: &v1.ObjectFieldSelector{ APIVersion: \"v1\", FieldPath:  \"metadata.name\", }, }, }, }, }) deletingPodForRollingUpdatePartitionTest(ctx, f, c, ns, ss) }) </ins> // Do not mark this as Conformance. // The legacy OnDelete strategy only exists for backward compatibility with pre-v1 APIs. ginkgo.It(\"should implement legacy replacement when the update strategy is OnDelete\", func(ctx context.Context) {", "positive_passages": [{"docid": "doc-en-kubernetes-cbff279a5a2209254c6527f41e3183737e33b6607a7e6fb4945b04f53611a022", "text": "My application is clustered and I have 2 pods running. I am using a rolling upgrade strategy and my partitioning number is 1. First I need to upgrade the pod with the ordinal number 1 so I triggered that upgrade with partitioning number 1 and my upgrade gets completed. After this, my pod having the ordinal number 0 gets restarted and it's automatically upgraded to a new image. This is not an expected behavior because still, my partition number is 1 and pod-0 should come up with an older image only. I am facing this issue for the v1.27 cluster. Prior to this, it was working fine. pod-0 should not upgrade to new image until I upgrade the partition number to 0.a Do helm install and upgrade pod-1 only keeping partition number to 1. No response <detailsconsole $ cat /etc/os-release $ uname -a C:wmic os get Caption, Version, BuildNumber, OSArchitecture </details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig/api-machinery\n/sig apps /sig storage\nHi, Can someone suggest here? As this is introduced in my setup after the v1.27 upgrade? Is there any change in partition logic?\nThis can be reproduced by using the said STS. 1 - Deploy STS using attached that has a replica count is 2 and updatingstrategy.rolling.partition as 1. 2 - Do edit STS and update the image to 1.15. This will upgrade, pod-1 with image 1.15. 3 - Next delete the pod pod-0 and check that POD-0 came up with a new image which is not the expected behavior. POD 0 should not be updated to a new image until the partition is changed to 0. We have noticed this behavior change in v1.27.", "commid": "kubernetes_issue_119685", "tokennum": 476}], "negative_passages": []}
{"query_id": "q-en-kubernetes-67cd0640b409436d66bca97c0af5b7848cafe2a5be4cf1d2a0f826ad3f2b02e7", "query": "}) <ins> ginkgo.It(\"should perform canary updates and phased rolling updates of template modifications for partiton1 and delete pod-0 without failing container\", func(ctx context.Context) { ginkgo.By(\"Creating a new StatefulSet without failing container\") ss := e2estatefulset.NewStatefulSet(\"ss2\", ns, headlessSvcName, 3, nil, nil, labels) deletingPodForRollingUpdatePartitionTest(ctx, f, c, ns, ss) }) ginkgo.It(\"should perform canary updates and phased rolling updates of template modifications for partiton1 and delete pod-0 with failing container\", func(ctx context.Context) { ginkgo.By(\"Creating a new StatefulSet with failing container\") ss := e2estatefulset.NewStatefulSet(\"ss3\", ns, headlessSvcName, 3, nil, nil, labels) ss.Spec.Template.Spec.Containers = append(ss.Spec.Template.Spec.Containers, v1.Container{ Name:    \"sleep-exit-with-1\", Image:   imageutils.GetE2EImage(imageutils.BusyBox), Command: []string{\"sh\", \"-c\"}, Args: []string{` echo \"Running in pod $POD_NAME\" _term(){ echo \"Received SIGTERM signal\" if [ \"${POD_NAME}\" = \"ss3-0\" ]; then exit 1 else exit 0 fi } trap _term SIGTERM while true; do echo \"Running in infinite loop in $POD_NAME\" sleep 1 done `, }, Env: []v1.EnvVar{ { Name: \"POD_NAME\", ValueFrom: &v1.EnvVarSource{ FieldRef: &v1.ObjectFieldSelector{ APIVersion: \"v1\", FieldPath:  \"metadata.name\", }, }, }, }, }) deletingPodForRollingUpdatePartitionTest(ctx, f, c, ns, ss) }) </ins> // Do not mark this as Conformance. // The legacy OnDelete strategy only exists for backward compatibility with pre-v1 APIs. ginkgo.It(\"should implement legacy replacement when the update strategy is OnDelete\", func(ctx context.Context) {", "positive_passages": [{"docid": "doc-en-kubernetes-78482ca8aa8474337677389890aeefe9bf7c97cdeab333d3d2b330616683b55b", "text": "Pla suggest : apiVersion: v1 kind: Service metadata: name: nginx labels: app: nginx spec: ports: port: 80 name: web clusterIP: None selector: app: nginx apiVersion: apps/v1 kind: StatefulSet metadata: name: web-am spec: updateStrategy: type: RollingUpdate rollingUpdate: partition: 1 serviceName: \"nginx\" replicas: 2 selector: matchLabels: app: nginx template: metadata: labels: app: nginx spec: containers: name: nginx args: /bin/sh -c sleep 30;touch /tmp/healthy; sleep 3600 image: nginx:1.14.2 ports: containerPort: 80 name: web", "commid": "kubernetes_issue_119685", "tokennum": 170}], "negative_passages": []}
{"query_id": "q-en-kubernetes-67f50274ba11dd64cb2d3453509e84cdb0bf2b5377f3a47f6c2f36dce419d5dd", "query": "if ss.excludeMasterNodesFromStandardLB() && isMasterNode(node) { continue } <ins> if ss.ShouldNodeExcludedFromLoadBalancer(node) { klog.V(4).Infof(\"Excluding unmanaged/external-resource-group node %q\", node.Name) continue } </ins> // in this scenario the vmSetName is an empty string and the name of vmss should be obtained from the provider IDs of nodes resourceGroupName, vmssName, err := getVmssAndResourceGroupNameByVMProviderID(node.Spec.ProviderID) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-55c62ef7d3a20811fc11fc78d986a318ea3d711ec0d8f690353464985c4986dd", "text": "What happened: After creating Kubernetes service on a Kubernetes cluster built on Azure IaaS (not AKS), nodes which are not master nodes but are also not worker nodes and which are labeled with are included in the backend pool for the load balancer. What you expected to happen: All nodes labeled with should be excluded from the load balancer's backend pool. How to reproduce it (as minimally and precisely as possible): Create a node with a type other than and label it with Anything else we need to know?: Environment: Kubernetes version (use ): Client Version: version.Info{Major:\"1\", Minor:\"16\", GitVersion:\"v1.16.10\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2020-05-20T14:00:52Z\", GoVersion:\"go1.13.9\", Compiler:\"gc\", Platform:\"linux/amd64\"} Server Version: version.Info{Major:\"1\", Minor:\"16\", GitVersion:\"v1.16.10\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2020-05-20T13:51:56Z\", GoVersion:\"go1.13.9\", Compiler:\"gc\", Platform:\"linux/amd64\"} Cloud provider or hardware configuration: Azure OS (e.g: ): CentOS Linux release 7.8.2003 (Core) Kernel (e.g. ): Linux master- 3.10.0-1127.8.2.el7.x8664 SMP Tue May 12 16:57:42 UTC 2020 x8664 x8664 x8664 GNU/Linux Install tools: Custom terraform stack Network plugin and version (if this is a network-related bug): Others:\n/sig cloud-provider These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by vllry. \u200d\n/priority important-soon /sig cloud-provider /area provider/azure\n/priority critical-urgent", "commid": "kubernetes_issue_93033", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-68631a912a8da368a1a862c61c859649af4bb74cae434e7a3b46fe7fe2d9dde6", "query": "} func PostStartHook(hookContext genericapiserver.PostStartHookContext) error { <del> clientset, err := rbacclient.NewForConfig(hookContext.LoopbackClientConfig) if err != nil { utilruntime.HandleError(fmt.Errorf(\"unable to initialize clusterroles: %v\", err)) return nil } existingClusterRoles, err := clientset.ClusterRoles().List(api.ListOptions{}) if err != nil { utilruntime.HandleError(fmt.Errorf(\"unable to initialize clusterroles: %v\", err)) return nil } // if clusterroles already exist, then assume we don't have work to do because we've already // initialized or another API server has started this task if len(existingClusterRoles.Items) > 0 { return nil } for _, clusterRole := range append(bootstrappolicy.ClusterRoles(), bootstrappolicy.ControllerRoles()...) { if _, err := clientset.ClusterRoles().Create(&clusterRole); err != nil { // don't fail on failures, try to create as many as you can </del> <ins> // intializing roles is really important.  On some e2e runs, we've seen cases where etcd is down when the server // starts, the roles don't initialize, and nothing works. err := wait.Poll(1*time.Second, 30*time.Second, func() (done bool, err error) { clientset, err := rbacclient.NewForConfig(hookContext.LoopbackClientConfig) if err != nil { </ins> utilruntime.HandleError(fmt.Errorf(\"unable to initialize clusterroles: %v\", err)) <del> continue </del> <ins> return false, nil </ins> } <del> glog.Infof(\"Created clusterrole.%s/%s\", rbac.GroupName, clusterRole.Name) } existingClusterRoleBindings, err := clientset.ClusterRoleBindings().List(api.ListOptions{}) if err != nil { utilruntime.HandleError(fmt.Errorf(\"unable to initialize clusterrolebindings: %v\", err)) return nil } // if clusterrolebindings already exist, then assume we don't have work to do because we've already // initialized or another API server has started this task if len(existingClusterRoleBindings.Items) > 0 { return nil } </del> <ins> existingClusterRoles, err := clientset.ClusterRoles().List(api.ListOptions{}) if err != nil { utilruntime.HandleError(fmt.Errorf(\"unable to initialize clusterroles: %v\", err)) return false, nil } // only initialized on empty etcd if len(existingClusterRoles.Items) == 0 { for _, clusterRole := range append(bootstrappolicy.ClusterRoles(), bootstrappolicy.ControllerRoles()...) { if _, err := clientset.ClusterRoles().Create(&clusterRole); err != nil { // don't fail on failures, try to create as many as you can utilruntime.HandleError(fmt.Errorf(\"unable to initialize clusterroles: %v\", err)) continue } glog.Infof(\"Created clusterrole.%s/%s\", rbac.GroupName, clusterRole.Name) } } </ins> <del> for _, clusterRoleBinding := range append(bootstrappolicy.ClusterRoleBindings(), bootstrappolicy.ControllerRoleBindings()...) { if _, err := clientset.ClusterRoleBindings().Create(&clusterRoleBinding); err != nil { // don't fail on failures, try to create as many as you can </del> <ins> existingClusterRoleBindings, err := clientset.ClusterRoleBindings().List(api.ListOptions{}) if err != nil { </ins> utilruntime.HandleError(fmt.Errorf(\"unable to initialize clusterrolebindings: %v\", err)) <del> continue </del> <ins> return false, nil } // only initialized on empty etcd if len(existingClusterRoleBindings.Items) == 0 { for _, clusterRoleBinding := range append(bootstrappolicy.ClusterRoleBindings(), bootstrappolicy.ControllerRoleBindings()...) { if _, err := clientset.ClusterRoleBindings().Create(&clusterRoleBinding); err != nil { // don't fail on failures, try to create as many as you can utilruntime.HandleError(fmt.Errorf(\"unable to initialize clusterrolebindings: %v\", err)) continue } glog.Infof(\"Created clusterrolebinding.%s/%s\", rbac.GroupName, clusterRoleBinding.Name) } </ins> } <del> glog.Infof(\"Created clusterrolebinding.%s/%s\", rbac.GroupName, clusterRoleBinding.Name) </del> <ins> return true, nil }) // if we're never able to make it through intialization, kill the API server if err != nil { return fmt.Errorf(\"unable to initialize roles: %v\", err) </ins> } return nil", "positive_passages": [{"docid": "doc-en-kubernetes-b8d2c0da68304e83135ba886da3cc34043a1f75faa72e9753c7e99fa612dae72", "text": "From etcd3: May need to retry poststarthook a few times to avoid bootstrapping failures like this.", "commid": "kubernetes_issue_39108", "tokennum": 26}], "negative_passages": []}
{"query_id": "q-en-kubernetes-688cc19f13570486ab69836d98980eea6cf5876eb3b7141c3a07b0fef8d931de", "query": "openapinamer \"k8s.io/apiserver/pkg/endpoints/openapi\" \"k8s.io/apiserver/pkg/registry/rest\" genericfilters \"k8s.io/apiserver/pkg/server/filters\" <ins> \"k8s.io/apiserver/pkg/warning\" </ins> \"k8s.io/client-go/informers\" \"k8s.io/client-go/kubernetes/fake\" restclient \"k8s.io/client-go/rest\"", "positive_passages": [{"docid": "doc-en-kubernetes-c00c4002c1ceb0f27a0d12e9f8008c8e3b435d9e5dbb0a6b5f62beaf7aea3677", "text": "I am doing v1.28.3 kube-apiserver testing in the test environment, and I often encounter kube-apiserver panic, especially when kube-apiserver call webhook fails. The following are the captured panic logs: and: kube-apiserver does not panic even if calling webhook times out or fails Deploy a webhook, remove the service corresponding to the webhook, and then create pods in batches to trigger webhook calls No response <details</details<detailsprivate cloud </details<details</details<details</details<details</details<details</details\n/sig api-machinery\nsomewhat related to\nThe scenarios that trigger panic are similar(the apiserver fails to call webhook), but the log shows that the location of panic is different.\n/assign For context of  Thank you. /triage accepted\nagain, full stack logs:\nI'll try to test the mr:\nLet me try to explain the panic - both goroutines are trying to write to the of the first goroutine: This request has timed out, and consequently the filter is trying to send a response to the caller. This is the client facing goroutine from the timeout filter. Note that the call to is protected by a mutex, that means that if the other goroutine is using the delegated object via the adapter, then this panic should not happen. second goroutine: let's check the other goroutine, it is also trying to write to the of the object: Now uses an unprotected version of the ResponseWriter object: The filter precedes the filter in the execution order, so the in is not using the thread safe implementation. This is the order today: one quick resolution is to move the after the timeout filter: , but there could be code that precedes that needs to write warning? Also note that the panic mentioned in is not as severe, it does not cause the apiserver to crash. For a more proper solution, i think we would want any thoughts?", "commid": "kubernetes_issue_122940", "tokennum": 443}], "negative_passages": []}
{"query_id": "q-en-kubernetes-688cc19f13570486ab69836d98980eea6cf5876eb3b7141c3a07b0fef8d931de", "query": "openapinamer \"k8s.io/apiserver/pkg/endpoints/openapi\" \"k8s.io/apiserver/pkg/registry/rest\" genericfilters \"k8s.io/apiserver/pkg/server/filters\" <ins> \"k8s.io/apiserver/pkg/warning\" </ins> \"k8s.io/client-go/informers\" \"k8s.io/client-go/kubernetes/fake\" restclient \"k8s.io/client-go/rest\"", "positive_passages": [{"docid": "doc-en-kubernetes-f6276625b0df7e8b951a42b4ce484e48eb7715b4546658f042b200999787970a", "text": "/cc\nI tend to remove the timeout filter, the sooner the better, and I think the Apiserver panic is the P0-level bug, directly affecting the availability of the cluster I have cherry-picked and tested it in my cluster, and I still need to continue to observe for 1-2 days\nI opened a minimal WIP fix for the warning writer in since the timeout filter removal is a much bigger change to reason through\nthanks a lot, I will try to test and cherry-pick the above minimal WIP fix in\nsorry, I completely overlooked , I only saw and that looked too big to take safely right now I prefer to\nCan we backport the fix to 1.28?\nWhy 1.28 specifically? I'm not aware of anything that changed in 1.28 that made this more or less prevalent. If this meets backport criteria, going to all active branches could make sense (1.27+)", "commid": "kubernetes_issue_122940", "tokennum": 191}], "negative_passages": []}
{"query_id": "q-en-kubernetes-68b0e92f78ebfde2f4757599420d11019f38776f043b8ecfc3bfc1f186ef2241", "query": "} kind = fqParentKind.Kind } <ins> verbOverrider, needOverride := storage.(StorageMetricsOverride) </ins> switch action.Verb { case \"GET\": // Get a resource. var handler restful.RouteFunction", "positive_passages": [{"docid": "doc-en-kubernetes-818250efc38f3e1e4f69f5ba9f53826c59d17d9aa3970f389bfaed5f09e5cc10", "text": "Is this a BUG REPORT or FEATURE REQUEST?: What happened: use kubectl search log with follow option get api latency (apiserverrequestlatenciessummary{quantile=\"0.99\",resource=\"pods\",verb=\"GET\"} )high to give a alert in my cluster. the apiserver log is below and we can see it costs 1m25s. What you expected to happen: do not make this api latency account in getting pod request api latency How to reproduce it (as minimally and precisely as possible): use kubectl to search a pod log with follow option long enough and you will get this metric apiserverrequestlatenciessummary{quantile=\"0.99\",resource=\"pods\",verb=\"GET\"} higher than the ordinary case. Anything else we need to know?: I am happy to fix it. Environment: Kubernetes version (use ): 1.6 Cloud provider or hardware configuration**: bare-metal OS (e.g. from /etc/os-release): ubuntu 16.04 Kernel (e.g. ): 4.4 Install tools: kubeadm Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig API Machinery\n/area apiserver\n/sig api-machinery\n/assign Thanks... looking forward to your PR!\nfixed with PTAL", "commid": "kubernetes_issue_49998", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-69086266779059a825e1fbaa72a24a127495b9d273314951e90ed9dd3b04b594", "query": "if skipFirstAllOfAnyOf && i == 0 { skipAnyOf = true } <del> allErrs = append(allErrs, validateNestedValueValidation(&v.AllOf[i], skipAnyOf, false, fldPath.Child(\"allOf\").Index(i))...) </del> <ins> allErrs = append(allErrs, validateNestedValueValidation(&v.AllOf[i], skipAnyOf, false, lvl, fldPath.Child(\"allOf\").Index(i))...) </ins> } for i := range v.OneOf { <del> allErrs = append(allErrs, validateNestedValueValidation(&v.OneOf[i], false, false, fldPath.Child(\"oneOf\").Index(i))...) </del> <ins> allErrs = append(allErrs, validateNestedValueValidation(&v.OneOf[i], false, false, lvl, fldPath.Child(\"oneOf\").Index(i))...) </ins> } <del> allErrs = append(allErrs, validateNestedValueValidation(v.Not, false, false, fldPath.Child(\"not\"))...) </del> <ins> allErrs = append(allErrs, validateNestedValueValidation(v.Not, false, false, lvl, fldPath.Child(\"not\"))...) </ins> return allErrs } // validateNestedValueValidation checks the nested value validation under a logic junctor in a structural schema. <del> func validateNestedValueValidation(v *NestedValueValidation, skipAnyOf, skipAllOfAnyOf bool, fldPath *field.Path) field.ErrorList { </del> <ins> func validateNestedValueValidation(v *NestedValueValidation, skipAnyOf, skipAllOfAnyOf bool, lvl level, fldPath *field.Path) field.ErrorList { </ins> if v == nil { return nil } allErrs := field.ErrorList{} <del> allErrs = append(allErrs, validateValueValidation(&v.ValueValidation, skipAnyOf, skipAllOfAnyOf, fldPath)...) allErrs = append(allErrs, validateNestedValueValidation(v.Items, false, false, fldPath.Child(\"items\"))...) </del> <ins> allErrs = append(allErrs, validateValueValidation(&v.ValueValidation, skipAnyOf, skipAllOfAnyOf, lvl, fldPath)...) allErrs = append(allErrs, validateNestedValueValidation(v.Items, false, false, lvl, fldPath.Child(\"items\"))...) </ins> for k, fld := range v.Properties { <del> allErrs = append(allErrs, validateNestedValueValidation(&fld, false, false, fldPath.Child(\"properties\").Key(k))...) </del> <ins> allErrs = append(allErrs, validateNestedValueValidation(&fld, false, false, fieldLevel, fldPath.Child(\"properties\").Key(k))...) </ins> } if len(v.ForbiddenGenerics.Type) > 0 {", "positive_passages": [{"docid": "doc-en-kubernetes-4be11de3bdb9e2a86ad3a19c4d6f5342db422d48e5979c118fca9ce077f64900", "text": "We allow CRD authors to write . Currently we don't restrict writing validation for , which means people can have . For example, people can have additive name constraints (require CR to be ) with the following schema: This brings us two questions: do we if \"metadata\" is included in the schema: simplest option is to publish standard metav1.ObjectMeta schema info, and use any CRD-specified \"metadata\" properties as additive validation (just like in-tree types do, publishing standard ObjectMeta schema info, and implementing type-specific name validation internally) alternatively, we can try merging user-specified metadata schema with the standard one. Technically people should only add extra validation to existing metadata properties (adding new fields to metadata won't work since they will be pruned by built-in validation first), but it's unclear to me how arbitrary people may want the metadata validation to be term question is whether to allow people specifying metadata validation at all, or just allow a subset (like name validation) in CRD v1 /sig api-machinery /area custom-resources cc\nWhat is the difference between these two? I mean the end result is the same right? The only thing that can be is validation. Nothing else works unless you are considering extensions?\nThe former means we drop/hide user-specified metadata schema when we publish CRD OpenAPI. We still validate user-specified constraints on server side, but client-side validation won't see them. The latter enables client-side user-specified metadata validation.\nIf it's possible to merge with standard metadata schema info, or at the cost of not publishing the standard schema. My inclination would be to publish the complete standard schema for metadata/apiVersion/kind, which we know is complete and accurate, and use and user-specified schema for those fields as addition validations server side", "commid": "kubernetes_issue_74620", "tokennum": 396}], "negative_passages": []}
{"query_id": "q-en-kubernetes-691903eb76e53fb64e55f59de517b45dd3a99e6974dd6d86c614780b5523da09", "query": "want:      []string{ss1Rev1.Name, ss1Rev2.Name, ss1Rev3.Name}, }, { <ins> name:      \"with ties\", revisions: []*apps.ControllerRevision{ss1Rev3, ss1Rev3Time2, ss1Rev2, ss1Rev1}, want:      []string{ss1Rev1.Name, ss1Rev2.Name, ss1Rev3.Name, ss1Rev3Time2.Name, ss1Rev3Time2Name2.Name}, }, { </ins> name:      \"empty\", revisions: nil, want:      nil,", "positive_passages": [{"docid": "doc-en-kubernetes-4d5dc3f2fd1aa2418695125e98dd263b9bbd4b25db7ea8b25723d335bfe8c79b", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Statefulsets are sometimes continually rolling pods and I don't know why statefulset created: storageclass referenced: kubectl describe statefulset statefulset-test: As you can see from the above describe, the pod in the statefulset has been restarted a lot of times. Observing the created pod, 1) The pod comes up ready 2) immediately transitions to terminating 3) Is terminated 4) A new pod is created 5) Go back to (1) (repeats forever) Despite no updates to the statefulset spec ocurring. Making a change to the statefulset template (for example a trivial change adding a nonsense annotation) stops the rolling and fixes the issue When this statefulset was created, there was a mutating webhook enabled. After the observed pod rolling. I disabled this by making its configuration invalid and making it non required, and the rolling persisted. The status of the statefulset: : You can see that there is a discrepency between currentRevision and updateRevision. currentRevision: statefulset-test- updateRevision: statefulset-test- A short while later the status is changed to contain currentRevision: statefulset-test- updateRevision: statefulset-test- This change happened at Sun Apr 1 19:48:48 2018 Presumably after the rollout of statefulset-test- is complete.", "commid": "kubernetes_issue_61998", "tokennum": 342}], "negative_passages": []}
{"query_id": "q-en-kubernetes-691903eb76e53fb64e55f59de517b45dd3a99e6974dd6d86c614780b5523da09", "query": "want:      []string{ss1Rev1.Name, ss1Rev2.Name, ss1Rev3.Name}, }, { <ins> name:      \"with ties\", revisions: []*apps.ControllerRevision{ss1Rev3, ss1Rev3Time2, ss1Rev2, ss1Rev1}, want:      []string{ss1Rev1.Name, ss1Rev2.Name, ss1Rev3.Name, ss1Rev3Time2.Name, ss1Rev3Time2Name2.Name}, }, { </ins> name:      \"empty\", revisions: nil, want:      nil,", "positive_passages": [{"docid": "doc-en-kubernetes-25284c3702a45280c2a40fae68a3ba4d1c026c9e5d96ab43c2dee09fe3985aa0", "text": "Here are all the controllerrevisions from above: kubectl get controllerrevision statefulset-test- -o yaml kubectl get controllerrevision statefulset-test- -o yaml: kubectl get controllerrevision statefulset-test- -o yaml: The differences between the above controllerrevisions are insignificant (the hash, the creation timestamp, the name, the resource version, the uid, the self link) Interestingly all these controllerrevisions were created very close together in time shortly after I created the statefulset The current controllerrevisions are After watching the state change for a while, it actually seems like the statefulset is just cycling through the updateRevision being one of the above 10 controllerrevisions Leaders during this time From kube-controller-manager logs during this time, here is one excerpt: The error sync in there is suspicous, and as you can see the controllerrevisions are changing in the logs I have the full logs from a 5 minute window on either side of the above if necessary. The reason I'm inclined to think this is a kubernetes bug is that any update to the statefulset template fixes the problem. How to reproduce it (as minimally and precisely as possible): Not really sure. Worth just trying to create the above statefulset (requires creating the I tried deleting and recreating the above statefulset and it didn't happen, so something flaky is going on Anything else we need to know?: kubernetes 1.9.3 (client and server) cloud provider: aws\n/sig apps\nI realize this will probably need some further debugging, happy to get some direction\nConsistent repro: Create a statefulset that creates a controllerrevision whose hash is between max int32 and max uint32 (this shouldn't be that hard to do, possibly a 50/50 chance of this). Manually create a controllerrevision identical to the first (same revision), incrementing both the name and hash by one. See that the statefulset controller will continually switch which controller revision should be the target of the statefulset.\nDue to the issue fixed here: , under some circumstances controllerrevisions whose revision is the same were being considered equal.", "commid": "kubernetes_issue_61998", "tokennum": 496}], "negative_passages": []}
{"query_id": "q-en-kubernetes-691903eb76e53fb64e55f59de517b45dd3a99e6974dd6d86c614780b5523da09", "query": "want:      []string{ss1Rev1.Name, ss1Rev2.Name, ss1Rev3.Name}, }, { <ins> name:      \"with ties\", revisions: []*apps.ControllerRevision{ss1Rev3, ss1Rev3Time2, ss1Rev2, ss1Rev1}, want:      []string{ss1Rev1.Name, ss1Rev2.Name, ss1Rev3.Name, ss1Rev3Time2.Name, ss1Rev3Time2Name2.Name}, }, { </ins> name:      \"empty\", revisions: nil, want:      nil,", "positive_passages": [{"docid": "doc-en-kubernetes-59ace9008f72ca5d82f22a23445c41e6f5a4a98690d88922022af0dc9f3faebe", "text": "This ends up causing this bug to manifest as follows: ListRevisions finds many controllerrevisions with the same revision (unclear how this state happens, but it can happen) The sort here randomly sorts them Due to the linked bug , FindEqualRevisions incorrectly finds that all these controller revisions are equal to the proposed udpate. The updateRevision selects the last revision found here Therefore, updateRevision, is randomly selected and causes the bug. This fixes the immediate issue, but the sort should probably be made stable (i.e not just look at the revision number, perhaps just consider the hash for tie breakers)\nAs an update, fixing the equality check will not be sufficient because it is possible for multiple controller revisions to be created that are actually equal, including the same hash, that have the same revision number. I believe the fix will need to be equal controllerrevisions with the same revision number from being created sort the controllerrevisions so that the controllerrevision that is the target of the statefulset is stable\nIssues 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\n/remove-lifecycle stale\nping I use the K8S which version is 1.11.4 and encounter the same problem. I want to reproduce the problem and find your way: Manually create a controllerrevision identical to the first (same revision), incrementing both the name and hash by one. Could you tell me how to mannually create a same controllerrevision identical to the first? Thanks in anvance.", "commid": "kubernetes_issue_61998", "tokennum": 374}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6944ce8a45573317d8a00b3062f6713e6adb18f522313f13400ff1b58d878c91", "query": "// Create a deployment to delete nginx pods and instead bring up redis pods. deploymentName := \"redis-deployment-2\" Logf(\"Creating deployment %s\", deploymentName) <del> _, err = c.Deployments(ns).Create(newDeployment(deploymentName, replicas, deploymentPodLabels, \"redis\", \"redis\")) </del> <ins> _, err = c.Deployments(ns).Create(newDeployment(deploymentName, replicas, deploymentPodLabels, \"redis\", \"redis\", extensions.RollingUpdateDeploymentStrategyType)) </ins> Expect(err).NotTo(HaveOccurred()) defer func() { deployment, err := c.Deployments(ns).Get(deploymentName)", "positive_passages": [{"docid": "doc-en-kubernetes-ceb20554e653f6657baad1bbb36c40e66d8a76887956e3c674b77febc82d4455", "text": "There's some practical limit on the number of concurrent access tokens that can be used in a Kubernetes cluster before it begins to spend all of its time in the authn stack verifying them. Absent fixes to it was < 500; with the fixes linked there it's still not infinitely scalable-- I still hit (what I believe to be) with ~ 5k unique tokens @ ~700QPS. This request is to this dimension an official name & definition, and list it with others, e.g. here: it it have a useful value (I think it should be 10k) /kind bug /sig scalability\n/cc\noh and 4. add tests which verify it is as high as believed.\ncc since projected tokens will increase the number of unique tokens\n/sig auth\nLRUs are not good at scaling and sharding has some major pitfalls as pointed out. I would suggest that we try to drop the LRU cache for successful authentication results in the token cache. The main benefit of using an LRU here is bound cache size. Entries in the token cache have a fast expiration independent of the LRU policy. The records probably take up O(2kb) (guesstimate) of memory. Given that these are successful attempts with presumably valid tokens, I don't think we are getting any benefit from the LRU. If we don't have a constraint on fixed cache size, we can back the token cache with a sync.Map and run a single background goroutine to periodically walk the map and remove expired entries. This would fix the problematic locking and eviction due to nonuniform distribution of tokens over shards. The failure cache is less important and we don't cache failures by default. If we consider this the \"slowpath\", we can probably leave it as. If that's not good enough, we have a couple options (with various tradeoffs) to improve it.\nIf off by default is not enough, more reasoning why the failed cache is not super useful: it might help with an accidental DoS but it doesn't prevent anything actively malicious DoS. I think we can focus our improvements on the success cache.\n/assign He is already working on adding an explicit test for it.\nhas taken it over and is actively working on this. Unfortunately, I cannot assign this issue to him as he's not a k8s member yet\nIt's not closed - all testes must be submitted and appropriate documentation must be\nThanks everyone!!", "commid": "kubernetes_issue_83375", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-69864ab041018e5d525330c3d51561768f2093a2d3bc5bf58eaa5ba639fc3990", "query": "if (-not (Test-Path $user_dir)) { # If for some reason Create-NewProfile failed to create the user profile # directory just continue on to the next user. <del> continue </del> <ins> return </ins> } # NOTE: there is a race condition here where someone could try to ssh to", "positive_passages": [{"docid": "doc-en-kubernetes-9ba650efd322225fce569f5f04b924197d000dece17d628f51cd31eac5f4f289", "text": "I followed the document to create an e2e cluster However, doesn't work after the cluster is up. I got the following error: /cc\n/cc\nwhere are you trying to ssh from? Can you ssh to a Linux instance in GCE? If you run do you see ssh keys there? Do any of them match a public key that you have under ? There could be a delay the very first time you try to ssh; we noted this in , but we could add it to the README too. If you try a second time after a couple minutes does it still fail?\nYeah I can ssh to a linux instance in the same cluster. It still fails after a long. I've removed all my ssh keys from cloud metadata, and recreating a cluster. Let me see how it goes this time.\nI still got the same error after recreating the cluster. I can ssh into linux nodes in the same cluster just fine.", "commid": "kubernetes_issue_81734", "tokennum": 201}], "negative_passages": []}
{"query_id": "q-en-kubernetes-69872a95bf1d4d39ddda8265678af3c31614c49a571ebca77134e81cfa9f4606", "query": "logger.V(5).Info(\"Starting attacherDetacher.AttachVolume\", \"volume\", volumeToAttach) err := rc.attacherDetacher.AttachVolume(logger, volumeToAttach.VolumeToAttach, rc.actualStateOfWorld) if err == nil { <del> logger.Info(\"attacherDetacher.AttachVolume started\", \"volume\", volumeToAttach) </del> <ins> logger.Info(\"attacherDetacher.AttachVolume started\", \"volumeName\", volumeToAttach.VolumeName, \"nodeName\", volumeToAttach.NodeName, \"scheduledPods\", klog.KObjSlice(volumeToAttach.ScheduledPods)) </ins> } if err != nil && !exponentialbackoff.IsExponentialBackoff(err) { // Ignore exponentialbackoff.IsExponentialBackoff errors, they are expected. // Log all other errors. <del> logger.Error(err, \"attacherDetacher.AttachVolume failed to start\", \"volume\", volumeToAttach) </del> <ins> logger.Error(err, \"attacherDetacher.AttachVolume failed to start\", \"volumeName\", volumeToAttach.VolumeName, \"nodeName\", volumeToAttach.NodeName, \"scheduledPods\", klog.KObjSlice(volumeToAttach.ScheduledPods)) </ins> } } }", "positive_passages": [{"docid": "doc-en-kubernetes-a26579e34c4e1ee413ed781fcfba121a4c6a53c97161cd6f60e138eced3ebf5d", "text": "Keep running but not crashing Have a long volume attach path This corresponds to these lines We are using k0s <details</detailsbare metal <details</details<details</details<details</details<details</details\nI turned to use the JSON logger, it is gorgeous no wonder it failed\nrelated\n/sig node storage\n/cc\nVolumeToAttach contains Pod pointers, so yes, I think we should not log the entire struct, and only log important parts to it. /triage accepted /help-wanted\n/priority important-longterm /assign", "commid": "kubernetes_issue_114483", "tokennum": 123}], "negative_passages": []}
{"query_id": "q-en-kubernetes-699b0344c12b58f7715d84037418ceaebcf56ccac2c59be3e79db3eb64d3cfd5", "query": "true, }, { <del> \"mounting-unix-socket\", </del> <ins> \"mount-unix-socket\", </ins> func(base string) error { <del> testSocketFile := filepath.Join(base, \"mount_test.sock\") _, err := net.Listen(\"unix\", testSocketFile) if err != nil { return fmt.Errorf(\"Error preparing socket file %s with %v\", testSocketFile, err) </del> <ins> socketFile, socketError := createSocketFile(base) if socketError != nil { return fmt.Errorf(\"Error preparing socket file %s with %v\", socketFile, socketError) </ins> } return nil }, <del> \"mount_test.sock\", </del> <ins> \"mt.sock\", </ins> false, }, { \"mounting-unix-socket-in-middle\", func(base string) error { <del> testSocketFile := filepath.Join(base, \"mount_test.sock\") _, err := net.Listen(\"unix\", testSocketFile) if err != nil { return fmt.Errorf(\"Error preparing socket file %s with %v\", testSocketFile, err) </del> <ins> testSocketFile, socketError := createSocketFile(base) if socketError != nil { return fmt.Errorf(\"Error preparing socket file %s with %v\", testSocketFile, socketError) </ins> } return nil }, <del> \"mount_test.sock/bar\", </del> <ins> \"mt.sock/bar\", </ins> true, }, }", "positive_passages": [{"docid": "doc-en-kubernetes-ea06bb5e10f9c1a3c6e6bdd4b05e49a63cf7c6313178f3d65784c243007cbe65", "text": "Subpath unix socket tests can flake because of long socket path. On Linux the path limit should be 108 chars or less. /sig storage", "commid": "kubernetes_issue_61844", "tokennum": 31}], "negative_passages": []}
{"query_id": "q-en-kubernetes-69bd6ef272b0795b7dac35934225cd5d3cc3c94ce8906b72ef93dfa483be2c3b", "query": "return f } <ins> type CSINodeLister []storagev1.CSINode // Get returns a fake CSINode object. func (n CSINodeLister) Get(name string) (*storagev1.CSINode, error) { for _, cn := range n { if cn.Name == name { return &cn, nil } } return nil, fmt.Errorf(\"csiNode %q not found\", name) } // List lists all CSINodes in the indexer. func (n CSINodeLister) List(selector labels.Selector) (ret []*storagev1.CSINode, err error) { return nil, fmt.Errorf(\"not implemented\") } func getFakeCSINodeLister(csiNode *storagev1.CSINode) CSINodeLister { csiNodeLister := CSINodeLister{} if csiNode != nil { csiNodeLister = append(csiNodeLister, *csiNode.DeepCopy()) } return csiNodeLister } </ins> func (f *fakeKubeletVolumeHost) SetKubeletError(err error) { f.mux.Lock() defer f.mux.Unlock()", "positive_passages": [{"docid": "doc-en-kubernetes-43fa70370952068e2f27033c41492113945a1e0b0ce47a43a47f5065969f2aa7", "text": "After the cluster was updated to enable PD CSI Driver, there was a race condition where AD Controller (kube-controller-manager) started to BEFORE the PD CSI Driver was up, thus AD Controller gave us the error Then AD Controller triggered the disk detach because the disk/volume was not populated in the desired state of world. Unfortunately the disk was in use during this detach and got corrupted. Since cluster upgrades can cause the controller manager and CSI drivers to start at different times, the AD controller needs to be more conservative when detaching We have not been able to reproduce this, it came up from a customer. /sig storage /assign <detailsk8s 1.23, CSI migration enabled </details<detailsGKE </details<details</details<details</details<details</details<details</details\n/triage accepted\nI think there's potentially two changes we should do: 1) for the initial DSW population, we should skip the check that if the csi driver is not installed. 2) in general, we should not skip volumes during dsw initial population if an error is returned. If we had some temporary api server error then that would cause volumes to not get to dsw and similar behavior happen. cc\nfor a repro, maybe you can try something like: a cluster with csi migration enabled (control plane + nodes) a pod with intree-volume and get it running the csi driver node daemonset. verify the driver is removed from CSINode kube-controller-manager\ncc\n/cc was trying to repro this, but on GKE with the managed driver which made it complicated.\nYeah maybe gce kube-up would be easier for a repro\nIf CSINode says that it has migrated GCP PD volume plugin to CSI, then IMO A/D controller should always attach GCP PD volumes to it using CSI, regardless if the CSI driver is present or not. In-tree volume plugin in the kubelet is disabled and can't mount any in-tree volumes anyway. To flip the migration feature gate / upgrade / downgrade kubelet, the cluster admin must drain the node first to make sure everything is detached. A/D controller should not see change of CSINode migration annotations with any volume attached to it.\n/priority important-soon\nAnother option could be to process these volumes anyways but add them to DSOW with migration status as \"uncertain\", so as they can be re-processed later.", "commid": "kubernetes_issue_115297", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-69bd6ef272b0795b7dac35934225cd5d3cc3c94ce8906b72ef93dfa483be2c3b", "query": "return f } <ins> type CSINodeLister []storagev1.CSINode // Get returns a fake CSINode object. func (n CSINodeLister) Get(name string) (*storagev1.CSINode, error) { for _, cn := range n { if cn.Name == name { return &cn, nil } } return nil, fmt.Errorf(\"csiNode %q not found\", name) } // List lists all CSINodes in the indexer. func (n CSINodeLister) List(selector labels.Selector) (ret []*storagev1.CSINode, err error) { return nil, fmt.Errorf(\"not implemented\") } func getFakeCSINodeLister(csiNode *storagev1.CSINode) CSINodeLister { csiNodeLister := CSINodeLister{} if csiNode != nil { csiNodeLister = append(csiNodeLister, *csiNode.DeepCopy()) } return csiNodeLister } </ins> func (f *fakeKubeletVolumeHost) SetKubeletError(err error) { f.mux.Lock() defer f.mux.Unlock()", "positive_passages": [{"docid": "doc-en-kubernetes-8286ec57fa1e024ad026b2342f466cffd200140a0a95c9b64ae688331c52eb45", "text": "But surely it looks like might be easiest unless it has any downsides.\nThere wasn't a node update in this case---there was a control plane update which restarted the PD CSI driver, and it looks like the CSIDriver resource was updated or changed in some way which raced with the kube-controller-manager restart.\nIs there anyway we can know if the csi driver is up and running(like a health check ping) before populating DSW?\nWe use the CSINode registration to determine that. The discussion here I think is concluding that we should not use that as a criteria for adding the volume to DSW. We only need to check that CSI migration is enabled on the node.\n+1 we need to be very resilient against races, I think we have to assume a driver is in process of being installed at any point in the AD controller reconcilliation.\n/assign sunnylovestiramisu\nReproduced with the steps: In /var/log/kube-controller-\nTested with the and doing the reproduce steps above. The error of does not show up anymore. The error message still get logged in the kube-controller- for debugging purpose: Ran Ran On the GCP console, the disk is used by node: Ran I redeploy the pd-csi-driver and then make sure it is up and running. Ran", "commid": "kubernetes_issue_115297", "tokennum": 285}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6a1b0872dab68d089605077754a375404f032cef3d97587b961f0aee741c4b5d", "query": "containers: # TODO: Add resources in 1.8 - name: event-exporter <del> image: gcr.io/google-containers/event-exporter:v0.1.0-r2 </del> <ins> image: gcr.io/google-containers/event-exporter:v0.1.4 </ins> command: - '/event-exporter' - name: prometheus-to-sd-exporter", "positive_passages": [{"docid": "doc-en-kubernetes-efc4d6f641fd1b1bcaa275636a136a6176382b556456e87b10de85fb3c9c026d", "text": "Every time watch is reset, event exporter exports an entry about it to Stackdriver. To make it less irritating, this has to be done once per container run Related image PR: /cc", "commid": "kubernetes_issue_47914", "tokennum": 40}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6ab9a49b545aca76b5a6e2ca3370678fd0643230063feab1dd28bdd89b3ce92c", "query": "} func (c *LRUExpireCache) Get(key lru.Key) (interface{}, bool) { <del> c.lock.RLock() defer c.lock.RUnlock() </del> <ins> c.lock.Lock() defer c.lock.Unlock() </ins> e, ok := c.cache.Get(key) if !ok { return nil, false", "positive_passages": [{"docid": "doc-en-kubernetes-125faf475ef5c9fadc127cee08d3d538bc2825eff7d3fd81be9f088e2d4a0dbf", "text": "Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see ): No What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): \"LRUExpireCache\" Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT What happened: requires write lock since needs to manipulate its list to track recently used item. Currently it uses read lock so it may introduce race condition. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else do we need to know:\nThis was fixed in", "commid": "kubernetes_issue_31081", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6ad1efbc670277278f3c98c91b02f1f82bf7d7016d5e90d8aba6332e86302155", "query": "return isDummyVMPresent, nil } <ins> func (vs *VSphere) GetNodeNameFromProviderID(providerID string) (string, error) { var nodeName string nodes, err := vs.nodeManager.GetNodeDetails() if err != nil { glog.Errorf(\"Error while obtaining Kubernetes node nodeVmDetail details. error : %+v\", err) return \"\", err } for _, node := range nodes { // ProviderID is UUID for nodes v1.9.3+ if node.VMUUID == GetUUIDFromProviderID(providerID) || node.NodeName == providerID { nodeName = node.NodeName break } } if nodeName == \"\" { msg := fmt.Sprintf(\"Error while obtaining Kubernetes nodename for providerID %s.\", providerID) return \"\", errors.New(msg) } return nodeName, nil } </ins> func GetVMUUID() (string, error) { id, err := ioutil.ReadFile(UUIDPath) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-8cc0000ebdb21aeba4d3dda4212069010f35d863300d721e65a4eeef908ef7b3", "text": "As planned for 1.12 in kubernetes/features: After , the next step is to add the logic to the reconciler to detach the volumes when the nodeShutdown taint is applied. /assign /sig storage /kind feature looping\nHow do you know that node is Shutdown? is it a planned shutdown or a unplanned shutdown?\nAFAIK regardless of whether it's planned or not, it's detected by the cloud provider. In case of bare-metal node it doesn't happen automatically, as there is no universal way to reliably determine if a node is powered off, so the node must be tainted as by some external source.\nIssues 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\nany update on this issue?\n, I am currently working with sig-node team on handling node shut down. I will make a proposal and discuss in sig-node meeting next Tuesday. Will post the update soon.\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten /kind bug /priority critical-urgent /assign /sig node\nThose labels are not set on the issue: <detailsIn response to : /remove-kind feature 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\nIssues 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\nany update on this? is it going to be part of 1.15?\nStale issues rot after 30d of inactivity. Mark the issue as fresh with .", "commid": "kubernetes_issue_66181", "tokennum": 511}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6ad1efbc670277278f3c98c91b02f1f82bf7d7016d5e90d8aba6332e86302155", "query": "return isDummyVMPresent, nil } <ins> func (vs *VSphere) GetNodeNameFromProviderID(providerID string) (string, error) { var nodeName string nodes, err := vs.nodeManager.GetNodeDetails() if err != nil { glog.Errorf(\"Error while obtaining Kubernetes node nodeVmDetail details. error : %+v\", err) return \"\", err } for _, node := range nodes { // ProviderID is UUID for nodes v1.9.3+ if node.VMUUID == GetUUIDFromProviderID(providerID) || node.NodeName == providerID { nodeName = node.NodeName break } } if nodeName == \"\" { msg := fmt.Sprintf(\"Error while obtaining Kubernetes nodename for providerID %s.\", providerID) return \"\", errors.New(msg) } return nodeName, nil } </ins> func GetVMUUID() (string, error) { id, err := ioutil.ReadFile(UUIDPath) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-8b5c9612057f9871f14258bc136d8e86f57d2327861ec200bbe8402ae4819108", "text": "Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten\nIssues 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\n/remove-lifecycle stale\n/priority important-longterm\nIssues 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\n/remove-lifecycle stale /lifecycle frozen\n/triage accepted /kind feature\nThis 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\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI think this can be closed now as we have non-graceful node shutdown.\n/close\nClosing 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", "commid": "kubernetes_issue_66181", "tokennum": 436}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6ad84b19a3315068cb4b516a73d964e1d1cf3d9e9b7ac6dba4c75ecbd58bf399", "query": "defer logs.FlushLogs() if err := command.Execute(); err != nil { <del> fmt.Fprintf(os.Stderr, \"error: %vn\", err) </del> os.Exit(1) } }", "positive_passages": [{"docid": "doc-en-kubernetes-0b2213d42768c43adcb1b4f15cf67b8722c82d28c3ec9792f5837d41705eb847", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: kubectl version --client=yes command is giving the following error message. Error message is repeated at the start and the end and also containing programming jargon Error: invalid argument \"yes\" for \"--client\" flag: strconv.ParseBool: parsing \"yes\": invalid syntax Examples: Print the client and server versions for the current context kubectl version Options: --client=false: Client version only (no server required). -o, --output='': One of 'yaml' or 'json'. --short=false: Print just the version number. Usage: kubectl version [flags] [options] Use \"kubectl options\" for a list of global command-line options (applies to all commands). invalid argument \"yes\" for \"--client\" flag: strconv.ParseBool: parsing \"yes\": invalid syntax What you expected to happen: The error message can be improved with one of the two variants invalid argument \"yes\" for \"--client\" flag Examples: Print the client and server versions for the current context kubectl version Options: --client=false: Client version only (no server required). -o, --output='': One of 'yaml' or 'json'. --short=false: Print just the version number. Usage: kubectl version [flags] [options] Use \"kubectl options\" for a list of global command-line options (applies to all commands). (or) Invalid argument \"yes\" for \"--client\" flag How to reproduce it (as minimally and precisely as possible): Run the command kubectl version --client=yes Anything else we need to know?: Environment: Kubernetes version (use ): 1.15 Cloud provider or hardware configuration: AWS OS (e.g: ): Amazon Linux Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig cli\nHi Thanks for posting this issue! It turns out that this duplicate output has been in kubectl, and all the other cli cmds, since . This should be fixed by , and hopefully we can cherry pick it back to at least .", "commid": "kubernetes_issue_79454", "tokennum": 560}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6ae6aba4ef6e30e41f62cefa69825dcbb791f9f2ed952a54ed15015799ff8269", "query": "// Register registers the device plugin for the given resourceName with Kubelet. func (m *Stub) Register(kubeletEndpoint, resourceName string) error { <del> conn, err := grpc.Dial(kubeletEndpoint, grpc.WithInsecure(), </del> <ins> conn, err := grpc.Dial(kubeletEndpoint, grpc.WithInsecure(), grpc.WithBlock(), grpc.WithTimeout(10*time.Second), </ins> grpc.WithDialer(func(addr string, timeout time.Duration) (net.Conn, error) { return net.DialTimeout(\"unix\", addr, timeout) }))", "positive_passages": [{"docid": "doc-en-kubernetes-3e8f9b25d1f3d96c25ea3e7b882f872baf67d41cad6a3bbcf2df0e192dbdfda5", "text": "This is not 100% reproducable in my cluster. There is 20% chance of failing in my environment.\n/area hw-accelerators mentioned a root cause that might be due to unit tests sharing the same Unix socket and interfering with each others. cc\nCan you please share latest commit id of your code base using ?\nThanks very much, can you try the follow command please:\n/assign\nThe latest commit id of my code base:\nI found this is not 100% reproducable in my cluster. There is 20% chance of failing in my environment.\nResult of go test command:\n/sig scheduling\nThanks!\nHi, does these unit tests pass with PR\nI run 100 times without failure.\nGood to here that, Nice work! Thanks!", "commid": "kubernetes_issue_58281", "tokennum": 154}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6aeb5a46e6fd0c4ce57e9cb19104e750622c6cec989528baa4dfa5e12e248cac", "query": "[[projects]] name = \"github.com/modern-go/reflect2\" packages = [\".\"] <del> revision = \"1df9eeb2bb81f327b96228865c5687bc2194af3f\" version = \"1.0.0\" </del> <ins> revision = \"4b7aa43c6742a2c18fdef89dd197aaae7dac7ccd\" version = \"1.0.1\" </ins> [solve-meta] analyzer-name = \"dep\" analyzer-version = 1 <del> inputs-digest = \"56a0b9e9e61d2bc8af5e1b68537401b7f4d60805eda3d107058f3171aa5cf793\" </del> <ins> inputs-digest = \"ea54a775e5a354cb015502d2e7aa4b74230fc77e894f34a838b268c25ec8eeb8\" </ins> solver-name = \"gps-cdcl\" solver-version = 1", "positive_passages": [{"docid": "doc-en-kubernetes-0d085a3ee589d9a38ade8c650d9534110265a809ec41b82f41ce81cebea870e6", "text": "is a library yet is is instead of release tag. Please consider vendoring by tag whenever possible. Thanks.\nWe vendored it that way because the commit that fixed a bug (which we needed to be fixed and vendored back in) was This was merged on June 13. The release 1.1.4 () was released on July 1. If we want to update it to 1.1.4, I believe it should be fine. Between the commit we have vendored right now and the latest release, there are only three commits: adds tests merges (?) the case-sensitive fix - I'm not really sure what this commit is doing. fixes renaming when naming strategy is set (looks fine). Also, there are also no licensing changes. opinions?\n/sig api-machinery\n+1 to what said, it was a fire drill and 1.11.0 release was in trouble. Though in hind sight, we should have opened a issue to track that. something better to do next time. cc\nI'm indifferent to updating this. I'm okay with moving up if it doesn't break anything, or I'm fine with leaving things as is. We don't require deps to match semver. We can version out any commit in a deps tree, as we rely on our vendored copy.\nIt is always a good idea to match semver and it should be a default policy. Even if it doesn't matter to you, it should, because it is a best practice. Moreover downstream it matters much more as dependencies may be un-vendored in favour of tested re-usable packages.\n/cc\nIssues 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\nSomeone please take care of this or bot will eventually close this valid issue without action...\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_66422", "tokennum": 501}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6aeb5a46e6fd0c4ce57e9cb19104e750622c6cec989528baa4dfa5e12e248cac", "query": "[[projects]] name = \"github.com/modern-go/reflect2\" packages = [\".\"] <del> revision = \"1df9eeb2bb81f327b96228865c5687bc2194af3f\" version = \"1.0.0\" </del> <ins> revision = \"4b7aa43c6742a2c18fdef89dd197aaae7dac7ccd\" version = \"1.0.1\" </ins> [solve-meta] analyzer-name = \"dep\" analyzer-version = 1 <del> inputs-digest = \"56a0b9e9e61d2bc8af5e1b68537401b7f4d60805eda3d107058f3171aa5cf793\" </del> <ins> inputs-digest = \"ea54a775e5a354cb015502d2e7aa4b74230fc77e894f34a838b268c25ec8eeb8\" </ins> solver-name = \"gps-cdcl\" solver-version = 1", "positive_passages": [{"docid": "doc-en-kubernetes-3d634ec524d1253e3e5f3f0b99b6d74925e6b15b79d6d989e49b255bf837eee0", "text": "/lifecycle rotten\n/lifecycle rotten\n/remove-lifecycle rotten PR open (thanks,\noops! sorry, I meant to remove it. thanks!\nThanks.\nplease do feel free to open issues/prs of this sort early in the release cycle, so we can work through things needed well before the milestones/freeze etc. we are getting some heat about updating dependencies and we kind of settled on some guidelines here: if you think that needs updating, we could definitely debate that as well :) (on a PR against that doc)\nit have nothing to do with release cycle or justification for upgrade if/when dependency has been vendored incorrectly. It is basically a vendoring bug. No debate is necessary although that kind of issues usually meet some resistance and even hostility here... Bugs are filed when they are discovered, regardless of release cycle. It would be wrong to sit on the bug without reporting it in order to synchronise with release cycle.", "commid": "kubernetes_issue_66422", "tokennum": 200}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6b201f879ce2071681a01405d4321f20b4ccdea9b0e72fa02dfb668619cff44f", "query": "}, { \"ImportPath\": \"github.com/json-iterator/go\", <del> \"Comment\": \"1.1.3-22-gf2b4162afba355\", \"Rev\": \"f2b4162afba35581b6d4a50d3b8f34e33c144682\" </del> <ins> \"Comment\": \"1.1.4\", \"Rev\": \"ab8a2e0c74be9d3be70b3184d9acc634935ded82\" </ins> }, { \"ImportPath\": \"github.com/jteeuwen/go-bindata\",", "positive_passages": [{"docid": "doc-en-kubernetes-0d085a3ee589d9a38ade8c650d9534110265a809ec41b82f41ce81cebea870e6", "text": "is a library yet is is instead of release tag. Please consider vendoring by tag whenever possible. Thanks.\nWe vendored it that way because the commit that fixed a bug (which we needed to be fixed and vendored back in) was This was merged on June 13. The release 1.1.4 () was released on July 1. If we want to update it to 1.1.4, I believe it should be fine. Between the commit we have vendored right now and the latest release, there are only three commits: adds tests merges (?) the case-sensitive fix - I'm not really sure what this commit is doing. fixes renaming when naming strategy is set (looks fine). Also, there are also no licensing changes. opinions?\n/sig api-machinery\n+1 to what said, it was a fire drill and 1.11.0 release was in trouble. Though in hind sight, we should have opened a issue to track that. something better to do next time. cc\nI'm indifferent to updating this. I'm okay with moving up if it doesn't break anything, or I'm fine with leaving things as is. We don't require deps to match semver. We can version out any commit in a deps tree, as we rely on our vendored copy.\nIt is always a good idea to match semver and it should be a default policy. Even if it doesn't matter to you, it should, because it is a best practice. Moreover downstream it matters much more as dependencies may be un-vendored in favour of tested re-usable packages.\n/cc\nIssues 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\nSomeone please take care of this or bot will eventually close this valid issue without action...\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_66422", "tokennum": 501}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6b201f879ce2071681a01405d4321f20b4ccdea9b0e72fa02dfb668619cff44f", "query": "}, { \"ImportPath\": \"github.com/json-iterator/go\", <del> \"Comment\": \"1.1.3-22-gf2b4162afba355\", \"Rev\": \"f2b4162afba35581b6d4a50d3b8f34e33c144682\" </del> <ins> \"Comment\": \"1.1.4\", \"Rev\": \"ab8a2e0c74be9d3be70b3184d9acc634935ded82\" </ins> }, { \"ImportPath\": \"github.com/jteeuwen/go-bindata\",", "positive_passages": [{"docid": "doc-en-kubernetes-3d634ec524d1253e3e5f3f0b99b6d74925e6b15b79d6d989e49b255bf837eee0", "text": "/lifecycle rotten\n/lifecycle rotten\n/remove-lifecycle rotten PR open (thanks,\noops! sorry, I meant to remove it. thanks!\nThanks.\nplease do feel free to open issues/prs of this sort early in the release cycle, so we can work through things needed well before the milestones/freeze etc. we are getting some heat about updating dependencies and we kind of settled on some guidelines here: if you think that needs updating, we could definitely debate that as well :) (on a PR against that doc)\nit have nothing to do with release cycle or justification for upgrade if/when dependency has been vendored incorrectly. It is basically a vendoring bug. No debate is necessary although that kind of issues usually meet some resistance and even hostility here... Bugs are filed when they are discovered, regardless of release cycle. It would be wrong to sit on the bug without reporting it in order to synchronise with release cycle.", "commid": "kubernetes_issue_66422", "tokennum": 200}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6b3b65bcd5ed85448329719053d5df4e6c39d10d53d658d44c43ebb9bf71dea0", "query": "q99 := hist.Quantile(0.95) avg := hist.Average() <del> // clear the metrics so that next test always starts with empty prometheus // metrics (since the metrics are shared among all tests run inside the same binary) hist.Clear() </del> msFactor := float64(time.Second) / float64(time.Millisecond) // Copy labels and add \"Metric\" label for this metric.", "positive_passages": [{"docid": "doc-en-kubernetes-43f40e78041c5b4f7b71fe448bfb25306103aa8e8278b5a81de2f92cd8b688c4", "text": "In the new scheduler performance testing framework, (bool) is provided to benchmark performance of pods created in an \"operator\": (L11 below) However, the initialized Pods created in L5~L7 seem to be also benchmarked, although it doesn't specify . (please see the reproduce steps below). I think it's b/c once scheduler starts, the associated Prometheus artifacts are also up, and it's a single in-memory datastore. So no matter we start to collect the metric in which step, the prometheus data is already up-to-date. In the above workload config, the final data have benchmarked 1500 pods instead of 1000 pods. I guess it won't work either if running in the pod initialization step or not. Unless we manage a breakpoint at the end of each step, and calculate delta histogram for the step that specifies . Pods created in step without are not benchmarked. Apply the following diff: And then run: You will get an output sth. like: /sig scheduling\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nCould you please help confirm if it's an issue?\ncc\nUnfortunately, does not apply for metrics gathered from . As you mentioned. The default gatherer collects all metrics produced by the scheduler. It's the scheduler itself who knows pod specs and would have to decide which pods will get ignored when updating metrics. The question is if computing metrics for a subset of pods processed by the scheduler is a valid use case.\nThis is probably what we want. Is something like that possible ?\nI think being able to absolutely ignore certain pods for metrics is an overkill.\nThe use case is to ignore the pods created in steps that don't specify , so as to collect the Pod metrics create at particular step(s) (). Otherwise, the semantics of option is quite misleading. Nope, that's not the intention. We don't need to target certain pods, like using label selector or whatever. Just as I mentioned, measure pods created at particular steps.", "commid": "kubernetes_issue_99218", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6b3b65bcd5ed85448329719053d5df4e6c39d10d53d658d44c43ebb9bf71dea0", "query": "q99 := hist.Quantile(0.95) avg := hist.Average() <del> // clear the metrics so that next test always starts with empty prometheus // metrics (since the metrics are shared among all tests run inside the same binary) hist.Clear() </del> msFactor := float64(time.Second) / float64(time.Millisecond) // Copy labels and add \"Metric\" label for this metric.", "positive_passages": [{"docid": "doc-en-kubernetes-a8b513dba6e655a29138693e1746ea6f16e628420cb4b4aca138e84f0ed453fc", "text": "I would do something like the following: if a step has collectMetrics:false, we wait for them to finish scheduling, and then we take a snapshot of the histogram. Then for the next step that has collectMetrics:true, we take the diff with the latest snapshot to report the results. This might not be perfect, as we don't control if the metrics have finished syncing when we take the snapshot. But I think that's fine. Would doing this be possible? Now, if we have steps that run in parallel, one with collectMetrics:false and another with collectMetrics:true, then this doesn't work. Note that I don't know the details of how the gatherer works.\nThat adheres to what I have in my mind - we can only manage this on client side. I think it's fine. As we are already fetching the \"snapshot\" when pods get scheduled when equals true. True. An alternative is to design the case to be like: the step with to employ Pods that are all unschedulable, and then specify a custom metric \"schedulere2eschedulingdurationseconds[result=\"unschedulable\"]\" to target a particular histogram instead of all histograms (default option) inside a histogramVec. Note this can only be possible when and some subsequent changes get in place.\nWe might just call Histogram.Clear() method which will clear what has been collected so far at the end of phase: Assuming individual phases have no pods in common and each phase can clear metrics without affecting other phases. Though, as said, it will work only for serial case.\nWDYT\nI'm afraid doesn't work. That was my initial thought as well, but no luck. I guess it's b/c, theoretically, we cannot reset a metric on the server side - Promoetheus' model doesn't support this. But let me know if I miss anything.\nThe performance tests assume all the metrics all gathered and accessed in the same binary. As long as that's the case, works.", "commid": "kubernetes_issue_99218", "tokennum": 457}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6b3b65bcd5ed85448329719053d5df4e6c39d10d53d658d44c43ebb9bf71dea0", "query": "q99 := hist.Quantile(0.95) avg := hist.Average() <del> // clear the metrics so that next test always starts with empty prometheus // metrics (since the metrics are shared among all tests run inside the same binary) hist.Clear() </del> msFactor := float64(time.Second) / float64(time.Millisecond) // Copy labels and add \"Metric\" label for this metric.", "positive_passages": [{"docid": "doc-en-kubernetes-c977cd9286b4a197ec98b02fe65342de07359c1835b69599916b95554e8a5e53", "text": "We already call in the code:\nThat was my understanding as well, but no luck :( Here is a diff to call in case when \"concreteOp.CollectMetrics\" is false: <details<summaryDiff:</summary<p</p</detailsAnd below is the output - it's still 1500 (500 init pods plus 1000 measured pods) instead of 1000 being benchmarked: <details<summaryOutput:</summary<p</p</details\nAlso, if you run the tests and together, the result proves doesn't work as expected:\nBut I do find a way to fix this: .", "commid": "kubernetes_issue_99218", "tokennum": 136}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6b553727a8f0087f5f43f298738a4189a347ba7cac7780c4f05e1d72a6c3dab4", "query": "// we didn't validate against any provider, reject the pod and give the errors for each attempt klog.V(4).Infof(\"unable to validate pod %s (generate: %s) in namespace %s against any pod security policy: %v\", pod.Name, pod.GenerateName, a.GetNamespace(), validationErrs) <del> return admission.NewForbidden(a, fmt.Errorf(\"unable to validate against any pod security policy: %v\", validationErrs)) </del> <ins> return admission.NewForbidden(a, fmt.Errorf(\"PodSecurityPolicy: unable to validate pod: %v\", validationErrs)) </ins> } func shouldIgnore(a admission.Attributes) (bool, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-d654f914f6cdd0bd3bce5db6eb3c4ebef631bd8d2558ac9d591cab12ba724061", "text": "What happened: e2e tests detect whether PSP is enabled based on presence of PSP API objects. An addon that proactively includes a PSP in a manifest can trigger that detection and enable PSP-specific e2e tests that should not be run. What you expected to happen: In addition to detecting presence of PSP objects, consider dry-run creating a pod and verifying the annotation indicating the selected PSP policy is , indicating the admission plugin is active. /sig auth /assign", "commid": "kubernetes_issue_91463", "tokennum": 109}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6b773e98b45cc0f4fdf3da5a1de57708a0908b3258d19f71214ee287f1370d94", "query": "return c.callCustom(sv, dv, fv, scope) } <ins> return c.defaultConvert(sv, dv, scope) } // defaultConvert recursively copies sv into dv. no conversion function is called // for the current stack frame (but conversion functions may be called for nested objects) func (c *Converter) defaultConvert(sv, dv reflect.Value, scope *scope) error { dt, st := dv.Type(), sv.Type() </ins> if !scope.flags.IsSet(AllowDifferentFieldTypeNames) && c.NameFunc(dt) != c.NameFunc(st) { return scope.error(\"type names don't match (%v, %v)\", c.NameFunc(st), c.NameFunc(dt)) }", "positive_passages": [{"docid": "doc-en-kubernetes-518f837785f17a5fd9706a6c0a0614adac703d65f6bb6045d79a025795dcb97b", "text": "Files storing latest versions for minors are not updated since infix was to the version string. Example Similar issues can be found in 1.25 and 1.24 builds (last 1.23 build infix so it has not happened there yet): I expect the files to be overwritten with newer version of the build. Manually run build job for one of the minors. No response Not related. Not related. No response No response No response No response\nI believe this may be also responsible for breaking kubemark tests: since they fail due to version mismatch\n/sig release\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority high 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\nThanks for raising the issue! /cc who is working on before\nI assume this will be fixed automatically with the next patches, because then we would compare with . Anyway, I think we should fix that intermediately by manually updating the version markers to match their correct version. I did that now for the bucket\nWe had to update the versions markers again, because those were pointing to two commits earlier and didn't include the Go updates. The latest version markers are: v1.24.12-35+ v1.25.8-37+ v1.26.3-41+\nlatest-1.27 has been affected by this as well. I updated it manually to v1.27.0-9+. See this thread for more details:\n/triage accepted\nThis should be fixed now, closing it. Feel free to reopen if we missed anything.\nThis issue is still present, see this Slack thread for more details: /reopen\nReopened this issue. <detailsIn response to : This issue is still present, see this Slack thread for more details: /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nWe have a similar situation with latest-1.28 which is currently pointing to: . This is one commit before the release commit: ! It's mostly like that the release step didn't update version markers, we should look into this.", "commid": "kubernetes_issue_117115", "tokennum": 486}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6b773e98b45cc0f4fdf3da5a1de57708a0908b3258d19f71214ee287f1370d94", "query": "return c.callCustom(sv, dv, fv, scope) } <ins> return c.defaultConvert(sv, dv, scope) } // defaultConvert recursively copies sv into dv. no conversion function is called // for the current stack frame (but conversion functions may be called for nested objects) func (c *Converter) defaultConvert(sv, dv reflect.Value, scope *scope) error { dt, st := dv.Type(), sv.Type() </ins> if !scope.flags.IsSet(AllowDifferentFieldTypeNames) && c.NameFunc(dt) != c.NameFunc(st) { return scope.error(\"type names don't match (%v, %v)\", c.NameFunc(st), c.NameFunc(dt)) }", "positive_passages": [{"docid": "doc-en-kubernetes-5a00e106d863b6b2d6ffe122805a64f76a2709c3a46b9a75024b175401623671", "text": "As of now, I'm going to manually update this version marker to unblock 1.28.1 patch release. I'll also take a look into this. /assign\nThe PR that fixed this issue got reverted so this is still relevant: /reopen\nReopened this issue. <detailsIn response to : The PR that fixed this issue got reverted so this is still relevant: /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nWe're running into this issue again with stable-1.29 marker. It's currently pointing to which is It should instead point to I'm going to manually change it following the same procedure as the last time. Version marker updated to\nThis issue is labeled with but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release. You can: Confirm that this issue is still relevant with (org members only) Deprioritize it with or Close this issue with For more details on the triage process, see /remove-triage accepted\n/triage accepted\nSame issue for 1.30, where I had to update the version marker manually again.", "commid": "kubernetes_issue_117115", "tokennum": 278}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6b84738a94a23af0f56a7c8cf31220024d7d74d7993be985041a14472692bb8b", "query": "<ins> /* Copyright 2016 The Kubernetes Authors All rights reserved. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package core import ( \"k8s.io/kubernetes/pkg/api\" \"k8s.io/kubernetes/pkg/fields\" \"k8s.io/kubernetes/pkg/labels\" \"k8s.io/kubernetes/pkg/runtime\" ) func addDefaultingFuncs(scheme *runtime.Scheme) { scheme.AddDefaultingFuncs( func(obj *api.ListOptions) { if obj.LabelSelector == nil { obj.LabelSelector = labels.Everything() } if obj.FieldSelector == nil { obj.FieldSelector = fields.Everything() } }, ) } func addConversionFuncs(scheme *runtime.Scheme) { scheme.AddConversionFuncs( api.Convert_unversioned_TypeMeta_To_unversioned_TypeMeta, api.Convert_unversioned_ListMeta_To_unversioned_ListMeta, api.Convert_intstr_IntOrString_To_intstr_IntOrString, api.Convert_unversioned_Time_To_unversioned_Time, api.Convert_Slice_string_To_unversioned_Time, api.Convert_string_To_labels_Selector, api.Convert_string_To_fields_Selector, api.Convert_Pointer_bool_To_bool, api.Convert_bool_To_Pointer_bool, api.Convert_Pointer_string_To_string, api.Convert_string_To_Pointer_string, api.Convert_labels_Selector_To_string, api.Convert_fields_Selector_To_string, api.Convert_resource_Quantity_To_resource_Quantity, ) } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-5056a2515a29befdf589a74f13db031ed4142bbabfa8d2c37cafac2de4fccaea", "text": "I started the federation-apiserver and went to and got the following output: Expected: I should have got an empty v1.ServiceList Any idea on what we are doing wrong? Have you guys seen this error?\nI think your deep copiers or conversion functions are not getting registered properly. If you look at my change in , some places are inappropriately registering with api.Scheme instead of the passed in scheme. Maybe you have that problem or a similar one, since I think you guys copied some code. , Nikhil Jindal wrote:\nDeep copy generation was slightly broken as well - you may want to double check that they are registered. On May 23, 2016, at 5:50 PM, Daniel Smith wrote: I think your deep copiers or conversion functions are not getting registered properly. If you look at my change in , some places are inappropriately registering with api.Scheme instead of the passed in scheme. Maybe you have that problem or a similar one, since I think you guys copied some code. , Nikhil Jindal wrote: \u2014 You are receiving this because you are on a team that was mentioned. Reply to this email directly or view it on GitHub\nI got the same error with latest branch, as I was swamping on service controller, so I use a previous version and worked around it.\ndeep copies were indeed missing, but adding them hasnt fixed the issue. Will debug more. is my PR to add the deep copies cc Please feel free to file issues for any such problem you face. We need to fix all these issues. Its good if we know about them early. Thanks!\nfixes this", "commid": "kubernetes_issue_26111", "tokennum": 335}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6b84edf8e5821ada92698fb97ea9fb1ec4b5fe365b5334c0710c535f793600ab", "query": "return fmt.Errorf(\"failed to watch %s, err: %v\", path, err) } case mode&os.ModeSocket != 0: <ins> w.wg.Add(1) </ins> go func() { <ins> defer w.wg.Done() </ins> w.fsWatcher.Events <- fsnotify.Event{ Name: path, Op:   fsnotify.Create,", "positive_passages": [{"docid": "doc-en-kubernetes-6f8ca0211eec05ccf55bb519cf8df0569345414eb205c19a4215b8fda8e40904", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: https://k8s- Which test(s) are failing: should unmount if pod is force deleted while kubelet is down [Disruptive][Slow] Since when has it been failing: 11/07/18 15:02 Testgrid link: https://k8s- Reason for failure: The test case stops and starts kubelet, and it seems like kubelet is unable to start again Anything else we need to know: <!-- DO NOT EDIT BELOW THIS LINE --/kind failing-test\ncc\nThanks for opening this Looking at , looks like could be the cause? /assign can you please look into this as priority. This is failing critical release blocking tests. /cc /sig cli /priority critical-urgent /milestone v1.13\nIt looks like kubelet keeps restarting. The error right before restarting is:\n/assign\nThis bug could have been exposed by the newly tests in\nHmm, so I see two errors: Which is a Fatal error and would prevent Kubelet from starting anyways. In which case this error is handled correctly by the pluginwatcher, but I'm not sure preventing Kubelet from starting is the desired behavior. Should we log this error and skip it? There also seem to be a cleanup issue here on that file is this expected? This one is clearly a bug and not really handled correctly. It's due to the fact that we encounter an error at start, cleanup but don't wait for the gorountines to finish before cleaning up. I can send in a fix pretty easily for the second issue, basically add a waitgroup in the . For the first error, what do we think is the expected behavior?\nThis was mentioned in as well. /cc\nIs this related to the issue where plugin watcher is recursively scanning for sockets?\nAlso, it should be noted that the path it's erroring on is not a socket type.\nThat's a bit different, as it is intended to scan recursively. Also note that the error here is produced by . What should be our behavior in such a case? Ignore that error?\nI'm not sure if we want to be recursively scanning. The volume directories are mount points, which means there could be lots of files/directories existing in those volumes.", "commid": "kubernetes_issue_70810", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6b84edf8e5821ada92698fb97ea9fb1ec4b5fe365b5334c0710c535f793600ab", "query": "return fmt.Errorf(\"failed to watch %s, err: %v\", path, err) } case mode&os.ModeSocket != 0: <ins> w.wg.Add(1) </ins> go func() { <ins> defer w.wg.Done() </ins> w.fsWatcher.Events <- fsnotify.Event{ Name: path, Op:   fsnotify.Create,", "positive_passages": [{"docid": "doc-en-kubernetes-5fd14dcabf74b34a3f64d7f7feeb636f4d13fa903d9084a91cc242778a1c3d1e", "text": "maybe we can put a limit on depth of plugin directory for on the same PR:\nIdeally the directory that the plugin sockets are dropped in should be different from the directory where mounts happens. Currently the plugin socket directory is: ) The mounts directory is (so far so good). Problem is the \"global mount\" directory is also :( So options are: recursively scanning like suggested, and say plugins will can only be directly under This will break existing plugins, for example, the GCP plugin is at (see ). recursively scanning but change the plugin socket directory to ? This will also break existing plugins, like the GCP one pointed out above. the plugin dir the same, and leave recursion in, but put a limit on depth of plugin directory as suggested by This is ugly but may be the cleanest solution.\nThis conversation is completely different from the bug surfaced by this issue. Let's move that to the corresponding issue: I have a fix ready to go out for the panic, we should figure out what behavior we expect Kubelet to have when encountering this error from filepath.Walk: Should we ignore it?\nIgnoring the error (with a warning maybe) instead of failing all of kubelet seems reasonable to me. If the plugin did not setup their registration socket correctly, then the end result should be that the plugin fails to register, but all other plugins should continue to work correctly.\nthe latest runs of this job no longer timesout - Instead I am seeing a new CSI related failure Is this expected. Do we want to track that failure in this bug now or do we have a separate issue?\nthe latest test logs indicate some test-infra issue:\nthe same shows up as a timeout on that particular test. Lets wait for the next run. but somehow the timeout seems to have gone. Are we still planning to merge and associated with this issue?\nshould be merged as it fixes a bug. can you help with approval? Thanks!\nare you missing the right PR# in the comment above?\nthis is the correct PR -\n/reopen Keeping it open until we can see the job pass a couple of rounds\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository.", "commid": "kubernetes_issue_70810", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6b84edf8e5821ada92698fb97ea9fb1ec4b5fe365b5334c0710c535f793600ab", "query": "return fmt.Errorf(\"failed to watch %s, err: %v\", path, err) } case mode&os.ModeSocket != 0: <ins> w.wg.Add(1) </ins> go func() { <ins> defer w.wg.Done() </ins> w.fsWatcher.Events <- fsnotify.Event{ Name: path, Op:   fsnotify.Create,", "positive_passages": [{"docid": "doc-en-kubernetes-7a1e75b2dd238a9264dd7ee20adbbea7f5a6949137fb440b1e66e3d97a7ebee9", "text": "</details\nI see just one CSI test timing out in serial job Is that something the fixes here attempted to resolve? if not I can open a new issue if it persists and close this one out. Thanks.\nThe test mentioned in my comment above was a flake.. closing this issue now. will open a new issue for the flake\nI'm getting the following related error on a busy Node: In the above case it's a full filesystem, but I imagine the same error would pop up with a RO filesystem as well. Looking at the patch, I'd expect kubelet would still be failing to start when it tries to watch it. (above was from a v1.12.3 cluster) , what do you reckon?\nplugin watcher fixes for 1.12 are expected to be released with 1.12.5:\n, I understand that I'm missing that patch. The patch code, however, would not make a difference in this case, if I read it correctly. It would not prevent the recursive dive into mounted volumes, as the errors happening at the deeper levels of that dive.\nThe patch blacklists the plugin watcher from searching the directory\nOK, I was looking at the wrong patch after all (). Thanks for the clarifications.", "commid": "kubernetes_issue_70810", "tokennum": 274}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6baa6a68f3a245554be6603a2e77c5e10449d46c31439e19b6dbd008023de733", "query": "Name:      \"total_preemption_attempts\", Help:      \"Total preemption attempts in the cluster till now\", }) <ins> equivalenceCacheLookups = prometheus.NewCounterVec( prometheus.CounterOpts{ Subsystem: SchedulerSubsystem, Name:      \"equiv_cache_lookups_total\", Help:      \"Total number of equivalence cache lookups, by whether or not a cache entry was found\", }, []string{\"result\"}) EquivalenceCacheHits   = equivalenceCacheLookups.With(prometheus.Labels{\"result\": \"hit\"}) EquivalenceCacheMisses = equivalenceCacheLookups.With(prometheus.Labels{\"result\": \"miss\"}) EquivalenceCacheWrites = prometheus.NewCounterVec( prometheus.CounterOpts{ Subsystem: SchedulerSubsystem, Name:      \"equiv_cache_writes\", Help:      \"Total number of equivalence cache writes, by result\", }, []string{\"result\"}) </ins> metricsList = []prometheus.Collector{ SchedulingLatency, E2eSchedulingLatency,", "positive_passages": [{"docid": "doc-en-kubernetes-aa59e6a5adfc1b233e34e0c1fe9e3a0ec7f2fe6a4636f877a41f4c9aef45f71d", "text": "/kind feature The equivalence cache feature is planned to move to beta in 1.11, and it would be useful to have some metrics attached to it. The equivalence cache should improve scheduling throughput, so we want to be able to correlate e.g. throughput with eCache hit rate. /sig scheduling /sig instrumentation\n/assign misterikkit\nIssues 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\n/remove-lifecycle stale", "commid": "kubernetes_issue_63259", "tokennum": 154}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6bf6b78f6e63368a7f16114587d7c81b66cbd0ef30b977c6f48473b0894682eb", "query": "} func getCPUStat(f *framework.Framework, host string) (usage, uptime float64) { <del> cpuCmd := \"cat /sys/fs/cgroup/cpu/system.slice/node-problem-detector.service/cpuacct.usage && cat /proc/uptime | awk '{print $1}'\" </del> <ins> var cpuCmd string if isHostRunningCgroupV2(f, host) { cpuCmd = \" cat /sys/fs/cgroup/cpu.stat | grep 'usage_usec' | sed 's/[^0-9]*//g' && cat /proc/uptime | awk '{print $1}'\" } else { cpuCmd = \"cat /sys/fs/cgroup/cpu/system.slice/node-problem-detector.service/cpuacct.usage && cat /proc/uptime | awk '{print $1}'\" } </ins> result, err := e2essh.SSH(cpuCmd, host, framework.TestContext.Provider) framework.ExpectNoError(err) framework.ExpectEqual(result.Code, 0)", "positive_passages": [{"docid": "doc-en-kubernetes-0c07e91eb7d66ee92c3b6d05f523cece58039dffcf1123c44ba752c30922deab", "text": "N/A [sig-node] NodeProblemDetector: N/A https://prow- Not cgroupv2 compatible when access cpu and memory data\n/sig node\nHi, can i work on this ?\nSure. Thanks\n/assign\n/triage accepted\n/priority important-soon\n/cc\nare you still working on this? Were you able to setup environment to repro the test failure? Let us know if you need any help. Thanks!\nSorry for the delay, I followed the wrong guide and ended up getting stuck. But now I have managed to set it up. Please give me few more days to work on it.\nThanks Feel free to reach out here or on slack if you need any help, thanks for working on this!\n/retitle Make nodeproblemdetector test cgroupv2 compatible\nFailing job:\nTestgrid:", "commid": "kubernetes_issue_105178", "tokennum": 180}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6c114e216e0d52e6390c6dbf1ca69ebe20e240a73f583d249c7d066c197408cc", "query": "// we expect following values for: Major -> digit, Minor -> numeric followed by an optional '+',  GitCommit -> alphanumeric requiredItems := []string{\"Client Version: \", \"Server Version: \"} for _, item := range requiredItems { <del> if matched, _ := regexp.MatchString(item+`vd.d+.[dw-.+]+`, versionString); !matched { </del> <ins> // prior to 1.28 we printed long version information oldMatched, _ := regexp.MatchString(item+`version.Info{Major:\"d\", Minor:\"d++?\", GitVersion:\"vd.d+.[dw-.+]+\", GitCommit:\"[0-9a-f]+\"`, versionString) // 1.28+ prints short information newMatched, _ := regexp.MatchString(item+`vd.d+.[dw-.+]+`, versionString) // due to backwards compatibility we need to match both until 1.30 most likely if !oldMatched && !newMatched { </ins> framework.Failf(\"Item %s value is not valid in %sn\", item, versionString) } }", "positive_passages": [{"docid": "doc-en-kubernetes-b66f5b7782acce0f091a6b4a6784e7025204ffa447d61b006db9acac747a220f", "text": "master-informing: capz-windows-master ! 07-10 17:46 IST No response /sig cli cc\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/kind failing-test\nLooking at the failure and tracing the recent code changes, the test was recently modified for the regex pattern match as part of this PR which comes with deprecation of the golang-based short version information in favor of making the --short the new default. But the output of kubectl version is still reflecting the older long format which is causing this test to fail.\n/assign", "commid": "kubernetes_issue_119230", "tokennum": 197}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6c1704e916136972e2875d04f986ae4c9302dadc8e1b376ee75954dc624f862f", "query": "<ins> /* Copyright 2017 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package types import ( \"testing\" \"github.com/stretchr/testify/assert\" ) func TestGetContainerName(t *testing.T) { var cases = []struct { labels        map[string]string containerName string }{ { labels: map[string]string{ \"io.kubernetes.container.name\": \"c1\", }, containerName: \"c1\", }, { labels: map[string]string{ \"io.kubernetes.container.name\": \"c2\", }, containerName: \"c2\", }, } for _, data := range cases { containerName := GetContainerName(data.labels) assert.Equal(t, data.containerName, containerName) } } func TestGetPodName(t *testing.T) { var cases = []struct { labels  map[string]string podName string }{ { labels: map[string]string{ \"io.kubernetes.pod.name\": \"p1\", }, podName: \"p1\", }, { labels: map[string]string{ \"io.kubernetes.pod.name\": \"p2\", }, podName: \"p2\", }, } for _, data := range cases { podName := GetPodName(data.labels) assert.Equal(t, data.podName, podName) } } func TestGetPodUID(t *testing.T) { var cases = []struct { labels map[string]string podUID string }{ { labels: map[string]string{ \"io.kubernetes.pod.uid\": \"uid1\", }, podUID: \"uid1\", }, { labels: map[string]string{ \"io.kubernetes.pod.uid\": \"uid2\", }, podUID: \"uid2\", }, } for _, data := range cases { podUID := GetPodUID(data.labels) assert.Equal(t, data.podUID, podUID) } } func TestGetPodNamespace(t *testing.T) { var cases = []struct { labels       map[string]string podNamespace string }{ { labels: map[string]string{ \"io.kubernetes.pod.namespace\": \"ns1\", }, podNamespace: \"ns1\", }, { labels: map[string]string{ \"io.kubernetes.pod.namespace\": \"ns2\", }, podNamespace: \"ns2\", }, } for _, data := range cases { podNamespace := GetPodNamespace(data.labels) assert.Equal(t, data.podNamespace, podNamespace) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-672dc953e52a460d81d453213d4e2e634446d10e93c8bdf3e045ab9c2943abdc", "text": "This is a sub issue for\ncc can you please assign this to me? Thanks.\n, please create PR directly and cc to Tim for review.\n/sig node\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close", "commid": "kubernetes_issue_40780", "tokennum": 237}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6c1936c6be36f5056fb340df40081f49f85643377a2d28e62afb26f96f744be0", "query": "\"description\": \"EndpointPort represents a Port used by an EndpointSlice\", \"properties\": { \"name\": { <del> \"description\": \"The name of this port. All ports in an EndpointSlice must have a unique name. If the EndpointSlice is dervied from a Kubernetes service, this corresponds to the Service.ports[].name. Name must either be an empty string or pass IANA_SVC_NAME validation: * must be no more than 15 characters long * may contain only [-a-z0-9] * must contain at least one letter [a-z] * it must not start or end with a hyphen, nor contain adjacent hyphens Default is empty string.\", </del> <ins> \"description\": \"The name of this port. All ports in an EndpointSlice must have a unique name. If the EndpointSlice is dervied from a Kubernetes service, this corresponds to the Service.ports[].name. Name must either be an empty string or pass DNS_LABEL validation: * must be no more than 63 characters long. * must consist of lower case alphanumeric characters or '-'. * must start and end with an alphanumeric character. Default is empty string.\", </ins> \"type\": \"string\" }, \"port\": {", "positive_passages": [{"docid": "doc-en-kubernetes-b73bb51cef5016ee2dcd80aae4248808fec811a4dad3a3b7abbba7673a446c48", "text": "What happened: No endpoints created in the EndpointSlice for my service due to the port on the service being too long. Logs show: EndpointSlice created has no endpoint: What you expected to happen: Service that works with Endpoints should work with EndpointSlice. If this is intentional, it should be clearly documented How to reproduce it (as minimally and precisely as possible): Create a service with a long port name Environment: Kubernetes version (use ): 1.16 Cloud provider or hardware configuration: kind\n/sig networking\nThe label(s) cannot be applied. These labels are supported: <detailsIn response to : /sig networking 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\n/sig network These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by vllry. \u200d\nFor a rough measure of impact, Istio had 5 ports that were over this limit (and many more that were right at 15 characters), so I suspect it may not be terribly rare.\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nThis needs to be resolved before endpointslices graduate from alpha\n/assign\n/remove-triage unresolved", "commid": "kubernetes_issue_84388", "tokennum": 292}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6c4e91a988d6c2cf43075e523b28868790ea0987e2c64d256bbdaa1824540e42", "query": "TEMP_DIR:=$(shell mktemp -d) ifeq ($(ARCH),amd64) <del> BASEIMAGE?=k8s.gcr.io/build-image/debian-base:buster-v1.3.0 </del> <ins> BASEIMAGE?=k8s.gcr.io/build-image/debian-base:buster-v1.4.0 </ins> endif ifeq ($(ARCH),arm) <del> BASEIMAGE?=k8s.gcr.io/build-image/debian-base-arm:buster-v1.3.0 </del> <ins> BASEIMAGE?=k8s.gcr.io/build-image/debian-base-arm:buster-v1.4.0 </ins> endif ifeq ($(ARCH),arm64) <del> BASEIMAGE?=k8s.gcr.io/build-image/debian-base-arm64:buster-v1.3.0 </del> <ins> BASEIMAGE?=k8s.gcr.io/build-image/debian-base-arm64:buster-v1.4.0 </ins> endif ifeq ($(ARCH),ppc64le) <del> BASEIMAGE?=k8s.gcr.io/build-image/debian-base-ppc64le:buster-v1.3.0 </del> <ins> BASEIMAGE?=k8s.gcr.io/build-image/debian-base-ppc64le:buster-v1.4.0 </ins> endif ifeq ($(ARCH),s390x) <del> BASEIMAGE?=k8s.gcr.io/build-image/debian-base-s390x:buster-v1.3.0 </del> <ins> BASEIMAGE?=k8s.gcr.io/build-image/debian-base-s390x:buster-v1.4.0 </ins> endif RUNNERIMAGE?=gcr.io/distroless/static:latest", "positive_passages": [{"docid": "doc-en-kubernetes-ee0826757468ea334f95c77509b257c3d392b6713b4311ba7afa125d642dcec9", "text": "The based container images for are shipped with the wrong architecture within the manifest if not amd64: Refers to We updated the images a few minutes ago to buster-v1.3.0, which are now ready to be used as base for the multi-architecture images. If the images contain the right architectures, then it may magically happen that the kube-proxy images are fixed, too. This is because we already use the build syntax for it: /cc\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig release", "commid": "kubernetes_issue_98229", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6c57620a346dc9774cae37860441bc5390d4a14725ba0fc39487c770b3b420f1", "query": "if podConfig.NS == \"\" { return nil, fmt.Errorf(\"Cannot create pod with empty namespace\") } <del> if len(podConfig.Command) == 0 && !NodeOSDistroIs(\"windows\") { </del> <ins> if len(podConfig.Command) == 0 { </ins> podConfig.Command = \"trap exit TERM; while true; do sleep 1; done\" }", "positive_passages": [{"docid": "doc-en-kubernetes-2598e11fb35075705c3572da278160109a38df575ea6022e29df9bb46aaee489", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --ci-kubernetes-e2e-gci-gce-serial (gce-cos-master-serial) Four tests: Kubernetes e2e suite.[sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly] Kubernetes e2e suite.[sig-storage] In-tree Volumes [Driver: hostPath] [Testpattern: Inline-volume (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly] Kubernetes e2e suite.[sig-storage] In-tree Volumes [Driver: hostPathSymlink] [Testpattern: Inline-volume (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly] Kubernetes e2e suite.[sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should unmount if pod is force deleted while kubelet is down [Disruptive][Slow][LinuxOnly] is failing since June 29th 2021 (but the first failure was different than more recent ones). Commit , infra commit , . Other three tests are failing since July 9th 2021. Commit , infra commit , . Testgrid: https://k8s- Prow history: For CSI Volumes: For In-tree Volumes: There is another open issues for failing tests in this job: Failures reported there are about missing metrics, and were occuring before unmounting problems. So I opened a new issue, even though it's the same SIG. These tests don't look related to me, but I don't have enough context, maybe they somehow are. /sig storage /kind failing-test /milestone 1.22\nYou must be a member of the GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.", "commid": "kubernetes_issue_103651", "tokennum": 533}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6c57620a346dc9774cae37860441bc5390d4a14725ba0fc39487c770b3b420f1", "query": "if podConfig.NS == \"\" { return nil, fmt.Errorf(\"Cannot create pod with empty namespace\") } <del> if len(podConfig.Command) == 0 && !NodeOSDistroIs(\"windows\") { </del> <ins> if len(podConfig.Command) == 0 { </ins> podConfig.Command = \"trap exit TERM; while true; do sleep 1; done\" }", "positive_passages": [{"docid": "doc-en-kubernetes-fc6065ba1a9951ec296be8e3d5eed3592b7f58a8cbf0f7d83f44e7e6b4d2f288", "text": "<detailsIn response to : <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --ci-kubernetes-e2e-gci-gce-serial (gce-cos-master-serial) Four tests: Testgrid: https://k8s- Prow history: For CSI Volumes: For In-tree Volumes: #### Anything else we need to know: /kind failing-test /milestone 1.22 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\n/milestone v1.22\n/cc\n/cc (my close/reopen yesterday was accidental, sorry)\nI can take a look /assign\nThe non-subpath counterpart of this test is passing: These tests seem to use the default storageclass, whereas failing tests use in-tree hostpath and csi-hostpath\nThe CSI ones are failing because the hostpath driver never received a NodeUnstage (whereas it did in passing tests), causing the driver to error on volume deletion.\nIn the failed run kubelet has this error: which seems to have prevented kubelet from triggering a UnmountDevice. This error didn't exist in a successful run.\nHostpath driver can run with and without support for attach. Do you know which mode is enabled for this test?\nBetween the last passing time and when the test started failing, are there any PRs merged that look suspicious?\nAccording to csi-attacher logs, attach is disabled for both the good run and the failing run. Haven't spotted any obvious PRs so far, but I did find this: in the successful run, the log message for the successful is this: and the failed run: so the reconstructed volume names are somehow different. Checking reconstruction logic\nThis merged 12 days ago and was a pretty big change to pod lifecycle and could have trickling impact to volume manager. Does the timing of test failure match?\nThere is also this reconstruction fix that merged yesterday and seems related to outer vs inner spec name. I don't know if that will help fix this issue:\ncc\nLast successful run started at 7/8 17:49 PT, first failing run started at 7/9 2:23 PT.", "commid": "kubernetes_issue_103651", "tokennum": 491}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6c57620a346dc9774cae37860441bc5390d4a14725ba0fc39487c770b3b420f1", "query": "if podConfig.NS == \"\" { return nil, fmt.Errorf(\"Cannot create pod with empty namespace\") } <del> if len(podConfig.Command) == 0 && !NodeOSDistroIs(\"windows\") { </del> <ins> if len(podConfig.Command) == 0 { </ins> podConfig.Command = \"trap exit TERM; while true; do sleep 1; done\" }", "positive_passages": [{"docid": "doc-en-kubernetes-9f1333b0e960fd7acd243a96166fc71cf5883a52e7407e5f9400e1f08c54d3cf", "text": "was merged at 7/8 16:48 PT, so it's possible (if there's a delay in picking up master) Also this is in the failing kubelet logs but not in the successful one: I0720 18:20:42. ] \"Reconciler sync states: could not find volume information in desired state, clean up the mount points\" podName=-e508-45c2-8509- volumeSpecName=\"pvc--a615-4e89-afe8-\"\nFrom , the newly introduced log message here exists in the failing kubelet logs but not the successful one:\nFailures starting 07/08: /sig node for visibility\nI think caused the failures. Before after kubelet restarts, pod will still be in desired state (even through it is in terminating state), so that clean up mounts can be done completely. I think now, terminating pods will not be back to desired state, but reconstruction to actual state cannot completely clean up mounts. I am testing it about this.\nIs there a reason why reconstruction to actual state cannot clean up mounts? Note that a pod can be force deleted at any time, so a terminating pod that is force deleted would still have to be capable of being cleaned up (it won't be in desired state)? (note too that the expectation of the changes in is that terminating and fully terminated and \"never seen before\" should all completely equivalent from the perspective of other loops in the kubelet) If I understand you correctly, is this an existing bug that we're now triggering consistently?\nWe have both \"grace pod deletion\" and \"force pod deletion\" test cases that are failing.\nThere were a couple of key changes to volume loops in : Roughly before was \"it looks like it's got no running containers\", and after my change is \"we are going to be stopping all the containers from now on\". So this change meant that once a pod starts terminating, we are in \"tearing down mode\" and so my understanding of this method was that \"any pod where containers are being torn down is not in the desired state of the world\".", "commid": "kubernetes_issue_103651", "tokennum": 455}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6c57620a346dc9774cae37860441bc5390d4a14725ba0fc39487c770b3b420f1", "query": "if podConfig.NS == \"\" { return nil, fmt.Errorf(\"Cannot create pod with empty namespace\") } <del> if len(podConfig.Command) == 0 && !NodeOSDistroIs(\"windows\") { </del> <ins> if len(podConfig.Command) == 0 { </ins> podConfig.Command = \"trap exit TERM; while true; do sleep 1; done\" }", "positive_passages": [{"docid": "doc-en-kubernetes-015fa24d1e5eab79f6c5c1e5c14379be6e8185c1f089267f0bfc29a8792fef5f", "text": "After a restart, we would definitely not add a pod back that was in terminating state into desired state of the world, but \"restart + this change\" should be roughly equivalent to \"restart and force delete while restart is processing\" The other change was in which changed a live CRI read (which was trying to enforce that the dsowp is synchronized with the pod worker) into a threadsafe check against the pod worker directly (the pod worker can provide authoritative answers to \"this pod has no running containers\" now). The latter change seems less likely to impact you.\nThank you for the details! I think your change is making the right change, but unfortunately some of volume management still have issues, and so the tests rely on some behaviors that is not very right (pod volume is back to desired state even after it is in terminating) The cleanup mount currently does not have the logic to clean up global mount point if the volume plugin sets it up. I am still testing more and will share more details.\nis this a release blocker?\nYes, this impacts volume cleanup if kubelet restarts for any reason.\nOn a kube-up cluster running the latest master against the latest e2e binary, I was able to reproduce the in-tree failures but not the CSI ones for some reason. Will focus on in-tree failures for the time being\n/triage accepted\nmarking release-blocker per note on slack:\n/priority critical-urgent (once upon a time we used to not ship a release if any priority/critical-urgent issues were open, not sure if we decided to stop doing that)\nWe were able to find the trigger for the CSI failures - on 6/29 there was a change in the hostpath driver test manifest, and the driver's is enabled. This makes the driver return an error instead of only logging a warning message on if the volume isn't unstaged properly. IIUC there's a long standing issue that reconstruction doesn't handle node unstage. could you confirm? If that's the case, then these CSI failures are not release blocking. Furthermore, the CSI test with graceful delete started to fail on 7/9 because of since graceful and force deletes are now considered the same from the point of view of the volume manager. cc\nWhen that check was enabled, I don't think we realized it would impact the reconstruction path; it was enabled to validate a different issue.", "commid": "kubernetes_issue_103651", "tokennum": 504}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6c57620a346dc9774cae37860441bc5390d4a14725ba0fc39487c770b3b420f1", "query": "if podConfig.NS == \"\" { return nil, fmt.Errorf(\"Cannot create pod with empty namespace\") } <del> if len(podConfig.Command) == 0 && !NodeOSDistroIs(\"windows\") { </del> <ins> if len(podConfig.Command) == 0 { </ins> podConfig.Command = \"trap exit TERM; while true; do sleep 1; done\" }", "positive_passages": [{"docid": "doc-en-kubernetes-f86a5554f8df185db14256e7a7df5d445e052035a06405a03d3d05e494e0b68d", "text": "Are we running into the issue that reconstruction of staging directories isn't supported () OR is it that our reconstruction path requires drivers to have real mount points ()? Either way since both are known gaps with reconstruction, I think it makes sense to to disable the flag until we can address those issues.\nI was looking at this today too, trying to understand the underlying cause. That is why the failures are being reported now, but the part that I didn't understand is why NodeUnstageVolume is not being called for these volumes. In this instance: The DeleteVolume request fails because a staged path is still present: And in the kubelet log, NodeUnpublishVolume is called Then we hit this error: And NodeUnstageVolume is never called for this volume (same for other failures I looked at) so DeleteVolume keeps failing. So I think you're right that it's triggered by reconstruction, and it looks similar to , except in this case the restart happened before NodeUnpublishVolume.\nAnd it's probably not since the test uses a PVC\nWill look deeper into why UnmountDevice wasn't issued as well, but some update on the in-tree tests: the force delete test is skipped for the in-tree hostpath CSI driver because of Graceful tests are now failing as well because they behave like force tests due to\nI don't think the issue is related to PVC or not. I think it's related to drivers that do not actually mount devices as a separate filesystem than the root.\nThere are three possible flows during kubelet restart pod gracefully delete case, the pod still exists (it is not considered as terminated in function isPodTerminated(); note that this logic has some changes after , see , so pod volume will be back to desired state, and reconciler will try to set up volume and fill in actual state. When pod volume is finally deleted from desired state, reconciler will trigger teardown with information from actual state to unpublish and unstage volume. pod is forcefully deleted, pod volume will not be in desired state. If volume reconstruction succeeds (be able to reconstruct volume spec), volume will be back into actual state. Then reconciler will trigger teardown with information from actual state to unpublish and unstage volume (this part is similar to case 1).", "commid": "kubernetes_issue_103651", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6c57620a346dc9774cae37860441bc5390d4a14725ba0fc39487c770b3b420f1", "query": "if podConfig.NS == \"\" { return nil, fmt.Errorf(\"Cannot create pod with empty namespace\") } <del> if len(podConfig.Command) == 0 && !NodeOSDistroIs(\"windows\") { </del> <ins> if len(podConfig.Command) == 0 { </ins> podConfig.Command = \"trap exit TERM; while true; do sleep 1; done\" }", "positive_passages": [{"docid": "doc-en-kubernetes-0adb5aef0ac6855d53f98480f83c42da417641735fd51e124c8667d192575ced", "text": "last case is reconstruction failed (in this csi-host-path test, reconstruction will fail due to issue related to , it fail to check mount point for csi hostpath driver because it is using a bind mount of the same device ). In this case, reconciler will try to clean up mounts directly, but only published volume path, not the staged volume path (this logic is not implemented due to missing information). As a workaround, we can now disable check-volume-lifecycle if it does not cause other issues. Then we will work on to make sure csi-host-path driver can pass volume mountpoint check during reconstruction.\nThis issue is now mitigated with merged. There are two longer-term issues that are isolated to hostpath plugins (and maybe other plugins that are similar in behavior, perhaps emptydir and similar?): related to IsLikelyNotMountPoint as mentioned. Because these don't impact the core volume machinery and are not regressions, this issue doesn't need to be release blocking. We'll close this issue once (2) is tracked.\nis the IsLikelyNotMountPoint issue\nafter is merged, two csi-hostpath driver subpath test can pass, and two in-tree driver gracefully delete tests were skipped. https://k8s-\ncan you please cherry-pick to release-1.22 branch?\nOpened cherry-pick, please review:\n- what is the plan for reenabling them?\ncherry-pick merged!\nCheng and I will work on solving IsLikelyNotMountPoint issue for hostpath drivers. That should allow test to pass and we can enable them.\nCan this be removed from the milestone now that the workarounds have been merged, while leaving this issue open to track further work?\nWe can use existing issue to track the real fix. /close\nClosing this issue. <detailsIn response to : We can use existing issue to track the real fix. 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", "commid": "kubernetes_issue_103651", "tokennum": 438}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6c890f494514786854fa51e2bbf4bca08b9b1682b1a7c462f3b6274629330ce6", "query": "continue } <del> // Remember the last supported test for subsequent test of beta API betaTest = &test </del> ginkgo.By(\"Testing \" + test.Name) suffix := fmt.Sprintf(\"%d\", i) test.Client = c", "positive_passages": [{"docid": "doc-en-kubernetes-e2f4fe7b99012f8e7173e2f6c46ef5707967f19510033d4b6b03e3a31c7298f0", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --ci-kubernetes-e2e-gci-gce-slow [sig-storage] Dynamic Provisioning DynamicProvisioner [Slow] should provision storage with different parameters 5/13 https://k8s- v1beta1.StorageClass got removed in We should remove the v1beta1 test.\n/assign can you help take a look?\n/triage accepted\n/sig storage\nI run the test with the latest from master without removing the beta test and it failed with a different error before getting to the beta test part: Do you have any idea what would've happened in my setup? I redeployed k/k using master HEAD\nFor this testcase: I saw that the provisioned PD has a size of 1.5Gi according to kubernetes: And in gcloud It's really interesting that the test was expecting 2Gi to be created, is this something that was changed recently?\nThe logs you posted are showing pd csi as the provisioner. Were you testing with the intree driver or csi driver? The CSI driver should to the nearest Gb. I believe intree does the .\nI think I did intree because I didn't send as an argument in my command: It's interesting that the PVC has this annotation too:\nmmm something interesting about my setup is that I created the cluster with CSIMigration turned on Do you think that might be forcing the usage of ?\nYes likely. Try with CSIMigration off and see if that helps. If so, then this potentially seems like a rounding bug with the csi driver\nThanks I tried with and it did indeed round up to 2Gi.", "commid": "kubernetes_issue_102076", "tokennum": 373}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6cd36c4b73d2ce3777044fb979b39661e259bd4186cf8361f9d4aee3d12cbfe5", "query": "local local_ssds=\"\" if [[ ! -z ${NODE_LOCAL_SSDS+x} ]]; then <ins> # The NODE_LOCAL_SSDS check below fixes issue #49171 # Some versions of seq will count down from 1 if \"seq 0\" is specified if [[ ${NODE_LOCAL_SSDS} -ge 1 ]]; then </ins> for i in $(seq ${NODE_LOCAL_SSDS}); do <del> local_ssds=\"$local_ssds--local-ssd=interface=SCSI \" </del> <ins> local_ssds=\"$local_ssds--local-ssd=interface=SCSI \" </ins> done <ins> fi </ins> fi local network=$(make-gcloud-network-argument ", "positive_passages": [{"docid": "doc-en-kubernetes-c8f75f1ad6e3f2bccb3ac0da7b9de068a195504da38201c6a8a8d5b4a34c6c73", "text": "Is this a BUG REPORT or FEATURE REQUEST?: BUG /kind bug What happened: If you are using a mac and GCE and you specify NODELOCALSSDS=0 when using GCE via kube-up or e2e --up, then you end up getting 2 local SSDs. What you expected to happen: I would expect to get 0 local SSDs by default and when I specify NODELOCALSSDS=0 explicitly. How to reproduce it (as minimally and precisely as possible): On mac execute: NODELOCALSSDS=0 go run -- -v --up Anything else we need to know?: I've discovered that this issue is due to If NODELOCALSSDS=0, this evaluates to $(seq 0) From man seq on mac osx This was run on mac with the seq manpage indicating it comes from BSD Feb 19 2010. Note: some unix/linux variants, e.g. a test on ubuntu with coreutils 8.25 and a test on centos-7 with coreutils 8.22, had a different behavior that does not demonstrate this bug. Environment: Cloud provider or hardware configuration**: GCE OS (e.g. from /etc/os-release): mac osx\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig storage", "commid": "kubernetes_issue_49171", "tokennum": 376}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6d55f23be52681c64b32b29762287dc516b8eac8bf8546f1574dcde8d7ded593", "query": "command: - /bin/sh - -c <del> - echo -998 > /proc/$$$/oom_score_adj && kube-proxy {{api_servers_with_port}} {{kubeconfig}} {{cluster_cidr}} --resource-container=\"\" {{params}} 1>>/var/log/kube-proxy.log 2>&1 </del> <ins> - kube-proxy {{api_servers_with_port}} {{kubeconfig}} {{cluster_cidr}} --resource-container=\"\" --oom-score-adj=-998 {{params}} 1>>/var/log/kube-proxy.log 2>&1 </ins> {{container_env}} {{kube_cache_mutation_detector_env_name}} {{kube_cache_mutation_detector_env_value}}", "positive_passages": [{"docid": "doc-en-kubernetes-5266c57682848ccf4bbfd7d438a66f7fa505006f21647746bff2e69ab7956c41", "text": "In cluster/saltbase/salt/kube-proxy/kube-proxy.manifest, we have this: But kube-proxy also has a flag. Is there a reason to use the approach instead of using the flag? cc as you wrote the code, in\n/cc who's working on moving kube-proxy to a DaemonSet\nIn general, oomscoreadj is not expected to be directly updated by pods and kubelet is expected to manage it. If kube-proxy runs in the Guaranteed QoS class, then it's OOM score adj will be set to a low number. Until that happens, kube-proxy process may want to be shielded from OOM kills to an extent (this matters only when kube-proxy's memory usage memory request) Meanwhile, it does not make sense to have two means to configure the same thing. I'll let decide which option he prefers and sunset the other option.\nThanks for clarifying. At this point, I prefer to use the built-in flag instead of relying on composing bash commands. Sent for this.", "commid": "kubernetes_issue_51083", "tokennum": 231}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6d588a1e395c16797b66a24e4fc0e8288c66d00603734aae74a6f868f36064c0", "query": "// visit selectors if b.selector != nil { <del> if len(b.name) != 0 { </del> <ins> if len(b.names) != 0 { </ins> return &Result{err: fmt.Errorf(\"name cannot be provided when a selector is specified\")} } if len(b.resources) == 0 {", "positive_passages": [{"docid": "doc-en-kubernetes-8781beaf9cecb5a2a5891763e358d97bbb8efac5ebba9fc986604965efa0dda5", "text": "Currently, it could not delete multiple pods at once, need to delete them one by one, it's very inconvenient if I have tons of pods to delete. Unlike docker, docker can multiple stop/rm containers/images at once.\nThis is possible using label selectors as of , which is better if you have tons of pods.\nI agree that using label selector is better to delete all of pods under the label. But to delete multile pods at once is still usable: I just want to delete 1/2 pods under the label, label selector will not work selector could not span over other selectors or pods Another reason is docker rm/stop x y z works, I will wonder why kubectl cannot. This is not urgent, but I hope it can be implemented.\nI agree. Thanks for the suggestion.\nWould this be a suitable task for someone new to k8s development? If so, I'd be willing to take a look at this, if someone could provide a couple of hints where to start.\nFurther to my last message, I have a functional work in progress I would like to share, if anyone is interested?\nPRs are welcome. See\nYes, this is a reasonable place to start. Since its in the client, you won't get much orientation to the core server code, but it will be a good place to orient to the client side API. There us also prior art that you can model off of. The kubectl create ... command already supports multiple resources. A good command to adapter would be the 'label' command. You can find it in Many thanks in advance! Brendan On Feb 19, 2015 8:21 AM, \"Eric Tune\" wrote:", "commid": "kubernetes_issue_3050", "tokennum": 364}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6db9f0ccd4a5da72ebbe80c8253c1cff68d85fedeb704ccc4e094466ceb93ec8", "query": "}, expected: CreatePodUpdate(kubetypes.SET, kubetypes.FileSource, &api.Pod{ ObjectMeta: api.ObjectMeta{ <del> Name:      \"test-\" + hostname, UID:       \"12345\", Namespace: \"mynamespace\", SelfLink:  getSelfLink(\"test-\"+hostname, \"mynamespace\"), </del> <ins> Name:        \"test-\" + hostname, UID:         \"12345\", Namespace:   \"mynamespace\", Annotations: map[string]string{kubetypes.ConfigHashAnnotationKey: \"12345\"}, SelfLink:    getSelfLink(\"test-\"+hostname, \"mynamespace\"), </ins> }, Spec: api.PodSpec{ NodeName:                      hostname,", "positive_passages": [{"docid": "doc-en-kubernetes-8bc8d69d49aedfb4a9bf3991de80f7c339e96bfbefe5b1f250dae70fa0393729", "text": "See for more context. Currently, kubelet compares the spec of a mirror pod (created via apiserver) with that of a static pod (config stored as a file) to decide whether the two are considered identical. If they differ, kubelet would delete the mirror pod and re-create it with the correct spec. Due to the fact that apiserver may set default values for some fields in the spec of the mirror pod, the specs could deviate undesirably. To avoid problems like this, we can store the config of a static pod as an annotation in the mirror pod, and compare the static pod with the annotation.\nWould a hash of the config be sufficient if we're only going to compare? The whole spec would generally be more useful, but I wonder if that is too much data to put in an annotation.\nThis seems totally reasonable to me, but I'm still desperately curious why you can't just bypass defaulting when you generate mirror pod from static pod? (i.e. just use the static pod's configuration verbatim)\nIt's not kubelet who applies the default values here. The admission plugin was only run at the apiserver, and to bypass that, you have to ask apiserver to treat mirror pods differently and potentially at multiple places.\nOn May 22, 2015 10:38 AM, \"Yu-Ju Hong\" wrote: Understood, but is it really multiple places? If so then I agree it's a bad idea. Otherwise it might be worth considering as an alternative.\nIt's untenable for Kubelet to assume to know/circumvent all fields that will be set by other entities: admission control, defaulting, late initialization, auto-something, whatever. It needs to obey the same rules as other clients.\nI don't understand why you would ever want to apply any of the things you mentioned to static pods. Static pods should be copied verbatim into the mirror pods, right? That's what I'm proposing.\nWhat if the master is updated before the kubelet, and the master adds a new API field with a default value?\nThat case should be discussed in\nI agree that mirror pod should reflect the true status of the static pod running on the node, and no default values should be set in this case.", "commid": "kubernetes_issue_8683", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6db9f0ccd4a5da72ebbe80c8253c1cff68d85fedeb704ccc4e094466ceb93ec8", "query": "}, expected: CreatePodUpdate(kubetypes.SET, kubetypes.FileSource, &api.Pod{ ObjectMeta: api.ObjectMeta{ <del> Name:      \"test-\" + hostname, UID:       \"12345\", Namespace: \"mynamespace\", SelfLink:  getSelfLink(\"test-\"+hostname, \"mynamespace\"), </del> <ins> Name:        \"test-\" + hostname, UID:         \"12345\", Namespace:   \"mynamespace\", Annotations: map[string]string{kubetypes.ConfigHashAnnotationKey: \"12345\"}, SelfLink:    getSelfLink(\"test-\"+hostname, \"mynamespace\"), </ins> }, Spec: api.PodSpec{ NodeName:                      hostname,", "positive_passages": [{"docid": "doc-en-kubernetes-0491e123884f0f20f50d0a788bca7a6a29e2fa08227703a00221ecbd3bcf483c", "text": "However, I think it'd be harder to implement this way since, as stated above, that there are many things to circumvent in the apiserver itself. It could also be harder to keep this special case from being broken by a yet another new feature/plugin. Keeping the hash of the config in the annotation seems like a good compromise even though it may not reflect the true status 100% accurately. I think this is acceptable. What do you think?\nSure, if you think the annotation approach is easier, I would go with that. I guess in the case Brian mentoined (master adds a new API field with a default value), you would not update the mirror pod, because the static pod definition has not changed?\nYes, a hash would be sufficient.\nIt shouldn't be necessary to update the mirror pod in the case that a new default field was updated, because that field should be populated automatically by the apiserver on decode from etcd.\nWe should fix this so we don't have this problem again in 1.2.", "commid": "kubernetes_issue_8683", "tokennum": 226}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6e0fdf11bc38c79c98a53c48e4a4f7e1d43a7339cec1cd42cc3ce1e09b2f67dd", "query": "idxPath := fldPath.Index(i) if len(*endpointPort.Name) > 0 { <del> for _, msg := range validation.IsValidPortName(*endpointPort.Name) { allErrs = append(allErrs, field.Invalid(idxPath.Child(\"name\"), endpointPort.Name, msg)) } </del> <ins> allErrs = append(allErrs, apivalidation.ValidateDNS1123Label(*endpointPort.Name, idxPath.Child(\"name\"))...) </ins> } if portNames.Has(*endpointPort.Name) {", "positive_passages": [{"docid": "doc-en-kubernetes-b73bb51cef5016ee2dcd80aae4248808fec811a4dad3a3b7abbba7673a446c48", "text": "What happened: No endpoints created in the EndpointSlice for my service due to the port on the service being too long. Logs show: EndpointSlice created has no endpoint: What you expected to happen: Service that works with Endpoints should work with EndpointSlice. If this is intentional, it should be clearly documented How to reproduce it (as minimally and precisely as possible): Create a service with a long port name Environment: Kubernetes version (use ): 1.16 Cloud provider or hardware configuration: kind\n/sig networking\nThe label(s) cannot be applied. These labels are supported: <detailsIn response to : /sig networking 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\n/sig network These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by vllry. \u200d\nFor a rough measure of impact, Istio had 5 ports that were over this limit (and many more that were right at 15 characters), so I suspect it may not be terribly rare.\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nThis needs to be resolved before endpointslices graduate from alpha\n/assign\n/remove-triage unresolved", "commid": "kubernetes_issue_84388", "tokennum": 292}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6e2c1bc6158e191a5160572ec5b4961d1dad35e7dd1f69c2ea85d11f9204dae9", "query": "if err := nm.syncNamespaceFromKey(key.(string)); err != nil { if estimate, ok := err.(*contentRemainingError); ok { go func() { <ins> defer utilruntime.HandleCrash() </ins> t := estimate.Estimate/2 + 1 glog.V(4).Infof(\"Content remaining in namespace %s, waiting %d seconds\", key, t) time.Sleep(time.Duration(t) * time.Second) nm.queue.Add(key) }() <ins> } else { // rather than wait for a full resync, re-add the namespace to the queue to be processed nm.queue.Add(key) utilruntime.HandleError(err) </ins> } } }()", "positive_passages": [{"docid": "doc-en-kubernetes-5963c982feb2169d82fc17ad89ab9be2967cbad808254e7a712ad33fb952ec83", "text": "If the namespace controller gets an error when doing a sync and the error is not a error the error will not be handled. Ran in to this when we found When deleting a namespace it received a error that wasn't reported anywhere and the namespace stuck in because a finalizer was left.\nOther things noticed in the namespace controller: need a crash handler in sweep for all error return cases and determine whether should be returned determine what to do with non- errors at ... I think that currently it just hangs termination of that namespace until a resync\nI will take a look. Thanks for the heads up.", "commid": "kubernetes_issue_21406", "tokennum": 130}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6e399915e317dbca1e2d3af1f1e58142ce2c16f02c837d72146028f96969a102", "query": "admissionapi \"k8s.io/pod-security-admission/api\" samplev1alpha1 \"k8s.io/sample-apiserver/pkg/apis/wardle/v1alpha1\" \"k8s.io/utils/pointer\" <del> \"k8s.io/utils/strings/slices\" </del> \"github.com/onsi/ginkgo/v2\" \"github.com/onsi/gomega\"", "positive_passages": [{"docid": "doc-en-kubernetes-a36678f387087dd8252401a5249426873ced2ebb26644cae4efea96ce80ca1f6", "text": "reported that conformance testing with the latest version of sonobuoy against a version 1.29.0-alpha.3 cluster fails on the support the 1.17 Sample API Server using the current Aggregator test: , related to I found the reason why the test is working fine in Kubernetes CI jobs but fails with sonobuoy is because the service account used by sonobuoy \"sonobuoy-serviceaccount\" doesn't have read permission of the non-resource url \"/\", which is used by the test to confirm the removal of group path: The permission of \"sonobuoy-serviceaccount\" is as below: There may be two ways to fix it: the RBAC rule of sonobuoy to include \"get\" of \"/\". However, could other test runners encounter this issue? Is there a doc listing the required permissions for running e2e tests? the e2e to skip checking the removal of the group path if the service account doesn't have permission to access the root path. Which way do we usually prefer? Running e2e with sonobuoy should succeed. a v1.29.0-alpha.3 cluster. No response <details</details<details</details<details</details<details</details<details</details<details</details\nimplemented this solution.\n/sig api-machinery\nthank you for opening this issue and working on a solution. I'm probably not the right person to decide on which solution is preferred. From my perspective, either solution is fine.\nNote: Sonobuoy is not owned by any Kubernetes SIG. At most it is between SIG Architecture and the CNCF to choose whether to recommend it for running tests. SIG Testing owns the e2e image that sonobuoy can be used to schedule but not sonobuoy. IMHO this is a bug in running the tests via a pod, which is not how we develop the tests (they're run outside the cluster, by a cluster admin account typically). I would say 1) is the correct answer. xref: /sig architecture /sig testing /triage accepted cc\nthanks for your comment. I guess 1) means non of the existing sonobuoy versions can pass K8s conformance test against a cluster 1.29.0-alpha3, as the RBAC rule is hardcoded.", "commid": "kubernetes_issue_121985", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6e399915e317dbca1e2d3af1f1e58142ce2c16f02c837d72146028f96969a102", "query": "admissionapi \"k8s.io/pod-security-admission/api\" samplev1alpha1 \"k8s.io/sample-apiserver/pkg/apis/wardle/v1alpha1\" \"k8s.io/utils/pointer\" <del> \"k8s.io/utils/strings/slices\" </del> \"github.com/onsi/ginkgo/v2\" \"github.com/onsi/gomega\"", "positive_passages": [{"docid": "doc-en-kubernetes-4545476cbce0605bfe46d5a01c41b8f4cf7b5ac07772bfb1748611bc506e90ef", "text": "I will file an issue to sonobuoy first.\nquestion here is what are the set of client permissions required to run the conformance suite? perhaps a level of access or a more granular recommendation should be documented. what is your take on the root path requirement as approver for: EDIT: slack thread:\nI agree, we already require e.g. privileged pods for a long time in conformance tests and we should make it clear that we expect a highly privileged client.\n+1 for what is saying, that we should expect that the user running the tests has required permissions. These tests are not built for being run unprivileged.\ni wanted to PR the admin note in our conformance docs under sig-arch, but then i saw this: so broke this guarantee. sounds like SIG Arch needs to comment.\nThis statement surprises me. Root discovery is one of the least-privileged permissions you can have on a cluster. For years this was even open for unauthorized users on the internet (if your api endpoint has been exposed). In other words, just add the permission. While thinking about it, it is surprising that the user in question does not have this access already. Don't we allow that for every authorized user?\nIn contrast, I hope that lots of privileged operations are tested by conformance today. If we don't test things like admission webhooks for example, we have much bigger problems. And admission webhooks are basically equivalent to cluster-admin.\nthat is outdated, we use hostNetwork pods one some of the tests IIRC\nlooks like we don't. before this ticket, i was under the impression that the conformance suite already requires admin and that all testers (like Sonobuoy) use admin level credentials. it is non-privileged (e.g., does not require root on nodes, access to raw network interfaces, or cluster admin permissions) looks like we may have to change that sentence completely.\nWould have expected it here: The PR in question explicitly fixes the result returned by . If that is part of conformance (IMO it should), every conformance test needs access it obviously. Whether we require admin, or we add it manually, either would work.", "commid": "kubernetes_issue_121985", "tokennum": 474}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6e399915e317dbca1e2d3af1f1e58142ce2c16f02c837d72146028f96969a102", "query": "admissionapi \"k8s.io/pod-security-admission/api\" samplev1alpha1 \"k8s.io/sample-apiserver/pkg/apis/wardle/v1alpha1\" \"k8s.io/utils/pointer\" <del> \"k8s.io/utils/strings/slices\" </del> \"github.com/onsi/ginkgo/v2\" \"github.com/onsi/gomega\"", "positive_passages": [{"docid": "doc-en-kubernetes-06abc1218304c92779dae2744e33107a4d26263c1c54e4453f3f92a1949c2aa2", "text": "adding to milestone and making release blocking ... we should not release 1.29 in a state that the most commonly used conformance tool will fail\nIMO we should clarify the state and go fix the tool, but we should keep the test and we should NOT add skip. Conformance docs are not a release artifact, and sonobuoy release lifecycle is not a conformance artifact. If we can't get sonobuoy working in a reasonable time, we already know the tests can be run by scheduling the image (which is ours) directly with kubectl instead and we can document that in the upstream conformance docs. We need to fix the for this image: ,%20master%20(dev) And it should probably be to release-blocking in the future.\nit looks like the e2e change made in was not consciously made part of conformance, it was just trying to functionally test the bugfix being made. For 1.29, I think we should revert the change to and make an integration test that validates the fix instead. We can revisit whether content of is part of conformance or not for 1.30\nI opened to revert the e2e change and move the functional test to an integration test\nFiled to try to get the image job passing again.\nWe probably need another issue to track 1.30 follow-up?\nIf no one has done it, I could create another issue and follow up with the items that have been discussed here: outdated privilege requirement in commonly used conformance tools like sonobuoy aware of the required priviledge to avoid similar situations in the future. permission of GET \"/\" to authorized users via the role for root discovery.", "commid": "kubernetes_issue_121985", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6e3c74340fb0c64c805550bd7e7f70304bcbe8e68ef36a554bf030df27c671f3", "query": "# The IP of the master export MASTER_IP=\"10.245.1.2\" <del> export INSTANCE_PREFIX=kubernetes </del> <ins> export INSTANCE_PREFIX=\"kubernetes\" </ins> export MASTER_NAME=\"${INSTANCE_PREFIX}-master\" # Map out the IPs, names and container subnets of each minion", "positive_passages": [{"docid": "doc-en-kubernetes-618a17ee1a2bfcaa30e720bd6c59c3ac91ee900494c2c92ac1b2427757bb09d9", "text": "reported a variety of failure modes in .\n+1\nI figured I'd add to this issue rather than create a new one. I attempted to create a vagrant cluster today (dev tree is up to date) with 1 Master and 1 Minion and the cluster creation is stuck in the 'Validating master' loop ( for over 10 minutes in the validating loop ). salt-master and salt-minion logs seem to be empty ( they don't appear to be running, in fact ).\nI still have the cluster running in case anybody wants additional information.\n/cc please let me know if there is any other information about my vagrant setup that I need to post here.\nI have been working to get more stability in this environment over last few days. Can you try again from HEAD after this merges:\nCan you also verify that you built a release prior to running cluster/Kube-up?\nyes, I started from scratch and built a release before running cluster/kube- - cluster/kube- seems to fail fairly early in case there is no release build available.\nIt looks like got merged. I'll try again and get back to you.\nThe vagrant cluster seems to come up ( completes master and minion validation ). However, there is new credentials related error that is showing up at the end of running cluster/kube- :\nI'll add one more problem I've encountered. Runing from head:\nNew to me. Will investigate more tomorrow. Sent from my iPhone\nAlso new to me :-) - will see if I can reproduce either. Sent from my iPhone\nYour credendials and certificates are not working with new environment. Just delete your .kubernetesvagrant* files and recreate the cluster. It would be nice to automate this task, if you tear down the cluster.\nI am able to reproduce the 502 Bad Gateway error and am working on determining what changed in order to provide a resolution over the last couple days. Please assign this issue to me.\nThe issue appears to me that the kube-apiserver is not getting provisioned by salt correctly. Parsing Salt logs to determine why.\nLooks like the file is not getting laid down by salt for some reason ;-)\nThe Jinja template was changed as part of identifying the cluster. Fixing up now, and will send a PR to close this issue.\nthat was it, thanks!", "commid": "kubernetes_issue_4302", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6e94eb507cdefe046b645f78591bee857508ff5220baaf141131aecb10b15c57", "query": "\"//pkg/registry/rbac/rolebinding/etcd:go_default_library\", \"//pkg/registry/rbac/rolebinding/policybased:go_default_library\", \"//pkg/util/runtime:go_default_library\", <ins> \"//pkg/util/wait:go_default_library\", </ins> \"//plugin/pkg/auth/authorizer/rbac/bootstrappolicy:go_default_library\", \"//vendor:github.com/golang/glog\", ],", "positive_passages": [{"docid": "doc-en-kubernetes-b8d2c0da68304e83135ba886da3cc34043a1f75faa72e9753c7e99fa612dae72", "text": "From etcd3: May need to retry poststarthook a few times to avoid bootstrapping failures like this.", "commid": "kubernetes_issue_39108", "tokennum": 26}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6ea9bd2c4e188e1ecd46ccabfd84939d8a3cdf02ac53fa1dc281c07d5f11d0a0", "query": "github.com/envoyproxy/go-control-plane v0.10.2-0.20220325020618-49ff273808a1/go.mod h1:KJwIaB5Mv44NWtYuAOFCVOjcI94vtpEz2JU/D2v6IjE= github.com/envoyproxy/protoc-gen-validate v0.1.0/go.mod h1:iSmxcyjqTsJpI2R4NaDN7+kN2VEUnK/pcBlmesArF7c= github.com/ghodss/yaml v1.0.0/go.mod h1:4dBDuWmgqj2HViK6kFavaiC9ZROes6MMH2rRYeMEF04= <ins> github.com/go-logr/logr v1.2.0/go.mod h1:jdQByPbusPIv2/zmleS9BjJVeZ6kBagPoEUsqbVz/1A= github.com/go-logr/logr v1.2.3 h1:2DntVwHkVopvECVRSlL5PSo9eG+cAkDCuckLubN+rq0= github.com/go-logr/logr v1.2.3/go.mod h1:jdQByPbusPIv2/zmleS9BjJVeZ6kBagPoEUsqbVz/1A= </ins> github.com/gogo/protobuf v1.3.2 h1:Ov1cvc58UF3b5XjBnZv7+opcTcQFZebYjWzi34vdm4Q= github.com/gogo/protobuf v1.3.2/go.mod h1:P1XiOD3dCwIKUDQYPy72D8LYyHL2YPYrpS2s69NZV8Q= github.com/golang/glog v0.0.0-20160126235308-23def4e6c14b/go.mod h1:SBH7ygxi8pfUlaOkMMuAQtPIUF8ecWP5IEl/CR7VP2Q=", "positive_passages": [{"docid": "doc-en-kubernetes-82432c9a9613bf4aed980cc8db469ba43857eb8e48c1e0dd0f39492115206ab6", "text": "generation for local KEK based on counter; also rotate once a week even if the counter does not hit 2 million? using AES-GCM encryption of local KEK ref: The implementation would be to the directory.\n/sig auth /triage accepted\n/assign\nGitHub didn't allow me to assign the following users: ibihim. 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\n/assign\nthank you !\n/milestone v1.26\nHi bug-triage shadow team member for 1.26 here. Looks like this issue is in the 1.26 milestone, but has been moved to 1.27. Is there something else or should this issue go to 1.27 as well? Thank you!\nI just forgot to move this issue /milestone v1.27\n/reopen is the partial implementation.\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nMy suggestion on the reference implementation, after reading 's comments is like so... The GRPC server, which implements the expects an implementation that satisfies . The local key logic can be a middleware. So it expects a it can fallback to, if it doesn't know a key or needs to encrypt its own local KEK. So the local implementation would be need to: have a storage of s have a reference to the current in use (if we put it into the cache, it might vanish) have a reference to another , which should be the remote KMS. So the sub-stories could look like: write Middleware write Transformers that can get exhausted (by time, by usage) write 's storage write some dummy for remote KMS? I have some sketches of what I am talking about .", "commid": "kubernetes_issue_112859", "tokennum": 462}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6ea9bd2c4e188e1ecd46ccabfd84939d8a3cdf02ac53fa1dc281c07d5f11d0a0", "query": "github.com/envoyproxy/go-control-plane v0.10.2-0.20220325020618-49ff273808a1/go.mod h1:KJwIaB5Mv44NWtYuAOFCVOjcI94vtpEz2JU/D2v6IjE= github.com/envoyproxy/protoc-gen-validate v0.1.0/go.mod h1:iSmxcyjqTsJpI2R4NaDN7+kN2VEUnK/pcBlmesArF7c= github.com/ghodss/yaml v1.0.0/go.mod h1:4dBDuWmgqj2HViK6kFavaiC9ZROes6MMH2rRYeMEF04= <ins> github.com/go-logr/logr v1.2.0/go.mod h1:jdQByPbusPIv2/zmleS9BjJVeZ6kBagPoEUsqbVz/1A= github.com/go-logr/logr v1.2.3 h1:2DntVwHkVopvECVRSlL5PSo9eG+cAkDCuckLubN+rq0= github.com/go-logr/logr v1.2.3/go.mod h1:jdQByPbusPIv2/zmleS9BjJVeZ6kBagPoEUsqbVz/1A= </ins> github.com/gogo/protobuf v1.3.2 h1:Ov1cvc58UF3b5XjBnZv7+opcTcQFZebYjWzi34vdm4Q= github.com/gogo/protobuf v1.3.2/go.mod h1:P1XiOD3dCwIKUDQYPy72D8LYyHL2YPYrpS2s69NZV8Q= github.com/golang/glog v0.0.0-20160126235308-23def4e6c14b/go.mod h1:SBH7ygxi8pfUlaOkMMuAQtPIUF8ecWP5IEl/CR7VP2Q=", "positive_passages": [{"docid": "doc-en-kubernetes-b75b4d558a76c05a2f299aa9e4208bfe14cbcf4125785eeef841ee037778035f", "text": "I would implement that in terms of the interface so that it can be used both in testing (via a local key) and in real code (by delegating to a HSM).\nHi bug-triage team member for 1.27 here. This issue is still open but has had no recent activity, and no active PRs. Is everything on track for the Code Freeze in March 14th? Thank you!\n/milestone clear\nCould be closed, right? :)\nWe still need metrics and tracing support for the reference implementation (though it is all a lot less important now).\n/retitle [KMSv2] Add metrics and tracing in for plugins\nThis is duplicate of /close\nClosing this issue. <detailsIn response to : This is duplicate of 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", "commid": "kubernetes_issue_112859", "tokennum": 192}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6ebe6b94ce008526b4c731126dfc7c24390464421e7b69eec3221b573a191c1a", "query": "syncLoopPeriod                = 100 * time.Minute maxWaitForUnmountDuration     = 50 * time.Millisecond maxLongWaitForUnmountDuration = 4200 * time.Second <ins> volumeAttachedCheckTimeout    = 5 * time.Second </ins> ) // Calls Run()", "positive_passages": [{"docid": "doc-en-kubernetes-dc8aac09a0e4bb26f9dc5f50aef7f845ea9d7c4b925d34b9f6eda044925f80f5", "text": "TestRunOneVolumeDetachFailNodeWithReadWriteOnce 4 times since 03-19 23:00 PDT, intermittently ! https://k8s- Still investigating whether this is a tolerable flake or not with more history than testgrid view, or otherwise would appreciate input from anyone with expertise in this test, especially as regards to whether this should be a blocker for tomorrows beta cut. maybe: /sig storage /sig testing\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nis already open for this, looks like it is attempting to fix it\nthank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. /close\nClosing this issue. <detailsIn response to : thank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. 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", "commid": "kubernetes_issue_116774", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6ebe6b94ce008526b4c731126dfc7c24390464421e7b69eec3221b573a191c1a", "query": "syncLoopPeriod                = 100 * time.Minute maxWaitForUnmountDuration     = 50 * time.Millisecond maxLongWaitForUnmountDuration = 4200 * time.Second <ins> volumeAttachedCheckTimeout    = 5 * time.Second </ins> ) // Calls Run()", "positive_passages": [{"docid": "doc-en-kubernetes-aef7ec00dc93616f97177ca3d23f28217445848b34c429e5746962ea28329f43", "text": "pull-kubernetes-unit TestRunOneVolumeDetachFailNodeWithReadWriteOnce Jan 7th, 2022 Check volume <fake-plugin/volume-nameis reported as attached to node <fail-detach-node, got false, expected true No response_ /sig storage\n/cc\nthis is the top unit test flake according to\ncc\nThe 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]:\nI think this test is no longer flaky by checking the test grid, close it now.\nUnfortunately this does still seem to be flaky: Here was the output from : /reopen\nReopened this issue. <detailsIn response to : Unfortunately this does still seem to be flaky: 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\n/remove-lifecycle stale\nstill the case\nHow about adding some logging to help troubleshoot this? I looked at it a little, but it is hard to tell which part of the test is failing. PR\n/\nThis is still happening\n/triage accepted\nFrom the logs, in the OneVolumeDetachFailNodeWithReadWriteOnce test, succeeded, but the next verification failed. In verifyVolumeAttachedToNode, the attachState is from calling and within asw, it calls . In verifyVolumeReportedAsAttachedToNode, the volumes are obtained from calling , it seems that the node is not in asw.nodesToUpdateStatusFor at this step. Cannot reproduce locally. I tried to run the test 100 times locally with debug.Stack()... 3 * 100 times all passed.\nTried to run stress test on my linux machine as well but still cannot reproduce. Command: Result: Also tried running n process in parallel. Command: Result:\nIt seems like it happens more frequently.", "commid": "kubernetes_issue_107414", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6ebe6b94ce008526b4c731126dfc7c24390464421e7b69eec3221b573a191c1a", "query": "syncLoopPeriod                = 100 * time.Minute maxWaitForUnmountDuration     = 50 * time.Millisecond maxLongWaitForUnmountDuration = 4200 * time.Second <ins> volumeAttachedCheckTimeout    = 5 * time.Second </ins> ) // Calls Run()", "positive_passages": [{"docid": "doc-en-kubernetes-62e47fd83b7fc1cc39259be1688a9f133b9cd2dc48247eb5d858fae7fd13955b", "text": "But I may have no time to dig into the cause. Let's see.\ncc as the test author.\nThe problem is that this test has a lot of dependency on the sleeps that are hardcoded with a very narrow scope, but our CI seems to be able to stress it much more. As soon as you slightly change one of the sleep duration it starts to flake locally The test can not make an assumption that timing is perfect, even more in the sub second range can someone in sig-storage review this test and make it less dependant on those tight sleeps?\nAccording to most failures, it failed at Line 660. Let me run some stress locally. with 250ms sleep with 100ms sleep\nI agree this test case is too brittle due to its specific timing dependencies. To fix this, I suggest reworking the test case to: 1) Add retry with timeout to wait for final conditions 2) Remove the intermediate timing-based state transition checks. Instead, we can keep track of state transitions in the Fakes and validate those stats. wdyt?\nFriendly ping from 1.27 CI Signal that this test is still a noisy flake on the master-blocking dashboard as CI Signal has flagged it in and", "commid": "kubernetes_issue_107414", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6ecb01aacb6f026714fe23cc353e275d39d2a646d9c522a80d5d14f019403bae", "query": "testCases := []struct { name          string ipModeEnabled bool <ins> nonLBAllowed  bool </ins> tweakLBStatus func(s *core.LoadBalancerStatus) <ins> tweakSvcSpec  func(s *core.ServiceSpec) </ins> numErrs       int }{ <del> /* LoadBalancerIPMode*/ </del> { <ins> name:         \"type is not LB\", nonLBAllowed: false, tweakSvcSpec: func(s *core.ServiceSpec) { s.Type = core.ServiceTypeClusterIP }, tweakLBStatus: func(s *core.LoadBalancerStatus) { s.Ingress = []core.LoadBalancerIngress{{ IP: \"1.2.3.4\", }} }, numErrs: 1, }, { name:         \"type is not LB. back-compat\", nonLBAllowed: true, tweakSvcSpec: func(s *core.ServiceSpec) { s.Type = core.ServiceTypeClusterIP }, tweakLBStatus: func(s *core.LoadBalancerStatus) { s.Ingress = []core.LoadBalancerIngress{{ IP: \"1.2.3.4\", }} }, numErrs: 0, }, { </ins> name:          \"valid vip ipMode\", ipModeEnabled: true, tweakLBStatus: func(s *core.LoadBalancerStatus) {", "positive_passages": [{"docid": "doc-en-kubernetes-e021a9a686a92d83ba285392c70089f3a0813200ee010fb06825ed96dc15cfdb", "text": "xref I think this may be one of the few cases where we can actually change the behavior in a \"breaking\" way. User creates service with , is empty Controller or user updates the status subresource, sets (not wiped or validated, should be) User updates in any way, is wiped It's clear that the is not meant to be set when is not \"LoadBalancer\". The question is: 1) Fail validation? 2) Silently discard the value? 3) Warn and then discard the value? 4) Just warn and leave it. Because we allowed it in the past, but it is so volatile, I lean towards 3. and - the people most familair with this type. Edit: PrepareForUpdate() runs before warnings. So: (1) is easy (2) is easy (4) is slightly less easy than (2) (3) is slightly less easy than (4)\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nOMG change it to clusterIP as expected Status is wiped update status as ClusterIP ... and if I edit the service back to loadbalancer it keeps the status??\n/kind bug\n/retitle Service can be set when !=\nWe talked about this one at the SIG Network meeting today. suggested we use the feature gate for deprecation option to phase the current (problematic) functionality out.\n/triage accept\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /triage accept 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", "commid": "kubernetes_issue_119700", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6f0cda27c2ea899f4f51d26525bdc7be3ed4d97df747556f5756a829b9e9a80d", "query": "} client := oauth2.NewClient(oauth2.NoContext, tokenSource) <ins> // Override the transport to make it rate-limited. client.Transport = &rateLimitedRoundTripper{ rt:      client.Transport, limiter: flowcontrol.NewTokenBucketRateLimiter(10, 100), // 10 qps, 100 bucket size. } </ins> svc, err := compute.New(client) if err != nil { return nil, err", "positive_passages": [{"docid": "doc-en-kubernetes-599cbd9914ac52a34ee08ac617d1f4bd774f52f2d5bdcb07fa1a0e76f7194545", "text": "On a large cluster, the routecontroller basically makes O(n) requests all at once, and most of them error out with \"Rate Limit Exceeded\". We then wait for operations to complete on the ones that did stick, and damn the rest, they'll be caught next reconcile (which is a while). In fact, in some cases it appears we're spamming hard enough to get rate limited by the upper-level API DOS protections and seeing something akin to , e.g.: We can do better than this!\nc.f. , which is the other leg of this problem\nI took a look into code and it seems that we are doing full reconciliation every 10s. If we need to create 2000 routes at the beginning it seems to frequently. I think that we need to: first compute how many routes we have to create based on that try to spread them over some time to reduce possibility of causing 'rate limit exceeded' I will try to put some small PR together as a starting point.\nI'm reopening this one, since this doesn't seem to be solved. So basically something strange is happening here. With PR we have 10/s limit on API calls send to GCE. And we are still rate-limitted. However, according to documentation we are allowed for 20/s: So something either doesn't work or is weird.\nWhat is super interesting from the logs of recent run: It starts to creating routes: After 2 minutes from that, we are hitting \"Rate limit Exceeded\" for the first time: And only after 9 minutes we create the first route ever. The second one is created after 15 minutes, and from that point we create a number of them So it seems that nothing useful is happening for the first 2 minutes, and then between 3m30 and 9m30\nOK - so I think that what is happening is that all controllers are sharing GCE interface (and thuse they have common throttling). So if one controller is generating a lot of API calls, then other controllers may be throttled. has a hypothesis that it may be caused by nodecontroller.\nOne thing my PR didn't address (because it was late): Now we have some obnoxious differences in logging when you go to make a request, because the versus could actually be absorbing a fair amount of ratelimiter.", "commid": "kubernetes_issue_26119", "tokennum": 488}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6f0cda27c2ea899f4f51d26525bdc7be3ed4d97df747556f5756a829b9e9a80d", "query": "} client := oauth2.NewClient(oauth2.NoContext, tokenSource) <ins> // Override the transport to make it rate-limited. client.Transport = &rateLimitedRoundTripper{ rt:      client.Transport, limiter: flowcontrol.NewTokenBucketRateLimiter(10, 100), // 10 qps, 100 bucket size. } </ins> svc, err := compute.New(client) if err != nil { return nil, err", "positive_passages": [{"docid": "doc-en-kubernetes-bf24c8733a67a958496376416be2eb636c6e4bfb94999815173220461c93fd0c", "text": "It could before because of the operation rate limiter and operation polling anyways, but now could be worse.\n- yes I'm aware of that. And probably this is exactly the case here.\nI got fooled by that - I guess we should fix it somehow.\nOne approach to fixing it is a similar approach to the operation polling code, but in the : warn if we ratelimited for more than N seconds (and dump the request or something? not clear how to clarify what we were sending).\nI found something else - Kubelet is also building GCE interface: We have 2000 kubelets, so if all of them send multiple requests to GCE, we may hit limits.\nAny idea in what circumstances Kubelet will contact cloud provider?\nHmm - it seems it contacts GCE exactly once at the beginning. So it doesn't explain much.\nI think it's only here: I've rarely seen GCE ratelimit readonly calls, in practice, and kubelets come up pretty well staggered.\nOK - so with logs that I , it is pretty clear that we are very heavily throttled on GCE api calls. In particular, when I was running 1000-node cluster, I see lines where we were throttle for 1m30. I'm pretty sure it's significantly higher in 2000-node cluster. I'm going to investigate a bit more where all those reuqests come from.\nActually - it seems that we have a pretty big problem here. Basically, Kubelet seems to send a lot of requests to GCE. So to clarify: every time Kubelet is updating NodeStatus (so every 10s by default) it is sending an API call to GCE to get it's not addresses: that means, that if we have 2000 nodes, kubelets generate 200 QPS to GCE (which is significantly more than we can afford) We should think how to solve this issue, but I think the options are: increasing QPS quota or calling GCE only once per X statusUpdates.\nThe second issue is that we are throttled at the controller level too, and this one I'm tryin to understand right now.", "commid": "kubernetes_issue_26119", "tokennum": 457}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6f0cda27c2ea899f4f51d26525bdc7be3ed4d97df747556f5756a829b9e9a80d", "query": "} client := oauth2.NewClient(oauth2.NoContext, tokenSource) <ins> // Override the transport to make it rate-limited. client.Transport = &rateLimitedRoundTripper{ rt:      client.Transport, limiter: flowcontrol.NewTokenBucketRateLimiter(10, 100), // 10 qps, 100 bucket size. } </ins> svc, err := compute.New(client) if err != nil { return nil, err", "positive_passages": [{"docid": "doc-en-kubernetes-b1dad1b374e4c58d925d9fef62d9846d5e0e5eda04aecdd78a124036a36cf31c", "text": "- that said, any rate-limitting on our side, will not solve the kubelet-related problem\nHmm - actually looking into implementation it seems that NodeAddresses are only contacting metadata server, so I'm not longer that convinced...\nAlso, I think that important thing is that a single call to GCE API can translate to multiple api calls to GCE. In particular - CreateRoute translates to: get instance insert route a bunch of getOperation (until this is finished)\nOK - so I think that what is happening here is that since CreateRoute translates to: get instance insert route a bunch of getOperations That means that if we call say 2000 CreateRoute() at the same time, all of them will try to issue: getInstance at the beginning. So we will quickly accumulate 2000 GET requests in the queue. Once they are processed, we generate the \"POST route\" then for any processed. So It's kind of expected what is happening here. So getting back to the Zach`s PR - I think that throttling POST and GET and OPERATION calls separate is kind of good idea in general.\nBut I still don't really understand why do we get \"RateLimitExceeded\". Is that because of Kubelets?\nI think that one problem we have at the RouteController level is that if CreateRoute fails, we simply don't react on it. And we will wait at least 5 minutes before even retrying it. We should add some retries at the route controller level too. I will send out some short PR for it.\nBut I still don't understand why do we get those \"RateLimitExceeded\" error\nOK - so as an update. In GCE, we have a separate rate-limit for number of in-flight CreateRoute call per project. is supposed to address this issue.\nOK - so this one is actually fixed. I mean that it is still long, but currently it's purely blocked on GCE.\nAs a comment - we have an internal bug for it already.", "commid": "kubernetes_issue_26119", "tokennum": 438}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6f385988b4a27cc38efd8a5f99d836f733d9e1780b566013a6e936760a242fe0", "query": "var _ = SIGDescribe(\"Deployment\", func() { var ns string var c clientset.Interface <ins> var dc dynamic.Interface </ins> ginkgo.AfterEach(func() { failureTrap(c, ns)", "positive_passages": [{"docid": "doc-en-kubernetes-cea21dfbf74ea26aea8b8fcc0c8d9d3e2b3e4488cd9f6d30773b87652fe6e220", "text": "[x] Original approval issue: [x] Test pr: [x] Two weeks soak end date: 19 November 2020 This issue is created to allow edit by /wip /hold According to this APIsnoop query, there are still some remaining Deployment endpoints which are untested. a Deployment with a static label the Deployment with a new Label and updated data the Deployment to ensure it's patched all Deployments in all Namespaces find the Deployment(1) ensure that the Deployment is found and is patched Namespaced Deployment(1) via a Collection with a LabelSelector Discover useragents: List endpoints hit by the test: Display endpoint coverage change: If a test with these calls gets merged, test coverage will go up by 5 points* This test is also created with the goal of conformance promotion.\n/sig testing /sig architecture /area conformance\nBobyMcbobs commented in original Issue: Unsure if the endpoint replaceAppsV1NamespacedDeploymentStatus is able to be hit. When this endpoint is attempted to be updated the data after retrieving the update resource doesn't reflect the values in the update\n/assign\nWhen using the appv1.Deployment structure instead of maps of interfaces to build the structure in a patch of the Deployment, this error comes up. Still in progress yment-static\":\"true\"}: does not match template , spec.selector: Invalid value: \"null\": field is immutable]\nreplaceAppsV1NamespacedDeploymentStatus to test. Increase cover by 1 Endpoint\n/reopen PR reverted by due to flaky test\nReopened this issue. <detailsIn response to : /reopen PR reverted by due to flaky test 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\nIssues 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\n/reopen Soaking, ready for promotion 19 November 2020\nReopened this issue. <detailsIn response to : /reopen Soaking, ready for promotion 19 November 2020 Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_90916", "tokennum": 522}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6f385988b4a27cc38efd8a5f99d836f733d9e1780b566013a6e936760a242fe0", "query": "var _ = SIGDescribe(\"Deployment\", func() { var ns string var c clientset.Interface <ins> var dc dynamic.Interface </ins> ginkgo.AfterEach(func() { failureTrap(c, ns)", "positive_passages": [{"docid": "doc-en-kubernetes-ff9ccf83336a9bf28b0576a991dfda56392cc48f280c272644ff154877b8104d", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/remove-lifecycle stale\n/triage accepted\n/merged", "commid": "kubernetes_issue_90916", "tokennum": 34}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6f508d75c32d21eb4c6e63a01f9c0fc1e69692c81e1ea2a4fdb13043c7f153fd", "query": "load(\"@io_bazel_rules_docker//container:container.bzl\", \"container_pull\") container_pull( <del> name = \"debian_jessie\", digest = \"sha256:e25703ee6ab5b2fac31510323d959cdae31eebdf48e88891c549e55b25ad7e94\", registry = \"index.docker.io\", repository = \"library/debian\", tag = \"jessie\",  # ignored when digest provided, but kept here for documentation. </del> <ins> name = \"distroless_base\", digest = \"sha256:7fa7445dfbebae4f4b7ab0e6ef99276e96075ae42584af6286ba080750d6dfe5\", registry = \"gcr.io\", repository = \"distroless/base\", tag = \"latest\",  # ignored when digest provided, but kept here for documentation. </ins> ) load(\"//build:workspace.bzl\", \"release_dependencies\")", "positive_passages": [{"docid": "doc-en-kubernetes-d99484417892d904a3f5edbb73fa06d2de654c460b279ad73f511e028afa6a6f", "text": "There are CVEs happening in different images - we already migrated Kubmeark from busybox in , but we should go one step further and migrate the base image to distroless. There are some things that would need to be changed mentioned here: /sig scalability\nCan I work on this? /assign\n/remove-help\n- sure that would be great.\nHi based on the discussion in , the kubemark image has dependency on and maybe more other utilities. So it seems impossible to migrate the base image to distroless? Or do we need something like debian-hyperkube-base?\nThe mount one we may get rid of - basically we should be able to switch to FakeMounter:", "commid": "kubernetes_issue_84284", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6f63f22b8747e74c1f6ce456abbfec7a860f0f4a052303b63f4874b5ec3d5a4d", "query": "} } <del> for _, endpointSlice := range slicesToCreate { addTriggerTimeAnnotation(endpointSlice, triggerTime) createdSlice, err := r.client.DiscoveryV1beta1().EndpointSlices(service.Namespace).Create(context.TODO(), endpointSlice, metav1.CreateOptions{}) if err != nil { // If the namespace is terminating, creates will continue to fail. Simply drop the item. if errors.HasStatusCause(err, corev1.NamespaceTerminatingCause) { return nil </del> <ins> // Don't create new EndpointSlices if the Service is pending deletion. This // is to avoid a potential race condition with the garbage collector where // it tries to delete EndpointSlices as this controller replaces them. if service.DeletionTimestamp == nil { for _, endpointSlice := range slicesToCreate { addTriggerTimeAnnotation(endpointSlice, triggerTime) createdSlice, err := r.client.DiscoveryV1beta1().EndpointSlices(service.Namespace).Create(context.TODO(), endpointSlice, metav1.CreateOptions{}) if err != nil { // If the namespace is terminating, creates will continue to fail. Simply drop the item. if errors.HasStatusCause(err, corev1.NamespaceTerminatingCause) { return nil } errs = append(errs, fmt.Errorf(\"Error creating EndpointSlice for Service %s/%s: %v\", service.Namespace, service.Name, err)) } else { r.endpointSliceTracker.Update(createdSlice) metrics.EndpointSliceChanges.WithLabelValues(\"create\").Inc() </ins> } <del> errs = append(errs, fmt.Errorf(\"Error creating EndpointSlice for Service %s/%s: %v\", service.Namespace, service.Name, err)) } else { r.endpointSliceTracker.Update(createdSlice) metrics.EndpointSliceChanges.WithLabelValues(\"create\").Inc() </del> } }", "positive_passages": [{"docid": "doc-en-kubernetes-b47abd0a7beb2bc1a841f65e5737673c1fa7ed1c22ab52e8ed01b146c2722dfe", "text": "What happened: In the PMEM-CSI CI, we rapidly deploy and remove a custom resources which then owns all objects created for that resource. Deletion of those objects is handled through ownership references, i.e. deleting the CR is expected to cascade to all objects. This worked fine up to Kubernetes 1.17. When starting to test with 1.18.2, we pretty reliably get into a state where the CR and the service objects owned by it are marked for deletion, but don't go away. Debugging with the garbage collector's dependency graph (see ) showed that endpointslices were blocking the deletion of the services and thus the CR. In the graph dump (= a snaphot in time), they were not even marked for deletion. A closer look showed that endpointslices for the services were getting created and deleted continuously for over 15 minutes. Eventually, the garbage collector won and managed to delete endpointslices and services before new endpointslices were created. What you expected to happen: There seems to be a missing check in if the service is marked for deletion (i.e. has a deletionTimestamp), then the controller should not create new endpointslices. How to reproduce it (as minimally and precisely as possible): I tried to boil it down to a script, but it just ran fine. The \"easiest\" way to reproduce it is to run PMEM-CSI's E2E testing, which is probably not easy enough :disappointed: Anything else we need to know?: Disabling the EndpointSlice feature makes the problem go away. Environment: Kubernetes version (use ): 1.18.2 Cloud provider or hardware configuration: QEMU virtual machines OS (e.g: ): Fedora Install tools: kubeadm /sig network\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\ncc for endpointslice\nThanks for the detailed bug report! Will work on getting a fix in soon. /assign\n/remove-triage unresolved\nCan you describe the general process to reproduce this bug? Would it involve hundreds of EndpointSlices for a Service? I've tried to recreate this in a , but unfortunately I haven't been able to get anything to break. Any ideas for what I could try?\nThere's one endpointslice per service. Our operator creates two services.", "commid": "kubernetes_issue_91287", "tokennum": 525}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6f63f22b8747e74c1f6ce456abbfec7a860f0f4a052303b63f4874b5ec3d5a4d", "query": "} } <del> for _, endpointSlice := range slicesToCreate { addTriggerTimeAnnotation(endpointSlice, triggerTime) createdSlice, err := r.client.DiscoveryV1beta1().EndpointSlices(service.Namespace).Create(context.TODO(), endpointSlice, metav1.CreateOptions{}) if err != nil { // If the namespace is terminating, creates will continue to fail. Simply drop the item. if errors.HasStatusCause(err, corev1.NamespaceTerminatingCause) { return nil </del> <ins> // Don't create new EndpointSlices if the Service is pending deletion. This // is to avoid a potential race condition with the garbage collector where // it tries to delete EndpointSlices as this controller replaces them. if service.DeletionTimestamp == nil { for _, endpointSlice := range slicesToCreate { addTriggerTimeAnnotation(endpointSlice, triggerTime) createdSlice, err := r.client.DiscoveryV1beta1().EndpointSlices(service.Namespace).Create(context.TODO(), endpointSlice, metav1.CreateOptions{}) if err != nil { // If the namespace is terminating, creates will continue to fail. Simply drop the item. if errors.HasStatusCause(err, corev1.NamespaceTerminatingCause) { return nil } errs = append(errs, fmt.Errorf(\"Error creating EndpointSlice for Service %s/%s: %v\", service.Namespace, service.Name, err)) } else { r.endpointSliceTracker.Update(createdSlice) metrics.EndpointSliceChanges.WithLabelValues(\"create\").Inc() </ins> } <del> errs = append(errs, fmt.Errorf(\"Error creating EndpointSlice for Service %s/%s: %v\", service.Namespace, service.Name, err)) } else { r.endpointSliceTracker.Update(createdSlice) metrics.EndpointSliceChanges.WithLabelValues(\"create\").Inc() </del> } }", "positive_passages": [{"docid": "doc-en-kubernetes-884db7f4f09e6e30f5114a0e6bbb9ebc21f2d686aa6c190d6a4d9470af013127", "text": "One peculiarity may be that we don't actually want the pods to start during these tests because we only want to verify object creation, not the usage of the result, and therefore all pods reference non-existent images. All objects immediately get deleted once the test has verified that they exist, so the timing is probably very different from \"normal\" usage patterns. I suspect that it is more important to create and delete services quickly than it is to have many endpointslices per service.\nI had tried to come up with a script that triggers the problem, without success. That was before I realized that endpointslices are involved. On Monday I can have another look.\nThat was because I thought that (the default) enables foreground deletion. It doesn't, and there's also no option to select it. After explicitly selecting it via curl, the following script failed for me eventually: Output: Note that for the endpointslice is greater than the of its service.", "commid": "kubernetes_issue_91287", "tokennum": 201}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6f69998e3894eca82a651eb706cbd65011151be54fae8e6e7ca99584df895786", "query": "} <ins> func TestFailedParseParamsSummaryHandler(t *testing.T) { fw := newServerTest() defer fw.testHTTPServer.Close() resp, err := http.Post(fw.testHTTPServer.URL+\"/stats/summary\", \"invalid/content/type\", nil) assert.NoError(t, err) defer resp.Body.Close() v, err := ioutil.ReadAll(resp.Body) assert.NoError(t, err) assert.Equal(t, http.StatusInternalServerError, resp.StatusCode) assert.Contains(t, string(v), \"parse form failed\") } </ins> func TestTrimURLPath(t *testing.T) { tests := []struct { path, expected string", "positive_passages": [{"docid": "doc-en-kubernetes-2d86227263004d2306fadc99355cf0a88aac1d38d7e2576116201cd81e3141b9", "text": "What happened: In handler#handleSummary, return value from request.Request.ParseForm() is ignored. What you expected to happen: The error return should be checked.\n/sig node\nHi this seems to be easy to fix. Could I solve this?\nPlease go ahead.", "commid": "kubernetes_issue_90085", "tokennum": 62}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6f75c268445f53b1ad7995aaae0fb1c9d3f101171f2230a27fbb2e472bfd34a2", "query": ") decoder := opts.StorageSerializer.DecoderToVersion( recognizer.NewDecoder(decoders...), <del> runtime.NewMultiGroupVersioner( </del> <ins> runtime.NewCoercingMultiGroupVersioner( </ins> opts.MemoryVersion, schema.GroupKind{Group: opts.MemoryVersion.Group}, schema.GroupKind{Group: opts.StorageVersion.Group},", "positive_passages": [{"docid": "doc-en-kubernetes-7ee140198c665b218e0dfb7e3cd2f2624912887cfcfab5f30828d12c6130aa35", "text": "What happened: Set up a HA cluster with 1.9 and 1.10 API servers (occurs on any apiserver skew boundary where a cohabitating resource's storage version changed groups) Observed errors when modifying workload objects: when modified via the 1.10 server, saw this error in the 1.9 server: when modified via the 1.9 server, saw this error in the 1.10 server: When this error was encountered, all watchers for the resource in question would be dropped and have to re-establish, and the internal watchers feeding the watch cache would drop and re-establish What you expected to happen: Watch events from all supported storage versions are processed correctly How to reproduce it (as minimally and precisely as possible): Start a server from master (for inspectability, store in json). With Create a deployment (e.g. kube-dns in kube-system) Establish a watch via extensions (kubectl get deployments.extensions --all-namespaces -w) Establish a watch via apps (kubectl get --all-namespaces -w) Tail the kube-apiserver log Change the apps/v1 deployment in etcd to extensions/v1beta1: Observer client watches drop and server log errors: Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: /sig api-machinery /cc /priority critical-urgent\nerror is triggered by this returning false: constructed here: the info about expected cohabitating groups is not included in the list of acceptable inputs", "commid": "kubernetes_issue_73478", "tokennum": 368}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6f78eaaccb4ef7dcbfaed81dcce675ab94c42c14912cf5f60e2345021af8632f", "query": "expectedIPFamilies:     nil, expectError:            true, }, <ins> // preferDualStack services should not be updated // to match cluster config if the user didn't change any // ClusterIPs related fields { name:       \"unchanged preferDualStack-1-ClusterUpgraded\", modifyRest: fnMakeDualStackStackIPv4IPv6Allocator, oldSvc: &api.Service{ Spec: api.ServiceSpec{ Type:           api.ServiceTypeClusterIP, ClusterIPs:     []string{\"1.1.1.1\"}, IPFamilies:     []api.IPFamily{api.IPv4Protocol}, IPFamilyPolicy: &preferDualStack, }, }, svc: api.Service{ Spec: api.ServiceSpec{ Type:           api.ServiceTypeClusterIP, ClusterIPs:     []string{\"1.1.1.1\"}, IPFamilies:     []api.IPFamily{api.IPv4Protocol}, IPFamilyPolicy: &preferDualStack, }, }, expectedIPFamilyPolicy: &preferDualStack, expectedIPFamilies:     []api.IPFamily{api.IPv4Protocol}, expectError:            false, }, { name:       \"unchanged preferDualStack-2-ClusterDowngraded\", modifyRest: fnMakeSingleStackIPv4Allocator, oldSvc: &api.Service{ Spec: api.ServiceSpec{ Type:           api.ServiceTypeClusterIP, ClusterIPs:     []string{\"1.1.1.1\", \"2001::1\"}, IPFamilies:     []api.IPFamily{api.IPv4Protocol, api.IPv6Protocol}, IPFamilyPolicy: &preferDualStack, }, }, svc: api.Service{ Spec: api.ServiceSpec{ Type:           api.ServiceTypeClusterIP, ClusterIPs:     []string{\"1.1.1.1\", \"2001::1\"}, IPFamilies:     []api.IPFamily{api.IPv4Protocol, api.IPv6Protocol}, IPFamilyPolicy: &preferDualStack, }, }, expectedIPFamilyPolicy: &preferDualStack, expectedIPFamilies:     []api.IPFamily{api.IPv4Protocol, api.IPv6Protocol}, expectError:            false, }, { name:       \"changed preferDualStack-1 (cluster upgraded)\", modifyRest: fnMakeDualStackStackIPv4IPv6Allocator, oldSvc: &api.Service{ Spec: api.ServiceSpec{ Type:           api.ServiceTypeClusterIP, ClusterIPs:     []string{\"1.1.1.1\"}, IPFamilies:     []api.IPFamily{api.IPv4Protocol}, IPFamilyPolicy: &preferDualStack, }, }, svc: api.Service{ Spec: api.ServiceSpec{ Type:           api.ServiceTypeClusterIP, ClusterIPs:     nil, IPFamilies:     []api.IPFamily{api.IPv4Protocol}, IPFamilyPolicy: &requireDualStack, }, }, expectedIPFamilyPolicy: &requireDualStack, expectedIPFamilies:     []api.IPFamily{api.IPv4Protocol, api.IPv6Protocol}, expectError:            false, }, { name:       \"changed preferDualStack-2-ClusterDowngraded\", modifyRest: fnMakeSingleStackIPv4Allocator, oldSvc: &api.Service{ Spec: api.ServiceSpec{ Type:           api.ServiceTypeClusterIP, ClusterIPs:     []string{\"1.1.1.1\", \"2001::1\"}, IPFamilies:     []api.IPFamily{api.IPv4Protocol, api.IPv6Protocol}, IPFamilyPolicy: &preferDualStack, }, }, svc: api.Service{ Spec: api.ServiceSpec{ Type:           api.ServiceTypeClusterIP, ClusterIPs:     []string{\"1.1.1.1\"}, IPFamilies:     []api.IPFamily{api.IPv4Protocol}, IPFamilyPolicy: &singleStack, }, }, expectedIPFamilyPolicy: &singleStack, expectedIPFamilies:     []api.IPFamily{api.IPv4Protocol}, expectError:            false, }, </ins> } // This func only runs when feature gate is on", "positive_passages": [{"docid": "doc-en-kubernetes-572d0164a11730b1ec949ed970afee14cdb12823b4b7a698fae66a86d82f748e", "text": "1) start with a single stack cluster 2) create a PreferDualStack service 3) configure API server with a 2nd service CIDR 4) Confirm the above service is not dual-stack 5) Add a label to the above service 6) Observe that the service becomes dual-stack I think the correct answer is to have a \"repair loop\" that upgrades (and downgrades!) PreferDualStack Services to match the config. I think this is a GA blocker.\n/triage accepted The current thought is: of type with are special new breed of api objects that I don't think we have any similar precedent in the apis, i could be wrong. Their behavior is tied to how the cluster is configured. Thus their behavior must change as the cluster behavior change. a way the user is stating . If it is cluster then i am good with two ClusterIPs. If it is single stack cluster then I am also good with a single ClusterIP. One can assume that if the user was ok was with getting a additional IP when possible then they must be ok with taking it away when it is no longer possible. Based on the above I believe best course of action is create a new repair loop or piggyback on any of the existing (or better: fix it in rest stack during list and get calls). The new logic takes care of matching to the .\nreproducer and regression test if somebody takes this, feel free to add it\nack - Scheduled to tackle 3rd week of May. Will definitely include that patch.", "commid": "kubernetes_issue_101681", "tokennum": 322}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6f990199a5f356e414a7bdf0fd84db90c4e21203384509c9c30a5824a5a4e147", "query": "} func testZonalFailover(c clientset.Interface, ns string) { <del> nodes := framework.GetReadySchedulableNodesOrDie(c) nodeCount := len(nodes.Items) </del> cloudZones := getTwoRandomZones(c) class := newRegionalStorageClass(ns, cloudZones) claimTemplate := newClaimTemplate(ns)", "positive_passages": [{"docid": "doc-en-kubernetes-07b454797aabeff00bf033fc34fa4c22bd06966ba8574ac0fa868459bacbceea", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: What happened: Testgrid: https://k8s-\n/assign\nThe test's assumption about test parameter is wrong. Previously it assumed the group name is the same across all zones, but they are different in regional clusters. Looking into using node taints as the permanent fix, as suggested by the TODO comment in the test.\nHm I think taint based evictions is still an alpha feature.\nOK. I propose the following solution: Get the zone of Schedule the StatefulSet pod to that zone using node affinity; wait for the pod to run Remove the node affinity from StatefulSet Delete\nCan it be simplified? Schedule the pod Figure out which zone that pod got scheduled in Delete the instance group of that zone\nUnfortunately I don't know of a good way to look up the instance group given the zone, since there could be instance groups from multiple clusters in the same project\nHow about: Schedule the pod Figure out the zone Taint all the nodes in the zone Kill the pod\nTaint with NoSchedule? yeah that sounds good", "commid": "kubernetes_issue_69005", "tokennum": 267}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6f9d7168e4cdc65c3a13a8f908455cc252a7f972fc5c936c8b1fea77c4175487", "query": "if err != nil { return nil, err } <del> minion, err := rs.registry.GetMinion(ctx, minion.Name) </del> <ins> minionName := minion.Name minion, err := rs.registry.GetMinion(ctx, minionName) if err == ErrNotHealty { return rs.toApiMinion(minionName), nil } </ins> if minion == nil { return nil, ErrDoesNotExist }", "positive_passages": [{"docid": "doc-en-kubernetes-30529ae066bc3d8742ebaf2b5d541b47e2e9d65d08ef4d2580a588e88b337906", "text": "apiserver reports creation failure if a node is not ready (unhealthy, or kubelet is not ready), but the api object is already stored in master. extracted from and A short term solution is to have health_registry check node health upon creation, not just on retrieving. Or ignore unhealthy node. A long term solution might fall into the interface revamp\nWhy can't apiserver accept an unhealthy minion.\nWhat's the point of having an unhealthy minion that we'll never be able to use? One reason I can think of is that the minion can later becomes healthy and thus a valid node in k8s. But for now, as we don't have the ability to handle unhealthy node, delegate the responsibility to user makes more sense. However, I admit the title is misleading. What I really what to convey is that kubernetes currently allow registrying unhealthy node, by storing it in RESTStorage. But the create operation reports fail because the node can't pass health checking. I don't think this is the right behavior. We can either return success and do health check later, or return failure and do not store it. (i prefer the latter one for the above reason).\nI tend to think that we should accept unhealthy minions - minions may go in and out of health, or go up and down at any time - so trying ensure health at registration time seems like a fruitless effort since we have to handle the error cases anyway.\nI've no problem with accepting unhealthy minions, and I agree with your point. The real problem here is that the apiserver returns an inconsistent status. For example, if I have an unhealthy minion that I want to registry. From user's perspective, the registration fails, because apiserver returns an error (resource not found). So I retry, but apiserver returns failure again; this time, the error is resource already exists, no matter the minion is healthy or not.\n- yes, we should remove the health check as part of the registration and just report success. agree there is inconsistency.\n+1 On Nov 7, 2014 8:48 AM, \"Derek Carr\" wrote:\nSeems like it's a clients responsibility to warn the user that a node might not be available prior to it being , but the the master's responsibility to assume that all properly specified nodes are reachable before making decisions regarding using a node.", "commid": "kubernetes_issue_2192", "tokennum": 533}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6f9d7168e4cdc65c3a13a8f908455cc252a7f972fc5c936c8b1fea77c4175487", "query": "if err != nil { return nil, err } <del> minion, err := rs.registry.GetMinion(ctx, minion.Name) </del> <ins> minionName := minion.Name minion, err := rs.registry.GetMinion(ctx, minionName) if err == ErrNotHealty { return rs.toApiMinion(minionName), nil } </ins> if minion == nil { return nil, ErrDoesNotExist }", "positive_passages": [{"docid": "doc-en-kubernetes-7568b4abf7e2f804d9652dc70d160bdc940baf27110dcb02262716f8b93b0df2", "text": "There's very little difference between an admin stopping a VM without clearing Kube and adding a node to the cluster prior to it being fully reachable (I think).\n\"clients responsibility\" ? if we enable kubectl to create minions, it would be kubectl who should check if the minion is reachable and complain? I'm not sure what 'client' means. (but I agree 100%, don't report failure adding a minion just because it isn't reachable)\nnode controller plugin should also give warning", "commid": "kubernetes_issue_2192", "tokennum": 117}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6fb88bc4c56cb33d882b20d65a320dc76ea4f7ef97dc5d0bb94ecf52fdc0a233", "query": "defer nodePortOp.Finish() // try set ip families (for missing ip families) <del> if err := rs.tryDefaultValidateServiceClusterIPFields(service); err != nil { </del> <ins> if err := rs.tryDefaultValidateServiceClusterIPFields(oldService, service); err != nil { </ins> return nil, false, err }", "positive_passages": [{"docid": "doc-en-kubernetes-572d0164a11730b1ec949ed970afee14cdb12823b4b7a698fae66a86d82f748e", "text": "1) start with a single stack cluster 2) create a PreferDualStack service 3) configure API server with a 2nd service CIDR 4) Confirm the above service is not dual-stack 5) Add a label to the above service 6) Observe that the service becomes dual-stack I think the correct answer is to have a \"repair loop\" that upgrades (and downgrades!) PreferDualStack Services to match the config. I think this is a GA blocker.\n/triage accepted The current thought is: of type with are special new breed of api objects that I don't think we have any similar precedent in the apis, i could be wrong. Their behavior is tied to how the cluster is configured. Thus their behavior must change as the cluster behavior change. a way the user is stating . If it is cluster then i am good with two ClusterIPs. If it is single stack cluster then I am also good with a single ClusterIP. One can assume that if the user was ok was with getting a additional IP when possible then they must be ok with taking it away when it is no longer possible. Based on the above I believe best course of action is create a new repair loop or piggyback on any of the existing (or better: fix it in rest stack during list and get calls). The new logic takes care of matching to the .\nreproducer and regression test if somebody takes this, feel free to add it\nack - Scheduled to tackle 3rd week of May. Will definitely include that patch.", "commid": "kubernetes_issue_101681", "tokennum": 322}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6fe7f416f4b8a188562232d24f692448e38a164609b657b1c18d57b335e23504", "query": "} /* <del> Testname: allowPrivilegeEscalation unset and uid != 0. Description: Configuring the allowPrivilegeEscalation unset, allows the privilege escalation operation. A container is configured with allowPrivilegeEscalation not specified (nil) and a given uid which is not 0. When the container is run, the container is run using uid=0. This test is marked LinuxOnly since Windows does not support running as UID / GID, or privilege escalation. </del> <ins> Release : v1.15 Testname: Security Context, allowPrivilegeEscalation unset, uid != 0. Description: Configuring the allowPrivilegeEscalation unset, allows the privilege escalation operation. A container is configured with allowPrivilegeEscalation not specified (nil) and a given uid which is not 0. When the container is run, container's output MUST match with expected output verifying container ran with uid=0. This e2e Can not be promoted to Conformance as it is Container Runtime dependent and not all conformant platforms will require this behavior. [LinuxOnly]: This test is marked LinuxOnly since Windows does not support running as UID / GID, or privilege escalation. </ins> */ It(\"should allow privilege escalation when not explicitly set and uid != 0 [LinuxOnly] [NodeConformance]\", func() { podName := \"alpine-nnp-nil-\" + string(uuid.NewUUID())", "positive_passages": [{"docid": "doc-en-kubernetes-f8a45a347ca0a58053d8639059bb6be0a8ec66e1196dbd0290c02922abc9dcd2", "text": "/kind cleanup /area conformance /area test /sig node /sig testing /sig architecture /assign /assign We have a number of tests that only have the tag that may make sense as tests, we should identify whether these tests cases meet (or could meet) the . We should open PR's to promote these if so. I would advise starting with the test/common cases\nGitHub didn't allow me to assign the following users: mgdevstack, mkurylec. Note that only and repo collaborators can be assigned. For more information please see <detailsIn response to : /kind cleanup /area conformance /area test /sig node /sig testing /sig architecture /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\n/assign\nThe tests in test/e2enode don't actually get run as part of Conformance as near as I can tell. If we want to run them as part of conformance, they need to be migrated into test/e2e/common. Some of the tests in e2enode may not be able to be ported over because they assume a level access we don't have in a conformance environment.\nregarding this testcase: [sig-storage] HostPath should support r/w [NodeConformance]: It uses hostPath and privileged=true, to read/write from /tmp folder. Which would you suggest is the best orientation to overcome the privilege mode setting and allow its promotion?\n/assign\nRegarding , the suite runs the test only if the kubelet configuration was required to have the QOS (cgroups-per-qos) enabled. This configuration for the kubelet is selected at the time the cluster is set up. Looking for where this might be configured found: where is set to true. For other settings it is also configured to true. where is set to true. BUT also found where it is mentioned that the flag is no longer available. Questions: would it be ok to promote this test to be conformance, even it can be skipped based on configuration of the cluster? And not supported in the containerized kubelet?\nI would consider cgroups to be an implementation detail that Conformance shouldn't be verifying\nIt uses hostPath and privileged=true, to read/write from /tmp folder.", "commid": "kubernetes_issue_66875", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6fe7f416f4b8a188562232d24f692448e38a164609b657b1c18d57b335e23504", "query": "} /* <del> Testname: allowPrivilegeEscalation unset and uid != 0. Description: Configuring the allowPrivilegeEscalation unset, allows the privilege escalation operation. A container is configured with allowPrivilegeEscalation not specified (nil) and a given uid which is not 0. When the container is run, the container is run using uid=0. This test is marked LinuxOnly since Windows does not support running as UID / GID, or privilege escalation. </del> <ins> Release : v1.15 Testname: Security Context, allowPrivilegeEscalation unset, uid != 0. Description: Configuring the allowPrivilegeEscalation unset, allows the privilege escalation operation. A container is configured with allowPrivilegeEscalation not specified (nil) and a given uid which is not 0. When the container is run, container's output MUST match with expected output verifying container ran with uid=0. This e2e Can not be promoted to Conformance as it is Container Runtime dependent and not all conformant platforms will require this behavior. [LinuxOnly]: This test is marked LinuxOnly since Windows does not support running as UID / GID, or privilege escalation. </ins> */ It(\"should allow privilege escalation when not explicitly set and uid != 0 [LinuxOnly] [NodeConformance]\", func() { podName := \"alpine-nnp-nil-\" + string(uuid.NewUUID())", "positive_passages": [{"docid": "doc-en-kubernetes-b0f7522fd47a7c9f3d30009b5f18d7b37ba2aa8723a4c0ef112b90078054f0fc", "text": "Which would you suggest is the best orientation to overcome the privilege mode setting and allow its promotion? Michelle Au If my understanding is correct, on some platforms, writing to /tmp requires privileged. I don't see a way to to remove that requirement.\nIf my understanding is correct, on some platforms, writing to /tmp requires privileged. I don't see a way to to remove that requirement. Yeah writing to host doesn't seem like a thing we can expect of conformance tests. I wonder if it makes sense to tag this test with something to denote the requirement, ie: I see some tests in test/e2e_node use\nThe hostpath tests in already have a comment explaining this. Maybe the comment should be updated to be more clear that that is the reason why we can't add it to conformance.\nThat's /tmp on the host or in the container filesystem?\n/tmp on the host\nping what else remains to be done before we close this out? I am guessing that we want to close , is there anything beyond that?\nOnce tests under (issue- ) and are promoted we are good to close this issue. Short update for reference- None of [NodeConformance] tests from \"test/e2e_node\" seems eligible for [Conformance] promotion at this moment due to node level dependencies. Remaining [NodeConformance] tests from \"test/e2e\" has following status - Waiting for to be closed and then below tests would be promoted to Conformance Needs to be Promoted Can not be promoted to Conformance as //Slow by design Can not be promoted due to Node level dependency\nIssues 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\n/remove-lifecycle stale\n/lifecycle frozen\n/assign", "commid": "kubernetes_issue_66875", "tokennum": 428}], "negative_passages": []}
{"query_id": "q-en-kubernetes-6ffb573bc7d9b88e021a48c89106216e64dcdadef9e542f1ab1cb4206fe44067", "query": "List<InetAddress> list = new ArrayList<InetAddress>(); String host = \"https://kubernetes.default.cluster.local\"; String serviceName = getEnvOrDefault(\"CASSANDRA_SERVICE\", \"cassandra\"); <del> String path = \"/api/v1/namespaces/default/endpoints/\"; </del> <ins> String podNamespace = getEnvOrDefault(\"POD_NAMESPACE\", \"default\"); String path = String.format(\"/api/v1/namespaces/%s/endpoints/\", podNamespace); </ins> try { String token = getServiceAccountToken();", "positive_passages": [{"docid": "doc-en-kubernetes-600b05087b3e5a02baef82de4ad7a72820fecd2de58582bba171390ab13fae8d", "text": "The namespace seems to be hard coded :\ncc:\nThanks. We can improve it after v1 release.", "commid": "kubernetes_issue_10034", "tokennum": 22}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7001b4e7de9fcd7a14303e7d61103f1939842a93312ce4b003e47f60831115ef", "query": "cachedCreds *credentials exp         time.Time <del> onRotate func() </del> <ins> onRotateList []func() </ins> } type credentials struct {", "positive_passages": [{"docid": "doc-en-kubernetes-d5f405b98ac26e68bb52a403345cda18a0b690bbcb8385b5ec06372b302c6e2d", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Data race in client-go with below sample code: Data race: What you expected to happen: No data race How to reproduce it (as minimally and precisely as possible): Using above given sample code Kubernetes version (use ):Cloud provider or hardware configuration:OS (e.g: ): OSX\n/sig api-machinery\nI'd like to take it. /assign\n/remove-sig api-machinery /sig auth cli\nBug triage for release 1.17 here. Since this issue has been tagged for the milestone, we would like to check it's status. Code freeze is on Nov. 14. Will this issue be resolved before then?\nAnother reminder here that code freeze is in less than two weeks (Nov. 14). We will need to move this issue out of the milestone if isn't going to be resolved before then.", "commid": "kubernetes_issue_80269", "tokennum": 239}], "negative_passages": []}
{"query_id": "q-en-kubernetes-70354507a91d89d53a73042f2a709fabb522103eb0995e8c2e9360ad551bc889", "query": "#     sleep 4 #     i=$[$i+1] #   done <del> apiVersion: v1beta1 </del> <ins> apiVersion: v1beta3 </ins> kind: Pod <del> id: synthetic-logger-0.25lps-pod desiredState: manifest: version: v1beta1 id: synth-logger-0.25lps containers: - name: synth-lgr image: ubuntu:14.04 command: [\"bash\", \"-c\", \"i=\"0\"; while true; do echo -n \"`hostname`: $i: \"; date --rfc-3339 ns; sleep 4; i=$[$i+1]; done\"] labels: name: synth-logging-source </del>  No newline at end of file <ins> metadata: labels: name: synth-logging-source name: synthetic-logger-0.25lps-pod spec: containers: - args: - bash - -c - 'i=\"0\"; while true; do echo -n \"`hostname`: $i: \"; date --rfc-3339 ns; sleep 4; i=$[$i+1]; done' image: ubuntu:14.04 name: synth-lgr </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-bc75029de49571476e249812075ff7ffff85fb8014f5cfe5e32228962baa98b2", "text": "Hi , I followed the instructions in examples/logging-demo, and there was no \"external IP\" field for elasticsearch-logging or kibana-logging, as shown below: I start up my cluster via cluster/kube- Did I miss something or is it a bug? Thanks.\nCorrect. This demo does not create an ELB so there is no external IP address. Access is via service proxy at the master. Type: and you should see the URLs for Elasticsearch and Kibana.\nplease let us know whether: a. Satnam's comment resolves your issue b. the demo should be updated to prevent this misunderstanding c. the issue isn't resolved Thank you!\nYes, Satnam's comment resolve the issue. I updated the demo in .\nAwesome, thanks for sending the patch! We'll discuss there. Always fantastic to have docs updated regularly by folks trying them.", "commid": "kubernetes_issue_7818", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-70376548b6529ba9d479934c8b6b7ad2caec983bd10145caca44aa7ed7503d24", "query": "type PredicateFailureError struct { PredicateName string <ins> PredicateDesc string </ins> } <del> func newPredicateFailureError(predicateName string) *PredicateFailureError { return &PredicateFailureError{PredicateName: predicateName} </del> <ins> func newPredicateFailureError(predicateName, predicateDesc string) *PredicateFailureError { return &PredicateFailureError{PredicateName: predicateName, PredicateDesc: predicateDesc} </ins> } func (e *PredicateFailureError) Error() string {", "positive_passages": [{"docid": "doc-en-kubernetes-10c13016eb5239afc7a330cfdab91dbf78232a49f2993f71669df735dbb939e1", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature The is not user friendly. There has been to make it better, but we still print in the pending message. We should change these errors to a more human readable message. For example, should be changed to something like . /sig scheduling", "commid": "kubernetes_issue_58546", "tokennum": 91}], "negative_passages": []}
{"query_id": "q-en-kubernetes-703eae7639ee028d9144cee21a508cb4081d7ec398c3c4598275e7bcd9f63876", "query": "<del> { \"kind\": \"ValidatingAdmissionPolicy\", \"apiVersion\": \"admissionregistration.k8s.io/v1alpha1\", \"metadata\": { \"name\": \"nameValue\", \"generateName\": \"generateNameValue\", \"namespace\": \"namespaceValue\", \"selfLink\": \"selfLinkValue\", \"uid\": \"uidValue\", \"resourceVersion\": \"resourceVersionValue\", \"generation\": 7, \"creationTimestamp\": \"2008-01-01T01:01:01Z\", \"deletionTimestamp\": \"2009-01-01T01:01:01Z\", \"deletionGracePeriodSeconds\": 10, \"labels\": { \"labelsKey\": \"labelsValue\" }, \"annotations\": { \"annotationsKey\": \"annotationsValue\" }, \"ownerReferences\": [ { \"apiVersion\": \"apiVersionValue\", \"kind\": \"kindValue\", \"name\": \"nameValue\", \"uid\": \"uidValue\", \"controller\": true, \"blockOwnerDeletion\": true } ], \"finalizers\": [ \"finalizersValue\" ], \"managedFields\": [ { \"manager\": \"managerValue\", \"operation\": \"operationValue\", \"apiVersion\": \"apiVersionValue\", \"time\": \"2004-01-01T01:01:01Z\", \"fieldsType\": \"fieldsTypeValue\", \"fieldsV1\": {}, \"subresource\": \"subresourceValue\" } ] }, \"spec\": { \"paramKind\": { \"apiVersion\": \"apiVersionValue\", \"kind\": \"kindValue\" }, \"matchConstraints\": { \"namespaceSelector\": { \"matchLabels\": { \"matchLabelsKey\": \"matchLabelsValue\" }, \"matchExpressions\": [ { \"key\": \"keyValue\", \"operator\": \"operatorValue\", \"values\": [ \"valuesValue\" ] } ] }, \"objectSelector\": { \"matchLabels\": { \"matchLabelsKey\": \"matchLabelsValue\" }, \"matchExpressions\": [ { \"key\": \"keyValue\", \"operator\": \"operatorValue\", \"values\": [ \"valuesValue\" ] } ] }, \"resourceRules\": [ { \"resourceNames\": [ \"resourceNamesValue\" ], \"operations\": [ \"operationsValue\" ], \"apiGroups\": [ \"apiGroupsValue\" ], \"apiVersions\": [ \"apiVersionsValue\" ], \"resources\": [ \"resourcesValue\" ], \"scope\": \"scopeValue\" } ], \"excludeResourceRules\": [ { \"resourceNames\": [ \"resourceNamesValue\" ], \"operations\": [ \"operationsValue\" ], \"apiGroups\": [ \"apiGroupsValue\" ], \"apiVersions\": [ \"apiVersionsValue\" ], \"resources\": [ \"resourcesValue\" ], \"scope\": \"scopeValue\" } ], \"matchPolicy\": \"matchPolicyValue\" }, \"validations\": [ { \"expression\": \"expressionValue\", \"message\": \"messageValue\", \"reason\": \"reasonValue\", \"messageExpression\": \"messageExpressionValue\" } ], \"failurePolicy\": \"failurePolicyValue\", \"auditAnnotations\": [ { \"key\": \"keyValue\", \"valueExpression\": \"valueExpressionValue\" } ], \"matchConditions\": [ { \"name\": \"nameValue\", \"expression\": \"expressionValue\" } ], \"variables\": null }, \"status\": { \"observedGeneration\": 1, \"typeChecking\": { \"expressionWarnings\": [ { \"fieldRef\": \"fieldRefValue\", \"warning\": \"warningValue\" } ] }, \"conditions\": [ { \"type\": \"typeValue\", \"status\": \"statusValue\", \"observedGeneration\": 3, \"lastTransitionTime\": \"2004-01-01T01:01:01Z\", \"reason\": \"reasonValue\", \"message\": \"messageValue\" } ] } } </del>  No newline at end of file", "positive_passages": [{"docid": "doc-en-kubernetes-f7dbb3a7bd33f39ed155e3c1ad6b8c55c94743d34cf8c863dee73b5ba5ef4403", "text": "spec.variables should be marked omitempty. I'm trying to create a validating admission policy that uses in v1.27 as follows: I'm setting : to \"Strict\" in CreateOptions so that the server will reject requests with unknown fields but it complains that the don't exist in v1.27 and it does make sense because this field was introduced in v1.28: I'm using a 1.28 client.\n/sig api-machinery\n/assign\n/assign /triage accepted\nThanks for raising this! /cc", "commid": "kubernetes_issue_120491", "tokennum": 117}], "negative_passages": []}
{"query_id": "q-en-kubernetes-704a8be13a73aedfaf3ccb25bc169c7ca5fde83eb3b03a149411e024fdfc9a68", "query": "awsServices := newMockedFakeAWSServices(TestClusterId) c, _ := newAWSCloud(strings.NewReader(\"[global]\"), awsServices) <del> sg1 := \"sg-000001\" sg2 := \"sg-000002\" </del> <ins> sg1 := map[string]string{ServiceAnnotationLoadBalancerExtraSecurityGroups: \"sg-000001\"} sg2 := map[string]string{ServiceAnnotationLoadBalancerExtraSecurityGroups: \"sg-000002\"} sg3 := map[string]string{ServiceAnnotationLoadBalancerExtraSecurityGroups: \"sg-000001, sg-000002\"} </ins> tests := []struct { name string <del> extraSGsAnnotation string expectedSGs        []string </del> <ins> annotations map[string]string expectedSGs []string </ins> }{ <del> {\"No extra SG annotation\", \"\", []string{}}, {\"Empty extra SGs specified\", \", ,,\", []string{}}, {\"SG specified\", sg1, []string{sg1}}, {\"Multiple SGs specified\", fmt.Sprintf(\"%s, %s\", sg1, sg2), []string{sg1, sg2}}, </del> <ins> {\"No extra SG annotation\", map[string]string{}, []string{}}, {\"Empty extra SGs specified\", map[string]string{ServiceAnnotationLoadBalancerExtraSecurityGroups: \", ,,\"}, []string{}}, {\"SG specified\", sg1, []string{sg1[ServiceAnnotationLoadBalancerExtraSecurityGroups]}}, {\"Multiple SGs specified\", sg3, []string{sg1[ServiceAnnotationLoadBalancerExtraSecurityGroups], sg2[ServiceAnnotationLoadBalancerExtraSecurityGroups]}}, </ins> } awsServices.ec2.(*MockedFakeEC2).expectDescribeSecurityGroups(TestClusterId, \"k8s-elb-aid\", \"cluster.test\")", "positive_passages": [{"docid": "doc-en-kubernetes-f0769863fab39b633cda95f4d162dbe6bf42638a791c88a2a3acb41bb68633b3", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature /sig aws What happened: In k8s 1.7, when creating a service of type LoadBalancer, K8S creates the ELB and a Security Group for it. For these resources, it adds a tag, constructed dynamically, containing the cluster id: \"${cluster_id}\" with the value \"true\" What you expected to happen: We'd like to have also a statically named tag , as it was in 1.5 (\"KubernetesCluster\") with the value of the cluster id. How to reproduce it (as minimally and precisely as possible): Running on AWS cloud provider, create a service of type LoadBalancer. Anything else we need to know?: The reason for what we expect is that we have tight security constraints that require us to fine tune the IAM policies for the Instance profiles that the controllers use. With a statically named tag we were able, in 1.5, to restrict the permissions in the IAM policy to act only on the k8s managed resources (ELBs, security groups). Here is the relevant part of the IAM policy: With a dynamically named tag we are not able to do this any more as AWS IAM doesn't support something like: We are sharing the Instance Profiles among different k8s clusters, hence the \"\" in the value of the tag. Environment: Kubernetes version (use ):Cloud provider or hardware configuration*: AWS OS (e.g. from /etc/os-release):Kernel (e.g. ):Install tools: kube-aws Others:\nReiterating the mentions to trigger a notification: <detailsIn response to : <!-- This form is for bug reports and feature requests ONLY! -- /sig aws In k8s 1.7, when creating a service of type LoadBalancer, K8S creates the ELB and a Security Group for it. For these resources, it adds a tag, constructed dynamically, containing the cluster id: \"${cluster_id}\" with the value \"true\" We'd like to have also a statically named tag , as it was in 1.5 (\"KubernetesCluster\") with the value of the cluster id. Running on AWS cloud provider, create a service of type LoadBalancer.", "commid": "kubernetes_issue_53489", "tokennum": 543}], "negative_passages": []}
{"query_id": "q-en-kubernetes-704a8be13a73aedfaf3ccb25bc169c7ca5fde83eb3b03a149411e024fdfc9a68", "query": "awsServices := newMockedFakeAWSServices(TestClusterId) c, _ := newAWSCloud(strings.NewReader(\"[global]\"), awsServices) <del> sg1 := \"sg-000001\" sg2 := \"sg-000002\" </del> <ins> sg1 := map[string]string{ServiceAnnotationLoadBalancerExtraSecurityGroups: \"sg-000001\"} sg2 := map[string]string{ServiceAnnotationLoadBalancerExtraSecurityGroups: \"sg-000002\"} sg3 := map[string]string{ServiceAnnotationLoadBalancerExtraSecurityGroups: \"sg-000001, sg-000002\"} </ins> tests := []struct { name string <del> extraSGsAnnotation string expectedSGs        []string </del> <ins> annotations map[string]string expectedSGs []string </ins> }{ <del> {\"No extra SG annotation\", \"\", []string{}}, {\"Empty extra SGs specified\", \", ,,\", []string{}}, {\"SG specified\", sg1, []string{sg1}}, {\"Multiple SGs specified\", fmt.Sprintf(\"%s, %s\", sg1, sg2), []string{sg1, sg2}}, </del> <ins> {\"No extra SG annotation\", map[string]string{}, []string{}}, {\"Empty extra SGs specified\", map[string]string{ServiceAnnotationLoadBalancerExtraSecurityGroups: \", ,,\"}, []string{}}, {\"SG specified\", sg1, []string{sg1[ServiceAnnotationLoadBalancerExtraSecurityGroups]}}, {\"Multiple SGs specified\", sg3, []string{sg1[ServiceAnnotationLoadBalancerExtraSecurityGroups], sg2[ServiceAnnotationLoadBalancerExtraSecurityGroups]}}, </ins> } awsServices.ec2.(*MockedFakeEC2).expectDescribeSecurityGroups(TestClusterId, \"k8s-elb-aid\", \"cluster.test\")", "positive_passages": [{"docid": "doc-en-kubernetes-a01a3c41e631760f28b69af73c7e0688234151a20f7dd4b67642a3c81f6b4dfa", "text": "The reason for what we expect is that we have tight security constraints that require us to fine tune the IAM policies for the Instance profiles that the controllers use. With a statically named tag we were able, in 1.5, to restrict the permissions in the IAM policy to act only on the k8s managed resources (ELBs, security groups). Here is the relevant part of the IAM policy: Environment: Kubernetes version (use ):OS (e.g. from /etc/os-release):Others: </details\nI believe they are moving away from the tag since there are many resources that can be shared by multiple clusters. could you use an annotation?\nWe removed the condition in roles in the end. Thank you for your suggestion.\nThat annotation affects the ELB but not any security groups that are created. can you please reopen this? You reported a real issue, and even if it no longer affects you, it needs to be tracked and fixed.\nIndeed, this might be a feature that someone else would need.\nIn fact, this is a feature I need!\nFood for thought: should we propagate the tags on the ELB to the SG, or should we introduce an annotation for the SG specifically?", "commid": "kubernetes_issue_53489", "tokennum": 265}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7059c440c3965c29ea70083ce4cb22bf6dc3d6c975fb090ef222c20c5eccca35", "query": "}) } } <ins> func TestConvertToAPIContainerStatusesDataRace(t *testing.T) { pod := podWithUIDNameNs(\"12345\", \"test-pod\", \"test-namespace\") testTimestamp := time.Unix(123456789, 987654321) criStatus := &kubecontainer.PodStatus{ ID:        pod.UID, Name:      pod.Name, Namespace: pod.Namespace, ContainerStatuses: []*kubecontainer.Status{ {Name: \"containerA\", CreatedAt: testTimestamp}, {Name: \"containerB\", CreatedAt: testTimestamp.Add(1)}, }, } testKubelet := newTestKubelet(t, false) defer testKubelet.Cleanup() kl := testKubelet.kubelet // convertToAPIContainerStatuses is purely transformative and shouldn't alter the state of the kubelet // as there are no synchronisation events in that function (no locks, no channels, ...) each test routine // should have its own vector clock increased independently. Golang race detector uses pure happens-before // detection, so would catch a race condition consistently, despite only spawning 2 goroutines for i := 0; i < 2; i++ { go func() { kl.convertToAPIContainerStatuses(pod, criStatus, []v1.ContainerStatus{}, []v1.Container{}, false, false) }() } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-4510e09c6fe68ed5e12ffcf7126f6af8b2755c8c7c2f631bec51ed41fca52919", "text": "What happened: One pod stuck at CreateContainerError and can't get recovered automatically. Kubelet log shows that the requested name (let's say Container2) is already in use. shows the Container2 Running, and it's created before Container1 This should never happen. How to reproduce it (as minimally and precisely as possible): I wish i knew. Anything else we need to know?: I know this can be caused by time shifting, but I didn't find any time shifting sign in system log and chrony log, and there is no rebooting between the create timestamp of Container1 and Container2, so this should be caused by something else. This happens intermittently in our env, like 3 times in half a year, and I didn't find any ime shifting sign each time. Environment: Kubernetes version (use ): Client Version: version.Info{Major:\"1\", Minor:\"15\", GitVersion:\"v1.15.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2019-11-13T11:20:18Z\", GoVersion:\"go1.12.12\", Compiler:\"gc\", Platform:\"linux/amd64\"} Server Version: version.Info{Major:\"1\", Minor:\"15\", GitVersion:\"v1.15.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2020-08-28T11:18:26Z\", GoVersion:\"go1.12.12\", Compiler:\"gc\", Platform:\"linux/amd64\"} Cloud provider or hardware configuration: OS (e.g: ): CentOS Linux release 7.5.1804 (Core) Kernel (e.g. ): Linux node-1 3.10.0-957.21.3.el7.x8664 SMP Wed Jul 17 06:57:50 UTC 2019 x8664 x8664 x86_64 GNU/Linux Install tools: kubeadm Network plugin and version (if this is a network-related bug): Others:\n/sig node\nAny update on this issue, we are also facing the same issue. EKS version : 1.14.9 Docker version: 19.03.6-ce AWS CNI: 1.6.2 Intermittently we are also facing this , what might the issue, could please guide us here? Below are the kubelet logs. )\"", "commid": "kubernetes_issue_94557", "tokennum": 571}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7059c440c3965c29ea70083ce4cb22bf6dc3d6c975fb090ef222c20c5eccca35", "query": "}) } } <ins> func TestConvertToAPIContainerStatusesDataRace(t *testing.T) { pod := podWithUIDNameNs(\"12345\", \"test-pod\", \"test-namespace\") testTimestamp := time.Unix(123456789, 987654321) criStatus := &kubecontainer.PodStatus{ ID:        pod.UID, Name:      pod.Name, Namespace: pod.Namespace, ContainerStatuses: []*kubecontainer.Status{ {Name: \"containerA\", CreatedAt: testTimestamp}, {Name: \"containerB\", CreatedAt: testTimestamp.Add(1)}, }, } testKubelet := newTestKubelet(t, false) defer testKubelet.Cleanup() kl := testKubelet.kubelet // convertToAPIContainerStatuses is purely transformative and shouldn't alter the state of the kubelet // as there are no synchronisation events in that function (no locks, no channels, ...) each test routine // should have its own vector clock increased independently. Golang race detector uses pure happens-before // detection, so would catch a race condition consistently, despite only spawning 2 goroutines for i := 0; i < 2; i++ { go func() { kl.convertToAPIContainerStatuses(pod, criStatus, []v1.ContainerStatus{}, []v1.Container{}, false, false) }() } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-cf3a33a19ef0552fe6ccd0d8ccfc3a21fead851f6c57fd16801184b4e1e277da", "text": "with CreatePodSandboxError: \"CreatePodSandbox for pod \"-f0fe-11ea-9872-)\" failed: rpc error: code = Unknown desc = failed to create a sandbox for pod \"aiqx-server-dep--b9lmv\": operation timeout: context deadline exceeded\" Sep 07 11:40:40 kubelet[2899]: W0907 11:40:40. 2899 ] No ref for container \"docker://7b9c86b529530f15d941f8e68973a202c8f348ab5db864a8371e8c82ddbf9dc4\" (r(-e845-11ea-bd96-) Sep 07 11:40:43 kubelet[2899]: W0907 11:40:43. 2899 ] Unable to create pod sandbox due to conflict. Attempting to remove sandbox \"a73bd9a03d56bc7855e4e89e163e13c5e7173397f10edcc200fb686e1b6885c8\" Sep 07 11:40:43 kubelet[2899]: E0907 11:40:43. 2899 ] Failed to remove the conflicting container \"a73bd9a03d56bc7855e4e89e163e13c5e7173397f10edcc200fb686e1b6885c8\": Error: No such container: a73bd9a03d56bc7855e4e89e163e13c5e7173397f10edcc200fb686e1b6885c8\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_94557", "tokennum": 554}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7059c440c3965c29ea70083ce4cb22bf6dc3d6c975fb090ef222c20c5eccca35", "query": "}) } } <ins> func TestConvertToAPIContainerStatusesDataRace(t *testing.T) { pod := podWithUIDNameNs(\"12345\", \"test-pod\", \"test-namespace\") testTimestamp := time.Unix(123456789, 987654321) criStatus := &kubecontainer.PodStatus{ ID:        pod.UID, Name:      pod.Name, Namespace: pod.Namespace, ContainerStatuses: []*kubecontainer.Status{ {Name: \"containerA\", CreatedAt: testTimestamp}, {Name: \"containerB\", CreatedAt: testTimestamp.Add(1)}, }, } testKubelet := newTestKubelet(t, false) defer testKubelet.Cleanup() kl := testKubelet.kubelet // convertToAPIContainerStatuses is purely transformative and shouldn't alter the state of the kubelet // as there are no synchronisation events in that function (no locks, no channels, ...) each test routine // should have its own vector clock increased independently. Golang race detector uses pure happens-before // detection, so would catch a race condition consistently, despite only spawning 2 goroutines for i := 0; i < 2; i++ { go func() { kl.convertToAPIContainerStatuses(pod, criStatus, []v1.ContainerStatus{}, []v1.Container{}, false, false) }() } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-af4ac4b9e185e9334a90bdc75507d53790e8bdc2018fef7b4f1e5e30a35b49e6", "text": "/lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /close\nClosing 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", "commid": "kubernetes_issue_94557", "tokennum": 110}], "negative_passages": []}
{"query_id": "q-en-kubernetes-706d7fbe949d5c2195c9b64b306883ba14440c8c39f7cbcee45f3f6e23d15a98", "query": "mountPath: /device-plugin - name: dev mountPath: /dev <ins> updateStrategy: type: RollingUpdate </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-81aeaa915020279b8f6f88fad69c7f8c675b68383da3729b9f05c07134ed836b", "text": "This issue is here to satisfy PR requirements of issue association. A lot of times we need to do version bumps for minor bug fixes that don't deserve a separate issue in the kubernetes/kubernetes repo. /kind bug /sig node\n/lifecycle frozen\nall the linked PRs are emrged and no activity since more than 3 years /close\nClosing this issue. <detailsIn response to : all the linked PRs are emrged and no activity since more than 3 years /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", "commid": "kubernetes_issue_57125", "tokennum": 141}], "negative_passages": []}
{"query_id": "q-en-kubernetes-70bedf886735a6690ee554ef0152fe083d460fba3ef3e01e9214f693adabb525", "query": "{ \"ImportPath\": \"github.com/GoogleCloudPlatform/kubernetes\", <del> \"GoVersion\": \"go1.3\", </del> <ins> \"GoVersion\": \"go1.4.1\", </ins> \"Packages\": [ \"./...\" ],", "positive_passages": [{"docid": "doc-en-kubernetes-03a1b5e4c6941c765bd244d07f4ddb990e16cb6fe45dcc8cf0eeb5fc4aec846d", "text": "committed a changed version of go into godeps. Was this deliberate? I don't see any discussion of it ( I've almost done this by mistake as well, so I'm inclined to think it was just an oversight. (I think this is giving me errors building, but I'm not yet 100% sure this is the cause)\nHmm, this is a good point. It does look to be accidental. I don't know. I think and would have context though I believe they are out\u2014 do you know offhand whether this is probably an accident? I guess were talking specifically about in the .\nI believe it's an accident.\nThanks, The linked PR should fix this (assuming I don't have to do anything else with Godeps).\nThis was almost certainly an accident. Whenever I've updated godeps it's changed automatically to 1.3 and I've had to adjust it back manually.\nActually, jeff lowdermilk was super helpful and showed me how to update the deps on this PR. it was his commit which I merged into my PR, so not sure it it was accidental or not. Fortunately, now that k8petstore is in the go build, we will know if it breaks anything when you revert the version back. Thanks for noticing this. , Alex Robinson wrote:", "commid": "kubernetes_issue_5708", "tokennum": 280}], "negative_passages": []}
{"query_id": "q-en-kubernetes-70f42fd3a53891408b7ade8b6f57203a1ee731c2d99e832a9c3effe6886111a7", "query": "import ( \"context\" <ins> \"fmt\" </ins> \"time\" v1 \"k8s.io/api/core/v1\"", "positive_passages": [{"docid": "doc-en-kubernetes-e89d62bf4b636217c9a329c55c70299ddc99e1e546e8bf63873df452671a65c2", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: aks-engine-azure-windows-master-containerd-serial-slow Which test(s) are failing: [sig-windows] [Feature:Windows] Kubelet-Stats [Serial] Kubelet stats collection for Windows nodes when running 10 pods should return within 10 seconds Since when has it been failing: Unknown. Testgrid link: Reason for failure: The test spawns 10 pods with the same pod name, which contains multiple containers with the same container name. Because of this, the test fails. Logs: Anything else we need to know:\n/sig windows These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by vllry. \u200d", "commid": "kubernetes_issue_91677", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-70fb071781e5487b572a0df0bc68aabf0d289955a1de72b90e6e73adc8af62e5", "query": "func (m *manager) UpdatePodStatus(podUID types.UID, podStatus *v1.PodStatus) { for i, c := range podStatus.ContainerStatuses { <del> var ready bool if c.State.Running == nil { ready = false } else if result, ok := m.readinessManager.Get(kubecontainer.ParseContainerID(c.ContainerID)); ok { ready = result == results.Success } else { // The check whether there is a probe which hasn't run yet. _, exists := m.getWorker(podUID, c.Name, readiness) ready = !exists } podStatus.ContainerStatuses[i].Ready = ready </del> var started bool if c.State.Running == nil { started = false", "positive_passages": [{"docid": "doc-en-kubernetes-1a4f2a91f513677e5b237ae427502f2b96572c4f540bf286aa5c4a8d97d94caf", "text": "If I have probe and then all good. Previous version of the pod is terminated after startup probe success, but if wasn't specified the pod becomes ready immediately. It would be nice to add new state (for example starting) which would have pods until a is successful. Also, it would mean that container not ready for connection. Thank you for attention!\n/sig cluster-lifecycle\n/remove-sig cluster-lifecycle /sig apps try asking in #kubernetes-users on k8s slack.\nthey are silent in the chat. Who is involved in the development of startup probe?\ni think this topic better fits SIG Node. try asking in their channel on slack , but be patient ;) /sig node /remove-sig apps\nThose labels are not set on the issue: <detailsIn response to : i think this topic better fits SIG Node. /sig node /remove-sig apps </details\nI think this is a feature request, not support, so I changed labels. On its face it SEEMS reasonable, but I am not close enough to the details to say. This is definitely sig-node.\nAdding a new pod lifecycle state has been determined to be intractable in the past. Is the proposed change keeping the pod in !Ready until the first success from ?\nWhere do you usually discuss this? Just wondering. Yes, I want that pod considered not ready until will not be successful. If readiness probe doesn't present then a pod can become ready. How can a pod be ready if it is not running?\nhow long wait?\nLooking at this issue, I can confirm it, at least superficially - a pod with a perma-failing is \"ready\" if there is no readinessGate defined and \"not ready\" if it is defined. The question I have is whether we think that is \"correct\" or not? Initially I thought it was correct, but the more I think about it the less convinced I am. If I have defined a startupProbe and it is not passing, my app should not be ready. Does anyone disagree?\nAlso, the app should not be ready in status. It's funny, but without a readiness probe, pods in the final state have the status ready and accept requests. This is unexpected.\nWhether a pod is ready while terminating is an entirely different question, IMO.", "commid": "kubernetes_issue_89995", "tokennum": 488}], "negative_passages": []}
{"query_id": "q-en-kubernetes-70fb071781e5487b572a0df0bc68aabf0d289955a1de72b90e6e73adc8af62e5", "query": "func (m *manager) UpdatePodStatus(podUID types.UID, podStatus *v1.PodStatus) { for i, c := range podStatus.ContainerStatuses { <del> var ready bool if c.State.Running == nil { ready = false } else if result, ok := m.readinessManager.Get(kubecontainer.ParseContainerID(c.ContainerID)); ok { ready = result == results.Success } else { // The check whether there is a probe which hasn't run yet. _, exists := m.getWorker(podUID, c.Name, readiness) ready = !exists } podStatus.ContainerStatuses[i].Ready = ready </del> var started bool if c.State.Running == nil { started = false", "positive_passages": [{"docid": "doc-en-kubernetes-3f629dda069dd58c9ce26e66996c26ea4a1a35ac59c48a136ee3c51de61527c3", "text": "Apps that server network traffic probably need to \"drain\" and to do that they need to stay \"ready\" for a while as upstream LBs de-program. Let's not conflate issues, please.\nThe fix seems simple - lets see what CI says.\nSorry, I don't spend much time on slack... you could have checked the release notes in 1.18 ;-) Tim's fix seems good, thanks!\n/reopen Until we merge all related PRs...\nReopened this issue. <detailsIn response to : /reopen Until we merge all related PRs... 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\nAll merged. /close\nClosing this issue. <detailsIn response to : All merged. /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", "commid": "kubernetes_issue_89995", "tokennum": 213}], "negative_passages": []}
{"query_id": "q-en-kubernetes-71493df9dd735e64b867a28c12062f31ef4528f5bd3902906deada4ebb2e3741", "query": "t.Errorf(\"Invalid content read from cache %q\", string(content)) } } <ins> func TestCacheRoundTripperPathPerm(t *testing.T) { assert := assert.New(t) rt := &testRoundTripper{} cacheDir, err := ioutil.TempDir(\"\", \"cache-rt\") os.RemoveAll(cacheDir) defer os.RemoveAll(cacheDir) if err != nil { t.Fatal(err) } cache := newCacheRoundTripper(cacheDir, rt) // First call, caches the response req := &http.Request{ Method: http.MethodGet, URL:    &url.URL{Host: \"localhost\"}, } rt.Response = &http.Response{ Header:     http.Header{\"ETag\": []string{`\"123456\"`}}, Body:       ioutil.NopCloser(bytes.NewReader([]byte(\"Content\"))), StatusCode: http.StatusOK, } resp, err := cache.RoundTrip(req) if err != nil { t.Fatal(err) } content, err := ioutil.ReadAll(resp.Body) if err != nil { t.Fatal(err) } if string(content) != \"Content\" { t.Errorf(`Expected Body to be \"Content\", got %q`, string(content)) } err = filepath.Walk(cacheDir, func(path string, info os.FileInfo, err error) error { if err != nil { return err } if info.IsDir() { assert.Equal(os.FileMode(0750), info.Mode().Perm()) } else { assert.Equal(os.FileMode(0660), info.Mode().Perm()) } return nil }) assert.NoError(err) } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-30e07950978ed617c12104c8342559dfe477718ba7eb61f98c21f95bb37c1439", "text": "In kubectl v1.8.0+, schema info is cached in the location specified by (defaulting to ), written with world-writeable permissions (rw-rw-rw-). If is specified and pointed at a different location accessible to other users/groups, the written files may be modified by other users/groups and disrupt the kubectl invocation. CVSS score: CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N (3.3, low) What versions are affected? kubectl v1.8.0+ What configurations are affected? Invocations that point at world-writeable locations Impact Malformed responses written to the cache directory can disrupt the kubectl invocation Workaround Use the default location in the $HOME directory or point it at a directory that is only accessible to desired users/groups. (original description follows) ==== What happened: The files inside of \".kube/http-cache\" are world writeable (rw-rw-rw-). While the default for these files appears to be the home directory, using the \"--cache-dir\" flag could put these files into a place where world writeable files would allow any user / process to modify the cache files. Modification of the cache files could influence the kubectl utility in a negative way for other users. What you expected to happen: Apply stricter file permissions to the http-cache files. How to reproduce it (as minimally and precisely as possible): Run any generic kubectl command which is successful and then list the cache directory $ kubectl get pods --all-namespaces $ ls -la Anything else we need to know?", "commid": "kubernetes_issue_76676", "tokennum": 398}], "negative_passages": []}
{"query_id": "q-en-kubernetes-71493df9dd735e64b867a28c12062f31ef4528f5bd3902906deada4ebb2e3741", "query": "t.Errorf(\"Invalid content read from cache %q\", string(content)) } } <ins> func TestCacheRoundTripperPathPerm(t *testing.T) { assert := assert.New(t) rt := &testRoundTripper{} cacheDir, err := ioutil.TempDir(\"\", \"cache-rt\") os.RemoveAll(cacheDir) defer os.RemoveAll(cacheDir) if err != nil { t.Fatal(err) } cache := newCacheRoundTripper(cacheDir, rt) // First call, caches the response req := &http.Request{ Method: http.MethodGet, URL:    &url.URL{Host: \"localhost\"}, } rt.Response = &http.Response{ Header:     http.Header{\"ETag\": []string{`\"123456\"`}}, Body:       ioutil.NopCloser(bytes.NewReader([]byte(\"Content\"))), StatusCode: http.StatusOK, } resp, err := cache.RoundTrip(req) if err != nil { t.Fatal(err) } content, err := ioutil.ReadAll(resp.Body) if err != nil { t.Fatal(err) } if string(content) != \"Content\" { t.Errorf(`Expected Body to be \"Content\", got %q`, string(content)) } err = filepath.Walk(cacheDir, func(path string, info os.FileInfo, err error) error { if err != nil { return err } if info.IsDir() { assert.Equal(os.FileMode(0750), info.Mode().Perm()) } else { assert.Equal(os.FileMode(0660), info.Mode().Perm()) } return nil }) assert.NoError(err) } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-03c8940a04bf023e0d3632a105949b7e85efda694ffafea56ecb99998a766122", "text": ": I estimate this is a low severity security issue with a CVSS score of \"3.3 / CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N\" - Environment: Linux Kubernetes version (use kubectl version):Client Version: version.Info{Major:\"1\", Minor:\"12\", GitVersion:\"v1.12.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2019-02-26T12:49:28Z\", GoVersion:\"go1.10.8\", Compiler:\"gc\", Platform:\"linux/amd64\"} Server Version: version.Info{Major:\"1\", Minor:\"12\", GitVersion:\"v1.12.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2019-02-26T12:49:28Z\", GoVersion:\"go1.10.8\", Compiler:\"gc\", Platform:\"linux/amd64\"} Cloud provider or hardware configuration: AWS. Running kube api server in hyperkube. OS (e.g: cat /etc/os-release): NAME=\"CentOS Linux\" VERSION=\"7.1808 (Core)\" ID=\"centos\" IDLIKE=\"rhel fedora\" VERSIONID=\"7\" PRETTYNAME=\"CentOS Linux 7.1808 (Core)\" ANSICOLOR=\"0;31\" CPENAME=\"cpe:/o:centos:centos:7\" HOMEURL=\"\" BUGREPORTURL=\"\" CENTOSMANTISBTPROJECT=\"CentOS-7\" CENTOSMANTISBTPROJECTVERSION=\"7\" REDHATSUPPORTPRODUCT=\"centos\" REDHATSUPPORTPRODUCTVERSION=\"7\" OSTREEVERSION=7.1808 Kernel (e.g. uname -a): Linux hackit.internal 3.10.0-862.11.6.el7.x8664 SMP Tue Aug 14 21:49:04 UTC 2018 x8664 x8664 x86_64 GNU/Linux Install tools: Manual installation. Others: n/a\n/sig product-security\nClosing this issue. <detailsIn response to : if you think this is serious, send an email thanks!", "commid": "kubernetes_issue_76676", "tokennum": 565}], "negative_passages": []}
{"query_id": "q-en-kubernetes-71493df9dd735e64b867a28c12062f31ef4528f5bd3902906deada4ebb2e3741", "query": "t.Errorf(\"Invalid content read from cache %q\", string(content)) } } <ins> func TestCacheRoundTripperPathPerm(t *testing.T) { assert := assert.New(t) rt := &testRoundTripper{} cacheDir, err := ioutil.TempDir(\"\", \"cache-rt\") os.RemoveAll(cacheDir) defer os.RemoveAll(cacheDir) if err != nil { t.Fatal(err) } cache := newCacheRoundTripper(cacheDir, rt) // First call, caches the response req := &http.Request{ Method: http.MethodGet, URL:    &url.URL{Host: \"localhost\"}, } rt.Response = &http.Response{ Header:     http.Header{\"ETag\": []string{`\"123456\"`}}, Body:       ioutil.NopCloser(bytes.NewReader([]byte(\"Content\"))), StatusCode: http.StatusOK, } resp, err := cache.RoundTrip(req) if err != nil { t.Fatal(err) } content, err := ioutil.ReadAll(resp.Body) if err != nil { t.Fatal(err) } if string(content) != \"Content\" { t.Errorf(`Expected Body to be \"Content\", got %q`, string(content)) } err = filepath.Walk(cacheDir, func(path string, info os.FileInfo, err error) error { if err != nil { return err } if info.IsDir() { assert.Equal(os.FileMode(0750), info.Mode().Perm()) } else { assert.Equal(os.FileMode(0660), info.Mode().Perm()) } return nil }) assert.NoError(err) } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-5f4971cee99e57062ae7961121de35cc677214a3e6ca77682b093e74b00a9b30", "text": "</details\nAdjusted the CVSS score to to indicate user interaction is required (since they must specify a non-default cache option pointed at a shared writeable location)\nThere are two places this should be done: PathPerm and FilePerm should be set here: the temp file and final file should have stricter permissions (probably 0660) here:\n/cc\n/help\nThis request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\n/assign I would like to work on release-1.9, as I just made a hot fix for our team's k8s version of 1.9.\nGitHub didn't allow me to assign the following users: yuchengwu. Note that only and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign I would like to work on release-1.9, as I just made a hot fix for our team's k8s version of 1.9. 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\nhelp fixing this is welcome, though it would only be fixed in releases 1.12+, per\n/label official-cve-feed (Related to kubernetes/sig-security)", "commid": "kubernetes_issue_76676", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-71505ba8fbbb10789462bd8975f0e0b891fc4f7321a67910c145c12bd2234b59", "query": "}) } } <ins> func TestSubnet(t *testing.T) { for i, c := range []struct { desc     string service  *v1.Service expected *string }{ { desc:     \"No annotation should return nil\", service:  &v1.Service{}, expected: nil, }, { desc: \"annotation with subnet but no ILB should return nil\", service: &v1.Service{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ ServiceAnnotationLoadBalancerInternalSubnet: \"subnet\", }, }, }, expected: nil, }, { desc: \"annotation with subnet but ILB=false should return nil\", service: &v1.Service{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ ServiceAnnotationLoadBalancerInternalSubnet: \"subnet\", ServiceAnnotationLoadBalancerInternal:       \"false\", }, }, }, expected: nil, }, { desc: \"annotation with empty subnet should return nil\", service: &v1.Service{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ ServiceAnnotationLoadBalancerInternalSubnet: \"\", ServiceAnnotationLoadBalancerInternal:       \"true\", }, }, }, expected: nil, }, { desc: \"annotation with subnet and ILB should return subnet\", service: &v1.Service{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ ServiceAnnotationLoadBalancerInternalSubnet: \"subnet\", ServiceAnnotationLoadBalancerInternal:       \"true\", }, }, }, expected: to.StringPtr(\"subnet\"), }, } { real := subnet(c.service) assert.Equal(t, c.expected, real, fmt.Sprintf(\"TestCase[%d]: %s\", i, c.desc)) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-94ebb6d5cc5a883444cc57b7fe675619934dadcea635fbafcba0058503bec1c7", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: When service is set with ILB annotation and empty string subnet, e.g. The service would be pending forever with following error: What you expected to happen: ILB should be provisioned successfully. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Others: /sig azure /kind bug /assign\n/milestone v1.14 We're entering and this looks relevant to the 1.14 release. Please if I am incorrect\nThanks", "commid": "kubernetes_issue_74497", "tokennum": 195}], "negative_passages": []}
{"query_id": "q-en-kubernetes-715925d93a41296f6068e5cb7db4c0aa728f8ee9ec8bf8eecf5ff2fa73cb8ebf", "query": "\"fmt\" \"os\" \"path/filepath\" <ins> \"strings\" </ins> \"time\" \"github.com/pkg/errors\"", "positive_passages": [{"docid": "doc-en-kubernetes-1d9713caefc449b5fa12697f2f529990c13dff1a712a56404b9120eb41d78bc3", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --When attempting to upgrade kubernetes using kubeadm upgrade apply, kubeadm fails to parse an etcd imagetag containing build metadata in the form of as a valid semver. An example upgrade produces an error similar to: Note this will occur even if the etcd version is unchanged. The +` character. This pattern is used to support custom kubernetes images, for instance kube-apiserver:v1.20.4+patch.0 will be converted to imagetag v1.20.4_patch.0 when running make quick-release-images. Add the following to kubeadm- Install kubernetes. Then upgrade kubernetes with kubeadm upgrade apply. I have tested a fix for this issue and will PR shortly. Kubernetes version (use ): N/A Cloud provider or hardware configuration: N/A OS (e.g: ): N/A Kernel (e.g. ): N/A Install tools: kubeadm Network plugin and version (if this is a network-related bug): N/A Others: N/A\n/sig cluster-lifecycle\n/area kubeadm\n/triage accepted", "commid": "kubernetes_issue_100349", "tokennum": 312}], "negative_passages": []}
{"query_id": "q-en-kubernetes-716999b38246af4c9270b6160848053ed7fc15884b244ce0fe1dcb9d94f46b3f", "query": "} // CleanupAdapter deletes Custom Metrics - Stackdriver adapter deployments. <del> func CleanupAdapter(namespace, adapterDeploymentFile string) { stat, err := framework.RunKubectl(namespace, \"delete\", \"-f\", adapterDeploymentFile) </del> <ins> func CleanupAdapter(adapterDeploymentFile string) { stat, err := framework.RunKubectl(\"\", \"delete\", \"-f\", adapterDeploymentFile) </ins> framework.Logf(stat) if err != nil { framework.Logf(\"Failed to delete adapter deployments: %s\", err)", "positive_passages": [{"docid": "doc-en-kubernetes-cecee0a132f84dbf6d5783d328e94b49c8666ebba8eef4ded1687e53b0451e97", "text": "/kind failing-test <!-- If this is a flake, please add: /kind flake --/sig autoscaling Looks like it just started happening today (@ 2020-09-15 03:54:19 +0000 UTC) !\ncc the namespace from the provided object \"kube-system\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=kube-system' to perform this operation. the namespace from the provided object \"custom-metrics\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=custom-metrics' to perform this operation. the namespace from the provided object \"custom-metrics\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=custom-metrics' to perform this operation.\nrelated fix:\nNo I don't think that's the fix for this (that is just a little cleanup). Actually I think we have to delete namespace parameter in line : Because before , the will have no actually effect. But now with the change of , it will have namespace : at the end of the command. But the namespace in yaml file is which is different from . We should not have parameter when applying from file because this test didn't have before, right? Related PR:\n/assign", "commid": "kubernetes_issue_94809", "tokennum": 318}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7170f5e1f674e349b705d2899e7b1fb10156086e42893bebdc5c466bc686907f", "query": "internalapi \"k8s.io/cri-api/pkg/apis\" apitest \"k8s.io/cri-api/pkg/apis/testing\" fakeremote \"k8s.io/kubernetes/pkg/kubelet/cri/remote/fake\" <ins> \"k8s.io/kubernetes/pkg/kubelet/cri/remote/util\" </ins> ) const (", "positive_passages": [{"docid": "doc-en-kubernetes-a55cc9cf23a1aa66af6ba96638da8c1361b9b34938bf9fbe2ee98dcb858f1383", "text": "Which jobs are flaking: periodics-kubernetes-bazel-test Which test(s) are flaking: //pkg/kubelet/cri/remote TestVersion Testgrid link: Reason for failure: Error: Received unexpected error: rpc error: code = Unavailable desc = transport is closing panic: runtime error: invalid memory address or nil pointer dereference [recovered] panic: runtime error: invalid memory address or nil pointer dereference Anything else we need to know: To reproduce with stress: go test -race -c ./pkg/kubelet/cri/remote stress - TestVersion Detailed logs\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig testing\nI 'll give it a see and fix it :)\n/assign\n/remove-sig testing SIG node owns their unit tests. SIG testing owns the framework, infrastructure, etc.\n/sig node", "commid": "kubernetes_issue_96950", "tokennum": 277}], "negative_passages": []}
{"query_id": "q-en-kubernetes-718671d140b86ebf5b93a6194596b0324f233352f6657a5cad794f27a1ec1d0d", "query": "* [Example of dynamic updates](examples/update-demo/README.md) * [Cluster monitoring with heapster and cAdvisor](https://github.com/GoogleCloudPlatform/heapster) * [Community projects](https://github.com/GoogleCloudPlatform/kubernetes/wiki/Kubernetes-Community) <del> * [Development guide](docs/development.md) </del> <ins> * [Development guide](docs/devel/development.md) </ins> Or fork and start hacking!", "positive_passages": [{"docid": "doc-en-kubernetes-7c5448078f172c3dba4d1f6f6ed5d66f21d2fc0ea9dd38dbb1ed9b4cc49eea15", "text": "Right now, we have a mixture of user documentation and developer documentation in the top-level directory. We should make it easier to find a just user documentation. Step 1 would be to move developer documentation into a subdir like docs/development or something like that. User docs would stay in the top-level docs dir.\nmove to", "commid": "kubernetes_issue_1797", "tokennum": 71}], "negative_passages": []}
{"query_id": "q-en-kubernetes-718a96f0663797fccf6cec1365e3d1ffc94cc79229396dcfcd62a7941b8f333f", "query": "\"description\": \"EndpointPort is a tuple that describes a single port.\", \"properties\": { \"appProtocol\": { <del> \"description\": \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and http://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol. This is a beta field that is guarded by the ServiceAppProtocol feature gate and enabled by default.\", </del> <ins> \"description\": \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol. This is a beta field that is guarded by the ServiceAppProtocol feature gate and enabled by default.\", </ins> \"type\": \"string\" }, \"name\": {", "positive_passages": [{"docid": "doc-en-kubernetes-3e7e95e6f142ca39e6e3ca0b78c3932bd6cbdfdc898eed9d3ffda27d28f904c7", "text": "We should make the change in PR API reference links to should use HTTPS, not HTTP Visit h and look at the IANA hyperlinks Once this fix is made, a PR to is needed to update the docs (by autogenerating them). This typically would be deferred until the next Kubernetes release. v1.23 not applicable not applicable not applicable not applicable not applicable\n/sig docs\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI opened this issue so that someone else can open a new PR that is equivalent to .\n/retitle Update links to IANA for Service Name and Transport Protocol Port Number Registry\nI would like to work on this issue. May I assign it to myself?\nAnyone - including you - is welcome to work on this issue! So long as you've you can open a pull request to propose a fix.\nThanks\n/assign\nI have made the PR. I hope this works. If not then will be happy to do the necessary changes.\nHad to close the previous PR because of issues, here is the new one I made.", "commid": "kubernetes_issue_106980", "tokennum": 300}], "negative_passages": []}
{"query_id": "q-en-kubernetes-71a56af80b333d369ea5436decfac8d8bc987f9747310af3a27f973e0960eff4", "query": "return feasibleNodes, nil } <del> type pluginScores struct { Plugin           string Score            int64 AverageNodeScore float64 } </del> // prioritizeNodes prioritizes the nodes by running the score plugins, // which return a score for each node from the call to RunScorePlugins(). // The scores from each plugin are added together to make the score for that node, then", "positive_passages": [{"docid": "doc-en-kubernetes-008ca2b69bf6f84855aa7fc74e613d0733365e6cd47dcc25c8f18519fbaaf463", "text": "Scheduler throughput drops significantly in http://perf- ! After , seems to be the curlspirit.\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/priority critical-urgent /sig scheduling /sig scalability", "commid": "kubernetes_issue_99913", "tokennum": 125}], "negative_passages": []}
{"query_id": "q-en-kubernetes-71d20a89960ccd8b120add7e2889312112c8a3d5316f22268340474a922acb89", "query": ") apiserverRequestConcurrencyLimit = compbasemetrics.NewGaugeVec( &compbasemetrics.GaugeOpts{ <del> Namespace:      namespace, Subsystem:      subsystem, Name:           \"request_concurrency_limit\", Help:           \"Shared concurrency limit in the API Priority and Fairness subsystem\", StabilityLevel: compbasemetrics.ALPHA, </del> <ins> Namespace: namespace, Subsystem: subsystem, Name:      \"request_concurrency_limit\", Help:      \"Nominal number of execution seats configured for each priority level\", // Remove this metric once all suppported releases have the equal nominal_limit_seats metric DeprecatedVersion: \"1.30.0\", StabilityLevel:    compbasemetrics.ALPHA, </ins> }, []string{priorityLevel}, )", "positive_passages": [{"docid": "doc-en-kubernetes-a3e5f991085cecca4a970d807dd5157be9d11e288da6daa6aadb8b1d3ef3056a", "text": "In asked the following question. While the user-facing documentation answers this question clearly enough, John was reading the HELP string in the Prometheus scrapes. That thing only says the following. The metric HELP strings should be clear enough. Scrape or read the code (). No response <detailsThis problem started when we generalized to allow width other than 1 and got worse when we introduced borrowing. </details<detailsN/A </details<detailsN/A </details<details</details<details</details<details</details\n/assign\nActually, this metric should be removed. It is a duplicate of but with an inferior name.\nLooks good (Sorry I never got around to logging this issue myself. Have been super busy. And your wording is better anyway :-) )\n/triage accepted Thank you.", "commid": "kubernetes_issue_118957", "tokennum": 173}], "negative_passages": []}
{"query_id": "q-en-kubernetes-71d428ebfbc7fa4fb0807eb410ca7f2bf521c711473b4462db452802b18c4739", "query": "<ins> /* Copyright 2016 The Kubernetes Authors All rights reserved. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package v1 import ( \"k8s.io/kubernetes/pkg/api/v1\" \"k8s.io/kubernetes/pkg/runtime\" ) func addDeepCopyFuncs(scheme *runtime.Scheme) { if err := scheme.AddGeneratedDeepCopyFuncs( v1.DeepCopy_v1_DeleteOptions, v1.DeepCopy_v1_ExportOptions, v1.DeepCopy_v1_List, v1.DeepCopy_v1_ListOptions, v1.DeepCopy_v1_ObjectMeta, v1.DeepCopy_v1_ObjectReference, v1.DeepCopy_v1_OwnerReference, v1.DeepCopy_v1_Service, v1.DeepCopy_v1_ServiceList, v1.DeepCopy_v1_ServicePort, v1.DeepCopy_v1_ServiceSpec, v1.DeepCopy_v1_ServiceStatus, ); err != nil { // if one of the deep copy functions is malformed, detect it immediately. panic(err) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-5056a2515a29befdf589a74f13db031ed4142bbabfa8d2c37cafac2de4fccaea", "text": "I started the federation-apiserver and went to and got the following output: Expected: I should have got an empty v1.ServiceList Any idea on what we are doing wrong? Have you guys seen this error?\nI think your deep copiers or conversion functions are not getting registered properly. If you look at my change in , some places are inappropriately registering with api.Scheme instead of the passed in scheme. Maybe you have that problem or a similar one, since I think you guys copied some code. , Nikhil Jindal wrote:\nDeep copy generation was slightly broken as well - you may want to double check that they are registered. On May 23, 2016, at 5:50 PM, Daniel Smith wrote: I think your deep copiers or conversion functions are not getting registered properly. If you look at my change in , some places are inappropriately registering with api.Scheme instead of the passed in scheme. Maybe you have that problem or a similar one, since I think you guys copied some code. , Nikhil Jindal wrote: \u2014 You are receiving this because you are on a team that was mentioned. Reply to this email directly or view it on GitHub\nI got the same error with latest branch, as I was swamping on service controller, so I use a previous version and worked around it.\ndeep copies were indeed missing, but adding them hasnt fixed the issue. Will debug more. is my PR to add the deep copies cc Please feel free to file issues for any such problem you face. We need to fix all these issues. Its good if we know about them early. Thanks!\nfixes this", "commid": "kubernetes_issue_26111", "tokennum": 335}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7246166cab5d200f4711466274910e226d2d0ef91c4dd091e47740daf97683b2", "query": "statuses = append(statuses, \"Unknown\") } row.Cells = append(row.Cells, obj.Name, strings.Join(statuses, \",\"), translateTimestamp(obj.CreationTimestamp)) <ins> if options.ShowLabels { row.Cells = append(row.Cells, labels.FormatLabels(obj.Labels)) } </ins> return []metav1alpha1.TableRow{row}, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-f29982137c07dadb3e257d7391e0d9b7bfd5f1ce8fdca72f798301cc159728a0", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: After labeling clusters in a Federation, when you type the field is empty. What you expected to happen: The fiels should contain information about the labels in the cluster How to reproduce it (as minimally and precisely as possible): a federation control pane in any Cloud Provider and any DNS provider your cluster: info aboyut the cluster with the flag: Note: if you describe it, you see the labels being : Environment: Kubernetes version (use ): 1.8.0 Cloud provider or hardware configuration**: anyone OS (e.g. from /etc/os-release): Ubuntu 16.04 Kernel (e.g. ): Linux Install tools: curl Others:\n/sig multicluster\nI'm working on it.", "commid": "kubernetes_issue_53729", "tokennum": 179}], "negative_passages": []}
{"query_id": "q-en-kubernetes-72af7b59ec9ebd34d57bf50a67026b162e74fd85721c157a0730fc80f8201d15", "query": "echo -n Attempt \"$(($attempt+1))\" to check for salt-master local output local ok=1 <del> output=$(ssh -oStrictHostKeyChecking=no -i \"${AWS_SSH_KEY}\" ubuntu@${KUBE_MASTER_IP} pgrep salt-master 2> $LOG) || ok=0 </del> <ins> output=$(ssh -oStrictHostKeyChecking=no -i \"${AWS_SSH_KEY}\" ${SSH_USER}@${KUBE_MASTER_IP} pgrep salt-master 2> $LOG) || ok=0 </ins> if [[ ${ok} == 0 ]]; then if (( attempt > 30 )); then echo", "positive_passages": [{"docid": "doc-en-kubernetes-7c0443d3746fe3757c9195c5c33416ecd39f97575569d1247bf005f30b3d366d", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: What happened: I visited the Kubernetes 1.11 release blog post and clicked on the link to the article on resizing persistent volumes. The server returned a 404. What you expected to happen: I expected to navigate to the article on resizing persistent volumes in Kubernetes. How to reproduce it (as minimally and precisely as possible): Visit the release announcement blog post (), scroll down to the \"4 Day Features Blog Series\" section, and click on the link to the article on resizing persistent volumes. Anything else we need to know?: The link currently points to: The correct link is: Environment: Kubernetes version (use ): N/A Cloud provider or hardware configuration: N/A OS (e.g. from /etc/os-release): N/A Kernel (e.g. ): N/A Install tools: N/A Others: N/A\nReiterating the mentions to trigger a notification: <detailsIn response to : <!-- This form is for bug reports and feature requests ONLY! --/kind bug /kind feature What happened: I visited the Kubernetes 1.11 release blog post and clicked on the link to the article on resizing persistent volumes. The server returned a 404. I expected to navigate to the article on resizing persistent volumes in Kubernetes. Visit the release announcement blog post (), scroll down to the \"4 Day Features Blog Series\" section, and click on the link to the article on resizing persistent volumes. The link currently points to: The correct link is: Kubernetes version (use ): N/A Cloud provider or hardware configuration: N/A OS (e.g. from /etc/os-release): N/A Kernel (e.g. ): N/A Install tools: N/A Others: N/A 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\nIt should be reported to kubernetes/website, but doesn't matter.", "commid": "kubernetes_issue_66944", "tokennum": 494}], "negative_passages": []}
{"query_id": "q-en-kubernetes-72d504fbe29a40e4965d730182509c6382eedbf5be1f11660e96036eda24e8c5", "query": "// Run begins watching and syncing. func (rm *ReplicationManager) Run(workers int, stopCh <-chan struct{}) { defer util.HandleCrash() <ins> glog.Infof(\"Starting RC Manager\") controller.SyncAllPodsWithStore(rm.kubeClient, rm.podStore.Store) </ins> go rm.rcController.Run(stopCh) go rm.podController.Run(stopCh) for i := 0; i < workers; i++ {", "positive_passages": [{"docid": "doc-en-kubernetes-b0a441a371f8db864bebc11c7303837af71a86244bb0f50ec81fe1d8a09d5c71", "text": "The test is in flaky suite and no one seems to care. We need an owner for this test. cc Last failure log:\ndo you think you can take a look at this?\nThis is happening because of a bad assumption. The assumption is: if the reflector's store is consistent with etcd, the store given back to clients of the framework.Controller is too. I'd really like a general fix applicable to all controllers for this problem, but fixing it just for the RCs is pretty easy. In more detail: This function reports when the reflector has listed from apiserver. But the store given to the reflector is the fifo of the framework.Controller. The store given back to the caller is still not consistent, and will not be till the framework.Controller puts all the objects from the fifo into the client state store (). The rc specific fix: Before starting the rc manager, seed the expectations store with an expectation like {rc:foo, adds: foo.Status.Replicas, deletes:0}. This will wait for status.Replicas number of ADD events till a timeout. The general fix: Somehow expose this through framework.Controller.HasSynced (clients don't care about the fifo anyway, shouldn't it just be an implementation detail?) ideas? cc'ing people who have written controllers that might be interested I don't think this (and generally anything flaky for 1 release) is a p0, I can fix it if you don't mind dealing with the flakes till I've cleared things off my plate. I'd be more than happy to review a fix.\nWell, it's a P0 because test is flaky. E.g last run:\n- did you have chance to look into it?\nThe \"DaemonRestart\" tests are still labeled at . I will send a PR to promote them.\nare you still planning to send aPR to promote the DaemonRestart tests out of flaky? I think this is the right thing to do.\nAck; sorry, I lost this in the muck.", "commid": "kubernetes_issue_17829", "tokennum": 444}], "negative_passages": []}
{"query_id": "q-en-kubernetes-730e16fcf0872634daf133e83372c62bab09568914217adae36e316b4301ad9a", "query": "for _, kind := range []string{ \"Service\", } { <del> err = api.Scheme.AddFieldLabelConversionFunc(\"v1\", kind, </del> <ins> err = scheme.AddFieldLabelConversionFunc(\"v1\", kind, </ins> func(label, value string) (string, string, error) { switch label { case \"metadata.namespace\",", "positive_passages": [{"docid": "doc-en-kubernetes-5056a2515a29befdf589a74f13db031ed4142bbabfa8d2c37cafac2de4fccaea", "text": "I started the federation-apiserver and went to and got the following output: Expected: I should have got an empty v1.ServiceList Any idea on what we are doing wrong? Have you guys seen this error?\nI think your deep copiers or conversion functions are not getting registered properly. If you look at my change in , some places are inappropriately registering with api.Scheme instead of the passed in scheme. Maybe you have that problem or a similar one, since I think you guys copied some code. , Nikhil Jindal wrote:\nDeep copy generation was slightly broken as well - you may want to double check that they are registered. On May 23, 2016, at 5:50 PM, Daniel Smith wrote: I think your deep copiers or conversion functions are not getting registered properly. If you look at my change in , some places are inappropriately registering with api.Scheme instead of the passed in scheme. Maybe you have that problem or a similar one, since I think you guys copied some code. , Nikhil Jindal wrote: \u2014 You are receiving this because you are on a team that was mentioned. Reply to this email directly or view it on GitHub\nI got the same error with latest branch, as I was swamping on service controller, so I use a previous version and worked around it.\ndeep copies were indeed missing, but adding them hasnt fixed the issue. Will debug more. is my PR to add the deep copies cc Please feel free to file issues for any such problem you face. We need to fix all these issues. Its good if we know about them early. Thanks!\nfixes this", "commid": "kubernetes_issue_26111", "tokennum": 335}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7315a192ace9f41f386ea62608c77db4ccee12fdc7ea9b0ae17bb21a12e26e3e", "query": "// zero capacity, and the default labels. func (kl *Kubelet) getNodeAnyWay() (*v1.Node, error) { if kl.kubeClient != nil { <del> if n, err := kl.nodeLister.Get(string(kl.nodeName)); err == nil { </del> <ins> if n, err := kl.GetNode(); err == nil { </ins> return n, nil } }", "positive_passages": [{"docid": "doc-en-kubernetes-8476bba8e23a7ed885cd34c1077ce17dbf12901ac7ae9725333264f6ea8cfdae", "text": "What happened: A deployment is created that uses a after the cluster master is created but before the cluster worker nodes are fully initialized. During the initialization of the worker nodes, the nodes are temporarily available for scheduling without the necessary label to match the deployment's node selector. Depending on how long the nodes are available for scheduling without the necessary node labels for the deployment, the scheduler will start to spam with cluster with pods in status. This spamming stops once the worker nodes are fully initialized and the pods are scheduled successful. The exact timing of all of this is TBD. What you expected to happen: Pods in status are annoying and require manual cleanup. It would be preferred that the scheduler avoid this an simply issue warning events. How to reproduce it (as minimally and precisely as possible): See issue description. Anything else we need to know?: No. Environment: Kubernetes version (use ): 1.18.3 Cloud provider or hardware configuration: IBM Cloud Kubernetes Service OS (e.g: ): Ubuntu 18.04.4 LTS Kernel (e.g. ): 4.15.0-96-generic Install tools: Managed service install Network plugin and version (if this is a network-related bug): N/A Others: N/A\nRelated to and\n/sig scheduling\nby spamming are you referring to scheduler logs? also, why are the nodes not labelled from the get go?\nJust to confirm, all the pods in question are still in Pending state, yes? If the pods are in pending state, all of them will get scheduled eventually once the nodes get their labels.\nThe pods are not in state. They are actually in state. The pods eventually get scheduled but we are left with anywhere from a few to dozens of these state pods. Also, we are looking at labeling the nodes via kubelet flags to see if that helps.\n/remove-kind bug\nAfter we add some retry logic and wait time in this problem can be solved: As you can see this function returns initial node as the first request failed.\nI also get hit by this, when single controller node gets rebooted and scheduler starts as static container before kubelet becomes ready.", "commid": "kubernetes_issue_92067", "tokennum": 465}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7315a192ace9f41f386ea62608c77db4ccee12fdc7ea9b0ae17bb21a12e26e3e", "query": "// zero capacity, and the default labels. func (kl *Kubelet) getNodeAnyWay() (*v1.Node, error) { if kl.kubeClient != nil { <del> if n, err := kl.nodeLister.Get(string(kl.nodeName)); err == nil { </del> <ins> if n, err := kl.GetNode(); err == nil { </ins> return n, nil } }", "positive_passages": [{"docid": "doc-en-kubernetes-6c53201dbb91d52a8ade960092a5ed582f4d35e33a53b75d555d15ae815dc25c", "text": "Can be cleaned up with:\n/sig node\nthe spam cycle is this loop: \"pod create, pod schedule, worker reject, pod failed\" -- we don't have a lot of protection in higher level workload controllers to handle pods that fail at kubelet admission time versus pods that just dont create due to quota/admission. in general, is the spam causing any other stability issues? is pod gc pruning the pods?\nI wonder if we can do a trick in node lister to mitigate any race condition here...\nwe could maybe do something similar to to ensure node lister has synced...\nhacking on option to ensure if kubelet has a node lister with a valid kube client, we wait for it to sync at least once here which should mitigate this issue. see:\nWe noticed the problem on the OLM pod which is managed by the OLM operator. Right or wrong, the operator does not like seeing the pod go to status and no longer reconciles the pod. The end result is that manual intervention (i.e. pod deletion) is required to fix the problem.\nsure... i would have thought the pod is failed in that instance and reached a terminal state. either way, i am looking at what i can do to mitigate this.\nThe problem persists in our environment as well, and the workaround cited above will not do anymore. Is there something in the works for this one?\nIssues 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\n/remove-lifecycle stale", "commid": "kubernetes_issue_92067", "tokennum": 383}], "negative_passages": []}
{"query_id": "q-en-kubernetes-73295edc882161b8be65028842cfb0cb0d438b3beb196432dc1c73796c43fca1", "query": "var k8sBinDir = flag.String(\"k8s-bin-dir\", \"\", \"Directory containing k8s kubelet and kube-apiserver binaries.\") <del> var buildTargets = []string{ \"cmd/kubelet\", \"cmd/kube-apiserver\", \"test/e2e_node/e2e_node.test\", } </del> func buildGo() { glog.Infof(\"Building k8s binaries...\") k8sRoot, err := getK8sRootDir() if err != nil { glog.Fatalf(\"Failed to locate kubernetes root directory %v.\", err) } <del> cmd := exec.Command(filepath.Join(k8sRoot, \"hack/build-go.sh\"), buildTargets...) </del> <ins> cmd := exec.Command(filepath.Join(k8sRoot, \"hack/build-go.sh\")) </ins> cmd.Stdout = os.Stdout cmd.Stderr = os.Stderr err = cmd.Run()", "positive_passages": [{"docid": "doc-en-kubernetes-7f95224274155bb39af2e05742451e79cefc1f176d05622797c3ba56ecf46808", "text": "is failing with: Examples:\nThis is the failing line of code...\nPASS: FAIL: Seems like this disappeared: Also this is flipped: we run the following\nmy leading theory is this is something in\nThe issue is that the above PR changed a bunch of to be and thus we no longer wait for getArchive() to complete before starting tests. And unfortunately the previous PR cannot be reverted\nAfter merging, kubelet-gce-e2e-ci still failed with the same issue. reopen the issue. Currently the failure blocked the merge-bot.\ndid stop the bleeding. Now kubelet-gce-e2e-ci is green: and merge-bot is unblocked.\nI think the \"go arc\" piece was a red herring. I suspect the issue is that the same PR tries to copy the binary into the archive directory, but PR stops building ginkgo, so the copy fails. That is why this line then fails...", "commid": "kubernetes_issue_27104", "tokennum": 203}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7370a595c266f58e16dfadcc43e67e51e6781c1ebbd5ad0b3f2237523c96ac67", "query": "} } } <ins> func hasJump(rules []iptablestest.Rule, destChain, ipSet string) bool { match := false for _, r := range rules { if r[iptablestest.Jump] == destChain { match = true if ipSet != \"\" { if strings.Contains(r[iptablestest.MatchSet], ipSet) { return true } match = false } } } return match } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-4b95e73f98faca5940a16ee2fccddf37ae93437213e073578ff34d76b732271f", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Service loadbalancer source range don't work in ipvs proxy mode. Which result in gci-gce-ipvs CI failed. http://k8s- How to reproduce it (as minimally and precisely as possible): In gce environment. a service with backend. service type to service util service external IP is specified. the service from pod inside and pod out of the . Environment: Kubernetes version (use ): master Cloud provider or hardware configuration: gce OS (e.g. from /etc/os-release): ubuntu Kernel (e.g. ): Install tools: cluster/kube- Others:\n/kind bug /sig network /label ipvs\n/area ipvs\nThe test seems to be flaky now. Can you take a look please?\nI don't know why, but I think this flaky have the similiar reason with other normal service-test cases, like Those flaky are pretty annoying, problem is, I have run those cases in my own environment many times, never fail... : ( But still, I'll do my best to find the reason.", "commid": "kubernetes_issue_61090", "tokennum": 264}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7378151faa881b9d04a90683c7f1060671f81b0448b442a31bb94649272f5744", "query": "deps = [ \"//cmd/kubeadm/app/apis/kubeadm:go_default_library\", \"//cmd/kubeadm/app/constants:go_default_library\", <ins> \"//cmd/kubeadm/app/features:go_default_library\", </ins> \"//cmd/kubeadm/app/util:go_default_library\", \"//cmd/kubeadm/app/util/apiclient:go_default_library\", \"//pkg/api/legacyscheme:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-fdf6c8e5598e80992f62cef52eca112e7ba1d532fe8ace89dc932a5edac53dea", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: Currently, IPVS proxier does not run any e2e test cases. What you expected to happen: I think it's important to create test suite for IPVS in upstream CI which will help a lot in moving IPVS existing alpha. Anything else we need to know?: Let's work together. /sig network\nSelf /assign\nThere are to ways to do this work: , but doesn't support any kube-proxy config right now, so I had this pr , and also, need support it too, see this pr: kubernetes/kubernetes-anywhere build cluster. See this pr: kubernetes/test-infra The second way is much easier and faster, but I was told they gonna deprecated the , so in the long term, we still need and 's support. If anybody have better way or have some suggestion about this, please let me know, I'll be really appreciate, Thanks.", "commid": "kubernetes_issue_52834", "tokennum": 247}], "negative_passages": []}
{"query_id": "q-en-kubernetes-737bc614ab54dce551cd4cbc21c996bb46d8d6d577a9fd705b4372f278f47bfa", "query": "\"terminationMessagePath\":   \"Optional: Path at which the file to which the container's termination message will be written is mounted into the container's filesystem. Message written is intended to be brief final status, such as an assertion failure message. Will be truncated by the node if greater than 4096 bytes. The total message length across all containers will be limited to 12kb. Defaults to /dev/termination-log. Cannot be updated.\", \"terminationMessagePolicy\": \"Indicate how the termination message should be populated. File will use the contents of terminationMessagePath to populate the container status message on both success and failure. FallbackToLogsOnError will use the last chunk of container log output if the termination message file is empty and the container exited with an error. The log output is limited to 2048 bytes or 80 lines, whichever is smaller. Defaults to File. Cannot be updated.\", \"imagePullPolicy\":          \"Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise. Cannot be updated. More info: https://kubernetes.io/docs/concepts/containers/images#updating-images\", <del> \"securityContext\":          \"Security options the pod should run with. More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/\", </del> <ins> \"securityContext\":          \"SecurityContext defines the security options the container should be run with. If set, the fields of SecurityContext override the equivalent fields of PodSecurityContext. More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/\", </ins> \"stdin\":                    \"Whether this container should allocate a buffer for stdin in the container runtime. If this is not set, reads from stdin in the container will always result in EOF. Default is false.\", \"stdinOnce\":                \"Whether the container runtime should close the stdin channel after it has been opened by a single attach. When stdin is true the stdin stream will remain open across multiple attach sessions. If stdinOnce is set to true, stdin is opened on container start, is empty until the first client attaches to stdin, and then remains open and accepts data until the client disconnects, at which time stdin is closed and remains closed until the container is restarted. If this flag is false, a container processes that reads from stdin will never receive an EOF. Default is false\", \"tty\":                      \"Whether this container should allocate a TTY for itself, also requires 'stdin' to be true. Default is false.\",", "positive_passages": [{"docid": "doc-en-kubernetes-2eefef1a83ddd783604f0989f7bcbb86ee11f3e15f09ced1fa06f0ad1ee322e6", "text": "What happened: states that Container.SecurityContext applies to a Pod, which can be misleading since we already have PodSecurityContext. What you expected to happen: Documentation states that it applies to container How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment:\n/sig api-machinery /kind documentation\n/cc\nIssues 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\nNot stale.\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten\nIssues 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\n/remove-lifecycle rotten\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nClosing 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", "commid": "kubernetes_issue_90634", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-737c78118b9f2825dfc162456aa695b4ff6ec9abf9a9c5f7cedb46f632b55c82", "query": "apps \"k8s.io/api/apps/v1\" \"k8s.io/api/core/v1\" <ins> \"k8s.io/apimachinery/pkg/api/errors\" </ins> apierrs \"k8s.io/apimachinery/pkg/api/errors\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/labels\"", "positive_passages": [{"docid": "doc-en-kubernetes-da00f1cf1a24475bca3717ed24d8bd1cf5079c51cd54d6d4d01b160ed7cae851", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: DaemonSet has an e2e test running that has dubious purpose. What you expected to happen: The e2e test should be refactored and commented clearer as it will be part of the conformance.\nTo elaborate, we're concerned that the following may not actually ensure that DaemonSet recreates Failed Pods: For example, it seems possible that the Node might simply overwrite the Pod status with its own information if it hasn't yet seen the change to the Phase. Ideally, we should verify that the Pod UID we force to Failed no longer shows up in the DaemonSet's list of Pods after the DaemonSet becomes happy again.", "commid": "kubernetes_issue_59076", "tokennum": 150}], "negative_passages": []}
{"query_id": "q-en-kubernetes-738bfbf2a2cfece745dd90ccc3a283f28bcf6b2f4401ed755cee1818a5c1e352", "query": "if itemOut.Status != api.StatusWorking || itemOut.Details == nil || itemOut.Details.ID == \"\" { t.Errorf(\"Unexpected status: %#v (%s)\", itemOut, string(body)) } <ins> wait.Done() </ins> } func TestCreateNotFound(t *testing.T) {", "positive_passages": [{"docid": "doc-en-kubernetes-f8d5fa52ad40b7a48721555fc6e9ed2d9d20bf180da0265ac5e3a79ed043fc75", "text": "Intermittent failures on Travis.\nHrm, this passes 100/100 locally for me. I'll look at the code and see if I see anything. --brendan", "commid": "kubernetes_issue_2103", "tokennum": 34}], "negative_passages": []}
{"query_id": "q-en-kubernetes-73bf9911847c40ff86ab3144058ee980db2a621094879a2f80b1d3f7bea22e6a", "query": "// MinionList is a list of minions. type MinionList struct { JSONBase `json:\",inline\" yaml:\",inline\"` <del> Items    []Minion `json:\"minions,omitempty\" yaml:\"minions,omitempty\"` </del> <ins> // DEPRECATED: the below Minions is due to a naming mistake and // will be replaced with Items in the future. Minions []Minion `json:\"minions,omitempty\" yaml:\"minions,omitempty\"` Items   []Minion `json:\"items,omitempty\" yaml:\"items,omitempty\"` </ins> } // Binding is written by a scheduler to cause a pod to be bound to a host.", "positive_passages": [{"docid": "doc-en-kubernetes-a574ac2a261fa7b4cd59d0907178e287efcaa3989e734104cb2eecf5d89ff460", "text": "should have the JSON attribute name \"items\", not \"minions\"\nDoh! Fix now and break clients?\nDefine Items and Minions and use Convertors to resolve it?\nSure. I'll make a fix.", "commid": "kubernetes_issue_1101", "tokennum": 45}], "negative_passages": []}
{"query_id": "q-en-kubernetes-73ce865f9c34194f1c7450d11e4c6f130974cd16147e0f9040323cc00396a57a", "query": "burst, containerLogsDir, osInterface, networkPlugin, runtimeHelper, httpClient, &NativeExecHandler{}, fakeOOMAdjuster, fakeProcFs, false, imageBackOff, false, false, true) dm.dockerPuller = &FakeDockerPuller{} <del> dm.versionCache = cache.NewVersionCache(func() (kubecontainer.Version, kubecontainer.Version, error) { return dm.getVersionInfo() }) </del> return dm }", "positive_passages": [{"docid": "doc-en-kubernetes-c9313de66f3508f8886cd07268b253d5e2cfa321359afb89838b6984a0afe883", "text": "The recently merged PR a version cache in dockertools, which makes the test  flaky. The reason is that injected error into fakedockerclient and then expected to see the error from right after that (See ). However, the error was consumed by the goroutine which periodically updates the version cache (See ). The docker daemon version is rarely updated, and we only need version once for each container creating, during which we also do container create, start, inspect #etc. 1) Do we care about the cost of the call so much that we have to introduce the complexity? 2) Kubelet periodically calls , can we rely on that to update the cache? Anyhow, at least, we should disable the cache or have a fake one in the unit test. :) /cc\nI once considered move this cache to runtime level, while thus may need to change runtime interface. What if only cache apiversion?\nWe can only get via , so there will still be the data race. :) One option is to update the version cache in , now kubelet periodically call to check the runtime status. Another better option is to cache the version in layer, now is under our control, we can refactor it with an additional argument indicating whether to use cached value or get directly from the daemon. If we cache the version only for performance, I prefer the second option which is cleaner and more efficient. :)\nOK, will look into this tonight\nThe unit test itself should not start a goroutine to update the cache (unless you're actually testing the goroutine). We should disable it anyway, as we often do in our unit tests. It also sounds like we don't need a goroutine dedicated for this. If we can tolerate the additional overhead from time to time, we can set a expiration time (e.g., 1 minute), and only call the runtime if the entry expires.\nTotally agree. :) Maybe a new function in wrapping the update logic, or wrapping the logic in the .\nexpiration time sounds good in this case\nThis is happening quite frequently - increasing priority to P0.", "commid": "kubernetes_issue_24298", "tokennum": 452}], "negative_passages": []}
{"query_id": "q-en-kubernetes-73ec152a766d272dce7a0fa9968b1ca77f18ba0d8df8ea2b522687ebd0a574a7", "query": "}) /* <del> Testname: allowPrivilegeEscalation=true. Description: Configuring the allowPrivilegeEscalation to true, allows the privilege escalation operation. A container is configured with allowPrivilegeEscalation=true and a given uid (1000) which is not 0. When the container is run, the container is run using uid=0 (making use of the privilege escalation). This test is marked LinuxOnly since Windows does not support running as UID / GID. </del> <ins> Release : v1.15 Testname: Security Context, allowPrivilegeEscalation=true. Description: Configuring the allowPrivilegeEscalation to true, allows the privilege escalation operation. A container is configured with allowPrivilegeEscalation=true and a given uid (1000) which is not 0. When the container is run, container's output MUST match with expected output verifying container ran with uid=0 (making use of the privilege escalation). This e2e Can not be promoted to Conformance as it is Container Runtime dependent and runtime may not allow to run. [LinuxOnly]: This test is marked LinuxOnly since Windows does not support running as UID / GID. </ins> */ It(\"should allow privilege escalation when true [LinuxOnly] [NodeConformance]\", func() { podName := \"alpine-nnp-true-\" + string(uuid.NewUUID())", "positive_passages": [{"docid": "doc-en-kubernetes-f8a45a347ca0a58053d8639059bb6be0a8ec66e1196dbd0290c02922abc9dcd2", "text": "/kind cleanup /area conformance /area test /sig node /sig testing /sig architecture /assign /assign We have a number of tests that only have the tag that may make sense as tests, we should identify whether these tests cases meet (or could meet) the . We should open PR's to promote these if so. I would advise starting with the test/common cases\nGitHub didn't allow me to assign the following users: mgdevstack, mkurylec. Note that only and repo collaborators can be assigned. For more information please see <detailsIn response to : /kind cleanup /area conformance /area test /sig node /sig testing /sig architecture /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\n/assign\nThe tests in test/e2enode don't actually get run as part of Conformance as near as I can tell. If we want to run them as part of conformance, they need to be migrated into test/e2e/common. Some of the tests in e2enode may not be able to be ported over because they assume a level access we don't have in a conformance environment.\nregarding this testcase: [sig-storage] HostPath should support r/w [NodeConformance]: It uses hostPath and privileged=true, to read/write from /tmp folder. Which would you suggest is the best orientation to overcome the privilege mode setting and allow its promotion?\n/assign\nRegarding , the suite runs the test only if the kubelet configuration was required to have the QOS (cgroups-per-qos) enabled. This configuration for the kubelet is selected at the time the cluster is set up. Looking for where this might be configured found: where is set to true. For other settings it is also configured to true. where is set to true. BUT also found where it is mentioned that the flag is no longer available. Questions: would it be ok to promote this test to be conformance, even it can be skipped based on configuration of the cluster? And not supported in the containerized kubelet?\nI would consider cgroups to be an implementation detail that Conformance shouldn't be verifying\nIt uses hostPath and privileged=true, to read/write from /tmp folder.", "commid": "kubernetes_issue_66875", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-73ec152a766d272dce7a0fa9968b1ca77f18ba0d8df8ea2b522687ebd0a574a7", "query": "}) /* <del> Testname: allowPrivilegeEscalation=true. Description: Configuring the allowPrivilegeEscalation to true, allows the privilege escalation operation. A container is configured with allowPrivilegeEscalation=true and a given uid (1000) which is not 0. When the container is run, the container is run using uid=0 (making use of the privilege escalation). This test is marked LinuxOnly since Windows does not support running as UID / GID. </del> <ins> Release : v1.15 Testname: Security Context, allowPrivilegeEscalation=true. Description: Configuring the allowPrivilegeEscalation to true, allows the privilege escalation operation. A container is configured with allowPrivilegeEscalation=true and a given uid (1000) which is not 0. When the container is run, container's output MUST match with expected output verifying container ran with uid=0 (making use of the privilege escalation). This e2e Can not be promoted to Conformance as it is Container Runtime dependent and runtime may not allow to run. [LinuxOnly]: This test is marked LinuxOnly since Windows does not support running as UID / GID. </ins> */ It(\"should allow privilege escalation when true [LinuxOnly] [NodeConformance]\", func() { podName := \"alpine-nnp-true-\" + string(uuid.NewUUID())", "positive_passages": [{"docid": "doc-en-kubernetes-b0f7522fd47a7c9f3d30009b5f18d7b37ba2aa8723a4c0ef112b90078054f0fc", "text": "Which would you suggest is the best orientation to overcome the privilege mode setting and allow its promotion? Michelle Au If my understanding is correct, on some platforms, writing to /tmp requires privileged. I don't see a way to to remove that requirement.\nIf my understanding is correct, on some platforms, writing to /tmp requires privileged. I don't see a way to to remove that requirement. Yeah writing to host doesn't seem like a thing we can expect of conformance tests. I wonder if it makes sense to tag this test with something to denote the requirement, ie: I see some tests in test/e2e_node use\nThe hostpath tests in already have a comment explaining this. Maybe the comment should be updated to be more clear that that is the reason why we can't add it to conformance.\nThat's /tmp on the host or in the container filesystem?\n/tmp on the host\nping what else remains to be done before we close this out? I am guessing that we want to close , is there anything beyond that?\nOnce tests under (issue- ) and are promoted we are good to close this issue. Short update for reference- None of [NodeConformance] tests from \"test/e2e_node\" seems eligible for [Conformance] promotion at this moment due to node level dependencies. Remaining [NodeConformance] tests from \"test/e2e\" has following status - Waiting for to be closed and then below tests would be promoted to Conformance Needs to be Promoted Can not be promoted to Conformance as //Slow by design Can not be promoted due to Node level dependency\nIssues 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\n/remove-lifecycle stale\n/lifecycle frozen\n/assign", "commid": "kubernetes_issue_66875", "tokennum": 428}], "negative_passages": []}
{"query_id": "q-en-kubernetes-74011e2b27e6fbc3f1b24d1134d404a0ef1fc87f0d9ed66c6b161588e2455265", "query": "}) } <ins> func getParams(featureList map[string]bool) string { if features.Enabled(featureList, features.SupportIPVSProxyMode) { return \"- --proxy-mode=ipvsn        - --feature-gates=SupportIPVSProxyMode=true\" } return \"\" } </ins> func getClusterCIDR(podsubnet string) string { if len(podsubnet) == 0 { return \"\"", "positive_passages": [{"docid": "doc-en-kubernetes-fdf6c8e5598e80992f62cef52eca112e7ba1d532fe8ace89dc932a5edac53dea", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: Currently, IPVS proxier does not run any e2e test cases. What you expected to happen: I think it's important to create test suite for IPVS in upstream CI which will help a lot in moving IPVS existing alpha. Anything else we need to know?: Let's work together. /sig network\nSelf /assign\nThere are to ways to do this work: , but doesn't support any kube-proxy config right now, so I had this pr , and also, need support it too, see this pr: kubernetes/kubernetes-anywhere build cluster. See this pr: kubernetes/test-infra The second way is much easier and faster, but I was told they gonna deprecated the , so in the long term, we still need and 's support. If anybody have better way or have some suggestion about this, please let me know, I'll be really appreciate, Thanks.", "commid": "kubernetes_issue_52834", "tokennum": 247}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7415173c57ead87619d3dabadb70718f60476ae65db71d31283a3cfa1a1802c9", "query": "glog.Infof(\"Starting APIServiceRegistrationController\") defer glog.Infof(\"Shutting down APIServiceRegistrationController\") <del> if !controllers.WaitForCacheSync(\"APIServiceRegistrationController\", stopCh, c.apiServiceSynced, c.servicesSynced) { </del> <ins> if !controllers.WaitForCacheSync(\"APIServiceRegistrationController\", stopCh, c.apiServiceSynced) { </ins> return }", "positive_passages": [{"docid": "doc-en-kubernetes-89e8d863e20723ba6498e9abf897dd4e49e26cad02c0dde0a4957b2eb3151e69", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Currently APIServiceRegistrationController watch service change and find the related APIServices related if any. Then it AddAPIService/RemoveAPIService for APIAggregator. I dig into the kube-aggregator and find it no need totally, because update APIServices status when related service or endpoint change. So if does not watch services, it will not miss any event for APIServices. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/cc\n/kind enhancement /sig api-machinery\n/assign\nthat does not follow. AvailableConditionController modifies the APIService object. APIServiceRegistrationController must still watch the APIService objects to observe those changes.\noh, I misread the description. You're saying APIServiceRegistrationController doesn't need to watch v1.Service objects", "commid": "kubernetes_issue_57836", "tokennum": 300}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7424831c3d31f727134eeba69d863878fb983c0be2b56f720316f7e9485698ec", "query": "var warnOnce sync.Once func newGCPAuthProvider(_ string, gcpConfig map[string]string, persister restclient.AuthProviderConfigPersister) (restclient.AuthProvider, error) { <del> // deprecated in v1.22, remove in v1.25 // this should be updated to use klog.Warningf in v1.24 to more actively warn consumers </del> warnOnce.Do(func() { <del> klog.V(1).Infof(`WARNING: the gcp auth plugin is deprecated in v1.22+, unavailable in v1.25+; use gcloud instead. To learn more, consult https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins`) </del> <ins> klog.Warningf(`WARNING: the gcp auth plugin is deprecated in v1.22+, unavailable in v1.25+; use gcloud instead. To learn more, consult https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke`) </ins> }) ts, err := tokenSource(isCmdTokenSource(gcpConfig), gcpConfig)", "positive_passages": [{"docid": "doc-en-kubernetes-78c3aac202d1e5d328f496362409af5f5e81f7978b044bd0fb2f29b228ab13af", "text": "We should drop the bit once in favor of a once gcp has a replacement. xref: /assign /milestone v1.24 /triage accepted /sig auth\nThe 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]:\nThe 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]:\n/remove-lifecycle rotten /lifecycle frozen\nI'm in the release 1.24 bug triage shadow. Does this issue still target release 1.24? If yes, would you please update the kind and priority fields for us to track it better?\nYes, definitely targeting 1.24 /priority important-soon /kind cleanup deprecation\nwould you please link the PR that solves this issue and update the status?\nThere is none yet. Waiting on GKE folks.\naddresses this issue.", "commid": "kubernetes_issue_103499", "tokennum": 393}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7425c8298fd95dbc48399390bc15f55f3f1537449a4fd39e14e07fc348a95920", "query": "<ins> /* Copyright 2020 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package testutil import ( \"strings\" \"testing\" \"k8s.io/component-base/metrics\" ) func TestNewFakeKubeRegistry(t *testing.T) { registryVersion := \"1.18.0\" counter := metrics.NewCounter( &metrics.CounterOpts{ Name: \"test_counter_name\", Help: \"counter help\", }, ) deprecatedCounter := metrics.NewCounter( &metrics.CounterOpts{ Name:              \"test_deprecated_counter\", Help:              \"counter help\", DeprecatedVersion: \"1.18.0\", }, ) hiddenCounter := metrics.NewCounter( &metrics.CounterOpts{ Name:              \"test_hidden_counter\", Help:              \"counter help\", DeprecatedVersion: \"1.17.0\", }, ) var tests = []struct { name     string metric   *metrics.Counter expected string }{ { name:   \"normal\", metric: counter, expected: ` # HELP test_counter_name [ALPHA] counter help # TYPE test_counter_name counter test_counter_name 0 `, }, { name:   \"deprecated\", metric: deprecatedCounter, expected: ` # HELP test_deprecated_counter [ALPHA] (Deprecated since 1.18.0) counter help # TYPE test_deprecated_counter counter test_deprecated_counter 0 `, }, { name:     \"hidden\", metric:   hiddenCounter, expected: ``, }, } for _, test := range tests { tc := test t.Run(tc.name, func(t *testing.T) { registry := NewFakeKubeRegistry(registryVersion) registry.MustRegister(tc.metric) if err := GatherAndCompare(registry, strings.NewReader(tc.expected), tc.metric.FQName()); err != nil { t.Fatal(err) } }) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-b57bf0f1b2dd71c1293d1dafb95c6e51debc5c1d26878053edb8d335b76a3a11", "text": "What would you like to be : Once a metric be deprecated, we should update the unit test accordingly if there is any. We need to work out a way for a unit test freely select codebase version, and also should make sure the unit test won't fail in the subsequent release. Why is this needed: Deprecated also needs to be protected. /sig instrumentation /assign", "commid": "kubernetes_issue_86292", "tokennum": 81}], "negative_passages": []}
{"query_id": "q-en-kubernetes-745d381fa41da15f155ef8da60ae55fcca0f06dadec83246b90b044f9bd74fa6", "query": "} if status == health.Healthy { result = append(result, minion) <ins> } else { glog.Errorf(\"%s failed a health check, ignoring.\", minion) </ins> } } return result, nil", "positive_passages": [{"docid": "doc-en-kubernetes-24df73a6db05c45f0cac4e827cf56a2dc89af2bfb599ee7ed6ea71c4b1f5c613", "text": "Should be able to tell from logs if a minion isn't present because cloud provider didn't tell us about it, or if it's failing health checks.", "commid": "kubernetes_issue_612", "tokennum": 35}], "negative_passages": []}
{"query_id": "q-en-kubernetes-74890f172185e57f4f5c1afbf79ec5ad22bdd6d130ea728d6090650e7e706c5a", "query": "go_library( name = \"go_default_library\", srcs = [ <ins> \"conntrack.go\", </ins> \"dns.go\", \"dns_common.go\", \"dns_configmap.go\",", "positive_passages": [{"docid": "doc-en-kubernetes-7bfb1f284722c2f05aa84834ae56662d5ec19fb895a91cc774b04328b8cdc59d", "text": "Which jobs are flaking: ci-kubernetes-e2e-gce-scale-correctness Which test(s) are flaking: [sig-network] Services should be able to preserve UDP traffic when server pod cycles for a NodePort service Testgrid link: https://k8s- Reason for failure: /sig network /assign\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nCRI-O CI is also hitting this failure. We have been unable to reproduce locally. our CI runs on aws\nhmm, I only see 1 failure out of 4 and seems that the connectivity didn't work at all\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\n/assign\nGitHub didn't allow me to assign the following users: JacobTanenbaum. 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\n/cc Saw the test flaking recently: Wondering if this is just a timeout issue.", "commid": "kubernetes_issue_91236", "tokennum": 320}], "negative_passages": []}
{"query_id": "q-en-kubernetes-74890f172185e57f4f5c1afbf79ec5ad22bdd6d130ea728d6090650e7e706c5a", "query": "go_library( name = \"go_default_library\", srcs = [ <ins> \"conntrack.go\", </ins> \"dns.go\", \"dns_common.go\", \"dns_configmap.go\",", "positive_passages": [{"docid": "doc-en-kubernetes-7ebfc2af23ebf8477a19d5b139a7e0f62f200d8158a5532a965c9eb49bf73a96", "text": "Maybe we can increase the timeout and/or switch to a TCP based test:\nthe test should use UDP, and UDP is unreliable by definition ... however is curious that most of the failures happen because it is not able to communicate with the first pod I think that is something that should be investigated, I've analyzed some occurences and it works fine for the second pod, however, the UDP losses should be totally random\nHi everyone, yeah so.. collecting some data on this... using a two node kind cluster, locally, with the antrea plugin, it passes using a 4 node AWS cluster with the antrea CNI plugin, it failed using a two node kidn cluster locally with calico, it passes So I guess the best reproducer is to run these tests, for now, in the cloud.... Now that I have a reproducer for this maybe can live debug it some time next wk with one of yall :)\nbear in mind that this test is connecting to a nodePort in the node IP, the test is functionally correct, it may be flaky due to the unreliable UDP nature or due to the pod scheduling, but if is failing constantly it has to be environmental.\nSecond failure after two weeks of green 5k runs:\nyep, :/ https://k8s-|UDP /assign\n/reopen I'm afraid this is going to be challenging :smile: The difference now is that we are testing NodePort and ClusterIP If both fail, we can blame the test for sure, If only NodePort fails, we need to check the job, if GCE or KIND If only ClusterIP fails, ... :thinking:\nReopened this issue. <detailsIn response to : /reopen I'm afraid this is going to be challenging :smile: 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\nWe're hitting this really frequently in 5k-node tests. So I started looking a little bit into that.", "commid": "kubernetes_issue_91236", "tokennum": 445}], "negative_passages": []}
{"query_id": "q-en-kubernetes-74890f172185e57f4f5c1afbf79ec5ad22bdd6d130ea728d6090650e7e706c5a", "query": "go_library( name = \"go_default_library\", srcs = [ <ins> \"conntrack.go\", </ins> \"dns.go\", \"dns_common.go\", \"dns_configmap.go\",", "positive_passages": [{"docid": "doc-en-kubernetes-5846160d0947d31469e9f6af93fd879e379d05716d3adf8932316babb4b3ae6c", "text": "I don't have full understanding of what exactly is happening, but I already see a couple things that may be causing issues: when creating the first pod, you wait for corresponding endpoint for that being created; but that doesn't mean that kube-proxy was actually programmed correctly at that time (in general it isn't); given iptables programming is rate-limitted, it may easily happen that actually programming happens 10s+ later That explains some delays, but it doesn't explain e.g. this run: where iptables were programmed at but the test didn't respond until If someone more familiar with networking stuff could look into it, it would be great. - can you help triaging ^^ for deletions it's even worse, because you don't even wait for endpoints to be there (i.e. Endpoints can still contain the old pod when the test start pinging to look for the second one) So I claim that timeouts are visibly to low in this test, but I suspect it's not everything. I will send out the first PR that tries to improve it in couple minutes.\nthanks wojtek, have been slammed but Ill try to collect more data on it this wknd as well.\nIt seems that my PR didn't really help much. We should dig deeper, but I would need someone with more networking expertise to look a bit into\nActually - it seems only failures from one group are on non . So maybe that's actually related. The non-kind related ones look like:\nOK - for this one, I actually know what is happening - I will send out a PR with a fix for this too.\nfor the KIND jobs already increased the resource requests on some of the jobs, there are issues on KIND jobs with kube-proxy not able to take the iptables lock and not being able to create the iptables rules for the services until the next resync\nis to fix the flakes I mentioned above; all other flakes seem to be kind-oriented to me (which I'm not super familiar with).\nWe did not adjust the CPU on all jobs yet, pending how to manage that on prow ... I do see just a few other flakes at the bottom of the triage dashboard that look like timeouts instead.\nActually - almost all failures are effectively timeout. The top one that is is actually also a timeout. Didn't look into kind failures, but this may easily be related to iptables issues.", "commid": "kubernetes_issue_91236", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-74890f172185e57f4f5c1afbf79ec5ad22bdd6d130ea728d6090650e7e706c5a", "query": "go_library( name = \"go_default_library\", srcs = [ <ins> \"conntrack.go\", </ins> \"dns.go\", \"dns_common.go\", \"dns_configmap.go\",", "positive_passages": [{"docid": "doc-en-kubernetes-0543f3a3993360bbed011d4060e35a21f3f79414d82ea25f247261ac2b705804", "text": "After my second deflaking PR, we seem to be in the stage where: tests are failing on dozens of different things (probably iptables-issues related) tests are failing only on NodePort tests on \"Failed to connecto to backend 1\" which it would be great if someone else could look into (kube-proxy seemed to be programmed correctly based on logs)\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\nThis has failed again - Linking to specific part of log where timeout occurred .... we see this\nSo reviewing the above logs note how in STEP: checking client pod connected to the backend 1 on Node IP 10.138.0.5 28 attempts are made all in the 25th second of the 2 minute at 11am Should this Step back off and wait a few seconds in between tries? So looking at this code we see the following\nFrom reading ... the intention expressed in the test code looks good to me. It is not clear to me why there is a mismatch between the 28 tries in the POD Client Logs and the expressed intention running the logContainsFn(podBackend1) every 5 seconds still digging ....\nwe are trying to catch one failure in this PR that has additional debugging, it dumps the conntrack table of the nodes on a failure\nfor those following the issue, we've extra debugging to the test so it dumps the whole conntrack table once it finish. We should look that there is NO stale entries, connections from the pod client to the deleted endpoint) and there is conntrack entries to the new endpoint from the pod client.\n- we have runs with the conntrack dump now, e.g. this one: would you be able to take a look into it?\nnot yet :/ , but I think tomorrow can have some time\ncc\nFor anyone reproducing this issue btw, you need a multinode k8s cluster (it isnt doable on kind i guess bc less likeliehood of network failures when running local) -\nCurious about two potential hypotheses to fix this, have we looked into either of these? 1) can we confirm that is turned on/off? 2) is it possible that scaling the number of coredns replicas could help ?", "commid": "kubernetes_issue_91236", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-74890f172185e57f4f5c1afbf79ec5ad22bdd6d130ea728d6090650e7e706c5a", "query": "go_library( name = \"go_default_library\", srcs = [ <ins> \"conntrack.go\", </ins> \"dns.go\", \"dns_common.go\", \"dns_configmap.go\",", "positive_passages": [{"docid": "doc-en-kubernetes-66f25b05b1c90d93aad713cb7c943585d55afc690fe7a4f7e9fa0b7a5a5f23b1", "text": "3) Would simulating this in kind by overloading coredns be a possibility as a way to make a more reproducible bug model?\nregarding 1) kubeadm does not ship nodeLocalDNSCache I don't think GCE kube-up does by default either\nok, so now im curious about (2) - i.e. what if we just bumped coredns replica count?\ninteresting, :thinking: why do you think is a DNS thing? the netcat command that polls the services use the IP addresses not the hostname. I think that it has to be related to some iptables/conntrack race or similar,at least in KIND jobs we know that we have an iptables problem that affects network tests, that has to be fixed before this because it affect this test You can instrument the test locally with this and dump the state of iptables and conntrack on failure if you are able to reproduce it\ni figured DNS bc i believe its known that conntrack and DNS at scale can get very messy, right ?\none other curious thing about this test is that we only create 2 pods in the recycling event for the svc. that likely means that any real error is hidden by chance..... If we created a 3rd pod, then we might potentially double the failure rate thus making the flakyness go away and expose the real underlying issue .\nThere's an invocation of dumpConntrack(cs) here [sig-network] Conntrack should be able to preserve UDP traffic when server pod cycles for a ClusterIP service\nis updating the logging to run in an infinite loop ..\nThis is improving in KIND with the new changes we rolled out yesterday, let's see how it evolves this week\n- which changes ? Are you saying this is no longer reproducible on Kind?\nthere was a lot of noise in the CI signal, especially in KIND jobs due to the CNI portmap bug we finally solved yesterday now we should have a better signal and we can go to the bottom because probably the failure will be \"legit\" and not a consequence, so this comment should apply\nHi ! I ran this a few times on kind and it passed, but I see , so I'm going to try the loop approach you suggested. Here's what I'm using to test:\nquick note, <- potential motivation to possibly have runnable on some subset of tests in upstream eventually, i.e.", "commid": "kubernetes_issue_91236", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-74890f172185e57f4f5c1afbf79ec5ad22bdd6d130ea728d6090650e7e706c5a", "query": "go_library( name = \"go_default_library\", srcs = [ <ins> \"conntrack.go\", </ins> \"dns.go\", \"dns_common.go\", \"dns_configmap.go\",", "positive_passages": [{"docid": "doc-en-kubernetes-deebb69aabcaf9005201c68e52f1f862e88c30f5231beaa0034b1d576abe9a4a", "text": "so we can do things like to reproduce this sort of thing. matt did you get around to the 'try-till-it-fails' scenario?\nI haven't been able to get it to fail on kind yet, -- 100 cycles and 0 failures on a three-node kind cluster! I'm letting the loop run for a few hours, will check back in when I have that data. Is it worth running this test on a non-kind environment?\nI ran for several hours on my mac, through 1144 iterations no error yet. My conclusion: this test isn't flaky on KinD. Possible next step: run a large number of iterations of the same test on a GKE cluster.\nFlakes on kind are also happening:\nnot many since the portmap fix on the 14th though ( / ) <img width=\"1111\" alt=\"Screen Shot 2020-07-23 at 11 45 46 PM\" src=\"https://user-\"\nAgree - it's much better than it was before.\nI was analyzing this failure, the problem is that kind jobs does not have verbosity enough in kube-proxy We can see that the packet was never replied, this is the NAT entry from client -nodePort in the node with the client This is the same flow, but in the node with the server and the pod-server-1 seems to be healthy we need more logs :eyeglasses:\nWe have an open ticket to bump those in CI, it's just been lost in the noise. We should still do that. Antonio Ojea <:\nIf you are busy just assign it to me, I'll need this verbosity soon :)\nIt's in the kind repo, shouldn't be too hard to find, we have ~60 open atm. Antonio Ojea <:\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\nI made another attempt to reproduce these failures locally on KinD, but still no success. Here's what I did: create a KinD cluster run two instances of sonobuoy at the same time This took ~4 hours to run; all the kube tests passed and sonobuoy reported all successes.", "commid": "kubernetes_issue_91236", "tokennum": 494}], "negative_passages": []}
{"query_id": "q-en-kubernetes-74890f172185e57f4f5c1afbf79ec5ad22bdd6d130ea728d6090650e7e706c5a", "query": "go_library( name = \"go_default_library\", srcs = [ <ins> \"conntrack.go\", </ins> \"dns.go\", \"dns_common.go\", \"dns_configmap.go\",", "positive_passages": [{"docid": "doc-en-kubernetes-738ad9cb1373dead6b2f556ac241cd0c8a6cc7a0f09950111e765d9eb1dab68b", "text": "Would love to help out in reproing this, I'm at a loss for good next step so any suggestions welcome!\nthat's the problem with these flakes, they are not easy to repro, and with this low rate of failures it may be caused for combination of running tests, environmental problems (cpu, memory, ...) , ... I always start for checking the current failures and try to find patterns\nLet's take a look to one occurrence The tests fails because can't connect to the first pod If we check the code of the tests, we can see that it always uses the port as source port, we can use that to identify the nodePort assigned interesting thing here, we are source nating the pod ip, and we don't see any other conntrack entry The test verifies it has endpoints however, kube-proxy is using endpointlsices since this version but it has no entries so the iptables rules to forward the traffic are not there Seems we have to adapt this function in the e2e framework to use endpointslices cc: EDIT seems that this function is being used by all the network tests that can cause flakes if the endpoint is updated before the endpointslice (we switched recently kube-proxy to use the later)\nGreat catch. Ideally this function should validate if both Endpoint and appropriate EndpointSlice objects(s) exist.\nActually - let me take it and send a PR for it.\nis out for review\nInteresting failures here It fails to connect to the first pod\nHmm - I took a quick look at kube-proxy logs and these look fine to me....\nI clicked too fast, sorry ... I was looking at the wrong service and I though I've found something\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry.", "commid": "kubernetes_issue_91236", "tokennum": 416}], "negative_passages": []}
{"query_id": "q-en-kubernetes-74890f172185e57f4f5c1afbf79ec5ad22bdd6d130ea728d6090650e7e706c5a", "query": "go_library( name = \"go_default_library\", srcs = [ <ins> \"conntrack.go\", </ins> \"dns.go\", \"dns_common.go\", \"dns_configmap.go\",", "positive_passages": [{"docid": "doc-en-kubernetes-7b1ee5acca525c6b88a5b6825056ab7c4df586768503c885715c9a87d944744a", "text": "\u200d\njust saw it as well\ncan you please add links to the job with the failures, I just merged new code to improve the logging 2 days ago\nok, here there is a new occurrence and with the new debug logs is easier to follow has unreplied conntrack entries: looking at the other side The iptables rules are there but no conntrack entries related to 10.244.2.32\nIn I revert PR with debug info as I think that it likely caused significant memory growth in scalability tests, but we have one run that has finished without being killed by OOMKiller (I increased memory limit for that jobs as a mitigation). Maybe logs from this run will be useful for debugging:\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\nTwo more flakes today:\nIt seems that the packet never gets DNATed in the receiving host, so it does not reach the pod in the node. There is the same test that is using ClusterIP instead of NodePort that is more reliable. This is being a tough one\n/triage accepted\nYesterday's flake - I don't think I'm seeing the log messages from the latest log PR you made ? Or are the prow logs not logging at a high-enough level?\nLogs are there, please bear with me: The error on the test is: click on the job failure and you'll see a larger output where you can see the server pod name and get the node where the pod is running: and the client-pod name and its node: and the flow we are looking for: with the node-name we can get the kube-proxy logs there, clicking in artifacts: and you can see the \"new\" conntrack log entries : and in the client: wow, there is a kernel bug there , can it be related? :thinking:\nwohoo - some progress :) I'm not an expert here, but I think it can be? Adding here - they may be able to confirm/reject the hypothesis.\nThis kernel panic may be a coincidence, maybe this is the reason\nAdding some recent failures:\nSpotted another flake today:\nAnother flake in the 5k job:", "commid": "kubernetes_issue_91236", "tokennum": 495}], "negative_passages": []}
{"query_id": "q-en-kubernetes-74bd8f33efc87cc69096e7d9eaea99df730af0f019dfc9b0d89ef15002239232", "query": "// Create a deployment to delete nginx pods and instead bring up redis pods. deploymentName := \"redis-deployment\" Logf(\"Creating deployment %s\", deploymentName) <del> _, err = c.Deployments(ns).Create(newDeployment(deploymentName, replicas, deploymentPodLabels, \"redis\", \"redis\")) </del> <ins> _, err = c.Deployments(ns).Create(newDeployment(deploymentName, replicas, deploymentPodLabels, \"redis\", \"redis\", extensions.RollingUpdateDeploymentStrategyType)) </ins> Expect(err).NotTo(HaveOccurred()) defer func() { deployment, err := c.Deployments(ns).Get(deploymentName)", "positive_passages": [{"docid": "doc-en-kubernetes-ceb20554e653f6657baad1bbb36c40e66d8a76887956e3c674b77febc82d4455", "text": "There's some practical limit on the number of concurrent access tokens that can be used in a Kubernetes cluster before it begins to spend all of its time in the authn stack verifying them. Absent fixes to it was < 500; with the fixes linked there it's still not infinitely scalable-- I still hit (what I believe to be) with ~ 5k unique tokens @ ~700QPS. This request is to this dimension an official name & definition, and list it with others, e.g. here: it it have a useful value (I think it should be 10k) /kind bug /sig scalability\n/cc\noh and 4. add tests which verify it is as high as believed.\ncc since projected tokens will increase the number of unique tokens\n/sig auth\nLRUs are not good at scaling and sharding has some major pitfalls as pointed out. I would suggest that we try to drop the LRU cache for successful authentication results in the token cache. The main benefit of using an LRU here is bound cache size. Entries in the token cache have a fast expiration independent of the LRU policy. The records probably take up O(2kb) (guesstimate) of memory. Given that these are successful attempts with presumably valid tokens, I don't think we are getting any benefit from the LRU. If we don't have a constraint on fixed cache size, we can back the token cache with a sync.Map and run a single background goroutine to periodically walk the map and remove expired entries. This would fix the problematic locking and eviction due to nonuniform distribution of tokens over shards. The failure cache is less important and we don't cache failures by default. If we consider this the \"slowpath\", we can probably leave it as. If that's not good enough, we have a couple options (with various tradeoffs) to improve it.\nIf off by default is not enough, more reasoning why the failed cache is not super useful: it might help with an accidental DoS but it doesn't prevent anything actively malicious DoS. I think we can focus our improvements on the success cache.\n/assign He is already working on adding an explicit test for it.\nhas taken it over and is actively working on this. Unfortunately, I cannot assign this issue to him as he's not a k8s member yet\nIt's not closed - all testes must be submitted and appropriate documentation must be\nThanks everyone!!", "commid": "kubernetes_issue_83375", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-74c4bd2d0b4b4776c8dcc18cb2a4e9a3c6a50fa495f4f282fffa51bdb2d33dcf", "query": "t *testing.T, expectedDetachCallCount int, fakePlugin *volumetesting.FakeVolumePlugin) { <del> if len(fakePlugin.Detachers) == 0 && expectedDetachCallCount == 0 { </del> <ins> if len(fakePlugin.GetDetachers()) == 0 && expectedDetachCallCount == 0 { </ins> return } err := retryWithExponentialBackOff( time.Duration(5*time.Millisecond), func() (bool, error) { <del> for i, detacher := range fakePlugin.Detachers { </del> <ins> for i, detacher := range fakePlugin.GetDetachers() { </ins> actualCallCount := detacher.GetDetachCallCount() if actualCallCount == expectedDetachCallCount { return true, nil", "positive_passages": [{"docid": "doc-en-kubernetes-8eb466904f09832d9690a82d180fa467ae255966eba3f5f112ba1d2e4e87f745", "text": "Looks like similar issue with\nThat's the PV controller this is the attach controller, thus separate issues.", "commid": "kubernetes_issue_26377", "tokennum": 21}], "negative_passages": []}
{"query_id": "q-en-kubernetes-74cf27df18e88f565c42ae5aa3fcfd3ff0d6e4088880ba8533c9e645202a244d", "query": "return 1 fi <ins> # provide `--pull` argument to `docker build` if `KUBE_BUILD_PULL_LATEST_IMAGES` # is set to y or Y; otherwise try to build the image without forcefully # pulling the latest base image. local DOCKER_BUILD_OPTS=() if [[ \"${KUBE_BUILD_PULL_LATEST_IMAGES}\" =~ [yY] ]]; then DOCKER_BUILD_OPTS+=(\"--pull\") fi local -r docker_build_opts=\"${DOCKER_BUILD_OPTS[@]}\" </ins> for wrappable in \"${binaries[@]}\"; do local oldifs=$IFS", "positive_passages": [{"docid": "doc-en-kubernetes-5881ca0980b851b5719338c7fae783dda8e5f4172ff43857090ef00a488ce809", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: when I run , found bound variable err. What you expected to happen: Build success How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ):Linux paasn1 4.14.78-300.el7.Centos.x8664 SMP Sat Jan 5 15:49:43 CST 2019 x8664 x8664 x8664 GNU/Linux Install tools: Network plugin and version (if this is a network-related bug): Others: GNU bash version 4.2.46(2)-release (x8664-redhat-linux-gnu) Copyright (C) 2011 Free Software Foundation, Inc.\n/sig release", "commid": "kubernetes_issue_82962", "tokennum": 236}], "negative_passages": []}
{"query_id": "q-en-kubernetes-74fd5c00cce4eb5c167d5de9e56991ec6c4c3677102ba3da67527a31723773d1", "query": "input MicroTime }{ {MicroTime{}}, <del> {DateMicro(1998, time.May, 5, 1, 5, 5, 50, time.Local)}, </del> <ins> {DateMicro(1998, time.May, 5, 1, 5, 5, 1000, time.Local)}, </ins> {DateMicro(1998, time.May, 5, 5, 5, 5, 0, time.Local)}, }", "positive_passages": [{"docid": "doc-en-kubernetes-56cd908854c413b8fe52b6acbb170713ddc1a064a7bd9d42b4a3ba81ae7efcaf", "text": "Found some error logs when sending series events to apiserver: seems the later eventTime differed from the first one in series events After investigation, I found the problem was in the marshal. MicroTime is supposed to work on microsecond level precision, but init with nanosecond level precision, in this case, generates microsecond level precision data and generates nanosecond level precision, so when unmarshalled, the new time is not considered the exactly same as the original time (they are different at nanosecond level) MicroTime marshal should work at same precision for json and proto, so unmarshal can generate the exactly same MicroTime result: This causes the series events won't be updated on api-server after created master <details</details<details</details<details</details<details</details<details</details\n/sig api-machinery\n/assign\nGood catch... we'd probably need to truncate to microseconds when marshaling and unmarshaling proto to ensure any already persisted data is fixed up when read. Something like this:\nThanks for advice, going to send a PR soon", "commid": "kubernetes_issue_111928", "tokennum": 247}], "negative_passages": []}
{"query_id": "q-en-kubernetes-75062d570a53a521afef67ca4f68c770e526b1d547a8ac38d6f9c56fc9bb5083", "query": "Hard_rename log message [FILTER] <ins> Name        modify Match       winevt.raw Hard_rename Message message [FILTER] </ins> Name         parser Match        kube_* Key_Name     message", "positive_passages": [{"docid": "doc-en-kubernetes-89b11fc4c25f0b72d5f027a149a029fe0341e3d491bf3200f9e9687686d8fec6", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --On Windows 20H2 we are observing crashloops with fluent-bit due to a malformed Windows Event Log entry in the Security log. Fluent-bit to not crash loop. Bring up a GCE Windows cluster on Windows 20H2. You may see a loss of logs. Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others: /sig windows /triage accepted", "commid": "kubernetes_issue_102023", "tokennum": 170}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7533904bb03a72fbf692721e06056562020b17702e5a6869c3a505373e81f10e", "query": "return &os.PathError{Op: \"fstat\", Path: file.Name(), Err: err} } <del> // Skip chown if uid is already the one we want. if int(s.Uid) == u.Uid { </del> <ins> // Skip chown if uid is already the one we want or any of the STDIO descriptors // were redirected to /dev/null. if int(s.Uid) == u.Uid || s.Rdev == null.Rdev { </ins> continue }", "positive_passages": [{"docid": "doc-en-kubernetes-3a5f1791fd28a186fcf23c773fa97525e98fb83cc70e7098ac61d449614dcefb", "text": "opencontainers/runc has fixed three CVEs: Latest runc is pulled by k/k Check runc version in file No response n/a n/a <details</details<details</details<details</details<details</details\n/assign /sig security architecture release\n/triage accepted", "commid": "kubernetes_issue_117094", "tokennum": 68}], "negative_passages": []}
{"query_id": "q-en-kubernetes-757dec5aea8d65fe714da4e929418f8d1b34d11baef1a5ab295f3751b8b5f423", "query": "err = gce.waitForRegionOp(op, region) if err != nil { glog.Warningf(\"Failed waiting for Forwarding Rule %s to be deleted: got error %s.\", name, err.Error()) <ins> return err </ins> } } op, err = gce.service.TargetPools.Delete(gce.projectID, region, name).Do()", "positive_passages": [{"docid": "doc-en-kubernetes-9fca6378f8b8df6d20b226b62d39deddc0dd6ba6166f0f70fb99239f64c63f5d", "text": "All of our external load balancer tests failed for the better part of a day due to the GCE project that our tests run in hitting its quota for number of target pools. While the target pools have been deleted, the fact that we hit our quota indicates that there must be a leak somewhere, and we need to plug it.\nFor reference, the previous issue was\nCould the leakage be related to ? The quota exhaustion occurred about 22 hrs after that.\nI'd guess that this is due to GetTCPLoadBalancer returning that the load balancer doesn't exist if the forwarding rule is gone, ignoring the target pool, while the service controller considers its deleting done if the cloud provider says that the load balancer doesn't exist. I that logic to the cloud provider because the other implementations of DeleteTCPLoadBalancer weren't/won't be idempotent in the sense of returning ok if the LB doesn't exist. To fix it, we'll either need to make sure all Delete implementations are idempotent and remove the Get call in the controller, or add a method along the lines of IsTCPLoadBalancerDeleted to ask the cloud provider whether all pieces of it have been completely cleaned up. We can't make GetTCPLoadBalancer check that because it's relied on to tell us whether or not the balancer is fully created.\nCopying over my commentary from on why the GKE e2e tests are leaking so many forwarding rules and target pools vs the GCE tests:\nIs there a way for the services test to wait for the service controller to clean up the external resources before finishing (without just doing a sleep)?\nNot without polling GCE directly for whether the resources still exist, although that may be worth it as a workaround. What would be perfect is that clean-up-all-cloud-provider-resources API method that we talked about a couple months ago.\nCan we not perhaps use GCE namespaces or projects as a cheap way of getting this here?\nI don't believe so. We can't use projects due to the fact that projects can't be programatically created (they're intended to be long-lived). I'm not aware of anything along the lines of a GCE namespace other than networks, which won't work because target pools and forwarding rules unfortunately don't seem to be scoped to networks.", "commid": "kubernetes_issue_7753", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-757dec5aea8d65fe714da4e929418f8d1b34d11baef1a5ab295f3751b8b5f423", "query": "err = gce.waitForRegionOp(op, region) if err != nil { glog.Warningf(\"Failed waiting for Forwarding Rule %s to be deleted: got error %s.\", name, err.Error()) <ins> return err </ins> } } op, err = gce.service.TargetPools.Delete(gce.projectID, region, name).Do()", "positive_passages": [{"docid": "doc-en-kubernetes-d79b213781c20847fbb47c058c0afaba60ed2f1d9f5b51e77a0a4cda944c52e0", "text": "The target pool leak in the code might be fixed, but the forwarding rule + target pool leak from deleting GKE clusters too quickly is certainly still happening. Reopening for the sake of that half of the issue.\nCan we just add a short sleep to jenkins after the last test has run before it deletes anything?\nYes, you could add a sleep to Ginkgo's AfterEachSuite(): But I'd be concerned about what the upper bound on the sleep period is. Can we get the tests and code in sync with a 1 minute latency here? (e.g. if the controller garbage collects every 60 seconds, then the test only needs to sleep for 60 sec?) And add a BEEG comment to the test's sleep config noting that increasing the sleep time will not improve things, otherwise I'm pretty sure that someone noting flakes in this test in future will think \"maybe I should just increase the sleep period a little bit.\"\nActually, thinking about this a little more, it would be better to put the \"sleep\" logic in the k8s master teardown procedure (i.e. not in the e2e tests or in Jenkins), because otherwise users are going to run into the same resource leakage problems as we are. So master deletion blocks on cleanup of backend cloud resources.\nThere's no way to block master deletion from the master itself. The test framework (or user) just pulls the rug out from underneath the master. See\nRobby's right -- is the real solution to this, but until we have that the best we can do is to have the wait happen elsewhere. The options seem to be: GKE itself Ginkgo's post-testing logic Jenkins' teardown logic I don't like putting it in GKE, because arbitrarily slowing down our API makes for a poor experience for the majority of people that don't still have resources being deleted. I'm not eager to put it in Gingko either, since won't that sleep also take effect whenever anyone runs an e2e test locally against a dev cluster? Putting it in the Jenkins logic makes the most sense to me. I'll send a PR and cc you.\nWe may also want to change the kube-down logic to bring down the master and then nodes in parallel to both speed it up and more closely resemble GKE's teardown logic.\nI've deleted the old forwarding rules and target pools from the project.", "commid": "kubernetes_issue_7753", "tokennum": 530}], "negative_passages": []}
{"query_id": "q-en-kubernetes-757dec5aea8d65fe714da4e929418f8d1b34d11baef1a5ab295f3751b8b5f423", "query": "err = gce.waitForRegionOp(op, region) if err != nil { glog.Warningf(\"Failed waiting for Forwarding Rule %s to be deleted: got error %s.\", name, err.Error()) <ins> return err </ins> } } op, err = gce.service.TargetPools.Delete(gce.projectID, region, name).Do()", "positive_passages": [{"docid": "doc-en-kubernetes-6b81898435dc239c0c98669b4836ce5b1423be788127f142aa9eb15c198137cf", "text": "I'll periodically check to see whether anything is leaked after this point. I apologize if the deletions affected any running tests - everything looked to only be from GKE and parallel e2e runs.", "commid": "kubernetes_issue_7753", "tokennum": 42}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7594f092355a5bc5de3628251b80f8ee7d09e6e990b3b8284693c9a26ddfe3ac", "query": "<ins> /* Copyright 2016 The Kubernetes Authors All rights reserved. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package core import ( \"k8s.io/kubernetes/pkg/api\" \"k8s.io/kubernetes/pkg/runtime\" ) func addDeepCopyFuncs(scheme *runtime.Scheme) { if err := scheme.AddGeneratedDeepCopyFuncs( api.DeepCopy_api_DeleteOptions, api.DeepCopy_api_ExportOptions, api.DeepCopy_api_List, api.DeepCopy_api_ListOptions, api.DeepCopy_api_ObjectMeta, api.DeepCopy_api_ObjectReference, api.DeepCopy_api_OwnerReference, api.DeepCopy_api_Service, api.DeepCopy_api_ServiceList, api.DeepCopy_api_ServicePort, api.DeepCopy_api_ServiceSpec, api.DeepCopy_api_ServiceStatus, ); err != nil { // if one of the deep copy functions is malformed, detect it immediately. panic(err) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-5056a2515a29befdf589a74f13db031ed4142bbabfa8d2c37cafac2de4fccaea", "text": "I started the federation-apiserver and went to and got the following output: Expected: I should have got an empty v1.ServiceList Any idea on what we are doing wrong? Have you guys seen this error?\nI think your deep copiers or conversion functions are not getting registered properly. If you look at my change in , some places are inappropriately registering with api.Scheme instead of the passed in scheme. Maybe you have that problem or a similar one, since I think you guys copied some code. , Nikhil Jindal wrote:\nDeep copy generation was slightly broken as well - you may want to double check that they are registered. On May 23, 2016, at 5:50 PM, Daniel Smith wrote: I think your deep copiers or conversion functions are not getting registered properly. If you look at my change in , some places are inappropriately registering with api.Scheme instead of the passed in scheme. Maybe you have that problem or a similar one, since I think you guys copied some code. , Nikhil Jindal wrote: \u2014 You are receiving this because you are on a team that was mentioned. Reply to this email directly or view it on GitHub\nI got the same error with latest branch, as I was swamping on service controller, so I use a previous version and worked around it.\ndeep copies were indeed missing, but adding them hasnt fixed the issue. Will debug more. is my PR to add the deep copies cc Please feel free to file issues for any such problem you face. We need to fix all these issues. Its good if we know about them early. Thanks!\nfixes this", "commid": "kubernetes_issue_26111", "tokennum": 335}], "negative_passages": []}
{"query_id": "q-en-kubernetes-75b6393280866c79efe2b580c4cb85b12373b210e07e9124ecde60d9d092c237", "query": "require ( github.com/gogo/protobuf v1.3.2 google.golang.org/grpc v1.51.0 <ins> k8s.io/klog/v2 v2.80.1 </ins> ) require ( <ins> github.com/go-logr/logr v1.2.3 // indirect </ins> github.com/golang/protobuf v1.5.2 // indirect github.com/google/go-cmp v0.5.9 // indirect golang.org/x/net v0.4.0 // indirect", "positive_passages": [{"docid": "doc-en-kubernetes-82432c9a9613bf4aed980cc8db469ba43857eb8e48c1e0dd0f39492115206ab6", "text": "generation for local KEK based on counter; also rotate once a week even if the counter does not hit 2 million? using AES-GCM encryption of local KEK ref: The implementation would be to the directory.\n/sig auth /triage accepted\n/assign\nGitHub didn't allow me to assign the following users: ibihim. 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\n/assign\nthank you !\n/milestone v1.26\nHi bug-triage shadow team member for 1.26 here. Looks like this issue is in the 1.26 milestone, but has been moved to 1.27. Is there something else or should this issue go to 1.27 as well? Thank you!\nI just forgot to move this issue /milestone v1.27\n/reopen is the partial implementation.\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nMy suggestion on the reference implementation, after reading 's comments is like so... The GRPC server, which implements the expects an implementation that satisfies . The local key logic can be a middleware. So it expects a it can fallback to, if it doesn't know a key or needs to encrypt its own local KEK. So the local implementation would be need to: have a storage of s have a reference to the current in use (if we put it into the cache, it might vanish) have a reference to another , which should be the remote KMS. So the sub-stories could look like: write Middleware write Transformers that can get exhausted (by time, by usage) write 's storage write some dummy for remote KMS? I have some sketches of what I am talking about .", "commid": "kubernetes_issue_112859", "tokennum": 462}], "negative_passages": []}
{"query_id": "q-en-kubernetes-75b6393280866c79efe2b580c4cb85b12373b210e07e9124ecde60d9d092c237", "query": "require ( github.com/gogo/protobuf v1.3.2 google.golang.org/grpc v1.51.0 <ins> k8s.io/klog/v2 v2.80.1 </ins> ) require ( <ins> github.com/go-logr/logr v1.2.3 // indirect </ins> github.com/golang/protobuf v1.5.2 // indirect github.com/google/go-cmp v0.5.9 // indirect golang.org/x/net v0.4.0 // indirect", "positive_passages": [{"docid": "doc-en-kubernetes-b75b4d558a76c05a2f299aa9e4208bfe14cbcf4125785eeef841ee037778035f", "text": "I would implement that in terms of the interface so that it can be used both in testing (via a local key) and in real code (by delegating to a HSM).\nHi bug-triage team member for 1.27 here. This issue is still open but has had no recent activity, and no active PRs. Is everything on track for the Code Freeze in March 14th? Thank you!\n/milestone clear\nCould be closed, right? :)\nWe still need metrics and tracing support for the reference implementation (though it is all a lot less important now).\n/retitle [KMSv2] Add metrics and tracing in for plugins\nThis is duplicate of /close\nClosing this issue. <detailsIn response to : This is duplicate of 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", "commid": "kubernetes_issue_112859", "tokennum": 192}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7609b717c8ebcc0dbf38bafb8c4462172ba2857fa3fa9d8415d4dd9b3792a043", "query": "<del> apiVersion: v1 kind: ReplicationController </del> <ins> apiVersion: extensions/v1beta1 kind: Deployment </ins> metadata: labels: name: openshift name: openshift spec: replicas: 1 <del> selector: name: openshift </del> <ins> selector: matchLabels: name: openshift </ins> template: metadata: labels:", "positive_passages": [{"docid": "doc-en-kubernetes-970debf69dc4e7e663c051298279ebf93b58654f6c393d8683796c73cb4f1c74", "text": "Kubernetes version (use ): Environment: Cloud provider or hardware configuration: Vagrant OS (e.g. from /etc/os-release): CoreOS Kernel (e.g. ):Install tools: Vagrant & Others: What happened: What you expected to happen: Success How to reproduce it (as minimally and precisely as possible): Followed instructions at Tried to run Received: Anything else do we need to know: From googling, it seems several of the fields in the config are for when using OpenShift origin. But creating the replication controller is a prerequisite to launching OpenShift Origin. Chicken & egg problem.", "commid": "kubernetes_issue_39575", "tokennum": 138}], "negative_passages": []}
{"query_id": "q-en-kubernetes-768ed7f224abbd55364ca6405e748724e74adcc449b1253d60efedff4fa06964", "query": "} } <ins> // genEnumWithRuleAndValues creates a function that accepts an optional maxLength // with given validation rule and a set of enum values, following the convention of existing tests. // The test has two checks, first with maxLength unset to check if maxLength can be concluded from enums, // second with maxLength set to ensure it takes precedence. func genEnumWithRuleAndValues(rule string, values ...string) func(maxLength *int64) *schema.Structural { enums := make([]schema.JSON, 0, len(values)) for _, v := range values { enums = append(enums, schema.JSON{Object: v}) } return func(maxLength *int64) *schema.Structural { return &schema.Structural{ Generic: schema.Generic{ Type: \"string\", }, ValueValidation: &schema.ValueValidation{ MaxLength: maxLength, Enum:      enums, }, Extensions: schema.Extensions{ XValidations: apiextensions.ValidationRules{ { Rule: rule, }, }, }, } } } </ins> func genBytesWithRule(rule string) func(maxLength *int64) *schema.Structural { return func(maxLength *int64) *schema.Structural { return &schema.Structural{", "positive_passages": [{"docid": "doc-en-kubernetes-d87f35a9862b77934b500147b1ec4bb0e958c531e2fdcae282b21499e2f51131", "text": "pointed out to me that a CEL x-kubernetes-validations rule in a CRD was hitting the estimated cost limit when performing a simple \"string has prefix\" check on an en enum field. Putting a limit in the OpenAPI of the enum string field fixed the problem, but having to add a limit like this is counter-intuitive and unnecessary, since the allowed enum values already make the max allowed length obvious. The apiserver automatically computes the max length of an enum as the length of the longest allowed enum value. I believe we already refuse evaluate CEL rules on values that fail OpenAPI value validation, since we rely in the value validations to establish all length limits. I haven't tested it locally, but something like this should work (given enough nested arrays): As a workaround, one can manually set on the string enum, e.g.: 25+ All No response No response No response No response\n/sig api-machinery /triage accepted /assign\n/assign\nI wasn't sure if we special-cased the maxLength / maxItems / maxProperties failures, or if all openapi validation had to pass before we started messing with CEL evaluation\nit looks like we currently special-case specific openapi errors that short-circuit CEL validation, I'm not sure an enum validation failure would currently prevent evaluation:\nThe enum err is converted to () error which is not short-circuit here. But for defaulting case, all error would be short-circuit. I would suggest to add error into the blockingErr list to short-circuit CEL validation. Would this make sense?\nyeah, that sounds good if we're going to rely on it to catch things that are longer than the maximum length enum value", "commid": "kubernetes_issue_119511", "tokennum": 383}], "negative_passages": []}
{"query_id": "q-en-kubernetes-76d7d746440f27d05dbf5070d75b26e44a97b2d98953ef4487573662b4c12fdc", "query": "buf.Reset() } } <ins> func TestPrintCluster(t *testing.T) { tests := []struct { cluster    federation.Cluster expect     []metav1alpha1.TableRow showLabels bool }{ { federation.Cluster{ ObjectMeta: metav1.ObjectMeta{ Name:              \"cluster1\", CreationTimestamp: metav1.Time{Time: time.Now().Add(1.9e9)}, }, }, []metav1alpha1.TableRow{{Cells: []interface{}{\"cluster1\", \"Unknown\", \"0s\"}}}, false, }, { federation.Cluster{ ObjectMeta: metav1.ObjectMeta{ Name:              \"cluster2\", CreationTimestamp: metav1.Time{Time: time.Now().Add(1.9e9)}, Labels:            map[string]string{\"label1\": \"\", \"label2\": \"cluster\"}, }, Status: federation.ClusterStatus{ Conditions: []federation.ClusterCondition{ { Status: api.ConditionTrue, Type:   federation.ClusterReady, }, { Status: api.ConditionFalse, Type:   federation.ClusterOffline, }, }, }, }, []metav1alpha1.TableRow{{Cells: []interface{}{\"cluster2\", \"Ready,NotOffline\", \"0s\", \"label1=,label2=cluster\"}}}, true, }, } for i, test := range tests { rows, err := printCluster(&test.cluster, printers.PrintOptions{ShowLabels: test.showLabels}) if err != nil { t.Fatal(err) } for i := range rows { rows[i].Object.Object = nil } if !reflect.DeepEqual(test.expect, rows) { t.Errorf(\"%d mismatch: %s\", i, diff.ObjectReflectDiff(test.expect, rows)) } } } func TestPrintClusterList(t *testing.T) { tests := []struct { clusters   federation.ClusterList expect     []metav1alpha1.TableRow showLabels bool }{ // Test podList's pod: name, num of containers, restarts, container ready status { federation.ClusterList{ Items: []federation.Cluster{ { ObjectMeta: metav1.ObjectMeta{ Name:              \"cluster1\", CreationTimestamp: metav1.Time{Time: time.Now().Add(1.9e9)}, }, Status: federation.ClusterStatus{ Conditions: []federation.ClusterCondition{ { Status: api.ConditionTrue, Type:   federation.ClusterReady, }, }, }, }, { ObjectMeta: metav1.ObjectMeta{ Name:              \"cluster2\", CreationTimestamp: metav1.Time{Time: time.Now().Add(1.9e9)}, Labels:            map[string]string{\"label1\": \"\", \"label2\": \"cluster2\"}, }, Status: federation.ClusterStatus{ Conditions: []federation.ClusterCondition{ { Status: api.ConditionTrue, Type:   federation.ClusterReady, }, { Status: api.ConditionFalse, Type:   federation.ClusterOffline, }, }, }, }, }, }, []metav1alpha1.TableRow{{Cells: []interface{}{\"cluster1\", \"Ready\", \"0s\", \"<none>\"}}, {Cells: []interface{}{\"cluster2\", \"Ready,NotOffline\", \"0s\", \"label1=,label2=cluster2\"}}}, true, }, } for _, test := range tests { rows, err := printClusterList(&test.clusters, printers.PrintOptions{ShowLabels: test.showLabels}) if err != nil { t.Fatal(err) } for i := range rows { rows[i].Object.Object = nil } if !reflect.DeepEqual(test.expect, rows) { t.Errorf(\"mismatch: %s\", diff.ObjectReflectDiff(test.expect, rows)) } } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-f29982137c07dadb3e257d7391e0d9b7bfd5f1ce8fdca72f798301cc159728a0", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: After labeling clusters in a Federation, when you type the field is empty. What you expected to happen: The fiels should contain information about the labels in the cluster How to reproduce it (as minimally and precisely as possible): a federation control pane in any Cloud Provider and any DNS provider your cluster: info aboyut the cluster with the flag: Note: if you describe it, you see the labels being : Environment: Kubernetes version (use ): 1.8.0 Cloud provider or hardware configuration**: anyone OS (e.g. from /etc/os-release): Ubuntu 16.04 Kernel (e.g. ): Linux Install tools: curl Others:\n/sig multicluster\nI'm working on it.", "commid": "kubernetes_issue_53729", "tokennum": 179}], "negative_passages": []}
{"query_id": "q-en-kubernetes-76ed9941f6568b10987402f1d02b195a933c4a81ab823dc2fcde884a44565718", "query": "node := newNode(\"node1\", nil) node.Status.Conditions = []v1.NodeCondition{ {Type: v1.NodeOutOfDisk, Status: v1.ConditionTrue}, <del> {Type: v1.NodeInodePressure, Status: v1.ConditionFalse}, </del> } return node }(),", "positive_passages": [{"docid": "doc-en-kubernetes-7164ee736ec8b7198f38602535de086e7396a736ea12447e5be8a654710fb76e", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind cleanup What happened: It seems kubelet did not update inode pressure; and only test codes are using . So prefer to deprecate or remove it directly. (seems no node-misc group :). )", "commid": "kubernetes_issue_49103", "tokennum": 58}], "negative_passages": []}
{"query_id": "q-en-kubernetes-770e2b1fae79149520a4950ae6858e6c0953b566b24c8bd88e9f0a22990ed0be", "query": "// utils.go contains functions used across test suites. const ( <del> cniVersion       = \"v0.8.7\" </del> <ins> cniVersion       = \"v0.9.1\" </ins> cniArch          = \"amd64\" cniDirectory     = \"cni/bin\" // The CNI tarball places binaries under directory under \"cni/bin\". cniConfDirectory = \"cni/net.d\"", "positive_passages": [{"docid": "doc-en-kubernetes-dfff84e3b11879758919fecc393710655267c5015ee34e69e71565465ba5db90", "text": "The latest release of CNI plugins is , but we still have . I'll attempt to create a PR for this based on the .\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig network\n- assigning to you :)", "commid": "kubernetes_issue_102311", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7747b08b0a771e77cd63d35d2f07f578b745011577ce73e2ba70f68989171410", "query": "func TestPriorityQueue_PendingPods(t *testing.T) { q := NewPriorityQueue(nil) q.Add(&medPriorityPod) <del> q.unschedulableQ.addOrUpdate(&unschedulablePod) q.unschedulableQ.addOrUpdate(&highPriorityPod) </del> <ins> addOrUpdateUnschedulablePod(q, &unschedulablePod) addOrUpdateUnschedulablePod(q, &highPriorityPod) </ins> expectedList := []*v1.Pod{&medPriorityPod, &unschedulablePod, &highPriorityPod} if !reflect.DeepEqual(expectedList, q.PendingPods()) { t.Error(\"Unexpected list of pending Pods for node.\")", "positive_passages": [{"docid": "doc-en-kubernetes-e059cd0647305d70a174ce6bffb9584a993a023526be428075760ddef27cc3b0", "text": "Which jobs are failing: pull-kubernetes-bazel-test Which test(s) are failing: bazel test //pkg/scheduler/internal/queue:godefaulttest Since when has it been failing: Testgrid link: Reason for failure: WARNING: DATA RACE Read at 0x00c000230db0 by goroutine 47: runtime.mapiterinit() +0x0 (PriorityQueue).flushUnschedulableQLeftover() +0x17a (PriorityQueue).flushUnschedulableQLeftover-fm() +0x41 () +0x61 () +0xce () +0x5a Previous write at 0x00c000230db0 by goroutine 45: runtime.mapassignfaststr() +0x0 (UnschedulablePodsMap).addOrUpdate() +0x30e () +0x601 testing.tRunner() +0x162 Goroutine 47 (running) created at: (PriorityQueue).run() +0x172 () +0xe0b () +0x50 () +0x5a5 testing.tRunner() +0x162 Goroutine 45 (running) created at: testing.(T).Run() +0x659 testing.runTests.func1() +0xa8 testing.tRunner() +0x162 testing.runTests() +0x4ee testing.(M).Run() +0x2ee () bazel-out/k8- +0x2fb Anything else we need to know: I'm very sorry about that. UnschedulablePodsMap is not thread-safe. In , lock will be acquired before operating UnschedulablePodsMap. But in , lock isn\u2018t be acquired. In the previous case, only a single thread runs so it's ok. But after add goroutine , there will be data race. So I need to acquire lock before operating UnschedulablePodsMap.\n/sig testing /sig scheduling", "commid": "kubernetes_issue_73021", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-77551711d5317576d9bcf7bfcce2d67215470440912170b3cbd5c3ce03c8ac08", "query": "return true, errors.New(\"not implemented\") } <ins> func (mounter *Mounter) EvalHostSymlinks(pathname string) (string, error) { return \"\", unsupportedErr } </ins> func (mounter *Mounter) PrepareSafeSubpath(subPath Subpath) (newHostPath string, cleanupAction func(), err error) { return subPath.Path, nil, unsupportedErr }", "positive_passages": [{"docid": "doc-en-kubernetes-226c0928db9d5aa6f1446838b8788eb7c60cd41b1b8246f4bd1a4e2614bb7834", "text": "/kind bug Using , if a block device is symlinked to the discovery directory e.g. , then MapVolume will fail with since the containerized kubelet cannot see the path on host. is mounted by containerized kubelet, so if before we try to map the device we set devicePath to the evaluation of symlink and end up with a devicePath of , containerized kubelet will see the device and successfully map the device. Are there any issues with this solution? This is on Kubernetes 1.10\n/sig storage\nah yes containerized kubelet has many issues when dealing with symlinks. Check out Mounter.GetMode(), it calls a nsenter EvalSymlinks which should be able to do what you need. But actually, one thing to consider, is do you need to do the losetup on the host, or does inside the container work?\nYes it appears to work from inside the container, on the host I run which disappears after I delete the pod using the device. My understanding of running losetup in MapVolume is not that great but I suppose that as long as that /dev/loop0 is created we are fine. Thanks for the quick response, I'll create a PR using that function and tag you\nDoes it create it on the host or in the containerized kubelet? What happens when containerized kubelet is restarted? The purpose of losetup is to do \"refcounting\" on the block device to prevent possible naming collisions when devices are attached/detached under unhealthy conditions. Ie, if a device showed up as /dev/sdb and you gave that to a pod, and then for some reason it become unhealthy and disappeared (while the pod is still running), another device (maybe even another volume type) could get attached to the node and reuse /dev/sdb. Now the pod has access to a device it's not supposed to. With filesystem volumes, the refcounting is done with mount points, but for block device, loopback is the equivalent.\nIt is created on the host (and also visible in the container), and stays around through restart. I understand now, thank you.\nActually after I restart it becomes /vdb instead of /dev/vdb in the losetup output, idk what that is about.", "commid": "kubernetes_issue_65445", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-77551711d5317576d9bcf7bfcce2d67215470440912170b3cbd5c3ce03c8ac08", "query": "return true, errors.New(\"not implemented\") } <ins> func (mounter *Mounter) EvalHostSymlinks(pathname string) (string, error) { return \"\", unsupportedErr } </ins> func (mounter *Mounter) PrepareSafeSubpath(subPath Subpath) (newHostPath string, cleanupAction func(), err error) { return subPath.Path, nil, unsupportedErr }", "positive_passages": [{"docid": "doc-en-kubernetes-e6271b0ba1dda755d5bb536a727016a621c7c29c599386bc1e9c22a230980cbf", "text": "There is no such thing as /vdb and /dev/vdb is still intact of course. Seems inconsequential since it is disappearing after all pods using the device are deleted, i.e. it's still serving as a refcounter", "commid": "kubernetes_issue_65445", "tokennum": 55}], "negative_passages": []}
{"query_id": "q-en-kubernetes-779f61b2109c7949b85bc06cb7e9c72af0039630f64170d6c3bbaac8986a4bd8", "query": "// Verify scheduler metrics. // TODO: Reset metrics at the beginning of the test. // We should do something similar to how we do it for APIserver. <del> framework.ExpectNoError(framework.VerifySchedulerLatency(c)) </del> <ins> if err = framework.VerifySchedulerLatency(c); err != nil { framework.Logf(\"Warning: Scheduler latency not calculated, %v\", err) } </ins> }) // Explicitly put here, to delete namespace at the end of the test", "positive_passages": [{"docid": "doc-en-kubernetes-43bb87e0e7e2bbc9a63f125545e4751ea88971868bf29aa570529777682e8f1f", "text": "Problem Running the e2e density tests on a local cluster or any other cluster where ssh to master doesn't work fails, even though enough pods are created, because of SSH attempts. Specifically \"should allow starting 30\" is the argument to reproduce. Solution Allow density tests to pass even if some meta test operations fail after the fact. cc", "commid": "kubernetes_issue_35369", "tokennum": 71}], "negative_passages": []}
{"query_id": "q-en-kubernetes-77ab73f7c5e6f0fadc63071acf012c03dab36d9060b274e71b0ec0651b801d2e", "query": "return errRequeue } <del> // Check parameters. claimParameters, classParameters, err := ctrl.getParameters(ctx, claim, class) </del> <ins> // Check parameters. Do not record event to Claim if its parameters are invalid, // syncKey will record the error. claimParameters, classParameters, err := ctrl.getParameters(ctx, claim, class, false) </ins> if err != nil { return err }", "positive_passages": [{"docid": "doc-en-kubernetes-e8eec0a3f7a81297ed919db6952e73e9801661fbfe386a524b19b8189beefe88", "text": "When ResourceClaimParameters or ResourceClassParameters fail validation in resource driver during PodSchedulingContext sync loop, the error is visible only in the events of the PodSchedulingContext. The error should be visible on the object that fails validation as well, ResourceClaim or ResourceClass respectively. Creating ResourceClaim with unsupported parameters' values or unsupported No response <details</details<details</details<details</details<details</details<details</details<details</details\n/assign\n/sig node\n/triage accepted\nKEP:", "commid": "kubernetes_issue_121063", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-77bdef0f77ba2b53a4d1c2b0a1e59df27d27fc565f25e39d21af376445457170", "query": "kubectl get replicationcontrollers \"${kube_flags[@]}\" kubectl describe replicationcontroller frontend-controller \"${kube_flags[@]}\" | grep -q 'Replicas:.*3 desired' kubectl delete rc frontend-controller \"${kube_flags[@]}\" <ins> rcsbefore=\"$(kubectl get replicationcontrollers  -o template -t \"{{ len .items }}\" \"${kube_flags[@]}\")\" kubectl create -f examples/guestbook/frontend-controller.json \"${kube_flags[@]}\" kubectl create -f examples/guestbook/redis-slave-controller.json \"${kube_flags[@]}\" kubectl delete rc frontend-controller redis-slave-controller \"${kube_flags[@]}\" # delete multiple controllers at once rcsafter=\"$(kubectl get replicationcontrollers  -o template -t \"{{ len .items }}\" \"${kube_flags[@]}\")\" [ \"$((${rcsafter} - ${rcsbefore}))\" -eq 0 ] </ins> kube::log::status \"Testing kubectl(${version}:nodes)\" kubectl get nodes \"${kube_flags[@]}\"", "positive_passages": [{"docid": "doc-en-kubernetes-8781beaf9cecb5a2a5891763e358d97bbb8efac5ebba9fc986604965efa0dda5", "text": "Currently, it could not delete multiple pods at once, need to delete them one by one, it's very inconvenient if I have tons of pods to delete. Unlike docker, docker can multiple stop/rm containers/images at once.\nThis is possible using label selectors as of , which is better if you have tons of pods.\nI agree that using label selector is better to delete all of pods under the label. But to delete multile pods at once is still usable: I just want to delete 1/2 pods under the label, label selector will not work selector could not span over other selectors or pods Another reason is docker rm/stop x y z works, I will wonder why kubectl cannot. This is not urgent, but I hope it can be implemented.\nI agree. Thanks for the suggestion.\nWould this be a suitable task for someone new to k8s development? If so, I'd be willing to take a look at this, if someone could provide a couple of hints where to start.\nFurther to my last message, I have a functional work in progress I would like to share, if anyone is interested?\nPRs are welcome. See\nYes, this is a reasonable place to start. Since its in the client, you won't get much orientation to the core server code, but it will be a good place to orient to the client side API. There us also prior art that you can model off of. The kubectl create ... command already supports multiple resources. A good command to adapter would be the 'label' command. You can find it in Many thanks in advance! Brendan On Feb 19, 2015 8:21 AM, \"Eric Tune\" wrote:", "commid": "kubernetes_issue_3050", "tokennum": 364}], "negative_passages": []}
{"query_id": "q-en-kubernetes-77cfdc29a9a2fac9190c95e6468b990f68f0ecc85879ca28cb82b188f0af1077", "query": "currentRevision *apps.ControllerRevision, updateRevision *apps.ControllerRevision, collisionCount int32, <del> pods []*v1.Pod) (*apps.StatefulSetStatus, error) { </del> <ins> pods []*v1.Pod) (statefulSetStatus *apps.StatefulSetStatus, updateErr error) { </ins> // get the current and update revisions of the set. currentSet, err := ApplyRevision(set, currentRevision) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-0cad02d163e61aff3cc2c1257b68701a42fb1145e0b51f6816fd9a85adca78e6", "text": "I create a ResourceQuota with two pods limit in my namespace. Then, I create a statefuleSet with 3 replicas. As expected, two pods are created successfully, and the third pod failed to create. But, the ReadyReplicas is not 2 ,but 1. The ReadyReplicas is correct 1Create a ResourceQuota with two pods limit in a new namespace. 2Create a statefulSet with 3 replicas 3Check if the ReadyReplicas of statefulSet matchs the number of stateful running pods. 1According to the logic of the statefulSet controller, new pod created in current sync is not be immediately counted into the ReadyReplicas. 2Failure to create pod will cause to return error, then skip updating status. <details</details<details</details<detailskind v1.23.3 </details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig apps\n/assign", "commid": "kubernetes_issue_108837", "tokennum": 302}], "negative_passages": []}
{"query_id": "q-en-kubernetes-77df114c43a189b62632a05b84e9ca6446b2c39b2d9a7b7526a1a98e009f3dc3", "query": "}, }, { <ins> // PV requires external deleter name:            \"8-10-2 - external deleter when volume is static provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { // PV requires external deleter name:            \"8-10-3 - external deleter when volume is migrated\", initialVolumes:  []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, expectedVolumes: []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { </ins> // delete success - two PVs are provisioned for a single claim. // One of the PVs is deleted. name: \"8-11 - two PVs provisioned for a single claim\",", "positive_passages": [{"docid": "doc-en-kubernetes-17da90f267168da4485057cb3c70835a09c33080424540be2f99c7292698f22f", "text": "In my CSI controller I have enabled the feature gate HonorPVReclaimPolicy for csi-provisioner. Based on the documentation Finalizers can be on a PersistentVolume to ensure that PersistentVolumes having Delete reclaim policy are deleted only after the backing storage are deleted. The newly introduced finalizers and external- are only to dynamically provisioned volumes. I can see the finalizer set on the PV while creating static Persistent Volume. PV deletion is stuck due to this finalizer apiVersion: v1 kind: PersistentVolume metadata: creationTimestamp: \"2023-11-08T11:39:24Z\" deletionGracePeriodSeconds: 0 deletionTimestamp: \"2023-11-08T11:54:31Z\" finalizers: external- name: csi-infoscale-pv PV should be deleted when PVC is deleted. Persistent Volume yaml apiVersion: v1 kind: PersistentVolume metadata: name: csi-infoscale-pv spec: storageClassName: csi-infoscale-sc-prod persistentVolumeReclaimPolicy: Delete capacity: storage: 2Gi accessModes: ReadWriteOnce csi: driver: org.veritas.infoscale # Please provide pre-provisioned Infoscale volume name. volumeHandle: clust21432/vrtskube_dg-/vol1 fsType: vxfs Persistent Volume Claim apiVersion: v1 kind: PersistentVolumeClaim metadata: name: csi-infoscale-pvc-static spec: accessModes: ReadWriteOnce resources: requests: storage: 2Gi storageClassName: csi-infoscale-sc-prod volumeName: csi-infoscale-pv Same thing works fine on OCP. WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version.", "commid": "kubernetes_issue_121799", "tokennum": 440}], "negative_passages": []}
{"query_id": "q-en-kubernetes-77df114c43a189b62632a05b84e9ca6446b2c39b2d9a7b7526a1a98e009f3dc3", "query": "}, }, { <ins> // PV requires external deleter name:            \"8-10-2 - external deleter when volume is static provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { // PV requires external deleter name:            \"8-10-3 - external deleter when volume is migrated\", initialVolumes:  []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, expectedVolumes: []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { </ins> // delete success - two PVs are provisioned for a single claim. // One of the PVs is deleted. name: \"8-11 - two PVs provisioned for a single claim\",", "positive_passages": [{"docid": "doc-en-kubernetes-0ba3f4f18a7007434ced94c47e051d55455d5fb79cd77986fc1ae4d5bc653af8", "text": "Client Version: version.Info{Major:\"1\", Minor:\"27\", GitVersion:\"v1.27.5\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2023-08-24T00:48:26Z\", GoVersion:\"go1.20.7\", Compiler:\"gc\", Platform:\"linux/amd64\"} Kustomize Version: v5.0.1 Server Version: version.Info{Major:\"1\", Minor:\"27\", GitVersion:\"v1.27.5\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2023-08-24T00:42:11Z\", GoVersion:\"go1.20.7\", Compiler:\"gc\", Platform:\"linux/amd64\"} Vanilla K8s setup <details</details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig storage maybe similar issues should go in\nOpened similar issue in external-provisioner repo also There is no reply on that as well. Can you please help understand the behavior of the feature HonorPVReclaimPolicy.\nIf you want Persistent Volume (PV) to be deleted when the associated Persistent Volume Claim (PVC) is deleted, you donot need to use finalizers explicitly. Kubernetes handles this behavior by default. It is ok that if you use to get the desire output using Finalizer we can do it.\nAs per my understanding Please follow the steps : Add finalizer in metadata of as you did above need to make change in the controller which is handling PV deletion in .go file. See whether the controller administrator is working or not. I think it will work.\nFinalizer is because the feature gate HonorPVReclaimPolicy for csi-provisioner is enabled. We are not adding the finalizer explicitly. From the documentation, \"The newly introduced finalizers and external- are only to dynamically provisioned volumes.\" Not sure why is the finalizer getting set.", "commid": "kubernetes_issue_121799", "tokennum": 555}], "negative_passages": []}
{"query_id": "q-en-kubernetes-77df114c43a189b62632a05b84e9ca6446b2c39b2d9a7b7526a1a98e009f3dc3", "query": "}, }, { <ins> // PV requires external deleter name:            \"8-10-2 - external deleter when volume is static provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { // PV requires external deleter name:            \"8-10-3 - external deleter when volume is migrated\", initialVolumes:  []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, expectedVolumes: []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { </ins> // delete success - two PVs are provisioned for a single claim. // One of the PVs is deleted. name: \"8-11 - two PVs provisioned for a single claim\",", "positive_passages": [{"docid": "doc-en-kubernetes-592cda3e1f42c2eb1f47fff2bb790922cec52a4f953f170e43c5acb028d04e55", "text": "Also, for deleting PV it requires the annotation \"\" but this annotation is set in case of dynamic PVs. Should it be set explicitly for static PV?\nThis feature is alpha so the feature gate is not enabled by default. Did you enable the feature gate on kube-controller-manager?\nYes, i have enabled this feature.\nexternal- is also applied to statically provisioned volumes. FYI\nHi Which version of the external provisioner is the driver using? Does the driver meet the requirements of the CSI spec on the DeleteVolume PRC? FYI: Is this problem occasional or permanently reproducible? Can you provide the provisioner logs at that time?\n/triage needs-information\ncc\ncc\nExternal provisioner used is : \"csi-provisioner:v3.5.0\" This problem is always reproducible Provisioner logs: I1123 12:22:38. 1 ] handleProtectionFinalizer Volume : &PersistentVolume{ObjectMeta:{csi-infoscale-pv -420a-4e9e-be82- 0 2023-11-23 12:21:18 +0000 UTC <nil<nilmap[] map[{\"apiVersion\":\"v1\",\"kind\":\"PersistentVolume\",\"metadata\":{\"annotations\":{},\"name\":\"csi-infoscale-pv\"},\"spec\":{\"accessModes\":[\"ReadWriteOnce\"],\"capacity\":{\"storage\":\"2Gi\"},\"csi\":{\"driver\":\"org.veritas.infoscale\",\"fsType\":\"vxfs\",\"volumeHandle\":\"clust40559/vrtskubedg-/vol1\"},\"persistentVolumeReclaimPolicy\":\"Delete\",\"storageClassName\":\"csi-infoscale-sc-prod\"}} ] [] [ external-] [{kubectl-client-side-apply Update v1 2023-11-23 12:21:18 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:annotations\":{\".\":{},\"\":{}}},\"f:spec\":{\"f:accessModes\":{},\"f:capacity\":{\".\":{},\"f:storage\":{}},\"f:csi\":{\".", "commid": "kubernetes_issue_121799", "tokennum": 563}], "negative_passages": []}
{"query_id": "q-en-kubernetes-77df114c43a189b62632a05b84e9ca6446b2c39b2d9a7b7526a1a98e009f3dc3", "query": "}, }, { <ins> // PV requires external deleter name:            \"8-10-2 - external deleter when volume is static provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { // PV requires external deleter name:            \"8-10-3 - external deleter when volume is migrated\", initialVolumes:  []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, expectedVolumes: []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { </ins> // delete success - two PVs are provisioned for a single claim. // One of the PVs is deleted. name: \"8-11 - two PVs provisioned for a single claim\",", "positive_passages": [{"docid": "doc-en-kubernetes-3ecd202a68dc777f32874cd48d4b39291a9bf67f2771bfe1a1dd4808649976b8", "text": "\":{},\"f:driver\":{},\"f:fsType\":{},\"f:volumeHandle\":{}},\"f:persistentVolumeReclaimPolicy\":{},\"f:storageClassName\":{},\"f:volumeMode\":{}}} } {csi-provisioner Update v1 2023-11-23 12:21:22 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:finalizers\":{\"v:\"external-\"\":{}}}} } {kube-controller-manager Update v1 2023-11-23 12:21:22 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:annotations\":{\"\":{}}},\"f:spec\":{\"f:claimRef\":{\".", "commid": "kubernetes_issue_121799", "tokennum": 208}], "negative_passages": []}
{"query_id": "q-en-kubernetes-77df114c43a189b62632a05b84e9ca6446b2c39b2d9a7b7526a1a98e009f3dc3", "query": "}, }, { <ins> // PV requires external deleter name:            \"8-10-2 - external deleter when volume is static provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { // PV requires external deleter name:            \"8-10-3 - external deleter when volume is migrated\", initialVolumes:  []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, expectedVolumes: []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { </ins> // delete success - two PVs are provisioned for a single claim. // One of the PVs is deleted. name: \"8-11 - two PVs provisioned for a single claim\",", "positive_passages": [{"docid": "doc-en-kubernetes-fb611cee6f984fef598fa329474fd3d3abef5728e2a0833d8129f0a5ee9ed92e", "text": "\":{},\"f:apiVersion\":{},\"f:kind\":{},\"f:name\":{},\"f:namespace\":{},\"f:resourceVersion\":{},\"f:uid\":{}}}} } {kube-controller-manager Update v1 2023-11-23 12:22:38 +0000 UTC FieldsV1 {\"f:status\":{\"f:phase\":{}}} status}]},Spec:PersistentVolumeSpec{Capacity:ResourceList{storage: {{ 0} {<nil} 2Gi BinarySI},},PersistentVolumeSource:PersistentVolumeSource{GCEPersistentDisk:nil,AWSElasticBlockStore:nil,HostPath:nil,Glusterfs:nil,NFS:nil,RBD:nil,ISCSI:nil,Cinder:nil,CephFS:nil,FC:nil,Flocker:nil,FlexVolume:nil,AzureFile:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Local:nil,StorageOS:nil,CSI:&CSIPersistentVolumeSource{Driver:org.veritas.infoscale,VolumeHandle:clust40559/vrtskubedg-/vol1,ReadOnly:false,FSType:vxfs,VolumeAttributes:map[string]string{},ControllerPublishSecretRef:nil,NodeStageSecretRef:nil,NodePublishSecretRef:nil,ControllerExpandSecretRef:nil,NodeExpandSecretRef:nil,},},AccessModes:[ReadWriteOnce],ClaimRef:&ObjectReference{Kind:PersistentVolumeClaim,Namespace:default,Name:csi-infoscale-pvc-static,UID:-59a5-4f02-83ac-,APIVersion:v1,ResourceVersion:,FieldPath:,},PersistentVolumeReclaimPolicy:Delete,StorageClassName:csi-infoscale-sc-prod,MountOptions:[],VolumeMode:Filesystem,NodeAffinity:nil,},Status:PersistentVolumeStatus{Phase:Released,Message:,Reason:,},} I1123 12:22:38. 1 ] delete \"csi-infoscale-pv\": started I1123 12:22:38. 1 ] GRPC call: /csi.v1.Controller/DeleteVolume I1123 12:22:38. 1 ] GRPC request: {\"volumeid\":\"clust40559/vrtskubedg-/vol1\"} I1123 12:22:39.", "commid": "kubernetes_issue_121799", "tokennum": 705}], "negative_passages": []}
{"query_id": "q-en-kubernetes-77df114c43a189b62632a05b84e9ca6446b2c39b2d9a7b7526a1a98e009f3dc3", "query": "}, }, { <ins> // PV requires external deleter name:            \"8-10-2 - external deleter when volume is static provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { // PV requires external deleter name:            \"8-10-3 - external deleter when volume is migrated\", initialVolumes:  []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, expectedVolumes: []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { </ins> // delete success - two PVs are provisioned for a single claim. // One of the PVs is deleted. name: \"8-11 - two PVs provisioned for a single claim\",", "positive_passages": [{"docid": "doc-en-kubernetes-21563431fea9ed5a14c1fde8160d9fcab633c35237ee882cf06625b1768a9487", "text": "1 ] GRPC response: {} I1123 12:22:39. 1 ] GRPC error: <nilI1123 12:22:39. 1 ] delete \"csi-infoscale-pv\": volume deleted I1123 12:22:39. 1 ] delete \"csi-infoscale-pv\": failed to remove finalizer for persistentvolume: Operation cannot be fulfilled on persistentvolumes \"csi-infoscale-pv\": the object has been modified; please apply your changes to the latest version and try again W1123 12:22:39. 1 ] Retrying syncing volume \"csi-infoscale-pv\", failure 0 E1123 12:22:39. 1 ] error syncing volume \"csi-infoscale-pv\": Operation cannot be fulfilled on persistentvolumes \"csi-infoscale-pv\": the object has been modified; please apply your changes to the latest version and try again I1123 12:22:39. 1 ] handleProtectionFinalizer Volume : &PersistentVolume{ObjectMeta:{csi-infoscale-pv -420a-4e9e-be82- 0 2023-11-23 12:21:18 +0000 UTC 2023-11-23 12:22:38 +0000 UTC 0xc0007f63d0 map[] map[{\"apiVersion\":\"v1\",\"kind\":\"PersistentVolume\",\"metadata\":{\"annotations\":{},\"name\":\"csi-infoscale-pv\"},\"spec\":{\"accessModes\":[\"ReadWriteOnce\"],\"capacity\":{\"storage\":\"2Gi\"},\"csi\":{\"driver\":\"org.veritas.infoscale\",\"fsType\":\"vxfs\",\"volumeHandle\":\"clust40559/vrtskubedg-/vol1\"},\"persistentVolumeReclaimPolicy\":\"Delete\",\"storageClassName\":\"csi-infoscale-sc-prod\"}} ] [] [external-] [{kubectl-client-side-apply Update v1 2023-11-23 12:21:18 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:annotations\":{\".\":{},\"\":{}}},\"f:spec\":{\"f:accessModes\":{},\"f:capacity\":{\".\":{},\"f:storage\":{}},\"f:csi\":{\".", "commid": "kubernetes_issue_121799", "tokennum": 610}], "negative_passages": []}
{"query_id": "q-en-kubernetes-77df114c43a189b62632a05b84e9ca6446b2c39b2d9a7b7526a1a98e009f3dc3", "query": "}, }, { <ins> // PV requires external deleter name:            \"8-10-2 - external deleter when volume is static provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { // PV requires external deleter name:            \"8-10-3 - external deleter when volume is migrated\", initialVolumes:  []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, expectedVolumes: []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { </ins> // delete success - two PVs are provisioned for a single claim. // One of the PVs is deleted. name: \"8-11 - two PVs provisioned for a single claim\",", "positive_passages": [{"docid": "doc-en-kubernetes-3ecd202a68dc777f32874cd48d4b39291a9bf67f2771bfe1a1dd4808649976b8", "text": "\":{},\"f:driver\":{},\"f:fsType\":{},\"f:volumeHandle\":{}},\"f:persistentVolumeReclaimPolicy\":{},\"f:storageClassName\":{},\"f:volumeMode\":{}}} } {csi-provisioner Update v1 2023-11-23 12:21:22 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:finalizers\":{\"v:\"external-\"\":{}}}} } {kube-controller-manager Update v1 2023-11-23 12:21:22 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:annotations\":{\"\":{}}},\"f:spec\":{\"f:claimRef\":{\".", "commid": "kubernetes_issue_121799", "tokennum": 208}], "negative_passages": []}
{"query_id": "q-en-kubernetes-77df114c43a189b62632a05b84e9ca6446b2c39b2d9a7b7526a1a98e009f3dc3", "query": "}, }, { <ins> // PV requires external deleter name:            \"8-10-2 - external deleter when volume is static provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { // PV requires external deleter name:            \"8-10-3 - external deleter when volume is migrated\", initialVolumes:  []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, expectedVolumes: []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { </ins> // delete success - two PVs are provisioned for a single claim. // One of the PVs is deleted. name: \"8-11 - two PVs provisioned for a single claim\",", "positive_passages": [{"docid": "doc-en-kubernetes-11586616fd718035f7c04dbcead8d898c73d9e9840ec80b2b32382f64622ed92", "text": "\":{},\"f:apiVersion\":{},\"f:kind\":{},\"f:name\":{},\"f:namespace\":{},\"f:resourceVersion\":{},\"f:uid\":{}}}} } {kube-controller-manager Update v1 2023-11-23 12:22:38 +0000 UTC FieldsV1 {\"f:status\":{\"f:message\":{},\"f:phase\":{}}} status}]},Spec:PersistentVolumeSpec{Capacity:ResourceList{storage: {{ 0} {<nil} 2Gi BinarySI},},PersistentVolumeSource:PersistentVolumeSource{GCEPersistentDisk:nil,AWSElasticBlockStore:nil,HostPath:nil,Glusterfs:nil,NFS:nil,RBD:nil,ISCSI:nil,Cinder:nil,CephFS:nil,FC:nil,Flocker:nil,FlexVolume:nil,AzureFile:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Local:nil,StorageOS:nil,CSI:&CSIPersistentVolumeSource{Driver:org.veritas.infoscale,VolumeHandle:clust40559/vrtskubedg-/vol1,ReadOnly:false,FSType:vxfs,VolumeAttributes:map[string]string{},ControllerPublishSecretRef:nil,NodeStageSecretRef:nil,NodePublishSecretRef:nil,ControllerExpandSecretRef:nil,NodeExpandSecretRef:nil,},},AccessModes:[ReadWriteOnce],ClaimRef:&ObjectReference{Kind:PersistentVolumeClaim,Namespace:default,Name:csi-infoscale-pvc-static,UID:-59a5-4f02-83ac-,APIVersion:v1,ResourceVersion:,FieldPath:,},PersistentVolumeReclaimPolicy:Delete,StorageClassName:csi-infoscale-sc-prod,MountOptions:[],VolumeMode:Filesystem,NodeAffinity:nil,},Status:PersistentVolumeStatus{Phase:Failed,Message:error getting deleter volume plugin for volume \"csi-infoscale-pv\": no deletable volume plugin matched,Reason:,},} I1123 12:22:40.", "commid": "kubernetes_issue_121799", "tokennum": 650}], "negative_passages": []}
{"query_id": "q-en-kubernetes-77df114c43a189b62632a05b84e9ca6446b2c39b2d9a7b7526a1a98e009f3dc3", "query": "}, }, { <ins> // PV requires external deleter name:            \"8-10-2 - external deleter when volume is static provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { // PV requires external deleter name:            \"8-10-3 - external deleter when volume is migrated\", initialVolumes:  []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, expectedVolumes: []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { </ins> // delete success - two PVs are provisioned for a single claim. // One of the PVs is deleted. name: \"8-11 - two PVs provisioned for a single claim\",", "positive_passages": [{"docid": "doc-en-kubernetes-372f094f1905cb03e404d407c686a802e84a00b41a059cf5fa90382ee5601de2", "text": "1 ] handleProtectionFinalizer Volume : &PersistentVolume{ObjectMeta:{csi-infoscale-pv -420a-4e9e-be82- 0 2023-11-23 12:21:18 +0000 UTC 2023-11-23 12:22:38 +0000 UTC 0xc0007f63d0 map[] map[{\"apiVersion\":\"v1\",\"kind\":\"PersistentVolume\",\"metadata\":{\"annotations\":{},\"name\":\"csi-infoscale-pv\"},\"spec\":{\"accessModes\":[\"ReadWriteOnce\"],\"capacity\":{\"storage\":\"2Gi\"},\"csi\":{\"driver\":\"org.veritas.infoscale\",\"fsType\":\"vxfs\",\"volumeHandle\":\"clust40559/vrtskubedg-/vol1\"},\"persistentVolumeReclaimPolicy\":\"Delete\",\"storageClassName\":\"csi-infoscale-sc-prod\"}} ] [] [external-] [{kubectl-client-side-apply Update v1 2023-11-23 12:21:18 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:annotations\":{\".\":{},\"\":{}}},\"f:spec\":{\"f:accessModes\":{},\"f:capacity\":{\".\":{},\"f:storage\":{}},\"f:csi\":{\".\":{},\"f:driver\":{},\"f:fsType\":{},\"f:volumeHandle\":{}},\"f:persistentVolumeReclaimPolicy\":{},\"f:storageClassName\":{},\"f:volumeMode\":{}}} } {csi-provisioner Update v1 2023-11-23 12:21:22 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:finalizers\":{\"v:\"external-\"\":{}}}} } {kube-controller-manager Update v1 2023-11-23 12:21:22 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:annotations\":{\"\":{}}},\"f:spec\":{\"f:claimRef\":{\".", "commid": "kubernetes_issue_121799", "tokennum": 599}], "negative_passages": []}
{"query_id": "q-en-kubernetes-77df114c43a189b62632a05b84e9ca6446b2c39b2d9a7b7526a1a98e009f3dc3", "query": "}, }, { <ins> // PV requires external deleter name:            \"8-10-2 - external deleter when volume is static provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-2\", \"1Gi\", \"uid10-1-2\", \"claim10-1-2\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { // PV requires external deleter name:            \"8-10-3 - external deleter when volume is migrated\", initialVolumes:  []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, expectedVolumes: []*v1.PersistentVolume{volumeWithAnnotation(volume.AnnMigratedTo, \"pd.csi.storage.gke.io\", volumeWithAnnotation(volume.AnnDynamicallyProvisioned, \"kubernetes.io/gce-pd\", newVolume(\"volume8-10-3\", \"1Gi\", \"uid10-1-3\", \"claim10-1-3\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, volume.AnnDynamicallyProvisioned)))}, initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents, errors:          noerrors, test:            testSyncVolume, }, { </ins> // delete success - two PVs are provisioned for a single claim. // One of the PVs is deleted. name: \"8-11 - two PVs provisioned for a single claim\",", "positive_passages": [{"docid": "doc-en-kubernetes-8654731eb8139b66a1cecad4a317b2078534f6977aa1c7223978f7fff83e9392", "text": "\":{},\"f:apiVersion\":{},\"f:kind\":{},\"f:name\":{},\"f:namespace\":{},\"f:resourceVersion\":{},\"f:uid\":{}}}} } {kube-controller-manager Update v1 2023-11-23 12:22:38 +0000 UTC FieldsV1 {\"f:status\":{\"f:message\":{},\"f:phase\":{}}} status}]},Spec:PersistentVolumeSpec{Capacity:ResourceList{storage: {{ 0} {<nil} 2Gi BinarySI},},PersistentVolumeSource:PersistentVolumeSource{GCEPersistentDisk:nil,AWSElasticBlockStore:nil,HostPath:nil,Glusterfs:nil,NFS:nil,RBD:nil,ISCSI:nil,Cinder:nil,CephFS:nil,FC:nil,Flocker:nil,FlexVolume:nil,AzureFile:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Local:nil,StorageOS:nil,CSI:&CSIPersistentVolumeSource{Driver:org.veritas.infoscale,VolumeHandle:clust40559/vrtskubedg-/vol1,ReadOnly:false,FSType:vxfs,VolumeAttributes:map[string]string{},ControllerPublishSecretRef:nil,NodeStageSecretRef:nil,NodePublishSecretRef:nil,ControllerExpandSecretRef:nil,NodeExpandSecretRef:nil,},},AccessModes:[ReadWriteOnce],ClaimRef:&ObjectReference{Kind:PersistentVolumeClaim,Namespace:default,Name:csi-infoscale-pvc-static,UID:-59a5-4f02-83ac-,APIVersion:v1,ResourceVersion:,FieldPath:,},PersistentVolumeReclaimPolicy:Delete,StorageClassName:csi-infoscale-sc-prod,MountOptions:[],VolumeMode:*Filesystem,NodeAffinity:nil,},Status:PersistentVolumeStatus{Phase:Failed,Message:error getting deleter volume plugin for volume \"csi-infoscale-pv\": no deletable volume plugin matched,Reason:,},}\nThank you I will try to fix it. /remove-triage needs-information /assign", "commid": "kubernetes_issue_121799", "tokennum": 661}], "negative_passages": []}
{"query_id": "q-en-kubernetes-77e3d83a29034075042ac647e5b426607d4843e588df5eeb0176865a8a0d7104", "query": "The `FLANNEL_NET` variable defines the IP range used for flannel overlay network, should not conflict with above `SERVICE_CLUSTER_IP_RANGE`. <ins> You can optionally provide additional Flannel network configuration through `FLANNEL_OTHER_NET_CONFIG`, as explained in `cluster/ubuntu/config-default.sh`. </ins> **Note:** When deploying, master needs to be connected to the Internet to download the necessary files. If your machines are located in a private network that need proxy setting to connect the Internet,", "positive_passages": [{"docid": "doc-en-kubernetes-3bb3543c0323a70faea91ccc43a3eaf950d3e30c811cd93e021b94a126351841", "text": "and provide for configuring Flannel's parameter but none of the others listed in", "commid": "kubernetes_issue_19618", "tokennum": 20}], "negative_passages": []}
{"query_id": "q-en-kubernetes-77fe0578932a380737835c6b4aa2f30caee3c2892d04b655b3906681314137fc", "query": "i := rand.Intn(x.NumField()) fuzzer.Fuzz(x.Field(i).Addr().Interface()) <del> errs := validateNestedValueValidation(vv, false, false, nil) </del> <ins> errs := validateNestedValueValidation(vv, false, false, fieldLevel, nil) </ins> if len(errs) == 0 && !reflect.DeepEqual(vv.ForbiddenExtensions, Extensions{}) { t.Errorf(\"expected ForbiddenExtensions validation errors for: %#v\", vv) }", "positive_passages": [{"docid": "doc-en-kubernetes-4be11de3bdb9e2a86ad3a19c4d6f5342db422d48e5979c118fca9ce077f64900", "text": "We allow CRD authors to write . Currently we don't restrict writing validation for , which means people can have . For example, people can have additive name constraints (require CR to be ) with the following schema: This brings us two questions: do we if \"metadata\" is included in the schema: simplest option is to publish standard metav1.ObjectMeta schema info, and use any CRD-specified \"metadata\" properties as additive validation (just like in-tree types do, publishing standard ObjectMeta schema info, and implementing type-specific name validation internally) alternatively, we can try merging user-specified metadata schema with the standard one. Technically people should only add extra validation to existing metadata properties (adding new fields to metadata won't work since they will be pruned by built-in validation first), but it's unclear to me how arbitrary people may want the metadata validation to be term question is whether to allow people specifying metadata validation at all, or just allow a subset (like name validation) in CRD v1 /sig api-machinery /area custom-resources cc\nWhat is the difference between these two? I mean the end result is the same right? The only thing that can be is validation. Nothing else works unless you are considering extensions?\nThe former means we drop/hide user-specified metadata schema when we publish CRD OpenAPI. We still validate user-specified constraints on server side, but client-side validation won't see them. The latter enables client-side user-specified metadata validation.\nIf it's possible to merge with standard metadata schema info, or at the cost of not publishing the standard schema. My inclination would be to publish the complete standard schema for metadata/apiVersion/kind, which we know is complete and accurate, and use and user-specified schema for those fields as addition validations server side", "commid": "kubernetes_issue_74620", "tokennum": 396}], "negative_passages": []}
{"query_id": "q-en-kubernetes-780eb534e26a61ce16161c17e19965545a5dd64f90bb6f70ac26dc25ada56427", "query": "storageframework.DefaultFsInlineVolume, storageframework.DefaultFsPreprovisionedPV, storageframework.DefaultFsDynamicPV, <ins> storageframework.NtfsDynamicPV, </ins> } return InitCustomVolumeIOTestSuite(patterns) }", "positive_passages": [{"docid": "doc-en-kubernetes-2598e11fb35075705c3572da278160109a38df575ea6022e29df9bb46aaee489", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --ci-kubernetes-e2e-gci-gce-serial (gce-cos-master-serial) Four tests: Kubernetes e2e suite.[sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly] Kubernetes e2e suite.[sig-storage] In-tree Volumes [Driver: hostPath] [Testpattern: Inline-volume (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly] Kubernetes e2e suite.[sig-storage] In-tree Volumes [Driver: hostPathSymlink] [Testpattern: Inline-volume (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly] Kubernetes e2e suite.[sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should unmount if pod is force deleted while kubelet is down [Disruptive][Slow][LinuxOnly] is failing since June 29th 2021 (but the first failure was different than more recent ones). Commit , infra commit , . Other three tests are failing since July 9th 2021. Commit , infra commit , . Testgrid: https://k8s- Prow history: For CSI Volumes: For In-tree Volumes: There is another open issues for failing tests in this job: Failures reported there are about missing metrics, and were occuring before unmounting problems. So I opened a new issue, even though it's the same SIG. These tests don't look related to me, but I don't have enough context, maybe they somehow are. /sig storage /kind failing-test /milestone 1.22\nYou must be a member of the GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.", "commid": "kubernetes_issue_103651", "tokennum": 533}], "negative_passages": []}
{"query_id": "q-en-kubernetes-780eb534e26a61ce16161c17e19965545a5dd64f90bb6f70ac26dc25ada56427", "query": "storageframework.DefaultFsInlineVolume, storageframework.DefaultFsPreprovisionedPV, storageframework.DefaultFsDynamicPV, <ins> storageframework.NtfsDynamicPV, </ins> } return InitCustomVolumeIOTestSuite(patterns) }", "positive_passages": [{"docid": "doc-en-kubernetes-fc6065ba1a9951ec296be8e3d5eed3592b7f58a8cbf0f7d83f44e7e6b4d2f288", "text": "<detailsIn response to : <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --ci-kubernetes-e2e-gci-gce-serial (gce-cos-master-serial) Four tests: Testgrid: https://k8s- Prow history: For CSI Volumes: For In-tree Volumes: #### Anything else we need to know: /kind failing-test /milestone 1.22 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\n/milestone v1.22\n/cc\n/cc (my close/reopen yesterday was accidental, sorry)\nI can take a look /assign\nThe non-subpath counterpart of this test is passing: These tests seem to use the default storageclass, whereas failing tests use in-tree hostpath and csi-hostpath\nThe CSI ones are failing because the hostpath driver never received a NodeUnstage (whereas it did in passing tests), causing the driver to error on volume deletion.\nIn the failed run kubelet has this error: which seems to have prevented kubelet from triggering a UnmountDevice. This error didn't exist in a successful run.\nHostpath driver can run with and without support for attach. Do you know which mode is enabled for this test?\nBetween the last passing time and when the test started failing, are there any PRs merged that look suspicious?\nAccording to csi-attacher logs, attach is disabled for both the good run and the failing run. Haven't spotted any obvious PRs so far, but I did find this: in the successful run, the log message for the successful is this: and the failed run: so the reconstructed volume names are somehow different. Checking reconstruction logic\nThis merged 12 days ago and was a pretty big change to pod lifecycle and could have trickling impact to volume manager. Does the timing of test failure match?\nThere is also this reconstruction fix that merged yesterday and seems related to outer vs inner spec name. I don't know if that will help fix this issue:\ncc\nLast successful run started at 7/8 17:49 PT, first failing run started at 7/9 2:23 PT.", "commid": "kubernetes_issue_103651", "tokennum": 491}], "negative_passages": []}
{"query_id": "q-en-kubernetes-780eb534e26a61ce16161c17e19965545a5dd64f90bb6f70ac26dc25ada56427", "query": "storageframework.DefaultFsInlineVolume, storageframework.DefaultFsPreprovisionedPV, storageframework.DefaultFsDynamicPV, <ins> storageframework.NtfsDynamicPV, </ins> } return InitCustomVolumeIOTestSuite(patterns) }", "positive_passages": [{"docid": "doc-en-kubernetes-9f1333b0e960fd7acd243a96166fc71cf5883a52e7407e5f9400e1f08c54d3cf", "text": "was merged at 7/8 16:48 PT, so it's possible (if there's a delay in picking up master) Also this is in the failing kubelet logs but not in the successful one: I0720 18:20:42. ] \"Reconciler sync states: could not find volume information in desired state, clean up the mount points\" podName=-e508-45c2-8509- volumeSpecName=\"pvc--a615-4e89-afe8-\"\nFrom , the newly introduced log message here exists in the failing kubelet logs but not the successful one:\nFailures starting 07/08: /sig node for visibility\nI think caused the failures. Before after kubelet restarts, pod will still be in desired state (even through it is in terminating state), so that clean up mounts can be done completely. I think now, terminating pods will not be back to desired state, but reconstruction to actual state cannot completely clean up mounts. I am testing it about this.\nIs there a reason why reconstruction to actual state cannot clean up mounts? Note that a pod can be force deleted at any time, so a terminating pod that is force deleted would still have to be capable of being cleaned up (it won't be in desired state)? (note too that the expectation of the changes in is that terminating and fully terminated and \"never seen before\" should all completely equivalent from the perspective of other loops in the kubelet) If I understand you correctly, is this an existing bug that we're now triggering consistently?\nWe have both \"grace pod deletion\" and \"force pod deletion\" test cases that are failing.\nThere were a couple of key changes to volume loops in : Roughly before was \"it looks like it's got no running containers\", and after my change is \"we are going to be stopping all the containers from now on\". So this change meant that once a pod starts terminating, we are in \"tearing down mode\" and so my understanding of this method was that \"any pod where containers are being torn down is not in the desired state of the world\".", "commid": "kubernetes_issue_103651", "tokennum": 455}], "negative_passages": []}
{"query_id": "q-en-kubernetes-780eb534e26a61ce16161c17e19965545a5dd64f90bb6f70ac26dc25ada56427", "query": "storageframework.DefaultFsInlineVolume, storageframework.DefaultFsPreprovisionedPV, storageframework.DefaultFsDynamicPV, <ins> storageframework.NtfsDynamicPV, </ins> } return InitCustomVolumeIOTestSuite(patterns) }", "positive_passages": [{"docid": "doc-en-kubernetes-015fa24d1e5eab79f6c5c1e5c14379be6e8185c1f089267f0bfc29a8792fef5f", "text": "After a restart, we would definitely not add a pod back that was in terminating state into desired state of the world, but \"restart + this change\" should be roughly equivalent to \"restart and force delete while restart is processing\" The other change was in which changed a live CRI read (which was trying to enforce that the dsowp is synchronized with the pod worker) into a threadsafe check against the pod worker directly (the pod worker can provide authoritative answers to \"this pod has no running containers\" now). The latter change seems less likely to impact you.\nThank you for the details! I think your change is making the right change, but unfortunately some of volume management still have issues, and so the tests rely on some behaviors that is not very right (pod volume is back to desired state even after it is in terminating) The cleanup mount currently does not have the logic to clean up global mount point if the volume plugin sets it up. I am still testing more and will share more details.\nis this a release blocker?\nYes, this impacts volume cleanup if kubelet restarts for any reason.\nOn a kube-up cluster running the latest master against the latest e2e binary, I was able to reproduce the in-tree failures but not the CSI ones for some reason. Will focus on in-tree failures for the time being\n/triage accepted\nmarking release-blocker per note on slack:\n/priority critical-urgent (once upon a time we used to not ship a release if any priority/critical-urgent issues were open, not sure if we decided to stop doing that)\nWe were able to find the trigger for the CSI failures - on 6/29 there was a change in the hostpath driver test manifest, and the driver's is enabled. This makes the driver return an error instead of only logging a warning message on if the volume isn't unstaged properly. IIUC there's a long standing issue that reconstruction doesn't handle node unstage. could you confirm? If that's the case, then these CSI failures are not release blocking. Furthermore, the CSI test with graceful delete started to fail on 7/9 because of since graceful and force deletes are now considered the same from the point of view of the volume manager. cc\nWhen that check was enabled, I don't think we realized it would impact the reconstruction path; it was enabled to validate a different issue.", "commid": "kubernetes_issue_103651", "tokennum": 504}], "negative_passages": []}
{"query_id": "q-en-kubernetes-780eb534e26a61ce16161c17e19965545a5dd64f90bb6f70ac26dc25ada56427", "query": "storageframework.DefaultFsInlineVolume, storageframework.DefaultFsPreprovisionedPV, storageframework.DefaultFsDynamicPV, <ins> storageframework.NtfsDynamicPV, </ins> } return InitCustomVolumeIOTestSuite(patterns) }", "positive_passages": [{"docid": "doc-en-kubernetes-f86a5554f8df185db14256e7a7df5d445e052035a06405a03d3d05e494e0b68d", "text": "Are we running into the issue that reconstruction of staging directories isn't supported () OR is it that our reconstruction path requires drivers to have real mount points ()? Either way since both are known gaps with reconstruction, I think it makes sense to to disable the flag until we can address those issues.\nI was looking at this today too, trying to understand the underlying cause. That is why the failures are being reported now, but the part that I didn't understand is why NodeUnstageVolume is not being called for these volumes. In this instance: The DeleteVolume request fails because a staged path is still present: And in the kubelet log, NodeUnpublishVolume is called Then we hit this error: And NodeUnstageVolume is never called for this volume (same for other failures I looked at) so DeleteVolume keeps failing. So I think you're right that it's triggered by reconstruction, and it looks similar to , except in this case the restart happened before NodeUnpublishVolume.\nAnd it's probably not since the test uses a PVC\nWill look deeper into why UnmountDevice wasn't issued as well, but some update on the in-tree tests: the force delete test is skipped for the in-tree hostpath CSI driver because of Graceful tests are now failing as well because they behave like force tests due to\nI don't think the issue is related to PVC or not. I think it's related to drivers that do not actually mount devices as a separate filesystem than the root.\nThere are three possible flows during kubelet restart pod gracefully delete case, the pod still exists (it is not considered as terminated in function isPodTerminated(); note that this logic has some changes after , see , so pod volume will be back to desired state, and reconciler will try to set up volume and fill in actual state. When pod volume is finally deleted from desired state, reconciler will trigger teardown with information from actual state to unpublish and unstage volume. pod is forcefully deleted, pod volume will not be in desired state. If volume reconstruction succeeds (be able to reconstruct volume spec), volume will be back into actual state. Then reconciler will trigger teardown with information from actual state to unpublish and unstage volume (this part is similar to case 1).", "commid": "kubernetes_issue_103651", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-780eb534e26a61ce16161c17e19965545a5dd64f90bb6f70ac26dc25ada56427", "query": "storageframework.DefaultFsInlineVolume, storageframework.DefaultFsPreprovisionedPV, storageframework.DefaultFsDynamicPV, <ins> storageframework.NtfsDynamicPV, </ins> } return InitCustomVolumeIOTestSuite(patterns) }", "positive_passages": [{"docid": "doc-en-kubernetes-0adb5aef0ac6855d53f98480f83c42da417641735fd51e124c8667d192575ced", "text": "last case is reconstruction failed (in this csi-host-path test, reconstruction will fail due to issue related to , it fail to check mount point for csi hostpath driver because it is using a bind mount of the same device ). In this case, reconciler will try to clean up mounts directly, but only published volume path, not the staged volume path (this logic is not implemented due to missing information). As a workaround, we can now disable check-volume-lifecycle if it does not cause other issues. Then we will work on to make sure csi-host-path driver can pass volume mountpoint check during reconstruction.\nThis issue is now mitigated with merged. There are two longer-term issues that are isolated to hostpath plugins (and maybe other plugins that are similar in behavior, perhaps emptydir and similar?): related to IsLikelyNotMountPoint as mentioned. Because these don't impact the core volume machinery and are not regressions, this issue doesn't need to be release blocking. We'll close this issue once (2) is tracked.\nis the IsLikelyNotMountPoint issue\nafter is merged, two csi-hostpath driver subpath test can pass, and two in-tree driver gracefully delete tests were skipped. https://k8s-\ncan you please cherry-pick to release-1.22 branch?\nOpened cherry-pick, please review:\n- what is the plan for reenabling them?\ncherry-pick merged!\nCheng and I will work on solving IsLikelyNotMountPoint issue for hostpath drivers. That should allow test to pass and we can enable them.\nCan this be removed from the milestone now that the workarounds have been merged, while leaving this issue open to track further work?\nWe can use existing issue to track the real fix. /close\nClosing this issue. <detailsIn response to : We can use existing issue to track the real fix. 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", "commid": "kubernetes_issue_103651", "tokennum": 438}], "negative_passages": []}
{"query_id": "q-en-kubernetes-78166db65ca37a91a7d74b4e89cc9208889ff6a9bf1545bf5137d94b7c48c55a", "query": "<ins> /* Copyright 2016 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package e2e_node import ( \"k8s.io/kubernetes/pkg/api\" \"k8s.io/kubernetes/pkg/kubelet\" kubecontainer \"k8s.io/kubernetes/pkg/kubelet/container\" \"k8s.io/kubernetes/pkg/util/uuid\" \"k8s.io/kubernetes/test/e2e/framework\" . \"github.com/onsi/ginkgo\" ) const logString = \"This is the expected log content of this node e2e test\" var _ = framework.KubeDescribe(\"ContainerLogPath\", func() { f := framework.NewDefaultFramework(\"kubelet-container-log-path\") Describe(\"Pod with a container\", func() { Context(\"printed log to stdout\", func() { It(\"should print log to correct log path\", func() { podClient := f.PodClient() ns := f.Namespace.Name logDirVolumeName := \"log-dir-vol\" logDir := kubelet.ContainerLogsDir logPodName := \"logger-\" + string(uuid.NewUUID()) logContName := \"logger-c-\" + string(uuid.NewUUID()) checkPodName := \"checker\" + string(uuid.NewUUID()) checkContName := \"checker-c-\" + string(uuid.NewUUID()) logPod := &api.Pod{ ObjectMeta: api.ObjectMeta{ Name: logPodName, }, Spec: api.PodSpec{ // this pod is expected to exit successfully RestartPolicy: api.RestartPolicyNever, Containers: []api.Container{ { Image:   \"gcr.io/google_containers/busybox:1.24\", Name:    logContName, Command: []string{\"sh\", \"-c\", \"echo \" + logString}, }, }, }, } podClient.Create(logPod) err := framework.WaitForPodSuccessInNamespace(f.ClientSet, logPodName, ns) framework.ExpectNoError(err, \"Failed waiting for pod: %s to enter success state\", logPodName) // get containerID from created Pod createdLogPod, err := podClient.Get(logPodName) logConID := kubecontainer.ParseContainerID(createdLogPod.Status.ContainerStatuses[0].ContainerID) framework.ExpectNoError(err, \"Failed to get pod: %s\", logPodName) expectedlogFile := logDir + \"/\" + logPodName + \"_\" + ns + \"_\" + logContName + \"-\" + logConID.ID + \".log\" checkPod := &api.Pod{ ObjectMeta: api.ObjectMeta{ Name: checkPodName, }, Spec: api.PodSpec{ // this pod is expected to exit successfully RestartPolicy: api.RestartPolicyNever, Containers: []api.Container{ { Image: \"gcr.io/google_containers/busybox:1.24\", Name:  checkContName, // If we find expected log file and contains right content, exit 0 // else, keep checking until test timeout Command: []string{\"sh\", \"-c\", \"while true; do if [ -e \" + expectedlogFile + \" ] && grep -q \" + logString + \" \" + expectedlogFile + \"; then exit 0; fi; sleep 1; done\"}, VolumeMounts: []api.VolumeMount{ { Name: logDirVolumeName, // mount ContainerLogsDir to the same path in container MountPath: expectedlogFile, ReadOnly:  true, }, }, }, }, Volumes: []api.Volume{ { Name: logDirVolumeName, VolumeSource: api.VolumeSource{ HostPath: &api.HostPathVolumeSource{ Path: expectedlogFile, }, }, }, }, }, } podClient.Create(checkPod) err = framework.WaitForPodSuccessInNamespace(f.ClientSet, checkPodName, ns) framework.ExpectNoError(err, \"Failed waiting for pod: %s to enter success state\", checkPodName) }) }) }) }) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-0ad427ca9c00c618017f4be9fb19a1df6f4ab39ddc68f128fc109eb4d0409cbf", "text": "Cluster logging assumes kubelet stores container log at a specific directory with specific name. Currently the path is: After the CRI work, the path will be: However, we don't have test coverage for this. We don't even know whether the log files are there or not. We should add a node e2e test for this, basically: 1) Create a container which prints logs 2) Check whether the expected log file is created. 3) Check whether the logs are collected in the file as expected. And it would be better to launch a pod to do the check instead of accessing local file system directly, which makes containerizing easier. /cc because you are collecting missing test. /cc\nI will try to add a node-e2e test there\nI think it's ok to add this for CRI. But there maybe problems on today's interface for rkt. If I'm not wrong, rkt does't store logs at same location with docker. cc/ Is this true?\nThanks! :)\nAfter gets merged, we need to update the test to verify the cri log path.", "commid": "kubernetes_issue_34661", "tokennum": 234}], "negative_passages": []}
{"query_id": "q-en-kubernetes-78a2d57d5542e1d6ccb581cae9dbf204cc879816a4a8ef60ba16202360d666b3", "query": "<ins> #!/usr/bin/env bash # Copyright 2018 The Kubernetes Authors. # # Licensed under the Apache License, Version 2.0 (the \"License\"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # #     http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an \"AS IS\" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. set -o errexit set -o nounset set -o pipefail KUBE_ROOT=$(dirname \"${BASH_SOURCE[0]}\")/.. source \"${KUBE_ROOT}/hack/lib/init.sh\" # upstream shellcheck latest stable image as of January 10th, 2019 SHELLCHECK_IMAGE=\"koalaman/shellcheck-alpine:v0.6.0@sha256:7d4d712a2686da99d37580b4e2f45eb658b74e4b01caf67c1099adc294b96b52\" SHELLCHECK_CONTAINER=\"k8s-shellcheck\" # disabled lints disabled=( # this lint dissalows non-constant source, which we use extensively 1090 # this lint prefers command -v to which, they are not the same 2230 ) # comma separate for passing to shellcheck join_by() { local IFS=\"$1\"; shift; echo \"$*\"; } SHELLCHECK_DISABLED=\"$(join_by , \"${disabled[@]}\")\" readonly SHELLCHECK_DISABLED cd \"${KUBE_ROOT}\" # find all shell scripts excluding ./_*, ./.git/*, ./vendor*, # and anything git-ignored all_shell_scripts=() while IFS=$'n' read -r script; do git check-ignore -q \"$script\" || all_shell_scripts+=(\"$script\"); done < <(find . -name \"*.sh\"  -not (  -path ./_*      -o  -path ./.git*   -o  -path ./vendor*     )) # make sure known failures are sorted failure_file=\"${KUBE_ROOT}/hack/.shellcheck_failures\" if ! diff -u \"${failure_file}\" <(LC_ALL=C sort \"${failure_file}\"); then { echo echo \"hack/.shellcheck_failures is not in alphabetical order. Please sort it:\" echo echo \"  LC_ALL=C sort -o hack/.shellcheck_failures hack/.shellcheck_failures\" echo } >&2 false fi # load known failure files failing_files=() while IFS=$'n' read -r script; do failing_files+=(\"$script\"); done < <(cat \"${failure_file}\") # TODO(bentheelder): we should probably move this and the copy in verify-golint.sh # to one of the bash libs array_contains () { local seeking=$1; shift # shift will iterate through the array local in=1 # in holds the exit status for the function for element; do if [[ \"$element\" == \"$seeking\" ]]; then in=0 # set in to 0 since we found it break fi done return $in } # creates the shellcheck container for later user create_container () { # TODO(bentheelder): this is a performance hack, we create the container with # a sleep MAX_INT32 so that it is effectively paused. # We then repeatedly exec to it to run each shellcheck, and later rm it when # we're done. # This is incredibly much faster than creating a container for each shellcheck # call ... docker run --name \"${SHELLCHECK_CONTAINER}\" -d --rm -v \"${KUBE_ROOT}:${KUBE_ROOT}\" -w \"${KUBE_ROOT}\" --entrypoint=\"sleep\" \"${SHELLCHECK_IMAGE}\" 2147483647 } # removes the shellcheck container remove_container () { docker rm -f \"${SHELLCHECK_CONTAINER}\" &> /dev/null || true } # remove any previous container, ensure we will attempt to cleanup on exit, # and create the container remove_container trap remove_container EXIT if ! output=\"$(create_container 2>&1)\"; then { echo \"Failed to create shellcheck container with output: \" echo \"\" echo \"${output}\" } >&2 exit 1 fi # lint each script, tracking failures errors=() not_failing=() for f in \"${all_shell_scripts[@]}\"; do set +o errexit failedLint=$(docker exec -t \"${SHELLCHECK_CONTAINER}\" shellcheck --exclude=\"${SHELLCHECK_DISABLED}\" \"${f}\") set -o errexit array_contains \"${f}\" \"${failing_files[@]}\" && in_failing=$? || in_failing=$? if [[ -n \"${failedLint}\" ]] && [[ \"${in_failing}\" -ne \"0\" ]]; then errors+=( \"${failedLint}\" ) fi if [[ -z \"${failedLint}\" ]] && [[ \"${in_failing}\" -eq \"0\" ]]; then not_failing+=( \"${f}\" ) fi done # Check to be sure all the packages that should pass lint are. if [ ${#errors[@]} -eq 0 ]; then echo 'Congratulations!  All shell files have been linted.' else { echo \"Errors from shellcheck:\" for err in \"${errors[@]}\"; do echo \"$err\" done echo echo 'Please review the above warnings. You can test via \"./hack/verify-shellcheck\"' echo 'If the above warnings do not make sense, you can exempt this package from shellcheck' echo 'checking by adding it to hack/.shellcheck_failures (if your reviewer is okay with it).' echo } >&2 false fi if [[ ${#not_failing[@]} -gt 0 ]]; then { echo \"Some packages in hack/.shellcheck_failures are passing shellcheck. Please remove them.\" echo for f in \"${not_failing[@]}\"; do echo \"  $f\" done echo } >&2 false fi # Check that all failing_packages actually still exist gone=() for f in \"${failing_files[@]}\"; do array_contains \"$f\" \"${all_shell_scripts[@]}\" || gone+=( \"$f\" ) done if [[ ${#gone[@]} -gt 0 ]]; then { echo \"Some files in hack/.shellcheck_failures do not exist anymore. Please remove them.\" echo for f in \"${gone[@]}\"; do echo \"  $f\" done echo } >&2 false fi </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-33260ec64a7d900f1342ac27e4dcabb354b23351ec3e8ae604c63a04e69f42d4", "text": "is a bash script linter which could help catch common problems in our (numerous) bash scripts. I know we'd like to reduce our use of bash scripts, but until then I think being stricter about script quality would be helpful. /cc\ncc you were talking about this earlier. It has to only check modified lines.\nFalse positives are a problem. For instance, not being able to follow a call through an environment variable causes an error. I would be much more comfortable with a non-blocking way to point out these issues, and leave to it human judgement.\nYeah, I've been interested in doing this for a while, but can be pretty persnickety and I haven't yet taken the time to configure it to be less noisy (or figure out if it can be). It's good, though.\nYeah, it would definitely need to be configured to ignore a lot of types of errors, but I still think it could be used to check for some types of errors. We could start with a pretty minimal set.\nI would settle for something that just produced a quick-fix format artifact in the GCS bucket, and then the PR munger reading from it and commenting on the PR. We could re-use that for other linters too.\nhas been pretty accurate historically.\nshellcheck, not spellcheck\nreading too many issues in a on\n/sig testing /priority awaiting-more-evidence Might be more noise than it's worth, but we do pylint our .py scripts now\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with .", "commid": "kubernetes_issue_24614", "tokennum": 500}], "negative_passages": []}
{"query_id": "q-en-kubernetes-78a2d57d5542e1d6ccb581cae9dbf204cc879816a4a8ef60ba16202360d666b3", "query": "<ins> #!/usr/bin/env bash # Copyright 2018 The Kubernetes Authors. # # Licensed under the Apache License, Version 2.0 (the \"License\"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # #     http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an \"AS IS\" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. set -o errexit set -o nounset set -o pipefail KUBE_ROOT=$(dirname \"${BASH_SOURCE[0]}\")/.. source \"${KUBE_ROOT}/hack/lib/init.sh\" # upstream shellcheck latest stable image as of January 10th, 2019 SHELLCHECK_IMAGE=\"koalaman/shellcheck-alpine:v0.6.0@sha256:7d4d712a2686da99d37580b4e2f45eb658b74e4b01caf67c1099adc294b96b52\" SHELLCHECK_CONTAINER=\"k8s-shellcheck\" # disabled lints disabled=( # this lint dissalows non-constant source, which we use extensively 1090 # this lint prefers command -v to which, they are not the same 2230 ) # comma separate for passing to shellcheck join_by() { local IFS=\"$1\"; shift; echo \"$*\"; } SHELLCHECK_DISABLED=\"$(join_by , \"${disabled[@]}\")\" readonly SHELLCHECK_DISABLED cd \"${KUBE_ROOT}\" # find all shell scripts excluding ./_*, ./.git/*, ./vendor*, # and anything git-ignored all_shell_scripts=() while IFS=$'n' read -r script; do git check-ignore -q \"$script\" || all_shell_scripts+=(\"$script\"); done < <(find . -name \"*.sh\"  -not (  -path ./_*      -o  -path ./.git*   -o  -path ./vendor*     )) # make sure known failures are sorted failure_file=\"${KUBE_ROOT}/hack/.shellcheck_failures\" if ! diff -u \"${failure_file}\" <(LC_ALL=C sort \"${failure_file}\"); then { echo echo \"hack/.shellcheck_failures is not in alphabetical order. Please sort it:\" echo echo \"  LC_ALL=C sort -o hack/.shellcheck_failures hack/.shellcheck_failures\" echo } >&2 false fi # load known failure files failing_files=() while IFS=$'n' read -r script; do failing_files+=(\"$script\"); done < <(cat \"${failure_file}\") # TODO(bentheelder): we should probably move this and the copy in verify-golint.sh # to one of the bash libs array_contains () { local seeking=$1; shift # shift will iterate through the array local in=1 # in holds the exit status for the function for element; do if [[ \"$element\" == \"$seeking\" ]]; then in=0 # set in to 0 since we found it break fi done return $in } # creates the shellcheck container for later user create_container () { # TODO(bentheelder): this is a performance hack, we create the container with # a sleep MAX_INT32 so that it is effectively paused. # We then repeatedly exec to it to run each shellcheck, and later rm it when # we're done. # This is incredibly much faster than creating a container for each shellcheck # call ... docker run --name \"${SHELLCHECK_CONTAINER}\" -d --rm -v \"${KUBE_ROOT}:${KUBE_ROOT}\" -w \"${KUBE_ROOT}\" --entrypoint=\"sleep\" \"${SHELLCHECK_IMAGE}\" 2147483647 } # removes the shellcheck container remove_container () { docker rm -f \"${SHELLCHECK_CONTAINER}\" &> /dev/null || true } # remove any previous container, ensure we will attempt to cleanup on exit, # and create the container remove_container trap remove_container EXIT if ! output=\"$(create_container 2>&1)\"; then { echo \"Failed to create shellcheck container with output: \" echo \"\" echo \"${output}\" } >&2 exit 1 fi # lint each script, tracking failures errors=() not_failing=() for f in \"${all_shell_scripts[@]}\"; do set +o errexit failedLint=$(docker exec -t \"${SHELLCHECK_CONTAINER}\" shellcheck --exclude=\"${SHELLCHECK_DISABLED}\" \"${f}\") set -o errexit array_contains \"${f}\" \"${failing_files[@]}\" && in_failing=$? || in_failing=$? if [[ -n \"${failedLint}\" ]] && [[ \"${in_failing}\" -ne \"0\" ]]; then errors+=( \"${failedLint}\" ) fi if [[ -z \"${failedLint}\" ]] && [[ \"${in_failing}\" -eq \"0\" ]]; then not_failing+=( \"${f}\" ) fi done # Check to be sure all the packages that should pass lint are. if [ ${#errors[@]} -eq 0 ]; then echo 'Congratulations!  All shell files have been linted.' else { echo \"Errors from shellcheck:\" for err in \"${errors[@]}\"; do echo \"$err\" done echo echo 'Please review the above warnings. You can test via \"./hack/verify-shellcheck\"' echo 'If the above warnings do not make sense, you can exempt this package from shellcheck' echo 'checking by adding it to hack/.shellcheck_failures (if your reviewer is okay with it).' echo } >&2 false fi if [[ ${#not_failing[@]} -gt 0 ]]; then { echo \"Some packages in hack/.shellcheck_failures are passing shellcheck. Please remove them.\" echo for f in \"${not_failing[@]}\"; do echo \"  $f\" done echo } >&2 false fi # Check that all failing_packages actually still exist gone=() for f in \"${failing_files[@]}\"; do array_contains \"$f\" \"${all_shell_scripts[@]}\" || gone+=( \"$f\" ) done if [[ ${#gone[@]} -gt 0 ]]; then { echo \"Some files in hack/.shellcheck_failures do not exist anymore. Please remove them.\" echo for f in \"${gone[@]}\"; do echo \"  $f\" done echo } >&2 false fi </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-7c2396e8c525e9f1f7bfa4cd4f910bc5e5cdd53da779129188a0590e81ff81c5", "text": "Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nI'd like to reopen this, and eventually implement (first we need to deal with the failures ...) I've easily found a lot of bugs in test-infra and kubernetes/kubernetes bash with shellcheck. See also /assign\n/reopen /remove-lifecycle rotten /priority important-longterm\nReopening this issue. <detailsIn response to : /reopen /remove-lifecycle rotten /priority important-longterm 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\nWe also have non-blocking and optionally-run presubmits, even just having an easy way for reviewers to request a shellcheck result for changed files seems like something we should do. I also think we should fix the existing failures. Glancing through some k/k bash with shellcheck in my editor, these generally seem to be things that are actually wrong.\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten coming back to this hopefully\nThis is done now. Only took two years :^)", "commid": "kubernetes_issue_24614", "tokennum": 400}], "negative_passages": []}
{"query_id": "q-en-kubernetes-78b102b7aa96c0d0cd845781c491378a8c9e0f4f46b03a9ffa3426f3d2e8ed55", "query": "} } } <ins> func TestGetStorageAccount(t *testing.T) { ctrl := gomock.NewController(t) defer ctrl.Finish() cloud := &Cloud{} name := \"testAccount\" location := \"testLocation\" networkID := \"networkID\" accountProperties := storage.AccountProperties{ NetworkRuleSet: &storage.NetworkRuleSet{ VirtualNetworkRules: &[]storage.VirtualNetworkRule{ { VirtualNetworkResourceID: &networkID, Action:                   storage.Allow, State:                    \"state\", }, }, }} account := storage.Account{ Sku: &storage.Sku{ Name: \"testSku\", Tier: \"testSkuTier\", }, Kind:              \"testKind\", Location:          &location, Name:              &name, AccountProperties: &accountProperties, } testResourceGroups := []storage.Account{account} accountOptions := &AccountOptions{ ResourceGroup:             \"rg\", VirtualNetworkResourceIDs: []string{networkID}, } mockStorageAccountsClient := mockstorageaccountclient.NewMockInterface(ctrl) cloud.StorageAccountClient = mockStorageAccountsClient mockStorageAccountsClient.EXPECT().ListByResourceGroup(gomock.Any(), \"rg\").Return(testResourceGroups, nil).Times(1) accountsWithLocations, err := cloud.getStorageAccounts(accountOptions) if err != nil { t.Errorf(\"unexpected error: %v\", err) } if accountsWithLocations == nil { t.Error(\"unexpected error as returned accounts are nil\") } if len(accountsWithLocations) == 0 { t.Error(\"unexpected error as returned accounts slice is empty\") } expectedAccountWithLocation := accountWithLocation{ Name:        \"testAccount\", StorageType: \"testSku\", Location:    \"testLocation\", } accountWithLocation := accountsWithLocations[0] if accountWithLocation.Name != expectedAccountWithLocation.Name { t.Errorf(\"expected %s, but was %s\", accountWithLocation.Name, expectedAccountWithLocation.Name) } if accountWithLocation.StorageType != expectedAccountWithLocation.StorageType { t.Errorf(\"expected %s, but was %s\", accountWithLocation.StorageType, expectedAccountWithLocation.StorageType) } if accountWithLocation.Location != expectedAccountWithLocation.Location { t.Errorf(\"expected %s, but was %s\", accountWithLocation.Location, expectedAccountWithLocation.Location) } } func TestGetStorageAccountEdgeCases(t *testing.T) { ctrl := gomock.NewController(t) defer ctrl.Finish() cloud := &Cloud{} // default account with name, location, sku, kind name := \"testAccount\" location := \"testLocation\" sku := &storage.Sku{ Name: \"testSku\", Tier: \"testSkuTier\", } account := storage.Account{ Sku:      sku, Kind:     \"testKind\", Location: &location, Name:     &name, } accountPropertiesWithoutNetworkRuleSet := storage.AccountProperties{NetworkRuleSet: nil} accountPropertiesWithoutVirtualNetworkRules := storage.AccountProperties{ NetworkRuleSet: &storage.NetworkRuleSet{ VirtualNetworkRules: nil, }} tests := []struct { testCase           string testAccountOptions *AccountOptions testResourceGroups []storage.Account expectedResult     []accountWithLocation expectedError      error }{ { testCase: \"account name is nil\", testAccountOptions: &AccountOptions{ ResourceGroup: \"rg\", }, testResourceGroups: []storage.Account{}, expectedResult:     []accountWithLocation{}, expectedError:      nil, }, { testCase: \"account location is nil\", testAccountOptions: &AccountOptions{ ResourceGroup: \"rg\", }, testResourceGroups: []storage.Account{{Name: &name}}, expectedResult:     []accountWithLocation{}, expectedError:      nil, }, { testCase: \"account sku is nil\", testAccountOptions: &AccountOptions{ ResourceGroup: \"rg\", }, testResourceGroups: []storage.Account{{Name: &name, Location: &location}}, expectedResult:     []accountWithLocation{}, expectedError:      nil, }, { testCase: \"account options type is not empty and not equal account storage type\", testAccountOptions: &AccountOptions{ ResourceGroup: \"rg\", Type:          \"testAccountOptionsType\", }, testResourceGroups: []storage.Account{account}, expectedResult:     []accountWithLocation{}, expectedError:      nil, }, { testCase: \"account options kind is not empty and not equal account type\", testAccountOptions: &AccountOptions{ ResourceGroup: \"rg\", Kind:          \"testAccountOptionsKind\", }, testResourceGroups: []storage.Account{account}, expectedResult:     []accountWithLocation{}, expectedError:      nil, }, { testCase: \"account options location is not empty and not equal account location\", testAccountOptions: &AccountOptions{ ResourceGroup: \"rg\", Location:      \"testAccountOptionsLocation\", }, testResourceGroups: []storage.Account{account}, expectedResult:     []accountWithLocation{}, expectedError:      nil, }, { testCase: \"account options account properties are nil\", testAccountOptions: &AccountOptions{ ResourceGroup:             \"rg\", VirtualNetworkResourceIDs: []string{\"id\"}, }, testResourceGroups: []storage.Account{}, expectedResult:     []accountWithLocation{}, expectedError:      nil, }, { testCase: \"account options account properties network rule set is nil\", testAccountOptions: &AccountOptions{ ResourceGroup:             \"rg\", VirtualNetworkResourceIDs: []string{\"id\"}, }, testResourceGroups: []storage.Account{{Name: &name, Kind: \"kind\", Location: &location, Sku: sku, AccountProperties: &accountPropertiesWithoutNetworkRuleSet}}, expectedResult:     []accountWithLocation{}, expectedError:      nil, }, { testCase: \"account options account properties virtual network rule is nil\", testAccountOptions: &AccountOptions{ ResourceGroup:             \"rg\", VirtualNetworkResourceIDs: []string{\"id\"}, }, testResourceGroups: []storage.Account{{Name: &name, Kind: \"kind\", Location: &location, Sku: sku, AccountProperties: &accountPropertiesWithoutVirtualNetworkRules}}, expectedResult:     []accountWithLocation{}, expectedError:      nil, }, } for _, test := range tests { t.Logf(\"running test case: %s\", test.testCase) mockStorageAccountsClient := mockstorageaccountclient.NewMockInterface(ctrl) cloud.StorageAccountClient = mockStorageAccountsClient mockStorageAccountsClient.EXPECT().ListByResourceGroup(gomock.Any(), \"rg\").Return(test.testResourceGroups, nil).AnyTimes() accountsWithLocations, err := cloud.getStorageAccounts(test.testAccountOptions) if err != test.expectedError { t.Errorf(\"unexpected error: %v\", err) } if len(accountsWithLocations) != len(test.expectedResult) { t.Error(\"unexpected error as returned accounts slice is not empty\") } } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-4915683bef189ef7cc4e0ae9494c2fe05f18b93b7b90a4cf05226bf1e9ad07a8", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : and functions need unit tests Why is this needed: /kind test /sig cloud-provider /area provider/azure /assign\nThe label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : What would you like to be : /sig cloud-provider /area provider/azure 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\nrelated to\ncc\n/good-first-issue\nThis request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /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\nHi I'd like to give this one a go, if no one is currently working on it.\nsure, go ahead, thanks\nI pushed some first tests for", "commid": "kubernetes_issue_94240", "tokennum": 250}], "negative_passages": []}
{"query_id": "q-en-kubernetes-78cf0c08fe6e7e894e6a1d7042e53761a45809ee04c9a04cb3d6c09248de1442", "query": "} // we didn't validate against any provider, reject the pod and give the errors for each attempt <del> klog.V(4).Infof(\"unable to validate pod %s (generate: %s) in namespace %s against any pod security policy: %v\", pod.Name, pod.GenerateName, a.GetNamespace(), validationErrs) return admission.NewForbidden(a, fmt.Errorf(\"unable to validate against any pod security policy: %v\", validationErrs)) </del> <ins> klog.V(4).Infof(\"unable to admit pod %s (generate: %s) in namespace %s against any pod security policy: %v\", pod.Name, pod.GenerateName, a.GetNamespace(), validationErrs) return admission.NewForbidden(a, fmt.Errorf(\"PodSecurityPolicy: unable to admit pod: %v\", validationErrs)) </ins> } // Validate verifies attributes against the PodSecurityPolicy", "positive_passages": [{"docid": "doc-en-kubernetes-d654f914f6cdd0bd3bce5db6eb3c4ebef631bd8d2558ac9d591cab12ba724061", "text": "What happened: e2e tests detect whether PSP is enabled based on presence of PSP API objects. An addon that proactively includes a PSP in a manifest can trigger that detection and enable PSP-specific e2e tests that should not be run. What you expected to happen: In addition to detecting presence of PSP objects, consider dry-run creating a pod and verifying the annotation indicating the selected PSP policy is , indicating the admission plugin is active. /sig auth /assign", "commid": "kubernetes_issue_91463", "tokennum": 109}], "negative_passages": []}
{"query_id": "q-en-kubernetes-78ff5afa23de91ff6a37d9ac491c6b64d66b20e4f99bacd34c71088b1a0c077a", "query": "<del> 1.4 </del> <ins> 1.5 </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-2d0ebe90b3c755e0edf33c6811bf431b4c51fd00f4f7b6a1d49649dd59cb487b", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: Used the endpoint /BumpMetric to create fake metrics for Prometheus. When I tried to curl /metrics I got the following response: Bad request. Not a POST request What you expected to happen: I expected to see something like this: # HELP info message. # TYPE gauge 0. How to reproduce it (as minimally and precisely as possible): Following the docs, after having it running inside kubernetes: Anything else we need to know?: Looks like introduced this by mistake. Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: <!-- DO NOT EDIT BELOW THIS LINE --/kind bug\n/sig testing", "commid": "kubernetes_issue_72403", "tokennum": 213}], "negative_passages": []}
{"query_id": "q-en-kubernetes-790ce1d1e1af11c65dc96d5f9e25024ec912f3647beeae4f789169aab489fd25", "query": "Client: http.DefaultClient, Port:   *kubelet_port, } <ins> random := rand.New(rand.NewSource(int64(time.Now().Nanosecond()))) </ins> storage := map[string]apiserver.RESTStorage{ <del> \"pods\": registry.MakePodRegistryStorage(podRegistry, containerInfo, registry.MakeFirstFitScheduler(machineList, podRegistry)), </del> <ins> \"pods\": registry.MakePodRegistryStorage(podRegistry, containerInfo, registry.MakeFirstFitScheduler(machineList, podRegistry, random)), </ins> \"replicationControllers\": registry.MakeControllerRegistryStorage(controllerRegistry), \"services\":               registry.MakeServiceRegistryStorage(serviceRegistry), }", "positive_passages": [{"docid": "doc-en-kubernetes-cd494847d4bddf9ea80027a9691be245174d67d67dcf4a48743332a9d199dc09", "text": "This was the root cause of rancher/rancher. In , when is called, it is given the oldVersion of an object and the newVersion of the object. It then uses the indexers to calculate the old values (from the old version) and the new updated values. In cases where are size of 1, are of size greater than 1, and contain the sole value from , the key will be deleted for the old value will be deleted and won't be re-. This is due to the two for loops at the end of the method which are used for optimization. When the first for loop is processed, . Because of this, the key is deleted from the index for this value. In the second for loop, the , and for at least one of the values . The continue statement causes the key to not be to the index for this value (and since the value was deleted in the prior for loop, it no longer exists in the index for this value), despite the fact that the indicated that this is the desired state. Since specified that this value was still valid for this object, the key should not be deleted from the index for this value, or it should be re- when it is re-discovered in . Either way, the end state of the index should include this key in the set for the specified value. I've created a which demonstrates the issue (branch is ). To use it (assuming that you have a running kubernetes cluster to use with): the controller: . the foo crd: the controller (assumes that you have $KUBECONFIG set to the file path of your kubeconfig file). an example foo with only one label: . Observe, in the logs of the running sample-controller, that the indexer was able to locate this foo using the indexer. the foo to include a second label: . Observe, in the logs of the running sample-controller, that the indexer was not able to locate the foo using the first key any longer, despite the fact that the label was still on the object. The sample-controller fork adds an indexer for foo objects which uses the indexerFunction of . This function looks for labels that have a key with a prefix of and uses their values as index keys for the foo objects. For example, if I have a with a label of , the indexer will allow you to retrieve using .", "commid": "kubernetes_issue_109115", "tokennum": 500}], "negative_passages": []}
{"query_id": "q-en-kubernetes-790ce1d1e1af11c65dc96d5f9e25024ec912f3647beeae4f789169aab489fd25", "query": "Client: http.DefaultClient, Port:   *kubelet_port, } <ins> random := rand.New(rand.NewSource(int64(time.Now().Nanosecond()))) </ins> storage := map[string]apiserver.RESTStorage{ <del> \"pods\": registry.MakePodRegistryStorage(podRegistry, containerInfo, registry.MakeFirstFitScheduler(machineList, podRegistry)), </del> <ins> \"pods\": registry.MakePodRegistryStorage(podRegistry, containerInfo, registry.MakeFirstFitScheduler(machineList, podRegistry, random)), </ins> \"replicationControllers\": registry.MakeControllerRegistryStorage(controllerRegistry), \"services\":               registry.MakeServiceRegistryStorage(serviceRegistry), }", "positive_passages": [{"docid": "doc-en-kubernetes-582c669d9e852f593828621e1df0588db01f01d305d2c20cc4978aeea726760c", "text": "The controller's method has been altered to just ensure that the foos can be retrieved using the indexer for all valid labels. If the controller can't retrieve foo by using the value from a valid label, then it returns an error (it tries for all valid labels). This was originally discovered in a fork of client-go that we maintain. After we reverted the changes introduced by , our issues stopped occurring. N/A - This was introduced in and appears to be in all versions of the client v0.23+. N/A - issue is with client-go No response No response No response No response\n/sig api-machinery\nI think that you have background in this issue/area of the code. Would you mind taking a look at this issue and the PR that I have up to fix it? Please let me know if I've misunderstood anything.\n/assign Would you mind to take a look? Thank you /triage accepted\nThanks for reporting the issue. will address this issue\nReopening - since we need to cherrypick back to 1.23\nCherrypick is merged - closing.", "commid": "kubernetes_issue_109115", "tokennum": 230}], "negative_passages": []}
{"query_id": "q-en-kubernetes-791254237b92d1c50a3e918fd7b20d6938c2cc3634c627315dc9fa3e391bb9df", "query": "value: 512M - name: HEAP_NEWSIZE value: 100M <ins> - name: POD_NAMESPACE valueFrom: fieldRef: fieldPath: metadata.namespace </ins> image: gcr.io/google_containers/cassandra:v4 name: cassandra ports:", "positive_passages": [{"docid": "doc-en-kubernetes-600b05087b3e5a02baef82de4ad7a72820fecd2de58582bba171390ab13fae8d", "text": "The namespace seems to be hard coded :\ncc:\nThanks. We can improve it after v1 release.", "commid": "kubernetes_issue_10034", "tokennum": 22}], "negative_passages": []}
{"query_id": "q-en-kubernetes-79619cc714d88966391b6192a4dbd7c906b61e74235141101df701551937e425", "query": "\"github.com/GoogleCloudPlatform/kubernetes/pkg/api\" \"github.com/GoogleCloudPlatform/kubernetes/pkg/client\" \"github.com/GoogleCloudPlatform/kubernetes/pkg/runtime\" <ins> \"github.com/GoogleCloudPlatform/kubernetes/pkg/util\" </ins> ) func TestRunExposeService(t *testing.T) {", "positive_passages": [{"docid": "doc-en-kubernetes-9d5ff2ec60db4b621aa04c218edf9e88ebba3dc541b6528b009593e479ccf9f2", "text": "This was broken by , and therefore broken in as well. Any fix should be offered as a cherry pick so \"make release\" is clean there.\nI went ahead and worked something up for this this morning, to get Shippable builds back on the rails.", "commid": "kubernetes_issue_11105", "tokennum": 53}], "negative_passages": []}
{"query_id": "q-en-kubernetes-799472561da969b8176a827cf6ba2744cf87790f8ad12161a2205164c7653266", "query": "\"k8s.io/client-go/discovery\" \"k8s.io/client-go/dynamic\" \"k8s.io/client-go/kubernetes/fake\" <del> scheme \"k8s.io/client-go/kubernetes/scheme\" </del> \"k8s.io/client-go/metadata\" metadatafake \"k8s.io/client-go/metadata/fake\" restclient \"k8s.io/client-go/rest\"", "positive_passages": [{"docid": "doc-en-kubernetes-d7e6fda1614d5720cc8c8b15824f08c5e880f7950d0c5cc5cd811c2fcceb82ab", "text": "Because of this scheme mutation, this leads to concurrent use of the same scheme to cause the program to panic. It would be ideal to do this in some concurrent safe manner or add a warning or similar\n/sig api-machinery\n/assign\n/assign /triage accepted", "commid": "kubernetes_issue_107823", "tokennum": 54}], "negative_passages": []}
{"query_id": "q-en-kubernetes-79995acd2d6b8eef42217802ad36308670a372e69f3b1f71c3f8aa2150dce3e2", "query": "} defer monitoring.CleanupDescriptors(gcmService, projectID) <del> err = monitoring.CreateAdapter(tc.framework.Namespace.ObjectMeta.Name, monitoring.AdapterDefault) </del> <ins> err = monitoring.CreateAdapter(monitoring.AdapterDefault) </ins> if err != nil { framework.Failf(\"Failed to set up: %v\", err) } <del> defer monitoring.CleanupAdapter(tc.framework.Namespace.ObjectMeta.Name, monitoring.AdapterDefault) </del> <ins> defer monitoring.CleanupAdapter(monitoring.AdapterDefault) </ins> // Run application that exports the metric err = createDeploymentToScale(tc.framework, tc.kubeClient, tc.deployment, tc.pod)", "positive_passages": [{"docid": "doc-en-kubernetes-cecee0a132f84dbf6d5783d328e94b49c8666ebba8eef4ded1687e53b0451e97", "text": "/kind failing-test <!-- If this is a flake, please add: /kind flake --/sig autoscaling Looks like it just started happening today (@ 2020-09-15 03:54:19 +0000 UTC) !\ncc the namespace from the provided object \"kube-system\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=kube-system' to perform this operation. the namespace from the provided object \"custom-metrics\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=custom-metrics' to perform this operation. the namespace from the provided object \"custom-metrics\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=custom-metrics' to perform this operation.\nrelated fix:\nNo I don't think that's the fix for this (that is just a little cleanup). Actually I think we have to delete namespace parameter in line : Because before , the will have no actually effect. But now with the change of , it will have namespace : at the end of the command. But the namespace in yaml file is which is different from . We should not have parameter when applying from file because this test didn't have before, right? Related PR:\n/assign", "commid": "kubernetes_issue_94809", "tokennum": 318}], "negative_passages": []}
{"query_id": "q-en-kubernetes-799d065b91ee8da1c8ec9f07e9cf9fe7605b5729e05e7bea38d34bacd5aad24e", "query": "defer CleanupDescriptors(gcmService, projectID) // Both deployments - for old and new resource model - expose External Metrics API. <del> err = CreateAdapter(f.Namespace.Name, AdapterForOldResourceModel) </del> <ins> err = CreateAdapter(AdapterForOldResourceModel) </ins> if err != nil { framework.Failf(\"Failed to set up: %s\", err) } <del> defer CleanupAdapter(f.Namespace.Name, AdapterForOldResourceModel) </del> <ins> defer CleanupAdapter(AdapterForOldResourceModel) </ins> _, err = kubeClient.RbacV1().ClusterRoleBindings().Create(context.TODO(), HPAPermissions, metav1.CreateOptions{}) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-cecee0a132f84dbf6d5783d328e94b49c8666ebba8eef4ded1687e53b0451e97", "text": "/kind failing-test <!-- If this is a flake, please add: /kind flake --/sig autoscaling Looks like it just started happening today (@ 2020-09-15 03:54:19 +0000 UTC) !\ncc the namespace from the provided object \"kube-system\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=kube-system' to perform this operation. the namespace from the provided object \"custom-metrics\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=custom-metrics' to perform this operation. the namespace from the provided object \"custom-metrics\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=custom-metrics' to perform this operation.\nrelated fix:\nNo I don't think that's the fix for this (that is just a little cleanup). Actually I think we have to delete namespace parameter in line : Because before , the will have no actually effect. But now with the change of , it will have namespace : at the end of the command. But the namespace in yaml file is which is different from . We should not have parameter when applying from file because this test didn't have before, right? Related PR:\n/assign", "commid": "kubernetes_issue_94809", "tokennum": 318}], "negative_passages": []}
{"query_id": "q-en-kubernetes-79b4cdc9b7c98d59458911b10302739998f851371d6e03d4337b2d304ccc9153", "query": "Corefile: | __PILLAR__DNS__DOMAIN__:53 { errors <del> cache 30 </del> <ins> cache { success 9984 30 denial 9984 5 } </ins> reload loop bind __PILLAR__LOCAL__DNS__", "positive_passages": [{"docid": "doc-en-kubernetes-598a5e6d79587d97464d296fe938aac9741dc183fde75d2da349cdf55e566259", "text": "What happened: node-local-dns caches negative queries, causing things that do polling for orchestration to fail (like operators with StatefulSets). What you expected to happen: Have a minimal TTL for negative responses (alternatively just disable caching by setting the cache size to 0) that follows what was done for kube-dns: How to reproduce it (as minimally and precisely as possible): With node-local-dns cache deployed, in my cluster it was the that failed to create clusters because the cached entry didn't expire before it had exhausted all of it's retries. Environment: Kubernetes version (use ): 1.11.6 Cloud provider or hardware configuration: GKE OS (e.g. from /etc/os-release): any Kernel (e.g. ): any\n/sig network", "commid": "kubernetes_issue_74092", "tokennum": 186}], "negative_passages": []}
{"query_id": "q-en-kubernetes-79bcc461bc8d80201179cb07876ba1d6533924ce2fc4644ea6cb250d6c006bdc", "query": "StabilityLevel: metrics.ALPHA, }, ) <del> PreemptionVictims = metrics.NewGauge( &metrics.GaugeOpts{ Subsystem:      SchedulerSubsystem, Name:           \"pod_preemption_victims\", Help:           \"Number of selected preemption victims\", </del> <ins> PreemptionVictims = metrics.NewHistogram( &metrics.HistogramOpts{ Subsystem: SchedulerSubsystem, Name:      \"pod_preemption_victims\", Help:      \"Number of selected preemption victims\", // we think #victims>50 is pretty rare, therefore [50, +Inf) is considered a single bucket. Buckets:        metrics.LinearBuckets(5, 5, 10), </ins> StabilityLevel: metrics.ALPHA, }) PreemptionAttempts = metrics.NewCounter(", "positive_passages": [{"docid": "doc-en-kubernetes-747d699b97976a530bdb275e803e2be1bb68ac7168a6ff8b59806b000dbdf33f", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Change scheduler metric from Gauge to Histogram Why is this needed: is recorded for each preemption attempt. A histogram is better. /sig scheduling /help /good-first-issue\n/help /good-first-issue\nThis request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /help /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\nI can work on this issue.\n/assign\nI could work on this as well if doesn't have time to work on this.\nI am working on it, I will create the initial PR in less than a week. Sorry for the delay.", "commid": "kubernetes_issue_83464", "tokennum": 211}], "negative_passages": []}
{"query_id": "q-en-kubernetes-79e7d5526ea9f7287631b1dfc5a12237ddf8f082a0fd386cdf23991f8d6a4022", "query": "#   DOCKER_REGISTRY function start-kube-controller-manager { echo \"Start kubernetes controller-manager\" <ins> create-kubecontrollermanager-kubeconfig </ins> prepare-log-file /var/log/kube-controller-manager.log # Calculate variables and assemble the command line. local params=\"${CONTROLLER_MANAGER_TEST_LOG_LEVEL:-\"--v=2\"} ${CONTROLLER_MANAGER_TEST_ARGS:-} ${CLOUD_CONFIG_OPT}\" <ins> params+=\" --use-service-account-credentials\" </ins> params+=\" --cloud-provider=gce\" <del> params+=\" --master=127.0.0.1:8080\" </del> <ins> params+=\" --kubeconfig=/etc/srv/kubernetes/kube-controller-manager/kubeconfig\" </ins> params+=\" --root-ca-file=/etc/srv/kubernetes/ca.crt\" params+=\" --service-account-private-key-file=/etc/srv/kubernetes/server.key\" if [[ -n \"${ENABLE_GARBAGE_COLLECTOR:-}\" ]]; then", "positive_passages": [{"docid": "doc-en-kubernetes-19a61d82ec14336213ef377c4e39e11807c2ce9673880ce3d82a192d5a783624", "text": "Typically, the dns and dashboard is in crash loop. Ref cc\nif you check the file, does it contain lines like ?\nPrevious comment is ref: from I'll copy that to container-linux as well.", "commid": "kubernetes_issue_39395", "tokennum": 44}], "negative_passages": []}
{"query_id": "q-en-kubernetes-79fbc453a29b37c6ed37ce74d01ec8d101fffa10ad9b98ab631d5e02ce83047f", "query": "<del> apiVersion: v1 kind: ReplicationController metadata: name: es-data labels: component: elasticsearch role: data spec: replicas: 1 template: metadata: labels: component: elasticsearch role: data spec: serviceAccount: elasticsearch containers: - name: es-data securityContext: capabilities: add: - IPC_LOCK image: quay.io/pires/docker-elasticsearch-kubernetes:1.7.1-4 env: - name: KUBERNETES_CA_CERTIFICATE_FILE value: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt - name: NAMESPACE valueFrom: fieldRef: fieldPath: metadata.namespace - name: \"CLUSTER_NAME\" value: \"myesdb\" - name: NODE_MASTER value: \"false\" - name: HTTP_ENABLE value: \"false\" ports: - containerPort: 9300 name: transport protocol: TCP volumeMounts: - mountPath: /data name: storage volumes: - name: storage emptyDir: {} </del>", "positive_passages": [{"docid": "doc-en-kubernetes-5fef938b0452d0f6b58e576cd11f17813fb6d6b970f83a7868d905b7784a5e39", "text": "Presently, the elasticsearch example Kubernetes configurations target elasticsearch v1.7.1, which is quite old. As of this writing, the latest elasticsearch release is v5.6.2, with many deployment changes since then. Could the elasticsearch examples be updated to target the v5 series of elasticsearch? See for a more up to date reference configuration.\ncc\nhey it's been a long while since I last contributed to the docs. i can do it soon but i need pointers on how to properly do it.\nhey, so we need to update the stuff under examples/elasticsearch/ *&repos=kubernetes So basically update the images, yaml files etc and test that everything works (and submit a PR)\n/sig testing\nAh, so there's no documentation updates anymore. OK I'll take care of it, assign it to me.\nIssues 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\nGitHub didn't allow me to assign the following users: me. Note that only and repo collaborators can be assigned. <detailsIn response to : /assign me 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\n/assign pires\n/remove-lifecycle stale\nit seems that the example moved to I am now reading that repo guidelines and will update this there. I'll also open a PR that cleans this folder in the current repo and closes this issue.", "commid": "kubernetes_issue_53142", "tokennum": 387}], "negative_passages": []}
{"query_id": "q-en-kubernetes-79fcc80fe875ab470d3c2118f230c7076be428d6d4857d8af58b3a9ab0d9c5b4", "query": "framework.Failf(\"Container port output missing expected value. Wanted:'%s', got: %s\", nginxDefaultOutput, body) } }) <ins> It(\"should handle in-cluster config\", func() { By(\"overriding icc with values provided by flags\") kubectlPath := framework.TestContext.KubectlPath inClusterHost := strings.TrimSpace(framework.RunHostCmdOrDie(ns, simplePodName, \"printenv KUBERNETES_SERVICE_HOST\")) inClusterPort := strings.TrimSpace(framework.RunHostCmdOrDie(ns, simplePodName, \"printenv KUBERNETES_SERVICE_PORT\")) framework.RunKubectlOrDie(\"cp\", kubectlPath, ns+\"/\"+simplePodName+\":/\") By(\"getting pods with in-cluster configs\") execOutput := framework.RunHostCmdOrDie(ns, simplePodName, \"/kubectl get pods\") if matched, err := regexp.MatchString(\"nginx +1/1 +Running\", execOutput); err != nil || !matched { framework.Failf(\"Unexpected kubectl exec output: \", execOutput) } By(\"trying to use kubectl with invalid token\") _, err := framework.RunHostCmd(ns, simplePodName, \"/kubectl get pods --token=invalid --v=7 2>&1\") framework.Logf(\"got err %v\", err) Expect(err).To(HaveOccurred()) Expect(err).To(ContainSubstring(\"User \"system:anonymous\" cannot list pods in the namespace\")) Expect(err).To(ContainSubstring(\"Using in-cluster namespace\")) Expect(err).To(ContainSubstring(\"Using in-cluster configuration\")) Expect(err).To(ContainSubstring(\"Authorization: Bearer invalid\")) Expect(err).To(ContainSubstring(\"Response Status: 403 Forbidden\")) By(\"trying to use kubectl with invalid server\") _, err = framework.RunHostCmd(ns, simplePodName, \"/kubectl get pods --server=invalid --v=6 2>&1\") framework.Logf(\"got err %v\", err) Expect(err).To(HaveOccurred()) Expect(err).To(ContainSubstring(\"Unable to connect to the server\")) Expect(err).To(ContainSubstring(\"GET http://invalid/api\")) By(\"trying to use kubectl with invalid namespace\") output, _ := framework.RunHostCmd(ns, simplePodName, \"/kubectl get pods --namespace=invalid --v=6 2>&1\") Expect(output).To(ContainSubstring(\"No resources found\")) Expect(output).ToNot(ContainSubstring(\"Using in-cluster namespace\")) Expect(output).To(ContainSubstring(\"Using in-cluster configuration\")) if matched, _ := regexp.MatchString(fmt.Sprintf(\"GET http[s]?://%s:%s/api/v1/namespaces/invalid/pods\", inClusterHost, inClusterPort), output); !matched { framework.Failf(\"Unexpected kubectl exec output: \", output) } }) </ins> }) framework.KubeDescribe(\"Kubectl api-versions\", func() {", "positive_passages": [{"docid": "doc-en-kubernetes-4e19a56e8ccacbab4546f622baecdb0b8ef30250430c55f8bcdc4de99b100cd2", "text": "Found in openshift, but I'm pretty sure the codepaths are the same. That means the token is getting ignored and in-cluster config is being used in preference to flags.\nIs a similar issue?\nYep, kind of regression.\nSigh.\nYes, most likely the same cause.\nI'm on it.\nUnit test :)\nProbably will want to cherrypick this into 1.5.\nWIP in", "commid": "kubernetes_issue_38834", "tokennum": 89}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7a1aadd17d8f3dd3b6cd92351747a5efb92486aa3ea63933adf345036721e3f7", "query": "import ( \"fmt\" <ins> \"math/rand\" </ins> \"net\" \"net/url\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-cc18fa8624c9153eb5caf2824e8d5840bb7b2767a3286fa9c73b8b488eed7889", "text": "/kind bug What happened: Every time a health check is called on the APIServer via the endpoint, an etcd healthcheck is performed. However, as this just starts at the first server in the list passed to the apiserver binary all the healthchecks generate read load on a single etcd member. What you expected to happen: The first server that is checked should either increment (and wrap around) each time or be randomised to spread load around the cluster\n/assign\nI think a random check is ok.\n/sig api-machinery", "commid": "kubernetes_issue_61180", "tokennum": 117}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7a48b8ac5e0cae6ba33a21d2b5bbf341da232bd27761733846144565921ac2dd", "query": "return fmt.Errorf(\"error when parsing kube-proxy configmap template: %v\", err) } <del> proxyDaemonSetBytes, err := kubeadmutil.ParseTemplate(KubeProxyDaemonSet, struct{ ImageRepository, Arch, Version, ImageOverride, ClusterCIDR, MasterTaintKey, CloudTaintKey string }{ </del> <ins> proxyDaemonSetBytes, err := kubeadmutil.ParseTemplate(KubeProxyDaemonSet, struct{ ImageRepository, Arch, Version, ImageOverride, ExtraParams, ClusterCIDR, MasterTaintKey, CloudTaintKey string }{ </ins> ImageRepository: cfg.GetControlPlaneImageRepository(), Arch:            runtime.GOARCH, Version:         kubeadmutil.KubernetesVersionToImageTag(cfg.KubernetesVersion), ImageOverride:   cfg.UnifiedControlPlaneImage, <ins> ExtraParams:     getParams(cfg.FeatureGates), </ins> ClusterCIDR:     getClusterCIDR(cfg.Networking.PodSubnet), MasterTaintKey:  kubeadmconstants.LabelNodeRoleMaster, CloudTaintKey:   algorithm.TaintExternalCloudProvider,", "positive_passages": [{"docid": "doc-en-kubernetes-fdf6c8e5598e80992f62cef52eca112e7ba1d532fe8ace89dc932a5edac53dea", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: Currently, IPVS proxier does not run any e2e test cases. What you expected to happen: I think it's important to create test suite for IPVS in upstream CI which will help a lot in moving IPVS existing alpha. Anything else we need to know?: Let's work together. /sig network\nSelf /assign\nThere are to ways to do this work: , but doesn't support any kube-proxy config right now, so I had this pr , and also, need support it too, see this pr: kubernetes/kubernetes-anywhere build cluster. See this pr: kubernetes/test-infra The second way is much easier and faster, but I was told they gonna deprecated the , so in the long term, we still need and 's support. If anybody have better way or have some suggestion about this, please let me know, I'll be really appreciate, Thanks.", "commid": "kubernetes_issue_52834", "tokennum": 247}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7a4bc052901e82c4306d3f664dc859710543265a61e7b2f68a33be1d90a96448", "query": "description: The discovery.k8s.io API group MUST exist in the /apis discovery document. The discovery.k8s.io/v1 API group/version MUST exist in the /apis/discovery.k8s.io discovery document. The endpointslices resource MUST exist in the /apis/discovery.k8s.io/v1 <del> discovery document. API Server should create self referential Endpoints and EndpointSlices named \"kubernetes\" in the default namespace. </del> <ins> discovery document. The cluster MUST have a service named \"kubernetes\" on the default namespace referencing the API servers. The \"kubernetes.default\" service MUST have Endpoints and EndpointSlices pointing to each API server instance. </ins> release: v1.21 file: test/e2e/network/endpointslice.go - testname: EndpointSlice API", "positive_passages": [{"docid": "doc-en-kubernetes-7f1e6e7766f66194a4a76f7bcbc82118fdef24c779ae808892b54bf44f2870dc", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --E2E test fails. The test is implemented at: I would expect the test pass with these objects in place: AFAIK this fulfills the general requirement of the test that there's a corresponding endpointslice object with same addressing information as is on the endpoint object. IMO the test should rather look for epslice which is owned by the endpoint rather than relying on a hardcoded name. Add flag to kube-apiserver Manually create the endpoint with proper addressing for the api-server epslice \"mirroring\" create new endpointslice with name like --The test fails as it's hardcoded to look for endpointslice named I'm working on a PR to provide a fix proposal Kubernetes version (use ): 1.22.1 Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: k0s Network plugin and version (if this is a network-related bug): kube-router 1.3.1 Others:\n/sig testing\n/remove-sig testing /sig network EndpointSlices are owned by sig network.\n/kind failing-test\n/remove kind-bug /remove kind-failing-test The test is correct, apiserver must generates both endpoint and enpointslices with the special name \"kubernetes\" , that are the backends for the \"kubernetes.default\" service with the IP addresses of the apiservers. This special service \"kubernetes.default\" and its endpoints are used by clients with In-Cluster auto discovery. I think that whatever cluster that is not generating the endpoint and endpointslices for the \"kubernetes.default\" service should not meet Conformance, at least I can't see how automatic in-cluster configuration will work without that ... I only see option used for webhook tests, the other 2 reconcilers always create the endpoints and slices for \"kubernetes.default\" should we clarify the goal of this \"none\" option?\nYes, I do understand this. And in our case this is true, there is a svc called as there is also endpoints object called . This makes the in-cluster discovery work.", "commid": "kubernetes_issue_104612", "tokennum": 531}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7a4bc052901e82c4306d3f664dc859710543265a61e7b2f68a33be1d90a96448", "query": "description: The discovery.k8s.io API group MUST exist in the /apis discovery document. The discovery.k8s.io/v1 API group/version MUST exist in the /apis/discovery.k8s.io discovery document. The endpointslices resource MUST exist in the /apis/discovery.k8s.io/v1 <del> discovery document. API Server should create self referential Endpoints and EndpointSlices named \"kubernetes\" in the default namespace. </del> <ins> discovery document. The cluster MUST have a service named \"kubernetes\" on the default namespace referencing the API servers. The \"kubernetes.default\" service MUST have Endpoints and EndpointSlices pointing to each API server instance. </ins> release: v1.21 file: test/e2e/network/endpointslice.go - testname: EndpointSlice API", "positive_passages": [{"docid": "doc-en-kubernetes-e7b624ebdf04c04b0fd86ae888848c4f91744879af316f1243574b67dd031473", "text": "Otherwise we'd get much more errors in the conformance instead of this only one... :) In our case we're relying on the endpointslice mirroring to take care of creating the endpointslice object, which makes this test fail as it uses generated \"suffix\" on the object name. I have not dived too deep (yet) into the internals of endpointslices but I fail to see how the endpointslice object name really matters when both svc and endpoint object does have proper name.\noh, this seems interesting then ... who is creating the corresponding endpoint? can you paste a kubectl get endpoints -o yaml?\nthis is how it looks like in my cluster\nIn our case (k0s distro) it's our custom controller that is triggered when the controlplane is configured in HA mode. So this basically sets the api to mode . When our controller runs it has a configured LB address which it resolves to IP address(es) and creates the corresponding EP object. We do NOT create the endpointslice as we rely on the mirroring functionality to let it create and sync it. Here's the object details: Reading the code for API built-in endpoint reconcilers I see they set and create the endpointslice object by themselves. Yes, we could do that too in k0s but I fail to see why the name of the endpointslice object really matters at all.\nI agree the conformance test should not be looking up endpointslice by name. It should be using a label selector of to locate one or more endpointslices and verifying the ports and endpoints across them.\nFair enough, on the good side this also will simplify the KEP from to dual-stack the apiserver you are the expert in this area, can you PTAL at this discussion? /kind failing-test\nhmm the test description explicitly says the name of the object has to be \"kubernetes\", if the name is mandatory the test is correct, otherwise we need to rewrite the test description and talk with conformance people /area conformance\nthe description should be rewritten... the test is enforcing stricter requirements on endpointslices than required/expected\n/triage accepted", "commid": "kubernetes_issue_104612", "tokennum": 469}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7a70c122d47eeac8b6552f28650eb832693e8798e2ab6c2ed44cc46aee0219bd", "query": "} func wait(cmd string, args ...string) error { <ins> sigChannel := make(chan os.Signal, 1) signal.Notify(sigChannel, os.Interrupt) </ins> c := exec.Command(cmd, args...) c.Stdout = os.Stdout c.Stderr = os.Stderr if err := c.Start(); err != nil { return err } <ins> go func() { sig := <-sigChannel if err := c.Process.Signal(sig); err != nil { log.Fatalf(\"could not send %s signal %s: %v\", cmd, sig, err) } }() </ins> return c.Wait() }", "positive_passages": [{"docid": "doc-en-kubernetes-91b918bf4349bc4d86d996ff7ec289a620469d416a95bd3acf270a016c4f134a", "text": "Once e2e tests are running, the tests keep running even if I press and exit the process that controls the TTY. But the tests actually keep running in the background and they keep printing stuff on a shell prompt which has already returned and thereby clobbering the STDOUT\n/assign\nGitHub didn't allow me to assign the following users: oomichi. Note that only can be assigned. <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", "commid": "kubernetes_issue_43051", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7a7d351108ce6bad18c930e677c6eca88f40d1f74edddc1822196cd6d823209d", "query": "execAffinityTestForNonLBServiceWithTransition(f, cs, svc) }) <del> // TODO: Get rid of [DisabledForLargeClusters] tag when issue #56138 is fixed. </del> // [LinuxOnly]: Windows does not support session affinity. <del> ginkgo.It(\"should have session affinity work for LoadBalancer service with ESIPP on [Slow] [DisabledForLargeClusters] [LinuxOnly]\", func() { </del> <ins> ginkgo.It(\"should have session affinity work for LoadBalancer service with ESIPP on [Slow] [LinuxOnly]\", func() { </ins> // L4 load balancer affinity `ClientIP` is not supported on AWS ELB. e2eskipper.SkipIfProviderIs(\"aws\")", "positive_passages": [{"docid": "doc-en-kubernetes-23d2f241356f8f089aacd04cb02b22714ea2023d38ddcb3dae2268a8e3824c6f", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug This is a followup from filed separately now that we're not tracking this as part of 1.9 release. The tests have been disabled with [DisabledForLargeClusters] tag for now, and this fact will be mentioned in the scalability validation report for v1.9. This issue tracks fixing the test so the tag can be removed and the test ran again in the large cluster. /assign /kind e2e-test-failure\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIs this e2e test still broken?\nSorry for the confusion here. Currently this e2e test is disabled on extra large cluster due to some scalability issues with the load balancer related components. At the moment the issues haven't been completely resolved yet.\nok, adding priority so that I know it's not a 1.13 blocker. /priority important-longterm\ncc - this is why the relevant tests for are not part of the e2e suite.\nThis issue is still valid --- some action items on top of my head: Figure out a plan to make service controller properly handle operations in parallel. Check on the status for cloud providers (especially GCP, which the test ran against) on handling large number of nodes as LB backends. /remove-triage unresolved\nIssues 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 .", "commid": "kubernetes_issue_56138", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7a7d351108ce6bad18c930e677c6eca88f40d1f74edddc1822196cd6d823209d", "query": "execAffinityTestForNonLBServiceWithTransition(f, cs, svc) }) <del> // TODO: Get rid of [DisabledForLargeClusters] tag when issue #56138 is fixed. </del> // [LinuxOnly]: Windows does not support session affinity. <del> ginkgo.It(\"should have session affinity work for LoadBalancer service with ESIPP on [Slow] [DisabledForLargeClusters] [LinuxOnly]\", func() { </del> <ins> ginkgo.It(\"should have session affinity work for LoadBalancer service with ESIPP on [Slow] [LinuxOnly]\", func() { </ins> // L4 load balancer affinity `ClientIP` is not supported on AWS ELB. e2eskipper.SkipIfProviderIs(\"aws\")", "positive_passages": [{"docid": "doc-en-kubernetes-82e0e423f6c651003322d5e3ca8baa34b91f0522dd0c015fbde1e81f949704e6", "text": "/lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten /lifecycle frozen\n/reopen Reopening as is being reverted in\nReopened this issue. <detailsIn response to : /reopen Reopening as is being reverted in 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\nthese tests are flaking in xref\ncc since these were enabled by\nYeah - though these failures doesn't seem to be scale related, they seem to be test related to me. This basically means nodes without public ips: It's pretty much the same thing as (just for a different test). should be addressing these kinds of errors. [Not a release blocker for sure]\nBTW - has been opened directly for this one.\n... so since is closed, Can we close this and re-enable for large clusters ? (i.e. remove the Tag in that disables this test) ? I'm not up to speed on the history but 2 related notes I came across digging into related test today... 's a couple of TODOs in the code referencing this specific issue, but your above direct issue is now closed, so we can close this as well right?... And if so, we can remove the TODO on the test... -enabling the test ... not sure wether the timing is good right now (given that is open right now , which sparked my stumbling upon this issue :))\nWe tried to enable all of them and that caused us a bunch of issues and those had to be reverted: A couple tests were enabled later in: and those seem fine. The remaining (mostly session-affinity ones) had some issue, which so far we didn't have time to debug and I haven't heard a good explanation why those were failing. It's possible that they were improved with , but I doubt those would really cause the failures we've seen in the past. So until this is debugged (or at least understood) I'm reluctant to enabling them.", "commid": "kubernetes_issue_56138", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7ab914479a2e8961f7a53f8b4958ae57d52448c5b0b625e5703995c4af097808", "query": "hostUpdates := make([]func() error, 0, len(ipConfigurationIDs)) nodeUpdates := make(map[vmssMetaInfo]map[string]compute.VirtualMachineScaleSetVM) <del> errors := make([]error, 0) </del> <ins> allErrs := make([]error, 0) </ins> for i := range ipConfigurationIDs { ipConfigurationID := ipConfigurationIDs[i]", "positive_passages": [{"docid": "doc-en-kubernetes-27479256c4cd4a81489a76c239bc26b6dc52b8a0b6a444f52adbe9ce38513013", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --/kind bug /sig cloud-provider /area provider/azure Azure in-tree CCM fails to delete a load balancer: The corresponding logs: The clouprovider config is: The Nodes are actually Azure VMs that belong to a VMO (aka vmss with flexible orchestration mode) - regular VMs and managed independently of the vmss. So those VMs are managed on Azure as . LoadBalancer deletion works with the very same setup with v1.21.1 of the in-tree Azure CCM. After recent cherry-picks, with v1.21.4 we observe the failure above. a cluster using VMs that belong to a VMO a Service of type LoadBalancer the Service of type LoadBalancer sure that the deletion fails with: Kubernetes version (use ): v1.21.4 Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Gardener Network plugin and version (if this is a network-related bug): Others:\n/assign /triage accepted", "commid": "kubernetes_issue_105184", "tokennum": 289}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7abd83bfe44bf943e5544f3172037adf312c4613ac7796cd82c51faa9c573536", "query": "KUBE_ROOT=$(dirname \"${BASH_SOURCE[0]}\")/.. cd \"${KUBE_ROOT}\" <del> mapfile -t all_e2e_files < <(find test/e2e -name '*.go') </del> <ins> # NOTE: This checks e2e test code without the e2e framework which contains Expect().To(HaveOccurred()) mapfile -t all_e2e_files < <(find test/e2e -name '*.go' | grep -v 'test/e2e/framework/') </ins> errors_expect_no_error=() for file in \"${all_e2e_files[@]}\" do", "positive_passages": [{"docid": "doc-en-kubernetes-c082543f1889f90c5ee780d309eeb8f41ee57a7e9e8bb6b6fe7c2e4381ff48af", "text": "What happened: After fixing golint failures under (now still in progress), we need to put for each and . Then common error checking code has become like: We can replace this code with which is more readable and easy to be understood what the code does. Now we have following e2e test directories which can be replaced: [x] test/e2e/apimachinery/ () [x] test/e2e/apps/ () [x] test/e2e/auth/ () [x] test/e2e/common/ () [x] test/e2e/node/ () [x] test/e2e/storage/ () [x] () [x] () [x] () [x] () [x] () [x] () [x] [x] test/e2e/storage/persistentvolumes- [x] () [x] () [x] [x] [x] [x] [x] ()\n/sig testing /kind cleanup\n/assign PR will be submitted soon.\nFix the following in\nFix in\nFix in\nHi, maybe I could take files beneath test/e2e/storage/vsphere/\noops, I'm finished and prepare for PR.\nThank you That's OK\nFix the following in\n/assign\nAll related PRs were merged. I think this ticket can be closed. BTW, should we also replace to ?\nThanks for your work. thing is managed with We are almost finishing the work also :-)\n/remove-kind bug\nI found in these files. I'm working on :\nI can work to the following item.", "commid": "kubernetes_issue_77706", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7ad2a11ca21a4cffb52c55a961faf90e50cce02607ea1750876fa372c789a98a", "query": "t.Errorf(\"Check ipset entries failed for ipset: %q, expect %d, got %d\", set, len(entries), len(ents)) continue } <del> if len(entries) == 1 { if ents[0] != entries[0].String() { t.Errorf(\"Check ipset entries failed for ipset: %q\", set) } </del> <ins> expectedEntries := []string{} for _, entry := range entries { expectedEntries = append(expectedEntries, entry.String()) } sort.Strings(ents) sort.Strings(expectedEntries) if !reflect.DeepEqual(ents, expectedEntries) { t.Errorf(\"Check ipset entries failed for ipset: %q\", set) </ins> } } }", "positive_passages": [{"docid": "doc-en-kubernetes-dd58629e743b6e4eeaad6ce708921acac15734ca4e62ad8f92d2c296b406f940", "text": "What happened: SCTP nodeport service is not working for all IPs present in the node when ipvs is enabled. It is working only for node's InternalIP. What you expected to happen: SCTP nodeport service must work for all ips present in the node when ipvs is enabled. How to reproduce it (as minimally and precisely as possible): Create a kubernetes cluster with at least one node having multiple interfaces with different IPs. Start an SCTP server deployment. Then create a nodeport service for the same. Now try to reach the service using all the IPs present in that node. The service will be accessible only via node's InternalIP not any other IPs. Environment: Kubernetes version: v1.15.2 OS: ubuntu 18.04 Kernel: 4.15.0-54-generic Network plugin and version (if this is a network-related bug): ipset version v6.34\n/sig network /area kube-proxy /area ipvs\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/remove-triage unresolved", "commid": "kubernetes_issue_81474", "tokennum": 251}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7ae0860eccbf97091645c26e577255334e2b875ab1619a58b59e841173da40f9", "query": "} func (mounter *Mounter) IsNotMountPoint(dir string) (bool, error) { <del> return IsNotMountPoint(mounter, dir) </del> <ins> return isNotMountPoint(mounter, dir) </ins> } func (mounter *Mounter) IsLikelyNotMountPoint(file string) (bool, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-4bcfc015d2b9d9fa1e84475a3e08fb9ef8299b4e5f821f790188ad7bdae6ecbc", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: There's , and . The former is used by local and nfs volume plugins, while the latter is used by , which is also used by local and nfs volume plugins. What you expected to happen: Can we consolidate these? This is really confusing and could easily be the source of bugs. <!-- DO NOT EDIT BELOW THIS LINE --/kind cleanup\ncc\n/assign I'd like to clean up code.", "commid": "kubernetes_issue_72387", "tokennum": 133}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7b083e4bd362b07ed8921f80f200df0ff4983d348d70c927f6ad2e33a55c109c", "query": "<ins> load(\"@io_bazel_rules_go//go:def.bzl\", \"go_library\") go_library( name = \"go_default_library\", srcs = [\"fuzzer.go\"], importpath = \"k8s.io/kubernetes/pkg/kubelet/apis/kubeletconfig/fuzzer\", visibility = [\"//visibility:public\"], deps = [ \"//pkg/kubelet/apis/kubeletconfig:go_default_library\", \"//pkg/kubelet/apis/kubeletconfig/v1alpha1:go_default_library\", \"//pkg/kubelet/qos:go_default_library\", \"//pkg/kubelet/types:go_default_library\", \"//pkg/master/ports:go_default_library\", \"//vendor/github.com/google/gofuzz:go_default_library\", \"//vendor/k8s.io/apimachinery/pkg/apis/meta/v1:go_default_library\", \"//vendor/k8s.io/apimachinery/pkg/runtime/serializer:go_default_library\", ], ) filegroup( name = \"package-srcs\", srcs = glob([\"**\"]), tags = [\"automanaged\"], visibility = [\"//visibility:private\"], ) filegroup( name = \"all-srcs\", srcs = [\":package-srcs\"], tags = [\"automanaged\"], visibility = [\"//visibility:public\"], ) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-937f1cb17c20e5fd2b4a1f81201690c3dbe6990ef3c1bc74ff71daaa02b6db56", "text": "Solution: I will add one.\n/cc\nxref\nThanks for sending a PR so quickly!\n[MILESTONENOTIFIER] Milestone Issue Needs Attention Action required: During code slush, issues in the milestone should be in progress. If this issue is not being actively worked on, please remove it from the milestone. If it is being worked on, please add the label so it can be tracked with other in-flight issues. Note: If this issue is not resolved or labeled as by Wed, Nov 22 it will be moved out of the v1.9 milestone. <details<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details", "commid": "kubernetes_issue_55959", "tokennum": 230}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7b0b706bbff80900a09bec18e1ded8a858a18c20b6a141de516ff3c5d6e7a8ef", "query": "Name: \"foo\", }, Data: map[string][]byte{ <del> v1.DockerConfigKey: secretData, </del> <ins> v1.DockerConfigJsonKey: secretData, </ins> }, <del> Type: v1.SecretTypeDockercfg, </del> <ins> Type: v1.SecretTypeDockerConfigJson, </ins> }, expectErr: false, },", "positive_passages": [{"docid": "doc-en-kubernetes-4279a6f285666ec67ce8924ca9393c19176af7de5707dd42a5f4c239ba12ead2", "text": "/kind bug We're having trouble retrieving images from a private registry on DockerCloud. For nearly a year the following has worked flawlessly. Last Friday I pulled down the 1.9.0 CLI (via brew) and since then have not been able to access any image in a private registry on DockerCloud. I've tried this on 10+ brand new clusters created with kops v1.8.0. The Kubernetes cluster version have been 1.8.0, 1.8.4, 1.8.5 and 1.9.0 (which is not supported by kops yet) and all exhibit the same problem. We create the secret as such: And verify it using: Which yields: And create a test service with with these contents: The pod fails immediatly with: I've reviewed the 1.9.0 release notes and nothing jumps out as the root cause. For reference I've tried putting quotes around the value when creating the secret to no avail. I've also tried prefixing the value with , so the full value would read: also to no avail. Environment: Kubernetes version: Cloud provider and installation info: AWS cluster built with Kops 1.8.0, using (to isolate this issue) nearly the default settings for everything.\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI have same problem, and I \"solved\" it creating a docker-registry secret in an old kubernetes version and pasting it on new kubernetes\nI'm recently (I know it worked perfectly about last month) facing issues with as well. For me it ended in a similar manner saying: I was able to confirm, that this is a kubernetes CLI related issue and not end user. Based on and this I was able to create properly formatted auth information looking like this: . When encoding this one-liner using (MacOS workstation) and apply like this works fine and images can be pulled from private repository again.", "commid": "kubernetes_issue_57427", "tokennum": 466}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7b0b706bbff80900a09bec18e1ded8a858a18c20b6a141de516ff3c5d6e7a8ef", "query": "Name: \"foo\", }, Data: map[string][]byte{ <del> v1.DockerConfigKey: secretData, </del> <ins> v1.DockerConfigJsonKey: secretData, </ins> }, <del> Type: v1.SecretTypeDockercfg, </del> <ins> Type: v1.SecretTypeDockerConfigJson, </ins> }, expectErr: false, },", "positive_passages": [{"docid": "doc-en-kubernetes-784638a373a6d25c569537512411337ba05226e31cffa99d23b394dffb534564", "text": "However this breaks all automation and can't be considered as solution Confirmed working with kubectl 1.8.5 and server 1.8.4 (guess 1.7.9 as well)\nlooks like there's an extra \"auths\" element when adding the secret using 1.9 kubectl\nAdded in /assign\nMany thanks for the quick fix on this. Any idea when this might get rolled out? Also, it might be a good idea if this was to the known issue list for v1.9.0. It would have saved us a bunch of time trying to track down the root cause. Just trying to make sure no one else needs to do the same.\nlinking to the \"v1.9.0 known issues\" list\nack, asking Mehdy since he is the patch manager for v1.9 branch. Mehdy, any idea when we can ship 1.9.1 with this fix?\nworkarounds for folks until 1.9.1 is released: if you have a .dockerconfigjson for your private registry already, you can manually specify the type and data key (e.g. ) if you don't have a .dockerconfigjson file already, you can fix up the secret produced by manually: the type from to the data key from to the modified secret with\n1 will be released tomorrow\nI can confirm solution works, thanks so much!\nI am still having issues in 1.9.1. This worked in the 1.8.x branches: results in the following error:\nyou have to remove the gitlab-registry secret before you can apply an update... type is immutable, and the fix in 1.9.1 required changing the type of the secret", "commid": "kubernetes_issue_57427", "tokennum": 370}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7b10299e55d8707ba818ea889ba9c71cf79a004115f22f50d03ec71032faccd3", "query": "/* Release : v1.23 Testname: Pod Lifecycle, prestop https hook <del> Description: When a pre-stop handler is specified in the container lifecycle using a 'HttpGet' action, then the handler MUST be invoked before the container is terminated. A server pod is created that will serve https requests, create a second pod with a container lifecycle specifying a pre-stop that invokes the server pod to validate that the pre-stop is executed. </del> <ins> Description: When a pre-stop handler is specified in the container lifecycle using a 'HttpGet' action, then the handler MUST be invoked before the container is terminated. A server pod is created that will serve https requests, create a second pod on the same node with a container lifecycle specifying a pre-stop that invokes the server pod to validate that the pre-stop is executed. </ins> */ ginkgo.It(\"should execute prestop https hook properly [MinimumKubeletVersion:1.23] [NodeConformance]\", func() { lifecycle := &v1.Lifecycle{", "positive_passages": [{"docid": "doc-en-kubernetes-52b8d78c627cb5787b11bea8197d2293333b64736fbbbb287954cc79911301a5", "text": "release-master-informing: capz-windows-containerd-masterKubernetes e2e suite: [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop https hook properly [MinimumKubeletVersion:1.23] [NodeConformance] Kubernetes e2e suite: [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart https hook properly [MinimumKubeletVersion:1.23] [NodeConformance] Both the tests have been failing during most of the runs since 20th October Kubernetes e2e suite: [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop https hook properly [MinimumKubeletVersion:1.23] [NodeConformance] | 1m6s -- | -- {Oct 31 18:42:02.425: Timed out after 30.001s. Expected <errors.errorString | 0xc0015283b0: { s: \"failed to match regexp \"GET /echo?msg=prestop\" in output \"I1031 18:41:06. 8988 ] Started HTTP server on port 9090nI1031 18:41:06. 8988 ] Started UDP server on port 9091n\"\", } to be nil failed (0xc000f1d000) +0x469 () +0x335} Kubernetes e2e suite: [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart https hook properly [MinimumKubeletVersion:1.23] [NodeConformance] | 5m11s -- | -- {Oct 31 19:05:50.205: timed out while waiting for pod container-lifecycle-hook-6892/pod-with-poststart-https-hook to be running and ready failed (PodClient).CreateSync(0xc000eb5920, 0x22?) +0x94 (0xc0045e8c00) +0x73 () +0x325} No response_ /sig windows cc\n/triage accepted /cc\nThese failures happen also with Kubernetes master + containerd master with Flannel CNI. Testgrid link:\nI figured out why these new failures appear.", "commid": "kubernetes_issue_113479", "tokennum": 564}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7b10299e55d8707ba818ea889ba9c71cf79a004115f22f50d03ec71032faccd3", "query": "/* Release : v1.23 Testname: Pod Lifecycle, prestop https hook <del> Description: When a pre-stop handler is specified in the container lifecycle using a 'HttpGet' action, then the handler MUST be invoked before the container is terminated. A server pod is created that will serve https requests, create a second pod with a container lifecycle specifying a pre-stop that invokes the server pod to validate that the pre-stop is executed. </del> <ins> Description: When a pre-stop handler is specified in the container lifecycle using a 'HttpGet' action, then the handler MUST be invoked before the container is terminated. A server pod is created that will serve https requests, create a second pod on the same node with a container lifecycle specifying a pre-stop that invokes the server pod to validate that the pre-stop is executed. </ins> */ ginkgo.It(\"should execute prestop https hook properly [MinimumKubeletVersion:1.23] [NodeConformance]\", func() { lifecycle := &v1.Lifecycle{", "positive_passages": [{"docid": "doc-en-kubernetes-468407671b0c3bb4dc0cf6c503c02539c6d31cfb69250c40c5c81f059af779f1", "text": "I've submitted the fix via PR\nThis issue is also affecting 1.25 tests: If possible, we should cherry-pick to the release-1.25 branch once it's merged on master.", "commid": "kubernetes_issue_113479", "tokennum": 42}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7b18bab35e421acf1a8a6b1648d1e48f3ed68db49fa302b28e91cd8be214b4c1", "query": "return } <ins> func getProxyEnvVars() []api.EnvVar { envs := []api.EnvVar{} for _, env := range os.Environ() { pos := strings.Index(env, \"=\") if pos == -1 { // malformed environment variable, skip it. continue } name := env[:pos] value := env[pos+1:] if strings.HasSuffix(strings.ToLower(name), \"_proxy\") && value != \"\" { envVar := api.EnvVar{Name: name, Value: value} envs = append(envs, envVar) } } return envs } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-dc3be6ce7b42d453edf0753a2cf7546d061a63c2e475384cc9c94a48a05e7f4a", "text": "Is this a request for help? No What keywords did you search in Kubernetes issues before filing this one? http proxy, httpproxy, httpsproxy, AWS, kubeadm, kubectl, cloud-provider Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT Kubernetes version (use ): v1.4.4 Environment: Cloud provider or hardware configuration: kubeadm on EC2 instances on AWS OS (e.g. from /etc/os-release): Ubuntu 16.04.1 LTS Kernel (e.g. ): Linux ip-10-0-133-99 4.4.0-45-generic -Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x8664 x8664 x8664 GNU/Linux Install tools: kubeadm Others: httpproxy, httpsproxy and noproxy set in /etc/environment, Docker config as well on startup scripts that run What happened: won't complete and gets stuck on it's first deployment. When one looks through the logs it shows that the pods are downloading fine but we are stuck due to the kube-controller-manager continually crashing as it can't contact AWS. Elsewhere in kubernetes I see references to and if the AWS cloud provider could use that it would be able to connect as well. From the POD if I manually set httpproxy and httpsproxy and no_proxy I am able to use the AWS CLI without any issues. What you expected to happen: I would expect to successfully complete and use the environment proxies set up on the system so as not to depend on a default Internet Gateway being connected to the VPC just for AWS access. How to reproduce it (as minimally and precisely as possible): Set up a public VPC with Squid set up as a proxy Set up a private VPC peered to the public VPC Set up a master node and run Set up a regular node and run will never fully initialize. If you remove the --cloud-provider aws` then it will complete and nodes will register. Anything else do we need to know:\nwhat do you have in proxy variables ? (env | grep -i proxy) it tries to connect to (tcp 176.32.118.53:443) directly. You're expecting to connect there via proxy ? then do you have something like in your no_proxy ?", "commid": "kubernetes_issue_36573", "tokennum": 535}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7b18bab35e421acf1a8a6b1648d1e48f3ed68db49fa302b28e91cd8be214b4c1", "query": "return } <ins> func getProxyEnvVars() []api.EnvVar { envs := []api.EnvVar{} for _, env := range os.Environ() { pos := strings.Index(env, \"=\") if pos == -1 { // malformed environment variable, skip it. continue } name := env[:pos] value := env[pos+1:] if strings.HasSuffix(strings.ToLower(name), \"_proxy\") && value != \"\" { envVar := api.EnvVar{Name: name, Value: value} envs = append(envs, envVar) } } return envs } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-984a2b369276e3156e0990106838472387b6975b0768d694bc54d8f6e19402d4", "text": "Unfortunately on the pod itself for the the environment variables aren't passed through. As this is created using I don't have control over the pod definition. So basically none of the *_proxy variables are set inside the pod in the docker image, however if I and export the variables and try to wget that URL it works. Basically I'm hoping we can update to respect and pass the environment variables down to the system pods if they exist, eg, add: Without it I can't stand up a cluster with AWS integration on a completely private VPC and for such a small change it would make a rather big difference.\nok, so request is actually to pass proxy variables into containers. interesting. I'll check how it can be done. BTW, for noproxy value in your example: things like 10.0.0.0/8 would not work on 99% of software that respects noproxy variable. it must be always exact IP match.\nyou're right that what I'm actually asking for is to pass proxy variables through either from a commandline setting on kubeadm or pick it up from /etc/environment or shell environment that launches kubeadm. I didn't realize it till I dug in to try and think about how one might go about fixing this. At first I thought we would just pick up the variables from the system environment but then I realized kube-controller-manager is deployed in a container and so we'd need to update the yaml file that launches it to contain the environment variables. As I'd like to go to production with this soon hopefully this is a small change that can be .\nThis issue was moved to kubernetes/kubeadm", "commid": "kubernetes_issue_36573", "tokennum": 362}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7b2fe8f34a4abcf7473564fc5faee17287a950dd625a9d750d69f518bfbe06cf", "query": "} newNodes, err := e2enode.CheckReady(c, len(origNodes.Items)-1, 5*time.Minute) <del> framework.ExpectEqual(err, nil) </del> <ins> framework.ExpectNoError(err) </ins> framework.ExpectEqual(len(newNodes), len(origNodes.Items)-1) _, err = c.CoreV1().Nodes().Get(nodeToDelete.Name, metav1.GetOptions{})", "positive_passages": [{"docid": "doc-en-kubernetes-4d7af6d1d5d1ba0c7ab59da9ea13925b54c282d46d48402ebb3f5409fd2b1204", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: kubernetes/node-problem-detector/node-problem-detector-ci: ci-npd-e2e-node See the Which test(s) are failing: [] NodeProblemDetector [NodeFeature:NodeProblemDetector] [] SystemLogMonitor should generate node condition and events for corresponding errors Since when has it been failing: Dec 03. was at 19:50 PST, was at 21:51 PST. Testgrid link: https://k8s- Reason for failure: Apparently is the culprit. Anything else we need to know: This is likely caused by some library upgrade. Nothing big.\n/sig node\n/assign\nSeems like the failure is caused by . /cc /cc /cc /cc\n/priority critical-urgent\nThe particular bug I care about has been fixed in . I'm gonna still work on submitting , as the same error should also be affecting a few other tests.", "commid": "kubernetes_issue_85933", "tokennum": 235}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7b55276867dc9c84d53653062fab33bb2026f0ff9aba7d4d39a92a5a7c49dc74", "query": "//  * Multiple consumers and producers. In particular, it is allowed for an //      item to be reenqueued while it is being processed. //  * Shutdown notifications. <del> package workqueue </del> <ins> package workqueue // import \"k8s.io/client-go/util/workqueue\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-460ceb7b52a1ab0cadc1b29d7eee5cc1013b8d23be9bca0d145119ffcf7b27c6", "text": "Look at one of the directories under (Please don't pick more than one directory for one PR as it will cause issues for reviewers) Find all the files named (example find -name ) See the following link it has a this tells tools how this package needs to be imported. So we should ensure that each has an import Add a description appropriate to the package (similar to the one below) Look through sub directories and see if there are any other important directories that are likely to be used by outside users and add a Why are we doing this? We perfer to use vanity urls instead of directly using to refer to code, so this helps ensure that tools honor our wish. See It would be good to have some package level documentation since these directories under staging/ are meant to be for use by folks outside of kubernetes github org. /good-first-issue\n/kind documentation /sig architecture\ncurrently working my through Not going to use / assign since there could be a number of PRs for this issue.\n/lifecycle active /good-first-issue edit: hmm..\nThis request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /lifecycle active /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\nMay I try on\nIIUC this means that there needs to be a even at the root of the repo? Then how does work? :thinking:\nHi , can I make a PR for this directory ?\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_68231", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7b55276867dc9c84d53653062fab33bb2026f0ff9aba7d4d39a92a5a7c49dc74", "query": "//  * Multiple consumers and producers. In particular, it is allowed for an //      item to be reenqueued while it is being processed. //  * Shutdown notifications. <del> package workqueue </del> <ins> package workqueue // import \"k8s.io/client-go/util/workqueue\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-5f31f1c27d7198dc83b313154ff681043a8b41e17eb5d3ddf32cd84bc023f931", "text": "/lifecycle rotten\nI guess this is still not done, was supposed to partially fix this issue. /reopen\nReopened this issue. <detailsIn response to : I guess this is still not done, was supposed to partially fix this 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\n/remove-lifecycle rotten /area code-organization", "commid": "kubernetes_issue_68231", "tokennum": 93}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7b698a9c158ddc9ebc3f49571212854332a2a9c61df827c739112793f91ce7f5", "query": "failedGVs := map[schema.GroupVersion]error{} var resourcesByGV map[schema.GroupVersion]*metav1.APIResourceList // Switch on content-type server responded with: aggregated or unaggregated. <del> switch responseContentType { case AcceptV1: err = json.Unmarshal(body, apiGroupList) if err != nil { return nil, nil, nil, err } case AcceptV2Beta1: </del> <ins> switch { case isV2Beta1ContentType(responseContentType): </ins> var aggregatedDiscovery apidiscovery.APIGroupDiscoveryList err = json.Unmarshal(body, &aggregatedDiscovery) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-3257ecff81fbc60fa2a8f982346c462089eb7c896f62cce1d4e02ff6df66d913", "text": "We are using (and ) to interact with Kubernetes clusters behind a couple of proxy layers. One of these proxies completes the headers to include character encoding details. This was working fine until recently, when client-go/kubectl have started to fail when interacting with the discovery API. It seems that a recent change has made kubectl more restrictive of the content-type that it expects. I suspect that it is related to this commit: For example, this is an error from a kubectl command: We can of course try to fix it on our end, removing that charset information. However, it is a valid content-type and the way kubectl is handling the content-type there seems like it is relying on implementation details of kube-apiserver (that it does not add metadata to the content-type). I propose to fix this issue in , by properly parsing and handling the content-type.\ncc /kind regression /kind bug /sig api-machinery /priority important-soon looks like the switch statement in downloadLegacy() needs to be more tolerant of the variety of content-types it can get from a server (including text/plain or no content-type if old servers could have returned that...)\n/transfer kubernetes/kubernetes\nSomething went wrong or the destination repo kubernetes/kubernetes/kubernetes does not exist. <detailsIn response to : /transfer kubernetes/kubernetes 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\n/transfer kubernetes\nYep, the string comparison for the content-type is flimsy, let's address that. Thanks for the report!\n/assign\n/triage accepted\n/cc\nThe fix is being cherry-picked back to: : :", "commid": "kubernetes_issue_117562", "tokennum": 408}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7b9ec9286bba734cea6e6da7f304401d65fd6d12d01a50164a1b3788e2217d7f", "query": "Reason: startWaitingReason, }}, }, <del> map[string]api.ContainerState{ </del> <ins> expectedInitState: map[string]api.ContainerState{ \"without-old-record\": {Waiting: &api.ContainerStateWaiting{ Reason: initWaitingReason, }}, \"with-old-record\": {Waiting: &api.ContainerStateWaiting{ Reason: initWaitingReason, }}, }, expectedLastTerminationState: map[string]api.ContainerState{ </ins> \"with-old-record\": {Terminated: &api.ContainerStateTerminated{}}, }, }, // For running container, State should be Running, LastTerminationState should be retrieved from latest terminated status. { <del> []api.Container{{Name: \"running\"}}, []*kubecontainer.ContainerStatus{ </del> <ins> containers: []api.Container{{Name: \"running\"}}, statuses: []*kubecontainer.ContainerStatus{ </ins> { Name:      \"running\", State:     kubecontainer.ContainerStateRunning,", "positive_passages": [{"docid": "doc-en-kubernetes-b4459e221a04f6723f7b97c6a9d43d61c0d65417b08d143223c7057699636055", "text": "is this a Node bug? cc as next oncall to follow up on this.\nThis is a node bug due to init containers\nI may need help debugging - I see:\nSo I think the problem is in the error case - we're not properly recording that the start failed, and the next time we come in we somehow think the first container succeeded. I'll add some debugging to see if we can't recreate it.\nLet's discuss on instead.", "commid": "kubernetes_issue_25879", "tokennum": 102}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7b9ec9286bba734cea6e6da7f304401d65fd6d12d01a50164a1b3788e2217d7f", "query": "Reason: startWaitingReason, }}, }, <del> map[string]api.ContainerState{ </del> <ins> expectedInitState: map[string]api.ContainerState{ \"without-old-record\": {Waiting: &api.ContainerStateWaiting{ Reason: initWaitingReason, }}, \"with-old-record\": {Waiting: &api.ContainerStateWaiting{ Reason: initWaitingReason, }}, }, expectedLastTerminationState: map[string]api.ContainerState{ </ins> \"with-old-record\": {Terminated: &api.ContainerStateTerminated{}}, }, }, // For running container, State should be Running, LastTerminationState should be retrieved from latest terminated status. { <del> []api.Container{{Name: \"running\"}}, []*kubecontainer.ContainerStatus{ </del> <ins> containers: []api.Container{{Name: \"running\"}}, statuses: []*kubecontainer.ContainerStatus{ </ins> { Name:      \"running\", State:     kubecontainer.ContainerStateRunning,", "positive_passages": [{"docid": "doc-en-kubernetes-dcc88d1d89328d1da3366de828afcd8ab0373228cc4437ea655e2cda79030f86", "text": "Kubelet issues a docker inspect call after creating a container, but for very short lived containers there is a window in which they could exit before being inspected in the docker manager. If the container PID is 0, we should check the ExitCode and other relevant fields and handle them appropriately. [1] This is the suspected cause of several flakes: /cc\nlooking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: I'd expect the second one to not have run in this case? Node logs:\nInit containers have an implicit assumption that container statuses include results of previous SyncPod invocations. If that's not the case we may need to fix that (or at least mitigate it). On May 18, 2016, at 8:28 PM, Prashanth B wrote: looking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: May 18 15:58:33.380: INFO: pod-init--1d4b-11e6-80a4- started at 2016-05-18T15:58:04-07:00 (2+1 container statuses recorded) May 18 15:58:33.380: INFO: Init container init1 ready: false, restart count 0 May 18 15:58:33.380: INFO: Init container init2 ready: true, restart count 0 I'd expect the second one to not have run in this case? Node logs: \u2014 You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub\nThis should be true. Is there any evidence that suggests the opposite? only shows conflicting view of whether init1 has run.\nIf the container exits already and it's not an infra container, kubelet should not error out. Although even if it does, I failed to see how this could affect the readiness of the init container without checking the code further.", "commid": "kubernetes_issue_25844", "tokennum": 487}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7b9ec9286bba734cea6e6da7f304401d65fd6d12d01a50164a1b3788e2217d7f", "query": "Reason: startWaitingReason, }}, }, <del> map[string]api.ContainerState{ </del> <ins> expectedInitState: map[string]api.ContainerState{ \"without-old-record\": {Waiting: &api.ContainerStateWaiting{ Reason: initWaitingReason, }}, \"with-old-record\": {Waiting: &api.ContainerStateWaiting{ Reason: initWaitingReason, }}, }, expectedLastTerminationState: map[string]api.ContainerState{ </ins> \"with-old-record\": {Terminated: &api.ContainerStateTerminated{}}, }, }, // For running container, State should be Running, LastTerminationState should be retrieved from latest terminated status. { <del> []api.Container{{Name: \"running\"}}, []*kubecontainer.ContainerStatus{ </del> <ins> containers: []api.Container{{Name: \"running\"}}, statuses: []*kubecontainer.ContainerStatus{ </ins> { Name:      \"running\", State:     kubecontainer.ContainerStateRunning,", "positive_passages": [{"docid": "doc-en-kubernetes-ade5deee53831749acf4a20dbe39f9ef1836656ae43e40b0bb8594efa4e81e92", "text": "Each syncPod invocation, we inspect the list of init container in order looking for lastTerminationState. There could be a bug in that logic, or if we didn't get the full status, we might make a bad decision. When determining which container to run next, we always look for the last init container in the chain that has success, then run the next container (unless the pod is RestartNever). , Yu-Ju Hong wrote:\nSaw this flake again. How do we verify that container status is not lost between syn pods?\n... between calls to syncPods\nThe second sync clearly saw the init1 container, and decided to launch init2. See \"InitContainersToKeep\" in the message below.\ncontainers to keep can include failed containers. , Yu-Ju Hong wrote:\nDiscussed on slack. In summary, the problem has to do with how we convert the kubecontainer.PodStatus to the api.PodStatus. If a container is terminated, the function makes the decisions: the pod restart policy is \"Always\", and there is a \"failure reason\" recorded for the given container, this means the pod worker tried to (re)start the container but failed. Set the state to \"Waiting\" and populate the reason. , the container state is simply \"terminated\". Init containers don't obey the restart policy like regular containers, and the logic will need to be amended to work with them. is working on a PR. In addition to that, kubelet should not error out if a user container exited before it could apply the oom score (which is best effort in this case). fixes that.\nAhh, thanks for digging into the issue. This is the exact the concern I had when I reviewed the initial implementation of init container, which blocks pr for a while. I even asked to help me verify this case, unfortunately we didn't reproduce the issue back then. :-(\nI wish I'd seen the flakes in the runs prior to merge.\nWe didn't notice this until we started running the tests against docker v1.11.1, which is much faster and hit the race condition differently.\nI suppose that's a good thing...\nIt is hard to reproduce this.", "commid": "kubernetes_issue_25844", "tokennum": 482}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7b9ec9286bba734cea6e6da7f304401d65fd6d12d01a50164a1b3788e2217d7f", "query": "Reason: startWaitingReason, }}, }, <del> map[string]api.ContainerState{ </del> <ins> expectedInitState: map[string]api.ContainerState{ \"without-old-record\": {Waiting: &api.ContainerStateWaiting{ Reason: initWaitingReason, }}, \"with-old-record\": {Waiting: &api.ContainerStateWaiting{ Reason: initWaitingReason, }}, }, expectedLastTerminationState: map[string]api.ContainerState{ </ins> \"with-old-record\": {Terminated: &api.ContainerStateTerminated{}}, }, }, // For running container, State should be Running, LastTerminationState should be retrieved from latest terminated status. { <del> []api.Container{{Name: \"running\"}}, []*kubecontainer.ContainerStatus{ </del> <ins> containers: []api.Container{{Name: \"running\"}}, statuses: []*kubecontainer.ContainerStatus{ </ins> { Name:      \"running\", State:     kubecontainer.ContainerStateRunning,", "positive_passages": [{"docid": "doc-en-kubernetes-0814a4e75b48cf2d27d20141c180e04fbc9b55d5398cce31b037f460c93acb1b", "text": "The extra check of last terminated container in your initial code makes me nervous, but we couldn't reproduce it due to that small race windows until we have a faster docker running on the node. :-)\nI got \"Pods should invoke init containers on a RestartAlways pod\" flake (referenced from ): Logs:\nAll the fixes went in. Please reopen this issue if you see any more flakes.", "commid": "kubernetes_issue_25844", "tokennum": 90}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7b9f304dc3ce92447646beaaddac687823a796430ef24a41f0d464d894e0e811", "query": "framework.ExpectNoError(waitErr, \"some pods failed to complete within %v\", completeTimeout) }) }) <del> ginkgo.Context(\"Pods sharing a single local PV [Serial]\", func() { var ( pv *v1.PersistentVolume ) ginkgo.BeforeEach(func(ctx context.Context) { localVolume := &localTestVolume{ ltr: &utils.LocalTestResource{ Node: config.randomNode, Path: \"/tmp\", }, localVolumeType: DirectoryLocalVolumeType, } pvConfig := makeLocalPVConfig(config, localVolume) var err error pv, err = e2epv.CreatePV(ctx, config.client, f.Timeouts, e2epv.MakePersistentVolume(pvConfig)) framework.ExpectNoError(err) }) ginkgo.AfterEach(func(ctx context.Context) { if pv == nil { return } ginkgo.By(fmt.Sprintf(\"Clean PV %s\", pv.Name)) err := config.client.CoreV1().PersistentVolumes().Delete(ctx, pv.Name, metav1.DeleteOptions{}) framework.ExpectNoError(err) }) ginkgo.It(\"all pods should be running\", func(ctx context.Context) { var ( pvc   *v1.PersistentVolumeClaim pods  = map[string]*v1.Pod{} count = 2 err   error ) pvc = e2epv.MakePersistentVolumeClaim(makeLocalPVCConfig(config, DirectoryLocalVolumeType), config.ns) ginkgo.By(fmt.Sprintf(\"Create a PVC %s\", pvc.Name)) pvc, err = e2epv.CreatePVC(ctx, config.client, config.ns, pvc) framework.ExpectNoError(err) ginkgo.By(fmt.Sprintf(\"Create %d pods to use this PVC\", count)) podConfig := e2epod.Config{ NS:           config.ns, PVCs:         []*v1.PersistentVolumeClaim{pvc}, SeLinuxLabel: selinuxLabel, } for i := 0; i < count; i++ { pod, err := e2epod.MakeSecPod(&podConfig) framework.ExpectNoError(err) pod, err = config.client.CoreV1().Pods(config.ns).Create(ctx, pod, metav1.CreateOptions{}) framework.ExpectNoError(err) pods[pod.Name] = pod } ginkgo.By(\"Wait for all pods are running\") const runningTimeout = 5 * time.Minute waitErr := wait.PollImmediate(time.Second, runningTimeout, func() (done bool, err error) { podsList, err := config.client.CoreV1().Pods(config.ns).List(ctx, metav1.ListOptions{}) if err != nil { return false, err } runningPods := 0 for _, pod := range podsList.Items { switch pod.Status.Phase { case v1.PodRunning: runningPods++ } } return runningPods == count, nil }) framework.ExpectNoError(waitErr, \"Some pods are not running within %v\", runningTimeout) }) }) </del> }) func deletePodAndPVCs(ctx context.Context, config *localTestConfig, pod *v1.Pod) error {", "positive_passages": [{"docid": "doc-en-kubernetes-d2ad17ee33cbb9dd0cc3cd8888bfcb21e558f50039e64e1a5ba0cdc518d0afba", "text": "During OPNFV test execution we noticed the folder selinux context changed. e2e test log How the folder changed after the test executed. I expected the TC won't change the selinux context. The question here, should this sigstorageserial TC set work on an selinux enabled K8S cluster or not? This question valid for the another sigstorage TC set with several test case, where selinux block a lot of TC too. See above. No response_ <details</details<detailsOpenStack </details<details</details<details</details<details</details<details</details\n/sig testing\n/sig storage\nThe Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues 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 as fresh with Close this issue with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:\n/remove-lifecycle stale\n/assign\nReproducer with simple kubernetes/kubernetes artifacts:\n/triage accepted", "commid": "kubernetes_issue_116764", "tokennum": 291}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7baf1c17367e9fc1f5b8b9cae3062448b893f8a46ffe445d4dc3735b17a284d4", "query": "ds:            newDaemonSet(\"ds\"), shouldEnqueue: true, }, <ins> { test:    \"Node Allocatable changed\", oldNode: newNode(\"node1\", nil), newNode: func() *v1.Node { node := newNode(\"node1\", nil) node.Status.Allocatable = allocatableResources(\"200M\", \"200m\") return node }(), ds: func() *apps.DaemonSet { ds := newDaemonSet(\"ds\") ds.Spec.Template.Spec = resourcePodSpecWithoutNodeName(\"200M\", \"200m\") return ds }(), expectedEventsFunc: func(strategyType apps.DaemonSetUpdateStrategyType) int { switch strategyType { case apps.OnDeleteDaemonSetStrategyType: return 2 case apps.RollingUpdateDaemonSetStrategyType: return 3 default: t.Fatalf(\"unexpected UpdateStrategy %+v\", strategyType) } return 0 }, shouldEnqueue: true, }, </ins> } for _, c := range cases { for _, strategy := range updateStrategies() {", "positive_passages": [{"docid": "doc-en-kubernetes-56dc15a3fe2161c6cf8927a51d2d0dce03fea80f01ef1e0345dcc3ca50d1379f", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: a cluster, And node1 with resource 1 DaemonSet, request resource 4 run , There is no pod created. resource to the node: run , There is still no pod created. What you expected to happen: In step 5, There is one pod created. How to reproduce it (as minimally and precisely as possible): see above description Anything else we need to know?: Environment: Kubernetes version (use ):1.10.5 Cloud provider or hardware configuration: OS (e.g. from /etc/os-release):CentOS7 Kernel (e.g. ): Install tools: Others: /sig app\nxref\nThanks! is not work here! Because: DaemonSetsController didn't watch the changes.(we use to updateNode.) we restart kubelet, The DaemonSetsController watch the changes, but it seems that the node info is not updated, and still failed to create pod:\nI found it is a bug here, ignore the changes. I made a fix , PTAL! Thanks!\nAny workarounds for old cluster versions? Up: looks like in my case helped but after some delay.\n, which version of k8s are you using? If it's sunset, you have to merge the pr yourself :). I think restart kubelet trigger delete/add to make sure it sync .\nSorry, I didn't say\nI think we still support 1.12 for now :) let's cherry pick it if not and wait for next 1.12 release.", "commid": "kubernetes_issue_67225", "tokennum": 342}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7bc1c87a0e7a9481ba4263b6b220a30a84d96aa446dc3b30c8eb09ab7e8ec5da", "query": "\"//pkg/api/unversioned:go_default_library\", \"//pkg/client/cache:go_default_library\", \"//pkg/client/clientset_generated/internalclientset:go_default_library\", <ins> \"//pkg/kubelet:go_default_library\", </ins> \"//pkg/kubelet/api/v1alpha1/stats:go_default_library\", \"//pkg/kubelet/cm:go_default_library\", <ins> \"//pkg/kubelet/container:go_default_library\", </ins> \"//pkg/kubelet/dockertools:go_default_library\", \"//pkg/kubelet/images:go_default_library\", \"//pkg/kubelet/metrics:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-0ad427ca9c00c618017f4be9fb19a1df6f4ab39ddc68f128fc109eb4d0409cbf", "text": "Cluster logging assumes kubelet stores container log at a specific directory with specific name. Currently the path is: After the CRI work, the path will be: However, we don't have test coverage for this. We don't even know whether the log files are there or not. We should add a node e2e test for this, basically: 1) Create a container which prints logs 2) Check whether the expected log file is created. 3) Check whether the logs are collected in the file as expected. And it would be better to launch a pod to do the check instead of accessing local file system directly, which makes containerizing easier. /cc because you are collecting missing test. /cc\nI will try to add a node-e2e test there\nI think it's ok to add this for CRI. But there maybe problems on today's interface for rkt. If I'm not wrong, rkt does't store logs at same location with docker. cc/ Is this true?\nThanks! :)\nAfter gets merged, we need to update the test to verify the cri log path.", "commid": "kubernetes_issue_34661", "tokennum": 234}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7be339b7d4909df1af51600658fca8bbbcd771380f847dabbc2a57834b823252", "query": "return nil, fmt.Errorf(\"failed to run in container - Exec setup failed - %v\", err) } var buf bytes.Buffer <del> wrBuf := bufio.NewWriter(&buf) </del> startOpts := docker.StartExecOptions{ Detach:       false, Tty:          false, <del> OutputStream: wrBuf, ErrorStream:  wrBuf, </del> <ins> OutputStream: &buf, ErrorStream:  &buf, </ins> RawTerminal:  false, } <del> errChan := make(chan error, 1) go func() { errChan <- dm.client.StartExec(execObj.ID, startOpts) }() wrBuf.Flush() return buf.Bytes(), <-errChan </del> <ins> err = dm.client.StartExec(execObj.ID, startOpts) return buf.Bytes(), err </ins> } // ExecInContainer uses nsenter to run the command inside the container identified by containerID.", "positive_passages": [{"docid": "doc-en-kubernetes-65bf469670180d69e57fdc1a820a8f2f435cec685a9975e90f226dd126851fba", "text": "As far as I can tell, container liveness probes of type exec flat out don't work against clusters built at head. I had the kubelet always log the output of the exec'ed command, and it's always empty no matter what I exec, causing the probe to fail since it requires the output to be equal to the string \"ok\". If you want to test it, try adding a liveness probe of this form to any container: I also tried these lovely forms, to more closely match the liveness example under examples/: On the plus side, this may be an opportunistic time to switch over to\nThe reason that the e2e test for exec liveness probes hasn't caught this is that it only tests that containers are restarted when they fail liveness probes. It doesn't test that containers aren't restarted when their liveness checks should be succeeding. The e2e test's exec'ed commands also only ever produced empty output, rather than the expected \"fail\" output.\nIs it possible to include this in a new pre-release, since it fixes a bug in health checking? I see it merged in master and I'm wondering what the policy is of releasing new code in a separate (0.16.*) release.", "commid": "kubernetes_issue_7618", "tokennum": 275}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7be4258d6cc49fe84d8c03dac26a7a2370bd5abd88fa6662673d60fdaa10bec5", "query": "\"testing\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" <ins> \"k8s.io/apimachinery/pkg/util/validation/field\" </ins> \"k8s.io/kubernetes/federation/apis/federation\" \"k8s.io/kubernetes/pkg/api\" ) <ins> func TestValidateClusterSpec(t *testing.T) { type validateClusterSpecTest struct { testName string spec     *federation.ClusterSpec path     *field.Path } successCases := []validateClusterSpecTest{ { testName: \"normal CIDR\", spec: &federation.ClusterSpec{ ServerAddressByClientCIDRs: []federation.ServerAddressByClientCIDR{ { ClientCIDR:    \"0.0.0.0/0\", ServerAddress: \"localhost:8888\", }, }, }, path: field.NewPath(\"spec\"), }, { testName: \"missing CIDR\", spec: &federation.ClusterSpec{ ServerAddressByClientCIDRs: []federation.ServerAddressByClientCIDR{ { ClientCIDR:    \"\", ServerAddress: \"localhost:8888\", }, }, }, path: field.NewPath(\"spec\"), }, { testName: \"no host in CIDR\", spec: &federation.ClusterSpec{ ServerAddressByClientCIDRs: []federation.ServerAddressByClientCIDR{ { ClientCIDR:    \"0.0.0.0/32\", ServerAddress: \"localhost:8888\", }, }, }, path: field.NewPath(\"spec\"), }, } for _, successCase := range successCases { errs := ValidateClusterSpec(successCase.spec, successCase.path) if len(errs) != 0 { t.Errorf(\"expect success for testname: %q  but got: %v\", successCase.testName, errs) } } errorCases := []validateClusterSpecTest{ { testName: \"invalid CIDR : network missing\", spec: &federation.ClusterSpec{ ServerAddressByClientCIDRs: []federation.ServerAddressByClientCIDR{ { ClientCIDR:    \"0.0.0.0\", ServerAddress: \"localhost:8888\", }, }, }, path: field.NewPath(\"spec\"), }, { testName: \"invalid CIDR : invalid address value\", spec: &federation.ClusterSpec{ ServerAddressByClientCIDRs: []federation.ServerAddressByClientCIDR{ { ClientCIDR:    \"256.0.0.0/16\", ServerAddress: \"localhost:8888\", }, }, }, path: field.NewPath(\"spec\"), }, { testName: \"invalid CIDR : invalid address formation\", spec: &federation.ClusterSpec{ ServerAddressByClientCIDRs: []federation.ServerAddressByClientCIDR{ { ClientCIDR:    \"0.0.0/16\", ServerAddress: \"localhost:8888\", }, }, }, path: field.NewPath(\"spec\"), }, { testName: \"invalid CIDR : invalid network num\", spec: &federation.ClusterSpec{ ServerAddressByClientCIDRs: []federation.ServerAddressByClientCIDR{ { ClientCIDR:    \"0.0.0.0/33\", ServerAddress: \"localhost:8888\", }, }, }, path: field.NewPath(\"spec\"), }, } for _, errorCase := range errorCases { errs := ValidateClusterSpec(errorCase.spec, errorCase.path) if len(errs) == 0 { t.Errorf(\"expect failure for testname : %q\", errorCase.testName) } } } </ins> func TestValidateCluster(t *testing.T) { successCases := []federation.Cluster{ {", "positive_passages": [{"docid": "doc-en-kubernetes-9ef34f91f24cf25c8ee57899ba28766272335d7f286e3495efa44b9480fef2d3", "text": "Right now it is possible to add a cluster for which it won't be possible to create a client. For example client-related code does: while validation checks only: cc:\nswitching this to 1.6 as it's too late for 1.5. ok? (please switch it right back if you disagree)\nNot a release blocker for 1.7.\nare you interested in fixing this?\nof course, will do that.\n[MILESTONENOTIFIER] Milestone Removed Important: This issue was missing labels required for the v1.8 milestone for more than 7 days: kind: Must specify exactly one of [, , ]. priority: Must specify exactly one of [, , ]. Removing it from the milestone. <detailsAdditional instructions available <a href=\"\"here</aThe commands available for adding these labels are documented <a href=\"\"here</a</details", "commid": "kubernetes_issue_29911", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7c15bc19500faac6133ec5038e9b47ff7d6b03c9d859f68bc62b369849e3795d", "query": "result := int32(0) for i := range pods { po := pods[i] <del> if po.Status.Phase != v1.PodRunning { continue } for j := range po.Status.InitContainerStatuses { stat := po.Status.InitContainerStatuses[j] result += stat.RestartCount } for j := range po.Status.ContainerStatuses { stat := po.Status.ContainerStatuses[j] result += stat.RestartCount </del> <ins> if po.Status.Phase == v1.PodRunning || po.Status.Phase == v1.PodPending { for j := range po.Status.InitContainerStatuses { stat := po.Status.InitContainerStatuses[j] result += stat.RestartCount } for j := range po.Status.ContainerStatuses { stat := po.Status.ContainerStatuses[j] result += stat.RestartCount } </ins> } } if *job.Spec.BackoffLimit == 0 {", "positive_passages": [{"docid": "doc-en-kubernetes-57b8eab4723f670b6603d9bfb82377ab99cdb5a96c17a18501cc8d4284272435", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: I create a job with initcontainer with restartPolicy : when the initContainer exec failed and it will be restarted, the pod Phase will be pending all the time. but in JobController, the only care the running pod. So this pod will be always restarted. What you expected to happen: when restart count to backoffLimit, the job failed. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig apps\n/assign", "commid": "kubernetes_issue_77644", "tokennum": 220}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7c3a4d00d3ccce5fca869044821b604840a0bbe3e9e819ce0aae03c716c44273", "query": "}, }, }, <ins> Required: []string{\"name\"}, </ins> }, }, Dependencies: []string{},", "positive_passages": [{"docid": "doc-en-kubernetes-65858ef6270e846dbad645a3cdb03be72308acbcbd2d437380bbe522248f5825", "text": "FYI. Currently the field of TPR is marked as which is wrong, actually if you try to create a TPR with empty versions, it will cause api server panic. Versions should be necessary field of TPR, we should validate this somehow.", "commid": "kubernetes_issue_36991", "tokennum": 52}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7c3a89fd7f2ba045184a8808a8942a6e7ba395fb954a317629cb172fe4ab9584", "query": "key = \"oops something went wrong with the key\" } <del> // Record some output when items are deleted. outputSetLock.Lock() defer outputSetLock.Unlock() outputSet.Insert(key) </del> <ins> // Report this deletion. deletionCounter <- key </ins> }, }, ) // Run the controller and run it until we close stop. stop := make(chan struct{}) <ins> defer close(stop) </ins> go controller.Run(stop) // Let's add a few objects to the source. <del> for _, name := range []string{\"a-hello\", \"b-controller\", \"c-framework\"} { </del> <ins> testIDs := []string{\"a-hello\", \"b-controller\", \"c-framework\"} for _, name := range testIDs { </ins> // Note that these pods are not valid-- the fake source doesn't <del> // call validation or perform any other checking. </del> <ins> // call validation or anything. </ins> source.Add(&api.Pod{ObjectMeta: api.ObjectMeta{Name: name}}) } // Let's wait for the controller to process the things we just added. <del> time.Sleep(500 * time.Millisecond) close(stop) </del> <ins> outputSet := util.StringSet{} for i := 0; i < len(testIDs); i++ { outputSet.Insert(<-deletionCounter) } </ins> <del> outputSetLock.Lock() </del> for _, key := range outputSet.List() { fmt.Println(key) }", "positive_passages": [{"docid": "doc-en-kubernetes-20ba07f969c78351406740c712da4b4d48c539c847c31f97f90729edba71a7c4", "text": "From shippable, I noticed there are several failed cases, for example, E0413 17:34:38. ] watch of *api.Pod ended with: Stop requested --- FAIL: Example (0.61s) got: want: a-hello b-controller c-framework FAIL coverage: 85.9% of statements FAIL 7.652s cc/\nanother example:\nah-- this is a different thing. I will fix this, too.\nI'm seeing this from an unrelated change\nYeah I think that's the one I expected to see.", "commid": "kubernetes_issue_6777", "tokennum": 121}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7c5bb456baa7b9d172640d79ca153592a2d630754dd811d9d0a1b4936e748f08", "query": "}, { // PV requires external deleter <del> name:            \"8-10 - external deleter\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </del> <ins> name:            \"8-10-1 - external deleter when volume is dynamic provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </ins> initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents,", "positive_passages": [{"docid": "doc-en-kubernetes-17da90f267168da4485057cb3c70835a09c33080424540be2f99c7292698f22f", "text": "In my CSI controller I have enabled the feature gate HonorPVReclaimPolicy for csi-provisioner. Based on the documentation Finalizers can be on a PersistentVolume to ensure that PersistentVolumes having Delete reclaim policy are deleted only after the backing storage are deleted. The newly introduced finalizers and external- are only to dynamically provisioned volumes. I can see the finalizer set on the PV while creating static Persistent Volume. PV deletion is stuck due to this finalizer apiVersion: v1 kind: PersistentVolume metadata: creationTimestamp: \"2023-11-08T11:39:24Z\" deletionGracePeriodSeconds: 0 deletionTimestamp: \"2023-11-08T11:54:31Z\" finalizers: external- name: csi-infoscale-pv PV should be deleted when PVC is deleted. Persistent Volume yaml apiVersion: v1 kind: PersistentVolume metadata: name: csi-infoscale-pv spec: storageClassName: csi-infoscale-sc-prod persistentVolumeReclaimPolicy: Delete capacity: storage: 2Gi accessModes: ReadWriteOnce csi: driver: org.veritas.infoscale # Please provide pre-provisioned Infoscale volume name. volumeHandle: clust21432/vrtskube_dg-/vol1 fsType: vxfs Persistent Volume Claim apiVersion: v1 kind: PersistentVolumeClaim metadata: name: csi-infoscale-pvc-static spec: accessModes: ReadWriteOnce resources: requests: storage: 2Gi storageClassName: csi-infoscale-sc-prod volumeName: csi-infoscale-pv Same thing works fine on OCP. WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version.", "commid": "kubernetes_issue_121799", "tokennum": 440}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7c5bb456baa7b9d172640d79ca153592a2d630754dd811d9d0a1b4936e748f08", "query": "}, { // PV requires external deleter <del> name:            \"8-10 - external deleter\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </del> <ins> name:            \"8-10-1 - external deleter when volume is dynamic provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </ins> initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents,", "positive_passages": [{"docid": "doc-en-kubernetes-0ba3f4f18a7007434ced94c47e051d55455d5fb79cd77986fc1ae4d5bc653af8", "text": "Client Version: version.Info{Major:\"1\", Minor:\"27\", GitVersion:\"v1.27.5\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2023-08-24T00:48:26Z\", GoVersion:\"go1.20.7\", Compiler:\"gc\", Platform:\"linux/amd64\"} Kustomize Version: v5.0.1 Server Version: version.Info{Major:\"1\", Minor:\"27\", GitVersion:\"v1.27.5\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2023-08-24T00:42:11Z\", GoVersion:\"go1.20.7\", Compiler:\"gc\", Platform:\"linux/amd64\"} Vanilla K8s setup <details</details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig storage maybe similar issues should go in\nOpened similar issue in external-provisioner repo also There is no reply on that as well. Can you please help understand the behavior of the feature HonorPVReclaimPolicy.\nIf you want Persistent Volume (PV) to be deleted when the associated Persistent Volume Claim (PVC) is deleted, you donot need to use finalizers explicitly. Kubernetes handles this behavior by default. It is ok that if you use to get the desire output using Finalizer we can do it.\nAs per my understanding Please follow the steps : Add finalizer in metadata of as you did above need to make change in the controller which is handling PV deletion in .go file. See whether the controller administrator is working or not. I think it will work.\nFinalizer is because the feature gate HonorPVReclaimPolicy for csi-provisioner is enabled. We are not adding the finalizer explicitly. From the documentation, \"The newly introduced finalizers and external- are only to dynamically provisioned volumes.\" Not sure why is the finalizer getting set.", "commid": "kubernetes_issue_121799", "tokennum": 555}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7c5bb456baa7b9d172640d79ca153592a2d630754dd811d9d0a1b4936e748f08", "query": "}, { // PV requires external deleter <del> name:            \"8-10 - external deleter\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </del> <ins> name:            \"8-10-1 - external deleter when volume is dynamic provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </ins> initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents,", "positive_passages": [{"docid": "doc-en-kubernetes-592cda3e1f42c2eb1f47fff2bb790922cec52a4f953f170e43c5acb028d04e55", "text": "Also, for deleting PV it requires the annotation \"\" but this annotation is set in case of dynamic PVs. Should it be set explicitly for static PV?\nThis feature is alpha so the feature gate is not enabled by default. Did you enable the feature gate on kube-controller-manager?\nYes, i have enabled this feature.\nexternal- is also applied to statically provisioned volumes. FYI\nHi Which version of the external provisioner is the driver using? Does the driver meet the requirements of the CSI spec on the DeleteVolume PRC? FYI: Is this problem occasional or permanently reproducible? Can you provide the provisioner logs at that time?\n/triage needs-information\ncc\ncc\nExternal provisioner used is : \"csi-provisioner:v3.5.0\" This problem is always reproducible Provisioner logs: I1123 12:22:38. 1 ] handleProtectionFinalizer Volume : &PersistentVolume{ObjectMeta:{csi-infoscale-pv -420a-4e9e-be82- 0 2023-11-23 12:21:18 +0000 UTC <nil<nilmap[] map[{\"apiVersion\":\"v1\",\"kind\":\"PersistentVolume\",\"metadata\":{\"annotations\":{},\"name\":\"csi-infoscale-pv\"},\"spec\":{\"accessModes\":[\"ReadWriteOnce\"],\"capacity\":{\"storage\":\"2Gi\"},\"csi\":{\"driver\":\"org.veritas.infoscale\",\"fsType\":\"vxfs\",\"volumeHandle\":\"clust40559/vrtskubedg-/vol1\"},\"persistentVolumeReclaimPolicy\":\"Delete\",\"storageClassName\":\"csi-infoscale-sc-prod\"}} ] [] [ external-] [{kubectl-client-side-apply Update v1 2023-11-23 12:21:18 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:annotations\":{\".\":{},\"\":{}}},\"f:spec\":{\"f:accessModes\":{},\"f:capacity\":{\".\":{},\"f:storage\":{}},\"f:csi\":{\".", "commid": "kubernetes_issue_121799", "tokennum": 563}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7c5bb456baa7b9d172640d79ca153592a2d630754dd811d9d0a1b4936e748f08", "query": "}, { // PV requires external deleter <del> name:            \"8-10 - external deleter\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </del> <ins> name:            \"8-10-1 - external deleter when volume is dynamic provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </ins> initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents,", "positive_passages": [{"docid": "doc-en-kubernetes-3ecd202a68dc777f32874cd48d4b39291a9bf67f2771bfe1a1dd4808649976b8", "text": "\":{},\"f:driver\":{},\"f:fsType\":{},\"f:volumeHandle\":{}},\"f:persistentVolumeReclaimPolicy\":{},\"f:storageClassName\":{},\"f:volumeMode\":{}}} } {csi-provisioner Update v1 2023-11-23 12:21:22 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:finalizers\":{\"v:\"external-\"\":{}}}} } {kube-controller-manager Update v1 2023-11-23 12:21:22 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:annotations\":{\"\":{}}},\"f:spec\":{\"f:claimRef\":{\".", "commid": "kubernetes_issue_121799", "tokennum": 208}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7c5bb456baa7b9d172640d79ca153592a2d630754dd811d9d0a1b4936e748f08", "query": "}, { // PV requires external deleter <del> name:            \"8-10 - external deleter\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </del> <ins> name:            \"8-10-1 - external deleter when volume is dynamic provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </ins> initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents,", "positive_passages": [{"docid": "doc-en-kubernetes-fb611cee6f984fef598fa329474fd3d3abef5728e2a0833d8129f0a5ee9ed92e", "text": "\":{},\"f:apiVersion\":{},\"f:kind\":{},\"f:name\":{},\"f:namespace\":{},\"f:resourceVersion\":{},\"f:uid\":{}}}} } {kube-controller-manager Update v1 2023-11-23 12:22:38 +0000 UTC FieldsV1 {\"f:status\":{\"f:phase\":{}}} status}]},Spec:PersistentVolumeSpec{Capacity:ResourceList{storage: {{ 0} {<nil} 2Gi BinarySI},},PersistentVolumeSource:PersistentVolumeSource{GCEPersistentDisk:nil,AWSElasticBlockStore:nil,HostPath:nil,Glusterfs:nil,NFS:nil,RBD:nil,ISCSI:nil,Cinder:nil,CephFS:nil,FC:nil,Flocker:nil,FlexVolume:nil,AzureFile:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Local:nil,StorageOS:nil,CSI:&CSIPersistentVolumeSource{Driver:org.veritas.infoscale,VolumeHandle:clust40559/vrtskubedg-/vol1,ReadOnly:false,FSType:vxfs,VolumeAttributes:map[string]string{},ControllerPublishSecretRef:nil,NodeStageSecretRef:nil,NodePublishSecretRef:nil,ControllerExpandSecretRef:nil,NodeExpandSecretRef:nil,},},AccessModes:[ReadWriteOnce],ClaimRef:&ObjectReference{Kind:PersistentVolumeClaim,Namespace:default,Name:csi-infoscale-pvc-static,UID:-59a5-4f02-83ac-,APIVersion:v1,ResourceVersion:,FieldPath:,},PersistentVolumeReclaimPolicy:Delete,StorageClassName:csi-infoscale-sc-prod,MountOptions:[],VolumeMode:Filesystem,NodeAffinity:nil,},Status:PersistentVolumeStatus{Phase:Released,Message:,Reason:,},} I1123 12:22:38. 1 ] delete \"csi-infoscale-pv\": started I1123 12:22:38. 1 ] GRPC call: /csi.v1.Controller/DeleteVolume I1123 12:22:38. 1 ] GRPC request: {\"volumeid\":\"clust40559/vrtskubedg-/vol1\"} I1123 12:22:39.", "commid": "kubernetes_issue_121799", "tokennum": 705}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7c5bb456baa7b9d172640d79ca153592a2d630754dd811d9d0a1b4936e748f08", "query": "}, { // PV requires external deleter <del> name:            \"8-10 - external deleter\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </del> <ins> name:            \"8-10-1 - external deleter when volume is dynamic provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </ins> initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents,", "positive_passages": [{"docid": "doc-en-kubernetes-21563431fea9ed5a14c1fde8160d9fcab633c35237ee882cf06625b1768a9487", "text": "1 ] GRPC response: {} I1123 12:22:39. 1 ] GRPC error: <nilI1123 12:22:39. 1 ] delete \"csi-infoscale-pv\": volume deleted I1123 12:22:39. 1 ] delete \"csi-infoscale-pv\": failed to remove finalizer for persistentvolume: Operation cannot be fulfilled on persistentvolumes \"csi-infoscale-pv\": the object has been modified; please apply your changes to the latest version and try again W1123 12:22:39. 1 ] Retrying syncing volume \"csi-infoscale-pv\", failure 0 E1123 12:22:39. 1 ] error syncing volume \"csi-infoscale-pv\": Operation cannot be fulfilled on persistentvolumes \"csi-infoscale-pv\": the object has been modified; please apply your changes to the latest version and try again I1123 12:22:39. 1 ] handleProtectionFinalizer Volume : &PersistentVolume{ObjectMeta:{csi-infoscale-pv -420a-4e9e-be82- 0 2023-11-23 12:21:18 +0000 UTC 2023-11-23 12:22:38 +0000 UTC 0xc0007f63d0 map[] map[{\"apiVersion\":\"v1\",\"kind\":\"PersistentVolume\",\"metadata\":{\"annotations\":{},\"name\":\"csi-infoscale-pv\"},\"spec\":{\"accessModes\":[\"ReadWriteOnce\"],\"capacity\":{\"storage\":\"2Gi\"},\"csi\":{\"driver\":\"org.veritas.infoscale\",\"fsType\":\"vxfs\",\"volumeHandle\":\"clust40559/vrtskubedg-/vol1\"},\"persistentVolumeReclaimPolicy\":\"Delete\",\"storageClassName\":\"csi-infoscale-sc-prod\"}} ] [] [external-] [{kubectl-client-side-apply Update v1 2023-11-23 12:21:18 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:annotations\":{\".\":{},\"\":{}}},\"f:spec\":{\"f:accessModes\":{},\"f:capacity\":{\".\":{},\"f:storage\":{}},\"f:csi\":{\".", "commid": "kubernetes_issue_121799", "tokennum": 610}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7c5bb456baa7b9d172640d79ca153592a2d630754dd811d9d0a1b4936e748f08", "query": "}, { // PV requires external deleter <del> name:            \"8-10 - external deleter\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </del> <ins> name:            \"8-10-1 - external deleter when volume is dynamic provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </ins> initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents,", "positive_passages": [{"docid": "doc-en-kubernetes-3ecd202a68dc777f32874cd48d4b39291a9bf67f2771bfe1a1dd4808649976b8", "text": "\":{},\"f:driver\":{},\"f:fsType\":{},\"f:volumeHandle\":{}},\"f:persistentVolumeReclaimPolicy\":{},\"f:storageClassName\":{},\"f:volumeMode\":{}}} } {csi-provisioner Update v1 2023-11-23 12:21:22 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:finalizers\":{\"v:\"external-\"\":{}}}} } {kube-controller-manager Update v1 2023-11-23 12:21:22 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:annotations\":{\"\":{}}},\"f:spec\":{\"f:claimRef\":{\".", "commid": "kubernetes_issue_121799", "tokennum": 208}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7c5bb456baa7b9d172640d79ca153592a2d630754dd811d9d0a1b4936e748f08", "query": "}, { // PV requires external deleter <del> name:            \"8-10 - external deleter\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </del> <ins> name:            \"8-10-1 - external deleter when volume is dynamic provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </ins> initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents,", "positive_passages": [{"docid": "doc-en-kubernetes-11586616fd718035f7c04dbcead8d898c73d9e9840ec80b2b32382f64622ed92", "text": "\":{},\"f:apiVersion\":{},\"f:kind\":{},\"f:name\":{},\"f:namespace\":{},\"f:resourceVersion\":{},\"f:uid\":{}}}} } {kube-controller-manager Update v1 2023-11-23 12:22:38 +0000 UTC FieldsV1 {\"f:status\":{\"f:message\":{},\"f:phase\":{}}} status}]},Spec:PersistentVolumeSpec{Capacity:ResourceList{storage: {{ 0} {<nil} 2Gi BinarySI},},PersistentVolumeSource:PersistentVolumeSource{GCEPersistentDisk:nil,AWSElasticBlockStore:nil,HostPath:nil,Glusterfs:nil,NFS:nil,RBD:nil,ISCSI:nil,Cinder:nil,CephFS:nil,FC:nil,Flocker:nil,FlexVolume:nil,AzureFile:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Local:nil,StorageOS:nil,CSI:&CSIPersistentVolumeSource{Driver:org.veritas.infoscale,VolumeHandle:clust40559/vrtskubedg-/vol1,ReadOnly:false,FSType:vxfs,VolumeAttributes:map[string]string{},ControllerPublishSecretRef:nil,NodeStageSecretRef:nil,NodePublishSecretRef:nil,ControllerExpandSecretRef:nil,NodeExpandSecretRef:nil,},},AccessModes:[ReadWriteOnce],ClaimRef:&ObjectReference{Kind:PersistentVolumeClaim,Namespace:default,Name:csi-infoscale-pvc-static,UID:-59a5-4f02-83ac-,APIVersion:v1,ResourceVersion:,FieldPath:,},PersistentVolumeReclaimPolicy:Delete,StorageClassName:csi-infoscale-sc-prod,MountOptions:[],VolumeMode:Filesystem,NodeAffinity:nil,},Status:PersistentVolumeStatus{Phase:Failed,Message:error getting deleter volume plugin for volume \"csi-infoscale-pv\": no deletable volume plugin matched,Reason:,},} I1123 12:22:40.", "commid": "kubernetes_issue_121799", "tokennum": 650}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7c5bb456baa7b9d172640d79ca153592a2d630754dd811d9d0a1b4936e748f08", "query": "}, { // PV requires external deleter <del> name:            \"8-10 - external deleter\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </del> <ins> name:            \"8-10-1 - external deleter when volume is dynamic provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </ins> initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents,", "positive_passages": [{"docid": "doc-en-kubernetes-372f094f1905cb03e404d407c686a802e84a00b41a059cf5fa90382ee5601de2", "text": "1 ] handleProtectionFinalizer Volume : &PersistentVolume{ObjectMeta:{csi-infoscale-pv -420a-4e9e-be82- 0 2023-11-23 12:21:18 +0000 UTC 2023-11-23 12:22:38 +0000 UTC 0xc0007f63d0 map[] map[{\"apiVersion\":\"v1\",\"kind\":\"PersistentVolume\",\"metadata\":{\"annotations\":{},\"name\":\"csi-infoscale-pv\"},\"spec\":{\"accessModes\":[\"ReadWriteOnce\"],\"capacity\":{\"storage\":\"2Gi\"},\"csi\":{\"driver\":\"org.veritas.infoscale\",\"fsType\":\"vxfs\",\"volumeHandle\":\"clust40559/vrtskubedg-/vol1\"},\"persistentVolumeReclaimPolicy\":\"Delete\",\"storageClassName\":\"csi-infoscale-sc-prod\"}} ] [] [external-] [{kubectl-client-side-apply Update v1 2023-11-23 12:21:18 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:annotations\":{\".\":{},\"\":{}}},\"f:spec\":{\"f:accessModes\":{},\"f:capacity\":{\".\":{},\"f:storage\":{}},\"f:csi\":{\".\":{},\"f:driver\":{},\"f:fsType\":{},\"f:volumeHandle\":{}},\"f:persistentVolumeReclaimPolicy\":{},\"f:storageClassName\":{},\"f:volumeMode\":{}}} } {csi-provisioner Update v1 2023-11-23 12:21:22 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:finalizers\":{\"v:\"external-\"\":{}}}} } {kube-controller-manager Update v1 2023-11-23 12:21:22 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:annotations\":{\"\":{}}},\"f:spec\":{\"f:claimRef\":{\".", "commid": "kubernetes_issue_121799", "tokennum": 599}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7c5bb456baa7b9d172640d79ca153592a2d630754dd811d9d0a1b4936e748f08", "query": "}, { // PV requires external deleter <del> name:            \"8-10 - external deleter\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10\", \"1Gi\", \"uid10-1\", \"claim10-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </del> <ins> name:            \"8-10-1 - external deleter when volume is dynamic provisioning\", initialVolumes:  []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeBound, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, expectedVolumes: []*v1.PersistentVolume{newExternalProvisionedVolume(\"volume8-10-1\", \"1Gi\", \"uid10-1-1\", \"claim10-1-1\", v1.VolumeReleased, v1.PersistentVolumeReclaimDelete, classEmpty, gceDriver, nil, volume.AnnBoundByController)}, </ins> initialClaims:   noclaims, expectedClaims:  noclaims, expectedEvents:  noevents,", "positive_passages": [{"docid": "doc-en-kubernetes-8654731eb8139b66a1cecad4a317b2078534f6977aa1c7223978f7fff83e9392", "text": "\":{},\"f:apiVersion\":{},\"f:kind\":{},\"f:name\":{},\"f:namespace\":{},\"f:resourceVersion\":{},\"f:uid\":{}}}} } {kube-controller-manager Update v1 2023-11-23 12:22:38 +0000 UTC FieldsV1 {\"f:status\":{\"f:message\":{},\"f:phase\":{}}} status}]},Spec:PersistentVolumeSpec{Capacity:ResourceList{storage: {{ 0} {<nil} 2Gi BinarySI},},PersistentVolumeSource:PersistentVolumeSource{GCEPersistentDisk:nil,AWSElasticBlockStore:nil,HostPath:nil,Glusterfs:nil,NFS:nil,RBD:nil,ISCSI:nil,Cinder:nil,CephFS:nil,FC:nil,Flocker:nil,FlexVolume:nil,AzureFile:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Local:nil,StorageOS:nil,CSI:&CSIPersistentVolumeSource{Driver:org.veritas.infoscale,VolumeHandle:clust40559/vrtskubedg-/vol1,ReadOnly:false,FSType:vxfs,VolumeAttributes:map[string]string{},ControllerPublishSecretRef:nil,NodeStageSecretRef:nil,NodePublishSecretRef:nil,ControllerExpandSecretRef:nil,NodeExpandSecretRef:nil,},},AccessModes:[ReadWriteOnce],ClaimRef:&ObjectReference{Kind:PersistentVolumeClaim,Namespace:default,Name:csi-infoscale-pvc-static,UID:-59a5-4f02-83ac-,APIVersion:v1,ResourceVersion:,FieldPath:,},PersistentVolumeReclaimPolicy:Delete,StorageClassName:csi-infoscale-sc-prod,MountOptions:[],VolumeMode:*Filesystem,NodeAffinity:nil,},Status:PersistentVolumeStatus{Phase:Failed,Message:error getting deleter volume plugin for volume \"csi-infoscale-pv\": no deletable volume plugin matched,Reason:,},}\nThank you I will try to fix it. /remove-triage needs-information /assign", "commid": "kubernetes_issue_121799", "tokennum": 661}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7c9d8af9a61997fc27922c486cdac55660c2134260f357190a7b916988b29ded", "query": "namespace: kube-system labels: k8s-app: fluentd-gcp-scaler <del> version: v0.1.0 </del> <ins> version: v0.2.0 </ins> addonmanager.kubernetes.io/mode: Reconcile spec: selector:", "positive_passages": [{"docid": "doc-en-kubernetes-a63e01ebe6efecf34b1eda7468cd7472762d7f902ee9117cf6f0f2ff92b9f93a", "text": "Forking from To summarize, here's what we observed: daemonset calls coming every minute from both fluentd-scaler and addon-manager (verified this by individually turning them on/off). Things we need to understand here: Is the daemonset object continuously toggling b/w 2 states? (we know here that it's RV is increasing continuously) If yes, what field(s) in the object are changing? IIRC value of some label/annotation (I think 'UpdatedPodsScheduled') is changing (probably related to 2 below) Also, why/should the fluentd-scaler send any api request if the resources are already set to the right value? pods are getting deleted and recreated by daemonset-controller when the scaler is enabled (as was also seen in ). Why this is happening? One thing to note here - all those delete calls are preceded by calls from respective kubelets (but maybe that's expected). cc /priority critical-urgent /assign\nMarked this as release-blocker as at least some part of it seems like a correctness issue (i.e fluentd pods dying and getting recreated). Note also that this is causing increased mem-usage with daemonset-controller (depicted here - )\nThanks for filing this! The only thing that was changing (apart from ds/fluentd-gcp status) was the resource version.\nI modified fluentd scaler to use --dry-run in to check whether there would be a change, but this still keeps on updating, even though there is no change. Apparently, the logic inside kubectl is broken...\nBtw, addon manager sends tons of PATCH requests for all resources every minute anyway, so even though I will fix fluent-scaler not to send them, it won't solve everything.\nShould this issue actually be closed? It was auto-closed by the bot, but nobody has confirmed that the actual issue is fixed.\nI'll let to confirm (looks like he'll be back on Monday)\n/status in-progress\nYes, we should keep this issue open until we fully understand what's going wrong and fix the root-cause. I believe much of the discussion wrt this is happening under related issue\nACK. In progress ETA: 20/03/2018 Risks: May delay the release if not satisfactorily resolved\nNeed a number of successive green runs, then close.", "commid": "kubernetes_issue_61190", "tokennum": 515}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7c9d8af9a61997fc27922c486cdac55660c2134260f357190a7b916988b29ded", "query": "namespace: kube-system labels: k8s-app: fluentd-gcp-scaler <del> version: v0.1.0 </del> <ins> version: v0.2.0 </ins> addonmanager.kubernetes.io/mode: Reconcile spec: selector:", "positive_passages": [{"docid": "doc-en-kubernetes-2efbc26b22516e4405a8d5724e6f4faec26f16538d69327dd97918ad592fbe81", "text": "So I took a look and seems like the fluentd-scaler version bump (which was supposed to fix) was merged b/w runs and of our . However, I don't see any visible improvement in controller-manager memory usage around that time: !\nAlso, I'm noticing such lines occasionally (once every 5-10 secs in the start and once every ~1min later on) from of latest run: And back when the fluentd-scaler wasn't doing anything useful (i.e before ), the had such lines only sparingly.\nNow it isn't even sending requests (other than GET) to the apiserver. How do you generate that graph? Is it 99th percentile of memory usage over time? Or what exactly? One difference after introducing fluentd-gcp-scaler is that now there is a change occurring on the DaemonSet (once, but still). Also, what test is failing because of this? I'd like to take a look into the logs.\nAnswering your questions: I fetched the ResourceUsageSummaries for density test from historical runs (e.g ) and then obtained the 99% mem-usage for controller-manager for each run. Yes. More precisely, we're collecting mem-usage from controller-manager once every 1 min (or sth like that) and then taking 99th %ile of the resulting sample. Density and load tests. Where we're checking that mem usage of controller-manager is less than the given threshold (i.e 500MB). Ref: The tests are occasionally failing due to just crossing the threshold. Overall, the mem-usage had seen an increase back during the scaler change (see graph above). The job is this - https://k8s- Inside , you'll find all necessary logs (also a file named which has the resource-usage data).\nThe fluentd-scaler update eliminated fluentd restarts problem. Verified from controller-manager logs that we no longer see such logs that we were : This is great, and I believe that moves this out of release-blocker as we no longer face problems I mentioned in\nThat said, and me will continue looking into increase in mem-usage (which is not that serious). We'll start by verifying that turning the scaler off improves mem-usage.\nFeel free to override me if you have a good reason :)\nI agree that this doesn't sounds to be release-blocker.", "commid": "kubernetes_issue_61190", "tokennum": 529}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7c9d8af9a61997fc27922c486cdac55660c2134260f357190a7b916988b29ded", "query": "namespace: kube-system labels: k8s-app: fluentd-gcp-scaler <del> version: v0.1.0 </del> <ins> version: v0.2.0 </ins> addonmanager.kubernetes.io/mode: Reconcile spec: selector:", "positive_passages": [{"docid": "doc-en-kubernetes-ad76c0c3dd106ecff60d8298c8700ef88a9f32d4985b54e29d57ef6ad7351ef8", "text": "But I would like to see follow-ups at least for issues like: does this memory increase come from? what was claimed to be \"no-op\" changes for daemon set were causing problems [is that issues in kubectl, apiserver, somewhere else?] Something like that may hit us again in the (near?) future if we won't understand it now. The current solution is really volatile [if there is a bug somewhere we shouldn't workaround it on our side, but instead have this fixed] at the cluster start (maybe it's fine to leave as is, but I would like to see a discussion of that and a conscious decision being made here)\nDefinitely agree those are questions we need to answer.\nYup. 1) is tested in . 2) I believe apiserver sends watch events even when only resource version changes, which causes the daemonset controller to recreate the pods. So either: resource version shouldn't change when there is no change anywhere else in the resource apiserver shouldn't send watch events when only resource version is changing daemonset should check whether watch event it got is actually changing anything 3) Isn't that an inherent part of the way addon manager works? It creates all sorts of resources, some dependent on the other (e.g. cluster roles and cluster role bindings), all at once. If some dependency is not satisfied, it will get fixed during the next run.\nThis is the code that is supposed to protect us from situation that something must change when we write object to etcd (resource version is not stored in etcd): So there should never be a situation that only resource version is changing. If it is, there is bug and need to be fixed. - FYI Reconciliation is a different thing that creating something in one state only to change that to a different state by a different component. I'm not saying this is for sure wrong approach. But I would like to see a conscious decision process discussing pros-and-cons of that.\nThat's what I'd expect as well. This I'm not sure if should be correct behaviour as IIUC watchers need to receive every RV update for correctness reasons ( ) Maybe. But are we sure if RV is just increasing without any object change? For creation of addons, yes (that race will likely last only for starting few seconds).", "commid": "kubernetes_issue_61190", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7c9d8af9a61997fc27922c486cdac55660c2134260f357190a7b916988b29ded", "query": "namespace: kube-system labels: k8s-app: fluentd-gcp-scaler <del> version: v0.1.0 </del> <ins> version: v0.2.0 </ins> addonmanager.kubernetes.io/mode: Reconcile spec: selector:", "positive_passages": [{"docid": "doc-en-kubernetes-87ee63a141c821e91ed597807f3f6830646e2e9b40e1991334df493e9d39b5a9", "text": "But this is wrt addon changing cluster resources, which can potentially create race at arbitrary time after cluster start (though your fix may have gotten rid of this).\nOk.. Seems like I missed Wojtek's comment above.\nSo I just checked the ds-controller code and it seems like we're updating the ds status only if this condition is being violated: Which means one of those fields is probably mismatching. I'll try to add some logs and run the test at --v=4 to get more info.\nanything is possible, but we do have tests ensuring this works properly (no-op updates do not actually result in an update+resourceVersion bump in etcd):\nSo I ran some 100-node experiments against with more debug logs and I think I now understand the reason for this. The controller-manager logs and mainly show the following difference: This logs show-up when the scaler is active. And these pod deletions are happening as part of rolling-upgrade of daemonset to newer version (the one having resources set). You can see they're getting deleted one-by-one, which also explains why it takes so long (and so are happening even 30 mins after the cluster creation). And the reason why they're deleted one-by-one is because ds-controller has a rolling-upgrade strategy where by default. Proof: And the increased mem-usage FMU is because of the rolling-upgrade performed by ds-controller (over the prolonged period) - as it's the only difference I observe from logs Further, the reason why the RV was increasing was because of few fields 'NumUnavailable', 'NumAvailable', etc fluctuating while the rolling-upgrade\nI spoke offline with and suggested that we should increase maxUnavailable for the fluentd daemonset to a large enough value so that we're not bottlenecked by it. My reasoning is: fluentd is not some user workload which will have some service downtime in case there are many unavailable at once fluentds on nodes are independent of each other (i.e one fluentd shouldn't need to wait for another node's fluentd to come up) we should try to make the scaling happen as fast as possible - otherwise it may be too late before they cope-up with increased log-load in the cluster I'm going to make that change and test it against my PR (thanks for pointing that we can change maxUnavailable directly in ds config).", "commid": "kubernetes_issue_61190", "tokennum": 536}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7c9d8af9a61997fc27922c486cdac55660c2134260f357190a7b916988b29ded", "query": "namespace: kube-system labels: k8s-app: fluentd-gcp-scaler <del> version: v0.1.0 </del> <ins> version: v0.2.0 </ins> addonmanager.kubernetes.io/mode: Reconcile spec: selector:", "positive_passages": [{"docid": "doc-en-kubernetes-90b3139f2f371dfe70c636d4111a7217036a6164fbce02b650a75f688275a9fd", "text": "So increasing maxUnavailable indeed seems to help (ref: ): All the 101 replicas were deleted at once instead of one-by-one and happened pretty much within 2 mins of the original fluentd-ds seen by the controller: We should get that PR into 1.10.\nThanks for confirming this! Did increasing maxUnavailable also reduce c-m memory usage?\nSo the run was still over the threshold, but I was expecting it as I ran c-m with increased verbosity (which ). That said, I'll observe how the usages are once that PR gets in - and FMU it's still possible to have higher values due to the rolling-upgrade potentially happening during the test.\nIs there anything else to do here or should this be closed now?\nLet's close it once we're sure there are no more such failures. We may also need to bump the threshold. On Mon, Mar 26, 2018, 9:46 AM Kubernetes Submit Queue < :\nSo bumping maxUnavailable for fluentd rolling-upgrade in is causing couple of issues: Our latest 5k-node performance failed as part of BeforeSuite where we're checking that ~all kube-system pods are running or ready. The reason is because quite some fluentd pods were killed as part of the rolling-upgrade and we timed out before all those pods could come up Our 100-node performance runs due to high CPU/mem-usage of c-m observed during density test, in cases when the fluentd upgrade happens during the test - which is kind of expected So at this point, we might want to choose among one of the 2 options: Rollback , which comes at the cost of tradeoffs I explained in Increase our CPU/mem thresholds to eliminate those flakes in 100-node job and increase the \"max-allowed-not-ready-pods\" in kube-system ns to a higher value, so that our 5k-node test doesn't fail in BeforeSuite Thoughts?\nTBH, I don't know why it was merged without waiting for opinions... I really vote for reverting that. We don't want this - this may mean making cluster \"not fully usable\" from user perspective.Which is not really what we want to test.\nSGTM. Let's revert it and increase our thresholds for the time-being. The discussion about changing fluentd rolling-upgrades can continue to happen in the background.", "commid": "kubernetes_issue_61190", "tokennum": 523}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7c9d8af9a61997fc27922c486cdac55660c2134260f357190a7b916988b29ded", "query": "namespace: kube-system labels: k8s-app: fluentd-gcp-scaler <del> version: v0.1.0 </del> <ins> version: v0.2.0 </ins> addonmanager.kubernetes.io/mode: Reconcile spec: selector:", "positive_passages": [{"docid": "doc-en-kubernetes-59f7438c09573642bfc1d12812df1bf9a90b62da276e49f75dd1387c9fcb0e09", "text": "[MILESTONENOTIFIER] Milestone Issue Needs Approval Action required: This issue must have the label applied by a SIG maintainer. If the label is not applied within 5 days, the issue will be moved out of the v1.11 milestone. <details<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details\nThis issue is now fixed after my above PRs. We're having continuous for the job", "commid": "kubernetes_issue_61190", "tokennum": 184}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7cd8b49c5631068e4520ae09850148fcd0c464b3ce63cd7a8ec5a863c42825e7", "query": "if limitedMode { limitedNum-- } <ins> if len(msg.log) > 0 { isNewLine = msg.log[len(msg.log)-1] == eol[0] } else { isNewLine = true } </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-1611cacb700fc7bde4bed341ff7dc392aeb6c35e6c0f63ce6a10b84981e8d04a", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Docker has a hardcoded 16K limit on log line length, which splits lines longer than that into multiple messages in the log file. in , however, doesn't account for this when is set to and prints the timestamp in front of every entry in the log file instead of every logical line. This leads to random timestamps appearing in the middle of log lines, potentially breaking the applications that parse these logs. What you expected to happen: inserts timestamps once per logical line, so original log data is preserved. Alternatively, allow API to request the logs in a sane format like JSON, which would allow merging the lines back and combining them with the timestamps more intelligently on the application side. How to reproduce it (as minimally and precisely as possible): Create : apiVersion: v1 kind: Pod metadata: name: log-lines spec: containers: name: main image: busybox command: ['sh', '-c', 'while sleep 1; do echo -n ; for i in $(seq 1 ); do echo -n A; done; echo ; done'] Start the pod with Fetch the logs with , or using the API () Observe random timestamps inserted in the middle of the log lines. Environment: Kubernetes version (use ):\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI will work on it. /sig cli /remove-sig node\nThe logs are being corrupted by the API endpoint in kubelet, so shouldn't it be in scope of SIG node?\nThe log is not corrupted by k8s. The same log could be got using \"docker container logs -t CONTAINERID\" I think you should post your requirement to Docker.", "commid": "kubernetes_issue_77603", "tokennum": 465}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7cd8b49c5631068e4520ae09850148fcd0c464b3ce63cd7a8ec5a863c42825e7", "query": "if limitedMode { limitedNum-- } <ins> if len(msg.log) > 0 { isNewLine = msg.log[len(msg.log)-1] == eol[0] } else { isNewLine = true } </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-495f248c0af4a1a8db07569505db46eac9f11be4907de183bc6923cd7882b142", "text": "Please refer following code Line 50 ~ 52 if config.Timestamps { logLine = append([]byte(msg.Timestamp.Format(jsonmessage.RFC3339NanoFixed)+\" \"), logLine...) }\nkubelet doesn't rely on Docker when reading logs, it reads the files itself (see the code linked in the issue). I don't think Docker would change the forced line splitting (see for example), so this should be fixed in Kubernetes.\nYour are right and kubelet read log file from host such as /var/log/pods/pods/NAMESPACEPOD-NAMExxx/....(JSON format) I will post a PR for it. /remove-sig cli /sig node\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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 .", "commid": "kubernetes_issue_77603", "tokennum": 539}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7cd8b49c5631068e4520ae09850148fcd0c464b3ce63cd7a8ec5a863c42825e7", "query": "if limitedMode { limitedNum-- } <ins> if len(msg.log) > 0 { isNewLine = msg.log[len(msg.log)-1] == eol[0] } else { isNewLine = true } </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-2f614c9ad06da31fe9313a5b2eaea6d6901d55cba8508cf5ebe57105d301c4f6", "text": "Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\nStale 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\nI saw the attempt fixing this but it was scary (echo this comment: ). I suggested a way it may be improved. Also the proposed fix didn't introduce any e2e tests to validate that runtime behavior is not changed and runtimes keep the no-newline-on-splitted-log logic. are you or anybody on this thread are still interested to work on this? Please re-open if so. Meanwhile closing this ahead of bot doing it because the inactivity. /close\nClosing this issue. <detailsIn response to : I saw the attempt fixing this but it was scary (echo this comment: ). I suggested a way it may be improved. Also the proposed fix didn't introduce any e2e tests to validate that runtime behavior is not changed and runtimes keep the no-newline-on-splitted-log logic. Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_77603", "tokennum": 493}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7cd8b49c5631068e4520ae09850148fcd0c464b3ce63cd7a8ec5a863c42825e7", "query": "if limitedMode { limitedNum-- } <ins> if len(msg.log) > 0 { isNewLine = msg.log[len(msg.log)-1] == eol[0] } else { isNewLine = true } </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-2e8714433462894a36e35ec9c24fb7c5a56d0558d2953a09bb86920b184c167e", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nYou can't reopen an issue/PR unless you authored it or you are a collaborator. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/remove-lifecycle rotten /reopen will fix it.\nReopened this issue. <detailsIn response to : /remove-lifecycle rotten /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/triage accepted\nThe Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.", "commid": "kubernetes_issue_77603", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7cd8b49c5631068e4520ae09850148fcd0c464b3ce63cd7a8ec5a863c42825e7", "query": "if limitedMode { limitedNum-- } <ins> if len(msg.log) > 0 { isNewLine = msg.log[len(msg.log)-1] == eol[0] } else { isNewLine = true } </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-422d52914e9725e7355cb5e937e13c24e15f273f63951d92fe52d86a167487cb", "text": "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]:\nThe 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]:\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_77603", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7cd8b49c5631068e4520ae09850148fcd0c464b3ce63cd7a8ec5a863c42825e7", "query": "if limitedMode { limitedNum-- } <ins> if len(msg.log) > 0 { isNewLine = msg.log[len(msg.log)-1] == eol[0] } else { isNewLine = true } </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-0e28d298340708e57a780633dba41fa2a744d19c9ab3d061a118f6b1e6c3d902", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI received a bug report about this issue. The root cause is that the buffer reads up to a new line. If the line is greater than 4096 bytes and '--timestamps' is turrned on the kubelet will write the timestamp and the partial log line. We will need to refactor the ReadLogs function to allow for a partial line read.", "commid": "kubernetes_issue_77603", "tokennum": 104}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7d0ba8a8d6db28e11e579c355b4c0785cd65ae66172f4e604620bde745213b63", "query": "func exportCustomMetricFromService(f *framework.Framework, consumerName string, metricValue int) *common.ResourceConsumer { serviceAnnotations := map[string]string{ \"prometheus.io/scrape\": \"true\", <del> \"prometheus.io/path\":   \"/Metrics\", </del> <ins> \"prometheus.io/path\":   \"/metrics\", </ins> \"prometheus.io/port\":   \"8080\", } return common.NewMetricExporter(consumerName, f.Namespace.Name, nil, serviceAnnotations, metricValue, f.ClientSet, f.InternalClientset, f.ScalesGetter)", "positive_passages": [{"docid": "doc-en-kubernetes-2d0ebe90b3c755e0edf33c6811bf431b4c51fd00f4f7b6a1d49649dd59cb487b", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: Used the endpoint /BumpMetric to create fake metrics for Prometheus. When I tried to curl /metrics I got the following response: Bad request. Not a POST request What you expected to happen: I expected to see something like this: # HELP info message. # TYPE gauge 0. How to reproduce it (as minimally and precisely as possible): Following the docs, after having it running inside kubernetes: Anything else we need to know?: Looks like introduced this by mistake. Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: <!-- DO NOT EDIT BELOW THIS LINE --/kind bug\n/sig testing", "commid": "kubernetes_issue_72403", "tokennum": 213}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7d1257c6785b283ce73e57d0649889e9500ef2dfd03d5767b81cdfb3331ceed2", "query": "args: args, // PodStart is used as default because waiting for a pod is the // most common operation. <del> timeout:  TestContext.timeouts.PodStart, interval: TestContext.timeouts.Poll, </del> <ins> timeout:      TestContext.timeouts.PodStart, interval:     TestContext.timeouts.Poll, consistently: consistently, </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-d3815452ec6a4b65682bad0d5bef0b8e8ccaebedbf3ea598534c49251f831668", "text": "In and , I started seeing these flakes. The job in question has not been very flaky before so this is odd. In and , I started seeing these flakes. The job \"Job should not create pods when created in suspend state\" is the one that is flaking. Triage says a few days ago. No response No response /sig apps\nDid some digging and I did not see any changes that could account for an increase of flakiness in the job controller code. There was a change made to the e2e tests: The logs say: The code is pretty simple so I wonder if we are hitting a case where sometimes the suspend condition is not set and we fail. Maybe we could add a consistent call here?\n/triage accepted /priority important-soon\n/cc\n/reopen /assign do you mind monitoring the CI state for 1 or 2 days to confirm your PR really fixed it ?\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nIt makes sense to me.\ncc I think this issue has been fixed. Can we close it?\n/close Thanks for the fix. The test is not flaky now.\nClosing this issue. <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_121013", "tokennum": 313}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7d16a34e411853baf86f3134286f70a5d33c285ee275776685e37ecc367e0e22", "query": "// +groupName=samplecontroller.k8s.io // Package v1alpha1 is the v1alpha1 version of the API. <del> package v1alpha1 </del> <ins> package v1alpha1 // import \"k8s.io/sample-controller/pkg/apis/samplecontroller/v1alpha1\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-460ceb7b52a1ab0cadc1b29d7eee5cc1013b8d23be9bca0d145119ffcf7b27c6", "text": "Look at one of the directories under (Please don't pick more than one directory for one PR as it will cause issues for reviewers) Find all the files named (example find -name ) See the following link it has a this tells tools how this package needs to be imported. So we should ensure that each has an import Add a description appropriate to the package (similar to the one below) Look through sub directories and see if there are any other important directories that are likely to be used by outside users and add a Why are we doing this? We perfer to use vanity urls instead of directly using to refer to code, so this helps ensure that tools honor our wish. See It would be good to have some package level documentation since these directories under staging/ are meant to be for use by folks outside of kubernetes github org. /good-first-issue\n/kind documentation /sig architecture\ncurrently working my through Not going to use / assign since there could be a number of PRs for this issue.\n/lifecycle active /good-first-issue edit: hmm..\nThis request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /lifecycle active /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\nMay I try on\nIIUC this means that there needs to be a even at the root of the repo? Then how does work? :thinking:\nHi , can I make a PR for this directory ?\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_68231", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7d16a34e411853baf86f3134286f70a5d33c285ee275776685e37ecc367e0e22", "query": "// +groupName=samplecontroller.k8s.io // Package v1alpha1 is the v1alpha1 version of the API. <del> package v1alpha1 </del> <ins> package v1alpha1 // import \"k8s.io/sample-controller/pkg/apis/samplecontroller/v1alpha1\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-5f31f1c27d7198dc83b313154ff681043a8b41e17eb5d3ddf32cd84bc023f931", "text": "/lifecycle rotten\nI guess this is still not done, was supposed to partially fix this issue. /reopen\nReopened this issue. <detailsIn response to : I guess this is still not done, was supposed to partially fix this 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\n/remove-lifecycle rotten /area code-organization", "commid": "kubernetes_issue_68231", "tokennum": 93}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7d1a47e7ef0d0a1e97f26a7ef68552fea171769495bc5c0cfa96ebba7feb8c3f", "query": "# Arguments: a list of kubernetes packages to build. # Expected variables: ${build_args} should be set to an array of Go build arguments. # In addition, ${package} and ${platform} should have been set earlier, and if <del> # ${build_with_coverage} is set, coverage instrumentation will be enabled. </del> <ins> # ${KUBE_BUILD_WITH_COVERAGE} is set, coverage instrumentation will be enabled. </ins> # # Invokes Go to actually build some packages. If coverage is disabled, simply invokes # go install. If coverage is enabled, builds covered binaries using go test, temporarily # producing the required unit test files and then cleaning up after itself. # Non-covered binaries are then built using go install as usual. kube::golang::build_some_binaries() { <del> if [[ -n \"${build_with_coverage:-}\" ]]; then </del> <ins> if [[ -n \"${KUBE_BUILD_WITH_COVERAGE:-}\" ]]; then </ins> local -a uncovered=() for package in \"$@\"; do if kube::golang::is_instrumented_package \"${package}\"; then", "positive_passages": [{"docid": "doc-en-kubernetes-3d30f80339d7c67274e12c6190891fb695bbdad2c822e929f8e060cdf1647787", "text": "/kind cleanup /sig testing /priority important-longterm This is a followup issue to address the \"standard build globals\" nit on At the very least I think we shouldn't capture our custom env var. Also think it'd be worth documenting the assumed variables in a list, similar to\ncc\n/assign", "commid": "kubernetes_issue_68163", "tokennum": 69}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7d225c6aa97cecba17eb37fd459e3bebf373d4bfbb2a450b0abbebb838d9ac6b", "query": "# See the License for the specific language governing permissions and # limitations under the License. <del> # The line below points to debian:jessie as of 2019-10-23. The SHA should be # kept in sycn with debian_jessie definition in the WORKSPACE file. FROM debian@sha256:e25703ee6ab5b2fac31510323d959cdae31eebdf48e88891c549e55b25ad7e94 </del> <ins> # The line below points to distroless/base as of 2019-11-15. The SHA should be # kept in sycn with distroless_base definition in the WORKSPACE file. FROM gcr.io/distroless/base@sha256:7fa7445dfbebae4f4b7ab0e6ef99276e96075ae42584af6286ba080750d6dfe5 </ins> COPY kubemark /kubemark", "positive_passages": [{"docid": "doc-en-kubernetes-d99484417892d904a3f5edbb73fa06d2de654c460b279ad73f511e028afa6a6f", "text": "There are CVEs happening in different images - we already migrated Kubmeark from busybox in , but we should go one step further and migrate the base image to distroless. There are some things that would need to be changed mentioned here: /sig scalability\nCan I work on this? /assign\n/remove-help\n- sure that would be great.\nHi based on the discussion in , the kubemark image has dependency on and maybe more other utilities. So it seems impossible to migrate the base image to distroless? Or do we need something like debian-hyperkube-base?\nThe mount one we may get rid of - basically we should be able to switch to FakeMounter:", "commid": "kubernetes_issue_84284", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7d324a6ea6c5c26c6c57e8a249eb77e963ccf019af15fc54fa7977d560bca64f", "query": "hash := hash(podUpdate.nodeName()) select { case <-stopCh: <ins> tc.podUpdateQueue.Done(item) </ins> break case tc.podUpdateChannels[hash%workers] <- podUpdate: } <ins> tc.podUpdateQueue.Done(item) </ins> } }(stopCh)", "positive_passages": [{"docid": "doc-en-kubernetes-2c221590d5e1ff106fb9cb8927cfb7dd0bc0677f71da23dc8e18ac35421ec6b8", "text": "We're seeing an issue with large memory growth in NoExecuteTaintManager when pods with tolerations are rapidly created/deleted. The item to the workqueue contains the full pod objects received from the informer: That means those pod objects are retained until they are processed. Additionally, it looks like the processing loop never removed the keys from the workqueue when it was done. It also means that multiple updates for the same pod result in multiple items in the workqueue, rather than enqueuing the pod to be processed once, like other controllers do. Simplifying this controller to enqueue pod updates only by name/namespace, and operate on the latest pod obtained from the store (like other controllers do) would speed up the processing and relieve the memory burden of the workqueue. /sig scheduling /cc\n/assign\nThanks for finding this Jordan - looking into your fixes.\nthe memory issue was fixed by /close", "commid": "kubernetes_issue_65325", "tokennum": 197}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7d5567ae30b0a3fecb9cd1db02cd985bf42c5619aacc69f39d48455c6c2e2bac", "query": "<del> { \"apiVersion\": \"v1beta3\", \"kind\": \"ResourceQuota\", \"metadata\": { \"name\": \"quota\" }, \"spec\": { \"hard\": { \"memory\": \"1Gi\", \"cpu\": \"20\", \"pods\": \"10\", \"services\": \"5\", \"replicationcontrollers\":\"20\", \"resourcequotas\":\"1\", \"secrets\":\"10\", \"persistentvolumeclaims\":\"10\" } } } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-b9774b02da3d7547dcc6ec82c6d1246d6586e28e6fe16ad58f3c28b2558ac905", "text": "Resource quota example is missing readme. Was it once there and was accidentally deleted?\nI wrote something up in Origin repo I need to repurpose for Kubernetes. Sent from my iPhone", "commid": "kubernetes_issue_8749", "tokennum": 41}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7d6ada37844e18cfa384fde5e4d5d2d0a97871e672ed27ef05bf9cccea5ecc9a", "query": "return nil } <ins> // applyFSGroup applies the volume ownership it derives its logic // from https://github.com/kubernetes/kubernetes/issues/66323 // 1) if fstype is \"\", then skip fsgroup (could be indication of non-block filesystem) // 2) if fstype is provided and pv.AccessMode == ReadWriteOnly and !c.spec.ReadOnly then apply fsgroup func (c *csiMountMgr) applyFSGroup(fsType string, fsGroup *int64) error { if fsGroup != nil { if fsType == \"\" { glog.V(4).Info(log(\"mounter.SetupAt WARNING: skipping fsGroup, fsType not provided\")) return nil } accessModes := c.spec.PersistentVolume.Spec.AccessModes if c.spec.PersistentVolume.Spec.AccessModes == nil { glog.V(4).Info(log(\"mounter.SetupAt WARNING: skipping fsGroup, access modes not provided\")) return nil } if !hasReadWriteOnce(accessModes) { glog.V(4).Info(log(\"mounter.SetupAt WARNING: skipping fsGroup, only support ReadWriteOnce access mode\")) return nil } if c.readOnly { glog.V(4).Info(log(\"mounter.SetupAt WARNING: skipping fsGroup, volume is readOnly\")) return nil } err := volume.SetVolumeOwnership(c, fsGroup) if err != nil { return err } glog.V(4).Info(log(\"mounter.SetupAt fsGroup [%d] applied successfully to %s\", *fsGroup, c.volumeID)) } return nil } </ins> // isDirMounted returns the !notMounted result from IsLikelyNotMountPoint check func isDirMounted(plug *csiPlugin, dir string) (bool, error) { mounter := plug.host.GetMounter(plug.GetPluginName())", "positive_passages": [{"docid": "doc-en-kubernetes-91422af253157e56510335693740251e17b7c26d119e77363e85ed4155980546", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: What happened: fsgroup is only intended for RWO volumes because it recursively changes the permissions of all the directories in the volume. This can cause problems for nfs-type volumes because multiple pods could access the same volume and have the permissions changed out from underneath. What you expected to happen: Determine whether or not the plugin supports fsgroup either via: access mode. This is still a bit ambiguous for nfs volume types, that can theoretically support rwo, especially since Kubernetes does not do any sort of access mode enforcement. a new csi capability\nCC\nAre you saying that CSI internal driver should check driver capability for RWO, if supported, only then apply value ? What would the be ?\nYes one possible way is to infer fsgroup is supported for all rwo volumes, which may not be true? Like a nfs volume technically supports rwo but not fsgroup. So the other option is to make it a new CSI capability. I'm not sure exactly sure how best to describe it though, maybe something about volume ownership management.\nWill it work if is not set then don't chown the ownership? I would think that for shared file system types(nfs, glusterfs) - won't be set. For raw block storage too - I think we shouldn't have to do this.\nwhat do you mean by ? Shouldnt have to solve this issue ?\nI meant - which is obvious. I just meant that the entire mechanism of changing ownership of files should apply only to volume types with block storage filesystems. I am just wondering if we can get away with detecting fsType and not have to introduce new capability in CSI.\nagreed, do not map well to current csi.Capabilities enums which makes it hard to determine RWO when mounting. Perhaps, instead of a new capability, we revisit the existing capabilities to see if there are any way RWO can be reliably inferred from returned capabilities.", "commid": "kubernetes_issue_66323", "tokennum": 463}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7d6ada37844e18cfa384fde5e4d5d2d0a97871e672ed27ef05bf9cccea5ecc9a", "query": "return nil } <ins> // applyFSGroup applies the volume ownership it derives its logic // from https://github.com/kubernetes/kubernetes/issues/66323 // 1) if fstype is \"\", then skip fsgroup (could be indication of non-block filesystem) // 2) if fstype is provided and pv.AccessMode == ReadWriteOnly and !c.spec.ReadOnly then apply fsgroup func (c *csiMountMgr) applyFSGroup(fsType string, fsGroup *int64) error { if fsGroup != nil { if fsType == \"\" { glog.V(4).Info(log(\"mounter.SetupAt WARNING: skipping fsGroup, fsType not provided\")) return nil } accessModes := c.spec.PersistentVolume.Spec.AccessModes if c.spec.PersistentVolume.Spec.AccessModes == nil { glog.V(4).Info(log(\"mounter.SetupAt WARNING: skipping fsGroup, access modes not provided\")) return nil } if !hasReadWriteOnce(accessModes) { glog.V(4).Info(log(\"mounter.SetupAt WARNING: skipping fsGroup, only support ReadWriteOnce access mode\")) return nil } if c.readOnly { glog.V(4).Info(log(\"mounter.SetupAt WARNING: skipping fsGroup, volume is readOnly\")) return nil } err := volume.SetVolumeOwnership(c, fsGroup) if err != nil { return err } glog.V(4).Info(log(\"mounter.SetupAt fsGroup [%d] applied successfully to %s\", *fsGroup, c.volumeID)) } return nil } </ins> // isDirMounted returns the !notMounted result from IsLikelyNotMountPoint check func isDirMounted(plug *csiPlugin, dir string) (bool, error) { mounter := plug.host.GetMounter(plug.GetPluginName())", "positive_passages": [{"docid": "doc-en-kubernetes-e4259f265013a5d1d3262148ae5650fa802161db5ab8c8ccc1d210e68217a7fd", "text": "Currently, this is what the code is doing which we knew needed to be revisited:\nUsers may not fully understand what fsgroup is and set it anyway, or a default psp with some fsgroup may be defined in which it will automatically be set on all pods. The first case we can attribute to user error, but the second case may not have a good workaround and could cause permission issues on rwx volumes. So I think we do need to solve this.\nYes, agreed this has to be solved. As you pointed out user error or improperly configured PSP can set value that does not match the correct attribute, causing permission issues. Here is what I think can be done without new CSI capabilities: , then do not apply fsgroup then: , apply fsgroup , do not apply fsgroup to void stated issue then: , apply fsgroup I think that may help deduce when to apply fsgroup.\nIf mount reference count <= 1, apply fsgroup If mount reference count 1, do not apply fsgroup to void stated issue A RWM volume (say NFS) can be mounted on multiple nodes. Do you have reliable count of mounts across all nodes?\nIn addition, that would be a change in semantics to how we support rwx volumes today. If we don't have a new CSI capability, then I think the best course of action is to only apply fsgroup for RWO volumes. Some questions remain: Do all RWO volumes support fsgroup? RWX is a superset of RWO. So if a user requests a RWO volume, it could still be satisfied by a RWX volume type. Can we detect this and still not apply the fsgroup even though the volume capability will say RWO?\nIf there's not a reliable way to enumerate node mounts (thinking about it, for CSI external drivers, the answer is NO). Theres is no reliable way to have k8s autocorrect a bad fsgroup/PV.AccessMode combo. So we would have to rely on the config provided by user/admin. I have come to similar conclusion as -- mainly, apply fsgroup only to volumes with access modes. The other k8s specified access modes, , cannot be reliably applied.", "commid": "kubernetes_issue_66323", "tokennum": 487}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7d6ada37844e18cfa384fde5e4d5d2d0a97871e672ed27ef05bf9cccea5ecc9a", "query": "return nil } <ins> // applyFSGroup applies the volume ownership it derives its logic // from https://github.com/kubernetes/kubernetes/issues/66323 // 1) if fstype is \"\", then skip fsgroup (could be indication of non-block filesystem) // 2) if fstype is provided and pv.AccessMode == ReadWriteOnly and !c.spec.ReadOnly then apply fsgroup func (c *csiMountMgr) applyFSGroup(fsType string, fsGroup *int64) error { if fsGroup != nil { if fsType == \"\" { glog.V(4).Info(log(\"mounter.SetupAt WARNING: skipping fsGroup, fsType not provided\")) return nil } accessModes := c.spec.PersistentVolume.Spec.AccessModes if c.spec.PersistentVolume.Spec.AccessModes == nil { glog.V(4).Info(log(\"mounter.SetupAt WARNING: skipping fsGroup, access modes not provided\")) return nil } if !hasReadWriteOnce(accessModes) { glog.V(4).Info(log(\"mounter.SetupAt WARNING: skipping fsGroup, only support ReadWriteOnce access mode\")) return nil } if c.readOnly { glog.V(4).Info(log(\"mounter.SetupAt WARNING: skipping fsGroup, volume is readOnly\")) return nil } err := volume.SetVolumeOwnership(c, fsGroup) if err != nil { return err } glog.V(4).Info(log(\"mounter.SetupAt fsGroup [%d] applied successfully to %s\", *fsGroup, c.volumeID)) } return nil } </ins> // isDirMounted returns the !notMounted result from IsLikelyNotMountPoint check func isDirMounted(plug *csiPlugin, dir string) (bool, error) { mounter := plug.host.GetMounter(plug.GetPluginName())", "positive_passages": [{"docid": "doc-en-kubernetes-d8c35fcb948670df81783d48737c49dba78eee3bd98e80f83b95ce53a92518be", "text": "Even if we were to introduce additional plugin capabilities that the CO can query (from driver) to find out what modes can be applied, there would still be the possibility of user/admin mis-configuration. Probably not, Is this where you think an additional capability would help ( ) That is a good point. Can't think of a way to detect/guess RWX when RWO is specified, this without the driver providing that info. Can we adopt the rule until we decide what capabilities would look like ?\nI will just try to summarize the conversation from Slack. We can safely assume that only applies to block storage type with file system on top of it. So for all - volumes that need to have called MUST have a file system() on them. Is that assumption correct? If it is - can we not use presence of field or we can query the local volume for fs type (like how we query selinux relabelling capability) and call only when - volume is RW and has a valid block storage file system type. Will this not solve our use case? EDIT: renamed to .\nWe'll need to make it clear that is only for block-based storage systems, and the field cannot be reused for some multi-protocol file server (ie, nfsv3, nfsv4, smb, etc). For that case, then the plugin will need to expose its own new storageclass parameter + volume attribute to specify protocol.\nCan we not use to get fsType - and use that information for calling ? It may be problematic to rely entirely on present inside csi source.\nthe only problem with is that in CSI volume info is intentionally opaque to the CSI code inside k8s. All mount logic is delegated to the driver.\nInstead of a new capability or trying to deduce how best to apply fsgroup, why not pass the to the driver and let it decide how to apply it (either as a attribute for the mount or top level request param)? Right now, all mount logic has been delegated to the external CSI driver except for applying permission. Thoughts ?\nthat is true but we can still inspect file system on the mounted path because by the time gets called volume is already mounted. This should be no different than how selinux support is determined. what you think?\nis this approved for 1.12 milestone? Thank you for working on this,\nstill discussing how best to approach this.", "commid": "kubernetes_issue_66323", "tokennum": 506}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7d6ada37844e18cfa384fde5e4d5d2d0a97871e672ed27ef05bf9cccea5ecc9a", "query": "return nil } <ins> // applyFSGroup applies the volume ownership it derives its logic // from https://github.com/kubernetes/kubernetes/issues/66323 // 1) if fstype is \"\", then skip fsgroup (could be indication of non-block filesystem) // 2) if fstype is provided and pv.AccessMode == ReadWriteOnly and !c.spec.ReadOnly then apply fsgroup func (c *csiMountMgr) applyFSGroup(fsType string, fsGroup *int64) error { if fsGroup != nil { if fsType == \"\" { glog.V(4).Info(log(\"mounter.SetupAt WARNING: skipping fsGroup, fsType not provided\")) return nil } accessModes := c.spec.PersistentVolume.Spec.AccessModes if c.spec.PersistentVolume.Spec.AccessModes == nil { glog.V(4).Info(log(\"mounter.SetupAt WARNING: skipping fsGroup, access modes not provided\")) return nil } if !hasReadWriteOnce(accessModes) { glog.V(4).Info(log(\"mounter.SetupAt WARNING: skipping fsGroup, only support ReadWriteOnce access mode\")) return nil } if c.readOnly { glog.V(4).Info(log(\"mounter.SetupAt WARNING: skipping fsGroup, volume is readOnly\")) return nil } err := volume.SetVolumeOwnership(c, fsGroup) if err != nil { return err } glog.V(4).Info(log(\"mounter.SetupAt fsGroup [%d] applied successfully to %s\", *fsGroup, c.volumeID)) } return nil } </ins> // isDirMounted returns the !notMounted result from IsLikelyNotMountPoint check func isDirMounted(plug *csiPlugin, dir string) (bool, error) { mounter := plug.host.GetMounter(plug.GetPluginName())", "positive_passages": [{"docid": "doc-en-kubernetes-5cbdf2214fb613203f89164533ba44fdfe78b2afafa2ed81aceb81e111086f6f", "text": "It would be a 1.12.\n[MILESTONENOTIFIER] Milestone Issue: Up-to-date for process <details open<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Never automatically move issue out of a release milestone; continually escalate to contributor and SIG through all available channels. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details\nApproved for 1.12\nBased on previous post, this is a summary: If then is not applied (because it could be an indication of a nonblock fs, or error) Done is provided if fstype is invalid Done if fstype is valid and then apply fsgroup logic else ignore fsGroup Done\n- any updates on ?\nWaiting for a review and approval.\nyou have a outstanding comment on the PR. Can you please answer that?\nHow does this approach relate to inline CSI volumes? There's no PersistentVolume involved, and hence no way to specify an access mode. , but my driver ignores it (always using tmpfs). I considered having my CSI driver read the mounting pod's spec to see if it has a security context with \"fsGroup\" set, since that detail is not supplied to the driver, as . My goal is to have the volume mounted with the files on it readable by the container's user, but there's no way for my driver to know who that user will be. Am I supposed to just use 0444 for the ownership bits, to allow everyone to read the files?", "commid": "kubernetes_issue_66323", "tokennum": 377}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7d6d311b7b3da3f4bd87d16b449086a94ec3bee04b86c15833ef770b4ee759aa", "query": "resources: {} terminationMessagePath: \"/dev/termination-log\" imagePullPolicy: IfNotPresent <del> capabilities: {} </del> securityContext: capabilities: {} privileged: false", "positive_passages": [{"docid": "doc-en-kubernetes-970debf69dc4e7e663c051298279ebf93b58654f6c393d8683796c73cb4f1c74", "text": "Kubernetes version (use ): Environment: Cloud provider or hardware configuration: Vagrant OS (e.g. from /etc/os-release): CoreOS Kernel (e.g. ):Install tools: Vagrant & Others: What happened: What you expected to happen: Success How to reproduce it (as minimally and precisely as possible): Followed instructions at Tried to run Received: Anything else do we need to know: From googling, it seems several of the fields in the config are for when using OpenShift origin. But creating the replication controller is a prerequisite to launching OpenShift Origin. Chicken & egg problem.", "commid": "kubernetes_issue_39575", "tokennum": 138}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7d72136beb552b5f5f010017cde9e8d9fa345450796075e2a7735feac96f7cb7", "query": "} } if len(unknownLabels) > 0 { <del> // TODO(liggitt): in 1.16, return an error klog.Warningf(\"unknown 'kubernetes.io' or 'k8s.io' labels specified with --node-labels: %v\", unknownLabels.List()) klog.Warningf(\"in 1.16, --node-labels in the 'kubernetes.io' namespace must begin with an allowed prefix (%s) or be in the specifically allowed set (%s)\", strings.Join(kubeletapis.KubeletLabelNamespaces(), \", \"), strings.Join(kubeletapis.KubeletLabels(), \", \")) </del> <ins> return fmt.Errorf(\"unknown 'kubernetes.io' or 'k8s.io' labels specified with --node-labels: %vn--node-labels in the 'kubernetes.io' namespace must begin with an allowed prefix (%s) or be in the specifically allowed set (%s)\", unknownLabels.List(), strings.Join(kubeletapis.KubeletLabelNamespaces(), \", \"), strings.Join(kubeletapis.KubeletLabels(), \", \")) </ins> } return nil", "positive_passages": [{"docid": "doc-en-kubernetes-2c9ef8984ebaf899659836b925069334113c910fc47ebe0516a7d659674f044a", "text": "xref In 1.16: change the metadata-proxy addon to use change the kube-proxy addon to use change the masq-agent addon to use stop setting , , and in kube-up\nHey I'm trying to start to contribute to kubernetes and this seem to be an easy task. Can I help with this one?", "commid": "kubernetes_issue_75050", "tokennum": 77}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7d976756582ec9b042d01c3f733544ef13fe65befeedeea3789f5b6b10869fad", "query": "reference, target, current, <del> minPods, </del> <ins> *minPods, </ins> maxPods, translateTimestamp(hpa.CreationTimestamp), ); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-c565e19bceebcf0dd9ac2effd9df046efbfbf8278a160afc85d83d70045c5f06", "text": "returns It's because we recently change HorizontalPodAutoscalerSpec.MinReplicas from int to *int.", "commid": "kubernetes_issue_15898", "tokennum": 28}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7dd85160b83d21cae33220ad6353d3e0934b5180d04692b3bac86e98489b6ac8", "query": "ginkgo.By(\"updating the pod\") podClient.Update(pod.ObjectMeta.Name, func(pod *v1.Pod) { <del> pod.ObjectMeta.Annotations = map[string]string{\"mysubpath\": \"mypath\"} </del> <ins> if pod.ObjectMeta.Annotations == nil { pod.ObjectMeta.Annotations = make(map[string]string) } pod.ObjectMeta.Annotations[\"mysubpath\"] = \"mypath\" </ins> }) ginkgo.By(\"waiting for pod running\")", "positive_passages": [{"docid": "doc-en-kubernetes-07ac40315577ee77e8734022e934cb4c363bc3e85cf45880c776268568485961", "text": "In our Tanzu Supervisor Cluster k8s setup, we observe that the \"should verify that a failing subpath expansion can be modified during the lifecycle of a container\" conformance test fails. The root-cause seems to be that the test is updating the pod annotations, thereby resulting in removing the other annotations present in the pod object. Removing the custom annotations that we use causes the test to fail during pod deletion. Should this test perhaps use Patch instead of Update so that the annotations are merged and not replaced? Thanks ginkgo.By(\"updating the pod\") podClient.Update(pod.ObjectMeta.Name, func(pod *v1.Pod) { pod.ObjectMeta.Annotations = map[string]string{\"mysubpath\": \"mypath\"} })\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig storage /sig conformance I personally agree that it should not remove existing annotations, but better ask the test owners\nThe label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : /sig storage /sig conformance I personally agree that it should not remove existing annotations, but better ask the test owners 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\nMay I request the original author to weigh in on this? Thank you.\nI dont have any issues with the code change to a merge but what would bother me is that conformance tests are being altered by outside influences which doesnt seem particularly right. I think this would be for the sig storage owners to decide\nIssues 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", "commid": "kubernetes_issue_98537", "tokennum": 508}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7e2760fa517c288f288f08e535414e3e53a7287ed7a82fd6e97ed18568c4daa3", "query": "return fmt.Errorf(\"unimplemented\") } <del> func (f *fakeVMSet) GetDiskLun(diskName, diskURI string, nodeName types.NodeName) (int32, error) { return -1, fmt.Errorf(\"unimplemented\") } func (f *fakeVMSet) GetNextDiskLun(nodeName types.NodeName) (int32, error) { return -1, fmt.Errorf(\"unimplemented\") } func (f *fakeVMSet) DisksAreAttached(diskNames []string, nodeName types.NodeName) (map[string]bool, error) { </del> <ins> func (f *fakeVMSet) GetDataDisks(nodeName types.NodeName) ([]compute.DataDisk, error) { </ins> return nil, fmt.Errorf(\"unimplemented\") }", "positive_passages": [{"docid": "doc-en-kubernetes-6cfc50824280daf2f66f5e84f9a8c720c316cfa724f1e90fa02f306c798e5010", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind cleanup What happened: VirtualMachineScaleSetVM and VirtualMachine are different data structures (because of different API versions), so the disk attach operation seems duplicate between vm and vmss. That means although disk operations are in same logic, some duplication are still required now. They should use same api version in the future and should be merged into same code base, e.g. move sharing logic to Refer What you expected to happen: vmss and vm disk operations should share same code logic. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\nI have checked with currently we can\u2019t merge, e.g. following two structs are different since they using different sdk-for-azure versions. While in the end when sdk-for-azure version is upgraded, above two versions should be same and at that time, we should merge functions like \u2018AttachDisk\u2019, \u2018DetachDiskByName\u2019, 'GetDiskLun', GetNextDiskLun, DisksAreAttached", "commid": "kubernetes_issue_59736", "tokennum": 313}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7e2c0253993eaa3db9ade0ba1d744ff780b65829006d75923c0afd95c19b1d77", "query": "exec, syncPeriod, minSyncPeriod, filterCIDRs(true, excludeCIDRs), strictARP, tcpTimeout, tcpFinTimeout, udpTimeout, masqueradeAll, masqueradeBit, localDetectors[1], hostname, nodeIP[1], <del> nil, nil, scheduler, nodePortAddresses, kernelHandler) </del> <ins> nil, nil, scheduler, nodePortAddresses6, kernelHandler) </ins> if err != nil { return nil, fmt.Errorf(\"unable to create ipv6 proxier: %v\", err) }", "positive_passages": [{"docid": "doc-en-kubernetes-10e0800334eabc101ba3e719bde6addc76496fd00734e09bb571fcc5b6be7d48", "text": "What happened: In a dual-stack cluster when specifying both ipv6 and ipv4 addresses in the entries are inserted in ipvs for the ipv6 nodeports but with an invalid ipv4 address; The example shows the ipv4 loopback address but any ipv4 address in will cause a faulty entry. What you expected to happen: No ipv4 entry shall be inserted for the ipv6 nodeport. How to reproduce it (as minimally and precisely as possible): Configure with both ipv4 and ipv6 addresses Bring up a dual-stack cluster with proxy-mode Create a service with ipFamily:IPv6 Do Anything else we need to know?: Proxy-mode=iptables seems to work. With no ipv4 entries are inserted for ipv6 nodeports. In it is recommended to use but doing so makes kube-proxy enter rules for address (in addition to \"127.0.0.1\"). While these entries cause no harm they can't be used and should not be there. These entries are created for both proxy-mode \"iptables\" and \"ipvs\". This should not be handled in this issue but in another (new) issue if needed. Example; Environment: Kubernetes version (use ):Cloud provider or hardware configuration: Kvm's on Ubuntu OS (e.g: ): xcluster Kernel (e.g. ):Install tools: \"from scratch\" Network plugin and version (if this is a network-related bug): calico/cni:v3.12.0 Others: /sig network\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/area ipvs /area ipv6\n/remove-triage unresolved /assign I take this myself if no one objects.\nThe ipv4 address is obviously a ipv4-converted ipv6 from .\nAccording to the code here (), we may need to filter the before passing it to .\nLooks that that's it. Please go ahead and make a PR, or I can do it if you prefer. I will help test the PR of course. Here are some review comments right away; Use v1.IPFamily as param to the filter function rather than The filter function seem usable and generic and may be placed in some \"util\" package, but leave it as-is and let the maintainers decide that.\nHi feel free to send a PR please, as you have took this already :) I'd like to help review it!\nThe \"addresses\" are really CIDRs which make the fix even simpler.", "commid": "kubernetes_issue_89923", "tokennum": 576}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7e532ba6e9001a608e002b2a34b8b480391799e7918ccdccbe41e2c2c4424e22", "query": "frameworkruntime.WithCaptureProfile(frameworkruntime.CaptureProfile(c.frameworkCapturer)), frameworkruntime.WithClusterEventMap(c.clusterEventMap), frameworkruntime.WithParallelism(int(c.parallellism)), <ins> frameworkruntime.WithExtenders(extenders), </ins> ) if err != nil { return nil, fmt.Errorf(\"initializing profiles: %v\", err)", "positive_passages": [{"docid": "doc-en-kubernetes-75719ce40debdc24665e0bd0c466c638c232f756949a78511459bd94dde06b58", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --here is supposed to be set through , but is not called from anywhere except tests, so always returns . should be set through here. Am I missing something? N/A None Kubernetes version (use ): master () Cloud provider or hardware configuration: N/A OS (e.g: ): N/A Kernel (e.g. ): N/A Install tools: N/A Network plugin and version (if this is a network-related bug): N/A Others: None\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scheduling\nThanks for pointing that out. The plumbing of extenders to the framework impact calling extenders on preemption. That seems to be a path not covered by tests end to end. Can you submit a PR to fix this? as you mentioned we need to pass the extenders on profile creation. We need to patch the fix back to v1.21 and v1.20 (the release where this was refactored). /cc\nI have submitted a PR for a fix.", "commid": "kubernetes_issue_102971", "tokennum": 348}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7e69036018d565269b8b8f9641b0928f433fd8744aa2f7b91f337bcfb173311f", "query": "v1 \"k8s.io/api/core/v1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" <del> \"k8s.io/apimachinery/pkg/util/sets\" </del> \"k8s.io/apimachinery/pkg/util/uuid\" \"k8s.io/kubernetes/pkg/kubelet/events\" \"k8s.io/kubernetes/test/e2e/framework\"", "positive_passages": [{"docid": "doc-en-kubernetes-b8a3e3a5c22dc8491069aa612d226f113bfee5a5c0b17ff9cb35a90b4b6a10ba", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: , Which test(s) are failing: Since when has it been failing: since this PR introduced them Testgrid link: Note that this is the flakiest test in both dashboards, and failing quite frequently. Reason for failure: unknown Anything else we need to know: cc\n/sig node\nsee: , both getting empty PID and multiple PIDs.\nopened revert at\nfor discoverability for the release team /priority critical-urgent /milestone v1.17", "commid": "kubernetes_issue_84209", "tokennum": 127}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7eb5d61e07fff3a861dbc33f65dd69e7cadd89d166c82c5d550e5461926538c7", "query": "AllNamespaces bool // true iff the action is namespaced but works on aggregate result for all namespaces } <ins> // An interface to see if one storage supports override its default verb for monitoring type StorageMetricsOverride interface { // OverrideMetricsVerb gives a storage object an opportunity to override the verb reported to the metrics endpoint OverrideMetricsVerb(oldVerb string) (newVerb string) } </ins> // An interface to see if an object supports swagger documentation as a method type documentable interface { SwaggerDoc() map[string]string", "positive_passages": [{"docid": "doc-en-kubernetes-818250efc38f3e1e4f69f5ba9f53826c59d17d9aa3970f389bfaed5f09e5cc10", "text": "Is this a BUG REPORT or FEATURE REQUEST?: What happened: use kubectl search log with follow option get api latency (apiserverrequestlatenciessummary{quantile=\"0.99\",resource=\"pods\",verb=\"GET\"} )high to give a alert in my cluster. the apiserver log is below and we can see it costs 1m25s. What you expected to happen: do not make this api latency account in getting pod request api latency How to reproduce it (as minimally and precisely as possible): use kubectl to search a pod log with follow option long enough and you will get this metric apiserverrequestlatenciessummary{quantile=\"0.99\",resource=\"pods\",verb=\"GET\"} higher than the ordinary case. Anything else we need to know?: I am happy to fix it. Environment: Kubernetes version (use ): 1.6 Cloud provider or hardware configuration**: bare-metal OS (e.g. from /etc/os-release): ubuntu 16.04 Kernel (e.g. ): 4.4 Install tools: kubeadm Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig API Machinery\n/area apiserver\n/sig api-machinery\n/assign Thanks... looking forward to your PR!\nfixed with PTAL", "commid": "kubernetes_issue_49998", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7ebbd102419530e60005cf245cda13a58d04197bff1900153214ec8d3e1fd89c", "query": "_, err = f.ClientSet.CoreV1().Endpoints(testNamespaceName).Get(context.TODO(), testEndpointName, metav1.GetOptions{}) framework.ExpectError(err, \"should not be able to fetch Endpoint\") }) <ins> ginkgo.It(\"should complete a service status lifecycle\", func() { ns := f.Namespace.Name svcResource := schema.GroupVersionResource{Group: \"\", Version: \"v1\", Resource: \"services\"} svcClient := f.ClientSet.CoreV1().Services(ns) testSvcName := \"test-service-\" + utilrand.String(5) testSvcLabels := map[string]string{\"test-service-static\": \"true\"} testSvcLabelsFlat := \"test-service-static=true\" w := &cache.ListWatch{ WatchFunc: func(options metav1.ListOptions) (watch.Interface, error) { options.LabelSelector = testSvcLabelsFlat return cs.CoreV1().Services(ns).Watch(context.TODO(), options) }, } svcList, err := cs.CoreV1().Services(\"\").List(context.TODO(), metav1.ListOptions{LabelSelector: testSvcLabelsFlat}) framework.ExpectNoError(err, \"failed to list Services\") ginkgo.By(\"creating a Service\") testService := v1.Service{ ObjectMeta: metav1.ObjectMeta{ Name:   testSvcName, Labels: testSvcLabels, }, Spec: v1.ServiceSpec{ Type: \"ClusterIP\", Ports: []v1.ServicePort{{ Name:       \"http\", Protocol:   v1.ProtocolTCP, Port:       int32(80), TargetPort: intstr.FromInt(80), }}, }, } _, err = cs.CoreV1().Services(ns).Create(context.TODO(), &testService, metav1.CreateOptions{}) framework.ExpectNoError(err, \"failed to create Service\") ginkgo.By(\"watching for the Service to be added\") ctx, cancel := context.WithTimeout(context.Background(), svcReadyTimeout) defer cancel() _, err = watchtools.Until(ctx, svcList.ResourceVersion, w, func(event watch.Event) (bool, error) { if svc, ok := event.Object.(*v1.Service); ok { found := svc.ObjectMeta.Name == testService.ObjectMeta.Name && svc.ObjectMeta.Namespace == ns && svc.Labels[\"test-service-static\"] == \"true\" if !found { framework.Logf(\"observed Service %v in namespace %v with labels: %v & ports %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Labels, svc.Spec.Ports) return false, nil } framework.Logf(\"Found Service %v in namespace %v with labels: %v & ports %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Labels, svc.Spec.Ports) return found, nil } framework.Logf(\"Observed event: %+v\", event.Object) return false, nil }) framework.ExpectNoError(err, \"Failed to locate Service %v in namespace %v\", testService.ObjectMeta.Name, ns) framework.Logf(\"Service %s created\", testSvcName) ginkgo.By(\"Getting /status\") svcStatusUnstructured, err := f.DynamicClient.Resource(svcResource).Namespace(ns).Get(context.TODO(), testSvcName, metav1.GetOptions{}, \"status\") framework.ExpectNoError(err, \"Failed to fetch ServiceStatus of Service %s in namespace %s\", testSvcName, ns) svcStatusBytes, err := json.Marshal(svcStatusUnstructured) framework.ExpectNoError(err, \"Failed to marshal unstructured response. %v\", err) var svcStatus v1.Service err = json.Unmarshal(svcStatusBytes, &svcStatus) framework.ExpectNoError(err, \"Failed to unmarshal JSON bytes to a Service object type\") framework.Logf(\"Service %s has LoadBalancer: %v\", testSvcName, svcStatus.Status.LoadBalancer) ginkgo.By(\"patching the ServiceStatus\") lbStatus := v1.LoadBalancerStatus{ Ingress: []v1.LoadBalancerIngress{{IP: \"203.0.113.1\"}}, } lbStatusJSON, err := json.Marshal(lbStatus) framework.ExpectNoError(err, \"Failed to marshal JSON. %v\", err) _, err = svcClient.Patch(context.TODO(), testSvcName, types.MergePatchType, []byte(`{\"metadata\":{\"annotations\":{\"patchedstatus\":\"true\"}},\"status\":{\"loadBalancer\":`+string(lbStatusJSON)+`}}`), metav1.PatchOptions{}, \"status\") framework.ExpectNoError(err, \"Could not patch service status\", err) ginkgo.By(\"watching for the Service to be patched\") ctx, cancel = context.WithTimeout(context.Background(), svcReadyTimeout) defer cancel() _, err = watchtools.Until(ctx, svcList.ResourceVersion, w, func(event watch.Event) (bool, error) { if svc, ok := event.Object.(*v1.Service); ok { found := svc.ObjectMeta.Name == testService.ObjectMeta.Name && svc.ObjectMeta.Namespace == ns && svc.Annotations[\"patchedstatus\"] == \"true\" if !found { framework.Logf(\"observed Service %v in namespace %v with annotations: %v & LoadBalancer: %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Annotations, svc.Status.LoadBalancer) return false, nil } framework.Logf(\"Found Service %v in namespace %v with annotations: %v & LoadBalancer: %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Annotations, svc.Status.LoadBalancer) return found, nil } framework.Logf(\"Observed event: %+v\", event.Object) return false, nil }) framework.ExpectNoError(err, \"failed to locate Service %v in namespace %v\", testService.ObjectMeta.Name, ns) framework.Logf(\"Service %s has service status patched\", testSvcName) ginkgo.By(\"updating the ServiceStatus\") var statusToUpdate, updatedStatus *v1.Service err = retry.RetryOnConflict(retry.DefaultRetry, func() error { statusToUpdate, err = svcClient.Get(context.TODO(), testSvcName, metav1.GetOptions{}) framework.ExpectNoError(err, \"Unable to retrieve service %s\", testSvcName) statusToUpdate.Status.Conditions = append(statusToUpdate.Status.Conditions, metav1.Condition{ Type:    \"StatusUpdate\", Status:  metav1.ConditionTrue, Reason:  \"E2E\", Message: \"Set from e2e test\", }) updatedStatus, err = svcClient.UpdateStatus(context.TODO(), statusToUpdate, metav1.UpdateOptions{}) return err }) framework.ExpectNoError(err, \"nn Failed to UpdateStatus. %vnn\", err) framework.Logf(\"updatedStatus.Conditions: %#v\", updatedStatus.Status.Conditions) ginkgo.By(\"watching for the Service to be updated\") ctx, cancel = context.WithTimeout(context.Background(), svcReadyTimeout) defer cancel() _, err = watchtools.Until(ctx, svcList.ResourceVersion, w, func(event watch.Event) (bool, error) { if svc, ok := event.Object.(*v1.Service); ok { found := svc.ObjectMeta.Name == testService.ObjectMeta.Name && svc.ObjectMeta.Namespace == ns && svc.Annotations[\"patchedstatus\"] == \"true\" if !found { framework.Logf(\"Observed Service %v in namespace %v with annotations: %v & Conditions: %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Annotations, svc.Status.LoadBalancer) return false, nil } for _, cond := range svc.Status.Conditions { if cond.Type == \"StatusUpdate\" && cond.Reason == \"E2E\" && cond.Message == \"Set from e2e test\" { framework.Logf(\"Found Service %v in namespace %v with annotations: %v & Conditions: %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Annotations, svc.Status.Conditions) return found, nil } else { framework.Logf(\"Observed Service %v in namespace %v with annotations: %v & Conditions: %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Annotations, svc.Status.LoadBalancer) return false, nil } } } framework.Logf(\"Observed event: %+v\", event.Object) return false, nil }) framework.ExpectNoError(err, \"failed to locate Service %v in namespace %v\", testService.ObjectMeta.Name, ns) framework.Logf(\"Service %s has service status updated\", testSvcName) ginkgo.By(\"patching the service\") servicePatchPayload, err := json.Marshal(v1.Service{ ObjectMeta: metav1.ObjectMeta{ Labels: map[string]string{ \"test-service\": \"patched\", }, }, }) _, err = svcClient.Patch(context.TODO(), testSvcName, types.StrategicMergePatchType, []byte(servicePatchPayload), metav1.PatchOptions{}) framework.ExpectNoError(err, \"failed to patch service. %v\", err) ginkgo.By(\"watching for the Service to be patched\") ctx, cancel = context.WithTimeout(context.Background(), svcReadyTimeout) defer cancel() _, err = watchtools.Until(ctx, svcList.ResourceVersion, w, func(event watch.Event) (bool, error) { if svc, ok := event.Object.(*v1.Service); ok { found := svc.ObjectMeta.Name == testService.ObjectMeta.Name && svc.ObjectMeta.Namespace == ns && svc.Labels[\"test-service\"] == \"patched\" if !found { framework.Logf(\"observed Service %v in namespace %v with labels: %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Labels) return false, nil } framework.Logf(\"Found Service %v in namespace %v with labels: %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Labels) return found, nil } framework.Logf(\"Observed event: %+v\", event.Object) return false, nil }) framework.ExpectNoError(err, \"failed to locate Service %v in namespace %v\", testService.ObjectMeta.Name, ns) framework.Logf(\"Service %s patched\", testSvcName) ginkgo.By(\"deleting the service\") err = cs.CoreV1().Services(ns).Delete(context.TODO(), testSvcName, metav1.DeleteOptions{}) framework.ExpectNoError(err, \"failed to delete the Service. %v\", err) ginkgo.By(\"watching for the Service to be deleted\") ctx, cancel = context.WithTimeout(context.Background(), svcReadyTimeout) defer cancel() _, err = watchtools.Until(ctx, svcList.ResourceVersion, w, func(event watch.Event) (bool, error) { switch event.Type { case watch.Deleted: if svc, ok := event.Object.(*v1.Service); ok { found := svc.ObjectMeta.Name == testService.ObjectMeta.Name && svc.ObjectMeta.Namespace == ns && svc.Labels[\"test-service-static\"] == \"true\" if !found { framework.Logf(\"observed Service %v in namespace %v with labels: %v & annotations: %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Labels, svc.Annotations) return false, nil } framework.Logf(\"Found Service %v in namespace %v with labels: %v & annotations: %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Labels, svc.Annotations) return found, nil } default: framework.Logf(\"Observed event: %+v\", event.Type) } return false, nil }) framework.ExpectNoError(err, \"failed to delete Service %v in namespace %v\", testService.ObjectMeta.Name, ns) framework.Logf(\"Service %s deleted\", testSvcName) }) </ins> }) // execAffinityTestForSessionAffinityTimeout is a helper function that wrap the logic of", "positive_passages": [{"docid": "doc-en-kubernetes-c5b2d72b2e785256d7a2577807fdbd43ef000a4da594f69c949ac55e4186d114", "text": "[x] two weeks soak end date : 18 March 2021 According to this APIsnoop query, there are still some remaining RESOURCENAME endpoints which are untested. with this query you can filter untested endpoints by their category and eligiblity for conformance. e.g below shows a query to find all conformance eligible untested,stable,core endpoints Note: Community feedback for the e2e test has lead to a number of improvements including extending the test coverage to all outstanding endpoints listed above. As each endpoint is tested a &rsquo;watch&rsquo; confirms that the result is valid before testing the next endpoint. readCoreV1NamespacedServiceStatus (get /status) patchCoreV1NamespacedServiceStatus (patch /status) replaceCoreV1NamespacedServiceStatus (update /status) patchCoreV1NamespacedService Create a Service with a static label Patch the Service with a new label and updated data Get the Service to ensure it&rsquo;s patched Upate the Service with a new label and updated data Get the Service to ensure it&rsquo;s updated Delete Namespaced Service via a Collection with a LabelSelector This query by apisnoop shows that all outstanding endpoints as list at the start of this document have been hit by the e2e test. Note that the results do include other service endpoints that have been addressed in other conformance tests. If a test with these calls gets merged, test coverage will go up by 4 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance\nCan you please review the proposed test and advise if we could go ahead with a PR\n/assign\nIt looks like it's patching metadata and spec but not status?\nIssues 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\n/remove-lifecycle stale\nI've been retesting this mock test and apisnoop does log as been hit. From my testing below it looks like the patchStatus is working as expected or have I missed something?", "commid": "kubernetes_issue_94867", "tokennum": 517}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7ebbd102419530e60005cf245cda13a58d04197bff1900153214ec8d3e1fd89c", "query": "_, err = f.ClientSet.CoreV1().Endpoints(testNamespaceName).Get(context.TODO(), testEndpointName, metav1.GetOptions{}) framework.ExpectError(err, \"should not be able to fetch Endpoint\") }) <ins> ginkgo.It(\"should complete a service status lifecycle\", func() { ns := f.Namespace.Name svcResource := schema.GroupVersionResource{Group: \"\", Version: \"v1\", Resource: \"services\"} svcClient := f.ClientSet.CoreV1().Services(ns) testSvcName := \"test-service-\" + utilrand.String(5) testSvcLabels := map[string]string{\"test-service-static\": \"true\"} testSvcLabelsFlat := \"test-service-static=true\" w := &cache.ListWatch{ WatchFunc: func(options metav1.ListOptions) (watch.Interface, error) { options.LabelSelector = testSvcLabelsFlat return cs.CoreV1().Services(ns).Watch(context.TODO(), options) }, } svcList, err := cs.CoreV1().Services(\"\").List(context.TODO(), metav1.ListOptions{LabelSelector: testSvcLabelsFlat}) framework.ExpectNoError(err, \"failed to list Services\") ginkgo.By(\"creating a Service\") testService := v1.Service{ ObjectMeta: metav1.ObjectMeta{ Name:   testSvcName, Labels: testSvcLabels, }, Spec: v1.ServiceSpec{ Type: \"ClusterIP\", Ports: []v1.ServicePort{{ Name:       \"http\", Protocol:   v1.ProtocolTCP, Port:       int32(80), TargetPort: intstr.FromInt(80), }}, }, } _, err = cs.CoreV1().Services(ns).Create(context.TODO(), &testService, metav1.CreateOptions{}) framework.ExpectNoError(err, \"failed to create Service\") ginkgo.By(\"watching for the Service to be added\") ctx, cancel := context.WithTimeout(context.Background(), svcReadyTimeout) defer cancel() _, err = watchtools.Until(ctx, svcList.ResourceVersion, w, func(event watch.Event) (bool, error) { if svc, ok := event.Object.(*v1.Service); ok { found := svc.ObjectMeta.Name == testService.ObjectMeta.Name && svc.ObjectMeta.Namespace == ns && svc.Labels[\"test-service-static\"] == \"true\" if !found { framework.Logf(\"observed Service %v in namespace %v with labels: %v & ports %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Labels, svc.Spec.Ports) return false, nil } framework.Logf(\"Found Service %v in namespace %v with labels: %v & ports %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Labels, svc.Spec.Ports) return found, nil } framework.Logf(\"Observed event: %+v\", event.Object) return false, nil }) framework.ExpectNoError(err, \"Failed to locate Service %v in namespace %v\", testService.ObjectMeta.Name, ns) framework.Logf(\"Service %s created\", testSvcName) ginkgo.By(\"Getting /status\") svcStatusUnstructured, err := f.DynamicClient.Resource(svcResource).Namespace(ns).Get(context.TODO(), testSvcName, metav1.GetOptions{}, \"status\") framework.ExpectNoError(err, \"Failed to fetch ServiceStatus of Service %s in namespace %s\", testSvcName, ns) svcStatusBytes, err := json.Marshal(svcStatusUnstructured) framework.ExpectNoError(err, \"Failed to marshal unstructured response. %v\", err) var svcStatus v1.Service err = json.Unmarshal(svcStatusBytes, &svcStatus) framework.ExpectNoError(err, \"Failed to unmarshal JSON bytes to a Service object type\") framework.Logf(\"Service %s has LoadBalancer: %v\", testSvcName, svcStatus.Status.LoadBalancer) ginkgo.By(\"patching the ServiceStatus\") lbStatus := v1.LoadBalancerStatus{ Ingress: []v1.LoadBalancerIngress{{IP: \"203.0.113.1\"}}, } lbStatusJSON, err := json.Marshal(lbStatus) framework.ExpectNoError(err, \"Failed to marshal JSON. %v\", err) _, err = svcClient.Patch(context.TODO(), testSvcName, types.MergePatchType, []byte(`{\"metadata\":{\"annotations\":{\"patchedstatus\":\"true\"}},\"status\":{\"loadBalancer\":`+string(lbStatusJSON)+`}}`), metav1.PatchOptions{}, \"status\") framework.ExpectNoError(err, \"Could not patch service status\", err) ginkgo.By(\"watching for the Service to be patched\") ctx, cancel = context.WithTimeout(context.Background(), svcReadyTimeout) defer cancel() _, err = watchtools.Until(ctx, svcList.ResourceVersion, w, func(event watch.Event) (bool, error) { if svc, ok := event.Object.(*v1.Service); ok { found := svc.ObjectMeta.Name == testService.ObjectMeta.Name && svc.ObjectMeta.Namespace == ns && svc.Annotations[\"patchedstatus\"] == \"true\" if !found { framework.Logf(\"observed Service %v in namespace %v with annotations: %v & LoadBalancer: %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Annotations, svc.Status.LoadBalancer) return false, nil } framework.Logf(\"Found Service %v in namespace %v with annotations: %v & LoadBalancer: %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Annotations, svc.Status.LoadBalancer) return found, nil } framework.Logf(\"Observed event: %+v\", event.Object) return false, nil }) framework.ExpectNoError(err, \"failed to locate Service %v in namespace %v\", testService.ObjectMeta.Name, ns) framework.Logf(\"Service %s has service status patched\", testSvcName) ginkgo.By(\"updating the ServiceStatus\") var statusToUpdate, updatedStatus *v1.Service err = retry.RetryOnConflict(retry.DefaultRetry, func() error { statusToUpdate, err = svcClient.Get(context.TODO(), testSvcName, metav1.GetOptions{}) framework.ExpectNoError(err, \"Unable to retrieve service %s\", testSvcName) statusToUpdate.Status.Conditions = append(statusToUpdate.Status.Conditions, metav1.Condition{ Type:    \"StatusUpdate\", Status:  metav1.ConditionTrue, Reason:  \"E2E\", Message: \"Set from e2e test\", }) updatedStatus, err = svcClient.UpdateStatus(context.TODO(), statusToUpdate, metav1.UpdateOptions{}) return err }) framework.ExpectNoError(err, \"nn Failed to UpdateStatus. %vnn\", err) framework.Logf(\"updatedStatus.Conditions: %#v\", updatedStatus.Status.Conditions) ginkgo.By(\"watching for the Service to be updated\") ctx, cancel = context.WithTimeout(context.Background(), svcReadyTimeout) defer cancel() _, err = watchtools.Until(ctx, svcList.ResourceVersion, w, func(event watch.Event) (bool, error) { if svc, ok := event.Object.(*v1.Service); ok { found := svc.ObjectMeta.Name == testService.ObjectMeta.Name && svc.ObjectMeta.Namespace == ns && svc.Annotations[\"patchedstatus\"] == \"true\" if !found { framework.Logf(\"Observed Service %v in namespace %v with annotations: %v & Conditions: %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Annotations, svc.Status.LoadBalancer) return false, nil } for _, cond := range svc.Status.Conditions { if cond.Type == \"StatusUpdate\" && cond.Reason == \"E2E\" && cond.Message == \"Set from e2e test\" { framework.Logf(\"Found Service %v in namespace %v with annotations: %v & Conditions: %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Annotations, svc.Status.Conditions) return found, nil } else { framework.Logf(\"Observed Service %v in namespace %v with annotations: %v & Conditions: %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Annotations, svc.Status.LoadBalancer) return false, nil } } } framework.Logf(\"Observed event: %+v\", event.Object) return false, nil }) framework.ExpectNoError(err, \"failed to locate Service %v in namespace %v\", testService.ObjectMeta.Name, ns) framework.Logf(\"Service %s has service status updated\", testSvcName) ginkgo.By(\"patching the service\") servicePatchPayload, err := json.Marshal(v1.Service{ ObjectMeta: metav1.ObjectMeta{ Labels: map[string]string{ \"test-service\": \"patched\", }, }, }) _, err = svcClient.Patch(context.TODO(), testSvcName, types.StrategicMergePatchType, []byte(servicePatchPayload), metav1.PatchOptions{}) framework.ExpectNoError(err, \"failed to patch service. %v\", err) ginkgo.By(\"watching for the Service to be patched\") ctx, cancel = context.WithTimeout(context.Background(), svcReadyTimeout) defer cancel() _, err = watchtools.Until(ctx, svcList.ResourceVersion, w, func(event watch.Event) (bool, error) { if svc, ok := event.Object.(*v1.Service); ok { found := svc.ObjectMeta.Name == testService.ObjectMeta.Name && svc.ObjectMeta.Namespace == ns && svc.Labels[\"test-service\"] == \"patched\" if !found { framework.Logf(\"observed Service %v in namespace %v with labels: %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Labels) return false, nil } framework.Logf(\"Found Service %v in namespace %v with labels: %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Labels) return found, nil } framework.Logf(\"Observed event: %+v\", event.Object) return false, nil }) framework.ExpectNoError(err, \"failed to locate Service %v in namespace %v\", testService.ObjectMeta.Name, ns) framework.Logf(\"Service %s patched\", testSvcName) ginkgo.By(\"deleting the service\") err = cs.CoreV1().Services(ns).Delete(context.TODO(), testSvcName, metav1.DeleteOptions{}) framework.ExpectNoError(err, \"failed to delete the Service. %v\", err) ginkgo.By(\"watching for the Service to be deleted\") ctx, cancel = context.WithTimeout(context.Background(), svcReadyTimeout) defer cancel() _, err = watchtools.Until(ctx, svcList.ResourceVersion, w, func(event watch.Event) (bool, error) { switch event.Type { case watch.Deleted: if svc, ok := event.Object.(*v1.Service); ok { found := svc.ObjectMeta.Name == testService.ObjectMeta.Name && svc.ObjectMeta.Namespace == ns && svc.Labels[\"test-service-static\"] == \"true\" if !found { framework.Logf(\"observed Service %v in namespace %v with labels: %v & annotations: %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Labels, svc.Annotations) return false, nil } framework.Logf(\"Found Service %v in namespace %v with labels: %v & annotations: %v\", svc.ObjectMeta.Name, svc.ObjectMeta.Namespace, svc.Labels, svc.Annotations) return found, nil } default: framework.Logf(\"Observed event: %+v\", event.Type) } return false, nil }) framework.ExpectNoError(err, \"failed to delete Service %v in namespace %v\", testService.ObjectMeta.Name, ns) framework.Logf(\"Service %s deleted\", testSvcName) }) </ins> }) // execAffinityTestForSessionAffinityTimeout is a helper function that wrap the logic of", "positive_passages": [{"docid": "doc-en-kubernetes-6c98fb90bee2cd0d2fc404edc784deab934fddaa81022ed1883862c51f5dae6d", "text": "Using the following code before the patch request Gives this response Then after running the patch ServiceStatus Then running The response shows the patched changes.\nDuring the Conformance Meeting on 12th of January 2021, reviewed approach with Clayton, and we will start on the test PR this week!\n/reopen\nReopened this issue. <detailsIn response to : /reopen </details\n/triage accepted", "commid": "kubernetes_issue_94867", "tokennum": 79}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7ec6b90cf4579506937b150fae0a35994eb6a522a11624ddd377c002f149dfae", "query": "fi sudo -E \"${GO_OUT}/hyperkube\" kubelet ${priv_arg} <del> --enable-cri=false  </del> <ins> --enable-cri=\"${ENABLE_CRI}\"  </ins> --v=${LOG_LEVEL}  --chaos-chance=\"${CHAOS_CHANCE}\"  --container-runtime=\"${CONTAINER_RUNTIME}\" ", "positive_passages": [{"docid": "doc-en-kubernetes-6248148605ea242e531a4bb3c184ba4481934859726617f8259287d94988a4e9", "text": "When setting for other container runtime, won't start kubelet correctly because cri is disabled : Is there any reason of disabling cri at ? cc\nno, that wasn't supposed to go in. I was testing something and it slipped in accidentally. I'll open a PR to fix.\nAh I see your PR for it. Thanks!", "commid": "kubernetes_issue_42315", "tokennum": 75}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7ef257114cec1c2333e51bfc36e372afec659e258f7a2936d2f323d909ce2b0e", "query": "\"/readyz/shutdown\", } checkExpectedPathsAtRoot(server.URL, expectedPaths, t) <ins> // wait for health (max-in-flight-filter is initialized asynchronously, can take a few milliseconds to initialize) if err := wait.PollImmediate(100*time.Millisecond, wait.ForeverTestTimeout, func() (bool, error) { // healthz checks are installed in PrepareRun resp, err := http.Get(server.URL + \"/healthz?exclude=wrapping-health&exclude=delegate-health\") if err != nil { t.Fatal(err) } data, _ := ioutil.ReadAll(resp.Body) if http.StatusOK != resp.StatusCode { t.Logf(\"got %d\", resp.StatusCode) t.Log(string(data)) return false, nil } return true, nil }); err != nil { t.Fatal(err) } </ins> checkPath(server.URL+\"/healthz\", http.StatusInternalServerError, `[+]ping ok [+]log ok [-]wrapping-health failed: reason withheld", "positive_passages": [{"docid": "doc-en-kubernetes-00113afbb73b199bafe3ba83166412a7273f0dfa544fc7d4bd6466795076d1a7", "text": "<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI --Which jobs are flaking: bazel-test-master Which test(s) are flaking: gotest: Testgrid link: Reason for failure: Anything else we need to know: links to appreciated [Will update shortly] links to specific failures in spyglass appreciated <!-- Please see the deflaking doc () for more guidance! --/sig api-machinery\nThe label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : Which jobs are flaking: bazel-test-master Which test(s) are flaking: gotest: Testgrid link: Reason for failure: links to appreciatedlinks to specific failures in spyglass appreciated /sig api-machinary 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\n/sig api-machinery\n/assign /triage accepted\nFlaked twice ~2 weeks ago but now looking good: Since it's been relatively quiet, I'm going to go ahead and close this for now. /close\nClosing this issue. <detailsIn response to : Flaked twice ~2 weeks ago but now looking good: 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\n/reopen /assign I meet this test failure in And I can reproduce it with local stress testing. The reason is the same with\nReopened this issue. <detailsIn response to : /reopen /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", "commid": "kubernetes_issue_97312", "tokennum": 408}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7f1c4ae81bcfc19facc81332b323d5b418d0ba79b10f5d0e94c13a06c381a468", "query": "} } <ins> func verifyContainerStatuses(statuses []api.ContainerStatus, state, lastTerminationState map[string]api.ContainerState) error { for _, s := range statuses { if !reflect.DeepEqual(s.State, state[s.Name]) { return fmt.Errorf(\"unexpected state: %s\", diff.ObjectDiff(state[s.Name], s.State)) } if !reflect.DeepEqual(s.LastTerminationState, lastTerminationState[s.Name]) { return fmt.Errorf(\"unexpected last termination state %s\", diff.ObjectDiff( lastTerminationState[s.Name], s.LastTerminationState)) } } return nil } // Test generateAPIPodStatus with different reason cache and old api pod status. </ins> func TestGenerateAPIPodStatusWithReasonCache(t *testing.T) { // The following waiting reason and message  are generated in convertStatusToAPIStatus() startWaitingReason := \"ContainerCreating\" <ins> initWaitingReason := \"PodInitializing\" </ins> testTimestamp := time.Unix(123456789, 987654321) testErrorReason := fmt.Errorf(\"test-error\") emptyContainerID := (&kubecontainer.ContainerID{}).String() <del> verifyStatus := func(t *testing.T, c int, podStatus api.PodStatus, state, lastTerminationState map[string]api.ContainerState) { statuses := podStatus.ContainerStatuses for _, s := range statuses { if !reflect.DeepEqual(s.State, state[s.Name]) { t.Errorf(\"case #%d, unexpected state: %s\", c, diff.ObjectDiff(state[s.Name], s.State)) } if !reflect.DeepEqual(s.LastTerminationState, lastTerminationState[s.Name]) { t.Errorf(\"case #%d, unexpected last termination state %s\", c, diff.ObjectDiff( lastTerminationState[s.Name], s.LastTerminationState)) } } } </del> testKubelet := newTestKubelet(t) kubelet := testKubelet.kubelet pod := podWithUidNameNs(\"12345678\", \"foo\", \"new\")", "positive_passages": [{"docid": "doc-en-kubernetes-b4459e221a04f6723f7b97c6a9d43d61c0d65417b08d143223c7057699636055", "text": "is this a Node bug? cc as next oncall to follow up on this.\nThis is a node bug due to init containers\nI may need help debugging - I see:\nSo I think the problem is in the error case - we're not properly recording that the start failed, and the next time we come in we somehow think the first container succeeded. I'll add some debugging to see if we can't recreate it.\nLet's discuss on instead.", "commid": "kubernetes_issue_25879", "tokennum": 102}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7f1c4ae81bcfc19facc81332b323d5b418d0ba79b10f5d0e94c13a06c381a468", "query": "} } <ins> func verifyContainerStatuses(statuses []api.ContainerStatus, state, lastTerminationState map[string]api.ContainerState) error { for _, s := range statuses { if !reflect.DeepEqual(s.State, state[s.Name]) { return fmt.Errorf(\"unexpected state: %s\", diff.ObjectDiff(state[s.Name], s.State)) } if !reflect.DeepEqual(s.LastTerminationState, lastTerminationState[s.Name]) { return fmt.Errorf(\"unexpected last termination state %s\", diff.ObjectDiff( lastTerminationState[s.Name], s.LastTerminationState)) } } return nil } // Test generateAPIPodStatus with different reason cache and old api pod status. </ins> func TestGenerateAPIPodStatusWithReasonCache(t *testing.T) { // The following waiting reason and message  are generated in convertStatusToAPIStatus() startWaitingReason := \"ContainerCreating\" <ins> initWaitingReason := \"PodInitializing\" </ins> testTimestamp := time.Unix(123456789, 987654321) testErrorReason := fmt.Errorf(\"test-error\") emptyContainerID := (&kubecontainer.ContainerID{}).String() <del> verifyStatus := func(t *testing.T, c int, podStatus api.PodStatus, state, lastTerminationState map[string]api.ContainerState) { statuses := podStatus.ContainerStatuses for _, s := range statuses { if !reflect.DeepEqual(s.State, state[s.Name]) { t.Errorf(\"case #%d, unexpected state: %s\", c, diff.ObjectDiff(state[s.Name], s.State)) } if !reflect.DeepEqual(s.LastTerminationState, lastTerminationState[s.Name]) { t.Errorf(\"case #%d, unexpected last termination state %s\", c, diff.ObjectDiff( lastTerminationState[s.Name], s.LastTerminationState)) } } } </del> testKubelet := newTestKubelet(t) kubelet := testKubelet.kubelet pod := podWithUidNameNs(\"12345678\", \"foo\", \"new\")", "positive_passages": [{"docid": "doc-en-kubernetes-dcc88d1d89328d1da3366de828afcd8ab0373228cc4437ea655e2cda79030f86", "text": "Kubelet issues a docker inspect call after creating a container, but for very short lived containers there is a window in which they could exit before being inspected in the docker manager. If the container PID is 0, we should check the ExitCode and other relevant fields and handle them appropriately. [1] This is the suspected cause of several flakes: /cc\nlooking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: I'd expect the second one to not have run in this case? Node logs:\nInit containers have an implicit assumption that container statuses include results of previous SyncPod invocations. If that's not the case we may need to fix that (or at least mitigate it). On May 18, 2016, at 8:28 PM, Prashanth B wrote: looking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: May 18 15:58:33.380: INFO: pod-init--1d4b-11e6-80a4- started at 2016-05-18T15:58:04-07:00 (2+1 container statuses recorded) May 18 15:58:33.380: INFO: Init container init1 ready: false, restart count 0 May 18 15:58:33.380: INFO: Init container init2 ready: true, restart count 0 I'd expect the second one to not have run in this case? Node logs: \u2014 You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub\nThis should be true. Is there any evidence that suggests the opposite? only shows conflicting view of whether init1 has run.\nIf the container exits already and it's not an infra container, kubelet should not error out. Although even if it does, I failed to see how this could affect the readiness of the init container without checking the code further.", "commid": "kubernetes_issue_25844", "tokennum": 487}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7f1c4ae81bcfc19facc81332b323d5b418d0ba79b10f5d0e94c13a06c381a468", "query": "} } <ins> func verifyContainerStatuses(statuses []api.ContainerStatus, state, lastTerminationState map[string]api.ContainerState) error { for _, s := range statuses { if !reflect.DeepEqual(s.State, state[s.Name]) { return fmt.Errorf(\"unexpected state: %s\", diff.ObjectDiff(state[s.Name], s.State)) } if !reflect.DeepEqual(s.LastTerminationState, lastTerminationState[s.Name]) { return fmt.Errorf(\"unexpected last termination state %s\", diff.ObjectDiff( lastTerminationState[s.Name], s.LastTerminationState)) } } return nil } // Test generateAPIPodStatus with different reason cache and old api pod status. </ins> func TestGenerateAPIPodStatusWithReasonCache(t *testing.T) { // The following waiting reason and message  are generated in convertStatusToAPIStatus() startWaitingReason := \"ContainerCreating\" <ins> initWaitingReason := \"PodInitializing\" </ins> testTimestamp := time.Unix(123456789, 987654321) testErrorReason := fmt.Errorf(\"test-error\") emptyContainerID := (&kubecontainer.ContainerID{}).String() <del> verifyStatus := func(t *testing.T, c int, podStatus api.PodStatus, state, lastTerminationState map[string]api.ContainerState) { statuses := podStatus.ContainerStatuses for _, s := range statuses { if !reflect.DeepEqual(s.State, state[s.Name]) { t.Errorf(\"case #%d, unexpected state: %s\", c, diff.ObjectDiff(state[s.Name], s.State)) } if !reflect.DeepEqual(s.LastTerminationState, lastTerminationState[s.Name]) { t.Errorf(\"case #%d, unexpected last termination state %s\", c, diff.ObjectDiff( lastTerminationState[s.Name], s.LastTerminationState)) } } } </del> testKubelet := newTestKubelet(t) kubelet := testKubelet.kubelet pod := podWithUidNameNs(\"12345678\", \"foo\", \"new\")", "positive_passages": [{"docid": "doc-en-kubernetes-ade5deee53831749acf4a20dbe39f9ef1836656ae43e40b0bb8594efa4e81e92", "text": "Each syncPod invocation, we inspect the list of init container in order looking for lastTerminationState. There could be a bug in that logic, or if we didn't get the full status, we might make a bad decision. When determining which container to run next, we always look for the last init container in the chain that has success, then run the next container (unless the pod is RestartNever). , Yu-Ju Hong wrote:\nSaw this flake again. How do we verify that container status is not lost between syn pods?\n... between calls to syncPods\nThe second sync clearly saw the init1 container, and decided to launch init2. See \"InitContainersToKeep\" in the message below.\ncontainers to keep can include failed containers. , Yu-Ju Hong wrote:\nDiscussed on slack. In summary, the problem has to do with how we convert the kubecontainer.PodStatus to the api.PodStatus. If a container is terminated, the function makes the decisions: the pod restart policy is \"Always\", and there is a \"failure reason\" recorded for the given container, this means the pod worker tried to (re)start the container but failed. Set the state to \"Waiting\" and populate the reason. , the container state is simply \"terminated\". Init containers don't obey the restart policy like regular containers, and the logic will need to be amended to work with them. is working on a PR. In addition to that, kubelet should not error out if a user container exited before it could apply the oom score (which is best effort in this case). fixes that.\nAhh, thanks for digging into the issue. This is the exact the concern I had when I reviewed the initial implementation of init container, which blocks pr for a while. I even asked to help me verify this case, unfortunately we didn't reproduce the issue back then. :-(\nI wish I'd seen the flakes in the runs prior to merge.\nWe didn't notice this until we started running the tests against docker v1.11.1, which is much faster and hit the race condition differently.\nI suppose that's a good thing...\nIt is hard to reproduce this.", "commid": "kubernetes_issue_25844", "tokennum": 482}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7f1c4ae81bcfc19facc81332b323d5b418d0ba79b10f5d0e94c13a06c381a468", "query": "} } <ins> func verifyContainerStatuses(statuses []api.ContainerStatus, state, lastTerminationState map[string]api.ContainerState) error { for _, s := range statuses { if !reflect.DeepEqual(s.State, state[s.Name]) { return fmt.Errorf(\"unexpected state: %s\", diff.ObjectDiff(state[s.Name], s.State)) } if !reflect.DeepEqual(s.LastTerminationState, lastTerminationState[s.Name]) { return fmt.Errorf(\"unexpected last termination state %s\", diff.ObjectDiff( lastTerminationState[s.Name], s.LastTerminationState)) } } return nil } // Test generateAPIPodStatus with different reason cache and old api pod status. </ins> func TestGenerateAPIPodStatusWithReasonCache(t *testing.T) { // The following waiting reason and message  are generated in convertStatusToAPIStatus() startWaitingReason := \"ContainerCreating\" <ins> initWaitingReason := \"PodInitializing\" </ins> testTimestamp := time.Unix(123456789, 987654321) testErrorReason := fmt.Errorf(\"test-error\") emptyContainerID := (&kubecontainer.ContainerID{}).String() <del> verifyStatus := func(t *testing.T, c int, podStatus api.PodStatus, state, lastTerminationState map[string]api.ContainerState) { statuses := podStatus.ContainerStatuses for _, s := range statuses { if !reflect.DeepEqual(s.State, state[s.Name]) { t.Errorf(\"case #%d, unexpected state: %s\", c, diff.ObjectDiff(state[s.Name], s.State)) } if !reflect.DeepEqual(s.LastTerminationState, lastTerminationState[s.Name]) { t.Errorf(\"case #%d, unexpected last termination state %s\", c, diff.ObjectDiff( lastTerminationState[s.Name], s.LastTerminationState)) } } } </del> testKubelet := newTestKubelet(t) kubelet := testKubelet.kubelet pod := podWithUidNameNs(\"12345678\", \"foo\", \"new\")", "positive_passages": [{"docid": "doc-en-kubernetes-0814a4e75b48cf2d27d20141c180e04fbc9b55d5398cce31b037f460c93acb1b", "text": "The extra check of last terminated container in your initial code makes me nervous, but we couldn't reproduce it due to that small race windows until we have a faster docker running on the node. :-)\nI got \"Pods should invoke init containers on a RestartAlways pod\" flake (referenced from ): Logs:\nAll the fixes went in. Please reopen this issue if you see any more flakes.", "commid": "kubernetes_issue_25844", "tokennum": 90}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7f42e3f634f3f5eb957b40cfdc946217fd3f9f5f3ad6555d2cc5a7c8abd2905e", "query": "\"net\" \"os\" \"strconv\" <ins> \"time\" </ins> \"github.com/golang/glog\" \"github.com/spf13/pflag\"", "positive_passages": [{"docid": "doc-en-kubernetes-638d244f4d44257351ae4786f705d88f47a0e12c74ce71a459164cb07c9c1943", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: kube-cm kube-scheduler does not exit when kube-apiserver suspended What you expected to happen: kube-cm kube-scheduler should exit after LeaderElector stops leading How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/sig api-machinery /kind bug\n/assign\n/cc", "commid": "kubernetes_issue_65090", "tokennum": 179}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7f5f423606f68e31c4843868fbdbea1add32dc8468db8147561b8cbad4e2504a", "query": "} if svc := h.ClientConfig.Service; svc != nil { <del> serverName := svc.Name + \".\" + svc.Namespace + \".svc\" restConfig, err := cm.authInfoResolver.ClientConfigFor(serverName) </del> <ins> restConfig, err := cm.authInfoResolver.ClientConfigForService(svc.Name, svc.Namespace) </ins> if err != nil { return nil, err } cfg := rest.CopyConfig(restConfig) <ins> serverName := svc.Name + \".\" + svc.Namespace + \".svc\" </ins> host := serverName + \":443\" cfg.Host = \"https://\" + host if svc.Path != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-73496a383d34eb1ab5962a20be4dce66952c6d20058c4ff89ce94afc1cb5683d", "text": "We are getting the following error when the apiserver connects the webhook on localhost (configured via URL). We should only use the SSL tunnel for the connections to nodes when the webhooks are running as services. /sig api-machinery /kind bug /assign\n/close", "commid": "kubernetes_issue_58779", "tokennum": 64}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7f747efaf75d516bf52bf23ce4b852385d4295745abfb63abbae5199662ec5df", "query": "--pull  -t ${REGISTRY}/conformance-${ARCH}:${VERSION}  --build-arg BASEIMAGE=$(BASEIMAGE)  <ins> --build-arg RUNNERIMAGE=$(RUNNERIMAGE)  </ins> ${TEMP_DIR} rm -rf \"${TEMP_DIR}\"", "positive_passages": [{"docid": "doc-en-kubernetes-b6e1a63eb087c1fdbaf4f20789cf4dc422d7eb3a250658bf836af9dda6b010da", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be modified: image to be based on anything other than Docker Hub sourced Why is this needed: With Docker Hub rate-limit policy in-place, we probably should consider removing this dependency to stay in sync with other base images in Kubernetes project. Folks building their own binaries (i.e. with ) might run into this as well. Notes: Prior discussion happened on An idea from is to use the should probably be renamed to avoid confusion with k/release (h/t Currently, is set to , so migrating to may not be a drop-in move However, , so maybe we don't have to start from scratch /sig testing /area conformance /sig release (cc'ing because builds conformance image, though my quick search seem to show there isn't any build pipelines referencing )\n/assign\ndo we still want to do this? I read somewhere that the images built in Google Cloud are being mirrored from Docker Hub, right? This would mean that the API rate limiting will not hit us any more.\nWomp yeah I think DockerHub rate limit is not really the big motivator at this point. However, I think I still want to consider using distroless / go-runner to build and produce conformance image to reduce the noise from CVE scanning done in downstream places. What do you think?\nYeah I think this seems a valuable addition. Are you planning to work on this issue? :)\nI will, though probably won't start until next week. If you have ideas and would like to start early feel free to go for it! Otherwise, I'd be happy to work on and deliver this.\nThank you Wilson! Feel free to ping again if you need any assistance. /assign\n/triage accepted\none thing I need a little help with is to find a reference for using go-runner image that's used everywhere -- the one that I've found is inside conformance directory which seems to be different from what everyone else is using\nWe maintain a go-runner in k/release:\noops, I forgot to get back on this last week -- I meant to say that I need a reference for image which I can use as , so something like on Dockerfile. Is that a possible thing to do?", "commid": "kubernetes_issue_96692", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7f747efaf75d516bf52bf23ce4b852385d4295745abfb63abbae5199662ec5df", "query": "--pull  -t ${REGISTRY}/conformance-${ARCH}:${VERSION}  --build-arg BASEIMAGE=$(BASEIMAGE)  <ins> --build-arg RUNNERIMAGE=$(RUNNERIMAGE)  </ins> ${TEMP_DIR} rm -rf \"${TEMP_DIR}\"", "positive_passages": [{"docid": "doc-en-kubernetes-5d193977829c25729bf0cf7e65192f8c845e68df9f65fd9e6c218e9e5725e8bf", "text": "after searching around, I found this -- going to try and use and see how it works :smile:\nStarted a PR -- plenty of things I'd like to be discussed but we should probably have the discussions there\nIssues 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\n/remove-lifecycle stale there is work in progress", "commid": "kubernetes_issue_96692", "tokennum": 118}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7f8ae8717ecb93389b9203882f515bcd519cedb24d7ad3e7ba21d73e3aea7db0", "query": "// TODO(#58034): This is not a static file, so it's not quite as straightforward as --google-json-key. // We need to figure out how ACR users can dynamically provide pull credentials before we can deprecate this. pflagRegister(global, local, \"azure-container-registry-config\") <ins> local.MarkDeprecated(\"azure-container-registry-config\", \"Use --image-credential-provider-config and --image-credential-provider-bin-dir to setup acr credential provider instead. Will be removed in a future release.\") </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-164397ea6f5fa2ca928d4dd76377d3f8103ac21b9ae3014f9a95c921fb791826", "text": "WRT , container registry credentials should be included in a docker file instead. We deprecated for this reason in , but is more tricky, because the file it references is not static. We need to figure out what the alternative is for dynamically providing pull credentials to nodes. /cc\nI think we need to enable Managed Service Identity (MSI) for all instances before deprecating . To do this, we also need to grant VM access to Resource Group in Azure IAM (e.g. config Azure AD in acs-engine). WDYT?\nIssues 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\nI think this is still active. Right, /remove-lifecycle stale\nThanks, this is still active\nIssues 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\n-- What's the status of this?\nSorry, no progress yet. Any ideas on this?\n-- pinging again on this one.\nWe're not making any progress yet in this release. Still seeking the possible solutions for non-MSI cases, secret is one option for this. /milestone v1.15 Related and\nNone one is working on this. Let's move this out of 1.15 /milestone v1.16\nthanks. This missed v1.15 feature timeline. LGTM of moving to v1.16.\nHello! I'm the bug triage lead for the 1.16 release cycle and considering this issue is tagged for 1.16, I'd like to check its status. The code freeze is starting on August 29th EOD PST (about 5 days from now) and once the code freeze starts, only release-blocking changes will be considered to be merged. Is this issue still planned to be fixed for the 1.16 release?", "commid": "kubernetes_issue_58034", "tokennum": 489}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7f8ae8717ecb93389b9203882f515bcd519cedb24d7ad3e7ba21d73e3aea7db0", "query": "// TODO(#58034): This is not a static file, so it's not quite as straightforward as --google-json-key. // We need to figure out how ACR users can dynamically provide pull credentials before we can deprecate this. pflagRegister(global, local, \"azure-container-registry-config\") <ins> local.MarkDeprecated(\"azure-container-registry-config\", \"Use --image-credential-provider-config and --image-credential-provider-bin-dir to setup acr credential provider instead. Will be removed in a future release.\") </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-d697b49623b35e9f2d1bfe1612db7307739262948b622701b4cd63789983d676", "text": "/milestone clear is preparing a KEP for this, but it's still not ready yet.\nWill follow this KEP for implementation\nThis should be addressed by /milestone v1.18\nHello ! Bug Triage team here for the 1.18 release. This is a friendly reminder that code freeze is scheduled for 5 March, which is a few weeks from now. Is this issue still intended for 1.18? Thanks in advance!\nC/O Code freeze for release 1.18 is starting in 5 March (less than 1 week from now) and we want to ensure that each issue has a chance to be finished on time. Is this still on track for this deadline?\n/milestone v1.19 The work on the KEP hasn't started yet, so moving this to 1.19\nHello from Bug Triage team! Wanted to follow up on this issue with a friendly reminder that the code freeze for 1.19 is starting June 25th (about 4 weeks from now). As this issue is tagged for 1.19, is it still planned for this release?\n/milestone v1.20\nHey Bug Triage here. Wanted to follow up on the status of this issue as we're approaching code freeze on 12.11.2020. This issue is tagged for 1.20, is it still planned for this release?\nHi Bug Triage here, seeing that there is not much recent activity here, and we are pretty late into code freeze, I am going to remove the milestone label. /milestone clear\n/triage accepted /priority backlog I think we would be able to remove the flag once external kubelet credential provider promoted to GA\n/kind deprecation\nThis 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\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_58034", "tokennum": 462}], "negative_passages": []}
{"query_id": "q-en-kubernetes-7f8ae8717ecb93389b9203882f515bcd519cedb24d7ad3e7ba21d73e3aea7db0", "query": "// TODO(#58034): This is not a static file, so it's not quite as straightforward as --google-json-key. // We need to figure out how ACR users can dynamically provide pull credentials before we can deprecate this. pflagRegister(global, local, \"azure-container-registry-config\") <ins> local.MarkDeprecated(\"azure-container-registry-config\", \"Use --image-credential-provider-config and --image-credential-provider-bin-dir to setup acr credential provider instead. Will be removed in a future release.\") </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-d4a21b3be577ab214d5d61faf9bcc6243731916e2690559ffed63dd63be604bd", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_58034", "tokennum": 22}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8021ffd2c29350fd4ce695e987bbbc630397440601ace240dc16a0216892a71c", "query": "<ins> /* Copyright 2016 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package proxy import ( \"crypto/tls\" \"crypto/x509\" \"fmt\" \"net\" \"net/http\" \"net/http/httptest\" \"net/url\" \"reflect\" \"strings\" \"testing\" utilnet \"k8s.io/kubernetes/pkg/util/net\" ) func TestDialURL(t *testing.T) { roots := x509.NewCertPool() if !roots.AppendCertsFromPEM(localhostCert) { t.Fatal(\"error setting up localhostCert pool\") } cert, err := tls.X509KeyPair(localhostCert, localhostKey) if err != nil { t.Fatal(err) } testcases := map[string]struct { TLSConfig   *tls.Config Dial        func(network, addr string) (net.Conn, error) ExpectError string }{ \"insecure\": { TLSConfig: &tls.Config{InsecureSkipVerify: true}, }, \"secure, no roots\": { TLSConfig:   &tls.Config{InsecureSkipVerify: false}, ExpectError: \"unknown authority\", }, \"secure with roots\": { TLSConfig: &tls.Config{InsecureSkipVerify: false, RootCAs: roots}, }, \"secure with mismatched server\": { TLSConfig:   &tls.Config{InsecureSkipVerify: false, RootCAs: roots, ServerName: \"bogus.com\"}, ExpectError: \"not bogus.com\", }, \"secure with matched server\": { TLSConfig: &tls.Config{InsecureSkipVerify: false, RootCAs: roots, ServerName: \"example.com\"}, }, \"insecure, custom dial\": { TLSConfig: &tls.Config{InsecureSkipVerify: true}, Dial:      net.Dial, }, \"secure, no roots, custom dial\": { TLSConfig:   &tls.Config{InsecureSkipVerify: false}, Dial:        net.Dial, ExpectError: \"unknown authority\", }, \"secure with roots, custom dial\": { TLSConfig: &tls.Config{InsecureSkipVerify: false, RootCAs: roots}, Dial:      net.Dial, }, \"secure with mismatched server, custom dial\": { TLSConfig:   &tls.Config{InsecureSkipVerify: false, RootCAs: roots, ServerName: \"bogus.com\"}, Dial:        net.Dial, ExpectError: \"not bogus.com\", }, \"secure with matched server, custom dial\": { TLSConfig: &tls.Config{InsecureSkipVerify: false, RootCAs: roots, ServerName: \"example.com\"}, Dial:      net.Dial, }, } for k, tc := range testcases { func() { ts := httptest.NewUnstartedServer(http.HandlerFunc(func(w http.ResponseWriter, req *http.Request) {})) defer ts.Close() ts.TLS = &tls.Config{Certificates: []tls.Certificate{cert}} ts.StartTLS() tlsConfigCopy := utilnet.CloneTLSConfig(tc.TLSConfig) transport := &http.Transport{ Dial:            tc.Dial, TLSClientConfig: tlsConfigCopy, } extractedDial, err := utilnet.Dialer(transport) if err != nil { t.Fatal(err) } if fmt.Sprintf(\"%p\", extractedDial) != fmt.Sprintf(\"%p\", tc.Dial) { t.Fatalf(\"%s: Unexpected dial\", k) } extractedTLSConfig, err := utilnet.TLSClientConfig(transport) if err != nil { t.Fatal(err) } if extractedTLSConfig == nil { t.Fatalf(\"%s: Expected tlsConfig\", k) } u, _ := url.Parse(ts.URL) _, p, _ := net.SplitHostPort(u.Host) u.Host = net.JoinHostPort(\"127.0.0.1\", p) conn, err := DialURL(u, transport) // Make sure dialing doesn't mutate the transport's TLSConfig if !reflect.DeepEqual(tc.TLSConfig, tlsConfigCopy) { t.Errorf(\"%s: transport's copy of TLSConfig was mutatedn%#vnn%#v\", k, tc.TLSConfig, tlsConfigCopy) } if err != nil { if tc.ExpectError == \"\" { t.Errorf(\"%s: expected no error, got %q\", k, err.Error()) } if !strings.Contains(err.Error(), tc.ExpectError) { t.Errorf(\"%s: expected error containing %q, got %q\", k, tc.ExpectError, err.Error()) } return } conn.Close() if tc.ExpectError != \"\" { t.Errorf(\"%s: expected error %q, got none\", k, tc.ExpectError) } }() } } // localhostCert was generated from crypto/tls/generate_cert.go with the following command: //     go run generate_cert.go  --rsa-bits 512 --host 127.0.0.1,::1,example.com --ca --start-date \"Jan 1 00:00:00 1970\" --duration=1000000h var localhostCert = []byte(`-----BEGIN CERTIFICATE----- MIIBdzCCASOgAwIBAgIBADALBgkqhkiG9w0BAQUwEjEQMA4GA1UEChMHQWNtZSBD bzAeFw03MDAxMDEwMDAwMDBaFw00OTEyMzEyMzU5NTlaMBIxEDAOBgNVBAoTB0Fj bWUgQ28wWjALBgkqhkiG9w0BAQEDSwAwSAJBAN55NcYKZeInyTuhcCwFMhDHCmwa IUSdtXdcbItRB/yfXGBhiex00IaLXQnSU+QZPRZWYqeTEbFSgihqi1PUDy8CAwEA AaNoMGYwDgYDVR0PAQH/BAQDAgCkMBMGA1UdJQQMMAoGCCsGAQUFBwMBMA8GA1Ud EwEB/wQFMAMBAf8wLgYDVR0RBCcwJYILZXhhbXBsZS5jb22HBH8AAAGHEAAAAAAA AAAAAAAAAAAAAAEwCwYJKoZIhvcNAQEFA0EAAoQn/ytgqpiLcZu9XKbCJsJcvkgk Se6AbGXgSlq+ZCEVo0qIwSgeBqmsJxUu7NCSOwVJLYNEBO2DtIxoYVk+MA== -----END CERTIFICATE-----`) // localhostKey is the private key for localhostCert. var localhostKey = []byte(`-----BEGIN RSA PRIVATE KEY----- MIIBPAIBAAJBAN55NcYKZeInyTuhcCwFMhDHCmwaIUSdtXdcbItRB/yfXGBhiex0 0IaLXQnSU+QZPRZWYqeTEbFSgihqi1PUDy8CAwEAAQJBAQdUx66rfh8sYsgfdcvV NoafYpnEcB5s4m/vSVe6SU7dCK6eYec9f9wpT353ljhDUHq3EbmE4foNzJngh35d AekCIQDhRQG5Li0Wj8TM4obOnnXUXf1jRv0UkzE9AHWLG5q3AwIhAPzSjpYUDjVW MCUXgckTpKCuGwbJk7424Nb8bLzf3kllAiA5mUBgjfr/WtFSJdWcPQ4Zt9KTMNKD EUO0ukpTwEIl6wIhAMbGqZK3zAAFdq8DD2jPx+UJXnh0rnOkZBzDtJ6/iN69AiEA 1Aq8MJgTaYsDQWyU/hDq5YkDJc9e9DSCvUIzqxQWMQE= -----END RSA PRIVATE KEY-----`) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-01f8727bc339d7af9aee90f0167a90af1aad001fdd8330c2abd8f77d4ae97abe", "text": "When the master dials nodes, it is mutating the tlsConfig held by the master kubelet client, to add a server name. That means if two different nodes are dialed from a master started with , x509 verification will fail for the second one. Introduced in\nthis is a regression from 1.3 and breaks pod logs/exec/attach and node proxying on installations that use\nWe probably need to review that PR and look to see if any other deliberate copies were flagged incorrectly by govet.\nInstallations that depend on secure trust from externally provided kubelet server certs are the highest security rings. If we don't fix this we need to tell anyone using this flag not to upgrade until we release 1.4.1.\nthe rest of the changes in the govet cleanup PR looked fine to me. fix for this issue is in\nSince we are telling folks they have to upgrade to kubectl 1.4.0 for rollingupdate to work it would definitely be a confusing message to say other folks should not upgrade to 1.4.0 at all.\nIf the fix is merged into master by this afternoon, lets discuss whether or not we should cherrypick it - e.g. risks involved, how we can manually qa to verify nothing else was broken, etc.\nRisk involved: If you are using a secure cluster (defined as ensuring no one can MITM your nodes and masters) and you upgrade to 1.4.0 and it does not include this fix - you are broken.\nWhat is the likelihood of interactions with other code? Is it possible this fix could introduce a breaking change to something else? Has the fix been manually verified? Are we confident that this will fully fixes the issue (vs other edge cases exist for secure clusters that this doesn't catch). Ideally I would like to see this cherrypicked into 1.4 this evening and then cut a new beta that includes it.\nNone. The single line that is currently broken was changed. The rest is a new function (with no side effects), and tests. No, it restores the original intent of the TLS config copy, and tests cover the cases we are using this with (secure, insecure, custom dialer) Yes. I swept for the same issue elsewhere and didn't find any issues. We test with a fully secured master-kubelet setup in Openshift and got a clean test run with this fix applied.\nSGTM. Thanks for fixing this.", "commid": "kubernetes_issue_33140", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-803aee470ae7e7b4c45653f289b419ac8bd1654bfefdcc05226cb2cf68204503", "query": "\"k8s.io/klog\" <ins> \"k8s.io/apimachinery/pkg/util/sets\" </ins> \"k8s.io/apimachinery/pkg/util/wait\" )", "positive_passages": [{"docid": "doc-en-kubernetes-01cc291fb1d6afeae9b284d60dd407b578a72d26e4c50043cbdf654c92184c45", "text": "What would you like to be : Add support to the kube-apiserver so that we can disable health-checks via query params. Why is this needed: Currently, the healthz endpoint is inflexible in that any and all health checks are currently executed when the endpoint is hit. Since the kube-apiserver only currently supports a liveness check, this means all persistent health check failures will eventually result in a kubelet driven restart. However, this may not be desirable behavior if you have additional monitoring services layered on top of your control plane. For instance, take the etcd failure from the perspective of the kube-apiserver. Currently, persistent failures during the etcd health check from the api-server healthz endpoint will cause the kube-apiserver to be restarted. This sometimes helps (in the case of a faulty etcd-client connection) but also can be detrimental (the kube-apiserver restarts until the etcd cluster is functioning, then the kube-apiserver bombards the etcd cluster with requests to update local caches, saturating the etcd cluster with requests, causing it to timeout on its own liveness probes and trigger a kubelet-driven restart). Let's say that we could now disable etcd from our liveness health check. Then if we had an external monitoring service, we could ask independently ask etcd if it was healthy and we could also ask the kube-apiserver if it thought etcd was unhealthy. Based on the combination of those answers, we could enable more intelligent responses to certain situation, like restarting the kube-apiserver when it thought etcd was unhealthy but etcd was actually reporting as healthy but not doing so when etcd was actually unhealthy. This feature is backwards-compatible and opt-in. There would be no impact to existing behavior unless these query params are actually used. /sig api-machinery /kind feature\n/cc\nSGTM\n/assign", "commid": "kubernetes_issue_70591", "tokennum": 432}], "negative_passages": []}
{"query_id": "q-en-kubernetes-803b15ed802e9ffa59825a965a50fb957f615a58bdc52b4cd2b93434b3e93d63", "query": "jig := framework.NewServiceTestJig(cs, serviceName) nodes := jig.GetNodes(framework.MaxNodesForEndpointsTests) <del> svc := jig.CreateOnlyLocalLoadBalancerService(namespace, serviceName, loadBalancerCreateTimeout, false, nil) </del> <ins> svc := jig.CreateOnlyLocalLoadBalancerService(namespace, serviceName, loadBalancerCreateTimeout, false, func(svc *v1.Service) { // Change service port to avoid collision with opened hostPorts // in other tests that run in parallel. if len(svc.Spec.Ports) != 0 { svc.Spec.Ports[0].TargetPort = intstr.FromInt(int(svc.Spec.Ports[0].Port)) svc.Spec.Ports[0].Port = 8081 } }) </ins> serviceLBNames = append(serviceLBNames, cloudprovider.GetLoadBalancerName(svc)) defer func() { jig.ChangeServiceType(svc.Namespace, svc.Name, v1.ServiceTypeClusterIP, loadBalancerCreateTimeout)", "positive_passages": [{"docid": "doc-en-kubernetes-7b220aad8e787390cf311abd9e152a85d982510e255be9f3d76952f410cd2fe7", "text": "https://k8s- It's quite flaky.\nThere are no sig labels on this issue. Please by:<br(1) mentioning a sig: <br(2) specifying the label manually: <br<brNote: method (1) will trigger a notification to the team. You can find the team list and label list\n/assign\n/sig networking\nThere are two failures in gci-gce-slow, so it's not specific to gke. https://k8s- Also in gce-slow: https://k8s-\n/sig network\nThis is strange, seems like this test is trying to reach the test-netexec pod through servicePublicIP:serivcePort, but the request hit the gce default backend instead. cc\nThere is another type of failure: Seems to be the port collision between test service and fluentd daemonset, which changed to use few days ago ().\ncc\nChecked the kube-proxy logs and found this is not the case. Port was not allocated (although that could happen in theory) to any service during test:\nThis turned out to be an interesting corner case. It happens at the beginning after we set up the GCE network LoadBalancer for OnlyLocal service --- when the LB still forwarding traffic onto nodes that don't have endpoints on. For more context, when network LB forward traffic to nodes, packet arrives node with below src:dst: If no endpoints are on the node, and there happens to have a pod using hostPort with the same port number, packet will be DNAT to that pod IP instead. These are observations and I haven't traced down to the exact iptables entries. I'm changing service port in test to avoid collision for now. cc", "commid": "kubernetes_issue_47745", "tokennum": 387}], "negative_passages": []}
{"query_id": "q-en-kubernetes-804a219c1997de0611cf2b0c8e1682c21f388e42f38ec0e1970a2a6e66135c0c", "query": "{\"name\" : \"ServiceSpreadingPriority\", \"weight\" : 1}, {\"name\" : \"EqualPriority\", \"weight\" : 1} ], <del> \"extenders\":[ </del> <ins> \"extenders\" : [ </ins> { \"urlPrefix\": \"http://127.0.0.1:12346/scheduler\", \"apiVersion\": \"v1beta1\",", "positive_passages": [{"docid": "doc-en-kubernetes-88466bc637a805045217da94feabbdbd3df0ba52cd0d9904e95d3984c4cf4efa", "text": "( noticed this) HardPodAffinitySymmetricWeight should be in the , not in KubeSchedulerConfiguration If/when fixing this, we need to be careful to do it in a backward-compatilble way.\nDo you mean ? It seems scheduler policy config's args can not passed to FitPredicates; it need to update related interface. For the : mark to be deprecated and set scheduler policy config to HardPodAffinitySymmetricWeight if policy config is empty.\nAre you working on this? if no, I can take it.\n, nop; please go ahead.\n/ / / , When reviewing the PR, there's one question on : the default value of is 1, which means the weight (1) will always add to priorities if term matched (), does it our expectation? And the user has to set it to 0 to disable it. IMO, the default value of should be 0.\nThe value 1 (instead of 0) was chosen so that if you say A must run with B, there is an automatic preference that B should run with A. This seems like reasonable behavior.\nThanks very much; reasonable case to me. But it seems we can not disable it: if set to 0, the default funcs will set it to default (1); similar result to un-set. Anyway, no user complain this now :).", "commid": "kubernetes_issue_43845", "tokennum": 306}], "negative_passages": []}
{"query_id": "q-en-kubernetes-805116ed3c91c3a20e839b0310283ee03b8ad3575efd6c2dde9c433b9ff7d43a", "query": "var _ = framework.KubeDescribe(\"Pods\", func() { f := framework.NewDefaultFramework(\"pods\") var podClient *framework.PodClient <ins> var dc dynamic.Interface </ins> ginkgo.BeforeEach(func() { podClient = f.PodClient() <ins> dc = f.DynamicClient </ins> }) /*", "positive_passages": [{"docid": "doc-en-kubernetes-a4e08d4660e59e77b869eee3e8c161e5e01175b90d68e1077fd3e84d4f4d567b", "text": "[x] Original approval issue: - Reverted due to flakes [x] Two weeks soak end date: 20 November 2020 This issue is created to allow edit by /wip /hold According to this APIsnoop query, there are still some remaining Pod endpoints which are untested. a Pod with a static label the Pod with a new Label and updated data the Pod to ensure it's patched the Pod's status the Pod's status Ready condition to False the Pod's status to check if Ready is False all Pods in all Namespaces find the Pod(1) ensure that the Pod is found and is patched Namespaced Pod(1) via a Collection with a LabelSelector the Pod to check that it's deleted Discover useragents: List endpoints hit by the test: Display endpoint coverage change: If a test with these calls gets merged, test coverage will go up by 4 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance\n/reopen Test PR Merge Promotion PR to be created next\nReopened this issue. <detailsIn response to : /reopen Test PR Merge Promotion PR to be created next 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\nreverted by due to flaky test\nIssues 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\n/remove-lifecycle stale\n/reopen PR on test grid for 2 weeks before promotion to conformance\nReopened this issue. <detailsIn response to : /reopen PR on test grid for 2 weeks before promotion to conformance 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\n/triage accepted", "commid": "kubernetes_issue_90936", "tokennum": 449}], "negative_passages": []}
{"query_id": "q-en-kubernetes-80547700908d4d8f6b34e5f8ce1d059da424e8ca5e3eab1bf750fb83fa185143", "query": "// rules separately to systemd) we can safely skip entries that don't // have a corresponding path. if _, err := os.Stat(entry.Path); err != nil { <del> logrus.Debugf(\"skipping device %s for systemd: %s\", entry.Path, err) continue </del> <ins> // Also check /sys/dev so that we don't depend on /dev/{block,char} // being populated. (/dev/{block,char} is populated by udev, which // isn't strictly required for systemd). Ironically, this happens most // easily when starting containerd within a runc created container // itself. // We don't bother with securejoin here because we create entry.Path // right above here, so we know it's safe. if _, err := os.Stat(\"/sys\" + entry.Path); err != nil { logrus.Warnf(\"skipping device %s for systemd: %s\", entry.Path, err) continue } </ins> } } deviceAllowList = append(deviceAllowList, entry)", "positive_passages": [{"docid": "doc-en-kubernetes-3a5f1791fd28a186fcf23c773fa97525e98fb83cc70e7098ac61d449614dcefb", "text": "opencontainers/runc has fixed three CVEs: Latest runc is pulled by k/k Check runc version in file No response n/a n/a <details</details<details</details<details</details<details</details\n/assign /sig security architecture release\n/triage accepted", "commid": "kubernetes_issue_117094", "tokennum": 68}], "negative_passages": []}
{"query_id": "q-en-kubernetes-807c14cc58e6fdcfeee57f90b915209f4c72cb88e93099389589da588f0766a1", "query": "<del> This file has moved to [https://github.com/kubernetes/examples/blob/master/staging/elasticsearch/production_cluster/README.md](https://github.com/kubernetes/examples/blob/master/staging/elasticsearch/production_cluster/README.md) </del>", "positive_passages": [{"docid": "doc-en-kubernetes-5fef938b0452d0f6b58e576cd11f17813fb6d6b970f83a7868d905b7784a5e39", "text": "Presently, the elasticsearch example Kubernetes configurations target elasticsearch v1.7.1, which is quite old. As of this writing, the latest elasticsearch release is v5.6.2, with many deployment changes since then. Could the elasticsearch examples be updated to target the v5 series of elasticsearch? See for a more up to date reference configuration.\ncc\nhey it's been a long while since I last contributed to the docs. i can do it soon but i need pointers on how to properly do it.\nhey, so we need to update the stuff under examples/elasticsearch/ *&repos=kubernetes So basically update the images, yaml files etc and test that everything works (and submit a PR)\n/sig testing\nAh, so there's no documentation updates anymore. OK I'll take care of it, assign it to me.\nIssues 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\nGitHub didn't allow me to assign the following users: me. Note that only and repo collaborators can be assigned. <detailsIn response to : /assign me 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\n/assign pires\n/remove-lifecycle stale\nit seems that the example moved to I am now reading that repo guidelines and will update this there. I'll also open a PR that cleans this folder in the current repo and closes this issue.", "commid": "kubernetes_issue_53142", "tokennum": 387}], "negative_passages": []}
{"query_id": "q-en-kubernetes-80873da499d1f101fde86cb7b064a82a9d1aa22ebf282a6c82296a06e75471f9", "query": "} } <ins> // ensure KUBE-MARK-DROP chain exist but do not change any rules for _, ch := range iptablesEnsureChains { if _, err := proxier.iptables.EnsureChain(ch.table, ch.chain); err != nil { klog.Errorf(\"Failed to ensure that %s chain %s exists: %v\", ch.table, ch.chain, err) return } } </ins> // // Below this point we will not return until we try to write the iptables rules. //", "positive_passages": [{"docid": "doc-en-kubernetes-6cbf7dcb5e6486cb532532a59cda0ac4f93a00ec9c96bc20136b3a20d89cc61b", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: ci-kubernetes-e2e-gci-gce-ipvs Which test(s) are failing: [sig-network] Services should only allow access from service loadbalancer source ranges [Slow] Testgrid link: https://k8s- Reason for failure: Anything else we need to know: The test is failing consistently, however, there is also test that is failing a lot but not always, may it be related?\n/sig-network /area ipvs /cc /help wanted\n/sig network\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/assign\n/remove-triage unresolved\nHi, , turnout this is because mark drop rule in be deleted, I raied a pr to fix this issue, PTAL. : )\n/close as duplicate of\nClosing this issue. <detailsIn response to : /close as duplicate of 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\n/reopen this was affecting ipvs only before , let's keep it open until we verify is not failing anymore\nReopened this issue. <detailsIn response to : /reopen this was affecting ipvs only before , let's keep it open until we verify is not failing anymore 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\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign Ok I tested this out with kind in ipvs-mode with metallb. In iptables mode I had zero failures but ipvs does not pass at all during the timeout window. This is likely due to", "commid": "kubernetes_issue_94356", "tokennum": 488}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8092a661b389c0d9a779af2986180a627f9f4796e6884cd8e9ca30bc25c65855", "query": "}, { \"ImportPath\": \"github.com/docker/libnetwork/ipvs\", <del> \"Comment\": \"v0.8.0-dev.2-908-gd5c82231\", \"Rev\": \"d5c822319097cc01cc9bd5ffedd74c7ce7c894f2\" </del> <ins> \"Rev\": \"ba46b928444931e6865d8618dc03622cac79aa6f\" </ins> }, { \"ImportPath\": \"github.com/docker/libtrust\",", "positive_passages": [{"docid": "doc-en-kubernetes-13eba344b12142e2782a67745f08ac2e814f1785c70b127779bdac58248d8b7b", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: Currently, we flush ipvs services by deleting them one by one. That's because there was no flush API in libnetwork. Now, libnetwork supports flush API, I think it's time to rsync. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration**: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig network\n/area kube-proxy\n/assign", "commid": "kubernetes_issue_52070", "tokennum": 279}], "negative_passages": []}
{"query_id": "q-en-kubernetes-80b79a5a1ff8246bc14f28da6f0523e13151322307d296da92f9593a01170544", "query": "isReady, err := testutils.PodRunningReady(p) framework.ExpectNoError(err) framework.ExpectEqual(isReady, true, \"pod should be ready\") <del> readyIn := readyTime.Sub(startedTime) framework.Logf(\"Container started at %v, pod became ready at %v, %v after startupProbe succeeded\", startedTime, readyTime, readyIn) if readyIn < 0 { framework.Failf(\"Pod became ready before startupProbe succeeded\") } if readyIn > 5*time.Second { framework.Failf(\"Pod became ready in %v, more than 5s after startupProbe succeeded. It means that the delay readiness probes were not initiated immediately after startup finished.\", readyIn) } </del> }) /*", "positive_passages": [{"docid": "doc-en-kubernetes-17394de51a0297c3b5009d62fc651309bc0945a0e851cb08a887385f3706124d", "text": "<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI --Seems to be impacting a few KIND jobs on the master branch the most, but also assorted other jobs see the triage link above Reported by Sample failure: /sig node <!-- Please see the deflaking doc () for more guidance! --\nxref probing tests\n/assign ref /triage accepted\nThanks Elana, still trying today... Does anyone know if we can use the kubelet logs in e2e tests?\nNot very portably in cluster e2e tests at least. Maybe in node_e2e instead.\nHave you considered that the issue is not with the test but with the underlying code in kubelet like detailed in this issue Like detailed in the issue I can reliably reproduce (on k8s 1.18) the startup probe passing within a few seconds, but the container is only marked as ready after about a minute.\nthere is already a fix in the 1.21 release for that (part of a bigger PR): And actually this test was to verify that part of the code, but unfortunately sometimes it doesn't respond as quick as it should (but never on my PC, only in ci/cd tests)...\nSome recent flakes:\none of the most common flakes in kind jobs currently failures like: Mar 25 17:03:42.508: Pod became ready in 42.007286524s, more than 5s after startupProbe succeeded. It means that the delay readiness probes were not initiated immediately after startup finished.\nMaybe we could speed up the review on\nThank you I will take a look. I'm making a pass through flakes tonight trying to identify if anything is on kind's end\nI don't think it's kind... since running on my PC with kind it works 100%, I think the issue is either the resources... or contention in the queue as mentioned to in the comment\n/milestone v1.22\ncommented on PR with the suggested fix\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository.", "commid": "kubernetes_issue_99979", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-80b79a5a1ff8246bc14f28da6f0523e13151322307d296da92f9593a01170544", "query": "isReady, err := testutils.PodRunningReady(p) framework.ExpectNoError(err) framework.ExpectEqual(isReady, true, \"pod should be ready\") <del> readyIn := readyTime.Sub(startedTime) framework.Logf(\"Container started at %v, pod became ready at %v, %v after startupProbe succeeded\", startedTime, readyTime, readyIn) if readyIn < 0 { framework.Failf(\"Pod became ready before startupProbe succeeded\") } if readyIn > 5*time.Second { framework.Failf(\"Pod became ready in %v, more than 5s after startupProbe succeeded. It means that the delay readiness probes were not initiated immediately after startup finished.\", readyIn) } </del> }) /*", "positive_passages": [{"docid": "doc-en-kubernetes-e379199dcc10ef545e6719d9fd62c8045ba08caeee0b4e30e1a8cba90abc8ed8", "text": "</details\nYeah...\nThanks for your great work in keeping things in check\nFYI\nI have (finally) understood what's happening, and I can even explain why the deflake made things worse... Please have a look at the sleep before the worker starts to process probes: So, you have to remember that we have one worker per pod and per probe, and since we have these probe settings for the test: We have (PeriodSeconds=10) starting sometimes immediately (if the Kubelet has started since more than 10s) or after a quick sleep of rand10s. On the contrary, will likely sleep most of the time for rand60s. This causes a delay in the processing of notifications: If we are lucky, this delay is less than 5s and the test passes: Now you can understand why the deflaked settings were actually worse:\nThe reason I didn't spot these was that I usually start my cluster once for all and iterate on the tests... so the kubelet had plenty of time to start and I never ended in that sleep.\nFor the solution, I suggest we either remove the sleep completely, or we find something that would make all 3 probe workers start at the same time to avoid sync issues... For the record, I was able to spot this issue thanks to the following log error (because the channel was overflowing): What do you think ?\nI have found another issue in that code: If has already ran (and failed), we go to L245 and don't probe via and therefore wait for the next tick, making the test fail.\nThis seems consistent with what I found when I was adding e2es for the new probe-level termination grace period and why I did my timing math the way I did.\n/reopen I don't think this is fixed, I just hit it again and gubernator is still showing plenty of flakes:\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nhow to check the exact commit used for each test?", "commid": "kubernetes_issue_99979", "tokennum": 462}], "negative_passages": []}
{"query_id": "q-en-kubernetes-80b79a5a1ff8246bc14f28da6f0523e13151322307d296da92f9593a01170544", "query": "isReady, err := testutils.PodRunningReady(p) framework.ExpectNoError(err) framework.ExpectEqual(isReady, true, \"pod should be ready\") <del> readyIn := readyTime.Sub(startedTime) framework.Logf(\"Container started at %v, pod became ready at %v, %v after startupProbe succeeded\", startedTime, readyTime, readyIn) if readyIn < 0 { framework.Failf(\"Pod became ready before startupProbe succeeded\") } if readyIn > 5*time.Second { framework.Failf(\"Pod became ready in %v, more than 5s after startupProbe succeeded. It means that the delay readiness probes were not initiated immediately after startup finished.\", readyIn) } </del> }) /*", "positive_passages": [{"docid": "doc-en-kubernetes-1225e4b3fb518feb838b0b4898217ee9b18190e72a1e6684a1b960954bc011fd", "text": "For instance, I am not sure (from the name) that should include my latest fix...\nIn your PR the fix wasn't there:\nyou may send cherry-pick to 1.21 for which is using kubelet 1.21, not 1.22.\nis using kubelet. Cherry-pick to 1.20 may be needed as well.\nI have found this one that failed even with the fix: corresponding to:\nI don't know what could explain this atm... but it seems we still have delay propagating container statuses.\nIn the job artifacts there are multiple places with this info including the clone records/logs, and In testgrid it's a row.\nyeah afaict since the tests ran on my PR after your fix was merged into master, it showed the flake was still present :( Prow will always use the latest master when running CI.\nSorry for doubting what you said... I was probably in deny and hoped this annoyance was fixed once for all :(\nPlan: we'll see if Clayton's pod lifecycle refactor and/or the jitter refactor for probes affects this.\nClayton's PR jitter refactor\nsince isn't (likely) coming to 1.22 we could cut off 90% of flakes by increasing to 15s delay:\nit seems it fails even after merging so let's continue our discussion on slack\nthis is not a regression, our suggestion is not block release on it. feel free to remove the milestone\n/milestone v1.23\nIn Kubelet maybe, but in the flakiness of the e2e tests it was. Unfortunately we can't easily explore the current state :/\nIn the release blocking jobs the frequency is not horrible now, so unblocking is probably fine, it is not as bad as it was. Outside of the release cycle this is still the flakiest test in some jobs, see e.g. where it's the only flake source we have on record currently.\nif we end up needing it, we have a timing/period adjustment PR we can take that should help with the flakiness with", "commid": "kubernetes_issue_99979", "tokennum": 451}], "negative_passages": []}
{"query_id": "q-en-kubernetes-80cafa6f4f2486128f867f7c8d42b4fcf6f63b6c35115223c15ba974760e2d88", "query": "// unset or false and it can be flipped later when storage // capacity information has been published. // <del> // This field is immutable. </del> <ins> // This field was immutable in Kubernetes <= 1.22 and now is mutable. </ins> // // This is a beta field and only available when the CSIStorageCapacity // feature is enabled. The default is false.", "positive_passages": [{"docid": "doc-en-kubernetes-cdccab911562ccfffce851739652bcccdbeabc99e62d699c46baa58ef67f3bbe", "text": "Up to 1.21, that field is immutable. That means in practice, a CSIDriver object has to be deleted and then re-created with a different value instead. Mutation via delete/created is unnecessarily complex and as the only consumer of that field (the kube-scheduler) can handle mutation just fine (it'll always ask the informer cache for the current value), it's better to allow mutation.\n/sig storage /assign\nThis is independent of allowing other fields to become mutable, but that might also make sense.\n/triage accepted", "commid": "kubernetes_issue_100089", "tokennum": 125}], "negative_passages": []}
{"query_id": "q-en-kubernetes-81086183f73a39618f88d6d4ab71ce42d13ffbe48413818442fa7c99be5955d3", "query": "kubelet.kubeClient = fakeKubeClient kubelet.os = kubecontainer.FakeOS{} <del> kubelet.hostname = \"testnode\" </del> <ins> kubelet.hostname = testKubeletHostname </ins> kubelet.runtimeUpThreshold = maxWaitForContainerRuntime kubelet.networkPlugin, _ = network.InitNetworkPlugin([]network.NetworkPlugin{}, \"\", network.NewFakeHost(nil)) if tempDir, err := ioutil.TempDir(\"/tmp\", \"kubelet_test.\"); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-d16ca614c05197aa8b2652e3bf008c3a9a5ce41d960188a2ba3459b13d8b1102", "text": "Looks like some kubelet unit tests perform a lookupIp which ends up depending on the health of the local resolver. Specifically has this failing: Which leads to the test in: And we recently swapped out the node names from testnode to 127.0.0.1, so probably the culprit?\n/ref\nInteresting. I did swap out the node names in the unit test as part of to be 127.0.0.1, party because I thought that it wouldn't have any problems resolving during unit tests.\n/cc", "commid": "kubernetes_issue_8549", "tokennum": 113}], "negative_passages": []}
{"query_id": "q-en-kubernetes-81086183f73a39618f88d6d4ab71ce42d13ffbe48413818442fa7c99be5955d3", "query": "kubelet.kubeClient = fakeKubeClient kubelet.os = kubecontainer.FakeOS{} <del> kubelet.hostname = \"testnode\" </del> <ins> kubelet.hostname = testKubeletHostname </ins> kubelet.runtimeUpThreshold = maxWaitForContainerRuntime kubelet.networkPlugin, _ = network.InitNetworkPlugin([]network.NetworkPlugin{}, \"\", network.NewFakeHost(nil)) if tempDir, err := ioutil.TempDir(\"/tmp\", \"kubelet_test.\"); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-4a4c75dd985aaeba56d487bbde17d68f0425afc5d7e1167fdf1a1abcb97cd0b6", "text": "cc\nWhat is the environment where you are running the tests? They pass for me on my mac, a linux box, and shippable seems to be passing them as well.\nI couldn 't reproduce the failure either.\nI'm out right now; i'll try them when i get back. For the record, I run hack/test- Paul Morie wrote:\nAhem FTR This acronym is going to go quad-plat Paul Morie wrote:\nI ran on both platforms and saw the tests pass.\nI'm still seeing it. Won't have bandwidth to dig in personally until tomorrow.\nseeing a similar failure after a git pull\nI knew I wasn't crazy\nenvironment: fedora 21, golang: 1.4, docker: 1.6\nI think I see the problem. When I set the node name to in the test I was assuming it would parse as a valid ip address and not end up at the LookupIP call. But only the node name (and not the kubelet hostname) is being set (except in my new test where I ) so it's trying to do a lookup. Do you think you could test just changing the default hostname from \"testnode\" to \"127.0.0.1\" and see if that fixes it for you?\nTrying now\nI still get failures but no panic / threaddump.\ngist coming\nthis looks like again?\nGood that it isn't panicing any longer. I can dig into the test failures tomorrow (I think it should be relatively simple to resolve).\ncool, thanks for looking\nPasses in master now for me. Closing.\nFYI, they will break again once goes in, and then we can merge my PR to see if that fixes it for you.\n:+1:\nis in -- are these tests breaking again?\nI just rebased which I think will fix them.\nThey are breaking again.\nis on it.", "commid": "kubernetes_issue_8522", "tokennum": 407}], "negative_passages": []}
{"query_id": "q-en-kubernetes-815253d83112bec34d2b4354675b46ada938c704e7558a35f7fcdba7b1c8857e", "query": "<ins> ntp: pkg: - installed ntp-service: service: - running - name: ntp - watch: - pkg: ntp </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-2c743938ba30f2fba7527b26804dcfbb8cfcfa24fc2e107c2d5fed7244e0552d", "text": "At least on AWS, if the clock drifts 300 seconds (which it will), then we get the rather cryptic message: This is because AWS includes the timestamp in the request. Installing ntpd would stop this drifting from happening. If the drift does happen, the likely symptom is that EC2 calls would stop working: attach/detach volumes on the minions, instance sync and routing configuration on the master. I don't believe that GCE has the same problem.", "commid": "kubernetes_issue_11371", "tokennum": 102}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8156c6402445227737f12ba1603a50ddeeab1700874cba9d72417366c695ff70", "query": "// InstanceExistsByProviderID returns true if the instance with the given provider id still exists and is running. // If false is returned with no error, the instance will be immediately deleted by the cloud controller manager. func (vs *VSphere) InstanceExistsByProviderID(ctx context.Context, providerID string) (bool, error) { <del> var nodeName string nodes, err := vs.nodeManager.GetNodeDetails() </del> <ins> nodeName, err := vs.GetNodeNameFromProviderID(providerID) </ins> if err != nil { <del> glog.Errorf(\"Error while obtaining Kubernetes node nodeVmDetail details. error : %+v\", err) </del> <ins> glog.Errorf(\"Error while getting nodename for providerID %s\", providerID) </ins> return false, err } <del> for _, node := range nodes { // ProviderID is UUID for nodes v1.9.3+ if node.VMUUID == GetUUIDFromProviderID(providerID) || node.NodeName == providerID { nodeName = node.NodeName break } } if nodeName == \"\" { msg := fmt.Sprintf(\"Error while obtaining Kubernetes nodename for providerID %s.\", providerID) return false, errors.New(msg) } </del> _, err = vs.InstanceID(ctx, convertToK8sType(nodeName)) if err == nil { return true, nil", "positive_passages": [{"docid": "doc-en-kubernetes-8cc0000ebdb21aeba4d3dda4212069010f35d863300d721e65a4eeef908ef7b3", "text": "As planned for 1.12 in kubernetes/features: After , the next step is to add the logic to the reconciler to detach the volumes when the nodeShutdown taint is applied. /assign /sig storage /kind feature looping\nHow do you know that node is Shutdown? is it a planned shutdown or a unplanned shutdown?\nAFAIK regardless of whether it's planned or not, it's detected by the cloud provider. In case of bare-metal node it doesn't happen automatically, as there is no universal way to reliably determine if a node is powered off, so the node must be tainted as by some external source.\nIssues 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\nany update on this issue?\n, I am currently working with sig-node team on handling node shut down. I will make a proposal and discuss in sig-node meeting next Tuesday. Will post the update soon.\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten /kind bug /priority critical-urgent /assign /sig node\nThose labels are not set on the issue: <detailsIn response to : /remove-kind feature 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\nIssues 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\nany update on this? is it going to be part of 1.15?\nStale issues rot after 30d of inactivity. Mark the issue as fresh with .", "commid": "kubernetes_issue_66181", "tokennum": 511}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8156c6402445227737f12ba1603a50ddeeab1700874cba9d72417366c695ff70", "query": "// InstanceExistsByProviderID returns true if the instance with the given provider id still exists and is running. // If false is returned with no error, the instance will be immediately deleted by the cloud controller manager. func (vs *VSphere) InstanceExistsByProviderID(ctx context.Context, providerID string) (bool, error) { <del> var nodeName string nodes, err := vs.nodeManager.GetNodeDetails() </del> <ins> nodeName, err := vs.GetNodeNameFromProviderID(providerID) </ins> if err != nil { <del> glog.Errorf(\"Error while obtaining Kubernetes node nodeVmDetail details. error : %+v\", err) </del> <ins> glog.Errorf(\"Error while getting nodename for providerID %s\", providerID) </ins> return false, err } <del> for _, node := range nodes { // ProviderID is UUID for nodes v1.9.3+ if node.VMUUID == GetUUIDFromProviderID(providerID) || node.NodeName == providerID { nodeName = node.NodeName break } } if nodeName == \"\" { msg := fmt.Sprintf(\"Error while obtaining Kubernetes nodename for providerID %s.\", providerID) return false, errors.New(msg) } </del> _, err = vs.InstanceID(ctx, convertToK8sType(nodeName)) if err == nil { return true, nil", "positive_passages": [{"docid": "doc-en-kubernetes-8b5c9612057f9871f14258bc136d8e86f57d2327861ec200bbe8402ae4819108", "text": "Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten\nIssues 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\n/remove-lifecycle stale\n/priority important-longterm\nIssues 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\n/remove-lifecycle stale /lifecycle frozen\n/triage accepted /kind feature\nThis 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\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI think this can be closed now as we have non-graceful node shutdown.\n/close\nClosing 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", "commid": "kubernetes_issue_66181", "tokennum": 436}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8158677c116d83b2bb18a0ef35df7521d99c8a88a1263b04f99ac456a35ce8c3", "query": ". \"github.com/onsi/gomega\" ) <del> func runLivenessTest(c *client.Client, podDescr *api.Pod) { </del> <ins> func runLivenessTest(c *client.Client, podDescr *api.Pod, expectRestart bool) { </ins> ns := \"e2e-test-\" + string(util.NewUUID()) By(fmt.Sprintf(\"Creating pod %s in namespace %s\", podDescr.Name, ns))", "positive_passages": [{"docid": "doc-en-kubernetes-65bf469670180d69e57fdc1a820a8f2f435cec685a9975e90f226dd126851fba", "text": "As far as I can tell, container liveness probes of type exec flat out don't work against clusters built at head. I had the kubelet always log the output of the exec'ed command, and it's always empty no matter what I exec, causing the probe to fail since it requires the output to be equal to the string \"ok\". If you want to test it, try adding a liveness probe of this form to any container: I also tried these lovely forms, to more closely match the liveness example under examples/: On the plus side, this may be an opportunistic time to switch over to\nThe reason that the e2e test for exec liveness probes hasn't caught this is that it only tests that containers are restarted when they fail liveness probes. It doesn't test that containers aren't restarted when their liveness checks should be succeeding. The e2e test's exec'ed commands also only ever produced empty output, rather than the expected \"fail\" output.\nIs it possible to include this in a new pre-release, since it fixes a bug in health checking? I see it merged in master and I'm wondering what the policy is of releasing new code in a separate (0.16.*) release.", "commid": "kubernetes_issue_7618", "tokennum": 275}], "negative_passages": []}
{"query_id": "q-en-kubernetes-81608425dfcbd2e96c854a2c42df027809867c7435e640ade348ea730f341be9", "query": "import ( \"fmt\" <ins> \"reflect\" \"sort\" </ins> \"strings\" \"testing\"", "positive_passages": [{"docid": "doc-en-kubernetes-8c9ebf4e41021efd0692132f5b2f5e7ec08451127a302fc405c42cb972b9ed2e", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: I created several Workloads which require up to ten ports for both UDP and TCP protocol. Now my logs get spammed with . What you expected to happen: should consider -combination instead of only . How to reproduce it (as minimally and precisely as possible): Deploy any service with a node-port with both protocols, e.g.: Anything else we need to know?: This was already acknowledged by here: However, as this thread addresses a different bug and seems kind of stuck, i'd like to suggest that this might be addressed in a new context. Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Deployed via Rancher v2.4.3\n/sig api-machinery\n/remove-sig api-machinery /sig network\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nHow did you get into this situation? The allocator should not have granted the same node port twice?\nOh right, that issue. The only real way out is to de-allocate the NodePorts and then re-allocate them, I think\nAs this happens for all of my ports in the said Production Application (the one where my log gets spammed) as well as complete fresh installation (where i verified the bug), i think there's no \"way out\" except fixing the bug. As said, for me it's necessary to assign both protocols to the same port. This might be a niche-use-case, but checking the it's actually very likely for ports to allow tcp AND udp. I'm not sure about the history of this, but it might be that issue was the origin, which was adressed in PR (\"Allow services which use same port, different protocol to use the same nodePort for both\"). But this PR doesn't contain the adjustment of the said , so still considers the behaviour as invalid, while it's actually allowed and supported.", "commid": "kubernetes_issue_91404", "tokennum": 498}], "negative_passages": []}
{"query_id": "q-en-kubernetes-81608425dfcbd2e96c854a2c42df027809867c7435e640ade348ea730f341be9", "query": "import ( \"fmt\" <ins> \"reflect\" \"sort\" </ins> \"strings\" \"testing\"", "positive_passages": [{"docid": "doc-en-kubernetes-33f53ed726ab1a89c68c77aae3b932484545b038842bda14047a639f615b725d", "text": "/assign\nAhh, I thought you meant that you had accidentally been allocated the same nodePorts and I was very confused when you said \"all of them\". I have reproduced this issue, and I can see it by inspection. The obvious fix would be to collect ports split by protocol, but I think that's not right since we don't store it split. An even simpler fix would be for to build a . Then for each protocol, for each port, build that contains all the port numbers, but remove any duplicates ONLY IF they are duplicated across protocols. Duplicates in the same protocol should be retained (to report an error later). I don't have time to tackle this tonight (and write a test), but it seems like a good bug.\nperhaps I can fix this problem /assign\nthings may be a little more complicated. Right now the is not aware of the protocol of the port so I guess simply rewriting function to return is not enough, the port allocator will still return on same node port even with different protocol. perhaps we need to refactor the to make it protocol-aware.\nI don't think we need to do make the allocator be protocol aware. IIRC we allow you to use the same nodeport on different protocols ONLY within a single service. This means (I think) that we can do hyper-local deduplication as we collect the nodeports for each service. If we find the same nodeport number with different protocols, just remove the duplicates because it is allowed. I.e. a service that looks like: return - deduped. if ANY OTHER service tried to use it would be an error at the \"rebuilt\" allocator Likewise if a single Service claims to use the same nodeport number more than once on the same protocol, it should be an error: return - NOT deduped.\nobviously, we want a great unit test here :P\nah got it! thanks for your detailed explanation!\nHi! I have filed a PR to resolve this issue, could you take a look?", "commid": "kubernetes_issue_91404", "tokennum": 428}], "negative_passages": []}
{"query_id": "q-en-kubernetes-81673d7a3502e88554df9ac53bcae358082e341c4d604a586dc41373bb5c326c", "query": "return &serverList[0], nil } <del> func findAddrs(netblob interface{}) []string { // Run-time types for the win :( ret := []string{} list, ok := netblob.([]interface{}) if !ok { return ret } for _, item := range list { props, ok := item.(map[string]interface{}) if !ok { continue } tmp, ok := props[\"addr\"] </del> <ins> func getAddressesByName(client *gophercloud.ServiceClient, name string) ([]api.NodeAddress, error) { srv, err := getServerByName(client, name) if err != nil { return nil, err } addrs := []api.NodeAddress{} for network, netblob := range srv.Addresses { list, ok := netblob.([]interface{}) </ins> if !ok { continue } <del> addr, ok := tmp.(string) if !ok { continue </del> <ins> for _, item := range list { var addressType api.NodeAddressType props, ok := item.(map[string]interface{}) if !ok { continue } extIPType, ok := props[\"OS-EXT-IPS:type\"] if (ok && extIPType == \"floating\") || (!ok && network == \"public\") { addressType = api.NodeExternalIP } else { addressType = api.NodeInternalIP } tmp, ok := props[\"addr\"] if !ok { continue } addr, ok := tmp.(string) if !ok { continue } api.AddToNodeAddresses(&addrs, api.NodeAddress{ Type:    addressType, Address: addr, }, ) </ins> } <del> ret = append(ret, addr) </del> } <del> return ret </del> <ins> // AccessIPs are usually duplicates of \"public\" addresses. if srv.AccessIPv4 != \"\" { api.AddToNodeAddresses(&addrs, api.NodeAddress{ Type:    api.NodeExternalIP, Address: srv.AccessIPv4, }, ) } if srv.AccessIPv6 != \"\" { api.AddToNodeAddresses(&addrs, api.NodeAddress{ Type:    api.NodeExternalIP, Address: srv.AccessIPv6, }, ) } return addrs, nil </ins> } <del> func getAddressByName(api *gophercloud.ServiceClient, name string) (string, error) { srv, err := getServerByName(api, name) </del> <ins> func getAddressByName(client *gophercloud.ServiceClient, name string) (string, error) { addrs, err := getAddressesByName(client, name) </ins> if err != nil { return \"\", err <ins> } else if len(addrs) == 0 { return \"\", ErrNoAddressFound </ins> } <del> var s string if s == \"\" { if tmp := findAddrs(srv.Addresses[\"private\"]); len(tmp) >= 1 { s = tmp[0] } } if s == \"\" { if tmp := findAddrs(srv.Addresses[\"public\"]); len(tmp) >= 1 { s = tmp[0] </del> <ins> for _, addr := range addrs { if addr.Type == api.NodeInternalIP { return addr.Address, nil </ins> } } <del> if s == \"\" { s = srv.AccessIPv4 } if s == \"\" { s = srv.AccessIPv6 } if s == \"\" { return \"\", ErrNoAddressFound } return s, nil </del> <ins> return addrs[0].Address, nil </ins> } // Implementation of Instances.CurrentNodeName", "positive_passages": [{"docid": "doc-en-kubernetes-3129ecf685ad2fea6cb3ff97d12eed1692df1703f934c30f7ebae50375bb63d6", "text": "From we can find that, hardcode \"private\" and \"public\", seems only support that network with such name. , it fetch the first ip. usually, it can include both v6 and v4 ip. what's the meaning to just fetch the first one ? is it v4 or v6 ?\nping and\nYes. Zoom out a level or two in the code, and you'll see we're trying to either a) setup an openstack loadbalancer to point to the minion node (a single address) using , or b) report to kubernetes all the addresses we know about the node and whether they are \"internal\" or \"external\" in . All we have at the starting point is the server name (from kubernetes), and we need to make up the rest of this information somehow. (I agree (a) should reuse the NodeAddresses() function from (b), but the latter is a newer function and the code hasn't yet been refactored in that way. This doesn't really change the substance of this discussion.) Re (1): The logic as currently implemented is: Assume any network named \"private\" is \"internal\" Assume any network named \"public\" is \"external\" Assume the AccessIPs (IPv4 and IPv6) are \"external\" Any other network addresses are ignored. I implemented the first two (\"private\" and \"public\") following the Rackspace public cloud precedent, and on the basis that users in other OpenStack clouds can use these names if they want to encourage an address other than the Access addresses. For the (a) use case, we just take the first address we find in order of the above; for (b) we report that full list. I preferred \"private\" to \"public\" since (again, at least on Rackspace public cloud), the traffic on \"private\" network is sometimes cheaper/free. I agree this isn't great, and please suggest something better if you have a use case in mind. Perhaps we should pull a list of network names that should be considered \"internal\" and \"external\" from the provider config? Perhaps I could assume that provider networks are public and non-provider networks are internal? I don't want to add too much configuration here if there's a good algorithm that will Just Work.", "commid": "kubernetes_issue_18409", "tokennum": 498}], "negative_passages": []}
{"query_id": "q-en-kubernetes-81673d7a3502e88554df9ac53bcae358082e341c4d604a586dc41373bb5c326c", "query": "return &serverList[0], nil } <del> func findAddrs(netblob interface{}) []string { // Run-time types for the win :( ret := []string{} list, ok := netblob.([]interface{}) if !ok { return ret } for _, item := range list { props, ok := item.(map[string]interface{}) if !ok { continue } tmp, ok := props[\"addr\"] </del> <ins> func getAddressesByName(client *gophercloud.ServiceClient, name string) ([]api.NodeAddress, error) { srv, err := getServerByName(client, name) if err != nil { return nil, err } addrs := []api.NodeAddress{} for network, netblob := range srv.Addresses { list, ok := netblob.([]interface{}) </ins> if !ok { continue } <del> addr, ok := tmp.(string) if !ok { continue </del> <ins> for _, item := range list { var addressType api.NodeAddressType props, ok := item.(map[string]interface{}) if !ok { continue } extIPType, ok := props[\"OS-EXT-IPS:type\"] if (ok && extIPType == \"floating\") || (!ok && network == \"public\") { addressType = api.NodeExternalIP } else { addressType = api.NodeInternalIP } tmp, ok := props[\"addr\"] if !ok { continue } addr, ok := tmp.(string) if !ok { continue } api.AddToNodeAddresses(&addrs, api.NodeAddress{ Type:    addressType, Address: addr, }, ) </ins> } <del> ret = append(ret, addr) </del> } <del> return ret </del> <ins> // AccessIPs are usually duplicates of \"public\" addresses. if srv.AccessIPv4 != \"\" { api.AddToNodeAddresses(&addrs, api.NodeAddress{ Type:    api.NodeExternalIP, Address: srv.AccessIPv4, }, ) } if srv.AccessIPv6 != \"\" { api.AddToNodeAddresses(&addrs, api.NodeAddress{ Type:    api.NodeExternalIP, Address: srv.AccessIPv6, }, ) } return addrs, nil </ins> } <del> func getAddressByName(api *gophercloud.ServiceClient, name string) (string, error) { srv, err := getServerByName(api, name) </del> <ins> func getAddressByName(client *gophercloud.ServiceClient, name string) (string, error) { addrs, err := getAddressesByName(client, name) </ins> if err != nil { return \"\", err <ins> } else if len(addrs) == 0 { return \"\", ErrNoAddressFound </ins> } <del> var s string if s == \"\" { if tmp := findAddrs(srv.Addresses[\"private\"]); len(tmp) >= 1 { s = tmp[0] } } if s == \"\" { if tmp := findAddrs(srv.Addresses[\"public\"]); len(tmp) >= 1 { s = tmp[0] </del> <ins> for _, addr := range addrs { if addr.Type == api.NodeInternalIP { return addr.Address, nil </ins> } } <del> if s == \"\" { s = srv.AccessIPv4 } if s == \"\" { s = srv.AccessIPv6 } if s == \"\" { return \"\", ErrNoAddressFound } return s, nil </del> <ins> return addrs[0].Address, nil </ins> } // Implementation of Instances.CurrentNodeName", "positive_passages": [{"docid": "doc-en-kubernetes-73739ae9bad159746241b14eae0e38aaa61fc839e6a2ae622df67e262b940fc6", "text": "I think in practice it's probably ok to continue to prefer \"internal\" to \"external\" for loadbalancer setup, but I can contrive hypothetical cases that need more flexibility here too. Again, if you have a concrete need for such a thing, please file a bug so we have some idea of the flexibility required. Complicating all this is that Kubernetes never actually defined what an \"internal\" address was. just says \"Generally the IP address of the node that is routable only within the cluster\" which isn't a sufficiently strict definition. Looking at where Kubernetes actually uses it: just uses the first address reported (preferring InternalIPs to ExternalIPs) and the Kubernetes master configures an \"SSH Tunnel Check\" which just uses the first ExternalIP ... which kind of makes it pointless to ever even bother reporting anything beyond the first address. In both cases, it's assumed that this address is reachable by the Kubernetes master nodes, which makes the Internal vs External distinction a bit pointless. Re (2): is meant to return more than one IP, and the loadbalancer setup can only use a single IP for each node (or would unnecessarily track/healthceck multiple paths to the same backend for multiple addresses). If you're seeing single addresses returned by then you should file a bug. All the above treats IPv4 and IPv6 as equally important, if the OpenStack cloud has both, and the \"first\" address used for the loadbalancer will be an arbitrary choice between the two protocols (not quite true: will use AccessIPv4 before AccessIPv6). I think that's how it should be (the rest of the code should be protocol agnostic), but I wouldn't be surprised if there's some part of Kubernetes that doesn't support IPv6 properly. There certainly used to be lots of places that assumed IPv4 in Kubernetes, and GCE doesn't support IPv6 iirc so it gets less testing - if you've found something that breaks with IPv6, please file bugs. Now this bug: what would you like done here? Would you like the current situation to be documented further? Is the \"private\"/\"public\" naming thing too restrictive for your usecase? Something else?", "commid": "kubernetes_issue_18409", "tokennum": 505}], "negative_passages": []}
{"query_id": "q-en-kubernetes-81673d7a3502e88554df9ac53bcae358082e341c4d604a586dc41373bb5c326c", "query": "return &serverList[0], nil } <del> func findAddrs(netblob interface{}) []string { // Run-time types for the win :( ret := []string{} list, ok := netblob.([]interface{}) if !ok { return ret } for _, item := range list { props, ok := item.(map[string]interface{}) if !ok { continue } tmp, ok := props[\"addr\"] </del> <ins> func getAddressesByName(client *gophercloud.ServiceClient, name string) ([]api.NodeAddress, error) { srv, err := getServerByName(client, name) if err != nil { return nil, err } addrs := []api.NodeAddress{} for network, netblob := range srv.Addresses { list, ok := netblob.([]interface{}) </ins> if !ok { continue } <del> addr, ok := tmp.(string) if !ok { continue </del> <ins> for _, item := range list { var addressType api.NodeAddressType props, ok := item.(map[string]interface{}) if !ok { continue } extIPType, ok := props[\"OS-EXT-IPS:type\"] if (ok && extIPType == \"floating\") || (!ok && network == \"public\") { addressType = api.NodeExternalIP } else { addressType = api.NodeInternalIP } tmp, ok := props[\"addr\"] if !ok { continue } addr, ok := tmp.(string) if !ok { continue } api.AddToNodeAddresses(&addrs, api.NodeAddress{ Type:    addressType, Address: addr, }, ) </ins> } <del> ret = append(ret, addr) </del> } <del> return ret </del> <ins> // AccessIPs are usually duplicates of \"public\" addresses. if srv.AccessIPv4 != \"\" { api.AddToNodeAddresses(&addrs, api.NodeAddress{ Type:    api.NodeExternalIP, Address: srv.AccessIPv4, }, ) } if srv.AccessIPv6 != \"\" { api.AddToNodeAddresses(&addrs, api.NodeAddress{ Type:    api.NodeExternalIP, Address: srv.AccessIPv6, }, ) } return addrs, nil </ins> } <del> func getAddressByName(api *gophercloud.ServiceClient, name string) (string, error) { srv, err := getServerByName(api, name) </del> <ins> func getAddressByName(client *gophercloud.ServiceClient, name string) (string, error) { addrs, err := getAddressesByName(client, name) </ins> if err != nil { return \"\", err <ins> } else if len(addrs) == 0 { return \"\", ErrNoAddressFound </ins> } <del> var s string if s == \"\" { if tmp := findAddrs(srv.Addresses[\"private\"]); len(tmp) >= 1 { s = tmp[0] } } if s == \"\" { if tmp := findAddrs(srv.Addresses[\"public\"]); len(tmp) >= 1 { s = tmp[0] </del> <ins> for _, addr := range addrs { if addr.Type == api.NodeInternalIP { return addr.Address, nil </ins> } } <del> if s == \"\" { s = srv.AccessIPv4 } if s == \"\" { s = srv.AccessIPv6 } if s == \"\" { return \"\", ErrNoAddressFound } return s, nil </del> <ins> return addrs[0].Address, nil </ins> } // Implementation of Instances.CurrentNodeName", "positive_passages": [{"docid": "doc-en-kubernetes-fcd218ff1291684683bf7f5abec9b421b4d5bd08568265528c48e934f7742a2f", "text": "Hi, if we talked about openstack, I expect it not bind to rackspace, although, the kubernetes called RK SDK, But from my understanding, seems RK itself SDK not bind network to \"private\" and \"pubic\". User can define public network with their names, like site-network, for example. or \"testnet\", And for private, it should be seem. For nova list, the addresses, it can have \"OS-EXT-IPS:type\":\"fixed\" or \"OS-EXT-IPS:type\":\"floating\" for floating, I think what you means \"Public\", for fixed, I think its what you means \"Private\". In other words, we'd better to find related information from other fields in nova or neutron infromation. Instead of bind to \"private\" and \"public\" name.\nI this issue and wrote a patch that implements what suggests. I will send a PR soon\nGlad to see some improvements here. And wish to use it if implemented", "commid": "kubernetes_issue_18409", "tokennum": 223}], "negative_passages": []}
{"query_id": "q-en-kubernetes-816a85c3621479d60db4e6522fb3f1b4098b11a8364726b882dd1c8a0e481898", "query": "} trap cleanup EXIT <ins> goarch=$(go env GOARCH) </ins> kind build node-image --image \"$tag\" \"$(pwd)\" <del> curl -L --silent https://github.com/kind-ci/containerd-nightlies/releases/download/$containerd/$containerd-linux-amd64.tar.gz | tar -C \"$tmpdir\" -vzxf - curl -L --silent https://github.com/kind-ci/containerd-nightlies/releases/download/$containerd/runc.amd64 >\"$tmpdir/runc\" </del> <ins> curl -L --silent https://github.com/kind-ci/containerd-nightlies/releases/download/$containerd/$containerd-linux-\"$goarch\".tar.gz | tar -C \"$tmpdir\" -vzxf - curl -L --silent https://github.com/kind-ci/containerd-nightlies/releases/download/$containerd/runc.\"$goarch\" >\"$tmpdir/runc\" </ins> cat >\"$tmpdir/Dockerfile\" <<EOF FROM $tag", "positive_passages": [{"docid": "doc-en-kubernetes-f1fd45d6e4c1b622cbcb5debe7400d2388f299758e0c5fe9f2d35eac274ddbc5", "text": "I am trying to bring up a kind cluster with containerd in order to run e2e test on mac + kind. Not sure whether this is a bug or I missed some prerequisites. Any help would be greatly appreciated :) building the image dra/node:latest works as expected:bringing up the kind cluster failed (seems that kubelet is unhealthy and healthchecked failed) below the control plane logs: below the logs of one worker: successfully bring up the kind cluster with containerd Tried on M2 macbook pro I followed NONE Darwin MacBook-Pro-de- 22.1.0 Darwin Kernel Version 22.1.0: Sun Oct 9 20:19:12 PDT 2022; root:xnu-8792.41.9~3/RELEASEARM64T6020 arm64 arm Darwin No response No response\nThere are no sig labels on this issue. Please add an appropriate label by using one of the following commands: - Please see the for a listing of the SIGs, working groups, and committees available. <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\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nwhat type of mac you're using? for m1/m2 mac, you need to replace the linux-amd64 with linux-arm64(your log seems like using m1/m2 mac which same as the problem I've met before)\nthanks I am going to try that\nping me if you can run e2e on mac. I setup the cluster but failed to run the e2e test..\ncan you please share the exact command you tried and the failure ?\nIf you use a newer version of kind you might not need to clobber the included containerd, not sure what version is required And yes, on M1/M2 you need to use arm binaries/images.\nthis is the command that I tried !", "commid": "kubernetes_issue_117878", "tokennum": 495}], "negative_passages": []}
{"query_id": "q-en-kubernetes-816a85c3621479d60db4e6522fb3f1b4098b11a8364726b882dd1c8a0e481898", "query": "} trap cleanup EXIT <ins> goarch=$(go env GOARCH) </ins> kind build node-image --image \"$tag\" \"$(pwd)\" <del> curl -L --silent https://github.com/kind-ci/containerd-nightlies/releases/download/$containerd/$containerd-linux-amd64.tar.gz | tar -C \"$tmpdir\" -vzxf - curl -L --silent https://github.com/kind-ci/containerd-nightlies/releases/download/$containerd/runc.amd64 >\"$tmpdir/runc\" </del> <ins> curl -L --silent https://github.com/kind-ci/containerd-nightlies/releases/download/$containerd/$containerd-linux-\"$goarch\".tar.gz | tar -C \"$tmpdir\" -vzxf - curl -L --silent https://github.com/kind-ci/containerd-nightlies/releases/download/$containerd/runc.\"$goarch\" >\"$tmpdir/runc\" </ins> cat >\"$tmpdir/Dockerfile\" <<EOF FROM $tag", "positive_passages": [{"docid": "doc-en-kubernetes-360d9c6c864de0dc81a219b1de4cd5a5370dd74d19a3f94773debf0837eaf62c", "text": "It worked for me just fine on M2 machine with this obvious fix for the build script: Here is a test output:\nI'll submit a PR with the fix. Updating the documentation would be also nice to have. I hope and can do that.\nDRA tests fail on kind 0.18.0. Which Containerd version is used there?\nIt was the latest 1.6.x at release time. 1.6 is their LTS branch before 2.0 comes which has some tricky changes for us to deal with (notably the CRI hosts config deprecation which will break all our local registry users :/)\nUnfortunately 1.6 doesn't have CDI support, which DRA depends on. The version used in the build script is 1.6.0-830-g34d078e99, but it was probably built from containerd master after 1.6 was released.\nthanks for providing the details. you could run the e2e as shown by and find the result", "commid": "kubernetes_issue_117878", "tokennum": 212}], "negative_passages": []}
{"query_id": "q-en-kubernetes-81aaaa2c32c35b12422456e05906af40a56154a8f6aa6e4b7d9e0e6fcbc5bf84", "query": "VolumeMounts:  volumeMounts, LivenessProbe: componentProbe(10252, \"/healthz\"), Resources:     componentResources(\"200m\"), <ins> Env:           getProxyEnvVars(), </ins> }, volumes...), kubeScheduler: componentPod(api.Container{ Name:          kubeScheduler,", "positive_passages": [{"docid": "doc-en-kubernetes-dc3be6ce7b42d453edf0753a2cf7546d061a63c2e475384cc9c94a48a05e7f4a", "text": "Is this a request for help? No What keywords did you search in Kubernetes issues before filing this one? http proxy, httpproxy, httpsproxy, AWS, kubeadm, kubectl, cloud-provider Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT Kubernetes version (use ): v1.4.4 Environment: Cloud provider or hardware configuration: kubeadm on EC2 instances on AWS OS (e.g. from /etc/os-release): Ubuntu 16.04.1 LTS Kernel (e.g. ): Linux ip-10-0-133-99 4.4.0-45-generic -Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x8664 x8664 x8664 GNU/Linux Install tools: kubeadm Others: httpproxy, httpsproxy and noproxy set in /etc/environment, Docker config as well on startup scripts that run What happened: won't complete and gets stuck on it's first deployment. When one looks through the logs it shows that the pods are downloading fine but we are stuck due to the kube-controller-manager continually crashing as it can't contact AWS. Elsewhere in kubernetes I see references to and if the AWS cloud provider could use that it would be able to connect as well. From the POD if I manually set httpproxy and httpsproxy and no_proxy I am able to use the AWS CLI without any issues. What you expected to happen: I would expect to successfully complete and use the environment proxies set up on the system so as not to depend on a default Internet Gateway being connected to the VPC just for AWS access. How to reproduce it (as minimally and precisely as possible): Set up a public VPC with Squid set up as a proxy Set up a private VPC peered to the public VPC Set up a master node and run Set up a regular node and run will never fully initialize. If you remove the --cloud-provider aws` then it will complete and nodes will register. Anything else do we need to know:\nwhat do you have in proxy variables ? (env | grep -i proxy) it tries to connect to (tcp 176.32.118.53:443) directly. You're expecting to connect there via proxy ? then do you have something like in your no_proxy ?", "commid": "kubernetes_issue_36573", "tokennum": 535}], "negative_passages": []}
{"query_id": "q-en-kubernetes-81aaaa2c32c35b12422456e05906af40a56154a8f6aa6e4b7d9e0e6fcbc5bf84", "query": "VolumeMounts:  volumeMounts, LivenessProbe: componentProbe(10252, \"/healthz\"), Resources:     componentResources(\"200m\"), <ins> Env:           getProxyEnvVars(), </ins> }, volumes...), kubeScheduler: componentPod(api.Container{ Name:          kubeScheduler,", "positive_passages": [{"docid": "doc-en-kubernetes-984a2b369276e3156e0990106838472387b6975b0768d694bc54d8f6e19402d4", "text": "Unfortunately on the pod itself for the the environment variables aren't passed through. As this is created using I don't have control over the pod definition. So basically none of the *_proxy variables are set inside the pod in the docker image, however if I and export the variables and try to wget that URL it works. Basically I'm hoping we can update to respect and pass the environment variables down to the system pods if they exist, eg, add: Without it I can't stand up a cluster with AWS integration on a completely private VPC and for such a small change it would make a rather big difference.\nok, so request is actually to pass proxy variables into containers. interesting. I'll check how it can be done. BTW, for noproxy value in your example: things like 10.0.0.0/8 would not work on 99% of software that respects noproxy variable. it must be always exact IP match.\nyou're right that what I'm actually asking for is to pass proxy variables through either from a commandline setting on kubeadm or pick it up from /etc/environment or shell environment that launches kubeadm. I didn't realize it till I dug in to try and think about how one might go about fixing this. At first I thought we would just pick up the variables from the system environment but then I realized kube-controller-manager is deployed in a container and so we'd need to update the yaml file that launches it to contain the environment variables. As I'd like to go to production with this soon hopefully this is a small change that can be .\nThis issue was moved to kubernetes/kubeadm", "commid": "kubernetes_issue_36573", "tokennum": 362}], "negative_passages": []}
{"query_id": "q-en-kubernetes-81d112ed7a6a330977489c27dde8641533e82f081855863b4e5ed8ae471b388c", "query": "dial = (&net.Dialer{Timeout: 30 * time.Second, KeepAlive: 30 * time.Second}).DialContext } d := connrotation.NewDialer(dial) <del> a.onRotate = d.CloseAll </del> <ins> a.mu.Lock() defer a.mu.Unlock() a.onRotateList = append(a.onRotateList, d.CloseAll) onRotateListLength := len(a.onRotateList) if onRotateListLength > onRotateListWarningLength { klog.Warningf(\"constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust available network connections; %d clients constructed calling %q\", onRotateListLength, a.cmd) } </ins> c.Dial = d.DialContext return nil", "positive_passages": [{"docid": "doc-en-kubernetes-d5f405b98ac26e68bb52a403345cda18a0b690bbcb8385b5ec06372b302c6e2d", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Data race in client-go with below sample code: Data race: What you expected to happen: No data race How to reproduce it (as minimally and precisely as possible): Using above given sample code Kubernetes version (use ):Cloud provider or hardware configuration:OS (e.g: ): OSX\n/sig api-machinery\nI'd like to take it. /assign\n/remove-sig api-machinery /sig auth cli\nBug triage for release 1.17 here. Since this issue has been tagged for the milestone, we would like to check it's status. Code freeze is on Nov. 14. Will this issue be resolved before then?\nAnother reminder here that code freeze is in less than two weeks (Nov. 14). We will need to move this issue out of the milestone if isn't going to be resolved before then.", "commid": "kubernetes_issue_80269", "tokennum": 239}], "negative_passages": []}
{"query_id": "q-en-kubernetes-81d68fbf27852a57afe694945a19509f573f04cc3e125b35f2b3dac52be8ee18", "query": "fs.StringVar(&o.ConfigFile, \"config\", o.ConfigFile, \"The path to the configuration file.\") fs.StringVar(&o.WriteConfigTo, \"write-config-to\", o.WriteConfigTo, \"If set, write the default configuration values to this file and exit.\") fs.StringVar(&o.config.ClientConnection.Kubeconfig, \"kubeconfig\", o.config.ClientConnection.Kubeconfig, \"Path to kubeconfig file with authorization information (the master location can be overridden by the master flag).\") <del> fs.StringVar(&o.config.ClusterCIDR, \"cluster-cidr\", o.config.ClusterCIDR, \"The CIDR range of pods in the cluster. When configured, traffic sent to a Service cluster IP from outside this range will be masqueraded and traffic sent from pods to an external LoadBalancer IP will be directed to the respective cluster IP instead\") </del> <ins> fs.StringVar(&o.config.ClusterCIDR, \"cluster-cidr\", o.config.ClusterCIDR, \"The CIDR range of pods in the cluster. When configured, traffic sent to a Service cluster IP from outside this range will be masqueraded and traffic sent from pods to an external LoadBalancer IP will be directed to the respective cluster IP instead. This parameter is ignored if a config file is specified by --config.\") </ins> fs.StringVar(&o.config.ClientConnection.ContentType, \"kube-api-content-type\", o.config.ClientConnection.ContentType, \"Content type of requests sent to apiserver.\") fs.StringVar(&o.master, \"master\", o.master, \"The address of the Kubernetes API server (overrides any value in kubeconfig)\") fs.StringVar(&o.hostnameOverride, \"hostname-override\", o.hostnameOverride, \"If non-empty, will use this string as identification instead of the actual hostname.\")", "positive_passages": [{"docid": "doc-en-kubernetes-d25af00145ce02f273723fdbada2e8cd6b506acebe2a7cb4f99e67bf0c6cc038", "text": "Start service with a config file without specifying the argument in the config file, instead, pass the value via the CLI args, the value is just ignored, for example, I have a config file as this, NOTE: I have not specified the in the config file, but give a value for the via the CLI, the proxy mode is still set as after the service is started. The reason for this is that CLI args is parsed before the loading of the config file, if the config file haven't specified the or leave it as empty, then it will be use the default value instead. Two choices from my side, Add a note somewhere, maybe where the option is defined, just say that the CLI args will be ignored when the config file is provided regardless the option is specified in the config file or not (this should be noted for lots of options). Merge the value passed from CLI with the config file if the option has an empty value, but we need to consider the backward compatibility. and check which mode is effective. No response_ vanilla deployment with code in the upstream. <details</details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig network Hey Tim, WDYT? /assign\nHeh, this is a recurrent topic :smile: , you did a great analysis: I think that explains here why merging flags and config overriding defaults is not a desirable option (the whole thread is worth reading) I'm in favor of documenting the behavior\nthanks for showing the earlier thread, I have created a simple PR to document this in the CLI option.", "commid": "kubernetes_issue_107156", "tokennum": 446}], "negative_passages": []}
{"query_id": "q-en-kubernetes-825f3807cfa161a4ddffe2e8ab04417734cc47ff6f0541094e56f197b9659dba", "query": "<del> /* Copyright 2023 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package plugin import ( \"context\" \"fmt\" \"net\" \"os\" \"path/filepath\" \"sync\" \"testing\" \"github.com/stretchr/testify/assert\" \"google.golang.org/grpc\" drapb \"k8s.io/kubelet/pkg/apis/dra/v1alpha4\" \"k8s.io/kubernetes/test/utils/ktesting\" ) const ( v1alpha4Version = \"v1alpha4\" ) type fakeV1alpha4GRPCServer struct { drapb.UnimplementedNodeServer } var _ drapb.NodeServer = &fakeV1alpha4GRPCServer{} func (f *fakeV1alpha4GRPCServer) NodePrepareResources(ctx context.Context, in *drapb.NodePrepareResourcesRequest) (*drapb.NodePrepareResourcesResponse, error) { return &drapb.NodePrepareResourcesResponse{Claims: map[string]*drapb.NodePrepareResourceResponse{\"claim-uid\": { Devices: []*drapb.Device{ { RequestNames: []string{\"test-request\"}, CDIDeviceIDs: []string{\"test-cdi-id\"}, }, }, }}}, nil } func (f *fakeV1alpha4GRPCServer) NodeUnprepareResources(ctx context.Context, in *drapb.NodeUnprepareResourcesRequest) (*drapb.NodeUnprepareResourcesResponse, error) { return &drapb.NodeUnprepareResourcesResponse{}, nil } type tearDown func() func setupFakeGRPCServer(version string) (string, tearDown, error) { p, err := os.MkdirTemp(\"\", \"dra_plugin\") if err != nil { return \"\", nil, err } closeCh := make(chan struct{}) addr := filepath.Join(p, \"server.sock\") teardown := func() { close(closeCh) os.RemoveAll(addr) } listener, err := net.Listen(\"unix\", addr) if err != nil { teardown() return \"\", nil, err } s := grpc.NewServer() switch version { case v1alpha4Version: fakeGRPCServer := &fakeV1alpha4GRPCServer{} drapb.RegisterNodeServer(s, fakeGRPCServer) default: return \"\", nil, fmt.Errorf(\"unsupported version: %s\", version) } go func() { go s.Serve(listener) <-closeCh s.GracefulStop() }() return addr, teardown, nil } func TestGRPCConnIsReused(t *testing.T) { tCtx := ktesting.Init(t) addr, teardown, err := setupFakeGRPCServer(v1alpha4Version) if err != nil { t.Fatal(err) } defer teardown() reusedConns := make(map[*grpc.ClientConn]int) wg := sync.WaitGroup{} m := sync.Mutex{} p := &Plugin{ backgroundCtx:     tCtx, endpoint:          addr, clientCallTimeout: defaultClientCallTimeout, } conn, err := p.getOrCreateGRPCConn() defer func() { err := conn.Close() if err != nil { t.Error(err) } }() if err != nil { t.Fatal(err) } // ensure the plugin we are using is registered draPlugins.add(\"dummy-plugin\", p) defer draPlugins.delete(\"dummy-plugin\") // we call `NodePrepareResource` 2 times and check whether a new connection is created or the same is reused for i := 0; i < 2; i++ { wg.Add(1) go func() { defer wg.Done() client, err := NewDRAPluginClient(\"dummy-plugin\") if err != nil { t.Error(err) return } req := &drapb.NodePrepareResourcesRequest{ Claims: []*drapb.Claim{ { Namespace: \"dummy-namespace\", UID:       \"dummy-uid\", Name:      \"dummy-claim\", }, }, } _, err = client.NodePrepareResources(tCtx, req) assert.NoError(t, err) client.mutex.Lock() conn := client.conn client.mutex.Unlock() m.Lock() defer m.Unlock() reusedConns[conn]++ }() } wg.Wait() // We should have only one entry otherwise it means another gRPC connection has been created if len(reusedConns) != 1 { t.Errorf(\"expected length to be 1 but got %d\", len(reusedConns)) } if counter, ok := reusedConns[conn]; ok && counter != 2 { t.Errorf(\"expected counter to be 2 but got %d\", counter) } } func TestNewDRAPluginClient(t *testing.T) { for _, test := range []struct { description string setup       func(string) tearDown pluginName  string shouldError bool }{ { description: \"plugin name is empty\", setup: func(_ string) tearDown { return func() {} }, pluginName:  \"\", shouldError: true, }, { description: \"plugin name not found in the list\", setup: func(_ string) tearDown { return func() {} }, pluginName:  \"plugin-name-not-found-in-the-list\", shouldError: true, }, { description: \"plugin exists\", setup: func(name string) tearDown { draPlugins.add(name, &Plugin{}) return func() { draPlugins.delete(name) } }, pluginName: \"dummy-plugin\", }, } { t.Run(test.description, func(t *testing.T) { teardown := test.setup(test.pluginName) defer teardown() client, err := NewDRAPluginClient(test.pluginName) if test.shouldError { assert.Nil(t, client) assert.Error(t, err) } else { assert.NotNil(t, client) assert.Nil(t, err) } }) } } func TestNodeUnprepareResources(t *testing.T) { for _, test := range []struct { description   string serverSetup   func(string) (string, tearDown, error) serverVersion string request       *drapb.NodeUnprepareResourcesRequest }{ { description:   \"server supports v1alpha4\", serverSetup:   setupFakeGRPCServer, serverVersion: v1alpha4Version, request:       &drapb.NodeUnprepareResourcesRequest{}, }, } { t.Run(test.description, func(t *testing.T) { tCtx := ktesting.Init(t) addr, teardown, err := setupFakeGRPCServer(test.serverVersion) if err != nil { t.Fatal(err) } defer teardown() p := &Plugin{ backgroundCtx:     tCtx, endpoint:          addr, clientCallTimeout: defaultClientCallTimeout, } conn, err := p.getOrCreateGRPCConn() defer func() { err := conn.Close() if err != nil { t.Error(err) } }() if err != nil { t.Fatal(err) } draPlugins.add(\"dummy-plugin\", p) defer draPlugins.delete(\"dummy-plugin\") client, err := NewDRAPluginClient(\"dummy-plugin\") if err != nil { t.Fatal(err) } _, err = client.NodeUnprepareResources(tCtx, test.request) if err != nil { t.Fatal(err) } }) } } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-e1c6f7407b346df6fb6212f23a2f930e04198e198bb03b9cff5041967802082d", "text": "The PR above moved everything related to into because that was where most of the code already was, but didn't renamed the files to avoid a larger diff and merge conflicts. Once is merged, we can do the renaming. Code clarity. /sig node\n/triage accepted /priority important-soon\n/assign\na PR can be created for this now.\nwill do", "commid": "kubernetes_issue_125924", "tokennum": 75}], "negative_passages": []}
{"query_id": "q-en-kubernetes-82714b23078de7d9c916a4ec258ac0f36c10a97c8448b15fa39ab417c21257e5", "query": ") const ( <del> // When these values are updated, also update test/e2e/framework/util.go </del> <ins> // When these values are updated, also update test/utils/image/manifest.go </ins> defaultPodSandboxImageName    = \"gcr.io/google_containers/pause\" <del> defaultPodSandboxImageVersion = \"3.0\" </del> <ins> defaultPodSandboxImageVersion = \"3.1\" </ins> // From pkg/kubelet/rkt/rkt.go to avoid circular import defaultRktAPIServiceEndpoint = \"localhost:15441\" )", "positive_passages": [{"docid": "doc-en-kubernetes-a834f77ddd825b3d04a660aa7c11d0734893e4dcde6e0d4a7399e3b3daf56428", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: the pause-amd64:3.0 image on has an empty schema2 manifest, which prevents is from being pulled by proxy/caches which only support V2 registries. What you expected to happen: Being able to pull ` using a V2 manifest compatible client. Anything else we need to know?: The proxy/cahce is requesting this\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nAfter talking with , he mentionned the following\nAFAIK, does not support well. After inspecting the image, you can find is still using manifest v1.\n/cc FYI\nIm not sure which exact version x sch\u00e9ma X is needed. What I know is that we can download through the proxy/cache all other Kubernetes kube-system images, only the pause image is giving us trouble. Therefore, I would say that having the image available using the same format as the other kube-system images would be the request here.\nYeah, we haven't updated the pause image in a while, since it doesn't really ever change. I'm not sure whether rebuilding + pushing over the existing tag is safe, or if we should bump to or something. thoughts?\nIf we do rebuilding/updating the image, that would help and a bunch of similar issues.\nit's better/save to go with new tag\nI didn't realize there were changes to the pause binary that were never actually deployed. It seems like we should probably just do that (and bump the tag).\nthat sounds great. Any idea when the existing 3.0 tag could be pushed again?\nWe shouldn't push over the 3.0 tag; we should push a 3.1 or 4.0 tag instead. I'm not sure who owns the pause container who should drive this. Maybe sig-node and/or\nIt seems like it should be sig-node. I'll look into it.\nThe new container has been built, can you test with\nIts working! thanks! I was able to pull it through our artifactory proxy , Lee Verberne <:\nexcellent, thanks for checking. /assign", "commid": "kubernetes_issue_56253", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-82714b23078de7d9c916a4ec258ac0f36c10a97c8448b15fa39ab417c21257e5", "query": ") const ( <del> // When these values are updated, also update test/e2e/framework/util.go </del> <ins> // When these values are updated, also update test/utils/image/manifest.go </ins> defaultPodSandboxImageName    = \"gcr.io/google_containers/pause\" <del> defaultPodSandboxImageVersion = \"3.0\" </del> <ins> defaultPodSandboxImageVersion = \"3.1\" </ins> // From pkg/kubelet/rkt/rkt.go to avoid circular import defaultRktAPIServiceEndpoint = \"localhost:15441\" )", "positive_passages": [{"docid": "doc-en-kubernetes-7628cd26f0dafa992a4ea43a6c68b9bcdbf056fca43ee32b40ab60cef4154c17", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: pause does not reap zombie processes using the default pause container provided by What you expected to happen: should include the up to date pause code to reap zombie processes when using docker = 1.13.1 found here How to reproduce it (as minimally and precisely as possible): a.out will leave a zombie process that is not cleaned up Anything else we need to know?: Building the pause container from master solves this issue Related: Environment: Kubernetes version (use ): 1.7.0+ Cloud provider or hardware configuration**: N/A OS (e.g. from /etc/os-release): CentOS 7 Kernel (e.g. ): 4.10.13+ Install tools: Others: docker = 1.13.1\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\ni get a simliar problem when i run crond service in pod container, every day it makes some [anacron] zombie progresses UID PID PPID C STIME TTY TIME CMD root 1 0 0 Nov14 ? 00:00:00 /pause root 7 0 0 Nov14 ? 00:00:00 /usr/local/bin/dumb-init /usr/lo root 13 7 0 Nov14 ? 00:00:00 nginx: master process /usr/local nobody 21 13 0 Nov14 ? 00:00:01 nginx: worker process nobody 22 13 0 Nov14 ? 00:00:07 nginx: worker process nobody 23 13 0 Nov14 ? 00:00:07 nginx: worker process nobody 24 13 0 Nov14 ? 00:00:05 nginx: worker process root 77 1 0 Nov14 ? 00:00:00 [anacron] root 1 0 00:01 ? 00:00:00 [anacron] <defunctroot 1 0 01:01 ? 00:00:00 [anacron] <defunctroot 1 0 02:01 ?", "commid": "kubernetes_issue_50865", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-82714b23078de7d9c916a4ec258ac0f36c10a97c8448b15fa39ab417c21257e5", "query": ") const ( <del> // When these values are updated, also update test/e2e/framework/util.go </del> <ins> // When these values are updated, also update test/utils/image/manifest.go </ins> defaultPodSandboxImageName    = \"gcr.io/google_containers/pause\" <del> defaultPodSandboxImageVersion = \"3.0\" </del> <ins> defaultPodSandboxImageVersion = \"3.1\" </ins> // From pkg/kubelet/rkt/rkt.go to avoid circular import defaultRktAPIServiceEndpoint = \"localhost:15441\" )", "positive_passages": [{"docid": "doc-en-kubernetes-6179feaaee46a15cd909bb088c82657b9b59fba8efdee1296995076588512032", "text": "00:00:00 [anacron] <defunctroot 1 0 03:01 ? 00:00:00 [anacron] <defunctroot 0 0 11:49 ? 00:00:00 /bin/bash root 0 1 19:15 ? 00:00:00 /bin/bash root 0 19:15 ? 00:00:00 ps -ef !\nDo we know why this was never resolved / was never deployed?\nI just fought through this issue with a rabbitmq helm chart. I had to custom build a pause container from master to fix it. The rabbitmq helm chart uses for its liveness checks. It's a thin wrapper around a call to the rabbitmq-server daemon, which is not PID 1 (/pause is PID 1). The rabbitmq-server process forks some children to do the work and then they exit. Since the pause-amd64:3.0 is not reaping, those processes stick around as zombies. The liveness check runs every 5 seconds. After about 4 hours, there are about 27K zombies and the node begins failing to launch new containers because it's starved for resources. The pause container built from current master fixes that behavior, no zombies at all in the container.\nThe plan is to build a new version of pause-amd64 and then update the image referenced by Kubernetes. This means the default image will change in the next Kubernetes release. We can make the new image available once the freeze lifts and we can merge .\nLooks like this made it into 1.10", "commid": "kubernetes_issue_50865", "tokennum": 336}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8282b9d5dab86a982db92cd7c9d2b87c04c469a0395a8eeacb6c44bda3d91424", "query": "e := exec.New() hostIfName, err := findPairInterfaceOfContainerInterface(e, containerInterfaceName, containerDesc, nsenterArgs) if err != nil { <del> glog.Infof(\"Unable to find pair interface, setting up all interfaces: %v\", err) return setUpAllInterfaces() </del> <ins> return err </ins> } return setUpInterface(hostIfName) }", "positive_passages": [{"docid": "doc-en-kubernetes-1338c1265dc2da957b27c9fcf90bf88eaa9473c2ffb7e29c3dbb2785dec4e5f0", "text": "From another issue, said: DockerManager.SyncPod() calls the network Plugin and then sets hairpin mode unilaterally. This is wrong. We should either pass the bool down to here or else we should get rid of the default no-op plugin and use the non-existence of a plugin as a flag to control this. This should be a relatively easy one for people who want to contribute but don't know where to start.\nI volunteer myself to do this. Actually I have done something about kubernetes network plugin so guess I can do this. I will start to do this when I am on the office tomorrow.\nAwesome. I'd advise starting with a sketch so we can all make sure it is a good approach, before jumping in with both feet. , TonyAdo wrote:\nok, I will start with a sketch as soon as possible.\nI thought about this for a while: if we pass the bool down to here, of course we can check this flag, if it is set, we should set veth hairpin mode, but problem is that if user set this flag, but still use a custom network plugin just like you mentioned the ovs plugin, I am afraid we will still enable hairpin mode in all interfaces on this host, since we cannot find a peer interface. Is that correct?\nYeah, I think the better fix is to use the existence of a network plugin as an indicator. It sort of makes --configure-cbr0 redundant , TonyAdo wrote:\nok, I will try to get rid of the default no-op plugin and use the non-existence of a plugin as a flag to control this.\nI decided to use the existence of a network plugin as an indicator, also I will get ride of the no-op network plugin, I am not going to add new flag to kubelet structure, if the user don't specify network plugin name, the networkPlugin within kubelet will be which just means non-existence of a plugin, and we have to check the existence in the docker manager to avoid nil pointer exception also for setting, I think if a custom network plugin exists, kubelet should not do this. How about this? Should I open a PR?\nfyi, saw a hairpin pr today that might be related. ymmv.\nwhat do you think about this?\nWhat you described sounds right to me.", "commid": "kubernetes_issue_19766", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8282b9d5dab86a982db92cd7c9d2b87c04c469a0395a8eeacb6c44bda3d91424", "query": "e := exec.New() hostIfName, err := findPairInterfaceOfContainerInterface(e, containerInterfaceName, containerDesc, nsenterArgs) if err != nil { <del> glog.Infof(\"Unable to find pair interface, setting up all interfaces: %v\", err) return setUpAllInterfaces() </del> <ins> return err </ins> } return setUpInterface(hostIfName) }", "positive_passages": [{"docid": "doc-en-kubernetes-63d22d436297e1e341b6c3c9db0f8b916cd9a8fc746e2ad0128076b35b0cb5ac", "text": "I think the only way to see if there is some detail I am missing is to try it and see if anything pops up that would make this not work. , TonyAdo wrote:\nI need to check which part is responsible of what, but what if the hairpin package was just a utility package that should be called by the plugin if it needs to set this up? As long as it is single and simple function call, doing so would avoid adding extra logic here and fix the issue. This is valid only if the aim is to have a \"linux bridge plugin\", an \"OVS plugin\", etc.\nactually kubelet will call after get called, I think to make the network plugin can call hairpin package is not that easy, of course, I agree that network plugin should setup hairpin mode if it really needs, kubelet should not set hairpin mode unilaterally. Besides, kubelet is not going to provide an \"linux bridge plugin\" or \"OVS plugin\".\nthen the validity conditions of my comment are not met, so I see any simpler way. Thanks for checking! :)\nstill what do you think about disable hairpin completely and leave this to network plugin?\nor if there is a custom network plugin, we don't setup hairpin mode, only do this in default.\nCompletely? It will break my use case (and anyone using Apache Kafka).\nOnly by default is what I understood from the previous comments, and LGTM.\nReally sorry about that, but I really want to know are you using a kubelet network plugin in your use case? If no, I think we will still setup hairpin, as in default we will do this.\nI don't use any plugin, so it is ok if hairpin is set up by default.\nok, I think this will not break your use case.\nIt's not really the network plugin that needs hairpinmode though, it's the pure-iptables-based kube-proxy code. It's possible the proxying code could change again in the future in such a way that hairpinmode wouldn't be needed any more. So it seems wrong to put that code into the plugin. makes it so that we set hairpinmode on the veth if it's attached to a bridge, but just silently do nothing if it's not.", "commid": "kubernetes_issue_19766", "tokennum": 509}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8282b9d5dab86a982db92cd7c9d2b87c04c469a0395a8eeacb6c44bda3d91424", "query": "e := exec.New() hostIfName, err := findPairInterfaceOfContainerInterface(e, containerInterfaceName, containerDesc, nsenterArgs) if err != nil { <del> glog.Infof(\"Unable to find pair interface, setting up all interfaces: %v\", err) return setUpAllInterfaces() </del> <ins> return err </ins> } return setUpInterface(hostIfName) }", "positive_passages": [{"docid": "doc-en-kubernetes-3bf0b78c82438b679aab4fecf6e8905cfec517728c795c679dfaefb3dd282eea", "text": "(Yes, we currently set hairpinmode even if you're using the userspace proxier, but AFAIK it's not needed in that case.)\nIMHO... The proxy has the responsibility of service objects, while the kubelet is responsible of pod objects, including their networking. Also, the responsibility of hairpin must be at the same place as the code that creates the network interface, otherwise you have code managing a single object (the pod interface) spread over multiple programs, which will eventually lead to complex problems and a system harder to understand even for the end-user. Thus, it doesn't seems wrong to me that the kubelet does whatever is required to make the pod work in the environment of the cluster. While its true that the hairpin requirement is only for the proxy in iptables mode, a switch to this mode can happen at any time in the life of the cluster. And when it happens, its probably because the userland proxy becomes unresponsive, which means in a situation where the administrator is in a hurry to find a solution. Currently, you just change the proxy mode and restart the proxies. There's little chance the administrator will think about hairpin or restarting the kubelet in this case, so the kubelet should be reacting to this; which means the proxy and the kubelet of a given host should be able to communicate (AFAIK, this doesn't exist now). And all this is currently only to avoid setting up hairpin on the pod's port of standard Linux bridge.\nFeel sure I'm missing something but... The CNI bridge plugin now has a flag, so kubenet can use that. Having done that, we can set false when the plugin name is non-blank.\nIs this fixed now?\nI apologise for leaving a somewhat vague answer, but I have been in that code recently. I don't think it's fixed.\n, Bryan Boreham wrote:\nThanks for the PR. CNI Bridge plugin is expecting . Not . Hence the bridge plugin did not recognize it.\nEDIT 2016-12-09: The chain below was broken by , so the issue can be closed again (remain closed) I suggest this should be re-opened. The chain of calls is: sets to , e.g. when using CNI calls something goes wrong and it sets the mode on everything. An example of \"something goes wrong\":", "commid": "kubernetes_issue_19766", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8283226613d2840ca538cf66f5aaf63662cfe5cb84446edefd3c3dff96025a6d", "query": "framework.ExpectNoError(verifyServeHostnameServiceUp(cs, ns, host, podNames2, svc2IP, servicePort)) }) <del> ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a NodePort service\", func() { serviceName := \"clusterip-test\" serverPod1Name := \"server-1\" serverPod2Name := \"server-2\" ns := f.Namespace.Name nodeIP, err := e2enode.PickIP(cs) // for later framework.ExpectNoError(err) // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=NodePort in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeNodePort svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"http\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Add a backend pod to the service ginkgo.By(\"creating a backend pod for the service \" + serviceName) serverPod1 := newAgnhostPod(serverPod1Name, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels _, err = cs.CoreV1().Pods(ns).Create(context.TODO(), serverPod1, metav1.CreateOptions{}) ginkgo.By(fmt.Sprintf(\"checking NodePort service %s on node with public IP %s\", serviceName, nodeIP)) framework.ExpectNoError(err) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, serverPod1.Name, f.Namespace.Name, framework.PodStartTimeout)) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{serverPod1Name: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod reveives the traffic ginkgo.By(\"Sending UDP traffic to NodePort service \" + serviceName + \" on node with publicIP \" + nodeIP) errorChannel := make(chan error) signal := make(chan struct{}, 1) go continuousEcho(nodeIP, int(udpService.Spec.Ports[0].NodePort), 3*time.Second, 20, signal, errorChannel) // Create a second pod ginkgo.By(\"creating a second pod for the service \" + serviceName) serverPod2 := newAgnhostPod(serverPod2Name, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels _, err = cs.CoreV1().Pods(ns).Create(context.TODO(), serverPod2, metav1.CreateOptions{}) framework.ExpectNoError(err) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, serverPod2.Name, f.Namespace.Name, framework.PodStartTimeout)) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", serverPod1Name) err = cs.CoreV1().Pods(ns).Delete(context.TODO(), serverPod1Name, metav1.DeleteOptions{}) framework.ExpectNoError(err, \"failed to delete pod: %s on node\", serverPod1Name) // Check that the second pod keeps receiving traffic ginkgo.By(\"Sending UDP traffic to NodePort service \" + serviceName + \" on node with publicIP \" + nodeIP) signal <- struct{}{} // Check that there are no errors err = <-errorChannel framework.ExpectNoError(err, \"pod communication failed\") }) </del> /* Release : v1.16 Testname: Service, NodePort Service", "positive_passages": [{"docid": "doc-en-kubernetes-7bfb1f284722c2f05aa84834ae56662d5ec19fb895a91cc774b04328b8cdc59d", "text": "Which jobs are flaking: ci-kubernetes-e2e-gce-scale-correctness Which test(s) are flaking: [sig-network] Services should be able to preserve UDP traffic when server pod cycles for a NodePort service Testgrid link: https://k8s- Reason for failure: /sig network /assign\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nCRI-O CI is also hitting this failure. We have been unable to reproduce locally. our CI runs on aws\nhmm, I only see 1 failure out of 4 and seems that the connectivity didn't work at all\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\n/assign\nGitHub didn't allow me to assign the following users: JacobTanenbaum. 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\n/cc Saw the test flaking recently: Wondering if this is just a timeout issue.", "commid": "kubernetes_issue_91236", "tokennum": 320}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8283226613d2840ca538cf66f5aaf63662cfe5cb84446edefd3c3dff96025a6d", "query": "framework.ExpectNoError(verifyServeHostnameServiceUp(cs, ns, host, podNames2, svc2IP, servicePort)) }) <del> ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a NodePort service\", func() { serviceName := \"clusterip-test\" serverPod1Name := \"server-1\" serverPod2Name := \"server-2\" ns := f.Namespace.Name nodeIP, err := e2enode.PickIP(cs) // for later framework.ExpectNoError(err) // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=NodePort in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeNodePort svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"http\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Add a backend pod to the service ginkgo.By(\"creating a backend pod for the service \" + serviceName) serverPod1 := newAgnhostPod(serverPod1Name, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels _, err = cs.CoreV1().Pods(ns).Create(context.TODO(), serverPod1, metav1.CreateOptions{}) ginkgo.By(fmt.Sprintf(\"checking NodePort service %s on node with public IP %s\", serviceName, nodeIP)) framework.ExpectNoError(err) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, serverPod1.Name, f.Namespace.Name, framework.PodStartTimeout)) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{serverPod1Name: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod reveives the traffic ginkgo.By(\"Sending UDP traffic to NodePort service \" + serviceName + \" on node with publicIP \" + nodeIP) errorChannel := make(chan error) signal := make(chan struct{}, 1) go continuousEcho(nodeIP, int(udpService.Spec.Ports[0].NodePort), 3*time.Second, 20, signal, errorChannel) // Create a second pod ginkgo.By(\"creating a second pod for the service \" + serviceName) serverPod2 := newAgnhostPod(serverPod2Name, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels _, err = cs.CoreV1().Pods(ns).Create(context.TODO(), serverPod2, metav1.CreateOptions{}) framework.ExpectNoError(err) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, serverPod2.Name, f.Namespace.Name, framework.PodStartTimeout)) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", serverPod1Name) err = cs.CoreV1().Pods(ns).Delete(context.TODO(), serverPod1Name, metav1.DeleteOptions{}) framework.ExpectNoError(err, \"failed to delete pod: %s on node\", serverPod1Name) // Check that the second pod keeps receiving traffic ginkgo.By(\"Sending UDP traffic to NodePort service \" + serviceName + \" on node with publicIP \" + nodeIP) signal <- struct{}{} // Check that there are no errors err = <-errorChannel framework.ExpectNoError(err, \"pod communication failed\") }) </del> /* Release : v1.16 Testname: Service, NodePort Service", "positive_passages": [{"docid": "doc-en-kubernetes-7ebfc2af23ebf8477a19d5b139a7e0f62f200d8158a5532a965c9eb49bf73a96", "text": "Maybe we can increase the timeout and/or switch to a TCP based test:\nthe test should use UDP, and UDP is unreliable by definition ... however is curious that most of the failures happen because it is not able to communicate with the first pod I think that is something that should be investigated, I've analyzed some occurences and it works fine for the second pod, however, the UDP losses should be totally random\nHi everyone, yeah so.. collecting some data on this... using a two node kind cluster, locally, with the antrea plugin, it passes using a 4 node AWS cluster with the antrea CNI plugin, it failed using a two node kidn cluster locally with calico, it passes So I guess the best reproducer is to run these tests, for now, in the cloud.... Now that I have a reproducer for this maybe can live debug it some time next wk with one of yall :)\nbear in mind that this test is connecting to a nodePort in the node IP, the test is functionally correct, it may be flaky due to the unreliable UDP nature or due to the pod scheduling, but if is failing constantly it has to be environmental.\nSecond failure after two weeks of green 5k runs:\nyep, :/ https://k8s-|UDP /assign\n/reopen I'm afraid this is going to be challenging :smile: The difference now is that we are testing NodePort and ClusterIP If both fail, we can blame the test for sure, If only NodePort fails, we need to check the job, if GCE or KIND If only ClusterIP fails, ... :thinking:\nReopened this issue. <detailsIn response to : /reopen I'm afraid this is going to be challenging :smile: 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\nWe're hitting this really frequently in 5k-node tests. So I started looking a little bit into that.", "commid": "kubernetes_issue_91236", "tokennum": 445}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8283226613d2840ca538cf66f5aaf63662cfe5cb84446edefd3c3dff96025a6d", "query": "framework.ExpectNoError(verifyServeHostnameServiceUp(cs, ns, host, podNames2, svc2IP, servicePort)) }) <del> ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a NodePort service\", func() { serviceName := \"clusterip-test\" serverPod1Name := \"server-1\" serverPod2Name := \"server-2\" ns := f.Namespace.Name nodeIP, err := e2enode.PickIP(cs) // for later framework.ExpectNoError(err) // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=NodePort in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeNodePort svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"http\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Add a backend pod to the service ginkgo.By(\"creating a backend pod for the service \" + serviceName) serverPod1 := newAgnhostPod(serverPod1Name, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels _, err = cs.CoreV1().Pods(ns).Create(context.TODO(), serverPod1, metav1.CreateOptions{}) ginkgo.By(fmt.Sprintf(\"checking NodePort service %s on node with public IP %s\", serviceName, nodeIP)) framework.ExpectNoError(err) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, serverPod1.Name, f.Namespace.Name, framework.PodStartTimeout)) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{serverPod1Name: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod reveives the traffic ginkgo.By(\"Sending UDP traffic to NodePort service \" + serviceName + \" on node with publicIP \" + nodeIP) errorChannel := make(chan error) signal := make(chan struct{}, 1) go continuousEcho(nodeIP, int(udpService.Spec.Ports[0].NodePort), 3*time.Second, 20, signal, errorChannel) // Create a second pod ginkgo.By(\"creating a second pod for the service \" + serviceName) serverPod2 := newAgnhostPod(serverPod2Name, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels _, err = cs.CoreV1().Pods(ns).Create(context.TODO(), serverPod2, metav1.CreateOptions{}) framework.ExpectNoError(err) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, serverPod2.Name, f.Namespace.Name, framework.PodStartTimeout)) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", serverPod1Name) err = cs.CoreV1().Pods(ns).Delete(context.TODO(), serverPod1Name, metav1.DeleteOptions{}) framework.ExpectNoError(err, \"failed to delete pod: %s on node\", serverPod1Name) // Check that the second pod keeps receiving traffic ginkgo.By(\"Sending UDP traffic to NodePort service \" + serviceName + \" on node with publicIP \" + nodeIP) signal <- struct{}{} // Check that there are no errors err = <-errorChannel framework.ExpectNoError(err, \"pod communication failed\") }) </del> /* Release : v1.16 Testname: Service, NodePort Service", "positive_passages": [{"docid": "doc-en-kubernetes-5846160d0947d31469e9f6af93fd879e379d05716d3adf8932316babb4b3ae6c", "text": "I don't have full understanding of what exactly is happening, but I already see a couple things that may be causing issues: when creating the first pod, you wait for corresponding endpoint for that being created; but that doesn't mean that kube-proxy was actually programmed correctly at that time (in general it isn't); given iptables programming is rate-limitted, it may easily happen that actually programming happens 10s+ later That explains some delays, but it doesn't explain e.g. this run: where iptables were programmed at but the test didn't respond until If someone more familiar with networking stuff could look into it, it would be great. - can you help triaging ^^ for deletions it's even worse, because you don't even wait for endpoints to be there (i.e. Endpoints can still contain the old pod when the test start pinging to look for the second one) So I claim that timeouts are visibly to low in this test, but I suspect it's not everything. I will send out the first PR that tries to improve it in couple minutes.\nthanks wojtek, have been slammed but Ill try to collect more data on it this wknd as well.\nIt seems that my PR didn't really help much. We should dig deeper, but I would need someone with more networking expertise to look a bit into\nActually - it seems only failures from one group are on non . So maybe that's actually related. The non-kind related ones look like:\nOK - for this one, I actually know what is happening - I will send out a PR with a fix for this too.\nfor the KIND jobs already increased the resource requests on some of the jobs, there are issues on KIND jobs with kube-proxy not able to take the iptables lock and not being able to create the iptables rules for the services until the next resync\nis to fix the flakes I mentioned above; all other flakes seem to be kind-oriented to me (which I'm not super familiar with).\nWe did not adjust the CPU on all jobs yet, pending how to manage that on prow ... I do see just a few other flakes at the bottom of the triage dashboard that look like timeouts instead.\nActually - almost all failures are effectively timeout. The top one that is is actually also a timeout. Didn't look into kind failures, but this may easily be related to iptables issues.", "commid": "kubernetes_issue_91236", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8283226613d2840ca538cf66f5aaf63662cfe5cb84446edefd3c3dff96025a6d", "query": "framework.ExpectNoError(verifyServeHostnameServiceUp(cs, ns, host, podNames2, svc2IP, servicePort)) }) <del> ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a NodePort service\", func() { serviceName := \"clusterip-test\" serverPod1Name := \"server-1\" serverPod2Name := \"server-2\" ns := f.Namespace.Name nodeIP, err := e2enode.PickIP(cs) // for later framework.ExpectNoError(err) // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=NodePort in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeNodePort svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"http\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Add a backend pod to the service ginkgo.By(\"creating a backend pod for the service \" + serviceName) serverPod1 := newAgnhostPod(serverPod1Name, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels _, err = cs.CoreV1().Pods(ns).Create(context.TODO(), serverPod1, metav1.CreateOptions{}) ginkgo.By(fmt.Sprintf(\"checking NodePort service %s on node with public IP %s\", serviceName, nodeIP)) framework.ExpectNoError(err) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, serverPod1.Name, f.Namespace.Name, framework.PodStartTimeout)) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{serverPod1Name: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod reveives the traffic ginkgo.By(\"Sending UDP traffic to NodePort service \" + serviceName + \" on node with publicIP \" + nodeIP) errorChannel := make(chan error) signal := make(chan struct{}, 1) go continuousEcho(nodeIP, int(udpService.Spec.Ports[0].NodePort), 3*time.Second, 20, signal, errorChannel) // Create a second pod ginkgo.By(\"creating a second pod for the service \" + serviceName) serverPod2 := newAgnhostPod(serverPod2Name, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels _, err = cs.CoreV1().Pods(ns).Create(context.TODO(), serverPod2, metav1.CreateOptions{}) framework.ExpectNoError(err) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, serverPod2.Name, f.Namespace.Name, framework.PodStartTimeout)) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", serverPod1Name) err = cs.CoreV1().Pods(ns).Delete(context.TODO(), serverPod1Name, metav1.DeleteOptions{}) framework.ExpectNoError(err, \"failed to delete pod: %s on node\", serverPod1Name) // Check that the second pod keeps receiving traffic ginkgo.By(\"Sending UDP traffic to NodePort service \" + serviceName + \" on node with publicIP \" + nodeIP) signal <- struct{}{} // Check that there are no errors err = <-errorChannel framework.ExpectNoError(err, \"pod communication failed\") }) </del> /* Release : v1.16 Testname: Service, NodePort Service", "positive_passages": [{"docid": "doc-en-kubernetes-0543f3a3993360bbed011d4060e35a21f3f79414d82ea25f247261ac2b705804", "text": "After my second deflaking PR, we seem to be in the stage where: tests are failing on dozens of different things (probably iptables-issues related) tests are failing only on NodePort tests on \"Failed to connecto to backend 1\" which it would be great if someone else could look into (kube-proxy seemed to be programmed correctly based on logs)\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\nThis has failed again - Linking to specific part of log where timeout occurred .... we see this\nSo reviewing the above logs note how in STEP: checking client pod connected to the backend 1 on Node IP 10.138.0.5 28 attempts are made all in the 25th second of the 2 minute at 11am Should this Step back off and wait a few seconds in between tries? So looking at this code we see the following\nFrom reading ... the intention expressed in the test code looks good to me. It is not clear to me why there is a mismatch between the 28 tries in the POD Client Logs and the expressed intention running the logContainsFn(podBackend1) every 5 seconds still digging ....\nwe are trying to catch one failure in this PR that has additional debugging, it dumps the conntrack table of the nodes on a failure\nfor those following the issue, we've extra debugging to the test so it dumps the whole conntrack table once it finish. We should look that there is NO stale entries, connections from the pod client to the deleted endpoint) and there is conntrack entries to the new endpoint from the pod client.\n- we have runs with the conntrack dump now, e.g. this one: would you be able to take a look into it?\nnot yet :/ , but I think tomorrow can have some time\ncc\nFor anyone reproducing this issue btw, you need a multinode k8s cluster (it isnt doable on kind i guess bc less likeliehood of network failures when running local) -\nCurious about two potential hypotheses to fix this, have we looked into either of these? 1) can we confirm that is turned on/off? 2) is it possible that scaling the number of coredns replicas could help ?", "commid": "kubernetes_issue_91236", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8283226613d2840ca538cf66f5aaf63662cfe5cb84446edefd3c3dff96025a6d", "query": "framework.ExpectNoError(verifyServeHostnameServiceUp(cs, ns, host, podNames2, svc2IP, servicePort)) }) <del> ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a NodePort service\", func() { serviceName := \"clusterip-test\" serverPod1Name := \"server-1\" serverPod2Name := \"server-2\" ns := f.Namespace.Name nodeIP, err := e2enode.PickIP(cs) // for later framework.ExpectNoError(err) // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=NodePort in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeNodePort svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"http\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Add a backend pod to the service ginkgo.By(\"creating a backend pod for the service \" + serviceName) serverPod1 := newAgnhostPod(serverPod1Name, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels _, err = cs.CoreV1().Pods(ns).Create(context.TODO(), serverPod1, metav1.CreateOptions{}) ginkgo.By(fmt.Sprintf(\"checking NodePort service %s on node with public IP %s\", serviceName, nodeIP)) framework.ExpectNoError(err) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, serverPod1.Name, f.Namespace.Name, framework.PodStartTimeout)) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{serverPod1Name: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod reveives the traffic ginkgo.By(\"Sending UDP traffic to NodePort service \" + serviceName + \" on node with publicIP \" + nodeIP) errorChannel := make(chan error) signal := make(chan struct{}, 1) go continuousEcho(nodeIP, int(udpService.Spec.Ports[0].NodePort), 3*time.Second, 20, signal, errorChannel) // Create a second pod ginkgo.By(\"creating a second pod for the service \" + serviceName) serverPod2 := newAgnhostPod(serverPod2Name, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels _, err = cs.CoreV1().Pods(ns).Create(context.TODO(), serverPod2, metav1.CreateOptions{}) framework.ExpectNoError(err) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, serverPod2.Name, f.Namespace.Name, framework.PodStartTimeout)) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", serverPod1Name) err = cs.CoreV1().Pods(ns).Delete(context.TODO(), serverPod1Name, metav1.DeleteOptions{}) framework.ExpectNoError(err, \"failed to delete pod: %s on node\", serverPod1Name) // Check that the second pod keeps receiving traffic ginkgo.By(\"Sending UDP traffic to NodePort service \" + serviceName + \" on node with publicIP \" + nodeIP) signal <- struct{}{} // Check that there are no errors err = <-errorChannel framework.ExpectNoError(err, \"pod communication failed\") }) </del> /* Release : v1.16 Testname: Service, NodePort Service", "positive_passages": [{"docid": "doc-en-kubernetes-66f25b05b1c90d93aad713cb7c943585d55afc690fe7a4f7e9fa0b7a5a5f23b1", "text": "3) Would simulating this in kind by overloading coredns be a possibility as a way to make a more reproducible bug model?\nregarding 1) kubeadm does not ship nodeLocalDNSCache I don't think GCE kube-up does by default either\nok, so now im curious about (2) - i.e. what if we just bumped coredns replica count?\ninteresting, :thinking: why do you think is a DNS thing? the netcat command that polls the services use the IP addresses not the hostname. I think that it has to be related to some iptables/conntrack race or similar,at least in KIND jobs we know that we have an iptables problem that affects network tests, that has to be fixed before this because it affect this test You can instrument the test locally with this and dump the state of iptables and conntrack on failure if you are able to reproduce it\ni figured DNS bc i believe its known that conntrack and DNS at scale can get very messy, right ?\none other curious thing about this test is that we only create 2 pods in the recycling event for the svc. that likely means that any real error is hidden by chance..... If we created a 3rd pod, then we might potentially double the failure rate thus making the flakyness go away and expose the real underlying issue .\nThere's an invocation of dumpConntrack(cs) here [sig-network] Conntrack should be able to preserve UDP traffic when server pod cycles for a ClusterIP service\nis updating the logging to run in an infinite loop ..\nThis is improving in KIND with the new changes we rolled out yesterday, let's see how it evolves this week\n- which changes ? Are you saying this is no longer reproducible on Kind?\nthere was a lot of noise in the CI signal, especially in KIND jobs due to the CNI portmap bug we finally solved yesterday now we should have a better signal and we can go to the bottom because probably the failure will be \"legit\" and not a consequence, so this comment should apply\nHi ! I ran this a few times on kind and it passed, but I see , so I'm going to try the loop approach you suggested. Here's what I'm using to test:\nquick note, <- potential motivation to possibly have runnable on some subset of tests in upstream eventually, i.e.", "commid": "kubernetes_issue_91236", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8283226613d2840ca538cf66f5aaf63662cfe5cb84446edefd3c3dff96025a6d", "query": "framework.ExpectNoError(verifyServeHostnameServiceUp(cs, ns, host, podNames2, svc2IP, servicePort)) }) <del> ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a NodePort service\", func() { serviceName := \"clusterip-test\" serverPod1Name := \"server-1\" serverPod2Name := \"server-2\" ns := f.Namespace.Name nodeIP, err := e2enode.PickIP(cs) // for later framework.ExpectNoError(err) // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=NodePort in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeNodePort svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"http\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Add a backend pod to the service ginkgo.By(\"creating a backend pod for the service \" + serviceName) serverPod1 := newAgnhostPod(serverPod1Name, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels _, err = cs.CoreV1().Pods(ns).Create(context.TODO(), serverPod1, metav1.CreateOptions{}) ginkgo.By(fmt.Sprintf(\"checking NodePort service %s on node with public IP %s\", serviceName, nodeIP)) framework.ExpectNoError(err) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, serverPod1.Name, f.Namespace.Name, framework.PodStartTimeout)) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{serverPod1Name: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod reveives the traffic ginkgo.By(\"Sending UDP traffic to NodePort service \" + serviceName + \" on node with publicIP \" + nodeIP) errorChannel := make(chan error) signal := make(chan struct{}, 1) go continuousEcho(nodeIP, int(udpService.Spec.Ports[0].NodePort), 3*time.Second, 20, signal, errorChannel) // Create a second pod ginkgo.By(\"creating a second pod for the service \" + serviceName) serverPod2 := newAgnhostPod(serverPod2Name, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels _, err = cs.CoreV1().Pods(ns).Create(context.TODO(), serverPod2, metav1.CreateOptions{}) framework.ExpectNoError(err) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, serverPod2.Name, f.Namespace.Name, framework.PodStartTimeout)) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", serverPod1Name) err = cs.CoreV1().Pods(ns).Delete(context.TODO(), serverPod1Name, metav1.DeleteOptions{}) framework.ExpectNoError(err, \"failed to delete pod: %s on node\", serverPod1Name) // Check that the second pod keeps receiving traffic ginkgo.By(\"Sending UDP traffic to NodePort service \" + serviceName + \" on node with publicIP \" + nodeIP) signal <- struct{}{} // Check that there are no errors err = <-errorChannel framework.ExpectNoError(err, \"pod communication failed\") }) </del> /* Release : v1.16 Testname: Service, NodePort Service", "positive_passages": [{"docid": "doc-en-kubernetes-deebb69aabcaf9005201c68e52f1f862e88c30f5231beaa0034b1d576abe9a4a", "text": "so we can do things like to reproduce this sort of thing. matt did you get around to the 'try-till-it-fails' scenario?\nI haven't been able to get it to fail on kind yet, -- 100 cycles and 0 failures on a three-node kind cluster! I'm letting the loop run for a few hours, will check back in when I have that data. Is it worth running this test on a non-kind environment?\nI ran for several hours on my mac, through 1144 iterations no error yet. My conclusion: this test isn't flaky on KinD. Possible next step: run a large number of iterations of the same test on a GKE cluster.\nFlakes on kind are also happening:\nnot many since the portmap fix on the 14th though ( / ) <img width=\"1111\" alt=\"Screen Shot 2020-07-23 at 11 45 46 PM\" src=\"https://user-\"\nAgree - it's much better than it was before.\nI was analyzing this failure, the problem is that kind jobs does not have verbosity enough in kube-proxy We can see that the packet was never replied, this is the NAT entry from client -nodePort in the node with the client This is the same flow, but in the node with the server and the pod-server-1 seems to be healthy we need more logs :eyeglasses:\nWe have an open ticket to bump those in CI, it's just been lost in the noise. We should still do that. Antonio Ojea <:\nIf you are busy just assign it to me, I'll need this verbosity soon :)\nIt's in the kind repo, shouldn't be too hard to find, we have ~60 open atm. Antonio Ojea <:\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\nI made another attempt to reproduce these failures locally on KinD, but still no success. Here's what I did: create a KinD cluster run two instances of sonobuoy at the same time This took ~4 hours to run; all the kube tests passed and sonobuoy reported all successes.", "commid": "kubernetes_issue_91236", "tokennum": 494}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8283226613d2840ca538cf66f5aaf63662cfe5cb84446edefd3c3dff96025a6d", "query": "framework.ExpectNoError(verifyServeHostnameServiceUp(cs, ns, host, podNames2, svc2IP, servicePort)) }) <del> ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a NodePort service\", func() { serviceName := \"clusterip-test\" serverPod1Name := \"server-1\" serverPod2Name := \"server-2\" ns := f.Namespace.Name nodeIP, err := e2enode.PickIP(cs) // for later framework.ExpectNoError(err) // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=NodePort in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeNodePort svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"http\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Add a backend pod to the service ginkgo.By(\"creating a backend pod for the service \" + serviceName) serverPod1 := newAgnhostPod(serverPod1Name, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels _, err = cs.CoreV1().Pods(ns).Create(context.TODO(), serverPod1, metav1.CreateOptions{}) ginkgo.By(fmt.Sprintf(\"checking NodePort service %s on node with public IP %s\", serviceName, nodeIP)) framework.ExpectNoError(err) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, serverPod1.Name, f.Namespace.Name, framework.PodStartTimeout)) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{serverPod1Name: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod reveives the traffic ginkgo.By(\"Sending UDP traffic to NodePort service \" + serviceName + \" on node with publicIP \" + nodeIP) errorChannel := make(chan error) signal := make(chan struct{}, 1) go continuousEcho(nodeIP, int(udpService.Spec.Ports[0].NodePort), 3*time.Second, 20, signal, errorChannel) // Create a second pod ginkgo.By(\"creating a second pod for the service \" + serviceName) serverPod2 := newAgnhostPod(serverPod2Name, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels _, err = cs.CoreV1().Pods(ns).Create(context.TODO(), serverPod2, metav1.CreateOptions{}) framework.ExpectNoError(err) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, serverPod2.Name, f.Namespace.Name, framework.PodStartTimeout)) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", serverPod1Name) err = cs.CoreV1().Pods(ns).Delete(context.TODO(), serverPod1Name, metav1.DeleteOptions{}) framework.ExpectNoError(err, \"failed to delete pod: %s on node\", serverPod1Name) // Check that the second pod keeps receiving traffic ginkgo.By(\"Sending UDP traffic to NodePort service \" + serviceName + \" on node with publicIP \" + nodeIP) signal <- struct{}{} // Check that there are no errors err = <-errorChannel framework.ExpectNoError(err, \"pod communication failed\") }) </del> /* Release : v1.16 Testname: Service, NodePort Service", "positive_passages": [{"docid": "doc-en-kubernetes-738ad9cb1373dead6b2f556ac241cd0c8a6cc7a0f09950111e765d9eb1dab68b", "text": "Would love to help out in reproing this, I'm at a loss for good next step so any suggestions welcome!\nthat's the problem with these flakes, they are not easy to repro, and with this low rate of failures it may be caused for combination of running tests, environmental problems (cpu, memory, ...) , ... I always start for checking the current failures and try to find patterns\nLet's take a look to one occurrence The tests fails because can't connect to the first pod If we check the code of the tests, we can see that it always uses the port as source port, we can use that to identify the nodePort assigned interesting thing here, we are source nating the pod ip, and we don't see any other conntrack entry The test verifies it has endpoints however, kube-proxy is using endpointlsices since this version but it has no entries so the iptables rules to forward the traffic are not there Seems we have to adapt this function in the e2e framework to use endpointslices cc: EDIT seems that this function is being used by all the network tests that can cause flakes if the endpoint is updated before the endpointslice (we switched recently kube-proxy to use the later)\nGreat catch. Ideally this function should validate if both Endpoint and appropriate EndpointSlice objects(s) exist.\nActually - let me take it and send a PR for it.\nis out for review\nInteresting failures here It fails to connect to the first pod\nHmm - I took a quick look at kube-proxy logs and these look fine to me....\nI clicked too fast, sorry ... I was looking at the wrong service and I though I've found something\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry.", "commid": "kubernetes_issue_91236", "tokennum": 416}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8283226613d2840ca538cf66f5aaf63662cfe5cb84446edefd3c3dff96025a6d", "query": "framework.ExpectNoError(verifyServeHostnameServiceUp(cs, ns, host, podNames2, svc2IP, servicePort)) }) <del> ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a NodePort service\", func() { serviceName := \"clusterip-test\" serverPod1Name := \"server-1\" serverPod2Name := \"server-2\" ns := f.Namespace.Name nodeIP, err := e2enode.PickIP(cs) // for later framework.ExpectNoError(err) // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=NodePort in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeNodePort svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"http\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Add a backend pod to the service ginkgo.By(\"creating a backend pod for the service \" + serviceName) serverPod1 := newAgnhostPod(serverPod1Name, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels _, err = cs.CoreV1().Pods(ns).Create(context.TODO(), serverPod1, metav1.CreateOptions{}) ginkgo.By(fmt.Sprintf(\"checking NodePort service %s on node with public IP %s\", serviceName, nodeIP)) framework.ExpectNoError(err) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, serverPod1.Name, f.Namespace.Name, framework.PodStartTimeout)) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{serverPod1Name: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod reveives the traffic ginkgo.By(\"Sending UDP traffic to NodePort service \" + serviceName + \" on node with publicIP \" + nodeIP) errorChannel := make(chan error) signal := make(chan struct{}, 1) go continuousEcho(nodeIP, int(udpService.Spec.Ports[0].NodePort), 3*time.Second, 20, signal, errorChannel) // Create a second pod ginkgo.By(\"creating a second pod for the service \" + serviceName) serverPod2 := newAgnhostPod(serverPod2Name, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels _, err = cs.CoreV1().Pods(ns).Create(context.TODO(), serverPod2, metav1.CreateOptions{}) framework.ExpectNoError(err) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, serverPod2.Name, f.Namespace.Name, framework.PodStartTimeout)) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", serverPod1Name) err = cs.CoreV1().Pods(ns).Delete(context.TODO(), serverPod1Name, metav1.DeleteOptions{}) framework.ExpectNoError(err, \"failed to delete pod: %s on node\", serverPod1Name) // Check that the second pod keeps receiving traffic ginkgo.By(\"Sending UDP traffic to NodePort service \" + serviceName + \" on node with publicIP \" + nodeIP) signal <- struct{}{} // Check that there are no errors err = <-errorChannel framework.ExpectNoError(err, \"pod communication failed\") }) </del> /* Release : v1.16 Testname: Service, NodePort Service", "positive_passages": [{"docid": "doc-en-kubernetes-7b1ee5acca525c6b88a5b6825056ab7c4df586768503c885715c9a87d944744a", "text": "\u200d\njust saw it as well\ncan you please add links to the job with the failures, I just merged new code to improve the logging 2 days ago\nok, here there is a new occurrence and with the new debug logs is easier to follow has unreplied conntrack entries: looking at the other side The iptables rules are there but no conntrack entries related to 10.244.2.32\nIn I revert PR with debug info as I think that it likely caused significant memory growth in scalability tests, but we have one run that has finished without being killed by OOMKiller (I increased memory limit for that jobs as a mitigation). Maybe logs from this run will be useful for debugging:\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\nTwo more flakes today:\nIt seems that the packet never gets DNATed in the receiving host, so it does not reach the pod in the node. There is the same test that is using ClusterIP instead of NodePort that is more reliable. This is being a tough one\n/triage accepted\nYesterday's flake - I don't think I'm seeing the log messages from the latest log PR you made ? Or are the prow logs not logging at a high-enough level?\nLogs are there, please bear with me: The error on the test is: click on the job failure and you'll see a larger output where you can see the server pod name and get the node where the pod is running: and the client-pod name and its node: and the flow we are looking for: with the node-name we can get the kube-proxy logs there, clicking in artifacts: and you can see the \"new\" conntrack log entries : and in the client: wow, there is a kernel bug there , can it be related? :thinking:\nwohoo - some progress :) I'm not an expert here, but I think it can be? Adding here - they may be able to confirm/reject the hypothesis.\nThis kernel panic may be a coincidence, maybe this is the reason\nAdding some recent failures:\nSpotted another flake today:\nAnother flake in the 5k job:", "commid": "kubernetes_issue_91236", "tokennum": 495}], "negative_passages": []}
{"query_id": "q-en-kubernetes-82c311b6f319e9f436a0ec0caf0b550e9d9cbd534080cf4e5025c93b27dd20cc", "query": "import ( \"fmt\" <ins> \"strings\" </ins> \"testing\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\"", "positive_passages": [{"docid": "doc-en-kubernetes-b73bb51cef5016ee2dcd80aae4248808fec811a4dad3a3b7abbba7673a446c48", "text": "What happened: No endpoints created in the EndpointSlice for my service due to the port on the service being too long. Logs show: EndpointSlice created has no endpoint: What you expected to happen: Service that works with Endpoints should work with EndpointSlice. If this is intentional, it should be clearly documented How to reproduce it (as minimally and precisely as possible): Create a service with a long port name Environment: Kubernetes version (use ): 1.16 Cloud provider or hardware configuration: kind\n/sig networking\nThe label(s) cannot be applied. These labels are supported: <detailsIn response to : /sig networking 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\n/sig network These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by vllry. \u200d\nFor a rough measure of impact, Istio had 5 ports that were over this limit (and many more that were right at 15 characters), so I suspect it may not be terribly rare.\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nThis needs to be resolved before endpointslices graduate from alpha\n/assign\n/remove-triage unresolved", "commid": "kubernetes_issue_84388", "tokennum": 292}], "negative_passages": []}
{"query_id": "q-en-kubernetes-82db5fab83dc792afe74f953697507bf1283050c02eed553a38b2a671e3c0cd8", "query": "framework.ExpectNoError(err, \"found a pod(s)\") }) <del> ginkgo.It(\"should run through the lifecycle of Pods and PodStatus\", func() { </del> <ins> /* Release: v1.20 Testname: Pods, completes the lifecycle of a Pod and the PodStatus Description: A Pod is created with a static label which MUST succeed. It MUST succeed when patching the label and the pod data. When checking and replacing the PodStatus it MUST succeed. It MUST succeed when deleting the Pod. */ framework.ConformanceIt(\"should run through the lifecycle of Pods and PodStatus\", func() { </ins> podResource := schema.GroupVersionResource{Group: \"\", Version: \"v1\", Resource: \"pods\"} testNamespaceName := f.Namespace.Name testPodName := \"pod-test\"", "positive_passages": [{"docid": "doc-en-kubernetes-a4e08d4660e59e77b869eee3e8c161e5e01175b90d68e1077fd3e84d4f4d567b", "text": "[x] Original approval issue: - Reverted due to flakes [x] Two weeks soak end date: 20 November 2020 This issue is created to allow edit by /wip /hold According to this APIsnoop query, there are still some remaining Pod endpoints which are untested. a Pod with a static label the Pod with a new Label and updated data the Pod to ensure it's patched the Pod's status the Pod's status Ready condition to False the Pod's status to check if Ready is False all Pods in all Namespaces find the Pod(1) ensure that the Pod is found and is patched Namespaced Pod(1) via a Collection with a LabelSelector the Pod to check that it's deleted Discover useragents: List endpoints hit by the test: Display endpoint coverage change: If a test with these calls gets merged, test coverage will go up by 4 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance\n/reopen Test PR Merge Promotion PR to be created next\nReopened this issue. <detailsIn response to : /reopen Test PR Merge Promotion PR to be created next 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\nreverted by due to flaky test\nIssues 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\n/remove-lifecycle stale\n/reopen PR on test grid for 2 weeks before promotion to conformance\nReopened this issue. <detailsIn response to : /reopen PR on test grid for 2 weeks before promotion to conformance 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\n/triage accepted", "commid": "kubernetes_issue_90936", "tokennum": 449}], "negative_passages": []}
{"query_id": "q-en-kubernetes-82e46b041a2046c946a7effe3167b3c10a853cb52ceb12587e0933061e47ec9a", "query": "removed := map[int]bool{} for i := 0; i < 5; i++ { if i != 0 { <del> klog.V(3).Infof(\"Attempt %v failed to kill all unwanted process. Retyring\", i) </del> <ins> klog.V(3).Infof(\"Attempt %v failed to kill all unwanted process from cgroup: %v. Retyring\", i, podCgroup) </ins> } errlist = []error{} for _, pid := range pidsToKill { if _, ok := removed[pid]; ok { continue } <del> klog.V(3).Infof(\"Attempt to kill process with pid: %v\", pid) </del> <ins> klog.V(3).Infof(\"Attempt to kill process with pid: %v from cgroup: %v\", pid, podCgroup) </ins> if err := m.killOnePid(pid); err != nil { <del> klog.V(3).Infof(\"failed to kill process with pid: %v\", pid) </del> <ins> klog.V(3).Infof(\"failed to kill process with pid: %v from cgroup: %v\", pid, podCgroup) </ins> errlist = append(errlist, err) } else { removed[pid] = true } } if len(errlist) == 0 { <del> klog.V(3).Infof(\"successfully killed all unwanted processes.\") </del> <ins> klog.V(3).Infof(\"successfully killed all unwanted processes from cgroup: %v\", podCgroup) </ins> return nil } }", "positive_passages": [{"docid": "doc-en-kubernetes-b90c168e06a7b711f67a139e334802368690ddadfe42c413624f21a9b2a8ae1a", "text": "What happened: When debugging timeouts related to the stopping of cgroups, the current logs from -tryKillingCgroupProcesses do not provide any correlation between the PIDs which were killed and the cgroup they belonged to. What you expected to happen: Log the cgroup name along with the PID How to reproduce it (as minimally and precisely as possible): N/A Anything else we need to know?: N/A Environment: Kubernetes version (use ): master\n/sig node", "commid": "kubernetes_issue_83624", "tokennum": 111}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8316223e20259fe461d460e2dd299079e3b7912d299749f0925b4c4cb895b776", "query": "return f.Err } <del> // DeleteTCPLoadBalancer is a test-spy implementation of TCPLoadBalancer.DeleteTCPLoadBalancer. </del> <ins> // EnsureTCPLoadBalancerDeleted is a test-spy implementation of TCPLoadBalancer.EnsureTCPLoadBalancerDeleted. </ins> // It adds an entry \"delete\" into the internal method call record. <del> func (f *FakeCloud) DeleteTCPLoadBalancer(name, region string) error { </del> <ins> func (f *FakeCloud) EnsureTCPLoadBalancerDeleted(name, region string) error { </ins> f.addCall(\"delete\") return f.Err }", "positive_passages": [{"docid": "doc-en-kubernetes-9fca6378f8b8df6d20b226b62d39deddc0dd6ba6166f0f70fb99239f64c63f5d", "text": "All of our external load balancer tests failed for the better part of a day due to the GCE project that our tests run in hitting its quota for number of target pools. While the target pools have been deleted, the fact that we hit our quota indicates that there must be a leak somewhere, and we need to plug it.\nFor reference, the previous issue was\nCould the leakage be related to ? The quota exhaustion occurred about 22 hrs after that.\nI'd guess that this is due to GetTCPLoadBalancer returning that the load balancer doesn't exist if the forwarding rule is gone, ignoring the target pool, while the service controller considers its deleting done if the cloud provider says that the load balancer doesn't exist. I that logic to the cloud provider because the other implementations of DeleteTCPLoadBalancer weren't/won't be idempotent in the sense of returning ok if the LB doesn't exist. To fix it, we'll either need to make sure all Delete implementations are idempotent and remove the Get call in the controller, or add a method along the lines of IsTCPLoadBalancerDeleted to ask the cloud provider whether all pieces of it have been completely cleaned up. We can't make GetTCPLoadBalancer check that because it's relied on to tell us whether or not the balancer is fully created.\nCopying over my commentary from on why the GKE e2e tests are leaking so many forwarding rules and target pools vs the GCE tests:\nIs there a way for the services test to wait for the service controller to clean up the external resources before finishing (without just doing a sleep)?\nNot without polling GCE directly for whether the resources still exist, although that may be worth it as a workaround. What would be perfect is that clean-up-all-cloud-provider-resources API method that we talked about a couple months ago.\nCan we not perhaps use GCE namespaces or projects as a cheap way of getting this here?\nI don't believe so. We can't use projects due to the fact that projects can't be programatically created (they're intended to be long-lived). I'm not aware of anything along the lines of a GCE namespace other than networks, which won't work because target pools and forwarding rules unfortunately don't seem to be scoped to networks.", "commid": "kubernetes_issue_7753", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8316223e20259fe461d460e2dd299079e3b7912d299749f0925b4c4cb895b776", "query": "return f.Err } <del> // DeleteTCPLoadBalancer is a test-spy implementation of TCPLoadBalancer.DeleteTCPLoadBalancer. </del> <ins> // EnsureTCPLoadBalancerDeleted is a test-spy implementation of TCPLoadBalancer.EnsureTCPLoadBalancerDeleted. </ins> // It adds an entry \"delete\" into the internal method call record. <del> func (f *FakeCloud) DeleteTCPLoadBalancer(name, region string) error { </del> <ins> func (f *FakeCloud) EnsureTCPLoadBalancerDeleted(name, region string) error { </ins> f.addCall(\"delete\") return f.Err }", "positive_passages": [{"docid": "doc-en-kubernetes-d79b213781c20847fbb47c058c0afaba60ed2f1d9f5b51e77a0a4cda944c52e0", "text": "The target pool leak in the code might be fixed, but the forwarding rule + target pool leak from deleting GKE clusters too quickly is certainly still happening. Reopening for the sake of that half of the issue.\nCan we just add a short sleep to jenkins after the last test has run before it deletes anything?\nYes, you could add a sleep to Ginkgo's AfterEachSuite(): But I'd be concerned about what the upper bound on the sleep period is. Can we get the tests and code in sync with a 1 minute latency here? (e.g. if the controller garbage collects every 60 seconds, then the test only needs to sleep for 60 sec?) And add a BEEG comment to the test's sleep config noting that increasing the sleep time will not improve things, otherwise I'm pretty sure that someone noting flakes in this test in future will think \"maybe I should just increase the sleep period a little bit.\"\nActually, thinking about this a little more, it would be better to put the \"sleep\" logic in the k8s master teardown procedure (i.e. not in the e2e tests or in Jenkins), because otherwise users are going to run into the same resource leakage problems as we are. So master deletion blocks on cleanup of backend cloud resources.\nThere's no way to block master deletion from the master itself. The test framework (or user) just pulls the rug out from underneath the master. See\nRobby's right -- is the real solution to this, but until we have that the best we can do is to have the wait happen elsewhere. The options seem to be: GKE itself Ginkgo's post-testing logic Jenkins' teardown logic I don't like putting it in GKE, because arbitrarily slowing down our API makes for a poor experience for the majority of people that don't still have resources being deleted. I'm not eager to put it in Gingko either, since won't that sleep also take effect whenever anyone runs an e2e test locally against a dev cluster? Putting it in the Jenkins logic makes the most sense to me. I'll send a PR and cc you.\nWe may also want to change the kube-down logic to bring down the master and then nodes in parallel to both speed it up and more closely resemble GKE's teardown logic.\nI've deleted the old forwarding rules and target pools from the project.", "commid": "kubernetes_issue_7753", "tokennum": 530}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8316223e20259fe461d460e2dd299079e3b7912d299749f0925b4c4cb895b776", "query": "return f.Err } <del> // DeleteTCPLoadBalancer is a test-spy implementation of TCPLoadBalancer.DeleteTCPLoadBalancer. </del> <ins> // EnsureTCPLoadBalancerDeleted is a test-spy implementation of TCPLoadBalancer.EnsureTCPLoadBalancerDeleted. </ins> // It adds an entry \"delete\" into the internal method call record. <del> func (f *FakeCloud) DeleteTCPLoadBalancer(name, region string) error { </del> <ins> func (f *FakeCloud) EnsureTCPLoadBalancerDeleted(name, region string) error { </ins> f.addCall(\"delete\") return f.Err }", "positive_passages": [{"docid": "doc-en-kubernetes-6b81898435dc239c0c98669b4836ce5b1423be788127f142aa9eb15c198137cf", "text": "I'll periodically check to see whether anything is leaked after this point. I apologize if the deletions affected any running tests - everything looked to only be from GKE and parallel e2e runs.", "commid": "kubernetes_issue_7753", "tokennum": 42}], "negative_passages": []}
{"query_id": "q-en-kubernetes-834afccd0e045bd0e6cc6d66378347941577afc89fd3f6c054a5ee2b1606eef3", "query": "kubelet.masterServiceNamespace = metav1.NamespaceDefault kubelet.serviceLister = testServiceLister{} kubelet.serviceHasSynced = func() bool { return true } <ins> kubelet.nodeHasSynced = func() bool { return true } </ins> kubelet.nodeLister = testNodeLister{ nodes: []*v1.Node{ {", "positive_passages": [{"docid": "doc-en-kubernetes-8476bba8e23a7ed885cd34c1077ce17dbf12901ac7ae9725333264f6ea8cfdae", "text": "What happened: A deployment is created that uses a after the cluster master is created but before the cluster worker nodes are fully initialized. During the initialization of the worker nodes, the nodes are temporarily available for scheduling without the necessary label to match the deployment's node selector. Depending on how long the nodes are available for scheduling without the necessary node labels for the deployment, the scheduler will start to spam with cluster with pods in status. This spamming stops once the worker nodes are fully initialized and the pods are scheduled successful. The exact timing of all of this is TBD. What you expected to happen: Pods in status are annoying and require manual cleanup. It would be preferred that the scheduler avoid this an simply issue warning events. How to reproduce it (as minimally and precisely as possible): See issue description. Anything else we need to know?: No. Environment: Kubernetes version (use ): 1.18.3 Cloud provider or hardware configuration: IBM Cloud Kubernetes Service OS (e.g: ): Ubuntu 18.04.4 LTS Kernel (e.g. ): 4.15.0-96-generic Install tools: Managed service install Network plugin and version (if this is a network-related bug): N/A Others: N/A\nRelated to and\n/sig scheduling\nby spamming are you referring to scheduler logs? also, why are the nodes not labelled from the get go?\nJust to confirm, all the pods in question are still in Pending state, yes? If the pods are in pending state, all of them will get scheduled eventually once the nodes get their labels.\nThe pods are not in state. They are actually in state. The pods eventually get scheduled but we are left with anywhere from a few to dozens of these state pods. Also, we are looking at labeling the nodes via kubelet flags to see if that helps.\n/remove-kind bug\nAfter we add some retry logic and wait time in this problem can be solved: As you can see this function returns initial node as the first request failed.\nI also get hit by this, when single controller node gets rebooted and scheduler starts as static container before kubelet becomes ready.", "commid": "kubernetes_issue_92067", "tokennum": 465}], "negative_passages": []}
{"query_id": "q-en-kubernetes-834afccd0e045bd0e6cc6d66378347941577afc89fd3f6c054a5ee2b1606eef3", "query": "kubelet.masterServiceNamespace = metav1.NamespaceDefault kubelet.serviceLister = testServiceLister{} kubelet.serviceHasSynced = func() bool { return true } <ins> kubelet.nodeHasSynced = func() bool { return true } </ins> kubelet.nodeLister = testNodeLister{ nodes: []*v1.Node{ {", "positive_passages": [{"docid": "doc-en-kubernetes-6c53201dbb91d52a8ade960092a5ed582f4d35e33a53b75d555d15ae815dc25c", "text": "Can be cleaned up with:\n/sig node\nthe spam cycle is this loop: \"pod create, pod schedule, worker reject, pod failed\" -- we don't have a lot of protection in higher level workload controllers to handle pods that fail at kubelet admission time versus pods that just dont create due to quota/admission. in general, is the spam causing any other stability issues? is pod gc pruning the pods?\nI wonder if we can do a trick in node lister to mitigate any race condition here...\nwe could maybe do something similar to to ensure node lister has synced...\nhacking on option to ensure if kubelet has a node lister with a valid kube client, we wait for it to sync at least once here which should mitigate this issue. see:\nWe noticed the problem on the OLM pod which is managed by the OLM operator. Right or wrong, the operator does not like seeing the pod go to status and no longer reconciles the pod. The end result is that manual intervention (i.e. pod deletion) is required to fix the problem.\nsure... i would have thought the pod is failed in that instance and reached a terminal state. either way, i am looking at what i can do to mitigate this.\nThe problem persists in our environment as well, and the workaround cited above will not do anymore. Is there something in the works for this one?\nIssues 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\n/remove-lifecycle stale", "commid": "kubernetes_issue_92067", "tokennum": 383}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8359b74da41c66ae6cd4b76528d2bbfdec4160fe4da5db8601f78081ad4c5cc5", "query": "return fmt.Errorf(\"PersistentVolumeClaims %v not all in phase %s within %v\", pvcNames, phase, timeout) } <ins> // findAvailableNamespaceName random namespace name starting with baseName. func findAvailableNamespaceName(baseName string, c clientset.Interface) (string, error) { var name string err := wait.PollImmediate(Poll, 30*time.Second, func() (bool, error) { name = fmt.Sprintf(\"%v-%v\", baseName, randomSuffix()) _, err := c.CoreV1().Namespaces().Get(name, metav1.GetOptions{}) if err == nil { // Already taken return false, nil } if apierrs.IsNotFound(err) { return true, nil } Logf(\"Unexpected error while getting namespace: %v\", err) return false, nil }) return name, err } </ins> // CreateTestingNS should be used by every test, note that we append a common prefix to the provided test name. // Please see NewFramework instead of using this directly. func CreateTestingNS(baseName string, c clientset.Interface, labels map[string]string) (*v1.Namespace, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-754a337748c77aa830912aa5c369fd083977cc37177bb1280fd450d5c939bfe3", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: In the test failed due to namespace leakage: we created e2e-tests-load-30-nodepods-1-pfn9m, but never got response from api server (got 0-length response instead) we retried and created e2e-tests-load-30-nodepods-1-m9tq5 e2e-tests-load-30-nodepods-1-m9tq5 to f.namespacesToDelete and leaked -pfn9m next test case failed because e2e-tests-load-30-nodepods-1-pfn9m wasn't deleted. What you expected to happen: While it's unclear why we got 0-length response instead ( investigates that), we always can get error while the namespace was created (e.g. connection reset, timeout, io error). We should handle this case in retrying correctly. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.14.0-alpha.0.793+ Cloud provider or hardware configuration: gce OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: <!-- DO NOT EDIT BELOW THIS LINE --/kind bug\nThere are no sig labels on this issue. Please add a sig label by either: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. See the . The in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals. <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\n/cc", "commid": "kubernetes_issue_71697", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-835e2b4a89ac5297285607e50095bf8deb56f4565253c51d2d63e2208b59a864", "query": "endpointsAvailableForLB := !allEndpointsTerminating && !allEndpointsNonServing proxier.deleteExistingLoadBalancer(hns, svcInfo.winProxyOptimization, &svcInfo.hnsID, sourceVip, Enum(svcInfo.Protocol()), uint16(svcInfo.targetPort), uint16(svcInfo.Port()), hnsEndpoints, queriedLoadBalancers) <del> if endpointsAvailableForLB { </del> <ins> // clusterIPEndpoints is the endpoint list used for creating ClusterIP loadbalancer. clusterIPEndpoints := hnsEndpoints if svcInfo.internalTrafficLocal { // Take local endpoints for clusterip loadbalancer when internal traffic policy is local. clusterIPEndpoints = hnsLocalEndpoints } </ins> <del> // clusterIPEndpoints is the endpoint list used for creating ClusterIP loadbalancer. clusterIPEndpoints := hnsEndpoints if svcInfo.internalTrafficLocal { // Take local endpoints for clusterip loadbalancer when internal traffic policy is local. clusterIPEndpoints = hnsLocalEndpoints } </del> <ins> if len(clusterIPEndpoints) > 0 { </ins> // If all endpoints are terminating, then no need to create Cluster IP LoadBalancer // Cluster IP LoadBalancer creation", "positive_passages": [{"docid": "doc-en-kubernetes-f554e53a2b0895170400ceeeb3f9d1f2002f8788d2419fe2262e5a5418c69b9b", "text": "I am tracking a changed behavior in networking with kubernetes 1.26. If I create a service of type externalTrafficPolicy: Local, and there are no local endpoints in a node, kube-proxy does not create hns loadbalancers for the clusterIP of that service. With kubernetes 1.25, it creates a loadbalancer for clusterIP (but not externalIP). This is the relevant log message: Looks like this comes with a result from a new function isAllEndpointsTerminating introduced in kubernetes 1.26. In Linux, we can still access clusterIP even if there are no local endpoints for the service. Thoughts? The end result is that in Windows, clients cannot access the clusterIP of such a service with there are no local endpoints.\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig windows\ncc\nDoes this issue occur when there are no local endpoints for a given service? If there is a local endpoint, then you can reach the service again, right?\n, Also let us know, do you have any InternalTrafficPolicy configured ?\nDoes this issue occur when there are no local endpoints for a given service? If there is a local endpoint, then you can reach the service again, right? That is correct , Also let us know, do you have any InternalTrafficPolicy configured ? We do not have that configured", "commid": "kubernetes_issue_115783", "tokennum": 376}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8386259c4824b98108e451a17ba26050cd1d43f7bfc0bb76104576cf7bf0460c", "query": "} mountComplete := false <del> err = wait.Poll(5*time.Second, 10*time.Minute, func() (bool, error) { </del> <ins> err = wait.PollImmediate(1*time.Second, 2*time.Minute, func() (bool, error) { </ins> err := b.mounter.MountSensitive(source, dir, \"cifs\", mountOptions, sensitiveMountOptions) mountComplete = true return true, err", "positive_passages": [{"docid": "doc-en-kubernetes-9945f53575b60dc39792ed32e02eb9c66a039731b5284891454b6dce2289c963", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: When starting pods with AFS volumes, there is an initial delay of five seconds until the pod is transitioning from the \"Scheduled\" state. The reason for this is that currently the volume mounting happens inside a wait.Poll which will initially wait a specified interval (currently 5 seconds) before execution. Event log for comparison with and without AFS volume attached (seconds since event): What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others: /assign /priority important-soon /sig cloud-provider /area provider/azure\nsee", "commid": "kubernetes_issue_93025", "tokennum": 233}], "negative_passages": []}
{"query_id": "q-en-kubernetes-838c2678175b6946c432f6f6338edea4801902be38f352ccefe554fbda1e4761", "query": "klog.V(4).Info(log(\"attacher.Attach finished OK with VolumeAttachment object [%s]\", attachID)) <ins> // TODO(71164): In 1.15, return empty devicePath </ins> return attachID, nil } <del> func (c *csiAttacher) WaitForAttach(spec *volume.Spec, attachID string, pod *v1.Pod, timeout time.Duration) (string, error) { </del> <ins> func (c *csiAttacher) WaitForAttach(spec *volume.Spec, _ string, pod *v1.Pod, timeout time.Duration) (string, error) { </ins> source, err := getCSISourceFromSpec(spec) if err != nil { klog.Error(log(\"attacher.WaitForAttach failed to extract CSI volume source: %v\", err)) return \"\", err } <ins> attachID := getAttachmentName(source.VolumeHandle, source.Driver, string(c.plugin.host.GetNodeName())) </ins> skip, err := c.plugin.skipAttach(source.Driver) if err != nil { klog.Error(log(\"attacher.Attach failed to find if driver is attachable: %v\", err))", "positive_passages": [{"docid": "doc-en-kubernetes-2aac55d80f27da70e775c33573d217f00c9becbbc11daa530f1576640fc1582a", "text": "The test flakes very occasionally. Below are the findings of the circumstances of the flake. During two pods are created in quick succession. The test flakes when the second Pod fails to come up. The second pod fails to come up with error: Upon exploring the logs we discovered that there was only 1 Attach call made at the beginning, and one Detach call upon timeout of the test [See timestamps]: We tracked down the error to the likely culprit in func : based on the error message returned. This is likely caused by (string) being empty [uncomfirmed], which is what the Kubelet would get from the DevicePath field on the Node object. This DevicePath field is normally on Attach and removed on Detach of the volume. The DevicePath is clearly present on the Node when the first pod is being brought up. But it is possible that it is somehow missing or not able to be retrieved by the time the second Pod is starting up (and continues to be unavailable exhausting the 15m timeout on the test) even though no Detach operation was performed on the volume in the meantime (according to logs). We are currently unable to reproduce this flake on command and did all analysis based on logs from the two flakes we saw naturally occur in the 100s of runs performed of the test. This flake was originally seen in and the test logs can be found here: https://k8s- Environment: GCE Kubernetes version (use ):Cloud provider or hardware configuration: GCP OS (e.g. from /etc/os-release):Kernel (e.g. ): /kind flake /kind bug /sig storage /cc\nIssues 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\n/remove-lifecycle stale A check in triage shows that this failing test is still a problem, and in fact has become more of a problem since October 4th. Has there been any progress on a fix?", "commid": "kubernetes_issue_65246", "tokennum": 474}], "negative_passages": []}
{"query_id": "q-en-kubernetes-838c2678175b6946c432f6f6338edea4801902be38f352ccefe554fbda1e4761", "query": "klog.V(4).Info(log(\"attacher.Attach finished OK with VolumeAttachment object [%s]\", attachID)) <ins> // TODO(71164): In 1.15, return empty devicePath </ins> return attachID, nil } <del> func (c *csiAttacher) WaitForAttach(spec *volume.Spec, attachID string, pod *v1.Pod, timeout time.Duration) (string, error) { </del> <ins> func (c *csiAttacher) WaitForAttach(spec *volume.Spec, _ string, pod *v1.Pod, timeout time.Duration) (string, error) { </ins> source, err := getCSISourceFromSpec(spec) if err != nil { klog.Error(log(\"attacher.WaitForAttach failed to extract CSI volume source: %v\", err)) return \"\", err } <ins> attachID := getAttachmentName(source.VolumeHandle, source.Driver, string(c.plugin.host.GetNodeName())) </ins> skip, err := c.plugin.skipAttach(source.Driver) if err != nil { klog.Error(log(\"attacher.Attach failed to find if driver is attachable: %v\", err))", "positive_passages": [{"docid": "doc-en-kubernetes-2e50b6735500133e652390e8c295dea37c7d3b52bec7ef89ae580efb33be52fd", "text": "/priority important-soon\n/assign for triage\nWe should find the root cause and fix for 1.13\n/assign Patrick can you PTAL at what is causing flakiness in this test.\nI will have a look. Right now the log output of the sidecar containers and the CSI driver are not captured, which makes debugging a bit hard. In PR I am adding code which includes those message in the test log. Let me finish that PR and once it is merged, debugging the next test flake might provide some better insight into what went wrong.\nHey, this issue is considered a blocker for 1.13beta. Is there anything we can do to get it resolved sooner, so that it doesn't delay beta next week?\nis trying to instrument the e2e tests to get logs from the csi driver containers so that we can debug. He has tried running the test locally ~100 times and didn't see it flake.\nhere's one recent one you can check out:\nMichelle Au <: I had a look, but something is odd about that one. The error for the second pod is there: But under there is no further information about node bootstrap-e2e-gce-mz-minion-group-3kn6. Shouldn't that be available?\n\"Patrick Ohly\" Here's a better example where the kublet log with the error is available: That one also has the log of the external-attacher, but that doesn't tell me much. I'm now comparing a \"bad\" run with a \"good\" local run. One observation is that in the \"good\" run, operationExecutor.UnmountDevice is completed before the second usage, including the \"Volume detached for volume\" step in Then operationExecutor.VerifyControllerAttachedVolume is done again for the second pod, exactly as it was done for the first: In the \"bad\" run, operationExecutor.MountVolume is invoked before that \"Volume detached for volume\" and then runs with an empty device path, without going through VerifyControllerAttachedVolume again: So to me it looks like a race between two conflicting operations. Does that make sense? How to fix it is less obvious. The relevant code seems to be this in Any suggestions?\nThis seems inline with the observations that made initially. We should trace where DevicePath is getting set.", "commid": "kubernetes_issue_65246", "tokennum": 520}], "negative_passages": []}
{"query_id": "q-en-kubernetes-838c2678175b6946c432f6f6338edea4801902be38f352ccefe554fbda1e4761", "query": "klog.V(4).Info(log(\"attacher.Attach finished OK with VolumeAttachment object [%s]\", attachID)) <ins> // TODO(71164): In 1.15, return empty devicePath </ins> return attachID, nil } <del> func (c *csiAttacher) WaitForAttach(spec *volume.Spec, attachID string, pod *v1.Pod, timeout time.Duration) (string, error) { </del> <ins> func (c *csiAttacher) WaitForAttach(spec *volume.Spec, _ string, pod *v1.Pod, timeout time.Duration) (string, error) { </ins> source, err := getCSISourceFromSpec(spec) if err != nil { klog.Error(log(\"attacher.WaitForAttach failed to extract CSI volume source: %v\", err)) return \"\", err } <ins> attachID := getAttachmentName(source.VolumeHandle, source.Driver, string(c.plugin.host.GetNodeName())) </ins> skip, err := c.plugin.skipAttach(source.Driver) if err != nil { klog.Error(log(\"attacher.Attach failed to find if driver is attachable: %v\", err))", "positive_passages": [{"docid": "doc-en-kubernetes-50ecdb83cd1167eaf5e0774965d35fc15510d148142317b954cbbba2a849431a", "text": "Could there be a race with AD controller or external attacher if they try to detach the volume? is another race around this area. Unclear if it's the same yet.\nMichelle Au <: No idea. Even if it isn't, it's at least related to the same piece of code. Probably worth fixing both together. Can we get someone who has worked in this area to fix these issues? Today is the first day that I've ever seen this code, so I'm a bit afraid that it'll take me a long time to get it right, and I'm worried about regressions.\nI've asked to help investigate\nIt is not a blocker for beta or freeze. Can be addressed in stabilization. Let's keep the 1.13 tag on it. And based on progress by stabilization we can reassess if it is even a 1.13 blocker (at this point I don't believe it is).\nThe in the actual state of the world gets reset during unmounting:\nThat removes the device path looks wrong to me. I've submitted PR which changes that. Let's see how much that breaks...\n/assign The conclusion in the CSI working group was that while my analysis and the resulting fix might be correct, further debugging and a second pair of eyes would be good. Let me reassign, because I have done what I could for this issue.\nThe RT considers this a blocker now, because flakes are happening often enough to interfere with getting clear signal on several jobs. Even if the underlying problem isn't that serious.\n/assign I will help triage as well.\nAck Thanks\nInstead of which may have negative side effects for non-CSI volumes, let's do this instead: Modify the CSI method in to ignore the passed in (which is populated from devicePath. Instead let's have that method generate the from scratch, e.g. attachID := getAttachmentName(volID, driverName, string(nodeName)) This will remove any CSI dependency on devicePath and not effect other volume plugins.\nI am trying to twist my head around the code. IMO it affects also AWS that uses devicePath stored in and it should be reproducible there too. So far I was unsuccessful. In the logs it's clearly visible that UnmountDevice succeeded. So why kubelet continues with MountVolume instead of MountDevice? That's wrong.", "commid": "kubernetes_issue_65246", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-838c2678175b6946c432f6f6338edea4801902be38f352ccefe554fbda1e4761", "query": "klog.V(4).Info(log(\"attacher.Attach finished OK with VolumeAttachment object [%s]\", attachID)) <ins> // TODO(71164): In 1.15, return empty devicePath </ins> return attachID, nil } <del> func (c *csiAttacher) WaitForAttach(spec *volume.Spec, attachID string, pod *v1.Pod, timeout time.Duration) (string, error) { </del> <ins> func (c *csiAttacher) WaitForAttach(spec *volume.Spec, _ string, pod *v1.Pod, timeout time.Duration) (string, error) { </ins> source, err := getCSISourceFromSpec(spec) if err != nil { klog.Error(log(\"attacher.WaitForAttach failed to extract CSI volume source: %v\", err)) return \"\", err } <ins> attachID := getAttachmentName(source.VolumeHandle, source.Driver, string(c.plugin.host.GetNodeName())) </ins> skip, err := c.plugin.skipAttach(source.Driver) if err != nil { klog.Error(log(\"attacher.Attach failed to find if driver is attachable: %v\", err))", "positive_passages": [{"docid": "doc-en-kubernetes-d22ef691d33dfaf1e5b5dad591a3014f6fd8d0e62064752134a5c7ffdbfdc8ce", "text": "A workaround in CSI volume plugin won't really help here, it will work only for drivers without .\nI finally reproduced it on AWS with a long sleep in : Steps to reproduce (with the hack above): a pod with a volume the pod. Wait until is called. a new pod with the same volume. - checks that the volume is still attached and the device is still mounted and enqueues an operation to mount the volume. When finishes, starts and 1) uses empty and 2) calls on volume that's not DeviceMounted.\nFix: Any idea how to test it for real? Fake CSI plugin with slow NodeUnstage would be the best, however we don't have one.\nI'm going to work on a targeted fix for CSI. We can continue to pursue fixing aws in-tree separately.\nPR to fix csi is here:\nwhat are the final set of PRs pending for this? , and ?\nOnly is needed to fix this particular test failure.\ncan you please confirm if we are going to fix this using or ?\nI discussed with offline, he has some suggestions for that I am investigating. I think we will want both PRs eventually, although only one of them will be needed to fix the CSI test for now. Since it's his off hours, I will continue working on today.\nAre we talking 1.13 for as well?\nReopening this since we are seeing consistent failures in latest runs. We also see one more test fail in the job with same error. Failing job https://k8s- Failing Tests [sig-storage] [Serial] CSI Volumes CSI plugin test using CSI driver: gcePD [Serial] should provision storage [sig-storage] [Serial] CSI Volumes CSI plugin test using CSI driver: hostPath [Serial] should provision storage Error This is now 1.13 release blocking.\n/priority critical-urgent /kind failing-test\n/remove-priority important-soon\nI think this is a different issue and could be due to the fact that CSI is intentionally not backwards compatible between 1.12 and 1.13. We may need to enhance the test to figure out what version the cluster is on and launch appropriate versions of the CSI driver.\n\"intentionally not backwards compatible\" -- is there a writeup for the release notes and release announcement for this change?", "commid": "kubernetes_issue_65246", "tokennum": 488}], "negative_passages": []}
{"query_id": "q-en-kubernetes-838c2678175b6946c432f6f6338edea4801902be38f352ccefe554fbda1e4761", "query": "klog.V(4).Info(log(\"attacher.Attach finished OK with VolumeAttachment object [%s]\", attachID)) <ins> // TODO(71164): In 1.15, return empty devicePath </ins> return attachID, nil } <del> func (c *csiAttacher) WaitForAttach(spec *volume.Spec, attachID string, pod *v1.Pod, timeout time.Duration) (string, error) { </del> <ins> func (c *csiAttacher) WaitForAttach(spec *volume.Spec, _ string, pod *v1.Pod, timeout time.Duration) (string, error) { </ins> source, err := getCSISourceFromSpec(spec) if err != nil { klog.Error(log(\"attacher.WaitForAttach failed to extract CSI volume source: %v\", err)) return \"\", err } <ins> attachID := getAttachmentName(source.VolumeHandle, source.Driver, string(c.plugin.host.GetNodeName())) </ins> skip, err := c.plugin.skipAttach(source.Driver) if err != nil { klog.Error(log(\"attacher.Attach failed to find if driver is attachable: %v\", err))", "positive_passages": [{"docid": "doc-en-kubernetes-532bee311f9ca5785c50bc17dbae5c7650ea95f95b647a2552dbb2ae250d0a88", "text": "Yes has the release note\nthanks, I'll also call it to the Release Notes lead's attention\nwhat does it mean from the user impact perspective for CSI to not be backward compatible with 1.12? can you please point me to any discussions on this behavior for 1.13?\nKubernetes v1.13 speaks CSI v1.0 and no longer understands CSI v0.x. Any CSI drivers deployed on previous versions of Kubernetes speaking CSI v0.x must removed, updated to be CSI 1.0 compatible, and redeployed on the on Kubernetes v1.13. If only the master is upgraded to 1.13 (and nodes are 1.12 or earlier) older drivers will continue to work. When nodes are upgraded to 1.13, then older drivers will stop working. I will capture this in detail in the \"Action Required\" section.\nIm tracking these upgrade test failures elsewhere: They are not related to this original issue, the flaky test referenced by this issue should have been solved by and for non CSI /close\nClosing this issue. <detailsIn response to : Im tracking these upgrade test failures elsewhere: They are not related to this original issue, the flaky test referenced by this issue should have been solved 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\nas FYI to call this out clearly in the Release notes.", "commid": "kubernetes_issue_65246", "tokennum": 312}], "negative_passages": []}
{"query_id": "q-en-kubernetes-839cd7cb3d8561e304a58b07bd138ab1f324e09cbd1d73e9d67d51bebedbb819", "query": "\"fmt\" \"io\" \"os\" <ins> \"strconv\" </ins> \"github.com/GoogleCloudPlatform/kubernetes/pkg/api\" cmdutil \"github.com/GoogleCloudPlatform/kubernetes/pkg/kubectl/cmd/util\"", "positive_passages": [{"docid": "doc-en-kubernetes-0f269e408c0c5ca583af123d217b4d1fb7160d426de10d2601450f917f382cd5", "text": "I an ELB to the Kibana cluster log viewer but it is not reported by which, aside from having a URL, should check each cluster service and if it has an external IP it should report that instead of the master proxy address.\ncc", "commid": "kubernetes_issue_7521", "tokennum": 50}], "negative_passages": []}
{"query_id": "q-en-kubernetes-83a651d24fdd1abbc5c865eca76961c3186e91441365ed99b8370cd52be93e51", "query": "} ) <ins> func TestConflictingCurrentContext(t *testing.T) { commandLineFile, _ := ioutil.TempFile(\"\", \"\") defer os.Remove(commandLineFile.Name()) envVarFile, _ := ioutil.TempFile(\"\", \"\") defer os.Remove(envVarFile.Name()) mockCommandLineConfig := clientcmdapi.Config{ CurrentContext: \"any-context-value\", } mockEnvVarConfig := clientcmdapi.Config{ CurrentContext: \"a-different-context\", } WriteToFile(mockCommandLineConfig, commandLineFile.Name()) WriteToFile(mockEnvVarConfig, envVarFile.Name()) loadingRules := ClientConfigLoadingRules{ CommandLinePath: commandLineFile.Name(), EnvVarPath:      envVarFile.Name(), } mergedConfig, err := loadingRules.Load() if err != nil { t.Errorf(\"Unexpected error: %v\", err) } if mergedConfig.CurrentContext != mockCommandLineConfig.CurrentContext { t.Errorf(\"expected %v, got %v\", mockCommandLineConfig.CurrentContext, mergedConfig.CurrentContext) } } </ins> func TestResolveRelativePaths(t *testing.T) { pathResolutionConfig1 := clientcmdapi.Config{ AuthInfos: map[string]clientcmdapi.AuthInfo{", "positive_passages": [{"docid": "doc-en-kubernetes-dbcf83004ea3f0459daec6a4d94a4bece404fe8f97225f1a2fba429c343bf057", "text": "I've been pulling my hair out trying get kubectl talk to my local cluster. It seems that kubectl merges the local file with values pulled down from the cloud. I've done the following: The I just set is silently overridden. Questions: is this documented anywhere? should kubectl merge in my GCE cluster when I set my cloud-provider to something else? should kubectl override my previously set current-context?\nworkaround is to use flag to override the config file value.\nbut not a good UX long term\nSomeone else hit this as well: . Better fix is to have the local-up script set a context, which I will try to add today. As for the overwriting behavior, it's documented in , but based on what you describe, the intended load order is not working; local .kubeconfig should overwrite global. cc\nThat sounds infuriating. I'll take a look this morning.", "commid": "kubernetes_issue_4397", "tokennum": 210}], "negative_passages": []}
{"query_id": "q-en-kubernetes-83a6c439d4aa2b2ad43f81bb5695d8631579171540c67f30e5afe4deea434252", "query": "UpdateFake(obj *metav1.PartialObjectMetadata, opts metav1.UpdateOptions, subresources ...string) (*metav1.PartialObjectMetadata, error) } <ins> // NewTestScheme creates a unique Scheme for each test. func NewTestScheme() *runtime.Scheme { return runtime.NewScheme() } </ins> // NewSimpleMetadataClient creates a new client that will use the provided scheme and respond with the // provided objects when requests are made. It will track actions made to the client which can be checked // with GetActions().", "positive_passages": [{"docid": "doc-en-kubernetes-d7e6fda1614d5720cc8c8b15824f08c5e880f7950d0c5cc5cd811c2fcceb82ab", "text": "Because of this scheme mutation, this leads to concurrent use of the same scheme to cause the program to panic. It would be ideal to do this in some concurrent safe manner or add a warning or similar\n/sig api-machinery\n/assign\n/assign /triage accepted", "commid": "kubernetes_issue_107823", "tokennum": 54}], "negative_passages": []}
{"query_id": "q-en-kubernetes-83aa217d98247c74a6352d157d0749da944ebf6b39dc84955fdee6a06efa1808", "query": "cache.ResourceEventHandlerFuncs{UpdateFunc: vs.syncNodeZoneLabels}, zoneLabelsResyncPeriod, ) <ins> nodeLister := informerFactory.Core().V1().Nodes().Lister() vs.nodeManager.SetNodeLister(nodeLister) </ins> klog.V(4).Infof(\"Node informers in vSphere cloud provider initialized\") }", "positive_passages": [{"docid": "doc-en-kubernetes-b9a7a79272b4f05e986ec052f9f8348c60cffedf2d99a44ddafb98b4101b558f", "text": "I am enabling CSI migration on a vSphere cluster. A node was fully drained, all its Pods are deleted, but just before KCM detaches in-tree vSphere volume volumes from it, KCM restarts. A new KCM starts, sees attached volumes in that are not needed by any Pod on the node and calls vSphere in-tree volume plugin . The in-tree vSphere volume plugin + cloud provider marks the volume as detached right away, without reaching to vCenter API. The volume remains attached forever. I don't think it's related to CSI migration, IMO a regular node drain + KCM restart at the same time can cause the same issue. KCM logs: The in-tree cloud provider has a and from it. It apparently has not processed all nodes at the time A/D controller tries to detach the node. The in-tree vSphere volume plugin + cloud provider detaches the volume in vCenter. That's really tricky, it's very hard / impossible to reproduce on a real cluster. I had to inject errors to Detach() in-tree volume call, so they fail until KCM is restarted. Newly started KCM would detach the volume just fine (no error would be injected there), but marks the volume as detached right away. For the record (and search-ability), the CSI driver that tries to attach the volume to another node complains either: Or: cc It could be somewhat related to , however, not all cases of can be related to KCM restart. As I mentioned above, it's very hard/impossible to synchronize KCM restart with draining a node in a real cluster. <details</details<detailsvSphere 7.0.3 </details<details</details<detailsOpenShift </details<detailsCRI-O </details<details</details\n/sig storage\nTried just moving a Pod between nodes without CSI migration involved + restarting KCM when the volume is still attached to the old node. In-tree volume plugin on the new node says:\n/assign\nWhat CSI driver version and K8s version are you testing with?\nKubernetes is 1.25 and CSI driver is 2.7, still, I think it's not releated to the CSI driver, it's KCM who marks the in-tree volume as detached due to not populated node cache.", "commid": "kubernetes_issue_117091", "tokennum": 517}], "negative_passages": []}
{"query_id": "q-en-kubernetes-83aa217d98247c74a6352d157d0749da944ebf6b39dc84955fdee6a06efa1808", "query": "cache.ResourceEventHandlerFuncs{UpdateFunc: vs.syncNodeZoneLabels}, zoneLabelsResyncPeriod, ) <ins> nodeLister := informerFactory.Core().V1().Nodes().Lister() vs.nodeManager.SetNodeLister(nodeLister) </ins> klog.V(4).Infof(\"Node informers in vSphere cloud provider initialized\") }", "positive_passages": [{"docid": "doc-en-kubernetes-27c84c169fad17ff032040ca08c7bb73c7215213dd29c5491da1ee415abb2a33", "text": "/assign\n/triage accepted\nI found an easier way how to reproduce this without extra code in KCM: a StatefulSet with 1 Pod that uses 1 PVC. the node where the Pod runs. down kube-controller-manager to zero (not really possible for me) or kill all kube-controller-manager Pods. This will cause new KCM processes to wait for leader election. In my env. this gives me ~30 seconds for the next step. Delete the Pod. A new one will be scheduled on a different node (because the current node is cordoned) + there is no KCM running at this time that would detach the volume from the old node. KCM wins its leader election, sees a volume attached to a node where it is not needed -it calls of the volume plugin. VSphere cloud provider does not have its caches populated yet (= this bug) -the volume is not detached, but returns success.\ndangling attach does not help here. The volume is still attached to the old node even after ~10 minutes. fails with and not with . I can see there is a lot of dangling attach code in the cloud provider, but I did not debug further.", "commid": "kubernetes_issue_117091", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-83b2b776a2e64f877ed0226431aa85eff80c84767731c73e4982e391db9a8e7e", "query": "// Status of containers in the pod. ContainerStatuses []*ContainerStatus // Status of the pod sandbox. <ins> // Only for kuberuntime now, other runtime may keep it nil. </ins> SandboxStatuses []*runtimeapi.PodSandboxStatus }", "positive_passages": [{"docid": "doc-en-kubernetes-59e10ac9f842c5137d16434532387dd09ba10f619a9264b3e368e8bd51bb44b7", "text": "What happened: It's most visible in the test <img width=\"323\" alt=\"Screen Shot 2020-05-20 at 6 09 10 PM\" src=\"https://user-\"It shows up in kind, kube- and kops jobs The regression was introduced somewhere within , possible culprits are: (FYI (FYI (FYI There are more tests affected, just not as prominently (visually inspecting ) [sig-apps] StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications with PVCs [sig-apps] StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance] [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Inline-volume (default fs)] volumes should store data [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data I wasn't sure whether to tag this as kind/regression or not, I'll leave that up to or someone /sig node /sig api-machimery /sig scheduling\nThe label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : What happened: It's most visible in the test (FYI (FYI (FYI StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications with PVCs [sig-apps] StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance] [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Inline-volume (default fs)] volumes should store data [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data /sig api-machimery /sig scheduling 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.", "commid": "kubernetes_issue_91316", "tokennum": 506}], "negative_passages": []}
{"query_id": "q-en-kubernetes-83b2b776a2e64f877ed0226431aa85eff80c84767731c73e4982e391db9a8e7e", "query": "// Status of containers in the pod. ContainerStatuses []*ContainerStatus // Status of the pod sandbox. <ins> // Only for kuberuntime now, other runtime may keep it nil. </ins> SandboxStatuses []*runtimeapi.PodSandboxStatus }", "positive_passages": [{"docid": "doc-en-kubernetes-aa1ca8a6c4f552108d5e4f5627cf5341a0bb7748f7b82e510f647cbc02b0a76b", "text": "</details\n/cc\nwill increase the time for deletion of pod and it should be expected because currently pod is deleted from apiserver before removing the sandbox container but after this fix pod will be deleted from the apiserver only after deleting the sandbox container.\n/remove-sig scheduling doesn't affect scheduling running time at all.\nYeah, is almost definitely the culprit. Last time we changed that code path, it also caused a regression. The degradation in performance is expected, but a 5x slowdown is definitely larger than it should be.\ndo we know if that's because the status used by the path is stale, or if removing sandboxes is actually that slow?\nif there's not a quick fix, should we revert and bring it back in once the root issue is understood?\nI think a revert is appropriate in this case.\nok, I'll open it\nopen at\nI agree with that 5x is something which shouldn't happen and i can take a look on why thats happening and that might require changing the way how the sandbox is currently deleted which is only during GC.", "commid": "kubernetes_issue_91316", "tokennum": 237}], "negative_passages": []}
{"query_id": "q-en-kubernetes-83c093008c63be620505930e3ff974f921b7cbc00bde6eac1a282f99a6e075fc", "query": "metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/util/wait\" \"k8s.io/client-go/kubernetes/fake\" <del> \"k8s.io/kubernetes/pkg/apis/apps\" </del> kubepod \"k8s.io/kubernetes/pkg/kubelet/pod\" \"k8s.io/kubernetes/pkg/kubelet/prober/results\" \"k8s.io/kubernetes/pkg/kubelet/status\"", "positive_passages": [{"docid": "doc-en-kubernetes-8720ed8a574bdce7c104bd3a62cc93935fad36eef53bf2f2ff98186bbe4abc40", "text": "The metric used to report acutal pod in the label , but now I see the podname prefix only. The full pod name in the label, so I can trace the metric to the failing pod. Check raw api and verify the actual pod name with uids. <details</detailsAzure AKS <details</detailsNo response No response No response_\n/sig node\n/triage accepted /priority important-soon /cc As discussed this is a change in functionaloty that wasn't highlighted in release notes. Need to decide on what do do with it. I understand it's a change of functionality. what is the side effect of this for you? Does the label without last part not informational enough?\nI've been using the metric in my custom grafana dashboard that shows CPU, RAM, IO usage of pods with graph of increases in probes. If the apps are stable, the probe graph looks steadily. I can see if some irregularities in system metrics are influencing probes of respective pod. Also, if readiness probe is failing, the pod is removed from service, but is not restarted so I must have knowledge of pods with failing readiness probes. I attach the screenshot of my graph. ! So I'd welcome the possibility to pair the probes with exact pod and thank you for looking into it.\nare we thinking that this resulted in an undesirable change? Spologies for being a bit late to reply, I'm returning from a brief paternity leave staycation.\nThis issue is labeled with but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release. You can: Confirm that this issue is still relevant with (org members only) Deprioritize it with or Close this issue with For more details on the triage process, see /remove-triage accepted\nWell this is awkward... I still believe the actual behavior does not respect the intended idea...\nThis issue makes it hard to link probe metrics with right pods. The value of pod label in and are also inconsistent with how it is used in other kubelet metrics, see: vs Definitely a bug, regression since 1.25.\nI can't get anyone to look at the fix/revert: you may have better luck\n/milestone v1.28\ndiscussion in\nYou've pushed it through, congrats!", "commid": "kubernetes_issue_115766", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-83e7571f94062f9be00fab22d77c397c3903abf53d57e84e39b915ce53f4472f", "query": "expectedErrMsg:      fmt.Errorf(\"failure of getting instance metadata\"), }, { <del> name:                \"NodeAddresses should report error if VMSS instanceID is invalid\", nodeName:            \"vm123456\", metadataName:        \"vmss_$123\", vmType:              vmTypeVMSS, useInstanceMetadata: true, expectedErrMsg:      fmt.Errorf(\"failed to parse VMSS instanceID %q: strconv.ParseInt: parsing %q: invalid syntax\", \"$123\", \"$123\"), }, { </del> name:                \"NodeAddresses should report error if cloud.vmSet is nil\", nodeName:            \"vm1\", vmType:              vmTypeStandard,", "positive_passages": [{"docid": "doc-en-kubernetes-93c0a615d6725c12b66abb2dead01e17ca700d451119b1467d3edce68f73a013", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: If computer name prefix does not match VMSS name, then Azure cloud provider will use VMSS API instead of using metadata service data. This leads to throttling, because every affected kubelet is making API requests. What you expected to happen: Azure cloud provider should use metadata service data instead of calling VMSS API when instance is current. How to reproduce it (as minimally and precisely as possible): Set computer name prefix of the VMSS to something different than default. You should observe Azure provider making requests to the VMSS API rather than using metadata service, which leads to throttling if you have multiple kubelets with this bug. Anything else we need to know?: This is bug was introduced by - returns false even if instance is current, because it expects node name to match VMSS name + instance id, however node name is derived from the computer-name-prefix which can be different than VMSS name. Node name should be matched against , not against . Environment: Kubernetes version (use ): 1.18.x and higher Cloud provider or hardware configuration: azure /sig cloud-provider\n/sig cloud-provider\n/area provider/azure\nCC\n/remove-sig cloud-provider /sig cloud-provider (trying to remove the label)\n/sig cloud-provider\nThanks for the reporting. Unfortunately, computer name prefix is not included in IMDS, so it can't be used without VMSS API for constructing the NodeName. Would check what could we do to workaround the issue.\nCan you memorize the computer name prefix in the first request to the Azure API and then use it for the isCurrentInstance check?\nopened to fix the issue. Would you like to have a look?\nI can confirm that your change should fix the problem I reported. Do you know if your fix will be to 1.18.x?\nis working on the cherry pick\nThank you for quick fix!", "commid": "kubernetes_issue_92733", "tokennum": 464}], "negative_passages": []}
{"query_id": "q-en-kubernetes-83fc1383f2484af86bd93e52b7720acb211dfefd83bd33a496b341ea6e6c1fb9", "query": "OOMScoreAdj:        config.OOMScoreAdj, ConfigSyncPeriod:   config.ConfigSyncPeriod.Duration, HealthzServer:      healthzServer, <ins> UseEndpointSlices:  false, </ins> }, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-94306baf6d6408dd320a641269af3f429c4d2a949a311ade7ed7994b23100633", "text": "After this () has been merged and EnpointSlice feature is now enabled by default, we noticed Kube-proxy will not work on Windows. Only message I can see in the logs is: /sig windows\n/cc /cc /cc\nHow about separating the above check into two if statements so that the log can pinpoint which field is false ?\nIt seems long term, EndpointSlice support should be so that is kept in sync with other implementations.\ncc\nThanks for reporting this! Windows proxiers were still intended to be reading from Endpoints, but apparently that's not working as intended. EndpointSlices are moving back to disabled by default for 1.17, so that should fix the failing tests for now. I'll work on an actual fix for this as well, but it may not make it in until after KubeCon. /assign /sig network /priority important-soon\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/remove-triage unresolved\n/assign cc\nGitHub didn't allow me to assign the following users: jocelynberrendonner. 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 cc 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\n: Please let me know if you need any help on the fix! I'll be more than happy to review/help test the fix on Windows.", "commid": "kubernetes_issue_85352", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-840a4c4d10dc0b459a5952ff34aed8bcadcf340a0df2b2537b07f569e355c461", "query": "}) It(\"should serve a basic image on each replica with a private image\", func() { <del> switch testContext.Provider { case \"gce\", \"gke\": ServeImageOrFail(c, \"private\", \"gcr.io/_b_k8s_authenticated_test/serve_hostname:1.1\") default: </del> <ins> if !providerIs(\"gce\", \"gke\") { </ins> By(fmt.Sprintf(\"Skipping private variant, which is only supported for providers gce and gke (not %s)\", testContext.Provider)) <ins> return </ins> } <ins> ServeImageOrFail(c, \"private\", \"gcr.io/_b_k8s_authenticated_test/serve_hostname:1.1\") </ins> }) })", "positive_passages": [{"docid": "doc-en-kubernetes-5702d542be386cac9e4333778515fd94620fcdb52c66d8dfc11487da78971dda", "text": "I noticed while running e2e tests locally that some tests were apparently being incorrectly skipped: I checked, and this is also true for our Jenkins runs. Currently it looks like and have this bug, though only the former actually skips the test, I think. The issue appears to be that the code inside the top-level in these files is being run before the testContext struct is filled out (and before is even called), and so testContext.Provider is empty. I'm not immediately sure what the proper fix is; I'm also worried that there might be other things broken by the fact that these blocks are called before initialization is complete. We also probably investigate if there is a better way to mark these tests as skipped; right now, there's no indication in the test report (, Jenkins test report, etc) that these tests were skipped.\nI merged and which tried to disable these tests for non-{gke,gce} but apparently didn't follow-up and verify that they were still running on our platforms. /cc\nSeems easy enough to fix. I'll have a PR out to fix this before Monday.", "commid": "kubernetes_issue_7008", "tokennum": 242}], "negative_passages": []}
{"query_id": "q-en-kubernetes-84621684bd6c380719c7fff4929287f62abfd945d806de7f5557173e2713605c", "query": "DeleteLocalData     bool Selector            string PodSelector         string <del> Out                 io.Writer ErrOut              io.Writer </del> <ins> // DisableEviction forces drain to use delete rather than evict DisableEviction bool Out    io.Writer ErrOut io.Writer </ins> // TODO(justinsb): unnecessary? DryRun bool", "positive_passages": [{"docid": "doc-en-kubernetes-1de7ff63e7ce8b64bf52f2105a2efc7375b6d0f9c29fe56834b2956453e0280d", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Allow to have an additional flag (e.g. or ) to allow a to drain pods off a node, even if they violate PodDisruptionBudgets Why is this needed: There are times where you want to drain pods off a node even if violating a PDB. For example, if you are running a one-worker node kubernetes cluster (not minikube), and you want to upgrade it. Or, like me, you are running a test cluster and want to scale down to zero nodes when you're not going to be using the cluster for a while in order to save costs. If that worker node has a deployment with a PDB, then will get stuck as it cannot get rid of the pod while respecting the PDB, which is expected; but in this case, it is a hindrance. Adding the switch will allow users to explicitly acknowledge that they want to ignore the PDBs (and accept the corresponding downtime for an application/service)\n/sig node\n+1\n+1 Our company offers Kubernetes as PaaS. We manage Kubernetes, including IaaS OS updates and if a customer does not specify the PDB correctly, we are not able to drain the node for the OS updates. A flag would be werry helpfull for our use case.\n+1\n/active\nI have created to address this. This is a pretty simple implementation, but I think it achieves the desired results. A suitable workflow would be: 1) Configure you component to use drain as normal 2) After some timeout, run drain with --disable-eviction option.\nI'll wait until the PR is merged and released before testing, but if I understand right, it would require me do this, right? If so, I think it would be better if we did it a different way and have one call, something like this: Where implies that if the drain is still running after this time, switch to the mode without having to call kubectl again\nI think that would require a sizeable refactor or add a great deal of complexity to the code, the same could be achieved with In practical terms, I'm focused on automatic node remediation via destroying the node and getting a new one. The timeout would be very large, the drain library is blocking, so I want it to fail quickly and requeue.", "commid": "kubernetes_issue_83307", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-84621684bd6c380719c7fff4929287f62abfd945d806de7f5557173e2713605c", "query": "DeleteLocalData     bool Selector            string PodSelector         string <del> Out                 io.Writer ErrOut              io.Writer </del> <ins> // DisableEviction forces drain to use delete rather than evict DisableEviction bool Out    io.Writer ErrOut io.Writer </ins> // TODO(justinsb): unnecessary? DryRun bool", "positive_passages": [{"docid": "doc-en-kubernetes-b7bae32dd27973078cd1b23d1dbdce25c736eb34a86ee68bc51d78045bb08cfb", "text": "I'm going to be performing the calculation of when it's appropriate to evict/delete outside of the drain library, and I suspect most will be as well, so there's not really a great incentive to do it in the drain library itself IMO.\nThat's all good, I have no issue using the flag as long as does error out and return a non-zero code as expected (there's been a few times where it seems to error out, but still return 0)", "commid": "kubernetes_issue_83307", "tokennum": 105}], "negative_passages": []}
{"query_id": "q-en-kubernetes-84a592279cf74a2e6e7de5d831af54272a1792c704ba412b3e4ebea6774239db", "query": "// RemoveContainer removes the container. func (ds *dockerService) RemoveContainer(_ context.Context, r *runtimeapi.RemoveContainerRequest) (*runtimeapi.RemoveContainerResponse, error) { <del> ds.performPlatformSpecificContainerForContainer(r.ContainerId) </del> // Ideally, log lifecycle should be independent of container lifecycle. // However, docker will remove container log after container is removed, // we can't prevent that now, so we also clean up the symlink here.", "positive_passages": [{"docid": "doc-en-kubernetes-486ca0159276eedd0d2aa336961ee5fd6fb83d0ac97af7f3f9c8c863d43fcef2", "text": "What would you like to be : Periodically remove cleanupInfos for old containers from dockershim's map. One way of doing that would be to just forget about s older than say an hour, as they should always be short-lived. Why is this needed: introduced a new in-memory map for the dockershim, that could potentially (in pathological cases) cause memory leaks - for containers that use GMSA cred specs, get created successfully, but then never get started nor removed. This might be okay for the alpha release of the GMSA feature, but should be addressed in the beta. See\n/assign wk8\n/sig windows\n/milestone v1.15\ngot moved out. let's move this issue with it as well /milestone v1.16\nHello! I'm bug triage lead for the 1.16 release cycle and considering this issue is tagged for 1.16, but not updated for a long time, I'd like to check its status. The code freeze is starting on August 29th (about 1.5 weeks from now), which means that there should be a PR ready (and merged) until then. Do we still target this issue to be fixed for 1.16?\n: yup we'd love to have this in 1.16, still waiting for kind reviewers on :) ...", "commid": "kubernetes_issue_74843", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-84f207fa68c444cc8e2226260715474e961ee7a619b9f2cc50546cbcfa22c6b1", "query": "t.Fatalf(\"unexpected proxy user: %v\", authUser) } } <ins> // The channel must be closed before any of the connections are closed close(closed) </ins> }) } })", "positive_passages": [{"docid": "doc-en-kubernetes-631bc5da562ebc33bd49790f3078648639a2126878c5fc7773cd8143bd3bdf27", "text": "TestRoundTripSocks5AndNewConnection Disabled by No response No response No response /sig\nThere are no sig labels on this issue. Please add an appropriate label by using one of the following commands: - Please see the for a listing of the SIGs, working groups, and committees available. <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\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nthere is a race shutting down the socks5 server", "commid": "kubernetes_issue_107766", "tokennum": 198}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8527f1762aa8c9623597004716e633fb9b2f430f3c92a77bf4219e1b87d86b74", "query": "network_mode: openvswitch node_ip: $MINION_IP etcd_servers: $MASTER_IP <ins> api_servers: $MASTER_IP </ins> networkInterfaceName: eth1 apiservers: $MASTER_IP roles:", "positive_passages": [{"docid": "doc-en-kubernetes-8f6e6c1f685c98cc169477efadd1a12031a77645ead6fa9fa244a9ca04430443", "text": "is sent as a fix. cc It's a test failure reported by the publishing robot.\nThe line it fails at:\nIt looks like a vendor copy vs gopath copy issue.\nOne possible fix is removing from the vendor/ directory. I'm testing locally.\nConfirmed removing from the vendor/ directory fixed the test in robot.\nWe need to add the \"issue filer\" feature to the publishing robot, we can't rely on to report robot issues everytime :P I'm just not sure how long the publishing robot will be needed (i.e., when we will get rid of the staging/ directory) so not sure whether we should invest more time on the robot.", "commid": "kubernetes_issue_45693", "tokennum": 141}], "negative_passages": []}
{"query_id": "q-en-kubernetes-855ae5a86b901ddba759970a4b331ab71561fd3db3f6cbbbf8804baaf24944f4", "query": "\"Foo\": defaultbinder.New, } cases := []struct { <del> name         string opts         []Option wantErr      string wantProfiles []string </del> <ins> name          string opts          []Option wantErr       string wantProfiles  []string wantExtenders []string </ins> }{ { name: \"valid out-of-tree registry\",", "positive_passages": [{"docid": "doc-en-kubernetes-75719ce40debdc24665e0bd0c466c638c232f756949a78511459bd94dde06b58", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --here is supposed to be set through , but is not called from anywhere except tests, so always returns . should be set through here. Am I missing something? N/A None Kubernetes version (use ): master () Cloud provider or hardware configuration: N/A OS (e.g: ): N/A Kernel (e.g. ): N/A Install tools: N/A Network plugin and version (if this is a network-related bug): N/A Others: None\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scheduling\nThanks for pointing that out. The plumbing of extenders to the framework impact calling extenders on preemption. That seems to be a path not covered by tests end to end. Can you submit a PR to fix this? as you mentioned we need to pass the extenders on profile creation. We need to patch the fix back to v1.21 and v1.20 (the release where this was refactored). /cc\nI have submitted a PR for a fix.", "commid": "kubernetes_issue_102971", "tokennum": 348}], "negative_passages": []}
{"query_id": "q-en-kubernetes-856813cb7f4fc55181803a09f916e14c23eb6e99467cfbf7ebd23eb93a96465d", "query": "} t.Logf(\"rc._internal -> rc.v1\") <del> data, err = runtime.Encode(defaultGroup.Codec(), rc) </del> <ins> data, err = runtime.Encode(defaultCodec, rc) </ins> if err != nil { t.Fatalf(\"unexpected encoding error: %v\", err) }", "positive_passages": [{"docid": "doc-en-kubernetes-fe4a53f9c12ffb58184de5c048a5217a0a9a95660f59883741a14147feb2210e", "text": "Execute make test WHAT=./pkg/api/testing/ And it failed with information: /kind failing-test\n/sig api-machinery\nwhat's the urgency of fixing this? Is it a release blocker?\ni don't see it as a release blocker. but the problem is in client-go, so it's important to get fixed.", "commid": "kubernetes_issue_71369", "tokennum": 78}], "negative_passages": []}
{"query_id": "q-en-kubernetes-85bd6562d4deaa063e017d874880ee1caac967937aa729c3e365c248f7e1c1a7", "query": "addNodes(manager.nodeStore, 0, 1, nil) addPods(manager.podStore, \"node-0\", simpleDaemonSetLabel, ds, 1) addPods(manager.podStore, \"node-1\", simpleDaemonSetLabel, ds, 1) <ins> podScheduledUsingAffinity := newPod(\"pod1-node-3\", \"\", simpleDaemonSetLabel, ds) podScheduledUsingAffinity.Spec.Affinity = &v1.Affinity{ NodeAffinity: &v1.NodeAffinity{ RequiredDuringSchedulingIgnoredDuringExecution: &v1.NodeSelector{ NodeSelectorTerms: []v1.NodeSelectorTerm{ { MatchFields: []v1.NodeSelectorRequirement{ { Key:      schedulerapi.NodeFieldSelectorKeyNodeName, Operator: v1.NodeSelectorOpIn, Values:   []string{\"node-2\"}, }, }, }, }, }, }, } manager.podStore.Add(podScheduledUsingAffinity) </ins> if f { syncAndValidateDaemonSets(t, manager, ds, podControl, 0, 1, 0) } else {", "positive_passages": [{"docid": "doc-en-kubernetes-2bd3e1d9e94a5358a6c2d5b4c6b5864c879bb8cabae55e6531ce8f2da7e1ce93", "text": "What happened: Occasionally we get a Daemonset stuck with less Current replicas than Desired, causing a Daemonset sync tends to fix it, e.g (add a new node). This happens to all our Daemonsets. I'm using fluentd as an example. There are no Daemonsets pods in pending nor are there any errors when describing the Daemonset What you expected to happen: The Daemonset Pod to be scheduled How to reproduce it (as minimally and precisely as possible): Reproducing this state is very tricky, I've had the most success by terminating nodes in our ASG causing a new one to come up. However I think I've identified why this is happening. The issue appears to be related to daemonset Pod deletion, a Pod gets deleted causing to trigger, this lowers the expectations by as expected. The delete pod event then triggers a sync of the daemonset, in which it finds which involves fetching pods from the informer cache This is somehow returning the deleted pod. You can see in the logs here thinks that it needs to delete the pod that was deleted. It is also setting the expectation back to after the delete pod event previously lowered it by 1. At this point you're stuck as the function can't get past this line As the expectation can not be satisfied as syncNodes set it back to and there's nothing it to get it back to . So I believe this is what's causing us to get less replicas than expected, the function is stuck due to the expectation so it can't perform a full sync to schedule the new pods. There's also not much to trigger a new sync once the expectation has expired until a new node comes up or one goes down. Environment: Kubernetes version (use ):Cloud provider or hardware configuration: AWS OS (e.g: ):Kernel (e.g. ):\n/sig apps\nI investigated this as much as I could without getting some external input, it feels like it's some kind of race condition in the informer cache. If anyone has ideas of if places to dig deeper that would be handy.\nReiterating the mentions to trigger a notification: <detailsIn response to : I investigated this as much as I could without getting some external input, it feels like it's some kind of race condition in the informer cache. If anyone has ideas of if places to dig deeper that would be handy.", "commid": "kubernetes_issue_75836", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-85bd6562d4deaa063e017d874880ee1caac967937aa729c3e365c248f7e1c1a7", "query": "addNodes(manager.nodeStore, 0, 1, nil) addPods(manager.podStore, \"node-0\", simpleDaemonSetLabel, ds, 1) addPods(manager.podStore, \"node-1\", simpleDaemonSetLabel, ds, 1) <ins> podScheduledUsingAffinity := newPod(\"pod1-node-3\", \"\", simpleDaemonSetLabel, ds) podScheduledUsingAffinity.Spec.Affinity = &v1.Affinity{ NodeAffinity: &v1.NodeAffinity{ RequiredDuringSchedulingIgnoredDuringExecution: &v1.NodeSelector{ NodeSelectorTerms: []v1.NodeSelectorTerm{ { MatchFields: []v1.NodeSelectorRequirement{ { Key:      schedulerapi.NodeFieldSelectorKeyNodeName, Operator: v1.NodeSelectorOpIn, Values:   []string{\"node-2\"}, }, }, }, }, }, }, } manager.podStore.Add(podScheduledUsingAffinity) </ins> if f { syncAndValidateDaemonSets(t, manager, ds, podControl, 0, 1, 0) } else {", "positive_passages": [{"docid": "doc-en-kubernetes-cf3a9a922f150fcd06b37026fcb1a4fe5fd4fd3de4493928a0abbcee85e2e3a6", "text": "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\nThis problem is definitely related to node termination, it's trying to delete the already deleted pod from the node that's been terminated. The problem seems to go away if is set, I think although this kind of race condition may have always been possible, it's being frequently caused via Which is finding the non-existent pod in the pod cache and seeing that it is assigned to a non-running node, resulting in a request to delete the non-existent pod. cc\nReiterating the mentions to trigger a notification: <detailsIn response to : This problem is definitely related to node termination, it's trying to delete the already deleted pod from the node that's been terminated. 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\n/assign could you please take a look at this? It seems that it is related to the code you in .\nThanks for reporting the bug. Bug was introduced in which deleting pods without nodes. There is race condition between removing pod from cache and listing pods for DaemonSet. Bug occurs during following scenario: is deleted. for node is deleted by PodGCController. handler is executed by informer () set is to queue by delete handler () is processed and pods are taken from cache before deleted pod is removed. for deleted pod is not found so we add deleted pod to podsToDelete list (). are set to del:1() succeeds as pod is not found(). are never met so we need to wait till expectations expire. As fix I will send a change to so only pods that can't be deleted by PodGCController are deleted by DaemonSet controller.", "commid": "kubernetes_issue_75836", "tokennum": 399}], "negative_passages": []}
{"query_id": "q-en-kubernetes-85cf3dcceb648052dd83ebcc1ec400d721c28e5d582ce2a1f83a1e4900efd095", "query": "ID:               volumeV3.ID, Name:             volumeV3.Name, Status:           volumeV3.Status, <ins> Size:             volumeV3.Size, </ins> } if len(volumeV3.Attachments) > 0 {", "positive_passages": [{"docid": "doc-en-kubernetes-62f595d5f46f490d9eea1d39e1ba000bf29c92ed637615b4bae439425896a1f8", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: What happened: patched out the Size field (was PR ), it will cause issue again. See also and . What you expected to happen: PVC resizes of Cinder volumes successfully. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/kind bug /sig storage /sig openstack\n/assign", "commid": "kubernetes_issue_66705", "tokennum": 171}], "negative_passages": []}
{"query_id": "q-en-kubernetes-85f584455feb7b140ef016b8896597b2ed4dbfe253fc0c9e0b4984bdd1b1e9b1", "query": "// +build !ignore_autogenerated /* <del> Copyright 2016 The Kubernetes Authors. </del> <ins> Copyright 2017 The Kubernetes Authors. </ins> Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License.", "positive_passages": [{"docid": "doc-en-kubernetes-2c477631a31f290ae271a7ca0a83a97399cbf63c4cfd883674b6ddce7387fc19", "text": "What happened: Latest kubelet + Windows Docker version 1.14.0-dev refused to start any containers, error output: \"invalid option: Windows does not support MemorySwap\" How to reproduce it (as minimally and precisely as possible): It's always reproducible with Windows Docker 1.14.0-dev + latest kubelet code base. Anything else do we need to know: It didn't happen for Windows Docker 1.12.2-cs2-ws-beta. The reason behind the issue was because new code was for Windows Docker to check Resources parameters, it doesn't accept a non-zero value for MemorySwap: But kubelet was default to set an unlimited (-1) value. The issue was gone in my setup after applied a private fix to disable MemorySwap by set it to zero for Windows.", "commid": "kubernetes_issue_39003", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8608cded23b1e748b032bd930ac65990b2019e0d0c20353039b6a8d9df1418c8", "query": "<ins> apiVersion: v1beta3 kind: Namespace metadata: name: quota-example </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-b9774b02da3d7547dcc6ec82c6d1246d6586e28e6fe16ad58f3c28b2558ac905", "text": "Resource quota example is missing readme. Was it once there and was accidentally deleted?\nI wrote something up in Origin repo I need to repurpose for Kubernetes. Sent from my iPhone", "commid": "kubernetes_issue_8749", "tokennum": 41}], "negative_passages": []}
{"query_id": "q-en-kubernetes-865516108e14fa4f856d2c73418e0e5ab5db037e022ddb6e620a2c5478e754c4", "query": "func TestPriorityQueue_AddIfNotPresent(t *testing.T) { q := NewPriorityQueue(nil) <del> q.unschedulableQ.addOrUpdate(&highPriNominatedPod) </del> <ins> addOrUpdateUnschedulablePod(q, &highPriNominatedPod) </ins> q.AddIfNotPresent(&highPriNominatedPod) // Must not add anything. q.AddIfNotPresent(&medPriorityPod) q.AddIfNotPresent(&unschedulablePod)", "positive_passages": [{"docid": "doc-en-kubernetes-e059cd0647305d70a174ce6bffb9584a993a023526be428075760ddef27cc3b0", "text": "Which jobs are failing: pull-kubernetes-bazel-test Which test(s) are failing: bazel test //pkg/scheduler/internal/queue:godefaulttest Since when has it been failing: Testgrid link: Reason for failure: WARNING: DATA RACE Read at 0x00c000230db0 by goroutine 47: runtime.mapiterinit() +0x0 (PriorityQueue).flushUnschedulableQLeftover() +0x17a (PriorityQueue).flushUnschedulableQLeftover-fm() +0x41 () +0x61 () +0xce () +0x5a Previous write at 0x00c000230db0 by goroutine 45: runtime.mapassignfaststr() +0x0 (UnschedulablePodsMap).addOrUpdate() +0x30e () +0x601 testing.tRunner() +0x162 Goroutine 47 (running) created at: (PriorityQueue).run() +0x172 () +0xe0b () +0x50 () +0x5a5 testing.tRunner() +0x162 Goroutine 45 (running) created at: testing.(T).Run() +0x659 testing.runTests.func1() +0xa8 testing.tRunner() +0x162 testing.runTests() +0x4ee testing.(M).Run() +0x2ee () bazel-out/k8- +0x2fb Anything else we need to know: I'm very sorry about that. UnschedulablePodsMap is not thread-safe. In , lock will be acquired before operating UnschedulablePodsMap. But in , lock isn\u2018t be acquired. In the previous case, only a single thread runs so it's ok. But after add goroutine , there will be data race. So I need to acquire lock before operating UnschedulablePodsMap.\n/sig testing /sig scheduling", "commid": "kubernetes_issue_73021", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-866e09d1b4a9794262d6f48b0c9a67e0f3a501b86c6ca459821277377bee86df", "query": "}, }, { <ins> name: \"UnschedulableAndUnschedulableFilters\", plugins: []*TestPlugin{ { name: \"TestPlugin1\", inj:  injectedResult{FilterStatus: int(framework.Unschedulable)}, }, { name: \"TestPlugin2\", inj:  injectedResult{FilterStatus: int(framework.Unschedulable)}, }, }, wantStatus: framework.NewStatus(framework.Unschedulable, injectFilterReason).WithFailedPlugin(\"TestPlugin1\"), wantStatusMap: framework.PluginToStatus{ \"TestPlugin1\": framework.NewStatus(framework.Unschedulable, injectFilterReason).WithFailedPlugin(\"TestPlugin1\"), }, }, { </ins> name: \"SuccessAndSuccessFilters\", plugins: []*TestPlugin{ {", "positive_passages": [{"docid": "doc-en-kubernetes-63751a7023e8b04f1af20ab3ae3207ec2b4f40a0fbf73a42db07ba523eb8b990", "text": "changed the default behavior of scheduler framework's - from stopping at the first failed filter to always running all filters. This change breaks Cluster Autoscaler at scale. Cluster Autoscaler imports the scheduler framework to simulate filters on artificial nodes. In a (pretty common) one-pod-per-node scenario, the number of calls is ~quadratic wrt. the number of nodes needed for unschedulable pods - it can be a lot of calls. Before , in such scenario the vast majority of calls would stop at failing Fit or NodeAffinity filters, and not run the rest of them (e.g. PV-related filters). After the change, every call to runs all filters, which completely breaks Cluster Autoscaler at scale (an example scenario of 300 1-pod-per-node pods and 200 node groups takes 10min in 1.24, and ~50s in <1.22). Can we get the old behavior back? Or re-introduce the config option so that Cluster Autoscaler can set it accordingly? Ideally, we'd also like to get this backported as far as possible (the change was introduced in 1.24).\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scheduling\nThis seems to be a regression. I would be interested in adding a toggle flag that allows one to toggle on that behavior if this was done on purpose.\nThat PR wasn't supposed to change the behavior actually. Scheduler is always defaulted to stop upon the first Filter failure, and it's just we offered an option to continue go through other Filter plugins upon failures, and that option was removed recently. Let me check the code to see if there is a regression.\nWhen removed the following changes: It should have kept . I will submit a fix along with test, and backport to 1.24, 1.25, 1.26. Thanks for reporting!", "commid": "kubernetes_issue_114509", "tokennum": 478}], "negative_passages": []}
{"query_id": "q-en-kubernetes-866e09d1b4a9794262d6f48b0c9a67e0f3a501b86c6ca459821277377bee86df", "query": "}, }, { <ins> name: \"UnschedulableAndUnschedulableFilters\", plugins: []*TestPlugin{ { name: \"TestPlugin1\", inj:  injectedResult{FilterStatus: int(framework.Unschedulable)}, }, { name: \"TestPlugin2\", inj:  injectedResult{FilterStatus: int(framework.Unschedulable)}, }, }, wantStatus: framework.NewStatus(framework.Unschedulable, injectFilterReason).WithFailedPlugin(\"TestPlugin1\"), wantStatusMap: framework.PluginToStatus{ \"TestPlugin1\": framework.NewStatus(framework.Unschedulable, injectFilterReason).WithFailedPlugin(\"TestPlugin1\"), }, }, { </ins> name: \"SuccessAndSuccessFilters\", plugins: []*TestPlugin{ {", "positive_passages": [{"docid": "doc-en-kubernetes-64891c2c5f731cd49a5bc282c860dc0eba8f556ac4ce7c46f89d192c47705edc", "text": "cc /assign /kind bug /kind regression /priority critical-urgent /triage/accepted\nThanks Kuba, this is indeed a regression on the scheduler end.\n/open for patches\n/re-open /reopen\nReopened this issue. <detailsIn response to : /re-open /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThanks for the reporting, and thanks for the fix.\nReally sorry about this regression, and hope not to happen again. I think there's no e2e tests between kubernetes scheduler and cluster-autoscaler, so can we also have testcases of pods unschedulable in scheduling perf-test, maybe this can also help to prevent this happening again. UT benchmark test also makes sense, but it's not graphical.\nThanks for the quick fix! Unfortunately I'm afraid this kind of issue would only be caught in a large-scale test scenario, which is not cheap to run continuously.\nFor this particular issue, UT ( in the PR) is able to catch it. And hence doesn't need to be that complicated to test with cluster-autoscaler. However, standing from a broader angle, why we didn't catch the regression in perf test is b/c the triggering actor is unschedulable Pods, instead of schedulable Pods (which are the happy path most perf tests covered). So going forward, I'd like to see more perf tests to mixin unschedulable Pods, and hence more likely to surface this kind of issue. (we have preemptio preemption test suite but doesn't seem adequate)\nThis is not for the particular issue, but keeping an eye on whether there's any performance degradation between two kubernetes components, like we do for scheduling performance. but it's actually out of the scope of scheduler. I'll add it as one of the goals of\nActually, the schedulerperf has a test case . And, the schedulerperf collects the metric (), which has the label in it (). But, the problem is currently we don't distinguish the metric values by label on each data; we just collect/aggregate it regardless the label.", "commid": "kubernetes_issue_114509", "tokennum": 494}], "negative_passages": []}
{"query_id": "q-en-kubernetes-866e09d1b4a9794262d6f48b0c9a67e0f3a501b86c6ca459821277377bee86df", "query": "}, }, { <ins> name: \"UnschedulableAndUnschedulableFilters\", plugins: []*TestPlugin{ { name: \"TestPlugin1\", inj:  injectedResult{FilterStatus: int(framework.Unschedulable)}, }, { name: \"TestPlugin2\", inj:  injectedResult{FilterStatus: int(framework.Unschedulable)}, }, }, wantStatus: framework.NewStatus(framework.Unschedulable, injectFilterReason).WithFailedPlugin(\"TestPlugin1\"), wantStatusMap: framework.PluginToStatus{ \"TestPlugin1\": framework.NewStatus(framework.Unschedulable, injectFilterReason).WithFailedPlugin(\"TestPlugin1\"), }, }, { </ins> name: \"SuccessAndSuccessFilters\", plugins: []*TestPlugin{ {", "positive_passages": [{"docid": "doc-en-kubernetes-e7a581bff1a17589b65e3454390d917eb3d7571d932e457d6db360afa738d97e", "text": "(We can distinguish the metric values by any labels in the schedulerperf as we do in the metric ()) I'd say just distinguishing the happy path and unhappy path with label in metric should be enough to observe the particular performance degradation in the unhappy path.\ncould you help share the perf-dash link where this metric () is exposed?\nHm, cannot see any scheduler metrics result from the current perf-dash I see some configuration that seems to be to parse the schedulerperf result file though. https://perf- TBH, I haven't visited the perf-dash so much, so not sure whether it's not working for a long time, or got broken recently. Also, another thing, I noticed the perf-dash doesn't show all test cases. All test cases after haven't been executed.\nSo... probably, something wrong happens in  job (probably in the test case) and the schedulerperf is failing. The schedulerperf doesn't make the result file when fails, so I'm guessing that's why we cannot see any scheduler metrics results from the perf-dash. Okay, I found it. Let me open another issue for this.\ncc is this actually a regression, and is it resolved yet?\nIt's resolved by , and also cherry-picked to 1.24.x ~ 1.26.x. /close\nClosing this issue. <detailsIn response to : It's resolved by , and also cherry-picked to 1.24.x ~ 1.26.x. 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", "commid": "kubernetes_issue_114509", "tokennum": 369}], "negative_passages": []}
{"query_id": "q-en-kubernetes-86a25aed3aa0af9d5c4e2b2180ea579278ca5076c77702b4bb8b4fb1b2da2778", "query": "} }() err = r.cmd.Wait() <del> stopped <- true </del> <ins> close(stopped) </ins> if exiterr, ok := err.(*exec.ExitError); ok { klog.Infof(\"etcd server stopped (signal: %s)\", exiterr.Error()) // stopped", "positive_passages": [{"docid": "doc-en-kubernetes-f2910a5a7757744dd88700c551fb3f5fe81db92c4ae532e768f1444ef3ba7b10", "text": "It's at line 111 When the server stopped before timeout, the first goroutine will be block on because the receiver in the second goroutine is not exist. Changing to a buffered one may fix it. no goroutine leaks run related test with leak checker No response <detailsdev </details<detailsunknown </details<details</details<details</details<details</details<details</details\n/sig api-machinery\n/assign /triage accepted\n/cc\nIt should close the channel rather than write to it, that's the easiest fix", "commid": "kubernetes_issue_114070", "tokennum": 125}], "negative_passages": []}
{"query_id": "q-en-kubernetes-86a4be9e94cce166db2d3af74966a4b750a47b16d8b1f9e07827558ed6dab97a", "query": "- mkdir -p /home/kubernetes/containerized_mounter/rootfs - mount --bind /home/kubernetes/containerized_mounter/ /home/kubernetes/containerized_mounter/ - mount -o remount, exec /home/kubernetes/containerized_mounter/ <del> - wget https://storage.googleapis.com/kubernetes-release/gci-mounter/mounter.tar -O /tmp/mounter.tar </del> <ins> - wget https://dl.k8s.io/gci-mounter/mounter.tar -O /tmp/mounter.tar </ins> - tar xvf /tmp/mounter.tar -C /home/kubernetes/containerized_mounter/rootfs - mkdir -p /home/kubernetes/containerized_mounter/rootfs/var/lib/kubelet - mount --rbind /var/lib/kubelet /home/kubernetes/containerized_mounter/rootfs/var/lib/kubelet", "positive_passages": [{"docid": "doc-en-kubernetes-af2890d14d0991d34b559e2e2a7effc23a0b7cafb90e6ce93894f3fac456697c", "text": "We have a new vanity url, , which redirects to the GCS release bucket - e.g. Right now, the https endpoint doesn't work, since isn't in the list of domains on the certificate. Once it works, we should switch all references over to the nicer vanity URL. x-ref\nSo what it required to make this issues actionable? Where to add this for the certificate?\nthe issue tracking that is\nThis needs to be triaged as a release-blocker or not for 1.5\nnot a release blocker.\nIs it appropriate to move this to the next milestone or clear the 1.5 milestone? (and remove the non-release-blocker tag as well)\ncan this be closed?\nI forgot to get to this in 1.6, but it'd still be good to do.\ndo you want this in v1.7? is there a sig to own this?\ndoesn't need to block 1.7, no.\nThere are no sig labels on this issue. Please by:<br(1) mentioning a sig: <br(2) specifying the label manually: <br<brNote: method (1) will trigger a notification to the team. You can find the team list .\n/sig release", "commid": "kubernetes_issue_33726", "tokennum": 270}], "negative_passages": []}
{"query_id": "q-en-kubernetes-86a4f4978cbf12989e58e71644d003fa854b6acbf9333aa5e00fadf23e57f1ab", "query": "glog.Infof(\"managing multiple zones: %v\", managedZones) } <del> operationPollRateLimiter := flowcontrol.NewTokenBucketRateLimiter(10, 100) // 10 qps, 100 bucket size. </del> return &GCECloud{ <del> service:                  svc, containerService:         containerSvc, projectID:                projectID, region:                   region, localZone:                zone, managedZones:             managedZones, networkURL:               networkURL, nodeTags:                 nodeTags, useMetadataServer:        useMetadataServer, operationPollRateLimiter: operationPollRateLimiter, </del> <ins> service:           svc, containerService:  containerSvc, projectID:         projectID, region:            region, localZone:         zone, managedZones:      managedZones, networkURL:        networkURL, nodeTags:          nodeTags, useMetadataServer: useMetadataServer, </ins> }, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-599cbd9914ac52a34ee08ac617d1f4bd774f52f2d5bdcb07fa1a0e76f7194545", "text": "On a large cluster, the routecontroller basically makes O(n) requests all at once, and most of them error out with \"Rate Limit Exceeded\". We then wait for operations to complete on the ones that did stick, and damn the rest, they'll be caught next reconcile (which is a while). In fact, in some cases it appears we're spamming hard enough to get rate limited by the upper-level API DOS protections and seeing something akin to , e.g.: We can do better than this!\nc.f. , which is the other leg of this problem\nI took a look into code and it seems that we are doing full reconciliation every 10s. If we need to create 2000 routes at the beginning it seems to frequently. I think that we need to: first compute how many routes we have to create based on that try to spread them over some time to reduce possibility of causing 'rate limit exceeded' I will try to put some small PR together as a starting point.\nI'm reopening this one, since this doesn't seem to be solved. So basically something strange is happening here. With PR we have 10/s limit on API calls send to GCE. And we are still rate-limitted. However, according to documentation we are allowed for 20/s: So something either doesn't work or is weird.\nWhat is super interesting from the logs of recent run: It starts to creating routes: After 2 minutes from that, we are hitting \"Rate limit Exceeded\" for the first time: And only after 9 minutes we create the first route ever. The second one is created after 15 minutes, and from that point we create a number of them So it seems that nothing useful is happening for the first 2 minutes, and then between 3m30 and 9m30\nOK - so I think that what is happening is that all controllers are sharing GCE interface (and thuse they have common throttling). So if one controller is generating a lot of API calls, then other controllers may be throttled. has a hypothesis that it may be caused by nodecontroller.\nOne thing my PR didn't address (because it was late): Now we have some obnoxious differences in logging when you go to make a request, because the versus could actually be absorbing a fair amount of ratelimiter.", "commid": "kubernetes_issue_26119", "tokennum": 488}], "negative_passages": []}
{"query_id": "q-en-kubernetes-86a4f4978cbf12989e58e71644d003fa854b6acbf9333aa5e00fadf23e57f1ab", "query": "glog.Infof(\"managing multiple zones: %v\", managedZones) } <del> operationPollRateLimiter := flowcontrol.NewTokenBucketRateLimiter(10, 100) // 10 qps, 100 bucket size. </del> return &GCECloud{ <del> service:                  svc, containerService:         containerSvc, projectID:                projectID, region:                   region, localZone:                zone, managedZones:             managedZones, networkURL:               networkURL, nodeTags:                 nodeTags, useMetadataServer:        useMetadataServer, operationPollRateLimiter: operationPollRateLimiter, </del> <ins> service:           svc, containerService:  containerSvc, projectID:         projectID, region:            region, localZone:         zone, managedZones:      managedZones, networkURL:        networkURL, nodeTags:          nodeTags, useMetadataServer: useMetadataServer, </ins> }, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-bf24c8733a67a958496376416be2eb636c6e4bfb94999815173220461c93fd0c", "text": "It could before because of the operation rate limiter and operation polling anyways, but now could be worse.\n- yes I'm aware of that. And probably this is exactly the case here.\nI got fooled by that - I guess we should fix it somehow.\nOne approach to fixing it is a similar approach to the operation polling code, but in the : warn if we ratelimited for more than N seconds (and dump the request or something? not clear how to clarify what we were sending).\nI found something else - Kubelet is also building GCE interface: We have 2000 kubelets, so if all of them send multiple requests to GCE, we may hit limits.\nAny idea in what circumstances Kubelet will contact cloud provider?\nHmm - it seems it contacts GCE exactly once at the beginning. So it doesn't explain much.\nI think it's only here: I've rarely seen GCE ratelimit readonly calls, in practice, and kubelets come up pretty well staggered.\nOK - so with logs that I , it is pretty clear that we are very heavily throttled on GCE api calls. In particular, when I was running 1000-node cluster, I see lines where we were throttle for 1m30. I'm pretty sure it's significantly higher in 2000-node cluster. I'm going to investigate a bit more where all those reuqests come from.\nActually - it seems that we have a pretty big problem here. Basically, Kubelet seems to send a lot of requests to GCE. So to clarify: every time Kubelet is updating NodeStatus (so every 10s by default) it is sending an API call to GCE to get it's not addresses: that means, that if we have 2000 nodes, kubelets generate 200 QPS to GCE (which is significantly more than we can afford) We should think how to solve this issue, but I think the options are: increasing QPS quota or calling GCE only once per X statusUpdates.\nThe second issue is that we are throttled at the controller level too, and this one I'm tryin to understand right now.", "commid": "kubernetes_issue_26119", "tokennum": 457}], "negative_passages": []}
{"query_id": "q-en-kubernetes-86a4f4978cbf12989e58e71644d003fa854b6acbf9333aa5e00fadf23e57f1ab", "query": "glog.Infof(\"managing multiple zones: %v\", managedZones) } <del> operationPollRateLimiter := flowcontrol.NewTokenBucketRateLimiter(10, 100) // 10 qps, 100 bucket size. </del> return &GCECloud{ <del> service:                  svc, containerService:         containerSvc, projectID:                projectID, region:                   region, localZone:                zone, managedZones:             managedZones, networkURL:               networkURL, nodeTags:                 nodeTags, useMetadataServer:        useMetadataServer, operationPollRateLimiter: operationPollRateLimiter, </del> <ins> service:           svc, containerService:  containerSvc, projectID:         projectID, region:            region, localZone:         zone, managedZones:      managedZones, networkURL:        networkURL, nodeTags:          nodeTags, useMetadataServer: useMetadataServer, </ins> }, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-b1dad1b374e4c58d925d9fef62d9846d5e0e5eda04aecdd78a124036a36cf31c", "text": "- that said, any rate-limitting on our side, will not solve the kubelet-related problem\nHmm - actually looking into implementation it seems that NodeAddresses are only contacting metadata server, so I'm not longer that convinced...\nAlso, I think that important thing is that a single call to GCE API can translate to multiple api calls to GCE. In particular - CreateRoute translates to: get instance insert route a bunch of getOperation (until this is finished)\nOK - so I think that what is happening here is that since CreateRoute translates to: get instance insert route a bunch of getOperations That means that if we call say 2000 CreateRoute() at the same time, all of them will try to issue: getInstance at the beginning. So we will quickly accumulate 2000 GET requests in the queue. Once they are processed, we generate the \"POST route\" then for any processed. So It's kind of expected what is happening here. So getting back to the Zach`s PR - I think that throttling POST and GET and OPERATION calls separate is kind of good idea in general.\nBut I still don't really understand why do we get \"RateLimitExceeded\". Is that because of Kubelets?\nI think that one problem we have at the RouteController level is that if CreateRoute fails, we simply don't react on it. And we will wait at least 5 minutes before even retrying it. We should add some retries at the route controller level too. I will send out some short PR for it.\nBut I still don't understand why do we get those \"RateLimitExceeded\" error\nOK - so as an update. In GCE, we have a separate rate-limit for number of in-flight CreateRoute call per project. is supposed to address this issue.\nOK - so this one is actually fixed. I mean that it is still long, but currently it's purely blocked on GCE.\nAs a comment - we have an internal bug for it already.", "commid": "kubernetes_issue_26119", "tokennum": 438}], "negative_passages": []}
{"query_id": "q-en-kubernetes-86e5b23601f6a99129f514a43dac81f3cd61d23b71702835c773af8383693370", "query": "} servicePrincipalToken, err := auth.GetServicePrincipalToken(&config.AzureAuthConfig, env) <del> if err != nil { </del> <ins> if err == auth.ErrorNoAuth { if !config.UseInstanceMetadata { // No credentials provided, useInstanceMetadata should be enabled. return nil, fmt.Errorf(\"useInstanceMetadata must be enabled without Azure credentials\") } klog.V(2).Infof(\"Azure cloud provider is starting without credentials\") } else if err != nil { </ins> return nil, err }", "positive_passages": [{"docid": "doc-en-kubernetes-effe9bff1df2586252b385cbf4a7cacd04cb77f4739ff9c987e63818f9dc1c82", "text": "Currently there is no way to run without any identity (be it service principal or E/MSI). In reality code running on a worker node can use via - and only via - without the need to access ARM. Here is the proposed change a new mode authN = this mode, is basically telling the cloud provider to work any identity, this means only IMDS calls is allowed. This mode can be detected from if no SPN set and both MSI settings are set to . to use a config map within the cluster. This config map can be loaded on the cluster statically. or created - if not existent - in that then only is used in The net new result of the above is users bootstrapping clusters can configure the worker node to use without any identity on said worker nodes.\n/sig azure These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by \u200d\nIn-tree AzureDisk volume plugin is also depending on Azure credential to fetch lun id. we should figure out how to solve it without credential\nfetch disk lun id is also a dependency in kubelet code now, after my investigation, it could be removed on Linux node, while it cannot be removed on Windows node, need to change the k/k upstream code, there is a discussion on going here: , let' wait for the discussion result.\nFor Linux: 1- use IMDS my understanding is new api versions will have the disk/lun pairs. 2- don't use arm for the return of is the second parameter passed to . For Windows: I don't understand the dep on ARM for this. The above still apply, we just need to find a way to encode the value as ut return from that allow us to find the disk by on a windows machine. might be a good source for this. Ideally speaking. The value should be the same. But i will leave it for you to decide.\ncould be a good idea since currently it's a LUN num returned by Attach() and then it could be changed to the windows disk num, I will make the code change on v1.15 later, thanks for discussion.\nUpdate: PR would remove the VM API calls when getting the LUN number for AzureDisk.", "commid": "kubernetes_issue_77309", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-871ee5a5fba56088d31e0a14ea1f30bb49d81bb0c45746b71740fd920803e799", "query": "execAffinityTestForLBService(f, cs, svc) }) <del> // TODO: Get rid of [DisabledForLargeClusters] tag when issue #56138 is fixed. </del> // [LinuxOnly]: Windows does not support session affinity. <del> ginkgo.It(\"should be able to switch session affinity for LoadBalancer service with ESIPP off [Slow] [DisabledForLargeClusters] [LinuxOnly]\", func() { </del> <ins> ginkgo.It(\"should be able to switch session affinity for LoadBalancer service with ESIPP off [Slow] [LinuxOnly]\", func() { </ins> // L4 load balancer affinity `ClientIP` is not supported on AWS ELB. e2eskipper.SkipIfProviderIs(\"aws\")", "positive_passages": [{"docid": "doc-en-kubernetes-23d2f241356f8f089aacd04cb02b22714ea2023d38ddcb3dae2268a8e3824c6f", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug This is a followup from filed separately now that we're not tracking this as part of 1.9 release. The tests have been disabled with [DisabledForLargeClusters] tag for now, and this fact will be mentioned in the scalability validation report for v1.9. This issue tracks fixing the test so the tag can be removed and the test ran again in the large cluster. /assign /kind e2e-test-failure\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIs this e2e test still broken?\nSorry for the confusion here. Currently this e2e test is disabled on extra large cluster due to some scalability issues with the load balancer related components. At the moment the issues haven't been completely resolved yet.\nok, adding priority so that I know it's not a 1.13 blocker. /priority important-longterm\ncc - this is why the relevant tests for are not part of the e2e suite.\nThis issue is still valid --- some action items on top of my head: Figure out a plan to make service controller properly handle operations in parallel. Check on the status for cloud providers (especially GCP, which the test ran against) on handling large number of nodes as LB backends. /remove-triage unresolved\nIssues 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 .", "commid": "kubernetes_issue_56138", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-871ee5a5fba56088d31e0a14ea1f30bb49d81bb0c45746b71740fd920803e799", "query": "execAffinityTestForLBService(f, cs, svc) }) <del> // TODO: Get rid of [DisabledForLargeClusters] tag when issue #56138 is fixed. </del> // [LinuxOnly]: Windows does not support session affinity. <del> ginkgo.It(\"should be able to switch session affinity for LoadBalancer service with ESIPP off [Slow] [DisabledForLargeClusters] [LinuxOnly]\", func() { </del> <ins> ginkgo.It(\"should be able to switch session affinity for LoadBalancer service with ESIPP off [Slow] [LinuxOnly]\", func() { </ins> // L4 load balancer affinity `ClientIP` is not supported on AWS ELB. e2eskipper.SkipIfProviderIs(\"aws\")", "positive_passages": [{"docid": "doc-en-kubernetes-82e0e423f6c651003322d5e3ca8baa34b91f0522dd0c015fbde1e81f949704e6", "text": "/lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten /lifecycle frozen\n/reopen Reopening as is being reverted in\nReopened this issue. <detailsIn response to : /reopen Reopening as is being reverted in 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\nthese tests are flaking in xref\ncc since these were enabled by\nYeah - though these failures doesn't seem to be scale related, they seem to be test related to me. This basically means nodes without public ips: It's pretty much the same thing as (just for a different test). should be addressing these kinds of errors. [Not a release blocker for sure]\nBTW - has been opened directly for this one.\n... so since is closed, Can we close this and re-enable for large clusters ? (i.e. remove the Tag in that disables this test) ? I'm not up to speed on the history but 2 related notes I came across digging into related test today... 's a couple of TODOs in the code referencing this specific issue, but your above direct issue is now closed, so we can close this as well right?... And if so, we can remove the TODO on the test... -enabling the test ... not sure wether the timing is good right now (given that is open right now , which sparked my stumbling upon this issue :))\nWe tried to enable all of them and that caused us a bunch of issues and those had to be reverted: A couple tests were enabled later in: and those seem fine. The remaining (mostly session-affinity ones) had some issue, which so far we didn't have time to debug and I haven't heard a good explanation why those were failing. It's possible that they were improved with , but I doubt those would really cause the failures we've seen in the past. So until this is debugged (or at least understood) I'm reluctant to enabling them.", "commid": "kubernetes_issue_56138", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-871ee9d4f7d34f2cf5d05fbdcc6261a23c6125936de0e44dd751e3bfaa7c8cd7", "query": "out.Description = in.Description if in.Type != \"\" { out.Type = spec.StringOrArray([]string{in.Type}) <del> if in.Nullable { out.Type = append(out.Type, \"null\") } </del> <ins> } if in.XIntOrString { out.VendorExtensible.AddExtension(\"x-kubernetes-int-or-string\", true) out.Type = spec.StringOrArray{\"integer\", \"string\"} } if out.Type != nil && in.Nullable { out.Type = append(out.Type, \"null\") </ins> } out.Format = in.Format out.Title = in.Title", "positive_passages": [{"docid": "doc-en-kubernetes-42eca355948acd2923f06d9ab50c5116c5afebe4d73334e949a0d732f7352d29", "text": "The server-side validation does not check the type of values with . Create a CRD like: Then create a CR: It is not rejected, but should because must not be a boolean.", "commid": "kubernetes_issue_78817", "tokennum": 40}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8741e24353e28b19c9dfc249781e7e773d8837d2937e5855d93bda5ec41614d0", "query": "local -ra docker_cmd=( \"${DOCKER[@]}\" run \"${docker_run_opts[@]}\" \"${KUBE_BUILD_IMAGE}\") <del> # Remove the container if it is left over from some previous aborted run \"${DOCKER[@]}\" rm -f -v \"${KUBE_BUILD_CONTAINER_NAME}\" >/dev/null 2>&1 || true </del> <ins> # Clean up container from any previous run kube::build::destroy_container \"${KUBE_BUILD_CONTAINER_NAME}\" </ins> \"${docker_cmd[@]}\" \"$@\" <del> # Remove the container after we run.  '--rm' might be appropriate but it # appears that sometimes it fails. See # https://github.com/docker/docker/issues/3968 \"${DOCKER[@]}\" rm -f -v \"${KUBE_BUILD_CONTAINER_NAME}\" >/dev/null 2>&1 || true </del> <ins> kube::build::destroy_container \"${KUBE_BUILD_CONTAINER_NAME}\" </ins> } # Test if the output directory is remote (and can only be accessed through", "positive_passages": [{"docid": "doc-en-kubernetes-349c839c0314e1386e949c881af8735bbe6497abcf3a15697139e75deb1d1835", "text": "Github automatically adds a artifact to every release, which sounds very similar to the artifact that we generate as the release artifact. Assuming we don't have control over the naming or presence of the autogenerated source code artifact, I think we should consider renaming our published artifact to better disambiguate between the two.\nWe distribute most of our artifacts outside of GitHub. We should probably stop uploading this one entirely.\ncc\nWe've got a thread going on w/ Tim. /assign\ncan you please link so folks can follow the bread crumbs? ( cc )\n-- It's currently sensitive. Will share once there's an outcome.\nACK. thanks for the heads up\nI think it's safe to discuss openly at this point. We had a report that the sha512 hashes on our release artifacts were incorrect. We have confirmed that the mismatch was due to a bug in the release pipeline, and not malicious. This issue here was just a point of confusion that came out of that discussion.\nthanks !\n/assign\nGoing one step back since I think the exists for historical reasons: The client and server binaries were part of this bundle, which is not the case any more: So it seems that is mostly a collection of licenses and scripts. Do we really need it or may we cleanup some code paths and remove it completely?\n+1 to put the word out and remove it completely if no one depends on it.\nI'm not confident that CI is not using these versioned scripts, in fact i'm fairly sure that it is. However it would not be pulling it from github.\nThe 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]:\n/remove-lifecycle stale I think this remains as relevant as ever.\n/milestone v1.23\n/triage accepted\nHi and k8s 1.23 bug triage shadow here.", "commid": "kubernetes_issue_100460", "tokennum": 507}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8741e24353e28b19c9dfc249781e7e773d8837d2937e5855d93bda5ec41614d0", "query": "local -ra docker_cmd=( \"${DOCKER[@]}\" run \"${docker_run_opts[@]}\" \"${KUBE_BUILD_IMAGE}\") <del> # Remove the container if it is left over from some previous aborted run \"${DOCKER[@]}\" rm -f -v \"${KUBE_BUILD_CONTAINER_NAME}\" >/dev/null 2>&1 || true </del> <ins> # Clean up container from any previous run kube::build::destroy_container \"${KUBE_BUILD_CONTAINER_NAME}\" </ins> \"${docker_cmd[@]}\" \"$@\" <del> # Remove the container after we run.  '--rm' might be appropriate but it # appears that sometimes it fails. See # https://github.com/docker/docker/issues/3968 \"${DOCKER[@]}\" rm -f -v \"${KUBE_BUILD_CONTAINER_NAME}\" >/dev/null 2>&1 || true </del> <ins> kube::build::destroy_container \"${KUBE_BUILD_CONTAINER_NAME}\" </ins> } # Test if the output directory is remote (and can only be accessed through", "positive_passages": [{"docid": "doc-en-kubernetes-dbd15f43daca5c062443bfb889f914327019b692ac2d45e387a4f7451b197946", "text": "There hasn't been any activity or linked PRs for this issue. Just wanted to check in to see if this is still on track for 1.23.\n/milestone v1.24\nHi I am part of the bug triage team for v1.24. We noticed that this issue hasn't been updated for a while. Just wanted to check if there is any work planned that would go into this.\nthis one keeps moving down the milestones. i don't see any activity since november. So kick the can down the road /milestone v1.25\nHi My name Hossein Salahi from Bug-Triage team. I am just checking to ensure if everything is on track for K8s 1.25. Thanks!\nThat's a question for or\nany remarks on that?\nthe release 1.25 bug triage Lead. I'm reaching out to see the status of this issue and if we are still targeting the current release. Also, kindly if you can update the priority so we can track it in the future.\nthis one keeps moving down the milestones yet again!. i don't see any activity since i moved this down the line. So kick the can down the road: /milestone clear (instead of v1.26 as this has been moving down the line for a few releases now)\nThe 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]:\n/remove-lifecycle stale\nWhat's the current status of this issue? Is there anything that we can do to move this forward?\nWe got new conversations going on during Kubecon on whether we should publish our release binaries on GitHub. Given that and I think we should rethink now what we publish on the release pages. I think we should start publishing all binaries for one. It is a common practice everywhere and I think users largely expect them to be there.", "commid": "kubernetes_issue_100460", "tokennum": 505}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8741e24353e28b19c9dfc249781e7e773d8837d2937e5855d93bda5ec41614d0", "query": "local -ra docker_cmd=( \"${DOCKER[@]}\" run \"${docker_run_opts[@]}\" \"${KUBE_BUILD_IMAGE}\") <del> # Remove the container if it is left over from some previous aborted run \"${DOCKER[@]}\" rm -f -v \"${KUBE_BUILD_CONTAINER_NAME}\" >/dev/null 2>&1 || true </del> <ins> # Clean up container from any previous run kube::build::destroy_container \"${KUBE_BUILD_CONTAINER_NAME}\" </ins> \"${docker_cmd[@]}\" \"$@\" <del> # Remove the container after we run.  '--rm' might be appropriate but it # appears that sometimes it fails. See # https://github.com/docker/docker/issues/3968 \"${DOCKER[@]}\" rm -f -v \"${KUBE_BUILD_CONTAINER_NAME}\" >/dev/null 2>&1 || true </del> <ins> kube::build::destroy_container \"${KUBE_BUILD_CONTAINER_NAME}\" </ins> } # Test if the output directory is remote (and can only be accessed through", "positive_passages": [{"docid": "doc-en-kubernetes-63377ea8eda65aaaac09acc9ed7dd8461429e8729a6daebbb93d9c0997493c68", "text": "let's scope the issue to the actual \"Kubernetes Source Code\" tarball. We can still remove it from what I can see from the discussion.\nI agree with Removing the \"Kubernetes Source Code\" tarball should be as easy as removing this from krel: However, there are a few questions: is it safe to do so? I believe yes, because this \"Kubernetes Source Code\" tarball is pointing to the GCS bucket, and we'll still continue publishing that tarball to the bucket The link is also available in the changelog, so it's easy to find do we need any deprecation period? Considering the above two points, I don't think so. If you folks agree with that, I can go ahead and create a PR to update krel.\nI agree on that, let's drop an additional note on k-dev that others are aware of the change.\n/assign\nUpdate: An announcement to proceed with the removal of the \"Kubernetes Source Code\" artifact has been sent to k-dev: PR to remove this artifact from being published: Removal will go into effect starting the January patch releases.", "commid": "kubernetes_issue_100460", "tokennum": 245}], "negative_passages": []}
{"query_id": "q-en-kubernetes-87498deae5bd4bea7e96d4e7916257e1b1d621370b1cc323623c16733900ccd3", "query": "if diff := cmp.Diff(tc.wantProfiles, profiles); diff != \"\" { t.Errorf(\"unexpected profiles (-want, +got):n%s\", diff) } <ins> // Extenders if len(tc.wantExtenders) != 0 { // Scheduler.Extenders extenders := make([]string, 0, len(s.Extenders)) for _, e := range s.Extenders { extenders = append(extenders, e.Name()) } if diff := cmp.Diff(tc.wantExtenders, extenders); diff != \"\" { t.Errorf(\"unexpected extenders (-want, +got):n%s\", diff) } // framework.Handle.Extenders() for _, p := range s.Profiles { extenders := make([]string, 0, len(p.Extenders())) for _, e := range p.Extenders() { extenders = append(extenders, e.Name()) } if diff := cmp.Diff(tc.wantExtenders, extenders); diff != \"\" { t.Errorf(\"unexpected extenders (-want, +got):n%s\", diff) } } } </ins> }) } }", "positive_passages": [{"docid": "doc-en-kubernetes-75719ce40debdc24665e0bd0c466c638c232f756949a78511459bd94dde06b58", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --here is supposed to be set through , but is not called from anywhere except tests, so always returns . should be set through here. Am I missing something? N/A None Kubernetes version (use ): master () Cloud provider or hardware configuration: N/A OS (e.g: ): N/A Kernel (e.g. ): N/A Install tools: N/A Network plugin and version (if this is a network-related bug): N/A Others: None\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scheduling\nThanks for pointing that out. The plumbing of extenders to the framework impact calling extenders on preemption. That seems to be a path not covered by tests end to end. Can you submit a PR to fix this? as you mentioned we need to pass the extenders on profile creation. We need to patch the fix back to v1.21 and v1.20 (the release where this was refactored). /cc\nI have submitted a PR for a fix.", "commid": "kubernetes_issue_102971", "tokennum": 348}], "negative_passages": []}
{"query_id": "q-en-kubernetes-87642e3f1a588c9f37e5e76a83825d6ca131e26dd77be0c9ef5af3d40d534c5f", "query": "if err != nil { return \"\", err } <del> if isLocalInstance { if metadata.Compute.VMSize != \"\" { return metadata.Compute.VMSize, nil </del> <ins> if !isLocalInstance { if az.vmSet != nil { return az.vmSet.GetInstanceTypeByNodeName(string(name)) </ins> } <ins> // vmSet == nil indicates credentials are not provided. return \"\", fmt.Errorf(\"no credentials provided for Azure cloud provider\") } if metadata.Compute.VMSize != \"\" { return metadata.Compute.VMSize, nil </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-effe9bff1df2586252b385cbf4a7cacd04cb77f4739ff9c987e63818f9dc1c82", "text": "Currently there is no way to run without any identity (be it service principal or E/MSI). In reality code running on a worker node can use via - and only via - without the need to access ARM. Here is the proposed change a new mode authN = this mode, is basically telling the cloud provider to work any identity, this means only IMDS calls is allowed. This mode can be detected from if no SPN set and both MSI settings are set to . to use a config map within the cluster. This config map can be loaded on the cluster statically. or created - if not existent - in that then only is used in The net new result of the above is users bootstrapping clusters can configure the worker node to use without any identity on said worker nodes.\n/sig azure These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by \u200d\nIn-tree AzureDisk volume plugin is also depending on Azure credential to fetch lun id. we should figure out how to solve it without credential\nfetch disk lun id is also a dependency in kubelet code now, after my investigation, it could be removed on Linux node, while it cannot be removed on Windows node, need to change the k/k upstream code, there is a discussion on going here: , let' wait for the discussion result.\nFor Linux: 1- use IMDS my understanding is new api versions will have the disk/lun pairs. 2- don't use arm for the return of is the second parameter passed to . For Windows: I don't understand the dep on ARM for this. The above still apply, we just need to find a way to encode the value as ut return from that allow us to find the disk by on a windows machine. might be a good source for this. Ideally speaking. The value should be the same. But i will leave it for you to decide.\ncould be a good idea since currently it's a LUN num returned by Attach() and then it could be changed to the windows disk num, I will make the code change on v1.15 later, thanks for discussion.\nUpdate: PR would remove the VM API calls when getting the LUN number for AzureDisk.", "commid": "kubernetes_issue_77309", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8797eef8b1200c8afc4252295c0dc42c980ff804d63269f52784a9e4700ef9be", "query": "jig.SanityCheckService(svc, v1.ServiceTypeLoadBalancer) defer func() { framework.StopServeHostnameService(cs, f.InternalClientset, f.ScalesGetter, ns, serviceName) <ins> lb := cloudprovider.GetLoadBalancerName(svc) framework.Logf(\"cleaning gce resource for %s\", lb) framework.CleanupServiceGCEResources(cs, lb, framework.TestContext.CloudConfig.Region, framework.TestContext.CloudConfig.Zone) </ins> }() ingressIP := framework.GetIngressPoint(&svc.Status.LoadBalancer.Ingress[0]) port := int(svc.Spec.Ports[0].Port)", "positive_passages": [{"docid": "doc-en-kubernetes-95b3abd37032c873ce8d7d9904ff018c8e3e7e0f9808f24d7c83d05cb3882c93", "text": "Our GKE scalability jobs (https://k8s-) are failing in the cluster teardown step (even though the e2e tests themselves passed). E.g failures: https://k8s- https://k8s- Seems like it's caused by some leaked network-related resources: /assign Krzysiek - Could you PTAL into this when you find time? It'll be great to have our GKE suite back to green. cc\nI think this is related to an earlier bug we've seen (similar one for GCE): Basically service-controller is creating some cloud resources (like firewalls) for lb-type services which are not brought down properly when the k8s cluster is brought down.\nAlso another related issue - There should also be an internal bug for this somewhere. IMO we may be able to fix this in test-infra (without waiting for proper long-term fix on gke side).\nI am adding clean-up method. This way all of the firewall rules will be cleaned up after tests. If this method has to remove any firewall rule, the teardown phase will return exception. It's not a fix for the bug - it only allows us to easy isolate tests leaking firewall rules.\nTests: should have session affinity work for LoadBalancer service with ESIPP on should be able to switch session affinity for LoadBalancer service with ESIPP on should have session affinity work for LoadBalancer service with ESIPP off should be able to switch session affinity for LoadBalancer service with ESIPP off leak resources related to the LoadBalancer. PR will fix this.", "commid": "kubernetes_issue_63026", "tokennum": 352}], "negative_passages": []}
{"query_id": "q-en-kubernetes-87c306b425bc125bf871a09365c98051645696b3c7f30df0d761489cc308589c", "query": "} } <ins> func TestCertSatisfiesTemplate(t *testing.T) { testCases := []struct { name          string cert          *x509.Certificate template      *x509.CertificateRequest shouldSatisfy bool }{ { name:          \"No certificate, no template\", cert:          nil, template:      nil, shouldSatisfy: false, }, { name:          \"No certificate\", cert:          nil, template:      &x509.CertificateRequest{}, shouldSatisfy: false, }, { name: \"No template\", cert: &x509.Certificate{ Subject: pkix.Name{ CommonName: \"system:node:fake-node-name\", }, }, template:      nil, shouldSatisfy: true, }, { name: \"Mismatched common name\", cert: &x509.Certificate{ Subject: pkix.Name{ CommonName: \"system:node:fake-node-name-2\", }, }, template: &x509.CertificateRequest{ Subject: pkix.Name{ CommonName: \"system:node:fake-node-name\", }, }, shouldSatisfy: false, }, { name: \"Missing orgs in certificate\", cert: &x509.Certificate{ Subject: pkix.Name{ Organization: []string{\"system:nodes\"}, }, }, template: &x509.CertificateRequest{ Subject: pkix.Name{ Organization: []string{\"system:nodes\", \"foobar\"}, }, }, shouldSatisfy: false, }, { name: \"Extra orgs in certificate\", cert: &x509.Certificate{ Subject: pkix.Name{ Organization: []string{\"system:nodes\", \"foobar\"}, }, }, template: &x509.CertificateRequest{ Subject: pkix.Name{ Organization: []string{\"system:nodes\"}, }, }, shouldSatisfy: true, }, { name: \"Missing DNS names in certificate\", cert: &x509.Certificate{ Subject:  pkix.Name{}, DNSNames: []string{\"foo.example.com\"}, }, template: &x509.CertificateRequest{ Subject:  pkix.Name{}, DNSNames: []string{\"foo.example.com\", \"bar.example.com\"}, }, shouldSatisfy: false, }, { name: \"Extra DNS names in certificate\", cert: &x509.Certificate{ Subject:  pkix.Name{}, DNSNames: []string{\"foo.example.com\", \"bar.example.com\"}, }, template: &x509.CertificateRequest{ Subject:  pkix.Name{}, DNSNames: []string{\"foo.example.com\"}, }, shouldSatisfy: true, }, { name: \"Missing IP addresses in certificate\", cert: &x509.Certificate{ Subject:     pkix.Name{}, IPAddresses: []net.IP{net.ParseIP(\"192.168.1.1\")}, }, template: &x509.CertificateRequest{ Subject:     pkix.Name{}, IPAddresses: []net.IP{net.ParseIP(\"192.168.1.1\"), net.ParseIP(\"192.168.1.2\")}, }, shouldSatisfy: false, }, { name: \"Extra IP addresses in certificate\", cert: &x509.Certificate{ Subject:     pkix.Name{}, IPAddresses: []net.IP{net.ParseIP(\"192.168.1.1\"), net.ParseIP(\"192.168.1.2\")}, }, template: &x509.CertificateRequest{ Subject:     pkix.Name{}, IPAddresses: []net.IP{net.ParseIP(\"192.168.1.1\")}, }, shouldSatisfy: true, }, { name: \"Matching certificate\", cert: &x509.Certificate{ Subject: pkix.Name{ CommonName:   \"system:node:fake-node-name\", Organization: []string{\"system:nodes\"}, }, DNSNames:    []string{\"foo.example.com\"}, IPAddresses: []net.IP{net.ParseIP(\"192.168.1.1\")}, }, template: &x509.CertificateRequest{ Subject: pkix.Name{ CommonName:   \"system:node:fake-node-name\", Organization: []string{\"system:nodes\"}, }, DNSNames:    []string{\"foo.example.com\"}, IPAddresses: []net.IP{net.ParseIP(\"192.168.1.1\")}, }, shouldSatisfy: true, }, } for _, tc := range testCases { t.Run(tc.name, func(t *testing.T) { var tlsCert *tls.Certificate if tc.cert != nil { tlsCert = &tls.Certificate{ Leaf: tc.cert, } } m := manager{ cert:        tlsCert, getTemplate: func() *x509.CertificateRequest { return tc.template }, } result := m.certSatisfiesTemplate() if result != tc.shouldSatisfy { t.Errorf(\"cert: %+v, template: %+v, certSatisfiesTemplate returned %v, want %v\", m.cert, tc.template, result, tc.shouldSatisfy) } }) } } </ins> func TestRotateCertCreateCSRError(t *testing.T) { now := time.Now() m := manager{", "positive_passages": [{"docid": "doc-en-kubernetes-8be37f8ebf3b929ba13e3d88ac8f62b2b24f9ed008212f39c0aaa7e2ec850c18", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: I'm testing the new option in kubernetes 1.12 and it seems that kubelet always requests the signing of a new CSR and tries to rotate the certificates when it is started. This is happening even though there's a valid (brand new) certificate on disk issued by kube-controller-manager. From what I can tell, this is happening because kubelet implements and is set after a successful certificate rotation, but is never persisted to disk. If kubelet is restarted, then the last requested CSR is nil. What you expected to happen: Ideally, kubelet should only request the signing of a new CSR if it doesn't already have a serving certificate or it's about to expire. How to reproduce it (as minimally and precisely as possible): Restart a kubelet instance that had it's serving certificate issued by kube-controller-manager Check and see that it requested the signing of a new CSR Anything else we need to know?: kubelet is being run with . , , and are all omitted to use the default values. The TLS bootstrapping for client certificates is currently not being used--just the bootstrapping for serving certificates. Environment: Kubernetes version: v1.12.0 - built from source at the tag () Cloud provider or hardware configuration: Bare metal OS: CentOS 7.5.1804 Kernel: Install tools: Custom RPMs built from this git repo with no additional patches Others:\n/sig node\n/sig auth\nNot sure if this is the ideal fix, but I've patched it so that it compares the current CSR template to the last requested template only if it doesn't already match the current cert.\ncc\nthanks for the proposed fix. I think it looks good. Could you send a PR? We should also remove entirely and only look at current cert and template. does that sound reasonable?\nSure thing, I'd be happy to do that. EDIT: I will submit a PR after approval from my employer.\nI think that's probably ok, as long as it checks everything we include in the template and we consider a certificate missing anything we request to be cause for re-requesting another cert (an issuer couldn't choose to issue a cert that drops some SANs and us not request another cert) left some comments in\nThis regression is a frequent flyer.", "commid": "kubernetes_issue_69471", "tokennum": 523}], "negative_passages": []}
{"query_id": "q-en-kubernetes-87c306b425bc125bf871a09365c98051645696b3c7f30df0d761489cc308589c", "query": "} } <ins> func TestCertSatisfiesTemplate(t *testing.T) { testCases := []struct { name          string cert          *x509.Certificate template      *x509.CertificateRequest shouldSatisfy bool }{ { name:          \"No certificate, no template\", cert:          nil, template:      nil, shouldSatisfy: false, }, { name:          \"No certificate\", cert:          nil, template:      &x509.CertificateRequest{}, shouldSatisfy: false, }, { name: \"No template\", cert: &x509.Certificate{ Subject: pkix.Name{ CommonName: \"system:node:fake-node-name\", }, }, template:      nil, shouldSatisfy: true, }, { name: \"Mismatched common name\", cert: &x509.Certificate{ Subject: pkix.Name{ CommonName: \"system:node:fake-node-name-2\", }, }, template: &x509.CertificateRequest{ Subject: pkix.Name{ CommonName: \"system:node:fake-node-name\", }, }, shouldSatisfy: false, }, { name: \"Missing orgs in certificate\", cert: &x509.Certificate{ Subject: pkix.Name{ Organization: []string{\"system:nodes\"}, }, }, template: &x509.CertificateRequest{ Subject: pkix.Name{ Organization: []string{\"system:nodes\", \"foobar\"}, }, }, shouldSatisfy: false, }, { name: \"Extra orgs in certificate\", cert: &x509.Certificate{ Subject: pkix.Name{ Organization: []string{\"system:nodes\", \"foobar\"}, }, }, template: &x509.CertificateRequest{ Subject: pkix.Name{ Organization: []string{\"system:nodes\"}, }, }, shouldSatisfy: true, }, { name: \"Missing DNS names in certificate\", cert: &x509.Certificate{ Subject:  pkix.Name{}, DNSNames: []string{\"foo.example.com\"}, }, template: &x509.CertificateRequest{ Subject:  pkix.Name{}, DNSNames: []string{\"foo.example.com\", \"bar.example.com\"}, }, shouldSatisfy: false, }, { name: \"Extra DNS names in certificate\", cert: &x509.Certificate{ Subject:  pkix.Name{}, DNSNames: []string{\"foo.example.com\", \"bar.example.com\"}, }, template: &x509.CertificateRequest{ Subject:  pkix.Name{}, DNSNames: []string{\"foo.example.com\"}, }, shouldSatisfy: true, }, { name: \"Missing IP addresses in certificate\", cert: &x509.Certificate{ Subject:     pkix.Name{}, IPAddresses: []net.IP{net.ParseIP(\"192.168.1.1\")}, }, template: &x509.CertificateRequest{ Subject:     pkix.Name{}, IPAddresses: []net.IP{net.ParseIP(\"192.168.1.1\"), net.ParseIP(\"192.168.1.2\")}, }, shouldSatisfy: false, }, { name: \"Extra IP addresses in certificate\", cert: &x509.Certificate{ Subject:     pkix.Name{}, IPAddresses: []net.IP{net.ParseIP(\"192.168.1.1\"), net.ParseIP(\"192.168.1.2\")}, }, template: &x509.CertificateRequest{ Subject:     pkix.Name{}, IPAddresses: []net.IP{net.ParseIP(\"192.168.1.1\")}, }, shouldSatisfy: true, }, { name: \"Matching certificate\", cert: &x509.Certificate{ Subject: pkix.Name{ CommonName:   \"system:node:fake-node-name\", Organization: []string{\"system:nodes\"}, }, DNSNames:    []string{\"foo.example.com\"}, IPAddresses: []net.IP{net.ParseIP(\"192.168.1.1\")}, }, template: &x509.CertificateRequest{ Subject: pkix.Name{ CommonName:   \"system:node:fake-node-name\", Organization: []string{\"system:nodes\"}, }, DNSNames:    []string{\"foo.example.com\"}, IPAddresses: []net.IP{net.ParseIP(\"192.168.1.1\")}, }, shouldSatisfy: true, }, } for _, tc := range testCases { t.Run(tc.name, func(t *testing.T) { var tlsCert *tls.Certificate if tc.cert != nil { tlsCert = &tls.Certificate{ Leaf: tc.cert, } } m := manager{ cert:        tlsCert, getTemplate: func() *x509.CertificateRequest { return tc.template }, } result := m.certSatisfiesTemplate() if result != tc.shouldSatisfy { t.Errorf(\"cert: %+v, template: %+v, certSatisfiesTemplate returned %v, want %v\", m.cert, tc.template, result, tc.shouldSatisfy) } }) } } </ins> func TestRotateCertCreateCSRError(t *testing.T) { now := time.Now() m := manager{", "positive_passages": [{"docid": "doc-en-kubernetes-1b55ad000b296f12b046608a2d187d8503e900f5b67dbcaa87fc7ef8e9366d19", "text": "I'd love to see an integration test that would catch this (but that shouldn't block a fix).\nThanks for the comments! Now that I have the CLA signed, I'll address those and submit a PR.\nJust submitted the PR:", "commid": "kubernetes_issue_69471", "tokennum": 53}], "negative_passages": []}
{"query_id": "q-en-kubernetes-88183a9c9cc2e64a1f6a35fade43de26e30978106f8384ec7d0445680db2acfa", "query": "var cpuFractionMap = make(map[string]float64) var memFractionMap = make(map[string]float64) <ins> // For each node, stores its pods info nodeNameToPodList := podListForEachNode(cs) </ins> for _, node := range nodes { <del> cpuFraction, memFraction, _, _ := computeCPUMemFraction(cs, node, requestedResource) </del> <ins> cpuFraction, memFraction, _, _ := computeCPUMemFraction(node, requestedResource, nodeNameToPodList[node.Name]) </ins> cpuFractionMap[node.Name] = cpuFraction memFractionMap[node.Name] = memFraction if cpuFraction > maxCPUFraction {", "positive_passages": [{"docid": "doc-en-kubernetes-68f56cf00eaca7b36f313a8fbb47f02ec3096dc918e863d7bad5040791bff0ba", "text": "From After , Multi-AZ Clusters tests in 1.19 and 1.20 started timing out as createBalancedPodForNodes is extremely inefficient in scale: for each node (out of 5k), it lists all pods in a cluster serially (each list takes ~5s), which translates to ~7 hours. Optimizing this function by listing pods once and then in memory by Spec.NodeName /kind bug /priority critical-urgent /sig scheduling\n/triage accepted\n/assign\n/reopen Looks that ComputeCPUMemFraction took only 12 minutes, but it stuck later, on It is scheduling one pod per each node: Which is waiting 5s to be ready: 5k nodes * 5s = ~7h\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign Can you do the pod creations in parallel?\nYes, good idea. I'll update to do that", "commid": "kubernetes_issue_100705", "tokennum": 227}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8835cb86de7b2830ad47740edbe064640ba6539238589dc83be01c6e34c91698", "query": "#     sleep 4 #     i=$[$i+1] #   done <del> apiVersion: v1beta1 </del> <ins> apiVersion: v1beta3 </ins> kind: Pod <del> id: synthetic-logger-0.25lps-pod desiredState: manifest: version: v1beta1 id: synth-logger-0.25lps containers: - name: synth-lgr image: ubuntu:14.04 command: [\"bash\", \"-c\", \"i=\"0\"; while true; do echo -n \"`hostname`: $i: \"; date --rfc-3339 ns; sleep 4; i=$[$i+1]; done\"] labels: name: synth-logging-source </del> <ins> metadata: labels: name: synth-logging-source name: synthetic-logger-0.25lps-pod spec: containers: - args: - bash - -c - 'i=\"0\"; while true; do echo -n \"`hostname`: $i: \"; date --rfc-3339 ns; sleep 4; i=$[$i+1]; done' image: ubuntu:14.04 name: synth-lgr </ins> ``` The other YAML file [synthetic_10lps.yaml](synthetic_10lps.yaml) specifies a similar synthetic logger that emits 10 log messages every second. To run both synthetic loggers:", "positive_passages": [{"docid": "doc-en-kubernetes-bc75029de49571476e249812075ff7ffff85fb8014f5cfe5e32228962baa98b2", "text": "Hi , I followed the instructions in examples/logging-demo, and there was no \"external IP\" field for elasticsearch-logging or kibana-logging, as shown below: I start up my cluster via cluster/kube- Did I miss something or is it a bug? Thanks.\nCorrect. This demo does not create an ELB so there is no external IP address. Access is via service proxy at the master. Type: and you should see the URLs for Elasticsearch and Kibana.\nplease let us know whether: a. Satnam's comment resolves your issue b. the demo should be updated to prevent this misunderstanding c. the issue isn't resolved Thank you!\nYes, Satnam's comment resolve the issue. I updated the demo in .\nAwesome, thanks for sending the patch! We'll discuss there. Always fantastic to have docs updated regularly by folks trying them.", "commid": "kubernetes_issue_7818", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-88716c2d0fbf6aec0c8b57194ba6cebca563440aeb5ae06ccc776be19e871111", "query": "if m == nil { return &Timestamp{} } <ins> // truncate precision to microseconds to match JSON marshaling/unmarshaling truncatedNanoseconds := time.Duration(m.Time.Nanosecond()).Truncate(time.Microsecond) </ins> return &Timestamp{ Seconds: m.Time.Unix(), <del> Nanos:   int32(m.Time.Nanosecond()), </del> <ins> Nanos:   int32(truncatedNanoseconds), </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-56cd908854c413b8fe52b6acbb170713ddc1a064a7bd9d42b4a3ba81ae7efcaf", "text": "Found some error logs when sending series events to apiserver: seems the later eventTime differed from the first one in series events After investigation, I found the problem was in the marshal. MicroTime is supposed to work on microsecond level precision, but init with nanosecond level precision, in this case, generates microsecond level precision data and generates nanosecond level precision, so when unmarshalled, the new time is not considered the exactly same as the original time (they are different at nanosecond level) MicroTime marshal should work at same precision for json and proto, so unmarshal can generate the exactly same MicroTime result: This causes the series events won't be updated on api-server after created master <details</details<details</details<details</details<details</details<details</details\n/sig api-machinery\n/assign\nGood catch... we'd probably need to truncate to microseconds when marshaling and unmarshaling proto to ensure any already persisted data is fixed up when read. Something like this:\nThanks for advice, going to send a PR soon", "commid": "kubernetes_issue_111928", "tokennum": 247}], "negative_passages": []}
{"query_id": "q-en-kubernetes-88771ef3870a258503ddf7e2f96b3e7265871912b273f8994480d45143ab921c", "query": "func (plugin *flexVolumePlugin) getExecutable() string { parts := strings.Split(plugin.driverName, \"/\") execName := parts[len(parts)-1] <del> return path.Join(plugin.execPath, execName) </del> <ins> execPath := path.Join(plugin.execPath, execName) if runtime.GOOS == \"windows\" { execPath = volume.GetWindowsPath(execPath) } return execPath </ins> } // Name is part of the volume.VolumePlugin interface.", "positive_passages": [{"docid": "doc-en-kubernetes-295b16ebdca2097490863d761fa466b150fe770891272091eba588ee367ef882", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: I have tried FlexVolume on a Windows node, it does not work. I am now working on this feature now. Below is the FlexVolume initialization error What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.7.7 Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: /sig windows /assign\nDetailed steps about how to use flexvolume on Windows with this PR:\ncc:", "commid": "kubernetes_issue_56875", "tokennum": 183}], "negative_passages": []}
{"query_id": "q-en-kubernetes-887ea752de759c78914705d32b2a19f1fbd25076dc9b094b6c63b504a7bb8dff", "query": "if err := s.validate(); err != nil { return nil, err } <del> dockercfgContent, err := handleDockercfgContent(s.Username, s.Password, s.Email, s.Server) </del> <ins> dockercfgJsonContent, err := handleDockerCfgJsonContent(s.Username, s.Password, s.Email, s.Server) </ins> if err != nil { return nil, err } secret := &v1.Secret{} secret.Name = s.Name <del> secret.Type = v1.SecretTypeDockercfg </del> <ins> secret.Type = v1.SecretTypeDockerConfigJson </ins> secret.Data = map[string][]byte{} <del> secret.Data[v1.DockerConfigKey] = dockercfgContent </del> <ins> secret.Data[v1.DockerConfigJsonKey] = dockercfgJsonContent </ins> if s.AppendHash { h, err := hash.SecretHash(secret) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-4279a6f285666ec67ce8924ca9393c19176af7de5707dd42a5f4c239ba12ead2", "text": "/kind bug We're having trouble retrieving images from a private registry on DockerCloud. For nearly a year the following has worked flawlessly. Last Friday I pulled down the 1.9.0 CLI (via brew) and since then have not been able to access any image in a private registry on DockerCloud. I've tried this on 10+ brand new clusters created with kops v1.8.0. The Kubernetes cluster version have been 1.8.0, 1.8.4, 1.8.5 and 1.9.0 (which is not supported by kops yet) and all exhibit the same problem. We create the secret as such: And verify it using: Which yields: And create a test service with with these contents: The pod fails immediatly with: I've reviewed the 1.9.0 release notes and nothing jumps out as the root cause. For reference I've tried putting quotes around the value when creating the secret to no avail. I've also tried prefixing the value with , so the full value would read: also to no avail. Environment: Kubernetes version: Cloud provider and installation info: AWS cluster built with Kops 1.8.0, using (to isolate this issue) nearly the default settings for everything.\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI have same problem, and I \"solved\" it creating a docker-registry secret in an old kubernetes version and pasting it on new kubernetes\nI'm recently (I know it worked perfectly about last month) facing issues with as well. For me it ended in a similar manner saying: I was able to confirm, that this is a kubernetes CLI related issue and not end user. Based on and this I was able to create properly formatted auth information looking like this: . When encoding this one-liner using (MacOS workstation) and apply like this works fine and images can be pulled from private repository again.", "commid": "kubernetes_issue_57427", "tokennum": 466}], "negative_passages": []}
{"query_id": "q-en-kubernetes-887ea752de759c78914705d32b2a19f1fbd25076dc9b094b6c63b504a7bb8dff", "query": "if err := s.validate(); err != nil { return nil, err } <del> dockercfgContent, err := handleDockercfgContent(s.Username, s.Password, s.Email, s.Server) </del> <ins> dockercfgJsonContent, err := handleDockerCfgJsonContent(s.Username, s.Password, s.Email, s.Server) </ins> if err != nil { return nil, err } secret := &v1.Secret{} secret.Name = s.Name <del> secret.Type = v1.SecretTypeDockercfg </del> <ins> secret.Type = v1.SecretTypeDockerConfigJson </ins> secret.Data = map[string][]byte{} <del> secret.Data[v1.DockerConfigKey] = dockercfgContent </del> <ins> secret.Data[v1.DockerConfigJsonKey] = dockercfgJsonContent </ins> if s.AppendHash { h, err := hash.SecretHash(secret) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-784638a373a6d25c569537512411337ba05226e31cffa99d23b394dffb534564", "text": "However this breaks all automation and can't be considered as solution Confirmed working with kubectl 1.8.5 and server 1.8.4 (guess 1.7.9 as well)\nlooks like there's an extra \"auths\" element when adding the secret using 1.9 kubectl\nAdded in /assign\nMany thanks for the quick fix on this. Any idea when this might get rolled out? Also, it might be a good idea if this was to the known issue list for v1.9.0. It would have saved us a bunch of time trying to track down the root cause. Just trying to make sure no one else needs to do the same.\nlinking to the \"v1.9.0 known issues\" list\nack, asking Mehdy since he is the patch manager for v1.9 branch. Mehdy, any idea when we can ship 1.9.1 with this fix?\nworkarounds for folks until 1.9.1 is released: if you have a .dockerconfigjson for your private registry already, you can manually specify the type and data key (e.g. ) if you don't have a .dockerconfigjson file already, you can fix up the secret produced by manually: the type from to the data key from to the modified secret with\n1 will be released tomorrow\nI can confirm solution works, thanks so much!\nI am still having issues in 1.9.1. This worked in the 1.8.x branches: results in the following error:\nyou have to remove the gitlab-registry secret before you can apply an update... type is immutable, and the fix in 1.9.1 required changing the type of the secret", "commid": "kubernetes_issue_57427", "tokennum": 370}], "negative_passages": []}
{"query_id": "q-en-kubernetes-891256752de78dc4da8910f52912fc0d5e794913677ec30484cbc3641f9a2a1b", "query": "``` Note that we are still working on making all containerized the master components run smoothly in rkt. Before that we are not able to run the master node with rkt yet. <ins> [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/rkt/README.md?pixel)]() </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-5e2660950cda0f785263613d5dae344eb16f84b548bf3bbe07f6c94efec5b686", "text": "The \"service\" file in this document contains a trailing comma on the line ' \"name\": \"my-service\", ` and thus kubectl fails to parse it properly.", "commid": "kubernetes_issue_8938", "tokennum": 41}], "negative_passages": []}
{"query_id": "q-en-kubernetes-897669b991c62501896f51c892a088a243744e05ee365704b7f9c65b70ee0ec1", "query": "}) It(\"should schedule a pod w/ a RW PD, remove it, then schedule it on another host\", func() { <del> if testContext.Provider != \"gce\" && testContext.Provider != \"aws\" { </del> <ins> if !providerIs(\"gce\", \"aws\") { </ins> By(fmt.Sprintf(\"Skipping PD test, which is only supported for providers gce & aws (not %s)\", testContext.Provider)) return", "positive_passages": [{"docid": "doc-en-kubernetes-5702d542be386cac9e4333778515fd94620fcdb52c66d8dfc11487da78971dda", "text": "I noticed while running e2e tests locally that some tests were apparently being incorrectly skipped: I checked, and this is also true for our Jenkins runs. Currently it looks like and have this bug, though only the former actually skips the test, I think. The issue appears to be that the code inside the top-level in these files is being run before the testContext struct is filled out (and before is even called), and so testContext.Provider is empty. I'm not immediately sure what the proper fix is; I'm also worried that there might be other things broken by the fact that these blocks are called before initialization is complete. We also probably investigate if there is a better way to mark these tests as skipped; right now, there's no indication in the test report (, Jenkins test report, etc) that these tests were skipped.\nI merged and which tried to disable these tests for non-{gke,gce} but apparently didn't follow-up and verify that they were still running on our platforms. /cc\nSeems easy enough to fix. I'll have a PR out to fix this before Monday.", "commid": "kubernetes_issue_7008", "tokennum": 242}], "negative_passages": []}
{"query_id": "q-en-kubernetes-89b69b2b4a0c0fd5280b357025f1541bdeb31bd53485ff1ea5e0606ecb6929d6", "query": "Contexts: map[string]clientcmdapi.Context{ \"gothic-context\": {AuthInfo: \"blue-user\", Cluster: \"chicken-cluster\", Namespace: \"plane-ns\"}}, } testConfigConflictAlfa = clientcmdapi.Config{ AuthInfos: map[string]clientcmdapi.AuthInfo{ \"red-user\":    {Token: \"a-different-red-token\"},", "positive_passages": [{"docid": "doc-en-kubernetes-dbcf83004ea3f0459daec6a4d94a4bece404fe8f97225f1a2fba429c343bf057", "text": "I've been pulling my hair out trying get kubectl talk to my local cluster. It seems that kubectl merges the local file with values pulled down from the cloud. I've done the following: The I just set is silently overridden. Questions: is this documented anywhere? should kubectl merge in my GCE cluster when I set my cloud-provider to something else? should kubectl override my previously set current-context?\nworkaround is to use flag to override the config file value.\nbut not a good UX long term\nSomeone else hit this as well: . Better fix is to have the local-up script set a context, which I will try to add today. As for the overwriting behavior, it's documented in , but based on what you describe, the intended load order is not working; local .kubeconfig should overwrite global. cc\nThat sounds infuriating. I'll take a look this morning.", "commid": "kubernetes_issue_4397", "tokennum": 210}], "negative_passages": []}
{"query_id": "q-en-kubernetes-89b903eb62fe0d6b39a16c729a937f57183139fe48a64307e20db765bf81dae1", "query": "cloud                 *Cloud } <del> // AttachDisk attaches a vhd to vm. The vhd must exist, can be identified by diskName, diskURI, and lun. func (c *controllerCommon) AttachDisk(isManagedDisk bool, diskName, diskURI string, nodeName types.NodeName, lun int32, cachingMode compute.CachingTypes) error { // 1. vmType is standard, attach with availabilitySet.AttachDisk. </del> <ins> // getNodeVMSet gets the VMSet interface based on config.VMType and the real virtual machine type. func (c *controllerCommon) getNodeVMSet(nodeName types.NodeName) (VMSet, error) { // 1. vmType is standard, return cloud.vmSet directly. </ins> if c.cloud.VMType == vmTypeStandard { <del> return c.cloud.vmSet.AttachDisk(isManagedDisk, diskName, diskURI, nodeName, lun, cachingMode) </del> <ins> return c.cloud.vmSet, nil </ins> } // 2. vmType is Virtual Machine Scale Set (vmss), convert vmSet to scaleSet. ss, ok := c.cloud.vmSet.(*scaleSet) if !ok { <del> return fmt.Errorf(\"error of converting vmSet (%q) to scaleSet with vmType %q\", c.cloud.vmSet, c.cloud.VMType) </del> <ins> return nil, fmt.Errorf(\"error of converting vmSet (%q) to scaleSet with vmType %q\", c.cloud.vmSet, c.cloud.VMType) </ins> } <del> // 3. If the node is managed by availability set, then attach with availabilitySet.AttachDisk. </del> <ins> // 3. If the node is managed by availability set, then return ss.availabilitySet. </ins> managedByAS, err := ss.isNodeManagedByAvailabilitySet(mapNodeNameToVMName(nodeName)) if err != nil { <del> return err </del> <ins> return nil, err </ins> } if managedByAS { // vm is managed by availability set. <del> return ss.availabilitySet.AttachDisk(isManagedDisk, diskName, diskURI, nodeName, lun, cachingMode) </del> <ins> return ss.availabilitySet, nil </ins> } <del> // 4. Node is managed by vmss, attach with scaleSet.AttachDisk. return ss.AttachDisk(isManagedDisk, diskName, diskURI, nodeName, lun, cachingMode) </del> <ins> // 4. Node is managed by vmss return ss, nil </ins> } <del> // DetachDiskByName detaches a vhd from host. The vhd can be identified by diskName or diskURI. func (c *controllerCommon) DetachDiskByName(diskName, diskURI string, nodeName types.NodeName) error { // 1. vmType is standard, detach with availabilitySet.DetachDiskByName. if c.cloud.VMType == vmTypeStandard { return c.cloud.vmSet.DetachDiskByName(diskName, diskURI, nodeName) </del> <ins> // AttachDisk attaches a vhd to vm. The vhd must exist, can be identified by diskName, diskURI, and lun. func (c *controllerCommon) AttachDisk(isManagedDisk bool, diskName, diskURI string, nodeName types.NodeName, lun int32, cachingMode compute.CachingTypes) error { vmset, err := c.getNodeVMSet(nodeName) if err != nil { return err </ins> } <del> // 2. vmType is Virtual Machine Scale Set (vmss), convert vmSet to scaleSet. ss, ok := c.cloud.vmSet.(*scaleSet) if !ok { return fmt.Errorf(\"error of converting vmSet (%q) to scaleSet with vmType %q\", c.cloud.vmSet, c.cloud.VMType) } </del> <ins> return vmset.AttachDisk(isManagedDisk, diskName, diskURI, nodeName, lun, cachingMode) } </ins> <del> // 3. If the node is managed by availability set, then detach with availabilitySet.DetachDiskByName. managedByAS, err := ss.isNodeManagedByAvailabilitySet(mapNodeNameToVMName(nodeName)) </del> <ins> // DetachDiskByName detaches a vhd from host. The vhd can be identified by diskName or diskURI. func (c *controllerCommon) DetachDiskByName(diskName, diskURI string, nodeName types.NodeName) error { vmset, err := c.getNodeVMSet(nodeName) </ins> if err != nil { return err } <del> if managedByAS { // vm is managed by availability set. return ss.availabilitySet.DetachDiskByName(diskName, diskURI, nodeName) } // 4. Node is managed by vmss, detach with scaleSet.DetachDiskByName. return ss.DetachDiskByName(diskName, diskURI, nodeName) </del> <ins> return vmset.DetachDiskByName(diskName, diskURI, nodeName) </ins> } <del> // GetDiskLun finds the lun on the host that the vhd is attached to, given a vhd's diskName and diskURI. func (c *controllerCommon) GetDiskLun(diskName, diskURI string, nodeName types.NodeName) (int32, error) { // 1. vmType is standard, get with availabilitySet.GetDiskLun. if c.cloud.VMType == vmTypeStandard { return c.cloud.vmSet.GetDiskLun(diskName, diskURI, nodeName) </del> <ins> // getNodeDataDisks invokes vmSet interfaces to get data disks for the node. func (c *controllerCommon) getNodeDataDisks(nodeName types.NodeName) ([]compute.DataDisk, error) { vmset, err := c.getNodeVMSet(nodeName) if err != nil { return nil, err </ins> } <del> // 2. vmType is Virtual Machine Scale Set (vmss), convert vmSet to scaleSet. ss, ok := c.cloud.vmSet.(*scaleSet) if !ok { return -1, fmt.Errorf(\"error of converting vmSet (%q) to scaleSet with vmType %q\", c.cloud.vmSet, c.cloud.VMType) } </del> <ins> return vmset.GetDataDisks(nodeName) } </ins> <del> // 3. If the node is managed by availability set, then get with availabilitySet.GetDiskLun. managedByAS, err := ss.isNodeManagedByAvailabilitySet(mapNodeNameToVMName(nodeName)) </del> <ins> // GetDiskLun finds the lun on the host that the vhd is attached to, given a vhd's diskName and diskURI. func (c *controllerCommon) GetDiskLun(diskName, diskURI string, nodeName types.NodeName) (int32, error) { disks, err := c.getNodeDataDisks(nodeName) </ins> if err != nil { <ins> glog.Errorf(\"error of getting data disks for node %q: %v\", nodeName, err) </ins> return -1, err } <del> if managedByAS { // vm is managed by availability set. return ss.availabilitySet.GetDiskLun(diskName, diskURI, nodeName) } // 4. Node is managed by vmss, get with scaleSet.GetDiskLun. return ss.GetDiskLun(diskName, diskURI, nodeName) </del> <ins> for _, disk := range disks { if disk.Lun != nil && (disk.Name != nil && diskName != \"\" && *disk.Name == diskName) || (disk.Vhd != nil && disk.Vhd.URI != nil && diskURI != \"\" && *disk.Vhd.URI == diskURI) || (disk.ManagedDisk != nil && *disk.ManagedDisk.ID == diskURI) { // found the disk glog.V(4).Infof(\"azureDisk - find disk: lun %d name %q uri %q\", *disk.Lun, diskName, diskURI) return *disk.Lun, nil } } return -1, fmt.Errorf(\"Cannot find Lun for disk %s\", diskName) </ins> } // GetNextDiskLun searches all vhd attachment on the host and find unused lun. Return -1 if all luns are used. func (c *controllerCommon) GetNextDiskLun(nodeName types.NodeName) (int32, error) { <del> // 1. vmType is standard, get with availabilitySet.GetNextDiskLun. if c.cloud.VMType == vmTypeStandard { return c.cloud.vmSet.GetNextDiskLun(nodeName) } // 2. vmType is Virtual Machine Scale Set (vmss), convert vmSet to scaleSet. ss, ok := c.cloud.vmSet.(*scaleSet) if !ok { return -1, fmt.Errorf(\"error of converting vmSet (%q) to scaleSet with vmType %q\", c.cloud.vmSet, c.cloud.VMType) } // 3. If the node is managed by availability set, then get with availabilitySet.GetNextDiskLun. managedByAS, err := ss.isNodeManagedByAvailabilitySet(mapNodeNameToVMName(nodeName)) </del> <ins> disks, err := c.getNodeDataDisks(nodeName) </ins> if err != nil { <ins> glog.Errorf(\"error of getting data disks for node %q: %v\", nodeName, err) </ins> return -1, err } <del> if managedByAS { // vm is managed by availability set. return ss.availabilitySet.GetNextDiskLun(nodeName) } // 4. Node is managed by vmss, get with scaleSet.GetNextDiskLun. return ss.GetNextDiskLun(nodeName) </del> <ins> used := make([]bool, maxLUN) for _, disk := range disks { if disk.Lun != nil { used[*disk.Lun] = true } } for k, v := range used { if !v { return int32(k), nil } } return -1, fmt.Errorf(\"all luns are used\") </ins> } // DisksAreAttached checks if a list of volumes are attached to the node with the specified NodeName. func (c *controllerCommon) DisksAreAttached(diskNames []string, nodeName types.NodeName) (map[string]bool, error) { <del> // 1. vmType is standard, check with availabilitySet.DisksAreAttached. if c.cloud.VMType == vmTypeStandard { return c.cloud.vmSet.DisksAreAttached(diskNames, nodeName) } // 2. vmType is Virtual Machine Scale Set (vmss), convert vmSet to scaleSet. ss, ok := c.cloud.vmSet.(*scaleSet) if !ok { return nil, fmt.Errorf(\"error of converting vmSet (%q) to scaleSet with vmType %q\", c.cloud.vmSet, c.cloud.VMType) </del> <ins> attached := make(map[string]bool) for _, diskName := range diskNames { attached[diskName] = false </ins> } <del> // 3. If the node is managed by availability set, then check with availabilitySet.DisksAreAttached. managedByAS, err := ss.isNodeManagedByAvailabilitySet(mapNodeNameToVMName(nodeName)) </del> <ins> disks, err := c.getNodeDataDisks(nodeName) </ins> if err != nil { <del> return nil, err </del> <ins> if err == cloudprovider.InstanceNotFound { // if host doesn't exist, no need to detach glog.Warningf(\"azureDisk - Cannot find node %q, DisksAreAttached will assume disks %v are not attached to it.\", nodeName, diskNames) return attached, nil } return attached, err </ins> } <del> if managedByAS { // vm is managed by availability set. return ss.availabilitySet.DisksAreAttached(diskNames, nodeName) </del> <ins> for _, disk := range disks { for _, diskName := range diskNames { if disk.Name != nil && diskName != \"\" && *disk.Name == diskName { attached[diskName] = true } } </ins> } <del> // 4. Node is managed by vmss, check with scaleSet.DisksAreAttached. return ss.DisksAreAttached(diskNames, nodeName) </del> <ins> return attached, nil </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-6cfc50824280daf2f66f5e84f9a8c720c316cfa724f1e90fa02f306c798e5010", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind cleanup What happened: VirtualMachineScaleSetVM and VirtualMachine are different data structures (because of different API versions), so the disk attach operation seems duplicate between vm and vmss. That means although disk operations are in same logic, some duplication are still required now. They should use same api version in the future and should be merged into same code base, e.g. move sharing logic to Refer What you expected to happen: vmss and vm disk operations should share same code logic. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\nI have checked with currently we can\u2019t merge, e.g. following two structs are different since they using different sdk-for-azure versions. While in the end when sdk-for-azure version is upgraded, above two versions should be same and at that time, we should merge functions like \u2018AttachDisk\u2019, \u2018DetachDiskByName\u2019, 'GetDiskLun', GetNextDiskLun, DisksAreAttached", "commid": "kubernetes_issue_59736", "tokennum": 313}], "negative_passages": []}
{"query_id": "q-en-kubernetes-89d4152a66acc472f732ca356d45eb558c97d42bffb6d96217c14f8c7bc29827", "query": "if err != nil { if apierrors.IsNotFound(err) { c.triggerTimeTracker.DeleteService(namespace, name) <ins> // The service has been deleted, return nil so that it won't be retried. return nil </ins> } return err }", "positive_passages": [{"docid": "doc-en-kubernetes-0786e42c64621bc4d095c4e71177424c568ccfa7fdb0651a37698d341e1aa584", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: This requires 1.16 alpha feature: Endpoint Slices being enabled. After deleting a , EndpointSliceController kept enqueuing the service after syncing it successfully, until its retry budget exceeded. And the logs are misleading by indicating something wrong happened while the cleanup has been executed successfully: What you expected to happen: The deletion should be triggered only once and there should be no warning and error logs if the cleanup is successfully. How to reproduce it (as minimally and precisely as possible): Endpoint Slices feature a then delete it. kube-controller-manager logs, there would be repeated logs. Anything else we need to know?: Environment: Kubernetes version (use ):Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\nThere are no sig labels on this issue. Please add a sig label by either: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. See the . The in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals. <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\n/assign\n/assign", "commid": "kubernetes_issue_82995", "tokennum": 384}], "negative_passages": []}
{"query_id": "q-en-kubernetes-89dc010d6ac8766c568d5e5936b339ceeec510a0c0082a23242eede031c6ff4b", "query": "\"sort\" \"strconv\" \"strings\" <ins> \"sync\" </ins> \"testing\" \"github.com/vmware/govmomi/find\"", "positive_passages": [{"docid": "doc-en-kubernetes-59b9ae5b52e0b40199c236ff5490b403bebb933bd0751cd293a630848c9a0b07", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: What you expected to happen: No data races How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\nfor the record as we tend to lose the logs in the gcs bucket\n/sig instrumentation", "commid": "kubernetes_issue_98941", "tokennum": 247}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8a08a7221b814f5400af87e04be96461d5bb455376aabc62c6f0051d41a1062e", "query": "for _, file := range files { fileName := file.Name() // Make a copy It(fmt.Sprintf(\"tests that %v passes\", fileName), func() { <ins> // A number of scripts only work on gce if !providerIs(\"gce\", \"gke\") { By(fmt.Sprintf(\"Skipping Shell test %s, which is only supported for provider gce and gke (not %s)\", fileName, testContext.Provider)) return } </ins> runCmdTest(filepath.Join(bashE2ERoot, fileName)) }) }", "positive_passages": [{"docid": "doc-en-kubernetes-5702d542be386cac9e4333778515fd94620fcdb52c66d8dfc11487da78971dda", "text": "I noticed while running e2e tests locally that some tests were apparently being incorrectly skipped: I checked, and this is also true for our Jenkins runs. Currently it looks like and have this bug, though only the former actually skips the test, I think. The issue appears to be that the code inside the top-level in these files is being run before the testContext struct is filled out (and before is even called), and so testContext.Provider is empty. I'm not immediately sure what the proper fix is; I'm also worried that there might be other things broken by the fact that these blocks are called before initialization is complete. We also probably investigate if there is a better way to mark these tests as skipped; right now, there's no indication in the test report (, Jenkins test report, etc) that these tests were skipped.\nI merged and which tried to disable these tests for non-{gke,gce} but apparently didn't follow-up and verify that they were still running on our platforms. /cc\nSeems easy enough to fix. I'll have a PR out to fix this before Monday.", "commid": "kubernetes_issue_7008", "tokennum": 242}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8a24aee8beb1a8d4ac362630e22675b2fb661e88c86b5a009e165fa86c1ee62a", "query": "WhenScaled:  apps.DeletePersistentVolumeClaimRetentionPolicyType, WhenDeleted: apps.DeletePersistentVolumeClaimRetentionPolicyType, }, <ins> // tests the case when no policy is set. nil, </ins> } { subtestName := pvcDeletePolicyString(policy) + \"/StatefulSetAutoDeletePVCEnabled\" if testName != \"\" {", "positive_passages": [{"docid": "doc-en-kubernetes-0282c95c8ddc11607ba516e065f4121126017f786957d03a031978171c244a62", "text": "The replicas is 3 but just create 1 pod 'web-0' and one pvc, then kube-controller-manager panic happend. Should create 3 pod and 3 pvc add '--feature-gates=StatefulSetAutoDeletePVC=true' arg for kube-controller-manager, then create statefulset with 2 replicas and volumeClaimTemplates. No response <details</details<details</details<details</details<details</details<details</details<details</details\n/sig apps\nI can reproduce the issue and want to fix it. It seems like variables cause . /assign\n/triage accepted\nGreat find! Does this only happen on an upgraded cluster? I'll spin up a cluster and see if the e2e test catches this problem.\nThe e2e tests are still passing on a 1.24 cluster, so I suspect this is an upgrade problem. I wonder if there are other holes here.\nI installed the Kubernetes 1.25 cluster directly using and still reproduced this issue, so it was probably not caused by upgrading the cluster.\nInteresting. I thought that would set the policy to be non-nil. Let's keep this bug open after you submit your PR as I think something else is going on here---I don't think we should be seeing the null policy in the first place.\nI suspect that somewhere accidentally set it to nil, and I'll keep looking at this code.\nI tried the following (and also with parallel pod management), and it didn't seem to cause the panic. This was a 1.24 cluster, maybe this is only happening on head versions?\nI just tried this on a kind cluster running on k8s head, and the problem didn't seem to reproduce. But this was setting the feature flag default in I wonder----does the api server need to have the feature gate as well? That would explain why defaulting wasn't happening.\nAs far as I'm concerned,I just set the in kube-controller-manager manifests to reproduce this issue. I repeat the yaml used as follows: I tested that in statefulset yaml, setting or not would cause the component to panic. The panic logs are the same as above, so ignore them here.", "commid": "kubernetes_issue_113319", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8a24aee8beb1a8d4ac362630e22675b2fb661e88c86b5a009e165fa86c1ee62a", "query": "WhenScaled:  apps.DeletePersistentVolumeClaimRetentionPolicyType, WhenDeleted: apps.DeletePersistentVolumeClaimRetentionPolicyType, }, <ins> // tests the case when no policy is set. nil, </ins> } { subtestName := pvcDeletePolicyString(policy) + \"/StatefulSetAutoDeletePVCEnabled\" if testName != \"\" {", "positive_passages": [{"docid": "doc-en-kubernetes-bacc559e7a05833801486ab81cebdf65b8969406a4ba99bead3e0d4a0613defb", "text": "statefulset with : The environment\nI believe you---this doesn't seem to be well-documented, but it's my understanding that you need to set the feature gate on all of the system components. Obviously failing to do so shouldn't cause a panic, so thank you again for finding & fixing this bug! Let me ask around to see what the expected behavior is. I know there may be skew between kubelets and master versions, but I didn't expect to have to deal with skew between master components.\nI read the code, and now I understand what you mean. This feature gate must be enabled in both the and components. We need to describe it in the to prevent someone from ignoring the component, which also needs to enable the feature gate.\nI don't think we need all the system components, like the component, right? I read the original KEP documentation. This feature gate only involves components and :\nI had a bit of discussion about this with others. Because upgrades don't occur atomically, any feature gate has to work regardless of how the other system components are configured (things shouldn't panic!). I suppose if the cluster administrator wants to track what needs to be enabled on each feature they can try to sequence which component has which feature gate. If it were me I'd try to make all the components consistent though.\nThis is certainly a method, but it is a bit more cumbersome for the administrator. It is best to have a place for the document to be queried by the administrator and avoid confusion. I don't think everyone is very familiar with the k8s mechanism. I suggest adding a partial description to this section of the : Before: After: I can submit this PR on .\nThis is going to be true of any api change. When you tried to use it with only adding the controller manager feature gate, I think you would be able to set the retain policy, but there wouldn't be any defaulting or validation (?).\nI've seen other feature gates that say what components are needed to enable it to use the new feature. For example: If it's not necessary, then I close .\nonly adding the controller manager feature gate, I think you would be able to set the retain policy, but there wouldn't be any defaulting or validation (?). I remember just enabling it in kube-controller-manager.", "commid": "kubernetes_issue_113319", "tokennum": 500}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8a24aee8beb1a8d4ac362630e22675b2fb661e88c86b5a009e165fa86c1ee62a", "query": "WhenScaled:  apps.DeletePersistentVolumeClaimRetentionPolicyType, WhenDeleted: apps.DeletePersistentVolumeClaimRetentionPolicyType, }, <ins> // tests the case when no policy is set. nil, </ins> } { subtestName := pvcDeletePolicyString(policy) + \"/StatefulSetAutoDeletePVCEnabled\" if testName != \"\" {", "positive_passages": [{"docid": "doc-en-kubernetes-dc6539ce5e1daf74890724a45ab3f8f9d1791d28b0765a687405f604711fc05a", "text": "it using the retain policy, but the statefulset does not have the policy from output of (It should be the apiserver authentication forbids it)\nYeah I think that makes sense. Thanks for finding this issue! After your PR with the panic fix is submitted, I think we can close this?\nYes. I agree. /close\nClosing this issue. <detailsIn response to : Yes. I agree. 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", "commid": "kubernetes_issue_113319", "tokennum": 117}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8a75104517f024130b1511e58ed3ee381b976144e44c56d3812622fc4fcfe861", "query": "FindBoundSatsified:   true, }, eventReason: \"FailedScheduling\", <del> expectError: makePredicateError(\"1 VolumeBindingNoMatch\"), </del> <ins> expectError: makePredicateError(\"1 node(s) didn't find available persistent volumes to bind\"), </ins> }, \"bound-and-unbound-unsatisfied\": { volumeBinderConfig: &persistentvolume.FakeVolumeBinderConfig{", "positive_passages": [{"docid": "doc-en-kubernetes-10c13016eb5239afc7a330cfdab91dbf78232a49f2993f71669df735dbb939e1", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature The is not user friendly. There has been to make it better, but we still print in the pending message. We should change these errors to a more human readable message. For example, should be changed to something like . /sig scheduling", "commid": "kubernetes_issue_58546", "tokennum": 91}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8a847e2cea909eaaab7638c220b89fbc1ea74bdd65321ba50dad97a86f61471b", "query": "ginkgo.By(\"Waiting for container to stop restarting\") stableCount := int(0) stableThreshold := int(time.Minute / framework.Poll) <del> err = wait.PollImmediate(framework.Poll, 2*time.Minute, func() (bool, error) { </del> <ins> err = wait.PollImmediate(framework.Poll, framework.PodStartTimeout, func() (bool, error) { </ins> pod, err := f.ClientSet.CoreV1().Pods(f.Namespace.Name).Get(context.TODO(), pod.Name, metav1.GetOptions{}) if err != nil { return false, err", "positive_passages": [{"docid": "doc-en-kubernetes-d581fd23524a17c2e094f8c22d9237840c9557b1634d31d91db6cf64598bf32e", "text": "<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI --ci-kubernetes-e2e-ubuntu-gce [sig-storage] Subpath Container restart should verify that container can restart successfully after configmaps modified links to appreciated links to specific failures in spyglass appreciated Triage shows that this has been flaking quite frequently: It has flaked in 5 of the last 10 runs: /sig storage /priority important-soon <!-- Please see the deflaking doc () for more guidance! --\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nNoticed some more flakes on this one\nYep, looks like this is still flaking quite frequently: Going to re-ping SIG Storage.\n/assign\nTest is flaking maybe half of the time. ~This test is failing in gce-ubuntu-master-default - not sure if it's failing in any other dashboards, nor whether this is run anywhere else.~ edit: This is failing on Ubuntu only. Not sure if this is limited to master branch. Fix to the original issue was in since 1.19. This is a subpath test which a configmap a container that mounts the configmap a liveness probe and waits for the container to restart. liveness probe and waits for the container to stop restarting. The test failed at the last step - the container never stopped restarting. Timeout is 2min. The liveness probe continuously checks whether a \"probeFile\" exists in (an emptyDir), and if it doesn't exist, whether the configmap file contains the modified value. The probeFile essentially acts as a condition which guards the probe from checking the configmap file. The test fails the liveness probe by removing the probeFile without updating the configmap just yet. It then fixes the liveness probe by updating the configmap to the modified value.", "commid": "kubernetes_issue_100194", "tokennum": 522}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8a847e2cea909eaaab7638c220b89fbc1ea74bdd65321ba50dad97a86f61471b", "query": "ginkgo.By(\"Waiting for container to stop restarting\") stableCount := int(0) stableThreshold := int(time.Minute / framework.Poll) <del> err = wait.PollImmediate(framework.Poll, 2*time.Minute, func() (bool, error) { </del> <ins> err = wait.PollImmediate(framework.Poll, framework.PodStartTimeout, func() (bool, error) { </ins> pod, err := f.ClientSet.CoreV1().Pods(f.Namespace.Name).Get(context.TODO(), pod.Name, metav1.GetOptions{}) if err != nil { return false, err", "positive_passages": [{"docid": "doc-en-kubernetes-fe4ad65b6af4a4370d93bc829526a20d829ebc4486fe6305d4213476a53bb63c", "text": "So if the container keeps restarting, the liveness probe could've been failing continuously within 2min, due to one of the following: (? not sure about this one) Command can't be executed (for example if container can't start) configmap file was never updated. Within 2min, the pod only restarted 5 times. The liveness probe's period is 2s, initial delay is 1s, and failure threshold is 1, so a restart due to liveness probe failure is triggered every 3s. The image is busybox. The command is just , so it's unlikely for the container to have crashed. There were no liveness probe unhealthy events after the test fixes the probe, and yet it continued to restart. No more events after probe is fixed.\nCould we check if the configmap value was updated for sure to rule out that scenario ? I have not tried to run an end to end test locally :) so am not sure how to debug it\nWill do! I ran the test in a GKE Ubuntu cluster running 1.19.6 and couldn't reproduce the failure. I'm now trying to run a cluster on GCE with Ubuntu nodes running k8s master, but haven't been successful after trying a number of techniques. If anyone happens to know how to do this let me know; I'll keep asking around otherwise.\nI got a repro on a GKE cluster backed by COS. After the test failed the container ends up in Running state eventually, and the configmap file outputs the expected modified value. The fix is to increase the test timeout. PR coming up.", "commid": "kubernetes_issue_100194", "tokennum": 355}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8ab764be11aaaa9d4a3094e05c9736abb48eee1f9fdef6bb0be64fcb7e5b11a7", "query": "It(\"should lookup the Schema by its GroupVersionKind\", func() { schema = resources.LookupResource(gvk) Expect(schema).ToNot(BeNil()) <del> }) var sarspec *proto.Kind It(\"should be a Kind and have a spec\", func() { </del> sar := schema.(*proto.Kind) Expect(sar).ToNot(BeNil()) Expect(sar.Fields).To(HaveKey(\"spec\")) specRef := sar.Fields[\"spec\"].(proto.Reference) Expect(specRef).ToNot(BeNil()) Expect(specRef.Reference()).To(Equal(\"io.k8s.api.authorization.v1.SubjectAccessReviewSpec\")) <del> sarspec = specRef.SubSchema().(*proto.Kind) Expect(sarspec).ToNot(BeNil()) </del> <ins> Expect(specRef.SubSchema().(*proto.Kind)).ToNot(BeNil()) </ins> }) })", "positive_passages": [{"docid": "doc-en-kubernetes-828b2f2bc9a1c73b1b130d20e1091ab566168df681bda6f542cc66f3f230828b", "text": "/kind failing-test <!-- If this is a flake, please add: /kind flake --<!-- Please assign a SIG using: /sig SIG-NAME --\n/sig cli\nThere may have two issues to fix: doesn't support run with assertion must check whether schema is nil first\n/assign\n/triage accepted", "commid": "kubernetes_issue_106761", "tokennum": 80}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8ac8a8253b6c65a48168eec0fa70d40419b9d34f3feb615741c19bb03c6e685f", "query": "kubetypes.HTTPSource, &api.Pod{ ObjectMeta: api.ObjectMeta{ <del> UID:       \"111\", Name:      \"foo\" + \"-\" + hostname, Namespace: \"mynamespace\", SelfLink: getSelfLink(\"foo-\"+hostname, \"mynamespace\"), </del> <ins> UID:         \"111\", Name:        \"foo\" + \"-\" + hostname, Namespace:   \"mynamespace\", Annotations: map[string]string{kubetypes.ConfigHashAnnotationKey: \"111\"}, SelfLink:    getSelfLink(\"foo-\"+hostname, \"mynamespace\"), </ins> }, Spec: api.PodSpec{ NodeName:                      hostname,", "positive_passages": [{"docid": "doc-en-kubernetes-8bc8d69d49aedfb4a9bf3991de80f7c339e96bfbefe5b1f250dae70fa0393729", "text": "See for more context. Currently, kubelet compares the spec of a mirror pod (created via apiserver) with that of a static pod (config stored as a file) to decide whether the two are considered identical. If they differ, kubelet would delete the mirror pod and re-create it with the correct spec. Due to the fact that apiserver may set default values for some fields in the spec of the mirror pod, the specs could deviate undesirably. To avoid problems like this, we can store the config of a static pod as an annotation in the mirror pod, and compare the static pod with the annotation.\nWould a hash of the config be sufficient if we're only going to compare? The whole spec would generally be more useful, but I wonder if that is too much data to put in an annotation.\nThis seems totally reasonable to me, but I'm still desperately curious why you can't just bypass defaulting when you generate mirror pod from static pod? (i.e. just use the static pod's configuration verbatim)\nIt's not kubelet who applies the default values here. The admission plugin was only run at the apiserver, and to bypass that, you have to ask apiserver to treat mirror pods differently and potentially at multiple places.\nOn May 22, 2015 10:38 AM, \"Yu-Ju Hong\" wrote: Understood, but is it really multiple places? If so then I agree it's a bad idea. Otherwise it might be worth considering as an alternative.\nIt's untenable for Kubelet to assume to know/circumvent all fields that will be set by other entities: admission control, defaulting, late initialization, auto-something, whatever. It needs to obey the same rules as other clients.\nI don't understand why you would ever want to apply any of the things you mentioned to static pods. Static pods should be copied verbatim into the mirror pods, right? That's what I'm proposing.\nWhat if the master is updated before the kubelet, and the master adds a new API field with a default value?\nThat case should be discussed in\nI agree that mirror pod should reflect the true status of the static pod running on the node, and no default values should be set in this case.", "commid": "kubernetes_issue_8683", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8ac8a8253b6c65a48168eec0fa70d40419b9d34f3feb615741c19bb03c6e685f", "query": "kubetypes.HTTPSource, &api.Pod{ ObjectMeta: api.ObjectMeta{ <del> UID:       \"111\", Name:      \"foo\" + \"-\" + hostname, Namespace: \"mynamespace\", SelfLink: getSelfLink(\"foo-\"+hostname, \"mynamespace\"), </del> <ins> UID:         \"111\", Name:        \"foo\" + \"-\" + hostname, Namespace:   \"mynamespace\", Annotations: map[string]string{kubetypes.ConfigHashAnnotationKey: \"111\"}, SelfLink:    getSelfLink(\"foo-\"+hostname, \"mynamespace\"), </ins> }, Spec: api.PodSpec{ NodeName:                      hostname,", "positive_passages": [{"docid": "doc-en-kubernetes-0491e123884f0f20f50d0a788bca7a6a29e2fa08227703a00221ecbd3bcf483c", "text": "However, I think it'd be harder to implement this way since, as stated above, that there are many things to circumvent in the apiserver itself. It could also be harder to keep this special case from being broken by a yet another new feature/plugin. Keeping the hash of the config in the annotation seems like a good compromise even though it may not reflect the true status 100% accurately. I think this is acceptable. What do you think?\nSure, if you think the annotation approach is easier, I would go with that. I guess in the case Brian mentoined (master adds a new API field with a default value), you would not update the mirror pod, because the static pod definition has not changed?\nYes, a hash would be sufficient.\nIt shouldn't be necessary to update the mirror pod in the case that a new default field was updated, because that field should be populated automatically by the apiserver on decode from etcd.\nWe should fix this so we don't have this problem again in 1.2.", "commid": "kubernetes_issue_8683", "tokennum": 226}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8af178860a3c1800ecf419aa518069c607460de0970fb5edf5d40402c80f5995", "query": "{ code: http.StatusBadRequest, expected: &Error{ <del> Retriable:      true, </del> <ins> Retriable:      false, </ins> HTTPStatusCode: http.StatusBadRequest, RawError:       fmt.Errorf(\"HTTP response: 400\"), },", "positive_passages": [{"docid": "doc-en-kubernetes-e65d433be70b14f59611269e2f1c0fa746f312a0f5c96a0c29a874f17f7c06ea", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: If you create a service that reference a Basic IP in a standard load balancer cluster, the service will stuck at \"Pending\" state for days without detailed error from Azure response. When you describe the service, it only has following: What you expected to happen: In this case Azure responded 400 with detailed error message that the referenced IP is a basic IP and cannot be used on standard LB. I would expect the detailed error message show up as events for easier diagnostic. How to reproduce it (as minimally and precisely as possible): Create a service that reference a Basic IP in a standard load balancer cluster Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/assign /area provider/azure /sig cloud-provider\n/area cloudprovider", "commid": "kubernetes_issue_86686", "tokennum": 259}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8b7bd46d1c75c3cad8a320f3adcca87a4acdb2f2662b2a9069d40bb0814046d6", "query": "const ( operationDeleteCollection operation = \"deleteCollection\" operationList             operation = \"list\" <ins> // assume a default estimate for finalizers to complete when found on items pending deletion. finalizerEstimateSeconds int64 = int64(15) </ins> ) // operationKey is an entry in a cache.", "positive_passages": [{"docid": "doc-en-kubernetes-125faf475ef5c9fadc127cee08d3d538bc2825eff7d3fd81be9f088e2d4a0dbf", "text": "Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see ): No What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): \"LRUExpireCache\" Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT What happened: requires write lock since needs to manipulate its list to track recently used item. Currently it uses read lock so it may introduce race condition. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else do we need to know:\nThis was fixed in", "commid": "kubernetes_issue_31081", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8c00eacceb432666c5619a2f9e86e0cc27fa32e42ace4c52c183b10ce16bc244", "query": "// in https://github.com/kubernetes/kubernetes/issues/120720. // We are already hinting the external cloud provider via the annotation AnnotationAlphaProvidedIPAddr. if !nodeIPSpecified { <ins> node.Status.Addresses = []v1.NodeAddress{ {Type: v1.NodeHostName, Address: hostname}, } </ins> return nil } }", "positive_passages": [{"docid": "doc-en-kubernetes-7c861bbb23da2f1ab2b6ca68ce44086076d9635fab7f36a80cef91e7d1c385de", "text": "It looks like there was a change that first appeared in Kubernetes 1.29, where in 1.29 the flag on kubelet is no longer being used to populate the Node's Addresses.Hostname value. Here is the relevant output from a for a 1.28 cluster with : And here's the output from a 1.29 cluster with the same configuration: Here is the full list of parameters in case that is helpful: This is from an IBM Cloud Kubernetes Service 1.28 and 1.29 cluster. We do not think there was any cloud-configuration-manager or any other related change that would cause this difference. Is it possible it is a side effect of ? I expected the behavior to be consistent between Kubernetes releases, since I didn't find any reference to this change in Create an IBM Cloud Kubernetes Service cluster at 1.28 and 1.29 and see the difference No response <details</details<details</details<details</details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nyeah, it seems likely my change broke this, it should keep working as you say, let me take a look /assign\n/sig network /sig cloud-provider\n/assign /unassign Thanks\nFYI it was an unintended side effect of:\nDo the sig cloud provider folks need to help here? We did make external cloud providers the default as of 1.29, which may have uncovered this. Let us know!\nNo, it's just a dumb kubelet startup bug. Well, not dumb, but easy to fix.\nIt seems the problem is that once kubelet sets the hostname the cloud controller manager does not override it so maybe the right behavior is only override it if is actually overridden ?\nwhat problem?", "commid": "kubernetes_issue_124453", "tokennum": 469}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8c00eacceb432666c5619a2f9e86e0cc27fa32e42ace4c52c183b10ce16bc244", "query": "// in https://github.com/kubernetes/kubernetes/issues/120720. // We are already hinting the external cloud provider via the annotation AnnotationAlphaProvidedIPAddr. if !nodeIPSpecified { <ins> node.Status.Addresses = []v1.NodeAddress{ {Type: v1.NodeHostName, Address: hostname}, } </ins> return nil } }", "positive_passages": [{"docid": "doc-en-kubernetes-cb25003b88a3fd857f2f7edabf578ed21b587771e769d62a703fb5f227a9b05a", "text": "we are discussing if the fix should be backported or not It seems you are relaying on the with type Hostname and this not clearly documented We also find out recently that the behavior of this address will be overriden if the external cloud provider configures it if the external cloud provider returns the hostname , then this problem will be solved without need to backport\n(Well, to clarify my comments there: it's not well-defined between different clouds and node linux distros. If you know what cloud and distro you are on, then the behavior might be consistent and usable, but that still makes for a lousy kubernetes API.) Anyway, the question here is: was this actually breaking anything major, or did you just happen to notice this and think \"that's weird\"? (Also, if anyone else was broken by this bug, feel free to chime in; trying to figure out what to do about backporting this, because the original fix for this bug ended up introducing another bug, and the fix for that_ bug is maybe not backport-able...)\nSo far I have only heard from a single customer (who was using IBM Cloud Kubernetes Service) who had something in their cluster relying on cluster node's Address.Hostname value, and so when they updated to 1.29 they were broken. I believe they just modified their code to get this \"Hostname\" value (which was really the node IP) from somewhere else. So, to answer the question, it is somewhere between the \"I noticed it and thought 'that's weird'\" option and the \"it broke something major\" option. We have this documented in our 1.29 release notes for IBM Cloud Kubernetes Service, so other customers will have fair warning before updating. So at this point I don't consider fixing this in 1.29 as essential.", "commid": "kubernetes_issue_124453", "tokennum": 399}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8c2b7daeb2f2fd8ba7fdad2df8322b95cced33a6dff3d9257c5a56bd56282fc8", "query": "return err } glog.V(4).Info(\"Successfully created federation controller manager deployment\") <del> fmt.Println(cmdOut, \" done\") </del> <ins> fmt.Fprintln(cmdOut, \" done\") </ins> fmt.Fprint(cmdOut, \"Updating kubeconfig...\") glog.V(4).Info(\"Updating kubeconfig\")", "positive_passages": [{"docid": "doc-en-kubernetes-6612882cbe44a332a8a18637718123dbd71ae9f680fe3a41129c9067a30b426a", "text": "Kubernetes version (use ): kubernetes/master Environment: na What happened: What you expected to happen: How to reproduce it (as minimally and precisely as possible): see above Anything else we need to know: nope, have a fix.\nThere are no sig labels on this issue. Please by:<br(1) mentioning a sig: <br(2) specifying the label manually: <br<brNote: method (1) will trigger a notification to the team. You can find the team list and label list", "commid": "kubernetes_issue_47291", "tokennum": 117}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8c467caecf5200eafa8b8a2f263bf3c6b6e121e690618ce8a661a0f3e40a61a9", "query": "\"//test/e2e_node/services:go_default_library\", \"//test/e2e_node/system:go_default_library\", \"//test/utils:go_default_library\", <ins> \"//vendor:github.com/coreos/go-systemd/util\", </ins> \"//vendor:github.com/davecgh/go-spew/spew\", \"//vendor:github.com/golang/glog\", \"//vendor:github.com/kardianos/osext\",", "positive_passages": [{"docid": "doc-en-kubernetes-237446a2101b1d0e3896762c3997d0b07e17e89bcd32bef5edcdc8a493c92d82", "text": "Kubernetes version (use ): 6 Environment: GCE What happened: I created a cluster for Heapster testing purposes to debug failing test in It turned out that Summary API does not export system/misc stats in SystemContainers section (though there are kubelet and docker stats). Everything works as expected on nodes. See also https://k8s-\nWhat node OS were you using? We don't create the system (misc) container on systemd, so it's expected that GCI nodes don't report those stats.\nThe default configuration for 1.4, which is: master: GCI nodes: Container VM\nAre the nodes running 1.4.6 too? There was a bug with this in 1.4.5, but it should have been fixed in 1.4.6.\nYes, both are running in 1.4.6. If you want to reproduce from Heapster current head run . It will take some time and as a side effect you should have a cluster with the mentioned problem. This was catch by integration tests and I temporary disabled the check here\nif you have spare cycles, can you look into this?\nfriendly ping\nLooking at it now\nI have found a couple things so far. On the containerVM nodes, cadvisor is exporting a container with \"name\": \"/system\" On the GCI Master, cadvisor is exporting a container with \"name\": \"\" The has this: \"{% set system_container = \"--system-cgroups=/system\" -%}\" (/system is the default misc container name) So the real question is: Should cadvisor export \"/system\" instead of \"\" on GCI? Or should we be configuring GCI to use \"--system-\"?\nI thought we fix this very issue for 1.4 branch by a while back. Are you running into the same issue with 1.5?\nI think I told you the wrong thing earlier. We don't support the misc (/system) cgroup on systemd systems (I can't remember why, but it was an explicit decision - or might know). The is something different, I believe a base systemd cgroup (slice). As for the misc container on ContainerVM nodes, we've been testing for the misc container in 1.5+ in the summary api test (https://k8s-) for a while, and I haven't seen this issue.", "commid": "kubernetes_issue_37453", "tokennum": 538}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8c467caecf5200eafa8b8a2f263bf3c6b6e121e690618ce8a661a0f3e40a61a9", "query": "\"//test/e2e_node/services:go_default_library\", \"//test/e2e_node/system:go_default_library\", \"//test/utils:go_default_library\", <ins> \"//vendor:github.com/coreos/go-systemd/util\", </ins> \"//vendor:github.com/davecgh/go-spew/spew\", \"//vendor:github.com/golang/glog\", \"//vendor:github.com/kardianos/osext\",", "positive_passages": [{"docid": "doc-en-kubernetes-c190eb06e0eb058949f528f1af5886fe17cab35cd1b33a69ea2cddc6a3fc8812", "text": "So if this is still reproducible, it's limited to 1.4. See this the bug was created for the post-fix.\nFound the explanation here: The should use the flag to know the location that has the processes that are associated with , but it should not modify the cgroups of existing processes on the system during bootstrapping of the node. This is because is the on the host and it has not delegated authority to the to change how it manages .\nIIUC this is intended behavior on systemd nodes. Based on the explanation provided, the kubelet doesnt have the authority to control \"misc\" processes on systemd.\n+1. \"misc\" is just a bandaid for cvm. , David Ashpole <:\nOk, so I'm closing this issue.", "commid": "kubernetes_issue_37453", "tokennum": 168}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8c67e36baf5601adbf26705e24ce125af1a5d362667df6aca04c9d3819961dfd", "query": "return } <del> klog.V(4).Infof(\"Updating customresourcedefinition %s\", oldCRD.Name) </del> <ins> klog.V(4).Infof(\"Updating customresourcedefinition %s\", newCRD.Name) r.removeStorage_locked(newCRD.UID) } </ins> <del> if oldInfo, ok := storageMap[types.UID(oldCRD.UID)]; ok { </del> <ins> // removeStorage_locked removes the cached storage with the given uid as key from the storage map. This function // updates r.customStorage with the cleaned-up storageMap and tears down the old storage. // NOTE: Caller MUST hold r.customStorageLock to write r.customStorage thread-safely. func (r *crdHandler) removeStorage_locked(uid types.UID) { storageMap := r.customStorage.Load().(crdStorageMap) if oldInfo, ok := storageMap[uid]; ok { </ins> // Copy because we cannot write to storageMap without a race // as it is used without locking elsewhere. storageMap2 := storageMap.clone() // Remove from the CRD info map and store the map <del> delete(storageMap2, types.UID(oldCRD.UID)) </del> <ins> delete(storageMap2, uid) </ins> r.customStorage.Store(storageMap2) // Tear down the old storage", "positive_passages": [{"docid": "doc-en-kubernetes-16c95be4925a0d298a67709c93efbb137b71325e5e3041edcf306d6572e4ae65", "text": "Which jobs are failing: pull-kubernetes-integration Which test(s) are failing: TestWebhookConverterWithDefaulting /assign /priority important-soon /area custom-resources /sig api-machinery /kind flake /milestone v1.16\n/cc\nseveral of the webhook converter tests have similar flakes. it looks like the wait for storage version to become effective times out occasionally Rare flakes seen in all of these tests: TestWebhookConverterWithWatchCache/nontrivial-converter TestWebhookConverterWithWatchCache/metadata-mutating-converter TestWebhookConverterWithDefaulting/metadata-mutating-converter TestWebhookConverterWithWatchCache/noop-converter TestWebhookConverterWithDefaulting/empty-response TestWebhookConverterWithoutWatchCache/nontrivial-converter/check-2 TestWebhookConverterWithoutWatchCache/noop-converter/check-0/v1beta2 TestWebhookConverterWithoutWatchCache/nontrivial-converter/check-0/v1beta2\ncc\nYikes, I\u2019ll sort it out.\niiuc sending an empty patch gets short-circuited and doesn't bump CR generation, even if the storage version gets changed, which means we do not re-write to etcd and go through the encoding path this would be racing and doing noop's if the first pass of didn't get the expected storage version I will send a fix to make the patch do actual mutation\nIt doesn't bump generation, but the bytes to persist in etcd would still be different if the storage version had changed, so they should persist. You can verify that by changing the storage version on a CRD yourself, do an empty patch, and see if the resourceVersion changes.\nyou're right. Generation is for non-metadata change only, and the RV changes. I queried etcd locally and the apiVersion did change for an empty patch (sidetracking: another observation is after changing the storage version (say v1 -v2; noop convertor), empty-patching v2 endpoint would bump generation, while empty-patching v1 endpoint wouldn't)\nanother theory: our cached storage strategy could be stale if the CRD informer merges multiple events together (e.g. the informer does a re-list).", "commid": "kubernetes_issue_78913", "tokennum": 546}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8c67e36baf5601adbf26705e24ce125af1a5d362667df6aca04c9d3819961dfd", "query": "return } <del> klog.V(4).Infof(\"Updating customresourcedefinition %s\", oldCRD.Name) </del> <ins> klog.V(4).Infof(\"Updating customresourcedefinition %s\", newCRD.Name) r.removeStorage_locked(newCRD.UID) } </ins> <del> if oldInfo, ok := storageMap[types.UID(oldCRD.UID)]; ok { </del> <ins> // removeStorage_locked removes the cached storage with the given uid as key from the storage map. This function // updates r.customStorage with the cleaned-up storageMap and tears down the old storage. // NOTE: Caller MUST hold r.customStorageLock to write r.customStorage thread-safely. func (r *crdHandler) removeStorage_locked(uid types.UID) { storageMap := r.customStorage.Load().(crdStorageMap) if oldInfo, ok := storageMap[uid]; ok { </ins> // Copy because we cannot write to storageMap without a race // as it is used without locking elsewhere. storageMap2 := storageMap.clone() // Remove from the CRD info map and store the map <del> delete(storageMap2, types.UID(oldCRD.UID)) </del> <ins> delete(storageMap2, uid) </ins> r.customStorage.Store(storageMap2) // Tear down the old storage", "positive_passages": [{"docid": "doc-en-kubernetes-4d6bef5a272bfef04fa7527d92c495ee5b0e5d06d06a593b8089b98a3b84ddb9", "text": "Two scenarios: -create-update events merged into an update event: strategy with UID:a was created on demand for CRD Foo Foo was deleted and recreated strategy with UID:b was created on demand for the new Foo new Foo got updated (e.g. switching storage version) the strategy with UID:b is supposed to be deleted and , to reflect the last update. But if the CRD informer merges the delete-create-update events into , the strategy with UID:a will be deleted, but the strategy with UID:b won't. -update events merged into a create event: strategy with UID:a was created on demand for CRD Foo Foo was updated (e.g. switching storage version) the strategy with UID:a is supposed to be deleted and , to reflect the last update. But if the CRD informer merges the create-update events into , the strategy with UID:a won't be deleted (as we don't react on create events). another race found in , which could happen in a single update.\nI think I :", "commid": "kubernetes_issue_78913", "tokennum": 234}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8c6af7196bdb34714ca3a0b55ef7cd6c33a35deecbcfe6e8652fea83b762000c", "query": "extensions.Kind(\"ReplicaSet\"):                  &ReplicaSetDescriber{c}, extensions.Kind(\"NetworkPolicy\"):               &ExtensionsNetworkPolicyDescriber{c}, <ins> extensions.Kind(\"PodSecurityPolicy\"):           &PodSecurityPolicyDescriber{c}, </ins> autoscaling.Kind(\"HorizontalPodAutoscaler\"):    &HorizontalPodAutoscalerDescriber{c}, extensions.Kind(\"DaemonSet\"):                   &DaemonSetDescriber{c}, extensions.Kind(\"Deployment\"):                  &DeploymentDescriber{c, versionedClientsetForDeployment(c)},", "positive_passages": [{"docid": "doc-en-kubernetes-6d76348628664e8e1283688eb2571b9c9ddbeb679dd9d941b90f8deb0741d5d7", "text": "Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see ): No What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): describe psp Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST Kubernetes version (use ): Environment: Doesn't matter. What happened: doesn't show PSP's fields: What you expected to happen: All PSP fields should be shown. How to reproduce it (as minimally and precisely as possible):\nIf you're agree with that than I (or :) ) could implement it.\nyes, improve the describer. Look at the scc describer for formatting.\nany ideas which SIG should own PSP?\nIn this case it should be sig-cli /sig cli\nyeah, this is cli related. I'd go with sig-auth for actual behavior.", "commid": "kubernetes_issue_43757", "tokennum": 222}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8c9cad5ab9934801e5e0096c9835e7a1cd1a3fff6d905c8e7a67eb93670ea907", "query": "value: 512M - name: HEAP_NEWSIZE value: 100M <ins> - name: POD_NAMESPACE valueFrom: fieldRef: fieldPath: metadata.namespace </ins> volumes: - name: data emptyDir: {}", "positive_passages": [{"docid": "doc-en-kubernetes-600b05087b3e5a02baef82de4ad7a72820fecd2de58582bba171390ab13fae8d", "text": "The namespace seems to be hard coded :\ncc:\nThanks. We can improve it after v1 release.", "commid": "kubernetes_issue_10034", "tokennum": 22}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8ca30b6fe0a058f21d123edb518016758be1d4b1ae4725a6ffaac453bbd91ddd", "query": "isMigratedOnNode := mpaSet.Has(pluginName) <del> if isMigratedOnNode { installed := false driverName, err := csiMigratedPluginManager.GetCSINameFromInTreeName(pluginName) if err != nil { return isMigratedOnNode, err } for _, driver := range csiNode.Spec.Drivers { if driver.Name == driverName { installed = true break } } if !installed { return true, fmt.Errorf(\"in-tree plugin %s is migrated on node %s but driver %s is not installed\", pluginName, string(nodeName), driverName) } } </del> return isMigratedOnNode, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-43fa70370952068e2f27033c41492113945a1e0b0ce47a43a47f5065969f2aa7", "text": "After the cluster was updated to enable PD CSI Driver, there was a race condition where AD Controller (kube-controller-manager) started to BEFORE the PD CSI Driver was up, thus AD Controller gave us the error Then AD Controller triggered the disk detach because the disk/volume was not populated in the desired state of world. Unfortunately the disk was in use during this detach and got corrupted. Since cluster upgrades can cause the controller manager and CSI drivers to start at different times, the AD controller needs to be more conservative when detaching We have not been able to reproduce this, it came up from a customer. /sig storage /assign <detailsk8s 1.23, CSI migration enabled </details<detailsGKE </details<details</details<details</details<details</details<details</details\n/triage accepted\nI think there's potentially two changes we should do: 1) for the initial DSW population, we should skip the check that if the csi driver is not installed. 2) in general, we should not skip volumes during dsw initial population if an error is returned. If we had some temporary api server error then that would cause volumes to not get to dsw and similar behavior happen. cc\nfor a repro, maybe you can try something like: a cluster with csi migration enabled (control plane + nodes) a pod with intree-volume and get it running the csi driver node daemonset. verify the driver is removed from CSINode kube-controller-manager\ncc\n/cc was trying to repro this, but on GKE with the managed driver which made it complicated.\nYeah maybe gce kube-up would be easier for a repro\nIf CSINode says that it has migrated GCP PD volume plugin to CSI, then IMO A/D controller should always attach GCP PD volumes to it using CSI, regardless if the CSI driver is present or not. In-tree volume plugin in the kubelet is disabled and can't mount any in-tree volumes anyway. To flip the migration feature gate / upgrade / downgrade kubelet, the cluster admin must drain the node first to make sure everything is detached. A/D controller should not see change of CSINode migration annotations with any volume attached to it.\n/priority important-soon\nAnother option could be to process these volumes anyways but add them to DSOW with migration status as \"uncertain\", so as they can be re-processed later.", "commid": "kubernetes_issue_115297", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8ca30b6fe0a058f21d123edb518016758be1d4b1ae4725a6ffaac453bbd91ddd", "query": "isMigratedOnNode := mpaSet.Has(pluginName) <del> if isMigratedOnNode { installed := false driverName, err := csiMigratedPluginManager.GetCSINameFromInTreeName(pluginName) if err != nil { return isMigratedOnNode, err } for _, driver := range csiNode.Spec.Drivers { if driver.Name == driverName { installed = true break } } if !installed { return true, fmt.Errorf(\"in-tree plugin %s is migrated on node %s but driver %s is not installed\", pluginName, string(nodeName), driverName) } } </del> return isMigratedOnNode, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-8286ec57fa1e024ad026b2342f466cffd200140a0a95c9b64ae688331c52eb45", "text": "But surely it looks like might be easiest unless it has any downsides.\nThere wasn't a node update in this case---there was a control plane update which restarted the PD CSI driver, and it looks like the CSIDriver resource was updated or changed in some way which raced with the kube-controller-manager restart.\nIs there anyway we can know if the csi driver is up and running(like a health check ping) before populating DSW?\nWe use the CSINode registration to determine that. The discussion here I think is concluding that we should not use that as a criteria for adding the volume to DSW. We only need to check that CSI migration is enabled on the node.\n+1 we need to be very resilient against races, I think we have to assume a driver is in process of being installed at any point in the AD controller reconcilliation.\n/assign sunnylovestiramisu\nReproduced with the steps: In /var/log/kube-controller-\nTested with the and doing the reproduce steps above. The error of does not show up anymore. The error message still get logged in the kube-controller- for debugging purpose: Ran Ran On the GCP console, the disk is used by node: Ran I redeploy the pd-csi-driver and then make sure it is up and running. Ran", "commid": "kubernetes_issue_115297", "tokennum": 285}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8cb17090ac0b7f807ada5fce8ceb5df265aeb62cf70d00589d8485c362956ff4", "query": "if err != nil { return err } <ins> if existingRole.AggregationRule != nil { // the old role already moved to an aggregated role, so there are no custom rules to migrate at this point return nil } </ins> glog.V(1).Infof(\"migrating %v to %v\", existingRole.Name, newName) existingRole.Name = newName existingRole.ResourceVersion = \"\" // clear this so the object can be created.", "positive_passages": [{"docid": "doc-en-kubernetes-cf86a1652325e783afd2e6de68ee19a134c3d5bc67e73b574ad8b67c1852b0fb", "text": "/kind bug What happened: I deployed a fresh custom HA kubernetes v1.10.2 cluster with 3 nodes (all controller and worker currently, more workers planned). I then created a namespace called \"stummi\" and a rolebinding with \"user=stummi clusterrole=admin\" in this namespace. User stummi (successfully authenticated by TLS client certificate) was not able to list pods or anything else in his namespace: While trying to figure things out, I downgraded to v1.8.11 (a version without cluster role aggregation, that worked) and also tried v1.11 alpha2 (which did not work). I never purged my etcd and I sadly do not have logs from before the different versions. Shortly after posting on slack and before writing this ticket, I dumped the cluster roles in question: Note the rules. What you expected to happen: I expected user stummi to be able to do most things in his namespace. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: I posted this problem on slack and helped me and wanted this issue opened. /sig auth The cluster is deployed with ansible and I can give the playbooks when required. Environment: Kubernetes version (use ):Cloud provider or hardware configuration: 3 virtual machines (2 cores, 8GB memory) OS (e.g. from /etc/os-release): Debian Stretch Kernel (e.g. ): Install tools: custom ansible playbooks Others: Please let me know if you need more information. I'm happy to provide everything you need to fix this :)\n/assign", "commid": "kubernetes_issue_63760", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8ce1f7123faf139192f1ba727ed3da36529cce120c33a879b9fc5229cdd5286d", "query": "\"net/http\" \"net/url\" \"os\" <ins> \"path/filepath\" </ins> \"testing\" <ins> \"github.com/stretchr/testify/assert\" </ins> ) // copied from k8s.io/client-go/transport/round_trippers_test.go", "positive_passages": [{"docid": "doc-en-kubernetes-30e07950978ed617c12104c8342559dfe477718ba7eb61f98c21f95bb37c1439", "text": "In kubectl v1.8.0+, schema info is cached in the location specified by (defaulting to ), written with world-writeable permissions (rw-rw-rw-). If is specified and pointed at a different location accessible to other users/groups, the written files may be modified by other users/groups and disrupt the kubectl invocation. CVSS score: CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N (3.3, low) What versions are affected? kubectl v1.8.0+ What configurations are affected? Invocations that point at world-writeable locations Impact Malformed responses written to the cache directory can disrupt the kubectl invocation Workaround Use the default location in the $HOME directory or point it at a directory that is only accessible to desired users/groups. (original description follows) ==== What happened: The files inside of \".kube/http-cache\" are world writeable (rw-rw-rw-). While the default for these files appears to be the home directory, using the \"--cache-dir\" flag could put these files into a place where world writeable files would allow any user / process to modify the cache files. Modification of the cache files could influence the kubectl utility in a negative way for other users. What you expected to happen: Apply stricter file permissions to the http-cache files. How to reproduce it (as minimally and precisely as possible): Run any generic kubectl command which is successful and then list the cache directory $ kubectl get pods --all-namespaces $ ls -la Anything else we need to know?", "commid": "kubernetes_issue_76676", "tokennum": 398}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8ce1f7123faf139192f1ba727ed3da36529cce120c33a879b9fc5229cdd5286d", "query": "\"net/http\" \"net/url\" \"os\" <ins> \"path/filepath\" </ins> \"testing\" <ins> \"github.com/stretchr/testify/assert\" </ins> ) // copied from k8s.io/client-go/transport/round_trippers_test.go", "positive_passages": [{"docid": "doc-en-kubernetes-03c8940a04bf023e0d3632a105949b7e85efda694ffafea56ecb99998a766122", "text": ": I estimate this is a low severity security issue with a CVSS score of \"3.3 / CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N\" - Environment: Linux Kubernetes version (use kubectl version):Client Version: version.Info{Major:\"1\", Minor:\"12\", GitVersion:\"v1.12.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2019-02-26T12:49:28Z\", GoVersion:\"go1.10.8\", Compiler:\"gc\", Platform:\"linux/amd64\"} Server Version: version.Info{Major:\"1\", Minor:\"12\", GitVersion:\"v1.12.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2019-02-26T12:49:28Z\", GoVersion:\"go1.10.8\", Compiler:\"gc\", Platform:\"linux/amd64\"} Cloud provider or hardware configuration: AWS. Running kube api server in hyperkube. OS (e.g: cat /etc/os-release): NAME=\"CentOS Linux\" VERSION=\"7.1808 (Core)\" ID=\"centos\" IDLIKE=\"rhel fedora\" VERSIONID=\"7\" PRETTYNAME=\"CentOS Linux 7.1808 (Core)\" ANSICOLOR=\"0;31\" CPENAME=\"cpe:/o:centos:centos:7\" HOMEURL=\"\" BUGREPORTURL=\"\" CENTOSMANTISBTPROJECT=\"CentOS-7\" CENTOSMANTISBTPROJECTVERSION=\"7\" REDHATSUPPORTPRODUCT=\"centos\" REDHATSUPPORTPRODUCTVERSION=\"7\" OSTREEVERSION=7.1808 Kernel (e.g. uname -a): Linux hackit.internal 3.10.0-862.11.6.el7.x8664 SMP Tue Aug 14 21:49:04 UTC 2018 x8664 x8664 x86_64 GNU/Linux Install tools: Manual installation. Others: n/a\n/sig product-security\nClosing this issue. <detailsIn response to : if you think this is serious, send an email thanks!", "commid": "kubernetes_issue_76676", "tokennum": 565}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8ce1f7123faf139192f1ba727ed3da36529cce120c33a879b9fc5229cdd5286d", "query": "\"net/http\" \"net/url\" \"os\" <ins> \"path/filepath\" </ins> \"testing\" <ins> \"github.com/stretchr/testify/assert\" </ins> ) // copied from k8s.io/client-go/transport/round_trippers_test.go", "positive_passages": [{"docid": "doc-en-kubernetes-5f4971cee99e57062ae7961121de35cc677214a3e6ca77682b093e74b00a9b30", "text": "</details\nAdjusted the CVSS score to to indicate user interaction is required (since they must specify a non-default cache option pointed at a shared writeable location)\nThere are two places this should be done: PathPerm and FilePerm should be set here: the temp file and final file should have stricter permissions (probably 0660) here:\n/cc\n/help\nThis request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\n/assign I would like to work on release-1.9, as I just made a hot fix for our team's k8s version of 1.9.\nGitHub didn't allow me to assign the following users: yuchengwu. Note that only and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign I would like to work on release-1.9, as I just made a hot fix for our team's k8s version of 1.9. 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\nhelp fixing this is welcome, though it would only be fixed in releases 1.12+, per\n/label official-cve-feed (Related to kubernetes/sig-security)", "commid": "kubernetes_issue_76676", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8d2d955142b0c9fcf62cd999d56cd72ac79b377d0e250a88d6a487d10ab07bed", "query": "return false, nil, nil }, }, <ins> { name:         \"API watch error happen\", volID:        \"vol-005\", attachID:     getAttachmentName(\"vol-005\", testDriver, nodeName), shouldFail:   true, watcherError: true, reactor: func(action core.Action) (handled bool, ret runtime.Object, err error) { if action.Matches(\"get\", \"volumeattachments\") { return true, makeTestAttachment(getAttachmentName(\"vol-005\", testDriver, nodeName), nodeName, \"vol-005\"), nil } return false, nil, nil }, }, </ins> } for _, tc := range testCases {", "positive_passages": [{"docid": "doc-en-kubernetes-bf4acf56a8324d5d9229417a25d2febc989c56201f9f4bdce8fffe7a46728546", "text": "A CSI plugin that the 1.10 controller manager can't detect (which could occur in a number of scenarios, such as when a rollout is being performed or a node is evacuated) seems to retry without backoff. In this case, I have a pod referencing a PVC -PV that references my CSI plugin, but no controller plugin running. The controller is probing every 100ms continuously for a single volume attachment. The controller should backoff. Have not tested with higher numbers of pods, but in a busy system this could cause the controller manager to burn CPU. Also, there isn't actually a great error telling the user why the probing is happening (I knew in this case, but an admin likely has no idea).\n/assign\nIssues 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\n/remove-lifecycle stale /milestone v1.14 adding it to next milestone as per if it doesn't make it then it can be further moved\nas KEP has been moved, unless an exception is made, /milestone v1.15\nthe linked kep above is unrelated to this issue. This is a bug and I don't think it needs an associated enhancement\nsorry, got diverted by the comments on that KEP. /milestone v1.14\nHello from Bug Triage Shadow . I'd like to remind that code freeze is coming in 3 days (Friday, 8th March). Is this still planned to be fixed for 1.14?\nWe have not been tracking this for 1.14. /assign can you help triage and see if this is still an issue and if there is a quick fix?\nI can't reproduce the issue, do you remember what you did? From the logs it seems that Watch channel consistently returns so new is called recursively (beware, 1.10 code, but it's very similar in master): Can it produce fairly stable 100ms delay between calls? Anyway, this is not usual code path, watcher does not return in most cases.", "commid": "kubernetes_issue_64952", "tokennum": 478}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8d2d955142b0c9fcf62cd999d56cd72ac79b377d0e250a88d6a487d10ab07bed", "query": "return false, nil, nil }, }, <ins> { name:         \"API watch error happen\", volID:        \"vol-005\", attachID:     getAttachmentName(\"vol-005\", testDriver, nodeName), shouldFail:   true, watcherError: true, reactor: func(action core.Action) (handled bool, ret runtime.Object, err error) { if action.Matches(\"get\", \"volumeattachments\") { return true, makeTestAttachment(getAttachmentName(\"vol-005\", testDriver, nodeName), nodeName, \"vol-005\"), nil } return false, nil, nil }, }, </ins> } for _, tc := range testCases {", "positive_passages": [{"docid": "doc-en-kubernetes-386907f979b2ab6cc28dd5590343cbf2830e874540a448be35232bf4673dff7e", "text": "if I read the code correctly, such recursive must end up with timeout - caller does not care about return value and caller's watch probably won't return anything useful. Is there a reason why we don't return error? This will kick in exponential backoff in A/D controller.\nclearing the milestone for tracking purposes to let the fix land in its own time /milestone clear\nIssues 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\nI found the error would happen when a pv is attahing(volumeattachment has created) and the csi-attacher is deleted at the same time. Then the log would print so frequently (because of recursion).\nis this fixed by ?\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nClosing 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", "commid": "kubernetes_issue_64952", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8d32d5d0bfd9c0bd3c6005814799c863547cc8b4308cfc50442b5a781efa5270", "query": "\"testing\" \"github.com/imdario/mergo\" <ins> \"k8s.io/kubernetes/pkg/client/restclient\" </ins> clientcmdapi \"k8s.io/kubernetes/pkg/client/unversioned/clientcmd/api\" )", "positive_passages": [{"docid": "doc-en-kubernetes-4e19a56e8ccacbab4546f622baecdb0b8ef30250430c55f8bcdc4de99b100cd2", "text": "Found in openshift, but I'm pretty sure the codepaths are the same. That means the token is getting ignored and in-cluster config is being used in preference to flags.\nIs a similar issue?\nYep, kind of regression.\nSigh.\nYes, most likely the same cause.\nI'm on it.\nUnit test :)\nProbably will want to cherrypick this into 1.5.\nWIP in", "commid": "kubernetes_issue_38834", "tokennum": 89}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8d3fcbdaf86325c05a4f1528159bfeae0a48d3dc0b9adcaaef99775054cae001", "query": "targetNumNodes := int32(framework.TestContext.CloudConfig.NumNodes - 1) ginkgo.By(fmt.Sprintf(\"decreasing cluster size to %d\", targetNumNodes)) err = framework.ResizeGroup(group, targetNumNodes) <del> framework.ExpectEqual(err, nil) </del> <ins> framework.ExpectNoError(err) </ins> err = framework.WaitForGroupSize(group, targetNumNodes) <del> framework.ExpectEqual(err, nil) </del> <ins> framework.ExpectNoError(err) </ins> err = e2enode.WaitForReadyNodes(c, framework.TestContext.CloudConfig.NumNodes-1, 10*time.Minute) <del> framework.ExpectEqual(err, nil) </del> <ins> framework.ExpectNoError(err) </ins> targetNodes, err := e2enode.GetReadySchedulableNodes(c) framework.ExpectNoError(err) framework.ExpectEqual(len(targetNodes.Items), int(targetNumNodes))", "positive_passages": [{"docid": "doc-en-kubernetes-4d7af6d1d5d1ba0c7ab59da9ea13925b54c282d46d48402ebb3f5409fd2b1204", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: kubernetes/node-problem-detector/node-problem-detector-ci: ci-npd-e2e-node See the Which test(s) are failing: [] NodeProblemDetector [NodeFeature:NodeProblemDetector] [] SystemLogMonitor should generate node condition and events for corresponding errors Since when has it been failing: Dec 03. was at 19:50 PST, was at 21:51 PST. Testgrid link: https://k8s- Reason for failure: Apparently is the culprit. Anything else we need to know: This is likely caused by some library upgrade. Nothing big.\n/sig node\n/assign\nSeems like the failure is caused by . /cc /cc /cc /cc\n/priority critical-urgent\nThe particular bug I care about has been fixed in . I'm gonna still work on submitting , as the same error should also be affecting a few other tests.", "commid": "kubernetes_issue_85933", "tokennum": 235}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8d46d01c3e78078817bc77c7a4819d3eeee857470db70a5d4fd6c208160fa746", "query": "assert.Equal(t, c.expected, real, fmt.Sprintf(\"TestCase[%d]: %s\", i, c.desc)) } } <ins> func TestEnsureLoadBalancerDeleted(t *testing.T) { const vmCount = 8 const availabilitySetCount = 4 const serviceCount = 9 tests := []struct { desc              string service           v1.Service expectCreateError bool }{ { desc:    \"external service should be created and deleted successfully\", service: getTestService(\"test1\", v1.ProtocolTCP, 80), }, { desc:    \"internal service should be created and deleted successfully\", service: getInternalTestService(\"test2\", 80), }, { desc:    \"annotated service with same resourceGroup should be created and deleted successfully\", service: getResourceGroupTestService(\"test3\", \"rg\", \"\", 80), }, { desc:              \"annotated service with different resourceGroup shouldn't be created but should be deleted successfully\", service:           getResourceGroupTestService(\"test4\", \"random-rg\", \"1.2.3.4\", 80), expectCreateError: true, }, } az := getTestCloud() for i, c := range tests { clusterResources := getClusterResources(az, vmCount, availabilitySetCount) getTestSecurityGroup(az) if c.service.Annotations[ServiceAnnotationLoadBalancerInternal] == \"true\" { addTestSubnet(t, az, &c.service) } // create the service first. lbStatus, err := az.EnsureLoadBalancer(context.TODO(), testClusterName, &c.service, clusterResources.nodes) if c.expectCreateError { assert.NotNil(t, err, \"TestCase[%d]: %s\", i, c.desc) } else { assert.Nil(t, err, \"TestCase[%d]: %s\", i, c.desc) assert.NotNil(t, lbStatus, \"TestCase[%d]: %s\", i, c.desc) result, err := az.LoadBalancerClient.List(context.TODO(), az.Config.ResourceGroup) assert.Nil(t, err, \"TestCase[%d]: %s\", i, c.desc) assert.Equal(t, len(result), 1, \"TestCase[%d]: %s\", i, c.desc) assert.Equal(t, len(*result[0].LoadBalancingRules), 1, \"TestCase[%d]: %s\", i, c.desc) } // finally, delete it. err = az.EnsureLoadBalancerDeleted(context.TODO(), testClusterName, &c.service) assert.Nil(t, err, \"TestCase[%d]: %s\", i, c.desc) result, err := az.LoadBalancerClient.List(context.Background(), az.Config.ResourceGroup) assert.Nil(t, err, \"TestCase[%d]: %s\", i, c.desc) assert.Equal(t, len(result), 0, \"TestCase[%d]: %s\", i, c.desc) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-4ac48b480971aca26f0a1896d0fa1bdd3b9ed6e78abeeb1cea4ee05f140cc101", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: controller-manager is stuck in deleting an incorrectly configured LB type service. it cannot be recovered until restarted. What you expected to happen: controller-manager should recover. At least it should allow us to create the service without restarting it. How to reproduce it (as minimally and precisely as possible): put a random IP in above yaml and make sure the resource group doen't exist. Anything else we need to know?: Environment: Kubernetes version (use ): 1.12.4 Cloud provider or hardware configuration: AKS OS (e.g: ): Kernel (e.g. ): Install tools: Others:\n/sig azure\nI also want to add that the above repro is stuck in 403. It's possible for it to be stuck in 404 as well when the SP has the right permission.\nCan you share the log for 404?\nThanks for reporting the issue. /assign Do you mean other services couldn't be configured when this happens?\ncorrect.\nFYI, we had the same issue when the Idle Timeout annotation was set to \"3\" which isn't a supported case. Will this PR also cover this edge case ?\nUnfortunately , this is still not fixed. The idle timeout is not 403 or 404. We need another fix for this (and possibly more for other annotations)", "commid": "kubernetes_issue_75198", "tokennum": 337}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8d7447ee23b804223b90f4154bff0d506eda92bab0292a358d051fb0d1819cf9", "query": "\"fmt\" \"io\" \"net\" <ins> \"net/http\" </ins> \"regexp\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-9fca6378f8b8df6d20b226b62d39deddc0dd6ba6166f0f70fb99239f64c63f5d", "text": "All of our external load balancer tests failed for the better part of a day due to the GCE project that our tests run in hitting its quota for number of target pools. While the target pools have been deleted, the fact that we hit our quota indicates that there must be a leak somewhere, and we need to plug it.\nFor reference, the previous issue was\nCould the leakage be related to ? The quota exhaustion occurred about 22 hrs after that.\nI'd guess that this is due to GetTCPLoadBalancer returning that the load balancer doesn't exist if the forwarding rule is gone, ignoring the target pool, while the service controller considers its deleting done if the cloud provider says that the load balancer doesn't exist. I that logic to the cloud provider because the other implementations of DeleteTCPLoadBalancer weren't/won't be idempotent in the sense of returning ok if the LB doesn't exist. To fix it, we'll either need to make sure all Delete implementations are idempotent and remove the Get call in the controller, or add a method along the lines of IsTCPLoadBalancerDeleted to ask the cloud provider whether all pieces of it have been completely cleaned up. We can't make GetTCPLoadBalancer check that because it's relied on to tell us whether or not the balancer is fully created.\nCopying over my commentary from on why the GKE e2e tests are leaking so many forwarding rules and target pools vs the GCE tests:\nIs there a way for the services test to wait for the service controller to clean up the external resources before finishing (without just doing a sleep)?\nNot without polling GCE directly for whether the resources still exist, although that may be worth it as a workaround. What would be perfect is that clean-up-all-cloud-provider-resources API method that we talked about a couple months ago.\nCan we not perhaps use GCE namespaces or projects as a cheap way of getting this here?\nI don't believe so. We can't use projects due to the fact that projects can't be programatically created (they're intended to be long-lived). I'm not aware of anything along the lines of a GCE namespace other than networks, which won't work because target pools and forwarding rules unfortunately don't seem to be scoped to networks.", "commid": "kubernetes_issue_7753", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8d7447ee23b804223b90f4154bff0d506eda92bab0292a358d051fb0d1819cf9", "query": "\"fmt\" \"io\" \"net\" <ins> \"net/http\" </ins> \"regexp\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-d79b213781c20847fbb47c058c0afaba60ed2f1d9f5b51e77a0a4cda944c52e0", "text": "The target pool leak in the code might be fixed, but the forwarding rule + target pool leak from deleting GKE clusters too quickly is certainly still happening. Reopening for the sake of that half of the issue.\nCan we just add a short sleep to jenkins after the last test has run before it deletes anything?\nYes, you could add a sleep to Ginkgo's AfterEachSuite(): But I'd be concerned about what the upper bound on the sleep period is. Can we get the tests and code in sync with a 1 minute latency here? (e.g. if the controller garbage collects every 60 seconds, then the test only needs to sleep for 60 sec?) And add a BEEG comment to the test's sleep config noting that increasing the sleep time will not improve things, otherwise I'm pretty sure that someone noting flakes in this test in future will think \"maybe I should just increase the sleep period a little bit.\"\nActually, thinking about this a little more, it would be better to put the \"sleep\" logic in the k8s master teardown procedure (i.e. not in the e2e tests or in Jenkins), because otherwise users are going to run into the same resource leakage problems as we are. So master deletion blocks on cleanup of backend cloud resources.\nThere's no way to block master deletion from the master itself. The test framework (or user) just pulls the rug out from underneath the master. See\nRobby's right -- is the real solution to this, but until we have that the best we can do is to have the wait happen elsewhere. The options seem to be: GKE itself Ginkgo's post-testing logic Jenkins' teardown logic I don't like putting it in GKE, because arbitrarily slowing down our API makes for a poor experience for the majority of people that don't still have resources being deleted. I'm not eager to put it in Gingko either, since won't that sleep also take effect whenever anyone runs an e2e test locally against a dev cluster? Putting it in the Jenkins logic makes the most sense to me. I'll send a PR and cc you.\nWe may also want to change the kube-down logic to bring down the master and then nodes in parallel to both speed it up and more closely resemble GKE's teardown logic.\nI've deleted the old forwarding rules and target pools from the project.", "commid": "kubernetes_issue_7753", "tokennum": 530}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8d7447ee23b804223b90f4154bff0d506eda92bab0292a358d051fb0d1819cf9", "query": "\"fmt\" \"io\" \"net\" <ins> \"net/http\" </ins> \"regexp\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-6b81898435dc239c0c98669b4836ce5b1423be788127f142aa9eb15c198137cf", "text": "I'll periodically check to see whether anything is leaked after this point. I apologize if the deletions affected any running tests - everything looked to only be from GKE and parallel e2e runs.", "commid": "kubernetes_issue_7753", "tokennum": 42}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8d833bb18376202ab108268d89fe2bfddcf2ae90481aac2480f57df85594cbeb", "query": "SSLContext ctx = SSLContext.getInstance(\"SSL\"); ctx.init(null, trustAll, new SecureRandom()); <del> URL url = new URL(host + path + serviceName); </del> <ins> URL url = new URL(proto + host + \":\" + port + path + serviceName); </ins> logger.info(\"Getting endpoints from \" + url); HttpsURLConnection conn = (HttpsURLConnection)url.openConnection();", "positive_passages": [{"docid": "doc-en-kubernetes-82cb26acad9fc9df916ca73a6711809a93da9752a7947ed537b4183fa019f2e5", "text": "What would you like to be : There is a tab in the k8s perf dashaboard for the scheduler perf benchmarks, but it is showing nothing, we should fix that: http://perf- What this dashboard should be showing is multiple runs per day of We can run it every hour, and summarize the 24 runs of each day to show 50%, 90% and 99% percentile. Why is this needed: Having daily runs of the benchmarks is important to track performance regressions. /sig scheduling /assign /priority important-soon\nRef\n/cc\nThe ci job's config is at And one of failed logs could be found at I tried to reproduce it on my local machine(because I do not have Gloud credentials, I run the task directly in the container): However it works well on my local machine. It is so weird. It will be very appreciated if anyone could help reproduce it with Gloud credentials.\ncan you try and reach out to the test-infra people? ping them on the slack channel perhaps.\nyes, I have tried to get help from , he is busy now. I'll try more.\nWhile working on reproducing this in order to file a bug against test-infra folks I think I found a solution. Will send PRs shortly. /assign\n/retitle sig-scalability-benchmarks#scheduler fails consistently due to build issues\n/sig scalability Testgrid link: https://k8s- Error logs:\nA word about the solution, the job uses the deprecated script which is not supported anymore by test-infra oncall / folks. I've rewritten the job definition to use pod utilities and it started working (will require to get merged first).\nThanks\nThanks !", "commid": "kubernetes_issue_84186", "tokennum": 383}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8d96894a8a0baecd878fa71e59bf311de1a0c2a8c74cb3bc0bf49191c2b44a6e", "query": "while true; do if result=$(gcloud compute ${resource} list --project=${PROJECT} ${@:2}); then if [[ ! -z \"${GREP_REGEX}\" ]]; then <del> result=$(echo \"${result}\" | grep \"${GREP_REGEX}\") </del> <ins> result=$(echo \"${result}\" | grep \"${GREP_REGEX}\" || true) </ins> fi echo \"${result}\" return", "positive_passages": [{"docid": "doc-en-kubernetes-432f38af47f0e48a0119df4c6a3e98c546702de6b66b5c01890c1ec73b3675a0", "text": "The last 4 runs of https://k8s- have failed on the and steps with : https://k8s- https://k8s- https://k8s- https://k8s- The GCE version of this test suite appears to be fine. This is blocking the submit queue. CC\nIs there a way to see what does /cluster/gce/list- output in the runs... exit status 1 is not very informative\nHere is a non-gke failure: https://k8s-\nGiven that the last thing output from the listing of resource is: I would bet that the defined is failing to find a match from (see )\nHummm I ran it locally against but did not get the same failure\nyou might be more familiar with list-\nThis started happening on the 16th and became more regular on the 18th-- do you think the new janitor code might be causing this? More details here:\nis giving me exit status 1, let me find which command it is.\nYeah, and have figured it out. Because of the janitor, we no longer have any default firewall rules in these projects (which might be a bug), and so now the is failing. I think in the distant past always printed out a header, even if nothing was found, though it hasn't done that in a long time. Fix for is to the on L52. We may also want to decide if we should be deleting the default firewalls.\nWe'll want to cherrypick that to the old branches, too.\nhummm I'll let it skip default-firewall\nKeeping open until we've verified fix", "commid": "kubernetes_issue_41917", "tokennum": 355}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8db58878320cdab5cd92960035d738ca6f04596f6f20348aee3210e384540eff", "query": "} // Filter based on extender implemented predicate functions. The filtered list is <del> // expected to be a subset of the supplied list. failedNodesMap optionally contains // the list of failed nodes and failure reasons. </del> <ins> // expected to be a subset of the supplied list; otherwise the function returns an error. // failedNodesMap optionally contains the list of failed nodes and failure reasons. </ins> func (h *HTTPExtender) Filter( pod *v1.Pod, nodes []*v1.Node, nodeNameToInfo map[string]*schedulernodeinfo.NodeInfo,", "positive_passages": [{"docid": "doc-en-kubernetes-f39360e36dc13c7f3c135efe81c665373563851402d40604cca632c72aed6a7c", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Default scheduler crash if scheduler extender filter returns a not found node What you expected to happen: Default scheduler just should consider the not found node as not an candidate, instead of crash itself (panic). How to reproduce it (as minimally and precisely as possible): cluster only have 1 node: 0.0.0.1 scheduler extender (with nodeCacheCapable enabled) filter accidentally returns a candidate node: 0.0.0.2 scheduler recieved the candidate nodes: 0.0.0.2 from scheduler extender, but got below error: The is SuggestedHost: filteredNodes[0].Name: Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig scheduling", "commid": "kubernetes_issue_79640", "tokennum": 261}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8dee938c7c2dcbe6bab58b1159674e71fce686e46ffa979cf53a8308172c26ec", "query": "// IsNotMountPoint determines if a directory is a mountpoint. func (mounter *Mounter) IsNotMountPoint(dir string) (bool, error) { <del> return IsNotMountPoint(mounter, dir) </del> <ins> return isNotMountPoint(mounter, dir) </ins> } // IsLikelyNotMountPoint determines if a directory is not a mountpoint.", "positive_passages": [{"docid": "doc-en-kubernetes-4bcfc015d2b9d9fa1e84475a3e08fb9ef8299b4e5f821f790188ad7bdae6ecbc", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: There's , and . The former is used by local and nfs volume plugins, while the latter is used by , which is also used by local and nfs volume plugins. What you expected to happen: Can we consolidate these? This is really confusing and could easily be the source of bugs. <!-- DO NOT EDIT BELOW THIS LINE --/kind cleanup\ncc\n/assign I'd like to clean up code.", "commid": "kubernetes_issue_72387", "tokennum": 133}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8e02a1b38f1087d4e8443824f8508a8683cc4db935d00986edf9d3a20f67b916", "query": "kind: Service apiVersion: v1beta1 <del> id: nginxExample </del> <ins> id: nginx-example </ins> # the port that this service should serve on port: 8000 # just like the selector in the replication controller, # but this time it identifies the set of pods to load balance # traffic to. selector: <del> - name: nginx </del> <ins> name: nginx </ins> # the container on each pod to connect to, can be a name # (e.g. 'www') or a number (e.g. 80) containerPort: 80", "positive_passages": [{"docid": "doc-en-kubernetes-8b28935a84f88ac18c7fc65931585a933c76320eb13cd6ef7170c583b31097e6", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: cAdvisor has a option to only collect docker related cgroups. Kubelet stats api now supports allocatable cgroup, /kubepods, for the runtime cgroup and the kubelet cgroup. But with settings, Kubelet stats api can not query pod related cgroups metrics. FYI: What you expected to happen: should be compatible with kubelet stats api.\n/cc\n/sig node /sig instrumentation\nadd to cadvisor in A comma-separated list of cgroup path prefix that needs to be collected even docker-only is specified bump cadvisor dep for Kubernetes setting to\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_61994", "tokennum": 525}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8e02a1b38f1087d4e8443824f8508a8683cc4db935d00986edf9d3a20f67b916", "query": "kind: Service apiVersion: v1beta1 <del> id: nginxExample </del> <ins> id: nginx-example </ins> # the port that this service should serve on port: 8000 # just like the selector in the replication controller, # but this time it identifies the set of pods to load balance # traffic to. selector: <del> - name: nginx </del> <ins> name: nginx </ins> # the container on each pod to connect to, can be a name # (e.g. 'www') or a number (e.g. 80) containerPort: 80", "positive_passages": [{"docid": "doc-en-kubernetes-c993cfc824e8b144526f19f7f90c37dca7b5b7104e06f115b259fa72f1d9ae68", "text": "/close\nClosing 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", "commid": "kubernetes_issue_61994", "tokennum": 71}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8e1e658472189b90bd77fab65ae3b86f1b935834a4e9284c37d75de77a71796b", "query": "} } <ins> func createSocketFile(socketDir string) (string, error) { testSocketFile := filepath.Join(socketDir, \"mt.sock\") // Switch to volume path and create the socket file // socket file can not have length of more than 108 character // and hence we must use relative path oldDir, _ := os.Getwd() err := os.Chdir(socketDir) if err != nil { return \"\", err } defer func() { os.Chdir(oldDir) }() _, socketCreateError := net.Listen(\"unix\", \"mt.sock\") return testSocketFile, socketCreateError } </ins> func TestFindExistingPrefix(t *testing.T) { defaultPerm := os.FileMode(0750) tests := []struct {", "positive_passages": [{"docid": "doc-en-kubernetes-ea06bb5e10f9c1a3c6e6bdd4b05e49a63cf7c6313178f3d65784c243007cbe65", "text": "Subpath unix socket tests can flake because of long socket path. On Linux the path limit should be 108 chars or less. /sig storage", "commid": "kubernetes_issue_61844", "tokennum": 31}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8e55848d5b327d75e554bb8732266e15fb48ac1f5d6641f6727e9307b35ff9a9", "query": "<del> load(\"@io_bazel_rules_go//go:def.bzl\", \"go_library\") </del> <ins> load(\"@io_bazel_rules_go//go:def.bzl\", \"go_library\", \"go_test\") </ins> go_library( name = \"go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-937f1cb17c20e5fd2b4a1f81201690c3dbe6990ef3c1bc74ff71daaa02b6db56", "text": "Solution: I will add one.\n/cc\nxref\nThanks for sending a PR so quickly!\n[MILESTONENOTIFIER] Milestone Issue Needs Attention Action required: During code slush, issues in the milestone should be in progress. If this issue is not being actively worked on, please remove it from the milestone. If it is being worked on, please add the label so it can be tracked with other in-flight issues. Note: If this issue is not resolved or labeled as by Wed, Nov 22 it will be moved out of the v1.9 milestone. <details<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details", "commid": "kubernetes_issue_55959", "tokennum": 230}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8e55848d5b327d75e554bb8732266e15fb48ac1f5d6641f6727e9307b35ff9a9", "query": "<del> load(\"@io_bazel_rules_go//go:def.bzl\", \"go_library\") </del> <ins> load(\"@io_bazel_rules_go//go:def.bzl\", \"go_library\", \"go_test\") </ins> go_library( name = \"go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-b57bf0f1b2dd71c1293d1dafb95c6e51debc5c1d26878053edb8d335b76a3a11", "text": "What would you like to be : Once a metric be deprecated, we should update the unit test accordingly if there is any. We need to work out a way for a unit test freely select codebase version, and also should make sure the unit test won't fail in the subsequent release. Why is this needed: Deprecated also needs to be protected. /sig instrumentation /assign", "commid": "kubernetes_issue_86292", "tokennum": 81}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8ec3a774aa176fce66df3737fa08ceb58d984fb7c16165941972c6e05995d7ae", "query": "(disk.ManagedDisk != nil && diskURI != \"\" && strings.EqualFold(*disk.ManagedDisk.ID, diskURI)) { // found the disk klog.V(2).Infof(\"azureDisk - detach disk: name %q uri %q\", diskName, diskURI) <del> disks[i].ToBeDetached = to.BoolPtr(true) </del> <ins> if strings.EqualFold(ss.cloud.Environment.Name, \"AZURESTACKCLOUD\") { disks = append(disks[:i], disks[i+1:]...) } else { disks[i].ToBeDetached = to.BoolPtr(true) } </ins> bFoundDisk = true break }", "positive_passages": [{"docid": "doc-en-kubernetes-5bed2d3142dabe6e3fc7269ef850324d324032cbc87a456c8f2e9b79085fd590", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: flag is not supported on Azure Stack, should switch to use original way to remove a disk from data disk list, refer to for more details What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others: /kind bug /assign /priority important-soon /sig cloud-provider /area provider/azure", "commid": "kubernetes_issue_94886", "tokennum": 186}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8ec6406138c62bb8b97d5a7b8eacde39b51043d4a4f75c43407f578c7ba8df6d", "query": "REGISTRY ?= gcr.io/kubernetes-e2e-test-images GOARM=7 QEMUVERSION=v2.9.1 <del> GOLANG_VERSION=1.8.3 </del> <ins> GOLANG_VERSION=1.9.1 </ins> export ifndef WHAT", "positive_passages": [{"docid": "doc-en-kubernetes-1b1e05089c93c6eb59b848626d58302483d33d2f2e5531ac5b621da204277493", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind feature This is a followup on , but for Go 1.9 We should do the same kind of testing now to possibly catch bugs in either Go or Kubernetes when doing this kind of dependency version bump. Ideally we'd have automated tests against Go tip (), but we don't have that at the moment, so we have to do it kind of manually. We should also decide which k8s version we should target. k8s v1.8 or v1.9? What Go versions have been used so far? Kubernetes v1.7.0 - go1.8.3 Kubernetes v1.6.0 - go1.7.5 Kubernetes v1.5.0 - go1.7.4 Kubernetes v1.4.0 - go1.6.3 Kubernetes v1.3.0 - go1.6.2 Kubernetes v1.2.0 - go1.4.2 Seems like the trend has been to stay on the same Go version for two releases and then bump. That'd mean we'd switch to Go1.9 in k8s v1.9 Everyone happy with that? Or is there any reason for us to go start using go1.9 in k8s v1.8? In any case, we should indeed start testing go1.9 out now... cc\nLet me know if you find any bugs\nFWIW pretty tight to code-freeze I would prefer punting out a cycle fwiw.\nI don't think we're that close to code freeze given that we have 5 (of 8) weeks left in this coding cycle But I'm happy to defer this to v1.9 if others think that. I guess the main reason for a bump would be scalability goals, but I'm not sure we have the need to expand above 5000 (and that Go would be the bottleneck in that case) for v1.8\nmade the Go benchmarks 9% faster with 15% larger binaries. I'm interested to see how that affects our numbers.\nmid-stack inlining was not included in Go 1.9. It made the compiler too slow. It's being targeted to Go 1.10 now instead, after some compiler optimization work.\nOh, thanks for the correction!", "commid": "kubernetes_issue_49484", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8ec6406138c62bb8b97d5a7b8eacde39b51043d4a4f75c43407f578c7ba8df6d", "query": "REGISTRY ?= gcr.io/kubernetes-e2e-test-images GOARM=7 QEMUVERSION=v2.9.1 <del> GOLANG_VERSION=1.8.3 </del> <ins> GOLANG_VERSION=1.9.1 </ins> export ifndef WHAT", "positive_passages": [{"docid": "doc-en-kubernetes-018b01245292fe1977b7eec8bea53846947ed737ea149d849054911d63924f58", "text": "Regardless, we need to run the scalability tests against the RC so we can report issues earlier-- the last upgrade was particularly painful because of an HTTP regression that we caught way too late.\nyeah. I filed for that now\nyeah, my recollection is that the Go releases usually occur too late in our release cadence and end up getting bumped to the next Kubernetes release. (Also we inevitably find something wrong, though testing RCs would help with that. Though I'm not sure anyone has cycles to test RCs and fix all of the issues that do come up.)\nBased on our current time frame, it looks like go1.9 support will have to slip to k8s 1.9. is open to dig into and start things testing, but there's a number of things that have to move.. I'll try to document those this time around to help with future go version bumps. So far: bazel build rules needed to be updated to support go1.9 () bazel version possibly needs to be updated? some of our custom bazel rules broke\nWhen done, we should update this:\n/priority important-soon\nUpdating the dependency is blocked pending bazel 0.6.0 - .\nCan we upgrade to 0.6.0 now? Does bazel 0.6.0 have multiarch support btw?\nWe can't update to depend on bazel 0.6.0+ until we can figure out how to support different versions of the bazelbuild and kubekins-e2e images in PR jobs in prow based on what branch is being tested. cc\nNoting that we're working on branching jobs, is testing one option here:\n[MILESTONENOTIFIER] Milestone Issue Current <details open<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts. : New functionality.", "commid": "kubernetes_issue_49484", "tokennum": 416}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8ec6406138c62bb8b97d5a7b8eacde39b51043d4a4f75c43407f578c7ba8df6d", "query": "REGISTRY ?= gcr.io/kubernetes-e2e-test-images GOARM=7 QEMUVERSION=v2.9.1 <del> GOLANG_VERSION=1.8.3 </del> <ins> GOLANG_VERSION=1.9.1 </ins> export ifndef WHAT", "positive_passages": [{"docid": "doc-en-kubernetes-69273b286facac9ab246a3deb71fa6e24d55618a503d411a1618742e8a027c28", "text": "</details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details\nI approved this for v1.9, this is something we definitely want in order to keep up with Go (and for improved performance)\nwe're starting to use the forked images now /cc this should be more feasible very soon Edit: test-infra jobs have also been using bazel 0.6 (now 0.6.1) / a recent rules_go to soak things a bit\nWe've identified a failing test as a result of the WIP PR to upgrade the codebase to go1.9: The admission webhook test fails with certificate errors under go1.9.1, but runs successfully under go1.8.3. cc: who wanted to be alerted to potential bugs\n- please see for a possible fix", "commid": "kubernetes_issue_49484", "tokennum": 212}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8efcbb15dec65e745bef4b59c6754f957448ccf484d1a9234cdea3578d1c746a", "query": "// remove all existing c.RemoveStreams(stream0, stream1) <ins> // remove nil stream should not crash c.RemoveStreams(nil) </ins> if len(c.streams) != 0 { t.Fatalf(\"should not have any streams, has %d\", len(c.streams)) }", "positive_passages": [{"docid": "doc-en-kubernetes-68fed35f8c13d4bb380046d0fa704085775461d797cc59667c2cdfcb32483bea", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --Since upgrading to Kubernetes v1.19.11 (from v1.19.10) we see occasional panics in kubelet related to portforward streams: This issue seem to be introduced with should not panic and crash. We have not been able to successfully force this to happen, but it has happened 41 times in the last 2 weeks across 7 clusters (~100 nodes). Kubernetes version (use ):Cloud provider or hardware configuration: Self managed clusters on AWS. OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others: /sig node /cc\nHey thank you for the report! :pray: Uhh, thats unfortunate. The panic occurs there on L101: It looks like because works. The stack trace indicates the same: A on is a no-op, so would not be harmful. does also not seem to be , a crash in would have been visible in the stack trace. It may be possible that something assigned to the stream interface. Which means a check for will return , but accessing its fields is causing a segmentation fault. This does not explain why the crash is not visible in the trace.\nWith a quick look at the streaming code it's likely to be triggered by a timeout in waiting for streams: If the above case is hit then it goes down to , and if the timeout occurs before then it means that either or And then it attempts to remove the streams where at least one is : So it probably makes sense to check for either before passing to or inside the method where it crashes. This theory lines up with our kubelet logs, where I can see this just before the panic (didn't notice before):\nThank you for the summary working on a fix in\n/triage accepted /assign\ndo you use dockershim within your cluster?\nYes, we still use dockershim.\nGood, that's also why the panic happens within the kubelet.\nJust to make sure I understand the scope of this issue, this only affects things like or other things that use the API, correct?\nExactly :+1:", "commid": "kubernetes_issue_102480", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8f11fbe91fcc9e6c9655ad66308de8ae050820f484175e463906dfc40ef087ab", "query": "if _, err := dc.coreClient.CoreV1().Pods(tc.pod.Namespace).Create(ctx, tc.pod, metav1.CreateOptions{}); err != nil { t.Fatalf(\"Failed to create pod: %v\", err) } <ins> dc.clock.Sleep(tc.timePassed) </ins> if err := dc.informerFactory.Core().V1().Pods().Informer().GetIndexer().Add(tc.pod); err != nil { t.Fatalf(\"Failed adding pod to indexer: %v\", err) } <del> dc.clock.Sleep(tc.timePassed) </del> <ins> diff := \"\" </ins> if err := wait.Poll(100*time.Millisecond, wait.ForeverTestTimeout, func() (bool, error) { <del> return dc.stalePodDisruptionQueue.Len() == 0, nil </del> <ins> pod, err := dc.kubeClient.CoreV1().Pods(tc.pod.Namespace).Get(ctx, tc.pod.Name, metav1.GetOptions{}) if err != nil { t.Fatalf(\"Failed getting updated pod: %v\", err) } diff = cmp.Diff(tc.wantConditions, pod.Status.Conditions, cmpopts.IgnoreFields(v1.PodCondition{}, \"LastTransitionTime\")) return diff == \"\", nil </ins> }); err != nil { <del> t.Fatalf(\"Failed waiting for worker to sync: %v\", err) } pod, err := dc.kubeClient.CoreV1().Pods(tc.pod.Namespace).Get(ctx, tc.pod.Name, metav1.GetOptions{}) if err != nil { t.Fatalf(\"Failed getting updated pod: %v\", err) } diff := cmp.Diff(tc.wantConditions, pod.Status.Conditions, cmpopts.IgnoreFields(v1.PodCondition{}, \"LastTransitionTime\")) if diff != \"\" { t.Errorf(\"Obtained pod conditions (-want,+got):n%s\", diff) </del> <ins> t.Fatalf(\"Failed waiting for worker to sync: %v, (-want,+got):n%s\", err, diff) </ins> } }) }", "positive_passages": [{"docid": "doc-en-kubernetes-124d4c7fb9ee696a83909f715e9bd8706a0f4465e08a35801f7cd2c1ed445555", "text": "/kind failing-test <!-- If this is a flake, please add: /kind flake --/kind flake <!-- Please assign a SIG using: /sig SIG-NAME --/sig testing apps\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\ncan you PTAL, it seems this test was in It doesn't seem to have a high rate of failure , but seems flakes are legit\n/assign\nside note: it's really hard to make it fail in a fast machine :) I had to temporarily add a sleep in the reconciler.\nhave you tried Jordan's instructions compiling and running with ? for integration you should have an external etcd instance\nI haven't. Good to know for next time :)", "commid": "kubernetes_issue_112594", "tokennum": 238}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8f331c45627274ac8fff69c65876c04c18b4a61cc8edc92a00ba2361f90b93e8", "query": "k8s-app: nvidia-gpu-device-plugin addonmanager.kubernetes.io/mode: Reconcile spec: <ins> selector: matchLabels: k8s-app: nvidia-gpu-device-plugin </ins> template: metadata: labels:", "positive_passages": [{"docid": "doc-en-kubernetes-81aeaa915020279b8f6f88fad69c7f8c675b68383da3729b9f05c07134ed836b", "text": "This issue is here to satisfy PR requirements of issue association. A lot of times we need to do version bumps for minor bug fixes that don't deserve a separate issue in the kubernetes/kubernetes repo. /kind bug /sig node\n/lifecycle frozen\nall the linked PRs are emrged and no activity since more than 3 years /close\nClosing this issue. <detailsIn response to : all the linked PRs are emrged and no activity since more than 3 years /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", "commid": "kubernetes_issue_57125", "tokennum": 141}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8f402cd9e780cac89ee852b185a256ebc76a205b55cb097d736a0483668fbc48", "query": "containers: - name: fluentd-elasticsearch image: gcr.io/google_containers/fluentd-elasticsearch:1.5 <ins> resources: limits: cpu: 100m </ins> env: - name: \"FLUENTD_ARGS\" value: \"-qq\"", "positive_passages": [{"docid": "doc-en-kubernetes-76a1437b2e9419a405205d59af74d9b368790a08551fbd85b287efde2a056dcd", "text": "During debugging , I noticed that one of services pods: monitoring and logging pods stuck at pending sometimes forever: I logged into the node, and found the container is running happily on the node: Looks like status is never reported from kubelet. I checked kubelet log, then I found: Why we cannot delete mirror pod? and Created a new one? Because this regression, once we run into such state, the rest of test won't be triggered, and eventually timeout / failed.\nchecks those service pods in ready state, and prevent the test to run once it is pending. cc/ I think this is the real issue I talked to you earlier about PodStatus.\nI spoke to offline. For some reason, kubelet thinks the spec of the mirror pod does not match the static pod locally. It then decides to delete the mirror pod and recreate it, repeatedly. As a result of that, it slows down (due to the QPS limit?) reporting statuses of other pods. This can be reproduced by running the e2e \"Shell\" test. I am looking into why the specs would suddenly mismatch. Did any recent PR modified the pod spec in apiserver?\nThe recently introduced default cpu share limit was not there in the static pod, causing the difference between its spec and the mirror pod's.\nSeeing this as well. Makes the whole cluster slow and unusable for me. Sent from my iPhone\nIs there a desired fix for this?\nsaid she would add default resource limits to the static pod manifest files. If we go for that, I think it's reasonable to fail (not run the static pod) if resource limit is not specified. Also, the resource limits set in the mirror pods are not meaningful because kubelet creates containers based on the spec of the static pod. In general, static pods do not subject to any defaulting values applied at the apiserver.\nPretty sure that this is fixed by . Certainly testing against head since then works well for me. What version are you testing?\nwas fixing node status, and the problem had been around for a while. This issue is about pod status, which is still unfixed on head. These two are very different, and my cluster did include the fix :) This issue will slow down kubelet at times, but if you get lucky and the pod status (running) get sent out in time, the tests will still pass.", "commid": "kubernetes_issue_8642", "tokennum": 506}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8f402cd9e780cac89ee852b185a256ebc76a205b55cb097d736a0483668fbc48", "query": "containers: - name: fluentd-elasticsearch image: gcr.io/google_containers/fluentd-elasticsearch:1.5 <ins> resources: limits: cpu: 100m </ins> env: - name: \"FLUENTD_ARGS\" value: \"-qq\"", "positive_passages": [{"docid": "doc-en-kubernetes-dbb34576173a9a8fefb5aa440567e5b808bc06b80f759ff3da54bf129fc77991", "text": "There is no way the issue is fixed by that PR. I am still seeing the issue on HEAD. The system gets worse the longer its up. I agree with the analysis of the issue in source PR Sent from my iPhone\nI am on this one, and here is proposed solution in my mind so far (not final yet since I haven't put too much thoughts into it yet): 1) For all our static pods I am going to update them with some initial cpu limit for now. This should quickly stop flakiness caused by this particular issue. 2) Next step is that for static pods, if there is no initial cpu limit, kubelet should refuse to run. Before I do this, I need to send an announcement to our container-vm users about this potential breakage for the in the future. Another potential fix is we can ignore resource changes when comparing if a mirror pod is updated or not. I think is proposed a similiar one earlier. But I had a concern with it: this is defeat the initial purpose we created mirror pods and sync back to master. So if one made some resource changes on the static pods, you have to always ssh-ed into the node to see if the new value applied or not. Also eventually (post 1.0) those mirrored pod's resource limit is going to be used by scheduler when calculating if user pods are fit or not, we need them to be accurated. Another concern is in the code implementation itself to distinuguish mirror pods future from rest of pods. I guess this shouldn't be the big issue here. Any more suggestions here? One puzzle I had is that why master component pods doesn't have issue at all. I manually restart kube-apiserver pod, still doesn't have the issue.\nDepending on time we could just remove the default limit from the limit range as a stop gap. Sent from my iPhone\nCan you just bypass defaulting at the apiserver when you create mirror pods? I can't think of any other solution that works in general and is easily maintainable. Approach 2 you described in the previous entry works if we are defaulting cpu limit, but breaks as soon as we default anything else.", "commid": "kubernetes_issue_8642", "tokennum": 459}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8f402cd9e780cac89ee852b185a256ebc76a205b55cb097d736a0483668fbc48", "query": "containers: - name: fluentd-elasticsearch image: gcr.io/google_containers/fluentd-elasticsearch:1.5 <ins> resources: limits: cpu: 100m </ins> env: - name: \"FLUENTD_ARGS\" value: \"-qq\"", "positive_passages": [{"docid": "doc-en-kubernetes-f6117564d0d1387afeb4e79ddb55d47325739be1eed6d26971dac3a1b60079fd", "text": "Same problem with ignoring resource differences when comparing mirror pod to static pod -- as long as defaulting only touches resources, that works, but if we change it to touch other stuff, then it breaks.\nCommit I had can quickly fix current bleeding issue. Currently we only have master component pods and fluentd pod are file based by default. Master component pods doesn't create any issue now because mirror pods aren't created at the first place (due to recent change made by Also file-based pods will have issue only when its spec doesn't have initial value, and need to update (delete miss matched mirror pod, and recreate a new one). Please note that with my commit, everything is working even I manually update its cpu limit from 100m to 200m, there is no issue at all, and query pod shows accurate result with the new limit too: How badly we request all users using file-based pod feature providing default cpu limit for now? Eventually we want to get rid of file-based pods completely, also encouraging the user provides the initial resource limit is aligning with our direction in a long run anyway.\nJust to clarify, what I was suggesting was for a \"real fix\" not the temporary measure to stop the bleeding (which you already have in your PR). But what do you think of what I suggested as the longer-term fix? My point is that today, we default CPU, but in the future, we may default anything. It seems that the most maintainable fix is to just not do defaulting when creating mirror pod from static pod. Is that possible? I wonder if the reason manual update works (what you described in your last comment) is because we don't go through the defaulting when you do an update, only a create? (Though that sounds like a bug.) IMO we don't need CPU default right now, especially since we already have kubelet flag for limiting pods per machine (though unfortunately it's currently set to 100 because we haven't reconfigured the tests that intentionally run lots of pods per node, to override the flag. we can change the default to 30 and add an override mechanism if this is important.)\nComparing a config file with the live state and expecting them to match is doomed. The recommended approach is described by . Kubelet could store the config as an annotation in the mirror pod and compare with that.", "commid": "kubernetes_issue_8642", "tokennum": 504}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8f402cd9e780cac89ee852b185a256ebc76a205b55cb097d736a0483668fbc48", "query": "containers: - name: fluentd-elasticsearch image: gcr.io/google_containers/fluentd-elasticsearch:1.5 <ins> resources: limits: cpu: 100m </ins> env: - name: \"FLUENTD_ARGS\" value: \"-qq\"", "positive_passages": [{"docid": "doc-en-kubernetes-335d12ba313aa19619a2c4b18ee4ddf7703e123f21840f5e77167fa2ece19bed", "text": "Does the scheduler favor nodes with the fewest pods even if they don't specify resources? LimitRange does cause that to happen.\nStoring the config as an annotation sounds good to me. Filed\nAlthough this issues was closed, it still appears in my environment\nSame here, this happens from time to time in our environments, is there a way to debug to find the root cause?", "commid": "kubernetes_issue_8642", "tokennum": 84}], "negative_passages": []}
{"query_id": "q-en-kubernetes-8f5cd44b3f59397983a613f7b52974af70138af8bee2229e47786a6622258d93", "query": "}, { manifest: KubeProxyDaemonSet, <del> data: struct{ ImageRepository, Arch, Version, ImageOverride, ClusterCIDR, MasterTaintKey, CloudTaintKey string }{ </del> <ins> data: struct{ ImageRepository, Arch, Version, ImageOverride, ExtraParams, ClusterCIDR, MasterTaintKey, CloudTaintKey string }{ </ins> ImageRepository: \"foo\", Arch:            \"foo\", Version:         \"foo\", ImageOverride:   \"foo\", <ins> ExtraParams:     \"foo\", </ins> ClusterCIDR:     \"foo\", MasterTaintKey:  \"foo\", CloudTaintKey:   \"foo\",", "positive_passages": [{"docid": "doc-en-kubernetes-fdf6c8e5598e80992f62cef52eca112e7ba1d532fe8ace89dc932a5edac53dea", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: Currently, IPVS proxier does not run any e2e test cases. What you expected to happen: I think it's important to create test suite for IPVS in upstream CI which will help a lot in moving IPVS existing alpha. Anything else we need to know?: Let's work together. /sig network\nSelf /assign\nThere are to ways to do this work: , but doesn't support any kube-proxy config right now, so I had this pr , and also, need support it too, see this pr: kubernetes/kubernetes-anywhere build cluster. See this pr: kubernetes/test-infra The second way is much easier and faster, but I was told they gonna deprecated the , so in the long term, we still need and 's support. If anybody have better way or have some suggestion about this, please let me know, I'll be really appreciate, Thanks.", "commid": "kubernetes_issue_52834", "tokennum": 247}], "negative_passages": []}
{"query_id": "q-en-kubernetes-901be35611ea647ab9219a5e31219d67c30015a3d7719610b2a2a92576023f3c", "query": "Description string `json:\"description,omitempty\"` // Versions are versions for this third party object <del> // +optional </del> Versions []APIVersion `json:\"versions,omitempty\"` }", "positive_passages": [{"docid": "doc-en-kubernetes-65858ef6270e846dbad645a3cdb03be72308acbcbd2d437380bbe522248f5825", "text": "FYI. Currently the field of TPR is marked as which is wrong, actually if you try to create a TPR with empty versions, it will cause api server panic. Versions should be necessary field of TPR, we should validate this somehow.", "commid": "kubernetes_issue_36991", "tokennum": 52}], "negative_passages": []}
{"query_id": "q-en-kubernetes-901fe3681178dda850bc11d4c95b7a4c4310c7f22d77c15a45204107c812ab80", "query": "nodeTime = time.Now() bootTime, err = util.GetBootTime() <del> gomega.Expect(err).To(gomega.BeNil()) </del> <ins> framework.ExpectNoError(err) </ins> // Set lookback duration longer than node up time. // Assume the test won't take more than 1 hour, in fact it usually only takes 90 seconds.", "positive_passages": [{"docid": "doc-en-kubernetes-4d7af6d1d5d1ba0c7ab59da9ea13925b54c282d46d48402ebb3f5409fd2b1204", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: kubernetes/node-problem-detector/node-problem-detector-ci: ci-npd-e2e-node See the Which test(s) are failing: [] NodeProblemDetector [NodeFeature:NodeProblemDetector] [] SystemLogMonitor should generate node condition and events for corresponding errors Since when has it been failing: Dec 03. was at 19:50 PST, was at 21:51 PST. Testgrid link: https://k8s- Reason for failure: Apparently is the culprit. Anything else we need to know: This is likely caused by some library upgrade. Nothing big.\n/sig node\n/assign\nSeems like the failure is caused by . /cc /cc /cc /cc\n/priority critical-urgent\nThe particular bug I care about has been fixed in . I'm gonna still work on submitting , as the same error should also be affecting a few other tests.", "commid": "kubernetes_issue_85933", "tokennum": 235}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9027c23491064882a52715c7c4ced9e3fc76ab4bbe0a16f366f6f0a7c95a6a66", "query": "genericConfig.DisabledPostStartHooks.Insert(rbacrest.PostStartHookName) } <del> webhookAuthResolver := func(delegate webhookconfig.AuthenticationInfoResolver) webhookconfig.AuthenticationInfoResolver { return webhookconfig.AuthenticationInfoResolverFunc(func(server string) (*rest.Config, error) { if server == \"kubernetes.default.svc\" { return genericConfig.LoopbackClientConfig, nil } ret, err := delegate.ClientConfigFor(server) if err != nil { return nil, err } if proxyTransport != nil && proxyTransport.Dial != nil { ret.Dial = proxyTransport.Dial } return ret, err }) </del> <ins> webhookAuthResolverWrapper := func(delegate webhookconfig.AuthenticationInfoResolver) webhookconfig.AuthenticationInfoResolver { return &webhookconfig.AuthenticationInfoResolverDelegator{ ClientConfigForFunc: func(server string) (*rest.Config, error) { if server == \"kubernetes.default.svc\" { return genericConfig.LoopbackClientConfig, nil } return delegate.ClientConfigFor(server) }, ClientConfigForServiceFunc: func(serviceName, serviceNamespace string) (*rest.Config, error) { if serviceName == \"kubernetes\" && serviceNamespace == \"default\" { return genericConfig.LoopbackClientConfig, nil } ret, err := delegate.ClientConfigForService(serviceName, serviceNamespace) if err != nil { return nil, err } if proxyTransport != nil && proxyTransport.Dial != nil { ret.Dial = proxyTransport.Dial } return ret, err }, } </ins> } pluginInitializers, err := BuildAdmissionPluginInitializers( s, client, sharedInformers, serviceResolver, <del> webhookAuthResolver, </del> <ins> webhookAuthResolverWrapper, </ins> ) if err != nil { return nil, nil, nil, nil, nil, fmt.Errorf(\"failed to create admission plugin initializer: %v\", err)", "positive_passages": [{"docid": "doc-en-kubernetes-73496a383d34eb1ab5962a20be4dce66952c6d20058c4ff89ce94afc1cb5683d", "text": "We are getting the following error when the apiserver connects the webhook on localhost (configured via URL). We should only use the SSL tunnel for the connections to nodes when the webhooks are running as services. /sig api-machinery /kind bug /assign\n/close", "commid": "kubernetes_issue_58779", "tokennum": 64}], "negative_passages": []}
{"query_id": "q-en-kubernetes-90280c2e8dddfd4a483193840427cd08f1a4ac75473d05f84e7ebfb71537f47b", "query": "// recent start error or not, State should be Terminated, LastTerminationState should be retrieved from second latest // terminated status. { <del> []api.Container{{Name: \"without-reason\"}, {Name: \"with-reason\"}}, []*kubecontainer.ContainerStatus{ </del> <ins> containers: []api.Container{{Name: \"without-reason\"}, {Name: \"with-reason\"}}, statuses: []*kubecontainer.ContainerStatus{ </ins> { Name:     \"without-reason\", State:    kubecontainer.ContainerStateExited,", "positive_passages": [{"docid": "doc-en-kubernetes-b4459e221a04f6723f7b97c6a9d43d61c0d65417b08d143223c7057699636055", "text": "is this a Node bug? cc as next oncall to follow up on this.\nThis is a node bug due to init containers\nI may need help debugging - I see:\nSo I think the problem is in the error case - we're not properly recording that the start failed, and the next time we come in we somehow think the first container succeeded. I'll add some debugging to see if we can't recreate it.\nLet's discuss on instead.", "commid": "kubernetes_issue_25879", "tokennum": 102}], "negative_passages": []}
{"query_id": "q-en-kubernetes-90280c2e8dddfd4a483193840427cd08f1a4ac75473d05f84e7ebfb71537f47b", "query": "// recent start error or not, State should be Terminated, LastTerminationState should be retrieved from second latest // terminated status. { <del> []api.Container{{Name: \"without-reason\"}, {Name: \"with-reason\"}}, []*kubecontainer.ContainerStatus{ </del> <ins> containers: []api.Container{{Name: \"without-reason\"}, {Name: \"with-reason\"}}, statuses: []*kubecontainer.ContainerStatus{ </ins> { Name:     \"without-reason\", State:    kubecontainer.ContainerStateExited,", "positive_passages": [{"docid": "doc-en-kubernetes-dcc88d1d89328d1da3366de828afcd8ab0373228cc4437ea655e2cda79030f86", "text": "Kubelet issues a docker inspect call after creating a container, but for very short lived containers there is a window in which they could exit before being inspected in the docker manager. If the container PID is 0, we should check the ExitCode and other relevant fields and handle them appropriately. [1] This is the suspected cause of several flakes: /cc\nlooking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: I'd expect the second one to not have run in this case? Node logs:\nInit containers have an implicit assumption that container statuses include results of previous SyncPod invocations. If that's not the case we may need to fix that (or at least mitigate it). On May 18, 2016, at 8:28 PM, Prashanth B wrote: looking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: May 18 15:58:33.380: INFO: pod-init--1d4b-11e6-80a4- started at 2016-05-18T15:58:04-07:00 (2+1 container statuses recorded) May 18 15:58:33.380: INFO: Init container init1 ready: false, restart count 0 May 18 15:58:33.380: INFO: Init container init2 ready: true, restart count 0 I'd expect the second one to not have run in this case? Node logs: \u2014 You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub\nThis should be true. Is there any evidence that suggests the opposite? only shows conflicting view of whether init1 has run.\nIf the container exits already and it's not an infra container, kubelet should not error out. Although even if it does, I failed to see how this could affect the readiness of the init container without checking the code further.", "commid": "kubernetes_issue_25844", "tokennum": 487}], "negative_passages": []}
{"query_id": "q-en-kubernetes-90280c2e8dddfd4a483193840427cd08f1a4ac75473d05f84e7ebfb71537f47b", "query": "// recent start error or not, State should be Terminated, LastTerminationState should be retrieved from second latest // terminated status. { <del> []api.Container{{Name: \"without-reason\"}, {Name: \"with-reason\"}}, []*kubecontainer.ContainerStatus{ </del> <ins> containers: []api.Container{{Name: \"without-reason\"}, {Name: \"with-reason\"}}, statuses: []*kubecontainer.ContainerStatus{ </ins> { Name:     \"without-reason\", State:    kubecontainer.ContainerStateExited,", "positive_passages": [{"docid": "doc-en-kubernetes-ade5deee53831749acf4a20dbe39f9ef1836656ae43e40b0bb8594efa4e81e92", "text": "Each syncPod invocation, we inspect the list of init container in order looking for lastTerminationState. There could be a bug in that logic, or if we didn't get the full status, we might make a bad decision. When determining which container to run next, we always look for the last init container in the chain that has success, then run the next container (unless the pod is RestartNever). , Yu-Ju Hong wrote:\nSaw this flake again. How do we verify that container status is not lost between syn pods?\n... between calls to syncPods\nThe second sync clearly saw the init1 container, and decided to launch init2. See \"InitContainersToKeep\" in the message below.\ncontainers to keep can include failed containers. , Yu-Ju Hong wrote:\nDiscussed on slack. In summary, the problem has to do with how we convert the kubecontainer.PodStatus to the api.PodStatus. If a container is terminated, the function makes the decisions: the pod restart policy is \"Always\", and there is a \"failure reason\" recorded for the given container, this means the pod worker tried to (re)start the container but failed. Set the state to \"Waiting\" and populate the reason. , the container state is simply \"terminated\". Init containers don't obey the restart policy like regular containers, and the logic will need to be amended to work with them. is working on a PR. In addition to that, kubelet should not error out if a user container exited before it could apply the oom score (which is best effort in this case). fixes that.\nAhh, thanks for digging into the issue. This is the exact the concern I had when I reviewed the initial implementation of init container, which blocks pr for a while. I even asked to help me verify this case, unfortunately we didn't reproduce the issue back then. :-(\nI wish I'd seen the flakes in the runs prior to merge.\nWe didn't notice this until we started running the tests against docker v1.11.1, which is much faster and hit the race condition differently.\nI suppose that's a good thing...\nIt is hard to reproduce this.", "commid": "kubernetes_issue_25844", "tokennum": 482}], "negative_passages": []}
{"query_id": "q-en-kubernetes-90280c2e8dddfd4a483193840427cd08f1a4ac75473d05f84e7ebfb71537f47b", "query": "// recent start error or not, State should be Terminated, LastTerminationState should be retrieved from second latest // terminated status. { <del> []api.Container{{Name: \"without-reason\"}, {Name: \"with-reason\"}}, []*kubecontainer.ContainerStatus{ </del> <ins> containers: []api.Container{{Name: \"without-reason\"}, {Name: \"with-reason\"}}, statuses: []*kubecontainer.ContainerStatus{ </ins> { Name:     \"without-reason\", State:    kubecontainer.ContainerStateExited,", "positive_passages": [{"docid": "doc-en-kubernetes-0814a4e75b48cf2d27d20141c180e04fbc9b55d5398cce31b037f460c93acb1b", "text": "The extra check of last terminated container in your initial code makes me nervous, but we couldn't reproduce it due to that small race windows until we have a faster docker running on the node. :-)\nI got \"Pods should invoke init containers on a RestartAlways pod\" flake (referenced from ): Logs:\nAll the fixes went in. Please reopen this issue if you see any more flakes.", "commid": "kubernetes_issue_25844", "tokennum": 90}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9055a964750ffaba0809bc197fef094c7fffbe95aac76e5a1e654931233e6a4f", "query": "} } <del> func k8sVolume(cfg *kubeadmapi.MasterConfiguration) api.Volume { </del> <ins> func isPkiVolumeMountNeeded() bool { // On some systems were we host-mount /etc/ssl/certs, it is also required to mount /etc/pki. This is needed // due to symlinks pointing from files in /etc/ssl/certs into /etc/pki/ if _, err := os.Stat(\"/etc/pki\"); err == nil { return true } return false } func pkiVolume(cfg *kubeadmapi.MasterConfiguration) api.Volume { </ins> return api.Volume{ Name: \"pki\", VolumeSource: api.VolumeSource{ <ins> // TODO(phase1+) make path configurable HostPath: &api.HostPathVolumeSource{Path: \"/etc/pki\"}, }, } } func pkiVolumeMount() api.VolumeMount { return api.VolumeMount{ Name:      \"pki\", MountPath: \"/etc/pki\", } } func k8sVolume(cfg *kubeadmapi.MasterConfiguration) api.Volume { return api.Volume{ Name: \"k8s\", VolumeSource: api.VolumeSource{ </ins> HostPath: &api.HostPathVolumeSource{Path: kubeadmapi.GlobalEnvParams.KubernetesDir}, }, }", "positive_passages": [{"docid": "doc-en-kubernetes-aa0efe62d493b3611250d6c4d1b34c71d8fe0e732e78e4445af443d5c2b2f03c", "text": "<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.--What keywords did you search in Kubernetes issues before filing this one? controller /etc/ssl/certs kubeadm /etc/ssl/certs Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT <!-- If this is a BUG REPORT, please: Fill in as much of the template below as you can. If you leave out information, we can't help you as well. If this is a FEATURE REQUEST, please: Describe in detail the feature/behavior/change you'd like to see. In both cases, be ready for followup questions, and please respond in a timely manner. If we can't reproduce a bug or think a feature already exists, we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why. --Kubernetes version (use ): 5 custom built master I also use a custom built hyperkube image instead of the single app images for apiserver, controller, ... Environment: Cloud provider or hardware configuration: azure OS (e.g. from /etc/os-release): CentOS 7.2 Kernel (e.g. ): Linux ma-kub8ms0 3.10.0-327.36.3.el7.x8664 SMP Mon Oct 24 16:09:20 UTC 2016 x8664 x8664 x8664 GNU/Linux Install tools: kubeadm Others: deployed with Azure RM template and ansible What happened: controller is not able to do https, including calls to the Azure RM API What you expected to happen: https should work as usual How to reproduce it (as minimally and precisely as possible): Use kubeadm to install kubernetes on CentOS exec into the controller and try \"curl \" Anything else do we need to know: It looks like caused this issue. On CentOS, I see these files on the host OS: I suspect the symlinks to /etc/pki/... being the problem here, as they are not available inside the hyperkube Debian image. I also tried to verify this with It seems to not be based on Debian and thus gives a different error: I see 2 possible solutions: of host mounting /etc/ssl/certs into the controller pod, the ca certificates could be installed into the image.", "commid": "kubernetes_issue_36150", "tokennum": 529}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9055a964750ffaba0809bc197fef094c7fffbe95aac76e5a1e654931233e6a4f", "query": "} } <del> func k8sVolume(cfg *kubeadmapi.MasterConfiguration) api.Volume { </del> <ins> func isPkiVolumeMountNeeded() bool { // On some systems were we host-mount /etc/ssl/certs, it is also required to mount /etc/pki. This is needed // due to symlinks pointing from files in /etc/ssl/certs into /etc/pki/ if _, err := os.Stat(\"/etc/pki\"); err == nil { return true } return false } func pkiVolume(cfg *kubeadmapi.MasterConfiguration) api.Volume { </ins> return api.Volume{ Name: \"pki\", VolumeSource: api.VolumeSource{ <ins> // TODO(phase1+) make path configurable HostPath: &api.HostPathVolumeSource{Path: \"/etc/pki\"}, }, } } func pkiVolumeMount() api.VolumeMount { return api.VolumeMount{ Name:      \"pki\", MountPath: \"/etc/pki\", } } func k8sVolume(cfg *kubeadmapi.MasterConfiguration) api.Volume { return api.Volume{ Name: \"k8s\", VolumeSource: api.VolumeSource{ </ins> HostPath: &api.HostPathVolumeSource{Path: kubeadmapi.GlobalEnvParams.KubernetesDir}, }, }", "positive_passages": [{"docid": "doc-en-kubernetes-41c6565c36e0283a9e2054713b809a870281386c810e77c1faf5476befe20dbf", "text": "This is already done for hyperkube and would work out of the box when the host mount would be omitted. could try to figure out if /etc/pki should also be host mounted and add this to the controller manifest if required. I'd be happy to provide a fix by myself, I just need to know which solution you would prefer.\nSame problem seems to apply to the apiserver. Not sure however if it actually does https calls.\nimplements solution 2.\nThis issue was moved to kubernetes/kubeadm", "commid": "kubernetes_issue_36150", "tokennum": 111}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9096211cf39ca4e83d703d5a0298032a402b8a9bcc2c1a13fd5a866c10a3eaa9", "query": "Namespace: pod.Namespace, } tests := []struct { <del> containers                   []api.Container statuses                     []*kubecontainer.ContainerStatus reasons                      map[string]error oldStatuses                  []api.ContainerStatus expectedState                map[string]api.ContainerState </del> <ins> containers    []api.Container statuses      []*kubecontainer.ContainerStatus reasons       map[string]error oldStatuses   []api.ContainerStatus expectedState map[string]api.ContainerState // Only set expectedInitState when it is different from expectedState expectedInitState            map[string]api.ContainerState </ins> expectedLastTerminationState map[string]api.ContainerState }{ // For container with no historical record, State should be Waiting, LastTerminationState should be retrieved from // old status from apiserver. { <del> []api.Container{{Name: \"without-old-record\"}, {Name: \"with-old-record\"}}, []*kubecontainer.ContainerStatus{}, map[string]error{}, []api.ContainerStatus{{ </del> <ins> containers: []api.Container{{Name: \"without-old-record\"}, {Name: \"with-old-record\"}}, statuses:   []*kubecontainer.ContainerStatus{}, reasons:    map[string]error{}, oldStatuses: []api.ContainerStatus{{ </ins> Name:                 \"with-old-record\", LastTerminationState: api.ContainerState{Terminated: &api.ContainerStateTerminated{}}, }}, <del> map[string]api.ContainerState{ </del> <ins> expectedState: map[string]api.ContainerState{ </ins> \"without-old-record\": {Waiting: &api.ContainerStateWaiting{ Reason: startWaitingReason, }},", "positive_passages": [{"docid": "doc-en-kubernetes-b4459e221a04f6723f7b97c6a9d43d61c0d65417b08d143223c7057699636055", "text": "is this a Node bug? cc as next oncall to follow up on this.\nThis is a node bug due to init containers\nI may need help debugging - I see:\nSo I think the problem is in the error case - we're not properly recording that the start failed, and the next time we come in we somehow think the first container succeeded. I'll add some debugging to see if we can't recreate it.\nLet's discuss on instead.", "commid": "kubernetes_issue_25879", "tokennum": 102}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9096211cf39ca4e83d703d5a0298032a402b8a9bcc2c1a13fd5a866c10a3eaa9", "query": "Namespace: pod.Namespace, } tests := []struct { <del> containers                   []api.Container statuses                     []*kubecontainer.ContainerStatus reasons                      map[string]error oldStatuses                  []api.ContainerStatus expectedState                map[string]api.ContainerState </del> <ins> containers    []api.Container statuses      []*kubecontainer.ContainerStatus reasons       map[string]error oldStatuses   []api.ContainerStatus expectedState map[string]api.ContainerState // Only set expectedInitState when it is different from expectedState expectedInitState            map[string]api.ContainerState </ins> expectedLastTerminationState map[string]api.ContainerState }{ // For container with no historical record, State should be Waiting, LastTerminationState should be retrieved from // old status from apiserver. { <del> []api.Container{{Name: \"without-old-record\"}, {Name: \"with-old-record\"}}, []*kubecontainer.ContainerStatus{}, map[string]error{}, []api.ContainerStatus{{ </del> <ins> containers: []api.Container{{Name: \"without-old-record\"}, {Name: \"with-old-record\"}}, statuses:   []*kubecontainer.ContainerStatus{}, reasons:    map[string]error{}, oldStatuses: []api.ContainerStatus{{ </ins> Name:                 \"with-old-record\", LastTerminationState: api.ContainerState{Terminated: &api.ContainerStateTerminated{}}, }}, <del> map[string]api.ContainerState{ </del> <ins> expectedState: map[string]api.ContainerState{ </ins> \"without-old-record\": {Waiting: &api.ContainerStateWaiting{ Reason: startWaitingReason, }},", "positive_passages": [{"docid": "doc-en-kubernetes-dcc88d1d89328d1da3366de828afcd8ab0373228cc4437ea655e2cda79030f86", "text": "Kubelet issues a docker inspect call after creating a container, but for very short lived containers there is a window in which they could exit before being inspected in the docker manager. If the container PID is 0, we should check the ExitCode and other relevant fields and handle them appropriately. [1] This is the suspected cause of several flakes: /cc\nlooking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: I'd expect the second one to not have run in this case? Node logs:\nInit containers have an implicit assumption that container statuses include results of previous SyncPod invocations. If that's not the case we may need to fix that (or at least mitigate it). On May 18, 2016, at 8:28 PM, Prashanth B wrote: looking at the logs 2 weird things: race described second container ran, which suggests inconsistent reporting of initialized status of init1 and choosing init2 as the next container ( vs ). I think 1 got it right and 2 got it wrong. From logs: May 18 15:58:33.380: INFO: pod-init--1d4b-11e6-80a4- started at 2016-05-18T15:58:04-07:00 (2+1 container statuses recorded) May 18 15:58:33.380: INFO: Init container init1 ready: false, restart count 0 May 18 15:58:33.380: INFO: Init container init2 ready: true, restart count 0 I'd expect the second one to not have run in this case? Node logs: \u2014 You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub\nThis should be true. Is there any evidence that suggests the opposite? only shows conflicting view of whether init1 has run.\nIf the container exits already and it's not an infra container, kubelet should not error out. Although even if it does, I failed to see how this could affect the readiness of the init container without checking the code further.", "commid": "kubernetes_issue_25844", "tokennum": 487}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9096211cf39ca4e83d703d5a0298032a402b8a9bcc2c1a13fd5a866c10a3eaa9", "query": "Namespace: pod.Namespace, } tests := []struct { <del> containers                   []api.Container statuses                     []*kubecontainer.ContainerStatus reasons                      map[string]error oldStatuses                  []api.ContainerStatus expectedState                map[string]api.ContainerState </del> <ins> containers    []api.Container statuses      []*kubecontainer.ContainerStatus reasons       map[string]error oldStatuses   []api.ContainerStatus expectedState map[string]api.ContainerState // Only set expectedInitState when it is different from expectedState expectedInitState            map[string]api.ContainerState </ins> expectedLastTerminationState map[string]api.ContainerState }{ // For container with no historical record, State should be Waiting, LastTerminationState should be retrieved from // old status from apiserver. { <del> []api.Container{{Name: \"without-old-record\"}, {Name: \"with-old-record\"}}, []*kubecontainer.ContainerStatus{}, map[string]error{}, []api.ContainerStatus{{ </del> <ins> containers: []api.Container{{Name: \"without-old-record\"}, {Name: \"with-old-record\"}}, statuses:   []*kubecontainer.ContainerStatus{}, reasons:    map[string]error{}, oldStatuses: []api.ContainerStatus{{ </ins> Name:                 \"with-old-record\", LastTerminationState: api.ContainerState{Terminated: &api.ContainerStateTerminated{}}, }}, <del> map[string]api.ContainerState{ </del> <ins> expectedState: map[string]api.ContainerState{ </ins> \"without-old-record\": {Waiting: &api.ContainerStateWaiting{ Reason: startWaitingReason, }},", "positive_passages": [{"docid": "doc-en-kubernetes-ade5deee53831749acf4a20dbe39f9ef1836656ae43e40b0bb8594efa4e81e92", "text": "Each syncPod invocation, we inspect the list of init container in order looking for lastTerminationState. There could be a bug in that logic, or if we didn't get the full status, we might make a bad decision. When determining which container to run next, we always look for the last init container in the chain that has success, then run the next container (unless the pod is RestartNever). , Yu-Ju Hong wrote:\nSaw this flake again. How do we verify that container status is not lost between syn pods?\n... between calls to syncPods\nThe second sync clearly saw the init1 container, and decided to launch init2. See \"InitContainersToKeep\" in the message below.\ncontainers to keep can include failed containers. , Yu-Ju Hong wrote:\nDiscussed on slack. In summary, the problem has to do with how we convert the kubecontainer.PodStatus to the api.PodStatus. If a container is terminated, the function makes the decisions: the pod restart policy is \"Always\", and there is a \"failure reason\" recorded for the given container, this means the pod worker tried to (re)start the container but failed. Set the state to \"Waiting\" and populate the reason. , the container state is simply \"terminated\". Init containers don't obey the restart policy like regular containers, and the logic will need to be amended to work with them. is working on a PR. In addition to that, kubelet should not error out if a user container exited before it could apply the oom score (which is best effort in this case). fixes that.\nAhh, thanks for digging into the issue. This is the exact the concern I had when I reviewed the initial implementation of init container, which blocks pr for a while. I even asked to help me verify this case, unfortunately we didn't reproduce the issue back then. :-(\nI wish I'd seen the flakes in the runs prior to merge.\nWe didn't notice this until we started running the tests against docker v1.11.1, which is much faster and hit the race condition differently.\nI suppose that's a good thing...\nIt is hard to reproduce this.", "commid": "kubernetes_issue_25844", "tokennum": 482}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9096211cf39ca4e83d703d5a0298032a402b8a9bcc2c1a13fd5a866c10a3eaa9", "query": "Namespace: pod.Namespace, } tests := []struct { <del> containers                   []api.Container statuses                     []*kubecontainer.ContainerStatus reasons                      map[string]error oldStatuses                  []api.ContainerStatus expectedState                map[string]api.ContainerState </del> <ins> containers    []api.Container statuses      []*kubecontainer.ContainerStatus reasons       map[string]error oldStatuses   []api.ContainerStatus expectedState map[string]api.ContainerState // Only set expectedInitState when it is different from expectedState expectedInitState            map[string]api.ContainerState </ins> expectedLastTerminationState map[string]api.ContainerState }{ // For container with no historical record, State should be Waiting, LastTerminationState should be retrieved from // old status from apiserver. { <del> []api.Container{{Name: \"without-old-record\"}, {Name: \"with-old-record\"}}, []*kubecontainer.ContainerStatus{}, map[string]error{}, []api.ContainerStatus{{ </del> <ins> containers: []api.Container{{Name: \"without-old-record\"}, {Name: \"with-old-record\"}}, statuses:   []*kubecontainer.ContainerStatus{}, reasons:    map[string]error{}, oldStatuses: []api.ContainerStatus{{ </ins> Name:                 \"with-old-record\", LastTerminationState: api.ContainerState{Terminated: &api.ContainerStateTerminated{}}, }}, <del> map[string]api.ContainerState{ </del> <ins> expectedState: map[string]api.ContainerState{ </ins> \"without-old-record\": {Waiting: &api.ContainerStateWaiting{ Reason: startWaitingReason, }},", "positive_passages": [{"docid": "doc-en-kubernetes-0814a4e75b48cf2d27d20141c180e04fbc9b55d5398cce31b037f460c93acb1b", "text": "The extra check of last terminated container in your initial code makes me nervous, but we couldn't reproduce it due to that small race windows until we have a faster docker running on the node. :-)\nI got \"Pods should invoke init containers on a RestartAlways pod\" flake (referenced from ): Logs:\nAll the fixes went in. Please reopen this issue if you see any more flakes.", "commid": "kubernetes_issue_25844", "tokennum": 90}], "negative_passages": []}
{"query_id": "q-en-kubernetes-90d75b92aebc087d99c19766369daecf20c8f367c33cfba375452fd2b82b356d", "query": "rs := &apps.ReplicaSet{} rc := &api.ReplicationController{} <ins> extGroup := schema.GroupVersion{Group: \"apps\", Version: \"v1\"} extCodec := legacyscheme.Codecs.LegacyCodec(extGroup) </ins> <del> extGroup := testapi.Apps defaultGroup := testapi.Default </del> <ins> defaultGroup := schema.GroupVersion{Group: \"\", Version: \"v1\"} defaultCodec := legacyscheme.Codecs.LegacyCodec(defaultGroup) </ins> fuzzInternalObject(t, schema.GroupVersion{Group: \"apps\", Version: runtime.APIVersionInternal}, rs, rand.Int63())", "positive_passages": [{"docid": "doc-en-kubernetes-fe4a53f9c12ffb58184de5c048a5217a0a9a95660f59883741a14147feb2210e", "text": "Execute make test WHAT=./pkg/api/testing/ And it failed with information: /kind failing-test\n/sig api-machinery\nwhat's the urgency of fixing this? Is it a release blocker?\ni don't see it as a release blocker. but the problem is in client-go, so it's important to get fixed.", "commid": "kubernetes_issue_71369", "tokennum": 78}], "negative_passages": []}
{"query_id": "q-en-kubernetes-90fdc7bf07c3019ef559594aed6e65e7cfc05ad0d43cfd9a2e1a53a2c2df0605", "query": "kubeClient := testKubelet.fakeKubeClient kubeClient.ReactFn = testclient.NewSimpleFake(&api.NodeList{Items: []api.Node{ { <del> ObjectMeta: api.ObjectMeta{Name: \"127.0.0.1\"}, </del> <ins> ObjectMeta: api.ObjectMeta{Name: testKubeletHostname}, </ins> Spec:       api.NodeSpec{}, Status: api.NodeStatus{ Conditions: []api.NodeCondition{", "positive_passages": [{"docid": "doc-en-kubernetes-d16ca614c05197aa8b2652e3bf008c3a9a5ce41d960188a2ba3459b13d8b1102", "text": "Looks like some kubelet unit tests perform a lookupIp which ends up depending on the health of the local resolver. Specifically has this failing: Which leads to the test in: And we recently swapped out the node names from testnode to 127.0.0.1, so probably the culprit?\n/ref\nInteresting. I did swap out the node names in the unit test as part of to be 127.0.0.1, party because I thought that it wouldn't have any problems resolving during unit tests.\n/cc", "commid": "kubernetes_issue_8549", "tokennum": 113}], "negative_passages": []}
{"query_id": "q-en-kubernetes-90fdc7bf07c3019ef559594aed6e65e7cfc05ad0d43cfd9a2e1a53a2c2df0605", "query": "kubeClient := testKubelet.fakeKubeClient kubeClient.ReactFn = testclient.NewSimpleFake(&api.NodeList{Items: []api.Node{ { <del> ObjectMeta: api.ObjectMeta{Name: \"127.0.0.1\"}, </del> <ins> ObjectMeta: api.ObjectMeta{Name: testKubeletHostname}, </ins> Spec:       api.NodeSpec{}, Status: api.NodeStatus{ Conditions: []api.NodeCondition{", "positive_passages": [{"docid": "doc-en-kubernetes-4a4c75dd985aaeba56d487bbde17d68f0425afc5d7e1167fdf1a1abcb97cd0b6", "text": "cc\nWhat is the environment where you are running the tests? They pass for me on my mac, a linux box, and shippable seems to be passing them as well.\nI couldn 't reproduce the failure either.\nI'm out right now; i'll try them when i get back. For the record, I run hack/test- Paul Morie wrote:\nAhem FTR This acronym is going to go quad-plat Paul Morie wrote:\nI ran on both platforms and saw the tests pass.\nI'm still seeing it. Won't have bandwidth to dig in personally until tomorrow.\nseeing a similar failure after a git pull\nI knew I wasn't crazy\nenvironment: fedora 21, golang: 1.4, docker: 1.6\nI think I see the problem. When I set the node name to in the test I was assuming it would parse as a valid ip address and not end up at the LookupIP call. But only the node name (and not the kubelet hostname) is being set (except in my new test where I ) so it's trying to do a lookup. Do you think you could test just changing the default hostname from \"testnode\" to \"127.0.0.1\" and see if that fixes it for you?\nTrying now\nI still get failures but no panic / threaddump.\ngist coming\nthis looks like again?\nGood that it isn't panicing any longer. I can dig into the test failures tomorrow (I think it should be relatively simple to resolve).\ncool, thanks for looking\nPasses in master now for me. Closing.\nFYI, they will break again once goes in, and then we can merge my PR to see if that fixes it for you.\n:+1:\nis in -- are these tests breaking again?\nI just rebased which I think will fix them.\nThey are breaking again.\nis on it.", "commid": "kubernetes_issue_8522", "tokennum": 407}], "negative_passages": []}
{"query_id": "q-en-kubernetes-91174186c4fd8ef29f5dbdf91609014da46d86563a33891124ea09fa5bea1e99", "query": "# # We specify -X to avoid a race condition that can cause minion failure to # install.  See https://github.com/saltstack/salt-bootstrap/issues/270 <del> curl -L http://bootstrap.saltstack.com | sh -s -- -X </del> <ins> curl -L --connect-timeout 20 --retry 6 --retry-delay 10 http://bootstrap.saltstack.com | sh -s -- -X </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-9fcfa37c5fd88e21dae3cf641aefb45ac17c97dc04df9b3a60101bffeb7f8b4c", "text": "Failed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nFailed: https://k8s- Run so broken it didn't make JUnit output!\nthis appears to have always been broken, I'm going to disable the job for now. https://k8s-\nFailed: https://k8s- Run so broken it didn't make JUnit output!", "commid": "kubernetes_issue_34116", "tokennum": 556}], "negative_passages": []}
{"query_id": "q-en-kubernetes-918b309685e171a82b1807300314b0e301fec6fad0f296c355012112aa38f273", "query": "if err := os.MkdirAll(dest, 0o755); err != nil { return err } <del> return utils.WithProcfd(c.root, m.Destination, func(procfd string) error { if err := mount(m.Source, m.Destination, procfd, \"cgroup2\", uintptr(m.Flags), m.Data); err != nil { // when we are in UserNS but CgroupNS is not unshared, we cannot mount cgroup2 (#2158) if errors.Is(err, unix.EPERM) || errors.Is(err, unix.EBUSY) { src := fs2.UnifiedMountpoint if c.cgroupns && c.cgroup2Path != \"\" { // Emulate cgroupns by bind-mounting // the container cgroup path rather than // the whole /sys/fs/cgroup. src = c.cgroup2Path } err = mount(src, m.Destination, procfd, \"\", uintptr(m.Flags)|unix.MS_BIND, \"\") if c.rootlessCgroups && errors.Is(err, unix.ENOENT) { err = nil } } return err } return nil </del> <ins> err = utils.WithProcfd(c.root, m.Destination, func(procfd string) error { return mount(m.Source, m.Destination, procfd, \"cgroup2\", uintptr(m.Flags), m.Data) </ins> }) <ins> if err == nil || !(errors.Is(err, unix.EPERM) || errors.Is(err, unix.EBUSY)) { return err } // When we are in UserNS but CgroupNS is not unshared, we cannot mount // cgroup2 (#2158), so fall back to bind mount. bindM := &configs.Mount{ Device:           \"bind\", Source:           fs2.UnifiedMountpoint, Destination:      m.Destination, Flags:            unix.MS_BIND | m.Flags, PropagationFlags: m.PropagationFlags, } if c.cgroupns && c.cgroup2Path != \"\" { // Emulate cgroupns by bind-mounting the container cgroup path // rather than the whole /sys/fs/cgroup. bindM.Source = c.cgroup2Path } // mountToRootfs() handles remounting for MS_RDONLY. // No need to set c.fd here, because mountToRootfs() calls utils.WithProcfd() by itself in mountPropagate(). err = mountToRootfs(bindM, c) if c.rootlessCgroups && errors.Is(err, unix.ENOENT) { // ENOENT (for `src = c.cgroup2Path`) happens when rootless runc is being executed // outside the userns+mountns. // // Mask `/sys/fs/cgroup` to ensure it is read-only, even when `/sys` is mounted // with `rbind,ro` (`runc spec --rootless` produces `rbind,ro` for `/sys`). err = utils.WithProcfd(c.root, m.Destination, func(procfd string) error { return maskPath(procfd, c.label) }) } return err </ins> } func doTmpfsCopyUp(m *configs.Mount, rootfs, mountLabel string) (Err error) {", "positive_passages": [{"docid": "doc-en-kubernetes-3a5f1791fd28a186fcf23c773fa97525e98fb83cc70e7098ac61d449614dcefb", "text": "opencontainers/runc has fixed three CVEs: Latest runc is pulled by k/k Check runc version in file No response n/a n/a <details</details<details</details<details</details<details</details\n/assign /sig security architecture release\n/triage accepted", "commid": "kubernetes_issue_117094", "tokennum": 68}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9193350c46f90fcba863fe730753ca88a2c7e627b9f6e798745899178328a0f9", "query": "import ( \"fmt\" <del> \"k8s.io/kubernetes/pkg/api\" </del> \"k8s.io/kubernetes/pkg/api/v1\" \"k8s.io/kubernetes/pkg/runtime\" )", "positive_passages": [{"docid": "doc-en-kubernetes-5056a2515a29befdf589a74f13db031ed4142bbabfa8d2c37cafac2de4fccaea", "text": "I started the federation-apiserver and went to and got the following output: Expected: I should have got an empty v1.ServiceList Any idea on what we are doing wrong? Have you guys seen this error?\nI think your deep copiers or conversion functions are not getting registered properly. If you look at my change in , some places are inappropriately registering with api.Scheme instead of the passed in scheme. Maybe you have that problem or a similar one, since I think you guys copied some code. , Nikhil Jindal wrote:\nDeep copy generation was slightly broken as well - you may want to double check that they are registered. On May 23, 2016, at 5:50 PM, Daniel Smith wrote: I think your deep copiers or conversion functions are not getting registered properly. If you look at my change in , some places are inappropriately registering with api.Scheme instead of the passed in scheme. Maybe you have that problem or a similar one, since I think you guys copied some code. , Nikhil Jindal wrote: \u2014 You are receiving this because you are on a team that was mentioned. Reply to this email directly or view it on GitHub\nI got the same error with latest branch, as I was swamping on service controller, so I use a previous version and worked around it.\ndeep copies were indeed missing, but adding them hasnt fixed the issue. Will debug more. is my PR to add the deep copies cc Please feel free to file issues for any such problem you face. We need to fix all these issues. Its good if we know about them early. Thanks!\nfixes this", "commid": "kubernetes_issue_26111", "tokennum": 335}], "negative_passages": []}
{"query_id": "q-en-kubernetes-919fd37fcf804ff8c704ca14d4a4ab403bab771779c38d5cc67e21eb1f9a483c", "query": "framework.ExpectNoError(framework.VerifyServeHostnameServiceUp(cs, ns, host, podNames1, svc1IP, servicePort)) // Restart apiserver <del> initialRestartCount, err := framework.GetApiserverRestartCount(cs) Expect(err).NotTo(HaveOccurred(), \"failed to get apiserver's restart count\") </del> By(\"Restarting apiserver\") <del> if err := framework.RestartApiserver(cs.Discovery()); err != nil { </del> <ins> if err := framework.RestartApiserver(cs); err != nil { </ins> framework.Failf(\"error restarting apiserver: %v\", err) } <del> By(\"Waiting for apiserver to be restarted\") if err := framework.WaitForApiserverRestarted(cs, initialRestartCount); err != nil { framework.Failf(\"error while waiting for apiserver to be restarted: %v\", err) } </del> By(\"Waiting for apiserver to come up by polling /healthz\") if err := framework.WaitForApiserverUp(cs); err != nil { framework.Failf(\"error while waiting for apiserver up: %v\", err)", "positive_passages": [{"docid": "doc-en-kubernetes-45049cecee14166a5520f4dc4cbecae5a5a4a44f20c23557ee81cd45d6979f23", "text": "This test is failing in both gce serial suite: http://k8s- /sig network /priority failing-test /priority critical-urgent /kind bug /status approved-for-milestone cc /assign PTAL\nxref\n/milestone v1.10\nthis also fails in http://k8s-\nFailing to connect to Services at all. I can't even ping pod IPs:\nSo I can ping pods same-node and cross-node right up until it kills the apiserver. Rebooting fixes a given node. The apiserver demonstrably comes back - I can query it for info...\n- I could use help - have to shift attention soon.\nFWIW, I am testing on a Calico-enabled node\nI'll take a look at this as well.\nWeird, now even after a reboot, this condition is sticky. I have a cluster in this state, if you want to poke.\nugh, now it is resolved.\nI just repro'ed without the e2e - have a cluster, proved ping works, killed apiserver ping fails.\nInteresting - docker shows the pods not running, but apiserver says they are alive.\nUpdate: docker sees no running pods. API server thinks kubelet is running them. kubelet is getting \"\" from apiserver, even after kubelet restart.\nUpdate and recap: Bring up a cluster Run some pods Prove that pods are running and services work pkill -9 apiserver Wait. Watch kubelets \"lose\" pods that were assigned to them Observe that pods are not running and services do not work Observe that apiserver says the pods are running pkill -9 kubelet Observe that it is still broken kubectl delete one pod Observe that kubelet is fixed for that one pod, but not others Q: Why is kubelet not getting a full listing when it restarts?\nWhat exactly does it mean for it to be fixed for a deleted pod?\nKubelet started running the pod that was deleted - it got the update for that one.\nThe cluster I was testing was a week or 2 old. I built a cluster from HEAD and I can not repro - said the same. Is this test running against head of master?\nI also ran the test manually against my new cluster and it passed\nFWIW I was also unable to reproduce this yesterday on a cluster from HEAD.", "commid": "kubernetes_issue_60761", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-919fd37fcf804ff8c704ca14d4a4ab403bab771779c38d5cc67e21eb1f9a483c", "query": "framework.ExpectNoError(framework.VerifyServeHostnameServiceUp(cs, ns, host, podNames1, svc1IP, servicePort)) // Restart apiserver <del> initialRestartCount, err := framework.GetApiserverRestartCount(cs) Expect(err).NotTo(HaveOccurred(), \"failed to get apiserver's restart count\") </del> By(\"Restarting apiserver\") <del> if err := framework.RestartApiserver(cs.Discovery()); err != nil { </del> <ins> if err := framework.RestartApiserver(cs); err != nil { </ins> framework.Failf(\"error restarting apiserver: %v\", err) } <del> By(\"Waiting for apiserver to be restarted\") if err := framework.WaitForApiserverRestarted(cs, initialRestartCount); err != nil { framework.Failf(\"error while waiting for apiserver to be restarted: %v\", err) } </del> By(\"Waiting for apiserver to come up by polling /healthz\") if err := framework.WaitForApiserverUp(cs); err != nil { framework.Failf(\"error while waiting for apiserver up: %v\", err)", "positive_passages": [{"docid": "doc-en-kubernetes-a335c4245d7a15c6e680ffd06bca4d469bc98515fa6a43286dbf7f7a3bfccc88", "text": "Did some investigations and had some findings for this specific failure: Traced down a bit on the history, the first occurrence was https://k8s- From the , seems suspicious because it modified . Also found reported a relevant symptom: The fix () for that was merged a day ago and may explained why we can't repro from HEAD anymore.\nnice, is this issue reproducible without the fix ()?\nSorry should have had confirmed this, bringing up a cluster now.\nQuick update: I was able to repro the same failure () from HEAD with reverted. Though this test is now flaky on some other errors: https://k8s- https://k8s- They all seem to failed while communicating with apiserver.\nThanks ! So fixed the issue and I am curious about what introduced the issue. Do you happen to know when did this test start to fail? Just trying to find out what went wrong in between. We have some other possibly related issues so finding out the root cause of this one would be super helpful.\n/assign\nThe first occurrence (for that exact failure) I noticed was https://k8s-, which happened on 2018-02-15 09:49 PST.\nYou all rock! I see a couple greens on it now, but still mostly red?\nThe test is now flaky mostly on creating an exec pod after restarting apiserver. Some sample failures: To elaborate a bit more, a snippet of the test procedure is: ssh to master and (sending a SIGTERM) Keep polling on /healthz on apiserver until 200 is returned. Create an exec pod for later steps (and failed on various erros --- EOF, connection refused, apiserver terminating). According to above test failures, my suspicion is that the test is assuming the apiserver is restarted too soon. It is possible that apiserver captured SIGTERM and did a graceful termination, so that polling on /healthz may succeed even in the termination phase. I'm not surprised trying to create a pod via a terminating apiserver will hit those errors. Could anyone confirme the SIGTERM theory?\nSpoke with folks, sounds like after SIGTERM apiserver does wait a bit for remaining requests to finish. I will take a stab to refine the test. cc\nSent .\nTest is now passing on gce but failing on gke.", "commid": "kubernetes_issue_60761", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-919fd37fcf804ff8c704ca14d4a4ab403bab771779c38d5cc67e21eb1f9a483c", "query": "framework.ExpectNoError(framework.VerifyServeHostnameServiceUp(cs, ns, host, podNames1, svc1IP, servicePort)) // Restart apiserver <del> initialRestartCount, err := framework.GetApiserverRestartCount(cs) Expect(err).NotTo(HaveOccurred(), \"failed to get apiserver's restart count\") </del> By(\"Restarting apiserver\") <del> if err := framework.RestartApiserver(cs.Discovery()); err != nil { </del> <ins> if err := framework.RestartApiserver(cs); err != nil { </ins> framework.Failf(\"error restarting apiserver: %v\", err) } <del> By(\"Waiting for apiserver to be restarted\") if err := framework.WaitForApiserverRestarted(cs, initialRestartCount); err != nil { framework.Failf(\"error while waiting for apiserver to be restarted: %v\", err) } </del> By(\"Waiting for apiserver to come up by polling /healthz\") if err := framework.WaitForApiserverUp(cs); err != nil { framework.Failf(\"error while waiting for apiserver up: %v\", err)", "positive_passages": [{"docid": "doc-en-kubernetes-937105a0fb62d0b30f0dcf82865ffcd7dde374c2d2e0895384450ffe72527abd", "text": "Apparently we don't have a way to trigger apiserver restart on gke at this moment. Sending a PR to skip this test on gke.\n[MILESTONENOTIFIER] Milestone Issue Needs Attention Action required: During code freeze, issues in the milestone should be in progress. If this issue is not being actively worked on, please remove it from the milestone. If it is being worked on, please add the label so it can be tracked with other in-flight issues. Note: This issue is marked as , and must be updated every 1 day during code freeze. Example update: <details<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Never automatically move issue out of a release milestone; continually escalate to contributor and SIG through all available channels. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details\nCommented too quick. On gke we do a same-version master upgrade. Will send another fix :/", "commid": "kubernetes_issue_60761", "tokennum": 256}], "negative_passages": []}
{"query_id": "q-en-kubernetes-91a3199cc3708fdd3890213945390c771560de5ff310d38c5cec64990b0e9e55", "query": "serviceHasSynced cache.InformerSynced // nodeLister knows how to list nodes nodeLister corelisters.NodeLister <ins> // nodeHasSynced indicates whether nodes have been sync'd at least once. // Check this before trusting a response from the node lister. nodeHasSynced cache.InformerSynced </ins> // a list of node labels to register nodeLabels map[string]string", "positive_passages": [{"docid": "doc-en-kubernetes-8476bba8e23a7ed885cd34c1077ce17dbf12901ac7ae9725333264f6ea8cfdae", "text": "What happened: A deployment is created that uses a after the cluster master is created but before the cluster worker nodes are fully initialized. During the initialization of the worker nodes, the nodes are temporarily available for scheduling without the necessary label to match the deployment's node selector. Depending on how long the nodes are available for scheduling without the necessary node labels for the deployment, the scheduler will start to spam with cluster with pods in status. This spamming stops once the worker nodes are fully initialized and the pods are scheduled successful. The exact timing of all of this is TBD. What you expected to happen: Pods in status are annoying and require manual cleanup. It would be preferred that the scheduler avoid this an simply issue warning events. How to reproduce it (as minimally and precisely as possible): See issue description. Anything else we need to know?: No. Environment: Kubernetes version (use ): 1.18.3 Cloud provider or hardware configuration: IBM Cloud Kubernetes Service OS (e.g: ): Ubuntu 18.04.4 LTS Kernel (e.g. ): 4.15.0-96-generic Install tools: Managed service install Network plugin and version (if this is a network-related bug): N/A Others: N/A\nRelated to and\n/sig scheduling\nby spamming are you referring to scheduler logs? also, why are the nodes not labelled from the get go?\nJust to confirm, all the pods in question are still in Pending state, yes? If the pods are in pending state, all of them will get scheduled eventually once the nodes get their labels.\nThe pods are not in state. They are actually in state. The pods eventually get scheduled but we are left with anywhere from a few to dozens of these state pods. Also, we are looking at labeling the nodes via kubelet flags to see if that helps.\n/remove-kind bug\nAfter we add some retry logic and wait time in this problem can be solved: As you can see this function returns initial node as the first request failed.\nI also get hit by this, when single controller node gets rebooted and scheduler starts as static container before kubelet becomes ready.", "commid": "kubernetes_issue_92067", "tokennum": 465}], "negative_passages": []}
{"query_id": "q-en-kubernetes-91a3199cc3708fdd3890213945390c771560de5ff310d38c5cec64990b0e9e55", "query": "serviceHasSynced cache.InformerSynced // nodeLister knows how to list nodes nodeLister corelisters.NodeLister <ins> // nodeHasSynced indicates whether nodes have been sync'd at least once. // Check this before trusting a response from the node lister. nodeHasSynced cache.InformerSynced </ins> // a list of node labels to register nodeLabels map[string]string", "positive_passages": [{"docid": "doc-en-kubernetes-6c53201dbb91d52a8ade960092a5ed582f4d35e33a53b75d555d15ae815dc25c", "text": "Can be cleaned up with:\n/sig node\nthe spam cycle is this loop: \"pod create, pod schedule, worker reject, pod failed\" -- we don't have a lot of protection in higher level workload controllers to handle pods that fail at kubelet admission time versus pods that just dont create due to quota/admission. in general, is the spam causing any other stability issues? is pod gc pruning the pods?\nI wonder if we can do a trick in node lister to mitigate any race condition here...\nwe could maybe do something similar to to ensure node lister has synced...\nhacking on option to ensure if kubelet has a node lister with a valid kube client, we wait for it to sync at least once here which should mitigate this issue. see:\nWe noticed the problem on the OLM pod which is managed by the OLM operator. Right or wrong, the operator does not like seeing the pod go to status and no longer reconciles the pod. The end result is that manual intervention (i.e. pod deletion) is required to fix the problem.\nsure... i would have thought the pod is failed in that instance and reached a terminal state. either way, i am looking at what i can do to mitigate this.\nThe problem persists in our environment as well, and the workaround cited above will not do anymore. Is there something in the works for this one?\nIssues 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\n/remove-lifecycle stale", "commid": "kubernetes_issue_92067", "tokennum": 383}], "negative_passages": []}
{"query_id": "q-en-kubernetes-91b28e4f471ab497bc1d28bee252a54898e7a67f0bb6a0e7ca4856173670cca1", "query": "echo \"Prepare kube-addons manifests and start kube addon manager\" local -r src_dir=\"${KUBE_HOME}/kube-manifests/kubernetes/gci-trusty\" local -r dst_dir=\"/etc/kubernetes/addons\" <ins> # prep the additional bindings that are particular to e2e users and groups setup-addon-manifests \"addons\" \"e2e-rbac-bindings\" </ins> # Set up manifests of other addons. if [[ \"${ENABLE_CLUSTER_MONITORING:-}\" == \"influxdb\" ]] ||  [[ \"${ENABLE_CLUSTER_MONITORING:-}\" == \"google\" ]] || ", "positive_passages": [{"docid": "doc-en-kubernetes-19a61d82ec14336213ef377c4e39e11807c2ce9673880ce3d82a192d5a783624", "text": "Typically, the dns and dashboard is in crash loop. Ref cc\nif you check the file, does it contain lines like ?\nPrevious comment is ref: from I'll copy that to container-linux as well.", "commid": "kubernetes_issue_39395", "tokennum": 44}], "negative_passages": []}
{"query_id": "q-en-kubernetes-91bbce143c59e6edc9d1cf267df92f82d75647c7c19f32dafdda38daee566e40", "query": "\"context\" \"encoding/json\" \"fmt\" <ins> \"mime\" </ins> \"net/http\" \"net/url\" \"sort\"", "positive_passages": [{"docid": "doc-en-kubernetes-3257ecff81fbc60fa2a8f982346c462089eb7c896f62cce1d4e02ff6df66d913", "text": "We are using (and ) to interact with Kubernetes clusters behind a couple of proxy layers. One of these proxies completes the headers to include character encoding details. This was working fine until recently, when client-go/kubectl have started to fail when interacting with the discovery API. It seems that a recent change has made kubectl more restrictive of the content-type that it expects. I suspect that it is related to this commit: For example, this is an error from a kubectl command: We can of course try to fix it on our end, removing that charset information. However, it is a valid content-type and the way kubectl is handling the content-type there seems like it is relying on implementation details of kube-apiserver (that it does not add metadata to the content-type). I propose to fix this issue in , by properly parsing and handling the content-type.\ncc /kind regression /kind bug /sig api-machinery /priority important-soon looks like the switch statement in downloadLegacy() needs to be more tolerant of the variety of content-types it can get from a server (including text/plain or no content-type if old servers could have returned that...)\n/transfer kubernetes/kubernetes\nSomething went wrong or the destination repo kubernetes/kubernetes/kubernetes does not exist. <detailsIn response to : /transfer kubernetes/kubernetes 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\n/transfer kubernetes\nYep, the string comparison for the content-type is flimsy, let's address that. Thanks for the report!\n/assign\n/triage accepted\n/cc\nThe fix is being cherry-picked back to: : :", "commid": "kubernetes_issue_117562", "tokennum": 408}], "negative_passages": []}
{"query_id": "q-en-kubernetes-91c71d2f57c6688994674e2b0d54365cf384190e1f91904fea33317f3fa521e2", "query": "echo ${short_hash:0:5} } <ins> # Pedantically kill, wait-on and remove a container. The -f -v options # to rm don't actually seem to get the job done, so force kill the # container, wait to ensure it's stopped, then try the remove. This is # a workaround for bug https://github.com/docker/docker/issues/3968. function kube::build::destroy_container() { \"${DOCKER[@]}\" kill \"$1\" >/dev/null 2>&1 || true \"${DOCKER[@]}\" wait \"$1\" >/dev/null 2>&1 || true \"${DOCKER[@]}\" rm -f -v \"$1\" >/dev/null 2>&1 || true } </ins> # --------------------------------------------------------------------------- # Building", "positive_passages": [{"docid": "doc-en-kubernetes-349c839c0314e1386e949c881af8735bbe6497abcf3a15697139e75deb1d1835", "text": "Github automatically adds a artifact to every release, which sounds very similar to the artifact that we generate as the release artifact. Assuming we don't have control over the naming or presence of the autogenerated source code artifact, I think we should consider renaming our published artifact to better disambiguate between the two.\nWe distribute most of our artifacts outside of GitHub. We should probably stop uploading this one entirely.\ncc\nWe've got a thread going on w/ Tim. /assign\ncan you please link so folks can follow the bread crumbs? ( cc )\n-- It's currently sensitive. Will share once there's an outcome.\nACK. thanks for the heads up\nI think it's safe to discuss openly at this point. We had a report that the sha512 hashes on our release artifacts were incorrect. We have confirmed that the mismatch was due to a bug in the release pipeline, and not malicious. This issue here was just a point of confusion that came out of that discussion.\nthanks !\n/assign\nGoing one step back since I think the exists for historical reasons: The client and server binaries were part of this bundle, which is not the case any more: So it seems that is mostly a collection of licenses and scripts. Do we really need it or may we cleanup some code paths and remove it completely?\n+1 to put the word out and remove it completely if no one depends on it.\nI'm not confident that CI is not using these versioned scripts, in fact i'm fairly sure that it is. However it would not be pulling it from github.\nThe 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]:\n/remove-lifecycle stale I think this remains as relevant as ever.\n/milestone v1.23\n/triage accepted\nHi and k8s 1.23 bug triage shadow here.", "commid": "kubernetes_issue_100460", "tokennum": 507}], "negative_passages": []}
{"query_id": "q-en-kubernetes-91c71d2f57c6688994674e2b0d54365cf384190e1f91904fea33317f3fa521e2", "query": "echo ${short_hash:0:5} } <ins> # Pedantically kill, wait-on and remove a container. The -f -v options # to rm don't actually seem to get the job done, so force kill the # container, wait to ensure it's stopped, then try the remove. This is # a workaround for bug https://github.com/docker/docker/issues/3968. function kube::build::destroy_container() { \"${DOCKER[@]}\" kill \"$1\" >/dev/null 2>&1 || true \"${DOCKER[@]}\" wait \"$1\" >/dev/null 2>&1 || true \"${DOCKER[@]}\" rm -f -v \"$1\" >/dev/null 2>&1 || true } </ins> # --------------------------------------------------------------------------- # Building", "positive_passages": [{"docid": "doc-en-kubernetes-dbd15f43daca5c062443bfb889f914327019b692ac2d45e387a4f7451b197946", "text": "There hasn't been any activity or linked PRs for this issue. Just wanted to check in to see if this is still on track for 1.23.\n/milestone v1.24\nHi I am part of the bug triage team for v1.24. We noticed that this issue hasn't been updated for a while. Just wanted to check if there is any work planned that would go into this.\nthis one keeps moving down the milestones. i don't see any activity since november. So kick the can down the road /milestone v1.25\nHi My name Hossein Salahi from Bug-Triage team. I am just checking to ensure if everything is on track for K8s 1.25. Thanks!\nThat's a question for or\nany remarks on that?\nthe release 1.25 bug triage Lead. I'm reaching out to see the status of this issue and if we are still targeting the current release. Also, kindly if you can update the priority so we can track it in the future.\nthis one keeps moving down the milestones yet again!. i don't see any activity since i moved this down the line. So kick the can down the road: /milestone clear (instead of v1.26 as this has been moving down the line for a few releases now)\nThe 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]:\n/remove-lifecycle stale\nWhat's the current status of this issue? Is there anything that we can do to move this forward?\nWe got new conversations going on during Kubecon on whether we should publish our release binaries on GitHub. Given that and I think we should rethink now what we publish on the release pages. I think we should start publishing all binaries for one. It is a common practice everywhere and I think users largely expect them to be there.", "commid": "kubernetes_issue_100460", "tokennum": 505}], "negative_passages": []}
{"query_id": "q-en-kubernetes-91c71d2f57c6688994674e2b0d54365cf384190e1f91904fea33317f3fa521e2", "query": "echo ${short_hash:0:5} } <ins> # Pedantically kill, wait-on and remove a container. The -f -v options # to rm don't actually seem to get the job done, so force kill the # container, wait to ensure it's stopped, then try the remove. This is # a workaround for bug https://github.com/docker/docker/issues/3968. function kube::build::destroy_container() { \"${DOCKER[@]}\" kill \"$1\" >/dev/null 2>&1 || true \"${DOCKER[@]}\" wait \"$1\" >/dev/null 2>&1 || true \"${DOCKER[@]}\" rm -f -v \"$1\" >/dev/null 2>&1 || true } </ins> # --------------------------------------------------------------------------- # Building", "positive_passages": [{"docid": "doc-en-kubernetes-63377ea8eda65aaaac09acc9ed7dd8461429e8729a6daebbb93d9c0997493c68", "text": "let's scope the issue to the actual \"Kubernetes Source Code\" tarball. We can still remove it from what I can see from the discussion.\nI agree with Removing the \"Kubernetes Source Code\" tarball should be as easy as removing this from krel: However, there are a few questions: is it safe to do so? I believe yes, because this \"Kubernetes Source Code\" tarball is pointing to the GCS bucket, and we'll still continue publishing that tarball to the bucket The link is also available in the changelog, so it's easy to find do we need any deprecation period? Considering the above two points, I don't think so. If you folks agree with that, I can go ahead and create a PR to update krel.\nI agree on that, let's drop an additional note on k-dev that others are aware of the change.\n/assign\nUpdate: An announcement to proceed with the removal of the \"Kubernetes Source Code\" artifact has been sent to k-dev: PR to remove this artifact from being published: Removal will go into effect starting the January patch releases.", "commid": "kubernetes_issue_100460", "tokennum": 245}], "negative_passages": []}
{"query_id": "q-en-kubernetes-92107579e54d96400b617b596f54e43e809d8c4aca2e3eed9f48d3018b8306a8", "query": "\"k8s.io/client-go/tools/cache\" \"k8s.io/client-go/tools/record\" cloudprovider \"k8s.io/cloud-provider\" <ins> csilibplugins \"k8s.io/csi-translation-lib/plugins\" </ins> proxyutil \"k8s.io/kubernetes/pkg/proxy/util\" . \"k8s.io/kubernetes/pkg/volume\" \"k8s.io/kubernetes/pkg/volume/util/hostutil\"", "positive_passages": [{"docid": "doc-en-kubernetes-43fa70370952068e2f27033c41492113945a1e0b0ce47a43a47f5065969f2aa7", "text": "After the cluster was updated to enable PD CSI Driver, there was a race condition where AD Controller (kube-controller-manager) started to BEFORE the PD CSI Driver was up, thus AD Controller gave us the error Then AD Controller triggered the disk detach because the disk/volume was not populated in the desired state of world. Unfortunately the disk was in use during this detach and got corrupted. Since cluster upgrades can cause the controller manager and CSI drivers to start at different times, the AD controller needs to be more conservative when detaching We have not been able to reproduce this, it came up from a customer. /sig storage /assign <detailsk8s 1.23, CSI migration enabled </details<detailsGKE </details<details</details<details</details<details</details<details</details\n/triage accepted\nI think there's potentially two changes we should do: 1) for the initial DSW population, we should skip the check that if the csi driver is not installed. 2) in general, we should not skip volumes during dsw initial population if an error is returned. If we had some temporary api server error then that would cause volumes to not get to dsw and similar behavior happen. cc\nfor a repro, maybe you can try something like: a cluster with csi migration enabled (control plane + nodes) a pod with intree-volume and get it running the csi driver node daemonset. verify the driver is removed from CSINode kube-controller-manager\ncc\n/cc was trying to repro this, but on GKE with the managed driver which made it complicated.\nYeah maybe gce kube-up would be easier for a repro\nIf CSINode says that it has migrated GCP PD volume plugin to CSI, then IMO A/D controller should always attach GCP PD volumes to it using CSI, regardless if the CSI driver is present or not. In-tree volume plugin in the kubelet is disabled and can't mount any in-tree volumes anyway. To flip the migration feature gate / upgrade / downgrade kubelet, the cluster admin must drain the node first to make sure everything is detached. A/D controller should not see change of CSINode migration annotations with any volume attached to it.\n/priority important-soon\nAnother option could be to process these volumes anyways but add them to DSOW with migration status as \"uncertain\", so as they can be re-processed later.", "commid": "kubernetes_issue_115297", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-92107579e54d96400b617b596f54e43e809d8c4aca2e3eed9f48d3018b8306a8", "query": "\"k8s.io/client-go/tools/cache\" \"k8s.io/client-go/tools/record\" cloudprovider \"k8s.io/cloud-provider\" <ins> csilibplugins \"k8s.io/csi-translation-lib/plugins\" </ins> proxyutil \"k8s.io/kubernetes/pkg/proxy/util\" . \"k8s.io/kubernetes/pkg/volume\" \"k8s.io/kubernetes/pkg/volume/util/hostutil\"", "positive_passages": [{"docid": "doc-en-kubernetes-8286ec57fa1e024ad026b2342f466cffd200140a0a95c9b64ae688331c52eb45", "text": "But surely it looks like might be easiest unless it has any downsides.\nThere wasn't a node update in this case---there was a control plane update which restarted the PD CSI driver, and it looks like the CSIDriver resource was updated or changed in some way which raced with the kube-controller-manager restart.\nIs there anyway we can know if the csi driver is up and running(like a health check ping) before populating DSW?\nWe use the CSINode registration to determine that. The discussion here I think is concluding that we should not use that as a criteria for adding the volume to DSW. We only need to check that CSI migration is enabled on the node.\n+1 we need to be very resilient against races, I think we have to assume a driver is in process of being installed at any point in the AD controller reconcilliation.\n/assign sunnylovestiramisu\nReproduced with the steps: In /var/log/kube-controller-\nTested with the and doing the reproduce steps above. The error of does not show up anymore. The error message still get logged in the kube-controller- for debugging purpose: Ran Ran On the GCP console, the disk is used by node: Ran I redeploy the pd-csi-driver and then make sure it is up and running. Ran", "commid": "kubernetes_issue_115297", "tokennum": 285}], "negative_passages": []}
{"query_id": "q-en-kubernetes-923f7a01728f7eefd81183197eb1e34dd14d98d01db31b3ce848e2969018e5ed", "query": "// ResourceConfiguration stores per resource configuration. type ResourceConfiguration struct { <del> // resources is a list of kubernetes resources which have to be encrypted. </del> <ins> // resources is a list of kubernetes resources which have to be encrypted. The resource names are derived from `resource` or `resource.group` of the group/version/resource. // eg: pandas.awesome.bears.example is a custom resource with 'group': awesome.bears.example, 'resource': pandas) </ins> Resources []string // providers is a list of transformers to be used for reading and writing the resources to disk. // eg: aesgcm, aescbc, secretbox, identity.", "positive_passages": [{"docid": "doc-en-kubernetes-0045c1600a60d9073df9d5127e356e4d0c19e0407dd07c166d371541fb200a6a", "text": "Update the godoc on the encryption config API on how to specify group/resources to be encrypted ref: godoc has the details na No response_ na na <details</details<details</details<details</details<details</details\n/sig auth /triage accepted\n/assign Cool-Coder174\nThanks for volunteering for this LMK if you need any help with it.\nJust for clarification, I just need to add documentation on how to configure encryption on groups/resources?\nYou can update godoc to mention that custom resources can now be to the list of to be encrypted as well and how to add the of the resource to the list. e.g. from this test\n/assign /unassign Release v1.26 deadlines are here so we need to get this completed ASAP.\n/milestone v1.26\nI apologize for the slow actions. I know time and contributions are valuable. May I request a walk through. This is my first time ever contributing and I really want to learn. I have been reading some of the code base on my spare time.\nthis feature is on the harder side of things to get started with. Reading the blog post and the associated documentation is probably the best starting point:\n& what is the status on this issue? 1.26 is coming up! cc\n/milestone v1.27", "commid": "kubernetes_issue_113272", "tokennum": 293}], "negative_passages": []}
{"query_id": "q-en-kubernetes-92618f9008bfb67b8195de8208c30a4726f24c48504df0cd40f940aeab112be8", "query": "registry = \"k8s.gcr.io/build-image\", repository = \"debian-base\", # Ensure the digests above are updated to match a new tag <del> tag = \"buster-v1.3.0\",  # ignored, but kept here for documentation </del> <ins> tag = \"buster-v1.4.0\",  # ignored, but kept here for documentation </ins> ) container_pull(", "positive_passages": [{"docid": "doc-en-kubernetes-ee0826757468ea334f95c77509b257c3d392b6713b4311ba7afa125d642dcec9", "text": "The based container images for are shipped with the wrong architecture within the manifest if not amd64: Refers to We updated the images a few minutes ago to buster-v1.3.0, which are now ready to be used as base for the multi-architecture images. If the images contain the right architectures, then it may magically happen that the kube-proxy images are fixed, too. This is because we already use the build syntax for it: /cc\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig release", "commid": "kubernetes_issue_98229", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-92620ae8f83e66e75708e6c8a93876ad52d1b44ed51cd73e94803198f6e5dc76", "query": "<ins> /* Copyright 2020 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package network import ( \"fmt\" \"strings\" \"time\" \"github.com/onsi/ginkgo\" v1 \"k8s.io/api/core/v1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/util/intstr\" clientset \"k8s.io/client-go/kubernetes\" \"k8s.io/kubernetes/test/e2e/framework\" e2enode \"k8s.io/kubernetes/test/e2e/framework/node\" e2epod \"k8s.io/kubernetes/test/e2e/framework/pod\" e2eservice \"k8s.io/kubernetes/test/e2e/framework/service\" e2eskipper \"k8s.io/kubernetes/test/e2e/framework/skipper\" ) const ( serviceName = \"svc-udp\" podClient   = \"pod-client\" podBackend1 = \"pod-server-1\" podBackend2 = \"pod-server-2\" srcPort     = 12345 ) // Linux NAT uses conntrack to perform NAT, everytime a new // flow is seen, a connection is created in the conntrack table, and it // is being used by the NAT module. // Each entry in the conntrack table has associated a timeout, that removes // the connection once it expires. // UDP is a connectionless protocol, so the conntrack module tracking functions // are not very advanced. // It uses a short timeout (30 sec by default) that is renewed if there are new flows // matching the connection. Otherwise it expires the entry. // This behaviour can cause issues in Kubernetes when one entry on the conntrack table // is never expired because the sender does not stop sending traffic, but the pods or // endpoints were deleted, blackholing the traffic // In order to mitigate this problem, Kubernetes delete the stale entries: // - when an endpoint is removed // - when a service goes from no endpoints to new endpoint // Ref: https://api.semanticscholar.org/CorpusID:198903401 // Boye, Magnus. \u201cNetfilter Connection Tracking and NAT Implementation.\u201d (2012). var _ = SIGDescribe(\"Conntrack\", func() { fr := framework.NewDefaultFramework(\"conntrack\") type nodeInfo struct { name   string nodeIP string } var ( cs                             clientset.Interface ns                             string clientNodeInfo, serverNodeInfo nodeInfo ) ginkgo.BeforeEach(func() { cs = fr.ClientSet ns = fr.Namespace.Name nodes, err := e2enode.GetBoundedReadySchedulableNodes(cs, 2) framework.ExpectNoError(err) if len(nodes.Items) < 2 { e2eskipper.Skipf( \"Test requires >= 2 Ready nodes, but there are only %v nodes\", len(nodes.Items)) } ips := e2enode.CollectAddresses(nodes, v1.NodeInternalIP) clientNodeInfo = nodeInfo{ name:   nodes.Items[0].Name, nodeIP: ips[0], } serverNodeInfo = nodeInfo{ name:   nodes.Items[1].Name, nodeIP: ips[1], } }) ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a NodePort service\", func() { // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=NodePort in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeNodePort svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"udp\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Create a pod in one node to create the UDP traffic against the NodePort service every 5 seconds ginkgo.By(\"creating a client pod for probing the service \" + serviceName) clientPod := newAgnhostPod(podClient, \"\") clientPod.Spec.NodeName = clientNodeInfo.name cmd := fmt.Sprintf(`date; for i in $(seq 1 300); do echo \"$(date) Try: ${i}\"; echo hostname | nc -u -w 5 -p %d %s %d; echo; done`, srcPort, serverNodeInfo.nodeIP, udpService.Spec.Ports[0].NodePort) clientPod.Spec.Containers[0].Command = []string{\"/bin/sh\", \"-c\", cmd} clientPod.Spec.Containers[0].Name = podClient fr.PodClient().CreateSync(clientPod) // Read the client pod logs logs, err := e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) // Add a backend pod to the service in the other node ginkgo.By(\"creating a backend pod \" + podBackend1 + \" for the service \" + serviceName) serverPod1 := newAgnhostPod(podBackend1, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels serverPod1.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod1) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{podBackend1: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod receives the traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 1 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend1) { framework.Failf(\"Failed to connecto to backend 1\") } // Create a second pod ginkgo.By(\"creating a second backend pod \" + podBackend2 + \" for the service \" + serviceName) serverPod2 := newAgnhostPod(podBackend2, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels serverPod2.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod2) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", podBackend1) fr.PodClient().DeleteSync(podBackend1, metav1.DeleteOptions{}, framework.DefaultPodDeletionTimeout) // Check that the second pod keeps receiving traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 2 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend2) { framework.Failf(\"Failed to connecto to backend 2\") } }) ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a ClusterIP service\", func() { // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=ClusterIP in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeClusterIP svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"udp\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Create a pod in one node to create the UDP traffic against the NodePort service every 5 seconds ginkgo.By(\"creating a client pod for probing the service \" + serviceName) clientPod := newAgnhostPod(podClient, \"\") clientPod.Spec.NodeName = clientNodeInfo.name cmd := fmt.Sprintf(`date; for i in $(seq 1 300); do echo \"$(date) Try: ${i}\"; echo hostname | nc -u -w 5 -p %d %s %d; echo; done`, srcPort, udpService.Spec.ClusterIP, udpService.Spec.Ports[0].Port) clientPod.Spec.Containers[0].Command = []string{\"/bin/sh\", \"-c\", cmd} clientPod.Spec.Containers[0].Name = podClient fr.PodClient().CreateSync(clientPod) // Read the client pod logs logs, err := e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) // Add a backend pod to the service in the other node ginkgo.By(\"creating a backend pod \" + podBackend1 + \" for the service \" + serviceName) serverPod1 := newAgnhostPod(podBackend1, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels serverPod1.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod1) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{podBackend1: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod receives the traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 1 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend1) { framework.Failf(\"Failed to connecto to backend 1\") } // Create a second pod ginkgo.By(\"creating a second backend pod \" + podBackend2 + \" for the service \" + serviceName) serverPod2 := newAgnhostPod(podBackend2, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels serverPod2.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod2) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", podBackend1) fr.PodClient().DeleteSync(podBackend1, metav1.DeleteOptions{}, framework.DefaultPodDeletionTimeout) // Check that the second pod keeps receiving traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 2 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend2) { framework.Failf(\"Failed to connecto to backend 2\") } }) }) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-7bfb1f284722c2f05aa84834ae56662d5ec19fb895a91cc774b04328b8cdc59d", "text": "Which jobs are flaking: ci-kubernetes-e2e-gce-scale-correctness Which test(s) are flaking: [sig-network] Services should be able to preserve UDP traffic when server pod cycles for a NodePort service Testgrid link: https://k8s- Reason for failure: /sig network /assign\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nCRI-O CI is also hitting this failure. We have been unable to reproduce locally. our CI runs on aws\nhmm, I only see 1 failure out of 4 and seems that the connectivity didn't work at all\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\n/assign\nGitHub didn't allow me to assign the following users: JacobTanenbaum. 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\n/cc Saw the test flaking recently: Wondering if this is just a timeout issue.", "commid": "kubernetes_issue_91236", "tokennum": 320}], "negative_passages": []}
{"query_id": "q-en-kubernetes-92620ae8f83e66e75708e6c8a93876ad52d1b44ed51cd73e94803198f6e5dc76", "query": "<ins> /* Copyright 2020 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package network import ( \"fmt\" \"strings\" \"time\" \"github.com/onsi/ginkgo\" v1 \"k8s.io/api/core/v1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/util/intstr\" clientset \"k8s.io/client-go/kubernetes\" \"k8s.io/kubernetes/test/e2e/framework\" e2enode \"k8s.io/kubernetes/test/e2e/framework/node\" e2epod \"k8s.io/kubernetes/test/e2e/framework/pod\" e2eservice \"k8s.io/kubernetes/test/e2e/framework/service\" e2eskipper \"k8s.io/kubernetes/test/e2e/framework/skipper\" ) const ( serviceName = \"svc-udp\" podClient   = \"pod-client\" podBackend1 = \"pod-server-1\" podBackend2 = \"pod-server-2\" srcPort     = 12345 ) // Linux NAT uses conntrack to perform NAT, everytime a new // flow is seen, a connection is created in the conntrack table, and it // is being used by the NAT module. // Each entry in the conntrack table has associated a timeout, that removes // the connection once it expires. // UDP is a connectionless protocol, so the conntrack module tracking functions // are not very advanced. // It uses a short timeout (30 sec by default) that is renewed if there are new flows // matching the connection. Otherwise it expires the entry. // This behaviour can cause issues in Kubernetes when one entry on the conntrack table // is never expired because the sender does not stop sending traffic, but the pods or // endpoints were deleted, blackholing the traffic // In order to mitigate this problem, Kubernetes delete the stale entries: // - when an endpoint is removed // - when a service goes from no endpoints to new endpoint // Ref: https://api.semanticscholar.org/CorpusID:198903401 // Boye, Magnus. \u201cNetfilter Connection Tracking and NAT Implementation.\u201d (2012). var _ = SIGDescribe(\"Conntrack\", func() { fr := framework.NewDefaultFramework(\"conntrack\") type nodeInfo struct { name   string nodeIP string } var ( cs                             clientset.Interface ns                             string clientNodeInfo, serverNodeInfo nodeInfo ) ginkgo.BeforeEach(func() { cs = fr.ClientSet ns = fr.Namespace.Name nodes, err := e2enode.GetBoundedReadySchedulableNodes(cs, 2) framework.ExpectNoError(err) if len(nodes.Items) < 2 { e2eskipper.Skipf( \"Test requires >= 2 Ready nodes, but there are only %v nodes\", len(nodes.Items)) } ips := e2enode.CollectAddresses(nodes, v1.NodeInternalIP) clientNodeInfo = nodeInfo{ name:   nodes.Items[0].Name, nodeIP: ips[0], } serverNodeInfo = nodeInfo{ name:   nodes.Items[1].Name, nodeIP: ips[1], } }) ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a NodePort service\", func() { // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=NodePort in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeNodePort svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"udp\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Create a pod in one node to create the UDP traffic against the NodePort service every 5 seconds ginkgo.By(\"creating a client pod for probing the service \" + serviceName) clientPod := newAgnhostPod(podClient, \"\") clientPod.Spec.NodeName = clientNodeInfo.name cmd := fmt.Sprintf(`date; for i in $(seq 1 300); do echo \"$(date) Try: ${i}\"; echo hostname | nc -u -w 5 -p %d %s %d; echo; done`, srcPort, serverNodeInfo.nodeIP, udpService.Spec.Ports[0].NodePort) clientPod.Spec.Containers[0].Command = []string{\"/bin/sh\", \"-c\", cmd} clientPod.Spec.Containers[0].Name = podClient fr.PodClient().CreateSync(clientPod) // Read the client pod logs logs, err := e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) // Add a backend pod to the service in the other node ginkgo.By(\"creating a backend pod \" + podBackend1 + \" for the service \" + serviceName) serverPod1 := newAgnhostPod(podBackend1, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels serverPod1.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod1) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{podBackend1: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod receives the traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 1 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend1) { framework.Failf(\"Failed to connecto to backend 1\") } // Create a second pod ginkgo.By(\"creating a second backend pod \" + podBackend2 + \" for the service \" + serviceName) serverPod2 := newAgnhostPod(podBackend2, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels serverPod2.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod2) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", podBackend1) fr.PodClient().DeleteSync(podBackend1, metav1.DeleteOptions{}, framework.DefaultPodDeletionTimeout) // Check that the second pod keeps receiving traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 2 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend2) { framework.Failf(\"Failed to connecto to backend 2\") } }) ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a ClusterIP service\", func() { // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=ClusterIP in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeClusterIP svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"udp\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Create a pod in one node to create the UDP traffic against the NodePort service every 5 seconds ginkgo.By(\"creating a client pod for probing the service \" + serviceName) clientPod := newAgnhostPod(podClient, \"\") clientPod.Spec.NodeName = clientNodeInfo.name cmd := fmt.Sprintf(`date; for i in $(seq 1 300); do echo \"$(date) Try: ${i}\"; echo hostname | nc -u -w 5 -p %d %s %d; echo; done`, srcPort, udpService.Spec.ClusterIP, udpService.Spec.Ports[0].Port) clientPod.Spec.Containers[0].Command = []string{\"/bin/sh\", \"-c\", cmd} clientPod.Spec.Containers[0].Name = podClient fr.PodClient().CreateSync(clientPod) // Read the client pod logs logs, err := e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) // Add a backend pod to the service in the other node ginkgo.By(\"creating a backend pod \" + podBackend1 + \" for the service \" + serviceName) serverPod1 := newAgnhostPod(podBackend1, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels serverPod1.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod1) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{podBackend1: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod receives the traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 1 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend1) { framework.Failf(\"Failed to connecto to backend 1\") } // Create a second pod ginkgo.By(\"creating a second backend pod \" + podBackend2 + \" for the service \" + serviceName) serverPod2 := newAgnhostPod(podBackend2, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels serverPod2.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod2) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", podBackend1) fr.PodClient().DeleteSync(podBackend1, metav1.DeleteOptions{}, framework.DefaultPodDeletionTimeout) // Check that the second pod keeps receiving traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 2 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend2) { framework.Failf(\"Failed to connecto to backend 2\") } }) }) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-7ebfc2af23ebf8477a19d5b139a7e0f62f200d8158a5532a965c9eb49bf73a96", "text": "Maybe we can increase the timeout and/or switch to a TCP based test:\nthe test should use UDP, and UDP is unreliable by definition ... however is curious that most of the failures happen because it is not able to communicate with the first pod I think that is something that should be investigated, I've analyzed some occurences and it works fine for the second pod, however, the UDP losses should be totally random\nHi everyone, yeah so.. collecting some data on this... using a two node kind cluster, locally, with the antrea plugin, it passes using a 4 node AWS cluster with the antrea CNI plugin, it failed using a two node kidn cluster locally with calico, it passes So I guess the best reproducer is to run these tests, for now, in the cloud.... Now that I have a reproducer for this maybe can live debug it some time next wk with one of yall :)\nbear in mind that this test is connecting to a nodePort in the node IP, the test is functionally correct, it may be flaky due to the unreliable UDP nature or due to the pod scheduling, but if is failing constantly it has to be environmental.\nSecond failure after two weeks of green 5k runs:\nyep, :/ https://k8s-|UDP /assign\n/reopen I'm afraid this is going to be challenging :smile: The difference now is that we are testing NodePort and ClusterIP If both fail, we can blame the test for sure, If only NodePort fails, we need to check the job, if GCE or KIND If only ClusterIP fails, ... :thinking:\nReopened this issue. <detailsIn response to : /reopen I'm afraid this is going to be challenging :smile: 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\nWe're hitting this really frequently in 5k-node tests. So I started looking a little bit into that.", "commid": "kubernetes_issue_91236", "tokennum": 445}], "negative_passages": []}
{"query_id": "q-en-kubernetes-92620ae8f83e66e75708e6c8a93876ad52d1b44ed51cd73e94803198f6e5dc76", "query": "<ins> /* Copyright 2020 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package network import ( \"fmt\" \"strings\" \"time\" \"github.com/onsi/ginkgo\" v1 \"k8s.io/api/core/v1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/util/intstr\" clientset \"k8s.io/client-go/kubernetes\" \"k8s.io/kubernetes/test/e2e/framework\" e2enode \"k8s.io/kubernetes/test/e2e/framework/node\" e2epod \"k8s.io/kubernetes/test/e2e/framework/pod\" e2eservice \"k8s.io/kubernetes/test/e2e/framework/service\" e2eskipper \"k8s.io/kubernetes/test/e2e/framework/skipper\" ) const ( serviceName = \"svc-udp\" podClient   = \"pod-client\" podBackend1 = \"pod-server-1\" podBackend2 = \"pod-server-2\" srcPort     = 12345 ) // Linux NAT uses conntrack to perform NAT, everytime a new // flow is seen, a connection is created in the conntrack table, and it // is being used by the NAT module. // Each entry in the conntrack table has associated a timeout, that removes // the connection once it expires. // UDP is a connectionless protocol, so the conntrack module tracking functions // are not very advanced. // It uses a short timeout (30 sec by default) that is renewed if there are new flows // matching the connection. Otherwise it expires the entry. // This behaviour can cause issues in Kubernetes when one entry on the conntrack table // is never expired because the sender does not stop sending traffic, but the pods or // endpoints were deleted, blackholing the traffic // In order to mitigate this problem, Kubernetes delete the stale entries: // - when an endpoint is removed // - when a service goes from no endpoints to new endpoint // Ref: https://api.semanticscholar.org/CorpusID:198903401 // Boye, Magnus. \u201cNetfilter Connection Tracking and NAT Implementation.\u201d (2012). var _ = SIGDescribe(\"Conntrack\", func() { fr := framework.NewDefaultFramework(\"conntrack\") type nodeInfo struct { name   string nodeIP string } var ( cs                             clientset.Interface ns                             string clientNodeInfo, serverNodeInfo nodeInfo ) ginkgo.BeforeEach(func() { cs = fr.ClientSet ns = fr.Namespace.Name nodes, err := e2enode.GetBoundedReadySchedulableNodes(cs, 2) framework.ExpectNoError(err) if len(nodes.Items) < 2 { e2eskipper.Skipf( \"Test requires >= 2 Ready nodes, but there are only %v nodes\", len(nodes.Items)) } ips := e2enode.CollectAddresses(nodes, v1.NodeInternalIP) clientNodeInfo = nodeInfo{ name:   nodes.Items[0].Name, nodeIP: ips[0], } serverNodeInfo = nodeInfo{ name:   nodes.Items[1].Name, nodeIP: ips[1], } }) ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a NodePort service\", func() { // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=NodePort in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeNodePort svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"udp\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Create a pod in one node to create the UDP traffic against the NodePort service every 5 seconds ginkgo.By(\"creating a client pod for probing the service \" + serviceName) clientPod := newAgnhostPod(podClient, \"\") clientPod.Spec.NodeName = clientNodeInfo.name cmd := fmt.Sprintf(`date; for i in $(seq 1 300); do echo \"$(date) Try: ${i}\"; echo hostname | nc -u -w 5 -p %d %s %d; echo; done`, srcPort, serverNodeInfo.nodeIP, udpService.Spec.Ports[0].NodePort) clientPod.Spec.Containers[0].Command = []string{\"/bin/sh\", \"-c\", cmd} clientPod.Spec.Containers[0].Name = podClient fr.PodClient().CreateSync(clientPod) // Read the client pod logs logs, err := e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) // Add a backend pod to the service in the other node ginkgo.By(\"creating a backend pod \" + podBackend1 + \" for the service \" + serviceName) serverPod1 := newAgnhostPod(podBackend1, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels serverPod1.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod1) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{podBackend1: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod receives the traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 1 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend1) { framework.Failf(\"Failed to connecto to backend 1\") } // Create a second pod ginkgo.By(\"creating a second backend pod \" + podBackend2 + \" for the service \" + serviceName) serverPod2 := newAgnhostPod(podBackend2, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels serverPod2.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod2) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", podBackend1) fr.PodClient().DeleteSync(podBackend1, metav1.DeleteOptions{}, framework.DefaultPodDeletionTimeout) // Check that the second pod keeps receiving traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 2 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend2) { framework.Failf(\"Failed to connecto to backend 2\") } }) ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a ClusterIP service\", func() { // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=ClusterIP in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeClusterIP svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"udp\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Create a pod in one node to create the UDP traffic against the NodePort service every 5 seconds ginkgo.By(\"creating a client pod for probing the service \" + serviceName) clientPod := newAgnhostPod(podClient, \"\") clientPod.Spec.NodeName = clientNodeInfo.name cmd := fmt.Sprintf(`date; for i in $(seq 1 300); do echo \"$(date) Try: ${i}\"; echo hostname | nc -u -w 5 -p %d %s %d; echo; done`, srcPort, udpService.Spec.ClusterIP, udpService.Spec.Ports[0].Port) clientPod.Spec.Containers[0].Command = []string{\"/bin/sh\", \"-c\", cmd} clientPod.Spec.Containers[0].Name = podClient fr.PodClient().CreateSync(clientPod) // Read the client pod logs logs, err := e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) // Add a backend pod to the service in the other node ginkgo.By(\"creating a backend pod \" + podBackend1 + \" for the service \" + serviceName) serverPod1 := newAgnhostPod(podBackend1, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels serverPod1.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod1) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{podBackend1: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod receives the traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 1 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend1) { framework.Failf(\"Failed to connecto to backend 1\") } // Create a second pod ginkgo.By(\"creating a second backend pod \" + podBackend2 + \" for the service \" + serviceName) serverPod2 := newAgnhostPod(podBackend2, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels serverPod2.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod2) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", podBackend1) fr.PodClient().DeleteSync(podBackend1, metav1.DeleteOptions{}, framework.DefaultPodDeletionTimeout) // Check that the second pod keeps receiving traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 2 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend2) { framework.Failf(\"Failed to connecto to backend 2\") } }) }) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-5846160d0947d31469e9f6af93fd879e379d05716d3adf8932316babb4b3ae6c", "text": "I don't have full understanding of what exactly is happening, but I already see a couple things that may be causing issues: when creating the first pod, you wait for corresponding endpoint for that being created; but that doesn't mean that kube-proxy was actually programmed correctly at that time (in general it isn't); given iptables programming is rate-limitted, it may easily happen that actually programming happens 10s+ later That explains some delays, but it doesn't explain e.g. this run: where iptables were programmed at but the test didn't respond until If someone more familiar with networking stuff could look into it, it would be great. - can you help triaging ^^ for deletions it's even worse, because you don't even wait for endpoints to be there (i.e. Endpoints can still contain the old pod when the test start pinging to look for the second one) So I claim that timeouts are visibly to low in this test, but I suspect it's not everything. I will send out the first PR that tries to improve it in couple minutes.\nthanks wojtek, have been slammed but Ill try to collect more data on it this wknd as well.\nIt seems that my PR didn't really help much. We should dig deeper, but I would need someone with more networking expertise to look a bit into\nActually - it seems only failures from one group are on non . So maybe that's actually related. The non-kind related ones look like:\nOK - for this one, I actually know what is happening - I will send out a PR with a fix for this too.\nfor the KIND jobs already increased the resource requests on some of the jobs, there are issues on KIND jobs with kube-proxy not able to take the iptables lock and not being able to create the iptables rules for the services until the next resync\nis to fix the flakes I mentioned above; all other flakes seem to be kind-oriented to me (which I'm not super familiar with).\nWe did not adjust the CPU on all jobs yet, pending how to manage that on prow ... I do see just a few other flakes at the bottom of the triage dashboard that look like timeouts instead.\nActually - almost all failures are effectively timeout. The top one that is is actually also a timeout. Didn't look into kind failures, but this may easily be related to iptables issues.", "commid": "kubernetes_issue_91236", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-92620ae8f83e66e75708e6c8a93876ad52d1b44ed51cd73e94803198f6e5dc76", "query": "<ins> /* Copyright 2020 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package network import ( \"fmt\" \"strings\" \"time\" \"github.com/onsi/ginkgo\" v1 \"k8s.io/api/core/v1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/util/intstr\" clientset \"k8s.io/client-go/kubernetes\" \"k8s.io/kubernetes/test/e2e/framework\" e2enode \"k8s.io/kubernetes/test/e2e/framework/node\" e2epod \"k8s.io/kubernetes/test/e2e/framework/pod\" e2eservice \"k8s.io/kubernetes/test/e2e/framework/service\" e2eskipper \"k8s.io/kubernetes/test/e2e/framework/skipper\" ) const ( serviceName = \"svc-udp\" podClient   = \"pod-client\" podBackend1 = \"pod-server-1\" podBackend2 = \"pod-server-2\" srcPort     = 12345 ) // Linux NAT uses conntrack to perform NAT, everytime a new // flow is seen, a connection is created in the conntrack table, and it // is being used by the NAT module. // Each entry in the conntrack table has associated a timeout, that removes // the connection once it expires. // UDP is a connectionless protocol, so the conntrack module tracking functions // are not very advanced. // It uses a short timeout (30 sec by default) that is renewed if there are new flows // matching the connection. Otherwise it expires the entry. // This behaviour can cause issues in Kubernetes when one entry on the conntrack table // is never expired because the sender does not stop sending traffic, but the pods or // endpoints were deleted, blackholing the traffic // In order to mitigate this problem, Kubernetes delete the stale entries: // - when an endpoint is removed // - when a service goes from no endpoints to new endpoint // Ref: https://api.semanticscholar.org/CorpusID:198903401 // Boye, Magnus. \u201cNetfilter Connection Tracking and NAT Implementation.\u201d (2012). var _ = SIGDescribe(\"Conntrack\", func() { fr := framework.NewDefaultFramework(\"conntrack\") type nodeInfo struct { name   string nodeIP string } var ( cs                             clientset.Interface ns                             string clientNodeInfo, serverNodeInfo nodeInfo ) ginkgo.BeforeEach(func() { cs = fr.ClientSet ns = fr.Namespace.Name nodes, err := e2enode.GetBoundedReadySchedulableNodes(cs, 2) framework.ExpectNoError(err) if len(nodes.Items) < 2 { e2eskipper.Skipf( \"Test requires >= 2 Ready nodes, but there are only %v nodes\", len(nodes.Items)) } ips := e2enode.CollectAddresses(nodes, v1.NodeInternalIP) clientNodeInfo = nodeInfo{ name:   nodes.Items[0].Name, nodeIP: ips[0], } serverNodeInfo = nodeInfo{ name:   nodes.Items[1].Name, nodeIP: ips[1], } }) ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a NodePort service\", func() { // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=NodePort in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeNodePort svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"udp\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Create a pod in one node to create the UDP traffic against the NodePort service every 5 seconds ginkgo.By(\"creating a client pod for probing the service \" + serviceName) clientPod := newAgnhostPod(podClient, \"\") clientPod.Spec.NodeName = clientNodeInfo.name cmd := fmt.Sprintf(`date; for i in $(seq 1 300); do echo \"$(date) Try: ${i}\"; echo hostname | nc -u -w 5 -p %d %s %d; echo; done`, srcPort, serverNodeInfo.nodeIP, udpService.Spec.Ports[0].NodePort) clientPod.Spec.Containers[0].Command = []string{\"/bin/sh\", \"-c\", cmd} clientPod.Spec.Containers[0].Name = podClient fr.PodClient().CreateSync(clientPod) // Read the client pod logs logs, err := e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) // Add a backend pod to the service in the other node ginkgo.By(\"creating a backend pod \" + podBackend1 + \" for the service \" + serviceName) serverPod1 := newAgnhostPod(podBackend1, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels serverPod1.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod1) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{podBackend1: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod receives the traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 1 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend1) { framework.Failf(\"Failed to connecto to backend 1\") } // Create a second pod ginkgo.By(\"creating a second backend pod \" + podBackend2 + \" for the service \" + serviceName) serverPod2 := newAgnhostPod(podBackend2, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels serverPod2.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod2) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", podBackend1) fr.PodClient().DeleteSync(podBackend1, metav1.DeleteOptions{}, framework.DefaultPodDeletionTimeout) // Check that the second pod keeps receiving traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 2 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend2) { framework.Failf(\"Failed to connecto to backend 2\") } }) ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a ClusterIP service\", func() { // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=ClusterIP in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeClusterIP svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"udp\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Create a pod in one node to create the UDP traffic against the NodePort service every 5 seconds ginkgo.By(\"creating a client pod for probing the service \" + serviceName) clientPod := newAgnhostPod(podClient, \"\") clientPod.Spec.NodeName = clientNodeInfo.name cmd := fmt.Sprintf(`date; for i in $(seq 1 300); do echo \"$(date) Try: ${i}\"; echo hostname | nc -u -w 5 -p %d %s %d; echo; done`, srcPort, udpService.Spec.ClusterIP, udpService.Spec.Ports[0].Port) clientPod.Spec.Containers[0].Command = []string{\"/bin/sh\", \"-c\", cmd} clientPod.Spec.Containers[0].Name = podClient fr.PodClient().CreateSync(clientPod) // Read the client pod logs logs, err := e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) // Add a backend pod to the service in the other node ginkgo.By(\"creating a backend pod \" + podBackend1 + \" for the service \" + serviceName) serverPod1 := newAgnhostPod(podBackend1, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels serverPod1.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod1) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{podBackend1: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod receives the traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 1 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend1) { framework.Failf(\"Failed to connecto to backend 1\") } // Create a second pod ginkgo.By(\"creating a second backend pod \" + podBackend2 + \" for the service \" + serviceName) serverPod2 := newAgnhostPod(podBackend2, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels serverPod2.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod2) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", podBackend1) fr.PodClient().DeleteSync(podBackend1, metav1.DeleteOptions{}, framework.DefaultPodDeletionTimeout) // Check that the second pod keeps receiving traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 2 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend2) { framework.Failf(\"Failed to connecto to backend 2\") } }) }) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-0543f3a3993360bbed011d4060e35a21f3f79414d82ea25f247261ac2b705804", "text": "After my second deflaking PR, we seem to be in the stage where: tests are failing on dozens of different things (probably iptables-issues related) tests are failing only on NodePort tests on \"Failed to connecto to backend 1\" which it would be great if someone else could look into (kube-proxy seemed to be programmed correctly based on logs)\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\nThis has failed again - Linking to specific part of log where timeout occurred .... we see this\nSo reviewing the above logs note how in STEP: checking client pod connected to the backend 1 on Node IP 10.138.0.5 28 attempts are made all in the 25th second of the 2 minute at 11am Should this Step back off and wait a few seconds in between tries? So looking at this code we see the following\nFrom reading ... the intention expressed in the test code looks good to me. It is not clear to me why there is a mismatch between the 28 tries in the POD Client Logs and the expressed intention running the logContainsFn(podBackend1) every 5 seconds still digging ....\nwe are trying to catch one failure in this PR that has additional debugging, it dumps the conntrack table of the nodes on a failure\nfor those following the issue, we've extra debugging to the test so it dumps the whole conntrack table once it finish. We should look that there is NO stale entries, connections from the pod client to the deleted endpoint) and there is conntrack entries to the new endpoint from the pod client.\n- we have runs with the conntrack dump now, e.g. this one: would you be able to take a look into it?\nnot yet :/ , but I think tomorrow can have some time\ncc\nFor anyone reproducing this issue btw, you need a multinode k8s cluster (it isnt doable on kind i guess bc less likeliehood of network failures when running local) -\nCurious about two potential hypotheses to fix this, have we looked into either of these? 1) can we confirm that is turned on/off? 2) is it possible that scaling the number of coredns replicas could help ?", "commid": "kubernetes_issue_91236", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-92620ae8f83e66e75708e6c8a93876ad52d1b44ed51cd73e94803198f6e5dc76", "query": "<ins> /* Copyright 2020 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package network import ( \"fmt\" \"strings\" \"time\" \"github.com/onsi/ginkgo\" v1 \"k8s.io/api/core/v1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/util/intstr\" clientset \"k8s.io/client-go/kubernetes\" \"k8s.io/kubernetes/test/e2e/framework\" e2enode \"k8s.io/kubernetes/test/e2e/framework/node\" e2epod \"k8s.io/kubernetes/test/e2e/framework/pod\" e2eservice \"k8s.io/kubernetes/test/e2e/framework/service\" e2eskipper \"k8s.io/kubernetes/test/e2e/framework/skipper\" ) const ( serviceName = \"svc-udp\" podClient   = \"pod-client\" podBackend1 = \"pod-server-1\" podBackend2 = \"pod-server-2\" srcPort     = 12345 ) // Linux NAT uses conntrack to perform NAT, everytime a new // flow is seen, a connection is created in the conntrack table, and it // is being used by the NAT module. // Each entry in the conntrack table has associated a timeout, that removes // the connection once it expires. // UDP is a connectionless protocol, so the conntrack module tracking functions // are not very advanced. // It uses a short timeout (30 sec by default) that is renewed if there are new flows // matching the connection. Otherwise it expires the entry. // This behaviour can cause issues in Kubernetes when one entry on the conntrack table // is never expired because the sender does not stop sending traffic, but the pods or // endpoints were deleted, blackholing the traffic // In order to mitigate this problem, Kubernetes delete the stale entries: // - when an endpoint is removed // - when a service goes from no endpoints to new endpoint // Ref: https://api.semanticscholar.org/CorpusID:198903401 // Boye, Magnus. \u201cNetfilter Connection Tracking and NAT Implementation.\u201d (2012). var _ = SIGDescribe(\"Conntrack\", func() { fr := framework.NewDefaultFramework(\"conntrack\") type nodeInfo struct { name   string nodeIP string } var ( cs                             clientset.Interface ns                             string clientNodeInfo, serverNodeInfo nodeInfo ) ginkgo.BeforeEach(func() { cs = fr.ClientSet ns = fr.Namespace.Name nodes, err := e2enode.GetBoundedReadySchedulableNodes(cs, 2) framework.ExpectNoError(err) if len(nodes.Items) < 2 { e2eskipper.Skipf( \"Test requires >= 2 Ready nodes, but there are only %v nodes\", len(nodes.Items)) } ips := e2enode.CollectAddresses(nodes, v1.NodeInternalIP) clientNodeInfo = nodeInfo{ name:   nodes.Items[0].Name, nodeIP: ips[0], } serverNodeInfo = nodeInfo{ name:   nodes.Items[1].Name, nodeIP: ips[1], } }) ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a NodePort service\", func() { // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=NodePort in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeNodePort svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"udp\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Create a pod in one node to create the UDP traffic against the NodePort service every 5 seconds ginkgo.By(\"creating a client pod for probing the service \" + serviceName) clientPod := newAgnhostPod(podClient, \"\") clientPod.Spec.NodeName = clientNodeInfo.name cmd := fmt.Sprintf(`date; for i in $(seq 1 300); do echo \"$(date) Try: ${i}\"; echo hostname | nc -u -w 5 -p %d %s %d; echo; done`, srcPort, serverNodeInfo.nodeIP, udpService.Spec.Ports[0].NodePort) clientPod.Spec.Containers[0].Command = []string{\"/bin/sh\", \"-c\", cmd} clientPod.Spec.Containers[0].Name = podClient fr.PodClient().CreateSync(clientPod) // Read the client pod logs logs, err := e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) // Add a backend pod to the service in the other node ginkgo.By(\"creating a backend pod \" + podBackend1 + \" for the service \" + serviceName) serverPod1 := newAgnhostPod(podBackend1, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels serverPod1.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod1) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{podBackend1: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod receives the traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 1 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend1) { framework.Failf(\"Failed to connecto to backend 1\") } // Create a second pod ginkgo.By(\"creating a second backend pod \" + podBackend2 + \" for the service \" + serviceName) serverPod2 := newAgnhostPod(podBackend2, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels serverPod2.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod2) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", podBackend1) fr.PodClient().DeleteSync(podBackend1, metav1.DeleteOptions{}, framework.DefaultPodDeletionTimeout) // Check that the second pod keeps receiving traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 2 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend2) { framework.Failf(\"Failed to connecto to backend 2\") } }) ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a ClusterIP service\", func() { // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=ClusterIP in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeClusterIP svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"udp\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Create a pod in one node to create the UDP traffic against the NodePort service every 5 seconds ginkgo.By(\"creating a client pod for probing the service \" + serviceName) clientPod := newAgnhostPod(podClient, \"\") clientPod.Spec.NodeName = clientNodeInfo.name cmd := fmt.Sprintf(`date; for i in $(seq 1 300); do echo \"$(date) Try: ${i}\"; echo hostname | nc -u -w 5 -p %d %s %d; echo; done`, srcPort, udpService.Spec.ClusterIP, udpService.Spec.Ports[0].Port) clientPod.Spec.Containers[0].Command = []string{\"/bin/sh\", \"-c\", cmd} clientPod.Spec.Containers[0].Name = podClient fr.PodClient().CreateSync(clientPod) // Read the client pod logs logs, err := e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) // Add a backend pod to the service in the other node ginkgo.By(\"creating a backend pod \" + podBackend1 + \" for the service \" + serviceName) serverPod1 := newAgnhostPod(podBackend1, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels serverPod1.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod1) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{podBackend1: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod receives the traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 1 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend1) { framework.Failf(\"Failed to connecto to backend 1\") } // Create a second pod ginkgo.By(\"creating a second backend pod \" + podBackend2 + \" for the service \" + serviceName) serverPod2 := newAgnhostPod(podBackend2, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels serverPod2.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod2) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", podBackend1) fr.PodClient().DeleteSync(podBackend1, metav1.DeleteOptions{}, framework.DefaultPodDeletionTimeout) // Check that the second pod keeps receiving traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 2 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend2) { framework.Failf(\"Failed to connecto to backend 2\") } }) }) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-66f25b05b1c90d93aad713cb7c943585d55afc690fe7a4f7e9fa0b7a5a5f23b1", "text": "3) Would simulating this in kind by overloading coredns be a possibility as a way to make a more reproducible bug model?\nregarding 1) kubeadm does not ship nodeLocalDNSCache I don't think GCE kube-up does by default either\nok, so now im curious about (2) - i.e. what if we just bumped coredns replica count?\ninteresting, :thinking: why do you think is a DNS thing? the netcat command that polls the services use the IP addresses not the hostname. I think that it has to be related to some iptables/conntrack race or similar,at least in KIND jobs we know that we have an iptables problem that affects network tests, that has to be fixed before this because it affect this test You can instrument the test locally with this and dump the state of iptables and conntrack on failure if you are able to reproduce it\ni figured DNS bc i believe its known that conntrack and DNS at scale can get very messy, right ?\none other curious thing about this test is that we only create 2 pods in the recycling event for the svc. that likely means that any real error is hidden by chance..... If we created a 3rd pod, then we might potentially double the failure rate thus making the flakyness go away and expose the real underlying issue .\nThere's an invocation of dumpConntrack(cs) here [sig-network] Conntrack should be able to preserve UDP traffic when server pod cycles for a ClusterIP service\nis updating the logging to run in an infinite loop ..\nThis is improving in KIND with the new changes we rolled out yesterday, let's see how it evolves this week\n- which changes ? Are you saying this is no longer reproducible on Kind?\nthere was a lot of noise in the CI signal, especially in KIND jobs due to the CNI portmap bug we finally solved yesterday now we should have a better signal and we can go to the bottom because probably the failure will be \"legit\" and not a consequence, so this comment should apply\nHi ! I ran this a few times on kind and it passed, but I see , so I'm going to try the loop approach you suggested. Here's what I'm using to test:\nquick note, <- potential motivation to possibly have runnable on some subset of tests in upstream eventually, i.e.", "commid": "kubernetes_issue_91236", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-92620ae8f83e66e75708e6c8a93876ad52d1b44ed51cd73e94803198f6e5dc76", "query": "<ins> /* Copyright 2020 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package network import ( \"fmt\" \"strings\" \"time\" \"github.com/onsi/ginkgo\" v1 \"k8s.io/api/core/v1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/util/intstr\" clientset \"k8s.io/client-go/kubernetes\" \"k8s.io/kubernetes/test/e2e/framework\" e2enode \"k8s.io/kubernetes/test/e2e/framework/node\" e2epod \"k8s.io/kubernetes/test/e2e/framework/pod\" e2eservice \"k8s.io/kubernetes/test/e2e/framework/service\" e2eskipper \"k8s.io/kubernetes/test/e2e/framework/skipper\" ) const ( serviceName = \"svc-udp\" podClient   = \"pod-client\" podBackend1 = \"pod-server-1\" podBackend2 = \"pod-server-2\" srcPort     = 12345 ) // Linux NAT uses conntrack to perform NAT, everytime a new // flow is seen, a connection is created in the conntrack table, and it // is being used by the NAT module. // Each entry in the conntrack table has associated a timeout, that removes // the connection once it expires. // UDP is a connectionless protocol, so the conntrack module tracking functions // are not very advanced. // It uses a short timeout (30 sec by default) that is renewed if there are new flows // matching the connection. Otherwise it expires the entry. // This behaviour can cause issues in Kubernetes when one entry on the conntrack table // is never expired because the sender does not stop sending traffic, but the pods or // endpoints were deleted, blackholing the traffic // In order to mitigate this problem, Kubernetes delete the stale entries: // - when an endpoint is removed // - when a service goes from no endpoints to new endpoint // Ref: https://api.semanticscholar.org/CorpusID:198903401 // Boye, Magnus. \u201cNetfilter Connection Tracking and NAT Implementation.\u201d (2012). var _ = SIGDescribe(\"Conntrack\", func() { fr := framework.NewDefaultFramework(\"conntrack\") type nodeInfo struct { name   string nodeIP string } var ( cs                             clientset.Interface ns                             string clientNodeInfo, serverNodeInfo nodeInfo ) ginkgo.BeforeEach(func() { cs = fr.ClientSet ns = fr.Namespace.Name nodes, err := e2enode.GetBoundedReadySchedulableNodes(cs, 2) framework.ExpectNoError(err) if len(nodes.Items) < 2 { e2eskipper.Skipf( \"Test requires >= 2 Ready nodes, but there are only %v nodes\", len(nodes.Items)) } ips := e2enode.CollectAddresses(nodes, v1.NodeInternalIP) clientNodeInfo = nodeInfo{ name:   nodes.Items[0].Name, nodeIP: ips[0], } serverNodeInfo = nodeInfo{ name:   nodes.Items[1].Name, nodeIP: ips[1], } }) ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a NodePort service\", func() { // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=NodePort in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeNodePort svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"udp\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Create a pod in one node to create the UDP traffic against the NodePort service every 5 seconds ginkgo.By(\"creating a client pod for probing the service \" + serviceName) clientPod := newAgnhostPod(podClient, \"\") clientPod.Spec.NodeName = clientNodeInfo.name cmd := fmt.Sprintf(`date; for i in $(seq 1 300); do echo \"$(date) Try: ${i}\"; echo hostname | nc -u -w 5 -p %d %s %d; echo; done`, srcPort, serverNodeInfo.nodeIP, udpService.Spec.Ports[0].NodePort) clientPod.Spec.Containers[0].Command = []string{\"/bin/sh\", \"-c\", cmd} clientPod.Spec.Containers[0].Name = podClient fr.PodClient().CreateSync(clientPod) // Read the client pod logs logs, err := e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) // Add a backend pod to the service in the other node ginkgo.By(\"creating a backend pod \" + podBackend1 + \" for the service \" + serviceName) serverPod1 := newAgnhostPod(podBackend1, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels serverPod1.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod1) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{podBackend1: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod receives the traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 1 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend1) { framework.Failf(\"Failed to connecto to backend 1\") } // Create a second pod ginkgo.By(\"creating a second backend pod \" + podBackend2 + \" for the service \" + serviceName) serverPod2 := newAgnhostPod(podBackend2, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels serverPod2.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod2) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", podBackend1) fr.PodClient().DeleteSync(podBackend1, metav1.DeleteOptions{}, framework.DefaultPodDeletionTimeout) // Check that the second pod keeps receiving traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 2 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend2) { framework.Failf(\"Failed to connecto to backend 2\") } }) ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a ClusterIP service\", func() { // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=ClusterIP in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeClusterIP svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"udp\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Create a pod in one node to create the UDP traffic against the NodePort service every 5 seconds ginkgo.By(\"creating a client pod for probing the service \" + serviceName) clientPod := newAgnhostPod(podClient, \"\") clientPod.Spec.NodeName = clientNodeInfo.name cmd := fmt.Sprintf(`date; for i in $(seq 1 300); do echo \"$(date) Try: ${i}\"; echo hostname | nc -u -w 5 -p %d %s %d; echo; done`, srcPort, udpService.Spec.ClusterIP, udpService.Spec.Ports[0].Port) clientPod.Spec.Containers[0].Command = []string{\"/bin/sh\", \"-c\", cmd} clientPod.Spec.Containers[0].Name = podClient fr.PodClient().CreateSync(clientPod) // Read the client pod logs logs, err := e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) // Add a backend pod to the service in the other node ginkgo.By(\"creating a backend pod \" + podBackend1 + \" for the service \" + serviceName) serverPod1 := newAgnhostPod(podBackend1, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels serverPod1.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod1) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{podBackend1: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod receives the traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 1 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend1) { framework.Failf(\"Failed to connecto to backend 1\") } // Create a second pod ginkgo.By(\"creating a second backend pod \" + podBackend2 + \" for the service \" + serviceName) serverPod2 := newAgnhostPod(podBackend2, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels serverPod2.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod2) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", podBackend1) fr.PodClient().DeleteSync(podBackend1, metav1.DeleteOptions{}, framework.DefaultPodDeletionTimeout) // Check that the second pod keeps receiving traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 2 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend2) { framework.Failf(\"Failed to connecto to backend 2\") } }) }) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-deebb69aabcaf9005201c68e52f1f862e88c30f5231beaa0034b1d576abe9a4a", "text": "so we can do things like to reproduce this sort of thing. matt did you get around to the 'try-till-it-fails' scenario?\nI haven't been able to get it to fail on kind yet, -- 100 cycles and 0 failures on a three-node kind cluster! I'm letting the loop run for a few hours, will check back in when I have that data. Is it worth running this test on a non-kind environment?\nI ran for several hours on my mac, through 1144 iterations no error yet. My conclusion: this test isn't flaky on KinD. Possible next step: run a large number of iterations of the same test on a GKE cluster.\nFlakes on kind are also happening:\nnot many since the portmap fix on the 14th though ( / ) <img width=\"1111\" alt=\"Screen Shot 2020-07-23 at 11 45 46 PM\" src=\"https://user-\"\nAgree - it's much better than it was before.\nI was analyzing this failure, the problem is that kind jobs does not have verbosity enough in kube-proxy We can see that the packet was never replied, this is the NAT entry from client -nodePort in the node with the client This is the same flow, but in the node with the server and the pod-server-1 seems to be healthy we need more logs :eyeglasses:\nWe have an open ticket to bump those in CI, it's just been lost in the noise. We should still do that. Antonio Ojea <:\nIf you are busy just assign it to me, I'll need this verbosity soon :)\nIt's in the kind repo, shouldn't be too hard to find, we have ~60 open atm. Antonio Ojea <:\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\nI made another attempt to reproduce these failures locally on KinD, but still no success. Here's what I did: create a KinD cluster run two instances of sonobuoy at the same time This took ~4 hours to run; all the kube tests passed and sonobuoy reported all successes.", "commid": "kubernetes_issue_91236", "tokennum": 494}], "negative_passages": []}
{"query_id": "q-en-kubernetes-92620ae8f83e66e75708e6c8a93876ad52d1b44ed51cd73e94803198f6e5dc76", "query": "<ins> /* Copyright 2020 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package network import ( \"fmt\" \"strings\" \"time\" \"github.com/onsi/ginkgo\" v1 \"k8s.io/api/core/v1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/util/intstr\" clientset \"k8s.io/client-go/kubernetes\" \"k8s.io/kubernetes/test/e2e/framework\" e2enode \"k8s.io/kubernetes/test/e2e/framework/node\" e2epod \"k8s.io/kubernetes/test/e2e/framework/pod\" e2eservice \"k8s.io/kubernetes/test/e2e/framework/service\" e2eskipper \"k8s.io/kubernetes/test/e2e/framework/skipper\" ) const ( serviceName = \"svc-udp\" podClient   = \"pod-client\" podBackend1 = \"pod-server-1\" podBackend2 = \"pod-server-2\" srcPort     = 12345 ) // Linux NAT uses conntrack to perform NAT, everytime a new // flow is seen, a connection is created in the conntrack table, and it // is being used by the NAT module. // Each entry in the conntrack table has associated a timeout, that removes // the connection once it expires. // UDP is a connectionless protocol, so the conntrack module tracking functions // are not very advanced. // It uses a short timeout (30 sec by default) that is renewed if there are new flows // matching the connection. Otherwise it expires the entry. // This behaviour can cause issues in Kubernetes when one entry on the conntrack table // is never expired because the sender does not stop sending traffic, but the pods or // endpoints were deleted, blackholing the traffic // In order to mitigate this problem, Kubernetes delete the stale entries: // - when an endpoint is removed // - when a service goes from no endpoints to new endpoint // Ref: https://api.semanticscholar.org/CorpusID:198903401 // Boye, Magnus. \u201cNetfilter Connection Tracking and NAT Implementation.\u201d (2012). var _ = SIGDescribe(\"Conntrack\", func() { fr := framework.NewDefaultFramework(\"conntrack\") type nodeInfo struct { name   string nodeIP string } var ( cs                             clientset.Interface ns                             string clientNodeInfo, serverNodeInfo nodeInfo ) ginkgo.BeforeEach(func() { cs = fr.ClientSet ns = fr.Namespace.Name nodes, err := e2enode.GetBoundedReadySchedulableNodes(cs, 2) framework.ExpectNoError(err) if len(nodes.Items) < 2 { e2eskipper.Skipf( \"Test requires >= 2 Ready nodes, but there are only %v nodes\", len(nodes.Items)) } ips := e2enode.CollectAddresses(nodes, v1.NodeInternalIP) clientNodeInfo = nodeInfo{ name:   nodes.Items[0].Name, nodeIP: ips[0], } serverNodeInfo = nodeInfo{ name:   nodes.Items[1].Name, nodeIP: ips[1], } }) ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a NodePort service\", func() { // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=NodePort in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeNodePort svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"udp\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Create a pod in one node to create the UDP traffic against the NodePort service every 5 seconds ginkgo.By(\"creating a client pod for probing the service \" + serviceName) clientPod := newAgnhostPod(podClient, \"\") clientPod.Spec.NodeName = clientNodeInfo.name cmd := fmt.Sprintf(`date; for i in $(seq 1 300); do echo \"$(date) Try: ${i}\"; echo hostname | nc -u -w 5 -p %d %s %d; echo; done`, srcPort, serverNodeInfo.nodeIP, udpService.Spec.Ports[0].NodePort) clientPod.Spec.Containers[0].Command = []string{\"/bin/sh\", \"-c\", cmd} clientPod.Spec.Containers[0].Name = podClient fr.PodClient().CreateSync(clientPod) // Read the client pod logs logs, err := e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) // Add a backend pod to the service in the other node ginkgo.By(\"creating a backend pod \" + podBackend1 + \" for the service \" + serviceName) serverPod1 := newAgnhostPod(podBackend1, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels serverPod1.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod1) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{podBackend1: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod receives the traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 1 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend1) { framework.Failf(\"Failed to connecto to backend 1\") } // Create a second pod ginkgo.By(\"creating a second backend pod \" + podBackend2 + \" for the service \" + serviceName) serverPod2 := newAgnhostPod(podBackend2, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels serverPod2.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod2) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", podBackend1) fr.PodClient().DeleteSync(podBackend1, metav1.DeleteOptions{}, framework.DefaultPodDeletionTimeout) // Check that the second pod keeps receiving traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 2 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend2) { framework.Failf(\"Failed to connecto to backend 2\") } }) ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a ClusterIP service\", func() { // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=ClusterIP in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeClusterIP svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"udp\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Create a pod in one node to create the UDP traffic against the NodePort service every 5 seconds ginkgo.By(\"creating a client pod for probing the service \" + serviceName) clientPod := newAgnhostPod(podClient, \"\") clientPod.Spec.NodeName = clientNodeInfo.name cmd := fmt.Sprintf(`date; for i in $(seq 1 300); do echo \"$(date) Try: ${i}\"; echo hostname | nc -u -w 5 -p %d %s %d; echo; done`, srcPort, udpService.Spec.ClusterIP, udpService.Spec.Ports[0].Port) clientPod.Spec.Containers[0].Command = []string{\"/bin/sh\", \"-c\", cmd} clientPod.Spec.Containers[0].Name = podClient fr.PodClient().CreateSync(clientPod) // Read the client pod logs logs, err := e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) // Add a backend pod to the service in the other node ginkgo.By(\"creating a backend pod \" + podBackend1 + \" for the service \" + serviceName) serverPod1 := newAgnhostPod(podBackend1, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels serverPod1.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod1) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{podBackend1: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod receives the traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 1 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend1) { framework.Failf(\"Failed to connecto to backend 1\") } // Create a second pod ginkgo.By(\"creating a second backend pod \" + podBackend2 + \" for the service \" + serviceName) serverPod2 := newAgnhostPod(podBackend2, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels serverPod2.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod2) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", podBackend1) fr.PodClient().DeleteSync(podBackend1, metav1.DeleteOptions{}, framework.DefaultPodDeletionTimeout) // Check that the second pod keeps receiving traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 2 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend2) { framework.Failf(\"Failed to connecto to backend 2\") } }) }) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-738ad9cb1373dead6b2f556ac241cd0c8a6cc7a0f09950111e765d9eb1dab68b", "text": "Would love to help out in reproing this, I'm at a loss for good next step so any suggestions welcome!\nthat's the problem with these flakes, they are not easy to repro, and with this low rate of failures it may be caused for combination of running tests, environmental problems (cpu, memory, ...) , ... I always start for checking the current failures and try to find patterns\nLet's take a look to one occurrence The tests fails because can't connect to the first pod If we check the code of the tests, we can see that it always uses the port as source port, we can use that to identify the nodePort assigned interesting thing here, we are source nating the pod ip, and we don't see any other conntrack entry The test verifies it has endpoints however, kube-proxy is using endpointlsices since this version but it has no entries so the iptables rules to forward the traffic are not there Seems we have to adapt this function in the e2e framework to use endpointslices cc: EDIT seems that this function is being used by all the network tests that can cause flakes if the endpoint is updated before the endpointslice (we switched recently kube-proxy to use the later)\nGreat catch. Ideally this function should validate if both Endpoint and appropriate EndpointSlice objects(s) exist.\nActually - let me take it and send a PR for it.\nis out for review\nInteresting failures here It fails to connect to the first pod\nHmm - I took a quick look at kube-proxy logs and these look fine to me....\nI clicked too fast, sorry ... I was looking at the wrong service and I though I've found something\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry.", "commid": "kubernetes_issue_91236", "tokennum": 416}], "negative_passages": []}
{"query_id": "q-en-kubernetes-92620ae8f83e66e75708e6c8a93876ad52d1b44ed51cd73e94803198f6e5dc76", "query": "<ins> /* Copyright 2020 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package network import ( \"fmt\" \"strings\" \"time\" \"github.com/onsi/ginkgo\" v1 \"k8s.io/api/core/v1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/util/intstr\" clientset \"k8s.io/client-go/kubernetes\" \"k8s.io/kubernetes/test/e2e/framework\" e2enode \"k8s.io/kubernetes/test/e2e/framework/node\" e2epod \"k8s.io/kubernetes/test/e2e/framework/pod\" e2eservice \"k8s.io/kubernetes/test/e2e/framework/service\" e2eskipper \"k8s.io/kubernetes/test/e2e/framework/skipper\" ) const ( serviceName = \"svc-udp\" podClient   = \"pod-client\" podBackend1 = \"pod-server-1\" podBackend2 = \"pod-server-2\" srcPort     = 12345 ) // Linux NAT uses conntrack to perform NAT, everytime a new // flow is seen, a connection is created in the conntrack table, and it // is being used by the NAT module. // Each entry in the conntrack table has associated a timeout, that removes // the connection once it expires. // UDP is a connectionless protocol, so the conntrack module tracking functions // are not very advanced. // It uses a short timeout (30 sec by default) that is renewed if there are new flows // matching the connection. Otherwise it expires the entry. // This behaviour can cause issues in Kubernetes when one entry on the conntrack table // is never expired because the sender does not stop sending traffic, but the pods or // endpoints were deleted, blackholing the traffic // In order to mitigate this problem, Kubernetes delete the stale entries: // - when an endpoint is removed // - when a service goes from no endpoints to new endpoint // Ref: https://api.semanticscholar.org/CorpusID:198903401 // Boye, Magnus. \u201cNetfilter Connection Tracking and NAT Implementation.\u201d (2012). var _ = SIGDescribe(\"Conntrack\", func() { fr := framework.NewDefaultFramework(\"conntrack\") type nodeInfo struct { name   string nodeIP string } var ( cs                             clientset.Interface ns                             string clientNodeInfo, serverNodeInfo nodeInfo ) ginkgo.BeforeEach(func() { cs = fr.ClientSet ns = fr.Namespace.Name nodes, err := e2enode.GetBoundedReadySchedulableNodes(cs, 2) framework.ExpectNoError(err) if len(nodes.Items) < 2 { e2eskipper.Skipf( \"Test requires >= 2 Ready nodes, but there are only %v nodes\", len(nodes.Items)) } ips := e2enode.CollectAddresses(nodes, v1.NodeInternalIP) clientNodeInfo = nodeInfo{ name:   nodes.Items[0].Name, nodeIP: ips[0], } serverNodeInfo = nodeInfo{ name:   nodes.Items[1].Name, nodeIP: ips[1], } }) ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a NodePort service\", func() { // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=NodePort in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeNodePort svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"udp\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Create a pod in one node to create the UDP traffic against the NodePort service every 5 seconds ginkgo.By(\"creating a client pod for probing the service \" + serviceName) clientPod := newAgnhostPod(podClient, \"\") clientPod.Spec.NodeName = clientNodeInfo.name cmd := fmt.Sprintf(`date; for i in $(seq 1 300); do echo \"$(date) Try: ${i}\"; echo hostname | nc -u -w 5 -p %d %s %d; echo; done`, srcPort, serverNodeInfo.nodeIP, udpService.Spec.Ports[0].NodePort) clientPod.Spec.Containers[0].Command = []string{\"/bin/sh\", \"-c\", cmd} clientPod.Spec.Containers[0].Name = podClient fr.PodClient().CreateSync(clientPod) // Read the client pod logs logs, err := e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) // Add a backend pod to the service in the other node ginkgo.By(\"creating a backend pod \" + podBackend1 + \" for the service \" + serviceName) serverPod1 := newAgnhostPod(podBackend1, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels serverPod1.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod1) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{podBackend1: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod receives the traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 1 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend1) { framework.Failf(\"Failed to connecto to backend 1\") } // Create a second pod ginkgo.By(\"creating a second backend pod \" + podBackend2 + \" for the service \" + serviceName) serverPod2 := newAgnhostPod(podBackend2, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels serverPod2.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod2) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", podBackend1) fr.PodClient().DeleteSync(podBackend1, metav1.DeleteOptions{}, framework.DefaultPodDeletionTimeout) // Check that the second pod keeps receiving traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 2 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend2) { framework.Failf(\"Failed to connecto to backend 2\") } }) ginkgo.It(\"should be able to preserve UDP traffic when server pod cycles for a ClusterIP service\", func() { // Create a NodePort service udpJig := e2eservice.NewTestJig(cs, ns, serviceName) ginkgo.By(\"creating a UDP service \" + serviceName + \" with type=ClusterIP in \" + ns) udpService, err := udpJig.CreateUDPService(func(svc *v1.Service) { svc.Spec.Type = v1.ServiceTypeClusterIP svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"udp\", Protocol: v1.ProtocolUDP, TargetPort: intstr.FromInt(80)}, } }) framework.ExpectNoError(err) // Create a pod in one node to create the UDP traffic against the NodePort service every 5 seconds ginkgo.By(\"creating a client pod for probing the service \" + serviceName) clientPod := newAgnhostPod(podClient, \"\") clientPod.Spec.NodeName = clientNodeInfo.name cmd := fmt.Sprintf(`date; for i in $(seq 1 300); do echo \"$(date) Try: ${i}\"; echo hostname | nc -u -w 5 -p %d %s %d; echo; done`, srcPort, udpService.Spec.ClusterIP, udpService.Spec.Ports[0].Port) clientPod.Spec.Containers[0].Command = []string{\"/bin/sh\", \"-c\", cmd} clientPod.Spec.Containers[0].Name = podClient fr.PodClient().CreateSync(clientPod) // Read the client pod logs logs, err := e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) // Add a backend pod to the service in the other node ginkgo.By(\"creating a backend pod \" + podBackend1 + \" for the service \" + serviceName) serverPod1 := newAgnhostPod(podBackend1, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod1.Labels = udpJig.Labels serverPod1.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod1) // Waiting for service to expose endpoint. err = validateEndpointsPorts(cs, ns, serviceName, portsByPodName{podBackend1: {80}}) framework.ExpectNoError(err, \"failed to validate endpoints for service %s in namespace: %s\", serviceName, ns) // Check that the pod receives the traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 1 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend1) { framework.Failf(\"Failed to connecto to backend 1\") } // Create a second pod ginkgo.By(\"creating a second backend pod \" + podBackend2 + \" for the service \" + serviceName) serverPod2 := newAgnhostPod(podBackend2, \"netexec\", fmt.Sprintf(\"--udp-port=%d\", 80)) serverPod2.Labels = udpJig.Labels serverPod2.Spec.NodeName = serverNodeInfo.name fr.PodClient().CreateSync(serverPod2) // and delete the first pod framework.Logf(\"Cleaning up %s pod\", podBackend1) fr.PodClient().DeleteSync(podBackend1, metav1.DeleteOptions{}, framework.DefaultPodDeletionTimeout) // Check that the second pod keeps receiving traffic // UDP conntrack entries timeout is 30 sec by default ginkgo.By(\"checking client pod connected to the backend 2 on Node IP \" + serverNodeInfo.nodeIP) time.Sleep(30 * time.Second) logs, err = e2epod.GetPodLogs(cs, ns, podClient, podClient) framework.ExpectNoError(err) framework.Logf(\"Pod client logs: %s\", logs) if !strings.Contains(string(logs), podBackend2) { framework.Failf(\"Failed to connecto to backend 2\") } }) }) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-7b1ee5acca525c6b88a5b6825056ab7c4df586768503c885715c9a87d944744a", "text": "\u200d\njust saw it as well\ncan you please add links to the job with the failures, I just merged new code to improve the logging 2 days ago\nok, here there is a new occurrence and with the new debug logs is easier to follow has unreplied conntrack entries: looking at the other side The iptables rules are there but no conntrack entries related to 10.244.2.32\nIn I revert PR with debug info as I think that it likely caused significant memory growth in scalability tests, but we have one run that has finished without being killed by OOMKiller (I increased memory limit for that jobs as a mitigation). Maybe logs from this run will be useful for debugging:\nIf this issue has been triaged, please comment . If you aren't able to handle this issue, consider unassigning yourself and/or adding the label. I am a bot run by vllry. \u200d\nTwo more flakes today:\nIt seems that the packet never gets DNATed in the receiving host, so it does not reach the pod in the node. There is the same test that is using ClusterIP instead of NodePort that is more reliable. This is being a tough one\n/triage accepted\nYesterday's flake - I don't think I'm seeing the log messages from the latest log PR you made ? Or are the prow logs not logging at a high-enough level?\nLogs are there, please bear with me: The error on the test is: click on the job failure and you'll see a larger output where you can see the server pod name and get the node where the pod is running: and the client-pod name and its node: and the flow we are looking for: with the node-name we can get the kube-proxy logs there, clicking in artifacts: and you can see the \"new\" conntrack log entries : and in the client: wow, there is a kernel bug there , can it be related? :thinking:\nwohoo - some progress :) I'm not an expert here, but I think it can be? Adding here - they may be able to confirm/reject the hypothesis.\nThis kernel panic may be a coincidence, maybe this is the reason\nAdding some recent failures:\nSpotted another flake today:\nAnother flake in the 5k job:", "commid": "kubernetes_issue_91236", "tokennum": 495}], "negative_passages": []}
{"query_id": "q-en-kubernetes-92743c6358e0bad6ac9d7d238a92ee22571b88ffaefaedc04c71c8086c6a496e", "query": "return \"\", err } if _, err := os.Stat(filepath.Join(*k8sBinDir, bin)); err != nil { <del> return \"\", fmt.Errorf(\"Could not find %s under directory %s.\", bin, absPath) </del> <ins> return \"\", fmt.Errorf(\"Could not find kube-apiserver under directory %s.\", absPath) </ins> } return filepath.Join(absPath, bin), nil }", "positive_passages": [{"docid": "doc-en-kubernetes-7f95224274155bb39af2e05742451e79cefc1f176d05622797c3ba56ecf46808", "text": "is failing with: Examples:\nThis is the failing line of code...\nPASS: FAIL: Seems like this disappeared: Also this is flipped: we run the following\nmy leading theory is this is something in\nThe issue is that the above PR changed a bunch of to be and thus we no longer wait for getArchive() to complete before starting tests. And unfortunately the previous PR cannot be reverted\nAfter merging, kubelet-gce-e2e-ci still failed with the same issue. reopen the issue. Currently the failure blocked the merge-bot.\ndid stop the bleeding. Now kubelet-gce-e2e-ci is green: and merge-bot is unblocked.\nI think the \"go arc\" piece was a red herring. I suspect the issue is that the same PR tries to copy the binary into the archive directory, but PR stops building ginkgo, so the copy fails. That is why this line then fails...", "commid": "kubernetes_issue_27104", "tokennum": 203}], "negative_passages": []}
{"query_id": "q-en-kubernetes-92aba47a49f2bb5b00191424b531674b36a0131c6285e4b059d802eb0b43cfce", "query": "- Ingress - Egress ``` <ins> ### Negative caching The `denial` cache TTL has been reduced to the minimum of 5 seconds [here](https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/dns/nodelocaldns/nodelocaldns.yaml#L37). In the unlikely event that this impacts performance, setting this TTL to a higher value make help alleviate issues, but be aware that operations that rely on DNS polling for orchestration may fail (for example operators with StatefulSets). </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-598a5e6d79587d97464d296fe938aac9741dc183fde75d2da349cdf55e566259", "text": "What happened: node-local-dns caches negative queries, causing things that do polling for orchestration to fail (like operators with StatefulSets). What you expected to happen: Have a minimal TTL for negative responses (alternatively just disable caching by setting the cache size to 0) that follows what was done for kube-dns: How to reproduce it (as minimally and precisely as possible): With node-local-dns cache deployed, in my cluster it was the that failed to create clusters because the cached entry didn't expire before it had exhausted all of it's retries. Environment: Kubernetes version (use ): 1.11.6 Cloud provider or hardware configuration: GKE OS (e.g. from /etc/os-release): any Kernel (e.g. ): any\n/sig network", "commid": "kubernetes_issue_74092", "tokennum": 186}], "negative_passages": []}
{"query_id": "q-en-kubernetes-92b07e258327c702b113d679e8227626af70349fa8d0c3ba02d8de545eff6bde", "query": "if [[ \"${master}\" == \"true\" && \"${MASTER_OS_DISTRIBUTION}\" == \"gci\" ]] || [[ \"${master}\" == \"false\" && \"${NODE_OS_DISTRIBUTION}\" == \"gci\" ]]; then cat >>$file <<EOF <del> VOLUME_PLUGIN_DIR: $(yaml-quote ${VOLUME_PLUGIN_DIR:-/home/kubernetes/flexvolume}) </del> <ins> VOLUME_PLUGIN_DIR: $(yaml-quote ${VOLUME_PLUGIN_DIR:-/etc/srv/kubernetes/kubelet-plugins/volume/exec}) </ins> EOF fi", "positive_passages": [{"docid": "doc-en-kubernetes-3e146b385ed02c4a2f1c99c93d7470431d31b35da9a5c1943b70b3f73ebe8376", "text": "tests are failing atm on GCI https://k8s- because VOLUMEPLUGINDIR=/home/kubernetes/flexvolume set in takes precedence over KUBELETTESTVOLUMEPLUGINDIR=\"/etc/srv/kubernetes/kubelet-plugins/volume/exec\". As far as I can tell /home/kubernetes/flexvolume is not readable yet by containerized kubelet so the test needs to keep using \"/etc/srv/kubernetes/kubelet-plugins/volume/exec\" and the bash needs to be shuffled around to solve this. cc\n/sig storage\nThis is more an acknowledgment of the issue than anything, can't write a PR until later\ncc /kind e2e-test-failure\nthis is currently blocking alpha.3 release\nwe are just waiting for approval\nI think they\u2019re still failing, not sure what the release process is, but these tests started running only yesterday and so failure indicates something wrong with the test themselves, they shouldn\u2019t block release. (They succeed on gce cluster with Debian nodes but fail on gci)\nwell, let's see if we can get the kinks worked out before the beta release on 9/27 or we will need to disable it from release-blocking\n/assign /reopen\nI0824 17:49:28. 8562 ] operationExecutor.VerifyControllerAttachedVolume started for volume \"flex-volume-0\" (UniqueName: \"flexvolume-k8s/dummy-e2e-tests-flexvolume-wf48v/-88f4-11e7-a3f9--flex-volume-0\") pod \"flex-client\" (UID: \"-88f4-11e7-a3f9-\") edit: VerifyControllerAttachedVolume must succeed since the plugin is non-attachalbe and no error is reported. But the voluem is absent from node.volumesInUse I0824 17:44:06. 4 ] AttachVolume.Attach succeeded for volume \"flex-volume-0\" (UniqueName: \"flexvolume-k8s/dummy-attachable-e2e-tests-flexvolume-j8962/flex-volume-0\") from node \"bootstrap-e2e-minion-group-9913\" W0824 17:44:06.", "commid": "kubernetes_issue_51123", "tokennum": 562}], "negative_passages": []}
{"query_id": "q-en-kubernetes-92b07e258327c702b113d679e8227626af70349fa8d0c3ba02d8de545eff6bde", "query": "if [[ \"${master}\" == \"true\" && \"${MASTER_OS_DISTRIBUTION}\" == \"gci\" ]] || [[ \"${master}\" == \"false\" && \"${NODE_OS_DISTRIBUTION}\" == \"gci\" ]]; then cat >>$file <<EOF <del> VOLUME_PLUGIN_DIR: $(yaml-quote ${VOLUME_PLUGIN_DIR:-/home/kubernetes/flexvolume}) </del> <ins> VOLUME_PLUGIN_DIR: $(yaml-quote ${VOLUME_PLUGIN_DIR:-/etc/srv/kubernetes/kubelet-plugins/volume/exec}) </ins> EOF fi", "positive_passages": [{"docid": "doc-en-kubernetes-2c104bfa2b3eddfc8805d23cd7bd64cf6563fee869d8467e10776a93a804d4bb", "text": "4 plugin-] flexVolume driver k8s/dummy-attachable-e2e-tests-flexvolume-j8962: using default GetVolumeName for volume 0x1c5df60 I0824 17:43:59. 3728 ] operationExecutor.VerifyControllerAttachedVolume started for volume \"flex-volume-0\" (UniqueName: \"flexvolume-k8s/dummy-attachable-e2e-tests-flexvolume-j8962/flex-volume-0\") pod \"flex-client\" (UID: \"-88f3-11e7-a3f9-\") E0824 17:43:59. 3728 ] Operation for \"\"flexvolume-k8s/dummy-attachable-e2e-tests-flexvolume-j8962/flex-volume-0\"\" failed. No retries permitted until 2017-08-24 17:44:00. +0000 UTC (durationBeforeRetry 500ms). Error: Volume has not been to the list of VolumesInUse in the node's volume status for volume \"flex-volume-0\" (UniqueName: \"flexvolume-k8s/dummy-attachable-e2e-tests-flexvolume-j8962/flex-volume-0\") pod \"flex-client\" (UID: \"-88f3-11e7-a3f9-\") Seems there is something wrong with VerifyControllerAttachedVolume, still at a loss as to why it's showing up in GCI but not Debian edit: get node -o yaml shows: yet it errors because the volume hasn't been to volumesInUse??? Aug 24 20:31:42 mawong-e2e-minion-group-npjh kubelet[9431]: E0824 20:31:42. 9431 ] Operation for \"\"flexvolume-k8s/dummy-attachable-e2e-tests-flexvolume-z8xc4/flex-volume-0\"\" failed. No retries permitted until 2017-08-24 20:31:44. +0000 UTC (durationBeforeRetry 2s).", "commid": "kubernetes_issue_51123", "tokennum": 532}], "negative_passages": []}
{"query_id": "q-en-kubernetes-92b07e258327c702b113d679e8227626af70349fa8d0c3ba02d8de545eff6bde", "query": "if [[ \"${master}\" == \"true\" && \"${MASTER_OS_DISTRIBUTION}\" == \"gci\" ]] || [[ \"${master}\" == \"false\" && \"${NODE_OS_DISTRIBUTION}\" == \"gci\" ]]; then cat >>$file <<EOF <del> VOLUME_PLUGIN_DIR: $(yaml-quote ${VOLUME_PLUGIN_DIR:-/home/kubernetes/flexvolume}) </del> <ins> VOLUME_PLUGIN_DIR: $(yaml-quote ${VOLUME_PLUGIN_DIR:-/etc/srv/kubernetes/kubelet-plugins/volume/exec}) </ins> EOF fi", "positive_passages": [{"docid": "doc-en-kubernetes-522cbbb5c0d9fc5ea9cc6970c506130e31c26f402262297f89cf1b73ad15c110", "text": "Error: Volume has not been to the list of VolumesInUse in the node's volume status for volume \"flex-volume-0\" (UniqueName: \"flexvolume-k8s/dummy-attachable-e2e-tests-flexvolume-z8xc4/flex-volume-0\") pod \"flex-client\" (UID: \"-890b-11e7-9392-\")\nNever mind the GCI vs Debian issue, our test fix would have worked but in between and , something else changed and is causing both GCI and Debian tests to fail.\nmight be the cause, so we might be looking at legitimate failures caught by the test at this point (yay?) and not faulty tests. investigating...", "commid": "kubernetes_issue_51123", "tokennum": 169}], "negative_passages": []}
{"query_id": "q-en-kubernetes-92b3f3efe33931a6178c3e2997ba6b83a7e2a2dc64936e51ef2be6f23b1a6429", "query": "readonly node_logfiles=\"kube-proxy\" readonly aws_logfiles=\"cloud-init-output\" readonly gce_logfiles=\"startupscript\" <del> readonly common_logfiles=\"kern\" </del> <ins> readonly kern_logfile=\"kern\" </ins> readonly initd_logfiles=\"docker\" readonly supervisord_logfiles=\"kubelet supervisor/supervisord supervisor/kubelet-stdout supervisor/kubelet-stderr supervisor/docker-stdout supervisor/docker-stderr\"", "positive_passages": [{"docid": "doc-en-kubernetes-125faf475ef5c9fadc127cee08d3d538bc2825eff7d3fd81be9f088e2d4a0dbf", "text": "Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see ): No What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): \"LRUExpireCache\" Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT What happened: requires write lock since needs to manipulate its list to track recently used item. Currently it uses read lock so it may introduce race condition. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else do we need to know:\nThis was fixed in", "commid": "kubernetes_issue_31081", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-92b83be58a3423a3d14d59c74ecb197980725ffcd0c8783f644cff67c0cb806e", "query": "} } } <ins> func TestGetRbdImageInfo(t *testing.T) { tmpDir, err := utiltesting.MkTmpdir(\"rbd_test\") if err != nil { t.Fatalf(\"error creating temp dir: %v\", err) } defer os.RemoveAll(tmpDir) for i, c := range []struct { DeviceMountPath    string TargetRbdImageInfo *rbdImageInfo }{ { DeviceMountPath:    fmt.Sprintf(\"%s/plugins/kubernetes.io/rbd/rbd/pool1-image-image1\", tmpDir), TargetRbdImageInfo: &rbdImageInfo{pool: \"pool1\", name: \"image1\"}, }, { DeviceMountPath:    fmt.Sprintf(\"%s/plugins/kubernetes.io/rbd/mounts/pool2-image-image2\", tmpDir), TargetRbdImageInfo: &rbdImageInfo{pool: \"pool2\", name: \"image2\"}, }, } { rbdImageInfo, err := getRbdImageInfo(c.DeviceMountPath) if err != nil { t.Errorf(\"Case %d: getRbdImageInfo failed: %v\", i, err) continue } if !reflect.DeepEqual(rbdImageInfo, c.TargetRbdImageInfo) { t.Errorf(\"Case %d: unexpected RbdImageInfo, wanted %v, got %v\", i, c.TargetRbdImageInfo, rbdImageInfo) } } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-504dcfb92cdb541009bacf4c1b680d2ebe053bb62fdf81ca10ac728d32628e43", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: Pod was deleted successfully but there is still a lock on the ceph image. I find two logs,one for that lock not removed and another for that lock removed. I find that there are little difference between them. the log that lock not removed: and the log that lock removed: What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.6.7 Cloud provider or hardware configuration**: OS (e.g. from /etc/os-release): centos7 Kernel (e.g. ): 3.10.0-327.el7.x86_64 Install tools: Others:\n/sig storage\nError 16 is EBUSY. similar to\nwere you running kubelet with cadvisor on?\n/assign\nyes, every kubelet run with cadvisor,and i know what code 16 represent for,but i still don't know the reason, is this a bug? How can i avoid this kind of situation from happening,thank you\nIt is probably related to\nWe see some other case may cause , kubelet run with nodeexporter and nodeexporter is deployed by k8s daemonset with -v /:/rootfs:ro (mount kubelet host rootfs into nodeexporter container). rbd device is mounted before nodeexporter started, because k8s 1.6.7 not support mount propagation, when the rbd plugin unmount /dev/rbd0 on the host namespace, the mount info will still leave over in node_exporter container namespace, may cause . hope this would help\nthanks, does the problem persist if node_exporter stops collecting filesystem metrics?\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with .", "commid": "kubernetes_issue_54214", "tokennum": 513}], "negative_passages": []}
{"query_id": "q-en-kubernetes-92b83be58a3423a3d14d59c74ecb197980725ffcd0c8783f644cff67c0cb806e", "query": "} } } <ins> func TestGetRbdImageInfo(t *testing.T) { tmpDir, err := utiltesting.MkTmpdir(\"rbd_test\") if err != nil { t.Fatalf(\"error creating temp dir: %v\", err) } defer os.RemoveAll(tmpDir) for i, c := range []struct { DeviceMountPath    string TargetRbdImageInfo *rbdImageInfo }{ { DeviceMountPath:    fmt.Sprintf(\"%s/plugins/kubernetes.io/rbd/rbd/pool1-image-image1\", tmpDir), TargetRbdImageInfo: &rbdImageInfo{pool: \"pool1\", name: \"image1\"}, }, { DeviceMountPath:    fmt.Sprintf(\"%s/plugins/kubernetes.io/rbd/mounts/pool2-image-image2\", tmpDir), TargetRbdImageInfo: &rbdImageInfo{pool: \"pool2\", name: \"image2\"}, }, } { rbdImageInfo, err := getRbdImageInfo(c.DeviceMountPath) if err != nil { t.Errorf(\"Case %d: getRbdImageInfo failed: %v\", i, err) continue } if !reflect.DeepEqual(rbdImageInfo, c.TargetRbdImageInfo) { t.Errorf(\"Case %d: unexpected RbdImageInfo, wanted %v, got %v\", i, c.TargetRbdImageInfo, rbdImageInfo) } } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-e58e0280341e2b39cd2fb25afc5193b55cba235066305ff633e2c34889e5eefe", "text": "Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nI'm experiencing this issue. From what I can read above, if the rbd mount happens before the node_exporter starts; we'll always experience status 16?\nWe're getting this issue. This is because the mounted volume is mounted on Cadvisor container too. So the /dev/rbdX file is still in use. But still didn't find any solution to fix.\nrbd volume will stuck when failed as will always returen\nMy solution: container use a volumeMount. make a script file to be executed every a minute:", "commid": "kubernetes_issue_54214", "tokennum": 220}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9345ac39a77107687b5b29a10e081ec8110cb0ab456b04e3a850b06465c685cd", "query": "\"k8s.io/apimachinery/pkg/util/strategicpatch\" core \"k8s.io/client-go/testing\" <ins> \"time\" </ins> ) func TestRealHistory_ListControllerRevisions(t *testing.T) {", "positive_passages": [{"docid": "doc-en-kubernetes-4d5dc3f2fd1aa2418695125e98dd263b9bbd4b25db7ea8b25723d335bfe8c79b", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Statefulsets are sometimes continually rolling pods and I don't know why statefulset created: storageclass referenced: kubectl describe statefulset statefulset-test: As you can see from the above describe, the pod in the statefulset has been restarted a lot of times. Observing the created pod, 1) The pod comes up ready 2) immediately transitions to terminating 3) Is terminated 4) A new pod is created 5) Go back to (1) (repeats forever) Despite no updates to the statefulset spec ocurring. Making a change to the statefulset template (for example a trivial change adding a nonsense annotation) stops the rolling and fixes the issue When this statefulset was created, there was a mutating webhook enabled. After the observed pod rolling. I disabled this by making its configuration invalid and making it non required, and the rolling persisted. The status of the statefulset: : You can see that there is a discrepency between currentRevision and updateRevision. currentRevision: statefulset-test- updateRevision: statefulset-test- A short while later the status is changed to contain currentRevision: statefulset-test- updateRevision: statefulset-test- This change happened at Sun Apr 1 19:48:48 2018 Presumably after the rollout of statefulset-test- is complete.", "commid": "kubernetes_issue_61998", "tokennum": 342}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9345ac39a77107687b5b29a10e081ec8110cb0ab456b04e3a850b06465c685cd", "query": "\"k8s.io/apimachinery/pkg/util/strategicpatch\" core \"k8s.io/client-go/testing\" <ins> \"time\" </ins> ) func TestRealHistory_ListControllerRevisions(t *testing.T) {", "positive_passages": [{"docid": "doc-en-kubernetes-25284c3702a45280c2a40fae68a3ba4d1c026c9e5d96ab43c2dee09fe3985aa0", "text": "Here are all the controllerrevisions from above: kubectl get controllerrevision statefulset-test- -o yaml kubectl get controllerrevision statefulset-test- -o yaml: kubectl get controllerrevision statefulset-test- -o yaml: The differences between the above controllerrevisions are insignificant (the hash, the creation timestamp, the name, the resource version, the uid, the self link) Interestingly all these controllerrevisions were created very close together in time shortly after I created the statefulset The current controllerrevisions are After watching the state change for a while, it actually seems like the statefulset is just cycling through the updateRevision being one of the above 10 controllerrevisions Leaders during this time From kube-controller-manager logs during this time, here is one excerpt: The error sync in there is suspicous, and as you can see the controllerrevisions are changing in the logs I have the full logs from a 5 minute window on either side of the above if necessary. The reason I'm inclined to think this is a kubernetes bug is that any update to the statefulset template fixes the problem. How to reproduce it (as minimally and precisely as possible): Not really sure. Worth just trying to create the above statefulset (requires creating the I tried deleting and recreating the above statefulset and it didn't happen, so something flaky is going on Anything else we need to know?: kubernetes 1.9.3 (client and server) cloud provider: aws\n/sig apps\nI realize this will probably need some further debugging, happy to get some direction\nConsistent repro: Create a statefulset that creates a controllerrevision whose hash is between max int32 and max uint32 (this shouldn't be that hard to do, possibly a 50/50 chance of this). Manually create a controllerrevision identical to the first (same revision), incrementing both the name and hash by one. See that the statefulset controller will continually switch which controller revision should be the target of the statefulset.\nDue to the issue fixed here: , under some circumstances controllerrevisions whose revision is the same were being considered equal.", "commid": "kubernetes_issue_61998", "tokennum": 496}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9345ac39a77107687b5b29a10e081ec8110cb0ab456b04e3a850b06465c685cd", "query": "\"k8s.io/apimachinery/pkg/util/strategicpatch\" core \"k8s.io/client-go/testing\" <ins> \"time\" </ins> ) func TestRealHistory_ListControllerRevisions(t *testing.T) {", "positive_passages": [{"docid": "doc-en-kubernetes-59ace9008f72ca5d82f22a23445c41e6f5a4a98690d88922022af0dc9f3faebe", "text": "This ends up causing this bug to manifest as follows: ListRevisions finds many controllerrevisions with the same revision (unclear how this state happens, but it can happen) The sort here randomly sorts them Due to the linked bug , FindEqualRevisions incorrectly finds that all these controller revisions are equal to the proposed udpate. The updateRevision selects the last revision found here Therefore, updateRevision, is randomly selected and causes the bug. This fixes the immediate issue, but the sort should probably be made stable (i.e not just look at the revision number, perhaps just consider the hash for tie breakers)\nAs an update, fixing the equality check will not be sufficient because it is possible for multiple controller revisions to be created that are actually equal, including the same hash, that have the same revision number. I believe the fix will need to be equal controllerrevisions with the same revision number from being created sort the controllerrevisions so that the controllerrevision that is the target of the statefulset is stable\nIssues 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\n/remove-lifecycle stale\nping I use the K8S which version is 1.11.4 and encounter the same problem. I want to reproduce the problem and find your way: Manually create a controllerrevision identical to the first (same revision), incrementing both the name and hash by one. Could you tell me how to mannually create a same controllerrevision identical to the first? Thanks in anvance.", "commid": "kubernetes_issue_61998", "tokennum": 374}], "negative_passages": []}
{"query_id": "q-en-kubernetes-935a674b6f0846aa008c9e64c6b59be3b89ea60a35b52057b71ebf1bf3c47cef", "query": "### Hook Handler Implementations Hook handlers are the way that hooks are surfaced to containers.\u00a0 Containers can select the type of hook handler they would like to implement.\u00a0 Kubernetes currently supports two different hook handler types: <del> * Exec - Executes a specific command (e.g. pre-stop.sh) inside the cgroup and namespaces of the container.\u00a0 Resources consumed by the command are counted against the container.\u00a0 Commands which return non-zero values are treated as container failures (and will cause kubelet to forcibly restart the container).\u00a0 Parameters are passed to the command as traditional linux command line flags (e.g. pre-stop.sh --reason=HEALTH) </del> <ins> * Exec - Executes a specific command (e.g. pre-stop.sh) inside the cgroup and namespaces of the container.\u00a0 Resources consumed by the command are counted against the container.\u00a0 Commands which print \"ok\" to standard out (stdout) are treated as healthy, any other output is treated as container failures (and will cause kubelet to forcibly restart the container).\u00a0 Parameters are passed to the command as traditional linux command line flags (e.g. pre-stop.sh --reason=HEALTH) </ins> * HTTP - Executes an HTTP request against a specific endpoint on the container.\u00a0 HTTP error codes (5xx) and non-response/failure to connect are treated as container failures. Parameters are passed to the http endpoint as query args (e.g. http://some.server.com/some/path?reason=HEALTH)", "positive_passages": [{"docid": "doc-en-kubernetes-0d64a06982b9b42eb12ec4911c298e718209b3fb4fbfb723e1ec7aab0e2e7e0b", "text": "It seems that exec probes must emit \"ok\" to be considered success, rather than return 0. If this is what we really want, we should document it somewhere.\nThis is (was?) a limitation of docker exec, which didn't return the code. Brendan On Jan 28, 2015 8:38 AM, \"Tim Hockin\" wrote:\nThe doc says it looks at exit status, so we need to fix one or the other.\nfor kubelet\nfor exec\ncould you take a look at this? Feel free to re-assign it back to me.\nFWIW the current behavior isn't SO bad, and it makes clear a failure in the thing that probed vs a failed probe. Just saying, we don't NECESSARILY need to change it. On Jan 28, 2015 5:26 PM, \"Dawn Chen\" wrote:\nWith docker 1.5 we can go back to using the exitCode instead of \"ok\" string. OOM kills will also have special exitCodes in docker 1.5. , Tim Hockin wrote:\nok, I'm going to change the docs for now, we can change back when we standardize on 1.5...", "commid": "kubernetes_issue_3873", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-935a80e9380fb718b6022ed1a33deb275424039d5d4580430665f5fad71fa4a9", "query": "func rcByNameContainer(name string, replicas int, image string, labels map[string]string, c api.Container) *api.ReplicationController { // Add \"name\": name to the labels, overwriting if it exists. labels[\"name\"] = name <ins> gracePeriod := int64(0) </ins> return &api.ReplicationController{ TypeMeta: unversioned.TypeMeta{ Kind:       \"ReplicationController\",", "positive_passages": [{"docid": "doc-en-kubernetes-f3af4e5ee08342f3d9a5775ee2c1466702ed34eb1665ac9c4b71bf76c8f54023", "text": "Nodes Network when a minion node becomes unreachable [replication controller] recreates pods scheduled on the unreachable minion node AND allows scheduling of pods on a minion after it rejoins the cluster(Failed 17 times in the last 30 runs. Stability: 43 %)Failed with 0 retries\nfor triage\nI'll look into this.\nI talked to about this and he had a pretty good guess in about two seconds about what the problem is. ReplicationController sync method does this: but DaemonSet controller doesn't. (I guess when DaemonSet was copy-pasted from ReplicationController, this was accidentally removed.) Pod reflector and syncer are running in separate goroutines, and if pod reflector doesn't run then syncer will think there are no pods on the node.\nTo be clear: this is about the test Controller Manager should not create/delete replicas across restart which is the one that is actually failing.\nI'm confused you're saying that this is about , but you're updating . I thought they are about two different tests...\nYes sorry, I put my comment in the wrong issue. Reassigning this one to you, and I'll copy my comment into the other one.\nFirst failure: We check if all namespace are deleted. If other tests failed to delete their namespace this test will fail. I'm going to delete this logic as we already check if we have successfully deleted our namespace. See also for some more details.\nSecond failure: We disable network by running the following command: I checked and it seems that it results in ing master to hang. I suspect that Kubelet hangs on updating node status and depending when it breaks the connection (by timeout) it will fit in test timeouts or not.\nWhat is the default timeout for connections using client libraries to apiserver? I'm checking the code, but can't find it.\nI'm not sure if we set one, but we should. I guess I would expect to see that in the config, w/ default set by this function: , Filip Grzadkowski wrote:\nSo: let's add a timeout, and revert .\nI think that adding a timeout and reverting are orthogonal. I we want to simulate network problems with node-master communication then using REJECT is better anyway. At the same time adding timeout makes sense for many other reasons.", "commid": "kubernetes_issue_14695", "tokennum": 521}], "negative_passages": []}
{"query_id": "q-en-kubernetes-935a80e9380fb718b6022ed1a33deb275424039d5d4580430665f5fad71fa4a9", "query": "func rcByNameContainer(name string, replicas int, image string, labels map[string]string, c api.Container) *api.ReplicationController { // Add \"name\": name to the labels, overwriting if it exists. labels[\"name\"] = name <ins> gracePeriod := int64(0) </ins> return &api.ReplicationController{ TypeMeta: unversioned.TypeMeta{ Kind:       \"ReplicationController\",", "positive_passages": [{"docid": "doc-en-kubernetes-171a96c8c8138970f18a9330482c8efd4960f1ea370d03cb243605d2473f3591", "text": "OK then, let's add a timeout and test both DROP and REJECT-- no sort of network problem should hang a component.\nI think it didn't hang. It just that the kubelet was retrying too slow and sometimes it fit test timeout, sometime it didn't.\nCould we reduce the timeout to make it always fit the test timeout? , Filip Grzadkowski\nI guess we can. I'll try tomorrow.\nIt seems we have a new type of failure: It seems that kubelet on a machine where network is blocked doesn't notice new pod. After reading logs I assume that kubelet doesn't notice that the watch is broken and doesn't try to relist everything. It notices new pod only after watch timeout.\nUgh, I hope we don't have to start sending watch heartbeats.\nIt seems that all recent failures are with the following error: which means the reason is here: - can you please take a look or delegate?\nI did some more debugging of it. I was looking into this failure: There is something strange happening here: run performTemporaryNetworkFailure: succesfully block the load from kubelet: the succesfully wait for node to become not ready: some time nodecontroller successfully removes the pod: replication controller creates a new pod: here is something I don't undertand - because of some reason, the test doesn't observe that the pod actually disappeared. - any thoughts on it?\nBTW - this is exactly the same situation in:\nOK - I think this is related to default 30s deletion grace period.\nYes - it seems that this is exactly the case. I will send out PR fixing this out for review.\nI'm reopening it for tracking. If there won't be any failures within next few days - I will move the test back from flaky and close this issue.\nThanks for fixing, .\nIt seems that the main issue is fixed. However, there was one failure in the last 30 runs: in which one pod simply didn't started (and it was \"preparation\" for the test, not the test itself).\nDuring next 2 days there was exactly one more failure of this test: it is exactly the same as the previous one. However, those are duplicates of So I'm going to move this test out of flaky suite.", "commid": "kubernetes_issue_14695", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-93816507baee97d6583b60234241b114f8a7263c4e7163179ff32ca694fe2ff2", "query": "} if kernelVersion.LessThan(version.MustParseGeneric(connReuseMinSupportedKernelVersion)) { klog.ErrorS(nil, fmt.Sprintf(\"can't set sysctl %s, kernel version must be at least %s\", sysctlConnReuse, connReuseMinSupportedKernelVersion)) <ins> } else if kernelVersion.AtLeast(version.MustParseGeneric(connReuseFixedKernelVersion)) { // https://github.com/kubernetes/kubernetes/issues/93297 klog.V(2).InfoS(\"Left as-is\", \"sysctl\", sysctlConnReuse) </ins> } else { // Set the connection reuse mode if err := utilproxy.EnsureSysctl(sysctl, sysctlConnReuse, 0); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-53ca4ed8e960fbba0bd8112d5cddbb22b80695a5a78dce628bb98a2132843341", "text": "There were two patches merged recently in the kernel that will significantly improve the IPVS proxier: The first patch fixes an issue where a packet is dropped whenever a stale conntrack entry is reused. This caused a 1s delay whenever the stale conntrack entry was used. This was the original reason for setting . More details in The second patch fixes an issue when a source port is reused from a given client and the corresponding destination was deleted. This is easily reproducible when a single client sends a lot traffic to a small set of destinations and one of the destination servers are removed. More details in Based on these two patches, we should start setting (default) starting on Linux v5.9 when those two patches make it to the main line. The new sysctls for the IPVS proxier would be: We should probably wait for v5.9 before making any changes to kube-proxy, this is just a tracking issue so we don't forget.\n/sig network /area ipvs\nShould probably hold on the PR until v5.9 is released later this year. cc\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/remove-triage unresolved\nYes it makes sense to wait until a kernel with the patch exists ;) I think we can also avoid touching it and follow the approach \"only touch the sysctl we absolutely need, otherwise trust the admin to know what they need\"\nI install linux-5.9-rc2 in centos7. set /proc/sys/net/ipv4/vs/connreusemode = 1 i have three service: service-a ---service-b --service-c in k8s. service-c return \"helloworld\" I use ab to benchmark service-a. [root ~]# ab -n -c 1000 http://172.17.2.66:/ This is ApacheBench, Version 2.3 &lt;Copyright 1996 Adam Twiss, Zeus Technology Ltd, Licensed to The Apache Software Foundation, Benchmarking 172.17.2.66 (be patient) Completed 1000 requests Completed 2000 requests Completed 3000 requests Completed 4000 requests Completed 5000 requests Completed 6000 requests Completed 7000 requests Completed 8000 requests Completed 9000 requests Completed requests Finished requests Server Software: Server Hostname: 172.", "commid": "kubernetes_issue_93297", "tokennum": 506}], "negative_passages": []}
{"query_id": "q-en-kubernetes-93816507baee97d6583b60234241b114f8a7263c4e7163179ff32ca694fe2ff2", "query": "} if kernelVersion.LessThan(version.MustParseGeneric(connReuseMinSupportedKernelVersion)) { klog.ErrorS(nil, fmt.Sprintf(\"can't set sysctl %s, kernel version must be at least %s\", sysctlConnReuse, connReuseMinSupportedKernelVersion)) <ins> } else if kernelVersion.AtLeast(version.MustParseGeneric(connReuseFixedKernelVersion)) { // https://github.com/kubernetes/kubernetes/issues/93297 klog.V(2).InfoS(\"Left as-is\", \"sysctl\", sysctlConnReuse) </ins> } else { // Set the connection reuse mode if err := utilproxy.EnsureSysctl(sysctl, sysctlConnReuse, 0); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-2c3bb3dca2a83bb247d336067e1c335109a2eb22fe4a06bf3bed6ebfcc858325", "text": "17.2.66 Server Port: Document Path: / Document Length: 11 bytes Concurrency Level: 1000 Time taken for tests: 4.128 seconds Complete requests: Failed requests: 0 Write errors: 0 Total transferred: bytes HTML transferred: bytes Requests per second: 2422.76 [#/sec] (mean) Time per request: 412.753 [ms] (mean) Time per request: 0.413 [ms] (mean, across all concurrent requests) Transfer rate: 302.84 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect: 0 16 71.5 4 1004 Processing: 4 216 92.9 202 2340 Waiting: 4 215 92.7 202 2340 Total: 4 232 121.5 215 2341 Percentage of the requests served within a certain time (ms) 50% 215 66% 253 75% 280 80% 299 90% 348 95% 412 98% 490 99% 556 100% 2341 (longest request) [root ~]# ab -n -c 1000 http://172.17.2.66:/ This is ApacheBench, Version 2.3 &lt;Copyright 1996 Adam Twiss, Zeus Technology Ltd, Licensed to The Apache Software Foundation, Benchmarking 172.17.2.66 (be patient) Completed 1000 requests Completed 2000 requests Completed 3000 requests Completed 4000 requests Completed 5000 requests Completed 6000 requests Completed 7000 requests Completed 8000 requests Completed 9000 requests Completed requests Finished requests Server Software: Server Hostname: 172.17.2.66 Server Port: Document Path: / Document Length: 11 bytes Concurrency Level: 1000 Time taken for tests: 7.071 seconds Complete requests: Failed requests: 0 Write errors: 0 Total transferred: bytes HTML transferred: bytes Requests per second: 1414.21 [#/sec] (mean) Time per request: 707.110 [ms] (mean) Time per request: 0.707 [ms] (mean, across all concurrent requests) Transfer rate: 176.", "commid": "kubernetes_issue_93297", "tokennum": 429}], "negative_passages": []}
{"query_id": "q-en-kubernetes-93816507baee97d6583b60234241b114f8a7263c4e7163179ff32ca694fe2ff2", "query": "} if kernelVersion.LessThan(version.MustParseGeneric(connReuseMinSupportedKernelVersion)) { klog.ErrorS(nil, fmt.Sprintf(\"can't set sysctl %s, kernel version must be at least %s\", sysctlConnReuse, connReuseMinSupportedKernelVersion)) <ins> } else if kernelVersion.AtLeast(version.MustParseGeneric(connReuseFixedKernelVersion)) { // https://github.com/kubernetes/kubernetes/issues/93297 klog.V(2).InfoS(\"Left as-is\", \"sysctl\", sysctlConnReuse) </ins> } else { // Set the connection reuse mode if err := utilproxy.EnsureSysctl(sysctl, sysctlConnReuse, 0); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-c35c3d64a37eee54a055f855f349a29d12f9312945295419d8a667917ed08399", "text": "78 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect: 0 9 66.2 2 1019 Processing: 10 661 575.2 372 3603 Waiting: 1 659 573.7 372 3603 Total: 10 670 584.6 380 3607 Percentage of the requests served within a certain time (ms) 50% 380 66% 742 75% 1008 80% 1183 90% 1535 95% 1784 98% 2376 99% 2479 100% 3607 (longest request) [root ~]# ab -n -c 1000 http://172.17.2.66:/ This is ApacheBench, Version 2.3 &lt;Copyright 1996 Adam Twiss, Zeus Technology Ltd, Licensed to The Apache Software Foundation, Benchmarking 172.17.2.66 (be patient) Completed 1000 requests Completed 2000 requests Completed 3000 requests Completed 4000 requests Completed 5000 requests Completed 6000 requests Completed 7000 requests Completed 8000 requests Completed 9000 requests Completed requests Finished requests Server Software: Server Hostname: 172.17.2.66 Server Port: Document Path: / Document Length: 11 bytes Concurrency Level: 1000 Time taken for tests: 13.580 seconds Complete requests: Failed requests: 0 Write errors: 0 Total transferred: bytes HTML transferred: bytes Requests per second: 736.40 [#/sec] (mean) Time per request: 1357.958 [ms] (mean) Time per request: 1.358 [ms] (mean, across all concurrent requests) Transfer rate: 92.05 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect: 0 4 6.6 1 49 Processing: 11 1333 491.9 1307 3185 Waiting: 1 1330 491.9 1305 3185 Total: 17 1337 491.", "commid": "kubernetes_issue_93297", "tokennum": 404}], "negative_passages": []}
{"query_id": "q-en-kubernetes-93816507baee97d6583b60234241b114f8a7263c4e7163179ff32ca694fe2ff2", "query": "} if kernelVersion.LessThan(version.MustParseGeneric(connReuseMinSupportedKernelVersion)) { klog.ErrorS(nil, fmt.Sprintf(\"can't set sysctl %s, kernel version must be at least %s\", sysctlConnReuse, connReuseMinSupportedKernelVersion)) <ins> } else if kernelVersion.AtLeast(version.MustParseGeneric(connReuseFixedKernelVersion)) { // https://github.com/kubernetes/kubernetes/issues/93297 klog.V(2).InfoS(\"Left as-is\", \"sysctl\", sysctlConnReuse) </ins> } else { // Set the connection reuse mode if err := utilproxy.EnsureSysctl(sysctl, sysctlConnReuse, 0); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-8a42de3c47fe5733a8be9b0431ca4615a2a4c3e9126af1e5f3fc1676b07bf58b", "text": "9 1311 3191 Percentage of the requests served within a certain time (ms) 50% 1311 66% 1565 75% 1679 80% 1748 90% 1911 95% 2129 98% 2384 99% 2650 100% 3191 (longest request) [root ~]# ab -n -c 1000 http://172.17.2.66:/ This is ApacheBench, Version 2.3 &lt;Copyright 1996 Adam Twiss, Zeus Technology Ltd, Licensed to The Apache Software Foundation, Benchmarking 172.17.2.66 (be patient) Completed 1000 requests Completed 2000 requests Completed 3000 requests Completed 4000 requests Completed 5000 requests Completed 6000 requests Completed 7000 requests Completed 8000 requests Completed 9000 requests Completed requests Finished requests Server Software: Server Hostname: 172.17.2.66 Server Port: Document Path: / Document Length: 11 bytes Concurrency Level: 1000 Time taken for tests: 23.720 seconds Complete requests: Failed requests: 936 (Connect: 0, Receive: 0, Length: 936, Exceptions: 0) Write errors: 0 Total transferred: bytes HTML transferred: bytes Requests per second: 421.58 [#/sec] (mean) Time per request: 2372.009 [ms] (mean) Time per request: 2.372 [ms] (mean, across all concurrent requests) Transfer rate: 47.77 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect: 0 5 7.5 1 49 Processing: 8 2345 3364.8 333 Waiting: 0 1744 3030.9 277 Total: 8 2350 3364.8 340 Percentage of the requests served within a certain time (ms) 50% 340 66% 1434 75% 3390 80% 5490 90% 8669 95% 9233 98% 99% 100% (longest request) the last time tcp connections of service-b :\n/assign Sorry, but I do not understand what are you trying to say.", "commid": "kubernetes_issue_93297", "tokennum": 423}], "negative_passages": []}
{"query_id": "q-en-kubernetes-93816507baee97d6583b60234241b114f8a7263c4e7163179ff32ca694fe2ff2", "query": "} if kernelVersion.LessThan(version.MustParseGeneric(connReuseMinSupportedKernelVersion)) { klog.ErrorS(nil, fmt.Sprintf(\"can't set sysctl %s, kernel version must be at least %s\", sysctlConnReuse, connReuseMinSupportedKernelVersion)) <ins> } else if kernelVersion.AtLeast(version.MustParseGeneric(connReuseFixedKernelVersion)) { // https://github.com/kubernetes/kubernetes/issues/93297 klog.V(2).InfoS(\"Left as-is\", \"sysctl\", sysctlConnReuse) </ins> } else { // Set the connection reuse mode if err := utilproxy.EnsureSysctl(sysctl, sysctlConnReuse, 0); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-78960ac39e24e400e47e6916fdf5044032c9ae95fde2e36f307e50e5504537d0", "text": ": (\n/cc\nWill this be implemented in 1.21?\n/area kube-proxy\nIssues 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", "commid": "kubernetes_issue_93297", "tokennum": 81}], "negative_passages": []}
{"query_id": "q-en-kubernetes-93b1720a67957e573b7fbca288d2491833fedcc0b71eb5a798db8a3d71c07ce0", "query": "mkdir -p \"${download_path}\" if [[ $(which gsutil) ]] && [[ \"$url\" =~ ^https://storage.googleapis.com/.* ]]; then <del> gsutil cp \"${url//'https://storage.googleapis.com/'/'gs://'}\" \"${download_path}/${file}\" </del> <ins> gsutil cp \"${url//'https://storage.googleapis.com/'/gs://}\" \"${download_path}/${file}\" </ins> elif [[ $(which curl) ]]; then # if the url belongs to GCS API we should use oauth2_token in the headers curl_headers=\"\"", "positive_passages": [{"docid": "doc-en-kubernetes-3d2f3dab1a1037d1573c264392a8fb35a501948caa8df40cf12a2cd970b123e2", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --command fails because of I think the link is from k/k's Am I right?? kubetest command succeeds With installed, OR Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig release /sig testing\n/assign\nNeed cherry-picks for 1.21, 1.20 to address this. is updated but downloaded downloads and executes its /reopen\nReopened this issue. <detailsIn response to : Need cherry-picks for 1.21, 1.20 to address 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\ncc\nthis was cherry picked AFAICT, thank you!", "commid": "kubernetes_issue_102029", "tokennum": 328}], "negative_passages": []}
{"query_id": "q-en-kubernetes-93de0853518d296b8addb0a0f44e08ef96bd2464541fc7c375812a5d98ec1725", "query": "Expect(err).ToNot(HaveOccurred()) podZone := node.Labels[apis.LabelZoneFailureDomain] <del> // TODO (verult) Consider using node taints to simulate zonal failure instead. By(\"deleting instance group belonging to pod's zone\") // Asynchronously detect a pod reschedule is triggered during/after instance group deletion. waitStatus := make(chan error) go func() { waitStatus <- waitForStatefulSetReplicasNotReady(statefulSet.Name, ns, c) }() cloud, err := gce.GetGCECloud() if err != nil { Expect(err).NotTo(HaveOccurred()) } instanceGroupName := framework.TestContext.CloudConfig.NodeInstanceGroup instanceGroup, err := cloud.GetInstanceGroup(instanceGroupName, podZone) Expect(err).NotTo(HaveOccurred(), \"Error getting instance group %s in zone %s\", instanceGroupName, podZone) templateName, err := framework.GetManagedInstanceGroupTemplateName(podZone) Expect(err).NotTo(HaveOccurred(), \"Error getting instance group template in zone %s\", podZone) err = framework.DeleteManagedInstanceGroup(podZone) Expect(err).NotTo(HaveOccurred(), \"Error deleting instance group in zone %s\", podZone) </del> <ins> By(\"tainting nodes in the zone the pod is scheduled in\") selector := labels.SelectorFromSet(labels.Set(map[string]string{apis.LabelZoneFailureDomain: podZone})) nodesInZone, err := c.CoreV1().Nodes().List(metav1.ListOptions{LabelSelector: selector.String()}) Expect(err).ToNot(HaveOccurred()) removeTaintFunc := addTaint(c, ns, nodesInZone.Items, podZone) </ins> defer func() { <del> framework.Logf(\"recreating instance group %s\", instanceGroup.Name) framework.ExpectNoError(framework.CreateManagedInstanceGroup(instanceGroup.Size, podZone, templateName), \"Error recreating instance group %s in zone %s\", instanceGroup.Name, podZone) framework.ExpectNoError(framework.WaitForReadyNodes(c, nodeCount, framework.RestartNodeReadyAgainTimeout), \"Error waiting for nodes from the new instance group to become ready.\") </del> <ins> framework.Logf(\"removing previously added node taints\") removeTaintFunc() </ins> }() <del> err = <-waitStatus Expect(err).ToNot(HaveOccurred(), \"Error waiting for replica to be deleted during failover: %v\", err) </del> <ins> By(\"deleting StatefulSet pod\") err = c.CoreV1().Pods(ns).Delete(pod.Name, &metav1.DeleteOptions{}) // Verify the pod is scheduled in the other zone. By(\"verifying the pod is scheduled in a different zone.\") var otherZone string if cloudZones[0] == podZone { otherZone = cloudZones[1] } else { otherZone = cloudZones[0] } err = wait.PollImmediate(framework.Poll, statefulSetReadyTimeout, func() (bool, error) { framework.Logf(\"checking whether new pod is scheduled in zone %q\", otherZone) pod = getPod(c, ns, regionalPDLabels) nodeName = pod.Spec.NodeName node, err = c.CoreV1().Nodes().Get(nodeName, metav1.GetOptions{}) if err != nil { return false, nil } newPodZone := node.Labels[apis.LabelZoneFailureDomain] return newPodZone == otherZone, nil }) Expect(err).NotTo(HaveOccurred(), \"Error waiting for pod to be scheduled in a different zone (%q): %v\", otherZone, err) </ins> err = framework.WaitForStatefulSetReplicasReady(statefulSet.Name, ns, c, 3*time.Second, framework.RestartPodReadyAgainTimeout) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-07b454797aabeff00bf033fc34fa4c22bd06966ba8574ac0fa868459bacbceea", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: What happened: Testgrid: https://k8s-\n/assign\nThe test's assumption about test parameter is wrong. Previously it assumed the group name is the same across all zones, but they are different in regional clusters. Looking into using node taints as the permanent fix, as suggested by the TODO comment in the test.\nHm I think taint based evictions is still an alpha feature.\nOK. I propose the following solution: Get the zone of Schedule the StatefulSet pod to that zone using node affinity; wait for the pod to run Remove the node affinity from StatefulSet Delete\nCan it be simplified? Schedule the pod Figure out which zone that pod got scheduled in Delete the instance group of that zone\nUnfortunately I don't know of a good way to look up the instance group given the zone, since there could be instance groups from multiple clusters in the same project\nHow about: Schedule the pod Figure out the zone Taint all the nodes in the zone Kill the pod\nTaint with NoSchedule? yeah that sounds good", "commid": "kubernetes_issue_69005", "tokennum": 267}], "negative_passages": []}
{"query_id": "q-en-kubernetes-93f17d6e2cb4bf0817e42e37b36fef28ff5294627170246125a74f60f283597e", "query": "cp \"${src_file}\" /etc/kubernetes/manifests } <ins> # Starts k8s cluster autoscaler. start_cluster_autoscaler() { if [ \"${ENABLE_NODE_AUTOSCALER:-}\" = \"true\" ]; then # Remove salt comments and replace variables with values src_file=\"${kube_home}/kube-manifests/kubernetes/gci-trusty/cluster-autoscaler.manifest\" remove_salt_config_comments \"${src_file}\" local params=`sed 's/^/\"/;s/ /\",\"/g;s/$/\",/' <<< \"${AUTOSCALER_MIG_CONFIG}\"` sed -i -e \"s@\"{{param}}\",@${params}@g\" \"${src_file}\" sed -i -e \"s@{%.*%}@@g\" \"${src_file}\" cp \"${src_file}\" /etc/kubernetes/manifests fi } </ins> # Starts a fluentd static pod for logging. start_fluentd() { if [ \"${ENABLE_NODE_LOGGING:-}\" = \"true\" ]; then", "positive_passages": [{"docid": "doc-en-kubernetes-cafbbd3cd664270b9fbd0ce7e8faa35ad0e8800a7c5d7cdeb5164eec0f1b24f1", "text": "For some reason they stopped working and we even don't create manifest file for cluster autoscaler. I used the following command to start the cluster:\nIt's possible it's related to", "commid": "kubernetes_issue_26346", "tokennum": 40}], "negative_passages": []}
{"query_id": "q-en-kubernetes-93f38e1f38c89bf4240f1c3d70513fe4e3713350f280b631be4cfa0d14cf19a7", "query": "// Will operate in the host mount namespace if kubelet is running in a container. // Error is returned on any other error than \"file not found\". ExistsPath(pathname string) (bool, error) <ins> // EvalHostSymlinks returns the path name after evaluating symlinks. // Will operate in the host mount namespace if kubelet is running in a container. EvalHostSymlinks(pathname string) (string, error) </ins> // CleanSubPaths removes any bind-mounts created by PrepareSafeSubpath in given // pod volume directory. CleanSubPaths(podDir string, volumeName string) error", "positive_passages": [{"docid": "doc-en-kubernetes-226c0928db9d5aa6f1446838b8788eb7c60cd41b1b8246f4bd1a4e2614bb7834", "text": "/kind bug Using , if a block device is symlinked to the discovery directory e.g. , then MapVolume will fail with since the containerized kubelet cannot see the path on host. is mounted by containerized kubelet, so if before we try to map the device we set devicePath to the evaluation of symlink and end up with a devicePath of , containerized kubelet will see the device and successfully map the device. Are there any issues with this solution? This is on Kubernetes 1.10\n/sig storage\nah yes containerized kubelet has many issues when dealing with symlinks. Check out Mounter.GetMode(), it calls a nsenter EvalSymlinks which should be able to do what you need. But actually, one thing to consider, is do you need to do the losetup on the host, or does inside the container work?\nYes it appears to work from inside the container, on the host I run which disappears after I delete the pod using the device. My understanding of running losetup in MapVolume is not that great but I suppose that as long as that /dev/loop0 is created we are fine. Thanks for the quick response, I'll create a PR using that function and tag you\nDoes it create it on the host or in the containerized kubelet? What happens when containerized kubelet is restarted? The purpose of losetup is to do \"refcounting\" on the block device to prevent possible naming collisions when devices are attached/detached under unhealthy conditions. Ie, if a device showed up as /dev/sdb and you gave that to a pod, and then for some reason it become unhealthy and disappeared (while the pod is still running), another device (maybe even another volume type) could get attached to the node and reuse /dev/sdb. Now the pod has access to a device it's not supposed to. With filesystem volumes, the refcounting is done with mount points, but for block device, loopback is the equivalent.\nIt is created on the host (and also visible in the container), and stays around through restart. I understand now, thank you.\nActually after I restart it becomes /vdb instead of /dev/vdb in the losetup output, idk what that is about.", "commid": "kubernetes_issue_65445", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-93f38e1f38c89bf4240f1c3d70513fe4e3713350f280b631be4cfa0d14cf19a7", "query": "// Will operate in the host mount namespace if kubelet is running in a container. // Error is returned on any other error than \"file not found\". ExistsPath(pathname string) (bool, error) <ins> // EvalHostSymlinks returns the path name after evaluating symlinks. // Will operate in the host mount namespace if kubelet is running in a container. EvalHostSymlinks(pathname string) (string, error) </ins> // CleanSubPaths removes any bind-mounts created by PrepareSafeSubpath in given // pod volume directory. CleanSubPaths(podDir string, volumeName string) error", "positive_passages": [{"docid": "doc-en-kubernetes-e6271b0ba1dda755d5bb536a727016a621c7c29c599386bc1e9c22a230980cbf", "text": "There is no such thing as /vdb and /dev/vdb is still intact of course. Seems inconsequential since it is disappearing after all pods using the device are deleted, i.e. it's still serving as a refcounter", "commid": "kubernetes_issue_65445", "tokennum": 55}], "negative_passages": []}
{"query_id": "q-en-kubernetes-940386b6c522679b990d5f7fadeb1b62fc25bd5b14acfe2d17b7ea7267758640", "query": "func GetNodeAddresses(node *v1.Node, addressType v1.NodeAddressType) (ips []string) { for j := range node.Status.Addresses { nodeAddress := &node.Status.Addresses[j] <del> if nodeAddress.Type == addressType { </del> <ins> if nodeAddress.Type == addressType && nodeAddress.Address != \"\" { </ins> ips = append(ips, nodeAddress.Address) } }", "positive_passages": [{"docid": "doc-en-kubernetes-3fbd6fe4c52deabe3c900459c29c36a04807fdd1453263d11d2244d21f4a4f4a", "text": "Public IPs are expensive resources. Given that we're running scalability tests on 5k-node clusters, we are unnecessarily consuming 5k IPs which is a lot. We should switch our tests so that nodes have only private IP addresses. We are going to do that by configuring NAT so that nodes can talk to outside world (e.g. to download image from dockerhub). But that also requires changing some correctness tests which assume public IPs.\nTo summarize recent work: setting up private gce clusters with nat, feature is gated via the env test and dashboard with correctness tests on gce private cluster - https://k8s- 27 tests fail on fixing the tests - should fix majority of them\nIssues 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\n/remove-lifecycle stale /lifecycle frozen\n- is there anything missing to be done here?\nNo, we can close this one. It was done long time ago. Thanks for catching /close\nClosing this issue. <detailsIn response to : No, we can close this one. It was done long time ago. Thanks for catching 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", "commid": "kubernetes_issue_76374", "tokennum": 335}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9405089d2ba195518d1beb276e12e7a4e5ff9eefeb639d3fd71b09ed628b780e", "query": "// SortControllerRevisions sorts revisions by their Revision. func SortControllerRevisions(revisions []*apps.ControllerRevision) { <del> sort.Sort(byRevision(revisions)) </del> <ins> sort.Stable(byRevision(revisions)) </ins> } // EqualRevision returns true if lhs and rhs are either both nil, or both point to non-nil ControllerRevisions that", "positive_passages": [{"docid": "doc-en-kubernetes-4d5dc3f2fd1aa2418695125e98dd263b9bbd4b25db7ea8b25723d335bfe8c79b", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Statefulsets are sometimes continually rolling pods and I don't know why statefulset created: storageclass referenced: kubectl describe statefulset statefulset-test: As you can see from the above describe, the pod in the statefulset has been restarted a lot of times. Observing the created pod, 1) The pod comes up ready 2) immediately transitions to terminating 3) Is terminated 4) A new pod is created 5) Go back to (1) (repeats forever) Despite no updates to the statefulset spec ocurring. Making a change to the statefulset template (for example a trivial change adding a nonsense annotation) stops the rolling and fixes the issue When this statefulset was created, there was a mutating webhook enabled. After the observed pod rolling. I disabled this by making its configuration invalid and making it non required, and the rolling persisted. The status of the statefulset: : You can see that there is a discrepency between currentRevision and updateRevision. currentRevision: statefulset-test- updateRevision: statefulset-test- A short while later the status is changed to contain currentRevision: statefulset-test- updateRevision: statefulset-test- This change happened at Sun Apr 1 19:48:48 2018 Presumably after the rollout of statefulset-test- is complete.", "commid": "kubernetes_issue_61998", "tokennum": 342}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9405089d2ba195518d1beb276e12e7a4e5ff9eefeb639d3fd71b09ed628b780e", "query": "// SortControllerRevisions sorts revisions by their Revision. func SortControllerRevisions(revisions []*apps.ControllerRevision) { <del> sort.Sort(byRevision(revisions)) </del> <ins> sort.Stable(byRevision(revisions)) </ins> } // EqualRevision returns true if lhs and rhs are either both nil, or both point to non-nil ControllerRevisions that", "positive_passages": [{"docid": "doc-en-kubernetes-25284c3702a45280c2a40fae68a3ba4d1c026c9e5d96ab43c2dee09fe3985aa0", "text": "Here are all the controllerrevisions from above: kubectl get controllerrevision statefulset-test- -o yaml kubectl get controllerrevision statefulset-test- -o yaml: kubectl get controllerrevision statefulset-test- -o yaml: The differences between the above controllerrevisions are insignificant (the hash, the creation timestamp, the name, the resource version, the uid, the self link) Interestingly all these controllerrevisions were created very close together in time shortly after I created the statefulset The current controllerrevisions are After watching the state change for a while, it actually seems like the statefulset is just cycling through the updateRevision being one of the above 10 controllerrevisions Leaders during this time From kube-controller-manager logs during this time, here is one excerpt: The error sync in there is suspicous, and as you can see the controllerrevisions are changing in the logs I have the full logs from a 5 minute window on either side of the above if necessary. The reason I'm inclined to think this is a kubernetes bug is that any update to the statefulset template fixes the problem. How to reproduce it (as minimally and precisely as possible): Not really sure. Worth just trying to create the above statefulset (requires creating the I tried deleting and recreating the above statefulset and it didn't happen, so something flaky is going on Anything else we need to know?: kubernetes 1.9.3 (client and server) cloud provider: aws\n/sig apps\nI realize this will probably need some further debugging, happy to get some direction\nConsistent repro: Create a statefulset that creates a controllerrevision whose hash is between max int32 and max uint32 (this shouldn't be that hard to do, possibly a 50/50 chance of this). Manually create a controllerrevision identical to the first (same revision), incrementing both the name and hash by one. See that the statefulset controller will continually switch which controller revision should be the target of the statefulset.\nDue to the issue fixed here: , under some circumstances controllerrevisions whose revision is the same were being considered equal.", "commid": "kubernetes_issue_61998", "tokennum": 496}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9405089d2ba195518d1beb276e12e7a4e5ff9eefeb639d3fd71b09ed628b780e", "query": "// SortControllerRevisions sorts revisions by their Revision. func SortControllerRevisions(revisions []*apps.ControllerRevision) { <del> sort.Sort(byRevision(revisions)) </del> <ins> sort.Stable(byRevision(revisions)) </ins> } // EqualRevision returns true if lhs and rhs are either both nil, or both point to non-nil ControllerRevisions that", "positive_passages": [{"docid": "doc-en-kubernetes-59ace9008f72ca5d82f22a23445c41e6f5a4a98690d88922022af0dc9f3faebe", "text": "This ends up causing this bug to manifest as follows: ListRevisions finds many controllerrevisions with the same revision (unclear how this state happens, but it can happen) The sort here randomly sorts them Due to the linked bug , FindEqualRevisions incorrectly finds that all these controller revisions are equal to the proposed udpate. The updateRevision selects the last revision found here Therefore, updateRevision, is randomly selected and causes the bug. This fixes the immediate issue, but the sort should probably be made stable (i.e not just look at the revision number, perhaps just consider the hash for tie breakers)\nAs an update, fixing the equality check will not be sufficient because it is possible for multiple controller revisions to be created that are actually equal, including the same hash, that have the same revision number. I believe the fix will need to be equal controllerrevisions with the same revision number from being created sort the controllerrevisions so that the controllerrevision that is the target of the statefulset is stable\nIssues 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\n/remove-lifecycle stale\nping I use the K8S which version is 1.11.4 and encounter the same problem. I want to reproduce the problem and find your way: Manually create a controllerrevision identical to the first (same revision), incrementing both the name and hash by one. Could you tell me how to mannually create a same controllerrevision identical to the first? Thanks in anvance.", "commid": "kubernetes_issue_61998", "tokennum": 374}], "negative_passages": []}
{"query_id": "q-en-kubernetes-94db617fac4b7006c1c59d42d7d889bebe5ab182b326ab066c1c80a30992d1a6", "query": "embed = [\":go_default_library\"], deps = [ \"//pkg/kubelet/cri/remote/fake:go_default_library\", <ins> \"//pkg/kubelet/cri/remote/util:go_default_library\", </ins> \"//staging/src/k8s.io/cri-api/pkg/apis:go_default_library\", \"//staging/src/k8s.io/cri-api/pkg/apis/testing:go_default_library\", \"//vendor/github.com/stretchr/testify/assert:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-a55cc9cf23a1aa66af6ba96638da8c1361b9b34938bf9fbe2ee98dcb858f1383", "text": "Which jobs are flaking: periodics-kubernetes-bazel-test Which test(s) are flaking: //pkg/kubelet/cri/remote TestVersion Testgrid link: Reason for failure: Error: Received unexpected error: rpc error: code = Unavailable desc = transport is closing panic: runtime error: invalid memory address or nil pointer dereference [recovered] panic: runtime error: invalid memory address or nil pointer dereference Anything else we need to know: To reproduce with stress: go test -race -c ./pkg/kubelet/cri/remote stress - TestVersion Detailed logs\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig testing\nI 'll give it a see and fix it :)\n/assign\n/remove-sig testing SIG node owns their unit tests. SIG testing owns the framework, infrastructure, etc.\n/sig node", "commid": "kubernetes_issue_96950", "tokennum": 277}], "negative_passages": []}
{"query_id": "q-en-kubernetes-95228b5a246acc6e8b3f998063e1338e38a2572a47c77a724112c9e857597e71", "query": "cmd.SetUsageFunc(func(cmd *cobra.Command) error { fmt.Fprintf(cmd.OutOrStderr(), usageFmt, cmd.UseLine()) cliflag.PrintSections(cmd.OutOrStderr(), namedFlagSets, cols) <ins> cliflag.PrintSections(cmd.OutOrStderr(), additionalFlags, cols) </ins> return nil }) cmd.SetHelpFunc(func(cmd *cobra.Command, args []string) { fmt.Fprintf(cmd.OutOrStdout(), \"%snn\"+usageFmt, cmd.Long, cmd.UseLine()) cliflag.PrintSections(cmd.OutOrStdout(), namedFlagSets, cols) <ins> cliflag.PrintSections(cmd.OutOrStdout(), additionalFlags, cols) </ins> }) return cmd", "positive_passages": [{"docid": "doc-en-kubernetes-9f300d1173b6c69710c4c78dc86f3d1b70206f2452121d5fb8dd9b7678b638cc", "text": "The function in accepts an parameter which it describes as a way to \"controller specific flags to be included in the complete set of controller manager flags\". However, when the usage string is shown (either via or when parsing options fails), these additional options are not included in the usage string. This was identified via code inspection while trying to figure out what options did in . For e.g. , the output of should include a section corresponding to . This section should in turn list all of . a cloud provider executable that includes additional options, such as the additional options are not shown in the output No response_ n/a (all cloud providers are affected) n/a n/a n/a n/a\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig cloud-provider", "commid": "kubernetes_issue_120522", "tokennum": 240}], "negative_passages": []}
{"query_id": "q-en-kubernetes-95265eace8ca3a2e32f22c55fb2c1b018bccf45fb59bfaf772e40ea87b1eb6f8", "query": "return p.Attach.Attach(\"POST\", req.URL(), p.Config, p.In, p.Out, p.Err, t.Raw, sizeQueue) } <ins> if !p.Quiet && stderr != nil { fmt.Fprintln(stderr, \"If you don't see a command prompt, try pressing enter.\") } </ins> if err := t.Safe(fn); err != nil { return err }", "positive_passages": [{"docid": "doc-en-kubernetes-cf7ef9edd7e31f4b8286dd6738f8e55df1658c21b56557082b0f1b4070aed850", "text": "First, the formatting. Second, \"init-ctr-demo_demos\" is an internal artifact, not fit for human-facing errors. Third, the container DOES exist, it's just in a terminating state.\nThe formatting issue should be fixed by . Regarding to the pod name, I think is better. As for the pod name, the error message is from the HTTP response of kubelet server. I've looked at the code, functions defined in interface are using ($podName_podNamespace) to identify a pod. Without spiting the parameter into two separated parameters, it could be tricky to change the output format of an error message. Personally I would prefer to change the signatures, but I don't know if we are planing to do it. In order to improve the readability, I a client-side check for pod status. See .", "commid": "kubernetes_issue_56450", "tokennum": 184}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9543782f9f12fa4559a6dede0c9ffea8636fbf6ca800c33763147df6802a3ef4", "query": "deps = [ \"//pkg/kubelet/container:go_default_library\", \"//pkg/kubelet/container/testing:go_default_library\", <ins> \"//pkg/kubelet/metrics:go_default_library\", </ins> \"//staging/src/k8s.io/apimachinery/pkg/types:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/util/clock:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/util/diff:go_default_library\", <ins> \"//vendor/github.com/prometheus/client_model/go:go_default_library\", </ins> \"//vendor/github.com/stretchr/testify/assert:go_default_library\", ], )", "positive_passages": [{"docid": "doc-en-kubernetes-3f173d1022a4408031efac17c8299f04d835794ab8a77d69bb7667b0107a08bf", "text": "Some kubelet metrics use non-standard prometheus collectors unnecessarily. Specifically, we have which can be simple gauges. Since we cannot migrate non-standard prometheus collectors using the internal metrics stability framework, we will need to convert these metrics into standard prometheus variants. /sig instrumentation /assign\nGitHub didn't allow me to assign the following users: solodov. Note that only and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : Some kubelet metrics use non-standard prometheus collectors unnecessarily. Specifically, we have which can be simple gauges. Since we cannot migrate non-standard prometheus collectors using the internal metrics stability framework, we will need to convert these metrics into standard prometheus variants. /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\nrecommends that we generate those metrics in the GenericPLEG during the relist. We can generate the data directly from the pods call there ().\nI would be interested to work on this issue if no one else is working on it currently\nGo for it!\n/assign", "commid": "kubernetes_issue_79286", "tokennum": 282}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9577c72f65cedc865808a3680255942f22d772b914ee857d864a9bad5f14d58b", "query": "\"k8s.io/klog\" ) <ins> var ( // ErrorNoAuth indicates that no credentials are provided. ErrorNoAuth = fmt.Errorf(\"no credentials provided for Azure cloud provider\") ) </ins> // AzureAuthConfig holds auth related part of cloud config type AzureAuthConfig struct { // The cloud environment identifier. Takes values from https://github.com/Azure/go-autorest/blob/ec5f4903f77ed9927ac95b19ab8e44ada64c1356/autorest/azure/environments.go#L13", "positive_passages": [{"docid": "doc-en-kubernetes-effe9bff1df2586252b385cbf4a7cacd04cb77f4739ff9c987e63818f9dc1c82", "text": "Currently there is no way to run without any identity (be it service principal or E/MSI). In reality code running on a worker node can use via - and only via - without the need to access ARM. Here is the proposed change a new mode authN = this mode, is basically telling the cloud provider to work any identity, this means only IMDS calls is allowed. This mode can be detected from if no SPN set and both MSI settings are set to . to use a config map within the cluster. This config map can be loaded on the cluster statically. or created - if not existent - in that then only is used in The net new result of the above is users bootstrapping clusters can configure the worker node to use without any identity on said worker nodes.\n/sig azure These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by \u200d\nIn-tree AzureDisk volume plugin is also depending on Azure credential to fetch lun id. we should figure out how to solve it without credential\nfetch disk lun id is also a dependency in kubelet code now, after my investigation, it could be removed on Linux node, while it cannot be removed on Windows node, need to change the k/k upstream code, there is a discussion on going here: , let' wait for the discussion result.\nFor Linux: 1- use IMDS my understanding is new api versions will have the disk/lun pairs. 2- don't use arm for the return of is the second parameter passed to . For Windows: I don't understand the dep on ARM for this. The above still apply, we just need to find a way to encode the value as ut return from that allow us to find the disk by on a windows machine. might be a good source for this. Ideally speaking. The value should be the same. But i will leave it for you to decide.\ncould be a good idea since currently it's a LUN num returned by Attach() and then it could be changed to the windows disk num, I will make the code change on v1.15 later, thanks for discussion.\nUpdate: PR would remove the VM API calls when getting the LUN number for AzureDisk.", "commid": "kubernetes_issue_77309", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-957f071ab3f013c13c1c88a8acf4e4c91db5f2282d8403e1158f3355d77c438c", "query": "Containers: []v1.Container{ { Image: image.GetE2EImage(), <del> Name:  podName, </del> <ins> Name:  \"stat-container\", </ins> Command: []string{ \"powershell.exe\", \"-Command\",", "positive_passages": [{"docid": "doc-en-kubernetes-e89d62bf4b636217c9a329c55c70299ddc99e1e546e8bf63873df452671a65c2", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: aks-engine-azure-windows-master-containerd-serial-slow Which test(s) are failing: [sig-windows] [Feature:Windows] Kubelet-Stats [Serial] Kubelet stats collection for Windows nodes when running 10 pods should return within 10 seconds Since when has it been failing: Unknown. Testgrid link: Reason for failure: The test spawns 10 pods with the same pod name, which contains multiple containers with the same container name. Because of this, the test fails. Logs: Anything else we need to know:\n/sig windows These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by vllry. \u200d", "commid": "kubernetes_issue_91677", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-95c3538aa6ab8387bc6396ea14c9edbaa931ecfdc8d673546b640129e05637f9", "query": "GetProtocol() v1.Protocol // GetHealthCheckNodePort returns service health check node port if present.  If return 0, it means not present. GetHealthCheckNodePort() int <ins> // GetNodePort returns a service Node port if present. If return 0, it means not present. GetNodePort() int </ins> } // Endpoint in an interface which abstracts information about an endpoint.", "positive_passages": [{"docid": "doc-en-kubernetes-9e39524d0e4c89f1ddf9c516fe4e1c471a25826ee6b222abfe1f6c0cc213064c", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: BUG REPORT What happened: When deleting/recreating pods backing a UDP service, traffic from external senders stops flowing. What you expected to happen: Traffic would continue to flow to new pods. How to reproduce it (as minimally and precisely as possible): Based on reading of similar issues and commit messages it seems like this would be most noticable on high-volume UDP applications, statsd and syslog are good examples. a deployment and service for a UDP app. In my test case, this would be the container. an external node, create a small test script utilizing a statsd library such as pystatsd. The most important part is that the sender uses the same source-port for every packet sent. Ex: the sender. Install tcpdump into the pod and watch for incoming packets, example from the test case: the pod tcpdump in the newly created pod. Observe that no new matching packets are flowing. existing conntrack rules on all nodes in the cluster. You should see traffic start flowing to the pod again. example command for clearing conntrack rules on the nodes: Anything else we need to know?: I have tested this only on GKE-managed clusters that utilize google forwarding-rules for external LBs, but I believe the issue may be present on any platform where iptables mode for kube-proxy is used. Tested and verified on 1.8.6-gke.0 and 1.7.11-gke.1. Also tested with both Google Container-optimized OS and the Ubuntu-based node images. I have only test this on GKE It appears this was a known issue and should have been cleared up by: From my reading of , it seems as if the func should exec() to clear up UDP entries on service endpoint change, but the only place I see that func called is from syncProxyRules(). That func looks complex and possibly like it is only run occasionally and not on service/endpoint changes. Environment: Kubernetes version (use ): (Also tested on 1.7.11-gke.1) Cloud provider or hardware configuration: GKE-managed clusters, google cloud. OS (e.g.", "commid": "kubernetes_issue_59368", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-95c3538aa6ab8387bc6396ea14c9edbaa931ecfdc8d673546b640129e05637f9", "query": "GetProtocol() v1.Protocol // GetHealthCheckNodePort returns service health check node port if present.  If return 0, it means not present. GetHealthCheckNodePort() int <ins> // GetNodePort returns a service Node port if present. If return 0, it means not present. GetNodePort() int </ins> } // Endpoint in an interface which abstracts information about an endpoint.", "positive_passages": [{"docid": "doc-en-kubernetes-27a4c6cdabc82c95dde932bb7bf1e1865b5f691c3b3e7bf1ed0c71bfc361fddc", "text": "from /etc/os-release): tried both: and Kernel (e.g. ): and Install tools: Others:\n/sig network\nWe also ran into this in kubernetes v1.7.6 using OpenShift 3.7:\n~I believe this is the same as ~If so, it is fixed in 1.10: These are about HostPort, not NodePort, sorry for the noise.\nIssues 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\nIs there any other known workaround for this besides updating conntrack rules on the kube nodes? I tried deleting and recreating the service, but this didn't update the rules. When I restart the stream on the client side data flows correctly again (perhaps it's perceived as a new connection), but I have to restart the stream for each sender.\n/remove-lifecycle stale\nFWIW, this is not fixed in 1.10 - that fix was for HostPort, and this is still a bug for NodePort.\nI am seeing this issue in 1.11. I am using LoadBalancer type.\nhas been working on a fix for this, FYI.\nThis issue is extremely impactful for telephony protocols that rely on static source ip and source port. Any update on a possible workaround? I was thinking a potential workaround might be to reduce the UDP timeout to something really short so the stale conntrack entries go away faster. Or maybe there is a way to flush conntrack on the event of pod deletion? Edit: Removed stupid idea of a workaround to disable conntrack for UDP. Can't disable conntrack for UDP because it's used for DNAT from node to container.\nThe workaround is to not use NodePorts. Other kinds of services are already correct.\nnot sure what you mean. I am seeing the issue with a LoadBalancer type so it does not affect NodePorts only. As a workaround I have created a small python script that watches the K8s API for pod deletions and clears the related conntrack entries when that happens. I can share it when I get to work on Monday if you want to try it out.", "commid": "kubernetes_issue_59368", "tokennum": 535}], "negative_passages": []}
{"query_id": "q-en-kubernetes-95c3538aa6ab8387bc6396ea14c9edbaa931ecfdc8d673546b640129e05637f9", "query": "GetProtocol() v1.Protocol // GetHealthCheckNodePort returns service health check node port if present.  If return 0, it means not present. GetHealthCheckNodePort() int <ins> // GetNodePort returns a service Node port if present. If return 0, it means not present. GetNodePort() int </ins> } // Endpoint in an interface which abstracts information about an endpoint.", "positive_passages": [{"docid": "doc-en-kubernetes-956c9b1270ab4e0eb744fb5e7c207e8e7b7c0a49e83c634550198bfe9b333eeb", "text": "I've my script . Note that it's not tested much so don't use it in a production environment. Also it cleans up all conntrack entries for a deleted pod, not only the UDP related ones.\nWe are also seeing this issue with type loadbalancer. We are on 1.11. Our use-case is the following: multiple devices are sending to an aggreagator machine. This machine forwards the UDP packages to a loadBalancer in gcp. When debugging the service, I noticed the following: The traffic is assigned to one pod, and the packages are not loadbalanced (client and server are the same cfr use-case) When redeploying a new cluster, Conntrack is cleared on termination signal of the old pod. (client receives connection refused) red/black and highlander deployment strategies have the same effect. How would I expect this to be working then? New cluster is . Conntrack is cleared Data is routed to NEW pods old pods are terminated Best Regards, Tim\nI am seeing this exact same issue on our cluster which has k8s v1.14.5 . We have endpoint nginx pods backing a UDP service with nodeport. Suddenly one day we see traffic not hitting into nginx pod but reaching the node hosting the nginx pod. We could simulate the problem by restarting the nginx pods. I am assuming with this issue marked as closed; and having made its way into v1.14; we should not be seeing this. Would also like to point out; the one thing, in addition we have in the service is ExternalTrafficPolicy set to Local. Can anyone please guide/help on why we are seeing this in v.1.14.5 of our cluster.\nSeeing this with k8s v1.16.5", "commid": "kubernetes_issue_59368", "tokennum": 391}], "negative_passages": []}
{"query_id": "q-en-kubernetes-95c58e1230e051455e52970857e78f2c2a51ca86f779d02394eca54298f5f413", "query": "timedout := make(chan bool) go func() { time.Sleep(gracefulWait) <del> timedout <- true </del> <ins> close(timedout) </ins> }() go func() { select {", "positive_passages": [{"docid": "doc-en-kubernetes-f2910a5a7757744dd88700c551fb3f5fe81db92c4ae532e768f1444ef3ba7b10", "text": "It's at line 111 When the server stopped before timeout, the first goroutine will be block on because the receiver in the second goroutine is not exist. Changing to a buffered one may fix it. no goroutine leaks run related test with leak checker No response <detailsdev </details<detailsunknown </details<details</details<details</details<details</details<details</details\n/sig api-machinery\n/assign /triage accepted\n/cc\nIt should close the channel rather than write to it, that's the easiest fix", "commid": "kubernetes_issue_114070", "tokennum": 125}], "negative_passages": []}
{"query_id": "q-en-kubernetes-95df3ef735676da7abf5dda22ef31f3b5764483ebf74ad4e263e015f69503fc5", "query": "import ( \"fmt\" \"os\" <ins> \"path/filepath\" </ins> \"strings\" \"github.com/golang/glog\"", "positive_passages": [{"docid": "doc-en-kubernetes-9100812604bb274f029e79ebee13bfe2ce369a45e8a3a70a5fa62bc6c27fbac5", "text": "<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.--Is this a request for help? No What keywords did you search in Kubernetes issues before filing this one? static manifest Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug report Kubernetes version (use ): Environment: Cloud provider or hardware configuration: Bare metal and reproduced in Vagrant OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: custom scratch install and reproduced with kubeadm Others: Calico for networking. Used (Also able to reproduce without calico) What happened: Modified one of the static manifest files in . The kubelet killed the running pod and did NOT create a new pod. (waited 30 minutes, still no pod) What you expected to happen: Kubelet should have killed the pod and started a new one. How to reproduce it (as minimally and precisely as possible): Started with single node, vanilla Ubuntu Xenial, installed kubernetes via kubeadm, nothing special. Modify , for example change the logging level or even just whitespace at the end of the file. Observe the kubelet kill the controller manager pod, and does not restart it. Anything else we need to know: If I remove the file from the directory, and then replace the file, kubelet will start it up. Kubelet logs from the period where I updated the file:\nDid you modify the yaml file using an editor (e.g., vim)? If the editor creates a temporary file in the same directory, kubelet can get confused and thinking that's a new pod (with the same name & namespace). When the temporary file gets removed, kubelet'd inadvertently delete the pod from its cache. Since kubelet relies on inotify for changes, if it doesn't get notified for any new changes from the original yaml file, it'd forever ignore the pod. There is an issue open to add periodic listing in addition to inotify (introduced in 1.5). This would make sure kubelet eventually recover from the situation. I can't find the issue, but there is another one for inotify: . Another fix is to make sure kubelet ignore such known temporary files (it already ignores files starting with ). In general, don't edit the file directly.", "commid": "kubernetes_issue_44450", "tokennum": 525}], "negative_passages": []}
{"query_id": "q-en-kubernetes-95df3ef735676da7abf5dda22ef31f3b5764483ebf74ad4e263e015f69503fc5", "query": "import ( \"fmt\" \"os\" <ins> \"path/filepath\" </ins> \"strings\" \"github.com/golang/glog\"", "positive_passages": [{"docid": "doc-en-kubernetes-0117d4a9a190c22a46ca0d65f470fd275b0d70394b42857314fa11d87e816ed2", "text": "Copy the file to another place, edit, and copy it back to the manifests directory.\nI'm seeing a similar problem except I never edited the file, might be fit for a separate issue\nYes I was using vim, and this explanation makes sense. Would be nice if it was smart about it. Would a PR to ignore the vim temp file be acceptable\nI think it's reasonable. I doubt if anyone uses those file names on purpose.\nThe dot ignore should have covered the vim temp file too, but it doesn't work because the filename passed in is the absolute filename including the path. So the first character is not a dot. I'll try to submit a PR fix.\nPR submitted\nfixed?\nHow to work around? I coudn't start api server when using kubeadm to deploy k8s. Thanks!", "commid": "kubernetes_issue_44450", "tokennum": 180}], "negative_passages": []}
{"query_id": "q-en-kubernetes-961763de8b7afa4c0b02b8b173c4aca9ed5c1249b2b8cf1db5662f4b6843feee", "query": "}) It(\"verify monitoring pods and all cluster nodes are available on influxdb using heapster.\", func() { <del> if testContext.Provider != \"gce\" { </del> <ins> if !providerIs(\"gce\") { </ins> By(fmt.Sprintf(\"Skipping Monitoring test, which is only supported for provider gce (not %s)\", testContext.Provider)) return", "positive_passages": [{"docid": "doc-en-kubernetes-5702d542be386cac9e4333778515fd94620fcdb52c66d8dfc11487da78971dda", "text": "I noticed while running e2e tests locally that some tests were apparently being incorrectly skipped: I checked, and this is also true for our Jenkins runs. Currently it looks like and have this bug, though only the former actually skips the test, I think. The issue appears to be that the code inside the top-level in these files is being run before the testContext struct is filled out (and before is even called), and so testContext.Provider is empty. I'm not immediately sure what the proper fix is; I'm also worried that there might be other things broken by the fact that these blocks are called before initialization is complete. We also probably investigate if there is a better way to mark these tests as skipped; right now, there's no indication in the test report (, Jenkins test report, etc) that these tests were skipped.\nI merged and which tried to disable these tests for non-{gke,gce} but apparently didn't follow-up and verify that they were still running on our platforms. /cc\nSeems easy enough to fix. I'll have a PR out to fix this before Monday.", "commid": "kubernetes_issue_7008", "tokennum": 242}], "negative_passages": []}
{"query_id": "q-en-kubernetes-961ac5c2985441ac4ed7f0ecc434c3f823b052e5b259095d44f5a34126863c8d", "query": "serviceConfig.RegisterEventHandler(s.Proxier) go serviceConfig.Run(wait.NeverStop) <del> if utilfeature.DefaultFeatureGate.Enabled(features.EndpointSlice) { </del> <ins> if s.UseEndpointSlices { </ins> endpointSliceConfig := config.NewEndpointSliceConfig(informerFactory.Discovery().V1beta1().EndpointSlices(), s.ConfigSyncPeriod) endpointSliceConfig.RegisterEventHandler(s.Proxier) go endpointSliceConfig.Run(wait.NeverStop)", "positive_passages": [{"docid": "doc-en-kubernetes-94306baf6d6408dd320a641269af3f429c4d2a949a311ade7ed7994b23100633", "text": "After this () has been merged and EnpointSlice feature is now enabled by default, we noticed Kube-proxy will not work on Windows. Only message I can see in the logs is: /sig windows\n/cc /cc /cc\nHow about separating the above check into two if statements so that the log can pinpoint which field is false ?\nIt seems long term, EndpointSlice support should be so that is kept in sync with other implementations.\ncc\nThanks for reporting this! Windows proxiers were still intended to be reading from Endpoints, but apparently that's not working as intended. EndpointSlices are moving back to disabled by default for 1.17, so that should fix the failing tests for now. I'll work on an actual fix for this as well, but it may not make it in until after KubeCon. /assign /sig network /priority important-soon\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/remove-triage unresolved\n/assign cc\nGitHub didn't allow me to assign the following users: jocelynberrendonner. 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 cc 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\n: Please let me know if you need any help on the fix! I'll be more than happy to review/help test the fix on Windows.", "commid": "kubernetes_issue_85352", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-96452bb278782147452f76fa8973789650a789cd6eac47a241599f2239b2c129", "query": "annotations: storageclass.beta.kubernetes.io/is-default-class: \"true\" labels: <del> addonmanager.kubernetes.io/mode: Reconcile </del> <ins> addonmanager.kubernetes.io/mode: EnsureExists </ins> provisioner: kubernetes.io/host-path", "positive_passages": [{"docid": "doc-en-kubernetes-942aeb92abd77b2734de9fd7148076d7883d9fdc897495b27676df96d5abc03a", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: What happened: Not able to change the default storage class. What you expected to happen: Default storage class to change. How to reproduce it (as minimally and precisely as possible): But after few mins. Anything else we need to know?: Tried to remove the annotation but no luck. Environment: Kubernetes version (use ):Cloud provider or hardware configuration: minikube OS (e.g. from /etc/os-release): Buildroot 2018.05 Kernel (e.g. ): 4.16.14 Install tools: minikube Others:\n/assign\nThose labels are not set on the issue: <detailsIn response to : /remove-sig api-machinery 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\n/sig cluster-lifecycle\nThe cause is that kube-addon-manager is reconciling the standard storage class.\nThose labels are not set on the issue: <detailsIn response to : /remove-sig api-machinery 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\nThanks for looking into it. Sorry for native question, I want to keep only ceph as a default storage class how can I do that?\nhi I'm not really sure about the actual command to fix this. Basically, you could log into the VM and do the same modification as the PR above does, then restart minikube.\nHas the fix made it into minikube yet? I'm still seeing the issue in 0.31.0\nLooking at PR , the fix was made in kubernetes core, not minikube. The error still exists in minikube:", "commid": "kubernetes_issue_66222", "tokennum": 440}], "negative_passages": []}
{"query_id": "q-en-kubernetes-96a58620b58fcfcd6bc0773da4a5dc959037b7274515deb88f78ae5f902afaa6", "query": "get(t, \"valid TLS cert again\", false) } <ins> func TestConcurrentUpdateTransportConfig(t *testing.T) { n := time.Now() now := func() time.Time { return n } env := []string{\"\"} environ := func() []string { s := make([]string, len(env)) copy(s, env) return s } c := api.ExecConfig{ Command:    \"./testdata/test-plugin.sh\", APIVersion: \"client.authentication.k8s.io/v1alpha1\", } a, err := newAuthenticator(newCache(), &c) if err != nil { t.Fatal(err) } a.environ = environ a.now = now a.stderr = ioutil.Discard stopCh := make(chan struct{}) defer close(stopCh) numConcurrent := 2 for i := 0; i < numConcurrent; i++ { go func() { for { tc := &transport.Config{} a.UpdateTransportConfig(tc) select { case <-stopCh: return default: continue } } }() } time.Sleep(2 * time.Second) } </ins> // genClientCert generates an x509 certificate for testing. Certificate and key // are returned in PEM encoding. func genClientCert(t *testing.T) ([]byte, []byte) {", "positive_passages": [{"docid": "doc-en-kubernetes-d5f405b98ac26e68bb52a403345cda18a0b690bbcb8385b5ec06372b302c6e2d", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Data race in client-go with below sample code: Data race: What you expected to happen: No data race How to reproduce it (as minimally and precisely as possible): Using above given sample code Kubernetes version (use ):Cloud provider or hardware configuration:OS (e.g: ): OSX\n/sig api-machinery\nI'd like to take it. /assign\n/remove-sig api-machinery /sig auth cli\nBug triage for release 1.17 here. Since this issue has been tagged for the milestone, we would like to check it's status. Code freeze is on Nov. 14. Will this issue be resolved before then?\nAnother reminder here that code freeze is in less than two weeks (Nov. 14). We will need to move this issue out of the milestone if isn't going to be resolved before then.", "commid": "kubernetes_issue_80269", "tokennum": 239}], "negative_passages": []}
{"query_id": "q-en-kubernetes-96a79def1d0d1a3b3b3c00c2f4cb2a19cfe4ed8e5b02b145827aded5ee34a843", "query": "<del> apiVersion: extensions/v1beta1 </del> <ins> apiVersion: apps/v1 </ins> kind: DaemonSet metadata: name: nvidia-gpu-device-plugin", "positive_passages": [{"docid": "doc-en-kubernetes-81aeaa915020279b8f6f88fad69c7f8c675b68383da3729b9f05c07134ed836b", "text": "This issue is here to satisfy PR requirements of issue association. A lot of times we need to do version bumps for minor bug fixes that don't deserve a separate issue in the kubernetes/kubernetes repo. /kind bug /sig node\n/lifecycle frozen\nall the linked PRs are emrged and no activity since more than 3 years /close\nClosing this issue. <detailsIn response to : all the linked PRs are emrged and no activity since more than 3 years /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", "commid": "kubernetes_issue_57125", "tokennum": 141}], "negative_passages": []}
{"query_id": "q-en-kubernetes-96bf0cb11c24496f34756412935817aa0c22f8c4f3640c5c7a0069ad0b7bb0fd", "query": "fmt.Fprint(out, \"n\") } <ins> func printMissingMetricsNodeLine(out io.Writer, nodeName string) { printValue(out, nodeName) unknownMetricsStatus := \"<unknown>\" for i := 0; i < len(MeasuredResources); i++ { printValue(out, unknownMetricsStatus) printValue(out, \"t\") printValue(out, unknownMetricsStatus) printValue(out, \"t\") } fmt.Fprint(out, \"n\") } </ins> func printValue(out io.Writer, value interface{}) { fmt.Fprintf(out, \"%vt\", value) }", "positive_passages": [{"docid": "doc-en-kubernetes-e039746a8b3b20db88e55e1a23e49575ef9c4052776f0c6f0c425699707a07a4", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If this may be security issue, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: What happened: kubectl top nodes didn't report one of my nodes. I have a cluster of 8 and only 7 printed.", "commid": "kubernetes_issue_63986", "tokennum": 79}], "negative_passages": []}
{"query_id": "q-en-kubernetes-96bf0cb11c24496f34756412935817aa0c22f8c4f3640c5c7a0069ad0b7bb0fd", "query": "fmt.Fprint(out, \"n\") } <ins> func printMissingMetricsNodeLine(out io.Writer, nodeName string) { printValue(out, nodeName) unknownMetricsStatus := \"<unknown>\" for i := 0; i < len(MeasuredResources); i++ { printValue(out, unknownMetricsStatus) printValue(out, \"t\") printValue(out, unknownMetricsStatus) printValue(out, \"t\") } fmt.Fprint(out, \"n\") } </ins> func printValue(out io.Writer, value interface{}) { fmt.Fprintf(out, \"%vt\", value) }", "positive_passages": [{"docid": "doc-en-kubernetes-3b3a7005744c97bc2a779a3634e9ae4963750e882f0e9fc3a43aa2969cd1ed2b", "text": "<pre:::: fang 10:04:02 (cgthayer-pchat) 0 platform; kubectl top nodes NAME CPU(cores) CPU% MEMORY(bytes) MEMORY% gke-charles-test-cluster-default-pool--jkrj 311m 33% 2470Mi 93% gke-charles-test-cluster-default-pool--krsh 154m 16% 1763Mi 66% gke-charles-test-cluster-default-pool--vhgq 265m 28% 1954Mi 73% gke-charles-test-cluster-default-pool--x3bs 186m 19% 1990Mi 75% gke-charles-test-cluster-default-pool--073f 270m 28% 1729Mi 65% gke-charles-test-cluster-default-pool--09zf 403m 42% 2698Mi 102% gke-charles-test-cluster-default-pool--p7h1 191m 20% 1582Mi 59% :::: fang 10:04:07 (cgthayer-pchat) 0 platform; kubectl get nodes NAME STATUS ROLES AGE VERSION gke-charles-test-cluster-default-pool--073f Ready <none7d v1.7.12-gke.1 gke-charles-test-cluster-default-pool--09zf Ready <none7d v1.7.12-gke.1 gke-charles-test-cluster-default-pool--cl65 Ready <none6d v1.7.12-gke.1 gke-charles-test-cluster-default-pool--jkrj Ready <none8d v1.7.12-gke.1 gke-charles-test-cluster-default-pool--krsh Ready <none8d v1.7.12-gke.1 gke-charles-test-cluster-default-pool--p7h1 Ready <none7d v1.7.12-gke.1 gke-charles-test-cluster-default-pool--vhgq Ready <none8d v1.7.12-gke.1 gke-charles-test-cluster-default-pool--x3bs Ready <none8d v1.7.12-gke.1 <preWhat you expected to happen: I expected all nodes to be printed.", "commid": "kubernetes_issue_63986", "tokennum": 536}], "negative_passages": []}
{"query_id": "q-en-kubernetes-96bf0cb11c24496f34756412935817aa0c22f8c4f3640c5c7a0069ad0b7bb0fd", "query": "fmt.Fprint(out, \"n\") } <ins> func printMissingMetricsNodeLine(out io.Writer, nodeName string) { printValue(out, nodeName) unknownMetricsStatus := \"<unknown>\" for i := 0; i < len(MeasuredResources); i++ { printValue(out, unknownMetricsStatus) printValue(out, \"t\") printValue(out, unknownMetricsStatus) printValue(out, \"t\") } fmt.Fprint(out, \"n\") } </ins> func printValue(out io.Writer, value interface{}) { fmt.Fprintf(out, \"%vt\", value) }", "positive_passages": [{"docid": "doc-en-kubernetes-ba6ca4dcc9f7eacf0c6e395f7904a902222263b10161fd5f101ea154df88d32e", "text": "Since the missing node might have bad data I might expect it to have the same number of columns with \"-\" values and a note in a new 6th column saying something like \"unavailabe\" \"unresponsive\" \"stale-data\" etc. e.g. <pregke-charles-test-cluster-default-pool--p7h1 - - - - unreachable </preHow to reproduce it (as minimally and precisely as possible): Not sure. Perhaps run a pod where you can intentionally trigger it to use too much cpu or memory. Anything else we need to know?: Environment: Kubernetes version (use ): kubectl version Client Version: version.Info{Major:\"1\", Minor:\"8\", GitVersion:\"v1.8.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2017-12-21T06:34:11Z\", GoVersion:\"go1.8.3\", Compiler:\"gc\", Platform:\"linux/amd64\"} Server Version: version.Info{Major:\"1\", Minor:\"8+\", GitVersion:\"v1.8.8-gke.0\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2018-02-16T18:26:58Z\", GoVersion:\"go1.8.3b4\", Compiler:\"gc\", Platform:\"linux/amd64\"} Cloud provider or hardware configuration: GKE OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/sig cli\n/kind feature\nI raise a PR to print when the metrics is missing. As for the 6th column you mentioned, I think it could be debatable for its necessity. :)", "commid": "kubernetes_issue_63986", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-96d9e05f369fcc20609eab1df50252f2664cec1161fff63917f06fcea4578388", "query": "import ( \"context\" <del> \"fmt\" </del> \"math/rand\" <del> \"strings\" </del> \"time\" v1 \"k8s.io/api/core/v1\"", "positive_passages": [{"docid": "doc-en-kubernetes-8720ed8a574bdce7c104bd3a62cc93935fad36eef53bf2f2ff98186bbe4abc40", "text": "The metric used to report acutal pod in the label , but now I see the podname prefix only. The full pod name in the label, so I can trace the metric to the failing pod. Check raw api and verify the actual pod name with uids. <details</detailsAzure AKS <details</detailsNo response No response No response_\n/sig node\n/triage accepted /priority important-soon /cc As discussed this is a change in functionaloty that wasn't highlighted in release notes. Need to decide on what do do with it. I understand it's a change of functionality. what is the side effect of this for you? Does the label without last part not informational enough?\nI've been using the metric in my custom grafana dashboard that shows CPU, RAM, IO usage of pods with graph of increases in probes. If the apps are stable, the probe graph looks steadily. I can see if some irregularities in system metrics are influencing probes of respective pod. Also, if readiness probe is failing, the pod is removed from service, but is not restarted so I must have knowledge of pods with failing readiness probes. I attach the screenshot of my graph. ! So I'd welcome the possibility to pair the probes with exact pod and thank you for looking into it.\nare we thinking that this resulted in an undesirable change? Spologies for being a bit late to reply, I'm returning from a brief paternity leave staycation.\nThis issue is labeled with but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release. You can: Confirm that this issue is still relevant with (org members only) Deprioritize it with or Close this issue with For more details on the triage process, see /remove-triage accepted\nWell this is awkward... I still believe the actual behavior does not respect the intended idea...\nThis issue makes it hard to link probe metrics with right pods. The value of pod label in and are also inconsistent with how it is used in other kubelet metrics, see: vs Definitely a bug, regression since 1.25.\nI can't get anyone to look at the fix/revert: you may have better luck\n/milestone v1.28\ndiscussion in\nYou've pushed it through, congrats!", "commid": "kubernetes_issue_115766", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-972480b799835319e79f426057c0f3ab842b1766c6eff29ec453803ba22102c6", "query": "// Ensure all of the pods that we found on this node before the reboot are // running / healthy. if !checkPodsRunningReady(c, ns, podNames, rebootPodReadyAgainTimeout) { <ins> newPods := ps.List() printStatusAndLogsForNotReadyPods(c, pods, newPods) </ins> return false }", "positive_passages": [{"docid": "doc-en-kubernetes-cf37b0ab7a08d0e2457507bc271b1cb7d1e13fbaee3773971363bc32ae71b35b", "text": "We are running heapster, dns server, kube-proxy etc. in kube-system namespace. Some e2e tests try to make sure all those kube-system pods are at ready state before firing the real tests, others just simply ingore them. But both cases might cause e2e flakiness when some of those kube-system containers are in crashloop, for example, for heapster crashloop, for influxdb crashloop, etc. When such cases happen, the developer doesn't have much information on why since the nodes might be teared down. We should watch those kube-system pods, and onContainerFailure, we should collect the related logs. One simple way is using kubectl logs <Pod<Container--previous cc/\nis this related enough to and that you can bundle it in?\nThe logs from the pods should be retrieved via the api server. This is different from the kubelet logs. I'll upload a PR for this.\nGreat job It will be very helpful for debugging.", "commid": "kubernetes_issue_20099", "tokennum": 229}], "negative_passages": []}
{"query_id": "q-en-kubernetes-97841307970fc4c3a76d20aeb9714b48f4ac302c42e29261356da2d85cc6436e", "query": "\"reason\":                   \"FailedScheduling\", }.AsSelector()) expectNoError(err) <ins> // If we failed to find event with a capitalized first letter of reason // try looking for one starting with a small one for backward compatibility. // If we don't do it we end up in #15806. // TODO: remove this block when we don't care about supporting v1.0 too much. if len(schedEvents.Items) == 0 { schedEvents, err = c.Events(ns).List( labels.Everything(), fields.Set{ \"involvedObject.kind\":      \"Pod\", \"involvedObject.name\":      podName, \"involvedObject.namespace\": ns, \"source\":                   \"scheduler\", \"reason\":                   \"failedScheduling\", }.AsSelector()) expectNoError(err) } </ins> printed := false printOnce := func(msg string) string {", "positive_passages": [{"docid": "doc-en-kubernetes-d5b156fb720dd6621e83bb68112b4d593c6df8e76f8835be3c4f5531ff7b5602", "text": "See Jenkins job kubernetes-upgrade-1.0-1.1-gke-step3-e2e-old's last few runs. The relevant line is . Note that this is running e2e tests off of the branch. It's possible that this is also caused by , but it's not clear to me.\nThis is also failing on kubernetes-upgrade-1.0-1.1-gke-step5-e2e-old, where we're running tests against a cluster that's been fully upgraded, (master and nodes,) from 1.0 to 1.1.\nStatus update: this may be caused by , so that issue should be prioritized, but it's not totally clear if that will fix this problem.\nsaid he would take a look and update the issue with any findings. It may be a bit premature to look into it before is resolved, but at least we can try to figure out how to manually repro this now, so that we will know whether fixes this issue.\nI'm unable to find logs from failed runs, which makes everything slightly harder. I'll try to reproduce the problem on GCE cluster, but it may not work. FYI: most of was caused by waiting for skydns to come back up (which doesn't happen: ). I see that there's a difference in number of system pods between version 1.1 and 1.0 - there's only 5 of them in 1.1 and 8 of them in 1.0. I'm wondering if this may cause problems in 'old' version of test which we're running there. I'm going to try reproduce it on GCE (as this is the setup I understand better) and if I'll fail I'll try again on GKE.\nAFAICT there's a problem with the test, not the upgrade itself. The test from 1.1 branch fails on 1.0 cluster.\nIt's caused by . Can we please stop renaming things? AFAICT the problem is with test only, everything should be working 'on production'. In v1.0 scheduler Events reasons start with a small letter (e.g. failedScheduling) and v1.0 test is looking for those kind of events to occur. In v1.1 we changed Event reasons to start with a capital letter (e.g.", "commid": "kubernetes_issue_15806", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-97841307970fc4c3a76d20aeb9714b48f4ac302c42e29261356da2d85cc6436e", "query": "\"reason\":                   \"FailedScheduling\", }.AsSelector()) expectNoError(err) <ins> // If we failed to find event with a capitalized first letter of reason // try looking for one starting with a small one for backward compatibility. // If we don't do it we end up in #15806. // TODO: remove this block when we don't care about supporting v1.0 too much. if len(schedEvents.Items) == 0 { schedEvents, err = c.Events(ns).List( labels.Everything(), fields.Set{ \"involvedObject.kind\":      \"Pod\", \"involvedObject.name\":      podName, \"involvedObject.namespace\": ns, \"source\":                   \"scheduler\", \"reason\":                   \"failedScheduling\", }.AsSelector()) expectNoError(err) } </ins> printed := false printOnce := func(msg string) string {", "positive_passages": [{"docid": "doc-en-kubernetes-a9b54e968993d2debcdfb36dbc5942943d975a32ddc74ac1464196bee7cec493", "text": "FailedScheduling) and modified test accordingly. Effects are obvious. We can: revert patch it to v1.0 merge and patch a test fix which adds handling both versions () I'm for the last option, but whatever we do (except reverting) will break backward compatibility for everyone depending/counting/filtering/whatnot on scheduler Event reasons\nthanks for your work on this. From on : Furthermore, in my (rookie) opinion, seems like it should be considered a bug fix rather than an API change. Thus I think makes good sense.\nThanks a lot for debugging this, and I agree we should go with your PR. I talked to Brian and he said we don't consider changes to values of fields in events to be breaking API changes. Unfortunately people do seem to depend on these in various places. One solution is what I proposed in so the compiler could prevent these incompatibilities (at least for components and tests that are compiled together).\n+1 to creating a file containing constants for the event reasons that are currently in use.\nI'll prepare a cherry pick.\nReopening until cherry pick is merged.\nCherry pick is .\nThe test mentioned in the first entry in this thread is still failing but not due to the error message related to this issue. Since the cherrypick has been merged, can we close this issue, and followup with additional debugging in ?\nWorks for me. Thanks to again for your work on this.\nI actually still see failures of the same kind in (master 1.1, nodes 1.0) and (master 1.1, nodes 1.1). I assume this is because we haven't cherrypicked test fix into . So this is now a duplicate of .", "commid": "kubernetes_issue_15806", "tokennum": 364}], "negative_passages": []}
{"query_id": "q-en-kubernetes-97aeb43cbcfebe3d7e45367081df6cb1dc231e7a84c06e2e7acc1421de861075", "query": "import ( \"fmt\" \"net\" <ins> \"os\" </ins> \"strconv\" \"strings\" \"testing\"", "positive_passages": [{"docid": "doc-en-kubernetes-5e93ba1a338583c6193506912a68a67fcc908451a37c483694071bc120df2bcb", "text": "When a --resolv-conf (DNS resolver config) is passed to kubelet on a Windows node, the config content is used as part of sandbox initialization (through getHostDNSConfig()). Now with the recent changes (), it seems now to fail with an error like: E0315 10:22:16. 4764 ] \"Error syncing pod, skipping\" err=\"failed to \"CreatePodSandbox\" for \"img-pull-(-b40a-459d-9033-)\" with CreatePodSandboxError: \"Failed to generate sandbox config for pod \"img-pull-(-b40a-459d-9033-)\": Unexpected resolver config value: \"C:etckubernetescni\". Expected \"\" or \"Host\".\"\" pod=\"img-puller-3842/img-pull-\" podUID=-b40a-459d-9033- This is showing on all the runs of GCE testgrid (latest): Reading/using the passed resolv config on Windows Run a Windows pool with DNS resolv config being set as part of kubelet params. No response_ 27 alpha.3 1.27 beta.0 master <detailsGCE </details<details</details<details</details<details</details<details</details\n/triage accepted /milestone v1.27 /sig node /sig network\n/sig windows /cc\n/priority criticial-urgent as this is likely a release blocking\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority criticial-urgent 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\n/priority critical-urgent\nHmm, so you're setting the [1]. This PR introduced the capability to read the DNS config options from the Windows host registries while removing the capability to read from a file, introducing a regression. I've sent a PR addressing this issue: [1]\nIs the file you are pointing to a UNIX-style or something else?\nWas the file changing the behavior of the node?", "commid": "kubernetes_issue_116782", "tokennum": 565}], "negative_passages": []}
{"query_id": "q-en-kubernetes-97aeb43cbcfebe3d7e45367081df6cb1dc231e7a84c06e2e7acc1421de861075", "query": "import ( \"fmt\" \"net\" <ins> \"os\" </ins> \"strconv\" \"strings\" \"testing\"", "positive_passages": [{"docid": "doc-en-kubernetes-a55794e1d2c420cf7484c297920657922704eb45d045ae8237364febdd60d634", "text": "Yeah, what used on GCE/GKE, seems to be a Linux-like conf, eg: nameserver 10.128.0.1 search c.<project_name.internal google.internal ` We haven't tried to remove from kubelet to see the behavior.\nThis Issue/PR has been marked as release blocker. Please have the fix merged by eod today otherwise the feature has to be reverted. For the Issue/PR owner: please have a revert/feature disable PR open today in case the fix failed to get in. Thank you! See the -- Kubernetes 1.27 release manager\nI opened up a revert PR in case this PR does not merge by code freeze.\nThanks for the resolution! both 2019 and 2022 grids seems to be back to green now!\nThanks for confirming! I opened to ensure gets updated too", "commid": "kubernetes_issue_116782", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-97d25bcb5bcb02b65b6b05ad5491508b270f00875aeae81bb91a431d886a8dc3", "query": "serviceHealthServer := healthcheck.NewServiceHealthServer(hostname, recorder) isIPv6 := ipt.IsIPv6() <ins> var incorrectAddresses []string nodePortAddresses, incorrectAddresses = utilproxy.FilterIncorrectCIDRVersion(nodePortAddresses, isIPv6) if len(incorrectAddresses) > 0 { klog.Warning(\"NodePortAddresses of wrong family; \", incorrectAddresses) } </ins> proxier := &Proxier{ portsMap:                 make(map[utilproxy.LocalPort]utilproxy.Closeable), serviceMap:               make(proxy.ServiceMap),", "positive_passages": [{"docid": "doc-en-kubernetes-10e0800334eabc101ba3e719bde6addc76496fd00734e09bb571fcc5b6be7d48", "text": "What happened: In a dual-stack cluster when specifying both ipv6 and ipv4 addresses in the entries are inserted in ipvs for the ipv6 nodeports but with an invalid ipv4 address; The example shows the ipv4 loopback address but any ipv4 address in will cause a faulty entry. What you expected to happen: No ipv4 entry shall be inserted for the ipv6 nodeport. How to reproduce it (as minimally and precisely as possible): Configure with both ipv4 and ipv6 addresses Bring up a dual-stack cluster with proxy-mode Create a service with ipFamily:IPv6 Do Anything else we need to know?: Proxy-mode=iptables seems to work. With no ipv4 entries are inserted for ipv6 nodeports. In it is recommended to use but doing so makes kube-proxy enter rules for address (in addition to \"127.0.0.1\"). While these entries cause no harm they can't be used and should not be there. These entries are created for both proxy-mode \"iptables\" and \"ipvs\". This should not be handled in this issue but in another (new) issue if needed. Example; Environment: Kubernetes version (use ):Cloud provider or hardware configuration: Kvm's on Ubuntu OS (e.g: ): xcluster Kernel (e.g. ):Install tools: \"from scratch\" Network plugin and version (if this is a network-related bug): calico/cni:v3.12.0 Others: /sig network\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/area ipvs /area ipv6\n/remove-triage unresolved /assign I take this myself if no one objects.\nThe ipv4 address is obviously a ipv4-converted ipv6 from .\nAccording to the code here (), we may need to filter the before passing it to .\nLooks that that's it. Please go ahead and make a PR, or I can do it if you prefer. I will help test the PR of course. Here are some review comments right away; Use v1.IPFamily as param to the filter function rather than The filter function seem usable and generic and may be placed in some \"util\" package, but leave it as-is and let the maintainers decide that.\nHi feel free to send a PR please, as you have took this already :) I'd like to help review it!\nThe \"addresses\" are really CIDRs which make the fix even simpler.", "commid": "kubernetes_issue_89923", "tokennum": 576}], "negative_passages": []}
{"query_id": "q-en-kubernetes-980d2df2f7941661651ba968f0ef0457b805ef3cfd0c96a16ff8984f0dd0d908", "query": "go_library( name = \"go_default_library\", srcs = [ <ins> \"bindata.go\", </ins> \"main.go\", <del> \":bindata\", ], ) genrule( name = \"bindata\", srcs = [ \"//examples:sources\", \"//test/images:sources\", \"//test/fixtures:sources\", \"//test/e2e/testing-manifests:sources\", ], outs = [\"bindata.go\"], cmd = \"\"\" $(location //vendor:github.com/jteeuwen/go-bindata/go-bindata)  -nometadata -o \"$(OUTS)\" -pkg generated  -prefix $$(pwd)  -ignore .jpg -ignore .png -ignore .md  $(SRCS) \"\"\", tools = [ \"//vendor:github.com/jteeuwen/go-bindata/go-bindata\", </del> ], <ins> tags = [\"automanaged\"], </ins> )", "positive_passages": [{"docid": "doc-en-kubernetes-0ad427ca9c00c618017f4be9fb19a1df6f4ab39ddc68f128fc109eb4d0409cbf", "text": "Cluster logging assumes kubelet stores container log at a specific directory with specific name. Currently the path is: After the CRI work, the path will be: However, we don't have test coverage for this. We don't even know whether the log files are there or not. We should add a node e2e test for this, basically: 1) Create a container which prints logs 2) Check whether the expected log file is created. 3) Check whether the logs are collected in the file as expected. And it would be better to launch a pod to do the check instead of accessing local file system directly, which makes containerizing easier. /cc because you are collecting missing test. /cc\nI will try to add a node-e2e test there\nI think it's ok to add this for CRI. But there maybe problems on today's interface for rkt. If I'm not wrong, rkt does't store logs at same location with docker. cc/ Is this true?\nThanks! :)\nAfter gets merged, we need to update the test to verify the cri log path.", "commid": "kubernetes_issue_34661", "tokennum": 234}], "negative_passages": []}
{"query_id": "q-en-kubernetes-98265b155578a94de2d8391a7d4a48d899ff560bac6662052e09cd4dbd93a80c", "query": "ctx, cancel := context.WithCancel(context.Background()) defer cancel() // Start to follow the container's log. <ins> fileName := file.Name() </ins> go func(ctx context.Context) { podLogOptions := v1.PodLogOptions{ Follow: true, } opts := NewLogOptions(&podLogOptions, time.Now()) <del> ReadLogs(ctx, file.Name(), containerID, opts, fakeRuntimeService, stdoutBuf, stderrBuf) </del> <ins> _ = ReadLogs(ctx, fileName, containerID, opts, fakeRuntimeService, stdoutBuf, stderrBuf) </ins> }(ctx) // log in stdout", "positive_passages": [{"docid": "doc-en-kubernetes-d28453dfc6bcf829133f35627fac482c86b9caf8a20943cea67f030688a8c436", "text": "Runs k8s with master golang: test Failure was observed on Aug 25th, it is passing after that. However it can be reproduced with stress tool. No response No response It is failing on both ppc and x86 architectures. Steps to reproduce: up golang tip version. clone kubernetes master /sig testing\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\nit is a sig node test, sig testing charter is not about doing or maintain tests, we need to remove that old mindset of having a QA department, that is not how software development works or should work :) Besides, thanks for spotting it and submittn a patch /sig node /remove-sig testing\nFlaky in\nmerging this PR will fix the issue", "commid": "kubernetes_issue_121564", "tokennum": 237}], "negative_passages": []}
{"query_id": "q-en-kubernetes-989bbde8d227797953a8f4fd3865ff2a6e64fdf5d7999e646ff43deb9ba82519", "query": "return nc.evictionLimiterQPS } <del> // ReducedQPSFunc returns the QPS for when a the cluster is large make </del> <ins> // ReducedQPSFunc returns the QPS for when the cluster is large make </ins> // evictions slower, if they're small stop evictions altogether. func (nc *Controller) ReducedQPSFunc(nodeNum int) float32 { if int32(nodeNum) > nc.largeClusterThreshold {", "positive_passages": [{"docid": "doc-en-kubernetes-c2ab3144aef8ccfdc5bfa24e077aa0687e2812de3da5460311eb2f2561c37ff3", "text": "The arg large-cluster-size-threshold for kube-controller-manager works as zone size threshold when determining node eviction rate. If there are multiple zones, the description for arg stating \"cluster\" threshold would be missleading. ARG: Matched arg description Multiple zones cluster No response <details</details<details</details<details</details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig docs", "commid": "kubernetes_issue_119499", "tokennum": 184}], "negative_passages": []}
{"query_id": "q-en-kubernetes-98b98ebfc8e72bdd15c13a474bfe70bd078df8ff7afdaa649a069f534356f8b6", "query": "name = \"go_default_test\", srcs = [\"healthz_test.go\"], embed = [\":go_default_library\"], <ins> deps = [ \"//staging/src/k8s.io/apimachinery/pkg/util/sets:go_default_library\", ], </ins> ) go_library(", "positive_passages": [{"docid": "doc-en-kubernetes-01cc291fb1d6afeae9b284d60dd407b578a72d26e4c50043cbdf654c92184c45", "text": "What would you like to be : Add support to the kube-apiserver so that we can disable health-checks via query params. Why is this needed: Currently, the healthz endpoint is inflexible in that any and all health checks are currently executed when the endpoint is hit. Since the kube-apiserver only currently supports a liveness check, this means all persistent health check failures will eventually result in a kubelet driven restart. However, this may not be desirable behavior if you have additional monitoring services layered on top of your control plane. For instance, take the etcd failure from the perspective of the kube-apiserver. Currently, persistent failures during the etcd health check from the api-server healthz endpoint will cause the kube-apiserver to be restarted. This sometimes helps (in the case of a faulty etcd-client connection) but also can be detrimental (the kube-apiserver restarts until the etcd cluster is functioning, then the kube-apiserver bombards the etcd cluster with requests to update local caches, saturating the etcd cluster with requests, causing it to timeout on its own liveness probes and trigger a kubelet-driven restart). Let's say that we could now disable etcd from our liveness health check. Then if we had an external monitoring service, we could ask independently ask etcd if it was healthy and we could also ask the kube-apiserver if it thought etcd was unhealthy. Based on the combination of those answers, we could enable more intelligent responses to certain situation, like restarting the kube-apiserver when it thought etcd was unhealthy but etcd was actually reporting as healthy but not doing so when etcd was actually unhealthy. This feature is backwards-compatible and opt-in. There would be no impact to existing behavior unless these query params are actually used. /sig api-machinery /kind feature\n/cc\nSGTM\n/assign", "commid": "kubernetes_issue_70591", "tokennum": 432}], "negative_passages": []}
{"query_id": "q-en-kubernetes-98bc6556d7f3a8f24abd0676961aa299639e10ed8dcea635ab43d4b08033862f", "query": "}, } <del> var betaTest *testsuites.StorageClassTest </del> for i, t := range tests { // Beware of closure, use local variables instead of those from // outer scope", "positive_passages": [{"docid": "doc-en-kubernetes-e2f4fe7b99012f8e7173e2f6c46ef5707967f19510033d4b6b03e3a31c7298f0", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --ci-kubernetes-e2e-gci-gce-slow [sig-storage] Dynamic Provisioning DynamicProvisioner [Slow] should provision storage with different parameters 5/13 https://k8s- v1beta1.StorageClass got removed in We should remove the v1beta1 test.\n/assign can you help take a look?\n/triage accepted\n/sig storage\nI run the test with the latest from master without removing the beta test and it failed with a different error before getting to the beta test part: Do you have any idea what would've happened in my setup? I redeployed k/k using master HEAD\nFor this testcase: I saw that the provisioned PD has a size of 1.5Gi according to kubernetes: And in gcloud It's really interesting that the test was expecting 2Gi to be created, is this something that was changed recently?\nThe logs you posted are showing pd csi as the provisioner. Were you testing with the intree driver or csi driver? The CSI driver should to the nearest Gb. I believe intree does the .\nI think I did intree because I didn't send as an argument in my command: It's interesting that the PVC has this annotation too:\nmmm something interesting about my setup is that I created the cluster with CSIMigration turned on Do you think that might be forcing the usage of ?\nYes likely. Try with CSIMigration off and see if that helps. If so, then this potentially seems like a rounding bug with the csi driver\nThanks I tried with and it did indeed round up to 2Gi.", "commid": "kubernetes_issue_102076", "tokennum": 373}], "negative_passages": []}
{"query_id": "q-en-kubernetes-98d44487b5668a5f53df99f195813b0951c6d35860639aa5986ce72755df7202", "query": "t.Errorf(\"No client request should have been made\") } } <ins> // TestAdmissionNamespaceExistsUnknownToHandler func TestAdmissionNamespaceExistsUnknownToHandler(t *testing.T) { namespace := \"test\" mockClient := &client.Fake{ Err: errors.NewAlreadyExists(\"namespaces\", namespace), } store := cache.NewStore(cache.MetaNamespaceKeyFunc) handler := &provision{ client: mockClient, store:  store, } pod := api.Pod{ ObjectMeta: api.ObjectMeta{Name: \"123\", Namespace: namespace}, Spec: api.PodSpec{ Volumes:    []api.Volume{{Name: \"vol\"}}, Containers: []api.Container{{Name: \"ctr\", Image: \"image\"}}, }, } err := handler.Admit(admission.NewAttributesRecord(&pod, namespace, \"pods\", \"CREATE\")) if err != nil { t.Errorf(\"Unexpected error returned from admission handler\") } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-c343f6e7b091e9b4529e6227acb6329e7535006eb05bcc59008c8d5d37213826", "text": "While running one of my soak tests I noticed the error message: I don't see why I should get this error message. Why should it matter if the namespace already exists? It was created as part of the service creation call just beforehand. And the second attempt to create this pod in exactly the same namespace works. Is this a bug?\nRunning a second time did not produce this error.\nI agree it should not matter. The error is produced there, and I suspect there were multiple concurrent calls being made that try to create a resource in a namespace that had not yet existed. We need to update the code in question to swallow the error if the namespace already exists.\nFYI - longer term, I would like to eliminate the use of autoprovision of namespace and require you to first create a namespace manually. what is there now is more to preserve existing behavior prior to namespace as object was introduced.", "commid": "kubernetes_issue_5873", "tokennum": 190}], "negative_passages": []}
{"query_id": "q-en-kubernetes-98db40faf68511f11736447debfb18b041695b510634831aadc506b9499efde0", "query": "// will not need to be updated until new changes are applied (detach is triggered again) time.Sleep(100 * time.Millisecond) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <del> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw) // After the first detach fails, reconciler will wait for a period of time before retrying to detach. // The wait time is increasing exponentially from initial value of 0.5s (0.5, 1, 2, 4, ...). // The test here waits for 100 Millisecond to make sure it is in exponential backoff period after // the first detach operation. At this point, volumes status should not be updated time.Sleep(100 * time.Millisecond) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) verifyVolumeNoStatusUpdateNeeded(t, logger, generatedVolumeName, nodeName1, asw) // Wait for 600ms to make sure second detach operation triggered. Again, The volume will be // removed from being reported as attached on node status and then added back as attached. // The volume will be in the list of attached volumes that need to be updated to node status. time.Sleep(600 * time.Millisecond) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw) </del> <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw, volumeAttachedCheckTimeout) </ins> // Add a second pod which tries to attach the volume to the same node. // After adding pod to the same node, detach will not be triggered any more.", "positive_passages": [{"docid": "doc-en-kubernetes-dc8aac09a0e4bb26f9dc5f50aef7f845ea9d7c4b925d34b9f6eda044925f80f5", "text": "TestRunOneVolumeDetachFailNodeWithReadWriteOnce 4 times since 03-19 23:00 PDT, intermittently ! https://k8s- Still investigating whether this is a tolerable flake or not with more history than testgrid view, or otherwise would appreciate input from anyone with expertise in this test, especially as regards to whether this should be a blocker for tomorrows beta cut. maybe: /sig storage /sig testing\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nis already open for this, looks like it is attempting to fix it\nthank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. /close\nClosing this issue. <detailsIn response to : thank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. 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", "commid": "kubernetes_issue_116774", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-98db40faf68511f11736447debfb18b041695b510634831aadc506b9499efde0", "query": "// will not need to be updated until new changes are applied (detach is triggered again) time.Sleep(100 * time.Millisecond) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <del> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw) // After the first detach fails, reconciler will wait for a period of time before retrying to detach. // The wait time is increasing exponentially from initial value of 0.5s (0.5, 1, 2, 4, ...). // The test here waits for 100 Millisecond to make sure it is in exponential backoff period after // the first detach operation. At this point, volumes status should not be updated time.Sleep(100 * time.Millisecond) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) verifyVolumeNoStatusUpdateNeeded(t, logger, generatedVolumeName, nodeName1, asw) // Wait for 600ms to make sure second detach operation triggered. Again, The volume will be // removed from being reported as attached on node status and then added back as attached. // The volume will be in the list of attached volumes that need to be updated to node status. time.Sleep(600 * time.Millisecond) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw) </del> <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw, volumeAttachedCheckTimeout) </ins> // Add a second pod which tries to attach the volume to the same node. // After adding pod to the same node, detach will not be triggered any more.", "positive_passages": [{"docid": "doc-en-kubernetes-aef7ec00dc93616f97177ca3d23f28217445848b34c429e5746962ea28329f43", "text": "pull-kubernetes-unit TestRunOneVolumeDetachFailNodeWithReadWriteOnce Jan 7th, 2022 Check volume <fake-plugin/volume-nameis reported as attached to node <fail-detach-node, got false, expected true No response_ /sig storage\n/cc\nthis is the top unit test flake according to\ncc\nThe 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]:\nI think this test is no longer flaky by checking the test grid, close it now.\nUnfortunately this does still seem to be flaky: Here was the output from : /reopen\nReopened this issue. <detailsIn response to : Unfortunately this does still seem to be flaky: 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\n/remove-lifecycle stale\nstill the case\nHow about adding some logging to help troubleshoot this? I looked at it a little, but it is hard to tell which part of the test is failing. PR\n/\nThis is still happening\n/triage accepted\nFrom the logs, in the OneVolumeDetachFailNodeWithReadWriteOnce test, succeeded, but the next verification failed. In verifyVolumeAttachedToNode, the attachState is from calling and within asw, it calls . In verifyVolumeReportedAsAttachedToNode, the volumes are obtained from calling , it seems that the node is not in asw.nodesToUpdateStatusFor at this step. Cannot reproduce locally. I tried to run the test 100 times locally with debug.Stack()... 3 * 100 times all passed.\nTried to run stress test on my linux machine as well but still cannot reproduce. Command: Result: Also tried running n process in parallel. Command: Result:\nIt seems like it happens more frequently.", "commid": "kubernetes_issue_107414", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-98db40faf68511f11736447debfb18b041695b510634831aadc506b9499efde0", "query": "// will not need to be updated until new changes are applied (detach is triggered again) time.Sleep(100 * time.Millisecond) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <del> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw) // After the first detach fails, reconciler will wait for a period of time before retrying to detach. // The wait time is increasing exponentially from initial value of 0.5s (0.5, 1, 2, 4, ...). // The test here waits for 100 Millisecond to make sure it is in exponential backoff period after // the first detach operation. At this point, volumes status should not be updated time.Sleep(100 * time.Millisecond) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) verifyVolumeNoStatusUpdateNeeded(t, logger, generatedVolumeName, nodeName1, asw) // Wait for 600ms to make sure second detach operation triggered. Again, The volume will be // removed from being reported as attached on node status and then added back as attached. // The volume will be in the list of attached volumes that need to be updated to node status. time.Sleep(600 * time.Millisecond) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw) </del> <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw, volumeAttachedCheckTimeout) </ins> // Add a second pod which tries to attach the volume to the same node. // After adding pod to the same node, detach will not be triggered any more.", "positive_passages": [{"docid": "doc-en-kubernetes-62e47fd83b7fc1cc39259be1688a9f133b9cd2dc48247eb5d858fae7fd13955b", "text": "But I may have no time to dig into the cause. Let's see.\ncc as the test author.\nThe problem is that this test has a lot of dependency on the sleeps that are hardcoded with a very narrow scope, but our CI seems to be able to stress it much more. As soon as you slightly change one of the sleep duration it starts to flake locally The test can not make an assumption that timing is perfect, even more in the sub second range can someone in sig-storage review this test and make it less dependant on those tight sleeps?\nAccording to most failures, it failed at Line 660. Let me run some stress locally. with 250ms sleep with 100ms sleep\nI agree this test case is too brittle due to its specific timing dependencies. To fix this, I suggest reworking the test case to: 1) Add retry with timeout to wait for final conditions 2) Remove the intermediate timing-based state transition checks. Instead, we can keep track of state transitions in the Fakes and validate those stats. wdyt?\nFriendly ping from 1.27 CI Signal that this test is still a noisy flake on the master-blocking dashboard as CI Signal has flagged it in and", "commid": "kubernetes_issue_107414", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-991a0cc7419cd89b7f84d2e7945b766273bb2bda91d4fb894682e992d77f79f6", "query": "<del> apiVersion: admissionregistration.k8s.io/v1alpha1 kind: ValidatingAdmissionPolicy metadata: annotations: annotationsKey: annotationsValue creationTimestamp: \"2008-01-01T01:01:01Z\" deletionGracePeriodSeconds: 10 deletionTimestamp: \"2009-01-01T01:01:01Z\" finalizers: - finalizersValue generateName: generateNameValue generation: 7 labels: labelsKey: labelsValue managedFields: - apiVersion: apiVersionValue fieldsType: fieldsTypeValue fieldsV1: {} manager: managerValue operation: operationValue subresource: subresourceValue time: \"2004-01-01T01:01:01Z\" name: nameValue namespace: namespaceValue ownerReferences: - apiVersion: apiVersionValue blockOwnerDeletion: true controller: true kind: kindValue name: nameValue uid: uidValue resourceVersion: resourceVersionValue selfLink: selfLinkValue uid: uidValue spec: auditAnnotations: - key: keyValue valueExpression: valueExpressionValue failurePolicy: failurePolicyValue matchConditions: - expression: expressionValue name: nameValue matchConstraints: excludeResourceRules: - apiGroups: - apiGroupsValue apiVersions: - apiVersionsValue operations: - operationsValue resourceNames: - resourceNamesValue resources: - resourcesValue scope: scopeValue matchPolicy: matchPolicyValue namespaceSelector: matchExpressions: - key: keyValue operator: operatorValue values: - valuesValue matchLabels: matchLabelsKey: matchLabelsValue objectSelector: matchExpressions: - key: keyValue operator: operatorValue values: - valuesValue matchLabels: matchLabelsKey: matchLabelsValue resourceRules: - apiGroups: - apiGroupsValue apiVersions: - apiVersionsValue operations: - operationsValue resourceNames: - resourceNamesValue resources: - resourcesValue scope: scopeValue paramKind: apiVersion: apiVersionValue kind: kindValue validations: - expression: expressionValue message: messageValue messageExpression: messageExpressionValue reason: reasonValue variables: null status: conditions: - lastTransitionTime: \"2004-01-01T01:01:01Z\" message: messageValue observedGeneration: 3 reason: reasonValue status: statusValue type: typeValue observedGeneration: 1 typeChecking: expressionWarnings: - fieldRef: fieldRefValue warning: warningValue </del>", "positive_passages": [{"docid": "doc-en-kubernetes-f7dbb3a7bd33f39ed155e3c1ad6b8c55c94743d34cf8c863dee73b5ba5ef4403", "text": "spec.variables should be marked omitempty. I'm trying to create a validating admission policy that uses in v1.27 as follows: I'm setting : to \"Strict\" in CreateOptions so that the server will reject requests with unknown fields but it complains that the don't exist in v1.27 and it does make sense because this field was introduced in v1.28: I'm using a 1.28 client.\n/sig api-machinery\n/assign\n/assign /triage accepted\nThanks for raising this! /cc", "commid": "kubernetes_issue_120491", "tokennum": 117}], "negative_passages": []}
{"query_id": "q-en-kubernetes-991bfa0df38d7b6d69bfe41a50781c1f2c0fbdddc402c208ef55f15e7c1b5b2f", "query": "return } <ins> func (az *azPublicIPAddressesClient) GetVirtualMachineScaleSetPublicIPAddress(ctx context.Context, resourceGroupName string, virtualMachineScaleSetName string, virtualmachineIndex string, networkInterfaceName string, IPConfigurationName string, publicIPAddressName string, expand string) (result network.PublicIPAddress, err error) { if !az.rateLimiterReader.TryAccept() { err = createRateLimitErr(false, \"VMSSPublicIPGet\") return } klog.V(10).Infof(\"azPublicIPAddressesClient.GetVirtualMachineScaleSetPublicIPAddress(%q,%q): start\", resourceGroupName, publicIPAddressName) defer func() { klog.V(10).Infof(\"azPublicIPAddressesClient.GetVirtualMachineScaleSetPublicIPAddress(%q,%q): end\", resourceGroupName, publicIPAddressName) }() mc := newMetricContext(\"vmss_public_ip_addresses\", \"get\", resourceGroupName, az.client.SubscriptionID, \"\") result, err = az.client.GetVirtualMachineScaleSetPublicIPAddress(ctx, resourceGroupName, virtualMachineScaleSetName, virtualmachineIndex, networkInterfaceName, IPConfigurationName, publicIPAddressName, expand) mc.Observe(err) return } </ins> func (az *azPublicIPAddressesClient) List(ctx context.Context, resourceGroupName string) ([]network.PublicIPAddress, error) { if !az.rateLimiterReader.TryAccept() { return nil, createRateLimitErr(false, \"PublicIPList\")", "positive_passages": [{"docid": "doc-en-kubernetes-c62a800befd6b705c74ea2036c66907711f830c03e53ca86df0e2014d6541d16", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Node external IP of azure VMSS cannot be obtained when cloud-controller-manager is enabled. Corresponding logs are shown as follows:\n/sig azure\n/milestone v1.16", "commid": "kubernetes_issue_80014", "tokennum": 92}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9982afcd4199a0e30dda450beb036b88d1bc86f3b2b2f3ad4be7286f14bc0a73", "query": "return nil, err } <del> res := metricObj.(*v1beta2.MetricValueList) </del> <ins> var res *v1beta2.MetricValueList var ok bool if res, ok = metricObj.(*v1beta2.MetricValueList); !ok { return nil, fmt.Errorf(\"the custom metrics API server didn't return MetricValueList, the type is %v\", reflect.TypeOf(metricObj)) } </ins> return res, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-c04a0817a9f8c0cfea921bee7f0710f81a15653683e102754b69999644e85b55", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: What you expected to happen: kube-controller-manager should not panic. How to reproduce it (as minimally and precisely as possible): Kubernetes 1.12.6, , and Anything else we need to know?: It's running and , and logs says: Don't see any notable errors in . Is that because it's running the old ? Basically, is expecting , but somehow it's getting which I assume Environment: Kubernetes version (use ): v1.12.6 Cloud provider or hardware configuration: AWS EC2 OS (e.g: ): Amazon Linux 2 Kernel (e.g. ): 4.14.109-99.92.amzn2.x86_64\nCould be related to , but this happens with all the patches from the issue /sig scalability /cc\n/sig autoscaling /assign can you triage please?\n/sig-remove scalabilty\n/sig remove scalability\n/sig scalability remove\n/remove-sig scalability\nAPI returned v1.Status instead of v1beta2.MetricValueList. We should check what is the type of the object\n/sig instrumention\n/assign\n/sig instrumentation\nseems promising. Is it missing anything?\nI've root-caused the issue. Explained here -\nYep, should address the issue.", "commid": "kubernetes_issue_80390", "tokennum": 343}], "negative_passages": []}
{"query_id": "q-en-kubernetes-999b4636edc0ed8d9ce206a995589f1df66a1ad88449ec5c37f2290de1596b43", "query": "if protocol == \"udp\" { // TODO: It would be enough to pass 1s+epsilon to timeout, but unfortunately // busybox timeout doesn't support non-integer values. <del> cmd = fmt.Sprintf(\"echo 'hostName' | nc -w 1 -u %s %d\", targetIP, targetPort) </del> <ins> cmd = fmt.Sprintf(\"echo hostName | nc -w 1 -u %s %d\", targetIP, targetPort) </ins> } else { ipPort := net.JoinHostPort(targetIP, strconv.Itoa(targetPort)) // The current versions of curl included in CentOS and RHEL distros", "positive_passages": [{"docid": "doc-en-kubernetes-8ad6fcc1c21931d1df01e57d73eaefbe4f4eb3b6b6c8749d3543decdbcaf5bd3", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: N/A Which test(s) are failing: should function for node-pod communication: udp Since when has it been failing: Unknown. Testgrid link: The test is currently excluded. Reason for failure: By default, cmd is used to execute commands in Windows containers, but it has some issues executing the command (no output): echo 'hostName' | nc -w 1 -u <targetIP<targetPortBut it has no issues running (output is correct): echo hostName | nc -w 1 -u <targetIP<targetPortThis causes the test \"should function for node-pod communication: udp\" to fail when using Windows Containers. Anything else we need to know: /sig testing /sig windows", "commid": "kubernetes_issue_72917", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-99a57b466d39325790f7acb7b692e1eda697b932c9efa649fe4da7b33b7c7c34", "query": "} func mountPointsEqual(a, b *MountPoint) bool { <del> if a.Device != b.Device || a.Path != b.Path || a.Type != b.Type || !slicesEqual(a.Opts, b.Opts) || a.Pass != b.Pass || a.Freq != b.Freq { </del> <ins> if a.Device != b.Device || a.Path != b.Path || a.Type != b.Type || !reflect.DeepEqual(a.Opts, b.Opts) || a.Pass != b.Pass || a.Freq != b.Freq { </ins> return false } return true } <del> func slicesEqual(a, b []string) bool { if len(a) != len(b) { return false } for i := range a { if a[i] != b[i] { return false } } return true } </del> func TestGetMountRefs(t *testing.T) { fm := &FakeMounter{ MountPoints: []MountPoint{", "positive_passages": [{"docid": "doc-en-kubernetes-2eda896003caba863d0609f67aa343029dbd4049babda0317e758512fcccca95", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: In some files, i found that there are many self-contained function, whose feature is as same as some util function. Obviously, they are redundant. What you expected to happen: Use util function to replace self-contained function How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration**: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/assign\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\nsimilar comment to Can you edit the description in to say instead of ? Thanks!\nThanks. Done.", "commid": "kubernetes_issue_50952", "tokennum": 279}], "negative_passages": []}
{"query_id": "q-en-kubernetes-99cd58416e85601ae1c02fa9583ce6dff19e642192e8c2cb213d1fe00c2496f6", "query": "} // Verify the proxy server logs saw the connection <del> expectedProxyLog := fmt.Sprintf(\"Accepting CONNECT to %s\", strings.TrimRight(strings.TrimLeft(framework.TestContext.Host, \"https://\"), \"/api\")) </del> <ins> expectedProxyLog := fmt.Sprintf(\"Accepting CONNECT to %s\", strings.TrimSuffix(strings.TrimPrefix(framework.TestContext.Host, \"https://\"), \"/api\")) </ins> proxyLog := proxyLogs.String() if !strings.Contains(proxyLog, expectedProxyLog) {", "positive_passages": [{"docid": "doc-en-kubernetes-51391b67bb5f7406f2fc1910c3ffa31576cbedf4c6c7ca16b25a67ab404b314c", "text": "TrimLeft returns a slice of the string s with all leading Unicode code points contained in cutset removed. To remove a prefix, use TrimPrefix instead. /sig release /kind bug\n/assign", "commid": "kubernetes_issue_68327", "tokennum": 43}], "negative_passages": []}
{"query_id": "q-en-kubernetes-99d35e6ff66d8241fd163312bb7fd9e796f74f675c8c79d853ce85310e38c881", "query": "framework.ExpectNoError(err, \"error deleting Service\") return svc } <ins> // endpointSlicesEqual compare if the Endpoint and the EndpointSliceList contains the same endpoints values // as in addresses and ports, considering Ready and Unready addresses func endpointSlicesEqual(endpoints *v1.Endpoints, endpointSliceList *discoveryv1.EndpointSliceList) bool { // get the apiserver endpoint addresses epAddresses := sets.NewString() epPorts := sets.NewInt32() for _, subset := range endpoints.Subsets { for _, addr := range subset.Addresses { epAddresses.Insert(addr.IP) } for _, addr := range subset.NotReadyAddresses { epAddresses.Insert(addr.IP) } for _, port := range subset.Ports { epPorts.Insert(port.Port) } } framework.Logf(\"Endpoints addresses: %v , ports: %v\", epAddresses.List(), epPorts.List()) // Endpoints are single stack, and must match the primary IP family of the Service kubernetes.default // However, EndpointSlices can be IPv4 or IPv6, we can only compare the Slices that match the same IP family // framework.TestContext.ClusterIsIPv6() reports the IP family of the kubernetes.default service var addrType discoveryv1.AddressType if framework.TestContext.ClusterIsIPv6() { addrType = discoveryv1.AddressTypeIPv6 } else { addrType = discoveryv1.AddressTypeIPv4 } // get the apiserver addresses from the endpoint slice list sliceAddresses := sets.NewString() slicePorts := sets.NewInt32() for _, slice := range endpointSliceList.Items { if slice.AddressType != addrType { framework.Logf(\"Skipping slice %s: wanted %s family, got %s\", slice.Name, addrType, slice.AddressType) continue } for _, s := range slice.Endpoints { sliceAddresses.Insert(s.Addresses...) } for _, ports := range slice.Ports { if ports.Port != nil { slicePorts.Insert(*ports.Port) } } } framework.Logf(\"EndpointSlices addresses: %v , ports: %v\", sliceAddresses.List(), slicePorts.List()) if sliceAddresses.Equal(epAddresses) && slicePorts.Equal(epPorts) { return true } return false } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-7f1e6e7766f66194a4a76f7bcbc82118fdef24c779ae808892b54bf44f2870dc", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --E2E test fails. The test is implemented at: I would expect the test pass with these objects in place: AFAIK this fulfills the general requirement of the test that there's a corresponding endpointslice object with same addressing information as is on the endpoint object. IMO the test should rather look for epslice which is owned by the endpoint rather than relying on a hardcoded name. Add flag to kube-apiserver Manually create the endpoint with proper addressing for the api-server epslice \"mirroring\" create new endpointslice with name like --The test fails as it's hardcoded to look for endpointslice named I'm working on a PR to provide a fix proposal Kubernetes version (use ): 1.22.1 Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: k0s Network plugin and version (if this is a network-related bug): kube-router 1.3.1 Others:\n/sig testing\n/remove-sig testing /sig network EndpointSlices are owned by sig network.\n/kind failing-test\n/remove kind-bug /remove kind-failing-test The test is correct, apiserver must generates both endpoint and enpointslices with the special name \"kubernetes\" , that are the backends for the \"kubernetes.default\" service with the IP addresses of the apiservers. This special service \"kubernetes.default\" and its endpoints are used by clients with In-Cluster auto discovery. I think that whatever cluster that is not generating the endpoint and endpointslices for the \"kubernetes.default\" service should not meet Conformance, at least I can't see how automatic in-cluster configuration will work without that ... I only see option used for webhook tests, the other 2 reconcilers always create the endpoints and slices for \"kubernetes.default\" should we clarify the goal of this \"none\" option?\nYes, I do understand this. And in our case this is true, there is a svc called as there is also endpoints object called . This makes the in-cluster discovery work.", "commid": "kubernetes_issue_104612", "tokennum": 531}], "negative_passages": []}
{"query_id": "q-en-kubernetes-99d35e6ff66d8241fd163312bb7fd9e796f74f675c8c79d853ce85310e38c881", "query": "framework.ExpectNoError(err, \"error deleting Service\") return svc } <ins> // endpointSlicesEqual compare if the Endpoint and the EndpointSliceList contains the same endpoints values // as in addresses and ports, considering Ready and Unready addresses func endpointSlicesEqual(endpoints *v1.Endpoints, endpointSliceList *discoveryv1.EndpointSliceList) bool { // get the apiserver endpoint addresses epAddresses := sets.NewString() epPorts := sets.NewInt32() for _, subset := range endpoints.Subsets { for _, addr := range subset.Addresses { epAddresses.Insert(addr.IP) } for _, addr := range subset.NotReadyAddresses { epAddresses.Insert(addr.IP) } for _, port := range subset.Ports { epPorts.Insert(port.Port) } } framework.Logf(\"Endpoints addresses: %v , ports: %v\", epAddresses.List(), epPorts.List()) // Endpoints are single stack, and must match the primary IP family of the Service kubernetes.default // However, EndpointSlices can be IPv4 or IPv6, we can only compare the Slices that match the same IP family // framework.TestContext.ClusterIsIPv6() reports the IP family of the kubernetes.default service var addrType discoveryv1.AddressType if framework.TestContext.ClusterIsIPv6() { addrType = discoveryv1.AddressTypeIPv6 } else { addrType = discoveryv1.AddressTypeIPv4 } // get the apiserver addresses from the endpoint slice list sliceAddresses := sets.NewString() slicePorts := sets.NewInt32() for _, slice := range endpointSliceList.Items { if slice.AddressType != addrType { framework.Logf(\"Skipping slice %s: wanted %s family, got %s\", slice.Name, addrType, slice.AddressType) continue } for _, s := range slice.Endpoints { sliceAddresses.Insert(s.Addresses...) } for _, ports := range slice.Ports { if ports.Port != nil { slicePorts.Insert(*ports.Port) } } } framework.Logf(\"EndpointSlices addresses: %v , ports: %v\", sliceAddresses.List(), slicePorts.List()) if sliceAddresses.Equal(epAddresses) && slicePorts.Equal(epPorts) { return true } return false } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-e7b624ebdf04c04b0fd86ae888848c4f91744879af316f1243574b67dd031473", "text": "Otherwise we'd get much more errors in the conformance instead of this only one... :) In our case we're relying on the endpointslice mirroring to take care of creating the endpointslice object, which makes this test fail as it uses generated \"suffix\" on the object name. I have not dived too deep (yet) into the internals of endpointslices but I fail to see how the endpointslice object name really matters when both svc and endpoint object does have proper name.\noh, this seems interesting then ... who is creating the corresponding endpoint? can you paste a kubectl get endpoints -o yaml?\nthis is how it looks like in my cluster\nIn our case (k0s distro) it's our custom controller that is triggered when the controlplane is configured in HA mode. So this basically sets the api to mode . When our controller runs it has a configured LB address which it resolves to IP address(es) and creates the corresponding EP object. We do NOT create the endpointslice as we rely on the mirroring functionality to let it create and sync it. Here's the object details: Reading the code for API built-in endpoint reconcilers I see they set and create the endpointslice object by themselves. Yes, we could do that too in k0s but I fail to see why the name of the endpointslice object really matters at all.\nI agree the conformance test should not be looking up endpointslice by name. It should be using a label selector of to locate one or more endpointslices and verifying the ports and endpoints across them.\nFair enough, on the good side this also will simplify the KEP from to dual-stack the apiserver you are the expert in this area, can you PTAL at this discussion? /kind failing-test\nhmm the test description explicitly says the name of the object has to be \"kubernetes\", if the name is mandatory the test is correct, otherwise we need to rewrite the test description and talk with conformance people /area conformance\nthe description should be rewritten... the test is enforcing stricter requirements on endpointslices than required/expected\n/triage accepted", "commid": "kubernetes_issue_104612", "tokennum": 469}], "negative_passages": []}
{"query_id": "q-en-kubernetes-99df29ea730fb11a83c6b490c6f031e43d534c8163d6696c3cce6bd658a3c495", "query": "docs/user-guide/kubectl/kubectl_alpha.md docs/user-guide/kubectl/kubectl_alpha_diff.md docs/user-guide/kubectl/kubectl_annotate.md <ins> docs/user-guide/kubectl/kubectl_api-resources.md </ins> docs/user-guide/kubectl/kubectl_api-versions.md docs/user-guide/kubectl/kubectl_apply.md docs/user-guide/kubectl/kubectl_apply_edit-last-applied.md", "positive_passages": [{"docid": "doc-en-kubernetes-3c17ea4b4f4a9bb23915ee9fbb41703ef0532ac00becc05b8dda4d23a9ea9da2", "text": "As the RBAC role need to be related to resources. I think we could use a command to get the supported resources. ref to\nThis would be cool.\nI thought we a command that listed resources in the discover doc a long time ago.\nis just the versions, but principle is the same. We want to list all the types, their resources, and tie that back to \"explain\".\nWhat's the best way to determine this information currently? I'm having difficulty figuring out the exact set of permissions (and how they would be written in an RBAC role) for any given kubectl command. The documentation for this right now is split across multiple places and certain things are not explained at all. Specifically, it's difficult to determine which \"API verb\" is used for which operations. Take as an example. It's unclear if the way to allow this is to use the \"proxy\" subresource of a pod or service with \"get\"/\"create\"/etc. verbs, or to use the \"proxy\" verb with the resource (pod, service) directly. is a similar case. The almost works for this purpose, but it's still difficult. Operations for a given resource are grouped into categories like write, read, status, and proxy, but these things don't obviously correlate with API verbs. Again, proxy is especially confusing as there is no mention of a proxy \"verb\". The API operations are only shown using their HTTP verbs. One thing that could help on this document would be a section on the right column under \"kubectl command\" that shows exactly the rule needed in an RBAC role to allow this command via kubectl. And even then, that assumes an exact 1-to-1 mapping between API endpoints and kubectl commands, which I doubt is always the case. (For example, port fowarding to a pod seems to require both a GET on the pod resource and a CREATE on a port forward subresource.) There also needs to be better documentation about how this information could have been determined in the first place. I've resorted to manually looking through API requests made with but even then it's difficult to figure out. Amusingly, I was the one who wrote which is referenced in the original issue description (as well as the table explaining verbs in ).", "commid": "kubernetes_issue_42932", "tokennum": 494}], "negative_passages": []}
{"query_id": "q-en-kubernetes-99df29ea730fb11a83c6b490c6f031e43d534c8163d6696c3cce6bd658a3c495", "query": "docs/user-guide/kubectl/kubectl_alpha.md docs/user-guide/kubectl/kubectl_alpha_diff.md docs/user-guide/kubectl/kubectl_annotate.md <ins> docs/user-guide/kubectl/kubectl_api-resources.md </ins> docs/user-guide/kubectl/kubectl_api-versions.md docs/user-guide/kubectl/kubectl_apply.md docs/user-guide/kubectl/kubectl_apply_edit-last-applied.md", "positive_passages": [{"docid": "doc-en-kubernetes-20fd632aaf82ba3efee7609ebeda29ca6df3199abf73ef8bcfe417660974a0ce", "text": "tl;dr: It's too difficult right now to go from \"I want a user to be able to run \" to \"here is the RBAC rule to use for that\" for any case where there isn't a specific example shown in the docs.\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nIt seem that relative PR stop updated. If this issue still valuable, i will help fix it\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close", "commid": "kubernetes_issue_42932", "tokennum": 279}], "negative_passages": []}
{"query_id": "q-en-kubernetes-99df2f0270740022a532746a24ed9d7144f74862dd41c7283ee358de0dc3849a", "query": "fs.MarkDeprecated(\"non-masquerade-cidr\", \"will be removed in a future version\") fs.BoolVar(&f.KeepTerminatedPodVolumes, \"keep-terminated-pod-volumes\", f.KeepTerminatedPodVolumes, \"Keep terminated pod volumes mounted to the node after the pod terminates.  Can be useful for debugging volume related issues.\") fs.MarkDeprecated(\"keep-terminated-pod-volumes\", \"will be removed in a future version\") <del> fs.BoolVar(&f.EnableCAdvisorJSONEndpoints, \"enable-cadvisor-json-endpoints\", f.EnableCAdvisorJSONEndpoints, \"Enable cAdvisor json /spec and /stats/* endpoints.  [default=false]\") </del> <ins> fs.BoolVar(&f.EnableCAdvisorJSONEndpoints, \"enable-cadvisor-json-endpoints\", f.EnableCAdvisorJSONEndpoints, \"Enable cAdvisor json /spec and /stats/* endpoints. This flag has no effect on the /stats/summary endpoint.  [default=false]\") </ins> // TODO: Remove this flag in 1.20+.  https://github.com/kubernetes/kubernetes/issues/68522 fs.MarkDeprecated(\"enable-cadvisor-json-endpoints\", \"will be removed in a future version\") fs.BoolVar(&f.ReallyCrashForTesting, \"really-crash-for-testing\", f.ReallyCrashForTesting, \"If true, when panics occur crash. Intended for testing.\")", "positive_passages": [{"docid": "doc-en-kubernetes-2fbecb3a2a825518f63af71ef5aa66b86ea1fb43ba7fb1eee661c2cc82f50635", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Update the help text for kubelet's flag to explicitly mention that it has no effect over the endpoint. Why is this needed: The help text for kubelet's flag describes it as \"Enable cAdvisor json and endpoints.\" which would seem to include , however this is not the case as that endpoint is required by kube-metrics-server and exposes stats from cadvisor or CRI (depending on the stat provider selected internally). Related Issues: /sig node /sig instrumentation /kind documentation\n/kind documentation /triage accepted /help\nThis request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /kind documentation /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\n/assign This should be updated in as well as (unless there is some automated process that updates the website from the options in code that I'm not aware of).\nTo summarize a conversation in slack, it appears there is a documented procedure for updating the website found at The procedure is long, so it is tempting to just copy in the small amount of text that was changed from into a website PR rather than pulling down so many moving parts. In any case, we likely should keep this issue open until both the change to and an associated website change are merged.\ncan you link to the Slack convo?\nCan do - The conversation ended with a question whether there is a bug that would prevent an automated update of the documentation or if we need to submit a PR now that the fix has merged. I searched for an issue but didn't find a match. So we can either try to find someone on sig-docs who might know if there is an issue if it should be updated automagically, or just fix the doc if the website didn't get updated (and I just checked the master branch and it has not been updated yet).\nJust in case that is the right answer, I created the PR.\nI think the website gets autogenerated upon point releases but that'd be a good thing to clarify with the website team. I'll leave a comment asking as much.", "commid": "kubernetes_issue_96483", "tokennum": 525}], "negative_passages": []}
{"query_id": "q-en-kubernetes-99ff62c2022af1a3ed2e6bcdac5346cae6b5612ae4d3c5fc1ecc65360713a811", "query": "<del> ## JSON-Patch </del> <ins> # JSON-Patch `jsonpatch` is a library which provides functionallity for both applying [RFC6902 JSON patches](http://tools.ietf.org/html/rfc6902) against documents, as well as for calculating & applying [RFC7396 JSON merge patches](https://tools.ietf.org/html/rfc7396). </ins> <del> Provides the ability to modify and test a JSON according to a [RFC6902 JSON patch](http://tools.ietf.org/html/rfc6902) and [RFC7396 JSON Merge Patch](https://tools.ietf.org/html/rfc7396). </del> <ins> [![GoDoc](https://godoc.org/github.com/evanphx/json-patch?status.svg)](http://godoc.org/github.com/evanphx/json-patch) [![Build Status](https://travis-ci.org/evanphx/json-patch.svg?branch=master)](https://travis-ci.org/evanphx/json-patch) [![Report Card](https://goreportcard.com/badge/github.com/evanphx/json-patch)](https://goreportcard.com/report/github.com/evanphx/json-patch) </ins> <del> *Version*: **1.0** </del> <ins> # Get It! </ins> <del> [![GoDoc](https://godoc.org/github.com/evanphx/json-patch?status.svg)](http://godoc.org/github.com/evanphx/json-patch) </del> <ins> **Latest and greatest**: ```bash go get -u github.com/evanphx/json-patch ``` </ins> <del> [![Build Status](https://travis-ci.org/evanphx/json-patch.svg?branch=master)](https://travis-ci.org/evanphx/json-patch) </del> <ins> **Stable Versions**: * Version 3: `go get -u gopkg.in/evanphx/json-patch.v3` (previous versions below `v3` are unavailable) # Use It! * [Create and apply a merge patch](#create-and-apply-a-merge-patch) * [Create and apply a JSON Patch](#create-and-apply-a-json-patch) * [Comparing JSON documents](#comparing-json-documents) * [Combine merge patches](#combine-merge-patches) ## Create and apply a merge patch Given both an original JSON document and a modified JSON document, you can create a [Merge Patch](https://tools.ietf.org/html/rfc7396) document. It can describe the changes needed to convert from the original to the modified JSON document. Once you have a merge patch, you can apply it to other JSON documents using the `jsonpatch.MergePatch(document, patch)` function. ```go package main import ( \"fmt\" jsonpatch \"github.com/evanphx/json-patch\" ) func main() { // Let's create a merge patch from these two documents... original := []byte(`{\"name\": \"John\", \"age\": 24, \"height\": 3.21}`) target := []byte(`{\"name\": \"Jane\", \"age\": 24}`) patch, err := jsonpatch.CreateMergePatch(original, target) if err != nil { panic(err) } // Now lets apply the patch against a different JSON document... alternative := []byte(`{\"name\": \"Tina\", \"age\": 28, \"height\": 3.75}`) modifiedAlternative, err := jsonpatch.MergePatch(alternative, patch) fmt.Printf(\"patch document:   %sn\", patch) fmt.Printf(\"updated alternative doc: %sn\", modifiedAlternative) } ``` When ran, you get the following output: ```bash $ go run main.go patch document:   {\"height\":null,\"name\":\"Jane\"} updated tina doc: {\"age\":28,\"name\":\"Jane\"} ``` ## Create and apply a JSON Patch You can create patch objects using `DecodePatch([]byte)`, which can then be applied against JSON documents. The following is an example of creating a patch from two operations, and applying it against a JSON document. ```go package main import ( \"fmt\" jsonpatch \"github.com/evanphx/json-patch\" ) func main() { original := []byte(`{\"name\": \"John\", \"age\": 24, \"height\": 3.21}`) patchJSON := []byte(`[ {\"op\": \"replace\", \"path\": \"/name\", \"value\": \"Jane\"}, {\"op\": \"remove\", \"path\": \"/height\"} ]`) patch, err := jsonpatch.DecodePatch(patchJSON) if err != nil { panic(err) } modified, err := patch.Apply(original) if err != nil { panic(err) } fmt.Printf(\"Original document: %sn\", original) fmt.Printf(\"Modified document: %sn\", modified) } ``` When ran, you get the following output: ```bash $ go run main.go Original document: {\"name\": \"John\", \"age\": 24, \"height\": 3.21} Modified document: {\"age\":24,\"name\":\"Jane\"} ``` ## Comparing JSON documents Due to potential whitespace and ordering differences, one cannot simply compare JSON strings or byte-arrays directly. As such, you can instead use `jsonpatch.Equal(document1, document2)` to determine if two JSON documents are _structurally_ equal. This ignores whitespace differences, and key-value ordering. ```go package main import ( \"fmt\" jsonpatch \"github.com/evanphx/json-patch\" ) func main() { original := []byte(`{\"name\": \"John\", \"age\": 24, \"height\": 3.21}`) similar := []byte(` { \"age\": 24, \"height\": 3.21, \"name\": \"John\" } `) different := []byte(`{\"name\": \"Jane\", \"age\": 20, \"height\": 3.37}`) if jsonpatch.Equal(original, similar) { fmt.Println(`\"original\" is structurally equal to \"similar\"`) } if !jsonpatch.Equal(original, different) { fmt.Println(`\"original\" is _not_ structurally equal to \"similar\"`) } } ``` When ran, you get the following output: ```bash $ go run main.go \"original\" is structurally equal to \"similar\" \"original\" is _not_ structurally equal to \"similar\" ``` ## Combine merge patches Given two JSON merge patch documents, it is possible to combine them into a single merge patch which can describe both set of changes. The resulting merge patch can be used such that applying it results in a document structurally similar as merging each merge patch to the document in succession. ```go package main import ( \"fmt\" jsonpatch \"github.com/evanphx/json-patch\" ) func main() { original := []byte(`{\"name\": \"John\", \"age\": 24, \"height\": 3.21}`) nameAndHeight := []byte(`{\"height\":null,\"name\":\"Jane\"}`) ageAndEyes := []byte(`{\"age\":4.23,\"eyes\":\"blue\"}`) // Let's combine these merge patch documents... combinedPatch, err := jsonpatch.MergeMergePatches(nameAndHeight, ageAndEyes) if err != nil { panic(err) } // Apply each patch individual against the original document withoutCombinedPatch, err := jsonpatch.MergePatch(original, nameAndHeight) if err != nil { panic(err) } withoutCombinedPatch, err = jsonpatch.MergePatch(withoutCombinedPatch, ageAndEyes) if err != nil { panic(err) } // Apply the combined patch against the original document withCombinedPatch, err := jsonpatch.MergePatch(original, combinedPatch) if err != nil { panic(err) } // Do both result in the same thing? They should! if jsonpatch.Equal(withCombinedPatch, withoutCombinedPatch) { fmt.Println(\"Both JSON documents are structurally the same!\") } fmt.Printf(\"combined merge patch: %s\", combinedPatch) } ``` When ran, you get the following output: ```bash $ go run main.go Both JSON documents are structurally the same! combined merge patch: {\"age\":4.23,\"eyes\":\"blue\",\"height\":null,\"name\":\"Jane\"} ``` # CLI for comparing JSON documents You can install the commandline program `json-patch`. This program can take multiple JSON patch documents as arguments, and fed a JSON document from `stdin`. It will apply the patch(es) against the document and output the modified doc. **patch.1.json** ```json [ {\"op\": \"replace\", \"path\": \"/name\", \"value\": \"Jane\"}, {\"op\": \"remove\", \"path\": \"/height\"} ] ``` **patch.2.json** ```json [ {\"op\": \"add\", \"path\": \"/address\", \"value\": \"123 Main St\"}, {\"op\": \"replace\", \"path\": \"/age\", \"value\": \"21\"} ] ``` </ins> <del> ### API Usage </del> <ins> **document.json** ```json { \"name\": \"John\", \"age\": 24, \"height\": 3.21 } ``` </ins> <del> * Given a `[]byte`, obtain a Patch object </del> <ins> You can then run: </ins> <del> `obj, err := jsonpatch.DecodePatch(patch)` </del> <ins> ```bash $ go install github.com/evanphx/json-patch/cmd/json-patch $ cat document.json | json-patch -p patch.1.json -p patch.2.json {\"address\":\"123 Main St\",\"age\":\"21\",\"name\":\"Jane\"} ``` </ins> <del> * Apply the patch and get a new document back </del> <ins> # Help It! Contributions are welcomed! Leave [an issue](https://github.com/evanphx/json-patch/issues) or [create a PR](https://github.com/evanphx/json-patch/compare). </ins> <del> `out, err := obj.Apply(doc)` * Create a JSON Merge Patch document based on two json documents (a to b): </del> <ins> Before creating a pull request, we'd ask that you make sure tests are passing and that you have added new tests when applicable. </ins> <del> `mergeDoc, err := jsonpatch.CreateMergePatch(a, b)` * Bonus API: compare documents for structural equality </del> <ins> Contributors can run tests using: </ins> <del> `jsonpatch.Equal(doca, docb)` </del> <ins> ```bash go test -cover ./... ``` Builds for pull requests are tested automatically using [TravisCI](https://travis-ci.org/evanphx/json-patch). </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-e51351c05e6844b765acf34eaa6a0653d5a4e3452baed4722f32f9c5caa3ece5", "text": "/kind bug What happened: Wrote a that returned a faulty json patch which specified an our of range index (e.G. when there is only one container). This resulted in the apiserver crashing. Stacktrace: What you expected to happen: No crash /sig-api-machinery\n/sig api-machinery\nThis maybe a bug in . I will follow this question.\nThis bug had been fixed in PR: you can checkout it.\nThanks for your comment but I don't think the linked PR fixed the issue, as it got merged almost a year ago and I am running Kube 1.10.1 which does contain that patch but still panics. Just from quickly looking at the code I the linked PR I believe there are two things wrong: The check if the index is valid only happens when a negative index was given should be\nOnce the PR of is merged I will update kubernetes.\n/kind bug", "commid": "kubernetes_issue_64291", "tokennum": 194}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9a0b9185ee586b2da20cc3631977604149db73070176de267f7992383dadba4e", "query": "glog.Fatalf(\"unable to create flag defaults: %v\", err) } <del> opts.AddFlags(pflag.CommandLine) </del> <ins> opts.AddFlags(cmd.Flags()) </ins> cmd.MarkFlagFilename(\"config\", \"yaml\", \"yml\", \"json\")", "positive_passages": [{"docid": "doc-en-kubernetes-5044536d87edb25c665421bf3dc4b536a0586e8213d754dc6188da659a17c1aa", "text": "There are no sig labels on this issue. Please add a sig label. <detailsA sig label can be by either: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. See the . The in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals 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\nprobably caused by\nCould be a clash between these two?\ncc\nI still see the issue with local-cluster on the latest master: F0225 17:06:49. ] error: v1alpha1.KubeProxyConfiguration: FeatureGates: ReadMapCB: expect { or n, but found \", error found in byte of ......\nlooks like that's another issue, can you please file a new bug? with more logs? this one was about none of the hyperkube based processes starting up.\nwill do as it is also broke container kube-proxy as well. Same type of error.", "commid": "kubernetes_issue_60378", "tokennum": 274}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9a1c1de2c8454232d2df0e8c6309c985ca7ff90337c6d2e6d42d862ca82aac6b", "query": "if [ ! -w $(dirname `which gcloud`) ]; then sudo_prefix=\"sudo\" fi <del> ${sudo_prefix} gcloud ${gcloud_prompt:-} components update alpha || true ${sudo_prefix} gcloud ${gcloud_prompt:-} components update beta || true </del> <ins> ${sudo_prefix} gcloud ${gcloud_prompt:-} components install alpha || true ${sudo_prefix} gcloud ${gcloud_prompt:-} components install beta || true </ins> ${sudo_prefix} gcloud ${gcloud_prompt:-} components update || true }", "positive_passages": [{"docid": "doc-en-kubernetes-e853f94b17b31c823d86645df008663c9942e2f2dd039e3926420121cf6b1093", "text": "This is really annoying because it requires me to interact with my shell while running up / down whereas before the commands just ran to completion on their own.", "commid": "kubernetes_issue_18374", "tokennum": 30}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9a37a5fc6b2c420b9f7387f1d9cea53e81adb6a5f47afdfbd9e96672dd8ea14c", "query": "package testing import ( <del> \"encoding/json\" </del> \"fmt\" \"math/rand\" <del> \"os\" \"path/filepath\" </del> <ins> \"sigs.k8s.io/structured-merge-diff/v4/typed\" </ins> \"strconv\" <del> \"strings\" </del> \"sync\" \"testing\"", "positive_passages": [{"docid": "doc-en-kubernetes-29db4d0749071d4e54a9083e12a93fb8b6b43cd54c28626ec2efc45861483a16", "text": "Smoke tests run by publishing-bot on client-go master are failing Ref for failure logs: Tests defined for client-go, after publishing, Since commit No response As part of , when module is used from within the staging directory, can be used by traversing to the parent directory. But once the module is made as a separate repository as part of publishing, then traversing to repository using path will not work. No response /sig-api-machinery\n/sig api-machinery\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /sig api-machinery 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\nLooking\nI'll remove the swagger file dependency, I don't think we strictly need it.\n/triage accepted", "commid": "kubernetes_issue_125704", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9a3911e23d79b609d32b7100c79844384085a6ac9c5f38eacdce2c1e3dfecd4f", "query": "<ins> apiVersion: v1beta1 desiredState: manifest: containers: - image: kubernetes/pause name: testpd volumeMounts: - mountPath: \"/testpd\" name: \"testpd\" id: testpd version: v1beta1 volumes: - name: testpd source: persistentDisk: # This GCE PD must already exist and be formatted ext4 pdName: \"%insert_pd_name_here%\" fsType: ext4 id: testpd kind: Pod labels: test: testpd </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-4cc03be8a4c78b1eefdd458c17e35e10d17eae1288a6e1bcb08b9d7d585d4633", "text": "07-02 and 13-02 No response No response /sig\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scalability\nI might be related to the npd.\nThe same test failures happening again on 25.02:\n/sig node\n/sig node /cc The restart of caused the flake. I also opened to track it in NPD repo.\nI missed this log. It is caused by oom. Adding some memory may help. I submitted to fix it. Does mean killing metrics-server?\n/remove-sig node Sorry, I misread the log. The NPD found the metric server is OOM. It is about the metrics server, not the NPD. Sorry for disturb. I may add some memory for metric-server and check why metric server memory changed. I heard that metrics server recently released a new version. I will check if it is related.\n/sig node\nOOM metrics shows the metric server is OOMed. This is odd, that only metrics-server-nanny is with a memory limit. It uses whose command is . metrics-server container has no memory limit, but it got killed by OOM. Does this indicate that the node is OOM? (edited)\nThe last run failed in node-problem-detector ContainerStateTerminated. I0227 05:03:31. ] PodStartupLatency: perc50: 14m29.018886827s, perc90: 28m44.625518807s, perc99: 32m2.19303496s; threshold 1h0m0s I0227 05:03:32. ]", "commid": "kubernetes_issue_123328", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9a3911e23d79b609d32b7100c79844384085a6ac9c5f38eacdce2c1e3dfecd4f", "query": "<ins> apiVersion: v1beta1 desiredState: manifest: containers: - image: kubernetes/pause name: testpd volumeMounts: - mountPath: \"/testpd\" name: \"testpd\" id: testpd version: v1beta1 volumes: - name: testpd source: persistentDisk: # This GCE PD must already exist and be formatted ext4 pdName: \"%insert_pd_name_here%\" fsType: ext4 id: testpd kind: Pod labels: test: testpd </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-a11072f45f81b280dea24734413173747c87bdd472ce068bad905ce856d1cb81", "text": "Loaded restart count threshold overrides: map[coredns:2 fluentd-gcp:999 konnectivity-agent:2 kube-controller-manager:1 kube-proxy:2 kube-scheduler:1 l7-lb-controller:1 metadata-proxy:2 prometheus-to-sd-exporter:2] I0227 05:03:32. ] ClusterOOMsTracker: gathering cluster OOMs tracking measurement E0227 05:03:32. ] TestMetrics: [action gather failed for SystemPodMetrics measurement: restart counts violation: RestartCount(node-problem-detector-tgl8h, node-problem-detector)=1, want <= 0; RestartCount(node-problem-detector-vpsmz, node-problem-detector)=1, want <= 0] I0227 05:03:32. ] Step \"[step: 29] gathering measurements\" ended W0227 05:03:32. ] Got errors during step execution: [measurement call TestMetrics - TestMetrics error: [action gather failed for SystemPodMetrics measurement: restart counts violation: RestartCount(node-problem-detector-tgl8h, node-problem-detector)=1, want <= 0; RestartCount(node-problem-detector-vpsmz, node-problem-detector)=1, want <= 0]] I0227 05:03:32. ] Waiting for the chaos monkey subroutine to end... I0227 05:03:32. ] Chaos monkey ended. I0227 05:03:32. ] I0227 05:03:32. ] Stopping DnsLookupLatency probe... I0227 05:03:47. ] Stopping InClusterNetworkLatency probe... I0227 05:04:22. ] Resources cleanup time: 50.539700215s E0227 05:04:22. ]\nE0227 05:04:22. ] Test Finished E0227 05:04:22. ] Test: E0227 05:04:22. ] Status: Fail E0227 05:04:22. ]", "commid": "kubernetes_issue_123328", "tokennum": 491}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9a3911e23d79b609d32b7100c79844384085a6ac9c5f38eacdce2c1e3dfecd4f", "query": "<ins> apiVersion: v1beta1 desiredState: manifest: containers: - image: kubernetes/pause name: testpd volumeMounts: - mountPath: \"/testpd\" name: \"testpd\" id: testpd version: v1beta1 volumes: - name: testpd source: persistentDisk: # This GCE PD must already exist and be formatted ext4 pdName: \"%insert_pd_name_here%\" fsType: ext4 id: testpd kind: Pod labels: test: testpd </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-8045aaa7c39478c40c58e17441fd375a472ca56f31885311d26bd40c11b2233d", "text": "Errors: [measurement call TestMetrics - TestMetrics error: [action gather failed for SystemPodMetrics measurement: restart counts violation: RestartCount(node-problem-detector-tgl8h, node-problem-detector)=1, want <= 0; RestartCount(node-problem-detector-vpsmz, node-problem-detector)=1, want <= 0]] E0227 05:04:22. ]\nI0227 05:04:22. ]\nI0227 05:04:22. ] Running testing/huge- I0227 05:04:22. ]", "commid": "kubernetes_issue_123328", "tokennum": 136}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9a4fe3d35b495ec3148d7b4d3569fda7c2f4335e2632548313cd9d00ed7b42fa", "query": "- subresource - verb - version <ins> - name: apiserver_storage_object_counts help: Number of stored objects at the time of last check split by kind. type: Gauge stabilityLevel: STABLE labels: - resource </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-49b5f1148571079e399a01da886ccfbbffa2370f5f5a5844a5ac847b772993f9", "text": "What would you like to be : We want to start migrating metrics which people depend on for operations to stable status. etcdobjectcounts was mentioned in a recent SIG meeting as a viable candidate. However, the 'etcd' prefix is not in line with stated metric conventions. SIG consensus determined that creating a new version of the metric with the metric name 'apiserverstorageobjectcounts' would be sufficient allow this metric to be promoted. We'd want to simultaneously deprecate 'etcdobjectcounts' (since it would be a duplicate) and remove it after the deprecation grace period window. /assign /cc\nGitHub didn't allow me to assign the following users: erain. 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 : What would you like to be : /cc 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\n/sig instrumentation api-machinery /cc\nAck. I am going to work on this.\n/assign /triage accepted\nIn the SIG api-machinery meeting today, we agreed that the stable version of this metric should be named 'apiserverstorageobject_count'\nThanks and will use in the PR. (And sorry for missing today's meeting - due to a conflict)", "commid": "kubernetes_issue_98270", "tokennum": 331}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9a681cc131426e27814583936498eeaf5511d3a37b2562028a8968a6c0e3a4af", "query": "return nil } <ins> //waitForServiceEndpointsNum waits until the amount of endpoints that implement service to expectNum. func waitForServiceEndpointsNum(c *client.Client, namespace, serviceName string, expectNum int, interval, timeout time.Duration) error { return wait.Poll(interval, timeout, func() (bool, error) { Logf(\"Waiting for amount of service:%s endpoints to %d\", serviceName, expectNum) list, err := c.Endpoints(namespace).List(labels.Everything()) if err != nil { return false, err } for _, e := range list.Items { if e.Name == serviceName && countEndpointsNum(&e) == expectNum { return true, nil } } return false, nil }) } func countEndpointsNum(e *api.Endpoints) int { num := 0 for _, sub := range e.Subsets { num += len(sub.Addresses) } return num } </ins> // waitForReplicationController waits until the RC appears (exist == true), or disappears (exist == false) func waitForReplicationController(c *client.Client, namespace, name string, exist bool, interval, timeout time.Duration) error { err := wait.Poll(interval, timeout, func() (bool, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-57d83ef880aa3c3668480a2a99a63d94dfed9404bcfb6c9db559f5ee8b331861", "text": "More detail can be seen in e2e test\ncc\n, Marek Grabowski wrote:\nyou are running an older version of the test. can you get the latest and try again ? This test had not failed at all yesterday in our automated test runs yesterday. Closing issue for now.\nThis failure depends on if the pod is really deleted and kube-proxy (the test container on) catch that the endpoint is deleted in 5s . After sending \"delete pod\" request for 5s, if the pod was still there and kube-proxy still contains this endpoints(this may happen under pressure), hit test can still detect 5 endpoints. At least we should ensure the pod was deleted. Anyway, I think will be helpful to this test. What do you think?\nIt doesn't matter if the pod is actually deleted or not. We just care that kube-proxy thinks that it should not be part of the service endpoint. Having said that, it still doesn't hurt to do the check that you are doing. I will assign your PR to myself and review it. In the meantime, can you rebase your PR ?\nThanks for your review. The PR is up to date.\nFailed twice today in kubernetes-e2e-gce-parallel\nOne more today. The error message is not very helpful.\n18:28:37 STEP: dialing(http) endpointPodIP:endpointHttpPort from node1 18:28:37 STEP: Dialing from node. command:for i in ' wc -l This is the point where the test fails. Am looking into it. We need to have more tries, we just do seq (1 1), instead of seq (6 6). this is causing flakiness.\nFixed by PR", "commid": "kubernetes_issue_14342", "tokennum": 372}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9a6ceaa827eaa0a2e28ad41abd07db96af7953bb5d21da50a7d24b992b1ce682", "query": "import ( \"fmt\" \"path\" <ins> \"runtime\" </ins> \"strings\" \"sync\"", "positive_passages": [{"docid": "doc-en-kubernetes-295b16ebdca2097490863d761fa466b150fe770891272091eba588ee367ef882", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: I have tried FlexVolume on a Windows node, it does not work. I am now working on this feature now. Below is the FlexVolume initialization error What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.7.7 Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: /sig windows /assign\nDetailed steps about how to use flexvolume on Windows with this PR:\ncc:", "commid": "kubernetes_issue_56875", "tokennum": 183}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9a81dd5834be35eb6afc5480f1d6744bf802d32107eaf2722b12eb9c07da54d1", "query": "//   3.  CurrentDirectoryPath //   4.  HomeDirectoryPath // Empty filenames are ignored.  Files with non-deserializable content produced errors. <del> // The first file to set a particular value or map key wins and the value or map key is never changed. // This means that the first file to set CurrentContext will have its context preserved.  It also means // that if two files specify a \"red-user\", only values from the first file's red-user are used.  Even </del> <ins> // The first file to set a particular map key wins and map key's value is never changed. // BUT, if you set a struct value that is NOT contained inside of map, the value WILL be changed. // This results in some odd looking logic to merge in one direction, merge in the other, and then merge the two. // It also means that if two files specify a \"red-user\", only values from the first file's red-user are used.  Even </ins> // non-conflicting entries from the second file's \"red-user\" are discarded. // Relative paths inside of the .kubeconfig files are resolved against the .kubeconfig file's parent folder // and only absolute file paths are returned. func (rules *ClientConfigLoadingRules) Load() (*clientcmdapi.Config, error) { <del> config := clientcmdapi.NewConfig() mergeConfigWithFile(config, rules.CommandLinePath) resolveLocalPaths(rules.CommandLinePath, config) </del> <ins> kubeConfigFiles := []string{rules.CommandLinePath, rules.EnvVarPath, rules.CurrentDirectoryPath, rules.HomeDirectoryPath} </ins> <del> mergeConfigWithFile(config, rules.EnvVarPath) resolveLocalPaths(rules.EnvVarPath, config) </del> <ins> // first merge all of our maps mapConfig := clientcmdapi.NewConfig() for _, file := range kubeConfigFiles { mergeConfigWithFile(mapConfig, file) resolveLocalPaths(file, mapConfig) } </ins> <del> mergeConfigWithFile(config, rules.CurrentDirectoryPath) resolveLocalPaths(rules.CurrentDirectoryPath, config) </del> <ins> // merge all of the struct values in the reverse order so that priority is given correctly nonMapConfig := clientcmdapi.NewConfig() for i := len(kubeConfigFiles) - 1; i >= 0; i-- { file := kubeConfigFiles[i] mergeConfigWithFile(nonMapConfig, file) resolveLocalPaths(file, nonMapConfig) } </ins> <del> mergeConfigWithFile(config, rules.HomeDirectoryPath) resolveLocalPaths(rules.HomeDirectoryPath, config) </del> <ins> // since values are overwritten, but maps values are not, we can merge the non-map config on top of the map config and // get the values we expect. config := clientcmdapi.NewConfig() mergo.Merge(config, mapConfig) mergo.Merge(config, nonMapConfig) </ins> return config, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-dbcf83004ea3f0459daec6a4d94a4bece404fe8f97225f1a2fba429c343bf057", "text": "I've been pulling my hair out trying get kubectl talk to my local cluster. It seems that kubectl merges the local file with values pulled down from the cloud. I've done the following: The I just set is silently overridden. Questions: is this documented anywhere? should kubectl merge in my GCE cluster when I set my cloud-provider to something else? should kubectl override my previously set current-context?\nworkaround is to use flag to override the config file value.\nbut not a good UX long term\nSomeone else hit this as well: . Better fix is to have the local-up script set a context, which I will try to add today. As for the overwriting behavior, it's documented in , but based on what you describe, the intended load order is not working; local .kubeconfig should overwrite global. cc\nThat sounds infuriating. I'll take a look this morning.", "commid": "kubernetes_issue_4397", "tokennum": 210}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9a94143329d61cadccef10b4aca33433169b0eaee89bcc4382be2cc537fb0835", "query": "apiGroup = apiVersionsToAPIGroup(&v) } apiGroupList.Groups = []metav1.APIGroup{apiGroup} <del> case AcceptV2Beta1: var aggregatedDiscovery apidiscovery.APIGroupDiscoveryList err = json.Unmarshal(body, &aggregatedDiscovery) if err != nil { return nil, nil, nil, err } apiGroupList, resourcesByGV, failedGVs = SplitGroupsAndResources(aggregatedDiscovery) default: return nil, nil, nil, fmt.Errorf(\"Unknown discovery response content-type: %s\", responseContentType) </del> } return apiGroupList, resourcesByGV, failedGVs, nil", "positive_passages": [{"docid": "doc-en-kubernetes-3257ecff81fbc60fa2a8f982346c462089eb7c896f62cce1d4e02ff6df66d913", "text": "We are using (and ) to interact with Kubernetes clusters behind a couple of proxy layers. One of these proxies completes the headers to include character encoding details. This was working fine until recently, when client-go/kubectl have started to fail when interacting with the discovery API. It seems that a recent change has made kubectl more restrictive of the content-type that it expects. I suspect that it is related to this commit: For example, this is an error from a kubectl command: We can of course try to fix it on our end, removing that charset information. However, it is a valid content-type and the way kubectl is handling the content-type there seems like it is relying on implementation details of kube-apiserver (that it does not add metadata to the content-type). I propose to fix this issue in , by properly parsing and handling the content-type.\ncc /kind regression /kind bug /sig api-machinery /priority important-soon looks like the switch statement in downloadLegacy() needs to be more tolerant of the variety of content-types it can get from a server (including text/plain or no content-type if old servers could have returned that...)\n/transfer kubernetes/kubernetes\nSomething went wrong or the destination repo kubernetes/kubernetes/kubernetes does not exist. <detailsIn response to : /transfer kubernetes/kubernetes 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\n/transfer kubernetes\nYep, the string comparison for the content-type is flimsy, let's address that. Thanks for the report!\n/assign\n/triage accepted\n/cc\nThe fix is being cherry-picked back to: : :", "commid": "kubernetes_issue_117562", "tokennum": 408}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9aba69d915c18acbd6541f0e63aed3b04a17e27cc234607d80e9ba46c6d273e5", "query": "fmt.Fprintf(&verboseOut, \"[+]%v okn\", check.Name()) } } <ins> if excluded.Len() > 0 { fmt.Fprintf(&verboseOut, \"warn: some health checks cannot be excluded: no matches for %vn\", formatQuoted(excluded.List()...)) klog.Warningf(\"cannot exclude some health checks, no health checks are installed matching %v\", formatQuoted(excluded.List()...)) } </ins> // always be verbose on failure if failed { http.Error(w, fmt.Sprintf(\"%vhealthz check failed\", verboseOut.String()), http.StatusInternalServerError)", "positive_passages": [{"docid": "doc-en-kubernetes-01cc291fb1d6afeae9b284d60dd407b578a72d26e4c50043cbdf654c92184c45", "text": "What would you like to be : Add support to the kube-apiserver so that we can disable health-checks via query params. Why is this needed: Currently, the healthz endpoint is inflexible in that any and all health checks are currently executed when the endpoint is hit. Since the kube-apiserver only currently supports a liveness check, this means all persistent health check failures will eventually result in a kubelet driven restart. However, this may not be desirable behavior if you have additional monitoring services layered on top of your control plane. For instance, take the etcd failure from the perspective of the kube-apiserver. Currently, persistent failures during the etcd health check from the api-server healthz endpoint will cause the kube-apiserver to be restarted. This sometimes helps (in the case of a faulty etcd-client connection) but also can be detrimental (the kube-apiserver restarts until the etcd cluster is functioning, then the kube-apiserver bombards the etcd cluster with requests to update local caches, saturating the etcd cluster with requests, causing it to timeout on its own liveness probes and trigger a kubelet-driven restart). Let's say that we could now disable etcd from our liveness health check. Then if we had an external monitoring service, we could ask independently ask etcd if it was healthy and we could also ask the kube-apiserver if it thought etcd was unhealthy. Based on the combination of those answers, we could enable more intelligent responses to certain situation, like restarting the kube-apiserver when it thought etcd was unhealthy but etcd was actually reporting as healthy but not doing so when etcd was actually unhealthy. This feature is backwards-compatible and opt-in. There would be no impact to existing behavior unless these query params are actually used. /sig api-machinery /kind feature\n/cc\nSGTM\n/assign", "commid": "kubernetes_issue_70591", "tokennum": 432}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9ad4d8895717dde040bb6028ab289f3c6012f271453f450efaaa258c0ed5510d", "query": "http.Error(w, err.Error(), 400) } <del> // When resetting between tests, a marker object is patched until this webhook // observes it, at which point it is considered ready. if pod.Namespace == reinvocationMarkerFixture.Namespace && pod.Name == reinvocationMarkerFixture.Name { recorder.MarkerReceived() allow(w) return } </del> recorder.IncrementCount(r.URL.Path) switch r.URL.Path { <ins> case \"/marker\": // When resetting between tests, a marker object is patched until this webhook // observes it, at which point it is considered ready. recorder.MarkerReceived() allow(w) return </ins> case \"/noop\": allow(w) case \"/settrue\":", "positive_passages": [{"docid": "doc-en-kubernetes-ddb9bacde18c9f97d2ebd4306efde2d358d8075e932023fee86edf729006549a", "text": "Which jobs are failing: Which test(s) are failing: Since when has it been failing: Testgrid link: Reason for failure: Anything else we need to know: /sig api-machinery /assign\n/cc\nwant to take a look at the audit event issue first? I can dig in after that if issues remain.\nyes, I'm looking at the audit event issue now\nactually the failure message suggests that the missing audit log is caused by unexpected admission invocation: I think it's unrelated to auditing Note that there are two tests named \"no reinvocation of webhook B when in-tree or prior webhook mutations\" :( and from the audit log (), it also suggests that the test is hitting a wrong endpoint\nThanks I'll dig in.", "commid": "kubernetes_issue_82693", "tokennum": 163}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9ae9d858ba1bdd98493fcba9acfeefc23a07b4063b8c51fafe33c6dc0d58d275", "query": "Name: dsName, }, Spec: apps.DaemonSetSpec{ <ins> Selector: &metav1.LabelSelector{ MatchLabels: label, }, </ins> Template: v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Labels: label,", "positive_passages": [{"docid": "doc-en-kubernetes-da00f1cf1a24475bca3717ed24d8bd1cf5079c51cd54d6d4d01b160ed7cae851", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: DaemonSet has an e2e test running that has dubious purpose. What you expected to happen: The e2e test should be refactored and commented clearer as it will be part of the conformance.\nTo elaborate, we're concerned that the following may not actually ensure that DaemonSet recreates Failed Pods: For example, it seems possible that the Node might simply overwrite the Pod status with its own information if it hasn't yet seen the change to the Phase. Ideally, we should verify that the Pod UID we force to Failed no longer shows up in the DaemonSet's list of Pods after the DaemonSet becomes happy again.", "commid": "kubernetes_issue_59076", "tokennum": 150}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9b1730f6557045174dd304b6dff008bf3afe828fa6238ee84b4608a0b542dd93", "query": "t.Fatalf(\"Unexpected error: %v\", err) } } func TestCreateMissingContext(t *testing.T) { <del> const expectedErrorContains = \"Context was not found for specified context\" </del> <ins> const expectedErrorContains = \"context was not found for specified context: not-present\" </ins> config := createValidTestConfig() clientBuilder := NewNonInteractiveClientConfig(*config, \"not-present\", &ConfigOverrides{ ClusterDefaults: DefaultCluster, }, nil) <del> clientConfig, err := clientBuilder.ClientConfig() if err != nil { t.Fatalf(\"Unexpected error: %v\", err) </del> <ins> _, err := clientBuilder.ClientConfig() if err == nil { t.Fatalf(\"Expected error: %v\", expectedErrorContains) </ins> } <del> expectedConfig := &restclient.Config{Host: clientConfig.Host} if !reflect.DeepEqual(expectedConfig, clientConfig) { t.Errorf(\"Expected %#v, got %#v\", expectedConfig, clientConfig) </del> <ins> if !strings.Contains(err.Error(), expectedErrorContains) { t.Fatalf(\"Expected error: %v, but got %v\", expectedErrorContains, err) </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-f651131826f05881213cb9e37bd90a3c65eb2d3012bfdb53d9a39fc66f409d28", "text": "In 1.1, if you specify \"current-context: i-do-not-exist\" in a kubeconfig, and there's no matching context by that name in the contexts, kubelet silently uses what I assume is either an empty or a default configuration. This can result in hilarity like wondering why your kubelet isn't using the TLS settings you provided, and spending several hours debugging the whole stack only to discover that you typo'd current-context :). It would be better if kubelet and other users of errored out on such a misconfiguration, to make the failure obvious and trivial.\ncc\nI think kubelet silently uses an empty configuration. Guess we should give a waring here.\nDid you start to work on this?\nBelow is related code: can you confirm this? Besides if we want to log a waring in kubelet, we may need to get in kubelet.\ncc\ncc\nI believe kubelet already uses . Adding a check in that current context exists if specified sounds like the right approach.\nAre there any backwards compatibility implications here? would this break users who have existing configs (that fallback to default namespace)? , Jeff Lowdermilk wrote:\nI think kubelet directly use not . Also already checks whether the user-specified current context exists, the problem is that if not exist, we just skip. We need to do something if the current context not exist, like log a warning.\nErroring on a specified and bad seems reasonable. If it is not specified and there's only one option, I don't think we should fail.\nyeap, the case is that user specify the but not exist, in such case we should just fail.\nIf no one is working on this I can take it.\nI think this is the root cause. Basically we should error on this not exist context. If you have extra bandwidth, please go ahead :)\nThis is related to - the defaulting is what allows us to continue. When that merges, only kubectl will have the \"use localhost:8080\" as defaulting.", "commid": "kubernetes_issue_21062", "tokennum": 453}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9b206f955426a91127921292d543b454347bd843809717fcf466aa230cef8965", "query": "_, err := framework.RunHostCmd(pausePod1.Namespace, pausePod1.Name, cmd) framework.ExpectError(err, \"expected error when trying to connect to cluster IP\") } <del> }) ginkgo.It(\"should respect internalTrafficPolicy=Local Pod (hostNetwork: true) to Pod (hostNetwork: true) [Feature:ServiceInternalTrafficPolicy]\", func() { // windows kube-proxy does not support this feature yet // TODO: remove this skip when windows-based proxies implement internalTrafficPolicy e2eskipper.SkipIfNodeOSDistroIs(\"windows\") // This behavior is not supported if Kube-proxy is in \"userspace\" mode. // So we check the kube-proxy mode and skip this test if that's the case. if proxyMode, err := proxyMode(f); err == nil { if proxyMode == \"userspace\" { e2eskipper.Skipf(\"The test doesn't work with kube-proxy in userspace mode\") } } else { framework.Logf(\"Couldn't detect KubeProxy mode - test failure may be expected: %v\", err) } </del> <ins> ginkgo.By(\"Creating 2 pause hostNetwork pods that will try to connect to the webserver\") pausePod2 := e2epod.NewAgnhostPod(ns, \"pause-pod-2\", nil, nil, nil) pausePod2.Spec.HostNetwork = true e2epod.SetNodeSelection(&pausePod2.Spec, e2epod.NodeSelection{Name: node0.Name}) </ins> <del> nodes, err := e2enode.GetBoundedReadySchedulableNodes(cs, 2) </del> <ins> pausePod2, err = cs.CoreV1().Pods(ns).Create(context.TODO(), pausePod2, metav1.CreateOptions{}) </ins> framework.ExpectNoError(err) <del> nodeCounts := len(nodes.Items) if nodeCounts < 2 { e2eskipper.Skipf(\"The test requires at least two ready nodes on %s, but found %v\", framework.TestContext.Provider, nodeCounts) } node0 := nodes.Items[0] node1 := nodes.Items[1] </del> <ins> framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, pausePod2.Name, f.Namespace.Name, framework.PodStartTimeout)) </ins> <del> serviceName := \"svc-itp\" ns := f.Namespace.Name servicePort := 80 </del> <ins> pausePod3 := e2epod.NewAgnhostPod(ns, \"pause-pod-3\", nil, nil, nil) pausePod3.Spec.HostNetwork = true e2epod.SetNodeSelection(&pausePod3.Spec, e2epod.NodeSelection{Name: node1.Name}) </ins> <del> ginkgo.By(\"creating a TCP service \" + serviceName + \" with type=ClusterIP and internalTrafficPolicy=Local in namespace \" + ns) local := v1.ServiceInternalTrafficPolicyLocal jig := e2eservice.NewTestJig(cs, ns, serviceName) svc, err := jig.CreateTCPService(func(svc *v1.Service) { svc.Spec.Ports = []v1.ServicePort{ {Port: 80, Name: \"http\", Protocol: v1.ProtocolTCP, TargetPort: intstr.FromInt(80)}, } svc.Spec.InternalTrafficPolicy = &local }) framework.ExpectNoError(err) ginkgo.By(\"Creating 1 webserver pod to be part of the TCP service\") webserverPod0 := e2epod.NewAgnhostPod(ns, \"echo-hostname-0\", nil, nil, nil, \"netexec\", \"--http-port\", strconv.Itoa(servicePort)) webserverPod0.Labels = jig.Labels webserverPod0.Spec.HostNetwork = true e2epod.SetNodeSelection(&webserverPod0.Spec, e2epod.NodeSelection{Name: node0.Name}) _, err = cs.CoreV1().Pods(ns).Create(context.TODO(), webserverPod0, metav1.CreateOptions{}) </del> <ins> pausePod3, err = cs.CoreV1().Pods(ns).Create(context.TODO(), pausePod3, metav1.CreateOptions{}) </ins> framework.ExpectNoError(err) <del> framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, webserverPod0.Name, f.Namespace.Name, framework.PodStartTimeout)) validateEndpointsPortsOrFail(cs, ns, serviceName, portsByPodName{webserverPod0.Name: {servicePort}}) ginkgo.By(\"Creating 2 pause pods that will try to connect to the webservers\") pausePod0 := e2epod.NewAgnhostPod(ns, \"pause-pod-0\", nil, nil, nil) pausePod0.Spec.HostNetwork = true e2epod.SetNodeSelection(&pausePod0.Spec, e2epod.NodeSelection{Name: node0.Name}) pausePod0, err = cs.CoreV1().Pods(ns).Create(context.TODO(), pausePod0, metav1.CreateOptions{}) framework.ExpectNoError(err) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, pausePod0.Name, f.Namespace.Name, framework.PodStartTimeout)) pausePod1 := e2epod.NewAgnhostPod(ns, \"pause-pod-1\", nil, nil, nil) pausePod1.Spec.HostNetwork = true e2epod.SetNodeSelection(&pausePod1.Spec, e2epod.NodeSelection{Name: node1.Name}) pausePod1, err = cs.CoreV1().Pods(ns).Create(context.TODO(), pausePod1, metav1.CreateOptions{}) framework.ExpectNoError(err) framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, pausePod1.Name, f.Namespace.Name, framework.PodStartTimeout)) </del> <ins> framework.ExpectNoError(e2epod.WaitTimeoutForPodReadyInNamespace(f.ClientSet, pausePod3.Name, f.Namespace.Name, framework.PodStartTimeout)) </ins> // assert 5 times that the first pause pod can connect to the Service locally and the second one errors with a timeout <del> serviceAddress := net.JoinHostPort(svc.Spec.ClusterIP, strconv.Itoa(servicePort)) </del> for i := 0; i < 5; i++ { // the first pause pod should be on the same node as the webserver, so it can connect to the local pod using clusterIP // note that the expected hostname is the node name because the backend pod is on host network <del> execHostnameTest(*pausePod0, serviceAddress, node0.Name) </del> <ins> execHostnameTest(*pausePod2, serviceAddress, node0.Name) </ins> // the second pause pod is on a different node, so it should see a connection error every time cmd := fmt.Sprintf(`curl -q -s --connect-timeout 5 %s/hostname`, serviceAddress) <del> _, err := framework.RunHostCmd(pausePod1.Namespace, pausePod1.Name, cmd) </del> <ins> _, err := framework.RunHostCmd(pausePod3.Namespace, pausePod3.Name, cmd) </ins> framework.ExpectError(err, \"expected error when trying to connect to cluster IP\") } })", "positive_passages": [{"docid": "doc-en-kubernetes-06e17cf980b6b4fe370857f0b2e0687536ee3b3b60ed1f78548a694def2f21f6", "text": "Failed here /retest Originally posted by in This fails because the pod tries to bind port 80, that is a very demanded port, but there are two tests doing that, that increase the chance to collide\n/sig network\nClose when merges\n/triage accepted", "commid": "kubernetes_issue_104406", "tokennum": 54}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9b4c29c45f4004a82db84e5085406c7cb24f7c11e7af6ad0cf0bfaa0286f0111", "query": "Message:            \"currentMessage\", }, currentNominatedNodeName: \"node1\", <del> expectedPatchRequests:    1, </del> <ins> expectedPatchRequests:    0, </ins> }, { name: \"Should make patch request if pod condition already exists and is identical but nominated node name is set and different\",", "positive_passages": [{"docid": "doc-en-kubernetes-0c3eca7956c73a24f455c71a58b712ce183e874d4a3e3eb9b913120c8a8ac10c", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: Conformance - GCE - master (ci-kubernetes-gce-conformance-latest) Which test(s) are failing: [sig-scheduling] SchedulerPreemption [Serial] PreemptionExecutionPath runs ReplicaSets to verify preemption running path [Conformance]Changes Since when has it been failing: 2020-06-08 22:27 PDT Testgrid link: Reason for failure: Regression by Anything else we need to know: /sig scheduling /priority critical-urgent\ncc/ /assign", "commid": "kubernetes_issue_91972", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9b7222491dcdc7d0d627302146a3c6eee75341261abecd22390bb3eb43836b84", "query": "continue } <del> By(fmt.Sprintf(\"Successfully fetched pod logs:%vn\", string(logs))) </del> <ins> By(fmt.Sprintf(\"Successfully fetched pod logs:%vn\", logs)) </ins> break } for _, m := range expectedOutput { <del> Expect(string(logs)).To(matcher(m), \"%q in container output\", m) </del> <ins> Expect(logs).To(matcher(m), \"%q in container output\", m) </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-cf37b0ab7a08d0e2457507bc271b1cb7d1e13fbaee3773971363bc32ae71b35b", "text": "We are running heapster, dns server, kube-proxy etc. in kube-system namespace. Some e2e tests try to make sure all those kube-system pods are at ready state before firing the real tests, others just simply ingore them. But both cases might cause e2e flakiness when some of those kube-system containers are in crashloop, for example, for heapster crashloop, for influxdb crashloop, etc. When such cases happen, the developer doesn't have much information on why since the nodes might be teared down. We should watch those kube-system pods, and onContainerFailure, we should collect the related logs. One simple way is using kubectl logs <Pod<Container--previous cc/\nis this related enough to and that you can bundle it in?\nThe logs from the pods should be retrieved via the api server. This is different from the kubelet logs. I'll upload a PR for this.\nGreat job It will be very helpful for debugging.", "commid": "kubernetes_issue_20099", "tokennum": 229}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9b92b4673470b62a9de042e85d9815453d3958733bb52d786c58acb922d917f1", "query": "func TestPriorityQueue_MoveAllToActiveQueue(t *testing.T) { q := NewPriorityQueue(nil) q.Add(&medPriorityPod) <del> q.unschedulableQ.addOrUpdate(&unschedulablePod) q.unschedulableQ.addOrUpdate(&highPriorityPod) </del> <ins> addOrUpdateUnschedulablePod(q, &unschedulablePod) addOrUpdateUnschedulablePod(q, &highPriorityPod) </ins> q.MoveAllToActiveQueue() if q.activeQ.Len() != 3 { t.Error(\"Expected all items to be in activeQ.\")", "positive_passages": [{"docid": "doc-en-kubernetes-e059cd0647305d70a174ce6bffb9584a993a023526be428075760ddef27cc3b0", "text": "Which jobs are failing: pull-kubernetes-bazel-test Which test(s) are failing: bazel test //pkg/scheduler/internal/queue:godefaulttest Since when has it been failing: Testgrid link: Reason for failure: WARNING: DATA RACE Read at 0x00c000230db0 by goroutine 47: runtime.mapiterinit() +0x0 (PriorityQueue).flushUnschedulableQLeftover() +0x17a (PriorityQueue).flushUnschedulableQLeftover-fm() +0x41 () +0x61 () +0xce () +0x5a Previous write at 0x00c000230db0 by goroutine 45: runtime.mapassignfaststr() +0x0 (UnschedulablePodsMap).addOrUpdate() +0x30e () +0x601 testing.tRunner() +0x162 Goroutine 47 (running) created at: (PriorityQueue).run() +0x172 () +0xe0b () +0x50 () +0x5a5 testing.tRunner() +0x162 Goroutine 45 (running) created at: testing.(T).Run() +0x659 testing.runTests.func1() +0xa8 testing.tRunner() +0x162 testing.runTests() +0x4ee testing.(M).Run() +0x2ee () bazel-out/k8- +0x2fb Anything else we need to know: I'm very sorry about that. UnschedulablePodsMap is not thread-safe. In , lock will be acquired before operating UnschedulablePodsMap. But in , lock isn\u2018t be acquired. In the previous case, only a single thread runs so it's ok. But after add goroutine , there will be data race. So I need to acquire lock before operating UnschedulablePodsMap.\n/sig testing /sig scheduling", "commid": "kubernetes_issue_73021", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9bb0f66cb6907ae8ec820c8cc974880df8d22c641894f68bed4b479de40945e0", "query": "// created before this test, and may not be infra // containers. They should be excluded from the test. existingPausePIDs, err := getPidsForProcess(\"pause\", \"\") <del> gomega.Expect(err).To(gomega.BeNil(), \"failed to list all pause processes on the node\") </del> <ins> framework.ExpectNoError(err, \"failed to list all pause processes on the node\") </ins> existingPausePIDSet := sets.NewInt(existingPausePIDs...) podClient := f.PodClient()", "positive_passages": [{"docid": "doc-en-kubernetes-4d7af6d1d5d1ba0c7ab59da9ea13925b54c282d46d48402ebb3f5409fd2b1204", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: kubernetes/node-problem-detector/node-problem-detector-ci: ci-npd-e2e-node See the Which test(s) are failing: [] NodeProblemDetector [NodeFeature:NodeProblemDetector] [] SystemLogMonitor should generate node condition and events for corresponding errors Since when has it been failing: Dec 03. was at 19:50 PST, was at 21:51 PST. Testgrid link: https://k8s- Reason for failure: Apparently is the culprit. Anything else we need to know: This is likely caused by some library upgrade. Nothing big.\n/sig node\n/assign\nSeems like the failure is caused by . /cc /cc /cc /cc\n/priority critical-urgent\nThe particular bug I care about has been fixed in . I'm gonna still work on submitting , as the same error should also be affecting a few other tests.", "commid": "kubernetes_issue_85933", "tokennum": 235}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9bee74aa741376fd4ddaf2a203c930fac02a04bd7b35543ee6ec1e7cd26886ae", "query": "It(\"deployment should create new pods\", func() { testNewDeployment(f) }) <del> It(\"deployment should delete old pods and create new ones [Flaky]\", func() { </del> <ins> It(\"RollingUpdateDeployment should delete old pods and create new ones [Flaky]\", func() { </ins> testRollingUpdateDeployment(f) }) <del> It(\"deployment should scale up and down in the right order [Flaky]\", func() { </del> <ins> It(\"RollingUpdateDeployment should scale up and down in the right order [Flaky]\", func() { </ins> testRollingUpdateDeploymentEvents(f) }) <ins> It(\"RecreateDeployment should delete old pods and create new ones [Flaky]\", func() { testRecreateDeployment(f) }) </ins> It(\"deployment should support rollover [Flaky]\", func() { testRolloverDeployment(f) })", "positive_passages": [{"docid": "doc-en-kubernetes-ceb20554e653f6657baad1bbb36c40e66d8a76887956e3c674b77febc82d4455", "text": "There's some practical limit on the number of concurrent access tokens that can be used in a Kubernetes cluster before it begins to spend all of its time in the authn stack verifying them. Absent fixes to it was < 500; with the fixes linked there it's still not infinitely scalable-- I still hit (what I believe to be) with ~ 5k unique tokens @ ~700QPS. This request is to this dimension an official name & definition, and list it with others, e.g. here: it it have a useful value (I think it should be 10k) /kind bug /sig scalability\n/cc\noh and 4. add tests which verify it is as high as believed.\ncc since projected tokens will increase the number of unique tokens\n/sig auth\nLRUs are not good at scaling and sharding has some major pitfalls as pointed out. I would suggest that we try to drop the LRU cache for successful authentication results in the token cache. The main benefit of using an LRU here is bound cache size. Entries in the token cache have a fast expiration independent of the LRU policy. The records probably take up O(2kb) (guesstimate) of memory. Given that these are successful attempts with presumably valid tokens, I don't think we are getting any benefit from the LRU. If we don't have a constraint on fixed cache size, we can back the token cache with a sync.Map and run a single background goroutine to periodically walk the map and remove expired entries. This would fix the problematic locking and eviction due to nonuniform distribution of tokens over shards. The failure cache is less important and we don't cache failures by default. If we consider this the \"slowpath\", we can probably leave it as. If that's not good enough, we have a couple options (with various tradeoffs) to improve it.\nIf off by default is not enough, more reasoning why the failed cache is not super useful: it might help with an accidental DoS but it doesn't prevent anything actively malicious DoS. I think we can focus our improvements on the success cache.\n/assign He is already working on adding an explicit test for it.\nhas taken it over and is actively working on this. Unfortunately, I cannot assign this issue to him as he's not a k8s member yet\nIt's not closed - all testes must be submitted and appropriate documentation must be\nThanks everyone!!", "commid": "kubernetes_issue_83375", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9c1ccba6552e49dcef76df7e9c12a57ada18d9e990b88b37b31b35218ace1a6b", "query": "echo \"Detecting nodes in the cluster\" detect-node-names &> /dev/null <del> if [[ \"${#NODE_NAMES[@]}\" == 0 ]]; then </del> <ins> if [[ -z \"${NODE_NAMES:-}\" ]]; then </ins> echo \"No nodes found!\" return fi", "positive_passages": [{"docid": "doc-en-kubernetes-764cede5d9efbc9aa0896bda8776a6a1986b2e142264cb7af9fd4363856aed51", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: In https://k8s- failed due to . Afterwards crashed as follows: What you expected to happen: Graceful exit.\n/assign", "commid": "kubernetes_issue_55675", "tokennum": 45}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9c4edf00366ff424623bbd4fccda612ecda83299e99d199e00886c331808a7bd", "query": "// ClusterLevelLoggingWithElasticsearch is an end to end test for cluster level logging. func ClusterLevelLoggingWithElasticsearch(c *client.Client) { // TODO: For now assume we are only testing cluster logging with Elasticsearch // on GCE. Once we are sure that Elasticsearch cluster level logging // works for other providers we should widen this scope of this test. <del> if testContext.Provider != \"gce\" { </del> <ins> if !providerIs(\"gce\") { </ins> Logf(\"Skipping cluster level logging test for provider %s\", testContext.Provider) return }", "positive_passages": [{"docid": "doc-en-kubernetes-5702d542be386cac9e4333778515fd94620fcdb52c66d8dfc11487da78971dda", "text": "I noticed while running e2e tests locally that some tests were apparently being incorrectly skipped: I checked, and this is also true for our Jenkins runs. Currently it looks like and have this bug, though only the former actually skips the test, I think. The issue appears to be that the code inside the top-level in these files is being run before the testContext struct is filled out (and before is even called), and so testContext.Provider is empty. I'm not immediately sure what the proper fix is; I'm also worried that there might be other things broken by the fact that these blocks are called before initialization is complete. We also probably investigate if there is a better way to mark these tests as skipped; right now, there's no indication in the test report (, Jenkins test report, etc) that these tests were skipped.\nI merged and which tried to disable these tests for non-{gke,gce} but apparently didn't follow-up and verify that they were still running on our platforms. /cc\nSeems easy enough to fix. I'll have a PR out to fix this before Monday.", "commid": "kubernetes_issue_7008", "tokennum": 242}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9c66f978c09a6a01a1dc6145b60d7d603b912d1dd7bcf53de96f2ccffad8151e", "query": "assert.Len(t, client.Actions(), 0) } <ins> // Ensure SyncService for service with pending deletion results in no action func TestSyncServicePendingDeletion(t *testing.T) { ns := metav1.NamespaceDefault serviceName := \"testing-1\" deletionTimestamp := metav1.Now() client, esController := newController([]string{\"node-1\"}, time.Duration(0)) esController.serviceStore.Add(&v1.Service{ ObjectMeta: metav1.ObjectMeta{Name: serviceName, Namespace: ns, DeletionTimestamp: &deletionTimestamp}, Spec: v1.ServiceSpec{ Selector: map[string]string{\"foo\": \"bar\"}, Ports:    []v1.ServicePort{{TargetPort: intstr.FromInt(80)}}, }, }) err := esController.syncService(fmt.Sprintf(\"%s/%s\", ns, serviceName)) assert.Nil(t, err) assert.Len(t, client.Actions(), 0) } </ins> // Ensure SyncService for service with selector but no pods results in placeholder EndpointSlice func TestSyncServiceWithSelector(t *testing.T) { ns := metav1.NamespaceDefault", "positive_passages": [{"docid": "doc-en-kubernetes-b47abd0a7beb2bc1a841f65e5737673c1fa7ed1c22ab52e8ed01b146c2722dfe", "text": "What happened: In the PMEM-CSI CI, we rapidly deploy and remove a custom resources which then owns all objects created for that resource. Deletion of those objects is handled through ownership references, i.e. deleting the CR is expected to cascade to all objects. This worked fine up to Kubernetes 1.17. When starting to test with 1.18.2, we pretty reliably get into a state where the CR and the service objects owned by it are marked for deletion, but don't go away. Debugging with the garbage collector's dependency graph (see ) showed that endpointslices were blocking the deletion of the services and thus the CR. In the graph dump (= a snaphot in time), they were not even marked for deletion. A closer look showed that endpointslices for the services were getting created and deleted continuously for over 15 minutes. Eventually, the garbage collector won and managed to delete endpointslices and services before new endpointslices were created. What you expected to happen: There seems to be a missing check in if the service is marked for deletion (i.e. has a deletionTimestamp), then the controller should not create new endpointslices. How to reproduce it (as minimally and precisely as possible): I tried to boil it down to a script, but it just ran fine. The \"easiest\" way to reproduce it is to run PMEM-CSI's E2E testing, which is probably not easy enough :disappointed: Anything else we need to know?: Disabling the EndpointSlice feature makes the problem go away. Environment: Kubernetes version (use ): 1.18.2 Cloud provider or hardware configuration: QEMU virtual machines OS (e.g: ): Fedora Install tools: kubeadm /sig network\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\ncc for endpointslice\nThanks for the detailed bug report! Will work on getting a fix in soon. /assign\n/remove-triage unresolved\nCan you describe the general process to reproduce this bug? Would it involve hundreds of EndpointSlices for a Service? I've tried to recreate this in a , but unfortunately I haven't been able to get anything to break. Any ideas for what I could try?\nThere's one endpointslice per service. Our operator creates two services.", "commid": "kubernetes_issue_91287", "tokennum": 525}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9c66f978c09a6a01a1dc6145b60d7d603b912d1dd7bcf53de96f2ccffad8151e", "query": "assert.Len(t, client.Actions(), 0) } <ins> // Ensure SyncService for service with pending deletion results in no action func TestSyncServicePendingDeletion(t *testing.T) { ns := metav1.NamespaceDefault serviceName := \"testing-1\" deletionTimestamp := metav1.Now() client, esController := newController([]string{\"node-1\"}, time.Duration(0)) esController.serviceStore.Add(&v1.Service{ ObjectMeta: metav1.ObjectMeta{Name: serviceName, Namespace: ns, DeletionTimestamp: &deletionTimestamp}, Spec: v1.ServiceSpec{ Selector: map[string]string{\"foo\": \"bar\"}, Ports:    []v1.ServicePort{{TargetPort: intstr.FromInt(80)}}, }, }) err := esController.syncService(fmt.Sprintf(\"%s/%s\", ns, serviceName)) assert.Nil(t, err) assert.Len(t, client.Actions(), 0) } </ins> // Ensure SyncService for service with selector but no pods results in placeholder EndpointSlice func TestSyncServiceWithSelector(t *testing.T) { ns := metav1.NamespaceDefault", "positive_passages": [{"docid": "doc-en-kubernetes-884db7f4f09e6e30f5114a0e6bbb9ebc21f2d686aa6c190d6a4d9470af013127", "text": "One peculiarity may be that we don't actually want the pods to start during these tests because we only want to verify object creation, not the usage of the result, and therefore all pods reference non-existent images. All objects immediately get deleted once the test has verified that they exist, so the timing is probably very different from \"normal\" usage patterns. I suspect that it is more important to create and delete services quickly than it is to have many endpointslices per service.\nI had tried to come up with a script that triggers the problem, without success. That was before I realized that endpointslices are involved. On Monday I can have another look.\nThat was because I thought that (the default) enables foreground deletion. It doesn't, and there's also no option to select it. After explicitly selecting it via curl, the following script failed for me eventually: Output: Note that for the endpointslice is greater than the of its service.", "commid": "kubernetes_issue_91287", "tokennum": 201}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9cb109f42c4a0061468becdd099d4383525e1f23b98ba763b731d082a8510ba2", "query": "ginkgo.By(\"Expanding non-expandable pvc\") newSize := resource.MustParse(\"6Gi\") pvc, err = expandPVCSize(pvc, newSize, c) <del> gomega.Expect(err).To(gomega.HaveOccurred(), \"While updating non-expandable PVC\") </del> <ins> framework.ExpectError(err, \"While updating non-expandable PVC\") </ins> }) ginkgo.It(\"Verify if editing PVC allows resize\", func() {", "positive_passages": [{"docid": "doc-en-kubernetes-c082543f1889f90c5ee780d309eeb8f41ee57a7e9e8bb6b6fe7c2e4381ff48af", "text": "What happened: After fixing golint failures under (now still in progress), we need to put for each and . Then common error checking code has become like: We can replace this code with which is more readable and easy to be understood what the code does. Now we have following e2e test directories which can be replaced: [x] test/e2e/apimachinery/ () [x] test/e2e/apps/ () [x] test/e2e/auth/ () [x] test/e2e/common/ () [x] test/e2e/node/ () [x] test/e2e/storage/ () [x] () [x] () [x] () [x] () [x] () [x] () [x] [x] test/e2e/storage/persistentvolumes- [x] () [x] () [x] [x] [x] [x] [x] ()\n/sig testing /kind cleanup\n/assign PR will be submitted soon.\nFix the following in\nFix in\nFix in\nHi, maybe I could take files beneath test/e2e/storage/vsphere/\noops, I'm finished and prepare for PR.\nThank you That's OK\nFix the following in\n/assign\nAll related PRs were merged. I think this ticket can be closed. BTW, should we also replace to ?\nThanks for your work. thing is managed with We are almost finishing the work also :-)\n/remove-kind bug\nI found in these files. I'm working on :\nI can work to the following item.", "commid": "kubernetes_issue_77706", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9cb3bd98229bc4c6725b8a75dc135965b17c5674b103bd331e4f316a1ed95479", "query": "test/e2e/common/secrets_volume.go: \"should be able to mount in a volume regardless of a different secret existing with same name in different namespace\" test/e2e/common/secrets_volume.go: \"should be consumable in multiple volumes in a pod\" test/e2e/common/secrets_volume.go: \"optional updates should be reflected in volume\" <ins> test/e2e/common/security_context.go: \"should run the container with uid 65534\" test/e2e/common/security_context.go: \"should run the container with writable rootfs when readOnlyRootFilesystem=false\" test/e2e/common/security_context.go: \"should run the container as unprivileged when false\" test/e2e/common/security_context.go: \"should not allow privilege escalation when false\" </ins> test/e2e/kubectl/kubectl.go: \"should create and stop a replication controller\" test/e2e/kubectl/kubectl.go: \"should scale a replication controller\" test/e2e/kubectl/kubectl.go: \"should do a rolling update of a replication controller\"", "positive_passages": [{"docid": "doc-en-kubernetes-f8a45a347ca0a58053d8639059bb6be0a8ec66e1196dbd0290c02922abc9dcd2", "text": "/kind cleanup /area conformance /area test /sig node /sig testing /sig architecture /assign /assign We have a number of tests that only have the tag that may make sense as tests, we should identify whether these tests cases meet (or could meet) the . We should open PR's to promote these if so. I would advise starting with the test/common cases\nGitHub didn't allow me to assign the following users: mgdevstack, mkurylec. Note that only and repo collaborators can be assigned. For more information please see <detailsIn response to : /kind cleanup /area conformance /area test /sig node /sig testing /sig architecture /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\n/assign\nThe tests in test/e2enode don't actually get run as part of Conformance as near as I can tell. If we want to run them as part of conformance, they need to be migrated into test/e2e/common. Some of the tests in e2enode may not be able to be ported over because they assume a level access we don't have in a conformance environment.\nregarding this testcase: [sig-storage] HostPath should support r/w [NodeConformance]: It uses hostPath and privileged=true, to read/write from /tmp folder. Which would you suggest is the best orientation to overcome the privilege mode setting and allow its promotion?\n/assign\nRegarding , the suite runs the test only if the kubelet configuration was required to have the QOS (cgroups-per-qos) enabled. This configuration for the kubelet is selected at the time the cluster is set up. Looking for where this might be configured found: where is set to true. For other settings it is also configured to true. where is set to true. BUT also found where it is mentioned that the flag is no longer available. Questions: would it be ok to promote this test to be conformance, even it can be skipped based on configuration of the cluster? And not supported in the containerized kubelet?\nI would consider cgroups to be an implementation detail that Conformance shouldn't be verifying\nIt uses hostPath and privileged=true, to read/write from /tmp folder.", "commid": "kubernetes_issue_66875", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9cb3bd98229bc4c6725b8a75dc135965b17c5674b103bd331e4f316a1ed95479", "query": "test/e2e/common/secrets_volume.go: \"should be able to mount in a volume regardless of a different secret existing with same name in different namespace\" test/e2e/common/secrets_volume.go: \"should be consumable in multiple volumes in a pod\" test/e2e/common/secrets_volume.go: \"optional updates should be reflected in volume\" <ins> test/e2e/common/security_context.go: \"should run the container with uid 65534\" test/e2e/common/security_context.go: \"should run the container with writable rootfs when readOnlyRootFilesystem=false\" test/e2e/common/security_context.go: \"should run the container as unprivileged when false\" test/e2e/common/security_context.go: \"should not allow privilege escalation when false\" </ins> test/e2e/kubectl/kubectl.go: \"should create and stop a replication controller\" test/e2e/kubectl/kubectl.go: \"should scale a replication controller\" test/e2e/kubectl/kubectl.go: \"should do a rolling update of a replication controller\"", "positive_passages": [{"docid": "doc-en-kubernetes-b0f7522fd47a7c9f3d30009b5f18d7b37ba2aa8723a4c0ef112b90078054f0fc", "text": "Which would you suggest is the best orientation to overcome the privilege mode setting and allow its promotion? Michelle Au If my understanding is correct, on some platforms, writing to /tmp requires privileged. I don't see a way to to remove that requirement.\nIf my understanding is correct, on some platforms, writing to /tmp requires privileged. I don't see a way to to remove that requirement. Yeah writing to host doesn't seem like a thing we can expect of conformance tests. I wonder if it makes sense to tag this test with something to denote the requirement, ie: I see some tests in test/e2e_node use\nThe hostpath tests in already have a comment explaining this. Maybe the comment should be updated to be more clear that that is the reason why we can't add it to conformance.\nThat's /tmp on the host or in the container filesystem?\n/tmp on the host\nping what else remains to be done before we close this out? I am guessing that we want to close , is there anything beyond that?\nOnce tests under (issue- ) and are promoted we are good to close this issue. Short update for reference- None of [NodeConformance] tests from \"test/e2e_node\" seems eligible for [Conformance] promotion at this moment due to node level dependencies. Remaining [NodeConformance] tests from \"test/e2e\" has following status - Waiting for to be closed and then below tests would be promoted to Conformance Needs to be Promoted Can not be promoted to Conformance as //Slow by design Can not be promoted due to Node level dependency\nIssues 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\n/remove-lifecycle stale\n/lifecycle frozen\n/assign", "commid": "kubernetes_issue_66875", "tokennum": 428}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9ce1e1e9fefca58331188ffbf1da46ff5f09b8140023284a6e5ce966f936d22e", "query": "testCases := []struct { name       string modifyRest func(rest *REST) <ins> oldSvc     *api.Service </ins> svc        api.Service expectedIPFamilyPolicy *api.IPFamilyPolicyType", "positive_passages": [{"docid": "doc-en-kubernetes-572d0164a11730b1ec949ed970afee14cdb12823b4b7a698fae66a86d82f748e", "text": "1) start with a single stack cluster 2) create a PreferDualStack service 3) configure API server with a 2nd service CIDR 4) Confirm the above service is not dual-stack 5) Add a label to the above service 6) Observe that the service becomes dual-stack I think the correct answer is to have a \"repair loop\" that upgrades (and downgrades!) PreferDualStack Services to match the config. I think this is a GA blocker.\n/triage accepted The current thought is: of type with are special new breed of api objects that I don't think we have any similar precedent in the apis, i could be wrong. Their behavior is tied to how the cluster is configured. Thus their behavior must change as the cluster behavior change. a way the user is stating . If it is cluster then i am good with two ClusterIPs. If it is single stack cluster then I am also good with a single ClusterIP. One can assume that if the user was ok was with getting a additional IP when possible then they must be ok with taking it away when it is no longer possible. Based on the above I believe best course of action is create a new repair loop or piggyback on any of the existing (or better: fix it in rest stack during list and get calls). The new logic takes care of matching to the .\nreproducer and regression test if somebody takes this, feel free to add it\nack - Scheduled to tackle 3rd week of May. Will definitely include that patch.", "commid": "kubernetes_issue_101681", "tokennum": 322}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9ce6d39f210c1071a80a91f537ccf7e861330a59a98cdb1499fcbe3611f67caa", "query": "func (f *ConfigFactory) CreateFromKeys(predicateKeys, priorityKeys sets.String, extenders []algorithm.SchedulerExtender) (*scheduler.Config, error) { glog.V(2).Infof(\"Creating scheduler with fit predicates '%v' and priority functions '%v\", predicateKeys, priorityKeys) <del> if f.GetHardPodAffinitySymmetricWeight() < 0 || f.GetHardPodAffinitySymmetricWeight() > 100 { return nil, fmt.Errorf(\"invalid hardPodAffinitySymmetricWeight: %d, must be in the range 0-100\", f.GetHardPodAffinitySymmetricWeight()) </del> <ins> if f.GetHardPodAffinitySymmetricWeight() < 1 || f.GetHardPodAffinitySymmetricWeight() > 100 { return nil, fmt.Errorf(\"invalid hardPodAffinitySymmetricWeight: %d, must be in the range 1-100\", f.GetHardPodAffinitySymmetricWeight()) </ins> } predicateFuncs, err := f.GetPredicates(predicateKeys)", "positive_passages": [{"docid": "doc-en-kubernetes-88466bc637a805045217da94feabbdbd3df0ba52cd0d9904e95d3984c4cf4efa", "text": "( noticed this) HardPodAffinitySymmetricWeight should be in the , not in KubeSchedulerConfiguration If/when fixing this, we need to be careful to do it in a backward-compatilble way.\nDo you mean ? It seems scheduler policy config's args can not passed to FitPredicates; it need to update related interface. For the : mark to be deprecated and set scheduler policy config to HardPodAffinitySymmetricWeight if policy config is empty.\nAre you working on this? if no, I can take it.\n, nop; please go ahead.\n/ / / , When reviewing the PR, there's one question on : the default value of is 1, which means the weight (1) will always add to priorities if term matched (), does it our expectation? And the user has to set it to 0 to disable it. IMO, the default value of should be 0.\nThe value 1 (instead of 0) was chosen so that if you say A must run with B, there is an automatic preference that B should run with A. This seems like reasonable behavior.\nThanks very much; reasonable case to me. But it seems we can not disable it: if set to 0, the default funcs will set it to default (1); similar result to un-set. Anyway, no user complain this now :).", "commid": "kubernetes_issue_43845", "tokennum": 306}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9d028013d3a202390a977e79d1f017f5eb4031ffba14609b5f4ee0b0d3c22238", "query": "return nil, err } <del> res := metricObj.(*v1beta2.MetricValueList) </del> <ins> var res *v1beta2.MetricValueList var ok bool if res, ok = metricObj.(*v1beta2.MetricValueList); !ok { return nil, fmt.Errorf(\"the custom metrics API server didn't return MetricValueList, the type is %v\", reflect.TypeOf(metricObj)) } </ins> if len(res.Items) != 1 { return nil, fmt.Errorf(\"the custom metrics API server returned %v results when we asked for exactly one\", len(res.Items)) }", "positive_passages": [{"docid": "doc-en-kubernetes-c04a0817a9f8c0cfea921bee7f0710f81a15653683e102754b69999644e85b55", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: What you expected to happen: kube-controller-manager should not panic. How to reproduce it (as minimally and precisely as possible): Kubernetes 1.12.6, , and Anything else we need to know?: It's running and , and logs says: Don't see any notable errors in . Is that because it's running the old ? Basically, is expecting , but somehow it's getting which I assume Environment: Kubernetes version (use ): v1.12.6 Cloud provider or hardware configuration: AWS EC2 OS (e.g: ): Amazon Linux 2 Kernel (e.g. ): 4.14.109-99.92.amzn2.x86_64\nCould be related to , but this happens with all the patches from the issue /sig scalability /cc\n/sig autoscaling /assign can you triage please?\n/sig-remove scalabilty\n/sig remove scalability\n/sig scalability remove\n/remove-sig scalability\nAPI returned v1.Status instead of v1beta2.MetricValueList. We should check what is the type of the object\n/sig instrumention\n/assign\n/sig instrumentation\nseems promising. Is it missing anything?\nI've root-caused the issue. Explained here -\nYep, should address the issue.", "commid": "kubernetes_issue_80390", "tokennum": 343}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9d3c34e0541c971177c0fcc2a535ef9a770b08e32a7315a6dfa420b62347aa38", "query": "return svc } <ins> func getResourceGroupTestService(identifier, resourceGroup, loadBalancerIP string, requestedPorts ...int32) v1.Service { svc := getTestService(identifier, v1.ProtocolTCP, requestedPorts...) svc.Spec.LoadBalancerIP = loadBalancerIP svc.Annotations[ServiceAnnotationLoadBalancerResourceGroup] = resourceGroup return svc } </ins> func setLoadBalancerModeAnnotation(service *v1.Service, lbMode string) { service.Annotations[ServiceAnnotationLoadBalancerMode] = lbMode }", "positive_passages": [{"docid": "doc-en-kubernetes-4ac48b480971aca26f0a1896d0fa1bdd3b9ed6e78abeeb1cea4ee05f140cc101", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: controller-manager is stuck in deleting an incorrectly configured LB type service. it cannot be recovered until restarted. What you expected to happen: controller-manager should recover. At least it should allow us to create the service without restarting it. How to reproduce it (as minimally and precisely as possible): put a random IP in above yaml and make sure the resource group doen't exist. Anything else we need to know?: Environment: Kubernetes version (use ): 1.12.4 Cloud provider or hardware configuration: AKS OS (e.g: ): Kernel (e.g. ): Install tools: Others:\n/sig azure\nI also want to add that the above repro is stuck in 403. It's possible for it to be stuck in 404 as well when the SP has the right permission.\nCan you share the log for 404?\nThanks for reporting the issue. /assign Do you mean other services couldn't be configured when this happens?\ncorrect.\nFYI, we had the same issue when the Idle Timeout annotation was set to \"3\" which isn't a supported case. Will this PR also cover this edge case ?\nUnfortunately , this is still not fixed. The idle timeout is not 403 or 404. We need another fix for this (and possibly more for other annotations)", "commid": "kubernetes_issue_75198", "tokennum": 337}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9d730cd43a86d1d194c08a666b7c4ea237baff9e736083247c4b512d4bfaccff", "query": "LOGGING_DESTINATION=elasticsearch # options: elasticsearch, gcp ENABLE_CLUSTER_MONITORING=false <ins> # Don't require https for registries in our local RFC1918 network EXTRA_DOCKER_OPTS=\"--insecure-registry 10.0.0.0/8\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-142e8decd8d12f564814b0a08026ec0c2500ddcd8040f0182edc6a7f51b222f8", "text": "0/8 is with a company's intranet, so it can be insecure. This is similiar to \"For GCE, allow insecure registries anywhere in 10.0.0.0/8\" Thanks!\nLinking to and .\nThis was", "commid": "kubernetes_issue_2807", "tokennum": 55}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9d82ed537d27da371d710b4ba6862bdafe6e2ce81470b171c93acb8ec346c85d", "query": "\"k8s.io/client-go/tools/leaderelection\" cliflag \"k8s.io/component-base/cli/flag\" \"k8s.io/component-base/cli/globalflag\" <ins> \"k8s.io/component-base/logs\" </ins> \"k8s.io/component-base/metrics/legacyregistry\" \"k8s.io/component-base/version\" \"k8s.io/component-base/version/verflag\"", "positive_passages": [{"docid": "doc-en-kubernetes-1ae4374d89f67ace7ae0a669d00ed1569d20a542da5564faf73570670010978e", "text": "What would you like to be : Support dynamically set log level for kube-scheduler, is blocked on node controller approval, but we can move forward with a scheduler only change. /sig scheduling\n/help\n/assign /remove-help\ndo you have a PR for this one?\nI submitted the PR.", "commid": "kubernetes_issue_83783", "tokennum": 65}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9d84761c0064dfb227ad9c7954dc8de4c28dac9b9e65511f8043ce07ca9e36bd", "query": "} else { klog.V(4).InfoS(\"Added volume to desired state\", \"pod\", klog.KObj(pod), \"volumeName\", podVolume.Name, \"volumeSpecName\", volumeSpec.Name()) } <ins> // sync reconstructed volume dswp.actualStateOfWorld.SyncReconstructedVolume(uniqueVolumeName, uniquePodName, podVolume.Name) </ins> if expandInUsePV { dswp.checkVolumeFSResize(pod, podVolume, pvc, volumeSpec,", "positive_passages": [{"docid": "doc-en-kubernetes-95820dc44dfb57216fa4466fe0b08e35d101b3576d175fcc0793312a1c18dfad", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --We have even encountered such case that pod continuously reports \u201cUnable to attach or mount volumes for pod;...\u201d when kubelet restarted. The reasons are listed in details as below: , as result of apiserver instantaneous unstablility, dswp get pvc\u2018s pv spec failed, then the pvc volume does not be to dsw. , syncStates() lists all the volume directories locally, and recontructs the volume from local volume, if the volume isn't in dsw, it will put the recontructed volume to asw, but now the volume.OuterVolumeSpecName isn't correct. chance, at this time, In , the fail to pvc volume is to dsw again normally in reconcile() -mountAttachVolumes(), it compares dsw and asw by volume's innerVolumename, it's all the same. but it could not sense the OuterVolumeSpecName dismatch. so it will not re-mount again to update asw cache , it checks pod's volume attach or mount success by comparing volume.OuterVolumeSpecName and , but this pv'c OuterVolumeSpecName isn't correct in asw. so pod continuously reports \u201cUnable to attach or mount volumes for pod;...\u201d reconcile() could sense the reconstruct volume's dismatch to the dsw, then re-mount again to make volume cache consistency Kubernetes version (use ): 1.19.4 Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig node\n/triage accepted\n/assign\nCC\nI think this is a point that can be optimized. /cc\nI will give a fix for this\nThanks for reporting the issue, this innerSpecName and outerSpecName are confusing and cause issues. Please ping me for review when you have a fix. Thanks!\nPlease don't triage your own issues immediately, give someone else a chance to review them :( /sig storage\nokay, I know", "commid": "kubernetes_issue_103143", "tokennum": 528}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9da647ad38eea54dc2b00dc99f1ca395efd65e9d3687d4791c8eb5ee077daa47", "query": "// Otherwise we should delete the victim. if waitingPod := fh.GetWaitingPod(victim.UID); waitingPod != nil { waitingPod.Reject(pluginName, \"preempted\") <ins> klog.V(2).InfoS(\"Preemptor pod rejected a waiting pod\", \"preemptor\", klog.KObj(pod), \"waitingPod\", klog.KObj(victim), \"node\", c.Name()) </ins> } else { if feature.DefaultFeatureGate.Enabled(features.PodDisruptionConditions) { victimPodApply := corev1apply.Pod(victim.Name, victim.Namespace).WithStatus(corev1apply.PodStatus())", "positive_passages": [{"docid": "doc-en-kubernetes-8b547b0918354692a878225113bae9a07e658398c400349efcb40fc715b52424", "text": "A V(2) log line that includes preemption details (preemptee and preemptor), somewhere here We used to have most of this information as part of the logging for Events. But we removed the preemptor from it as a security measure Logs can have pod names.\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scheduling\n/help\nThis 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 : /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\n/assign\n/help-remove", "commid": "kubernetes_issue_117210", "tokennum": 334}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9dbeb28184259505efc7b93aacf2ca55fddccbdf35239e1bf605e61c73364635", "query": "} const ( <ins> testPodSpecFile = `{ \"kind\": \"Pod\", \"apiVersion\": \"v1beta3\", \"metadata\": { \"name\": \"container-vm-guestbook-pod-spec\" }, \"spec\": { \"containers\": [ { \"name\": \"redis\", \"image\": \"dockerfile/redis\", \"volumeMounts\": [{ \"name\": \"redis-data\", \"mountPath\": \"/data\" }] }, { \"name\": \"guestbook\", \"image\": \"google/guestbook-python-redis\", \"ports\": [{ \"name\": \"www\", \"hostPort\": 80, \"containerPort\": 80 }] }], \"volumes\": [{\t\"name\": \"redis-data\" }] } }` ) const ( </ins> // This is copied from, and should be kept in sync with: // https://raw.githubusercontent.com/GoogleCloudPlatform/container-vm-guestbook-redis-python/master/manifest.yaml // Note that kubelet complains about these containers not having a self link. testManifestFile = `version: v1beta2 <del> id: container-vm-guestbook </del> <ins> id: container-vm-guestbook-manifest </ins> containers: - name: redis image: dockerfile/redis", "positive_passages": [{"docid": "doc-en-kubernetes-56027fa26048aea64718f2bd7d7c5d6f58ddca1472c1fc738c03141b6dea3ad6", "text": "Currently it assumes it can read ContainerManifest - it should try both\nWhy not hold on this until we have Kubelet-read-Pod in?\nAlso the HTTP source has the same problem.\nIt should read Pod. Changed the title.\nIdeally, I'd like all Pods created directly via Kubelet to be to etcd and surfaced via the API. If updates are made via the API, I'd like those to propagate back to the node. We can discuss whether the config file should be updated or ignored. At some point, I'd like Kubelet to persistently cache pods received from the apiserver, perhaps by just writing them all out as config files.\nis the issue to sync local pods back to apiserver.\nthis is somewhat related to other issues we talked about.\nDetail: We want locally specified pods to be able to use YAML config files, but we also want to rip YAML out of the API server . The config-file behavior should be as similar to the kubectl experience. Kubelet could use parts of the kubectl library to translate YAML to JSON. Vision: Eventually, I'd like Kubelet to use the apiserver library and support exactly the same Pod API as the master, at which time I'd like kubectl be able to create pods directly on Kubelets, as well as reading from config files. I also expect to have a per-node controller . I'd like to be able to use the per-node controller to update pods started via config files (or direct kubectl-kubelet pods), overriding those original files. For availability and self-hosting, we'll eventually need local checkpointing , ideally just using serialized JSON for each object. If Kubelet used apiserver, this could be done using a custom registry implementation.\nI think that is a prerequisite for it.\nIf noone picks it up, I'm going to start working on it tomorrow.\nthanks, wojtek-t\nfixed it for http channel", "commid": "kubernetes_issue_3372", "tokennum": 445}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9ddef8812cad782f4c5e8137ed479959bc608d8f005148172df935e1d20d011d", "query": "/* Release : v1.23 Testname: Pod Lifecycle, poststart https hook <del> Description: When a post-start handler is specified in the container lifecycle using a 'HttpGet' action, then the handler MUST be invoked before the container is terminated. A server pod is created that will serve https requests, create a second pod with a container lifecycle specifying a post-start that invokes the server pod to validate that the post-start is executed. </del> <ins> Description: When a post-start handler is specified in the container lifecycle using a 'HttpGet' action, then the handler MUST be invoked before the container is terminated. A server pod is created that will serve https requests, create a second pod on the same node with a container lifecycle specifying a post-start that invokes the server pod to validate that the post-start is executed. </ins> */ ginkgo.It(\"should execute poststart https hook properly [MinimumKubeletVersion:1.23] [NodeConformance]\", func() { lifecycle := &v1.Lifecycle{", "positive_passages": [{"docid": "doc-en-kubernetes-52b8d78c627cb5787b11bea8197d2293333b64736fbbbb287954cc79911301a5", "text": "release-master-informing: capz-windows-containerd-masterKubernetes e2e suite: [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop https hook properly [MinimumKubeletVersion:1.23] [NodeConformance] Kubernetes e2e suite: [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart https hook properly [MinimumKubeletVersion:1.23] [NodeConformance] Both the tests have been failing during most of the runs since 20th October Kubernetes e2e suite: [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop https hook properly [MinimumKubeletVersion:1.23] [NodeConformance] | 1m6s -- | -- {Oct 31 18:42:02.425: Timed out after 30.001s. Expected <errors.errorString | 0xc0015283b0: { s: \"failed to match regexp \"GET /echo?msg=prestop\" in output \"I1031 18:41:06. 8988 ] Started HTTP server on port 9090nI1031 18:41:06. 8988 ] Started UDP server on port 9091n\"\", } to be nil failed (0xc000f1d000) +0x469 () +0x335} Kubernetes e2e suite: [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart https hook properly [MinimumKubeletVersion:1.23] [NodeConformance] | 5m11s -- | -- {Oct 31 19:05:50.205: timed out while waiting for pod container-lifecycle-hook-6892/pod-with-poststart-https-hook to be running and ready failed (PodClient).CreateSync(0xc000eb5920, 0x22?) +0x94 (0xc0045e8c00) +0x73 () +0x325} No response_ /sig windows cc\n/triage accepted /cc\nThese failures happen also with Kubernetes master + containerd master with Flannel CNI. Testgrid link:\nI figured out why these new failures appear.", "commid": "kubernetes_issue_113479", "tokennum": 564}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9ddef8812cad782f4c5e8137ed479959bc608d8f005148172df935e1d20d011d", "query": "/* Release : v1.23 Testname: Pod Lifecycle, poststart https hook <del> Description: When a post-start handler is specified in the container lifecycle using a 'HttpGet' action, then the handler MUST be invoked before the container is terminated. A server pod is created that will serve https requests, create a second pod with a container lifecycle specifying a post-start that invokes the server pod to validate that the post-start is executed. </del> <ins> Description: When a post-start handler is specified in the container lifecycle using a 'HttpGet' action, then the handler MUST be invoked before the container is terminated. A server pod is created that will serve https requests, create a second pod on the same node with a container lifecycle specifying a post-start that invokes the server pod to validate that the post-start is executed. </ins> */ ginkgo.It(\"should execute poststart https hook properly [MinimumKubeletVersion:1.23] [NodeConformance]\", func() { lifecycle := &v1.Lifecycle{", "positive_passages": [{"docid": "doc-en-kubernetes-468407671b0c3bb4dc0cf6c503c02539c6d31cfb69250c40c5c81f059af779f1", "text": "I've submitted the fix via PR\nThis issue is also affecting 1.25 tests: If possible, we should cherry-pick to the release-1.25 branch once it's merged on master.", "commid": "kubernetes_issue_113479", "tokennum": 42}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9e65032d5be8d1eb334d7d135d9d0bd3b466ac135631274abed97cccfa3bb82f", "query": "# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE # INSTRUCTIONS AT https://kubernetes.io/security/ <del> cjcullen joelsmith liggitt philips </del> <ins> caesarxuchao deads2k lavalamp </ins> sttts <del> tallclair </del>", "positive_passages": [{"docid": "doc-en-kubernetes-4c28255cc86038c3c93f9e461780faa3ed1b46443f53f929b0e421cdbd186a35", "text": "The purpose of the file for each Kubernetes repository is to provide a list of people who can assist the Kubernetes in the event that a security issue related to the repository is discovered or disclosed. As described in the file, those on the list should agree to our . Please update the  file for the sample-controller repository. After finding people who are willing to work in this capacity, you should add them to the list, then remove PSC members (except any PSC member will be working as a security contact for this repository). The list is GitHub usernames, optionally followed by an email address. If no email address is listed, the PSC will use the email address found on git commits made by the listed user. The file may already have people listed who are secuirty contacts. In that case, simply remove any PSC members who aren't also security contacts for the repo. See for more information /area security /committee product-security /kind cleanup /lifecycle frozen /priority important-soon /sig api-machinery", "commid": "kubernetes_issue_92105", "tokennum": 223}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9e65032d5be8d1eb334d7d135d9d0bd3b466ac135631274abed97cccfa3bb82f", "query": "# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE # INSTRUCTIONS AT https://kubernetes.io/security/ <del> cjcullen joelsmith liggitt philips </del> <ins> caesarxuchao deads2k lavalamp </ins> sttts <del> tallclair </del>", "positive_passages": [{"docid": "doc-en-kubernetes-33911e735262f8481400ca2430d671c6536468b71d87ed87bbe4f11626c79fd6", "text": "The purpose of the file for each Kubernetes repository is to provide a list of people who can assist the Kubernetes in the event that a security issue related to the repository is discovered or disclosed. As described in the file, those on the list should agree to our . Please update the  file for the sample-apiserver repository. After finding people who are willing to work in this capacity, you should add them to the list, then remove PSC members (except any PSC member will be working as a security contact for this repository). The list is GitHub usernames, optionally followed by an email address. If no email address is listed, the PSC will use the email address found on git commits made by the listed user. The file may already have people listed who are secuirty contacts. In that case, simply remove any PSC members who aren't also security contacts for the repo. See for more information /area security /committee product-security /kind cleanup /lifecycle frozen /priority important-soon /sig api-machinery", "commid": "kubernetes_issue_92103", "tokennum": 225}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9e65032d5be8d1eb334d7d135d9d0bd3b466ac135631274abed97cccfa3bb82f", "query": "# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE # INSTRUCTIONS AT https://kubernetes.io/security/ <del> cjcullen joelsmith liggitt philips </del> <ins> caesarxuchao deads2k lavalamp </ins> sttts <del> tallclair </del>", "positive_passages": [{"docid": "doc-en-kubernetes-575caba005fa0a194c5e9ab05a9e30ee6530f864ab126bf649eed87c7efec61c", "text": "The purpose of the file for each Kubernetes repository is to provide a list of people who can assist the Kubernetes in the event that a security issue related to the repository is discovered or disclosed. As described in the file, those on the list should agree to our . Please update the  file for the kube-aggregator repository. After finding people who are willing to work in this capacity, you should add them to the list, then remove PSC members (except any PSC member will be working as a security contact for this repository). The list is GitHub usernames, optionally followed by an email address. If no email address is listed, the PSC will use the email address found on git commits made by the listed user. The file may already have people listed who are secuirty contacts. In that case, simply remove any PSC members who aren't also security contacts for the repo. See for more information /area security /committee product-security /kind cleanup /lifecycle frozen /priority important-soon /sig api-machinery", "commid": "kubernetes_issue_92095", "tokennum": 224}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9e65032d5be8d1eb334d7d135d9d0bd3b466ac135631274abed97cccfa3bb82f", "query": "# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE # INSTRUCTIONS AT https://kubernetes.io/security/ <del> cjcullen joelsmith liggitt philips </del> <ins> caesarxuchao deads2k lavalamp </ins> sttts <del> tallclair </del>", "positive_passages": [{"docid": "doc-en-kubernetes-f1cb8df6316e5a200598bb646e70f7d130ec0c75fc9f39b3e957189b80c10ad2", "text": "The purpose of the file for each Kubernetes repository is to provide a list of people who can assist the Kubernetes in the event that a security issue related to the repository is discovered or disclosed. As described in the file, those on the list should agree to our . Please update the  file for the code-generator repository. After finding people who are willing to work in this capacity, you should add them to the list, then remove PSC members (except any PSC member will be working as a security contact for this repository). The list is GitHub usernames, optionally followed by an email address. If no email address is listed, the PSC will use the email address found on git commits made by the listed user. The file may already have people listed who are secuirty contacts. In that case, simply remove any PSC members who aren't also security contacts for the repo. See for more information /area code-generation /area security /committee product-security /kind cleanup /lifecycle frozen /priority important-soon /sig api-machinery", "commid": "kubernetes_issue_92091", "tokennum": 228}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9e65032d5be8d1eb334d7d135d9d0bd3b466ac135631274abed97cccfa3bb82f", "query": "# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE # INSTRUCTIONS AT https://kubernetes.io/security/ <del> cjcullen joelsmith liggitt philips </del> <ins> caesarxuchao deads2k lavalamp </ins> sttts <del> tallclair </del>", "positive_passages": [{"docid": "doc-en-kubernetes-b6c24ff2339a072ce41f583a86461ffd390f0efd073046044ccabd0e8baad713", "text": "The purpose of the file for each Kubernetes repository is to provide a list of people who can assist the Kubernetes in the event that a security issue related to the repository is discovered or disclosed. As described in the file, those on the list should agree to our . Please update the  file for the client-go repository. After finding people who are willing to work in this capacity, you should add them to the list, then remove PSC members (except any PSC member will be working as a security contact for this repository). The list is GitHub usernames, optionally followed by an email address. If no email address is listed, the PSC will use the email address found on git commits made by the listed user. The file may already have people listed who are secuirty contacts. In that case, simply remove any PSC members who aren't also security contacts for the repo. See for more information /area security /committee product-security /kind cleanup /lifecycle frozen /priority important-soon /sig api-machinery", "commid": "kubernetes_issue_92088", "tokennum": 223}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9e65032d5be8d1eb334d7d135d9d0bd3b466ac135631274abed97cccfa3bb82f", "query": "# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE # INSTRUCTIONS AT https://kubernetes.io/security/ <del> cjcullen joelsmith liggitt philips </del> <ins> caesarxuchao deads2k lavalamp </ins> sttts <del> tallclair </del>", "positive_passages": [{"docid": "doc-en-kubernetes-773ad9c7c77ed09f247ebe6fe4a2e977a2482d0db8567e965fc0d687730a34f0", "text": "The purpose of the file for each Kubernetes repository is to provide a list of people who can assist the Kubernetes in the event that a security issue related to the repository is discovered or disclosed. As described in the file, those on the list should agree to our . Please update the  file for the apiserver repository. After finding people who are willing to work in this capacity, you should add them to the list, then remove PSC members (except any PSC member will be working as a security contact for this repository). The list is GitHub usernames, optionally followed by an email address. If no email address is listed, the PSC will use the email address found on git commits made by the listed user. The file may already have people listed who are secuirty contacts. In that case, simply remove any PSC members who aren't also security contacts for the repo. See for more information /area apiserver /area security /committee product-security /kind cleanup /lifecycle frozen /priority important-soon /sig api-machinery", "commid": "kubernetes_issue_92087", "tokennum": 228}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9e65032d5be8d1eb334d7d135d9d0bd3b466ac135631274abed97cccfa3bb82f", "query": "# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE # INSTRUCTIONS AT https://kubernetes.io/security/ <del> cjcullen joelsmith liggitt philips </del> <ins> caesarxuchao deads2k lavalamp </ins> sttts <del> tallclair </del>", "positive_passages": [{"docid": "doc-en-kubernetes-fad8ee5585f13cbd059c3b23e9b0beba24a9e5cc8dc4cbda61f103e29d873595", "text": "The purpose of the file for each Kubernetes repository is to provide a list of people who can assist the Kubernetes in the event that a security issue related to the repository is discovered or disclosed. As described in the file, those on the list should agree to our . Please update the  file for the apimachinery repository. After finding people who are willing to work in this capacity, you should add them to the list, then remove PSC members (except any PSC member will be working as a security contact for this repository). The list is GitHub usernames, optionally followed by an email address. If no email address is listed, the PSC will use the email address found on git commits made by the listed user. The file may already have people listed who are secuirty contacts. In that case, simply remove any PSC members who aren't also security contacts for the repo. See for more information /area security /committee product-security /kind cleanup /lifecycle frozen /priority important-soon /sig api-machinery", "commid": "kubernetes_issue_92085", "tokennum": 224}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9e65032d5be8d1eb334d7d135d9d0bd3b466ac135631274abed97cccfa3bb82f", "query": "# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE # INSTRUCTIONS AT https://kubernetes.io/security/ <del> cjcullen joelsmith liggitt philips </del> <ins> caesarxuchao deads2k lavalamp </ins> sttts <del> tallclair </del>", "positive_passages": [{"docid": "doc-en-kubernetes-df9e56efa1a5d0dfe5cf4c9ff5d0ae22d67682beafe379ced520bca8e339d7ed", "text": "The purpose of the file for each Kubernetes repository is to provide a list of people who can assist the Kubernetes in the event that a security issue related to the repository is discovered or disclosed. As described in the file, those on the list should agree to our . Please update the  file for the apiextensions-apiserver repository. After finding people who are willing to work in this capacity, you should add them to the list, then remove PSC members (except any PSC member will be working as a security contact for this repository). The list is GitHub usernames, optionally followed by an email address. If no email address is listed, the PSC will use the email address found on git commits made by the listed user. The file may already have people listed who are secuirty contacts. In that case, simply remove any PSC members who aren't also security contacts for the repo. See for more information /area security /committee product-security /kind cleanup /lifecycle frozen /priority important-soon /sig api-machinery", "commid": "kubernetes_issue_92084", "tokennum": 228}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9e83e63ec7f36b10e779fe6f9b2f6d8291d23f7fa92f7cc79d9af6af6954ba77", "query": "func (detacher *vsphereVMDKDetacher) Detach(volumeName string, nodeName types.NodeName) error { volPath := getVolPathfromVolumeName(volumeName) <del> attached, err := detacher.vsphereVolumes.DiskIsAttached(volPath, nodeName) </del> <ins> attached, newVolumePath, err := detacher.vsphereVolumes.DiskIsAttached(volPath, nodeName) </ins> if err != nil { // Log error and continue with detach klog.Errorf(", "positive_passages": [{"docid": "doc-en-kubernetes-e1df151812a738ca8d7e9f97519d671c643638f3ca9d9400cc430f5f7a7d204c", "text": "When user creates a static PV using folder name in path: on vSAN backed datastore then detach disk does not work because check fails - The code expects folder name to be UUID but it does not and hence it determines disk is not attached to the node and hence no detach is ever performed. /sig storage cc", "commid": "kubernetes_issue_95121", "tokennum": 68}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9e8a193df356d1bfa4ea4013a630b82e7f28bfbc8a84ff32231370d87c7ab4d3", "query": "prepare-e2e while true; do <del> ${KUBECTL} --watch-only get events </del> <ins> ${KUBECTL} get events --watch-only </ins> done", "positive_passages": [{"docid": "doc-en-kubernetes-dbffed5438f566ecf1b631adacf4d68392348225a8f199c6d9953211f55b24b3", "text": "This is the script that runs to capture event output during e2e runs: It's failing after the recent pflag merge:\ncc\nOr something. I might be completely off. But something broke it recently enough, and I know like his event log.\nThat command is actually invalid. is a flag on the command, not the root. Fix in", "commid": "kubernetes_issue_5902", "tokennum": 72}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9e9600bc3e4e00d4074aaf5006c18cbc89098c3534383fb71fc932f6f4f5ec65", "query": "], \"volumes\": [{ \"name\":\"kubectl\", <del> \"hostPath\":{\"path\": \"/usr/bin/kubectl\"} </del> <ins> \"hostPath\":{\"path\": \"$KUBECTL_PATH\"} </ins> }] } }", "positive_passages": [{"docid": "doc-en-kubernetes-30073b5bdd6536f3426706d62259848d2143e49f7e7d427f9e7ac1b4ee8d409d", "text": "https://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes", "commid": "kubernetes_issue_36586", "tokennum": 633}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9e9600bc3e4e00d4074aaf5006c18cbc89098c3534383fb71fc932f6f4f5ec65", "query": "], \"volumes\": [{ \"name\":\"kubectl\", <del> \"hostPath\":{\"path\": \"/usr/bin/kubectl\"} </del> <ins> \"hostPath\":{\"path\": \"$KUBECTL_PATH\"} </ins> }] } }", "positive_passages": [{"docid": "doc-en-kubernetes-190b617a6f6f5bf58cdcd7e3b6ef0448e95fbe4e5f55ef7f7041e83808b7f11a", "text": "e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nAre you the correct assignee for this? If so, can you please give an update. If not, can you please reassign it to the correct person. CC\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nYes, I guess so. I'm looking into it.", "commid": "kubernetes_issue_36586", "tokennum": 517}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9e9600bc3e4e00d4074aaf5006c18cbc89098c3534383fb71fc932f6f4f5ec65", "query": "], \"volumes\": [{ \"name\":\"kubectl\", <del> \"hostPath\":{\"path\": \"/usr/bin/kubectl\"} </del> <ins> \"hostPath\":{\"path\": \"$KUBECTL_PATH\"} </ins> }] } }", "positive_passages": [{"docid": "doc-en-kubernetes-dd35fe5a7b4eb5003d2805a282d33ab299b7be8f45ced73e66ae92981d37585e", "text": "https://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nWe need to get this fixed soon and picked up in release-1.5 since it is consistently red in\nack i have a PR currently running\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nIf you found the root cause, we will close my pending PR that printing out some debug info. What is the PR # of the commit you mentioned above?", "commid": "kubernetes_issue_36586", "tokennum": 470}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9e9600bc3e4e00d4074aaf5006c18cbc89098c3534383fb71fc932f6f4f5ec65", "query": "], \"volumes\": [{ \"name\":\"kubectl\", <del> \"hostPath\":{\"path\": \"/usr/bin/kubectl\"} </del> <ins> \"hostPath\":{\"path\": \"$KUBECTL_PATH\"} </ins> }] } }", "positive_passages": [{"docid": "doc-en-kubernetes-34e45dcd30e91b287f55b34ca0f7c874b506aed582f8cf03d9c09b8eddbaff00", "text": "https://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\n: here it is\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nWe timeout waiting for pod sometimes. Is it reasonable to use a longer timeout? Use for in that test.\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}\n: sure thing, do you want to do that in a fresh PR?\nI updated my pending PR .\nhttps://k8s- Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite}", "commid": "kubernetes_issue_36586", "tokennum": 397}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9ea8d31209f711b11930431c5c060293c0355db1ff8d807eda73d81a903b2f96", "query": "readCloser, err := client.RESTClient.Get(). Prefix(\"proxy\"). <del> Resource(\"minions\"). </del> <ins> Resource(\"nodes\"). </ins> Name(pod.Spec.Host). Suffix(\"containerLogs\", namespace, podID, container). Param(\"follow\", strconv.FormatBool(follow)).", "positive_passages": [{"docid": "doc-en-kubernetes-26d82dfedb03b77df6b1c9ca183f41f5576785fb4175159c538818ffb957183e", "text": "kubectl log stops working for me all the sudden: A little bit digging into the issue, I found the problem is only limited to /v1beta3: Query /v1beta1 Query through v1beta3\ncc/\nDoes replacing \"minions\" by \"nodes\" work?\nCool, looks like it should be a simple kubectl fix, I will do it shortly.", "commid": "kubernetes_issue_6696", "tokennum": 83}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9ef4928e312270530d85863e3f09af40a35f466fbbb33077c0f95e0c107922d4", "query": "}, \"fieldRef\": { \"$ref\": \"#/definitions/io.k8s.api.core.v1.ObjectFieldSelector\", <del> \"description\": \"Selects a field of the pod: supports metadata.name, metadata.namespace, metadata.labels, metadata.annotations, spec.nodeName, spec.serviceAccountName, status.hostIP, status.podIP, status.podIPs.\" </del> <ins> \"description\": \"Selects a field of the pod: supports metadata.name, metadata.namespace, `metadata.labels['<KEY>']`, `metadata.annotations['<KEY>']`, spec.nodeName, spec.serviceAccountName, status.hostIP, status.podIP, status.podIPs.\" </ins> }, \"resourceFieldRef\": { \"$ref\": \"#/definitions/io.k8s.api.core.v1.ResourceFieldSelector\",", "positive_passages": [{"docid": "doc-en-kubernetes-5018642be16ab87784521fef6d356d625aa306ba1fff6efc2d4048e42ef1a94c", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: When I tried to create a pod with env variables referencing to annotations: What you expected to happen: Should Proceed. As in It stated is a valid option How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.18.2 Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig docs\nThe API docs need to be updated to indicate the correct supported values. See for correct values\nYou are a lifesaver. Thank you!\n/assign I can try to update the api documentation", "commid": "kubernetes_issue_91165", "tokennum": 215}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9f282c409a5e9f21e1339f81b521757c3d9e12c155eff764de0359ffa9dbd385", "query": "framework.ExpectNoError(err, \"Failed to remove %s cronjob in namespace %s\", cronJob.Name, f.Namespace.Name) }) <del> // cleanup of successful/failed finished jobs, with successfulJobsHistoryLimit and failedJobsHistoryLimit ginkgo.It(\"should delete successful/failed finished jobs with limit of one job [Flaky]\", func() { testCases := []struct { description  string command      []string successLimit int32 failedLimit  int32 }{ { description:  \"successful-jobs-history-limit\", command:      successCommand, successLimit: 1, // keep one successful job failedLimit:  0, // keep none failed job }, { description:  \"failed-jobs-history-limit\", command:      failureCommand, successLimit: 0, // keep none succcessful job failedLimit:  1, // keep one failed job }, } </del> <ins> // cleanup of successful finished jobs, with limit of one successful job ginkgo.It(\"should delete successful finished jobs with limit of one successful job\", func() { ginkgo.By(\"Creating an AllowConcurrent cronjob with custom history limit\") successLimit := int32(1) failedLimit := int32(0) cronJob := newTestCronJob(\"successful-jobs-history-limit\", \"*/1 * * * ?\", batchv1beta1.AllowConcurrent, successCommand, &successLimit, &failedLimit) ensureHistoryLimits(f.ClientSet, f.Namespace.Name, cronJob) }) </ins> <del> for _, t := range testCases { ginkgo.By(fmt.Sprintf(\"Creating a AllowConcurrent cronjob with custom %s\", t.description)) cronJob := newTestCronJob(t.description, \"*/1 * * * ?\", batchv1beta1.AllowConcurrent, t.command, &t.successLimit, &t.failedLimit) cronJob, err := createCronJob(f.ClientSet, f.Namespace.Name, cronJob) framework.ExpectNoError(err, \"Failed to create allowconcurrent cronjob with custom history limits in namespace %s\", f.Namespace.Name) // Job is going to complete instantly: do not check for an active job // as we are most likely to miss it ginkgo.By(\"Ensuring a finished job exists\") err = waitForAnyFinishedJob(f.ClientSet, f.Namespace.Name) framework.ExpectNoError(err, \"Failed to ensure a finished cronjob exists in namespace %s\", f.Namespace.Name) ginkgo.By(\"Ensuring a finished job exists by listing jobs explicitly\") jobs, err := f.ClientSet.BatchV1().Jobs(f.Namespace.Name).List(metav1.ListOptions{}) framework.ExpectNoError(err, \"Failed to ensure a finished cronjob exists by listing jobs explicitly in namespace %s\", f.Namespace.Name) activeJobs, finishedJobs := filterActiveJobs(jobs) if len(finishedJobs) != 1 { framework.Logf(\"Expected one finished job in namespace %s; activeJobs=%v; finishedJobs=%v\", f.Namespace.Name, activeJobs, finishedJobs) framework.ExpectEqual(len(finishedJobs), 1) } </del> <ins> // cleanup of failed finished jobs, with limit of one failed job ginkgo.It(\"should delete failed finished jobs with limit of one job\", func() { ginkgo.By(\"Creating an AllowConcurrent cronjob with custom history limit\") successLimit := int32(0) failedLimit := int32(1) cronJob := newTestCronJob(\"failed-jobs-history-limit\", \"*/1 * * * ?\", batchv1beta1.AllowConcurrent, failureCommand, &successLimit, &failedLimit) </ins> <del> // Job should get deleted when the next job finishes the next minute ginkgo.By(\"Ensuring this job and its pods does not exist anymore\") err = waitForJobToDisappear(f.ClientSet, f.Namespace.Name, finishedJobs[0]) framework.ExpectNoError(err, \"Failed to ensure that job does not exists anymore in namespace %s\", f.Namespace.Name) err = waitForJobsPodToDisappear(f.ClientSet, f.Namespace.Name, finishedJobs[0]) framework.ExpectNoError(err, \"Failed to ensure that pods for job does not exists anymore in namespace %s\", f.Namespace.Name) ginkgo.By(\"Ensuring there is 1 finished job by listing jobs explicitly\") jobs, err = f.ClientSet.BatchV1().Jobs(f.Namespace.Name).List(metav1.ListOptions{}) framework.ExpectNoError(err, \"Failed to ensure there is one finished job by listing job explicitly in namespace %s\", f.Namespace.Name) _, finishedJobs = filterActiveJobs(jobs) framework.ExpectEqual(len(finishedJobs), 1) ginkgo.By(\"Removing cronjob\") err = deleteCronJob(f.ClientSet, f.Namespace.Name, cronJob.Name) framework.ExpectNoError(err, \"Failed to remove the %s cronjob in namespace %s\", cronJob.Name, f.Namespace.Name) } </del> <ins> ensureHistoryLimits(f.ClientSet, f.Namespace.Name, cronJob) </ins> }) }) <ins> func ensureHistoryLimits(c clientset.Interface, ns string, cronJob *batchv1beta1.CronJob) { cronJob, err := createCronJob(c, ns, cronJob) framework.ExpectNoError(err, \"Failed to create allowconcurrent cronjob with custom history limits in namespace %s\", ns) // Job is going to complete instantly: do not check for an active job // as we are most likely to miss it ginkgo.By(\"Ensuring a finished job exists\") err = waitForAnyFinishedJob(c, ns) framework.ExpectNoError(err, \"Failed to ensure a finished cronjob exists in namespace %s\", ns) ginkgo.By(\"Ensuring a finished job exists by listing jobs explicitly\") jobs, err := c.BatchV1().Jobs(ns).List(metav1.ListOptions{}) framework.ExpectNoError(err, \"Failed to ensure a finished cronjob exists by listing jobs explicitly in namespace %s\", ns) activeJobs, finishedJobs := filterActiveJobs(jobs) if len(finishedJobs) != 1 { framework.Logf(\"Expected one finished job in namespace %s; activeJobs=%v; finishedJobs=%v\", ns, activeJobs, finishedJobs) framework.ExpectEqual(len(finishedJobs), 1) } // Job should get deleted when the next job finishes the next minute ginkgo.By(\"Ensuring this job and its pods does not exist anymore\") err = waitForJobToDisappear(c, ns, finishedJobs[0]) framework.ExpectNoError(err, \"Failed to ensure that job does not exists anymore in namespace %s\", ns) err = waitForJobsPodToDisappear(c, ns, finishedJobs[0]) framework.ExpectNoError(err, \"Failed to ensure that pods for job does not exists anymore in namespace %s\", ns) ginkgo.By(\"Ensuring there is 1 finished job by listing jobs explicitly\") jobs, err = c.BatchV1().Jobs(ns).List(metav1.ListOptions{}) framework.ExpectNoError(err, \"Failed to ensure there is one finished job by listing job explicitly in namespace %s\", ns) activeJobs, finishedJobs = filterActiveJobs(jobs) if len(finishedJobs) != 1 { framework.Logf(\"Expected one finished job in namespace %s; activeJobs=%v; finishedJobs=%v\", ns, activeJobs, finishedJobs) framework.ExpectEqual(len(finishedJobs), 1) } ginkgo.By(\"Removing cronjob\") err = deleteCronJob(c, ns, cronJob.Name) framework.ExpectNoError(err, \"Failed to remove the %s cronjob in namespace %s\", cronJob.Name, ns) } </ins> // newTestCronJob returns a cronjob which does one of several testing behaviors. func newTestCronJob(name, schedule string, concurrencyPolicy batchv1beta1.ConcurrencyPolicy, command []string, successfulJobsHistoryLimit *int32, failedJobsHistoryLimit *int32) *batchv1beta1.CronJob {", "positive_passages": [{"docid": "doc-en-kubernetes-f4fbd406d4e0e170dfafc3e7da28855114900a8241a757fc2216c8af6fba3e29", "text": "<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI --Which jobs are flaking: pull-kubernetes-e2e-gce ci-kubernetes-e2e-gci-gce Which test(s) are flaking: [sig-apps] CronJob should delete successful/failed finished jobs with limit of one job Testgrid link: Reason for failure: Anything else we need to know: this is the top flake for pull-kubernetes-e2e-gce: triage link: specific failures /sig apps /priority important-soon\nthis is the second flakiest test (failing on ~15% of PR runs)\nI'll look into it. /assign\nif there's not an obvious immediate fix, I would recommend: the test as to skip the test in merge-blocking job runs a second PR that reverts the change and adds debugging commits and do on that PR to flush out issues this issue open and in the current milestone to track resolution of the test before release (either by fixing the test, finding/fixing an underlying bug, or proving we have test coverage of the function via another method and deleting the test)\nmarked as in , will leave this issue open to track root causing, fixing, restoring the test before release\nTo follow up here, this was confirmed as root-caused, fixed and restored by", "commid": "kubernetes_issue_86179", "tokennum": 323}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9f49c1bd3dd87cb062469e04bcec7d56ac8d57af26fee05a4821c9687d9f4bdc", "query": "return false, nil } <ins> func (f *FakeMounter) EvalHostSymlinks(pathname string) (string, error) { return pathname, nil } </ins> func (f *FakeMounter) PrepareSafeSubpath(subPath Subpath) (newHostPath string, cleanupAction func(), err error) { return subPath.Path, nil, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-226c0928db9d5aa6f1446838b8788eb7c60cd41b1b8246f4bd1a4e2614bb7834", "text": "/kind bug Using , if a block device is symlinked to the discovery directory e.g. , then MapVolume will fail with since the containerized kubelet cannot see the path on host. is mounted by containerized kubelet, so if before we try to map the device we set devicePath to the evaluation of symlink and end up with a devicePath of , containerized kubelet will see the device and successfully map the device. Are there any issues with this solution? This is on Kubernetes 1.10\n/sig storage\nah yes containerized kubelet has many issues when dealing with symlinks. Check out Mounter.GetMode(), it calls a nsenter EvalSymlinks which should be able to do what you need. But actually, one thing to consider, is do you need to do the losetup on the host, or does inside the container work?\nYes it appears to work from inside the container, on the host I run which disappears after I delete the pod using the device. My understanding of running losetup in MapVolume is not that great but I suppose that as long as that /dev/loop0 is created we are fine. Thanks for the quick response, I'll create a PR using that function and tag you\nDoes it create it on the host or in the containerized kubelet? What happens when containerized kubelet is restarted? The purpose of losetup is to do \"refcounting\" on the block device to prevent possible naming collisions when devices are attached/detached under unhealthy conditions. Ie, if a device showed up as /dev/sdb and you gave that to a pod, and then for some reason it become unhealthy and disappeared (while the pod is still running), another device (maybe even another volume type) could get attached to the node and reuse /dev/sdb. Now the pod has access to a device it's not supposed to. With filesystem volumes, the refcounting is done with mount points, but for block device, loopback is the equivalent.\nIt is created on the host (and also visible in the container), and stays around through restart. I understand now, thank you.\nActually after I restart it becomes /vdb instead of /dev/vdb in the losetup output, idk what that is about.", "commid": "kubernetes_issue_65445", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9f49c1bd3dd87cb062469e04bcec7d56ac8d57af26fee05a4821c9687d9f4bdc", "query": "return false, nil } <ins> func (f *FakeMounter) EvalHostSymlinks(pathname string) (string, error) { return pathname, nil } </ins> func (f *FakeMounter) PrepareSafeSubpath(subPath Subpath) (newHostPath string, cleanupAction func(), err error) { return subPath.Path, nil, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-e6271b0ba1dda755d5bb536a727016a621c7c29c599386bc1e9c22a230980cbf", "text": "There is no such thing as /vdb and /dev/vdb is still intact of course. Seems inconsequential since it is disappearing after all pods using the device are deleted, i.e. it's still serving as a refcounter", "commid": "kubernetes_issue_65445", "tokennum": 55}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9f60228400e9569121547cf37f7cf82af4c5b399131e2c5f74b451f9e9818659", "query": "\"github.com/vmware/govmomi/object\" \"github.com/vmware/govmomi/vim25/mo\" <del> \"k8s.io/klog/v2\" </del> v1 \"k8s.io/api/core/v1\" <ins> \"k8s.io/apimachinery/pkg/api/errors\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" </ins> k8stypes \"k8s.io/apimachinery/pkg/types\" <ins> coreclients \"k8s.io/client-go/kubernetes/typed/core/v1\" corelisters \"k8s.io/client-go/listers/core/v1\" </ins> cloudprovider \"k8s.io/cloud-provider\" <ins> \"k8s.io/klog/v2\" </ins> \"k8s.io/legacy-cloud-providers/vsphere/vclib\" )", "positive_passages": [{"docid": "doc-en-kubernetes-b9a7a79272b4f05e986ec052f9f8348c60cffedf2d99a44ddafb98b4101b558f", "text": "I am enabling CSI migration on a vSphere cluster. A node was fully drained, all its Pods are deleted, but just before KCM detaches in-tree vSphere volume volumes from it, KCM restarts. A new KCM starts, sees attached volumes in that are not needed by any Pod on the node and calls vSphere in-tree volume plugin . The in-tree vSphere volume plugin + cloud provider marks the volume as detached right away, without reaching to vCenter API. The volume remains attached forever. I don't think it's related to CSI migration, IMO a regular node drain + KCM restart at the same time can cause the same issue. KCM logs: The in-tree cloud provider has a and from it. It apparently has not processed all nodes at the time A/D controller tries to detach the node. The in-tree vSphere volume plugin + cloud provider detaches the volume in vCenter. That's really tricky, it's very hard / impossible to reproduce on a real cluster. I had to inject errors to Detach() in-tree volume call, so they fail until KCM is restarted. Newly started KCM would detach the volume just fine (no error would be injected there), but marks the volume as detached right away. For the record (and search-ability), the CSI driver that tries to attach the volume to another node complains either: Or: cc It could be somewhat related to , however, not all cases of can be related to KCM restart. As I mentioned above, it's very hard/impossible to synchronize KCM restart with draining a node in a real cluster. <details</details<detailsvSphere 7.0.3 </details<details</details<detailsOpenShift </details<detailsCRI-O </details<details</details\n/sig storage\nTried just moving a Pod between nodes without CSI migration involved + restarting KCM when the volume is still attached to the old node. In-tree volume plugin on the new node says:\n/assign\nWhat CSI driver version and K8s version are you testing with?\nKubernetes is 1.25 and CSI driver is 2.7, still, I think it's not releated to the CSI driver, it's KCM who marks the in-tree volume as detached due to not populated node cache.", "commid": "kubernetes_issue_117091", "tokennum": 517}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9f60228400e9569121547cf37f7cf82af4c5b399131e2c5f74b451f9e9818659", "query": "\"github.com/vmware/govmomi/object\" \"github.com/vmware/govmomi/vim25/mo\" <del> \"k8s.io/klog/v2\" </del> v1 \"k8s.io/api/core/v1\" <ins> \"k8s.io/apimachinery/pkg/api/errors\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" </ins> k8stypes \"k8s.io/apimachinery/pkg/types\" <ins> coreclients \"k8s.io/client-go/kubernetes/typed/core/v1\" corelisters \"k8s.io/client-go/listers/core/v1\" </ins> cloudprovider \"k8s.io/cloud-provider\" <ins> \"k8s.io/klog/v2\" </ins> \"k8s.io/legacy-cloud-providers/vsphere/vclib\" )", "positive_passages": [{"docid": "doc-en-kubernetes-27c84c169fad17ff032040ca08c7bb73c7215213dd29c5491da1ee415abb2a33", "text": "/assign\n/triage accepted\nI found an easier way how to reproduce this without extra code in KCM: a StatefulSet with 1 Pod that uses 1 PVC. the node where the Pod runs. down kube-controller-manager to zero (not really possible for me) or kill all kube-controller-manager Pods. This will cause new KCM processes to wait for leader election. In my env. this gives me ~30 seconds for the next step. Delete the Pod. A new one will be scheduled on a different node (because the current node is cordoned) + there is no KCM running at this time that would detach the volume from the old node. KCM wins its leader election, sees a volume attached to a node where it is not needed -it calls of the volume plugin. VSphere cloud provider does not have its caches populated yet (= this bug) -the volume is not detached, but returns success.\ndangling attach does not help here. The volume is still attached to the old node even after ~10 minutes. fails with and not with . I can see there is a lot of dangling attach code in the cloud provider, but I did not debug further.", "commid": "kubernetes_issue_117091", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9f6c363e5132a9e87b5efae07ee69369c2cc668ac7116c48c3e7ad9601dae140", "query": "if index != -1 { // Delete element `index` <del> addr_pairs[index] = addr_pairs[len(routes)-1] addr_pairs = addr_pairs[:len(routes)-1] </del> <ins> addr_pairs[index] = addr_pairs[len(addr_pairs)-1] addr_pairs = addr_pairs[:len(addr_pairs)-1] </ins> unwind, err := updateAllowedAddressPairs(r.network, &port, addr_pairs) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-d17b1ff8ae06b13c6af5817488a3cb18d76c8f278663cf75b8a3d7d0d9abccc1", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: After starting controller manager, get the following panic: /---------------------------------- I0712 08:54:30. 1 ] Deleting route 10.245.1.0/24 10.245.1.0/24 I0712 08:54:30. 1 ] Creating route for node ab-6l35lzekrg-0-7igjn3vr43tw-kube-minion-abhezrwnqucq 10.245.1.0/24 with hint -655c-11e7-9a48-, throttled 1.602\u00b5s I0712 08:54:30. 1 ] Creating route for node ab-hfvphu5tyl-0-623ksgxczeoh-kube-master-oevhfzd3xo7s 10.245.0.0/24 with hint -655c-11e7-9a48-, throttled 651ns I0712 08:54:31. 1 ] Created route for node ab-6l35lzekrg-0-7igjn3vr43tw-kube-minion-abhezrwnqucq 10.245.1.0/24 with hint -655c-11e7-9a48- after 349.278413ms I0712 08:54:32.", "commid": "kubernetes_issue_48800", "tokennum": 353}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9f6c363e5132a9e87b5efae07ee69369c2cc668ac7116c48c3e7ad9601dae140", "query": "if index != -1 { // Delete element `index` <del> addr_pairs[index] = addr_pairs[len(routes)-1] addr_pairs = addr_pairs[:len(routes)-1] </del> <ins> addr_pairs[index] = addr_pairs[len(addr_pairs)-1] addr_pairs = addr_pairs[:len(addr_pairs)-1] </ins> unwind, err := updateAllowedAddressPairs(r.network, &port, addr_pairs) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-def0ff2d7afb1041ed38dd536114d4f932b578dcf3a59e0d27da6b34b247c308", "text": "1 ] Created route for node ab-hfvphu5tyl-0-623ksgxczeoh-kube-master-oevhfzd3xo7s 10.245.0.0/24 with hint -655c-11e7-9a48- after 1.583805322s panic: runtime error: index out of range goroutine 1250 [running]: panic(0x3a3d4e0, 0xc42001a080) +0x1a1 (Routes).DeleteRoute(0xc4212e15a0, 0x40ff60e, 0xa, 0xc421bf22a0, 0x0, 0x0) +0x7d5 (RouteController).reconcile.func2(0xc4210bed70, 0xc421bf05e0, 0xc421bf22a0, 0xed0f7dac6, 0x3264f461, 0x6f143e0) +0x15a created by (RouteController).reconcile +0x6e6 /---------------------------------- What you expected to happen: Successed to delete route. How to reproduce it (as minimally and precisely as possible): verytime Anything else we need to know?: Environment: Kubernetes version (use ): v1.6.4 Cloud provider or hardware configuration*: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: cc /sig-openstack\nThere are no sig labels on this issue. Please by:<br(1) mentioning a sig: <bre.g., for API Machinery<br(2) specifying the label manually: <bre.g., for sig/scalability<br<brNote: method (1) will trigger a notification to the team. You can find the team list and label list\ncc\nReiterating the mentions to trigger a notification: <detailsIn response to : cc 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", "commid": "kubernetes_issue_48800", "tokennum": 530}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9fa9a8fa4a655f3b6fdb1af28ca7924f44f68b87457fec0ae7137a5302ab4f53", "query": "- /eventer - --source=kubernetes:'' - --sink=influxdb:http://monitoring-influxdb:8086 <del> - image: gcr.io/google_containers/addon-resizer:1.5 </del> <ins> - image: gcr.io/google_containers/addon-resizer:1.6 </ins> name: heapster-nanny resources: limits:", "positive_passages": [{"docid": "doc-en-kubernetes-aa5745d62aee7fc04015b35348d752ab217dfca76565e758f0ca6e53fe701514", "text": "HPA tests are currently failing in gke-large cluster suite: I did some debugging and the problem seems to be related to pod-nanny. Looking into logs from the last run: was first scheduled on the large node dedicated to it pod-nany updated heapster deployment then heapster was scheduled on the normal node (when it actually shouldn't fit) that point it was never updated by the pod nanny. that point, heapster started crashlooping (OOMing) [which in fact was expected in too small machine] So it's pretty clear that that pod-nanny changed the amount of resources to something smaller, which in fact it shouldn't.", "commid": "kubernetes_issue_31950", "tokennum": 140}], "negative_passages": []}
{"query_id": "q-en-kubernetes-9ffdebbae9526c98b1778c42b0bf762161b195aef3f5ad0041ac7df917e95674", "query": "source := framework.NewFakeControllerSource() // Let's do threadsafe output to get predictable test results. <del> outputSetLock := sync.Mutex{} outputSet := util.StringSet{} </del> <ins> deletionCounter := make(chan string, 1000) </ins> // Make a controller that immediately deletes anything added to it, and // logs anything deleted.", "positive_passages": [{"docid": "doc-en-kubernetes-20ba07f969c78351406740c712da4b4d48c539c847c31f97f90729edba71a7c4", "text": "From shippable, I noticed there are several failed cases, for example, E0413 17:34:38. ] watch of *api.Pod ended with: Stop requested --- FAIL: Example (0.61s) got: want: a-hello b-controller c-framework FAIL coverage: 85.9% of statements FAIL 7.652s cc/\nanother example:\nah-- this is a different thing. I will fix this, too.\nI'm seeing this from an unrelated change\nYeah I think that's the one I expected to see.", "commid": "kubernetes_issue_6777", "tokennum": 121}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a07b51b16ccd5ae2e42cad417f3353be8fe0125fa99325f81d73f1744d34cae9", "query": "// klog.V(4).Infof(\"rbd: info %s using mon %s, pool %s id %s key %s\", b.Image, mon, b.Pool, id, secret) output, err = b.exec.Run(\"rbd\", <del> \"info\", b.Image, \"--pool\", b.Pool, \"-m\", mon, \"--id\", id, \"--key=\"+secret, \"--format=json\") </del> <ins> \"info\", b.Image, \"--pool\", b.Pool, \"-m\", mon, \"--id\", id, \"--key=\"+secret, \"-k=/dev/null\", \"--format=json\") </ins> if err, ok := err.(*exec.Error); ok { if err.Err == exec.ErrNotFound {", "positive_passages": [{"docid": "doc-en-kubernetes-9ba58a38d1b26cddbe35d0c0365909f33d458f500f4464f9dc0ae31755bbc823", "text": "What happened: The rbd plugin use \"rbd info\" error: The messages before and after json result is warning string and no effect to rbd info, but it is effect to parse the output. So the kubernetes will failed: What you expected to happen: Kubernete no failed and errors How to reproduce it (as minimally and precisely as possible): Remove the config file\n/sig storage\nWe are blocked by this issue, can't resize any PVCs\nIssues 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\n/remove-lifecycle stale\nThat is another situation that cluster configuation is empty, aslo will return lots of warnning information: Also will trigger expand volume failed. But should we add -c=/dev/null in rbd info command?\nFolks, the pull request that would have fixed this just got closed as it was rotting away. This is an actual problem in production, can we please fix this?\n+1 we are still being plagued by this issue...\n+1 {\"name\":\"kubernetes-dynamic-pvc--147e-422c-9e67-\",\"size\":,\"objects\":2560,\"order\":22,\"objectsize\":,\"blocknameprefix\":\"rbddata.\",\"format\":2,\"features\":[\"layering\"],\"flags\":[]}, invalid character '-' after top-level value\nI solved by exceuting this command\nWow...I was not expecting this to work ... but it did ;) Any insights on why is it working with just the presence of the file? This is very strange... Appreciate any comments...", "commid": "kubernetes_issue_75581", "tokennum": 439}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a0cd06e09067dfe599c3ed5eba73f13d6ea7f47b8b3a3e6494815635b9278124", "query": "testRCReleaseControlledNotMatching(f) }) <del> ginkgo.It(\"[Flaky] should test the lifecycle of a ReplicationController\", func() { </del> <ins> /* Release: v1.20 Testname: Replication Controller, lifecycle Description: A Replication Controller (RC) is created, read, patched, and deleted with verification. */ framework.ConformanceIt(\"should test the lifecycle of a ReplicationController\", func() { </ins> testRcName := \"rc-test\" testRcNamespace := ns testRcInitialReplicaCount := int32(1)", "positive_passages": [{"docid": "doc-en-kubernetes-04298a57bb6bbadab2ae389c253044418da070e519876e8a987add6c4a3d1714", "text": "[x] Original approval issue: Start 9 June 2020 3 Flakes No Flakes for 2 weeks According to this APIsnoop query, there are still some remaining ReplicationController endpoints which are untested. a ReplicationController with a static label the ReplicationController with a new Label and updated data the ReplicationController's status /Scale the ReplicationController's Replica count to 2 Replicas the ReplicationController the ReplicationController's Status all ReplicationControllers in all Namespaces find the ReplicationControllers(1) ensure that the ReplicationController is found and is patched Namespaced ReplicationControllers(1) via a Collection with a LabelSelector Discover useragents: See all endpoints hit from this test Display test coverage change If a test with these calls gets merged, test coverage will go up by 7 points This test is also created with the goal of conformance promotion.\n/sig testing /sig architecture /area conformance\nCan you please add in PR\n/reopen Merged. Promotion to be created\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nIssues 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\n/remove-lifecycle stale", "commid": "kubernetes_issue_90881", "tokennum": 354}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a1383eea73f5cee2c37ff7baa26be38d8b780aa3633358b3ef0a403c091f1f2f", "query": "<del> 1.0 </del> <ins> 1.0.1 </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-086f2ac7dcab9c158ca481b0b58fae22976bc98ae146a7d10d5bef748052b70d", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: e2e tests which use RBD server image fail with What you expected to happen: These tests succeed. How to reproduce it (as minimally and precisely as possible): Run e2e tests which use RBD server image. Anything else we need to know?: /sig storage This issue is introduced by below commit: It change the base image from fedora 26 to fedora 28. In fedora 26, hostname command is installed as a dependency for  However, in fedora 28, it is not installed, as a result, this issue happens due to lack of hostname command. Environment: Kubernetes version (use ): k8s 1.12 alpha\nPlease see the difference of the behaviour between fedora 26 and 28. [Fedora26] [Fedora28]\nCould you help solving this issue? I assume the fix for the code would be as below, but I'm not familiar with the build and push process for the test image. ( in doesn't work.) So, I need your help to make further progress.\n(or) Both need to be run from directory\nThank you for letting me know it. It should be s/all-containers/all-container/, but it seems to work. I will test with above patch and above build commands, then make a PR, once I confirm that it works well.\nsorry typing from memory :)\nI need to ask you two more things: Do we need to increment the version for this image, like 1.0.1, even for this small change? (I guess that and test/images/volume/rbd/VERSION will need to be updated in this case.) How the image push process will be? Does it pushed by CI, if there are a change in the code or docker file, or do someone who have permission will push it manually?\ncreates below three docker images: Is my understanding right that to make each test access to each arch image, needs to be modified like below? (Without doing so, each test seems to keep trying to access to , without arch.)\nFor fedora28 image, just installing hostname doesn't seem to work well. Please see the log below and attached . I guess that this is due to the difference of ceph version, which will be beyond my beyond my expertise.", "commid": "kubernetes_issue_67269", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a1383eea73f5cee2c37ff7baa26be38d8b780aa3633358b3ef0a403c091f1f2f", "query": "<del> 1.0 </del> <ins> 1.0.1 </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-77a7b6220df65aff10095b84f9a73f01dc0b39abd15f0db81cc810c0f75ed2d0", "text": "So, could you help debugging this issue? Meanwhile, I will try testing with the image by using fedora26 for workaround.\nI confirmed that below commit, which change the base image back to fedora 26, fix this issue. Please see the log . After I checked the image-, I come to think that by pushing the image, each image will be able to be pulled without -arch, so I guess the last parameter for ImageConfig should be false. (I couldn't test it in my environment.) I will fix the commit as so and make a PR once I confirm it. Also, if it will easy to fix with Fedora 28, I will wait for the actual fix and quit making a PR for the workaround.\nthanks yes, a quick fix is welcome, looking forward\nThank you for your comment. I will continue with the workaround. I saw a commit for deleting multi arch consideration. I rebased the patch to the commit and made a PR. Please review it.", "commid": "kubernetes_issue_67269", "tokennum": 212}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a15cf79de2f5216b3530301aa6a55ddb7813fb466b1e42b10f8f9302e52826df", "query": "**All done !** <del> You can also use kubectl command to see if the newly created k8s is working correctly. </del> <ins> You can also use `kubectl` command to see if the newly created k8s is working correctly. The `kubectl` binary is under the `cluster/ubuntu/binaries` directory. You can move it into your PATH. Then you can use the below command smoothly. </ins> For example, use `$ kubectl get minions` to see if you get all your minion nodes comming up and ready. It may take some times for the minions be ready to use like below.", "positive_passages": [{"docid": "doc-en-kubernetes-6ad186288ef256533240c5bfccb6ba92929a47585cc346f791c0fbaeeb93c979", "text": "Though I have successfully installed kubernetes via :smiley: , still want to point out this doc missing the step to install . Thus, if user just follow the guide in the doc without having much knowledge about kubernetes, he/she would get error \"It looks as if you don't have a compiled kubectl binary\" during the step of . Manually install kubectl on at least master node should be necessary (suggest to let user also install on minion node for convenience), any way, the installation step is .\nI forget to mention that.I will update the doc this tuned\nI update the scripts in pr , you can try it now. I copied the kubectl binary from the kubernetes release and put it in , so there is no extra step for user to manually download . Actually, in the first version of ubuntu k8s deployment, I copied the to every node, but I think it is an overhead, so I removed it.I think this is just enough.\nDoc update : Move the kubectl into the PATH, it may need sudo privilege so I decide not do for the user.\nHave the same issue, please update the doc ASAP.\nGreat job :+1:\nAlso ran into this bug after recklessly running ( instead of ) :)", "commid": "kubernetes_issue_8373", "tokennum": 276}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a1685023e31121624d5cc4c2fb9ee289e05a0dcbafedddcb64eb993d84723675", "query": "var enqueued bool cases := []struct { <del> test          string newNode       *v1.Node oldNode       *v1.Node ds            *apps.DaemonSet shouldEnqueue bool </del> <ins> test               string newNode            *v1.Node oldNode            *v1.Node ds                 *apps.DaemonSet expectedEventsFunc func(strategyType apps.DaemonSetUpdateStrategyType) int shouldEnqueue      bool </ins> }{ { test:    \"Nothing changed, should not enqueue\",", "positive_passages": [{"docid": "doc-en-kubernetes-56dc15a3fe2161c6cf8927a51d2d0dce03fea80f01ef1e0345dcc3ca50d1379f", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: a cluster, And node1 with resource 1 DaemonSet, request resource 4 run , There is no pod created. resource to the node: run , There is still no pod created. What you expected to happen: In step 5, There is one pod created. How to reproduce it (as minimally and precisely as possible): see above description Anything else we need to know?: Environment: Kubernetes version (use ):1.10.5 Cloud provider or hardware configuration: OS (e.g. from /etc/os-release):CentOS7 Kernel (e.g. ): Install tools: Others: /sig app\nxref\nThanks! is not work here! Because: DaemonSetsController didn't watch the changes.(we use to updateNode.) we restart kubelet, The DaemonSetsController watch the changes, but it seems that the node info is not updated, and still failed to create pod:\nI found it is a bug here, ignore the changes. I made a fix , PTAL! Thanks!\nAny workarounds for old cluster versions? Up: looks like in my case helped but after some delay.\n, which version of k8s are you using? If it's sunset, you have to merge the pr yourself :). I think restart kubelet trigger delete/add to make sure it sync .\nSorry, I didn't say\nI think we still support 1.12 for now :) let's cherry pick it if not and wait for next 1.12 release.", "commid": "kubernetes_issue_67225", "tokennum": 342}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a16f4d0361d9022bd49314597410d9af998f54441a6dadaf8476561b0709e74f", "query": "} func (f *fakeAttachDetachVolumeHost) CSINodeLister() storagelistersv1.CSINodeLister { <del> // not needed for testing return nil </del> <ins> csiNode := &storagev1.CSINode{ ObjectMeta: metav1.ObjectMeta{Name: f.nodeName}, Spec: storagev1.CSINodeSpec{ Drivers: []storagev1.CSINodeDriver{}, }, } enableMigrationOnNode(csiNode, csilibplugins.GCEPDInTreePluginName) return getFakeCSINodeLister(csiNode) } func enableMigrationOnNode(csiNode *storagev1.CSINode, pluginName string) { nodeInfoAnnotations := csiNode.GetAnnotations() if nodeInfoAnnotations == nil { nodeInfoAnnotations = map[string]string{} } newAnnotationSet := sets.NewString() newAnnotationSet.Insert(pluginName) nas := strings.Join(newAnnotationSet.List(), \",\") nodeInfoAnnotations[v1.MigratedPluginsAnnotationKey] = nas csiNode.Annotations = nodeInfoAnnotations </ins> } func (f *fakeAttachDetachVolumeHost) CSIDriverLister() storagelistersv1.CSIDriverLister {", "positive_passages": [{"docid": "doc-en-kubernetes-43fa70370952068e2f27033c41492113945a1e0b0ce47a43a47f5065969f2aa7", "text": "After the cluster was updated to enable PD CSI Driver, there was a race condition where AD Controller (kube-controller-manager) started to BEFORE the PD CSI Driver was up, thus AD Controller gave us the error Then AD Controller triggered the disk detach because the disk/volume was not populated in the desired state of world. Unfortunately the disk was in use during this detach and got corrupted. Since cluster upgrades can cause the controller manager and CSI drivers to start at different times, the AD controller needs to be more conservative when detaching We have not been able to reproduce this, it came up from a customer. /sig storage /assign <detailsk8s 1.23, CSI migration enabled </details<detailsGKE </details<details</details<details</details<details</details<details</details\n/triage accepted\nI think there's potentially two changes we should do: 1) for the initial DSW population, we should skip the check that if the csi driver is not installed. 2) in general, we should not skip volumes during dsw initial population if an error is returned. If we had some temporary api server error then that would cause volumes to not get to dsw and similar behavior happen. cc\nfor a repro, maybe you can try something like: a cluster with csi migration enabled (control plane + nodes) a pod with intree-volume and get it running the csi driver node daemonset. verify the driver is removed from CSINode kube-controller-manager\ncc\n/cc was trying to repro this, but on GKE with the managed driver which made it complicated.\nYeah maybe gce kube-up would be easier for a repro\nIf CSINode says that it has migrated GCP PD volume plugin to CSI, then IMO A/D controller should always attach GCP PD volumes to it using CSI, regardless if the CSI driver is present or not. In-tree volume plugin in the kubelet is disabled and can't mount any in-tree volumes anyway. To flip the migration feature gate / upgrade / downgrade kubelet, the cluster admin must drain the node first to make sure everything is detached. A/D controller should not see change of CSINode migration annotations with any volume attached to it.\n/priority important-soon\nAnother option could be to process these volumes anyways but add them to DSOW with migration status as \"uncertain\", so as they can be re-processed later.", "commid": "kubernetes_issue_115297", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a16f4d0361d9022bd49314597410d9af998f54441a6dadaf8476561b0709e74f", "query": "} func (f *fakeAttachDetachVolumeHost) CSINodeLister() storagelistersv1.CSINodeLister { <del> // not needed for testing return nil </del> <ins> csiNode := &storagev1.CSINode{ ObjectMeta: metav1.ObjectMeta{Name: f.nodeName}, Spec: storagev1.CSINodeSpec{ Drivers: []storagev1.CSINodeDriver{}, }, } enableMigrationOnNode(csiNode, csilibplugins.GCEPDInTreePluginName) return getFakeCSINodeLister(csiNode) } func enableMigrationOnNode(csiNode *storagev1.CSINode, pluginName string) { nodeInfoAnnotations := csiNode.GetAnnotations() if nodeInfoAnnotations == nil { nodeInfoAnnotations = map[string]string{} } newAnnotationSet := sets.NewString() newAnnotationSet.Insert(pluginName) nas := strings.Join(newAnnotationSet.List(), \",\") nodeInfoAnnotations[v1.MigratedPluginsAnnotationKey] = nas csiNode.Annotations = nodeInfoAnnotations </ins> } func (f *fakeAttachDetachVolumeHost) CSIDriverLister() storagelistersv1.CSIDriverLister {", "positive_passages": [{"docid": "doc-en-kubernetes-8286ec57fa1e024ad026b2342f466cffd200140a0a95c9b64ae688331c52eb45", "text": "But surely it looks like might be easiest unless it has any downsides.\nThere wasn't a node update in this case---there was a control plane update which restarted the PD CSI driver, and it looks like the CSIDriver resource was updated or changed in some way which raced with the kube-controller-manager restart.\nIs there anyway we can know if the csi driver is up and running(like a health check ping) before populating DSW?\nWe use the CSINode registration to determine that. The discussion here I think is concluding that we should not use that as a criteria for adding the volume to DSW. We only need to check that CSI migration is enabled on the node.\n+1 we need to be very resilient against races, I think we have to assume a driver is in process of being installed at any point in the AD controller reconcilliation.\n/assign sunnylovestiramisu\nReproduced with the steps: In /var/log/kube-controller-\nTested with the and doing the reproduce steps above. The error of does not show up anymore. The error message still get logged in the kube-controller- for debugging purpose: Ran Ran On the GCP console, the disk is used by node: Ran I redeploy the pd-csi-driver and then make sure it is up and running. Ran", "commid": "kubernetes_issue_115297", "tokennum": 285}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a17f665f8d373d7b1270ad6d2270a2d2d077ee4c0ab30adb63d1585fe80a474f", "query": "<ins> /* Copyright 2023 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package topologymanager import ( \"k8s.io/api/core/v1\" \"k8s.io/kubernetes/pkg/kubelet/cm/containermap\" \"k8s.io/kubernetes/pkg/kubelet/lifecycle\" ) type noneScope struct { scope } // Ensure noneScope implements Scope interface var _ Scope = &noneScope{} // NewNoneScope returns a none scope. func NewNoneScope() Scope { return &noneScope{ scope{ name:             noneTopologyScope, podTopologyHints: podTopologyHints{}, policy:           NewNonePolicy(), podMap:           containermap.NewContainerMap(), }, } } func (s *noneScope) Admit(pod *v1.Pod) lifecycle.PodAdmitResult { return s.admitPolicyNone(pod) } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-4d10931e14d2065e9a15e6880eb555f03f2fd6b09352947daeddff0435b576bc", "text": "Follow up from: See details there. When is , there is no need to discover the NUMA topology. /sig node /priority backlog /kind feature /help-wanted\n/cc\n/triage accepted\nI would like to take this up also can I get more brief information about it? code review comments from asking that inside the NewManager() implementation, we need to skip NewPolicyOptions and NewNUMAInfo but when the NumaTopology comes kubelet issue also comes. I need some more information to start with this!\n/cc\nWhen there is no topology manger policy specified, NewManager should be a no-op. Just skip all checks.\nExactly. Just to add: we may need few iterations over the change to get a clean flow in the call.\n/assign", "commid": "kubernetes_issue_116391", "tokennum": 166}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a1be3c263fdb3d0d9c4f9204e7f5710c90807cf1bedc715d2fb3c95d7df79c62", "query": "assert.Equal(t, test.output, output) } } <del> func TestPodResourcesAreReclaimed(t *testing.T) { type args struct { pod           *v1.Pod status        v1.PodStatus runtimeStatus kubecontainer.PodStatus } tests := []struct { name string args args want bool }{ { \"pod with running containers\", args{ pod: &v1.Pod{}, status: v1.PodStatus{ ContainerStatuses: []v1.ContainerStatus{ runningState(\"containerA\"), runningState(\"containerB\"), }, }, }, false, }, { \"pod with containers in runtime cache\", args{ pod:    &v1.Pod{}, status: v1.PodStatus{}, runtimeStatus: kubecontainer.PodStatus{ ContainerStatuses: []*kubecontainer.ContainerStatus{ {}, }, }, }, false, }, { \"pod with sandbox present\", args{ pod:    &v1.Pod{}, status: v1.PodStatus{}, runtimeStatus: kubecontainer.PodStatus{ SandboxStatuses: []*runtimeapi.PodSandboxStatus{ {}, }, }, }, false, }, } testKubelet := newTestKubelet(t, false) defer testKubelet.Cleanup() kl := testKubelet.kubelet for _, tt := range tests { t.Run(tt.name, func(t *testing.T) { testKubelet.fakeRuntime.PodStatus = tt.args.runtimeStatus if got := kl.PodResourcesAreReclaimed(tt.args.pod, tt.args.status); got != tt.want { t.Errorf(\"PodResourcesAreReclaimed() = %v, want %v\", got, tt.want) } }) } } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-59e10ac9f842c5137d16434532387dd09ba10f619a9264b3e368e8bd51bb44b7", "text": "What happened: It's most visible in the test <img width=\"323\" alt=\"Screen Shot 2020-05-20 at 6 09 10 PM\" src=\"https://user-\"It shows up in kind, kube- and kops jobs The regression was introduced somewhere within , possible culprits are: (FYI (FYI (FYI There are more tests affected, just not as prominently (visually inspecting ) [sig-apps] StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications with PVCs [sig-apps] StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance] [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Inline-volume (default fs)] volumes should store data [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data I wasn't sure whether to tag this as kind/regression or not, I'll leave that up to or someone /sig node /sig api-machimery /sig scheduling\nThe label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : What happened: It's most visible in the test (FYI (FYI (FYI StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications with PVCs [sig-apps] StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance] [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Inline-volume (default fs)] volumes should store data [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data /sig api-machimery /sig scheduling 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.", "commid": "kubernetes_issue_91316", "tokennum": 506}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a1be3c263fdb3d0d9c4f9204e7f5710c90807cf1bedc715d2fb3c95d7df79c62", "query": "assert.Equal(t, test.output, output) } } <del> func TestPodResourcesAreReclaimed(t *testing.T) { type args struct { pod           *v1.Pod status        v1.PodStatus runtimeStatus kubecontainer.PodStatus } tests := []struct { name string args args want bool }{ { \"pod with running containers\", args{ pod: &v1.Pod{}, status: v1.PodStatus{ ContainerStatuses: []v1.ContainerStatus{ runningState(\"containerA\"), runningState(\"containerB\"), }, }, }, false, }, { \"pod with containers in runtime cache\", args{ pod:    &v1.Pod{}, status: v1.PodStatus{}, runtimeStatus: kubecontainer.PodStatus{ ContainerStatuses: []*kubecontainer.ContainerStatus{ {}, }, }, }, false, }, { \"pod with sandbox present\", args{ pod:    &v1.Pod{}, status: v1.PodStatus{}, runtimeStatus: kubecontainer.PodStatus{ SandboxStatuses: []*runtimeapi.PodSandboxStatus{ {}, }, }, }, false, }, } testKubelet := newTestKubelet(t, false) defer testKubelet.Cleanup() kl := testKubelet.kubelet for _, tt := range tests { t.Run(tt.name, func(t *testing.T) { testKubelet.fakeRuntime.PodStatus = tt.args.runtimeStatus if got := kl.PodResourcesAreReclaimed(tt.args.pod, tt.args.status); got != tt.want { t.Errorf(\"PodResourcesAreReclaimed() = %v, want %v\", got, tt.want) } }) } } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-aa1ca8a6c4f552108d5e4f5627cf5341a0bb7748f7b82e510f647cbc02b0a76b", "text": "</details\n/cc\nwill increase the time for deletion of pod and it should be expected because currently pod is deleted from apiserver before removing the sandbox container but after this fix pod will be deleted from the apiserver only after deleting the sandbox container.\n/remove-sig scheduling doesn't affect scheduling running time at all.\nYeah, is almost definitely the culprit. Last time we changed that code path, it also caused a regression. The degradation in performance is expected, but a 5x slowdown is definitely larger than it should be.\ndo we know if that's because the status used by the path is stale, or if removing sandboxes is actually that slow?\nif there's not a quick fix, should we revert and bring it back in once the root issue is understood?\nI think a revert is appropriate in this case.\nok, I'll open it\nopen at\nI agree with that 5x is something which shouldn't happen and i can take a look on why thats happening and that might require changing the way how the sandbox is currently deleted which is only during GC.", "commid": "kubernetes_issue_91316", "tokennum": 237}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a1c27088226a051543776b6c7b60f7faf877c7158cb6e4e6dba63772108d9c3f", "query": "echo -n Attempt \"$(($attempt+1))\" to check for SSH to master local output local ok=1 <del> output=$(ssh -oStrictHostKeyChecking=no -i \"${AWS_SSH_KEY}\" ubuntu@${KUBE_MASTER_IP} uptime 2> $LOG) || ok=0 </del> <ins> output=$(ssh -oStrictHostKeyChecking=no -i \"${AWS_SSH_KEY}\" ${SSH_USER}@${KUBE_MASTER_IP} uptime 2> $LOG) || ok=0 </ins> if [[ ${ok} == 0 ]]; then if (( attempt > 30 )); then echo", "positive_passages": [{"docid": "doc-en-kubernetes-7c0443d3746fe3757c9195c5c33416ecd39f97575569d1247bf005f30b3d366d", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: What happened: I visited the Kubernetes 1.11 release blog post and clicked on the link to the article on resizing persistent volumes. The server returned a 404. What you expected to happen: I expected to navigate to the article on resizing persistent volumes in Kubernetes. How to reproduce it (as minimally and precisely as possible): Visit the release announcement blog post (), scroll down to the \"4 Day Features Blog Series\" section, and click on the link to the article on resizing persistent volumes. Anything else we need to know?: The link currently points to: The correct link is: Environment: Kubernetes version (use ): N/A Cloud provider or hardware configuration: N/A OS (e.g. from /etc/os-release): N/A Kernel (e.g. ): N/A Install tools: N/A Others: N/A\nReiterating the mentions to trigger a notification: <detailsIn response to : <!-- This form is for bug reports and feature requests ONLY! --/kind bug /kind feature What happened: I visited the Kubernetes 1.11 release blog post and clicked on the link to the article on resizing persistent volumes. The server returned a 404. I expected to navigate to the article on resizing persistent volumes in Kubernetes. Visit the release announcement blog post (), scroll down to the \"4 Day Features Blog Series\" section, and click on the link to the article on resizing persistent volumes. The link currently points to: The correct link is: Kubernetes version (use ): N/A Cloud provider or hardware configuration: N/A OS (e.g. from /etc/os-release): N/A Kernel (e.g. ): N/A Install tools: N/A Others: N/A 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\nIt should be reported to kubernetes/website, but doesn't matter.", "commid": "kubernetes_issue_66944", "tokennum": 494}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a1e028e45bfa45e7706363df57647dc39fd2ce503cbddc406b56a5c23c96a89a", "query": "// Enable swagger api on master. components.KubeMaster.InstallSwaggerAPI() cluster := clientcmdapi.NewCluster() cluster.Server = components.ApiServer.URL cluster.InsecureSkipTLSVerify = true <ins> cfg.Contexts = map[string]*clientcmdapi.Context{\"test\": ctx} cfg.CurrentContext = \"test\" </ins> overrides := clientcmd.ConfigOverrides{ <del> ClusterInfo:    *cluster, Context:        *ctx, CurrentContext: \"test\", </del> <ins> ClusterInfo: *cluster, </ins> } cmdConfig := clientcmd.NewNonInteractiveClientConfig(*cfg, \"test\", &overrides, nil) factory := util.NewFactory(cmdConfig)", "positive_passages": [{"docid": "doc-en-kubernetes-f651131826f05881213cb9e37bd90a3c65eb2d3012bfdb53d9a39fc66f409d28", "text": "In 1.1, if you specify \"current-context: i-do-not-exist\" in a kubeconfig, and there's no matching context by that name in the contexts, kubelet silently uses what I assume is either an empty or a default configuration. This can result in hilarity like wondering why your kubelet isn't using the TLS settings you provided, and spending several hours debugging the whole stack only to discover that you typo'd current-context :). It would be better if kubelet and other users of errored out on such a misconfiguration, to make the failure obvious and trivial.\ncc\nI think kubelet silently uses an empty configuration. Guess we should give a waring here.\nDid you start to work on this?\nBelow is related code: can you confirm this? Besides if we want to log a waring in kubelet, we may need to get in kubelet.\ncc\ncc\nI believe kubelet already uses . Adding a check in that current context exists if specified sounds like the right approach.\nAre there any backwards compatibility implications here? would this break users who have existing configs (that fallback to default namespace)? , Jeff Lowdermilk wrote:\nI think kubelet directly use not . Also already checks whether the user-specified current context exists, the problem is that if not exist, we just skip. We need to do something if the current context not exist, like log a warning.\nErroring on a specified and bad seems reasonable. If it is not specified and there's only one option, I don't think we should fail.\nyeap, the case is that user specify the but not exist, in such case we should just fail.\nIf no one is working on this I can take it.\nI think this is the root cause. Basically we should error on this not exist context. If you have extra bandwidth, please go ahead :)\nThis is related to - the defaulting is what allows us to continue. When that merges, only kubectl will have the \"use localhost:8080\" as defaulting.", "commid": "kubernetes_issue_21062", "tokennum": 453}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a1e2e1f001285d227dd3f4a9f515b6d707b31ea87e1604cd5be04274137bc8c4", "query": "klog.Errorf(\"Unsupported protocol type: %s\", protocol) } if nodePortLocalSet != nil { <del> if valid := nodePortLocalSet.validateEntry(entry); !valid { klog.Errorf(\"%s\", fmt.Sprintf(EntryInvalidErr, entry, nodePortLocalSet.Name)) </del> <ins> entryInvalidErr := false for _, entry := range entries { if valid := nodePortLocalSet.validateEntry(entry); !valid { klog.Errorf(\"%s\", fmt.Sprintf(EntryInvalidErr, entry, nodePortLocalSet.Name)) entryInvalidErr = true break } nodePortLocalSet.activeEntries.Insert(entry.String()) } if entryInvalidErr { </ins> continue } <del> nodePortLocalSet.activeEntries.Insert(entry.String()) </del> } }", "positive_passages": [{"docid": "doc-en-kubernetes-dd58629e743b6e4eeaad6ce708921acac15734ca4e62ad8f92d2c296b406f940", "text": "What happened: SCTP nodeport service is not working for all IPs present in the node when ipvs is enabled. It is working only for node's InternalIP. What you expected to happen: SCTP nodeport service must work for all ips present in the node when ipvs is enabled. How to reproduce it (as minimally and precisely as possible): Create a kubernetes cluster with at least one node having multiple interfaces with different IPs. Start an SCTP server deployment. Then create a nodeport service for the same. Now try to reach the service using all the IPs present in that node. The service will be accessible only via node's InternalIP not any other IPs. Environment: Kubernetes version: v1.15.2 OS: ubuntu 18.04 Kernel: 4.15.0-54-generic Network plugin and version (if this is a network-related bug): ipset version v6.34\n/sig network /area kube-proxy /area ipvs\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/remove-triage unresolved", "commid": "kubernetes_issue_81474", "tokennum": 251}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a209490dbd9991254bb002ca22aa5e648bc9d54ccab63bb554259dcfca8490fd", "query": "return b } <del> // ResourceTypeOrNameArgs indicates that the builder should accept one or two arguments // of the form `(<type1>[,<type2>,...]|<type> <name>)`. When one argument is received, the types // provided will be retrieved from the server (and be comma delimited).  When two arguments are // received, they must be a single type and name. If more than two arguments are provided an // error is set. The allowEmptySelector permits to select all the resources (via Everything func). </del> <ins> // ResourceTypeOrNameArgs indicates that the builder should accept arguments // of the form `(<type1>[,<type2>,...]|<type> <name1>[,<name2>,...])`. When one argument is // received, the types provided will be retrieved from the server (and be comma delimited). // When two or more arguments are received, they must be a single type and resource name(s). // The allowEmptySelector permits to select all the resources (via Everything func). </ins> func (b *Builder) ResourceTypeOrNameArgs(allowEmptySelector bool, args ...string) *Builder { <del> switch len(args) { case 2: b.name = args[1] </del> <ins> switch { case len(args) > 2: b.names = append(b.names, args[1:]...) b.ResourceTypes(SplitResourceArgument(args[0])...) case len(args) == 2: b.names = append(b.names, args[1]) </ins> b.ResourceTypes(SplitResourceArgument(args[0])...) <del> case 1: </del> <ins> case len(args) == 1: </ins> b.ResourceTypes(SplitResourceArgument(args[0])...) if b.selector == nil && allowEmptySelector { b.selector = labels.Everything() } <del> case 0: </del> <ins> case len(args) == 0: </ins> default: b.errs = append(b.errs, fmt.Errorf(\"when passing arguments, must be resource or resource and name\")) }", "positive_passages": [{"docid": "doc-en-kubernetes-8781beaf9cecb5a2a5891763e358d97bbb8efac5ebba9fc986604965efa0dda5", "text": "Currently, it could not delete multiple pods at once, need to delete them one by one, it's very inconvenient if I have tons of pods to delete. Unlike docker, docker can multiple stop/rm containers/images at once.\nThis is possible using label selectors as of , which is better if you have tons of pods.\nI agree that using label selector is better to delete all of pods under the label. But to delete multile pods at once is still usable: I just want to delete 1/2 pods under the label, label selector will not work selector could not span over other selectors or pods Another reason is docker rm/stop x y z works, I will wonder why kubectl cannot. This is not urgent, but I hope it can be implemented.\nI agree. Thanks for the suggestion.\nWould this be a suitable task for someone new to k8s development? If so, I'd be willing to take a look at this, if someone could provide a couple of hints where to start.\nFurther to my last message, I have a functional work in progress I would like to share, if anyone is interested?\nPRs are welcome. See\nYes, this is a reasonable place to start. Since its in the client, you won't get much orientation to the core server code, but it will be a good place to orient to the client side API. There us also prior art that you can model off of. The kubectl create ... command already supports multiple resources. A good command to adapter would be the 'label' command. You can find it in Many thanks in advance! Brendan On Feb 19, 2015 8:21 AM, \"Eric Tune\" wrote:", "commid": "kubernetes_issue_3050", "tokennum": 364}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a214aa178f8b771b96976633ed66db162d781e78ad065de0d71ac3bd8053469b", "query": "Expect(err).NotTo(HaveOccurred(), \"error failing a daemon pod\") err = wait.PollImmediate(dsRetryPeriod, dsRetryTimeout, checkRunningOnAllNodes(f, ds)) Expect(err).NotTo(HaveOccurred(), \"error waiting for daemon pod to revive\") <ins> By(\"Wait for the failed daemon pod to be completely deleted.\") err = wait.PollImmediate(dsRetryPeriod, dsRetryTimeout, waitFailedDaemonPodDeleted(c, &pod)) Expect(err).NotTo(HaveOccurred(), \"error waiting for the failed daemon pod to be completely deleted\") </ins> }) // This test should not be added to conformance. We will consider deprecating OnDelete when the", "positive_passages": [{"docid": "doc-en-kubernetes-da00f1cf1a24475bca3717ed24d8bd1cf5079c51cd54d6d4d01b160ed7cae851", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: DaemonSet has an e2e test running that has dubious purpose. What you expected to happen: The e2e test should be refactored and commented clearer as it will be part of the conformance.\nTo elaborate, we're concerned that the following may not actually ensure that DaemonSet recreates Failed Pods: For example, it seems possible that the Node might simply overwrite the Pod status with its own information if it hasn't yet seen the change to the Phase. Ideally, we should verify that the Pod UID we force to Failed no longer shows up in the DaemonSet's list of Pods after the DaemonSet becomes happy again.", "commid": "kubernetes_issue_59076", "tokennum": 150}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a22daa94ea0c204ac857019f7acce1bdbc0beefbde890538eaaad7ac6143ce99", "query": "}, expectErr: false, }, <ins> // IPVS Timeout can be 0 { config: kubeproxyconfig.KubeProxyIPVSConfiguration{ SyncPeriod:    metav1.Duration{Duration: 5 * time.Second}, TCPTimeout:    metav1.Duration{Duration: 0 * time.Second}, TCPFinTimeout: metav1.Duration{Duration: 0 * time.Second}, UDPTimeout:    metav1.Duration{Duration: 0 * time.Second}, }, expectErr: false, }, // IPVS Timeout > 0 { config: kubeproxyconfig.KubeProxyIPVSConfiguration{ SyncPeriod:    metav1.Duration{Duration: 5 * time.Second}, TCPTimeout:    metav1.Duration{Duration: 1 * time.Second}, TCPFinTimeout: metav1.Duration{Duration: 2 * time.Second}, UDPTimeout:    metav1.Duration{Duration: 3 * time.Second}, }, expectErr: false, }, // TCPTimeout Timeout < 0 { config: kubeproxyconfig.KubeProxyIPVSConfiguration{ SyncPeriod: metav1.Duration{Duration: 5 * time.Second}, TCPTimeout: metav1.Duration{Duration: -1 * time.Second}, }, expectErr: true, reason:    \"TCPTimeout must be greater than or equal to 0\", }, // TCPFinTimeout Timeout < 0 { config: kubeproxyconfig.KubeProxyIPVSConfiguration{ SyncPeriod:    metav1.Duration{Duration: 5 * time.Second}, TCPFinTimeout: metav1.Duration{Duration: -1 * time.Second}, }, expectErr: true, reason:    \"TCPFinTimeout must be greater than or equal to 0\", }, // UDPTimeout Timeout < 0 { config: kubeproxyconfig.KubeProxyIPVSConfiguration{ SyncPeriod: metav1.Duration{Duration: 5 * time.Second}, UDPTimeout: metav1.Duration{Duration: -1 * time.Second}, }, expectErr: true, reason:    \"UDPTimeout must be greater than or equal to 0\", }, </ins> } for _, test := range testCases {", "positive_passages": [{"docid": "doc-en-kubernetes-be027d483b5644a511b34dd42acd191f0a8a8265cd239e919307434a4dbdd401", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: kube-proxy doesn't validate the configurable IPVS tcp, tcpfin and udp timeouts. For example, when kube-proxy starts with , it will always log a warning: . What you expected to happen: kube-proxy should validate --ipvs-tcp-timeout, --ipvs-tcpfin-timeout, --ipvs-udp-timeout flag values at start. How to reproduce it (as minimally and precisely as possible): add flags to kube-proxy Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig network /area ipvs\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d", "commid": "kubernetes_issue_88656", "tokennum": 269}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a23b20b0a17c704d46dd45ea45eb59ba8b69bf430355b035d90dda341b4bfc68", "query": "}, }, }, <del> map[string]interface{}{\"field\": \"foo\"}, }, true}, </del> <ins> failingObjects: []interface{}{map[string]interface{}{\"field\": \"foo\"}}, }, </ins> } for _, tt := range tests { t.Run(tt.name, func(t *testing.T) { <del> validator, _, err := NewSchemaValidator(&apiextensions.CustomResourceValidation{OpenAPIV3Schema: &tt.args.schema}) </del> <ins> validator, _, err := NewSchemaValidator(&apiextensions.CustomResourceValidation{OpenAPIV3Schema: &tt.schema}) </ins> if err != nil { t.Fatal(err) } <del> if err := ValidateCustomResource(tt.args.object, validator); (err != nil) != tt.wantErr { if err == nil { t.Error(\"expected error, but didn't get one\") } else { t.Errorf(\"unexpected validation error: %v\", err) </del> <ins> for _, obj := range tt.objects { if err := ValidateCustomResource(obj, validator); err != nil { t.Errorf(\"unexpected validation error for %v: %v\", obj, err) } } for _, obj := range tt.failingObjects { if err := ValidateCustomResource(obj, validator); err == nil { t.Errorf(\"missing error for %v\", obj) </ins> } } })", "positive_passages": [{"docid": "doc-en-kubernetes-42eca355948acd2923f06d9ab50c5116c5afebe4d73334e949a0d732f7352d29", "text": "The server-side validation does not check the type of values with . Create a CRD like: Then create a CR: It is not rejected, but should because must not be a boolean.", "commid": "kubernetes_issue_78817", "tokennum": 40}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a26e1c704819c66bc05353aae69c0cc074075daf98a731ac845cfdff285249b3", "query": "CSI: &v1.CSIPersistentVolumeSource{ Driver:           AzureDiskDriverName, VolumeHandle:     azureSource.DataDiskURI, <del> ReadOnly:         *azureSource.ReadOnly, FSType:           *azureSource.FSType, </del> VolumeAttributes: map[string]string{azureDiskKind: \"Managed\"}, }, }, AccessModes: []v1.PersistentVolumeAccessMode{v1.ReadWriteOnce}, }, } <ins> if azureSource.ReadOnly != nil { pv.Spec.PersistentVolumeSource.CSI.ReadOnly = *azureSource.ReadOnly } </ins> <del> if *azureSource.CachingMode != \"\" { </del> <ins> if azureSource.CachingMode != nil && *azureSource.CachingMode != \"\" { </ins> pv.Spec.PersistentVolumeSource.CSI.VolumeAttributes[azureDiskCachingMode] = string(*azureSource.CachingMode) } <del> if *azureSource.FSType != \"\" { </del> <ins> if azureSource.FSType != nil { pv.Spec.PersistentVolumeSource.CSI.FSType = *azureSource.FSType </ins> pv.Spec.PersistentVolumeSource.CSI.VolumeAttributes[azureDiskFSType] = *azureSource.FSType } if azureSource.Kind != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-ec905797ef340d09da7d9d2e34a2767d786c5cb37de40d4b7cae6a294742089b", "text": "What happened: Some of the Azure CSI translation checks in and needs to perform NPE checks for pointer based fields as pointed out in and What you expected to happen: NPE checks should be there How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.15 Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/assign\n/sig storage\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten\n/priority critical-urgent", "commid": "kubernetes_issue_78524", "tokennum": 277}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a29f0fd0b6aed058b0bc2782346bfc8471d0ad238fa1d4a687719eab985a60d2", "query": "// Volume is added to asw. Because attach operation fails, volume should not be reported as attached to the node. waitForVolumeAddedToNode(t, generatedVolumeName, nodeName1, asw) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateUncertain, asw) <del> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, false, asw) </del> <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, false, asw, volumeAttachedCheckTimeout) </ins> // When volume is added to the node, it is set to mounted by default. Then the status will be updated by checking node status VolumeInUse. // Without this, the delete operation will be delayed due to mounted status", "positive_passages": [{"docid": "doc-en-kubernetes-dc8aac09a0e4bb26f9dc5f50aef7f845ea9d7c4b925d34b9f6eda044925f80f5", "text": "TestRunOneVolumeDetachFailNodeWithReadWriteOnce 4 times since 03-19 23:00 PDT, intermittently ! https://k8s- Still investigating whether this is a tolerable flake or not with more history than testgrid view, or otherwise would appreciate input from anyone with expertise in this test, especially as regards to whether this should be a blocker for tomorrows beta cut. maybe: /sig storage /sig testing\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nis already open for this, looks like it is attempting to fix it\nthank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. /close\nClosing this issue. <detailsIn response to : thank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. 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", "commid": "kubernetes_issue_116774", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a29f0fd0b6aed058b0bc2782346bfc8471d0ad238fa1d4a687719eab985a60d2", "query": "// Volume is added to asw. Because attach operation fails, volume should not be reported as attached to the node. waitForVolumeAddedToNode(t, generatedVolumeName, nodeName1, asw) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateUncertain, asw) <del> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, false, asw) </del> <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, false, asw, volumeAttachedCheckTimeout) </ins> // When volume is added to the node, it is set to mounted by default. Then the status will be updated by checking node status VolumeInUse. // Without this, the delete operation will be delayed due to mounted status", "positive_passages": [{"docid": "doc-en-kubernetes-aef7ec00dc93616f97177ca3d23f28217445848b34c429e5746962ea28329f43", "text": "pull-kubernetes-unit TestRunOneVolumeDetachFailNodeWithReadWriteOnce Jan 7th, 2022 Check volume <fake-plugin/volume-nameis reported as attached to node <fail-detach-node, got false, expected true No response_ /sig storage\n/cc\nthis is the top unit test flake according to\ncc\nThe 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]:\nI think this test is no longer flaky by checking the test grid, close it now.\nUnfortunately this does still seem to be flaky: Here was the output from : /reopen\nReopened this issue. <detailsIn response to : Unfortunately this does still seem to be flaky: 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\n/remove-lifecycle stale\nstill the case\nHow about adding some logging to help troubleshoot this? I looked at it a little, but it is hard to tell which part of the test is failing. PR\n/\nThis is still happening\n/triage accepted\nFrom the logs, in the OneVolumeDetachFailNodeWithReadWriteOnce test, succeeded, but the next verification failed. In verifyVolumeAttachedToNode, the attachState is from calling and within asw, it calls . In verifyVolumeReportedAsAttachedToNode, the volumes are obtained from calling , it seems that the node is not in asw.nodesToUpdateStatusFor at this step. Cannot reproduce locally. I tried to run the test 100 times locally with debug.Stack()... 3 * 100 times all passed.\nTried to run stress test on my linux machine as well but still cannot reproduce. Command: Result: Also tried running n process in parallel. Command: Result:\nIt seems like it happens more frequently.", "commid": "kubernetes_issue_107414", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a29f0fd0b6aed058b0bc2782346bfc8471d0ad238fa1d4a687719eab985a60d2", "query": "// Volume is added to asw. Because attach operation fails, volume should not be reported as attached to the node. waitForVolumeAddedToNode(t, generatedVolumeName, nodeName1, asw) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateUncertain, asw) <del> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, false, asw) </del> <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, false, asw, volumeAttachedCheckTimeout) </ins> // When volume is added to the node, it is set to mounted by default. Then the status will be updated by checking node status VolumeInUse. // Without this, the delete operation will be delayed due to mounted status", "positive_passages": [{"docid": "doc-en-kubernetes-62e47fd83b7fc1cc39259be1688a9f133b9cd2dc48247eb5d858fae7fd13955b", "text": "But I may have no time to dig into the cause. Let's see.\ncc as the test author.\nThe problem is that this test has a lot of dependency on the sleeps that are hardcoded with a very narrow scope, but our CI seems to be able to stress it much more. As soon as you slightly change one of the sleep duration it starts to flake locally The test can not make an assumption that timing is perfect, even more in the sub second range can someone in sig-storage review this test and make it less dependant on those tight sleeps?\nAccording to most failures, it failed at Line 660. Let me run some stress locally. with 250ms sleep with 100ms sleep\nI agree this test case is too brittle due to its specific timing dependencies. To fix this, I suggest reworking the test case to: 1) Add retry with timeout to wait for final conditions 2) Remove the intermediate timing-based state transition checks. Instead, we can keep track of state transitions in the Fakes and validate those stats. wdyt?\nFriendly ping from 1.27 CI Signal that this test is still a noisy flake on the master-blocking dashboard as CI Signal has flagged it in and", "commid": "kubernetes_issue_107414", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a2b6b55667915031196503afc2ed8aab70a8d6d06638bf406b4c5ca34ce96307", "query": "func FilterActivePods(pods []api.Pod) []*api.Pod { var result []*api.Pod for i := range pods { <del> if api.PodSucceeded != pods[i].Status.Phase && api.PodFailed != pods[i].Status.Phase && pods[i].DeletionTimestamp == nil { result = append(result, &pods[i]) </del> <ins> p := pods[i] if api.PodSucceeded != p.Status.Phase && api.PodFailed != p.Status.Phase && p.DeletionTimestamp == nil { result = append(result, &p) } else { glog.V(4).Infof(\"Ignoring inactive pod %v/%v in state %v, deletion time %v\", p.Namespace, p.Name, p.Status.Phase, p.DeletionTimestamp) </ins> } } return result } <ins> // SyncAllPodsWithStore lists all pods and inserts them into the given store. // Though this function is written in a generic manner, it is only used by the // controllers for a specific purpose, to synchronously populate the store // with the first batch of pods that would otherwise be sent by the Informer. // Doing this avoids more complicated forms of synchronization with the // Informer, though it also means that the controller calling this function // will receive \"OnUpdate\" events for all the pods in the store, instead of // \"OnAdd\". This should be ok, since most controllers are level triggered // and make decisions based on the contents of the store. // // TODO: Extend this logic to load arbitrary local state for the controllers // instead of just pods. func SyncAllPodsWithStore(kubeClient client.Interface, store cache.Store) { var allPods *api.PodList var err error listOptions := api.ListOptions{LabelSelector: labels.Everything(), FieldSelector: fields.Everything()} for { if allPods, err = kubeClient.Pods(api.NamespaceAll).List(listOptions); err != nil { glog.Warningf(\"Retrying pod list: %v\", err) continue } break } pods := []interface{}{} for i := range allPods.Items { p := allPods.Items[i] glog.V(4).Infof(\"Initializing store with pod %v/%v\", p.Namespace, p.Name) pods = append(pods, &p) } store.Replace(pods, allPods.ResourceVersion) return } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-b0a441a371f8db864bebc11c7303837af71a86244bb0f50ec81fe1d8a09d5c71", "text": "The test is in flaky suite and no one seems to care. We need an owner for this test. cc Last failure log:\ndo you think you can take a look at this?\nThis is happening because of a bad assumption. The assumption is: if the reflector's store is consistent with etcd, the store given back to clients of the framework.Controller is too. I'd really like a general fix applicable to all controllers for this problem, but fixing it just for the RCs is pretty easy. In more detail: This function reports when the reflector has listed from apiserver. But the store given to the reflector is the fifo of the framework.Controller. The store given back to the caller is still not consistent, and will not be till the framework.Controller puts all the objects from the fifo into the client state store (). The rc specific fix: Before starting the rc manager, seed the expectations store with an expectation like {rc:foo, adds: foo.Status.Replicas, deletes:0}. This will wait for status.Replicas number of ADD events till a timeout. The general fix: Somehow expose this through framework.Controller.HasSynced (clients don't care about the fifo anyway, shouldn't it just be an implementation detail?) ideas? cc'ing people who have written controllers that might be interested I don't think this (and generally anything flaky for 1 release) is a p0, I can fix it if you don't mind dealing with the flakes till I've cleared things off my plate. I'd be more than happy to review a fix.\nWell, it's a P0 because test is flaky. E.g last run:\n- did you have chance to look into it?\nThe \"DaemonRestart\" tests are still labeled at . I will send a PR to promote them.\nare you still planning to send aPR to promote the DaemonRestart tests out of flaky? I think this is the right thing to do.\nAck; sorry, I lost this in the muck.", "commid": "kubernetes_issue_17829", "tokennum": 444}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a2df3fb8e50ced712520a3f56e222d8fa123c6ce62c43cd52fee14d43f624e86", "query": "<del> /* Copyright 2015 Google Inc. All rights reserved. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ // Tests for liveness probes, both with http and with docker exec. // These tests use the descriptions in examples/liveness to create test pods. package e2e import ( \"time\" \"github.com/GoogleCloudPlatform/kubernetes/pkg/api\" \"github.com/GoogleCloudPlatform/kubernetes/pkg/client\" \"github.com/GoogleCloudPlatform/kubernetes/pkg/util\" \"github.com/golang/glog\" . \"github.com/onsi/ginkgo\" . \"github.com/onsi/gomega\" ) func runLivenessTest(c *client.Client, podDescr *api.Pod) bool { ns := \"e2e-test-\" + string(util.NewUUID()) glog.Infof(\"Creating pod %s in namespace %s\", podDescr.Name, ns) _, err := c.Pods(ns).Create(podDescr) if err != nil { glog.Infof(\"Failed to create pod %s: %v\", podDescr.Name, err) return false } // At the end of the test, clean up by removing the pod. defer c.Pods(ns).Delete(podDescr.Name) // Wait until the pod is not pending. (Here we need to check for something other than // 'Pending' other than checking for 'Running', since when failures occur, we go to // 'Terminated' which can cause indefinite blocking.) err = waitForPodNotPending(c, ns, podDescr.Name, 60*time.Second) if err != nil { glog.Infof(\"Failed to start pod %s in namespace %s: %v\", podDescr.Name, ns, err) return false } glog.Infof(\"Started pod %s in namespace %s\", podDescr.Name, ns) // Check the pod's current state and verify that restartCount is present. pod, err := c.Pods(ns).Get(podDescr.Name) if err != nil { glog.Errorf(\"Get pod %s in namespace %s failed: %v\", podDescr.Name, ns, err) return false } initialRestartCount := pod.Status.Info[\"liveness\"].RestartCount glog.Infof(\"Initial restart count of pod %s is %d\", podDescr.Name, initialRestartCount) // Wait for at most 48 * 5 = 240s = 4 minutes until restartCount is incremented for i := 0; i < 48; i++ { // Wait until restartCount is incremented. time.Sleep(5 * time.Second) pod, err = c.Pods(ns).Get(podDescr.Name) if err != nil { glog.Errorf(\"Get pod %s failed: %v\", podDescr.Name, err) return false } restartCount := pod.Status.Info[\"liveness\"].RestartCount glog.Infof(\"Restart count of pod %s in namespace %s is now %d\", podDescr.Name, ns, restartCount) if restartCount > initialRestartCount { glog.Infof(\"Restart count of pod %s in namespace %s increased from %d to %d during the test\", podDescr.Name, ns, initialRestartCount, restartCount) return true } } glog.Errorf(\"Did not see the restart count of pod %s in namespace %s increase from %d during the test\", podDescr.Name, ns, initialRestartCount) return false } // TestLivenessHttp tests restarts with a /healthz http liveness probe. func TestLivenessHttp(c *client.Client) bool { return runLivenessTest(c, &api.Pod{ ObjectMeta: api.ObjectMeta{ Name:   \"liveness-http\", Labels: map[string]string{\"test\": \"liveness\"}, }, Spec: api.PodSpec{ Containers: []api.Container{ { Name:    \"liveness\", Image:   \"kubernetes/liveness\", Command: []string{\"/server\"}, LivenessProbe: &api.Probe{ Handler: api.Handler{ HTTPGet: &api.HTTPGetAction{ Path: \"/healthz\", Port: util.NewIntOrStringFromInt(8080), }, }, InitialDelaySeconds: 15, }, }, }, }, }) } // TestLivenessExec tests restarts with a docker exec \"cat /tmp/health\" liveness probe. func TestLivenessExec(c *client.Client) bool { return runLivenessTest(c, &api.Pod{ ObjectMeta: api.ObjectMeta{ Name:   \"liveness-exec\", Labels: map[string]string{\"test\": \"liveness\"}, }, Spec: api.PodSpec{ Containers: []api.Container{ { Name:    \"liveness\", Image:   \"busybox\", Command: []string{\"/bin/sh\", \"-c\", \"echo ok >/tmp/health; sleep 10; echo fail >/tmp/health; sleep 600\"}, LivenessProbe: &api.Probe{ Handler: api.Handler{ Exec: &api.ExecAction{ Command: []string{\"cat\", \"/tmp/health\"}, }, }, InitialDelaySeconds: 15, }, }, }, }, }) } var _ = Describe(\"TestLivenessHttp\", func() { It(\"should pass\", func() { c, err := loadClient() Expect(err).NotTo(HaveOccurred()) Expect(TestLivenessHttp(c)).To(BeTrue()) }) }) var _ = Describe(\"TestLivenessExec\", func() { It(\"should pass\", func() { c, err := loadClient() Expect(err).NotTo(HaveOccurred()) Expect(TestLivenessExec(c)).To(BeTrue()) }) }) </del>", "positive_passages": [{"docid": "doc-en-kubernetes-563adcd071a3c6fe544aec5f1bf507590a5c621259a5e37f4edab1ba22b77da9", "text": "Park of ginkgo-ization\nPer IRC, is working on this\nPushed an update yesterday to address comments.\nwhat's the status of this? There's an issue open to de-flake this test (), but it's tough to do that if the code is in the middle of being moved to ginkgo.\nThis has been merged.", "commid": "kubernetes_issue_4253", "tokennum": 76}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a3542af8c701543a3992b139ee67543d6f012ba6a20cda3b4877dc6c6fd5fe94", "query": "} // Write stores the given \"val\" in CycleState with the given \"key\". <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Write(key StateKey, val StateData) { <ins> c.mx.Lock() </ins> c.storage[key] = val <ins> c.mx.Unlock() </ins> } // Delete deletes data with the given key from CycleState. <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Delete(key StateKey) { <del> delete(c.storage, key) } // Lock acquires CycleState lock. func (c *CycleState) Lock() { </del> c.mx.Lock() <del> } // Unlock releases CycleState lock. func (c *CycleState) Unlock() { </del> <ins> delete(c.storage, key) </ins> c.mx.Unlock() } <del> // RLock acquires CycleState read lock. func (c *CycleState) RLock() { c.mx.RLock() } // RUnlock releases CycleState read lock. func (c *CycleState) RUnlock() { c.mx.RUnlock() } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-43588246e28947764a0f8a5c9c5b1d76a5819a8eaa1c439f79abd429269822c0", "text": "What happened: kube-scheduler () crashes due to a panic while running : The race condition is triggered when an out-of-tree plugin, that writes to during its Filter phase, is registered through . Access to in general happens from a single goroutine and there are no practical concurrency issues, with the exception of the phase, that parallelizes calls for each node across plugins: A quick glance at the tip of the branch seems to indicate the bug is still present there. What you expected to happen: Ideally access to should be synchronized everywhere for correctness, including by all in-tree plugins, since there are no guarantees about how will call multiple plugins concurrently. It seems to me it is something that was considered at some point, given that has methods. Sadly, almost no in-tree plugins are synchronizing access. For now, I will try to work around the problem by doing a single write to during and storing a data bag structure where I will write state into during (with proper synchronization), instead of writing to directly. How to reproduce it (as minimally and precisely as possible): Install a scheduler plugin that writes to during its phase. In-tree (builtin) plugins are not synchronizing their access to . Environment: Kubernetes version (use ): v1.18.8 Cloud provider or hardware configuration: linux-amd64 (AWS) OS (e.g: ): Ubuntu 18.04.5 LTS (Bionic Beaver) Others: custom kube-scheduler binary built with an out-of-tree plugin using\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scheduling\nAFAICT all in-tree plugins write to the cycle state in PreFilter and then only read from cycle state in Filter. So this shouldn't be a problem with in-tree plugins as concurrent read access should be fine during RunFilterPlugins. But since your out-of-tree plugin writes in Filter, I can see why this can be a problem.", "commid": "kubernetes_issue_95887", "tokennum": 515}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a3542af8c701543a3992b139ee67543d6f012ba6a20cda3b4877dc6c6fd5fe94", "query": "} // Write stores the given \"val\" in CycleState with the given \"key\". <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Write(key StateKey, val StateData) { <ins> c.mx.Lock() </ins> c.storage[key] = val <ins> c.mx.Unlock() </ins> } // Delete deletes data with the given key from CycleState. <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Delete(key StateKey) { <del> delete(c.storage, key) } // Lock acquires CycleState lock. func (c *CycleState) Lock() { </del> c.mx.Lock() <del> } // Unlock releases CycleState lock. func (c *CycleState) Unlock() { </del> <ins> delete(c.storage, key) </ins> c.mx.Unlock() } <del> // RLock acquires CycleState read lock. func (c *CycleState) RLock() { c.mx.RLock() } // RUnlock releases CycleState read lock. func (c *CycleState) RUnlock() { c.mx.RUnlock() } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-278036efba637c2a6a49330142a64ca8f7b65a0d21755fde24824f9c473a00c9", "text": "Aside from adding Lock/Unlock in in-tree plugin, offering mutual exclusion on each key as a built-in feature within CycleState could be an alternative solution. This way, reads from in-tree plugins during Filter wouldn't interfere with writes during Filter from out-of-tree plugins.\ncc\nshould we change the Read/Write CycleState methods to be thread safe?\nAdding locks without a proper justification would just increase the latency. could you clarify your use case? Why do you need to write anything during Filter?\nyeah, we should measure it, but I don't expect it to have significant effect...\nAdding locks without a proper justification would just increase the latency. Without contention (which is the case with in-tree plugins), I don't think this is a concern.\nAdapting source from : source: essentially, 11.3 ns/Lock-Unlock pair\nI remember locks showing up in profiling for PreScore/Score for certain plugins. Although I have to admit that the accesses were not properly implemented. I'd like to hear an answer for before doing any experiments.\n+1 to that I'd also like to understand the motivations / requirements of mutating CycleState in Filter().\nMy particular use-case is that we have resources being dynamically to/removed from Nodes, and those resources need to be allocated (and tracked) in the scheduling loop. Technically I could pre-compute all the available dynamic resources for all Nodes at the phase, and snapshot it, but that would require me to pre-compute everything for all Nodes on all scheduling cycles. Instead, what I'm currently doing is computing what dynamic resources can be utilized on-demand during the phase (kind of a lazy loading of dynamic resources for each pair), and saving state of what extra resources were considered during for each Node that was evaluated. Then, later in the scheduler plugin can lock-in the exact dynamic resources for the particular Node that was selected. I understand the concern with adding extra synchronization overhead without a real need. Even if my use-case is not good enough to justify it, there is another argument for it: technically, the lack of access synchronization on violates the . Even if in the end we decide synchronizing all access is not worth the overhead (for correctness), I would strongly encourage better documentation saying which plugin phases are allowed to modify , and perhaps even forcing a snapshot-read-only copy of to be used by plugins.\nUsing the scheduler to track resources is not a good idea.", "commid": "kubernetes_issue_95887", "tokennum": 539}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a3542af8c701543a3992b139ee67543d6f012ba6a20cda3b4877dc6c6fd5fe94", "query": "} // Write stores the given \"val\" in CycleState with the given \"key\". <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Write(key StateKey, val StateData) { <ins> c.mx.Lock() </ins> c.storage[key] = val <ins> c.mx.Unlock() </ins> } // Delete deletes data with the given key from CycleState. <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Delete(key StateKey) { <del> delete(c.storage, key) } // Lock acquires CycleState lock. func (c *CycleState) Lock() { </del> c.mx.Lock() <del> } // Unlock releases CycleState lock. func (c *CycleState) Unlock() { </del> <ins> delete(c.storage, key) </ins> c.mx.Unlock() } <del> // RLock acquires CycleState read lock. func (c *CycleState) RLock() { c.mx.RLock() } // RUnlock releases CycleState read lock. func (c *CycleState) RUnlock() { c.mx.RUnlock() } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-b826aaa34ec054d9cc587ce8587a04002d4daa70694ce73071b413f1bf7ba0c6", "text": "The scheduler should be stateless. Can't you track the resources with an external controller or with a device plugin and making it part of the Node spec?\nthere may be some misunderstanding in my poor choice of words. What I mean by \"tracking\" is that the scheduler needs to track usage and availability of these extra per-Node resources, to be able to allocate them during placement/scheduling. Exactly the same it does with volumes, cpus, memory, ephemeral disk, etc Doing computations in a controller outside of the scheduling loop would be similar to \"precomputing\" these resources. In my particular use case I chose a different way because: introduces another point of failure, if the external controller stops pre-computing extra resources and publishing them somewhere (CRD, Node spec, etc) scheduling halts (at least scheduling on these extra resources) Node resources in my use case are volatile (they are coming and going frequently), and the extra latency by an extra controller (vs doing all computations right in the scheduling loop) may be problematic for my use case. Even if you consider my use case not enough to add proper synchronization to , I'd still encourage making it explicit what scheduling phases are allowed to modify it (and even passing in a snapshot read-only version of to phases that are not expected to update it), to avoid confusion and race conditions.\nOk, if you are not tracking the existence of resources in the scheduler, I wouldn't suggest the external controller. Still, have you considered the device plugin framework? That way, the default kube-scheduler could keep track of resources usage. Otherwise, I still don't see why you would need to update the CycleState during Filter. As its name indicates, CycleState only lives during a scheduling cycle.\nRegardless of the correctness of usage of CycleState to do what wants, I still think we need to do at least one of the following: that writing to CycleState during Filter will lead to data races, a read-only CycleState to Filter plugins (whether we do this at the interface level or if we simply drop Write requests during Filter is an implementation detail), or make CycleState concurrency safe CycleState as it exists right now allows plugin authors to shoot themselves in the foot IMO.\nI'm leaning towards 1, but it's fair to continue the discussion before deciding.\nCan you run the \"controller\" as a goroutine along with your scheduler plugin?", "commid": "kubernetes_issue_95887", "tokennum": 520}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a3542af8c701543a3992b139ee67543d6f012ba6a20cda3b4877dc6c6fd5fe94", "query": "} // Write stores the given \"val\" in CycleState with the given \"key\". <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Write(key StateKey, val StateData) { <ins> c.mx.Lock() </ins> c.storage[key] = val <ins> c.mx.Unlock() </ins> } // Delete deletes data with the given key from CycleState. <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Delete(key StateKey) { <del> delete(c.storage, key) } // Lock acquires CycleState lock. func (c *CycleState) Lock() { </del> c.mx.Lock() <del> } // Unlock releases CycleState lock. func (c *CycleState) Unlock() { </del> <ins> delete(c.storage, key) </ins> c.mx.Unlock() } <del> // RLock acquires CycleState read lock. func (c *CycleState) RLock() { c.mx.RLock() } // RUnlock releases CycleState read lock. func (c *CycleState) RUnlock() { c.mx.RUnlock() } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-038a628d524f09c8393af798b6053a1fded9e84e2c01785ad258fb86c8d6d618", "text": "So it's not an external controller binary, and hence don't introduce another point of failure. It's pretty like how the default scheduler manages its internal cache. But note that cache is only needed when you need a more efficient data structure. If a {key:value} map is good enough, spinning up a XYZInformer and obtain the latest XYZ resource on-demand is the most recommended way. I think it quite depends on how you design the internal XYZ cache. For example, it should only tweak the cache in an incremental manner - in other words, unchanged resource will be kept unmodified. You can check out the \"doubly-pointer snapshot\" of scheduler's cache. With above said, if I understand your case correctly, you may need to build a sophisticated XYZ cache, which runs in a separate goroutine and responds to your XYZ resource changes. And then upon each scheduling cycle, take a snapshot (may needs a specific snapshotting algorithm) in PreFilter() and WRITE to CycleState, and then in Filter() READ from CycleState. My personal option is to suggest all plugin developers to read from CycleState in Filter().\nnailed it. What you describe is almost exactly what I\u2019m doing today. There are some details particular to my use case (e.g. just tracking current state with an informer and an incremental cache is not enough, because there\u2019s some logic involved in deciding if currently available resources are usable by each pair, and I currently do that computation in as pairs are evaluated). In any case, I just wanted to share my use case to provide some color, but I don\u2019t want what I\u2019m doing distracting us from the more important questions, mentioned by above. My personal preference would be as a very short term next step, then when someone has cycles to do it. I would be OK with punting on until a more strong need shows up.\nNote that limiting to only reading from works for me, as long as I can still read my own data structure from it and do writes on it (i.e. don\u2019t deepclone for the phase).\nalso adds overhead (from copying the state, which can be very expensive).\nCould implement just by changing the interface passed to (e.g. ). That wouldn\u2019t be backwards compatible, but very cheap.", "commid": "kubernetes_issue_95887", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a3542af8c701543a3992b139ee67543d6f012ba6a20cda3b4877dc6c6fd5fe94", "query": "} // Write stores the given \"val\" in CycleState with the given \"key\". <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Write(key StateKey, val StateData) { <ins> c.mx.Lock() </ins> c.storage[key] = val <ins> c.mx.Unlock() </ins> } // Delete deletes data with the given key from CycleState. <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Delete(key StateKey) { <del> delete(c.storage, key) } // Lock acquires CycleState lock. func (c *CycleState) Lock() { </del> c.mx.Lock() <del> } // Unlock releases CycleState lock. func (c *CycleState) Unlock() { </del> <ins> delete(c.storage, key) </ins> c.mx.Unlock() } <del> // RLock acquires CycleState read lock. func (c *CycleState) RLock() { c.mx.RLock() } // RUnlock releases CycleState read lock. func (c *CycleState) RUnlock() { c.mx.RUnlock() } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-73e2408e2bea0ec3fe3177e8a87291d57a052eb7c05f546c204ec27aefee3293", "text": "I guess that would work in the sense that you cannot change the high level values of the CycleState map, but you could still override what's inside them, if they have pointers. But maybe that's ok.\nbut you could still override what's inside them, if they have pointers. But maybe that's ok. yeah, if it was pointers and if the underlying data needed to be modified, I'd imagine it would have its own Lock/Unlock semantics\nfor such implementation, the only remaining concern is backwards compatibility. So I would leave that decision to who leads the scheduling-plugins repo.\nI rethink 's original problem a little bit: the original racing issue occurs when reading CycleState in in-tree plugins, this indicates one of the (out-of-tree) plugins is (over)writing the most high-level value of the CycleState map. But if we control the locking inside the out-of-tree plugin, and mutate that particular in-place, that would be good enough? Case 3 in the above program demonstrates the correct way to manipulate the specific out-of-tree state. Let me know your thoughts. If it resolves 's concern, we don't need to make any change on the Filter() interface.\nCase 3 is how I am working around the problem today to avoid the race. I write a \"data bag\" once into top level in , then only modify my own inner structure (with proper locking) in , without doing any further modifications to directly (top level) in . That is acceptable, but I'd encourage you to consider making the interface (and documentation) more explicit for plugins, so they avoid the mistake of writing directly into . Without changing anything (no documentation, no readonly interface), it is pretty easy for a plugin to use in a way that you don't want to support.\nThanks for confirming that. Yes, documenting it, or(and) publishing examples would be quite helpful to clarify the semantics. As a wrap-up: a keyed value can be read from CycleState, literally , in any phase. It's always race-free.", "commid": "kubernetes_issue_95887", "tokennum": 455}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a3542af8c701543a3992b139ee67543d6f012ba6a20cda3b4877dc6c6fd5fe94", "query": "} // Write stores the given \"val\" in CycleState with the given \"key\". <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Write(key StateKey, val StateData) { <ins> c.mx.Lock() </ins> c.storage[key] = val <ins> c.mx.Unlock() </ins> } // Delete deletes data with the given key from CycleState. <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Delete(key StateKey) { <del> delete(c.storage, key) } // Lock acquires CycleState lock. func (c *CycleState) Lock() { </del> c.mx.Lock() <del> } // Unlock releases CycleState lock. func (c *CycleState) Unlock() { </del> <ins> delete(c.storage, key) </ins> c.mx.Unlock() } <del> // RLock acquires CycleState read lock. func (c *CycleState) RLock() { c.mx.RLock() } // RUnlock releases CycleState read lock. func (c *CycleState) RUnlock() { c.mx.RUnlock() } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-3be32b87589c297c7c2842b086ef786e82de3563d7c057c1ca18b1f858ccd170", "text": "if you want to mutate the top-level keyed value in CycleState, if it's a phase that CycleState is accessed consecutively, such as PreFilter, PreScore, it's safe to mutate CycleState in any manner if it's a phase that CycleState is accessed parallelly, to be race-free, (for now) you only have 1 option: keep the keyed value's pointer unchanged, and use an internal lock to mutate that pointer obj [TBD] we may come up with changes to add read locks to all in-tree plugins when reading values from CycleState, so that the out-of-tree plugin can surround its mutating logic between and - th mutating logic thereby can be any style Any thoughts on the TBD item? I would assume read locks wouldn't cost too much.\nFor now, I think the documentation is correct, it clearly says Read() and Write() are not thread-safe: The key thing here is whether in-tree plugin should use RLock/RUnlock or not. If yes, out-of-tree plugins can be freed to use Lock/Unlock. (see the TBD item in the previous comment)\nI like the TBD, and optimizing for correctness in how in-tree plugins are accessing . I understand the concern with synchronization overhead, but I would be really surprised if it is the bottleneck in scheduling code.\nIt can be, when you have 5k-nodes clusters, or bigger.\nI don't think it will be expensive, a rlock should be equivalent to an atomic add operation (basically it increments the number of readers). As a comparison, looking up the state from the map is likely to be more expensive.\nOf course we are assuming no contention in the default plugins.\nThis is my impression as well. A vanilla version of scheduler doesn't impose write lock in Filter() and Score(), so should be good.\nWe can always see with the benchmarks and revert if its not negligible.\nI will run the benchmarks to see if there is perf downgrade. /assign\nIssues 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\n/remove-lifecycle stale This is still relevant, yes?", "commid": "kubernetes_issue_95887", "tokennum": 535}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a3542af8c701543a3992b139ee67543d6f012ba6a20cda3b4877dc6c6fd5fe94", "query": "} // Write stores the given \"val\" in CycleState with the given \"key\". <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Write(key StateKey, val StateData) { <ins> c.mx.Lock() </ins> c.storage[key] = val <ins> c.mx.Unlock() </ins> } // Delete deletes data with the given key from CycleState. <del> // This function is not thread safe. In multi-threaded code, lock should be // acquired first. </del> <ins> // This function is thread safe by acquiring an internal lock first. </ins> func (c *CycleState) Delete(key StateKey) { <del> delete(c.storage, key) } // Lock acquires CycleState lock. func (c *CycleState) Lock() { </del> c.mx.Lock() <del> } // Unlock releases CycleState lock. func (c *CycleState) Unlock() { </del> <ins> delete(c.storage, key) </ins> c.mx.Unlock() } <del> // RLock acquires CycleState read lock. func (c *CycleState) RLock() { c.mx.RLock() } // RUnlock releases CycleState read lock. func (c *CycleState) RUnlock() { c.mx.RUnlock() } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-bcac7b47c31a3bdcd9ddd71bfacab7dca4a98e08ad1188f8a89f61b6d0a63d38", "text": "IIUC the volumebinding plugin has been fixed, but external plugins can still shoot themselves in the foot.\n/priority backlog\nYes. I'm working on this, late this week I will send out a PR along with perf test result.", "commid": "kubernetes_issue_95887", "tokennum": 53}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a35e2f6d2278a3d4338b67f593ae860d215763fd0fd83cb1828782d189d661f4", "query": "creationTimestamp: null labels: kubernetes.io/bootstrapping: rbac-defaults <del> name: system:csi-external-attacher rules: - apiGroups: - \"\" resources: - persistentvolumes verbs: - get - list - patch - update - watch - apiGroups: - \"\" resources: - nodes verbs: - get - list - watch - apiGroups: - storage.k8s.io resources: - volumeattachments verbs: - get - list - patch - update - watch - apiGroups: - \"\" resources: - events verbs: - create - get - list - patch - update - watch - apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: annotations: rbac.authorization.kubernetes.io/autoupdate: \"true\" creationTimestamp: null labels: kubernetes.io/bootstrapping: rbac-defaults name: system:csi-external-provisioner rules: - apiGroups: - \"\" resources: - persistentvolumes verbs: - create - delete - get - list - watch - apiGroups: - \"\" resources: - persistentvolumeclaims verbs: - get - list - patch - update - watch - apiGroups: - storage.k8s.io resources: - storageclasses verbs: - list - watch - apiGroups: - \"\" resources: - events verbs: - create - get - list - patch - update - watch - apiGroups: - \"\" resources: - nodes verbs: - get - list - watch - apiGroups: - storage.k8s.io resources: - csinodes verbs: - get - list - watch - apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: annotations: rbac.authorization.kubernetes.io/autoupdate: \"true\" creationTimestamp: null labels: kubernetes.io/bootstrapping: rbac-defaults </del> name: system:discovery rules: - nonResourceURLs:", "positive_passages": [{"docid": "doc-en-kubernetes-083944d00199b655f25fb35f51e7ea3786d4181f487cac5cdbda9f2140ce4497", "text": "<!-- Please only use this template for submitting enhancement requests --The built-in and cluster roles here are deprecated in 1.13 when this issue was resolved: /sig storage /milestone v1.17 /priorit important-longterm\nYou must be a member of the GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility. <detailsIn response to : <!-- Please only use this template for submitting enhancement requests -- /milestone v1.17 /priorit important-longterm 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\n/cc /priority important-longterm\nIssues 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\n/remove-lifecycle stale /assign\nBug triage for 1.17 here with a gentle reminder that code freeze for this release is on November 14. Is this issue still intended for 1.17?", "commid": "kubernetes_issue_78739", "tokennum": 293}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a39cc3ab0b3c6533e0d5ae41a116f8db22fed924febaec5332c7512948eb1b39", "query": "\"//staging/src/k8s.io/apimachinery/pkg/util/wait:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/watch:go_default_library\", \"//staging/src/k8s.io/apiserver/pkg/util/feature:go_default_library\", <ins> \"//staging/src/k8s.io/client-go/dynamic:go_default_library\", </ins> \"//staging/src/k8s.io/client-go/kubernetes:go_default_library\", \"//staging/src/k8s.io/client-go/tools/cache:go_default_library\", \"//staging/src/k8s.io/client-go/tools/watch:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-a4e08d4660e59e77b869eee3e8c161e5e01175b90d68e1077fd3e84d4f4d567b", "text": "[x] Original approval issue: - Reverted due to flakes [x] Two weeks soak end date: 20 November 2020 This issue is created to allow edit by /wip /hold According to this APIsnoop query, there are still some remaining Pod endpoints which are untested. a Pod with a static label the Pod with a new Label and updated data the Pod to ensure it's patched the Pod's status the Pod's status Ready condition to False the Pod's status to check if Ready is False all Pods in all Namespaces find the Pod(1) ensure that the Pod is found and is patched Namespaced Pod(1) via a Collection with a LabelSelector the Pod to check that it's deleted Discover useragents: List endpoints hit by the test: Display endpoint coverage change: If a test with these calls gets merged, test coverage will go up by 4 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance\n/reopen Test PR Merge Promotion PR to be created next\nReopened this issue. <detailsIn response to : /reopen Test PR Merge Promotion PR to be created next 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\nreverted by due to flaky test\nIssues 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\n/remove-lifecycle stale\n/reopen PR on test grid for 2 weeks before promotion to conformance\nReopened this issue. <detailsIn response to : /reopen PR on test grid for 2 weeks before promotion to conformance 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\n/triage accepted", "commid": "kubernetes_issue_90936", "tokennum": 449}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a3ed6a2f28d1ce850d761442170dc51e3e527fbc10b354b6a44639196574966d", "query": "func (s *sourceFile) processEvent(e *inotify.Event) error { // Ignore file start with dots <del> if strings.HasPrefix(e.Name, \".\") { </del> <ins> if strings.HasPrefix(filepath.Base(e.Name), \".\") { </ins> glog.V(4).Infof(\"Ignored pod manifest: %s, because it starts with dots\", e.Name) return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-9100812604bb274f029e79ebee13bfe2ce369a45e8a3a70a5fa62bc6c27fbac5", "text": "<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.--Is this a request for help? No What keywords did you search in Kubernetes issues before filing this one? static manifest Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug report Kubernetes version (use ): Environment: Cloud provider or hardware configuration: Bare metal and reproduced in Vagrant OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: custom scratch install and reproduced with kubeadm Others: Calico for networking. Used (Also able to reproduce without calico) What happened: Modified one of the static manifest files in . The kubelet killed the running pod and did NOT create a new pod. (waited 30 minutes, still no pod) What you expected to happen: Kubelet should have killed the pod and started a new one. How to reproduce it (as minimally and precisely as possible): Started with single node, vanilla Ubuntu Xenial, installed kubernetes via kubeadm, nothing special. Modify , for example change the logging level or even just whitespace at the end of the file. Observe the kubelet kill the controller manager pod, and does not restart it. Anything else we need to know: If I remove the file from the directory, and then replace the file, kubelet will start it up. Kubelet logs from the period where I updated the file:\nDid you modify the yaml file using an editor (e.g., vim)? If the editor creates a temporary file in the same directory, kubelet can get confused and thinking that's a new pod (with the same name & namespace). When the temporary file gets removed, kubelet'd inadvertently delete the pod from its cache. Since kubelet relies on inotify for changes, if it doesn't get notified for any new changes from the original yaml file, it'd forever ignore the pod. There is an issue open to add periodic listing in addition to inotify (introduced in 1.5). This would make sure kubelet eventually recover from the situation. I can't find the issue, but there is another one for inotify: . Another fix is to make sure kubelet ignore such known temporary files (it already ignores files starting with ). In general, don't edit the file directly.", "commid": "kubernetes_issue_44450", "tokennum": 525}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a3ed6a2f28d1ce850d761442170dc51e3e527fbc10b354b6a44639196574966d", "query": "func (s *sourceFile) processEvent(e *inotify.Event) error { // Ignore file start with dots <del> if strings.HasPrefix(e.Name, \".\") { </del> <ins> if strings.HasPrefix(filepath.Base(e.Name), \".\") { </ins> glog.V(4).Infof(\"Ignored pod manifest: %s, because it starts with dots\", e.Name) return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-0117d4a9a190c22a46ca0d65f470fd275b0d70394b42857314fa11d87e816ed2", "text": "Copy the file to another place, edit, and copy it back to the manifests directory.\nI'm seeing a similar problem except I never edited the file, might be fit for a separate issue\nYes I was using vim, and this explanation makes sense. Would be nice if it was smart about it. Would a PR to ignore the vim temp file be acceptable\nI think it's reasonable. I doubt if anyone uses those file names on purpose.\nThe dot ignore should have covered the vim temp file too, but it doesn't work because the filename passed in is the absolute filename including the path. So the first character is not a dot. I'll try to submit a PR fix.\nPR submitted\nfixed?\nHow to work around? I coudn't start api server when using kubeadm to deploy k8s. Thanks!", "commid": "kubernetes_issue_44450", "tokennum": 180}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a40216cdead09cc699620e52cf17038828aa969465664589af69a56a033aaa42", "query": "return nil, err } defer os.RemoveAll(tmpDir) <del> out, err := exec.Command(\"nice\", \"-n\", \"19\", \"du\", \"-s\", \"-B\", \"1\", tmpDir).CombinedOutput() </del> <ins> out, err := exec.Command(\"nice\", \"-n\", \"19\", \"du\", \"-x\", \"-s\", \"-B\", \"1\", tmpDir).CombinedOutput() </ins> if err != nil { return nil, fmt.Errorf(\"failed command 'du' on %s with error %v\", tmpDir, err) }", "positive_passages": [{"docid": "doc-en-kubernetes-1983b5ea5659683f3a4ba96803f2792373389d2c0ef10ffa2f957e3f76064a9d", "text": "I'm using K8S 1.10 and have a specific use case where I'm trying to use an emptyDir to share mounts between two containers in a pod. I'm using the MountPropagation feature successfully, but while debugging another issue I noticed that the node was running a very long running du command. Looking into the source I noted: Which runs du on any emptyDir, do measure disk usage. I recommend that in this case we should add the -x flag that will skip any mounted directories as they do not count against the file usage and would make these scans a lot faster. I could of course add a simple pull request for this but first wanted to see if this was known and on purpose. To reproduce bind mount/loop mount/device mount any large/slow directory into an emptyDir volume and watch as the du process slogs away Environment: Kubernetes 1.10 GKE <!-- DO NOT EDIT BELOW THIS LINE --/kind bug\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI think it makes sense to ignore submounts.\nIssues 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\n/remove-lifecycle stale\nIssues 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\ndo you still want to submit a PR to fix this? Thanks!\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_71012", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a40216cdead09cc699620e52cf17038828aa969465664589af69a56a033aaa42", "query": "return nil, err } defer os.RemoveAll(tmpDir) <del> out, err := exec.Command(\"nice\", \"-n\", \"19\", \"du\", \"-s\", \"-B\", \"1\", tmpDir).CombinedOutput() </del> <ins> out, err := exec.Command(\"nice\", \"-n\", \"19\", \"du\", \"-x\", \"-s\", \"-B\", \"1\", tmpDir).CombinedOutput() </ins> if err != nil { return nil, fmt.Errorf(\"failed command 'du' on %s with error %v\", tmpDir, err) }", "positive_passages": [{"docid": "doc-en-kubernetes-eea01b18436aabcf24011fc8d3531d9a102c009dd1b30b027c1434bcedaabd88", "text": "/lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nClosing 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", "commid": "kubernetes_issue_71012", "tokennum": 120}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a4183fa66f98b6732082303e9c067fb3222a6ce06f424aa792ab7f109d5d10e3", "query": "restful \"github.com/emicklei/go-restful\" cadvisorapi \"github.com/google/cadvisor/info/v1\" <ins> \"github.com/pkg/errors\" </ins> \"k8s.io/klog\" \"k8s.io/api/core/v1\"", "positive_passages": [{"docid": "doc-en-kubernetes-2d86227263004d2306fadc99355cf0a88aac1d38d7e2576116201cd81e3141b9", "text": "What happened: In handler#handleSummary, return value from request.Request.ParseForm() is ignored. What you expected to happen: The error return should be checked.\n/sig node\nHi this seems to be easy to fix. Could I solve this?\nPlease go ahead.", "commid": "kubernetes_issue_90085", "tokennum": 62}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a41a8a1855b1e266eefe75bf8d12fcd40452e568666db14cb2cc5961333e6e39", "query": "\"//federation/apis/federation:go_default_library\", \"//pkg/api:go_default_library\", \"//vendor/k8s.io/apimachinery/pkg/apis/meta/v1:go_default_library\", <ins> \"//vendor/k8s.io/apimachinery/pkg/util/validation/field:go_default_library\", </ins> ], )", "positive_passages": [{"docid": "doc-en-kubernetes-9ef34f91f24cf25c8ee57899ba28766272335d7f286e3495efa44b9480fef2d3", "text": "Right now it is possible to add a cluster for which it won't be possible to create a client. For example client-related code does: while validation checks only: cc:\nswitching this to 1.6 as it's too late for 1.5. ok? (please switch it right back if you disagree)\nNot a release blocker for 1.7.\nare you interested in fixing this?\nof course, will do that.\n[MILESTONENOTIFIER] Milestone Removed Important: This issue was missing labels required for the v1.8 milestone for more than 7 days: kind: Must specify exactly one of [, , ]. priority: Must specify exactly one of [, , ]. Removing it from the milestone. <detailsAdditional instructions available <a href=\"\"here</aThe commands available for adding these labels are documented <a href=\"\"here</a</details", "commid": "kubernetes_issue_29911", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a44e0f4084835fb01bc7a089a822fcb44a953d3a0bf70c73df5fe749905c355c", "query": "}, }, }, <del> }) </del> <ins> }, true) }) It(\"should *not* be restarted with a docker exec \"cat /tmp/health\" liveness probe\", func() { runLivenessTest(c, &api.Pod{ ObjectMeta: api.ObjectMeta{ Name:   \"liveness-exec\", Labels: map[string]string{\"test\": \"liveness\"}, }, Spec: api.PodSpec{ Containers: []api.Container{ { Name:    \"liveness\", Image:   \"gcr.io/google_containers/busybox\", Command: []string{\"/bin/sh\", \"-c\", \"echo ok >/tmp/health; sleep 600\"}, LivenessProbe: &api.Probe{ Handler: api.Handler{ Exec: &api.ExecAction{ Command: []string{\"cat\", \"/tmp/health\"}, }, }, InitialDelaySeconds: 15, }, }, }, }, }, false) </ins> }) It(\"should be restarted with a /healthz http liveness probe\", func() {", "positive_passages": [{"docid": "doc-en-kubernetes-65bf469670180d69e57fdc1a820a8f2f435cec685a9975e90f226dd126851fba", "text": "As far as I can tell, container liveness probes of type exec flat out don't work against clusters built at head. I had the kubelet always log the output of the exec'ed command, and it's always empty no matter what I exec, causing the probe to fail since it requires the output to be equal to the string \"ok\". If you want to test it, try adding a liveness probe of this form to any container: I also tried these lovely forms, to more closely match the liveness example under examples/: On the plus side, this may be an opportunistic time to switch over to\nThe reason that the e2e test for exec liveness probes hasn't caught this is that it only tests that containers are restarted when they fail liveness probes. It doesn't test that containers aren't restarted when their liveness checks should be succeeding. The e2e test's exec'ed commands also only ever produced empty output, rather than the expected \"fail\" output.\nIs it possible to include this in a new pre-release, since it fixes a bug in health checking? I see it merged in master and I'm wondering what the policy is of releasing new code in a separate (0.16.*) release.", "commid": "kubernetes_issue_7618", "tokennum": 275}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a44f6cb5e869eccf248b8ac505e27244011ef25c2c80e1233583629299af7a4f", "query": "`service`, a client can simply connect to $MYAPP_SERVICE_HOST on port $MYAPP_SERVICE_PORT. <ins> ## Service without selector Services, in addition to providing clean abstraction to access pods, can also abstract any kind of backend: - you want to have an external database cluster in production, but in test you use your own databases. - you want to point your service to a service in another [`namespace`](namespaces.md) or on another cluster. - you are migrating your workload to Kubernetes and some of your backends run outside of Kubernetes. In any of these scenarios you can define a service without a selector: ```json \"kind\": \"Service\", \"apiVersion\": \"v1beta1\", \"id\": \"myapp\", \"port\": 8765 ``` then you can explicitly map the service to a specific endpoint(s): ```json \"kind\": \"Endpoints\", \"apiVersion\": \"v1beta1\", \"id\": \"myapp\", \"endpoints\": [\"173.194.112.206:80\"] ``` Access to the service without a selector works the same as if it had selector. The traffic will be routed to endpoints defined by the user (`173.194.112.206:80` in case of this example). </ins> ## How do they work? Each node in a Kubernetes cluster runs a `service proxy`.  This application", "positive_passages": [{"docid": "doc-en-kubernetes-e28bd845629ca30049478b8fcedafd43696075613f16aad0ce76758069ac8ba0", "text": "For example, kubernetes-ro service appears with empty selector (this service was created by the hack/local cluster) - is that ok? What meaning such service has if it has no entity to fwd traffic to?\nkubernetes and kubernetes-ro are currently \"virtual\" - they are not backed by running pods, but by the master itself. , abonas wrote:\nif that's internal impl, why is it exposed to user? let's say a client pulls all entities and builds a UI around it. then a service with no selector arrives, and it's internal to kube - how the client should know not to present it/touch it? (similar to the \"net\" container in pods)\nIt's exposed exactly FOR users - so they can find the apiserver. It has a corresponding Endpoints object, it gets a portal IP and a kube-proxy rule, and it gets service env vars and a DNS name. The fact that it is virtual is an implementation detail. That it exists is all users should need to know. , abonas wrote:\nAnd FWIW, the master components may one day actually be pods... , Tim Hockin wrote:\nthanks for the explanation. so any general rule how to distinguish kube pods/services from user defined?\nDo we need to distinguish them? We could add labels, I guess, if it is really important to distinguish them.\nsometimes users would want to see only the things they defined and not implementation details of the system.\nOne could argue this is why the users should be using labels. I'm not against defining labels for \"special\" stuff, but it's new territory, so we should enter with caution. , abonas wrote:\nI think the right answer might be to put them in a special \"cluster\" or \"system\" namespace. , Tim Hockin wrote:\nSee If we put them in a \"kubernetes\" ns, the DNS name would be :) I'm not against segmenting them into a different namespace. We just need to decide on what that namespace is called, plumb through that configuration, decide on compatibility for a short while or not, and decide if that namespace is \"special\" or just \"different\" - i.e. should the skydns, heapster, etc pods go into this namespace? , Brendan Burns wrote:\nAs said, the services are there for applications that need to contact the apiserver.", "commid": "kubernetes_issue_3712", "tokennum": 524}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a44f6cb5e869eccf248b8ac505e27244011ef25c2c80e1233583629299af7a4f", "query": "`service`, a client can simply connect to $MYAPP_SERVICE_HOST on port $MYAPP_SERVICE_PORT. <ins> ## Service without selector Services, in addition to providing clean abstraction to access pods, can also abstract any kind of backend: - you want to have an external database cluster in production, but in test you use your own databases. - you want to point your service to a service in another [`namespace`](namespaces.md) or on another cluster. - you are migrating your workload to Kubernetes and some of your backends run outside of Kubernetes. In any of these scenarios you can define a service without a selector: ```json \"kind\": \"Service\", \"apiVersion\": \"v1beta1\", \"id\": \"myapp\", \"port\": 8765 ``` then you can explicitly map the service to a specific endpoint(s): ```json \"kind\": \"Endpoints\", \"apiVersion\": \"v1beta1\", \"id\": \"myapp\", \"endpoints\": [\"173.194.112.206:80\"] ``` Access to the service without a selector works the same as if it had selector. The traffic will be routed to endpoints defined by the user (`173.194.112.206:80` in case of this example). </ins> ## How do they work? Each node in a Kubernetes cluster runs a `service proxy`.  This application", "positive_passages": [{"docid": "doc-en-kubernetes-d870c86aebdf975c7f742c9ae5f4b46feed435261a0bfef8e8c1547e324212d5", "text": "Additionally, nil selectors can be used by users to import external services. Adding labels to the kubernetes services won't help. Users need to manage their objects using labels. /cc\nYeah, lots of consumers will expose \"special\" services. IN fact, in many clusters the \"special\" services will outweigh the unspecial ones. At this point, the namespace they are in is completely arbitrary, and I think because it is a name, it should be free for the end user to choose where they are surfaced.\nPer the proposal here: , I think the namespace should continue to hold these services, and they require no special labels. I sense comment is made without thinking through what Kubernetes operators do to bootstrap a cluster. I think it's reasonable that namespace holds everything you need to run, and operators may or may not choose to segment their data in other namespaces. If they want to not see this information, its an exact reason for why they should use their own namespace. I don't think we need anything new here.\n- I'm not clear on your meaning. Did you mean that we should make the \"cluster admin\" namespace a config param that everyone knows about and can be different cluster-to-cluster? Or did you mean that default is as arbitrary a name as any other? I'd be fine moving things out of default into \"kube\" or \"kubernetes\" or \"cluster\" or something, but I am less convinced that a flag is a good thing. , Clayton Coleman wrote:\n- wherever we stick this stuff, it should be the namespace that is initially bootstrapped, which today is . I continue to believe that is as good a name as any other. I do not see a need to do more here.\nI think as soon as you bring naming into the picture, making decisions based on names gets very tricky (what if I want my logging service to be everywhere?). If there is a magic namespace that exposes things to the rest of the cluster, we should ask whether there's only one magic namespace, or multiple? Are services supposed to cross namespaces? It's great that pods can find the master... but that's not the only thing they'll need to find in each namespace. And baking in special names (or customizable names) into your app code is fragile, because then your code only works inside Kubernetes.", "commid": "kubernetes_issue_3712", "tokennum": 523}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a44f6cb5e869eccf248b8ac505e27244011ef25c2c80e1233583629299af7a4f", "query": "`service`, a client can simply connect to $MYAPP_SERVICE_HOST on port $MYAPP_SERVICE_PORT. <ins> ## Service without selector Services, in addition to providing clean abstraction to access pods, can also abstract any kind of backend: - you want to have an external database cluster in production, but in test you use your own databases. - you want to point your service to a service in another [`namespace`](namespaces.md) or on another cluster. - you are migrating your workload to Kubernetes and some of your backends run outside of Kubernetes. In any of these scenarios you can define a service without a selector: ```json \"kind\": \"Service\", \"apiVersion\": \"v1beta1\", \"id\": \"myapp\", \"port\": 8765 ``` then you can explicitly map the service to a specific endpoint(s): ```json \"kind\": \"Endpoints\", \"apiVersion\": \"v1beta1\", \"id\": \"myapp\", \"endpoints\": [\"173.194.112.206:80\"] ``` Access to the service without a selector works the same as if it had selector. The traffic will be routed to endpoints defined by the user (`173.194.112.206:80` in case of this example). </ins> ## How do they work? Each node in a Kubernetes cluster runs a `service proxy`.  This application", "positive_passages": [{"docid": "doc-en-kubernetes-19a1388f52e9d713eb0f4efe1574687db54358876426fa8c067da9ba3c2f2fbb", "text": "I'm just trying to pump the brakes on special services prior to us designing them... :) ----- Original Message -----\noh, to be clear, I don't want \"special\" services - I am merely asking if moving non-user-defined objects (where that is defined very loosely) out of \"default\" is worthwhile. I tend to agree with Derek that it's not worth energy. , Clayton Coleman wrote:\nagree with you that lots of consumers will expose \"special\" services We should not use the (namespace + k8s-service + skydns) mechanism for publishing the location of those special services. We should decouple the choice of namespace to run the pods of the service in from the well-known dns address of special services. Otherwise, it will be hard to move the pods of the service to another namespace, which people will definitely want to do as they grow. Instead, we need a place to publish well-known services which is not tied to the namespace of the pods of that service.\nyou open a whole new topic. I've noodled with the idea of a Name resource type. We would generate a Name for each Service as \"service.namespace\", but users could also add their own Name resources. , Eric Tune wrote:\nI'd like to understand better your comment regarding nil selectors used to export external services - can you elaborate? give an example? my understanding is that service redirects traffic to pods based on labels. with nil selector service does nothing, so why is it a service in the first place? I'm pro decoupling special services/internal implementation services from user defined entities. whether by separate namespace, or by saying that the default namespace is reserved, or by any other solution. because otherwise internal implementation and user defined content are mixed and that's no good for a proper management. just tagging you so you could see this issue and the related discussions.\nServices abstract backends - they don't have to abstract pods. Some examples: You want to have an external database cluster in production, but in test you use your own databases. You would have a service for both and use the environment variables, but the production service has a nil selector with its endpoints set to the database cluster. You want to have an empty service because you're reserving a name (that isn't accessible yet) but will be in the future You want to point your service to a service in another namespace or on another cluster.", "commid": "kubernetes_issue_3712", "tokennum": 535}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a44f6cb5e869eccf248b8ac505e27244011ef25c2c80e1233583629299af7a4f", "query": "`service`, a client can simply connect to $MYAPP_SERVICE_HOST on port $MYAPP_SERVICE_PORT. <ins> ## Service without selector Services, in addition to providing clean abstraction to access pods, can also abstract any kind of backend: - you want to have an external database cluster in production, but in test you use your own databases. - you want to point your service to a service in another [`namespace`](namespaces.md) or on another cluster. - you are migrating your workload to Kubernetes and some of your backends run outside of Kubernetes. In any of these scenarios you can define a service without a selector: ```json \"kind\": \"Service\", \"apiVersion\": \"v1beta1\", \"id\": \"myapp\", \"port\": 8765 ``` then you can explicitly map the service to a specific endpoint(s): ```json \"kind\": \"Endpoints\", \"apiVersion\": \"v1beta1\", \"id\": \"myapp\", \"endpoints\": [\"173.194.112.206:80\"] ``` Access to the service without a selector works the same as if it had selector. The traffic will be routed to endpoints defined by the user (`173.194.112.206:80` in case of this example). </ins> ## How do they work? Each node in a Kubernetes cluster runs a `service proxy`.  This application", "positive_passages": [{"docid": "doc-en-kubernetes-1ddfea6d99e7ccf8c03b659f81beb02dd771f14183ebec47ce91a7703edcbce2", "text": "You set the endpoints for your service to the publicIPs of the other service. ----- Original Message -----\n, thanks. regarding the last point - I was under impression (based on some other discussion) that there would not be cross namespace interaction? that entities can can access only entities in the same namespace?\nCross-namespace is currently allowed and I think has to be allowed, though perhaps (in the fullness of time) that can be policy based rather than wide open. , abonas wrote:\nplease see this correspondence. my understanding is that there is isolation\nResponded there. I think there's some less-than-crystal-clear words in play. , abonas wrote:\n+1 to Eric's comment about ensuring there is a consistent manner for system services like kubernetes-ro, if that's not fixes for all clusters it's going to be a nightmare to write reusable containers for multiple different clusters. I don't care if we do that by using a constant namespace, or by giving system services two different names, but there needs to be at least one name that is constant. Regarding default vs. cluster namespace, I think the issue is one of clutter as a user is starting to understand k8s, you turn up a new cluster, launch a pod, or service, and it's hard to find your one object on the sea of system created pods and services. It's visual clutter that confuses people as they onboard. On Jan 23, 2015 3:01 PM, \"Tim Hockin\" wrote:\n- can you drop me a line (my github name at google) - I want to ask you something, and you have no contact info :) , abonas wrote:\nsorry for naive question but why would I care as an user that wants to run its existing workload on Kubernetes about kubernetes-ro ? If I write an application that uses kubernetes-ro then I'm locked into Kubernetes. I understand the need for kubernetes-ro being accessible by cluster level services such as monitoring, logging. I also can imagine that a power user might want to start its own cluster services that use kubernetes-ro. I don't see clearly why would majority of users care about kubernetes-ro being visible from their container.", "commid": "kubernetes_issue_3712", "tokennum": 504}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a44f6cb5e869eccf248b8ac505e27244011ef25c2c80e1233583629299af7a4f", "query": "`service`, a client can simply connect to $MYAPP_SERVICE_HOST on port $MYAPP_SERVICE_PORT. <ins> ## Service without selector Services, in addition to providing clean abstraction to access pods, can also abstract any kind of backend: - you want to have an external database cluster in production, but in test you use your own databases. - you want to point your service to a service in another [`namespace`](namespaces.md) or on another cluster. - you are migrating your workload to Kubernetes and some of your backends run outside of Kubernetes. In any of these scenarios you can define a service without a selector: ```json \"kind\": \"Service\", \"apiVersion\": \"v1beta1\", \"id\": \"myapp\", \"port\": 8765 ``` then you can explicitly map the service to a specific endpoint(s): ```json \"kind\": \"Endpoints\", \"apiVersion\": \"v1beta1\", \"id\": \"myapp\", \"endpoints\": [\"173.194.112.206:80\"] ``` Access to the service without a selector works the same as if it had selector. The traffic will be routed to endpoints defined by the user (`173.194.112.206:80` in case of this example). </ins> ## How do they work? Each node in a Kubernetes cluster runs a `service proxy`.  This application", "positive_passages": [{"docid": "doc-en-kubernetes-f742a948ec6f92870d242caf8e3787bfcbe2f4250e3c7f0a894622bd17960df0", "text": "I see a reason for the cluster services being visible and accessible for Kubernetes developer, but from an user perspective such services only make the system more complex: why do I see these services (pods,rc) ? are they related to my application ? should I care about them (especially when I use hosted Kubernetes) ? why does my container get all these environment variables for cluster services ?\nI will update file to explain why one would have service without a selector.\nRight now, every service goes everywhere for simplicity. Name spacing and filtering probably make sense in the long run, but it's not a high priority for v1.0 Brendan On Mar 4, 2015 5:02 AM, \"Rafa\u0142 Soko\u0142owski\" wrote:", "commid": "kubernetes_issue_3712", "tokennum": 155}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a466b9e63c540584048e9bacc1300b9f74afd17d614bd11edff383774d1ea5f2", "query": "if plug.GetPluginName() != \"testPlugin\" { t.Errorf(\"Wrong name: %s\", plug.GetPluginName()) } <ins> plug, err = vpm.FindPluginBySpec(nil) if err == nil { t.Errorf(\"Should return error if volume spec is nil\") } volumeSpec := &Spec{} plug, err = vpm.FindPluginBySpec(volumeSpec) if err != nil { t.Errorf(\"Should return test plugin if volume spec is not nil\") } </ins> } func Test_ValidatePodTemplate(t *testing.T) {", "positive_passages": [{"docid": "doc-en-kubernetes-4cf2bcce2d9cf8bfbc9f2302c057ef4fa219c655a3340b1abe23f2bb07c57620", "text": "In volume management code, VolumeSpec is firstly needed to find the volume plugin. After the volume plugin is found, VolumeSpec is again used to attach or mount or check volume is still attached or not. This information is reconstructed during controller failure. The assumptions used here are If pod still exists, VolumeSpec should be reconstructed when controller is restarted. However, as discover from this bug, it might not be true if PVC is deleted in the meantime because pod only has PVC information and requires to use PVC to get PV information. By fixing Issue , we could fix this problem.If pod is already deleted, VolumeSpec is not really needed for detaching. But before detaching finishes, syncState loop might check this volume's attachement status and will use VolumeSpec during checking. One safe guard we can put here is to fail FindAttachablePluginBySpec if spec is nil. This function is used by multiple places such as attachdetachcontroller, desiredstateofworld, and actualstateofworld, oeperation_generator etc. Instead of adding nil check many places, I feel FindAttachablePluginBySpec or even better FindPluginBySpec (is called by FindAttachablePluginBySpec and other places). Open an issue for this\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close", "commid": "kubernetes_issue_49513", "tokennum": 492}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a488ab7256b4fcb0fadbded6d0bc5f28418fdb73d767c40b027b5e6964ad7b7c", "query": "if host == \"\" { // No external IPs were found, let's try to use internal as plan B for _, a := range node.Status.Addresses { <del> if a.Type == v1.NodeInternalIP { </del> <ins> if a.Type == v1.NodeInternalIP && a.Address != \"\" { </ins> host = net.JoinHostPort(a.Address, sshPort) break }", "positive_passages": [{"docid": "doc-en-kubernetes-3fbd6fe4c52deabe3c900459c29c36a04807fdd1453263d11d2244d21f4a4f4a", "text": "Public IPs are expensive resources. Given that we're running scalability tests on 5k-node clusters, we are unnecessarily consuming 5k IPs which is a lot. We should switch our tests so that nodes have only private IP addresses. We are going to do that by configuring NAT so that nodes can talk to outside world (e.g. to download image from dockerhub). But that also requires changing some correctness tests which assume public IPs.\nTo summarize recent work: setting up private gce clusters with nat, feature is gated via the env test and dashboard with correctness tests on gce private cluster - https://k8s- 27 tests fail on fixing the tests - should fix majority of them\nIssues 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\n/remove-lifecycle stale /lifecycle frozen\n- is there anything missing to be done here?\nNo, we can close this one. It was done long time ago. Thanks for catching /close\nClosing this issue. <detailsIn response to : No, we can close this one. It was done long time ago. Thanks for catching 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", "commid": "kubernetes_issue_76374", "tokennum": 335}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a4a209b7171b9aa8c094647eef09956300a575bc73759a1dcdcbebf01825676d", "query": "import ( \"context\" \"fmt\" <ins> \"strings\" </ins> \"sync\" v1 \"k8s.io/api/core/v1\"", "positive_passages": [{"docid": "doc-en-kubernetes-d654f914f6cdd0bd3bce5db6eb3c4ebef631bd8d2558ac9d591cab12ba724061", "text": "What happened: e2e tests detect whether PSP is enabled based on presence of PSP API objects. An addon that proactively includes a PSP in a manifest can trigger that detection and enable PSP-specific e2e tests that should not be run. What you expected to happen: In addition to detecting presence of PSP objects, consider dry-run creating a pod and verifying the annotation indicating the selected PSP policy is , indicating the admission plugin is active. /sig auth /assign", "commid": "kubernetes_issue_91463", "tokennum": 109}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a4aa0ffea015c7284836f585216784e6c120c3fd758872fd75c1f8df890ccf6f", "query": "return admission.NewForbidden(a, fmt.Errorf(\"node requested token bound to a pod scheduled on a different node\")) } <ins> // Note: A token may only be bound to one object at a time. By requiring // the Pod binding, noderestriction eliminates the opportunity to spoof // a Node binding. Instead, kube-apiserver automatically infers and sets // the Node binding when it receives a Pod binding. See: // https://github.com/kubernetes/kubernetes/issues/121723 for more info. </ins> return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-6fd44da75083eb708bb282062daff0367437c77cffc0b305712ab45fdcf69fe6", "text": "recently merged, adding nodes as something we can put in bound object refs (yay!) Today while reading noderestriction code for a different reason, I realized we never extended noderestriction to block Kubelets from binding tokens to nodes other than themselves. Today, noderestriction does block Kubelets from binding tokens to Pods on other nodes, so perhaps it should do the same for bound node references. noderestriction to block it, probably. Read the code here: And note that we didn't modify in No response Not yet in any released version of K8s. N/A N/A N/A N/A N/A\n/triage accepted\nTo summarize Slack discussion: TokenRequest can only bind to one object at a time. kubelet (node identity) is already required to bind to Pod by noderestriction. kube-apiserver automatically inserts the node information based on the Pod binding. kubelet does not set it. So this is technically still node bound. We should still add a comment in to avoid future confusion. There may be other reasons to add a check, like future proofing...", "commid": "kubernetes_issue_121723", "tokennum": 249}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a4ce69cc8100ded1683c886462a275a072b27d656155a2dc3ea86e211b08586b", "query": "FailedPreStopHook     = \"FailedPreStopHook\" UnfinishedPreStopHook = \"UnfinishedPreStopHook\" ) <del> // ToObjectReference takes an old style object reference and converts it to a client-go one func ToObjectReference(ref *v1.ObjectReference) *clientv1.ObjectReference { if ref == nil { return nil } return &clientv1.ObjectReference{ Kind:            ref.Kind, Namespace:       ref.Namespace, Name:            ref.Name, UID:             ref.UID, APIVersion:      ref.APIVersion, ResourceVersion: ref.ResourceVersion, FieldPath:       ref.FieldPath, } } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-b0087f3d33811f5a8bf21a1757c4fff7aaef7add29731940c9c3bd61ec9b29c4", "text": "Is this a BUG REPORT or FEATURE REQUEST?: What happened: Now the and has been consistent in by PR . There is no need to convert v1.ObjectReference to clientv1.ObjectReference in . What you expected to happen: Remove this function and cleanup the codes which call this function. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?:\nThere are no sig labels on this issue. Please by:<br(1) mentioning a sig: <bre.g., for API Machinery<br(2) specifying the label manually: <bre.g., for sig/scalability<br<brNote: method (1) will trigger a notification to the team. You can find the team list and label list\nWill submit the cleanup after PR merged.\n/sig api-machinery\n/sub", "commid": "kubernetes_issue_48747", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a4d320751528f78384b9a160437157d1b0581273363616ed802fd7552bf18b71", "query": "failedPodsObserved += failedPodsObservedOnNode } <del> // Remove pods assigned to not existing nodes when daemonset pods are scheduled by default scheduler. </del> <ins> // Remove unscheduled pods assigned to not existing nodes when daemonset pods are scheduled by scheduler. </ins> // If node doesn't exist then pods are never scheduled and can't be deleted by PodGCController. if utilfeature.DefaultFeatureGate.Enabled(features.ScheduleDaemonSetPods) { <del> podsToDelete = append(podsToDelete, getPodsWithoutNode(nodeList, nodeToDaemonPods)...) </del> <ins> podsToDelete = append(podsToDelete, getUnscheduledPodsWithoutNode(nodeList, nodeToDaemonPods)...) </ins> } // Label new pods using the hash label value of the current history when creating them", "positive_passages": [{"docid": "doc-en-kubernetes-2bd3e1d9e94a5358a6c2d5b4c6b5864c879bb8cabae55e6531ce8f2da7e1ce93", "text": "What happened: Occasionally we get a Daemonset stuck with less Current replicas than Desired, causing a Daemonset sync tends to fix it, e.g (add a new node). This happens to all our Daemonsets. I'm using fluentd as an example. There are no Daemonsets pods in pending nor are there any errors when describing the Daemonset What you expected to happen: The Daemonset Pod to be scheduled How to reproduce it (as minimally and precisely as possible): Reproducing this state is very tricky, I've had the most success by terminating nodes in our ASG causing a new one to come up. However I think I've identified why this is happening. The issue appears to be related to daemonset Pod deletion, a Pod gets deleted causing to trigger, this lowers the expectations by as expected. The delete pod event then triggers a sync of the daemonset, in which it finds which involves fetching pods from the informer cache This is somehow returning the deleted pod. You can see in the logs here thinks that it needs to delete the pod that was deleted. It is also setting the expectation back to after the delete pod event previously lowered it by 1. At this point you're stuck as the function can't get past this line As the expectation can not be satisfied as syncNodes set it back to and there's nothing it to get it back to . So I believe this is what's causing us to get less replicas than expected, the function is stuck due to the expectation so it can't perform a full sync to schedule the new pods. There's also not much to trigger a new sync once the expectation has expired until a new node comes up or one goes down. Environment: Kubernetes version (use ):Cloud provider or hardware configuration: AWS OS (e.g: ):Kernel (e.g. ):\n/sig apps\nI investigated this as much as I could without getting some external input, it feels like it's some kind of race condition in the informer cache. If anyone has ideas of if places to dig deeper that would be handy.\nReiterating the mentions to trigger a notification: <detailsIn response to : I investigated this as much as I could without getting some external input, it feels like it's some kind of race condition in the informer cache. If anyone has ideas of if places to dig deeper that would be handy.", "commid": "kubernetes_issue_75836", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a4d320751528f78384b9a160437157d1b0581273363616ed802fd7552bf18b71", "query": "failedPodsObserved += failedPodsObservedOnNode } <del> // Remove pods assigned to not existing nodes when daemonset pods are scheduled by default scheduler. </del> <ins> // Remove unscheduled pods assigned to not existing nodes when daemonset pods are scheduled by scheduler. </ins> // If node doesn't exist then pods are never scheduled and can't be deleted by PodGCController. if utilfeature.DefaultFeatureGate.Enabled(features.ScheduleDaemonSetPods) { <del> podsToDelete = append(podsToDelete, getPodsWithoutNode(nodeList, nodeToDaemonPods)...) </del> <ins> podsToDelete = append(podsToDelete, getUnscheduledPodsWithoutNode(nodeList, nodeToDaemonPods)...) </ins> } // Label new pods using the hash label value of the current history when creating them", "positive_passages": [{"docid": "doc-en-kubernetes-cf3a9a922f150fcd06b37026fcb1a4fe5fd4fd3de4493928a0abbcee85e2e3a6", "text": "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\nThis problem is definitely related to node termination, it's trying to delete the already deleted pod from the node that's been terminated. The problem seems to go away if is set, I think although this kind of race condition may have always been possible, it's being frequently caused via Which is finding the non-existent pod in the pod cache and seeing that it is assigned to a non-running node, resulting in a request to delete the non-existent pod. cc\nReiterating the mentions to trigger a notification: <detailsIn response to : This problem is definitely related to node termination, it's trying to delete the already deleted pod from the node that's been terminated. 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\n/assign could you please take a look at this? It seems that it is related to the code you in .\nThanks for reporting the bug. Bug was introduced in which deleting pods without nodes. There is race condition between removing pod from cache and listing pods for DaemonSet. Bug occurs during following scenario: is deleted. for node is deleted by PodGCController. handler is executed by informer () set is to queue by delete handler () is processed and pods are taken from cache before deleted pod is removed. for deleted pod is not found so we add deleted pod to podsToDelete list (). are set to del:1() succeeds as pod is not found(). are never met so we need to wait till expectations expire. As fix I will send a change to so only pods that can't be deleted by PodGCController are deleted by DaemonSet controller.", "commid": "kubernetes_issue_75836", "tokennum": 399}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a516243635fb744399c8da04724fecc7d86e9ccb58a3fb3cac909bc904571e1c", "query": "\"k8s.io/apimachinery/pkg/util/sets\" utilfeature \"k8s.io/apiserver/pkg/util/feature\" cliflag \"k8s.io/component-base/cli/flag\" <del> \"k8s.io/klog\" </del> \"k8s.io/kubelet/config/v1beta1\" \"k8s.io/kubernetes/pkg/apis/core\" \"k8s.io/kubernetes/pkg/features\"", "positive_passages": [{"docid": "doc-en-kubernetes-2c9ef8984ebaf899659836b925069334113c910fc47ebe0516a7d659674f044a", "text": "xref In 1.16: change the metadata-proxy addon to use change the kube-proxy addon to use change the masq-agent addon to use stop setting , , and in kube-up\nHey I'm trying to start to contribute to kubernetes and this seem to be an easy task. Can I help with this one?", "commid": "kubernetes_issue_75050", "tokennum": 77}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a51ef2e6038ae62038970c53eb0371837726b81b7e9469671466c96ea6452f8c", "query": "\"spec.version[v1].schema.openAPIV3Schema.properties[d]: Required value: because it is defined in spec.version[v1].schema.openAPIV3Schema.not.properties[d]\", }, }, <ins> { desc: \"metadata with non-properties\", globalSchema: ` type: object properties: metadata: minimum: 42.0 `, expectedViolations: []string{ \"spec.validation.openAPIV3Schema.properties[metadata]: Forbidden: must not specify anything other than name and generateName, but metadata is implicitly specified\", \"spec.validation.openAPIV3Schema.properties[metadata].type: Required value: must not be empty for specified object fields\", }, }, { desc: \"metadata with other properties\", globalSchema: ` type: object properties: metadata: properties: name: pattern: \"^[a-z]+$\" labels: type: object maxLength: 4 `, expectedViolations: []string{ \"spec.validation.openAPIV3Schema.properties[metadata]: Forbidden: must not specify anything other than name and generateName, but metadata is implicitly specified\", \"spec.validation.openAPIV3Schema.properties[metadata].type: Required value: must not be empty for specified object fields\", \"spec.validation.openAPIV3Schema.properties[metadata].properties[name].type: Required value: must not be empty for specified object fields\", }, }, { desc: \"metadata with name property\", globalSchema: ` type: object properties: metadata: type: object properties: name: type: string pattern: \"^[a-z]+$\" `, expectedViolations: []string{}, }, { desc: \"metadata with generateName property\", globalSchema: ` type: object properties: metadata: type: object properties: generateName: type: string pattern: \"^[a-z]+$\" `, expectedViolations: []string{}, }, { desc: \"metadata with name and generateName property\", globalSchema: ` type: object properties: metadata: type: object properties: name: type: string pattern: \"^[a-z]+$\" generateName: type: string pattern: \"^[a-z]+$\" `, expectedViolations: []string{}, }, { desc: \"metadata under junctors\", globalSchema: ` type: object properties: metadata: type: object properties: name: type: string pattern: \"^[a-z]+$\" allOf: - properties: metadata: {} anyOf: - properties: metadata: {} oneOf: - properties: metadata: {} not: properties: metadata: {} `, expectedViolations: []string{ \"spec.validation.openAPIV3Schema.anyOf[0].properties[metadata]: Forbidden: must not be specified in a nested context\", \"spec.validation.openAPIV3Schema.allOf[0].properties[metadata]: Forbidden: must not be specified in a nested context\", \"spec.validation.openAPIV3Schema.oneOf[0].properties[metadata]: Forbidden: must not be specified in a nested context\", \"spec.validation.openAPIV3Schema.not.properties[metadata]: Forbidden: must not be specified in a nested context\", }, }, </ins> } for i := range tests {", "positive_passages": [{"docid": "doc-en-kubernetes-4be11de3bdb9e2a86ad3a19c4d6f5342db422d48e5979c118fca9ce077f64900", "text": "We allow CRD authors to write . Currently we don't restrict writing validation for , which means people can have . For example, people can have additive name constraints (require CR to be ) with the following schema: This brings us two questions: do we if \"metadata\" is included in the schema: simplest option is to publish standard metav1.ObjectMeta schema info, and use any CRD-specified \"metadata\" properties as additive validation (just like in-tree types do, publishing standard ObjectMeta schema info, and implementing type-specific name validation internally) alternatively, we can try merging user-specified metadata schema with the standard one. Technically people should only add extra validation to existing metadata properties (adding new fields to metadata won't work since they will be pruned by built-in validation first), but it's unclear to me how arbitrary people may want the metadata validation to be term question is whether to allow people specifying metadata validation at all, or just allow a subset (like name validation) in CRD v1 /sig api-machinery /area custom-resources cc\nWhat is the difference between these two? I mean the end result is the same right? The only thing that can be is validation. Nothing else works unless you are considering extensions?\nThe former means we drop/hide user-specified metadata schema when we publish CRD OpenAPI. We still validate user-specified constraints on server side, but client-side validation won't see them. The latter enables client-side user-specified metadata validation.\nIf it's possible to merge with standard metadata schema info, or at the cost of not publishing the standard schema. My inclination would be to publish the complete standard schema for metadata/apiVersion/kind, which we know is complete and accurate, and use and user-specified schema for those fields as addition validations server side", "commid": "kubernetes_issue_74620", "tokennum": 396}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a574ad834c454170f53f47111f06258f88e29758d5d397cc0e21a02c600b0762", "query": "// IsFitPredicateRegistered is useful for testing providers. func IsFitPredicateRegistered(name string) bool { <del> schedulerFactoryMutex.Lock() defer schedulerFactoryMutex.Unlock() </del> <ins> schedulerFactoryMutex.RLock() defer schedulerFactoryMutex.RUnlock() </ins> _, ok := fitPredicateMap[name] return ok }", "positive_passages": [{"docid": "doc-en-kubernetes-a3c7d28dcea4cbdaac9e2be0d7d2d60e791f1250fe870aa2d2d4769d84db6cae", "text": "What would you like to be : Currently Mutex lock is acquired in for accessing different maps. Some functions only read map entry: We can utilize RWMutex where the above function acquires read lock. Why is this needed: For concurrent calls to IsFitPredicateRegistered / IsPriorityFunctionRegistered, read lock would lower contention.\n/sig scheduling\nfunctions getFitPredicateFunctions, getPriorityFunctionConfigs, ListRegisteredFitPredicates, ListRegisteredPriorityFunctions and GetAlgorithmProvider can also use read lock.\nI happened to raise earlier today. Anyone can finish resting ones.\nGood to know,\nThanks for raising this ! My PR covered and . Feel free to raise another PR to cover others.\nOnce is merged, I will send my PR thanks\nit's merged now.", "commid": "kubernetes_issue_76248", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a5e0825a9e4c0413d67bc0c514897f150cbf14c9831056f3407f1b5b7bcd15a4", "query": "name = \"go_default_library\", srcs = [\"event.go\"], tags = [\"automanaged\"], <del> deps = [\"//vendor/k8s.io/api/core/v1:go_default_library\"], </del> ) filegroup(", "positive_passages": [{"docid": "doc-en-kubernetes-b0087f3d33811f5a8bf21a1757c4fff7aaef7add29731940c9c3bd61ec9b29c4", "text": "Is this a BUG REPORT or FEATURE REQUEST?: What happened: Now the and has been consistent in by PR . There is no need to convert v1.ObjectReference to clientv1.ObjectReference in . What you expected to happen: Remove this function and cleanup the codes which call this function. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?:\nThere are no sig labels on this issue. Please by:<br(1) mentioning a sig: <bre.g., for API Machinery<br(2) specifying the label manually: <bre.g., for sig/scalability<br<brNote: method (1) will trigger a notification to the team. You can find the team list and label list\nWill submit the cleanup after PR merged.\n/sig api-machinery\n/sub", "commid": "kubernetes_issue_48747", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a5f510111ba0fa9274e518c02f796091ca400ed8faeb5631315120a7b4045817", "query": "} func (dc *DeploymentController) syncRecreateDeployment(deployment extensions.Deployment) error { <del> // TODO: implement me. </del> <ins> newRC, err := dc.getNewRC(deployment) if err != nil { return err } oldRCs, err := dc.getOldRCs(deployment) if err != nil { return err } allRCs := append(oldRCs, newRC) // scale down old rcs scaledDown, err := dc.scaleDownOldRCsForRecreate(oldRCs, deployment) if err != nil { return err } if scaledDown { // Update DeploymentStatus return dc.updateDeploymentStatus(allRCs, newRC, deployment) } // scale up new rc scaledUp, err := dc.scaleUpNewRCForRecreate(newRC, deployment) if err != nil { return err } if scaledUp { // Update DeploymentStatus return dc.updateDeploymentStatus(allRCs, newRC, deployment) } </ins> return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-ceb20554e653f6657baad1bbb36c40e66d8a76887956e3c674b77febc82d4455", "text": "There's some practical limit on the number of concurrent access tokens that can be used in a Kubernetes cluster before it begins to spend all of its time in the authn stack verifying them. Absent fixes to it was < 500; with the fixes linked there it's still not infinitely scalable-- I still hit (what I believe to be) with ~ 5k unique tokens @ ~700QPS. This request is to this dimension an official name & definition, and list it with others, e.g. here: it it have a useful value (I think it should be 10k) /kind bug /sig scalability\n/cc\noh and 4. add tests which verify it is as high as believed.\ncc since projected tokens will increase the number of unique tokens\n/sig auth\nLRUs are not good at scaling and sharding has some major pitfalls as pointed out. I would suggest that we try to drop the LRU cache for successful authentication results in the token cache. The main benefit of using an LRU here is bound cache size. Entries in the token cache have a fast expiration independent of the LRU policy. The records probably take up O(2kb) (guesstimate) of memory. Given that these are successful attempts with presumably valid tokens, I don't think we are getting any benefit from the LRU. If we don't have a constraint on fixed cache size, we can back the token cache with a sync.Map and run a single background goroutine to periodically walk the map and remove expired entries. This would fix the problematic locking and eviction due to nonuniform distribution of tokens over shards. The failure cache is less important and we don't cache failures by default. If we consider this the \"slowpath\", we can probably leave it as. If that's not good enough, we have a couple options (with various tradeoffs) to improve it.\nIf off by default is not enough, more reasoning why the failed cache is not super useful: it might help with an accidental DoS but it doesn't prevent anything actively malicious DoS. I think we can focus our improvements on the success cache.\n/assign He is already working on adding an explicit test for it.\nhas taken it over and is actively working on this. Unfortunately, I cannot assign this issue to him as he's not a k8s member yet\nIt's not closed - all testes must be submitted and appropriate documentation must be\nThanks everyone!!", "commid": "kubernetes_issue_83375", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a5f63c695c7a7fd3e106f81a353c7857116c33873d36a846a1dbbea7047d87cd", "query": "continue } <del> if o.Local || cmdutil.GetDryRunFlag(o.Cmd) { </del> <ins> if cmdutil.GetDryRunFlag(o.Cmd) { fmt.Fprintln(o.Err, \"info: running in local mode...\") </ins> return o.PrintObject(o.Cmd, o.Mapper, info.Object, o.Out) }", "positive_passages": [{"docid": "doc-en-kubernetes-f45c12318e35043c65362c27e361ee13adfef369e183f2b4f0557c11353bd9e9", "text": "from https://k8s-\nReally suspect this is\nThis is putting us into test-go post-commit run is broken\ncc:\nmarked this p0 - if a fix isn't easy let's try to identify what introduced this and revert.\nThis flake on: 2016-10-30 07:19 PDT First instance: : It is flaking frequently, blocking PRs from getting merged, and slowing the submit queue ( at 75%). As on-call, I'm going to try and identify the cluprit and revert. Can use all help in doing so.\ncan you investigate whether your additional tests could cause this (by breaking the deployment of those pods, for instance) , Saad Ali wrote:\nPR looks most suspect to me. It mucked with , and the errors we are seeing in each of the failures is related to : That PR was merged at Oct 30, 2016, 6:18 AM PDT and the first flake in was at Oct 30, 2016, 7:19 AM PDT. Thoughts? CC\nI'm going to initiate a revert of to see if that fixes the issue\nIMO we can just change the flaky test to not get pods but some other resources, such as deployments. We can't really expect to clean up pods immediately.\nI'm going to proceed with revert (). Please feel free to send a follow up PR to handle this more gracefully.\nGoing to leave this opened until we have a few hours of runs with the revert. Want to verify, with some degree of certainty, that the revert took care of this flake.\nWe had 15 green runs of in a row. Considering this flake fixed.", "commid": "kubernetes_issue_35898", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a5fd77247d73ccb39ef29b9b2173fb7359d3bc2a3821f09118697f9dd145a1e3", "query": "<ins> #!/bin/bash # Copyright 2014 Google Inc. All rights reserved. # # Licensed under the Apache License, Version 2.0 (the \"License\"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # #     http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an \"AS IS\" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. # Launches a container and verifies it can be reached. Assumes that # we're being called by hack/e2e-test.sh (we use some env vars it sets up). # TODO: Convert uses of gcutil to gcloud set -o errexit set -o nounset set -o pipefail KUBE_ROOT=$(dirname \"${BASH_SOURCE}\")/../.. source \"${KUBE_ROOT}/cluster/kube-env.sh\" source \"${KUBE_ROOT}/cluster/$KUBERNETES_PROVIDER/util.sh\" if [[ \"$KUBERNETES_PROVIDER\" != \"gce\" ]]; then echo \"PD test is only run for GCE\" return 0 fi disk_name=\"e2e-$(date +%H-%M-%s)\" config=\"/tmp/${disk_name}.yaml\" function teardown() { echo \"Cleaning up test artifacts\" ${KUBECFG} delete pods/testpd rm -rf ${config} echo \"Waiting for disk to become unmounted\" sleep 20 gcutil deletedisk -f --zone=${ZONE} ${disk_name} } trap \"teardown\" EXIT perl -p -e \"s/%.*%/${disk_name}/g\" ${KUBE_ROOT}/examples/gce-pd/testpd.yaml > ${config} # Create and mount the disk. gcutil adddisk --size_gb=10 --zone=${ZONE} ${disk_name} gcutil attachdisk --disk ${disk_name} ${MASTER_NAME} gcutil ssh ${MASTER_NAME} sudo rm -rf /mnt/tmp gcutil ssh ${MASTER_NAME} sudo mkdir /mnt/tmp gcutil ssh ${MASTER_NAME} sudo /usr/share/google/safe_format_and_mount /dev/disk/by-id/google-${disk_name} /mnt/tmp gcutil ssh ${MASTER_NAME} sudo umount /mnt/tmp gcloud compute instances detach-disk --disk ${disk_name} --zone ${ZONE} ${MASTER_NAME} ${KUBECFG} -c ${config} create pods pod_id_list=$($KUBECFG '-template={{range.items}}{{.id}} {{end}}' -l test=testpd list pods) # Pod turn up on a clean cluster can take a while for the docker image pull. all_running=0 for i in $(seq 1 24); do echo \"Waiting for pods to come up.\" sleep 5 all_running=1 for id in $pod_id_list; do current_status=$($KUBECFG -template '{{.currentState.status}}' get pods/$id) || true if [[ \"$current_status\" != \"Running\" ]]; then all_running=0 break fi done if [[ \"${all_running}\" == 1 ]]; then break fi done if [[ \"${all_running}\" == 0 ]]; then echo \"Pods did not come up in time\" exit 1 fi </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-4cc03be8a4c78b1eefdd458c17e35e10d17eae1288a6e1bcb08b9d7d585d4633", "text": "07-02 and 13-02 No response No response /sig\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scalability\nI might be related to the npd.\nThe same test failures happening again on 25.02:\n/sig node\n/sig node /cc The restart of caused the flake. I also opened to track it in NPD repo.\nI missed this log. It is caused by oom. Adding some memory may help. I submitted to fix it. Does mean killing metrics-server?\n/remove-sig node Sorry, I misread the log. The NPD found the metric server is OOM. It is about the metrics server, not the NPD. Sorry for disturb. I may add some memory for metric-server and check why metric server memory changed. I heard that metrics server recently released a new version. I will check if it is related.\n/sig node\nOOM metrics shows the metric server is OOMed. This is odd, that only metrics-server-nanny is with a memory limit. It uses whose command is . metrics-server container has no memory limit, but it got killed by OOM. Does this indicate that the node is OOM? (edited)\nThe last run failed in node-problem-detector ContainerStateTerminated. I0227 05:03:31. ] PodStartupLatency: perc50: 14m29.018886827s, perc90: 28m44.625518807s, perc99: 32m2.19303496s; threshold 1h0m0s I0227 05:03:32. ]", "commid": "kubernetes_issue_123328", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a5fd77247d73ccb39ef29b9b2173fb7359d3bc2a3821f09118697f9dd145a1e3", "query": "<ins> #!/bin/bash # Copyright 2014 Google Inc. All rights reserved. # # Licensed under the Apache License, Version 2.0 (the \"License\"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # #     http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an \"AS IS\" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. # Launches a container and verifies it can be reached. Assumes that # we're being called by hack/e2e-test.sh (we use some env vars it sets up). # TODO: Convert uses of gcutil to gcloud set -o errexit set -o nounset set -o pipefail KUBE_ROOT=$(dirname \"${BASH_SOURCE}\")/../.. source \"${KUBE_ROOT}/cluster/kube-env.sh\" source \"${KUBE_ROOT}/cluster/$KUBERNETES_PROVIDER/util.sh\" if [[ \"$KUBERNETES_PROVIDER\" != \"gce\" ]]; then echo \"PD test is only run for GCE\" return 0 fi disk_name=\"e2e-$(date +%H-%M-%s)\" config=\"/tmp/${disk_name}.yaml\" function teardown() { echo \"Cleaning up test artifacts\" ${KUBECFG} delete pods/testpd rm -rf ${config} echo \"Waiting for disk to become unmounted\" sleep 20 gcutil deletedisk -f --zone=${ZONE} ${disk_name} } trap \"teardown\" EXIT perl -p -e \"s/%.*%/${disk_name}/g\" ${KUBE_ROOT}/examples/gce-pd/testpd.yaml > ${config} # Create and mount the disk. gcutil adddisk --size_gb=10 --zone=${ZONE} ${disk_name} gcutil attachdisk --disk ${disk_name} ${MASTER_NAME} gcutil ssh ${MASTER_NAME} sudo rm -rf /mnt/tmp gcutil ssh ${MASTER_NAME} sudo mkdir /mnt/tmp gcutil ssh ${MASTER_NAME} sudo /usr/share/google/safe_format_and_mount /dev/disk/by-id/google-${disk_name} /mnt/tmp gcutil ssh ${MASTER_NAME} sudo umount /mnt/tmp gcloud compute instances detach-disk --disk ${disk_name} --zone ${ZONE} ${MASTER_NAME} ${KUBECFG} -c ${config} create pods pod_id_list=$($KUBECFG '-template={{range.items}}{{.id}} {{end}}' -l test=testpd list pods) # Pod turn up on a clean cluster can take a while for the docker image pull. all_running=0 for i in $(seq 1 24); do echo \"Waiting for pods to come up.\" sleep 5 all_running=1 for id in $pod_id_list; do current_status=$($KUBECFG -template '{{.currentState.status}}' get pods/$id) || true if [[ \"$current_status\" != \"Running\" ]]; then all_running=0 break fi done if [[ \"${all_running}\" == 1 ]]; then break fi done if [[ \"${all_running}\" == 0 ]]; then echo \"Pods did not come up in time\" exit 1 fi </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-a11072f45f81b280dea24734413173747c87bdd472ce068bad905ce856d1cb81", "text": "Loaded restart count threshold overrides: map[coredns:2 fluentd-gcp:999 konnectivity-agent:2 kube-controller-manager:1 kube-proxy:2 kube-scheduler:1 l7-lb-controller:1 metadata-proxy:2 prometheus-to-sd-exporter:2] I0227 05:03:32. ] ClusterOOMsTracker: gathering cluster OOMs tracking measurement E0227 05:03:32. ] TestMetrics: [action gather failed for SystemPodMetrics measurement: restart counts violation: RestartCount(node-problem-detector-tgl8h, node-problem-detector)=1, want <= 0; RestartCount(node-problem-detector-vpsmz, node-problem-detector)=1, want <= 0] I0227 05:03:32. ] Step \"[step: 29] gathering measurements\" ended W0227 05:03:32. ] Got errors during step execution: [measurement call TestMetrics - TestMetrics error: [action gather failed for SystemPodMetrics measurement: restart counts violation: RestartCount(node-problem-detector-tgl8h, node-problem-detector)=1, want <= 0; RestartCount(node-problem-detector-vpsmz, node-problem-detector)=1, want <= 0]] I0227 05:03:32. ] Waiting for the chaos monkey subroutine to end... I0227 05:03:32. ] Chaos monkey ended. I0227 05:03:32. ] I0227 05:03:32. ] Stopping DnsLookupLatency probe... I0227 05:03:47. ] Stopping InClusterNetworkLatency probe... I0227 05:04:22. ] Resources cleanup time: 50.539700215s E0227 05:04:22. ]\nE0227 05:04:22. ] Test Finished E0227 05:04:22. ] Test: E0227 05:04:22. ] Status: Fail E0227 05:04:22. ]", "commid": "kubernetes_issue_123328", "tokennum": 491}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a5fd77247d73ccb39ef29b9b2173fb7359d3bc2a3821f09118697f9dd145a1e3", "query": "<ins> #!/bin/bash # Copyright 2014 Google Inc. All rights reserved. # # Licensed under the Apache License, Version 2.0 (the \"License\"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # #     http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an \"AS IS\" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. # Launches a container and verifies it can be reached. Assumes that # we're being called by hack/e2e-test.sh (we use some env vars it sets up). # TODO: Convert uses of gcutil to gcloud set -o errexit set -o nounset set -o pipefail KUBE_ROOT=$(dirname \"${BASH_SOURCE}\")/../.. source \"${KUBE_ROOT}/cluster/kube-env.sh\" source \"${KUBE_ROOT}/cluster/$KUBERNETES_PROVIDER/util.sh\" if [[ \"$KUBERNETES_PROVIDER\" != \"gce\" ]]; then echo \"PD test is only run for GCE\" return 0 fi disk_name=\"e2e-$(date +%H-%M-%s)\" config=\"/tmp/${disk_name}.yaml\" function teardown() { echo \"Cleaning up test artifacts\" ${KUBECFG} delete pods/testpd rm -rf ${config} echo \"Waiting for disk to become unmounted\" sleep 20 gcutil deletedisk -f --zone=${ZONE} ${disk_name} } trap \"teardown\" EXIT perl -p -e \"s/%.*%/${disk_name}/g\" ${KUBE_ROOT}/examples/gce-pd/testpd.yaml > ${config} # Create and mount the disk. gcutil adddisk --size_gb=10 --zone=${ZONE} ${disk_name} gcutil attachdisk --disk ${disk_name} ${MASTER_NAME} gcutil ssh ${MASTER_NAME} sudo rm -rf /mnt/tmp gcutil ssh ${MASTER_NAME} sudo mkdir /mnt/tmp gcutil ssh ${MASTER_NAME} sudo /usr/share/google/safe_format_and_mount /dev/disk/by-id/google-${disk_name} /mnt/tmp gcutil ssh ${MASTER_NAME} sudo umount /mnt/tmp gcloud compute instances detach-disk --disk ${disk_name} --zone ${ZONE} ${MASTER_NAME} ${KUBECFG} -c ${config} create pods pod_id_list=$($KUBECFG '-template={{range.items}}{{.id}} {{end}}' -l test=testpd list pods) # Pod turn up on a clean cluster can take a while for the docker image pull. all_running=0 for i in $(seq 1 24); do echo \"Waiting for pods to come up.\" sleep 5 all_running=1 for id in $pod_id_list; do current_status=$($KUBECFG -template '{{.currentState.status}}' get pods/$id) || true if [[ \"$current_status\" != \"Running\" ]]; then all_running=0 break fi done if [[ \"${all_running}\" == 1 ]]; then break fi done if [[ \"${all_running}\" == 0 ]]; then echo \"Pods did not come up in time\" exit 1 fi </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-8045aaa7c39478c40c58e17441fd375a472ca56f31885311d26bd40c11b2233d", "text": "Errors: [measurement call TestMetrics - TestMetrics error: [action gather failed for SystemPodMetrics measurement: restart counts violation: RestartCount(node-problem-detector-tgl8h, node-problem-detector)=1, want <= 0; RestartCount(node-problem-detector-vpsmz, node-problem-detector)=1, want <= 0]] E0227 05:04:22. ]\nI0227 05:04:22. ]\nI0227 05:04:22. ] Running testing/huge- I0227 05:04:22. ]", "commid": "kubernetes_issue_123328", "tokennum": 136}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a6230681f6cd44905810676af4cf1a61b3e1fb0fc64d64f6d4a8f2a8818d0c5f", "query": "<ins> <?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"no\"?> <!DOCTYPE svg PUBLIC \"-//W3C//DTD SVG 1.1//EN\" \"http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd\"> <!-- Generated by graphviz version 2.36.0 (20140111.2315) --> <!-- Title: tagged_release Pages: 1 --> <svg width=\"257pt\" height=\"360pt\" viewBox=\"0.00 0.00 257.33 360.00\" xmlns=\"http://www.w3.org/2000/svg\" xmlns:xlink=\"http://www.w3.org/1999/xlink\"> <g id=\"graph0\" class=\"graph\" transform=\"scale(0.649819 0.649819) rotate(0) translate(4 550)\"> <title>tagged_release</title> <polygon fill=\"white\" stroke=\"none\" points=\"-4,4 -4,-550 392,-550 392,4 -4,4\"/> <!-- ci012abc --> <g id=\"node1\" class=\"node\"><title>ci012abc</title> <ellipse fill=\"#ffffcc\" stroke=\"black\" cx=\"56\" cy=\"-115\" rx=\"42.7926\" ry=\"42.7926\"/> <text text-anchor=\"middle\" x=\"56\" y=\"-111.3\" font-family=\"Consolas, Liberation Mono, Menlo, Courier, monospace\" font-size=\"14.00\">012abc</text> </g> <!-- pr101 --> <g id=\"node2\" class=\"node\"><title>pr101</title> <polygon fill=\"#ccccff\" stroke=\"black\" points=\"112,-255 0,-255 0,-219 112,-219 112,-255\"/> <text text-anchor=\"middle\" x=\"56\" y=\"-233.3\" font-family=\"Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif\" font-size=\"14.00\">Merge PR #101</text> </g> <!-- ci012abc&#45;&gt;pr101 --> <g id=\"edge1\" class=\"edge\"><title>ci012abc&#45;&gt;pr101</title> <path fill=\"none\" stroke=\"black\" d=\"M56,-157.97C56,-174.83 56,-193.784 56,-208.789\"/> <polygon fill=\"black\" stroke=\"black\" points=\"52.5001,-208.93 56,-218.93 59.5001,-208.93 52.5001,-208.93\"/> </g> <!-- ci345cde --> <g id=\"node3\" class=\"node\"><title>ci345cde</title> <ellipse fill=\"#ffffcc\" stroke=\"black\" cx=\"62\" cy=\"-359\" rx=\"42.7926\" ry=\"42.7926\"/> <text text-anchor=\"middle\" x=\"62\" y=\"-355.3\" font-family=\"Consolas, Liberation Mono, Menlo, Courier, monospace\" font-size=\"14.00\">345cde</text> </g> <!-- pr101&#45;&gt;ci345cde --> <g id=\"edge2\" class=\"edge\"><title>pr101&#45;&gt;ci345cde</title> <path fill=\"none\" stroke=\"black\" d=\"M56.8597,-255.193C57.5237,-268.473 58.4796,-287.592 59.3874,-305.748\"/> <polygon fill=\"black\" stroke=\"black\" points=\"55.904,-306.17 59.8991,-315.982 62.8953,-305.82 55.904,-306.17\"/> </g> <!-- pr102 --> <g id=\"node4\" class=\"node\"><title>pr102</title> <polygon fill=\"#ccccff\" stroke=\"black\" points=\"129,-474 17,-474 17,-438 129,-438 129,-474\"/> <text text-anchor=\"middle\" x=\"73\" y=\"-452.3\" font-family=\"Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif\" font-size=\"14.00\">Merge PR #102</text> </g> <!-- ci345cde&#45;&gt;pr102 --> <g id=\"edge3\" class=\"edge\"><title>ci345cde&#45;&gt;pr102</title> <path fill=\"none\" stroke=\"black\" d=\"M66.8248,-401.668C67.8523,-410.542 68.9117,-419.692 69.8567,-427.853\"/> <polygon fill=\"black\" stroke=\"black\" points=\"66.3936,-428.375 71.0207,-437.906 73.3472,-427.57 66.3936,-428.375\"/> </g> <!-- pr100 --> <g id=\"node10\" class=\"node\"><title>pr100</title> <polygon fill=\"#ccccff\" stroke=\"black\" points=\"174,-546 62,-546 62,-510 174,-510 174,-546\"/> <text text-anchor=\"middle\" x=\"118\" y=\"-524.3\" font-family=\"Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif\" font-size=\"14.00\">Merge PR #100</text> </g> <!-- pr102&#45;&gt;pr100 --> <g id=\"edge6\" class=\"edge\"><title>pr102&#45;&gt;pr100</title> <path fill=\"none\" stroke=\"black\" d=\"M84.1236,-474.303C89.355,-482.441 95.6999,-492.311 101.478,-501.299\"/> <polygon fill=\"black\" stroke=\"black\" points=\"98.6526,-503.377 107.004,-509.896 104.541,-499.591 98.6526,-503.377\"/> </g> <!-- version_commit --> <g id=\"node5\" class=\"node\"><title>version_commit</title> <ellipse fill=\"#ccffcc\" stroke=\"black\" cx=\"173\" cy=\"-237\" rx=\"42.7926\" ry=\"42.7926\"/> <text text-anchor=\"middle\" x=\"173\" y=\"-233.3\" font-family=\"Consolas, Liberation Mono, Menlo, Courier, monospace\" font-size=\"14.00\">678fed</text> </g> <!-- dev_commit --> <g id=\"node6\" class=\"node\"><title>dev_commit</title> <ellipse fill=\"#ffffcc\" stroke=\"black\" cx=\"169\" cy=\"-359\" rx=\"42.7926\" ry=\"42.7926\"/> <text text-anchor=\"middle\" x=\"169\" y=\"-355.3\" font-family=\"Consolas, Liberation Mono, Menlo, Courier, monospace\" font-size=\"14.00\">456dcb</text> </g> <!-- version_commit&#45;&gt;dev_commit --> <g id=\"edge4\" class=\"edge\"><title>version_commit&#45;&gt;dev_commit</title> <path fill=\"none\" stroke=\"black\" d=\"M171.601,-279.97C171.322,-288.326 171.027,-297.195 170.739,-305.844\"/> <polygon fill=\"black\" stroke=\"black\" points=\"167.24,-305.74 170.405,-315.851 174.236,-305.973 167.24,-305.74\"/> </g> <!-- dev_commit&#45;&gt;pr100 --> <g id=\"edge8\" class=\"edge\"><title>dev_commit&#45;&gt;pr100</title> <path fill=\"none\" stroke=\"black\" d=\"M158.36,-400.568C152.438,-422.433 144.719,-449.815 137,-474 134.253,-482.606 131.013,-491.906 127.994,-500.278\"/> <polygon fill=\"black\" stroke=\"black\" points=\"124.616,-499.325 124.47,-509.919 131.191,-501.729 124.616,-499.325\"/> </g> <!-- release_info --> <g id=\"node7\" class=\"node\"><title>release_info</title> <text text-anchor=\"middle\" x=\"304\" y=\"-240.8\" font-family=\"Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif\" font-size=\"14.00\">pkg/version/base.go:</text> <text text-anchor=\"middle\" x=\"304\" y=\"-225.8\" font-family=\"Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif\" font-size=\"14.00\">gitVersion = &quot;v0.5&quot;;</text> </g> <!-- dev_info --> <g id=\"node8\" class=\"node\"><title>dev_info</title> <text text-anchor=\"middle\" x=\"309\" y=\"-362.8\" font-family=\"Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif\" font-size=\"14.00\">pkg/version/base.go:</text> <text text-anchor=\"middle\" x=\"309\" y=\"-347.8\" font-family=\"Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif\" font-size=\"14.00\">gitVersion = &quot;v0.5&#45;dev&quot;;</text> </g> <!-- pr99 --> <g id=\"node9\" class=\"node\"><title>pr99</title> <polygon fill=\"#ccccff\" stroke=\"black\" points=\"143,-36 39,-36 39,-0 143,-0 143,-36\"/> <text text-anchor=\"middle\" x=\"91\" y=\"-14.3\" font-family=\"Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif\" font-size=\"14.00\">Merge PR #99</text> </g> <!-- pr99&#45;&gt;ci012abc --> <g id=\"edge5\" class=\"edge\"><title>pr99&#45;&gt;ci012abc</title> <path fill=\"none\" stroke=\"black\" d=\"M84.5805,-36.4245C81.5586,-44.6267 77.7879,-54.8615 73.9865,-65.1795\"/> <polygon fill=\"black\" stroke=\"black\" points=\"70.6804,-64.0292 70.5075,-74.6226 77.2488,-66.4492 70.6804,-64.0292\"/> </g> <!-- pr99&#45;&gt;version_commit --> <g id=\"edge7\" class=\"edge\"><title>pr99&#45;&gt;version_commit</title> <path fill=\"none\" stroke=\"black\" d=\"M97.4344,-36.0276C109.585,-68.1826 136.317,-138.924 154.498,-187.038\"/> <polygon fill=\"black\" stroke=\"black\" points=\"151.318,-188.523 158.127,-196.64 157.866,-186.048 151.318,-188.523\"/> </g> <!-- tag --> <g id=\"node11\" class=\"node\"><title>tag</title> <ellipse fill=\"#ffcccc\" stroke=\"black\" cx=\"226\" cy=\"-115\" rx=\"71.4873\" ry=\"18\"/> <text text-anchor=\"middle\" x=\"226\" y=\"-111.3\" font-family=\"Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif\" font-size=\"14.00\">$ git tag &#45;a v0.5</text> </g> <!-- tag&#45;&gt;version_commit --> <g id=\"edge9\" class=\"edge\"><title>tag&#45;&gt;version_commit</title> <path fill=\"none\" stroke=\"black\" d=\"M218.519,-132.939C212.168,-147.318 202.736,-168.673 194.103,-188.22\"/> <polygon fill=\"black\" stroke=\"black\" points=\"190.784,-187.071 189.946,-197.632 197.188,-189.899 190.784,-187.071\"/> </g> </g> </svg> </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-7c5448078f172c3dba4d1f6f6ed5d66f21d2fc0ea9dd38dbb1ed9b4cc49eea15", "text": "Right now, we have a mixture of user documentation and developer documentation in the top-level directory. We should make it easier to find a just user documentation. Step 1 would be to move developer documentation into a subdir like docs/development or something like that. User docs would stay in the top-level docs dir.\nmove to", "commid": "kubernetes_issue_1797", "tokennum": 71}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a62793a3b95d6154d92dbb5c2a9dce87a97b4035747cff8d90565e03c4cdd943", "query": "// If the ordinal could not be parsed (ord < 0), ignore the Pod. } <ins> // make sure to update the latest status even if there is an error later defer func() { // update the set's status statusErr := ssc.updateStatefulSetStatus(ctx, set, &status) if statusErr == nil { klog.V(4).InfoS(\"Updated status\", \"statefulSet\", klog.KObj(set), \"replicas\", status.Replicas, \"readyReplicas\", status.ReadyReplicas, \"currentReplicas\", status.CurrentReplicas, \"updatedReplicas\", status.UpdatedReplicas) } else if updateErr == nil { updateErr = statusErr } else { klog.V(4).InfoS(\"Could not update status\", \"statefulSet\", klog.KObj(set), \"err\", statusErr) } }() </ins> // for any empty indices in the sequence [0,set.Spec.Replicas) create a new Pod at the correct revision for ord := 0; ord < replicaCount; ord++ { if replicas[ord] == nil {", "positive_passages": [{"docid": "doc-en-kubernetes-0cad02d163e61aff3cc2c1257b68701a42fb1145e0b51f6816fd9a85adca78e6", "text": "I create a ResourceQuota with two pods limit in my namespace. Then, I create a statefuleSet with 3 replicas. As expected, two pods are created successfully, and the third pod failed to create. But, the ReadyReplicas is not 2 ,but 1. The ReadyReplicas is correct 1Create a ResourceQuota with two pods limit in a new namespace. 2Create a statefulSet with 3 replicas 3Check if the ReadyReplicas of statefulSet matchs the number of stateful running pods. 1According to the logic of the statefulSet controller, new pod created in current sync is not be immediately counted into the ReadyReplicas. 2Failure to create pod will cause to return error, then skip updating status. <details</details<details</details<detailskind v1.23.3 </details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig apps\n/assign", "commid": "kubernetes_issue_108837", "tokennum": 302}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a62df326aabecbe22d6130e8c85254673b9dda4732ea745e85d1ba0b23efb4ee", "query": "NoSnatTest               = ImageConfig{e2eRegistry, \"no-snat-test\", \"1.0\", true} NoSnatTestProxy          = ImageConfig{e2eRegistry, \"no-snat-test-proxy\", \"1.0\", true} NWayHTTP                 = ImageConfig{e2eRegistry, \"n-way-http\", \"1.0\", true} <del> // When these values are updated, also update cmd/kubelet/app/options/options.go Pause               = ImageConfig{gcRegistry, \"pause\", \"3.0\", true} </del> <ins> // When these values are updated, also update cmd/kubelet/app/options/container_runtime.go Pause               = ImageConfig{gcRegistry, \"pause\", \"3.1\", true} </ins> Porter              = ImageConfig{e2eRegistry, \"porter\", \"1.0\", true} PortForwardTester   = ImageConfig{e2eRegistry, \"port-forward-tester\", \"1.0\", true} Redis               = ImageConfig{e2eRegistry, \"redis\", \"1.0\", true}", "positive_passages": [{"docid": "doc-en-kubernetes-a834f77ddd825b3d04a660aa7c11d0734893e4dcde6e0d4a7399e3b3daf56428", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: the pause-amd64:3.0 image on has an empty schema2 manifest, which prevents is from being pulled by proxy/caches which only support V2 registries. What you expected to happen: Being able to pull ` using a V2 manifest compatible client. Anything else we need to know?: The proxy/cahce is requesting this\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nAfter talking with , he mentionned the following\nAFAIK, does not support well. After inspecting the image, you can find is still using manifest v1.\n/cc FYI\nIm not sure which exact version x sch\u00e9ma X is needed. What I know is that we can download through the proxy/cache all other Kubernetes kube-system images, only the pause image is giving us trouble. Therefore, I would say that having the image available using the same format as the other kube-system images would be the request here.\nYeah, we haven't updated the pause image in a while, since it doesn't really ever change. I'm not sure whether rebuilding + pushing over the existing tag is safe, or if we should bump to or something. thoughts?\nIf we do rebuilding/updating the image, that would help and a bunch of similar issues.\nit's better/save to go with new tag\nI didn't realize there were changes to the pause binary that were never actually deployed. It seems like we should probably just do that (and bump the tag).\nthat sounds great. Any idea when the existing 3.0 tag could be pushed again?\nWe shouldn't push over the 3.0 tag; we should push a 3.1 or 4.0 tag instead. I'm not sure who owns the pause container who should drive this. Maybe sig-node and/or\nIt seems like it should be sig-node. I'll look into it.\nThe new container has been built, can you test with\nIts working! thanks! I was able to pull it through our artifactory proxy , Lee Verberne <:\nexcellent, thanks for checking. /assign", "commid": "kubernetes_issue_56253", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a62df326aabecbe22d6130e8c85254673b9dda4732ea745e85d1ba0b23efb4ee", "query": "NoSnatTest               = ImageConfig{e2eRegistry, \"no-snat-test\", \"1.0\", true} NoSnatTestProxy          = ImageConfig{e2eRegistry, \"no-snat-test-proxy\", \"1.0\", true} NWayHTTP                 = ImageConfig{e2eRegistry, \"n-way-http\", \"1.0\", true} <del> // When these values are updated, also update cmd/kubelet/app/options/options.go Pause               = ImageConfig{gcRegistry, \"pause\", \"3.0\", true} </del> <ins> // When these values are updated, also update cmd/kubelet/app/options/container_runtime.go Pause               = ImageConfig{gcRegistry, \"pause\", \"3.1\", true} </ins> Porter              = ImageConfig{e2eRegistry, \"porter\", \"1.0\", true} PortForwardTester   = ImageConfig{e2eRegistry, \"port-forward-tester\", \"1.0\", true} Redis               = ImageConfig{e2eRegistry, \"redis\", \"1.0\", true}", "positive_passages": [{"docid": "doc-en-kubernetes-7628cd26f0dafa992a4ea43a6c68b9bcdbf056fca43ee32b40ab60cef4154c17", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: pause does not reap zombie processes using the default pause container provided by What you expected to happen: should include the up to date pause code to reap zombie processes when using docker = 1.13.1 found here How to reproduce it (as minimally and precisely as possible): a.out will leave a zombie process that is not cleaned up Anything else we need to know?: Building the pause container from master solves this issue Related: Environment: Kubernetes version (use ): 1.7.0+ Cloud provider or hardware configuration**: N/A OS (e.g. from /etc/os-release): CentOS 7 Kernel (e.g. ): 4.10.13+ Install tools: Others: docker = 1.13.1\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\ni get a simliar problem when i run crond service in pod container, every day it makes some [anacron] zombie progresses UID PID PPID C STIME TTY TIME CMD root 1 0 0 Nov14 ? 00:00:00 /pause root 7 0 0 Nov14 ? 00:00:00 /usr/local/bin/dumb-init /usr/lo root 13 7 0 Nov14 ? 00:00:00 nginx: master process /usr/local nobody 21 13 0 Nov14 ? 00:00:01 nginx: worker process nobody 22 13 0 Nov14 ? 00:00:07 nginx: worker process nobody 23 13 0 Nov14 ? 00:00:07 nginx: worker process nobody 24 13 0 Nov14 ? 00:00:05 nginx: worker process root 77 1 0 Nov14 ? 00:00:00 [anacron] root 1 0 00:01 ? 00:00:00 [anacron] <defunctroot 1 0 01:01 ? 00:00:00 [anacron] <defunctroot 1 0 02:01 ?", "commid": "kubernetes_issue_50865", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a62df326aabecbe22d6130e8c85254673b9dda4732ea745e85d1ba0b23efb4ee", "query": "NoSnatTest               = ImageConfig{e2eRegistry, \"no-snat-test\", \"1.0\", true} NoSnatTestProxy          = ImageConfig{e2eRegistry, \"no-snat-test-proxy\", \"1.0\", true} NWayHTTP                 = ImageConfig{e2eRegistry, \"n-way-http\", \"1.0\", true} <del> // When these values are updated, also update cmd/kubelet/app/options/options.go Pause               = ImageConfig{gcRegistry, \"pause\", \"3.0\", true} </del> <ins> // When these values are updated, also update cmd/kubelet/app/options/container_runtime.go Pause               = ImageConfig{gcRegistry, \"pause\", \"3.1\", true} </ins> Porter              = ImageConfig{e2eRegistry, \"porter\", \"1.0\", true} PortForwardTester   = ImageConfig{e2eRegistry, \"port-forward-tester\", \"1.0\", true} Redis               = ImageConfig{e2eRegistry, \"redis\", \"1.0\", true}", "positive_passages": [{"docid": "doc-en-kubernetes-6179feaaee46a15cd909bb088c82657b9b59fba8efdee1296995076588512032", "text": "00:00:00 [anacron] <defunctroot 1 0 03:01 ? 00:00:00 [anacron] <defunctroot 0 0 11:49 ? 00:00:00 /bin/bash root 0 1 19:15 ? 00:00:00 /bin/bash root 0 19:15 ? 00:00:00 ps -ef !\nDo we know why this was never resolved / was never deployed?\nI just fought through this issue with a rabbitmq helm chart. I had to custom build a pause container from master to fix it. The rabbitmq helm chart uses for its liveness checks. It's a thin wrapper around a call to the rabbitmq-server daemon, which is not PID 1 (/pause is PID 1). The rabbitmq-server process forks some children to do the work and then they exit. Since the pause-amd64:3.0 is not reaping, those processes stick around as zombies. The liveness check runs every 5 seconds. After about 4 hours, there are about 27K zombies and the node begins failing to launch new containers because it's starved for resources. The pause container built from current master fixes that behavior, no zombies at all in the container.\nThe plan is to build a new version of pause-amd64 and then update the image referenced by Kubernetes. This means the default image will change in the next Kubernetes release. We can make the new image available once the freeze lifts and we can merge .\nLooks like this made it into 1.10", "commid": "kubernetes_issue_50865", "tokennum": 336}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a688c882943d891e578f38d10a181b608761cb3841c8683b7d4e998158b9799d", "query": "} func pvcDeletePolicyString(policy *apps.StatefulSetPersistentVolumeClaimRetentionPolicy) string { <ins> if policy == nil { return \"nullPolicy\" } </ins> const retain = apps.RetainPersistentVolumeClaimRetentionPolicyType const delete = apps.DeletePersistentVolumeClaimRetentionPolicyType switch {", "positive_passages": [{"docid": "doc-en-kubernetes-0282c95c8ddc11607ba516e065f4121126017f786957d03a031978171c244a62", "text": "The replicas is 3 but just create 1 pod 'web-0' and one pvc, then kube-controller-manager panic happend. Should create 3 pod and 3 pvc add '--feature-gates=StatefulSetAutoDeletePVC=true' arg for kube-controller-manager, then create statefulset with 2 replicas and volumeClaimTemplates. No response <details</details<details</details<details</details<details</details<details</details<details</details\n/sig apps\nI can reproduce the issue and want to fix it. It seems like variables cause . /assign\n/triage accepted\nGreat find! Does this only happen on an upgraded cluster? I'll spin up a cluster and see if the e2e test catches this problem.\nThe e2e tests are still passing on a 1.24 cluster, so I suspect this is an upgrade problem. I wonder if there are other holes here.\nI installed the Kubernetes 1.25 cluster directly using and still reproduced this issue, so it was probably not caused by upgrading the cluster.\nInteresting. I thought that would set the policy to be non-nil. Let's keep this bug open after you submit your PR as I think something else is going on here---I don't think we should be seeing the null policy in the first place.\nI suspect that somewhere accidentally set it to nil, and I'll keep looking at this code.\nI tried the following (and also with parallel pod management), and it didn't seem to cause the panic. This was a 1.24 cluster, maybe this is only happening on head versions?\nI just tried this on a kind cluster running on k8s head, and the problem didn't seem to reproduce. But this was setting the feature flag default in I wonder----does the api server need to have the feature gate as well? That would explain why defaulting wasn't happening.\nAs far as I'm concerned,I just set the in kube-controller-manager manifests to reproduce this issue. I repeat the yaml used as follows: I tested that in statefulset yaml, setting or not would cause the component to panic. The panic logs are the same as above, so ignore them here.", "commid": "kubernetes_issue_113319", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a688c882943d891e578f38d10a181b608761cb3841c8683b7d4e998158b9799d", "query": "} func pvcDeletePolicyString(policy *apps.StatefulSetPersistentVolumeClaimRetentionPolicy) string { <ins> if policy == nil { return \"nullPolicy\" } </ins> const retain = apps.RetainPersistentVolumeClaimRetentionPolicyType const delete = apps.DeletePersistentVolumeClaimRetentionPolicyType switch {", "positive_passages": [{"docid": "doc-en-kubernetes-bacc559e7a05833801486ab81cebdf65b8969406a4ba99bead3e0d4a0613defb", "text": "statefulset with : The environment\nI believe you---this doesn't seem to be well-documented, but it's my understanding that you need to set the feature gate on all of the system components. Obviously failing to do so shouldn't cause a panic, so thank you again for finding & fixing this bug! Let me ask around to see what the expected behavior is. I know there may be skew between kubelets and master versions, but I didn't expect to have to deal with skew between master components.\nI read the code, and now I understand what you mean. This feature gate must be enabled in both the and components. We need to describe it in the to prevent someone from ignoring the component, which also needs to enable the feature gate.\nI don't think we need all the system components, like the component, right? I read the original KEP documentation. This feature gate only involves components and :\nI had a bit of discussion about this with others. Because upgrades don't occur atomically, any feature gate has to work regardless of how the other system components are configured (things shouldn't panic!). I suppose if the cluster administrator wants to track what needs to be enabled on each feature they can try to sequence which component has which feature gate. If it were me I'd try to make all the components consistent though.\nThis is certainly a method, but it is a bit more cumbersome for the administrator. It is best to have a place for the document to be queried by the administrator and avoid confusion. I don't think everyone is very familiar with the k8s mechanism. I suggest adding a partial description to this section of the : Before: After: I can submit this PR on .\nThis is going to be true of any api change. When you tried to use it with only adding the controller manager feature gate, I think you would be able to set the retain policy, but there wouldn't be any defaulting or validation (?).\nI've seen other feature gates that say what components are needed to enable it to use the new feature. For example: If it's not necessary, then I close .\nonly adding the controller manager feature gate, I think you would be able to set the retain policy, but there wouldn't be any defaulting or validation (?). I remember just enabling it in kube-controller-manager.", "commid": "kubernetes_issue_113319", "tokennum": 500}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a688c882943d891e578f38d10a181b608761cb3841c8683b7d4e998158b9799d", "query": "} func pvcDeletePolicyString(policy *apps.StatefulSetPersistentVolumeClaimRetentionPolicy) string { <ins> if policy == nil { return \"nullPolicy\" } </ins> const retain = apps.RetainPersistentVolumeClaimRetentionPolicyType const delete = apps.DeletePersistentVolumeClaimRetentionPolicyType switch {", "positive_passages": [{"docid": "doc-en-kubernetes-dc6539ce5e1daf74890724a45ab3f8f9d1791d28b0765a687405f604711fc05a", "text": "it using the retain policy, but the statefulset does not have the policy from output of (It should be the apiserver authentication forbids it)\nYeah I think that makes sense. Thanks for finding this issue! After your PR with the panic fix is submitted, I think we can close this?\nYes. I agree. /close\nClosing this issue. <detailsIn response to : Yes. I agree. 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", "commid": "kubernetes_issue_113319", "tokennum": 117}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a6c7888653047e866b89738d62ef682b2c33577692edf0e5b92cc40b604b488a", "query": "\"os/exec\" \"path\" \"path/filepath\" <del> \"runtime\" </del> \"strconv\" \"strings\" \"sync\"", "positive_passages": [{"docid": "doc-en-kubernetes-2c477631a31f290ae271a7ca0a83a97399cbf63c4cfd883674b6ddce7387fc19", "text": "What happened: Latest kubelet + Windows Docker version 1.14.0-dev refused to start any containers, error output: \"invalid option: Windows does not support MemorySwap\" How to reproduce it (as minimally and precisely as possible): It's always reproducible with Windows Docker 1.14.0-dev + latest kubelet code base. Anything else do we need to know: It didn't happen for Windows Docker 1.12.2-cs2-ws-beta. The reason behind the issue was because new code was for Windows Docker to check Resources parameters, it doesn't accept a non-zero value for MemorySwap: But kubelet was default to set an unlimited (-1) value. The issue was gone in my setup after applied a private fix to disable MemorySwap by set it to zero for Windows.", "commid": "kubernetes_issue_39003", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a6df48e174beefffa0800f0afb38d17410ec77c007cc0658e26039ff501b959e", "query": "// Write 10 lines to log file. // Let ReadLogs start. time.Sleep(50 * time.Millisecond) for line := 0; line < 10; line++ { // Write the first three lines to log file now := time.Now().Format(types.RFC3339NanoLenient)", "positive_passages": [{"docid": "doc-en-kubernetes-d28453dfc6bcf829133f35627fac482c86b9caf8a20943cea67f030688a8c436", "text": "Runs k8s with master golang: test Failure was observed on Aug 25th, it is passing after that. However it can be reproduced with stress tool. No response No response It is failing on both ppc and x86 architectures. Steps to reproduce: up golang tip version. clone kubernetes master /sig testing\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\nit is a sig node test, sig testing charter is not about doing or maintain tests, we need to remove that old mindset of having a QA department, that is not how software development works or should work :) Besides, thanks for spotting it and submittn a patch /sig node /remove-sig testing\nFlaky in\nmerging this PR will fix the issue", "commid": "kubernetes_issue_121564", "tokennum": 237}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a701d97f6b606857ad676eaf7e3e874536f0587c7e9331d78d581bc9fc9ae5b5", "query": "\"k8s.io/kubernetes/pkg/kubelet/api/v1alpha1/stats\" \"k8s.io/kubernetes/test/e2e/framework\" <ins> systemdutil \"github.com/coreos/go-systemd/util\" </ins> . \"github.com/onsi/ginkgo\" . \"github.com/onsi/gomega\" \"github.com/onsi/gomega/gstruct\"", "positive_passages": [{"docid": "doc-en-kubernetes-237446a2101b1d0e3896762c3997d0b07e17e89bcd32bef5edcdc8a493c92d82", "text": "Kubernetes version (use ): 6 Environment: GCE What happened: I created a cluster for Heapster testing purposes to debug failing test in It turned out that Summary API does not export system/misc stats in SystemContainers section (though there are kubelet and docker stats). Everything works as expected on nodes. See also https://k8s-\nWhat node OS were you using? We don't create the system (misc) container on systemd, so it's expected that GCI nodes don't report those stats.\nThe default configuration for 1.4, which is: master: GCI nodes: Container VM\nAre the nodes running 1.4.6 too? There was a bug with this in 1.4.5, but it should have been fixed in 1.4.6.\nYes, both are running in 1.4.6. If you want to reproduce from Heapster current head run . It will take some time and as a side effect you should have a cluster with the mentioned problem. This was catch by integration tests and I temporary disabled the check here\nif you have spare cycles, can you look into this?\nfriendly ping\nLooking at it now\nI have found a couple things so far. On the containerVM nodes, cadvisor is exporting a container with \"name\": \"/system\" On the GCI Master, cadvisor is exporting a container with \"name\": \"\" The has this: \"{% set system_container = \"--system-cgroups=/system\" -%}\" (/system is the default misc container name) So the real question is: Should cadvisor export \"/system\" instead of \"\" on GCI? Or should we be configuring GCI to use \"--system-\"?\nI thought we fix this very issue for 1.4 branch by a while back. Are you running into the same issue with 1.5?\nI think I told you the wrong thing earlier. We don't support the misc (/system) cgroup on systemd systems (I can't remember why, but it was an explicit decision - or might know). The is something different, I believe a base systemd cgroup (slice). As for the misc container on ContainerVM nodes, we've been testing for the misc container in 1.5+ in the summary api test (https://k8s-) for a while, and I haven't seen this issue.", "commid": "kubernetes_issue_37453", "tokennum": 538}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a701d97f6b606857ad676eaf7e3e874536f0587c7e9331d78d581bc9fc9ae5b5", "query": "\"k8s.io/kubernetes/pkg/kubelet/api/v1alpha1/stats\" \"k8s.io/kubernetes/test/e2e/framework\" <ins> systemdutil \"github.com/coreos/go-systemd/util\" </ins> . \"github.com/onsi/ginkgo\" . \"github.com/onsi/gomega\" \"github.com/onsi/gomega/gstruct\"", "positive_passages": [{"docid": "doc-en-kubernetes-c190eb06e0eb058949f528f1af5886fe17cab35cd1b33a69ea2cddc6a3fc8812", "text": "So if this is still reproducible, it's limited to 1.4. See this the bug was created for the post-fix.\nFound the explanation here: The should use the flag to know the location that has the processes that are associated with , but it should not modify the cgroups of existing processes on the system during bootstrapping of the node. This is because is the on the host and it has not delegated authority to the to change how it manages .\nIIUC this is intended behavior on systemd nodes. Based on the explanation provided, the kubelet doesnt have the authority to control \"misc\" processes on systemd.\n+1. \"misc\" is just a bandaid for cvm. , David Ashpole <:\nOk, so I'm closing this issue.", "commid": "kubernetes_issue_37453", "tokennum": 168}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a77481b09911abf81cebe0f1adf50907281f6589dc406684ffa0acdde3888577", "query": "```yaml kind: Service apiVersion: v1beta1 <del> id: nginxExample </del> <ins> # must be a DNS compatible name id: nginx-example </ins> # the port that this service should serve on port: 8000 # just like the selector in the replication controller, # but this time it identifies the set of pods to load balance # traffic to. selector: <del> - name: nginx </del> <ins> name: nginx </ins> # the container on each pod to connect to, can be a name # (e.g. 'www') or a number (e.g. 80) containerPort: 80", "positive_passages": [{"docid": "doc-en-kubernetes-8b28935a84f88ac18c7fc65931585a933c76320eb13cd6ef7170c583b31097e6", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: cAdvisor has a option to only collect docker related cgroups. Kubelet stats api now supports allocatable cgroup, /kubepods, for the runtime cgroup and the kubelet cgroup. But with settings, Kubelet stats api can not query pod related cgroups metrics. FYI: What you expected to happen: should be compatible with kubelet stats api.\n/cc\n/sig node /sig instrumentation\nadd to cadvisor in A comma-separated list of cgroup path prefix that needs to be collected even docker-only is specified bump cadvisor dep for Kubernetes setting to\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_61994", "tokennum": 525}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a77481b09911abf81cebe0f1adf50907281f6589dc406684ffa0acdde3888577", "query": "```yaml kind: Service apiVersion: v1beta1 <del> id: nginxExample </del> <ins> # must be a DNS compatible name id: nginx-example </ins> # the port that this service should serve on port: 8000 # just like the selector in the replication controller, # but this time it identifies the set of pods to load balance # traffic to. selector: <del> - name: nginx </del> <ins> name: nginx </ins> # the container on each pod to connect to, can be a name # (e.g. 'www') or a number (e.g. 80) containerPort: 80", "positive_passages": [{"docid": "doc-en-kubernetes-c993cfc824e8b144526f19f7f90c37dca7b5b7104e06f115b259fa72f1d9ae68", "text": "/close\nClosing 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", "commid": "kubernetes_issue_61994", "tokennum": 71}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a7903da6be812df496914eab316874f755b430ef5ba0268f91fe4f7c225f0f24", "query": "}) }) <ins> ginkgo.Context(\"when creating a pod in the host PID namespace\", func() { makeHostPidPod := func(podName, image string, command []string, hostPID bool) *v1.Pod { return &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name: podName, }, Spec: v1.PodSpec{ RestartPolicy: v1.RestartPolicyNever, HostPID:       hostPID, Containers: []v1.Container{ { Image:   image, Name:    podName, Command: command, }, }, }, } } createAndWaitHostPidPod := func(podName string, hostPID bool) { podClient.Create(makeHostPidPod(podName, busyboxImage, []string{\"sh\", \"-c\", \"pidof nginx || true\"}, hostPID, )) podClient.WaitForSuccess(podName, framework.PodStartTimeout) } nginxPid := \"\" ginkgo.BeforeEach(func() { nginxPodName := \"nginx-hostpid-\" + string(uuid.NewUUID()) podClient.CreateSync(makeHostPidPod(nginxPodName, imageutils.GetE2EImage(imageutils.Nginx), nil, true, )) output := f.ExecShellInContainer(nginxPodName, nginxPodName, \"cat /var/run/nginx.pid\") nginxPid = strings.TrimSpace(output) }) ginkgo.It(\"should show its pid in the host PID namespace [NodeFeature:HostAccess]\", func() { busyboxPodName := \"busybox-hostpid-\" + string(uuid.NewUUID()) createAndWaitHostPidPod(busyboxPodName, true) logs, err := e2epod.GetPodLogs(f.ClientSet, f.Namespace.Name, busyboxPodName, busyboxPodName) if err != nil { framework.Failf(\"GetPodLogs for pod %q failed: %v\", busyboxPodName, err) } pids := strings.TrimSpace(logs) framework.Logf(\"Got nginx's pid %q from pod %q\", pids, busyboxPodName) if pids == \"\" { framework.Failf(\"nginx's pid should be seen by hostpid containers\") } pidSets := sets.NewString(strings.Split(pids, \" \")...) if !pidSets.Has(nginxPid) { framework.Failf(\"nginx's pid should be seen by hostpid containers\") } }) ginkgo.It(\"should not show its pid in the non-hostpid containers [NodeFeature:HostAccess]\", func() { busyboxPodName := \"busybox-non-hostpid-\" + string(uuid.NewUUID()) createAndWaitHostPidPod(busyboxPodName, false) logs, err := e2epod.GetPodLogs(f.ClientSet, f.Namespace.Name, busyboxPodName, busyboxPodName) if err != nil { framework.Failf(\"GetPodLogs for pod %q failed: %v\", busyboxPodName, err) } pids := strings.TrimSpace(logs) framework.Logf(\"Got nginx's pid %q from pod %q\", pids, busyboxPodName) pidSets := sets.NewString(strings.Split(pids, \" \")...) if pidSets.Has(nginxPid) { framework.Failf(\"nginx's pid should not be seen by non-hostpid containers\") } }) }) </ins> ginkgo.Context(\"when creating a pod in the host IPC namespace\", func() { makeHostIPCPod := func(podName, image string, command []string, hostIPC bool) *v1.Pod { return &v1.Pod{", "positive_passages": [{"docid": "doc-en-kubernetes-b8a3e3a5c22dc8491069aa612d226f113bfee5a5c0b17ff9cb35a90b4b6a10ba", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: , Which test(s) are failing: Since when has it been failing: since this PR introduced them Testgrid link: Note that this is the flakiest test in both dashboards, and failing quite frequently. Reason for failure: unknown Anything else we need to know: cc\n/sig node\nsee: , both getting empty PID and multiple PIDs.\nopened revert at\nfor discoverability for the release team /priority critical-urgent /milestone v1.17", "commid": "kubernetes_issue_84209", "tokennum": 127}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a7fd09a436b53fb7dfa652732c093e614b5e19b8b01acf6471e820421d9d938c", "query": "m.mutex.Lock() defer m.mutex.Unlock() <del> if _, exists := m.endpoints[resourceName]; exists { </del> <ins> if ep, exists := m.endpoints[resourceName]; exists { </ins> m.markResourceUnhealthy(resourceName) <del> klog.V(2).InfoS(\"Endpoint became unhealthy\", \"resourceName\", resourceName, \"endpoint\", m.endpoints[resourceName]) } </del> <ins> klog.V(2).InfoS(\"Endpoint became unhealthy\", \"resourceName\", resourceName, \"endpoint\", ep) </ins> <del> m.endpoints[resourceName].e.setStopTime(time.Now()) </del> <ins> ep.e.setStopTime(time.Now()) } </ins> } // PluginListAndWatchReceiver receives ListAndWatchResponse from a device plugin", "positive_passages": [{"docid": "doc-en-kubernetes-5bc96dc4d12a3dcdc2937e744d86eb7f421f613963225d2302a19e261319d9fc", "text": "Seen in and in No hits on stack strace nothing evident on the git history of the test itself, but it seems , so most probable something in the device manager has changed? /sig node /kind flake\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\n/cc as this flakes a lot in", "commid": "kubernetes_issue_121451", "tokennum": 142}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a83cd53bae5825829bd5f8d34cf762ad40cdf7fb413b5b2cadce3c6877143e08", "query": "allErrs = append(allErrs, field.Duplicate(fldPath.Child(\"name\"), driver.Name)) } driverNamesInSpecs.Insert(driver.Name) <del> topoKeys := make(sets.String) </del> <ins> topoKeys := sets.New[string]() </ins> for _, key := range driver.TopologyKeys { if len(key) == 0 { allErrs = append(allErrs, field.Required(fldPath, key))", "positive_passages": [{"docid": "doc-en-kubernetes-c6679bcd8f59ea95eb0b6a4e2bf394545d09b32db20c61705567c0727bbb7817", "text": "It seems to be valid to add here. Would you like to open a pull request for it? this is like a cleanup, as the set insert will skip and the validation will do twice. is used to track bugs. I suggest you open a PR for that if you like.\n/sig storage\nI think adding ` == true and we didn't skip, it will insert set twice I believe? wasn't notice that at first glance. However, I can file a PR now\n/triage accepted\nThe label cannot be applied. Only GitHub organization members can add the label. <detailsIn response to : /triage accepted 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\n/triage accepted\nPlease feel free to submit a PR.", "commid": "kubernetes_issue_117027", "tokennum": 176}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a845d1c61cf7444ea9e038c7d67dcecdcb1834ec56a5a39866b3820705feb46d", "query": "e.clientConn.Close() } <del> // dial establishes the gRPC communication with the registered device plugin. </del> <ins> // dial establishes the gRPC communication with the registered device plugin. https://godoc.org/google.golang.org/grpc#Dial </ins> func dial(unixSocketPath string) (pluginapi.DevicePluginClient, *grpc.ClientConn, error) { <del> c, err := grpc.Dial(unixSocketPath, grpc.WithInsecure(), </del> <ins> c, err := grpc.Dial(unixSocketPath, grpc.WithInsecure(), grpc.WithBlock(), grpc.WithTimeout(10*time.Second), </ins> grpc.WithDialer(func(addr string, timeout time.Duration) (net.Conn, error) { return net.DialTimeout(\"unix\", addr, timeout) }),", "positive_passages": [{"docid": "doc-en-kubernetes-3e8f9b25d1f3d96c25ea3e7b882f872baf67d41cad6a3bbcf2df0e192dbdfda5", "text": "This is not 100% reproducable in my cluster. There is 20% chance of failing in my environment.\n/area hw-accelerators mentioned a root cause that might be due to unit tests sharing the same Unix socket and interfering with each others. cc\nCan you please share latest commit id of your code base using ?\nThanks very much, can you try the follow command please:\n/assign\nThe latest commit id of my code base:\nI found this is not 100% reproducable in my cluster. There is 20% chance of failing in my environment.\nResult of go test command:\n/sig scheduling\nThanks!\nHi, does these unit tests pass with PR\nI run 100 times without failure.\nGood to here that, Nice work! Thanks!", "commid": "kubernetes_issue_58281", "tokennum": 154}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a86859753535cf42bb99a82c1fcaa44dfe5c935f7b008dba9c957466dcec9c92", "query": "type LRUExpireCache struct { cache *lru.Cache <del> lock  sync.RWMutex </del> <ins> lock  sync.Mutex </ins> } func NewLRUExpireCache(maxSize int) *LRUExpireCache {", "positive_passages": [{"docid": "doc-en-kubernetes-125faf475ef5c9fadc127cee08d3d538bc2825eff7d3fd81be9f088e2d4a0dbf", "text": "Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see ): No What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): \"LRUExpireCache\" Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT What happened: requires write lock since needs to manipulate its list to track recently used item. Currently it uses read lock so it may introduce race condition. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else do we need to know:\nThis was fixed in", "commid": "kubernetes_issue_31081", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a884b6f9cb8344dc90ae47cb46a2a5bee81676705d8985974446e1ec66074cc2", "query": "\"k8s.io/apimachinery/pkg/apis/meta/v1/unstructured\" \"k8s.io/apimachinery/pkg/runtime\" \"k8s.io/apimachinery/pkg/runtime/schema\" <ins> \"k8s.io/apimachinery/pkg/util/sets\" </ins> \"k8s.io/apimachinery/pkg/util/wait\" \"k8s.io/client-go/dynamic\" \"k8s.io/client-go/kubernetes\"", "positive_passages": [{"docid": "doc-en-kubernetes-a36678f387087dd8252401a5249426873ced2ebb26644cae4efea96ce80ca1f6", "text": "reported that conformance testing with the latest version of sonobuoy against a version 1.29.0-alpha.3 cluster fails on the support the 1.17 Sample API Server using the current Aggregator test: , related to I found the reason why the test is working fine in Kubernetes CI jobs but fails with sonobuoy is because the service account used by sonobuoy \"sonobuoy-serviceaccount\" doesn't have read permission of the non-resource url \"/\", which is used by the test to confirm the removal of group path: The permission of \"sonobuoy-serviceaccount\" is as below: There may be two ways to fix it: the RBAC rule of sonobuoy to include \"get\" of \"/\". However, could other test runners encounter this issue? Is there a doc listing the required permissions for running e2e tests? the e2e to skip checking the removal of the group path if the service account doesn't have permission to access the root path. Which way do we usually prefer? Running e2e with sonobuoy should succeed. a v1.29.0-alpha.3 cluster. No response <details</details<details</details<details</details<details</details<details</details<details</details\nimplemented this solution.\n/sig api-machinery\nthank you for opening this issue and working on a solution. I'm probably not the right person to decide on which solution is preferred. From my perspective, either solution is fine.\nNote: Sonobuoy is not owned by any Kubernetes SIG. At most it is between SIG Architecture and the CNCF to choose whether to recommend it for running tests. SIG Testing owns the e2e image that sonobuoy can be used to schedule but not sonobuoy. IMHO this is a bug in running the tests via a pod, which is not how we develop the tests (they're run outside the cluster, by a cluster admin account typically). I would say 1) is the correct answer. xref: /sig architecture /sig testing /triage accepted cc\nthanks for your comment. I guess 1) means non of the existing sonobuoy versions can pass K8s conformance test against a cluster 1.29.0-alpha3, as the RBAC rule is hardcoded.", "commid": "kubernetes_issue_121985", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a884b6f9cb8344dc90ae47cb46a2a5bee81676705d8985974446e1ec66074cc2", "query": "\"k8s.io/apimachinery/pkg/apis/meta/v1/unstructured\" \"k8s.io/apimachinery/pkg/runtime\" \"k8s.io/apimachinery/pkg/runtime/schema\" <ins> \"k8s.io/apimachinery/pkg/util/sets\" </ins> \"k8s.io/apimachinery/pkg/util/wait\" \"k8s.io/client-go/dynamic\" \"k8s.io/client-go/kubernetes\"", "positive_passages": [{"docid": "doc-en-kubernetes-4545476cbce0605bfe46d5a01c41b8f4cf7b5ac07772bfb1748611bc506e90ef", "text": "I will file an issue to sonobuoy first.\nquestion here is what are the set of client permissions required to run the conformance suite? perhaps a level of access or a more granular recommendation should be documented. what is your take on the root path requirement as approver for: EDIT: slack thread:\nI agree, we already require e.g. privileged pods for a long time in conformance tests and we should make it clear that we expect a highly privileged client.\n+1 for what is saying, that we should expect that the user running the tests has required permissions. These tests are not built for being run unprivileged.\ni wanted to PR the admin note in our conformance docs under sig-arch, but then i saw this: so broke this guarantee. sounds like SIG Arch needs to comment.\nThis statement surprises me. Root discovery is one of the least-privileged permissions you can have on a cluster. For years this was even open for unauthorized users on the internet (if your api endpoint has been exposed). In other words, just add the permission. While thinking about it, it is surprising that the user in question does not have this access already. Don't we allow that for every authorized user?\nIn contrast, I hope that lots of privileged operations are tested by conformance today. If we don't test things like admission webhooks for example, we have much bigger problems. And admission webhooks are basically equivalent to cluster-admin.\nthat is outdated, we use hostNetwork pods one some of the tests IIRC\nlooks like we don't. before this ticket, i was under the impression that the conformance suite already requires admin and that all testers (like Sonobuoy) use admin level credentials. it is non-privileged (e.g., does not require root on nodes, access to raw network interfaces, or cluster admin permissions) looks like we may have to change that sentence completely.\nWould have expected it here: The PR in question explicitly fixes the result returned by . If that is part of conformance (IMO it should), every conformance test needs access it obviously. Whether we require admin, or we add it manually, either would work.", "commid": "kubernetes_issue_121985", "tokennum": 474}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a884b6f9cb8344dc90ae47cb46a2a5bee81676705d8985974446e1ec66074cc2", "query": "\"k8s.io/apimachinery/pkg/apis/meta/v1/unstructured\" \"k8s.io/apimachinery/pkg/runtime\" \"k8s.io/apimachinery/pkg/runtime/schema\" <ins> \"k8s.io/apimachinery/pkg/util/sets\" </ins> \"k8s.io/apimachinery/pkg/util/wait\" \"k8s.io/client-go/dynamic\" \"k8s.io/client-go/kubernetes\"", "positive_passages": [{"docid": "doc-en-kubernetes-06abc1218304c92779dae2744e33107a4d26263c1c54e4453f3f92a1949c2aa2", "text": "adding to milestone and making release blocking ... we should not release 1.29 in a state that the most commonly used conformance tool will fail\nIMO we should clarify the state and go fix the tool, but we should keep the test and we should NOT add skip. Conformance docs are not a release artifact, and sonobuoy release lifecycle is not a conformance artifact. If we can't get sonobuoy working in a reasonable time, we already know the tests can be run by scheduling the image (which is ours) directly with kubectl instead and we can document that in the upstream conformance docs. We need to fix the for this image: ,%20master%20(dev) And it should probably be to release-blocking in the future.\nit looks like the e2e change made in was not consciously made part of conformance, it was just trying to functionally test the bugfix being made. For 1.29, I think we should revert the change to and make an integration test that validates the fix instead. We can revisit whether content of is part of conformance or not for 1.30\nI opened to revert the e2e change and move the functional test to an integration test\nFiled to try to get the image job passing again.\nWe probably need another issue to track 1.30 follow-up?\nIf no one has done it, I could create another issue and follow up with the items that have been discussed here: outdated privilege requirement in commonly used conformance tools like sonobuoy aware of the required priviledge to avoid similar situations in the future. permission of GET \"/\" to authorized users via the role for root discovery.", "commid": "kubernetes_issue_121985", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a8dd1917797bc5f482daee60bf0f29aa78e79fe2e7a014099ddb78a0099f1600", "query": "\"attachRequired\":       \"attachRequired indicates this CSI volume driver requires an attach operation (because it implements the CSI ControllerPublishVolume() method), and that the Kubernetes attach detach controller should call the attach volume interface which checks the volumeattachment status and waits until the volume is attached before proceeding to mounting. The CSI external-attacher coordinates with CSI volume driver and updates the volumeattachment status when the attach operation is complete. If the CSIDriverRegistry feature gate is enabled and the value is specified to false, the attach operation will be skipped. Otherwise the attach operation will be called.nnThis field is immutable.\", \"podInfoOnMount\":       \"If set to true, podInfoOnMount indicates this CSI volume driver requires additional pod information (like podName, podUID, etc.) during mount operations. If set to false, pod information will not be passed on mount. Default is false. The CSI driver specifies podInfoOnMount as part of driver deployment. If true, Kubelet will pass pod information as VolumeContext in the CSI NodePublishVolume() calls. The CSI driver is responsible for parsing and validating the information passed in as VolumeContext. The following VolumeConext will be passed if podInfoOnMount is set to true. This list might grow, but the prefix will be used. \"csi.storage.k8s.io/pod.name\": pod.Name \"csi.storage.k8s.io/pod.namespace\": pod.Namespace \"csi.storage.k8s.io/pod.uid\": string(pod.UID) \"csi.storage.k8s.io/ephemeral\": \"true\" if the volume is an ephemeral inline volumen                                defined by a CSIVolumeSource, otherwise \"false\"nn\"csi.storage.k8s.io/ephemeral\" is a new feature in Kubernetes 1.16. It is only required for drivers which support both the \"Persistent\" and \"Ephemeral\" VolumeLifecycleMode. Other drivers can leave pod info disabled and/or ignore this field. As Kubernetes 1.15 doesn't support this field, drivers can only support one mode when deployed on such a cluster and the deployment determines which mode that is, for example via a command line parameter of the driver.nnThis field is immutable.\", \"volumeLifecycleModes\": \"VolumeLifecycleModes defines what kind of volumes this CSI volume driver supports. The default if the list is empty is \"Persistent\", which is the usage defined by the CSI specification and implemented in Kubernetes via the usual PV/PVC mechanism. The other mode is \"Ephemeral\". In this mode, volumes are defined inline inside the pod spec with CSIVolumeSource and their lifecycle is tied to the lifecycle of that pod. A driver has to be aware of this because it is only going to get a NodePublishVolume call for such a volume. For more information about implementing this mode, see https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html A driver can support one or more of these modes and more modes may be added in the future.nnThis field is immutable.\", <del> \"storageCapacity\":      \"If set to true, storageCapacity indicates that the CSI volume driver wants pod scheduling to consider the storage capacity that the driver deployment will report by creating CSIStorageCapacity objects with capacity information.nnThe check can be enabled immediately when deploying a driver. In that case, provisioning new volumes with late binding will pause until the driver deployment has published some suitable CSIStorageCapacity object.nnAlternatively, the driver can be deployed with the field unset or false and it can be flipped later when storage capacity information has been published.nnThis field is immutable.nnThis is a beta field and only available when the CSIStorageCapacity feature is enabled. The default is false.\", </del> <ins> \"storageCapacity\":      \"If set to true, storageCapacity indicates that the CSI volume driver wants pod scheduling to consider the storage capacity that the driver deployment will report by creating CSIStorageCapacity objects with capacity information.nnThe check can be enabled immediately when deploying a driver. In that case, provisioning new volumes with late binding will pause until the driver deployment has published some suitable CSIStorageCapacity object.nnAlternatively, the driver can be deployed with the field unset or false and it can be flipped later when storage capacity information has been published.nnThis field was immutable in Kubernetes <= 1.22 and now is mutable.nnThis is a beta field and only available when the CSIStorageCapacity feature is enabled. The default is false.\", </ins> \"fsGroupPolicy\":        \"Defines if the underlying volume supports changing ownership and permission of the volume before being mounted. Refer to the specific FSGroupPolicy values for additional details. This field is beta, and is only honored by servers that enable the CSIVolumeFSGroupPolicy feature gate.nnThis field is immutable.nnDefaults to ReadWriteOnceWithFSType, which will examine each volume to determine if Kubernetes should modify ownership and permissions of the volume. With the default policy the defined fsGroup will only be applied if a fstype is defined and the volume's access mode contains ReadWriteOnce.\", \"tokenRequests\":        \"TokenRequests indicates the CSI driver needs pods' service account tokens it is mounting volume for to do necessary authentication. Kubelet will pass the tokens in VolumeContext in the CSI NodePublishVolume calls. The CSI driver should parse and validate the following VolumeContext: \"csi.storage.k8s.io/serviceAccount.tokens\": {n  \"<audience>\": {n    \"token\": <token>,n    \"expirationTimestamp\": <expiration timestamp in RFC3339>,n  },n  ...n}nnNote: Audience in each TokenRequest should be different and at most one token is empty string. To receive a new token after expiry, RequiresRepublish can be used to trigger NodePublishVolume periodically.\", \"requiresRepublish\":    \"RequiresRepublish indicates the CSI driver wants `NodePublishVolume` being periodically called to reflect any possible change in the mounted volume. This field defaults to false.nnNote: After a successful initial NodePublishVolume call, subsequent calls to NodePublishVolume should only update the contents of the volume. New mount points will not be seen by a running container.\",", "positive_passages": [{"docid": "doc-en-kubernetes-cdccab911562ccfffce851739652bcccdbeabc99e62d699c46baa58ef67f3bbe", "text": "Up to 1.21, that field is immutable. That means in practice, a CSIDriver object has to be deleted and then re-created with a different value instead. Mutation via delete/created is unnecessarily complex and as the only consumer of that field (the kube-scheduler) can handle mutation just fine (it'll always ask the informer cache for the current value), it's better to allow mutation.\n/sig storage /assign\nThis is independent of allowing other fields to become mutable, but that might also make sense.\n/triage accepted", "commid": "kubernetes_issue_100089", "tokennum": 125}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a8e7be87469f3db4b87b353f0c5442e105958d66686a072ebeba0ec2f9c5238f", "query": "allErrs := errs.ValidationErrorList{} allErrs = append(allErrs, ValidateObjectMetaUpdate(&oldNamespace.ObjectMeta, &newNamespace.ObjectMeta).Prefix(\"metadata\")...) newNamespace.Spec = oldNamespace.Spec <ins> if newNamespace.DeletionTimestamp.IsZero() { if newNamespace.Status.Phase != api.NamespaceActive { allErrs = append(allErrs, errs.NewFieldInvalid(\"Status.Phase\", newNamespace.Status.Phase, \"A namespace may only be in active status if it does not have a deletion timestamp.\")) } } else { if newNamespace.Status.Phase != api.NamespaceTerminating { allErrs = append(allErrs, errs.NewFieldInvalid(\"Status.Phase\", newNamespace.Status.Phase, \"A namespace may only be in terminating status if it has a deletion timestamp.\")) } } </ins> return allErrs }", "positive_passages": [{"docid": "doc-en-kubernetes-859a8b847337ca2cf9879726f3bdb71f0db5559ee2589591ceae612e41f71a1b", "text": "There is a funny subtle behvaiour in get namespaces, in which if i call more than one time, it seems that the removal from Terminating state is accelarated. It seems this might indicate a bug, or maybe its not a bug and the eventual semantics of is a little funny sometimes. in any case, here's what we are seeing : 1) when i delete a namespace the first time usning kubectl, we get a state change to . that is correct, of course. 2) but ... if make the call a second time, then the same status line is immediately removed from . Expected behaviour : A second call to \"kubectl delete ...\" shouldn't have any effect on the timing of removal of a namespace from 'Terminating' state*... So i guess there is some \"eventual consistency\" subtle bug that is resolved by repeated calls to\nsuggests this may not be e bug, maybe its just the etcd eventual deleter thingy.\nLooks to definitely be a bug. The 2nd delete seems to have interrupted the delete process and artifacts (like events) from the namespace still exist in etcd.\ninvestigating...\noops, see the error, will submit a fix.\nI have a fix, but need a test case, will submit PR tomorrow AM", "commid": "kubernetes_issue_6633", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a8ecd5f427bafb546097a1791a95d81e1e2cf9cb3776f47c98f8a6cc9c76e25d", "query": "opts.Client = c opts.PodName = name opts.Namespace = ns <ins> // TODO: opts.Run sets opts.Err to nil, we need to find a better way stderr := opts.Err </ins> if err := opts.Run(); err != nil { <del> fmt.Fprintf(opts.Err, \"Error attaching, falling back to logs: %vn\", err) </del> <ins> fmt.Fprintf(stderr, \"Error attaching, falling back to logs: %vn\", err) </ins> req, err := f.LogsForObject(pod, &api.PodLogOptions{Container: ctrName}) if err != nil { return err", "positive_passages": [{"docid": "doc-en-kubernetes-b371ee8508434fd0fa06120fe5733e14a37c0788b05c28b7017350eace3dad7d", "text": "This was build from master earlier today.\ncc This should be fixed before v1.4\nThis is critical\nThis needs to be tracked as a 1.4 blocker\nETA for resolution: This afternoon This is in the process of being cherrypicked", "commid": "kubernetes_issue_32206", "tokennum": 49}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a9036c71391bef63fbd276b3b23ffa2572e4e4d5fe9611814be8a20ab57999b7", "query": ") const ( <del> defaultSandboxImage = \"gcr.io/google_containers/pause-amd64:3.0\" </del> <ins> defaultSandboxImage = \"gcr.io/google_containers/pause-amd64:3.1\" </ins> // Various default sandbox resources requests/limits. defaultSandboxCPUshares int64 = 2", "positive_passages": [{"docid": "doc-en-kubernetes-a834f77ddd825b3d04a660aa7c11d0734893e4dcde6e0d4a7399e3b3daf56428", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: the pause-amd64:3.0 image on has an empty schema2 manifest, which prevents is from being pulled by proxy/caches which only support V2 registries. What you expected to happen: Being able to pull ` using a V2 manifest compatible client. Anything else we need to know?: The proxy/cahce is requesting this\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nAfter talking with , he mentionned the following\nAFAIK, does not support well. After inspecting the image, you can find is still using manifest v1.\n/cc FYI\nIm not sure which exact version x sch\u00e9ma X is needed. What I know is that we can download through the proxy/cache all other Kubernetes kube-system images, only the pause image is giving us trouble. Therefore, I would say that having the image available using the same format as the other kube-system images would be the request here.\nYeah, we haven't updated the pause image in a while, since it doesn't really ever change. I'm not sure whether rebuilding + pushing over the existing tag is safe, or if we should bump to or something. thoughts?\nIf we do rebuilding/updating the image, that would help and a bunch of similar issues.\nit's better/save to go with new tag\nI didn't realize there were changes to the pause binary that were never actually deployed. It seems like we should probably just do that (and bump the tag).\nthat sounds great. Any idea when the existing 3.0 tag could be pushed again?\nWe shouldn't push over the 3.0 tag; we should push a 3.1 or 4.0 tag instead. I'm not sure who owns the pause container who should drive this. Maybe sig-node and/or\nIt seems like it should be sig-node. I'll look into it.\nThe new container has been built, can you test with\nIts working! thanks! I was able to pull it through our artifactory proxy , Lee Verberne <:\nexcellent, thanks for checking. /assign", "commid": "kubernetes_issue_56253", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a9036c71391bef63fbd276b3b23ffa2572e4e4d5fe9611814be8a20ab57999b7", "query": ") const ( <del> defaultSandboxImage = \"gcr.io/google_containers/pause-amd64:3.0\" </del> <ins> defaultSandboxImage = \"gcr.io/google_containers/pause-amd64:3.1\" </ins> // Various default sandbox resources requests/limits. defaultSandboxCPUshares int64 = 2", "positive_passages": [{"docid": "doc-en-kubernetes-7628cd26f0dafa992a4ea43a6c68b9bcdbf056fca43ee32b40ab60cef4154c17", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: pause does not reap zombie processes using the default pause container provided by What you expected to happen: should include the up to date pause code to reap zombie processes when using docker = 1.13.1 found here How to reproduce it (as minimally and precisely as possible): a.out will leave a zombie process that is not cleaned up Anything else we need to know?: Building the pause container from master solves this issue Related: Environment: Kubernetes version (use ): 1.7.0+ Cloud provider or hardware configuration**: N/A OS (e.g. from /etc/os-release): CentOS 7 Kernel (e.g. ): 4.10.13+ Install tools: Others: docker = 1.13.1\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\ni get a simliar problem when i run crond service in pod container, every day it makes some [anacron] zombie progresses UID PID PPID C STIME TTY TIME CMD root 1 0 0 Nov14 ? 00:00:00 /pause root 7 0 0 Nov14 ? 00:00:00 /usr/local/bin/dumb-init /usr/lo root 13 7 0 Nov14 ? 00:00:00 nginx: master process /usr/local nobody 21 13 0 Nov14 ? 00:00:01 nginx: worker process nobody 22 13 0 Nov14 ? 00:00:07 nginx: worker process nobody 23 13 0 Nov14 ? 00:00:07 nginx: worker process nobody 24 13 0 Nov14 ? 00:00:05 nginx: worker process root 77 1 0 Nov14 ? 00:00:00 [anacron] root 1 0 00:01 ? 00:00:00 [anacron] <defunctroot 1 0 01:01 ? 00:00:00 [anacron] <defunctroot 1 0 02:01 ?", "commid": "kubernetes_issue_50865", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a9036c71391bef63fbd276b3b23ffa2572e4e4d5fe9611814be8a20ab57999b7", "query": ") const ( <del> defaultSandboxImage = \"gcr.io/google_containers/pause-amd64:3.0\" </del> <ins> defaultSandboxImage = \"gcr.io/google_containers/pause-amd64:3.1\" </ins> // Various default sandbox resources requests/limits. defaultSandboxCPUshares int64 = 2", "positive_passages": [{"docid": "doc-en-kubernetes-6179feaaee46a15cd909bb088c82657b9b59fba8efdee1296995076588512032", "text": "00:00:00 [anacron] <defunctroot 1 0 03:01 ? 00:00:00 [anacron] <defunctroot 0 0 11:49 ? 00:00:00 /bin/bash root 0 1 19:15 ? 00:00:00 /bin/bash root 0 19:15 ? 00:00:00 ps -ef !\nDo we know why this was never resolved / was never deployed?\nI just fought through this issue with a rabbitmq helm chart. I had to custom build a pause container from master to fix it. The rabbitmq helm chart uses for its liveness checks. It's a thin wrapper around a call to the rabbitmq-server daemon, which is not PID 1 (/pause is PID 1). The rabbitmq-server process forks some children to do the work and then they exit. Since the pause-amd64:3.0 is not reaping, those processes stick around as zombies. The liveness check runs every 5 seconds. After about 4 hours, there are about 27K zombies and the node begins failing to launch new containers because it's starved for resources. The pause container built from current master fixes that behavior, no zombies at all in the container.\nThe plan is to build a new version of pause-amd64 and then update the image referenced by Kubernetes. This means the default image will change in the next Kubernetes release. We can make the new image available once the freeze lifts and we can merge .\nLooks like this made it into 1.10", "commid": "kubernetes_issue_50865", "tokennum": 336}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a91084b567a3a4271cdda2fe5a4c99255e3423efb8e261aed9543bf3311eba0d", "query": "expectedReconciledRole:       aggregatedRole(aggregationrule([]map[string]string{{\"alpha\": \"bravo\"}, {\"foo\": \"bar\"}})), expectedReconciliationNeeded: true, }, <ins> \"unexpected aggregation\": { // desired role is not aggregated expectedRole: role(rules(\"pods\", \"nodes\", \"secrets\"), nil, nil), // existing role is aggregated actualRole:             aggregatedRole(aggregationrule([]map[string]string{{\"alpha\": \"bravo\"}})), removeExtraPermissions: false, // reconciled role should have desired permissions and not be aggregated expectedReconciledRole:       role(rules(\"pods\", \"nodes\", \"secrets\"), nil, nil), expectedReconciliationNeeded: true, }, \"unexpected aggregation with differing permissions\": { // desired role is not aggregated expectedRole: role(rules(\"pods\", \"nodes\", \"secrets\"), nil, nil), // existing role is aggregated and has other permissions actualRole: func() *rbac.ClusterRole { r := aggregatedRole(aggregationrule([]map[string]string{{\"alpha\": \"bravo\"}})) r.Rules = rules(\"deployments\") return r }(), removeExtraPermissions: false, // reconciled role should have aggregation removed, preserve differing permissions, and include desired permissions expectedReconciledRole:       role(rules(\"deployments\", \"pods\", \"nodes\", \"secrets\"), nil, nil), expectedReconciliationNeeded: true, }, </ins> } for k, tc := range tests {", "positive_passages": [{"docid": "doc-en-kubernetes-cf86a1652325e783afd2e6de68ee19a134c3d5bc67e73b574ad8b67c1852b0fb", "text": "/kind bug What happened: I deployed a fresh custom HA kubernetes v1.10.2 cluster with 3 nodes (all controller and worker currently, more workers planned). I then created a namespace called \"stummi\" and a rolebinding with \"user=stummi clusterrole=admin\" in this namespace. User stummi (successfully authenticated by TLS client certificate) was not able to list pods or anything else in his namespace: While trying to figure things out, I downgraded to v1.8.11 (a version without cluster role aggregation, that worked) and also tried v1.11 alpha2 (which did not work). I never purged my etcd and I sadly do not have logs from before the different versions. Shortly after posting on slack and before writing this ticket, I dumped the cluster roles in question: Note the rules. What you expected to happen: I expected user stummi to be able to do most things in his namespace. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: I posted this problem on slack and helped me and wanted this issue opened. /sig auth The cluster is deployed with ansible and I can give the playbooks when required. Environment: Kubernetes version (use ):Cloud provider or hardware configuration: 3 virtual machines (2 cores, 8GB memory) OS (e.g. from /etc/os-release): Debian Stretch Kernel (e.g. ): Install tools: custom ansible playbooks Others: Please let me know if you need more information. I'm happy to provide everything you need to fix this :)\n/assign", "commid": "kubernetes_issue_63760", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a9894783a43b93fe5e0a627e2645d94f7c8bf0f9017e126f6ccfeb3313b04aa3", "query": "## Set resource limits/request of a deployment # Pre-condition: no deployment exists kube::test::get_object_assert deployment \"{{range.items}}{{$id_field}}:{{end}}\" '' <del> # Set resources of a local file without talking to the server kubectl set resources -f hack/testdata/deployment-multicontainer.yaml -c=perl --limits=cpu=300m --requests=cpu=300m --local -o yaml \"${kube_flags[@]}\" ! kubectl set resources -f hack/testdata/deployment-multicontainer.yaml -c=perl --limits=cpu=300m --requests=cpu=300m --dry-run -o yaml \"${kube_flags[@]}\" </del> # Create a deployment kubectl create -f hack/testdata/deployment-multicontainer.yaml \"${kube_flags[@]}\" kube::test::get_object_assert deployment \"{{range.items}}{{$id_field}}:{{end}}\" 'nginx-deployment:' kube::test::get_object_assert deployment \"{{range.items}}{{$deployment_image_field}}:{{end}}\" \"${IMAGE_DEPLOYMENT_R1}:\" kube::test::get_object_assert deployment \"{{range.items}}{{$deployment_second_image_field}}:{{end}}\" \"${IMAGE_PERL}:\" # Set the deployment's cpu limits <del> kubectl set resources deployment nginx-deployment --limits=cpu=200m \"${kube_flags[@]}\" kube::test::get_object_assert deployment \"{{range.items}}{{(index .spec.template.spec.containers 0).resources.limits.cpu}}:{{end}}\" \"200m:\" kube::test::get_object_assert deployment \"{{range.items}}{{(index .spec.template.spec.containers 1).resources.limits.cpu}}:{{end}}\" \"200m:\" # Set the deployments memory limits without affecting the cpu limits kubectl set resources deployment nginx-deployment --limits=memory=256Mi \"${kube_flags[@]}\" kube::test::get_object_assert deployment \"{{range.items}}{{(index .spec.template.spec.containers 0).resources.limits.cpu}}:{{end}}\" \"200m:\" kube::test::get_object_assert deployment \"{{range.items}}{{(index .spec.template.spec.containers 0).resources.limits.memory}}:{{end}}\" \"256Mi:\" # Set the deployments resource requests without effecting the deployments limits kubectl set resources deployment nginx-deployment --requests=cpu=100m,memory=256Mi \"${kube_flags[@]}\" kube::test::get_object_assert deployment \"{{range.items}}{{(index .spec.template.spec.containers 0).resources.limits.cpu}}:{{end}}\" \"200m:\" kube::test::get_object_assert deployment \"{{range.items}}{{(index .spec.template.spec.containers 0).resources.limits.memory}}:{{end}}\" \"256Mi:\" kube::test::get_object_assert deployment \"{{range.items}}{{(index .spec.template.spec.containers 0).resources.requests.cpu}}:{{end}}\" \"100m:\" kube::test::get_object_assert deployment \"{{range.items}}{{(index .spec.template.spec.containers 0).resources.requests.memory}}:{{end}}\" \"256Mi:\" # Set the deployments resource requests and limits to zero kubectl set resources deployment nginx-deployment --requests=cpu=0,memory=0 --limits=cpu=0,memory=0 \"${kube_flags[@]}\" </del> <ins> kubectl set resources deployment nginx-deployment --limits=cpu=100m \"${kube_flags[@]}\" kube::test::get_object_assert deployment \"{{range.items}}{{(index .spec.template.spec.containers 0).resources.limits.cpu}}:{{end}}\" \"100m:\" kube::test::get_object_assert deployment \"{{range.items}}{{(index .spec.template.spec.containers 1).resources.limits.cpu}}:{{end}}\" \"100m:\" </ins> # Set a non-existing container should fail ! kubectl set resources deployment nginx-deployment -c=redis --limits=cpu=100m # Set the limit of a specific container in deployment <del> kubectl set resources deployment nginx-deployment --limits=cpu=100m \"${kube_flags[@]}\" </del> kubectl set resources deployment nginx-deployment -c=nginx --limits=cpu=200m \"${kube_flags[@]}\" kube::test::get_object_assert deployment \"{{range.items}}{{(index .spec.template.spec.containers 0).resources.limits.cpu}}:{{end}}\" \"200m:\" kube::test::get_object_assert deployment \"{{range.items}}{{(index .spec.template.spec.containers 1).resources.limits.cpu}}:{{end}}\" \"100m:\"", "positive_passages": [{"docid": "doc-en-kubernetes-f45c12318e35043c65362c27e361ee13adfef369e183f2b4f0557c11353bd9e9", "text": "from https://k8s-\nReally suspect this is\nThis is putting us into test-go post-commit run is broken\ncc:\nmarked this p0 - if a fix isn't easy let's try to identify what introduced this and revert.\nThis flake on: 2016-10-30 07:19 PDT First instance: : It is flaking frequently, blocking PRs from getting merged, and slowing the submit queue ( at 75%). As on-call, I'm going to try and identify the cluprit and revert. Can use all help in doing so.\ncan you investigate whether your additional tests could cause this (by breaking the deployment of those pods, for instance) , Saad Ali wrote:\nPR looks most suspect to me. It mucked with , and the errors we are seeing in each of the failures is related to : That PR was merged at Oct 30, 2016, 6:18 AM PDT and the first flake in was at Oct 30, 2016, 7:19 AM PDT. Thoughts? CC\nI'm going to initiate a revert of to see if that fixes the issue\nIMO we can just change the flaky test to not get pods but some other resources, such as deployments. We can't really expect to clean up pods immediately.\nI'm going to proceed with revert (). Please feel free to send a follow up PR to handle this more gracefully.\nGoing to leave this opened until we have a few hours of runs with the revert. Want to verify, with some degree of certainty, that the revert took care of this flake.\nWe had 15 green runs of in a row. Considering this flake fixed.", "commid": "kubernetes_issue_35898", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a9a56b4a6ade3668a7f9f5fcff4beb2d43641c365c33284dbae7180f2c8a15e7", "query": "// we have removed content, so mark it finalized by us result, err := retryOnConflictError(kubeClient, namespace, finalizeNamespaceFunc) if err != nil { <ins> // in normal practice, this should not be possible, but if a deployment is running // two controllers to do namespace deletion that share a common finalizer token it's // possible that a not found could occur since the other controller would have finished the delete. if errors.IsNotFound(err) { return nil } </ins> return err }", "positive_passages": [{"docid": "doc-en-kubernetes-5963c982feb2169d82fc17ad89ab9be2967cbad808254e7a712ad33fb952ec83", "text": "If the namespace controller gets an error when doing a sync and the error is not a error the error will not be handled. Ran in to this when we found When deleting a namespace it received a error that wasn't reported anywhere and the namespace stuck in because a finalizer was left.\nOther things noticed in the namespace controller: need a crash handler in sweep for all error return cases and determine whether should be returned determine what to do with non- errors at ... I think that currently it just hangs termination of that namespace until a resync\nI will take a look. Thanks for the heads up.", "commid": "kubernetes_issue_21406", "tokennum": 130}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a9ab3762a0a4d0fec1dd07cd29c0a59db124419a72e81cf29f7562474b24e8ff", "query": "klog.Errorf(\"cannot convert to *v1.Pod: %v\", obj) return } <ins> klog.V(3).Infof(\"add event for scheduled pod %s/%s \", pod.Namespace, pod.Name) </ins> if err := sched.SchedulerCache.AddPod(pod); err != nil { klog.Errorf(\"scheduler cache AddPod failed: %v\", err)", "positive_passages": [{"docid": "doc-en-kubernetes-671a12759d851f1b99028bc477360c418e1157a45a2e814ff1c5c1cdd09da36a", "text": "This helps debugging scheduler's behavior, currently we don't have logs that indicate when the scheduler first saw a pod or a node. The log level should be v=3. /sig scheduling /cc\nDo you mean add logging for callbacks in ?\nyes, at least for add and delete events\nSure, I can also give this pr, before tomorrow\n/assign\nWe actually have one v=2 log line for a Node being to the cache's tree: But it's probably good to keep this one.", "commid": "kubernetes_issue_87524", "tokennum": 111}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a9ac6b55a394d8008f12142a87651ac19dadbfabf469a4064b2c16382416509d", "query": "// we can recreate it cleanly. if cachedService.Spec.CreateExternalLoadBalancer { glog.Infof(\"Deleting existing load balancer for service %s that needs an updated load balancer.\", namespacedName) <del> if err := s.ensureLBDeleted(cachedService); err != nil { </del> <ins> if err := s.balancer.EnsureTCPLoadBalancerDeleted(s.loadBalancerName(cachedService), s.zone.Region); err != nil { </ins> return err, retryable } }", "positive_passages": [{"docid": "doc-en-kubernetes-9fca6378f8b8df6d20b226b62d39deddc0dd6ba6166f0f70fb99239f64c63f5d", "text": "All of our external load balancer tests failed for the better part of a day due to the GCE project that our tests run in hitting its quota for number of target pools. While the target pools have been deleted, the fact that we hit our quota indicates that there must be a leak somewhere, and we need to plug it.\nFor reference, the previous issue was\nCould the leakage be related to ? The quota exhaustion occurred about 22 hrs after that.\nI'd guess that this is due to GetTCPLoadBalancer returning that the load balancer doesn't exist if the forwarding rule is gone, ignoring the target pool, while the service controller considers its deleting done if the cloud provider says that the load balancer doesn't exist. I that logic to the cloud provider because the other implementations of DeleteTCPLoadBalancer weren't/won't be idempotent in the sense of returning ok if the LB doesn't exist. To fix it, we'll either need to make sure all Delete implementations are idempotent and remove the Get call in the controller, or add a method along the lines of IsTCPLoadBalancerDeleted to ask the cloud provider whether all pieces of it have been completely cleaned up. We can't make GetTCPLoadBalancer check that because it's relied on to tell us whether or not the balancer is fully created.\nCopying over my commentary from on why the GKE e2e tests are leaking so many forwarding rules and target pools vs the GCE tests:\nIs there a way for the services test to wait for the service controller to clean up the external resources before finishing (without just doing a sleep)?\nNot without polling GCE directly for whether the resources still exist, although that may be worth it as a workaround. What would be perfect is that clean-up-all-cloud-provider-resources API method that we talked about a couple months ago.\nCan we not perhaps use GCE namespaces or projects as a cheap way of getting this here?\nI don't believe so. We can't use projects due to the fact that projects can't be programatically created (they're intended to be long-lived). I'm not aware of anything along the lines of a GCE namespace other than networks, which won't work because target pools and forwarding rules unfortunately don't seem to be scoped to networks.", "commid": "kubernetes_issue_7753", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a9ac6b55a394d8008f12142a87651ac19dadbfabf469a4064b2c16382416509d", "query": "// we can recreate it cleanly. if cachedService.Spec.CreateExternalLoadBalancer { glog.Infof(\"Deleting existing load balancer for service %s that needs an updated load balancer.\", namespacedName) <del> if err := s.ensureLBDeleted(cachedService); err != nil { </del> <ins> if err := s.balancer.EnsureTCPLoadBalancerDeleted(s.loadBalancerName(cachedService), s.zone.Region); err != nil { </ins> return err, retryable } }", "positive_passages": [{"docid": "doc-en-kubernetes-d79b213781c20847fbb47c058c0afaba60ed2f1d9f5b51e77a0a4cda944c52e0", "text": "The target pool leak in the code might be fixed, but the forwarding rule + target pool leak from deleting GKE clusters too quickly is certainly still happening. Reopening for the sake of that half of the issue.\nCan we just add a short sleep to jenkins after the last test has run before it deletes anything?\nYes, you could add a sleep to Ginkgo's AfterEachSuite(): But I'd be concerned about what the upper bound on the sleep period is. Can we get the tests and code in sync with a 1 minute latency here? (e.g. if the controller garbage collects every 60 seconds, then the test only needs to sleep for 60 sec?) And add a BEEG comment to the test's sleep config noting that increasing the sleep time will not improve things, otherwise I'm pretty sure that someone noting flakes in this test in future will think \"maybe I should just increase the sleep period a little bit.\"\nActually, thinking about this a little more, it would be better to put the \"sleep\" logic in the k8s master teardown procedure (i.e. not in the e2e tests or in Jenkins), because otherwise users are going to run into the same resource leakage problems as we are. So master deletion blocks on cleanup of backend cloud resources.\nThere's no way to block master deletion from the master itself. The test framework (or user) just pulls the rug out from underneath the master. See\nRobby's right -- is the real solution to this, but until we have that the best we can do is to have the wait happen elsewhere. The options seem to be: GKE itself Ginkgo's post-testing logic Jenkins' teardown logic I don't like putting it in GKE, because arbitrarily slowing down our API makes for a poor experience for the majority of people that don't still have resources being deleted. I'm not eager to put it in Gingko either, since won't that sleep also take effect whenever anyone runs an e2e test locally against a dev cluster? Putting it in the Jenkins logic makes the most sense to me. I'll send a PR and cc you.\nWe may also want to change the kube-down logic to bring down the master and then nodes in parallel to both speed it up and more closely resemble GKE's teardown logic.\nI've deleted the old forwarding rules and target pools from the project.", "commid": "kubernetes_issue_7753", "tokennum": 530}], "negative_passages": []}
{"query_id": "q-en-kubernetes-a9ac6b55a394d8008f12142a87651ac19dadbfabf469a4064b2c16382416509d", "query": "// we can recreate it cleanly. if cachedService.Spec.CreateExternalLoadBalancer { glog.Infof(\"Deleting existing load balancer for service %s that needs an updated load balancer.\", namespacedName) <del> if err := s.ensureLBDeleted(cachedService); err != nil { </del> <ins> if err := s.balancer.EnsureTCPLoadBalancerDeleted(s.loadBalancerName(cachedService), s.zone.Region); err != nil { </ins> return err, retryable } }", "positive_passages": [{"docid": "doc-en-kubernetes-6b81898435dc239c0c98669b4836ce5b1423be788127f142aa9eb15c198137cf", "text": "I'll periodically check to see whether anything is leaked after this point. I apologize if the deletions affected any running tests - everything looked to only be from GKE and parallel e2e runs.", "commid": "kubernetes_issue_7753", "tokennum": 42}], "negative_passages": []}
{"query_id": "q-en-kubernetes-aa05ce0d76b9bc116e13d2106a38ef8cff549dcc1af5bcdc1d9ddd74c8e2567e", "query": "err = wait.PollImmediate(podRetryPeriod, podRetryTimeout, checkPodListQuantity(f, \"type=Testing\", 0)) framework.ExpectNoError(err, \"found a pod(s)\") }) <ins> ginkgo.It(\"should run through the lifecycle of Pods and PodStatus\", func() { podResource := schema.GroupVersionResource{Group: \"\", Version: \"v1\", Resource: \"pods\"} testNamespaceName := f.Namespace.Name testPodName := \"pod-test\" testPodImage := imageutils.GetE2EImage(imageutils.Agnhost) testPodImage2 := imageutils.GetE2EImage(imageutils.Httpd) testPodLabels := map[string]string{\"test-pod-static\": \"true\"} testPodLabelsFlat := \"test-pod-static=true\" zero := int64(0) w := &cache.ListWatch{ WatchFunc: func(options metav1.ListOptions) (watch.Interface, error) { options.LabelSelector = testPodLabelsFlat return f.ClientSet.CoreV1().Pods(testNamespaceName).Watch(context.TODO(), options) }, } podsList, err := f.ClientSet.CoreV1().Pods(\"\").List(context.TODO(), metav1.ListOptions{LabelSelector: testPodLabelsFlat}) framework.ExpectNoError(err, \"failed to list Pods\") testPod := v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name:   testPodName, Labels: testPodLabels, }, Spec: v1.PodSpec{ TerminationGracePeriodSeconds: &zero, Containers: []v1.Container{ { Name:  testPodName, Image: testPodImage, }, }, }, } ginkgo.By(\"creating a Pod with a static label\") _, err = f.ClientSet.CoreV1().Pods(testNamespaceName).Create(context.TODO(), &testPod, metav1.CreateOptions{}) framework.ExpectNoError(err, \"failed to create Pod %v in namespace %v\", testPod.ObjectMeta.Name, testNamespaceName) ginkgo.By(\"watching for Pod to be ready\") ctx, cancel := context.WithTimeout(context.Background(), podReadyTimeout) defer cancel() _, err = watchtools.Until(ctx, podsList.ResourceVersion, w, func(event watch.Event) (bool, error) { if pod, ok := event.Object.(*v1.Pod); ok { found := pod.ObjectMeta.Name == testPod.ObjectMeta.Name && pod.ObjectMeta.Namespace == testNamespaceName && pod.Labels[\"test-pod-static\"] == \"true\" && pod.Status.Phase == v1.PodRunning if !found { framework.Logf(\"observed Pod %v in namespace %v in phase %v conditions %v\", pod.ObjectMeta.Name, pod.ObjectMeta.Namespace, pod.Status.Phase, pod.Status.Conditions) } return found, nil } return false, nil }) framework.ExpectNoError(err, \"failed to see Pod %v in namespace %v running\", testPod.ObjectMeta.Name, testNamespaceName) ginkgo.By(\"patching the Pod with a new Label and updated data\") podPatch, err := json.Marshal(v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Labels: map[string]string{\"test-pod\": \"patched\"}, }, Spec: v1.PodSpec{ TerminationGracePeriodSeconds: &zero, Containers: []v1.Container{{ Name:  testPodName, Image: testPodImage2, }}, }, }) framework.ExpectNoError(err, \"failed to marshal JSON patch for Pod\") _, err = f.ClientSet.CoreV1().Pods(testNamespaceName).Patch(context.TODO(), testPodName, types.StrategicMergePatchType, []byte(podPatch), metav1.PatchOptions{}) framework.ExpectNoError(err, \"failed to patch Pod %s in namespace %s\", testPodName, testNamespaceName) ctx, cancel = context.WithTimeout(context.Background(), 30*time.Second) defer cancel() _, err = watchtools.Until(ctx, podsList.ResourceVersion, w, func(event watch.Event) (bool, error) { switch event.Type { case watch.Modified: if pod, ok := event.Object.(*v1.Pod); ok { found := pod.ObjectMeta.Name == pod.Name && pod.Labels[\"test-pod-static\"] == \"true\" return found, nil } default: framework.Logf(\"observed event type %v\", event.Type) } return false, nil }) framework.ExpectNoError(err, \"failed to see %v event\", watch.Modified) ginkgo.By(\"getting the Pod and ensuring that it's patched\") pod, err := f.ClientSet.CoreV1().Pods(testNamespaceName).Get(context.TODO(), testPodName, metav1.GetOptions{}) framework.ExpectNoError(err, \"failed to fetch Pod %s in namespace %s\", testPodName, testNamespaceName) framework.ExpectEqual(pod.ObjectMeta.Labels[\"test-pod\"], \"patched\", \"failed to patch Pod - missing label\") framework.ExpectEqual(pod.Spec.Containers[0].Image, testPodImage2, \"failed to patch Pod - wrong image\") ginkgo.By(\"getting the PodStatus\") podStatusUnstructured, err := dc.Resource(podResource).Namespace(testNamespaceName).Get(context.TODO(), testPodName, metav1.GetOptions{}, \"status\") framework.ExpectNoError(err, \"failed to fetch PodStatus of Pod %s in namespace %s\", testPodName, testNamespaceName) podStatusBytes, err := json.Marshal(podStatusUnstructured) framework.ExpectNoError(err, \"failed to marshal unstructured response\") var podStatus v1.Pod err = json.Unmarshal(podStatusBytes, &podStatus) framework.ExpectNoError(err, \"failed to unmarshal JSON bytes to a Pod object type\") ginkgo.By(\"replacing the Pod's status Ready condition to False\") podStatusUpdated := podStatus podStatusFieldPatchCount := 0 podStatusFieldPatchCountTotal := 2 for pos, cond := range podStatusUpdated.Status.Conditions { if (cond.Type == v1.PodReady && cond.Status == v1.ConditionTrue) || (cond.Type == v1.ContainersReady && cond.Status == v1.ConditionTrue) { podStatusUpdated.Status.Conditions[pos].Status = v1.ConditionFalse podStatusFieldPatchCount++ } } framework.ExpectEqual(podStatusFieldPatchCount, podStatusFieldPatchCountTotal, \"failed to patch all relevant Pod conditions\") podStatusUpdate, err := f.ClientSet.CoreV1().Pods(testNamespaceName).UpdateStatus(context.TODO(), &podStatusUpdated, metav1.UpdateOptions{}) framework.ExpectNoError(err, \"failed to update PodStatus of Pod %s in namespace %s\", testPodName, testNamespaceName) ginkgo.By(\"check the Pod again to ensure its Ready conditions are False\") podStatusFieldPatchCount = 0 podStatusFieldPatchCountTotal = 2 for _, cond := range podStatusUpdate.Status.Conditions { if (cond.Type == v1.PodReady && cond.Status == v1.ConditionFalse) || (cond.Type == v1.ContainersReady && cond.Status == v1.ConditionFalse) { podStatusFieldPatchCount++ } } framework.ExpectEqual(podStatusFieldPatchCount, podStatusFieldPatchCountTotal, \"failed to update PodStatus - field patch count doesn't match the total\") ginkgo.By(\"deleting the Pod via a Collection with a LabelSelector\") err = f.ClientSet.CoreV1().Pods(testNamespaceName).DeleteCollection(context.TODO(), metav1.DeleteOptions{GracePeriodSeconds: &zero}, metav1.ListOptions{LabelSelector: testPodLabelsFlat}) framework.ExpectNoError(err, \"failed to delete Pod by collection\") ginkgo.By(\"watching for the Pod to be deleted\") ctx, cancel = context.WithTimeout(context.Background(), 1*time.Minute) defer cancel() _, err = watchtools.Until(ctx, podsList.ResourceVersion, w, func(event watch.Event) (bool, error) { switch event.Type { case watch.Deleted: if pod, ok := event.Object.(*v1.Pod); ok { found := pod.ObjectMeta.Name == pod.Name && pod.Labels[\"test-pod-static\"] == \"true\" return found, nil } default: framework.Logf(\"observed event type %v\", event.Type) } return false, nil }) framework.ExpectNoError(err, \"failed to see %v event\", watch.Deleted) }) </ins> }) func checkPodListQuantity(f *framework.Framework, label string, quantity int) func() (bool, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-a4e08d4660e59e77b869eee3e8c161e5e01175b90d68e1077fd3e84d4f4d567b", "text": "[x] Original approval issue: - Reverted due to flakes [x] Two weeks soak end date: 20 November 2020 This issue is created to allow edit by /wip /hold According to this APIsnoop query, there are still some remaining Pod endpoints which are untested. a Pod with a static label the Pod with a new Label and updated data the Pod to ensure it's patched the Pod's status the Pod's status Ready condition to False the Pod's status to check if Ready is False all Pods in all Namespaces find the Pod(1) ensure that the Pod is found and is patched Namespaced Pod(1) via a Collection with a LabelSelector the Pod to check that it's deleted Discover useragents: List endpoints hit by the test: Display endpoint coverage change: If a test with these calls gets merged, test coverage will go up by 4 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance\n/reopen Test PR Merge Promotion PR to be created next\nReopened this issue. <detailsIn response to : /reopen Test PR Merge Promotion PR to be created next 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\nreverted by due to flaky test\nIssues 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\n/remove-lifecycle stale\n/reopen PR on test grid for 2 weeks before promotion to conformance\nReopened this issue. <detailsIn response to : /reopen PR on test grid for 2 weeks before promotion to conformance 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\n/triage accepted", "commid": "kubernetes_issue_90936", "tokennum": 449}], "negative_passages": []}
{"query_id": "q-en-kubernetes-aa1efbc4d608095a5d3e17c08d7eaa0fee6303f65b6f340062852405c1e167e9", "query": "watch \"k8s.io/apimachinery/pkg/watch\" clientset \"k8s.io/client-go/kubernetes\" watchtools \"k8s.io/client-go/tools/watch\" <ins> \"k8s.io/client-go/util/retry\" </ins> cloudprovider \"k8s.io/cloud-provider\" \"k8s.io/kubernetes/test/e2e/framework\" e2edeployment \"k8s.io/kubernetes/test/e2e/framework/deployment\"", "positive_passages": [{"docid": "doc-en-kubernetes-c5b2d72b2e785256d7a2577807fdbd43ef000a4da594f69c949ac55e4186d114", "text": "[x] two weeks soak end date : 18 March 2021 According to this APIsnoop query, there are still some remaining RESOURCENAME endpoints which are untested. with this query you can filter untested endpoints by their category and eligiblity for conformance. e.g below shows a query to find all conformance eligible untested,stable,core endpoints Note: Community feedback for the e2e test has lead to a number of improvements including extending the test coverage to all outstanding endpoints listed above. As each endpoint is tested a &rsquo;watch&rsquo; confirms that the result is valid before testing the next endpoint. readCoreV1NamespacedServiceStatus (get /status) patchCoreV1NamespacedServiceStatus (patch /status) replaceCoreV1NamespacedServiceStatus (update /status) patchCoreV1NamespacedService Create a Service with a static label Patch the Service with a new label and updated data Get the Service to ensure it&rsquo;s patched Upate the Service with a new label and updated data Get the Service to ensure it&rsquo;s updated Delete Namespaced Service via a Collection with a LabelSelector This query by apisnoop shows that all outstanding endpoints as list at the start of this document have been hit by the e2e test. Note that the results do include other service endpoints that have been addressed in other conformance tests. If a test with these calls gets merged, test coverage will go up by 4 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance\nCan you please review the proposed test and advise if we could go ahead with a PR\n/assign\nIt looks like it's patching metadata and spec but not status?\nIssues 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\n/remove-lifecycle stale\nI've been retesting this mock test and apisnoop does log as been hit. From my testing below it looks like the patchStatus is working as expected or have I missed something?", "commid": "kubernetes_issue_94867", "tokennum": 517}], "negative_passages": []}
{"query_id": "q-en-kubernetes-aa1efbc4d608095a5d3e17c08d7eaa0fee6303f65b6f340062852405c1e167e9", "query": "watch \"k8s.io/apimachinery/pkg/watch\" clientset \"k8s.io/client-go/kubernetes\" watchtools \"k8s.io/client-go/tools/watch\" <ins> \"k8s.io/client-go/util/retry\" </ins> cloudprovider \"k8s.io/cloud-provider\" \"k8s.io/kubernetes/test/e2e/framework\" e2edeployment \"k8s.io/kubernetes/test/e2e/framework/deployment\"", "positive_passages": [{"docid": "doc-en-kubernetes-6c98fb90bee2cd0d2fc404edc784deab934fddaa81022ed1883862c51f5dae6d", "text": "Using the following code before the patch request Gives this response Then after running the patch ServiceStatus Then running The response shows the patched changes.\nDuring the Conformance Meeting on 12th of January 2021, reviewed approach with Clayton, and we will start on the test PR this week!\n/reopen\nReopened this issue. <detailsIn response to : /reopen </details\n/triage accepted", "commid": "kubernetes_issue_94867", "tokennum": 79}], "negative_passages": []}
{"query_id": "q-en-kubernetes-aa33b876bce8e9df08322f22c218e14eae27c5b882b225019681ed40e1df7cbd", "query": "utilruntime.Must(events.AddToScheme(scheme)) utilruntime.Must(v1beta1.AddToScheme(scheme)) utilruntime.Must(v1.AddToScheme(scheme)) <del> utilruntime.Must(scheme.SetVersionPriority(v1beta1.SchemeGroupVersion, v1.SchemeGroupVersion)) </del> <ins> utilruntime.Must(scheme.SetVersionPriority(v1.SchemeGroupVersion, v1beta1.SchemeGroupVersion)) </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-151038cc19e020d7d7996b734b8e9e17c5611ef500523f3ad799d063a04956b9", "text": "What would you like to be : The Event API is being promoted to v1 in and right now v1beta1 has higher priority than v1 in We should bump this in 1.20. Why is this needed: The new Event API is being promoted.\n/sig instrumentation\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nClosing 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\n/reopen\nReopened this issue. <detailsIn response to : /reopen </details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_91965", "tokennum": 419}], "negative_passages": []}
{"query_id": "q-en-kubernetes-aadfb1e412524753acefc9059dd4650eb6f63baf6a7dc4c62908d2a77048a20b", "query": "ginkgo.AfterEach(func() { // print out additional info if tests failed if ginkgo.CurrentGinkgoTestDescription().Failed { <del> // list existing priorities </del> <ins> // List existing PriorityClasses. </ins> priorityList, err := cs.SchedulingV1().PriorityClasses().List(context.TODO(), metav1.ListOptions{}) if err != nil { <del> framework.Logf(\"Unable to list priorities: %v\", err) </del> <ins> framework.Logf(\"Unable to list PriorityClasses: %v\", err) </ins> } else { <del> framework.Logf(\"List existing priorities:\") </del> <ins> framework.Logf(\"List existing PriorityClasses:\") </ins> for _, p := range priorityList.Items { framework.Logf(\"%v/%v created at %v\", p.Name, p.Value, p.CreationTimestamp) }", "positive_passages": [{"docid": "doc-en-kubernetes-3bda2fba5ce2ad90b89601bf2aa62ec37353e4edef7a62972ac2a85cc1aff832", "text": "The following PriorityClass endpoints was Promoted it 1.14 without Conformance tests, and remain untested: replace-, read-, patch-, list-, delete-collection- SchedulingV1PriorityClass According to this APIsnoop query, there are still some remaining PriorityClass endpoints which are untested. with this query you can filter untested endpoints by their category and eligiblity for conformance. e.g below shows a query to find all conformance eligible untested,stable,core endpoints ! createSchedulingV1PriorityClass deleteSchedulingV1PriorityClass Promoted to Conformance 1.19 with /sig testing /sig architecture /area conformance\nIs the ultimiate goal to use conformance tests to explicitly issue all CRUD requests against PriorityClass? And, is equivalent to \"update PriorityClass\"?\nall APIs must have Conformance tests unless they are not eligible for Conformance due to the There is other APIGroups that have both Replace and Update as endpoints. That is the prerogative of the SIG to decide.\ncan you please point us to similar conformance tests used for core objects such as pods and nodes?\nThis is a life cycle test for Create, List, Update, Patch, DeleteCollection More can be found in the test/e2e folder. Also look for examples on the Conformance at previously Promoted Conformance test Reach out if we can help with more information on our approach to Conformance testing.\nI remembered about this PR. Last week a few lines of code was to cover the last of the \"Lease\" endpoint group for conformance. The one file contain the Conformance tests for the complete life cycle of Lease endpoints.\n/assign I will work on it.\n/reopen Will monitor in test grid to move to Conformance after 2 weeks soak.\nReopened this issue. <detailsIn response to : /reopen Will monitor in test grid to move to Conformance after 2 weeks soak. </details\n/triage accepted", "commid": "kubernetes_issue_94954", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ab17cd52c2d223798804c4a8f57d33a8581223ad1d63f58e185af963967a5a7b", "query": "\"flag\" \"fmt\" \"log\" <ins> \"math/rand\" </ins> \"net/http\" \"os\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-cd494847d4bddf9ea80027a9691be245174d67d67dcf4a48743332a9d199dc09", "text": "This was the root cause of rancher/rancher. In , when is called, it is given the oldVersion of an object and the newVersion of the object. It then uses the indexers to calculate the old values (from the old version) and the new updated values. In cases where are size of 1, are of size greater than 1, and contain the sole value from , the key will be deleted for the old value will be deleted and won't be re-. This is due to the two for loops at the end of the method which are used for optimization. When the first for loop is processed, . Because of this, the key is deleted from the index for this value. In the second for loop, the , and for at least one of the values . The continue statement causes the key to not be to the index for this value (and since the value was deleted in the prior for loop, it no longer exists in the index for this value), despite the fact that the indicated that this is the desired state. Since specified that this value was still valid for this object, the key should not be deleted from the index for this value, or it should be re- when it is re-discovered in . Either way, the end state of the index should include this key in the set for the specified value. I've created a which demonstrates the issue (branch is ). To use it (assuming that you have a running kubernetes cluster to use with): the controller: . the foo crd: the controller (assumes that you have $KUBECONFIG set to the file path of your kubeconfig file). an example foo with only one label: . Observe, in the logs of the running sample-controller, that the indexer was able to locate this foo using the indexer. the foo to include a second label: . Observe, in the logs of the running sample-controller, that the indexer was not able to locate the foo using the first key any longer, despite the fact that the label was still on the object. The sample-controller fork adds an indexer for foo objects which uses the indexerFunction of . This function looks for labels that have a key with a prefix of and uses their values as index keys for the foo objects. For example, if I have a with a label of , the indexer will allow you to retrieve using .", "commid": "kubernetes_issue_109115", "tokennum": 500}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ab17cd52c2d223798804c4a8f57d33a8581223ad1d63f58e185af963967a5a7b", "query": "\"flag\" \"fmt\" \"log\" <ins> \"math/rand\" </ins> \"net/http\" \"os\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-582c669d9e852f593828621e1df0588db01f01d305d2c20cc4978aeea726760c", "text": "The controller's method has been altered to just ensure that the foos can be retrieved using the indexer for all valid labels. If the controller can't retrieve foo by using the value from a valid label, then it returns an error (it tries for all valid labels). This was originally discovered in a fork of client-go that we maintain. After we reverted the changes introduced by , our issues stopped occurring. N/A - This was introduced in and appears to be in all versions of the client v0.23+. N/A - issue is with client-go No response No response No response No response\n/sig api-machinery\nI think that you have background in this issue/area of the code. Would you mind taking a look at this issue and the PR that I have up to fix it? Please let me know if I've misunderstood anything.\n/assign Would you mind to take a look? Thank you /triage accepted\nThanks for reporting the issue. will address this issue\nReopening - since we need to cherrypick back to 1.23\nCherrypick is merged - closing.", "commid": "kubernetes_issue_109115", "tokennum": 230}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ab40d2d534a6f14a70b2f712bbb4a2d7b6f8dea3e9b3ec0d3b52fb569b4c23ca", "query": "<ins> /* Copyright 2019 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package main import ( \"io\" \"io/ioutil\" \"log\" \"os\" \"os/signal\" \"path/filepath\" \"strings\" \"github.com/pkg/errors\" ) func main() { if strings.Contains(os.Args[0], \"run_e2e.sh\") || strings.Contains(os.Args[0], \"gorunner\") { log.Print(\"warn: calling test with e2e.test is deprecated and will be removed in 1.25, please rely on container manifest to invoke executable\") } env := envWithDefaults(map[string]string{ resultsDirEnvKey: defaultResultsDir, skipEnvKey:       defaultSkip, focusEnvKey:      defaultFocus, providerEnvKey:   defaultProvider, parallelEnvKey:   defaultParallel, ginkgoEnvKey:     defaultGinkgoBinary, testBinEnvKey:    defaultTestBinary, }) if err := configureAndRunWithEnv(env); err != nil { log.Fatal(err) } } // configureAndRunWithEnv uses the given environment to configure and then start the test run. // It will handle TERM signals gracefully and kill the test process and will // save the logs/results to the location specified via the RESULTS_DIR environment // variable. func configureAndRunWithEnv(env Getenver) error { // Ensure we save results regardless of other errors. This helps any // consumer who may be polling for the results. resultsDir := env.Getenv(resultsDirEnvKey) defer saveResults(resultsDir) // Print the output to stdout and a logfile which will be returned // as part of the results tarball. logFilePath := filepath.Join(resultsDir, logFileName) logFile, err := os.Create(logFilePath) if err != nil { return errors.Wrapf(err, \"failed to create log file %v\", logFilePath) } mw := io.MultiWriter(os.Stdout, logFile) cmd := getCmd(env, mw) log.Printf(\"Running command:n%vn\", cmdInfo(cmd)) err = cmd.Start() if err != nil { return errors.Wrap(err, \"starting command\") } // Handle signals and shutdown process gracefully. go setupSigHandler(cmd.Process.Pid) return errors.Wrap(cmd.Wait(), \"running command\") } // setupSigHandler will kill the process identified by the given PID if it // gets a TERM signal. func setupSigHandler(pid int) { c := make(chan os.Signal, 1) signal.Notify(c, os.Interrupt) // Block until a signal is received. log.Println(\"Now listening for interrupts\") s := <-c log.Printf(\"Got signal: %v. Shutting down test process (PID: %v)n\", s, pid) p, err := os.FindProcess(pid) if err != nil { log.Printf(\"Could not find process %v to shut down.n\", pid) return } if err := p.Signal(s); err != nil { log.Printf(\"Failed to signal test process to terminate: %vn\", err) return } log.Printf(\"Signalled process %v to terminate successfully.n\", pid) } // saveResults will tar the results directory and write the resulting tarball path // into the donefile. func saveResults(resultsDir string) error { log.Printf(\"Saving results at %vn\", resultsDir) err := tarDir(resultsDir, filepath.Join(resultsDir, resultsTarballName)) if err != nil { return errors.Wrapf(err, \"tar directory %v\", resultsDir) } doneFile := filepath.Join(resultsDir, doneFileName) resultsTarball := filepath.Join(resultsDir, resultsTarballName) resultsTarball, err = filepath.Abs(resultsTarball) if err != nil { return errors.Wrapf(err, \"failed to find absolute path for %v\", resultsTarball) } return errors.Wrap( ioutil.WriteFile(doneFile, []byte(resultsTarball), os.FileMode(0777)), \"writing donefile\", ) } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-b6e1a63eb087c1fdbaf4f20789cf4dc422d7eb3a250658bf836af9dda6b010da", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be modified: image to be based on anything other than Docker Hub sourced Why is this needed: With Docker Hub rate-limit policy in-place, we probably should consider removing this dependency to stay in sync with other base images in Kubernetes project. Folks building their own binaries (i.e. with ) might run into this as well. Notes: Prior discussion happened on An idea from is to use the should probably be renamed to avoid confusion with k/release (h/t Currently, is set to , so migrating to may not be a drop-in move However, , so maybe we don't have to start from scratch /sig testing /area conformance /sig release (cc'ing because builds conformance image, though my quick search seem to show there isn't any build pipelines referencing )\n/assign\ndo we still want to do this? I read somewhere that the images built in Google Cloud are being mirrored from Docker Hub, right? This would mean that the API rate limiting will not hit us any more.\nWomp yeah I think DockerHub rate limit is not really the big motivator at this point. However, I think I still want to consider using distroless / go-runner to build and produce conformance image to reduce the noise from CVE scanning done in downstream places. What do you think?\nYeah I think this seems a valuable addition. Are you planning to work on this issue? :)\nI will, though probably won't start until next week. If you have ideas and would like to start early feel free to go for it! Otherwise, I'd be happy to work on and deliver this.\nThank you Wilson! Feel free to ping again if you need any assistance. /assign\n/triage accepted\none thing I need a little help with is to find a reference for using go-runner image that's used everywhere -- the one that I've found is inside conformance directory which seems to be different from what everyone else is using\nWe maintain a go-runner in k/release:\noops, I forgot to get back on this last week -- I meant to say that I need a reference for image which I can use as , so something like on Dockerfile. Is that a possible thing to do?", "commid": "kubernetes_issue_96692", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ab40d2d534a6f14a70b2f712bbb4a2d7b6f8dea3e9b3ec0d3b52fb569b4c23ca", "query": "<ins> /* Copyright 2019 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package main import ( \"io\" \"io/ioutil\" \"log\" \"os\" \"os/signal\" \"path/filepath\" \"strings\" \"github.com/pkg/errors\" ) func main() { if strings.Contains(os.Args[0], \"run_e2e.sh\") || strings.Contains(os.Args[0], \"gorunner\") { log.Print(\"warn: calling test with e2e.test is deprecated and will be removed in 1.25, please rely on container manifest to invoke executable\") } env := envWithDefaults(map[string]string{ resultsDirEnvKey: defaultResultsDir, skipEnvKey:       defaultSkip, focusEnvKey:      defaultFocus, providerEnvKey:   defaultProvider, parallelEnvKey:   defaultParallel, ginkgoEnvKey:     defaultGinkgoBinary, testBinEnvKey:    defaultTestBinary, }) if err := configureAndRunWithEnv(env); err != nil { log.Fatal(err) } } // configureAndRunWithEnv uses the given environment to configure and then start the test run. // It will handle TERM signals gracefully and kill the test process and will // save the logs/results to the location specified via the RESULTS_DIR environment // variable. func configureAndRunWithEnv(env Getenver) error { // Ensure we save results regardless of other errors. This helps any // consumer who may be polling for the results. resultsDir := env.Getenv(resultsDirEnvKey) defer saveResults(resultsDir) // Print the output to stdout and a logfile which will be returned // as part of the results tarball. logFilePath := filepath.Join(resultsDir, logFileName) logFile, err := os.Create(logFilePath) if err != nil { return errors.Wrapf(err, \"failed to create log file %v\", logFilePath) } mw := io.MultiWriter(os.Stdout, logFile) cmd := getCmd(env, mw) log.Printf(\"Running command:n%vn\", cmdInfo(cmd)) err = cmd.Start() if err != nil { return errors.Wrap(err, \"starting command\") } // Handle signals and shutdown process gracefully. go setupSigHandler(cmd.Process.Pid) return errors.Wrap(cmd.Wait(), \"running command\") } // setupSigHandler will kill the process identified by the given PID if it // gets a TERM signal. func setupSigHandler(pid int) { c := make(chan os.Signal, 1) signal.Notify(c, os.Interrupt) // Block until a signal is received. log.Println(\"Now listening for interrupts\") s := <-c log.Printf(\"Got signal: %v. Shutting down test process (PID: %v)n\", s, pid) p, err := os.FindProcess(pid) if err != nil { log.Printf(\"Could not find process %v to shut down.n\", pid) return } if err := p.Signal(s); err != nil { log.Printf(\"Failed to signal test process to terminate: %vn\", err) return } log.Printf(\"Signalled process %v to terminate successfully.n\", pid) } // saveResults will tar the results directory and write the resulting tarball path // into the donefile. func saveResults(resultsDir string) error { log.Printf(\"Saving results at %vn\", resultsDir) err := tarDir(resultsDir, filepath.Join(resultsDir, resultsTarballName)) if err != nil { return errors.Wrapf(err, \"tar directory %v\", resultsDir) } doneFile := filepath.Join(resultsDir, doneFileName) resultsTarball := filepath.Join(resultsDir, resultsTarballName) resultsTarball, err = filepath.Abs(resultsTarball) if err != nil { return errors.Wrapf(err, \"failed to find absolute path for %v\", resultsTarball) } return errors.Wrap( ioutil.WriteFile(doneFile, []byte(resultsTarball), os.FileMode(0777)), \"writing donefile\", ) } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-5d193977829c25729bf0cf7e65192f8c845e68df9f65fd9e6c218e9e5725e8bf", "text": "after searching around, I found this -- going to try and use and see how it works :smile:\nStarted a PR -- plenty of things I'd like to be discussed but we should probably have the discussions there\nIssues 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\n/remove-lifecycle stale there is work in progress", "commid": "kubernetes_issue_96692", "tokennum": 118}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ab4cde103e3d3d85c9493d1a03602bb4f689a283596ee80b573542d13c5284a9", "query": "By(fmt.Sprintf(\"Restart count of pod %s in namespace %s is now %d\", podDescr.Name, ns, restartCount)) if restartCount > initialRestartCount { By(fmt.Sprintf(\"Restart count of pod %s in namespace %s increased from %d to %d during the test\", podDescr.Name, ns, initialRestartCount, restartCount)) <del> pass = true </del> <ins> restarts = true </ins> break } } <del> if !pass { Fail(fmt.Sprintf(\"Did not see the restart count of pod %s in namespace %s increase from %d during the test\", podDescr.Name, ns, initialRestartCount)) </del> <ins> if restarts != expectRestart { Fail(fmt.Sprintf(\"pod %s in namespace %s - expected restarts: %v, found restarts: %v\", podDescr.Name, ns, expectRestart, restarts)) </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-65bf469670180d69e57fdc1a820a8f2f435cec685a9975e90f226dd126851fba", "text": "As far as I can tell, container liveness probes of type exec flat out don't work against clusters built at head. I had the kubelet always log the output of the exec'ed command, and it's always empty no matter what I exec, causing the probe to fail since it requires the output to be equal to the string \"ok\". If you want to test it, try adding a liveness probe of this form to any container: I also tried these lovely forms, to more closely match the liveness example under examples/: On the plus side, this may be an opportunistic time to switch over to\nThe reason that the e2e test for exec liveness probes hasn't caught this is that it only tests that containers are restarted when they fail liveness probes. It doesn't test that containers aren't restarted when their liveness checks should be succeeding. The e2e test's exec'ed commands also only ever produced empty output, rather than the expected \"fail\" output.\nIs it possible to include this in a new pre-release, since it fixes a bug in health checking? I see it merged in master and I'm wondering what the policy is of releasing new code in a separate (0.16.*) release.", "commid": "kubernetes_issue_7618", "tokennum": 275}], "negative_passages": []}
{"query_id": "q-en-kubernetes-abdd48798a74a1bea50049c4dfaaf9086f476890480292b5b324ee1e3864e112", "query": "return device, refCount, nil } <del> // IsNotMountPoint determines if a directory is a mountpoint. // It should return ErrNotExist when the directory does not exist. // This method uses the List() of all mountpoints // It is more extensive than IsLikelyNotMountPoint // and it detects bind mounts in linux func IsNotMountPoint(mounter Interface, file string) (bool, error) { </del> <ins> // isNotMountPoint implements Mounter.IsNotMountPoint and is shared by mounter // implementations. func isNotMountPoint(mounter Interface, file string) (bool, error) { </ins> // IsLikelyNotMountPoint provides a quick check // to determine whether file IS A mountpoint notMnt, notMntErr := mounter.IsLikelyNotMountPoint(file)", "positive_passages": [{"docid": "doc-en-kubernetes-4bcfc015d2b9d9fa1e84475a3e08fb9ef8299b4e5f821f790188ad7bdae6ecbc", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: There's , and . The former is used by local and nfs volume plugins, while the latter is used by , which is also used by local and nfs volume plugins. What you expected to happen: Can we consolidate these? This is really confusing and could easily be the source of bugs. <!-- DO NOT EDIT BELOW THIS LINE --/kind cleanup\ncc\n/assign I'd like to clean up code.", "commid": "kubernetes_issue_72387", "tokennum": 133}], "negative_passages": []}
{"query_id": "q-en-kubernetes-abf1c206c1173dde2aec72b54124c79376f4b30c155161c8c50314e6178acbc7", "query": "valueFrom: fieldRef: fieldPath: metadata.name <del> command: - /bin/sh - -c - /kubemark --morph=proxy --name=$(NODE_NAME) {{hollow_proxy_params}} --kubeconfig=/kubeconfig/kubeproxy.kubeconfig $(CONTENT_TYPE) --alsologtostderr 1>>/var/log/kubeproxy-$(NODE_NAME).log 2>&1 </del> <ins> command: [ \"/kubemark\", \"--morph=proxy\", \"--name=$(NODE_NAME)\", \"--kubeconfig=/kubeconfig/kubeproxy.kubeconfig\", \"$(CONTENT_TYPE)\", \"--log-file=/var/log/kubeproxy-$(NODE_NAME).log\", \"--logtostderr=false\", {{hollow_proxy_params}} ] </ins> volumeMounts: - name: kubeconfig-volume mountPath: /kubeconfig", "positive_passages": [{"docid": "doc-en-kubernetes-d99484417892d904a3f5edbb73fa06d2de654c460b279ad73f511e028afa6a6f", "text": "There are CVEs happening in different images - we already migrated Kubmeark from busybox in , but we should go one step further and migrate the base image to distroless. There are some things that would need to be changed mentioned here: /sig scalability\nCan I work on this? /assign\n/remove-help\n- sure that would be great.\nHi based on the discussion in , the kubemark image has dependency on and maybe more other utilities. So it seems impossible to migrate the base image to distroless? Or do we need something like debian-hyperkube-base?\nThe mount one we may get rid of - basically we should be able to switch to FakeMounter:", "commid": "kubernetes_issue_84284", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ac2918ff7c83107e9aeb82fbc6b17fa5ba14778fbe47e46f124ce8a35d7c6d86", "query": "// Enable usage of Provision of PVCs from snapshots in other namespaces CrossNamespaceVolumeDataSource featuregate.Feature = \"CrossNamespaceVolumeDataSource\" <ins> // owner: @thockin // deprecated: v1.29 // // Enables Service.status.ingress.loadBanace to be set on // services of types other than LoadBalancer. AllowServiceLBStatusOnNonLB featuregate.Feature = \"AllowServiceLBStatusOnNonLB\" </ins> // owner: @bswartz // alpha: v1.18 // beta: v1.24", "positive_passages": [{"docid": "doc-en-kubernetes-e021a9a686a92d83ba285392c70089f3a0813200ee010fb06825ed96dc15cfdb", "text": "xref I think this may be one of the few cases where we can actually change the behavior in a \"breaking\" way. User creates service with , is empty Controller or user updates the status subresource, sets (not wiped or validated, should be) User updates in any way, is wiped It's clear that the is not meant to be set when is not \"LoadBalancer\". The question is: 1) Fail validation? 2) Silently discard the value? 3) Warn and then discard the value? 4) Just warn and leave it. Because we allowed it in the past, but it is so volatile, I lean towards 3. and - the people most familair with this type. Edit: PrepareForUpdate() runs before warnings. So: (1) is easy (2) is easy (4) is slightly less easy than (2) (3) is slightly less easy than (4)\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nOMG change it to clusterIP as expected Status is wiped update status as ClusterIP ... and if I edit the service back to loadbalancer it keeps the status??\n/kind bug\n/retitle Service can be set when !=\nWe talked about this one at the SIG Network meeting today. suggested we use the feature gate for deprecation option to phase the current (problematic) functionality out.\n/triage accept\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /triage accept 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", "commid": "kubernetes_issue_119700", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ac4ebae47c7d23ffd624e9bcd37bc9a75f2ed0b7bccb921aebd67463713a4559", "query": "podClient.WaitForSuccess(podName, framework.PodStartTimeout) return podName } <del> It(\"should run the container as unprivileged when false [LinuxOnly] [NodeConformance]\", func() { // This test is marked LinuxOnly since it runs a Linux-specific command, and Windows does not support Windows escalation. </del> <ins> /* Release : v1.15 Testname: Security Context, privileged=false. Description: Create a container to run in unprivileged mode by setting pod's SecurityContext Privileged option as false. Pod MUST be in Succeeded phase. [LinuxOnly]: This test is marked as LinuxOnly since it runs a Linux-specific command. */ framework.ConformanceIt(\"should run the container as unprivileged when false [LinuxOnly] [NodeConformance]\", func() { </ins> podName := createAndWaitUserPod(false) logs, err := framework.GetPodLogs(f.ClientSet, f.Namespace.Name, podName, podName) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-f8a45a347ca0a58053d8639059bb6be0a8ec66e1196dbd0290c02922abc9dcd2", "text": "/kind cleanup /area conformance /area test /sig node /sig testing /sig architecture /assign /assign We have a number of tests that only have the tag that may make sense as tests, we should identify whether these tests cases meet (or could meet) the . We should open PR's to promote these if so. I would advise starting with the test/common cases\nGitHub didn't allow me to assign the following users: mgdevstack, mkurylec. Note that only and repo collaborators can be assigned. For more information please see <detailsIn response to : /kind cleanup /area conformance /area test /sig node /sig testing /sig architecture /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\n/assign\nThe tests in test/e2enode don't actually get run as part of Conformance as near as I can tell. If we want to run them as part of conformance, they need to be migrated into test/e2e/common. Some of the tests in e2enode may not be able to be ported over because they assume a level access we don't have in a conformance environment.\nregarding this testcase: [sig-storage] HostPath should support r/w [NodeConformance]: It uses hostPath and privileged=true, to read/write from /tmp folder. Which would you suggest is the best orientation to overcome the privilege mode setting and allow its promotion?\n/assign\nRegarding , the suite runs the test only if the kubelet configuration was required to have the QOS (cgroups-per-qos) enabled. This configuration for the kubelet is selected at the time the cluster is set up. Looking for where this might be configured found: where is set to true. For other settings it is also configured to true. where is set to true. BUT also found where it is mentioned that the flag is no longer available. Questions: would it be ok to promote this test to be conformance, even it can be skipped based on configuration of the cluster? And not supported in the containerized kubelet?\nI would consider cgroups to be an implementation detail that Conformance shouldn't be verifying\nIt uses hostPath and privileged=true, to read/write from /tmp folder.", "commid": "kubernetes_issue_66875", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ac4ebae47c7d23ffd624e9bcd37bc9a75f2ed0b7bccb921aebd67463713a4559", "query": "podClient.WaitForSuccess(podName, framework.PodStartTimeout) return podName } <del> It(\"should run the container as unprivileged when false [LinuxOnly] [NodeConformance]\", func() { // This test is marked LinuxOnly since it runs a Linux-specific command, and Windows does not support Windows escalation. </del> <ins> /* Release : v1.15 Testname: Security Context, privileged=false. Description: Create a container to run in unprivileged mode by setting pod's SecurityContext Privileged option as false. Pod MUST be in Succeeded phase. [LinuxOnly]: This test is marked as LinuxOnly since it runs a Linux-specific command. */ framework.ConformanceIt(\"should run the container as unprivileged when false [LinuxOnly] [NodeConformance]\", func() { </ins> podName := createAndWaitUserPod(false) logs, err := framework.GetPodLogs(f.ClientSet, f.Namespace.Name, podName, podName) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-b0f7522fd47a7c9f3d30009b5f18d7b37ba2aa8723a4c0ef112b90078054f0fc", "text": "Which would you suggest is the best orientation to overcome the privilege mode setting and allow its promotion? Michelle Au If my understanding is correct, on some platforms, writing to /tmp requires privileged. I don't see a way to to remove that requirement.\nIf my understanding is correct, on some platforms, writing to /tmp requires privileged. I don't see a way to to remove that requirement. Yeah writing to host doesn't seem like a thing we can expect of conformance tests. I wonder if it makes sense to tag this test with something to denote the requirement, ie: I see some tests in test/e2e_node use\nThe hostpath tests in already have a comment explaining this. Maybe the comment should be updated to be more clear that that is the reason why we can't add it to conformance.\nThat's /tmp on the host or in the container filesystem?\n/tmp on the host\nping what else remains to be done before we close this out? I am guessing that we want to close , is there anything beyond that?\nOnce tests under (issue- ) and are promoted we are good to close this issue. Short update for reference- None of [NodeConformance] tests from \"test/e2e_node\" seems eligible for [Conformance] promotion at this moment due to node level dependencies. Remaining [NodeConformance] tests from \"test/e2e\" has following status - Waiting for to be closed and then below tests would be promoted to Conformance Needs to be Promoted Can not be promoted to Conformance as //Slow by design Can not be promoted due to Node level dependency\nIssues 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\n/remove-lifecycle stale\n/lifecycle frozen\n/assign", "commid": "kubernetes_issue_66875", "tokennum": 428}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ac515c8075ba4ac849872fa6ab849ed2db3efebe3f7055bf346fb299919c9d83", "query": "// EnvVarSource represents a source for the value of an EnvVar. type EnvVarSource struct { <del> // Selects a field of the pod: supports metadata.name, metadata.namespace, metadata.labels, metadata.annotations, </del> <ins> // Selects a field of the pod: supports metadata.name, metadata.namespace, `metadata.labels['<KEY>']`, `metadata.annotations['<KEY>']`, </ins> // spec.nodeName, spec.serviceAccountName, status.hostIP, status.podIP, status.podIPs. // +optional FieldRef *ObjectFieldSelector `json:\"fieldRef,omitempty\" protobuf:\"bytes,1,opt,name=fieldRef\"`", "positive_passages": [{"docid": "doc-en-kubernetes-5018642be16ab87784521fef6d356d625aa306ba1fff6efc2d4048e42ef1a94c", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: When I tried to create a pod with env variables referencing to annotations: What you expected to happen: Should Proceed. As in It stated is a valid option How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.18.2 Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig docs\nThe API docs need to be updated to indicate the correct supported values. See for correct values\nYou are a lifesaver. Thank you!\n/assign I can try to update the api documentation", "commid": "kubernetes_issue_91165", "tokennum": 215}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ac58116a840399ad3abbbd179cd36efaaf1d1efd1b3f2ca941eba766eb066deb", "query": "out.Filter = (*config.PluginSet)(unsafe.Pointer(in.Filter)) out.PostFilter = (*config.PluginSet)(unsafe.Pointer(in.PostFilter)) out.Score = (*config.PluginSet)(unsafe.Pointer(in.Score)) <del> out.NormalizeScore = (*config.PluginSet)(unsafe.Pointer(in.NormalizeScore)) </del> out.Reserve = (*config.PluginSet)(unsafe.Pointer(in.Reserve)) out.Permit = (*config.PluginSet)(unsafe.Pointer(in.Permit)) out.PreBind = (*config.PluginSet)(unsafe.Pointer(in.PreBind))", "positive_passages": [{"docid": "doc-en-kubernetes-65d9c28fb77fe0bb882df060209fc22bf399af9c3b9dfe5829b0e5a45dc20b3d", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Consolidate ) into Score plugin set in config API. Why is this needed: NormalizeScore extension point is implemented in . We decided to treat NormalizeScore as an \"optional\" step of Score plugin, see . However, we deferred the removal of due to API review delays. Now that PR was merged. We can start the actual removal from the API and start the API review process. /sig scheduling\n/assign", "commid": "kubernetes_issue_80908", "tokennum": 113}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ac58de09aeb1517c34a337428ccefa0e0c3ce7872bd3cbb562323271dca9baef", "query": "<ins> # Hunting flaky tests in Kubernetes Sometimes unit tests are flaky.  This means that due to (usually) race conditions, they will occasionally fail, even though most of the time they pass. We have a goal of 99.9% flake free tests.  This means that there is only one flake in one thousand runs of a test. Running a test 1000 times on your own machine can be tedious and time consuming.  Fortunately, there is a better way to achieve this using Kubernetes. _Note: these instructions are mildly hacky for now, as we get run once semantics and logging they will get better_ There is a testing image ```brendanburns/flake``` up on the docker hub.  We will use this image to test our fix. Create a replication controller with the following config: ```yaml id: flakeController desiredState: replicas: 24 replicaSelector: name: flake podTemplate: desiredState: manifest: version: v1beta1 id: \"\" volumes: [] containers: - name: flake image: brendanburns/flake env: - name: TEST_PACKAGE value: pkg/tools - name: REPO_SPEC value: https://github.com/GoogleCloudPlatform/kubernetes restartpolicy: {} labels: name: flake labels: name: flake ``` ```./cluster/kubecfg.sh -c controller.yaml create replicaControllers``` This will spin up 100 instances of the test.  They will run to completion, then exit, the kubelet will restart them, eventually you will have sufficient runs for your purposes, and you can stop the replication controller: ```sh ./cluster/kubecfg.sh stop flakeController ./cluster/kubecfg.sh rm flakeController ``` Now examine the machines with ```docker ps -a``` and look for tasks that exited with non-zero exit codes (ignore those that exited -1, since that's what happens when you stop the replica controller) Happy flake hunting! </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-7c5448078f172c3dba4d1f6f6ed5d66f21d2fc0ea9dd38dbb1ed9b4cc49eea15", "text": "Right now, we have a mixture of user documentation and developer documentation in the top-level directory. We should make it easier to find a just user documentation. Step 1 would be to move developer documentation into a subdir like docs/development or something like that. User docs would stay in the top-level docs dir.\nmove to", "commid": "kubernetes_issue_1797", "tokennum": 71}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ac9ecd0a688bd43cc7c285d992e68ac15e796f0208726c9db9bf271d58d017ef", "query": "<ins> Resource Quota ======================================== This example demonstrates how resource quota and limits can be applied to a Kubernetes namespace. This example assumes you have a functional Kubernetes setup. Step 1: Create a namespace ----------------------------------------- This example will work in a custom namespace to demonstrate the concepts involved. Let's create a new namespace called quota-example: ```shell $ cluster/kubectl.sh create -f namespace.yaml $ cluster/kubectl.sh get namespaces NAME            LABELS             STATUS default         <none>             Active quota-example   <none>             Active ``` Step 2: Apply a quota to the namespace ----------------------------------------- By default, a pod will run with unbounded CPU and memory limits.  This means that any pod in the system will be able to consume as much CPU and memory on the node that executes the pod. Users may want to restrict how much of the cluster resources a given namespace may consume across all of its pods in order to manage cluster usage.  To do this, a user applies a quota to a namespace.  A quota lets the user set hard limits on the total amount of node resources (cpu, memory) and API resources (pods, services, etc.) that a namespace may consume. Let's create a simple quota in our namespace: ```shell $ cluster/kubectl.sh create -f quota.yaml --namespace=quota-example ``` Once your quota is applied to a namespace, the system will restrict any creation of content in the namespace until the quota usage has been calculated.  This should happen quickly. You can describe your current quota usage to see what resources are being consumed in your namespace. ``` $ cluster/kubectl.sh describe quota quota --namespace=quota-example Name:     quota Resource    Used  Hard --------    ----  ---- cpu     0m  20 memory      0m  1Gi persistentvolumeclaims  0m  10 pods      0m  10 replicationcontrollers  0m  20 resourcequotas    1 1 secrets     1 10 services    0m  5 ``` Step 3: Applying default resource limits ----------------------------------------- Pod authors rarely specify resource limits for their pods. Since we applied a quota to our project, let's see what happens when an end-user creates a pod that has unbounded cpu and memory by creating an nginx container. To demonstrate, lets create a replication controller that runs nginx: ```shell $ cluster/kubectl.sh run nginx --image=nginx --replicas=1 --namespace=quota-example CONTROLLER   CONTAINER(S)   IMAGE(S)   SELECTOR    REPLICAS nginx        nginx          nginx      run=nginx   1 ``` Now let's look at the pods that were created. ```shell $ cluster/kubectl.sh get pods --namespace=quota-example POD       IP        CONTAINER(S)   IMAGE(S)   HOST      LABELS    STATUS    CREATED   MESSAGE ``` What happened?  I have no pods!  Let's describe the replication controller to get a view of what is happening. ```shell cluster/kubectl.sh describe rc nginx --namespace=quota-example Name:   nginx Image(s): nginx Selector: run=nginx Labels:   run=nginx Replicas: 0 current / 1 desired Pods Status:  0 Running / 0 Waiting / 0 Succeeded / 0 Failed Events: FirstSeen       LastSeen      Count From        SubobjectPath Reason    Message Mon, 01 Jun 2015 22:49:31 -0400 Mon, 01 Jun 2015 22:52:22 -0400 7 {replication-controller }     failedCreate  Error creating: Pod \"nginx-\" is forbidden: Limited to 1Gi memory, but pod has no specified memory limit ``` The Kubernetes API server is rejecting the replication controllers requests to create a pod because our pods do not specify any memory usage. So let's set some default limits for the amount of cpu and memory a pod can consume: ```shell $ cluster/kubectl.sh create -f limits.yaml --namespace=quota-example limitranges/limits $ cluster/kubectl.sh describe limits limits --namespace=quota-example Name:   limits Type    Resource  Min Max Default ----    --------  --- --- --- Container cpu   - - 100m Container memory    - - 512Mi ``` Now any time a pod is created in this namespace, if it has not specified any resource limits, the default amount of cpu and memory per container will be applied as part of admission control. Now that we have applied default limits for our namespace, our replication controller should be able to create its pods. ```shell $ cluster/kubectl.sh get pods --namespace=quota-example POD           IP         CONTAINER(S)   IMAGE(S)   HOST                    LABELS      STATUS    CREATED     MESSAGE nginx-t40zm   10.0.0.2                             10.245.1.3/10.245.1.3   run=nginx   Running   2 minutes nginx          nginx                                          Running   2 minutes ``` And if we print out our quota usage in the namespace: ```shell cluster/kubectl.sh describe quota quota --namespace=quota-example Name:     quota Resource    Used    Hard --------    ----    ---- cpu     100m    20 memory      536870912 1Gi persistentvolumeclaims  0m    10 pods      1   10 replicationcontrollers  1   20 resourcequotas    1   1 secrets     1   10 services    0m    5 ``` You can now see the pod that was created is consuming explicit amounts of resources, and the usage is being tracked by the Kubernetes system properly. Summary ---------------------------- Actions that consume node resources for cpu and memory can be subject to hard quota limits defined by the namespace quota. Any action that consumes those resources can be tweaked, or can pick up namespace level defaults to meet your end goal. [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/resourcequota/README.md?pixel)]() </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-b9774b02da3d7547dcc6ec82c6d1246d6586e28e6fe16ad58f3c28b2558ac905", "text": "Resource quota example is missing readme. Was it once there and was accidentally deleted?\nI wrote something up in Origin repo I need to repurpose for Kubernetes. Sent from my iPhone", "commid": "kubernetes_issue_8749", "tokennum": 41}], "negative_passages": []}
{"query_id": "q-en-kubernetes-acc1f878c217fd7adba18c1872a95d2aaaeca7c8a9c04e096e4b38334ea94aba", "query": "package validation import ( <ins> \"fmt\" \"net\" </ins> \"k8s.io/apimachinery/pkg/util/validation/field\" \"k8s.io/kubernetes/federation/apis/federation\" \"k8s.io/kubernetes/pkg/api/validation\"", "positive_passages": [{"docid": "doc-en-kubernetes-9ef34f91f24cf25c8ee57899ba28766272335d7f286e3495efa44b9480fef2d3", "text": "Right now it is possible to add a cluster for which it won't be possible to create a client. For example client-related code does: while validation checks only: cc:\nswitching this to 1.6 as it's too late for 1.5. ok? (please switch it right back if you disagree)\nNot a release blocker for 1.7.\nare you interested in fixing this?\nof course, will do that.\n[MILESTONENOTIFIER] Milestone Removed Important: This issue was missing labels required for the v1.8 milestone for more than 7 days: kind: Must specify exactly one of [, , ]. priority: Must specify exactly one of [, , ]. Removing it from the milestone. <detailsAdditional instructions available <a href=\"\"here</aThe commands available for adding these labels are documented <a href=\"\"here</a</details", "commid": "kubernetes_issue_29911", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-acc4196190eea24ea44133d74f1897487191bf3099e4a941a823dfe8a63b45f2", "query": "# Use skopeo to find these values: https://github.com/containers/skopeo # # Example <del> # Manifest: skopeo inspect docker://gcr.io/k8s-staging-build-image/debian-base:buster-v1.3.0 # Arches: skopeo inspect --raw docker://gcr.io/k8s-staging-build-image/debian-base:buster-v1.3.0 </del> <ins> # Manifest: skopeo inspect docker://gcr.io/k8s-staging-build-image/debian-base:buster-v1.4.0 # Arches: skopeo inspect --raw docker://gcr.io/k8s-staging-build-image/debian-base:buster-v1.4.0 </ins> _DEBIAN_BASE_DIGEST = { <del> \"manifest\": \"sha256:d66137c7c362d1026dca670d1ff4c25e5b0770e8ace87ac3d008d52e4b0db338\", \"amd64\": \"sha256:a5ab028d9a730b78af9abb15b5db9b2e6f82448ab269d6f3a07d1834c571ccc6\", \"arm\": \"sha256:94e611363760607366ca1fed9375105b6c5fc922ab1249869b708690ca13733c\", \"arm64\": \"sha256:83512c52d44587271cd0f355c0a9a7e6c2412ddc66b8a8eb98f994277297a72f\", \"ppc64le\": \"sha256:9c8284b2797b114ebe8f3f1b2b5817a9c7f07f3f82513c49a30e6191a1acc1fc\", \"s390x\": \"sha256:d617637dd4df0bc1cfa524fae3b4892cfe57f7fec9402ad8dfa28e38e82ec688\", </del> <ins> \"manifest\": \"sha256:36652ef8e4dd6715de02e9b68e5c122ed8ee06c75f83f5c574b97301e794c3fb\", \"amd64\": \"sha256:afff10fcd513483e492807f8d934bdf0be4a237997f55e0f1f8e34c04a6cb213\", \"arm\": \"sha256:27e6e66ea3c4c4ca6dbfc8c949f0c4c870f038f4500fd267c242422a244f233c\", \"arm64\": \"sha256:4333a5edc9ce6d6660c76104749c2e50e6158e57c8e5956f732991bb032a8ce1\", \"ppc64le\": \"sha256:01a0ba2645883ea8d985460c2913070a90a098056cc6d188122942678923ddb7\", \"s390x\": \"sha256:610526b047d4b528d9e14b4f15347aa4e37af0c47e1307a2f7aebf8745c8a323\", </ins> } # Use skopeo to find these values: https://github.com/containers/skopeo # # Example <del> # Manifest: skopeo inspect docker://gcr.io/k8s-staging-build-image/debian-iptables:buster-v1.4.0 # Arches: skopeo inspect --raw docker://gcr.io/k8s-staging-build-image/debian-iptables:buster-v1.4.0 </del> <ins> # Manifest: skopeo inspect docker://gcr.io/k8s-staging-build-image/debian-iptables:buster-v1.5.0 # Arches: skopeo inspect --raw docker://gcr.io/k8s-staging-build-image/debian-iptables:buster-v1.5.0 </ins> _DEBIAN_IPTABLES_DIGEST = { <del> \"manifest\": \"sha256:87f97cf2b62eb107871ee810f204ccde41affb70b29883aa898e93df85dea0f0\", \"amd64\": \"sha256:da837f39cf3af78adb796c0caa9733449ae99e51cf624590c328e4c9951ace7a\", \"arm\": \"sha256:bb6677337a4dbc3e578a3e87642d99be740dea391dc5e8987f04211c5e23abcd\", \"arm64\": \"sha256:6ad4717d69db2cc47bc2efc91cebb96ba736be1de49e62e0deffdbaf0fa2318c\", \"ppc64le\": \"sha256:168ccfeb861239536826a26da24ab5f68bb5349d7439424b7008b01e8f6534fc\", \"s390x\": \"sha256:5a88d4f4c29bac5b5c93195059b928f7346be11d0f0f7f6da0e14c0bfdbd1362\", </del> <ins> \"manifest\": \"sha256:abe8cef9e116f2d5ec1175c386e33841ff3386779138b425af876384b0fd7ccb\", \"amd64\": \"sha256:b4b8b1e0d4617011dd03f20b804cc2e50bf48bafc36b1c8c7bd23fd44bfd641e\", \"arm\": \"sha256:09f79b3a00268705a8f8462f1528fed536e204905359f21e9965f08dd306c60a\", \"arm64\": \"sha256:b4fa11965f34a9f668c424b401c0af22e88f600d22c899699bdb0bd1e6953ad6\", \"ppc64le\": \"sha256:0ea0be4dec281b506f6ceef4cb3594cabea8d80e2dc0d93c7eb09d46259dd837\", \"s390x\": \"sha256:50ef25fba428b6002ef0a9dea7ceae5045430dc1035d50498a478eefccba17f5\", </ins> } # Use skopeo to find these values: https://github.com/containers/skopeo", "positive_passages": [{"docid": "doc-en-kubernetes-ee0826757468ea334f95c77509b257c3d392b6713b4311ba7afa125d642dcec9", "text": "The based container images for are shipped with the wrong architecture within the manifest if not amd64: Refers to We updated the images a few minutes ago to buster-v1.3.0, which are now ready to be used as base for the multi-architecture images. If the images contain the right architectures, then it may magically happen that the kube-proxy images are fixed, too. This is because we already use the build syntax for it: /cc\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig release", "commid": "kubernetes_issue_98229", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ad36e5a41968266b5d487d1b5190950091462c03fc5c10c9979416c596cba087", "query": "defaultVersion := cmdutil.OutputVersion(cmd, clientConfig.Version) results := editResults{} for { <del> obj, err := resource.AsVersionedObject(infos, false, defaultVersion) </del> <ins> objs, err := resource.AsVersionedObjects(infos, defaultVersion) </ins> if err != nil { return preservedFile(err, results.file, out) } <ins> // if input object is a list, traverse and edit each item one at a time for _, obj := range objs { // TODO: add an annotating YAML printer that can print inline comments on each field, //   including descriptions or validation errors // generate the file to edit buf := &bytes.Buffer{} if err := results.header.writeTo(buf); err != nil { return preservedFile(err, results.file, out) } if err := printer.PrintObj(obj, buf); err != nil { return preservedFile(err, results.file, out) } original := buf.Bytes() </ins> <del> // TODO: add an annotating YAML printer that can print inline comments on each field, //   including descriptions or validation errors // generate the file to edit buf := &bytes.Buffer{} if err := results.header.writeTo(buf); err != nil { return preservedFile(err, results.file, out) } if err := printer.PrintObj(obj, buf); err != nil { return preservedFile(err, results.file, out) } original := buf.Bytes() // launch the editor edit := editor.NewDefaultEditor() edited, file, err := edit.LaunchTempFile(\"kubectl-edit-\", ext, buf) if err != nil { return preservedFile(err, results.file, out) } </del> <ins> // launch the editor edit := editor.NewDefaultEditor() edited, file, err := edit.LaunchTempFile(\"kubectl-edit-\", ext, buf) if err != nil { return preservedFile(err, results.file, out) } </ins> <del> // cleanup any file from the previous pass if len(results.file) > 0 { os.Remove(results.file) } </del> <ins> // cleanup any file from the previous pass if len(results.file) > 0 { os.Remove(results.file) } </ins> <del> glog.V(4).Infof(\"User edited:n%s\", string(edited)) fmt.Printf(\"User edited:n%s\", string(edited)) lines, err := hasLines(bytes.NewBuffer(edited)) if err != nil { return preservedFile(err, file, out) } if bytes.Equal(original, edited) { if len(results.edit) > 0 { preservedFile(nil, file, out) } else { os.Remove(file) </del> <ins> glog.V(4).Infof(\"User edited:n%s\", string(edited)) lines, err := hasLines(bytes.NewBuffer(edited)) if err != nil { return preservedFile(err, file, out) </ins> } <del> fmt.Fprintln(out, \"Edit cancelled, no changes made.\") return nil } if !lines { if len(results.edit) > 0 { preservedFile(nil, file, out) } else { os.Remove(file) </del> <ins> // Compare content without comments if bytes.Equal(stripComments(original), stripComments(edited)) { if len(results.edit) > 0 { preservedFile(nil, file, out) } else { os.Remove(file) } fmt.Fprintln(out, \"Edit cancelled, no changes made.\") continue } if !lines { if len(results.edit) > 0 { preservedFile(nil, file, out) } else { os.Remove(file) } fmt.Fprintln(out, \"Edit cancelled, saved file was empty.\") continue </ins> } <del> fmt.Fprintln(out, \"Edit cancelled, saved file was empty.\") return nil } results = editResults{ file: file, } </del> <ins> results = editResults{ file: file, } </ins> <del> // parse the edited file updates, err := rmap.InfoForData(edited, \"edited-file\") if err != nil { return preservedFile(err, file, out) } </del> <ins> // parse the edited file updates, err := rmap.InfoForData(edited, \"edited-file\") if err != nil { return fmt.Errorf(\"The edited file had a syntax error: %v\", err) } </ins> <del> // annotate the edited object for kubectl apply if err := kubectl.UpdateApplyAnnotation(updates); err != nil { return preservedFile(err, file, out) } </del> <ins> // annotate the edited object for kubectl apply if err := kubectl.UpdateApplyAnnotation(updates); err != nil { return preservedFile(err, file, out) } </ins> <del> visitor := resource.NewFlattenListVisitor(updates, rmap) </del> <ins> visitor := resource.NewFlattenListVisitor(updates, rmap) </ins> <del> // need to make sure the original namespace wasn't changed while editing if err = visitor.Visit(resource.RequireNamespace(cmdNamespace)); err != nil { return preservedFile(err, file, out) } </del> <ins> // need to make sure the original namespace wasn't changed while editing if err = visitor.Visit(resource.RequireNamespace(cmdNamespace)); err != nil { return preservedFile(err, file, out) } </ins> <del> // use strategic merge to create a patch originalJS, err := yaml.ToJSON(original) if err != nil { return preservedFile(err, file, out) } editedJS, err := yaml.ToJSON(edited) if err != nil { return preservedFile(err, file, out) } patch, err := strategicpatch.CreateStrategicMergePatch(originalJS, editedJS, obj) // TODO: change all jsonmerge to strategicpatch // for checking preconditions preconditions := []jsonmerge.PreconditionFunc{} if err != nil { glog.V(4).Infof(\"Unable to calculate diff, no merge is possible: %v\", err) return preservedFile(err, file, out) } else { preconditions = append(preconditions, jsonmerge.RequireKeyUnchanged(\"apiVersion\")) preconditions = append(preconditions, jsonmerge.RequireKeyUnchanged(\"kind\")) preconditions = append(preconditions, jsonmerge.RequireMetadataKeyUnchanged(\"name\")) results.version = defaultVersion } </del> <ins> // use strategic merge to create a patch originalJS, err := yaml.ToJSON(original) if err != nil { return preservedFile(err, file, out) } editedJS, err := yaml.ToJSON(edited) if err != nil { return preservedFile(err, file, out) } patch, err := strategicpatch.CreateStrategicMergePatch(originalJS, editedJS, obj) // TODO: change all jsonmerge to strategicpatch // for checking preconditions preconditions := []jsonmerge.PreconditionFunc{} if err != nil { glog.V(4).Infof(\"Unable to calculate diff, no merge is possible: %v\", err) return preservedFile(err, file, out) } else { preconditions = append(preconditions, jsonmerge.RequireKeyUnchanged(\"apiVersion\")) preconditions = append(preconditions, jsonmerge.RequireKeyUnchanged(\"kind\")) preconditions = append(preconditions, jsonmerge.RequireMetadataKeyUnchanged(\"name\")) results.version = defaultVersion } </ins> <del> if hold, msg := jsonmerge.TestPreconditionsHold(patch, preconditions); !hold { fmt.Fprintf(out, \"error: %s\", msg) return preservedFile(nil, file, out) } </del> <ins> if hold, msg := jsonmerge.TestPreconditionsHold(patch, preconditions); !hold { fmt.Fprintf(out, \"error: %s\", msg) return preservedFile(nil, file, out) } </ins> <del> err = visitor.Visit(func(info *resource.Info, err error) error { patched, err := resource.NewHelper(info.Client, info.Mapping).Patch(info.Namespace, info.Name, api.StrategicMergePatchType, patch) if err != nil { fmt.Fprintln(out, results.addError(err, info)) </del> <ins> err = visitor.Visit(func(info *resource.Info, err error) error { patched, err := resource.NewHelper(info.Client, info.Mapping).Patch(info.Namespace, info.Name, api.StrategicMergePatchType, patch) if err != nil { fmt.Fprintln(out, results.addError(err, info)) return nil } info.Refresh(patched, true) cmdutil.PrintSuccess(mapper, false, out, info.Mapping.Resource, info.Name, \"edited\") </ins> return nil <ins> }) if err != nil { return preservedFile(err, file, out) </ins> } <del> info.Refresh(patched, true) cmdutil.PrintSuccess(mapper, false, out, info.Mapping.Resource, info.Name, \"edited\") return nil }) if err != nil { return preservedFile(err, file, out) } if results.retryable > 0 { fmt.Fprintf(out, \"You can run `kubectl replace -f %s` to try this update again.n\", file) return errExit } if results.conflict > 0 { fmt.Fprintf(out, \"You must update your local resource version and run `kubectl replace -f %s` to overwrite the remote changes.n\", file) return errExit </del> <ins> if results.retryable > 0 { fmt.Fprintf(out, \"You can run `kubectl replace -f %s` to try this update again.n\", file) return errExit } if results.conflict > 0 { fmt.Fprintf(out, \"You must update your local resource version and run `kubectl replace -f %s` to overwrite the remote changes.n\", file) return errExit } if len(results.edit) == 0 { if results.notfound == 0 { os.Remove(file) } else { fmt.Fprintf(out, \"The edits you made on deleted resources have been saved to %qn\", file) } } </ins> } if len(results.edit) == 0 { <del> if results.notfound == 0 { os.Remove(file) } else { fmt.Fprintf(out, \"The edits you made on deleted resources have been saved to %qn\", file) } </del> return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-5d8539be161cacf223528437869590f13423a31b1176c381211bcba6b79e0cca", "text": "When trying to edit multiple resources, for example: will panic. Ref as the possible cause cc\nif was the cause, any fix needs to happen in 1.1 as well, was already cherry picked there\nAlso shows that we need a test for this case.\nis the cause. When we edit multiple resources (i.e., list-type objects), the list's Accessor.annotations (type ) is nil and will panic when UpdateApplyAnnotation tries to SetAnnotations ().", "commid": "kubernetes_issue_15907", "tokennum": 108}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ad37c38d08e42ab61110b1b4d3870be9b90fe2526bdbdd29f964ad6463465a40", "query": "return err } if ipCorrect && portsCorrect { <del> return nil </del> <ins> return r.epAdapter.EnsureEndpointSliceFromEndpoints(metav1.NamespaceDefault, e) </ins> } if !ipCorrect { // We *always* add our own IP address.", "positive_passages": [{"docid": "doc-en-kubernetes-12f7047d8d873a7d6bac7023fc38517c350449071b3fe2b6d53f3ea14de5351f", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: EndpointSlice for masters was not created after enabling EndpointSlice on a pre-existing cluster. Only those EndpointSlices managed by kube-controller-manager were created. What you expected to happen: EndpointSlice for masters should be created after enabling EndpointSlice on a pre-existing cluster, the same as the EndpointSlices managed by kube-controller-manager. How to reproduce it (as minimally and precisely as possible): kubeadm to create a cluster: the EndpointSlice feature by editing the kube-apiserver, kube-controller-manager, kube-proxy manifest kube-apiserver and kube-controller-manager is restarted, the EndpointSlice in namespace will be missing. Anything else we need to know?: Environment: Kubernetes version (use ):Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools:Network plugin and version (if this is a network-related bug): Others:\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/remove-triage unresolved /assign", "commid": "kubernetes_issue_84419", "tokennum": 307}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ad5cc60efa71774aff040a9930b30ad60d3fd4deef1f09301e2c65cb13ece7b7", "query": "if rOpts != nil { hc.Resources = dockercontainer.Resources{ Memory:     rOpts.GetMemoryLimitInBytes(), <del> MemorySwap: -1, </del> <ins> MemorySwap: dockertools.DefaultMemorySwap(), </ins> CPUShares:  rOpts.GetCpuShares(), CPUQuota:   rOpts.GetCpuQuota(), CPUPeriod:  rOpts.GetCpuPeriod(),", "positive_passages": [{"docid": "doc-en-kubernetes-2c477631a31f290ae271a7ca0a83a97399cbf63c4cfd883674b6ddce7387fc19", "text": "What happened: Latest kubelet + Windows Docker version 1.14.0-dev refused to start any containers, error output: \"invalid option: Windows does not support MemorySwap\" How to reproduce it (as minimally and precisely as possible): It's always reproducible with Windows Docker 1.14.0-dev + latest kubelet code base. Anything else do we need to know: It didn't happen for Windows Docker 1.12.2-cs2-ws-beta. The reason behind the issue was because new code was for Windows Docker to check Resources parameters, it doesn't accept a non-zero value for MemorySwap: But kubelet was default to set an unlimited (-1) value. The issue was gone in my setup after applied a private fix to disable MemorySwap by set it to zero for Windows.", "commid": "kubernetes_issue_39003", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ada0426ef87cb8986ec8fe69856ef5b044833ae25d8616646d20048e1de93261", "query": "import ( \"context\" <ins> \"crypto/tls\" </ins> \"encoding/json\" \"flag\" \"fmt\"", "positive_passages": [{"docid": "doc-en-kubernetes-88c095cfe151193749adeb925825c9856381f9f8544c8822d93b8eb731e64566", "text": "ci-kubernetes-node-kubelet-serial-hugepages when start the pod with the resources requests that contain multiple hugepages resources should set correct hugetlb mount and limit under the container cgroup Unexpected error: \"pod ran to completion\", Multiple sizes huge pages is going to be graduated to GA, so having this test job fixed is quite important.\n/sig node\n/assign\n/triage accepted\n/cc\nI did a small analysis and I can see that the pod failed to start, I can not find any failure messages under the kubelet log, so it really hard to say why it failed.\nwere you able to reproduce it locally? btw, there is a \"right way\" to fix this - to fix dynamic update of a hugepage resources. This would eliminate need in a kubelet restart. There is even a PR for that: , we just need to make it working again.\nafter conversation with on slack I'd say we should stick to the current procedure - restarting kubelet when hugepages allocation changes. So, we should investigate why kubelet doesn't restart properly in this test case and fix it.\nNope, I failed to reproduce it locally, also under the CI, it does not appear often. The best thing will be to describe the pod in case if it failed, so we will see the reason.\nunder the code we have so from the log , I can see that the kubelet received the pod before the kubelet stopped, so the problem that pod dropped to Failed state because of the kubelet stop.\nSo some additional details, the one who responsible to restart the kubelet again, is the server service: restart the kubelet service are waiting for hugepages to be available are starting the pod server service restart the kubelet again because it was not healthy for too long - failed to start because of the kubelet restart\ngreat findings! Should we just stop the kubelet and let the server service to start it again? We can also check if the kubelet is restarted successfully before starting the pod.\nI tried it under the PR , also I unsure how can we check if the kubelet restarted successfully. All tests that I wrote before I checked if the node has NotReady state and waited until it will be Ready, but in case of the restart probably the node will always have Ready state because the time period is very short. I will continue to investigate and will check locally how can I fix it.", "commid": "kubernetes_issue_99402", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ada0426ef87cb8986ec8fe69856ef5b044833ae25d8616646d20048e1de93261", "query": "import ( \"context\" <ins> \"crypto/tls\" </ins> \"encoding/json\" \"flag\" \"fmt\"", "positive_passages": [{"docid": "doc-en-kubernetes-df5fd4d114576094d5b1a71b893d21a3e13b2c561e9313633a9dfbe243849634", "text": "So the only reliable solution that I found, it just trying to start the pod number of times. I tested it 5 times and the test passed. Can you please review\nCan we access kubelet service from hugepage test cases? If we can we can use its APIs like or to check if kubelet is ready after the restart. Overall I have a feeling of duplication test/e2enode/services functionality in This is a main reason for this and similar bugs I believe. It would be nice to get rid of this duplication if possible. That would nicely isolate kubelet service controls in one place and eliminate conflicts like this one. wdyt?\nnot really, the used mostly to start all needed components to emulate the cluster(not only the kubelet) and the test does not have access to it. I think you can separate the readiness check under the importable method, but it worth the separate PR.\nI updated the PR to check the healthiness of the kubelet and looks like it works just fine.\nthank you. it looks good to me so far. I'll add lgtm label when is merged and tests are all green.\nthe job is still flaky. can you reopen this issue?\nI opened a different one - , the issue can affect any job, not only the hugepages one.\nI can open a fix to W/A an issue(start the pod until it will succeed), it should fix all problems, WDYT?\ni think it's ok as a workaround, until is fixed\nwould it be better to wait until api server reports correct resource value before running the pod?\nWe are waiting for it, the problem that the scheduler and the kubelet see a different picture regarding resources requested by pods.\nok. In this case restarting the pod until it succeeds seems reasonable to me to fix the flakiness until is fixed.\nany progress on the workaround fix?", "commid": "kubernetes_issue_99402", "tokennum": 404}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ae1fe1130ae67618d7e606d8657e31c25d135d03d932e27325a80b7858907cc8", "query": "} func runStaticPodTest(c *client.Client, configFilePath string) { <del> manifest := `version: v1beta2 id: static-pod </del> <ins> var testCases = []struct { desc         string fileContents string }{ { desc: \"static-pod-from-manifest\", fileContents: `version: v1beta2 id: static-pod-from-manifest </ins> containers: <del> - name: static-container image: kubernetes/pause` manifestFile, err := ioutil.TempFile(configFilePath, \"\") defer os.Remove(manifestFile.Name()) ioutil.WriteFile(manifestFile.Name(), []byte(manifest), 0600) // Wait for the mirror pod to be created. podName := \"static-pod-localhost\" namespace := kubelet.NamespaceDefault if err := wait.Poll(time.Second, time.Minute*2, podRunning(c, namespace, podName)); err != nil { if pods, err := c.Pods(namespace).List(labels.Everything()); err == nil { for _, pod := range pods.Items { glog.Infof(\"pod found: %s/%s\", namespace, pod.Name) } } glog.Fatalf(\"FAILED: mirror pod has not been created or is not running: %v\", err) } // Delete the mirror pod, and wait for it to be recreated. c.Pods(namespace).Delete(podName) if err = wait.Poll(time.Second, time.Second*30, podRunning(c, namespace, podName)); err != nil { glog.Fatalf(\"FAILED: mirror pod has not been re-created or is not running: %v\", err) } // Remove the manifest file, and wait for the mirror pod to be deleted. os.Remove(manifestFile.Name()) if err = wait.Poll(time.Second, time.Second*30, podNotFound(c, namespace, podName)); err != nil { glog.Fatalf(\"FAILED: mirror pod has not been deleted: %v\", err) </del> <ins> - name: static-container image: kubernetes/pause`, }, { desc: \"static-pod-from-spec\", fileContents: `{ \"kind\": \"Pod\", \"apiVersion\": \"v1beta3\", \"metadata\": { \"name\": \"static-pod-from-spec\" }, \"spec\": { \"containers\": [{ \"name\": \"static-container\", \"image\": \"kubernetes/pause\" }] } }`, }, </ins> } <ins> for _, testCase := range testCases { func() { desc := testCase.desc manifestFile, err := ioutil.TempFile(configFilePath, \"\") defer os.Remove(manifestFile.Name()) ioutil.WriteFile(manifestFile.Name(), []byte(testCase.fileContents), 0600) // Wait for the mirror pod to be created. podName := fmt.Sprintf(\"%s-localhost\", desc) namespace := kubelet.NamespaceDefault if err := wait.Poll(time.Second, time.Minute*2, podRunning(c, namespace, podName)); err != nil { if pods, err := c.Pods(namespace).List(labels.Everything()); err == nil { for _, pod := range pods.Items { glog.Infof(\"pod found: %s/%s\", namespace, pod.Name) } } glog.Fatalf(\"%s FAILED: mirror pod has not been created or is not running: %v\", desc, err) } // Delete the mirror pod, and wait for it to be recreated. c.Pods(namespace).Delete(podName) if err = wait.Poll(time.Second, time.Second*30, podRunning(c, namespace, podName)); err != nil { glog.Fatalf(\"%s FAILED: mirror pod has not been re-created or is not running: %v\", desc, err) } // Remove the manifest file, and wait for the mirror pod to be deleted. os.Remove(manifestFile.Name()) if err = wait.Poll(time.Second, time.Second*30, podNotFound(c, namespace, podName)); err != nil { glog.Fatalf(\"%s FAILED: mirror pod has not been deleted: %v\", desc, err) } }() } </ins> } func runReplicationControllerTest(c *client.Client) {", "positive_passages": [{"docid": "doc-en-kubernetes-56027fa26048aea64718f2bd7d7c5d6f58ddca1472c1fc738c03141b6dea3ad6", "text": "Currently it assumes it can read ContainerManifest - it should try both\nWhy not hold on this until we have Kubelet-read-Pod in?\nAlso the HTTP source has the same problem.\nIt should read Pod. Changed the title.\nIdeally, I'd like all Pods created directly via Kubelet to be to etcd and surfaced via the API. If updates are made via the API, I'd like those to propagate back to the node. We can discuss whether the config file should be updated or ignored. At some point, I'd like Kubelet to persistently cache pods received from the apiserver, perhaps by just writing them all out as config files.\nis the issue to sync local pods back to apiserver.\nthis is somewhat related to other issues we talked about.\nDetail: We want locally specified pods to be able to use YAML config files, but we also want to rip YAML out of the API server . The config-file behavior should be as similar to the kubectl experience. Kubelet could use parts of the kubectl library to translate YAML to JSON. Vision: Eventually, I'd like Kubelet to use the apiserver library and support exactly the same Pod API as the master, at which time I'd like kubectl be able to create pods directly on Kubelets, as well as reading from config files. I also expect to have a per-node controller . I'd like to be able to use the per-node controller to update pods started via config files (or direct kubectl-kubelet pods), overriding those original files. For availability and self-hosting, we'll eventually need local checkpointing , ideally just using serialized JSON for each object. If Kubelet used apiserver, this could be done using a custom registry implementation.\nI think that is a prerequisite for it.\nIf noone picks it up, I'm going to start working on it tomorrow.\nthanks, wojtek-t\nfixed it for http channel", "commid": "kubernetes_issue_3372", "tokennum": 445}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ae35ac61df8b4a51ddd8638b02563d3eb4b915fb8692d8f91641b90c9fb968a7", "query": "func (o *ResourcesOptions) Validate() error { var err error if len(o.Limits) == 0 && len(o.Requests) == 0 { <del> return fmt.Errorf(\"you must specify an update to requests or limits (in the form of --requests/--limits)\") </del> <ins> return fmt.Errorf(\"you must specify an update to requests or limits or  (in the form of --requests/--limits)\") </ins> } o.ResourceRequirements, err = kubectl.HandleResourceRequirements(map[string]string{\"limits\": o.Limits, \"requests\": o.Requests})", "positive_passages": [{"docid": "doc-en-kubernetes-f45c12318e35043c65362c27e361ee13adfef369e183f2b4f0557c11353bd9e9", "text": "from https://k8s-\nReally suspect this is\nThis is putting us into test-go post-commit run is broken\ncc:\nmarked this p0 - if a fix isn't easy let's try to identify what introduced this and revert.\nThis flake on: 2016-10-30 07:19 PDT First instance: : It is flaking frequently, blocking PRs from getting merged, and slowing the submit queue ( at 75%). As on-call, I'm going to try and identify the cluprit and revert. Can use all help in doing so.\ncan you investigate whether your additional tests could cause this (by breaking the deployment of those pods, for instance) , Saad Ali wrote:\nPR looks most suspect to me. It mucked with , and the errors we are seeing in each of the failures is related to : That PR was merged at Oct 30, 2016, 6:18 AM PDT and the first flake in was at Oct 30, 2016, 7:19 AM PDT. Thoughts? CC\nI'm going to initiate a revert of to see if that fixes the issue\nIMO we can just change the flaky test to not get pods but some other resources, such as deployments. We can't really expect to clean up pods immediately.\nI'm going to proceed with revert (). Please feel free to send a follow up PR to handle this more gracefully.\nGoing to leave this opened until we have a few hours of runs with the revert. Want to verify, with some degree of certainty, that the revert took care of this flake.\nWe had 15 green runs of in a row. Considering this flake fixed.", "commid": "kubernetes_issue_35898", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-aec1e1cf3a1ce5bc7d6d21c2e4720b1caab8fdb00bb364f84704f860fd3fded1", "query": "}) } } <ins> func TestGetExcludedChecks(t *testing.T) { type args struct { r *http.Request } tests := []struct { name string r    *http.Request want sets.String }{ {\"Should have no excluded health checks\", createGetRequestWithUrl(\"/healthz?verbose=true\"), sets.NewString(), }, {\"Should extract out the ping health check\", createGetRequestWithUrl(\"/healthz?exclude=ping\"), sets.NewString(\"ping\"), }, {\"Should extract out ping and log health check\", createGetRequestWithUrl(\"/healthz?exclude=ping&exclude=log\"), sets.NewString(\"ping\", \"log\"), }, } for _, tt := range tests { t.Run(tt.name, func(t *testing.T) { if got := getExcludedChecks(tt.r); !reflect.DeepEqual(got, tt.want) { t.Errorf(\"getExcludedChecks() = %v, want %v\", got, tt.want) } }) } } func createGetRequestWithUrl(rawUrlString string) *http.Request { url, _ := url.Parse(rawUrlString) return &http.Request{ Method: http.MethodGet, Proto:  \"HTTP/1.1\", URL:    url, } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-01cc291fb1d6afeae9b284d60dd407b578a72d26e4c50043cbdf654c92184c45", "text": "What would you like to be : Add support to the kube-apiserver so that we can disable health-checks via query params. Why is this needed: Currently, the healthz endpoint is inflexible in that any and all health checks are currently executed when the endpoint is hit. Since the kube-apiserver only currently supports a liveness check, this means all persistent health check failures will eventually result in a kubelet driven restart. However, this may not be desirable behavior if you have additional monitoring services layered on top of your control plane. For instance, take the etcd failure from the perspective of the kube-apiserver. Currently, persistent failures during the etcd health check from the api-server healthz endpoint will cause the kube-apiserver to be restarted. This sometimes helps (in the case of a faulty etcd-client connection) but also can be detrimental (the kube-apiserver restarts until the etcd cluster is functioning, then the kube-apiserver bombards the etcd cluster with requests to update local caches, saturating the etcd cluster with requests, causing it to timeout on its own liveness probes and trigger a kubelet-driven restart). Let's say that we could now disable etcd from our liveness health check. Then if we had an external monitoring service, we could ask independently ask etcd if it was healthy and we could also ask the kube-apiserver if it thought etcd was unhealthy. Based on the combination of those answers, we could enable more intelligent responses to certain situation, like restarting the kube-apiserver when it thought etcd was unhealthy but etcd was actually reporting as healthy but not doing so when etcd was actually unhealthy. This feature is backwards-compatible and opt-in. There would be no impact to existing behavior unless these query params are actually used. /sig api-machinery /kind feature\n/cc\nSGTM\n/assign", "commid": "kubernetes_issue_70591", "tokennum": 432}], "negative_passages": []}
{"query_id": "q-en-kubernetes-aed8c9b033062fc2f6ec18e306ca56caf114dd687fa01ed814ab4c1fa847a696", "query": "* [kubectl](kubectl.md)\t - kubectl controls the Kubernetes cluster manager <del> ###### Auto generated by spf13/cobra on 5-Apr-2016 </del> <ins> ###### Auto generated by spf13/cobra on 3-Jun-2016 </ins> <!-- BEGIN MUNGE: GENERATED_ANALYTICS --> [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/kubectl/kubectl_exec.md?pixel)]()", "positive_passages": [{"docid": "doc-en-kubernetes-b8cb95fef1c3c524a6b804cd28cd2236820a76e473144ffd27898d08f0344824", "text": "Need to finish so the client allows you to select an init container, and verify the kubelet works correctly.\n(this is a nice intersection of new in 1.3, node and usability, if anyone wants to give it a shot. Pretty sure Clayton is busier than I am and I don't think I'll get to it)\nWill be happy to review any changes - should be fairly straightforward.\nYes, init containers are \"run to completion\" always. , harryz wrote:\nIIUC when the init containers of pod have not complete, the pod should be in status, which means will fail, if init containers run to completion, they will exit, still fail. I don't know what you mean exec should work on init containers?\nthe init container is still up and running even when the pod is in pending, we should be able to exec and debug why it's hung, for example.\nadd a straightforward exec implementation ptal.", "commid": "kubernetes_issue_25818", "tokennum": 207}], "negative_passages": []}
{"query_id": "q-en-kubernetes-af01767c5412f46657ddb2037870634c72880837b2f8b92e4eb3083de1ae0946", "query": "result.User = os.Getenv(\"USER\") } <del> if bastion := os.Getenv(\"KUBE_SSH_BASTION\"); len(bastion) > 0 { </del> <ins> if bastion := os.Getenv(sshBastionEnvKey); len(bastion) > 0 { </ins> stdout, stderr, code, err := runSSHCommandViaBastion(cmd, result.User, bastion, host, signer) result.Stdout = stdout result.Stderr = stderr", "positive_passages": [{"docid": "doc-en-kubernetes-375711dd290c57e850707ef6745091e3080fe654060082beb69e30fe80db0e88", "text": "ci-kubernetes-e2e-gce-scale-correctness Kubernetes e2e suite: [sig-node] SSH should SSH to all nodes and run commands kubetest.Test Jul 10 14:01:51 UTC+0200 Kubernetes e2e suite: [sig-node] SSH should SSH to all nodes and run commands: more . Test /sig node\n/cc\n/triage accepted\nUhhh, this may help here\n/milestone v1.22\n/sig scalability FYI\nI got annoyed that I couldn't click through to see the other logs, so now you can, ref: (spyglass doesn't render build- because it's 500MB, and the limit for rendering is 100MB)\n/assign SIG Scalability chairs/TLs, please find someone to address or call this a non-release-blocking failure\nAssigning to current scalability oncall (): /assign\nThis is sig-node issue - should be addres by SIG-node folks. /sig node\nis being discussed as a fix for this and I'm not sure it's correct\nis it sig scalability's intent that 5k node clusters should support SSH?\nThe SSH test in question passes in the \"default\" job: So the fact that this failure is unique to a scalability job means to me that scalability needs to own at least some part of this\nI did a little bit of digging and ci-kubernetes-e2e-gce-scale-correctness uses option in kubetest, which according to seems to be setting KUBESSHBASTION env. So I believe this is main difference between our scalability job and \"default\".\nDebugging the test in and providing a fix there. The crictl host PR () is doing something different.", "commid": "kubernetes_issue_103688", "tokennum": 400}], "negative_passages": []}
{"query_id": "q-en-kubernetes-af3b62fd3d98e7596533a817bb4d172662e9f3b64841679a414460a8bfe15ef5", "query": "}) matchExpectations := ptrMatchAllFields(gstruct.Fields{ \"Node\": gstruct.MatchAllFields(gstruct.Fields{ <del> \"NodeName\":  Equal(framework.TestContext.NodeName), \"StartTime\": recent(maxStartAge), \"SystemContainers\": gstruct.MatchElements(summaryObjectID, gstruct.IgnoreExtras, gstruct.Elements{ \"kubelet\": sysContExpectations, \"runtime\": sysContExpectations, }), </del> <ins> \"NodeName\":         Equal(framework.TestContext.NodeName), \"StartTime\":        recent(maxStartAge), \"SystemContainers\": gstruct.MatchAllElements(summaryObjectID, systemContainers), </ins> \"CPU\": ptrMatchAllFields(gstruct.Fields{ \"Time\":                 recent(maxStatsAge), \"UsageNanoCores\":       bounded(100E3, 2E9),", "positive_passages": [{"docid": "doc-en-kubernetes-237446a2101b1d0e3896762c3997d0b07e17e89bcd32bef5edcdc8a493c92d82", "text": "Kubernetes version (use ): 6 Environment: GCE What happened: I created a cluster for Heapster testing purposes to debug failing test in It turned out that Summary API does not export system/misc stats in SystemContainers section (though there are kubelet and docker stats). Everything works as expected on nodes. See also https://k8s-\nWhat node OS were you using? We don't create the system (misc) container on systemd, so it's expected that GCI nodes don't report those stats.\nThe default configuration for 1.4, which is: master: GCI nodes: Container VM\nAre the nodes running 1.4.6 too? There was a bug with this in 1.4.5, but it should have been fixed in 1.4.6.\nYes, both are running in 1.4.6. If you want to reproduce from Heapster current head run . It will take some time and as a side effect you should have a cluster with the mentioned problem. This was catch by integration tests and I temporary disabled the check here\nif you have spare cycles, can you look into this?\nfriendly ping\nLooking at it now\nI have found a couple things so far. On the containerVM nodes, cadvisor is exporting a container with \"name\": \"/system\" On the GCI Master, cadvisor is exporting a container with \"name\": \"\" The has this: \"{% set system_container = \"--system-cgroups=/system\" -%}\" (/system is the default misc container name) So the real question is: Should cadvisor export \"/system\" instead of \"\" on GCI? Or should we be configuring GCI to use \"--system-\"?\nI thought we fix this very issue for 1.4 branch by a while back. Are you running into the same issue with 1.5?\nI think I told you the wrong thing earlier. We don't support the misc (/system) cgroup on systemd systems (I can't remember why, but it was an explicit decision - or might know). The is something different, I believe a base systemd cgroup (slice). As for the misc container on ContainerVM nodes, we've been testing for the misc container in 1.5+ in the summary api test (https://k8s-) for a while, and I haven't seen this issue.", "commid": "kubernetes_issue_37453", "tokennum": 538}], "negative_passages": []}
{"query_id": "q-en-kubernetes-af3b62fd3d98e7596533a817bb4d172662e9f3b64841679a414460a8bfe15ef5", "query": "}) matchExpectations := ptrMatchAllFields(gstruct.Fields{ \"Node\": gstruct.MatchAllFields(gstruct.Fields{ <del> \"NodeName\":  Equal(framework.TestContext.NodeName), \"StartTime\": recent(maxStartAge), \"SystemContainers\": gstruct.MatchElements(summaryObjectID, gstruct.IgnoreExtras, gstruct.Elements{ \"kubelet\": sysContExpectations, \"runtime\": sysContExpectations, }), </del> <ins> \"NodeName\":         Equal(framework.TestContext.NodeName), \"StartTime\":        recent(maxStartAge), \"SystemContainers\": gstruct.MatchAllElements(summaryObjectID, systemContainers), </ins> \"CPU\": ptrMatchAllFields(gstruct.Fields{ \"Time\":                 recent(maxStatsAge), \"UsageNanoCores\":       bounded(100E3, 2E9),", "positive_passages": [{"docid": "doc-en-kubernetes-c190eb06e0eb058949f528f1af5886fe17cab35cd1b33a69ea2cddc6a3fc8812", "text": "So if this is still reproducible, it's limited to 1.4. See this the bug was created for the post-fix.\nFound the explanation here: The should use the flag to know the location that has the processes that are associated with , but it should not modify the cgroups of existing processes on the system during bootstrapping of the node. This is because is the on the host and it has not delegated authority to the to change how it manages .\nIIUC this is intended behavior on systemd nodes. Based on the explanation provided, the kubelet doesnt have the authority to control \"misc\" processes on systemd.\n+1. \"misc\" is just a bandaid for cvm. , David Ashpole <:\nOk, so I'm closing this issue.", "commid": "kubernetes_issue_37453", "tokennum": 168}], "negative_passages": []}
{"query_id": "q-en-kubernetes-af4cfab2b32b0c92f8a245912327bde3c68d070cd4d7f585f1cfde5048b071a9", "query": "\"errors\" \"testing\" <del> \"k8s.io/api/core/v1\" </del> <ins> v1 \"k8s.io/api/core/v1\" </ins> \"k8s.io/apimachinery/pkg/types\" \"k8s.io/kubernetes/pkg/volume\" volumetest \"k8s.io/kubernetes/pkg/volume/testing\"", "positive_passages": [{"docid": "doc-en-kubernetes-e1df151812a738ca8d7e9f97519d671c643638f3ca9d9400cc430f5f7a7d204c", "text": "When user creates a static PV using folder name in path: on vSAN backed datastore then detach disk does not work because check fails - The code expects folder name to be UUID but it does not and hence it determines disk is not attached to the node and hence no detach is ever performed. /sig storage cc", "commid": "kubernetes_issue_95121", "tokennum": 68}], "negative_passages": []}
{"query_id": "q-en-kubernetes-af532b0662b3fb32cd8400ce4524f4bfbf5ac5caf8455958531f029eddce26bd", "query": "\"//staging/src/k8s.io/apimachinery/pkg/apis/meta/v1:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/util/net:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/util/runtime:go_default_library\", <ins> \"//staging/src/k8s.io/apimachinery/pkg/util/sets:go_default_library\", </ins> \"//staging/src/k8s.io/apimachinery/pkg/util/wait:go_default_library\", \"//staging/src/k8s.io/client-go/kubernetes/typed/core/v1:go_default_library\", \"//staging/src/k8s.io/client-go/tools/record:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-8c9ebf4e41021efd0692132f5b2f5e7ec08451127a302fc405c42cb972b9ed2e", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: I created several Workloads which require up to ten ports for both UDP and TCP protocol. Now my logs get spammed with . What you expected to happen: should consider -combination instead of only . How to reproduce it (as minimally and precisely as possible): Deploy any service with a node-port with both protocols, e.g.: Anything else we need to know?: This was already acknowledged by here: However, as this thread addresses a different bug and seems kind of stuck, i'd like to suggest that this might be addressed in a new context. Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Deployed via Rancher v2.4.3\n/sig api-machinery\n/remove-sig api-machinery /sig network\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nHow did you get into this situation? The allocator should not have granted the same node port twice?\nOh right, that issue. The only real way out is to de-allocate the NodePorts and then re-allocate them, I think\nAs this happens for all of my ports in the said Production Application (the one where my log gets spammed) as well as complete fresh installation (where i verified the bug), i think there's no \"way out\" except fixing the bug. As said, for me it's necessary to assign both protocols to the same port. This might be a niche-use-case, but checking the it's actually very likely for ports to allow tcp AND udp. I'm not sure about the history of this, but it might be that issue was the origin, which was adressed in PR (\"Allow services which use same port, different protocol to use the same nodePort for both\"). But this PR doesn't contain the adjustment of the said , so still considers the behaviour as invalid, while it's actually allowed and supported.", "commid": "kubernetes_issue_91404", "tokennum": 498}], "negative_passages": []}
{"query_id": "q-en-kubernetes-af532b0662b3fb32cd8400ce4524f4bfbf5ac5caf8455958531f029eddce26bd", "query": "\"//staging/src/k8s.io/apimachinery/pkg/apis/meta/v1:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/util/net:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/util/runtime:go_default_library\", <ins> \"//staging/src/k8s.io/apimachinery/pkg/util/sets:go_default_library\", </ins> \"//staging/src/k8s.io/apimachinery/pkg/util/wait:go_default_library\", \"//staging/src/k8s.io/client-go/kubernetes/typed/core/v1:go_default_library\", \"//staging/src/k8s.io/client-go/tools/record:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-33f53ed726ab1a89c68c77aae3b932484545b038842bda14047a639f615b725d", "text": "/assign\nAhh, I thought you meant that you had accidentally been allocated the same nodePorts and I was very confused when you said \"all of them\". I have reproduced this issue, and I can see it by inspection. The obvious fix would be to collect ports split by protocol, but I think that's not right since we don't store it split. An even simpler fix would be for to build a . Then for each protocol, for each port, build that contains all the port numbers, but remove any duplicates ONLY IF they are duplicated across protocols. Duplicates in the same protocol should be retained (to report an error later). I don't have time to tackle this tonight (and write a test), but it seems like a good bug.\nperhaps I can fix this problem /assign\nthings may be a little more complicated. Right now the is not aware of the protocol of the port so I guess simply rewriting function to return is not enough, the port allocator will still return on same node port even with different protocol. perhaps we need to refactor the to make it protocol-aware.\nI don't think we need to do make the allocator be protocol aware. IIRC we allow you to use the same nodeport on different protocols ONLY within a single service. This means (I think) that we can do hyper-local deduplication as we collect the nodeports for each service. If we find the same nodeport number with different protocols, just remove the duplicates because it is allowed. I.e. a service that looks like: return - deduped. if ANY OTHER service tried to use it would be an error at the \"rebuilt\" allocator Likewise if a single Service claims to use the same nodeport number more than once on the same protocol, it should be an error: return - NOT deduped.\nobviously, we want a great unit test here :P\nah got it! thanks for your detailed explanation!\nHi! I have filed a PR to resolve this issue, could you take a look?", "commid": "kubernetes_issue_91404", "tokennum": 428}], "negative_passages": []}
{"query_id": "q-en-kubernetes-af6730683f59e2fa9fd479326c29671f1818d3e9b51615ec8493d326a0bb38e2", "query": "// Allow users to update labels and capacity oldMinion.Labels = minion.Labels oldMinion.Spec.Capacity = minion.Spec.Capacity <ins> // Clear status oldMinion.Status = minion.Status </ins> if !reflect.DeepEqual(oldMinion, minion) { glog.V(4).Infof(\"Update failed validation %#v vs %#v\", oldMinion, minion)", "positive_passages": [{"docid": "doc-en-kubernetes-88a6665f471219ba222a644b43576808b71f5f4fb39e5a18e0bc0e94ac9cb36e", "text": "Two problems: on node do not have namepace, but kubectl requires namespace. However, if explicitly set namespace to 'default', this will cause an error because we are updating not allowed field (only label update is allowed). is usually created by node controller, update node label with a file is tedious since user needs to create a file with id, resource.capacity, etc. can we make it easier?\nIt would make more sense to have a special global namespace than no namespace. We should make it easy in kubectl to update a single field or subset of fields, generally, for all objects. What this would do is GET, merge, and PUT.\nI had a discussion with on IRC about namespace on node. We'd like to just use \"\" (empty string) as of now. As we are not supporting any namespace feature on node, it's less confusing if we can hide the concept for now. Thinking a little more, \"\" is the special global namespace. I'm going to update kubectl to not assume 'default' namespace on every resources. It works fine for pod, service, but not for node, external LB, etc.\nThere was some discussion about \"\" being (essentially) an alias to \"default\": is that dead? , Deyuan Deng wrote:\nI've seen two versions of NamespaceALL (\"\") NamespaceAll is the default argument to specify on a context when you want to list or filter resources across An empty namespace is equivalent to the , but \"default\" is the canonical representation. Either means , or the definition conflicts - all namespace should include \"default\" namespace. Also, for things like Node, I'd really like a NamespaceNone.\n- I think there is a confusion here because of a poor naming choice. is a constant intended to be used as a filter to LIST/WATCH across multiple namespaces. It is NOT intended to be the value that is set on a resource for persistence. The discussion was to update to which I think is still a good thing to do. I have held off doing that until after we embed the namespace as a path parameter in our URLs instead of a query parameter, which I plan to look at after the holidays. is a constant intended to be used as the namespace context of a request when it's not explicitly stated on a request URL.", "commid": "kubernetes_issue_2548", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-af6730683f59e2fa9fd479326c29671f1818d3e9b51615ec8493d326a0bb38e2", "query": "// Allow users to update labels and capacity oldMinion.Labels = minion.Labels oldMinion.Spec.Capacity = minion.Spec.Capacity <ins> // Clear status oldMinion.Status = minion.Status </ins> if !reflect.DeepEqual(oldMinion, minion) { glog.V(4).Infof(\"Update failed validation %#v vs %#v\", oldMinion, minion)", "positive_passages": [{"docid": "doc-en-kubernetes-5a4d1d083bc5e635544966baa95a7511fe688574aded9d8644d8c7753070f0a1", "text": "Since create operations pull the namespace from the context during persistence, it is also the value intended to be persisted. This is referring to a request URL that does not specify a namespace. It is not referring to the persisted value in the database directly - although that is the value that gets pulled. I think a is a good thing to add AFTER we make the change to specify namespace as a path parameter instead of a query parameter, and we update/rename to something that clarifies that its a wild-card filter whose value is probably best represented as.\nok, sounds good. Thanks. Look forward to see api.NamespaceAll = \"*\" and api.NamespaceNone :)", "commid": "kubernetes_issue_2548", "tokennum": 145}], "negative_passages": []}
{"query_id": "q-en-kubernetes-af834d5c180ecc69b93c544a7c56c86afc3fe516611b0febb2047c576abd15a4", "query": "// EnvVarSource represents a source for the value of an EnvVar. // Only one of its fields may be set. type EnvVarSource struct { <del> // Selects a field of the pod: supports metadata.name, metadata.namespace, metadata.labels, metadata.annotations, </del> <ins> // Selects a field of the pod: supports metadata.name, metadata.namespace, `metadata.labels['<KEY>']`, `metadata.annotations['<KEY>']`, </ins> // metadata.uid, spec.nodeName, spec.serviceAccountName, status.hostIP, status.podIP, status.podIPs. // +optional FieldRef *ObjectFieldSelector", "positive_passages": [{"docid": "doc-en-kubernetes-5018642be16ab87784521fef6d356d625aa306ba1fff6efc2d4048e42ef1a94c", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: When I tried to create a pod with env variables referencing to annotations: What you expected to happen: Should Proceed. As in It stated is a valid option How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.18.2 Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig docs\nThe API docs need to be updated to indicate the correct supported values. See for correct values\nYou are a lifesaver. Thank you!\n/assign I can try to update the api documentation", "commid": "kubernetes_issue_91165", "tokennum": 215}], "negative_passages": []}
{"query_id": "q-en-kubernetes-af9ef1c826fc273fe35b122a506870595c92531ee8f1d699fc9d868c426fd27d", "query": "{% if grains['os_family'] == 'RedHat' -%} {% set daemon_args = \"\" -%} {% endif -%} <del> {% if grains.etcd_servers is defined -%} {% set etcd_servers = \"-etcd_servers=http://\" + grains.etcd_servers + \":4001\" -%} </del> <ins> {% if grains.api_servers is defined -%} {% set api_servers = \"-master=http://\" + grains.api_servers + \":7080\" -%} </ins> {% else -%} {% set ips = salt['mine.get']('roles:kubernetes-master', 'network.ip_addrs', 'grain').values() -%} <del> {% set etcd_servers = \"-etcd_servers=http://\" + ips[0][0] + \":4001\" -%} </del> <ins> {% set api_servers = \"-master=http://\" + ips[0][0] + \":7080\" -%} </ins> {% endif -%} <del> DAEMON_ARGS=\"{{daemon_args}} {{etcd_servers}}\" </del> <ins> DAEMON_ARGS=\"{{daemon_args}} {{api_servers}}\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-8f6e6c1f685c98cc169477efadd1a12031a77645ead6fa9fa244a9ca04430443", "text": "is sent as a fix. cc It's a test failure reported by the publishing robot.\nThe line it fails at:\nIt looks like a vendor copy vs gopath copy issue.\nOne possible fix is removing from the vendor/ directory. I'm testing locally.\nConfirmed removing from the vendor/ directory fixed the test in robot.\nWe need to add the \"issue filer\" feature to the publishing robot, we can't rely on to report robot issues everytime :P I'm just not sure how long the publishing robot will be needed (i.e., when we will get rid of the staging/ directory) so not sure whether we should invest more time on the robot.", "commid": "kubernetes_issue_45693", "tokennum": 141}], "negative_passages": []}
{"query_id": "q-en-kubernetes-afb8259b72328e33b04ceb5df41ec289c627dc4f135cbc191e848845e9f32bfd", "query": "func (s *gcepdSource) createVolume(f *framework.Framework) volInfo { var err error <del> framework.Logf(\"Creating GCE PD volume\") s.diskName, err = framework.CreatePDWithRetry() framework.ExpectNoError(err, \"Error creating PD\") </del> <ins> framework.Logf(\"Creating GCE PD volume via dynamic provisioning\") testCase := storageClassTest{ name:      \"subpath\", claimSize: \"2G\", } pvc := newClaim(testCase, f.Namespace.Name, \"subpath\") s.pvc, err = framework.CreatePVC(f.ClientSet, f.Namespace.Name, pvc) framework.ExpectNoError(err, \"Error creating PVC\") </ins> return volInfo{ source: &v1.VolumeSource{ <del> GCEPersistentDisk: &v1.GCEPersistentDiskVolumeSource{PDName: s.diskName}, </del> <ins> PersistentVolumeClaim: &v1.PersistentVolumeClaimVolumeSource{ ClaimName: s.pvc.Name, }, </ins> }, } } func (s *gcepdSource) cleanupVolume(f *framework.Framework) { <del> if s.diskName != \"\" { err := framework.DeletePDWithRetry(s.diskName) framework.ExpectNoError(err, \"Error deleting PD\") </del> <ins> if s.pvc != nil { err := f.ClientSet.CoreV1().PersistentVolumeClaims(f.Namespace.Name).Delete(s.pvc.Name, nil) framework.ExpectNoError(err, \"Error deleting PVC\") </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-1e6e7a922459aa1ae762d90ee2c0c561e09f7928de6f5ad4ad5cc72934b7dcd1", "text": "New tests for subpath consistently fail in ci-kubernetes-e2e-gce-multizone: https://k8s- /kind bug /sig storage\nIs this a blocker for 1.10?\nI would expect so, yes. /milestone v1.10\nI'm on it /assign\nThe problem is likely due to inline GCE PD volumes not having enough zone information. Considering changing volumes to PVs instead.\nfix was in progress in to change to a PV\n/unassign\n[MILESTONENOTIFIER] Milestone Issue: Up-to-date for process Note: This issue is marked as , and must be updated every 1 day during code freeze. Example update: <details open<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Never automatically move issue out of a release milestone; continually escalate to contributor and SIG through all available channels. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details", "commid": "kubernetes_issue_61101", "tokennum": 262}], "negative_passages": []}
{"query_id": "q-en-kubernetes-afe9e55b9140f7bce692ea94048c746508ae4e52f48ab998bbc16e2edbcc1b9d", "query": "return fmt.Errorf(\"Error building CNI config: %v\", err) } <ins> glog.V(3).Infof(\"Calling cni plugins to add container to network with cni runtime: %+v\", rt) </ins> res, err := plugin.cniConfig.AddNetwork(plugin.netConfig, rt) if err != nil { return fmt.Errorf(\"Error adding container to network: %v\", err)", "positive_passages": [{"docid": "doc-en-kubernetes-3e2b7d9568ee0bf267de4bcdac04137844677bca3ba3f5eceb5026951de8c86d", "text": "Event for a pod: The cni plugins do exist at /opt/cni/bin. They cannot be executed and bash is complaining:\ncc\nI'm guessing this is a shared lib problem, since /usr/grte/v4/lib64/ld-linux-x86- doesn't exist on my gce vm. We should update docs to make it clear how someone would install manually (if they run into such problems again) and statically link (if the problem is indeed the shared lib) with something like Unsure how we'd support different GOOS (vend different tarballs vs checking in and building the plugin inline with our make scripts)\nuggh. These binaries need to be ultra-static or else we need to containerize them.\nEssentially doing would've prevented this bug :)\nAnd see for the CNI_ARGS problems\nalso , re ... however, I'm not too sure if your comment was mean to be on this ticket.\ncc\nI have a working version. I uploaded my cni binary with bug fix on GCS. change source to change sourcehash to Welcome to give it a try.\nAlso see problem:", "commid": "kubernetes_issue_23011", "tokennum": 252}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b0019dfcb90c48519e909538343989684d0d3cd8f5416434641f66d3f8251d2c", "query": "utilruntime.HandleError(fmt.Errorf(\"unable to handle object in %T: %T\", sched, obj)) return } <ins> klog.V(3).Infof(\"delete event for unscheduled pod %s/%s\", pod.Namespace, pod.Name) </ins> if err := sched.SchedulingQueue.Delete(pod); err != nil { utilruntime.HandleError(fmt.Errorf(\"unable to dequeue %T: %v\", obj, err)) }", "positive_passages": [{"docid": "doc-en-kubernetes-671a12759d851f1b99028bc477360c418e1157a45a2e814ff1c5c1cdd09da36a", "text": "This helps debugging scheduler's behavior, currently we don't have logs that indicate when the scheduler first saw a pod or a node. The log level should be v=3. /sig scheduling /cc\nDo you mean add logging for callbacks in ?\nyes, at least for add and delete events\nSure, I can also give this pr, before tomorrow\n/assign\nWe actually have one v=2 log line for a Node being to the cache's tree: But it's probably good to keep this one.", "commid": "kubernetes_issue_87524", "tokennum": 111}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b0378c3ee5a6d0e86d46aa11bd7abab7974794443c33dad3946451bc1c9ad526", "query": "export LD_PRELOAD=/usr/lib/aarch64-linux-gnu/libjemalloc.so.2 fi <ins> # For disabling elasticsearch ruby client sniffering feature. # Because, on k8s, sniffering feature sometimes causes failed to flush buffers error # due to between service name and ip address glitch. # And this should be needed for downstream helm chart configurations # for sniffer_class_name parameter. SIMPLE_SNIFFER=$( gem contents fluent-plugin-elasticsearch | grep elasticsearch_simple_sniffer.rb ) if [ -n \"$SIMPLE_SNIFFER\" ] && [ -f \"$SIMPLE_SNIFFER\" ] ; then FLUENTD_ARGS=\"$FLUENTD_ARGS -r $SIMPLE_SNIFFER\" fi </ins> # Use exec to get the signal # A non-quoted string and add the comment to prevent shellcheck failures on this line. # See https://github.com/koalaman/shellcheck/wiki/SC2086", "positive_passages": [{"docid": "doc-en-kubernetes-d8638ef20bd789f7becbb6da887bf6c67832db9cba785d76d8909f1b2b419007", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Sometimes reported in fluent-plugin-elasticsearch repository for exhausted Elasticsearch cluster issue due to elasticsearch ruby client sniffering issue. This should be fixed with but k/k fluentd-elasticsearch image doesn't use this. Why is this needed: This change should be also applied in the downstream docker images and using helm charts such as\n/sig instrumentation\n/sig cloud-provider\n/assign cosmo0920\nIssues 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\n/remove-lifecycle stale\n/assign\nIssues 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\n/remove-lifecycle stale\nIssues 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\nThe 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]:\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.", "commid": "kubernetes_issue_92852", "tokennum": 469}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b0378c3ee5a6d0e86d46aa11bd7abab7974794443c33dad3946451bc1c9ad526", "query": "export LD_PRELOAD=/usr/lib/aarch64-linux-gnu/libjemalloc.so.2 fi <ins> # For disabling elasticsearch ruby client sniffering feature. # Because, on k8s, sniffering feature sometimes causes failed to flush buffers error # due to between service name and ip address glitch. # And this should be needed for downstream helm chart configurations # for sniffer_class_name parameter. SIMPLE_SNIFFER=$( gem contents fluent-plugin-elasticsearch | grep elasticsearch_simple_sniffer.rb ) if [ -n \"$SIMPLE_SNIFFER\" ] && [ -f \"$SIMPLE_SNIFFER\" ] ; then FLUENTD_ARGS=\"$FLUENTD_ARGS -r $SIMPLE_SNIFFER\" fi </ins> # Use exec to get the signal # A non-quoted string and add the comment to prevent shellcheck failures on this line. # See https://github.com/koalaman/shellcheck/wiki/SC2086", "positive_passages": [{"docid": "doc-en-kubernetes-cfbf31e1193e1637a12fc4a38528199469147183babcacd44c068bee92a1aeb9", "text": "This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_92852", "tokennum": 231}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b058834257fdfff2d31afba364b13ea3f1336bf2c682cca4431de5a882589d08", "query": "\"k8s.io/apimachinery/pkg/runtime/schema\" runtimeserializer \"k8s.io/apimachinery/pkg/runtime/serializer\" utilruntime \"k8s.io/apimachinery/pkg/util/runtime\" <ins> \"k8s.io/apimachinery/pkg/util/sets\" </ins> discoveryendpoint \"k8s.io/apiserver/pkg/endpoints/discovery/aggregated\" genericfeatures \"k8s.io/apiserver/pkg/features\" utilfeature \"k8s.io/apiserver/pkg/util/feature\"", "positive_passages": [{"docid": "doc-en-kubernetes-a36678f387087dd8252401a5249426873ced2ebb26644cae4efea96ce80ca1f6", "text": "reported that conformance testing with the latest version of sonobuoy against a version 1.29.0-alpha.3 cluster fails on the support the 1.17 Sample API Server using the current Aggregator test: , related to I found the reason why the test is working fine in Kubernetes CI jobs but fails with sonobuoy is because the service account used by sonobuoy \"sonobuoy-serviceaccount\" doesn't have read permission of the non-resource url \"/\", which is used by the test to confirm the removal of group path: The permission of \"sonobuoy-serviceaccount\" is as below: There may be two ways to fix it: the RBAC rule of sonobuoy to include \"get\" of \"/\". However, could other test runners encounter this issue? Is there a doc listing the required permissions for running e2e tests? the e2e to skip checking the removal of the group path if the service account doesn't have permission to access the root path. Which way do we usually prefer? Running e2e with sonobuoy should succeed. a v1.29.0-alpha.3 cluster. No response <details</details<details</details<details</details<details</details<details</details<details</details\nimplemented this solution.\n/sig api-machinery\nthank you for opening this issue and working on a solution. I'm probably not the right person to decide on which solution is preferred. From my perspective, either solution is fine.\nNote: Sonobuoy is not owned by any Kubernetes SIG. At most it is between SIG Architecture and the CNCF to choose whether to recommend it for running tests. SIG Testing owns the e2e image that sonobuoy can be used to schedule but not sonobuoy. IMHO this is a bug in running the tests via a pod, which is not how we develop the tests (they're run outside the cluster, by a cluster admin account typically). I would say 1) is the correct answer. xref: /sig architecture /sig testing /triage accepted cc\nthanks for your comment. I guess 1) means non of the existing sonobuoy versions can pass K8s conformance test against a cluster 1.29.0-alpha3, as the RBAC rule is hardcoded.", "commid": "kubernetes_issue_121985", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b058834257fdfff2d31afba364b13ea3f1336bf2c682cca4431de5a882589d08", "query": "\"k8s.io/apimachinery/pkg/runtime/schema\" runtimeserializer \"k8s.io/apimachinery/pkg/runtime/serializer\" utilruntime \"k8s.io/apimachinery/pkg/util/runtime\" <ins> \"k8s.io/apimachinery/pkg/util/sets\" </ins> discoveryendpoint \"k8s.io/apiserver/pkg/endpoints/discovery/aggregated\" genericfeatures \"k8s.io/apiserver/pkg/features\" utilfeature \"k8s.io/apiserver/pkg/util/feature\"", "positive_passages": [{"docid": "doc-en-kubernetes-4545476cbce0605bfe46d5a01c41b8f4cf7b5ac07772bfb1748611bc506e90ef", "text": "I will file an issue to sonobuoy first.\nquestion here is what are the set of client permissions required to run the conformance suite? perhaps a level of access or a more granular recommendation should be documented. what is your take on the root path requirement as approver for: EDIT: slack thread:\nI agree, we already require e.g. privileged pods for a long time in conformance tests and we should make it clear that we expect a highly privileged client.\n+1 for what is saying, that we should expect that the user running the tests has required permissions. These tests are not built for being run unprivileged.\ni wanted to PR the admin note in our conformance docs under sig-arch, but then i saw this: so broke this guarantee. sounds like SIG Arch needs to comment.\nThis statement surprises me. Root discovery is one of the least-privileged permissions you can have on a cluster. For years this was even open for unauthorized users on the internet (if your api endpoint has been exposed). In other words, just add the permission. While thinking about it, it is surprising that the user in question does not have this access already. Don't we allow that for every authorized user?\nIn contrast, I hope that lots of privileged operations are tested by conformance today. If we don't test things like admission webhooks for example, we have much bigger problems. And admission webhooks are basically equivalent to cluster-admin.\nthat is outdated, we use hostNetwork pods one some of the tests IIRC\nlooks like we don't. before this ticket, i was under the impression that the conformance suite already requires admin and that all testers (like Sonobuoy) use admin level credentials. it is non-privileged (e.g., does not require root on nodes, access to raw network interfaces, or cluster admin permissions) looks like we may have to change that sentence completely.\nWould have expected it here: The PR in question explicitly fixes the result returned by . If that is part of conformance (IMO it should), every conformance test needs access it obviously. Whether we require admin, or we add it manually, either would work.", "commid": "kubernetes_issue_121985", "tokennum": 474}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b058834257fdfff2d31afba364b13ea3f1336bf2c682cca4431de5a882589d08", "query": "\"k8s.io/apimachinery/pkg/runtime/schema\" runtimeserializer \"k8s.io/apimachinery/pkg/runtime/serializer\" utilruntime \"k8s.io/apimachinery/pkg/util/runtime\" <ins> \"k8s.io/apimachinery/pkg/util/sets\" </ins> discoveryendpoint \"k8s.io/apiserver/pkg/endpoints/discovery/aggregated\" genericfeatures \"k8s.io/apiserver/pkg/features\" utilfeature \"k8s.io/apiserver/pkg/util/feature\"", "positive_passages": [{"docid": "doc-en-kubernetes-06abc1218304c92779dae2744e33107a4d26263c1c54e4453f3f92a1949c2aa2", "text": "adding to milestone and making release blocking ... we should not release 1.29 in a state that the most commonly used conformance tool will fail\nIMO we should clarify the state and go fix the tool, but we should keep the test and we should NOT add skip. Conformance docs are not a release artifact, and sonobuoy release lifecycle is not a conformance artifact. If we can't get sonobuoy working in a reasonable time, we already know the tests can be run by scheduling the image (which is ours) directly with kubectl instead and we can document that in the upstream conformance docs. We need to fix the for this image: ,%20master%20(dev) And it should probably be to release-blocking in the future.\nit looks like the e2e change made in was not consciously made part of conformance, it was just trying to functionally test the bugfix being made. For 1.29, I think we should revert the change to and make an integration test that validates the fix instead. We can revisit whether content of is part of conformance or not for 1.30\nI opened to revert the e2e change and move the functional test to an integration test\nFiled to try to get the image job passing again.\nWe probably need another issue to track 1.30 follow-up?\nIf no one has done it, I could create another issue and follow up with the items that have been discussed here: outdated privilege requirement in commonly used conformance tools like sonobuoy aware of the required priviledge to avoid similar situations in the future. permission of GET \"/\" to authorized users via the role for root discovery.", "commid": "kubernetes_issue_121985", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b060e774fc054b60240f2008827502a879ebd37112dccdeec191d258e9b216dd", "query": "}) It(\"should provide DNS for the cluster\", func() { <del> if testContext.Provider == \"vagrant\" { </del> <ins> if providerIs(\"vagrant\") { </ins> By(\"Skipping test which is broken for vagrant (See https://github.com/GoogleCloudPlatform/kubernetes/issues/3580)\") return }", "positive_passages": [{"docid": "doc-en-kubernetes-5702d542be386cac9e4333778515fd94620fcdb52c66d8dfc11487da78971dda", "text": "I noticed while running e2e tests locally that some tests were apparently being incorrectly skipped: I checked, and this is also true for our Jenkins runs. Currently it looks like and have this bug, though only the former actually skips the test, I think. The issue appears to be that the code inside the top-level in these files is being run before the testContext struct is filled out (and before is even called), and so testContext.Provider is empty. I'm not immediately sure what the proper fix is; I'm also worried that there might be other things broken by the fact that these blocks are called before initialization is complete. We also probably investigate if there is a better way to mark these tests as skipped; right now, there's no indication in the test report (, Jenkins test report, etc) that these tests were skipped.\nI merged and which tried to disable these tests for non-{gke,gce} but apparently didn't follow-up and verify that they were still running on our platforms. /cc\nSeems easy enough to fix. I'll have a PR out to fix this before Monday.", "commid": "kubernetes_issue_7008", "tokennum": 242}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b0784699441e0d831712725d3c3c37600524519ed561f3ee7acbbb6ebabdf1e1", "query": "}}, }, }, <ins> \"long-port-name\": { expectedErrors: 0, endpointSlice: &discovery.EndpointSlice{ ObjectMeta:  standardMeta, AddressType: addressTypePtr(discovery.AddressTypeIP), Ports: []discovery.EndpointPort{{ Name:     utilpointer.StringPtr(strings.Repeat(\"a\", 63)), Protocol: protocolPtr(api.ProtocolTCP), }}, Endpoints: []discovery.Endpoint{{ Addresses: generateIPAddresses(1), }}, }, }, </ins> \"empty-ports-and-endpoints\": { expectedErrors: 0, endpointSlice: &discovery.EndpointSlice{", "positive_passages": [{"docid": "doc-en-kubernetes-b73bb51cef5016ee2dcd80aae4248808fec811a4dad3a3b7abbba7673a446c48", "text": "What happened: No endpoints created in the EndpointSlice for my service due to the port on the service being too long. Logs show: EndpointSlice created has no endpoint: What you expected to happen: Service that works with Endpoints should work with EndpointSlice. If this is intentional, it should be clearly documented How to reproduce it (as minimally and precisely as possible): Create a service with a long port name Environment: Kubernetes version (use ): 1.16 Cloud provider or hardware configuration: kind\n/sig networking\nThe label(s) cannot be applied. These labels are supported: <detailsIn response to : /sig networking 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\n/sig network These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by vllry. \u200d\nFor a rough measure of impact, Istio had 5 ports that were over this limit (and many more that were right at 15 characters), so I suspect it may not be terribly rare.\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nThis needs to be resolved before endpointslices graduate from alpha\n/assign\n/remove-triage unresolved", "commid": "kubernetes_issue_84388", "tokennum": 292}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b07e5ca3940ab5bb2ddab3cc773f24bc154e7bcd3673df915d8e6214a2d41179", "query": "type makeLocalPodWith func(config *localTestConfig, volume *localTestVolume, nodeName string) *v1.Pod <del> func testPodWithNodeName(config *localTestConfig, testVolType localVolumeType, ep *eventPatterns, nodeName string, makeLocalPodFunc makeLocalPodWith, bindingMode storagev1.VolumeBindingMode) { </del> <ins> func testPodWithNodeConflict(config *localTestConfig, testVolType localVolumeType, nodeName string, makeLocalPodFunc makeLocalPodWith, bindingMode storagev1.VolumeBindingMode) { </ins> By(fmt.Sprintf(\"local-volume-type: %s\", testVolType)) testVols := setupLocalVolumesPVCsPVs(config, testVolType, config.node0, 1, bindingMode) testVol := testVols[0]", "positive_passages": [{"docid": "doc-en-kubernetes-9df8e5ba2e9f919d9bec92d550979c4e420a21d16e91da208714cd0aae742f47", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /assign What happened: The tests are failing again because the scheduler messages have changed yet again. I'm going to remove the check for the exact messages because this is at least the 3rd time this has happened. Instead depend on unit/integration tests to check for specific failures. Also there's no need for these tests to run across all types of local volumes because it's just testing the scheduler part.", "commid": "kubernetes_issue_59369", "tokennum": 123}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b092eba58396030e9812aeb324b8d52c682598419e72b129b5678681a728a629", "query": "for _, epSvcPair := range connectionMap { if svcInfo, ok := proxier.serviceMap[epSvcPair.ServicePortName]; ok && svcInfo.GetProtocol() == v1.ProtocolUDP { endpointIP := utilproxy.IPPart(epSvcPair.Endpoint) <del> err := conntrack.ClearEntriesForNAT(proxier.exec, svcInfo.ClusterIPString(), endpointIP, v1.ProtocolUDP) </del> <ins> nodePort := svcInfo.GetNodePort() var err error if nodePort != 0 { err = conntrack.ClearEntriesForPortNAT(proxier.exec, endpointIP, nodePort, v1.ProtocolUDP) } else { err = conntrack.ClearEntriesForNAT(proxier.exec, svcInfo.ClusterIPString(), endpointIP, v1.ProtocolUDP) } </ins> if err != nil { klog.Errorf(\"Failed to delete %s endpoint connections, error: %v\", epSvcPair.ServicePortName.String(), err) }", "positive_passages": [{"docid": "doc-en-kubernetes-9e39524d0e4c89f1ddf9c516fe4e1c471a25826ee6b222abfe1f6c0cc213064c", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: BUG REPORT What happened: When deleting/recreating pods backing a UDP service, traffic from external senders stops flowing. What you expected to happen: Traffic would continue to flow to new pods. How to reproduce it (as minimally and precisely as possible): Based on reading of similar issues and commit messages it seems like this would be most noticable on high-volume UDP applications, statsd and syslog are good examples. a deployment and service for a UDP app. In my test case, this would be the container. an external node, create a small test script utilizing a statsd library such as pystatsd. The most important part is that the sender uses the same source-port for every packet sent. Ex: the sender. Install tcpdump into the pod and watch for incoming packets, example from the test case: the pod tcpdump in the newly created pod. Observe that no new matching packets are flowing. existing conntrack rules on all nodes in the cluster. You should see traffic start flowing to the pod again. example command for clearing conntrack rules on the nodes: Anything else we need to know?: I have tested this only on GKE-managed clusters that utilize google forwarding-rules for external LBs, but I believe the issue may be present on any platform where iptables mode for kube-proxy is used. Tested and verified on 1.8.6-gke.0 and 1.7.11-gke.1. Also tested with both Google Container-optimized OS and the Ubuntu-based node images. I have only test this on GKE It appears this was a known issue and should have been cleared up by: From my reading of , it seems as if the func should exec() to clear up UDP entries on service endpoint change, but the only place I see that func called is from syncProxyRules(). That func looks complex and possibly like it is only run occasionally and not on service/endpoint changes. Environment: Kubernetes version (use ): (Also tested on 1.7.11-gke.1) Cloud provider or hardware configuration: GKE-managed clusters, google cloud. OS (e.g.", "commid": "kubernetes_issue_59368", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b092eba58396030e9812aeb324b8d52c682598419e72b129b5678681a728a629", "query": "for _, epSvcPair := range connectionMap { if svcInfo, ok := proxier.serviceMap[epSvcPair.ServicePortName]; ok && svcInfo.GetProtocol() == v1.ProtocolUDP { endpointIP := utilproxy.IPPart(epSvcPair.Endpoint) <del> err := conntrack.ClearEntriesForNAT(proxier.exec, svcInfo.ClusterIPString(), endpointIP, v1.ProtocolUDP) </del> <ins> nodePort := svcInfo.GetNodePort() var err error if nodePort != 0 { err = conntrack.ClearEntriesForPortNAT(proxier.exec, endpointIP, nodePort, v1.ProtocolUDP) } else { err = conntrack.ClearEntriesForNAT(proxier.exec, svcInfo.ClusterIPString(), endpointIP, v1.ProtocolUDP) } </ins> if err != nil { klog.Errorf(\"Failed to delete %s endpoint connections, error: %v\", epSvcPair.ServicePortName.String(), err) }", "positive_passages": [{"docid": "doc-en-kubernetes-27a4c6cdabc82c95dde932bb7bf1e1865b5f691c3b3e7bf1ed0c71bfc361fddc", "text": "from /etc/os-release): tried both: and Kernel (e.g. ): and Install tools: Others:\n/sig network\nWe also ran into this in kubernetes v1.7.6 using OpenShift 3.7:\n~I believe this is the same as ~If so, it is fixed in 1.10: These are about HostPort, not NodePort, sorry for the noise.\nIssues 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\nIs there any other known workaround for this besides updating conntrack rules on the kube nodes? I tried deleting and recreating the service, but this didn't update the rules. When I restart the stream on the client side data flows correctly again (perhaps it's perceived as a new connection), but I have to restart the stream for each sender.\n/remove-lifecycle stale\nFWIW, this is not fixed in 1.10 - that fix was for HostPort, and this is still a bug for NodePort.\nI am seeing this issue in 1.11. I am using LoadBalancer type.\nhas been working on a fix for this, FYI.\nThis issue is extremely impactful for telephony protocols that rely on static source ip and source port. Any update on a possible workaround? I was thinking a potential workaround might be to reduce the UDP timeout to something really short so the stale conntrack entries go away faster. Or maybe there is a way to flush conntrack on the event of pod deletion? Edit: Removed stupid idea of a workaround to disable conntrack for UDP. Can't disable conntrack for UDP because it's used for DNAT from node to container.\nThe workaround is to not use NodePorts. Other kinds of services are already correct.\nnot sure what you mean. I am seeing the issue with a LoadBalancer type so it does not affect NodePorts only. As a workaround I have created a small python script that watches the K8s API for pod deletions and clears the related conntrack entries when that happens. I can share it when I get to work on Monday if you want to try it out.", "commid": "kubernetes_issue_59368", "tokennum": 535}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b092eba58396030e9812aeb324b8d52c682598419e72b129b5678681a728a629", "query": "for _, epSvcPair := range connectionMap { if svcInfo, ok := proxier.serviceMap[epSvcPair.ServicePortName]; ok && svcInfo.GetProtocol() == v1.ProtocolUDP { endpointIP := utilproxy.IPPart(epSvcPair.Endpoint) <del> err := conntrack.ClearEntriesForNAT(proxier.exec, svcInfo.ClusterIPString(), endpointIP, v1.ProtocolUDP) </del> <ins> nodePort := svcInfo.GetNodePort() var err error if nodePort != 0 { err = conntrack.ClearEntriesForPortNAT(proxier.exec, endpointIP, nodePort, v1.ProtocolUDP) } else { err = conntrack.ClearEntriesForNAT(proxier.exec, svcInfo.ClusterIPString(), endpointIP, v1.ProtocolUDP) } </ins> if err != nil { klog.Errorf(\"Failed to delete %s endpoint connections, error: %v\", epSvcPair.ServicePortName.String(), err) }", "positive_passages": [{"docid": "doc-en-kubernetes-956c9b1270ab4e0eb744fb5e7c207e8e7b7c0a49e83c634550198bfe9b333eeb", "text": "I've my script . Note that it's not tested much so don't use it in a production environment. Also it cleans up all conntrack entries for a deleted pod, not only the UDP related ones.\nWe are also seeing this issue with type loadbalancer. We are on 1.11. Our use-case is the following: multiple devices are sending to an aggreagator machine. This machine forwards the UDP packages to a loadBalancer in gcp. When debugging the service, I noticed the following: The traffic is assigned to one pod, and the packages are not loadbalanced (client and server are the same cfr use-case) When redeploying a new cluster, Conntrack is cleared on termination signal of the old pod. (client receives connection refused) red/black and highlander deployment strategies have the same effect. How would I expect this to be working then? New cluster is . Conntrack is cleared Data is routed to NEW pods old pods are terminated Best Regards, Tim\nI am seeing this exact same issue on our cluster which has k8s v1.14.5 . We have endpoint nginx pods backing a UDP service with nodeport. Suddenly one day we see traffic not hitting into nginx pod but reaching the node hosting the nginx pod. We could simulate the problem by restarting the nginx pods. I am assuming with this issue marked as closed; and having made its way into v1.14; we should not be seeing this. Would also like to point out; the one thing, in addition we have in the service is ExternalTrafficPolicy set to Local. Can anyone please guide/help on why we are seeing this in v.1.14.5 of our cluster.\nSeeing this with k8s v1.16.5", "commid": "kubernetes_issue_59368", "tokennum": 391}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b095a0afff45990e8f234ec587e225bf110f1384a5819421d701ff0cf760260e", "query": "AttachDisk(isManagedDisk bool, diskName, diskURI string, nodeName types.NodeName, lun int32, cachingMode compute.CachingTypes) error // DetachDiskByName detaches a vhd from host. The vhd can be identified by diskName or diskURI. DetachDiskByName(diskName, diskURI string, nodeName types.NodeName) error <del> // GetDiskLun finds the lun on the host that the vhd is attached to, given a vhd's diskName and diskURI. GetDiskLun(diskName, diskURI string, nodeName types.NodeName) (int32, error) // GetNextDiskLun searches all vhd attachment on the host and find unused lun. Return -1 if all luns are used. GetNextDiskLun(nodeName types.NodeName) (int32, error) // DisksAreAttached checks if a list of volumes are attached to the node with the specified NodeName. DisksAreAttached(diskNames []string, nodeName types.NodeName) (map[string]bool, error) </del> <ins> // GetDataDisks gets a list of data disks attached to the node. GetDataDisks(nodeName types.NodeName) ([]compute.DataDisk, error) </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-6cfc50824280daf2f66f5e84f9a8c720c316cfa724f1e90fa02f306c798e5010", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind cleanup What happened: VirtualMachineScaleSetVM and VirtualMachine are different data structures (because of different API versions), so the disk attach operation seems duplicate between vm and vmss. That means although disk operations are in same logic, some duplication are still required now. They should use same api version in the future and should be merged into same code base, e.g. move sharing logic to Refer What you expected to happen: vmss and vm disk operations should share same code logic. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\nI have checked with currently we can\u2019t merge, e.g. following two structs are different since they using different sdk-for-azure versions. While in the end when sdk-for-azure version is upgraded, above two versions should be same and at that time, we should merge functions like \u2018AttachDisk\u2019, \u2018DetachDiskByName\u2019, 'GetDiskLun', GetNextDiskLun, DisksAreAttached", "commid": "kubernetes_issue_59736", "tokennum": 313}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b0c8f979e4d60c5e47e00efaa3ec09e72784c345754abece910d3a4f69b56888", "query": "} var clientBuilder controller.ControllerClientBuilder if s.UseServiceAccountCredentials { <del> if len(s.ServiceAccountKeyFile) > 0 { </del> <ins> if len(s.ServiceAccountKeyFile) == 0 { </ins> // It's possible another controller process is creating the tokens for us. // If one isn't, we'll timeout and exit when our client builder is unable to create the tokens. glog.Warningf(\"--use-service-account-credentials was specified without providing a --service-account-private-key-file\")", "positive_passages": [{"docid": "doc-en-kubernetes-dec167f232fc78679b57ee7f7f6400be17dd5e43f5f10aa50473841ecfd59319", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: During startup shows the following warning: However is set and refers to a valid X.509 private key file. All service accounts seem to be created despite the warning. How to reproduce it (as minimally and precisely as possible): start controller-manager with Anything else we need to know?: Environment: Kubernetes version (use ): v1.8.0 OS (e.g. from /etc/os-release): Debian GNU/Linux 8 (jessie)\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\nThanks for the report. The condition for printing the warning is backwards, but has no effect on behavior. Fixed in\nStill present in 1.8.3 , can it be ~backported~ cherry-picked to 1.8 branch please?\nSee for proposed cherry-pick", "commid": "kubernetes_issue_53291", "tokennum": 270}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b14c79c69d6b75679a30291cd1bc78be989e200ace076e3df42bd4f0ade82723", "query": "<del> /* Copyright 2016 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package storage import ( \"context\" \"fmt\" \"os/exec\" v1 \"k8s.io/api/core/v1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/util/uuid\" \"k8s.io/kubernetes/test/e2e/framework\" e2eoutput \"k8s.io/kubernetes/test/e2e/framework/pod/output\" e2eskipper \"k8s.io/kubernetes/test/e2e/framework/skipper\" \"k8s.io/kubernetes/test/e2e/storage/utils\" admissionapi \"k8s.io/pod-security-admission/api\" \"github.com/onsi/ginkgo/v2\" ) var _ = utils.SIGDescribe(\"GKE local SSD [Feature:GKELocalSSD]\", func() { f := framework.NewDefaultFramework(\"localssd\") f.NamespacePodSecurityEnforceLevel = admissionapi.LevelPrivileged ginkgo.BeforeEach(func() { e2eskipper.SkipUnlessProviderIs(\"gke\") }) ginkgo.It(\"should write and read from node local SSD [Feature:GKELocalSSD]\", func(ctx context.Context) { framework.Logf(\"Start local SSD test\") createNodePoolWithLocalSsds(\"np-ssd\") doTestWriteAndReadToLocalSsd(ctx, f) }) }) func createNodePoolWithLocalSsds(nodePoolName string) { framework.Logf(\"Create node pool: %s with local SSDs in cluster: %s \", nodePoolName, framework.TestContext.CloudConfig.Cluster) out, err := exec.Command(\"gcloud\", \"alpha\", \"container\", \"node-pools\", \"create\", nodePoolName, fmt.Sprintf(\"--cluster=%s\", framework.TestContext.CloudConfig.Cluster), \"--local-ssd-count=1\").CombinedOutput() if err != nil { framework.Failf(\"Failed to create node pool %s: Err: %vn%v\", nodePoolName, err, string(out)) } framework.Logf(\"Successfully created node pool %s:n%v\", nodePoolName, string(out)) } func doTestWriteAndReadToLocalSsd(ctx context.Context, f *framework.Framework) { var pod = testPodWithSsd(\"echo 'hello world' > /mnt/disks/ssd0/data  && sleep 1 && cat /mnt/disks/ssd0/data\") var msg string var out = []string{\"hello world\"} e2eoutput.TestContainerOutput(ctx, f, msg, pod, 0, out) } func testPodWithSsd(command string) *v1.Pod { containerName := \"test-container\" volumeName := \"test-ssd-volume\" path := \"/mnt/disks/ssd0\" podName := \"pod-\" + string(uuid.NewUUID()) image := \"ubuntu:14.04\" return &v1.Pod{ TypeMeta: metav1.TypeMeta{ Kind:       \"Pod\", APIVersion: \"v1\", }, ObjectMeta: metav1.ObjectMeta{ Name: podName, }, Spec: v1.PodSpec{ Containers: []v1.Container{ { Name:    containerName, Image:   image, Command: []string{\"/bin/sh\"}, Args:    []string{\"-c\", command}, VolumeMounts: []v1.VolumeMount{ { Name:      volumeName, MountPath: path, }, }, }, }, RestartPolicy: v1.RestartPolicyNever, Volumes: []v1.Volume{ { Name: volumeName, VolumeSource: v1.VolumeSource{ HostPath: &v1.HostPathVolumeSource{ Path: path, }, }, }, }, NodeSelector: map[string]string{\"cloud.google.com/gke-local-ssd\": \"true\"}, }, } } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-a416b49d9932f64618fc25d3906fc3f29787f4b2fe9d0ffb0b804ce600654c09", "text": "Following up on , evaluate if the test for local SSD on GKE clusters is still necessary (it is also tested internally in Google). /assign\n/sig storage\n/triage accepted\nIssues 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\n/lifecycle frozen\nThis 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\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThis test should be removed as it's using a GKE feature that, while not deprecated, is discouraged in favor of newer APIs. Those APIs are well-tested internally in google, and I don't see value in additional toil upstream to maintain them.", "commid": "kubernetes_issue_99383", "tokennum": 304}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b1726454ab0174d38ae79e711cae6773df9788078fb5823bf4c48e15ccae8e42", "query": "// Start the reconciler to fill ASW. stopChan, stoppedChan := make(chan struct{}), make(chan struct{}) go func() { <ins> defer close(stoppedChan) </ins> reconciler.Run(stopChan) <del> close(stoppedChan) </del> }() waitForMount(t, fakePlugin, volumeName, asw) // Stop the reconciler.", "positive_passages": [{"docid": "doc-en-kubernetes-d047193f0eb4348dad25266c8f06cc7d0100df3011e6281006c74e70d78d442e", "text": "<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI --pull-kubernetes-unit : (PR with no go code changes, should not have failed any unit tests) links to appreciated links to specific failures in spyglass appreciated <!-- Please see the deflaking doc () for more guidance! --/sig storage\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assigne\n/assign\n/assign tried to fix it in", "commid": "kubernetes_issue_99815", "tokennum": 196}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b1d10e4053e9733a53f106d8bd0015f9cd9c27f4b5dee34a4564fd3bca9aa48c", "query": "t.Errorf(\"Expected %v, got %v\", e, a) } } <ins> func TestCacheParallelNoDeadlocksNoDoubleCalls(t *testing.T) { // Make 50 random keys keys := []string{} fuzz.New().NilChance(0).NumElements(50, 50).Fuzz(&keys) // Data structure for tracking when each key is accessed. type callTrack struct { sync.Mutex accessTimes []time.Time } calls := map[string]*callTrack{} for _, k := range keys { calls[k] = &callTrack{} } // This is called to fill the cache in the case of a cache miss // or cache entry expiration. We record the time. ff := func(key string) T { ct := calls[key] ct.Lock() ct.accessTimes = append(ct.accessTimes, time.Now()) ct.Unlock() // make sure that there is time for multiple requests to come in // for the same key before this returns. time.Sleep(time.Millisecond) return key } cacheDur := 10 * time.Millisecond c := NewTimeCache(RealClock{}, cacheDur, ff) // Spawn a bunch of goroutines, each of which sequentially requests // 500 random keys from the cache. runtime.GOMAXPROCS(16) var wg sync.WaitGroup for i := 0; i < 500; i++ { wg.Add(1) go func(seed int64) { r := rand.New(rand.NewSource(seed)) for i := 0; i < 500; i++ { c.Get(keys[r.Intn(len(keys))]) } wg.Done() }(rand.Int63()) } wg.Wait() // Since the cache should hold things for 10ms, no calls for a given key // should be more closely spaced than that. for k, ct := range calls { if len(ct.accessTimes) < 2 { continue } cur := ct.accessTimes[0] for i := 1; i < len(ct.accessTimes); i++ { next := ct.accessTimes[i] if next.Sub(cur) < cacheDur { t.Errorf(\"%v was called at %v and %v\", k, cur, next) } cur = next } } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-0882877f8aa87dd9f2fab7aa6c2163d630c073e98d0481f7c1762728faaae3b6", "text": "Failed due to an apparently unrelated PR: https://travis-\nProblem here is that I left a small chance of a double-call in my parallelized cache. Didn't realize this was being tested. Will fix.", "commid": "kubernetes_issue_3439", "tokennum": 46}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b1d8c8b86a03b578fab8704f22e72e5e1e8db20798883cb5cb70578830bf6913", "query": "} } <ins> func TestWithMaxWaitRateLimiter(t *testing.T) { limiter := NewWithMaxWaitRateLimiter(DefaultControllerRateLimiter(), 500*time.Second) for i := 0; i < 100; i++ { if e, a := 5*time.Millisecond, limiter.When(i); e != a { t.Errorf(\"expected %v, got %v\", e, a) } } for i := 100; i < 5100; i++ { if e, a := 500*time.Second, limiter.When(i); e < a { t.Errorf(\"expected %v, got %v\", e, a) } } for i := 5100; i < 5200; i++ { if e, a := 500*time.Second, limiter.When(i); e != a { t.Errorf(\"expected %v, got %v\", e, a) } } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-6758a4fd9fc03e20cf227e8e04e978c36b819698b12d653642006e59891b2248", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --Currently when using it adds as one of the limiters. This does not work as intended because there is no immediate sleep following the call to the limiter as seen in which does work correctly. The issue with the in its current usage is there is no forget nor a sleep immediately following the call so if is called thousands of times in a row, the timeout grows very quickly with no max. For example, if a clusters has 10k secrets and those are all enqueued using the the will end up with a 16 min wait before the tail end of objects can be enqueued and processed. I would expect some max backoff to take affect. This can be seen at\n/sig api-machinery\n/cc /triage accepted\nit possible to set maxWaitingTime for BucketRateLimiter? when r.Limiter.Reserve().Delay() maxWaitingTime, the return of BucketRateLimiter When() is maxWaitingTime. defined is 1000ms / r.limit * MAXQPS(5000) this issue example (r.tokens = 100, r.limit = 10), if call When() times, the tail end of the object is enqueued waiting for 8.33 min. i'm not sure how to set the value of MAXQPS please help review it\nThe fix merged to close this issue does not fix the underlying issue with the DefaultControllerRateLimiter. The bucket is not being used correctly so this does not work as intended, please read my issue description again as to what is actually happening.\nis another fix needed to solve this issue?\nA token bucket rate limiter will only refill at the defined rate. If enough requeues are , it will take a long time for the refill rate to clear the queue. If a max wait is introduced, then requeues will be inserted into the queue faster than the refill rate of the token bucket rate limiter. A max wait will violate the token bucket rate limiter and we want token bucket rate limiting behavior.", "commid": "kubernetes_issue_104554", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b1db02b61e8d89817b1d7abae9a21785cabcf8f9963e922bbde26ac5d8a09bde", "query": "inferredHost = host } // Make a copy to avoid polluting the provided config <del> tlsConfigCopy, _ := utilnet.TLSClientConfig(transport) </del> <ins> tlsConfigCopy := utilnet.CloneTLSConfig(tlsConfig) </ins> tlsConfigCopy.ServerName = inferredHost tlsConfig = tlsConfigCopy }", "positive_passages": [{"docid": "doc-en-kubernetes-01f8727bc339d7af9aee90f0167a90af1aad001fdd8330c2abd8f77d4ae97abe", "text": "When the master dials nodes, it is mutating the tlsConfig held by the master kubelet client, to add a server name. That means if two different nodes are dialed from a master started with , x509 verification will fail for the second one. Introduced in\nthis is a regression from 1.3 and breaks pod logs/exec/attach and node proxying on installations that use\nWe probably need to review that PR and look to see if any other deliberate copies were flagged incorrectly by govet.\nInstallations that depend on secure trust from externally provided kubelet server certs are the highest security rings. If we don't fix this we need to tell anyone using this flag not to upgrade until we release 1.4.1.\nthe rest of the changes in the govet cleanup PR looked fine to me. fix for this issue is in\nSince we are telling folks they have to upgrade to kubectl 1.4.0 for rollingupdate to work it would definitely be a confusing message to say other folks should not upgrade to 1.4.0 at all.\nIf the fix is merged into master by this afternoon, lets discuss whether or not we should cherrypick it - e.g. risks involved, how we can manually qa to verify nothing else was broken, etc.\nRisk involved: If you are using a secure cluster (defined as ensuring no one can MITM your nodes and masters) and you upgrade to 1.4.0 and it does not include this fix - you are broken.\nWhat is the likelihood of interactions with other code? Is it possible this fix could introduce a breaking change to something else? Has the fix been manually verified? Are we confident that this will fully fixes the issue (vs other edge cases exist for secure clusters that this doesn't catch). Ideally I would like to see this cherrypicked into 1.4 this evening and then cut a new beta that includes it.\nNone. The single line that is currently broken was changed. The rest is a new function (with no side effects), and tests. No, it restores the original intent of the TLS config copy, and tests cover the cases we are using this with (secure, insecure, custom dialer) Yes. I swept for the same issue elsewhere and didn't find any issues. We test with a fully secured master-kubelet setup in Openshift and got a clean test run with this fix applied.\nSGTM. Thanks for fixing this.", "commid": "kubernetes_issue_33140", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b1fae174b76ce4c683dae9b8792f2f4ce5bb1a2a1ace8eb83b0ed8c441bbcff9", "query": "migrated := getMigratedStatusBySpec(volumeToDetach.VolumeSpec) if err != nil { <del> // On failure, add volume back to ReportAsAttached list actualStateOfWorld.AddVolumeToReportAsAttached( logger, volumeToDetach.VolumeName, volumeToDetach.NodeName) </del> <ins> // On failure, mark the volume as uncertain. Attach() must succeed before adding the volume back // to node status as attached. uncertainError := actualStateOfWorld.MarkVolumeAsUncertain( logger, volumeToDetach.VolumeName, volumeToDetach.VolumeSpec, volumeToDetach.NodeName) if uncertainError != nil { klog.Errorf(\"DetachVolume.MarkVolumeAsUncertain failed to add the volume %q to actual state after detach error: %s\", volumeToDetach.VolumeName, uncertainError) } </ins> eventErr, detailedErr := volumeToDetach.GenerateError(\"DetachVolume.Detach failed\", err) return volumetypes.NewOperationContext(eventErr, detailedErr, migrated) }", "positive_passages": [{"docid": "doc-en-kubernetes-2a1f139ca790a16bd0882043a2e2916760e4c33264d1a31f1254bc354f4822db", "text": "After KCM restart, any Pod that reuses a volume that failed to detach gets stuck ContainerCreating with message: User \"system:node:ip-10-0-243-\" cannot get resource \"volumeattachments\" in API group \"\" at the cluster scope: no relationship found between node 'ip-10-0-243-' and this object See steps to reproduce below, it's quite a complex condition. It happens when a pod is restarted, a CSI driver \"busy\" (i.e. times out) + KCM restarted at a wrong time. Pods start just fine. a Pod that uses an attachable CSI volume. the Pod. Make sure it unmounts successfully, but any fails with a transient error, such as timeout. The external attacher continues to detach the volume at this point. kube-controller-manager (KCM) and start a new one. Wait for any leader election etc - it's important for the new KCM to populate A/D controller with no pod using the detaching volume. Let the A/D controller to observe detach error. a new Pod on the same node that uses the same volume. the CSI driver to detach the volume (i.e. stop injecting any transient errors). At this point: The external attacher succeeds detaching the volume, VolumeAttachment is deleted. The volume is marked as attached in node status (!!!) despite no VolumeAttachment exists. A/D controller does not even try to create a new VolumeAttachment, the volume is marked as attached in its Actual State of World (ASW). Kubelet tries to mount the volume, but WaitForAttach fails with: , basically forever. I created . The script expects that the cluster is created by , because it restarts KCM in the middle. It uses my hacked hostpath CSI driver to inject detach errors. Sources are at / the last commit(s) there. There are two issues that together lead to this situation: fails, , i.e. puts it back to . With the volume in , kubelet may try to mount it, while the external attacher tries to detach it. It is not as bad as it sounds, because kubelet can't read VolumeAttachment with the deletion timestamp and it will not call / of un-attached volume.", "commid": "kubernetes_issue_120571", "tokennum": 509}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b1fae174b76ce4c683dae9b8792f2f4ce5bb1a2a1ace8eb83b0ed8c441bbcff9", "query": "migrated := getMigratedStatusBySpec(volumeToDetach.VolumeSpec) if err != nil { <del> // On failure, add volume back to ReportAsAttached list actualStateOfWorld.AddVolumeToReportAsAttached( logger, volumeToDetach.VolumeName, volumeToDetach.NodeName) </del> <ins> // On failure, mark the volume as uncertain. Attach() must succeed before adding the volume back // to node status as attached. uncertainError := actualStateOfWorld.MarkVolumeAsUncertain( logger, volumeToDetach.VolumeName, volumeToDetach.VolumeSpec, volumeToDetach.NodeName) if uncertainError != nil { klog.Errorf(\"DetachVolume.MarkVolumeAsUncertain failed to add the volume %q to actual state after detach error: %s\", volumeToDetach.VolumeName, uncertainError) } </ins> eventErr, detailedErr := volumeToDetach.GenerateError(\"DetachVolume.Detach failed\", err) return volumetypes.NewOperationContext(eventErr, detailedErr, migrated) }", "positive_passages": [{"docid": "doc-en-kubernetes-86a0f830cda4a62b3e964f9aa561f07fe82e259bc1038677353226e3d67190fe", "text": "KCM starts, all VolumeAttachments that don't have a Pod (that's good), but also (that's probably bad). When the newly started KCM re-tries to detach the volume and gets an error again, it marks the volume as fully attached (same as the previous point) and adds it to . Now the volume is both mounted + attached in ASW and A/D controller actually stops here and waits forever for kubelet to unmount the volume. <detailsToday's k/k master, </details<detailsNone </details<detailsN/A, it's KCM issue. </details<details, but seen in a downstream Kubernetes distro too. </details<details</details<details</details\n/sig storage\n/assign\n/triage accepted\nI have the same problem: Seems restart of Kubelet solves this problem. Kubernetes v1.25.13", "commid": "kubernetes_issue_120571", "tokennum": 208}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b20f43741353c50ba0c5b2b83a9eec2fa46ec04a3384f71fa66fe80c303d7ba8", "query": "// ResourceConfiguration stores per resource configuration. type ResourceConfiguration struct { <del> // resources is a list of kubernetes resources which have to be encrypted. </del> <ins> // resources is a list of kubernetes resources which have to be encrypted. The resource names are derived from `resource` or `resource.group` of the group/version/resource. // eg: pandas.awesome.bears.example is a custom resource with 'group': awesome.bears.example, 'resource': pandas) </ins> Resources []string `json:\"resources\"` // providers is a list of transformers to be used for reading and writing the resources to disk. // eg: aesgcm, aescbc, secretbox, identity.", "positive_passages": [{"docid": "doc-en-kubernetes-0045c1600a60d9073df9d5127e356e4d0c19e0407dd07c166d371541fb200a6a", "text": "Update the godoc on the encryption config API on how to specify group/resources to be encrypted ref: godoc has the details na No response_ na na <details</details<details</details<details</details<details</details\n/sig auth /triage accepted\n/assign Cool-Coder174\nThanks for volunteering for this LMK if you need any help with it.\nJust for clarification, I just need to add documentation on how to configure encryption on groups/resources?\nYou can update godoc to mention that custom resources can now be to the list of to be encrypted as well and how to add the of the resource to the list. e.g. from this test\n/assign /unassign Release v1.26 deadlines are here so we need to get this completed ASAP.\n/milestone v1.26\nI apologize for the slow actions. I know time and contributions are valuable. May I request a walk through. This is my first time ever contributing and I really want to learn. I have been reading some of the code base on my spare time.\nthis feature is on the harder side of things to get started with. Reading the blog post and the associated documentation is probably the best starting point:\n& what is the status on this issue? 1.26 is coming up! cc\n/milestone v1.27", "commid": "kubernetes_issue_113272", "tokennum": 293}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b2315483f73b0271ce6d3f1306f8e334311d13cd1df55181577229a07cabc644", "query": "return err } <del> // Record some output. outputSetLock.Lock() defer outputSetLock.Unlock() outputSet.Insert(key) </del> <ins> // Report this deletion. deletionCounter <- key </ins> } return nil },", "positive_passages": [{"docid": "doc-en-kubernetes-20ba07f969c78351406740c712da4b4d48c539c847c31f97f90729edba71a7c4", "text": "From shippable, I noticed there are several failed cases, for example, E0413 17:34:38. ] watch of *api.Pod ended with: Stop requested --- FAIL: Example (0.61s) got: want: a-hello b-controller c-framework FAIL coverage: 85.9% of statements FAIL 7.652s cc/\nanother example:\nah-- this is a different thing. I will fix this, too.\nI'm seeing this from an unrelated change\nYeah I think that's the one I expected to see.", "commid": "kubernetes_issue_6777", "tokennum": 121}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b23fb8e446770c9ff72af150b463ac2dd265bed967c42413e5c8276a66b8f835", "query": "unversioned.GroupResource{Group: \"\", Resource: \"endpoints\"}:              \"services/endpoints\", unversioned.GroupResource{Group: \"\", Resource: \"nodes\"}:                  \"minions\", unversioned.GroupResource{Group: \"\", Resource: \"services\"}:               \"services/specs\", <ins> unversioned.GroupResource{Group: \"extensions\", Resource: \"ingresses\"}:    \"ingress\", </ins> } func (s *DefaultStorageFactory) ResourcePrefix(groupResource unversioned.GroupResource) string {", "positive_passages": [{"docid": "doc-en-kubernetes-f3221c09c6d59949b8ff055be19bd249df646b41606c69fa43fd98ef3f599715", "text": "On a 1.3.6 master: But on a 1.4 master: Obviously this will cause upgrade issues. ideas? If not I will debug tomorrow.\ndefaults to using the resource name as the etcd prefix, but ingresses was not using the resource name as its prefix. fix in\nreopening until cherry-pick merges\nYikes, good catch. This would have been a disaster. , Jordan Liggitt wrote:\nmerged to release-1.4", "commid": "kubernetes_issue_32255", "tokennum": 99}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b27bc9bb4470d84252cbd63b1b8133f462885f9732d3b581e6ee6438f5d428c1", "query": "annotations: scheduler.alpha.kubernetes.io/critical-pod: '' spec: <del> affinity: podAntiAffinity: preferredDuringSchedulingIgnoredDuringExecution: - weight: 100 podAffinityTerm: labelSelector: matchExpressions: - key: k8s-app operator: In values: [\"kube-dns\"] topologyKey: kubernetes.io/hostname </del> tolerations: - key: \"CriticalAddonsOnly\" operator: \"Exists\"", "positive_passages": [{"docid": "doc-en-kubernetes-87812c2d6cc8421563555995ddc62216ea46df17dcd4476f816c4a4bdf2ab614", "text": "Our 5k-node cluster jobs recently started failing even before the e2e tests start. The reason is the step which checks that all kube-system pods are running is timing out: cc\nFrom the scheduler logs I'm seeing that the pods are being scheduled quite slowly, getting worse with time: 2-3 pods/min looks quite bad. cc\nAlso finding such traces: Seems like most of the time is being spent in priority calculation.\nFrom the pod spec, I'm seeing soft inter-pod anti-affinity at node-level topology: I'm almost sure this is the one causing the mischief. We've been having performance issues with anti-affinity traditionally :p\nOk... PR is the cause. It introduced anti-affinity to kube-dns. I think we should revert this change given known issues with anti-affinity. - Opinions?\nFYI - it is taking 80m until the last pod is scheduled when I'm running 5k-node cluster locally.\nThat's quite unfortunate. It looks like we should revert the change until the anti-affinity change is scalable enough to be used more broadly, unless the scheduler folks have a target fix for this use case.\ncc\nWe are very well aware of the performance issues in our affinity/anti-affinity functions, but I am not aware of a concrete solution at this point. This is partly due to the flexible design of affinity/anti-affinity concept. My humble opinion at this point is to drop some of the flexibility as they are rarely used, in order to streamline the algorithm and improve performance. Anyway, I think the proper solution to this problem needs more time than your requirements to address the issue in hand. So, you may want to change your configuration and drop the anti-affinity rule.\nwould it make sense to add a note to the anti-affinity user documentation to hint at performance problems at large scale, until this is fixed?\nRe-opening this issue as this problem has struck again.", "commid": "kubernetes_issue_54164", "tokennum": 411}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b27bc9bb4470d84252cbd63b1b8133f462885f9732d3b581e6ee6438f5d428c1", "query": "annotations: scheduler.alpha.kubernetes.io/critical-pod: '' spec: <del> affinity: podAntiAffinity: preferredDuringSchedulingIgnoredDuringExecution: - weight: 100 podAffinityTerm: labelSelector: matchExpressions: - key: k8s-app operator: In values: [\"kube-dns\"] topologyKey: kubernetes.io/hostname </del> tolerations: - key: \"CriticalAddonsOnly\" operator: \"Exists\"", "positive_passages": [{"docid": "doc-en-kubernetes-e9d9c7cf78723b98b17d4b4c5d875d12d6958caf3d4df35a73aa6ed31f64de32", "text": "The following runs of our 5k-node scalability jobs failed to bring up the cluster on time: https://k8s- https://k8s- https://k8s- https://k8s- And the reason is kube-dns pods pending to be scheduled for a long time:\nThese failures started happening about 4 days ago and I'm pretty sure it's this one: Add self anti-affinity to kube-dns pods Sadly, we'll have to revert it again for now :( cc - Seems like the improvements to anti-affinity performance made under weren't enough?\nWe need to find other improvements for the predicate. If we cannot find major improvement opportunities, we may have to change its design to be more scalable at the cost of the reducing its flexibility.\n- my personal opinion is that we need to change the design anyway. Having it work both ways (i.e. existing pods everywhere impacting placing of our pod) will always be painful (especially for things like cluster autoscaler)\nI agree. The symetrical application of anti-affinity is problematic. I also think we need to change it.\nGreat. - do you agree with that too?\n, I'm wondering after some affinity/anti-affinity optimization in scheduler, do you think if it's fine to test coreDNS with anti-affinity policy in large cluster with 5000 nodes?\nWe probably should try to see where we are - but this requires testing before enabling that.\nI agree with - Could we first try checking with a benchmark integration test () as a proxy for real cluster test?\nI'm wondering how many real nodes are required for testing?\nSince the integration tests fake out the nodes, I think it's safe to crank it up to 5000 (that's the current largest integration test benchmark size) I'm also hoping to refactor our benchmarks soon, so let me know if you have any thoughts about them.", "commid": "kubernetes_issue_54164", "tokennum": 417}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b2a9e96d731c1c79fdd004eef5a54d2434a980fec2273b6b4b5a919937d4c751", "query": "tags = [\"automanaged\"], visibility = [\"//visibility:public\"], ) <ins> go_test( name = \"go_default_test\", srcs = [\"scheme_test.go\"], importpath = \"k8s.io/kubernetes/pkg/kubelet/apis/kubeletconfig/scheme\", library = \":go_default_library\", deps = [ \"//pkg/kubelet/apis/kubeletconfig/fuzzer:go_default_library\", \"//vendor/k8s.io/apimachinery/pkg/api/testing/roundtrip:go_default_library\", ], ) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-937f1cb17c20e5fd2b4a1f81201690c3dbe6990ef3c1bc74ff71daaa02b6db56", "text": "Solution: I will add one.\n/cc\nxref\nThanks for sending a PR so quickly!\n[MILESTONENOTIFIER] Milestone Issue Needs Attention Action required: During code slush, issues in the milestone should be in progress. If this issue is not being actively worked on, please remove it from the milestone. If it is being worked on, please add the label so it can be tracked with other in-flight issues. Note: If this issue is not resolved or labeled as by Wed, Nov 22 it will be moved out of the v1.9 milestone. <details<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details", "commid": "kubernetes_issue_55959", "tokennum": 230}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b2aa580a992ed71d17921fe616a9cedfb55b0dc8ecc3646aa5b640a32a69023b", "query": ") { if nodeInfo == nil || nodeInfo.Node() == nil { // This may happen during tests. <ins> metrics.EquivalenceCacheWrites.WithLabelValues(\"discarded_bad_node\").Inc() </ins> return } // Skip update if NodeInfo is stale. if !cache.IsUpToDate(nodeInfo) { <ins> metrics.EquivalenceCacheWrites.WithLabelValues(\"discarded_stale\").Inc() </ins> return }", "positive_passages": [{"docid": "doc-en-kubernetes-aa59e6a5adfc1b233e34e0c1fe9e3a0ec7f2fe6a4636f877a41f4c9aef45f71d", "text": "/kind feature The equivalence cache feature is planned to move to beta in 1.11, and it would be useful to have some metrics attached to it. The equivalence cache should improve scheduling throughput, so we want to be able to correlate e.g. throughput with eCache hit rate. /sig scheduling /sig instrumentation\n/assign misterikkit\nIssues 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\n/remove-lifecycle stale", "commid": "kubernetes_issue_63259", "tokennum": 154}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b3623bb1a96a19a770aec1e9c0c28d2a2aee765ef67e8fbe8395456d9d313847", "query": "output_message=$(! kubectl get pods a 2>&1 \"${kube_flags[@]:?}\") kube::test::if_has_string \"${output_message}\" 'pods \"a\" not found' <ins> kubectl delete pods a kubectl delete pods b # apply a kubectl apply --namespace nsb -l prune-group=true -f hack/testdata/prune/a.yaml \"${kube_flags[@]:?}\" # apply b with namespace kubectl apply --namespace nsb --prune -l prune-group=true -f hack/testdata/prune/b.yaml \"${kube_flags[@]:?}\" # check right pod exists kube::test::get_object_assert 'pods b' \"{{${id_field:?}}}\" 'b' # check wrong pod doesn't exist output_message=$(! kubectl get pods a 2>&1 \"${kube_flags[@]:?}\") kube::test::if_has_string \"${output_message}\" 'pods \"a\" not found' </ins> # cleanup kubectl delete pods b", "positive_passages": [{"docid": "doc-en-kubernetes-55af5a538910186290479e8a37adc800d26766e6d09583162f76a512f0433ab7", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Actually, the parameter depends to all namespaces in the cluster. Filtering is only possible with labels. When running the should only depend on the objects defined in . Why is this needed: A typical use-case is having one repository and namespace per project. When working with declarative objects it should be possible to remove objects and get them pruned like having them described in the respository. This would also help when renaming objects within the repository - which actually needs a manual on the host for the old objects. This even could be a better solution for the problem described in\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig api-machinery\ncc\n/assign\nGitHub didn't allow me to assign the following users: Liujingfang1. Note that only and repo collaborators can be assigned and that 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\nWe have been aware of the issues in prune and we want to improve it. Recently we opened a for improving pruning in . With the proposed solution, the problem from current will be fixed.\nIssues 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\n/remove-lifecycle stale\nIssues 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 .", "commid": "kubernetes_issue_74414", "tokennum": 481}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b3623bb1a96a19a770aec1e9c0c28d2a2aee765ef67e8fbe8395456d9d313847", "query": "output_message=$(! kubectl get pods a 2>&1 \"${kube_flags[@]:?}\") kube::test::if_has_string \"${output_message}\" 'pods \"a\" not found' <ins> kubectl delete pods a kubectl delete pods b # apply a kubectl apply --namespace nsb -l prune-group=true -f hack/testdata/prune/a.yaml \"${kube_flags[@]:?}\" # apply b with namespace kubectl apply --namespace nsb --prune -l prune-group=true -f hack/testdata/prune/b.yaml \"${kube_flags[@]:?}\" # check right pod exists kube::test::get_object_assert 'pods b' \"{{${id_field:?}}}\" 'b' # check wrong pod doesn't exist output_message=$(! kubectl get pods a 2>&1 \"${kube_flags[@]:?}\") kube::test::if_has_string \"${output_message}\" 'pods \"a\" not found' </ins> # cleanup kubectl delete pods b", "positive_passages": [{"docid": "doc-en-kubernetes-cb54288fa32d0be96e99fcb10abda15ff9759ea2461e12485115b7e51b53055d", "text": "/lifecycle stale\n/remove-lifecycle stale\nI just deleted a bunch of things in another team's namespace (:blush:). I'd would love to have this feature. I had been using dry-run in another context, but then forgot to check it again after switching contexts.\nIs there any workaround for this? I want to prune resources within a single namespace only.\nWe're still working on improving prune, the current mechanism is broken enough that we don't recommend people us it.\nAlso look like it's been fixed recently.\nCan someone confirm if this is implemented? I tried using this feature with kubectl 1.18.2, which has , yet as with previous versions kubectl it returned an error about pruning a nonNamespaced object of kind Namespace.\nI assume the problem is that \"Namespace\" is a non-namespaced resource, and therefore is not filtered by namespace, so gets deleted by \"prune\". As a workaround it's possible to manually pass a (whitelist of resources allowed to be deleted), and not include \"Namespace\" in it: The list of resources is taken from .\nWould wrapping this loop with achieve the same result?", "commid": "kubernetes_issue_74414", "tokennum": 262}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b376c06b9b296bfd188d3d242bc0887e853af09a942b8b870df0c42d35d24c1d", "query": "// clusters: //   cow-cluster: //     LocationOfOrigin: \"\" <del> //     certificate-authority-data: REDACTED </del> <ins> //     certificate-authority-data: DATA+OMITTED </ins> //     server: http://cow.org:8080 // contexts: //   federal-context:", "positive_passages": [{"docid": "doc-en-kubernetes-397ec6d3ebe6b2748109f44339689e34d7c15d3a74b9e08d5b86ed108288f149", "text": "Is this a BUG REPORT or FEATURE REQUEST?: What happened: shows: The use of \"REDACTED\" for a CA here is misleading, since it's a public certificate that is not a secret. What you expected to happen: I expected to see the full CA in pem format (like when you cat ) or something like \"SUPPRESSED\" or \"TRUNCATED\" How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Nope Environment: Kubernetes version (use ):Cloud provider or hardware configuration:OS (e.g. from /etc/os-release):Kernel (e.g. ):\n(for thoughts)\nReiterating the mentions to trigger a notification: <detailsIn response to : (for thoughts) 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\nuse you can see the complete certificate authority data\nHey Thank you - I have tracking that . The point of this issue is that at best it's a bad UX; at worst it's a miseducation on pki. \"REDACTED\" isn't the right word here\nIf there are multiple clusters displaying certificates, the configuration will be too long, so this switch is turned off by default. But we can add an example to help use. thanks\nHey I don't personally view truncation the responsibility of the CLI... users can pipe things to a pager if they really care. That being said, I'm not concerned about the length. The issue is purely about the word choice of \"REDACTED\". The term means: The use of the term \"REDACTED\" in the output implies that a CA public key is remove for security when (as you've pointed out) it is removed for truncation. Truncation and redaction are fundamentally different things, and k8s is misusing the word redacted for this use case.\nNot quite a bug, but I think you're right a better term could be used there as it is a public key, not a private key. /remove-kind bug\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close.", "commid": "kubernetes_issue_61573", "tokennum": 495}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b376c06b9b296bfd188d3d242bc0887e853af09a942b8b870df0c42d35d24c1d", "query": "// clusters: //   cow-cluster: //     LocationOfOrigin: \"\" <del> //     certificate-authority-data: REDACTED </del> <ins> //     certificate-authority-data: DATA+OMITTED </ins> //     server: http://cow.org:8080 // contexts: //   federal-context:", "positive_passages": [{"docid": "doc-en-kubernetes-be8602378a7d778cfbc76bff14bb786f501b2719d8c237c227cdd36827d468ae", "text": "If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale I'm not sure what I need to do here. This was marked as a feature. Do you need something more from me?\nWe are waiting for someone to fix this.\n/remove-good-first-issue I don't think this fits our definition of a :\nSo I have to keep replying to the comment bot every 30 days so it doesn't get auto-closed? That feels... odd\nthanks for the education :) unfortunately other issues are higher priority and no one has stepped up to fix this. The autocloser is a form of bug bankruptcy that keeps our issue load in check. The contribex special interest group is definitely open to feedback on the bot.\nThe biggest hurdle in this is that Kubernetes is using some base64 trickery to display the string (basically setting the certificate data to the decoded bytes from ). We can change this to or but not (it has to be a valid base64 encoded string). I tried exploring multiple options for the text, but I couldn't find a suitable one. Given that we already print the user tokens and other credentials this is a bit weird. Should we redact those too? Is it okay if we print the CA certificate instead of truncating it?\nI can't help but laugh at: I'm not wed to any particular name. I also have no problem displaying the entire certificate. The crux of the issue is that a CA public key is not secret or sensitive. It's a public key\nI agree. The issue is with the constraints imposed by how this is implemented currently. I tried to come up with a suitable string (given the constraint) and couldn't find anything acceptable... The only suitable option that worked for me is . I personally prefer to print the CA certificate since we are already printing user tokens and client certs that are actual secrets.\nI agree. Who do we need to get in agreement that printing the full CA is the best path forward?\nthe data is not omitted for security purposes, but to make the output more readable. see REDACTED is misleading... it should probably be \"elided\" or \"...\"\nyou can run to view full content\nthat's the crux of this issue - REDACTED is misleading.", "commid": "kubernetes_issue_61573", "tokennum": 520}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b376c06b9b296bfd188d3d242bc0887e853af09a942b8b870df0c42d35d24c1d", "query": "// clusters: //   cow-cluster: //     LocationOfOrigin: \"\" <del> //     certificate-authority-data: REDACTED </del> <ins> //     certificate-authority-data: DATA+OMITTED </ins> //     server: http://cow.org:8080 // contexts: //   federal-context:", "positive_passages": [{"docid": "doc-en-kubernetes-0c20cfda2a4143b97ca34085e4ba4933a2256b4cc12b09ed01e77387d3b1e642", "text": "However, pointed out that other \"long\" fields are still completely printed in plain text such as client certs, so I think we need to revisit the \"readability\" argument. What do you think?\nthey are not... client cert/key are elided in the same way for the same reason: something like \"++data+omitted++\" could be better If the intent of config view without --raw specified is to be readable (which it currently is), printing many extremely long fields isn't great\nHmm what about: I'm pretty sure that would give us a valid b64 string (8+12=20%4=0) and it would subtly hint that the data isn't a secret.\nOnly valid characters are . And adding a prefix from the certificate only complicates things. is a suitable usable option. I'll submit a PR to continue the discussion there.", "commid": "kubernetes_issue_61573", "tokennum": 195}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b37b926d267c280c40a208460e9f1482071423626869c880937eed848e16137e", "query": "ginkgo.By(\"Creating a ResourceQuota\") quotaName := \"test-quota\" resourceQuota := newTestResourceQuota(quotaName) <ins> resourceQuota.Spec.Hard[v1.ResourceConfigMaps] = resource.MustParse(hardConfigMaps) </ins> _, err = createResourceQuota(f.ClientSet, f.Namespace.Name, resourceQuota) framework.ExpectNoError(err)", "positive_passages": [{"docid": "doc-en-kubernetes-7efc22ed3a8fb290fc16a7b40edf13445187015d16976624a8ed8ba9d9def220", "text": "I ran conformance tests on a cluster that had a controller enabled that syncs a configmap across all clusters. It failed: Appears to be due to a 2 configmap limit: These clusters should pass conformance. This is a very common pattern (even Kubernetes itself does it!). I didn't run it myself, but apparently just install Istio and run the conformance suite. See for details Kubernetes version (use ): v1.20.2\n/assign\nmy guess is the CA configmap created by default in 1.20 exacerbated this issue. I agree the conformance test should make fewer assumptions about the cluster it is running in and should accomodate default configmaps. left a comment on the PR in flight for this. I'd like to see the change picked to 1.20 as well.\n/triage accepted /priority important-soon", "commid": "kubernetes_issue_100016", "tokennum": 195}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b3819bbd8850f7c5f7d60734e07be169894e99ed2db1f12b3650c7d5f906d1d5", "query": "} }) <del> ginkgo.It(\"should respect internalTrafficPolicy=Local Pod to Pod (hostNetwork: true) [Feature:ServiceInternalTrafficPolicy]\", func() { </del> <ins> ginkgo.It(\"should respect internalTrafficPolicy=Local Pod and Node, to Pod (hostNetwork: true) [Feature:ServiceInternalTrafficPolicy]\", func() { </ins> // windows kube-proxy does not support this feature yet // TODO: remove this skip when windows-based proxies implement internalTrafficPolicy e2eskipper.SkipIfNodeOSDistroIs(\"windows\")", "positive_passages": [{"docid": "doc-en-kubernetes-06e17cf980b6b4fe370857f0b2e0687536ee3b3b60ed1f78548a694def2f21f6", "text": "Failed here /retest Originally posted by in This fails because the pod tries to bind port 80, that is a very demanded port, but there are two tests doing that, that increase the chance to collide\n/sig network\nClose when merges\n/triage accepted", "commid": "kubernetes_issue_104406", "tokennum": 54}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b39288e2e61adc4ac931f5dff5e732805cd0d6a0fef83dd11ee54f67e970223a", "query": "} /* <del> Release : v1.12 Testname: Security Context: readOnlyRootFilesystem=true. Description: when a container has configured readOnlyRootFilesystem to true, write operations are not allowed. This test is marked LinuxOnly since Windows does not support creating containers with read-only access. </del> <ins> Release : v1.15 Testname: Security Context, readOnlyRootFilesystem=true. Description: Container is configured to run with readOnlyRootFilesystem to true which will force containers to run with a read only root file system. Write operation MUST NOT be allowed and Pod MUST be in Failed state. At this moment we are not considering this test for Conformance due to use of SecurityContext. [LinuxOnly]: This test is marked as LinuxOnly since Windows does not support creating containers with read-only access. </ins> */ It(\"should run the container with readonly rootfs when readOnlyRootFilesystem=true [LinuxOnly] [NodeConformance]\", func() { createAndWaitUserPod(true) }) /* <del> Release : v1.12 Testname: Security Context: readOnlyRootFilesystem=false. Description: when a container has configured readOnlyRootFilesystem to false, write operations are allowed. </del> <ins> Release : v1.15 Testname: Security Context, readOnlyRootFilesystem=false. Description: Container is configured to run with readOnlyRootFilesystem to false. Write operation MUST be allowed and Pod MUST be in Succeeded state. </ins> */ <del> It(\"should run the container with writable rootfs when readOnlyRootFilesystem=false [NodeConformance]\", func() { </del> <ins> framework.ConformanceIt(\"should run the container with writable rootfs when readOnlyRootFilesystem=false [NodeConformance]\", func() { </ins> createAndWaitUserPod(false) }) })", "positive_passages": [{"docid": "doc-en-kubernetes-f8a45a347ca0a58053d8639059bb6be0a8ec66e1196dbd0290c02922abc9dcd2", "text": "/kind cleanup /area conformance /area test /sig node /sig testing /sig architecture /assign /assign We have a number of tests that only have the tag that may make sense as tests, we should identify whether these tests cases meet (or could meet) the . We should open PR's to promote these if so. I would advise starting with the test/common cases\nGitHub didn't allow me to assign the following users: mgdevstack, mkurylec. Note that only and repo collaborators can be assigned. For more information please see <detailsIn response to : /kind cleanup /area conformance /area test /sig node /sig testing /sig architecture /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\n/assign\nThe tests in test/e2enode don't actually get run as part of Conformance as near as I can tell. If we want to run them as part of conformance, they need to be migrated into test/e2e/common. Some of the tests in e2enode may not be able to be ported over because they assume a level access we don't have in a conformance environment.\nregarding this testcase: [sig-storage] HostPath should support r/w [NodeConformance]: It uses hostPath and privileged=true, to read/write from /tmp folder. Which would you suggest is the best orientation to overcome the privilege mode setting and allow its promotion?\n/assign\nRegarding , the suite runs the test only if the kubelet configuration was required to have the QOS (cgroups-per-qos) enabled. This configuration for the kubelet is selected at the time the cluster is set up. Looking for where this might be configured found: where is set to true. For other settings it is also configured to true. where is set to true. BUT also found where it is mentioned that the flag is no longer available. Questions: would it be ok to promote this test to be conformance, even it can be skipped based on configuration of the cluster? And not supported in the containerized kubelet?\nI would consider cgroups to be an implementation detail that Conformance shouldn't be verifying\nIt uses hostPath and privileged=true, to read/write from /tmp folder.", "commid": "kubernetes_issue_66875", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b39288e2e61adc4ac931f5dff5e732805cd0d6a0fef83dd11ee54f67e970223a", "query": "} /* <del> Release : v1.12 Testname: Security Context: readOnlyRootFilesystem=true. Description: when a container has configured readOnlyRootFilesystem to true, write operations are not allowed. This test is marked LinuxOnly since Windows does not support creating containers with read-only access. </del> <ins> Release : v1.15 Testname: Security Context, readOnlyRootFilesystem=true. Description: Container is configured to run with readOnlyRootFilesystem to true which will force containers to run with a read only root file system. Write operation MUST NOT be allowed and Pod MUST be in Failed state. At this moment we are not considering this test for Conformance due to use of SecurityContext. [LinuxOnly]: This test is marked as LinuxOnly since Windows does not support creating containers with read-only access. </ins> */ It(\"should run the container with readonly rootfs when readOnlyRootFilesystem=true [LinuxOnly] [NodeConformance]\", func() { createAndWaitUserPod(true) }) /* <del> Release : v1.12 Testname: Security Context: readOnlyRootFilesystem=false. Description: when a container has configured readOnlyRootFilesystem to false, write operations are allowed. </del> <ins> Release : v1.15 Testname: Security Context, readOnlyRootFilesystem=false. Description: Container is configured to run with readOnlyRootFilesystem to false. Write operation MUST be allowed and Pod MUST be in Succeeded state. </ins> */ <del> It(\"should run the container with writable rootfs when readOnlyRootFilesystem=false [NodeConformance]\", func() { </del> <ins> framework.ConformanceIt(\"should run the container with writable rootfs when readOnlyRootFilesystem=false [NodeConformance]\", func() { </ins> createAndWaitUserPod(false) }) })", "positive_passages": [{"docid": "doc-en-kubernetes-b0f7522fd47a7c9f3d30009b5f18d7b37ba2aa8723a4c0ef112b90078054f0fc", "text": "Which would you suggest is the best orientation to overcome the privilege mode setting and allow its promotion? Michelle Au If my understanding is correct, on some platforms, writing to /tmp requires privileged. I don't see a way to to remove that requirement.\nIf my understanding is correct, on some platforms, writing to /tmp requires privileged. I don't see a way to to remove that requirement. Yeah writing to host doesn't seem like a thing we can expect of conformance tests. I wonder if it makes sense to tag this test with something to denote the requirement, ie: I see some tests in test/e2e_node use\nThe hostpath tests in already have a comment explaining this. Maybe the comment should be updated to be more clear that that is the reason why we can't add it to conformance.\nThat's /tmp on the host or in the container filesystem?\n/tmp on the host\nping what else remains to be done before we close this out? I am guessing that we want to close , is there anything beyond that?\nOnce tests under (issue- ) and are promoted we are good to close this issue. Short update for reference- None of [NodeConformance] tests from \"test/e2e_node\" seems eligible for [Conformance] promotion at this moment due to node level dependencies. Remaining [NodeConformance] tests from \"test/e2e\" has following status - Waiting for to be closed and then below tests would be promoted to Conformance Needs to be Promoted Can not be promoted to Conformance as //Slow by design Can not be promoted due to Node level dependency\nIssues 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\n/remove-lifecycle stale\n/lifecycle frozen\n/assign", "commid": "kubernetes_issue_66875", "tokennum": 428}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b39d7f59b3947c4dee51e21c73f2337f0a2ea3f83e104e8f85b802d4348be0af", "query": "} func (zones Zones) List() ([]dnsprovider.Zone, error) { <ins> var zoneList []dnsprovider.Zone </ins> response, err := zones.impl.List(zones.project()).Do() if err != nil { <ins> if apiErr, ok := err.(*googleapi.Error); ok && apiErr.Code == 404 { return zoneList, nil } </ins> return nil, err } managedZones := response.ManagedZones() <del> zoneList := make([]dnsprovider.Zone, len(managedZones)) </del> <ins> zoneList = make([]dnsprovider.Zone, len(managedZones)) </ins> for i, zone := range managedZones { zoneList[i] = &Zone{zone, &zones} }", "positive_passages": [{"docid": "doc-en-kubernetes-2b4d325d4814fe81f2a99615b844cff823940de918e3b360e7f108b94b4fe81b", "text": "/kind bug What happened: walteraa [6:55 AM] Hi, The controller manager of the federation using Google cloud DNS is crashing, the log showed is that: the hyperkube command is that: I have created this in the Google DNS Someone knows why the DNS zone query is getting the 404 error?? :disappointed: What you expected to happen: It should have created the missing domain. How to reproduce it (as minimally and precisely as possible): As per above. Anything else we need to know?: Environment: Kubernetes version (use ): 1.7.4 Cloud provider or hardware configuration**: OpenStack (irrelevant) OS (e.g. from /etc/os-release): irrelevant Kernel (e.g. ): irrelevant Install tools: irrelevant Others: irrelevant\nThe bug is related to this: The above code assumes that the provider code returns no error but an empty list if the domain does not exist, but instead the provider returns a 404. Need to fix the provider and/or the above code.\n/sig federation\nI am unlikely to have time to work on this soon, so if anyone else wants to, go right ahead.\n/assign\nAn additional information: I have created a which is based on the credential JSON file created through instruction. After that, I have configured the Federation controller manager to mount this secret as a volume in the container and set the environment variable to the JSON file inside this volume. Before doing that, I was getting an authentication error so the google DNS provider couldn't be instantiated, and after doing the instructions that I mentioned before, this authentication error was solved but now I'm getting 404 error when Google DNS provider tries access the specified managed zone. The file that I have generated follow this structure:", "commid": "kubernetes_issue_51139", "tokennum": 376}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b3a4b4f777e2fe7b742285fe9ebd148d0af4b8ce91a8ab550b9c42dfa9ae6c19", "query": "kubectl create secret docker-registry test-secret --docker-username=test-user --docker-password=test-password --docker-email='test-user@test.com' --namespace=test-secrets # Post-condition: secret exists and has expected values kube::test::get_object_assert 'secret/test-secret --namespace=test-secrets' \"{{$id_field}}\" 'test-secret' <del> kube::test::get_object_assert 'secret/test-secret --namespace=test-secrets' \"{{$secret_type}}\" 'kubernetes.io/dockercfg' [[ \"$(kubectl get secret/test-secret --namespace=test-secrets -o yaml \"${kube_flags[@]}\" | grep '.dockercfg:')\" ]] </del> <ins> kube::test::get_object_assert 'secret/test-secret --namespace=test-secrets' \"{{$secret_type}}\" 'kubernetes.io/dockerconfigjson' [[ \"$(kubectl get secret/test-secret --namespace=test-secrets -o yaml \"${kube_flags[@]}\" | grep '.dockerconfigjson:')\" ]] </ins> # Clean-up kubectl delete secret test-secret --namespace=test-secrets", "positive_passages": [{"docid": "doc-en-kubernetes-4279a6f285666ec67ce8924ca9393c19176af7de5707dd42a5f4c239ba12ead2", "text": "/kind bug We're having trouble retrieving images from a private registry on DockerCloud. For nearly a year the following has worked flawlessly. Last Friday I pulled down the 1.9.0 CLI (via brew) and since then have not been able to access any image in a private registry on DockerCloud. I've tried this on 10+ brand new clusters created with kops v1.8.0. The Kubernetes cluster version have been 1.8.0, 1.8.4, 1.8.5 and 1.9.0 (which is not supported by kops yet) and all exhibit the same problem. We create the secret as such: And verify it using: Which yields: And create a test service with with these contents: The pod fails immediatly with: I've reviewed the 1.9.0 release notes and nothing jumps out as the root cause. For reference I've tried putting quotes around the value when creating the secret to no avail. I've also tried prefixing the value with , so the full value would read: also to no avail. Environment: Kubernetes version: Cloud provider and installation info: AWS cluster built with Kops 1.8.0, using (to isolate this issue) nearly the default settings for everything.\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI have same problem, and I \"solved\" it creating a docker-registry secret in an old kubernetes version and pasting it on new kubernetes\nI'm recently (I know it worked perfectly about last month) facing issues with as well. For me it ended in a similar manner saying: I was able to confirm, that this is a kubernetes CLI related issue and not end user. Based on and this I was able to create properly formatted auth information looking like this: . When encoding this one-liner using (MacOS workstation) and apply like this works fine and images can be pulled from private repository again.", "commid": "kubernetes_issue_57427", "tokennum": 466}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b3a4b4f777e2fe7b742285fe9ebd148d0af4b8ce91a8ab550b9c42dfa9ae6c19", "query": "kubectl create secret docker-registry test-secret --docker-username=test-user --docker-password=test-password --docker-email='test-user@test.com' --namespace=test-secrets # Post-condition: secret exists and has expected values kube::test::get_object_assert 'secret/test-secret --namespace=test-secrets' \"{{$id_field}}\" 'test-secret' <del> kube::test::get_object_assert 'secret/test-secret --namespace=test-secrets' \"{{$secret_type}}\" 'kubernetes.io/dockercfg' [[ \"$(kubectl get secret/test-secret --namespace=test-secrets -o yaml \"${kube_flags[@]}\" | grep '.dockercfg:')\" ]] </del> <ins> kube::test::get_object_assert 'secret/test-secret --namespace=test-secrets' \"{{$secret_type}}\" 'kubernetes.io/dockerconfigjson' [[ \"$(kubectl get secret/test-secret --namespace=test-secrets -o yaml \"${kube_flags[@]}\" | grep '.dockerconfigjson:')\" ]] </ins> # Clean-up kubectl delete secret test-secret --namespace=test-secrets", "positive_passages": [{"docid": "doc-en-kubernetes-784638a373a6d25c569537512411337ba05226e31cffa99d23b394dffb534564", "text": "However this breaks all automation and can't be considered as solution Confirmed working with kubectl 1.8.5 and server 1.8.4 (guess 1.7.9 as well)\nlooks like there's an extra \"auths\" element when adding the secret using 1.9 kubectl\nAdded in /assign\nMany thanks for the quick fix on this. Any idea when this might get rolled out? Also, it might be a good idea if this was to the known issue list for v1.9.0. It would have saved us a bunch of time trying to track down the root cause. Just trying to make sure no one else needs to do the same.\nlinking to the \"v1.9.0 known issues\" list\nack, asking Mehdy since he is the patch manager for v1.9 branch. Mehdy, any idea when we can ship 1.9.1 with this fix?\nworkarounds for folks until 1.9.1 is released: if you have a .dockerconfigjson for your private registry already, you can manually specify the type and data key (e.g. ) if you don't have a .dockerconfigjson file already, you can fix up the secret produced by manually: the type from to the data key from to the modified secret with\n1 will be released tomorrow\nI can confirm solution works, thanks so much!\nI am still having issues in 1.9.1. This worked in the 1.8.x branches: results in the following error:\nyou have to remove the gitlab-registry secret before you can apply an update... type is immutable, and the fix in 1.9.1 required changing the type of the secret", "commid": "kubernetes_issue_57427", "tokennum": 370}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b3deb8737701dac7c97f1110aed23842bd83a63edb4fb439497425313bc89a6e", "query": "<ins> <!-- BEGIN MUNGE: UNVERSIONED_WARNING --> <!-- BEGIN STRIP_FOR_RELEASE --> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <img src=\"http://kubernetes.io/img/warning.png\" alt=\"WARNING\" width=\"25\" height=\"25\"> <h2>PLEASE NOTE: This document applies to the HEAD of the source tree</h2> If you are using a released version of Kubernetes, you should refer to the docs that go with that version. Documentation for other releases can be found at [releases.k8s.io](http://releases.k8s.io). </strong> -- <!-- END STRIP_FOR_RELEASE --> <!-- END MUNGE: UNVERSIONED_WARNING --> # Generic Configuration Object ## Abstract The `ConfigMap` API resource stores data used for the configuration of applications deployed on Kubernetes. The main focus of this resource is to: * Provide dynamic distribution of configuration data to deployed applications. * Encapsulate configuration information and simplify `Kubernetes` deployments. * Create a flexible configuration model for `Kubernetes`. ## Motivation A `Secret`-like API resource is needed to store configuration data that pods can consume. Goals of this design: 1.  Describe a `ConfigMap` API resource 2.  Describe the semantics of consuming `ConfigMap` as environment variables 3.  Describe the semantics of consuming `ConfigMap` as files in a volume ## Use Cases 1. As a user, I want to be able to consume configuration data as environment variables 2. As a user, I want to be able to consume configuration data as files in a volume 3. As a user, I want my view of configuration data in files to be eventually consistent with changes to the data ### Consuming `ConfigMap` as Environment Variables Many programs read their configuration from environment variables.  `ConfigMap` should be possible to consume in environment variables.  The rough series of events for consuming `ConfigMap` this way is: 1. A `ConfigMap` object is created 2. A pod that consumes the configuration data via environment variables is created 3. The pod is scheduled onto a node 4. The kubelet retrieves the `ConfigMap` resource(s) referenced by the pod and starts the container processes with the appropriate data in environment variables ### Consuming `ConfigMap` in Volumes Many programs read their configuration from configuration files.  `ConfigMap` should be possible to consume in a volume.  The rough series of events for consuming `ConfigMap` this way is: 1. A `ConfigMap` object is created 2. A new pod using the `ConfigMap` via the volume plugin is created 3. The pod is scheduled onto a node 4. The Kubelet creates an instance of the volume plugin and calls its `Setup()` method 5. The volume plugin retrieves the `ConfigMap` resource(s) referenced by the pod and projects the appropriate data into the volume ### Consuming `ConfigMap`  Updates Any long-running system has configuration that is mutated over time.  Changes made to configuration data must be made visible to pods consuming data in volumes so that they can respond to those changes. The `resourceVersion` of the `ConfigMap` object will be updated by the API server every time the object is modified.  After an update, modifications will be made visible to the consumer container: 1. A `ConfigMap` object is created 2. A new pod using the `ConfigMap` via the volume plugin is created 3. The pod is scheduled onto a node 4. During the sync loop, the Kubelet creates an instance of the volume plugin and calls its `Setup()` method 5. The volume plugin retrieves the `ConfigMap` resource(s) referenced by the pod and projects the appropriate data into the volume 6. The `ConfigMap` referenced by the pod is updated 7. During the next iteration of the `syncLoop`, the Kubelet creates an instance of the volume plugin and calls its `Setup()` method 8. The volume plugin projects the updated data into the volume atomically It is the consuming pod's responsibility to make use of the updated data once it is made visible. Because environment variables cannot be updated without restarting a container, configuration data consumed in environment variables will not be updated. ### Advantages * Easy to consume in pods; consumer-agnostic * Configuration data is persistent and versioned * Consumers of configuration data in volumes can respond to changes in the data ## Proposed Design ### API Resource The `ConfigMap` resource will be added to the main API: ```go package api // ConfigMap holds configuration data for pods to consume. type ConfigMap struct { TypeMeta   `json:\",inline\"` ObjectMeta `json:\"metadata,omitempty\"` // Data contains the configuration data.  Each key must be a valid DNS_SUBDOMAIN or leading // dot followed by valid DNS_SUBDOMAIN. Data map[string]string `json:\"data,omitempty\"` } type ConfigMapList struct { TypeMeta `json:\",inline\"` ListMeta `json:\"metadata,omitempty\"` Items []ConfigMap `json:\"items\"` } ``` A `Registry` implementation for `ConfigMap` will be added to `pkg/registry/configmap`. ### Environment Variables The `EnvVarSource` will be extended with a new selector for `ConfigMap`: ```go package api // EnvVarSource represents a source for the value of an EnvVar. type EnvVarSource struct { // other fields omitted // Specifies a ConfigMap key ConfigMap *ConfigMapSelector `json:\"configMap,omitempty\"` } // ConfigMapSelector selects a key of a ConfigMap. type ConfigMapSelector struct { // The name of the ConfigMap to select a key from. ConfigMapName string `json:\"configMapName\"` // The key of the ConfigMap to select. Key string `json:\"key\"` } ``` ### Volume Source A new `ConfigMapVolumeSource` type of volume source containing the `ConfigMap` object will be added to the `VolumeSource` struct in the API: ```go package api type VolumeSource struct { // other fields omitted ConfigMap *ConfigMapVolumeSource `json:\"configMap,omitempty\"` } // Represents a volume that holds configuration data. type ConfigMapVolumeSource struct { LocalObjectReference `json:\",inline\"` // A list of keys to project into the volume. // If unspecified, each key-value pair in the Data field of the // referenced ConfigMap will be projected into the volume as a file whose name // is the key and content is the value. // If specified, the listed keys will be project into the specified paths, and // unlisted keys will not be present. Items []KeyToPath `json:\"items,omitempty\"` } // Represents a mapping of a key to a relative path. type KeyToPath struct { // The name of the key to select Key string `json:\"key\"` // The relative path name of the file to be created. // Must not be absolute or contain the '..' path. Must be utf-8 encoded. // The first item of the relative path must not start with '..' Path string `json:\"path\"` } ``` **Note:** The update logic used in the downward API volume plug-in will be extracted and re-used in the volume plug-in for `ConfigMap`. ### Changes to Secret We will update the Secret volume plugin to have a similar API to the new ConfigMap volume plugin. The secret volume plugin will also begin updating secret content in the volume when secrets change. ## Examples #### Consuming `ConfigMap` as Environment Variables ```yaml apiVersion: v1 kind: ConfigMap metadata: name: etcd-env-config data: number-of-members: 1 initial-cluster-state: new initial-cluster-token: DUMMY_ETCD_INITIAL_CLUSTER_TOKEN discovery-token: DUMMY_ETCD_DISCOVERY_TOKEN discovery-url: http://etcd-discovery:2379 etcdctl-peers: http://etcd:2379 ``` This pod consumes the `ConfigMap` as environment variables: ```yaml apiVersion: v1 kind: Pod metadata: name: config-env-example spec: containers: - name: etcd image: openshift/etcd-20-centos7 ports: - containerPort: 2379 protocol: TCP - containerPort: 2380 protocol: TCP env: - name: ETCD_NUM_MEMBERS valueFrom: configMap: configMapName: etcd-env-config key: number-of-members - name: ETCD_INITIAL_CLUSTER_STATE valueFrom: configMap: configMapName: etcd-env-config key: initial-cluster-state - name: ETCD_DISCOVERY_TOKEN valueFrom: configMap: configMapName: etcd-env-config key: discovery-token - name: ETCD_DISCOVERY_URL valueFrom: configMap: configMapName: etcd-env-config key: discovery-url - name: ETCDCTL_PEERS valueFrom: configMap: configMapName: etcd-env-config key: etcdctl-peers ``` #### Consuming `ConfigMap` as Volumes `redis-volume-config` is intended to be used as a volume containing a config file: ```yaml apiVersion: extensions/v1beta1 kind: ConfigMap metadata: name: redis-volume-config data: redis.conf: \"pidfile /var/run/redis.pidnport6379ntcp-backlog 511n databases 1ntimeout 0n\" ``` The following pod consumes the `redis-volume-config` in a volume: ```yaml apiVersion: v1 kind: Pod metadata: name: config-volume-example spec: containers: - name: redis image: kubernetes/redis command: \"redis-server /mnt/config-map/etc/redis.conf\" ports: - containerPort: 6379 volumeMounts: - name: config-map-volume mountPath: /mnt/config-map volumes: - name: config-map-volume configMap: name: redis-volume-config items: - path: \"etc/redis.conf\" key: redis.conf ``` ## Future Improvements In the future, we may add the ability to specify an init-container that can watch the volume contents for updates and respond to changes when they occur. <!-- BEGIN MUNGE: GENERATED_ANALYTICS --> [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/configmap.md?pixel)]() <!-- END MUNGE: GENERATED_ANALYTICS --> </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-ab39f39ee12e84e818aa9c92c6877733f255a4fad832176aa0525d5bb0051663", "text": "What happened: Visited It shows the release notes for v1.17 What you expected to happen: See the release notes for v1.18 How to reproduce it (as minimally and precisely as possible): Open in any browser or with curl\n/sig docs\n/assign", "commid": "kubernetes_issue_89598", "tokennum": 57}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b3e0989c22fd7b6ccabce082f989f2c02ef4ecfa2523df8b13aecd09bbe30fd2", "query": "}) }) <ins> Describe(\"[Skipped][Example]Liveness\", func() { It(\"liveness pods should be automatically restarted\", func() { mkpath := func(file string) string { return filepath.Join(testContext.RepoRoot, \"docs\", \"user-guide\", \"liveness\", file) } execYaml := mkpath(\"exec-liveness.yaml\") httpYaml := mkpath(\"http-liveness.yaml\") nsFlag := fmt.Sprintf(\"--namespace=%v\", ns) runKubectl(\"create\", \"-f\", execYaml, nsFlag) runKubectl(\"create\", \"-f\", httpYaml, nsFlag) checkRestart := func(podName string, timeout time.Duration) { err := waitForPodRunningInNamespace(c, podName, ns) Expect(err).NotTo(HaveOccurred()) for t := time.Now(); time.Since(t) < timeout; time.Sleep(poll) { pod, err := c.Pods(ns).Get(podName) expectNoError(err, fmt.Sprintf(\"getting pod %s\", podName)) restartCount := api.GetExistingContainerStatus(pod.Status.ContainerStatuses, \"liveness\").RestartCount Logf(\"Pod: %s   restart count:%d\", podName, restartCount) if restartCount > 0 { return } } Failf(\"Pod %s was not restarted\", podName) } By(\"Check restarts\") checkRestart(\"liveness-exec\", time.Minute) checkRestart(\"liveness-http\", time.Minute) }) }) </ins> }) func makeHttpRequestToService(c *client.Client, ns, service, path string) (string, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-efbe4c5d01aeff5665bc84249f5b94afd1b0f5aa50522bcb417b43505717780e", "text": "! ! Which jobs are failing: Which test(s) are failing: Since when has it been failing: failures started between 3-4PM (EST), on 1/11/2019 the failures appear limited to containerd jobs (here's a triage search for note that only containerd jobs appear as failing): /sig node\nthe relevant commit range on master appears to be ... the relevent commit range in test-infra appears to be\ncc\nfor test-infra: aws-janitor: clean up ELBs - definitely unrelated, only affects some of the AWS testing cleanup Update kubekins tag for eks jobs - definitely unrelated, affects the docker image in which some EKS testing runs only Update ubuntu image used for e2e node test - I think unrelated, appears to only affect the node e2e tests rest are merge commits\nthanks for checking. it's also possible the commit ranges I linked to need to be expanded slightly... that was my first attempt at correlating merge timestamps with the triage board failures... it's possible I got timezone correlation wrong a few hours in one direction or the other.\nah, they probably do then. otherwise I'd say something else must have changed out of band (perhaps there's a pointer to a containerd version to use somewhere or something).\nflakes or was something fixed offline (gce / gci / gke)? https://k8s- https://k8s- these turned (mostly) green without k/k and k/test-infra changes.\nHuh. Disconcerting, but ok. /close\nClosing this issue. <detailsIn response to : Huh. Disconcerting, but ok. 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\nAll test failed because of not being able to pull image from : I guess this is a bug in , and they fixed it now.\nnice catch. thanks\nshould the CSI images be in our regular repo?", "commid": "kubernetes_issue_72863", "tokennum": 448}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b404923405e57657c259e765730a86215e884eef0194ef6fe0a4d8be20313979", "query": "t.Errorf(\"Expect command executed %d times, but got %d\", svcCount, fexec.CommandCalls) } } <ins> func TestClearUDPConntrackForPortNAT(t *testing.T) { fcmd := fakeexec.FakeCmd{ CombinedOutputScript: []fakeexec.FakeCombinedOutputAction{ func() ([]byte, error) { return []byte(\"1 flow entries have been deleted\"), nil }, func() ([]byte, error) { return []byte(\"\"), fmt.Errorf(\"conntrack v1.4.2 (conntrack-tools): 0 flow entries have been deleted\") }, func() ([]byte, error) { return []byte(\"1 flow entries have been deleted\"), nil }, }, } fexec := fakeexec.FakeExec{ CommandScript: []fakeexec.FakeCommandAction{ func(cmd string, args ...string) exec.Cmd { return fakeexec.InitFakeCmd(&fcmd, cmd, args...) }, func(cmd string, args ...string) exec.Cmd { return fakeexec.InitFakeCmd(&fcmd, cmd, args...) }, func(cmd string, args ...string) exec.Cmd { return fakeexec.InitFakeCmd(&fcmd, cmd, args...) }, }, LookPathFunc: func(cmd string) (string, error) { return cmd, nil }, } testCases := []struct { name string port int dest string }{ { name: \"IPv4 success\", port: 30211, dest: \"1.2.3.4\", }, } svcCount := 0 for i, tc := range testCases { err := ClearEntriesForPortNAT(&fexec, tc.dest, tc.port, v1.ProtocolUDP) if err != nil { t.Errorf(\"%s test case: unexpected error: %v\", tc.name, err) } expectCommand := fmt.Sprintf(\"conntrack -D -p udp --dport %d --dst-nat %s\", tc.port, tc.dest) + familyParamStr(utilnet.IsIPv6String(tc.dest)) execCommand := strings.Join(fcmd.CombinedOutputLog[i], \" \") if expectCommand != execCommand { t.Errorf(\"%s test case: Expect command: %s, but executed %s\", tc.name, expectCommand, execCommand) } svcCount++ } if svcCount != fexec.CommandCalls { t.Errorf(\"Expect command executed %d times, but got %d\", svcCount, fexec.CommandCalls) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-9e39524d0e4c89f1ddf9c516fe4e1c471a25826ee6b222abfe1f6c0cc213064c", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: BUG REPORT What happened: When deleting/recreating pods backing a UDP service, traffic from external senders stops flowing. What you expected to happen: Traffic would continue to flow to new pods. How to reproduce it (as minimally and precisely as possible): Based on reading of similar issues and commit messages it seems like this would be most noticable on high-volume UDP applications, statsd and syslog are good examples. a deployment and service for a UDP app. In my test case, this would be the container. an external node, create a small test script utilizing a statsd library such as pystatsd. The most important part is that the sender uses the same source-port for every packet sent. Ex: the sender. Install tcpdump into the pod and watch for incoming packets, example from the test case: the pod tcpdump in the newly created pod. Observe that no new matching packets are flowing. existing conntrack rules on all nodes in the cluster. You should see traffic start flowing to the pod again. example command for clearing conntrack rules on the nodes: Anything else we need to know?: I have tested this only on GKE-managed clusters that utilize google forwarding-rules for external LBs, but I believe the issue may be present on any platform where iptables mode for kube-proxy is used. Tested and verified on 1.8.6-gke.0 and 1.7.11-gke.1. Also tested with both Google Container-optimized OS and the Ubuntu-based node images. I have only test this on GKE It appears this was a known issue and should have been cleared up by: From my reading of , it seems as if the func should exec() to clear up UDP entries on service endpoint change, but the only place I see that func called is from syncProxyRules(). That func looks complex and possibly like it is only run occasionally and not on service/endpoint changes. Environment: Kubernetes version (use ): (Also tested on 1.7.11-gke.1) Cloud provider or hardware configuration: GKE-managed clusters, google cloud. OS (e.g.", "commid": "kubernetes_issue_59368", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b404923405e57657c259e765730a86215e884eef0194ef6fe0a4d8be20313979", "query": "t.Errorf(\"Expect command executed %d times, but got %d\", svcCount, fexec.CommandCalls) } } <ins> func TestClearUDPConntrackForPortNAT(t *testing.T) { fcmd := fakeexec.FakeCmd{ CombinedOutputScript: []fakeexec.FakeCombinedOutputAction{ func() ([]byte, error) { return []byte(\"1 flow entries have been deleted\"), nil }, func() ([]byte, error) { return []byte(\"\"), fmt.Errorf(\"conntrack v1.4.2 (conntrack-tools): 0 flow entries have been deleted\") }, func() ([]byte, error) { return []byte(\"1 flow entries have been deleted\"), nil }, }, } fexec := fakeexec.FakeExec{ CommandScript: []fakeexec.FakeCommandAction{ func(cmd string, args ...string) exec.Cmd { return fakeexec.InitFakeCmd(&fcmd, cmd, args...) }, func(cmd string, args ...string) exec.Cmd { return fakeexec.InitFakeCmd(&fcmd, cmd, args...) }, func(cmd string, args ...string) exec.Cmd { return fakeexec.InitFakeCmd(&fcmd, cmd, args...) }, }, LookPathFunc: func(cmd string) (string, error) { return cmd, nil }, } testCases := []struct { name string port int dest string }{ { name: \"IPv4 success\", port: 30211, dest: \"1.2.3.4\", }, } svcCount := 0 for i, tc := range testCases { err := ClearEntriesForPortNAT(&fexec, tc.dest, tc.port, v1.ProtocolUDP) if err != nil { t.Errorf(\"%s test case: unexpected error: %v\", tc.name, err) } expectCommand := fmt.Sprintf(\"conntrack -D -p udp --dport %d --dst-nat %s\", tc.port, tc.dest) + familyParamStr(utilnet.IsIPv6String(tc.dest)) execCommand := strings.Join(fcmd.CombinedOutputLog[i], \" \") if expectCommand != execCommand { t.Errorf(\"%s test case: Expect command: %s, but executed %s\", tc.name, expectCommand, execCommand) } svcCount++ } if svcCount != fexec.CommandCalls { t.Errorf(\"Expect command executed %d times, but got %d\", svcCount, fexec.CommandCalls) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-27a4c6cdabc82c95dde932bb7bf1e1865b5f691c3b3e7bf1ed0c71bfc361fddc", "text": "from /etc/os-release): tried both: and Kernel (e.g. ): and Install tools: Others:\n/sig network\nWe also ran into this in kubernetes v1.7.6 using OpenShift 3.7:\n~I believe this is the same as ~If so, it is fixed in 1.10: These are about HostPort, not NodePort, sorry for the noise.\nIssues 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\nIs there any other known workaround for this besides updating conntrack rules on the kube nodes? I tried deleting and recreating the service, but this didn't update the rules. When I restart the stream on the client side data flows correctly again (perhaps it's perceived as a new connection), but I have to restart the stream for each sender.\n/remove-lifecycle stale\nFWIW, this is not fixed in 1.10 - that fix was for HostPort, and this is still a bug for NodePort.\nI am seeing this issue in 1.11. I am using LoadBalancer type.\nhas been working on a fix for this, FYI.\nThis issue is extremely impactful for telephony protocols that rely on static source ip and source port. Any update on a possible workaround? I was thinking a potential workaround might be to reduce the UDP timeout to something really short so the stale conntrack entries go away faster. Or maybe there is a way to flush conntrack on the event of pod deletion? Edit: Removed stupid idea of a workaround to disable conntrack for UDP. Can't disable conntrack for UDP because it's used for DNAT from node to container.\nThe workaround is to not use NodePorts. Other kinds of services are already correct.\nnot sure what you mean. I am seeing the issue with a LoadBalancer type so it does not affect NodePorts only. As a workaround I have created a small python script that watches the K8s API for pod deletions and clears the related conntrack entries when that happens. I can share it when I get to work on Monday if you want to try it out.", "commid": "kubernetes_issue_59368", "tokennum": 535}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b404923405e57657c259e765730a86215e884eef0194ef6fe0a4d8be20313979", "query": "t.Errorf(\"Expect command executed %d times, but got %d\", svcCount, fexec.CommandCalls) } } <ins> func TestClearUDPConntrackForPortNAT(t *testing.T) { fcmd := fakeexec.FakeCmd{ CombinedOutputScript: []fakeexec.FakeCombinedOutputAction{ func() ([]byte, error) { return []byte(\"1 flow entries have been deleted\"), nil }, func() ([]byte, error) { return []byte(\"\"), fmt.Errorf(\"conntrack v1.4.2 (conntrack-tools): 0 flow entries have been deleted\") }, func() ([]byte, error) { return []byte(\"1 flow entries have been deleted\"), nil }, }, } fexec := fakeexec.FakeExec{ CommandScript: []fakeexec.FakeCommandAction{ func(cmd string, args ...string) exec.Cmd { return fakeexec.InitFakeCmd(&fcmd, cmd, args...) }, func(cmd string, args ...string) exec.Cmd { return fakeexec.InitFakeCmd(&fcmd, cmd, args...) }, func(cmd string, args ...string) exec.Cmd { return fakeexec.InitFakeCmd(&fcmd, cmd, args...) }, }, LookPathFunc: func(cmd string) (string, error) { return cmd, nil }, } testCases := []struct { name string port int dest string }{ { name: \"IPv4 success\", port: 30211, dest: \"1.2.3.4\", }, } svcCount := 0 for i, tc := range testCases { err := ClearEntriesForPortNAT(&fexec, tc.dest, tc.port, v1.ProtocolUDP) if err != nil { t.Errorf(\"%s test case: unexpected error: %v\", tc.name, err) } expectCommand := fmt.Sprintf(\"conntrack -D -p udp --dport %d --dst-nat %s\", tc.port, tc.dest) + familyParamStr(utilnet.IsIPv6String(tc.dest)) execCommand := strings.Join(fcmd.CombinedOutputLog[i], \" \") if expectCommand != execCommand { t.Errorf(\"%s test case: Expect command: %s, but executed %s\", tc.name, expectCommand, execCommand) } svcCount++ } if svcCount != fexec.CommandCalls { t.Errorf(\"Expect command executed %d times, but got %d\", svcCount, fexec.CommandCalls) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-956c9b1270ab4e0eb744fb5e7c207e8e7b7c0a49e83c634550198bfe9b333eeb", "text": "I've my script . Note that it's not tested much so don't use it in a production environment. Also it cleans up all conntrack entries for a deleted pod, not only the UDP related ones.\nWe are also seeing this issue with type loadbalancer. We are on 1.11. Our use-case is the following: multiple devices are sending to an aggreagator machine. This machine forwards the UDP packages to a loadBalancer in gcp. When debugging the service, I noticed the following: The traffic is assigned to one pod, and the packages are not loadbalanced (client and server are the same cfr use-case) When redeploying a new cluster, Conntrack is cleared on termination signal of the old pod. (client receives connection refused) red/black and highlander deployment strategies have the same effect. How would I expect this to be working then? New cluster is . Conntrack is cleared Data is routed to NEW pods old pods are terminated Best Regards, Tim\nI am seeing this exact same issue on our cluster which has k8s v1.14.5 . We have endpoint nginx pods backing a UDP service with nodeport. Suddenly one day we see traffic not hitting into nginx pod but reaching the node hosting the nginx pod. We could simulate the problem by restarting the nginx pods. I am assuming with this issue marked as closed; and having made its way into v1.14; we should not be seeing this. Would also like to point out; the one thing, in addition we have in the service is ExternalTrafficPolicy set to Local. Can anyone please guide/help on why we are seeing this in v.1.14.5 of our cluster.\nSeeing this with k8s v1.16.5", "commid": "kubernetes_issue_59368", "tokennum": 391}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b47795c0ab3f44c72016f8b2f55103796171d6d1da611c35c00d395c7a95701e", "query": "g.updateRelistTime(timestamp) pods := kubecontainer.Pods(podList) <ins> // update running pod and container count updateRunningPodAndContainerMetrics(pods) </ins> g.podRecords.setCurrent(pods) // Compare the old and the current pods, and generate events.", "positive_passages": [{"docid": "doc-en-kubernetes-3f173d1022a4408031efac17c8299f04d835794ab8a77d69bb7667b0107a08bf", "text": "Some kubelet metrics use non-standard prometheus collectors unnecessarily. Specifically, we have which can be simple gauges. Since we cannot migrate non-standard prometheus collectors using the internal metrics stability framework, we will need to convert these metrics into standard prometheus variants. /sig instrumentation /assign\nGitHub didn't allow me to assign the following users: solodov. Note that only and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : Some kubelet metrics use non-standard prometheus collectors unnecessarily. Specifically, we have which can be simple gauges. Since we cannot migrate non-standard prometheus collectors using the internal metrics stability framework, we will need to convert these metrics into standard prometheus variants. /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\nrecommends that we generate those metrics in the GenericPLEG during the relist. We can generate the data directly from the pods call there ().\nI would be interested to work on this issue if no one else is working on it currently\nGo for it!\n/assign", "commid": "kubernetes_issue_79286", "tokennum": 282}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b477ec8df38ddd66d2e9bccb2d408ed511523b905c7b4c4285582d8be34d9c4d", "query": "return } <ins> if curPod.DeletionTimestamp != nil { // when a pod is deleted gracefully its deletion timestamp is first modified to reflect a grace period, // and after such time has passed, the kubelet actually deletes it from the store. We receive an update // for modification of the deletion timestamp and expect an ds to create more replicas asap, not wait // until the kubelet actually deletes the pod. dsc.deletePod(curPod) return } </ins> curControllerRef := metav1.GetControllerOf(curPod) oldControllerRef := metav1.GetControllerOf(oldPod) controllerRefChanged := !reflect.DeepEqual(curControllerRef, oldControllerRef)", "positive_passages": [{"docid": "doc-en-kubernetes-d34e56b4503184aafc2f81081d2e7d6ebfab0ded5a2f7a2bfd1277aaa2a8d441", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If this may be security issue, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: I have a daemonsets with 250 replicas and maxUnavailable is 20%. When I try to update its image, the ds will scale down 50 old replicas and wait for SatisfiedExpectations, after that it will scale up 50 new replicas. But if a pod delete failed (node is notready, and pod stuck at terminating status), ds controller will never reach the expectation and just stuck here. What you expected to happen: When a pod stuck at terminating, ds controller should start new pods like deployment controller, instead of waiting for the delete batch finish and ready for next poll. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Client Version: version.Info{Major:\"1\", Minor:\"8+\", GitVersion:\"v1.8.1-8+\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2017-10-25T13:04:04Z\", GoVersion:\"go1.8.3\", Compiler:\"gc\", Platform:\"linux/amd64\"} Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/sig apps /cc\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nDaemonSet controller waits for old pods to terminate before creating new ones for best-effort at-most-one pod per node. This is a deliberate design decision.", "commid": "kubernetes_issue_63465", "tokennum": 549}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b477ec8df38ddd66d2e9bccb2d408ed511523b905c7b4c4285582d8be34d9c4d", "query": "return } <ins> if curPod.DeletionTimestamp != nil { // when a pod is deleted gracefully its deletion timestamp is first modified to reflect a grace period, // and after such time has passed, the kubelet actually deletes it from the store. We receive an update // for modification of the deletion timestamp and expect an ds to create more replicas asap, not wait // until the kubelet actually deletes the pod. dsc.deletePod(curPod) return } </ins> curControllerRef := metav1.GetControllerOf(curPod) oldControllerRef := metav1.GetControllerOf(oldPod) controllerRefChanged := !reflect.DeepEqual(curControllerRef, oldControllerRef)", "positive_passages": [{"docid": "doc-en-kubernetes-3717eeb03a72e85e977fbd3018fc04b90903ed01af39ae113b30935dae199f29", "text": "In most cases, DaemonSets won't tolerate two pods scheduled on the same node at the same time; for example, it's common to communicate with DaemonSet pods via . I'm going to close this ticket as this works as designed. Please feel free to reopen the ticket if you think there are still issues to be resolved.\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nwhy does the DaemonSet controller wait for all pods 50 to be done, before moving to the NEXT 50 ? I completely understand that we want only at most 1 pod per node. But if a pod deletion fails on the node, move on to the next pod as long as the total unavailable pods are less than maxUnavailable. This will allow us to make progress in the face of bad nodes or failed pod deletions due to failing tear down of bad volumes or other reasons.\n/assign\nthoughts on this one ?\nAny progress on this issue? We also encountered this problem. There are thousands of nodes in our prod cluster and nodes often go down, which cause daemonset rolling update stucked, this problem really bother us.\nPTAL\n/reopen\nYou can't reopen an issue/PR unless you authored it or you are a collaborator. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nYou can't reopen an issue/PR unless you authored it or you are a collaborator. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_63465", "tokennum": 452}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b48a27ff52afc6aab4d6cc11b8d52521a495ca28733a090042ad1dfc0672d2ce", "query": "pm.mutex.Lock() defer pm.mutex.Unlock() <ins> if spec == nil { return nil, fmt.Errorf(\"Could not find plugin because volume spec is nil\") } </ins> matches := []string{} for k, v := range pm.plugins { if v.CanSupport(spec) {", "positive_passages": [{"docid": "doc-en-kubernetes-4cf2bcce2d9cf8bfbc9f2302c057ef4fa219c655a3340b1abe23f2bb07c57620", "text": "In volume management code, VolumeSpec is firstly needed to find the volume plugin. After the volume plugin is found, VolumeSpec is again used to attach or mount or check volume is still attached or not. This information is reconstructed during controller failure. The assumptions used here are If pod still exists, VolumeSpec should be reconstructed when controller is restarted. However, as discover from this bug, it might not be true if PVC is deleted in the meantime because pod only has PVC information and requires to use PVC to get PV information. By fixing Issue , we could fix this problem.If pod is already deleted, VolumeSpec is not really needed for detaching. But before detaching finishes, syncState loop might check this volume's attachement status and will use VolumeSpec during checking. One safe guard we can put here is to fail FindAttachablePluginBySpec if spec is nil. This function is used by multiple places such as attachdetachcontroller, desiredstateofworld, and actualstateofworld, oeperation_generator etc. Instead of adding nil check many places, I feel FindAttachablePluginBySpec or even better FindPluginBySpec (is called by FindAttachablePluginBySpec and other places). Open an issue for this\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close", "commid": "kubernetes_issue_49513", "tokennum": 492}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b4988f89391ff6df9f05f30353e3c10e002bfa50253ac5ede2a35236d81ceb50", "query": "i := rand.Intn(x.NumField()) fuzzer.Fuzz(x.Field(i).Addr().Interface()) <del> errs := validateNestedValueValidation(vv, false, false, nil) </del> <ins> errs := validateNestedValueValidation(vv, false, false, fieldLevel, nil) </ins> if len(errs) == 0 && !reflect.DeepEqual(vv.ForbiddenGenerics, Generic{}) { t.Errorf(\"expected ForbiddenGenerics validation errors for: %#v\", vv) }", "positive_passages": [{"docid": "doc-en-kubernetes-4be11de3bdb9e2a86ad3a19c4d6f5342db422d48e5979c118fca9ce077f64900", "text": "We allow CRD authors to write . Currently we don't restrict writing validation for , which means people can have . For example, people can have additive name constraints (require CR to be ) with the following schema: This brings us two questions: do we if \"metadata\" is included in the schema: simplest option is to publish standard metav1.ObjectMeta schema info, and use any CRD-specified \"metadata\" properties as additive validation (just like in-tree types do, publishing standard ObjectMeta schema info, and implementing type-specific name validation internally) alternatively, we can try merging user-specified metadata schema with the standard one. Technically people should only add extra validation to existing metadata properties (adding new fields to metadata won't work since they will be pruned by built-in validation first), but it's unclear to me how arbitrary people may want the metadata validation to be term question is whether to allow people specifying metadata validation at all, or just allow a subset (like name validation) in CRD v1 /sig api-machinery /area custom-resources cc\nWhat is the difference between these two? I mean the end result is the same right? The only thing that can be is validation. Nothing else works unless you are considering extensions?\nThe former means we drop/hide user-specified metadata schema when we publish CRD OpenAPI. We still validate user-specified constraints on server side, but client-side validation won't see them. The latter enables client-side user-specified metadata validation.\nIf it's possible to merge with standard metadata schema info, or at the cost of not publishing the standard schema. My inclination would be to publish the complete standard schema for metadata/apiVersion/kind, which we know is complete and accurate, and use and user-specified schema for those fields as addition validations server side", "commid": "kubernetes_issue_74620", "tokennum": 396}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b4b37cb100cdb4cc4bf472a77537b6d8ce750f1794915c33985116027acd3296", "query": "nm.registeredNodesLock.RLock() node := nm.registeredNodes[convertToString(nodeName)] nm.registeredNodesLock.RUnlock() <del> if node == nil { return v1.Node{}, vclib.ErrNoVMFound </del> <ins> if node != nil { klog.V(4).Infof(\"Node %s found in vSphere cloud provider cache\", nodeName) return *node, nil } if nm.nodeLister != nil { klog.V(4).Infof(\"Node %s missing in vSphere cloud provider cache, trying node informer\") node, err := nm.nodeLister.Get(convertToString(nodeName)) if err != nil { if !errors.IsNotFound(err) { return v1.Node{}, err } // Fall through with IsNotFound error and try to get the node from the API server } else { node := node.DeepCopy() nm.addNode(node) klog.V(4).Infof(\"Node %s found in vSphere cloud provider node informer\", nodeName) return *node, nil } </ins> } <del> return *node, nil </del> <ins> if nm.nodeGetter != nil { klog.V(4).Infof(\"Node %s missing in vSphere cloud provider caches, trying the API server\") node, err := nm.nodeGetter.Nodes().Get(context.TODO(), convertToString(nodeName), metav1.GetOptions{}) if err != nil { if !errors.IsNotFound(err) { return v1.Node{}, err } // Fall through with IsNotFound error to keep the code consistent with the above } else { nm.addNode(node) klog.V(4).Infof(\"Node %s found in the API server\", nodeName) return *node, nil } } klog.V(4).Infof(\"Node %s not found in vSphere cloud provider\", nodeName) return v1.Node{}, vclib.ErrNoVMFound </ins> } func (nm *NodeManager) getNodes() map[string]*v1.Node {", "positive_passages": [{"docid": "doc-en-kubernetes-b9a7a79272b4f05e986ec052f9f8348c60cffedf2d99a44ddafb98b4101b558f", "text": "I am enabling CSI migration on a vSphere cluster. A node was fully drained, all its Pods are deleted, but just before KCM detaches in-tree vSphere volume volumes from it, KCM restarts. A new KCM starts, sees attached volumes in that are not needed by any Pod on the node and calls vSphere in-tree volume plugin . The in-tree vSphere volume plugin + cloud provider marks the volume as detached right away, without reaching to vCenter API. The volume remains attached forever. I don't think it's related to CSI migration, IMO a regular node drain + KCM restart at the same time can cause the same issue. KCM logs: The in-tree cloud provider has a and from it. It apparently has not processed all nodes at the time A/D controller tries to detach the node. The in-tree vSphere volume plugin + cloud provider detaches the volume in vCenter. That's really tricky, it's very hard / impossible to reproduce on a real cluster. I had to inject errors to Detach() in-tree volume call, so they fail until KCM is restarted. Newly started KCM would detach the volume just fine (no error would be injected there), but marks the volume as detached right away. For the record (and search-ability), the CSI driver that tries to attach the volume to another node complains either: Or: cc It could be somewhat related to , however, not all cases of can be related to KCM restart. As I mentioned above, it's very hard/impossible to synchronize KCM restart with draining a node in a real cluster. <details</details<detailsvSphere 7.0.3 </details<details</details<detailsOpenShift </details<detailsCRI-O </details<details</details\n/sig storage\nTried just moving a Pod between nodes without CSI migration involved + restarting KCM when the volume is still attached to the old node. In-tree volume plugin on the new node says:\n/assign\nWhat CSI driver version and K8s version are you testing with?\nKubernetes is 1.25 and CSI driver is 2.7, still, I think it's not releated to the CSI driver, it's KCM who marks the in-tree volume as detached due to not populated node cache.", "commid": "kubernetes_issue_117091", "tokennum": 517}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b4b37cb100cdb4cc4bf472a77537b6d8ce750f1794915c33985116027acd3296", "query": "nm.registeredNodesLock.RLock() node := nm.registeredNodes[convertToString(nodeName)] nm.registeredNodesLock.RUnlock() <del> if node == nil { return v1.Node{}, vclib.ErrNoVMFound </del> <ins> if node != nil { klog.V(4).Infof(\"Node %s found in vSphere cloud provider cache\", nodeName) return *node, nil } if nm.nodeLister != nil { klog.V(4).Infof(\"Node %s missing in vSphere cloud provider cache, trying node informer\") node, err := nm.nodeLister.Get(convertToString(nodeName)) if err != nil { if !errors.IsNotFound(err) { return v1.Node{}, err } // Fall through with IsNotFound error and try to get the node from the API server } else { node := node.DeepCopy() nm.addNode(node) klog.V(4).Infof(\"Node %s found in vSphere cloud provider node informer\", nodeName) return *node, nil } </ins> } <del> return *node, nil </del> <ins> if nm.nodeGetter != nil { klog.V(4).Infof(\"Node %s missing in vSphere cloud provider caches, trying the API server\") node, err := nm.nodeGetter.Nodes().Get(context.TODO(), convertToString(nodeName), metav1.GetOptions{}) if err != nil { if !errors.IsNotFound(err) { return v1.Node{}, err } // Fall through with IsNotFound error to keep the code consistent with the above } else { nm.addNode(node) klog.V(4).Infof(\"Node %s found in the API server\", nodeName) return *node, nil } } klog.V(4).Infof(\"Node %s not found in vSphere cloud provider\", nodeName) return v1.Node{}, vclib.ErrNoVMFound </ins> } func (nm *NodeManager) getNodes() map[string]*v1.Node {", "positive_passages": [{"docid": "doc-en-kubernetes-27c84c169fad17ff032040ca08c7bb73c7215213dd29c5491da1ee415abb2a33", "text": "/assign\n/triage accepted\nI found an easier way how to reproduce this without extra code in KCM: a StatefulSet with 1 Pod that uses 1 PVC. the node where the Pod runs. down kube-controller-manager to zero (not really possible for me) or kill all kube-controller-manager Pods. This will cause new KCM processes to wait for leader election. In my env. this gives me ~30 seconds for the next step. Delete the Pod. A new one will be scheduled on a different node (because the current node is cordoned) + there is no KCM running at this time that would detach the volume from the old node. KCM wins its leader election, sees a volume attached to a node where it is not needed -it calls of the volume plugin. VSphere cloud provider does not have its caches populated yet (= this bug) -the volume is not detached, but returns success.\ndangling attach does not help here. The volume is still attached to the old node even after ~10 minutes. fails with and not with . I can see there is a lot of dangling attach code in the cloud provider, but I did not debug further.", "commid": "kubernetes_issue_117091", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b4c3ff8eb671ad7afdecf19fd4932e054eeaa5188105c916c973916ed82efc25", "query": "package util import ( <ins> \"math/rand\" \"runtime\" </ins> \"sync\" \"testing\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-0882877f8aa87dd9f2fab7aa6c2163d630c073e98d0481f7c1762728faaae3b6", "text": "Failed due to an apparently unrelated PR: https://travis-\nProblem here is that I left a small chance of a double-call in my parallelized cache. Didn't realize this was being tested. Will fix.", "commid": "kubernetes_issue_3439", "tokennum": 46}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b4c873b5a9fce33ac41de07a9f77af381be3be424ea6cdcd41839286fe32a391", "query": "dirMode         = \"dir_mode\" gid             = \"gid\" vers            = \"vers\" <del> defaultFileMode = \"0755\" defaultDirMode  = \"0755\" </del> <ins> defaultFileMode = \"0777\" defaultDirMode  = \"0777\" </ins> defaultVers     = \"3.0\" )", "positive_passages": [{"docid": "doc-en-kubernetes-b91639c622bb64c70a52cad670c2f62bee84a1358c20408d54f6229d98acd356", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Default azure file permission is not suitable for most users, dozens of users complain about this, set as is the best choice here, if users don't want , then they could use mountOptions to override and . What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.12 Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: /sig azure /assign", "commid": "kubernetes_issue_69853", "tokennum": 184}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b4e3512cb79b947656cba5e5237a5e90c520421e044aad820ba60ef6d5b80799", "query": "return \"\", err } <ins> pc := d.Core().Pods(namespace) mountPods, err := getMountPods(pc, pvc.Name) if err != nil { return \"\", err } </ins> events, _ := d.Core().Events(namespace).Search(legacyscheme.Scheme, pvc) <del> return describePersistentVolumeClaim(pvc, events) </del> <ins> return describePersistentVolumeClaim(pvc, events, mountPods) } func getMountPods(c coreclient.PodInterface, pvcName string) ([]api.Pod, error) { nsPods, err := c.List(metav1.ListOptions{}) if err != nil { return []api.Pod{}, err } var pods []api.Pod for _, pod := range nsPods.Items { pvcs := getPvcs(pod.Spec.Volumes) for _, pvc := range pvcs { if pvc.PersistentVolumeClaim.ClaimName == pvcName { pods = append(pods, pod) } } } return pods, nil </ins> } <del> func describePersistentVolumeClaim(pvc *api.PersistentVolumeClaim, events *api.EventList) (string, error) { </del> <ins> func getPvcs(volumes []api.Volume) []api.Volume { var pvcs []api.Volume for _, volume := range volumes { if volume.VolumeSource.PersistentVolumeClaim != nil { pvcs = append(pvcs, volume) } } return pvcs } func describePersistentVolumeClaim(pvc *api.PersistentVolumeClaim, events *api.EventList, mountPods []api.Pod) (string, error) { </ins> return tabbedString(func(out io.Writer) error { w := NewPrefixWriter(out) w.Write(LEVEL_0, \"Name:t%sn\", pvc.Name)", "positive_passages": [{"docid": "doc-en-kubernetes-b97e647702b8859b86e9b0127fc694e7b8feffe09fe2ccd8837b28995c7af595", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: I need to know to which Pod(s) a PVC is being mounted to, without having to go through each Pod one by one checking the Volume mounts and the PersistentVolumeClaim. The kubectl describe pvc and get pvc, only tell you to which Persistent Volume the PVC is bound to, but not if is being used by a Pod(s) What you expected to happen: Add a new field in the describe or get that lists the pods that are using the PVC as a volume mount How to reproduce it (as minimally and precisely as possible): Have a PV/PVC bound and create a pod using a volume mount Anything else we need to know?: Not sure if this is only for Azure Disk, which is the Storage Class I am using. Environment: Kubernetes version (use ): 7 Cloud provider or hardware configuration: Azure OS (e.g. from /etc/os-release): Ubuntu 16.04 Kernel (e.g. ): 4 Install tools: Azure Kubernetes Services Others: -n/a\n/sig storage\n/sig cli\nI think the kubectl describe can just construct this on the fly. Another angle is should we add this information to PVC object itself\nThat will be great, as right now the only way to correlate a PVC to a Pod is via a \"describe\" on the Pod.\nI can work on a PR for this!\nGitHub didn't allow me to assign the following users: clandry94. Note that only and repo collaborators can be assigned. <detailsIn response to : I can work on 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\n+1 for the feature. cc\nHow to find \"what pods are using particular PVC through command line\"\n+1 for the feature.\nthis feature will be in Kubernetes 1.12\nok kubernetes 1.12 released, how to? which command?\nCan someone point to the documentation or paste command to get the pods which have the PVC in use\nsee the associated PR to see an example usage of this The line in should show it.\nWorkaround for the meantime:\nThanks , this workaround is great for those people who still use old kubernetes version.", "commid": "kubernetes_issue_65233", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b4e3512cb79b947656cba5e5237a5e90c520421e044aad820ba60ef6d5b80799", "query": "return \"\", err } <ins> pc := d.Core().Pods(namespace) mountPods, err := getMountPods(pc, pvc.Name) if err != nil { return \"\", err } </ins> events, _ := d.Core().Events(namespace).Search(legacyscheme.Scheme, pvc) <del> return describePersistentVolumeClaim(pvc, events) </del> <ins> return describePersistentVolumeClaim(pvc, events, mountPods) } func getMountPods(c coreclient.PodInterface, pvcName string) ([]api.Pod, error) { nsPods, err := c.List(metav1.ListOptions{}) if err != nil { return []api.Pod{}, err } var pods []api.Pod for _, pod := range nsPods.Items { pvcs := getPvcs(pod.Spec.Volumes) for _, pvc := range pvcs { if pvc.PersistentVolumeClaim.ClaimName == pvcName { pods = append(pods, pod) } } } return pods, nil </ins> } <del> func describePersistentVolumeClaim(pvc *api.PersistentVolumeClaim, events *api.EventList) (string, error) { </del> <ins> func getPvcs(volumes []api.Volume) []api.Volume { var pvcs []api.Volume for _, volume := range volumes { if volume.VolumeSource.PersistentVolumeClaim != nil { pvcs = append(pvcs, volume) } } return pvcs } func describePersistentVolumeClaim(pvc *api.PersistentVolumeClaim, events *api.EventList, mountPods []api.Pod) (string, error) { </ins> return tabbedString(func(out io.Writer) error { w := NewPrefixWriter(out) w.Write(LEVEL_0, \"Name:t%sn\", pvc.Name)", "positive_passages": [{"docid": "doc-en-kubernetes-d7becb5323d04fe79bf1f030fc587d9b0aefb9105f1724f943828245df0352e1", "text": "However it will meet an error if the pod have no volumes, so I improves it by adding a to check whether the volumes exists or not.\npython script to list pods with pvc in namespace(s): Is a part of a cli to set pods with velero/restic annotations. Hope it helps someone :)\nFor posterity... There is a Used By: field in the output of describe.\nclient-go didn't give this api... ,PodPVCIndex can solve the problem\nHi thanks worked for me ;) but I want to make it reverse my workarounds with adding after didn't worked do you have any ideas\n$ kubectl describe pvc -A Used\" Name: ocs-deviceset-lso-volumeset-0-data-1b45dn Namespace: openshift-storage StorageClass: lso-volumeset Used By: rook-ceph-osd-1--8fwpd Also useful ^\nthe reason it didn't work is because each return does, in point of fact, have a key defined for claimName. That key is just set to null value. So, what you'd actually want to do is test for nulls. As nice as answer is, it's a PITA to parse unstructured human-readable command output, as opposed to command output in a markup language that well known shell parsers like jq and yq can work with. Towards that end, because I had use of this, I came up with the following: That simple not null test at the end plucks out all your nulls. Obviously invert the last conditional if you want all the nulls, but you'll get all sorts of temp things that way that you probably won't care about.", "commid": "kubernetes_issue_65233", "tokennum": 387}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b50d7789d2d038980826a3ed2825714d157b6879e64a74aa3a718a81b4c09672", "query": "<ins> This file is autogenerated, but we've stopped checking such files into the repository to reduce the need for rebases. Please run hack/generate-docs.sh to populate this file. </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-3c17ea4b4f4a9bb23915ee9fbb41703ef0532ac00becc05b8dda4d23a9ea9da2", "text": "As the RBAC role need to be related to resources. I think we could use a command to get the supported resources. ref to\nThis would be cool.\nI thought we a command that listed resources in the discover doc a long time ago.\nis just the versions, but principle is the same. We want to list all the types, their resources, and tie that back to \"explain\".\nWhat's the best way to determine this information currently? I'm having difficulty figuring out the exact set of permissions (and how they would be written in an RBAC role) for any given kubectl command. The documentation for this right now is split across multiple places and certain things are not explained at all. Specifically, it's difficult to determine which \"API verb\" is used for which operations. Take as an example. It's unclear if the way to allow this is to use the \"proxy\" subresource of a pod or service with \"get\"/\"create\"/etc. verbs, or to use the \"proxy\" verb with the resource (pod, service) directly. is a similar case. The almost works for this purpose, but it's still difficult. Operations for a given resource are grouped into categories like write, read, status, and proxy, but these things don't obviously correlate with API verbs. Again, proxy is especially confusing as there is no mention of a proxy \"verb\". The API operations are only shown using their HTTP verbs. One thing that could help on this document would be a section on the right column under \"kubectl command\" that shows exactly the rule needed in an RBAC role to allow this command via kubectl. And even then, that assumes an exact 1-to-1 mapping between API endpoints and kubectl commands, which I doubt is always the case. (For example, port fowarding to a pod seems to require both a GET on the pod resource and a CREATE on a port forward subresource.) There also needs to be better documentation about how this information could have been determined in the first place. I've resorted to manually looking through API requests made with but even then it's difficult to figure out. Amusingly, I was the one who wrote which is referenced in the original issue description (as well as the table explaining verbs in ).", "commid": "kubernetes_issue_42932", "tokennum": 494}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b50d7789d2d038980826a3ed2825714d157b6879e64a74aa3a718a81b4c09672", "query": "<ins> This file is autogenerated, but we've stopped checking such files into the repository to reduce the need for rebases. Please run hack/generate-docs.sh to populate this file. </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-20fd632aaf82ba3efee7609ebeda29ca6df3199abf73ef8bcfe417660974a0ce", "text": "tl;dr: It's too difficult right now to go from \"I want a user to be able to run \" to \"here is the RBAC rule to use for that\" for any case where there isn't a specific example shown in the docs.\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nIt seem that relative PR stop updated. If this issue still valuable, i will help fix it\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close", "commid": "kubernetes_issue_42932", "tokennum": 279}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b51a6f6ad150d42c3ad2c2aac15dafd3233c0e6c88413c75cde1e341a9077c5d", "query": "// prior to final deletion, we must ensure that finalizers is empty if len(namespace.Spec.Finalizers) != 0 { <del> err = fmt.Errorf(\"Unable to delete namespace %v because finalizers is not empty %v\", namespace.Name, namespace.Spec.Finalizers) </del> <ins> err = fmt.Errorf(\"Namespace %v termination is in progress, waiting for %v\", namespace.Name, namespace.Spec.Finalizers) return nil, err </ins> } return r.Etcd.Delete(ctx, name, nil) }", "positive_passages": [{"docid": "doc-en-kubernetes-859a8b847337ca2cf9879726f3bdb71f0db5559ee2589591ceae612e41f71a1b", "text": "There is a funny subtle behvaiour in get namespaces, in which if i call more than one time, it seems that the removal from Terminating state is accelarated. It seems this might indicate a bug, or maybe its not a bug and the eventual semantics of is a little funny sometimes. in any case, here's what we are seeing : 1) when i delete a namespace the first time usning kubectl, we get a state change to . that is correct, of course. 2) but ... if make the call a second time, then the same status line is immediately removed from . Expected behaviour : A second call to \"kubectl delete ...\" shouldn't have any effect on the timing of removal of a namespace from 'Terminating' state*... So i guess there is some \"eventual consistency\" subtle bug that is resolved by repeated calls to\nsuggests this may not be e bug, maybe its just the etcd eventual deleter thingy.\nLooks to definitely be a bug. The 2nd delete seems to have interrupted the delete process and artifacts (like events) from the namespace still exist in etcd.\ninvestigating...\noops, see the error, will submit a fix.\nI have a fix, but need a test case, will submit PR tomorrow AM", "commid": "kubernetes_issue_6633", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b523346162c6261eba71ca156b6922bc66525fd693841794037c38fb91113385", "query": "return plugin.getFakeVolume(&plugin.Detachers), nil } <ins> func (plugin *FakeVolumePlugin) GetDetachers() (Detachers []*FakeVolume) { plugin.RLock() defer plugin.RUnlock() return plugin.Detachers } </ins> func (plugin *FakeVolumePlugin) GetNewDetacherCallCount() int { plugin.RLock() defer plugin.RUnlock()", "positive_passages": [{"docid": "doc-en-kubernetes-8eb466904f09832d9690a82d180fa467ae255966eba3f5f112ba1d2e4e87f745", "text": "Looks like similar issue with\nThat's the PV controller this is the attach controller, thus separate issues.", "commid": "kubernetes_issue_26377", "tokennum": 21}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b52b961f16b926b2983d16c6f6bb09df973754943ab612903195c190fedcd54a", "query": "} if test.expectFailure { err = waitForResizingCondition(pvc, m.cs, csiResizingConditionWait) <del> gomega.Expect(err).To(gomega.HaveOccurred(), \"unexpected resizing condition on PVC\") </del> <ins> framework.ExpectError(err, \"unexpected resizing condition on PVC\") </ins> return }", "positive_passages": [{"docid": "doc-en-kubernetes-c082543f1889f90c5ee780d309eeb8f41ee57a7e9e8bb6b6fe7c2e4381ff48af", "text": "What happened: After fixing golint failures under (now still in progress), we need to put for each and . Then common error checking code has become like: We can replace this code with which is more readable and easy to be understood what the code does. Now we have following e2e test directories which can be replaced: [x] test/e2e/apimachinery/ () [x] test/e2e/apps/ () [x] test/e2e/auth/ () [x] test/e2e/common/ () [x] test/e2e/node/ () [x] test/e2e/storage/ () [x] () [x] () [x] () [x] () [x] () [x] () [x] [x] test/e2e/storage/persistentvolumes- [x] () [x] () [x] [x] [x] [x] [x] ()\n/sig testing /kind cleanup\n/assign PR will be submitted soon.\nFix the following in\nFix in\nFix in\nHi, maybe I could take files beneath test/e2e/storage/vsphere/\noops, I'm finished and prepare for PR.\nThank you That's OK\nFix the following in\n/assign\nAll related PRs were merged. I think this ticket can be closed. BTW, should we also replace to ?\nThanks for your work. thing is managed with We are almost finishing the work also :-)\n/remove-kind bug\nI found in these files. I'm working on :\nI can work to the following item.", "commid": "kubernetes_issue_77706", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b568f14d52771e039418054ee41d52cffa2695f05ea7fbbe0a29e218e25bb50a", "query": "// TODO: we should consider merge this struct with GroupVersion in unversioned.go type APIVersion struct { // Name of this version (e.g. 'v1'). <del> // +optional </del> Name string `json:\"name,omitempty\"` }", "positive_passages": [{"docid": "doc-en-kubernetes-65858ef6270e846dbad645a3cdb03be72308acbcbd2d437380bbe522248f5825", "text": "FYI. Currently the field of TPR is marked as which is wrong, actually if you try to create a TPR with empty versions, it will cause api server panic. Versions should be necessary field of TPR, we should validate this somehow.", "commid": "kubernetes_issue_36991", "tokennum": 52}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b570092a18aaa77995c5e00a3b378ede62e7670ff7e3777eb0cd1d8536d5df79", "query": "if err != nil { t.Fatalf(err.Error()) } mounts, volPath, subPath, err := test.prepare(base) if err != nil { os.RemoveAll(base)", "positive_passages": [{"docid": "doc-en-kubernetes-ea06bb5e10f9c1a3c6e6bdd4b05e49a63cf7c6313178f3d65784c243007cbe65", "text": "Subpath unix socket tests can flake because of long socket path. On Linux the path limit should be 108 chars or less. /sig storage", "commid": "kubernetes_issue_61844", "tokennum": 31}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b57431ae15296f6ae90fe79a2e1f95582f5dc923bcecdded1507f95e21766ca6", "query": "readinessProbe := &v1.Probe{ Handler:             execHandler([]string{\"/bin/cat\", \"/tmp/health\"}), InitialDelaySeconds: 0, <del> PeriodSeconds:       60, </del> <ins> // PeriodSeconds is set to a large value to make sure that the first execution of readiness probe // will happen before the first period passed. PeriodSeconds: 600, </ins> } startupProbe := &v1.Probe{ Handler:             execHandler([]string{\"/bin/cat\", \"/tmp/startup\"}),", "positive_passages": [{"docid": "doc-en-kubernetes-17394de51a0297c3b5009d62fc651309bc0945a0e851cb08a887385f3706124d", "text": "<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI --Seems to be impacting a few KIND jobs on the master branch the most, but also assorted other jobs see the triage link above Reported by Sample failure: /sig node <!-- Please see the deflaking doc () for more guidance! --\nxref probing tests\n/assign ref /triage accepted\nThanks Elana, still trying today... Does anyone know if we can use the kubelet logs in e2e tests?\nNot very portably in cluster e2e tests at least. Maybe in node_e2e instead.\nHave you considered that the issue is not with the test but with the underlying code in kubelet like detailed in this issue Like detailed in the issue I can reliably reproduce (on k8s 1.18) the startup probe passing within a few seconds, but the container is only marked as ready after about a minute.\nthere is already a fix in the 1.21 release for that (part of a bigger PR): And actually this test was to verify that part of the code, but unfortunately sometimes it doesn't respond as quick as it should (but never on my PC, only in ci/cd tests)...\nSome recent flakes:\none of the most common flakes in kind jobs currently failures like: Mar 25 17:03:42.508: Pod became ready in 42.007286524s, more than 5s after startupProbe succeeded. It means that the delay readiness probes were not initiated immediately after startup finished.\nMaybe we could speed up the review on\nThank you I will take a look. I'm making a pass through flakes tonight trying to identify if anything is on kind's end\nI don't think it's kind... since running on my PC with kind it works 100%, I think the issue is either the resources... or contention in the queue as mentioned to in the comment\n/milestone v1.22\ncommented on PR with the suggested fix\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository.", "commid": "kubernetes_issue_99979", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b57431ae15296f6ae90fe79a2e1f95582f5dc923bcecdded1507f95e21766ca6", "query": "readinessProbe := &v1.Probe{ Handler:             execHandler([]string{\"/bin/cat\", \"/tmp/health\"}), InitialDelaySeconds: 0, <del> PeriodSeconds:       60, </del> <ins> // PeriodSeconds is set to a large value to make sure that the first execution of readiness probe // will happen before the first period passed. PeriodSeconds: 600, </ins> } startupProbe := &v1.Probe{ Handler:             execHandler([]string{\"/bin/cat\", \"/tmp/startup\"}),", "positive_passages": [{"docid": "doc-en-kubernetes-e379199dcc10ef545e6719d9fd62c8045ba08caeee0b4e30e1a8cba90abc8ed8", "text": "</details\nYeah...\nThanks for your great work in keeping things in check\nFYI\nI have (finally) understood what's happening, and I can even explain why the deflake made things worse... Please have a look at the sleep before the worker starts to process probes: So, you have to remember that we have one worker per pod and per probe, and since we have these probe settings for the test: We have (PeriodSeconds=10) starting sometimes immediately (if the Kubelet has started since more than 10s) or after a quick sleep of rand10s. On the contrary, will likely sleep most of the time for rand60s. This causes a delay in the processing of notifications: If we are lucky, this delay is less than 5s and the test passes: Now you can understand why the deflaked settings were actually worse:\nThe reason I didn't spot these was that I usually start my cluster once for all and iterate on the tests... so the kubelet had plenty of time to start and I never ended in that sleep.\nFor the solution, I suggest we either remove the sleep completely, or we find something that would make all 3 probe workers start at the same time to avoid sync issues... For the record, I was able to spot this issue thanks to the following log error (because the channel was overflowing): What do you think ?\nI have found another issue in that code: If has already ran (and failed), we go to L245 and don't probe via and therefore wait for the next tick, making the test fail.\nThis seems consistent with what I found when I was adding e2es for the new probe-level termination grace period and why I did my timing math the way I did.\n/reopen I don't think this is fixed, I just hit it again and gubernator is still showing plenty of flakes:\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nhow to check the exact commit used for each test?", "commid": "kubernetes_issue_99979", "tokennum": 462}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b57431ae15296f6ae90fe79a2e1f95582f5dc923bcecdded1507f95e21766ca6", "query": "readinessProbe := &v1.Probe{ Handler:             execHandler([]string{\"/bin/cat\", \"/tmp/health\"}), InitialDelaySeconds: 0, <del> PeriodSeconds:       60, </del> <ins> // PeriodSeconds is set to a large value to make sure that the first execution of readiness probe // will happen before the first period passed. PeriodSeconds: 600, </ins> } startupProbe := &v1.Probe{ Handler:             execHandler([]string{\"/bin/cat\", \"/tmp/startup\"}),", "positive_passages": [{"docid": "doc-en-kubernetes-1225e4b3fb518feb838b0b4898217ee9b18190e72a1e6684a1b960954bc011fd", "text": "For instance, I am not sure (from the name) that should include my latest fix...\nIn your PR the fix wasn't there:\nyou may send cherry-pick to 1.21 for which is using kubelet 1.21, not 1.22.\nis using kubelet. Cherry-pick to 1.20 may be needed as well.\nI have found this one that failed even with the fix: corresponding to:\nI don't know what could explain this atm... but it seems we still have delay propagating container statuses.\nIn the job artifacts there are multiple places with this info including the clone records/logs, and In testgrid it's a row.\nyeah afaict since the tests ran on my PR after your fix was merged into master, it showed the flake was still present :( Prow will always use the latest master when running CI.\nSorry for doubting what you said... I was probably in deny and hoped this annoyance was fixed once for all :(\nPlan: we'll see if Clayton's pod lifecycle refactor and/or the jitter refactor for probes affects this.\nClayton's PR jitter refactor\nsince isn't (likely) coming to 1.22 we could cut off 90% of flakes by increasing to 15s delay:\nit seems it fails even after merging so let's continue our discussion on slack\nthis is not a regression, our suggestion is not block release on it. feel free to remove the milestone\n/milestone v1.23\nIn Kubelet maybe, but in the flakiness of the e2e tests it was. Unfortunately we can't easily explore the current state :/\nIn the release blocking jobs the frequency is not horrible now, so unblocking is probably fine, it is not as bad as it was. Outside of the release cycle this is still the flakiest test in some jobs, see e.g. where it's the only flake source we have on record currently.\nif we end up needing it, we have a timing/period adjustment PR we can take that should help with the flakiness with", "commid": "kubernetes_issue_99979", "tokennum": 451}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b589a3169e02c1097257359b4f95fd09f5319a70b544edb41b1960eae6fb1150", "query": "It(\"should lookup the Schema by its GroupVersionKind\", func() { schema = resources.LookupResource(gvk) Expect(schema).ToNot(BeNil()) <del> }) var deployment *proto.Kind It(\"should be a Kind\", func() { deployment = schema.(*proto.Kind) Expect(deployment).ToNot(BeNil()) </del> <ins> Expect(schema.(*proto.Kind)).ToNot(BeNil()) </ins> }) })", "positive_passages": [{"docid": "doc-en-kubernetes-828b2f2bc9a1c73b1b130d20e1091ab566168df681bda6f542cc66f3f230828b", "text": "/kind failing-test <!-- If this is a flake, please add: /kind flake --<!-- Please assign a SIG using: /sig SIG-NAME --\n/sig cli\nThere may have two issues to fix: doesn't support run with assertion must check whether schema is nil first\n/assign\n/triage accepted", "commid": "kubernetes_issue_106761", "tokennum": 80}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b5ab3943fc6c32d5b7b62be21a7b7bdabd34f6dfc6111ede94eded25c53f8712", "query": "// scan /var/lib/kubelet/pods/<uid>/volume-subpaths/<volume>/<container name>/* fullContainerDirPath := filepath.Join(subPathDir, containerDir.Name()) <del> err = filepath.Walk(fullContainerDirPath, func(path string, info os.FileInfo, _ error) error { </del> <ins> // The original traversal method here was ReadDir, which was not so robust to handle some error such as \"stale NFS file handle\", // so it was replaced with filepath.Walk in a later patch, which can pass through error and handled by the callback WalkFunc. // After go 1.16, WalkDir was introduced, it's more effective than Walk because the callback WalkDirFunc is called before // reading a directory, making it save some time when a container's subPath contains lots of dirs. // See https://github.com/kubernetes/kubernetes/pull/71804 and https://github.com/kubernetes/kubernetes/issues/107667 for more details. err = filepath.WalkDir(fullContainerDirPath, func(path string, info os.DirEntry, _ error) error { </ins> if path == fullContainerDirPath { // Skip top level directory return nil", "positive_passages": [{"docid": "doc-en-kubernetes-e7fba9d64f1431a5cdd542cd6f9cce6e6a943bdeb7b1334304ccc5bcf3efb9f5", "text": "I ran a deployment with replicas 1 and use to set container's subpath dir, which uses NFS as the storage backend, and create about dirs in container's subPath dir,when delete the pod, it spent much more time to end status, and when the replicas increase to 10 and do the rolling update, at the same time dir nums in containers increase to , it spent about 30 minutes to totally remove pod, which is intolerant. The pod is deleted fast. a pod using subPathExpr as the volume mount. dirs in the backend storage corresponds to the container volume mount the pod kubelet log We can find that it spent about 17s to clean the mount dir in kuelet. No response <details</details<details</details<details</details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nAfter some debugging, I inspected the pprof with flame graph when delete a pod, it shows that and cost much more time, here is the graph: ! Apparently the Walk func spent much time when doCleanPath, what we care is the top level dir,and this pr has some fast path to avoid much recursive time, but before gol1.16, the filepath.Walk is still less efficient, because when used in kubelet, it reads all the dir in the mount point before call the callback func in Walk even we don't use it after that, so it spends much time. And after go 1.16, filepath.WalkDir is introduced, which is more efficient than Walk, as the comment said in golang WalkDirFunc is called before reading a directory, so it can save much time when there are lots of dirs in the first level of mount points. So it's time wasting and meaningless when we use Walk so far because we traverse the dir but we didn't use it and return SkipDir err, the code is After I replaced it with , the took only about 41ms, which is a huge boost than 17s before.", "commid": "kubernetes_issue_107667", "tokennum": 529}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b5b8ebe493cbf1754a46685c191cc65ad51e107012876da1fe410ea29ec1e2ca", "query": "// compute the context. Mutation is not allowed. ValidatedPSPAnnotation is used as a hint to gain same speed-up. allowedPod, pspName, validationErrs, err := p.computeSecurityContext(ctx, a, pod, false, pod.ObjectMeta.Annotations[psputil.ValidatedPSPAnnotation]) if err != nil { <del> return admission.NewForbidden(a, err) </del> <ins> return admission.NewForbidden(a, fmt.Errorf(\"PodSecurityPolicy: %w\", err)) </ins> } if apiequality.Semantic.DeepEqual(pod, allowedPod) { key := auditKeyPrefix + \"/\" + \"validate-policy\"", "positive_passages": [{"docid": "doc-en-kubernetes-d654f914f6cdd0bd3bce5db6eb3c4ebef631bd8d2558ac9d591cab12ba724061", "text": "What happened: e2e tests detect whether PSP is enabled based on presence of PSP API objects. An addon that proactively includes a PSP in a manifest can trigger that detection and enable PSP-specific e2e tests that should not be run. What you expected to happen: In addition to detecting presence of PSP objects, consider dry-run creating a pod and verifying the annotation indicating the selected PSP policy is , indicating the admission plugin is active. /sig auth /assign", "commid": "kubernetes_issue_91463", "tokennum": 109}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b5d71dc301c1e0e5044a4a2acc16931ae86d90d51a9c6ee5b117566298773cae", "query": "// owner: @derekwaynecarr // alpha: v1.20 <ins> // beta: v1.22 </ins> // // Enables kubelet support to size memory backed volumes SizeMemoryBackedVolumes featuregate.Feature = \"SizeMemoryBackedVolumes\"", "positive_passages": [{"docid": "doc-en-kubernetes-2270f3670748d4dd417a0804239a121b559b1166e20ffa4186cfbb1c59e670cb", "text": "When master opens up for , we need to add this back in: /sig node\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nnote to self / 1.21 and 1.22 release notes team -- let's make sure the PR body on the original PR is copied over to the new PR. will think that the old release note and documentation has been covered in 1.21, but we will (I will update this comment with link) manually override it to not show up in 1.21 release notes.", "commid": "kubernetes_issue_100371", "tokennum": 184}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b5e3187f3db0947ca19d7333766de3ad10657cbd296b36bc3e424933ece7ff35", "query": "\"net/url\" \"reflect\" \"strings\" <ins> \"sync/atomic\" </ins> \"testing\" \"golang.org/x/net/websocket\"", "positive_passages": [{"docid": "doc-en-kubernetes-dde8d0812f4d036029fc33418cfa6f164f8f025662aa48e3db09b87dd15763e4", "text": "There are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig api-machinery", "commid": "kubernetes_issue_49413", "tokennum": 102}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b5f51ef5158cdfdf3d9e09e230a1b51ced03375d10bcc6b5bd82cf0282526f3e", "query": "if !ignoreChangesAndAdditions { // Add any remaining items found only in modified for ; modifiedIndex < len(modifiedSorted); modifiedIndex++ { <del> patch = append(patch, modified[modifiedIndex]) </del> <ins> patch = append(patch, modifiedSorted[modifiedIndex]) </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-a9efceceb9be4ec0ae924972e4a207288eddcc2b046c2722d13a8ac3250be7d4", "text": "Deployment is defined in a json file with several environment varibles. Deployment is deployed using \"kubectl apply -f \". Pods get most of the environment variables defined, but not all. Specifically, the variables defined in the are named: { \"name\": \"DBHOSTS\", \"value\": \"10.0.0.1\" }, { \"name\": \"SLACKENDPOINT\", \"value\": \"ERRORNOT\" }, { \"name\": \"LACKENDPOINT\", \"value\": \"ERRORNOT\" }, { \"name\": \"SLACK\", \"value\": \"ERRORNOT\" }, { \"name\": \"CKENDPOINT\", \"value\": \"ERRORNOT\" }, { \"name\": \"ACKENDPOINT\", \"value\": \"ERRORNOT\" }, { \"name\": \"KENDPOINT\", \"value\": \"ERRORNOT\" }, { \"name\": \"CASSANDRALOGGINGLEVEL\", \"value\": \"ERROR\" }, { \"name\": \"ENABLEGETIP\", \"value\": \"\" } the environment variables that appear in a pod are: ENABLEGETIP CASSANDRALOGGINGLEVEL KENDPOINT ACKENDPOINT CKENDPOINT DBHOSTS That is, ENV variables named \"SLACKENDPOINT\", \"LACKENDPOINT\" and \"SLACK\" never get passed on to the pods.\nIt also won't accept \"randomshit\" as an environment varible. When I add that as an environment variable to an existing deployment and run \"kubctl apply -f \" nothing happens. This is on version v1.2.4 /\nEhh? Can you post a full but minimized yaml that I can run to reproduce it? , drashkov wrote:\nWe use JSON files, here is the full one. \"SLACK_ENDPOINT\" does not appear as an environment variable in the pods. Doing \"kubectl apply -f \" does not create new pods, and does not pass these variables to the pods. If I change the number of replicas and add a new pod, that pod will be created, but won't have that varible.\nI am not able to reproduce on GKE at 1.2.4 when exec'ing into one of the Pods and printing the environment. This is the yaml I used - note the image is different: What are the symptoms you are seeing?", "commid": "kubernetes_issue_25585", "tokennum": 520}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b5f51ef5158cdfdf3d9e09e230a1b51ced03375d10bcc6b5bd82cf0282526f3e", "query": "if !ignoreChangesAndAdditions { // Add any remaining items found only in modified for ; modifiedIndex < len(modifiedSorted); modifiedIndex++ { <del> patch = append(patch, modified[modifiedIndex]) </del> <ins> patch = append(patch, modifiedSorted[modifiedIndex]) </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-88cd42fc07ef7063636f75ce8fb36b9d8d96cd9dd28f579d99991871766445e3", "text": "Can you provide yaml using standard public image along with the specific symptoms you are seeing?\ndid you create the deployment first with out the env vars, then add them via an apply?\nThanks for looking into it I managed to reproduce it with the yaml you posted. Here's what I did: the yaml you provided as '' the \"SLACKENDPOINT\" env var from that file and saved that as \"\" (no other changes) This creates the deployment with all env vars as expected This re-creates a new set of pods and they don't have the SLACKENDPOINT var, as expected. This does not re-create the pods, so the env var is not passed along. kubectl does not return errors.\ncc cc\nThanks, I was able to reproduce the issue. It looks like the config with the ENV does get stored in the last-applied-configurations annotation: But does not get put into the pods:\nAfter a few tries I found that if you add the env as the last one you'll be able to add it. Definitely a bug.\nThe generated three way merge patch wasn't correct (the annotation is good, but look at the spec part): \"spec\":{\"template\":{\"spec\":{\"containers\":[{\"env\":[{\"name\":\"CASSANDRALOGGING_LEVEL\",\"value\":\"ERROR\"}],\"name\":\"test-api\"}]}}}}\nIt only recognizes the last env as diff\nOpened a PR ptal.\nThanks everyone.", "commid": "kubernetes_issue_25585", "tokennum": 344}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b60bc5190c11a1b0aaa08e97a45cb529b9f5ea2fdaca2a0378b7d7ac3fc4b44e", "query": "} } } <ins> func TestGetWindowsPath(t *testing.T) { tests := []struct { path         string expectedPath string }{ { path:         `/var/lib/kubelet/pods/146f8428-83e7-11e7-8dd4-000d3a31dac4/volumes/kubernetes.io~disk`, expectedPath: `c:varlibkubeletpods146f8428-83e7-11e7-8dd4-000d3a31dac4volumeskubernetes.io~disk`, }, { path:         `var/lib/kubelet/pods/146f8428-83e7-11e7-8dd4-000d3a31dac4volumeskubernetes.io~disk`, expectedPath: `c:varlibkubeletpods146f8428-83e7-11e7-8dd4-000d3a31dac4volumeskubernetes.io~disk`, }, { path:         `/`, expectedPath: `c:`, }, { path:         ``, expectedPath: ``, }, } for _, test := range tests { result := GetWindowsPath(test.path) if result != test.expectedPath { t.Errorf(\"GetWindowsPath(%v) returned (%v), want (%v)\", test.path, result, test.expectedPath) } } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-295b16ebdca2097490863d761fa466b150fe770891272091eba588ee367ef882", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: I have tried FlexVolume on a Windows node, it does not work. I am now working on this feature now. Below is the FlexVolume initialization error What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.7.7 Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: /sig windows /assign\nDetailed steps about how to use flexvolume on Windows with this PR:\ncc:", "commid": "kubernetes_issue_56875", "tokennum": 183}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b6103aaaff8f2d0ea06cf4ebc28778ab577d0295c58b78c91cb9f32343952d8f", "query": "c = f.ClientSet ns = f.Namespace.Name systemPods, err := e2epod.GetPodsInNamespace(c, ns, map[string]string{}) <del> framework.ExpectEqual(err, nil) </del> <ins> framework.ExpectNoError(err) </ins> systemPodsNo = int32(len(systemPods)) if strings.Index(framework.TestContext.CloudConfig.NodeInstanceGroup, \",\") >= 0 { framework.Failf(\"Test dose not support cluster setup with more than one MIG: %s\", framework.TestContext.CloudConfig.NodeInstanceGroup)", "positive_passages": [{"docid": "doc-en-kubernetes-4d7af6d1d5d1ba0c7ab59da9ea13925b54c282d46d48402ebb3f5409fd2b1204", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: kubernetes/node-problem-detector/node-problem-detector-ci: ci-npd-e2e-node See the Which test(s) are failing: [] NodeProblemDetector [NodeFeature:NodeProblemDetector] [] SystemLogMonitor should generate node condition and events for corresponding errors Since when has it been failing: Dec 03. was at 19:50 PST, was at 21:51 PST. Testgrid link: https://k8s- Reason for failure: Apparently is the culprit. Anything else we need to know: This is likely caused by some library upgrade. Nothing big.\n/sig node\n/assign\nSeems like the failure is caused by . /cc /cc /cc /cc\n/priority critical-urgent\nThe particular bug I care about has been fixed in . I'm gonna still work on submitting , as the same error should also be affecting a few other tests.", "commid": "kubernetes_issue_85933", "tokennum": 235}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b6506f96f2736040398e881898bf127720fa27c5948db94312ae73b087dda7a6", "query": "podResources, err := getNodeDevices() var resourcesForOurPod *kubeletpodresourcesv1alpha1.PodResources framework.Logf(\"pod resources %v\", podResources) <del> gomega.Expect(err).To(gomega.BeNil()) </del> <ins> framework.ExpectNoError(err) </ins> framework.ExpectEqual(len(podResources.PodResources), 2) for _, res := range podResources.GetPodResources() { if res.Name == pod1.Name {", "positive_passages": [{"docid": "doc-en-kubernetes-4d7af6d1d5d1ba0c7ab59da9ea13925b54c282d46d48402ebb3f5409fd2b1204", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: kubernetes/node-problem-detector/node-problem-detector-ci: ci-npd-e2e-node See the Which test(s) are failing: [] NodeProblemDetector [NodeFeature:NodeProblemDetector] [] SystemLogMonitor should generate node condition and events for corresponding errors Since when has it been failing: Dec 03. was at 19:50 PST, was at 21:51 PST. Testgrid link: https://k8s- Reason for failure: Apparently is the culprit. Anything else we need to know: This is likely caused by some library upgrade. Nothing big.\n/sig node\n/assign\nSeems like the failure is caused by . /cc /cc /cc /cc\n/priority critical-urgent\nThe particular bug I care about has been fixed in . I'm gonna still work on submitting , as the same error should also be affecting a few other tests.", "commid": "kubernetes_issue_85933", "tokennum": 235}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b66fa12fd85eca477b99c426659b99a57817f0d8385bd93fc6b781568669f206", "query": "return nil, scoreStatus.AsError() } <ins> if klog.V(10).Enabled() { for plugin, nodeScoreList := range scoresMap { for _, nodeScore := range nodeScoreList { klog.InfoS(\"Plugin scored node for pod\", \"pod\", klog.KObj(pod), \"plugin\", plugin, \"node\", nodeScore.Name, \"score\", nodeScore.Score) } } } </ins> // Summarize all scores. result := make(framework.NodeScoreList, 0, len(nodes)) for i := range nodes { result = append(result, framework.NodeScore{Name: nodes[i].Name, Score: 0}) for j := range scoresMap {", "positive_passages": [{"docid": "doc-en-kubernetes-008ca2b69bf6f84855aa7fc74e613d0733365e6cd47dcc25c8f18519fbaaf463", "text": "Scheduler throughput drops significantly in http://perf- ! After , seems to be the curlspirit.\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/priority critical-urgent /sig scheduling /sig scalability", "commid": "kubernetes_issue_99913", "tokennum": 125}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b673eb1d3d8e084cea9a49aaba0f3560f26929320ad24528bd15a1b743b8997d", "query": "kl.statusManager.SetPodStatus(pod, v1.PodStatus{ Phase:   v1.PodFailed, Reason:  reason, <del> Message: \"Pod \" + message}) </del> <ins> Message: \"Pod was rejected: \" + message}) </ins> } // canAdmitPod determines if a pod can be admitted, and gives a reason if it", "positive_passages": [{"docid": "doc-en-kubernetes-2fe80e49aa5ae53d41f8add8e37445a19adaf3497eeef8427dfc711a0635077f", "text": "When a Pod admission fails due to node-pressure condition then the Pod's looks like this: \"Pod The node had condition: [DiskPressure].\" The \"Pod The node...\" reads awkward. A message like: \"The node had condition: [DiskPressure].\". a job with a pod on a single node cluster, when the node is under disk pressure (then it is tainted with ). The Pod gets stuck in the phase. the node by kubectl command line: Pod is scheduled but admission by Kubelet fails as the taint is re- shortly after its manual removal. Then, the status of the Pod contains the awkward message. No response <details</details<detailsReproducible on kind </details<details</details<details</details<details</details<details</details\n/sig node /triage accepted /priority backlog\nThe first part () is returned here: . I wonder where the is being appended to the beginning. It's my first try to contribute, so I am a little bit lost.\nI think this is a candidate place which might be responsible for the prefix (but haven't checked): I would suggest you to try to reproduce the issue locally first then experiment with modifying the code.\n/assign\nthanks, I've managed to reproduce and used Delve to make sure who's responsible. I opened the changing the message. If it's accepted it will change to .", "commid": "kubernetes_issue_112605", "tokennum": 313}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b682b6c64dc3cd9b142f0903977ac194155edad5146b2d244a323aea6faa8f59", "query": "} apiResource := unversioned.APIResource{Name: gvr.Resource, Namespaced: true} <del> err := dynamicClient.Resource(&apiResource, namespace).DeleteCollection(nil, &v1.ListOptions{}) </del> <ins> // namespace controller does not want the garbage collector to insert the orphan finalizer since it calls // resource deletions generically.  it will ensure all resources in the namespace are purged prior to releasing // namespace itself. orphanDependents := false err := dynamicClient.Resource(&apiResource, namespace).DeleteCollection(&v1.DeleteOptions{OrphanDependents: &orphanDependents}, &v1.ListOptions{}) </ins> if err == nil { return true, nil", "positive_passages": [{"docid": "doc-en-kubernetes-125faf475ef5c9fadc127cee08d3d538bc2825eff7d3fd81be9f088e2d4a0dbf", "text": "Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see ): No What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): \"LRUExpireCache\" Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT What happened: requires write lock since needs to manipulate its list to track recently used item. Currently it uses read lock so it may introduce race condition. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else do we need to know:\nThis was fixed in", "commid": "kubernetes_issue_31081", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b6905192256b8c478f5c39410c75f93e02fe1b746feac6d75db7896787306db6", "query": "\"fmt\" \"os\" \"path\" <ins> \"strings\" </ins> \"github.com/golang/glog\" \"k8s.io/kubernetes/pkg/api/resource\"", "positive_passages": [{"docid": "doc-en-kubernetes-65b87d6ab9dc4eafe4d20be92d7fc50e93b7f8fc56cfe96572cf225758153ef7", "text": "Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG <!-- If this is a BUG REPORT, please: Fill in as much of the template below as you can. If you leave out information, we can't help you as well. If this is a FEATURE REQUEST, please: Describe in detail the feature/behavior/change you'd like to see. In both cases, be ready for followup questions, and please respond in a timely manner. If we can't reproduce a bug or think a feature already exists, we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why. --Kubernetes version (use ): Client Version: version.Info{Major:\"1\", Minor:\"4\", GitVersion:\"v1.4.5\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2016-10-29T01:38:40Z\", GoVersion:\"go1.6.3\", Compiler:\"gc\", Platform:\"linux/amd64\"} Server Version: version.Info{Major:\"1\", Minor:\"4\", GitVersion:\"v1.4.5\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2016-10-29T01:32:42Z\", GoVersion:\"go1.6.3\", Compiler:\"gc\", Platform:\"linux/amd64\"} Environment: Cloud provider or hardware configuration: vSphere OS (e.g. from /etc/os-release):Kernel (e.g. ):Install tools: None Others: None What happened: When I create a deployment with vSphere cloud provider dynamic provisioning, it creates a volume spec with volume path - [datastore] kubevols/volume which contains a white space in it. In this case the cloud provider queries the getDeviceNameFromMount() to return the path of the volume mounted. Since getDeviceNameFromMount() queries the filesystem to get the mount references, it returns a volume path \"[datastore]040kubevols/volume\". Later the kubelet searches for this volume path in both the actual and desired states. Th actual and desired states contains volume with path \"[datastore] kubevols/volume\". So, it couldn't find such volume path and therefore kubernetes stalls unable to make any progress further similar to one described in .", "commid": "kubernetes_issue_38148", "tokennum": 574}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b6905192256b8c478f5c39410c75f93e02fe1b746feac6d75db7896787306db6", "query": "\"fmt\" \"os\" \"path\" <ins> \"strings\" </ins> \"github.com/golang/glog\" \"k8s.io/kubernetes/pkg/api/resource\"", "positive_passages": [{"docid": "doc-en-kubernetes-4472e5c92e91fa48fbd9ae4b2faf4fe2f973ca70781a7072044a8b4998a8c4c5", "text": "Also similar issue described in What you expected to happen: All the pods in the recreated deployment comes up. How to reproduce it (as minimally and precisely as possible): See above. Anything else do we need to know: None\ncc", "commid": "kubernetes_issue_38148", "tokennum": 48}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b6905192256b8c478f5c39410c75f93e02fe1b746feac6d75db7896787306db6", "query": "\"fmt\" \"os\" \"path\" <ins> \"strings\" </ins> \"github.com/golang/glog\" \"k8s.io/kubernetes/pkg/api/resource\"", "positive_passages": [{"docid": "doc-en-kubernetes-856660a825f3ffe3a03d6e2754ae87c832572ac27681226648a4feba9d3ff6d0", "text": "I tried to create a kubernetes deployment with vSphere volume with volume path \"[datastore] kubevols/redis-master\". In this case the cloud provider queries the getDeviceNameFromMount() to return the path of the volume mounted. Since getDeviceNameFromMount() queries the filesystem to get the mount references, it returns a volume path \"[datastore]040kubevols/redis-master\". Later the kubelet searches for this volume path in both the actual and desired states. Th actual and desired states contains volume with path \"[datastore] kubevols/redis-master\". So, it couldn't find such volume path and therefore kubernetes stalls unable to make any progress further similar to one described in . However, when I create a kubernetes deployment with volume path - \"[datastore]kubevols/redis-master\" which doesn't contain any spaces, it works perfectly fine. So, the basic problem is to format and return the correct volume path from getDeviceNameFromMount() function. Alternatively, we can format it properly in the cloud provider code but this has to be done individually in all the cloud provider code base. Inorder to prevent it, it would be better to fix the getDeviceNameFromMount() function to return the correct formatted volume path.\nCC Kubernetes should handle volumes with spaces (looks like vsphere is the first such volume) gracefully. Non a blocker issue for 1.5.\nyou should make sure that the 1.5 release notes capture that \"vsphere volumes w/spaces have problems\". Known issue accumulator in\ngetDeviceNameFromMount is function which queries /proc/mount to get mount points. 040 - is an escape sequence. 040 is the ascii code, in octal(base 8) number system, of the space. The mount command interprets 040 as literal space in the mount point. : Can't we provide a fix for this in 1.5 release itself? There a 2 options: can provide a fix in getDeviceNameFromMount. can provide a fix to vSphere cloud provider to fix it after the call to getDeviceNameFromMount. For option 1, we have to make sure it works for all cloud providers where as for option 2 its not needed. Let me know which option you think is feasible. I am ok with anything.", "commid": "kubernetes_issue_37712", "tokennum": 548}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b6905192256b8c478f5c39410c75f93e02fe1b746feac6d75db7896787306db6", "query": "\"fmt\" \"os\" \"path\" <ins> \"strings\" </ins> \"github.com/golang/glog\" \"k8s.io/kubernetes/pkg/api/resource\"", "positive_passages": [{"docid": "doc-en-kubernetes-f0c75eb090ebda051cbb8d4dcd548ddf167d040dce30f4ff6f2c05a5971aa5a4", "text": "1 is the right answer. But we're very close to 1.5.0 release (<1 week). I'd also like whoever addresses this to ensure the entire system works end-to-end for volumes with spaces, not just patch one little corner. I'm afraid it would be a large change and we're not going to have enough time to validate it in 1.5. You can certainly start working on it. If you get a PR in time, we can consider it for 1.5.0. Otherwise it'll have to go in a patch release.", "commid": "kubernetes_issue_37712", "tokennum": 124}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b6a116e9974f300b9a01ccda3277d7a3e9c1ecbbc3ba68f060ff0b57b226e316", "query": "import ( dockertypes \"github.com/docker/engine-api/types\" <ins> dockercontainer \"github.com/docker/engine-api/types/container\" </ins> \"k8s.io/kubernetes/pkg/api/v1\" ) <ins> // These two functions are OS specific (for now at least) func updateHostConfig(config *dockercontainer.HostConfig) { // no-op, there is a windows implementation that is different. } func DefaultMemorySwap() int64 { return -1 } </ins> func getContainerIP(container *dockertypes.ContainerJSON) string { result := \"\" if container.NetworkSettings != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-2c477631a31f290ae271a7ca0a83a97399cbf63c4cfd883674b6ddce7387fc19", "text": "What happened: Latest kubelet + Windows Docker version 1.14.0-dev refused to start any containers, error output: \"invalid option: Windows does not support MemorySwap\" How to reproduce it (as minimally and precisely as possible): It's always reproducible with Windows Docker 1.14.0-dev + latest kubelet code base. Anything else do we need to know: It didn't happen for Windows Docker 1.12.2-cs2-ws-beta. The reason behind the issue was because new code was for Windows Docker to check Resources parameters, it doesn't accept a non-zero value for MemorySwap: But kubelet was default to set an unlimited (-1) value. The issue was gone in my setup after applied a private fix to disable MemorySwap by set it to zero for Windows.", "commid": "kubernetes_issue_39003", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b6c11e1973260c6dbb785cff750d65221e758c441f6056d42030c965a64ad8e7", "query": "\"strconv\" \"time\" <ins> apierrors \"k8s.io/apimachinery/pkg/api/errors\" </ins> \"k8s.io/apimachinery/pkg/fields\" \"github.com/onsi/ginkgo\"", "positive_passages": [{"docid": "doc-en-kubernetes-bc1f56f76d806f780c64417014c4b072addf1f4df6d254dd55319774f349a24c", "text": "Flaked a couple of times on serial lane with the same error. Test is relatively new. This run only has the single test flake: /sig node /kind flake /cc\n/assign\nNew recent failures: /triage accepted", "commid": "kubernetes_issue_106664", "tokennum": 50}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b6e4fc7f49cfbd3f6fbd8a67c3f54ea8dcd2e43e7f81282d028ceb0530dace13", "query": "- --container=heapster - --poll-period=300000 - --estimator=exponential <del> - image: gcr.io/google_containers/addon-resizer:1.5 </del> <ins> - image: gcr.io/google_containers/addon-resizer:1.6 </ins> name: eventer-nanny resources: limits:", "positive_passages": [{"docid": "doc-en-kubernetes-aa5745d62aee7fc04015b35348d752ab217dfca76565e758f0ca6e53fe701514", "text": "HPA tests are currently failing in gke-large cluster suite: I did some debugging and the problem seems to be related to pod-nanny. Looking into logs from the last run: was first scheduled on the large node dedicated to it pod-nany updated heapster deployment then heapster was scheduled on the normal node (when it actually shouldn't fit) that point it was never updated by the pod nanny. that point, heapster started crashlooping (OOMing) [which in fact was expected in too small machine] So it's pretty clear that that pod-nanny changed the amount of resources to something smaller, which in fact it shouldn't.", "commid": "kubernetes_issue_31950", "tokennum": 140}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b72aab5d6e69fcf782ac94a078ea88cb7b9550454b65417bf1e51ba3c9787ac9", "query": "return err } <del> count := 0 err = r.Visit(func(info *resource.Info, err error) error { </del> <ins> singular := false infos, err := r.IntoSingular(&singular).Infos() if err != nil { return err } if len(infos) == 0 { return fmt.Errorf(\"no objects passed to convert\") } objects, err := resource.AsVersionedObject(infos, !singular, o.outputVersion, o.encoder) if err != nil { return err } if meta.IsListType(objects) { _, items, err := cmdutil.FilterResourceList(objects, nil, nil) </ins> if err != nil { return err } <del> infos := []*resource.Info{info} objects, err := resource.AsVersionedObject(infos, false, o.outputVersion, o.encoder) </del> <ins> filteredObj, err := cmdutil.ObjectListToVersionedObject(items, o.outputVersion) </ins> if err != nil { return err } <del> count++ return o.printer.PrintObj(objects, o.out) }) if err != nil { return err </del> <ins> return o.printer.PrintObj(filteredObj, o.out) </ins> } <del> if count == 0 { return fmt.Errorf(\"no objects passed to convert\") } return nil </del> <ins> return o.printer.PrintObj(objects, o.out) </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-e8aabcf3e5e99db1922665cc12fe15914953073d88b0bc68ff14545d188d9dd5", "text": "BUG REPORT When using with multiple files (like when referencing a directory in ), the json or yaml output is not a valid list format, and when fed to just the first file gets created. Kubernetes version (use ): latest master What happened: only the first file in directory gets created. What you expected to happen: all files in directory must be created. How to reproduce it (as minimally and precisely as possible):", "commid": "kubernetes_issue_36722", "tokennum": 92}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b74956458e46d4ebfbf6fb2aa4284224e299b042bbf1864b773f3c4c32160a0e", "query": "parameters[k] = v.(string) } } <ins> if snapshotProvider, ok := snapshotClass.Object[\"driver\"]; ok { snapshotter = snapshotProvider.(string) } </ins> case d.SnapshotClass.FromFile != \"\": snapshotClass, err := loadSnapshotClass(d.SnapshotClass.FromFile) framework.ExpectNoError(err, \"load snapshot class from %s\", d.SnapshotClass.FromFile)", "positive_passages": [{"docid": "doc-en-kubernetes-51cd929448b3f8fa92237306f83461a030cd5dfe6702e988f5001cdfbd724eae", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: On running kubetest with external storage driver option with driver name \"\", encountered error of flag redefinition. The issue happens because: As part of this patch , a flag is defined for number of inline volumes. The driver name is used to construct the flag name. Thus, when running tests on an externally provided driver (in this instance the Persistent Disk CSI driver) with driver name \"\", a redefinition error happens since the ephemeral test suite code path is executed once for and once for External PD CSI driver. [example run command: kubetest --test --check-version-skew=false --testargs=\"-- --storage.testdriver=/path/to/gcp-compute-persistent-disk-csi-driver/test/k8s-integration/config/test-\" Test config looks something like this: { StorageClass: FromFile: ... SnapshotClass: FromFile: ... DriverInfo: Name: ... } ] What you expected to happen: Test should run and succeed. How to reproduce it (as minimally and precisely as possible): Use an test-, with driver name as \"\", and run kubetest with focus as \"External.Storage\" kubetest --test --check-version-skew=false --testargs=\"-- --storage.testdriver=/path/to/gcp-compute-persistent-disk-csi-driver/test/k8s-integration/config/test-\" Anything else we need to know?: Possible fixes options: , (), when using a FromFile or FromExistingClassName option to pass in SnapshotClass information, pickup the provisioner name from the class definition's \"driver\" field. the flag which has a dependency on driver names. (need to understand the impact of removing the command line flag) Environment: Kubernetes version (use ): latest master Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig storage\n/assign Do you know why this parameter is set as a flag and not a part of the ?\nTo me, is something that defines what the driver can do. This flag is about what the test does and not related to driver capabilities.", "commid": "kubernetes_issue_90868", "tokennum": 582}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b74956458e46d4ebfbf6fb2aa4284224e299b042bbf1864b773f3c4c32160a0e", "query": "parameters[k] = v.(string) } } <ins> if snapshotProvider, ok := snapshotClass.Object[\"driver\"]; ok { snapshotter = snapshotProvider.(string) } </ins> case d.SnapshotClass.FromFile != \"\": snapshotClass, err := loadSnapshotClass(d.SnapshotClass.FromFile) framework.ExpectNoError(err, \"load snapshot class from %s\", d.SnapshotClass.FromFile)", "positive_passages": [{"docid": "doc-en-kubernetes-270b31a5e196f61611ca75afa5bbde1923e891fb5ac161d33aa5adc26b5fc154", "text": "Making it depend on the driver name was probably unnecessary. A single flag for all incarnations of that test probably would have been sufficient and thus better (\"keep it simple, stupid!\" - the stupid being me here...). It also shouldn't have used the global flag set. In other words:\n/reopen I don't really want to get into the habit of defining per test case flags in There are thousands of test cases and it would be unwieldy to discover all the flags available and understand how to use them. What factors would influence how many volumes you want the test to create? Can we just hardcode a value in the test case?\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThe defaults must be usable so that users do not need to understand them. The flags can be discovered with - not ideal, but at least they show up. That's effectively what the default value for the flag does. This is a way to to run a custom stress test: the default is so low, it just tests that the feature works. By increasing it as high as the underlying CSI driver and storage system supports, one can run this (and potentially other tests) as part of stress testing. Not sure whether it's worth supporting this. It seemed worthwhile at the time, and better than hard-coding just one value.\nThe bigger issue is: how do users of the test suite actually learn what tests they run and what those tests do? I suspect the answer to that is simply \"read the source\", in which case they'll also find the knobs that can be used to tweak testing.\nSince increasing the parameter depends on the csi driver/storage system, then I would recommending splitting this up into 2 test cases: 1) test basic functionality 2) test stress scenario, and add the parameter to the driver test config similarly to other stress tests:\nAt least for the storage tests, because we are intending that they be run externally, having all the tunables in one place I think makes it easier to discover.\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close.", "commid": "kubernetes_issue_90868", "tokennum": 496}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b74956458e46d4ebfbf6fb2aa4284224e299b042bbf1864b773f3c4c32160a0e", "query": "parameters[k] = v.(string) } } <ins> if snapshotProvider, ok := snapshotClass.Object[\"driver\"]; ok { snapshotter = snapshotProvider.(string) } </ins> case d.SnapshotClass.FromFile != \"\": snapshotClass, err := loadSnapshotClass(d.SnapshotClass.FromFile) framework.ExpectNoError(err, \"load snapshot class from %s\", d.SnapshotClass.FromFile)", "positive_passages": [{"docid": "doc-en-kubernetes-25193f95a984c83e59d3bf61132d542700dd22032bd8c1cb3f7d9def5d988f52", "text": "If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten\nIssues 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\n/remove-lifecycle stale /help\nThis request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /remove-lifecycle stale /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\nIssues 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\n/remove-lifecycle stale\nI saw that the flag was removed in , I think we can close this one if doesn't apply anymore\n/close The flag was removed in #diff-20517805986874f69e3254bed93d59996d5a6fd571a70ab8120736ded5aafa24\nYou can't close an active issue/PR unless you authored it or you are a collaborator. <detailsIn response to : /close The flag was removed in #diff-20517805986874f69e3254bed93d59996d5a6fd571a70ab8120736ded5aafa24 </details\n/close\nClosing this issue.", "commid": "kubernetes_issue_90868", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b74956458e46d4ebfbf6fb2aa4284224e299b042bbf1864b773f3c4c32160a0e", "query": "parameters[k] = v.(string) } } <ins> if snapshotProvider, ok := snapshotClass.Object[\"driver\"]; ok { snapshotter = snapshotProvider.(string) } </ins> case d.SnapshotClass.FromFile != \"\": snapshotClass, err := loadSnapshotClass(d.SnapshotClass.FromFile) framework.ExpectNoError(err, \"load snapshot class from %s\", d.SnapshotClass.FromFile)", "positive_passages": [{"docid": "doc-en-kubernetes-51e228a10e330c9cdfe0846a8842785d5f11851661581fda232b614aedbd5649", "text": "<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", "commid": "kubernetes_issue_90868", "tokennum": 41}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b7b432e4801e554c9b8b8d53e7f73c78a721804b44e4e0b7c3c1fc6d8f634ccf", "query": "There are a few things to note in this description.  First is that we are running the ```kubernetes/cassandra``` image.  This is a standard Cassandra installation on top of Debian.  However it also adds a custom [```SeedProvider```](https://svn.apache.org/repos/asf/cassandra/trunk/src/java/org/apache/cassandra/locator/SeedProvider.java) to Cassandra.  In Cassandra, a ```SeedProvider``` bootstraps the gossip protocol that Cassandra uses to find other nodes.  The ```KubernetesSeedProvider``` discovers the Kubernetes API Server using the built in Kubernetes discovery service, and then uses the Kubernetes API to find new nodes (more on this later) <del> You may also note that we are setting some Cassandra parameters (```MAX_HEAP_SIZE``` and ```HEAP_NEWSIZE```).  We also tell Kubernetes that the container exposes both the ```CQL``` and ```Thrift``` API ports.  Finally, we tell the cluster manager that we need 0.5 cpu (0.5 core). </del> <ins> You may also note that we are setting some Cassandra parameters (```MAX_HEAP_SIZE``` and ```HEAP_NEWSIZE```) and adding information about the [namespace](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/namespaces.md).  We also tell Kubernetes that the container exposes both the ```CQL``` and ```Thrift``` API ports.  Finally, we tell the cluster manager that we need 0.5 cpu (0.5 core). </ins> Given this configuration, we can create the pod from a file specification as follows", "positive_passages": [{"docid": "doc-en-kubernetes-600b05087b3e5a02baef82de4ad7a72820fecd2de58582bba171390ab13fae8d", "text": "The namespace seems to be hard coded :\ncc:\nThanks. We can improve it after v1 release.", "commid": "kubernetes_issue_10034", "tokennum": 22}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b7c2fbd72a2b14f0fbdbef31b5b02f5824b9c21c869cd2b50d565e1497f15103", "query": "manager.podStoreSynced = alwaysReady syncAndValidateDaemonSets(t, manager, ds, podControl, 1, 0) } <ins> func TestDSManagerInit(t *testing.T) { // Insert a stable daemon set and make sure we don't create an extra pod // for the one node which already has a daemon after a simulated restart. ds := newDaemonSet(\"test\") ds.Status = extensions.DaemonSetStatus{ CurrentNumberScheduled: 1, NumberMisscheduled:     0, DesiredNumberScheduled: 1, } nodeName := \"only-node\" podList := &api.PodList{ Items: []api.Pod{ *newPod(\"podname\", nodeName, simpleDaemonSetLabel), }} response := runtime.EncodeOrDie(testapi.Default.Codec(), podList) fakeHandler := utiltesting.FakeHandler{ StatusCode:   200, ResponseBody: response, } testServer := httptest.NewServer(&fakeHandler) // TODO: Uncomment when fix #19254 // defer testServer.Close() client := client.NewOrDie(&client.Config{Host: testServer.URL, GroupVersion: testapi.Default.GroupVersion()}) manager := NewDaemonSetsController(client, controller.NoResyncPeriodFunc) manager.dsStore.Add(ds) manager.nodeStore.Add(newNode(nodeName, nil)) manager.podStoreSynced = alwaysReady controller.SyncAllPodsWithStore(manager.kubeClient, manager.podStore.Store) fakePodControl := &controller.FakePodControl{} manager.podControl = fakePodControl manager.syncHandler(getKey(ds, t)) validateSyncDaemonSets(t, fakePodControl, 0, 0) } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-b0a441a371f8db864bebc11c7303837af71a86244bb0f50ec81fe1d8a09d5c71", "text": "The test is in flaky suite and no one seems to care. We need an owner for this test. cc Last failure log:\ndo you think you can take a look at this?\nThis is happening because of a bad assumption. The assumption is: if the reflector's store is consistent with etcd, the store given back to clients of the framework.Controller is too. I'd really like a general fix applicable to all controllers for this problem, but fixing it just for the RCs is pretty easy. In more detail: This function reports when the reflector has listed from apiserver. But the store given to the reflector is the fifo of the framework.Controller. The store given back to the caller is still not consistent, and will not be till the framework.Controller puts all the objects from the fifo into the client state store (). The rc specific fix: Before starting the rc manager, seed the expectations store with an expectation like {rc:foo, adds: foo.Status.Replicas, deletes:0}. This will wait for status.Replicas number of ADD events till a timeout. The general fix: Somehow expose this through framework.Controller.HasSynced (clients don't care about the fifo anyway, shouldn't it just be an implementation detail?) ideas? cc'ing people who have written controllers that might be interested I don't think this (and generally anything flaky for 1 release) is a p0, I can fix it if you don't mind dealing with the flakes till I've cleared things off my plate. I'd be more than happy to review a fix.\nWell, it's a P0 because test is flaky. E.g last run:\n- did you have chance to look into it?\nThe \"DaemonRestart\" tests are still labeled at . I will send a PR to promote them.\nare you still planning to send aPR to promote the DaemonRestart tests out of flaky? I think this is the right thing to do.\nAck; sorry, I lost this in the muck.", "commid": "kubernetes_issue_17829", "tokennum": 444}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b7c500c8f86990f336d9d472bf27d7ebdbf87af5f9c0794497578b9683924604", "query": "return fmt.Errorf(\"waiting for apiserver timed out\") } <del> // WaitForApiserverRestarted waits until apiserver's restart count increased. func WaitForApiserverRestarted(c clientset.Interface, initialRestartCount int32) error { </del> <ins> // waitForApiserverRestarted waits until apiserver's restart count increased. func waitForApiserverRestarted(c clientset.Interface, initialRestartCount int32) error { </ins> for start := time.Now(); time.Since(start) < time.Minute; time.Sleep(5 * time.Second) { <del> restartCount, err := GetApiserverRestartCount(c) </del> <ins> restartCount, err := getApiserverRestartCount(c) </ins> if err != nil { Logf(\"Failed to get apiserver's restart count: %v\", err) continue", "positive_passages": [{"docid": "doc-en-kubernetes-45049cecee14166a5520f4dc4cbecae5a5a4a44f20c23557ee81cd45d6979f23", "text": "This test is failing in both gce serial suite: http://k8s- /sig network /priority failing-test /priority critical-urgent /kind bug /status approved-for-milestone cc /assign PTAL\nxref\n/milestone v1.10\nthis also fails in http://k8s-\nFailing to connect to Services at all. I can't even ping pod IPs:\nSo I can ping pods same-node and cross-node right up until it kills the apiserver. Rebooting fixes a given node. The apiserver demonstrably comes back - I can query it for info...\n- I could use help - have to shift attention soon.\nFWIW, I am testing on a Calico-enabled node\nI'll take a look at this as well.\nWeird, now even after a reboot, this condition is sticky. I have a cluster in this state, if you want to poke.\nugh, now it is resolved.\nI just repro'ed without the e2e - have a cluster, proved ping works, killed apiserver ping fails.\nInteresting - docker shows the pods not running, but apiserver says they are alive.\nUpdate: docker sees no running pods. API server thinks kubelet is running them. kubelet is getting \"\" from apiserver, even after kubelet restart.\nUpdate and recap: Bring up a cluster Run some pods Prove that pods are running and services work pkill -9 apiserver Wait. Watch kubelets \"lose\" pods that were assigned to them Observe that pods are not running and services do not work Observe that apiserver says the pods are running pkill -9 kubelet Observe that it is still broken kubectl delete one pod Observe that kubelet is fixed for that one pod, but not others Q: Why is kubelet not getting a full listing when it restarts?\nWhat exactly does it mean for it to be fixed for a deleted pod?\nKubelet started running the pod that was deleted - it got the update for that one.\nThe cluster I was testing was a week or 2 old. I built a cluster from HEAD and I can not repro - said the same. Is this test running against head of master?\nI also ran the test manually against my new cluster and it passed\nFWIW I was also unable to reproduce this yesterday on a cluster from HEAD.", "commid": "kubernetes_issue_60761", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b7c500c8f86990f336d9d472bf27d7ebdbf87af5f9c0794497578b9683924604", "query": "return fmt.Errorf(\"waiting for apiserver timed out\") } <del> // WaitForApiserverRestarted waits until apiserver's restart count increased. func WaitForApiserverRestarted(c clientset.Interface, initialRestartCount int32) error { </del> <ins> // waitForApiserverRestarted waits until apiserver's restart count increased. func waitForApiserverRestarted(c clientset.Interface, initialRestartCount int32) error { </ins> for start := time.Now(); time.Since(start) < time.Minute; time.Sleep(5 * time.Second) { <del> restartCount, err := GetApiserverRestartCount(c) </del> <ins> restartCount, err := getApiserverRestartCount(c) </ins> if err != nil { Logf(\"Failed to get apiserver's restart count: %v\", err) continue", "positive_passages": [{"docid": "doc-en-kubernetes-a335c4245d7a15c6e680ffd06bca4d469bc98515fa6a43286dbf7f7a3bfccc88", "text": "Did some investigations and had some findings for this specific failure: Traced down a bit on the history, the first occurrence was https://k8s- From the , seems suspicious because it modified . Also found reported a relevant symptom: The fix () for that was merged a day ago and may explained why we can't repro from HEAD anymore.\nnice, is this issue reproducible without the fix ()?\nSorry should have had confirmed this, bringing up a cluster now.\nQuick update: I was able to repro the same failure () from HEAD with reverted. Though this test is now flaky on some other errors: https://k8s- https://k8s- They all seem to failed while communicating with apiserver.\nThanks ! So fixed the issue and I am curious about what introduced the issue. Do you happen to know when did this test start to fail? Just trying to find out what went wrong in between. We have some other possibly related issues so finding out the root cause of this one would be super helpful.\n/assign\nThe first occurrence (for that exact failure) I noticed was https://k8s-, which happened on 2018-02-15 09:49 PST.\nYou all rock! I see a couple greens on it now, but still mostly red?\nThe test is now flaky mostly on creating an exec pod after restarting apiserver. Some sample failures: To elaborate a bit more, a snippet of the test procedure is: ssh to master and (sending a SIGTERM) Keep polling on /healthz on apiserver until 200 is returned. Create an exec pod for later steps (and failed on various erros --- EOF, connection refused, apiserver terminating). According to above test failures, my suspicion is that the test is assuming the apiserver is restarted too soon. It is possible that apiserver captured SIGTERM and did a graceful termination, so that polling on /healthz may succeed even in the termination phase. I'm not surprised trying to create a pod via a terminating apiserver will hit those errors. Could anyone confirme the SIGTERM theory?\nSpoke with folks, sounds like after SIGTERM apiserver does wait a bit for remaining requests to finish. I will take a stab to refine the test. cc\nSent .\nTest is now passing on gce but failing on gke.", "commid": "kubernetes_issue_60761", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b7c500c8f86990f336d9d472bf27d7ebdbf87af5f9c0794497578b9683924604", "query": "return fmt.Errorf(\"waiting for apiserver timed out\") } <del> // WaitForApiserverRestarted waits until apiserver's restart count increased. func WaitForApiserverRestarted(c clientset.Interface, initialRestartCount int32) error { </del> <ins> // waitForApiserverRestarted waits until apiserver's restart count increased. func waitForApiserverRestarted(c clientset.Interface, initialRestartCount int32) error { </ins> for start := time.Now(); time.Since(start) < time.Minute; time.Sleep(5 * time.Second) { <del> restartCount, err := GetApiserverRestartCount(c) </del> <ins> restartCount, err := getApiserverRestartCount(c) </ins> if err != nil { Logf(\"Failed to get apiserver's restart count: %v\", err) continue", "positive_passages": [{"docid": "doc-en-kubernetes-937105a0fb62d0b30f0dcf82865ffcd7dde374c2d2e0895384450ffe72527abd", "text": "Apparently we don't have a way to trigger apiserver restart on gke at this moment. Sending a PR to skip this test on gke.\n[MILESTONENOTIFIER] Milestone Issue Needs Attention Action required: During code freeze, issues in the milestone should be in progress. If this issue is not being actively worked on, please remove it from the milestone. If it is being worked on, please add the label so it can be tracked with other in-flight issues. Note: This issue is marked as , and must be updated every 1 day during code freeze. Example update: <details<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Never automatically move issue out of a release milestone; continually escalate to contributor and SIG through all available channels. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details\nCommented too quick. On gke we do a same-version master upgrade. Will send another fix :/", "commid": "kubernetes_issue_60761", "tokennum": 256}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b7ce2b1e3c129c5b498240f795fa5ead88c9d9d9554e24fc992cd075c1c227d0", "query": "var policy Policy switch topologyPolicyName { <del> case PolicyNone: policy = NewNonePolicy() </del> case PolicyBestEffort: policy = NewBestEffortPolicy(numaInfo, opts)", "positive_passages": [{"docid": "doc-en-kubernetes-4d10931e14d2065e9a15e6880eb555f03f2fd6b09352947daeddff0435b576bc", "text": "Follow up from: See details there. When is , there is no need to discover the NUMA topology. /sig node /priority backlog /kind feature /help-wanted\n/cc\n/triage accepted\nI would like to take this up also can I get more brief information about it? code review comments from asking that inside the NewManager() implementation, we need to skip NewPolicyOptions and NewNUMAInfo but when the NumaTopology comes kubelet issue also comes. I need some more information to start with this!\n/cc\nWhen there is no topology manger policy specified, NewManager should be a no-op. Just skip all checks.\nExactly. Just to add: we may need few iterations over the change to get a clean flow in the call.\n/assign", "commid": "kubernetes_issue_116391", "tokennum": 166}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b801831883f01477a39d432c9e77dc4213e98ee0bdf60355e9f382018e89fd93", "query": "# Base images - name: \"k8s.gcr.io/debian-base: dependents\" <del> version: buster-v1.3.0 </del> <ins> version: buster-v1.4.0 </ins> refPaths: - path: build/workspace.bzl match: tag =", "positive_passages": [{"docid": "doc-en-kubernetes-ee0826757468ea334f95c77509b257c3d392b6713b4311ba7afa125d642dcec9", "text": "The based container images for are shipped with the wrong architecture within the manifest if not amd64: Refers to We updated the images a few minutes ago to buster-v1.3.0, which are now ready to be used as base for the multi-architecture images. If the images contain the right architectures, then it may magically happen that the kube-proxy images are fixed, too. This is because we already use the build syntax for it: /cc\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig release", "commid": "kubernetes_issue_98229", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b81bced438d9a9b8897df90c7354980d62902682f34ae288dfe79d43e4934de9", "query": "- name: ssl-certs mountPath: /etc/ssl/certs readOnly: true <del> - image: gcr.io/google_containers/addon-resizer:1.5 </del> <ins> - image: gcr.io/google_containers/addon-resizer:1.6 </ins> name: heapster-nanny resources: limits:", "positive_passages": [{"docid": "doc-en-kubernetes-aa5745d62aee7fc04015b35348d752ab217dfca76565e758f0ca6e53fe701514", "text": "HPA tests are currently failing in gke-large cluster suite: I did some debugging and the problem seems to be related to pod-nanny. Looking into logs from the last run: was first scheduled on the large node dedicated to it pod-nany updated heapster deployment then heapster was scheduled on the normal node (when it actually shouldn't fit) that point it was never updated by the pod nanny. that point, heapster started crashlooping (OOMing) [which in fact was expected in too small machine] So it's pretty clear that that pod-nanny changed the amount of resources to something smaller, which in fact it shouldn't.", "commid": "kubernetes_issue_31950", "tokennum": 140}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b8508bf359afa28573de7209833ccec56b3bfd900bdc661f55178bfefe90a0ff", "query": "} // returns the item and true if it is found and not expired, otherwise nil and false. <ins> // If this returns false, it has locked c.inFlightLock and it is caller's responsibility // to unlock that. </ins> func (c *timeCache) get(key string) (T, bool) { c.lock.RLock() defer c.lock.RUnlock() data, ok := c.cache[key] now := c.clock.Now() if !ok || now.Sub(data.lastUpdate) > c.ttl { <ins> // We must lock this while we hold c.lock-- otherwise, a writer could // write to c.cache and remove the channel from c.inFlight before we // manage to read c.inFlight. c.inFlightLock.Lock() </ins> return nil, false } return data.item, true } <ins> // c.inFlightLock MUST be locked before calling this. fillOrWait will unlock it. </ins> func (c *timeCache) fillOrWait(key string) chan T { <del> c.inFlightLock.Lock() </del> defer c.inFlightLock.Unlock() // Already a call in progress?", "positive_passages": [{"docid": "doc-en-kubernetes-0882877f8aa87dd9f2fab7aa6c2163d630c073e98d0481f7c1762728faaae3b6", "text": "Failed due to an apparently unrelated PR: https://travis-\nProblem here is that I left a small chance of a double-call in my parallelized cache. Didn't realize this was being tested. Will fix.", "commid": "kubernetes_issue_3439", "tokennum": 46}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b863cb4de38156d11e1735bbdbd2cf82b2bcb9387113d3c231bd00485a6b2add", "query": "if err != nil { t.Fatalf(err.Error()) } test.prepare(base) pathToCreate := filepath.Join(base, test.path) fd, err := doSafeOpen(pathToCreate, base)", "positive_passages": [{"docid": "doc-en-kubernetes-ea06bb5e10f9c1a3c6e6bdd4b05e49a63cf7c6313178f3d65784c243007cbe65", "text": "Subpath unix socket tests can flake because of long socket path. On Linux the path limit should be 108 chars or less. /sig storage", "commid": "kubernetes_issue_61844", "tokennum": 31}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b870041984b30c33b192a75cf635e2d777c278f2b72059ece9e3b30ec400762c", "query": "\"type\": \"boolean\" }, \"storageCapacity\": { <del> \"description\": \"If set to true, storageCapacity indicates that the CSI volume driver wants pod scheduling to consider the storage capacity that the driver deployment will report by creating CSIStorageCapacity objects with capacity information.nnThe check can be enabled immediately when deploying a driver. In that case, provisioning new volumes with late binding will pause until the driver deployment has published some suitable CSIStorageCapacity object.nnAlternatively, the driver can be deployed with the field unset or false and it can be flipped later when storage capacity information has been published.nnThis field is immutable.nnThis is a beta field and only available when the CSIStorageCapacity feature is enabled. The default is false.\", </del> <ins> \"description\": \"If set to true, storageCapacity indicates that the CSI volume driver wants pod scheduling to consider the storage capacity that the driver deployment will report by creating CSIStorageCapacity objects with capacity information.nnThe check can be enabled immediately when deploying a driver. In that case, provisioning new volumes with late binding will pause until the driver deployment has published some suitable CSIStorageCapacity object.nnAlternatively, the driver can be deployed with the field unset or false and it can be flipped later when storage capacity information has been published.nnThis field was immutable in Kubernetes <= 1.22 and now is mutable.nnThis is a beta field and only available when the CSIStorageCapacity feature is enabled. The default is false.\", </ins> \"type\": \"boolean\" }, \"tokenRequests\": {", "positive_passages": [{"docid": "doc-en-kubernetes-cdccab911562ccfffce851739652bcccdbeabc99e62d699c46baa58ef67f3bbe", "text": "Up to 1.21, that field is immutable. That means in practice, a CSIDriver object has to be deleted and then re-created with a different value instead. Mutation via delete/created is unnecessarily complex and as the only consumer of that field (the kube-scheduler) can handle mutation just fine (it'll always ask the informer cache for the current value), it's better to allow mutation.\n/sig storage /assign\nThis is independent of allowing other fields to become mutable, but that might also make sense.\n/triage accepted", "commid": "kubernetes_issue_100089", "tokennum": 125}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b8a3e8f47efb1353ec1db1a72c427784eba8041fe39cd38d747bf595df803583", "query": "Metrics:   usage, Available: availableResources[m.Name], }) <ins> delete(availableResources, m.Name) } // print lines for nodes of which the metrics is unreachable. for nodeName := range availableResources { printMissingMetricsNodeLine(w, nodeName) </ins> } return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-e039746a8b3b20db88e55e1a23e49575ef9c4052776f0c6f0c425699707a07a4", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If this may be security issue, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: What happened: kubectl top nodes didn't report one of my nodes. I have a cluster of 8 and only 7 printed.", "commid": "kubernetes_issue_63986", "tokennum": 79}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b8a3e8f47efb1353ec1db1a72c427784eba8041fe39cd38d747bf595df803583", "query": "Metrics:   usage, Available: availableResources[m.Name], }) <ins> delete(availableResources, m.Name) } // print lines for nodes of which the metrics is unreachable. for nodeName := range availableResources { printMissingMetricsNodeLine(w, nodeName) </ins> } return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-3b3a7005744c97bc2a779a3634e9ae4963750e882f0e9fc3a43aa2969cd1ed2b", "text": "<pre:::: fang 10:04:02 (cgthayer-pchat) 0 platform; kubectl top nodes NAME CPU(cores) CPU% MEMORY(bytes) MEMORY% gke-charles-test-cluster-default-pool--jkrj 311m 33% 2470Mi 93% gke-charles-test-cluster-default-pool--krsh 154m 16% 1763Mi 66% gke-charles-test-cluster-default-pool--vhgq 265m 28% 1954Mi 73% gke-charles-test-cluster-default-pool--x3bs 186m 19% 1990Mi 75% gke-charles-test-cluster-default-pool--073f 270m 28% 1729Mi 65% gke-charles-test-cluster-default-pool--09zf 403m 42% 2698Mi 102% gke-charles-test-cluster-default-pool--p7h1 191m 20% 1582Mi 59% :::: fang 10:04:07 (cgthayer-pchat) 0 platform; kubectl get nodes NAME STATUS ROLES AGE VERSION gke-charles-test-cluster-default-pool--073f Ready <none7d v1.7.12-gke.1 gke-charles-test-cluster-default-pool--09zf Ready <none7d v1.7.12-gke.1 gke-charles-test-cluster-default-pool--cl65 Ready <none6d v1.7.12-gke.1 gke-charles-test-cluster-default-pool--jkrj Ready <none8d v1.7.12-gke.1 gke-charles-test-cluster-default-pool--krsh Ready <none8d v1.7.12-gke.1 gke-charles-test-cluster-default-pool--p7h1 Ready <none7d v1.7.12-gke.1 gke-charles-test-cluster-default-pool--vhgq Ready <none8d v1.7.12-gke.1 gke-charles-test-cluster-default-pool--x3bs Ready <none8d v1.7.12-gke.1 <preWhat you expected to happen: I expected all nodes to be printed.", "commid": "kubernetes_issue_63986", "tokennum": 536}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b8a3e8f47efb1353ec1db1a72c427784eba8041fe39cd38d747bf595df803583", "query": "Metrics:   usage, Available: availableResources[m.Name], }) <ins> delete(availableResources, m.Name) } // print lines for nodes of which the metrics is unreachable. for nodeName := range availableResources { printMissingMetricsNodeLine(w, nodeName) </ins> } return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-ba6ca4dcc9f7eacf0c6e395f7904a902222263b10161fd5f101ea154df88d32e", "text": "Since the missing node might have bad data I might expect it to have the same number of columns with \"-\" values and a note in a new 6th column saying something like \"unavailabe\" \"unresponsive\" \"stale-data\" etc. e.g. <pregke-charles-test-cluster-default-pool--p7h1 - - - - unreachable </preHow to reproduce it (as minimally and precisely as possible): Not sure. Perhaps run a pod where you can intentionally trigger it to use too much cpu or memory. Anything else we need to know?: Environment: Kubernetes version (use ): kubectl version Client Version: version.Info{Major:\"1\", Minor:\"8\", GitVersion:\"v1.8.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2017-12-21T06:34:11Z\", GoVersion:\"go1.8.3\", Compiler:\"gc\", Platform:\"linux/amd64\"} Server Version: version.Info{Major:\"1\", Minor:\"8+\", GitVersion:\"v1.8.8-gke.0\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2018-02-16T18:26:58Z\", GoVersion:\"go1.8.3b4\", Compiler:\"gc\", Platform:\"linux/amd64\"} Cloud provider or hardware configuration: GKE OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/sig cli\n/kind feature\nI raise a PR to print when the metrics is missing. As for the 6th column you mentioned, I think it could be debatable for its necessity. :)", "commid": "kubernetes_issue_63986", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b8b221586c9a339b4cded0642f070bdefd3a9123aa9480cebaaa29f6b7733789", "query": "} } <del> if klog.V(4).Enabled() { logPluginScores(nodes, scoresMap, pod) } </del> if len(g.extenders) != 0 && nodes != nil { var mu sync.Mutex var wg sync.WaitGroup", "positive_passages": [{"docid": "doc-en-kubernetes-008ca2b69bf6f84855aa7fc74e613d0733365e6cd47dcc25c8f18519fbaaf463", "text": "Scheduler throughput drops significantly in http://perf- ! After , seems to be the curlspirit.\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/priority critical-urgent /sig scheduling /sig scalability", "commid": "kubernetes_issue_99913", "tokennum": 125}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b8dfc69b62043ac7d79a130bc124681d20624e6a649d81f9ffbdb9bcc58ce602", "query": "// Not local instance, get addresses from Azure ARM API. if !isLocalInstance { <del> return addressGetter(name) </del> <ins> if az.vmSet != nil { return addressGetter(name) } // vmSet == nil indicates credentials are not provided. return nil, fmt.Errorf(\"no credentials provided for Azure cloud provider\") </ins> } if len(metadata.Network.Interface) == 0 {", "positive_passages": [{"docid": "doc-en-kubernetes-effe9bff1df2586252b385cbf4a7cacd04cb77f4739ff9c987e63818f9dc1c82", "text": "Currently there is no way to run without any identity (be it service principal or E/MSI). In reality code running on a worker node can use via - and only via - without the need to access ARM. Here is the proposed change a new mode authN = this mode, is basically telling the cloud provider to work any identity, this means only IMDS calls is allowed. This mode can be detected from if no SPN set and both MSI settings are set to . to use a config map within the cluster. This config map can be loaded on the cluster statically. or created - if not existent - in that then only is used in The net new result of the above is users bootstrapping clusters can configure the worker node to use without any identity on said worker nodes.\n/sig azure These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by \u200d\nIn-tree AzureDisk volume plugin is also depending on Azure credential to fetch lun id. we should figure out how to solve it without credential\nfetch disk lun id is also a dependency in kubelet code now, after my investigation, it could be removed on Linux node, while it cannot be removed on Windows node, need to change the k/k upstream code, there is a discussion on going here: , let' wait for the discussion result.\nFor Linux: 1- use IMDS my understanding is new api versions will have the disk/lun pairs. 2- don't use arm for the return of is the second parameter passed to . For Windows: I don't understand the dep on ARM for this. The above still apply, we just need to find a way to encode the value as ut return from that allow us to find the disk by on a windows machine. might be a good source for this. Ideally speaking. The value should be the same. But i will leave it for you to decide.\ncould be a good idea since currently it's a LUN num returned by Attach() and then it could be changed to the windows disk num, I will make the code change on v1.15 later, thanks for discussion.\nUpdate: PR would remove the VM API calls when getting the LUN number for AzureDisk.", "commid": "kubernetes_issue_77309", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b932ff944551eb66946dfdae4b1a2af0b7de5f8905865f2c84185dfa324aa897", "query": "} } <ins> func TestPriorityQueue_MoveAllToActiveOrBackoffQueueWithOutQueueingHint(t *testing.T) { c := testingclock.NewFakeClock(time.Now()) logger, ctx := ktesting.NewTestContext(t) ctx, cancel := context.WithCancel(ctx) defer cancel() m := makeEmptyQueueingHintMapPerProfile() defer featuregatetesting.SetFeatureGateDuringTest(t, utilfeature.DefaultFeatureGate, features.SchedulerQueueingHints, false)() m[\"\"][NodeAdd] = []*QueueingHintFunction{ { PluginName:     \"fooPlugin\", QueueingHintFn: queueHintReturnQueue, }, } q := NewTestQueue(ctx, newDefaultQueueSort(), WithClock(c), WithQueueingHintMapPerProfile(m)) // To simulate the pod is failed in scheduling in the real world, Pop() the pod from activeQ before AddUnschedulableIfNotPresent()s below. if err := q.Add(logger, medPriorityPodInfo.Pod); err != nil { t.Errorf(\"add failed: %v\", err) } err := q.AddUnschedulableIfNotPresent(logger, q.newQueuedPodInfo(unschedulablePodInfo.Pod, \"fooPlugin\"), q.SchedulingCycle()) if err != nil { t.Fatalf(\"unexpected error from AddUnschedulableIfNotPresent: %v\", err) } err = q.AddUnschedulableIfNotPresent(logger, q.newQueuedPodInfo(highPriorityPodInfo.Pod, \"fooPlugin\"), q.SchedulingCycle()) if err != nil { t.Fatalf(\"unexpected error from AddUnschedulableIfNotPresent: %v\", err) } // Construct a Pod, but don't associate its scheduler failure to any plugin hpp1 := clonePod(highPriorityPodInfo.Pod, \"hpp1\") // This Pod will go to backoffQ because no failure plugin is associated with it. err = q.AddUnschedulableIfNotPresent(logger, q.newQueuedPodInfo(hpp1), q.SchedulingCycle()) if err != nil { t.Fatalf(\"unexpected error from AddUnschedulableIfNotPresent: %v\", err) } // Construct another Pod, and associate its scheduler failure to plugin \"barPlugin\". hpp2 := clonePod(highPriorityPodInfo.Pod, \"hpp2\") // This Pod will go to the unschedulable Pod pool. err = q.AddUnschedulableIfNotPresent(logger, q.newQueuedPodInfo(hpp2, \"barPlugin\"), q.SchedulingCycle()) if err != nil { t.Fatalf(\"unexpected error from AddUnschedulableIfNotPresent: %v\", err) } // This NodeAdd event moves unschedulablePodInfo and highPriorityPodInfo to the backoffQ, // because of the queueing hint function registered for NodeAdd/fooPlugin. q.MoveAllToActiveOrBackoffQueue(logger, NodeAdd, nil, nil, nil) if q.activeQ.Len() != 1 { t.Errorf(\"Expected 1 item to be in activeQ, but got: %v\", q.activeQ.Len()) } // Pop out the medPriorityPodInfo in activeQ. if p, err := q.Pop(logger); err != nil || p.Pod != medPriorityPodInfo.Pod { t.Errorf(\"Expected: %v after Pop, but got: %v\", medPriorityPodInfo.Pod, p.Pod.Name) } // hpp2 won't be moved. if q.podBackoffQ.Len() != 3 { t.Fatalf(\"Expected 3 items to be in podBackoffQ, but got: %v\", q.podBackoffQ.Len()) } // pop out the pods in the backoffQ. // This doesn't make them in-flight pods. for q.podBackoffQ.Len() != 0 { _, err = q.podBackoffQ.Pop() if err != nil { t.Errorf(\"pop failed: %v\", err) } } q.schedulingCycle++ unschedulableQueuedPodInfo := q.newQueuedPodInfo(unschedulablePodInfo.Pod, \"fooPlugin\") highPriorityQueuedPodInfo := q.newQueuedPodInfo(highPriorityPodInfo.Pod, \"fooPlugin\") hpp1QueuedPodInfo := q.newQueuedPodInfo(hpp1) err = q.AddUnschedulableIfNotPresent(logger, unschedulableQueuedPodInfo, q.SchedulingCycle()) if err != nil { t.Fatalf(\"unexpected error from AddUnschedulableIfNotPresent: %v\", err) } err = q.AddUnschedulableIfNotPresent(logger, highPriorityQueuedPodInfo, q.SchedulingCycle()) if err != nil { t.Fatalf(\"unexpected error from AddUnschedulableIfNotPresent: %v\", err) } err = q.AddUnschedulableIfNotPresent(logger, hpp1QueuedPodInfo, q.SchedulingCycle()) if err != nil { t.Fatalf(\"unexpected error from AddUnschedulableIfNotPresent: %v\", err) } if err = q.Add(logger, medPriorityPodInfo.Pod); err != nil { t.Errorf(\"add failed: %v\", err) } // hpp1 will go to backoffQ because no failure plugin is associated with it. // All plugins other than hpp1 are enqueued to the unschedulable Pod pool. for _, pod := range []*v1.Pod{unschedulablePodInfo.Pod, highPriorityPodInfo.Pod, hpp2} { if q.unschedulablePods.get(pod) == nil { t.Errorf(\"Expected %v in the unschedulablePods\", pod.Name) } } if _, ok, _ := q.podBackoffQ.Get(hpp1QueuedPodInfo); !ok { t.Errorf(\"Expected %v in the podBackoffQ\", hpp1.Name) } // Move clock by podInitialBackoffDuration, so that pods in the unschedulablePods would pass the backing off, // and the pods will be moved into activeQ. c.Step(q.podInitialBackoffDuration) q.flushBackoffQCompleted(logger) // flush the completed backoffQ to move hpp1 to activeQ. q.MoveAllToActiveOrBackoffQueue(logger, NodeAdd, nil, nil, nil) if q.activeQ.Len() != 4 { t.Errorf(\"Expected 4 items to be in activeQ, but got: %v\", q.activeQ.Len()) } if q.podBackoffQ.Len() != 0 { t.Errorf(\"Expected 0 item to be in podBackoffQ, but got: %v\", q.podBackoffQ.Len()) } if len(q.unschedulablePods.podInfoMap) != 1 { // hpp2 won't be moved regardless of its backoff timer. t.Errorf(\"Expected 1 item to be in unschedulablePods, but got: %v\", len(q.unschedulablePods.podInfoMap)) } } </ins> func clonePod(pod *v1.Pod, newName string) *v1.Pod { pod = pod.DeepCopy() pod.Name = newName", "positive_passages": [{"docid": "doc-en-kubernetes-067de3b7865dcc26d5939903adfdfd6f426066e830ffff2d268cf1b31c889111", "text": "ref: /sig scheduling /kind cleanup Part of: The unit test in the scheduling queue only assumes the case where the queueing hint is enabled. We should make another unit test to confirm works without QHint. should have been existing since before we introduced QHint. So, just bring the old one back should be fine.\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/priority important-soon\n/assign", "commid": "kubernetes_issue_122304", "tokennum": 162}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b9432ce3b6c9d0765b254d53f3437344d14ceacfd802207b94f90cdb3881f8c1", "query": "*out = new(PluginSet) (*in).DeepCopyInto(*out) } <del> if in.NormalizeScore != nil { in, out := &in.NormalizeScore, &out.NormalizeScore *out = new(PluginSet) (*in).DeepCopyInto(*out) } </del> if in.Reserve != nil { in, out := &in.Reserve, &out.Reserve *out = new(PluginSet)", "positive_passages": [{"docid": "doc-en-kubernetes-65d9c28fb77fe0bb882df060209fc22bf399af9c3b9dfe5829b0e5a45dc20b3d", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Consolidate ) into Score plugin set in config API. Why is this needed: NormalizeScore extension point is implemented in . We decided to treat NormalizeScore as an \"optional\" step of Score plugin, see . However, we deferred the removal of due to API review delays. Now that PR was merged. We can start the actual removal from the API and start the API review process. /sig scheduling\n/assign", "commid": "kubernetes_issue_80908", "tokennum": 113}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b950db1188ea1ea0ad61fef05a3b191d87f0cddae5477103b91ea19c98a03e65", "query": "return utilfile.FileExists(kubeletpath) } <ins> func (mounter *NsenterMounter) EvalHostSymlinks(pathname string) (string, error) { return mounter.ne.EvalSymlinks(pathname, true) } </ins> func (mounter *NsenterMounter) CleanSubPaths(podDir string, volumeName string) error { return doCleanSubPaths(mounter, podDir, volumeName) }", "positive_passages": [{"docid": "doc-en-kubernetes-226c0928db9d5aa6f1446838b8788eb7c60cd41b1b8246f4bd1a4e2614bb7834", "text": "/kind bug Using , if a block device is symlinked to the discovery directory e.g. , then MapVolume will fail with since the containerized kubelet cannot see the path on host. is mounted by containerized kubelet, so if before we try to map the device we set devicePath to the evaluation of symlink and end up with a devicePath of , containerized kubelet will see the device and successfully map the device. Are there any issues with this solution? This is on Kubernetes 1.10\n/sig storage\nah yes containerized kubelet has many issues when dealing with symlinks. Check out Mounter.GetMode(), it calls a nsenter EvalSymlinks which should be able to do what you need. But actually, one thing to consider, is do you need to do the losetup on the host, or does inside the container work?\nYes it appears to work from inside the container, on the host I run which disappears after I delete the pod using the device. My understanding of running losetup in MapVolume is not that great but I suppose that as long as that /dev/loop0 is created we are fine. Thanks for the quick response, I'll create a PR using that function and tag you\nDoes it create it on the host or in the containerized kubelet? What happens when containerized kubelet is restarted? The purpose of losetup is to do \"refcounting\" on the block device to prevent possible naming collisions when devices are attached/detached under unhealthy conditions. Ie, if a device showed up as /dev/sdb and you gave that to a pod, and then for some reason it become unhealthy and disappeared (while the pod is still running), another device (maybe even another volume type) could get attached to the node and reuse /dev/sdb. Now the pod has access to a device it's not supposed to. With filesystem volumes, the refcounting is done with mount points, but for block device, loopback is the equivalent.\nIt is created on the host (and also visible in the container), and stays around through restart. I understand now, thank you.\nActually after I restart it becomes /vdb instead of /dev/vdb in the losetup output, idk what that is about.", "commid": "kubernetes_issue_65445", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b950db1188ea1ea0ad61fef05a3b191d87f0cddae5477103b91ea19c98a03e65", "query": "return utilfile.FileExists(kubeletpath) } <ins> func (mounter *NsenterMounter) EvalHostSymlinks(pathname string) (string, error) { return mounter.ne.EvalSymlinks(pathname, true) } </ins> func (mounter *NsenterMounter) CleanSubPaths(podDir string, volumeName string) error { return doCleanSubPaths(mounter, podDir, volumeName) }", "positive_passages": [{"docid": "doc-en-kubernetes-e6271b0ba1dda755d5bb536a727016a621c7c29c599386bc1e9c22a230980cbf", "text": "There is no such thing as /vdb and /dev/vdb is still intact of course. Seems inconsequential since it is disappearing after all pods using the device are deleted, i.e. it's still serving as a refcounter", "commid": "kubernetes_issue_65445", "tokennum": 55}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b951a364599acb518308610e72812a19d9fe1076cb73e31fc457379aa5a8978d", "query": "// Max amount of time to wait for the container runtime to come up. maxWaitForContainerRuntime = 30 * time.Second <ins> // Max amount of time to wait for node list/watch to initially sync maxWaitForAPIServerSync = 10 * time.Second </ins> // nodeStatusUpdateRetry specifies how many times kubelet retries when posting node status failed. nodeStatusUpdateRetry = 5", "positive_passages": [{"docid": "doc-en-kubernetes-8476bba8e23a7ed885cd34c1077ce17dbf12901ac7ae9725333264f6ea8cfdae", "text": "What happened: A deployment is created that uses a after the cluster master is created but before the cluster worker nodes are fully initialized. During the initialization of the worker nodes, the nodes are temporarily available for scheduling without the necessary label to match the deployment's node selector. Depending on how long the nodes are available for scheduling without the necessary node labels for the deployment, the scheduler will start to spam with cluster with pods in status. This spamming stops once the worker nodes are fully initialized and the pods are scheduled successful. The exact timing of all of this is TBD. What you expected to happen: Pods in status are annoying and require manual cleanup. It would be preferred that the scheduler avoid this an simply issue warning events. How to reproduce it (as minimally and precisely as possible): See issue description. Anything else we need to know?: No. Environment: Kubernetes version (use ): 1.18.3 Cloud provider or hardware configuration: IBM Cloud Kubernetes Service OS (e.g: ): Ubuntu 18.04.4 LTS Kernel (e.g. ): 4.15.0-96-generic Install tools: Managed service install Network plugin and version (if this is a network-related bug): N/A Others: N/A\nRelated to and\n/sig scheduling\nby spamming are you referring to scheduler logs? also, why are the nodes not labelled from the get go?\nJust to confirm, all the pods in question are still in Pending state, yes? If the pods are in pending state, all of them will get scheduled eventually once the nodes get their labels.\nThe pods are not in state. They are actually in state. The pods eventually get scheduled but we are left with anywhere from a few to dozens of these state pods. Also, we are looking at labeling the nodes via kubelet flags to see if that helps.\n/remove-kind bug\nAfter we add some retry logic and wait time in this problem can be solved: As you can see this function returns initial node as the first request failed.\nI also get hit by this, when single controller node gets rebooted and scheduler starts as static container before kubelet becomes ready.", "commid": "kubernetes_issue_92067", "tokennum": 465}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b951a364599acb518308610e72812a19d9fe1076cb73e31fc457379aa5a8978d", "query": "// Max amount of time to wait for the container runtime to come up. maxWaitForContainerRuntime = 30 * time.Second <ins> // Max amount of time to wait for node list/watch to initially sync maxWaitForAPIServerSync = 10 * time.Second </ins> // nodeStatusUpdateRetry specifies how many times kubelet retries when posting node status failed. nodeStatusUpdateRetry = 5", "positive_passages": [{"docid": "doc-en-kubernetes-6c53201dbb91d52a8ade960092a5ed582f4d35e33a53b75d555d15ae815dc25c", "text": "Can be cleaned up with:\n/sig node\nthe spam cycle is this loop: \"pod create, pod schedule, worker reject, pod failed\" -- we don't have a lot of protection in higher level workload controllers to handle pods that fail at kubelet admission time versus pods that just dont create due to quota/admission. in general, is the spam causing any other stability issues? is pod gc pruning the pods?\nI wonder if we can do a trick in node lister to mitigate any race condition here...\nwe could maybe do something similar to to ensure node lister has synced...\nhacking on option to ensure if kubelet has a node lister with a valid kube client, we wait for it to sync at least once here which should mitigate this issue. see:\nWe noticed the problem on the OLM pod which is managed by the OLM operator. Right or wrong, the operator does not like seeing the pod go to status and no longer reconciles the pod. The end result is that manual intervention (i.e. pod deletion) is required to fix the problem.\nsure... i would have thought the pod is failed in that instance and reached a terminal state. either way, i am looking at what i can do to mitigate this.\nThe problem persists in our environment as well, and the workaround cited above will not do anymore. Is there something in the works for this one?\nIssues 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\n/remove-lifecycle stale", "commid": "kubernetes_issue_92067", "tokennum": 383}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b95cd2aa93dfa63928719fbcce3767ad951e5c681db6ea632836c4cbf22e627e", "query": "return true, nil } <del> // nextRotationDeadline returns a value for the threshold at which the // current certificate should be rotated, 80%+/-10% of the expiration of the // certificate. func (m *manager) nextRotationDeadline() time.Time { // forceRotation is not protected by locks if m.forceRotation { m.forceRotation = false return time.Now() } m.certAccessLock.RLock() defer m.certAccessLock.RUnlock() </del> <ins> // Check that the current certificate on disk satisfies the requests from the // current template. // // Note that extra items in the certificate's SAN or orgs that don't exist in // the template will not trigger a renewal. // // Requires certAccessLock to be locked. func (m *manager) certSatisfiesTemplateLocked() bool { </ins> if m.cert == nil { <del> return time.Now() </del> <ins> return false </ins> } <del> // Ensure the currently held certificate satisfies the requested subject CN and SANs </del> if template := m.getTemplate(); template != nil { if template.Subject.CommonName != m.cert.Leaf.Subject.CommonName { <del> glog.V(2).Infof(\"Current certificate CN (%s) does not match requested CN (%s), rotating now\", m.cert.Leaf.Subject.CommonName, template.Subject.CommonName) return time.Now() </del> <ins> glog.V(2).Infof(\"Current certificate CN (%s) does not match requested CN (%s)\", m.cert.Leaf.Subject.CommonName, template.Subject.CommonName) return false </ins> } currentDNSNames := sets.NewString(m.cert.Leaf.DNSNames...) desiredDNSNames := sets.NewString(template.DNSNames...) missingDNSNames := desiredDNSNames.Difference(currentDNSNames) if len(missingDNSNames) > 0 { <del> glog.V(2).Infof(\"Current certificate is missing requested DNS names %v, rotating now\", missingDNSNames.List()) return time.Now() </del> <ins> glog.V(2).Infof(\"Current certificate is missing requested DNS names %v\", missingDNSNames.List()) return false </ins> } currentIPs := sets.NewString()", "positive_passages": [{"docid": "doc-en-kubernetes-8be37f8ebf3b929ba13e3d88ac8f62b2b24f9ed008212f39c0aaa7e2ec850c18", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: I'm testing the new option in kubernetes 1.12 and it seems that kubelet always requests the signing of a new CSR and tries to rotate the certificates when it is started. This is happening even though there's a valid (brand new) certificate on disk issued by kube-controller-manager. From what I can tell, this is happening because kubelet implements and is set after a successful certificate rotation, but is never persisted to disk. If kubelet is restarted, then the last requested CSR is nil. What you expected to happen: Ideally, kubelet should only request the signing of a new CSR if it doesn't already have a serving certificate or it's about to expire. How to reproduce it (as minimally and precisely as possible): Restart a kubelet instance that had it's serving certificate issued by kube-controller-manager Check and see that it requested the signing of a new CSR Anything else we need to know?: kubelet is being run with . , , and are all omitted to use the default values. The TLS bootstrapping for client certificates is currently not being used--just the bootstrapping for serving certificates. Environment: Kubernetes version: v1.12.0 - built from source at the tag () Cloud provider or hardware configuration: Bare metal OS: CentOS 7.5.1804 Kernel: Install tools: Custom RPMs built from this git repo with no additional patches Others:\n/sig node\n/sig auth\nNot sure if this is the ideal fix, but I've patched it so that it compares the current CSR template to the last requested template only if it doesn't already match the current cert.\ncc\nthanks for the proposed fix. I think it looks good. Could you send a PR? We should also remove entirely and only look at current cert and template. does that sound reasonable?\nSure thing, I'd be happy to do that. EDIT: I will submit a PR after approval from my employer.\nI think that's probably ok, as long as it checks everything we include in the template and we consider a certificate missing anything we request to be cause for re-requesting another cert (an issuer couldn't choose to issue a cert that drops some SANs and us not request another cert) left some comments in\nThis regression is a frequent flyer.", "commid": "kubernetes_issue_69471", "tokennum": 523}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b95cd2aa93dfa63928719fbcce3767ad951e5c681db6ea632836c4cbf22e627e", "query": "return true, nil } <del> // nextRotationDeadline returns a value for the threshold at which the // current certificate should be rotated, 80%+/-10% of the expiration of the // certificate. func (m *manager) nextRotationDeadline() time.Time { // forceRotation is not protected by locks if m.forceRotation { m.forceRotation = false return time.Now() } m.certAccessLock.RLock() defer m.certAccessLock.RUnlock() </del> <ins> // Check that the current certificate on disk satisfies the requests from the // current template. // // Note that extra items in the certificate's SAN or orgs that don't exist in // the template will not trigger a renewal. // // Requires certAccessLock to be locked. func (m *manager) certSatisfiesTemplateLocked() bool { </ins> if m.cert == nil { <del> return time.Now() </del> <ins> return false </ins> } <del> // Ensure the currently held certificate satisfies the requested subject CN and SANs </del> if template := m.getTemplate(); template != nil { if template.Subject.CommonName != m.cert.Leaf.Subject.CommonName { <del> glog.V(2).Infof(\"Current certificate CN (%s) does not match requested CN (%s), rotating now\", m.cert.Leaf.Subject.CommonName, template.Subject.CommonName) return time.Now() </del> <ins> glog.V(2).Infof(\"Current certificate CN (%s) does not match requested CN (%s)\", m.cert.Leaf.Subject.CommonName, template.Subject.CommonName) return false </ins> } currentDNSNames := sets.NewString(m.cert.Leaf.DNSNames...) desiredDNSNames := sets.NewString(template.DNSNames...) missingDNSNames := desiredDNSNames.Difference(currentDNSNames) if len(missingDNSNames) > 0 { <del> glog.V(2).Infof(\"Current certificate is missing requested DNS names %v, rotating now\", missingDNSNames.List()) return time.Now() </del> <ins> glog.V(2).Infof(\"Current certificate is missing requested DNS names %v\", missingDNSNames.List()) return false </ins> } currentIPs := sets.NewString()", "positive_passages": [{"docid": "doc-en-kubernetes-1b55ad000b296f12b046608a2d187d8503e900f5b67dbcaa87fc7ef8e9366d19", "text": "I'd love to see an integration test that would catch this (but that shouldn't block a fix).\nThanks for the comments! Now that I have the CLA signed, I'll address those and submit a PR.\nJust submitted the PR:", "commid": "kubernetes_issue_69471", "tokennum": 53}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b95e5bf5be104c99fb48819005d34a9717d1abf73e4aa919b6c4af0232220bf4", "query": "Expect(events.Items[1].Message).Should(Equal(fmt.Sprintf(\"Scaled down rc %s to 0\", rcName))) } <ins> func testRecreateDeployment(f *Framework) { ns := f.Namespace.Name c := f.Client // Create nginx pods. deploymentPodLabels := map[string]string{\"name\": \"sample-pod-3\"} rcPodLabels := map[string]string{ \"name\": \"sample-pod-3\", \"pod\":  \"nginx\", } rcName := \"nginx-controller\" replicas := 3 _, err := c.ReplicationControllers(ns).Create(newRC(rcName, replicas, rcPodLabels, \"nginx\", \"nginx\")) Expect(err).NotTo(HaveOccurred()) defer func() { Logf(\"deleting replication controller %s\", rcName) Expect(c.ReplicationControllers(ns).Delete(rcName)).NotTo(HaveOccurred()) }() // Verify that the required pods have come up. err = verifyPods(c, ns, \"sample-pod-3\", false, 3) if err != nil { Logf(\"error in waiting for pods to come up: %s\", err) Expect(err).NotTo(HaveOccurred()) } // Create a deployment to delete nginx pods and instead bring up redis pods. deploymentName := \"redis-deployment-3\" Logf(\"Creating deployment %s\", deploymentName) _, err = c.Deployments(ns).Create(newDeployment(deploymentName, replicas, deploymentPodLabels, \"redis\", \"redis\", extensions.RecreateDeploymentStrategyType)) Expect(err).NotTo(HaveOccurred()) defer func() { deployment, err := c.Deployments(ns).Get(deploymentName) Expect(err).NotTo(HaveOccurred()) Logf(\"deleting deployment %s\", deploymentName) Expect(c.Deployments(ns).Delete(deploymentName, nil)).NotTo(HaveOccurred()) // TODO: remove this once we can delete rcs with deployment newRC, err := deploymentutil.GetNewRC(*deployment, c) Expect(err).NotTo(HaveOccurred()) Expect(c.ReplicationControllers(ns).Delete(newRC.Name)).NotTo(HaveOccurred()) }() err = waitForDeploymentStatus(c, ns, deploymentName, replicas, 0, replicas, 0) Expect(err).NotTo(HaveOccurred()) // Verify that the pods were scaled up and down as expected. We use events to verify that. deployment, err := c.Deployments(ns).Get(deploymentName) Expect(err).NotTo(HaveOccurred()) waitForEvents(c, ns, deployment, 2) events, err := c.Events(ns).Search(deployment) if err != nil { Logf(\"error in listing events: %s\", err) Expect(err).NotTo(HaveOccurred()) } // There should be 2 events, one to scale up the new RC and then to scale down the old RC. Expect(len(events.Items)).Should(Equal(2)) newRC, err := deploymentutil.GetNewRC(*deployment, c) Expect(err).NotTo(HaveOccurred()) Expect(newRC).NotTo(Equal(nil)) Expect(events.Items[0].Message).Should(Equal(fmt.Sprintf(\"Scaled down rc %s to 0\", rcName))) Expect(events.Items[1].Message).Should(Equal(fmt.Sprintf(\"Scaled up rc %s to 3\", newRC.Name))) } </ins> // testRolloverDeployment tests that deployment supports rollover. // i.e. we can change desired state and kick off rolling update, then change desired state again before it finishes. func testRolloverDeployment(f *Framework) {", "positive_passages": [{"docid": "doc-en-kubernetes-ceb20554e653f6657baad1bbb36c40e66d8a76887956e3c674b77febc82d4455", "text": "There's some practical limit on the number of concurrent access tokens that can be used in a Kubernetes cluster before it begins to spend all of its time in the authn stack verifying them. Absent fixes to it was < 500; with the fixes linked there it's still not infinitely scalable-- I still hit (what I believe to be) with ~ 5k unique tokens @ ~700QPS. This request is to this dimension an official name & definition, and list it with others, e.g. here: it it have a useful value (I think it should be 10k) /kind bug /sig scalability\n/cc\noh and 4. add tests which verify it is as high as believed.\ncc since projected tokens will increase the number of unique tokens\n/sig auth\nLRUs are not good at scaling and sharding has some major pitfalls as pointed out. I would suggest that we try to drop the LRU cache for successful authentication results in the token cache. The main benefit of using an LRU here is bound cache size. Entries in the token cache have a fast expiration independent of the LRU policy. The records probably take up O(2kb) (guesstimate) of memory. Given that these are successful attempts with presumably valid tokens, I don't think we are getting any benefit from the LRU. If we don't have a constraint on fixed cache size, we can back the token cache with a sync.Map and run a single background goroutine to periodically walk the map and remove expired entries. This would fix the problematic locking and eviction due to nonuniform distribution of tokens over shards. The failure cache is less important and we don't cache failures by default. If we consider this the \"slowpath\", we can probably leave it as. If that's not good enough, we have a couple options (with various tradeoffs) to improve it.\nIf off by default is not enough, more reasoning why the failed cache is not super useful: it might help with an accidental DoS but it doesn't prevent anything actively malicious DoS. I think we can focus our improvements on the success cache.\n/assign He is already working on adding an explicit test for it.\nhas taken it over and is actively working on this. Unfortunately, I cannot assign this issue to him as he's not a k8s member yet\nIt's not closed - all testes must be submitted and appropriate documentation must be\nThanks everyone!!", "commid": "kubernetes_issue_83375", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b9aa3f8bab58a1189b150b599c6e4079ddf843d4512317473c7d911999f3308c", "query": "Create-Directories Download-HelperScripts <del> Install-LoggingAgent Configure-LoggingAgent Restart-LoggingAgent </del> <ins> # Even if Stackdriver is already installed, the function will still [re]start the service. if (IsLoggingEnabled $kube_env) { Install-LoggingAgent Configure-LoggingAgent Restart-LoggingAgent } </ins> Create-DockerRegistryKey Configure-Dockerd", "positive_passages": [{"docid": "doc-en-kubernetes-c5ab0587303441aa15d1f99cf54443dd34979e6a47a9667d6d352ed63897253b", "text": "What happened: The stackdriver logging agent is installed and start running no matter logging is enabled/disabled in the cluster or not. What you expected to happen: Do not install and start the logging agent if logging is disabled.\n/sig windows\ncc", "commid": "kubernetes_issue_81299", "tokennum": 51}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b9bc27f0e1538f3438ef92d7392e28b1226db965a63130be5a3e1a32d8474198", "query": "BeforeEach(func() { podClient = f.PodClient() }) <del> // TODO: Fix Flaky issue #68066 and then re-add this back into Conformance Suite </del> /* <del> Release : v1.9 </del> <ins> Release : v1.15 </ins> Testname: Pods, delete grace period <del> Description: Create a pod, make sure it is running, create a watch to observe Pod creation. Create a 'kubectl local proxy', capture the port the proxy is listening. Using the http client send a \u2018delete\u2019 with gracePeriodSeconds=30. Pod SHOULD get deleted within 30 seconds. </del> <ins> Description: Create a pod, make sure it is running. Create a 'kubectl local proxy', capture the port the proxy is listening. Using the http client send a \u2018delete\u2019 with gracePeriodSeconds=30. Pod SHOULD get deleted within 30 seconds. </ins> */ <del> It(\"should be submitted and removed  [Flaky]\", func() { </del> <ins> framework.ConformanceIt(\"should be submitted and removed\", func() { </ins> By(\"creating the pod\") name := \"pod-submit-remove-\" + string(uuid.NewUUID()) value := strconv.Itoa(time.Now().Nanosecond())", "positive_passages": [{"docid": "doc-en-kubernetes-30eea2f2891480afb1ab3afc376d0efcc64938c80ac22e3ecb844909d4b7762a", "text": "We need to fix this potentially flaky test and add it back to conformance suite. Please see discussion in Also waiting on:\ncc /sig testing\n/area conformance\n/cc\nIssues 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\n/remove-lifecycle stale\ncan we convert it to conformance now??\nOnce 1.15 opens up", "commid": "kubernetes_issue_68066", "tokennum": 132}], "negative_passages": []}
{"query_id": "q-en-kubernetes-b9f9d7f0712875f8da480f7f26fc20b8ce77107e88e7a1780b081a4fe0299945", "query": "// be made to pass by removing pods, or you change an existing predicate so that // it can never be made to pass by removing pods, you need to add the predicate // failure error in nodesWherePreemptionMightHelp() in scheduler/core/generic_scheduler.go <del> ErrDiskConflict                          = newPredicateFailureError(\"NoDiskConflict\") ErrVolumeZoneConflict                    = newPredicateFailureError(\"NoVolumeZoneConflict\") ErrNodeSelectorNotMatch                  = newPredicateFailureError(\"MatchNodeSelector\") ErrPodAffinityNotMatch                   = newPredicateFailureError(\"MatchInterPodAffinity\") ErrPodAffinityRulesNotMatch              = newPredicateFailureError(\"PodAffinityRulesNotMatch\") ErrPodAntiAffinityRulesNotMatch          = newPredicateFailureError(\"PodAntiAffinityRulesNotMatch\") ErrExistingPodsAntiAffinityRulesNotMatch = newPredicateFailureError(\"ExistingPodsAntiAffinityRulesNotMatch\") ErrTaintsTolerationsNotMatch             = newPredicateFailureError(\"PodToleratesNodeTaints\") ErrPodNotMatchHostName                   = newPredicateFailureError(\"HostName\") ErrPodNotFitsHostPorts                   = newPredicateFailureError(\"PodFitsHostPorts\") ErrNodeLabelPresenceViolated             = newPredicateFailureError(\"CheckNodeLabelPresence\") ErrServiceAffinityViolated               = newPredicateFailureError(\"CheckServiceAffinity\") ErrMaxVolumeCountExceeded                = newPredicateFailureError(\"MaxVolumeCount\") ErrNodeUnderMemoryPressure               = newPredicateFailureError(\"NodeUnderMemoryPressure\") ErrNodeUnderDiskPressure                 = newPredicateFailureError(\"NodeUnderDiskPressure\") ErrNodeOutOfDisk                         = newPredicateFailureError(\"NodeOutOfDisk\") ErrNodeNotReady                          = newPredicateFailureError(\"NodeNotReady\") ErrNodeNetworkUnavailable                = newPredicateFailureError(\"NodeNetworkUnavailable\") ErrNodeUnschedulable                     = newPredicateFailureError(\"NodeUnschedulable\") ErrNodeUnknownCondition                  = newPredicateFailureError(\"NodeUnknownCondition\") ErrVolumeNodeConflict                    = newPredicateFailureError(\"VolumeNodeAffinityConflict\") ErrVolumeBindConflict                    = newPredicateFailureError(\"VolumeBindingNoMatch\") </del> <ins> ErrDiskConflict                          = newPredicateFailureError(\"NoDiskConflict\", \"node(s) had no available disk\") ErrVolumeZoneConflict                    = newPredicateFailureError(\"NoVolumeZoneConflict\", \"node(s) had no available volume zone\") ErrNodeSelectorNotMatch                  = newPredicateFailureError(\"MatchNodeSelector\", \"node(s) didn't match node selector\") ErrPodAffinityNotMatch                   = newPredicateFailureError(\"MatchInterPodAffinity\", \"node(s) didn't match pod affinity/anti-affinity\") ErrPodAffinityRulesNotMatch              = newPredicateFailureError(\"PodAffinityRulesNotMatch\", \"node(s) didn't match pod affinity rules\") ErrPodAntiAffinityRulesNotMatch          = newPredicateFailureError(\"PodAntiAffinityRulesNotMatch\", \"node(s) didn't match pod anti-affinity rules\") ErrExistingPodsAntiAffinityRulesNotMatch = newPredicateFailureError(\"ExistingPodsAntiAffinityRulesNotMatch\", \"node(s) didn't satisfy existing pods anti-affinity rules\") ErrTaintsTolerationsNotMatch             = newPredicateFailureError(\"PodToleratesNodeTaints\", \"node(s) had taints that the pod didn't tolerate\") ErrPodNotMatchHostName                   = newPredicateFailureError(\"HostName\", \"node(s) didn't match the requested hostname\") ErrPodNotFitsHostPorts                   = newPredicateFailureError(\"PodFitsHostPorts\", \"node(s) didn't have free ports for the requested pod ports\") ErrNodeLabelPresenceViolated             = newPredicateFailureError(\"CheckNodeLabelPresence\", \"node(s) didn't have the requested labels\") ErrServiceAffinityViolated               = newPredicateFailureError(\"CheckServiceAffinity\", \"node(s) didn't match service affinity\") ErrMaxVolumeCountExceeded                = newPredicateFailureError(\"MaxVolumeCount\", \"node(s) exceed max volume count\") ErrNodeUnderMemoryPressure               = newPredicateFailureError(\"NodeUnderMemoryPressure\", \"node(s) had memory pressure\") ErrNodeUnderDiskPressure                 = newPredicateFailureError(\"NodeUnderDiskPressure\", \"node(s) had disk pressure\") ErrNodeOutOfDisk                         = newPredicateFailureError(\"NodeOutOfDisk\", \"node(s) were out of disk space\") ErrNodeNotReady                          = newPredicateFailureError(\"NodeNotReady\", \"node(s) were not ready\") ErrNodeNetworkUnavailable                = newPredicateFailureError(\"NodeNetworkUnavailable\", \"node(s) had unavailable network\") ErrNodeUnschedulable                     = newPredicateFailureError(\"NodeUnschedulable\", \"node(s) were unschedulable\") ErrNodeUnknownCondition                  = newPredicateFailureError(\"NodeUnknownCondition\", \"node(s) had unknown conditions\") ErrVolumeNodeConflict                    = newPredicateFailureError(\"VolumeNodeAffinityConflict\", \"node(s) had volume node affinity conflict\") ErrVolumeBindConflict                    = newPredicateFailureError(\"VolumeBindingNoMatch\", \"node(s) didn't find available persistent volumes to bind\") </ins> // ErrFakePredicate is used for test only. The fake predicates returning false also returns error // as ErrFakePredicate. <del> ErrFakePredicate = newPredicateFailureError(\"FakePredicateError\") </del> <ins> ErrFakePredicate = newPredicateFailureError(\"FakePredicateError\", \"Nodes failed the fake predicate\") </ins> ) // InsufficientResourceError is an error type that indicates what kind of resource limit is", "positive_passages": [{"docid": "doc-en-kubernetes-10c13016eb5239afc7a330cfdab91dbf78232a49f2993f71669df735dbb939e1", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature The is not user friendly. There has been to make it better, but we still print in the pending message. We should change these errors to a more human readable message. For example, should be changed to something like . /sig scheduling", "commid": "kubernetes_issue_58546", "tokennum": 91}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ba3cc71293425b2866de7c94da9fba90610d9a91dd8bc211f96463bdc9e1497c", "query": "// ValidateCSINodeDrivers tests that the specified CSINodeDrivers have valid data. func validateCSINodeDrivers(drivers []storage.CSINodeDriver, fldPath *field.Path, validationOpts CSINodeValidationOptions) field.ErrorList { allErrs := field.ErrorList{} <del> driverNamesInSpecs := make(sets.String) </del> <ins> driverNamesInSpecs := sets.New[string]() </ins> for i, driver := range drivers { idxPath := fldPath.Index(i) allErrs = append(allErrs, validateCSINodeDriver(driver, driverNamesInSpecs, idxPath, validationOpts)...)", "positive_passages": [{"docid": "doc-en-kubernetes-c6679bcd8f59ea95eb0b6a4e2bf394545d09b32db20c61705567c0727bbb7817", "text": "It seems to be valid to add here. Would you like to open a pull request for it? this is like a cleanup, as the set insert will skip and the validation will do twice. is used to track bugs. I suggest you open a PR for that if you like.\n/sig storage\nI think adding ` == true and we didn't skip, it will insert set twice I believe? wasn't notice that at first glance. However, I can file a PR now\n/triage accepted\nThe label cannot be applied. Only GitHub organization members can add the label. <detailsIn response to : /triage accepted 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\n/triage accepted\nPlease feel free to submit a PR.", "commid": "kubernetes_issue_117027", "tokennum": 176}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ba767ac21fd089e7575dff088c09c108566a651f3d84cd52a921a99d67c1a972", "query": "} func (a genericAccessor) SetAnnotations(annotations map[string]string) { <ins> if a.annotations == nil { emptyAnnotations := make(map[string]string) a.annotations = &emptyAnnotations } </ins> *a.annotations = annotations }", "positive_passages": [{"docid": "doc-en-kubernetes-5d8539be161cacf223528437869590f13423a31b1176c381211bcba6b79e0cca", "text": "When trying to edit multiple resources, for example: will panic. Ref as the possible cause cc\nif was the cause, any fix needs to happen in 1.1 as well, was already cherry picked there\nAlso shows that we need a test for this case.\nis the cause. When we edit multiple resources (i.e., list-type objects), the list's Accessor.annotations (type ) is nil and will panic when UpdateApplyAnnotation tries to SetAnnotations ().", "commid": "kubernetes_issue_15907", "tokennum": 108}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ba9204ab3e9225584a90bce27ad6b567525823815c98b4cc1de77ef59a9b8cb3", "query": "maxBackOffTolerance  = time.Duration(1.3 * float64(kubelet.MaxContainerBackOff)) podRetryPeriod       = 1 * time.Second podRetryTimeout      = 1 * time.Minute <ins> podReadyTimeout      = 1 * time.Minute </ins> ) // testHostIP tests that a pod gets a host IP", "positive_passages": [{"docid": "doc-en-kubernetes-a4e08d4660e59e77b869eee3e8c161e5e01175b90d68e1077fd3e84d4f4d567b", "text": "[x] Original approval issue: - Reverted due to flakes [x] Two weeks soak end date: 20 November 2020 This issue is created to allow edit by /wip /hold According to this APIsnoop query, there are still some remaining Pod endpoints which are untested. a Pod with a static label the Pod with a new Label and updated data the Pod to ensure it's patched the Pod's status the Pod's status Ready condition to False the Pod's status to check if Ready is False all Pods in all Namespaces find the Pod(1) ensure that the Pod is found and is patched Namespaced Pod(1) via a Collection with a LabelSelector the Pod to check that it's deleted Discover useragents: List endpoints hit by the test: Display endpoint coverage change: If a test with these calls gets merged, test coverage will go up by 4 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance\n/reopen Test PR Merge Promotion PR to be created next\nReopened this issue. <detailsIn response to : /reopen Test PR Merge Promotion PR to be created next 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\nreverted by due to flaky test\nIssues 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\n/remove-lifecycle stale\n/reopen PR on test grid for 2 weeks before promotion to conformance\nReopened this issue. <detailsIn response to : /reopen PR on test grid for 2 weeks before promotion to conformance 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\n/triage accepted", "commid": "kubernetes_issue_90936", "tokennum": 449}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ba92e4b8b15b20b97c97c76d64e276165332e7f618223e533ff6e8ad52fcd33e", "query": "scheme := runtime.NewScheme() scheme.AddKnownTypes(cmResource.GroupVersion(), &v1.ConfigMap{}) codecs := serializer.NewCodecFactory(scheme) <del> o := NewFieldManagedObjectTracker(scheme, codecs.UniversalDecoder(), fakeTypeConverter) </del> <ins> o := NewFieldManagedObjectTracker(scheme, codecs.UniversalDecoder(), configMapTypeConverter(scheme)) </ins> reaction := ObjectReaction(o) patch := []byte(`{\"apiVersion\": \"v1\", \"kind\": \"ConfigMap\", \"metadata\": {\"name\": \"cm-1\"}, \"data\": {\"k\": \"v\"}}`)", "positive_passages": [{"docid": "doc-en-kubernetes-29db4d0749071d4e54a9083e12a93fb8b6b43cd54c28626ec2efc45861483a16", "text": "Smoke tests run by publishing-bot on client-go master are failing Ref for failure logs: Tests defined for client-go, after publishing, Since commit No response As part of , when module is used from within the staging directory, can be used by traversing to the parent directory. But once the module is made as a separate repository as part of publishing, then traversing to repository using path will not work. No response /sig-api-machinery\n/sig api-machinery\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /sig api-machinery 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\nLooking\nI'll remove the swagger file dependency, I don't think we strictly need it.\n/triage accepted", "commid": "kubernetes_issue_125704", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bab496a4f0fb5a261d011439e8e8216a28f98c5d9843362f3a2532a012b1d150", "query": "newDevicePath := \"\" <del> err = wait.Poll(1*time.Second, timeout, func() (bool, error) { </del> <ins> err = wait.PollImmediate(1*time.Second, timeout, func() (bool, error) { </ins> if newDevicePath, err = findDiskByLun(int(lun), io, exec); err != nil { return false, fmt.Errorf(\"azureDisk - WaitForAttach ticker failed node (%s) disk (%s) lun(%v) err(%s)\", nodeName, diskName, lun, err) }", "positive_passages": [{"docid": "doc-en-kubernetes-9945f53575b60dc39792ed32e02eb9c66a039731b5284891454b6dce2289c963", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: When starting pods with AFS volumes, there is an initial delay of five seconds until the pod is transitioning from the \"Scheduled\" state. The reason for this is that currently the volume mounting happens inside a wait.Poll which will initially wait a specified interval (currently 5 seconds) before execution. Event log for comparison with and without AFS volume attached (seconds since event): What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others: /assign /priority important-soon /sig cloud-provider /area provider/azure\nsee", "commid": "kubernetes_issue_93025", "tokennum": 233}], "negative_passages": []}
{"query_id": "q-en-kubernetes-babaf9254e0269814d1ea1b1eb97de10827b9e9acd7e6a4c851f885953482ae2", "query": "} } <del> // OpenAPIv3 type/maxLength/maxItems/MaxProperties/required/wrong type field validation failures are viewed as blocking err for CEL validation </del> <ins> // OpenAPIv3 type/maxLength/maxItems/MaxProperties/required/enum violation/wrong type field validation failures are viewed as blocking err for CEL validation </ins> func hasBlockingErr(errs field.ErrorList) (bool, *field.Error) { for _, err := range errs { <del> if err.Type == field.ErrorTypeRequired || err.Type == field.ErrorTypeTooLong || err.Type == field.ErrorTypeTooMany || err.Type == field.ErrorTypeTypeInvalid { </del> <ins> if err.Type == field.ErrorTypeNotSupported || err.Type == field.ErrorTypeRequired || err.Type == field.ErrorTypeTooLong || err.Type == field.ErrorTypeTooMany || err.Type == field.ErrorTypeTypeInvalid { </ins> return true, field.Invalid(nil, nil, \"some validation rules were not checked because the object was invalid; correct the existing errors to complete validation\") } }", "positive_passages": [{"docid": "doc-en-kubernetes-d87f35a9862b77934b500147b1ec4bb0e958c531e2fdcae282b21499e2f51131", "text": "pointed out to me that a CEL x-kubernetes-validations rule in a CRD was hitting the estimated cost limit when performing a simple \"string has prefix\" check on an en enum field. Putting a limit in the OpenAPI of the enum string field fixed the problem, but having to add a limit like this is counter-intuitive and unnecessary, since the allowed enum values already make the max allowed length obvious. The apiserver automatically computes the max length of an enum as the length of the longest allowed enum value. I believe we already refuse evaluate CEL rules on values that fail OpenAPI value validation, since we rely in the value validations to establish all length limits. I haven't tested it locally, but something like this should work (given enough nested arrays): As a workaround, one can manually set on the string enum, e.g.: 25+ All No response No response No response No response\n/sig api-machinery /triage accepted /assign\n/assign\nI wasn't sure if we special-cased the maxLength / maxItems / maxProperties failures, or if all openapi validation had to pass before we started messing with CEL evaluation\nit looks like we currently special-case specific openapi errors that short-circuit CEL validation, I'm not sure an enum validation failure would currently prevent evaluation:\nThe enum err is converted to () error which is not short-circuit here. But for defaulting case, all error would be short-circuit. I would suggest to add error into the blockingErr list to short-circuit CEL validation. Would this make sense?\nyeah, that sounds good if we're going to rely on it to catch things that are longer than the maximum length enum value", "commid": "kubernetes_issue_119511", "tokennum": 383}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bac0346b41bc1d6d88c4f5ec6d3b234ff335e006e21c72e1241c91306fe6d20f", "query": "// Removes SCSI controller which is latest attached to VM. func cleanUpController(newSCSIController types.BaseVirtualDevice, vmDevices object.VirtualDeviceList, vm *object.VirtualMachine, ctx context.Context) error { <ins> if newSCSIController == nil || vmDevices == nil || vm == nil { return nil } </ins> ctls := vmDevices.SelectByType(newSCSIController) if len(ctls) < 1 { return ErrNoDevicesFound", "positive_passages": [{"docid": "doc-en-kubernetes-72455550466a39f28970619bf50fef21b9396df700b03a9fcf4c2735a10457eb", "text": "Kubernetes 1.3.0. During attach disk to VM, call to cleanUpController dereferenced a null pointer. Stack trace:\nThe seems points to a comment instead of a cleanUpCotroller function in v1.3.0. There might be some modifications later which make the line number inaccurate. Would you please double check which line it really should point to? Thanks.\nthat is correct, this was a build from v1.3.0 with changes related to this: therefore the line numbers do no line up with v1.3.0. In either case, the panic happened inside\nHi Davide, I saw your PR for this issue and I have another question. Why cleanUpController could be called with an empty newSCSIController? According to the context, an empty newSCSIController should not even be returned by CreateSCSIController rt? Thanks.\nit doesn't look like it should happen, but it did and there wasn't any checks for nil pointers in our code or the Govmomi library.", "commid": "kubernetes_issue_31823", "tokennum": 224}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bac1f2053e4bc66fe7f0eb87b2d6956c86949b138a6ab565df8bbebf5b3facdf", "query": "// rest.Config generated by the resolver. type AuthenticationInfoResolverWrapper func(AuthenticationInfoResolver) AuthenticationInfoResolver <del> // AuthenticationInfoResolver builds rest.Config base on the server name. </del> <ins> // AuthenticationInfoResolver builds rest.Config base on the server or service // name and service namespace. </ins> type AuthenticationInfoResolver interface { <ins> // ClientConfigFor builds rest.Config based on the server. </ins> ClientConfigFor(server string) (*rest.Config, error) <ins> // ClientConfigForService builds rest.Config based on the serviceName and // serviceNamespace. ClientConfigForService(serviceName, serviceNamespace string) (*rest.Config, error) </ins> } <del> // AuthenticationInfoResolverFunc implements AuthenticationInfoResolver. type AuthenticationInfoResolverFunc func(server string) (*rest.Config, error) </del> <ins> // AuthenticationInfoResolverDelegator implements AuthenticationInfoResolver. type AuthenticationInfoResolverDelegator struct { ClientConfigForFunc        func(server string) (*rest.Config, error) ClientConfigForServiceFunc func(serviceName, serviceNamespace string) (*rest.Config, error) } func (a *AuthenticationInfoResolverDelegator) ClientConfigFor(server string) (*rest.Config, error) { return a.ClientConfigForFunc(server) } </ins> <del> //ClientConfigFor implements AuthenticationInfoResolver. func (a AuthenticationInfoResolverFunc) ClientConfigFor(server string) (*rest.Config, error) { return a(server) </del> <ins> func (a *AuthenticationInfoResolverDelegator) ClientConfigForService(serviceName, serviceNamespace string) (*rest.Config, error) { return a.ClientConfigForServiceFunc(serviceName, serviceNamespace) </ins> } type defaultAuthenticationInfoResolver struct {", "positive_passages": [{"docid": "doc-en-kubernetes-73496a383d34eb1ab5962a20be4dce66952c6d20058c4ff89ce94afc1cb5683d", "text": "We are getting the following error when the apiserver connects the webhook on localhost (configured via URL). We should only use the SSL tunnel for the connections to nodes when the webhooks are running as services. /sig api-machinery /kind bug /assign\n/close", "commid": "kubernetes_issue_58779", "tokennum": 64}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bae299292a8d1028634f493254b57b95a530033ff622225687915cd483f5f4f5", "query": "v1 \"k8s.io/api/core/v1\" policy \"k8s.io/api/policy/v1beta1\" <del> apierrors \"k8s.io/apimachinery/pkg/api/errors\" </del> \"k8s.io/apimachinery/pkg/api/resource\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/runtime\"", "positive_passages": [{"docid": "doc-en-kubernetes-0c3eca7956c73a24f455c71a58b712ce183e874d4a3e3eb9b913120c8a8ac10c", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: Conformance - GCE - master (ci-kubernetes-gce-conformance-latest) Which test(s) are failing: [sig-scheduling] SchedulerPreemption [Serial] PreemptionExecutionPath runs ReplicaSets to verify preemption running path [Conformance]Changes Since when has it been failing: 2020-06-08 22:27 PDT Testgrid link: Reason for failure: Regression by Anything else we need to know: /sig scheduling /priority critical-urgent\ncc/ /assign", "commid": "kubernetes_issue_91972", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-baee15794231afc7d2103e63f203132c627b0299e605f76a22ae9987bf9492b6", "query": "\"type\": \"string\" }, \"ports\": { <del> \"description\": \"List of ports to expose from the container. Exposing a port here gives the system additional information about the network connections a container uses, but is primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default \"0.0.0.0\" address inside a container will be accessible from the network. Cannot be updated.\", </del> <ins> \"description\": \"List of ports to expose from the container. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default \"0.0.0.0\" address inside a container will be accessible from the network. Modifying this array with strategic merge patch may corrupt the data. For more information See https://github.com/kubernetes/kubernetes/issues/108255. Cannot be updated.\", </ins> \"items\": { \"$ref\": \"#/definitions/io.k8s.api.core.v1.ContainerPort\" },", "positive_passages": [{"docid": "doc-en-kubernetes-754763163ccf179fd132c393411aa2d267e649990c98a81bb38938ec6debc8b2", "text": "The comments in says that : However there are several cases where this is false : When using a Service with a targetPort that references a name in the ports arrays of the pod. Some software (ab)uses this API to get which ports are used (See Although unfixable, my goal is to fix the documentation so other people don't have the same problem). The Azure Load Balancer implementation does this for instance. Some other network/security software might use this information. Also, is it possible to document/reference the above issue in the comment ? Since it is described as informational I expected for the network to work without this information. But it's definitely not the case. Not needed since it's mostly a doc issue. I'm interested in contributing this patch but would like some feedbacks before doing it. :) <details</details<details</details<details</details<details</details<details</details<details</details\n/sig network\n/triage accepted -- thoughts? I believe the doc are due for a refresh.\nI'd take this one. /assign\nI didn't see that you wanted to do this patch, I am very sorry and now I unassign it. /unassign\nNo worries But I'm still not sure where / what to add. Should I only fix the part saying it is only informational ? Is there anything else ? (cc\nThe 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]:\n/remove-lifecycle stale", "commid": "kubernetes_issue_108255", "tokennum": 435}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bb3448a2f8231e96978bd32caa3dfe4cef5816826281a0af9bc6816a74da177e", "query": "AUTOSCALER_MIN_NODES=\"${KUBE_AUTOSCALER_MIN_NODES:-1}\" AUTOSCALER_MAX_NODES=\"${KUBE_AUTOSCALER_MAX_NODES:-${NUM_MINIONS}}\" TARGET_NODE_UTILIZATION=\"${KUBE_TARGET_NODE_UTILIZATION:-0.7}\" <ins> ENABLE_CLUSTER_MONITORING=googleinfluxdb </ins> fi # Optional: Enable deployment experimental feature, not ready for production use.", "positive_passages": [{"docid": "doc-en-kubernetes-42a2dcc81f7ae4dc8763c9cd41f1b3c90a02e5ad103b4424eb3978e5cae8304c", "text": "Heapster pod: And logs: cc p0 for triage\nDid the required node scope change?\nIts either the API on the console or monitoring write scopes on the node. , Mike Danese wrote:\nI think this affects only GCE\nI will fix this issue since is on vacation.\nNeed to cherry pick so i'll leave open\nis out for review.\nhas been closed and the cherrypick here () has been merged so I'm closing this issue. Thanks everyone for the debugging.", "commid": "kubernetes_issue_16201", "tokennum": 104}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bb579085541433eea7607bbcec3b281daab625fb4d62f21af3cca072a610211f", "query": "ETCD_HOST=${ETCD_HOST:-127.0.0.1} ETCD_PORT=${ETCD_PORT:-4001} <ins> ETCD_PREFIX=${ETCD_PREFIX:-randomPrefix} </ins> API_PORT=${API_PORT:-8080} API_HOST=${API_HOST:-127.0.0.1} KUBE_API_VERSIONS=\"\"", "positive_passages": [{"docid": "doc-en-kubernetes-74ce4fea7378dc634ccb83a22893b6255fa243ed3e0b4f0e57320154ecc66caf", "text": "removed this test. We need to continue testing this. This wasn't about testing upgrades, the prefix has nothing to do with upgrades. It's just there so people can share etcd. We maybe don't need to double everything but we do need to make sure that keeps working.\nTo be honest - I think that what we was testing before didn't give us completely any information. We didn't testing what information we are storing in etcd and where. That said, if we had a hardcoded prefix somewhere in our code, we wouldn't discover it at all, and those tests would still be passing. We should have a test that is directly checking etcd contents. I think it should be possible to write a simple unit test for it. Will try to put something together next week.", "commid": "kubernetes_issue_26489", "tokennum": 167}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bb8513dd489146c5eef8a1f9213317b92e6113176274ae0bf52a55e9ed5d4c2d", "query": "} // performPlatformSpecificContainerCleanup is responsible for doing any platform-specific cleanup <del> // after either: //   * the container creation has failed //   * the container has been successfully started //   * the container has been removed // whichever happens first. // Any errors it returns are simply logged, but do not prevent the container from being started or // removed. </del> <ins> // after either the container creation has failed or the container has been removed. </ins> func (ds *dockerService) performPlatformSpecificContainerCleanup(cleanupInfo *containerCleanupInfo) (errors []error) { if err := removeGMSARegistryValue(cleanupInfo); err != nil { errors = append(errors, err)", "positive_passages": [{"docid": "doc-en-kubernetes-486ca0159276eedd0d2aa336961ee5fd6fb83d0ac97af7f3f9c8c863d43fcef2", "text": "What would you like to be : Periodically remove cleanupInfos for old containers from dockershim's map. One way of doing that would be to just forget about s older than say an hour, as they should always be short-lived. Why is this needed: introduced a new in-memory map for the dockershim, that could potentially (in pathological cases) cause memory leaks - for containers that use GMSA cred specs, get created successfully, but then never get started nor removed. This might be okay for the alpha release of the GMSA feature, but should be addressed in the beta. See\n/assign wk8\n/sig windows\n/milestone v1.15\ngot moved out. let's move this issue with it as well /milestone v1.16\nHello! I'm bug triage lead for the 1.16 release cycle and considering this issue is tagged for 1.16, but not updated for a long time, I'd like to check its status. The code freeze is starting on August 29th (about 1.5 weeks from now), which means that there should be a PR ready (and merged) until then. Do we still target this issue to be fixed for 1.16?\n: yup we'd love to have this in 1.16, still waiting for kind reviewers on :) ...", "commid": "kubernetes_issue_74843", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bbcf0942c9157828edace412baa2be6fe46820020e2daf36a43a3e9368548eee", "query": "DefaultDummyDevice = \"kube-ipvs0\" connReuseMinSupportedKernelVersion = \"4.1\" <ins> // https://github.com/torvalds/linux/commit/35dfb013149f74c2be1ff9c78f14e6a3cd1539d1 connReuseFixedKernelVersion = \"5.9\" </ins> ) // iptablesJumpChain is tables of iptables chains that ipvs proxier used to install iptables or cleanup iptables.", "positive_passages": [{"docid": "doc-en-kubernetes-53ca4ed8e960fbba0bd8112d5cddbb22b80695a5a78dce628bb98a2132843341", "text": "There were two patches merged recently in the kernel that will significantly improve the IPVS proxier: The first patch fixes an issue where a packet is dropped whenever a stale conntrack entry is reused. This caused a 1s delay whenever the stale conntrack entry was used. This was the original reason for setting . More details in The second patch fixes an issue when a source port is reused from a given client and the corresponding destination was deleted. This is easily reproducible when a single client sends a lot traffic to a small set of destinations and one of the destination servers are removed. More details in Based on these two patches, we should start setting (default) starting on Linux v5.9 when those two patches make it to the main line. The new sysctls for the IPVS proxier would be: We should probably wait for v5.9 before making any changes to kube-proxy, this is just a tracking issue so we don't forget.\n/sig network /area ipvs\nShould probably hold on the PR until v5.9 is released later this year. cc\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/remove-triage unresolved\nYes it makes sense to wait until a kernel with the patch exists ;) I think we can also avoid touching it and follow the approach \"only touch the sysctl we absolutely need, otherwise trust the admin to know what they need\"\nI install linux-5.9-rc2 in centos7. set /proc/sys/net/ipv4/vs/connreusemode = 1 i have three service: service-a ---service-b --service-c in k8s. service-c return \"helloworld\" I use ab to benchmark service-a. [root ~]# ab -n -c 1000 http://172.17.2.66:/ This is ApacheBench, Version 2.3 &lt;Copyright 1996 Adam Twiss, Zeus Technology Ltd, Licensed to The Apache Software Foundation, Benchmarking 172.17.2.66 (be patient) Completed 1000 requests Completed 2000 requests Completed 3000 requests Completed 4000 requests Completed 5000 requests Completed 6000 requests Completed 7000 requests Completed 8000 requests Completed 9000 requests Completed requests Finished requests Server Software: Server Hostname: 172.", "commid": "kubernetes_issue_93297", "tokennum": 506}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bbcf0942c9157828edace412baa2be6fe46820020e2daf36a43a3e9368548eee", "query": "DefaultDummyDevice = \"kube-ipvs0\" connReuseMinSupportedKernelVersion = \"4.1\" <ins> // https://github.com/torvalds/linux/commit/35dfb013149f74c2be1ff9c78f14e6a3cd1539d1 connReuseFixedKernelVersion = \"5.9\" </ins> ) // iptablesJumpChain is tables of iptables chains that ipvs proxier used to install iptables or cleanup iptables.", "positive_passages": [{"docid": "doc-en-kubernetes-2c3bb3dca2a83bb247d336067e1c335109a2eb22fe4a06bf3bed6ebfcc858325", "text": "17.2.66 Server Port: Document Path: / Document Length: 11 bytes Concurrency Level: 1000 Time taken for tests: 4.128 seconds Complete requests: Failed requests: 0 Write errors: 0 Total transferred: bytes HTML transferred: bytes Requests per second: 2422.76 [#/sec] (mean) Time per request: 412.753 [ms] (mean) Time per request: 0.413 [ms] (mean, across all concurrent requests) Transfer rate: 302.84 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect: 0 16 71.5 4 1004 Processing: 4 216 92.9 202 2340 Waiting: 4 215 92.7 202 2340 Total: 4 232 121.5 215 2341 Percentage of the requests served within a certain time (ms) 50% 215 66% 253 75% 280 80% 299 90% 348 95% 412 98% 490 99% 556 100% 2341 (longest request) [root ~]# ab -n -c 1000 http://172.17.2.66:/ This is ApacheBench, Version 2.3 &lt;Copyright 1996 Adam Twiss, Zeus Technology Ltd, Licensed to The Apache Software Foundation, Benchmarking 172.17.2.66 (be patient) Completed 1000 requests Completed 2000 requests Completed 3000 requests Completed 4000 requests Completed 5000 requests Completed 6000 requests Completed 7000 requests Completed 8000 requests Completed 9000 requests Completed requests Finished requests Server Software: Server Hostname: 172.17.2.66 Server Port: Document Path: / Document Length: 11 bytes Concurrency Level: 1000 Time taken for tests: 7.071 seconds Complete requests: Failed requests: 0 Write errors: 0 Total transferred: bytes HTML transferred: bytes Requests per second: 1414.21 [#/sec] (mean) Time per request: 707.110 [ms] (mean) Time per request: 0.707 [ms] (mean, across all concurrent requests) Transfer rate: 176.", "commid": "kubernetes_issue_93297", "tokennum": 429}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bbcf0942c9157828edace412baa2be6fe46820020e2daf36a43a3e9368548eee", "query": "DefaultDummyDevice = \"kube-ipvs0\" connReuseMinSupportedKernelVersion = \"4.1\" <ins> // https://github.com/torvalds/linux/commit/35dfb013149f74c2be1ff9c78f14e6a3cd1539d1 connReuseFixedKernelVersion = \"5.9\" </ins> ) // iptablesJumpChain is tables of iptables chains that ipvs proxier used to install iptables or cleanup iptables.", "positive_passages": [{"docid": "doc-en-kubernetes-c35c3d64a37eee54a055f855f349a29d12f9312945295419d8a667917ed08399", "text": "78 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect: 0 9 66.2 2 1019 Processing: 10 661 575.2 372 3603 Waiting: 1 659 573.7 372 3603 Total: 10 670 584.6 380 3607 Percentage of the requests served within a certain time (ms) 50% 380 66% 742 75% 1008 80% 1183 90% 1535 95% 1784 98% 2376 99% 2479 100% 3607 (longest request) [root ~]# ab -n -c 1000 http://172.17.2.66:/ This is ApacheBench, Version 2.3 &lt;Copyright 1996 Adam Twiss, Zeus Technology Ltd, Licensed to The Apache Software Foundation, Benchmarking 172.17.2.66 (be patient) Completed 1000 requests Completed 2000 requests Completed 3000 requests Completed 4000 requests Completed 5000 requests Completed 6000 requests Completed 7000 requests Completed 8000 requests Completed 9000 requests Completed requests Finished requests Server Software: Server Hostname: 172.17.2.66 Server Port: Document Path: / Document Length: 11 bytes Concurrency Level: 1000 Time taken for tests: 13.580 seconds Complete requests: Failed requests: 0 Write errors: 0 Total transferred: bytes HTML transferred: bytes Requests per second: 736.40 [#/sec] (mean) Time per request: 1357.958 [ms] (mean) Time per request: 1.358 [ms] (mean, across all concurrent requests) Transfer rate: 92.05 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect: 0 4 6.6 1 49 Processing: 11 1333 491.9 1307 3185 Waiting: 1 1330 491.9 1305 3185 Total: 17 1337 491.", "commid": "kubernetes_issue_93297", "tokennum": 404}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bbcf0942c9157828edace412baa2be6fe46820020e2daf36a43a3e9368548eee", "query": "DefaultDummyDevice = \"kube-ipvs0\" connReuseMinSupportedKernelVersion = \"4.1\" <ins> // https://github.com/torvalds/linux/commit/35dfb013149f74c2be1ff9c78f14e6a3cd1539d1 connReuseFixedKernelVersion = \"5.9\" </ins> ) // iptablesJumpChain is tables of iptables chains that ipvs proxier used to install iptables or cleanup iptables.", "positive_passages": [{"docid": "doc-en-kubernetes-8a42de3c47fe5733a8be9b0431ca4615a2a4c3e9126af1e5f3fc1676b07bf58b", "text": "9 1311 3191 Percentage of the requests served within a certain time (ms) 50% 1311 66% 1565 75% 1679 80% 1748 90% 1911 95% 2129 98% 2384 99% 2650 100% 3191 (longest request) [root ~]# ab -n -c 1000 http://172.17.2.66:/ This is ApacheBench, Version 2.3 &lt;Copyright 1996 Adam Twiss, Zeus Technology Ltd, Licensed to The Apache Software Foundation, Benchmarking 172.17.2.66 (be patient) Completed 1000 requests Completed 2000 requests Completed 3000 requests Completed 4000 requests Completed 5000 requests Completed 6000 requests Completed 7000 requests Completed 8000 requests Completed 9000 requests Completed requests Finished requests Server Software: Server Hostname: 172.17.2.66 Server Port: Document Path: / Document Length: 11 bytes Concurrency Level: 1000 Time taken for tests: 23.720 seconds Complete requests: Failed requests: 936 (Connect: 0, Receive: 0, Length: 936, Exceptions: 0) Write errors: 0 Total transferred: bytes HTML transferred: bytes Requests per second: 421.58 [#/sec] (mean) Time per request: 2372.009 [ms] (mean) Time per request: 2.372 [ms] (mean, across all concurrent requests) Transfer rate: 47.77 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect: 0 5 7.5 1 49 Processing: 8 2345 3364.8 333 Waiting: 0 1744 3030.9 277 Total: 8 2350 3364.8 340 Percentage of the requests served within a certain time (ms) 50% 340 66% 1434 75% 3390 80% 5490 90% 8669 95% 9233 98% 99% 100% (longest request) the last time tcp connections of service-b :\n/assign Sorry, but I do not understand what are you trying to say.", "commid": "kubernetes_issue_93297", "tokennum": 423}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bbcf0942c9157828edace412baa2be6fe46820020e2daf36a43a3e9368548eee", "query": "DefaultDummyDevice = \"kube-ipvs0\" connReuseMinSupportedKernelVersion = \"4.1\" <ins> // https://github.com/torvalds/linux/commit/35dfb013149f74c2be1ff9c78f14e6a3cd1539d1 connReuseFixedKernelVersion = \"5.9\" </ins> ) // iptablesJumpChain is tables of iptables chains that ipvs proxier used to install iptables or cleanup iptables.", "positive_passages": [{"docid": "doc-en-kubernetes-78960ac39e24e400e47e6916fdf5044032c9ae95fde2e36f307e50e5504537d0", "text": ": (\n/cc\nWill this be implemented in 1.21?\n/area kube-proxy\nIssues 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", "commid": "kubernetes_issue_93297", "tokennum": 81}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bbd8cb150cf000f93af2cb1d30f843b55174d1adbdd850d35819aa46d1236c09", "query": "VolumeSubpath:                  {Default: true, PreRelease: featuregate.GA}, ConfigurableFSGroupPolicy:      {Default: false, PreRelease: featuregate.Alpha}, BalanceAttachedNodeVolumes:     {Default: false, PreRelease: featuregate.Alpha}, <del> VolumeSubpathEnvExpansion:      {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.19, </del> CSIBlockVolume:                 {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.20 CSIInlineVolume:                {Default: true, PreRelease: featuregate.Beta}, RuntimeClass:                   {Default: true, PreRelease: featuregate.Beta},", "positive_passages": [{"docid": "doc-en-kubernetes-a166ddd65322b2b4c2d8cbe35891249f4d033568413f3b77fc1f46ee1d1ee8b8", "text": "/kind cleanup /sig storage /sig node Description: Feature gate VolumeSubpathEnvExpansion was GA in 1.17 and is marked for removal in 1.19 Related Issues: GA Release:\n/assign\n/cc", "commid": "kubernetes_issue_89519", "tokennum": 48}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bbea40c79339bb9188526744854378dbb35fb06288fe2dc2b69b6b560d481c98", "query": "tc.opts..., ) <ins> // Errors </ins> if len(tc.wantErr) != 0 { if err == nil || !strings.Contains(err.Error(), tc.wantErr) { t.Errorf(\"got error %q, want %q\", err, tc.wantErr)", "positive_passages": [{"docid": "doc-en-kubernetes-75719ce40debdc24665e0bd0c466c638c232f756949a78511459bd94dde06b58", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --here is supposed to be set through , but is not called from anywhere except tests, so always returns . should be set through here. Am I missing something? N/A None Kubernetes version (use ): master () Cloud provider or hardware configuration: N/A OS (e.g: ): N/A Kernel (e.g. ): N/A Install tools: N/A Network plugin and version (if this is a network-related bug): N/A Others: None\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scheduling\nThanks for pointing that out. The plumbing of extenders to the framework impact calling extenders on preemption. That seems to be a path not covered by tests end to end. Can you submit a PR to fix this? as you mentioned we need to pass the extenders on profile creation. We need to patch the fix back to v1.21 and v1.20 (the release where this was refactored). /cc\nI have submitted a PR for a fix.", "commid": "kubernetes_issue_102971", "tokennum": 348}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bc732cdeb30ce388e843781a18a6a48f4dc2378e84ab02cfa6e4aa9b2f76803d", "query": "<ins> /* Copyright 2017 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package scheme import ( \"testing\" \"k8s.io/apimachinery/pkg/api/testing/roundtrip\" \"k8s.io/kubernetes/pkg/kubelet/apis/kubeletconfig/fuzzer\" ) func TestRoundTripTypes(t *testing.T) { scheme, _, err := NewSchemeAndCodecs() if err != nil { t.Fatalf(\"unexpected error: %v\", err) } roundtrip.RoundTripTestForScheme(t, scheme, fuzzer.Funcs) } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-937f1cb17c20e5fd2b4a1f81201690c3dbe6990ef3c1bc74ff71daaa02b6db56", "text": "Solution: I will add one.\n/cc\nxref\nThanks for sending a PR so quickly!\n[MILESTONENOTIFIER] Milestone Issue Needs Attention Action required: During code slush, issues in the milestone should be in progress. If this issue is not being actively worked on, please remove it from the milestone. If it is being worked on, please add the label so it can be tracked with other in-flight issues. Note: If this issue is not resolved or labeled as by Wed, Nov 22 it will be moved out of the v1.9 milestone. <details<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details", "commid": "kubernetes_issue_55959", "tokennum": 230}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bc9a06301412860818b2d565b5039699b2ca04e7c35208978e5ff9398d8b9889", "query": "type NodeServer interface { // NodePrepareResources prepares several ResourceClaims // for use on the node. If an error is returned, the <del> // response is ignored. Failures for individidual claims </del> <ins> // response is ignored. Failures for individual claims </ins> // can be reported inside NodePrepareResourcesResponse. NodePrepareResources(context.Context, *NodePrepareResourcesRequest) (*NodePrepareResourcesResponse, error) // NodeUnprepareResources is the opposite of NodePrepareResources.", "positive_passages": [{"docid": "doc-en-kubernetes-e8eec0a3f7a81297ed919db6952e73e9801661fbfe386a524b19b8189beefe88", "text": "When ResourceClaimParameters or ResourceClassParameters fail validation in resource driver during PodSchedulingContext sync loop, the error is visible only in the events of the PodSchedulingContext. The error should be visible on the object that fails validation as well, ResourceClaim or ResourceClass respectively. Creating ResourceClaim with unsupported parameters' values or unsupported No response <details</details<details</details<details</details<details</details<details</details<details</details\n/assign\n/sig node\n/triage accepted\nKEP:", "commid": "kubernetes_issue_121063", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bca57e841fe2002a80ea867abf6e2b58d8e2c3abeefe32adaf34f24c55ff543d", "query": "Interval_Sec 2 # Channels Setup,Windows PowerShell Channels     application,system,security <del> Tag          winevent.raw </del> <ins> Tag          winevt.raw </ins> DB           /var/run/google-fluentbit/pos-files/winlog.db # Json Log Example:", "positive_passages": [{"docid": "doc-en-kubernetes-89b11fc4c25f0b72d5f027a149a029fe0341e3d491bf3200f9e9687686d8fec6", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --On Windows 20H2 we are observing crashloops with fluent-bit due to a malformed Windows Event Log entry in the Security log. Fluent-bit to not crash loop. Bring up a GCE Windows cluster on Windows 20H2. You may see a loss of logs. Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others: /sig windows /triage accepted", "commid": "kubernetes_issue_102023", "tokennum": 170}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bcc8c237ffc25b741e296c3b035552cef5b7866cd8f358559edd68eabcf83678", "query": "pod := config.endpointPods[0] config.getPodClient().Delete(pod.Name, nil) config.endpointPods = config.endpointPods[1:] <del> time.Sleep(5 * time.Second) // wait for kube-proxy to catch up with the pod being deleted. </del> <ins> // wait for pod being deleted. err := waitForPodToDisappear(config.f.Client, config.f.Namespace.Name, pod.Name, labels.Everything(), time.Second, util.ForeverTestTimeout) if err != nil { Failf(\"Failed to delete %s pod: %v\", pod.Name, err) } // wait for endpoint being removed. err = waitForServiceEndpointsNum(config.f.Client, config.f.Namespace.Name, nodePortServiceName, len(config.endpointPods), time.Second, util.ForeverTestTimeout) if err != nil { Failf(\"Failed to remove endpoint from service: %s\", nodePortServiceName) } // wait for kube-proxy to catch up with the pod being deleted. time.Sleep(5 * time.Second) </ins> } func (config *KubeProxyTestConfig) createPod(pod *api.Pod) *api.Pod {", "positive_passages": [{"docid": "doc-en-kubernetes-57d83ef880aa3c3668480a2a99a63d94dfed9404bcfb6c9db559f5ee8b331861", "text": "More detail can be seen in e2e test\ncc\n, Marek Grabowski wrote:\nyou are running an older version of the test. can you get the latest and try again ? This test had not failed at all yesterday in our automated test runs yesterday. Closing issue for now.\nThis failure depends on if the pod is really deleted and kube-proxy (the test container on) catch that the endpoint is deleted in 5s . After sending \"delete pod\" request for 5s, if the pod was still there and kube-proxy still contains this endpoints(this may happen under pressure), hit test can still detect 5 endpoints. At least we should ensure the pod was deleted. Anyway, I think will be helpful to this test. What do you think?\nIt doesn't matter if the pod is actually deleted or not. We just care that kube-proxy thinks that it should not be part of the service endpoint. Having said that, it still doesn't hurt to do the check that you are doing. I will assign your PR to myself and review it. In the meantime, can you rebase your PR ?\nThanks for your review. The PR is up to date.\nFailed twice today in kubernetes-e2e-gce-parallel\nOne more today. The error message is not very helpful.\n18:28:37 STEP: dialing(http) endpointPodIP:endpointHttpPort from node1 18:28:37 STEP: Dialing from node. command:for i in ' wc -l This is the point where the test fails. Am looking into it. We need to have more tries, we just do seq (1 1), instead of seq (6 6). this is causing flakiness.\nFixed by PR", "commid": "kubernetes_issue_14342", "tokennum": 372}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bcd6fec134cba1f25fb33bf784b5923bd54ebbc813dd25e0f6401358fe42e601", "query": "package e2e_node import ( <del> \"fmt\" </del> \"time\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/util/intstr\" <del> \"k8s.io/apimachinery/pkg/util/uuid\" </del> \"k8s.io/kubernetes/pkg/api/v1\" \"k8s.io/kubernetes/test/e2e/framework\"", "positive_passages": [{"docid": "doc-en-kubernetes-523d59ec5104a53f44aa3efaa79fa37e525dbabb537793d9e95c31ff14a3e1c1", "text": "The prestop and poststart exec tests volume mount /tmp from the host and attempt to create a file there from inside the pod. This is blocked by selinux. Failure:\nwe need to have a mechanism to say that a test should not be run if selinux is enabled (if legitimately required) or fix each test (where appropriate)", "commid": "kubernetes_issue_42905", "tokennum": 76}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bcd7ef3c287995690cde4ec53867261adfdc5bba31b363d08e3d8c163b1e290b", "query": "\"k8s.io/kubernetes/pkg/api\" \"k8s.io/kubernetes/pkg/api/resource\" \"k8s.io/kubernetes/pkg/apis/extensions\" <ins> \"k8s.io/kubernetes/pkg/util/codeinspector\" </ins> \"k8s.io/kubernetes/plugin/pkg/scheduler\" \"k8s.io/kubernetes/plugin/pkg/scheduler/algorithm\" priorityutil \"k8s.io/kubernetes/plugin/pkg/scheduler/algorithm/priorities/util\"", "positive_passages": [{"docid": "doc-en-kubernetes-3229e3f28f67afa9ddea85d9d31a50803c261e0ae30f76f950060d1790215e64", "text": "I just noticed you forgot to register the image locality priority function in in I also missed it when I reviewed your PR. I have fixed this in . But it would be great if you could figure out a mechanism that would ensure that all predicate/priority functions that are tested (you can assume they will always live under ) are registered, and fail the test if not. That will allow us to prevent this mistake in the future.\nThanks! Will fix this soon!\nSeems need to wait for in before I send PR? Otherwise this test will always fail ...", "commid": "kubernetes_issue_21236", "tokennum": 114}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bcdb2e68eac318f38438a9380cb2178a005791a119362cee82292e240214dfcb", "query": "psps, err := kubeClient.PolicyV1beta1().PodSecurityPolicies().List(context.TODO(), metav1.ListOptions{}) if err != nil { Logf(\"Error listing PodSecurityPolicies; assuming PodSecurityPolicy is disabled: %v\", err) <del> isPSPEnabled = false } else if psps == nil || len(psps.Items) == 0 { </del> <ins> return } if psps == nil || len(psps.Items) == 0 { </ins> Logf(\"No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.\") <del> isPSPEnabled = false } else { Logf(\"Found PodSecurityPolicies; assuming PodSecurityPolicy is enabled.\") isPSPEnabled = true </del> <ins> return } Logf(\"Found PodSecurityPolicies; testing pod creation to see if PodSecurityPolicy is enabled\") testPod := &v1.Pod{ ObjectMeta: metav1.ObjectMeta{GenerateName: \"psp-test-pod-\"}, Spec:       v1.PodSpec{Containers: []v1.Container{{Name: \"test\", Image: imageutils.GetPauseImageName()}}}, } dryRunPod, err := kubeClient.CoreV1().Pods(\"kube-system\").Create(context.TODO(), testPod, metav1.CreateOptions{DryRun: []string{metav1.DryRunAll}}) if err != nil { if strings.Contains(err.Error(), \"PodSecurityPolicy\") { Logf(\"PodSecurityPolicy error creating dryrun pod; assuming PodSecurityPolicy is enabled: %v\", err) isPSPEnabled = true } else { Logf(\"Error creating dryrun pod; assuming PodSecurityPolicy is disabled: %v\", err) } return } pspAnnotation, pspAnnotationExists := dryRunPod.Annotations[\"kubernetes.io/psp\"] if !pspAnnotationExists { Logf(\"No PSP annotation exists on dry run pod; assuming PodSecurityPolicy is disabled\") return </ins> } <ins> Logf(\"PSP annotation exists on dry run pod: %q; assuming PodSecurityPolicy is enabled\", pspAnnotation) isPSPEnabled = true </ins> }) return isPSPEnabled }", "positive_passages": [{"docid": "doc-en-kubernetes-d654f914f6cdd0bd3bce5db6eb3c4ebef631bd8d2558ac9d591cab12ba724061", "text": "What happened: e2e tests detect whether PSP is enabled based on presence of PSP API objects. An addon that proactively includes a PSP in a manifest can trigger that detection and enable PSP-specific e2e tests that should not be run. What you expected to happen: In addition to detecting presence of PSP objects, consider dry-run creating a pod and verifying the annotation indicating the selected PSP policy is , indicating the admission plugin is active. /sig auth /assign", "commid": "kubernetes_issue_91463", "tokennum": 109}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bce596787532dba5eb2ffddc4fe088e7d2060d755d6fa13691ec764b762c15da", "query": "} } <ins> func TestDiscoveryContentTypeVersion(t *testing.T) { tests := []struct { contentType string isV2Beta1   bool }{ { contentType: \"application/json; g=apidiscovery.k8s.io;v=v2beta1;as=APIGroupDiscoveryList\", isV2Beta1:   true, }, { // content-type parameters are not in correct order, but comparison ignores order. contentType: \"application/json; v=v2beta1;as=APIGroupDiscoveryList;g=apidiscovery.k8s.io\", isV2Beta1:   true, }, { // content-type parameters are not in correct order, but comparison ignores order. contentType: \"application/json; as=APIGroupDiscoveryList;g=apidiscovery.k8s.io;v=v2beta1\", isV2Beta1:   true, }, { // Ignores extra parameter \"charset=utf-8\" contentType: \"application/json; g=apidiscovery.k8s.io;v=v2beta1;as=APIGroupDiscoveryList;charset=utf-8\", isV2Beta1:   true, }, { contentType: \"application/json\", isV2Beta1:   false, }, { contentType: \"application/json; charset=UTF-8\", isV2Beta1:   false, }, { contentType: \"text/json\", isV2Beta1:   false, }, { contentType: \"text/html\", isV2Beta1:   false, }, { contentType: \"\", isV2Beta1:   false, }, } for _, test := range tests { isV2Beta1 := isV2Beta1ContentType(test.contentType) assert.Equal(t, test.isV2Beta1, isV2Beta1) } } </ins> func TestUseLegacyDiscovery(t *testing.T) { // Default client sends aggregated discovery accept format (first) as well as legacy format. server := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, req *http.Request) {", "positive_passages": [{"docid": "doc-en-kubernetes-3257ecff81fbc60fa2a8f982346c462089eb7c896f62cce1d4e02ff6df66d913", "text": "We are using (and ) to interact with Kubernetes clusters behind a couple of proxy layers. One of these proxies completes the headers to include character encoding details. This was working fine until recently, when client-go/kubectl have started to fail when interacting with the discovery API. It seems that a recent change has made kubectl more restrictive of the content-type that it expects. I suspect that it is related to this commit: For example, this is an error from a kubectl command: We can of course try to fix it on our end, removing that charset information. However, it is a valid content-type and the way kubectl is handling the content-type there seems like it is relying on implementation details of kube-apiserver (that it does not add metadata to the content-type). I propose to fix this issue in , by properly parsing and handling the content-type.\ncc /kind regression /kind bug /sig api-machinery /priority important-soon looks like the switch statement in downloadLegacy() needs to be more tolerant of the variety of content-types it can get from a server (including text/plain or no content-type if old servers could have returned that...)\n/transfer kubernetes/kubernetes\nSomething went wrong or the destination repo kubernetes/kubernetes/kubernetes does not exist. <detailsIn response to : /transfer kubernetes/kubernetes 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\n/transfer kubernetes\nYep, the string comparison for the content-type is flimsy, let's address that. Thanks for the report!\n/assign\n/triage accepted\n/cc\nThe fix is being cherry-picked back to: : :", "commid": "kubernetes_issue_117562", "tokennum": 408}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bd2f92b6278201843732cf4a9df0684949232e825c6ca7f9dc3e547fa998fdde", "query": "package main import ( <del> \"fmt\" </del> \"math/rand\" \"os\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-0b2213d42768c43adcb1b4f15cf67b8722c82d28c3ec9792f5837d41705eb847", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: kubectl version --client=yes command is giving the following error message. Error message is repeated at the start and the end and also containing programming jargon Error: invalid argument \"yes\" for \"--client\" flag: strconv.ParseBool: parsing \"yes\": invalid syntax Examples: Print the client and server versions for the current context kubectl version Options: --client=false: Client version only (no server required). -o, --output='': One of 'yaml' or 'json'. --short=false: Print just the version number. Usage: kubectl version [flags] [options] Use \"kubectl options\" for a list of global command-line options (applies to all commands). invalid argument \"yes\" for \"--client\" flag: strconv.ParseBool: parsing \"yes\": invalid syntax What you expected to happen: The error message can be improved with one of the two variants invalid argument \"yes\" for \"--client\" flag Examples: Print the client and server versions for the current context kubectl version Options: --client=false: Client version only (no server required). -o, --output='': One of 'yaml' or 'json'. --short=false: Print just the version number. Usage: kubectl version [flags] [options] Use \"kubectl options\" for a list of global command-line options (applies to all commands). (or) Invalid argument \"yes\" for \"--client\" flag How to reproduce it (as minimally and precisely as possible): Run the command kubectl version --client=yes Anything else we need to know?: Environment: Kubernetes version (use ): 1.15 Cloud provider or hardware configuration: AWS OS (e.g: ): Amazon Linux Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig cli\nHi Thanks for posting this issue! It turns out that this duplicate output has been in kubectl, and all the other cli cmds, since . This should be fixed by , and hopefully we can cherry pick it back to at least .", "commid": "kubernetes_issue_79454", "tokennum": 560}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bd53e66842fb9f0051aad196ae3200c4ebdf53ad5385cf363d168966eb761295", "query": "// our target metric should be updated by now if err := wait.PollUntilContextTimeout(ctx, 10*time.Second, 2*time.Minute, true, func(_ context.Context) (bool, error) { metrics, err := metricsGrabber.GrabFromKubeProxy(ctx, nodeName) <del> framework.ExpectNoError(err) </del> <ins> if err != nil { return false, fmt.Errorf(\"failed to fetch metrics: %w\", err) } </ins> targetMetricAfter, err := metrics.GetCounterMetricValue(metricName) <del> framework.ExpectNoError(err) </del> <ins> if err != nil { return false, fmt.Errorf(\"failed to fetch metric: %w\", err) } </ins> return targetMetricAfter > targetMetricBefore, nil }); err != nil { <del> framework.Failf(\"expected %s metric to be updated after accessing endpoints via localhost nodeports\", metricName) </del> <ins> if wait.Interrupted(err) { framework.Failf(\"expected %s metric to be updated after accessing endpoints via localhost nodeports\", metricName) } framework.ExpectNoError(err) </ins> } }) })", "positive_passages": [{"docid": "doc-en-kubernetes-a2e77bc9d5795a4a17af5bcc5860b35587b39d7e25d603a866fcb410798b82da", "text": "seen in this inside a like loop we execute a function that return a bool and an error. If we want to fail fast we return the error directly and assert on the output of the wait function. If we want to retry we log the error and return false nil /kind flake /kind bug /sig testing /sig network\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/cc since I think you this test but most probable the code is inherited and is a copy paste thing, but besides that, the change is to remove those there\n/assign", "commid": "kubernetes_issue_126885", "tokennum": 192}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bd5a0b06201c0496c7216fba6c2af63ce440a2d5e2db9cde2c9c21dff44c510a", "query": "NodeDiskPressure NodeConditionType = \"DiskPressure\" // NodeNetworkUnavailable means that network for the node is not correctly configured. NodeNetworkUnavailable NodeConditionType = \"NetworkUnavailable\" <del> // NodeInodePressure means the kubelet is under pressure due to insufficient available inodes. NodeInodePressure NodeConditionType = \"InodePressure\" </del> ) // NodeCondition contains condition information for a node.", "positive_passages": [{"docid": "doc-en-kubernetes-7164ee736ec8b7198f38602535de086e7396a736ea12447e5be8a654710fb76e", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind cleanup What happened: It seems kubelet did not update inode pressure; and only test codes are using . So prefer to deprecate or remove it directly. (seems no node-misc group :). )", "commid": "kubernetes_issue_49103", "tokennum": 58}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bd618854930423f5eb3bdfd852f79a000e1aee31463454c563b59e995725403d", "query": "go_test( name = \"go_default_test\", srcs = [ <ins> \"codec_test.go\", </ins> \"conversion_test.go\", \"converter_test.go\", \"embedded_test.go\",", "positive_passages": [{"docid": "doc-en-kubernetes-7ee140198c665b218e0dfb7e3cd2f2624912887cfcfab5f30828d12c6130aa35", "text": "What happened: Set up a HA cluster with 1.9 and 1.10 API servers (occurs on any apiserver skew boundary where a cohabitating resource's storage version changed groups) Observed errors when modifying workload objects: when modified via the 1.10 server, saw this error in the 1.9 server: when modified via the 1.9 server, saw this error in the 1.10 server: When this error was encountered, all watchers for the resource in question would be dropped and have to re-establish, and the internal watchers feeding the watch cache would drop and re-establish What you expected to happen: Watch events from all supported storage versions are processed correctly How to reproduce it (as minimally and precisely as possible): Start a server from master (for inspectability, store in json). With Create a deployment (e.g. kube-dns in kube-system) Establish a watch via extensions (kubectl get deployments.extensions --all-namespaces -w) Establish a watch via apps (kubectl get --all-namespaces -w) Tail the kube-apiserver log Change the apps/v1 deployment in etcd to extensions/v1beta1: Observer client watches drop and server log errors: Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: /sig api-machinery /cc /priority critical-urgent\nerror is triggered by this returning false: constructed here: the info about expected cohabitating groups is not included in the list of acceptable inputs", "commid": "kubernetes_issue_73478", "tokennum": 368}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bd800e9dbac04f642ec9a725edf97dc4a428703422a42289ea3af211a5986c5b", "query": "fi proxy_mem_per_node=50 proxy_mem=$((100 * 1024 + proxy_mem_per_node*NUM_NODES)) <ins> hollow_kubelet_params=$(eval \"for param in ${HOLLOW_KUBELET_TEST_ARGS:-}; do echo -n \"$param\",; done\") hollow_kubelet_params=${hollow_kubelet_params%?} hollow_proxy_params=$(eval \"for param in ${HOLLOW_PROXY_TEST_ARGS:-}; do echo -n \"$param\",; done\") hollow_proxy_params=${hollow_proxy_params%?} </ins> sed -i'' -e \"s/{{HOLLOW_PROXY_CPU}}/${proxy_cpu}/g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" sed -i'' -e \"s/{{HOLLOW_PROXY_MEM}}/${proxy_mem}/g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" sed -i'' -e \"s'{{kubemark_image_registry}}'${KUBEMARK_IMAGE_REGISTRY}${KUBE_NAMESPACE}'g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" sed -i'' -e \"s/{{kubemark_image_tag}}/${KUBEMARK_IMAGE_TAG}/g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" sed -i'' -e \"s/{{master_ip}}/${MASTER_IP}/g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" <del> sed -i'' -e \"s/{{hollow_kubelet_params}}/${HOLLOW_KUBELET_TEST_ARGS:-}/g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" sed -i'' -e \"s/{{hollow_proxy_params}}/${HOLLOW_PROXY_TEST_ARGS:-}/g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" </del> <ins> sed -i'' -e \"s/{{hollow_kubelet_params}}/${hollow_kubelet_params}/g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" sed -i'' -e \"s/{{hollow_proxy_params}}/${hollow_proxy_params}/g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" </ins> sed -i'' -e \"s'{{kubemark_mig_config}}'${KUBEMARK_MIG_CONFIG:-}'g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" \"${KUBECTL}\" create -f \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" --namespace=\"kubemark\"", "positive_passages": [{"docid": "doc-en-kubernetes-d99484417892d904a3f5edbb73fa06d2de654c460b279ad73f511e028afa6a6f", "text": "There are CVEs happening in different images - we already migrated Kubmeark from busybox in , but we should go one step further and migrate the base image to distroless. There are some things that would need to be changed mentioned here: /sig scalability\nCan I work on this? /assign\n/remove-help\n- sure that would be great.\nHi based on the discussion in , the kubemark image has dependency on and maybe more other utilities. So it seems impossible to migrate the base image to distroless? Or do we need something like debian-hyperkube-base?\nThe mount one we may get rid of - basically we should be able to switch to FakeMounter:", "commid": "kubernetes_issue_84284", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bd80475127377067f4148587ea88f824ff33aca6062560ee5bfdff8df1149066", "query": "var resourcesByGV map[schema.GroupVersion]*metav1.APIResourceList // Switch on content-type server responded with: aggregated or unaggregated. <del> switch responseContentType { case AcceptV1: </del> <ins> switch { case isV2Beta1ContentType(responseContentType): var aggregatedDiscovery apidiscovery.APIGroupDiscoveryList err = json.Unmarshal(body, &aggregatedDiscovery) if err != nil { return nil, nil, nil, err } apiGroupList, resourcesByGV, failedGVs = SplitGroupsAndResources(aggregatedDiscovery) default: // Default is unaggregated discovery v1. </ins> var v metav1.APIVersions err = json.Unmarshal(body, &v) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-3257ecff81fbc60fa2a8f982346c462089eb7c896f62cce1d4e02ff6df66d913", "text": "We are using (and ) to interact with Kubernetes clusters behind a couple of proxy layers. One of these proxies completes the headers to include character encoding details. This was working fine until recently, when client-go/kubectl have started to fail when interacting with the discovery API. It seems that a recent change has made kubectl more restrictive of the content-type that it expects. I suspect that it is related to this commit: For example, this is an error from a kubectl command: We can of course try to fix it on our end, removing that charset information. However, it is a valid content-type and the way kubectl is handling the content-type there seems like it is relying on implementation details of kube-apiserver (that it does not add metadata to the content-type). I propose to fix this issue in , by properly parsing and handling the content-type.\ncc /kind regression /kind bug /sig api-machinery /priority important-soon looks like the switch statement in downloadLegacy() needs to be more tolerant of the variety of content-types it can get from a server (including text/plain or no content-type if old servers could have returned that...)\n/transfer kubernetes/kubernetes\nSomething went wrong or the destination repo kubernetes/kubernetes/kubernetes does not exist. <detailsIn response to : /transfer kubernetes/kubernetes 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\n/transfer kubernetes\nYep, the string comparison for the content-type is flimsy, let's address that. Thanks for the report!\n/assign\n/triage accepted\n/cc\nThe fix is being cherry-picked back to: : :", "commid": "kubernetes_issue_117562", "tokennum": 408}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bd8c5ad17499247548776c55cf33cef77d1c9e197027f87c0e3ff6a606d0f4da", "query": "} } <ins> func TestInClusterClientConfigPrecedence(t *testing.T) { tt := []struct { overrides *ConfigOverrides }{ { overrides: &ConfigOverrides{ ClusterInfo: clientcmdapi.Cluster{ Server: \"https://host-from-overrides.com\", }, }, }, { overrides: &ConfigOverrides{ AuthInfo: clientcmdapi.AuthInfo{ Token: \"https://host-from-overrides.com\", }, }, }, { overrides: &ConfigOverrides{ ClusterInfo: clientcmdapi.Cluster{ CertificateAuthority: \"/path/to/ca-from-overrides.crt\", }, }, }, { overrides: &ConfigOverrides{ ClusterInfo: clientcmdapi.Cluster{ Server: \"https://host-from-overrides.com\", }, AuthInfo: clientcmdapi.AuthInfo{ Token: \"https://host-from-overrides.com\", }, }, }, { overrides: &ConfigOverrides{ ClusterInfo: clientcmdapi.Cluster{ Server:               \"https://host-from-overrides.com\", CertificateAuthority: \"/path/to/ca-from-overrides.crt\", }, }, }, { overrides: &ConfigOverrides{ ClusterInfo: clientcmdapi.Cluster{ CertificateAuthority: \"/path/to/ca-from-overrides.crt\", }, AuthInfo: clientcmdapi.AuthInfo{ Token: \"https://host-from-overrides.com\", }, }, }, { overrides: &ConfigOverrides{ ClusterInfo: clientcmdapi.Cluster{ Server:               \"https://host-from-overrides.com\", CertificateAuthority: \"/path/to/ca-from-overrides.crt\", }, AuthInfo: clientcmdapi.AuthInfo{ Token: \"https://host-from-overrides.com\", }, }, }, { overrides: &ConfigOverrides{}, }, } for _, tc := range tt { expectedServer := \"https://host-from-cluster.com\" expectedToken := \"token-from-cluster\" expectedCAFile := \"/path/to/ca-from-cluster.crt\" icc := &inClusterClientConfig{ inClusterConfigProvider: func() (*restclient.Config, error) { return &restclient.Config{ Host:        expectedServer, BearerToken: expectedToken, TLSClientConfig: restclient.TLSClientConfig{ CAFile: expectedCAFile, }, }, nil }, overrides: tc.overrides, } clientConfig, err := icc.ClientConfig() if err != nil { t.Fatalf(\"Unxpected error: %v\", err) } if overridenServer := tc.overrides.ClusterInfo.Server; len(overridenServer) > 0 { expectedServer = overridenServer } if overridenToken := tc.overrides.AuthInfo.Token; len(overridenToken) > 0 { expectedToken = overridenToken } if overridenCAFile := tc.overrides.ClusterInfo.CertificateAuthority; len(overridenCAFile) > 0 { expectedCAFile = overridenCAFile } if clientConfig.Host != expectedServer { t.Errorf(\"Expected server %v, got %v\", expectedServer, clientConfig.Host) } if clientConfig.BearerToken != expectedToken { t.Errorf(\"Expected token %v, got %v\", expectedToken, clientConfig.BearerToken) } if clientConfig.TLSClientConfig.CAFile != expectedCAFile { t.Errorf(\"Expected Certificate Authority %v, got %v\", expectedCAFile, clientConfig.TLSClientConfig.CAFile) } } } </ins> func matchBoolArg(expected, got bool, t *testing.T) { if expected != got { t.Errorf(\"Expected %v, got %v\", expected, got)", "positive_passages": [{"docid": "doc-en-kubernetes-4e19a56e8ccacbab4546f622baecdb0b8ef30250430c55f8bcdc4de99b100cd2", "text": "Found in openshift, but I'm pretty sure the codepaths are the same. That means the token is getting ignored and in-cluster config is being used in preference to flags.\nIs a similar issue?\nYep, kind of regression.\nSigh.\nYes, most likely the same cause.\nI'm on it.\nUnit test :)\nProbably will want to cherrypick this into 1.5.\nWIP in", "commid": "kubernetes_issue_38834", "tokennum": 89}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bd9a42d5417deaf4d05e5f75c501f17b739322592c115fdee4192f024545642a", "query": "// The name of this port. All ports in an EndpointSlice must have a unique // name. If the EndpointSlice is dervied from a Kubernetes service, this // corresponds to the Service.ports[].name. <del> // Name must either be an empty string or pass IANA_SVC_NAME validation: // * must be no more than 15 characters long // * may contain only [-a-z0-9] // * must contain at least one letter [a-z] // * it must not start or end with a hyphen, nor contain adjacent hyphens </del> <ins> // Name must either be an empty string or pass DNS_LABEL validation: // * must be no more than 63 characters long. // * must consist of lower case alphanumeric characters or '-'. // * must start and end with an alphanumeric character. </ins> Name *string // The IP protocol for this port. // Must be UDP, TCP, or SCTP.", "positive_passages": [{"docid": "doc-en-kubernetes-b73bb51cef5016ee2dcd80aae4248808fec811a4dad3a3b7abbba7673a446c48", "text": "What happened: No endpoints created in the EndpointSlice for my service due to the port on the service being too long. Logs show: EndpointSlice created has no endpoint: What you expected to happen: Service that works with Endpoints should work with EndpointSlice. If this is intentional, it should be clearly documented How to reproduce it (as minimally and precisely as possible): Create a service with a long port name Environment: Kubernetes version (use ): 1.16 Cloud provider or hardware configuration: kind\n/sig networking\nThe label(s) cannot be applied. These labels are supported: <detailsIn response to : /sig networking 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\n/sig network These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by vllry. \u200d\nFor a rough measure of impact, Istio had 5 ports that were over this limit (and many more that were right at 15 characters), so I suspect it may not be terribly rare.\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nThis needs to be resolved before endpointslices graduate from alpha\n/assign\n/remove-triage unresolved", "commid": "kubernetes_issue_84388", "tokennum": 292}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bdff48675cc6223bc8c66f8593c0515939335916e561cd38d65615a0de5d96bf", "query": "docs/man/man1/kubectl-alpha-diff.1 docs/man/man1/kubectl-alpha.1 docs/man/man1/kubectl-annotate.1 <ins> docs/man/man1/kubectl-api-resources.1 </ins> docs/man/man1/kubectl-api-versions.1 docs/man/man1/kubectl-apply-edit-last-applied.1 docs/man/man1/kubectl-apply-set-last-applied.1", "positive_passages": [{"docid": "doc-en-kubernetes-3c17ea4b4f4a9bb23915ee9fbb41703ef0532ac00becc05b8dda4d23a9ea9da2", "text": "As the RBAC role need to be related to resources. I think we could use a command to get the supported resources. ref to\nThis would be cool.\nI thought we a command that listed resources in the discover doc a long time ago.\nis just the versions, but principle is the same. We want to list all the types, their resources, and tie that back to \"explain\".\nWhat's the best way to determine this information currently? I'm having difficulty figuring out the exact set of permissions (and how they would be written in an RBAC role) for any given kubectl command. The documentation for this right now is split across multiple places and certain things are not explained at all. Specifically, it's difficult to determine which \"API verb\" is used for which operations. Take as an example. It's unclear if the way to allow this is to use the \"proxy\" subresource of a pod or service with \"get\"/\"create\"/etc. verbs, or to use the \"proxy\" verb with the resource (pod, service) directly. is a similar case. The almost works for this purpose, but it's still difficult. Operations for a given resource are grouped into categories like write, read, status, and proxy, but these things don't obviously correlate with API verbs. Again, proxy is especially confusing as there is no mention of a proxy \"verb\". The API operations are only shown using their HTTP verbs. One thing that could help on this document would be a section on the right column under \"kubectl command\" that shows exactly the rule needed in an RBAC role to allow this command via kubectl. And even then, that assumes an exact 1-to-1 mapping between API endpoints and kubectl commands, which I doubt is always the case. (For example, port fowarding to a pod seems to require both a GET on the pod resource and a CREATE on a port forward subresource.) There also needs to be better documentation about how this information could have been determined in the first place. I've resorted to manually looking through API requests made with but even then it's difficult to figure out. Amusingly, I was the one who wrote which is referenced in the original issue description (as well as the table explaining verbs in ).", "commid": "kubernetes_issue_42932", "tokennum": 494}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bdff48675cc6223bc8c66f8593c0515939335916e561cd38d65615a0de5d96bf", "query": "docs/man/man1/kubectl-alpha-diff.1 docs/man/man1/kubectl-alpha.1 docs/man/man1/kubectl-annotate.1 <ins> docs/man/man1/kubectl-api-resources.1 </ins> docs/man/man1/kubectl-api-versions.1 docs/man/man1/kubectl-apply-edit-last-applied.1 docs/man/man1/kubectl-apply-set-last-applied.1", "positive_passages": [{"docid": "doc-en-kubernetes-20fd632aaf82ba3efee7609ebeda29ca6df3199abf73ef8bcfe417660974a0ce", "text": "tl;dr: It's too difficult right now to go from \"I want a user to be able to run \" to \"here is the RBAC rule to use for that\" for any case where there isn't a specific example shown in the docs.\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nIt seem that relative PR stop updated. If this issue still valuable, i will help fix it\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close", "commid": "kubernetes_issue_42932", "tokennum": 279}], "negative_passages": []}
{"query_id": "q-en-kubernetes-be0f99e060e7b78cc0f4d55369474e8b1ce48f0caa95848431c1f2e6a912c273", "query": "maxStorageAccounts                     = 100 // max # is 200 (250 with special request). this allows 100 for everything else including stand alone disks maxDisksPerStorageAccounts             = 60 storageAccountUtilizationBeforeGrowing = 0.5 <ins> // Disk Caching is not supported for disks 4 TiB and larger // https://docs.microsoft.com/en-us/azure/virtual-machines/premium-storage-performance#disk-caching diskCachingLimit = 4096 // GiB </ins> maxLUN               = 64 // max number of LUNs per VM errLeaseFailed       = \"AcquireDiskLeaseFailed\"", "positive_passages": [{"docid": "doc-en-kubernetes-3186f04d894d2e98a9b770821be5e33542dd055d445ea6f78bf8e42e85bb59f7", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: there is a disk resize scenario: In the beginning, it\u2019s 3TiB with cachingMode=ReadOnly, and then disk detached, resized to 4TiB, then user find they could not attach that disk back to any agent node, I think that\u2019s a bug we need to fix. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others: /kind bug /assign /priority important-soon /sig cloud-provider /area provider/azure\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_95465", "tokennum": 311}], "negative_passages": []}
{"query_id": "q-en-kubernetes-be39fa1afb4eddcfa9728edc5859e03bb99d3b7f192c13cc02308c0f713990a3", "query": "// list all pods to include the pods that don't match the rs`s selector // anymore but has the stale controller ref. // TODO: Do the List and Filter in a single pass, or use an index. <del> pods, err := rsc.podLister.Pods(rs.Namespace).List(labels.Everything()) </del> <ins> allPods, err := rsc.podLister.Pods(rs.Namespace).List(labels.Everything()) </ins> if err != nil { return err } // Ignore inactive pods. var filteredPods []*v1.Pod <del> for _, pod := range pods { </del> <ins> for _, pod := range allPods { </ins> if controller.IsPodActive(pod) { filteredPods = append(filteredPods, pod) }", "positive_passages": [{"docid": "doc-en-kubernetes-38d52777560a5c6fb71d98b8b0953e61c4be2731ef4a377191b06cc53fcf6655", "text": "https://k8s- Failed: [] Network Partition [Disruptive] [Slow] [] [ReplicationController] should eagerly create replacement pod during network partition when termination grace is non-zero {Kubernetes e2e suite}\nhttps://k8s- seems to be the first failure here. It seems to have gone in with a bunch of RC/RS changes () cc/", "commid": "kubernetes_issue_37479", "tokennum": 88}], "negative_passages": []}
{"query_id": "q-en-kubernetes-be44fa41717b150de78312925771cd94e0fc8ee065f03960afa06dc045c37a51", "query": "statuses[container.Name] = status } <ins> // Copy the slice before sorting it containerStatusesCopy := make([]*kubecontainer.Status, len(podStatus.ContainerStatuses)) copy(containerStatusesCopy, podStatus.ContainerStatuses) </ins> // Make the latest container status comes first. <del> sort.Sort(sort.Reverse(kubecontainer.SortContainerStatusesByCreationTime(podStatus.ContainerStatuses))) </del> <ins> sort.Sort(sort.Reverse(kubecontainer.SortContainerStatusesByCreationTime(containerStatusesCopy))) </ins> // Set container statuses according to the statuses seen in pod status containerSeen := map[string]int{} <del> for _, cStatus := range podStatus.ContainerStatuses { </del> <ins> for _, cStatus := range containerStatusesCopy { </ins> cName := cStatus.Name if _, ok := statuses[cName]; !ok { // This would also ignore the infra container.", "positive_passages": [{"docid": "doc-en-kubernetes-4510e09c6fe68ed5e12ffcf7126f6af8b2755c8c7c2f631bec51ed41fca52919", "text": "What happened: One pod stuck at CreateContainerError and can't get recovered automatically. Kubelet log shows that the requested name (let's say Container2) is already in use. shows the Container2 Running, and it's created before Container1 This should never happen. How to reproduce it (as minimally and precisely as possible): I wish i knew. Anything else we need to know?: I know this can be caused by time shifting, but I didn't find any time shifting sign in system log and chrony log, and there is no rebooting between the create timestamp of Container1 and Container2, so this should be caused by something else. This happens intermittently in our env, like 3 times in half a year, and I didn't find any ime shifting sign each time. Environment: Kubernetes version (use ): Client Version: version.Info{Major:\"1\", Minor:\"15\", GitVersion:\"v1.15.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2019-11-13T11:20:18Z\", GoVersion:\"go1.12.12\", Compiler:\"gc\", Platform:\"linux/amd64\"} Server Version: version.Info{Major:\"1\", Minor:\"15\", GitVersion:\"v1.15.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2020-08-28T11:18:26Z\", GoVersion:\"go1.12.12\", Compiler:\"gc\", Platform:\"linux/amd64\"} Cloud provider or hardware configuration: OS (e.g: ): CentOS Linux release 7.5.1804 (Core) Kernel (e.g. ): Linux node-1 3.10.0-957.21.3.el7.x8664 SMP Wed Jul 17 06:57:50 UTC 2019 x8664 x8664 x86_64 GNU/Linux Install tools: kubeadm Network plugin and version (if this is a network-related bug): Others:\n/sig node\nAny update on this issue, we are also facing the same issue. EKS version : 1.14.9 Docker version: 19.03.6-ce AWS CNI: 1.6.2 Intermittently we are also facing this , what might the issue, could please guide us here? Below are the kubelet logs. )\"", "commid": "kubernetes_issue_94557", "tokennum": 571}], "negative_passages": []}
{"query_id": "q-en-kubernetes-be44fa41717b150de78312925771cd94e0fc8ee065f03960afa06dc045c37a51", "query": "statuses[container.Name] = status } <ins> // Copy the slice before sorting it containerStatusesCopy := make([]*kubecontainer.Status, len(podStatus.ContainerStatuses)) copy(containerStatusesCopy, podStatus.ContainerStatuses) </ins> // Make the latest container status comes first. <del> sort.Sort(sort.Reverse(kubecontainer.SortContainerStatusesByCreationTime(podStatus.ContainerStatuses))) </del> <ins> sort.Sort(sort.Reverse(kubecontainer.SortContainerStatusesByCreationTime(containerStatusesCopy))) </ins> // Set container statuses according to the statuses seen in pod status containerSeen := map[string]int{} <del> for _, cStatus := range podStatus.ContainerStatuses { </del> <ins> for _, cStatus := range containerStatusesCopy { </ins> cName := cStatus.Name if _, ok := statuses[cName]; !ok { // This would also ignore the infra container.", "positive_passages": [{"docid": "doc-en-kubernetes-cf3a33a19ef0552fe6ccd0d8ccfc3a21fead851f6c57fd16801184b4e1e277da", "text": "with CreatePodSandboxError: \"CreatePodSandbox for pod \"-f0fe-11ea-9872-)\" failed: rpc error: code = Unknown desc = failed to create a sandbox for pod \"aiqx-server-dep--b9lmv\": operation timeout: context deadline exceeded\" Sep 07 11:40:40 kubelet[2899]: W0907 11:40:40. 2899 ] No ref for container \"docker://7b9c86b529530f15d941f8e68973a202c8f348ab5db864a8371e8c82ddbf9dc4\" (r(-e845-11ea-bd96-) Sep 07 11:40:43 kubelet[2899]: W0907 11:40:43. 2899 ] Unable to create pod sandbox due to conflict. Attempting to remove sandbox \"a73bd9a03d56bc7855e4e89e163e13c5e7173397f10edcc200fb686e1b6885c8\" Sep 07 11:40:43 kubelet[2899]: E0907 11:40:43. 2899 ] Failed to remove the conflicting container \"a73bd9a03d56bc7855e4e89e163e13c5e7173397f10edcc200fb686e1b6885c8\": Error: No such container: a73bd9a03d56bc7855e4e89e163e13c5e7173397f10edcc200fb686e1b6885c8\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_94557", "tokennum": 554}], "negative_passages": []}
{"query_id": "q-en-kubernetes-be44fa41717b150de78312925771cd94e0fc8ee065f03960afa06dc045c37a51", "query": "statuses[container.Name] = status } <ins> // Copy the slice before sorting it containerStatusesCopy := make([]*kubecontainer.Status, len(podStatus.ContainerStatuses)) copy(containerStatusesCopy, podStatus.ContainerStatuses) </ins> // Make the latest container status comes first. <del> sort.Sort(sort.Reverse(kubecontainer.SortContainerStatusesByCreationTime(podStatus.ContainerStatuses))) </del> <ins> sort.Sort(sort.Reverse(kubecontainer.SortContainerStatusesByCreationTime(containerStatusesCopy))) </ins> // Set container statuses according to the statuses seen in pod status containerSeen := map[string]int{} <del> for _, cStatus := range podStatus.ContainerStatuses { </del> <ins> for _, cStatus := range containerStatusesCopy { </ins> cName := cStatus.Name if _, ok := statuses[cName]; !ok { // This would also ignore the infra container.", "positive_passages": [{"docid": "doc-en-kubernetes-af4ac4b9e185e9334a90bdc75507d53790e8bdc2018fef7b4f1e5e30a35b49e6", "text": "/lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /close\nClosing 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", "commid": "kubernetes_issue_94557", "tokennum": 110}], "negative_passages": []}
{"query_id": "q-en-kubernetes-be5fdb913ced9c353e4bfeb78cb3844524accd322efbadd7e8f03d20fd7401d2", "query": "\"k8s.io/apimachinery/pkg/util/diff\" \"k8s.io/apimachinery/pkg/util/intstr\" \"k8s.io/apimachinery/pkg/util/sets\" <ins> \"k8s.io/kubernetes/federation/apis/federation\" </ins> \"k8s.io/kubernetes/pkg/api\" \"k8s.io/kubernetes/pkg/api/testapi\" \"k8s.io/kubernetes/pkg/apis/apps\"", "positive_passages": [{"docid": "doc-en-kubernetes-f29982137c07dadb3e257d7391e0d9b7bfd5f1ce8fdca72f798301cc159728a0", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: After labeling clusters in a Federation, when you type the field is empty. What you expected to happen: The fiels should contain information about the labels in the cluster How to reproduce it (as minimally and precisely as possible): a federation control pane in any Cloud Provider and any DNS provider your cluster: info aboyut the cluster with the flag: Note: if you describe it, you see the labels being : Environment: Kubernetes version (use ): 1.8.0 Cloud provider or hardware configuration**: anyone OS (e.g. from /etc/os-release): Ubuntu 16.04 Kernel (e.g. ): Linux Install tools: curl Others:\n/sig multicluster\nI'm working on it.", "commid": "kubernetes_issue_53729", "tokennum": 179}], "negative_passages": []}
{"query_id": "q-en-kubernetes-be7ab46098e079765ea484fe46d26f283dd6300c8d4a86a9845ffc0552bac88f", "query": "}, } if strings.Contains(err.Error(), \"0/3 nodes are available\") { <del> if strings.Contains(err.Error(), \"2 NodeUnderDiskPressure\") && strings.Contains(err.Error(), \"1 NodeUnderMemoryPressure\") { </del> <ins> if strings.Contains(err.Error(), \"2 node(s) had disk pressure\") && strings.Contains(err.Error(), \"1 node(s) had memory pressure\") { </ins> return } }", "positive_passages": [{"docid": "doc-en-kubernetes-10c13016eb5239afc7a330cfdab91dbf78232a49f2993f71669df735dbb939e1", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature The is not user friendly. There has been to make it better, but we still print in the pending message. We should change these errors to a more human readable message. For example, should be changed to something like . /sig scheduling", "commid": "kubernetes_issue_58546", "tokennum": 91}], "negative_passages": []}
{"query_id": "q-en-kubernetes-be84fd8fc2a9e5af55c3799779d26697a431854f7ee69d65f64d1413ef0878a6", "query": "} } <ins> if utilfeature.DefaultFeatureGate.Enabled(features.HonorPVReclaimPolicy) { if metav1.HasAnnotation(volume.ObjectMeta, storagehelpers.AnnMigratedTo) { // CSI migration scenario - do not depend on in-tree plugin return nil, nil } if volume.Spec.CSI != nil { // CSI volume source scenario - external provisioner is requested return nil, nil } } </ins> // The plugin that provisioned the volume was not found or the volume // was not dynamically provisioned. Try to find a plugin by spec. spec := vol.NewSpecFromPersistentVolume(volume, false)", "positive_passages": [{"docid": "doc-en-kubernetes-17da90f267168da4485057cb3c70835a09c33080424540be2f99c7292698f22f", "text": "In my CSI controller I have enabled the feature gate HonorPVReclaimPolicy for csi-provisioner. Based on the documentation Finalizers can be on a PersistentVolume to ensure that PersistentVolumes having Delete reclaim policy are deleted only after the backing storage are deleted. The newly introduced finalizers and external- are only to dynamically provisioned volumes. I can see the finalizer set on the PV while creating static Persistent Volume. PV deletion is stuck due to this finalizer apiVersion: v1 kind: PersistentVolume metadata: creationTimestamp: \"2023-11-08T11:39:24Z\" deletionGracePeriodSeconds: 0 deletionTimestamp: \"2023-11-08T11:54:31Z\" finalizers: external- name: csi-infoscale-pv PV should be deleted when PVC is deleted. Persistent Volume yaml apiVersion: v1 kind: PersistentVolume metadata: name: csi-infoscale-pv spec: storageClassName: csi-infoscale-sc-prod persistentVolumeReclaimPolicy: Delete capacity: storage: 2Gi accessModes: ReadWriteOnce csi: driver: org.veritas.infoscale # Please provide pre-provisioned Infoscale volume name. volumeHandle: clust21432/vrtskube_dg-/vol1 fsType: vxfs Persistent Volume Claim apiVersion: v1 kind: PersistentVolumeClaim metadata: name: csi-infoscale-pvc-static spec: accessModes: ReadWriteOnce resources: requests: storage: 2Gi storageClassName: csi-infoscale-sc-prod volumeName: csi-infoscale-pv Same thing works fine on OCP. WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version.", "commid": "kubernetes_issue_121799", "tokennum": 440}], "negative_passages": []}
{"query_id": "q-en-kubernetes-be84fd8fc2a9e5af55c3799779d26697a431854f7ee69d65f64d1413ef0878a6", "query": "} } <ins> if utilfeature.DefaultFeatureGate.Enabled(features.HonorPVReclaimPolicy) { if metav1.HasAnnotation(volume.ObjectMeta, storagehelpers.AnnMigratedTo) { // CSI migration scenario - do not depend on in-tree plugin return nil, nil } if volume.Spec.CSI != nil { // CSI volume source scenario - external provisioner is requested return nil, nil } } </ins> // The plugin that provisioned the volume was not found or the volume // was not dynamically provisioned. Try to find a plugin by spec. spec := vol.NewSpecFromPersistentVolume(volume, false)", "positive_passages": [{"docid": "doc-en-kubernetes-0ba3f4f18a7007434ced94c47e051d55455d5fb79cd77986fc1ae4d5bc653af8", "text": "Client Version: version.Info{Major:\"1\", Minor:\"27\", GitVersion:\"v1.27.5\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2023-08-24T00:48:26Z\", GoVersion:\"go1.20.7\", Compiler:\"gc\", Platform:\"linux/amd64\"} Kustomize Version: v5.0.1 Server Version: version.Info{Major:\"1\", Minor:\"27\", GitVersion:\"v1.27.5\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2023-08-24T00:42:11Z\", GoVersion:\"go1.20.7\", Compiler:\"gc\", Platform:\"linux/amd64\"} Vanilla K8s setup <details</details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig storage maybe similar issues should go in\nOpened similar issue in external-provisioner repo also There is no reply on that as well. Can you please help understand the behavior of the feature HonorPVReclaimPolicy.\nIf you want Persistent Volume (PV) to be deleted when the associated Persistent Volume Claim (PVC) is deleted, you donot need to use finalizers explicitly. Kubernetes handles this behavior by default. It is ok that if you use to get the desire output using Finalizer we can do it.\nAs per my understanding Please follow the steps : Add finalizer in metadata of as you did above need to make change in the controller which is handling PV deletion in .go file. See whether the controller administrator is working or not. I think it will work.\nFinalizer is because the feature gate HonorPVReclaimPolicy for csi-provisioner is enabled. We are not adding the finalizer explicitly. From the documentation, \"The newly introduced finalizers and external- are only to dynamically provisioned volumes.\" Not sure why is the finalizer getting set.", "commid": "kubernetes_issue_121799", "tokennum": 555}], "negative_passages": []}
{"query_id": "q-en-kubernetes-be84fd8fc2a9e5af55c3799779d26697a431854f7ee69d65f64d1413ef0878a6", "query": "} } <ins> if utilfeature.DefaultFeatureGate.Enabled(features.HonorPVReclaimPolicy) { if metav1.HasAnnotation(volume.ObjectMeta, storagehelpers.AnnMigratedTo) { // CSI migration scenario - do not depend on in-tree plugin return nil, nil } if volume.Spec.CSI != nil { // CSI volume source scenario - external provisioner is requested return nil, nil } } </ins> // The plugin that provisioned the volume was not found or the volume // was not dynamically provisioned. Try to find a plugin by spec. spec := vol.NewSpecFromPersistentVolume(volume, false)", "positive_passages": [{"docid": "doc-en-kubernetes-592cda3e1f42c2eb1f47fff2bb790922cec52a4f953f170e43c5acb028d04e55", "text": "Also, for deleting PV it requires the annotation \"\" but this annotation is set in case of dynamic PVs. Should it be set explicitly for static PV?\nThis feature is alpha so the feature gate is not enabled by default. Did you enable the feature gate on kube-controller-manager?\nYes, i have enabled this feature.\nexternal- is also applied to statically provisioned volumes. FYI\nHi Which version of the external provisioner is the driver using? Does the driver meet the requirements of the CSI spec on the DeleteVolume PRC? FYI: Is this problem occasional or permanently reproducible? Can you provide the provisioner logs at that time?\n/triage needs-information\ncc\ncc\nExternal provisioner used is : \"csi-provisioner:v3.5.0\" This problem is always reproducible Provisioner logs: I1123 12:22:38. 1 ] handleProtectionFinalizer Volume : &PersistentVolume{ObjectMeta:{csi-infoscale-pv -420a-4e9e-be82- 0 2023-11-23 12:21:18 +0000 UTC <nil<nilmap[] map[{\"apiVersion\":\"v1\",\"kind\":\"PersistentVolume\",\"metadata\":{\"annotations\":{},\"name\":\"csi-infoscale-pv\"},\"spec\":{\"accessModes\":[\"ReadWriteOnce\"],\"capacity\":{\"storage\":\"2Gi\"},\"csi\":{\"driver\":\"org.veritas.infoscale\",\"fsType\":\"vxfs\",\"volumeHandle\":\"clust40559/vrtskubedg-/vol1\"},\"persistentVolumeReclaimPolicy\":\"Delete\",\"storageClassName\":\"csi-infoscale-sc-prod\"}} ] [] [ external-] [{kubectl-client-side-apply Update v1 2023-11-23 12:21:18 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:annotations\":{\".\":{},\"\":{}}},\"f:spec\":{\"f:accessModes\":{},\"f:capacity\":{\".\":{},\"f:storage\":{}},\"f:csi\":{\".", "commid": "kubernetes_issue_121799", "tokennum": 563}], "negative_passages": []}
{"query_id": "q-en-kubernetes-be84fd8fc2a9e5af55c3799779d26697a431854f7ee69d65f64d1413ef0878a6", "query": "} } <ins> if utilfeature.DefaultFeatureGate.Enabled(features.HonorPVReclaimPolicy) { if metav1.HasAnnotation(volume.ObjectMeta, storagehelpers.AnnMigratedTo) { // CSI migration scenario - do not depend on in-tree plugin return nil, nil } if volume.Spec.CSI != nil { // CSI volume source scenario - external provisioner is requested return nil, nil } } </ins> // The plugin that provisioned the volume was not found or the volume // was not dynamically provisioned. Try to find a plugin by spec. spec := vol.NewSpecFromPersistentVolume(volume, false)", "positive_passages": [{"docid": "doc-en-kubernetes-3ecd202a68dc777f32874cd48d4b39291a9bf67f2771bfe1a1dd4808649976b8", "text": "\":{},\"f:driver\":{},\"f:fsType\":{},\"f:volumeHandle\":{}},\"f:persistentVolumeReclaimPolicy\":{},\"f:storageClassName\":{},\"f:volumeMode\":{}}} } {csi-provisioner Update v1 2023-11-23 12:21:22 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:finalizers\":{\"v:\"external-\"\":{}}}} } {kube-controller-manager Update v1 2023-11-23 12:21:22 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:annotations\":{\"\":{}}},\"f:spec\":{\"f:claimRef\":{\".", "commid": "kubernetes_issue_121799", "tokennum": 208}], "negative_passages": []}
{"query_id": "q-en-kubernetes-be84fd8fc2a9e5af55c3799779d26697a431854f7ee69d65f64d1413ef0878a6", "query": "} } <ins> if utilfeature.DefaultFeatureGate.Enabled(features.HonorPVReclaimPolicy) { if metav1.HasAnnotation(volume.ObjectMeta, storagehelpers.AnnMigratedTo) { // CSI migration scenario - do not depend on in-tree plugin return nil, nil } if volume.Spec.CSI != nil { // CSI volume source scenario - external provisioner is requested return nil, nil } } </ins> // The plugin that provisioned the volume was not found or the volume // was not dynamically provisioned. Try to find a plugin by spec. spec := vol.NewSpecFromPersistentVolume(volume, false)", "positive_passages": [{"docid": "doc-en-kubernetes-fb611cee6f984fef598fa329474fd3d3abef5728e2a0833d8129f0a5ee9ed92e", "text": "\":{},\"f:apiVersion\":{},\"f:kind\":{},\"f:name\":{},\"f:namespace\":{},\"f:resourceVersion\":{},\"f:uid\":{}}}} } {kube-controller-manager Update v1 2023-11-23 12:22:38 +0000 UTC FieldsV1 {\"f:status\":{\"f:phase\":{}}} status}]},Spec:PersistentVolumeSpec{Capacity:ResourceList{storage: {{ 0} {<nil} 2Gi BinarySI},},PersistentVolumeSource:PersistentVolumeSource{GCEPersistentDisk:nil,AWSElasticBlockStore:nil,HostPath:nil,Glusterfs:nil,NFS:nil,RBD:nil,ISCSI:nil,Cinder:nil,CephFS:nil,FC:nil,Flocker:nil,FlexVolume:nil,AzureFile:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Local:nil,StorageOS:nil,CSI:&CSIPersistentVolumeSource{Driver:org.veritas.infoscale,VolumeHandle:clust40559/vrtskubedg-/vol1,ReadOnly:false,FSType:vxfs,VolumeAttributes:map[string]string{},ControllerPublishSecretRef:nil,NodeStageSecretRef:nil,NodePublishSecretRef:nil,ControllerExpandSecretRef:nil,NodeExpandSecretRef:nil,},},AccessModes:[ReadWriteOnce],ClaimRef:&ObjectReference{Kind:PersistentVolumeClaim,Namespace:default,Name:csi-infoscale-pvc-static,UID:-59a5-4f02-83ac-,APIVersion:v1,ResourceVersion:,FieldPath:,},PersistentVolumeReclaimPolicy:Delete,StorageClassName:csi-infoscale-sc-prod,MountOptions:[],VolumeMode:Filesystem,NodeAffinity:nil,},Status:PersistentVolumeStatus{Phase:Released,Message:,Reason:,},} I1123 12:22:38. 1 ] delete \"csi-infoscale-pv\": started I1123 12:22:38. 1 ] GRPC call: /csi.v1.Controller/DeleteVolume I1123 12:22:38. 1 ] GRPC request: {\"volumeid\":\"clust40559/vrtskubedg-/vol1\"} I1123 12:22:39.", "commid": "kubernetes_issue_121799", "tokennum": 705}], "negative_passages": []}
{"query_id": "q-en-kubernetes-be84fd8fc2a9e5af55c3799779d26697a431854f7ee69d65f64d1413ef0878a6", "query": "} } <ins> if utilfeature.DefaultFeatureGate.Enabled(features.HonorPVReclaimPolicy) { if metav1.HasAnnotation(volume.ObjectMeta, storagehelpers.AnnMigratedTo) { // CSI migration scenario - do not depend on in-tree plugin return nil, nil } if volume.Spec.CSI != nil { // CSI volume source scenario - external provisioner is requested return nil, nil } } </ins> // The plugin that provisioned the volume was not found or the volume // was not dynamically provisioned. Try to find a plugin by spec. spec := vol.NewSpecFromPersistentVolume(volume, false)", "positive_passages": [{"docid": "doc-en-kubernetes-21563431fea9ed5a14c1fde8160d9fcab633c35237ee882cf06625b1768a9487", "text": "1 ] GRPC response: {} I1123 12:22:39. 1 ] GRPC error: <nilI1123 12:22:39. 1 ] delete \"csi-infoscale-pv\": volume deleted I1123 12:22:39. 1 ] delete \"csi-infoscale-pv\": failed to remove finalizer for persistentvolume: Operation cannot be fulfilled on persistentvolumes \"csi-infoscale-pv\": the object has been modified; please apply your changes to the latest version and try again W1123 12:22:39. 1 ] Retrying syncing volume \"csi-infoscale-pv\", failure 0 E1123 12:22:39. 1 ] error syncing volume \"csi-infoscale-pv\": Operation cannot be fulfilled on persistentvolumes \"csi-infoscale-pv\": the object has been modified; please apply your changes to the latest version and try again I1123 12:22:39. 1 ] handleProtectionFinalizer Volume : &PersistentVolume{ObjectMeta:{csi-infoscale-pv -420a-4e9e-be82- 0 2023-11-23 12:21:18 +0000 UTC 2023-11-23 12:22:38 +0000 UTC 0xc0007f63d0 map[] map[{\"apiVersion\":\"v1\",\"kind\":\"PersistentVolume\",\"metadata\":{\"annotations\":{},\"name\":\"csi-infoscale-pv\"},\"spec\":{\"accessModes\":[\"ReadWriteOnce\"],\"capacity\":{\"storage\":\"2Gi\"},\"csi\":{\"driver\":\"org.veritas.infoscale\",\"fsType\":\"vxfs\",\"volumeHandle\":\"clust40559/vrtskubedg-/vol1\"},\"persistentVolumeReclaimPolicy\":\"Delete\",\"storageClassName\":\"csi-infoscale-sc-prod\"}} ] [] [external-] [{kubectl-client-side-apply Update v1 2023-11-23 12:21:18 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:annotations\":{\".\":{},\"\":{}}},\"f:spec\":{\"f:accessModes\":{},\"f:capacity\":{\".\":{},\"f:storage\":{}},\"f:csi\":{\".", "commid": "kubernetes_issue_121799", "tokennum": 610}], "negative_passages": []}
{"query_id": "q-en-kubernetes-be84fd8fc2a9e5af55c3799779d26697a431854f7ee69d65f64d1413ef0878a6", "query": "} } <ins> if utilfeature.DefaultFeatureGate.Enabled(features.HonorPVReclaimPolicy) { if metav1.HasAnnotation(volume.ObjectMeta, storagehelpers.AnnMigratedTo) { // CSI migration scenario - do not depend on in-tree plugin return nil, nil } if volume.Spec.CSI != nil { // CSI volume source scenario - external provisioner is requested return nil, nil } } </ins> // The plugin that provisioned the volume was not found or the volume // was not dynamically provisioned. Try to find a plugin by spec. spec := vol.NewSpecFromPersistentVolume(volume, false)", "positive_passages": [{"docid": "doc-en-kubernetes-3ecd202a68dc777f32874cd48d4b39291a9bf67f2771bfe1a1dd4808649976b8", "text": "\":{},\"f:driver\":{},\"f:fsType\":{},\"f:volumeHandle\":{}},\"f:persistentVolumeReclaimPolicy\":{},\"f:storageClassName\":{},\"f:volumeMode\":{}}} } {csi-provisioner Update v1 2023-11-23 12:21:22 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:finalizers\":{\"v:\"external-\"\":{}}}} } {kube-controller-manager Update v1 2023-11-23 12:21:22 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:annotations\":{\"\":{}}},\"f:spec\":{\"f:claimRef\":{\".", "commid": "kubernetes_issue_121799", "tokennum": 208}], "negative_passages": []}
{"query_id": "q-en-kubernetes-be84fd8fc2a9e5af55c3799779d26697a431854f7ee69d65f64d1413ef0878a6", "query": "} } <ins> if utilfeature.DefaultFeatureGate.Enabled(features.HonorPVReclaimPolicy) { if metav1.HasAnnotation(volume.ObjectMeta, storagehelpers.AnnMigratedTo) { // CSI migration scenario - do not depend on in-tree plugin return nil, nil } if volume.Spec.CSI != nil { // CSI volume source scenario - external provisioner is requested return nil, nil } } </ins> // The plugin that provisioned the volume was not found or the volume // was not dynamically provisioned. Try to find a plugin by spec. spec := vol.NewSpecFromPersistentVolume(volume, false)", "positive_passages": [{"docid": "doc-en-kubernetes-11586616fd718035f7c04dbcead8d898c73d9e9840ec80b2b32382f64622ed92", "text": "\":{},\"f:apiVersion\":{},\"f:kind\":{},\"f:name\":{},\"f:namespace\":{},\"f:resourceVersion\":{},\"f:uid\":{}}}} } {kube-controller-manager Update v1 2023-11-23 12:22:38 +0000 UTC FieldsV1 {\"f:status\":{\"f:message\":{},\"f:phase\":{}}} status}]},Spec:PersistentVolumeSpec{Capacity:ResourceList{storage: {{ 0} {<nil} 2Gi BinarySI},},PersistentVolumeSource:PersistentVolumeSource{GCEPersistentDisk:nil,AWSElasticBlockStore:nil,HostPath:nil,Glusterfs:nil,NFS:nil,RBD:nil,ISCSI:nil,Cinder:nil,CephFS:nil,FC:nil,Flocker:nil,FlexVolume:nil,AzureFile:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Local:nil,StorageOS:nil,CSI:&CSIPersistentVolumeSource{Driver:org.veritas.infoscale,VolumeHandle:clust40559/vrtskubedg-/vol1,ReadOnly:false,FSType:vxfs,VolumeAttributes:map[string]string{},ControllerPublishSecretRef:nil,NodeStageSecretRef:nil,NodePublishSecretRef:nil,ControllerExpandSecretRef:nil,NodeExpandSecretRef:nil,},},AccessModes:[ReadWriteOnce],ClaimRef:&ObjectReference{Kind:PersistentVolumeClaim,Namespace:default,Name:csi-infoscale-pvc-static,UID:-59a5-4f02-83ac-,APIVersion:v1,ResourceVersion:,FieldPath:,},PersistentVolumeReclaimPolicy:Delete,StorageClassName:csi-infoscale-sc-prod,MountOptions:[],VolumeMode:Filesystem,NodeAffinity:nil,},Status:PersistentVolumeStatus{Phase:Failed,Message:error getting deleter volume plugin for volume \"csi-infoscale-pv\": no deletable volume plugin matched,Reason:,},} I1123 12:22:40.", "commid": "kubernetes_issue_121799", "tokennum": 650}], "negative_passages": []}
{"query_id": "q-en-kubernetes-be84fd8fc2a9e5af55c3799779d26697a431854f7ee69d65f64d1413ef0878a6", "query": "} } <ins> if utilfeature.DefaultFeatureGate.Enabled(features.HonorPVReclaimPolicy) { if metav1.HasAnnotation(volume.ObjectMeta, storagehelpers.AnnMigratedTo) { // CSI migration scenario - do not depend on in-tree plugin return nil, nil } if volume.Spec.CSI != nil { // CSI volume source scenario - external provisioner is requested return nil, nil } } </ins> // The plugin that provisioned the volume was not found or the volume // was not dynamically provisioned. Try to find a plugin by spec. spec := vol.NewSpecFromPersistentVolume(volume, false)", "positive_passages": [{"docid": "doc-en-kubernetes-372f094f1905cb03e404d407c686a802e84a00b41a059cf5fa90382ee5601de2", "text": "1 ] handleProtectionFinalizer Volume : &PersistentVolume{ObjectMeta:{csi-infoscale-pv -420a-4e9e-be82- 0 2023-11-23 12:21:18 +0000 UTC 2023-11-23 12:22:38 +0000 UTC 0xc0007f63d0 map[] map[{\"apiVersion\":\"v1\",\"kind\":\"PersistentVolume\",\"metadata\":{\"annotations\":{},\"name\":\"csi-infoscale-pv\"},\"spec\":{\"accessModes\":[\"ReadWriteOnce\"],\"capacity\":{\"storage\":\"2Gi\"},\"csi\":{\"driver\":\"org.veritas.infoscale\",\"fsType\":\"vxfs\",\"volumeHandle\":\"clust40559/vrtskubedg-/vol1\"},\"persistentVolumeReclaimPolicy\":\"Delete\",\"storageClassName\":\"csi-infoscale-sc-prod\"}} ] [] [external-] [{kubectl-client-side-apply Update v1 2023-11-23 12:21:18 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:annotations\":{\".\":{},\"\":{}}},\"f:spec\":{\"f:accessModes\":{},\"f:capacity\":{\".\":{},\"f:storage\":{}},\"f:csi\":{\".\":{},\"f:driver\":{},\"f:fsType\":{},\"f:volumeHandle\":{}},\"f:persistentVolumeReclaimPolicy\":{},\"f:storageClassName\":{},\"f:volumeMode\":{}}} } {csi-provisioner Update v1 2023-11-23 12:21:22 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:finalizers\":{\"v:\"external-\"\":{}}}} } {kube-controller-manager Update v1 2023-11-23 12:21:22 +0000 UTC FieldsV1 {\"f:metadata\":{\"f:annotations\":{\"\":{}}},\"f:spec\":{\"f:claimRef\":{\".", "commid": "kubernetes_issue_121799", "tokennum": 599}], "negative_passages": []}
{"query_id": "q-en-kubernetes-be84fd8fc2a9e5af55c3799779d26697a431854f7ee69d65f64d1413ef0878a6", "query": "} } <ins> if utilfeature.DefaultFeatureGate.Enabled(features.HonorPVReclaimPolicy) { if metav1.HasAnnotation(volume.ObjectMeta, storagehelpers.AnnMigratedTo) { // CSI migration scenario - do not depend on in-tree plugin return nil, nil } if volume.Spec.CSI != nil { // CSI volume source scenario - external provisioner is requested return nil, nil } } </ins> // The plugin that provisioned the volume was not found or the volume // was not dynamically provisioned. Try to find a plugin by spec. spec := vol.NewSpecFromPersistentVolume(volume, false)", "positive_passages": [{"docid": "doc-en-kubernetes-8654731eb8139b66a1cecad4a317b2078534f6977aa1c7223978f7fff83e9392", "text": "\":{},\"f:apiVersion\":{},\"f:kind\":{},\"f:name\":{},\"f:namespace\":{},\"f:resourceVersion\":{},\"f:uid\":{}}}} } {kube-controller-manager Update v1 2023-11-23 12:22:38 +0000 UTC FieldsV1 {\"f:status\":{\"f:message\":{},\"f:phase\":{}}} status}]},Spec:PersistentVolumeSpec{Capacity:ResourceList{storage: {{ 0} {<nil} 2Gi BinarySI},},PersistentVolumeSource:PersistentVolumeSource{GCEPersistentDisk:nil,AWSElasticBlockStore:nil,HostPath:nil,Glusterfs:nil,NFS:nil,RBD:nil,ISCSI:nil,Cinder:nil,CephFS:nil,FC:nil,Flocker:nil,FlexVolume:nil,AzureFile:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Local:nil,StorageOS:nil,CSI:&CSIPersistentVolumeSource{Driver:org.veritas.infoscale,VolumeHandle:clust40559/vrtskubedg-/vol1,ReadOnly:false,FSType:vxfs,VolumeAttributes:map[string]string{},ControllerPublishSecretRef:nil,NodeStageSecretRef:nil,NodePublishSecretRef:nil,ControllerExpandSecretRef:nil,NodeExpandSecretRef:nil,},},AccessModes:[ReadWriteOnce],ClaimRef:&ObjectReference{Kind:PersistentVolumeClaim,Namespace:default,Name:csi-infoscale-pvc-static,UID:-59a5-4f02-83ac-,APIVersion:v1,ResourceVersion:,FieldPath:,},PersistentVolumeReclaimPolicy:Delete,StorageClassName:csi-infoscale-sc-prod,MountOptions:[],VolumeMode:*Filesystem,NodeAffinity:nil,},Status:PersistentVolumeStatus{Phase:Failed,Message:error getting deleter volume plugin for volume \"csi-infoscale-pv\": no deletable volume plugin matched,Reason:,},}\nThank you I will try to fix it. /remove-triage needs-information /assign", "commid": "kubernetes_issue_121799", "tokennum": 661}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bed9b6d45ae7ae677fce674fee9883dd43cc15342cec6c556f34832fa6a4e270", "query": "} func (s *containerScope) Admit(pod *v1.Pod) lifecycle.PodAdmitResult { <del> // Exception - Policy : none if s.policy.Name() == PolicyNone { return s.admitPolicyNone(pod) } </del> for _, container := range append(pod.Spec.InitContainers, pod.Spec.Containers...) { bestHint, admit := s.calculateAffinity(pod, &container) klog.InfoS(\"Best TopologyHint\", \"bestHint\", bestHint, \"pod\", klog.KObj(pod), \"containerName\", container.Name)", "positive_passages": [{"docid": "doc-en-kubernetes-4d10931e14d2065e9a15e6880eb555f03f2fd6b09352947daeddff0435b576bc", "text": "Follow up from: See details there. When is , there is no need to discover the NUMA topology. /sig node /priority backlog /kind feature /help-wanted\n/cc\n/triage accepted\nI would like to take this up also can I get more brief information about it? code review comments from asking that inside the NewManager() implementation, we need to skip NewPolicyOptions and NewNUMAInfo but when the NumaTopology comes kubelet issue also comes. I need some more information to start with this!\n/cc\nWhen there is no topology manger policy specified, NewManager should be a no-op. Just skip all checks.\nExactly. Just to add: we may need few iterations over the change to get a clean flow in the call.\n/assign", "commid": "kubernetes_issue_116391", "tokennum": 166}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bef27bef5c19cde72d5a3fb04023d8a16b2c68eb91d6f8f4b4b7eeaffab2c5a2", "query": "Name: \"foo\"}}, api.Namespace{ ObjectMeta: api.ObjectMeta{ <ins> Name: \"foo\"}, Status: api.NamespaceStatus{ Phase: api.NamespaceTerminating, }, }, false}, {api.Namespace{ ObjectMeta: api.ObjectMeta{ Name: \"foo\"}}, api.Namespace{ ObjectMeta: api.ObjectMeta{ </ins> Name: \"bar\"}, Status: api.NamespaceStatus{ Phase: api.NamespaceTerminating,", "positive_passages": [{"docid": "doc-en-kubernetes-859a8b847337ca2cf9879726f3bdb71f0db5559ee2589591ceae612e41f71a1b", "text": "There is a funny subtle behvaiour in get namespaces, in which if i call more than one time, it seems that the removal from Terminating state is accelarated. It seems this might indicate a bug, or maybe its not a bug and the eventual semantics of is a little funny sometimes. in any case, here's what we are seeing : 1) when i delete a namespace the first time usning kubectl, we get a state change to . that is correct, of course. 2) but ... if make the call a second time, then the same status line is immediately removed from . Expected behaviour : A second call to \"kubectl delete ...\" shouldn't have any effect on the timing of removal of a namespace from 'Terminating' state*... So i guess there is some \"eventual consistency\" subtle bug that is resolved by repeated calls to\nsuggests this may not be e bug, maybe its just the etcd eventual deleter thingy.\nLooks to definitely be a bug. The 2nd delete seems to have interrupted the delete process and artifacts (like events) from the namespace still exist in etcd.\ninvestigating...\noops, see the error, will submit a fix.\nI have a fix, but need a test case, will submit PR tomorrow AM", "commid": "kubernetes_issue_6633", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bff351294a9b81dd663fed0e8659254d8c2faa847c139e4daf1cb8d432aac742", "query": "Rule:       admissionv1beta1.Rule{APIGroups: []string{\"\"}, APIVersions: []string{\"v1\"}, Resources: []string{\"pods\"}}, }}, ObjectSelector:          webhook.objectSelector, <ins> NamespaceSelector:       &metav1.LabelSelector{MatchLabels: nsLabels}, </ins> FailurePolicy:           &fail, ReinvocationPolicy:      webhook.policy, AdmissionReviewVersions: []string{\"v1beta1\"}, }) } <ins> // Register a marker checking webhook with each set of webhook configurations markerEndpoint := webhookServer.URL + \"/marker\" webhooks = append(webhooks, admissionv1beta1.MutatingWebhook{ Name: \"admission.integration.test.marker\", ClientConfig: admissionv1beta1.WebhookClientConfig{ URL:      &markerEndpoint, CABundle: localhostCert, }, Rules: []admissionv1beta1.RuleWithOperations{{ Operations: []admissionv1beta1.OperationType{admissionv1beta1.OperationAll}, Rule:       admissionv1beta1.Rule{APIGroups: []string{\"\"}, APIVersions: []string{\"v1\"}, Resources: []string{\"pods\"}}, }}, NamespaceSelector:       &metav1.LabelSelector{MatchLabels: markerNsLabels}, ObjectSelector:          &metav1.LabelSelector{MatchLabels: map[string]string{\"marker\": \"true\"}}, AdmissionReviewVersions: []string{\"v1beta1\"}, }) </ins> cfg, err := client.AdmissionregistrationV1beta1().MutatingWebhookConfigurations().Create(&admissionv1beta1.MutatingWebhookConfiguration{ ObjectMeta: metav1.ObjectMeta{Name: fmt.Sprintf(\"admission.integration.test-%d\", i)},", "positive_passages": [{"docid": "doc-en-kubernetes-ddb9bacde18c9f97d2ebd4306efde2d358d8075e932023fee86edf729006549a", "text": "Which jobs are failing: Which test(s) are failing: Since when has it been failing: Testgrid link: Reason for failure: Anything else we need to know: /sig api-machinery /assign\n/cc\nwant to take a look at the audit event issue first? I can dig in after that if issues remain.\nyes, I'm looking at the audit event issue now\nactually the failure message suggests that the missing audit log is caused by unexpected admission invocation: I think it's unrelated to auditing Note that there are two tests named \"no reinvocation of webhook B when in-tree or prior webhook mutations\" :( and from the audit log (), it also suggests that the test is hitting a wrong endpoint\nThanks I'll dig in.", "commid": "kubernetes_issue_82693", "tokennum": 163}], "negative_passages": []}
{"query_id": "q-en-kubernetes-bffbd31fa74e52843a590a775cf27eae12acf496c973dd78ab34bc7aa3c02e45", "query": "} func (az *Cloud) isCurrentInstance(name types.NodeName, metadataVMName string) (bool, error) { <ins> var err error </ins> nodeName := mapNodeNameToVMName(name) <ins> // VMSS vmName is not same with hostname, use hostname instead. </ins> if az.VMType == vmTypeVMSS { <del> // VMSS vmName is not same with hostname, construct the node name \"{computer-name-prefix}{base-36-instance-id}\". // Refer https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-instance-ids#scale-set-vm-computer-name. if ssName, instanceID, err := extractVmssVMName(metadataVMName); err == nil { instance, err := strconv.ParseInt(instanceID, 10, 64) if err != nil { return false, fmt.Errorf(\"failed to parse VMSS instanceID %q: %v\", instanceID, err) } metadataVMName = fmt.Sprintf(\"%s%06s\", ssName, strconv.FormatInt(instance, 36)) </del> <ins> metadataVMName, err = os.Hostname() if err != nil { return false, err } // Use name from env variable \"NODE_NAME\" if it is set. nodeNameEnv := os.Getenv(nodeNameEnvironmentName) if nodeNameEnv != \"\" { metadataVMName = nodeNameEnv </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-93c0a615d6725c12b66abb2dead01e17ca700d451119b1467d3edce68f73a013", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: If computer name prefix does not match VMSS name, then Azure cloud provider will use VMSS API instead of using metadata service data. This leads to throttling, because every affected kubelet is making API requests. What you expected to happen: Azure cloud provider should use metadata service data instead of calling VMSS API when instance is current. How to reproduce it (as minimally and precisely as possible): Set computer name prefix of the VMSS to something different than default. You should observe Azure provider making requests to the VMSS API rather than using metadata service, which leads to throttling if you have multiple kubelets with this bug. Anything else we need to know?: This is bug was introduced by - returns false even if instance is current, because it expects node name to match VMSS name + instance id, however node name is derived from the computer-name-prefix which can be different than VMSS name. Node name should be matched against , not against . Environment: Kubernetes version (use ): 1.18.x and higher Cloud provider or hardware configuration: azure /sig cloud-provider\n/sig cloud-provider\n/area provider/azure\nCC\n/remove-sig cloud-provider /sig cloud-provider (trying to remove the label)\n/sig cloud-provider\nThanks for the reporting. Unfortunately, computer name prefix is not included in IMDS, so it can't be used without VMSS API for constructing the NodeName. Would check what could we do to workaround the issue.\nCan you memorize the computer name prefix in the first request to the Azure API and then use it for the isCurrentInstance check?\nopened to fix the issue. Would you like to have a look?\nI can confirm that your change should fix the problem I reported. Do you know if your fix will be to 1.18.x?\nis working on the cherry pick\nThank you for quick fix!", "commid": "kubernetes_issue_92733", "tokennum": 464}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c012b6ae7a29c7990a78a95fbc530c1691bdda7fff9051a124af84308e2593ea", "query": "Expect(lineCount).To(Equal(expectedLineCount), \"Line count of the written file should be %d.\", expectedLineCount) <del> // Verify the pod is scheduled in the other zone. By(\"verifying the pod is scheduled in a different zone.\") var otherZone string if cloudZones[0] == podZone { otherZone = cloudZones[1] } else { otherZone = cloudZones[0] </del> <ins> } func addTaint(c clientset.Interface, ns string, nodes []v1.Node, podZone string) (removeTaint func()) { reversePatches := make(map[string][]byte) for _, node := range nodes { oldData, err := json.Marshal(node) Expect(err).NotTo(HaveOccurred()) node.Spec.Taints = append(node.Spec.Taints, v1.Taint{ Key:    taintKeyPrefix + ns, Value:  podZone, Effect: v1.TaintEffectNoSchedule, }) newData, err := json.Marshal(node) Expect(err).NotTo(HaveOccurred()) patchBytes, err := strategicpatch.CreateTwoWayMergePatch(oldData, newData, v1.Node{}) Expect(err).NotTo(HaveOccurred()) reversePatchBytes, err := strategicpatch.CreateTwoWayMergePatch(newData, oldData, v1.Node{}) Expect(err).NotTo(HaveOccurred()) reversePatches[node.Name] = reversePatchBytes _, err = c.CoreV1().Nodes().Patch(node.Name, types.StrategicMergePatchType, patchBytes) Expect(err).ToNot(HaveOccurred()) </ins> } <del> nodeName = pod.Spec.NodeName node, err = c.CoreV1().Nodes().Get(nodeName, metav1.GetOptions{}) Expect(err).ToNot(HaveOccurred()) newPodZone := node.Labels[apis.LabelZoneFailureDomain] Expect(newPodZone).To(Equal(otherZone), \"The pod should be scheduled in zone %s after all nodes in zone %s have been deleted\", otherZone, podZone) </del> <ins> return func() { for nodeName, reversePatch := range reversePatches { _, err := c.CoreV1().Nodes().Patch(nodeName, types.StrategicMergePatchType, reversePatch) Expect(err).ToNot(HaveOccurred()) } } </ins> } func testRegionalDelayedBinding(c clientset.Interface, ns string) {", "positive_passages": [{"docid": "doc-en-kubernetes-07b454797aabeff00bf033fc34fa4c22bd06966ba8574ac0fa868459bacbceea", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: What happened: Testgrid: https://k8s-\n/assign\nThe test's assumption about test parameter is wrong. Previously it assumed the group name is the same across all zones, but they are different in regional clusters. Looking into using node taints as the permanent fix, as suggested by the TODO comment in the test.\nHm I think taint based evictions is still an alpha feature.\nOK. I propose the following solution: Get the zone of Schedule the StatefulSet pod to that zone using node affinity; wait for the pod to run Remove the node affinity from StatefulSet Delete\nCan it be simplified? Schedule the pod Figure out which zone that pod got scheduled in Delete the instance group of that zone\nUnfortunately I don't know of a good way to look up the instance group given the zone, since there could be instance groups from multiple clusters in the same project\nHow about: Schedule the pod Figure out the zone Taint all the nodes in the zone Kill the pod\nTaint with NoSchedule? yeah that sounds good", "commid": "kubernetes_issue_69005", "tokennum": 267}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c02c321cff997cfce6880aa80faca4c285f424e4cf6be75c1e47c80a2ecd0809", "query": "ginkgo.BeforeEach(func() { c = f.ClientSet ns = f.Namespace.Name <ins> dc = f.DynamicClient </ins> }) ginkgo.It(\"deployment reaping should cascade to its replica sets and pods\", func() {", "positive_passages": [{"docid": "doc-en-kubernetes-cea21dfbf74ea26aea8b8fcc0c8d9d3e2b3e4488cd9f6d30773b87652fe6e220", "text": "[x] Original approval issue: [x] Test pr: [x] Two weeks soak end date: 19 November 2020 This issue is created to allow edit by /wip /hold According to this APIsnoop query, there are still some remaining Deployment endpoints which are untested. a Deployment with a static label the Deployment with a new Label and updated data the Deployment to ensure it's patched all Deployments in all Namespaces find the Deployment(1) ensure that the Deployment is found and is patched Namespaced Deployment(1) via a Collection with a LabelSelector Discover useragents: List endpoints hit by the test: Display endpoint coverage change: If a test with these calls gets merged, test coverage will go up by 5 points* This test is also created with the goal of conformance promotion.\n/sig testing /sig architecture /area conformance\nBobyMcbobs commented in original Issue: Unsure if the endpoint replaceAppsV1NamespacedDeploymentStatus is able to be hit. When this endpoint is attempted to be updated the data after retrieving the update resource doesn't reflect the values in the update\n/assign\nWhen using the appv1.Deployment structure instead of maps of interfaces to build the structure in a patch of the Deployment, this error comes up. Still in progress yment-static\":\"true\"}: does not match template , spec.selector: Invalid value: \"null\": field is immutable]\nreplaceAppsV1NamespacedDeploymentStatus to test. Increase cover by 1 Endpoint\n/reopen PR reverted by due to flaky test\nReopened this issue. <detailsIn response to : /reopen PR reverted by due to flaky test 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\nIssues 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\n/reopen Soaking, ready for promotion 19 November 2020\nReopened this issue. <detailsIn response to : /reopen Soaking, ready for promotion 19 November 2020 Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_90916", "tokennum": 522}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c02c321cff997cfce6880aa80faca4c285f424e4cf6be75c1e47c80a2ecd0809", "query": "ginkgo.BeforeEach(func() { c = f.ClientSet ns = f.Namespace.Name <ins> dc = f.DynamicClient </ins> }) ginkgo.It(\"deployment reaping should cascade to its replica sets and pods\", func() {", "positive_passages": [{"docid": "doc-en-kubernetes-ff9ccf83336a9bf28b0576a991dfda56392cc48f280c272644ff154877b8104d", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/remove-lifecycle stale\n/triage accepted\n/merged", "commid": "kubernetes_issue_90916", "tokennum": 34}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c05c2cc70c2ef67ecd42837076a58c41d08e71b002757478fd6a9f5509ecae0d", "query": "func (i *Instances) NodeAddresses(name string) ([]api.NodeAddress, error) { glog.V(4).Infof(\"NodeAddresses(%v) called\", name) <del> srv, err := getServerByName(i.compute, name) </del> <ins> addrs, err := getAddressesByName(i.compute, name) </ins> if err != nil { return nil, err } <del> addrs := []api.NodeAddress{} for _, addr := range findAddrs(srv.Addresses[\"private\"]) { addrs = append(addrs, api.NodeAddress{ Type:    api.NodeInternalIP, Address: addr, }) } for _, addr := range findAddrs(srv.Addresses[\"public\"]) { addrs = append(addrs, api.NodeAddress{ Type:    api.NodeExternalIP, Address: addr, }) } // AccessIPs are usually duplicates of \"public\" addresses. api.AddToNodeAddresses(&addrs, api.NodeAddress{ Type:    api.NodeExternalIP, Address: srv.AccessIPv6, }, api.NodeAddress{ Type:    api.NodeExternalIP, Address: srv.AccessIPv4, }, ) </del> glog.V(4).Infof(\"NodeAddresses(%v) => %v\", name, addrs) return addrs, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-3129ecf685ad2fea6cb3ff97d12eed1692df1703f934c30f7ebae50375bb63d6", "text": "From we can find that, hardcode \"private\" and \"public\", seems only support that network with such name. , it fetch the first ip. usually, it can include both v6 and v4 ip. what's the meaning to just fetch the first one ? is it v4 or v6 ?\nping and\nYes. Zoom out a level or two in the code, and you'll see we're trying to either a) setup an openstack loadbalancer to point to the minion node (a single address) using , or b) report to kubernetes all the addresses we know about the node and whether they are \"internal\" or \"external\" in . All we have at the starting point is the server name (from kubernetes), and we need to make up the rest of this information somehow. (I agree (a) should reuse the NodeAddresses() function from (b), but the latter is a newer function and the code hasn't yet been refactored in that way. This doesn't really change the substance of this discussion.) Re (1): The logic as currently implemented is: Assume any network named \"private\" is \"internal\" Assume any network named \"public\" is \"external\" Assume the AccessIPs (IPv4 and IPv6) are \"external\" Any other network addresses are ignored. I implemented the first two (\"private\" and \"public\") following the Rackspace public cloud precedent, and on the basis that users in other OpenStack clouds can use these names if they want to encourage an address other than the Access addresses. For the (a) use case, we just take the first address we find in order of the above; for (b) we report that full list. I preferred \"private\" to \"public\" since (again, at least on Rackspace public cloud), the traffic on \"private\" network is sometimes cheaper/free. I agree this isn't great, and please suggest something better if you have a use case in mind. Perhaps we should pull a list of network names that should be considered \"internal\" and \"external\" from the provider config? Perhaps I could assume that provider networks are public and non-provider networks are internal? I don't want to add too much configuration here if there's a good algorithm that will Just Work.", "commid": "kubernetes_issue_18409", "tokennum": 498}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c05c2cc70c2ef67ecd42837076a58c41d08e71b002757478fd6a9f5509ecae0d", "query": "func (i *Instances) NodeAddresses(name string) ([]api.NodeAddress, error) { glog.V(4).Infof(\"NodeAddresses(%v) called\", name) <del> srv, err := getServerByName(i.compute, name) </del> <ins> addrs, err := getAddressesByName(i.compute, name) </ins> if err != nil { return nil, err } <del> addrs := []api.NodeAddress{} for _, addr := range findAddrs(srv.Addresses[\"private\"]) { addrs = append(addrs, api.NodeAddress{ Type:    api.NodeInternalIP, Address: addr, }) } for _, addr := range findAddrs(srv.Addresses[\"public\"]) { addrs = append(addrs, api.NodeAddress{ Type:    api.NodeExternalIP, Address: addr, }) } // AccessIPs are usually duplicates of \"public\" addresses. api.AddToNodeAddresses(&addrs, api.NodeAddress{ Type:    api.NodeExternalIP, Address: srv.AccessIPv6, }, api.NodeAddress{ Type:    api.NodeExternalIP, Address: srv.AccessIPv4, }, ) </del> glog.V(4).Infof(\"NodeAddresses(%v) => %v\", name, addrs) return addrs, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-73739ae9bad159746241b14eae0e38aaa61fc839e6a2ae622df67e262b940fc6", "text": "I think in practice it's probably ok to continue to prefer \"internal\" to \"external\" for loadbalancer setup, but I can contrive hypothetical cases that need more flexibility here too. Again, if you have a concrete need for such a thing, please file a bug so we have some idea of the flexibility required. Complicating all this is that Kubernetes never actually defined what an \"internal\" address was. just says \"Generally the IP address of the node that is routable only within the cluster\" which isn't a sufficiently strict definition. Looking at where Kubernetes actually uses it: just uses the first address reported (preferring InternalIPs to ExternalIPs) and the Kubernetes master configures an \"SSH Tunnel Check\" which just uses the first ExternalIP ... which kind of makes it pointless to ever even bother reporting anything beyond the first address. In both cases, it's assumed that this address is reachable by the Kubernetes master nodes, which makes the Internal vs External distinction a bit pointless. Re (2): is meant to return more than one IP, and the loadbalancer setup can only use a single IP for each node (or would unnecessarily track/healthceck multiple paths to the same backend for multiple addresses). If you're seeing single addresses returned by then you should file a bug. All the above treats IPv4 and IPv6 as equally important, if the OpenStack cloud has both, and the \"first\" address used for the loadbalancer will be an arbitrary choice between the two protocols (not quite true: will use AccessIPv4 before AccessIPv6). I think that's how it should be (the rest of the code should be protocol agnostic), but I wouldn't be surprised if there's some part of Kubernetes that doesn't support IPv6 properly. There certainly used to be lots of places that assumed IPv4 in Kubernetes, and GCE doesn't support IPv6 iirc so it gets less testing - if you've found something that breaks with IPv6, please file bugs. Now this bug: what would you like done here? Would you like the current situation to be documented further? Is the \"private\"/\"public\" naming thing too restrictive for your usecase? Something else?", "commid": "kubernetes_issue_18409", "tokennum": 505}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c05c2cc70c2ef67ecd42837076a58c41d08e71b002757478fd6a9f5509ecae0d", "query": "func (i *Instances) NodeAddresses(name string) ([]api.NodeAddress, error) { glog.V(4).Infof(\"NodeAddresses(%v) called\", name) <del> srv, err := getServerByName(i.compute, name) </del> <ins> addrs, err := getAddressesByName(i.compute, name) </ins> if err != nil { return nil, err } <del> addrs := []api.NodeAddress{} for _, addr := range findAddrs(srv.Addresses[\"private\"]) { addrs = append(addrs, api.NodeAddress{ Type:    api.NodeInternalIP, Address: addr, }) } for _, addr := range findAddrs(srv.Addresses[\"public\"]) { addrs = append(addrs, api.NodeAddress{ Type:    api.NodeExternalIP, Address: addr, }) } // AccessIPs are usually duplicates of \"public\" addresses. api.AddToNodeAddresses(&addrs, api.NodeAddress{ Type:    api.NodeExternalIP, Address: srv.AccessIPv6, }, api.NodeAddress{ Type:    api.NodeExternalIP, Address: srv.AccessIPv4, }, ) </del> glog.V(4).Infof(\"NodeAddresses(%v) => %v\", name, addrs) return addrs, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-fcd218ff1291684683bf7f5abec9b421b4d5bd08568265528c48e934f7742a2f", "text": "Hi, if we talked about openstack, I expect it not bind to rackspace, although, the kubernetes called RK SDK, But from my understanding, seems RK itself SDK not bind network to \"private\" and \"pubic\". User can define public network with their names, like site-network, for example. or \"testnet\", And for private, it should be seem. For nova list, the addresses, it can have \"OS-EXT-IPS:type\":\"fixed\" or \"OS-EXT-IPS:type\":\"floating\" for floating, I think what you means \"Public\", for fixed, I think its what you means \"Private\". In other words, we'd better to find related information from other fields in nova or neutron infromation. Instead of bind to \"private\" and \"public\" name.\nI this issue and wrote a patch that implements what suggests. I will send a PR soon\nGlad to see some improvements here. And wish to use it if implemented", "commid": "kubernetes_issue_18409", "tokennum": 223}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c0726c618b535f4afbd300883406c99fa4035bef41037c3ce284f72502ebe571", "query": "\"fmt\" \"net/http\" \"net/http/httptest\" <ins> \"net/url\" </ins> \"reflect\" \"testing\" <ins> \"k8s.io/apimachinery/pkg/util/sets\" </ins> ) func TestInstallHandler(t *testing.T) {", "positive_passages": [{"docid": "doc-en-kubernetes-01cc291fb1d6afeae9b284d60dd407b578a72d26e4c50043cbdf654c92184c45", "text": "What would you like to be : Add support to the kube-apiserver so that we can disable health-checks via query params. Why is this needed: Currently, the healthz endpoint is inflexible in that any and all health checks are currently executed when the endpoint is hit. Since the kube-apiserver only currently supports a liveness check, this means all persistent health check failures will eventually result in a kubelet driven restart. However, this may not be desirable behavior if you have additional monitoring services layered on top of your control plane. For instance, take the etcd failure from the perspective of the kube-apiserver. Currently, persistent failures during the etcd health check from the api-server healthz endpoint will cause the kube-apiserver to be restarted. This sometimes helps (in the case of a faulty etcd-client connection) but also can be detrimental (the kube-apiserver restarts until the etcd cluster is functioning, then the kube-apiserver bombards the etcd cluster with requests to update local caches, saturating the etcd cluster with requests, causing it to timeout on its own liveness probes and trigger a kubelet-driven restart). Let's say that we could now disable etcd from our liveness health check. Then if we had an external monitoring service, we could ask independently ask etcd if it was healthy and we could also ask the kube-apiserver if it thought etcd was unhealthy. Based on the combination of those answers, we could enable more intelligent responses to certain situation, like restarting the kube-apiserver when it thought etcd was unhealthy but etcd was actually reporting as healthy but not doing so when etcd was actually unhealthy. This feature is backwards-compatible and opt-in. There would be no impact to existing behavior unless these query params are actually used. /sig api-machinery /kind feature\n/cc\nSGTM\n/assign", "commid": "kubernetes_issue_70591", "tokennum": 432}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c09089e830f2f32bf327ee16aa05637d6aa7b38af703f48f085c99a2ca9bbaa9", "query": "# Get the compute zone zone=${ZONE:-\"$(gcloud info --format='value(config.properties.compute.zone.value)')\"} <ins> zone=${zone// /} </ins> if [[ ${zone} == \"\" ]]; then echo \"Could not find gcloud compute/zone when running: `gcloud info --format='value(config.properties.compute.zone.value)'`\" exit 1", "positive_passages": [{"docid": "doc-en-kubernetes-eb797bc1cabb351f81b78965d26c745c1a384907fc5b719bed4a9e14b0656c34", "text": "The compute project and zone in the prerequisites check are incorrectly calculated: !!! Error in hack/make-rules/test-e2e- Error in hack/make-rules/test-e2e- 'tee -i \"${artifacts}/build-\"' exited with status 1 0 Call stack: 1: hack/make-rules/test-e2e- main(...) Exiting with status 1 blocked by the following errors in each case: 1- Could not find gcloud compute/zone when running: .... 2- Could not find gcloud project when running: ..... 1- gcloud config unset compute/zone 2- gcloud config unset project 3- make test-e2e-node REMOTE=true LIST_IMAGES=true gcloud --version Google Cloud SDK 453.0.0 alpha 2023.10.27 beta 2023.10.27 bq 2.0.98 core 2023.10.27 gcloud-crc32c 1.0.0 <details</details<details</details<details</details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig node /assign", "commid": "kubernetes_issue_127362", "tokennum": 358}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c0b0d4d975911efa63929fe4c7683a8f0c03ef042aed94893f6ed409eb5557bc", "query": "Searches: []string{testHostDomain}, }, nil } <del> // getResolvConf returns the hostResolvConf string, which will be used to get the Host's DNS configuration. func getResolvConf(t *testing.T) (string, func()) { return hostResolvConf, func() {} } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-5e93ba1a338583c6193506912a68a67fcc908451a37c483694071bc120df2bcb", "text": "When a --resolv-conf (DNS resolver config) is passed to kubelet on a Windows node, the config content is used as part of sandbox initialization (through getHostDNSConfig()). Now with the recent changes (), it seems now to fail with an error like: E0315 10:22:16. 4764 ] \"Error syncing pod, skipping\" err=\"failed to \"CreatePodSandbox\" for \"img-pull-(-b40a-459d-9033-)\" with CreatePodSandboxError: \"Failed to generate sandbox config for pod \"img-pull-(-b40a-459d-9033-)\": Unexpected resolver config value: \"C:etckubernetescni\". Expected \"\" or \"Host\".\"\" pod=\"img-puller-3842/img-pull-\" podUID=-b40a-459d-9033- This is showing on all the runs of GCE testgrid (latest): Reading/using the passed resolv config on Windows Run a Windows pool with DNS resolv config being set as part of kubelet params. No response_ 27 alpha.3 1.27 beta.0 master <detailsGCE </details<details</details<details</details<details</details<details</details\n/triage accepted /milestone v1.27 /sig node /sig network\n/sig windows /cc\n/priority criticial-urgent as this is likely a release blocking\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority criticial-urgent 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\n/priority critical-urgent\nHmm, so you're setting the [1]. This PR introduced the capability to read the DNS config options from the Windows host registries while removing the capability to read from a file, introducing a regression. I've sent a PR addressing this issue: [1]\nIs the file you are pointing to a UNIX-style or something else?\nWas the file changing the behavior of the node?", "commid": "kubernetes_issue_116782", "tokennum": 565}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c0b0d4d975911efa63929fe4c7683a8f0c03ef042aed94893f6ed409eb5557bc", "query": "Searches: []string{testHostDomain}, }, nil } <del> // getResolvConf returns the hostResolvConf string, which will be used to get the Host's DNS configuration. func getResolvConf(t *testing.T) (string, func()) { return hostResolvConf, func() {} } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-a55794e1d2c420cf7484c297920657922704eb45d045ae8237364febdd60d634", "text": "Yeah, what used on GCE/GKE, seems to be a Linux-like conf, eg: nameserver 10.128.0.1 search c.<project_name.internal google.internal ` We haven't tried to remove from kubelet to see the behavior.\nThis Issue/PR has been marked as release blocker. Please have the fix merged by eod today otherwise the feature has to be reverted. For the Issue/PR owner: please have a revert/feature disable PR open today in case the fix failed to get in. Thank you! See the -- Kubernetes 1.27 release manager\nI opened up a revert PR in case this PR does not merge by code freeze.\nThanks for the resolution! both 2019 and 2022 grids seems to be back to green now!\nThanks for confirming! I opened to ensure gets updated too", "commid": "kubernetes_issue_116782", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c116c8d305937ccd42ccab4c68f9d21f584b5a8ae2e842308ac72638b49b66ff", "query": "} if h.nodeCacheCapable && result.NodeNames != nil { <del> nodeResult = make([]*v1.Node, 0, len(*result.NodeNames)) for i := range *result.NodeNames { nodeResult = append(nodeResult, nodeNameToInfo[(*result.NodeNames)[i]].Node()) </del> <ins> nodeResult = make([]*v1.Node, len(*result.NodeNames)) for i, nodeName := range *result.NodeNames { if node, ok := nodeNameToInfo[nodeName]; ok { nodeResult[i] = node.Node() } else { return nil, nil, fmt.Errorf( \"extender %q claims a filtered node %q which is not found in nodeNameToInfo map\", h.extenderURL, nodeName) } </ins> } } else if result.Nodes != nil { <del> nodeResult = make([]*v1.Node, 0, len(result.Nodes.Items)) </del> <ins> nodeResult = make([]*v1.Node, len(result.Nodes.Items)) </ins> for i := range result.Nodes.Items { <del> nodeResult = append(nodeResult, &result.Nodes.Items[i]) </del> <ins> nodeResult[i] = &result.Nodes.Items[i] </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-f39360e36dc13c7f3c135efe81c665373563851402d40604cca632c72aed6a7c", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Default scheduler crash if scheduler extender filter returns a not found node What you expected to happen: Default scheduler just should consider the not found node as not an candidate, instead of crash itself (panic). How to reproduce it (as minimally and precisely as possible): cluster only have 1 node: 0.0.0.1 scheduler extender (with nodeCacheCapable enabled) filter accidentally returns a candidate node: 0.0.0.2 scheduler recieved the candidate nodes: 0.0.0.2 from scheduler extender, but got below error: The is SuggestedHost: filteredNodes[0].Name: Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig scheduling", "commid": "kubernetes_issue_79640", "tokennum": 261}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c1205207799d17bc661e971e60f98018e7555d69b0104f03d2dc2543b614db08", "query": "return nil } <del> policyGroupVersion, err := CheckEvictionSupport(d.Client) if err != nil { return err } </del> // TODO(justinsb): unnecessary? getPodFn := func(namespace, name string) (*corev1.Pod, error) { return d.Client.CoreV1().Pods(namespace).Get(name, metav1.GetOptions{}) } <del> if len(policyGroupVersion) > 0 { return d.evictPods(pods, policyGroupVersion, getPodFn) </del> <ins> if !d.DisableEviction { policyGroupVersion, err := CheckEvictionSupport(d.Client) if err != nil { return err } if len(policyGroupVersion) > 0 { return d.evictPods(pods, policyGroupVersion, getPodFn) } </ins> } return d.deletePods(pods, getPodFn)", "positive_passages": [{"docid": "doc-en-kubernetes-1de7ff63e7ce8b64bf52f2105a2efc7375b6d0f9c29fe56834b2956453e0280d", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Allow to have an additional flag (e.g. or ) to allow a to drain pods off a node, even if they violate PodDisruptionBudgets Why is this needed: There are times where you want to drain pods off a node even if violating a PDB. For example, if you are running a one-worker node kubernetes cluster (not minikube), and you want to upgrade it. Or, like me, you are running a test cluster and want to scale down to zero nodes when you're not going to be using the cluster for a while in order to save costs. If that worker node has a deployment with a PDB, then will get stuck as it cannot get rid of the pod while respecting the PDB, which is expected; but in this case, it is a hindrance. Adding the switch will allow users to explicitly acknowledge that they want to ignore the PDBs (and accept the corresponding downtime for an application/service)\n/sig node\n+1\n+1 Our company offers Kubernetes as PaaS. We manage Kubernetes, including IaaS OS updates and if a customer does not specify the PDB correctly, we are not able to drain the node for the OS updates. A flag would be werry helpfull for our use case.\n+1\n/active\nI have created to address this. This is a pretty simple implementation, but I think it achieves the desired results. A suitable workflow would be: 1) Configure you component to use drain as normal 2) After some timeout, run drain with --disable-eviction option.\nI'll wait until the PR is merged and released before testing, but if I understand right, it would require me do this, right? If so, I think it would be better if we did it a different way and have one call, something like this: Where implies that if the drain is still running after this time, switch to the mode without having to call kubectl again\nI think that would require a sizeable refactor or add a great deal of complexity to the code, the same could be achieved with In practical terms, I'm focused on automatic node remediation via destroying the node and getting a new one. The timeout would be very large, the drain library is blocking, so I want it to fail quickly and requeue.", "commid": "kubernetes_issue_83307", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c1205207799d17bc661e971e60f98018e7555d69b0104f03d2dc2543b614db08", "query": "return nil } <del> policyGroupVersion, err := CheckEvictionSupport(d.Client) if err != nil { return err } </del> // TODO(justinsb): unnecessary? getPodFn := func(namespace, name string) (*corev1.Pod, error) { return d.Client.CoreV1().Pods(namespace).Get(name, metav1.GetOptions{}) } <del> if len(policyGroupVersion) > 0 { return d.evictPods(pods, policyGroupVersion, getPodFn) </del> <ins> if !d.DisableEviction { policyGroupVersion, err := CheckEvictionSupport(d.Client) if err != nil { return err } if len(policyGroupVersion) > 0 { return d.evictPods(pods, policyGroupVersion, getPodFn) } </ins> } return d.deletePods(pods, getPodFn)", "positive_passages": [{"docid": "doc-en-kubernetes-b7bae32dd27973078cd1b23d1dbdce25c736eb34a86ee68bc51d78045bb08cfb", "text": "I'm going to be performing the calculation of when it's appropriate to evict/delete outside of the drain library, and I suspect most will be as well, so there's not really a great incentive to do it in the drain library itself IMO.\nThat's all good, I have no issue using the flag as long as does error out and return a non-zero code as expected (there's been a few times where it seems to error out, but still return 0)", "commid": "kubernetes_issue_83307", "tokennum": 105}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c13232b721d5a00d4842dba6f03d3befbe6640a1731399210fa6e2e2b33f22f1", "query": "// shouldRetryHTTPRequest determines if the request is retriable. func shouldRetryHTTPRequest(resp *http.Response, err error) bool { if resp != nil { <del> // HTTP 412 (StatusPreconditionFailed) means etag mismatch, hence we shouldn't retry. if resp.StatusCode == http.StatusPreconditionFailed { </del> <ins> // HTTP 412 (StatusPreconditionFailed) means etag mismatch // HTTP 400 (BadRequest) means the request cannot be accepted, hence we shouldn't retry. if resp.StatusCode == http.StatusPreconditionFailed || resp.StatusCode == http.StatusBadRequest { </ins> return false }", "positive_passages": [{"docid": "doc-en-kubernetes-e65d433be70b14f59611269e2f1c0fa746f312a0f5c96a0c29a874f17f7c06ea", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: If you create a service that reference a Basic IP in a standard load balancer cluster, the service will stuck at \"Pending\" state for days without detailed error from Azure response. When you describe the service, it only has following: What you expected to happen: In this case Azure responded 400 with detailed error message that the referenced IP is a basic IP and cannot be used on standard LB. I would expect the detailed error message show up as events for easier diagnostic. How to reproduce it (as minimally and precisely as possible): Create a service that reference a Basic IP in a standard load balancer cluster Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/assign /area provider/azure /sig cloud-provider\n/area cloudprovider", "commid": "kubernetes_issue_86686", "tokennum": 259}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c15c75dd8f36dbd2cb26bd6c94ca63fdfe045c75918bb14e3cb55abb7c9453b2", "query": "return expected.ret } <del> func (testcase *testcase) DiskIsAttached(diskName string, nodeName types.NodeName) (bool, error) { </del> <ins> func (testcase *testcase) DiskIsAttached(diskName string, nodeName types.NodeName) (bool, string, error) { </ins> expected := &testcase.diskIsAttached if expected.diskName == \"\" && expected.nodeName == \"\" { // testcase.diskIsAttached looks uninitialized, test did not expect to // call DiskIsAttached testcase.t.Errorf(\"Unexpected DiskIsAttached call!\") <del> return false, errors.New(\"Unexpected DiskIsAttached call!\") </del> <ins> return false, diskName, errors.New(\"Unexpected DiskIsAttached call!\") </ins> } if expected.diskName != diskName { testcase.t.Errorf(\"Unexpected DiskIsAttached call: expected diskName %s, got %s\", expected.diskName, diskName) <del> return false, errors.New(\"Unexpected DiskIsAttached call: wrong diskName\") </del> <ins> return false, diskName, errors.New(\"Unexpected DiskIsAttached call: wrong diskName\") </ins> } if expected.nodeName != nodeName { testcase.t.Errorf(\"Unexpected DiskIsAttached call: expected nodeName %s, got %s\", expected.nodeName, nodeName) <del> return false, errors.New(\"Unexpected DiskIsAttached call: wrong nodeName\") </del> <ins> return false, diskName, errors.New(\"Unexpected DiskIsAttached call: wrong nodeName\") </ins> } klog.V(4).Infof(\"DiskIsAttached call: %s, %s, returning %v, %v\", diskName, nodeName, expected.isAttached, expected.ret) <del> return expected.isAttached, expected.ret </del> <ins> return expected.isAttached, diskName, expected.ret </ins> } func (testcase *testcase) DisksAreAttached(nodeVolumes map[types.NodeName][]string) (map[types.NodeName]map[string]bool, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-e1df151812a738ca8d7e9f97519d671c643638f3ca9d9400cc430f5f7a7d204c", "text": "When user creates a static PV using folder name in path: on vSAN backed datastore then detach disk does not work because check fails - The code expects folder name to be UUID but it does not and hence it determines disk is not attached to the node and hence no detach is ever performed. /sig storage cc", "commid": "kubernetes_issue_95121", "tokennum": 68}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c16e8e475e6ed7fd6e9c52903fbb6a7f7f29d813f98884d8bbb0ff604883a92f", "query": "package dns <del> import ( \"fmt\" \"os\" runtimeapi \"k8s.io/cri-api/pkg/apis/runtime/v1\" \"k8s.io/klog/v2\" ) func getHostDNSConfig(resolverConfig string) (*runtimeapi.DNSConfig, error) { var hostDNS, hostSearch, hostOptions []string // Get host DNS settings if resolverConfig != \"\" { f, err := os.Open(resolverConfig) if err != nil { klog.ErrorS(err, \"Could not open resolv conf file.\") return nil, err } defer f.Close() hostDNS, hostSearch, hostOptions, err = parseResolvConf(f) if err != nil { err := fmt.Errorf(\"Encountered error while parsing resolv conf file. Error: %w\", err) klog.ErrorS(err, \"Could not parse resolv conf file.\") return nil, err } } return &runtimeapi.DNSConfig{ Servers:  hostDNS, Searches: hostSearch, Options:  hostOptions, }, nil } </del> <ins> // Read the DNS configuration from a resolv.conf file. var getHostDNSConfig = getDNSConfig </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-5e93ba1a338583c6193506912a68a67fcc908451a37c483694071bc120df2bcb", "text": "When a --resolv-conf (DNS resolver config) is passed to kubelet on a Windows node, the config content is used as part of sandbox initialization (through getHostDNSConfig()). Now with the recent changes (), it seems now to fail with an error like: E0315 10:22:16. 4764 ] \"Error syncing pod, skipping\" err=\"failed to \"CreatePodSandbox\" for \"img-pull-(-b40a-459d-9033-)\" with CreatePodSandboxError: \"Failed to generate sandbox config for pod \"img-pull-(-b40a-459d-9033-)\": Unexpected resolver config value: \"C:etckubernetescni\". Expected \"\" or \"Host\".\"\" pod=\"img-puller-3842/img-pull-\" podUID=-b40a-459d-9033- This is showing on all the runs of GCE testgrid (latest): Reading/using the passed resolv config on Windows Run a Windows pool with DNS resolv config being set as part of kubelet params. No response_ 27 alpha.3 1.27 beta.0 master <detailsGCE </details<details</details<details</details<details</details<details</details\n/triage accepted /milestone v1.27 /sig node /sig network\n/sig windows /cc\n/priority criticial-urgent as this is likely a release blocking\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority criticial-urgent 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\n/priority critical-urgent\nHmm, so you're setting the [1]. This PR introduced the capability to read the DNS config options from the Windows host registries while removing the capability to read from a file, introducing a regression. I've sent a PR addressing this issue: [1]\nIs the file you are pointing to a UNIX-style or something else?\nWas the file changing the behavior of the node?", "commid": "kubernetes_issue_116782", "tokennum": 565}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c16e8e475e6ed7fd6e9c52903fbb6a7f7f29d813f98884d8bbb0ff604883a92f", "query": "package dns <del> import ( \"fmt\" \"os\" runtimeapi \"k8s.io/cri-api/pkg/apis/runtime/v1\" \"k8s.io/klog/v2\" ) func getHostDNSConfig(resolverConfig string) (*runtimeapi.DNSConfig, error) { var hostDNS, hostSearch, hostOptions []string // Get host DNS settings if resolverConfig != \"\" { f, err := os.Open(resolverConfig) if err != nil { klog.ErrorS(err, \"Could not open resolv conf file.\") return nil, err } defer f.Close() hostDNS, hostSearch, hostOptions, err = parseResolvConf(f) if err != nil { err := fmt.Errorf(\"Encountered error while parsing resolv conf file. Error: %w\", err) klog.ErrorS(err, \"Could not parse resolv conf file.\") return nil, err } } return &runtimeapi.DNSConfig{ Servers:  hostDNS, Searches: hostSearch, Options:  hostOptions, }, nil } </del> <ins> // Read the DNS configuration from a resolv.conf file. var getHostDNSConfig = getDNSConfig </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-a55794e1d2c420cf7484c297920657922704eb45d045ae8237364febdd60d634", "text": "Yeah, what used on GCE/GKE, seems to be a Linux-like conf, eg: nameserver 10.128.0.1 search c.<project_name.internal google.internal ` We haven't tried to remove from kubelet to see the behavior.\nThis Issue/PR has been marked as release blocker. Please have the fix merged by eod today otherwise the feature has to be reverted. For the Issue/PR owner: please have a revert/feature disable PR open today in case the fix failed to get in. Thank you! See the -- Kubernetes 1.27 release manager\nI opened up a revert PR in case this PR does not merge by code freeze.\nThanks for the resolution! both 2019 and 2022 grids seems to be back to green now!\nThanks for confirming! I opened to ensure gets updated too", "commid": "kubernetes_issue_116782", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c180881393106c8818750519172046c1d42d6d80ef5ac3b434e11dc0e7378008", "query": "return nil } <del> // Ensures that the load balancer associated with the given service is deleted, // doing the deletion if necessary. Should always be retried upon failure. func (s *ServiceController) ensureLBDeleted(service *api.Service) error { // This is only needed because not all delete load balancer implementations // are currently idempotent to the LB not existing. if _, exists, err := s.balancer.GetTCPLoadBalancer(s.loadBalancerName(service), s.zone.Region); err != nil { return err } else if !exists { return nil } if err := s.balancer.DeleteTCPLoadBalancer(s.loadBalancerName(service), s.zone.Region); err != nil { return err } return nil } </del> // ListKeys implements the interface required by DeltaFIFO to list the keys we // already know about. func (s *serviceCache) ListKeys() []string {", "positive_passages": [{"docid": "doc-en-kubernetes-9fca6378f8b8df6d20b226b62d39deddc0dd6ba6166f0f70fb99239f64c63f5d", "text": "All of our external load balancer tests failed for the better part of a day due to the GCE project that our tests run in hitting its quota for number of target pools. While the target pools have been deleted, the fact that we hit our quota indicates that there must be a leak somewhere, and we need to plug it.\nFor reference, the previous issue was\nCould the leakage be related to ? The quota exhaustion occurred about 22 hrs after that.\nI'd guess that this is due to GetTCPLoadBalancer returning that the load balancer doesn't exist if the forwarding rule is gone, ignoring the target pool, while the service controller considers its deleting done if the cloud provider says that the load balancer doesn't exist. I that logic to the cloud provider because the other implementations of DeleteTCPLoadBalancer weren't/won't be idempotent in the sense of returning ok if the LB doesn't exist. To fix it, we'll either need to make sure all Delete implementations are idempotent and remove the Get call in the controller, or add a method along the lines of IsTCPLoadBalancerDeleted to ask the cloud provider whether all pieces of it have been completely cleaned up. We can't make GetTCPLoadBalancer check that because it's relied on to tell us whether or not the balancer is fully created.\nCopying over my commentary from on why the GKE e2e tests are leaking so many forwarding rules and target pools vs the GCE tests:\nIs there a way for the services test to wait for the service controller to clean up the external resources before finishing (without just doing a sleep)?\nNot without polling GCE directly for whether the resources still exist, although that may be worth it as a workaround. What would be perfect is that clean-up-all-cloud-provider-resources API method that we talked about a couple months ago.\nCan we not perhaps use GCE namespaces or projects as a cheap way of getting this here?\nI don't believe so. We can't use projects due to the fact that projects can't be programatically created (they're intended to be long-lived). I'm not aware of anything along the lines of a GCE namespace other than networks, which won't work because target pools and forwarding rules unfortunately don't seem to be scoped to networks.", "commid": "kubernetes_issue_7753", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c180881393106c8818750519172046c1d42d6d80ef5ac3b434e11dc0e7378008", "query": "return nil } <del> // Ensures that the load balancer associated with the given service is deleted, // doing the deletion if necessary. Should always be retried upon failure. func (s *ServiceController) ensureLBDeleted(service *api.Service) error { // This is only needed because not all delete load balancer implementations // are currently idempotent to the LB not existing. if _, exists, err := s.balancer.GetTCPLoadBalancer(s.loadBalancerName(service), s.zone.Region); err != nil { return err } else if !exists { return nil } if err := s.balancer.DeleteTCPLoadBalancer(s.loadBalancerName(service), s.zone.Region); err != nil { return err } return nil } </del> // ListKeys implements the interface required by DeltaFIFO to list the keys we // already know about. func (s *serviceCache) ListKeys() []string {", "positive_passages": [{"docid": "doc-en-kubernetes-d79b213781c20847fbb47c058c0afaba60ed2f1d9f5b51e77a0a4cda944c52e0", "text": "The target pool leak in the code might be fixed, but the forwarding rule + target pool leak from deleting GKE clusters too quickly is certainly still happening. Reopening for the sake of that half of the issue.\nCan we just add a short sleep to jenkins after the last test has run before it deletes anything?\nYes, you could add a sleep to Ginkgo's AfterEachSuite(): But I'd be concerned about what the upper bound on the sleep period is. Can we get the tests and code in sync with a 1 minute latency here? (e.g. if the controller garbage collects every 60 seconds, then the test only needs to sleep for 60 sec?) And add a BEEG comment to the test's sleep config noting that increasing the sleep time will not improve things, otherwise I'm pretty sure that someone noting flakes in this test in future will think \"maybe I should just increase the sleep period a little bit.\"\nActually, thinking about this a little more, it would be better to put the \"sleep\" logic in the k8s master teardown procedure (i.e. not in the e2e tests or in Jenkins), because otherwise users are going to run into the same resource leakage problems as we are. So master deletion blocks on cleanup of backend cloud resources.\nThere's no way to block master deletion from the master itself. The test framework (or user) just pulls the rug out from underneath the master. See\nRobby's right -- is the real solution to this, but until we have that the best we can do is to have the wait happen elsewhere. The options seem to be: GKE itself Ginkgo's post-testing logic Jenkins' teardown logic I don't like putting it in GKE, because arbitrarily slowing down our API makes for a poor experience for the majority of people that don't still have resources being deleted. I'm not eager to put it in Gingko either, since won't that sleep also take effect whenever anyone runs an e2e test locally against a dev cluster? Putting it in the Jenkins logic makes the most sense to me. I'll send a PR and cc you.\nWe may also want to change the kube-down logic to bring down the master and then nodes in parallel to both speed it up and more closely resemble GKE's teardown logic.\nI've deleted the old forwarding rules and target pools from the project.", "commid": "kubernetes_issue_7753", "tokennum": 530}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c180881393106c8818750519172046c1d42d6d80ef5ac3b434e11dc0e7378008", "query": "return nil } <del> // Ensures that the load balancer associated with the given service is deleted, // doing the deletion if necessary. Should always be retried upon failure. func (s *ServiceController) ensureLBDeleted(service *api.Service) error { // This is only needed because not all delete load balancer implementations // are currently idempotent to the LB not existing. if _, exists, err := s.balancer.GetTCPLoadBalancer(s.loadBalancerName(service), s.zone.Region); err != nil { return err } else if !exists { return nil } if err := s.balancer.DeleteTCPLoadBalancer(s.loadBalancerName(service), s.zone.Region); err != nil { return err } return nil } </del> // ListKeys implements the interface required by DeltaFIFO to list the keys we // already know about. func (s *serviceCache) ListKeys() []string {", "positive_passages": [{"docid": "doc-en-kubernetes-6b81898435dc239c0c98669b4836ce5b1423be788127f142aa9eb15c198137cf", "text": "I'll periodically check to see whether anything is leaked after this point. I apologize if the deletions affected any running tests - everything looked to only be from GKE and parallel e2e runs.", "commid": "kubernetes_issue_7753", "tokennum": 42}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c1b7ebd49f91823a41fecc362bf2a3545a39e0104929a3c133b4d587e781137c", "query": "start_kube_controller_manager start_kube_scheduler start_kube_addons <ins> start_cluster_autoscaler </ins> } 2>&1 | logger --priority daemon.info -t ${UPSTART_JOB} end script", "positive_passages": [{"docid": "doc-en-kubernetes-cafbbd3cd664270b9fbd0ce7e8faa35ad0e8800a7c5d7cdeb5164eec0f1b24f1", "text": "For some reason they stopped working and we even don't create manifest file for cluster autoscaler. I used the following command to start the cluster:\nIt's possible it's related to", "commid": "kubernetes_issue_26346", "tokennum": 40}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c1c37109b81771a5e484fd7b96e869d332dedd430cb41ea000a4d518cc8ad2a3", "query": "// to the node. This list can be used to determine volumes that are either in-use // or have a mount/unmount operation pending. GetAttachedVolumes() []AttachedVolume <ins> // SyncReconstructedVolume check the volume.outerVolumeSpecName in asw and // the one populated from dsw , if they do not match, update this field from the value from dsw. SyncReconstructedVolume(volumeName v1.UniqueVolumeName, podName volumetypes.UniquePodName, outerVolumeSpecName string) </ins> } // MountedVolume represents a volume that has successfully been mounted to a pod.", "positive_passages": [{"docid": "doc-en-kubernetes-95820dc44dfb57216fa4466fe0b08e35d101b3576d175fcc0793312a1c18dfad", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --We have even encountered such case that pod continuously reports \u201cUnable to attach or mount volumes for pod;...\u201d when kubelet restarted. The reasons are listed in details as below: , as result of apiserver instantaneous unstablility, dswp get pvc\u2018s pv spec failed, then the pvc volume does not be to dsw. , syncStates() lists all the volume directories locally, and recontructs the volume from local volume, if the volume isn't in dsw, it will put the recontructed volume to asw, but now the volume.OuterVolumeSpecName isn't correct. chance, at this time, In , the fail to pvc volume is to dsw again normally in reconcile() -mountAttachVolumes(), it compares dsw and asw by volume's innerVolumename, it's all the same. but it could not sense the OuterVolumeSpecName dismatch. so it will not re-mount again to update asw cache , it checks pod's volume attach or mount success by comparing volume.OuterVolumeSpecName and , but this pv'c OuterVolumeSpecName isn't correct in asw. so pod continuously reports \u201cUnable to attach or mount volumes for pod;...\u201d reconcile() could sense the reconstruct volume's dismatch to the dsw, then re-mount again to make volume cache consistency Kubernetes version (use ): 1.19.4 Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig node\n/triage accepted\n/assign\nCC\nI think this is a point that can be optimized. /cc\nI will give a fix for this\nThanks for reporting the issue, this innerSpecName and outerSpecName are confusing and cause issues. Please ping me for review when you have a fix. Thanks!\nPlease don't triage your own issues immediately, give someone else a chance to review them :( /sig storage\nokay, I know", "commid": "kubernetes_issue_103143", "tokennum": 528}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c21499970c2e87db850d248524f9b7b2e291ed10ff86e96f6d39dda4aa340ce4", "query": "} }) <ins> It(\"should provision storage with non-default reclaim policy Retain\", func() { framework.SkipUnlessProviderIs(\"gce\", \"gke\") test := testsuites.StorageClassTest{ Name:           \"HDD PD on GCE/GKE\", CloudProviders: []string{\"gce\", \"gke\"}, Provisioner:    \"kubernetes.io/gce-pd\", Parameters: map[string]string{ \"type\": \"pd-standard\", }, ClaimSize:    \"1Gi\", ExpectedSize: \"1Gi\", PvCheck: func(volume *v1.PersistentVolume) error { return checkGCEPD(volume, \"pd-standard\") }, } class := newStorageClass(test, ns, \"reclaimpolicy\") retain := v1.PersistentVolumeReclaimRetain class.ReclaimPolicy = &retain claim := newClaim(test, ns, \"reclaimpolicy\") claim.Spec.StorageClassName = &class.Name pv := testsuites.TestDynamicProvisioning(test, c, claim, class) By(fmt.Sprintf(\"waiting for the provisioned PV %q to enter phase %s\", pv.Name, v1.VolumeReleased)) framework.ExpectNoError(framework.WaitForPersistentVolumePhase(v1.VolumeReleased, c, pv.Name, 1*time.Second, 30*time.Second)) By(fmt.Sprintf(\"deleting the storage asset backing the PV %q\", pv.Name)) framework.ExpectNoError(framework.DeletePDWithRetry(pv.Spec.GCEPersistentDisk.PDName)) By(fmt.Sprintf(\"deleting the PV %q\", pv.Name)) framework.ExpectNoError(framework.DeletePersistentVolume(c, pv.Name), \"Failed to delete PV \", pv.Name) framework.ExpectNoError(framework.WaitForPersistentVolumeDeleted(c, pv.Name, 1*time.Second, 30*time.Second)) }) </ins> It(\"should not provision a volume in an unmanaged GCE zone.\", func() { framework.SkipUnlessProviderIs(\"gce\", \"gke\") var suffix string = \"unmananged\"", "positive_passages": [{"docid": "doc-en-kubernetes-8769160e6f0dabeddd11cead4810305b5f582b45774110e5e46e9ec50492bd79", "text": "Testgrid: https://k8s- https://k8s- https://k8s- https://k8s- Sample failures: This started failing across multiple test jobs last night. The culprit appears to be PR over to you. /kind failing-test /priority critical-urgent /sig storage\n/milestone v1.13\n/assign\nGitHub didn't allow me to assign the following users: mkimuram. Note that only and repo collaborators can be assigned. 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\nI think should delete the PVC and wait for it to be deleted.\nThank you for your comment. I haven't yet catching up, but as for the PVC deletion code in , which is changed in the PR, PVC deletion is done inside for delete policy case or for retain policy case. Isn't it enough? In addition, could you let me know how I can check the matrix for the failure that we are focusing? I couldn't find the failure for provisioning tests themselves, there.\nIs my understanding right that the purpose of is to check whether resource is leaking by checking the diff of resource between the test? If so, is it correct that the sample output above means that one pd is leaking, not the leak of pv or pvc itself? I found that in the test for retain policy is removed in this PR when it is moved to , because it is gce specific logic and looks unnecessary. Do you think that it could be a cause of this issue? If so, should deleting the backend storage be generally required before removing the dynamic provisioned PV with retain policy?", "commid": "kubernetes_issue_70191", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c25610b7503458d6b99b3fe26dc1c64d544038ba8ce3768c0663c098c74b7bea", "query": "\"description\": \"EndpointPort is a tuple that describes a single port.\", \"properties\": { \"appProtocol\": { <del> \"description\": \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and http://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.\", </del> <ins> \"description\": \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.\", </ins> \"type\": \"string\" }, \"name\": {", "positive_passages": [{"docid": "doc-en-kubernetes-3e7e95e6f142ca39e6e3ca0b78c3932bd6cbdfdc898eed9d3ffda27d28f904c7", "text": "We should make the change in PR API reference links to should use HTTPS, not HTTP Visit h and look at the IANA hyperlinks Once this fix is made, a PR to is needed to update the docs (by autogenerating them). This typically would be deferred until the next Kubernetes release. v1.23 not applicable not applicable not applicable not applicable not applicable\n/sig docs\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI opened this issue so that someone else can open a new PR that is equivalent to .\n/retitle Update links to IANA for Service Name and Transport Protocol Port Number Registry\nI would like to work on this issue. May I assign it to myself?\nAnyone - including you - is welcome to work on this issue! So long as you've you can open a pull request to propose a fix.\nThanks\n/assign\nI have made the PR. I hope this works. If not then will be happy to do the necessary changes.\nHad to close the previous PR because of issues, here is the new one I made.", "commid": "kubernetes_issue_106980", "tokennum": 300}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c2623818a8c52843adaae0f533a35ac7dcf7fc8553058242a8d8473fe42d85a2", "query": "return i.doCmd(s, nil, ipvsCmdDelService) } <ins> // Flush deletes all existing services in the passed // handle. func (i *Handle) Flush() error { _, err := i.doCmdWithoutAttr(ipvsCmdFlush) return err } </ins> // NewDestination creates a new real server in the passed ipvs // service which should already be existing in the passed handle. func (i *Handle) NewDestination(s *Service, d *Destination) error {", "positive_passages": [{"docid": "doc-en-kubernetes-13eba344b12142e2782a67745f08ac2e814f1785c70b127779bdac58248d8b7b", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: Currently, we flush ipvs services by deleting them one by one. That's because there was no flush API in libnetwork. Now, libnetwork supports flush API, I think it's time to rsync. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration**: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig network\n/area kube-proxy\n/assign", "commid": "kubernetes_issue_52070", "tokennum": 279}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c291a2d41f9c74b4b110635dfb37a5b4c67585af2dfe6bbe39f5fa3e92b39985", "query": "<del> apiVersion: v1 kind: Service metadata: name: elasticsearch-discovery labels: component: elasticsearch role: master spec: selector: component: elasticsearch role: master ports: - name: transport port: 9300 protocol: TCP </del>", "positive_passages": [{"docid": "doc-en-kubernetes-5fef938b0452d0f6b58e576cd11f17813fb6d6b970f83a7868d905b7784a5e39", "text": "Presently, the elasticsearch example Kubernetes configurations target elasticsearch v1.7.1, which is quite old. As of this writing, the latest elasticsearch release is v5.6.2, with many deployment changes since then. Could the elasticsearch examples be updated to target the v5 series of elasticsearch? See for a more up to date reference configuration.\ncc\nhey it's been a long while since I last contributed to the docs. i can do it soon but i need pointers on how to properly do it.\nhey, so we need to update the stuff under examples/elasticsearch/ *&repos=kubernetes So basically update the images, yaml files etc and test that everything works (and submit a PR)\n/sig testing\nAh, so there's no documentation updates anymore. OK I'll take care of it, assign it to me.\nIssues 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\nGitHub didn't allow me to assign the following users: me. Note that only and repo collaborators can be assigned. <detailsIn response to : /assign me 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\n/assign pires\n/remove-lifecycle stale\nit seems that the example moved to I am now reading that repo guidelines and will update this there. I'll also open a PR that cleans this folder in the current repo and closes this issue.", "commid": "kubernetes_issue_53142", "tokennum": 387}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c2e5443cc153491b85828902364ffced6909f99376bd0f9fd8cdb8dfe13a1fed", "query": "}{ \"backoffLimit 0 should have 1 pod active\": { 1, 1, 0, <del> true, []int32{0}, </del> <ins> true, []int32{0}, v1.PodRunning, </ins> 1, 0, 0, nil, \"\", }, \"backoffLimit 1 with restartCount 0 should have 1 pod active\": { 1, 1, 1, <del> true, []int32{0}, </del> <ins> true, []int32{0}, v1.PodRunning, </ins> 1, 0, 0, nil, \"\", }, <del> \"backoffLimit 1 with restartCount 1 should have 0 pod active\": { </del> <ins> \"backoffLimit 1 with restartCount 1 and podRunning should have 0 pod active\": { </ins> 1, 1, 1, <del> true, []int32{1}, </del> <ins> true, []int32{1}, v1.PodRunning, </ins> 0, 0, 1, &jobConditionFailed, \"BackoffLimitExceeded\", }, <del> \"too many job failures - single pod\": { </del> <ins> \"backoffLimit 1 with restartCount 1 and podPending should have 0 pod active\": { 1, 1, 1, true, []int32{1}, v1.PodPending, 0, 0, 1, &jobConditionFailed, \"BackoffLimitExceeded\", }, \"too many job failures with podRunning - single pod\": { </ins> 1, 5, 2, <del> true, []int32{2}, </del> <ins> true, []int32{2}, v1.PodRunning, </ins> 0, 0, 1, &jobConditionFailed, \"BackoffLimitExceeded\", }, <del> \"too many job failures - multiple pods\": { </del> <ins> \"too many job failures with podPending - single pod\": { 1, 5, 2, true, []int32{2}, v1.PodPending, 0, 0, 1, &jobConditionFailed, \"BackoffLimitExceeded\", }, \"too many job failures with podRunning - multiple pods\": { 2, 5, 2, true, []int32{1, 1}, v1.PodRunning, 0, 0, 2, &jobConditionFailed, \"BackoffLimitExceeded\", }, \"too many job failures with podPending - multiple pods\": { </ins> 2, 5, 2, <del> true, []int32{1, 1}, </del> <ins> true, []int32{1, 1}, v1.PodPending, </ins> 0, 0, 2, &jobConditionFailed, \"BackoffLimitExceeded\", }, \"not enough failures\": { 2, 5, 3, <del> true, []int32{1, 1}, </del> <ins> true, []int32{1, 1}, v1.PodRunning, </ins> 2, 0, 0, nil, \"\", }, }", "positive_passages": [{"docid": "doc-en-kubernetes-57b8eab4723f670b6603d9bfb82377ab99cdb5a96c17a18501cc8d4284272435", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: I create a job with initcontainer with restartPolicy : when the initContainer exec failed and it will be restarted, the pod Phase will be pending all the time. but in JobController, the only care the running pod. So this pod will be always restarted. What you expected to happen: when restart count to backoffLimit, the job failed. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig apps\n/assign", "commid": "kubernetes_issue_77644", "tokennum": 220}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c30c65cd32a470f0d962328756672c8c816f8506ad13f51b30de3e97b16e38f8", "query": "import ( \"fmt\" <ins> \"os/exec\" </ins> \"reflect\" \"testing\" \"k8s.io/kubernetes/pkg/api\" \"k8s.io/kubernetes/pkg/api/resource\" <ins> \"k8s.io/kubernetes/pkg/util/codeinspector\" </ins> \"k8s.io/kubernetes/plugin/pkg/scheduler/algorithm\" \"k8s.io/kubernetes/plugin/pkg/scheduler/schedulercache\" )", "positive_passages": [{"docid": "doc-en-kubernetes-3229e3f28f67afa9ddea85d9d31a50803c261e0ae30f76f950060d1790215e64", "text": "I just noticed you forgot to register the image locality priority function in in I also missed it when I reviewed your PR. I have fixed this in . But it would be great if you could figure out a mechanism that would ensure that all predicate/priority functions that are tested (you can assume they will always live under ) are registered, and fail the test if not. That will allow us to prevent this mistake in the future.\nThanks! Will fix this soon!\nSeems need to wait for in before I send PR? Otherwise this test will always fail ...", "commid": "kubernetes_issue_21236", "tokennum": 114}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c344af00490ae519ccd492bdb21d93599190b242dd0cff0c34c4819eb2153983", "query": "\"fmt\" \"net\" \"path/filepath\" <ins> \"strings\" </ins> \"sync\" \"testing\" \"time\" authenticationv1 \"k8s.io/api/authentication/v1\" v1 \"k8s.io/api/core/v1\" <ins> storagev1 \"k8s.io/api/storage/v1\" </ins> metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" <ins> \"k8s.io/apimachinery/pkg/labels\" </ins> \"k8s.io/apimachinery/pkg/types\" <ins> \"k8s.io/apimachinery/pkg/util/sets\" </ins> \"k8s.io/apimachinery/pkg/util/wait\" \"k8s.io/client-go/informers\" clientset \"k8s.io/client-go/kubernetes\"", "positive_passages": [{"docid": "doc-en-kubernetes-43fa70370952068e2f27033c41492113945a1e0b0ce47a43a47f5065969f2aa7", "text": "After the cluster was updated to enable PD CSI Driver, there was a race condition where AD Controller (kube-controller-manager) started to BEFORE the PD CSI Driver was up, thus AD Controller gave us the error Then AD Controller triggered the disk detach because the disk/volume was not populated in the desired state of world. Unfortunately the disk was in use during this detach and got corrupted. Since cluster upgrades can cause the controller manager and CSI drivers to start at different times, the AD controller needs to be more conservative when detaching We have not been able to reproduce this, it came up from a customer. /sig storage /assign <detailsk8s 1.23, CSI migration enabled </details<detailsGKE </details<details</details<details</details<details</details<details</details\n/triage accepted\nI think there's potentially two changes we should do: 1) for the initial DSW population, we should skip the check that if the csi driver is not installed. 2) in general, we should not skip volumes during dsw initial population if an error is returned. If we had some temporary api server error then that would cause volumes to not get to dsw and similar behavior happen. cc\nfor a repro, maybe you can try something like: a cluster with csi migration enabled (control plane + nodes) a pod with intree-volume and get it running the csi driver node daemonset. verify the driver is removed from CSINode kube-controller-manager\ncc\n/cc was trying to repro this, but on GKE with the managed driver which made it complicated.\nYeah maybe gce kube-up would be easier for a repro\nIf CSINode says that it has migrated GCP PD volume plugin to CSI, then IMO A/D controller should always attach GCP PD volumes to it using CSI, regardless if the CSI driver is present or not. In-tree volume plugin in the kubelet is disabled and can't mount any in-tree volumes anyway. To flip the migration feature gate / upgrade / downgrade kubelet, the cluster admin must drain the node first to make sure everything is detached. A/D controller should not see change of CSINode migration annotations with any volume attached to it.\n/priority important-soon\nAnother option could be to process these volumes anyways but add them to DSOW with migration status as \"uncertain\", so as they can be re-processed later.", "commid": "kubernetes_issue_115297", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c344af00490ae519ccd492bdb21d93599190b242dd0cff0c34c4819eb2153983", "query": "\"fmt\" \"net\" \"path/filepath\" <ins> \"strings\" </ins> \"sync\" \"testing\" \"time\" authenticationv1 \"k8s.io/api/authentication/v1\" v1 \"k8s.io/api/core/v1\" <ins> storagev1 \"k8s.io/api/storage/v1\" </ins> metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" <ins> \"k8s.io/apimachinery/pkg/labels\" </ins> \"k8s.io/apimachinery/pkg/types\" <ins> \"k8s.io/apimachinery/pkg/util/sets\" </ins> \"k8s.io/apimachinery/pkg/util/wait\" \"k8s.io/client-go/informers\" clientset \"k8s.io/client-go/kubernetes\"", "positive_passages": [{"docid": "doc-en-kubernetes-8286ec57fa1e024ad026b2342f466cffd200140a0a95c9b64ae688331c52eb45", "text": "But surely it looks like might be easiest unless it has any downsides.\nThere wasn't a node update in this case---there was a control plane update which restarted the PD CSI driver, and it looks like the CSIDriver resource was updated or changed in some way which raced with the kube-controller-manager restart.\nIs there anyway we can know if the csi driver is up and running(like a health check ping) before populating DSW?\nWe use the CSINode registration to determine that. The discussion here I think is concluding that we should not use that as a criteria for adding the volume to DSW. We only need to check that CSI migration is enabled on the node.\n+1 we need to be very resilient against races, I think we have to assume a driver is in process of being installed at any point in the AD controller reconcilliation.\n/assign sunnylovestiramisu\nReproduced with the steps: In /var/log/kube-controller-\nTested with the and doing the reproduce steps above. The error of does not show up anymore. The error message still get logged in the kube-controller- for debugging purpose: Ran Ran On the GCP console, the disk is used by node: Ran I redeploy the pd-csi-driver and then make sure it is up and running. Ran", "commid": "kubernetes_issue_115297", "tokennum": 285}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c34f11093b7c998605521e1a8ed4ea9cd204a28c20a06edee5df5bdeb92d9293", "query": "// It must return (\"\", cloudprovider.InstanceNotFound) if the instance does // not exist or is no longer running. func (ss *scaleSet) GetInstanceIDByNodeName(name string) (string, error) { <del> _, _, vm, err := ss.getVmssVM(name) </del> <ins> managedByAS, err := ss.isNodeManagedByAvailabilitySet(name) </ins> if err != nil { <del> if err == ErrorNotVmssInstance { glog.V(4).Infof(\"GetInstanceIDByNodeName: node %q is managed by availability set\", name) // Retry with standard type because nodes are not managed by vmss. return ss.availabilitySet.GetInstanceIDByNodeName(name) } </del> <ins> glog.Errorf(\"Failed to check isNodeManagedByAvailabilitySet: %v\", err) return \"\", err } if managedByAS { // vm is managed by availability set. return ss.availabilitySet.GetInstanceIDByNodeName(name) } _, _, vm, err := ss.getVmssVM(name) if err != nil { </ins> return \"\", err }", "positive_passages": [{"docid": "doc-en-kubernetes-98264fae63e9d149f0171dd13218170b598f5e330429a04234e4c80f3d1b23d2", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: VMAS nodes are reporting error in vmss cluster (vmType set to vmss). What you expected to happen: Node should register correctly in the kubernetes cluster. How to reproduce it (as minimally and precisely as possible): Create a VMAS nodes inside vmss cluster. Anything else we need to know?: Environment: Kubernetes version (use ): master Cloud provider or hardware configuration: azure OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/sig azure", "commid": "kubernetes_issue_60185", "tokennum": 165}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c3be7299c05eef6b667287d1018676222ff29060d0795250627a26330de752bd", "query": "t.Errorf(\"Expect node port type service, got none\") } } <ins> func TestLoadBalanceSourceRanges(t *testing.T) { ipt := iptablestest.NewFake() ipvs := ipvstest.NewFake() ipset := ipsettest.NewFake(testIPSetVersion) fp := NewFakeProxier(ipt, ipvs, ipset, nil) svcIP := \"10.20.30.41\" svcPort := 80 svcLBIP := \"1.2.3.4\" svcLBSource := \"10.0.0.0/8\" svcPortName := proxy.ServicePortName{ NamespacedName: makeNSN(\"ns1\", \"svc1\"), Port:           \"p80\", } epIP := \"10.180.0.1\" makeServiceMap(fp, makeTestService(svcPortName.Namespace, svcPortName.Name, func(svc *api.Service) { svc.Spec.Type = \"LoadBalancer\" svc.Spec.ClusterIP = svcIP svc.Spec.Ports = []api.ServicePort{{ Name:     svcPortName.Port, Port:     int32(svcPort), Protocol: api.ProtocolTCP, }} svc.Status.LoadBalancer.Ingress = []api.LoadBalancerIngress{{ IP: svcLBIP, }} svc.Spec.LoadBalancerSourceRanges = []string{ svcLBSource, } }), ) makeEndpointsMap(fp, makeTestEndpoints(svcPortName.Namespace, svcPortName.Name, func(ept *api.Endpoints) { ept.Subsets = []api.EndpointSubset{{ Addresses: []api.EndpointAddress{{ IP:       epIP, NodeName: strPtr(testHostname), }}, Ports: []api.EndpointPort{{ Name: svcPortName.Port, Port: int32(svcPort), }}, }} }), ) fp.syncProxyRules() // Check ipvs service and destinations services, err := ipvs.GetVirtualServers() if err != nil { t.Errorf(\"Failed to get ipvs services, err: %v\", err) } found := false for _, svc := range services { fmt.Printf(\"address: %s:%d, %s\", svc.Address.String(), svc.Port, svc.Protocol) if svc.Address.Equal(net.ParseIP(svcLBIP)) && svc.Port == uint16(svcPort) && svc.Protocol == string(api.ProtocolTCP) { destinations, _ := ipvs.GetRealServers(svc) if len(destinations) != 1 { t.Errorf(\"Unexpected %d destinations, expect 0 destinations\", len(destinations)) } for _, ep := range destinations { if ep.Address.String() == epIP && ep.Port == uint16(svcPort) { found = true } } } } if !found { t.Errorf(\"Did not got expected loadbalance service\") } // Check ipset entry expectIPSet := map[string]*utilipset.Entry{ KubeLoadBalancerSet: { IP:       svcLBIP, Port:     svcPort, Protocol: strings.ToLower(string(api.ProtocolTCP)), SetType:  utilipset.HashIPPort, }, KubeLoadBalancerMasqSet: { IP:       svcLBIP, Port:     svcPort, Protocol: strings.ToLower(string(api.ProtocolTCP)), SetType:  utilipset.HashIPPort, }, KubeLoadBalancerSourceCIDRSet: { IP:       svcLBIP, Port:     svcPort, Protocol: strings.ToLower(string(api.ProtocolTCP)), Net:      svcLBSource, SetType:  utilipset.HashIPPortNet, }, } for set, entry := range expectIPSet { ents, err := ipset.ListEntries(set) if err != nil || len(ents) != 1 { t.Errorf(\"Check ipset entries failed for ipset: %q\", set) continue } if ents[0] != entry.String() { t.Errorf(\"Check ipset entries failed for ipset: %q\", set) } } // Check iptables chain and rules kubeSvcRules := ipt.GetRules(string(kubeServicesChain)) kubeFWRules := ipt.GetRules(string(KubeFireWallChain)) if !hasJump(kubeSvcRules, string(KubeMarkMasqChain), KubeLoadBalancerMasqSet) { t.Errorf(\"Didn't find jump from chain %v match set %v to MASQUERADE\", kubeServicesChain, KubeLoadBalancerMasqSet) } if !hasJump(kubeSvcRules, string(KubeFireWallChain), KubeLoadBalancerSet) { t.Errorf(\"Didn't find jump from chain %v match set %v to %v\", kubeServicesChain, KubeLoadBalancerSet, KubeFireWallChain) } if !hasJump(kubeFWRules, \"ACCEPT\", KubeLoadBalancerSourceCIDRSet) { t.Errorf(\"Didn't find jump from chain %v match set %v to ACCEPT\", kubeServicesChain, KubeLoadBalancerSourceCIDRSet) } } </ins> func TestOnlyLocalLoadBalancing(t *testing.T) { ipt := iptablestest.NewFake()", "positive_passages": [{"docid": "doc-en-kubernetes-4b95e73f98faca5940a16ee2fccddf37ae93437213e073578ff34d76b732271f", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Service loadbalancer source range don't work in ipvs proxy mode. Which result in gci-gce-ipvs CI failed. http://k8s- How to reproduce it (as minimally and precisely as possible): In gce environment. a service with backend. service type to service util service external IP is specified. the service from pod inside and pod out of the . Environment: Kubernetes version (use ): master Cloud provider or hardware configuration: gce OS (e.g. from /etc/os-release): ubuntu Kernel (e.g. ): Install tools: cluster/kube- Others:\n/kind bug /sig network /label ipvs\n/area ipvs\nThe test seems to be flaky now. Can you take a look please?\nI don't know why, but I think this flaky have the similiar reason with other normal service-test cases, like Those flaky are pretty annoying, problem is, I have run those cases in my own environment many times, never fail... : ( But still, I'll do my best to find the reason.", "commid": "kubernetes_issue_61090", "tokennum": 264}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c413563426f07ed4ff02087c4f962aaf75416bdb1e1788a61e6aba68cd6f2ac8", "query": "// Sleep 1s to verify no detach are triggered after second pod is added in the future. time.Sleep(1000 * time.Millisecond) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw, volumeAttachedCheckTimeout) </ins> // verifyVolumeNoStatusUpdateNeeded(t, logger, generatedVolumeName, nodeName1, asw) // Add a third pod which tries to attach the volume to a different node.", "positive_passages": [{"docid": "doc-en-kubernetes-2a1f139ca790a16bd0882043a2e2916760e4c33264d1a31f1254bc354f4822db", "text": "After KCM restart, any Pod that reuses a volume that failed to detach gets stuck ContainerCreating with message: User \"system:node:ip-10-0-243-\" cannot get resource \"volumeattachments\" in API group \"\" at the cluster scope: no relationship found between node 'ip-10-0-243-' and this object See steps to reproduce below, it's quite a complex condition. It happens when a pod is restarted, a CSI driver \"busy\" (i.e. times out) + KCM restarted at a wrong time. Pods start just fine. a Pod that uses an attachable CSI volume. the Pod. Make sure it unmounts successfully, but any fails with a transient error, such as timeout. The external attacher continues to detach the volume at this point. kube-controller-manager (KCM) and start a new one. Wait for any leader election etc - it's important for the new KCM to populate A/D controller with no pod using the detaching volume. Let the A/D controller to observe detach error. a new Pod on the same node that uses the same volume. the CSI driver to detach the volume (i.e. stop injecting any transient errors). At this point: The external attacher succeeds detaching the volume, VolumeAttachment is deleted. The volume is marked as attached in node status (!!!) despite no VolumeAttachment exists. A/D controller does not even try to create a new VolumeAttachment, the volume is marked as attached in its Actual State of World (ASW). Kubelet tries to mount the volume, but WaitForAttach fails with: , basically forever. I created . The script expects that the cluster is created by , because it restarts KCM in the middle. It uses my hacked hostpath CSI driver to inject detach errors. Sources are at / the last commit(s) there. There are two issues that together lead to this situation: fails, , i.e. puts it back to . With the volume in , kubelet may try to mount it, while the external attacher tries to detach it. It is not as bad as it sounds, because kubelet can't read VolumeAttachment with the deletion timestamp and it will not call / of un-attached volume.", "commid": "kubernetes_issue_120571", "tokennum": 509}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c413563426f07ed4ff02087c4f962aaf75416bdb1e1788a61e6aba68cd6f2ac8", "query": "// Sleep 1s to verify no detach are triggered after second pod is added in the future. time.Sleep(1000 * time.Millisecond) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <ins> verifyVolumeReportedAsAttachedToNode(t, logger, generatedVolumeName, nodeName1, true, asw, volumeAttachedCheckTimeout) </ins> // verifyVolumeNoStatusUpdateNeeded(t, logger, generatedVolumeName, nodeName1, asw) // Add a third pod which tries to attach the volume to a different node.", "positive_passages": [{"docid": "doc-en-kubernetes-86a0f830cda4a62b3e964f9aa561f07fe82e259bc1038677353226e3d67190fe", "text": "KCM starts, all VolumeAttachments that don't have a Pod (that's good), but also (that's probably bad). When the newly started KCM re-tries to detach the volume and gets an error again, it marks the volume as fully attached (same as the previous point) and adds it to . Now the volume is both mounted + attached in ASW and A/D controller actually stops here and waits forever for kubelet to unmount the volume. <detailsToday's k/k master, </details<detailsNone </details<detailsN/A, it's KCM issue. </details<details, but seen in a downstream Kubernetes distro too. </details<details</details<details</details\n/sig storage\n/assign\n/triage accepted\nI have the same problem: Seems restart of Kubelet solves this problem. Kubernetes v1.25.13", "commid": "kubernetes_issue_120571", "tokennum": 208}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c47338a0cb245d83d442f85bc265ba828aaf33a909e1f7a5bbe26d8f333fcea0", "query": "return nil } _, err = p.client.Namespaces().Create(namespace) <del> if err != nil { </del> <ins> if err != nil && !errors.IsAlreadyExists(err) { </ins> return err } return nil", "positive_passages": [{"docid": "doc-en-kubernetes-c343f6e7b091e9b4529e6227acb6329e7535006eb05bcc59008c8d5d37213826", "text": "While running one of my soak tests I noticed the error message: I don't see why I should get this error message. Why should it matter if the namespace already exists? It was created as part of the service creation call just beforehand. And the second attempt to create this pod in exactly the same namespace works. Is this a bug?\nRunning a second time did not produce this error.\nI agree it should not matter. The error is produced there, and I suspect there were multiple concurrent calls being made that try to create a resource in a namespace that had not yet existed. We need to update the code in question to swallow the error if the namespace already exists.\nFYI - longer term, I would like to eliminate the use of autoprovision of namespace and require you to first create a namespace manually. what is there now is more to preserve existing behavior prior to namespace as object was introduced.", "commid": "kubernetes_issue_5873", "tokennum": 190}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c4a285f08456603d4776f0fb54e41a42c114ff1372e6a564f1594975dfd4c60b", "query": "OOMScoreAdj:            config.OOMScoreAdj, ConfigSyncPeriod:       config.ConfigSyncPeriod.Duration, HealthzServer:          healthzServer, <ins> UseEndpointSlices:      utilfeature.DefaultFeatureGate.Enabled(features.EndpointSlice), </ins> }, nil }", "positive_passages": [{"docid": "doc-en-kubernetes-94306baf6d6408dd320a641269af3f429c4d2a949a311ade7ed7994b23100633", "text": "After this () has been merged and EnpointSlice feature is now enabled by default, we noticed Kube-proxy will not work on Windows. Only message I can see in the logs is: /sig windows\n/cc /cc /cc\nHow about separating the above check into two if statements so that the log can pinpoint which field is false ?\nIt seems long term, EndpointSlice support should be so that is kept in sync with other implementations.\ncc\nThanks for reporting this! Windows proxiers were still intended to be reading from Endpoints, but apparently that's not working as intended. EndpointSlices are moving back to disabled by default for 1.17, so that should fix the failing tests for now. I'll work on an actual fix for this as well, but it may not make it in until after KubeCon. /assign /sig network /priority important-soon\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/remove-triage unresolved\n/assign cc\nGitHub didn't allow me to assign the following users: jocelynberrendonner. 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 cc 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\n: Please let me know if you need any help on the fix! I'll be more than happy to review/help test the fix on Windows.", "commid": "kubernetes_issue_85352", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c4ee65ba71d8111c058b02b081870d2d9f24698bf3db8bfad0f5488941a6d324", "query": "allErrs = append(allErrs, field.Invalid(fldPath.Child(\"deletionTimestamp\"), newMeta.DeletionTimestamp, \"field is immutable; may only be changed via deletion\")) } <ins> // Finalizers cannot be added if the object is already being deleted. if oldMeta.DeletionTimestamp != nil { allErrs = append(allErrs, ValidateNoNewFinalizers(newMeta.Finalizers, oldMeta.Finalizers, fldPath.Child(\"finalizers\"))...) } </ins> // Reject updates that don't specify a resource version if len(newMeta.ResourceVersion) == 0 { allErrs = append(allErrs, field.Invalid(fldPath.Child(\"resourceVersion\"), newMeta.ResourceVersion, \"must be specified for an update\"))", "positive_passages": [{"docid": "doc-en-kubernetes-fc09a9ef1f5e957552c4803f2a8d5445e8992bd48fceb2f6d692294e4122c44c", "text": "says \"If the deletionTimestamp of the object is non-nil, entries in this list can only be removed.\". can you elucidate if I am assuming this does something different than reality\nThis is garbage collection finalizer field, not the namespace finalizer field that that new field was inspired from On Thursday, September 8, 2016, Tim Hockin wrote:\nI don't parse that - is this not a general-purpose \"refcount\" thing? It seems to work that way, except not as documented\nThis is a general purpose field and it should work like Tim thinks it should work. can you take a look at this when you don't have anything pressing for 1.4?\nThe namespace finalizer should switch to using this field if it is currently doing something else.\nI'm adding validation rule to prevent adding finalizers if deletionTimestamps is set. I'm still investigating why it can't be removed. This bug is strange.\nActually I guess it's a bug. It uses patch, and patch doesn't work on list of simple type, is a list of string.\nYep, it's a bug. I used to remove one finalizer and it worked as expected. I think this is a known bug of , we don't have a way to specify the mergekey of a list of simple type.\nIs there a bug open for this? Frankly, if is going to fail for things like this, we should not be offering it as a feature, or it should use PUT rather than PATCH , Chao Xu wrote:\nCreated cannot use PUT, because it's doing a three way merge (current state, last configuration, current configuration).\nThese are intended for automated use, not human use, so kubectl edit not working is just unfortunate, not a blocker. Although it's really unfortunate that PATCH is so broken. , Chao Xu wrote:\nWhy does need to be 3-way? I don't think that is the semantic a user would expect from an edit operation AT ALL. It certainly surprised ME. WRT automated vs human - if PATCH doesn't work (worse - says it succeeded but didn't) for some class of fields, then PATCH doesn't work, and we should not support it. Full stop. It's going to end up causing someone an outage. These are not necessarily related to this bug, but I'd call them pretty serious flaws.", "commid": "kubernetes_issue_32339", "tokennum": 515}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c4ee65ba71d8111c058b02b081870d2d9f24698bf3db8bfad0f5488941a6d324", "query": "allErrs = append(allErrs, field.Invalid(fldPath.Child(\"deletionTimestamp\"), newMeta.DeletionTimestamp, \"field is immutable; may only be changed via deletion\")) } <ins> // Finalizers cannot be added if the object is already being deleted. if oldMeta.DeletionTimestamp != nil { allErrs = append(allErrs, ValidateNoNewFinalizers(newMeta.Finalizers, oldMeta.Finalizers, fldPath.Child(\"finalizers\"))...) } </ins> // Reject updates that don't specify a resource version if len(newMeta.ResourceVersion) == 0 { allErrs = append(allErrs, field.Invalid(fldPath.Child(\"resourceVersion\"), newMeta.ResourceVersion, \"must be specified for an update\"))", "positive_passages": [{"docid": "doc-en-kubernetes-9d31dc444c003a67666d57a34035c70818d4ce333ea6367245ecb1f620bc17fd", "text": ", Daniel Smith wrote:\nDiscussed in real life. PATCH works, it's just that there are certain operations you cannot express using the strategicmerge patch syntax. I was wrong. is building . So perhaps it uses PATCH over PUT due to the efficiency.\nFWIW, I printed out the patch generated by when I removed one finalizer. The patch is empty, i.e., \"{}\".\n, Chao Xu wrote: Well, no, if there are operations that can not be represented, it really DOESN'T work. I still think it should not use PUT, but I bet Brian can prove me wrong.", "commid": "kubernetes_issue_32339", "tokennum": 129}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c4ef45834a2c6dba2f582cf76ecd14bee6c4b7d47028df41dfe47bcb24bddb83", "query": "\"time\" \"github.com/Azure/azure-sdk-for-go/services/compute/mgmt/2017-12-01/compute\" <ins> \"github.com/golang/glog\" </ins> \"k8s.io/apimachinery/pkg/types\" kwait \"k8s.io/apimachinery/pkg/util/wait\" <ins> \"k8s.io/kubernetes/pkg/cloudprovider\" </ins> ) const (", "positive_passages": [{"docid": "doc-en-kubernetes-6cfc50824280daf2f66f5e84f9a8c720c316cfa724f1e90fa02f306c798e5010", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind cleanup What happened: VirtualMachineScaleSetVM and VirtualMachine are different data structures (because of different API versions), so the disk attach operation seems duplicate between vm and vmss. That means although disk operations are in same logic, some duplication are still required now. They should use same api version in the future and should be merged into same code base, e.g. move sharing logic to Refer What you expected to happen: vmss and vm disk operations should share same code logic. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\nI have checked with currently we can\u2019t merge, e.g. following two structs are different since they using different sdk-for-azure versions. While in the end when sdk-for-azure version is upgraded, above two versions should be same and at that time, we should merge functions like \u2018AttachDisk\u2019, \u2018DetachDiskByName\u2019, 'GetDiskLun', GetNextDiskLun, DisksAreAttached", "commid": "kubernetes_issue_59736", "tokennum": 313}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c4fa0150e009b1be3023a777dbc65f42ccda353899fb6cbe330f57d67bbb51ad", "query": "\"k8s.io/kubernetes/pkg/client/record\" client \"k8s.io/kubernetes/pkg/client/unversioned\" \"k8s.io/kubernetes/pkg/controller/framework\" <ins> \"k8s.io/kubernetes/pkg/fields\" </ins> \"k8s.io/kubernetes/pkg/labels\" \"k8s.io/kubernetes/pkg/runtime\" )", "positive_passages": [{"docid": "doc-en-kubernetes-b0a441a371f8db864bebc11c7303837af71a86244bb0f50ec81fe1d8a09d5c71", "text": "The test is in flaky suite and no one seems to care. We need an owner for this test. cc Last failure log:\ndo you think you can take a look at this?\nThis is happening because of a bad assumption. The assumption is: if the reflector's store is consistent with etcd, the store given back to clients of the framework.Controller is too. I'd really like a general fix applicable to all controllers for this problem, but fixing it just for the RCs is pretty easy. In more detail: This function reports when the reflector has listed from apiserver. But the store given to the reflector is the fifo of the framework.Controller. The store given back to the caller is still not consistent, and will not be till the framework.Controller puts all the objects from the fifo into the client state store (). The rc specific fix: Before starting the rc manager, seed the expectations store with an expectation like {rc:foo, adds: foo.Status.Replicas, deletes:0}. This will wait for status.Replicas number of ADD events till a timeout. The general fix: Somehow expose this through framework.Controller.HasSynced (clients don't care about the fifo anyway, shouldn't it just be an implementation detail?) ideas? cc'ing people who have written controllers that might be interested I don't think this (and generally anything flaky for 1 release) is a p0, I can fix it if you don't mind dealing with the flakes till I've cleared things off my plate. I'd be more than happy to review a fix.\nWell, it's a P0 because test is flaky. E.g last run:\n- did you have chance to look into it?\nThe \"DaemonRestart\" tests are still labeled at . I will send a PR to promote them.\nare you still planning to send aPR to promote the DaemonRestart tests out of flaky? I think this is the right thing to do.\nAck; sorry, I lost this in the muck.", "commid": "kubernetes_issue_17829", "tokennum": 444}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c51297712c0807bb72e38e8f57099e155c77ba182d0b00ddc1daa05c319e177b", "query": "// Synced returns true if the view is synced (for the first time) func (f *federatedInformerImpl) ClustersSynced() bool { <del> f.Lock() defer f.Unlock() </del> return f.clusterInformer.controller.HasSynced() }", "positive_passages": [{"docid": "doc-en-kubernetes-59d4410d28b628c1be3d77bd9cd1cfdd4f523921f65910962a77fbec070a39e8", "text": "https://k8s- Failed: TestNamespaceController {namespace}", "commid": "kubernetes_issue_30855", "tokennum": 20}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c536fa102185c6c0d5a817a3d62b25ffc4f256546ce879da9277c1e451ac8f45", "query": "framework.Failf(\"failed dialing endpoint, %v\", err) } <ins> ginkgo.By(\"pod-Service(hostNetwork): udp\") ginkgo.By(fmt.Sprintf(\"dialing(udp) %v --> %v:%v (config.clusterIP)\", config.TestContainerPod.Name, config.ClusterIP, e2enetwork.ClusterUDPPort)) err = config.DialFromTestContainer(\"udp\", config.ClusterIP, e2enetwork.ClusterUDPPort, config.MaxTries, 0, config.EndpointHostnames()) if err != nil { framework.Failf(\"failed dialing endpoint, %v\", err) } ginkgo.By(fmt.Sprintf(\"dialing(udp) %v --> %v:%v (nodeIP)\", config.TestContainerPod.Name, config.NodeIP, config.NodeUDPPort)) err = config.DialFromTestContainer(\"udp\", config.NodeIP, config.NodeUDPPort, config.MaxTries, 0, config.EndpointHostnames()) if err != nil { framework.Failf(\"failed dialing endpoint, %v\", err) } </ins> ginkgo.By(\"node-Service(hostNetwork): http\") ginkgo.By(fmt.Sprintf(\"dialing(http) %v (node) --> %v:%v (config.clusterIP)\", config.NodeIP, config.ClusterIP, e2enetwork.ClusterHTTPPort))", "positive_passages": [{"docid": "doc-en-kubernetes-15fd873e113c2b87c10057fb05584532c0b0add34bb5504a54b7699060ebd74c", "text": "<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI --ci-kubernetes-e2e-gce-cos-k8sbeta-default Networking Granular Checks: Services should function for service endpoints using hostNetwork Triage looks like it's mostly flaking on this job only: Examples /sig network <!-- Please see the deflaking doc () for more guidance! --\n/milestone v1.21 (marking in the current milestone until we get confirmation whether it is relevant to the release or not)\nSlack Thread:\n/assign\nThis is fixed by , let's wait some runs to confirm before closing\n/milestone clear (since this has been deemed to be non release-blocking)\n/triage accepted\n/close\nClosing this issue. <detailsIn response to : This is fixed by , let's wait some runs to confirm before closing 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", "commid": "kubernetes_issue_100890", "tokennum": 243}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c567b9d136a8327766c88135dee362882b4830a33ab1926794ab35399cb6bc39", "query": "framework.ExpectNoError(err) }) <del> // TODO: Get rid of [DisabledForLargeClusters] tag when issue #56138 is fixed. ginkgo.It(\"should be able to change the type and ports of a service [Slow] [DisabledForLargeClusters]\", func() { </del> <ins> ginkgo.It(\"should be able to change the type and ports of a service [Slow]\", func() { </ins> // requires cloud load-balancer support e2eskipper.SkipUnlessProviderIs(\"gce\", \"gke\", \"aws\")", "positive_passages": [{"docid": "doc-en-kubernetes-23d2f241356f8f089aacd04cb02b22714ea2023d38ddcb3dae2268a8e3824c6f", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug This is a followup from filed separately now that we're not tracking this as part of 1.9 release. The tests have been disabled with [DisabledForLargeClusters] tag for now, and this fact will be mentioned in the scalability validation report for v1.9. This issue tracks fixing the test so the tag can be removed and the test ran again in the large cluster. /assign /kind e2e-test-failure\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIs this e2e test still broken?\nSorry for the confusion here. Currently this e2e test is disabled on extra large cluster due to some scalability issues with the load balancer related components. At the moment the issues haven't been completely resolved yet.\nok, adding priority so that I know it's not a 1.13 blocker. /priority important-longterm\ncc - this is why the relevant tests for are not part of the e2e suite.\nThis issue is still valid --- some action items on top of my head: Figure out a plan to make service controller properly handle operations in parallel. Check on the status for cloud providers (especially GCP, which the test ran against) on handling large number of nodes as LB backends. /remove-triage unresolved\nIssues 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 .", "commid": "kubernetes_issue_56138", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c567b9d136a8327766c88135dee362882b4830a33ab1926794ab35399cb6bc39", "query": "framework.ExpectNoError(err) }) <del> // TODO: Get rid of [DisabledForLargeClusters] tag when issue #56138 is fixed. ginkgo.It(\"should be able to change the type and ports of a service [Slow] [DisabledForLargeClusters]\", func() { </del> <ins> ginkgo.It(\"should be able to change the type and ports of a service [Slow]\", func() { </ins> // requires cloud load-balancer support e2eskipper.SkipUnlessProviderIs(\"gce\", \"gke\", \"aws\")", "positive_passages": [{"docid": "doc-en-kubernetes-82e0e423f6c651003322d5e3ca8baa34b91f0522dd0c015fbde1e81f949704e6", "text": "/lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten /lifecycle frozen\n/reopen Reopening as is being reverted in\nReopened this issue. <detailsIn response to : /reopen Reopening as is being reverted in 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\nthese tests are flaking in xref\ncc since these were enabled by\nYeah - though these failures doesn't seem to be scale related, they seem to be test related to me. This basically means nodes without public ips: It's pretty much the same thing as (just for a different test). should be addressing these kinds of errors. [Not a release blocker for sure]\nBTW - has been opened directly for this one.\n... so since is closed, Can we close this and re-enable for large clusters ? (i.e. remove the Tag in that disables this test) ? I'm not up to speed on the history but 2 related notes I came across digging into related test today... 's a couple of TODOs in the code referencing this specific issue, but your above direct issue is now closed, so we can close this as well right?... And if so, we can remove the TODO on the test... -enabling the test ... not sure wether the timing is good right now (given that is open right now , which sparked my stumbling upon this issue :))\nWe tried to enable all of them and that caused us a bunch of issues and those had to be reverted: A couple tests were enabled later in: and those seem fine. The remaining (mostly session-affinity ones) had some issue, which so far we didn't have time to debug and I haven't heard a good explanation why those were failing. It's possible that they were improved with , but I doubt those would really cause the failures we've seen in the past. So until this is debugged (or at least understood) I'm reluctant to enabling them.", "commid": "kubernetes_issue_56138", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c58896b042f4e8904f287db80ceec6c0a1dabba41113fabbdcaf56821cf3730d", "query": "w := newLogWriter(stdoutBuf, stderrBuf, &LogOptions{timestamp: test.timestamp, bytes: int64(test.bytes)}) for i := 0; i < test.stdoutLines; i++ { msg.stream = runtimeapi.Stdout <del> if err := w.write(msg); err != nil { </del> <ins> if err := w.write(msg, true); err != nil { </ins> assert.EqualError(t, err, errMaximumWrite.Error()) } } for i := 0; i < test.stderrLines; i++ { msg.stream = runtimeapi.Stderr <del> if err := w.write(msg); err != nil { </del> <ins> if err := w.write(msg, true); err != nil { </ins> assert.EqualError(t, err, errMaximumWrite.Error()) } }", "positive_passages": [{"docid": "doc-en-kubernetes-1611cacb700fc7bde4bed341ff7dc392aeb6c35e6c0f63ce6a10b84981e8d04a", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Docker has a hardcoded 16K limit on log line length, which splits lines longer than that into multiple messages in the log file. in , however, doesn't account for this when is set to and prints the timestamp in front of every entry in the log file instead of every logical line. This leads to random timestamps appearing in the middle of log lines, potentially breaking the applications that parse these logs. What you expected to happen: inserts timestamps once per logical line, so original log data is preserved. Alternatively, allow API to request the logs in a sane format like JSON, which would allow merging the lines back and combining them with the timestamps more intelligently on the application side. How to reproduce it (as minimally and precisely as possible): Create : apiVersion: v1 kind: Pod metadata: name: log-lines spec: containers: name: main image: busybox command: ['sh', '-c', 'while sleep 1; do echo -n ; for i in $(seq 1 ); do echo -n A; done; echo ; done'] Start the pod with Fetch the logs with , or using the API () Observe random timestamps inserted in the middle of the log lines. Environment: Kubernetes version (use ):\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI will work on it. /sig cli /remove-sig node\nThe logs are being corrupted by the API endpoint in kubelet, so shouldn't it be in scope of SIG node?\nThe log is not corrupted by k8s. The same log could be got using \"docker container logs -t CONTAINERID\" I think you should post your requirement to Docker.", "commid": "kubernetes_issue_77603", "tokennum": 465}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c58896b042f4e8904f287db80ceec6c0a1dabba41113fabbdcaf56821cf3730d", "query": "w := newLogWriter(stdoutBuf, stderrBuf, &LogOptions{timestamp: test.timestamp, bytes: int64(test.bytes)}) for i := 0; i < test.stdoutLines; i++ { msg.stream = runtimeapi.Stdout <del> if err := w.write(msg); err != nil { </del> <ins> if err := w.write(msg, true); err != nil { </ins> assert.EqualError(t, err, errMaximumWrite.Error()) } } for i := 0; i < test.stderrLines; i++ { msg.stream = runtimeapi.Stderr <del> if err := w.write(msg); err != nil { </del> <ins> if err := w.write(msg, true); err != nil { </ins> assert.EqualError(t, err, errMaximumWrite.Error()) } }", "positive_passages": [{"docid": "doc-en-kubernetes-495f248c0af4a1a8db07569505db46eac9f11be4907de183bc6923cd7882b142", "text": "Please refer following code Line 50 ~ 52 if config.Timestamps { logLine = append([]byte(msg.Timestamp.Format(jsonmessage.RFC3339NanoFixed)+\" \"), logLine...) }\nkubelet doesn't rely on Docker when reading logs, it reads the files itself (see the code linked in the issue). I don't think Docker would change the forced line splitting (see for example), so this should be fixed in Kubernetes.\nYour are right and kubelet read log file from host such as /var/log/pods/pods/NAMESPACEPOD-NAMExxx/....(JSON format) I will post a PR for it. /remove-sig cli /sig node\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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 .", "commid": "kubernetes_issue_77603", "tokennum": 539}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c58896b042f4e8904f287db80ceec6c0a1dabba41113fabbdcaf56821cf3730d", "query": "w := newLogWriter(stdoutBuf, stderrBuf, &LogOptions{timestamp: test.timestamp, bytes: int64(test.bytes)}) for i := 0; i < test.stdoutLines; i++ { msg.stream = runtimeapi.Stdout <del> if err := w.write(msg); err != nil { </del> <ins> if err := w.write(msg, true); err != nil { </ins> assert.EqualError(t, err, errMaximumWrite.Error()) } } for i := 0; i < test.stderrLines; i++ { msg.stream = runtimeapi.Stderr <del> if err := w.write(msg); err != nil { </del> <ins> if err := w.write(msg, true); err != nil { </ins> assert.EqualError(t, err, errMaximumWrite.Error()) } }", "positive_passages": [{"docid": "doc-en-kubernetes-2f614c9ad06da31fe9313a5b2eaea6d6901d55cba8508cf5ebe57105d301c4f6", "text": "Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\nStale 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\nI saw the attempt fixing this but it was scary (echo this comment: ). I suggested a way it may be improved. Also the proposed fix didn't introduce any e2e tests to validate that runtime behavior is not changed and runtimes keep the no-newline-on-splitted-log logic. are you or anybody on this thread are still interested to work on this? Please re-open if so. Meanwhile closing this ahead of bot doing it because the inactivity. /close\nClosing this issue. <detailsIn response to : I saw the attempt fixing this but it was scary (echo this comment: ). I suggested a way it may be improved. Also the proposed fix didn't introduce any e2e tests to validate that runtime behavior is not changed and runtimes keep the no-newline-on-splitted-log logic. Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_77603", "tokennum": 493}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c58896b042f4e8904f287db80ceec6c0a1dabba41113fabbdcaf56821cf3730d", "query": "w := newLogWriter(stdoutBuf, stderrBuf, &LogOptions{timestamp: test.timestamp, bytes: int64(test.bytes)}) for i := 0; i < test.stdoutLines; i++ { msg.stream = runtimeapi.Stdout <del> if err := w.write(msg); err != nil { </del> <ins> if err := w.write(msg, true); err != nil { </ins> assert.EqualError(t, err, errMaximumWrite.Error()) } } for i := 0; i < test.stderrLines; i++ { msg.stream = runtimeapi.Stderr <del> if err := w.write(msg); err != nil { </del> <ins> if err := w.write(msg, true); err != nil { </ins> assert.EqualError(t, err, errMaximumWrite.Error()) } }", "positive_passages": [{"docid": "doc-en-kubernetes-2e8714433462894a36e35ec9c24fb7c5a56d0558d2953a09bb86920b184c167e", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nYou can't reopen an issue/PR unless you authored it or you are a collaborator. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/remove-lifecycle rotten /reopen will fix it.\nReopened this issue. <detailsIn response to : /remove-lifecycle rotten /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/triage accepted\nThe Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.", "commid": "kubernetes_issue_77603", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c58896b042f4e8904f287db80ceec6c0a1dabba41113fabbdcaf56821cf3730d", "query": "w := newLogWriter(stdoutBuf, stderrBuf, &LogOptions{timestamp: test.timestamp, bytes: int64(test.bytes)}) for i := 0; i < test.stdoutLines; i++ { msg.stream = runtimeapi.Stdout <del> if err := w.write(msg); err != nil { </del> <ins> if err := w.write(msg, true); err != nil { </ins> assert.EqualError(t, err, errMaximumWrite.Error()) } } for i := 0; i < test.stderrLines; i++ { msg.stream = runtimeapi.Stderr <del> if err := w.write(msg); err != nil { </del> <ins> if err := w.write(msg, true); err != nil { </ins> assert.EqualError(t, err, errMaximumWrite.Error()) } }", "positive_passages": [{"docid": "doc-en-kubernetes-422d52914e9725e7355cb5e937e13c24e15f273f63951d92fe52d86a167487cb", "text": "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]:\nThe 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]:\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_77603", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c58896b042f4e8904f287db80ceec6c0a1dabba41113fabbdcaf56821cf3730d", "query": "w := newLogWriter(stdoutBuf, stderrBuf, &LogOptions{timestamp: test.timestamp, bytes: int64(test.bytes)}) for i := 0; i < test.stdoutLines; i++ { msg.stream = runtimeapi.Stdout <del> if err := w.write(msg); err != nil { </del> <ins> if err := w.write(msg, true); err != nil { </ins> assert.EqualError(t, err, errMaximumWrite.Error()) } } for i := 0; i < test.stderrLines; i++ { msg.stream = runtimeapi.Stderr <del> if err := w.write(msg); err != nil { </del> <ins> if err := w.write(msg, true); err != nil { </ins> assert.EqualError(t, err, errMaximumWrite.Error()) } }", "positive_passages": [{"docid": "doc-en-kubernetes-0e28d298340708e57a780633dba41fa2a744d19c9ab3d061a118f6b1e6c3d902", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI received a bug report about this issue. The root cause is that the buffer reads up to a new line. If the line is greater than 4096 bytes and '--timestamps' is turrned on the kubelet will write the timestamp and the partial log line. We will need to refactor the ReadLogs function to allow for a partial line read.", "commid": "kubernetes_issue_77603", "tokennum": 104}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c599dc0bdc0253a94b8c12a6f39298a187dc04b119737f91c2994d8bcab9a57c", "query": "} // exampleCert was generated from crypto/tls/generate_cert.go with the following command: <del> //    go run generate_cert.go  --rsa-bits 512 --host example.com --ca --start-date \"Jan 1 00:00:00 1970\" --duration=1000000h </del> <ins> //    go run generate_cert.go  --rsa-bits 1024 --host example.com --ca --start-date \"Jan 1 00:00:00 1970\" --duration=1000000h </ins> var exampleCert = []byte(`-----BEGIN CERTIFICATE----- <del> MIIBdzCCASGgAwIBAgIRAOVTAdPnfbS5V85mfS90TfIwDQYJKoZIhvcNAQELBQAw EjEQMA4GA1UEChMHQWNtZSBDbzAgFw03MDAxMDEwMDAwMDBaGA8yMDg0MDEyOTE2 MDAwMFowEjEQMA4GA1UEChMHQWNtZSBDbzBcMA0GCSqGSIb3DQEBAQUAA0sAMEgC QQCoVSqeu8TBvF+70T7Jm4340YQNhds6IxjRoifenYodAO1dnKGrcbF266DJGunh nIjQH7B12tduhl0fLK4Ezf7/AgMBAAGjUDBOMA4GA1UdDwEB/wQEAwICpDATBgNV HSUEDDAKBggrBgEFBQcDATAPBgNVHRMBAf8EBTADAQH/MBYGA1UdEQQPMA2CC2V4 YW1wbGUuY29tMA0GCSqGSIb3DQEBCwUAA0EAk1kVa5uZ/AzwYDVcS9bpM/czwjjV xq3VeSCfmNa2uNjbFvodmCRwZOHUvipAMGCUCV6j5vMrJ8eMj8tCQ36W9A== </del> <ins> MIIB+zCCAWSgAwIBAgIQK+TtYrwiS4SZU43mEj44eDANBgkqhkiG9w0BAQsFADAS MRAwDgYDVQQKEwdBY21lIENvMCAXDTcwMDEwMTAwMDAwMFoYDzIwODQwMTI5MTYw MDAwWjASMRAwDgYDVQQKEwdBY21lIENvMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCB iQKBgQDGrjJJBajkyWUEMVwVadkNI54cKV7snXFV6ZRE2jPQUpY0/6a2RKqjGekB +SKxN+ALY/WiPBkYCQVg7Bc1hFneHfR8T3oXlKpOv9VWMeKLH3vLmAKnrZHgBgZ3 jVcXupQlVLobRzABzfOFhhzMcs89vzbMDcxw+tRK84XYB+MNbwIDAQABo1AwTjAO BgNVHQ8BAf8EBAMCAqQwEwYDVR0lBAwwCgYIKwYBBQUHAwEwDwYDVR0TAQH/BAUw AwEB/zAWBgNVHREEDzANggtleGFtcGxlLmNvbTANBgkqhkiG9w0BAQsFAAOBgQCJ uqAiZIaaz5W2dbIUHnWJ3M47fuou8G2c4JzxPRfKxPGrOpBGZyk/I8v/MBZ50zdG ZCoFO0keiVr0q2fyMgKwcWNN4cwfRBgQWmk6SHJJR/jWHjnvnRDqhfPHzcqYqd90 MtpcamlkHhSG616mBaUujb+EdjlrxCwiPTv/U+z7Ug== </ins> -----END CERTIFICATE-----`) var exampleKey = []byte(`-----BEGIN RSA PRIVATE KEY----- <del> MIIBOgIBAAJBAKhVKp67xMG8X7vRPsmbjfjRhA2F2zojGNGiJ96dih0A7V2coatx sXbroMka6eGciNAfsHXa126GXR8srgTN/v8CAwEAAQJASdzdD7vKsUwMIejGCUb1 fAnLTPfAY3lFCa+CmR89nE22dAoRDv+5RbnBsZ58BazPNJHrsVPRlfXB3OQmSQr0 SQIhANoJhs+xOJE/i8nJv0uAbzKyiD1YkvRkta0GpUOULyAVAiEAxaQus3E/SuqD P7y5NeJnE7X6XkyC35zrsJRkz7orE8MCIHdDjsI8pjyNDeGqwUCDWE/a6DrmIDwe emHSqMN2YvChAiEAnxLCM9NWaenOsaIoP+J1rDuvw+4499nJKVqGuVrSCRkCIEqK 4KSchPMc3x8M/uhw9oWTtKFmjA/PPh0FsWCdKrEy </del> <ins> MIICeAIBADANBgkqhkiG9w0BAQEFAASCAmIwggJeAgEAAoGBAMauMkkFqOTJZQQx XBVp2Q0jnhwpXuydcVXplETaM9BSljT/prZEqqMZ6QH5IrE34Atj9aI8GRgJBWDs FzWEWd4d9HxPeheUqk6/1VYx4osfe8uYAqetkeAGBneNVxe6lCVUuhtHMAHN84WG HMxyzz2/NswNzHD61ErzhdgH4w1vAgMBAAECgYEAgv0GGi6pE23UM9d3JocKmycI bvi3pLiIqGO/ZUWXM5m/fmGuwCy1c6L5hFuFC+ISzG+y2qtUwAvyh9wf0SDZPfVK X+egWPJksBCPqphvPsxzolHNoi5FEvUhxXyDedkB3XuP2U3hniwEVtIA/rf1lHLt qMDEa/y4K1GT8QI0Y8ECQQDNl5Zu38BaroOLMpm7XBySlYVp8hs2q4TCnayxufAw wKZJpcTKTCiaZAqF00ZDu2YZ3m3dkDiYB6v3x2HIADVtAkEA92TIYjBy5Bx7+K2S X1YW+7P90UImxXGbPQeoODmghUD+/MfnBQyKM7AS7G2jO81hwzGfFiKk7AqF/nM5 lx1wywJANjoTfa8ax1Bcdeyky9xh1PAHPoiTUPowjDyWflIy3kkSEz7cBxfLZd2Z QO8XC2p0ZcJbbCNMKh1r6HD4g446iQJBANOMKdHUzhoDxXrTqcu+SS75Lf0HzTGf QPkCGDXkCUCJYMH1irYFkBQ85yGnayMTMBsCzp/WBiMVqJj6HO/8q9sCQQCxtTUn rOjiKXcyl2aNL7bGLfWtexl+MT2Z/PrjYcN5XbK4wmy2TFUAA1BCyHhv1/1jUDzf Ibw/Lq9YIiqVrg6T </ins> -----END RSA PRIVATE KEY-----`)", "positive_passages": [{"docid": "doc-en-kubernetes-c0ae7c5a9b926980f7fbe5b2efcf245b830bbe6bb1b2519b4aac2b3a38b48ce6", "text": "Golang 1.13 uses TLS 1.13 by default (opt-out), which introduces RSA-PSS. RSA-PSS does not work with keys that are too small. The issue was uncovered during Fedora mass rebuild which uses Golang 1.13: See /sig api-machinery\nWhat is the failure mode if a smaller key is used?\n/sig auth /sig scalability\n/sub", "commid": "kubernetes_issue_80733", "tokennum": 90}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c5becb4a628bc8a8988a94eb54391969e8980c9d2cc05a96248814c739bc4e8e", "query": "\"../examples/walkthrough\": { \"pod1\": &api.Pod{}, \"pod2\": &api.Pod{}, <ins> \"pod-with-http-healthcheck\": &api.Pod{}, \"service\":                   &api.Service{}, \"replication-controller\":    &api.ReplicationController{}, </ins> }, }", "positive_passages": [{"docid": "doc-en-kubernetes-8b28935a84f88ac18c7fc65931585a933c76320eb13cd6ef7170c583b31097e6", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: cAdvisor has a option to only collect docker related cgroups. Kubelet stats api now supports allocatable cgroup, /kubepods, for the runtime cgroup and the kubelet cgroup. But with settings, Kubelet stats api can not query pod related cgroups metrics. FYI: What you expected to happen: should be compatible with kubelet stats api.\n/cc\n/sig node /sig instrumentation\nadd to cadvisor in A comma-separated list of cgroup path prefix that needs to be collected even docker-only is specified bump cadvisor dep for Kubernetes setting to\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_61994", "tokennum": 525}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c5becb4a628bc8a8988a94eb54391969e8980c9d2cc05a96248814c739bc4e8e", "query": "\"../examples/walkthrough\": { \"pod1\": &api.Pod{}, \"pod2\": &api.Pod{}, <ins> \"pod-with-http-healthcheck\": &api.Pod{}, \"service\":                   &api.Service{}, \"replication-controller\":    &api.ReplicationController{}, </ins> }, }", "positive_passages": [{"docid": "doc-en-kubernetes-c993cfc824e8b144526f19f7f90c37dca7b5b7104e06f115b259fa72f1d9ae68", "text": "/close\nClosing 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", "commid": "kubernetes_issue_61994", "tokennum": 71}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c600d9fd70b092dabbbc961a584ea664a57e8d6c62722b7c34de560cf309775e", "query": "var defaultKubernetesFeatureGates = map[featuregate.Feature]featuregate.FeatureSpec{ CrossNamespaceVolumeDataSource: {Default: false, PreRelease: featuregate.Alpha}, <ins> AllowServiceLBStatusOnNonLB: {Default: false, PreRelease: featuregate.Deprecated}, // remove after 1.29 </ins> AnyVolumeDataSource: {Default: true, PreRelease: featuregate.Beta}, // on by default in 1.24 APISelfSubjectReview: {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // GA in 1.28; remove in 1.30", "positive_passages": [{"docid": "doc-en-kubernetes-e021a9a686a92d83ba285392c70089f3a0813200ee010fb06825ed96dc15cfdb", "text": "xref I think this may be one of the few cases where we can actually change the behavior in a \"breaking\" way. User creates service with , is empty Controller or user updates the status subresource, sets (not wiped or validated, should be) User updates in any way, is wiped It's clear that the is not meant to be set when is not \"LoadBalancer\". The question is: 1) Fail validation? 2) Silently discard the value? 3) Warn and then discard the value? 4) Just warn and leave it. Because we allowed it in the past, but it is so volatile, I lean towards 3. and - the people most familair with this type. Edit: PrepareForUpdate() runs before warnings. So: (1) is easy (2) is easy (4) is slightly less easy than (2) (3) is slightly less easy than (4)\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nOMG change it to clusterIP as expected Status is wiped update status as ClusterIP ... and if I edit the service back to loadbalancer it keeps the status??\n/kind bug\n/retitle Service can be set when !=\nWe talked about this one at the SIG Network meeting today. suggested we use the feature gate for deprecation option to phase the current (problematic) functionality out.\n/triage accept\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /triage accept 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", "commid": "kubernetes_issue_119700", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c648b23903ce707995ea3d5ea4a4a3fc5bce4d4224d02cb8723c6d3fc9cee7cb", "query": "v1 \"k8s.io/api/core/v1\" rbacv1 \"k8s.io/api/rbac/v1\" storagev1 \"k8s.io/api/storage/v1\" <del> storagev1beta1 \"k8s.io/api/storage/v1beta1\" </del> apierrors \"k8s.io/apimachinery/pkg/api/errors\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/runtime/schema\"", "positive_passages": [{"docid": "doc-en-kubernetes-e2f4fe7b99012f8e7173e2f6c46ef5707967f19510033d4b6b03e3a31c7298f0", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --ci-kubernetes-e2e-gci-gce-slow [sig-storage] Dynamic Provisioning DynamicProvisioner [Slow] should provision storage with different parameters 5/13 https://k8s- v1beta1.StorageClass got removed in We should remove the v1beta1 test.\n/assign can you help take a look?\n/triage accepted\n/sig storage\nI run the test with the latest from master without removing the beta test and it failed with a different error before getting to the beta test part: Do you have any idea what would've happened in my setup? I redeployed k/k using master HEAD\nFor this testcase: I saw that the provisioned PD has a size of 1.5Gi according to kubernetes: And in gcloud It's really interesting that the test was expecting 2Gi to be created, is this something that was changed recently?\nThe logs you posted are showing pd csi as the provisioner. Were you testing with the intree driver or csi driver? The CSI driver should to the nearest Gb. I believe intree does the .\nI think I did intree because I didn't send as an argument in my command: It's interesting that the PVC has this annotation too:\nmmm something interesting about my setup is that I created the cluster with CSIMigration turned on Do you think that might be forcing the usage of ?\nYes likely. Try with CSIMigration off and see if that helps. If so, then this potentially seems like a rounding bug with the csi driver\nThanks I tried with and it did indeed round up to 2Gi.", "commid": "kubernetes_issue_102076", "tokennum": 373}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c67474229eaa1b2ec4d736207b8b64b32537ef48361320c867a54fdabb3e4073", "query": "{% set params = \"--master=127.0.0.1:8080\" + \" \" + cluster_name + \" \" + cluster_cidr + \" \" + allocate_node_cidrs + \" \" + service_cluster_ip_range + \" \" + terminated_pod_gc + \" \" + enable_garbage_collector + \" \" + cloud_provider  + \" \" + cloud_config + \" \" + service_account_key + \" \" + log_level + \" \" + root_ca_file -%} {% set params = params + \" \" + feature_gates -%} <ins> {% if pillar.get('enable_hostpath_provisioner', '').lower() == 'true' -%} {% set params = params + \" --enable-hostpath-provisioner\" %} {% endif -%} </ins> # test_args has to be kept at the end, so they'll overwrite any prior configuration {% if pillar['controller_manager_test_args'] is defined -%}", "positive_passages": [{"docid": "doc-en-kubernetes-ef45ff070b2c05a069c3f77b9a64e0bfff59d1f717362ac04203c879e5a7b68c", "text": "feature request Enables easier testing for pv/pvc, and all derivatives like pet sets. The only alternative is to use manually created pv of local type. I have time to work on it myself and created this feature to collect feedback/ideas on what provider should be enabled by default.\nSince this was merged should we close this issue?", "commid": "kubernetes_issue_32119", "tokennum": 67}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c6905e530fa0a37237645627eb68081d94672d025a59076ae0821ddc019af1dd", "query": "{Name: \"Name\", Type: \"string\", Format: \"name\", Description: metav1.ObjectMeta{}.SwaggerDoc()[\"name\"]}, {Name: \"Status\", Type: \"string\", Description: \"Status of the cluster\"}, {Name: \"Age\", Type: \"string\", Description: metav1.ObjectMeta{}.SwaggerDoc()[\"creationTimestamp\"]}, <ins> {Name: \"Labels\", Type: \"string\", Description: \"The labels of the cluster\"}, </ins> } h.TableHandler(clusterColumnDefinitions, printCluster) h.TableHandler(clusterColumnDefinitions, printClusterList)", "positive_passages": [{"docid": "doc-en-kubernetes-f29982137c07dadb3e257d7391e0d9b7bfd5f1ce8fdca72f798301cc159728a0", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: After labeling clusters in a Federation, when you type the field is empty. What you expected to happen: The fiels should contain information about the labels in the cluster How to reproduce it (as minimally and precisely as possible): a federation control pane in any Cloud Provider and any DNS provider your cluster: info aboyut the cluster with the flag: Note: if you describe it, you see the labels being : Environment: Kubernetes version (use ): 1.8.0 Cloud provider or hardware configuration**: anyone OS (e.g. from /etc/os-release): Ubuntu 16.04 Kernel (e.g. ): Linux Install tools: curl Others:\n/sig multicluster\nI'm working on it.", "commid": "kubernetes_issue_53729", "tokennum": 179}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c6f231759f3fc86df2ad63249385eceb08b3af01fe64f69e9f24435cd670dadf", "query": "\"redis-sentinel-service\":    &api.Service{}, }, \"../examples/resourcequota\": { <del> \"resource-quota\": &api.ResourceQuota{}, </del> <ins> \"namespace\": &api.Namespace{}, \"limits\":    &api.LimitRange{}, \"quota\":     &api.ResourceQuota{}, </ins> }, \"../examples/rethinkdb\": { \"admin-pod\":      &api.Pod{},", "positive_passages": [{"docid": "doc-en-kubernetes-b9774b02da3d7547dcc6ec82c6d1246d6586e28e6fe16ad58f3c28b2558ac905", "text": "Resource quota example is missing readme. Was it once there and was accidentally deleted?\nI wrote something up in Origin repo I need to repurpose for Kubernetes. Sent from my iPhone", "commid": "kubernetes_issue_8749", "tokennum": 41}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c70b3ad9a6d280a9ba782d5fab6e732aac03a47154bbc5bac17b1745ff3893ab", "query": "kube::test::get_object_assert deployment \"{{range.items}}{{(index .spec.template.spec.containers 1).resources.limits.cpu}}:{{end}}\" \"300m:\" kube::test::get_object_assert deployment \"{{range.items}}{{(index .spec.template.spec.containers 1).resources.requests.cpu}}:{{end}}\" \"300m:\" # Set limits on a local file without talking to the server <del> kubectl set resources -f hack/testdata/deployment-multicontainer.yaml -c=perl --limits=cpu=500m --requests=cpu=500m --dry-run -o yaml \"${kube_flags[@]}\" kubectl set resources deployment nginx-deployment -c=perl --limits=cpu=500m --requests=cpu=500m --dry-run -o yaml \"${kube_flags[@]}\" ! kubectl set resources deployment nginx-deployment -c=perl --limits=cpu=500m --requests=cpu=500m --local -o yaml \"${kube_flags[@]}\" </del> <ins> kubectl set resources deployment -f hack/testdata/deployment-multicontainer.yaml -c=perl --limits=cpu=300m --requests=cpu=300m --dry-run -o yaml \"${kube_flags[@]}\" </ins> kube::test::get_object_assert deployment \"{{range.items}}{{(index .spec.template.spec.containers 0).resources.limits.cpu}}:{{end}}\" \"200m:\" kube::test::get_object_assert deployment \"{{range.items}}{{(index .spec.template.spec.containers 1).resources.limits.cpu}}:{{end}}\" \"300m:\" kube::test::get_object_assert deployment \"{{range.items}}{{(index .spec.template.spec.containers 1).resources.requests.cpu}}:{{end}}\" \"300m:\"", "positive_passages": [{"docid": "doc-en-kubernetes-f45c12318e35043c65362c27e361ee13adfef369e183f2b4f0557c11353bd9e9", "text": "from https://k8s-\nReally suspect this is\nThis is putting us into test-go post-commit run is broken\ncc:\nmarked this p0 - if a fix isn't easy let's try to identify what introduced this and revert.\nThis flake on: 2016-10-30 07:19 PDT First instance: : It is flaking frequently, blocking PRs from getting merged, and slowing the submit queue ( at 75%). As on-call, I'm going to try and identify the cluprit and revert. Can use all help in doing so.\ncan you investigate whether your additional tests could cause this (by breaking the deployment of those pods, for instance) , Saad Ali wrote:\nPR looks most suspect to me. It mucked with , and the errors we are seeing in each of the failures is related to : That PR was merged at Oct 30, 2016, 6:18 AM PDT and the first flake in was at Oct 30, 2016, 7:19 AM PDT. Thoughts? CC\nI'm going to initiate a revert of to see if that fixes the issue\nIMO we can just change the flaky test to not get pods but some other resources, such as deployments. We can't really expect to clean up pods immediately.\nI'm going to proceed with revert (). Please feel free to send a follow up PR to handle this more gracefully.\nGoing to leave this opened until we have a few hours of runs with the revert. Want to verify, with some degree of certainty, that the revert took care of this flake.\nWe had 15 green runs of in a row. Considering this flake fixed.", "commid": "kubernetes_issue_35898", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c786f4739180b8bb4276049674047f8bd6dd64394d06fe49bdfcb0fe44279fdb", "query": "// define volume limit to be 2 for this test var err error <del> init(testParameters{nodeSelectorKey: \"node-attach-limit-csi\", attachLimit: 2}) </del> <ins> nodeSelectorKey := fmt.Sprintf(\"attach-limit-csi-%s\", f.Namespace.Name) init(testParameters{nodeSelectorKey: nodeSelectorKey, attachLimit: 2}) </ins> defer cleanup() nodeName := m.config.ClientNodeName attachKey := v1.ResourceName(volumeutil.GetCSIAttachLimitKey(m.provisioner))", "positive_passages": [{"docid": "doc-en-kubernetes-1f9c3e5cc71a2eb982031bdc2376fc7ce9ffe73bb0100bc8df9e6d81af2040c4", "text": "Looks like CSI volume limit test is flaking. /sig storage /assign\nThis flake isn't happening in normal clusters, appears to be alpha only issue.", "commid": "kubernetes_issue_75070", "tokennum": 34}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c7a502b0bf51f34c5a159f62f908a6ad01ea81edb51e954b0f3be17719a34111", "query": "// buildELBSecurityGroupList returns list of SecurityGroups which should be // attached to ELB created by a service. List always consist of at least <del> // 1 member which is an SG created for this service or a SG from the Global config. Extra groups can be // specified via annotation func (c *Cloud) buildELBSecurityGroupList(serviceName types.NamespacedName, loadBalancerName, annotation string) ([]string, error) { </del> <ins> // 1 member which is an SG created for this service or a SG from the Global config. // Extra groups can be specified via annotation, as can extra tags for any // new groups. func (c *Cloud) buildELBSecurityGroupList(serviceName types.NamespacedName, loadBalancerName string, annotations map[string]string) ([]string, error) { </ins> var err error var securityGroupID string", "positive_passages": [{"docid": "doc-en-kubernetes-f0769863fab39b633cda95f4d162dbe6bf42638a791c88a2a3acb41bb68633b3", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature /sig aws What happened: In k8s 1.7, when creating a service of type LoadBalancer, K8S creates the ELB and a Security Group for it. For these resources, it adds a tag, constructed dynamically, containing the cluster id: \"${cluster_id}\" with the value \"true\" What you expected to happen: We'd like to have also a statically named tag , as it was in 1.5 (\"KubernetesCluster\") with the value of the cluster id. How to reproduce it (as minimally and precisely as possible): Running on AWS cloud provider, create a service of type LoadBalancer. Anything else we need to know?: The reason for what we expect is that we have tight security constraints that require us to fine tune the IAM policies for the Instance profiles that the controllers use. With a statically named tag we were able, in 1.5, to restrict the permissions in the IAM policy to act only on the k8s managed resources (ELBs, security groups). Here is the relevant part of the IAM policy: With a dynamically named tag we are not able to do this any more as AWS IAM doesn't support something like: We are sharing the Instance Profiles among different k8s clusters, hence the \"\" in the value of the tag. Environment: Kubernetes version (use ):Cloud provider or hardware configuration*: AWS OS (e.g. from /etc/os-release):Kernel (e.g. ):Install tools: kube-aws Others:\nReiterating the mentions to trigger a notification: <detailsIn response to : <!-- This form is for bug reports and feature requests ONLY! -- /sig aws In k8s 1.7, when creating a service of type LoadBalancer, K8S creates the ELB and a Security Group for it. For these resources, it adds a tag, constructed dynamically, containing the cluster id: \"${cluster_id}\" with the value \"true\" We'd like to have also a statically named tag , as it was in 1.5 (\"KubernetesCluster\") with the value of the cluster id. Running on AWS cloud provider, create a service of type LoadBalancer.", "commid": "kubernetes_issue_53489", "tokennum": 543}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c7a502b0bf51f34c5a159f62f908a6ad01ea81edb51e954b0f3be17719a34111", "query": "// buildELBSecurityGroupList returns list of SecurityGroups which should be // attached to ELB created by a service. List always consist of at least <del> // 1 member which is an SG created for this service or a SG from the Global config. Extra groups can be // specified via annotation func (c *Cloud) buildELBSecurityGroupList(serviceName types.NamespacedName, loadBalancerName, annotation string) ([]string, error) { </del> <ins> // 1 member which is an SG created for this service or a SG from the Global config. // Extra groups can be specified via annotation, as can extra tags for any // new groups. func (c *Cloud) buildELBSecurityGroupList(serviceName types.NamespacedName, loadBalancerName string, annotations map[string]string) ([]string, error) { </ins> var err error var securityGroupID string", "positive_passages": [{"docid": "doc-en-kubernetes-a01a3c41e631760f28b69af73c7e0688234151a20f7dd4b67642a3c81f6b4dfa", "text": "The reason for what we expect is that we have tight security constraints that require us to fine tune the IAM policies for the Instance profiles that the controllers use. With a statically named tag we were able, in 1.5, to restrict the permissions in the IAM policy to act only on the k8s managed resources (ELBs, security groups). Here is the relevant part of the IAM policy: Environment: Kubernetes version (use ):OS (e.g. from /etc/os-release):Others: </details\nI believe they are moving away from the tag since there are many resources that can be shared by multiple clusters. could you use an annotation?\nWe removed the condition in roles in the end. Thank you for your suggestion.\nThat annotation affects the ELB but not any security groups that are created. can you please reopen this? You reported a real issue, and even if it no longer affects you, it needs to be tracked and fixed.\nIndeed, this might be a feature that someone else would need.\nIn fact, this is a feature I need!\nFood for thought: should we propagate the tags on the ELB to the SG, or should we introduce an annotation for the SG specifically?", "commid": "kubernetes_issue_53489", "tokennum": 265}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c7b7a6e7c6b3f5de76fb3009c11c9872f590b66bfe77cb9c47b0acaefde7011f", "query": "var _ = SIGDescribe(\"PriorityPidEvictionOrdering [Slow] [Serial] [Disruptive][NodeFeature:Eviction]\", func() { f := framework.NewDefaultFramework(\"pidpressure-eviction-test\") f.NamespacePodSecurityLevel = admissionapi.LevelPrivileged <del> pressureTimeout := 2 * time.Minute </del> <ins> pressureTimeout := 3 * time.Minute </ins> expectedNodeCondition := v1.NodePIDPressure expectedStarvedResource := noStarvedResource", "positive_passages": [{"docid": "doc-en-kubernetes-182fb1698032797795262f9c7145a24707ed3bbf5827100ad6f2695fe6c12a83", "text": "PriorityPidEvictionOrdering [Slow] [Serial] [Disruptive][NodeFeature:Eviction] when we run containers that should cause PIDPressure should eventually evict all of the correct pods /kind failing-test <!-- If this is a flake, please add: /kind flake --/sig node /assign /priority important-soon\nfork-bomb-container-container exited with code 2. I tried to create a pod in my env of containerd: The pod can be running and it works as designed. I need to test it in cri-o later.\n/cc\n/triage accepted", "commid": "kubernetes_issue_119090", "tokennum": 137}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c7ccaa31d695544c9015ddf65e1995c9de3505d8de9fbde80f056d63b87a7b7d", "query": "command: - /usr/local/bin/kube-proxy - --kubeconfig=/var/lib/kube-proxy/kubeconfig.conf <ins> {{ .ExtraParams }} </ins> {{ .ClusterCIDR }} securityContext: privileged: true", "positive_passages": [{"docid": "doc-en-kubernetes-fdf6c8e5598e80992f62cef52eca112e7ba1d532fe8ace89dc932a5edac53dea", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: Currently, IPVS proxier does not run any e2e test cases. What you expected to happen: I think it's important to create test suite for IPVS in upstream CI which will help a lot in moving IPVS existing alpha. Anything else we need to know?: Let's work together. /sig network\nSelf /assign\nThere are to ways to do this work: , but doesn't support any kube-proxy config right now, so I had this pr , and also, need support it too, see this pr: kubernetes/kubernetes-anywhere build cluster. See this pr: kubernetes/test-infra The second way is much easier and faster, but I was told they gonna deprecated the , so in the long term, we still need and 's support. If anybody have better way or have some suggestion about this, please let me know, I'll be really appreciate, Thanks.", "commid": "kubernetes_issue_52834", "tokennum": 247}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c81c374869d045c8ff2635a39e5233c6991f896417eb8208c402ce8b2af70aa5", "query": "allErrs = append(allErrs, field.Forbidden(fldPath.Child(\"x-kubernetes-int-or-string\"), \"must be false to be structural\")) } <ins> // forbid reasoning about metadata because it can lead to metadata restriction we don't want if _, found := v.Properties[\"metadata\"]; found { allErrs = append(allErrs, field.Forbidden(fldPath.Child(\"properties\").Key(\"metadata\"), \"must not be specified in a nested context\")) } </ins> return allErrs }", "positive_passages": [{"docid": "doc-en-kubernetes-4be11de3bdb9e2a86ad3a19c4d6f5342db422d48e5979c118fca9ce077f64900", "text": "We allow CRD authors to write . Currently we don't restrict writing validation for , which means people can have . For example, people can have additive name constraints (require CR to be ) with the following schema: This brings us two questions: do we if \"metadata\" is included in the schema: simplest option is to publish standard metav1.ObjectMeta schema info, and use any CRD-specified \"metadata\" properties as additive validation (just like in-tree types do, publishing standard ObjectMeta schema info, and implementing type-specific name validation internally) alternatively, we can try merging user-specified metadata schema with the standard one. Technically people should only add extra validation to existing metadata properties (adding new fields to metadata won't work since they will be pruned by built-in validation first), but it's unclear to me how arbitrary people may want the metadata validation to be term question is whether to allow people specifying metadata validation at all, or just allow a subset (like name validation) in CRD v1 /sig api-machinery /area custom-resources cc\nWhat is the difference between these two? I mean the end result is the same right? The only thing that can be is validation. Nothing else works unless you are considering extensions?\nThe former means we drop/hide user-specified metadata schema when we publish CRD OpenAPI. We still validate user-specified constraints on server side, but client-side validation won't see them. The latter enables client-side user-specified metadata validation.\nIf it's possible to merge with standard metadata schema info, or at the cost of not publishing the standard schema. My inclination would be to publish the complete standard schema for metadata/apiVersion/kind, which we know is complete and accurate, and use and user-specified schema for those fields as addition validations server side", "commid": "kubernetes_issue_74620", "tokennum": 396}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c84ff1f427bbe272798f5148f9cdb98f5d98cb246f3b109929ac032c50dce983", "query": "} return false, nil, nil } <del> mockMetadataClient := metadatafake.NewSimpleMetadataClient(scheme.Scheme) </del> <ins> mockMetadataClient := metadatafake.NewSimpleMetadataClient(metadatafake.NewTestScheme()) </ins> mockMetadataClient.PrependReactor(\"delete-collection\", \"flakes\", ns1FlakesNotFound) mockMetadataClient.PrependReactor(\"list\", \"flakes\", ns1FlakesNotFound)", "positive_passages": [{"docid": "doc-en-kubernetes-d7e6fda1614d5720cc8c8b15824f08c5e880f7950d0c5cc5cd811c2fcceb82ab", "text": "Because of this scheme mutation, this leads to concurrent use of the same scheme to cause the program to panic. It would be ideal to do this in some concurrent safe manner or add a warning or similar\n/sig api-machinery\n/assign\n/assign /triage accepted", "commid": "kubernetes_issue_107823", "tokennum": 54}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c8850c190a8f9e4787d4601da45155b531d750920bb5df1fd8aedafd3ede8b35", "query": "// This call is idempotent, and must not return an error if the sandbox has // already been removed. func (f *RemoteRuntime) RemovePodSandbox(ctx context.Context, req *kubeapi.RemovePodSandboxRequest) (*kubeapi.RemovePodSandboxResponse, error) { <del> err := f.RuntimeService.RemovePodSandbox(req.PodSandboxId) </del> <ins> err := f.RuntimeService.StopPodSandbox(req.PodSandboxId) </ins> if err != nil { return nil, err }", "positive_passages": [{"docid": "doc-en-kubernetes-59e10ac9f842c5137d16434532387dd09ba10f619a9264b3e368e8bd51bb44b7", "text": "What happened: It's most visible in the test <img width=\"323\" alt=\"Screen Shot 2020-05-20 at 6 09 10 PM\" src=\"https://user-\"It shows up in kind, kube- and kops jobs The regression was introduced somewhere within , possible culprits are: (FYI (FYI (FYI There are more tests affected, just not as prominently (visually inspecting ) [sig-apps] StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications with PVCs [sig-apps] StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance] [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Inline-volume (default fs)] volumes should store data [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data I wasn't sure whether to tag this as kind/regression or not, I'll leave that up to or someone /sig node /sig api-machimery /sig scheduling\nThe label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : What happened: It's most visible in the test (FYI (FYI (FYI StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications with PVCs [sig-apps] StatefulSet [] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance] [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Inline-volume (default fs)] volumes should store data [sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data /sig api-machimery /sig scheduling 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.", "commid": "kubernetes_issue_91316", "tokennum": 506}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c8850c190a8f9e4787d4601da45155b531d750920bb5df1fd8aedafd3ede8b35", "query": "// This call is idempotent, and must not return an error if the sandbox has // already been removed. func (f *RemoteRuntime) RemovePodSandbox(ctx context.Context, req *kubeapi.RemovePodSandboxRequest) (*kubeapi.RemovePodSandboxResponse, error) { <del> err := f.RuntimeService.RemovePodSandbox(req.PodSandboxId) </del> <ins> err := f.RuntimeService.StopPodSandbox(req.PodSandboxId) </ins> if err != nil { return nil, err }", "positive_passages": [{"docid": "doc-en-kubernetes-aa1ca8a6c4f552108d5e4f5627cf5341a0bb7748f7b82e510f647cbc02b0a76b", "text": "</details\n/cc\nwill increase the time for deletion of pod and it should be expected because currently pod is deleted from apiserver before removing the sandbox container but after this fix pod will be deleted from the apiserver only after deleting the sandbox container.\n/remove-sig scheduling doesn't affect scheduling running time at all.\nYeah, is almost definitely the culprit. Last time we changed that code path, it also caused a regression. The degradation in performance is expected, but a 5x slowdown is definitely larger than it should be.\ndo we know if that's because the status used by the path is stale, or if removing sandboxes is actually that slow?\nif there's not a quick fix, should we revert and bring it back in once the root issue is understood?\nI think a revert is appropriate in this case.\nok, I'll open it\nopen at\nI agree with that 5x is something which shouldn't happen and i can take a look on why thats happening and that might require changing the way how the sandbox is currently deleted which is only during GC.", "commid": "kubernetes_issue_91316", "tokennum": 237}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c89a4bdeaebe80d3865795cbb0b0bc4b7c0ebee71376f0692e3efde1370b29d6", "query": "function config-ip-firewall { echo \"Configuring IP firewall rules\" # The GCI image has host firewall which drop most inbound/forwarded packets. <del> # We need to add rules to accept all TCP/UDP packets. </del> <ins> # We need to add rules to accept all TCP/UDP/ICMP packets. </ins> if iptables -L INPUT | grep \"Chain INPUT (policy DROP)\" > /dev/null; then <del> echo \"Add rules to accept all inbound TCP/UDP packets\" </del> <ins> echo \"Add rules to accept all inbound TCP/UDP/ICMP packets\" </ins> iptables -A INPUT -w -p TCP -j ACCEPT iptables -A INPUT -w -p UDP -j ACCEPT <ins> iptables -A INPUT -w -p ICMP -j ACCEPT </ins> fi if iptables -L FORWARD | grep \"Chain FORWARD (policy DROP)\" > /dev/null; then <del> echo \"Add rules to accept all forwarded TCP/UDP packets\" </del> <ins> echo \"Add rules to accept all forwarded TCP/UDP/ICMP packets\" </ins> iptables -A FORWARD -w -p TCP -j ACCEPT iptables -A FORWARD -w -p UDP -j ACCEPT <ins> iptables -A FORWARD -w -p ICMP -j ACCEPT </ins> fi }", "positive_passages": [{"docid": "doc-en-kubernetes-0c9ef3005ed9520787f5bf63165fe010227c899755479cb10a464fa14ceede75", "text": "ref:\nidentified one problem: firewall is not open for icmp in GCI setup. I opened it manually. Still does not work.\nHere are the symptoms: node can ping each other one node, it can ping all pods on it, and vice versa. one node or pod, it can ping all cbr0 gateways(10.X.X.1). pod, it cannot ping but able to curl. It cannot ping any other pod, even on the same bridge, but able to curl.\nMy first thought would be somethings blockign ping. your options are iptables, firewall, icmp is disabled alltogether (sysctl or somewhere in /proc/sys/net/ there should be a setting). Try traceroute and see where it gets to.\nI have a working version now. GCI setup icmp ACCEPT rules in INPUT chain of filter table. But not in OUTPUT and FORWARD chain.\nIn summary, 2 problems: is not opened for icmp is filtering icmp on FORWARD chain. ACCEPT on INPUT chain is not enough Will submit a fix\nGreat detective work, Is this a ping-specific problem, or are there going to be problems with other types of outgoing traffic from pods on GCI as well?\nI do not see any problem for udp/tcp traffic so far. e2e tests already covers lots of them. Unfortunately, no e2e covers ping tests and GCI happens to filter it.\nWe should add a test in networking suite for ping.\nIs this missing a milestone 1.3?", "commid": "kubernetes_issue_27059", "tokennum": 325}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c8bcc7042b38357d7109a141bb451b4a21562314f08d0d74c22a791455b5500c", "query": "return result, nil } <del> // logPluginScores adds summarized plugin score logging. The goal of this block is to show the highest scoring plugins on // each node, and the average score for those plugins across all nodes. func logPluginScores(nodes []*v1.Node, scoresMap framework.PluginToNodeScores, pod *v1.Pod) { totalPluginScores := make(map[string]int64) for j := range scoresMap { for i := range nodes { totalPluginScores[j] += scoresMap[j][i].Score } } // Build a map of Nodes->PluginScores on that node nodeToPluginScores := make(framework.PluginToNodeScores, len(nodes)) for _, node := range nodes { nodeToPluginScores[node.Name] = make(framework.NodeScoreList, len(scoresMap)) } // Convert the scoresMap (which contains Plugins->NodeScores) to the Nodes->PluginScores map for plugin, nodeScoreList := range scoresMap { for _, nodeScore := range nodeScoreList { klog.V(10).InfoS(\"Plugin scored node for pod\", \"pod\", klog.KObj(pod), \"plugin\", plugin, \"node\", nodeScore.Name, \"score\", nodeScore.Score) nodeToPluginScores[nodeScore.Name] = append(nodeToPluginScores[nodeScore.Name], framework.NodeScore{Name: plugin, Score: nodeScore.Score}) } } for node, scores := range nodeToPluginScores { // Get the top 3 scoring plugins for each node sort.Slice(scores, func(i, j int) bool { return scores[i].Score > scores[j].Score }) var topScores []pluginScores for _, score := range scores { pluginScore := pluginScores{ Plugin:           score.Name, Score:            score.Score, AverageNodeScore: float64(totalPluginScores[score.Name]) / float64(len(nodes)), } topScores = append(topScores, pluginScore) if len(topScores) == 3 { break } } klog.InfoS(\"Top 3 plugins for pod on node\", \"pod\", klog.KObj(pod), \"node\", node, \"scores\", topScores, ) } } </del> // NewGenericScheduler creates a genericScheduler object. func NewGenericScheduler( cache internalcache.Cache,", "positive_passages": [{"docid": "doc-en-kubernetes-008ca2b69bf6f84855aa7fc74e613d0733365e6cd47dcc25c8f18519fbaaf463", "text": "Scheduler throughput drops significantly in http://perf- ! After , seems to be the curlspirit.\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/priority critical-urgent /sig scheduling /sig scalability", "commid": "kubernetes_issue_99913", "tokennum": 125}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c900ec7ec60d5756cd08c9e3b96eb625dc6fffe4b21258558baae5d8b1d5a196", "query": "// Returns true if and only if changes were made // If the security group no longer exists, will return (false, nil) func (c *Cloud) removeSecurityGroupIngress(securityGroupID string, removePermissions []*ec2.IpPermission) (bool, error) { <ins> // We do not want to make changes to the Global defined SG if securityGroupID == c.cfg.Global.ElbSecurityGroup { return false, nil } </ins> group, err := c.findSecurityGroup(securityGroupID) if err != nil { glog.Warningf(\"Error retrieving security group: %q\", err)", "positive_passages": [{"docid": "doc-en-kubernetes-d6a2e132f72678770d8d41e08acf9f7359a4b887e33d930dbbc18ea7ecc9db7e", "text": "/kind bug What happened: When setting an elbSecurityGroup in for AWS, and deploying multiple services with differing ports, then the security group rules flap in AWS, causing services to become inaccessible (only one will be correctly configured at a time). What you expected to happen: I expect that the configured elbSecurityGroup's rules will not be touched at all. It must be pre-configured to permit access. Alternatively, all ports for all services are queried and managed together. How to reproduce it (as minimally and precisely as possible): See above. Anything else we need to know?: Most people are not running large clusters which may hit the AWS limits, so they won't use this option, nor see this issue. Environment: Kubernetes version (use ): 1.7.1 Cloud provider or hardware configuration**: AWS OS (e.g. from /etc/os-release): CentOS 7 Kernel (e.g. ): 4.10.13-1-ARCH Install tools: Custom Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig aws\nThis is fixed by", "commid": "kubernetes_issue_50105", "tokennum": 331}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c91e4137c7d9737305af34484f9a0c277d1a4dea6ec1cb13eb22c1ce0b04f932", "query": "// pod stats api summarizes ephemeral storage usage (container, emptyDir, host[etc-hosts, logs]) podEphemeralStorageTotalUsage := &resource.Quantity{} <del> if podStats.EphemeralStorage != nil { </del> <ins> if podStats.EphemeralStorage != nil && podStats.EphemeralStorage.UsedBytes != nil { </ins> podEphemeralStorageTotalUsage = resource.NewQuantity(int64(*podStats.EphemeralStorage.UsedBytes), resource.BinarySI) } podEphemeralStorageLimit := podLimits[v1.ResourceEphemeralStorage]", "positive_passages": [{"docid": "doc-en-kubernetes-673017a5e6e7ba59bdbbe8f10c13b378c1b56adec73e9d5f13b02c9f080d522d", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: ! What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.20.1 Cloud provider or hardware configuration: OS (e.g: ): 7 Kernel (e.g. ): Linux zsm-test-2 3.10.0-1160.11.1.el7.x8664 SMP Fri Dec 18 16:34:56 UTC 2020 x8664 x8664 x8664 GNU/Linux Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig node\nDo you know how to reproduce this problem?\nYes, can reproduce the problem stably, but the steps are a little complicated.\n/triage accepted", "commid": "kubernetes_issue_98260", "tokennum": 230}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c92efd831dfc8f1c1ca1b3e7d2129fb1cb25d227f6a631a6cb882fa8a1ab01b5", "query": "if err != nil { klog.Warningf(\"error looking for nvme volume %q: %v\", volumeID, err) } else if nvmePath != \"\" { <ins> if partition != \"\" { nvmePath = nvmePath + nvmeDiskPartitionSuffix + partition } </ins> devicePaths = append(devicePaths, nvmePath) } }", "positive_passages": [{"docid": "doc-en-kubernetes-d5a9e8b7bbc510dc155bb81dd6aed03e6a233b66a01ab8a13237a98090288309", "text": "When using a AWS EBS PV or on-line volume with a partition on a Nitro machine, the volume is available as NVMe device. Kubelet is not able to format & mount the partition: It seems to me that AWS EBS volume plugin does not support partitions at all. The partition is mounted. Using an in-line volume with this pod:\n/sig storage /sig cloud-provider /area provider/aws\n/triage accepted", "commid": "kubernetes_issue_100499", "tokennum": 100}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c94ce83b6046290c5e3ee283fb853db18cf054c0a3dc060fd24afeee55f9a5f1", "query": "// back to the caller. in.Spec.InitContainers = values // Call defaulters explicitly until annotations are removed <del> for i := range in.Spec.InitContainers { c := &in.Spec.InitContainers[i] SetDefaults_Container(c) </del> <ins> tmpPod := &Pod{ Spec: PodSpec{ HostNetwork:    in.Spec.HostNetwork, InitContainers: values, }, </ins> } <ins> SetObjectDefaults_Pod(tmpPod) in.Spec.InitContainers = tmpPod.Spec.InitContainers </ins> } // If there is a beta annotation, copy to alpha key. // See commit log for PR #31026 for why we do this.", "positive_passages": [{"docid": "doc-en-kubernetes-c7797df648733fdf9e156246e323d8c03549ac9a3ca2ad30e283629a87abe7ee", "text": "What happened: kubelet doesn't seem to be able to manage containers started with CRI-O any more I'm testing kubelet + CRI-O on an Ubuntu 18.04 server installation, inside a qemu/kvm VM managed by Vagrant (see ), in order to be able to test k8s + KubeVirt + KataContainers, which are all compatible with CRI-O kubelet will obsess on starting new containers, which looks like and endless process, and the cluster never gets ready. For instance here are some syslogs : What you expected to happen: It used to work (see asciinema recording at ) a few days ago, but I fear some recent changes broke it. How to reproduce it (as minimally and precisely as possible): Testing with vagrant up --provider=libvirt on Linux with a clone of that commit: vagrant ssh into the VM and ps -edf f or tail -f /var/log/syslog would do... Anything else we need to know?: Environment: Kubernetes version (use ):Cloud provider or hardware configuration: qemu/kvm VM +OS (e.g: ): Ubuntu 18.04.2 LTS Kernel (e.g. ): Linux kubernetes-vagrant-01 4.15.0-48-generic -Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x8664 x8664 x8664 GNU/Linux Install tools: kubeadm as in Network plugin and version (if this is a network-related bug): Others:\n/sig node\nI can confirm this. If I start cri-o from a systemd service it fails with the above mentioned error message. Starting crio with without systemd works just fine. systemd file:\nThanks for your detailed report :) Just want to do some quick version confirming - you've been using k8s 1.14.1 both when it did and did not work? Any other version changes?\nNot sure for before, when it used to work, but according to the asciinema recording mentioned above (), it seems the same. However, not sure for CRI-O, underlying OS stuff (systemd, kernel, etc.). Sorry.\nI was looking for some information for days. I have exactly the same issue when I use podman + systemd on 18.04.2.", "commid": "kubernetes_issue_77615", "tokennum": 541}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c94ce83b6046290c5e3ee283fb853db18cf054c0a3dc060fd24afeee55f9a5f1", "query": "// back to the caller. in.Spec.InitContainers = values // Call defaulters explicitly until annotations are removed <del> for i := range in.Spec.InitContainers { c := &in.Spec.InitContainers[i] SetDefaults_Container(c) </del> <ins> tmpPod := &Pod{ Spec: PodSpec{ HostNetwork:    in.Spec.HostNetwork, InitContainers: values, }, </ins> } <ins> SetObjectDefaults_Pod(tmpPod) in.Spec.InitContainers = tmpPod.Spec.InitContainers </ins> } // If there is a beta annotation, copy to alpha key. // See commit log for PR #31026 for why we do this.", "positive_passages": [{"docid": "doc-en-kubernetes-dca27e474f7f12153e878b1f27ed663eb17fd42e2832a567b0d652b26f30c566", "text": "It is the same for both 14.15 and 14.18 kernels. Podman without systemd runs fine. Podman with systemd fails at runc with the same error podman[]: open /dev/stderr: no such device or address podman[]: NAME: runc - Open Container Initiative runtime podman[]: runc is a command line client for running applications packaged according to ... podman[]: time=\"2019-05-11T13:04:59-07:00\" level=error msg=\"open /dev/stderr: no such device or addressn\" podman[]: open /dev/stderr: no such device or address\nI've tried to reproduce it on 18.04.2 using Podman from but I am not able to reproduce it. Do you have any reproducer? How did you install Podman?\nI used ceph unit files to run ceph in podman rather than docker. Systemd unit successfully starts docker but fails with podman. I can successfully run the same podman container run command from the command line. How were you trying to replicate this? Can you post your unit file?\nHi, I'am having the same problem with Kubernetes with CRI-O. After joining a second worker node it fails to start flannel. gives the following error: What I've tried: Installing previous version of Kubernetes (from to ) Installing previous version of crio (from to ) Building runc myself from their github page and selecting this in the Running it on Ubunut 18.04.2 Issue: (the one giuseppe linked)\nI wonder if the issue is with systemd and runc. In both cases, crio and podman, I see runc help output which tells me that something is not being passed to runc that it needs.\nI've only used so it is different than your test and you confirmed it works from the CLI for you as well. Could you share your service file so I test it?\nI've tried systemd and cgroupfs but no luck so far.\nso it seems that runc fails to re-open . That seems like a runc issue, as it doesn't really need to reopen it. To fix the failure, you could use something like:\nJust an example.", "commid": "kubernetes_issue_77615", "tokennum": 504}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c94ce83b6046290c5e3ee283fb853db18cf054c0a3dc060fd24afeee55f9a5f1", "query": "// back to the caller. in.Spec.InitContainers = values // Call defaulters explicitly until annotations are removed <del> for i := range in.Spec.InitContainers { c := &in.Spec.InitContainers[i] SetDefaults_Container(c) </del> <ins> tmpPod := &Pod{ Spec: PodSpec{ HostNetwork:    in.Spec.HostNetwork, InitContainers: values, }, </ins> } <ins> SetObjectDefaults_Pod(tmpPod) in.Spec.InitContainers = tmpPod.Spec.InitContainers </ins> } // If there is a beta annotation, copy to alpha key. // See commit log for PR #31026 for why we do this.", "positive_passages": [{"docid": "doc-en-kubernetes-1a33d9e403b3728be8b8de7e79372d00143f16de361084780a7a026e224a4dd2", "text": "I use ceph-ansible to install cluster so it may need to install additional daemons like mon before running mgr but the error, in this case, should be different, [Unit] Description=Ceph Manager [Service] EnvironmentFile=-/etc/environment ExecStartPre=-/usr/bin/podman stop ceph-mgr-storage2n1-la ExecStartPre=-/usr/bin/podman rm ceph-mgr-storage2n1-la ExecStart=/usr/bin/podman run --rm --net=host  --memory=16G  --cpus=4  -v /var/lib/ceph:/var/lib/ceph:z  -v /etc/ceph:/etc/ceph:z  -v /var/run/ceph:/var/run/ceph:z  -v /etc/localtime:/etc/localtime:ro  -e CLUSTER=ceph  -e CEPHDAEMON=MGR  -e CONTAINERIMAGE=  {{ cephmgrdockerextraenv }}  --name=ceph-mgr-storage2n1-la  ExecStopPost=-/usr/bin/podman stop ceph-mgr-storage2n1-la Restart=always RestartSec=10s TimeoutStartSec=120 TimeoutStopSec=15 [Install] WantedBy=multi- delighted <:\nBTW, I projectatomic ppa and used apt-get -y podman to install. My podman version is 1.3.0 Sasha Litvak \u2014 You are receiving this because you commented. Reply to this email directly, view it on GitHub , or mute the thread\nCorrected file.", "commid": "kubernetes_issue_77615", "tokennum": 404}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c94ce83b6046290c5e3ee283fb853db18cf054c0a3dc060fd24afeee55f9a5f1", "query": "// back to the caller. in.Spec.InitContainers = values // Call defaulters explicitly until annotations are removed <del> for i := range in.Spec.InitContainers { c := &in.Spec.InitContainers[i] SetDefaults_Container(c) </del> <ins> tmpPod := &Pod{ Spec: PodSpec{ HostNetwork:    in.Spec.HostNetwork, InitContainers: values, }, </ins> } <ins> SetObjectDefaults_Pod(tmpPod) in.Spec.InitContainers = tmpPod.Spec.InitContainers </ins> } // If there is a beta annotation, copy to alpha key. // See commit log for PR #31026 for why we do this.", "positive_passages": [{"docid": "doc-en-kubernetes-bae004f13a06f51a77aaeb8de64c7434d457cced5ee158b56a68659aa46bb958", "text": "[Unit] Description=Ceph Manager [Service] EnvironmentFile=-/etc/environment ExecStartPre=-/usr/bin/podman stop ceph-mgr-storage2n1-la ExecStartPre=-/usr/bin/podman rm ceph-mgr-storage2n1-la ExecStart=/usr/bin/podman run --rm --net=host  --memory=16G  --cpus=4  -v /var/lib/ceph:/var/lib/ceph:z  -v /etc/ceph:/etc/ceph:z  -v /var/run/ceph:/var/run/ceph:z  -v /etc/localtime:/etc/localtime:ro  -e CLUSTER=ceph  -e CEPHDAEMON=MGR  -e CONTAINERIMAGE=  --name=ceph-mgr-storage2n1-la  ExecStopPost=-/usr/bin/podman stop ceph-mgr-storage2n1-la Restart=always RestartSec=10s TimeoutStartSec=120 TimeoutStopSec=15 [Install] WantedBy=multi- Giuseppe Scrivano <:\nWould it have an effect system wide? Can I add it to a unit file or unit override instead? Giuseppe Scrivano <:\nyes, I think it is better to add it only to the unit file\nWhy would runc work outside of systemd? And if it needs stderr, giving it Null in settings will redirect stderr to Null I presume? On Tue, May 14, 2019, 9:46 AM Giuseppe Scrivano <:\nRunning into same issues on Ubuntu 18.04.2 using cri-o-1.13 via PPA.\nPR here: opencontainers/runc\nUntil it is avaialble with project atomic and such, can I use a null workaround? Giuseppe Scrivano <:\nyes, but you will lose anything written to stderr. You could probably also use a file, like\nWhat about actually mounting dev and using /dev/stderr ? On Tue, May 14, 2019, 3:11 PM Giuseppe Scrivano <:\nis a symlink to . It is present, the issue here is that is a socket. The fix for runc got merged, could you use an updated runc?\nI tried apt update/upgrade and restarting crio, but I'm still getting the issue.", "commid": "kubernetes_issue_77615", "tokennum": 570}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c94ce83b6046290c5e3ee283fb853db18cf054c0a3dc060fd24afeee55f9a5f1", "query": "// back to the caller. in.Spec.InitContainers = values // Call defaulters explicitly until annotations are removed <del> for i := range in.Spec.InitContainers { c := &in.Spec.InitContainers[i] SetDefaults_Container(c) </del> <ins> tmpPod := &Pod{ Spec: PodSpec{ HostNetwork:    in.Spec.HostNetwork, InitContainers: values, }, </ins> } <ins> SetObjectDefaults_Pod(tmpPod) in.Spec.InitContainers = tmpPod.Spec.InitContainers </ins> } // If there is a beta annotation, copy to alpha key. // See commit log for PR #31026 for why we do this.", "positive_passages": [{"docid": "doc-en-kubernetes-a9af1b8339c2af3d5a8899da2b8916e4bc8194e1229dc4a9dc77c862af07f4a9", "text": "Could it be that crio's runc is not updated yet? Edit Build new runc from and it is working now. Think crio hasn't updated it yet with their repository.\nI'm running this version from PPA repo for ubuntu and it fails: could you point to version/commit or whatever helps identify the fixed version/snapshot ? Thanks in advance.\nat the moment it is only fixed upstream. You'd need to build runc manually\nIs there a version of the package on ppa we can downgrade to? On Wed, May 15, 2019, 4:35 AM Giuseppe Scrivano <:\ncould we update the runc version in the PPA repo?\nThank you. I seem them built but nut pushed to ppa yet.\nshould be available now.. let me know..\ncri-o-runc (1.0.0-rc6-1~dev~ubuntu18.04~ppa42) bionic; urgency=medium autobuilt -- Lokesh Mandvekar (Bot) <, 15 May 2019 16:54:40 +0000\nThank you, everyone, for a quick turn around. Quick testing showed that fix is working, but more testing is needed. Lokesh Mandvekar <:\nI confirm my initial tests with seem to confirm the regression is fixed. Many thanks\nI also confirm the fix working for podman. Olivier Berger <:", "commid": "kubernetes_issue_77615", "tokennum": 305}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c94ce83b6046290c5e3ee283fb853db18cf054c0a3dc060fd24afeee55f9a5f1", "query": "// back to the caller. in.Spec.InitContainers = values // Call defaulters explicitly until annotations are removed <del> for i := range in.Spec.InitContainers { c := &in.Spec.InitContainers[i] SetDefaults_Container(c) </del> <ins> tmpPod := &Pod{ Spec: PodSpec{ HostNetwork:    in.Spec.HostNetwork, InitContainers: values, }, </ins> } <ins> SetObjectDefaults_Pod(tmpPod) in.Spec.InitContainers = tmpPod.Spec.InitContainers </ins> } // If there is a beta annotation, copy to alpha key. // See commit log for PR #31026 for why we do this.", "positive_passages": [{"docid": "doc-en-kubernetes-c1c167f97d0d68a2d507d0d919d58cd680ff8ed576e3225c7b24d703a964bd61", "text": "<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.--Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see ): No What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): initContainers imagePullPolicy initContainers required value Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT <!-- If this is a BUG REPORT, please: Fill in as much of the template below as you can. If you leave out information, we can't help you as well. If this is a FEATURE REQUEST, please: Describe in detail the feature/behavior/change you'd like to see. In both cases, be ready for followup questions, and please respond in a timely manner. If we can't reproduce a bug or think a feature already exists, we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why. --Kubernetes version (use ): Environment: Cloud provider or hardware configuration: GCE OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: cluster/kube- Others: What happened: When trying to create either a ReplicaSet or Replication Controller whose Pod template contains an Init Container, the validation fails saying is a required value. What you expected to happen: The create should succeed and the Init Container should receive a default . How to reproduce it (as minimally and precisely as possible): Try to create either of the following: ReplicaSet Replication Controller Anything else do we need to know: If I add to the Init Container in the ReplicaSet or Replication Controller Pod template, the create succeeds. When I create an Init Container without in a StatefulSet Pod template, it succeeds. When I create an Init Container without in a bare Pod, it succeeds:\nLooks like defaulting not being applied on server? That is probably due to removing defaulting from convert. Surprised we didn't catch this earlier\nSome values still not being defaulted\n, I'm going to create a PR if none works on it.\nWe decode from bytes, set defaults and then convert; but for init containers, we delay the decode from \"decode phase\" to \"convert phase\" at .", "commid": "kubernetes_issue_38542", "tokennum": 524}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c94ce83b6046290c5e3ee283fb853db18cf054c0a3dc060fd24afeee55f9a5f1", "query": "// back to the caller. in.Spec.InitContainers = values // Call defaulters explicitly until annotations are removed <del> for i := range in.Spec.InitContainers { c := &in.Spec.InitContainers[i] SetDefaults_Container(c) </del> <ins> tmpPod := &Pod{ Spec: PodSpec{ HostNetwork:    in.Spec.HostNetwork, InitContainers: values, }, </ins> } <ins> SetObjectDefaults_Pod(tmpPod) in.Spec.InitContainers = tmpPod.Spec.InitContainers </ins> } // If there is a beta annotation, copy to alpha key. // See commit log for PR #31026 for why we do this.", "positive_passages": [{"docid": "doc-en-kubernetes-69dbac4fd7f4ee2d4feb0af6994cc2f74e65b4d3465b8e0c7014cfb5909cea9b", "text": "The defaults has been handled for initContainer at . /cc I'm working to find a solution for that; if any suggestion, please let me know.\nWould this bug affect the deletion of jobs with an init-container? I ran into this bug and adjusted my manifest to add the pull policy to the init-container. However, I now cannot delete said job claiming a field is immutable. Example:\n, not sure now. Let me check it,\nSame error here with version 1.5.1, 1.5.2 The Job \"grafana-import-dashboards\" is invalid: [0].imagePullPolicy: Required value With this setup: kubectl apply -f monitoring Not working even if I specify a pullpolicy in the yaml. If I roll back to 1.4.7, it is working. Thank you. Greg.\nany updates on a PR to address this issue? Is anyone from able to pick this issue up otherwise?\n, here's the latest status: there's is a PR to generate for each Object (), it works for Object (Pod, Job) now but List; I'm working to make it generating for List.\nWhy would you need List to work? No client side logic should be decoding lists except as a generic submission.\nThe List tests are failed in . There's no for List, so no code to decode init-container annotation, e.g. of should call 's recursively.\nThanks for the update\n+1\nAny update on this? I still getting this issue with the last version of 1.5.3 on GKE?\nping for the comments? should we merge the PR for 1.5?\n, there's a PR () that handled that issue; but we're discussing not to merge it because initContainers had been moved to fields, and fields is the recommended way to use since 1.6. But I'd like to get & 's comments on 1.5.\nThis is still an issue in 1.5.3 when using annotations: Without the deployment would not be accepted\nping & :).\ni dont think this is fixed in 1.5 I just encountered this bug on 1.5.3\n, yes, the PR is NOT merged to any branch, so the issue is still here. I'll create a PR for 1.5.\nHi Anyone help this issue.", "commid": "kubernetes_issue_38542", "tokennum": 520}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c94ce83b6046290c5e3ee283fb853db18cf054c0a3dc060fd24afeee55f9a5f1", "query": "// back to the caller. in.Spec.InitContainers = values // Call defaulters explicitly until annotations are removed <del> for i := range in.Spec.InitContainers { c := &in.Spec.InitContainers[i] SetDefaults_Container(c) </del> <ins> tmpPod := &Pod{ Spec: PodSpec{ HostNetwork:    in.Spec.HostNetwork, InitContainers: values, }, </ins> } <ins> SetObjectDefaults_Pod(tmpPod) in.Spec.InitContainers = tmpPod.Spec.InitContainers </ins> } // If there is a beta annotation, copy to alpha key. // See commit log for PR #31026 for why we do this.", "positive_passages": [{"docid": "doc-en-kubernetes-cd1dc8216bffde40e45195a0aceb1bbd0c560296ad557f563dafcf3df89eeea5", "text": "#cat mongo- apiVersion: v1 kind: Pod metadata: labels: name: mongo-svc-a name: mongo-deployment spec: replicas: 1 template: metadata: labels: name: mongo spec: containers: image: mongo name: mongo ports: name: mongo containerPort: hostPort: volumeMounts: mountPath: \"/data/db\" name: mongopv volumes: name: mongopv persistentVolumeClaim: claimName: mongopvc When i want create mongo db container by using this file folowing error is occured. The Pod \"mongo-deployment\" is invalid:spec.containers: Required value\n, it seems there're two here, please remove the first one and have a try.\nHi my kubectl binary is configured at ubuntu 16.04 machine.", "commid": "kubernetes_issue_38542", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c94ce83b6046290c5e3ee283fb853db18cf054c0a3dc060fd24afeee55f9a5f1", "query": "// back to the caller. in.Spec.InitContainers = values // Call defaulters explicitly until annotations are removed <del> for i := range in.Spec.InitContainers { c := &in.Spec.InitContainers[i] SetDefaults_Container(c) </del> <ins> tmpPod := &Pod{ Spec: PodSpec{ HostNetwork:    in.Spec.HostNetwork, InitContainers: values, }, </ins> } <ins> SetObjectDefaults_Pod(tmpPod) in.Spec.InitContainers = tmpPod.Spec.InitContainers </ins> } // If there is a beta annotation, copy to alpha key. // See commit log for PR #31026 for why we do this.", "positive_passages": [{"docid": "doc-en-kubernetes-7c77a1e7ea84d582b899fa6b8d7216504334c47e064fb8eaad5c523c3bc66a32", "text": "NAME LABELS STATUS 10.1 Ready,SchedulingDisabled 10.2 10.1.10.2 Ready 10.3 Ready apiVersion: v1 kind: Node metadata: creationTimestamp: 2017-03-03T14:41:52Z labels: 10.1.10.1 name: 10.1.10.1 resourceVersion: \"\" selfLink: /api/v1/nodes/10.1.10.1 uid: -001f-11e7-8e83- spec: externalID: 10.1.10.1 status: addresses: address: 10.1.10.1 type: LegacyHostIP address: 10.1.10.1 type: InternalIP capacity: cpu: \"2\" memory: 4041352Ki pods: \"110\" conditions: lastHeartbeatTime: 2017-04-05T18:58:42Z lastTransitionTime: 2017-03-03T14:41:52Z message: kubelet has sufficient disk space available reason: KubeletHasSufficientDisk status: \"False\" type: OutOfDisk lastHeartbeatTime: 2017-04-05T18:58:42Z lastTransitionTime: 2017-04-05T15:27:52Z message: kubelet is posting ready status reason: KubeletReady status: \"True\" type: Ready nodeInfo: bootID: -6124-4ac7-ab96- containerRuntimeVersion: docker://1.12.6 kernelVersion: 4.9.16-coreos-r1 kubeProxyVersion: v1.2.4+coreos.1 kubeletVersion: v1.2.4+coreos.1 machineID: osImage: Container Linux by CoreOS 1298.7.0 (Ladybug) systemUUID: C3FD9852-2DFB-21F4-CE07-2597A746D99D When i create pv for creation pod is shows pv is pending. Please give any suggestions.....\nIs there solution of this problem with version 2.7. Still facing the same. what exactly expectation of helm upgrade --install relname chartsdirectory is is expected to work on first time installation in case with CI/CD Pipelines.", "commid": "kubernetes_issue_38542", "tokennum": 511}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c9667454a72dbef147eaf74d68005f5c9c6db06ba9b7460f165ea628a3bdcdbc", "query": "t.Errorf(\"%s: expect no error when applying json patch, but got %v\", test.name, err) continue } <del> if err.Error() != test.expectedError { </del> <ins> if !strings.Contains(err.Error(), test.expectedError) { </ins> t.Errorf(\"%s: expected error %v, but got %v\", test.name, test.expectedError, err) } if test.expectedErrorType != apierrors.ReasonForError(err) {", "positive_passages": [{"docid": "doc-en-kubernetes-984aaf2876c4d4651f6765b291626bccfb7d6364087d7ebb11c97e2832c59ee5", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Below k8s UT fail when run with master-golang. TestCheckpointStateRestore/RestorecheckpointwithinvalidJSON error:=== RUN TestCheckpointStateRestore/RestorecheckpointwithinvalidJSON I1124 05:38:14. ] [cpumanager] initializing new in-memory state store unexpected error while creatng checkpointState: could not restore state from checkpoint: json: unexpected end of JSON input, please drain this node and delete the CPU manager checkpoint file \"/tmp/cpumanagerstatetest479660663/cpumanagercheckpointtest\" before restarting Kubelet --- FAIL: TestCheckpointStateRestore/RestorecheckpointwithinvalidJSON (0.00s) TestStrategicMergePatchInvalid error:=== RUN TestStrategicMergePatchInvalid expected \"invalid character 'b' looking for beginning of value\", got \"json: invalid character 'b' looking for beginning of value\" --- FAIL: TestStrategicMergePatchInvalid (0.00s) TestJSONPatch error:=== RUN TestJSONPatch invalid-syntax: expected error invalid character 'i' looking for beginning of value, but got json: invalid character 'i' looking for beginning of value --- FAIL: TestJSONPatch (0.00s) TestV4ErrorDecoder expandless error:=== RUN TestV4ErrorDecoder wrong error for message \"{\": want=\"error stream protocol error: unexpected end of JSON input in \"{\"\", got=\"error stream protocol error: json: unexpected end of JSON input in \"{\"\" --- FAIL: TestV4ErrorDecoder (0.00s What you expected to happen: The tests should pass with no error. How to reproduce it (as minimally and precisely as possible): a stable version of golang installed master go from upstream git clone cd go/src cd ../.. cp -r ./go /usr/local export PATH=/usr/local/go/bin:$PATH kubernetes repo and run the unit tests. () Anything else we need to know?: These failures are occurring due to mismatch of error messages between upstream go and the k8s tests.", "commid": "kubernetes_issue_96853", "tokennum": 597}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c9667454a72dbef147eaf74d68005f5c9c6db06ba9b7460f165ea628a3bdcdbc", "query": "t.Errorf(\"%s: expect no error when applying json patch, but got %v\", test.name, err) continue } <del> if err.Error() != test.expectedError { </del> <ins> if !strings.Contains(err.Error(), test.expectedError) { </ins> t.Errorf(\"%s: expected error %v, but got %v\", test.name, test.expectedError, err) } if test.expectedErrorType != apierrors.ReasonForError(err) {", "positive_passages": [{"docid": "doc-en-kubernetes-d960907779eeb813df14a2ea4a00c97f52784ded937dbf1c71e5b05391843c78", "text": "There is an addition \"json:\" prefix to SyntaxError messages after this below commit: Environment: Kubernetes version (use ): latest source code from upstream Cloud provider or hardware configuration: OS (e.g: ): \"CentOS Linux 8 (Core)\" Kernel (e.g. ): Linux rajalakshmi-workspace 4.18.0-193.19.1.el82.ppc64le SMP Mon Sep 14 14:48:04 UTC 2020 ppc64le ppc64le ppc64le GNU/Linux Install tools: [root go]# go version go version devel + Fri Nov 20 00:54:43 2020 +0000 linux/ppc64le [root go]# Network plugin and version (if this is a network-related bug): Others:\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig testing\nwill fix it in Go 1.16 as release-blocker.\nI would fix the test here to be more tolerant. exact string matches on error messages aren't really an API\u2026 I would not expect that to block the golang release\nAgree too, we can think about having a substring match to avoid these issues instead!\n/assign Lets see if we can fix this in the k8s tests", "commid": "kubernetes_issue_96853", "tokennum": 352}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c9a3a6102eaf8d4fc4590a2a542a0fa31e35266c9f246998ef356e9ab2336868", "query": "discoveryv1beta1 \"k8s.io/api/discovery/v1beta1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/labels\" <ins> \"k8s.io/apimachinery/pkg/runtime/schema\" </ins> \"k8s.io/apimachinery/pkg/types\" \"k8s.io/apimachinery/pkg/util/intstr\" \"k8s.io/apimachinery/pkg/util/sets\"", "positive_passages": [{"docid": "doc-en-kubernetes-c5b2d72b2e785256d7a2577807fdbd43ef000a4da594f69c949ac55e4186d114", "text": "[x] two weeks soak end date : 18 March 2021 According to this APIsnoop query, there are still some remaining RESOURCENAME endpoints which are untested. with this query you can filter untested endpoints by their category and eligiblity for conformance. e.g below shows a query to find all conformance eligible untested,stable,core endpoints Note: Community feedback for the e2e test has lead to a number of improvements including extending the test coverage to all outstanding endpoints listed above. As each endpoint is tested a &rsquo;watch&rsquo; confirms that the result is valid before testing the next endpoint. readCoreV1NamespacedServiceStatus (get /status) patchCoreV1NamespacedServiceStatus (patch /status) replaceCoreV1NamespacedServiceStatus (update /status) patchCoreV1NamespacedService Create a Service with a static label Patch the Service with a new label and updated data Get the Service to ensure it&rsquo;s patched Upate the Service with a new label and updated data Get the Service to ensure it&rsquo;s updated Delete Namespaced Service via a Collection with a LabelSelector This query by apisnoop shows that all outstanding endpoints as list at the start of this document have been hit by the e2e test. Note that the results do include other service endpoints that have been addressed in other conformance tests. If a test with these calls gets merged, test coverage will go up by 4 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance\nCan you please review the proposed test and advise if we could go ahead with a PR\n/assign\nIt looks like it's patching metadata and spec but not status?\nIssues 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\n/remove-lifecycle stale\nI've been retesting this mock test and apisnoop does log as been hit. From my testing below it looks like the patchStatus is working as expected or have I missed something?", "commid": "kubernetes_issue_94867", "tokennum": 517}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c9a3a6102eaf8d4fc4590a2a542a0fa31e35266c9f246998ef356e9ab2336868", "query": "discoveryv1beta1 \"k8s.io/api/discovery/v1beta1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/labels\" <ins> \"k8s.io/apimachinery/pkg/runtime/schema\" </ins> \"k8s.io/apimachinery/pkg/types\" \"k8s.io/apimachinery/pkg/util/intstr\" \"k8s.io/apimachinery/pkg/util/sets\"", "positive_passages": [{"docid": "doc-en-kubernetes-6c98fb90bee2cd0d2fc404edc784deab934fddaa81022ed1883862c51f5dae6d", "text": "Using the following code before the patch request Gives this response Then after running the patch ServiceStatus Then running The response shows the patched changes.\nDuring the Conformance Meeting on 12th of January 2021, reviewed approach with Clayton, and we will start on the test PR this week!\n/reopen\nReopened this issue. <detailsIn response to : /reopen </details\n/triage accepted", "commid": "kubernetes_issue_94867", "tokennum": 79}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c9b8a9bb7894344fd43fc924f928fa06bf8a29410686aec28f9020eef9dd3ec1", "query": "return nil, \"\", \"\", err } <del> testSocketFile := filepath.Join(volpath, \"mount_test.sock\") _, err := net.Listen(\"unix\", testSocketFile) return mounts, volpath, testSocketFile, err </del> <ins> socketFile, socketCreateError := createSocketFile(volpath) return mounts, volpath, socketFile, socketCreateError </ins> }, expectError: false, },", "positive_passages": [{"docid": "doc-en-kubernetes-ea06bb5e10f9c1a3c6e6bdd4b05e49a63cf7c6313178f3d65784c243007cbe65", "text": "Subpath unix socket tests can flake because of long socket path. On Linux the path limit should be 108 chars or less. /sig storage", "commid": "kubernetes_issue_61844", "tokennum": 31}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c9ceae74e17328601fb1e6020be8b0556b408a2e12695c8692377b7e1d328f05", "query": "const ( gcePDDetachTimeout  = 10 * time.Minute gcePDDetachPollTime = 10 * time.Second <del> nodeStatusTimeout   = 5 * time.Minute </del> <ins> nodeStatusTimeout   = 10 * time.Minute </ins> nodeStatusPollTime  = 1 * time.Second maxReadRetry        = 3 )", "positive_passages": [{"docid": "doc-en-kubernetes-917c5aacdf98ee16adcfe96e5370eb2e1e342a70bc45d825e7dc562ccfb7cd09", "text": "Since 2 days ago, the test is becoming more and more flaky, and one of the examples is: https://k8s-\nThere are no sig labels on this issue. Please by:<br(1) mentioning a sig: <bre.g., for API Machinery<br(2) specifying the label manually: <bre.g., for sig/scalability<br<brNote: method (1) will trigger a notification to the team. You can find the team list and label list\nplease triage this one. Currently I put it as the release blocker, and please feel free to remove that if you think it is not. Thanks!\nThe test deletes the node, and at the end, waits 5 minutes for the node to become ready, but it timed out. cc\nThe test logic hasn't changed after I last modified it, so the test deletes the node through gcloud, and the instance should be restarted automatically by GCE because it's part of an instance template. The likely possibility, as pointed out, is that another change made node discovery take longer, so extending the timeout would be enough. The very unlikely possibility is there's a problem discovering brand new instances.", "commid": "kubernetes_issue_48008", "tokennum": 264}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c9dd7224c4794a6ffa480be98594fc8517bb6706ce23796fdcd343e92c883581", "query": "Description: The discovery.k8s.io API group MUST exist in the /apis discovery document. The discovery.k8s.io/v1 API group/version MUST exist in the /apis/discovery.k8s.io discovery document. The endpointslices resource MUST exist in the /apis/discovery.k8s.io/v1 discovery document. <del> API Server should create self referential Endpoints and EndpointSlices named \"kubernetes\" in the default namespace. </del> <ins> The cluster MUST have a service named \"kubernetes\" on the default namespace referencing the API servers. The \"kubernetes.default\" service MUST have Endpoints and EndpointSlices pointing to each API server instance. </ins> */ framework.ConformanceIt(\"should have Endpoints and EndpointSlices pointing to API Server\", func() { namespace := \"default\" name := \"kubernetes\" <ins> // verify \"kubernetes.default\" service exist _, err := cs.CoreV1().Services(namespace).Get(context.TODO(), name, metav1.GetOptions{}) framework.ExpectNoError(err, \"error obtaining API server \"kubernetes\" Service resource on \"default\" namespace\") // verify Endpoints for the API servers exist </ins> endpoints, err := cs.CoreV1().Endpoints(namespace).Get(context.TODO(), name, metav1.GetOptions{}) <del> framework.ExpectNoError(err, \"error creating Endpoints resource\") if len(endpoints.Subsets) != 1 { framework.Failf(\"Expected 1 subset in endpoints, got %d: %#v\", len(endpoints.Subsets), endpoints.Subsets) </del> <ins> framework.ExpectNoError(err, \"error obtaining API server \"kubernetes\" Endpoint resource on \"default\" namespace\") if len(endpoints.Subsets) == 0 { framework.Failf(\"Expected at least 1 subset in endpoints, got %d: %#v\", len(endpoints.Subsets), endpoints.Subsets) </ins> } <del> endpointSubset := endpoints.Subsets[0] endpointSlice, err := cs.DiscoveryV1().EndpointSlices(namespace).Get(context.TODO(), name, metav1.GetOptions{}) framework.ExpectNoError(err, \"error creating EndpointSlice resource\") if len(endpointSlice.Ports) != len(endpointSubset.Ports) { framework.Failf(\"Expected EndpointSlice to have %d ports, got %d: %#v\", len(endpointSubset.Ports), len(endpointSlice.Ports), endpointSlice.Ports) </del> <ins> // verify EndpointSlices for the API servers exist endpointSliceList, err := cs.DiscoveryV1().EndpointSlices(namespace).List(context.TODO(), metav1.ListOptions{ LabelSelector: \"kubernetes.io/service-name=\" + name, }) framework.ExpectNoError(err, \"error obtaining API server \"kubernetes\" EndpointSlice resource on \"default\" namespace\") if len(endpointSliceList.Items) == 0 { framework.Failf(\"Expected at least 1 EndpointSlice, got %d: %#v\", len(endpoints.Subsets), endpoints.Subsets) </ins> } <del> numExpectedEndpoints := len(endpointSubset.Addresses) + len(endpointSubset.NotReadyAddresses) if len(endpointSlice.Endpoints) != numExpectedEndpoints { framework.Failf(\"Expected EndpointSlice to have %d endpoints, got %d: %#v\", numExpectedEndpoints, len(endpointSlice.Endpoints), endpointSlice.Endpoints) </del> <ins> if !endpointSlicesEqual(endpoints, endpointSliceList) { framework.Failf(\"Expected EndpointSlice to have same addresses and port as Endpoints, got %#v: %#v\", endpoints, endpointSliceList) </ins> } })", "positive_passages": [{"docid": "doc-en-kubernetes-7f1e6e7766f66194a4a76f7bcbc82118fdef24c779ae808892b54bf44f2870dc", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --E2E test fails. The test is implemented at: I would expect the test pass with these objects in place: AFAIK this fulfills the general requirement of the test that there's a corresponding endpointslice object with same addressing information as is on the endpoint object. IMO the test should rather look for epslice which is owned by the endpoint rather than relying on a hardcoded name. Add flag to kube-apiserver Manually create the endpoint with proper addressing for the api-server epslice \"mirroring\" create new endpointslice with name like --The test fails as it's hardcoded to look for endpointslice named I'm working on a PR to provide a fix proposal Kubernetes version (use ): 1.22.1 Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: k0s Network plugin and version (if this is a network-related bug): kube-router 1.3.1 Others:\n/sig testing\n/remove-sig testing /sig network EndpointSlices are owned by sig network.\n/kind failing-test\n/remove kind-bug /remove kind-failing-test The test is correct, apiserver must generates both endpoint and enpointslices with the special name \"kubernetes\" , that are the backends for the \"kubernetes.default\" service with the IP addresses of the apiservers. This special service \"kubernetes.default\" and its endpoints are used by clients with In-Cluster auto discovery. I think that whatever cluster that is not generating the endpoint and endpointslices for the \"kubernetes.default\" service should not meet Conformance, at least I can't see how automatic in-cluster configuration will work without that ... I only see option used for webhook tests, the other 2 reconcilers always create the endpoints and slices for \"kubernetes.default\" should we clarify the goal of this \"none\" option?\nYes, I do understand this. And in our case this is true, there is a svc called as there is also endpoints object called . This makes the in-cluster discovery work.", "commid": "kubernetes_issue_104612", "tokennum": 531}], "negative_passages": []}
{"query_id": "q-en-kubernetes-c9dd7224c4794a6ffa480be98594fc8517bb6706ce23796fdcd343e92c883581", "query": "Description: The discovery.k8s.io API group MUST exist in the /apis discovery document. The discovery.k8s.io/v1 API group/version MUST exist in the /apis/discovery.k8s.io discovery document. The endpointslices resource MUST exist in the /apis/discovery.k8s.io/v1 discovery document. <del> API Server should create self referential Endpoints and EndpointSlices named \"kubernetes\" in the default namespace. </del> <ins> The cluster MUST have a service named \"kubernetes\" on the default namespace referencing the API servers. The \"kubernetes.default\" service MUST have Endpoints and EndpointSlices pointing to each API server instance. </ins> */ framework.ConformanceIt(\"should have Endpoints and EndpointSlices pointing to API Server\", func() { namespace := \"default\" name := \"kubernetes\" <ins> // verify \"kubernetes.default\" service exist _, err := cs.CoreV1().Services(namespace).Get(context.TODO(), name, metav1.GetOptions{}) framework.ExpectNoError(err, \"error obtaining API server \"kubernetes\" Service resource on \"default\" namespace\") // verify Endpoints for the API servers exist </ins> endpoints, err := cs.CoreV1().Endpoints(namespace).Get(context.TODO(), name, metav1.GetOptions{}) <del> framework.ExpectNoError(err, \"error creating Endpoints resource\") if len(endpoints.Subsets) != 1 { framework.Failf(\"Expected 1 subset in endpoints, got %d: %#v\", len(endpoints.Subsets), endpoints.Subsets) </del> <ins> framework.ExpectNoError(err, \"error obtaining API server \"kubernetes\" Endpoint resource on \"default\" namespace\") if len(endpoints.Subsets) == 0 { framework.Failf(\"Expected at least 1 subset in endpoints, got %d: %#v\", len(endpoints.Subsets), endpoints.Subsets) </ins> } <del> endpointSubset := endpoints.Subsets[0] endpointSlice, err := cs.DiscoveryV1().EndpointSlices(namespace).Get(context.TODO(), name, metav1.GetOptions{}) framework.ExpectNoError(err, \"error creating EndpointSlice resource\") if len(endpointSlice.Ports) != len(endpointSubset.Ports) { framework.Failf(\"Expected EndpointSlice to have %d ports, got %d: %#v\", len(endpointSubset.Ports), len(endpointSlice.Ports), endpointSlice.Ports) </del> <ins> // verify EndpointSlices for the API servers exist endpointSliceList, err := cs.DiscoveryV1().EndpointSlices(namespace).List(context.TODO(), metav1.ListOptions{ LabelSelector: \"kubernetes.io/service-name=\" + name, }) framework.ExpectNoError(err, \"error obtaining API server \"kubernetes\" EndpointSlice resource on \"default\" namespace\") if len(endpointSliceList.Items) == 0 { framework.Failf(\"Expected at least 1 EndpointSlice, got %d: %#v\", len(endpoints.Subsets), endpoints.Subsets) </ins> } <del> numExpectedEndpoints := len(endpointSubset.Addresses) + len(endpointSubset.NotReadyAddresses) if len(endpointSlice.Endpoints) != numExpectedEndpoints { framework.Failf(\"Expected EndpointSlice to have %d endpoints, got %d: %#v\", numExpectedEndpoints, len(endpointSlice.Endpoints), endpointSlice.Endpoints) </del> <ins> if !endpointSlicesEqual(endpoints, endpointSliceList) { framework.Failf(\"Expected EndpointSlice to have same addresses and port as Endpoints, got %#v: %#v\", endpoints, endpointSliceList) </ins> } })", "positive_passages": [{"docid": "doc-en-kubernetes-e7b624ebdf04c04b0fd86ae888848c4f91744879af316f1243574b67dd031473", "text": "Otherwise we'd get much more errors in the conformance instead of this only one... :) In our case we're relying on the endpointslice mirroring to take care of creating the endpointslice object, which makes this test fail as it uses generated \"suffix\" on the object name. I have not dived too deep (yet) into the internals of endpointslices but I fail to see how the endpointslice object name really matters when both svc and endpoint object does have proper name.\noh, this seems interesting then ... who is creating the corresponding endpoint? can you paste a kubectl get endpoints -o yaml?\nthis is how it looks like in my cluster\nIn our case (k0s distro) it's our custom controller that is triggered when the controlplane is configured in HA mode. So this basically sets the api to mode . When our controller runs it has a configured LB address which it resolves to IP address(es) and creates the corresponding EP object. We do NOT create the endpointslice as we rely on the mirroring functionality to let it create and sync it. Here's the object details: Reading the code for API built-in endpoint reconcilers I see they set and create the endpointslice object by themselves. Yes, we could do that too in k0s but I fail to see why the name of the endpointslice object really matters at all.\nI agree the conformance test should not be looking up endpointslice by name. It should be using a label selector of to locate one or more endpointslices and verifying the ports and endpoints across them.\nFair enough, on the good side this also will simplify the KEP from to dual-stack the apiserver you are the expert in this area, can you PTAL at this discussion? /kind failing-test\nhmm the test description explicitly says the name of the object has to be \"kubernetes\", if the name is mandatory the test is correct, otherwise we need to rewrite the test description and talk with conformance people /area conformance\nthe description should be rewritten... the test is enforcing stricter requirements on endpointslices than required/expected\n/triage accepted", "commid": "kubernetes_issue_104612", "tokennum": 469}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ca780b05e3fc995d864f6e55316ac94c61169f24652712d028547a316a3a9729", "query": "\"Only the previous minor version is meaningful, other values will not be allowed. \"+ \"The format is <major>.<minor>, e.g.: '1.16'. \"+ \"The purpose of this format is make sure you have the opportunity to notice if the next release hides additional metrics, \"+ <del> \"rather than being surprised when they are permanently removed in the release after that.\") </del> <ins> \"rather than being surprised when they are permanently removed in the release after that.\"+ \"This parameter is ignored if a config file is specified by --config.\") </ins> fs.StringSliceVar(&o.config.IPVS.ExcludeCIDRs, \"ipvs-exclude-cidrs\", o.config.IPVS.ExcludeCIDRs, \"A comma-separated list of CIDR's which the ipvs proxier should not touch when cleaning up IPVS rules.\") fs.StringSliceVar(&o.config.NodePortAddresses, \"nodeport-addresses\", o.config.NodePortAddresses, <del> \"A string slice of values which specify the addresses to use for NodePorts. Values may be valid IP blocks (e.g. 1.2.3.0/24, 1.2.3.4/32). The default empty string slice ([]) means to use all local addresses.\") </del> <ins> \"A string slice of values which specify the addresses to use for NodePorts. Values may be valid IP blocks (e.g. 1.2.3.0/24, 1.2.3.4/32). The default empty string slice ([]) means to use all local addresses. This parameter is ignored if a config file is specified by --config.\") </ins> fs.BoolVar(&o.CleanupAndExit, \"cleanup\", o.CleanupAndExit, \"If true cleanup iptables and ipvs rules and exit.\") <del> fs.Var(&utilflag.IPVar{Val: &o.config.BindAddress}, \"bind-address\", \"The IP address for the proxy server to serve on (set to '0.0.0.0' for all IPv4 interfaces and '::' for all IPv6 interfaces)\") fs.Var(&utilflag.IPPortVar{Val: &o.config.HealthzBindAddress}, \"healthz-bind-address\", \"The IP address with port for the health check server to serve on (set to '0.0.0.0:10256' for all IPv4 interfaces and '[::]:10256' for all IPv6 interfaces). Set empty to disable.\") fs.Var(&utilflag.IPPortVar{Val: &o.config.MetricsBindAddress}, \"metrics-bind-address\", \"The IP address with port for the metrics server to serve on (set to '0.0.0.0:10249' for all IPv4 interfaces and '[::]:10249' for all IPv6 interfaces). Set empty to disable.\") </del> <ins> fs.Var(&utilflag.IPVar{Val: &o.config.BindAddress}, \"bind-address\", \"The IP address for the proxy server to serve on (set to '0.0.0.0' for all IPv4 interfaces and '::' for all IPv6 interfaces). This parameter is ignored if a config file is specified by --config.\") fs.Var(&utilflag.IPPortVar{Val: &o.config.HealthzBindAddress}, \"healthz-bind-address\", \"The IP address with port for the health check server to serve on (set to '0.0.0.0:10256' for all IPv4 interfaces and '[::]:10256' for all IPv6 interfaces). Set empty to disable. This parameter is ignored if a config file is specified by --config.\") fs.Var(&utilflag.IPPortVar{Val: &o.config.MetricsBindAddress}, \"metrics-bind-address\", \"The IP address with port for the metrics server to serve on (set to '0.0.0.0:10249' for all IPv4 interfaces and '[::]:10249' for all IPv6 interfaces). Set empty to disable. This parameter is ignored if a config file is specified by --config.\") </ins> fs.BoolVar(&o.config.BindAddressHardFail, \"bind-address-hard-fail\", o.config.BindAddressHardFail, \"If true kube-proxy will treat failure to bind to a port as fatal and exit\") fs.Var(utilflag.PortRangeVar{Val: &o.config.PortRange}, \"proxy-port-range\", \"Range of host ports (beginPort-endPort, single port or beginPort+offset, inclusive) that may be consumed in order to proxy service traffic. If (unspecified, 0, or 0-0) then ports will be randomly chosen.\") <del> fs.Var(&o.config.Mode, \"proxy-mode\", \"Which proxy mode to use: 'userspace' (older) or 'iptables' (faster) or 'ipvs' or 'kernelspace' (windows). If blank, use the best-available proxy (currently iptables). If the iptables proxy is selected, regardless of how, but the system's kernel or iptables versions are insufficient, this always falls back to the userspace proxy.\") </del> <ins> fs.Var(&o.config.Mode, \"proxy-mode\", \"Which proxy mode to use: 'userspace' (older) or 'iptables' (faster) or 'ipvs' or 'kernelspace' (windows). If blank, use the best-available proxy (currently iptables). If the iptables proxy is selected, regardless of how, but the system's kernel or iptables versions are insufficient, this always falls back to the userspace proxy.\"+ \"This parameter is ignored if a config file is specified by --config.\") </ins> fs.Var(cliflag.NewMapStringBool(&o.config.FeatureGates), \"feature-gates\", \"A set of key=value pairs that describe feature gates for alpha/experimental features. \"+ <del> \"Options are:n\"+strings.Join(utilfeature.DefaultFeatureGate.KnownFeatures(), \"n\")) </del> <ins> \"Options are:n\"+strings.Join(utilfeature.DefaultFeatureGate.KnownFeatures(), \"n\")+ \"This parameter is ignored if a config file is specified by --config.\") </ins> fs.Int32Var(&o.healthzPort, \"healthz-port\", o.healthzPort, \"The port to bind the health check server. Use 0 to disable.\") fs.MarkDeprecated(\"healthz-port\", \"This flag is deprecated and will be removed in a future release. Please use --healthz-bind-address instead.\") fs.Int32Var(&o.metricsPort, \"metrics-port\", o.metricsPort, \"The port to bind the metrics server. Use 0 to disable.\") fs.MarkDeprecated(\"metrics-port\", \"This flag is deprecated and will be removed in a future release. Please use --metrics-bind-address instead.\") <del> fs.Int32Var(o.config.OOMScoreAdj, \"oom-score-adj\", utilpointer.Int32PtrDerefOr(o.config.OOMScoreAdj, int32(qos.KubeProxyOOMScoreAdj)), \"The oom-score-adj value for kube-proxy process. Values must be within the range [-1000, 1000]\") </del> <ins> fs.Int32Var(o.config.OOMScoreAdj, \"oom-score-adj\", utilpointer.Int32PtrDerefOr(o.config.OOMScoreAdj, int32(qos.KubeProxyOOMScoreAdj)), \"The oom-score-adj value for kube-proxy process. Values must be within the range [-1000, 1000]. This parameter is ignored if a config file is specified by --config.\") </ins> fs.Int32Var(o.config.IPTables.MasqueradeBit, \"iptables-masquerade-bit\", utilpointer.Int32PtrDerefOr(o.config.IPTables.MasqueradeBit, 14), \"If using the pure iptables proxy, the bit of the fwmark space to mark packets requiring SNAT with.  Must be within the range [0, 31].\") fs.Int32Var(o.config.Conntrack.MaxPerCore, \"conntrack-max-per-core\", *o.config.Conntrack.MaxPerCore, \"Maximum number of NAT connections to track per CPU core (0 to leave the limit as-is and ignore conntrack-min).\")", "positive_passages": [{"docid": "doc-en-kubernetes-d25af00145ce02f273723fdbada2e8cd6b506acebe2a7cb4f99e67bf0c6cc038", "text": "Start service with a config file without specifying the argument in the config file, instead, pass the value via the CLI args, the value is just ignored, for example, I have a config file as this, NOTE: I have not specified the in the config file, but give a value for the via the CLI, the proxy mode is still set as after the service is started. The reason for this is that CLI args is parsed before the loading of the config file, if the config file haven't specified the or leave it as empty, then it will be use the default value instead. Two choices from my side, Add a note somewhere, maybe where the option is defined, just say that the CLI args will be ignored when the config file is provided regardless the option is specified in the config file or not (this should be noted for lots of options). Merge the value passed from CLI with the config file if the option has an empty value, but we need to consider the backward compatibility. and check which mode is effective. No response_ vanilla deployment with code in the upstream. <details</details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig network Hey Tim, WDYT? /assign\nHeh, this is a recurrent topic :smile: , you did a great analysis: I think that explains here why merging flags and config overriding defaults is not a desirable option (the whole thread is worth reading) I'm in favor of documenting the behavior\nthanks for showing the earlier thread, I have created a simple PR to document this in the CLI option.", "commid": "kubernetes_issue_107156", "tokennum": 446}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ca9cd6f8dcc200789627ae32e69fe25813de38a4c0fabcb383d5eb602e0d3667", "query": "addrPath := connectionPath + \"/address\" addr, err := io.ReadFile(addrPath) if err != nil { <del> return nil, err </del> <ins> klog.Infof(\"Failed to process connection %s, assuming this connection is unavailable: %s\", dirName, err) continue </ins> } portPath := connectionPath + \"/port\" port, err := io.ReadFile(portPath) if err != nil { <del> return nil, err </del> <ins> klog.Infof(\"Failed to process connection %s, assuming this connection is unavailable: %s\", dirName, err) continue </ins> } persistentAddrPath := connectionPath + \"/persistent_address\" persistentAddr, err := io.ReadFile(persistentAddrPath) if err != nil { <del> return nil, err </del> <ins> klog.Infof(\"Failed to process connection %s, assuming this connection is unavailable: %s\", dirName, err) continue </ins> } persistentPortPath := connectionPath + \"/persistent_port\" persistentPort, err := io.ReadFile(persistentPortPath) if err != nil { <del> return nil, err </del> <ins> klog.Infof(\"Failed to process connection %s, assuming this connection is unavailable: %s\", dirName, err) continue </ins> } // Add entries to the map for both the current and persistent portals", "positive_passages": [{"docid": "doc-en-kubernetes-2bba8e4fb458ddf612a1ae84873c0951878ae27f68765b5b6efc434715382796", "text": "If one target in multipath volume gets down and a pod that uses the volume is deleted and quickly recreated (e.g. by a Deployment), the new pod never starts. How to reproduce it (as minimally and precisely as possible): Deployment with single replica with one multipath iSCSI volume one target (e.g. switch the machine off). Multipath will mark appropriate path as failed: the deployment pod. will quickly start a new pod for the Deployment. new pod will be (or ) forever, What happened: Kubelet tries to WaitForAttach / SetUp volume for the new pod. The volume is still attached. Kubelet goes through all targets and tries to find out if it's logged in or not. Eventually it tries to read of the failed path and that returns error: What you expected to happen: Kubelet assumes that the path is failed / not logged in and tries to recover it. If it fails it continues with multipath with 2 available devices and 1 failed one. IMO, simple instead of will do its job just fine. /assign /sig storage cc for iSCSI expertise\nFix:", "commid": "kubernetes_issue_74305", "tokennum": 238}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cab4995ba49be3ebdc7186ca81362cfa9a86da77e12a189c9ac7b6d4dd101a5f", "query": "var errRequeue = errors.New(\"requeue\") // errPeriodic is a special error instance that functions can return <del> // to request silent instance that functions can return </del> // to request silent retrying at a fixed rate. var errPeriodic = errors.New(\"periodic\")", "positive_passages": [{"docid": "doc-en-kubernetes-e8eec0a3f7a81297ed919db6952e73e9801661fbfe386a524b19b8189beefe88", "text": "When ResourceClaimParameters or ResourceClassParameters fail validation in resource driver during PodSchedulingContext sync loop, the error is visible only in the events of the PodSchedulingContext. The error should be visible on the object that fails validation as well, ResourceClaim or ResourceClass respectively. Creating ResourceClaim with unsupported parameters' values or unsupported No response <details</details<details</details<details</details<details</details<details</details<details</details\n/assign\n/sig node\n/triage accepted\nKEP:", "commid": "kubernetes_issue_121063", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cac3c28f6cbb33dafd0c9bbf1725f3f14e2ab454c004854c9ef666c6cbc84381", "query": "} } } <ins> func TestRCManagerInit(t *testing.T) { // Insert a stable rc into the replication manager's store and make sure // it syncs pods with the apiserver before making any decisions. rc := newReplicationController(2) response := runtime.EncodeOrDie(testapi.Default.Codec(), newPodList(nil, 2, api.PodRunning, rc)) fakeHandler := utiltesting.FakeHandler{ StatusCode:   200, ResponseBody: response, } testServer := httptest.NewServer(&fakeHandler) // TODO: Uncomment when fix #19254 // defer testServer.Close() client := client.NewOrDie(&client.Config{Host: testServer.URL, GroupVersion: testapi.Default.GroupVersion()}) manager := NewReplicationManager(client, controller.NoResyncPeriodFunc, BurstReplicas) manager.rcStore.Store.Add(rc) manager.podStoreSynced = alwaysReady controller.SyncAllPodsWithStore(manager.kubeClient, manager.podStore.Store) fakePodControl := &controller.FakePodControl{} manager.podControl = fakePodControl manager.syncReplicationController(getKey(rc, t)) validateSyncReplication(t, fakePodControl, 0, 0) } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-b0a441a371f8db864bebc11c7303837af71a86244bb0f50ec81fe1d8a09d5c71", "text": "The test is in flaky suite and no one seems to care. We need an owner for this test. cc Last failure log:\ndo you think you can take a look at this?\nThis is happening because of a bad assumption. The assumption is: if the reflector's store is consistent with etcd, the store given back to clients of the framework.Controller is too. I'd really like a general fix applicable to all controllers for this problem, but fixing it just for the RCs is pretty easy. In more detail: This function reports when the reflector has listed from apiserver. But the store given to the reflector is the fifo of the framework.Controller. The store given back to the caller is still not consistent, and will not be till the framework.Controller puts all the objects from the fifo into the client state store (). The rc specific fix: Before starting the rc manager, seed the expectations store with an expectation like {rc:foo, adds: foo.Status.Replicas, deletes:0}. This will wait for status.Replicas number of ADD events till a timeout. The general fix: Somehow expose this through framework.Controller.HasSynced (clients don't care about the fifo anyway, shouldn't it just be an implementation detail?) ideas? cc'ing people who have written controllers that might be interested I don't think this (and generally anything flaky for 1 release) is a p0, I can fix it if you don't mind dealing with the flakes till I've cleared things off my plate. I'd be more than happy to review a fix.\nWell, it's a P0 because test is flaky. E.g last run:\n- did you have chance to look into it?\nThe \"DaemonRestart\" tests are still labeled at . I will send a PR to promote them.\nare you still planning to send aPR to promote the DaemonRestart tests out of flaky? I think this is the right thing to do.\nAck; sorry, I lost this in the muck.", "commid": "kubernetes_issue_17829", "tokennum": 444}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cb0107493533f820b34c539192006535d74417fa6f51a81419bf6e5cbe3d2296", "query": "}, }, { <del> // a role for the csi external attacher ObjectMeta: metav1.ObjectMeta{Name: \"system:csi-external-attacher\"}, Rules: []rbacv1.PolicyRule{ rbacv1helpers.NewRule(\"get\", \"list\", \"watch\", \"update\", \"patch\").Groups(legacyGroup).Resources(\"persistentvolumes\").RuleOrDie(), rbacv1helpers.NewRule(\"get\", \"list\", \"watch\").Groups(legacyGroup).Resources(\"nodes\").RuleOrDie(), rbacv1helpers.NewRule(\"get\", \"list\", \"watch\", \"update\", \"patch\").Groups(storageGroup).Resources(\"volumeattachments\").RuleOrDie(), rbacv1helpers.NewRule(\"get\", \"list\", \"watch\", \"create\", \"update\", \"patch\").Groups(legacyGroup).Resources(\"events\").RuleOrDie(), }, }, { </del> // a role making the csrapprover controller approve a node client CSR ObjectMeta: metav1.ObjectMeta{Name: \"system:certificates.k8s.io:certificatesigningrequests:nodeclient\"}, Rules: []rbacv1.PolicyRule{", "positive_passages": [{"docid": "doc-en-kubernetes-083944d00199b655f25fb35f51e7ea3786d4181f487cac5cdbda9f2140ce4497", "text": "<!-- Please only use this template for submitting enhancement requests --The built-in and cluster roles here are deprecated in 1.13 when this issue was resolved: /sig storage /milestone v1.17 /priorit important-longterm\nYou must be a member of the GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility. <detailsIn response to : <!-- Please only use this template for submitting enhancement requests -- /milestone v1.17 /priorit important-longterm 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\n/cc /priority important-longterm\nIssues 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\n/remove-lifecycle stale /assign\nBug triage for 1.17 here with a gentle reminder that code freeze for this release is on November 14. Is this issue still intended for 1.17?", "commid": "kubernetes_issue_78739", "tokennum": 293}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cb183c75f8c38c68f2ff0d6ab232af47ba25026fe72534604fd08f8982c4c0a1", "query": "nodeName := \"test-node\" testCases := []struct { <del> name       string volID      string attachID   string shouldFail bool reactor    func(action core.Action) (handled bool, ret runtime.Object, err error) </del> <ins> name         string volID        string attachID     string shouldFail   bool watcherError bool reactor      func(action core.Action) (handled bool, ret runtime.Object, err error) </ins> }{ {name: \"normal test\", volID: \"vol-001\", attachID: getAttachmentName(\"vol-001\", testDriver, nodeName)}, {name: \"normal test 2\", volID: \"vol-002\", attachID: getAttachmentName(\"vol-002\", testDriver, nodeName)},", "positive_passages": [{"docid": "doc-en-kubernetes-bf4acf56a8324d5d9229417a25d2febc989c56201f9f4bdce8fffe7a46728546", "text": "A CSI plugin that the 1.10 controller manager can't detect (which could occur in a number of scenarios, such as when a rollout is being performed or a node is evacuated) seems to retry without backoff. In this case, I have a pod referencing a PVC -PV that references my CSI plugin, but no controller plugin running. The controller is probing every 100ms continuously for a single volume attachment. The controller should backoff. Have not tested with higher numbers of pods, but in a busy system this could cause the controller manager to burn CPU. Also, there isn't actually a great error telling the user why the probing is happening (I knew in this case, but an admin likely has no idea).\n/assign\nIssues 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\n/remove-lifecycle stale /milestone v1.14 adding it to next milestone as per if it doesn't make it then it can be further moved\nas KEP has been moved, unless an exception is made, /milestone v1.15\nthe linked kep above is unrelated to this issue. This is a bug and I don't think it needs an associated enhancement\nsorry, got diverted by the comments on that KEP. /milestone v1.14\nHello from Bug Triage Shadow . I'd like to remind that code freeze is coming in 3 days (Friday, 8th March). Is this still planned to be fixed for 1.14?\nWe have not been tracking this for 1.14. /assign can you help triage and see if this is still an issue and if there is a quick fix?\nI can't reproduce the issue, do you remember what you did? From the logs it seems that Watch channel consistently returns so new is called recursively (beware, 1.10 code, but it's very similar in master): Can it produce fairly stable 100ms delay between calls? Anyway, this is not usual code path, watcher does not return in most cases.", "commid": "kubernetes_issue_64952", "tokennum": 478}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cb183c75f8c38c68f2ff0d6ab232af47ba25026fe72534604fd08f8982c4c0a1", "query": "nodeName := \"test-node\" testCases := []struct { <del> name       string volID      string attachID   string shouldFail bool reactor    func(action core.Action) (handled bool, ret runtime.Object, err error) </del> <ins> name         string volID        string attachID     string shouldFail   bool watcherError bool reactor      func(action core.Action) (handled bool, ret runtime.Object, err error) </ins> }{ {name: \"normal test\", volID: \"vol-001\", attachID: getAttachmentName(\"vol-001\", testDriver, nodeName)}, {name: \"normal test 2\", volID: \"vol-002\", attachID: getAttachmentName(\"vol-002\", testDriver, nodeName)},", "positive_passages": [{"docid": "doc-en-kubernetes-386907f979b2ab6cc28dd5590343cbf2830e874540a448be35232bf4673dff7e", "text": "if I read the code correctly, such recursive must end up with timeout - caller does not care about return value and caller's watch probably won't return anything useful. Is there a reason why we don't return error? This will kick in exponential backoff in A/D controller.\nclearing the milestone for tracking purposes to let the fix land in its own time /milestone clear\nIssues 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\nI found the error would happen when a pv is attahing(volumeattachment has created) and the csi-attacher is deleted at the same time. Then the log would print so frequently (because of recursion).\nis this fixed by ?\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nClosing 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", "commid": "kubernetes_issue_64952", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cb1e4d41c8e153f43b0bbb51f565a1239479cf5ea165697224905218aceba052", "query": "\"k8s.io/apiserver/pkg/server/routes\" componentbaseconfig \"k8s.io/component-base/config\" \"k8s.io/component-base/metrics/legacyregistry\" <ins> _ \"k8s.io/component-base/metrics/prometheus/workqueue\" // for workqueue metric registration </ins> \"k8s.io/kubernetes/pkg/api/legacyscheme\" \"k8s.io/kubernetes/pkg/util/configz\" )", "positive_passages": [{"docid": "doc-en-kubernetes-532b1798e6d44b2cb365a3a392f829271af9f2d30a6550736395566aab22d4dd", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : kube-controller-manager currently does not expose work queue metrics Why is this needed: queuing delay and queue length are important information to debug control plane performance in large scale cluster /assign zhan849 /sig apps", "commid": "kubernetes_issue_87966", "tokennum": 72}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cb22100477d116432cf0109326cab5d7ffd6a82508963d8abd46b3c7c169da26", "query": "\"hash/fnv\" \"sync\" <ins> \"k8s.io/kubernetes/pkg/scheduler/metrics\" </ins> \"k8s.io/api/core/v1\" \"k8s.io/apimachinery/pkg/util/sets\" \"k8s.io/kubernetes/pkg/scheduler/algorithm\"", "positive_passages": [{"docid": "doc-en-kubernetes-aa59e6a5adfc1b233e34e0c1fe9e3a0ec7f2fe6a4636f877a41f4c9aef45f71d", "text": "/kind feature The equivalence cache feature is planned to move to beta in 1.11, and it would be useful to have some metrics attached to it. The equivalence cache should improve scheduling throughput, so we want to be able to correlate e.g. throughput with eCache hit rate. /sig scheduling /sig instrumentation\n/assign misterikkit\nIssues 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\n/remove-lifecycle stale", "commid": "kubernetes_issue_63259", "tokennum": 154}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cb2956ffc73cb334307b63f6c2e1bf334ffd109f3867880e7593575e44cfcd5d", "query": "// Note that the first set of old replica sets doesn't include the ones with no pods, and the second set of old replica sets include all old replica sets. // The third returned value is the new replica set, and it may be nil if it doesn't exist yet. func GetAllReplicaSets(deployment *extensions.Deployment, c clientset.Interface) ([]*extensions.ReplicaSet, []*extensions.ReplicaSet, *extensions.ReplicaSet, error) { <del> rsList, err := ListReplicaSets(deployment, rsListFromClient(c)) </del> <ins> rsList, err := ListReplicaSets(deployment, RsListFromClient(c)) </ins> if err != nil { return nil, nil, nil, err }", "positive_passages": [{"docid": "doc-en-kubernetes-2f9c6224492589431ce544bf6b6edab10c3ff06174d612eb6875bebaba0cb87e", "text": "IMO it feels like a bad practice to have mutating resource handlers. The deletePod handler is used for queueing a Recreate deployment once it has no pods running. It should merely look at the ReplicaSets that have owner refs as opposed to using dc.getReplicaSetsForDeployment. The orphaning/adoption dance is already happening inside the reconcilation loop.\nI'd like to work on this\nfeel free to grab it. I can't assign the issue to you so I'll add myself; ping me on the PR when you have one.", "commid": "kubernetes_issue_46933", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cb321b88dfe98c12df0cc32606e4c9bae44c292331ce7d80f670ad86579eeb2b", "query": "} serviceAccount := strings.TrimSpace(stdout) framework.Logf(\"current service account: %q\", serviceAccount) <del> stat, err := framework.RunKubectl(namespace, \"create\", \"clusterrolebinding\", ClusterAdminBinding, \"--clusterrole=cluster-admin\", \"--user=\"+serviceAccount) </del> <ins> stat, err := framework.RunKubectl(\"\", \"create\", \"clusterrolebinding\", ClusterAdminBinding, \"--clusterrole=cluster-admin\", \"--user=\"+serviceAccount) </ins> framework.Logf(stat) return err }", "positive_passages": [{"docid": "doc-en-kubernetes-cecee0a132f84dbf6d5783d328e94b49c8666ebba8eef4ded1687e53b0451e97", "text": "/kind failing-test <!-- If this is a flake, please add: /kind flake --/sig autoscaling Looks like it just started happening today (@ 2020-09-15 03:54:19 +0000 UTC) !\ncc the namespace from the provided object \"kube-system\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=kube-system' to perform this operation. the namespace from the provided object \"custom-metrics\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=custom-metrics' to perform this operation. the namespace from the provided object \"custom-metrics\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=custom-metrics' to perform this operation.\nrelated fix:\nNo I don't think that's the fix for this (that is just a little cleanup). Actually I think we have to delete namespace parameter in line : Because before , the will have no actually effect. But now with the change of , it will have namespace : at the end of the command. But the namespace in yaml file is which is different from . We should not have parameter when applying from file because this test didn't have before, right? Related PR:\n/assign", "commid": "kubernetes_issue_94809", "tokennum": 318}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cb587eb71b08fdf3c04dd1339074e019337bb8d9c2ff042cb4631abcddb39e70", "query": "\"fmt\" \"net\" \"reflect\" <ins> \"strings\" </ins> \"testing\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\"", "positive_passages": [{"docid": "doc-en-kubernetes-4b95e73f98faca5940a16ee2fccddf37ae93437213e073578ff34d76b732271f", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Service loadbalancer source range don't work in ipvs proxy mode. Which result in gci-gce-ipvs CI failed. http://k8s- How to reproduce it (as minimally and precisely as possible): In gce environment. a service with backend. service type to service util service external IP is specified. the service from pod inside and pod out of the . Environment: Kubernetes version (use ): master Cloud provider or hardware configuration: gce OS (e.g. from /etc/os-release): ubuntu Kernel (e.g. ): Install tools: cluster/kube- Others:\n/kind bug /sig network /label ipvs\n/area ipvs\nThe test seems to be flaky now. Can you take a look please?\nI don't know why, but I think this flaky have the similiar reason with other normal service-test cases, like Those flaky are pretty annoying, problem is, I have run those cases in my own environment many times, never fail... : ( But still, I'll do my best to find the reason.", "commid": "kubernetes_issue_61090", "tokennum": 264}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cb880f561db8c0b3063b48f053c87a9d27456ac8c6e320fe0cc2ab60cee27cba", "query": "cm := controller.NewPodControllerRefManager(rm.podControl, rc, labels.Set(rc.Spec.Selector).AsSelectorPreValidated(), controllerKind) // NOTE: filteredPods are pointing to objects from cache - if you need to // modify them, you need to copy it first. <del> filteredPods, err = cm.ClaimPods(pods) </del> <ins> filteredPods, err = cm.ClaimPods(filteredPods) </ins> if err != nil { return err }", "positive_passages": [{"docid": "doc-en-kubernetes-38d52777560a5c6fb71d98b8b0953e61c4be2731ef4a377191b06cc53fcf6655", "text": "https://k8s- Failed: [] Network Partition [Disruptive] [Slow] [] [ReplicationController] should eagerly create replacement pod during network partition when termination grace is non-zero {Kubernetes e2e suite}\nhttps://k8s- seems to be the first failure here. It seems to have gone in with a bunch of RC/RS changes () cc/", "commid": "kubernetes_issue_37479", "tokennum": 88}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cbe78618be6ec2c33f5b26b248d64e467ee220044799eef2352440a64d88206c", "query": "fakeMirrorClient *fakeMirrorClient } <del> const testKubeletHostname = \"testnode\" </del> <ins> const testKubeletHostname = \"127.0.0.1\" </ins> func newTestKubelet(t *testing.T) *TestKubelet { fakeDocker := &dockertools.FakeDockerClient{Errors: make(map[string]error), RemovedImages: util.StringSet{}}", "positive_passages": [{"docid": "doc-en-kubernetes-d16ca614c05197aa8b2652e3bf008c3a9a5ce41d960188a2ba3459b13d8b1102", "text": "Looks like some kubelet unit tests perform a lookupIp which ends up depending on the health of the local resolver. Specifically has this failing: Which leads to the test in: And we recently swapped out the node names from testnode to 127.0.0.1, so probably the culprit?\n/ref\nInteresting. I did swap out the node names in the unit test as part of to be 127.0.0.1, party because I thought that it wouldn't have any problems resolving during unit tests.\n/cc", "commid": "kubernetes_issue_8549", "tokennum": 113}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cbe78618be6ec2c33f5b26b248d64e467ee220044799eef2352440a64d88206c", "query": "fakeMirrorClient *fakeMirrorClient } <del> const testKubeletHostname = \"testnode\" </del> <ins> const testKubeletHostname = \"127.0.0.1\" </ins> func newTestKubelet(t *testing.T) *TestKubelet { fakeDocker := &dockertools.FakeDockerClient{Errors: make(map[string]error), RemovedImages: util.StringSet{}}", "positive_passages": [{"docid": "doc-en-kubernetes-4a4c75dd985aaeba56d487bbde17d68f0425afc5d7e1167fdf1a1abcb97cd0b6", "text": "cc\nWhat is the environment where you are running the tests? They pass for me on my mac, a linux box, and shippable seems to be passing them as well.\nI couldn 't reproduce the failure either.\nI'm out right now; i'll try them when i get back. For the record, I run hack/test- Paul Morie wrote:\nAhem FTR This acronym is going to go quad-plat Paul Morie wrote:\nI ran on both platforms and saw the tests pass.\nI'm still seeing it. Won't have bandwidth to dig in personally until tomorrow.\nseeing a similar failure after a git pull\nI knew I wasn't crazy\nenvironment: fedora 21, golang: 1.4, docker: 1.6\nI think I see the problem. When I set the node name to in the test I was assuming it would parse as a valid ip address and not end up at the LookupIP call. But only the node name (and not the kubelet hostname) is being set (except in my new test where I ) so it's trying to do a lookup. Do you think you could test just changing the default hostname from \"testnode\" to \"127.0.0.1\" and see if that fixes it for you?\nTrying now\nI still get failures but no panic / threaddump.\ngist coming\nthis looks like again?\nGood that it isn't panicing any longer. I can dig into the test failures tomorrow (I think it should be relatively simple to resolve).\ncool, thanks for looking\nPasses in master now for me. Closing.\nFYI, they will break again once goes in, and then we can merge my PR to see if that fixes it for you.\n:+1:\nis in -- are these tests breaking again?\nI just rebased which I think will fix them.\nThey are breaking again.\nis on it.", "commid": "kubernetes_issue_8522", "tokennum": 407}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cbeea931d2252d59b869316cedbde275334bcd102c7f6f5320b50dc08118394b", "query": "package dns import ( <del> \"testing\" </del> runtimeapi \"k8s.io/cri-api/pkg/apis/runtime/v1\" )", "positive_passages": [{"docid": "doc-en-kubernetes-5e93ba1a338583c6193506912a68a67fcc908451a37c483694071bc120df2bcb", "text": "When a --resolv-conf (DNS resolver config) is passed to kubelet on a Windows node, the config content is used as part of sandbox initialization (through getHostDNSConfig()). Now with the recent changes (), it seems now to fail with an error like: E0315 10:22:16. 4764 ] \"Error syncing pod, skipping\" err=\"failed to \"CreatePodSandbox\" for \"img-pull-(-b40a-459d-9033-)\" with CreatePodSandboxError: \"Failed to generate sandbox config for pod \"img-pull-(-b40a-459d-9033-)\": Unexpected resolver config value: \"C:etckubernetescni\". Expected \"\" or \"Host\".\"\" pod=\"img-puller-3842/img-pull-\" podUID=-b40a-459d-9033- This is showing on all the runs of GCE testgrid (latest): Reading/using the passed resolv config on Windows Run a Windows pool with DNS resolv config being set as part of kubelet params. No response_ 27 alpha.3 1.27 beta.0 master <detailsGCE </details<details</details<details</details<details</details<details</details\n/triage accepted /milestone v1.27 /sig node /sig network\n/sig windows /cc\n/priority criticial-urgent as this is likely a release blocking\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority criticial-urgent 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\n/priority critical-urgent\nHmm, so you're setting the [1]. This PR introduced the capability to read the DNS config options from the Windows host registries while removing the capability to read from a file, introducing a regression. I've sent a PR addressing this issue: [1]\nIs the file you are pointing to a UNIX-style or something else?\nWas the file changing the behavior of the node?", "commid": "kubernetes_issue_116782", "tokennum": 565}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cbeea931d2252d59b869316cedbde275334bcd102c7f6f5320b50dc08118394b", "query": "package dns import ( <del> \"testing\" </del> runtimeapi \"k8s.io/cri-api/pkg/apis/runtime/v1\" )", "positive_passages": [{"docid": "doc-en-kubernetes-a55794e1d2c420cf7484c297920657922704eb45d045ae8237364febdd60d634", "text": "Yeah, what used on GCE/GKE, seems to be a Linux-like conf, eg: nameserver 10.128.0.1 search c.<project_name.internal google.internal ` We haven't tried to remove from kubelet to see the behavior.\nThis Issue/PR has been marked as release blocker. Please have the fix merged by eod today otherwise the feature has to be reverted. For the Issue/PR owner: please have a revert/feature disable PR open today in case the fix failed to get in. Thank you! See the -- Kubernetes 1.27 release manager\nI opened up a revert PR in case this PR does not merge by code freeze.\nThanks for the resolution! both 2019 and 2022 grids seems to be back to green now!\nThanks for confirming! I opened to ensure gets updated too", "commid": "kubernetes_issue_116782", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cc32e821a17b8e08dfaee2e725409cbd0aded17b4e2f4c8b2f8f034abeb464fa", "query": "By(fmt.Sprintf(\"Trying to get logs from node %s pod %s container %s: %v\", podStatus.Spec.NodeName, podStatus.Name, containerName, err)) <del> var logs []byte </del> <ins> var logs string </ins> start := time.Now() // Sometimes the actual containers take a second to get started, try to get logs for 60s for time.Now().Sub(start) < (60 * time.Second) { err = nil <del> logs, err = c.Get(). Resource(\"pods\"). Namespace(ns). Name(pod.Name). SubResource(\"log\"). Param(\"container\", containerName). Do(). Raw() if err == nil && strings.Contains(string(logs), \"Internal Error\") { err = fmt.Errorf(\"Fetched log contains \"Internal Error\": %q.\", string(logs)) } </del> <ins> logs, err = getPodLogs(c, ns, pod.Name, containerName) </ins> if err != nil { By(fmt.Sprintf(\"Warning: Failed to get logs from node %q pod %q container %q. %v\", podStatus.Spec.NodeName, podStatus.Name, containerName, err))", "positive_passages": [{"docid": "doc-en-kubernetes-cf37b0ab7a08d0e2457507bc271b1cb7d1e13fbaee3773971363bc32ae71b35b", "text": "We are running heapster, dns server, kube-proxy etc. in kube-system namespace. Some e2e tests try to make sure all those kube-system pods are at ready state before firing the real tests, others just simply ingore them. But both cases might cause e2e flakiness when some of those kube-system containers are in crashloop, for example, for heapster crashloop, for influxdb crashloop, etc. When such cases happen, the developer doesn't have much information on why since the nodes might be teared down. We should watch those kube-system pods, and onContainerFailure, we should collect the related logs. One simple way is using kubectl logs <Pod<Container--previous cc/\nis this related enough to and that you can bundle it in?\nThe logs from the pods should be retrieved via the api server. This is different from the kubelet logs. I'll upload a PR for this.\nGreat job It will be very helpful for debugging.", "commid": "kubernetes_issue_20099", "tokennum": 229}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cc4be4cede4e90166f5c941827d3cfe63cd91865eabab532d8bc8f29bd519bab", "query": "import ( \"io/ioutil\" \"os\" <ins> \"path/filepath\" </ins> \"testing\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-30e07950978ed617c12104c8342559dfe477718ba7eb61f98c21f95bb37c1439", "text": "In kubectl v1.8.0+, schema info is cached in the location specified by (defaulting to ), written with world-writeable permissions (rw-rw-rw-). If is specified and pointed at a different location accessible to other users/groups, the written files may be modified by other users/groups and disrupt the kubectl invocation. CVSS score: CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N (3.3, low) What versions are affected? kubectl v1.8.0+ What configurations are affected? Invocations that point at world-writeable locations Impact Malformed responses written to the cache directory can disrupt the kubectl invocation Workaround Use the default location in the $HOME directory or point it at a directory that is only accessible to desired users/groups. (original description follows) ==== What happened: The files inside of \".kube/http-cache\" are world writeable (rw-rw-rw-). While the default for these files appears to be the home directory, using the \"--cache-dir\" flag could put these files into a place where world writeable files would allow any user / process to modify the cache files. Modification of the cache files could influence the kubectl utility in a negative way for other users. What you expected to happen: Apply stricter file permissions to the http-cache files. How to reproduce it (as minimally and precisely as possible): Run any generic kubectl command which is successful and then list the cache directory $ kubectl get pods --all-namespaces $ ls -la Anything else we need to know?", "commid": "kubernetes_issue_76676", "tokennum": 398}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cc4be4cede4e90166f5c941827d3cfe63cd91865eabab532d8bc8f29bd519bab", "query": "import ( \"io/ioutil\" \"os\" <ins> \"path/filepath\" </ins> \"testing\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-03c8940a04bf023e0d3632a105949b7e85efda694ffafea56ecb99998a766122", "text": ": I estimate this is a low severity security issue with a CVSS score of \"3.3 / CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N\" - Environment: Linux Kubernetes version (use kubectl version):Client Version: version.Info{Major:\"1\", Minor:\"12\", GitVersion:\"v1.12.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2019-02-26T12:49:28Z\", GoVersion:\"go1.10.8\", Compiler:\"gc\", Platform:\"linux/amd64\"} Server Version: version.Info{Major:\"1\", Minor:\"12\", GitVersion:\"v1.12.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2019-02-26T12:49:28Z\", GoVersion:\"go1.10.8\", Compiler:\"gc\", Platform:\"linux/amd64\"} Cloud provider or hardware configuration: AWS. Running kube api server in hyperkube. OS (e.g: cat /etc/os-release): NAME=\"CentOS Linux\" VERSION=\"7.1808 (Core)\" ID=\"centos\" IDLIKE=\"rhel fedora\" VERSIONID=\"7\" PRETTYNAME=\"CentOS Linux 7.1808 (Core)\" ANSICOLOR=\"0;31\" CPENAME=\"cpe:/o:centos:centos:7\" HOMEURL=\"\" BUGREPORTURL=\"\" CENTOSMANTISBTPROJECT=\"CentOS-7\" CENTOSMANTISBTPROJECTVERSION=\"7\" REDHATSUPPORTPRODUCT=\"centos\" REDHATSUPPORTPRODUCTVERSION=\"7\" OSTREEVERSION=7.1808 Kernel (e.g. uname -a): Linux hackit.internal 3.10.0-862.11.6.el7.x8664 SMP Tue Aug 14 21:49:04 UTC 2018 x8664 x8664 x86_64 GNU/Linux Install tools: Manual installation. Others: n/a\n/sig product-security\nClosing this issue. <detailsIn response to : if you think this is serious, send an email thanks!", "commid": "kubernetes_issue_76676", "tokennum": 565}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cc4be4cede4e90166f5c941827d3cfe63cd91865eabab532d8bc8f29bd519bab", "query": "import ( \"io/ioutil\" \"os\" <ins> \"path/filepath\" </ins> \"testing\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-5f4971cee99e57062ae7961121de35cc677214a3e6ca77682b093e74b00a9b30", "text": "</details\nAdjusted the CVSS score to to indicate user interaction is required (since they must specify a non-default cache option pointed at a shared writeable location)\nThere are two places this should be done: PathPerm and FilePerm should be set here: the temp file and final file should have stricter permissions (probably 0660) here:\n/cc\n/help\nThis request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\n/assign I would like to work on release-1.9, as I just made a hot fix for our team's k8s version of 1.9.\nGitHub didn't allow me to assign the following users: yuchengwu. Note that only and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign I would like to work on release-1.9, as I just made a hot fix for our team's k8s version of 1.9. 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\nhelp fixing this is welcome, though it would only be fixed in releases 1.12+, per\n/label official-cve-feed (Related to kubernetes/sig-security)", "commid": "kubernetes_issue_76676", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cc60fde0a1a3f337829334d8589aa1254deac82502c1464a4c539a70112a0038", "query": "return err } <ins> // Delete this object. </ins> source.Delete(newest.Object.(runtime.Object)) } else { // Update our downstream store.", "positive_passages": [{"docid": "doc-en-kubernetes-20ba07f969c78351406740c712da4b4d48c539c847c31f97f90729edba71a7c4", "text": "From shippable, I noticed there are several failed cases, for example, E0413 17:34:38. ] watch of *api.Pod ended with: Stop requested --- FAIL: Example (0.61s) got: want: a-hello b-controller c-framework FAIL coverage: 85.9% of statements FAIL 7.652s cc/\nanother example:\nah-- this is a different thing. I will fix this, too.\nI'm seeing this from an unrelated change\nYeah I think that's the one I expected to see.", "commid": "kubernetes_issue_6777", "tokennum": 121}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cc64360c3556d3a7f5df77a0af286ca29d00ce16da2740700234614b8cb69244", "query": "} } <ins> nodeNameToPodList = podListForEachNode(cs) </ins> for _, node := range nodes { ginkgo.By(\"Compute Cpu, Mem Fraction after create balanced pods.\") <del> computeCPUMemFraction(cs, node, requestedResource) </del> <ins> computeCPUMemFraction(node, requestedResource, nodeNameToPodList[node.Name]) </ins> } return cleanUp, nil } <del> func computeCPUMemFraction(cs clientset.Interface, node v1.Node, resource *v1.ResourceRequirements) (float64, float64, int64, int64) { framework.Logf(\"ComputeCPUMemFraction for node: %v\", node.Name) totalRequestedCPUResource := resource.Requests.Cpu().MilliValue() totalRequestedMemResource := resource.Requests.Memory().Value() allpods, err := cs.CoreV1().Pods(metav1.NamespaceAll).List(context.TODO(), metav1.ListOptions{}) </del> <ins> func podListForEachNode(cs clientset.Interface) map[string][]*v1.Pod { nodeNameToPodList := make(map[string][]*v1.Pod) allPods, err := cs.CoreV1().Pods(metav1.NamespaceAll).List(context.TODO(), metav1.ListOptions{}) </ins> if err != nil { framework.Failf(\"Expect error of invalid, got : %v\", err) } <del> for _, pod := range allpods.Items { if pod.Spec.NodeName == node.Name { framework.Logf(\"Pod for on the node: %v, Cpu: %v, Mem: %v\", pod.Name, getNonZeroRequests(&pod).MilliCPU, getNonZeroRequests(&pod).Memory) // Ignore best effort pods while computing fractions as they won't be taken in account by scheduler. if v1qos.GetPodQOS(&pod) == v1.PodQOSBestEffort { continue } totalRequestedCPUResource += getNonZeroRequests(&pod).MilliCPU totalRequestedMemResource += getNonZeroRequests(&pod).Memory </del> <ins> for _, pod := range allPods.Items { nodeName := pod.Spec.NodeName nodeNameToPodList[nodeName] = append(nodeNameToPodList[nodeName], &pod) } return nodeNameToPodList } func computeCPUMemFraction(node v1.Node, resource *v1.ResourceRequirements, pods []*v1.Pod) (float64, float64, int64, int64) { framework.Logf(\"ComputeCPUMemFraction for node: %v\", node.Name) totalRequestedCPUResource := resource.Requests.Cpu().MilliValue() totalRequestedMemResource := resource.Requests.Memory().Value() for _, pod := range pods { framework.Logf(\"Pod for on the node: %v, Cpu: %v, Mem: %v\", pod.Name, getNonZeroRequests(pod).MilliCPU, getNonZeroRequests(pod).Memory) // Ignore best effort pods while computing fractions as they won't be taken in account by scheduler. if v1qos.GetPodQOS(pod) == v1.PodQOSBestEffort { continue </ins> } <ins> totalRequestedCPUResource += getNonZeroRequests(pod).MilliCPU totalRequestedMemResource += getNonZeroRequests(pod).Memory </ins> } cpuAllocatable, found := node.Status.Allocatable[v1.ResourceCPU] framework.ExpectEqual(found, true) cpuAllocatableMil := cpuAllocatable.MilliValue()", "positive_passages": [{"docid": "doc-en-kubernetes-68f56cf00eaca7b36f313a8fbb47f02ec3096dc918e863d7bad5040791bff0ba", "text": "From After , Multi-AZ Clusters tests in 1.19 and 1.20 started timing out as createBalancedPodForNodes is extremely inefficient in scale: for each node (out of 5k), it lists all pods in a cluster serially (each list takes ~5s), which translates to ~7 hours. Optimizing this function by listing pods once and then in memory by Spec.NodeName /kind bug /priority critical-urgent /sig scheduling\n/triage accepted\n/assign\n/reopen Looks that ComputeCPUMemFraction took only 12 minutes, but it stuck later, on It is scheduling one pod per each node: Which is waiting 5s to be ready: 5k nodes * 5s = ~7h\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign Can you do the pod creations in parallel?\nYes, good idea. I'll update to do that", "commid": "kubernetes_issue_100705", "tokennum": 227}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cc67331c163b51bd73abebea8b3ff1df1bf8d9307eaed34e60a2907351061bff", "query": "DeleteFunc: c.deleteAPIService, }) <del> serviceInformer.Informer().AddEventHandler(cache.ResourceEventHandlerFuncs{ AddFunc:    c.addService, UpdateFunc: c.updateService, DeleteFunc: c.deleteService, }) </del> c.syncFn = c.sync return c", "positive_passages": [{"docid": "doc-en-kubernetes-89e8d863e20723ba6498e9abf897dd4e49e26cad02c0dde0a4957b2eb3151e69", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Currently APIServiceRegistrationController watch service change and find the related APIServices related if any. Then it AddAPIService/RemoveAPIService for APIAggregator. I dig into the kube-aggregator and find it no need totally, because update APIServices status when related service or endpoint change. So if does not watch services, it will not miss any event for APIServices. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/cc\n/kind enhancement /sig api-machinery\n/assign\nthat does not follow. AvailableConditionController modifies the APIService object. APIServiceRegistrationController must still watch the APIService objects to observe those changes.\noh, I misread the description. You're saying APIServiceRegistrationController doesn't need to watch v1.Service objects", "commid": "kubernetes_issue_57836", "tokennum": 300}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ccc51afb6b9d3bb0f1eb43adbdaca72e7c526728c8a1e8ec7271a8f895c6b991", "query": "\"attachRequired\":       \"attachRequired indicates this CSI volume driver requires an attach operation (because it implements the CSI ControllerPublishVolume() method), and that the Kubernetes attach detach controller should call the attach volume interface which checks the volumeattachment status and waits until the volume is attached before proceeding to mounting. The CSI external-attacher coordinates with CSI volume driver and updates the volumeattachment status when the attach operation is complete. If the CSIDriverRegistry feature gate is enabled and the value is specified to false, the attach operation will be skipped. Otherwise the attach operation will be called.nnThis field is immutable.\", \"podInfoOnMount\":       \"If set to true, podInfoOnMount indicates this CSI volume driver requires additional pod information (like podName, podUID, etc.) during mount operations. If set to false, pod information will not be passed on mount. Default is false. The CSI driver specifies podInfoOnMount as part of driver deployment. If true, Kubelet will pass pod information as VolumeContext in the CSI NodePublishVolume() calls. The CSI driver is responsible for parsing and validating the information passed in as VolumeContext. The following VolumeConext will be passed if podInfoOnMount is set to true. This list might grow, but the prefix will be used. \"csi.storage.k8s.io/pod.name\": pod.Name \"csi.storage.k8s.io/pod.namespace\": pod.Namespace \"csi.storage.k8s.io/pod.uid\": string(pod.UID) \"csi.storage.k8s.io/ephemeral\": \"true\" if the volume is an ephemeral inline volumen                                defined by a CSIVolumeSource, otherwise \"false\"nn\"csi.storage.k8s.io/ephemeral\" is a new feature in Kubernetes 1.16. It is only required for drivers which support both the \"Persistent\" and \"Ephemeral\" VolumeLifecycleMode. Other drivers can leave pod info disabled and/or ignore this field. As Kubernetes 1.15 doesn't support this field, drivers can only support one mode when deployed on such a cluster and the deployment determines which mode that is, for example via a command line parameter of the driver.nnThis field is immutable.\", \"volumeLifecycleModes\": \"volumeLifecycleModes defines what kind of volumes this CSI volume driver supports. The default if the list is empty is \"Persistent\", which is the usage defined by the CSI specification and implemented in Kubernetes via the usual PV/PVC mechanism. The other mode is \"Ephemeral\". In this mode, volumes are defined inline inside the pod spec with CSIVolumeSource and their lifecycle is tied to the lifecycle of that pod. A driver has to be aware of this because it is only going to get a NodePublishVolume call for such a volume. For more information about implementing this mode, see https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html A driver can support one or more of these modes and more modes may be added in the future. This field is beta.nnThis field is immutable.\", <del> \"storageCapacity\":      \"If set to true, storageCapacity indicates that the CSI volume driver wants pod scheduling to consider the storage capacity that the driver deployment will report by creating CSIStorageCapacity objects with capacity information.nnThe check can be enabled immediately when deploying a driver. In that case, provisioning new volumes with late binding will pause until the driver deployment has published some suitable CSIStorageCapacity object.nnAlternatively, the driver can be deployed with the field unset or false and it can be flipped later when storage capacity information has been published.nnThis field is immutable.nnThis is a beta field and only available when the CSIStorageCapacity feature is enabled. The default is false.\", </del> <ins> \"storageCapacity\":      \"If set to true, storageCapacity indicates that the CSI volume driver wants pod scheduling to consider the storage capacity that the driver deployment will report by creating CSIStorageCapacity objects with capacity information.nnThe check can be enabled immediately when deploying a driver. In that case, provisioning new volumes with late binding will pause until the driver deployment has published some suitable CSIStorageCapacity object.nnAlternatively, the driver can be deployed with the field unset or false and it can be flipped later when storage capacity information has been published.nnThis field was immutable in Kubernetes <= 1.22 and now is mutable.nnThis is a beta field and only available when the CSIStorageCapacity feature is enabled. The default is false.\", </ins> \"fsGroupPolicy\":        \"Defines if the underlying volume supports changing ownership and permission of the volume before being mounted. Refer to the specific FSGroupPolicy values for additional details. This field is beta, and is only honored by servers that enable the CSIVolumeFSGroupPolicy feature gate.nnThis field is immutable.nnDefaults to ReadWriteOnceWithFSType, which will examine each volume to determine if Kubernetes should modify ownership and permissions of the volume. With the default policy the defined fsGroup will only be applied if a fstype is defined and the volume's access mode contains ReadWriteOnce.\", \"tokenRequests\":        \"TokenRequests indicates the CSI driver needs pods' service account tokens it is mounting volume for to do necessary authentication. Kubelet will pass the tokens in VolumeContext in the CSI NodePublishVolume calls. The CSI driver should parse and validate the following VolumeContext: \"csi.storage.k8s.io/serviceAccount.tokens\": {n  \"<audience>\": {n    \"token\": <token>,n    \"expirationTimestamp\": <expiration timestamp in RFC3339>,n  },n  ...n}nnNote: Audience in each TokenRequest should be different and at most one token is empty string. To receive a new token after expiry, RequiresRepublish can be used to trigger NodePublishVolume periodically.\", \"requiresRepublish\":    \"RequiresRepublish indicates the CSI driver wants `NodePublishVolume` being periodically called to reflect any possible change in the mounted volume. This field defaults to false.nnNote: After a successful initial NodePublishVolume call, subsequent calls to NodePublishVolume should only update the contents of the volume. New mount points will not be seen by a running container.\",", "positive_passages": [{"docid": "doc-en-kubernetes-cdccab911562ccfffce851739652bcccdbeabc99e62d699c46baa58ef67f3bbe", "text": "Up to 1.21, that field is immutable. That means in practice, a CSIDriver object has to be deleted and then re-created with a different value instead. Mutation via delete/created is unnecessarily complex and as the only consumer of that field (the kube-scheduler) can handle mutation just fine (it'll always ask the informer cache for the current value), it's better to allow mutation.\n/sig storage /assign\nThis is independent of allowing other fields to become mutable, but that might also make sense.\n/triage accepted", "commid": "kubernetes_issue_100089", "tokennum": 125}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cd467bafcd03f4d0183e8bffe6e60485d9b33442475031506ee5488a4227993e", "query": "DisableAcceleratorUsageMetrics:                 {Default: true, PreRelease: featuregate.Beta}, HPAContainerMetrics:                            {Default: false, PreRelease: featuregate.Alpha}, RootCAConfigMap:                                {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.22 <del> SizeMemoryBackedVolumes:                        {Default: false, PreRelease: featuregate.Alpha}, </del> <ins> SizeMemoryBackedVolumes:                        {Default: true, PreRelease: featuregate.Beta}, </ins> ExecProbeTimeout:                               {Default: true, PreRelease: featuregate.GA}, // lock to default and remove after v1.22 based on KEP #1972 update KubeletCredentialProviders:                     {Default: false, PreRelease: featuregate.Alpha}, GracefulNodeShutdown:                           {Default: true, PreRelease: featuregate.Beta},", "positive_passages": [{"docid": "doc-en-kubernetes-2270f3670748d4dd417a0804239a121b559b1166e20ffa4186cfbb1c59e670cb", "text": "When master opens up for , we need to add this back in: /sig node\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nnote to self / 1.21 and 1.22 release notes team -- let's make sure the PR body on the original PR is copied over to the new PR. will think that the old release note and documentation has been covered in 1.21, but we will (I will update this comment with link) manually override it to not show up in 1.21 release notes.", "commid": "kubernetes_issue_100371", "tokennum": 184}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cd5f4ea04143295809ee4a94557d60b03c77c49db74cd16889211e9271140d31", "query": "return nil } <del> // handleDockercfgContent serializes a dockercfg json file func handleDockercfgContent(username, password, email, server string) ([]byte, error) { </del> <ins> // handleDockerCfgJsonContent serializes a ~/.docker/config.json file func handleDockerCfgJsonContent(username, password, email, server string) ([]byte, error) { </ins> dockercfgAuth := credentialprovider.DockerConfigEntry{ Username: username, Password: password, Email:    email, } <del> dockerCfg := credentialprovider.DockerConfigJson{ </del> <ins> dockerCfgJson := credentialprovider.DockerConfigJson{ </ins> Auths: map[string]credentialprovider.DockerConfigEntry{server: dockercfgAuth}, } <del> return json.Marshal(dockerCfg) </del> <ins> return json.Marshal(dockerCfgJson) </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-4279a6f285666ec67ce8924ca9393c19176af7de5707dd42a5f4c239ba12ead2", "text": "/kind bug We're having trouble retrieving images from a private registry on DockerCloud. For nearly a year the following has worked flawlessly. Last Friday I pulled down the 1.9.0 CLI (via brew) and since then have not been able to access any image in a private registry on DockerCloud. I've tried this on 10+ brand new clusters created with kops v1.8.0. The Kubernetes cluster version have been 1.8.0, 1.8.4, 1.8.5 and 1.9.0 (which is not supported by kops yet) and all exhibit the same problem. We create the secret as such: And verify it using: Which yields: And create a test service with with these contents: The pod fails immediatly with: I've reviewed the 1.9.0 release notes and nothing jumps out as the root cause. For reference I've tried putting quotes around the value when creating the secret to no avail. I've also tried prefixing the value with , so the full value would read: also to no avail. Environment: Kubernetes version: Cloud provider and installation info: AWS cluster built with Kops 1.8.0, using (to isolate this issue) nearly the default settings for everything.\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI have same problem, and I \"solved\" it creating a docker-registry secret in an old kubernetes version and pasting it on new kubernetes\nI'm recently (I know it worked perfectly about last month) facing issues with as well. For me it ended in a similar manner saying: I was able to confirm, that this is a kubernetes CLI related issue and not end user. Based on and this I was able to create properly formatted auth information looking like this: . When encoding this one-liner using (MacOS workstation) and apply like this works fine and images can be pulled from private repository again.", "commid": "kubernetes_issue_57427", "tokennum": 466}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cd5f4ea04143295809ee4a94557d60b03c77c49db74cd16889211e9271140d31", "query": "return nil } <del> // handleDockercfgContent serializes a dockercfg json file func handleDockercfgContent(username, password, email, server string) ([]byte, error) { </del> <ins> // handleDockerCfgJsonContent serializes a ~/.docker/config.json file func handleDockerCfgJsonContent(username, password, email, server string) ([]byte, error) { </ins> dockercfgAuth := credentialprovider.DockerConfigEntry{ Username: username, Password: password, Email:    email, } <del> dockerCfg := credentialprovider.DockerConfigJson{ </del> <ins> dockerCfgJson := credentialprovider.DockerConfigJson{ </ins> Auths: map[string]credentialprovider.DockerConfigEntry{server: dockercfgAuth}, } <del> return json.Marshal(dockerCfg) </del> <ins> return json.Marshal(dockerCfgJson) </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-784638a373a6d25c569537512411337ba05226e31cffa99d23b394dffb534564", "text": "However this breaks all automation and can't be considered as solution Confirmed working with kubectl 1.8.5 and server 1.8.4 (guess 1.7.9 as well)\nlooks like there's an extra \"auths\" element when adding the secret using 1.9 kubectl\nAdded in /assign\nMany thanks for the quick fix on this. Any idea when this might get rolled out? Also, it might be a good idea if this was to the known issue list for v1.9.0. It would have saved us a bunch of time trying to track down the root cause. Just trying to make sure no one else needs to do the same.\nlinking to the \"v1.9.0 known issues\" list\nack, asking Mehdy since he is the patch manager for v1.9 branch. Mehdy, any idea when we can ship 1.9.1 with this fix?\nworkarounds for folks until 1.9.1 is released: if you have a .dockerconfigjson for your private registry already, you can manually specify the type and data key (e.g. ) if you don't have a .dockerconfigjson file already, you can fix up the secret produced by manually: the type from to the data key from to the modified secret with\n1 will be released tomorrow\nI can confirm solution works, thanks so much!\nI am still having issues in 1.9.1. This worked in the 1.8.x branches: results in the following error:\nyou have to remove the gitlab-registry secret before you can apply an update... type is immutable, and the fix in 1.9.1 required changing the type of the secret", "commid": "kubernetes_issue_57427", "tokennum": 370}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cd76be3aca74daf649b2cfc0ef1b8bf5cae4f9013e5e9b302a58fcb57793e067", "query": "// } } } <ins> func TestRateLimitedRoundTripper(t *testing.T) { handler := utiltesting.FakeHandler{StatusCode: 200} server := httptest.NewServer(&handler) defer server.Close() method := \"GET\" path := \"/foo/bar\" req, err := http.NewRequest(method, server.URL+path, nil) if err != nil { t.Errorf(\"unexpected error: %v\", err) } // TODO(zmerlynn): Validate the rate limiter is actually getting called. client := http.Client{ Transport: &rateLimitedRoundTripper{ rt:      http.DefaultTransport, limiter: flowcontrol.NewFakeAlwaysRateLimiter(), }, } _, err = client.Do(req) if err != nil { t.Errorf(\"unexpected error: %v\", err) } handler.ValidateRequest(t, path, method, nil) } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-599cbd9914ac52a34ee08ac617d1f4bd774f52f2d5bdcb07fa1a0e76f7194545", "text": "On a large cluster, the routecontroller basically makes O(n) requests all at once, and most of them error out with \"Rate Limit Exceeded\". We then wait for operations to complete on the ones that did stick, and damn the rest, they'll be caught next reconcile (which is a while). In fact, in some cases it appears we're spamming hard enough to get rate limited by the upper-level API DOS protections and seeing something akin to , e.g.: We can do better than this!\nc.f. , which is the other leg of this problem\nI took a look into code and it seems that we are doing full reconciliation every 10s. If we need to create 2000 routes at the beginning it seems to frequently. I think that we need to: first compute how many routes we have to create based on that try to spread them over some time to reduce possibility of causing 'rate limit exceeded' I will try to put some small PR together as a starting point.\nI'm reopening this one, since this doesn't seem to be solved. So basically something strange is happening here. With PR we have 10/s limit on API calls send to GCE. And we are still rate-limitted. However, according to documentation we are allowed for 20/s: So something either doesn't work or is weird.\nWhat is super interesting from the logs of recent run: It starts to creating routes: After 2 minutes from that, we are hitting \"Rate limit Exceeded\" for the first time: And only after 9 minutes we create the first route ever. The second one is created after 15 minutes, and from that point we create a number of them So it seems that nothing useful is happening for the first 2 minutes, and then between 3m30 and 9m30\nOK - so I think that what is happening is that all controllers are sharing GCE interface (and thuse they have common throttling). So if one controller is generating a lot of API calls, then other controllers may be throttled. has a hypothesis that it may be caused by nodecontroller.\nOne thing my PR didn't address (because it was late): Now we have some obnoxious differences in logging when you go to make a request, because the versus could actually be absorbing a fair amount of ratelimiter.", "commid": "kubernetes_issue_26119", "tokennum": 488}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cd76be3aca74daf649b2cfc0ef1b8bf5cae4f9013e5e9b302a58fcb57793e067", "query": "// } } } <ins> func TestRateLimitedRoundTripper(t *testing.T) { handler := utiltesting.FakeHandler{StatusCode: 200} server := httptest.NewServer(&handler) defer server.Close() method := \"GET\" path := \"/foo/bar\" req, err := http.NewRequest(method, server.URL+path, nil) if err != nil { t.Errorf(\"unexpected error: %v\", err) } // TODO(zmerlynn): Validate the rate limiter is actually getting called. client := http.Client{ Transport: &rateLimitedRoundTripper{ rt:      http.DefaultTransport, limiter: flowcontrol.NewFakeAlwaysRateLimiter(), }, } _, err = client.Do(req) if err != nil { t.Errorf(\"unexpected error: %v\", err) } handler.ValidateRequest(t, path, method, nil) } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-bf24c8733a67a958496376416be2eb636c6e4bfb94999815173220461c93fd0c", "text": "It could before because of the operation rate limiter and operation polling anyways, but now could be worse.\n- yes I'm aware of that. And probably this is exactly the case here.\nI got fooled by that - I guess we should fix it somehow.\nOne approach to fixing it is a similar approach to the operation polling code, but in the : warn if we ratelimited for more than N seconds (and dump the request or something? not clear how to clarify what we were sending).\nI found something else - Kubelet is also building GCE interface: We have 2000 kubelets, so if all of them send multiple requests to GCE, we may hit limits.\nAny idea in what circumstances Kubelet will contact cloud provider?\nHmm - it seems it contacts GCE exactly once at the beginning. So it doesn't explain much.\nI think it's only here: I've rarely seen GCE ratelimit readonly calls, in practice, and kubelets come up pretty well staggered.\nOK - so with logs that I , it is pretty clear that we are very heavily throttled on GCE api calls. In particular, when I was running 1000-node cluster, I see lines where we were throttle for 1m30. I'm pretty sure it's significantly higher in 2000-node cluster. I'm going to investigate a bit more where all those reuqests come from.\nActually - it seems that we have a pretty big problem here. Basically, Kubelet seems to send a lot of requests to GCE. So to clarify: every time Kubelet is updating NodeStatus (so every 10s by default) it is sending an API call to GCE to get it's not addresses: that means, that if we have 2000 nodes, kubelets generate 200 QPS to GCE (which is significantly more than we can afford) We should think how to solve this issue, but I think the options are: increasing QPS quota or calling GCE only once per X statusUpdates.\nThe second issue is that we are throttled at the controller level too, and this one I'm tryin to understand right now.", "commid": "kubernetes_issue_26119", "tokennum": 457}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cd76be3aca74daf649b2cfc0ef1b8bf5cae4f9013e5e9b302a58fcb57793e067", "query": "// } } } <ins> func TestRateLimitedRoundTripper(t *testing.T) { handler := utiltesting.FakeHandler{StatusCode: 200} server := httptest.NewServer(&handler) defer server.Close() method := \"GET\" path := \"/foo/bar\" req, err := http.NewRequest(method, server.URL+path, nil) if err != nil { t.Errorf(\"unexpected error: %v\", err) } // TODO(zmerlynn): Validate the rate limiter is actually getting called. client := http.Client{ Transport: &rateLimitedRoundTripper{ rt:      http.DefaultTransport, limiter: flowcontrol.NewFakeAlwaysRateLimiter(), }, } _, err = client.Do(req) if err != nil { t.Errorf(\"unexpected error: %v\", err) } handler.ValidateRequest(t, path, method, nil) } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-b1dad1b374e4c58d925d9fef62d9846d5e0e5eda04aecdd78a124036a36cf31c", "text": "- that said, any rate-limitting on our side, will not solve the kubelet-related problem\nHmm - actually looking into implementation it seems that NodeAddresses are only contacting metadata server, so I'm not longer that convinced...\nAlso, I think that important thing is that a single call to GCE API can translate to multiple api calls to GCE. In particular - CreateRoute translates to: get instance insert route a bunch of getOperation (until this is finished)\nOK - so I think that what is happening here is that since CreateRoute translates to: get instance insert route a bunch of getOperations That means that if we call say 2000 CreateRoute() at the same time, all of them will try to issue: getInstance at the beginning. So we will quickly accumulate 2000 GET requests in the queue. Once they are processed, we generate the \"POST route\" then for any processed. So It's kind of expected what is happening here. So getting back to the Zach`s PR - I think that throttling POST and GET and OPERATION calls separate is kind of good idea in general.\nBut I still don't really understand why do we get \"RateLimitExceeded\". Is that because of Kubelets?\nI think that one problem we have at the RouteController level is that if CreateRoute fails, we simply don't react on it. And we will wait at least 5 minutes before even retrying it. We should add some retries at the route controller level too. I will send out some short PR for it.\nBut I still don't understand why do we get those \"RateLimitExceeded\" error\nOK - so as an update. In GCE, we have a separate rate-limit for number of in-flight CreateRoute call per project. is supposed to address this issue.\nOK - so this one is actually fixed. I mean that it is still long, but currently it's purely blocked on GCE.\nAs a comment - we have an internal bug for it already.", "commid": "kubernetes_issue_26119", "tokennum": 438}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cd89f0c3c1705a9c77c2eee2a5e8c932be0c6271ec8502e7e4dccd2bfd5f96e8", "query": "# TODO(pjh): move the logging agent code below into a separate # module; it was put here temporarily to avoid disrupting the file layout in # the K8s release machinery. <del> $LOGGINGAGENT_VERSION = '1.7.3' </del> <ins> $LOGGINGAGENT_VERSION = '1.7.5' </ins> $LOGGINGAGENT_ROOT = 'C:fluent-bit' $LOGGINGAGENT_SERVICE = 'fluent-bit' $LOGGINGAGENT_CMDLINE = '*fluent-bit.exe*'", "positive_passages": [{"docid": "doc-en-kubernetes-89b11fc4c25f0b72d5f027a149a029fe0341e3d491bf3200f9e9687686d8fec6", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --On Windows 20H2 we are observing crashloops with fluent-bit due to a malformed Windows Event Log entry in the Security log. Fluent-bit to not crash loop. Bring up a GCE Windows cluster on Windows 20H2. You may see a loss of logs. Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others: /sig windows /triage accepted", "commid": "kubernetes_issue_102023", "tokennum": 170}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cdd5ebf4388579fd3da35be0c817ea6f4a57ef2f43623fcf8401ec9431a48146", "query": "\"//pkg/api:go_default_library\", \"//pkg/api/v1/ref:go_default_library\", \"//pkg/kubelet/apis/cri/v1alpha1/runtime:go_default_library\", <del> \"//pkg/kubelet/events:go_default_library\", </del> \"//pkg/kubelet/util/format:go_default_library\", \"//pkg/kubelet/util/ioutils:go_default_library\", \"//pkg/util/hash:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-b0087f3d33811f5a8bf21a1757c4fff7aaef7add29731940c9c3bd61ec9b29c4", "text": "Is this a BUG REPORT or FEATURE REQUEST?: What happened: Now the and has been consistent in by PR . There is no need to convert v1.ObjectReference to clientv1.ObjectReference in . What you expected to happen: Remove this function and cleanup the codes which call this function. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?:\nThere are no sig labels on this issue. Please by:<br(1) mentioning a sig: <bre.g., for API Machinery<br(2) specifying the label manually: <bre.g., for sig/scalability<br<brNote: method (1) will trigger a notification to the team. You can find the team list and label list\nWill submit the cleanup after PR merged.\n/sig api-machinery\n/sub", "commid": "kubernetes_issue_48747", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ce079371cc1bcdb0d025fd7bf82884b6d86022a1e76e270cb17074b99dcca73f", "query": "return err } // Unmount the device from the device mount point. <del> klog.V(4).Infof(\"rbd: unmouting device mountpoint %s\", deviceMountPath) if err = detacher.mounter.Unmount(deviceMountPath); err != nil { </del> <ins> notMnt, err := detacher.mounter.IsLikelyNotMountPoint(deviceMountPath) if err != nil { </ins> return err } <del> klog.V(3).Infof(\"rbd: successfully umount device mountpath %s\", deviceMountPath) </del> <ins> if !notMnt { klog.V(4).Infof(\"rbd: unmouting device mountpoint %s\", deviceMountPath) if err = detacher.mounter.Unmount(deviceMountPath); err != nil { return err } klog.V(3).Infof(\"rbd: successfully umount device mountpath %s\", deviceMountPath) } </ins> <del> klog.V(4).Infof(\"rbd: detaching device %s\", devicePath) err = detacher.manager.DetachDisk(detacher.plugin, deviceMountPath, devicePath) if err != nil { return err </del> <ins> // Get devicePath from deviceMountPath if devicePath is empty if devicePath == \"\" { rbdImageInfo, err := getRbdImageInfo(deviceMountPath) if err != nil { return err } found := false devicePath, found = getRbdDevFromImageAndPool(rbdImageInfo.pool, rbdImageInfo.name) if !found { klog.Warningf(\"rbd: can't found devicePath for %v. Device is already unmounted, Image %v, Pool %v\", deviceMountPath, rbdImageInfo.pool, rbdImageInfo.name) } } if devicePath != \"\" { klog.V(4).Infof(\"rbd: detaching device %s\", devicePath) err = detacher.manager.DetachDisk(detacher.plugin, deviceMountPath, devicePath) if err != nil { return err } klog.V(3).Infof(\"rbd: successfully detach device %s\", devicePath) </ins> } <del> klog.V(3).Infof(\"rbd: successfully detach device %s\", devicePath) </del> err = os.Remove(deviceMountPath) if err != nil { return err", "positive_passages": [{"docid": "doc-en-kubernetes-504dcfb92cdb541009bacf4c1b680d2ebe053bb62fdf81ca10ac728d32628e43", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: Pod was deleted successfully but there is still a lock on the ceph image. I find two logs,one for that lock not removed and another for that lock removed. I find that there are little difference between them. the log that lock not removed: and the log that lock removed: What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.6.7 Cloud provider or hardware configuration**: OS (e.g. from /etc/os-release): centos7 Kernel (e.g. ): 3.10.0-327.el7.x86_64 Install tools: Others:\n/sig storage\nError 16 is EBUSY. similar to\nwere you running kubelet with cadvisor on?\n/assign\nyes, every kubelet run with cadvisor,and i know what code 16 represent for,but i still don't know the reason, is this a bug? How can i avoid this kind of situation from happening,thank you\nIt is probably related to\nWe see some other case may cause , kubelet run with nodeexporter and nodeexporter is deployed by k8s daemonset with -v /:/rootfs:ro (mount kubelet host rootfs into nodeexporter container). rbd device is mounted before nodeexporter started, because k8s 1.6.7 not support mount propagation, when the rbd plugin unmount /dev/rbd0 on the host namespace, the mount info will still leave over in node_exporter container namespace, may cause . hope this would help\nthanks, does the problem persist if node_exporter stops collecting filesystem metrics?\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with .", "commid": "kubernetes_issue_54214", "tokennum": 513}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ce079371cc1bcdb0d025fd7bf82884b6d86022a1e76e270cb17074b99dcca73f", "query": "return err } // Unmount the device from the device mount point. <del> klog.V(4).Infof(\"rbd: unmouting device mountpoint %s\", deviceMountPath) if err = detacher.mounter.Unmount(deviceMountPath); err != nil { </del> <ins> notMnt, err := detacher.mounter.IsLikelyNotMountPoint(deviceMountPath) if err != nil { </ins> return err } <del> klog.V(3).Infof(\"rbd: successfully umount device mountpath %s\", deviceMountPath) </del> <ins> if !notMnt { klog.V(4).Infof(\"rbd: unmouting device mountpoint %s\", deviceMountPath) if err = detacher.mounter.Unmount(deviceMountPath); err != nil { return err } klog.V(3).Infof(\"rbd: successfully umount device mountpath %s\", deviceMountPath) } </ins> <del> klog.V(4).Infof(\"rbd: detaching device %s\", devicePath) err = detacher.manager.DetachDisk(detacher.plugin, deviceMountPath, devicePath) if err != nil { return err </del> <ins> // Get devicePath from deviceMountPath if devicePath is empty if devicePath == \"\" { rbdImageInfo, err := getRbdImageInfo(deviceMountPath) if err != nil { return err } found := false devicePath, found = getRbdDevFromImageAndPool(rbdImageInfo.pool, rbdImageInfo.name) if !found { klog.Warningf(\"rbd: can't found devicePath for %v. Device is already unmounted, Image %v, Pool %v\", deviceMountPath, rbdImageInfo.pool, rbdImageInfo.name) } } if devicePath != \"\" { klog.V(4).Infof(\"rbd: detaching device %s\", devicePath) err = detacher.manager.DetachDisk(detacher.plugin, deviceMountPath, devicePath) if err != nil { return err } klog.V(3).Infof(\"rbd: successfully detach device %s\", devicePath) </ins> } <del> klog.V(3).Infof(\"rbd: successfully detach device %s\", devicePath) </del> err = os.Remove(deviceMountPath) if err != nil { return err", "positive_passages": [{"docid": "doc-en-kubernetes-e58e0280341e2b39cd2fb25afc5193b55cba235066305ff633e2c34889e5eefe", "text": "Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nI'm experiencing this issue. From what I can read above, if the rbd mount happens before the node_exporter starts; we'll always experience status 16?\nWe're getting this issue. This is because the mounted volume is mounted on Cadvisor container too. So the /dev/rbdX file is still in use. But still didn't find any solution to fix.\nrbd volume will stuck when failed as will always returen\nMy solution: container use a volumeMount. make a script file to be executed every a minute:", "commid": "kubernetes_issue_54214", "tokennum": 220}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ce608da03909ad5e7b0eadd7f153298d4513a8b232d46dbe29ae722a789bbe74", "query": "nsFlag := fmt.Sprintf(\"--namespace=%v\", ns) ginkgo.By(\"executing a command with run and attach with stdin\") <del> runOutput := framework.NewKubectlCommand(nsFlag, \"run\", \"run-test\", \"--image=\"+busyboxImage, \"--restart=OnFailure\", \"--attach=true\", \"--stdin\", \"--\", \"sh\", \"-c\", \"cat && echo 'stdin closed'\"). WithStdinData(\"abcd1234\"). </del> <ins> // We wait for a non-empty line so we know kubectl has attached runOutput := framework.NewKubectlCommand(nsFlag, \"run\", \"run-test\", \"--image=\"+busyboxImage, \"--restart=OnFailure\", \"--attach=true\", \"--stdin\", \"--\", \"sh\", \"-c\", \"while [ -z \"$s\" ]; do read s; sleep 1; done; echo read:$s && cat && echo 'stdin closed'\"). WithStdinData(\"valuenabcd1234\"). </ins> ExecOrDie() <del> g := func(pods []*v1.Pod) sort.Interface { return sort.Reverse(controller.ActivePods(pods)) } runTestPod, _, err := polymorphichelpers.GetFirstPod(f.ClientSet.CoreV1(), ns, \"run=run-test\", 1*time.Minute, g) gomega.Expect(err).To(gomega.BeNil()) // NOTE: we cannot guarantee our output showed up in the container logs before stdin was closed, so we have // to loop test. err = wait.PollImmediate(time.Second, time.Minute, func() (bool, error) { if !e2epod.CheckPodsRunningReady(c, ns, []string{runTestPod.Name}, 1*time.Second) { e2elog.Failf(\"Pod %q of Job %q should still be running\", runTestPod.Name, \"run-test\") } logOutput := framework.RunKubectlOrDie(nsFlag, \"logs\", runTestPod.Name) gomega.Expect(runOutput).To(gomega.ContainSubstring(\"abcd1234\")) gomega.Expect(runOutput).To(gomega.ContainSubstring(\"stdin closed\")) return strings.Contains(logOutput, \"abcd1234\"), nil }) gomega.Expect(err).To(gomega.BeNil()) </del> <ins> gomega.Expect(runOutput).To(gomega.ContainSubstring(\"read:value\")) gomega.Expect(runOutput).To(gomega.ContainSubstring(\"abcd1234\")) gomega.Expect(runOutput).To(gomega.ContainSubstring(\"stdin closed\")) </ins> gomega.Expect(c.BatchV1().Jobs(ns).Delete(\"run-test\", nil)).To(gomega.BeNil())", "positive_passages": [{"docid": "doc-en-kubernetes-7b2399b1ff0857c826d80a73801e04bffa6df7e676dd58a7e2d56a664bd364fc", "text": "The test case \"executing a command with run and attach without stdin\" is inherently racy. The test runs, and expected to see in the output. The case when the test passes: case 1: Kubernetes creates and starts the container without stdin; The container exits before attach runs; kubectl falls back to get container log, which contains . case 2: Kubernetes creates and starts the container without stdin; kubectl attach before \"stdin closed\" is printed; kubectl attach contains . The case when the test fails: Kubernetes creates and starts the container without stdin; The container prints \"stdin closed\", but hasn't exited yet; kubectl attach contains nothing. One example failure: Related issue: Can we modify this test not to check the output? Or use to check output instead? /cc\nUploaded to try to address\n/reopen This test is still inherently racy, even after\nFix in (I hope!)\nMoving into the current milestone as it was not fixed in 1.14\nHello I'm a bug triage shadow for the 1.16 release cycle and considering this issue is tagged for 1.16, I'd like to check its status. Code freeze is starting on August 29th (about 3 days from now). Do we still target this issue to be fixed for 1.16?\nThanks . PR is available and awaiting review!\nWhat is the PR in question? Is it targeting 1.16 or 1.17?\n/reopen This test is having a lot of failures these days\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nis right, it seems to be present in kind jobs now only\n/assign let's see if we start to recover a bit of stability :smile:\nThe rate of failures decreased a lot since last changes Checking the logs of the failures it seems that the problem is that the pod has not finished before checking the output, as Lantao described The test fails Collecting events from namespace The framework logs the pods the kubelet thinks is on the node\nnote that it's still racy, but it's hopefully somewhat mitigated.\n/reopen\nReopened this issue.", "commid": "kubernetes_issue_73099", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ce608da03909ad5e7b0eadd7f153298d4513a8b232d46dbe29ae722a789bbe74", "query": "nsFlag := fmt.Sprintf(\"--namespace=%v\", ns) ginkgo.By(\"executing a command with run and attach with stdin\") <del> runOutput := framework.NewKubectlCommand(nsFlag, \"run\", \"run-test\", \"--image=\"+busyboxImage, \"--restart=OnFailure\", \"--attach=true\", \"--stdin\", \"--\", \"sh\", \"-c\", \"cat && echo 'stdin closed'\"). WithStdinData(\"abcd1234\"). </del> <ins> // We wait for a non-empty line so we know kubectl has attached runOutput := framework.NewKubectlCommand(nsFlag, \"run\", \"run-test\", \"--image=\"+busyboxImage, \"--restart=OnFailure\", \"--attach=true\", \"--stdin\", \"--\", \"sh\", \"-c\", \"while [ -z \"$s\" ]; do read s; sleep 1; done; echo read:$s && cat && echo 'stdin closed'\"). WithStdinData(\"valuenabcd1234\"). </ins> ExecOrDie() <del> g := func(pods []*v1.Pod) sort.Interface { return sort.Reverse(controller.ActivePods(pods)) } runTestPod, _, err := polymorphichelpers.GetFirstPod(f.ClientSet.CoreV1(), ns, \"run=run-test\", 1*time.Minute, g) gomega.Expect(err).To(gomega.BeNil()) // NOTE: we cannot guarantee our output showed up in the container logs before stdin was closed, so we have // to loop test. err = wait.PollImmediate(time.Second, time.Minute, func() (bool, error) { if !e2epod.CheckPodsRunningReady(c, ns, []string{runTestPod.Name}, 1*time.Second) { e2elog.Failf(\"Pod %q of Job %q should still be running\", runTestPod.Name, \"run-test\") } logOutput := framework.RunKubectlOrDie(nsFlag, \"logs\", runTestPod.Name) gomega.Expect(runOutput).To(gomega.ContainSubstring(\"abcd1234\")) gomega.Expect(runOutput).To(gomega.ContainSubstring(\"stdin closed\")) return strings.Contains(logOutput, \"abcd1234\"), nil }) gomega.Expect(err).To(gomega.BeNil()) </del> <ins> gomega.Expect(runOutput).To(gomega.ContainSubstring(\"read:value\")) gomega.Expect(runOutput).To(gomega.ContainSubstring(\"abcd1234\")) gomega.Expect(runOutput).To(gomega.ContainSubstring(\"stdin closed\")) </ins> gomega.Expect(c.BatchV1().Jobs(ns).Delete(\"run-test\", nil)).To(gomega.BeNil())", "positive_passages": [{"docid": "doc-en-kubernetes-6fb855e6221755f4f8c679054412ceafcb7919572a50b214c71af07d9654c4d2", "text": "<detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nany updates here?\nnope, totally agree with the description, is racy by design, couldn't find any way or trick to avoid the randomness\nEDIT: It's late and I'm actually not sure I'm remembering this correctly, take this comment with a heap of salt: Specific sub-tests were fixed previously I think, but this one sub-case: That one we can't use the \"Wait for stdin input to signal we're attached\" hack, so it's just racy and broken. We could remove that case maybe. I'm not sure who I'd want to weigh in on that, probably someone more active in node / CLI.\nnot super common atm but still happening. discussing\n/unassign has a fix for this", "commid": "kubernetes_issue_73099", "tokennum": 203}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ce7815c25aecc858b2c573436b442f3d348254f662cf26e6fb31e3ecc8181799", "query": "CreateOrUpdate(ctx context.Context, resourceGroupName string, publicIPAddressName string, parameters network.PublicIPAddress) (resp *http.Response, err error) Delete(ctx context.Context, resourceGroupName string, publicIPAddressName string) (resp *http.Response, err error) Get(ctx context.Context, resourceGroupName string, publicIPAddressName string, expand string) (result network.PublicIPAddress, err error) <ins> GetVirtualMachineScaleSetPublicIPAddress(ctx context.Context, resourceGroupName string, virtualMachineScaleSetName string, virtualmachineIndex string, networkInterfaceName string, IPConfigurationName string, publicIPAddressName string, expand string) (result network.PublicIPAddress, err error) </ins> List(ctx context.Context, resourceGroupName string) (result []network.PublicIPAddress, err error) }", "positive_passages": [{"docid": "doc-en-kubernetes-c62a800befd6b705c74ea2036c66907711f830c03e53ca86df0e2014d6541d16", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Node external IP of azure VMSS cannot be obtained when cloud-controller-manager is enabled. Corresponding logs are shown as follows:\n/sig azure\n/milestone v1.16", "commid": "kubernetes_issue_80014", "tokennum": 92}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cea1df46b662b4c5b405fd066b723885003ec7400b1930a4aa2f94def3dd9e23", "query": "} } } func TestPrintPod(t *testing.T) { tests := []struct { pod    api.Pod", "positive_passages": [{"docid": "doc-en-kubernetes-f29982137c07dadb3e257d7391e0d9b7bfd5f1ce8fdca72f798301cc159728a0", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: After labeling clusters in a Federation, when you type the field is empty. What you expected to happen: The fiels should contain information about the labels in the cluster How to reproduce it (as minimally and precisely as possible): a federation control pane in any Cloud Provider and any DNS provider your cluster: info aboyut the cluster with the flag: Note: if you describe it, you see the labels being : Environment: Kubernetes version (use ): 1.8.0 Cloud provider or hardware configuration**: anyone OS (e.g. from /etc/os-release): Ubuntu 16.04 Kernel (e.g. ): Linux Install tools: curl Others:\n/sig multicluster\nI'm working on it.", "commid": "kubernetes_issue_53729", "tokennum": 179}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cef00164a645c31ceb4a0a11f092360b8f5f96b99da667d85b92fe8d4eae344d", "query": "} }) <del> ginkgo.It(\"should manage the lifecycle of a ResourceQuota\", func() { </del> <ins> /* Release: v1.25 Testname: ResourceQuota, manage lifecycle of a ResourceQuota Description: Attempt to create a ResourceQuota for CPU and Memory quota limits. Creation MUST be successful. Attempt to list all namespaces with a label selector which MUST succeed. One list MUST be found. The ResourceQuota when patched MUST succeed. Given the patching of the ResourceQuota, the fields MUST equal the new values. It MUST succeed at deleting a collection of ResourceQuota via a label selector. */ framework.ConformanceIt(\"should manage the lifecycle of a ResourceQuota\", func() { </ins> client := f.ClientSet ns := f.Namespace.Name", "positive_passages": [{"docid": "doc-en-kubernetes-8218004df321e49189cb8c22922209b0129dd124df9f46401769a8d8c1aa8714", "text": "[x] test approval issue : [x] test pr : 7 July 2022 [X] two weeks soak end date : 21 July 2022 [X] test promotion pr : According to this APIsnoop query, there is still some remaining ResourceQuota endpoints which are untested. The Status endpoints will be addressed in another test. listCoreV1ResourceQuotaForAllNamespacespatchCoreV1NamespacedResourceQuotadeleteCoreV1CollectionNamespacedResourceQuota Using a number of existing e2e test practices a new has been created for three ResourceQuota endpoints. The e2e logs for this test are listed below. This query shows the endpoints hit within a short period of running the e2e test If a test with these calls gets merged, test coverage will go up by 3 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance\n/triage accepted\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_109682", "tokennum": 223}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cf170160f1ffa82522d54ce57611bf262888546d8f81eb34ccbc54f5b549e597", "query": "ds.network = network.NewPluginManager(plug) klog.Infof(\"Docker cri networking managed by %v\", plug.Name()) <del> // NOTE: cgroup driver is only detectable in docker 1.11+ cgroupDriver := defaultCgroupDriver dockerInfo, err := ds.client.Info() klog.Infof(\"Docker Info: %+v\", dockerInfo) if err != nil { klog.Errorf(\"Failed to execute Info() call to the Docker client: %v\", err) klog.Warningf(\"Falling back to use the default driver: %q\", cgroupDriver) } else if len(dockerInfo.CgroupDriver) == 0 { klog.Warningf(\"No cgroup driver is set in Docker\") klog.Warningf(\"Falling back to use the default driver: %q\", cgroupDriver) } else { cgroupDriver = dockerInfo.CgroupDriver } if len(kubeCgroupDriver) != 0 && kubeCgroupDriver != cgroupDriver { return nil, fmt.Errorf(\"misconfiguration: kubelet cgroup driver: %q is different from docker cgroup driver: %q\", kubeCgroupDriver, cgroupDriver) </del> <ins> // skipping cgroup driver checks for Windows if runtime.GOOS == \"linux\" { // NOTE: cgroup driver is only detectable in docker 1.11+ cgroupDriver := defaultCgroupDriver dockerInfo, err := ds.client.Info() klog.Infof(\"Docker Info: %+v\", dockerInfo) if err != nil { klog.Errorf(\"Failed to execute Info() call to the Docker client: %v\", err) klog.Warningf(\"Falling back to use the default driver: %q\", cgroupDriver) } else if len(dockerInfo.CgroupDriver) == 0 { klog.Warningf(\"No cgroup driver is set in Docker\") klog.Warningf(\"Falling back to use the default driver: %q\", cgroupDriver) } else { cgroupDriver = dockerInfo.CgroupDriver } if len(kubeCgroupDriver) != 0 && kubeCgroupDriver != cgroupDriver { return nil, fmt.Errorf(\"misconfiguration: kubelet cgroup driver: %q is different from docker cgroup driver: %q\", kubeCgroupDriver, cgroupDriver) } klog.Infof(\"Setting cgroupDriver to %s\", cgroupDriver) ds.cgroupDriver = cgroupDriver </ins> } <del> klog.Infof(\"Setting cgroupDriver to %s\", cgroupDriver) ds.cgroupDriver = cgroupDriver </del> ds.versionCache = cache.NewObjectCache( func() (interface{}, error) { return ds.getDockerVersion()", "positive_passages": [{"docid": "doc-en-kubernetes-dea116f1992e38bb66fa8cbf634ccd764aeb1776d3000f923339739e72460ab8", "text": "What happened: I have a Kubernetes Cluster with 2 Windows Server 2019 Core VMs as worker nodes. I upgraded first the cluster, and then the first Windows node following the docs here: Every step ran without issue, but the kubelet service was not started. This was not immediately obvious, since \"restart-service kubelet\" does not propagate the error. I think \"start-service kubelet\" would be better advice. The logs said: After changing the value of cgroupDriver manually in from \"systemd\" to \"cgroupfs\", the kubelet started successfully. What you expected to happen: One of 2 things: Either the Windows upgrade docs telling me what I need to do to fix this, or the kubeadm not breaking the configuration for windows in the first place. How to reproduce it (as minimally and precisely as possible): a windows node to a Kubernetes v1.19 cluster via kubeadm the cluster via kubeadm the Windows node following the docs Anything else we need to know?: Environment: Kubernetes version (use ): 1.20.1 Cloud provider or hardware configuration: OS (e.g: ): Windows Server 2019 Core Kernel (e.g. ): Install tools: kubeadm Network plugin and version (if this is a network-related bug): Others: /sig windows\nthis may cause by the default value of defaultCgroupDriver cgroupfs Would you provide the from Windows node?\n/assign\nkubeadm doesn't do anything about cgroup drivers on Windows because cgroups don't exist on Windows. ideally the kubelet checks about this should be skipped entirely in dockershim for non-Linux.\n! However, windows docker return as cgroupfs.\nprobably 's output is the same structure on all OSes with being a default value. this field should not be checked on Windows at all.\n/retitle kubelet: don't check for the Docker cgroup driver on Windows\nadding since the PR is favorable. /triage accepted", "commid": "kubernetes_issue_97759", "tokennum": 446}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cf2ba9a1038c82b0b72a2ac59a6f288d78e28e5a1c8c5462d890dee115dbe1ec", "query": "} func TestValidateDisabledSubpathExpr(t *testing.T) { <del> // Enable feature VolumeSubpathEnvExpansion defer featuregatetesting.SetFeatureGateDuringTest(t, utilfeature.DefaultFeatureGate, features.VolumeSubpathEnvExpansion, true)() </del> volumes := []core.Volume{ {Name: \"abc\", VolumeSource: core.VolumeSource{PersistentVolumeClaim: &core.PersistentVolumeClaimVolumeSource{ClaimName: \"testclaim1\"}}},", "positive_passages": [{"docid": "doc-en-kubernetes-a166ddd65322b2b4c2d8cbe35891249f4d033568413f3b77fc1f46ee1d1ee8b8", "text": "/kind cleanup /sig storage /sig node Description: Feature gate VolumeSubpathEnvExpansion was GA in 1.17 and is marked for removal in 1.19 Related Issues: GA Release:\n/assign\n/cc", "commid": "kubernetes_issue_89519", "tokennum": 48}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cf34c44b2a628985bf7af758aa9e3be694d7554cfa9c226d9905942c98586370", "query": "return false } bucketID := nextTime.Unix() <ins> t.lock.Lock() defer t.lock.Unlock() </ins> if bucketID < t.startBucketID { bucketID = t.startBucketID }", "positive_passages": [{"docid": "doc-en-kubernetes-c66c9bab938b839459ac01dfd08140ea19c2b9a1199fe50a2b49f94fd9cbbbfb", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: I try to backport bookmark feature to our internal branch. When I enable bookmark feature, apiserver leaks memory. I spend some time to dig the root cause and find the bookmarkWatchers of service cacher is keep increasing. I am not sure if it exists at upstream code. Please let me know if it is ok at latest code. What you expected to happen: Avoid memory leaking How to reproduce it (as minimally and precisely as possible): a cluster. not update service. will find kube-apiserver's memory keep increasing. Anything else we need to know?: Kubelet will watch service with bookmark, and add a watcher to bookmarkWatchers. and service init resource version is 0 Without updating service, we cannot update \"lastProcessedResourceVersion\", it will keep 0, bookmarkTimer branch will always be continued. As a result, it cannot trigger popExpiredWatchers, so the service watcher will keep increasing every watching. Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig scalability PLAT :)\nHow about making this change ?\n- can you also please take a look?\nAgree with u. That's same way I fix in our branch. But I wanna hear the suggestion of and .\n! With the same bugfix wrote above, we can see the memory not increasing any more.\nGiven that watch-bookmarks doesn't create any additional go-routines (well, creates 1, but cannot leak them), it has to leak the data. The only data that can be leaked is exactly bookmarkWatchers. So I looked into the code and got into exactly the same conclusion - that we must be leaking watchers for resources that aren't changing. The fix as above makes sense (though we also need a unit test for it).\nThanks a lot.\nhas the fix by\nThanks for reporting the bug, I will look at this day later. In addition, also need to think carefully about whether need to send a bookmark when there are no events at all.\ncc", "commid": "kubernetes_issue_80690", "tokennum": 531}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cf45942809c6b5a607fe39e6c3a9dcb3626b03ad2c9b9ca17d92596426d6f432", "query": "} func (d *CachedDiscoveryClient) writeCachedFile(filename string, obj runtime.Object) error { <del> if err := os.MkdirAll(filepath.Dir(filename), 0755); err != nil { </del> <ins> if err := os.MkdirAll(filepath.Dir(filename), 0750); err != nil { </ins> return err }", "positive_passages": [{"docid": "doc-en-kubernetes-30e07950978ed617c12104c8342559dfe477718ba7eb61f98c21f95bb37c1439", "text": "In kubectl v1.8.0+, schema info is cached in the location specified by (defaulting to ), written with world-writeable permissions (rw-rw-rw-). If is specified and pointed at a different location accessible to other users/groups, the written files may be modified by other users/groups and disrupt the kubectl invocation. CVSS score: CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N (3.3, low) What versions are affected? kubectl v1.8.0+ What configurations are affected? Invocations that point at world-writeable locations Impact Malformed responses written to the cache directory can disrupt the kubectl invocation Workaround Use the default location in the $HOME directory or point it at a directory that is only accessible to desired users/groups. (original description follows) ==== What happened: The files inside of \".kube/http-cache\" are world writeable (rw-rw-rw-). While the default for these files appears to be the home directory, using the \"--cache-dir\" flag could put these files into a place where world writeable files would allow any user / process to modify the cache files. Modification of the cache files could influence the kubectl utility in a negative way for other users. What you expected to happen: Apply stricter file permissions to the http-cache files. How to reproduce it (as minimally and precisely as possible): Run any generic kubectl command which is successful and then list the cache directory $ kubectl get pods --all-namespaces $ ls -la Anything else we need to know?", "commid": "kubernetes_issue_76676", "tokennum": 398}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cf45942809c6b5a607fe39e6c3a9dcb3626b03ad2c9b9ca17d92596426d6f432", "query": "} func (d *CachedDiscoveryClient) writeCachedFile(filename string, obj runtime.Object) error { <del> if err := os.MkdirAll(filepath.Dir(filename), 0755); err != nil { </del> <ins> if err := os.MkdirAll(filepath.Dir(filename), 0750); err != nil { </ins> return err }", "positive_passages": [{"docid": "doc-en-kubernetes-03c8940a04bf023e0d3632a105949b7e85efda694ffafea56ecb99998a766122", "text": ": I estimate this is a low severity security issue with a CVSS score of \"3.3 / CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N\" - Environment: Linux Kubernetes version (use kubectl version):Client Version: version.Info{Major:\"1\", Minor:\"12\", GitVersion:\"v1.12.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2019-02-26T12:49:28Z\", GoVersion:\"go1.10.8\", Compiler:\"gc\", Platform:\"linux/amd64\"} Server Version: version.Info{Major:\"1\", Minor:\"12\", GitVersion:\"v1.12.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2019-02-26T12:49:28Z\", GoVersion:\"go1.10.8\", Compiler:\"gc\", Platform:\"linux/amd64\"} Cloud provider or hardware configuration: AWS. Running kube api server in hyperkube. OS (e.g: cat /etc/os-release): NAME=\"CentOS Linux\" VERSION=\"7.1808 (Core)\" ID=\"centos\" IDLIKE=\"rhel fedora\" VERSIONID=\"7\" PRETTYNAME=\"CentOS Linux 7.1808 (Core)\" ANSICOLOR=\"0;31\" CPENAME=\"cpe:/o:centos:centos:7\" HOMEURL=\"\" BUGREPORTURL=\"\" CENTOSMANTISBTPROJECT=\"CentOS-7\" CENTOSMANTISBTPROJECTVERSION=\"7\" REDHATSUPPORTPRODUCT=\"centos\" REDHATSUPPORTPRODUCTVERSION=\"7\" OSTREEVERSION=7.1808 Kernel (e.g. uname -a): Linux hackit.internal 3.10.0-862.11.6.el7.x8664 SMP Tue Aug 14 21:49:04 UTC 2018 x8664 x8664 x86_64 GNU/Linux Install tools: Manual installation. Others: n/a\n/sig product-security\nClosing this issue. <detailsIn response to : if you think this is serious, send an email thanks!", "commid": "kubernetes_issue_76676", "tokennum": 565}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cf45942809c6b5a607fe39e6c3a9dcb3626b03ad2c9b9ca17d92596426d6f432", "query": "} func (d *CachedDiscoveryClient) writeCachedFile(filename string, obj runtime.Object) error { <del> if err := os.MkdirAll(filepath.Dir(filename), 0755); err != nil { </del> <ins> if err := os.MkdirAll(filepath.Dir(filename), 0750); err != nil { </ins> return err }", "positive_passages": [{"docid": "doc-en-kubernetes-5f4971cee99e57062ae7961121de35cc677214a3e6ca77682b093e74b00a9b30", "text": "</details\nAdjusted the CVSS score to to indicate user interaction is required (since they must specify a non-default cache option pointed at a shared writeable location)\nThere are two places this should be done: PathPerm and FilePerm should be set here: the temp file and final file should have stricter permissions (probably 0660) here:\n/cc\n/help\nThis request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\n/assign I would like to work on release-1.9, as I just made a hot fix for our team's k8s version of 1.9.\nGitHub didn't allow me to assign the following users: yuchengwu. Note that only and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign I would like to work on release-1.9, as I just made a hot fix for our team's k8s version of 1.9. 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\nhelp fixing this is welcome, though it would only be fixed in releases 1.12+, per\n/label official-cve-feed (Related to kubernetes/sig-security)", "commid": "kubernetes_issue_76676", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cf46d539e11a5c819473fefbc11923df9e90dbeb0d6519e7a811d876303eaccf", "query": "} service, err := e.serviceLister.Services(namespace).Get(name) if err != nil { <del> // Delete the corresponding endpoint, as the service has been deleted. // TODO: Please note that this will delete an endpoint when a // service is deleted. However, if we're down at the time when // the service is deleted, we will miss that deletion, so this // doesn't completely solve the problem. See #6877. err = e.client.CoreV1().Endpoints(namespace).Delete(name, nil) if err != nil && !errors.IsNotFound(err) { return err } </del> <ins> // Service has been deleted. So no need to do any more operations. </ins> return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-4d460c4f5c8fb1c08c701d631c43381b00a0fa5b123446c3865b8df9432b458e", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: call delete endpoint when service is not found. What you expected to happen: It is no need to do delete in controller. Because in service restStorage, endpoint is deleted when delete service. See How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/area controller-manager /sig apps\n/kind bug", "commid": "kubernetes_issue_57745", "tokennum": 168}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cf74aa9c332e7889764cbf869b623d42f0f24b383520253935d08b825337f05d", "query": "kubelet := testKubelet.kubelet kubeClient := testKubelet.fakeKubeClient kubeClient.ReactFn = testclient.NewSimpleFake(&api.NodeList{Items: []api.Node{ <del> {ObjectMeta: api.ObjectMeta{Name: \"127.0.0.1\"}}, </del> <ins> {ObjectMeta: api.ObjectMeta{Name: testKubeletHostname}}, </ins> }}).ReactFn machineInfo := &cadvisorApi.MachineInfo{ MachineID:      \"123\",", "positive_passages": [{"docid": "doc-en-kubernetes-d16ca614c05197aa8b2652e3bf008c3a9a5ce41d960188a2ba3459b13d8b1102", "text": "Looks like some kubelet unit tests perform a lookupIp which ends up depending on the health of the local resolver. Specifically has this failing: Which leads to the test in: And we recently swapped out the node names from testnode to 127.0.0.1, so probably the culprit?\n/ref\nInteresting. I did swap out the node names in the unit test as part of to be 127.0.0.1, party because I thought that it wouldn't have any problems resolving during unit tests.\n/cc", "commid": "kubernetes_issue_8549", "tokennum": 113}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cf74aa9c332e7889764cbf869b623d42f0f24b383520253935d08b825337f05d", "query": "kubelet := testKubelet.kubelet kubeClient := testKubelet.fakeKubeClient kubeClient.ReactFn = testclient.NewSimpleFake(&api.NodeList{Items: []api.Node{ <del> {ObjectMeta: api.ObjectMeta{Name: \"127.0.0.1\"}}, </del> <ins> {ObjectMeta: api.ObjectMeta{Name: testKubeletHostname}}, </ins> }}).ReactFn machineInfo := &cadvisorApi.MachineInfo{ MachineID:      \"123\",", "positive_passages": [{"docid": "doc-en-kubernetes-4a4c75dd985aaeba56d487bbde17d68f0425afc5d7e1167fdf1a1abcb97cd0b6", "text": "cc\nWhat is the environment where you are running the tests? They pass for me on my mac, a linux box, and shippable seems to be passing them as well.\nI couldn 't reproduce the failure either.\nI'm out right now; i'll try them when i get back. For the record, I run hack/test- Paul Morie wrote:\nAhem FTR This acronym is going to go quad-plat Paul Morie wrote:\nI ran on both platforms and saw the tests pass.\nI'm still seeing it. Won't have bandwidth to dig in personally until tomorrow.\nseeing a similar failure after a git pull\nI knew I wasn't crazy\nenvironment: fedora 21, golang: 1.4, docker: 1.6\nI think I see the problem. When I set the node name to in the test I was assuming it would parse as a valid ip address and not end up at the LookupIP call. But only the node name (and not the kubelet hostname) is being set (except in my new test where I ) so it's trying to do a lookup. Do you think you could test just changing the default hostname from \"testnode\" to \"127.0.0.1\" and see if that fixes it for you?\nTrying now\nI still get failures but no panic / threaddump.\ngist coming\nthis looks like again?\nGood that it isn't panicing any longer. I can dig into the test failures tomorrow (I think it should be relatively simple to resolve).\ncool, thanks for looking\nPasses in master now for me. Closing.\nFYI, they will break again once goes in, and then we can merge my PR to see if that fixes it for you.\n:+1:\nis in -- are these tests breaking again?\nI just rebased which I think will fix them.\nThey are breaking again.\nis on it.", "commid": "kubernetes_issue_8522", "tokennum": 407}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cf78c739c70319e0436d8889f654fc28c5da1c1bd04fb9d7dccb5df0da71ab10", "query": "storageframework.BlockVolModeDynamicPV, storageframework.Ext4DynamicPV, storageframework.XfsDynamicPV, <ins> storageframework.NtfsDynamicPV, </ins> } return InitCustomMultiVolumeTestSuite(patterns) }", "positive_passages": [{"docid": "doc-en-kubernetes-2598e11fb35075705c3572da278160109a38df575ea6022e29df9bb46aaee489", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --ci-kubernetes-e2e-gci-gce-serial (gce-cos-master-serial) Four tests: Kubernetes e2e suite.[sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly] Kubernetes e2e suite.[sig-storage] In-tree Volumes [Driver: hostPath] [Testpattern: Inline-volume (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly] Kubernetes e2e suite.[sig-storage] In-tree Volumes [Driver: hostPathSymlink] [Testpattern: Inline-volume (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly] Kubernetes e2e suite.[sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should unmount if pod is force deleted while kubelet is down [Disruptive][Slow][LinuxOnly] is failing since June 29th 2021 (but the first failure was different than more recent ones). Commit , infra commit , . Other three tests are failing since July 9th 2021. Commit , infra commit , . Testgrid: https://k8s- Prow history: For CSI Volumes: For In-tree Volumes: There is another open issues for failing tests in this job: Failures reported there are about missing metrics, and were occuring before unmounting problems. So I opened a new issue, even though it's the same SIG. These tests don't look related to me, but I don't have enough context, maybe they somehow are. /sig storage /kind failing-test /milestone 1.22\nYou must be a member of the GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.", "commid": "kubernetes_issue_103651", "tokennum": 533}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cf78c739c70319e0436d8889f654fc28c5da1c1bd04fb9d7dccb5df0da71ab10", "query": "storageframework.BlockVolModeDynamicPV, storageframework.Ext4DynamicPV, storageframework.XfsDynamicPV, <ins> storageframework.NtfsDynamicPV, </ins> } return InitCustomMultiVolumeTestSuite(patterns) }", "positive_passages": [{"docid": "doc-en-kubernetes-fc6065ba1a9951ec296be8e3d5eed3592b7f58a8cbf0f7d83f44e7e6b4d2f288", "text": "<detailsIn response to : <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --ci-kubernetes-e2e-gci-gce-serial (gce-cos-master-serial) Four tests: Testgrid: https://k8s- Prow history: For CSI Volumes: For In-tree Volumes: #### Anything else we need to know: /kind failing-test /milestone 1.22 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\n/milestone v1.22\n/cc\n/cc (my close/reopen yesterday was accidental, sorry)\nI can take a look /assign\nThe non-subpath counterpart of this test is passing: These tests seem to use the default storageclass, whereas failing tests use in-tree hostpath and csi-hostpath\nThe CSI ones are failing because the hostpath driver never received a NodeUnstage (whereas it did in passing tests), causing the driver to error on volume deletion.\nIn the failed run kubelet has this error: which seems to have prevented kubelet from triggering a UnmountDevice. This error didn't exist in a successful run.\nHostpath driver can run with and without support for attach. Do you know which mode is enabled for this test?\nBetween the last passing time and when the test started failing, are there any PRs merged that look suspicious?\nAccording to csi-attacher logs, attach is disabled for both the good run and the failing run. Haven't spotted any obvious PRs so far, but I did find this: in the successful run, the log message for the successful is this: and the failed run: so the reconstructed volume names are somehow different. Checking reconstruction logic\nThis merged 12 days ago and was a pretty big change to pod lifecycle and could have trickling impact to volume manager. Does the timing of test failure match?\nThere is also this reconstruction fix that merged yesterday and seems related to outer vs inner spec name. I don't know if that will help fix this issue:\ncc\nLast successful run started at 7/8 17:49 PT, first failing run started at 7/9 2:23 PT.", "commid": "kubernetes_issue_103651", "tokennum": 491}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cf78c739c70319e0436d8889f654fc28c5da1c1bd04fb9d7dccb5df0da71ab10", "query": "storageframework.BlockVolModeDynamicPV, storageframework.Ext4DynamicPV, storageframework.XfsDynamicPV, <ins> storageframework.NtfsDynamicPV, </ins> } return InitCustomMultiVolumeTestSuite(patterns) }", "positive_passages": [{"docid": "doc-en-kubernetes-9f1333b0e960fd7acd243a96166fc71cf5883a52e7407e5f9400e1f08c54d3cf", "text": "was merged at 7/8 16:48 PT, so it's possible (if there's a delay in picking up master) Also this is in the failing kubelet logs but not in the successful one: I0720 18:20:42. ] \"Reconciler sync states: could not find volume information in desired state, clean up the mount points\" podName=-e508-45c2-8509- volumeSpecName=\"pvc--a615-4e89-afe8-\"\nFrom , the newly introduced log message here exists in the failing kubelet logs but not the successful one:\nFailures starting 07/08: /sig node for visibility\nI think caused the failures. Before after kubelet restarts, pod will still be in desired state (even through it is in terminating state), so that clean up mounts can be done completely. I think now, terminating pods will not be back to desired state, but reconstruction to actual state cannot completely clean up mounts. I am testing it about this.\nIs there a reason why reconstruction to actual state cannot clean up mounts? Note that a pod can be force deleted at any time, so a terminating pod that is force deleted would still have to be capable of being cleaned up (it won't be in desired state)? (note too that the expectation of the changes in is that terminating and fully terminated and \"never seen before\" should all completely equivalent from the perspective of other loops in the kubelet) If I understand you correctly, is this an existing bug that we're now triggering consistently?\nWe have both \"grace pod deletion\" and \"force pod deletion\" test cases that are failing.\nThere were a couple of key changes to volume loops in : Roughly before was \"it looks like it's got no running containers\", and after my change is \"we are going to be stopping all the containers from now on\". So this change meant that once a pod starts terminating, we are in \"tearing down mode\" and so my understanding of this method was that \"any pod where containers are being torn down is not in the desired state of the world\".", "commid": "kubernetes_issue_103651", "tokennum": 455}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cf78c739c70319e0436d8889f654fc28c5da1c1bd04fb9d7dccb5df0da71ab10", "query": "storageframework.BlockVolModeDynamicPV, storageframework.Ext4DynamicPV, storageframework.XfsDynamicPV, <ins> storageframework.NtfsDynamicPV, </ins> } return InitCustomMultiVolumeTestSuite(patterns) }", "positive_passages": [{"docid": "doc-en-kubernetes-015fa24d1e5eab79f6c5c1e5c14379be6e8185c1f089267f0bfc29a8792fef5f", "text": "After a restart, we would definitely not add a pod back that was in terminating state into desired state of the world, but \"restart + this change\" should be roughly equivalent to \"restart and force delete while restart is processing\" The other change was in which changed a live CRI read (which was trying to enforce that the dsowp is synchronized with the pod worker) into a threadsafe check against the pod worker directly (the pod worker can provide authoritative answers to \"this pod has no running containers\" now). The latter change seems less likely to impact you.\nThank you for the details! I think your change is making the right change, but unfortunately some of volume management still have issues, and so the tests rely on some behaviors that is not very right (pod volume is back to desired state even after it is in terminating) The cleanup mount currently does not have the logic to clean up global mount point if the volume plugin sets it up. I am still testing more and will share more details.\nis this a release blocker?\nYes, this impacts volume cleanup if kubelet restarts for any reason.\nOn a kube-up cluster running the latest master against the latest e2e binary, I was able to reproduce the in-tree failures but not the CSI ones for some reason. Will focus on in-tree failures for the time being\n/triage accepted\nmarking release-blocker per note on slack:\n/priority critical-urgent (once upon a time we used to not ship a release if any priority/critical-urgent issues were open, not sure if we decided to stop doing that)\nWe were able to find the trigger for the CSI failures - on 6/29 there was a change in the hostpath driver test manifest, and the driver's is enabled. This makes the driver return an error instead of only logging a warning message on if the volume isn't unstaged properly. IIUC there's a long standing issue that reconstruction doesn't handle node unstage. could you confirm? If that's the case, then these CSI failures are not release blocking. Furthermore, the CSI test with graceful delete started to fail on 7/9 because of since graceful and force deletes are now considered the same from the point of view of the volume manager. cc\nWhen that check was enabled, I don't think we realized it would impact the reconstruction path; it was enabled to validate a different issue.", "commid": "kubernetes_issue_103651", "tokennum": 504}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cf78c739c70319e0436d8889f654fc28c5da1c1bd04fb9d7dccb5df0da71ab10", "query": "storageframework.BlockVolModeDynamicPV, storageframework.Ext4DynamicPV, storageframework.XfsDynamicPV, <ins> storageframework.NtfsDynamicPV, </ins> } return InitCustomMultiVolumeTestSuite(patterns) }", "positive_passages": [{"docid": "doc-en-kubernetes-f86a5554f8df185db14256e7a7df5d445e052035a06405a03d3d05e494e0b68d", "text": "Are we running into the issue that reconstruction of staging directories isn't supported () OR is it that our reconstruction path requires drivers to have real mount points ()? Either way since both are known gaps with reconstruction, I think it makes sense to to disable the flag until we can address those issues.\nI was looking at this today too, trying to understand the underlying cause. That is why the failures are being reported now, but the part that I didn't understand is why NodeUnstageVolume is not being called for these volumes. In this instance: The DeleteVolume request fails because a staged path is still present: And in the kubelet log, NodeUnpublishVolume is called Then we hit this error: And NodeUnstageVolume is never called for this volume (same for other failures I looked at) so DeleteVolume keeps failing. So I think you're right that it's triggered by reconstruction, and it looks similar to , except in this case the restart happened before NodeUnpublishVolume.\nAnd it's probably not since the test uses a PVC\nWill look deeper into why UnmountDevice wasn't issued as well, but some update on the in-tree tests: the force delete test is skipped for the in-tree hostpath CSI driver because of Graceful tests are now failing as well because they behave like force tests due to\nI don't think the issue is related to PVC or not. I think it's related to drivers that do not actually mount devices as a separate filesystem than the root.\nThere are three possible flows during kubelet restart pod gracefully delete case, the pod still exists (it is not considered as terminated in function isPodTerminated(); note that this logic has some changes after , see , so pod volume will be back to desired state, and reconciler will try to set up volume and fill in actual state. When pod volume is finally deleted from desired state, reconciler will trigger teardown with information from actual state to unpublish and unstage volume. pod is forcefully deleted, pod volume will not be in desired state. If volume reconstruction succeeds (be able to reconstruct volume spec), volume will be back into actual state. Then reconciler will trigger teardown with information from actual state to unpublish and unstage volume (this part is similar to case 1).", "commid": "kubernetes_issue_103651", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cf78c739c70319e0436d8889f654fc28c5da1c1bd04fb9d7dccb5df0da71ab10", "query": "storageframework.BlockVolModeDynamicPV, storageframework.Ext4DynamicPV, storageframework.XfsDynamicPV, <ins> storageframework.NtfsDynamicPV, </ins> } return InitCustomMultiVolumeTestSuite(patterns) }", "positive_passages": [{"docid": "doc-en-kubernetes-0adb5aef0ac6855d53f98480f83c42da417641735fd51e124c8667d192575ced", "text": "last case is reconstruction failed (in this csi-host-path test, reconstruction will fail due to issue related to , it fail to check mount point for csi hostpath driver because it is using a bind mount of the same device ). In this case, reconciler will try to clean up mounts directly, but only published volume path, not the staged volume path (this logic is not implemented due to missing information). As a workaround, we can now disable check-volume-lifecycle if it does not cause other issues. Then we will work on to make sure csi-host-path driver can pass volume mountpoint check during reconstruction.\nThis issue is now mitigated with merged. There are two longer-term issues that are isolated to hostpath plugins (and maybe other plugins that are similar in behavior, perhaps emptydir and similar?): related to IsLikelyNotMountPoint as mentioned. Because these don't impact the core volume machinery and are not regressions, this issue doesn't need to be release blocking. We'll close this issue once (2) is tracked.\nis the IsLikelyNotMountPoint issue\nafter is merged, two csi-hostpath driver subpath test can pass, and two in-tree driver gracefully delete tests were skipped. https://k8s-\ncan you please cherry-pick to release-1.22 branch?\nOpened cherry-pick, please review:\n- what is the plan for reenabling them?\ncherry-pick merged!\nCheng and I will work on solving IsLikelyNotMountPoint issue for hostpath drivers. That should allow test to pass and we can enable them.\nCan this be removed from the milestone now that the workarounds have been merged, while leaving this issue open to track further work?\nWe can use existing issue to track the real fix. /close\nClosing this issue. <detailsIn response to : We can use existing issue to track the real fix. 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", "commid": "kubernetes_issue_103651", "tokennum": 438}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cf81d017bed6dcf92187b7ceba105fca9a092d0914574c3e4dc4c25c3fa69b59", "query": "for k, tc := range testcases { tcName := k path := \"/apis/\" + tc.APIService.Spec.Group + \"/\" + tc.APIService.Spec.Version + \"/foo\" <del> called := false </del> <ins> timesCalled := int32(0) </ins> func() { // Cleanup after each test case. backendHandler := http.NewServeMux() backendHandler.Handle(path, websocket.Handler(func(ws *websocket.Conn) { <ins> atomic.AddInt32(&timesCalled, 1) </ins> defer ws.Close() body := make([]byte, 5) ws.Read(body) ws.Write([]byte(\"hello \" + string(body))) <del> called = true </del> })) backendServer := httptest.NewUnstartedServer(backendHandler)", "positive_passages": [{"docid": "doc-en-kubernetes-dde8d0812f4d036029fc33418cfa6f164f8f025662aa48e3db09b87dd15763e4", "text": "There are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig api-machinery", "commid": "kubernetes_issue_49413", "tokennum": 102}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cfa7e54684e5748eb63527da8392cc92a830a99a6ea12398a9df325a04c6dccc", "query": "obj.MakeIPTablesUtilChains = boolVar(true) } if obj.IPTablesMasqueradeBit == nil { <del> temp := int32(defaultIPTablesMasqueradeBit) </del> <ins> temp := int32(DefaultIPTablesMasqueradeBit) </ins> obj.IPTablesMasqueradeBit = &temp } if obj.IPTablesDropBit == nil { <del> temp := int32(defaultIPTablesDropBit) </del> <ins> temp := int32(DefaultIPTablesDropBit) </ins> obj.IPTablesDropBit = &temp } if obj.CgroupsPerQOS == nil {", "positive_passages": [{"docid": "doc-en-kubernetes-937f1cb17c20e5fd2b4a1f81201690c3dbe6990ef3c1bc74ff71daaa02b6db56", "text": "Solution: I will add one.\n/cc\nxref\nThanks for sending a PR so quickly!\n[MILESTONENOTIFIER] Milestone Issue Needs Attention Action required: During code slush, issues in the milestone should be in progress. If this issue is not being actively worked on, please remove it from the milestone. If it is being worked on, please add the label so it can be tracked with other in-flight issues. Note: If this issue is not resolved or labeled as by Wed, Nov 22 it will be moved out of the v1.9 milestone. <details<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details", "commid": "kubernetes_issue_55959", "tokennum": 230}], "negative_passages": []}
{"query_id": "q-en-kubernetes-cfb4f850ce7ba5dd6f722dfe239f46333d1562a83c188fc0f362bfe09e2fcdc0", "query": "// This ensures the given VM's Primary NIC's Primary IP Configuration is // participating in the specified LoadBalancer Backend Pool. func (az *Cloud) ensureHostInPool(serviceName string, nodeName types.NodeName, backendPoolID string) error { <ins> var machine compute.VirtualMachine </ins> vmName := mapNodeNameToVMName(nodeName) az.operationPollRateLimiter.Accept() machine, err := az.VirtualMachinesClient.Get(az.ResourceGroup, vmName, \"\") if err != nil { <del> return err </del> <ins> if az.CloudProviderBackoff { glog.V(2).Infof(\"ensureHostInPool(%s, %s, %s) backing off\", serviceName, nodeName, backendPoolID) machine, err = az.VirtualMachineClientGetWithRetry(az.ResourceGroup, vmName, \"\") if err != nil { glog.V(2).Infof(\"ensureHostInPool(%s, %s, %s) abort backoff\", serviceName, nodeName, backendPoolID) return err } } else { return err } </ins> } primaryNicID, err := getPrimaryInterfaceID(machine)", "positive_passages": [{"docid": "doc-en-kubernetes-0f3fba1dceb9c94d1a19ea07536eb93382a47fa8d74b43be2f3310b5be7e4348", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: In certain large cluster scenarios we would like to anticipate kubelet behavior hitting request limits, and backoff in response. E.g., What you expected to happen: This is a request for add'l backoff coverage, so nothing surprising. How to reproduce it (as minimally and precisely as possible): Build a cluster with as many nodes as your subscription will support on azure until kubelet behavior contributes to backend API request limits. Environment: Kubernetes version (use ): and Cloud provider or hardware configuration**: azure OS (e.g. from /etc/os-release): Ubuntu 16.04.2 LTS (Xenial Xerus) Kernel (e.g. ): Linux k8s-pool7--7 4.4.0-83-generic -Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x8664 x8664 x86_64 GNU/Linux Install tools: acs-engine Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig azure", "commid": "kubernetes_issue_48971", "tokennum": 358}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d02406f639b9a6c0ddfef46d29198ec4261c71639a3ea48bbcbea07b087d3dd7", "query": "// GetPrimaryInterface gets machine primary network interface by node name and vmSet. func (ss *scaleSet) GetPrimaryInterface(nodeName, vmSetName string) (network.Interface, error) { <del> ssName, instanceID, vm, err := ss.getVmssVM(nodeName) </del> <ins> managedByAS, err := ss.isNodeManagedByAvailabilitySet(nodeName) </ins> if err != nil { <del> if err == ErrorNotVmssInstance { glog.V(4).Infof(\"GetPrimaryInterface: node %q is managed by availability set\", nodeName) // Retry with standard type because nodes are not managed by vmss. return ss.availabilitySet.GetPrimaryInterface(nodeName, \"\") } </del> <ins> glog.Errorf(\"Failed to check isNodeManagedByAvailabilitySet: %v\", err) return network.Interface{}, err } if managedByAS { // vm is managed by availability set. return ss.availabilitySet.GetPrimaryInterface(nodeName, \"\") } </ins> <del> glog.Errorf(\"error: ss.GetPrimaryInterface(%s), ss.getCachedVirtualMachine(%s), err=%v\", nodeName, nodeName, err) </del> <ins> ssName, instanceID, vm, err := ss.getVmssVM(nodeName) if err != nil { glog.Errorf(\"error: ss.GetPrimaryInterface(%s), ss.getVmssVM(%s), err=%v\", nodeName, nodeName, err) </ins> return network.Interface{}, err }", "positive_passages": [{"docid": "doc-en-kubernetes-98264fae63e9d149f0171dd13218170b598f5e330429a04234e4c80f3d1b23d2", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: VMAS nodes are reporting error in vmss cluster (vmType set to vmss). What you expected to happen: Node should register correctly in the kubernetes cluster. How to reproduce it (as minimally and precisely as possible): Create a VMAS nodes inside vmss cluster. Anything else we need to know?: Environment: Kubernetes version (use ): master Cloud provider or hardware configuration: azure OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/sig azure", "commid": "kubernetes_issue_60185", "tokennum": 165}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d024d7c729b69e5c6d76e0df8e4dd791b6c27d3bab099222ec7b7e8beda5c126", "query": "AppArmor:                                    {Default: true, PreRelease: utilfeature.Beta}, DynamicKubeletConfig:                        {Default: false, PreRelease: utilfeature.Alpha}, KubeletConfigFile:                           {Default: false, PreRelease: utilfeature.Alpha}, <del> DynamicVolumeProvisioning:                   {Default: true, PreRelease: utilfeature.Alpha}, </del> ExperimentalHostUserNamespaceDefaultingGate: {Default: false, PreRelease: utilfeature.Beta}, ExperimentalCriticalPodAnnotation:           {Default: false, PreRelease: utilfeature.Alpha}, Accelerators:                                {Default: false, PreRelease: utilfeature.Alpha},", "positive_passages": [{"docid": "doc-en-kubernetes-9bc3939632f91b367e9735795407824b8635b986a1aa4d3e42f19abbece1efa5", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: kube-apiserver --help still shows this: It looks like the related feature can be turned off. However, dynamic volume provisioning Alpha has retried in 1.6. What you expected to happen: Remove from feature gate to avoid confusion. How to reproduce it (as minimally and precisely as possible): Run Anything else we need to know?: No Environment: Kubernetes version (use ): 1.7+ Cloud provider or hardware configuration**: Any OS (e.g. from /etc/os-release): Any Kernel (e.g. ): Any Install tools: Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig api-machinery\n/sig api-machinery\nSIG API Machinery doesn't own the contents of the API. /sig storage", "commid": "kubernetes_issue_51120", "tokennum": 274}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d0e09438f698f1a4749d05e612627fdf21e77acc3710af797da9fd15effa81b6", "query": "tags = [\"automanaged\"], visibility = [\"//visibility:public\"], ) <ins> go_test( name = \"go_default_test\", srcs = [\"testutil_test.go\"], embed = [\":go_default_library\"], deps = [\"//staging/src/k8s.io/component-base/metrics:go_default_library\"], ) </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-b57bf0f1b2dd71c1293d1dafb95c6e51debc5c1d26878053edb8d335b76a3a11", "text": "What would you like to be : Once a metric be deprecated, we should update the unit test accordingly if there is any. We need to work out a way for a unit test freely select codebase version, and also should make sure the unit test won't fail in the subsequent release. Why is this needed: Deprecated also needs to be protected. /sig instrumentation /assign", "commid": "kubernetes_issue_86292", "tokennum": 81}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d0e5e9706d6988d35166e81f1bbec04c952b90b977d8d1497da63508ece84c72", "query": "return GatherAndCompare(registry, expected, metricNames...) } <ins> // NewFakeKubeRegistry creates a fake `KubeRegistry` that takes the input version as `build in version`. // It should only be used in testing scenario especially for the deprecated metrics. // The input version format should be `major.minor.patch`, e.g. '1.18.0'. func NewFakeKubeRegistry(ver string) metrics.KubeRegistry { backup := metrics.BuildVersion defer func() { metrics.BuildVersion = backup }() metrics.BuildVersion = func() apimachineryversion.Info { return apimachineryversion.Info{ GitVersion: fmt.Sprintf(\"v%s-alpha+1.12345\", ver), } } return metrics.NewKubeRegistry() } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-b57bf0f1b2dd71c1293d1dafb95c6e51debc5c1d26878053edb8d335b76a3a11", "text": "What would you like to be : Once a metric be deprecated, we should update the unit test accordingly if there is any. We need to work out a way for a unit test freely select codebase version, and also should make sure the unit test won't fail in the subsequent release. Why is this needed: Deprecated also needs to be protected. /sig instrumentation /assign", "commid": "kubernetes_issue_86292", "tokennum": 81}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d153a2548db4732d19bfb6c5a16fedb982ebdb5cc36a4035dc0c227ad6d4e599", "query": "containers, _ := selectContainers(spec.Containers, o.ContainerSelector) if len(containers) != 0 { for i := range containers { <del> if len(o.Limits) != 0 && len(containers[i].Resources.Limits) == 0 { containers[i].Resources.Limits = make(api.ResourceList) } for key, value := range o.ResourceRequirements.Limits { containers[i].Resources.Limits[key] = value } if len(o.Requests) != 0 && len(containers[i].Resources.Requests) == 0 { containers[i].Resources.Requests = make(api.ResourceList) } for key, value := range o.ResourceRequirements.Requests { containers[i].Resources.Requests[key] = value } </del> <ins> containers[i].Resources = o.ResourceRequirements </ins> transformed = true } } else {", "positive_passages": [{"docid": "doc-en-kubernetes-f45c12318e35043c65362c27e361ee13adfef369e183f2b4f0557c11353bd9e9", "text": "from https://k8s-\nReally suspect this is\nThis is putting us into test-go post-commit run is broken\ncc:\nmarked this p0 - if a fix isn't easy let's try to identify what introduced this and revert.\nThis flake on: 2016-10-30 07:19 PDT First instance: : It is flaking frequently, blocking PRs from getting merged, and slowing the submit queue ( at 75%). As on-call, I'm going to try and identify the cluprit and revert. Can use all help in doing so.\ncan you investigate whether your additional tests could cause this (by breaking the deployment of those pods, for instance) , Saad Ali wrote:\nPR looks most suspect to me. It mucked with , and the errors we are seeing in each of the failures is related to : That PR was merged at Oct 30, 2016, 6:18 AM PDT and the first flake in was at Oct 30, 2016, 7:19 AM PDT. Thoughts? CC\nI'm going to initiate a revert of to see if that fixes the issue\nIMO we can just change the flaky test to not get pods but some other resources, such as deployments. We can't really expect to clean up pods immediately.\nI'm going to proceed with revert (). Please feel free to send a follow up PR to handle this more gracefully.\nGoing to leave this opened until we have a few hours of runs with the revert. Want to verify, with some degree of certainty, that the revert took care of this flake.\nWe had 15 green runs of in a row. Considering this flake fixed.", "commid": "kubernetes_issue_35898", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d20d3c4c7e590cfd60ac1f75c4b53673cd9bbca32e3294e6fb83435e05856d3b", "query": "# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE # INSTRUCTIONS AT https://kubernetes.io/security/ <del> cjcullen joelsmith liggitt philips </del> <ins> cheftako deads2k lavalamp </ins> sttts <del> tallclair </del>", "positive_passages": [{"docid": "doc-en-kubernetes-4c28255cc86038c3c93f9e461780faa3ed1b46443f53f929b0e421cdbd186a35", "text": "The purpose of the file for each Kubernetes repository is to provide a list of people who can assist the Kubernetes in the event that a security issue related to the repository is discovered or disclosed. As described in the file, those on the list should agree to our . Please update the  file for the sample-controller repository. After finding people who are willing to work in this capacity, you should add them to the list, then remove PSC members (except any PSC member will be working as a security contact for this repository). The list is GitHub usernames, optionally followed by an email address. If no email address is listed, the PSC will use the email address found on git commits made by the listed user. The file may already have people listed who are secuirty contacts. In that case, simply remove any PSC members who aren't also security contacts for the repo. See for more information /area security /committee product-security /kind cleanup /lifecycle frozen /priority important-soon /sig api-machinery", "commid": "kubernetes_issue_92105", "tokennum": 223}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d20d3c4c7e590cfd60ac1f75c4b53673cd9bbca32e3294e6fb83435e05856d3b", "query": "# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE # INSTRUCTIONS AT https://kubernetes.io/security/ <del> cjcullen joelsmith liggitt philips </del> <ins> cheftako deads2k lavalamp </ins> sttts <del> tallclair </del>", "positive_passages": [{"docid": "doc-en-kubernetes-33911e735262f8481400ca2430d671c6536468b71d87ed87bbe4f11626c79fd6", "text": "The purpose of the file for each Kubernetes repository is to provide a list of people who can assist the Kubernetes in the event that a security issue related to the repository is discovered or disclosed. As described in the file, those on the list should agree to our . Please update the  file for the sample-apiserver repository. After finding people who are willing to work in this capacity, you should add them to the list, then remove PSC members (except any PSC member will be working as a security contact for this repository). The list is GitHub usernames, optionally followed by an email address. If no email address is listed, the PSC will use the email address found on git commits made by the listed user. The file may already have people listed who are secuirty contacts. In that case, simply remove any PSC members who aren't also security contacts for the repo. See for more information /area security /committee product-security /kind cleanup /lifecycle frozen /priority important-soon /sig api-machinery", "commid": "kubernetes_issue_92103", "tokennum": 225}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d20d3c4c7e590cfd60ac1f75c4b53673cd9bbca32e3294e6fb83435e05856d3b", "query": "# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE # INSTRUCTIONS AT https://kubernetes.io/security/ <del> cjcullen joelsmith liggitt philips </del> <ins> cheftako deads2k lavalamp </ins> sttts <del> tallclair </del>", "positive_passages": [{"docid": "doc-en-kubernetes-575caba005fa0a194c5e9ab05a9e30ee6530f864ab126bf649eed87c7efec61c", "text": "The purpose of the file for each Kubernetes repository is to provide a list of people who can assist the Kubernetes in the event that a security issue related to the repository is discovered or disclosed. As described in the file, those on the list should agree to our . Please update the  file for the kube-aggregator repository. After finding people who are willing to work in this capacity, you should add them to the list, then remove PSC members (except any PSC member will be working as a security contact for this repository). The list is GitHub usernames, optionally followed by an email address. If no email address is listed, the PSC will use the email address found on git commits made by the listed user. The file may already have people listed who are secuirty contacts. In that case, simply remove any PSC members who aren't also security contacts for the repo. See for more information /area security /committee product-security /kind cleanup /lifecycle frozen /priority important-soon /sig api-machinery", "commid": "kubernetes_issue_92095", "tokennum": 224}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d20d3c4c7e590cfd60ac1f75c4b53673cd9bbca32e3294e6fb83435e05856d3b", "query": "# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE # INSTRUCTIONS AT https://kubernetes.io/security/ <del> cjcullen joelsmith liggitt philips </del> <ins> cheftako deads2k lavalamp </ins> sttts <del> tallclair </del>", "positive_passages": [{"docid": "doc-en-kubernetes-f1cb8df6316e5a200598bb646e70f7d130ec0c75fc9f39b3e957189b80c10ad2", "text": "The purpose of the file for each Kubernetes repository is to provide a list of people who can assist the Kubernetes in the event that a security issue related to the repository is discovered or disclosed. As described in the file, those on the list should agree to our . Please update the  file for the code-generator repository. After finding people who are willing to work in this capacity, you should add them to the list, then remove PSC members (except any PSC member will be working as a security contact for this repository). The list is GitHub usernames, optionally followed by an email address. If no email address is listed, the PSC will use the email address found on git commits made by the listed user. The file may already have people listed who are secuirty contacts. In that case, simply remove any PSC members who aren't also security contacts for the repo. See for more information /area code-generation /area security /committee product-security /kind cleanup /lifecycle frozen /priority important-soon /sig api-machinery", "commid": "kubernetes_issue_92091", "tokennum": 228}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d20d3c4c7e590cfd60ac1f75c4b53673cd9bbca32e3294e6fb83435e05856d3b", "query": "# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE # INSTRUCTIONS AT https://kubernetes.io/security/ <del> cjcullen joelsmith liggitt philips </del> <ins> cheftako deads2k lavalamp </ins> sttts <del> tallclair </del>", "positive_passages": [{"docid": "doc-en-kubernetes-b6c24ff2339a072ce41f583a86461ffd390f0efd073046044ccabd0e8baad713", "text": "The purpose of the file for each Kubernetes repository is to provide a list of people who can assist the Kubernetes in the event that a security issue related to the repository is discovered or disclosed. As described in the file, those on the list should agree to our . Please update the  file for the client-go repository. After finding people who are willing to work in this capacity, you should add them to the list, then remove PSC members (except any PSC member will be working as a security contact for this repository). The list is GitHub usernames, optionally followed by an email address. If no email address is listed, the PSC will use the email address found on git commits made by the listed user. The file may already have people listed who are secuirty contacts. In that case, simply remove any PSC members who aren't also security contacts for the repo. See for more information /area security /committee product-security /kind cleanup /lifecycle frozen /priority important-soon /sig api-machinery", "commid": "kubernetes_issue_92088", "tokennum": 223}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d20d3c4c7e590cfd60ac1f75c4b53673cd9bbca32e3294e6fb83435e05856d3b", "query": "# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE # INSTRUCTIONS AT https://kubernetes.io/security/ <del> cjcullen joelsmith liggitt philips </del> <ins> cheftako deads2k lavalamp </ins> sttts <del> tallclair </del>", "positive_passages": [{"docid": "doc-en-kubernetes-773ad9c7c77ed09f247ebe6fe4a2e977a2482d0db8567e965fc0d687730a34f0", "text": "The purpose of the file for each Kubernetes repository is to provide a list of people who can assist the Kubernetes in the event that a security issue related to the repository is discovered or disclosed. As described in the file, those on the list should agree to our . Please update the  file for the apiserver repository. After finding people who are willing to work in this capacity, you should add them to the list, then remove PSC members (except any PSC member will be working as a security contact for this repository). The list is GitHub usernames, optionally followed by an email address. If no email address is listed, the PSC will use the email address found on git commits made by the listed user. The file may already have people listed who are secuirty contacts. In that case, simply remove any PSC members who aren't also security contacts for the repo. See for more information /area apiserver /area security /committee product-security /kind cleanup /lifecycle frozen /priority important-soon /sig api-machinery", "commid": "kubernetes_issue_92087", "tokennum": 228}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d20d3c4c7e590cfd60ac1f75c4b53673cd9bbca32e3294e6fb83435e05856d3b", "query": "# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE # INSTRUCTIONS AT https://kubernetes.io/security/ <del> cjcullen joelsmith liggitt philips </del> <ins> cheftako deads2k lavalamp </ins> sttts <del> tallclair </del>", "positive_passages": [{"docid": "doc-en-kubernetes-fad8ee5585f13cbd059c3b23e9b0beba24a9e5cc8dc4cbda61f103e29d873595", "text": "The purpose of the file for each Kubernetes repository is to provide a list of people who can assist the Kubernetes in the event that a security issue related to the repository is discovered or disclosed. As described in the file, those on the list should agree to our . Please update the  file for the apimachinery repository. After finding people who are willing to work in this capacity, you should add them to the list, then remove PSC members (except any PSC member will be working as a security contact for this repository). The list is GitHub usernames, optionally followed by an email address. If no email address is listed, the PSC will use the email address found on git commits made by the listed user. The file may already have people listed who are secuirty contacts. In that case, simply remove any PSC members who aren't also security contacts for the repo. See for more information /area security /committee product-security /kind cleanup /lifecycle frozen /priority important-soon /sig api-machinery", "commid": "kubernetes_issue_92085", "tokennum": 224}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d20d3c4c7e590cfd60ac1f75c4b53673cd9bbca32e3294e6fb83435e05856d3b", "query": "# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE # INSTRUCTIONS AT https://kubernetes.io/security/ <del> cjcullen joelsmith liggitt philips </del> <ins> cheftako deads2k lavalamp </ins> sttts <del> tallclair </del>", "positive_passages": [{"docid": "doc-en-kubernetes-df9e56efa1a5d0dfe5cf4c9ff5d0ae22d67682beafe379ced520bca8e339d7ed", "text": "The purpose of the file for each Kubernetes repository is to provide a list of people who can assist the Kubernetes in the event that a security issue related to the repository is discovered or disclosed. As described in the file, those on the list should agree to our . Please update the  file for the apiextensions-apiserver repository. After finding people who are willing to work in this capacity, you should add them to the list, then remove PSC members (except any PSC member will be working as a security contact for this repository). The list is GitHub usernames, optionally followed by an email address. If no email address is listed, the PSC will use the email address found on git commits made by the listed user. The file may already have people listed who are secuirty contacts. In that case, simply remove any PSC members who aren't also security contacts for the repo. See for more information /area security /committee product-security /kind cleanup /lifecycle frozen /priority important-soon /sig api-machinery", "commid": "kubernetes_issue_92084", "tokennum": 228}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d23f797cc7123e7970e949643b11654b86ac75c755afb78e3e8b91604dbb899c", "query": "} defer CleanupDescriptors(gcmService, projectID) <del> err = CreateAdapter(f.Namespace.Name, adapterDeployment) </del> <ins> err = CreateAdapter(adapterDeployment) </ins> if err != nil { framework.Failf(\"Failed to set up: %s\", err) } <del> defer CleanupAdapter(f.Namespace.Name, adapterDeployment) </del> <ins> defer CleanupAdapter(adapterDeployment) </ins> _, err = kubeClient.RbacV1().ClusterRoleBindings().Create(context.TODO(), HPAPermissions, metav1.CreateOptions{}) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-cecee0a132f84dbf6d5783d328e94b49c8666ebba8eef4ded1687e53b0451e97", "text": "/kind failing-test <!-- If this is a flake, please add: /kind flake --/sig autoscaling Looks like it just started happening today (@ 2020-09-15 03:54:19 +0000 UTC) !\ncc the namespace from the provided object \"kube-system\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=kube-system' to perform this operation. the namespace from the provided object \"custom-metrics\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=custom-metrics' to perform this operation. the namespace from the provided object \"custom-metrics\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=custom-metrics' to perform this operation.\nrelated fix:\nNo I don't think that's the fix for this (that is just a little cleanup). Actually I think we have to delete namespace parameter in line : Because before , the will have no actually effect. But now with the change of , it will have namespace : at the end of the command. But the namespace in yaml file is which is different from . We should not have parameter when applying from file because this test didn't have before, right? Related PR:\n/assign", "commid": "kubernetes_issue_94809", "tokennum": 318}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d2540c90ee1ede6826ea9093c8ecd7c68a3ef6e8c46653d6191ae3a0bb462081", "query": "BackendAddressPool: &network.SubResource{ ID: to.StringPtr(lbBackendPoolID), }, <del> LoadDistribution: loadDistribution, FrontendPort:     to.Int32Ptr(port.Port), BackendPort:      to.Int32Ptr(port.Port), EnableFloatingIP: to.BoolPtr(true), </del> <ins> LoadDistribution:    loadDistribution, FrontendPort:        to.Int32Ptr(port.Port), BackendPort:         to.Int32Ptr(port.Port), EnableFloatingIP:    to.BoolPtr(true), DisableOutboundSnat: to.BoolPtr(az.disableLoadBalancerOutboundSNAT()), </ins> }, } if protocol == v1.ProtocolTCP {", "positive_passages": [{"docid": "doc-en-kubernetes-f91ac3317a925ac3a02c50dc39021d458d6020da9f69361ec2732a68459b1b7c", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: is the recommended way to configure the outbound networks together with Azure standard loadbalancer (SLB). However, for load balancer rules are disabled by default. That means all frontend IPs would be used as the SNAT IPs for virtual machines, according to . This would introduce troubles for various security scenarios, as there's no way to get a stable list of egress IPs. Azure cloud provider should support this scenario, and disable the outbound SNAT when outbound rules are configured by provisioning tools. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Others: /kind bug /sig azure /priority critical-urgent", "commid": "kubernetes_issue_75281", "tokennum": 247}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d28d5d9a47a497a7f3ead66897b00acd53fc6f6d82bd20b9b60626e2c179785e", "query": "assert.Equal(c.groupCalls, 2) } <ins> func TestNewCachedDiscoveryClient_PathPerm(t *testing.T) { assert := assert.New(t) d, err := ioutil.TempDir(\"\", \"\") assert.NoError(err) os.RemoveAll(d) defer os.RemoveAll(d) c := fakeDiscoveryClient{} cdc := newCachedDiscoveryClient(&c, d, 1*time.Nanosecond) cdc.ServerGroups() err = filepath.Walk(d, func(path string, info os.FileInfo, err error) error { if err != nil { return err } if info.IsDir() { assert.Equal(os.FileMode(0750), info.Mode().Perm()) } else { assert.Equal(os.FileMode(0660), info.Mode().Perm()) } return nil }) assert.NoError(err) } </ins> type fakeDiscoveryClient struct { groupCalls    int resourceCalls int", "positive_passages": [{"docid": "doc-en-kubernetes-30e07950978ed617c12104c8342559dfe477718ba7eb61f98c21f95bb37c1439", "text": "In kubectl v1.8.0+, schema info is cached in the location specified by (defaulting to ), written with world-writeable permissions (rw-rw-rw-). If is specified and pointed at a different location accessible to other users/groups, the written files may be modified by other users/groups and disrupt the kubectl invocation. CVSS score: CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N (3.3, low) What versions are affected? kubectl v1.8.0+ What configurations are affected? Invocations that point at world-writeable locations Impact Malformed responses written to the cache directory can disrupt the kubectl invocation Workaround Use the default location in the $HOME directory or point it at a directory that is only accessible to desired users/groups. (original description follows) ==== What happened: The files inside of \".kube/http-cache\" are world writeable (rw-rw-rw-). While the default for these files appears to be the home directory, using the \"--cache-dir\" flag could put these files into a place where world writeable files would allow any user / process to modify the cache files. Modification of the cache files could influence the kubectl utility in a negative way for other users. What you expected to happen: Apply stricter file permissions to the http-cache files. How to reproduce it (as minimally and precisely as possible): Run any generic kubectl command which is successful and then list the cache directory $ kubectl get pods --all-namespaces $ ls -la Anything else we need to know?", "commid": "kubernetes_issue_76676", "tokennum": 398}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d28d5d9a47a497a7f3ead66897b00acd53fc6f6d82bd20b9b60626e2c179785e", "query": "assert.Equal(c.groupCalls, 2) } <ins> func TestNewCachedDiscoveryClient_PathPerm(t *testing.T) { assert := assert.New(t) d, err := ioutil.TempDir(\"\", \"\") assert.NoError(err) os.RemoveAll(d) defer os.RemoveAll(d) c := fakeDiscoveryClient{} cdc := newCachedDiscoveryClient(&c, d, 1*time.Nanosecond) cdc.ServerGroups() err = filepath.Walk(d, func(path string, info os.FileInfo, err error) error { if err != nil { return err } if info.IsDir() { assert.Equal(os.FileMode(0750), info.Mode().Perm()) } else { assert.Equal(os.FileMode(0660), info.Mode().Perm()) } return nil }) assert.NoError(err) } </ins> type fakeDiscoveryClient struct { groupCalls    int resourceCalls int", "positive_passages": [{"docid": "doc-en-kubernetes-03c8940a04bf023e0d3632a105949b7e85efda694ffafea56ecb99998a766122", "text": ": I estimate this is a low severity security issue with a CVSS score of \"3.3 / CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N\" - Environment: Linux Kubernetes version (use kubectl version):Client Version: version.Info{Major:\"1\", Minor:\"12\", GitVersion:\"v1.12.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2019-02-26T12:49:28Z\", GoVersion:\"go1.10.8\", Compiler:\"gc\", Platform:\"linux/amd64\"} Server Version: version.Info{Major:\"1\", Minor:\"12\", GitVersion:\"v1.12.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2019-02-26T12:49:28Z\", GoVersion:\"go1.10.8\", Compiler:\"gc\", Platform:\"linux/amd64\"} Cloud provider or hardware configuration: AWS. Running kube api server in hyperkube. OS (e.g: cat /etc/os-release): NAME=\"CentOS Linux\" VERSION=\"7.1808 (Core)\" ID=\"centos\" IDLIKE=\"rhel fedora\" VERSIONID=\"7\" PRETTYNAME=\"CentOS Linux 7.1808 (Core)\" ANSICOLOR=\"0;31\" CPENAME=\"cpe:/o:centos:centos:7\" HOMEURL=\"\" BUGREPORTURL=\"\" CENTOSMANTISBTPROJECT=\"CentOS-7\" CENTOSMANTISBTPROJECTVERSION=\"7\" REDHATSUPPORTPRODUCT=\"centos\" REDHATSUPPORTPRODUCTVERSION=\"7\" OSTREEVERSION=7.1808 Kernel (e.g. uname -a): Linux hackit.internal 3.10.0-862.11.6.el7.x8664 SMP Tue Aug 14 21:49:04 UTC 2018 x8664 x8664 x86_64 GNU/Linux Install tools: Manual installation. Others: n/a\n/sig product-security\nClosing this issue. <detailsIn response to : if you think this is serious, send an email thanks!", "commid": "kubernetes_issue_76676", "tokennum": 565}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d28d5d9a47a497a7f3ead66897b00acd53fc6f6d82bd20b9b60626e2c179785e", "query": "assert.Equal(c.groupCalls, 2) } <ins> func TestNewCachedDiscoveryClient_PathPerm(t *testing.T) { assert := assert.New(t) d, err := ioutil.TempDir(\"\", \"\") assert.NoError(err) os.RemoveAll(d) defer os.RemoveAll(d) c := fakeDiscoveryClient{} cdc := newCachedDiscoveryClient(&c, d, 1*time.Nanosecond) cdc.ServerGroups() err = filepath.Walk(d, func(path string, info os.FileInfo, err error) error { if err != nil { return err } if info.IsDir() { assert.Equal(os.FileMode(0750), info.Mode().Perm()) } else { assert.Equal(os.FileMode(0660), info.Mode().Perm()) } return nil }) assert.NoError(err) } </ins> type fakeDiscoveryClient struct { groupCalls    int resourceCalls int", "positive_passages": [{"docid": "doc-en-kubernetes-5f4971cee99e57062ae7961121de35cc677214a3e6ca77682b093e74b00a9b30", "text": "</details\nAdjusted the CVSS score to to indicate user interaction is required (since they must specify a non-default cache option pointed at a shared writeable location)\nThere are two places this should be done: PathPerm and FilePerm should be set here: the temp file and final file should have stricter permissions (probably 0660) here:\n/cc\n/help\nThis request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\n/assign I would like to work on release-1.9, as I just made a hot fix for our team's k8s version of 1.9.\nGitHub didn't allow me to assign the following users: yuchengwu. Note that only and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign I would like to work on release-1.9, as I just made a hot fix for our team's k8s version of 1.9. 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\nhelp fixing this is welcome, though it would only be fixed in releases 1.12+, per\n/label official-cve-feed (Related to kubernetes/sig-security)", "commid": "kubernetes_issue_76676", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d2f8dd8ba4d882d7774c610701aac28e324f9d0e781561c2bc7ae6641b496548", "query": "// Wraps syscall.Mount() func (mounter *DiskMounter) Mount(source string, target string, fstype string, flags uintptr, data string) error { <ins> glog.V(5).Infof(\"Mounting %s %s %s %d %s\", source, target, fstype, flags, data) </ins> return syscall.Mount(source, target, fstype, flags, data) }", "positive_passages": [{"docid": "doc-en-kubernetes-4cc03be8a4c78b1eefdd458c17e35e10d17eae1288a6e1bcb08b9d7d585d4633", "text": "07-02 and 13-02 No response No response /sig\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scalability\nI might be related to the npd.\nThe same test failures happening again on 25.02:\n/sig node\n/sig node /cc The restart of caused the flake. I also opened to track it in NPD repo.\nI missed this log. It is caused by oom. Adding some memory may help. I submitted to fix it. Does mean killing metrics-server?\n/remove-sig node Sorry, I misread the log. The NPD found the metric server is OOM. It is about the metrics server, not the NPD. Sorry for disturb. I may add some memory for metric-server and check why metric server memory changed. I heard that metrics server recently released a new version. I will check if it is related.\n/sig node\nOOM metrics shows the metric server is OOMed. This is odd, that only metrics-server-nanny is with a memory limit. It uses whose command is . metrics-server container has no memory limit, but it got killed by OOM. Does this indicate that the node is OOM? (edited)\nThe last run failed in node-problem-detector ContainerStateTerminated. I0227 05:03:31. ] PodStartupLatency: perc50: 14m29.018886827s, perc90: 28m44.625518807s, perc99: 32m2.19303496s; threshold 1h0m0s I0227 05:03:32. ]", "commid": "kubernetes_issue_123328", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d2f8dd8ba4d882d7774c610701aac28e324f9d0e781561c2bc7ae6641b496548", "query": "// Wraps syscall.Mount() func (mounter *DiskMounter) Mount(source string, target string, fstype string, flags uintptr, data string) error { <ins> glog.V(5).Infof(\"Mounting %s %s %s %d %s\", source, target, fstype, flags, data) </ins> return syscall.Mount(source, target, fstype, flags, data) }", "positive_passages": [{"docid": "doc-en-kubernetes-a11072f45f81b280dea24734413173747c87bdd472ce068bad905ce856d1cb81", "text": "Loaded restart count threshold overrides: map[coredns:2 fluentd-gcp:999 konnectivity-agent:2 kube-controller-manager:1 kube-proxy:2 kube-scheduler:1 l7-lb-controller:1 metadata-proxy:2 prometheus-to-sd-exporter:2] I0227 05:03:32. ] ClusterOOMsTracker: gathering cluster OOMs tracking measurement E0227 05:03:32. ] TestMetrics: [action gather failed for SystemPodMetrics measurement: restart counts violation: RestartCount(node-problem-detector-tgl8h, node-problem-detector)=1, want <= 0; RestartCount(node-problem-detector-vpsmz, node-problem-detector)=1, want <= 0] I0227 05:03:32. ] Step \"[step: 29] gathering measurements\" ended W0227 05:03:32. ] Got errors during step execution: [measurement call TestMetrics - TestMetrics error: [action gather failed for SystemPodMetrics measurement: restart counts violation: RestartCount(node-problem-detector-tgl8h, node-problem-detector)=1, want <= 0; RestartCount(node-problem-detector-vpsmz, node-problem-detector)=1, want <= 0]] I0227 05:03:32. ] Waiting for the chaos monkey subroutine to end... I0227 05:03:32. ] Chaos monkey ended. I0227 05:03:32. ] I0227 05:03:32. ] Stopping DnsLookupLatency probe... I0227 05:03:47. ] Stopping InClusterNetworkLatency probe... I0227 05:04:22. ] Resources cleanup time: 50.539700215s E0227 05:04:22. ]\nE0227 05:04:22. ] Test Finished E0227 05:04:22. ] Test: E0227 05:04:22. ] Status: Fail E0227 05:04:22. ]", "commid": "kubernetes_issue_123328", "tokennum": 491}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d2f8dd8ba4d882d7774c610701aac28e324f9d0e781561c2bc7ae6641b496548", "query": "// Wraps syscall.Mount() func (mounter *DiskMounter) Mount(source string, target string, fstype string, flags uintptr, data string) error { <ins> glog.V(5).Infof(\"Mounting %s %s %s %d %s\", source, target, fstype, flags, data) </ins> return syscall.Mount(source, target, fstype, flags, data) }", "positive_passages": [{"docid": "doc-en-kubernetes-8045aaa7c39478c40c58e17441fd375a472ca56f31885311d26bd40c11b2233d", "text": "Errors: [measurement call TestMetrics - TestMetrics error: [action gather failed for SystemPodMetrics measurement: restart counts violation: RestartCount(node-problem-detector-tgl8h, node-problem-detector)=1, want <= 0; RestartCount(node-problem-detector-vpsmz, node-problem-detector)=1, want <= 0]] E0227 05:04:22. ]\nI0227 05:04:22. ]\nI0227 05:04:22. ] Running testing/huge- I0227 05:04:22. ]", "commid": "kubernetes_issue_123328", "tokennum": 136}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d3292c1563bd973ca1bb0530f19c4f4e000c0d91ca9a584ceeba2e93c6a5cbd7", "query": "### END TEST DEFINITION CUSTOMIZATION ### ####################################################### # Step 1: Start a server which supports both the old and new api versions, # but KUBE_OLD_API_VERSION is the latest (storage) version.", "positive_passages": [{"docid": "doc-en-kubernetes-74ce4fea7378dc634ccb83a22893b6255fa243ed3e0b4f0e57320154ecc66caf", "text": "removed this test. We need to continue testing this. This wasn't about testing upgrades, the prefix has nothing to do with upgrades. It's just there so people can share etcd. We maybe don't need to double everything but we do need to make sure that keeps working.\nTo be honest - I think that what we was testing before didn't give us completely any information. We didn't testing what information we are storing in etcd and where. That said, if we had a hardcoded prefix somewhere in our code, we wouldn't discover it at all, and those tests would still be passing. We should have a test that is directly checking etcd contents. I think it should be possible to write a simple unit test for it. Will try to put something together next week.", "commid": "kubernetes_issue_26489", "tokennum": 167}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d3461dc3d03693e4493dec71ee936adcaf0b7125f81523c315a09746ec904275", "query": "\"image_id_test.go\", \"kubelet_test.go\", \"lifecycle_hook_test.go\", <ins> \"log_path_test.go\", </ins> \"memory_eviction_test.go\", \"mirror_pod_test.go\", \"resource_usage_test.go\",", "positive_passages": [{"docid": "doc-en-kubernetes-0ad427ca9c00c618017f4be9fb19a1df6f4ab39ddc68f128fc109eb4d0409cbf", "text": "Cluster logging assumes kubelet stores container log at a specific directory with specific name. Currently the path is: After the CRI work, the path will be: However, we don't have test coverage for this. We don't even know whether the log files are there or not. We should add a node e2e test for this, basically: 1) Create a container which prints logs 2) Check whether the expected log file is created. 3) Check whether the logs are collected in the file as expected. And it would be better to launch a pod to do the check instead of accessing local file system directly, which makes containerizing easier. /cc because you are collecting missing test. /cc\nI will try to add a node-e2e test there\nI think it's ok to add this for CRI. But there maybe problems on today's interface for rkt. If I'm not wrong, rkt does't store logs at same location with docker. cc/ Is this true?\nThanks! :)\nAfter gets merged, we need to update the test to verify the cri log path.", "commid": "kubernetes_issue_34661", "tokennum": 234}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d3465f406e96fbfada82171a2bcf7839370149372cfe622372c248a304953b8b", "query": "assert.Equal(t, result, test.expectSocket, \"Unexpected result from IsUnixDomainSocket: %v for %s\", result, test.label) } } <ins> func TestGetAddressAndDialer(t *testing.T) { tests := []struct { endpoint     string expectError  bool expectedAddr string }{ { endpoint:     \"unix:///tmp/s1.sock\", expectError:  false, expectedAddr: \"/tmp/s1.sock\", }, { endpoint:     \"unix:///tmp/f6.sock\", expectError:  false, expectedAddr: \"/tmp/f6.sock\", }, { endpoint:    \"tcp://localhost:9090\", expectError: true, }, { // The misspelling is intentional to make it error endpoint:    \"htta://free-test.com\", expectError: true, }, { endpoint:    \"https://www.youtube.com/\", expectError: true, }, { endpoint:    \"http://www.baidu.com/\", expectError: true, }, } for _, test := range tests { // just test addr and err addr, _, err := GetAddressAndDialer(test.endpoint) if test.expectError { assert.NotNil(t, err, \"expected error during parsing %s\", test.endpoint) continue } assert.Nil(t, err, \"expected no error during parsing %s\", test.endpoint) assert.Equal(t, test.expectedAddr, addr) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-9fe53756e4f224dbc05ba9a01e42da1fd9faed4696cdb60aebb7f8b8a8125e7b", "text": "What would you like to be : Currently, does not have unit test coverage. Unless there's a strong reason not to, we'd like public facing functions to have unit test coverage. Why is this needed: There's a fairly small chance of GetAddressAndDialer being modified, and thus breaking, in the future without this test coverage. However, it should be relatively straightforward to add the test coverage, and could make a good first issue for a new contributor. There's also the benefit that it helps keep the test coverage in pkg/kubelet high :) And we never know, it might help catch a bug some day :) Extra note I think this ticket could be a great candidate for someone who is new to contributing to sig-node/k8s. I'd prefer to please give first dibs for picking this up to any folks who are currently underrepresented in the k8s community. Please reach out to on k8s Slack (or post directly in #sig-node and tag me) if you're interested, and I'll assign you the issue. I'm happy to mentor and be helpful in whatever way I can :)\n/sig node\n/good-first-issue\nThis request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /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\n/assign\nHi let's me solve it\nSounds like a plan! Can you please tag and myself for the review?\nHi, I've already created a pr which , please help me complete the review, thanks", "commid": "kubernetes_issue_92996", "tokennum": 389}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d35fa71ee8824da4b40155b19d1ccd789d268fb5501f57faebeb2059c716bfd1", "query": "readonly KUBE_NODE_BINARIES=(\"${KUBE_NODE_TARGETS[@]##*/}\") readonly KUBE_NODE_BINARIES_WIN=(\"${KUBE_NODE_BINARIES[@]/%/.exe}\") <del> if [[ \"${KUBE_FASTBUILD:-}\" == \"true\" ]]; then </del> <ins> if [[ -n \"${KUBE_BUILD_PLATFORMS:-}\" ]]; then readonly KUBE_SERVER_PLATFORMS=(${KUBE_BUILD_PLATFORMS}) readonly KUBE_NODE_PLATFORMS=(${KUBE_BUILD_PLATFORMS}) readonly KUBE_TEST_PLATFORMS=(${KUBE_BUILD_PLATFORMS}) readonly KUBE_CLIENT_PLATFORMS=(${KUBE_BUILD_PLATFORMS}) elif [[ \"${KUBE_FASTBUILD:-}\" == \"true\" ]]; then </ins> readonly KUBE_SERVER_PLATFORMS=(linux/amd64) readonly KUBE_NODE_PLATFORMS=(linux/amd64) if [[ \"${KUBE_BUILDER_OS:-}\" == \"darwin\"* ]]; then", "positive_passages": [{"docid": "doc-en-kubernetes-1b2bcc3aa22e5d5f53df9233e5f80a56f1f4bdaeb462b3a5016092de1417360c", "text": "hack/build-cross sets it without looking at the current value. And the value has to be an array, which is a bit awkward to use.\nThis could be improved indeed. Maybe something like and Haven't tested it though... But why would one want to change the value?\nI just wanted to build one, so I did the \"obvious\" thing: hack/dev-build-and-` It failed for multiple reasons :) , Lucas K\u00e4ldstr\u00f6m wrote:\nThis issue has been a major downer for me. It's much harder right now than it ought to be to articulate the few platforms for which you'd like to build each of server binaries, client binaries, test binaries, etc. Every time I've tried to do this \"the right way,\" I've spent hours looking at scripts and feeling frustrated that build options aren't documented better. Every time, I end up cutting my losses and resorting to temporary build script hacks instead, just to get the job done.\nDoesn't fix this issue exactly, but I've found that you can easily build only if you set .\nTaking a look at this today, I also thought that setting seems to be the most reasonable.\n/sig release", "commid": "kubernetes_issue_20365", "tokennum": 260}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d371708c06cbf2ac5892e2a11700274abbb6230edc33a0b1b60d8acda252924d", "query": "# limitations under the License. ARG BASEIMAGE <ins> ARG RUNNERIMAGE </ins> <del> FROM ${BASEIMAGE} </del> <ins> FROM ${BASEIMAGE} as debbase FROM ${RUNNERIMAGE} # This is a dependency for `kubectl diff` tests COPY --from=debbase /usr/bin/diff /usr/local/bin/ COPY cluster /kubernetes/cluster </ins> COPY ginkgo /usr/local/bin/ COPY e2e.test /usr/local/bin/ COPY kubectl /usr/local/bin/ <del> COPY run_e2e.sh /run_e2e.sh </del> <ins> COPY gorunner /usr/local/bin/kubeconformance # Legacy executables -- deprecated COPY gorunner /run_e2e.sh </ins> COPY gorunner /gorunner <del> COPY cluster /kubernetes/cluster WORKDIR /usr/local/bin </del> ENV E2E_FOCUS=\"[Conformance]\" ENV E2E_SKIP=\"\"", "positive_passages": [{"docid": "doc-en-kubernetes-b6e1a63eb087c1fdbaf4f20789cf4dc422d7eb3a250658bf836af9dda6b010da", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be modified: image to be based on anything other than Docker Hub sourced Why is this needed: With Docker Hub rate-limit policy in-place, we probably should consider removing this dependency to stay in sync with other base images in Kubernetes project. Folks building their own binaries (i.e. with ) might run into this as well. Notes: Prior discussion happened on An idea from is to use the should probably be renamed to avoid confusion with k/release (h/t Currently, is set to , so migrating to may not be a drop-in move However, , so maybe we don't have to start from scratch /sig testing /area conformance /sig release (cc'ing because builds conformance image, though my quick search seem to show there isn't any build pipelines referencing )\n/assign\ndo we still want to do this? I read somewhere that the images built in Google Cloud are being mirrored from Docker Hub, right? This would mean that the API rate limiting will not hit us any more.\nWomp yeah I think DockerHub rate limit is not really the big motivator at this point. However, I think I still want to consider using distroless / go-runner to build and produce conformance image to reduce the noise from CVE scanning done in downstream places. What do you think?\nYeah I think this seems a valuable addition. Are you planning to work on this issue? :)\nI will, though probably won't start until next week. If you have ideas and would like to start early feel free to go for it! Otherwise, I'd be happy to work on and deliver this.\nThank you Wilson! Feel free to ping again if you need any assistance. /assign\n/triage accepted\none thing I need a little help with is to find a reference for using go-runner image that's used everywhere -- the one that I've found is inside conformance directory which seems to be different from what everyone else is using\nWe maintain a go-runner in k/release:\noops, I forgot to get back on this last week -- I meant to say that I need a reference for image which I can use as , so something like on Dockerfile. Is that a possible thing to do?", "commid": "kubernetes_issue_96692", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d371708c06cbf2ac5892e2a11700274abbb6230edc33a0b1b60d8acda252924d", "query": "# limitations under the License. ARG BASEIMAGE <ins> ARG RUNNERIMAGE </ins> <del> FROM ${BASEIMAGE} </del> <ins> FROM ${BASEIMAGE} as debbase FROM ${RUNNERIMAGE} # This is a dependency for `kubectl diff` tests COPY --from=debbase /usr/bin/diff /usr/local/bin/ COPY cluster /kubernetes/cluster </ins> COPY ginkgo /usr/local/bin/ COPY e2e.test /usr/local/bin/ COPY kubectl /usr/local/bin/ <del> COPY run_e2e.sh /run_e2e.sh </del> <ins> COPY gorunner /usr/local/bin/kubeconformance # Legacy executables -- deprecated COPY gorunner /run_e2e.sh </ins> COPY gorunner /gorunner <del> COPY cluster /kubernetes/cluster WORKDIR /usr/local/bin </del> ENV E2E_FOCUS=\"[Conformance]\" ENV E2E_SKIP=\"\"", "positive_passages": [{"docid": "doc-en-kubernetes-5d193977829c25729bf0cf7e65192f8c845e68df9f65fd9e6c218e9e5725e8bf", "text": "after searching around, I found this -- going to try and use and see how it works :smile:\nStarted a PR -- plenty of things I'd like to be discussed but we should probably have the discussions there\nIssues 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\n/remove-lifecycle stale there is work in progress", "commid": "kubernetes_issue_96692", "tokennum": 118}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d3c70e7835fe24910d3e29a6e11d0143e570329afb925cc171856ae54e449cc3", "query": "return nil } <ins> // We don't want to upgrade (add an IP) or downgrade (remove an IP) // following a cluster downgrade/upgrade to/from dual-stackness // a PreferDualStack service following principle of least surprise // That means: PreferDualStack service will only be upgraded // if: // - changes type to RequireDualStack // - manually adding or removing ClusterIP (secondary) // - manually adding or removing IPFamily (secondary) if isMatchingPreferDualStackClusterIPFields(oldService, service) { return nil // nothing more to do. } </ins> // two families or two IPs with SingleStack if service.Spec.IPFamilyPolicy != nil { el := make(field.ErrorList, 0)", "positive_passages": [{"docid": "doc-en-kubernetes-572d0164a11730b1ec949ed970afee14cdb12823b4b7a698fae66a86d82f748e", "text": "1) start with a single stack cluster 2) create a PreferDualStack service 3) configure API server with a 2nd service CIDR 4) Confirm the above service is not dual-stack 5) Add a label to the above service 6) Observe that the service becomes dual-stack I think the correct answer is to have a \"repair loop\" that upgrades (and downgrades!) PreferDualStack Services to match the config. I think this is a GA blocker.\n/triage accepted The current thought is: of type with are special new breed of api objects that I don't think we have any similar precedent in the apis, i could be wrong. Their behavior is tied to how the cluster is configured. Thus their behavior must change as the cluster behavior change. a way the user is stating . If it is cluster then i am good with two ClusterIPs. If it is single stack cluster then I am also good with a single ClusterIP. One can assume that if the user was ok was with getting a additional IP when possible then they must be ok with taking it away when it is no longer possible. Based on the above I believe best course of action is create a new repair loop or piggyback on any of the existing (or better: fix it in rest stack during list and get calls). The new logic takes care of matching to the .\nreproducer and regression test if somebody takes this, feel free to add it\nack - Scheduled to tackle 3rd week of May. Will definitely include that patch.", "commid": "kubernetes_issue_101681", "tokennum": 322}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d3c7c5eb62a7b703293c6e2548d7cea3b0d0bdad1eecc4f03cfd8d88afce0734", "query": "pod.Spec.NodeName = nodeName pod.ObjectMeta.SelfLink = getSelfLink(pod.Name, pod.Namespace) <ins> if pod.Annotations == nil { pod.Annotations = make(map[string]string) } // The generated UID is the hash of the file. pod.Annotations[kubetypes.ConfigHashAnnotationKey] = string(pod.UID) </ins> return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-8bc8d69d49aedfb4a9bf3991de80f7c339e96bfbefe5b1f250dae70fa0393729", "text": "See for more context. Currently, kubelet compares the spec of a mirror pod (created via apiserver) with that of a static pod (config stored as a file) to decide whether the two are considered identical. If they differ, kubelet would delete the mirror pod and re-create it with the correct spec. Due to the fact that apiserver may set default values for some fields in the spec of the mirror pod, the specs could deviate undesirably. To avoid problems like this, we can store the config of a static pod as an annotation in the mirror pod, and compare the static pod with the annotation.\nWould a hash of the config be sufficient if we're only going to compare? The whole spec would generally be more useful, but I wonder if that is too much data to put in an annotation.\nThis seems totally reasonable to me, but I'm still desperately curious why you can't just bypass defaulting when you generate mirror pod from static pod? (i.e. just use the static pod's configuration verbatim)\nIt's not kubelet who applies the default values here. The admission plugin was only run at the apiserver, and to bypass that, you have to ask apiserver to treat mirror pods differently and potentially at multiple places.\nOn May 22, 2015 10:38 AM, \"Yu-Ju Hong\" wrote: Understood, but is it really multiple places? If so then I agree it's a bad idea. Otherwise it might be worth considering as an alternative.\nIt's untenable for Kubelet to assume to know/circumvent all fields that will be set by other entities: admission control, defaulting, late initialization, auto-something, whatever. It needs to obey the same rules as other clients.\nI don't understand why you would ever want to apply any of the things you mentioned to static pods. Static pods should be copied verbatim into the mirror pods, right? That's what I'm proposing.\nWhat if the master is updated before the kubelet, and the master adds a new API field with a default value?\nThat case should be discussed in\nI agree that mirror pod should reflect the true status of the static pod running on the node, and no default values should be set in this case.", "commid": "kubernetes_issue_8683", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d3c7c5eb62a7b703293c6e2548d7cea3b0d0bdad1eecc4f03cfd8d88afce0734", "query": "pod.Spec.NodeName = nodeName pod.ObjectMeta.SelfLink = getSelfLink(pod.Name, pod.Namespace) <ins> if pod.Annotations == nil { pod.Annotations = make(map[string]string) } // The generated UID is the hash of the file. pod.Annotations[kubetypes.ConfigHashAnnotationKey] = string(pod.UID) </ins> return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-0491e123884f0f20f50d0a788bca7a6a29e2fa08227703a00221ecbd3bcf483c", "text": "However, I think it'd be harder to implement this way since, as stated above, that there are many things to circumvent in the apiserver itself. It could also be harder to keep this special case from being broken by a yet another new feature/plugin. Keeping the hash of the config in the annotation seems like a good compromise even though it may not reflect the true status 100% accurately. I think this is acceptable. What do you think?\nSure, if you think the annotation approach is easier, I would go with that. I guess in the case Brian mentoined (master adds a new API field with a default value), you would not update the mirror pod, because the static pod definition has not changed?\nYes, a hash would be sufficient.\nIt shouldn't be necessary to update the mirror pod in the case that a new default field was updated, because that field should be populated automatically by the apiserver on decode from etcd.\nWe should fix this so we don't have this problem again in 1.2.", "commid": "kubernetes_issue_8683", "tokennum": 226}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d3d9386ef2f63de773be7dca356594a69833cb8d67194e67d3837b307a06fdc0", "query": "// More info: https://kubernetes.io/docs/concepts/containers/images#updating-images // +optional ImagePullPolicy PullPolicy `json:\"imagePullPolicy,omitempty\" protobuf:\"bytes,14,opt,name=imagePullPolicy,casttype=PullPolicy\"` <del> // Security options the pod should run with. </del> <ins> // SecurityContext defines the security options the container should be run with. // If set, the fields of SecurityContext override the equivalent fields of PodSecurityContext. </ins> // More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ // +optional SecurityContext *SecurityContext `json:\"securityContext,omitempty\" protobuf:\"bytes,15,opt,name=securityContext\"`", "positive_passages": [{"docid": "doc-en-kubernetes-2eefef1a83ddd783604f0989f7bcbb86ee11f3e15f09ced1fa06f0ad1ee322e6", "text": "What happened: states that Container.SecurityContext applies to a Pod, which can be misleading since we already have PodSecurityContext. What you expected to happen: Documentation states that it applies to container How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment:\n/sig api-machinery /kind documentation\n/cc\nIssues 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\nNot stale.\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten\nIssues 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\n/remove-lifecycle rotten\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nClosing 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", "commid": "kubernetes_issue_90634", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d3d9848d5871553e919357479e48398bd164a28c33413140b22de2ecf83ceb27", "query": "if err != nil { t.Fatalf(\"socks5Server: proxy_test: Listen: %v\", err) } <del> defer func() { close(closed) l.Close() }() </del> <ins> defer l.Close() </ins> go func(shoulderror bool) { conn, err := l.Accept()", "positive_passages": [{"docid": "doc-en-kubernetes-631bc5da562ebc33bd49790f3078648639a2126878c5fc7773cd8143bd3bdf27", "text": "TestRoundTripSocks5AndNewConnection Disabled by No response No response No response /sig\nThere are no sig labels on this issue. Please add an appropriate label by using one of the following commands: - Please see the for a listing of the SIGs, working groups, and committees available. <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\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nthere is a race shutting down the socks5 server", "commid": "kubernetes_issue_107766", "tokennum": 198}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d3faf38d5f3ab04e6f628920a913d39ccf50d90a025315fb9c3f27593639d713", "query": "if c.SecureServing != nil && !c.SecureServing.DisableHTTP2 && c.GoawayChance > 0 { handler = genericfilters.WithProbabilisticGoaway(handler, c.GoawayChance) } <del> handler = genericapifilters.WithWarningRecorder(handler) </del> handler = genericapifilters.WithCacheControl(handler) handler = genericfilters.WithHSTS(handler, c.HSTSDirectives) if c.ShutdownSendRetryAfter {", "positive_passages": [{"docid": "doc-en-kubernetes-c00c4002c1ceb0f27a0d12e9f8008c8e3b435d9e5dbb0a6b5f62beaf7aea3677", "text": "I am doing v1.28.3 kube-apiserver testing in the test environment, and I often encounter kube-apiserver panic, especially when kube-apiserver call webhook fails. The following are the captured panic logs: and: kube-apiserver does not panic even if calling webhook times out or fails Deploy a webhook, remove the service corresponding to the webhook, and then create pods in batches to trigger webhook calls No response <details</details<detailsprivate cloud </details<details</details<details</details<details</details<details</details\n/sig api-machinery\nsomewhat related to\nThe scenarios that trigger panic are similar(the apiserver fails to call webhook), but the log shows that the location of panic is different.\n/assign For context of  Thank you. /triage accepted\nagain, full stack logs:\nI'll try to test the mr:\nLet me try to explain the panic - both goroutines are trying to write to the of the first goroutine: This request has timed out, and consequently the filter is trying to send a response to the caller. This is the client facing goroutine from the timeout filter. Note that the call to is protected by a mutex, that means that if the other goroutine is using the delegated object via the adapter, then this panic should not happen. second goroutine: let's check the other goroutine, it is also trying to write to the of the object: Now uses an unprotected version of the ResponseWriter object: The filter precedes the filter in the execution order, so the in is not using the thread safe implementation. This is the order today: one quick resolution is to move the after the timeout filter: , but there could be code that precedes that needs to write warning? Also note that the panic mentioned in is not as severe, it does not cause the apiserver to crash. For a more proper solution, i think we would want any thoughts?", "commid": "kubernetes_issue_122940", "tokennum": 443}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d3faf38d5f3ab04e6f628920a913d39ccf50d90a025315fb9c3f27593639d713", "query": "if c.SecureServing != nil && !c.SecureServing.DisableHTTP2 && c.GoawayChance > 0 { handler = genericfilters.WithProbabilisticGoaway(handler, c.GoawayChance) } <del> handler = genericapifilters.WithWarningRecorder(handler) </del> handler = genericapifilters.WithCacheControl(handler) handler = genericfilters.WithHSTS(handler, c.HSTSDirectives) if c.ShutdownSendRetryAfter {", "positive_passages": [{"docid": "doc-en-kubernetes-f6276625b0df7e8b951a42b4ce484e48eb7715b4546658f042b200999787970a", "text": "/cc\nI tend to remove the timeout filter, the sooner the better, and I think the Apiserver panic is the P0-level bug, directly affecting the availability of the cluster I have cherry-picked and tested it in my cluster, and I still need to continue to observe for 1-2 days\nI opened a minimal WIP fix for the warning writer in since the timeout filter removal is a much bigger change to reason through\nthanks a lot, I will try to test and cherry-pick the above minimal WIP fix in\nsorry, I completely overlooked , I only saw and that looked too big to take safely right now I prefer to\nCan we backport the fix to 1.28?\nWhy 1.28 specifically? I'm not aware of anything that changed in 1.28 that made this more or less prevalent. If this meets backport criteria, going to all active branches could make sense (1.27+)", "commid": "kubernetes_issue_122940", "tokennum": 191}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d40eb1efbd8fe64409ed3f4082b12df74a35795ac9caab6819b9ba0e4b108af6", "query": "start-kube-controller-manager start-kube-scheduler start-kube-addons <ins> start-cluster-autoscaler </ins> else start-kube-proxy # Kube-registry-proxy.", "positive_passages": [{"docid": "doc-en-kubernetes-cafbbd3cd664270b9fbd0ce7e8faa35ad0e8800a7c5d7cdeb5164eec0f1b24f1", "text": "For some reason they stopped working and we even don't create manifest file for cluster autoscaler. I used the following command to start the cluster:\nIt's possible it's related to", "commid": "kubernetes_issue_26346", "tokennum": 40}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d4d95c0898f1430d6f7d743001f27cd4cf9150f03ad3b125cc6649a21faa9c9f", "query": "if \"${need_download}\"; then if [[ $(which gsutil) ]] && [[ \"$kubernetes_tar_url\" =~ ^https://storage.googleapis.com/.* ]]; then <del> gsutil cp \"${kubernetes_tar_url//'https://storage.googleapis.com/'/'gs://'}\" \"${file}\" </del> <ins> gsutil cp \"${kubernetes_tar_url//'https://storage.googleapis.com/'/gs://}\" \"${file}\" </ins> elif [[ $(which curl) ]]; then # if the url belongs to GCS API we should use oauth2_token in the headers curl_headers=\"\"", "positive_passages": [{"docid": "doc-en-kubernetes-3d2f3dab1a1037d1573c264392a8fb35a501948caa8df40cf12a2cd970b123e2", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --command fails because of I think the link is from k/k's Am I right?? kubetest command succeeds With installed, OR Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig release /sig testing\n/assign\nNeed cherry-picks for 1.21, 1.20 to address this. is updated but downloaded downloads and executes its /reopen\nReopened this issue. <detailsIn response to : Need cherry-picks for 1.21, 1.20 to address 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\ncc\nthis was cherry picked AFAICT, thank you!", "commid": "kubernetes_issue_102029", "tokennum": 328}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d51e47aeee2ac8ee87f089abc0b1fd7e2f8ec986f718aad863d2f362c55c3d51", "query": "func (az *Cloud) EnsureLoadBalancerDeleted(ctx context.Context, clusterName string, service *v1.Service) error { isInternal := requiresInternalLoadBalancer(service) serviceName := getServiceName(service) <del> klog.V(5).Infof(\"delete(%s): START clusterName=%q\", serviceName, clusterName) </del> <ins> klog.V(5).Infof(\"Delete service (%s): START clusterName=%q\", serviceName, clusterName) ignoreErrors := func(err error) error { if ignoreStatusNotFoundFromError(err) == nil { klog.V(5).Infof(\"EnsureLoadBalancerDeleted: ignoring StatusNotFound error because the resource doesn't exist (%v)\", err) return nil } if ignoreStatusForbiddenFromError(err) == nil { klog.V(5).Infof(\"EnsureLoadBalancerDeleted: ignoring StatusForbidden error (%v). This may be caused by wrong configuration via service annotations\", err) return nil } return err } </ins> serviceIPToCleanup, err := az.findServiceIPAddress(ctx, clusterName, service, isInternal) <del> if err != nil { </del> <ins> if ignoreErrors(err) != nil { </ins> return err } klog.V(2).Infof(\"EnsureLoadBalancerDeleted: reconciling security group for service %q with IP %q, wantLb = false\", serviceName, serviceIPToCleanup) if _, err := az.reconcileSecurityGroup(clusterName, service, &serviceIPToCleanup, false /* wantLb */); err != nil { <del> return err </del> <ins> if ignoreErrors(err) != nil { return err } </ins> } if _, err := az.reconcileLoadBalancer(clusterName, service, nil, false /* wantLb */); err != nil { <del> return err </del> <ins> if ignoreErrors(err) != nil { return err } </ins> } if _, err := az.reconcilePublicIP(clusterName, service, nil, false /* wantLb */); err != nil { <del> return err </del> <ins> if ignoreErrors(err) != nil { return err } </ins> } <del> klog.V(2).Infof(\"delete(%s): FINISH\", serviceName) </del> <ins> klog.V(2).Infof(\"Delete service (%s): FINISH\", serviceName) </ins> return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-4ac48b480971aca26f0a1896d0fa1bdd3b9ed6e78abeeb1cea4ee05f140cc101", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: controller-manager is stuck in deleting an incorrectly configured LB type service. it cannot be recovered until restarted. What you expected to happen: controller-manager should recover. At least it should allow us to create the service without restarting it. How to reproduce it (as minimally and precisely as possible): put a random IP in above yaml and make sure the resource group doen't exist. Anything else we need to know?: Environment: Kubernetes version (use ): 1.12.4 Cloud provider or hardware configuration: AKS OS (e.g: ): Kernel (e.g. ): Install tools: Others:\n/sig azure\nI also want to add that the above repro is stuck in 403. It's possible for it to be stuck in 404 as well when the SP has the right permission.\nCan you share the log for 404?\nThanks for reporting the issue. /assign Do you mean other services couldn't be configured when this happens?\ncorrect.\nFYI, we had the same issue when the Idle Timeout annotation was set to \"3\" which isn't a supported case. Will this PR also cover this edge case ?\nUnfortunately , this is still not fixed. The idle timeout is not 403 or 404. We need another fix for this (and possibly more for other annotations)", "commid": "kubernetes_issue_75198", "tokennum": 337}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d532992cbb641fc9ae4afe8a51d9c63b8268cb86d5dc0d68b4300936edd01fb7", "query": "<ins> /* Copyright 2017 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package fuzzer import ( \"time\" \"github.com/google/gofuzz\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" runtimeserializer \"k8s.io/apimachinery/pkg/runtime/serializer\" \"k8s.io/kubernetes/pkg/kubelet/apis/kubeletconfig\" \"k8s.io/kubernetes/pkg/kubelet/apis/kubeletconfig/v1alpha1\" \"k8s.io/kubernetes/pkg/kubelet/qos\" kubetypes \"k8s.io/kubernetes/pkg/kubelet/types\" \"k8s.io/kubernetes/pkg/master/ports\" ) // Funcs returns the fuzzer functions for the kubeletconfig apis. func Funcs(codecs runtimeserializer.CodecFactory) []interface{} { return []interface{}{ // provide non-empty values for fields with defaults, so the defaulter doesn't change values during round-trip func(obj *kubeletconfig.KubeletConfiguration, c fuzz.Continue) { c.FuzzNoCustom(obj) obj.ConfigTrialDuration = &metav1.Duration{Duration: 10 * time.Minute} obj.Authentication.Anonymous.Enabled = true obj.Authentication.Webhook.Enabled = false obj.Authentication.Webhook.CacheTTL = metav1.Duration{Duration: 2 * time.Minute} obj.Authorization.Mode = kubeletconfig.KubeletAuthorizationModeAlwaysAllow obj.Authorization.Webhook.CacheAuthorizedTTL = metav1.Duration{Duration: 5 * time.Minute} obj.Authorization.Webhook.CacheUnauthorizedTTL = metav1.Duration{Duration: 30 * time.Second} obj.Address = \"0.0.0.0\" obj.CAdvisorPort = 4194 obj.VolumeStatsAggPeriod = metav1.Duration{Duration: time.Minute} obj.RuntimeRequestTimeout = metav1.Duration{Duration: 2 * time.Minute} obj.CPUCFSQuota = true obj.EventBurst = 10 obj.EventRecordQPS = 5 obj.EnableControllerAttachDetach = true obj.EnableDebuggingHandlers = true obj.EnableServer = true obj.FileCheckFrequency = metav1.Duration{Duration: 20 * time.Second} obj.HealthzBindAddress = \"127.0.0.1\" obj.HealthzPort = 10248 obj.HostNetworkSources = []string{kubetypes.AllSource} obj.HostPIDSources = []string{kubetypes.AllSource} obj.HostIPCSources = []string{kubetypes.AllSource} obj.HTTPCheckFrequency = metav1.Duration{Duration: 20 * time.Second} obj.ImageMinimumGCAge = metav1.Duration{Duration: 2 * time.Minute} obj.ImageGCHighThresholdPercent = 85 obj.ImageGCLowThresholdPercent = 80 obj.MaxOpenFiles = 1000000 obj.MaxPods = 110 obj.NodeStatusUpdateFrequency = metav1.Duration{Duration: 10 * time.Second} obj.CPUManagerPolicy = \"none\" obj.CPUManagerReconcilePeriod = obj.NodeStatusUpdateFrequency obj.OOMScoreAdj = int32(qos.KubeletOOMScoreAdj) obj.Port = ports.KubeletPort obj.ReadOnlyPort = ports.KubeletReadOnlyPort obj.RegistryBurst = 10 obj.RegistryPullQPS = 5 obj.ResolverConfig = kubetypes.ResolvConfDefault obj.SerializeImagePulls = true obj.StreamingConnectionIdleTimeout = metav1.Duration{Duration: 4 * time.Hour} obj.SyncFrequency = metav1.Duration{Duration: 1 * time.Minute} obj.ContentType = \"application/vnd.kubernetes.protobuf\" obj.KubeAPIQPS = 5 obj.KubeAPIBurst = 10 obj.HairpinMode = v1alpha1.PromiscuousBridge obj.EvictionHard = map[string]string{ \"memory.available\":  \"100Mi\", \"nodefs.available\":  \"10%\", \"nodefs.inodesFree\": \"5%\", \"imagefs.available\": \"15%\", } obj.EvictionPressureTransitionPeriod = metav1.Duration{Duration: 5 * time.Minute} obj.MakeIPTablesUtilChains = true obj.IPTablesMasqueradeBit = v1alpha1.DefaultIPTablesMasqueradeBit obj.IPTablesDropBit = v1alpha1.DefaultIPTablesDropBit obj.CgroupsPerQOS = true obj.CgroupDriver = \"cgroupfs\" obj.EnforceNodeAllocatable = v1alpha1.DefaultNodeAllocatableEnforcement obj.ManifestURLHeader = make(map[string][]string) }, } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-937f1cb17c20e5fd2b4a1f81201690c3dbe6990ef3c1bc74ff71daaa02b6db56", "text": "Solution: I will add one.\n/cc\nxref\nThanks for sending a PR so quickly!\n[MILESTONENOTIFIER] Milestone Issue Needs Attention Action required: During code slush, issues in the milestone should be in progress. If this issue is not being actively worked on, please remove it from the milestone. If it is being worked on, please add the label so it can be tracked with other in-flight issues. Note: If this issue is not resolved or labeled as by Wed, Nov 22 it will be moved out of the v1.9 milestone. <details<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details", "commid": "kubernetes_issue_55959", "tokennum": 230}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d5460dc0a276da91c6b109d458f11f09bd75050a4e995d3c29e5db1577475490", "query": "// We check for double because it needs to support at least the cri-o minimum // plus whatever delta between node usages (which could be up to or at least crioMinMemLimit) func nodesAreTooUtilized(cs clientset.Interface, nodeList *v1.NodeList) bool { <ins> nodeNameToPodList := podListForEachNode(cs) </ins> for _, node := range nodeList.Items { <del> _, memFraction, _, memAllocatable := computeCPUMemFraction(cs, node, podRequestedResource) </del> <ins> _, memFraction, _, memAllocatable := computeCPUMemFraction(node, podRequestedResource, nodeNameToPodList[node.Name]) </ins> if float64(memAllocatable)-(memFraction*float64(memAllocatable)) < float64(2*crioMinMemLimit) { return true }", "positive_passages": [{"docid": "doc-en-kubernetes-68f56cf00eaca7b36f313a8fbb47f02ec3096dc918e863d7bad5040791bff0ba", "text": "From After , Multi-AZ Clusters tests in 1.19 and 1.20 started timing out as createBalancedPodForNodes is extremely inefficient in scale: for each node (out of 5k), it lists all pods in a cluster serially (each list takes ~5s), which translates to ~7 hours. Optimizing this function by listing pods once and then in memory by Spec.NodeName /kind bug /priority critical-urgent /sig scheduling\n/triage accepted\n/assign\n/reopen Looks that ComputeCPUMemFraction took only 12 minutes, but it stuck later, on It is scheduling one pod per each node: Which is waiting 5s to be ready: 5k nodes * 5s = ~7h\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign Can you do the pod creations in parallel?\nYes, good idea. I'll update to do that", "commid": "kubernetes_issue_100705", "tokennum": 227}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d54e45b33e50654beab707bb8621c9e6d9f5916cb231ef5b6b5dc350f80e51be", "query": "} func TestCreate(t *testing.T) { <del> simpleStorage := &SimpleRESTStorage{} </del> <ins> wait := sync.WaitGroup{} wait.Add(1) simpleStorage := &SimpleRESTStorage{ injectedFunction: func(obj runtime.Object) (returnObj runtime.Object, err error) { wait.Wait() return &Simple{}, nil }, } </ins> handler := Handle(map[string]RESTStorage{ \"foo\": simpleStorage, }, codec, \"/prefix/version\", selfLinker)", "positive_passages": [{"docid": "doc-en-kubernetes-f8d5fa52ad40b7a48721555fc6e9ed2d9d20bf180da0265ac5e3a79ed043fc75", "text": "Intermittent failures on Travis.\nHrm, this passes 100/100 locally for me. I'll look at the code and see if I see anything. --brendan", "commid": "kubernetes_issue_2103", "tokennum": 34}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d58307d6d3f62eee4ec3902f33c9a26cfb7c897fa80d719b3190af58b52c7e62", "query": "// records an event using ref, event msg.  log to glog using prefix, msg, logFn func (m *imageManager) logIt(ref *v1.ObjectReference, eventtype, event, prefix, msg string, logFn func(args ...interface{})) { if ref != nil { <del> m.recorder.Event(events.ToObjectReference(ref), eventtype, event, msg) </del> <ins> m.recorder.Event(ref, eventtype, event, msg) </ins> } else { logFn(fmt.Sprint(prefix, \" \", msg)) }", "positive_passages": [{"docid": "doc-en-kubernetes-b0087f3d33811f5a8bf21a1757c4fff7aaef7add29731940c9c3bd61ec9b29c4", "text": "Is this a BUG REPORT or FEATURE REQUEST?: What happened: Now the and has been consistent in by PR . There is no need to convert v1.ObjectReference to clientv1.ObjectReference in . What you expected to happen: Remove this function and cleanup the codes which call this function. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?:\nThere are no sig labels on this issue. Please by:<br(1) mentioning a sig: <bre.g., for API Machinery<br(2) specifying the label manually: <bre.g., for sig/scalability<br<brNote: method (1) will trigger a notification to the team. You can find the team list and label list\nWill submit the cleanup after PR merged.\n/sig api-machinery\n/sub", "commid": "kubernetes_issue_48747", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d598b75e9fc7534ebc4abb5cf12a97fd6d2fca3ea6306699d49ab9ee93e9375b", "query": "if _, ok = t.objects[gvr][namespacedName]; ok { if replaceExisting { for _, w := range t.getWatches(gvr, ns) { <del> w.Modify(obj) </del> <ins> // To avoid the object from being accidentally modified by watcher w.Modify(obj.DeepCopyObject()) </ins> } t.objects[gvr][namespacedName] = obj return nil", "positive_passages": [{"docid": "doc-en-kubernetes-097cec69e6f696ee556282ba1b462f036510b26986c7b0a8c41c6e03be57a385", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --Hello, Found a potential data race in testing. There is a test If we update it like this (we actually can do it ): If watcher updates received object we get a data race. No data race My suggestion: send copy of object here:\n/sig api-machinery\n/cc /triage accepted Do you remember if we fixed similar issues before?\nHi ,The code avoiding data race seems to already exist If you commented the code on above, the following test case will pass (because of data race), so I think there is no data race in the code : )\nHi Did you run my test with flag? Of course if I comment there will be data race. But let's take a look at: We store in and do with the same . So, watcher receives that is stored in map. we call we take the same from : Therefore, if watcher modifies received in another goroutine we have data race. Output:\nHi You're right ,thank you for solving my confusion. One solution could be to copy of , I will try to fix it.", "commid": "kubernetes_issue_103148", "tokennum": 276}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d59c3657f546d25f9ec3a5fbc423eaf632a0a0178b7ac7b311fe403031b8d701", "query": "serviceAccountName: fluentd-gcp-scaler containers: - name: fluentd-gcp-scaler <del> image: gcr.io/google-containers/fluentd-gcp-scaler:0.1 </del> <ins> image: gcr.io/google-containers/fluentd-gcp-scaler:0.2 </ins> command: - /scaler.sh - --ds-name=fluentd-gcp-v3.0.0", "positive_passages": [{"docid": "doc-en-kubernetes-a63e01ebe6efecf34b1eda7468cd7472762d7f902ee9117cf6f0f2ff92b9f93a", "text": "Forking from To summarize, here's what we observed: daemonset calls coming every minute from both fluentd-scaler and addon-manager (verified this by individually turning them on/off). Things we need to understand here: Is the daemonset object continuously toggling b/w 2 states? (we know here that it's RV is increasing continuously) If yes, what field(s) in the object are changing? IIRC value of some label/annotation (I think 'UpdatedPodsScheduled') is changing (probably related to 2 below) Also, why/should the fluentd-scaler send any api request if the resources are already set to the right value? pods are getting deleted and recreated by daemonset-controller when the scaler is enabled (as was also seen in ). Why this is happening? One thing to note here - all those delete calls are preceded by calls from respective kubelets (but maybe that's expected). cc /priority critical-urgent /assign\nMarked this as release-blocker as at least some part of it seems like a correctness issue (i.e fluentd pods dying and getting recreated). Note also that this is causing increased mem-usage with daemonset-controller (depicted here - )\nThanks for filing this! The only thing that was changing (apart from ds/fluentd-gcp status) was the resource version.\nI modified fluentd scaler to use --dry-run in to check whether there would be a change, but this still keeps on updating, even though there is no change. Apparently, the logic inside kubectl is broken...\nBtw, addon manager sends tons of PATCH requests for all resources every minute anyway, so even though I will fix fluent-scaler not to send them, it won't solve everything.\nShould this issue actually be closed? It was auto-closed by the bot, but nobody has confirmed that the actual issue is fixed.\nI'll let to confirm (looks like he'll be back on Monday)\n/status in-progress\nYes, we should keep this issue open until we fully understand what's going wrong and fix the root-cause. I believe much of the discussion wrt this is happening under related issue\nACK. In progress ETA: 20/03/2018 Risks: May delay the release if not satisfactorily resolved\nNeed a number of successive green runs, then close.", "commid": "kubernetes_issue_61190", "tokennum": 515}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d59c3657f546d25f9ec3a5fbc423eaf632a0a0178b7ac7b311fe403031b8d701", "query": "serviceAccountName: fluentd-gcp-scaler containers: - name: fluentd-gcp-scaler <del> image: gcr.io/google-containers/fluentd-gcp-scaler:0.1 </del> <ins> image: gcr.io/google-containers/fluentd-gcp-scaler:0.2 </ins> command: - /scaler.sh - --ds-name=fluentd-gcp-v3.0.0", "positive_passages": [{"docid": "doc-en-kubernetes-2efbc26b22516e4405a8d5724e6f4faec26f16538d69327dd97918ad592fbe81", "text": "So I took a look and seems like the fluentd-scaler version bump (which was supposed to fix) was merged b/w runs and of our . However, I don't see any visible improvement in controller-manager memory usage around that time: !\nAlso, I'm noticing such lines occasionally (once every 5-10 secs in the start and once every ~1min later on) from of latest run: And back when the fluentd-scaler wasn't doing anything useful (i.e before ), the had such lines only sparingly.\nNow it isn't even sending requests (other than GET) to the apiserver. How do you generate that graph? Is it 99th percentile of memory usage over time? Or what exactly? One difference after introducing fluentd-gcp-scaler is that now there is a change occurring on the DaemonSet (once, but still). Also, what test is failing because of this? I'd like to take a look into the logs.\nAnswering your questions: I fetched the ResourceUsageSummaries for density test from historical runs (e.g ) and then obtained the 99% mem-usage for controller-manager for each run. Yes. More precisely, we're collecting mem-usage from controller-manager once every 1 min (or sth like that) and then taking 99th %ile of the resulting sample. Density and load tests. Where we're checking that mem usage of controller-manager is less than the given threshold (i.e 500MB). Ref: The tests are occasionally failing due to just crossing the threshold. Overall, the mem-usage had seen an increase back during the scaler change (see graph above). The job is this - https://k8s- Inside , you'll find all necessary logs (also a file named which has the resource-usage data).\nThe fluentd-scaler update eliminated fluentd restarts problem. Verified from controller-manager logs that we no longer see such logs that we were : This is great, and I believe that moves this out of release-blocker as we no longer face problems I mentioned in\nThat said, and me will continue looking into increase in mem-usage (which is not that serious). We'll start by verifying that turning the scaler off improves mem-usage.\nFeel free to override me if you have a good reason :)\nI agree that this doesn't sounds to be release-blocker.", "commid": "kubernetes_issue_61190", "tokennum": 529}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d59c3657f546d25f9ec3a5fbc423eaf632a0a0178b7ac7b311fe403031b8d701", "query": "serviceAccountName: fluentd-gcp-scaler containers: - name: fluentd-gcp-scaler <del> image: gcr.io/google-containers/fluentd-gcp-scaler:0.1 </del> <ins> image: gcr.io/google-containers/fluentd-gcp-scaler:0.2 </ins> command: - /scaler.sh - --ds-name=fluentd-gcp-v3.0.0", "positive_passages": [{"docid": "doc-en-kubernetes-ad76c0c3dd106ecff60d8298c8700ef88a9f32d4985b54e29d57ef6ad7351ef8", "text": "But I would like to see follow-ups at least for issues like: does this memory increase come from? what was claimed to be \"no-op\" changes for daemon set were causing problems [is that issues in kubectl, apiserver, somewhere else?] Something like that may hit us again in the (near?) future if we won't understand it now. The current solution is really volatile [if there is a bug somewhere we shouldn't workaround it on our side, but instead have this fixed] at the cluster start (maybe it's fine to leave as is, but I would like to see a discussion of that and a conscious decision being made here)\nDefinitely agree those are questions we need to answer.\nYup. 1) is tested in . 2) I believe apiserver sends watch events even when only resource version changes, which causes the daemonset controller to recreate the pods. So either: resource version shouldn't change when there is no change anywhere else in the resource apiserver shouldn't send watch events when only resource version is changing daemonset should check whether watch event it got is actually changing anything 3) Isn't that an inherent part of the way addon manager works? It creates all sorts of resources, some dependent on the other (e.g. cluster roles and cluster role bindings), all at once. If some dependency is not satisfied, it will get fixed during the next run.\nThis is the code that is supposed to protect us from situation that something must change when we write object to etcd (resource version is not stored in etcd): So there should never be a situation that only resource version is changing. If it is, there is bug and need to be fixed. - FYI Reconciliation is a different thing that creating something in one state only to change that to a different state by a different component. I'm not saying this is for sure wrong approach. But I would like to see a conscious decision process discussing pros-and-cons of that.\nThat's what I'd expect as well. This I'm not sure if should be correct behaviour as IIUC watchers need to receive every RV update for correctness reasons ( ) Maybe. But are we sure if RV is just increasing without any object change? For creation of addons, yes (that race will likely last only for starting few seconds).", "commid": "kubernetes_issue_61190", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d59c3657f546d25f9ec3a5fbc423eaf632a0a0178b7ac7b311fe403031b8d701", "query": "serviceAccountName: fluentd-gcp-scaler containers: - name: fluentd-gcp-scaler <del> image: gcr.io/google-containers/fluentd-gcp-scaler:0.1 </del> <ins> image: gcr.io/google-containers/fluentd-gcp-scaler:0.2 </ins> command: - /scaler.sh - --ds-name=fluentd-gcp-v3.0.0", "positive_passages": [{"docid": "doc-en-kubernetes-87ee63a141c821e91ed597807f3f6830646e2e9b40e1991334df493e9d39b5a9", "text": "But this is wrt addon changing cluster resources, which can potentially create race at arbitrary time after cluster start (though your fix may have gotten rid of this).\nOk.. Seems like I missed Wojtek's comment above.\nSo I just checked the ds-controller code and it seems like we're updating the ds status only if this condition is being violated: Which means one of those fields is probably mismatching. I'll try to add some logs and run the test at --v=4 to get more info.\nanything is possible, but we do have tests ensuring this works properly (no-op updates do not actually result in an update+resourceVersion bump in etcd):\nSo I ran some 100-node experiments against with more debug logs and I think I now understand the reason for this. The controller-manager logs and mainly show the following difference: This logs show-up when the scaler is active. And these pod deletions are happening as part of rolling-upgrade of daemonset to newer version (the one having resources set). You can see they're getting deleted one-by-one, which also explains why it takes so long (and so are happening even 30 mins after the cluster creation). And the reason why they're deleted one-by-one is because ds-controller has a rolling-upgrade strategy where by default. Proof: And the increased mem-usage FMU is because of the rolling-upgrade performed by ds-controller (over the prolonged period) - as it's the only difference I observe from logs Further, the reason why the RV was increasing was because of few fields 'NumUnavailable', 'NumAvailable', etc fluctuating while the rolling-upgrade\nI spoke offline with and suggested that we should increase maxUnavailable for the fluentd daemonset to a large enough value so that we're not bottlenecked by it. My reasoning is: fluentd is not some user workload which will have some service downtime in case there are many unavailable at once fluentds on nodes are independent of each other (i.e one fluentd shouldn't need to wait for another node's fluentd to come up) we should try to make the scaling happen as fast as possible - otherwise it may be too late before they cope-up with increased log-load in the cluster I'm going to make that change and test it against my PR (thanks for pointing that we can change maxUnavailable directly in ds config).", "commid": "kubernetes_issue_61190", "tokennum": 536}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d59c3657f546d25f9ec3a5fbc423eaf632a0a0178b7ac7b311fe403031b8d701", "query": "serviceAccountName: fluentd-gcp-scaler containers: - name: fluentd-gcp-scaler <del> image: gcr.io/google-containers/fluentd-gcp-scaler:0.1 </del> <ins> image: gcr.io/google-containers/fluentd-gcp-scaler:0.2 </ins> command: - /scaler.sh - --ds-name=fluentd-gcp-v3.0.0", "positive_passages": [{"docid": "doc-en-kubernetes-90b3139f2f371dfe70c636d4111a7217036a6164fbce02b650a75f688275a9fd", "text": "So increasing maxUnavailable indeed seems to help (ref: ): All the 101 replicas were deleted at once instead of one-by-one and happened pretty much within 2 mins of the original fluentd-ds seen by the controller: We should get that PR into 1.10.\nThanks for confirming this! Did increasing maxUnavailable also reduce c-m memory usage?\nSo the run was still over the threshold, but I was expecting it as I ran c-m with increased verbosity (which ). That said, I'll observe how the usages are once that PR gets in - and FMU it's still possible to have higher values due to the rolling-upgrade potentially happening during the test.\nIs there anything else to do here or should this be closed now?\nLet's close it once we're sure there are no more such failures. We may also need to bump the threshold. On Mon, Mar 26, 2018, 9:46 AM Kubernetes Submit Queue < :\nSo bumping maxUnavailable for fluentd rolling-upgrade in is causing couple of issues: Our latest 5k-node performance failed as part of BeforeSuite where we're checking that ~all kube-system pods are running or ready. The reason is because quite some fluentd pods were killed as part of the rolling-upgrade and we timed out before all those pods could come up Our 100-node performance runs due to high CPU/mem-usage of c-m observed during density test, in cases when the fluentd upgrade happens during the test - which is kind of expected So at this point, we might want to choose among one of the 2 options: Rollback , which comes at the cost of tradeoffs I explained in Increase our CPU/mem thresholds to eliminate those flakes in 100-node job and increase the \"max-allowed-not-ready-pods\" in kube-system ns to a higher value, so that our 5k-node test doesn't fail in BeforeSuite Thoughts?\nTBH, I don't know why it was merged without waiting for opinions... I really vote for reverting that. We don't want this - this may mean making cluster \"not fully usable\" from user perspective.Which is not really what we want to test.\nSGTM. Let's revert it and increase our thresholds for the time-being. The discussion about changing fluentd rolling-upgrades can continue to happen in the background.", "commid": "kubernetes_issue_61190", "tokennum": 523}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d59c3657f546d25f9ec3a5fbc423eaf632a0a0178b7ac7b311fe403031b8d701", "query": "serviceAccountName: fluentd-gcp-scaler containers: - name: fluentd-gcp-scaler <del> image: gcr.io/google-containers/fluentd-gcp-scaler:0.1 </del> <ins> image: gcr.io/google-containers/fluentd-gcp-scaler:0.2 </ins> command: - /scaler.sh - --ds-name=fluentd-gcp-v3.0.0", "positive_passages": [{"docid": "doc-en-kubernetes-59f7438c09573642bfc1d12812df1bf9a90b62da276e49f75dd1387c9fcb0e09", "text": "[MILESTONENOTIFIER] Milestone Issue Needs Approval Action required: This issue must have the label applied by a SIG maintainer. If the label is not applied within 5 days, the issue will be moved out of the v1.11 milestone. <details<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details\nThis issue is now fixed after my above PRs. We're having continuous for the job", "commid": "kubernetes_issue_61190", "tokennum": 184}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d5b996990ab915bf399dfd3aec7f2b777370c3e322f92ecca5a411bb2c1ba2fb", "query": "func RunEdit(f *cmdutil.Factory, out, errOut io.Writer, cmd *cobra.Command, args []string, options *EditOptions) error { var printer kubectl.ResourcePrinter var ext string <ins> var addHeader bool </ins> switch format := cmdutil.GetFlagString(cmd, \"output\"); format { case \"json\": printer = &kubectl.JSONPrinter{} ext = \".json\" <ins> addHeader = false </ins> case \"yaml\": printer = &kubectl.YAMLPrinter{} ext = \".yaml\" <ins> addHeader = true </ins> default: return cmdutil.UsageError(cmd, \"The flag 'output' must be one of yaml|json\") }", "positive_passages": [{"docid": "doc-en-kubernetes-1ecb677d90f8210e5dc6b2a237f898f5f4f944a4f983b5bfcd84eaf55dd52c98", "text": "Recently I was experimenting with changing for a Golang pre-purposed faux editor when editing resources when I noticed that it couldn't be marshaled. Upon inspecting the output JSON I noticed it had the same comments that the default yaml version has. Valid JSON cannot have comments. Since the comment also gives warning / error information upon saving it must be decided where to put that in the JSON output. Perhaps a new JSON property?\nMaybe just not save the comments as part of the json to get rid of the warning, but still should them?\nIs this a 1.2 thing? I do not see any errors when running the two commands. I made an edit in one run, and did not make an edit in a separate run. Maybe I don't understand the problem that is seen.\nthere isn't a kubernetes error that is shown, the issue is that the output JSON that kubernetes generates is actually invalid JSON due to the comments at the top. This caused errors when I was trying to unmarshal that JSON in another project.\nOkay. Got it. The editor is being very strict about json having no comments.\nIt's not only about editor, it's simply part of language specification. Explanation for this: IMO if we want to use format, we should comply with it's standard. Also currently used sign for comments is unusual in javascript world, from which json evolved. In this world comments are marked in \"C++ like\" style (what in early days of JSON was also supported), i mean using and . So IMO in time of converting into JSON - we should strip such comments (I would prefer that), or they should be in some documented and specific to kubernetes way into JSON object.", "commid": "kubernetes_issue_29524", "tokennum": 377}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d5c5378f24fb46bd45f685f67eaff4fbed9650af9553afa78f5caa2dd351db0c", "query": "dns_replicas: '$(echo \"$DNS_REPLICAS\" | sed -e \"s/'/''/g\")' dns_server: '$(echo \"$DNS_SERVER_IP\" | sed -e \"s/'/''/g\")' dns_domain: '$(echo \"$DNS_DOMAIN\" | sed -e \"s/'/''/g\")' <ins> instance_prefix: '$(echo \"$INSTANCE_PREFIX\" | sed -e \"s/'/''/g\")' </ins> EOF # Configure the salt-master", "positive_passages": [{"docid": "doc-en-kubernetes-618a17ee1a2bfcaa30e720bd6c59c3ac91ee900494c2c92ac1b2427757bb09d9", "text": "reported a variety of failure modes in .\n+1\nI figured I'd add to this issue rather than create a new one. I attempted to create a vagrant cluster today (dev tree is up to date) with 1 Master and 1 Minion and the cluster creation is stuck in the 'Validating master' loop ( for over 10 minutes in the validating loop ). salt-master and salt-minion logs seem to be empty ( they don't appear to be running, in fact ).\nI still have the cluster running in case anybody wants additional information.\n/cc please let me know if there is any other information about my vagrant setup that I need to post here.\nI have been working to get more stability in this environment over last few days. Can you try again from HEAD after this merges:\nCan you also verify that you built a release prior to running cluster/Kube-up?\nyes, I started from scratch and built a release before running cluster/kube- - cluster/kube- seems to fail fairly early in case there is no release build available.\nIt looks like got merged. I'll try again and get back to you.\nThe vagrant cluster seems to come up ( completes master and minion validation ). However, there is new credentials related error that is showing up at the end of running cluster/kube- :\nI'll add one more problem I've encountered. Runing from head:\nNew to me. Will investigate more tomorrow. Sent from my iPhone\nAlso new to me :-) - will see if I can reproduce either. Sent from my iPhone\nYour credendials and certificates are not working with new environment. Just delete your .kubernetesvagrant* files and recreate the cluster. It would be nice to automate this task, if you tear down the cluster.\nI am able to reproduce the 502 Bad Gateway error and am working on determining what changed in order to provide a resolution over the last couple days. Please assign this issue to me.\nThe issue appears to me that the kube-apiserver is not getting provisioned by salt correctly. Parsing Salt logs to determine why.\nLooks like the file is not getting laid down by salt for some reason ;-)\nThe Jinja template was changed as part of identifying the cluster. Fixing up now, and will send a PR to close this issue.\nthat was it, thanks!", "commid": "kubernetes_issue_4302", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d5d533fc778301049964f4ae9752b2bb6703e554d7614fc3e24d43e266658e28", "query": "\"k8s.io/kubernetes/pkg/controlplane\" \"k8s.io/kubernetes/pkg/features\" \"k8s.io/kubernetes/test/integration/framework\" <ins> \"k8s.io/utils/ptr\" </ins> ) const (", "positive_passages": [{"docid": "doc-en-kubernetes-cbff279a5a2209254c6527f41e3183737e33b6607a7e6fb4945b04f53611a022", "text": "My application is clustered and I have 2 pods running. I am using a rolling upgrade strategy and my partitioning number is 1. First I need to upgrade the pod with the ordinal number 1 so I triggered that upgrade with partitioning number 1 and my upgrade gets completed. After this, my pod having the ordinal number 0 gets restarted and it's automatically upgraded to a new image. This is not an expected behavior because still, my partition number is 1 and pod-0 should come up with an older image only. I am facing this issue for the v1.27 cluster. Prior to this, it was working fine. pod-0 should not upgrade to new image until I upgrade the partition number to 0.a Do helm install and upgrade pod-1 only keeping partition number to 1. No response <detailsconsole $ cat /etc/os-release $ uname -a C:wmic os get Caption, Version, BuildNumber, OSArchitecture </details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig/api-machinery\n/sig apps /sig storage\nHi, Can someone suggest here? As this is introduced in my setup after the v1.27 upgrade? Is there any change in partition logic?\nThis can be reproduced by using the said STS. 1 - Deploy STS using attached that has a replica count is 2 and updatingstrategy.rolling.partition as 1. 2 - Do edit STS and update the image to 1.15. This will upgrade, pod-1 with image 1.15. 3 - Next delete the pod pod-0 and check that POD-0 came up with a new image which is not the expected behavior. POD 0 should not be updated to a new image until the partition is changed to 0. We have noticed this behavior change in v1.27.", "commid": "kubernetes_issue_119685", "tokennum": 476}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d5d533fc778301049964f4ae9752b2bb6703e554d7614fc3e24d43e266658e28", "query": "\"k8s.io/kubernetes/pkg/controlplane\" \"k8s.io/kubernetes/pkg/features\" \"k8s.io/kubernetes/test/integration/framework\" <ins> \"k8s.io/utils/ptr\" </ins> ) const (", "positive_passages": [{"docid": "doc-en-kubernetes-78482ca8aa8474337677389890aeefe9bf7c97cdeab333d3d2b330616683b55b", "text": "Pla suggest : apiVersion: v1 kind: Service metadata: name: nginx labels: app: nginx spec: ports: port: 80 name: web clusterIP: None selector: app: nginx apiVersion: apps/v1 kind: StatefulSet metadata: name: web-am spec: updateStrategy: type: RollingUpdate rollingUpdate: partition: 1 serviceName: \"nginx\" replicas: 2 selector: matchLabels: app: nginx template: metadata: labels: app: nginx spec: containers: name: nginx args: /bin/sh -c sleep 30;touch /tmp/healthy; sleep 3600 image: nginx:1.14.2 ports: containerPort: 80 name: web", "commid": "kubernetes_issue_119685", "tokennum": 170}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d5e11b6d776ba27758d557bf5a385539226d58ceb1166bfd256d021409372d6a", "query": "// If \"only_cpu_and_memory\" GET param is true then only cpu and memory is returned in response. func (h *handler) handleSummary(request *restful.Request, response *restful.Response) { onlyCPUAndMemory := false <del> request.Request.ParseForm() </del> <ins> err := request.Request.ParseForm() if err != nil { handleError(response, \"/stats/summary\", errors.Wrapf(err, \"parse form failed\")) return } </ins> if onlyCluAndMemoryParam, found := request.Request.Form[\"only_cpu_and_memory\"]; found && len(onlyCluAndMemoryParam) == 1 && onlyCluAndMemoryParam[0] == \"true\" { onlyCPUAndMemory = true } var summary *statsapi.Summary <del> var err error </del> if onlyCPUAndMemory { summary, err = h.summaryProvider.GetCPUAndMemoryStats() } else {", "positive_passages": [{"docid": "doc-en-kubernetes-2d86227263004d2306fadc99355cf0a88aac1d38d7e2576116201cd81e3141b9", "text": "What happened: In handler#handleSummary, return value from request.Request.ParseForm() is ignored. What you expected to happen: The error return should be checked.\n/sig node\nHi this seems to be easy to fix. Could I solve this?\nPlease go ahead.", "commid": "kubernetes_issue_90085", "tokennum": 62}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d62fe7207ea5c3cfe4b418d2ff45e09670447f8ae92dbda5af0eae6fc9e7e6da", "query": "<del> apiVersion: extensions/v1beta1 </del> <ins> apiVersion: networking.k8s.io/v1beta1 </ins> kind: Ingress metadata: name: echomap", "positive_passages": [{"docid": "doc-en-kubernetes-bb7c21eb048735f6a80e177a210d26530b5959539babed9d56a66ccfff61adf4", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: Which test(s) are failing: Since when has it been failing: Testgrid link: https://k8s- Reason for failure: Anything else we need to know: /cc /milestone v1.19 /priority important-soon /sig network\nRef:\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nmy fu points me to this commit [] Fix multiple conversion tests that belongs to this PR , that seems related can you confirm if that PR is causing this test to fail? (should we gate on this test?)\nYes, that PR is related to the failure. The test utility is trying to convert extensions/v1beta1 data read from various files directly to a go type. This was never a valid thing to do, and happened to silently succeed because the two structs had an identical structure. This is exactly the type of bug was designed to flush out\nthe correct fix is to update the test/e2e/testing- files to\n/assign\nIt was my PR that broke this - I can also fix that.\nThanks, o it was the commit that was good but the test that was wrong :upsidedownface: , At least I got right the commit :sweat_smile:\nis out for review (talked with offline, he was aware that I'll send that out)", "commid": "kubernetes_issue_90451", "tokennum": 318}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d64887a7ca095941c7d7f13b66a7628c6961c50e0dfc0628a57152cc5c0eeb44", "query": "import ( \"context\" <ins> \"errors\" </ins> \"fmt\" \"io/ioutil\" \"net/http\"", "positive_passages": [{"docid": "doc-en-kubernetes-0ebc3a18530206d54bf966306c4d4d56c4fb7ca61cedeffe6a0cab2bf1fe76ea", "text": "In we discovered a bug where kube-apiserver metrics were being incorrectly reported (GET vs LIST problem). In this was addressed together with test exercising that proper metrics are exposed. However, this test isn't ideal because if params wouldn't be swapped, it wouldn't catch them. We should ideally develop a lower-level unit test for mapping url paths to exact values of labels/parameters. /sig apimachinery\nThe label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : In we discovered a bug where kube-apiserver metrics were being incorrectly reported (GET vs LIST problem). In this was addressed together with test exercising that proper metrics are exposed. We should ideally develop a lower-level unit test for mapping url paths to exact values of labels/parameters. 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\n/sig api-machinery\nare you planning on sending a fix for this one too? Thanks!\nNot very soon - if someone else could help with it, it would be great.\n/assign\n/triage accepted\ncc", "commid": "kubernetes_issue_95636", "tokennum": 258}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d655ba88b93bc1d650e3e651e10e0193b765d4303a01c40d75fe8ffd0a88300b", "query": "return true } } <ins> for _, c := range pod.Spec.InitContainers { if c.Name == containerName { return true } } </ins> return false }", "positive_passages": [{"docid": "doc-en-kubernetes-b8cb95fef1c3c524a6b804cd28cd2236820a76e473144ffd27898d08f0344824", "text": "Need to finish so the client allows you to select an init container, and verify the kubelet works correctly.\n(this is a nice intersection of new in 1.3, node and usability, if anyone wants to give it a shot. Pretty sure Clayton is busier than I am and I don't think I'll get to it)\nWill be happy to review any changes - should be fairly straightforward.\nYes, init containers are \"run to completion\" always. , harryz wrote:\nIIUC when the init containers of pod have not complete, the pod should be in status, which means will fail, if init containers run to completion, they will exit, still fail. I don't know what you mean exec should work on init containers?\nthe init container is still up and running even when the pod is in pending, we should be able to exec and debug why it's hung, for example.\nadd a straightforward exec implementation ptal.", "commid": "kubernetes_issue_25818", "tokennum": 207}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d67eb2c8061aec2396ea60df5989b444a242c6b0bc7dbf0635397675d841adb4", "query": "\"github.com/Azure/go-autorest/autorest/to\" \"github.com/stretchr/testify/assert\" \"k8s.io/api/core/v1\" <ins> metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" </ins> ) func TestFindProbe(t *testing.T) {", "positive_passages": [{"docid": "doc-en-kubernetes-94ebb6d5cc5a883444cc57b7fe675619934dadcea635fbafcba0058503bec1c7", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: When service is set with ILB annotation and empty string subnet, e.g. The service would be pending forever with following error: What you expected to happen: ILB should be provisioned successfully. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Others: /sig azure /kind bug /assign\n/milestone v1.14 We're entering and this looks relevant to the 1.14 release. Please if I am incorrect\nThanks", "commid": "kubernetes_issue_74497", "tokennum": 195}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d69110f4e78f061a397baf38e81382a0d75906406ab53c89d7a4e5b28e404ec4", "query": "}, nil } <del> func (c *configFactory) getNextPod() *v1.Pod { pod, err := c.podQueue.Pop() if err == nil { klog.V(4).Infof(\"About to try and schedule pod %v/%v\", pod.Namespace, pod.Name) return pod } klog.Errorf(\"Error while retrieving next pod from scheduling queue: %v\", err) return nil } </del> // assignedPod selects pods that are assigned (scheduled and running). func assignedPod(pod *v1.Pod) bool { return len(pod.Spec.NodeName) != 0", "positive_passages": [{"docid": "doc-en-kubernetes-90b5ca2d1baaaaa2aa124277e8c3fdace970eae885ff81aa4062d924fde9dbb7", "text": "PLEASE COORDINATE WITH SIG-SCHEDULING BEFORE WORKING ON THIS ISSUE. We want to avoid the situation where two people accidentally start work on the same fix. Main tracking issue: The method of is a simple wrapper around . It should be converted into a simple closure instead of being a method. i.e. we should have, (code is in ) /sig scheduling /kind cleanup /help\nI'd like to take this task. /assign /remove-help\nThanks, go for it! :smile:", "commid": "kubernetes_issue_72546", "tokennum": 104}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d6963d0e1453ddcd554230e7f1287c9eb640f8000ea3f99e9aca8dd227cf3075", "query": "CGROUP_ROOT=${CGROUP_ROOT:-\"\"} # name of the cgroup driver, i.e. cgroupfs or systemd CGROUP_DRIVER=${CGROUP_DRIVER:-\"\"} <ins> # owner of client certs, default to current user if not specified USER=${USER:-$(whoami)} </ins> # enables testing eviction scenarios locally. EVICTION_HARD=${EVICTION_HARD:-\"memory.available<100Mi\"}", "positive_passages": [{"docid": "doc-en-kubernetes-9ac079d1fd510b2062bc937a63b320f5cb9c70bc1e9e6c0c16b4b25caa3b72aa", "text": "Encountered this error while running on master: Should we set to by default? cc\nWhy is it empty? Would be better?\nseems to expect $(whoami) based on the value of that variable for my machine. I can make that change if you would like.\nCan you keep as an option if it is specified? returns a 6 digit numeric value on my machine (corporate provisioned) and that is incompatible with GCI images, as well as error-ing out during e2e provisioning.\nthat is a great idea, so should be defaulting to whoami in the case where it has not been defined.\nOK, will file an PR to fix this.\nFiled PR at . PTAL", "commid": "kubernetes_issue_41560", "tokennum": 143}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d6d3d8f8d081bf27aee9dc66b37e130ca3079e086e204de6ae07d97006e3beb8", "query": "return nil, err } <del> return newRuntimeVersion(typedVersion.Version) </del> <ins> return newRuntimeVersion(typedVersion.RuntimeVersion) </ins> } // APIVersion returns the cached API version information of the container", "positive_passages": [{"docid": "doc-en-kubernetes-36c3b1963e29994fcef0db8f2a8b4a629c6bfc24057a3ec2a6314c1367d30587", "text": "Is this a BUG REPORT or FEATURE REQUEST? : BUG: With CRI enabled by default, kubelet reports the version of CRI instead of container runtime version: Kubernetes version (use ): Master and 1.6. What you expected to happen: Kubelet should report the version of container runtime. Will file a PR to fix this. cc", "commid": "kubernetes_issue_42396", "tokennum": 77}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d6e352b13842b5df128e3b27c9b4d955b60634437d81caadc4683b0487255b0f", "query": "// use kubeletServer to construct the default KubeletDeps kubeletDeps, err := app.UnsecuredDependencies(kubeletServer) <ins> if err != nil { die(err) } </ins> // add the kubelet config controller to kubeletDeps kubeletDeps.KubeletConfigController = kubeletConfigController", "positive_passages": [{"docid": "doc-en-kubernetes-ead4a113e3280b31adabcef2a84a488ae269cf78485f762926d30cc661385643", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Testing bringing up k8s cluster using kubeadm from latest k8s code from master branch. kubelet is not coming up and below is the errors from syslog: upon looking at the code from where the error is happening, it is evident that the err checking is missing. What you expected to happen: deployment to succeed. How to reproduce it (as minimally and precisely as possible): Use the latest code from k8s and build a k8s release and bring up cluster using kubeadm Anything else we need to know?: Environment: Kubernetes version (use ): latest Cloud provider or hardware configuration**: GCE OS (e.g. from /etc/os-release): 16.04 LTS (Xenial Xerus) Kernel (e.g. ): Linux e2e--master 4.4.0-21-generic -Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x8664 x8664 x86_64 GNU/Linux Install tools: kubeadm Others: /sig node /cc\nPTAL", "commid": "kubernetes_issue_50981", "tokennum": 254}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d74dc590ea21d50cddd0907c06edcc753f64f733913efa949cb1729a10029737", "query": "obj.CgroupDriver = \"cgroupfs\" } if obj.EnforceNodeAllocatable == nil { <del> obj.EnforceNodeAllocatable = defaultNodeAllocatableEnforcement </del> <ins> obj.EnforceNodeAllocatable = DefaultNodeAllocatableEnforcement </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-937f1cb17c20e5fd2b4a1f81201690c3dbe6990ef3c1bc74ff71daaa02b6db56", "text": "Solution: I will add one.\n/cc\nxref\nThanks for sending a PR so quickly!\n[MILESTONENOTIFIER] Milestone Issue Needs Attention Action required: During code slush, issues in the milestone should be in progress. If this issue is not being actively worked on, please remove it from the milestone. If it is being worked on, please add the label so it can be tracked with other in-flight issues. Note: If this issue is not resolved or labeled as by Wed, Nov 22 it will be moved out of the v1.9 milestone. <details<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details", "commid": "kubernetes_issue_55959", "tokennum": 230}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d7510cc8968ea9338e33b5821c9e064913bc2a177cc951d0e83065f977f4b883", "query": "package testutil import ( <ins> \"fmt\" </ins> \"io\" \"github.com/prometheus/client_golang/prometheus/testutil\" <ins> apimachineryversion \"k8s.io/apimachinery/pkg/version\" </ins> \"k8s.io/component-base/metrics\" )", "positive_passages": [{"docid": "doc-en-kubernetes-b57bf0f1b2dd71c1293d1dafb95c6e51debc5c1d26878053edb8d335b76a3a11", "text": "What would you like to be : Once a metric be deprecated, we should update the unit test accordingly if there is any. We need to work out a way for a unit test freely select codebase version, and also should make sure the unit test won't fail in the subsequent release. Why is this needed: Deprecated also needs to be protected. /sig instrumentation /assign", "commid": "kubernetes_issue_86292", "tokennum": 81}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d75db80d926acf95c179839fb998106ab2e416852d194f096bb68a624512fe9d", "query": "// alpha: v1.4 ExternalTrafficLocalOnly utilfeature.Feature = \"AllowExtTrafficLocalEndpoints\" <del> // owner: @saad-ali // alpha: v1.3 DynamicVolumeProvisioning utilfeature.Feature = \"DynamicVolumeProvisioning\" </del> // owner: @mtaufen // alpha: v1.4 DynamicKubeletConfig utilfeature.Feature = \"DynamicKubeletConfig\"", "positive_passages": [{"docid": "doc-en-kubernetes-9bc3939632f91b367e9735795407824b8635b986a1aa4d3e42f19abbece1efa5", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: kube-apiserver --help still shows this: It looks like the related feature can be turned off. However, dynamic volume provisioning Alpha has retried in 1.6. What you expected to happen: Remove from feature gate to avoid confusion. How to reproduce it (as minimally and precisely as possible): Run Anything else we need to know?: No Environment: Kubernetes version (use ): 1.7+ Cloud provider or hardware configuration**: Any OS (e.g. from /etc/os-release): Any Kernel (e.g. ): Any Install tools: Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig api-machinery\n/sig api-machinery\nSIG API Machinery doesn't own the contents of the API. /sig storage", "commid": "kubernetes_issue_51120", "tokennum": 274}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d76bd83d1ada350f58905f83f5af40df6159c71d92a0ef6b4f5140d0a1cc266a", "query": "// For each groupversion served by our resourcemanager, create an APIService // object connected to our fake APIServer <ins> var groupVersions []metav1.GroupVersion </ins> for _, versionInfo := range basicTestGroup.Versions { groupVersion := metav1.GroupVersion{ Group:   basicTestGroup.Name,", "positive_passages": [{"docid": "doc-en-kubernetes-a36678f387087dd8252401a5249426873ced2ebb26644cae4efea96ce80ca1f6", "text": "reported that conformance testing with the latest version of sonobuoy against a version 1.29.0-alpha.3 cluster fails on the support the 1.17 Sample API Server using the current Aggregator test: , related to I found the reason why the test is working fine in Kubernetes CI jobs but fails with sonobuoy is because the service account used by sonobuoy \"sonobuoy-serviceaccount\" doesn't have read permission of the non-resource url \"/\", which is used by the test to confirm the removal of group path: The permission of \"sonobuoy-serviceaccount\" is as below: There may be two ways to fix it: the RBAC rule of sonobuoy to include \"get\" of \"/\". However, could other test runners encounter this issue? Is there a doc listing the required permissions for running e2e tests? the e2e to skip checking the removal of the group path if the service account doesn't have permission to access the root path. Which way do we usually prefer? Running e2e with sonobuoy should succeed. a v1.29.0-alpha.3 cluster. No response <details</details<details</details<details</details<details</details<details</details<details</details\nimplemented this solution.\n/sig api-machinery\nthank you for opening this issue and working on a solution. I'm probably not the right person to decide on which solution is preferred. From my perspective, either solution is fine.\nNote: Sonobuoy is not owned by any Kubernetes SIG. At most it is between SIG Architecture and the CNCF to choose whether to recommend it for running tests. SIG Testing owns the e2e image that sonobuoy can be used to schedule but not sonobuoy. IMHO this is a bug in running the tests via a pod, which is not how we develop the tests (they're run outside the cluster, by a cluster admin account typically). I would say 1) is the correct answer. xref: /sig architecture /sig testing /triage accepted cc\nthanks for your comment. I guess 1) means non of the existing sonobuoy versions can pass K8s conformance test against a cluster 1.29.0-alpha3, as the RBAC rule is hardcoded.", "commid": "kubernetes_issue_121985", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d76bd83d1ada350f58905f83f5af40df6159c71d92a0ef6b4f5140d0a1cc266a", "query": "// For each groupversion served by our resourcemanager, create an APIService // object connected to our fake APIServer <ins> var groupVersions []metav1.GroupVersion </ins> for _, versionInfo := range basicTestGroup.Versions { groupVersion := metav1.GroupVersion{ Group:   basicTestGroup.Name,", "positive_passages": [{"docid": "doc-en-kubernetes-4545476cbce0605bfe46d5a01c41b8f4cf7b5ac07772bfb1748611bc506e90ef", "text": "I will file an issue to sonobuoy first.\nquestion here is what are the set of client permissions required to run the conformance suite? perhaps a level of access or a more granular recommendation should be documented. what is your take on the root path requirement as approver for: EDIT: slack thread:\nI agree, we already require e.g. privileged pods for a long time in conformance tests and we should make it clear that we expect a highly privileged client.\n+1 for what is saying, that we should expect that the user running the tests has required permissions. These tests are not built for being run unprivileged.\ni wanted to PR the admin note in our conformance docs under sig-arch, but then i saw this: so broke this guarantee. sounds like SIG Arch needs to comment.\nThis statement surprises me. Root discovery is one of the least-privileged permissions you can have on a cluster. For years this was even open for unauthorized users on the internet (if your api endpoint has been exposed). In other words, just add the permission. While thinking about it, it is surprising that the user in question does not have this access already. Don't we allow that for every authorized user?\nIn contrast, I hope that lots of privileged operations are tested by conformance today. If we don't test things like admission webhooks for example, we have much bigger problems. And admission webhooks are basically equivalent to cluster-admin.\nthat is outdated, we use hostNetwork pods one some of the tests IIRC\nlooks like we don't. before this ticket, i was under the impression that the conformance suite already requires admin and that all testers (like Sonobuoy) use admin level credentials. it is non-privileged (e.g., does not require root on nodes, access to raw network interfaces, or cluster admin permissions) looks like we may have to change that sentence completely.\nWould have expected it here: The PR in question explicitly fixes the result returned by . If that is part of conformance (IMO it should), every conformance test needs access it obviously. Whether we require admin, or we add it manually, either would work.", "commid": "kubernetes_issue_121985", "tokennum": 474}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d76bd83d1ada350f58905f83f5af40df6159c71d92a0ef6b4f5140d0a1cc266a", "query": "// For each groupversion served by our resourcemanager, create an APIService // object connected to our fake APIServer <ins> var groupVersions []metav1.GroupVersion </ins> for _, versionInfo := range basicTestGroup.Versions { groupVersion := metav1.GroupVersion{ Group:   basicTestGroup.Name,", "positive_passages": [{"docid": "doc-en-kubernetes-06abc1218304c92779dae2744e33107a4d26263c1c54e4453f3f92a1949c2aa2", "text": "adding to milestone and making release blocking ... we should not release 1.29 in a state that the most commonly used conformance tool will fail\nIMO we should clarify the state and go fix the tool, but we should keep the test and we should NOT add skip. Conformance docs are not a release artifact, and sonobuoy release lifecycle is not a conformance artifact. If we can't get sonobuoy working in a reasonable time, we already know the tests can be run by scheduling the image (which is ours) directly with kubectl instead and we can document that in the upstream conformance docs. We need to fix the for this image: ,%20master%20(dev) And it should probably be to release-blocking in the future.\nit looks like the e2e change made in was not consciously made part of conformance, it was just trying to functionally test the bugfix being made. For 1.29, I think we should revert the change to and make an integration test that validates the fix instead. We can revisit whether content of is part of conformance or not for 1.30\nI opened to revert the e2e change and move the functional test to an integration test\nFiled to try to get the image job passing again.\nWe probably need another issue to track 1.30 follow-up?\nIf no one has done it, I could create another issue and follow up with the items that have been discussed here: outdated privilege requirement in commonly used conformance tools like sonobuoy aware of the required priviledge to avoid similar situations in the future. permission of GET \"/\" to authorized users via the role for root discovery.", "commid": "kubernetes_issue_121985", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d79222846c839f0972518666cdf1e2bb8c2efd0fef1215783d0e8054e2937936", "query": "fi done <ins> errors_expect_error=() for file in \"${all_e2e_files[@]}\" do if grep \"Expect(.*).To(.*HaveOccurred()\" \"${file}\" > /dev/null then errors_expect_error+=( \"${file}\" ) fi done </ins> if [ ${#errors_expect_no_error[@]} -ne 0 ]; then { echo \"Errors:\"", "positive_passages": [{"docid": "doc-en-kubernetes-c082543f1889f90c5ee780d309eeb8f41ee57a7e9e8bb6b6fe7c2e4381ff48af", "text": "What happened: After fixing golint failures under (now still in progress), we need to put for each and . Then common error checking code has become like: We can replace this code with which is more readable and easy to be understood what the code does. Now we have following e2e test directories which can be replaced: [x] test/e2e/apimachinery/ () [x] test/e2e/apps/ () [x] test/e2e/auth/ () [x] test/e2e/common/ () [x] test/e2e/node/ () [x] test/e2e/storage/ () [x] () [x] () [x] () [x] () [x] () [x] () [x] [x] test/e2e/storage/persistentvolumes- [x] () [x] () [x] [x] [x] [x] [x] ()\n/sig testing /kind cleanup\n/assign PR will be submitted soon.\nFix the following in\nFix in\nFix in\nHi, maybe I could take files beneath test/e2e/storage/vsphere/\noops, I'm finished and prepare for PR.\nThank you That's OK\nFix the following in\n/assign\nAll related PRs were merged. I think this ticket can be closed. BTW, should we also replace to ?\nThanks for your work. thing is managed with We are almost finishing the work also :-)\n/remove-kind bug\nI found in these files. I'm working on :\nI can work to the following item.", "commid": "kubernetes_issue_77706", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d7d29938a2b35b8a721331322db29686973334ac33584ed7b65cbe2dbc60f559", "query": "func (p *PriorityQueue) MoveAllToActiveQueue() { p.lock.Lock() defer p.lock.Unlock() <ins> // There is a chance of errors when adding pods to other queues, // we make a temporary slice to store the pods, // since the probability is low, we set its len to 0 addErrorPods := make([]*framework.PodInfo, 0) </ins> for _, pInfo := range p.unschedulableQ.podInfoMap { pod := pInfo.Pod if p.isPodBackingOff(pod) { if err := p.podBackoffQ.Add(pInfo); err != nil { klog.Errorf(\"Error adding pod %v to the backoff queue: %v\", pod.Name, err) <ins> addErrorPods = append(addErrorPods, pInfo) </ins> } } else { if err := p.activeQ.Add(pInfo); err != nil { klog.Errorf(\"Error adding pod %v to the scheduling queue: %v\", pod.Name, err) <ins> addErrorPods = append(addErrorPods, pInfo) </ins> } } } p.unschedulableQ.clear() <ins> // Adding pods that we could not move to Active queue or Backoff queue back to the Unschedulable queue for _, podInfo := range addErrorPods { p.unschedulableQ.addOrUpdate(podInfo) } </ins> p.moveRequestCycle = p.schedulingCycle p.cond.Broadcast() }", "positive_passages": [{"docid": "doc-en-kubernetes-25b4b43b77be18dfeeb1e5d60f56671fd9593ee9c291ed7dcecd0e9048479b76", "text": "What happened: We will now always delete the pods from unschedulable queue no matter the Add operations succeed or not in function. What you expected to happen: Delete pods from unschedulable queue only when add operations succeeds\n/sig scheduling\n/assign\nWill the pods be to the queues again somewhere if we delete them by mistake here ? It seems that can not make sure to add them again.\nI am not sure if we will add them back again somewhere. If not, not only but also need to be updated. I have already send a PR here:", "commid": "kubernetes_issue_78631", "tokennum": 120}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d81d826c0b568967ac299f979b8aa864f36a8e5b8b2ba77ec450b070b17d9b2d", "query": "if len(q.nominatedPods.nominatedPods) != 1 { t.Errorf(\"Expected nomindatePods to have one element: %v\", q.nominatedPods) } <del> if q.unschedulableQ.get(&unschedulablePod) != &unschedulablePod { </del> <ins> if getUnschedulablePod(q, &unschedulablePod) != &unschedulablePod { </ins> t.Errorf(\"Pod %v was not found in the unschedulableQ.\", unschedulablePod.Name) } }", "positive_passages": [{"docid": "doc-en-kubernetes-e059cd0647305d70a174ce6bffb9584a993a023526be428075760ddef27cc3b0", "text": "Which jobs are failing: pull-kubernetes-bazel-test Which test(s) are failing: bazel test //pkg/scheduler/internal/queue:godefaulttest Since when has it been failing: Testgrid link: Reason for failure: WARNING: DATA RACE Read at 0x00c000230db0 by goroutine 47: runtime.mapiterinit() +0x0 (PriorityQueue).flushUnschedulableQLeftover() +0x17a (PriorityQueue).flushUnschedulableQLeftover-fm() +0x41 () +0x61 () +0xce () +0x5a Previous write at 0x00c000230db0 by goroutine 45: runtime.mapassignfaststr() +0x0 (UnschedulablePodsMap).addOrUpdate() +0x30e () +0x601 testing.tRunner() +0x162 Goroutine 47 (running) created at: (PriorityQueue).run() +0x172 () +0xe0b () +0x50 () +0x5a5 testing.tRunner() +0x162 Goroutine 45 (running) created at: testing.(T).Run() +0x659 testing.runTests.func1() +0xa8 testing.tRunner() +0x162 testing.runTests() +0x4ee testing.(M).Run() +0x2ee () bazel-out/k8- +0x2fb Anything else we need to know: I'm very sorry about that. UnschedulablePodsMap is not thread-safe. In , lock will be acquired before operating UnschedulablePodsMap. But in , lock isn\u2018t be acquired. In the previous case, only a single thread runs so it's ok. But after add goroutine , there will be data race. So I need to acquire lock before operating UnschedulablePodsMap.\n/sig testing /sig scheduling", "commid": "kubernetes_issue_73021", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d82190b9d74ce6e83f0d3151b17f124972df97b0832eeca831773cc529e4e389", "query": "// GetCustomResourceListerCollectionDeleter returns the ListerCollectionDeleter of // the given crd. func (r *crdHandler) GetCustomResourceListerCollectionDeleter(crd *apiextensions.CustomResourceDefinition) (finalizer.ListerCollectionDeleter, error) { <del> info, err := r.getOrCreateServingInfoFor(crd) </del> <ins> info, err := r.getOrCreateServingInfoFor(crd.UID, crd.Name) </ins> if err != nil { return nil, err } return info.storages[info.storageVersion].CustomResource, nil } <del> func (r *crdHandler) getOrCreateServingInfoFor(crd *apiextensions.CustomResourceDefinition) (*crdInfo, error) { </del> <ins> // getOrCreateServingInfoFor gets the CRD serving info for the given CRD UID if the key exists in the storage map. // Otherwise the function fetches the up-to-date CRD using the given CRD name and creates CRD serving info. func (r *crdHandler) getOrCreateServingInfoFor(uid types.UID, name string) (*crdInfo, error) { </ins> storageMap := r.customStorage.Load().(crdStorageMap) <del> if ret, ok := storageMap[crd.UID]; ok { </del> <ins> if ret, ok := storageMap[uid]; ok { </ins> return ret, nil } r.customStorageLock.Lock() defer r.customStorageLock.Unlock() <ins> // Get the up-to-date CRD when we have the lock, to avoid racing with updateCustomResourceDefinition. // If updateCustomResourceDefinition sees an update and happens later, the storage will be deleted and // we will re-create the updated storage on demand. If updateCustomResourceDefinition happens before, // we make sure that we observe the same up-to-date CRD. crd, err := r.crdLister.Get(name) if err != nil { return nil, err } </ins> storageMap = r.customStorage.Load().(crdStorageMap) if ret, ok := storageMap[crd.UID]; ok { return ret, nil", "positive_passages": [{"docid": "doc-en-kubernetes-16c95be4925a0d298a67709c93efbb137b71325e5e3041edcf306d6572e4ae65", "text": "Which jobs are failing: pull-kubernetes-integration Which test(s) are failing: TestWebhookConverterWithDefaulting /assign /priority important-soon /area custom-resources /sig api-machinery /kind flake /milestone v1.16\n/cc\nseveral of the webhook converter tests have similar flakes. it looks like the wait for storage version to become effective times out occasionally Rare flakes seen in all of these tests: TestWebhookConverterWithWatchCache/nontrivial-converter TestWebhookConverterWithWatchCache/metadata-mutating-converter TestWebhookConverterWithDefaulting/metadata-mutating-converter TestWebhookConverterWithWatchCache/noop-converter TestWebhookConverterWithDefaulting/empty-response TestWebhookConverterWithoutWatchCache/nontrivial-converter/check-2 TestWebhookConverterWithoutWatchCache/noop-converter/check-0/v1beta2 TestWebhookConverterWithoutWatchCache/nontrivial-converter/check-0/v1beta2\ncc\nYikes, I\u2019ll sort it out.\niiuc sending an empty patch gets short-circuited and doesn't bump CR generation, even if the storage version gets changed, which means we do not re-write to etcd and go through the encoding path this would be racing and doing noop's if the first pass of didn't get the expected storage version I will send a fix to make the patch do actual mutation\nIt doesn't bump generation, but the bytes to persist in etcd would still be different if the storage version had changed, so they should persist. You can verify that by changing the storage version on a CRD yourself, do an empty patch, and see if the resourceVersion changes.\nyou're right. Generation is for non-metadata change only, and the RV changes. I queried etcd locally and the apiVersion did change for an empty patch (sidetracking: another observation is after changing the storage version (say v1 -v2; noop convertor), empty-patching v2 endpoint would bump generation, while empty-patching v1 endpoint wouldn't)\nanother theory: our cached storage strategy could be stale if the CRD informer merges multiple events together (e.g. the informer does a re-list).", "commid": "kubernetes_issue_78913", "tokennum": 546}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d82190b9d74ce6e83f0d3151b17f124972df97b0832eeca831773cc529e4e389", "query": "// GetCustomResourceListerCollectionDeleter returns the ListerCollectionDeleter of // the given crd. func (r *crdHandler) GetCustomResourceListerCollectionDeleter(crd *apiextensions.CustomResourceDefinition) (finalizer.ListerCollectionDeleter, error) { <del> info, err := r.getOrCreateServingInfoFor(crd) </del> <ins> info, err := r.getOrCreateServingInfoFor(crd.UID, crd.Name) </ins> if err != nil { return nil, err } return info.storages[info.storageVersion].CustomResource, nil } <del> func (r *crdHandler) getOrCreateServingInfoFor(crd *apiextensions.CustomResourceDefinition) (*crdInfo, error) { </del> <ins> // getOrCreateServingInfoFor gets the CRD serving info for the given CRD UID if the key exists in the storage map. // Otherwise the function fetches the up-to-date CRD using the given CRD name and creates CRD serving info. func (r *crdHandler) getOrCreateServingInfoFor(uid types.UID, name string) (*crdInfo, error) { </ins> storageMap := r.customStorage.Load().(crdStorageMap) <del> if ret, ok := storageMap[crd.UID]; ok { </del> <ins> if ret, ok := storageMap[uid]; ok { </ins> return ret, nil } r.customStorageLock.Lock() defer r.customStorageLock.Unlock() <ins> // Get the up-to-date CRD when we have the lock, to avoid racing with updateCustomResourceDefinition. // If updateCustomResourceDefinition sees an update and happens later, the storage will be deleted and // we will re-create the updated storage on demand. If updateCustomResourceDefinition happens before, // we make sure that we observe the same up-to-date CRD. crd, err := r.crdLister.Get(name) if err != nil { return nil, err } </ins> storageMap = r.customStorage.Load().(crdStorageMap) if ret, ok := storageMap[crd.UID]; ok { return ret, nil", "positive_passages": [{"docid": "doc-en-kubernetes-4d6bef5a272bfef04fa7527d92c495ee5b0e5d06d06a593b8089b98a3b84ddb9", "text": "Two scenarios: -create-update events merged into an update event: strategy with UID:a was created on demand for CRD Foo Foo was deleted and recreated strategy with UID:b was created on demand for the new Foo new Foo got updated (e.g. switching storage version) the strategy with UID:b is supposed to be deleted and , to reflect the last update. But if the CRD informer merges the delete-create-update events into , the strategy with UID:a will be deleted, but the strategy with UID:b won't. -update events merged into a create event: strategy with UID:a was created on demand for CRD Foo Foo was updated (e.g. switching storage version) the strategy with UID:a is supposed to be deleted and , to reflect the last update. But if the CRD informer merges the create-update events into , the strategy with UID:a won't be deleted (as we don't react on create events). another race found in , which could happen in a single update.\nI think I :", "commid": "kubernetes_issue_78913", "tokennum": 234}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d8358d5ecc272313f81361f5bd38ccfd10e6d1bc93dff67270e84845ef6f650f", "query": "else echo \"Detecting nodes in the cluster\" detect-node-names &> /dev/null <del> node_names=( \"${NODE_NAMES[@]}\" ) </del> <ins> if [[ -n \"${NODE_NAMES:-}\" ]]; then node_names=( \"${NODE_NAMES[@]}\" ) fi </ins> fi if [[ \"${#node_names[@]}\" == 0 ]]; then", "positive_passages": [{"docid": "doc-en-kubernetes-764cede5d9efbc9aa0896bda8776a6a1986b2e142264cb7af9fd4363856aed51", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: In https://k8s- failed due to . Afterwards crashed as follows: What you expected to happen: Graceful exit.\n/assign", "commid": "kubernetes_issue_55675", "tokennum": 45}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d875ac96ed630eb2f47da899ab78a799b5d8ad7a25df92d9af6780d887b8115f", "query": "// 3. While a volume is being unmounted, add it back to the desired state of world t.Logf(\"UnmountDevice called\") generatedVolumeName, err = dsw.AddPodToVolume( <del> podName, pod, volumeSpec, volumeSpec.Name(), \"\" /* volumeGidValue */) </del> <ins> podName, pod, volumeSpecCopy, volumeSpec.Name(), \"\" /* volumeGidValue */) </ins> dsw.MarkVolumesReportedInUse([]v1.UniqueVolumeName{generatedVolumeName}) return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-d047193f0eb4348dad25266c8f06cc7d0100df3011e6281006c74e70d78d442e", "text": "<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI --pull-kubernetes-unit : (PR with no go code changes, should not have failed any unit tests) links to appreciated links to specific failures in spyglass appreciated <!-- Please see the deflaking doc () for more guidance! --/sig storage\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assigne\n/assign\n/assign tried to fix it in", "commid": "kubernetes_issue_99815", "tokennum": 196}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d89426e4d59a52343c0a8d8553b501065ad3fccf139b70da4769bdf0e54bfd16", "query": "klog.V(4).Infof(\"GetHostsInZone %v returning: %v\", zoneFailureDomain, hosts) return hosts, nil } <ins> func (nm *NodeManager) SetNodeLister(nodeLister corelisters.NodeLister) { nm.nodeLister = nodeLister } func (nm *NodeManager) SetNodeGetter(nodeGetter coreclients.NodesGetter) { nm.nodeGetter = nodeGetter } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-b9a7a79272b4f05e986ec052f9f8348c60cffedf2d99a44ddafb98b4101b558f", "text": "I am enabling CSI migration on a vSphere cluster. A node was fully drained, all its Pods are deleted, but just before KCM detaches in-tree vSphere volume volumes from it, KCM restarts. A new KCM starts, sees attached volumes in that are not needed by any Pod on the node and calls vSphere in-tree volume plugin . The in-tree vSphere volume plugin + cloud provider marks the volume as detached right away, without reaching to vCenter API. The volume remains attached forever. I don't think it's related to CSI migration, IMO a regular node drain + KCM restart at the same time can cause the same issue. KCM logs: The in-tree cloud provider has a and from it. It apparently has not processed all nodes at the time A/D controller tries to detach the node. The in-tree vSphere volume plugin + cloud provider detaches the volume in vCenter. That's really tricky, it's very hard / impossible to reproduce on a real cluster. I had to inject errors to Detach() in-tree volume call, so they fail until KCM is restarted. Newly started KCM would detach the volume just fine (no error would be injected there), but marks the volume as detached right away. For the record (and search-ability), the CSI driver that tries to attach the volume to another node complains either: Or: cc It could be somewhat related to , however, not all cases of can be related to KCM restart. As I mentioned above, it's very hard/impossible to synchronize KCM restart with draining a node in a real cluster. <details</details<detailsvSphere 7.0.3 </details<details</details<detailsOpenShift </details<detailsCRI-O </details<details</details\n/sig storage\nTried just moving a Pod between nodes without CSI migration involved + restarting KCM when the volume is still attached to the old node. In-tree volume plugin on the new node says:\n/assign\nWhat CSI driver version and K8s version are you testing with?\nKubernetes is 1.25 and CSI driver is 2.7, still, I think it's not releated to the CSI driver, it's KCM who marks the in-tree volume as detached due to not populated node cache.", "commid": "kubernetes_issue_117091", "tokennum": 517}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d89426e4d59a52343c0a8d8553b501065ad3fccf139b70da4769bdf0e54bfd16", "query": "klog.V(4).Infof(\"GetHostsInZone %v returning: %v\", zoneFailureDomain, hosts) return hosts, nil } <ins> func (nm *NodeManager) SetNodeLister(nodeLister corelisters.NodeLister) { nm.nodeLister = nodeLister } func (nm *NodeManager) SetNodeGetter(nodeGetter coreclients.NodesGetter) { nm.nodeGetter = nodeGetter } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-27c84c169fad17ff032040ca08c7bb73c7215213dd29c5491da1ee415abb2a33", "text": "/assign\n/triage accepted\nI found an easier way how to reproduce this without extra code in KCM: a StatefulSet with 1 Pod that uses 1 PVC. the node where the Pod runs. down kube-controller-manager to zero (not really possible for me) or kill all kube-controller-manager Pods. This will cause new KCM processes to wait for leader election. In my env. this gives me ~30 seconds for the next step. Delete the Pod. A new one will be scheduled on a different node (because the current node is cordoned) + there is no KCM running at this time that would detach the volume from the old node. KCM wins its leader election, sees a volume attached to a node where it is not needed -it calls of the volume plugin. VSphere cloud provider does not have its caches populated yet (= this bug) -the volume is not detached, but returns success.\ndangling attach does not help here. The volume is still attached to the old node even after ~10 minutes. fails with and not with . I can see there is a lot of dangling attach code in the cloud provider, but I did not debug further.", "commid": "kubernetes_issue_117091", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d8b5b7b988afec59cb144f82f6ded70ab20fcd0503af6cd9b83fc8c6e56348dc", "query": "} if !proxier.lbWhiteListCIDRSet.isEmpty() || !proxier.lbWhiteListIPSet.isEmpty() { // link kube-services chain -> kube-fire-wall chain <del> args := []string{\"-m\", \"set\", \"--match-set\", proxier.lbIngressSet.Name, \"dst,dst\", \"-j\", string(KubeFireWallChain)} if _, err := proxier.iptables.EnsureRule(utiliptables.Append, utiliptables.TableNAT, kubeServicesChain, args...); err != nil { glog.Errorf(\"Failed to ensure that ipset %s chain %s jumps to %s: %v\", proxier.lbIngressSet.Name, kubeServicesChain, KubeFireWallChain, err) </del> <ins> args := []string{ \"-A\", string(kubeServicesChain), \"-m\", \"set\", \"--match-set\", proxier.lbIngressSet.Name, \"dst,dst\", \"-j\", string(KubeFireWallChain), </ins> } <ins> writeLine(proxier.natRules, args...) </ins> if !proxier.lbWhiteListCIDRSet.isEmpty() { args = append(args[:0], \"-A\", string(KubeFireWallChain),", "positive_passages": [{"docid": "doc-en-kubernetes-4b95e73f98faca5940a16ee2fccddf37ae93437213e073578ff34d76b732271f", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Service loadbalancer source range don't work in ipvs proxy mode. Which result in gci-gce-ipvs CI failed. http://k8s- How to reproduce it (as minimally and precisely as possible): In gce environment. a service with backend. service type to service util service external IP is specified. the service from pod inside and pod out of the . Environment: Kubernetes version (use ): master Cloud provider or hardware configuration: gce OS (e.g. from /etc/os-release): ubuntu Kernel (e.g. ): Install tools: cluster/kube- Others:\n/kind bug /sig network /label ipvs\n/area ipvs\nThe test seems to be flaky now. Can you take a look please?\nI don't know why, but I think this flaky have the similiar reason with other normal service-test cases, like Those flaky are pretty annoying, problem is, I have run those cases in my own environment many times, never fail... : ( But still, I'll do my best to find the reason.", "commid": "kubernetes_issue_61090", "tokennum": 264}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d8c8a47f42319517c58f8d3f0acd0568d8385e0f30dbd5592de64822a157c028", "query": "command := app.NewProxyCommand() <del> utilflag.InitFlags() </del> <ins> // TODO: once we switch everything over to Cobra commands, we can go back to calling // utilflag.InitFlags() (by removing its pflag.Parse() call). For now, we have to set the // normalize func and add the go flag set by hand. pflag.CommandLine.SetNormalizeFunc(utilflag.WordSepNormalizeFunc) pflag.CommandLine.AddGoFlagSet(goflag.CommandLine) // utilflag.InitFlags() </ins> logs.InitLogs() defer logs.FlushLogs()", "positive_passages": [{"docid": "doc-en-kubernetes-5044536d87edb25c665421bf3dc4b536a0586e8213d754dc6188da659a17c1aa", "text": "There are no sig labels on this issue. Please add a sig label. <detailsA sig label can be by either: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. See the . The in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals 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\nprobably caused by\nCould be a clash between these two?\ncc\nI still see the issue with local-cluster on the latest master: F0225 17:06:49. ] error: v1alpha1.KubeProxyConfiguration: FeatureGates: ReadMapCB: expect { or n, but found \", error found in byte of ......\nlooks like that's another issue, can you please file a new bug? with more logs? this one was about none of the hyperkube based processes starting up.\nwill do as it is also broke container kube-proxy as well. Same type of error.", "commid": "kubernetes_issue_60378", "tokennum": 274}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d8cb1f19665fd35c093ff2d6b5e92561d61ddb068316fd33d88f30cddc1835bc", "query": "public List<InetAddress> getSeeds() { List<InetAddress> list = new ArrayList<InetAddress>(); <del> String host = getEnvOrDefault(\"KUBERNETES_API_HOST\",\"https://kubernetes.default.svc.cluster.local\"); </del> <ins> //String host = \"https://kubernetes.default.svc.cluster.local\"; String proto = \"https://\"; String host = getEnvOrDefault(\"KUBERNETES_PORT_443_TCP_ADDR\", \"kubernetes.default.svc.cluster.local\"); String port = getEnvOrDefault(\"KUBERNETES_PORT_443_TCP_PORT\", \"443\"); </ins> String serviceName = getEnvOrDefault(\"CASSANDRA_SERVICE\", \"cassandra\"); String podNamespace = getEnvOrDefault(\"POD_NAMESPACE\", \"default\"); String path = String.format(\"/api/v1/namespaces/%s/endpoints/\", podNamespace);", "positive_passages": [{"docid": "doc-en-kubernetes-82cb26acad9fc9df916ca73a6711809a93da9752a7947ed537b4183fa019f2e5", "text": "What would you like to be : There is a tab in the k8s perf dashaboard for the scheduler perf benchmarks, but it is showing nothing, we should fix that: http://perf- What this dashboard should be showing is multiple runs per day of We can run it every hour, and summarize the 24 runs of each day to show 50%, 90% and 99% percentile. Why is this needed: Having daily runs of the benchmarks is important to track performance regressions. /sig scheduling /assign /priority important-soon\nRef\n/cc\nThe ci job's config is at And one of failed logs could be found at I tried to reproduce it on my local machine(because I do not have Gloud credentials, I run the task directly in the container): However it works well on my local machine. It is so weird. It will be very appreciated if anyone could help reproduce it with Gloud credentials.\ncan you try and reach out to the test-infra people? ping them on the slack channel perhaps.\nyes, I have tried to get help from , he is busy now. I'll try more.\nWhile working on reproducing this in order to file a bug against test-infra folks I think I found a solution. Will send PRs shortly. /assign\n/retitle sig-scalability-benchmarks#scheduler fails consistently due to build issues\n/sig scalability Testgrid link: https://k8s- Error logs:\nA word about the solution, the job uses the deprecated script which is not supported anymore by test-infra oncall / folks. I've rewritten the job definition to use pod utilities and it started working (will require to get merged first).\nThanks\nThanks !", "commid": "kubernetes_issue_84186", "tokennum": 383}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d903c70391408301b82a28ba5be1e2446764d2f22e53a18ccaf9c3045507ad51", "query": "\"//federation/pkg/dnsprovider/providers/aws/route53/stubs:go_default_library\", \"//federation/pkg/dnsprovider/rrstype:go_default_library\", \"//vendor/github.com/aws/aws-sdk-go/aws:go_default_library\", <ins> \"//vendor/github.com/aws/aws-sdk-go/aws/awserr:go_default_library\", </ins> \"//vendor/github.com/aws/aws-sdk-go/aws/request:go_default_library\", \"//vendor/github.com/aws/aws-sdk-go/aws/session:go_default_library\", \"//vendor/github.com/aws/aws-sdk-go/service/route53:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-2b4d325d4814fe81f2a99615b844cff823940de918e3b360e7f108b94b4fe81b", "text": "/kind bug What happened: walteraa [6:55 AM] Hi, The controller manager of the federation using Google cloud DNS is crashing, the log showed is that: the hyperkube command is that: I have created this in the Google DNS Someone knows why the DNS zone query is getting the 404 error?? :disappointed: What you expected to happen: It should have created the missing domain. How to reproduce it (as minimally and precisely as possible): As per above. Anything else we need to know?: Environment: Kubernetes version (use ): 1.7.4 Cloud provider or hardware configuration**: OpenStack (irrelevant) OS (e.g. from /etc/os-release): irrelevant Kernel (e.g. ): irrelevant Install tools: irrelevant Others: irrelevant\nThe bug is related to this: The above code assumes that the provider code returns no error but an empty list if the domain does not exist, but instead the provider returns a 404. Need to fix the provider and/or the above code.\n/sig federation\nI am unlikely to have time to work on this soon, so if anyone else wants to, go right ahead.\n/assign\nAn additional information: I have created a which is based on the credential JSON file created through instruction. After that, I have configured the Federation controller manager to mount this secret as a volume in the container and set the environment variable to the JSON file inside this volume. Before doing that, I was getting an authentication error so the google DNS provider couldn't be instantiated, and after doing the instructions that I mentioned before, this authentication error was solved but now I'm getting 404 error when Google DNS provider tries access the specified managed zone. The file that I have generated follow this structure:", "commid": "kubernetes_issue_51139", "tokennum": 376}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d92b26e3f29fd85ffd8d12f41a60d2ee1b31620042919a31389d9af0405ecbc4", "query": "Name: stats.Attributes.Metadata.Name, // The StartTime in the summary API is the container creation time. StartTime: metav1.NewTime(time.Unix(0, container.CreatedAt)), <del> // Work around heapster bug. https://github.com/kubernetes/kubernetes/issues/54962 // TODO(random-liu): Remove this after heapster is updated to newer than 1.5.0-beta.0. CPU: &statsapi.CPUStats{ UsageNanoCores: proto.Uint64(0), }, Memory: &statsapi.MemoryStats{ RSSBytes: proto.Uint64(0), }, Rootfs: &statsapi.FsStats{}, </del> <ins> CPU:       &statsapi.CPUStats{}, Memory:    &statsapi.MemoryStats{}, Rootfs:    &statsapi.FsStats{}, </ins> // UserDefinedMetrics is not supported by CRI. } if stats.Cpu != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-739981494c57aaeb7141fd974134e4440eb950badca5a937fa4552d94ec1af8a", "text": "In , we merged a work around for heapster panic We should get rid of the work around after heapster version is updated. /cc /cc\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close", "commid": "kubernetes_issue_55280", "tokennum": 224}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d960957fb25b6ed083708366c18bc6011e015213511483bf1612eb244312e04f", "query": "// Check that container has restarted ginkgo.By(\"Waiting for container to restart\") restarts := int32(0) <del> err = wait.PollImmediate(10*time.Second, 2*time.Minute, func() (bool, error) { </del> <ins> err = wait.PollImmediate(10*time.Second, framework.PodStartTimeout, func() (bool, error) { </ins> pod, err := f.ClientSet.CoreV1().Pods(f.Namespace.Name).Get(context.TODO(), pod.Name, metav1.GetOptions{}) if err != nil { return false, err", "positive_passages": [{"docid": "doc-en-kubernetes-d581fd23524a17c2e094f8c22d9237840c9557b1634d31d91db6cf64598bf32e", "text": "<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI --ci-kubernetes-e2e-ubuntu-gce [sig-storage] Subpath Container restart should verify that container can restart successfully after configmaps modified links to appreciated links to specific failures in spyglass appreciated Triage shows that this has been flaking quite frequently: It has flaked in 5 of the last 10 runs: /sig storage /priority important-soon <!-- Please see the deflaking doc () for more guidance! --\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nNoticed some more flakes on this one\nYep, looks like this is still flaking quite frequently: Going to re-ping SIG Storage.\n/assign\nTest is flaking maybe half of the time. ~This test is failing in gce-ubuntu-master-default - not sure if it's failing in any other dashboards, nor whether this is run anywhere else.~ edit: This is failing on Ubuntu only. Not sure if this is limited to master branch. Fix to the original issue was in since 1.19. This is a subpath test which a configmap a container that mounts the configmap a liveness probe and waits for the container to restart. liveness probe and waits for the container to stop restarting. The test failed at the last step - the container never stopped restarting. Timeout is 2min. The liveness probe continuously checks whether a \"probeFile\" exists in (an emptyDir), and if it doesn't exist, whether the configmap file contains the modified value. The probeFile essentially acts as a condition which guards the probe from checking the configmap file. The test fails the liveness probe by removing the probeFile without updating the configmap just yet. It then fixes the liveness probe by updating the configmap to the modified value.", "commid": "kubernetes_issue_100194", "tokennum": 522}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d960957fb25b6ed083708366c18bc6011e015213511483bf1612eb244312e04f", "query": "// Check that container has restarted ginkgo.By(\"Waiting for container to restart\") restarts := int32(0) <del> err = wait.PollImmediate(10*time.Second, 2*time.Minute, func() (bool, error) { </del> <ins> err = wait.PollImmediate(10*time.Second, framework.PodStartTimeout, func() (bool, error) { </ins> pod, err := f.ClientSet.CoreV1().Pods(f.Namespace.Name).Get(context.TODO(), pod.Name, metav1.GetOptions{}) if err != nil { return false, err", "positive_passages": [{"docid": "doc-en-kubernetes-fe4ad65b6af4a4370d93bc829526a20d829ebc4486fe6305d4213476a53bb63c", "text": "So if the container keeps restarting, the liveness probe could've been failing continuously within 2min, due to one of the following: (? not sure about this one) Command can't be executed (for example if container can't start) configmap file was never updated. Within 2min, the pod only restarted 5 times. The liveness probe's period is 2s, initial delay is 1s, and failure threshold is 1, so a restart due to liveness probe failure is triggered every 3s. The image is busybox. The command is just , so it's unlikely for the container to have crashed. There were no liveness probe unhealthy events after the test fixes the probe, and yet it continued to restart. No more events after probe is fixed.\nCould we check if the configmap value was updated for sure to rule out that scenario ? I have not tried to run an end to end test locally :) so am not sure how to debug it\nWill do! I ran the test in a GKE Ubuntu cluster running 1.19.6 and couldn't reproduce the failure. I'm now trying to run a cluster on GCE with Ubuntu nodes running k8s master, but haven't been successful after trying a number of techniques. If anyone happens to know how to do this let me know; I'll keep asking around otherwise.\nI got a repro on a GKE cluster backed by COS. After the test failed the container ends up in Running state eventually, and the configmap file outputs the expected modified value. The fix is to increase the test timeout. PR coming up.", "commid": "kubernetes_issue_100194", "tokennum": 355}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d9840f6b95fc8cc6de4cbc563a6af2483777eb1425e61637d19a25daa52ea419", "query": "local params=\"${API_SERVER_TEST_LOG_LEVEL:-\"--v=2\"} ${APISERVER_TEST_ARGS:-} ${CLOUD_CONFIG_OPT}\" params+=\" --address=127.0.0.1\" params+=\" --allow-privileged=true\" <del> params+=\" --authorization-policy-file=/etc/srv/kubernetes/abac-authz-policy.jsonl\" </del> params+=\" --cloud-provider=gce\" params+=\" --client-ca-file=/etc/srv/kubernetes/ca.crt\" params+=\" --etcd-servers=http://127.0.0.1:2379\"", "positive_passages": [{"docid": "doc-en-kubernetes-19a61d82ec14336213ef377c4e39e11807c2ce9673880ce3d82a192d5a783624", "text": "Typically, the dns and dashboard is in crash loop. Ref cc\nif you check the file, does it contain lines like ?\nPrevious comment is ref: from I'll copy that to container-linux as well.", "commid": "kubernetes_issue_39395", "tokennum": 44}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d9bf03b0ffcd343e6d5abdd60ec147cfc30066333d16956c91537bd4b86ab2fc", "query": "go_rules_dependencies() go_register_toolchains( <del> go_version = \"1.8.3\", </del> <ins> go_version = \"1.9.1\", </ins> ) docker_repositories()", "positive_passages": [{"docid": "doc-en-kubernetes-1b1e05089c93c6eb59b848626d58302483d33d2f2e5531ac5b621da204277493", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind feature This is a followup on , but for Go 1.9 We should do the same kind of testing now to possibly catch bugs in either Go or Kubernetes when doing this kind of dependency version bump. Ideally we'd have automated tests against Go tip (), but we don't have that at the moment, so we have to do it kind of manually. We should also decide which k8s version we should target. k8s v1.8 or v1.9? What Go versions have been used so far? Kubernetes v1.7.0 - go1.8.3 Kubernetes v1.6.0 - go1.7.5 Kubernetes v1.5.0 - go1.7.4 Kubernetes v1.4.0 - go1.6.3 Kubernetes v1.3.0 - go1.6.2 Kubernetes v1.2.0 - go1.4.2 Seems like the trend has been to stay on the same Go version for two releases and then bump. That'd mean we'd switch to Go1.9 in k8s v1.9 Everyone happy with that? Or is there any reason for us to go start using go1.9 in k8s v1.8? In any case, we should indeed start testing go1.9 out now... cc\nLet me know if you find any bugs\nFWIW pretty tight to code-freeze I would prefer punting out a cycle fwiw.\nI don't think we're that close to code freeze given that we have 5 (of 8) weeks left in this coding cycle But I'm happy to defer this to v1.9 if others think that. I guess the main reason for a bump would be scalability goals, but I'm not sure we have the need to expand above 5000 (and that Go would be the bottleneck in that case) for v1.8\nmade the Go benchmarks 9% faster with 15% larger binaries. I'm interested to see how that affects our numbers.\nmid-stack inlining was not included in Go 1.9. It made the compiler too slow. It's being targeted to Go 1.10 now instead, after some compiler optimization work.\nOh, thanks for the correction!", "commid": "kubernetes_issue_49484", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d9bf03b0ffcd343e6d5abdd60ec147cfc30066333d16956c91537bd4b86ab2fc", "query": "go_rules_dependencies() go_register_toolchains( <del> go_version = \"1.8.3\", </del> <ins> go_version = \"1.9.1\", </ins> ) docker_repositories()", "positive_passages": [{"docid": "doc-en-kubernetes-018b01245292fe1977b7eec8bea53846947ed737ea149d849054911d63924f58", "text": "Regardless, we need to run the scalability tests against the RC so we can report issues earlier-- the last upgrade was particularly painful because of an HTTP regression that we caught way too late.\nyeah. I filed for that now\nyeah, my recollection is that the Go releases usually occur too late in our release cadence and end up getting bumped to the next Kubernetes release. (Also we inevitably find something wrong, though testing RCs would help with that. Though I'm not sure anyone has cycles to test RCs and fix all of the issues that do come up.)\nBased on our current time frame, it looks like go1.9 support will have to slip to k8s 1.9. is open to dig into and start things testing, but there's a number of things that have to move.. I'll try to document those this time around to help with future go version bumps. So far: bazel build rules needed to be updated to support go1.9 () bazel version possibly needs to be updated? some of our custom bazel rules broke\nWhen done, we should update this:\n/priority important-soon\nUpdating the dependency is blocked pending bazel 0.6.0 - .\nCan we upgrade to 0.6.0 now? Does bazel 0.6.0 have multiarch support btw?\nWe can't update to depend on bazel 0.6.0+ until we can figure out how to support different versions of the bazelbuild and kubekins-e2e images in PR jobs in prow based on what branch is being tested. cc\nNoting that we're working on branching jobs, is testing one option here:\n[MILESTONENOTIFIER] Milestone Issue Current <details open<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts. : New functionality.", "commid": "kubernetes_issue_49484", "tokennum": 416}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d9bf03b0ffcd343e6d5abdd60ec147cfc30066333d16956c91537bd4b86ab2fc", "query": "go_rules_dependencies() go_register_toolchains( <del> go_version = \"1.8.3\", </del> <ins> go_version = \"1.9.1\", </ins> ) docker_repositories()", "positive_passages": [{"docid": "doc-en-kubernetes-69273b286facac9ab246a3deb71fa6e24d55618a503d411a1618742e8a027c28", "text": "</details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details\nI approved this for v1.9, this is something we definitely want in order to keep up with Go (and for improved performance)\nwe're starting to use the forked images now /cc this should be more feasible very soon Edit: test-infra jobs have also been using bazel 0.6 (now 0.6.1) / a recent rules_go to soak things a bit\nWe've identified a failing test as a result of the WIP PR to upgrade the codebase to go1.9: The admission webhook test fails with certificate errors under go1.9.1, but runs successfully under go1.8.3. cc: who wanted to be alerted to potential bugs\n- please see for a possible fix", "commid": "kubernetes_issue_49484", "tokennum": 212}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d9d90dd0b41d623d0c3da08848cc5033a6ca47f3f77cce5be71d3d54a5d33353", "query": "metadataVMName: \"node2\", expected:       false, }, <del> { nodeName:       \"vmss000001\", metadataVMName: \"vmss_1\", expected:       true, }, { nodeName:       \"vmss_2\", metadataVMName: \"vmss000000\", expected:       false, }, { nodeName:       \"vmss123456\", metadataVMName: \"vmss_$123\", expected:       false, expectedErrMsg: fmt.Errorf(\"failed to parse VMSS instanceID %q: strconv.ParseInt: parsing %q: invalid syntax\", \"$123\", \"$123\"), }, </del> } for _, test := range testcases {", "positive_passages": [{"docid": "doc-en-kubernetes-93c0a615d6725c12b66abb2dead01e17ca700d451119b1467d3edce68f73a013", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: If computer name prefix does not match VMSS name, then Azure cloud provider will use VMSS API instead of using metadata service data. This leads to throttling, because every affected kubelet is making API requests. What you expected to happen: Azure cloud provider should use metadata service data instead of calling VMSS API when instance is current. How to reproduce it (as minimally and precisely as possible): Set computer name prefix of the VMSS to something different than default. You should observe Azure provider making requests to the VMSS API rather than using metadata service, which leads to throttling if you have multiple kubelets with this bug. Anything else we need to know?: This is bug was introduced by - returns false even if instance is current, because it expects node name to match VMSS name + instance id, however node name is derived from the computer-name-prefix which can be different than VMSS name. Node name should be matched against , not against . Environment: Kubernetes version (use ): 1.18.x and higher Cloud provider or hardware configuration: azure /sig cloud-provider\n/sig cloud-provider\n/area provider/azure\nCC\n/remove-sig cloud-provider /sig cloud-provider (trying to remove the label)\n/sig cloud-provider\nThanks for the reporting. Unfortunately, computer name prefix is not included in IMDS, so it can't be used without VMSS API for constructing the NodeName. Would check what could we do to workaround the issue.\nCan you memorize the computer name prefix in the first request to the Azure API and then use it for the isCurrentInstance check?\nopened to fix the issue. Would you like to have a look?\nI can confirm that your change should fix the problem I reported. Do you know if your fix will be to 1.18.x?\nis working on the cherry pick\nThank you for quick fix!", "commid": "kubernetes_issue_92733", "tokennum": 464}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d9e176c98a14210958140c5326610f4506dd57772db50c629a21c5aaad44432b", "query": "} redacted := string(redactedBytes) <ins> dataOmitted := string(dataOmittedBytes) </ins> if len(mutatingConfig.Clusters) != 2 { t.Errorf(\"unexpected clusters: %v\", mutatingConfig.Clusters) } if !reflect.DeepEqual(startingConfig.Clusters[unchangingCluster], mutatingConfig.Clusters[unchangingCluster]) { t.Errorf(\"expected %v, got %v\", startingConfig.Clusters[unchangingCluster], mutatingConfig.Clusters[unchangingCluster]) } <del> if string(mutatingConfig.Clusters[changingCluster].CertificateAuthorityData) != redacted { t.Errorf(\"expected %v, got %v\", redacted, string(mutatingConfig.Clusters[changingCluster].CertificateAuthorityData)) </del> <ins> if string(mutatingConfig.Clusters[changingCluster].CertificateAuthorityData) != dataOmitted { t.Errorf(\"expected %v, got %v\", dataOmitted, string(mutatingConfig.Clusters[changingCluster].CertificateAuthorityData)) </ins> } if len(mutatingConfig.AuthInfos) != 2 {", "positive_passages": [{"docid": "doc-en-kubernetes-397ec6d3ebe6b2748109f44339689e34d7c15d3a74b9e08d5b86ed108288f149", "text": "Is this a BUG REPORT or FEATURE REQUEST?: What happened: shows: The use of \"REDACTED\" for a CA here is misleading, since it's a public certificate that is not a secret. What you expected to happen: I expected to see the full CA in pem format (like when you cat ) or something like \"SUPPRESSED\" or \"TRUNCATED\" How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Nope Environment: Kubernetes version (use ):Cloud provider or hardware configuration:OS (e.g. from /etc/os-release):Kernel (e.g. ):\n(for thoughts)\nReiterating the mentions to trigger a notification: <detailsIn response to : (for thoughts) 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\nuse you can see the complete certificate authority data\nHey Thank you - I have tracking that . The point of this issue is that at best it's a bad UX; at worst it's a miseducation on pki. \"REDACTED\" isn't the right word here\nIf there are multiple clusters displaying certificates, the configuration will be too long, so this switch is turned off by default. But we can add an example to help use. thanks\nHey I don't personally view truncation the responsibility of the CLI... users can pipe things to a pager if they really care. That being said, I'm not concerned about the length. The issue is purely about the word choice of \"REDACTED\". The term means: The use of the term \"REDACTED\" in the output implies that a CA public key is remove for security when (as you've pointed out) it is removed for truncation. Truncation and redaction are fundamentally different things, and k8s is misusing the word redacted for this use case.\nNot quite a bug, but I think you're right a better term could be used there as it is a public key, not a private key. /remove-kind bug\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close.", "commid": "kubernetes_issue_61573", "tokennum": 495}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d9e176c98a14210958140c5326610f4506dd57772db50c629a21c5aaad44432b", "query": "} redacted := string(redactedBytes) <ins> dataOmitted := string(dataOmittedBytes) </ins> if len(mutatingConfig.Clusters) != 2 { t.Errorf(\"unexpected clusters: %v\", mutatingConfig.Clusters) } if !reflect.DeepEqual(startingConfig.Clusters[unchangingCluster], mutatingConfig.Clusters[unchangingCluster]) { t.Errorf(\"expected %v, got %v\", startingConfig.Clusters[unchangingCluster], mutatingConfig.Clusters[unchangingCluster]) } <del> if string(mutatingConfig.Clusters[changingCluster].CertificateAuthorityData) != redacted { t.Errorf(\"expected %v, got %v\", redacted, string(mutatingConfig.Clusters[changingCluster].CertificateAuthorityData)) </del> <ins> if string(mutatingConfig.Clusters[changingCluster].CertificateAuthorityData) != dataOmitted { t.Errorf(\"expected %v, got %v\", dataOmitted, string(mutatingConfig.Clusters[changingCluster].CertificateAuthorityData)) </ins> } if len(mutatingConfig.AuthInfos) != 2 {", "positive_passages": [{"docid": "doc-en-kubernetes-be8602378a7d778cfbc76bff14bb786f501b2719d8c237c227cdd36827d468ae", "text": "If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale I'm not sure what I need to do here. This was marked as a feature. Do you need something more from me?\nWe are waiting for someone to fix this.\n/remove-good-first-issue I don't think this fits our definition of a :\nSo I have to keep replying to the comment bot every 30 days so it doesn't get auto-closed? That feels... odd\nthanks for the education :) unfortunately other issues are higher priority and no one has stepped up to fix this. The autocloser is a form of bug bankruptcy that keeps our issue load in check. The contribex special interest group is definitely open to feedback on the bot.\nThe biggest hurdle in this is that Kubernetes is using some base64 trickery to display the string (basically setting the certificate data to the decoded bytes from ). We can change this to or but not (it has to be a valid base64 encoded string). I tried exploring multiple options for the text, but I couldn't find a suitable one. Given that we already print the user tokens and other credentials this is a bit weird. Should we redact those too? Is it okay if we print the CA certificate instead of truncating it?\nI can't help but laugh at: I'm not wed to any particular name. I also have no problem displaying the entire certificate. The crux of the issue is that a CA public key is not secret or sensitive. It's a public key\nI agree. The issue is with the constraints imposed by how this is implemented currently. I tried to come up with a suitable string (given the constraint) and couldn't find anything acceptable... The only suitable option that worked for me is . I personally prefer to print the CA certificate since we are already printing user tokens and client certs that are actual secrets.\nI agree. Who do we need to get in agreement that printing the full CA is the best path forward?\nthe data is not omitted for security purposes, but to make the output more readable. see REDACTED is misleading... it should probably be \"elided\" or \"...\"\nyou can run to view full content\nthat's the crux of this issue - REDACTED is misleading.", "commid": "kubernetes_issue_61573", "tokennum": 520}], "negative_passages": []}
{"query_id": "q-en-kubernetes-d9e176c98a14210958140c5326610f4506dd57772db50c629a21c5aaad44432b", "query": "} redacted := string(redactedBytes) <ins> dataOmitted := string(dataOmittedBytes) </ins> if len(mutatingConfig.Clusters) != 2 { t.Errorf(\"unexpected clusters: %v\", mutatingConfig.Clusters) } if !reflect.DeepEqual(startingConfig.Clusters[unchangingCluster], mutatingConfig.Clusters[unchangingCluster]) { t.Errorf(\"expected %v, got %v\", startingConfig.Clusters[unchangingCluster], mutatingConfig.Clusters[unchangingCluster]) } <del> if string(mutatingConfig.Clusters[changingCluster].CertificateAuthorityData) != redacted { t.Errorf(\"expected %v, got %v\", redacted, string(mutatingConfig.Clusters[changingCluster].CertificateAuthorityData)) </del> <ins> if string(mutatingConfig.Clusters[changingCluster].CertificateAuthorityData) != dataOmitted { t.Errorf(\"expected %v, got %v\", dataOmitted, string(mutatingConfig.Clusters[changingCluster].CertificateAuthorityData)) </ins> } if len(mutatingConfig.AuthInfos) != 2 {", "positive_passages": [{"docid": "doc-en-kubernetes-0c20cfda2a4143b97ca34085e4ba4933a2256b4cc12b09ed01e77387d3b1e642", "text": "However, pointed out that other \"long\" fields are still completely printed in plain text such as client certs, so I think we need to revisit the \"readability\" argument. What do you think?\nthey are not... client cert/key are elided in the same way for the same reason: something like \"++data+omitted++\" could be better If the intent of config view without --raw specified is to be readable (which it currently is), printing many extremely long fields isn't great\nHmm what about: I'm pretty sure that would give us a valid b64 string (8+12=20%4=0) and it would subtly hint that the data isn't a secret.\nOnly valid characters are . And adding a prefix from the certificate only complicates things. is a suitable usable option. I'll submit a PR to continue the discussion there.", "commid": "kubernetes_issue_61573", "tokennum": 195}], "negative_passages": []}
{"query_id": "q-en-kubernetes-da1e41092a700a5cf24d55f5f1e92f229b49ab40bd2e6696389f99d34df9b107", "query": "return fmt.Sprintf(\"%s/%d/%s\", ds.UID, ds.Status.ObservedGeneration, nodeName) } <del> // getPodsWithoutNode returns list of pods assigned to not existing nodes. func getPodsWithoutNode(runningNodesList []*v1.Node, nodeToDaemonPods map[string][]*v1.Pod) []string { </del> <ins> // getUnscheduledPodsWithoutNode returns list of unscheduled pods assigned to not existing nodes. // Returned pods can't be deleted by PodGCController so they should be deleted by DaemonSetController. func getUnscheduledPodsWithoutNode(runningNodesList []*v1.Node, nodeToDaemonPods map[string][]*v1.Pod) []string { </ins> var results []string isNodeRunning := make(map[string]bool) for _, node := range runningNodesList {", "positive_passages": [{"docid": "doc-en-kubernetes-2bd3e1d9e94a5358a6c2d5b4c6b5864c879bb8cabae55e6531ce8f2da7e1ce93", "text": "What happened: Occasionally we get a Daemonset stuck with less Current replicas than Desired, causing a Daemonset sync tends to fix it, e.g (add a new node). This happens to all our Daemonsets. I'm using fluentd as an example. There are no Daemonsets pods in pending nor are there any errors when describing the Daemonset What you expected to happen: The Daemonset Pod to be scheduled How to reproduce it (as minimally and precisely as possible): Reproducing this state is very tricky, I've had the most success by terminating nodes in our ASG causing a new one to come up. However I think I've identified why this is happening. The issue appears to be related to daemonset Pod deletion, a Pod gets deleted causing to trigger, this lowers the expectations by as expected. The delete pod event then triggers a sync of the daemonset, in which it finds which involves fetching pods from the informer cache This is somehow returning the deleted pod. You can see in the logs here thinks that it needs to delete the pod that was deleted. It is also setting the expectation back to after the delete pod event previously lowered it by 1. At this point you're stuck as the function can't get past this line As the expectation can not be satisfied as syncNodes set it back to and there's nothing it to get it back to . So I believe this is what's causing us to get less replicas than expected, the function is stuck due to the expectation so it can't perform a full sync to schedule the new pods. There's also not much to trigger a new sync once the expectation has expired until a new node comes up or one goes down. Environment: Kubernetes version (use ):Cloud provider or hardware configuration: AWS OS (e.g: ):Kernel (e.g. ):\n/sig apps\nI investigated this as much as I could without getting some external input, it feels like it's some kind of race condition in the informer cache. If anyone has ideas of if places to dig deeper that would be handy.\nReiterating the mentions to trigger a notification: <detailsIn response to : I investigated this as much as I could without getting some external input, it feels like it's some kind of race condition in the informer cache. If anyone has ideas of if places to dig deeper that would be handy.", "commid": "kubernetes_issue_75836", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-da1e41092a700a5cf24d55f5f1e92f229b49ab40bd2e6696389f99d34df9b107", "query": "return fmt.Sprintf(\"%s/%d/%s\", ds.UID, ds.Status.ObservedGeneration, nodeName) } <del> // getPodsWithoutNode returns list of pods assigned to not existing nodes. func getPodsWithoutNode(runningNodesList []*v1.Node, nodeToDaemonPods map[string][]*v1.Pod) []string { </del> <ins> // getUnscheduledPodsWithoutNode returns list of unscheduled pods assigned to not existing nodes. // Returned pods can't be deleted by PodGCController so they should be deleted by DaemonSetController. func getUnscheduledPodsWithoutNode(runningNodesList []*v1.Node, nodeToDaemonPods map[string][]*v1.Pod) []string { </ins> var results []string isNodeRunning := make(map[string]bool) for _, node := range runningNodesList {", "positive_passages": [{"docid": "doc-en-kubernetes-cf3a9a922f150fcd06b37026fcb1a4fe5fd4fd3de4493928a0abbcee85e2e3a6", "text": "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\nThis problem is definitely related to node termination, it's trying to delete the already deleted pod from the node that's been terminated. The problem seems to go away if is set, I think although this kind of race condition may have always been possible, it's being frequently caused via Which is finding the non-existent pod in the pod cache and seeing that it is assigned to a non-running node, resulting in a request to delete the non-existent pod. cc\nReiterating the mentions to trigger a notification: <detailsIn response to : This problem is definitely related to node termination, it's trying to delete the already deleted pod from the node that's been terminated. 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\n/assign could you please take a look at this? It seems that it is related to the code you in .\nThanks for reporting the bug. Bug was introduced in which deleting pods without nodes. There is race condition between removing pod from cache and listing pods for DaemonSet. Bug occurs during following scenario: is deleted. for node is deleted by PodGCController. handler is executed by informer () set is to queue by delete handler () is processed and pods are taken from cache before deleted pod is removed. for deleted pod is not found so we add deleted pod to podsToDelete list (). are set to del:1() succeeds as pod is not found(). are never met so we need to wait till expectations expire. As fix I will send a change to so only pods that can't be deleted by PodGCController are deleted by DaemonSet controller.", "commid": "kubernetes_issue_75836", "tokennum": 399}], "negative_passages": []}
{"query_id": "q-en-kubernetes-da270a0533568f3a1745f6706e91f32c9cbd190f4f788acceddc897c21cf5b8b", "query": "\"k8s.io/kubernetes/pkg/api/latest\" \"k8s.io/kubernetes/pkg/api/unversioned\" client \"k8s.io/kubernetes/pkg/client/unversioned\" <ins> \"k8s.io/kubernetes/pkg/labels\" </ins> \"k8s.io/kubernetes/pkg/util\" \"k8s.io/kubernetes/pkg/util/wait\" )", "positive_passages": [{"docid": "doc-en-kubernetes-57d83ef880aa3c3668480a2a99a63d94dfed9404bcfb6c9db559f5ee8b331861", "text": "More detail can be seen in e2e test\ncc\n, Marek Grabowski wrote:\nyou are running an older version of the test. can you get the latest and try again ? This test had not failed at all yesterday in our automated test runs yesterday. Closing issue for now.\nThis failure depends on if the pod is really deleted and kube-proxy (the test container on) catch that the endpoint is deleted in 5s . After sending \"delete pod\" request for 5s, if the pod was still there and kube-proxy still contains this endpoints(this may happen under pressure), hit test can still detect 5 endpoints. At least we should ensure the pod was deleted. Anyway, I think will be helpful to this test. What do you think?\nIt doesn't matter if the pod is actually deleted or not. We just care that kube-proxy thinks that it should not be part of the service endpoint. Having said that, it still doesn't hurt to do the check that you are doing. I will assign your PR to myself and review it. In the meantime, can you rebase your PR ?\nThanks for your review. The PR is up to date.\nFailed twice today in kubernetes-e2e-gce-parallel\nOne more today. The error message is not very helpful.\n18:28:37 STEP: dialing(http) endpointPodIP:endpointHttpPort from node1 18:28:37 STEP: Dialing from node. command:for i in ' wc -l This is the point where the test fails. Am looking into it. We need to have more tries, we just do seq (1 1), instead of seq (6 6). this is causing flakiness.\nFixed by PR", "commid": "kubernetes_issue_14342", "tokennum": 372}], "negative_passages": []}
{"query_id": "q-en-kubernetes-da2970a6da449e89cadc228642b347181e61a20c034d0537dc8e1f52fc895643", "query": "Container Runtime Conformance Test container runtime conformance blackbox test when starting a container that exits should report termination message if TerminationMessagePath is set,timothysc,1 DNS horizontal autoscaling kube-dns-autoscaler should scale kube-dns pods in both nonfaulty and faulty scenarios,MrHohn,0 DNS horizontal autoscaling kube-dns-autoscaler should scale kube-dns pods when cluster size changed,MrHohn,0 <ins> ContainerLogPath Pod with a container printed log to stdout should print log to correct log path,resouer,0 </ins> DNS should provide DNS for ExternalName services,rmmh,1 DNS should provide DNS for pods for Hostname and Subdomain Annotation,mtaufen,1 DNS should provide DNS for services,roberthbailey,1", "positive_passages": [{"docid": "doc-en-kubernetes-0ad427ca9c00c618017f4be9fb19a1df6f4ab39ddc68f128fc109eb4d0409cbf", "text": "Cluster logging assumes kubelet stores container log at a specific directory with specific name. Currently the path is: After the CRI work, the path will be: However, we don't have test coverage for this. We don't even know whether the log files are there or not. We should add a node e2e test for this, basically: 1) Create a container which prints logs 2) Check whether the expected log file is created. 3) Check whether the logs are collected in the file as expected. And it would be better to launch a pod to do the check instead of accessing local file system directly, which makes containerizing easier. /cc because you are collecting missing test. /cc\nI will try to add a node-e2e test there\nI think it's ok to add this for CRI. But there maybe problems on today's interface for rkt. If I'm not wrong, rkt does't store logs at same location with docker. cc/ Is this true?\nThanks! :)\nAfter gets merged, we need to update the test to verify the cri log path.", "commid": "kubernetes_issue_34661", "tokennum": 234}], "negative_passages": []}
{"query_id": "q-en-kubernetes-da2b0a9dc02465e7860624cb8bde5e6bc931c37cd9a2a8890c87692399c35d13", "query": "sed -i'' -e \"s@{{kubemark_image_registry}}@${KUBEMARK_IMAGE_REGISTRY}@g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" sed -i'' -e \"s@{{kubemark_image_tag}}@${KUBEMARK_IMAGE_TAG}@g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" sed -i'' -e \"s@{{master_ip}}@${MASTER_IP}@g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" <del> sed -i'' -e \"s@{{hollow_kubelet_params}}@${HOLLOW_KUBELET_TEST_ARGS}@g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" sed -i'' -e \"s@{{hollow_proxy_params}}@${HOLLOW_PROXY_TEST_ARGS}@g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" </del> <ins> sed -i'' -e \"s@{{hollow_kubelet_params}}@${hollow_kubelet_params}@g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" sed -i'' -e \"s@{{hollow_proxy_params}}@${hollow_proxy_params}@g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" </ins> sed -i'' -e \"s@{{kubemark_mig_config}}@${KUBEMARK_MIG_CONFIG:-}@g\" \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" \"${KUBECTL}\" create -f \"${RESOURCE_DIRECTORY}/hollow-node.yaml\" --namespace=\"kubemark\"", "positive_passages": [{"docid": "doc-en-kubernetes-d99484417892d904a3f5edbb73fa06d2de654c460b279ad73f511e028afa6a6f", "text": "There are CVEs happening in different images - we already migrated Kubmeark from busybox in , but we should go one step further and migrate the base image to distroless. There are some things that would need to be changed mentioned here: /sig scalability\nCan I work on this? /assign\n/remove-help\n- sure that would be great.\nHi based on the discussion in , the kubemark image has dependency on and maybe more other utilities. So it seems impossible to migrate the base image to distroless? Or do we need something like debian-hyperkube-base?\nThe mount one we may get rid of - basically we should be able to switch to FakeMounter:", "commid": "kubernetes_issue_84284", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-da53197942f8e1d3aa406e4ec8e05b4e57562dedfc18b94f1c6fee7b996faa74", "query": "Containers: []v1.Container{ { Name:  \"nfs-provisioner\", <del> Image: \"quay.io/kubernetes_incubator/nfs-provisioner:v2.2.0-k8s1.12\", </del> <ins> Image: \"quay.io/kubernetes_incubator/nfs-provisioner:v2.2.2\", </ins> SecurityContext: &v1.SecurityContext{ Capabilities: &v1.Capabilities{ Add: []v1.Capability{\"DAC_READ_SEARCH\"},", "positive_passages": [{"docid": "doc-en-kubernetes-a8f763c740d3fb11e6b67f36722750f0a39e674fe923e77cebdc2dd4df02a0e7", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: ci-kubernetes-e2e-gci-gce-alpha-enabled-default Which test(s) are failing: CSI hostpath-v0 tests Since when has it been failing: 8/8 Testgrid link: https://k8s- Reason for failure: Anything else we need to know: We need to update client-go to get the fix for selfLink, build new nfs provisioner images, and update them in the e2e test. The fix for client-go is being cherry-picked to 1.15 if you want to use a tagged release:\n/assign\n/assign\nThis implies rebase to 1.15.x in external-storage, which seem to be challenging (at least to me :-) )\n14 cherry pick also in progress:\nOK, I guess this line in the lib is the culprit: So I need to update lib then external-storage to pull it in\nI don't think the lib itself needs to be updated. Only updating go-client to get the fix to is needed.\nRight, lib doesn't dictate what version of client-go to use. Will wait for client-go release/commit\n- thanks a lot for bumping the dependency. Did you have a chance to build the new container with it so that we could update it here:\nyeah, opened . (Not sure how to trigger test, or we can just merge and see.)\nYou can manually create a PVC on an alpha cluster to test.", "commid": "kubernetes_issue_81403", "tokennum": 350}], "negative_passages": []}
{"query_id": "q-en-kubernetes-da85d92549f64a4b7db1e845ff889721f57ba8731336d77e62922ca973e26712", "query": "} } <ins> func TestDeletingPodForRollingUpdatePartition(t *testing.T) { _, ctx := ktesting.NewTestContext(t) closeFn, rm, informers, c := scSetup(ctx, t) defer closeFn() ns := framework.CreateNamespaceOrDie(c, \"test-deleting-pod-for-rolling-update-partition\", t) defer framework.DeleteNamespaceOrDie(c, ns, t) cancel := runControllerAndInformers(rm, informers) defer cancel() labelMap := labelMap() sts := newSTS(\"sts\", ns.Name, 2) sts.Spec.UpdateStrategy = appsv1.StatefulSetUpdateStrategy{ Type: appsv1.RollingUpdateStatefulSetStrategyType, RollingUpdate: func() *appsv1.RollingUpdateStatefulSetStrategy { return &appsv1.RollingUpdateStatefulSetStrategy{ Partition: ptr.To[int32](1), } }(), } stss, _ := createSTSsPods(t, c, []*appsv1.StatefulSet{sts}, []*v1.Pod{}) sts = stss[0] waitSTSStable(t, c, sts) // Verify STS creates 2 pods podClient := c.CoreV1().Pods(ns.Name) pods := getPods(t, podClient, labelMap) if len(pods.Items) != 2 { t.Fatalf(\"len(pods) = %d, want 2\", len(pods.Items)) } // Setting all pods in Running, Ready, and Available setPodsReadyCondition(t, c, &v1.PodList{Items: pods.Items}, v1.ConditionTrue, time.Now()) // 1. Roll out a new image. oldImage := sts.Spec.Template.Spec.Containers[0].Image newImage := \"new-image\" if oldImage == newImage { t.Fatalf(\"bad test setup, statefulSet %s roll out with the same image\", sts.Name) } // Set finalizers for the pod-0 to trigger pod recreation failure while the status UpdateRevision is bumped pod0 := &pods.Items[0] updatePod(t, podClient, pod0.Name, func(pod *v1.Pod) { pod.Finalizers = []string{\"fake.example.com/blockDeletion\"} }) stsClient := c.AppsV1().StatefulSets(ns.Name) _ = updateSTS(t, stsClient, sts.Name, func(sts *appsv1.StatefulSet) { sts.Spec.Template.Spec.Containers[0].Image = newImage }) // Await for the pod-1 to be recreated, while pod-0 remains running if err := wait.PollUntilContextTimeout(ctx, pollInterval, pollTimeout, false, func(ctx context.Context) (bool, error) { ss, err := stsClient.Get(ctx, sts.Name, metav1.GetOptions{}) if err != nil { return false, err } pods := getPods(t, podClient, labelMap) recreatedPods := v1.PodList{} for _, pod := range pods.Items { if pod.Status.Phase == v1.PodPending { recreatedPods.Items = append(recreatedPods.Items, pod) } } setPodsReadyCondition(t, c, &v1.PodList{Items: recreatedPods.Items}, v1.ConditionTrue, time.Now()) return ss.Status.UpdatedReplicas == *ss.Spec.Replicas-*sts.Spec.UpdateStrategy.RollingUpdate.Partition && ss.Status.Replicas == *ss.Spec.Replicas && ss.Status.ReadyReplicas == *ss.Spec.Replicas, nil }); err != nil { t.Fatalf(\"failed to await for pod-1 to be recreated by sts %s: %v\", sts.Name, err) } // Mark pod-0 as terminal and not ready updatePodStatus(t, podClient, pod0.Name, func(pod *v1.Pod) { pod.Status.Phase = v1.PodFailed }) // Make sure pod-0 gets deletion timestamp so that it is recreated if err := c.CoreV1().Pods(ns.Name).Delete(context.TODO(), pod0.Name, metav1.DeleteOptions{}); err != nil { t.Fatalf(\"error deleting pod %s: %v\", pod0.Name, err) } // Await for pod-0 to be not ready if err := wait.PollUntilContextTimeout(ctx, pollInterval, pollTimeout, false, func(ctx context.Context) (bool, error) { ss, err := stsClient.Get(ctx, sts.Name, metav1.GetOptions{}) if err != nil { return false, err } return ss.Status.ReadyReplicas == *ss.Spec.Replicas-1, nil }); err != nil { t.Fatalf(\"failed to await for pod-0 to be not counted as ready in status of sts %s: %v\", sts.Name, err) } // Remove the finalizer to allow recreation updatePod(t, podClient, pod0.Name, func(pod *v1.Pod) { pod.Finalizers = []string{} }) // Await for pod-0 to be recreated and make it running if err := wait.PollUntilContextTimeout(ctx, pollInterval, pollTimeout, false, func(ctx context.Context) (bool, error) { pods := getPods(t, podClient, labelMap) recreatedPods := v1.PodList{} for _, pod := range pods.Items { if pod.Status.Phase == v1.PodPending { recreatedPods.Items = append(recreatedPods.Items, pod) } } setPodsReadyCondition(t, c, &v1.PodList{Items: recreatedPods.Items}, v1.ConditionTrue, time.Now().Add(-120*time.Minute)) return len(recreatedPods.Items) > 0, nil }); err != nil { t.Fatalf(\"failed to await for pod-0 to be recreated by sts %s: %v\", sts.Name, err) } // Await for all stateful set status to record all replicas as ready if err := wait.PollUntilContextTimeout(ctx, pollInterval, pollTimeout, false, func(ctx context.Context) (bool, error) { ss, err := stsClient.Get(ctx, sts.Name, metav1.GetOptions{}) if err != nil { return false, err } return ss.Status.ReadyReplicas == *ss.Spec.Replicas, nil }); err != nil { t.Fatalf(\"failed to verify .Spec.Template.Spec.Containers[0].Image is updated for sts %s: %v\", sts.Name, err) } // Verify 3 pods exist pods = getPods(t, podClient, labelMap) if len(pods.Items) != int(*sts.Spec.Replicas) { t.Fatalf(\"Unexpected number of pods\") } // Verify pod images for i := range pods.Items { if i < int(*sts.Spec.UpdateStrategy.RollingUpdate.Partition) { if pods.Items[i].Spec.Containers[0].Image != oldImage { t.Fatalf(\"Pod %s has image %s not equal to old image %s\", pods.Items[i].Name, pods.Items[i].Spec.Containers[0].Image, oldImage) } } else { if pods.Items[i].Spec.Containers[0].Image != newImage { t.Fatalf(\"Pod %s has image %s not equal to new image %s\", pods.Items[i].Name, pods.Items[i].Spec.Containers[0].Image, newImage) } } } } </ins> func TestStatefulSetStartOrdinal(t *testing.T) { tests := []struct { ordinals         *appsv1.StatefulSetOrdinals", "positive_passages": [{"docid": "doc-en-kubernetes-cbff279a5a2209254c6527f41e3183737e33b6607a7e6fb4945b04f53611a022", "text": "My application is clustered and I have 2 pods running. I am using a rolling upgrade strategy and my partitioning number is 1. First I need to upgrade the pod with the ordinal number 1 so I triggered that upgrade with partitioning number 1 and my upgrade gets completed. After this, my pod having the ordinal number 0 gets restarted and it's automatically upgraded to a new image. This is not an expected behavior because still, my partition number is 1 and pod-0 should come up with an older image only. I am facing this issue for the v1.27 cluster. Prior to this, it was working fine. pod-0 should not upgrade to new image until I upgrade the partition number to 0.a Do helm install and upgrade pod-1 only keeping partition number to 1. No response <detailsconsole $ cat /etc/os-release $ uname -a C:wmic os get Caption, Version, BuildNumber, OSArchitecture </details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig/api-machinery\n/sig apps /sig storage\nHi, Can someone suggest here? As this is introduced in my setup after the v1.27 upgrade? Is there any change in partition logic?\nThis can be reproduced by using the said STS. 1 - Deploy STS using attached that has a replica count is 2 and updatingstrategy.rolling.partition as 1. 2 - Do edit STS and update the image to 1.15. This will upgrade, pod-1 with image 1.15. 3 - Next delete the pod pod-0 and check that POD-0 came up with a new image which is not the expected behavior. POD 0 should not be updated to a new image until the partition is changed to 0. We have noticed this behavior change in v1.27.", "commid": "kubernetes_issue_119685", "tokennum": 476}], "negative_passages": []}
{"query_id": "q-en-kubernetes-da85d92549f64a4b7db1e845ff889721f57ba8731336d77e62922ca973e26712", "query": "} } <ins> func TestDeletingPodForRollingUpdatePartition(t *testing.T) { _, ctx := ktesting.NewTestContext(t) closeFn, rm, informers, c := scSetup(ctx, t) defer closeFn() ns := framework.CreateNamespaceOrDie(c, \"test-deleting-pod-for-rolling-update-partition\", t) defer framework.DeleteNamespaceOrDie(c, ns, t) cancel := runControllerAndInformers(rm, informers) defer cancel() labelMap := labelMap() sts := newSTS(\"sts\", ns.Name, 2) sts.Spec.UpdateStrategy = appsv1.StatefulSetUpdateStrategy{ Type: appsv1.RollingUpdateStatefulSetStrategyType, RollingUpdate: func() *appsv1.RollingUpdateStatefulSetStrategy { return &appsv1.RollingUpdateStatefulSetStrategy{ Partition: ptr.To[int32](1), } }(), } stss, _ := createSTSsPods(t, c, []*appsv1.StatefulSet{sts}, []*v1.Pod{}) sts = stss[0] waitSTSStable(t, c, sts) // Verify STS creates 2 pods podClient := c.CoreV1().Pods(ns.Name) pods := getPods(t, podClient, labelMap) if len(pods.Items) != 2 { t.Fatalf(\"len(pods) = %d, want 2\", len(pods.Items)) } // Setting all pods in Running, Ready, and Available setPodsReadyCondition(t, c, &v1.PodList{Items: pods.Items}, v1.ConditionTrue, time.Now()) // 1. Roll out a new image. oldImage := sts.Spec.Template.Spec.Containers[0].Image newImage := \"new-image\" if oldImage == newImage { t.Fatalf(\"bad test setup, statefulSet %s roll out with the same image\", sts.Name) } // Set finalizers for the pod-0 to trigger pod recreation failure while the status UpdateRevision is bumped pod0 := &pods.Items[0] updatePod(t, podClient, pod0.Name, func(pod *v1.Pod) { pod.Finalizers = []string{\"fake.example.com/blockDeletion\"} }) stsClient := c.AppsV1().StatefulSets(ns.Name) _ = updateSTS(t, stsClient, sts.Name, func(sts *appsv1.StatefulSet) { sts.Spec.Template.Spec.Containers[0].Image = newImage }) // Await for the pod-1 to be recreated, while pod-0 remains running if err := wait.PollUntilContextTimeout(ctx, pollInterval, pollTimeout, false, func(ctx context.Context) (bool, error) { ss, err := stsClient.Get(ctx, sts.Name, metav1.GetOptions{}) if err != nil { return false, err } pods := getPods(t, podClient, labelMap) recreatedPods := v1.PodList{} for _, pod := range pods.Items { if pod.Status.Phase == v1.PodPending { recreatedPods.Items = append(recreatedPods.Items, pod) } } setPodsReadyCondition(t, c, &v1.PodList{Items: recreatedPods.Items}, v1.ConditionTrue, time.Now()) return ss.Status.UpdatedReplicas == *ss.Spec.Replicas-*sts.Spec.UpdateStrategy.RollingUpdate.Partition && ss.Status.Replicas == *ss.Spec.Replicas && ss.Status.ReadyReplicas == *ss.Spec.Replicas, nil }); err != nil { t.Fatalf(\"failed to await for pod-1 to be recreated by sts %s: %v\", sts.Name, err) } // Mark pod-0 as terminal and not ready updatePodStatus(t, podClient, pod0.Name, func(pod *v1.Pod) { pod.Status.Phase = v1.PodFailed }) // Make sure pod-0 gets deletion timestamp so that it is recreated if err := c.CoreV1().Pods(ns.Name).Delete(context.TODO(), pod0.Name, metav1.DeleteOptions{}); err != nil { t.Fatalf(\"error deleting pod %s: %v\", pod0.Name, err) } // Await for pod-0 to be not ready if err := wait.PollUntilContextTimeout(ctx, pollInterval, pollTimeout, false, func(ctx context.Context) (bool, error) { ss, err := stsClient.Get(ctx, sts.Name, metav1.GetOptions{}) if err != nil { return false, err } return ss.Status.ReadyReplicas == *ss.Spec.Replicas-1, nil }); err != nil { t.Fatalf(\"failed to await for pod-0 to be not counted as ready in status of sts %s: %v\", sts.Name, err) } // Remove the finalizer to allow recreation updatePod(t, podClient, pod0.Name, func(pod *v1.Pod) { pod.Finalizers = []string{} }) // Await for pod-0 to be recreated and make it running if err := wait.PollUntilContextTimeout(ctx, pollInterval, pollTimeout, false, func(ctx context.Context) (bool, error) { pods := getPods(t, podClient, labelMap) recreatedPods := v1.PodList{} for _, pod := range pods.Items { if pod.Status.Phase == v1.PodPending { recreatedPods.Items = append(recreatedPods.Items, pod) } } setPodsReadyCondition(t, c, &v1.PodList{Items: recreatedPods.Items}, v1.ConditionTrue, time.Now().Add(-120*time.Minute)) return len(recreatedPods.Items) > 0, nil }); err != nil { t.Fatalf(\"failed to await for pod-0 to be recreated by sts %s: %v\", sts.Name, err) } // Await for all stateful set status to record all replicas as ready if err := wait.PollUntilContextTimeout(ctx, pollInterval, pollTimeout, false, func(ctx context.Context) (bool, error) { ss, err := stsClient.Get(ctx, sts.Name, metav1.GetOptions{}) if err != nil { return false, err } return ss.Status.ReadyReplicas == *ss.Spec.Replicas, nil }); err != nil { t.Fatalf(\"failed to verify .Spec.Template.Spec.Containers[0].Image is updated for sts %s: %v\", sts.Name, err) } // Verify 3 pods exist pods = getPods(t, podClient, labelMap) if len(pods.Items) != int(*sts.Spec.Replicas) { t.Fatalf(\"Unexpected number of pods\") } // Verify pod images for i := range pods.Items { if i < int(*sts.Spec.UpdateStrategy.RollingUpdate.Partition) { if pods.Items[i].Spec.Containers[0].Image != oldImage { t.Fatalf(\"Pod %s has image %s not equal to old image %s\", pods.Items[i].Name, pods.Items[i].Spec.Containers[0].Image, oldImage) } } else { if pods.Items[i].Spec.Containers[0].Image != newImage { t.Fatalf(\"Pod %s has image %s not equal to new image %s\", pods.Items[i].Name, pods.Items[i].Spec.Containers[0].Image, newImage) } } } } </ins> func TestStatefulSetStartOrdinal(t *testing.T) { tests := []struct { ordinals         *appsv1.StatefulSetOrdinals", "positive_passages": [{"docid": "doc-en-kubernetes-78482ca8aa8474337677389890aeefe9bf7c97cdeab333d3d2b330616683b55b", "text": "Pla suggest : apiVersion: v1 kind: Service metadata: name: nginx labels: app: nginx spec: ports: port: 80 name: web clusterIP: None selector: app: nginx apiVersion: apps/v1 kind: StatefulSet metadata: name: web-am spec: updateStrategy: type: RollingUpdate rollingUpdate: partition: 1 serviceName: \"nginx\" replicas: 2 selector: matchLabels: app: nginx template: metadata: labels: app: nginx spec: containers: name: nginx args: /bin/sh -c sleep 30;touch /tmp/healthy; sleep 3600 image: nginx:1.14.2 ports: containerPort: 80 name: web", "commid": "kubernetes_issue_119685", "tokennum": 170}], "negative_passages": []}
{"query_id": "q-en-kubernetes-da94c4cc3bb21d2bc3ad8c1a76a8829b20a25b98d8ed4b9b129df9675ff80592", "query": "testReadFile(input.f, input.filePathInSubpath, input.pod, 0) }) <del> It(\"should fail for new directories when readOnly specified in the volumeSource [Slow]\", func() { if input.roVol == nil { framework.Skipf(\"Volume type %v doesn't support readOnly source\", input.volType) } // Format the volume while it's writable formatVolume(input.f, input.formatPod) // Set volume source to read only input.pod.Spec.Volumes[0].VolumeSource = *input.roVol // Pod should fail testPodFailSubpathError(input.f, input.pod, \"\") }) </del> // TODO: add a test case for the same disk with two partitions }", "positive_passages": [{"docid": "doc-en-kubernetes-3a5f8f6fae70577f1cbce129e8b4c7178012c138aa12442a5305f077f7f55297", "text": "xref: When running the GCE PD CSI Driver against all dynamic provisioning tests from this PR: We encounter the following test failures that need to be resolved: /kind bug /sig storage /cc\nSo it seems that the flag is getting passed all the way through to the driver and it is behaving as we would expect it to in terms of mounting. All the correct commands are being run: When exec-ing into the gce-pd-driver container we can observe that the mounted point is indeed read only. However, when viewed from the host node's perspective the mount is still read write. And therefore since the subpath folder is created by the host, the folder is still being created successfully which fails the test. This behavior suggests that is either not properly propagating the read only option on remount, or not properly remounting at all. I can't figure out how to \"view mount events\" if that's even possible, some help would be appreciated if anyone is aware of how to do that. That would help me narrrow down which of those two options is happening. I have also attempted (from inside the gce pd driver container) to unmount the point (successful) and bind mount it back with the readonly option directly (not using remount trick, still unsuccessful). Suggesting that maybe it is the that is not being mount propagated and not a problem with in particular. /cc\n/assign\n/milestone v1.13 /priority important-soon", "commid": "kubernetes_issue_70549", "tokennum": 314}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dacfbb60b8332c0c62dadb5b538ee9defcdb63b70df5f58e4e2a89910f5f3803", "query": "priorityClassName: system-node-critical hostNetwork: true nodeSelector: <del> # TODO(liggitt): switch to node.kubernetes.io/kube-proxy-ds-ready in 1.16 beta.kubernetes.io/kube-proxy-ds-ready: \"true\" </del> <ins> node.kubernetes.io/kube-proxy-ds-ready: \"true\" </ins> tolerations: - operator: \"Exists\" effect: \"NoExecute\"", "positive_passages": [{"docid": "doc-en-kubernetes-2c9ef8984ebaf899659836b925069334113c910fc47ebe0516a7d659674f044a", "text": "xref In 1.16: change the metadata-proxy addon to use change the kube-proxy addon to use change the masq-agent addon to use stop setting , , and in kube-up\nHey I'm trying to start to contribute to kubernetes and this seem to be an easy task. Can I help with this one?", "commid": "kubernetes_issue_75050", "tokennum": 77}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dae7682f0872fbd36e6677538156df35bd514bc78b01ff6015caa6565b38b4d3", "query": "create-kube-controller-manager-opts '${NODE_IPS}' create-kube-scheduler-opts create-flanneld-opts '127.0.0.1' '${MASTER_IP}' <del> sudo -E -p '[sudo] password to start master: ' -- /bin/bash -ce ' </del> <ins> FLANNEL_OTHER_NET_CONFIG='${FLANNEL_OTHER_NET_CONFIG}' sudo -E -p '[sudo] password to start master: ' -- /bin/bash -ce ' </ins> ${BASH_DEBUG_FLAGS} cp ~/kube/default/* /etc/default/", "positive_passages": [{"docid": "doc-en-kubernetes-3bb3543c0323a70faea91ccc43a3eaf950d3e30c811cd93e021b94a126351841", "text": "and provide for configuring Flannel's parameter but none of the others listed in", "commid": "kubernetes_issue_19618", "tokennum": 20}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dafa5b1f678212301837456775a8e4b09e095095055e34f4f0a6e870bc468b0c", "query": "return oomScoreAdj } <del> // getCachedVersionInfo gets cached version info of docker runtime. func (dm *DockerManager) getCachedVersionInfo() (kubecontainer.Version, kubecontainer.Version, error) { apiVersion, daemonVersion, err := dm.versionCache.Get(dm.machineInfo.MachineID) if err != nil { glog.Errorf(\"Failed to get cached docker api version %v \", err) } // If we got nil versions, try to update version info. if apiVersion == nil || daemonVersion == nil { dm.versionCache.Update(dm.machineInfo.MachineID) } return apiVersion, daemonVersion, err } </del> // checkDockerAPIVersion checks current docker API version against expected version. // Return: // 1 : newer than expected version // -1: older than expected version // 0 : same version func (dm *DockerManager) checkDockerAPIVersion(expectedVersion string) (int, error) { <del> apiVersion, _, err := dm.getCachedVersionInfo() </del> <ins> apiVersion, _, err := dm.getVersionInfo() </ins> if err != nil { return 0, err }", "positive_passages": [{"docid": "doc-en-kubernetes-c9313de66f3508f8886cd07268b253d5e2cfa321359afb89838b6984a0afe883", "text": "The recently merged PR a version cache in dockertools, which makes the test  flaky. The reason is that injected error into fakedockerclient and then expected to see the error from right after that (See ). However, the error was consumed by the goroutine which periodically updates the version cache (See ). The docker daemon version is rarely updated, and we only need version once for each container creating, during which we also do container create, start, inspect #etc. 1) Do we care about the cost of the call so much that we have to introduce the complexity? 2) Kubelet periodically calls , can we rely on that to update the cache? Anyhow, at least, we should disable the cache or have a fake one in the unit test. :) /cc\nI once considered move this cache to runtime level, while thus may need to change runtime interface. What if only cache apiversion?\nWe can only get via , so there will still be the data race. :) One option is to update the version cache in , now kubelet periodically call to check the runtime status. Another better option is to cache the version in layer, now is under our control, we can refactor it with an additional argument indicating whether to use cached value or get directly from the daemon. If we cache the version only for performance, I prefer the second option which is cleaner and more efficient. :)\nOK, will look into this tonight\nThe unit test itself should not start a goroutine to update the cache (unless you're actually testing the goroutine). We should disable it anyway, as we often do in our unit tests. It also sounds like we don't need a goroutine dedicated for this. If we can tolerate the additional overhead from time to time, we can set a expiration time (e.g., 1 minute), and only call the runtime if the entry expires.\nTotally agree. :) Maybe a new function in wrapping the update logic, or wrapping the logic in the .\nexpiration time sounds good in this case\nThis is happening quite frequently - increasing priority to P0.", "commid": "kubernetes_issue_24298", "tokennum": 452}], "negative_passages": []}
{"query_id": "q-en-kubernetes-db1b59401647c7c5da74e952ce4a065115be469cf022f0ac1544563e6683e821", "query": "<del> amd64=fedora:28 arm64=arm64v8/fedora:28 ppc64le=ppc64le/fedora:28 </del> <ins> amd64=fedora:26 arm64=arm64v8/fedora:26 ppc64le=ppc64le/fedora:26 </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-086f2ac7dcab9c158ca481b0b58fae22976bc98ae146a7d10d5bef748052b70d", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: e2e tests which use RBD server image fail with What you expected to happen: These tests succeed. How to reproduce it (as minimally and precisely as possible): Run e2e tests which use RBD server image. Anything else we need to know?: /sig storage This issue is introduced by below commit: It change the base image from fedora 26 to fedora 28. In fedora 26, hostname command is installed as a dependency for  However, in fedora 28, it is not installed, as a result, this issue happens due to lack of hostname command. Environment: Kubernetes version (use ): k8s 1.12 alpha\nPlease see the difference of the behaviour between fedora 26 and 28. [Fedora26] [Fedora28]\nCould you help solving this issue? I assume the fix for the code would be as below, but I'm not familiar with the build and push process for the test image. ( in doesn't work.) So, I need your help to make further progress.\n(or) Both need to be run from directory\nThank you for letting me know it. It should be s/all-containers/all-container/, but it seems to work. I will test with above patch and above build commands, then make a PR, once I confirm that it works well.\nsorry typing from memory :)\nI need to ask you two more things: Do we need to increment the version for this image, like 1.0.1, even for this small change? (I guess that and test/images/volume/rbd/VERSION will need to be updated in this case.) How the image push process will be? Does it pushed by CI, if there are a change in the code or docker file, or do someone who have permission will push it manually?\ncreates below three docker images: Is my understanding right that to make each test access to each arch image, needs to be modified like below? (Without doing so, each test seems to keep trying to access to , without arch.)\nFor fedora28 image, just installing hostname doesn't seem to work well. Please see the log below and attached . I guess that this is due to the difference of ceph version, which will be beyond my beyond my expertise.", "commid": "kubernetes_issue_67269", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-db1b59401647c7c5da74e952ce4a065115be469cf022f0ac1544563e6683e821", "query": "<del> amd64=fedora:28 arm64=arm64v8/fedora:28 ppc64le=ppc64le/fedora:28 </del> <ins> amd64=fedora:26 arm64=arm64v8/fedora:26 ppc64le=ppc64le/fedora:26 </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-77a7b6220df65aff10095b84f9a73f01dc0b39abd15f0db81cc810c0f75ed2d0", "text": "So, could you help debugging this issue? Meanwhile, I will try testing with the image by using fedora26 for workaround.\nI confirmed that below commit, which change the base image back to fedora 26, fix this issue. Please see the log . After I checked the image-, I come to think that by pushing the image, each image will be able to be pulled without -arch, so I guess the last parameter for ImageConfig should be false. (I couldn't test it in my environment.) I will fix the commit as so and make a PR once I confirm it. Also, if it will easy to fix with Fedora 28, I will wait for the actual fix and quit making a PR for the workaround.\nthanks yes, a quick fix is welcome, looking forward\nThank you for your comment. I will continue with the workaround. I saw a commit for deleting multi arch consideration. I rebased the patch to the commit and made a PR. Please review it.", "commid": "kubernetes_issue_67269", "tokennum": 212}], "negative_passages": []}
{"query_id": "q-en-kubernetes-db9de83127d04f305a4428beba88d40c4a21863e1ba43306042b9c4889c97b98", "query": "return err } <del> // GetDiskLun finds the lun on the host that the vhd is attached to, given a vhd's diskName and diskURI func (as *availabilitySet) GetDiskLun(diskName, diskURI string, nodeName types.NodeName) (int32, error) { </del> <ins> // GetDataDisks gets a list of data disks attached to the node. func (as *availabilitySet) GetDataDisks(nodeName types.NodeName) ([]compute.DataDisk, error) { </ins> vm, err := as.getVirtualMachine(nodeName) if err != nil { <del> return -1, err } disks := *vm.StorageProfile.DataDisks for _, disk := range disks { if disk.Lun != nil && (disk.Name != nil && diskName != \"\" && *disk.Name == diskName) || (disk.Vhd != nil && disk.Vhd.URI != nil && diskURI != \"\" && *disk.Vhd.URI == diskURI) || (disk.ManagedDisk != nil && *disk.ManagedDisk.ID == diskURI) { // found the disk glog.V(4).Infof(\"azureDisk - find disk: lun %d name %q uri %q\", *disk.Lun, diskName, diskURI) return *disk.Lun, nil } } return -1, fmt.Errorf(\"Cannot find Lun for disk %s\", diskName) } // GetNextDiskLun searches all vhd attachment on the host and find unused lun // return -1 if all luns are used func (as *availabilitySet) GetNextDiskLun(nodeName types.NodeName) (int32, error) { vm, err := as.getVirtualMachine(nodeName) if err != nil { return -1, err } used := make([]bool, maxLUN) disks := *vm.StorageProfile.DataDisks for _, disk := range disks { if disk.Lun != nil { used[*disk.Lun] = true } } for k, v := range used { if !v { return int32(k), nil } } return -1, fmt.Errorf(\"All Luns are used\") } // DisksAreAttached checks if a list of volumes are attached to the node with the specified NodeName func (as *availabilitySet) DisksAreAttached(diskNames []string, nodeName types.NodeName) (map[string]bool, error) { attached := make(map[string]bool) for _, diskName := range diskNames { attached[diskName] = false } vm, err := as.getVirtualMachine(nodeName) if err == cloudprovider.InstanceNotFound { // if host doesn't exist, no need to detach glog.Warningf(\"azureDisk - Cannot find node %q, DisksAreAttached will assume disks %v are not attached to it.\", nodeName, diskNames) return attached, nil } else if err != nil { return attached, err </del> <ins> return nil, err </ins> } <del> disks := *vm.StorageProfile.DataDisks for _, disk := range disks { for _, diskName := range diskNames { if disk.Name != nil && diskName != \"\" && *disk.Name == diskName { attached[diskName] = true } } </del> <ins> if vm.StorageProfile.DataDisks == nil { return nil, nil </ins> } <del> return attached, nil </del> <ins> return *vm.StorageProfile.DataDisks, nil </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-6cfc50824280daf2f66f5e84f9a8c720c316cfa724f1e90fa02f306c798e5010", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind cleanup What happened: VirtualMachineScaleSetVM and VirtualMachine are different data structures (because of different API versions), so the disk attach operation seems duplicate between vm and vmss. That means although disk operations are in same logic, some duplication are still required now. They should use same api version in the future and should be merged into same code base, e.g. move sharing logic to Refer What you expected to happen: vmss and vm disk operations should share same code logic. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\nI have checked with currently we can\u2019t merge, e.g. following two structs are different since they using different sdk-for-azure versions. While in the end when sdk-for-azure version is upgraded, above two versions should be same and at that time, we should merge functions like \u2018AttachDisk\u2019, \u2018DetachDiskByName\u2019, 'GetDiskLun', GetNextDiskLun, DisksAreAttached", "commid": "kubernetes_issue_59736", "tokennum": 313}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dbc082ab114bdf814f731e9376aaa6593265e824bbad5f9e7de0b6f40b1f025c", "query": "client, ns, labels.SelectorFromSet(labels.Set(rc.Spec.Selector))) } } <ins> func getPodLogs(c *client.Client, namespace, podName, containerName string) (string, error) { return getPodLogsInternal(c, namespace, podName, containerName, false) } func getPreviousPodLogs(c *client.Client, namespace, podName, containerName string) (string, error) { return getPodLogsInternal(c, namespace, podName, containerName, true) } // utility function for gomega Eventually func getPodLogsInternal(c *client.Client, namespace, podName, containerName string, previous bool) (string, error) { logs, err := c.Get(). Resource(\"pods\"). Namespace(namespace). Name(podName).SubResource(\"log\"). Param(\"container\", containerName). Param(\"previous\", strconv.FormatBool(previous)). Do(). Raw() if err != nil { return \"\", err } if err == nil && strings.Contains(string(logs), \"Internal Error\") { return \"\", fmt.Errorf(\"Fetched log contains \"Internal Error\": %q.\", string(logs)) } return string(logs), err } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-cf37b0ab7a08d0e2457507bc271b1cb7d1e13fbaee3773971363bc32ae71b35b", "text": "We are running heapster, dns server, kube-proxy etc. in kube-system namespace. Some e2e tests try to make sure all those kube-system pods are at ready state before firing the real tests, others just simply ingore them. But both cases might cause e2e flakiness when some of those kube-system containers are in crashloop, for example, for heapster crashloop, for influxdb crashloop, etc. When such cases happen, the developer doesn't have much information on why since the nodes might be teared down. We should watch those kube-system pods, and onContainerFailure, we should collect the related logs. One simple way is using kubectl logs <Pod<Container--previous cc/\nis this related enough to and that you can bundle it in?\nThe logs from the pods should be retrieved via the api server. This is different from the kubelet logs. I'll upload a PR for this.\nGreat job It will be very helpful for debugging.", "commid": "kubernetes_issue_20099", "tokennum": 229}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dbd04dbee5e158e40a7171bd688972b357ded9528bfbfc4373daf47c0c495ad3", "query": "t *testing.T, expectedAttachCallCount int, fakePlugin *volumetesting.FakeVolumePlugin) { <del> if len(fakePlugin.Attachers) == 0 && expectedAttachCallCount == 0 { </del> <ins> if len(fakePlugin.GetAttachers()) == 0 && expectedAttachCallCount == 0 { </ins> return } err := retryWithExponentialBackOff( time.Duration(5*time.Millisecond), func() (bool, error) { <del> for i, attacher := range fakePlugin.Attachers { </del> <ins> for i, attacher := range fakePlugin.GetAttachers() { </ins> actualCallCount := attacher.GetAttachCallCount() if actualCallCount == expectedAttachCallCount { return true, nil", "positive_passages": [{"docid": "doc-en-kubernetes-8eb466904f09832d9690a82d180fa467ae255966eba3f5f112ba1d2e4e87f745", "text": "Looks like similar issue with\nThat's the PV controller this is the attach controller, thus separate issues.", "commid": "kubernetes_issue_26377", "tokennum": 21}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dbe4dfc4c44650bb7cfc5e94bdb838651fc50b1a966363ce44ae72f85b1084ec", "query": ") const ( <del> probeTimeOut = time.Minute </del> <ins> probeTimeOut = 20 * time.Second </ins> ) // TODO: this basic interface is duplicated in N places.  consolidate?", "positive_passages": [{"docid": "doc-en-kubernetes-98dd9e78520525bf65ff2afc2de58a6375036f9264791def3d02921656a321fe", "text": "this job failed with It seems it is imssing some dependency The job history confirms it is totally broken Originally posted by in\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig testing", "commid": "kubernetes_issue_103738", "tokennum": 114}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dbe63af62afeaa357339e2516839a12bd7a5f7f16fe419dcd206539efe8a4ceb", "query": "rbdImageSizeUnitMiB      = 1024 * 1024 ) <ins> // A struct contains rbd image info. type rbdImageInfo struct { pool string name string } </ins> func getDevFromImageAndPool(pool, image string) (string, bool) { device, found := getRbdDevFromImageAndPool(pool, image) if found {", "positive_passages": [{"docid": "doc-en-kubernetes-504dcfb92cdb541009bacf4c1b680d2ebe053bb62fdf81ca10ac728d32628e43", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: Pod was deleted successfully but there is still a lock on the ceph image. I find two logs,one for that lock not removed and another for that lock removed. I find that there are little difference between them. the log that lock not removed: and the log that lock removed: What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.6.7 Cloud provider or hardware configuration**: OS (e.g. from /etc/os-release): centos7 Kernel (e.g. ): 3.10.0-327.el7.x86_64 Install tools: Others:\n/sig storage\nError 16 is EBUSY. similar to\nwere you running kubelet with cadvisor on?\n/assign\nyes, every kubelet run with cadvisor,and i know what code 16 represent for,but i still don't know the reason, is this a bug? How can i avoid this kind of situation from happening,thank you\nIt is probably related to\nWe see some other case may cause , kubelet run with nodeexporter and nodeexporter is deployed by k8s daemonset with -v /:/rootfs:ro (mount kubelet host rootfs into nodeexporter container). rbd device is mounted before nodeexporter started, because k8s 1.6.7 not support mount propagation, when the rbd plugin unmount /dev/rbd0 on the host namespace, the mount info will still leave over in node_exporter container namespace, may cause . hope this would help\nthanks, does the problem persist if node_exporter stops collecting filesystem metrics?\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with .", "commid": "kubernetes_issue_54214", "tokennum": 513}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dbe63af62afeaa357339e2516839a12bd7a5f7f16fe419dcd206539efe8a4ceb", "query": "rbdImageSizeUnitMiB      = 1024 * 1024 ) <ins> // A struct contains rbd image info. type rbdImageInfo struct { pool string name string } </ins> func getDevFromImageAndPool(pool, image string) (string, bool) { device, found := getRbdDevFromImageAndPool(pool, image) if found {", "positive_passages": [{"docid": "doc-en-kubernetes-e58e0280341e2b39cd2fb25afc5193b55cba235066305ff633e2c34889e5eefe", "text": "Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nI'm experiencing this issue. From what I can read above, if the rbd mount happens before the node_exporter starts; we'll always experience status 16?\nWe're getting this issue. This is because the mounted volume is mounted on Cadvisor container too. So the /dev/rbdX file is still in use. But still didn't find any solution to fix.\nrbd volume will stuck when failed as will always returen\nMy solution: container use a volumeMount. make a script file to be executed every a minute:", "commid": "kubernetes_issue_54214", "tokennum": 220}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dbfbda2f88574957b82a5dd48e8d2d4f3f3b199a67b78319e88ec659c8539d1c", "query": "job.Spec.Template.Spec.RestartPolicy = v1.RestartPolicyOnFailure sharedInformerFactory.Batch().V1().Jobs().Informer().GetIndexer().Add(job) podIndexer := sharedInformerFactory.Core().V1().Pods().Informer().GetIndexer() <del> for i, pod := range newPodList(int32(len(tc.restartCounts)), v1.PodRunning, job) { </del> <ins> for i, pod := range newPodList(int32(len(tc.restartCounts)), tc.podPhase, job) { </ins> pod.Status.ContainerStatuses = []v1.ContainerStatus{{RestartCount: tc.restartCounts[i]}} podIndexer.Add(&pod) }", "positive_passages": [{"docid": "doc-en-kubernetes-57b8eab4723f670b6603d9bfb82377ab99cdb5a96c17a18501cc8d4284272435", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: I create a job with initcontainer with restartPolicy : when the initContainer exec failed and it will be restarted, the pod Phase will be pending all the time. but in JobController, the only care the running pod. So this pod will be always restarted. What you expected to happen: when restart count to backoffLimit, the job failed. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig apps\n/assign", "commid": "kubernetes_issue_77644", "tokennum": 220}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dc1ab924eec63e956eefd33df4f146060150af537a0d38a9db02f2999199bc4f", "query": "<ins> /* Copyright 2023 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package service import ( \"bytes\" \"context\" \"encoding/base64\" \"fmt\" \"math/rand\" \"net\" \"os\" \"path/filepath\" \"testing\" \"time\" \"google.golang.org/grpc\" \"google.golang.org/grpc/credentials/insecure\" kmsapi \"k8s.io/kms/apis/v2alpha1\" ) const version = \"v2alpha1\" func TestGRPCService(t *testing.T) { t.Parallel() defaultTimeout := 30 * time.Second ctx, cancel := context.WithTimeout(context.Background(), defaultTimeout) t.Cleanup(cancel) address := filepath.Join(os.TempDir(), \"kmsv2.sock\") plaintext := []byte(\"lorem ipsum dolor sit amet\") r := rand.New(rand.NewSource(time.Now().Unix())) id, err := makeID(r.Read) if err != nil { t.Fatal(err) } kmsService := newBase64Service(id) server := NewGRPCService(address, defaultTimeout, kmsService) go func() { if err := server.ListenAndServe(); err != nil { panic(err) } }() t.Cleanup(server.Shutdown) client := newClient(t, address) t.Run(\"should be able to encrypt and decrypt through unix domain sockets\", func(t *testing.T) { t.Parallel() encRes, err := client.Encrypt(ctx, &kmsapi.EncryptRequest{ Plaintext: plaintext, Uid:       id, }) if err != nil { t.Fatal(err) } if bytes.Equal(plaintext, encRes.Ciphertext) { t.Fatal(\"plaintext and ciphertext shouldn't be equal!\") } decRes, err := client.Decrypt(ctx, &kmsapi.DecryptRequest{ Ciphertext:  encRes.Ciphertext, KeyId:       encRes.KeyId, Annotations: encRes.Annotations, Uid:         id, }) if err != nil { t.Fatal(err) } if !bytes.Equal(decRes.Plaintext, plaintext) { t.Errorf(\"want: %q, have: %q\", plaintext, decRes.Plaintext) } }) t.Run(\"should return status data\", func(t *testing.T) { t.Parallel() status, err := client.Status(ctx, &kmsapi.StatusRequest{}) if err != nil { t.Fatal(err) } if status.Healthz != \"ok\" { t.Errorf(\"want: %q, have: %q\", \"ok\", status.Healthz) } if len(status.KeyId) == 0 { t.Errorf(\"want: len(keyID) > 0, have: %d\", len(status.KeyId)) } if status.Version != version { t.Errorf(\"want %q, have: %q\", version, status.Version) } }) } func newClient(t *testing.T, address string) kmsapi.KeyManagementServiceClient { t.Helper() cnn, err := grpc.Dial( address, grpc.WithTransportCredentials(insecure.NewCredentials()), grpc.WithDialer(func(addr string, t time.Duration) (net.Conn, error) { return net.Dial(\"unix\", addr) }), ) if err != nil { t.Fatal(err) } t.Cleanup(func() { _ = cnn.Close() }) return kmsapi.NewKeyManagementServiceClient(cnn) } type testService struct { decrypt func(ctx context.Context, uid string, req *DecryptRequest) ([]byte, error) encrypt func(ctx context.Context, uid string, data []byte) (*EncryptResponse, error) status  func(ctx context.Context) (*StatusResponse, error) } var _ Service = (*testService)(nil) func (s *testService) Decrypt(ctx context.Context, uid string, req *DecryptRequest) ([]byte, error) { return s.decrypt(ctx, uid, req) } func (s *testService) Encrypt(ctx context.Context, uid string, data []byte) (*EncryptResponse, error) { return s.encrypt(ctx, uid, data) } func (s *testService) Status(ctx context.Context) (*StatusResponse, error) { return s.status(ctx) } func makeID(rand func([]byte) (int, error)) (string, error) { b := make([]byte, 10) if _, err := rand(b); err != nil { return \"\", err } return base64.StdEncoding.EncodeToString(b), nil } func newBase64Service(keyID string) *testService { decrypt := func(_ context.Context, _ string, req *DecryptRequest) ([]byte, error) { if req.KeyID != keyID { return nil, fmt.Errorf(\"keyID mismatch. want: %q, have: %q\", keyID, req.KeyID) } return base64.StdEncoding.DecodeString(string(req.Ciphertext)) } encrypt := func(_ context.Context, _ string, data []byte) (*EncryptResponse, error) { return &EncryptResponse{ Ciphertext: []byte(base64.StdEncoding.EncodeToString(data)), KeyID:      keyID, }, nil } status := func(_ context.Context) (*StatusResponse, error) { return &StatusResponse{ Version: version, Healthz: \"ok\", KeyID:   keyID, }, nil } return &testService{ decrypt: decrypt, encrypt: encrypt, status:  status, } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-82432c9a9613bf4aed980cc8db469ba43857eb8e48c1e0dd0f39492115206ab6", "text": "generation for local KEK based on counter; also rotate once a week even if the counter does not hit 2 million? using AES-GCM encryption of local KEK ref: The implementation would be to the directory.\n/sig auth /triage accepted\n/assign\nGitHub didn't allow me to assign the following users: ibihim. 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\n/assign\nthank you !\n/milestone v1.26\nHi bug-triage shadow team member for 1.26 here. Looks like this issue is in the 1.26 milestone, but has been moved to 1.27. Is there something else or should this issue go to 1.27 as well? Thank you!\nI just forgot to move this issue /milestone v1.27\n/reopen is the partial implementation.\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nMy suggestion on the reference implementation, after reading 's comments is like so... The GRPC server, which implements the expects an implementation that satisfies . The local key logic can be a middleware. So it expects a it can fallback to, if it doesn't know a key or needs to encrypt its own local KEK. So the local implementation would be need to: have a storage of s have a reference to the current in use (if we put it into the cache, it might vanish) have a reference to another , which should be the remote KMS. So the sub-stories could look like: write Middleware write Transformers that can get exhausted (by time, by usage) write 's storage write some dummy for remote KMS? I have some sketches of what I am talking about .", "commid": "kubernetes_issue_112859", "tokennum": 462}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dc1ab924eec63e956eefd33df4f146060150af537a0d38a9db02f2999199bc4f", "query": "<ins> /* Copyright 2023 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package service import ( \"bytes\" \"context\" \"encoding/base64\" \"fmt\" \"math/rand\" \"net\" \"os\" \"path/filepath\" \"testing\" \"time\" \"google.golang.org/grpc\" \"google.golang.org/grpc/credentials/insecure\" kmsapi \"k8s.io/kms/apis/v2alpha1\" ) const version = \"v2alpha1\" func TestGRPCService(t *testing.T) { t.Parallel() defaultTimeout := 30 * time.Second ctx, cancel := context.WithTimeout(context.Background(), defaultTimeout) t.Cleanup(cancel) address := filepath.Join(os.TempDir(), \"kmsv2.sock\") plaintext := []byte(\"lorem ipsum dolor sit amet\") r := rand.New(rand.NewSource(time.Now().Unix())) id, err := makeID(r.Read) if err != nil { t.Fatal(err) } kmsService := newBase64Service(id) server := NewGRPCService(address, defaultTimeout, kmsService) go func() { if err := server.ListenAndServe(); err != nil { panic(err) } }() t.Cleanup(server.Shutdown) client := newClient(t, address) t.Run(\"should be able to encrypt and decrypt through unix domain sockets\", func(t *testing.T) { t.Parallel() encRes, err := client.Encrypt(ctx, &kmsapi.EncryptRequest{ Plaintext: plaintext, Uid:       id, }) if err != nil { t.Fatal(err) } if bytes.Equal(plaintext, encRes.Ciphertext) { t.Fatal(\"plaintext and ciphertext shouldn't be equal!\") } decRes, err := client.Decrypt(ctx, &kmsapi.DecryptRequest{ Ciphertext:  encRes.Ciphertext, KeyId:       encRes.KeyId, Annotations: encRes.Annotations, Uid:         id, }) if err != nil { t.Fatal(err) } if !bytes.Equal(decRes.Plaintext, plaintext) { t.Errorf(\"want: %q, have: %q\", plaintext, decRes.Plaintext) } }) t.Run(\"should return status data\", func(t *testing.T) { t.Parallel() status, err := client.Status(ctx, &kmsapi.StatusRequest{}) if err != nil { t.Fatal(err) } if status.Healthz != \"ok\" { t.Errorf(\"want: %q, have: %q\", \"ok\", status.Healthz) } if len(status.KeyId) == 0 { t.Errorf(\"want: len(keyID) > 0, have: %d\", len(status.KeyId)) } if status.Version != version { t.Errorf(\"want %q, have: %q\", version, status.Version) } }) } func newClient(t *testing.T, address string) kmsapi.KeyManagementServiceClient { t.Helper() cnn, err := grpc.Dial( address, grpc.WithTransportCredentials(insecure.NewCredentials()), grpc.WithDialer(func(addr string, t time.Duration) (net.Conn, error) { return net.Dial(\"unix\", addr) }), ) if err != nil { t.Fatal(err) } t.Cleanup(func() { _ = cnn.Close() }) return kmsapi.NewKeyManagementServiceClient(cnn) } type testService struct { decrypt func(ctx context.Context, uid string, req *DecryptRequest) ([]byte, error) encrypt func(ctx context.Context, uid string, data []byte) (*EncryptResponse, error) status  func(ctx context.Context) (*StatusResponse, error) } var _ Service = (*testService)(nil) func (s *testService) Decrypt(ctx context.Context, uid string, req *DecryptRequest) ([]byte, error) { return s.decrypt(ctx, uid, req) } func (s *testService) Encrypt(ctx context.Context, uid string, data []byte) (*EncryptResponse, error) { return s.encrypt(ctx, uid, data) } func (s *testService) Status(ctx context.Context) (*StatusResponse, error) { return s.status(ctx) } func makeID(rand func([]byte) (int, error)) (string, error) { b := make([]byte, 10) if _, err := rand(b); err != nil { return \"\", err } return base64.StdEncoding.EncodeToString(b), nil } func newBase64Service(keyID string) *testService { decrypt := func(_ context.Context, _ string, req *DecryptRequest) ([]byte, error) { if req.KeyID != keyID { return nil, fmt.Errorf(\"keyID mismatch. want: %q, have: %q\", keyID, req.KeyID) } return base64.StdEncoding.DecodeString(string(req.Ciphertext)) } encrypt := func(_ context.Context, _ string, data []byte) (*EncryptResponse, error) { return &EncryptResponse{ Ciphertext: []byte(base64.StdEncoding.EncodeToString(data)), KeyID:      keyID, }, nil } status := func(_ context.Context) (*StatusResponse, error) { return &StatusResponse{ Version: version, Healthz: \"ok\", KeyID:   keyID, }, nil } return &testService{ decrypt: decrypt, encrypt: encrypt, status:  status, } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-b75b4d558a76c05a2f299aa9e4208bfe14cbcf4125785eeef841ee037778035f", "text": "I would implement that in terms of the interface so that it can be used both in testing (via a local key) and in real code (by delegating to a HSM).\nHi bug-triage team member for 1.27 here. This issue is still open but has had no recent activity, and no active PRs. Is everything on track for the Code Freeze in March 14th? Thank you!\n/milestone clear\nCould be closed, right? :)\nWe still need metrics and tracing support for the reference implementation (though it is all a lot less important now).\n/retitle [KMSv2] Add metrics and tracing in for plugins\nThis is duplicate of /close\nClosing this issue. <detailsIn response to : This is duplicate of 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", "commid": "kubernetes_issue_112859", "tokennum": 192}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dc70d6005f083f2a6b41c6aa4503f2ed205d90d667bd54ee81cc7aeec98c5032", "query": "\"Logs\":               BeNil(), \"UserDefinedMetrics\": BeEmpty(), }) <ins> systemContainers := gstruct.Elements{ \"kubelet\": sysContExpectations, \"runtime\": sysContExpectations, } // The Kubelet only manages the 'misc' system container if the host is not running systemd. if !systemdutil.IsRunningSystemd() { framework.Logf(\"Host not running systemd; expecting 'misc' system container.\") systemContainers[\"misc\"] = sysContExpectations } </ins> // Expectations for pods. podExpectations := gstruct.MatchAllFields(gstruct.Fields{ \"PodRef\":    gstruct.Ignore(),", "positive_passages": [{"docid": "doc-en-kubernetes-237446a2101b1d0e3896762c3997d0b07e17e89bcd32bef5edcdc8a493c92d82", "text": "Kubernetes version (use ): 6 Environment: GCE What happened: I created a cluster for Heapster testing purposes to debug failing test in It turned out that Summary API does not export system/misc stats in SystemContainers section (though there are kubelet and docker stats). Everything works as expected on nodes. See also https://k8s-\nWhat node OS were you using? We don't create the system (misc) container on systemd, so it's expected that GCI nodes don't report those stats.\nThe default configuration for 1.4, which is: master: GCI nodes: Container VM\nAre the nodes running 1.4.6 too? There was a bug with this in 1.4.5, but it should have been fixed in 1.4.6.\nYes, both are running in 1.4.6. If you want to reproduce from Heapster current head run . It will take some time and as a side effect you should have a cluster with the mentioned problem. This was catch by integration tests and I temporary disabled the check here\nif you have spare cycles, can you look into this?\nfriendly ping\nLooking at it now\nI have found a couple things so far. On the containerVM nodes, cadvisor is exporting a container with \"name\": \"/system\" On the GCI Master, cadvisor is exporting a container with \"name\": \"\" The has this: \"{% set system_container = \"--system-cgroups=/system\" -%}\" (/system is the default misc container name) So the real question is: Should cadvisor export \"/system\" instead of \"\" on GCI? Or should we be configuring GCI to use \"--system-\"?\nI thought we fix this very issue for 1.4 branch by a while back. Are you running into the same issue with 1.5?\nI think I told you the wrong thing earlier. We don't support the misc (/system) cgroup on systemd systems (I can't remember why, but it was an explicit decision - or might know). The is something different, I believe a base systemd cgroup (slice). As for the misc container on ContainerVM nodes, we've been testing for the misc container in 1.5+ in the summary api test (https://k8s-) for a while, and I haven't seen this issue.", "commid": "kubernetes_issue_37453", "tokennum": 538}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dc70d6005f083f2a6b41c6aa4503f2ed205d90d667bd54ee81cc7aeec98c5032", "query": "\"Logs\":               BeNil(), \"UserDefinedMetrics\": BeEmpty(), }) <ins> systemContainers := gstruct.Elements{ \"kubelet\": sysContExpectations, \"runtime\": sysContExpectations, } // The Kubelet only manages the 'misc' system container if the host is not running systemd. if !systemdutil.IsRunningSystemd() { framework.Logf(\"Host not running systemd; expecting 'misc' system container.\") systemContainers[\"misc\"] = sysContExpectations } </ins> // Expectations for pods. podExpectations := gstruct.MatchAllFields(gstruct.Fields{ \"PodRef\":    gstruct.Ignore(),", "positive_passages": [{"docid": "doc-en-kubernetes-c190eb06e0eb058949f528f1af5886fe17cab35cd1b33a69ea2cddc6a3fc8812", "text": "So if this is still reproducible, it's limited to 1.4. See this the bug was created for the post-fix.\nFound the explanation here: The should use the flag to know the location that has the processes that are associated with , but it should not modify the cgroups of existing processes on the system during bootstrapping of the node. This is because is the on the host and it has not delegated authority to the to change how it manages .\nIIUC this is intended behavior on systemd nodes. Based on the explanation provided, the kubelet doesnt have the authority to control \"misc\" processes on systemd.\n+1. \"misc\" is just a bandaid for cvm. , David Ashpole <:\nOk, so I'm closing this issue.", "commid": "kubernetes_issue_37453", "tokennum": 168}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dcdd95f6dcd5c34cb54a8efd2df224cd1fc099e4e41352c736c7eabfa466eb5a", "query": "// +k8s:deepcopy-gen:interfaces=k8s.io/apimachinery/pkg/runtime.Object <del> // EncryptionConfiguration stores the complete configuration for encryption providers. </del> <ins> /* EncryptionConfiguration stores the complete configuration for encryption providers. example: kind: EncryptionConfiguration apiVersion: apiserver.config.k8s.io/v1 resources: - resources: - secrets - configmaps - pandas.awesome.bears.example providers: - aescbc: keys: - name: key1 secret: c2VjcmV0IGlzIHNlY3VyZQ== */ </ins> type EncryptionConfiguration struct { metav1.TypeMeta // resources is a list containing resources, and their corresponding encryption providers.", "positive_passages": [{"docid": "doc-en-kubernetes-0045c1600a60d9073df9d5127e356e4d0c19e0407dd07c166d371541fb200a6a", "text": "Update the godoc on the encryption config API on how to specify group/resources to be encrypted ref: godoc has the details na No response_ na na <details</details<details</details<details</details<details</details\n/sig auth /triage accepted\n/assign Cool-Coder174\nThanks for volunteering for this LMK if you need any help with it.\nJust for clarification, I just need to add documentation on how to configure encryption on groups/resources?\nYou can update godoc to mention that custom resources can now be to the list of to be encrypted as well and how to add the of the resource to the list. e.g. from this test\n/assign /unassign Release v1.26 deadlines are here so we need to get this completed ASAP.\n/milestone v1.26\nI apologize for the slow actions. I know time and contributions are valuable. May I request a walk through. This is my first time ever contributing and I really want to learn. I have been reading some of the code base on my spare time.\nthis feature is on the harder side of things to get started with. Reading the blog post and the associated documentation is probably the best starting point:\n& what is the status on this issue? 1.26 is coming up! cc\n/milestone v1.27", "commid": "kubernetes_issue_113272", "tokennum": 293}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dcddd04fa78b4e83b24595824a6413223ee6c70020bbd4491fd0da797fc81d65", "query": "import ( \"fmt\" <ins> \"net/http/httptest\" </ins> \"testing\" \"k8s.io/kubernetes/pkg/api\"", "positive_passages": [{"docid": "doc-en-kubernetes-b0a441a371f8db864bebc11c7303837af71a86244bb0f50ec81fe1d8a09d5c71", "text": "The test is in flaky suite and no one seems to care. We need an owner for this test. cc Last failure log:\ndo you think you can take a look at this?\nThis is happening because of a bad assumption. The assumption is: if the reflector's store is consistent with etcd, the store given back to clients of the framework.Controller is too. I'd really like a general fix applicable to all controllers for this problem, but fixing it just for the RCs is pretty easy. In more detail: This function reports when the reflector has listed from apiserver. But the store given to the reflector is the fifo of the framework.Controller. The store given back to the caller is still not consistent, and will not be till the framework.Controller puts all the objects from the fifo into the client state store (). The rc specific fix: Before starting the rc manager, seed the expectations store with an expectation like {rc:foo, adds: foo.Status.Replicas, deletes:0}. This will wait for status.Replicas number of ADD events till a timeout. The general fix: Somehow expose this through framework.Controller.HasSynced (clients don't care about the fifo anyway, shouldn't it just be an implementation detail?) ideas? cc'ing people who have written controllers that might be interested I don't think this (and generally anything flaky for 1 release) is a p0, I can fix it if you don't mind dealing with the flakes till I've cleared things off my plate. I'd be more than happy to review a fix.\nWell, it's a P0 because test is flaky. E.g last run:\n- did you have chance to look into it?\nThe \"DaemonRestart\" tests are still labeled at . I will send a PR to promote them.\nare you still planning to send aPR to promote the DaemonRestart tests out of flaky? I think this is the right thing to do.\nAck; sorry, I lost this in the muck.", "commid": "kubernetes_issue_17829", "tokennum": 444}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dce1fa08f444ae324ae3cd65da1871cc642b323b99ba50bebddf8d23db6d3529", "query": "./hack/test-cmd.sh ./hack/test-integration.sh ./hack/test-update-storage-objects.sh", "positive_passages": [{"docid": "doc-en-kubernetes-bbec53075a30148d3cbdbc5512f8af7c37c0a3695f84aff12aac6489eaa4282e", "text": "Not sure if this concided with a Jenkins restart.\nNot sure what we can do about this. Retry a few times?\nGitHub seemed to hiccup last night and fail a bunch of our builds. I'm not sure a retry would've helped, unless we kept retrying for many minutes.\nThis is the sort of thing that just happens occasionally. We've seen this a lot in OpenShift CI runs. I'm not sure there's much you can do other than try to avoid external network access (e.g. bake tools into the VM image).\nIt seems to have occurred twice in the last 12h so retry w/ timeout can't hurt?\nIt can't hurt... but it may or may not help depending on the extent of the external issue\nIf the problem is really bad, we could toss it somewhere on GCS?\nLooks like it failed on : We should probably put this in a retry loop or else do something more fancy", "commid": "kubernetes_issue_21887", "tokennum": 212}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dced4a85b86a6d99fde415c82d418f97edd2225575fc6e84584374a82ae503c0", "query": "klog.Errorf(\"scheduler cache AddNode failed: %v\", err) } <ins> klog.V(3).Infof(\"add event for node %q\", node.Name) </ins> sched.SchedulingQueue.MoveAllToActiveOrBackoffQueue(queue.NodeAdd) }", "positive_passages": [{"docid": "doc-en-kubernetes-671a12759d851f1b99028bc477360c418e1157a45a2e814ff1c5c1cdd09da36a", "text": "This helps debugging scheduler's behavior, currently we don't have logs that indicate when the scheduler first saw a pod or a node. The log level should be v=3. /sig scheduling /cc\nDo you mean add logging for callbacks in ?\nyes, at least for add and delete events\nSure, I can also give this pr, before tomorrow\n/assign\nWe actually have one v=2 log line for a Node being to the cache's tree: But it's probably good to keep this one.", "commid": "kubernetes_issue_87524", "tokennum": 111}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dceee20e81a639b0bb371ee9334ff07ee751bc2861752d95bf25e211e4e93742", "query": "} func (kvh *kubeletVolumeHost) GetPodVolumeDir(podUID types.UID, pluginName string, volumeName string) string { <del> return kvh.kubelet.getPodVolumeDir(podUID, pluginName, volumeName) </del> <ins> dir := kvh.kubelet.getPodVolumeDir(podUID, pluginName, volumeName) if runtime.GOOS == \"windows\" { dir = volume.GetWindowsPath(dir) } return dir </ins> } func (kvh *kubeletVolumeHost) GetPodVolumeDeviceDir(podUID types.UID, pluginName string) string {", "positive_passages": [{"docid": "doc-en-kubernetes-295b16ebdca2097490863d761fa466b150fe770891272091eba588ee367ef882", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: I have tried FlexVolume on a Windows node, it does not work. I am now working on this feature now. Below is the FlexVolume initialization error What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.7.7 Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: /sig windows /assign\nDetailed steps about how to use flexvolume on Windows with this PR:\ncc:", "commid": "kubernetes_issue_56875", "tokennum": 183}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dd162b9c51d51523549ad21ce4a9649ce70db7556783795df6a52afd80711ac9", "query": "// TestTimeout is used for most polling/waiting activities TestTimeout = 60 * time.Second <ins> // AffinityTimeout is the maximum time that CheckAffinity is allowed to take; this // needs to be more than long enough for AffinityConfirmCount HTTP requests to // complete in a busy CI cluster, but shouldn't be too long since we will end up // waiting the entire time in the tests where affinity is not expected. AffinityTimeout = 2 * time.Minute </ins> // AffinityConfirmCount is the number of needed continuous requests to confirm that // affinity is enabled. AffinityConfirmCount = 15", "positive_passages": [{"docid": "doc-en-kubernetes-3bd2c8928ffbfbb644dae4df3d9fa0aa73d567a5bc560c59938e22bd3dd510ca", "text": "Which jobs are failing: pull-kubernetes-e2e-gce Which test(s) are failing: [sig-network] Services should have session affinity work for NodePort service [LinuxOnly] [sig-network] Services should be able to switch session affinity for service with type clusterIP [LinuxOnly] [sig-network] Services should be able to switch session affinity for NodePort service [LinuxOnly] [sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] Since when has it been failing: At least since 9/30 (). But that's almost at the end of what's currently visible on the testgrid, so maybe longer Testgrid link: Not sure what I'm supposed to put here. ? Reason for failure: The test case connects to a service every 2 seconds for 1 minute and checks if it hit the same endpoint at least 15 times in a row. But the individual checks are taking unexpectedly long and so sometimes the test doesn't even manage to run 15 times total in 1 minute.", "commid": "kubernetes_issue_83617", "tokennum": 235}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dd162b9c51d51523549ad21ce4a9649ce70db7556783795df6a52afd80711ac9", "query": "// TestTimeout is used for most polling/waiting activities TestTimeout = 60 * time.Second <ins> // AffinityTimeout is the maximum time that CheckAffinity is allowed to take; this // needs to be more than long enough for AffinityConfirmCount HTTP requests to // complete in a busy CI cluster, but shouldn't be too long since we will end up // waiting the entire time in the tests where affinity is not expected. AffinityTimeout = 2 * time.Minute </ins> // AffinityConfirmCount is the number of needed continuous requests to confirm that // affinity is enabled. AffinityConfirmCount = 15", "positive_passages": [{"docid": "doc-en-kubernetes-be859aec3019c8f94fa574b44096bac92d128f839b0ed157072d5b09f5ea53f4", "text": "eg: Oct 8 13:32:01.402: INFO: Running ' --server=https://34.82.143.14 -- exec --namespace=services-1060 execpod-affinityklpfn -- /bin/sh -x -c curl -q -s --connect-timeout 2 http://10.40.0.5:/' Oct 8 13:32:07.627: INFO: stderr: \"+ curl -q -s --connect-timeout 2 http://10.40.0.5:/n\" Oct 8 13:32:07.627: INFO: stdout: \"affinity-nodeport-2z9hv\" Oct 8 13:32:07.627: INFO: Received response from host: affinity-nodeport-2z9hv Oct 8 13:32:09.402: INFO: Running ' --server=https://34.82.143.14 -- exec --namespace=services-1060 execpod-affinityklpfn -- /bin/sh -x -c curl -q -s --connect-timeout 2 http://10.40.0.5:/' Oct 8 13:32:16.027: INFO: stderr: \"+ curl -q -s --connect-timeout 2 http://10.40.0.5:/n\" Oct 8 13:32:16.027: INFO: stdout: \"affinity-nodeport-2z9hv\" Oct 8 13:32:16.027: INFO: Received response from host: affinity-nodeport-2z9hv Note the gap between the \"Running\" line and the \"stderr\" line. It's not clear if the slowness is in connecting to the execpod or in connecting from the execpod to the affinity service. It is also not particularly consistent between attempts. (Here it was 6s, 1s, 2s, 3s, 5s, 7s, 7s, 3s, 4s, 6s, 7s, 8s.) Anything else we need to know: It looks the checks are also slow in successful runs, it's just that they're not quite as slow, so they pass.", "commid": "kubernetes_issue_83617", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dd162b9c51d51523549ad21ce4a9649ce70db7556783795df6a52afd80711ac9", "query": "// TestTimeout is used for most polling/waiting activities TestTimeout = 60 * time.Second <ins> // AffinityTimeout is the maximum time that CheckAffinity is allowed to take; this // needs to be more than long enough for AffinityConfirmCount HTTP requests to // complete in a busy CI cluster, but shouldn't be too long since we will end up // waiting the entire time in the tests where affinity is not expected. AffinityTimeout = 2 * time.Minute </ins> // AffinityConfirmCount is the number of needed continuous requests to confirm that // affinity is enabled. AffinityConfirmCount = 15", "positive_passages": [{"docid": "doc-en-kubernetes-0f765c22d0d19db3b6df2fd444c9da8d7f7f8af548830f46d73b17c37e323eed", "text": "I'm not sure if the problem is \"something is making the cluster slow and so this totally valid test is taking too long and failing\" or \"e2e-gce has grown over time and now cluster load has reached the point where this formerly-passing test now has unreasonable performance expectations\". /sig network", "commid": "kubernetes_issue_83617", "tokennum": 66}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dd888b4d1db7ff4a425b3c9f02a871f70f057633818a00450e00d9176f8f3eaf", "query": "return &runtimeapi.UpdateContainerResourcesResponse{}, nil } <del> func (ds *dockerService) performPlatformSpecificContainerForContainer(containerID string) { </del> <ins> func (ds *dockerService) performPlatformSpecificContainerForContainer(containerID string) (errors []error) { </ins> if cleanupInfo, present := ds.containerCleanupInfos[containerID]; present { <del> ds.performPlatformSpecificContainerCleanupAndLogErrors(containerID, cleanupInfo) delete(ds.containerCleanupInfos, containerID) </del> <ins> errors = ds.performPlatformSpecificContainerCleanupAndLogErrors(containerID, cleanupInfo) if len(errors) == 0 { delete(ds.containerCleanupInfos, containerID) } </ins> } <ins> return </ins> } <del> func (ds *dockerService) performPlatformSpecificContainerCleanupAndLogErrors(containerNameOrID string, cleanupInfo *containerCleanupInfo) { </del> <ins> func (ds *dockerService) performPlatformSpecificContainerCleanupAndLogErrors(containerNameOrID string, cleanupInfo *containerCleanupInfo) []error { </ins> if cleanupInfo == nil { <del> return </del> <ins> return nil </ins> } <del> for _, err := range ds.performPlatformSpecificContainerCleanup(cleanupInfo) { </del> <ins> errors := ds.performPlatformSpecificContainerCleanup(cleanupInfo) for _, err := range errors { </ins> klog.Warningf(\"error when cleaning up after container %q: %v\", containerNameOrID, err) } <ins> return errors </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-486ca0159276eedd0d2aa336961ee5fd6fb83d0ac97af7f3f9c8c863d43fcef2", "text": "What would you like to be : Periodically remove cleanupInfos for old containers from dockershim's map. One way of doing that would be to just forget about s older than say an hour, as they should always be short-lived. Why is this needed: introduced a new in-memory map for the dockershim, that could potentially (in pathological cases) cause memory leaks - for containers that use GMSA cred specs, get created successfully, but then never get started nor removed. This might be okay for the alpha release of the GMSA feature, but should be addressed in the beta. See\n/assign wk8\n/sig windows\n/milestone v1.15\ngot moved out. let's move this issue with it as well /milestone v1.16\nHello! I'm bug triage lead for the 1.16 release cycle and considering this issue is tagged for 1.16, but not updated for a long time, I'd like to check its status. The code freeze is starting on August 29th (about 1.5 weeks from now), which means that there should be a PR ready (and merged) until then. Do we still target this issue to be fixed for 1.16?\n: yup we'd love to have this in 1.16, still waiting for kind reviewers on :) ...", "commid": "kubernetes_issue_74843", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dd8eced9382bd29d829109773c71911682a7fdad7c6fa8d5156b31f015d5db32", "query": "import ( \"fmt\" \"net\" <ins> \"runtime\" </ins> \"github.com/golang/glog\"", "positive_passages": [{"docid": "doc-en-kubernetes-295b16ebdca2097490863d761fa466b150fe770891272091eba588ee367ef882", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: I have tried FlexVolume on a Windows node, it does not work. I am now working on this feature now. Below is the FlexVolume initialization error What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.7.7 Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: /sig windows /assign\nDetailed steps about how to use flexvolume on Windows with this PR:\ncc:", "commid": "kubernetes_issue_56875", "tokennum": 183}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dd9c4e0febff1cd8dea8e5491a720a3588521526ffa9fd12d4047f9722e82620", "query": "# define the IP range used for flannel overlay network, should not conflict with above SERVICE_CLUSTER_IP_RANGE export FLANNEL_NET=${FLANNEL_NET:-172.16.0.0/16} <ins> # Optionally add other contents to the Flannel configuration JSON # object normally stored in etcd as /coreos.com/network/config.  Use # JSON syntax suitable for insertion into a JSON object constructor # after other field name:value pairs.  For example: # FLANNEL_OTHER_NET_CONFIG=', \"SubnetMin\": \"172.16.10.0\", \"SubnetMax\": \"172.16.90.0\"' export FLANNEL_OTHER_NET_CONFIG FLANNEL_OTHER_NET_CONFIG='' </ins> # Admission Controllers to invoke prior to persisting objects in cluster export ADMISSION_CONTROL=NamespaceLifecycle,LimitRanger,ServiceAccount,ResourceQuota,SecurityContextDeny", "positive_passages": [{"docid": "doc-en-kubernetes-3bb3543c0323a70faea91ccc43a3eaf950d3e30c811cd93e021b94a126351841", "text": "and provide for configuring Flannel's parameter but none of the others listed in", "commid": "kubernetes_issue_19618", "tokennum": 20}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dddd83cb4a5a2e6c6aa9bb9e35e3ef2d1a50a8d9a998862e704d7ff01377df6c", "query": "return nil } <del> // DeleteTCPLoadBalancer is an implementation of TCPLoadBalancer.DeleteTCPLoadBalancer. func (gce *GCECloud) DeleteTCPLoadBalancer(name, region string) error { </del> <ins> // EnsureTCPLoadBalancerDeleted is an implementation of TCPLoadBalancer.EnsureTCPLoadBalancerDeleted. func (gce *GCECloud) EnsureTCPLoadBalancerDeleted(name, region string) error { </ins> op, err := gce.service.ForwardingRules.Delete(gce.projectID, region, name).Do() if err != nil && isHTTPErrorCode(err, http.StatusNotFound) { glog.Infof(\"Forwarding rule %s already deleted. Continuing to delete target pool.\", name)", "positive_passages": [{"docid": "doc-en-kubernetes-9fca6378f8b8df6d20b226b62d39deddc0dd6ba6166f0f70fb99239f64c63f5d", "text": "All of our external load balancer tests failed for the better part of a day due to the GCE project that our tests run in hitting its quota for number of target pools. While the target pools have been deleted, the fact that we hit our quota indicates that there must be a leak somewhere, and we need to plug it.\nFor reference, the previous issue was\nCould the leakage be related to ? The quota exhaustion occurred about 22 hrs after that.\nI'd guess that this is due to GetTCPLoadBalancer returning that the load balancer doesn't exist if the forwarding rule is gone, ignoring the target pool, while the service controller considers its deleting done if the cloud provider says that the load balancer doesn't exist. I that logic to the cloud provider because the other implementations of DeleteTCPLoadBalancer weren't/won't be idempotent in the sense of returning ok if the LB doesn't exist. To fix it, we'll either need to make sure all Delete implementations are idempotent and remove the Get call in the controller, or add a method along the lines of IsTCPLoadBalancerDeleted to ask the cloud provider whether all pieces of it have been completely cleaned up. We can't make GetTCPLoadBalancer check that because it's relied on to tell us whether or not the balancer is fully created.\nCopying over my commentary from on why the GKE e2e tests are leaking so many forwarding rules and target pools vs the GCE tests:\nIs there a way for the services test to wait for the service controller to clean up the external resources before finishing (without just doing a sleep)?\nNot without polling GCE directly for whether the resources still exist, although that may be worth it as a workaround. What would be perfect is that clean-up-all-cloud-provider-resources API method that we talked about a couple months ago.\nCan we not perhaps use GCE namespaces or projects as a cheap way of getting this here?\nI don't believe so. We can't use projects due to the fact that projects can't be programatically created (they're intended to be long-lived). I'm not aware of anything along the lines of a GCE namespace other than networks, which won't work because target pools and forwarding rules unfortunately don't seem to be scoped to networks.", "commid": "kubernetes_issue_7753", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dddd83cb4a5a2e6c6aa9bb9e35e3ef2d1a50a8d9a998862e704d7ff01377df6c", "query": "return nil } <del> // DeleteTCPLoadBalancer is an implementation of TCPLoadBalancer.DeleteTCPLoadBalancer. func (gce *GCECloud) DeleteTCPLoadBalancer(name, region string) error { </del> <ins> // EnsureTCPLoadBalancerDeleted is an implementation of TCPLoadBalancer.EnsureTCPLoadBalancerDeleted. func (gce *GCECloud) EnsureTCPLoadBalancerDeleted(name, region string) error { </ins> op, err := gce.service.ForwardingRules.Delete(gce.projectID, region, name).Do() if err != nil && isHTTPErrorCode(err, http.StatusNotFound) { glog.Infof(\"Forwarding rule %s already deleted. Continuing to delete target pool.\", name)", "positive_passages": [{"docid": "doc-en-kubernetes-d79b213781c20847fbb47c058c0afaba60ed2f1d9f5b51e77a0a4cda944c52e0", "text": "The target pool leak in the code might be fixed, but the forwarding rule + target pool leak from deleting GKE clusters too quickly is certainly still happening. Reopening for the sake of that half of the issue.\nCan we just add a short sleep to jenkins after the last test has run before it deletes anything?\nYes, you could add a sleep to Ginkgo's AfterEachSuite(): But I'd be concerned about what the upper bound on the sleep period is. Can we get the tests and code in sync with a 1 minute latency here? (e.g. if the controller garbage collects every 60 seconds, then the test only needs to sleep for 60 sec?) And add a BEEG comment to the test's sleep config noting that increasing the sleep time will not improve things, otherwise I'm pretty sure that someone noting flakes in this test in future will think \"maybe I should just increase the sleep period a little bit.\"\nActually, thinking about this a little more, it would be better to put the \"sleep\" logic in the k8s master teardown procedure (i.e. not in the e2e tests or in Jenkins), because otherwise users are going to run into the same resource leakage problems as we are. So master deletion blocks on cleanup of backend cloud resources.\nThere's no way to block master deletion from the master itself. The test framework (or user) just pulls the rug out from underneath the master. See\nRobby's right -- is the real solution to this, but until we have that the best we can do is to have the wait happen elsewhere. The options seem to be: GKE itself Ginkgo's post-testing logic Jenkins' teardown logic I don't like putting it in GKE, because arbitrarily slowing down our API makes for a poor experience for the majority of people that don't still have resources being deleted. I'm not eager to put it in Gingko either, since won't that sleep also take effect whenever anyone runs an e2e test locally against a dev cluster? Putting it in the Jenkins logic makes the most sense to me. I'll send a PR and cc you.\nWe may also want to change the kube-down logic to bring down the master and then nodes in parallel to both speed it up and more closely resemble GKE's teardown logic.\nI've deleted the old forwarding rules and target pools from the project.", "commid": "kubernetes_issue_7753", "tokennum": 530}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dddd83cb4a5a2e6c6aa9bb9e35e3ef2d1a50a8d9a998862e704d7ff01377df6c", "query": "return nil } <del> // DeleteTCPLoadBalancer is an implementation of TCPLoadBalancer.DeleteTCPLoadBalancer. func (gce *GCECloud) DeleteTCPLoadBalancer(name, region string) error { </del> <ins> // EnsureTCPLoadBalancerDeleted is an implementation of TCPLoadBalancer.EnsureTCPLoadBalancerDeleted. func (gce *GCECloud) EnsureTCPLoadBalancerDeleted(name, region string) error { </ins> op, err := gce.service.ForwardingRules.Delete(gce.projectID, region, name).Do() if err != nil && isHTTPErrorCode(err, http.StatusNotFound) { glog.Infof(\"Forwarding rule %s already deleted. Continuing to delete target pool.\", name)", "positive_passages": [{"docid": "doc-en-kubernetes-6b81898435dc239c0c98669b4836ce5b1423be788127f142aa9eb15c198137cf", "text": "I'll periodically check to see whether anything is leaked after this point. I apologize if the deletions affected any running tests - everything looked to only be from GKE and parallel e2e runs.", "commid": "kubernetes_issue_7753", "tokennum": 42}], "negative_passages": []}
{"query_id": "q-en-kubernetes-de2cc5fe883ffb7cd72bcdfb43583341e6508f9c64d6bc4331dfab9eb02f8485", "query": "MounterSetUpTests(t, false) }) } <ins> func TestMounterSetUpWithFSGroup(t *testing.T) { fakeClient := fakeclient.NewSimpleClientset() plug, tmpDir := newTestPlugin(t, fakeClient, nil) defer os.RemoveAll(tmpDir) testCases := []struct { name        string accessModes []api.PersistentVolumeAccessMode readOnly    bool fsType      string setFsGroup  bool fsGroup     int64 }{ { name: \"default fstype, with no fsgroup (should not apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteOnce, }, readOnly: false, fsType:   \"\", }, { name: \"default fstype  with fsgroup (should not apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteOnce, }, readOnly:   false, fsType:     \"\", setFsGroup: true, fsGroup:    3000, }, { name: \"fstype, fsgroup, RWM, ROM provided (should not apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteMany, api.ReadOnlyMany, }, fsType:     \"ext4\", setFsGroup: true, fsGroup:    3000, }, { name: \"fstype, fsgroup, RWO, but readOnly (should not apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteOnce, }, readOnly:   true, fsType:     \"ext4\", setFsGroup: true, fsGroup:    3000, }, { name: \"fstype, fsgroup, RWO provided (should apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteOnce, }, fsType:     \"ext4\", setFsGroup: true, fsGroup:    3000, }, } for i, tc := range testCases { t.Logf(\"Running test %s\", tc.name) volName := fmt.Sprintf(\"test-vol-%d\", i) pv := makeTestPV(\"test-pv\", 10, testDriver, volName) pv.Spec.AccessModes = tc.accessModes pvName := pv.GetName() spec := volume.NewSpecFromPersistentVolume(pv, tc.readOnly) if tc.fsType != \"\" { spec.PersistentVolume.Spec.CSI.FSType = tc.fsType } mounter, err := plug.NewMounter( spec, &api.Pod{ObjectMeta: meta.ObjectMeta{UID: testPodUID, Namespace: testns}}, volume.VolumeOptions{}, ) if err != nil { t.Fatalf(\"Failed to make a new Mounter: %v\", err) } if mounter == nil { t.Fatal(\"failed to create CSI mounter\") } csiMounter := mounter.(*csiMountMgr) csiMounter.csiClient = setupClient(t, true) attachID := getAttachmentName(csiMounter.volumeID, csiMounter.driverName, string(plug.host.GetNodeName())) attachment := makeTestAttachment(attachID, \"test-node\", pvName) _, err = csiMounter.k8s.StorageV1beta1().VolumeAttachments().Create(attachment) if err != nil { t.Errorf(\"failed to setup VolumeAttachment: %v\", err) continue } // Mounter.SetUp() var fsGroupPtr *int64 if tc.setFsGroup { fsGroup := tc.fsGroup fsGroupPtr = &fsGroup } if err := csiMounter.SetUp(fsGroupPtr); err != nil { t.Fatalf(\"mounter.Setup failed: %v\", err) } //Test the default value of file system type is not overridden if len(csiMounter.spec.PersistentVolume.Spec.CSI.FSType) != len(tc.fsType) { t.Errorf(\"file system type was overridden by type %s\", csiMounter.spec.PersistentVolume.Spec.CSI.FSType) } // ensure call went all the way pubs := csiMounter.csiClient.(*fakeCsiDriverClient).nodeClient.GetNodePublishedVolumes() if pubs[csiMounter.volumeID].Path != csiMounter.GetPath() { t.Error(\"csi server may not have received NodePublishVolume call\") } } } </ins> func TestUnmounterTeardown(t *testing.T) { plug, tmpDir := newTestPlugin(t, nil, nil)", "positive_passages": [{"docid": "doc-en-kubernetes-91422af253157e56510335693740251e17b7c26d119e77363e85ed4155980546", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: What happened: fsgroup is only intended for RWO volumes because it recursively changes the permissions of all the directories in the volume. This can cause problems for nfs-type volumes because multiple pods could access the same volume and have the permissions changed out from underneath. What you expected to happen: Determine whether or not the plugin supports fsgroup either via: access mode. This is still a bit ambiguous for nfs volume types, that can theoretically support rwo, especially since Kubernetes does not do any sort of access mode enforcement. a new csi capability\nCC\nAre you saying that CSI internal driver should check driver capability for RWO, if supported, only then apply value ? What would the be ?\nYes one possible way is to infer fsgroup is supported for all rwo volumes, which may not be true? Like a nfs volume technically supports rwo but not fsgroup. So the other option is to make it a new CSI capability. I'm not sure exactly sure how best to describe it though, maybe something about volume ownership management.\nWill it work if is not set then don't chown the ownership? I would think that for shared file system types(nfs, glusterfs) - won't be set. For raw block storage too - I think we shouldn't have to do this.\nwhat do you mean by ? Shouldnt have to solve this issue ?\nI meant - which is obvious. I just meant that the entire mechanism of changing ownership of files should apply only to volume types with block storage filesystems. I am just wondering if we can get away with detecting fsType and not have to introduce new capability in CSI.\nagreed, do not map well to current csi.Capabilities enums which makes it hard to determine RWO when mounting. Perhaps, instead of a new capability, we revisit the existing capabilities to see if there are any way RWO can be reliably inferred from returned capabilities.", "commid": "kubernetes_issue_66323", "tokennum": 463}], "negative_passages": []}
{"query_id": "q-en-kubernetes-de2cc5fe883ffb7cd72bcdfb43583341e6508f9c64d6bc4331dfab9eb02f8485", "query": "MounterSetUpTests(t, false) }) } <ins> func TestMounterSetUpWithFSGroup(t *testing.T) { fakeClient := fakeclient.NewSimpleClientset() plug, tmpDir := newTestPlugin(t, fakeClient, nil) defer os.RemoveAll(tmpDir) testCases := []struct { name        string accessModes []api.PersistentVolumeAccessMode readOnly    bool fsType      string setFsGroup  bool fsGroup     int64 }{ { name: \"default fstype, with no fsgroup (should not apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteOnce, }, readOnly: false, fsType:   \"\", }, { name: \"default fstype  with fsgroup (should not apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteOnce, }, readOnly:   false, fsType:     \"\", setFsGroup: true, fsGroup:    3000, }, { name: \"fstype, fsgroup, RWM, ROM provided (should not apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteMany, api.ReadOnlyMany, }, fsType:     \"ext4\", setFsGroup: true, fsGroup:    3000, }, { name: \"fstype, fsgroup, RWO, but readOnly (should not apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteOnce, }, readOnly:   true, fsType:     \"ext4\", setFsGroup: true, fsGroup:    3000, }, { name: \"fstype, fsgroup, RWO provided (should apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteOnce, }, fsType:     \"ext4\", setFsGroup: true, fsGroup:    3000, }, } for i, tc := range testCases { t.Logf(\"Running test %s\", tc.name) volName := fmt.Sprintf(\"test-vol-%d\", i) pv := makeTestPV(\"test-pv\", 10, testDriver, volName) pv.Spec.AccessModes = tc.accessModes pvName := pv.GetName() spec := volume.NewSpecFromPersistentVolume(pv, tc.readOnly) if tc.fsType != \"\" { spec.PersistentVolume.Spec.CSI.FSType = tc.fsType } mounter, err := plug.NewMounter( spec, &api.Pod{ObjectMeta: meta.ObjectMeta{UID: testPodUID, Namespace: testns}}, volume.VolumeOptions{}, ) if err != nil { t.Fatalf(\"Failed to make a new Mounter: %v\", err) } if mounter == nil { t.Fatal(\"failed to create CSI mounter\") } csiMounter := mounter.(*csiMountMgr) csiMounter.csiClient = setupClient(t, true) attachID := getAttachmentName(csiMounter.volumeID, csiMounter.driverName, string(plug.host.GetNodeName())) attachment := makeTestAttachment(attachID, \"test-node\", pvName) _, err = csiMounter.k8s.StorageV1beta1().VolumeAttachments().Create(attachment) if err != nil { t.Errorf(\"failed to setup VolumeAttachment: %v\", err) continue } // Mounter.SetUp() var fsGroupPtr *int64 if tc.setFsGroup { fsGroup := tc.fsGroup fsGroupPtr = &fsGroup } if err := csiMounter.SetUp(fsGroupPtr); err != nil { t.Fatalf(\"mounter.Setup failed: %v\", err) } //Test the default value of file system type is not overridden if len(csiMounter.spec.PersistentVolume.Spec.CSI.FSType) != len(tc.fsType) { t.Errorf(\"file system type was overridden by type %s\", csiMounter.spec.PersistentVolume.Spec.CSI.FSType) } // ensure call went all the way pubs := csiMounter.csiClient.(*fakeCsiDriverClient).nodeClient.GetNodePublishedVolumes() if pubs[csiMounter.volumeID].Path != csiMounter.GetPath() { t.Error(\"csi server may not have received NodePublishVolume call\") } } } </ins> func TestUnmounterTeardown(t *testing.T) { plug, tmpDir := newTestPlugin(t, nil, nil)", "positive_passages": [{"docid": "doc-en-kubernetes-e4259f265013a5d1d3262148ae5650fa802161db5ab8c8ccc1d210e68217a7fd", "text": "Currently, this is what the code is doing which we knew needed to be revisited:\nUsers may not fully understand what fsgroup is and set it anyway, or a default psp with some fsgroup may be defined in which it will automatically be set on all pods. The first case we can attribute to user error, but the second case may not have a good workaround and could cause permission issues on rwx volumes. So I think we do need to solve this.\nYes, agreed this has to be solved. As you pointed out user error or improperly configured PSP can set value that does not match the correct attribute, causing permission issues. Here is what I think can be done without new CSI capabilities: , then do not apply fsgroup then: , apply fsgroup , do not apply fsgroup to void stated issue then: , apply fsgroup I think that may help deduce when to apply fsgroup.\nIf mount reference count <= 1, apply fsgroup If mount reference count 1, do not apply fsgroup to void stated issue A RWM volume (say NFS) can be mounted on multiple nodes. Do you have reliable count of mounts across all nodes?\nIn addition, that would be a change in semantics to how we support rwx volumes today. If we don't have a new CSI capability, then I think the best course of action is to only apply fsgroup for RWO volumes. Some questions remain: Do all RWO volumes support fsgroup? RWX is a superset of RWO. So if a user requests a RWO volume, it could still be satisfied by a RWX volume type. Can we detect this and still not apply the fsgroup even though the volume capability will say RWO?\nIf there's not a reliable way to enumerate node mounts (thinking about it, for CSI external drivers, the answer is NO). Theres is no reliable way to have k8s autocorrect a bad fsgroup/PV.AccessMode combo. So we would have to rely on the config provided by user/admin. I have come to similar conclusion as -- mainly, apply fsgroup only to volumes with access modes. The other k8s specified access modes, , cannot be reliably applied.", "commid": "kubernetes_issue_66323", "tokennum": 487}], "negative_passages": []}
{"query_id": "q-en-kubernetes-de2cc5fe883ffb7cd72bcdfb43583341e6508f9c64d6bc4331dfab9eb02f8485", "query": "MounterSetUpTests(t, false) }) } <ins> func TestMounterSetUpWithFSGroup(t *testing.T) { fakeClient := fakeclient.NewSimpleClientset() plug, tmpDir := newTestPlugin(t, fakeClient, nil) defer os.RemoveAll(tmpDir) testCases := []struct { name        string accessModes []api.PersistentVolumeAccessMode readOnly    bool fsType      string setFsGroup  bool fsGroup     int64 }{ { name: \"default fstype, with no fsgroup (should not apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteOnce, }, readOnly: false, fsType:   \"\", }, { name: \"default fstype  with fsgroup (should not apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteOnce, }, readOnly:   false, fsType:     \"\", setFsGroup: true, fsGroup:    3000, }, { name: \"fstype, fsgroup, RWM, ROM provided (should not apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteMany, api.ReadOnlyMany, }, fsType:     \"ext4\", setFsGroup: true, fsGroup:    3000, }, { name: \"fstype, fsgroup, RWO, but readOnly (should not apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteOnce, }, readOnly:   true, fsType:     \"ext4\", setFsGroup: true, fsGroup:    3000, }, { name: \"fstype, fsgroup, RWO provided (should apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteOnce, }, fsType:     \"ext4\", setFsGroup: true, fsGroup:    3000, }, } for i, tc := range testCases { t.Logf(\"Running test %s\", tc.name) volName := fmt.Sprintf(\"test-vol-%d\", i) pv := makeTestPV(\"test-pv\", 10, testDriver, volName) pv.Spec.AccessModes = tc.accessModes pvName := pv.GetName() spec := volume.NewSpecFromPersistentVolume(pv, tc.readOnly) if tc.fsType != \"\" { spec.PersistentVolume.Spec.CSI.FSType = tc.fsType } mounter, err := plug.NewMounter( spec, &api.Pod{ObjectMeta: meta.ObjectMeta{UID: testPodUID, Namespace: testns}}, volume.VolumeOptions{}, ) if err != nil { t.Fatalf(\"Failed to make a new Mounter: %v\", err) } if mounter == nil { t.Fatal(\"failed to create CSI mounter\") } csiMounter := mounter.(*csiMountMgr) csiMounter.csiClient = setupClient(t, true) attachID := getAttachmentName(csiMounter.volumeID, csiMounter.driverName, string(plug.host.GetNodeName())) attachment := makeTestAttachment(attachID, \"test-node\", pvName) _, err = csiMounter.k8s.StorageV1beta1().VolumeAttachments().Create(attachment) if err != nil { t.Errorf(\"failed to setup VolumeAttachment: %v\", err) continue } // Mounter.SetUp() var fsGroupPtr *int64 if tc.setFsGroup { fsGroup := tc.fsGroup fsGroupPtr = &fsGroup } if err := csiMounter.SetUp(fsGroupPtr); err != nil { t.Fatalf(\"mounter.Setup failed: %v\", err) } //Test the default value of file system type is not overridden if len(csiMounter.spec.PersistentVolume.Spec.CSI.FSType) != len(tc.fsType) { t.Errorf(\"file system type was overridden by type %s\", csiMounter.spec.PersistentVolume.Spec.CSI.FSType) } // ensure call went all the way pubs := csiMounter.csiClient.(*fakeCsiDriverClient).nodeClient.GetNodePublishedVolumes() if pubs[csiMounter.volumeID].Path != csiMounter.GetPath() { t.Error(\"csi server may not have received NodePublishVolume call\") } } } </ins> func TestUnmounterTeardown(t *testing.T) { plug, tmpDir := newTestPlugin(t, nil, nil)", "positive_passages": [{"docid": "doc-en-kubernetes-d8c35fcb948670df81783d48737c49dba78eee3bd98e80f83b95ce53a92518be", "text": "Even if we were to introduce additional plugin capabilities that the CO can query (from driver) to find out what modes can be applied, there would still be the possibility of user/admin mis-configuration. Probably not, Is this where you think an additional capability would help ( ) That is a good point. Can't think of a way to detect/guess RWX when RWO is specified, this without the driver providing that info. Can we adopt the rule until we decide what capabilities would look like ?\nI will just try to summarize the conversation from Slack. We can safely assume that only applies to block storage type with file system on top of it. So for all - volumes that need to have called MUST have a file system() on them. Is that assumption correct? If it is - can we not use presence of field or we can query the local volume for fs type (like how we query selinux relabelling capability) and call only when - volume is RW and has a valid block storage file system type. Will this not solve our use case? EDIT: renamed to .\nWe'll need to make it clear that is only for block-based storage systems, and the field cannot be reused for some multi-protocol file server (ie, nfsv3, nfsv4, smb, etc). For that case, then the plugin will need to expose its own new storageclass parameter + volume attribute to specify protocol.\nCan we not use to get fsType - and use that information for calling ? It may be problematic to rely entirely on present inside csi source.\nthe only problem with is that in CSI volume info is intentionally opaque to the CSI code inside k8s. All mount logic is delegated to the driver.\nInstead of a new capability or trying to deduce how best to apply fsgroup, why not pass the to the driver and let it decide how to apply it (either as a attribute for the mount or top level request param)? Right now, all mount logic has been delegated to the external CSI driver except for applying permission. Thoughts ?\nthat is true but we can still inspect file system on the mounted path because by the time gets called volume is already mounted. This should be no different than how selinux support is determined. what you think?\nis this approved for 1.12 milestone? Thank you for working on this,\nstill discussing how best to approach this.", "commid": "kubernetes_issue_66323", "tokennum": 506}], "negative_passages": []}
{"query_id": "q-en-kubernetes-de2cc5fe883ffb7cd72bcdfb43583341e6508f9c64d6bc4331dfab9eb02f8485", "query": "MounterSetUpTests(t, false) }) } <ins> func TestMounterSetUpWithFSGroup(t *testing.T) { fakeClient := fakeclient.NewSimpleClientset() plug, tmpDir := newTestPlugin(t, fakeClient, nil) defer os.RemoveAll(tmpDir) testCases := []struct { name        string accessModes []api.PersistentVolumeAccessMode readOnly    bool fsType      string setFsGroup  bool fsGroup     int64 }{ { name: \"default fstype, with no fsgroup (should not apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteOnce, }, readOnly: false, fsType:   \"\", }, { name: \"default fstype  with fsgroup (should not apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteOnce, }, readOnly:   false, fsType:     \"\", setFsGroup: true, fsGroup:    3000, }, { name: \"fstype, fsgroup, RWM, ROM provided (should not apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteMany, api.ReadOnlyMany, }, fsType:     \"ext4\", setFsGroup: true, fsGroup:    3000, }, { name: \"fstype, fsgroup, RWO, but readOnly (should not apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteOnce, }, readOnly:   true, fsType:     \"ext4\", setFsGroup: true, fsGroup:    3000, }, { name: \"fstype, fsgroup, RWO provided (should apply fsgroup)\", accessModes: []api.PersistentVolumeAccessMode{ api.ReadWriteOnce, }, fsType:     \"ext4\", setFsGroup: true, fsGroup:    3000, }, } for i, tc := range testCases { t.Logf(\"Running test %s\", tc.name) volName := fmt.Sprintf(\"test-vol-%d\", i) pv := makeTestPV(\"test-pv\", 10, testDriver, volName) pv.Spec.AccessModes = tc.accessModes pvName := pv.GetName() spec := volume.NewSpecFromPersistentVolume(pv, tc.readOnly) if tc.fsType != \"\" { spec.PersistentVolume.Spec.CSI.FSType = tc.fsType } mounter, err := plug.NewMounter( spec, &api.Pod{ObjectMeta: meta.ObjectMeta{UID: testPodUID, Namespace: testns}}, volume.VolumeOptions{}, ) if err != nil { t.Fatalf(\"Failed to make a new Mounter: %v\", err) } if mounter == nil { t.Fatal(\"failed to create CSI mounter\") } csiMounter := mounter.(*csiMountMgr) csiMounter.csiClient = setupClient(t, true) attachID := getAttachmentName(csiMounter.volumeID, csiMounter.driverName, string(plug.host.GetNodeName())) attachment := makeTestAttachment(attachID, \"test-node\", pvName) _, err = csiMounter.k8s.StorageV1beta1().VolumeAttachments().Create(attachment) if err != nil { t.Errorf(\"failed to setup VolumeAttachment: %v\", err) continue } // Mounter.SetUp() var fsGroupPtr *int64 if tc.setFsGroup { fsGroup := tc.fsGroup fsGroupPtr = &fsGroup } if err := csiMounter.SetUp(fsGroupPtr); err != nil { t.Fatalf(\"mounter.Setup failed: %v\", err) } //Test the default value of file system type is not overridden if len(csiMounter.spec.PersistentVolume.Spec.CSI.FSType) != len(tc.fsType) { t.Errorf(\"file system type was overridden by type %s\", csiMounter.spec.PersistentVolume.Spec.CSI.FSType) } // ensure call went all the way pubs := csiMounter.csiClient.(*fakeCsiDriverClient).nodeClient.GetNodePublishedVolumes() if pubs[csiMounter.volumeID].Path != csiMounter.GetPath() { t.Error(\"csi server may not have received NodePublishVolume call\") } } } </ins> func TestUnmounterTeardown(t *testing.T) { plug, tmpDir := newTestPlugin(t, nil, nil)", "positive_passages": [{"docid": "doc-en-kubernetes-5cbdf2214fb613203f89164533ba44fdfe78b2afafa2ed81aceb81e111086f6f", "text": "It would be a 1.12.\n[MILESTONENOTIFIER] Milestone Issue: Up-to-date for process <details open<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Never automatically move issue out of a release milestone; continually escalate to contributor and SIG through all available channels. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details\nApproved for 1.12\nBased on previous post, this is a summary: If then is not applied (because it could be an indication of a nonblock fs, or error) Done is provided if fstype is invalid Done if fstype is valid and then apply fsgroup logic else ignore fsGroup Done\n- any updates on ?\nWaiting for a review and approval.\nyou have a outstanding comment on the PR. Can you please answer that?\nHow does this approach relate to inline CSI volumes? There's no PersistentVolume involved, and hence no way to specify an access mode. , but my driver ignores it (always using tmpfs). I considered having my CSI driver read the mounting pod's spec to see if it has a security context with \"fsGroup\" set, since that detail is not supplied to the driver, as . My goal is to have the volume mounted with the files on it readable by the container's user, but there's no way for my driver to know who that user will be. Am I supposed to just use 0444 for the ownership bits, to allow everyone to read the files?", "commid": "kubernetes_issue_66323", "tokennum": 377}], "negative_passages": []}
{"query_id": "q-en-kubernetes-de59224eef555b9584eb25868db5ea53a7ca7ac8d6b61452810bb9f1faff5388", "query": "package events <del> import ( \"k8s.io/api/core/v1\" clientv1 \"k8s.io/api/core/v1\" ) </del> const ( // Container event reason list CreatedContainer        = \"Created\"", "positive_passages": [{"docid": "doc-en-kubernetes-b0087f3d33811f5a8bf21a1757c4fff7aaef7add29731940c9c3bd61ec9b29c4", "text": "Is this a BUG REPORT or FEATURE REQUEST?: What happened: Now the and has been consistent in by PR . There is no need to convert v1.ObjectReference to clientv1.ObjectReference in . What you expected to happen: Remove this function and cleanup the codes which call this function. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?:\nThere are no sig labels on this issue. Please by:<br(1) mentioning a sig: <bre.g., for API Machinery<br(2) specifying the label manually: <bre.g., for sig/scalability<br<brNote: method (1) will trigger a notification to the team. You can find the team list and label list\nWill submit the cleanup after PR merged.\n/sig api-machinery\n/sub", "commid": "kubernetes_issue_48747", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-de8d6d9c1d9b90b6e993e46abac3f822735c0c750a96d81da55ca35250199752", "query": "gomega.Expect(stdout).To(gomega.Equal(mountName), msg) } else { // We *expect* cat to return error here <del> gomega.Expect(err).To(gomega.HaveOccurred(), msg) </del> <ins> framework.ExpectError(err, msg) </ins> } } }", "positive_passages": [{"docid": "doc-en-kubernetes-c082543f1889f90c5ee780d309eeb8f41ee57a7e9e8bb6b6fe7c2e4381ff48af", "text": "What happened: After fixing golint failures under (now still in progress), we need to put for each and . Then common error checking code has become like: We can replace this code with which is more readable and easy to be understood what the code does. Now we have following e2e test directories which can be replaced: [x] test/e2e/apimachinery/ () [x] test/e2e/apps/ () [x] test/e2e/auth/ () [x] test/e2e/common/ () [x] test/e2e/node/ () [x] test/e2e/storage/ () [x] () [x] () [x] () [x] () [x] () [x] () [x] [x] test/e2e/storage/persistentvolumes- [x] () [x] () [x] [x] [x] [x] [x] ()\n/sig testing /kind cleanup\n/assign PR will be submitted soon.\nFix the following in\nFix in\nFix in\nHi, maybe I could take files beneath test/e2e/storage/vsphere/\noops, I'm finished and prepare for PR.\nThank you That's OK\nFix the following in\n/assign\nAll related PRs were merged. I think this ticket can be closed. BTW, should we also replace to ?\nThanks for your work. thing is managed with We are almost finishing the work also :-)\n/remove-kind bug\nI found in these files. I'm working on :\nI can work to the following item.", "commid": "kubernetes_issue_77706", "tokennum": 363}], "negative_passages": []}
{"query_id": "q-en-kubernetes-de95e02fcebb2a6f9e6844e7952fec351e08f44a131a5ccbae32acdde974dd0a", "query": "package net import ( <ins> \"crypto/tls\" </ins> \"net\" \"net/http\" \"net/url\" \"os\" \"reflect\" \"testing\" <ins> \"k8s.io/kubernetes/pkg/util/sets\" </ins> ) <ins> func TestCloneTLSConfig(t *testing.T) { expected := sets.NewString( // These fields are copied in CloneTLSConfig \"Rand\", \"Time\", \"Certificates\", \"RootCAs\", \"NextProtos\", \"ServerName\", \"InsecureSkipVerify\", \"CipherSuites\", \"PreferServerCipherSuites\", \"MinVersion\", \"MaxVersion\", \"CurvePreferences\", \"NameToCertificate\", \"GetCertificate\", \"ClientAuth\", \"ClientCAs\", \"ClientSessionCache\", // These fields are not copied \"SessionTicketsDisabled\", \"SessionTicketKey\", // These fields are unexported \"serverInitOnce\", \"mutex\", \"sessionTicketKeys\", ) fields := sets.NewString() structType := reflect.TypeOf(tls.Config{}) for i := 0; i < structType.NumField(); i++ { fields.Insert(structType.Field(i).Name) } if missing := expected.Difference(fields); len(missing) > 0 { t.Errorf(\"Expected fields that were not seen in http.Transport: %v\", missing.List()) } if extra := fields.Difference(expected); len(extra) > 0 { t.Errorf(\"New fields seen in http.Transport: %vnAdd to CopyClientTLSConfig if client-relevant, then add to expected list in TestCopyClientTLSConfig\", extra.List()) } } </ins> func TestGetClientIP(t *testing.T) { ipString := \"10.0.0.1\" ip := net.ParseIP(ipString)", "positive_passages": [{"docid": "doc-en-kubernetes-01f8727bc339d7af9aee90f0167a90af1aad001fdd8330c2abd8f77d4ae97abe", "text": "When the master dials nodes, it is mutating the tlsConfig held by the master kubelet client, to add a server name. That means if two different nodes are dialed from a master started with , x509 verification will fail for the second one. Introduced in\nthis is a regression from 1.3 and breaks pod logs/exec/attach and node proxying on installations that use\nWe probably need to review that PR and look to see if any other deliberate copies were flagged incorrectly by govet.\nInstallations that depend on secure trust from externally provided kubelet server certs are the highest security rings. If we don't fix this we need to tell anyone using this flag not to upgrade until we release 1.4.1.\nthe rest of the changes in the govet cleanup PR looked fine to me. fix for this issue is in\nSince we are telling folks they have to upgrade to kubectl 1.4.0 for rollingupdate to work it would definitely be a confusing message to say other folks should not upgrade to 1.4.0 at all.\nIf the fix is merged into master by this afternoon, lets discuss whether or not we should cherrypick it - e.g. risks involved, how we can manually qa to verify nothing else was broken, etc.\nRisk involved: If you are using a secure cluster (defined as ensuring no one can MITM your nodes and masters) and you upgrade to 1.4.0 and it does not include this fix - you are broken.\nWhat is the likelihood of interactions with other code? Is it possible this fix could introduce a breaking change to something else? Has the fix been manually verified? Are we confident that this will fully fixes the issue (vs other edge cases exist for secure clusters that this doesn't catch). Ideally I would like to see this cherrypicked into 1.4 this evening and then cut a new beta that includes it.\nNone. The single line that is currently broken was changed. The rest is a new function (with no side effects), and tests. No, it restores the original intent of the TLS config copy, and tests cover the cases we are using this with (secure, insecure, custom dialer) Yes. I swept for the same issue elsewhere and didn't find any issues. We test with a fully secured master-kubelet setup in Openshift and got a clean test run with this fix applied.\nSGTM. Thanks for fixing this.", "commid": "kubernetes_issue_33140", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dec1fce0185987f40a22102d7ff6d94b3eda1b06439c01c723a2973e4fa60f39", "query": "vmPowerStateStopped      = \"stopped\" vmPowerStateDeallocated  = \"deallocated\" vmPowerStateDeallocating = \"deallocating\" <ins> // nodeNameEnvironmentName is the environment variable name for getting node name. // It is only used for out-of-tree cloud provider. nodeNameEnvironmentName = \"NODE_NAME\" </ins> ) var (", "positive_passages": [{"docid": "doc-en-kubernetes-93c0a615d6725c12b66abb2dead01e17ca700d451119b1467d3edce68f73a013", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: If computer name prefix does not match VMSS name, then Azure cloud provider will use VMSS API instead of using metadata service data. This leads to throttling, because every affected kubelet is making API requests. What you expected to happen: Azure cloud provider should use metadata service data instead of calling VMSS API when instance is current. How to reproduce it (as minimally and precisely as possible): Set computer name prefix of the VMSS to something different than default. You should observe Azure provider making requests to the VMSS API rather than using metadata service, which leads to throttling if you have multiple kubelets with this bug. Anything else we need to know?: This is bug was introduced by - returns false even if instance is current, because it expects node name to match VMSS name + instance id, however node name is derived from the computer-name-prefix which can be different than VMSS name. Node name should be matched against , not against . Environment: Kubernetes version (use ): 1.18.x and higher Cloud provider or hardware configuration: azure /sig cloud-provider\n/sig cloud-provider\n/area provider/azure\nCC\n/remove-sig cloud-provider /sig cloud-provider (trying to remove the label)\n/sig cloud-provider\nThanks for the reporting. Unfortunately, computer name prefix is not included in IMDS, so it can't be used without VMSS API for constructing the NodeName. Would check what could we do to workaround the issue.\nCan you memorize the computer name prefix in the first request to the Azure API and then use it for the isCurrentInstance check?\nopened to fix the issue. Would you like to have a look?\nI can confirm that your change should fix the problem I reported. Do you know if your fix will be to 1.18.x?\nis working on the cherry pick\nThank you for quick fix!", "commid": "kubernetes_issue_92733", "tokennum": 464}], "negative_passages": []}
{"query_id": "q-en-kubernetes-df0f949b8b9d33d8a08078d52783944616dcfe7c17190524954a12b662e7880c", "query": "\"containers\": [ { \"name\": \"kubernetes-pause\", <del> \"image\": \"gcr.io/google_containers/pause-amd64:3.0\" </del> <ins> \"image\": \"gcr.io/google_containers/pause-amd64:3.1\" </ins> } ], \"restartPolicy\": \"Never\",", "positive_passages": [{"docid": "doc-en-kubernetes-a834f77ddd825b3d04a660aa7c11d0734893e4dcde6e0d4a7399e3b3daf56428", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: the pause-amd64:3.0 image on has an empty schema2 manifest, which prevents is from being pulled by proxy/caches which only support V2 registries. What you expected to happen: Being able to pull ` using a V2 manifest compatible client. Anything else we need to know?: The proxy/cahce is requesting this\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nAfter talking with , he mentionned the following\nAFAIK, does not support well. After inspecting the image, you can find is still using manifest v1.\n/cc FYI\nIm not sure which exact version x sch\u00e9ma X is needed. What I know is that we can download through the proxy/cache all other Kubernetes kube-system images, only the pause image is giving us trouble. Therefore, I would say that having the image available using the same format as the other kube-system images would be the request here.\nYeah, we haven't updated the pause image in a while, since it doesn't really ever change. I'm not sure whether rebuilding + pushing over the existing tag is safe, or if we should bump to or something. thoughts?\nIf we do rebuilding/updating the image, that would help and a bunch of similar issues.\nit's better/save to go with new tag\nI didn't realize there were changes to the pause binary that were never actually deployed. It seems like we should probably just do that (and bump the tag).\nthat sounds great. Any idea when the existing 3.0 tag could be pushed again?\nWe shouldn't push over the 3.0 tag; we should push a 3.1 or 4.0 tag instead. I'm not sure who owns the pause container who should drive this. Maybe sig-node and/or\nIt seems like it should be sig-node. I'll look into it.\nThe new container has been built, can you test with\nIts working! thanks! I was able to pull it through our artifactory proxy , Lee Verberne <:\nexcellent, thanks for checking. /assign", "commid": "kubernetes_issue_56253", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-df0f949b8b9d33d8a08078d52783944616dcfe7c17190524954a12b662e7880c", "query": "\"containers\": [ { \"name\": \"kubernetes-pause\", <del> \"image\": \"gcr.io/google_containers/pause-amd64:3.0\" </del> <ins> \"image\": \"gcr.io/google_containers/pause-amd64:3.1\" </ins> } ], \"restartPolicy\": \"Never\",", "positive_passages": [{"docid": "doc-en-kubernetes-7628cd26f0dafa992a4ea43a6c68b9bcdbf056fca43ee32b40ab60cef4154c17", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: pause does not reap zombie processes using the default pause container provided by What you expected to happen: should include the up to date pause code to reap zombie processes when using docker = 1.13.1 found here How to reproduce it (as minimally and precisely as possible): a.out will leave a zombie process that is not cleaned up Anything else we need to know?: Building the pause container from master solves this issue Related: Environment: Kubernetes version (use ): 1.7.0+ Cloud provider or hardware configuration**: N/A OS (e.g. from /etc/os-release): CentOS 7 Kernel (e.g. ): 4.10.13+ Install tools: Others: docker = 1.13.1\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\ni get a simliar problem when i run crond service in pod container, every day it makes some [anacron] zombie progresses UID PID PPID C STIME TTY TIME CMD root 1 0 0 Nov14 ? 00:00:00 /pause root 7 0 0 Nov14 ? 00:00:00 /usr/local/bin/dumb-init /usr/lo root 13 7 0 Nov14 ? 00:00:00 nginx: master process /usr/local nobody 21 13 0 Nov14 ? 00:00:01 nginx: worker process nobody 22 13 0 Nov14 ? 00:00:07 nginx: worker process nobody 23 13 0 Nov14 ? 00:00:07 nginx: worker process nobody 24 13 0 Nov14 ? 00:00:05 nginx: worker process root 77 1 0 Nov14 ? 00:00:00 [anacron] root 1 0 00:01 ? 00:00:00 [anacron] <defunctroot 1 0 01:01 ? 00:00:00 [anacron] <defunctroot 1 0 02:01 ?", "commid": "kubernetes_issue_50865", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-df0f949b8b9d33d8a08078d52783944616dcfe7c17190524954a12b662e7880c", "query": "\"containers\": [ { \"name\": \"kubernetes-pause\", <del> \"image\": \"gcr.io/google_containers/pause-amd64:3.0\" </del> <ins> \"image\": \"gcr.io/google_containers/pause-amd64:3.1\" </ins> } ], \"restartPolicy\": \"Never\",", "positive_passages": [{"docid": "doc-en-kubernetes-6179feaaee46a15cd909bb088c82657b9b59fba8efdee1296995076588512032", "text": "00:00:00 [anacron] <defunctroot 1 0 03:01 ? 00:00:00 [anacron] <defunctroot 0 0 11:49 ? 00:00:00 /bin/bash root 0 1 19:15 ? 00:00:00 /bin/bash root 0 19:15 ? 00:00:00 ps -ef !\nDo we know why this was never resolved / was never deployed?\nI just fought through this issue with a rabbitmq helm chart. I had to custom build a pause container from master to fix it. The rabbitmq helm chart uses for its liveness checks. It's a thin wrapper around a call to the rabbitmq-server daemon, which is not PID 1 (/pause is PID 1). The rabbitmq-server process forks some children to do the work and then they exit. Since the pause-amd64:3.0 is not reaping, those processes stick around as zombies. The liveness check runs every 5 seconds. After about 4 hours, there are about 27K zombies and the node begins failing to launch new containers because it's starved for resources. The pause container built from current master fixes that behavior, no zombies at all in the container.\nThe plan is to build a new version of pause-amd64 and then update the image referenced by Kubernetes. This means the default image will change in the next Kubernetes release. We can make the new image available once the freeze lifts and we can merge .\nLooks like this made it into 1.10", "commid": "kubernetes_issue_50865", "tokennum": 336}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dfa1f907939ed4f08b1d3a4a0f5678850ca45f6291ee7ef3472b32ac5adbf122", "query": "registry = \"k8s.gcr.io/build-image\", repository = \"debian-iptables\", # Ensure the digests above are updated to match a new tag <del> tag = \"buster-v1.4.0\",  # ignored, but kept here for documentation </del> <ins> tag = \"buster-v1.5.0\",  # ignored, but kept here for documentation </ins> ) def etcd_tarballs():", "positive_passages": [{"docid": "doc-en-kubernetes-ee0826757468ea334f95c77509b257c3d392b6713b4311ba7afa125d642dcec9", "text": "The based container images for are shipped with the wrong architecture within the manifest if not amd64: Refers to We updated the images a few minutes ago to buster-v1.3.0, which are now ready to be used as base for the multi-architecture images. If the images contain the right architectures, then it may magically happen that the kube-proxy images are fixed, too. This is because we already use the build syntax for it: /cc\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig release", "commid": "kubernetes_issue_98229", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dfb5ed9bd94e4af8913a5da3540c3da4d0ef45e7d4d72fd019147d1ccffdc9b0", "query": "if err != nil { return probe.Unknown, err } <del> if strings.ToLower(string(data)) != defaultHealthyOutput { </del> <ins> if !strings.HasPrefix(strings.ToLower(string(data)), defaultHealthyOutput) { </ins> return probe.Failure, nil } return probe.Success, nil", "positive_passages": [{"docid": "doc-en-kubernetes-65bf469670180d69e57fdc1a820a8f2f435cec685a9975e90f226dd126851fba", "text": "As far as I can tell, container liveness probes of type exec flat out don't work against clusters built at head. I had the kubelet always log the output of the exec'ed command, and it's always empty no matter what I exec, causing the probe to fail since it requires the output to be equal to the string \"ok\". If you want to test it, try adding a liveness probe of this form to any container: I also tried these lovely forms, to more closely match the liveness example under examples/: On the plus side, this may be an opportunistic time to switch over to\nThe reason that the e2e test for exec liveness probes hasn't caught this is that it only tests that containers are restarted when they fail liveness probes. It doesn't test that containers aren't restarted when their liveness checks should be succeeding. The e2e test's exec'ed commands also only ever produced empty output, rather than the expected \"fail\" output.\nIs it possible to include this in a new pre-release, since it fixes a bug in health checking? I see it merged in master and I'm wondering what the policy is of releasing new code in a separate (0.16.*) release.", "commid": "kubernetes_issue_7618", "tokennum": 275}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dfeb672942d9ae23fb77e7cd4a8b1adae09720ec2755a90e6bcad7d06f7724d5", "query": "// Otherwise we will return an error. func findSecurityGroupForInstance(instance *ec2.Instance, taggedSecurityGroups map[string]*ec2.SecurityGroup) (*ec2.GroupIdentifier, error) { instanceID := aws.StringValue(instance.InstanceId) <del> var best *ec2.GroupIdentifier </del> <ins> var tagged []*ec2.GroupIdentifier var untagged []*ec2.GroupIdentifier </ins> for _, group := range instance.SecurityGroups { groupID := aws.StringValue(group.GroupId) if groupID == \"\" { glog.Warningf(\"Ignoring security group without id for instance %q: %v\", instanceID, group) continue } <del> if best == nil { best = group continue </del> <ins> _, isTagged := taggedSecurityGroups[groupID] if isTagged { tagged = append(tagged, group) } else { untagged = append(untagged, group) </ins> } <ins> } </ins> <del> _, bestIsTagged := taggedSecurityGroups[*best.GroupId] _, groupIsTagged := taggedSecurityGroups[groupID] if bestIsTagged && !groupIsTagged { // best is still best } else if groupIsTagged && !bestIsTagged { best = group } else { // We create instances with one SG // If users create multiple SGs, they must tag one of them as being k8s owned return nil, fmt.Errorf(\"Multiple security groups found for instance (%s); ensure the k8s security group is tagged\", instanceID) </del> <ins> if len(tagged) > 0 { // We create instances with one SG // If users create multiple SGs, they must tag one of them as being k8s owned if len(tagged) != 1 { return nil, fmt.Errorf(\"Multiple tagged security groups found for instance %s; ensure only the k8s security group is tagged\", instanceID) </ins> } <ins> return tagged[0], nil </ins> } <del> if best == nil { glog.Warningf(\"No security group found for instance %q\", instanceID) </del> <ins> if len(untagged) > 0 { // For back-compat, we will allow a single untagged SG if len(untagged) != 1 { return nil, fmt.Errorf(\"Multiple untagged security groups found for instance %s; ensure the k8s security group is tagged\", instanceID) } return untagged[0], nil </ins> } <del> return best, nil </del> <ins> glog.Warningf(\"No security group found for instance %q\", instanceID) return nil, nil </ins> } // Return all the security groups that are tagged as being part of our cluster", "positive_passages": [{"docid": "doc-en-kubernetes-8b50a6e6165c8a4dec36611b88a25cd5e6225d1dd2a0483fe2c5b587bd4e7bf4", "text": "reported hitting this error: The instance had 4 security groups, and only one of them was tagged. However, the logic around picking the security group is incorrect.. if we get two non-tagged SGs before we see the first tagged SG, it throws an error. We'll want to cherry-pick this to 1.2\nI think this one was a victim of flakiness in the auto-assigner when the author is the first-listed maintainer. Assigning to you, :-)", "commid": "kubernetes_issue_23339", "tokennum": 104}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dff085188705c1afb0e99c2fe73ac9ecf92fc2494c676dc1ed7efedb43e99495", "query": "} } <del> func TestSetDefaultReplicationControllerImagePullPolicy(t *testing.T) { containersWithoutPullPolicy, _ := json.Marshal([]map[string]interface{}{ { \"name\":  \"install\", \"image\": \"busybox:latest\", }, }) </del> <ins> type InitContainerValidator func(got, expected *v1.Container) error </ins> <del> containersWithPullPolicy, _ := json.Marshal([]map[string]interface{}{ { \"name\":            \"install\", \"imagePullPolicy\": \"IfNotPresent\", }, }) </del> <ins> func TestSetDefaultReplicationControllerInitContainers(t *testing.T) { assertEnvFieldRef := func(got, expected *v1.Container) error { if len(got.Env) != len(expected.Env) { return fmt.Errorf(\"different number of env: got <%v>, expected <%v>\", len(got.Env), len(expected.Env)) } for j := range got.Env { ge := &got.Env[j] ee := &expected.Env[j] if ge.Name != ee.Name { return fmt.Errorf(\"different name of env: got <%v>, expected <%v>\", ge.Name, ee.Name) } if ge.ValueFrom.FieldRef.APIVersion != ee.ValueFrom.FieldRef.APIVersion { return fmt.Errorf(\"different api version of FieldRef <%v>: got <%v>, expected <%v>\", ge.Name, ge.ValueFrom.FieldRef.APIVersion, ee.ValueFrom.FieldRef.APIVersion) } } return nil } assertImagePullPolicy := func(got, expected *v1.Container) error { if got.ImagePullPolicy != expected.ImagePullPolicy { return fmt.Errorf(\"different image pull poicy: got <%v>, expected <%v>\", got.ImagePullPolicy, expected.ImagePullPolicy) } return nil } assertContainerPort := func(got, expected *v1.Container) error { if len(got.Ports) != len(expected.Ports) { return fmt.Errorf(\"different number of ports: got <%v>, expected <%v>\", len(got.Ports), len(expected.Ports)) } for i := range got.Ports { gp := &got.Ports[i] ep := &expected.Ports[i] if gp.Name != ep.Name { return fmt.Errorf(\"different name of port: got <%v>, expected <%v>\", gp.Name, ep.Name) } if gp.Protocol != ep.Protocol { return fmt.Errorf(\"different port protocol <%v>: got <%v>, expected <%v>\", gp.Name, gp.Protocol, ep.Protocol) } } return nil } assertResource := func(got, expected *v1.Container) error { if len(got.Resources.Limits) != len(expected.Resources.Limits) { return fmt.Errorf(\"different number of resources.Limits: got <%v>, expected <%v>\", len(got.Resources.Limits), (expected.Resources.Limits)) } for k, v := range got.Resources.Limits { if ev, found := expected.Resources.Limits[v1.ResourceName(k)]; !found { return fmt.Errorf(\"failed to find resource <%v> in expected resources.Limits.\", k) } else { if ev.Value() != v.Value() { return fmt.Errorf(\"different resource.Limits: got <%v>, expected <%v>.\", v.Value(), ev.Value()) } } } if len(got.Resources.Requests) != len(expected.Resources.Requests) { return fmt.Errorf(\"different number of resources.Requests: got <%v>, expected <%v>\", len(got.Resources.Requests), (expected.Resources.Requests)) } for k, v := range got.Resources.Requests { if ev, found := expected.Resources.Requests[v1.ResourceName(k)]; !found { return fmt.Errorf(\"failed to find resource <%v> in expected resources.Requests.\", k) } else { if ev.Value() != v.Value() { return fmt.Errorf(\"different resource.Requests: got <%v>, expected <%v>.\", v.Value(), ev.Value()) } } } return nil } assertProb := func(got, expected *v1.Container) error { // Assert LivenessProbe if got.LivenessProbe.Handler.HTTPGet.Path != expected.LivenessProbe.Handler.HTTPGet.Path || got.LivenessProbe.Handler.HTTPGet.Scheme != expected.LivenessProbe.Handler.HTTPGet.Scheme || got.LivenessProbe.FailureThreshold != expected.LivenessProbe.FailureThreshold || got.LivenessProbe.SuccessThreshold != expected.LivenessProbe.SuccessThreshold || got.LivenessProbe.PeriodSeconds != expected.LivenessProbe.PeriodSeconds || got.LivenessProbe.TimeoutSeconds != expected.LivenessProbe.TimeoutSeconds { return fmt.Errorf(\"different LivenessProbe: got <%v>, expected <%v>\", got.LivenessProbe, expected.LivenessProbe) } // Assert ReadinessProbe if got.ReadinessProbe.Handler.HTTPGet.Path != expected.ReadinessProbe.Handler.HTTPGet.Path || got.ReadinessProbe.Handler.HTTPGet.Scheme != expected.ReadinessProbe.Handler.HTTPGet.Scheme || got.ReadinessProbe.FailureThreshold != expected.ReadinessProbe.FailureThreshold || got.ReadinessProbe.SuccessThreshold != expected.ReadinessProbe.SuccessThreshold || got.ReadinessProbe.PeriodSeconds != expected.ReadinessProbe.PeriodSeconds || got.ReadinessProbe.TimeoutSeconds != expected.ReadinessProbe.TimeoutSeconds { return fmt.Errorf(\"different ReadinessProbe: got <%v>, expected <%v>\", got.ReadinessProbe, expected.ReadinessProbe) } return nil } assertLifeCycle := func(got, expected *v1.Container) error { if got.Lifecycle.PostStart.HTTPGet.Path != expected.Lifecycle.PostStart.HTTPGet.Path || got.Lifecycle.PostStart.HTTPGet.Scheme != expected.Lifecycle.PostStart.HTTPGet.Scheme { return fmt.Errorf(\"different LifeCycle: got <%v>, expected <%v>\", got.Lifecycle, expected.Lifecycle) } return nil } cpu, _ := resource.ParseQuantity(\"100Gi\") mem, _ := resource.ParseQuantity(\"100Mi\") </ins> tests := []struct { <del> rc               v1.ReplicationController expectPullPolicy v1.PullPolicy </del> <ins> name       string rc         v1.ReplicationController expected   []v1.Container validators []InitContainerValidator </ins> }{ { <ins> name: \"imagePullIPolicy\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"install\", \"image\": \"busybox\" } ]`, }, }, }, }, }, expected: []v1.Container{ { ImagePullPolicy: v1.PullAlways, }, }, validators: []InitContainerValidator{assertImagePullPolicy}, }, { name: \"FieldRef\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"env\": [ { \"name\": \"MY_POD_IP\", \"valueFrom\": { \"fieldRef\": { \"apiVersion\": \"\", \"fieldPath\": \"status.podIP\" } } } ] } ]`, }, }, }, }, }, expected: []v1.Container{ { Env: []v1.EnvVar{ { Name: \"MY_POD_IP\", ValueFrom: &v1.EnvVarSource{ FieldRef: &v1.ObjectFieldSelector{ APIVersion: \"v1\", FieldPath:  \"status.podIP\", }, }, }, }, }, }, validators: []InitContainerValidator{assertEnvFieldRef}, }, { name: \"ContainerPort\", </ins> rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ <del> \"pod.beta.kubernetes.io/init-containers\": string(containersWithoutPullPolicy), </del> <ins> \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"ports\": [ { \"name\": \"default\" } ] } ]`, </ins> }, }, }, }, }, <del> expectPullPolicy: v1.PullAlways, </del> <ins> expected: []v1.Container{ { Ports: []v1.ContainerPort{ { Name:     \"default\", Protocol: v1.ProtocolTCP, }, }, }, }, validators: []InitContainerValidator{assertContainerPort}, </ins> }, { <ins> name: \"Resources\", </ins> rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ <del> \"pod.beta.kubernetes.io/init-containers\": string(containersWithPullPolicy), </del> <ins> \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"resources\": { \"limits\": { \"cpu\": \"100Gi\", \"memory\": \"100Mi\" }, \"requests\": { \"cpu\": \"100Gi\", \"memory\": \"100Mi\" } } } ]`, </ins> }, }, }, }, }, <del> expectPullPolicy: v1.PullIfNotPresent, </del> <ins> expected: []v1.Container{ { Resources: v1.ResourceRequirements{ Limits: v1.ResourceList{ v1.ResourceCPU:    cpu, v1.ResourceMemory: mem, }, Requests: v1.ResourceList{ v1.ResourceCPU:    cpu, v1.ResourceMemory: mem, }, }, }, }, validators: []InitContainerValidator{assertResource}, }, { name: \"Prob\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"livenessProbe\": { \"httpGet\": { \"host\": \"localhost\" } }, \"readinessProbe\": { \"httpGet\": { \"host\": \"localhost\" } } } ]`, }, }, }, }, }, expected: []v1.Container{ { LivenessProbe: &v1.Probe{ Handler: v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, TimeoutSeconds:   1, PeriodSeconds:    10, SuccessThreshold: 1, FailureThreshold: 3, }, ReadinessProbe: &v1.Probe{ Handler: v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, TimeoutSeconds:   1, PeriodSeconds:    10, SuccessThreshold: 1, FailureThreshold: 3, }, }, }, validators: []InitContainerValidator{assertProb}, }, { name: \"LifeCycle\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"lifecycle\": { \"postStart\": { \"httpGet\": { \"host\": \"localhost\" } }, \"preStop\": { \"httpGet\": { \"host\": \"localhost\" } } } } ]`, }, }, }, }, }, expected: []v1.Container{ { Lifecycle: &v1.Lifecycle{ PostStart: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, PreStop: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, }, }, }, validators: []InitContainerValidator{assertLifeCycle}, </ins> }, } <ins> assertInitContainers := func(got, expected []v1.Container, validators []InitContainerValidator) error { if len(got) != len(expected) { return fmt.Errorf(\"different number of init container: got <%d>, expected <%d>\", len(got), len(expected)) } for i := range got { g := &got[i] e := &expected[i] for _, validator := range validators { if err := validator(g, e); err != nil { return err } } } return nil } </ins> for _, test := range tests { rc := &test.rc obj2 := roundTrip(t, runtime.Object(rc))", "positive_passages": [{"docid": "doc-en-kubernetes-c7797df648733fdf9e156246e323d8c03549ac9a3ca2ad30e283629a87abe7ee", "text": "What happened: kubelet doesn't seem to be able to manage containers started with CRI-O any more I'm testing kubelet + CRI-O on an Ubuntu 18.04 server installation, inside a qemu/kvm VM managed by Vagrant (see ), in order to be able to test k8s + KubeVirt + KataContainers, which are all compatible with CRI-O kubelet will obsess on starting new containers, which looks like and endless process, and the cluster never gets ready. For instance here are some syslogs : What you expected to happen: It used to work (see asciinema recording at ) a few days ago, but I fear some recent changes broke it. How to reproduce it (as minimally and precisely as possible): Testing with vagrant up --provider=libvirt on Linux with a clone of that commit: vagrant ssh into the VM and ps -edf f or tail -f /var/log/syslog would do... Anything else we need to know?: Environment: Kubernetes version (use ):Cloud provider or hardware configuration: qemu/kvm VM +OS (e.g: ): Ubuntu 18.04.2 LTS Kernel (e.g. ): Linux kubernetes-vagrant-01 4.15.0-48-generic -Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x8664 x8664 x8664 GNU/Linux Install tools: kubeadm as in Network plugin and version (if this is a network-related bug): Others:\n/sig node\nI can confirm this. If I start cri-o from a systemd service it fails with the above mentioned error message. Starting crio with without systemd works just fine. systemd file:\nThanks for your detailed report :) Just want to do some quick version confirming - you've been using k8s 1.14.1 both when it did and did not work? Any other version changes?\nNot sure for before, when it used to work, but according to the asciinema recording mentioned above (), it seems the same. However, not sure for CRI-O, underlying OS stuff (systemd, kernel, etc.). Sorry.\nI was looking for some information for days. I have exactly the same issue when I use podman + systemd on 18.04.2.", "commid": "kubernetes_issue_77615", "tokennum": 541}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dff085188705c1afb0e99c2fe73ac9ecf92fc2494c676dc1ed7efedb43e99495", "query": "} } <del> func TestSetDefaultReplicationControllerImagePullPolicy(t *testing.T) { containersWithoutPullPolicy, _ := json.Marshal([]map[string]interface{}{ { \"name\":  \"install\", \"image\": \"busybox:latest\", }, }) </del> <ins> type InitContainerValidator func(got, expected *v1.Container) error </ins> <del> containersWithPullPolicy, _ := json.Marshal([]map[string]interface{}{ { \"name\":            \"install\", \"imagePullPolicy\": \"IfNotPresent\", }, }) </del> <ins> func TestSetDefaultReplicationControllerInitContainers(t *testing.T) { assertEnvFieldRef := func(got, expected *v1.Container) error { if len(got.Env) != len(expected.Env) { return fmt.Errorf(\"different number of env: got <%v>, expected <%v>\", len(got.Env), len(expected.Env)) } for j := range got.Env { ge := &got.Env[j] ee := &expected.Env[j] if ge.Name != ee.Name { return fmt.Errorf(\"different name of env: got <%v>, expected <%v>\", ge.Name, ee.Name) } if ge.ValueFrom.FieldRef.APIVersion != ee.ValueFrom.FieldRef.APIVersion { return fmt.Errorf(\"different api version of FieldRef <%v>: got <%v>, expected <%v>\", ge.Name, ge.ValueFrom.FieldRef.APIVersion, ee.ValueFrom.FieldRef.APIVersion) } } return nil } assertImagePullPolicy := func(got, expected *v1.Container) error { if got.ImagePullPolicy != expected.ImagePullPolicy { return fmt.Errorf(\"different image pull poicy: got <%v>, expected <%v>\", got.ImagePullPolicy, expected.ImagePullPolicy) } return nil } assertContainerPort := func(got, expected *v1.Container) error { if len(got.Ports) != len(expected.Ports) { return fmt.Errorf(\"different number of ports: got <%v>, expected <%v>\", len(got.Ports), len(expected.Ports)) } for i := range got.Ports { gp := &got.Ports[i] ep := &expected.Ports[i] if gp.Name != ep.Name { return fmt.Errorf(\"different name of port: got <%v>, expected <%v>\", gp.Name, ep.Name) } if gp.Protocol != ep.Protocol { return fmt.Errorf(\"different port protocol <%v>: got <%v>, expected <%v>\", gp.Name, gp.Protocol, ep.Protocol) } } return nil } assertResource := func(got, expected *v1.Container) error { if len(got.Resources.Limits) != len(expected.Resources.Limits) { return fmt.Errorf(\"different number of resources.Limits: got <%v>, expected <%v>\", len(got.Resources.Limits), (expected.Resources.Limits)) } for k, v := range got.Resources.Limits { if ev, found := expected.Resources.Limits[v1.ResourceName(k)]; !found { return fmt.Errorf(\"failed to find resource <%v> in expected resources.Limits.\", k) } else { if ev.Value() != v.Value() { return fmt.Errorf(\"different resource.Limits: got <%v>, expected <%v>.\", v.Value(), ev.Value()) } } } if len(got.Resources.Requests) != len(expected.Resources.Requests) { return fmt.Errorf(\"different number of resources.Requests: got <%v>, expected <%v>\", len(got.Resources.Requests), (expected.Resources.Requests)) } for k, v := range got.Resources.Requests { if ev, found := expected.Resources.Requests[v1.ResourceName(k)]; !found { return fmt.Errorf(\"failed to find resource <%v> in expected resources.Requests.\", k) } else { if ev.Value() != v.Value() { return fmt.Errorf(\"different resource.Requests: got <%v>, expected <%v>.\", v.Value(), ev.Value()) } } } return nil } assertProb := func(got, expected *v1.Container) error { // Assert LivenessProbe if got.LivenessProbe.Handler.HTTPGet.Path != expected.LivenessProbe.Handler.HTTPGet.Path || got.LivenessProbe.Handler.HTTPGet.Scheme != expected.LivenessProbe.Handler.HTTPGet.Scheme || got.LivenessProbe.FailureThreshold != expected.LivenessProbe.FailureThreshold || got.LivenessProbe.SuccessThreshold != expected.LivenessProbe.SuccessThreshold || got.LivenessProbe.PeriodSeconds != expected.LivenessProbe.PeriodSeconds || got.LivenessProbe.TimeoutSeconds != expected.LivenessProbe.TimeoutSeconds { return fmt.Errorf(\"different LivenessProbe: got <%v>, expected <%v>\", got.LivenessProbe, expected.LivenessProbe) } // Assert ReadinessProbe if got.ReadinessProbe.Handler.HTTPGet.Path != expected.ReadinessProbe.Handler.HTTPGet.Path || got.ReadinessProbe.Handler.HTTPGet.Scheme != expected.ReadinessProbe.Handler.HTTPGet.Scheme || got.ReadinessProbe.FailureThreshold != expected.ReadinessProbe.FailureThreshold || got.ReadinessProbe.SuccessThreshold != expected.ReadinessProbe.SuccessThreshold || got.ReadinessProbe.PeriodSeconds != expected.ReadinessProbe.PeriodSeconds || got.ReadinessProbe.TimeoutSeconds != expected.ReadinessProbe.TimeoutSeconds { return fmt.Errorf(\"different ReadinessProbe: got <%v>, expected <%v>\", got.ReadinessProbe, expected.ReadinessProbe) } return nil } assertLifeCycle := func(got, expected *v1.Container) error { if got.Lifecycle.PostStart.HTTPGet.Path != expected.Lifecycle.PostStart.HTTPGet.Path || got.Lifecycle.PostStart.HTTPGet.Scheme != expected.Lifecycle.PostStart.HTTPGet.Scheme { return fmt.Errorf(\"different LifeCycle: got <%v>, expected <%v>\", got.Lifecycle, expected.Lifecycle) } return nil } cpu, _ := resource.ParseQuantity(\"100Gi\") mem, _ := resource.ParseQuantity(\"100Mi\") </ins> tests := []struct { <del> rc               v1.ReplicationController expectPullPolicy v1.PullPolicy </del> <ins> name       string rc         v1.ReplicationController expected   []v1.Container validators []InitContainerValidator </ins> }{ { <ins> name: \"imagePullIPolicy\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"install\", \"image\": \"busybox\" } ]`, }, }, }, }, }, expected: []v1.Container{ { ImagePullPolicy: v1.PullAlways, }, }, validators: []InitContainerValidator{assertImagePullPolicy}, }, { name: \"FieldRef\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"env\": [ { \"name\": \"MY_POD_IP\", \"valueFrom\": { \"fieldRef\": { \"apiVersion\": \"\", \"fieldPath\": \"status.podIP\" } } } ] } ]`, }, }, }, }, }, expected: []v1.Container{ { Env: []v1.EnvVar{ { Name: \"MY_POD_IP\", ValueFrom: &v1.EnvVarSource{ FieldRef: &v1.ObjectFieldSelector{ APIVersion: \"v1\", FieldPath:  \"status.podIP\", }, }, }, }, }, }, validators: []InitContainerValidator{assertEnvFieldRef}, }, { name: \"ContainerPort\", </ins> rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ <del> \"pod.beta.kubernetes.io/init-containers\": string(containersWithoutPullPolicy), </del> <ins> \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"ports\": [ { \"name\": \"default\" } ] } ]`, </ins> }, }, }, }, }, <del> expectPullPolicy: v1.PullAlways, </del> <ins> expected: []v1.Container{ { Ports: []v1.ContainerPort{ { Name:     \"default\", Protocol: v1.ProtocolTCP, }, }, }, }, validators: []InitContainerValidator{assertContainerPort}, </ins> }, { <ins> name: \"Resources\", </ins> rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ <del> \"pod.beta.kubernetes.io/init-containers\": string(containersWithPullPolicy), </del> <ins> \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"resources\": { \"limits\": { \"cpu\": \"100Gi\", \"memory\": \"100Mi\" }, \"requests\": { \"cpu\": \"100Gi\", \"memory\": \"100Mi\" } } } ]`, </ins> }, }, }, }, }, <del> expectPullPolicy: v1.PullIfNotPresent, </del> <ins> expected: []v1.Container{ { Resources: v1.ResourceRequirements{ Limits: v1.ResourceList{ v1.ResourceCPU:    cpu, v1.ResourceMemory: mem, }, Requests: v1.ResourceList{ v1.ResourceCPU:    cpu, v1.ResourceMemory: mem, }, }, }, }, validators: []InitContainerValidator{assertResource}, }, { name: \"Prob\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"livenessProbe\": { \"httpGet\": { \"host\": \"localhost\" } }, \"readinessProbe\": { \"httpGet\": { \"host\": \"localhost\" } } } ]`, }, }, }, }, }, expected: []v1.Container{ { LivenessProbe: &v1.Probe{ Handler: v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, TimeoutSeconds:   1, PeriodSeconds:    10, SuccessThreshold: 1, FailureThreshold: 3, }, ReadinessProbe: &v1.Probe{ Handler: v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, TimeoutSeconds:   1, PeriodSeconds:    10, SuccessThreshold: 1, FailureThreshold: 3, }, }, }, validators: []InitContainerValidator{assertProb}, }, { name: \"LifeCycle\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"lifecycle\": { \"postStart\": { \"httpGet\": { \"host\": \"localhost\" } }, \"preStop\": { \"httpGet\": { \"host\": \"localhost\" } } } } ]`, }, }, }, }, }, expected: []v1.Container{ { Lifecycle: &v1.Lifecycle{ PostStart: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, PreStop: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, }, }, }, validators: []InitContainerValidator{assertLifeCycle}, </ins> }, } <ins> assertInitContainers := func(got, expected []v1.Container, validators []InitContainerValidator) error { if len(got) != len(expected) { return fmt.Errorf(\"different number of init container: got <%d>, expected <%d>\", len(got), len(expected)) } for i := range got { g := &got[i] e := &expected[i] for _, validator := range validators { if err := validator(g, e); err != nil { return err } } } return nil } </ins> for _, test := range tests { rc := &test.rc obj2 := roundTrip(t, runtime.Object(rc))", "positive_passages": [{"docid": "doc-en-kubernetes-dca27e474f7f12153e878b1f27ed663eb17fd42e2832a567b0d652b26f30c566", "text": "It is the same for both 14.15 and 14.18 kernels. Podman without systemd runs fine. Podman with systemd fails at runc with the same error podman[]: open /dev/stderr: no such device or address podman[]: NAME: runc - Open Container Initiative runtime podman[]: runc is a command line client for running applications packaged according to ... podman[]: time=\"2019-05-11T13:04:59-07:00\" level=error msg=\"open /dev/stderr: no such device or addressn\" podman[]: open /dev/stderr: no such device or address\nI've tried to reproduce it on 18.04.2 using Podman from but I am not able to reproduce it. Do you have any reproducer? How did you install Podman?\nI used ceph unit files to run ceph in podman rather than docker. Systemd unit successfully starts docker but fails with podman. I can successfully run the same podman container run command from the command line. How were you trying to replicate this? Can you post your unit file?\nHi, I'am having the same problem with Kubernetes with CRI-O. After joining a second worker node it fails to start flannel. gives the following error: What I've tried: Installing previous version of Kubernetes (from to ) Installing previous version of crio (from to ) Building runc myself from their github page and selecting this in the Running it on Ubunut 18.04.2 Issue: (the one giuseppe linked)\nI wonder if the issue is with systemd and runc. In both cases, crio and podman, I see runc help output which tells me that something is not being passed to runc that it needs.\nI've only used so it is different than your test and you confirmed it works from the CLI for you as well. Could you share your service file so I test it?\nI've tried systemd and cgroupfs but no luck so far.\nso it seems that runc fails to re-open . That seems like a runc issue, as it doesn't really need to reopen it. To fix the failure, you could use something like:\nJust an example.", "commid": "kubernetes_issue_77615", "tokennum": 504}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dff085188705c1afb0e99c2fe73ac9ecf92fc2494c676dc1ed7efedb43e99495", "query": "} } <del> func TestSetDefaultReplicationControllerImagePullPolicy(t *testing.T) { containersWithoutPullPolicy, _ := json.Marshal([]map[string]interface{}{ { \"name\":  \"install\", \"image\": \"busybox:latest\", }, }) </del> <ins> type InitContainerValidator func(got, expected *v1.Container) error </ins> <del> containersWithPullPolicy, _ := json.Marshal([]map[string]interface{}{ { \"name\":            \"install\", \"imagePullPolicy\": \"IfNotPresent\", }, }) </del> <ins> func TestSetDefaultReplicationControllerInitContainers(t *testing.T) { assertEnvFieldRef := func(got, expected *v1.Container) error { if len(got.Env) != len(expected.Env) { return fmt.Errorf(\"different number of env: got <%v>, expected <%v>\", len(got.Env), len(expected.Env)) } for j := range got.Env { ge := &got.Env[j] ee := &expected.Env[j] if ge.Name != ee.Name { return fmt.Errorf(\"different name of env: got <%v>, expected <%v>\", ge.Name, ee.Name) } if ge.ValueFrom.FieldRef.APIVersion != ee.ValueFrom.FieldRef.APIVersion { return fmt.Errorf(\"different api version of FieldRef <%v>: got <%v>, expected <%v>\", ge.Name, ge.ValueFrom.FieldRef.APIVersion, ee.ValueFrom.FieldRef.APIVersion) } } return nil } assertImagePullPolicy := func(got, expected *v1.Container) error { if got.ImagePullPolicy != expected.ImagePullPolicy { return fmt.Errorf(\"different image pull poicy: got <%v>, expected <%v>\", got.ImagePullPolicy, expected.ImagePullPolicy) } return nil } assertContainerPort := func(got, expected *v1.Container) error { if len(got.Ports) != len(expected.Ports) { return fmt.Errorf(\"different number of ports: got <%v>, expected <%v>\", len(got.Ports), len(expected.Ports)) } for i := range got.Ports { gp := &got.Ports[i] ep := &expected.Ports[i] if gp.Name != ep.Name { return fmt.Errorf(\"different name of port: got <%v>, expected <%v>\", gp.Name, ep.Name) } if gp.Protocol != ep.Protocol { return fmt.Errorf(\"different port protocol <%v>: got <%v>, expected <%v>\", gp.Name, gp.Protocol, ep.Protocol) } } return nil } assertResource := func(got, expected *v1.Container) error { if len(got.Resources.Limits) != len(expected.Resources.Limits) { return fmt.Errorf(\"different number of resources.Limits: got <%v>, expected <%v>\", len(got.Resources.Limits), (expected.Resources.Limits)) } for k, v := range got.Resources.Limits { if ev, found := expected.Resources.Limits[v1.ResourceName(k)]; !found { return fmt.Errorf(\"failed to find resource <%v> in expected resources.Limits.\", k) } else { if ev.Value() != v.Value() { return fmt.Errorf(\"different resource.Limits: got <%v>, expected <%v>.\", v.Value(), ev.Value()) } } } if len(got.Resources.Requests) != len(expected.Resources.Requests) { return fmt.Errorf(\"different number of resources.Requests: got <%v>, expected <%v>\", len(got.Resources.Requests), (expected.Resources.Requests)) } for k, v := range got.Resources.Requests { if ev, found := expected.Resources.Requests[v1.ResourceName(k)]; !found { return fmt.Errorf(\"failed to find resource <%v> in expected resources.Requests.\", k) } else { if ev.Value() != v.Value() { return fmt.Errorf(\"different resource.Requests: got <%v>, expected <%v>.\", v.Value(), ev.Value()) } } } return nil } assertProb := func(got, expected *v1.Container) error { // Assert LivenessProbe if got.LivenessProbe.Handler.HTTPGet.Path != expected.LivenessProbe.Handler.HTTPGet.Path || got.LivenessProbe.Handler.HTTPGet.Scheme != expected.LivenessProbe.Handler.HTTPGet.Scheme || got.LivenessProbe.FailureThreshold != expected.LivenessProbe.FailureThreshold || got.LivenessProbe.SuccessThreshold != expected.LivenessProbe.SuccessThreshold || got.LivenessProbe.PeriodSeconds != expected.LivenessProbe.PeriodSeconds || got.LivenessProbe.TimeoutSeconds != expected.LivenessProbe.TimeoutSeconds { return fmt.Errorf(\"different LivenessProbe: got <%v>, expected <%v>\", got.LivenessProbe, expected.LivenessProbe) } // Assert ReadinessProbe if got.ReadinessProbe.Handler.HTTPGet.Path != expected.ReadinessProbe.Handler.HTTPGet.Path || got.ReadinessProbe.Handler.HTTPGet.Scheme != expected.ReadinessProbe.Handler.HTTPGet.Scheme || got.ReadinessProbe.FailureThreshold != expected.ReadinessProbe.FailureThreshold || got.ReadinessProbe.SuccessThreshold != expected.ReadinessProbe.SuccessThreshold || got.ReadinessProbe.PeriodSeconds != expected.ReadinessProbe.PeriodSeconds || got.ReadinessProbe.TimeoutSeconds != expected.ReadinessProbe.TimeoutSeconds { return fmt.Errorf(\"different ReadinessProbe: got <%v>, expected <%v>\", got.ReadinessProbe, expected.ReadinessProbe) } return nil } assertLifeCycle := func(got, expected *v1.Container) error { if got.Lifecycle.PostStart.HTTPGet.Path != expected.Lifecycle.PostStart.HTTPGet.Path || got.Lifecycle.PostStart.HTTPGet.Scheme != expected.Lifecycle.PostStart.HTTPGet.Scheme { return fmt.Errorf(\"different LifeCycle: got <%v>, expected <%v>\", got.Lifecycle, expected.Lifecycle) } return nil } cpu, _ := resource.ParseQuantity(\"100Gi\") mem, _ := resource.ParseQuantity(\"100Mi\") </ins> tests := []struct { <del> rc               v1.ReplicationController expectPullPolicy v1.PullPolicy </del> <ins> name       string rc         v1.ReplicationController expected   []v1.Container validators []InitContainerValidator </ins> }{ { <ins> name: \"imagePullIPolicy\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"install\", \"image\": \"busybox\" } ]`, }, }, }, }, }, expected: []v1.Container{ { ImagePullPolicy: v1.PullAlways, }, }, validators: []InitContainerValidator{assertImagePullPolicy}, }, { name: \"FieldRef\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"env\": [ { \"name\": \"MY_POD_IP\", \"valueFrom\": { \"fieldRef\": { \"apiVersion\": \"\", \"fieldPath\": \"status.podIP\" } } } ] } ]`, }, }, }, }, }, expected: []v1.Container{ { Env: []v1.EnvVar{ { Name: \"MY_POD_IP\", ValueFrom: &v1.EnvVarSource{ FieldRef: &v1.ObjectFieldSelector{ APIVersion: \"v1\", FieldPath:  \"status.podIP\", }, }, }, }, }, }, validators: []InitContainerValidator{assertEnvFieldRef}, }, { name: \"ContainerPort\", </ins> rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ <del> \"pod.beta.kubernetes.io/init-containers\": string(containersWithoutPullPolicy), </del> <ins> \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"ports\": [ { \"name\": \"default\" } ] } ]`, </ins> }, }, }, }, }, <del> expectPullPolicy: v1.PullAlways, </del> <ins> expected: []v1.Container{ { Ports: []v1.ContainerPort{ { Name:     \"default\", Protocol: v1.ProtocolTCP, }, }, }, }, validators: []InitContainerValidator{assertContainerPort}, </ins> }, { <ins> name: \"Resources\", </ins> rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ <del> \"pod.beta.kubernetes.io/init-containers\": string(containersWithPullPolicy), </del> <ins> \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"resources\": { \"limits\": { \"cpu\": \"100Gi\", \"memory\": \"100Mi\" }, \"requests\": { \"cpu\": \"100Gi\", \"memory\": \"100Mi\" } } } ]`, </ins> }, }, }, }, }, <del> expectPullPolicy: v1.PullIfNotPresent, </del> <ins> expected: []v1.Container{ { Resources: v1.ResourceRequirements{ Limits: v1.ResourceList{ v1.ResourceCPU:    cpu, v1.ResourceMemory: mem, }, Requests: v1.ResourceList{ v1.ResourceCPU:    cpu, v1.ResourceMemory: mem, }, }, }, }, validators: []InitContainerValidator{assertResource}, }, { name: \"Prob\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"livenessProbe\": { \"httpGet\": { \"host\": \"localhost\" } }, \"readinessProbe\": { \"httpGet\": { \"host\": \"localhost\" } } } ]`, }, }, }, }, }, expected: []v1.Container{ { LivenessProbe: &v1.Probe{ Handler: v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, TimeoutSeconds:   1, PeriodSeconds:    10, SuccessThreshold: 1, FailureThreshold: 3, }, ReadinessProbe: &v1.Probe{ Handler: v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, TimeoutSeconds:   1, PeriodSeconds:    10, SuccessThreshold: 1, FailureThreshold: 3, }, }, }, validators: []InitContainerValidator{assertProb}, }, { name: \"LifeCycle\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"lifecycle\": { \"postStart\": { \"httpGet\": { \"host\": \"localhost\" } }, \"preStop\": { \"httpGet\": { \"host\": \"localhost\" } } } } ]`, }, }, }, }, }, expected: []v1.Container{ { Lifecycle: &v1.Lifecycle{ PostStart: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, PreStop: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, }, }, }, validators: []InitContainerValidator{assertLifeCycle}, </ins> }, } <ins> assertInitContainers := func(got, expected []v1.Container, validators []InitContainerValidator) error { if len(got) != len(expected) { return fmt.Errorf(\"different number of init container: got <%d>, expected <%d>\", len(got), len(expected)) } for i := range got { g := &got[i] e := &expected[i] for _, validator := range validators { if err := validator(g, e); err != nil { return err } } } return nil } </ins> for _, test := range tests { rc := &test.rc obj2 := roundTrip(t, runtime.Object(rc))", "positive_passages": [{"docid": "doc-en-kubernetes-1a33d9e403b3728be8b8de7e79372d00143f16de361084780a7a026e224a4dd2", "text": "I use ceph-ansible to install cluster so it may need to install additional daemons like mon before running mgr but the error, in this case, should be different, [Unit] Description=Ceph Manager [Service] EnvironmentFile=-/etc/environment ExecStartPre=-/usr/bin/podman stop ceph-mgr-storage2n1-la ExecStartPre=-/usr/bin/podman rm ceph-mgr-storage2n1-la ExecStart=/usr/bin/podman run --rm --net=host  --memory=16G  --cpus=4  -v /var/lib/ceph:/var/lib/ceph:z  -v /etc/ceph:/etc/ceph:z  -v /var/run/ceph:/var/run/ceph:z  -v /etc/localtime:/etc/localtime:ro  -e CLUSTER=ceph  -e CEPHDAEMON=MGR  -e CONTAINERIMAGE=  {{ cephmgrdockerextraenv }}  --name=ceph-mgr-storage2n1-la  ExecStopPost=-/usr/bin/podman stop ceph-mgr-storage2n1-la Restart=always RestartSec=10s TimeoutStartSec=120 TimeoutStopSec=15 [Install] WantedBy=multi- delighted <:\nBTW, I projectatomic ppa and used apt-get -y podman to install. My podman version is 1.3.0 Sasha Litvak \u2014 You are receiving this because you commented. Reply to this email directly, view it on GitHub , or mute the thread\nCorrected file.", "commid": "kubernetes_issue_77615", "tokennum": 404}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dff085188705c1afb0e99c2fe73ac9ecf92fc2494c676dc1ed7efedb43e99495", "query": "} } <del> func TestSetDefaultReplicationControllerImagePullPolicy(t *testing.T) { containersWithoutPullPolicy, _ := json.Marshal([]map[string]interface{}{ { \"name\":  \"install\", \"image\": \"busybox:latest\", }, }) </del> <ins> type InitContainerValidator func(got, expected *v1.Container) error </ins> <del> containersWithPullPolicy, _ := json.Marshal([]map[string]interface{}{ { \"name\":            \"install\", \"imagePullPolicy\": \"IfNotPresent\", }, }) </del> <ins> func TestSetDefaultReplicationControllerInitContainers(t *testing.T) { assertEnvFieldRef := func(got, expected *v1.Container) error { if len(got.Env) != len(expected.Env) { return fmt.Errorf(\"different number of env: got <%v>, expected <%v>\", len(got.Env), len(expected.Env)) } for j := range got.Env { ge := &got.Env[j] ee := &expected.Env[j] if ge.Name != ee.Name { return fmt.Errorf(\"different name of env: got <%v>, expected <%v>\", ge.Name, ee.Name) } if ge.ValueFrom.FieldRef.APIVersion != ee.ValueFrom.FieldRef.APIVersion { return fmt.Errorf(\"different api version of FieldRef <%v>: got <%v>, expected <%v>\", ge.Name, ge.ValueFrom.FieldRef.APIVersion, ee.ValueFrom.FieldRef.APIVersion) } } return nil } assertImagePullPolicy := func(got, expected *v1.Container) error { if got.ImagePullPolicy != expected.ImagePullPolicy { return fmt.Errorf(\"different image pull poicy: got <%v>, expected <%v>\", got.ImagePullPolicy, expected.ImagePullPolicy) } return nil } assertContainerPort := func(got, expected *v1.Container) error { if len(got.Ports) != len(expected.Ports) { return fmt.Errorf(\"different number of ports: got <%v>, expected <%v>\", len(got.Ports), len(expected.Ports)) } for i := range got.Ports { gp := &got.Ports[i] ep := &expected.Ports[i] if gp.Name != ep.Name { return fmt.Errorf(\"different name of port: got <%v>, expected <%v>\", gp.Name, ep.Name) } if gp.Protocol != ep.Protocol { return fmt.Errorf(\"different port protocol <%v>: got <%v>, expected <%v>\", gp.Name, gp.Protocol, ep.Protocol) } } return nil } assertResource := func(got, expected *v1.Container) error { if len(got.Resources.Limits) != len(expected.Resources.Limits) { return fmt.Errorf(\"different number of resources.Limits: got <%v>, expected <%v>\", len(got.Resources.Limits), (expected.Resources.Limits)) } for k, v := range got.Resources.Limits { if ev, found := expected.Resources.Limits[v1.ResourceName(k)]; !found { return fmt.Errorf(\"failed to find resource <%v> in expected resources.Limits.\", k) } else { if ev.Value() != v.Value() { return fmt.Errorf(\"different resource.Limits: got <%v>, expected <%v>.\", v.Value(), ev.Value()) } } } if len(got.Resources.Requests) != len(expected.Resources.Requests) { return fmt.Errorf(\"different number of resources.Requests: got <%v>, expected <%v>\", len(got.Resources.Requests), (expected.Resources.Requests)) } for k, v := range got.Resources.Requests { if ev, found := expected.Resources.Requests[v1.ResourceName(k)]; !found { return fmt.Errorf(\"failed to find resource <%v> in expected resources.Requests.\", k) } else { if ev.Value() != v.Value() { return fmt.Errorf(\"different resource.Requests: got <%v>, expected <%v>.\", v.Value(), ev.Value()) } } } return nil } assertProb := func(got, expected *v1.Container) error { // Assert LivenessProbe if got.LivenessProbe.Handler.HTTPGet.Path != expected.LivenessProbe.Handler.HTTPGet.Path || got.LivenessProbe.Handler.HTTPGet.Scheme != expected.LivenessProbe.Handler.HTTPGet.Scheme || got.LivenessProbe.FailureThreshold != expected.LivenessProbe.FailureThreshold || got.LivenessProbe.SuccessThreshold != expected.LivenessProbe.SuccessThreshold || got.LivenessProbe.PeriodSeconds != expected.LivenessProbe.PeriodSeconds || got.LivenessProbe.TimeoutSeconds != expected.LivenessProbe.TimeoutSeconds { return fmt.Errorf(\"different LivenessProbe: got <%v>, expected <%v>\", got.LivenessProbe, expected.LivenessProbe) } // Assert ReadinessProbe if got.ReadinessProbe.Handler.HTTPGet.Path != expected.ReadinessProbe.Handler.HTTPGet.Path || got.ReadinessProbe.Handler.HTTPGet.Scheme != expected.ReadinessProbe.Handler.HTTPGet.Scheme || got.ReadinessProbe.FailureThreshold != expected.ReadinessProbe.FailureThreshold || got.ReadinessProbe.SuccessThreshold != expected.ReadinessProbe.SuccessThreshold || got.ReadinessProbe.PeriodSeconds != expected.ReadinessProbe.PeriodSeconds || got.ReadinessProbe.TimeoutSeconds != expected.ReadinessProbe.TimeoutSeconds { return fmt.Errorf(\"different ReadinessProbe: got <%v>, expected <%v>\", got.ReadinessProbe, expected.ReadinessProbe) } return nil } assertLifeCycle := func(got, expected *v1.Container) error { if got.Lifecycle.PostStart.HTTPGet.Path != expected.Lifecycle.PostStart.HTTPGet.Path || got.Lifecycle.PostStart.HTTPGet.Scheme != expected.Lifecycle.PostStart.HTTPGet.Scheme { return fmt.Errorf(\"different LifeCycle: got <%v>, expected <%v>\", got.Lifecycle, expected.Lifecycle) } return nil } cpu, _ := resource.ParseQuantity(\"100Gi\") mem, _ := resource.ParseQuantity(\"100Mi\") </ins> tests := []struct { <del> rc               v1.ReplicationController expectPullPolicy v1.PullPolicy </del> <ins> name       string rc         v1.ReplicationController expected   []v1.Container validators []InitContainerValidator </ins> }{ { <ins> name: \"imagePullIPolicy\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"install\", \"image\": \"busybox\" } ]`, }, }, }, }, }, expected: []v1.Container{ { ImagePullPolicy: v1.PullAlways, }, }, validators: []InitContainerValidator{assertImagePullPolicy}, }, { name: \"FieldRef\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"env\": [ { \"name\": \"MY_POD_IP\", \"valueFrom\": { \"fieldRef\": { \"apiVersion\": \"\", \"fieldPath\": \"status.podIP\" } } } ] } ]`, }, }, }, }, }, expected: []v1.Container{ { Env: []v1.EnvVar{ { Name: \"MY_POD_IP\", ValueFrom: &v1.EnvVarSource{ FieldRef: &v1.ObjectFieldSelector{ APIVersion: \"v1\", FieldPath:  \"status.podIP\", }, }, }, }, }, }, validators: []InitContainerValidator{assertEnvFieldRef}, }, { name: \"ContainerPort\", </ins> rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ <del> \"pod.beta.kubernetes.io/init-containers\": string(containersWithoutPullPolicy), </del> <ins> \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"ports\": [ { \"name\": \"default\" } ] } ]`, </ins> }, }, }, }, }, <del> expectPullPolicy: v1.PullAlways, </del> <ins> expected: []v1.Container{ { Ports: []v1.ContainerPort{ { Name:     \"default\", Protocol: v1.ProtocolTCP, }, }, }, }, validators: []InitContainerValidator{assertContainerPort}, </ins> }, { <ins> name: \"Resources\", </ins> rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ <del> \"pod.beta.kubernetes.io/init-containers\": string(containersWithPullPolicy), </del> <ins> \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"resources\": { \"limits\": { \"cpu\": \"100Gi\", \"memory\": \"100Mi\" }, \"requests\": { \"cpu\": \"100Gi\", \"memory\": \"100Mi\" } } } ]`, </ins> }, }, }, }, }, <del> expectPullPolicy: v1.PullIfNotPresent, </del> <ins> expected: []v1.Container{ { Resources: v1.ResourceRequirements{ Limits: v1.ResourceList{ v1.ResourceCPU:    cpu, v1.ResourceMemory: mem, }, Requests: v1.ResourceList{ v1.ResourceCPU:    cpu, v1.ResourceMemory: mem, }, }, }, }, validators: []InitContainerValidator{assertResource}, }, { name: \"Prob\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"livenessProbe\": { \"httpGet\": { \"host\": \"localhost\" } }, \"readinessProbe\": { \"httpGet\": { \"host\": \"localhost\" } } } ]`, }, }, }, }, }, expected: []v1.Container{ { LivenessProbe: &v1.Probe{ Handler: v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, TimeoutSeconds:   1, PeriodSeconds:    10, SuccessThreshold: 1, FailureThreshold: 3, }, ReadinessProbe: &v1.Probe{ Handler: v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, TimeoutSeconds:   1, PeriodSeconds:    10, SuccessThreshold: 1, FailureThreshold: 3, }, }, }, validators: []InitContainerValidator{assertProb}, }, { name: \"LifeCycle\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"lifecycle\": { \"postStart\": { \"httpGet\": { \"host\": \"localhost\" } }, \"preStop\": { \"httpGet\": { \"host\": \"localhost\" } } } } ]`, }, }, }, }, }, expected: []v1.Container{ { Lifecycle: &v1.Lifecycle{ PostStart: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, PreStop: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, }, }, }, validators: []InitContainerValidator{assertLifeCycle}, </ins> }, } <ins> assertInitContainers := func(got, expected []v1.Container, validators []InitContainerValidator) error { if len(got) != len(expected) { return fmt.Errorf(\"different number of init container: got <%d>, expected <%d>\", len(got), len(expected)) } for i := range got { g := &got[i] e := &expected[i] for _, validator := range validators { if err := validator(g, e); err != nil { return err } } } return nil } </ins> for _, test := range tests { rc := &test.rc obj2 := roundTrip(t, runtime.Object(rc))", "positive_passages": [{"docid": "doc-en-kubernetes-bae004f13a06f51a77aaeb8de64c7434d457cced5ee158b56a68659aa46bb958", "text": "[Unit] Description=Ceph Manager [Service] EnvironmentFile=-/etc/environment ExecStartPre=-/usr/bin/podman stop ceph-mgr-storage2n1-la ExecStartPre=-/usr/bin/podman rm ceph-mgr-storage2n1-la ExecStart=/usr/bin/podman run --rm --net=host  --memory=16G  --cpus=4  -v /var/lib/ceph:/var/lib/ceph:z  -v /etc/ceph:/etc/ceph:z  -v /var/run/ceph:/var/run/ceph:z  -v /etc/localtime:/etc/localtime:ro  -e CLUSTER=ceph  -e CEPHDAEMON=MGR  -e CONTAINERIMAGE=  --name=ceph-mgr-storage2n1-la  ExecStopPost=-/usr/bin/podman stop ceph-mgr-storage2n1-la Restart=always RestartSec=10s TimeoutStartSec=120 TimeoutStopSec=15 [Install] WantedBy=multi- Giuseppe Scrivano <:\nWould it have an effect system wide? Can I add it to a unit file or unit override instead? Giuseppe Scrivano <:\nyes, I think it is better to add it only to the unit file\nWhy would runc work outside of systemd? And if it needs stderr, giving it Null in settings will redirect stderr to Null I presume? On Tue, May 14, 2019, 9:46 AM Giuseppe Scrivano <:\nRunning into same issues on Ubuntu 18.04.2 using cri-o-1.13 via PPA.\nPR here: opencontainers/runc\nUntil it is avaialble with project atomic and such, can I use a null workaround? Giuseppe Scrivano <:\nyes, but you will lose anything written to stderr. You could probably also use a file, like\nWhat about actually mounting dev and using /dev/stderr ? On Tue, May 14, 2019, 3:11 PM Giuseppe Scrivano <:\nis a symlink to . It is present, the issue here is that is a socket. The fix for runc got merged, could you use an updated runc?\nI tried apt update/upgrade and restarting crio, but I'm still getting the issue.", "commid": "kubernetes_issue_77615", "tokennum": 570}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dff085188705c1afb0e99c2fe73ac9ecf92fc2494c676dc1ed7efedb43e99495", "query": "} } <del> func TestSetDefaultReplicationControllerImagePullPolicy(t *testing.T) { containersWithoutPullPolicy, _ := json.Marshal([]map[string]interface{}{ { \"name\":  \"install\", \"image\": \"busybox:latest\", }, }) </del> <ins> type InitContainerValidator func(got, expected *v1.Container) error </ins> <del> containersWithPullPolicy, _ := json.Marshal([]map[string]interface{}{ { \"name\":            \"install\", \"imagePullPolicy\": \"IfNotPresent\", }, }) </del> <ins> func TestSetDefaultReplicationControllerInitContainers(t *testing.T) { assertEnvFieldRef := func(got, expected *v1.Container) error { if len(got.Env) != len(expected.Env) { return fmt.Errorf(\"different number of env: got <%v>, expected <%v>\", len(got.Env), len(expected.Env)) } for j := range got.Env { ge := &got.Env[j] ee := &expected.Env[j] if ge.Name != ee.Name { return fmt.Errorf(\"different name of env: got <%v>, expected <%v>\", ge.Name, ee.Name) } if ge.ValueFrom.FieldRef.APIVersion != ee.ValueFrom.FieldRef.APIVersion { return fmt.Errorf(\"different api version of FieldRef <%v>: got <%v>, expected <%v>\", ge.Name, ge.ValueFrom.FieldRef.APIVersion, ee.ValueFrom.FieldRef.APIVersion) } } return nil } assertImagePullPolicy := func(got, expected *v1.Container) error { if got.ImagePullPolicy != expected.ImagePullPolicy { return fmt.Errorf(\"different image pull poicy: got <%v>, expected <%v>\", got.ImagePullPolicy, expected.ImagePullPolicy) } return nil } assertContainerPort := func(got, expected *v1.Container) error { if len(got.Ports) != len(expected.Ports) { return fmt.Errorf(\"different number of ports: got <%v>, expected <%v>\", len(got.Ports), len(expected.Ports)) } for i := range got.Ports { gp := &got.Ports[i] ep := &expected.Ports[i] if gp.Name != ep.Name { return fmt.Errorf(\"different name of port: got <%v>, expected <%v>\", gp.Name, ep.Name) } if gp.Protocol != ep.Protocol { return fmt.Errorf(\"different port protocol <%v>: got <%v>, expected <%v>\", gp.Name, gp.Protocol, ep.Protocol) } } return nil } assertResource := func(got, expected *v1.Container) error { if len(got.Resources.Limits) != len(expected.Resources.Limits) { return fmt.Errorf(\"different number of resources.Limits: got <%v>, expected <%v>\", len(got.Resources.Limits), (expected.Resources.Limits)) } for k, v := range got.Resources.Limits { if ev, found := expected.Resources.Limits[v1.ResourceName(k)]; !found { return fmt.Errorf(\"failed to find resource <%v> in expected resources.Limits.\", k) } else { if ev.Value() != v.Value() { return fmt.Errorf(\"different resource.Limits: got <%v>, expected <%v>.\", v.Value(), ev.Value()) } } } if len(got.Resources.Requests) != len(expected.Resources.Requests) { return fmt.Errorf(\"different number of resources.Requests: got <%v>, expected <%v>\", len(got.Resources.Requests), (expected.Resources.Requests)) } for k, v := range got.Resources.Requests { if ev, found := expected.Resources.Requests[v1.ResourceName(k)]; !found { return fmt.Errorf(\"failed to find resource <%v> in expected resources.Requests.\", k) } else { if ev.Value() != v.Value() { return fmt.Errorf(\"different resource.Requests: got <%v>, expected <%v>.\", v.Value(), ev.Value()) } } } return nil } assertProb := func(got, expected *v1.Container) error { // Assert LivenessProbe if got.LivenessProbe.Handler.HTTPGet.Path != expected.LivenessProbe.Handler.HTTPGet.Path || got.LivenessProbe.Handler.HTTPGet.Scheme != expected.LivenessProbe.Handler.HTTPGet.Scheme || got.LivenessProbe.FailureThreshold != expected.LivenessProbe.FailureThreshold || got.LivenessProbe.SuccessThreshold != expected.LivenessProbe.SuccessThreshold || got.LivenessProbe.PeriodSeconds != expected.LivenessProbe.PeriodSeconds || got.LivenessProbe.TimeoutSeconds != expected.LivenessProbe.TimeoutSeconds { return fmt.Errorf(\"different LivenessProbe: got <%v>, expected <%v>\", got.LivenessProbe, expected.LivenessProbe) } // Assert ReadinessProbe if got.ReadinessProbe.Handler.HTTPGet.Path != expected.ReadinessProbe.Handler.HTTPGet.Path || got.ReadinessProbe.Handler.HTTPGet.Scheme != expected.ReadinessProbe.Handler.HTTPGet.Scheme || got.ReadinessProbe.FailureThreshold != expected.ReadinessProbe.FailureThreshold || got.ReadinessProbe.SuccessThreshold != expected.ReadinessProbe.SuccessThreshold || got.ReadinessProbe.PeriodSeconds != expected.ReadinessProbe.PeriodSeconds || got.ReadinessProbe.TimeoutSeconds != expected.ReadinessProbe.TimeoutSeconds { return fmt.Errorf(\"different ReadinessProbe: got <%v>, expected <%v>\", got.ReadinessProbe, expected.ReadinessProbe) } return nil } assertLifeCycle := func(got, expected *v1.Container) error { if got.Lifecycle.PostStart.HTTPGet.Path != expected.Lifecycle.PostStart.HTTPGet.Path || got.Lifecycle.PostStart.HTTPGet.Scheme != expected.Lifecycle.PostStart.HTTPGet.Scheme { return fmt.Errorf(\"different LifeCycle: got <%v>, expected <%v>\", got.Lifecycle, expected.Lifecycle) } return nil } cpu, _ := resource.ParseQuantity(\"100Gi\") mem, _ := resource.ParseQuantity(\"100Mi\") </ins> tests := []struct { <del> rc               v1.ReplicationController expectPullPolicy v1.PullPolicy </del> <ins> name       string rc         v1.ReplicationController expected   []v1.Container validators []InitContainerValidator </ins> }{ { <ins> name: \"imagePullIPolicy\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"install\", \"image\": \"busybox\" } ]`, }, }, }, }, }, expected: []v1.Container{ { ImagePullPolicy: v1.PullAlways, }, }, validators: []InitContainerValidator{assertImagePullPolicy}, }, { name: \"FieldRef\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"env\": [ { \"name\": \"MY_POD_IP\", \"valueFrom\": { \"fieldRef\": { \"apiVersion\": \"\", \"fieldPath\": \"status.podIP\" } } } ] } ]`, }, }, }, }, }, expected: []v1.Container{ { Env: []v1.EnvVar{ { Name: \"MY_POD_IP\", ValueFrom: &v1.EnvVarSource{ FieldRef: &v1.ObjectFieldSelector{ APIVersion: \"v1\", FieldPath:  \"status.podIP\", }, }, }, }, }, }, validators: []InitContainerValidator{assertEnvFieldRef}, }, { name: \"ContainerPort\", </ins> rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ <del> \"pod.beta.kubernetes.io/init-containers\": string(containersWithoutPullPolicy), </del> <ins> \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"ports\": [ { \"name\": \"default\" } ] } ]`, </ins> }, }, }, }, }, <del> expectPullPolicy: v1.PullAlways, </del> <ins> expected: []v1.Container{ { Ports: []v1.ContainerPort{ { Name:     \"default\", Protocol: v1.ProtocolTCP, }, }, }, }, validators: []InitContainerValidator{assertContainerPort}, </ins> }, { <ins> name: \"Resources\", </ins> rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ <del> \"pod.beta.kubernetes.io/init-containers\": string(containersWithPullPolicy), </del> <ins> \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"resources\": { \"limits\": { \"cpu\": \"100Gi\", \"memory\": \"100Mi\" }, \"requests\": { \"cpu\": \"100Gi\", \"memory\": \"100Mi\" } } } ]`, </ins> }, }, }, }, }, <del> expectPullPolicy: v1.PullIfNotPresent, </del> <ins> expected: []v1.Container{ { Resources: v1.ResourceRequirements{ Limits: v1.ResourceList{ v1.ResourceCPU:    cpu, v1.ResourceMemory: mem, }, Requests: v1.ResourceList{ v1.ResourceCPU:    cpu, v1.ResourceMemory: mem, }, }, }, }, validators: []InitContainerValidator{assertResource}, }, { name: \"Prob\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"livenessProbe\": { \"httpGet\": { \"host\": \"localhost\" } }, \"readinessProbe\": { \"httpGet\": { \"host\": \"localhost\" } } } ]`, }, }, }, }, }, expected: []v1.Container{ { LivenessProbe: &v1.Probe{ Handler: v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, TimeoutSeconds:   1, PeriodSeconds:    10, SuccessThreshold: 1, FailureThreshold: 3, }, ReadinessProbe: &v1.Probe{ Handler: v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, TimeoutSeconds:   1, PeriodSeconds:    10, SuccessThreshold: 1, FailureThreshold: 3, }, }, }, validators: []InitContainerValidator{assertProb}, }, { name: \"LifeCycle\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"lifecycle\": { \"postStart\": { \"httpGet\": { \"host\": \"localhost\" } }, \"preStop\": { \"httpGet\": { \"host\": \"localhost\" } } } } ]`, }, }, }, }, }, expected: []v1.Container{ { Lifecycle: &v1.Lifecycle{ PostStart: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, PreStop: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, }, }, }, validators: []InitContainerValidator{assertLifeCycle}, </ins> }, } <ins> assertInitContainers := func(got, expected []v1.Container, validators []InitContainerValidator) error { if len(got) != len(expected) { return fmt.Errorf(\"different number of init container: got <%d>, expected <%d>\", len(got), len(expected)) } for i := range got { g := &got[i] e := &expected[i] for _, validator := range validators { if err := validator(g, e); err != nil { return err } } } return nil } </ins> for _, test := range tests { rc := &test.rc obj2 := roundTrip(t, runtime.Object(rc))", "positive_passages": [{"docid": "doc-en-kubernetes-a9af1b8339c2af3d5a8899da2b8916e4bc8194e1229dc4a9dc77c862af07f4a9", "text": "Could it be that crio's runc is not updated yet? Edit Build new runc from and it is working now. Think crio hasn't updated it yet with their repository.\nI'm running this version from PPA repo for ubuntu and it fails: could you point to version/commit or whatever helps identify the fixed version/snapshot ? Thanks in advance.\nat the moment it is only fixed upstream. You'd need to build runc manually\nIs there a version of the package on ppa we can downgrade to? On Wed, May 15, 2019, 4:35 AM Giuseppe Scrivano <:\ncould we update the runc version in the PPA repo?\nThank you. I seem them built but nut pushed to ppa yet.\nshould be available now.. let me know..\ncri-o-runc (1.0.0-rc6-1~dev~ubuntu18.04~ppa42) bionic; urgency=medium autobuilt -- Lokesh Mandvekar (Bot) <, 15 May 2019 16:54:40 +0000\nThank you, everyone, for a quick turn around. Quick testing showed that fix is working, but more testing is needed. Lokesh Mandvekar <:\nI confirm my initial tests with seem to confirm the regression is fixed. Many thanks\nI also confirm the fix working for podman. Olivier Berger <:", "commid": "kubernetes_issue_77615", "tokennum": 305}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dff085188705c1afb0e99c2fe73ac9ecf92fc2494c676dc1ed7efedb43e99495", "query": "} } <del> func TestSetDefaultReplicationControllerImagePullPolicy(t *testing.T) { containersWithoutPullPolicy, _ := json.Marshal([]map[string]interface{}{ { \"name\":  \"install\", \"image\": \"busybox:latest\", }, }) </del> <ins> type InitContainerValidator func(got, expected *v1.Container) error </ins> <del> containersWithPullPolicy, _ := json.Marshal([]map[string]interface{}{ { \"name\":            \"install\", \"imagePullPolicy\": \"IfNotPresent\", }, }) </del> <ins> func TestSetDefaultReplicationControllerInitContainers(t *testing.T) { assertEnvFieldRef := func(got, expected *v1.Container) error { if len(got.Env) != len(expected.Env) { return fmt.Errorf(\"different number of env: got <%v>, expected <%v>\", len(got.Env), len(expected.Env)) } for j := range got.Env { ge := &got.Env[j] ee := &expected.Env[j] if ge.Name != ee.Name { return fmt.Errorf(\"different name of env: got <%v>, expected <%v>\", ge.Name, ee.Name) } if ge.ValueFrom.FieldRef.APIVersion != ee.ValueFrom.FieldRef.APIVersion { return fmt.Errorf(\"different api version of FieldRef <%v>: got <%v>, expected <%v>\", ge.Name, ge.ValueFrom.FieldRef.APIVersion, ee.ValueFrom.FieldRef.APIVersion) } } return nil } assertImagePullPolicy := func(got, expected *v1.Container) error { if got.ImagePullPolicy != expected.ImagePullPolicy { return fmt.Errorf(\"different image pull poicy: got <%v>, expected <%v>\", got.ImagePullPolicy, expected.ImagePullPolicy) } return nil } assertContainerPort := func(got, expected *v1.Container) error { if len(got.Ports) != len(expected.Ports) { return fmt.Errorf(\"different number of ports: got <%v>, expected <%v>\", len(got.Ports), len(expected.Ports)) } for i := range got.Ports { gp := &got.Ports[i] ep := &expected.Ports[i] if gp.Name != ep.Name { return fmt.Errorf(\"different name of port: got <%v>, expected <%v>\", gp.Name, ep.Name) } if gp.Protocol != ep.Protocol { return fmt.Errorf(\"different port protocol <%v>: got <%v>, expected <%v>\", gp.Name, gp.Protocol, ep.Protocol) } } return nil } assertResource := func(got, expected *v1.Container) error { if len(got.Resources.Limits) != len(expected.Resources.Limits) { return fmt.Errorf(\"different number of resources.Limits: got <%v>, expected <%v>\", len(got.Resources.Limits), (expected.Resources.Limits)) } for k, v := range got.Resources.Limits { if ev, found := expected.Resources.Limits[v1.ResourceName(k)]; !found { return fmt.Errorf(\"failed to find resource <%v> in expected resources.Limits.\", k) } else { if ev.Value() != v.Value() { return fmt.Errorf(\"different resource.Limits: got <%v>, expected <%v>.\", v.Value(), ev.Value()) } } } if len(got.Resources.Requests) != len(expected.Resources.Requests) { return fmt.Errorf(\"different number of resources.Requests: got <%v>, expected <%v>\", len(got.Resources.Requests), (expected.Resources.Requests)) } for k, v := range got.Resources.Requests { if ev, found := expected.Resources.Requests[v1.ResourceName(k)]; !found { return fmt.Errorf(\"failed to find resource <%v> in expected resources.Requests.\", k) } else { if ev.Value() != v.Value() { return fmt.Errorf(\"different resource.Requests: got <%v>, expected <%v>.\", v.Value(), ev.Value()) } } } return nil } assertProb := func(got, expected *v1.Container) error { // Assert LivenessProbe if got.LivenessProbe.Handler.HTTPGet.Path != expected.LivenessProbe.Handler.HTTPGet.Path || got.LivenessProbe.Handler.HTTPGet.Scheme != expected.LivenessProbe.Handler.HTTPGet.Scheme || got.LivenessProbe.FailureThreshold != expected.LivenessProbe.FailureThreshold || got.LivenessProbe.SuccessThreshold != expected.LivenessProbe.SuccessThreshold || got.LivenessProbe.PeriodSeconds != expected.LivenessProbe.PeriodSeconds || got.LivenessProbe.TimeoutSeconds != expected.LivenessProbe.TimeoutSeconds { return fmt.Errorf(\"different LivenessProbe: got <%v>, expected <%v>\", got.LivenessProbe, expected.LivenessProbe) } // Assert ReadinessProbe if got.ReadinessProbe.Handler.HTTPGet.Path != expected.ReadinessProbe.Handler.HTTPGet.Path || got.ReadinessProbe.Handler.HTTPGet.Scheme != expected.ReadinessProbe.Handler.HTTPGet.Scheme || got.ReadinessProbe.FailureThreshold != expected.ReadinessProbe.FailureThreshold || got.ReadinessProbe.SuccessThreshold != expected.ReadinessProbe.SuccessThreshold || got.ReadinessProbe.PeriodSeconds != expected.ReadinessProbe.PeriodSeconds || got.ReadinessProbe.TimeoutSeconds != expected.ReadinessProbe.TimeoutSeconds { return fmt.Errorf(\"different ReadinessProbe: got <%v>, expected <%v>\", got.ReadinessProbe, expected.ReadinessProbe) } return nil } assertLifeCycle := func(got, expected *v1.Container) error { if got.Lifecycle.PostStart.HTTPGet.Path != expected.Lifecycle.PostStart.HTTPGet.Path || got.Lifecycle.PostStart.HTTPGet.Scheme != expected.Lifecycle.PostStart.HTTPGet.Scheme { return fmt.Errorf(\"different LifeCycle: got <%v>, expected <%v>\", got.Lifecycle, expected.Lifecycle) } return nil } cpu, _ := resource.ParseQuantity(\"100Gi\") mem, _ := resource.ParseQuantity(\"100Mi\") </ins> tests := []struct { <del> rc               v1.ReplicationController expectPullPolicy v1.PullPolicy </del> <ins> name       string rc         v1.ReplicationController expected   []v1.Container validators []InitContainerValidator </ins> }{ { <ins> name: \"imagePullIPolicy\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"install\", \"image\": \"busybox\" } ]`, }, }, }, }, }, expected: []v1.Container{ { ImagePullPolicy: v1.PullAlways, }, }, validators: []InitContainerValidator{assertImagePullPolicy}, }, { name: \"FieldRef\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"env\": [ { \"name\": \"MY_POD_IP\", \"valueFrom\": { \"fieldRef\": { \"apiVersion\": \"\", \"fieldPath\": \"status.podIP\" } } } ] } ]`, }, }, }, }, }, expected: []v1.Container{ { Env: []v1.EnvVar{ { Name: \"MY_POD_IP\", ValueFrom: &v1.EnvVarSource{ FieldRef: &v1.ObjectFieldSelector{ APIVersion: \"v1\", FieldPath:  \"status.podIP\", }, }, }, }, }, }, validators: []InitContainerValidator{assertEnvFieldRef}, }, { name: \"ContainerPort\", </ins> rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ <del> \"pod.beta.kubernetes.io/init-containers\": string(containersWithoutPullPolicy), </del> <ins> \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"ports\": [ { \"name\": \"default\" } ] } ]`, </ins> }, }, }, }, }, <del> expectPullPolicy: v1.PullAlways, </del> <ins> expected: []v1.Container{ { Ports: []v1.ContainerPort{ { Name:     \"default\", Protocol: v1.ProtocolTCP, }, }, }, }, validators: []InitContainerValidator{assertContainerPort}, </ins> }, { <ins> name: \"Resources\", </ins> rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ <del> \"pod.beta.kubernetes.io/init-containers\": string(containersWithPullPolicy), </del> <ins> \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"resources\": { \"limits\": { \"cpu\": \"100Gi\", \"memory\": \"100Mi\" }, \"requests\": { \"cpu\": \"100Gi\", \"memory\": \"100Mi\" } } } ]`, </ins> }, }, }, }, }, <del> expectPullPolicy: v1.PullIfNotPresent, </del> <ins> expected: []v1.Container{ { Resources: v1.ResourceRequirements{ Limits: v1.ResourceList{ v1.ResourceCPU:    cpu, v1.ResourceMemory: mem, }, Requests: v1.ResourceList{ v1.ResourceCPU:    cpu, v1.ResourceMemory: mem, }, }, }, }, validators: []InitContainerValidator{assertResource}, }, { name: \"Prob\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"livenessProbe\": { \"httpGet\": { \"host\": \"localhost\" } }, \"readinessProbe\": { \"httpGet\": { \"host\": \"localhost\" } } } ]`, }, }, }, }, }, expected: []v1.Container{ { LivenessProbe: &v1.Probe{ Handler: v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, TimeoutSeconds:   1, PeriodSeconds:    10, SuccessThreshold: 1, FailureThreshold: 3, }, ReadinessProbe: &v1.Probe{ Handler: v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, TimeoutSeconds:   1, PeriodSeconds:    10, SuccessThreshold: 1, FailureThreshold: 3, }, }, }, validators: []InitContainerValidator{assertProb}, }, { name: \"LifeCycle\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"lifecycle\": { \"postStart\": { \"httpGet\": { \"host\": \"localhost\" } }, \"preStop\": { \"httpGet\": { \"host\": \"localhost\" } } } } ]`, }, }, }, }, }, expected: []v1.Container{ { Lifecycle: &v1.Lifecycle{ PostStart: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, PreStop: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, }, }, }, validators: []InitContainerValidator{assertLifeCycle}, </ins> }, } <ins> assertInitContainers := func(got, expected []v1.Container, validators []InitContainerValidator) error { if len(got) != len(expected) { return fmt.Errorf(\"different number of init container: got <%d>, expected <%d>\", len(got), len(expected)) } for i := range got { g := &got[i] e := &expected[i] for _, validator := range validators { if err := validator(g, e); err != nil { return err } } } return nil } </ins> for _, test := range tests { rc := &test.rc obj2 := roundTrip(t, runtime.Object(rc))", "positive_passages": [{"docid": "doc-en-kubernetes-c1c167f97d0d68a2d507d0d919d58cd680ff8ed576e3225c7b24d703a964bd61", "text": "<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.--Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see ): No What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): initContainers imagePullPolicy initContainers required value Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT <!-- If this is a BUG REPORT, please: Fill in as much of the template below as you can. If you leave out information, we can't help you as well. If this is a FEATURE REQUEST, please: Describe in detail the feature/behavior/change you'd like to see. In both cases, be ready for followup questions, and please respond in a timely manner. If we can't reproduce a bug or think a feature already exists, we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why. --Kubernetes version (use ): Environment: Cloud provider or hardware configuration: GCE OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: cluster/kube- Others: What happened: When trying to create either a ReplicaSet or Replication Controller whose Pod template contains an Init Container, the validation fails saying is a required value. What you expected to happen: The create should succeed and the Init Container should receive a default . How to reproduce it (as minimally and precisely as possible): Try to create either of the following: ReplicaSet Replication Controller Anything else do we need to know: If I add to the Init Container in the ReplicaSet or Replication Controller Pod template, the create succeeds. When I create an Init Container without in a StatefulSet Pod template, it succeeds. When I create an Init Container without in a bare Pod, it succeeds:\nLooks like defaulting not being applied on server? That is probably due to removing defaulting from convert. Surprised we didn't catch this earlier\nSome values still not being defaulted\n, I'm going to create a PR if none works on it.\nWe decode from bytes, set defaults and then convert; but for init containers, we delay the decode from \"decode phase\" to \"convert phase\" at .", "commid": "kubernetes_issue_38542", "tokennum": 524}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dff085188705c1afb0e99c2fe73ac9ecf92fc2494c676dc1ed7efedb43e99495", "query": "} } <del> func TestSetDefaultReplicationControllerImagePullPolicy(t *testing.T) { containersWithoutPullPolicy, _ := json.Marshal([]map[string]interface{}{ { \"name\":  \"install\", \"image\": \"busybox:latest\", }, }) </del> <ins> type InitContainerValidator func(got, expected *v1.Container) error </ins> <del> containersWithPullPolicy, _ := json.Marshal([]map[string]interface{}{ { \"name\":            \"install\", \"imagePullPolicy\": \"IfNotPresent\", }, }) </del> <ins> func TestSetDefaultReplicationControllerInitContainers(t *testing.T) { assertEnvFieldRef := func(got, expected *v1.Container) error { if len(got.Env) != len(expected.Env) { return fmt.Errorf(\"different number of env: got <%v>, expected <%v>\", len(got.Env), len(expected.Env)) } for j := range got.Env { ge := &got.Env[j] ee := &expected.Env[j] if ge.Name != ee.Name { return fmt.Errorf(\"different name of env: got <%v>, expected <%v>\", ge.Name, ee.Name) } if ge.ValueFrom.FieldRef.APIVersion != ee.ValueFrom.FieldRef.APIVersion { return fmt.Errorf(\"different api version of FieldRef <%v>: got <%v>, expected <%v>\", ge.Name, ge.ValueFrom.FieldRef.APIVersion, ee.ValueFrom.FieldRef.APIVersion) } } return nil } assertImagePullPolicy := func(got, expected *v1.Container) error { if got.ImagePullPolicy != expected.ImagePullPolicy { return fmt.Errorf(\"different image pull poicy: got <%v>, expected <%v>\", got.ImagePullPolicy, expected.ImagePullPolicy) } return nil } assertContainerPort := func(got, expected *v1.Container) error { if len(got.Ports) != len(expected.Ports) { return fmt.Errorf(\"different number of ports: got <%v>, expected <%v>\", len(got.Ports), len(expected.Ports)) } for i := range got.Ports { gp := &got.Ports[i] ep := &expected.Ports[i] if gp.Name != ep.Name { return fmt.Errorf(\"different name of port: got <%v>, expected <%v>\", gp.Name, ep.Name) } if gp.Protocol != ep.Protocol { return fmt.Errorf(\"different port protocol <%v>: got <%v>, expected <%v>\", gp.Name, gp.Protocol, ep.Protocol) } } return nil } assertResource := func(got, expected *v1.Container) error { if len(got.Resources.Limits) != len(expected.Resources.Limits) { return fmt.Errorf(\"different number of resources.Limits: got <%v>, expected <%v>\", len(got.Resources.Limits), (expected.Resources.Limits)) } for k, v := range got.Resources.Limits { if ev, found := expected.Resources.Limits[v1.ResourceName(k)]; !found { return fmt.Errorf(\"failed to find resource <%v> in expected resources.Limits.\", k) } else { if ev.Value() != v.Value() { return fmt.Errorf(\"different resource.Limits: got <%v>, expected <%v>.\", v.Value(), ev.Value()) } } } if len(got.Resources.Requests) != len(expected.Resources.Requests) { return fmt.Errorf(\"different number of resources.Requests: got <%v>, expected <%v>\", len(got.Resources.Requests), (expected.Resources.Requests)) } for k, v := range got.Resources.Requests { if ev, found := expected.Resources.Requests[v1.ResourceName(k)]; !found { return fmt.Errorf(\"failed to find resource <%v> in expected resources.Requests.\", k) } else { if ev.Value() != v.Value() { return fmt.Errorf(\"different resource.Requests: got <%v>, expected <%v>.\", v.Value(), ev.Value()) } } } return nil } assertProb := func(got, expected *v1.Container) error { // Assert LivenessProbe if got.LivenessProbe.Handler.HTTPGet.Path != expected.LivenessProbe.Handler.HTTPGet.Path || got.LivenessProbe.Handler.HTTPGet.Scheme != expected.LivenessProbe.Handler.HTTPGet.Scheme || got.LivenessProbe.FailureThreshold != expected.LivenessProbe.FailureThreshold || got.LivenessProbe.SuccessThreshold != expected.LivenessProbe.SuccessThreshold || got.LivenessProbe.PeriodSeconds != expected.LivenessProbe.PeriodSeconds || got.LivenessProbe.TimeoutSeconds != expected.LivenessProbe.TimeoutSeconds { return fmt.Errorf(\"different LivenessProbe: got <%v>, expected <%v>\", got.LivenessProbe, expected.LivenessProbe) } // Assert ReadinessProbe if got.ReadinessProbe.Handler.HTTPGet.Path != expected.ReadinessProbe.Handler.HTTPGet.Path || got.ReadinessProbe.Handler.HTTPGet.Scheme != expected.ReadinessProbe.Handler.HTTPGet.Scheme || got.ReadinessProbe.FailureThreshold != expected.ReadinessProbe.FailureThreshold || got.ReadinessProbe.SuccessThreshold != expected.ReadinessProbe.SuccessThreshold || got.ReadinessProbe.PeriodSeconds != expected.ReadinessProbe.PeriodSeconds || got.ReadinessProbe.TimeoutSeconds != expected.ReadinessProbe.TimeoutSeconds { return fmt.Errorf(\"different ReadinessProbe: got <%v>, expected <%v>\", got.ReadinessProbe, expected.ReadinessProbe) } return nil } assertLifeCycle := func(got, expected *v1.Container) error { if got.Lifecycle.PostStart.HTTPGet.Path != expected.Lifecycle.PostStart.HTTPGet.Path || got.Lifecycle.PostStart.HTTPGet.Scheme != expected.Lifecycle.PostStart.HTTPGet.Scheme { return fmt.Errorf(\"different LifeCycle: got <%v>, expected <%v>\", got.Lifecycle, expected.Lifecycle) } return nil } cpu, _ := resource.ParseQuantity(\"100Gi\") mem, _ := resource.ParseQuantity(\"100Mi\") </ins> tests := []struct { <del> rc               v1.ReplicationController expectPullPolicy v1.PullPolicy </del> <ins> name       string rc         v1.ReplicationController expected   []v1.Container validators []InitContainerValidator </ins> }{ { <ins> name: \"imagePullIPolicy\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"install\", \"image\": \"busybox\" } ]`, }, }, }, }, }, expected: []v1.Container{ { ImagePullPolicy: v1.PullAlways, }, }, validators: []InitContainerValidator{assertImagePullPolicy}, }, { name: \"FieldRef\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"env\": [ { \"name\": \"MY_POD_IP\", \"valueFrom\": { \"fieldRef\": { \"apiVersion\": \"\", \"fieldPath\": \"status.podIP\" } } } ] } ]`, }, }, }, }, }, expected: []v1.Container{ { Env: []v1.EnvVar{ { Name: \"MY_POD_IP\", ValueFrom: &v1.EnvVarSource{ FieldRef: &v1.ObjectFieldSelector{ APIVersion: \"v1\", FieldPath:  \"status.podIP\", }, }, }, }, }, }, validators: []InitContainerValidator{assertEnvFieldRef}, }, { name: \"ContainerPort\", </ins> rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ <del> \"pod.beta.kubernetes.io/init-containers\": string(containersWithoutPullPolicy), </del> <ins> \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"ports\": [ { \"name\": \"default\" } ] } ]`, </ins> }, }, }, }, }, <del> expectPullPolicy: v1.PullAlways, </del> <ins> expected: []v1.Container{ { Ports: []v1.ContainerPort{ { Name:     \"default\", Protocol: v1.ProtocolTCP, }, }, }, }, validators: []InitContainerValidator{assertContainerPort}, </ins> }, { <ins> name: \"Resources\", </ins> rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ <del> \"pod.beta.kubernetes.io/init-containers\": string(containersWithPullPolicy), </del> <ins> \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"resources\": { \"limits\": { \"cpu\": \"100Gi\", \"memory\": \"100Mi\" }, \"requests\": { \"cpu\": \"100Gi\", \"memory\": \"100Mi\" } } } ]`, </ins> }, }, }, }, }, <del> expectPullPolicy: v1.PullIfNotPresent, </del> <ins> expected: []v1.Container{ { Resources: v1.ResourceRequirements{ Limits: v1.ResourceList{ v1.ResourceCPU:    cpu, v1.ResourceMemory: mem, }, Requests: v1.ResourceList{ v1.ResourceCPU:    cpu, v1.ResourceMemory: mem, }, }, }, }, validators: []InitContainerValidator{assertResource}, }, { name: \"Prob\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"livenessProbe\": { \"httpGet\": { \"host\": \"localhost\" } }, \"readinessProbe\": { \"httpGet\": { \"host\": \"localhost\" } } } ]`, }, }, }, }, }, expected: []v1.Container{ { LivenessProbe: &v1.Probe{ Handler: v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, TimeoutSeconds:   1, PeriodSeconds:    10, SuccessThreshold: 1, FailureThreshold: 3, }, ReadinessProbe: &v1.Probe{ Handler: v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, TimeoutSeconds:   1, PeriodSeconds:    10, SuccessThreshold: 1, FailureThreshold: 3, }, }, }, validators: []InitContainerValidator{assertProb}, }, { name: \"LifeCycle\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"lifecycle\": { \"postStart\": { \"httpGet\": { \"host\": \"localhost\" } }, \"preStop\": { \"httpGet\": { \"host\": \"localhost\" } } } } ]`, }, }, }, }, }, expected: []v1.Container{ { Lifecycle: &v1.Lifecycle{ PostStart: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, PreStop: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, }, }, }, validators: []InitContainerValidator{assertLifeCycle}, </ins> }, } <ins> assertInitContainers := func(got, expected []v1.Container, validators []InitContainerValidator) error { if len(got) != len(expected) { return fmt.Errorf(\"different number of init container: got <%d>, expected <%d>\", len(got), len(expected)) } for i := range got { g := &got[i] e := &expected[i] for _, validator := range validators { if err := validator(g, e); err != nil { return err } } } return nil } </ins> for _, test := range tests { rc := &test.rc obj2 := roundTrip(t, runtime.Object(rc))", "positive_passages": [{"docid": "doc-en-kubernetes-69dbac4fd7f4ee2d4feb0af6994cc2f74e65b4d3465b8e0c7014cfb5909cea9b", "text": "The defaults has been handled for initContainer at . /cc I'm working to find a solution for that; if any suggestion, please let me know.\nWould this bug affect the deletion of jobs with an init-container? I ran into this bug and adjusted my manifest to add the pull policy to the init-container. However, I now cannot delete said job claiming a field is immutable. Example:\n, not sure now. Let me check it,\nSame error here with version 1.5.1, 1.5.2 The Job \"grafana-import-dashboards\" is invalid: [0].imagePullPolicy: Required value With this setup: kubectl apply -f monitoring Not working even if I specify a pullpolicy in the yaml. If I roll back to 1.4.7, it is working. Thank you. Greg.\nany updates on a PR to address this issue? Is anyone from able to pick this issue up otherwise?\n, here's the latest status: there's is a PR to generate for each Object (), it works for Object (Pod, Job) now but List; I'm working to make it generating for List.\nWhy would you need List to work? No client side logic should be decoding lists except as a generic submission.\nThe List tests are failed in . There's no for List, so no code to decode init-container annotation, e.g. of should call 's recursively.\nThanks for the update\n+1\nAny update on this? I still getting this issue with the last version of 1.5.3 on GKE?\nping for the comments? should we merge the PR for 1.5?\n, there's a PR () that handled that issue; but we're discussing not to merge it because initContainers had been moved to fields, and fields is the recommended way to use since 1.6. But I'd like to get & 's comments on 1.5.\nThis is still an issue in 1.5.3 when using annotations: Without the deployment would not be accepted\nping & :).\ni dont think this is fixed in 1.5 I just encountered this bug on 1.5.3\n, yes, the PR is NOT merged to any branch, so the issue is still here. I'll create a PR for 1.5.\nHi Anyone help this issue.", "commid": "kubernetes_issue_38542", "tokennum": 520}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dff085188705c1afb0e99c2fe73ac9ecf92fc2494c676dc1ed7efedb43e99495", "query": "} } <del> func TestSetDefaultReplicationControllerImagePullPolicy(t *testing.T) { containersWithoutPullPolicy, _ := json.Marshal([]map[string]interface{}{ { \"name\":  \"install\", \"image\": \"busybox:latest\", }, }) </del> <ins> type InitContainerValidator func(got, expected *v1.Container) error </ins> <del> containersWithPullPolicy, _ := json.Marshal([]map[string]interface{}{ { \"name\":            \"install\", \"imagePullPolicy\": \"IfNotPresent\", }, }) </del> <ins> func TestSetDefaultReplicationControllerInitContainers(t *testing.T) { assertEnvFieldRef := func(got, expected *v1.Container) error { if len(got.Env) != len(expected.Env) { return fmt.Errorf(\"different number of env: got <%v>, expected <%v>\", len(got.Env), len(expected.Env)) } for j := range got.Env { ge := &got.Env[j] ee := &expected.Env[j] if ge.Name != ee.Name { return fmt.Errorf(\"different name of env: got <%v>, expected <%v>\", ge.Name, ee.Name) } if ge.ValueFrom.FieldRef.APIVersion != ee.ValueFrom.FieldRef.APIVersion { return fmt.Errorf(\"different api version of FieldRef <%v>: got <%v>, expected <%v>\", ge.Name, ge.ValueFrom.FieldRef.APIVersion, ee.ValueFrom.FieldRef.APIVersion) } } return nil } assertImagePullPolicy := func(got, expected *v1.Container) error { if got.ImagePullPolicy != expected.ImagePullPolicy { return fmt.Errorf(\"different image pull poicy: got <%v>, expected <%v>\", got.ImagePullPolicy, expected.ImagePullPolicy) } return nil } assertContainerPort := func(got, expected *v1.Container) error { if len(got.Ports) != len(expected.Ports) { return fmt.Errorf(\"different number of ports: got <%v>, expected <%v>\", len(got.Ports), len(expected.Ports)) } for i := range got.Ports { gp := &got.Ports[i] ep := &expected.Ports[i] if gp.Name != ep.Name { return fmt.Errorf(\"different name of port: got <%v>, expected <%v>\", gp.Name, ep.Name) } if gp.Protocol != ep.Protocol { return fmt.Errorf(\"different port protocol <%v>: got <%v>, expected <%v>\", gp.Name, gp.Protocol, ep.Protocol) } } return nil } assertResource := func(got, expected *v1.Container) error { if len(got.Resources.Limits) != len(expected.Resources.Limits) { return fmt.Errorf(\"different number of resources.Limits: got <%v>, expected <%v>\", len(got.Resources.Limits), (expected.Resources.Limits)) } for k, v := range got.Resources.Limits { if ev, found := expected.Resources.Limits[v1.ResourceName(k)]; !found { return fmt.Errorf(\"failed to find resource <%v> in expected resources.Limits.\", k) } else { if ev.Value() != v.Value() { return fmt.Errorf(\"different resource.Limits: got <%v>, expected <%v>.\", v.Value(), ev.Value()) } } } if len(got.Resources.Requests) != len(expected.Resources.Requests) { return fmt.Errorf(\"different number of resources.Requests: got <%v>, expected <%v>\", len(got.Resources.Requests), (expected.Resources.Requests)) } for k, v := range got.Resources.Requests { if ev, found := expected.Resources.Requests[v1.ResourceName(k)]; !found { return fmt.Errorf(\"failed to find resource <%v> in expected resources.Requests.\", k) } else { if ev.Value() != v.Value() { return fmt.Errorf(\"different resource.Requests: got <%v>, expected <%v>.\", v.Value(), ev.Value()) } } } return nil } assertProb := func(got, expected *v1.Container) error { // Assert LivenessProbe if got.LivenessProbe.Handler.HTTPGet.Path != expected.LivenessProbe.Handler.HTTPGet.Path || got.LivenessProbe.Handler.HTTPGet.Scheme != expected.LivenessProbe.Handler.HTTPGet.Scheme || got.LivenessProbe.FailureThreshold != expected.LivenessProbe.FailureThreshold || got.LivenessProbe.SuccessThreshold != expected.LivenessProbe.SuccessThreshold || got.LivenessProbe.PeriodSeconds != expected.LivenessProbe.PeriodSeconds || got.LivenessProbe.TimeoutSeconds != expected.LivenessProbe.TimeoutSeconds { return fmt.Errorf(\"different LivenessProbe: got <%v>, expected <%v>\", got.LivenessProbe, expected.LivenessProbe) } // Assert ReadinessProbe if got.ReadinessProbe.Handler.HTTPGet.Path != expected.ReadinessProbe.Handler.HTTPGet.Path || got.ReadinessProbe.Handler.HTTPGet.Scheme != expected.ReadinessProbe.Handler.HTTPGet.Scheme || got.ReadinessProbe.FailureThreshold != expected.ReadinessProbe.FailureThreshold || got.ReadinessProbe.SuccessThreshold != expected.ReadinessProbe.SuccessThreshold || got.ReadinessProbe.PeriodSeconds != expected.ReadinessProbe.PeriodSeconds || got.ReadinessProbe.TimeoutSeconds != expected.ReadinessProbe.TimeoutSeconds { return fmt.Errorf(\"different ReadinessProbe: got <%v>, expected <%v>\", got.ReadinessProbe, expected.ReadinessProbe) } return nil } assertLifeCycle := func(got, expected *v1.Container) error { if got.Lifecycle.PostStart.HTTPGet.Path != expected.Lifecycle.PostStart.HTTPGet.Path || got.Lifecycle.PostStart.HTTPGet.Scheme != expected.Lifecycle.PostStart.HTTPGet.Scheme { return fmt.Errorf(\"different LifeCycle: got <%v>, expected <%v>\", got.Lifecycle, expected.Lifecycle) } return nil } cpu, _ := resource.ParseQuantity(\"100Gi\") mem, _ := resource.ParseQuantity(\"100Mi\") </ins> tests := []struct { <del> rc               v1.ReplicationController expectPullPolicy v1.PullPolicy </del> <ins> name       string rc         v1.ReplicationController expected   []v1.Container validators []InitContainerValidator </ins> }{ { <ins> name: \"imagePullIPolicy\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"install\", \"image\": \"busybox\" } ]`, }, }, }, }, }, expected: []v1.Container{ { ImagePullPolicy: v1.PullAlways, }, }, validators: []InitContainerValidator{assertImagePullPolicy}, }, { name: \"FieldRef\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"env\": [ { \"name\": \"MY_POD_IP\", \"valueFrom\": { \"fieldRef\": { \"apiVersion\": \"\", \"fieldPath\": \"status.podIP\" } } } ] } ]`, }, }, }, }, }, expected: []v1.Container{ { Env: []v1.EnvVar{ { Name: \"MY_POD_IP\", ValueFrom: &v1.EnvVarSource{ FieldRef: &v1.ObjectFieldSelector{ APIVersion: \"v1\", FieldPath:  \"status.podIP\", }, }, }, }, }, }, validators: []InitContainerValidator{assertEnvFieldRef}, }, { name: \"ContainerPort\", </ins> rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ <del> \"pod.beta.kubernetes.io/init-containers\": string(containersWithoutPullPolicy), </del> <ins> \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"ports\": [ { \"name\": \"default\" } ] } ]`, </ins> }, }, }, }, }, <del> expectPullPolicy: v1.PullAlways, </del> <ins> expected: []v1.Container{ { Ports: []v1.ContainerPort{ { Name:     \"default\", Protocol: v1.ProtocolTCP, }, }, }, }, validators: []InitContainerValidator{assertContainerPort}, </ins> }, { <ins> name: \"Resources\", </ins> rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ <del> \"pod.beta.kubernetes.io/init-containers\": string(containersWithPullPolicy), </del> <ins> \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"resources\": { \"limits\": { \"cpu\": \"100Gi\", \"memory\": \"100Mi\" }, \"requests\": { \"cpu\": \"100Gi\", \"memory\": \"100Mi\" } } } ]`, </ins> }, }, }, }, }, <del> expectPullPolicy: v1.PullIfNotPresent, </del> <ins> expected: []v1.Container{ { Resources: v1.ResourceRequirements{ Limits: v1.ResourceList{ v1.ResourceCPU:    cpu, v1.ResourceMemory: mem, }, Requests: v1.ResourceList{ v1.ResourceCPU:    cpu, v1.ResourceMemory: mem, }, }, }, }, validators: []InitContainerValidator{assertResource}, }, { name: \"Prob\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"livenessProbe\": { \"httpGet\": { \"host\": \"localhost\" } }, \"readinessProbe\": { \"httpGet\": { \"host\": \"localhost\" } } } ]`, }, }, }, }, }, expected: []v1.Container{ { LivenessProbe: &v1.Probe{ Handler: v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, TimeoutSeconds:   1, PeriodSeconds:    10, SuccessThreshold: 1, FailureThreshold: 3, }, ReadinessProbe: &v1.Probe{ Handler: v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, TimeoutSeconds:   1, PeriodSeconds:    10, SuccessThreshold: 1, FailureThreshold: 3, }, }, }, validators: []InitContainerValidator{assertProb}, }, { name: \"LifeCycle\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"lifecycle\": { \"postStart\": { \"httpGet\": { \"host\": \"localhost\" } }, \"preStop\": { \"httpGet\": { \"host\": \"localhost\" } } } } ]`, }, }, }, }, }, expected: []v1.Container{ { Lifecycle: &v1.Lifecycle{ PostStart: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, PreStop: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, }, }, }, validators: []InitContainerValidator{assertLifeCycle}, </ins> }, } <ins> assertInitContainers := func(got, expected []v1.Container, validators []InitContainerValidator) error { if len(got) != len(expected) { return fmt.Errorf(\"different number of init container: got <%d>, expected <%d>\", len(got), len(expected)) } for i := range got { g := &got[i] e := &expected[i] for _, validator := range validators { if err := validator(g, e); err != nil { return err } } } return nil } </ins> for _, test := range tests { rc := &test.rc obj2 := roundTrip(t, runtime.Object(rc))", "positive_passages": [{"docid": "doc-en-kubernetes-cd1dc8216bffde40e45195a0aceb1bbd0c560296ad557f563dafcf3df89eeea5", "text": "#cat mongo- apiVersion: v1 kind: Pod metadata: labels: name: mongo-svc-a name: mongo-deployment spec: replicas: 1 template: metadata: labels: name: mongo spec: containers: image: mongo name: mongo ports: name: mongo containerPort: hostPort: volumeMounts: mountPath: \"/data/db\" name: mongopv volumes: name: mongopv persistentVolumeClaim: claimName: mongopvc When i want create mongo db container by using this file folowing error is occured. The Pod \"mongo-deployment\" is invalid:spec.containers: Required value\n, it seems there're two here, please remove the first one and have a try.\nHi my kubectl binary is configured at ubuntu 16.04 machine.", "commid": "kubernetes_issue_38542", "tokennum": 188}], "negative_passages": []}
{"query_id": "q-en-kubernetes-dff085188705c1afb0e99c2fe73ac9ecf92fc2494c676dc1ed7efedb43e99495", "query": "} } <del> func TestSetDefaultReplicationControllerImagePullPolicy(t *testing.T) { containersWithoutPullPolicy, _ := json.Marshal([]map[string]interface{}{ { \"name\":  \"install\", \"image\": \"busybox:latest\", }, }) </del> <ins> type InitContainerValidator func(got, expected *v1.Container) error </ins> <del> containersWithPullPolicy, _ := json.Marshal([]map[string]interface{}{ { \"name\":            \"install\", \"imagePullPolicy\": \"IfNotPresent\", }, }) </del> <ins> func TestSetDefaultReplicationControllerInitContainers(t *testing.T) { assertEnvFieldRef := func(got, expected *v1.Container) error { if len(got.Env) != len(expected.Env) { return fmt.Errorf(\"different number of env: got <%v>, expected <%v>\", len(got.Env), len(expected.Env)) } for j := range got.Env { ge := &got.Env[j] ee := &expected.Env[j] if ge.Name != ee.Name { return fmt.Errorf(\"different name of env: got <%v>, expected <%v>\", ge.Name, ee.Name) } if ge.ValueFrom.FieldRef.APIVersion != ee.ValueFrom.FieldRef.APIVersion { return fmt.Errorf(\"different api version of FieldRef <%v>: got <%v>, expected <%v>\", ge.Name, ge.ValueFrom.FieldRef.APIVersion, ee.ValueFrom.FieldRef.APIVersion) } } return nil } assertImagePullPolicy := func(got, expected *v1.Container) error { if got.ImagePullPolicy != expected.ImagePullPolicy { return fmt.Errorf(\"different image pull poicy: got <%v>, expected <%v>\", got.ImagePullPolicy, expected.ImagePullPolicy) } return nil } assertContainerPort := func(got, expected *v1.Container) error { if len(got.Ports) != len(expected.Ports) { return fmt.Errorf(\"different number of ports: got <%v>, expected <%v>\", len(got.Ports), len(expected.Ports)) } for i := range got.Ports { gp := &got.Ports[i] ep := &expected.Ports[i] if gp.Name != ep.Name { return fmt.Errorf(\"different name of port: got <%v>, expected <%v>\", gp.Name, ep.Name) } if gp.Protocol != ep.Protocol { return fmt.Errorf(\"different port protocol <%v>: got <%v>, expected <%v>\", gp.Name, gp.Protocol, ep.Protocol) } } return nil } assertResource := func(got, expected *v1.Container) error { if len(got.Resources.Limits) != len(expected.Resources.Limits) { return fmt.Errorf(\"different number of resources.Limits: got <%v>, expected <%v>\", len(got.Resources.Limits), (expected.Resources.Limits)) } for k, v := range got.Resources.Limits { if ev, found := expected.Resources.Limits[v1.ResourceName(k)]; !found { return fmt.Errorf(\"failed to find resource <%v> in expected resources.Limits.\", k) } else { if ev.Value() != v.Value() { return fmt.Errorf(\"different resource.Limits: got <%v>, expected <%v>.\", v.Value(), ev.Value()) } } } if len(got.Resources.Requests) != len(expected.Resources.Requests) { return fmt.Errorf(\"different number of resources.Requests: got <%v>, expected <%v>\", len(got.Resources.Requests), (expected.Resources.Requests)) } for k, v := range got.Resources.Requests { if ev, found := expected.Resources.Requests[v1.ResourceName(k)]; !found { return fmt.Errorf(\"failed to find resource <%v> in expected resources.Requests.\", k) } else { if ev.Value() != v.Value() { return fmt.Errorf(\"different resource.Requests: got <%v>, expected <%v>.\", v.Value(), ev.Value()) } } } return nil } assertProb := func(got, expected *v1.Container) error { // Assert LivenessProbe if got.LivenessProbe.Handler.HTTPGet.Path != expected.LivenessProbe.Handler.HTTPGet.Path || got.LivenessProbe.Handler.HTTPGet.Scheme != expected.LivenessProbe.Handler.HTTPGet.Scheme || got.LivenessProbe.FailureThreshold != expected.LivenessProbe.FailureThreshold || got.LivenessProbe.SuccessThreshold != expected.LivenessProbe.SuccessThreshold || got.LivenessProbe.PeriodSeconds != expected.LivenessProbe.PeriodSeconds || got.LivenessProbe.TimeoutSeconds != expected.LivenessProbe.TimeoutSeconds { return fmt.Errorf(\"different LivenessProbe: got <%v>, expected <%v>\", got.LivenessProbe, expected.LivenessProbe) } // Assert ReadinessProbe if got.ReadinessProbe.Handler.HTTPGet.Path != expected.ReadinessProbe.Handler.HTTPGet.Path || got.ReadinessProbe.Handler.HTTPGet.Scheme != expected.ReadinessProbe.Handler.HTTPGet.Scheme || got.ReadinessProbe.FailureThreshold != expected.ReadinessProbe.FailureThreshold || got.ReadinessProbe.SuccessThreshold != expected.ReadinessProbe.SuccessThreshold || got.ReadinessProbe.PeriodSeconds != expected.ReadinessProbe.PeriodSeconds || got.ReadinessProbe.TimeoutSeconds != expected.ReadinessProbe.TimeoutSeconds { return fmt.Errorf(\"different ReadinessProbe: got <%v>, expected <%v>\", got.ReadinessProbe, expected.ReadinessProbe) } return nil } assertLifeCycle := func(got, expected *v1.Container) error { if got.Lifecycle.PostStart.HTTPGet.Path != expected.Lifecycle.PostStart.HTTPGet.Path || got.Lifecycle.PostStart.HTTPGet.Scheme != expected.Lifecycle.PostStart.HTTPGet.Scheme { return fmt.Errorf(\"different LifeCycle: got <%v>, expected <%v>\", got.Lifecycle, expected.Lifecycle) } return nil } cpu, _ := resource.ParseQuantity(\"100Gi\") mem, _ := resource.ParseQuantity(\"100Mi\") </ins> tests := []struct { <del> rc               v1.ReplicationController expectPullPolicy v1.PullPolicy </del> <ins> name       string rc         v1.ReplicationController expected   []v1.Container validators []InitContainerValidator </ins> }{ { <ins> name: \"imagePullIPolicy\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"install\", \"image\": \"busybox\" } ]`, }, }, }, }, }, expected: []v1.Container{ { ImagePullPolicy: v1.PullAlways, }, }, validators: []InitContainerValidator{assertImagePullPolicy}, }, { name: \"FieldRef\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"env\": [ { \"name\": \"MY_POD_IP\", \"valueFrom\": { \"fieldRef\": { \"apiVersion\": \"\", \"fieldPath\": \"status.podIP\" } } } ] } ]`, }, }, }, }, }, expected: []v1.Container{ { Env: []v1.EnvVar{ { Name: \"MY_POD_IP\", ValueFrom: &v1.EnvVarSource{ FieldRef: &v1.ObjectFieldSelector{ APIVersion: \"v1\", FieldPath:  \"status.podIP\", }, }, }, }, }, }, validators: []InitContainerValidator{assertEnvFieldRef}, }, { name: \"ContainerPort\", </ins> rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ <del> \"pod.beta.kubernetes.io/init-containers\": string(containersWithoutPullPolicy), </del> <ins> \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"ports\": [ { \"name\": \"default\" } ] } ]`, </ins> }, }, }, }, }, <del> expectPullPolicy: v1.PullAlways, </del> <ins> expected: []v1.Container{ { Ports: []v1.ContainerPort{ { Name:     \"default\", Protocol: v1.ProtocolTCP, }, }, }, }, validators: []InitContainerValidator{assertContainerPort}, </ins> }, { <ins> name: \"Resources\", </ins> rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ <del> \"pod.beta.kubernetes.io/init-containers\": string(containersWithPullPolicy), </del> <ins> \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"resources\": { \"limits\": { \"cpu\": \"100Gi\", \"memory\": \"100Mi\" }, \"requests\": { \"cpu\": \"100Gi\", \"memory\": \"100Mi\" } } } ]`, </ins> }, }, }, }, }, <del> expectPullPolicy: v1.PullIfNotPresent, </del> <ins> expected: []v1.Container{ { Resources: v1.ResourceRequirements{ Limits: v1.ResourceList{ v1.ResourceCPU:    cpu, v1.ResourceMemory: mem, }, Requests: v1.ResourceList{ v1.ResourceCPU:    cpu, v1.ResourceMemory: mem, }, }, }, }, validators: []InitContainerValidator{assertResource}, }, { name: \"Prob\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"livenessProbe\": { \"httpGet\": { \"host\": \"localhost\" } }, \"readinessProbe\": { \"httpGet\": { \"host\": \"localhost\" } } } ]`, }, }, }, }, }, expected: []v1.Container{ { LivenessProbe: &v1.Probe{ Handler: v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, TimeoutSeconds:   1, PeriodSeconds:    10, SuccessThreshold: 1, FailureThreshold: 3, }, ReadinessProbe: &v1.Probe{ Handler: v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, TimeoutSeconds:   1, PeriodSeconds:    10, SuccessThreshold: 1, FailureThreshold: 3, }, }, }, validators: []InitContainerValidator{assertProb}, }, { name: \"LifeCycle\", rc: v1.ReplicationController{ Spec: v1.ReplicationControllerSpec{ Template: &v1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Annotations: map[string]string{ \"pod.beta.kubernetes.io/init-containers\": ` [ { \"name\": \"fun\", \"image\": \"alpine\", \"lifecycle\": { \"postStart\": { \"httpGet\": { \"host\": \"localhost\" } }, \"preStop\": { \"httpGet\": { \"host\": \"localhost\" } } } } ]`, }, }, }, }, }, expected: []v1.Container{ { Lifecycle: &v1.Lifecycle{ PostStart: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, PreStop: &v1.Handler{ HTTPGet: &v1.HTTPGetAction{ Path:   \"/\", Scheme: v1.URISchemeHTTP, }, }, }, }, }, validators: []InitContainerValidator{assertLifeCycle}, </ins> }, } <ins> assertInitContainers := func(got, expected []v1.Container, validators []InitContainerValidator) error { if len(got) != len(expected) { return fmt.Errorf(\"different number of init container: got <%d>, expected <%d>\", len(got), len(expected)) } for i := range got { g := &got[i] e := &expected[i] for _, validator := range validators { if err := validator(g, e); err != nil { return err } } } return nil } </ins> for _, test := range tests { rc := &test.rc obj2 := roundTrip(t, runtime.Object(rc))", "positive_passages": [{"docid": "doc-en-kubernetes-7c77a1e7ea84d582b899fa6b8d7216504334c47e064fb8eaad5c523c3bc66a32", "text": "NAME LABELS STATUS 10.1 Ready,SchedulingDisabled 10.2 10.1.10.2 Ready 10.3 Ready apiVersion: v1 kind: Node metadata: creationTimestamp: 2017-03-03T14:41:52Z labels: 10.1.10.1 name: 10.1.10.1 resourceVersion: \"\" selfLink: /api/v1/nodes/10.1.10.1 uid: -001f-11e7-8e83- spec: externalID: 10.1.10.1 status: addresses: address: 10.1.10.1 type: LegacyHostIP address: 10.1.10.1 type: InternalIP capacity: cpu: \"2\" memory: 4041352Ki pods: \"110\" conditions: lastHeartbeatTime: 2017-04-05T18:58:42Z lastTransitionTime: 2017-03-03T14:41:52Z message: kubelet has sufficient disk space available reason: KubeletHasSufficientDisk status: \"False\" type: OutOfDisk lastHeartbeatTime: 2017-04-05T18:58:42Z lastTransitionTime: 2017-04-05T15:27:52Z message: kubelet is posting ready status reason: KubeletReady status: \"True\" type: Ready nodeInfo: bootID: -6124-4ac7-ab96- containerRuntimeVersion: docker://1.12.6 kernelVersion: 4.9.16-coreos-r1 kubeProxyVersion: v1.2.4+coreos.1 kubeletVersion: v1.2.4+coreos.1 machineID: osImage: Container Linux by CoreOS 1298.7.0 (Ladybug) systemUUID: C3FD9852-2DFB-21F4-CE07-2597A746D99D When i create pv for creation pod is shows pv is pending. Please give any suggestions.....\nIs there solution of this problem with version 2.7. Still facing the same. what exactly expectation of helm upgrade --install relname chartsdirectory is is expected to work on first time installation in case with CI/CD Pipelines.", "commid": "kubernetes_issue_38542", "tokennum": 511}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e02b1e4e60ebe00e237ac9dd2f2e89a5a51ef385942ee5c4146efd1bf44a1772", "query": "} if latency := time.Since(now); latency > longThrottleLatency { <del> klog.V(4).Infof(\"Throttling request took %v, request: %s:%s\", latency, r.verb, r.URL().String()) </del> <ins> klog.V(3).Infof(\"Throttling request took %v, request: %s:%s\", latency, r.verb, r.URL().String()) </ins> } return err", "positive_passages": [{"docid": "doc-en-kubernetes-17cba5fefe0eb7064620c55e7004cb3247c052d63b398a81f9e1e6b57e9ab2c7", "text": "<!-- Please only use this template for submitting enhancement requests --What would you like to be : Report request throttling by the kubelet by default (i. e. V=3) Why is this needed: Request throttling can have serious consequences, but it is reported (in ) at V=4, so not by default. While attempting to probe limits of how many pods per node we could run, we hit a situation where the test pods would go Pending and eventually fail. After investigation, it turned out that the pod was being started by the kubelet, but that status update was not provided to the apiserver in a timely manner, resulting in the pod-to-pod network not coming up, so a pod attempting to connect would time out and fail. The delay was root caused to throttling by the kubelet; raising the KubeAPIBurst and KubeAPIQPS limits resolved the issue. The throttling was caused by fetching secrets for each pod, which was in its own namespace. The subjects of pods/node, namespaces/node, and throttling parameters are complex and I do not propose to solve them here (those are scalability issues that have to be approached carefully). However, being able to easily identify that throttling is taking place without having to restart the kubelet at higher verbosity would help administrators identify the possibility of this issue. My test attempted to create 500 pods across 3 nodes (OpenShift allows 250 pods/node). Running at V=5, I captured a histogram of the throttling delay in seconds. There were 7881 throttling events reported total over perhaps a 45 minute period, with a somewhat bimodal (in this case) distribution:\n/sig node /sig scalability\nThanks for filing the pr to fix :)\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten", "commid": "kubernetes_issue_80647", "tokennum": 537}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e083ff9b7c81d47b633e153a521869aef9052b7bf1cc06458f8a9b3b1d66a70e", "query": "hash := hash(nodeUpdate.name()) select { case <-stopCh: <ins> tc.nodeUpdateQueue.Done(item) </ins> break case tc.nodeUpdateChannels[hash%workers] <- nodeUpdate: } <ins> tc.nodeUpdateQueue.Done(item) </ins> } }(stopCh)", "positive_passages": [{"docid": "doc-en-kubernetes-2c221590d5e1ff106fb9cb8927cfb7dd0bc0677f71da23dc8e18ac35421ec6b8", "text": "We're seeing an issue with large memory growth in NoExecuteTaintManager when pods with tolerations are rapidly created/deleted. The item to the workqueue contains the full pod objects received from the informer: That means those pod objects are retained until they are processed. Additionally, it looks like the processing loop never removed the keys from the workqueue when it was done. It also means that multiple updates for the same pod result in multiple items in the workqueue, rather than enqueuing the pod to be processed once, like other controllers do. Simplifying this controller to enqueue pod updates only by name/namespace, and operate on the latest pod obtained from the store (like other controllers do) would speed up the processing and relieve the memory burden of the workqueue. /sig scheduling /cc\n/assign\nThanks for finding this Jordan - looking into your fixes.\nthe memory issue was fixed by /close", "commid": "kubernetes_issue_65325", "tokennum": 197}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e0acbf75126c8fe7a209e94517af48d42cc612a77a438f777b330aae41bd4685", "query": "framework.ExpectNoError(err, \"failed to see %v event\", watch.Deleted) }) <del> ginkgo.It(\"should validate Deployment Status endpoints\", func() { </del> <ins> /* Release: v1.22 Testname: Deployment, status sub-resource Description: When a Deployment is created it MUST succeed. Attempt to read, update and patch its status sub-resource; all mutating sub-resource operations MUST be visible to subsequent reads. */ framework.ConformanceIt(\"should validate Deployment Status endpoints\", func() { </ins> dClient := c.AppsV1().Deployments(ns) dName := \"test-deployment-\" + utilrand.String(5) labelSelector := \"e2e=testing\"", "positive_passages": [{"docid": "doc-en-kubernetes-7b39b114e3f8b25c65861c9c397d758891e478151ec492017dfbfbc72cee16e3", "text": "[X] Test PR: kuberenetes/kubernetes [x] Two weeks soak end date: 1 July 2021 [x] Test promotion PR: kubernetes/kubernetes According to this APIsnoop query, there are still some remaining StatefulSet endpoints which are untested. Create a watch to track deployment events. Create a deployment with a static label. Confirm that the pods are running. Get the deployment status. Parse the response and confirm that the deployment status conditions can be listed. Update the deployment status. Confirm via the watch that the status has been updated. Patch the deployment status. Confirm via the watch that the status has been patched. Using an existing as a template for a new for deployment lifecycle test. This query shows the endpoints hit within a short period of running the e2e test If a test with these calls gets merged, test coverage will go up by 1 point This test is also created with the goal of conformance promotion. /sig apps /sig testing /sig architecture /area conformance\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_102258", "tokennum": 359}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e0b4b6fb3a7c14bf2937f9e29dea4ffd67fa6ddfc55779f43e23a44a5bdf4692", "query": "cmd.Flags().BoolVar(&options.All, \"all\", false, \"select all resources in the namespace of the specified resource types\") cmd.Flags().StringVarP(&options.Selector, \"selector\", \"l\", \"\", \"Selector (label query) to filter on\") cmd.Flags().StringVarP(&options.ContainerSelector, \"containers\", \"c\", \"*\", \"The names of containers in the selected pod templates to change, all containers are selected by default - may use wildcards\") <del> cmd.Flags().BoolVar(&options.Local, \"local\", false, \"If true, set resources will NOT contact api-server but run locally.\") </del> cmdutil.AddDryRunFlag(cmd) cmdutil.AddRecordFlag(cmd) cmd.Flags().StringVar(&options.Limits, \"limits\", options.Limits, \"The resource requirement requests for this container.  For example, 'cpu=100m,memory=256Mi'.  Note that server side components may assign requests depending on the server configuration, such as limit ranges.\")", "positive_passages": [{"docid": "doc-en-kubernetes-f45c12318e35043c65362c27e361ee13adfef369e183f2b4f0557c11353bd9e9", "text": "from https://k8s-\nReally suspect this is\nThis is putting us into test-go post-commit run is broken\ncc:\nmarked this p0 - if a fix isn't easy let's try to identify what introduced this and revert.\nThis flake on: 2016-10-30 07:19 PDT First instance: : It is flaking frequently, blocking PRs from getting merged, and slowing the submit queue ( at 75%). As on-call, I'm going to try and identify the cluprit and revert. Can use all help in doing so.\ncan you investigate whether your additional tests could cause this (by breaking the deployment of those pods, for instance) , Saad Ali wrote:\nPR looks most suspect to me. It mucked with , and the errors we are seeing in each of the failures is related to : That PR was merged at Oct 30, 2016, 6:18 AM PDT and the first flake in was at Oct 30, 2016, 7:19 AM PDT. Thoughts? CC\nI'm going to initiate a revert of to see if that fixes the issue\nIMO we can just change the flaky test to not get pods but some other resources, such as deployments. We can't really expect to clean up pods immediately.\nI'm going to proceed with revert (). Please feel free to send a follow up PR to handle this more gracefully.\nGoing to leave this opened until we have a few hours of runs with the revert. Want to verify, with some degree of certainty, that the revert took care of this flake.\nWe had 15 green runs of in a row. Considering this flake fixed.", "commid": "kubernetes_issue_35898", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e0dc7608f5078a55b3bb68ef8bab21374a54f78b842b8dbb557cbb8c9ccd4e32", "query": ") apiserverRequestConcurrencyInUse = compbasemetrics.NewGaugeVec( &compbasemetrics.GaugeOpts{ <del> Namespace:         namespace, Subsystem:         subsystem, Name:              \"request_concurrency_in_use\", Help:              \"Concurrency (number of seats) occupied by the currently executing (initial stage for a WATCH, any stage otherwise) requests in the API Priority and Fairness subsystem\", DeprecatedVersion: \"1.28.0\", </del> <ins> Namespace: namespace, Subsystem: subsystem, Name:      \"request_concurrency_in_use\", Help:      \"Concurrency (number of seats) occupied by the currently executing (initial stage for a WATCH, any stage otherwise) requests in the API Priority and Fairness subsystem\", // Remove this metric once all suppported releases have the equal current_executing_seats metric DeprecatedVersion: \"1.31.0\", </ins> StabilityLevel:    compbasemetrics.ALPHA, }, []string{priorityLevel, flowSchema},", "positive_passages": [{"docid": "doc-en-kubernetes-a3e5f991085cecca4a970d807dd5157be9d11e288da6daa6aadb8b1d3ef3056a", "text": "In asked the following question. While the user-facing documentation answers this question clearly enough, John was reading the HELP string in the Prometheus scrapes. That thing only says the following. The metric HELP strings should be clear enough. Scrape or read the code (). No response <detailsThis problem started when we generalized to allow width other than 1 and got worse when we introduced borrowing. </details<detailsN/A </details<detailsN/A </details<details</details<details</details<details</details\n/assign\nActually, this metric should be removed. It is a duplicate of but with an inferior name.\nLooks good (Sorry I never got around to logging this issue myself. Have been super busy. And your wording is better anyway :-) )\n/triage accepted Thank you.", "commid": "kubernetes_issue_118957", "tokennum": 173}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e0ef1abd5747cd48fbfe93043f9fe4c5e075145156d7fc44f40d5d7e97875413", "query": "TestDynamicProvisioning(input.testCase, input.cs, input.pvc, input.sc) }) <del> It(\"should provision storage with non-default reclaim policy Retain\", func() { retain := v1.PersistentVolumeReclaimRetain input.sc.ReclaimPolicy = &retain pv := TestDynamicProvisioning(input.testCase, input.cs, input.pvc, input.sc) By(fmt.Sprintf(\"waiting for the provisioned PV %q to enter phase %s\", pv.Name, v1.VolumeReleased)) framework.ExpectNoError(framework.WaitForPersistentVolumePhase(v1.VolumeReleased, input.cs, pv.Name, 1*time.Second, 30*time.Second)) By(fmt.Sprintf(\"deleting the PV %q\", pv.Name)) framework.ExpectNoError(framework.DeletePersistentVolume(input.cs, pv.Name), \"Failed to delete PV \", pv.Name) framework.ExpectNoError(framework.WaitForPersistentVolumeDeleted(input.cs, pv.Name, 1*time.Second, 30*time.Second)) }) </del> It(\"should create and delete block persistent volumes [Feature:BlockVolume]\", func() { if !input.dInfo.IsBlockSupported { framework.Skipf(\"Driver %q does not support BlockVolume - skipping\", input.dInfo.Name)", "positive_passages": [{"docid": "doc-en-kubernetes-8769160e6f0dabeddd11cead4810305b5f582b45774110e5e46e9ec50492bd79", "text": "Testgrid: https://k8s- https://k8s- https://k8s- https://k8s- Sample failures: This started failing across multiple test jobs last night. The culprit appears to be PR over to you. /kind failing-test /priority critical-urgent /sig storage\n/milestone v1.13\n/assign\nGitHub didn't allow me to assign the following users: mkimuram. Note that only and repo collaborators can be assigned. 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\nI think should delete the PVC and wait for it to be deleted.\nThank you for your comment. I haven't yet catching up, but as for the PVC deletion code in , which is changed in the PR, PVC deletion is done inside for delete policy case or for retain policy case. Isn't it enough? In addition, could you let me know how I can check the matrix for the failure that we are focusing? I couldn't find the failure for provisioning tests themselves, there.\nIs my understanding right that the purpose of is to check whether resource is leaking by checking the diff of resource between the test? If so, is it correct that the sample output above means that one pd is leaking, not the leak of pv or pvc itself? I found that in the test for retain policy is removed in this PR when it is moved to , because it is gce specific logic and looks unnecessary. Do you think that it could be a cause of this issue? If so, should deleting the backend storage be generally required before removing the dynamic provisioned PV with retain policy?", "commid": "kubernetes_issue_70191", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e0f25bd45e17b83b992f9323a3d69785df6b6b718d82c10c1c9578bd0aa010e9", "query": "startLocalStreamingServer bool // containerCleanupInfos maps container IDs to the `containerCleanupInfo` structs <del> // needed to clean up after containers have been started or removed. </del> <ins> // needed to clean up after containers have been removed. </ins> // (see `applyPlatformSpecificDockerConfig` and `performPlatformSpecificContainerCleanup` // methods for more info). containerCleanupInfos map[string]*containerCleanupInfo", "positive_passages": [{"docid": "doc-en-kubernetes-486ca0159276eedd0d2aa336961ee5fd6fb83d0ac97af7f3f9c8c863d43fcef2", "text": "What would you like to be : Periodically remove cleanupInfos for old containers from dockershim's map. One way of doing that would be to just forget about s older than say an hour, as they should always be short-lived. Why is this needed: introduced a new in-memory map for the dockershim, that could potentially (in pathological cases) cause memory leaks - for containers that use GMSA cred specs, get created successfully, but then never get started nor removed. This might be okay for the alpha release of the GMSA feature, but should be addressed in the beta. See\n/assign wk8\n/sig windows\n/milestone v1.15\ngot moved out. let's move this issue with it as well /milestone v1.16\nHello! I'm bug triage lead for the 1.16 release cycle and considering this issue is tagged for 1.16, but not updated for a long time, I'd like to check its status. The code freeze is starting on August 29th (about 1.5 weeks from now), which means that there should be a PR ready (and merged) until then. Do we still target this issue to be fixed for 1.16?\n: yup we'd love to have this in 1.16, still waiting for kind reviewers on :) ...", "commid": "kubernetes_issue_74843", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e11f4d4be3fa640ec2b06f5b93611759fe1c7101baf3a7b56c494e66989af163", "query": "serviceName := \"svc-itp\" ns := f.Namespace.Name <del> servicePort := 8000 </del> <ins> servicePort := 80 // If the pod can't bind to this port, it will fail to start, and it will fail the test, // because is using hostNetwork. Using a not common port will reduce this possibility. endpointPort := 10180 </ins> ginkgo.By(\"creating a TCP service \" + serviceName + \" with type=ClusterIP and internalTrafficPolicy=Local in namespace \" + ns) local := v1.ServiceInternalTrafficPolicyLocal jig := e2eservice.NewTestJig(cs, ns, serviceName) svc, err := jig.CreateTCPService(func(svc *v1.Service) { svc.Spec.Ports = []v1.ServicePort{ <del> {Port: 8000, Name: \"http\", Protocol: v1.ProtocolTCP, TargetPort: intstr.FromInt(8000)}, </del> <ins> {Port: 80, Name: \"http\", Protocol: v1.ProtocolTCP, TargetPort: intstr.FromInt(endpointPort)}, </ins> } svc.Spec.InternalTrafficPolicy = &local }) framework.ExpectNoError(err) ginkgo.By(\"Creating 1 webserver pod to be part of the TCP service\") <del> webserverPod0 := e2epod.NewAgnhostPod(ns, \"echo-hostname-0\", nil, nil, nil, \"netexec\", \"--http-port\", strconv.Itoa(servicePort)) </del> <ins> webserverPod0 := e2epod.NewAgnhostPod(ns, \"echo-hostname-0\", nil, nil, nil, \"netexec\", \"--http-port\", strconv.Itoa(endpointPort)) </ins> webserverPod0.Labels = jig.Labels webserverPod0.Spec.HostNetwork = true e2epod.SetNodeSelection(&webserverPod0.Spec, e2epod.NodeSelection{Name: node0.Name})", "positive_passages": [{"docid": "doc-en-kubernetes-06e17cf980b6b4fe370857f0b2e0687536ee3b3b60ed1f78548a694def2f21f6", "text": "Failed here /retest Originally posted by in This fails because the pod tries to bind port 80, that is a very demanded port, but there are two tests doing that, that increase the chance to collide\n/sig network\nClose when merges\n/triage accepted", "commid": "kubernetes_issue_104406", "tokennum": 54}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e1202c2edf0c3fda05fe1cf56756b702f1e9a021b6250863ea361e37548644a1", "query": "#   standalone     - Heapster only. Metrics available via Heapster REST API. ENABLE_CLUSTER_MONITORING=\"${KUBE_ENABLE_CLUSTER_MONITORING:-influxdb}\" <ins> # Historically fluentd was a manifest pod and then was migrated to DaemonSet. # To avoid situation during cluster upgrade when there are two instances # of fluentd running on a node, kubelet need to mark node on which # fluentd is not running as a manifest pod with appropriate label. # TODO(piosz): remove this in 1.8 NODE_LABELS=\"${KUBE_NODE_LABELS:-alpha.kubernetes.io/fluentd-ds-ready=true}\" </ins> # Optional: Enable node logging. ENABLE_NODE_LOGGING=\"${KUBE_ENABLE_NODE_LOGGING:-true}\" LOGGING_DESTINATION=\"${KUBE_LOGGING_DESTINATION:-gcp}\" # options: elasticsearch, gcp", "positive_passages": [{"docid": "doc-en-kubernetes-3936c52aacccf581fb5174635de31acc9a85b981ebc339b83016fc7b6087f92b", "text": "PR introduced an annotation for fluentd migration from static pod to the daemonset to avoid two instances of fluentd on a single node during the transition stage. I didn't read the pr carefully, but based on the code at , every node object has one label be default: \"\". I think this is wrong. 1) Not everyone use fluentd as the logging agent. 2) It is hard-coded in Kubelet code as part of kubeletnodestatus. No matter running fluentd as a static pod or a daemonset on the node, Kubelet shouldn't treat it different from other pods. The right approach is introducing an external controller to apply this cloud-provider / kubernetes vendor (i.e. GKE) specific label to the node. cc/\nThe string \"fluentd\" shouldn't appear anywhere in our code. Please remove it ASAP.\nAbsolutely agree with you, thanks for bringing this up! Is it possible to apply labels to the node as part of the node startup script/salt?\nTo clarify, I'm thinking about possible ways to provide a fix for that ASAP. Writing external controller is a best solution, but here we have a release coming and this label is intended to be only a temporary measure to perform upgrade from using fluentd as static pods to using daemon set.\nThere are many ways to achieve this outside the core system. But I believe GKE already has an existing mechanism to add this kind of labels to the node, and the consistency is important for GKE management. cc/\nOK, thanks! However, I believe we should be sure not to break everyone's upgrade process, i.e. after master upgrade to 1.6 on any platform, there should be only one fluentd agent on each node. I propose changing the configure scripts and salt to set up needed labels in kubelet's flag (). WDYT?\nIt seems to me like upgrades could survive without the explicit dependency on fluentd: I'm not sure if upgrades call initialNode or not, my own ignorance ? If they do, and this is removed, can't an external controller just do the work of re--adding that label if its dropped?\nthanks for raising this. Let's sync f2f\ncc\nWDYT about exposing kubelet version as a label and have a selector in fluentd ds config targeting version 1.6+?", "commid": "kubernetes_issue_42840", "tokennum": 508}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e1202c2edf0c3fda05fe1cf56756b702f1e9a021b6250863ea361e37548644a1", "query": "#   standalone     - Heapster only. Metrics available via Heapster REST API. ENABLE_CLUSTER_MONITORING=\"${KUBE_ENABLE_CLUSTER_MONITORING:-influxdb}\" <ins> # Historically fluentd was a manifest pod and then was migrated to DaemonSet. # To avoid situation during cluster upgrade when there are two instances # of fluentd running on a node, kubelet need to mark node on which # fluentd is not running as a manifest pod with appropriate label. # TODO(piosz): remove this in 1.8 NODE_LABELS=\"${KUBE_NODE_LABELS:-alpha.kubernetes.io/fluentd-ds-ready=true}\" </ins> # Optional: Enable node logging. ENABLE_NODE_LOGGING=\"${KUBE_ENABLE_NODE_LOGGING:-true}\" LOGGING_DESTINATION=\"${KUBE_LOGGING_DESTINATION:-gcp}\" # options: elasticsearch, gcp", "positive_passages": [{"docid": "doc-en-kubernetes-4cb16c5ce2a173a3021e859767a51a1df9544dd94429e93c357c1a133ef72828", "text": "and I talked about this issue a bit for migrating kube-proxy. One idea we came up with was that of running a controller that will identify kubelet versions and apply taints to nodes running static pods. The daemonset version would not tolerate that taint and that way we keep daemon set pods off of nodes running static pods. Have you considered that approach?\nIt doesn't differ from a controller applying labels. I'd like to avoid necessity of introducing such controller, since it's not clear what is it's responsibility (generic controller for applying labels on nodes based on some rules? a custom controller just for fluentd purposes). In GKE we can do it on GKE control plane side, but we need a story for open source.\nMove applying labels to startup scripts/salt seems to be the least intrusive and easiest to implement way.\nActually what I proposed in is not an option since nodeSelector in PodSpec is old style selector.\nI'm not a big fan of approach with salt, but it seems there is no better option.\nRe: Instead of exposing Kubelet version as a label, why not using field selector. Kubelet version is part of NodeStatus already. I just simply don't want to have a duplicate info for the same object.\nis it possible to schedule based on fieldselector? I'm only aware of using field selector while listing objects.\nAlso node-labels option is in alpha\nBut it's present since 1.2 What is the status of this flag? Can we use it for fluentd purposes or better avoid this?\nMaybe it does make sense to implement a temporary ad-hoc controller? It's the easiest to deploy solution, just another in fluentd addon.\nI know. It totally doesn't make sense to introduce anything custom. I'll use just the flag. It's rather hacky but unfortunately I can't see anything better.\nCool thing about controller is that you can deploy it into any cluster and it will work, with CA also. You don't have to set up your node labels manually then or restart the cluster.\nThere is a number of open question with having a new controller: it run on the master or a node? we guarantee that it will be always running? it have any resource requirements? I'd like to avoid discussing it right before the release.\nHaving a controller will help with kube-proxy transition too in the future.", "commid": "kubernetes_issue_42840", "tokennum": 507}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e1202c2edf0c3fda05fe1cf56756b702f1e9a021b6250863ea361e37548644a1", "query": "#   standalone     - Heapster only. Metrics available via Heapster REST API. ENABLE_CLUSTER_MONITORING=\"${KUBE_ENABLE_CLUSTER_MONITORING:-influxdb}\" <ins> # Historically fluentd was a manifest pod and then was migrated to DaemonSet. # To avoid situation during cluster upgrade when there are two instances # of fluentd running on a node, kubelet need to mark node on which # fluentd is not running as a manifest pod with appropriate label. # TODO(piosz): remove this in 1.8 NODE_LABELS=\"${KUBE_NODE_LABELS:-alpha.kubernetes.io/fluentd-ds-ready=true}\" </ins> # Optional: Enable node logging. ENABLE_NODE_LOGGING=\"${KUBE_ENABLE_NODE_LOGGING:-true}\" LOGGING_DESTINATION=\"${KUBE_LOGGING_DESTINATION:-gcp}\" # options: elasticsearch, gcp", "positive_passages": [{"docid": "doc-en-kubernetes-3203f30994cf42c5336d5a6d0dc1585171cc98cff1719959478ccaf13036f1c4", "text": ", Piotr Szczesniak <:\nis this a 1.6 release blocker?\nI think yes. The PR is already sent and approved. I need to fix e2e tests because it doesn't work well with the test infra (e2e tests passes locally). EDIT: I'll do it hopefully today.\nThe PR is ready to be merged and lgtmed. Waiting for approvals.", "commid": "kubernetes_issue_42840", "tokennum": 89}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e12bb2dca3470a4f74da33540d31f960fd05d126fa3d7421c5d87554320cb76c", "query": "func setSandboxResources(hc *dockercontainer.HostConfig) { hc.Resources = dockercontainer.Resources{ <del> MemorySwap: -1, </del> <ins> MemorySwap: dockertools.DefaultMemorySwap(), </ins> CPUShares:  defaultSandboxCPUshares, // Use docker's default cpu quota/period. }", "positive_passages": [{"docid": "doc-en-kubernetes-2c477631a31f290ae271a7ca0a83a97399cbf63c4cfd883674b6ddce7387fc19", "text": "What happened: Latest kubelet + Windows Docker version 1.14.0-dev refused to start any containers, error output: \"invalid option: Windows does not support MemorySwap\" How to reproduce it (as minimally and precisely as possible): It's always reproducible with Windows Docker 1.14.0-dev + latest kubelet code base. Anything else do we need to know: It didn't happen for Windows Docker 1.12.2-cs2-ws-beta. The reason behind the issue was because new code was for Windows Docker to check Resources parameters, it doesn't accept a non-zero value for MemorySwap: But kubelet was default to set an unlimited (-1) value. The issue was gone in my setup after applied a private fix to disable MemorySwap by set it to zero for Windows.", "commid": "kubernetes_issue_39003", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e136b371e0079de48de6de26778afff56dd84dd7b1fb7223abd1eaab28d4c4ee", "query": "Labels: labels, }, Spec: api.PodSpec{ <del> Containers: []api.Container{c}, </del> <ins> Containers:                    []api.Container{c}, TerminationGracePeriodSeconds: &gracePeriod, </ins> }, }, },", "positive_passages": [{"docid": "doc-en-kubernetes-f3af4e5ee08342f3d9a5775ee2c1466702ed34eb1665ac9c4b71bf76c8f54023", "text": "Nodes Network when a minion node becomes unreachable [replication controller] recreates pods scheduled on the unreachable minion node AND allows scheduling of pods on a minion after it rejoins the cluster(Failed 17 times in the last 30 runs. Stability: 43 %)Failed with 0 retries\nfor triage\nI'll look into this.\nI talked to about this and he had a pretty good guess in about two seconds about what the problem is. ReplicationController sync method does this: but DaemonSet controller doesn't. (I guess when DaemonSet was copy-pasted from ReplicationController, this was accidentally removed.) Pod reflector and syncer are running in separate goroutines, and if pod reflector doesn't run then syncer will think there are no pods on the node.\nTo be clear: this is about the test Controller Manager should not create/delete replicas across restart which is the one that is actually failing.\nI'm confused you're saying that this is about , but you're updating . I thought they are about two different tests...\nYes sorry, I put my comment in the wrong issue. Reassigning this one to you, and I'll copy my comment into the other one.\nFirst failure: We check if all namespace are deleted. If other tests failed to delete their namespace this test will fail. I'm going to delete this logic as we already check if we have successfully deleted our namespace. See also for some more details.\nSecond failure: We disable network by running the following command: I checked and it seems that it results in ing master to hang. I suspect that Kubelet hangs on updating node status and depending when it breaks the connection (by timeout) it will fit in test timeouts or not.\nWhat is the default timeout for connections using client libraries to apiserver? I'm checking the code, but can't find it.\nI'm not sure if we set one, but we should. I guess I would expect to see that in the config, w/ default set by this function: , Filip Grzadkowski wrote:\nSo: let's add a timeout, and revert .\nI think that adding a timeout and reverting are orthogonal. I we want to simulate network problems with node-master communication then using REJECT is better anyway. At the same time adding timeout makes sense for many other reasons.", "commid": "kubernetes_issue_14695", "tokennum": 521}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e136b371e0079de48de6de26778afff56dd84dd7b1fb7223abd1eaab28d4c4ee", "query": "Labels: labels, }, Spec: api.PodSpec{ <del> Containers: []api.Container{c}, </del> <ins> Containers:                    []api.Container{c}, TerminationGracePeriodSeconds: &gracePeriod, </ins> }, }, },", "positive_passages": [{"docid": "doc-en-kubernetes-171a96c8c8138970f18a9330482c8efd4960f1ea370d03cb243605d2473f3591", "text": "OK then, let's add a timeout and test both DROP and REJECT-- no sort of network problem should hang a component.\nI think it didn't hang. It just that the kubelet was retrying too slow and sometimes it fit test timeout, sometime it didn't.\nCould we reduce the timeout to make it always fit the test timeout? , Filip Grzadkowski\nI guess we can. I'll try tomorrow.\nIt seems we have a new type of failure: It seems that kubelet on a machine where network is blocked doesn't notice new pod. After reading logs I assume that kubelet doesn't notice that the watch is broken and doesn't try to relist everything. It notices new pod only after watch timeout.\nUgh, I hope we don't have to start sending watch heartbeats.\nIt seems that all recent failures are with the following error: which means the reason is here: - can you please take a look or delegate?\nI did some more debugging of it. I was looking into this failure: There is something strange happening here: run performTemporaryNetworkFailure: succesfully block the load from kubelet: the succesfully wait for node to become not ready: some time nodecontroller successfully removes the pod: replication controller creates a new pod: here is something I don't undertand - because of some reason, the test doesn't observe that the pod actually disappeared. - any thoughts on it?\nBTW - this is exactly the same situation in:\nOK - I think this is related to default 30s deletion grace period.\nYes - it seems that this is exactly the case. I will send out PR fixing this out for review.\nI'm reopening it for tracking. If there won't be any failures within next few days - I will move the test back from flaky and close this issue.\nThanks for fixing, .\nIt seems that the main issue is fixed. However, there was one failure in the last 30 runs: in which one pod simply didn't started (and it was \"preparation\" for the test, not the test itself).\nDuring next 2 days there was exactly one more failure of this test: it is exactly the same as the previous one. However, those are duplicates of So I'm going to move this test out of flaky suite.", "commid": "kubernetes_issue_14695", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e14162c79bd012c038445a568e735633229a1b99277b34c4941f9b2e313319bf", "query": "\"k8s.io/kubernetes/pkg/client/cache\" client \"k8s.io/kubernetes/pkg/client/unversioned\" \"k8s.io/kubernetes/pkg/controller\" <ins> \"k8s.io/kubernetes/pkg/runtime\" </ins> \"k8s.io/kubernetes/pkg/securitycontext\" <ins> utiltesting \"k8s.io/kubernetes/pkg/util/testing\" </ins> ) var (", "positive_passages": [{"docid": "doc-en-kubernetes-b0a441a371f8db864bebc11c7303837af71a86244bb0f50ec81fe1d8a09d5c71", "text": "The test is in flaky suite and no one seems to care. We need an owner for this test. cc Last failure log:\ndo you think you can take a look at this?\nThis is happening because of a bad assumption. The assumption is: if the reflector's store is consistent with etcd, the store given back to clients of the framework.Controller is too. I'd really like a general fix applicable to all controllers for this problem, but fixing it just for the RCs is pretty easy. In more detail: This function reports when the reflector has listed from apiserver. But the store given to the reflector is the fifo of the framework.Controller. The store given back to the caller is still not consistent, and will not be till the framework.Controller puts all the objects from the fifo into the client state store (). The rc specific fix: Before starting the rc manager, seed the expectations store with an expectation like {rc:foo, adds: foo.Status.Replicas, deletes:0}. This will wait for status.Replicas number of ADD events till a timeout. The general fix: Somehow expose this through framework.Controller.HasSynced (clients don't care about the fifo anyway, shouldn't it just be an implementation detail?) ideas? cc'ing people who have written controllers that might be interested I don't think this (and generally anything flaky for 1 release) is a p0, I can fix it if you don't mind dealing with the flakes till I've cleared things off my plate. I'd be more than happy to review a fix.\nWell, it's a P0 because test is flaky. E.g last run:\n- did you have chance to look into it?\nThe \"DaemonRestart\" tests are still labeled at . I will send a PR to promote them.\nare you still planning to send aPR to promote the DaemonRestart tests out of flaky? I think this is the right thing to do.\nAck; sorry, I lost this in the muck.", "commid": "kubernetes_issue_17829", "tokennum": 444}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e15de90fb32a7686b6bbf9c31d40d116691842b94b478eccc88347d3023393d9", "query": "## Requirements 1. Docker, using one of the following configurations: <del> * **macOS** Install Docker for Mac. See installation instructions [here](https://docs.docker.com/docker-for-mac/). </del> <ins> * **macOS** Install Docker for Mac. See installation instructions [here](https://docs.docker.com/desktop/install/mac-install/). </ins> **Note**: You will want to set the Docker VM to have at least 8GB of initial memory or building will likely fail. (See: [#11852]( http://issue.k8s.io/11852)). * **Linux with local Docker**  Install Docker according to the [instructions](https://docs.docker.com/installation/#installation) for your OS. * **Windows with Docker Desktop WSL2 backend**  Install Docker according to the [instructions](https://docs.docker.com/docker-for-windows/wsl-tech-preview/). Be sure to store your sources in the local Linux file system, not the Windows remote mount at `/mnt/c`.", "positive_passages": [{"docid": "doc-en-kubernetes-f2596026c617784a7bc3035384709bb19d64afff46adfc25b28b10c412ad8eb8", "text": "The link in the following sentence is incorrect macOS Install Docker for Mac. See installation instructions . It redirects to instead of The link should get redirected to Navigate to Click on the hyperlink in the below section macOS Install Docker for Mac. See installation instructions . N/A N/A N/A N/A N/A N/A N/A\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\n/sig contributor-experience", "commid": "kubernetes_issue_122671", "tokennum": 173}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e15e4b32dcb3ee578a2b66ee900482bf1f992f7895fdaa7e3a548bf9fa956b3a", "query": "t.objects[gvr][namespacedName] = obj for _, w := range t.getWatches(gvr, ns) { <del> w.Add(obj) </del> <ins> // To avoid the object from being accidentally modified by watcher w.Add(obj.DeepCopyObject()) </ins> } return nil", "positive_passages": [{"docid": "doc-en-kubernetes-097cec69e6f696ee556282ba1b462f036510b26986c7b0a8c41c6e03be57a385", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --Hello, Found a potential data race in testing. There is a test If we update it like this (we actually can do it ): If watcher updates received object we get a data race. No data race My suggestion: send copy of object here:\n/sig api-machinery\n/cc /triage accepted Do you remember if we fixed similar issues before?\nHi ,The code avoiding data race seems to already exist If you commented the code on above, the following test case will pass (because of data race), so I think there is no data race in the code : )\nHi Did you run my test with flag? Of course if I comment there will be data race. But let's take a look at: We store in and do with the same . So, watcher receives that is stored in map. we call we take the same from : Therefore, if watcher modifies received in another goroutine we have data race. Output:\nHi You're right ,thank you for solving my confusion. One solution could be to copy of , I will try to fix it.", "commid": "kubernetes_issue_103148", "tokennum": 276}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e1902aacdb50a0724c24a6a065f69ce5ee6a1b63368c1936f0bb07bc6aab9cce", "query": ") func (c *FakeEvictions) Evict(eviction *policy.Eviction) error { <del> action := core.GetActionImpl{} action.Verb = \"post\" </del> <ins> action := core.CreateActionImpl{} action.Verb = \"create\" </ins> action.Namespace = c.ns action.Resource = schema.GroupVersionResource{Group: \"\", Version: \"v1\", Resource: \"pods\"} action.Subresource = \"eviction\" <del> action.Name = eviction.Name </del> <ins> action.Object = eviction </ins> _, err := c.Fake.Invokes(action, eviction) return err }", "positive_passages": [{"docid": "doc-en-kubernetes-82d56ce8e3638d906303613bbb222b7918f374f3f5d17197cc57429b2467d07d", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: I'm trying to test Eviction functionality in my program, but running into some inconsistencies around how Evictions are handled in the fake SimpleClient in the client-go testing functionality. Most notably, creates a different from , and both are missing information. issues a with set to (seems to be the only Fake that has this mismatch) on the subresource of . It is missing all the extra information in the eviction, i.e. the . issues a on the subresource of the resource. This is wrong, because aren't created, they're only posted and handled immediately. The Action is missing a Namespace. What you expected to happen: I want to be able to add my own reactor to the SimpleClient to handle this special case. I propose we change both cases to a with set to the . This will ensure it's not handled by the current SimpleClient ObjectReaction, and makes it so users can implement whatever they want themselves. I'd be happy to make a PR with these changes. How to reproduce it (as minimally and precisely as possible): Output: Environment: git revision of : <!-- DO NOT EDIT BELOW THIS LINE --/kind bug\nPOST requests are create requests. It doesn't matter if the object is persisted or not.\n/sig api-machinery\ncc", "commid": "kubernetes_issue_71598", "tokennum": 330}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e1a0ab10b595c58a51220f40ba03d52f1012117248a66a867e2715c6edadd131", "query": "name = \"all-srcs\", srcs = [ \":package-srcs\", <ins> \"//pkg/kubelet/apis/kubeletconfig/fuzzer:all-srcs\", </ins> \"//pkg/kubelet/apis/kubeletconfig/scheme:all-srcs\", \"//pkg/kubelet/apis/kubeletconfig/v1alpha1:all-srcs\", \"//pkg/kubelet/apis/kubeletconfig/validation:all-srcs\",", "positive_passages": [{"docid": "doc-en-kubernetes-937f1cb17c20e5fd2b4a1f81201690c3dbe6990ef3c1bc74ff71daaa02b6db56", "text": "Solution: I will add one.\n/cc\nxref\nThanks for sending a PR so quickly!\n[MILESTONENOTIFIER] Milestone Issue Needs Attention Action required: During code slush, issues in the milestone should be in progress. If this issue is not being actively worked on, please remove it from the milestone. If it is being worked on, please add the label so it can be tracked with other in-flight issues. Note: If this issue is not resolved or labeled as by Wed, Nov 22 it will be moved out of the v1.9 milestone. <details<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details", "commid": "kubernetes_issue_55959", "tokennum": 230}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e1c2fc0a938a0f5439903032c0d63018496b7a719075b13f2fda00b3b5af1114", "query": "current-release-pr current-replicas daemonset-lookup-cache-size <ins> data-dir </ins> default-container-cpu-limit default-container-mem-limit delay-shutdown", "positive_passages": [{"docid": "doc-en-kubernetes-6208b2974deee3332ab4020708350835523c141c61d79e5104e4c7dba961daa5", "text": "ci-kubernetes-e2e-gce-device-plugin-gpu.Overall ci-kubernetes-e2e-gce-device-plugin-gpu.Pod kubetest.Up Intermittently since 02/23 No response No response /sig testing /sig release\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/cc /sig node BTW, would you help to confirm if this is a release cut blocker? We plan to release 1.30.0-alpha.3 on Tuesday 27th February 2024.\nIt passed! Maybe it was some infra issues?\nFailed again. /sig k8s-infra\nMany recreating of nodes in log.\nThis is caused by infra flaky.\nThe problem is\nThis job only runs one test and GPU instances are hard to find we don\u2019t need many of those instances for this job, can we please change this job to only use 2 workers?\n/cc\ntests failed in a recent run. It failed the first time. The Job failure now changed to test case failing today. It failed 4 times in a row.\n/assign\nI launched a test run, logged into the master node and took the kubeconfig and found the following: Relevant bit\nLink some related updates recently on this job.\nThe error above in is weird to me. It said No firmware image found . In successful run before, like (02-27), there are no such failure logs. failure in only kubelet log shows the pod crashed and restarted for many times. No pod log or containerd log.\nAfter , the CI is not always failing now and 4 in a row.\n/close\nClosing 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\n/reopen as keeps flaking\nReopened this issue. <detailsIn response to : /reopen as keeps flaking Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_123491", "tokennum": 511}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e1c2fc0a938a0f5439903032c0d63018496b7a719075b13f2fda00b3b5af1114", "query": "current-release-pr current-replicas daemonset-lookup-cache-size <ins> data-dir </ins> default-container-cpu-limit default-container-mem-limit delay-shutdown", "positive_passages": [{"docid": "doc-en-kubernetes-93e6b458b8ba607e02020a8718331e5d8d90eb2c8daf949aa5e83a98cf741ed8", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThe problem is different with the failure after the revert. We(release signal team) plan to open an issue for the flake later. (Probably, we should open that one and then close on behalf of that new issue later.)\nFeel free to close it then. However, it failed 3 times out of last 4 runs. It's more a failure than a flake in my opinion. If doesn't help/ not appropriate, I'd suggest to revert installer and image changes\ncomment is clear about the root cause, we have a problem installing the drivers, can you redirect this issue if you think is a bug?\nAfter was merged, there are 6 failure in last 24 run. Tab stats: 8 of 10 (80.0%) recent columns passed (258 of 262 or 98.5% cells) The Flaky rate is lower.", "commid": "kubernetes_issue_123491", "tokennum": 202}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e1c5c3bb7499cab1f05613b1e1707438d35e7daf32561c481c132dbbe8e83844", "query": "\"golang.org/x/net/websocket\" <ins> \"encoding/json\" </ins> v1 \"k8s.io/api/core/v1\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/labels\" \"k8s.io/apimachinery/pkg/runtime\" <ins> \"k8s.io/apimachinery/pkg/runtime/schema\" </ins> \"k8s.io/apimachinery/pkg/types\" \"k8s.io/apimachinery/pkg/util/intstr\" \"k8s.io/apimachinery/pkg/util/uuid\" \"k8s.io/apimachinery/pkg/util/wait\" \"k8s.io/apimachinery/pkg/watch\" <ins> \"k8s.io/client-go/dynamic\" </ins> \"k8s.io/client-go/tools/cache\" watchtools \"k8s.io/client-go/tools/watch\" podutil \"k8s.io/kubernetes/pkg/api/v1/pod\"", "positive_passages": [{"docid": "doc-en-kubernetes-a4e08d4660e59e77b869eee3e8c161e5e01175b90d68e1077fd3e84d4f4d567b", "text": "[x] Original approval issue: - Reverted due to flakes [x] Two weeks soak end date: 20 November 2020 This issue is created to allow edit by /wip /hold According to this APIsnoop query, there are still some remaining Pod endpoints which are untested. a Pod with a static label the Pod with a new Label and updated data the Pod to ensure it's patched the Pod's status the Pod's status Ready condition to False the Pod's status to check if Ready is False all Pods in all Namespaces find the Pod(1) ensure that the Pod is found and is patched Namespaced Pod(1) via a Collection with a LabelSelector the Pod to check that it's deleted Discover useragents: List endpoints hit by the test: Display endpoint coverage change: If a test with these calls gets merged, test coverage will go up by 4 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance\n/reopen Test PR Merge Promotion PR to be created next\nReopened this issue. <detailsIn response to : /reopen Test PR Merge Promotion PR to be created next 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\nreverted by due to flaky test\nIssues 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\n/remove-lifecycle stale\n/reopen PR on test grid for 2 weeks before promotion to conformance\nReopened this issue. <detailsIn response to : /reopen PR on test grid for 2 weeks before promotion to conformance 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\n/triage accepted", "commid": "kubernetes_issue_90936", "tokennum": 449}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e20cba2df6d84f4c715748d5f7b29310f61c7db8b04f25b06935aed9b4f8ff9b", "query": "return selector.PodSelectorMatches } <del> // NodeMatchesNodeSelectorTerms checks if a node's labels satisfy a list of node selector terms, </del> <ins> // nodeMatchesNodeSelectorTerms checks if a node's labels satisfy a list of node selector terms, </ins> // terms are ORed, and an emtpy a list of terms will match nothing. <del> func NodeMatchesNodeSelectorTerms(node *api.Node, nodeSelectorTerms []api.NodeSelectorTerm) bool { </del> <ins> func nodeMatchesNodeSelectorTerms(node *api.Node, nodeSelectorTerms []api.NodeSelectorTerm) bool { </ins> for _, req := range nodeSelectorTerms { nodeSelector, err := api.NodeSelectorRequirementsAsSelector(req.MatchExpressions) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-3229e3f28f67afa9ddea85d9d31a50803c261e0ae30f76f950060d1790215e64", "text": "I just noticed you forgot to register the image locality priority function in in I also missed it when I reviewed your PR. I have fixed this in . But it would be great if you could figure out a mechanism that would ensure that all predicate/priority functions that are tested (you can assume they will always live under ) are registered, and fail the test if not. That will allow us to prevent this mistake in the future.\nThanks! Will fix this soon!\nSeems need to wait for in before I send PR? Otherwise this test will always fail ...", "commid": "kubernetes_issue_21236", "tokennum": 114}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e21bdc5763b59871a954222e0bdac0c992772aab12ead9263a9ec2d15935431d", "query": "if want == \"\" { want = \"<nil>\" } <del> if got := fmt.Sprintf(\"%v\", err); got != want { </del> <ins> if got := fmt.Sprintf(\"%v\", err); !strings.Contains(got, want) { </ins> t.Errorf(\"wrong error for message %q: want=%q, got=%q\", test.message, want, got) } }", "positive_passages": [{"docid": "doc-en-kubernetes-984aaf2876c4d4651f6765b291626bccfb7d6364087d7ebb11c97e2832c59ee5", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Below k8s UT fail when run with master-golang. TestCheckpointStateRestore/RestorecheckpointwithinvalidJSON error:=== RUN TestCheckpointStateRestore/RestorecheckpointwithinvalidJSON I1124 05:38:14. ] [cpumanager] initializing new in-memory state store unexpected error while creatng checkpointState: could not restore state from checkpoint: json: unexpected end of JSON input, please drain this node and delete the CPU manager checkpoint file \"/tmp/cpumanagerstatetest479660663/cpumanagercheckpointtest\" before restarting Kubelet --- FAIL: TestCheckpointStateRestore/RestorecheckpointwithinvalidJSON (0.00s) TestStrategicMergePatchInvalid error:=== RUN TestStrategicMergePatchInvalid expected \"invalid character 'b' looking for beginning of value\", got \"json: invalid character 'b' looking for beginning of value\" --- FAIL: TestStrategicMergePatchInvalid (0.00s) TestJSONPatch error:=== RUN TestJSONPatch invalid-syntax: expected error invalid character 'i' looking for beginning of value, but got json: invalid character 'i' looking for beginning of value --- FAIL: TestJSONPatch (0.00s) TestV4ErrorDecoder expandless error:=== RUN TestV4ErrorDecoder wrong error for message \"{\": want=\"error stream protocol error: unexpected end of JSON input in \"{\"\", got=\"error stream protocol error: json: unexpected end of JSON input in \"{\"\" --- FAIL: TestV4ErrorDecoder (0.00s What you expected to happen: The tests should pass with no error. How to reproduce it (as minimally and precisely as possible): a stable version of golang installed master go from upstream git clone cd go/src cd ../.. cp -r ./go /usr/local export PATH=/usr/local/go/bin:$PATH kubernetes repo and run the unit tests. () Anything else we need to know?: These failures are occurring due to mismatch of error messages between upstream go and the k8s tests.", "commid": "kubernetes_issue_96853", "tokennum": 597}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e21bdc5763b59871a954222e0bdac0c992772aab12ead9263a9ec2d15935431d", "query": "if want == \"\" { want = \"<nil>\" } <del> if got := fmt.Sprintf(\"%v\", err); got != want { </del> <ins> if got := fmt.Sprintf(\"%v\", err); !strings.Contains(got, want) { </ins> t.Errorf(\"wrong error for message %q: want=%q, got=%q\", test.message, want, got) } }", "positive_passages": [{"docid": "doc-en-kubernetes-d960907779eeb813df14a2ea4a00c97f52784ded937dbf1c71e5b05391843c78", "text": "There is an addition \"json:\" prefix to SyntaxError messages after this below commit: Environment: Kubernetes version (use ): latest source code from upstream Cloud provider or hardware configuration: OS (e.g: ): \"CentOS Linux 8 (Core)\" Kernel (e.g. ): Linux rajalakshmi-workspace 4.18.0-193.19.1.el82.ppc64le SMP Mon Sep 14 14:48:04 UTC 2020 ppc64le ppc64le ppc64le GNU/Linux Install tools: [root go]# go version go version devel + Fri Nov 20 00:54:43 2020 +0000 linux/ppc64le [root go]# Network plugin and version (if this is a network-related bug): Others:\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig testing\nwill fix it in Go 1.16 as release-blocker.\nI would fix the test here to be more tolerant. exact string matches on error messages aren't really an API\u2026 I would not expect that to block the golang release\nAgree too, we can think about having a substring match to avoid these issues instead!\n/assign Lets see if we can fix this in the k8s tests", "commid": "kubernetes_issue_96853", "tokennum": 352}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e29133af86a1c9267681fa5cf17f5773c93fae1b35253a09a06399dacf510341", "query": "apierrors \"k8s.io/apimachinery/pkg/api/errors\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/util/intstr\" <ins> \"k8s.io/apimachinery/pkg/util/uuid\" </ins> \"k8s.io/apimachinery/pkg/util/wait\" \"k8s.io/kubernetes/test/e2e/framework\" e2epod \"k8s.io/kubernetes/test/e2e/framework/pod\" imageutils \"k8s.io/kubernetes/test/utils/image\" \"github.com/onsi/ginkgo\" <ins> \"k8s.io/apimachinery/pkg/types\" </ins> ) func extinguish(f *framework.Framework, totalNS int, maxAllowedAfterDel int, maxSeconds int) {", "positive_passages": [{"docid": "doc-en-kubernetes-1e3d5f814d3d1cd0ae92f2f9adc262569d0e3418b95dbcb250b25bdb3821fc75", "text": "This issue proposes the writing of a new test for the API endpoint with the intention of promoting it to Conformance. This issue contains a very masic mock test in order to start the conversation about what a good e2e test would look like for this endpoint. The code below is verified to be hitting the intended endpoint, show as per the queries in APIsnoop's live view of the cluster's audit logs. According to this query, there is only one API endpoint which is for Namespace that isn't being covered. We selected patchCoreV1Namespace to write a test for. Dependencies: The mock test: If a test with these calls is build and merged, conformance will go up by 1 endpoint.\n/sig testing /sig architecture /area conformance", "commid": "kubernetes_issue_86051", "tokennum": 169}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e2b8f67c6c6914e7094a331cffc57628b1c018982fe24aca865cb2743d3b3c14", "query": "cloud: gce EOF <ins> DOCKER_OPTS=\"\" if [[ -n \"${EXTRA_DOCKER_OPTS-}\" ]]; then DOCKER_OPTS=\"${EXTRA_DOCKER_OPTS}\" fi </ins> # Decide if enable the cache <del> if [[ \"${ENABLE_DOCKER_REGISTRY_CACHE}\" == \"true\" ]]; then </del> <ins> if [[ \"${ENABLE_DOCKER_REGISTRY_CACHE}\" == \"true\" ]]; then </ins> REGION=$(echo \"${ZONE}\" | cut -f 1,2 -d -) echo \"Enable docker registry cache at region: \" $REGION <del> DOCKER_OPTS=\"--registry-mirror=\"https://${REGION}.docker-cache.clustermaster.net\"\" </del> <ins> DOCKER_OPTS=\"${DOCKER_OPTS} --registry-mirror='https://${REGION}.docker-cache.clustermaster.net'\" fi </ins> <del> cat <<EOF >>/etc/salt/minion.d/grains.conf </del> <ins> if [[ -n \"{DOCKER_OPTS}\" ]]; then cat <<EOF >>/etc/salt/minion.d/grains.conf </ins> docker_opts: $DOCKER_OPTS EOF fi", "positive_passages": [{"docid": "doc-en-kubernetes-142e8decd8d12f564814b0a08026ec0c2500ddcd8040f0182edc6a7f51b222f8", "text": "0/8 is with a company's intranet, so it can be insecure. This is similiar to \"For GCE, allow insecure registries anywhere in 10.0.0.0/8\" Thanks!\nLinking to and .\nThis was", "commid": "kubernetes_issue_2807", "tokennum": 55}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e2e629b206b5725045db59a13a56bbb1e07d0387eef65c90c0f5625c5a672282", "query": "} func TestValidateNamespaceStatusUpdate(t *testing.T) { <ins> now := util.Now() </ins> tests := []struct { oldNamespace api.Namespace namespace    api.Namespace valid        bool }{ <del> {api.Namespace{}, api.Namespace{}, true}, </del> <ins> {api.Namespace{}, api.Namespace{ Status: api.NamespaceStatus{ Phase: api.NamespaceActive, }, }, true}, </ins> {api.Namespace{ ObjectMeta: api.ObjectMeta{ Name: \"foo\"}}, api.Namespace{ ObjectMeta: api.ObjectMeta{ <del> Name: \"foo\"}, </del> <ins> Name:              \"foo\", DeletionTimestamp: &now}, </ins> Status: api.NamespaceStatus{ Phase: api.NamespaceTerminating, },", "positive_passages": [{"docid": "doc-en-kubernetes-859a8b847337ca2cf9879726f3bdb71f0db5559ee2589591ceae612e41f71a1b", "text": "There is a funny subtle behvaiour in get namespaces, in which if i call more than one time, it seems that the removal from Terminating state is accelarated. It seems this might indicate a bug, or maybe its not a bug and the eventual semantics of is a little funny sometimes. in any case, here's what we are seeing : 1) when i delete a namespace the first time usning kubectl, we get a state change to . that is correct, of course. 2) but ... if make the call a second time, then the same status line is immediately removed from . Expected behaviour : A second call to \"kubectl delete ...\" shouldn't have any effect on the timing of removal of a namespace from 'Terminating' state*... So i guess there is some \"eventual consistency\" subtle bug that is resolved by repeated calls to\nsuggests this may not be e bug, maybe its just the etcd eventual deleter thingy.\nLooks to definitely be a bug. The 2nd delete seems to have interrupted the delete process and artifacts (like events) from the namespace still exist in etcd.\ninvestigating...\noops, see the error, will submit a fix.\nI have a fix, but need a test case, will submit PR tomorrow AM", "commid": "kubernetes_issue_6633", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e31201d0ab97f53e3a1a62eb65ea8d21c9e65a52e1eb60c2972dc7392df13cdb", "query": "nodePorts[key] = true } <ins> // Check for duplicate TargetPort portsPath = specPath.Child(\"ports\") targetPorts := make(map[api.ServicePort]bool) for i, port := range service.Spec.Ports { if (port.TargetPort.Type == intstr.Int && port.TargetPort.IntVal == 0) || (port.TargetPort.Type == intstr.String && port.TargetPort.StrVal == \"\") { continue } portPath := portsPath.Index(i) key := api.ServicePort{Protocol: port.Protocol, TargetPort: port.TargetPort} _, found := targetPorts[key] if found { allErrs = append(allErrs, field.Duplicate(portPath.Child(\"targetPort\"), port.TargetPort)) } targetPorts[key] = true } </ins> // Validate SourceRange field and annotation _, ok := service.Annotations[api.AnnotationLoadBalancerSourceRangesKey] if len(service.Spec.LoadBalancerSourceRanges) > 0 || ok {", "positive_passages": [{"docid": "doc-en-kubernetes-aa91440105d9e0a880514623ff11a0ea2fc9d1181a696540d8af19c86c926acb", "text": "It is possible to express a Service where multiple front-side ports target the same back-side port. This is not very useful and may cause trouble for implementations of Services. `\njust for the purpose of clarity, are you requesting that duplicate targetPorts should be rejected or the opposite? PS: I am new to Kubernetes so please pardon the dumb question :)\nI think that should probably be rejected at validation unless we have a good reason WHY we need that.\nAye aye, thanks for the clarificiation!\n/assign\nGitHub didn't allow me to assign the following users: xiangpengzhao. Note that only can be assigned. <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\nwhat problems did this cause with services? This change broke backwards compatibility for services that depended on this feature. For example, lets take the load balancer service The load balancer here terminates SSL so the backend is always port 80; however, you want to make sure you support both protocols so having the same targetPort here is a valid use case.\nThis is an interesting (ab)use of Service. Not really what I had in mind - the LB in a Service is generally assumed to be L4. I'll try to dredge up the issues that this was causing.\nFYI, the does non layer4 things as well.\nOne issue is that this REQUIRES connection tracking when we otherwise might not need it. Consider two ServicePorts: my-service:80 mys-service:443 Let's say we map both services to a backend on port 8080, but we pass-through the VIP, so the pod sees packets as dest = my-service:8080. We MUST conntrack this VIP because we don't know whether to map the src port to 80 or 443. If service backends have unique TargetPorts, then we wouldn't have this issue. Port rewrites are at worst stateless, and at best can engage direct-return mode (no rewrites). It's worth noting that the PR which fixes this, which is proposed for revert, doesn't quite go far enough. It prevents a Service from using a given number twice and from using a given name twice, but not from using a number and a name that resolves to that number.", "commid": "kubernetes_issue_47222", "tokennum": 515}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e31201d0ab97f53e3a1a62eb65ea8d21c9e65a52e1eb60c2972dc7392df13cdb", "query": "nodePorts[key] = true } <ins> // Check for duplicate TargetPort portsPath = specPath.Child(\"ports\") targetPorts := make(map[api.ServicePort]bool) for i, port := range service.Spec.Ports { if (port.TargetPort.Type == intstr.Int && port.TargetPort.IntVal == 0) || (port.TargetPort.Type == intstr.String && port.TargetPort.StrVal == \"\") { continue } portPath := portsPath.Index(i) key := api.ServicePort{Protocol: port.Protocol, TargetPort: port.TargetPort} _, found := targetPorts[key] if found { allErrs = append(allErrs, field.Duplicate(portPath.Child(\"targetPort\"), port.TargetPort)) } targetPorts[key] = true } </ins> // Validate SourceRange field and annotation _, ok := service.Annotations[api.AnnotationLoadBalancerSourceRangesKey] if len(service.Spec.LoadBalancerSourceRanges) > 0 || ok {", "positive_passages": [{"docid": "doc-en-kubernetes-4a483a3c82b1bc41aa37a9f41461962211ab2500ff27fab076c9dbd88f68a578", "text": "That is a much trickier (impossible to do statically) proposition. :( Kind of a mess for getting high-perf Service networking.\nwas this an issue that came up during performance testing or IRL?\nAnyone has a workaround to deal with this? I think there is a lot of people using AWS ELBs on this way\nif your use-case is Ingress, then you can set . This should avoid generating the invalid Service spec. Obviously, you will lose the redirect behavior.\nThis is not an abuse of Service, but a quite common and wide-adopted pattern, especially in the AWS world.\nyou can't re-open an issue/PR unless you authored it or you are assigned to it. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nyou can't re-open an issue/PR unless you authored it or you are assigned to it. <detailsIn response to : /assign /reopen for further discussion 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\n/reopen for further discussion.\nI suspect we should probably revert the original PR. While I understand it might not have been the intention for Services, if I understand this correctly then it's a breaking change to a v1 API. Can we at least point to any documentation that indicates this was a code bug rather than a supported behavior?\nSentiment on today's sig call was that we should revert the original commit, since it broke lots of users, and then revisit to see if there's another solution.\nFYI: the revert PR is\nIssues 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\nStale 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 .", "commid": "kubernetes_issue_47222", "tokennum": 495}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e31201d0ab97f53e3a1a62eb65ea8d21c9e65a52e1eb60c2972dc7392df13cdb", "query": "nodePorts[key] = true } <ins> // Check for duplicate TargetPort portsPath = specPath.Child(\"ports\") targetPorts := make(map[api.ServicePort]bool) for i, port := range service.Spec.Ports { if (port.TargetPort.Type == intstr.Int && port.TargetPort.IntVal == 0) || (port.TargetPort.Type == intstr.String && port.TargetPort.StrVal == \"\") { continue } portPath := portsPath.Index(i) key := api.ServicePort{Protocol: port.Protocol, TargetPort: port.TargetPort} _, found := targetPorts[key] if found { allErrs = append(allErrs, field.Duplicate(portPath.Child(\"targetPort\"), port.TargetPort)) } targetPorts[key] = true } </ins> // Validate SourceRange field and annotation _, ok := service.Annotations[api.AnnotationLoadBalancerSourceRangesKey] if len(service.Spec.LoadBalancerSourceRanges) > 0 || ok {", "positive_passages": [{"docid": "doc-en-kubernetes-c9520d012b388262634de2c95cda13e5277a086c4973e0f847d3a162dd04c237", "text": "Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close", "commid": "kubernetes_issue_47222", "tokennum": 78}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e37adc53cafd89f74bfb02f5c90d82fadbfcdcad19c3f189c8ae1c8bb0a8ca3d", "query": "\"name\":        \"The name of this port. All ports in an EndpointSlice must have a unique name. If the EndpointSlice is dervied from a Kubernetes service, this corresponds to the Service.ports[].name. Name must either be an empty string or pass DNS_LABEL validation: * must be no more than 63 characters long. * must consist of lower case alphanumeric characters or '-'. * must start and end with an alphanumeric character. Default is empty string.\", \"protocol\":    \"The IP protocol for this port. Must be UDP, TCP, or SCTP. Default is TCP.\", \"port\":        \"The port number of the endpoint. If this is not specified, ports are not restricted and must be interpreted in the context of the specific consumer.\", <del> \"appProtocol\": \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and http://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.\", </del> <ins> \"appProtocol\": \"The application protocol for this port. This field follows standard Kubernetes label syntax. Un-prefixed names are reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.\", </ins> } func (EndpointPort) SwaggerDoc() map[string]string {", "positive_passages": [{"docid": "doc-en-kubernetes-3e7e95e6f142ca39e6e3ca0b78c3932bd6cbdfdc898eed9d3ffda27d28f904c7", "text": "We should make the change in PR API reference links to should use HTTPS, not HTTP Visit h and look at the IANA hyperlinks Once this fix is made, a PR to is needed to update the docs (by autogenerating them). This typically would be deferred until the next Kubernetes release. v1.23 not applicable not applicable not applicable not applicable not applicable\n/sig docs\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI opened this issue so that someone else can open a new PR that is equivalent to .\n/retitle Update links to IANA for Service Name and Transport Protocol Port Number Registry\nI would like to work on this issue. May I assign it to myself?\nAnyone - including you - is welcome to work on this issue! So long as you've you can open a pull request to propose a fix.\nThanks\n/assign\nI have made the PR. I hope this works. If not then will be happy to do the necessary changes.\nHad to close the previous PR because of issues, here is the new one I made.", "commid": "kubernetes_issue_106980", "tokennum": 300}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e3c9743f3d1f5bce3da58fda910da1704e3862ab0f01a60804752c2a7837a2cf", "query": "\"reflect\" \"sort\" \"testing\" <ins> \"time\" </ins> \"github.com/stretchr/testify/assert\" \"github.com/stretchr/testify/require\"", "positive_passages": [{"docid": "doc-en-kubernetes-4510e09c6fe68ed5e12ffcf7126f6af8b2755c8c7c2f631bec51ed41fca52919", "text": "What happened: One pod stuck at CreateContainerError and can't get recovered automatically. Kubelet log shows that the requested name (let's say Container2) is already in use. shows the Container2 Running, and it's created before Container1 This should never happen. How to reproduce it (as minimally and precisely as possible): I wish i knew. Anything else we need to know?: I know this can be caused by time shifting, but I didn't find any time shifting sign in system log and chrony log, and there is no rebooting between the create timestamp of Container1 and Container2, so this should be caused by something else. This happens intermittently in our env, like 3 times in half a year, and I didn't find any ime shifting sign each time. Environment: Kubernetes version (use ): Client Version: version.Info{Major:\"1\", Minor:\"15\", GitVersion:\"v1.15.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2019-11-13T11:20:18Z\", GoVersion:\"go1.12.12\", Compiler:\"gc\", Platform:\"linux/amd64\"} Server Version: version.Info{Major:\"1\", Minor:\"15\", GitVersion:\"v1.15.6\", GitCommit:\"\", GitTreeState:\"clean\", BuildDate:\"2020-08-28T11:18:26Z\", GoVersion:\"go1.12.12\", Compiler:\"gc\", Platform:\"linux/amd64\"} Cloud provider or hardware configuration: OS (e.g: ): CentOS Linux release 7.5.1804 (Core) Kernel (e.g. ): Linux node-1 3.10.0-957.21.3.el7.x8664 SMP Wed Jul 17 06:57:50 UTC 2019 x8664 x8664 x86_64 GNU/Linux Install tools: kubeadm Network plugin and version (if this is a network-related bug): Others:\n/sig node\nAny update on this issue, we are also facing the same issue. EKS version : 1.14.9 Docker version: 19.03.6-ce AWS CNI: 1.6.2 Intermittently we are also facing this , what might the issue, could please guide us here? Below are the kubelet logs. )\"", "commid": "kubernetes_issue_94557", "tokennum": 571}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e3c9743f3d1f5bce3da58fda910da1704e3862ab0f01a60804752c2a7837a2cf", "query": "\"reflect\" \"sort\" \"testing\" <ins> \"time\" </ins> \"github.com/stretchr/testify/assert\" \"github.com/stretchr/testify/require\"", "positive_passages": [{"docid": "doc-en-kubernetes-cf3a33a19ef0552fe6ccd0d8ccfc3a21fead851f6c57fd16801184b4e1e277da", "text": "with CreatePodSandboxError: \"CreatePodSandbox for pod \"-f0fe-11ea-9872-)\" failed: rpc error: code = Unknown desc = failed to create a sandbox for pod \"aiqx-server-dep--b9lmv\": operation timeout: context deadline exceeded\" Sep 07 11:40:40 kubelet[2899]: W0907 11:40:40. 2899 ] No ref for container \"docker://7b9c86b529530f15d941f8e68973a202c8f348ab5db864a8371e8c82ddbf9dc4\" (r(-e845-11ea-bd96-) Sep 07 11:40:43 kubelet[2899]: W0907 11:40:43. 2899 ] Unable to create pod sandbox due to conflict. Attempting to remove sandbox \"a73bd9a03d56bc7855e4e89e163e13c5e7173397f10edcc200fb686e1b6885c8\" Sep 07 11:40:43 kubelet[2899]: E0907 11:40:43. 2899 ] Failed to remove the conflicting container \"a73bd9a03d56bc7855e4e89e163e13c5e7173397f10edcc200fb686e1b6885c8\": Error: No such container: a73bd9a03d56bc7855e4e89e163e13c5e7173397f10edcc200fb686e1b6885c8\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_94557", "tokennum": 554}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e3c9743f3d1f5bce3da58fda910da1704e3862ab0f01a60804752c2a7837a2cf", "query": "\"reflect\" \"sort\" \"testing\" <ins> \"time\" </ins> \"github.com/stretchr/testify/assert\" \"github.com/stretchr/testify/require\"", "positive_passages": [{"docid": "doc-en-kubernetes-af4ac4b9e185e9334a90bdc75507d53790e8bdc2018fef7b4f1e5e30a35b49e6", "text": "/lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /close\nClosing 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", "commid": "kubernetes_issue_94557", "tokennum": 110}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e3ea27c28e9ec644df6b6cd8b38006c4fda54723d9cfc34950d68669f8f51680", "query": "<del> { \"apiVersion\": \"apidiscovery.k8s.io/v2beta1\", \"items\": [ { \"metadata\": { \"creationTimestamp\": null, \"name\": \"apiregistration.k8s.io\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"categories\": [ \"api-extensions\" ], \"resource\": \"apiservices\", \"responseKind\": { \"group\": \"\", \"kind\": \"APIService\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"apiservice\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"APIService\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"apps\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"controllerrevisions\", \"responseKind\": { \"group\": \"\", \"kind\": \"ControllerRevision\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"singularResource\": \"controllerrevision\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"categories\": [ \"all\" ], \"resource\": \"daemonsets\", \"responseKind\": { \"group\": \"\", \"kind\": \"DaemonSet\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"shortNames\": [ \"ds\" ], \"singularResource\": \"daemonset\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"DaemonSet\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"categories\": [ \"all\" ], \"resource\": \"deployments\", \"responseKind\": { \"group\": \"\", \"kind\": \"Deployment\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"shortNames\": [ \"deploy\" ], \"singularResource\": \"deployment\", \"subresources\": [ { \"responseKind\": { \"group\": \"autoscaling\", \"kind\": \"Scale\", \"version\": \"v1\" }, \"subresource\": \"scale\", \"verbs\": [ \"get\", \"patch\", \"update\" ] }, { \"responseKind\": { \"group\": \"\", \"kind\": \"Deployment\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"categories\": [ \"all\" ], \"resource\": \"replicasets\", \"responseKind\": { \"group\": \"\", \"kind\": \"ReplicaSet\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"shortNames\": [ \"rs\" ], \"singularResource\": \"replicaset\", \"subresources\": [ { \"responseKind\": { \"group\": \"autoscaling\", \"kind\": \"Scale\", \"version\": \"v1\" }, \"subresource\": \"scale\", \"verbs\": [ \"get\", \"patch\", \"update\" ] }, { \"responseKind\": { \"group\": \"\", \"kind\": \"ReplicaSet\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"categories\": [ \"all\" ], \"resource\": \"statefulsets\", \"responseKind\": { \"group\": \"\", \"kind\": \"StatefulSet\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"shortNames\": [ \"sts\" ], \"singularResource\": \"statefulset\", \"subresources\": [ { \"responseKind\": { \"group\": \"autoscaling\", \"kind\": \"Scale\", \"version\": \"v1\" }, \"subresource\": \"scale\", \"verbs\": [ \"get\", \"patch\", \"update\" ] }, { \"responseKind\": { \"group\": \"\", \"kind\": \"StatefulSet\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"events.k8s.io\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"events\", \"responseKind\": { \"group\": \"\", \"kind\": \"Event\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"shortNames\": [ \"ev\" ], \"singularResource\": \"event\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"authentication.k8s.io\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"selfsubjectreviews\", \"responseKind\": { \"group\": \"\", \"kind\": \"SelfSubjectReview\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"selfsubjectreview\", \"verbs\": [ \"create\" ] }, { \"resource\": \"tokenreviews\", \"responseKind\": { \"group\": \"\", \"kind\": \"TokenReview\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"tokenreview\", \"verbs\": [ \"create\" ] } ], \"version\": \"v1\" }, { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"selfsubjectreviews\", \"responseKind\": { \"group\": \"\", \"kind\": \"SelfSubjectReview\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"selfsubjectreview\", \"verbs\": [ \"create\" ] } ], \"version\": \"v1beta1\" }, { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"selfsubjectreviews\", \"responseKind\": { \"group\": \"\", \"kind\": \"SelfSubjectReview\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"selfsubjectreview\", \"verbs\": [ \"create\" ] } ], \"version\": \"v1alpha1\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"authorization.k8s.io\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"localsubjectaccessreviews\", \"responseKind\": { \"group\": \"\", \"kind\": \"LocalSubjectAccessReview\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"singularResource\": \"localsubjectaccessreview\", \"verbs\": [ \"create\" ] }, { \"resource\": \"selfsubjectaccessreviews\", \"responseKind\": { \"group\": \"\", \"kind\": \"SelfSubjectAccessReview\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"selfsubjectaccessreview\", \"verbs\": [ \"create\" ] }, { \"resource\": \"selfsubjectrulesreviews\", \"responseKind\": { \"group\": \"\", \"kind\": \"SelfSubjectRulesReview\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"selfsubjectrulesreview\", \"verbs\": [ \"create\" ] }, { \"resource\": \"subjectaccessreviews\", \"responseKind\": { \"group\": \"\", \"kind\": \"SubjectAccessReview\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"subjectaccessreview\", \"verbs\": [ \"create\" ] } ], \"version\": \"v1\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"autoscaling\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"categories\": [ \"all\" ], \"resource\": \"horizontalpodautoscalers\", \"responseKind\": { \"group\": \"\", \"kind\": \"HorizontalPodAutoscaler\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"shortNames\": [ \"hpa\" ], \"singularResource\": \"horizontalpodautoscaler\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"HorizontalPodAutoscaler\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v2\" }, { \"freshness\": \"Current\", \"resources\": [ { \"categories\": [ \"all\" ], \"resource\": \"horizontalpodautoscalers\", \"responseKind\": { \"group\": \"\", \"kind\": \"HorizontalPodAutoscaler\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"shortNames\": [ \"hpa\" ], \"singularResource\": \"horizontalpodautoscaler\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"HorizontalPodAutoscaler\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"batch\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"categories\": [ \"all\" ], \"resource\": \"cronjobs\", \"responseKind\": { \"group\": \"\", \"kind\": \"CronJob\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"shortNames\": [ \"cj\" ], \"singularResource\": \"cronjob\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"CronJob\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"categories\": [ \"all\" ], \"resource\": \"jobs\", \"responseKind\": { \"group\": \"\", \"kind\": \"Job\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"singularResource\": \"job\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"Job\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"certificates.k8s.io\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"certificatesigningrequests\", \"responseKind\": { \"group\": \"\", \"kind\": \"CertificateSigningRequest\", \"version\": \"\" }, \"scope\": \"Cluster\", \"shortNames\": [ \"csr\" ], \"singularResource\": \"certificatesigningrequest\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"CertificateSigningRequest\", \"version\": \"\" }, \"subresource\": \"approval\", \"verbs\": [ \"get\", \"patch\", \"update\" ] }, { \"responseKind\": { \"group\": \"\", \"kind\": \"CertificateSigningRequest\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1\" }, { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"clustertrustbundles\", \"responseKind\": { \"group\": \"\", \"kind\": \"ClusterTrustBundle\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"clustertrustbundle\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1alpha1\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"networking.k8s.io\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"ingressclasses\", \"responseKind\": { \"group\": \"\", \"kind\": \"IngressClass\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"ingressclass\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"resource\": \"ingresses\", \"responseKind\": { \"group\": \"\", \"kind\": \"Ingress\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"shortNames\": [ \"ing\" ], \"singularResource\": \"ingress\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"Ingress\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"resource\": \"networkpolicies\", \"responseKind\": { \"group\": \"\", \"kind\": \"NetworkPolicy\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"shortNames\": [ \"netpol\" ], \"singularResource\": \"networkpolicy\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1\" }, { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"ipaddresses\", \"responseKind\": { \"group\": \"\", \"kind\": \"IPAddress\", \"version\": \"\" }, \"scope\": \"Cluster\", \"shortNames\": [ \"ip\" ], \"singularResource\": \"ipaddress\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"resource\": \"servicecidrs\", \"responseKind\": { \"group\": \"\", \"kind\": \"ServiceCIDR\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"servicecidr\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"ServiceCIDR\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1beta1\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"policy\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"poddisruptionbudgets\", \"responseKind\": { \"group\": \"\", \"kind\": \"PodDisruptionBudget\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"shortNames\": [ \"pdb\" ], \"singularResource\": \"poddisruptionbudget\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"PodDisruptionBudget\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"rbac.authorization.k8s.io\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"clusterrolebindings\", \"responseKind\": { \"group\": \"\", \"kind\": \"ClusterRoleBinding\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"clusterrolebinding\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"resource\": \"clusterroles\", \"responseKind\": { \"group\": \"\", \"kind\": \"ClusterRole\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"clusterrole\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"resource\": \"rolebindings\", \"responseKind\": { \"group\": \"\", \"kind\": \"RoleBinding\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"singularResource\": \"rolebinding\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"resource\": \"roles\", \"responseKind\": { \"group\": \"\", \"kind\": \"Role\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"singularResource\": \"role\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"storage.k8s.io\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"csidrivers\", \"responseKind\": { \"group\": \"\", \"kind\": \"CSIDriver\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"csidriver\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"resource\": \"csinodes\", \"responseKind\": { \"group\": \"\", \"kind\": \"CSINode\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"csinode\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"resource\": \"csistoragecapacities\", \"responseKind\": { \"group\": \"\", \"kind\": \"CSIStorageCapacity\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"singularResource\": \"csistoragecapacity\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"resource\": \"storageclasses\", \"responseKind\": { \"group\": \"\", \"kind\": \"StorageClass\", \"version\": \"\" }, \"scope\": \"Cluster\", \"shortNames\": [ \"sc\" ], \"singularResource\": \"storageclass\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"resource\": \"volumeattachments\", \"responseKind\": { \"group\": \"\", \"kind\": \"VolumeAttachment\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"volumeattachment\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"VolumeAttachment\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1\" }, { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"volumeattributesclasses\", \"responseKind\": { \"group\": \"\", \"kind\": \"VolumeAttributesClass\", \"version\": \"\" }, \"scope\": \"Cluster\", \"shortNames\": [ \"vac\" ], \"singularResource\": \"volumeattributesclass\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1beta1\" }, { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"volumeattributesclasses\", \"responseKind\": { \"group\": \"\", \"kind\": \"VolumeAttributesClass\", \"version\": \"\" }, \"scope\": \"Cluster\", \"shortNames\": [ \"vac\" ], \"singularResource\": \"volumeattributesclass\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1alpha1\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"admissionregistration.k8s.io\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"categories\": [ \"api-extensions\" ], \"resource\": \"mutatingwebhookconfigurations\", \"responseKind\": { \"group\": \"\", \"kind\": \"MutatingWebhookConfiguration\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"mutatingwebhookconfiguration\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"categories\": [ \"api-extensions\" ], \"resource\": \"validatingadmissionpolicies\", \"responseKind\": { \"group\": \"\", \"kind\": \"ValidatingAdmissionPolicy\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"validatingadmissionpolicy\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"ValidatingAdmissionPolicy\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"categories\": [ \"api-extensions\" ], \"resource\": \"validatingadmissionpolicybindings\", \"responseKind\": { \"group\": \"\", \"kind\": \"ValidatingAdmissionPolicyBinding\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"validatingadmissionpolicybinding\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"categories\": [ \"api-extensions\" ], \"resource\": \"validatingwebhookconfigurations\", \"responseKind\": { \"group\": \"\", \"kind\": \"ValidatingWebhookConfiguration\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"validatingwebhookconfiguration\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1\" }, { \"freshness\": \"Current\", \"resources\": [ { \"categories\": [ \"api-extensions\" ], \"resource\": \"validatingadmissionpolicies\", \"responseKind\": { \"group\": \"\", \"kind\": \"ValidatingAdmissionPolicy\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"validatingadmissionpolicy\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"ValidatingAdmissionPolicy\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"categories\": [ \"api-extensions\" ], \"resource\": \"validatingadmissionpolicybindings\", \"responseKind\": { \"group\": \"\", \"kind\": \"ValidatingAdmissionPolicyBinding\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"validatingadmissionpolicybinding\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1beta1\" }, { \"freshness\": \"Current\", \"resources\": [ { \"categories\": [ \"api-extensions\" ], \"resource\": \"validatingadmissionpolicies\", \"responseKind\": { \"group\": \"\", \"kind\": \"ValidatingAdmissionPolicy\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"validatingadmissionpolicy\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"ValidatingAdmissionPolicy\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"categories\": [ \"api-extensions\" ], \"resource\": \"validatingadmissionpolicybindings\", \"responseKind\": { \"group\": \"\", \"kind\": \"ValidatingAdmissionPolicyBinding\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"validatingadmissionpolicybinding\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1alpha1\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"apiextensions.k8s.io\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"categories\": [ \"api-extensions\" ], \"resource\": \"customresourcedefinitions\", \"responseKind\": { \"group\": \"\", \"kind\": \"CustomResourceDefinition\", \"version\": \"\" }, \"scope\": \"Cluster\", \"shortNames\": [ \"crd\", \"crds\" ], \"singularResource\": \"customresourcedefinition\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"CustomResourceDefinition\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"scheduling.k8s.io\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"priorityclasses\", \"responseKind\": { \"group\": \"\", \"kind\": \"PriorityClass\", \"version\": \"\" }, \"scope\": \"Cluster\", \"shortNames\": [ \"pc\" ], \"singularResource\": \"priorityclass\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"coordination.k8s.io\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"leases\", \"responseKind\": { \"group\": \"\", \"kind\": \"Lease\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"singularResource\": \"lease\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1\" }, { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"leasecandidates\", \"responseKind\": { \"group\": \"\", \"kind\": \"LeaseCandidate\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"singularResource\": \"leasecandidate\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1alpha1\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"node.k8s.io\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"runtimeclasses\", \"responseKind\": { \"group\": \"\", \"kind\": \"RuntimeClass\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"runtimeclass\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"discovery.k8s.io\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"endpointslices\", \"responseKind\": { \"group\": \"\", \"kind\": \"EndpointSlice\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"singularResource\": \"endpointslice\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"flowcontrol.apiserver.k8s.io\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"flowschemas\", \"responseKind\": { \"group\": \"\", \"kind\": \"FlowSchema\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"flowschema\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"FlowSchema\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"resource\": \"prioritylevelconfigurations\", \"responseKind\": { \"group\": \"\", \"kind\": \"PriorityLevelConfiguration\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"prioritylevelconfiguration\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"PriorityLevelConfiguration\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1\" }, { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"flowschemas\", \"responseKind\": { \"group\": \"\", \"kind\": \"FlowSchema\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"flowschema\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"FlowSchema\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"resource\": \"prioritylevelconfigurations\", \"responseKind\": { \"group\": \"\", \"kind\": \"PriorityLevelConfiguration\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"prioritylevelconfiguration\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"PriorityLevelConfiguration\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1beta3\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"internal.apiserver.k8s.io\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"storageversions\", \"responseKind\": { \"group\": \"\", \"kind\": \"StorageVersion\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"storageversion\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"StorageVersion\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1alpha1\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"resource.k8s.io\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"deviceclasses\", \"responseKind\": { \"group\": \"\", \"kind\": \"DeviceClass\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"deviceclass\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"resource\": \"podschedulingcontexts\", \"responseKind\": { \"group\": \"\", \"kind\": \"PodSchedulingContext\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"singularResource\": \"podschedulingcontext\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"PodSchedulingContext\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"resource\": \"resourceclaims\", \"responseKind\": { \"group\": \"\", \"kind\": \"ResourceClaim\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"singularResource\": \"resourceclaim\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"ResourceClaim\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"resource\": \"resourceclaimtemplates\", \"responseKind\": { \"group\": \"\", \"kind\": \"ResourceClaimTemplate\", \"version\": \"\" }, \"scope\": \"Namespaced\", \"singularResource\": \"resourceclaimtemplate\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] }, { \"resource\": \"resourceslices\", \"responseKind\": { \"group\": \"\", \"kind\": \"ResourceSlice\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"resourceslice\", \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1alpha3\" } ] }, { \"metadata\": { \"creationTimestamp\": null, \"name\": \"storagemigration.k8s.io\" }, \"versions\": [ { \"freshness\": \"Current\", \"resources\": [ { \"resource\": \"storageversionmigrations\", \"responseKind\": { \"group\": \"\", \"kind\": \"StorageVersionMigration\", \"version\": \"\" }, \"scope\": \"Cluster\", \"singularResource\": \"storageversionmigration\", \"subresources\": [ { \"responseKind\": { \"group\": \"\", \"kind\": \"StorageVersionMigration\", \"version\": \"\" }, \"subresource\": \"status\", \"verbs\": [ \"get\", \"patch\", \"update\" ] } ], \"verbs\": [ \"create\", \"delete\", \"deletecollection\", \"get\", \"list\", \"patch\", \"update\", \"watch\" ] } ], \"version\": \"v1alpha1\" } ] } ], \"kind\": \"APIGroupDiscoveryList\", \"metadata\": {} } </del>", "positive_passages": [{"docid": "doc-en-kubernetes-1f38d50a57cfbeef9d8517599fecefb7d45971350552d6bdbc65534ca41945d0", "text": "Aggregated discovery v2beta1 fixtures should be removed. /sig api-machinery /triage accepted", "commid": "kubernetes_issue_127007", "tokennum": 22}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e408411725f8c8e4c0fe5b2da97503fe84575b975c20347883cfb9d092014000", "query": "if !pluginStatus.IsUnschedulable() { // Filter plugins are not supposed to return any status other than // Success or Unschedulable. <del> errStatus := framework.AsStatus(fmt.Errorf(\"running %q filter plugin: %w\", pl.Name(), pluginStatus.AsError())).WithFailedPlugin(pl.Name()) return map[string]*framework.Status{pl.Name(): errStatus} </del> <ins> pluginStatus = framework.AsStatus(fmt.Errorf(\"running %q filter plugin: %w\", pl.Name(), pluginStatus.AsError())) </ins> } pluginStatus.SetFailedPlugin(pl.Name()) <del> statuses[pl.Name()] = pluginStatus </del> <ins> return map[string]*framework.Status{pl.Name(): pluginStatus} </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-63751a7023e8b04f1af20ab3ae3207ec2b4f40a0fbf73a42db07ba523eb8b990", "text": "changed the default behavior of scheduler framework's - from stopping at the first failed filter to always running all filters. This change breaks Cluster Autoscaler at scale. Cluster Autoscaler imports the scheduler framework to simulate filters on artificial nodes. In a (pretty common) one-pod-per-node scenario, the number of calls is ~quadratic wrt. the number of nodes needed for unschedulable pods - it can be a lot of calls. Before , in such scenario the vast majority of calls would stop at failing Fit or NodeAffinity filters, and not run the rest of them (e.g. PV-related filters). After the change, every call to runs all filters, which completely breaks Cluster Autoscaler at scale (an example scenario of 300 1-pod-per-node pods and 200 node groups takes 10min in 1.24, and ~50s in <1.22). Can we get the old behavior back? Or re-introduce the config option so that Cluster Autoscaler can set it accordingly? Ideally, we'd also like to get this backported as far as possible (the change was introduced in 1.24).\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scheduling\nThis seems to be a regression. I would be interested in adding a toggle flag that allows one to toggle on that behavior if this was done on purpose.\nThat PR wasn't supposed to change the behavior actually. Scheduler is always defaulted to stop upon the first Filter failure, and it's just we offered an option to continue go through other Filter plugins upon failures, and that option was removed recently. Let me check the code to see if there is a regression.\nWhen removed the following changes: It should have kept . I will submit a fix along with test, and backport to 1.24, 1.25, 1.26. Thanks for reporting!", "commid": "kubernetes_issue_114509", "tokennum": 478}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e408411725f8c8e4c0fe5b2da97503fe84575b975c20347883cfb9d092014000", "query": "if !pluginStatus.IsUnschedulable() { // Filter plugins are not supposed to return any status other than // Success or Unschedulable. <del> errStatus := framework.AsStatus(fmt.Errorf(\"running %q filter plugin: %w\", pl.Name(), pluginStatus.AsError())).WithFailedPlugin(pl.Name()) return map[string]*framework.Status{pl.Name(): errStatus} </del> <ins> pluginStatus = framework.AsStatus(fmt.Errorf(\"running %q filter plugin: %w\", pl.Name(), pluginStatus.AsError())) </ins> } pluginStatus.SetFailedPlugin(pl.Name()) <del> statuses[pl.Name()] = pluginStatus </del> <ins> return map[string]*framework.Status{pl.Name(): pluginStatus} </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-64891c2c5f731cd49a5bc282c860dc0eba8f556ac4ce7c46f89d192c47705edc", "text": "cc /assign /kind bug /kind regression /priority critical-urgent /triage/accepted\nThanks Kuba, this is indeed a regression on the scheduler end.\n/open for patches\n/re-open /reopen\nReopened this issue. <detailsIn response to : /re-open /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThanks for the reporting, and thanks for the fix.\nReally sorry about this regression, and hope not to happen again. I think there's no e2e tests between kubernetes scheduler and cluster-autoscaler, so can we also have testcases of pods unschedulable in scheduling perf-test, maybe this can also help to prevent this happening again. UT benchmark test also makes sense, but it's not graphical.\nThanks for the quick fix! Unfortunately I'm afraid this kind of issue would only be caught in a large-scale test scenario, which is not cheap to run continuously.\nFor this particular issue, UT ( in the PR) is able to catch it. And hence doesn't need to be that complicated to test with cluster-autoscaler. However, standing from a broader angle, why we didn't catch the regression in perf test is b/c the triggering actor is unschedulable Pods, instead of schedulable Pods (which are the happy path most perf tests covered). So going forward, I'd like to see more perf tests to mixin unschedulable Pods, and hence more likely to surface this kind of issue. (we have preemptio preemption test suite but doesn't seem adequate)\nThis is not for the particular issue, but keeping an eye on whether there's any performance degradation between two kubernetes components, like we do for scheduling performance. but it's actually out of the scope of scheduler. I'll add it as one of the goals of\nActually, the schedulerperf has a test case . And, the schedulerperf collects the metric (), which has the label in it (). But, the problem is currently we don't distinguish the metric values by label on each data; we just collect/aggregate it regardless the label.", "commid": "kubernetes_issue_114509", "tokennum": 494}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e408411725f8c8e4c0fe5b2da97503fe84575b975c20347883cfb9d092014000", "query": "if !pluginStatus.IsUnschedulable() { // Filter plugins are not supposed to return any status other than // Success or Unschedulable. <del> errStatus := framework.AsStatus(fmt.Errorf(\"running %q filter plugin: %w\", pl.Name(), pluginStatus.AsError())).WithFailedPlugin(pl.Name()) return map[string]*framework.Status{pl.Name(): errStatus} </del> <ins> pluginStatus = framework.AsStatus(fmt.Errorf(\"running %q filter plugin: %w\", pl.Name(), pluginStatus.AsError())) </ins> } pluginStatus.SetFailedPlugin(pl.Name()) <del> statuses[pl.Name()] = pluginStatus </del> <ins> return map[string]*framework.Status{pl.Name(): pluginStatus} </ins> } }", "positive_passages": [{"docid": "doc-en-kubernetes-e7a581bff1a17589b65e3454390d917eb3d7571d932e457d6db360afa738d97e", "text": "(We can distinguish the metric values by any labels in the schedulerperf as we do in the metric ()) I'd say just distinguishing the happy path and unhappy path with label in metric should be enough to observe the particular performance degradation in the unhappy path.\ncould you help share the perf-dash link where this metric () is exposed?\nHm, cannot see any scheduler metrics result from the current perf-dash I see some configuration that seems to be to parse the schedulerperf result file though. https://perf- TBH, I haven't visited the perf-dash so much, so not sure whether it's not working for a long time, or got broken recently. Also, another thing, I noticed the perf-dash doesn't show all test cases. All test cases after haven't been executed.\nSo... probably, something wrong happens in  job (probably in the test case) and the schedulerperf is failing. The schedulerperf doesn't make the result file when fails, so I'm guessing that's why we cannot see any scheduler metrics results from the perf-dash. Okay, I found it. Let me open another issue for this.\ncc is this actually a regression, and is it resolved yet?\nIt's resolved by , and also cherry-picked to 1.24.x ~ 1.26.x. /close\nClosing this issue. <detailsIn response to : It's resolved by , and also cherry-picked to 1.24.x ~ 1.26.x. 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", "commid": "kubernetes_issue_114509", "tokennum": 369}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e412c671f8595c801bb6cba52a2c8d9739ea64487c4bc7c7a5d75db57da4c072", "query": "} } <ins> func TestDescribePodSecurityPolicy(t *testing.T) { expected := []string{ \"Name:t*mypsp\", \"Allow Privileged:t*false\", \"Default Add Capabilities:t*<none>\", \"Required Drop Capabilities:t*<none>\", \"Allowed Capabilities:t*<none>\", \"Allowed Volume Types:t*<none>\", \"Allow Host Network:t*false\", \"Allow Host Ports:t*<none>\", \"Allow Host PID:t*false\", \"Allow Host IPC:t*false\", \"Read Only Root Filesystem:t*false\", \"SELinux Context Strategy: RunAsAny\", \"User:t*<none>\", \"Role:t*<none>\", \"Type:t*<none>\", \"Level:t*<none>\", \"Run As User Strategy: RunAsAny\", \"FSGroup Strategy: RunAsAny\", \"Supplemental Groups Strategy: RunAsAny\", } fake := fake.NewSimpleClientset(&extensions.PodSecurityPolicy{ ObjectMeta: metav1.ObjectMeta{ Name: \"mypsp\", }, Spec: extensions.PodSecurityPolicySpec{ SELinux: extensions.SELinuxStrategyOptions{ Rule: extensions.SELinuxStrategyRunAsAny, }, RunAsUser: extensions.RunAsUserStrategyOptions{ Rule: extensions.RunAsUserStrategyRunAsAny, }, FSGroup: extensions.FSGroupStrategyOptions{ Rule: extensions.FSGroupStrategyRunAsAny, }, SupplementalGroups: extensions.SupplementalGroupsStrategyOptions{ Rule: extensions.SupplementalGroupsStrategyRunAsAny, }, }, }) c := &describeClient{T: t, Namespace: \"\", Interface: fake} d := PodSecurityPolicyDescriber{c} out, err := d.Describe(\"\", \"mypsp\", printers.DescriberSettings{}) if err != nil { t.Fatalf(\"unexpected error: %v\", err) } for _, item := range expected { if matched, _ := regexp.MatchString(item, out); !matched { t.Errorf(\"Expected to find %q in: %q\", item, out) } } } </ins> func TestDescribeResourceQuota(t *testing.T) { fake := fake.NewSimpleClientset(&api.ResourceQuota{ ObjectMeta: metav1.ObjectMeta{", "positive_passages": [{"docid": "doc-en-kubernetes-6d76348628664e8e1283688eb2571b9c9ddbeb679dd9d941b90f8deb0741d5d7", "text": "Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see ): No What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): describe psp Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST Kubernetes version (use ): Environment: Doesn't matter. What happened: doesn't show PSP's fields: What you expected to happen: All PSP fields should be shown. How to reproduce it (as minimally and precisely as possible):\nIf you're agree with that than I (or :) ) could implement it.\nyes, improve the describer. Look at the scc describer for formatting.\nany ideas which SIG should own PSP?\nIn this case it should be sig-cli /sig cli\nyeah, this is cli related. I'd go with sig-auth for actual behavior.", "commid": "kubernetes_issue_43757", "tokennum": 222}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e42d941083ad5efe8da95eefc11245db8034d25f41a61b9f2bd33cc8e8a8457e", "query": "createdConts.Insert(p[:n-8]) } } <del> // We expect 9: 2 pod infra containers + 2 pods from the replication controller + //              1 pod infra container + 2 pods from the URL + //              1 pod infra container + 1 pod from the service test. // In addition, runStaticPodTest creates 1 pod infra containers + //                                       1 pod container from the mainfest file // The total number of container created is 11 </del> <ins> // We expect 9: 2 pod infra containers + 2 containers from the replication controller + //              1 pod infra container + 2 containers from the URL on first Kubelet + //              1 pod infra container + 2 containers from the URL on second Kubelet + //              1 pod infra container + 1 container from the service test. // In addition, runStaticPodTest creates 2 pod infra containers + //                                       2 pod containers from the file (1 for manifest and 1 for spec) // The total number of container created is 13 </ins> <del> if len(createdConts) != 11 { glog.Fatalf(\"Expected 11 containers; got %vnnlist of created containers:nn%#vnnDocker 1 Created:nn%#vnnDocker 2 Created:nn%#vnn\", len(createdConts), createdConts.List(), fakeDocker1.Created, fakeDocker2.Created) </del> <ins> if len(createdConts) != 16 { glog.Fatalf(\"Expected 16 containers; got %vnnlist of created containers:nn%#vnnDocker 1 Created:nn%#vnnDocker 2 Created:nn%#vnn\", len(createdConts), createdConts.List(), fakeDocker1.Created, fakeDocker2.Created) </ins> } glog.Infof(\"OK - found created containers: %#v\", createdConts.List()) } // ServeCachedManifestFile serves a file for kubelet to read. <del> func ServeCachedManifestFile() (servingAddress string) { </del> <ins> func ServeCachedManifestFile(contents string) (servingAddress string) { </ins> server := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) { if r.URL.Path == \"/manifest\" { <del> w.Write([]byte(testManifestFile)) </del> <ins> w.Write([]byte(contents)) </ins> return } glog.Fatalf(\"Got request: %#vn\", r)", "positive_passages": [{"docid": "doc-en-kubernetes-56027fa26048aea64718f2bd7d7c5d6f58ddca1472c1fc738c03141b6dea3ad6", "text": "Currently it assumes it can read ContainerManifest - it should try both\nWhy not hold on this until we have Kubelet-read-Pod in?\nAlso the HTTP source has the same problem.\nIt should read Pod. Changed the title.\nIdeally, I'd like all Pods created directly via Kubelet to be to etcd and surfaced via the API. If updates are made via the API, I'd like those to propagate back to the node. We can discuss whether the config file should be updated or ignored. At some point, I'd like Kubelet to persistently cache pods received from the apiserver, perhaps by just writing them all out as config files.\nis the issue to sync local pods back to apiserver.\nthis is somewhat related to other issues we talked about.\nDetail: We want locally specified pods to be able to use YAML config files, but we also want to rip YAML out of the API server . The config-file behavior should be as similar to the kubectl experience. Kubelet could use parts of the kubectl library to translate YAML to JSON. Vision: Eventually, I'd like Kubelet to use the apiserver library and support exactly the same Pod API as the master, at which time I'd like kubectl be able to create pods directly on Kubelets, as well as reading from config files. I also expect to have a per-node controller . I'd like to be able to use the per-node controller to update pods started via config files (or direct kubectl-kubelet pods), overriding those original files. For availability and self-hosting, we'll eventually need local checkpointing , ideally just using serialized JSON for each object. If Kubelet used apiserver, this could be done using a custom registry implementation.\nI think that is a prerequisite for it.\nIf noone picks it up, I'm going to start working on it tomorrow.\nthanks, wojtek-t\nfixed it for http channel", "commid": "kubernetes_issue_3372", "tokennum": 445}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e43508cc8a8b87bedfc6f8689ea0cd3754674a455376341c3dbd71143f0918a3", "query": "command: - /heapster - --source=kubernetes.summary_api:'' <del> - image: gcr.io/google_containers/addon-resizer:1.5 </del> <ins> - image: gcr.io/google_containers/addon-resizer:1.6 </ins> name: heapster-nanny resources: limits:", "positive_passages": [{"docid": "doc-en-kubernetes-aa5745d62aee7fc04015b35348d752ab217dfca76565e758f0ca6e53fe701514", "text": "HPA tests are currently failing in gke-large cluster suite: I did some debugging and the problem seems to be related to pod-nanny. Looking into logs from the last run: was first scheduled on the large node dedicated to it pod-nany updated heapster deployment then heapster was scheduled on the normal node (when it actually shouldn't fit) that point it was never updated by the pod nanny. that point, heapster started crashlooping (OOMing) [which in fact was expected in too small machine] So it's pretty clear that that pod-nanny changed the amount of resources to something smaller, which in fact it shouldn't.", "commid": "kubernetes_issue_31950", "tokennum": 140}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e461d5a4abae83b4fcba7d918c5928cf9a10e8e3f688542105313c1510c4ced5", "query": "testAPIVersion = \"testgroup/testversion\" ) <del> var scheme *runtime.Scheme func init() { scheme = runtime.NewScheme() metav1.AddMetaToScheme(scheme) } </del> func newPartialObjectMetadata(apiVersion, kind, namespace, name string) *metav1.PartialObjectMetadata { return &metav1.PartialObjectMetadata{ TypeMeta: metav1.TypeMeta{", "positive_passages": [{"docid": "doc-en-kubernetes-d7e6fda1614d5720cc8c8b15824f08c5e880f7950d0c5cc5cd811c2fcceb82ab", "text": "Because of this scheme mutation, this leads to concurrent use of the same scheme to cause the program to panic. It would be ideal to do this in some concurrent safe manner or add a warning or similar\n/sig api-machinery\n/assign\n/assign /triage accepted", "commid": "kubernetes_issue_107823", "tokennum": 54}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e49e0305ea50fc0921cb376627bf54e2b7b34776b10fb41aa282238540388f61", "query": "<del> apiVersion: v1 kind: Service metadata: name: elasticsearch labels: component: elasticsearch role: client spec: type: LoadBalancer selector: component: elasticsearch role: client ports: - name: http port: 9200 protocol: TCP </del>", "positive_passages": [{"docid": "doc-en-kubernetes-5fef938b0452d0f6b58e576cd11f17813fb6d6b970f83a7868d905b7784a5e39", "text": "Presently, the elasticsearch example Kubernetes configurations target elasticsearch v1.7.1, which is quite old. As of this writing, the latest elasticsearch release is v5.6.2, with many deployment changes since then. Could the elasticsearch examples be updated to target the v5 series of elasticsearch? See for a more up to date reference configuration.\ncc\nhey it's been a long while since I last contributed to the docs. i can do it soon but i need pointers on how to properly do it.\nhey, so we need to update the stuff under examples/elasticsearch/ *&repos=kubernetes So basically update the images, yaml files etc and test that everything works (and submit a PR)\n/sig testing\nAh, so there's no documentation updates anymore. OK I'll take care of it, assign it to me.\nIssues 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\nGitHub didn't allow me to assign the following users: me. Note that only and repo collaborators can be assigned. <detailsIn response to : /assign me 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\n/assign pires\n/remove-lifecycle stale\nit seems that the example moved to I am now reading that repo guidelines and will update this there. I'll also open a PR that cleans this folder in the current repo and closes this issue.", "commid": "kubernetes_issue_53142", "tokennum": 387}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e4ceefd4801815ce240b9bd7cf07027b5e156462d0fb2c91a737d0aae7e0440d", "query": "// More details here: https://github.com/kubernetes/kubernetes/issues/50986 AutoDetectCloudProvider = \"auto-detect\" <del> defaultIPTablesMasqueradeBit = 14 defaultIPTablesDropBit       = 15 </del> <ins> DefaultIPTablesMasqueradeBit = 14 DefaultIPTablesDropBit       = 15 </ins> ) var ( zeroDuration = metav1.Duration{} // Refer to [Node Allocatable](https://git.k8s.io/community/contributors/design-proposals/node/node-allocatable.md) doc for more information. <del> defaultNodeAllocatableEnforcement = []string{\"pods\"} </del> <ins> DefaultNodeAllocatableEnforcement = []string{\"pods\"} </ins> ) func addDefaultingFuncs(scheme *kruntime.Scheme) error {", "positive_passages": [{"docid": "doc-en-kubernetes-937f1cb17c20e5fd2b4a1f81201690c3dbe6990ef3c1bc74ff71daaa02b6db56", "text": "Solution: I will add one.\n/cc\nxref\nThanks for sending a PR so quickly!\n[MILESTONENOTIFIER] Milestone Issue Needs Attention Action required: During code slush, issues in the milestone should be in progress. If this issue is not being actively worked on, please remove it from the milestone. If it is being worked on, please add the label so it can be tracked with other in-flight issues. Note: If this issue is not resolved or labeled as by Wed, Nov 22 it will be moved out of the v1.9 milestone. <details<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details", "commid": "kubernetes_issue_55959", "tokennum": 230}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e4dd9d3b194b2e8294c1d9d5dd47abdad3f5d1701115386dd3b30918bc6c1da1", "query": "ExpectedEtcdPath: \"/registry/configmaps/\" + namespace + \"/cm1\", }, gvr(\"\", \"v1\", \"services\"): { <del> Stub:             `{\"metadata\": {\"name\": \"service1\"}, \"spec\": {\"externalName\": \"service1name\", \"ports\": [{\"port\": 10000, \"targetPort\": 11000}], \"selector\": {\"test\": \"data\"}}}`, </del> <ins> Stub:             `{\"metadata\": {\"name\": \"service1\"}, \"spec\": {\"type\": \"LoadBalancer\", \"ports\": [{\"port\": 10000, \"targetPort\": 11000}], \"selector\": {\"test\": \"data\"}}}`, </ins> ExpectedEtcdPath: \"/registry/services/specs/\" + namespace + \"/service1\", }, gvr(\"\", \"v1\", \"podtemplates\"): {", "positive_passages": [{"docid": "doc-en-kubernetes-e021a9a686a92d83ba285392c70089f3a0813200ee010fb06825ed96dc15cfdb", "text": "xref I think this may be one of the few cases where we can actually change the behavior in a \"breaking\" way. User creates service with , is empty Controller or user updates the status subresource, sets (not wiped or validated, should be) User updates in any way, is wiped It's clear that the is not meant to be set when is not \"LoadBalancer\". The question is: 1) Fail validation? 2) Silently discard the value? 3) Warn and then discard the value? 4) Just warn and leave it. Because we allowed it in the past, but it is so volatile, I lean towards 3. and - the people most familair with this type. Edit: PrepareForUpdate() runs before warnings. So: (1) is easy (2) is easy (4) is slightly less easy than (2) (3) is slightly less easy than (4)\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nOMG change it to clusterIP as expected Status is wiped update status as ClusterIP ... and if I edit the service back to loadbalancer it keeps the status??\n/kind bug\n/retitle Service can be set when !=\nWe talked about this one at the SIG Network meeting today. suggested we use the feature gate for deprecation option to phase the current (problematic) functionality out.\n/triage accept\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /triage accept 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", "commid": "kubernetes_issue_119700", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e4f92dafde6780422859680195d7f48a0a8249b36e2ae1a41c56632c6746f6f8", "query": "defer close(stopCh) manager, informers := testNewReplicaSetControllerFromClient(client, stopCh, BurstReplicas) <del> // A controller with 2 replicas and no pods in the store, 2 creates expected </del> <ins> // A controller with 2 replicas and no active pods in the store. // Inactive pods should be ignored. 2 creates expected. </ins> labelMap := map[string]string{\"foo\": \"bar\"} rs := newReplicaSet(2, labelMap) informers.Extensions().V1beta1().ReplicaSets().Informer().GetIndexer().Add(rs) <ins> failedPod := newPod(\"failed-pod\", rs, v1.PodFailed, nil, true) deletedPod := newPod(\"deleted-pod\", rs, v1.PodRunning, nil, true) deletedPod.DeletionTimestamp = &metav1.Time{Time: time.Now()} informers.Core().V1().Pods().Informer().GetIndexer().Add(failedPod) informers.Core().V1().Pods().Informer().GetIndexer().Add(deletedPod) </ins> fakePodControl := controller.FakePodControl{} manager.podControl = &fakePodControl", "positive_passages": [{"docid": "doc-en-kubernetes-38d52777560a5c6fb71d98b8b0953e61c4be2731ef4a377191b06cc53fcf6655", "text": "https://k8s- Failed: [] Network Partition [Disruptive] [Slow] [] [ReplicationController] should eagerly create replacement pod during network partition when termination grace is non-zero {Kubernetes e2e suite}\nhttps://k8s- seems to be the first failure here. It seems to have gone in with a bunch of RC/RS changes () cc/", "commid": "kubernetes_issue_37479", "tokennum": 88}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e51279fb7b326d790b1115e55a1cb5a30b042a1e5da2f13b45c14bed83c742aa", "query": "// Represents the requirement on the container exit codes. // +optional <del> OnExitCodes *PodFailurePolicyOnExitCodesRequirement `json:\"onExitCodes\" protobuf:\"bytes,2,opt,name=onExitCodes\"` </del> <ins> OnExitCodes *PodFailurePolicyOnExitCodesRequirement `json:\"onExitCodes,omitempty\" protobuf:\"bytes,2,opt,name=onExitCodes\"` </ins> // Represents the requirement on the pod conditions. The requirement is represented // as a list of pod condition patterns. The requirement is satisfied if at // least one pattern matches an actual pod condition. At most 20 elements are allowed. // +listType=atomic // +optional <del> OnPodConditions []PodFailurePolicyOnPodConditionsPattern `json:\"onPodConditions\" protobuf:\"bytes,3,opt,name=onPodConditions\"` </del> <ins> OnPodConditions []PodFailurePolicyOnPodConditionsPattern `json:\"onPodConditions,omitempty\" protobuf:\"bytes,3,opt,name=onPodConditions\"` </ins> } // PodFailurePolicy describes how failed pods influence the backoffLimit.", "positive_passages": [{"docid": "doc-en-kubernetes-f4d4b7c473a266ffc48b535d9080ecbdaed52af3a9bd64395678a7e260a39c7f", "text": "for a PodFailurePolicyRule. However, when trying to create a JobSet programmatically with a JobTemplate that defines a PodFailurePolicy rule for failing a job immediately if the failed pod had condition DisruptionTarget, I get a validation error indicating that cannot be null. I've tried using both and (with matching versions for package as well). Error: JobSet spec: JobTemplate passes validation. JobSet: applying example JobSet in the description of this issue. JobSet: and applying example JobSet in the description of this issue. No response 30 (tests on a kind cluster using kindest/node:v1.30.0) <details</details<details</details<details</details<details</details<details</details\nThere are no sig labels on this issue. Please add an appropriate label by using one of the following commands: - Please see the for a listing of the SIGs, working groups, and committees available. <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\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\ncc\n/assign\nI confirmed the issue, moreover, I see that when the JobSet webhook is disabled then it works ok, I think it must be the JobSet webhook which adds the \"onExitCodes\" field during deserializion /serialization step. I can also see that when I rebuild JobSet using kubernetes field \"onExitCodes\" with \"omitempty\", then it the JobSet creates ok. I will open a PR.", "commid": "kubernetes_issue_126040", "tokennum": 438}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e55536ba0c675c4b6544dca41b2d5c63047f4731d304664766783f3b92cff922", "query": "}) ginkgo.It(\"Kubelet's oom-score-adj should be -999\", func() { kubeletPids, err := getPidsForProcess(kubeletProcessName, \"\") <del> gomega.Expect(err).To(gomega.BeNil(), \"failed to get list of kubelet pids\") </del> <ins> framework.ExpectNoError(err, \"failed to get list of kubelet pids\") </ins> framework.ExpectEqual(len(kubeletPids), 1, \"expected only one kubelet process; found %d\", len(kubeletPids)) gomega.Eventually(func() error { return validateOOMScoreAdjSetting(kubeletPids[0], -999)", "positive_passages": [{"docid": "doc-en-kubernetes-4d7af6d1d5d1ba0c7ab59da9ea13925b54c282d46d48402ebb3f5409fd2b1204", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: kubernetes/node-problem-detector/node-problem-detector-ci: ci-npd-e2e-node See the Which test(s) are failing: [] NodeProblemDetector [NodeFeature:NodeProblemDetector] [] SystemLogMonitor should generate node condition and events for corresponding errors Since when has it been failing: Dec 03. was at 19:50 PST, was at 21:51 PST. Testgrid link: https://k8s- Reason for failure: Apparently is the culprit. Anything else we need to know: This is likely caused by some library upgrade. Nothing big.\n/sig node\n/assign\nSeems like the failure is caused by . /cc /cc /cc /cc\n/priority critical-urgent\nThe particular bug I care about has been fixed in . I'm gonna still work on submitting , as the same error should also be affecting a few other tests.", "commid": "kubernetes_issue_85933", "tokennum": 235}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e5759ab7383f2f594a6312209d6e2e97a9a7cbb599722c575d3386ce53778bad", "query": "} sgList := []string{securityGroupID} <del> for _, extraSG := range strings.Split(annotation, \",\") { </del> <ins> for _, extraSG := range strings.Split(annotations[ServiceAnnotationLoadBalancerExtraSecurityGroups], \",\") { </ins> extraSG = strings.TrimSpace(extraSG) if len(extraSG) > 0 { sgList = append(sgList, extraSG)", "positive_passages": [{"docid": "doc-en-kubernetes-f0769863fab39b633cda95f4d162dbe6bf42638a791c88a2a3acb41bb68633b3", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature /sig aws What happened: In k8s 1.7, when creating a service of type LoadBalancer, K8S creates the ELB and a Security Group for it. For these resources, it adds a tag, constructed dynamically, containing the cluster id: \"${cluster_id}\" with the value \"true\" What you expected to happen: We'd like to have also a statically named tag , as it was in 1.5 (\"KubernetesCluster\") with the value of the cluster id. How to reproduce it (as minimally and precisely as possible): Running on AWS cloud provider, create a service of type LoadBalancer. Anything else we need to know?: The reason for what we expect is that we have tight security constraints that require us to fine tune the IAM policies for the Instance profiles that the controllers use. With a statically named tag we were able, in 1.5, to restrict the permissions in the IAM policy to act only on the k8s managed resources (ELBs, security groups). Here is the relevant part of the IAM policy: With a dynamically named tag we are not able to do this any more as AWS IAM doesn't support something like: We are sharing the Instance Profiles among different k8s clusters, hence the \"\" in the value of the tag. Environment: Kubernetes version (use ):Cloud provider or hardware configuration*: AWS OS (e.g. from /etc/os-release):Kernel (e.g. ):Install tools: kube-aws Others:\nReiterating the mentions to trigger a notification: <detailsIn response to : <!-- This form is for bug reports and feature requests ONLY! -- /sig aws In k8s 1.7, when creating a service of type LoadBalancer, K8S creates the ELB and a Security Group for it. For these resources, it adds a tag, constructed dynamically, containing the cluster id: \"${cluster_id}\" with the value \"true\" We'd like to have also a statically named tag , as it was in 1.5 (\"KubernetesCluster\") with the value of the cluster id. Running on AWS cloud provider, create a service of type LoadBalancer.", "commid": "kubernetes_issue_53489", "tokennum": 543}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e5759ab7383f2f594a6312209d6e2e97a9a7cbb599722c575d3386ce53778bad", "query": "} sgList := []string{securityGroupID} <del> for _, extraSG := range strings.Split(annotation, \",\") { </del> <ins> for _, extraSG := range strings.Split(annotations[ServiceAnnotationLoadBalancerExtraSecurityGroups], \",\") { </ins> extraSG = strings.TrimSpace(extraSG) if len(extraSG) > 0 { sgList = append(sgList, extraSG)", "positive_passages": [{"docid": "doc-en-kubernetes-a01a3c41e631760f28b69af73c7e0688234151a20f7dd4b67642a3c81f6b4dfa", "text": "The reason for what we expect is that we have tight security constraints that require us to fine tune the IAM policies for the Instance profiles that the controllers use. With a statically named tag we were able, in 1.5, to restrict the permissions in the IAM policy to act only on the k8s managed resources (ELBs, security groups). Here is the relevant part of the IAM policy: Environment: Kubernetes version (use ):OS (e.g. from /etc/os-release):Others: </details\nI believe they are moving away from the tag since there are many resources that can be shared by multiple clusters. could you use an annotation?\nWe removed the condition in roles in the end. Thank you for your suggestion.\nThat annotation affects the ELB but not any security groups that are created. can you please reopen this? You reported a real issue, and even if it no longer affects you, it needs to be tracked and fixed.\nIndeed, this might be a feature that someone else would need.\nIn fact, this is a feature I need!\nFood for thought: should we propagate the tags on the ELB to the SG, or should we introduce an annotation for the SG specifically?", "commid": "kubernetes_issue_53489", "tokennum": 265}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e581a061fefe3597069f9ad3759dfeb35280f0c253cebbe979b6544768af2e24", "query": "expectMetrics(t, expectedMetrics{desiredSlices: 1, actualSlices: 1, desiredEndpoints: 10, addedPerSync: 20, removedPerSync: 10, numCreated: 1, numUpdated: 1, numDeleted: 0}) } <ins> // When a Service has a non-nil deletionTimestamp we want to avoid creating any // new EndpointSlices but continue to allow updates and deletes through. This // test uses 3 EndpointSlices, 1 \"to-create\", 1 \"to-update\", and 1 \"to-delete\". // Each test case exercises different combinations of calls to finalize with // those resources. func TestReconcilerFinalizeSvcDeletionTimestamp(t *testing.T) { now := metav1.Now() testCases := []struct { name               string deletionTimestamp  *metav1.Time attemptCreate      bool attemptUpdate      bool attemptDelete      bool expectCreatedSlice bool expectUpdatedSlice bool expectDeletedSlice bool }{{ name:               \"Attempt create and update, nil deletion timestamp\", deletionTimestamp:  nil, attemptCreate:      true, attemptUpdate:      true, expectCreatedSlice: true, expectUpdatedSlice: true, expectDeletedSlice: true, }, { name:               \"Attempt create and update, deletion timestamp set\", deletionTimestamp:  &now, attemptCreate:      true, attemptUpdate:      true, expectCreatedSlice: false, expectUpdatedSlice: true, expectDeletedSlice: true, }, { // Slice scheduled for creation is transitioned to update of Slice // scheduled for deletion. name:               \"Attempt create, update, and delete, nil deletion timestamp, recycling in action\", deletionTimestamp:  nil, attemptCreate:      true, attemptUpdate:      true, attemptDelete:      true, expectCreatedSlice: false, expectUpdatedSlice: true, expectDeletedSlice: true, }, { // Slice scheduled for creation is transitioned to update of Slice // scheduled for deletion. name:               \"Attempt create, update, and delete, deletion timestamp set, recycling in action\", deletionTimestamp:  &now, attemptCreate:      true, attemptUpdate:      true, attemptDelete:      true, expectCreatedSlice: false, expectUpdatedSlice: true, expectDeletedSlice: true, }, { // Update and delete continue to work when deletionTimestamp is set. name:               \"Attempt update delete, deletion timestamp set\", deletionTimestamp:  &now, attemptCreate:      false, attemptUpdate:      true, attemptDelete:      true, expectCreatedSlice: false, expectUpdatedSlice: true, expectDeletedSlice: false, }} for _, tc := range testCases { t.Run(tc.name, func(t *testing.T) { client := newClientset() setupMetrics() r := newReconciler(client, []*corev1.Node{{ObjectMeta: metav1.ObjectMeta{Name: \"node-1\"}}}, defaultMaxEndpointsPerSlice) namespace := \"test\" svc, endpointMeta := newServiceAndEndpointMeta(\"foo\", namespace) svc.DeletionTimestamp = tc.deletionTimestamp esToCreate := &discovery.EndpointSlice{ ObjectMeta:  metav1.ObjectMeta{Name: \"to-create\"}, AddressType: endpointMeta.AddressType, Ports:       endpointMeta.Ports, } // Add EndpointSlice that can be updated. esToUpdate, err := client.DiscoveryV1beta1().EndpointSlices(namespace).Create(context.TODO(), &discovery.EndpointSlice{ ObjectMeta:  metav1.ObjectMeta{Name: \"to-update\"}, AddressType: endpointMeta.AddressType, Ports:       endpointMeta.Ports, }, metav1.CreateOptions{}) if err != nil { t.Fatalf(\"Expected no error creating EndpointSlice during test setup, got %v\", err) } // Add an endpoint so we can see if this has actually been updated by // finalize func. esToUpdate.Endpoints = []discovery.Endpoint{{Addresses: []string{\"10.2.3.4\"}}} // Add EndpointSlice that can be deleted. esToDelete, err := client.DiscoveryV1beta1().EndpointSlices(namespace).Create(context.TODO(), &discovery.EndpointSlice{ ObjectMeta:  metav1.ObjectMeta{Name: \"to-delete\"}, AddressType: endpointMeta.AddressType, Ports:       endpointMeta.Ports, }, metav1.CreateOptions{}) if err != nil { t.Fatalf(\"Expected no error creating EndpointSlice during test setup, got %v\", err) } slicesToCreate := []*discovery.EndpointSlice{} if tc.attemptCreate { slicesToCreate = append(slicesToCreate, esToCreate.DeepCopy()) } slicesToUpdate := []*discovery.EndpointSlice{} if tc.attemptUpdate { slicesToUpdate = append(slicesToUpdate, esToUpdate.DeepCopy()) } slicesToDelete := []*discovery.EndpointSlice{} if tc.attemptDelete { slicesToDelete = append(slicesToDelete, esToDelete.DeepCopy()) } err = r.finalize(&svc, slicesToCreate, slicesToUpdate, slicesToDelete, time.Now()) if err != nil { t.Errorf(\"Error calling r.finalize(): %v\", err) } fetchedSlices := fetchEndpointSlices(t, client, namespace) createdSliceFound := false updatedSliceFound := false deletedSliceFound := false for _, epSlice := range fetchedSlices { if epSlice.Name == esToCreate.Name { createdSliceFound = true } if epSlice.Name == esToUpdate.Name { updatedSliceFound = true if tc.attemptUpdate && len(epSlice.Endpoints) != len(esToUpdate.Endpoints) { t.Errorf(\"Expected EndpointSlice to be updated with %d endpoints, got %d endpoints\", len(esToUpdate.Endpoints), len(epSlice.Endpoints)) } } if epSlice.Name == esToDelete.Name { deletedSliceFound = true } } if createdSliceFound != tc.expectCreatedSlice { t.Errorf(\"Expected created EndpointSlice existence to be %t, got %t\", tc.expectCreatedSlice, createdSliceFound) } if updatedSliceFound != tc.expectUpdatedSlice { t.Errorf(\"Expected updated EndpointSlice existence to be %t, got %t\", tc.expectUpdatedSlice, updatedSliceFound) } if deletedSliceFound != tc.expectDeletedSlice { t.Errorf(\"Expected deleted EndpointSlice existence to be %t, got %t\", tc.expectDeletedSlice, deletedSliceFound) } }) } } </ins> // Test Helpers func newReconciler(client *fake.Clientset, nodes []*corev1.Node, maxEndpointsPerSlice int32) *reconciler {", "positive_passages": [{"docid": "doc-en-kubernetes-b47abd0a7beb2bc1a841f65e5737673c1fa7ed1c22ab52e8ed01b146c2722dfe", "text": "What happened: In the PMEM-CSI CI, we rapidly deploy and remove a custom resources which then owns all objects created for that resource. Deletion of those objects is handled through ownership references, i.e. deleting the CR is expected to cascade to all objects. This worked fine up to Kubernetes 1.17. When starting to test with 1.18.2, we pretty reliably get into a state where the CR and the service objects owned by it are marked for deletion, but don't go away. Debugging with the garbage collector's dependency graph (see ) showed that endpointslices were blocking the deletion of the services and thus the CR. In the graph dump (= a snaphot in time), they were not even marked for deletion. A closer look showed that endpointslices for the services were getting created and deleted continuously for over 15 minutes. Eventually, the garbage collector won and managed to delete endpointslices and services before new endpointslices were created. What you expected to happen: There seems to be a missing check in if the service is marked for deletion (i.e. has a deletionTimestamp), then the controller should not create new endpointslices. How to reproduce it (as minimally and precisely as possible): I tried to boil it down to a script, but it just ran fine. The \"easiest\" way to reproduce it is to run PMEM-CSI's E2E testing, which is probably not easy enough :disappointed: Anything else we need to know?: Disabling the EndpointSlice feature makes the problem go away. Environment: Kubernetes version (use ): 1.18.2 Cloud provider or hardware configuration: QEMU virtual machines OS (e.g: ): Fedora Install tools: kubeadm /sig network\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\ncc for endpointslice\nThanks for the detailed bug report! Will work on getting a fix in soon. /assign\n/remove-triage unresolved\nCan you describe the general process to reproduce this bug? Would it involve hundreds of EndpointSlices for a Service? I've tried to recreate this in a , but unfortunately I haven't been able to get anything to break. Any ideas for what I could try?\nThere's one endpointslice per service. Our operator creates two services.", "commid": "kubernetes_issue_91287", "tokennum": 525}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e581a061fefe3597069f9ad3759dfeb35280f0c253cebbe979b6544768af2e24", "query": "expectMetrics(t, expectedMetrics{desiredSlices: 1, actualSlices: 1, desiredEndpoints: 10, addedPerSync: 20, removedPerSync: 10, numCreated: 1, numUpdated: 1, numDeleted: 0}) } <ins> // When a Service has a non-nil deletionTimestamp we want to avoid creating any // new EndpointSlices but continue to allow updates and deletes through. This // test uses 3 EndpointSlices, 1 \"to-create\", 1 \"to-update\", and 1 \"to-delete\". // Each test case exercises different combinations of calls to finalize with // those resources. func TestReconcilerFinalizeSvcDeletionTimestamp(t *testing.T) { now := metav1.Now() testCases := []struct { name               string deletionTimestamp  *metav1.Time attemptCreate      bool attemptUpdate      bool attemptDelete      bool expectCreatedSlice bool expectUpdatedSlice bool expectDeletedSlice bool }{{ name:               \"Attempt create and update, nil deletion timestamp\", deletionTimestamp:  nil, attemptCreate:      true, attemptUpdate:      true, expectCreatedSlice: true, expectUpdatedSlice: true, expectDeletedSlice: true, }, { name:               \"Attempt create and update, deletion timestamp set\", deletionTimestamp:  &now, attemptCreate:      true, attemptUpdate:      true, expectCreatedSlice: false, expectUpdatedSlice: true, expectDeletedSlice: true, }, { // Slice scheduled for creation is transitioned to update of Slice // scheduled for deletion. name:               \"Attempt create, update, and delete, nil deletion timestamp, recycling in action\", deletionTimestamp:  nil, attemptCreate:      true, attemptUpdate:      true, attemptDelete:      true, expectCreatedSlice: false, expectUpdatedSlice: true, expectDeletedSlice: true, }, { // Slice scheduled for creation is transitioned to update of Slice // scheduled for deletion. name:               \"Attempt create, update, and delete, deletion timestamp set, recycling in action\", deletionTimestamp:  &now, attemptCreate:      true, attemptUpdate:      true, attemptDelete:      true, expectCreatedSlice: false, expectUpdatedSlice: true, expectDeletedSlice: true, }, { // Update and delete continue to work when deletionTimestamp is set. name:               \"Attempt update delete, deletion timestamp set\", deletionTimestamp:  &now, attemptCreate:      false, attemptUpdate:      true, attemptDelete:      true, expectCreatedSlice: false, expectUpdatedSlice: true, expectDeletedSlice: false, }} for _, tc := range testCases { t.Run(tc.name, func(t *testing.T) { client := newClientset() setupMetrics() r := newReconciler(client, []*corev1.Node{{ObjectMeta: metav1.ObjectMeta{Name: \"node-1\"}}}, defaultMaxEndpointsPerSlice) namespace := \"test\" svc, endpointMeta := newServiceAndEndpointMeta(\"foo\", namespace) svc.DeletionTimestamp = tc.deletionTimestamp esToCreate := &discovery.EndpointSlice{ ObjectMeta:  metav1.ObjectMeta{Name: \"to-create\"}, AddressType: endpointMeta.AddressType, Ports:       endpointMeta.Ports, } // Add EndpointSlice that can be updated. esToUpdate, err := client.DiscoveryV1beta1().EndpointSlices(namespace).Create(context.TODO(), &discovery.EndpointSlice{ ObjectMeta:  metav1.ObjectMeta{Name: \"to-update\"}, AddressType: endpointMeta.AddressType, Ports:       endpointMeta.Ports, }, metav1.CreateOptions{}) if err != nil { t.Fatalf(\"Expected no error creating EndpointSlice during test setup, got %v\", err) } // Add an endpoint so we can see if this has actually been updated by // finalize func. esToUpdate.Endpoints = []discovery.Endpoint{{Addresses: []string{\"10.2.3.4\"}}} // Add EndpointSlice that can be deleted. esToDelete, err := client.DiscoveryV1beta1().EndpointSlices(namespace).Create(context.TODO(), &discovery.EndpointSlice{ ObjectMeta:  metav1.ObjectMeta{Name: \"to-delete\"}, AddressType: endpointMeta.AddressType, Ports:       endpointMeta.Ports, }, metav1.CreateOptions{}) if err != nil { t.Fatalf(\"Expected no error creating EndpointSlice during test setup, got %v\", err) } slicesToCreate := []*discovery.EndpointSlice{} if tc.attemptCreate { slicesToCreate = append(slicesToCreate, esToCreate.DeepCopy()) } slicesToUpdate := []*discovery.EndpointSlice{} if tc.attemptUpdate { slicesToUpdate = append(slicesToUpdate, esToUpdate.DeepCopy()) } slicesToDelete := []*discovery.EndpointSlice{} if tc.attemptDelete { slicesToDelete = append(slicesToDelete, esToDelete.DeepCopy()) } err = r.finalize(&svc, slicesToCreate, slicesToUpdate, slicesToDelete, time.Now()) if err != nil { t.Errorf(\"Error calling r.finalize(): %v\", err) } fetchedSlices := fetchEndpointSlices(t, client, namespace) createdSliceFound := false updatedSliceFound := false deletedSliceFound := false for _, epSlice := range fetchedSlices { if epSlice.Name == esToCreate.Name { createdSliceFound = true } if epSlice.Name == esToUpdate.Name { updatedSliceFound = true if tc.attemptUpdate && len(epSlice.Endpoints) != len(esToUpdate.Endpoints) { t.Errorf(\"Expected EndpointSlice to be updated with %d endpoints, got %d endpoints\", len(esToUpdate.Endpoints), len(epSlice.Endpoints)) } } if epSlice.Name == esToDelete.Name { deletedSliceFound = true } } if createdSliceFound != tc.expectCreatedSlice { t.Errorf(\"Expected created EndpointSlice existence to be %t, got %t\", tc.expectCreatedSlice, createdSliceFound) } if updatedSliceFound != tc.expectUpdatedSlice { t.Errorf(\"Expected updated EndpointSlice existence to be %t, got %t\", tc.expectUpdatedSlice, updatedSliceFound) } if deletedSliceFound != tc.expectDeletedSlice { t.Errorf(\"Expected deleted EndpointSlice existence to be %t, got %t\", tc.expectDeletedSlice, deletedSliceFound) } }) } } </ins> // Test Helpers func newReconciler(client *fake.Clientset, nodes []*corev1.Node, maxEndpointsPerSlice int32) *reconciler {", "positive_passages": [{"docid": "doc-en-kubernetes-884db7f4f09e6e30f5114a0e6bbb9ebc21f2d686aa6c190d6a4d9470af013127", "text": "One peculiarity may be that we don't actually want the pods to start during these tests because we only want to verify object creation, not the usage of the result, and therefore all pods reference non-existent images. All objects immediately get deleted once the test has verified that they exist, so the timing is probably very different from \"normal\" usage patterns. I suspect that it is more important to create and delete services quickly than it is to have many endpointslices per service.\nI had tried to come up with a script that triggers the problem, without success. That was before I realized that endpointslices are involved. On Monday I can have another look.\nThat was because I thought that (the default) enables foreground deletion. It doesn't, and there's also no option to select it. After explicitly selecting it via curl, the following script failed for me eventually: Output: Note that for the endpointslice is greater than the of its service.", "commid": "kubernetes_issue_91287", "tokennum": 201}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e5d47aeac2556ece20ef3c81bc7962f620d571a0028c9789313dce7c055789cb", "query": "\"//staging/src/k8s.io/apimachinery/pkg/fields:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/labels:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/runtime:go_default_library\", <ins> \"//staging/src/k8s.io/apimachinery/pkg/runtime/schema:go_default_library\", </ins> \"//staging/src/k8s.io/apimachinery/pkg/types:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/util/diff:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/util/intstr:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-a4e08d4660e59e77b869eee3e8c161e5e01175b90d68e1077fd3e84d4f4d567b", "text": "[x] Original approval issue: - Reverted due to flakes [x] Two weeks soak end date: 20 November 2020 This issue is created to allow edit by /wip /hold According to this APIsnoop query, there are still some remaining Pod endpoints which are untested. a Pod with a static label the Pod with a new Label and updated data the Pod to ensure it's patched the Pod's status the Pod's status Ready condition to False the Pod's status to check if Ready is False all Pods in all Namespaces find the Pod(1) ensure that the Pod is found and is patched Namespaced Pod(1) via a Collection with a LabelSelector the Pod to check that it's deleted Discover useragents: List endpoints hit by the test: Display endpoint coverage change: If a test with these calls gets merged, test coverage will go up by 4 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance\n/reopen Test PR Merge Promotion PR to be created next\nReopened this issue. <detailsIn response to : /reopen Test PR Merge Promotion PR to be created next 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\nreverted by due to flaky test\nIssues 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\n/remove-lifecycle stale\n/reopen PR on test grid for 2 weeks before promotion to conformance\nReopened this issue. <detailsIn response to : /reopen PR on test grid for 2 weeks before promotion to conformance 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\n/triage accepted", "commid": "kubernetes_issue_90936", "tokennum": 449}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e604e12c56b573bcce06c1d802fb7237a747e6d539181d7f187dfaffe69f3b67", "query": "<del> apiVersion: v1 kind: ReplicationController metadata: name: es labels: component: elasticsearch spec: replicas: 1 template: metadata: labels: component: elasticsearch spec: serviceAccount: elasticsearch containers: - name: es securityContext: capabilities: add: - IPC_LOCK image: quay.io/pires/docker-elasticsearch-kubernetes:1.7.1-4 env: - name: KUBERNETES_CA_CERTIFICATE_FILE value: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt - name: NAMESPACE valueFrom: fieldRef: fieldPath: metadata.namespace - name: \"CLUSTER_NAME\" value: \"myesdb\" - name: \"DISCOVERY_SERVICE\" value: \"elasticsearch\" - name: NODE_MASTER value: \"true\" - name: NODE_DATA value: \"true\" - name: HTTP_ENABLE value: \"true\" ports: - containerPort: 9200 name: http protocol: TCP - containerPort: 9300 name: transport protocol: TCP volumeMounts: - mountPath: /data name: storage volumes: - name: storage emptyDir: {} </del>", "positive_passages": [{"docid": "doc-en-kubernetes-5fef938b0452d0f6b58e576cd11f17813fb6d6b970f83a7868d905b7784a5e39", "text": "Presently, the elasticsearch example Kubernetes configurations target elasticsearch v1.7.1, which is quite old. As of this writing, the latest elasticsearch release is v5.6.2, with many deployment changes since then. Could the elasticsearch examples be updated to target the v5 series of elasticsearch? See for a more up to date reference configuration.\ncc\nhey it's been a long while since I last contributed to the docs. i can do it soon but i need pointers on how to properly do it.\nhey, so we need to update the stuff under examples/elasticsearch/ *&repos=kubernetes So basically update the images, yaml files etc and test that everything works (and submit a PR)\n/sig testing\nAh, so there's no documentation updates anymore. OK I'll take care of it, assign it to me.\nIssues 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\nGitHub didn't allow me to assign the following users: me. Note that only and repo collaborators can be assigned. <detailsIn response to : /assign me 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\n/assign pires\n/remove-lifecycle stale\nit seems that the example moved to I am now reading that repo guidelines and will update this there. I'll also open a PR that cleans this folder in the current repo and closes this issue.", "commid": "kubernetes_issue_53142", "tokennum": 387}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e61c0699309787d0c7633477399359b562e72a5f6b8c6f4dd8047cb5b236f3f4", "query": "import ( \"context\" <ins> \"encoding/json\" </ins> \"fmt\" \"math/rand\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-cea21dfbf74ea26aea8b8fcc0c8d9d3e2b3e4488cd9f6d30773b87652fe6e220", "text": "[x] Original approval issue: [x] Test pr: [x] Two weeks soak end date: 19 November 2020 This issue is created to allow edit by /wip /hold According to this APIsnoop query, there are still some remaining Deployment endpoints which are untested. a Deployment with a static label the Deployment with a new Label and updated data the Deployment to ensure it's patched all Deployments in all Namespaces find the Deployment(1) ensure that the Deployment is found and is patched Namespaced Deployment(1) via a Collection with a LabelSelector Discover useragents: List endpoints hit by the test: Display endpoint coverage change: If a test with these calls gets merged, test coverage will go up by 5 points* This test is also created with the goal of conformance promotion.\n/sig testing /sig architecture /area conformance\nBobyMcbobs commented in original Issue: Unsure if the endpoint replaceAppsV1NamespacedDeploymentStatus is able to be hit. When this endpoint is attempted to be updated the data after retrieving the update resource doesn't reflect the values in the update\n/assign\nWhen using the appv1.Deployment structure instead of maps of interfaces to build the structure in a patch of the Deployment, this error comes up. Still in progress yment-static\":\"true\"}: does not match template , spec.selector: Invalid value: \"null\": field is immutable]\nreplaceAppsV1NamespacedDeploymentStatus to test. Increase cover by 1 Endpoint\n/reopen PR reverted by due to flaky test\nReopened this issue. <detailsIn response to : /reopen PR reverted by due to flaky test 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\nIssues 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\n/reopen Soaking, ready for promotion 19 November 2020\nReopened this issue. <detailsIn response to : /reopen Soaking, ready for promotion 19 November 2020 Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_90916", "tokennum": 522}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e61c0699309787d0c7633477399359b562e72a5f6b8c6f4dd8047cb5b236f3f4", "query": "import ( \"context\" <ins> \"encoding/json\" </ins> \"fmt\" \"math/rand\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-ff9ccf83336a9bf28b0576a991dfda56392cc48f280c272644ff154877b8104d", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/remove-lifecycle stale\n/triage accepted\n/merged", "commid": "kubernetes_issue_90916", "tokennum": 34}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e625a07848ef1959d299676d424f6f14adeca744fd2bcd42cfb66c0ac32cfd93", "query": "WithStdinData(\"abcd1234n\"). ExecOrDie() gomega.Expect(runOutput).ToNot(gomega.ContainSubstring(\"stdin closed\")) <del> g = func(pods []*v1.Pod) sort.Interface { return sort.Reverse(controller.ActivePods(pods)) } runTestPod, _, err = polymorphichelpers.GetFirstPod(f.ClientSet.CoreV1(), ns, \"run=run-test-3\", 1*time.Minute, g) </del> <ins> g := func(pods []*v1.Pod) sort.Interface { return sort.Reverse(controller.ActivePods(pods)) } runTestPod, _, err := polymorphichelpers.GetFirstPod(f.ClientSet.CoreV1(), ns, \"run=run-test-3\", 1*time.Minute, g) </ins> gomega.Expect(err).To(gomega.BeNil()) if !e2epod.CheckPodsRunningReady(c, ns, []string{runTestPod.Name}, time.Minute) { e2elog.Failf(\"Pod %q of Job %q should still be running\", runTestPod.Name, \"run-test-3\")", "positive_passages": [{"docid": "doc-en-kubernetes-7b2399b1ff0857c826d80a73801e04bffa6df7e676dd58a7e2d56a664bd364fc", "text": "The test case \"executing a command with run and attach without stdin\" is inherently racy. The test runs, and expected to see in the output. The case when the test passes: case 1: Kubernetes creates and starts the container without stdin; The container exits before attach runs; kubectl falls back to get container log, which contains . case 2: Kubernetes creates and starts the container without stdin; kubectl attach before \"stdin closed\" is printed; kubectl attach contains . The case when the test fails: Kubernetes creates and starts the container without stdin; The container prints \"stdin closed\", but hasn't exited yet; kubectl attach contains nothing. One example failure: Related issue: Can we modify this test not to check the output? Or use to check output instead? /cc\nUploaded to try to address\n/reopen This test is still inherently racy, even after\nFix in (I hope!)\nMoving into the current milestone as it was not fixed in 1.14\nHello I'm a bug triage shadow for the 1.16 release cycle and considering this issue is tagged for 1.16, I'd like to check its status. Code freeze is starting on August 29th (about 3 days from now). Do we still target this issue to be fixed for 1.16?\nThanks . PR is available and awaiting review!\nWhat is the PR in question? Is it targeting 1.16 or 1.17?\n/reopen This test is having a lot of failures these days\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nis right, it seems to be present in kind jobs now only\n/assign let's see if we start to recover a bit of stability :smile:\nThe rate of failures decreased a lot since last changes Checking the logs of the failures it seems that the problem is that the pod has not finished before checking the output, as Lantao described The test fails Collecting events from namespace The framework logs the pods the kubelet thinks is on the node\nnote that it's still racy, but it's hopefully somewhat mitigated.\n/reopen\nReopened this issue.", "commid": "kubernetes_issue_73099", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e625a07848ef1959d299676d424f6f14adeca744fd2bcd42cfb66c0ac32cfd93", "query": "WithStdinData(\"abcd1234n\"). ExecOrDie() gomega.Expect(runOutput).ToNot(gomega.ContainSubstring(\"stdin closed\")) <del> g = func(pods []*v1.Pod) sort.Interface { return sort.Reverse(controller.ActivePods(pods)) } runTestPod, _, err = polymorphichelpers.GetFirstPod(f.ClientSet.CoreV1(), ns, \"run=run-test-3\", 1*time.Minute, g) </del> <ins> g := func(pods []*v1.Pod) sort.Interface { return sort.Reverse(controller.ActivePods(pods)) } runTestPod, _, err := polymorphichelpers.GetFirstPod(f.ClientSet.CoreV1(), ns, \"run=run-test-3\", 1*time.Minute, g) </ins> gomega.Expect(err).To(gomega.BeNil()) if !e2epod.CheckPodsRunningReady(c, ns, []string{runTestPod.Name}, time.Minute) { e2elog.Failf(\"Pod %q of Job %q should still be running\", runTestPod.Name, \"run-test-3\")", "positive_passages": [{"docid": "doc-en-kubernetes-6fb855e6221755f4f8c679054412ceafcb7919572a50b214c71af07d9654c4d2", "text": "<detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nany updates here?\nnope, totally agree with the description, is racy by design, couldn't find any way or trick to avoid the randomness\nEDIT: It's late and I'm actually not sure I'm remembering this correctly, take this comment with a heap of salt: Specific sub-tests were fixed previously I think, but this one sub-case: That one we can't use the \"Wait for stdin input to signal we're attached\" hack, so it's just racy and broken. We could remove that case maybe. I'm not sure who I'd want to weigh in on that, probably someone more active in node / CLI.\nnot super common atm but still happening. discussing\n/unassign has a fix for this", "commid": "kubernetes_issue_73099", "tokennum": 203}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e63c9e24c19eae351637a7d83653de2da58debbc75e3f0a0f81c57bd2637c5d8", "query": "valueFrom: fieldRef: fieldPath: metadata.name <del> command: - /bin/sh - -c - /kubemark --morph=kubelet --name=$(NODE_NAME) {{hollow_kubelet_params}} --kubeconfig=/kubeconfig/kubelet.kubeconfig $(CONTENT_TYPE) --alsologtostderr 1>>/var/log/kubelet-$(NODE_NAME).log 2>&1 </del> <ins> command: [ \"/kubemark\", \"--morph=kubelet\", \"--name=$(NODE_NAME)\", \"--kubeconfig=/kubeconfig/kubelet.kubeconfig\", \"$(CONTENT_TYPE)\", \"--log-file=/var/log/kubelet-$(NODE_NAME).log\", \"--logtostderr=false\", {{hollow_kubelet_params}} ] </ins> volumeMounts: - name: kubeconfig-volume mountPath: /kubeconfig", "positive_passages": [{"docid": "doc-en-kubernetes-d99484417892d904a3f5edbb73fa06d2de654c460b279ad73f511e028afa6a6f", "text": "There are CVEs happening in different images - we already migrated Kubmeark from busybox in , but we should go one step further and migrate the base image to distroless. There are some things that would need to be changed mentioned here: /sig scalability\nCan I work on this? /assign\n/remove-help\n- sure that would be great.\nHi based on the discussion in , the kubemark image has dependency on and maybe more other utilities. So it seems impossible to migrate the base image to distroless? Or do we need something like debian-hyperkube-base?\nThe mount one we may get rid of - basically we should be able to switch to FakeMounter:", "commid": "kubernetes_issue_84284", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e64aafa9530bcbebf253fdca60651fed7042aa505efb069a9929e8853bff477b", "query": "\"//vendor/github.com/onsi/gomega:go_default_library\", \"//vendor/k8s.io/api/core/v1:go_default_library\", \"//vendor/k8s.io/api/settings/v1alpha1:go_default_library\", <ins> \"//vendor/k8s.io/apimachinery/pkg/api/errors:go_default_library\", </ins> \"//vendor/k8s.io/apimachinery/pkg/apis/meta/v1:go_default_library\", \"//vendor/k8s.io/apimachinery/pkg/labels:go_default_library\", \"//vendor/k8s.io/apimachinery/pkg/watch:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-fe3f123845ebc52583ef0b18b019ca5c9cf0487720bfc7eeadb38f7ce5aa77c7", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: is consistently failing because of PodPreset feature tests, which require settings/v1alpha1, which is no longer enabled by default What you expected to happen: . How to reproduce it (as minimally and precisely as possible): . Anything else we need to know?: This was caused by and kubernetes/test-infra Environment: . Kubernetes version (use ): . Cloud provider or hardware configuration**: . OS (e.g. from /etc/os-release): . Kernel (e.g. ): . Install tools: . Others: .\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig service-catalog\ndoes the alpha CI job enable alpha API versions?\nfile has \"AllAlpha=true\" Maybe would be better?", "commid": "kubernetes_issue_53079", "tokennum": 293}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e6520d4ad620e21114badad9e7f42193df1b01a97ba863d91831e30d754c667d", "query": "} // apply volume ownership <del> if !c.readOnly && fsGroup != nil { err := volume.SetVolumeOwnership(c, fsGroup) if err != nil { // attempt to rollback mount. glog.Error(log(\"mounter.SetupAt failed to set fsgroup volume ownership for [%s]: %v\", c.volumeID, err)) glog.V(4).Info(log(\"mounter.SetupAt attempting to unpublish volume %s due to previous error\", c.volumeID)) if unpubErr := csi.NodeUnpublishVolume(ctx, c.volumeID, dir); unpubErr != nil { glog.Error(log( \"mounter.SetupAt failed to unpublish volume [%s]: %v (caused by previous NodePublish error: %v)\", c.volumeID, unpubErr, err, )) return fmt.Errorf(\"%v (caused by %v)\", unpubErr, err) } </del> <ins> // The following logic is derived from https://github.com/kubernetes/kubernetes/issues/66323 // if fstype is \"\", then skip fsgroup (could be indication of non-block filesystem) // if fstype is provided and pv.AccessMode == ReadWriteOnly, then apply fsgroup </ins> <del> if unmountErr := removeMountDir(c.plugin, dir); unmountErr != nil { glog.Error(log( \"mounter.SetupAt failed to clean mount dir [%s]: %v (caused by previous NodePublish error: %v)\", dir, unmountErr, err, )) return fmt.Errorf(\"%v (caused by %v)\", unmountErr, err) } </del> <ins> err = c.applyFSGroup(fsType, fsGroup) if err != nil { // attempt to rollback mount. fsGrpErr := fmt.Errorf(\"applyFSGroup failed for vol %s: %v\", c.volumeID, err) if unpubErr := csi.NodeUnpublishVolume(ctx, c.volumeID, dir); unpubErr != nil { glog.Error(log(\"NodeUnpublishVolume failed for [%s]: %v\", c.volumeID, unpubErr)) return fsGrpErr } </ins> <del> return err </del> <ins> if unmountErr := removeMountDir(c.plugin, dir); unmountErr != nil { glog.Error(log(\"removeMountDir failed for [%s]: %v\", dir, unmountErr)) return fsGrpErr </ins> } <del> glog.V(4).Info(log(\"mounter.SetupAt sets fsGroup to [%d] for %s\", *fsGroup, c.volumeID)) </del> <ins> return fsGrpErr </ins> } glog.V(4).Infof(log(\"mounter.SetUp successfully requested NodePublish [%s]\", dir))", "positive_passages": [{"docid": "doc-en-kubernetes-91422af253157e56510335693740251e17b7c26d119e77363e85ed4155980546", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: What happened: fsgroup is only intended for RWO volumes because it recursively changes the permissions of all the directories in the volume. This can cause problems for nfs-type volumes because multiple pods could access the same volume and have the permissions changed out from underneath. What you expected to happen: Determine whether or not the plugin supports fsgroup either via: access mode. This is still a bit ambiguous for nfs volume types, that can theoretically support rwo, especially since Kubernetes does not do any sort of access mode enforcement. a new csi capability\nCC\nAre you saying that CSI internal driver should check driver capability for RWO, if supported, only then apply value ? What would the be ?\nYes one possible way is to infer fsgroup is supported for all rwo volumes, which may not be true? Like a nfs volume technically supports rwo but not fsgroup. So the other option is to make it a new CSI capability. I'm not sure exactly sure how best to describe it though, maybe something about volume ownership management.\nWill it work if is not set then don't chown the ownership? I would think that for shared file system types(nfs, glusterfs) - won't be set. For raw block storage too - I think we shouldn't have to do this.\nwhat do you mean by ? Shouldnt have to solve this issue ?\nI meant - which is obvious. I just meant that the entire mechanism of changing ownership of files should apply only to volume types with block storage filesystems. I am just wondering if we can get away with detecting fsType and not have to introduce new capability in CSI.\nagreed, do not map well to current csi.Capabilities enums which makes it hard to determine RWO when mounting. Perhaps, instead of a new capability, we revisit the existing capabilities to see if there are any way RWO can be reliably inferred from returned capabilities.", "commid": "kubernetes_issue_66323", "tokennum": 463}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e6520d4ad620e21114badad9e7f42193df1b01a97ba863d91831e30d754c667d", "query": "} // apply volume ownership <del> if !c.readOnly && fsGroup != nil { err := volume.SetVolumeOwnership(c, fsGroup) if err != nil { // attempt to rollback mount. glog.Error(log(\"mounter.SetupAt failed to set fsgroup volume ownership for [%s]: %v\", c.volumeID, err)) glog.V(4).Info(log(\"mounter.SetupAt attempting to unpublish volume %s due to previous error\", c.volumeID)) if unpubErr := csi.NodeUnpublishVolume(ctx, c.volumeID, dir); unpubErr != nil { glog.Error(log( \"mounter.SetupAt failed to unpublish volume [%s]: %v (caused by previous NodePublish error: %v)\", c.volumeID, unpubErr, err, )) return fmt.Errorf(\"%v (caused by %v)\", unpubErr, err) } </del> <ins> // The following logic is derived from https://github.com/kubernetes/kubernetes/issues/66323 // if fstype is \"\", then skip fsgroup (could be indication of non-block filesystem) // if fstype is provided and pv.AccessMode == ReadWriteOnly, then apply fsgroup </ins> <del> if unmountErr := removeMountDir(c.plugin, dir); unmountErr != nil { glog.Error(log( \"mounter.SetupAt failed to clean mount dir [%s]: %v (caused by previous NodePublish error: %v)\", dir, unmountErr, err, )) return fmt.Errorf(\"%v (caused by %v)\", unmountErr, err) } </del> <ins> err = c.applyFSGroup(fsType, fsGroup) if err != nil { // attempt to rollback mount. fsGrpErr := fmt.Errorf(\"applyFSGroup failed for vol %s: %v\", c.volumeID, err) if unpubErr := csi.NodeUnpublishVolume(ctx, c.volumeID, dir); unpubErr != nil { glog.Error(log(\"NodeUnpublishVolume failed for [%s]: %v\", c.volumeID, unpubErr)) return fsGrpErr } </ins> <del> return err </del> <ins> if unmountErr := removeMountDir(c.plugin, dir); unmountErr != nil { glog.Error(log(\"removeMountDir failed for [%s]: %v\", dir, unmountErr)) return fsGrpErr </ins> } <del> glog.V(4).Info(log(\"mounter.SetupAt sets fsGroup to [%d] for %s\", *fsGroup, c.volumeID)) </del> <ins> return fsGrpErr </ins> } glog.V(4).Infof(log(\"mounter.SetUp successfully requested NodePublish [%s]\", dir))", "positive_passages": [{"docid": "doc-en-kubernetes-e4259f265013a5d1d3262148ae5650fa802161db5ab8c8ccc1d210e68217a7fd", "text": "Currently, this is what the code is doing which we knew needed to be revisited:\nUsers may not fully understand what fsgroup is and set it anyway, or a default psp with some fsgroup may be defined in which it will automatically be set on all pods. The first case we can attribute to user error, but the second case may not have a good workaround and could cause permission issues on rwx volumes. So I think we do need to solve this.\nYes, agreed this has to be solved. As you pointed out user error or improperly configured PSP can set value that does not match the correct attribute, causing permission issues. Here is what I think can be done without new CSI capabilities: , then do not apply fsgroup then: , apply fsgroup , do not apply fsgroup to void stated issue then: , apply fsgroup I think that may help deduce when to apply fsgroup.\nIf mount reference count <= 1, apply fsgroup If mount reference count 1, do not apply fsgroup to void stated issue A RWM volume (say NFS) can be mounted on multiple nodes. Do you have reliable count of mounts across all nodes?\nIn addition, that would be a change in semantics to how we support rwx volumes today. If we don't have a new CSI capability, then I think the best course of action is to only apply fsgroup for RWO volumes. Some questions remain: Do all RWO volumes support fsgroup? RWX is a superset of RWO. So if a user requests a RWO volume, it could still be satisfied by a RWX volume type. Can we detect this and still not apply the fsgroup even though the volume capability will say RWO?\nIf there's not a reliable way to enumerate node mounts (thinking about it, for CSI external drivers, the answer is NO). Theres is no reliable way to have k8s autocorrect a bad fsgroup/PV.AccessMode combo. So we would have to rely on the config provided by user/admin. I have come to similar conclusion as -- mainly, apply fsgroup only to volumes with access modes. The other k8s specified access modes, , cannot be reliably applied.", "commid": "kubernetes_issue_66323", "tokennum": 487}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e6520d4ad620e21114badad9e7f42193df1b01a97ba863d91831e30d754c667d", "query": "} // apply volume ownership <del> if !c.readOnly && fsGroup != nil { err := volume.SetVolumeOwnership(c, fsGroup) if err != nil { // attempt to rollback mount. glog.Error(log(\"mounter.SetupAt failed to set fsgroup volume ownership for [%s]: %v\", c.volumeID, err)) glog.V(4).Info(log(\"mounter.SetupAt attempting to unpublish volume %s due to previous error\", c.volumeID)) if unpubErr := csi.NodeUnpublishVolume(ctx, c.volumeID, dir); unpubErr != nil { glog.Error(log( \"mounter.SetupAt failed to unpublish volume [%s]: %v (caused by previous NodePublish error: %v)\", c.volumeID, unpubErr, err, )) return fmt.Errorf(\"%v (caused by %v)\", unpubErr, err) } </del> <ins> // The following logic is derived from https://github.com/kubernetes/kubernetes/issues/66323 // if fstype is \"\", then skip fsgroup (could be indication of non-block filesystem) // if fstype is provided and pv.AccessMode == ReadWriteOnly, then apply fsgroup </ins> <del> if unmountErr := removeMountDir(c.plugin, dir); unmountErr != nil { glog.Error(log( \"mounter.SetupAt failed to clean mount dir [%s]: %v (caused by previous NodePublish error: %v)\", dir, unmountErr, err, )) return fmt.Errorf(\"%v (caused by %v)\", unmountErr, err) } </del> <ins> err = c.applyFSGroup(fsType, fsGroup) if err != nil { // attempt to rollback mount. fsGrpErr := fmt.Errorf(\"applyFSGroup failed for vol %s: %v\", c.volumeID, err) if unpubErr := csi.NodeUnpublishVolume(ctx, c.volumeID, dir); unpubErr != nil { glog.Error(log(\"NodeUnpublishVolume failed for [%s]: %v\", c.volumeID, unpubErr)) return fsGrpErr } </ins> <del> return err </del> <ins> if unmountErr := removeMountDir(c.plugin, dir); unmountErr != nil { glog.Error(log(\"removeMountDir failed for [%s]: %v\", dir, unmountErr)) return fsGrpErr </ins> } <del> glog.V(4).Info(log(\"mounter.SetupAt sets fsGroup to [%d] for %s\", *fsGroup, c.volumeID)) </del> <ins> return fsGrpErr </ins> } glog.V(4).Infof(log(\"mounter.SetUp successfully requested NodePublish [%s]\", dir))", "positive_passages": [{"docid": "doc-en-kubernetes-d8c35fcb948670df81783d48737c49dba78eee3bd98e80f83b95ce53a92518be", "text": "Even if we were to introduce additional plugin capabilities that the CO can query (from driver) to find out what modes can be applied, there would still be the possibility of user/admin mis-configuration. Probably not, Is this where you think an additional capability would help ( ) That is a good point. Can't think of a way to detect/guess RWX when RWO is specified, this without the driver providing that info. Can we adopt the rule until we decide what capabilities would look like ?\nI will just try to summarize the conversation from Slack. We can safely assume that only applies to block storage type with file system on top of it. So for all - volumes that need to have called MUST have a file system() on them. Is that assumption correct? If it is - can we not use presence of field or we can query the local volume for fs type (like how we query selinux relabelling capability) and call only when - volume is RW and has a valid block storage file system type. Will this not solve our use case? EDIT: renamed to .\nWe'll need to make it clear that is only for block-based storage systems, and the field cannot be reused for some multi-protocol file server (ie, nfsv3, nfsv4, smb, etc). For that case, then the plugin will need to expose its own new storageclass parameter + volume attribute to specify protocol.\nCan we not use to get fsType - and use that information for calling ? It may be problematic to rely entirely on present inside csi source.\nthe only problem with is that in CSI volume info is intentionally opaque to the CSI code inside k8s. All mount logic is delegated to the driver.\nInstead of a new capability or trying to deduce how best to apply fsgroup, why not pass the to the driver and let it decide how to apply it (either as a attribute for the mount or top level request param)? Right now, all mount logic has been delegated to the external CSI driver except for applying permission. Thoughts ?\nthat is true but we can still inspect file system on the mounted path because by the time gets called volume is already mounted. This should be no different than how selinux support is determined. what you think?\nis this approved for 1.12 milestone? Thank you for working on this,\nstill discussing how best to approach this.", "commid": "kubernetes_issue_66323", "tokennum": 506}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e6520d4ad620e21114badad9e7f42193df1b01a97ba863d91831e30d754c667d", "query": "} // apply volume ownership <del> if !c.readOnly && fsGroup != nil { err := volume.SetVolumeOwnership(c, fsGroup) if err != nil { // attempt to rollback mount. glog.Error(log(\"mounter.SetupAt failed to set fsgroup volume ownership for [%s]: %v\", c.volumeID, err)) glog.V(4).Info(log(\"mounter.SetupAt attempting to unpublish volume %s due to previous error\", c.volumeID)) if unpubErr := csi.NodeUnpublishVolume(ctx, c.volumeID, dir); unpubErr != nil { glog.Error(log( \"mounter.SetupAt failed to unpublish volume [%s]: %v (caused by previous NodePublish error: %v)\", c.volumeID, unpubErr, err, )) return fmt.Errorf(\"%v (caused by %v)\", unpubErr, err) } </del> <ins> // The following logic is derived from https://github.com/kubernetes/kubernetes/issues/66323 // if fstype is \"\", then skip fsgroup (could be indication of non-block filesystem) // if fstype is provided and pv.AccessMode == ReadWriteOnly, then apply fsgroup </ins> <del> if unmountErr := removeMountDir(c.plugin, dir); unmountErr != nil { glog.Error(log( \"mounter.SetupAt failed to clean mount dir [%s]: %v (caused by previous NodePublish error: %v)\", dir, unmountErr, err, )) return fmt.Errorf(\"%v (caused by %v)\", unmountErr, err) } </del> <ins> err = c.applyFSGroup(fsType, fsGroup) if err != nil { // attempt to rollback mount. fsGrpErr := fmt.Errorf(\"applyFSGroup failed for vol %s: %v\", c.volumeID, err) if unpubErr := csi.NodeUnpublishVolume(ctx, c.volumeID, dir); unpubErr != nil { glog.Error(log(\"NodeUnpublishVolume failed for [%s]: %v\", c.volumeID, unpubErr)) return fsGrpErr } </ins> <del> return err </del> <ins> if unmountErr := removeMountDir(c.plugin, dir); unmountErr != nil { glog.Error(log(\"removeMountDir failed for [%s]: %v\", dir, unmountErr)) return fsGrpErr </ins> } <del> glog.V(4).Info(log(\"mounter.SetupAt sets fsGroup to [%d] for %s\", *fsGroup, c.volumeID)) </del> <ins> return fsGrpErr </ins> } glog.V(4).Infof(log(\"mounter.SetUp successfully requested NodePublish [%s]\", dir))", "positive_passages": [{"docid": "doc-en-kubernetes-5cbdf2214fb613203f89164533ba44fdfe78b2afafa2ed81aceb81e111086f6f", "text": "It would be a 1.12.\n[MILESTONENOTIFIER] Milestone Issue: Up-to-date for process <details open<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Never automatically move issue out of a release milestone; continually escalate to contributor and SIG through all available channels. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details\nApproved for 1.12\nBased on previous post, this is a summary: If then is not applied (because it could be an indication of a nonblock fs, or error) Done is provided if fstype is invalid Done if fstype is valid and then apply fsgroup logic else ignore fsGroup Done\n- any updates on ?\nWaiting for a review and approval.\nyou have a outstanding comment on the PR. Can you please answer that?\nHow does this approach relate to inline CSI volumes? There's no PersistentVolume involved, and hence no way to specify an access mode. , but my driver ignores it (always using tmpfs). I considered having my CSI driver read the mounting pod's spec to see if it has a security context with \"fsGroup\" set, since that detail is not supplied to the driver, as . My goal is to have the volume mounted with the files on it readable by the container's user, but there's no way for my driver to know who that user will be. Am I supposed to just use 0444 for the ownership bits, to allow everyone to read the files?", "commid": "kubernetes_issue_66323", "tokennum": 377}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e6771feb95a0c95017154cf86225354e47025b538ae262f4a29364626eccfb00", "query": "\"//cmd/kube-proxy/app:go_default_library\", \"//pkg/client/metrics/prometheus:go_default_library\", \"//pkg/version/prometheus:go_default_library\", <ins> \"//vendor/github.com/spf13/pflag:go_default_library\", </ins> \"//vendor/k8s.io/apiserver/pkg/util/flag:go_default_library\", \"//vendor/k8s.io/apiserver/pkg/util/logs:go_default_library\", ],", "positive_passages": [{"docid": "doc-en-kubernetes-5044536d87edb25c665421bf3dc4b536a0586e8213d754dc6188da659a17c1aa", "text": "There are no sig labels on this issue. Please add a sig label. <detailsA sig label can be by either: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. See the . The in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals 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\nprobably caused by\nCould be a clash between these two?\ncc\nI still see the issue with local-cluster on the latest master: F0225 17:06:49. ] error: v1alpha1.KubeProxyConfiguration: FeatureGates: ReadMapCB: expect { or n, but found \", error found in byte of ......\nlooks like that's another issue, can you please file a new bug? with more logs? this one was about none of the hyperkube based processes starting up.\nwill do as it is also broke container kube-proxy as well. Same type of error.", "commid": "kubernetes_issue_60378", "tokennum": 274}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e6d9cf027d64c2c84643af065b5f49d223d35c1d298d4f0c1dd5d77c42937a57", "query": "} ip, err := az.getIPForMachine(name) if err != nil { <del> glog.Errorf(\"error: az.NodeAddresses, az.getIPForMachine(%s), err=%v\", name, err) return nil, err </del> <ins> if az.CloudProviderBackoff { glog.V(2).Infof(\"NodeAddresses(%s) backing off\", name) ip, err = az.GetIPForMachineWithRetry(name) if err != nil { glog.V(2).Infof(\"NodeAddresses(%s) abort backoff\", name) return nil, err } } else { glog.Errorf(\"error: az.NodeAddresses, az.getIPForMachine(%s), err=%v\", name, err) return nil, err } </ins> } return []v1.NodeAddress{", "positive_passages": [{"docid": "doc-en-kubernetes-0f3fba1dceb9c94d1a19ea07536eb93382a47fa8d74b43be2f3310b5be7e4348", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: In certain large cluster scenarios we would like to anticipate kubelet behavior hitting request limits, and backoff in response. E.g., What you expected to happen: This is a request for add'l backoff coverage, so nothing surprising. How to reproduce it (as minimally and precisely as possible): Build a cluster with as many nodes as your subscription will support on azure until kubelet behavior contributes to backend API request limits. Environment: Kubernetes version (use ): and Cloud provider or hardware configuration**: azure OS (e.g. from /etc/os-release): Ubuntu 16.04.2 LTS (Xenial Xerus) Kernel (e.g. ): Linux k8s-pool7--7 4.4.0-83-generic -Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x8664 x8664 x86_64 GNU/Linux Install tools: acs-engine Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig azure", "commid": "kubernetes_issue_48971", "tokennum": 358}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e704697ecb7b458d813755a931378e143dd784c3a42a8bb8b2078b143bb0e58a", "query": "'${MASTER_IP}' create-flanneld-opts '127.0.0.1' '${MASTER_IP}' <del> sudo -E -p '[sudo] password to start master: ' -- /bin/bash -ce ' </del> <ins> FLANNEL_OTHER_NET_CONFIG='${FLANNEL_OTHER_NET_CONFIG}' sudo -E -p '[sudo] password to start master: ' -- /bin/bash -ce ' </ins> ${BASH_DEBUG_FLAGS} cp ~/kube/default/* /etc/default/ cp ~/kube/init_conf/* /etc/init/", "positive_passages": [{"docid": "doc-en-kubernetes-3bb3543c0323a70faea91ccc43a3eaf950d3e30c811cd93e021b94a126351841", "text": "and provide for configuring Flannel's parameter but none of the others listed in", "commid": "kubernetes_issue_19618", "tokennum": 20}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e70be627d8d51fa7e0f637efd62c004bfa1d350a20f631f1930efa35e344dcc0", "query": "}{ { code:     http.StatusBadRequest, <del> expected: true, </del> <ins> expected: false, </ins> }, { code:     http.StatusInternalServerError,", "positive_passages": [{"docid": "doc-en-kubernetes-e65d433be70b14f59611269e2f1c0fa746f312a0f5c96a0c29a874f17f7c06ea", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: If you create a service that reference a Basic IP in a standard load balancer cluster, the service will stuck at \"Pending\" state for days without detailed error from Azure response. When you describe the service, it only has following: What you expected to happen: In this case Azure responded 400 with detailed error message that the referenced IP is a basic IP and cannot be used on standard LB. I would expect the detailed error message show up as events for easier diagnostic. How to reproduce it (as minimally and precisely as possible): Create a service that reference a Basic IP in a standard load balancer cluster Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/assign /area provider/azure /sig cloud-provider\n/area cloudprovider", "commid": "kubernetes_issue_86686", "tokennum": 259}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e73f0c8898528169c6810b1b9be1fefa5720c6d7929ce64be445f25cecef32fb", "query": "func subnet(service *v1.Service) *string { if requiresInternalLoadBalancer(service) { <del> if l, found := service.Annotations[ServiceAnnotationLoadBalancerInternalSubnet]; found { </del> <ins> if l, found := service.Annotations[ServiceAnnotationLoadBalancerInternalSubnet]; found && strings.TrimSpace(l) != \"\" { </ins> return &l } }", "positive_passages": [{"docid": "doc-en-kubernetes-94ebb6d5cc5a883444cc57b7fe675619934dadcea635fbafcba0058503bec1c7", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: When service is set with ILB annotation and empty string subnet, e.g. The service would be pending forever with following error: What you expected to happen: ILB should be provisioned successfully. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Others: /sig azure /kind bug /assign\n/milestone v1.14 We're entering and this looks relevant to the 1.14 release. Please if I am incorrect\nThanks", "commid": "kubernetes_issue_74497", "tokennum": 195}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e76f7e9c7c02f4ed44a7684b377e9790429a2cf1db9b3d0f71f7ae55a06893d6", "query": "}, }, }, <ins> Required: []string{\"versions\"}, </ins> }, }, Dependencies: []string{", "positive_passages": [{"docid": "doc-en-kubernetes-65858ef6270e846dbad645a3cdb03be72308acbcbd2d437380bbe522248f5825", "text": "FYI. Currently the field of TPR is marked as which is wrong, actually if you try to create a TPR with empty versions, it will cause api server panic. Versions should be necessary field of TPR, we should validate this somehow.", "commid": "kubernetes_issue_36991", "tokennum": 52}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e777c4a6bf6a39f12928daf74cd488b5b88832f89a3a632852ed29f351849d86", "query": "statefulSetTimeout = 10 * time.Minute // statefulPodTimeout is a timeout for stateful pods to change state statefulPodTimeout = 5 * time.Minute <ins> testFinalizer = \"example.com/test-finalizer\" </ins> ) var httpProbe = &v1.Probe{", "positive_passages": [{"docid": "doc-en-kubernetes-cbff279a5a2209254c6527f41e3183737e33b6607a7e6fb4945b04f53611a022", "text": "My application is clustered and I have 2 pods running. I am using a rolling upgrade strategy and my partitioning number is 1. First I need to upgrade the pod with the ordinal number 1 so I triggered that upgrade with partitioning number 1 and my upgrade gets completed. After this, my pod having the ordinal number 0 gets restarted and it's automatically upgraded to a new image. This is not an expected behavior because still, my partition number is 1 and pod-0 should come up with an older image only. I am facing this issue for the v1.27 cluster. Prior to this, it was working fine. pod-0 should not upgrade to new image until I upgrade the partition number to 0.a Do helm install and upgrade pod-1 only keeping partition number to 1. No response <detailsconsole $ cat /etc/os-release $ uname -a C:wmic os get Caption, Version, BuildNumber, OSArchitecture </details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig/api-machinery\n/sig apps /sig storage\nHi, Can someone suggest here? As this is introduced in my setup after the v1.27 upgrade? Is there any change in partition logic?\nThis can be reproduced by using the said STS. 1 - Deploy STS using attached that has a replica count is 2 and updatingstrategy.rolling.partition as 1. 2 - Do edit STS and update the image to 1.15. This will upgrade, pod-1 with image 1.15. 3 - Next delete the pod pod-0 and check that POD-0 came up with a new image which is not the expected behavior. POD 0 should not be updated to a new image until the partition is changed to 0. We have noticed this behavior change in v1.27.", "commid": "kubernetes_issue_119685", "tokennum": 476}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e777c4a6bf6a39f12928daf74cd488b5b88832f89a3a632852ed29f351849d86", "query": "statefulSetTimeout = 10 * time.Minute // statefulPodTimeout is a timeout for stateful pods to change state statefulPodTimeout = 5 * time.Minute <ins> testFinalizer = \"example.com/test-finalizer\" </ins> ) var httpProbe = &v1.Probe{", "positive_passages": [{"docid": "doc-en-kubernetes-78482ca8aa8474337677389890aeefe9bf7c97cdeab333d3d2b330616683b55b", "text": "Pla suggest : apiVersion: v1 kind: Service metadata: name: nginx labels: app: nginx spec: ports: port: 80 name: web clusterIP: None selector: app: nginx apiVersion: apps/v1 kind: StatefulSet metadata: name: web-am spec: updateStrategy: type: RollingUpdate rollingUpdate: partition: 1 serviceName: \"nginx\" replicas: 2 selector: matchLabels: app: nginx template: metadata: labels: app: nginx spec: containers: name: nginx args: /bin/sh -c sleep 30;touch /tmp/healthy; sleep 3600 image: nginx:1.14.2 ports: containerPort: 80 name: web", "commid": "kubernetes_issue_119685", "tokennum": 170}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e7a5b943cb86dbf44f92c75cb3c548373510beda62c5375f3f116c45f03fdf35", "query": "expectedErrMsg:      fmt.Errorf(\"getError\"), }, { <del> name:                \"InstanceMetadataByProviderID should report error if VMSS instanceID is invalid\", metadataName:        \"vmss_$123\", providerID:          providerID, vmType:              vmTypeVMSS, useInstanceMetadata: true, expectedErrMsg:      fmt.Errorf(\"failed to parse VMSS instanceID %q: strconv.ParseInt: parsing %q: invalid syntax\", \"$123\", \"$123\"), }, { </del> name:         \"InstanceMetadataByProviderID should get metadata from Azure API if cloud.UseInstanceMetadata is false\", metadataName: \"vm1\", providerID:   providerID,", "positive_passages": [{"docid": "doc-en-kubernetes-93c0a615d6725c12b66abb2dead01e17ca700d451119b1467d3edce68f73a013", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: If computer name prefix does not match VMSS name, then Azure cloud provider will use VMSS API instead of using metadata service data. This leads to throttling, because every affected kubelet is making API requests. What you expected to happen: Azure cloud provider should use metadata service data instead of calling VMSS API when instance is current. How to reproduce it (as minimally and precisely as possible): Set computer name prefix of the VMSS to something different than default. You should observe Azure provider making requests to the VMSS API rather than using metadata service, which leads to throttling if you have multiple kubelets with this bug. Anything else we need to know?: This is bug was introduced by - returns false even if instance is current, because it expects node name to match VMSS name + instance id, however node name is derived from the computer-name-prefix which can be different than VMSS name. Node name should be matched against , not against . Environment: Kubernetes version (use ): 1.18.x and higher Cloud provider or hardware configuration: azure /sig cloud-provider\n/sig cloud-provider\n/area provider/azure\nCC\n/remove-sig cloud-provider /sig cloud-provider (trying to remove the label)\n/sig cloud-provider\nThanks for the reporting. Unfortunately, computer name prefix is not included in IMDS, so it can't be used without VMSS API for constructing the NodeName. Would check what could we do to workaround the issue.\nCan you memorize the computer name prefix in the first request to the Azure API and then use it for the isCurrentInstance check?\nopened to fix the issue. Would you like to have a look?\nI can confirm that your change should fix the problem I reported. Do you know if your fix will be to 1.18.x?\nis working on the cherry pick\nThank you for quick fix!", "commid": "kubernetes_issue_92733", "tokennum": 464}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e7a7689f8e666e1bfd07eca3018d01693bb66e01512f2c4539798dee01350a6f", "query": "<ins> /* Copyright 2022 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package plugin import ( \"context\" \"errors\" \"fmt\" \"time\" v1 \"k8s.io/api/core/v1\" resourceapi \"k8s.io/api/resource/v1alpha3\" apierrors \"k8s.io/apimachinery/pkg/api/errors\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/fields\" utilversion \"k8s.io/apimachinery/pkg/util/version\" \"k8s.io/apimachinery/pkg/util/wait\" \"k8s.io/client-go/kubernetes\" \"k8s.io/klog/v2\" \"k8s.io/kubernetes/pkg/kubelet/pluginmanager/cache\" ) // defaultClientCallTimeout is the default amount of time that a DRA driver has // to respond to any of the gRPC calls. kubelet uses this value by passing nil // to RegisterPlugin. Some tests use a different, usually shorter timeout to // speed up testing. // // This is half of the kubelet retry period (according to // https://github.com/kubernetes/kubernetes/commit/0449cef8fd5217d394c5cd331d852bd50983e6b3). const defaultClientCallTimeout = 45 * time.Second // RegistrationHandler is the handler which is fed to the pluginwatcher API. type RegistrationHandler struct { // backgroundCtx is used for all future activities of the handler. // This is necessary because it implements APIs which don't // provide a context. backgroundCtx context.Context kubeClient    kubernetes.Interface getNode       func() (*v1.Node, error) } var _ cache.PluginHandler = &RegistrationHandler{} // NewPluginHandler returns new registration handler. // // Must only be called once per process because it manages global state. // If a kubeClient is provided, then it synchronizes ResourceSlices // with the resource information provided by plugins. func NewRegistrationHandler(kubeClient kubernetes.Interface, getNode func() (*v1.Node, error)) *RegistrationHandler { handler := &RegistrationHandler{ // The context and thus logger should come from the caller. backgroundCtx: klog.NewContext(context.TODO(), klog.LoggerWithName(klog.TODO(), \"DRA registration handler\")), kubeClient:    kubeClient, getNode:       getNode, } // When kubelet starts up, no DRA driver has registered yet. None of // the drivers are usable until they come back, which might not happen // at all. Therefore it is better to not advertise any local resources // because pods could get stuck on the node waiting for the driver // to start up. // // This has to run in the background. go handler.wipeResourceSlices(\"\") return handler } // wipeResourceSlices deletes ResourceSlices of the node, optionally just for a specific driver. func (h *RegistrationHandler) wipeResourceSlices(driver string) { if h.kubeClient == nil { return } ctx := h.backgroundCtx logger := klog.FromContext(ctx) backoff := wait.Backoff{ Duration: time.Second, Factor:   2, Jitter:   0.2, Cap:      5 * time.Minute, Steps:    100, } // Error logging is done inside the loop. Context cancellation doesn't get logged. _ = wait.ExponentialBackoffWithContext(ctx, backoff, func(ctx context.Context) (bool, error) { node, err := h.getNode() if apierrors.IsNotFound(err) { return false, nil } if err != nil { logger.Error(err, \"Unexpected error checking for node\") return false, nil } fieldSelector := fields.Set{resourceapi.ResourceSliceSelectorNodeName: node.Name} if driver != \"\" { fieldSelector[resourceapi.ResourceSliceSelectorDriver] = driver } err = h.kubeClient.ResourceV1alpha3().ResourceSlices().DeleteCollection(ctx, metav1.DeleteOptions{}, metav1.ListOptions{FieldSelector: fieldSelector.String()}) switch { case err == nil: logger.V(3).Info(\"Deleted ResourceSlices\", \"fieldSelector\", fieldSelector) return true, nil case apierrors.IsUnauthorized(err): // This can happen while kubelet is still figuring out // its credentials. logger.V(5).Info(\"Deleting ResourceSlice failed, retrying\", \"fieldSelector\", fieldSelector, \"err\", err) return false, nil default: // Log and retry for other errors. logger.V(3).Info(\"Deleting ResourceSlice failed, retrying\", \"fieldSelector\", fieldSelector, \"err\", err) return false, nil } }) } // RegisterPlugin is called when a plugin can be registered. func (h *RegistrationHandler) RegisterPlugin(pluginName string, endpoint string, versions []string, pluginClientTimeout *time.Duration) error { // Prepare a context with its own logger for the plugin. // // The lifecycle of the plugin's background activities is tied to our // root context, so canceling that will also cancel the plugin. // // The logger injects the plugin name as additional value // into all log output related to the plugin. ctx := h.backgroundCtx logger := klog.FromContext(ctx) logger = klog.LoggerWithValues(logger, \"pluginName\", pluginName) ctx = klog.NewContext(ctx, logger) logger.V(3).Info(\"Register new DRA plugin\", \"endpoint\", endpoint) highestSupportedVersion, err := h.validateVersions(pluginName, versions) if err != nil { return fmt.Errorf(\"version check of plugin %s failed: %w\", pluginName, err) } var timeout time.Duration if pluginClientTimeout == nil { timeout = defaultClientCallTimeout } else { timeout = *pluginClientTimeout } ctx, cancel := context.WithCancelCause(ctx) pluginInstance := &Plugin{ backgroundCtx:           ctx, cancel:                  cancel, conn:                    nil, endpoint:                endpoint, highestSupportedVersion: highestSupportedVersion, clientCallTimeout:       timeout, } // Storing endpoint of newly registered DRA Plugin into the map, where plugin name will be the key // all other DRA components will be able to get the actual socket of DRA plugins by its name. if draPlugins.add(pluginName, pluginInstance) { logger.V(1).Info(\"Already registered, previous plugin was replaced\") } return nil } func (h *RegistrationHandler) validateVersions( pluginName string, versions []string, ) (*utilversion.Version, error) { if len(versions) == 0 { return nil, errors.New(\"empty list for supported versions\") } // Validate version newPluginHighestVersion, err := utilversion.HighestSupportedVersion(versions) if err != nil { // HighestSupportedVersion includes the list of versions in its error // if relevant, no need to repeat it here. return nil, fmt.Errorf(\"none of the versions are supported: %w\", err) } existingPlugin := draPlugins.get(pluginName) if existingPlugin == nil { return newPluginHighestVersion, nil } if existingPlugin.highestSupportedVersion.LessThan(newPluginHighestVersion) { return newPluginHighestVersion, nil } return nil, fmt.Errorf(\"another plugin instance is already registered with a higher supported version: %q < %q\", newPluginHighestVersion, existingPlugin.highestSupportedVersion) } // DeRegisterPlugin is called when a plugin has removed its socket, // signaling it is no longer available. func (h *RegistrationHandler) DeRegisterPlugin(pluginName string) { if p := draPlugins.delete(pluginName); p != nil { logger := klog.FromContext(p.backgroundCtx) logger.V(3).Info(\"Deregister DRA plugin\", \"endpoint\", p.endpoint) // Clean up the ResourceSlices for the deleted Plugin since it // may have died without doing so itself and might never come // back. go h.wipeResourceSlices(pluginName) return } logger := klog.FromContext(h.backgroundCtx) logger.V(3).Info(\"Deregister DRA plugin not necessary, was already removed\") } // ValidatePlugin is called by kubelet's plugin watcher upon detection // of a new registration socket opened by DRA plugin. func (h *RegistrationHandler) ValidatePlugin(pluginName string, endpoint string, versions []string) error { _, err := h.validateVersions(pluginName, versions) if err != nil { return fmt.Errorf(\"invalid versions of plugin %s: %w\", pluginName, err) } return err } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-e1c6f7407b346df6fb6212f23a2f930e04198e198bb03b9cff5041967802082d", "text": "The PR above moved everything related to into because that was where most of the code already was, but didn't renamed the files to avoid a larger diff and merge conflicts. Once is merged, we can do the renaming. Code clarity. /sig node\n/triage accepted /priority important-soon\n/assign\na PR can be created for this now.\nwill do", "commid": "kubernetes_issue_125924", "tokennum": 75}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e7ce846309a8184798bd7d79b77dcf46c09a262f00e363c7a09cca4717cbd873", "query": "const ( pvDeletionTimeout       = 3 * time.Minute statefulSetReadyTimeout = 3 * time.Minute <ins> taintKeyPrefix          = \"zoneTaint_\" </ins> ) var _ = utils.SIGDescribe(\"Regional PD\", func() {", "positive_passages": [{"docid": "doc-en-kubernetes-07b454797aabeff00bf033fc34fa4c22bd06966ba8574ac0fa868459bacbceea", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: What happened: Testgrid: https://k8s-\n/assign\nThe test's assumption about test parameter is wrong. Previously it assumed the group name is the same across all zones, but they are different in regional clusters. Looking into using node taints as the permanent fix, as suggested by the TODO comment in the test.\nHm I think taint based evictions is still an alpha feature.\nOK. I propose the following solution: Get the zone of Schedule the StatefulSet pod to that zone using node affinity; wait for the pod to run Remove the node affinity from StatefulSet Delete\nCan it be simplified? Schedule the pod Figure out which zone that pod got scheduled in Delete the instance group of that zone\nUnfortunately I don't know of a good way to look up the instance group given the zone, since there could be instance groups from multiple clusters in the same project\nHow about: Schedule the pod Figure out the zone Taint all the nodes in the zone Kill the pod\nTaint with NoSchedule? yeah that sounds good", "commid": "kubernetes_issue_69005", "tokennum": 267}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e7d86f4108fb5fd6117dfcb994f42796562b630eb232d6c005fb7fccd37624b7", "query": "return multiGroupVersioner{target: gv, acceptedGroupKinds: groupKinds} } <ins> // NewCoercingMultiGroupVersioner returns the provided group version for any incoming kind. // Incoming kinds that match the provided groupKinds are preferred. // Kind may be empty in the provided group kind, in which case any kind will match. // Examples: //   gv=mygroup/__internal, groupKinds=mygroup/Foo, anothergroup/Bar //   KindForGroupVersionKinds(yetanother/v1/Baz, anothergroup/v1/Bar) -> mygroup/__internal/Bar (matched preferred group/kind) // //   gv=mygroup/__internal, groupKinds=mygroup, anothergroup //   KindForGroupVersionKinds(yetanother/v1/Baz, anothergroup/v1/Bar) -> mygroup/__internal/Bar (matched preferred group) // //   gv=mygroup/__internal, groupKinds=mygroup, anothergroup //   KindForGroupVersionKinds(yetanother/v1/Baz, yetanother/v1/Bar) -> mygroup/__internal/Baz (no preferred group/kind match, uses first kind in list) func NewCoercingMultiGroupVersioner(gv schema.GroupVersion, groupKinds ...schema.GroupKind) GroupVersioner { return multiGroupVersioner{target: gv, acceptedGroupKinds: groupKinds, coerce: true} } </ins> // KindForGroupVersionKinds returns the target group version if any kind matches any of the original group kinds. It will // use the originating kind where possible. func (v multiGroupVersioner) KindForGroupVersionKinds(kinds []schema.GroupVersionKind) (schema.GroupVersionKind, bool) {", "positive_passages": [{"docid": "doc-en-kubernetes-7ee140198c665b218e0dfb7e3cd2f2624912887cfcfab5f30828d12c6130aa35", "text": "What happened: Set up a HA cluster with 1.9 and 1.10 API servers (occurs on any apiserver skew boundary where a cohabitating resource's storage version changed groups) Observed errors when modifying workload objects: when modified via the 1.10 server, saw this error in the 1.9 server: when modified via the 1.9 server, saw this error in the 1.10 server: When this error was encountered, all watchers for the resource in question would be dropped and have to re-establish, and the internal watchers feeding the watch cache would drop and re-establish What you expected to happen: Watch events from all supported storage versions are processed correctly How to reproduce it (as minimally and precisely as possible): Start a server from master (for inspectability, store in json). With Create a deployment (e.g. kube-dns in kube-system) Establish a watch via extensions (kubectl get deployments.extensions --all-namespaces -w) Establish a watch via apps (kubectl get --all-namespaces -w) Tail the kube-apiserver log Change the apps/v1 deployment in etcd to extensions/v1beta1: Observer client watches drop and server log errors: Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: /sig api-machinery /cc /priority critical-urgent\nerror is triggered by this returning false: constructed here: the info about expected cohabitating groups is not included in the list of acceptable inputs", "commid": "kubernetes_issue_73478", "tokennum": 368}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e80ff961b20b1b5a1e447b9624aca9f22c977f1df75594679a1eb60d05525d27", "query": "// updated. The updated Endpoints object or an error will be returned. func (adapter *EndpointsAdapter) Update(namespace string, endpoints *corev1.Endpoints) (*corev1.Endpoints, error) { endpoints, err := adapter.endpointClient.Endpoints(namespace).Update(endpoints) <del> if err == nil && adapter.endpointSliceClient != nil { _, err = adapter.ensureEndpointSliceFromEndpoints(namespace, endpoints) </del> <ins> if err == nil { err = adapter.EnsureEndpointSliceFromEndpoints(namespace, endpoints) </ins> } return endpoints, err } <del> // ensureEndpointSliceFromEndpoints accepts a namespace and Endpoints resource // and creates or updates a corresponding EndpointSlice. The EndpointSlice // and/or an error will be returned. func (adapter *EndpointsAdapter) ensureEndpointSliceFromEndpoints(namespace string, endpoints *corev1.Endpoints) (*discovery.EndpointSlice, error) { </del> <ins> // EnsureEndpointSliceFromEndpoints accepts a namespace and Endpoints resource // and creates or updates a corresponding EndpointSlice if an endpointSliceClient // exists. An error will be returned if it fails to sync the EndpointSlice. func (adapter *EndpointsAdapter) EnsureEndpointSliceFromEndpoints(namespace string, endpoints *corev1.Endpoints) error { if adapter.endpointSliceClient == nil { return nil } </ins> endpointSlice := endpointSliceFromEndpoints(endpoints) <del> _, err := adapter.endpointSliceClient.EndpointSlices(namespace).Get(endpointSlice.Name, metav1.GetOptions{}) </del> <ins> currentEndpointSlice, err := adapter.endpointSliceClient.EndpointSlices(namespace).Get(endpointSlice.Name, metav1.GetOptions{}) </ins> if err != nil { if errors.IsNotFound(err) { <del> return adapter.endpointSliceClient.EndpointSlices(namespace).Create(endpointSlice) </del> <ins> if _, err = adapter.endpointSliceClient.EndpointSlices(namespace).Create(endpointSlice); errors.IsAlreadyExists(err) { err = nil } </ins> } <del> return nil, err </del> <ins> return err } if apiequality.Semantic.DeepEqual(currentEndpointSlice.Endpoints, endpointSlice.Endpoints) && apiequality.Semantic.DeepEqual(currentEndpointSlice.Ports, endpointSlice.Ports) && apiequality.Semantic.DeepEqual(currentEndpointSlice.Labels, endpointSlice.Labels) { return nil </ins> } <del> return adapter.endpointSliceClient.EndpointSlices(namespace).Update(endpointSlice) </del> <ins> _, err = adapter.endpointSliceClient.EndpointSlices(namespace).Update(endpointSlice) return err </ins> } // endpointSliceFromEndpoints generates an EndpointSlice from an Endpoints", "positive_passages": [{"docid": "doc-en-kubernetes-12f7047d8d873a7d6bac7023fc38517c350449071b3fe2b6d53f3ea14de5351f", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: EndpointSlice for masters was not created after enabling EndpointSlice on a pre-existing cluster. Only those EndpointSlices managed by kube-controller-manager were created. What you expected to happen: EndpointSlice for masters should be created after enabling EndpointSlice on a pre-existing cluster, the same as the EndpointSlices managed by kube-controller-manager. How to reproduce it (as minimally and precisely as possible): kubeadm to create a cluster: the EndpointSlice feature by editing the kube-apiserver, kube-controller-manager, kube-proxy manifest kube-apiserver and kube-controller-manager is restarted, the EndpointSlice in namespace will be missing. Anything else we need to know?: Environment: Kubernetes version (use ):Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools:Network plugin and version (if this is a network-related bug): Others:\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/remove-triage unresolved /assign", "commid": "kubernetes_issue_84419", "tokennum": 307}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e82b378dd04a9d7cb35a844ed4ce7c1efb719cd79e5363f5608a62b2c46109c8", "query": "import ( \"fmt\" <del> \"strings\" </del> \"time\" \"k8s.io/kubernetes/pkg/api\" <del> client \"k8s.io/kubernetes/pkg/client/unversioned\" </del> \"k8s.io/kubernetes/pkg/util\" . \"github.com/onsi/ginkgo\"", "positive_passages": [{"docid": "doc-en-kubernetes-cf37b0ab7a08d0e2457507bc271b1cb7d1e13fbaee3773971363bc32ae71b35b", "text": "We are running heapster, dns server, kube-proxy etc. in kube-system namespace. Some e2e tests try to make sure all those kube-system pods are at ready state before firing the real tests, others just simply ingore them. But both cases might cause e2e flakiness when some of those kube-system containers are in crashloop, for example, for heapster crashloop, for influxdb crashloop, etc. When such cases happen, the developer doesn't have much information on why since the nodes might be teared down. We should watch those kube-system pods, and onContainerFailure, we should collect the related logs. One simple way is using kubectl logs <Pod<Container--previous cc/\nis this related enough to and that you can bundle it in?\nThe logs from the pods should be retrieved via the api server. This is different from the kubelet logs. I'll upload a PR for this.\nGreat job It will be very helpful for debugging.", "commid": "kubernetes_issue_20099", "tokennum": 229}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e84c0e32bfe65505956074e2f3aaca99604674973b4c388043a60a6186bc3923", "query": "t.Fatalf(\"failed to mark all StatefulSet pods to ready: %v\", err) } } <ins> // add for issue: https://github.com/kubernetes/kubernetes/issues/108837 func TestStatefulSetStatusWithPodFail(t *testing.T) { limitedPodNumber := 2 controlPlaneConfig := framework.NewIntegrationTestControlPlaneConfig() controlPlaneConfig.GenericConfig.AdmissionControl = &fakePodFailAdmission{ limitedPodNumber: limitedPodNumber, } _, s, closeFn := framework.RunAnAPIServer(controlPlaneConfig) defer closeFn() config := restclient.Config{Host: s.URL} c, err := clientset.NewForConfig(&config) if err != nil { t.Fatalf(\"Could not create clientset: %v\", err) } resyncPeriod := 12 * time.Hour informers := informers.NewSharedInformerFactory(clientset.NewForConfigOrDie(restclient.AddUserAgent(&config, \"statefulset-informers\")), resyncPeriod) ssc := statefulset.NewStatefulSetController( informers.Core().V1().Pods(), informers.Apps().V1().StatefulSets(), informers.Core().V1().PersistentVolumeClaims(), informers.Apps().V1().ControllerRevisions(), clientset.NewForConfigOrDie(restclient.AddUserAgent(&config, \"statefulset-controller\")), ) ns := framework.CreateTestingNamespace(\"test-pod-fail\", s, t) defer framework.DeleteTestingNamespace(ns, s, t) ctx, cancel := context.WithCancel(context.Background()) defer cancel() informers.Start(ctx.Done()) go ssc.Run(ctx, 5) sts := newSTS(\"sts\", ns.Name, 4) _, err = c.AppsV1().StatefulSets(sts.Namespace).Create(context.TODO(), sts, metav1.CreateOptions{}) if err != nil { t.Fatalf(\"Could not create statefuleSet %s: %v\", sts.Name, err) } wantReplicas := limitedPodNumber var gotReplicas int32 if err := wait.PollImmediate(pollInterval, pollTimeout, func() (bool, error) { newSTS, err := c.AppsV1().StatefulSets(sts.Namespace).Get(context.TODO(), sts.Name, metav1.GetOptions{}) if err != nil { return false, err } gotReplicas = newSTS.Status.Replicas return gotReplicas == int32(wantReplicas), nil }); err != nil { t.Fatalf(\"StatefulSet %s status has %d replicas, want replicas %d: %v\", sts.Name, gotReplicas, wantReplicas, err) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-0cad02d163e61aff3cc2c1257b68701a42fb1145e0b51f6816fd9a85adca78e6", "text": "I create a ResourceQuota with two pods limit in my namespace. Then, I create a statefuleSet with 3 replicas. As expected, two pods are created successfully, and the third pod failed to create. But, the ReadyReplicas is not 2 ,but 1. The ReadyReplicas is correct 1Create a ResourceQuota with two pods limit in a new namespace. 2Create a statefulSet with 3 replicas 3Check if the ReadyReplicas of statefulSet matchs the number of stateful running pods. 1According to the logic of the statefulSet controller, new pod created in current sync is not be immediately counted into the ReadyReplicas. 2Failure to create pod will cause to return error, then skip updating status. <details</details<details</details<detailskind v1.23.3 </details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig apps\n/assign", "commid": "kubernetes_issue_108837", "tokennum": 302}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e85ed9aa688c730787be622b07eb18a2d5eb7ac72d15cac32179d75c14f08568", "query": "Name: \"mypsp\", }, Spec: policy.PodSecurityPolicySpec{ <ins> AllowedUnsafeSysctls: []string{\"kernel.*\", \"net.ipv4.ip_local_port_range\"}, ForbiddenSysctls:     []string{\"net.ipv4.ip_default_ttl\"}, </ins> SELinux: policy.SELinuxStrategyOptions{ Rule: policy.SELinuxStrategyRunAsAny, },", "positive_passages": [{"docid": "doc-en-kubernetes-1c37f3b13ef66319b53623e24b4fece0550cb85e7e62ca9b694924c6c433e0c8", "text": "/kind bug What happened: does not show the description for the new field in What you expected to happen: should describe the new field. How to reproduce it (as minimally and precisely as possible): Environment: Kubernetes version (use ): master\n/sig auth\nGitHub didn't allow me to assign the following users: fanzhangio. Note that only and repo collaborators can be assigned. <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\nIf nobody has started yet, I wanna to pick it up.\nwas working on it AFAIR.\nIndeed. if you don't mind, I'd take over.", "commid": "kubernetes_issue_65181", "tokennum": 165}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e87da8bd1825dff673941393b9eda3da7d43e4c36eb94fd871e0d511fab6e15e", "query": "defer testKubelet.Cleanup() kubelet := testKubelet.kubelet pods := newTestPods(5) <ins> now := metav1.NewTime(time.Now()) </ins> pods[0].Status.Phase = v1.PodFailed pods[1].Status.Phase = v1.PodSucceeded <ins> // The pod is terminating, should not filter out. </ins> pods[2].Status.Phase = v1.PodRunning <ins> pods[2].DeletionTimestamp = &now pods[2].Status.ContainerStatuses = []v1.ContainerStatus{ {State: v1.ContainerState{ Running: &v1.ContainerStateRunning{ StartedAt: now, }, }}, } </ins> pods[3].Status.Phase = v1.PodPending <ins> pods[4].Status.Phase = v1.PodRunning </ins> expected := []*v1.Pod{pods[2], pods[3], pods[4]} kubelet.podManager.SetPods(pods)", "positive_passages": [{"docid": "doc-en-kubernetes-05fa43eac8c17b852831e6979a2d93db8ab276262ace733bb7d146872dff7701", "text": "pointed out that for scheduling and kubelet admission, we should consider resources of terminated-but-not-yet-deleted pods to still be in use, because it may take an arbitrary amount of time for the system to deallocate resources. We didn't check to see if this is currently how it is implemented or not. cc/ /sig scheduling\ncc/\nFor terminated-but-not-yet-deleted & phase is case, the Pod is still in scheduler's cache, so it's handled well in scheduler; the Pod will be removed from cache when it's deleted. But in kubelet, it filtered terminated-but-not-yet-deleted out () when using scheduler.predicates. The option in my mind is to ~pass all Pods (including terminated-but-not-yet-deleted) to each admin, and let each admin decide whether filter terminated-but-not-yet-deleted out~ only filter out finished (Failed or Succeed) pods for Admits.\nIn -, it already consider by . So both scheduler & kubelet handles terminated-but-not-yet-deleted pods well.\nGreat, thanks for looking into it!\nshould this issue be closed then?\nI think so.\nJust to clarify: Kubelet correctly accounts the resources used by terminated-but-not-yet-deleted pods, i.e, kubelet does not count the resource usage of those pods towards total usage on the node. Scheduler, however, does not do the same. Scheduler waits for a pod to be deleted, and then it deducts its resource request from the associated node total usage. Upon deletion of a pod, scheduler is notified and acts: So, scheduler and kubelet behaviors are not exactly the same. I am not sure if scheduler can receive an event when a pod's container status changes. If it could, we could make the logic the same as that of Kubelet.\nI guess the current behavior is OK because it is conservative (scheduler considers the resources to be in use even though kubelet considers them free). And actually it seems that scheduler is more \"correct\" than kubelet, since the resources really aren't usable until the pod is deleted, right? (IIUC that was Vish's original point)\nI agree. The current behavior is correct, but a bit conservative. Basically, the scheduler side is more conservative and waits until a pod is deleted from the cache before considering its resources released.", "commid": "kubernetes_issue_47867", "tokennum": 529}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e87da8bd1825dff673941393b9eda3da7d43e4c36eb94fd871e0d511fab6e15e", "query": "defer testKubelet.Cleanup() kubelet := testKubelet.kubelet pods := newTestPods(5) <ins> now := metav1.NewTime(time.Now()) </ins> pods[0].Status.Phase = v1.PodFailed pods[1].Status.Phase = v1.PodSucceeded <ins> // The pod is terminating, should not filter out. </ins> pods[2].Status.Phase = v1.PodRunning <ins> pods[2].DeletionTimestamp = &now pods[2].Status.ContainerStatuses = []v1.ContainerStatus{ {State: v1.ContainerState{ Running: &v1.ContainerStateRunning{ StartedAt: now, }, }}, } </ins> pods[3].Status.Phase = v1.PodPending <ins> pods[4].Status.Phase = v1.PodRunning </ins> expected := []*v1.Pod{pods[2], pods[3], pods[4]} kubelet.podManager.SetPods(pods)", "positive_passages": [{"docid": "doc-en-kubernetes-0f8f1ec2a7e3c6ce351bcfa7358868ba1886341c66515327ef662e361aa12de0", "text": "That said, I believe resources of terminated-but-not-deleted pods are usable on nodes (should be verified). So, the current behavior is a bit less than ideal in terms of efficiency, but AFAIK the duration between termination and deletion is only a few seconds. So, it may not be worth optimizing.\nI thought was saying the opposite (see my first entry in this issue). Maybe he can clarify.", "commid": "kubernetes_issue_47867", "tokennum": 91}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e889b1ec87e0b5f0fadbcae4bcfb2b9967a35c37a35c90df0d5282ec12bd9b3c", "query": "podClient = f.PodClient() }) <del> ginkgo.Context(\"when creating a pod in the host PID namespace\", func() { makeHostPidPod := func(podName, image string, command []string, hostPID bool) *v1.Pod { return &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name: podName, }, Spec: v1.PodSpec{ RestartPolicy: v1.RestartPolicyNever, HostPID:       hostPID, Containers: []v1.Container{ { Image:   image, Name:    podName, Command: command, }, }, }, } } createAndWaitHostPidPod := func(podName string, hostPID bool) { podClient.Create(makeHostPidPod(podName, framework.BusyBoxImage, []string{\"sh\", \"-c\", \"pidof nginx || true\"}, hostPID, )) podClient.WaitForSuccess(podName, framework.PodStartTimeout) } nginxPid := \"\" ginkgo.BeforeEach(func() { nginxPodName := \"nginx-hostpid-\" + string(uuid.NewUUID()) podClient.CreateSync(makeHostPidPod(nginxPodName, imageutils.GetE2EImage(imageutils.Nginx), nil, true, )) output := f.ExecShellInContainer(nginxPodName, nginxPodName, \"cat /var/run/nginx.pid\") nginxPid = strings.TrimSpace(output) }) ginkgo.It(\"should show its pid in the host PID namespace [LinuxOnly] [NodeFeature:HostAccess]\", func() { busyboxPodName := \"busybox-hostpid-\" + string(uuid.NewUUID()) createAndWaitHostPidPod(busyboxPodName, true) logs, err := e2epod.GetPodLogs(f.ClientSet, f.Namespace.Name, busyboxPodName, busyboxPodName) if err != nil { framework.Failf(\"GetPodLogs for pod %q failed: %v\", busyboxPodName, err) } pids := strings.TrimSpace(logs) framework.Logf(\"Got nginx's pid %q from pod %q\", pids, busyboxPodName) if pids == \"\" { framework.Failf(\"nginx's pid should be seen by hostpid containers\") } pidSets := sets.NewString(strings.Split(pids, \" \")...) if !pidSets.Has(nginxPid) { framework.Failf(\"nginx's pid should be seen by hostpid containers\") } }) ginkgo.It(\"should not show its pid in the non-hostpid containers [LinuxOnly] [NodeFeature:HostAccess]\", func() { busyboxPodName := \"busybox-non-hostpid-\" + string(uuid.NewUUID()) createAndWaitHostPidPod(busyboxPodName, false) logs, err := e2epod.GetPodLogs(f.ClientSet, f.Namespace.Name, busyboxPodName, busyboxPodName) if err != nil { framework.Failf(\"GetPodLogs for pod %q failed: %v\", busyboxPodName, err) } pids := strings.TrimSpace(logs) framework.Logf(\"Got nginx's pid %q from pod %q\", pids, busyboxPodName) pidSets := sets.NewString(strings.Split(pids, \" \")...) if pidSets.Has(nginxPid) { framework.Failf(\"nginx's pid should not be seen by non-hostpid containers\") } }) }) </del> ginkgo.Context(\"When creating a container with runAsUser\", func() { makeUserPod := func(podName, image string, command []string, userid int64) *v1.Pod { return &v1.Pod{", "positive_passages": [{"docid": "doc-en-kubernetes-b8a3e3a5c22dc8491069aa612d226f113bfee5a5c0b17ff9cb35a90b4b6a10ba", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: , Which test(s) are failing: Since when has it been failing: since this PR introduced them Testgrid link: Note that this is the flakiest test in both dashboards, and failing quite frequently. Reason for failure: unknown Anything else we need to know: cc\n/sig node\nsee: , both getting empty PID and multiple PIDs.\nopened revert at\nfor discoverability for the release team /priority critical-urgent /milestone v1.17", "commid": "kubernetes_issue_84209", "tokennum": 127}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e8d34f2b728b4b06db8131bd5bdfead7d71cdaad3966b2c0d21ebdbaca934df3", "query": "return err } <ins> // ignoreStatusForbiddenFromError returns nil if the status code is StatusForbidden. // This happens when AuthorizationFailed is reported from Azure API. func ignoreStatusForbiddenFromError(err error) error { if err == nil { return nil } v, ok := err.(autorest.DetailedError) if ok && v.StatusCode == http.StatusForbidden { return nil } return err } </ins> /// getVirtualMachine calls 'VirtualMachinesClient.Get' with a timed cache /// The service side has throttling control that delays responses if there're multiple requests onto certain vm /// resource request in short period.", "positive_passages": [{"docid": "doc-en-kubernetes-4ac48b480971aca26f0a1896d0fa1bdd3b9ed6e78abeeb1cea4ee05f140cc101", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: controller-manager is stuck in deleting an incorrectly configured LB type service. it cannot be recovered until restarted. What you expected to happen: controller-manager should recover. At least it should allow us to create the service without restarting it. How to reproduce it (as minimally and precisely as possible): put a random IP in above yaml and make sure the resource group doen't exist. Anything else we need to know?: Environment: Kubernetes version (use ): 1.12.4 Cloud provider or hardware configuration: AKS OS (e.g: ): Kernel (e.g. ): Install tools: Others:\n/sig azure\nI also want to add that the above repro is stuck in 403. It's possible for it to be stuck in 404 as well when the SP has the right permission.\nCan you share the log for 404?\nThanks for reporting the issue. /assign Do you mean other services couldn't be configured when this happens?\ncorrect.\nFYI, we had the same issue when the Idle Timeout annotation was set to \"3\" which isn't a supported case. Will this PR also cover this edge case ?\nUnfortunately , this is still not fixed. The idle timeout is not 403 or 404. We need another fix for this (and possibly more for other annotations)", "commid": "kubernetes_issue_75198", "tokennum": 337}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e8f144112ac1a67bc87d092ccb7bf937556dd04fe7fa113e4593b23c475ca859", "query": "new.Spec.RequiresRepublish = &requiresRepublish }, }, <ins> { name: \"StorageCapacity changed\", modify: func(new *storage.CSIDriver) { new.Spec.StorageCapacity = &notStorageCapacity }, }, </ins> } for _, test := range successCases { t.Run(test.name, func(t *testing.T) {", "positive_passages": [{"docid": "doc-en-kubernetes-cdccab911562ccfffce851739652bcccdbeabc99e62d699c46baa58ef67f3bbe", "text": "Up to 1.21, that field is immutable. That means in practice, a CSIDriver object has to be deleted and then re-created with a different value instead. Mutation via delete/created is unnecessarily complex and as the only consumer of that field (the kube-scheduler) can handle mutation just fine (it'll always ask the informer cache for the current value), it's better to allow mutation.\n/sig storage /assign\nThis is independent of allowing other fields to become mutable, but that might also make sense.\n/triage accepted", "commid": "kubernetes_issue_100089", "tokennum": 125}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e8f39dd825af32319dc2f48072c0788081cb8816cebb1a526d34cd36f8d70985", "query": "if in.XEmbeddedResource { out.VendorExtensible.AddExtension(\"x-kubernetes-embedded-resource\", true) } <del> if in.XIntOrString { out.VendorExtensible.AddExtension(\"x-kubernetes-int-or-string\", true) } </del> return nil }", "positive_passages": [{"docid": "doc-en-kubernetes-42eca355948acd2923f06d9ab50c5116c5afebe4d73334e949a0d732f7352d29", "text": "The server-side validation does not check the type of values with . Create a CRD like: Then create a CR: It is not rejected, but should because must not be a boolean.", "commid": "kubernetes_issue_78817", "tokennum": 40}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e90c8857203276bd85e12e141fd54e14252db1505451c7abcf7dac1888ac107f", "query": "started = !exists } podStatus.ContainerStatuses[i].Started = &started <ins> if started { var ready bool if c.State.Running == nil { ready = false } else if result, ok := m.readinessManager.Get(kubecontainer.ParseContainerID(c.ContainerID)); ok { ready = result == results.Success } else { // The check whether there is a probe which hasn't run yet. _, exists := m.getWorker(podUID, c.Name, readiness) ready = !exists } podStatus.ContainerStatuses[i].Ready = ready } </ins> } // init containers are ready if they have exited with success or if a readiness probe has // succeeded.", "positive_passages": [{"docid": "doc-en-kubernetes-1a4f2a91f513677e5b237ae427502f2b96572c4f540bf286aa5c4a8d97d94caf", "text": "If I have probe and then all good. Previous version of the pod is terminated after startup probe success, but if wasn't specified the pod becomes ready immediately. It would be nice to add new state (for example starting) which would have pods until a is successful. Also, it would mean that container not ready for connection. Thank you for attention!\n/sig cluster-lifecycle\n/remove-sig cluster-lifecycle /sig apps try asking in #kubernetes-users on k8s slack.\nthey are silent in the chat. Who is involved in the development of startup probe?\ni think this topic better fits SIG Node. try asking in their channel on slack , but be patient ;) /sig node /remove-sig apps\nThose labels are not set on the issue: <detailsIn response to : i think this topic better fits SIG Node. /sig node /remove-sig apps </details\nI think this is a feature request, not support, so I changed labels. On its face it SEEMS reasonable, but I am not close enough to the details to say. This is definitely sig-node.\nAdding a new pod lifecycle state has been determined to be intractable in the past. Is the proposed change keeping the pod in !Ready until the first success from ?\nWhere do you usually discuss this? Just wondering. Yes, I want that pod considered not ready until will not be successful. If readiness probe doesn't present then a pod can become ready. How can a pod be ready if it is not running?\nhow long wait?\nLooking at this issue, I can confirm it, at least superficially - a pod with a perma-failing is \"ready\" if there is no readinessGate defined and \"not ready\" if it is defined. The question I have is whether we think that is \"correct\" or not? Initially I thought it was correct, but the more I think about it the less convinced I am. If I have defined a startupProbe and it is not passing, my app should not be ready. Does anyone disagree?\nAlso, the app should not be ready in status. It's funny, but without a readiness probe, pods in the final state have the status ready and accept requests. This is unexpected.\nWhether a pod is ready while terminating is an entirely different question, IMO.", "commid": "kubernetes_issue_89995", "tokennum": 488}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e90c8857203276bd85e12e141fd54e14252db1505451c7abcf7dac1888ac107f", "query": "started = !exists } podStatus.ContainerStatuses[i].Started = &started <ins> if started { var ready bool if c.State.Running == nil { ready = false } else if result, ok := m.readinessManager.Get(kubecontainer.ParseContainerID(c.ContainerID)); ok { ready = result == results.Success } else { // The check whether there is a probe which hasn't run yet. _, exists := m.getWorker(podUID, c.Name, readiness) ready = !exists } podStatus.ContainerStatuses[i].Ready = ready } </ins> } // init containers are ready if they have exited with success or if a readiness probe has // succeeded.", "positive_passages": [{"docid": "doc-en-kubernetes-3f629dda069dd58c9ce26e66996c26ea4a1a35ac59c48a136ee3c51de61527c3", "text": "Apps that server network traffic probably need to \"drain\" and to do that they need to stay \"ready\" for a while as upstream LBs de-program. Let's not conflate issues, please.\nThe fix seems simple - lets see what CI says.\nSorry, I don't spend much time on slack... you could have checked the release notes in 1.18 ;-) Tim's fix seems good, thanks!\n/reopen Until we merge all related PRs...\nReopened this issue. <detailsIn response to : /reopen Until we merge all related PRs... 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\nAll merged. /close\nClosing this issue. <detailsIn response to : All merged. /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", "commid": "kubernetes_issue_89995", "tokennum": 213}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e939fb5debdbea59b360333b507c66c1b4c13623ecc0a2507d06f088af51575d", "query": "%.png: %.seqdiag $(FONT) seqdiag --no-transparency -a -f '$(FONT)' $< <ins> # Build the stuff via a docker image .PHONY: docker docker: docker build -t clustering-seqdiag . docker run --rm clustering-seqdiag | tar xvf - docker-clean: docker rmi clustering-seqdiag || true docker images -q --filter \"dangling=true\" | xargs docker rmi fix-clock-skew: boot2docker ssh sudo date -u -D \"%Y%m%d%H%M.%S\" --set \"$(shell date -u +%Y%m%d%H%M.%S)\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-3871d24647a528f2ff7df25634241fd3cde165662602f0e95a0cba53fe987aee", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug /priority failing-test /area test-infra What happened: job is failing. See https://k8s- https://k8s- https://k8s- https://k8s- What you expected to happen: test should pass\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/assign\nReiterating the mentions to trigger a notification: <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\nI'm guessing that something got messed up in the bazel cache when reverting from 0.5.2 to 0.4.5. I'm not sure how best to fix.\nHow about updating everything to bazel 0.5.3 at once? I know you're trying to do a step-by-step approach to avoid breakages, but I suspect it will be cheaper to just deal with a brief outage while we update? (aka update the bazelbuild image to 0.5.3 and then merge your PR with updated and working BUILD rules?)\nthere's at least one other issue I've discovered with the latest go rules - the binary no longer works, due to changes introduced in that might be arguably better (at least everything still builds?), though it's frustrating that it makes things more broken in a different way.", "commid": "kubernetes_issue_49844", "tokennum": 434}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e93d0b607c85b6c2cf41ca79c8e8b072dd18c0f2c8077a7581a376f70d360499", "query": "\"log\" \"os\" \"os/exec\" <ins> \"os/signal\" </ins> \"path/filepath\" \"strings\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-91b918bf4349bc4d86d996ff7ec289a620469d416a95bd3acf270a016c4f134a", "text": "Once e2e tests are running, the tests keep running even if I press and exit the process that controls the TTY. But the tests actually keep running in the background and they keep printing stuff on a shell prompt which has already returned and thereby clobbering the STDOUT\n/assign\nGitHub didn't allow me to assign the following users: oomichi. Note that only can be assigned. <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", "commid": "kubernetes_issue_43051", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e947bfcf2f8deaa80fe9692e390f301c68cf78c3bc9378dd21c217897a8e77f6", "query": "}) It(\"should have all expected certs on the master\", func() { <del> if testContext.Provider != \"gce\" && testContext.Provider != \"gke\" { </del> <ins> if !providerIs(\"gce\", \"gke\") { </ins> By(fmt.Sprintf(\"Skipping MasterCerts test for cloud provider %s (only supported for gce and gke)\", testContext.Provider)) return }", "positive_passages": [{"docid": "doc-en-kubernetes-5702d542be386cac9e4333778515fd94620fcdb52c66d8dfc11487da78971dda", "text": "I noticed while running e2e tests locally that some tests were apparently being incorrectly skipped: I checked, and this is also true for our Jenkins runs. Currently it looks like and have this bug, though only the former actually skips the test, I think. The issue appears to be that the code inside the top-level in these files is being run before the testContext struct is filled out (and before is even called), and so testContext.Provider is empty. I'm not immediately sure what the proper fix is; I'm also worried that there might be other things broken by the fact that these blocks are called before initialization is complete. We also probably investigate if there is a better way to mark these tests as skipped; right now, there's no indication in the test report (, Jenkins test report, etc) that these tests were skipped.\nI merged and which tried to disable these tests for non-{gke,gce} but apparently didn't follow-up and verify that they were still running on our platforms. /cc\nSeems easy enough to fix. I'll have a PR out to fix this before Monday.", "commid": "kubernetes_issue_7008", "tokennum": 242}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e982dd843baa057965164342224d3d04ce5f0674d66fad57d31bab049d633599", "query": "if ds.Status.DesiredNumberScheduled == desiredNumberScheduled && ds.Status.CurrentNumberScheduled == currentNumberScheduled && ds.Status.NumberMisscheduled == numberMisscheduled { return nil } var updateErr, getErr error for i := 0; i <= StatusUpdateRetries; i++ { ds.Status.DesiredNumberScheduled = desiredNumberScheduled", "positive_passages": [{"docid": "doc-en-kubernetes-b0a441a371f8db864bebc11c7303837af71a86244bb0f50ec81fe1d8a09d5c71", "text": "The test is in flaky suite and no one seems to care. We need an owner for this test. cc Last failure log:\ndo you think you can take a look at this?\nThis is happening because of a bad assumption. The assumption is: if the reflector's store is consistent with etcd, the store given back to clients of the framework.Controller is too. I'd really like a general fix applicable to all controllers for this problem, but fixing it just for the RCs is pretty easy. In more detail: This function reports when the reflector has listed from apiserver. But the store given to the reflector is the fifo of the framework.Controller. The store given back to the caller is still not consistent, and will not be till the framework.Controller puts all the objects from the fifo into the client state store (). The rc specific fix: Before starting the rc manager, seed the expectations store with an expectation like {rc:foo, adds: foo.Status.Replicas, deletes:0}. This will wait for status.Replicas number of ADD events till a timeout. The general fix: Somehow expose this through framework.Controller.HasSynced (clients don't care about the fifo anyway, shouldn't it just be an implementation detail?) ideas? cc'ing people who have written controllers that might be interested I don't think this (and generally anything flaky for 1 release) is a p0, I can fix it if you don't mind dealing with the flakes till I've cleared things off my plate. I'd be more than happy to review a fix.\nWell, it's a P0 because test is flaky. E.g last run:\n- did you have chance to look into it?\nThe \"DaemonRestart\" tests are still labeled at . I will send a PR to promote them.\nare you still planning to send aPR to promote the DaemonRestart tests out of flaky? I think this is the right thing to do.\nAck; sorry, I lost this in the muck.", "commid": "kubernetes_issue_17829", "tokennum": 444}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e98edab55a2ef7d5ee9d7c7ed2e5d05e3fe8bce564797f44ed69b69e9ecfc026", "query": "ObjectMeta: metav1.ObjectMeta{ Name: string(kl.nodeName), Labels: map[string]string{ <del> metav1.LabelHostname:       kl.hostname, metav1.LabelOS:             goruntime.GOOS, metav1.LabelArch:           goruntime.GOARCH, metav1.LabelFluentdDsReady: \"true\", </del> <ins> metav1.LabelHostname: kl.hostname, metav1.LabelOS:       goruntime.GOOS, metav1.LabelArch:     goruntime.GOARCH, </ins> }, }, Spec: v1.NodeSpec{", "positive_passages": [{"docid": "doc-en-kubernetes-3936c52aacccf581fb5174635de31acc9a85b981ebc339b83016fc7b6087f92b", "text": "PR introduced an annotation for fluentd migration from static pod to the daemonset to avoid two instances of fluentd on a single node during the transition stage. I didn't read the pr carefully, but based on the code at , every node object has one label be default: \"\". I think this is wrong. 1) Not everyone use fluentd as the logging agent. 2) It is hard-coded in Kubelet code as part of kubeletnodestatus. No matter running fluentd as a static pod or a daemonset on the node, Kubelet shouldn't treat it different from other pods. The right approach is introducing an external controller to apply this cloud-provider / kubernetes vendor (i.e. GKE) specific label to the node. cc/\nThe string \"fluentd\" shouldn't appear anywhere in our code. Please remove it ASAP.\nAbsolutely agree with you, thanks for bringing this up! Is it possible to apply labels to the node as part of the node startup script/salt?\nTo clarify, I'm thinking about possible ways to provide a fix for that ASAP. Writing external controller is a best solution, but here we have a release coming and this label is intended to be only a temporary measure to perform upgrade from using fluentd as static pods to using daemon set.\nThere are many ways to achieve this outside the core system. But I believe GKE already has an existing mechanism to add this kind of labels to the node, and the consistency is important for GKE management. cc/\nOK, thanks! However, I believe we should be sure not to break everyone's upgrade process, i.e. after master upgrade to 1.6 on any platform, there should be only one fluentd agent on each node. I propose changing the configure scripts and salt to set up needed labels in kubelet's flag (). WDYT?\nIt seems to me like upgrades could survive without the explicit dependency on fluentd: I'm not sure if upgrades call initialNode or not, my own ignorance ? If they do, and this is removed, can't an external controller just do the work of re--adding that label if its dropped?\nthanks for raising this. Let's sync f2f\ncc\nWDYT about exposing kubelet version as a label and have a selector in fluentd ds config targeting version 1.6+?", "commid": "kubernetes_issue_42840", "tokennum": 508}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e98edab55a2ef7d5ee9d7c7ed2e5d05e3fe8bce564797f44ed69b69e9ecfc026", "query": "ObjectMeta: metav1.ObjectMeta{ Name: string(kl.nodeName), Labels: map[string]string{ <del> metav1.LabelHostname:       kl.hostname, metav1.LabelOS:             goruntime.GOOS, metav1.LabelArch:           goruntime.GOARCH, metav1.LabelFluentdDsReady: \"true\", </del> <ins> metav1.LabelHostname: kl.hostname, metav1.LabelOS:       goruntime.GOOS, metav1.LabelArch:     goruntime.GOARCH, </ins> }, }, Spec: v1.NodeSpec{", "positive_passages": [{"docid": "doc-en-kubernetes-4cb16c5ce2a173a3021e859767a51a1df9544dd94429e93c357c1a133ef72828", "text": "and I talked about this issue a bit for migrating kube-proxy. One idea we came up with was that of running a controller that will identify kubelet versions and apply taints to nodes running static pods. The daemonset version would not tolerate that taint and that way we keep daemon set pods off of nodes running static pods. Have you considered that approach?\nIt doesn't differ from a controller applying labels. I'd like to avoid necessity of introducing such controller, since it's not clear what is it's responsibility (generic controller for applying labels on nodes based on some rules? a custom controller just for fluentd purposes). In GKE we can do it on GKE control plane side, but we need a story for open source.\nMove applying labels to startup scripts/salt seems to be the least intrusive and easiest to implement way.\nActually what I proposed in is not an option since nodeSelector in PodSpec is old style selector.\nI'm not a big fan of approach with salt, but it seems there is no better option.\nRe: Instead of exposing Kubelet version as a label, why not using field selector. Kubelet version is part of NodeStatus already. I just simply don't want to have a duplicate info for the same object.\nis it possible to schedule based on fieldselector? I'm only aware of using field selector while listing objects.\nAlso node-labels option is in alpha\nBut it's present since 1.2 What is the status of this flag? Can we use it for fluentd purposes or better avoid this?\nMaybe it does make sense to implement a temporary ad-hoc controller? It's the easiest to deploy solution, just another in fluentd addon.\nI know. It totally doesn't make sense to introduce anything custom. I'll use just the flag. It's rather hacky but unfortunately I can't see anything better.\nCool thing about controller is that you can deploy it into any cluster and it will work, with CA also. You don't have to set up your node labels manually then or restart the cluster.\nThere is a number of open question with having a new controller: it run on the master or a node? we guarantee that it will be always running? it have any resource requirements? I'd like to avoid discussing it right before the release.\nHaving a controller will help with kube-proxy transition too in the future.", "commid": "kubernetes_issue_42840", "tokennum": 507}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e98edab55a2ef7d5ee9d7c7ed2e5d05e3fe8bce564797f44ed69b69e9ecfc026", "query": "ObjectMeta: metav1.ObjectMeta{ Name: string(kl.nodeName), Labels: map[string]string{ <del> metav1.LabelHostname:       kl.hostname, metav1.LabelOS:             goruntime.GOOS, metav1.LabelArch:           goruntime.GOARCH, metav1.LabelFluentdDsReady: \"true\", </del> <ins> metav1.LabelHostname: kl.hostname, metav1.LabelOS:       goruntime.GOOS, metav1.LabelArch:     goruntime.GOARCH, </ins> }, }, Spec: v1.NodeSpec{", "positive_passages": [{"docid": "doc-en-kubernetes-3203f30994cf42c5336d5a6d0dc1585171cc98cff1719959478ccaf13036f1c4", "text": ", Piotr Szczesniak <:\nis this a 1.6 release blocker?\nI think yes. The PR is already sent and approved. I need to fix e2e tests because it doesn't work well with the test infra (e2e tests passes locally). EDIT: I'll do it hopefully today.\nThe PR is ready to be merged and lgtmed. Waiting for approvals.", "commid": "kubernetes_issue_42840", "tokennum": 89}], "negative_passages": []}
{"query_id": "q-en-kubernetes-e9ee9608fdb91aeec05239a76f6e48b01eee0365377fddef30584a03bd4af83b", "query": "expectedPatchDataPattern: `{\"status\":{\"$setElementOrder/conditions\":[{\"type\":\"currentType\"}],\"conditions\":[{\"lastProbeTime\":\"2020-05-13T01:01:01Z\",\"message\":\"newMessage\",\"reason\":\"newReason\",\"type\":\"currentType\"}]}}`, }, { <del> name: \"Should make patch request if pod condition already exists and is identical but nominated node name is different\", </del> <ins> name: \"Should not make patch request if pod condition already exists and is identical and nominated node name is not set\", </ins> currentPodConditions: []v1.PodCondition{ { Type:               \"currentType\",", "positive_passages": [{"docid": "doc-en-kubernetes-0c3eca7956c73a24f455c71a58b712ce183e874d4a3e3eb9b913120c8a8ac10c", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: Conformance - GCE - master (ci-kubernetes-gce-conformance-latest) Which test(s) are failing: [sig-scheduling] SchedulerPreemption [Serial] PreemptionExecutionPath runs ReplicaSets to verify preemption running path [Conformance]Changes Since when has it been failing: 2020-06-08 22:27 PDT Testgrid link: Reason for failure: Regression by Anything else we need to know: /sig scheduling /priority critical-urgent\ncc/ /assign", "commid": "kubernetes_issue_91972", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ea02d2eeb25c105c04b4170af0ea1092cf8aae0815a288347ae3bdb68dd6f017", "query": "MUST match to expected used and total allowed resource quota count within namespace. release: v1.16 file: test/e2e/apimachinery/resource_quota.go <ins> - testname: ResourceQuota, manage lifecycle of a ResourceQuota codename: '[sig-api-machinery] ResourceQuota should manage the lifecycle of a ResourceQuota [Conformance]' description: Attempt to create a ResourceQuota for CPU and Memory quota limits. Creation MUST be successful. Attempt to list all namespaces with a label selector which MUST succeed. One list MUST be found. The ResourceQuota when patched MUST succeed. Given the patching of the ResourceQuota, the fields MUST equal the new values. It MUST succeed at deleting a collection of ResourceQuota via a label selector. release: v1.25 file: test/e2e/apimachinery/resource_quota.go </ins> - testname: ResourceQuota, quota scope, BestEffort and NotBestEffort scope codename: '[sig-api-machinery] ResourceQuota should verify ResourceQuota with best effort scope. [Conformance]'", "positive_passages": [{"docid": "doc-en-kubernetes-8218004df321e49189cb8c22922209b0129dd124df9f46401769a8d8c1aa8714", "text": "[x] test approval issue : [x] test pr : 7 July 2022 [X] two weeks soak end date : 21 July 2022 [X] test promotion pr : According to this APIsnoop query, there is still some remaining ResourceQuota endpoints which are untested. The Status endpoints will be addressed in another test. listCoreV1ResourceQuotaForAllNamespacespatchCoreV1NamespacedResourceQuotadeleteCoreV1CollectionNamespacedResourceQuota Using a number of existing e2e test practices a new has been created for three ResourceQuota endpoints. The e2e logs for this test are listed below. This query shows the endpoints hit within a short period of running the e2e test If a test with these calls gets merged, test coverage will go up by 3 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance\n/triage accepted\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_109682", "tokennum": 223}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ea5a2d0c99fb4a52ad1f09f3a48ba611004073fe8bab84900eb3c750f1f236b1", "query": "expectedErr:     true, }, { <del> desc:        \"correct LUN and no error shall be returned if everything is good\", vmList:      map[string]string{\"vm1\": \"PowerState/Running\"}, nodeName:    \"vm1\", existedDisk: compute.Disk{Name: to.StringPtr(\"disk-name\"), DiskProperties: &compute.DiskProperties{Encryption: &compute.Encryption{DiskEncryptionSetID: &diskEncryptionSetID, Type: compute.EncryptionAtRestWithCustomerKey}}, Tags: testTags}, </del> <ins> desc:     \"correct LUN and no error shall be returned if everything is good\", vmList:   map[string]string{\"vm1\": \"PowerState/Running\"}, nodeName: \"vm1\", existedDisk: compute.Disk{Name: to.StringPtr(\"disk-name\"), DiskProperties: &compute.DiskProperties{ Encryption: &compute.Encryption{DiskEncryptionSetID: &diskEncryptionSetID, Type: compute.EncryptionAtRestWithCustomerKey}, DiskSizeGB: to.Int32Ptr(4096), }, Tags: testTags}, </ins> expectedLun: 1, expectedErr: false, },", "positive_passages": [{"docid": "doc-en-kubernetes-3186f04d894d2e98a9b770821be5e33542dd055d445ea6f78bf8e42e85bb59f7", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: there is a disk resize scenario: In the beginning, it\u2019s 3TiB with cachingMode=ReadOnly, and then disk detached, resized to 4TiB, then user find they could not attach that disk back to any agent node, I think that\u2019s a bug we need to fix. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others: /kind bug /assign /priority important-soon /sig cloud-provider /area provider/azure\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_95465", "tokennum": 311}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ea60322a8e212f77fed6de1fd60f1e013453ac39c706015c8aeff42e6564ab56", "query": "sanitizedSpecVolID := kstrings.EscapeQualifiedNameForDisk(specVolID) return path.Join(host.GetVolumeDevicePluginDir(csiPluginName), sanitizedSpecVolID, \"data\") } <ins> // hasReadWriteOnce returns true if modes contains v1.ReadWriteOnce func hasReadWriteOnce(modes []api.PersistentVolumeAccessMode) bool { if modes == nil { return false } for _, mode := range modes { if mode == api.ReadWriteOnce { return true } } return false } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-91422af253157e56510335693740251e17b7c26d119e77363e85ed4155980546", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: What happened: fsgroup is only intended for RWO volumes because it recursively changes the permissions of all the directories in the volume. This can cause problems for nfs-type volumes because multiple pods could access the same volume and have the permissions changed out from underneath. What you expected to happen: Determine whether or not the plugin supports fsgroup either via: access mode. This is still a bit ambiguous for nfs volume types, that can theoretically support rwo, especially since Kubernetes does not do any sort of access mode enforcement. a new csi capability\nCC\nAre you saying that CSI internal driver should check driver capability for RWO, if supported, only then apply value ? What would the be ?\nYes one possible way is to infer fsgroup is supported for all rwo volumes, which may not be true? Like a nfs volume technically supports rwo but not fsgroup. So the other option is to make it a new CSI capability. I'm not sure exactly sure how best to describe it though, maybe something about volume ownership management.\nWill it work if is not set then don't chown the ownership? I would think that for shared file system types(nfs, glusterfs) - won't be set. For raw block storage too - I think we shouldn't have to do this.\nwhat do you mean by ? Shouldnt have to solve this issue ?\nI meant - which is obvious. I just meant that the entire mechanism of changing ownership of files should apply only to volume types with block storage filesystems. I am just wondering if we can get away with detecting fsType and not have to introduce new capability in CSI.\nagreed, do not map well to current csi.Capabilities enums which makes it hard to determine RWO when mounting. Perhaps, instead of a new capability, we revisit the existing capabilities to see if there are any way RWO can be reliably inferred from returned capabilities.", "commid": "kubernetes_issue_66323", "tokennum": 463}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ea60322a8e212f77fed6de1fd60f1e013453ac39c706015c8aeff42e6564ab56", "query": "sanitizedSpecVolID := kstrings.EscapeQualifiedNameForDisk(specVolID) return path.Join(host.GetVolumeDevicePluginDir(csiPluginName), sanitizedSpecVolID, \"data\") } <ins> // hasReadWriteOnce returns true if modes contains v1.ReadWriteOnce func hasReadWriteOnce(modes []api.PersistentVolumeAccessMode) bool { if modes == nil { return false } for _, mode := range modes { if mode == api.ReadWriteOnce { return true } } return false } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-e4259f265013a5d1d3262148ae5650fa802161db5ab8c8ccc1d210e68217a7fd", "text": "Currently, this is what the code is doing which we knew needed to be revisited:\nUsers may not fully understand what fsgroup is and set it anyway, or a default psp with some fsgroup may be defined in which it will automatically be set on all pods. The first case we can attribute to user error, but the second case may not have a good workaround and could cause permission issues on rwx volumes. So I think we do need to solve this.\nYes, agreed this has to be solved. As you pointed out user error or improperly configured PSP can set value that does not match the correct attribute, causing permission issues. Here is what I think can be done without new CSI capabilities: , then do not apply fsgroup then: , apply fsgroup , do not apply fsgroup to void stated issue then: , apply fsgroup I think that may help deduce when to apply fsgroup.\nIf mount reference count <= 1, apply fsgroup If mount reference count 1, do not apply fsgroup to void stated issue A RWM volume (say NFS) can be mounted on multiple nodes. Do you have reliable count of mounts across all nodes?\nIn addition, that would be a change in semantics to how we support rwx volumes today. If we don't have a new CSI capability, then I think the best course of action is to only apply fsgroup for RWO volumes. Some questions remain: Do all RWO volumes support fsgroup? RWX is a superset of RWO. So if a user requests a RWO volume, it could still be satisfied by a RWX volume type. Can we detect this and still not apply the fsgroup even though the volume capability will say RWO?\nIf there's not a reliable way to enumerate node mounts (thinking about it, for CSI external drivers, the answer is NO). Theres is no reliable way to have k8s autocorrect a bad fsgroup/PV.AccessMode combo. So we would have to rely on the config provided by user/admin. I have come to similar conclusion as -- mainly, apply fsgroup only to volumes with access modes. The other k8s specified access modes, , cannot be reliably applied.", "commid": "kubernetes_issue_66323", "tokennum": 487}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ea60322a8e212f77fed6de1fd60f1e013453ac39c706015c8aeff42e6564ab56", "query": "sanitizedSpecVolID := kstrings.EscapeQualifiedNameForDisk(specVolID) return path.Join(host.GetVolumeDevicePluginDir(csiPluginName), sanitizedSpecVolID, \"data\") } <ins> // hasReadWriteOnce returns true if modes contains v1.ReadWriteOnce func hasReadWriteOnce(modes []api.PersistentVolumeAccessMode) bool { if modes == nil { return false } for _, mode := range modes { if mode == api.ReadWriteOnce { return true } } return false } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-d8c35fcb948670df81783d48737c49dba78eee3bd98e80f83b95ce53a92518be", "text": "Even if we were to introduce additional plugin capabilities that the CO can query (from driver) to find out what modes can be applied, there would still be the possibility of user/admin mis-configuration. Probably not, Is this where you think an additional capability would help ( ) That is a good point. Can't think of a way to detect/guess RWX when RWO is specified, this without the driver providing that info. Can we adopt the rule until we decide what capabilities would look like ?\nI will just try to summarize the conversation from Slack. We can safely assume that only applies to block storage type with file system on top of it. So for all - volumes that need to have called MUST have a file system() on them. Is that assumption correct? If it is - can we not use presence of field or we can query the local volume for fs type (like how we query selinux relabelling capability) and call only when - volume is RW and has a valid block storage file system type. Will this not solve our use case? EDIT: renamed to .\nWe'll need to make it clear that is only for block-based storage systems, and the field cannot be reused for some multi-protocol file server (ie, nfsv3, nfsv4, smb, etc). For that case, then the plugin will need to expose its own new storageclass parameter + volume attribute to specify protocol.\nCan we not use to get fsType - and use that information for calling ? It may be problematic to rely entirely on present inside csi source.\nthe only problem with is that in CSI volume info is intentionally opaque to the CSI code inside k8s. All mount logic is delegated to the driver.\nInstead of a new capability or trying to deduce how best to apply fsgroup, why not pass the to the driver and let it decide how to apply it (either as a attribute for the mount or top level request param)? Right now, all mount logic has been delegated to the external CSI driver except for applying permission. Thoughts ?\nthat is true but we can still inspect file system on the mounted path because by the time gets called volume is already mounted. This should be no different than how selinux support is determined. what you think?\nis this approved for 1.12 milestone? Thank you for working on this,\nstill discussing how best to approach this.", "commid": "kubernetes_issue_66323", "tokennum": 506}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ea60322a8e212f77fed6de1fd60f1e013453ac39c706015c8aeff42e6564ab56", "query": "sanitizedSpecVolID := kstrings.EscapeQualifiedNameForDisk(specVolID) return path.Join(host.GetVolumeDevicePluginDir(csiPluginName), sanitizedSpecVolID, \"data\") } <ins> // hasReadWriteOnce returns true if modes contains v1.ReadWriteOnce func hasReadWriteOnce(modes []api.PersistentVolumeAccessMode) bool { if modes == nil { return false } for _, mode := range modes { if mode == api.ReadWriteOnce { return true } } return false } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-5cbdf2214fb613203f89164533ba44fdfe78b2afafa2ed81aceb81e111086f6f", "text": "It would be a 1.12.\n[MILESTONENOTIFIER] Milestone Issue: Up-to-date for process <details open<summaryIssue Labels</summary- : Issue will be escalated to these SIGs if needed. : Never automatically move issue out of a release milestone; continually escalate to contributor and SIG through all available channels. : Fixes a bug discovered during the current release. </details<details<summaryHelp</summary<ul<li<a href=\"\"Additional instructions</a</li<li<a href=\"\"Commands for setting labels</a</li</ul</details\nApproved for 1.12\nBased on previous post, this is a summary: If then is not applied (because it could be an indication of a nonblock fs, or error) Done is provided if fstype is invalid Done if fstype is valid and then apply fsgroup logic else ignore fsGroup Done\n- any updates on ?\nWaiting for a review and approval.\nyou have a outstanding comment on the PR. Can you please answer that?\nHow does this approach relate to inline CSI volumes? There's no PersistentVolume involved, and hence no way to specify an access mode. , but my driver ignores it (always using tmpfs). I considered having my CSI driver read the mounting pod's spec to see if it has a security context with \"fsGroup\" set, since that detail is not supplied to the driver, as . My goal is to have the volume mounted with the files on it readable by the container's user, but there's no way for my driver to know who that user will be. Am I supposed to just use 0444 for the ownership bits, to allow everyone to read the files?", "commid": "kubernetes_issue_66323", "tokennum": 377}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ea666026182ccfccc6a19616d22f71b8cbd9d8ea62fdfd2e828b408581b8a1a0", "query": "new_storage_version=${test_data[5]} kube::log::status \"Verifying ${resource}/${namespace}/${name} has updated storage version ${new_storage_version} in etcd\" <del> curl -s http://${ETCD_HOST}:${ETCD_PORT}/v2/keys/registry/${resource}/${namespace}/${name} | grep ${new_storage_version} </del> <ins> curl -s http://${ETCD_HOST}:${ETCD_PORT}/v2/keys/${ETCD_PREFIX}/${resource}/${namespace}/${name} | grep ${new_storage_version} </ins> done killApiServer", "positive_passages": [{"docid": "doc-en-kubernetes-74ce4fea7378dc634ccb83a22893b6255fa243ed3e0b4f0e57320154ecc66caf", "text": "removed this test. We need to continue testing this. This wasn't about testing upgrades, the prefix has nothing to do with upgrades. It's just there so people can share etcd. We maybe don't need to double everything but we do need to make sure that keeps working.\nTo be honest - I think that what we was testing before didn't give us completely any information. We didn't testing what information we are storing in etcd and where. That said, if we had a hardcoded prefix somewhere in our code, we wouldn't discover it at all, and those tests would still be passing. We should have a test that is directly checking etcd contents. I think it should be possible to write a simple unit test for it. Will try to put something together next week.", "commid": "kubernetes_issue_26489", "tokennum": 167}], "negative_passages": []}
{"query_id": "q-en-kubernetes-eb1fbe3b344397ccfa5bf355e370217fc3d5d85b3b97f7ed23e5cfd2f73d9472", "query": "dockertypes \"github.com/docker/engine-api/types\" ) <ins> // These two functions are OS specific (for now at least) func updateHostConfig(config *dockercontainer.HostConfig) { } func DefaultMemorySwap() int64 { return -1 } </ins> func getContainerIP(container *dockertypes.ContainerJSON) string { return \"\" }", "positive_passages": [{"docid": "doc-en-kubernetes-2c477631a31f290ae271a7ca0a83a97399cbf63c4cfd883674b6ddce7387fc19", "text": "What happened: Latest kubelet + Windows Docker version 1.14.0-dev refused to start any containers, error output: \"invalid option: Windows does not support MemorySwap\" How to reproduce it (as minimally and precisely as possible): It's always reproducible with Windows Docker 1.14.0-dev + latest kubelet code base. Anything else do we need to know: It didn't happen for Windows Docker 1.12.2-cs2-ws-beta. The reason behind the issue was because new code was for Windows Docker to check Resources parameters, it doesn't accept a non-zero value for MemorySwap: But kubelet was default to set an unlimited (-1) value. The issue was gone in my setup after applied a private fix to disable MemorySwap by set it to zero for Windows.", "commid": "kubernetes_issue_39003", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-eb264da187d63664252e85e6f56b93286205dae3ddddd946f23016a1bca0bb36", "query": "} base := host hostURL, err := url.Parse(base) <del> if err != nil { return nil, \"\", err } if hostURL.Scheme == \"\" || hostURL.Host == \"\" { </del> <ins> if err != nil || hostURL.Scheme == \"\" || hostURL.Host == \"\" { </ins> scheme := \"http://\" if defaultTLS { scheme = \"https://\"", "positive_passages": [{"docid": "doc-en-kubernetes-f8d2143077108332ac1fc56464c0f656ab79e989e202f2c3813e992956fd19da", "text": "Hi, I have been trying to run api-server as an standalone service along with etcd. I am passing etcd-servers and cluster-ip-range as arguments, here is the error I am getting: etcd servers are up and running on that address. Any leads as to how to resolve this? TIA.\nThis is only happening with go1.8 version, not really sure what is causing issue while parsing the URI.\nCaused by this change i believe - CC as 1.8beta1 is being worked on here -\nThanks\nI'm getting this exact issue using Kubernetes 1.5.7 and Go 1.8.3. Reverting to Go 1.7 seems to resolve it. This happened after updating a Go 1.7-compiled 1.4.8 Kubernetes cluster to 1.5.7, not sure if that's a corner case. For reference, my stack trace:", "commid": "kubernetes_issue_38380", "tokennum": 196}], "negative_passages": []}
{"query_id": "q-en-kubernetes-eb2fb2b99a42f440fa5477b0aa260ea8fde4068f05afeab9e58c44a24efdcb42", "query": "package main import ( <ins> goflag \"flag\" </ins> \"fmt\" \"math/rand\" \"os\" \"time\" <ins> \"github.com/spf13/pflag\" </ins> utilflag \"k8s.io/apiserver/pkg/util/flag\" \"k8s.io/apiserver/pkg/util/logs\" \"k8s.io/kubernetes/cmd/kube-proxy/app\"", "positive_passages": [{"docid": "doc-en-kubernetes-5044536d87edb25c665421bf3dc4b536a0586e8213d754dc6188da659a17c1aa", "text": "There are no sig labels on this issue. Please add a sig label. <detailsA sig label can be by either: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. See the . The in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals 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\nprobably caused by\nCould be a clash between these two?\ncc\nI still see the issue with local-cluster on the latest master: F0225 17:06:49. ] error: v1alpha1.KubeProxyConfiguration: FeatureGates: ReadMapCB: expect { or n, but found \", error found in byte of ......\nlooks like that's another issue, can you please file a new bug? with more logs? this one was about none of the hyperkube based processes starting up.\nwill do as it is also broke container kube-proxy as well. Same type of error.", "commid": "kubernetes_issue_60378", "tokennum": 274}], "negative_passages": []}
{"query_id": "q-en-kubernetes-eb48251297b2ad77b0249236beb9681e9436ecfca440d7d8e68888932ae9779d", "query": "\"context\" \"errors\" \"fmt\" <ins> \"net\" \"sync\" </ins> \"time\" <del> v1 \"k8s.io/api/core/v1\" resourceapi \"k8s.io/api/resource/v1alpha3\" apierrors \"k8s.io/apimachinery/pkg/api/errors\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/fields\" </del> <ins> \"google.golang.org/grpc\" \"google.golang.org/grpc/connectivity\" \"google.golang.org/grpc/credentials/insecure\" </ins> utilversion \"k8s.io/apimachinery/pkg/util/version\" <del> \"k8s.io/apimachinery/pkg/util/wait\" \"k8s.io/client-go/kubernetes\" </del> \"k8s.io/klog/v2\" <del> \"k8s.io/kubernetes/pkg/kubelet/pluginmanager/cache\" </del> <ins> drapb \"k8s.io/kubelet/pkg/apis/dra/v1alpha4\" </ins> ) <del> // defaultClientCallTimeout is the default amount of time that a DRA driver has // to respond to any of the gRPC calls. kubelet uses this value by passing nil // to RegisterPlugin. Some tests use a different, usually shorter timeout to // speed up testing. // // This is half of the kubelet retry period (according to // https://github.com/kubernetes/kubernetes/commit/0449cef8fd5217d394c5cd331d852bd50983e6b3). const defaultClientCallTimeout = 45 * time.Second // RegistrationHandler is the handler which is fed to the pluginwatcher API. type RegistrationHandler struct { // backgroundCtx is used for all future activities of the handler. // This is necessary because it implements APIs which don't // provide a context. backgroundCtx context.Context kubeClient    kubernetes.Interface getNode       func() (*v1.Node, error) } </del> <ins> // NewDRAPluginClient returns a wrapper around those gRPC methods of a DRA // driver kubelet plugin which need to be called by kubelet. The wrapper // handles gRPC connection management and logging. Connections are reused // across different NewDRAPluginClient calls. func NewDRAPluginClient(pluginName string) (*Plugin, error) { if pluginName == \"\" { return nil, fmt.Errorf(\"plugin name is empty\") } </ins> <del> var _ cache.PluginHandler = &RegistrationHandler{} // NewPluginHandler returns new registration handler. // // Must only be called once per process because it manages global state. // If a kubeClient is provided, then it synchronizes ResourceSlices // with the resource information provided by plugins. func NewRegistrationHandler(kubeClient kubernetes.Interface, getNode func() (*v1.Node, error)) *RegistrationHandler { handler := &RegistrationHandler{ // The context and thus logger should come from the caller. backgroundCtx: klog.NewContext(context.TODO(), klog.LoggerWithName(klog.TODO(), \"DRA registration handler\")), kubeClient:    kubeClient, getNode:       getNode, </del> <ins> existingPlugin := draPlugins.get(pluginName) if existingPlugin == nil { return nil, fmt.Errorf(\"plugin name %s not found in the list of registered DRA plugins\", pluginName) </ins> } <del> // When kubelet starts up, no DRA driver has registered yet. None of // the drivers are usable until they come back, which might not happen // at all. Therefore it is better to not advertise any local resources // because pods could get stuck on the node waiting for the driver // to start up. // // This has to run in the background. go handler.wipeResourceSlices(\"\") </del> <ins> return existingPlugin, nil } type Plugin struct { backgroundCtx context.Context cancel        func(cause error) </ins> <del> return handler </del> <ins> mutex                   sync.Mutex conn                    *grpc.ClientConn endpoint                string highestSupportedVersion *utilversion.Version clientCallTimeout       time.Duration </ins> } <del> // wipeResourceSlices deletes ResourceSlices of the node, optionally just for a specific driver. func (h *RegistrationHandler) wipeResourceSlices(driver string) { if h.kubeClient == nil { return } ctx := h.backgroundCtx logger := klog.FromContext(ctx) </del> <ins> func (p *Plugin) getOrCreateGRPCConn() (*grpc.ClientConn, error) { p.mutex.Lock() defer p.mutex.Unlock() </ins> <del> backoff := wait.Backoff{ Duration: time.Second, Factor:   2, Jitter:   0.2, Cap:      5 * time.Minute, Steps:    100, </del> <ins> if p.conn != nil { return p.conn, nil </ins> } <del> // Error logging is done inside the loop. Context cancellation doesn't get logged. _ = wait.ExponentialBackoffWithContext(ctx, backoff, func(ctx context.Context) (bool, error) { node, err := h.getNode() if apierrors.IsNotFound(err) { return false, nil } if err != nil { logger.Error(err, \"Unexpected error checking for node\") return false, nil } fieldSelector := fields.Set{resourceapi.ResourceSliceSelectorNodeName: node.Name} if driver != \"\" { fieldSelector[resourceapi.ResourceSliceSelectorDriver] = driver } err = h.kubeClient.ResourceV1alpha3().ResourceSlices().DeleteCollection(ctx, metav1.DeleteOptions{}, metav1.ListOptions{FieldSelector: fieldSelector.String()}) switch { case err == nil: logger.V(3).Info(\"Deleted ResourceSlices\", \"fieldSelector\", fieldSelector) return true, nil case apierrors.IsUnauthorized(err): // This can happen while kubelet is still figuring out // its credentials. logger.V(5).Info(\"Deleting ResourceSlice failed, retrying\", \"fieldSelector\", fieldSelector, \"err\", err) return false, nil default: // Log and retry for other errors. logger.V(3).Info(\"Deleting ResourceSlice failed, retrying\", \"fieldSelector\", fieldSelector, \"err\", err) return false, nil } }) } // RegisterPlugin is called when a plugin can be registered. func (h *RegistrationHandler) RegisterPlugin(pluginName string, endpoint string, versions []string, pluginClientTimeout *time.Duration) error { // Prepare a context with its own logger for the plugin. // // The lifecycle of the plugin's background activities is tied to our // root context, so canceling that will also cancel the plugin. // // The logger injects the plugin name as additional value // into all log output related to the plugin. ctx := h.backgroundCtx </del> <ins> ctx := p.backgroundCtx </ins> logger := klog.FromContext(ctx) <del> logger = klog.LoggerWithValues(logger, \"pluginName\", pluginName) ctx = klog.NewContext(ctx, logger) logger.V(3).Info(\"Register new DRA plugin\", \"endpoint\", endpoint) highestSupportedVersion, err := h.validateVersions(pluginName, versions) </del> <ins> network := \"unix\" logger.V(4).Info(\"Creating new gRPC connection\", \"protocol\", network, \"endpoint\", p.endpoint) // grpc.Dial is deprecated. grpc.NewClient should be used instead. // For now this gets ignored because this function is meant to establish // the connection, with the one second timeout below. Perhaps that // approach should be reconsidered? //nolint:staticcheck conn, err := grpc.Dial( p.endpoint, grpc.WithTransportCredentials(insecure.NewCredentials()), grpc.WithContextDialer(func(ctx context.Context, target string) (net.Conn, error) { return (&net.Dialer{}).DialContext(ctx, network, target) }), ) </ins> if err != nil { <del> return fmt.Errorf(\"version check of plugin %s failed: %w\", pluginName, err) } var timeout time.Duration if pluginClientTimeout == nil { timeout = defaultClientCallTimeout } else { timeout = *pluginClientTimeout </del> <ins> return nil, err </ins> } <del> ctx, cancel := context.WithCancelCause(ctx) </del> <ins> ctx, cancel := context.WithTimeout(context.Background(), time.Second) defer cancel() </ins> <del> pluginInstance := &Plugin{ backgroundCtx:           ctx, cancel:                  cancel, conn:                    nil, endpoint:                endpoint, highestSupportedVersion: highestSupportedVersion, clientCallTimeout:       timeout, </del> <ins> if ok := conn.WaitForStateChange(ctx, connectivity.Connecting); !ok { return nil, errors.New(\"timed out waiting for gRPC connection to be ready\") </ins> } <del> // Storing endpoint of newly registered DRA Plugin into the map, where plugin name will be the key // all other DRA components will be able to get the actual socket of DRA plugins by its name. if draPlugins.add(pluginName, pluginInstance) { logger.V(1).Info(\"Already registered, previous plugin was replaced\") } return nil </del> <ins> p.conn = conn return p.conn, nil </ins> } <del> func (h *RegistrationHandler) validateVersions( pluginName string, versions []string, ) (*utilversion.Version, error) { if len(versions) == 0 { return nil, errors.New(\"empty list for supported versions\") } </del> <ins> func (p *Plugin) NodePrepareResources( ctx context.Context, req *drapb.NodePrepareResourcesRequest, opts ...grpc.CallOption, ) (*drapb.NodePrepareResourcesResponse, error) { logger := klog.FromContext(ctx) logger.V(4).Info(\"Calling NodePrepareResources rpc\", \"request\", req) </ins> <del> // Validate version newPluginHighestVersion, err := utilversion.HighestSupportedVersion(versions) </del> <ins> conn, err := p.getOrCreateGRPCConn() </ins> if err != nil { <del> // HighestSupportedVersion includes the list of versions in its error // if relevant, no need to repeat it here. return nil, fmt.Errorf(\"none of the versions are supported: %w\", err) } existingPlugin := draPlugins.get(pluginName) if existingPlugin == nil { return newPluginHighestVersion, nil </del> <ins> return nil, err </ins> } <del> if existingPlugin.highestSupportedVersion.LessThan(newPluginHighestVersion) { return newPluginHighestVersion, nil } return nil, fmt.Errorf(\"another plugin instance is already registered with a higher supported version: %q < %q\", newPluginHighestVersion, existingPlugin.highestSupportedVersion) } // DeRegisterPlugin is called when a plugin has removed its socket, // signaling it is no longer available. func (h *RegistrationHandler) DeRegisterPlugin(pluginName string) { if p := draPlugins.delete(pluginName); p != nil { logger := klog.FromContext(p.backgroundCtx) logger.V(3).Info(\"Deregister DRA plugin\", \"endpoint\", p.endpoint) // Clean up the ResourceSlices for the deleted Plugin since it // may have died without doing so itself and might never come // back. go h.wipeResourceSlices(pluginName) return } </del> <ins> ctx, cancel := context.WithTimeout(ctx, p.clientCallTimeout) defer cancel() </ins> <del> logger := klog.FromContext(h.backgroundCtx) logger.V(3).Info(\"Deregister DRA plugin not necessary, was already removed\") </del> <ins> nodeClient := drapb.NewNodeClient(conn) response, err := nodeClient.NodePrepareResources(ctx, req) logger.V(4).Info(\"Done calling NodePrepareResources rpc\", \"response\", response, \"err\", err) return response, err </ins> } <del> // ValidatePlugin is called by kubelet's plugin watcher upon detection // of a new registration socket opened by DRA plugin. func (h *RegistrationHandler) ValidatePlugin(pluginName string, endpoint string, versions []string) error { _, err := h.validateVersions(pluginName, versions) </del> <ins> func (p *Plugin) NodeUnprepareResources( ctx context.Context, req *drapb.NodeUnprepareResourcesRequest, opts ...grpc.CallOption, ) (*drapb.NodeUnprepareResourcesResponse, error) { logger := klog.FromContext(ctx) logger.V(4).Info(\"Calling NodeUnprepareResource rpc\", \"request\", req) conn, err := p.getOrCreateGRPCConn() </ins> if err != nil { <del> return fmt.Errorf(\"invalid versions of plugin %s: %w\", pluginName, err) </del> <ins> return nil, err </ins> } <del> return err </del> <ins> ctx, cancel := context.WithTimeout(ctx, p.clientCallTimeout) defer cancel() nodeClient := drapb.NewNodeClient(conn) response, err := nodeClient.NodeUnprepareResources(ctx, req) logger.V(4).Info(\"Done calling NodeUnprepareResources rpc\", \"response\", response, \"err\", err) return response, err </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-e1c6f7407b346df6fb6212f23a2f930e04198e198bb03b9cff5041967802082d", "text": "The PR above moved everything related to into because that was where most of the code already was, but didn't renamed the files to avoid a larger diff and merge conflicts. Once is merged, we can do the renaming. Code clarity. /sig node\n/triage accepted /priority important-soon\n/assign\na PR can be created for this now.\nwill do", "commid": "kubernetes_issue_125924", "tokennum": 75}], "negative_passages": []}
{"query_id": "q-en-kubernetes-eb6be1e6a4215f41028aae75f55bf927c3d8320bcade944c5e0861ad1e7b09de", "query": "}) It(\"should write files of various sizes, verify size, validate content\", func() { <del> fileSizes := []int64{1 * framework.MiB, 100 * framework.MiB, 1 * framework.GiB} </del> <ins> fileSizes := []int64{fileSizeSmall, fileSizeMedium, fileSizeLarge} </ins> err := testVolumeIO(f, cs, config, volSource, &podSec, testFile, fileSizes) Expect(err).NotTo(HaveOccurred()) })", "positive_passages": [{"docid": "doc-en-kubernetes-540712d0b27ee7f52d7d02bd3719013304c1ce42c6b5d8b93c3ee3671a9c1c7c", "text": "The \"Volume plugin streaming [Slow] NFS should write files of various sizes, verify size, validate content\" e2e test is failing on our 2k-node gce clusters (https://k8s-) with the following error: cc\nCould you take a look into it or reassign as apt? This is part of the correctness suite and large cluster tests are release-blocking.\n/assign\nis this run using the kubemark environment? I'll also take a look. It could be that the commands this test needs to execute may not work with kubemark. /assign\ncc\nNo, this is not kubemark. This is on a real 2000-node cluster.\nAlso all other volume-related e2e tests are passing, except this one.\nLooking at the log I see that the nfs test fails trying to verify the test file's content. The test exec's into the nfs client pod and executes: The return code from above is 127. The test then deletes the nfs client pod calling which works. The nfs-server pod is deleted in the AfterEach. For some reason the reported error is 137 but the returned err 127. The same command is exec'd for all of the tested storage plugins so not sure why it's failing just for nfs. Error 127 might be \"command not found\".\nThe other strange thing is that it's only failing in this suite and not the others.\nWhen I look at the kubelet log, I see the exec command coming through: I also see these suspicious kubelet soon afterwards: So I think the grep command is causing the node to run out of memory and get evicted. I think we can fix this either by: Making the grep command more memory efficient. I'm guessing it's reading the whole file into memory or, Make this test Serial so that it doesn't run in parallel with other pods, since it consumes a lot of memory.\nAn unrelated issue, is that the node allocatable feature didn't actually evict the pod. Instead this pod got a system OOM kill. /cc\nrelated to the memcg notifications, not node allocatable. Thanks!\nany theories why we see this only for the nfs-io tests, and not the glusterfs-io test for instance?\nthe gluster test didn't run on this in this suite.", "commid": "kubernetes_issue_51717", "tokennum": 516}], "negative_passages": []}
{"query_id": "q-en-kubernetes-eb6be1e6a4215f41028aae75f55bf927c3d8320bcade944c5e0861ad1e7b09de", "query": "}) It(\"should write files of various sizes, verify size, validate content\", func() { <del> fileSizes := []int64{1 * framework.MiB, 100 * framework.MiB, 1 * framework.GiB} </del> <ins> fileSizes := []int64{fileSizeSmall, fileSizeMedium, fileSizeLarge} </ins> err := testVolumeIO(f, cs, config, volSource, &podSec, testFile, fileSizes) Expect(err).NotTo(HaveOccurred()) })", "positive_passages": [{"docid": "doc-en-kubernetes-fd4ca8cfd935058701597731533334687f2913bf0b9d409a83f3ac801f0182e1", "text": "I'm suspecting that the reason why we didn't see a problem with this test on other suites is that the load could be higher here. I've asked to see if we can reduce the memory usage of the grep call.\npointed out that there are no newlines in the generated file, so when grep is called it could buffer the entire file in memory. Adding a newline at the end of the dd input file should do it.\n/priority critical-urgent\n[MILESTONENOTIFIER] Milestone Labels Complete Issue label settings: sig/scalability sig/storage: Issue will be escalated to these SIGs if needed. priority/critical-urgent: Never automatically move out of a release milestone; continually escalate to contributor and SIG through all available channels. kind/bug: Fixes a bug discovered during the current release. <detailsAdditional instructions available <a href=\"\"here</a</details\nIt seems like even if the generated file is broken up by newlines, grep could still use on the order of hundreds of MB of memory for a 100MiB file (even with the -m1 and -F options). We could check the file line by line, but it would take a long time. A better solution would be to check the MD5 file hash. It's fast and uses little memory. The expected hashes will be hard-coded into the test, and if different file sizes are in the future, a hash needs to be computed and as well.\nThanks a lot for fixing this!\nRef", "commid": "kubernetes_issue_51717", "tokennum": 322}], "negative_passages": []}
{"query_id": "q-en-kubernetes-eba7a62362482022450bf05cfdbf1ca65be40f25f508e349418ef2a894ff5cc6", "query": "import ( \"fmt\" <ins> \"os\" </ins> \"strings\" \"syscall\" \"unsafe\"", "positive_passages": [{"docid": "doc-en-kubernetes-5e93ba1a338583c6193506912a68a67fcc908451a37c483694071bc120df2bcb", "text": "When a --resolv-conf (DNS resolver config) is passed to kubelet on a Windows node, the config content is used as part of sandbox initialization (through getHostDNSConfig()). Now with the recent changes (), it seems now to fail with an error like: E0315 10:22:16. 4764 ] \"Error syncing pod, skipping\" err=\"failed to \"CreatePodSandbox\" for \"img-pull-(-b40a-459d-9033-)\" with CreatePodSandboxError: \"Failed to generate sandbox config for pod \"img-pull-(-b40a-459d-9033-)\": Unexpected resolver config value: \"C:etckubernetescni\". Expected \"\" or \"Host\".\"\" pod=\"img-puller-3842/img-pull-\" podUID=-b40a-459d-9033- This is showing on all the runs of GCE testgrid (latest): Reading/using the passed resolv config on Windows Run a Windows pool with DNS resolv config being set as part of kubelet params. No response_ 27 alpha.3 1.27 beta.0 master <detailsGCE </details<details</details<details</details<details</details<details</details\n/triage accepted /milestone v1.27 /sig node /sig network\n/sig windows /cc\n/priority criticial-urgent as this is likely a release blocking\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority criticial-urgent 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\n/priority critical-urgent\nHmm, so you're setting the [1]. This PR introduced the capability to read the DNS config options from the Windows host registries while removing the capability to read from a file, introducing a regression. I've sent a PR addressing this issue: [1]\nIs the file you are pointing to a UNIX-style or something else?\nWas the file changing the behavior of the node?", "commid": "kubernetes_issue_116782", "tokennum": 565}], "negative_passages": []}
{"query_id": "q-en-kubernetes-eba7a62362482022450bf05cfdbf1ca65be40f25f508e349418ef2a894ff5cc6", "query": "import ( \"fmt\" <ins> \"os\" </ins> \"strings\" \"syscall\" \"unsafe\"", "positive_passages": [{"docid": "doc-en-kubernetes-a55794e1d2c420cf7484c297920657922704eb45d045ae8237364febdd60d634", "text": "Yeah, what used on GCE/GKE, seems to be a Linux-like conf, eg: nameserver 10.128.0.1 search c.<project_name.internal google.internal ` We haven't tried to remove from kubelet to see the behavior.\nThis Issue/PR has been marked as release blocker. Please have the fix merged by eod today otherwise the feature has to be reverted. For the Issue/PR owner: please have a revert/feature disable PR open today in case the fix failed to get in. Thank you! See the -- Kubernetes 1.27 release manager\nI opened up a revert PR in case this PR does not merge by code freeze.\nThanks for the resolution! both 2019 and 2022 grids seems to be back to green now!\nThanks for confirming! I opened to ensure gets updated too", "commid": "kubernetes_issue_116782", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ebc3e5a6b86f0e4adb9f9569fc1b8668cdd790bf85ecf959d1d9bb8ef8757106", "query": "t.Fatal(err) } j = convertNullTypeToNullable(j) <ins> j = stripIntOrStringType(j) </ins> openAPIJSON, err = json.Marshal(j) if err != nil { t.Fatal(err)", "positive_passages": [{"docid": "doc-en-kubernetes-42eca355948acd2923f06d9ab50c5116c5afebe4d73334e949a0d732f7352d29", "text": "The server-side validation does not check the type of values with . Create a CRD like: Then create a CR: It is not rejected, but should because must not be a boolean.", "commid": "kubernetes_issue_78817", "tokennum": 40}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ebfbc142309eaf532ab60148697a152ee7f48b5c99a5d9fc3a0193fd0089399a", "query": "foo := newDeployment(\"foo\", 1, nil, nil, nil, map[string]string{\"foo\": \"bar\"}) foo.Spec.Strategy.Type = extensions.RecreateDeploymentStrategyType <del> rs := newReplicaSet(foo, \"foo-1\", 1) pod := generatePodFromRS(rs) </del> <ins> rs1 := newReplicaSet(foo, \"foo-1\", 1) rs2 := newReplicaSet(foo, \"foo-1\", 1) pod1 := generatePodFromRS(rs1) pod2 := generatePodFromRS(rs2) </ins> f.dLister = append(f.dLister, foo) <del> f.rsLister = append(f.rsLister, rs) </del> <ins> // Let's pretend this is a different pod. The gist is that the pod lister needs to // return a non-empty list. f.podLister = append(f.podLister, pod1, pod2) c, _ := f.newController() enqueued := false c.enqueueDeployment = func(d *extensions.Deployment) { if d.Name == \"foo\" { enqueued = true } } c.deletePod(pod1) if enqueued { t.Errorf(\"expected deployment %q not to be queued after pod deletion\", foo.Name) } } // TestPodDeletionPartialReplicaSetOwnershipEnqueueRecreateDeployment ensures that // the deletion of a pod will requeue a Recreate deployment iff there is no other // pod returned from the client in the case where a deployment has multiple replica // sets, some of which have empty owner references. func TestPodDeletionPartialReplicaSetOwnershipEnqueueRecreateDeployment(t *testing.T) { f := newFixture(t) foo := newDeployment(\"foo\", 1, nil, nil, nil, map[string]string{\"foo\": \"bar\"}) foo.Spec.Strategy.Type = extensions.RecreateDeploymentStrategyType rs1 := newReplicaSet(foo, \"foo-1\", 1) rs2 := newReplicaSet(foo, \"foo-2\", 2) rs2.OwnerReferences = nil pod := generatePodFromRS(rs1) f.dLister = append(f.dLister, foo) f.rsLister = append(f.rsLister, rs1, rs2) f.objects = append(f.objects, foo, rs1, rs2) c, _ := f.newController() enqueued := false c.enqueueDeployment = func(d *extensions.Deployment) { if d.Name == \"foo\" { enqueued = true } } c.deletePod(pod) if !enqueued { t.Errorf(\"expected deployment %q to be queued after pod deletion\", foo.Name) } } // TestPodDeletionPartialReplicaSetOwnershipDoesntEnqueueRecreateDeployment that the // deletion of a pod will not requeue a Recreate deployment iff there are other pods // returned from the client in the case where a deployment has multiple replica sets, // some of which have empty owner references. func TestPodDeletionPartialReplicaSetOwnershipDoesntEnqueueRecreateDeployment(t *testing.T) { f := newFixture(t) foo := newDeployment(\"foo\", 1, nil, nil, nil, map[string]string{\"foo\": \"bar\"}) foo.Spec.Strategy.Type = extensions.RecreateDeploymentStrategyType rs1 := newReplicaSet(foo, \"foo-1\", 1) rs2 := newReplicaSet(foo, \"foo-2\", 2) rs2.OwnerReferences = nil pod := generatePodFromRS(rs1) f.dLister = append(f.dLister, foo) f.rsLister = append(f.rsLister, rs1, rs2) f.objects = append(f.objects, foo, rs1, rs2) </ins> // Let's pretend this is a different pod. The gist is that the pod lister needs to // return a non-empty list. f.podLister = append(f.podLister, pod)", "positive_passages": [{"docid": "doc-en-kubernetes-2f9c6224492589431ce544bf6b6edab10c3ff06174d612eb6875bebaba0cb87e", "text": "IMO it feels like a bad practice to have mutating resource handlers. The deletePod handler is used for queueing a Recreate deployment once it has no pods running. It should merely look at the ReplicaSets that have owner refs as opposed to using dc.getReplicaSetsForDeployment. The orphaning/adoption dance is already happening inside the reconcilation loop.\nI'd like to work on this\nfeel free to grab it. I can't assign the issue to you so I'll add myself; ping me on the PR when you have one.", "commid": "kubernetes_issue_46933", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ebff15c93364691f1e03b1c1b0ac628696a349d8cf9a24b81e164ed6ce74467b", "query": "// GetZoneByNodeName gets cloudprovider.Zone by node name. func (ss *scaleSet) GetZoneByNodeName(name string) (cloudprovider.Zone, error) { <del> _, _, vm, err := ss.getVmssVM(name) </del> <ins> managedByAS, err := ss.isNodeManagedByAvailabilitySet(name) </ins> if err != nil { <del> if err == ErrorNotVmssInstance { glog.V(4).Infof(\"GetZoneByNodeName: node %q is managed by availability set\", name) // Retry with standard type because nodes are not managed by vmss. return ss.availabilitySet.GetZoneByNodeName(name) } </del> <ins> glog.Errorf(\"Failed to check isNodeManagedByAvailabilitySet: %v\", err) return cloudprovider.Zone{}, err } if managedByAS { // vm is managed by availability set. return ss.availabilitySet.GetZoneByNodeName(name) } _, _, vm, err := ss.getVmssVM(name) if err != nil { </ins> return cloudprovider.Zone{}, err }", "positive_passages": [{"docid": "doc-en-kubernetes-98264fae63e9d149f0171dd13218170b598f5e330429a04234e4c80f3d1b23d2", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: VMAS nodes are reporting error in vmss cluster (vmType set to vmss). What you expected to happen: Node should register correctly in the kubernetes cluster. How to reproduce it (as minimally and precisely as possible): Create a VMAS nodes inside vmss cluster. Anything else we need to know?: Environment: Kubernetes version (use ): master Cloud provider or hardware configuration: azure OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/sig azure", "commid": "kubernetes_issue_60185", "tokennum": 165}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ec24b3419de5f077767872d50bec0ec54c146f42ed1b9177843825dd28fe9497", "query": "# CNI storage path for Windows nodes export WINDOWS_CNI_STORAGE_PATH=\"https://storage.googleapis.com/k8s-artifacts-cni/release\" # CNI version for Windows nodes <del> export WINDOWS_CNI_VERSION=\"v0.8.7\" </del> <ins> export WINDOWS_CNI_VERSION=\"v0.9.1\" </ins> # Pod manifests directory for Windows nodes on Windows nodes. export WINDOWS_MANIFESTS_DIR=\"${WINDOWS_K8S_DIR}manifests\" # Directory where cert/key files will be stores on Windows nodes.", "positive_passages": [{"docid": "doc-en-kubernetes-dfff84e3b11879758919fecc393710655267c5015ee34e69e71565465ba5db90", "text": "The latest release of CNI plugins is , but we still have . I'll attempt to create a PR for this based on the .\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig network\n- assigning to you :)", "commid": "kubernetes_issue_102311", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ec2a584f789d22a69fc37a2425c90be13d837c6bf6e26a432edaa3c89233145f", "query": "// The name of this port. All ports in an EndpointSlice must have a unique // name. If the EndpointSlice is dervied from a Kubernetes service, this // corresponds to the Service.ports[].name. <del> // Name must either be an empty string or pass IANA_SVC_NAME validation: // * must be no more than 15 characters long // * may contain only [-a-z0-9] // * must contain at least one letter [a-z] // * it must not start or end with a hyphen, nor contain adjacent hyphens </del> <ins> // Name must either be an empty string or pass DNS_LABEL validation: // * must be no more than 63 characters long. // * must consist of lower case alphanumeric characters or '-'. // * must start and end with an alphanumeric character. </ins> // Default is empty string. Name *string `json:\"name,omitempty\" protobuf:\"bytes,1,name=name\"` // The IP protocol for this port.", "positive_passages": [{"docid": "doc-en-kubernetes-b73bb51cef5016ee2dcd80aae4248808fec811a4dad3a3b7abbba7673a446c48", "text": "What happened: No endpoints created in the EndpointSlice for my service due to the port on the service being too long. Logs show: EndpointSlice created has no endpoint: What you expected to happen: Service that works with Endpoints should work with EndpointSlice. If this is intentional, it should be clearly documented How to reproduce it (as minimally and precisely as possible): Create a service with a long port name Environment: Kubernetes version (use ): 1.16 Cloud provider or hardware configuration: kind\n/sig networking\nThe label(s) cannot be applied. These labels are supported: <detailsIn response to : /sig networking 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\n/sig network These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by vllry. \u200d\nFor a rough measure of impact, Istio had 5 ports that were over this limit (and many more that were right at 15 characters), so I suspect it may not be terribly rare.\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nThis needs to be resolved before endpointslices graduate from alpha\n/assign\n/remove-triage unresolved", "commid": "kubernetes_issue_84388", "tokennum": 292}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ec59a5ccc120a0d41f1a18fe00a97c83faa734671c18c120f37e821d3cb630e2", "query": "} glog.V(5).Infof(\"namespace controller - deleteAllContentForGroupVersionResource - items remaining - namespace: %s, gvr: %v, items: %v\", namespace, gvr, len(unstructuredList.Items)) if len(unstructuredList.Items) != 0 && estimate == int64(0) { <ins> // if any item has a finalizer, we treat that as a normal condition, and use a default estimation to allow for GC to complete. for _, item := range unstructuredList.Items { if len(item.GetFinalizers()) > 0 { glog.V(5).Infof(\"namespace controller - deleteAllContentForGroupVersionResource - items remaining with finalizers - namespace: %s, gvr: %v, finalizers: %v\", namespace, gvr, item.GetFinalizers()) return finalizerEstimateSeconds, nil } } // nothing reported a finalizer, so something was unexpected as it should have been deleted. </ins> return estimate, fmt.Errorf(\"unexpected items still remain in namespace: %s for gvr: %v\", namespace, gvr) } return estimate, nil", "positive_passages": [{"docid": "doc-en-kubernetes-125faf475ef5c9fadc127cee08d3d538bc2825eff7d3fd81be9f088e2d4a0dbf", "text": "Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see ): No What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): \"LRUExpireCache\" Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT What happened: requires write lock since needs to manipulate its list to track recently used item. Currently it uses read lock so it may introduce race condition. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else do we need to know:\nThis was fixed in", "commid": "kubernetes_issue_31081", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ec63fc4fc32bbfd1c56e9870ee79239741c09d97ddc9229e91630ca825b62324", "query": "// the test so we can ensure that we clean up after // ourselves defer podClient.Delete(pod.Name, api.NewDeleteOptions(0)) <del> _, err = podClient.Create(pod) </del> <ins> pod, err = podClient.Create(pod) </ins> if err != nil { Failf(\"Failed to create pod: %v\", err) } By(\"verifying the pod is in kubernetes\") <ins> selector = labels.SelectorFromSet(labels.Set(map[string]string{\"time\": value})) options = api.ListOptions{ LabelSelector:   selector, ResourceVersion: pod.ResourceVersion, } </ins> pods, err = podClient.List(options) if err != nil { Failf(\"Failed to query for pods: %v\", err)", "positive_passages": [{"docid": "doc-en-kubernetes-7b2f86b1021161afba33b63af83ddb3cce3267e73d9102e5d7e2a19b1a8a0e6b", "text": "cc\nYet another failure\nThere is already fix in flight\nOk. I see\nThis was closed 5 days ago but appears to not be fixed. Many PRs have referenced it as a flake since the fix went in.\n- I referenced to it 2 after it was closed, but all of those failures were from runs before this was merged. So it's possible that it's already fixed.\nWhen was the fix merged? I saw this a couple hours ago:\nOops, same test but the error is slightly different... Maybe this is a seperate flake\nYeah - it seems to be something different.\nAlso - I'm not claiming it's definitely fixed - I just said that we need to double check, because the two that I linked was from before merge.\nI'll close this one for now. Please reopen the issue and cc us if the flake occurs again.", "commid": "kubernetes_issue_21045", "tokennum": 182}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ec9acbcc8bbdd5a3c4df5175648baec0700387a7f56d0d36f1448cae7dbb47bb", "query": "return true }) if err != nil { <ins> if apiErr, ok := err.(awserr.Error); ok && apiErr.Code() == \"DelegationSetNotReusable\" || apiErr.Code() == \"NoSuchDelegationSet\" || apiErr.Code() == \"InvalidInput\" { return []dnsprovider.Zone{}, nil } </ins> return []dnsprovider.Zone{}, err } return zoneList, nil", "positive_passages": [{"docid": "doc-en-kubernetes-2b4d325d4814fe81f2a99615b844cff823940de918e3b360e7f108b94b4fe81b", "text": "/kind bug What happened: walteraa [6:55 AM] Hi, The controller manager of the federation using Google cloud DNS is crashing, the log showed is that: the hyperkube command is that: I have created this in the Google DNS Someone knows why the DNS zone query is getting the 404 error?? :disappointed: What you expected to happen: It should have created the missing domain. How to reproduce it (as minimally and precisely as possible): As per above. Anything else we need to know?: Environment: Kubernetes version (use ): 1.7.4 Cloud provider or hardware configuration**: OpenStack (irrelevant) OS (e.g. from /etc/os-release): irrelevant Kernel (e.g. ): irrelevant Install tools: irrelevant Others: irrelevant\nThe bug is related to this: The above code assumes that the provider code returns no error but an empty list if the domain does not exist, but instead the provider returns a 404. Need to fix the provider and/or the above code.\n/sig federation\nI am unlikely to have time to work on this soon, so if anyone else wants to, go right ahead.\n/assign\nAn additional information: I have created a which is based on the credential JSON file created through instruction. After that, I have configured the Federation controller manager to mount this secret as a volume in the container and set the environment variable to the JSON file inside this volume. Before doing that, I was getting an authentication error so the google DNS provider couldn't be instantiated, and after doing the instructions that I mentioned before, this authentication error was solved but now I'm getting 404 error when Google DNS provider tries access the specified managed zone. The file that I have generated follow this structure:", "commid": "kubernetes_issue_51139", "tokennum": 376}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ed471791e5606d3be1585c6eb3fb95461e37c2c083c699923c7bbc9a02213c07", "query": "func exportCustomMetricFromPod(f *framework.Framework, consumerName string, metricValue int) *common.ResourceConsumer { podAnnotations := map[string]string{ \"prometheus.io/scrape\": \"true\", <del> \"prometheus.io/path\":   \"/Metrics\", </del> <ins> \"prometheus.io/path\":   \"/metrics\", </ins> \"prometheus.io/port\":   \"8080\", } return common.NewMetricExporter(consumerName, f.Namespace.Name, podAnnotations, nil, metricValue, f.ClientSet, f.InternalClientset, f.ScalesGetter)", "positive_passages": [{"docid": "doc-en-kubernetes-2d0ebe90b3c755e0edf33c6811bf431b4c51fd00f4f7b6a1d49649dd59cb487b", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: Used the endpoint /BumpMetric to create fake metrics for Prometheus. When I tried to curl /metrics I got the following response: Bad request. Not a POST request What you expected to happen: I expected to see something like this: # HELP info message. # TYPE gauge 0. How to reproduce it (as minimally and precisely as possible): Following the docs, after having it running inside kubernetes: Anything else we need to know?: Looks like introduced this by mistake. Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: <!-- DO NOT EDIT BELOW THIS LINE --/kind bug\n/sig testing", "commid": "kubernetes_issue_72403", "tokennum": 213}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ed5727a3741a38a6180719d6022decf75b761e2b77e7b1034ba21363a1c29bdf", "query": "package route53 import ( <ins> \"github.com/aws/aws-sdk-go/aws/awserr\" </ins> \"github.com/aws/aws-sdk-go/service/route53\" \"k8s.io/apimachinery/pkg/util/uuid\"", "positive_passages": [{"docid": "doc-en-kubernetes-2b4d325d4814fe81f2a99615b844cff823940de918e3b360e7f108b94b4fe81b", "text": "/kind bug What happened: walteraa [6:55 AM] Hi, The controller manager of the federation using Google cloud DNS is crashing, the log showed is that: the hyperkube command is that: I have created this in the Google DNS Someone knows why the DNS zone query is getting the 404 error?? :disappointed: What you expected to happen: It should have created the missing domain. How to reproduce it (as minimally and precisely as possible): As per above. Anything else we need to know?: Environment: Kubernetes version (use ): 1.7.4 Cloud provider or hardware configuration**: OpenStack (irrelevant) OS (e.g. from /etc/os-release): irrelevant Kernel (e.g. ): irrelevant Install tools: irrelevant Others: irrelevant\nThe bug is related to this: The above code assumes that the provider code returns no error but an empty list if the domain does not exist, but instead the provider returns a 404. Need to fix the provider and/or the above code.\n/sig federation\nI am unlikely to have time to work on this soon, so if anyone else wants to, go right ahead.\n/assign\nAn additional information: I have created a which is based on the credential JSON file created through instruction. After that, I have configured the Federation controller manager to mount this secret as a volume in the container and set the environment variable to the JSON file inside this volume. Before doing that, I was getting an authentication error so the google DNS provider couldn't be instantiated, and after doing the instructions that I mentioned before, this authentication error was solved but now I'm getting 404 error when Google DNS provider tries access the specified managed zone. The file that I have generated follow this structure:", "commid": "kubernetes_issue_51139", "tokennum": 376}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ed5d95ececc40164062f77e4c7d40b36324664058af89f6241d9161f6ab966de", "query": "return info.HealthCheckNodePort } <ins> // GetNodePort is part of the ServicePort interface. func (info *BaseServiceInfo) GetNodePort() int { return info.NodePort } </ins> func (sct *ServiceChangeTracker) newBaseServiceInfo(port *v1.ServicePort, service *v1.Service) *BaseServiceInfo { onlyNodeLocalEndpoints := false if apiservice.RequestsOnlyLocalTraffic(service) {", "positive_passages": [{"docid": "doc-en-kubernetes-9e39524d0e4c89f1ddf9c516fe4e1c471a25826ee6b222abfe1f6c0cc213064c", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: BUG REPORT What happened: When deleting/recreating pods backing a UDP service, traffic from external senders stops flowing. What you expected to happen: Traffic would continue to flow to new pods. How to reproduce it (as minimally and precisely as possible): Based on reading of similar issues and commit messages it seems like this would be most noticable on high-volume UDP applications, statsd and syslog are good examples. a deployment and service for a UDP app. In my test case, this would be the container. an external node, create a small test script utilizing a statsd library such as pystatsd. The most important part is that the sender uses the same source-port for every packet sent. Ex: the sender. Install tcpdump into the pod and watch for incoming packets, example from the test case: the pod tcpdump in the newly created pod. Observe that no new matching packets are flowing. existing conntrack rules on all nodes in the cluster. You should see traffic start flowing to the pod again. example command for clearing conntrack rules on the nodes: Anything else we need to know?: I have tested this only on GKE-managed clusters that utilize google forwarding-rules for external LBs, but I believe the issue may be present on any platform where iptables mode for kube-proxy is used. Tested and verified on 1.8.6-gke.0 and 1.7.11-gke.1. Also tested with both Google Container-optimized OS and the Ubuntu-based node images. I have only test this on GKE It appears this was a known issue and should have been cleared up by: From my reading of , it seems as if the func should exec() to clear up UDP entries on service endpoint change, but the only place I see that func called is from syncProxyRules(). That func looks complex and possibly like it is only run occasionally and not on service/endpoint changes. Environment: Kubernetes version (use ): (Also tested on 1.7.11-gke.1) Cloud provider or hardware configuration: GKE-managed clusters, google cloud. OS (e.g.", "commid": "kubernetes_issue_59368", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ed5d95ececc40164062f77e4c7d40b36324664058af89f6241d9161f6ab966de", "query": "return info.HealthCheckNodePort } <ins> // GetNodePort is part of the ServicePort interface. func (info *BaseServiceInfo) GetNodePort() int { return info.NodePort } </ins> func (sct *ServiceChangeTracker) newBaseServiceInfo(port *v1.ServicePort, service *v1.Service) *BaseServiceInfo { onlyNodeLocalEndpoints := false if apiservice.RequestsOnlyLocalTraffic(service) {", "positive_passages": [{"docid": "doc-en-kubernetes-27a4c6cdabc82c95dde932bb7bf1e1865b5f691c3b3e7bf1ed0c71bfc361fddc", "text": "from /etc/os-release): tried both: and Kernel (e.g. ): and Install tools: Others:\n/sig network\nWe also ran into this in kubernetes v1.7.6 using OpenShift 3.7:\n~I believe this is the same as ~If so, it is fixed in 1.10: These are about HostPort, not NodePort, sorry for the noise.\nIssues 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\nIs there any other known workaround for this besides updating conntrack rules on the kube nodes? I tried deleting and recreating the service, but this didn't update the rules. When I restart the stream on the client side data flows correctly again (perhaps it's perceived as a new connection), but I have to restart the stream for each sender.\n/remove-lifecycle stale\nFWIW, this is not fixed in 1.10 - that fix was for HostPort, and this is still a bug for NodePort.\nI am seeing this issue in 1.11. I am using LoadBalancer type.\nhas been working on a fix for this, FYI.\nThis issue is extremely impactful for telephony protocols that rely on static source ip and source port. Any update on a possible workaround? I was thinking a potential workaround might be to reduce the UDP timeout to something really short so the stale conntrack entries go away faster. Or maybe there is a way to flush conntrack on the event of pod deletion? Edit: Removed stupid idea of a workaround to disable conntrack for UDP. Can't disable conntrack for UDP because it's used for DNAT from node to container.\nThe workaround is to not use NodePorts. Other kinds of services are already correct.\nnot sure what you mean. I am seeing the issue with a LoadBalancer type so it does not affect NodePorts only. As a workaround I have created a small python script that watches the K8s API for pod deletions and clears the related conntrack entries when that happens. I can share it when I get to work on Monday if you want to try it out.", "commid": "kubernetes_issue_59368", "tokennum": 535}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ed5d95ececc40164062f77e4c7d40b36324664058af89f6241d9161f6ab966de", "query": "return info.HealthCheckNodePort } <ins> // GetNodePort is part of the ServicePort interface. func (info *BaseServiceInfo) GetNodePort() int { return info.NodePort } </ins> func (sct *ServiceChangeTracker) newBaseServiceInfo(port *v1.ServicePort, service *v1.Service) *BaseServiceInfo { onlyNodeLocalEndpoints := false if apiservice.RequestsOnlyLocalTraffic(service) {", "positive_passages": [{"docid": "doc-en-kubernetes-956c9b1270ab4e0eb744fb5e7c207e8e7b7c0a49e83c634550198bfe9b333eeb", "text": "I've my script . Note that it's not tested much so don't use it in a production environment. Also it cleans up all conntrack entries for a deleted pod, not only the UDP related ones.\nWe are also seeing this issue with type loadbalancer. We are on 1.11. Our use-case is the following: multiple devices are sending to an aggreagator machine. This machine forwards the UDP packages to a loadBalancer in gcp. When debugging the service, I noticed the following: The traffic is assigned to one pod, and the packages are not loadbalanced (client and server are the same cfr use-case) When redeploying a new cluster, Conntrack is cleared on termination signal of the old pod. (client receives connection refused) red/black and highlander deployment strategies have the same effect. How would I expect this to be working then? New cluster is . Conntrack is cleared Data is routed to NEW pods old pods are terminated Best Regards, Tim\nI am seeing this exact same issue on our cluster which has k8s v1.14.5 . We have endpoint nginx pods backing a UDP service with nodeport. Suddenly one day we see traffic not hitting into nginx pod but reaching the node hosting the nginx pod. We could simulate the problem by restarting the nginx pods. I am assuming with this issue marked as closed; and having made its way into v1.14; we should not be seeing this. Would also like to point out; the one thing, in addition we have in the service is ExternalTrafficPolicy set to Local. Can anyone please guide/help on why we are seeing this in v.1.14.5 of our cluster.\nSeeing this with k8s v1.16.5", "commid": "kubernetes_issue_59368", "tokennum": 391}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ed6b5417c29cf068d69b8025154deaba63cae41331b67b6f1ebdb25979aed152", "query": "kube::golang::setup_env <del> make -C \"${KUBE_ROOT}\" WHAT=cmd/genswaggertypedocs # Find binary genswaggertypedocs=$(kube::util::find-binary \"genswaggertypedocs\") if [[ ! -x \"$genswaggertypedocs\" ]]; then { echo \"It looks as if you don't have a compiled genswaggertypedocs binary\" echo echo \"If you are running from a clone of the git repo, please run\" echo \"'make WHAT=cmd/genswaggertypedocs'.\" } >&2 exit 1 fi </del> _tmpdir=\"$(kube::realpath \"$(mktemp -d -t swagger-docs.XXXXXX)\")\" function swagger_cleanup { rm -rf \"${_tmpdir}\"", "positive_passages": [{"docid": "doc-en-kubernetes-c72a20983cc57589ac47c7e12e6139151b8b668ad770346d9c321da0f1463da8", "text": "When working on I a strange issue. It seems that while auto-generating conversions it works fine, but during things like or in the presubmits what is generated is different. Looking into test results: it seems that the order in which the files are processed is different then. /kind bug /sig api-machinery\nFTR: The log from above has some debug-logging and panics and the conversion-generator logs are those with\n/assign\nmodifies conversion-gen, but doesn't change the generated files. Did you intentionally exclude those changes? I wonder if it's similar to I checked out , ran I was able to reproduce the error in If that's the case, a workaround to fix the auto-generating is to first remove the affected files and re-generate them locally.\nThis is supposed to be no-op :) no auto-generated files should change That's not the fix. The problem is with the test jobs themselves: for generating swagger doc, they actually generate different things than they generate when you call \"make generated-files\" My PR is only a trigger for the problem, it's not a root cause. The auto-generated files are correct, but as part of running swagger docs, we're in-process generating a different stuff.\nIt looks that packages were missing. has a shorter / list compared to the other checks (e.g. ) when I ran . In the case of , the component-base config package was missing, thus the FIXME code path got hit. The list of packages was derived from . It seems that the dir was dirty during . I'm exploring if we can clean up the dir like does.\nIt seems that this one isn't yet fully fixed. I have updated the based on the comments on it and a similar issue on that (which I think has a very similar root cause). However, now \"govet\" and \"staticcheck\" are failing: [Ironically all other tests are passing, so I think this is again connected to some garbage somewhere] - can you please help with this?\nAs previously, I can reproduce it by:\nI'm fairly sure at this point that the inputdirs param here is too restrictive:\nIt seems that this commit might be addressing this:\nHeh - I think it helped me locally, but it doesn't help for - I probably did something wrong. But I'm fairly sure it's something along those lines that we need to do.", "commid": "kubernetes_issue_94691", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ed6b5417c29cf068d69b8025154deaba63cae41331b67b6f1ebdb25979aed152", "query": "kube::golang::setup_env <del> make -C \"${KUBE_ROOT}\" WHAT=cmd/genswaggertypedocs # Find binary genswaggertypedocs=$(kube::util::find-binary \"genswaggertypedocs\") if [[ ! -x \"$genswaggertypedocs\" ]]; then { echo \"It looks as if you don't have a compiled genswaggertypedocs binary\" echo echo \"If you are running from a clone of the git repo, please run\" echo \"'make WHAT=cmd/genswaggertypedocs'.\" } >&2 exit 1 fi </del> _tmpdir=\"$(kube::realpath \"$(mktemp -d -t swagger-docs.XXXXXX)\")\" function swagger_cleanup { rm -rf \"${_tmpdir}\"", "positive_passages": [{"docid": "doc-en-kubernetes-990f60044784b00bffd5b4d8f47018806db1b06c6e833c64dee7a7e61af70ed4", "text": "- will you be able to help with it?\nSo yeah - I was completely wrong. Basically, running with with DBG it clearly is a problem with gen-conversion. And the problem is that we pass only limited input to it: I think we should always pass all inputs - but we should look a bit deeper into it.\nOK - so this is the problematic part: We basically process only packages that are explicitly requested by the user and ignore ones that are imported. So in order to have the conversion func imported by the generator, the package where it lives has to be explicitly imported. So we should basically always pass all input packages to conversion generator.\nI actually created a new one, as it seems to be a different thing. Closing in favor of\n/triage accepted", "commid": "kubernetes_issue_94691", "tokennum": 157}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ed97571e1c8d5e388cd9f545b9d9a020a7b85a6e31beedbe4173fb9cf4572020", "query": "if err != nil { framework.Failf(\"Error getting node hostnames: %v\", err) } <ins> ginkgo.By(fmt.Sprintf(\"Found %d SSH'able hosts\", len(hosts))) </ins> testCases := []struct { cmd            string", "positive_passages": [{"docid": "doc-en-kubernetes-375711dd290c57e850707ef6745091e3080fe654060082beb69e30fe80db0e88", "text": "ci-kubernetes-e2e-gce-scale-correctness Kubernetes e2e suite: [sig-node] SSH should SSH to all nodes and run commands kubetest.Test Jul 10 14:01:51 UTC+0200 Kubernetes e2e suite: [sig-node] SSH should SSH to all nodes and run commands: more . Test /sig node\n/cc\n/triage accepted\nUhhh, this may help here\n/milestone v1.22\n/sig scalability FYI\nI got annoyed that I couldn't click through to see the other logs, so now you can, ref: (spyglass doesn't render build- because it's 500MB, and the limit for rendering is 100MB)\n/assign SIG Scalability chairs/TLs, please find someone to address or call this a non-release-blocking failure\nAssigning to current scalability oncall (): /assign\nThis is sig-node issue - should be addres by SIG-node folks. /sig node\nis being discussed as a fix for this and I'm not sure it's correct\nis it sig scalability's intent that 5k node clusters should support SSH?\nThe SSH test in question passes in the \"default\" job: So the fact that this failure is unique to a scalability job means to me that scalability needs to own at least some part of this\nI did a little bit of digging and ci-kubernetes-e2e-gce-scale-correctness uses option in kubetest, which according to seems to be setting KUBESSHBASTION env. So I believe this is main difference between our scalability job and \"default\".\nDebugging the test in and providing a fix there. The crictl host PR () is doing something different.", "commid": "kubernetes_issue_103688", "tokennum": 400}], "negative_passages": []}
{"query_id": "q-en-kubernetes-edcbf51900748063d45b48d0141a032c6276337f094ca90b2d2a80f74896ff87", "query": "} } <ins> func TestCacherNoLeakWithMultipleWatchers(t *testing.T) { defer featuregatetesting.SetFeatureGateDuringTest(t, utilfeature.DefaultFeatureGate, features.WatchBookmark, true)() backingStorage := &dummyStorage{} cacher, _, err := newTestCacher(backingStorage, 1000) if err != nil { t.Fatalf(\"Couldn't create cacher: %v\", err) } defer cacher.Stop() // Wait until cacher is initialized. cacher.ready.wait() pred := storage.Everything pred.AllowWatchBookmarks = true // run the collision test for 3 seconds to let ~2 buckets expire stopCh := make(chan struct{}) time.AfterFunc(3*time.Second, func() { close(stopCh) }) wg := &sync.WaitGroup{} wg.Add(1) go func() { defer wg.Done() for { select { case <-stopCh: return default: ctx, _ := context.WithTimeout(context.Background(), 3*time.Second) w, err := cacher.Watch(ctx, \"pods/ns\", \"0\", pred) if err != nil { t.Fatalf(\"Failed to create watch: %v\", err) } w.Stop() } } }() wg.Add(1) go func() { defer wg.Done() for { select { case <-stopCh: return default: cacher.bookmarkWatchers.popExpiredWatchers() } } }() // wait for adding/removing watchers to end wg.Wait() // wait out the expiration period and pop expired watchers time.Sleep(2 * time.Second) cacher.bookmarkWatchers.popExpiredWatchers() cacher.bookmarkWatchers.lock.Lock() defer cacher.bookmarkWatchers.lock.Unlock() if len(cacher.bookmarkWatchers.watchersBuckets) != 0 { t.Errorf(\"unexpected bookmark watchers %v\", len(cacher.bookmarkWatchers.watchersBuckets)) } } </ins> func testCacherSendBookmarkEvents(t *testing.T, watchCacheEnabled, allowWatchBookmarks, expectedBookmarks bool) { defer featuregatetesting.SetFeatureGateDuringTest(t, utilfeature.DefaultFeatureGate, features.WatchBookmark, watchCacheEnabled)() backingStorage := &dummyStorage{}", "positive_passages": [{"docid": "doc-en-kubernetes-c66c9bab938b839459ac01dfd08140ea19c2b9a1199fe50a2b49f94fd9cbbbfb", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: I try to backport bookmark feature to our internal branch. When I enable bookmark feature, apiserver leaks memory. I spend some time to dig the root cause and find the bookmarkWatchers of service cacher is keep increasing. I am not sure if it exists at upstream code. Please let me know if it is ok at latest code. What you expected to happen: Avoid memory leaking How to reproduce it (as minimally and precisely as possible): a cluster. not update service. will find kube-apiserver's memory keep increasing. Anything else we need to know?: Kubelet will watch service with bookmark, and add a watcher to bookmarkWatchers. and service init resource version is 0 Without updating service, we cannot update \"lastProcessedResourceVersion\", it will keep 0, bookmarkTimer branch will always be continued. As a result, it cannot trigger popExpiredWatchers, so the service watcher will keep increasing every watching. Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig scalability PLAT :)\nHow about making this change ?\n- can you also please take a look?\nAgree with u. That's same way I fix in our branch. But I wanna hear the suggestion of and .\n! With the same bugfix wrote above, we can see the memory not increasing any more.\nGiven that watch-bookmarks doesn't create any additional go-routines (well, creates 1, but cannot leak them), it has to leak the data. The only data that can be leaked is exactly bookmarkWatchers. So I looked into the code and got into exactly the same conclusion - that we must be leaking watchers for resources that aren't changing. The fix as above makes sense (though we also need a unit test for it).\nThanks a lot.\nhas the fix by\nThanks for reporting the bug, I will look at this day later. In addition, also need to think carefully about whether need to send a bookmark when there are no events at all.\ncc", "commid": "kubernetes_issue_80690", "tokennum": 531}], "negative_passages": []}
{"query_id": "q-en-kubernetes-edd47c4b6eff769ce447fc2452e473c5bdff5b31bd57331f8323f5d1bd4ba1f4", "query": "}) return args } <ins> func TestValidateKubeletFlags(t *testing.T) { tests := []struct { name   string error  bool labels map[string]string }{ { name:  \"Invalid kubernetes.io label\", error: true, labels: map[string]string{ \"beta.kubernetes.io/metadata-proxy-ready\": \"true\", }, }, { name:  \"Valid label outside of kubernetes.io and k8s.io\", error: false, labels: map[string]string{ \"cloud.google.com/metadata-proxy-ready\": \"true\", }, }, { name:   \"Empty label list\", error:  false, labels: map[string]string{}, }, } for _, tt := range tests { t.Run(tt.name, func(t *testing.T) { err := ValidateKubeletFlags(&KubeletFlags{ NodeLabels: tt.labels, }) if tt.error && err == nil { t.Errorf(\"ValidateKubeletFlags should have failed with labels: %+v\", tt.labels) } if !tt.error && err != nil { t.Errorf(\"ValidateKubeletFlags should not have failed with labels: %+v\", tt.labels) } }) } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-2c9ef8984ebaf899659836b925069334113c910fc47ebe0516a7d659674f044a", "text": "xref In 1.16: change the metadata-proxy addon to use change the kube-proxy addon to use change the masq-agent addon to use stop setting , , and in kube-up\nHey I'm trying to start to contribute to kubernetes and this seem to be an easy task. Can I help with this one?", "commid": "kubernetes_issue_75050", "tokennum": 77}], "negative_passages": []}
{"query_id": "q-en-kubernetes-edf154825571749ea0dfb356a22bd29c269a6b35c9a58c3972f09275d38b961b", "query": "} } <ins> // Check if the inspected image matches what we are looking for func matchImageTagOrSHA(inspected dockertypes.ImageInspect, image string) bool { // The image string follows the grammar specified here // https://github.com/docker/distribution/blob/master/reference/reference.go#L4 named, err := dockerref.ParseNamed(image) if err != nil { glog.V(4).Infof(\"couldn't parse image reference %q: %v\", image, err) return false } _, isTagged := named.(dockerref.Tagged) digest, isDigested := named.(dockerref.Digested) if !isTagged && !isDigested { // No Tag or SHA specified, so just return what we have return true } if isTagged { // Check the RepoTags for an exact match for _, tag := range inspected.RepoTags { if tag == image { // We found a specific tag that we were looking for return true } } } if isDigested { algo := digest.Digest().Algorithm().String() sha := digest.Digest().Hex() // Look specifically for short and long sha(s) if strings.Contains(inspected.ID, algo+\":\"+sha) { // We found the short or long SHA requested return true } } glog.V(4).Infof(\"Inspected image (%q) does not match %s\", inspected.ID, image) return false } </ins> // applyDefaultImageTag parses a docker image string, if it doesn't contain any tag or digest, // a default tag will be applied. func applyDefaultImageTag(image string) (string, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-73e94f1f9679cf5fca554c149f1c357d9b16156cc7199a4d351eb3b22980b589", "text": "We had rather strange case today when after rolling update one of the kubelet's started wrong container. For this specific replicationcontroller we are using What happened was that after rolling-update when i started to debug the issue i discovered that one of the kubelet's did not pull the image: When looking into what image it actually started i saw: When checking from the actual node i saw this It seems that instead of starting myimage with tag 2208 kubelet started image tagged as 1393 since the docker image id starts with 2208.", "commid": "kubernetes_issue_30355", "tokennum": 119}], "negative_passages": []}
{"query_id": "q-en-kubernetes-edf4388215428f8afd1987e04577faeee63884d848149f7e13aac5381c190b6f", "query": "resources []string namespace string <del> name      string </del> <ins> names     []string </ins> defaultNamespace bool requireNamespace bool", "positive_passages": [{"docid": "doc-en-kubernetes-8781beaf9cecb5a2a5891763e358d97bbb8efac5ebba9fc986604965efa0dda5", "text": "Currently, it could not delete multiple pods at once, need to delete them one by one, it's very inconvenient if I have tons of pods to delete. Unlike docker, docker can multiple stop/rm containers/images at once.\nThis is possible using label selectors as of , which is better if you have tons of pods.\nI agree that using label selector is better to delete all of pods under the label. But to delete multile pods at once is still usable: I just want to delete 1/2 pods under the label, label selector will not work selector could not span over other selectors or pods Another reason is docker rm/stop x y z works, I will wonder why kubectl cannot. This is not urgent, but I hope it can be implemented.\nI agree. Thanks for the suggestion.\nWould this be a suitable task for someone new to k8s development? If so, I'd be willing to take a look at this, if someone could provide a couple of hints where to start.\nFurther to my last message, I have a functional work in progress I would like to share, if anyone is interested?\nPRs are welcome. See\nYes, this is a reasonable place to start. Since its in the client, you won't get much orientation to the core server code, but it will be a good place to orient to the client side API. There us also prior art that you can model off of. The kubectl create ... command already supports multiple resources. A good command to adapter would be the 'label' command. You can find it in Many thanks in advance! Brendan On Feb 19, 2015 8:21 AM, \"Eric Tune\" wrote:", "commid": "kubernetes_issue_3050", "tokennum": 364}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ee1bc1d135b293fd95bf23538d57845980768f3ec1667369efd74c3758a83b07", "query": "if err := deployClient.Delete(deployment.ObjectMeta.Name, deleteOptions); err != nil { framework.Failf(\"failed to delete the deployment: %v\", err) } <del> ginkgo.By(\"wait for 30 seconds to see if the garbage collector mistakenly deletes the rs\") time.Sleep(30 * time.Second) </del> <ins> ginkgo.By(\"wait for deployment deletion to see if the garbage collector mistakenly deletes the rs\") err = wait.PollImmediate(500*time.Millisecond, 1*time.Minute, func() (bool, error) { dList, err := deployClient.List(metav1.ListOptions{}) if err != nil { return false, fmt.Errorf(\"failed to list deployments: %v\", err) } return len(dList.Items) == 0, nil }) if err != nil { framework.Failf(\"Failed to wait for the Deployment to be deleted: %v\", err) } // Once the deployment object is gone, we'll know the GC has finished performing any relevant actions. </ins> objects := map[string]int{\"Deployments\": 0, \"ReplicaSets\": 1, \"Pods\": 2} ok, err := verifyRemainingObjects(f, objects) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-1813ae1c1e9259cc81e5e43ebbd125b04ddddae9d4c14bbc382305b454beda00", "text": "/priority failing-test /priority important-soon /kind flake /sig-api-machinery this failure is currently one of the top flake and repros in both Presubmits and CI jobs. This test is also part of the Conformance suite, which makes the flake far more critical. Can one of you please help triage this issue.\n/cc\n/cc\n/assign\nIssues 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\n/remove-lifecycle stale\nflakes are continuing, hopefully logging gives us more info to work with\nthis test seems to flake quite a bit in the presubmits and its a conformance test on top of this. Can we please look into the new logs to see if we have more info to deflake this? Triage: Logs: https://k8s-\n/cc\nFWIW this test seems to pass consistently in our conformance dashboards - https://k8s-,%20master%20(dev). But seems to flake only in CI and Presubmits\nDo those run at different parallelism levels? It could be load/timeout sensitive\nI have also seen a general uptick in flakes in other e2e tests that could be sensitive to watch event latency, not just gc tests - for example, see the failures in https://k8s-\nIssues 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\nHey, this test does not appear to be flaking anymore can we close this issue?\nClosing based on non-response. /close\nClosing this issue. <detailsIn response to : Closing based on non-response. 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\nThis was never actually fixed, looks like.", "commid": "kubernetes_issue_60463", "tokennum": 504}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ee367047bc707c64d66f6cc2f49b714f5f797978cfa68d86532f4039682affc2", "query": "} mockCadvisor.On(\"VersionInfo\").Return(versionInfo, nil) expectedNode := &api.Node{ <del> ObjectMeta: api.ObjectMeta{Name: \"127.0.0.1\"}, </del> <ins> ObjectMeta: api.ObjectMeta{Name: testKubeletHostname}, </ins> Spec:       api.NodeSpec{}, Status: api.NodeStatus{ Conditions: []api.NodeCondition{", "positive_passages": [{"docid": "doc-en-kubernetes-d16ca614c05197aa8b2652e3bf008c3a9a5ce41d960188a2ba3459b13d8b1102", "text": "Looks like some kubelet unit tests perform a lookupIp which ends up depending on the health of the local resolver. Specifically has this failing: Which leads to the test in: And we recently swapped out the node names from testnode to 127.0.0.1, so probably the culprit?\n/ref\nInteresting. I did swap out the node names in the unit test as part of to be 127.0.0.1, party because I thought that it wouldn't have any problems resolving during unit tests.\n/cc", "commid": "kubernetes_issue_8549", "tokennum": 113}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ee367047bc707c64d66f6cc2f49b714f5f797978cfa68d86532f4039682affc2", "query": "} mockCadvisor.On(\"VersionInfo\").Return(versionInfo, nil) expectedNode := &api.Node{ <del> ObjectMeta: api.ObjectMeta{Name: \"127.0.0.1\"}, </del> <ins> ObjectMeta: api.ObjectMeta{Name: testKubeletHostname}, </ins> Spec:       api.NodeSpec{}, Status: api.NodeStatus{ Conditions: []api.NodeCondition{", "positive_passages": [{"docid": "doc-en-kubernetes-4a4c75dd985aaeba56d487bbde17d68f0425afc5d7e1167fdf1a1abcb97cd0b6", "text": "cc\nWhat is the environment where you are running the tests? They pass for me on my mac, a linux box, and shippable seems to be passing them as well.\nI couldn 't reproduce the failure either.\nI'm out right now; i'll try them when i get back. For the record, I run hack/test- Paul Morie wrote:\nAhem FTR This acronym is going to go quad-plat Paul Morie wrote:\nI ran on both platforms and saw the tests pass.\nI'm still seeing it. Won't have bandwidth to dig in personally until tomorrow.\nseeing a similar failure after a git pull\nI knew I wasn't crazy\nenvironment: fedora 21, golang: 1.4, docker: 1.6\nI think I see the problem. When I set the node name to in the test I was assuming it would parse as a valid ip address and not end up at the LookupIP call. But only the node name (and not the kubelet hostname) is being set (except in my new test where I ) so it's trying to do a lookup. Do you think you could test just changing the default hostname from \"testnode\" to \"127.0.0.1\" and see if that fixes it for you?\nTrying now\nI still get failures but no panic / threaddump.\ngist coming\nthis looks like again?\nGood that it isn't panicing any longer. I can dig into the test failures tomorrow (I think it should be relatively simple to resolve).\ncool, thanks for looking\nPasses in master now for me. Closing.\nFYI, they will break again once goes in, and then we can merge my PR to see if that fixes it for you.\n:+1:\nis in -- are these tests breaking again?\nI just rebased which I think will fix them.\nThey are breaking again.\nis on it.", "commid": "kubernetes_issue_8522", "tokennum": 407}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ee3fee3aa8419fd126391e842018dee10ac05eb62c1c61012e18754db9d5b718", "query": ". \"github.com/onsi/gomega\" ) <ins> func runLivenessTest(c *client.Client, podDescr *api.Pod) { defer GinkgoRecover() ns := \"e2e-test-\" + string(util.NewUUID()) By(fmt.Sprintf(\"Creating pod %s in namespace %s\", podDescr.Name, ns)) _, err := c.Pods(ns).Create(podDescr) Expect(err).NotTo(HaveOccurred(), fmt.Sprintf(\"creating pod %s\", podDescr.Name)) // At the end of the test, clean up by removing the pod. defer func() { By(\"deleting the pod\") c.Pods(ns).Delete(podDescr.Name) }() // Wait until the pod is not pending. (Here we need to check for something other than // 'Pending' other than checking for 'Running', since when failures occur, we go to // 'Terminated' which can cause indefinite blocking.) By(\"waiting for the pod to be something other than pending\") err = waitForPodNotPending(c, ns, podDescr.Name, 60*time.Second) Expect(err).NotTo(HaveOccurred(), fmt.Sprintf(\"starting pod %s in namespace %s\", podDescr.Name, ns)) By(fmt.Sprintf(\"Started pod %s in namespace %s\", podDescr.Name, ns)) // Check the pod's current state and verify that restartCount is present. By(\"checking the pod's current state and verifying that restartCount is present\") pod, err := c.Pods(ns).Get(podDescr.Name) Expect(err).NotTo(HaveOccurred(), fmt.Sprintf(\"getting pod %s in namespace %s\", podDescr.Name, ns)) initialRestartCount := pod.Status.Info[\"liveness\"].RestartCount By(fmt.Sprintf(\"Initial restart count of pod %s is %d\", podDescr.Name, initialRestartCount)) // Wait for at most 48 * 5 = 240s = 4 minutes until restartCount is incremented pass := false for i := 0; i < 48; i++ { // Wait until restartCount is incremented. time.Sleep(5 * time.Second) pod, err = c.Pods(ns).Get(podDescr.Name) Expect(err).NotTo(HaveOccurred(), fmt.Sprintf(\"getting pod %s\", podDescr.Name)) restartCount := pod.Status.Info[\"liveness\"].RestartCount By(fmt.Sprintf(\"Restart count of pod %s in namespace %s is now %d\", podDescr.Name, ns, restartCount)) if restartCount > initialRestartCount { By(fmt.Sprintf(\"Restart count of pod %s in namespace %s increased from %d to %d during the test\", podDescr.Name, ns, initialRestartCount, restartCount)) pass = true break } } if !pass { Fail(fmt.Sprintf(\"Did not see the restart count of pod %s in namespace %s increase from %d during the test\", podDescr.Name, ns, initialRestartCount)) } } </ins> var _ = Describe(\"Pods\", func() { <del> var ( c *client.Client ) </del> <ins> var c *client.Client </ins> BeforeEach(func() { var err error", "positive_passages": [{"docid": "doc-en-kubernetes-563adcd071a3c6fe544aec5f1bf507590a5c621259a5e37f4edab1ba22b77da9", "text": "Park of ginkgo-ization\nPer IRC, is working on this\nPushed an update yesterday to address comments.\nwhat's the status of this? There's an issue open to de-flake this test (), but it's tough to do that if the code is in the middle of being moved to ginkgo.\nThis has been merged.", "commid": "kubernetes_issue_4253", "tokennum": 76}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ee4d8f18b2cacad9bb8703a6b1ba6c526aeed4ecc23e96f0bb56f7cb2735fba4", "query": "}, expected: &v1.Secret{ ObjectMeta: metav1.ObjectMeta{ <del> Name: \"foo-94759gc65b\", </del> <ins> Name: \"foo-548cm7fgdh\", </ins> }, Data: map[string][]byte{ <del> v1.DockerConfigKey: secretData, </del> <ins> v1.DockerConfigJsonKey: secretData, </ins> }, <del> Type: v1.SecretTypeDockercfg, </del> <ins> Type: v1.SecretTypeDockerConfigJson, </ins> }, expectErr: false, },", "positive_passages": [{"docid": "doc-en-kubernetes-4279a6f285666ec67ce8924ca9393c19176af7de5707dd42a5f4c239ba12ead2", "text": "/kind bug We're having trouble retrieving images from a private registry on DockerCloud. For nearly a year the following has worked flawlessly. Last Friday I pulled down the 1.9.0 CLI (via brew) and since then have not been able to access any image in a private registry on DockerCloud. I've tried this on 10+ brand new clusters created with kops v1.8.0. The Kubernetes cluster version have been 1.8.0, 1.8.4, 1.8.5 and 1.9.0 (which is not supported by kops yet) and all exhibit the same problem. We create the secret as such: And verify it using: Which yields: And create a test service with with these contents: The pod fails immediatly with: I've reviewed the 1.9.0 release notes and nothing jumps out as the root cause. For reference I've tried putting quotes around the value when creating the secret to no avail. I've also tried prefixing the value with , so the full value would read: also to no avail. Environment: Kubernetes version: Cloud provider and installation info: AWS cluster built with Kops 1.8.0, using (to isolate this issue) nearly the default settings for everything.\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI have same problem, and I \"solved\" it creating a docker-registry secret in an old kubernetes version and pasting it on new kubernetes\nI'm recently (I know it worked perfectly about last month) facing issues with as well. For me it ended in a similar manner saying: I was able to confirm, that this is a kubernetes CLI related issue and not end user. Based on and this I was able to create properly formatted auth information looking like this: . When encoding this one-liner using (MacOS workstation) and apply like this works fine and images can be pulled from private repository again.", "commid": "kubernetes_issue_57427", "tokennum": 466}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ee4d8f18b2cacad9bb8703a6b1ba6c526aeed4ecc23e96f0bb56f7cb2735fba4", "query": "}, expected: &v1.Secret{ ObjectMeta: metav1.ObjectMeta{ <del> Name: \"foo-94759gc65b\", </del> <ins> Name: \"foo-548cm7fgdh\", </ins> }, Data: map[string][]byte{ <del> v1.DockerConfigKey: secretData, </del> <ins> v1.DockerConfigJsonKey: secretData, </ins> }, <del> Type: v1.SecretTypeDockercfg, </del> <ins> Type: v1.SecretTypeDockerConfigJson, </ins> }, expectErr: false, },", "positive_passages": [{"docid": "doc-en-kubernetes-784638a373a6d25c569537512411337ba05226e31cffa99d23b394dffb534564", "text": "However this breaks all automation and can't be considered as solution Confirmed working with kubectl 1.8.5 and server 1.8.4 (guess 1.7.9 as well)\nlooks like there's an extra \"auths\" element when adding the secret using 1.9 kubectl\nAdded in /assign\nMany thanks for the quick fix on this. Any idea when this might get rolled out? Also, it might be a good idea if this was to the known issue list for v1.9.0. It would have saved us a bunch of time trying to track down the root cause. Just trying to make sure no one else needs to do the same.\nlinking to the \"v1.9.0 known issues\" list\nack, asking Mehdy since he is the patch manager for v1.9 branch. Mehdy, any idea when we can ship 1.9.1 with this fix?\nworkarounds for folks until 1.9.1 is released: if you have a .dockerconfigjson for your private registry already, you can manually specify the type and data key (e.g. ) if you don't have a .dockerconfigjson file already, you can fix up the secret produced by manually: the type from to the data key from to the modified secret with\n1 will be released tomorrow\nI can confirm solution works, thanks so much!\nI am still having issues in 1.9.1. This worked in the 1.8.x branches: results in the following error:\nyou have to remove the gitlab-registry secret before you can apply an update... type is immutable, and the fix in 1.9.1 required changing the type of the secret", "commid": "kubernetes_issue_57427", "tokennum": 370}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ee69cca9db8679a883cd636097bcb282c6d8ddcd097af662686fcb77ed14cbc6", "query": "} } <del> azClientConfig := &azClientConfig{ subscriptionID:                 config.SubscriptionID, resourceManagerEndpoint:        env.ResourceManagerEndpoint, servicePrincipalToken:          servicePrincipalToken, rateLimiterReader:              operationPollRateLimiter, rateLimiterWriter:              operationPollRateLimiterWrite, CloudProviderBackoffRetries:    config.CloudProviderBackoffRetries, CloudProviderBackoffDuration:   config.CloudProviderBackoffDuration, ShouldOmitCloudProviderBackoff: config.shouldOmitCloudProviderBackoff(), } </del> az := Cloud{ Config:                 *config, Environment:            *env,", "positive_passages": [{"docid": "doc-en-kubernetes-effe9bff1df2586252b385cbf4a7cacd04cb77f4739ff9c987e63818f9dc1c82", "text": "Currently there is no way to run without any identity (be it service principal or E/MSI). In reality code running on a worker node can use via - and only via - without the need to access ARM. Here is the proposed change a new mode authN = this mode, is basically telling the cloud provider to work any identity, this means only IMDS calls is allowed. This mode can be detected from if no SPN set and both MSI settings are set to . to use a config map within the cluster. This config map can be loaded on the cluster statically. or created - if not existent - in that then only is used in The net new result of the above is users bootstrapping clusters can configure the worker node to use without any identity on said worker nodes.\n/sig azure These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by \u200d\nIn-tree AzureDisk volume plugin is also depending on Azure credential to fetch lun id. we should figure out how to solve it without credential\nfetch disk lun id is also a dependency in kubelet code now, after my investigation, it could be removed on Linux node, while it cannot be removed on Windows node, need to change the k/k upstream code, there is a discussion on going here: , let' wait for the discussion result.\nFor Linux: 1- use IMDS my understanding is new api versions will have the disk/lun pairs. 2- don't use arm for the return of is the second parameter passed to . For Windows: I don't understand the dep on ARM for this. The above still apply, we just need to find a way to encode the value as ut return from that allow us to find the disk by on a windows machine. might be a good source for this. Ideally speaking. The value should be the same. But i will leave it for you to decide.\ncould be a good idea since currently it's a LUN num returned by Attach() and then it could be changed to the windows disk num, I will make the code change on v1.15 later, thanks for discussion.\nUpdate: PR would remove the VM API calls when getting the LUN number for AzureDisk.", "commid": "kubernetes_issue_77309", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ee8b9aed41941b9b945a491367aa16bcd59f97c291acdf1b7c6d3f1ad6f51c6e", "query": "// InstanceShutdownByProviderID returns true if the instance is in safe state to detach volumes func (vs *VSphere) InstanceShutdownByProviderID(ctx context.Context, providerID string) (bool, error) { <del> return false, cloudprovider.NotImplemented </del> <ins> nodeName, err := vs.GetNodeNameFromProviderID(providerID) if err != nil { glog.Errorf(\"Error while getting nodename for providerID %s\", providerID) return false, err } vsi, err := vs.getVSphereInstance(convertToK8sType(nodeName)) if err != nil { return false, err } // Ensure client is logged in and session is valid if err := vs.nodeManager.vcConnect(ctx, vsi); err != nil { return false, err } vm, err := vs.getVMFromNodeName(ctx, convertToK8sType(nodeName)) if err != nil { glog.Errorf(\"Failed to get VM object for node: %q. err: +%v\", nodeName, err) return false, err } isActive, err := vm.IsActive(ctx) if err != nil { glog.Errorf(\"Failed to check whether node %q is active. err: %+v.\", nodeName, err) return false, err } return !isActive, nil </ins> } // InstanceID returns the cloud provider ID of the node with the specified Name.", "positive_passages": [{"docid": "doc-en-kubernetes-8cc0000ebdb21aeba4d3dda4212069010f35d863300d721e65a4eeef908ef7b3", "text": "As planned for 1.12 in kubernetes/features: After , the next step is to add the logic to the reconciler to detach the volumes when the nodeShutdown taint is applied. /assign /sig storage /kind feature looping\nHow do you know that node is Shutdown? is it a planned shutdown or a unplanned shutdown?\nAFAIK regardless of whether it's planned or not, it's detected by the cloud provider. In case of bare-metal node it doesn't happen automatically, as there is no universal way to reliably determine if a node is powered off, so the node must be tainted as by some external source.\nIssues 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\nany update on this issue?\n, I am currently working with sig-node team on handling node shut down. I will make a proposal and discuss in sig-node meeting next Tuesday. Will post the update soon.\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten /kind bug /priority critical-urgent /assign /sig node\nThose labels are not set on the issue: <detailsIn response to : /remove-kind feature 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\nIssues 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\nany update on this? is it going to be part of 1.15?\nStale issues rot after 30d of inactivity. Mark the issue as fresh with .", "commid": "kubernetes_issue_66181", "tokennum": 511}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ee8b9aed41941b9b945a491367aa16bcd59f97c291acdf1b7c6d3f1ad6f51c6e", "query": "// InstanceShutdownByProviderID returns true if the instance is in safe state to detach volumes func (vs *VSphere) InstanceShutdownByProviderID(ctx context.Context, providerID string) (bool, error) { <del> return false, cloudprovider.NotImplemented </del> <ins> nodeName, err := vs.GetNodeNameFromProviderID(providerID) if err != nil { glog.Errorf(\"Error while getting nodename for providerID %s\", providerID) return false, err } vsi, err := vs.getVSphereInstance(convertToK8sType(nodeName)) if err != nil { return false, err } // Ensure client is logged in and session is valid if err := vs.nodeManager.vcConnect(ctx, vsi); err != nil { return false, err } vm, err := vs.getVMFromNodeName(ctx, convertToK8sType(nodeName)) if err != nil { glog.Errorf(\"Failed to get VM object for node: %q. err: +%v\", nodeName, err) return false, err } isActive, err := vm.IsActive(ctx) if err != nil { glog.Errorf(\"Failed to check whether node %q is active. err: %+v.\", nodeName, err) return false, err } return !isActive, nil </ins> } // InstanceID returns the cloud provider ID of the node with the specified Name.", "positive_passages": [{"docid": "doc-en-kubernetes-8b5c9612057f9871f14258bc136d8e86f57d2327861ec200bbe8402ae4819108", "text": "Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten\nIssues 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\n/remove-lifecycle stale\n/priority important-longterm\nIssues 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\n/remove-lifecycle stale /lifecycle frozen\n/triage accepted /kind feature\nThis 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\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI think this can be closed now as we have non-graceful node shutdown.\n/close\nClosing 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", "commid": "kubernetes_issue_66181", "tokennum": 436}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ee99c3a5e67af59161972ddca25be031a40ea44c68e419b0d1f1f21c8c2b6c62", "query": "if s.ServiceClusterIPRange.IP == nil { glog.Fatal(\"No --service-cluster-ip-range specified\") } <ins> var ones, bits = s.ServiceClusterIPRange.Mask.Size() if bits-ones > 20 { glog.Fatal(\"Specified --service-cluster-ip-range is too large\") } </ins> } func newEtcd(etcdConfigFile string, etcdServerList []string, interfacesFunc meta.VersionInterfacesFunc, defaultVersion, storageVersion, pathPrefix string) (etcdStorage storage.Interface, err error) {", "positive_passages": [{"docid": "doc-en-kubernetes-e8ea4b3822c8b6f9f15485ce88ff27518f982ee5d47e8079beb9d976426a7864", "text": "If you spec a /8 for your service Cluster IPs, the bitmask becomes 2 MB, which is too big for etcd. We should enforce that the prefix be /12 or smaller or something like that.\nYes", "commid": "kubernetes_issue_12820", "tokennum": 46}], "negative_passages": []}
{"query_id": "q-en-kubernetes-eec1b25dcc12c0da2d2a53d066baa741d4e49d9109d20fabb05ee1e87edac6c5", "query": "} <ins> func WaitForRootPaths(t *testing.T, ctx context.Context, client testClient, requirePaths, forbidPaths sets.Set[string]) error { return wait.PollUntilContextTimeout(ctx, 250*time.Millisecond, maxTimeout, true, func(ctx context.Context) (done bool, err error) { statusContent, err := client.Discovery().RESTClient().Get().AbsPath(\"/\").SetHeader(\"Accept\", \"application/json\").DoRaw(ctx) if err != nil { return false, err } rootPaths := metav1.RootPaths{} if err := json.Unmarshal(statusContent, &rootPaths); err != nil { return false, err } paths := sets.New(rootPaths.Paths...) if missing := requirePaths.Difference(paths); len(missing) > 0 { t.Logf(\"missing required root paths %v\", sets.List(missing)) return false, nil } if present := forbidPaths.Intersection(paths); len(present) > 0 { t.Logf(\"present forbidden root paths %v\", sets.List(present)) return false, nil } return true, nil }) } </ins> func WaitForGroups(ctx context.Context, client testClient, groups ...apidiscoveryv2beta1.APIGroupDiscovery) error { return WaitForResultWithCondition(ctx, client, func(groupList apidiscoveryv2beta1.APIGroupDiscoveryList) bool { for _, searchGroup := range groups {", "positive_passages": [{"docid": "doc-en-kubernetes-a36678f387087dd8252401a5249426873ced2ebb26644cae4efea96ce80ca1f6", "text": "reported that conformance testing with the latest version of sonobuoy against a version 1.29.0-alpha.3 cluster fails on the support the 1.17 Sample API Server using the current Aggregator test: , related to I found the reason why the test is working fine in Kubernetes CI jobs but fails with sonobuoy is because the service account used by sonobuoy \"sonobuoy-serviceaccount\" doesn't have read permission of the non-resource url \"/\", which is used by the test to confirm the removal of group path: The permission of \"sonobuoy-serviceaccount\" is as below: There may be two ways to fix it: the RBAC rule of sonobuoy to include \"get\" of \"/\". However, could other test runners encounter this issue? Is there a doc listing the required permissions for running e2e tests? the e2e to skip checking the removal of the group path if the service account doesn't have permission to access the root path. Which way do we usually prefer? Running e2e with sonobuoy should succeed. a v1.29.0-alpha.3 cluster. No response <details</details<details</details<details</details<details</details<details</details<details</details\nimplemented this solution.\n/sig api-machinery\nthank you for opening this issue and working on a solution. I'm probably not the right person to decide on which solution is preferred. From my perspective, either solution is fine.\nNote: Sonobuoy is not owned by any Kubernetes SIG. At most it is between SIG Architecture and the CNCF to choose whether to recommend it for running tests. SIG Testing owns the e2e image that sonobuoy can be used to schedule but not sonobuoy. IMHO this is a bug in running the tests via a pod, which is not how we develop the tests (they're run outside the cluster, by a cluster admin account typically). I would say 1) is the correct answer. xref: /sig architecture /sig testing /triage accepted cc\nthanks for your comment. I guess 1) means non of the existing sonobuoy versions can pass K8s conformance test against a cluster 1.29.0-alpha3, as the RBAC rule is hardcoded.", "commid": "kubernetes_issue_121985", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-eec1b25dcc12c0da2d2a53d066baa741d4e49d9109d20fabb05ee1e87edac6c5", "query": "} <ins> func WaitForRootPaths(t *testing.T, ctx context.Context, client testClient, requirePaths, forbidPaths sets.Set[string]) error { return wait.PollUntilContextTimeout(ctx, 250*time.Millisecond, maxTimeout, true, func(ctx context.Context) (done bool, err error) { statusContent, err := client.Discovery().RESTClient().Get().AbsPath(\"/\").SetHeader(\"Accept\", \"application/json\").DoRaw(ctx) if err != nil { return false, err } rootPaths := metav1.RootPaths{} if err := json.Unmarshal(statusContent, &rootPaths); err != nil { return false, err } paths := sets.New(rootPaths.Paths...) if missing := requirePaths.Difference(paths); len(missing) > 0 { t.Logf(\"missing required root paths %v\", sets.List(missing)) return false, nil } if present := forbidPaths.Intersection(paths); len(present) > 0 { t.Logf(\"present forbidden root paths %v\", sets.List(present)) return false, nil } return true, nil }) } </ins> func WaitForGroups(ctx context.Context, client testClient, groups ...apidiscoveryv2beta1.APIGroupDiscovery) error { return WaitForResultWithCondition(ctx, client, func(groupList apidiscoveryv2beta1.APIGroupDiscoveryList) bool { for _, searchGroup := range groups {", "positive_passages": [{"docid": "doc-en-kubernetes-4545476cbce0605bfe46d5a01c41b8f4cf7b5ac07772bfb1748611bc506e90ef", "text": "I will file an issue to sonobuoy first.\nquestion here is what are the set of client permissions required to run the conformance suite? perhaps a level of access or a more granular recommendation should be documented. what is your take on the root path requirement as approver for: EDIT: slack thread:\nI agree, we already require e.g. privileged pods for a long time in conformance tests and we should make it clear that we expect a highly privileged client.\n+1 for what is saying, that we should expect that the user running the tests has required permissions. These tests are not built for being run unprivileged.\ni wanted to PR the admin note in our conformance docs under sig-arch, but then i saw this: so broke this guarantee. sounds like SIG Arch needs to comment.\nThis statement surprises me. Root discovery is one of the least-privileged permissions you can have on a cluster. For years this was even open for unauthorized users on the internet (if your api endpoint has been exposed). In other words, just add the permission. While thinking about it, it is surprising that the user in question does not have this access already. Don't we allow that for every authorized user?\nIn contrast, I hope that lots of privileged operations are tested by conformance today. If we don't test things like admission webhooks for example, we have much bigger problems. And admission webhooks are basically equivalent to cluster-admin.\nthat is outdated, we use hostNetwork pods one some of the tests IIRC\nlooks like we don't. before this ticket, i was under the impression that the conformance suite already requires admin and that all testers (like Sonobuoy) use admin level credentials. it is non-privileged (e.g., does not require root on nodes, access to raw network interfaces, or cluster admin permissions) looks like we may have to change that sentence completely.\nWould have expected it here: The PR in question explicitly fixes the result returned by . If that is part of conformance (IMO it should), every conformance test needs access it obviously. Whether we require admin, or we add it manually, either would work.", "commid": "kubernetes_issue_121985", "tokennum": 474}], "negative_passages": []}
{"query_id": "q-en-kubernetes-eec1b25dcc12c0da2d2a53d066baa741d4e49d9109d20fabb05ee1e87edac6c5", "query": "} <ins> func WaitForRootPaths(t *testing.T, ctx context.Context, client testClient, requirePaths, forbidPaths sets.Set[string]) error { return wait.PollUntilContextTimeout(ctx, 250*time.Millisecond, maxTimeout, true, func(ctx context.Context) (done bool, err error) { statusContent, err := client.Discovery().RESTClient().Get().AbsPath(\"/\").SetHeader(\"Accept\", \"application/json\").DoRaw(ctx) if err != nil { return false, err } rootPaths := metav1.RootPaths{} if err := json.Unmarshal(statusContent, &rootPaths); err != nil { return false, err } paths := sets.New(rootPaths.Paths...) if missing := requirePaths.Difference(paths); len(missing) > 0 { t.Logf(\"missing required root paths %v\", sets.List(missing)) return false, nil } if present := forbidPaths.Intersection(paths); len(present) > 0 { t.Logf(\"present forbidden root paths %v\", sets.List(present)) return false, nil } return true, nil }) } </ins> func WaitForGroups(ctx context.Context, client testClient, groups ...apidiscoveryv2beta1.APIGroupDiscovery) error { return WaitForResultWithCondition(ctx, client, func(groupList apidiscoveryv2beta1.APIGroupDiscoveryList) bool { for _, searchGroup := range groups {", "positive_passages": [{"docid": "doc-en-kubernetes-06abc1218304c92779dae2744e33107a4d26263c1c54e4453f3f92a1949c2aa2", "text": "adding to milestone and making release blocking ... we should not release 1.29 in a state that the most commonly used conformance tool will fail\nIMO we should clarify the state and go fix the tool, but we should keep the test and we should NOT add skip. Conformance docs are not a release artifact, and sonobuoy release lifecycle is not a conformance artifact. If we can't get sonobuoy working in a reasonable time, we already know the tests can be run by scheduling the image (which is ours) directly with kubectl instead and we can document that in the upstream conformance docs. We need to fix the for this image: ,%20master%20(dev) And it should probably be to release-blocking in the future.\nit looks like the e2e change made in was not consciously made part of conformance, it was just trying to functionally test the bugfix being made. For 1.29, I think we should revert the change to and make an integration test that validates the fix instead. We can revisit whether content of is part of conformance or not for 1.30\nI opened to revert the e2e change and move the functional test to an integration test\nFiled to try to get the image job passing again.\nWe probably need another issue to track 1.30 follow-up?\nIf no one has done it, I could create another issue and follow up with the items that have been discussed here: outdated privilege requirement in commonly used conformance tools like sonobuoy aware of the required priviledge to avoid similar situations in the future. permission of GET \"/\" to authorized users via the role for root discovery.", "commid": "kubernetes_issue_121985", "tokennum": 357}], "negative_passages": []}
{"query_id": "q-en-kubernetes-eee282261b8c52a658a83eac8fa40a41907ce25ad97ce7bb920ad092f7231caa", "query": "fakeDocker.VersionInfo = []string{} kubeClient.ReactFn = testclient.NewSimpleFake(&api.NodeList{Items: []api.Node{ <del> {ObjectMeta: api.ObjectMeta{Name: \"127.0.0.1\"}}, </del> <ins> {ObjectMeta: api.ObjectMeta{Name: testKubeletHostname}}, </ins> }}).ReactFn mockCadvisor := testKubelet.fakeCadvisor machineInfo := &cadvisorApi.MachineInfo{", "positive_passages": [{"docid": "doc-en-kubernetes-d16ca614c05197aa8b2652e3bf008c3a9a5ce41d960188a2ba3459b13d8b1102", "text": "Looks like some kubelet unit tests perform a lookupIp which ends up depending on the health of the local resolver. Specifically has this failing: Which leads to the test in: And we recently swapped out the node names from testnode to 127.0.0.1, so probably the culprit?\n/ref\nInteresting. I did swap out the node names in the unit test as part of to be 127.0.0.1, party because I thought that it wouldn't have any problems resolving during unit tests.\n/cc", "commid": "kubernetes_issue_8549", "tokennum": 113}], "negative_passages": []}
{"query_id": "q-en-kubernetes-eee282261b8c52a658a83eac8fa40a41907ce25ad97ce7bb920ad092f7231caa", "query": "fakeDocker.VersionInfo = []string{} kubeClient.ReactFn = testclient.NewSimpleFake(&api.NodeList{Items: []api.Node{ <del> {ObjectMeta: api.ObjectMeta{Name: \"127.0.0.1\"}}, </del> <ins> {ObjectMeta: api.ObjectMeta{Name: testKubeletHostname}}, </ins> }}).ReactFn mockCadvisor := testKubelet.fakeCadvisor machineInfo := &cadvisorApi.MachineInfo{", "positive_passages": [{"docid": "doc-en-kubernetes-4a4c75dd985aaeba56d487bbde17d68f0425afc5d7e1167fdf1a1abcb97cd0b6", "text": "cc\nWhat is the environment where you are running the tests? They pass for me on my mac, a linux box, and shippable seems to be passing them as well.\nI couldn 't reproduce the failure either.\nI'm out right now; i'll try them when i get back. For the record, I run hack/test- Paul Morie wrote:\nAhem FTR This acronym is going to go quad-plat Paul Morie wrote:\nI ran on both platforms and saw the tests pass.\nI'm still seeing it. Won't have bandwidth to dig in personally until tomorrow.\nseeing a similar failure after a git pull\nI knew I wasn't crazy\nenvironment: fedora 21, golang: 1.4, docker: 1.6\nI think I see the problem. When I set the node name to in the test I was assuming it would parse as a valid ip address and not end up at the LookupIP call. But only the node name (and not the kubelet hostname) is being set (except in my new test where I ) so it's trying to do a lookup. Do you think you could test just changing the default hostname from \"testnode\" to \"127.0.0.1\" and see if that fixes it for you?\nTrying now\nI still get failures but no panic / threaddump.\ngist coming\nthis looks like again?\nGood that it isn't panicing any longer. I can dig into the test failures tomorrow (I think it should be relatively simple to resolve).\ncool, thanks for looking\nPasses in master now for me. Closing.\nFYI, they will break again once goes in, and then we can merge my PR to see if that fixes it for you.\n:+1:\nis in -- are these tests breaking again?\nI just rebased which I think will fix them.\nThey are breaking again.\nis on it.", "commid": "kubernetes_issue_8522", "tokennum": 407}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ef0515e6be4cb4ec7253b751f4c21fdf0dd7f85449cb555f5789e67d6f2a86ac", "query": "// a map[family]ip for the caller to release when everything else has // executed successfully func (rs *REST) handleClusterIPsForUpdatedService(oldService *api.Service, service *api.Service) (allocated map[api.IPFamily]string, toRelease map[api.IPFamily]string, err error) { <ins> // We don't want to upgrade (add an IP) or downgrade (remove an IP) // following a cluster downgrade/upgrade to/from dual-stackness // a PreferDualStack service following principle of least surprise // That means: PreferDualStack service will only be upgraded // if: // - changes type to RequireDualStack // - manually adding or removing ClusterIP (secondary) // - manually adding or removing IPFamily (secondary) if isMatchingPreferDualStackClusterIPFields(oldService, service) { return allocated, toRelease, nil // nothing more to do. } </ins> // use cases: // A: service changing types from ExternalName TO ClusterIP types ==> allocate all new // B: service changing types from ClusterIP types TO ExternalName ==> release all allocated", "positive_passages": [{"docid": "doc-en-kubernetes-572d0164a11730b1ec949ed970afee14cdb12823b4b7a698fae66a86d82f748e", "text": "1) start with a single stack cluster 2) create a PreferDualStack service 3) configure API server with a 2nd service CIDR 4) Confirm the above service is not dual-stack 5) Add a label to the above service 6) Observe that the service becomes dual-stack I think the correct answer is to have a \"repair loop\" that upgrades (and downgrades!) PreferDualStack Services to match the config. I think this is a GA blocker.\n/triage accepted The current thought is: of type with are special new breed of api objects that I don't think we have any similar precedent in the apis, i could be wrong. Their behavior is tied to how the cluster is configured. Thus their behavior must change as the cluster behavior change. a way the user is stating . If it is cluster then i am good with two ClusterIPs. If it is single stack cluster then I am also good with a single ClusterIP. One can assume that if the user was ok was with getting a additional IP when possible then they must be ok with taking it away when it is no longer possible. Based on the above I believe best course of action is create a new repair loop or piggyback on any of the existing (or better: fix it in rest stack during list and get calls). The new logic takes care of matching to the .\nreproducer and regression test if somebody takes this, feel free to add it\nack - Scheduled to tackle 3rd week of May. Will definitely include that patch.", "commid": "kubernetes_issue_101681", "tokennum": 322}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ef12fe4f3586ed116f8e231201ec307317ecd6744596b51b00a6fd8ca5c26e68", "query": "//\t    - ... zero or more // // * every specified field or array in s is also specified outside of value validation. <ins> // * metadata at the root can only restrict the name and generateName, and not be specified at all in nested contexts. </ins> // * additionalProperties at the root is not allowed. func ValidateStructural(s *Structural, fldPath *field.Path) field.ErrorList { allErrs := field.ErrorList{}", "positive_passages": [{"docid": "doc-en-kubernetes-4be11de3bdb9e2a86ad3a19c4d6f5342db422d48e5979c118fca9ce077f64900", "text": "We allow CRD authors to write . Currently we don't restrict writing validation for , which means people can have . For example, people can have additive name constraints (require CR to be ) with the following schema: This brings us two questions: do we if \"metadata\" is included in the schema: simplest option is to publish standard metav1.ObjectMeta schema info, and use any CRD-specified \"metadata\" properties as additive validation (just like in-tree types do, publishing standard ObjectMeta schema info, and implementing type-specific name validation internally) alternatively, we can try merging user-specified metadata schema with the standard one. Technically people should only add extra validation to existing metadata properties (adding new fields to metadata won't work since they will be pruned by built-in validation first), but it's unclear to me how arbitrary people may want the metadata validation to be term question is whether to allow people specifying metadata validation at all, or just allow a subset (like name validation) in CRD v1 /sig api-machinery /area custom-resources cc\nWhat is the difference between these two? I mean the end result is the same right? The only thing that can be is validation. Nothing else works unless you are considering extensions?\nThe former means we drop/hide user-specified metadata schema when we publish CRD OpenAPI. We still validate user-specified constraints on server side, but client-side validation won't see them. The latter enables client-side user-specified metadata validation.\nIf it's possible to merge with standard metadata schema info, or at the cost of not publishing the standard schema. My inclination would be to publish the complete standard schema for metadata/apiVersion/kind, which we know is complete and accurate, and use and user-specified schema for those fields as addition validations server side", "commid": "kubernetes_issue_74620", "tokennum": 396}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ef1b244cd33e87b21ca79e802b9ce9e42075cbeac38f60e97aacf03fe9fd99c4", "query": "kr.CustomMustRegister(cs...) } <ins> // BuildVersion is a helper function that can be easily mocked. var BuildVersion = version.Get </ins> func newKubeRegistry(v apimachineryversion.Info) *kubeRegistry { r := &kubeRegistry{ PromRegistry:     prometheus.NewRegistry(),", "positive_passages": [{"docid": "doc-en-kubernetes-b57bf0f1b2dd71c1293d1dafb95c6e51debc5c1d26878053edb8d335b76a3a11", "text": "What would you like to be : Once a metric be deprecated, we should update the unit test accordingly if there is any. We need to work out a way for a unit test freely select codebase version, and also should make sure the unit test won't fail in the subsequent release. Why is this needed: Deprecated also needs to be protected. /sig instrumentation /assign", "commid": "kubernetes_issue_86292", "tokennum": 81}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ef1f0ad51ca30526af38fa6481977cc1b9513e0aaa7290c03e1f84837680ad8d", "query": "// Store in cache c.lock.Lock() <ins> defer c.lock.Unlock() </ins> c.cache[key] = data <del> c.lock.Unlock() </del> // Remove in flight entry c.inFlightLock.Lock() <ins> defer c.inFlightLock.Unlock() </ins> delete(c.inFlight, key) <del> c.inFlightLock.Unlock() </del> }() return result }", "positive_passages": [{"docid": "doc-en-kubernetes-0882877f8aa87dd9f2fab7aa6c2163d630c073e98d0481f7c1762728faaae3b6", "text": "Failed due to an apparently unrelated PR: https://travis-\nProblem here is that I left a small chance of a double-call in my parallelized cache. Didn't realize this was being tested. Will fix.", "commid": "kubernetes_issue_3439", "tokennum": 46}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ef5027f2e80ba966164cd7425c1da49117430a50ad96dfeba74828a290e5bc4d", "query": "clientset \"k8s.io/client-go/kubernetes\" kubeadmapi \"k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm\" kubeadmconstants \"k8s.io/kubernetes/cmd/kubeadm/app/constants\" <ins> \"k8s.io/kubernetes/cmd/kubeadm/app/features\" </ins> kubeadmutil \"k8s.io/kubernetes/cmd/kubeadm/app/util\" \"k8s.io/kubernetes/cmd/kubeadm/app/util/apiclient\" \"k8s.io/kubernetes/pkg/api/legacyscheme\"", "positive_passages": [{"docid": "doc-en-kubernetes-fdf6c8e5598e80992f62cef52eca112e7ba1d532fe8ace89dc932a5edac53dea", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: Currently, IPVS proxier does not run any e2e test cases. What you expected to happen: I think it's important to create test suite for IPVS in upstream CI which will help a lot in moving IPVS existing alpha. Anything else we need to know?: Let's work together. /sig network\nSelf /assign\nThere are to ways to do this work: , but doesn't support any kube-proxy config right now, so I had this pr , and also, need support it too, see this pr: kubernetes/kubernetes-anywhere build cluster. See this pr: kubernetes/test-infra The second way is much easier and faster, but I was told they gonna deprecated the , so in the long term, we still need and 's support. If anybody have better way or have some suggestion about this, please let me know, I'll be really appreciate, Thanks.", "commid": "kubernetes_issue_52834", "tokennum": 247}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ef6c01cf4b16b0d168813095c59ba55091c5282d70f2e81e01519ad6fe894d86", "query": "} func (flunderStrategy) NamespaceScoped() bool { <del> return false </del> <ins> return true </ins> } func (flunderStrategy) PrepareForCreate(ctx genericapirequest.Context, obj runtime.Object) {", "positive_passages": [{"docid": "doc-en-kubernetes-6e9547d1b77f5f5e67275f7358d2b648055755d378e63a99679bc29fa4f8a944", "text": "1 tests failed, 11 jobs failed, 241 builds failed. Failure stats cover 1 day time range '17 Aug 2017 22:57 UTC' to '18 Aug 2017 22:57 UTC'.\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\nSeeing this failure on the e2e release-master-blocking https://k8s- Example failure https://k8s- Looks like an RBAC issue cc\nthis is currently blocking the alpha.3 release\nlooks like this new test was by in which was merged about 6 days ago and is failing consistently\nThis has started failing again on our GKE test suite https://k8s- https://k8s- cc\n[MILESTONENOTIFIER] Milestone Labels Complete Issue label settings: sig/api-machinery: Issue will be escalated to these SIGs if needed. priority/critical-urgent: Never automatically move out of a release milestone; continually escalate to contributor and SIG through all available channels. kind/bug: Fixes a bug discovered during the current release. <detailsAdditional instructions available <a href=\"\"here</aThe commands available for adding these labels are documented <a href=\"\"here</a</details\n/assign\nSeems to be flaking now with the error: https://k8s-\n- we need to determine (today if possible) if this is truly release blocking. If so, please add the release-blocker label. And, if not, how do we best continue work on this for 1.8.x/1.9.0?\nthis test has two passes and four failures on the same commit I'm seeing gke-specific authz grants in that test that are incorrect: That commit removed the wait for the authz grant to become effective (which can lead to flakes), and granted superuser permissions to all users, which is incorrect and invalidates any other authz-related tests run in parallel with this test\ncc\nI can add the wait back.", "commid": "kubernetes_issue_50945", "tokennum": 509}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ef6c01cf4b16b0d168813095c59ba55091c5282d70f2e81e01519ad6fe894d86", "query": "} func (flunderStrategy) NamespaceScoped() bool { <del> return false </del> <ins> return true </ins> } func (flunderStrategy) PrepareForCreate(ctx genericapirequest.Context, obj runtime.Object) {", "positive_passages": [{"docid": "doc-en-kubernetes-44c35af259d5583c472df6fa7f370aa48aa2c399176d09a89c981e3feb3444e5", "text": "edit: and fix the test given admin to all authenticated users.\nActually after staring at this test for about half an hour I can't figure out what different users exist or what permissions they're being granted. ClientSet, InternalClientset, and AggregatorClient are all initialized from the same config so I don't see how one would be able to create an RBAC binding but another would fail later. any thoughts here?\nI honestly think the gke specific BindClusterRole is a red-herring. It is needed so the client has permission to perform one of the setup steps. (I think it was either to create the wardler cluster role or to bind that role to the anonymous user) Once that setup step is complete we no longer need the that cluster role bound and so I don't think its related.\nThe gke authorizer allows the \u201cbind\u201d verb, so the client can create a binding to the cluster-admin. It cannot create a role directly unless it has permissions via RBAC. Since we don\u2019t have a way to determine the username associated with , binding to all authenticated users is what was done as a workaround.\nI agree that the point at which the tests are failing indicate that the previous authorization issues are not the cause.\n/open\n/reopen\nSo a lot more information to work with now but the error is still occurring. I am still looking into this.\nany update on the investigation?\nFriendly v1.8 release team ping. This failure still seems to be happening, is this actively being worked? Does this need to be in the v1.8 milestone?", "commid": "kubernetes_issue_50945", "tokennum": 342}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ef723f15c3671a933c56b0676b1e103aa96d98aac362d165a8e7253b04a20167", "query": "return rs.releaseClusterIPs(toRelease) } <ins> // tests if two preferred dual-stack service have matching ClusterIPFields // assumption: old service is a valid, default service (e.g., loaded from store) func isMatchingPreferDualStackClusterIPFields(oldService, service *api.Service) bool { if oldService == nil { return false } if service.Spec.IPFamilyPolicy == nil { return false } // if type mutated then it is an update // that needs to run through the entire process. if oldService.Spec.Type != service.Spec.Type { return false } // both must be type that gets an IP assigned if service.Spec.Type != api.ServiceTypeClusterIP && service.Spec.Type != api.ServiceTypeNodePort && service.Spec.Type != api.ServiceTypeLoadBalancer { return false } if oldService.Spec.Type != api.ServiceTypeClusterIP && oldService.Spec.Type != api.ServiceTypeNodePort && oldService.Spec.Type != api.ServiceTypeLoadBalancer { return false } // both must be of IPFamilyPolicy==PreferDualStack if service.Spec.IPFamilyPolicy != nil && *(service.Spec.IPFamilyPolicy) != api.IPFamilyPolicyPreferDualStack { return false } if oldService.Spec.IPFamilyPolicy != nil && *(oldService.Spec.IPFamilyPolicy) != api.IPFamilyPolicyPreferDualStack { return false } // compare ClusterIPs lengths. // due to validation. if len(service.Spec.ClusterIPs) != len(oldService.Spec.ClusterIPs) { return false } for i, ip := range service.Spec.ClusterIPs { if oldService.Spec.ClusterIPs[i] != ip { return false } } // compare IPFamilies if len(service.Spec.IPFamilies) != len(oldService.Spec.IPFamilies) { return false } for i, family := range service.Spec.IPFamilies { if oldService.Spec.IPFamilies[i] != family { return false } } // they match on // Policy: preferDualStack // ClusterIPs // IPFamilies return true } </ins> // attempts to default service ip families according to cluster configuration // while ensuring that provided families are configured on cluster. <del> func (rs *REST) tryDefaultValidateServiceClusterIPFields(service *api.Service) error { </del> <ins> func (rs *REST) tryDefaultValidateServiceClusterIPFields(oldService, service *api.Service) error { </ins> // can not do anything here if service.Spec.Type == api.ServiceTypeExternalName { return nil", "positive_passages": [{"docid": "doc-en-kubernetes-572d0164a11730b1ec949ed970afee14cdb12823b4b7a698fae66a86d82f748e", "text": "1) start with a single stack cluster 2) create a PreferDualStack service 3) configure API server with a 2nd service CIDR 4) Confirm the above service is not dual-stack 5) Add a label to the above service 6) Observe that the service becomes dual-stack I think the correct answer is to have a \"repair loop\" that upgrades (and downgrades!) PreferDualStack Services to match the config. I think this is a GA blocker.\n/triage accepted The current thought is: of type with are special new breed of api objects that I don't think we have any similar precedent in the apis, i could be wrong. Their behavior is tied to how the cluster is configured. Thus their behavior must change as the cluster behavior change. a way the user is stating . If it is cluster then i am good with two ClusterIPs. If it is single stack cluster then I am also good with a single ClusterIP. One can assume that if the user was ok was with getting a additional IP when possible then they must be ok with taking it away when it is no longer possible. Based on the above I believe best course of action is create a new repair loop or piggyback on any of the existing (or better: fix it in rest stack during list and get calls). The new logic takes care of matching to the .\nreproducer and regression test if somebody takes this, feel free to add it\nack - Scheduled to tackle 3rd week of May. Will definitely include that patch.", "commid": "kubernetes_issue_101681", "tokennum": 322}], "negative_passages": []}
{"query_id": "q-en-kubernetes-efa631d67e7f989b3d4263e96cdae7f8b737f487bb6c5a397755ca3783ded978", "query": "} } <del> func TestHistogramClear(t *testing.T) { samples := []float64{0.5, 0.5, 0.5, 0.5, 1.5, 1.5, 1.5, 1.5, 3, 3, 3, 3, 6, 6, 6, 6} bounds := []float64{1, 2, 4, 8} h := samples2Histogram(samples, bounds) if *h.SampleCount == 0 { t.Errorf(\"Expected histogram .SampleCount to be non-zero\") } if *h.SampleSum == 0 { t.Errorf(\"Expected histogram .SampleSum to be non-zero\") } for _, b := range h.Bucket { if b.CumulativeCount != nil { if *b.CumulativeCount == 0 { t.Errorf(\"Expected histogram bucket to have non-zero comulative count\") } } } h.Clear() if *h.SampleCount != 0 { t.Errorf(\"Expected histogram .SampleCount to be zero, have %v instead\", *h.SampleCount) } if *h.SampleSum != 0 { t.Errorf(\"Expected histogram .SampleSum to be zero, have %v instead\", *h.SampleSum) } for _, b := range h.Bucket { if b.CumulativeCount != nil { if *b.CumulativeCount != 0 { t.Errorf(\"Expected histogram bucket to have zero comulative count, have %v instead\", *b.CumulativeCount) } } if b.UpperBound != nil { *b.UpperBound = 0 } } } </del> func TestHistogramValidate(t *testing.T) { tests := []struct { name string", "positive_passages": [{"docid": "doc-en-kubernetes-43f40e78041c5b4f7b71fe448bfb25306103aa8e8278b5a81de2f92cd8b688c4", "text": "In the new scheduler performance testing framework, (bool) is provided to benchmark performance of pods created in an \"operator\": (L11 below) However, the initialized Pods created in L5~L7 seem to be also benchmarked, although it doesn't specify . (please see the reproduce steps below). I think it's b/c once scheduler starts, the associated Prometheus artifacts are also up, and it's a single in-memory datastore. So no matter we start to collect the metric in which step, the prometheus data is already up-to-date. In the above workload config, the final data have benchmarked 1500 pods instead of 1000 pods. I guess it won't work either if running in the pod initialization step or not. Unless we manage a breakpoint at the end of each step, and calculate delta histogram for the step that specifies . Pods created in step without are not benchmarked. Apply the following diff: And then run: You will get an output sth. like: /sig scheduling\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nCould you please help confirm if it's an issue?\ncc\nUnfortunately, does not apply for metrics gathered from . As you mentioned. The default gatherer collects all metrics produced by the scheduler. It's the scheduler itself who knows pod specs and would have to decide which pods will get ignored when updating metrics. The question is if computing metrics for a subset of pods processed by the scheduler is a valid use case.\nThis is probably what we want. Is something like that possible ?\nI think being able to absolutely ignore certain pods for metrics is an overkill.\nThe use case is to ignore the pods created in steps that don't specify , so as to collect the Pod metrics create at particular step(s) (). Otherwise, the semantics of option is quite misleading. Nope, that's not the intention. We don't need to target certain pods, like using label selector or whatever. Just as I mentioned, measure pods created at particular steps.", "commid": "kubernetes_issue_99218", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-efa631d67e7f989b3d4263e96cdae7f8b737f487bb6c5a397755ca3783ded978", "query": "} } <del> func TestHistogramClear(t *testing.T) { samples := []float64{0.5, 0.5, 0.5, 0.5, 1.5, 1.5, 1.5, 1.5, 3, 3, 3, 3, 6, 6, 6, 6} bounds := []float64{1, 2, 4, 8} h := samples2Histogram(samples, bounds) if *h.SampleCount == 0 { t.Errorf(\"Expected histogram .SampleCount to be non-zero\") } if *h.SampleSum == 0 { t.Errorf(\"Expected histogram .SampleSum to be non-zero\") } for _, b := range h.Bucket { if b.CumulativeCount != nil { if *b.CumulativeCount == 0 { t.Errorf(\"Expected histogram bucket to have non-zero comulative count\") } } } h.Clear() if *h.SampleCount != 0 { t.Errorf(\"Expected histogram .SampleCount to be zero, have %v instead\", *h.SampleCount) } if *h.SampleSum != 0 { t.Errorf(\"Expected histogram .SampleSum to be zero, have %v instead\", *h.SampleSum) } for _, b := range h.Bucket { if b.CumulativeCount != nil { if *b.CumulativeCount != 0 { t.Errorf(\"Expected histogram bucket to have zero comulative count, have %v instead\", *b.CumulativeCount) } } if b.UpperBound != nil { *b.UpperBound = 0 } } } </del> func TestHistogramValidate(t *testing.T) { tests := []struct { name string", "positive_passages": [{"docid": "doc-en-kubernetes-a8b513dba6e655a29138693e1746ea6f16e628420cb4b4aca138e84f0ed453fc", "text": "I would do something like the following: if a step has collectMetrics:false, we wait for them to finish scheduling, and then we take a snapshot of the histogram. Then for the next step that has collectMetrics:true, we take the diff with the latest snapshot to report the results. This might not be perfect, as we don't control if the metrics have finished syncing when we take the snapshot. But I think that's fine. Would doing this be possible? Now, if we have steps that run in parallel, one with collectMetrics:false and another with collectMetrics:true, then this doesn't work. Note that I don't know the details of how the gatherer works.\nThat adheres to what I have in my mind - we can only manage this on client side. I think it's fine. As we are already fetching the \"snapshot\" when pods get scheduled when equals true. True. An alternative is to design the case to be like: the step with to employ Pods that are all unschedulable, and then specify a custom metric \"schedulere2eschedulingdurationseconds[result=\"unschedulable\"]\" to target a particular histogram instead of all histograms (default option) inside a histogramVec. Note this can only be possible when and some subsequent changes get in place.\nWe might just call Histogram.Clear() method which will clear what has been collected so far at the end of phase: Assuming individual phases have no pods in common and each phase can clear metrics without affecting other phases. Though, as said, it will work only for serial case.\nWDYT\nI'm afraid doesn't work. That was my initial thought as well, but no luck. I guess it's b/c, theoretically, we cannot reset a metric on the server side - Promoetheus' model doesn't support this. But let me know if I miss anything.\nThe performance tests assume all the metrics all gathered and accessed in the same binary. As long as that's the case, works.", "commid": "kubernetes_issue_99218", "tokennum": 457}], "negative_passages": []}
{"query_id": "q-en-kubernetes-efa631d67e7f989b3d4263e96cdae7f8b737f487bb6c5a397755ca3783ded978", "query": "} } <del> func TestHistogramClear(t *testing.T) { samples := []float64{0.5, 0.5, 0.5, 0.5, 1.5, 1.5, 1.5, 1.5, 3, 3, 3, 3, 6, 6, 6, 6} bounds := []float64{1, 2, 4, 8} h := samples2Histogram(samples, bounds) if *h.SampleCount == 0 { t.Errorf(\"Expected histogram .SampleCount to be non-zero\") } if *h.SampleSum == 0 { t.Errorf(\"Expected histogram .SampleSum to be non-zero\") } for _, b := range h.Bucket { if b.CumulativeCount != nil { if *b.CumulativeCount == 0 { t.Errorf(\"Expected histogram bucket to have non-zero comulative count\") } } } h.Clear() if *h.SampleCount != 0 { t.Errorf(\"Expected histogram .SampleCount to be zero, have %v instead\", *h.SampleCount) } if *h.SampleSum != 0 { t.Errorf(\"Expected histogram .SampleSum to be zero, have %v instead\", *h.SampleSum) } for _, b := range h.Bucket { if b.CumulativeCount != nil { if *b.CumulativeCount != 0 { t.Errorf(\"Expected histogram bucket to have zero comulative count, have %v instead\", *b.CumulativeCount) } } if b.UpperBound != nil { *b.UpperBound = 0 } } } </del> func TestHistogramValidate(t *testing.T) { tests := []struct { name string", "positive_passages": [{"docid": "doc-en-kubernetes-c977cd9286b4a197ec98b02fe65342de07359c1835b69599916b95554e8a5e53", "text": "We already call in the code:\nThat was my understanding as well, but no luck :( Here is a diff to call in case when \"concreteOp.CollectMetrics\" is false: <details<summaryDiff:</summary<p</p</detailsAnd below is the output - it's still 1500 (500 init pods plus 1000 measured pods) instead of 1000 being benchmarked: <details<summaryOutput:</summary<p</p</details\nAlso, if you run the tests and together, the result proves doesn't work as expected:\nBut I do find a way to fix this: .", "commid": "kubernetes_issue_99218", "tokennum": 136}], "negative_passages": []}
{"query_id": "q-en-kubernetes-efc9e5cc64bda9809522032597d869e45d57656c72ff466f777a35a894a694a0", "query": "\"net/http\" \"path\" \"path/filepath\" <ins> \"runtime\" </ins> \"sync\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-dea116f1992e38bb66fa8cbf634ccd764aeb1776d3000f923339739e72460ab8", "text": "What happened: I have a Kubernetes Cluster with 2 Windows Server 2019 Core VMs as worker nodes. I upgraded first the cluster, and then the first Windows node following the docs here: Every step ran without issue, but the kubelet service was not started. This was not immediately obvious, since \"restart-service kubelet\" does not propagate the error. I think \"start-service kubelet\" would be better advice. The logs said: After changing the value of cgroupDriver manually in from \"systemd\" to \"cgroupfs\", the kubelet started successfully. What you expected to happen: One of 2 things: Either the Windows upgrade docs telling me what I need to do to fix this, or the kubeadm not breaking the configuration for windows in the first place. How to reproduce it (as minimally and precisely as possible): a windows node to a Kubernetes v1.19 cluster via kubeadm the cluster via kubeadm the Windows node following the docs Anything else we need to know?: Environment: Kubernetes version (use ): 1.20.1 Cloud provider or hardware configuration: OS (e.g: ): Windows Server 2019 Core Kernel (e.g. ): Install tools: kubeadm Network plugin and version (if this is a network-related bug): Others: /sig windows\nthis may cause by the default value of defaultCgroupDriver cgroupfs Would you provide the from Windows node?\n/assign\nkubeadm doesn't do anything about cgroup drivers on Windows because cgroups don't exist on Windows. ideally the kubelet checks about this should be skipped entirely in dockershim for non-Linux.\n! However, windows docker return as cgroupfs.\nprobably 's output is the same structure on all OSes with being a default value. this field should not be checked on Windows at all.\n/retitle kubelet: don't check for the Docker cgroup driver on Windows\nadding since the PR is favorable. /triage accepted", "commid": "kubernetes_issue_97759", "tokennum": 446}], "negative_passages": []}
{"query_id": "q-en-kubernetes-efd3a7d1996d915732c4ae2c09a53cf06652e53f84df98e9d3d101ac2673cbb0", "query": "# Cluster Role # ################ <ins> kubectl \"${kube_flags[@]}\" api-resources </ins> if kube::test::if_supports_resource \"${clusterroles}\" ; then record_command run_clusterroles_tests fi", "positive_passages": [{"docid": "doc-en-kubernetes-3c17ea4b4f4a9bb23915ee9fbb41703ef0532ac00becc05b8dda4d23a9ea9da2", "text": "As the RBAC role need to be related to resources. I think we could use a command to get the supported resources. ref to\nThis would be cool.\nI thought we a command that listed resources in the discover doc a long time ago.\nis just the versions, but principle is the same. We want to list all the types, their resources, and tie that back to \"explain\".\nWhat's the best way to determine this information currently? I'm having difficulty figuring out the exact set of permissions (and how they would be written in an RBAC role) for any given kubectl command. The documentation for this right now is split across multiple places and certain things are not explained at all. Specifically, it's difficult to determine which \"API verb\" is used for which operations. Take as an example. It's unclear if the way to allow this is to use the \"proxy\" subresource of a pod or service with \"get\"/\"create\"/etc. verbs, or to use the \"proxy\" verb with the resource (pod, service) directly. is a similar case. The almost works for this purpose, but it's still difficult. Operations for a given resource are grouped into categories like write, read, status, and proxy, but these things don't obviously correlate with API verbs. Again, proxy is especially confusing as there is no mention of a proxy \"verb\". The API operations are only shown using their HTTP verbs. One thing that could help on this document would be a section on the right column under \"kubectl command\" that shows exactly the rule needed in an RBAC role to allow this command via kubectl. And even then, that assumes an exact 1-to-1 mapping between API endpoints and kubectl commands, which I doubt is always the case. (For example, port fowarding to a pod seems to require both a GET on the pod resource and a CREATE on a port forward subresource.) There also needs to be better documentation about how this information could have been determined in the first place. I've resorted to manually looking through API requests made with but even then it's difficult to figure out. Amusingly, I was the one who wrote which is referenced in the original issue description (as well as the table explaining verbs in ).", "commid": "kubernetes_issue_42932", "tokennum": 494}], "negative_passages": []}
{"query_id": "q-en-kubernetes-efd3a7d1996d915732c4ae2c09a53cf06652e53f84df98e9d3d101ac2673cbb0", "query": "# Cluster Role # ################ <ins> kubectl \"${kube_flags[@]}\" api-resources </ins> if kube::test::if_supports_resource \"${clusterroles}\" ; then record_command run_clusterroles_tests fi", "positive_passages": [{"docid": "doc-en-kubernetes-20fd632aaf82ba3efee7609ebeda29ca6df3199abf73ef8bcfe417660974a0ce", "text": "tl;dr: It's too difficult right now to go from \"I want a user to be able to run \" to \"here is the RBAC rule to use for that\" for any case where there isn't a specific example shown in the docs.\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nIt seem that relative PR stop updated. If this issue still valuable, i will help fix it\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close", "commid": "kubernetes_issue_42932", "tokennum": 279}], "negative_passages": []}
{"query_id": "q-en-kubernetes-eff01f8b68e8f8a1c9952bd9e0985e92e1fa7c937dbaece507c3afc16b3ba19e", "query": "{Type: v1.NodeMemoryPressure, Status: v1.ConditionFalse}, {Type: v1.NodeDiskPressure, Status: v1.ConditionFalse}, {Type: v1.NodeNetworkUnavailable, Status: v1.ConditionFalse}, <del> {Type: v1.NodeInodePressure, Status: v1.ConditionFalse}, </del> } return node }(),", "positive_passages": [{"docid": "doc-en-kubernetes-7164ee736ec8b7198f38602535de086e7396a736ea12447e5be8a654710fb76e", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind cleanup What happened: It seems kubelet did not update inode pressure; and only test codes are using . So prefer to deprecate or remove it directly. (seems no node-misc group :). )", "commid": "kubernetes_issue_49103", "tokennum": 58}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f046f25f80abd9e198301de0f87a48ae1a04012158e8033431eea8eec2965f09", "query": "return dswp, fakePodManager } <ins> func TestFindAndAddNewPods_WithRescontructedVolume(t *testing.T) { // create dswp dswp, fakePodManager := prepareDswpWithVolume(t) // create pod fakeOuterVolumeName := \"dswp-test-volume-name\" containers := []v1.Container{ { VolumeMounts: []v1.VolumeMount{ { Name:      fakeOuterVolumeName, MountPath: \"/mnt\", }, }, }, } pod := createPodWithVolume(\"dswp-test-pod\", fakeOuterVolumeName, \"file-bound\", containers) fakePodManager.AddPod(pod) podName := util.GetUniquePodName(pod) mode := v1.PersistentVolumeFilesystem pv := &v1.PersistentVolume{ ObjectMeta: metav1.ObjectMeta{ Name: fakeOuterVolumeName, }, Spec: v1.PersistentVolumeSpec{ ClaimRef:   &v1.ObjectReference{Namespace: \"ns\", Name: \"file-bound\"}, VolumeMode: &mode, }, } generatedVolumeName := \"fake-plugin/\" + pod.Spec.Volumes[0].Name uniqueVolumeName := v1.UniqueVolumeName(generatedVolumeName) expectedOuterVolumeName := \"dswp-test-volume-name\" opts := operationexecutor.MarkVolumeOpts{ PodName:             podName, PodUID:              pod.UID, VolumeName:          uniqueVolumeName, OuterVolumeSpecName: generatedVolumeName, // fake reconstructed volume VolumeGidVolume:     \"\", VolumeSpec:          volume.NewSpecFromPersistentVolume(pv, false), VolumeMountState:    operationexecutor.VolumeMounted, } dswp.actualStateOfWorld.MarkVolumeAsAttached(opts.VolumeName, opts.VolumeSpec, \"fake-node\", \"\") dswp.actualStateOfWorld.MarkVolumeAsMounted(opts) dswp.findAndAddNewPods() mountedVolumes := dswp.actualStateOfWorld.GetMountedVolumesForPod(podName) found := false for _, volume := range mountedVolumes { if volume.OuterVolumeSpecName == expectedOuterVolumeName { found = true break } } if !found { t.Fatalf( \"Could not found pod volume %v in the list of actual state of world volumes to mount.\", expectedOuterVolumeName) } } </ins> func TestFindAndAddNewPods_WithReprocessPodAndVolumeRetrievalError(t *testing.T) { // create dswp dswp, fakePodManager := prepareDswpWithVolume(t)", "positive_passages": [{"docid": "doc-en-kubernetes-95820dc44dfb57216fa4466fe0b08e35d101b3576d175fcc0793312a1c18dfad", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --We have even encountered such case that pod continuously reports \u201cUnable to attach or mount volumes for pod;...\u201d when kubelet restarted. The reasons are listed in details as below: , as result of apiserver instantaneous unstablility, dswp get pvc\u2018s pv spec failed, then the pvc volume does not be to dsw. , syncStates() lists all the volume directories locally, and recontructs the volume from local volume, if the volume isn't in dsw, it will put the recontructed volume to asw, but now the volume.OuterVolumeSpecName isn't correct. chance, at this time, In , the fail to pvc volume is to dsw again normally in reconcile() -mountAttachVolumes(), it compares dsw and asw by volume's innerVolumename, it's all the same. but it could not sense the OuterVolumeSpecName dismatch. so it will not re-mount again to update asw cache , it checks pod's volume attach or mount success by comparing volume.OuterVolumeSpecName and , but this pv'c OuterVolumeSpecName isn't correct in asw. so pod continuously reports \u201cUnable to attach or mount volumes for pod;...\u201d reconcile() could sense the reconstruct volume's dismatch to the dsw, then re-mount again to make volume cache consistency Kubernetes version (use ): 1.19.4 Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig node\n/triage accepted\n/assign\nCC\nI think this is a point that can be optimized. /cc\nI will give a fix for this\nThanks for reporting the issue, this innerSpecName and outerSpecName are confusing and cause issues. Please ping me for review when you have a fix. Thanks!\nPlease don't triage your own issues immediately, give someone else a chance to review them :( /sig storage\nokay, I know", "commid": "kubernetes_issue_103143", "tokennum": 528}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f04a8a8ebef7d66fb544543b373508dafb7fd904c8b447d6538ab29ec032d31b", "query": "// +k8s:deepcopy-gen=package <del> package testing </del> <ins> package testing // import \"k8s.io/apiserver/pkg/storage/testing\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-460ceb7b52a1ab0cadc1b29d7eee5cc1013b8d23be9bca0d145119ffcf7b27c6", "text": "Look at one of the directories under (Please don't pick more than one directory for one PR as it will cause issues for reviewers) Find all the files named (example find -name ) See the following link it has a this tells tools how this package needs to be imported. So we should ensure that each has an import Add a description appropriate to the package (similar to the one below) Look through sub directories and see if there are any other important directories that are likely to be used by outside users and add a Why are we doing this? We perfer to use vanity urls instead of directly using to refer to code, so this helps ensure that tools honor our wish. See It would be good to have some package level documentation since these directories under staging/ are meant to be for use by folks outside of kubernetes github org. /good-first-issue\n/kind documentation /sig architecture\ncurrently working my through Not going to use / assign since there could be a number of PRs for this issue.\n/lifecycle active /good-first-issue edit: hmm..\nThis request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /lifecycle active /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\nMay I try on\nIIUC this means that there needs to be a even at the root of the repo? Then how does work? :thinking:\nHi , can I make a PR for this directory ?\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_68231", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f04a8a8ebef7d66fb544543b373508dafb7fd904c8b447d6538ab29ec032d31b", "query": "// +k8s:deepcopy-gen=package <del> package testing </del> <ins> package testing // import \"k8s.io/apiserver/pkg/storage/testing\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-5f31f1c27d7198dc83b313154ff681043a8b41e17eb5d3ddf32cd84bc023f931", "text": "/lifecycle rotten\nI guess this is still not done, was supposed to partially fix this issue. /reopen\nReopened this issue. <detailsIn response to : I guess this is still not done, was supposed to partially fix this 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\n/remove-lifecycle rotten /area code-organization", "commid": "kubernetes_issue_68231", "tokennum": 93}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f04e16b765fc15c63352942078ea479349ecf7a2a4deca5998ac73c57490179b", "query": "<del> kind: ReplicationController apiVersion: v1 </del> <ins> apiVersion: extensions/v1beta1 kind: Deployment </ins> metadata: name: etcd <del> creationTimestamp: </del> spec: strategy: type: Recreate <del> resources: {} triggers: - type: ConfigChange </del> replicas: 3 selector: <del> name: etcd </del> <ins> matchLabels: name: etcd </ins> template: metadata: <del> creationTimestamp: </del> labels: name: etcd spec:", "positive_passages": [{"docid": "doc-en-kubernetes-970debf69dc4e7e663c051298279ebf93b58654f6c393d8683796c73cb4f1c74", "text": "Kubernetes version (use ): Environment: Cloud provider or hardware configuration: Vagrant OS (e.g. from /etc/os-release): CoreOS Kernel (e.g. ):Install tools: Vagrant & Others: What happened: What you expected to happen: Success How to reproduce it (as minimally and precisely as possible): Followed instructions at Tried to run Received: Anything else do we need to know: From googling, it seems several of the fields in the config are for when using OpenShift origin. But creating the replication controller is a prerequisite to launching OpenShift Origin. Chicken & egg problem.", "commid": "kubernetes_issue_39575", "tokennum": 138}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f086dc1b587b1c9e45bff64e4df5390791ed90e5d4323aa3bdf8c085fd7c88a0", "query": "// or the kubeadm preferred one for the desired Kubernetes version var desiredEtcdVersion *version.Version if cfg.Etcd.Local.ImageTag != \"\" { <del> desiredEtcdVersion, err = version.ParseSemantic(cfg.Etcd.Local.ImageTag) </del> <ins> desiredEtcdVersion, err = version.ParseSemantic( convertImageTagMetadataToSemver(cfg.Etcd.Local.ImageTag)) </ins> if err != nil { return true, errors.Wrapf(err, \"failed to parse tag %q as a semantic version\", cfg.Etcd.Local.ImageTag) }", "positive_passages": [{"docid": "doc-en-kubernetes-1d9713caefc449b5fa12697f2f529990c13dff1a712a56404b9120eb41d78bc3", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --When attempting to upgrade kubernetes using kubeadm upgrade apply, kubeadm fails to parse an etcd imagetag containing build metadata in the form of as a valid semver. An example upgrade produces an error similar to: Note this will occur even if the etcd version is unchanged. The +` character. This pattern is used to support custom kubernetes images, for instance kube-apiserver:v1.20.4+patch.0 will be converted to imagetag v1.20.4_patch.0 when running make quick-release-images. Add the following to kubeadm- Install kubernetes. Then upgrade kubernetes with kubeadm upgrade apply. I have tested a fix for this issue and will PR shortly. Kubernetes version (use ): N/A Cloud provider or hardware configuration: N/A OS (e.g: ): N/A Kernel (e.g. ): N/A Install tools: kubeadm Network plugin and version (if this is a network-related bug): N/A Others: N/A\n/sig cluster-lifecycle\n/area kubeadm\n/triage accepted", "commid": "kubernetes_issue_100349", "tokennum": 312}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f092744af3c8c27c69a0522c777a3d4347f5295a9390b91e67a3a11525722baf", "query": "// Cannot be updated. // +optional WorkingDir string `json:\"workingDir,omitempty\" protobuf:\"bytes,5,opt,name=workingDir\"` <del> // List of ports to expose from the container. Exposing a port here gives // the system additional information about the network connections a // container uses, but is primarily informational. Not specifying a port here </del> <ins> // List of ports to expose from the container. Not specifying a port here </ins> // DOES NOT prevent that port from being exposed. Any port which is // listening on the default \"0.0.0.0\" address inside a container will be // accessible from the network. <ins> // Modifying this array with strategic merge patch may corrupt the data. // For more information See https://github.com/kubernetes/kubernetes/issues/108255. </ins> // Cannot be updated. // +optional // +patchMergeKey=containerPort", "positive_passages": [{"docid": "doc-en-kubernetes-754763163ccf179fd132c393411aa2d267e649990c98a81bb38938ec6debc8b2", "text": "The comments in says that : However there are several cases where this is false : When using a Service with a targetPort that references a name in the ports arrays of the pod. Some software (ab)uses this API to get which ports are used (See Although unfixable, my goal is to fix the documentation so other people don't have the same problem). The Azure Load Balancer implementation does this for instance. Some other network/security software might use this information. Also, is it possible to document/reference the above issue in the comment ? Since it is described as informational I expected for the network to work without this information. But it's definitely not the case. Not needed since it's mostly a doc issue. I'm interested in contributing this patch but would like some feedbacks before doing it. :) <details</details<details</details<details</details<details</details<details</details<details</details\n/sig network\n/triage accepted -- thoughts? I believe the doc are due for a refresh.\nI'd take this one. /assign\nI didn't see that you wanted to do this patch, I am very sorry and now I unassign it. /unassign\nNo worries But I'm still not sure where / what to add. Should I only fix the part saying it is only informational ? Is there anything else ? (cc\nThe 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]:\n/remove-lifecycle stale", "commid": "kubernetes_issue_108255", "tokennum": 435}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f0a8fdd4cf90141eb1a59b24146c324392e87a3f151e9e532cc5907beea21020", "query": "const ( // StatusSuccess represents the successful completion of command. StatusSuccess = \"Success\" <del> // StatusFailed represents that the command failed. StatusFailure = \"Failed\" </del> // StatusNotSupported represents that the command is not supported. StatusNotSupported = \"Not supported\" )", "positive_passages": [{"docid": "doc-en-kubernetes-532d95a36e3e64a064736a1778f1c9d5e68ebcc137b6e1127e9746ac22dbf538", "text": "<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.--Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see ): No What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): statusFailure Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT <!-- If this is a BUG REPORT, please: Fill in as much of the template below as you can. If you leave out information, we can't help you as well. If this is a FEATURE REQUEST, please: Describe in detail the feature/behavior/change you'd like to see. In both cases, be ready for followup questions, and please respond in a timely manner. If we can't reproduce a bug or think a feature already exists, we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why. --Kubernetes version (use ): 4 Environment: Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: Others What happened: In FlexVolume code: The statusFailure constant should have string literal \"Failure\", not \"Failed\". Because in the test code or documentation everywhere, only \"Failure\" string is used, not \"Failed\" for the flexvolume cmd output status string. So this is a typo bug. Here is the test: here is the documentation: here is the example: What you expected to happen: The statusFailure constant should have string literal \"Failure\", not \"Failed\" at this line: How to reproduce it (as minimally and precisely as possible): code inspect: Anything else do we need to know: nothing else", "commid": "kubernetes_issue_34510", "tokennum": 415}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f0ae008905a48d4ab597dff6eefac07f84aef613d2bffb0428cdf16c6d9d1fa4", "query": "FlagTimeout      = \"request-timeout\" ) <ins> // RecommendedConfigOverrideFlags is a convenience method to return recommended flag names prefixed with a string of your choosing func RecommendedConfigOverrideFlags(prefix string) ConfigOverrideFlags { return ConfigOverrideFlags{ AuthOverrideFlags:    RecommendedAuthOverrideFlags(prefix), ClusterOverrideFlags: RecommendedClusterOverrideFlags(prefix), ContextOverrideFlags: RecommendedContextOverrideFlags(prefix), CurrentContext: FlagInfo{prefix + FlagContext, \"\", \"\", \"The name of the kubeconfig context to use\"}, Timeout:        FlagInfo{prefix + FlagTimeout, \"\", \"0\", \"The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests.\"}, } } </ins> // RecommendedAuthOverrideFlags is a convenience method to return recommended flag names prefixed with a string of your choosing func RecommendedAuthOverrideFlags(prefix string) AuthOverrideFlags { return AuthOverrideFlags{", "positive_passages": [{"docid": "doc-en-kubernetes-4e19a56e8ccacbab4546f622baecdb0b8ef30250430c55f8bcdc4de99b100cd2", "text": "Found in openshift, but I'm pretty sure the codepaths are the same. That means the token is getting ignored and in-cluster config is being used in preference to flags.\nIs a similar issue?\nYep, kind of regression.\nSigh.\nYes, most likely the same cause.\nI'm on it.\nUnit test :)\nProbably will want to cherrypick this into 1.5.\nWIP in", "commid": "kubernetes_issue_38834", "tokennum": 89}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f0c1d0d51ee9714063554a951ca8bec470b8200e74ff32ff013a9f901ba39028", "query": "t.Errorf(\"Timed out waiting for response.\") } } <ins> func TestWarningWithRequestTimeout(t *testing.T) { type result struct { err        interface{} stackTrace string } clientDoneCh, resultCh := make(chan struct{}), make(chan result, 1) testHandler := http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) { // this will catch recoverable panic like 'Header called after Handler finished'. // go runtime crashes the program if it detects a program-ending // panic like 'concurrent map iteration and map write', so this // panic can not be caught. defer func() { result := result{} result.err = recover() if result.err != nil { // Same as stdlib http server code. Manually allocate stack // trace buffer size to prevent excessively large logs const size = 64 << 10 buf := make([]byte, size) buf = buf[:goruntime.Stack(buf, false)] result.stackTrace = string(buf) } resultCh <- result }() // add warnings while we're waiting for the request to timeout to catch read/write races loop: for { select { case <-r.Context().Done(): break loop default: warning.AddWarning(r.Context(), \"a\", \"1\") } } // the request has just timed out, write to catch read/write races warning.AddWarning(r.Context(), \"agent\", \"text\") // give time for the timeout response to be written, then try to // write a response header to catch the \"Header after Handler finished\" panic <-clientDoneCh warning.AddWarning(r.Context(), \"agent\", \"text\") }) handler := newGenericAPIServerHandlerChain(t, \"/test\", testHandler) server := httptest.NewUnstartedServer(handler) server.EnableHTTP2 = true server.StartTLS() defer server.Close() request, err := http.NewRequest(\"GET\", server.URL+\"/test?timeout=100ms\", nil) if err != nil { t.Fatalf(\"unexpected error: %v\", err) } client := server.Client() response, err := client.Do(request) close(clientDoneCh) if err != nil { t.Errorf(\"expected server to return an HTTP response: %v\", err) } if want := http.StatusGatewayTimeout; response == nil || response.StatusCode != want { t.Errorf(\"expected server to return %d, but got: %v\", want, response) } var resultGot result select { case resultGot = <-resultCh: case <-time.After(wait.ForeverTestTimeout): t.Errorf(\"the handler never returned a result\") } if resultGot.err != nil { t.Errorf(\"Expected no panic, but got: %v\", resultGot.err) t.Errorf(\"Stack Trace: %s\", resultGot.stackTrace) } } // builds a handler chain with the given user handler as used by GenericAPIServer. func newGenericAPIServerHandlerChain(t *testing.T, path string, handler http.Handler) http.Handler { config, _ := setUp(t) s, err := config.Complete(nil).New(\"test\", NewEmptyDelegate()) if err != nil { t.Fatalf(\"Error in bringing up the server: %v\", err) } s.Handler.NonGoRestfulMux.Handle(path, handler) return s.Handler } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-c00c4002c1ceb0f27a0d12e9f8008c8e3b435d9e5dbb0a6b5f62beaf7aea3677", "text": "I am doing v1.28.3 kube-apiserver testing in the test environment, and I often encounter kube-apiserver panic, especially when kube-apiserver call webhook fails. The following are the captured panic logs: and: kube-apiserver does not panic even if calling webhook times out or fails Deploy a webhook, remove the service corresponding to the webhook, and then create pods in batches to trigger webhook calls No response <details</details<detailsprivate cloud </details<details</details<details</details<details</details<details</details\n/sig api-machinery\nsomewhat related to\nThe scenarios that trigger panic are similar(the apiserver fails to call webhook), but the log shows that the location of panic is different.\n/assign For context of  Thank you. /triage accepted\nagain, full stack logs:\nI'll try to test the mr:\nLet me try to explain the panic - both goroutines are trying to write to the of the first goroutine: This request has timed out, and consequently the filter is trying to send a response to the caller. This is the client facing goroutine from the timeout filter. Note that the call to is protected by a mutex, that means that if the other goroutine is using the delegated object via the adapter, then this panic should not happen. second goroutine: let's check the other goroutine, it is also trying to write to the of the object: Now uses an unprotected version of the ResponseWriter object: The filter precedes the filter in the execution order, so the in is not using the thread safe implementation. This is the order today: one quick resolution is to move the after the timeout filter: , but there could be code that precedes that needs to write warning? Also note that the panic mentioned in is not as severe, it does not cause the apiserver to crash. For a more proper solution, i think we would want any thoughts?", "commid": "kubernetes_issue_122940", "tokennum": 443}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f0c1d0d51ee9714063554a951ca8bec470b8200e74ff32ff013a9f901ba39028", "query": "t.Errorf(\"Timed out waiting for response.\") } } <ins> func TestWarningWithRequestTimeout(t *testing.T) { type result struct { err        interface{} stackTrace string } clientDoneCh, resultCh := make(chan struct{}), make(chan result, 1) testHandler := http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) { // this will catch recoverable panic like 'Header called after Handler finished'. // go runtime crashes the program if it detects a program-ending // panic like 'concurrent map iteration and map write', so this // panic can not be caught. defer func() { result := result{} result.err = recover() if result.err != nil { // Same as stdlib http server code. Manually allocate stack // trace buffer size to prevent excessively large logs const size = 64 << 10 buf := make([]byte, size) buf = buf[:goruntime.Stack(buf, false)] result.stackTrace = string(buf) } resultCh <- result }() // add warnings while we're waiting for the request to timeout to catch read/write races loop: for { select { case <-r.Context().Done(): break loop default: warning.AddWarning(r.Context(), \"a\", \"1\") } } // the request has just timed out, write to catch read/write races warning.AddWarning(r.Context(), \"agent\", \"text\") // give time for the timeout response to be written, then try to // write a response header to catch the \"Header after Handler finished\" panic <-clientDoneCh warning.AddWarning(r.Context(), \"agent\", \"text\") }) handler := newGenericAPIServerHandlerChain(t, \"/test\", testHandler) server := httptest.NewUnstartedServer(handler) server.EnableHTTP2 = true server.StartTLS() defer server.Close() request, err := http.NewRequest(\"GET\", server.URL+\"/test?timeout=100ms\", nil) if err != nil { t.Fatalf(\"unexpected error: %v\", err) } client := server.Client() response, err := client.Do(request) close(clientDoneCh) if err != nil { t.Errorf(\"expected server to return an HTTP response: %v\", err) } if want := http.StatusGatewayTimeout; response == nil || response.StatusCode != want { t.Errorf(\"expected server to return %d, but got: %v\", want, response) } var resultGot result select { case resultGot = <-resultCh: case <-time.After(wait.ForeverTestTimeout): t.Errorf(\"the handler never returned a result\") } if resultGot.err != nil { t.Errorf(\"Expected no panic, but got: %v\", resultGot.err) t.Errorf(\"Stack Trace: %s\", resultGot.stackTrace) } } // builds a handler chain with the given user handler as used by GenericAPIServer. func newGenericAPIServerHandlerChain(t *testing.T, path string, handler http.Handler) http.Handler { config, _ := setUp(t) s, err := config.Complete(nil).New(\"test\", NewEmptyDelegate()) if err != nil { t.Fatalf(\"Error in bringing up the server: %v\", err) } s.Handler.NonGoRestfulMux.Handle(path, handler) return s.Handler } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-f6276625b0df7e8b951a42b4ce484e48eb7715b4546658f042b200999787970a", "text": "/cc\nI tend to remove the timeout filter, the sooner the better, and I think the Apiserver panic is the P0-level bug, directly affecting the availability of the cluster I have cherry-picked and tested it in my cluster, and I still need to continue to observe for 1-2 days\nI opened a minimal WIP fix for the warning writer in since the timeout filter removal is a much bigger change to reason through\nthanks a lot, I will try to test and cherry-pick the above minimal WIP fix in\nsorry, I completely overlooked , I only saw and that looked too big to take safely right now I prefer to\nCan we backport the fix to 1.28?\nWhy 1.28 specifically? I'm not aware of anything that changed in 1.28 that made this more or less prevalent. If this meets backport criteria, going to all active branches could make sense (1.27+)", "commid": "kubernetes_issue_122940", "tokennum": 191}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f0ca2c87c1f9890ea3d6b385e3be0c7ea12642650ac0fb57e159d06c3d6b97bc", "query": "metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/util/net\" \"k8s.io/apimachinery/pkg/util/runtime\" <ins> \"k8s.io/apimachinery/pkg/util/sets\" </ins> \"k8s.io/apimachinery/pkg/util/wait\" corev1client \"k8s.io/client-go/kubernetes/typed/core/v1\" \"k8s.io/client-go/tools/record\"", "positive_passages": [{"docid": "doc-en-kubernetes-8c9ebf4e41021efd0692132f5b2f5e7ec08451127a302fc405c42cb972b9ed2e", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: I created several Workloads which require up to ten ports for both UDP and TCP protocol. Now my logs get spammed with . What you expected to happen: should consider -combination instead of only . How to reproduce it (as minimally and precisely as possible): Deploy any service with a node-port with both protocols, e.g.: Anything else we need to know?: This was already acknowledged by here: However, as this thread addresses a different bug and seems kind of stuck, i'd like to suggest that this might be addressed in a new context. Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Deployed via Rancher v2.4.3\n/sig api-machinery\n/remove-sig api-machinery /sig network\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\nHow did you get into this situation? The allocator should not have granted the same node port twice?\nOh right, that issue. The only real way out is to de-allocate the NodePorts and then re-allocate them, I think\nAs this happens for all of my ports in the said Production Application (the one where my log gets spammed) as well as complete fresh installation (where i verified the bug), i think there's no \"way out\" except fixing the bug. As said, for me it's necessary to assign both protocols to the same port. This might be a niche-use-case, but checking the it's actually very likely for ports to allow tcp AND udp. I'm not sure about the history of this, but it might be that issue was the origin, which was adressed in PR (\"Allow services which use same port, different protocol to use the same nodePort for both\"). But this PR doesn't contain the adjustment of the said , so still considers the behaviour as invalid, while it's actually allowed and supported.", "commid": "kubernetes_issue_91404", "tokennum": 498}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f0ca2c87c1f9890ea3d6b385e3be0c7ea12642650ac0fb57e159d06c3d6b97bc", "query": "metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/util/net\" \"k8s.io/apimachinery/pkg/util/runtime\" <ins> \"k8s.io/apimachinery/pkg/util/sets\" </ins> \"k8s.io/apimachinery/pkg/util/wait\" corev1client \"k8s.io/client-go/kubernetes/typed/core/v1\" \"k8s.io/client-go/tools/record\"", "positive_passages": [{"docid": "doc-en-kubernetes-33f53ed726ab1a89c68c77aae3b932484545b038842bda14047a639f615b725d", "text": "/assign\nAhh, I thought you meant that you had accidentally been allocated the same nodePorts and I was very confused when you said \"all of them\". I have reproduced this issue, and I can see it by inspection. The obvious fix would be to collect ports split by protocol, but I think that's not right since we don't store it split. An even simpler fix would be for to build a . Then for each protocol, for each port, build that contains all the port numbers, but remove any duplicates ONLY IF they are duplicated across protocols. Duplicates in the same protocol should be retained (to report an error later). I don't have time to tackle this tonight (and write a test), but it seems like a good bug.\nperhaps I can fix this problem /assign\nthings may be a little more complicated. Right now the is not aware of the protocol of the port so I guess simply rewriting function to return is not enough, the port allocator will still return on same node port even with different protocol. perhaps we need to refactor the to make it protocol-aware.\nI don't think we need to do make the allocator be protocol aware. IIRC we allow you to use the same nodeport on different protocols ONLY within a single service. This means (I think) that we can do hyper-local deduplication as we collect the nodeports for each service. If we find the same nodeport number with different protocols, just remove the duplicates because it is allowed. I.e. a service that looks like: return - deduped. if ANY OTHER service tried to use it would be an error at the \"rebuilt\" allocator Likewise if a single Service claims to use the same nodeport number more than once on the same protocol, it should be an error: return - NOT deduped.\nobviously, we want a great unit test here :P\nah got it! thanks for your detailed explanation!\nHi! I have filed a PR to resolve this issue, could you take a look?", "commid": "kubernetes_issue_91404", "tokennum": 428}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f0ed166b3b61796722d6e450fd412ba6ed8e8cdfbcf8fdb6847d5c691c4fdf73", "query": "mkdir -p \"${dst_dir}\" local salt_dir=\"${KUBE_ROOT}/cluster/saltbase/salt\" <ins> cp \"${salt_dir}/cluster-autoscaler/cluster-autoscaler.manifest\" \"${dst_dir}/\" </ins> cp \"${salt_dir}/fluentd-es/fluentd-es.yaml\" \"${release_stage}/\" cp \"${salt_dir}/fluentd-gcp/fluentd-gcp.yaml\" \"${release_stage}/\" cp \"${salt_dir}/kube-registry-proxy/kube-registry-proxy.yaml\" \"${release_stage}/\"", "positive_passages": [{"docid": "doc-en-kubernetes-cafbbd3cd664270b9fbd0ce7e8faa35ad0e8800a7c5d7cdeb5164eec0f1b24f1", "text": "For some reason they stopped working and we even don't create manifest file for cluster autoscaler. I used the following command to start the cluster:\nIt's possible it's related to", "commid": "kubernetes_issue_26346", "tokennum": 40}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f1474a70c2f6cf8bcad84a497fe22704eb95dda435f4bdf926ada1c2336e6682", "query": "if pod == nil { return framework.NewStatus(framework.Error, \"pod cannot be nil\") } <del> state.RLock() defer state.RUnlock() </del> if v, e := state.Read(framework.StateKey(pod.Name)); e == nil { if value, ok := v.(*stateData); ok && value.data == \"never bind\" { return framework.NewStatus(framework.Unschedulable, \"pod is not permitted\")", "positive_passages": [{"docid": "doc-en-kubernetes-43588246e28947764a0f8a5c9c5b1d76a5819a8eaa1c439f79abd429269822c0", "text": "What happened: kube-scheduler () crashes due to a panic while running : The race condition is triggered when an out-of-tree plugin, that writes to during its Filter phase, is registered through . Access to in general happens from a single goroutine and there are no practical concurrency issues, with the exception of the phase, that parallelizes calls for each node across plugins: A quick glance at the tip of the branch seems to indicate the bug is still present there. What you expected to happen: Ideally access to should be synchronized everywhere for correctness, including by all in-tree plugins, since there are no guarantees about how will call multiple plugins concurrently. It seems to me it is something that was considered at some point, given that has methods. Sadly, almost no in-tree plugins are synchronizing access. For now, I will try to work around the problem by doing a single write to during and storing a data bag structure where I will write state into during (with proper synchronization), instead of writing to directly. How to reproduce it (as minimally and precisely as possible): Install a scheduler plugin that writes to during its phase. In-tree (builtin) plugins are not synchronizing their access to . Environment: Kubernetes version (use ): v1.18.8 Cloud provider or hardware configuration: linux-amd64 (AWS) OS (e.g: ): Ubuntu 18.04.5 LTS (Bionic Beaver) Others: custom kube-scheduler binary built with an out-of-tree plugin using\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig scheduling\nAFAICT all in-tree plugins write to the cycle state in PreFilter and then only read from cycle state in Filter. So this shouldn't be a problem with in-tree plugins as concurrent read access should be fine during RunFilterPlugins. But since your out-of-tree plugin writes in Filter, I can see why this can be a problem.", "commid": "kubernetes_issue_95887", "tokennum": 515}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f1474a70c2f6cf8bcad84a497fe22704eb95dda435f4bdf926ada1c2336e6682", "query": "if pod == nil { return framework.NewStatus(framework.Error, \"pod cannot be nil\") } <del> state.RLock() defer state.RUnlock() </del> if v, e := state.Read(framework.StateKey(pod.Name)); e == nil { if value, ok := v.(*stateData); ok && value.data == \"never bind\" { return framework.NewStatus(framework.Unschedulable, \"pod is not permitted\")", "positive_passages": [{"docid": "doc-en-kubernetes-278036efba637c2a6a49330142a64ca8f7b65a0d21755fde24824f9c473a00c9", "text": "Aside from adding Lock/Unlock in in-tree plugin, offering mutual exclusion on each key as a built-in feature within CycleState could be an alternative solution. This way, reads from in-tree plugins during Filter wouldn't interfere with writes during Filter from out-of-tree plugins.\ncc\nshould we change the Read/Write CycleState methods to be thread safe?\nAdding locks without a proper justification would just increase the latency. could you clarify your use case? Why do you need to write anything during Filter?\nyeah, we should measure it, but I don't expect it to have significant effect...\nAdding locks without a proper justification would just increase the latency. Without contention (which is the case with in-tree plugins), I don't think this is a concern.\nAdapting source from : source: essentially, 11.3 ns/Lock-Unlock pair\nI remember locks showing up in profiling for PreScore/Score for certain plugins. Although I have to admit that the accesses were not properly implemented. I'd like to hear an answer for before doing any experiments.\n+1 to that I'd also like to understand the motivations / requirements of mutating CycleState in Filter().\nMy particular use-case is that we have resources being dynamically to/removed from Nodes, and those resources need to be allocated (and tracked) in the scheduling loop. Technically I could pre-compute all the available dynamic resources for all Nodes at the phase, and snapshot it, but that would require me to pre-compute everything for all Nodes on all scheduling cycles. Instead, what I'm currently doing is computing what dynamic resources can be utilized on-demand during the phase (kind of a lazy loading of dynamic resources for each pair), and saving state of what extra resources were considered during for each Node that was evaluated. Then, later in the scheduler plugin can lock-in the exact dynamic resources for the particular Node that was selected. I understand the concern with adding extra synchronization overhead without a real need. Even if my use-case is not good enough to justify it, there is another argument for it: technically, the lack of access synchronization on violates the . Even if in the end we decide synchronizing all access is not worth the overhead (for correctness), I would strongly encourage better documentation saying which plugin phases are allowed to modify , and perhaps even forcing a snapshot-read-only copy of to be used by plugins.\nUsing the scheduler to track resources is not a good idea.", "commid": "kubernetes_issue_95887", "tokennum": 539}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f1474a70c2f6cf8bcad84a497fe22704eb95dda435f4bdf926ada1c2336e6682", "query": "if pod == nil { return framework.NewStatus(framework.Error, \"pod cannot be nil\") } <del> state.RLock() defer state.RUnlock() </del> if v, e := state.Read(framework.StateKey(pod.Name)); e == nil { if value, ok := v.(*stateData); ok && value.data == \"never bind\" { return framework.NewStatus(framework.Unschedulable, \"pod is not permitted\")", "positive_passages": [{"docid": "doc-en-kubernetes-b826aaa34ec054d9cc587ce8587a04002d4daa70694ce73071b413f1bf7ba0c6", "text": "The scheduler should be stateless. Can't you track the resources with an external controller or with a device plugin and making it part of the Node spec?\nthere may be some misunderstanding in my poor choice of words. What I mean by \"tracking\" is that the scheduler needs to track usage and availability of these extra per-Node resources, to be able to allocate them during placement/scheduling. Exactly the same it does with volumes, cpus, memory, ephemeral disk, etc Doing computations in a controller outside of the scheduling loop would be similar to \"precomputing\" these resources. In my particular use case I chose a different way because: introduces another point of failure, if the external controller stops pre-computing extra resources and publishing them somewhere (CRD, Node spec, etc) scheduling halts (at least scheduling on these extra resources) Node resources in my use case are volatile (they are coming and going frequently), and the extra latency by an extra controller (vs doing all computations right in the scheduling loop) may be problematic for my use case. Even if you consider my use case not enough to add proper synchronization to , I'd still encourage making it explicit what scheduling phases are allowed to modify it (and even passing in a snapshot read-only version of to phases that are not expected to update it), to avoid confusion and race conditions.\nOk, if you are not tracking the existence of resources in the scheduler, I wouldn't suggest the external controller. Still, have you considered the device plugin framework? That way, the default kube-scheduler could keep track of resources usage. Otherwise, I still don't see why you would need to update the CycleState during Filter. As its name indicates, CycleState only lives during a scheduling cycle.\nRegardless of the correctness of usage of CycleState to do what wants, I still think we need to do at least one of the following: that writing to CycleState during Filter will lead to data races, a read-only CycleState to Filter plugins (whether we do this at the interface level or if we simply drop Write requests during Filter is an implementation detail), or make CycleState concurrency safe CycleState as it exists right now allows plugin authors to shoot themselves in the foot IMO.\nI'm leaning towards 1, but it's fair to continue the discussion before deciding.\nCan you run the \"controller\" as a goroutine along with your scheduler plugin?", "commid": "kubernetes_issue_95887", "tokennum": 520}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f1474a70c2f6cf8bcad84a497fe22704eb95dda435f4bdf926ada1c2336e6682", "query": "if pod == nil { return framework.NewStatus(framework.Error, \"pod cannot be nil\") } <del> state.RLock() defer state.RUnlock() </del> if v, e := state.Read(framework.StateKey(pod.Name)); e == nil { if value, ok := v.(*stateData); ok && value.data == \"never bind\" { return framework.NewStatus(framework.Unschedulable, \"pod is not permitted\")", "positive_passages": [{"docid": "doc-en-kubernetes-038a628d524f09c8393af798b6053a1fded9e84e2c01785ad258fb86c8d6d618", "text": "So it's not an external controller binary, and hence don't introduce another point of failure. It's pretty like how the default scheduler manages its internal cache. But note that cache is only needed when you need a more efficient data structure. If a {key:value} map is good enough, spinning up a XYZInformer and obtain the latest XYZ resource on-demand is the most recommended way. I think it quite depends on how you design the internal XYZ cache. For example, it should only tweak the cache in an incremental manner - in other words, unchanged resource will be kept unmodified. You can check out the \"doubly-pointer snapshot\" of scheduler's cache. With above said, if I understand your case correctly, you may need to build a sophisticated XYZ cache, which runs in a separate goroutine and responds to your XYZ resource changes. And then upon each scheduling cycle, take a snapshot (may needs a specific snapshotting algorithm) in PreFilter() and WRITE to CycleState, and then in Filter() READ from CycleState. My personal option is to suggest all plugin developers to read from CycleState in Filter().\nnailed it. What you describe is almost exactly what I\u2019m doing today. There are some details particular to my use case (e.g. just tracking current state with an informer and an incremental cache is not enough, because there\u2019s some logic involved in deciding if currently available resources are usable by each pair, and I currently do that computation in as pairs are evaluated). In any case, I just wanted to share my use case to provide some color, but I don\u2019t want what I\u2019m doing distracting us from the more important questions, mentioned by above. My personal preference would be as a very short term next step, then when someone has cycles to do it. I would be OK with punting on until a more strong need shows up.\nNote that limiting to only reading from works for me, as long as I can still read my own data structure from it and do writes on it (i.e. don\u2019t deepclone for the phase).\nalso adds overhead (from copying the state, which can be very expensive).\nCould implement just by changing the interface passed to (e.g. ). That wouldn\u2019t be backwards compatible, but very cheap.", "commid": "kubernetes_issue_95887", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f1474a70c2f6cf8bcad84a497fe22704eb95dda435f4bdf926ada1c2336e6682", "query": "if pod == nil { return framework.NewStatus(framework.Error, \"pod cannot be nil\") } <del> state.RLock() defer state.RUnlock() </del> if v, e := state.Read(framework.StateKey(pod.Name)); e == nil { if value, ok := v.(*stateData); ok && value.data == \"never bind\" { return framework.NewStatus(framework.Unschedulable, \"pod is not permitted\")", "positive_passages": [{"docid": "doc-en-kubernetes-73e2408e2bea0ec3fe3177e8a87291d57a052eb7c05f546c204ec27aefee3293", "text": "I guess that would work in the sense that you cannot change the high level values of the CycleState map, but you could still override what's inside them, if they have pointers. But maybe that's ok.\nbut you could still override what's inside them, if they have pointers. But maybe that's ok. yeah, if it was pointers and if the underlying data needed to be modified, I'd imagine it would have its own Lock/Unlock semantics\nfor such implementation, the only remaining concern is backwards compatibility. So I would leave that decision to who leads the scheduling-plugins repo.\nI rethink 's original problem a little bit: the original racing issue occurs when reading CycleState in in-tree plugins, this indicates one of the (out-of-tree) plugins is (over)writing the most high-level value of the CycleState map. But if we control the locking inside the out-of-tree plugin, and mutate that particular in-place, that would be good enough? Case 3 in the above program demonstrates the correct way to manipulate the specific out-of-tree state. Let me know your thoughts. If it resolves 's concern, we don't need to make any change on the Filter() interface.\nCase 3 is how I am working around the problem today to avoid the race. I write a \"data bag\" once into top level in , then only modify my own inner structure (with proper locking) in , without doing any further modifications to directly (top level) in . That is acceptable, but I'd encourage you to consider making the interface (and documentation) more explicit for plugins, so they avoid the mistake of writing directly into . Without changing anything (no documentation, no readonly interface), it is pretty easy for a plugin to use in a way that you don't want to support.\nThanks for confirming that. Yes, documenting it, or(and) publishing examples would be quite helpful to clarify the semantics. As a wrap-up: a keyed value can be read from CycleState, literally , in any phase. It's always race-free.", "commid": "kubernetes_issue_95887", "tokennum": 455}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f1474a70c2f6cf8bcad84a497fe22704eb95dda435f4bdf926ada1c2336e6682", "query": "if pod == nil { return framework.NewStatus(framework.Error, \"pod cannot be nil\") } <del> state.RLock() defer state.RUnlock() </del> if v, e := state.Read(framework.StateKey(pod.Name)); e == nil { if value, ok := v.(*stateData); ok && value.data == \"never bind\" { return framework.NewStatus(framework.Unschedulable, \"pod is not permitted\")", "positive_passages": [{"docid": "doc-en-kubernetes-3be32b87589c297c7c2842b086ef786e82de3563d7c057c1ca18b1f858ccd170", "text": "if you want to mutate the top-level keyed value in CycleState, if it's a phase that CycleState is accessed consecutively, such as PreFilter, PreScore, it's safe to mutate CycleState in any manner if it's a phase that CycleState is accessed parallelly, to be race-free, (for now) you only have 1 option: keep the keyed value's pointer unchanged, and use an internal lock to mutate that pointer obj [TBD] we may come up with changes to add read locks to all in-tree plugins when reading values from CycleState, so that the out-of-tree plugin can surround its mutating logic between and - th mutating logic thereby can be any style Any thoughts on the TBD item? I would assume read locks wouldn't cost too much.\nFor now, I think the documentation is correct, it clearly says Read() and Write() are not thread-safe: The key thing here is whether in-tree plugin should use RLock/RUnlock or not. If yes, out-of-tree plugins can be freed to use Lock/Unlock. (see the TBD item in the previous comment)\nI like the TBD, and optimizing for correctness in how in-tree plugins are accessing . I understand the concern with synchronization overhead, but I would be really surprised if it is the bottleneck in scheduling code.\nIt can be, when you have 5k-nodes clusters, or bigger.\nI don't think it will be expensive, a rlock should be equivalent to an atomic add operation (basically it increments the number of readers). As a comparison, looking up the state from the map is likely to be more expensive.\nOf course we are assuming no contention in the default plugins.\nThis is my impression as well. A vanilla version of scheduler doesn't impose write lock in Filter() and Score(), so should be good.\nWe can always see with the benchmarks and revert if its not negligible.\nI will run the benchmarks to see if there is perf downgrade. /assign\nIssues 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\n/remove-lifecycle stale This is still relevant, yes?", "commid": "kubernetes_issue_95887", "tokennum": 535}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f1474a70c2f6cf8bcad84a497fe22704eb95dda435f4bdf926ada1c2336e6682", "query": "if pod == nil { return framework.NewStatus(framework.Error, \"pod cannot be nil\") } <del> state.RLock() defer state.RUnlock() </del> if v, e := state.Read(framework.StateKey(pod.Name)); e == nil { if value, ok := v.(*stateData); ok && value.data == \"never bind\" { return framework.NewStatus(framework.Unschedulable, \"pod is not permitted\")", "positive_passages": [{"docid": "doc-en-kubernetes-bcac7b47c31a3bdcd9ddd71bfacab7dca4a98e08ad1188f8a89f61b6d0a63d38", "text": "IIUC the volumebinding plugin has been fixed, but external plugins can still shoot themselves in the foot.\n/priority backlog\nYes. I'm working on this, late this week I will send out a PR along with perf test result.", "commid": "kubernetes_issue_95887", "tokennum": 53}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f14a1033278e09a7a45e0218a3acc1220729663323bc341cf328c0685bbd19c4", "query": "} } <ins> func TestValidateFinalizersUpdate(t *testing.T) { testcases := map[string]struct { Old         api.ObjectMeta New         api.ObjectMeta ExpectedErr string }{ \"invalid adding finalizers\": { Old:         api.ObjectMeta{Name: \"test\", ResourceVersion: \"1\", DeletionTimestamp: &unversioned.Time{}, Finalizers: []string{\"x/a\"}}, New:         api.ObjectMeta{Name: \"test\", ResourceVersion: \"1\", DeletionTimestamp: &unversioned.Time{}, Finalizers: []string{\"x/a\", \"y/b\"}}, ExpectedErr: \"y/b\", }, \"invalid changing finalizers\": { Old:         api.ObjectMeta{Name: \"test\", ResourceVersion: \"1\", DeletionTimestamp: &unversioned.Time{}, Finalizers: []string{\"x/a\"}}, New:         api.ObjectMeta{Name: \"test\", ResourceVersion: \"1\", DeletionTimestamp: &unversioned.Time{}, Finalizers: []string{\"x/b\"}}, ExpectedErr: \"x/b\", }, \"valid removing finalizers\": { Old:         api.ObjectMeta{Name: \"test\", ResourceVersion: \"1\", DeletionTimestamp: &unversioned.Time{}, Finalizers: []string{\"x/a\", \"y/b\"}}, New:         api.ObjectMeta{Name: \"test\", ResourceVersion: \"1\", DeletionTimestamp: &unversioned.Time{}, Finalizers: []string{\"x/a\"}}, ExpectedErr: \"\", }, \"valid adding finalizers for objects not being deleted\": { Old:         api.ObjectMeta{Name: \"test\", ResourceVersion: \"1\", Finalizers: []string{\"x/a\"}}, New:         api.ObjectMeta{Name: \"test\", ResourceVersion: \"1\", Finalizers: []string{\"x/a\", \"y/b\"}}, ExpectedErr: \"\", }, } for name, tc := range testcases { errs := ValidateObjectMetaUpdate(&tc.New, &tc.Old, field.NewPath(\"field\")) if len(errs) == 0 { if len(tc.ExpectedErr) != 0 { t.Errorf(\"case: %q, expected error to contain %q\", name, tc.ExpectedErr) } } else if e, a := tc.ExpectedErr, errs.ToAggregate().Error(); !strings.Contains(a, e) { t.Errorf(\"case: %q, expected error to contain %q, got error %q\", name, e, a) } } } </ins> func TestValidateObjectMetaUpdatePreventsDeletionFieldMutation(t *testing.T) { now := unversioned.NewTime(time.Unix(1000, 0).UTC()) later := unversioned.NewTime(time.Unix(2000, 0).UTC())", "positive_passages": [{"docid": "doc-en-kubernetes-fc09a9ef1f5e957552c4803f2a8d5445e8992bd48fceb2f6d692294e4122c44c", "text": "says \"If the deletionTimestamp of the object is non-nil, entries in this list can only be removed.\". can you elucidate if I am assuming this does something different than reality\nThis is garbage collection finalizer field, not the namespace finalizer field that that new field was inspired from On Thursday, September 8, 2016, Tim Hockin wrote:\nI don't parse that - is this not a general-purpose \"refcount\" thing? It seems to work that way, except not as documented\nThis is a general purpose field and it should work like Tim thinks it should work. can you take a look at this when you don't have anything pressing for 1.4?\nThe namespace finalizer should switch to using this field if it is currently doing something else.\nI'm adding validation rule to prevent adding finalizers if deletionTimestamps is set. I'm still investigating why it can't be removed. This bug is strange.\nActually I guess it's a bug. It uses patch, and patch doesn't work on list of simple type, is a list of string.\nYep, it's a bug. I used to remove one finalizer and it worked as expected. I think this is a known bug of , we don't have a way to specify the mergekey of a list of simple type.\nIs there a bug open for this? Frankly, if is going to fail for things like this, we should not be offering it as a feature, or it should use PUT rather than PATCH , Chao Xu wrote:\nCreated cannot use PUT, because it's doing a three way merge (current state, last configuration, current configuration).\nThese are intended for automated use, not human use, so kubectl edit not working is just unfortunate, not a blocker. Although it's really unfortunate that PATCH is so broken. , Chao Xu wrote:\nWhy does need to be 3-way? I don't think that is the semantic a user would expect from an edit operation AT ALL. It certainly surprised ME. WRT automated vs human - if PATCH doesn't work (worse - says it succeeded but didn't) for some class of fields, then PATCH doesn't work, and we should not support it. Full stop. It's going to end up causing someone an outage. These are not necessarily related to this bug, but I'd call them pretty serious flaws.", "commid": "kubernetes_issue_32339", "tokennum": 515}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f14a1033278e09a7a45e0218a3acc1220729663323bc341cf328c0685bbd19c4", "query": "} } <ins> func TestValidateFinalizersUpdate(t *testing.T) { testcases := map[string]struct { Old         api.ObjectMeta New         api.ObjectMeta ExpectedErr string }{ \"invalid adding finalizers\": { Old:         api.ObjectMeta{Name: \"test\", ResourceVersion: \"1\", DeletionTimestamp: &unversioned.Time{}, Finalizers: []string{\"x/a\"}}, New:         api.ObjectMeta{Name: \"test\", ResourceVersion: \"1\", DeletionTimestamp: &unversioned.Time{}, Finalizers: []string{\"x/a\", \"y/b\"}}, ExpectedErr: \"y/b\", }, \"invalid changing finalizers\": { Old:         api.ObjectMeta{Name: \"test\", ResourceVersion: \"1\", DeletionTimestamp: &unversioned.Time{}, Finalizers: []string{\"x/a\"}}, New:         api.ObjectMeta{Name: \"test\", ResourceVersion: \"1\", DeletionTimestamp: &unversioned.Time{}, Finalizers: []string{\"x/b\"}}, ExpectedErr: \"x/b\", }, \"valid removing finalizers\": { Old:         api.ObjectMeta{Name: \"test\", ResourceVersion: \"1\", DeletionTimestamp: &unversioned.Time{}, Finalizers: []string{\"x/a\", \"y/b\"}}, New:         api.ObjectMeta{Name: \"test\", ResourceVersion: \"1\", DeletionTimestamp: &unversioned.Time{}, Finalizers: []string{\"x/a\"}}, ExpectedErr: \"\", }, \"valid adding finalizers for objects not being deleted\": { Old:         api.ObjectMeta{Name: \"test\", ResourceVersion: \"1\", Finalizers: []string{\"x/a\"}}, New:         api.ObjectMeta{Name: \"test\", ResourceVersion: \"1\", Finalizers: []string{\"x/a\", \"y/b\"}}, ExpectedErr: \"\", }, } for name, tc := range testcases { errs := ValidateObjectMetaUpdate(&tc.New, &tc.Old, field.NewPath(\"field\")) if len(errs) == 0 { if len(tc.ExpectedErr) != 0 { t.Errorf(\"case: %q, expected error to contain %q\", name, tc.ExpectedErr) } } else if e, a := tc.ExpectedErr, errs.ToAggregate().Error(); !strings.Contains(a, e) { t.Errorf(\"case: %q, expected error to contain %q, got error %q\", name, e, a) } } } </ins> func TestValidateObjectMetaUpdatePreventsDeletionFieldMutation(t *testing.T) { now := unversioned.NewTime(time.Unix(1000, 0).UTC()) later := unversioned.NewTime(time.Unix(2000, 0).UTC())", "positive_passages": [{"docid": "doc-en-kubernetes-9d31dc444c003a67666d57a34035c70818d4ce333ea6367245ecb1f620bc17fd", "text": ", Daniel Smith wrote:\nDiscussed in real life. PATCH works, it's just that there are certain operations you cannot express using the strategicmerge patch syntax. I was wrong. is building . So perhaps it uses PATCH over PUT due to the efficiency.\nFWIW, I printed out the patch generated by when I removed one finalizer. The patch is empty, i.e., \"{}\".\n, Chao Xu wrote: Well, no, if there are operations that can not be represented, it really DOESN'T work. I still think it should not use PUT, but I bet Brian can prove me wrong.", "commid": "kubernetes_issue_32339", "tokennum": 129}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f18493885d7a515788a71305b971a62f1be8eca60c66ec97d5b9aeeb16ef57d9", "query": "package clouddns import ( <ins> \"google.golang.org/api/googleapi\" </ins> \"k8s.io/kubernetes/federation/pkg/dnsprovider\" \"k8s.io/kubernetes/federation/pkg/dnsprovider/providers/google/clouddns/internal/interfaces\" )", "positive_passages": [{"docid": "doc-en-kubernetes-2b4d325d4814fe81f2a99615b844cff823940de918e3b360e7f108b94b4fe81b", "text": "/kind bug What happened: walteraa [6:55 AM] Hi, The controller manager of the federation using Google cloud DNS is crashing, the log showed is that: the hyperkube command is that: I have created this in the Google DNS Someone knows why the DNS zone query is getting the 404 error?? :disappointed: What you expected to happen: It should have created the missing domain. How to reproduce it (as minimally and precisely as possible): As per above. Anything else we need to know?: Environment: Kubernetes version (use ): 1.7.4 Cloud provider or hardware configuration**: OpenStack (irrelevant) OS (e.g. from /etc/os-release): irrelevant Kernel (e.g. ): irrelevant Install tools: irrelevant Others: irrelevant\nThe bug is related to this: The above code assumes that the provider code returns no error but an empty list if the domain does not exist, but instead the provider returns a 404. Need to fix the provider and/or the above code.\n/sig federation\nI am unlikely to have time to work on this soon, so if anyone else wants to, go right ahead.\n/assign\nAn additional information: I have created a which is based on the credential JSON file created through instruction. After that, I have configured the Federation controller manager to mount this secret as a volume in the container and set the environment variable to the JSON file inside this volume. Before doing that, I was getting an authentication error so the google DNS provider couldn't be instantiated, and after doing the instructions that I mentioned before, this authentication error was solved but now I'm getting 404 error when Google DNS provider tries access the specified managed zone. The file that I have generated follow this structure:", "commid": "kubernetes_issue_51139", "tokennum": 376}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f1b9c367b2a1e04982f5b584f64cb75454395d8590120c6ca6dd5b3c5d45a1ae", "query": "// Package discovery provides ways to discover server-supported // API groups, versions and resources. <del> package discovery </del> <ins> package discovery // import \"k8s.io/client-go/discovery\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-460ceb7b52a1ab0cadc1b29d7eee5cc1013b8d23be9bca0d145119ffcf7b27c6", "text": "Look at one of the directories under (Please don't pick more than one directory for one PR as it will cause issues for reviewers) Find all the files named (example find -name ) See the following link it has a this tells tools how this package needs to be imported. So we should ensure that each has an import Add a description appropriate to the package (similar to the one below) Look through sub directories and see if there are any other important directories that are likely to be used by outside users and add a Why are we doing this? We perfer to use vanity urls instead of directly using to refer to code, so this helps ensure that tools honor our wish. See It would be good to have some package level documentation since these directories under staging/ are meant to be for use by folks outside of kubernetes github org. /good-first-issue\n/kind documentation /sig architecture\ncurrently working my through Not going to use / assign since there could be a number of PRs for this issue.\n/lifecycle active /good-first-issue edit: hmm..\nThis request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /lifecycle active /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\nMay I try on\nIIUC this means that there needs to be a even at the root of the repo? Then how does work? :thinking:\nHi , can I make a PR for this directory ?\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_68231", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f1b9c367b2a1e04982f5b584f64cb75454395d8590120c6ca6dd5b3c5d45a1ae", "query": "// Package discovery provides ways to discover server-supported // API groups, versions and resources. <del> package discovery </del> <ins> package discovery // import \"k8s.io/client-go/discovery\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-5f31f1c27d7198dc83b313154ff681043a8b41e17eb5d3ddf32cd84bc023f931", "text": "/lifecycle rotten\nI guess this is still not done, was supposed to partially fix this issue. /reopen\nReopened this issue. <detailsIn response to : I guess this is still not done, was supposed to partially fix this 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\n/remove-lifecycle rotten /area code-organization", "commid": "kubernetes_issue_68231", "tokennum": 93}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f1d2a6d7624183b6c4c3f30454cd5f039f8b07e5932cffb28bded5189e8a6557", "query": "serviceHasSynced = func() bool { return true } } <del> nodeIndexer := cache.NewIndexer(cache.MetaNamespaceKeyFunc, cache.Indexers{}) </del> <ins> var nodeHasSynced cache.InformerSynced var nodeLister corelisters.NodeLister </ins> if kubeDeps.KubeClient != nil { <del> fieldSelector := fields.Set{api.ObjectNameField: string(nodeName)}.AsSelector() nodeLW := cache.NewListWatchFromClient(kubeDeps.KubeClient.CoreV1().RESTClient(), \"nodes\", metav1.NamespaceAll, fieldSelector) r := cache.NewReflector(nodeLW, &v1.Node{}, nodeIndexer, 0) go r.Run(wait.NeverStop) </del> <ins> kubeInformers := informers.NewSharedInformerFactoryWithOptions(kubeDeps.KubeClient, 0, informers.WithTweakListOptions(func(options *metav1.ListOptions) { options.FieldSelector = fields.Set{api.ObjectNameField: string(nodeName)}.String() })) nodeLister = kubeInformers.Core().V1().Nodes().Lister() nodeHasSynced = func() bool { if kubeInformers.Core().V1().Nodes().Informer().HasSynced() { klog.Infof(\"kubelet nodes sync\") return true } klog.Infof(\"kubelet nodes not sync\") return false } kubeInformers.Start(wait.NeverStop) klog.Info(\"Kubelet client is not nil\") } else { // we dont have a client to sync! nodeIndexer := cache.NewIndexer(cache.MetaNamespaceKeyFunc, cache.Indexers{}) nodeLister = corelisters.NewNodeLister(nodeIndexer) nodeHasSynced = func() bool { return true } klog.Info(\"Kubelet client is nil\") </ins> } <del> nodeLister := corelisters.NewNodeLister(nodeIndexer) </del> // TODO: get the real node object of ourself, // and use the real node name and UID.", "positive_passages": [{"docid": "doc-en-kubernetes-8476bba8e23a7ed885cd34c1077ce17dbf12901ac7ae9725333264f6ea8cfdae", "text": "What happened: A deployment is created that uses a after the cluster master is created but before the cluster worker nodes are fully initialized. During the initialization of the worker nodes, the nodes are temporarily available for scheduling without the necessary label to match the deployment's node selector. Depending on how long the nodes are available for scheduling without the necessary node labels for the deployment, the scheduler will start to spam with cluster with pods in status. This spamming stops once the worker nodes are fully initialized and the pods are scheduled successful. The exact timing of all of this is TBD. What you expected to happen: Pods in status are annoying and require manual cleanup. It would be preferred that the scheduler avoid this an simply issue warning events. How to reproduce it (as minimally and precisely as possible): See issue description. Anything else we need to know?: No. Environment: Kubernetes version (use ): 1.18.3 Cloud provider or hardware configuration: IBM Cloud Kubernetes Service OS (e.g: ): Ubuntu 18.04.4 LTS Kernel (e.g. ): 4.15.0-96-generic Install tools: Managed service install Network plugin and version (if this is a network-related bug): N/A Others: N/A\nRelated to and\n/sig scheduling\nby spamming are you referring to scheduler logs? also, why are the nodes not labelled from the get go?\nJust to confirm, all the pods in question are still in Pending state, yes? If the pods are in pending state, all of them will get scheduled eventually once the nodes get their labels.\nThe pods are not in state. They are actually in state. The pods eventually get scheduled but we are left with anywhere from a few to dozens of these state pods. Also, we are looking at labeling the nodes via kubelet flags to see if that helps.\n/remove-kind bug\nAfter we add some retry logic and wait time in this problem can be solved: As you can see this function returns initial node as the first request failed.\nI also get hit by this, when single controller node gets rebooted and scheduler starts as static container before kubelet becomes ready.", "commid": "kubernetes_issue_92067", "tokennum": 465}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f1d2a6d7624183b6c4c3f30454cd5f039f8b07e5932cffb28bded5189e8a6557", "query": "serviceHasSynced = func() bool { return true } } <del> nodeIndexer := cache.NewIndexer(cache.MetaNamespaceKeyFunc, cache.Indexers{}) </del> <ins> var nodeHasSynced cache.InformerSynced var nodeLister corelisters.NodeLister </ins> if kubeDeps.KubeClient != nil { <del> fieldSelector := fields.Set{api.ObjectNameField: string(nodeName)}.AsSelector() nodeLW := cache.NewListWatchFromClient(kubeDeps.KubeClient.CoreV1().RESTClient(), \"nodes\", metav1.NamespaceAll, fieldSelector) r := cache.NewReflector(nodeLW, &v1.Node{}, nodeIndexer, 0) go r.Run(wait.NeverStop) </del> <ins> kubeInformers := informers.NewSharedInformerFactoryWithOptions(kubeDeps.KubeClient, 0, informers.WithTweakListOptions(func(options *metav1.ListOptions) { options.FieldSelector = fields.Set{api.ObjectNameField: string(nodeName)}.String() })) nodeLister = kubeInformers.Core().V1().Nodes().Lister() nodeHasSynced = func() bool { if kubeInformers.Core().V1().Nodes().Informer().HasSynced() { klog.Infof(\"kubelet nodes sync\") return true } klog.Infof(\"kubelet nodes not sync\") return false } kubeInformers.Start(wait.NeverStop) klog.Info(\"Kubelet client is not nil\") } else { // we dont have a client to sync! nodeIndexer := cache.NewIndexer(cache.MetaNamespaceKeyFunc, cache.Indexers{}) nodeLister = corelisters.NewNodeLister(nodeIndexer) nodeHasSynced = func() bool { return true } klog.Info(\"Kubelet client is nil\") </ins> } <del> nodeLister := corelisters.NewNodeLister(nodeIndexer) </del> // TODO: get the real node object of ourself, // and use the real node name and UID.", "positive_passages": [{"docid": "doc-en-kubernetes-6c53201dbb91d52a8ade960092a5ed582f4d35e33a53b75d555d15ae815dc25c", "text": "Can be cleaned up with:\n/sig node\nthe spam cycle is this loop: \"pod create, pod schedule, worker reject, pod failed\" -- we don't have a lot of protection in higher level workload controllers to handle pods that fail at kubelet admission time versus pods that just dont create due to quota/admission. in general, is the spam causing any other stability issues? is pod gc pruning the pods?\nI wonder if we can do a trick in node lister to mitigate any race condition here...\nwe could maybe do something similar to to ensure node lister has synced...\nhacking on option to ensure if kubelet has a node lister with a valid kube client, we wait for it to sync at least once here which should mitigate this issue. see:\nWe noticed the problem on the OLM pod which is managed by the OLM operator. Right or wrong, the operator does not like seeing the pod go to status and no longer reconciles the pod. The end result is that manual intervention (i.e. pod deletion) is required to fix the problem.\nsure... i would have thought the pod is failed in that instance and reached a terminal state. either way, i am looking at what i can do to mitigate this.\nThe problem persists in our environment as well, and the workaround cited above will not do anymore. Is there something in the works for this one?\nIssues 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\n/remove-lifecycle stale", "commid": "kubernetes_issue_92067", "tokennum": 383}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f204246583119678e6d8eea34180fa08b4d4b4795277a01cb5f4b986f5ae26f5", "query": "b.Do().Visit(func(r *resource.Info) error { services := r.Object.(*api.ServiceList).Items for _, service := range services { <del> link := client.Host + \"/api/v1beta3/proxy/namespaces/\" + service.ObjectMeta.Namespace + \"/services/\" + service.ObjectMeta.Name </del> <ins> var link string if len(service.Spec.PublicIPs) > 0 { for _, port := range service.Spec.Ports { link += \"http://\" + service.Spec.PublicIPs[0] + \":\" + strconv.Itoa(port.Port) + \" \" } } else { link = client.Host + \"/api/v1beta3/proxy/namespaces/\" + service.ObjectMeta.Namespace + \"/services/\" + service.ObjectMeta.Name } </ins> printService(out, service.ObjectMeta.Labels[\"name\"], link) } return nil", "positive_passages": [{"docid": "doc-en-kubernetes-0f269e408c0c5ca583af123d217b4d1fb7160d426de10d2601450f917f382cd5", "text": "I an ELB to the Kibana cluster log viewer but it is not reported by which, aside from having a URL, should check each cluster service and if it has an external IP it should report that instead of the master proxy address.\ncc", "commid": "kubernetes_issue_7521", "tokennum": 50}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f225138590d09c49cee89a28381cff37387733e001a4c63eb022aaf995729992", "query": "framework.ExpectNoError(err, \"failed to delete Service %v in namespace %v\", testService.ObjectMeta.Name, ns) framework.Logf(\"Service %s deleted\", testSvcName) }) <ins> ginkgo.It(\"should delete a collection of services\", func() { ns := f.Namespace.Name svcClient := f.ClientSet.CoreV1().Services(ns) svcResource := schema.GroupVersionResource{Group: \"\", Version: \"v1\", Resource: \"services\"} svcDynamicClient := f.DynamicClient.Resource(svcResource).Namespace(ns) svcLabel := map[string]string{\"e2e-test-service\": \"delete\"} deleteLabel := labels.SelectorFromSet(svcLabel).String() ginkgo.By(\"creating a collection of services\") testServices := []struct { name  string label map[string]string port  int }{ { name:  \"e2e-svc-a-\" + utilrand.String(5), label: map[string]string{\"e2e-test-service\": \"delete\"}, port:  8001, }, { name:  \"e2e-svc-b-\" + utilrand.String(5), label: map[string]string{\"e2e-test-service\": \"delete\"}, port:  8002, }, { name:  \"e2e-svc-c-\" + utilrand.String(5), label: map[string]string{\"e2e-test-service\": \"keep\"}, port:  8003, }, } for _, testService := range testServices { func() { framework.Logf(\"Creating %s\", testService.name) svc := v1.Service{ ObjectMeta: metav1.ObjectMeta{ Name:   testService.name, Labels: testService.label, }, Spec: v1.ServiceSpec{ Type: \"ClusterIP\", Ports: []v1.ServicePort{{ Name:       \"http\", Protocol:   v1.ProtocolTCP, Port:       int32(testService.port), TargetPort: intstr.FromInt(testService.port), }}, }, } _, err := svcClient.Create(context.TODO(), &svc, metav1.CreateOptions{}) framework.ExpectNoError(err, \"failed to create Service\") }() } svcList, err := cs.CoreV1().Services(ns).List(context.TODO(), metav1.ListOptions{}) framework.ExpectNoError(err, \"failed to list Services\") framework.ExpectEqual(len(svcList.Items), 3, \"Required count of services out of sync\") ginkgo.By(\"deleting service collection\") err = svcDynamicClient.DeleteCollection(context.TODO(), metav1.DeleteOptions{}, metav1.ListOptions{LabelSelector: deleteLabel}) framework.ExpectNoError(err, \"failed to delete service collection. %v\", err) svcList, err = cs.CoreV1().Services(ns).List(context.TODO(), metav1.ListOptions{}) framework.ExpectNoError(err, \"failed to list Services\") framework.ExpectEqual(len(svcList.Items), 1, \"Required count of services out of sync\") framework.Logf(\"Collection of services has been deleted\") }) </ins> }) // execAffinityTestForSessionAffinityTimeout is a helper function that wrap the logic of", "positive_passages": [{"docid": "doc-en-kubernetes-5e1e446ffee113a0fecf68600791d8062befcc769908a1fdd16ec9abcfdd9c85", "text": "[X] Two weeks soak end date: Nov 18 According to this APIsnoop query, there are still a remaining Service endpoint which is untested. A service resource didn&rsquo;t support endpoint until was merged. Create a watch to track service events Create a service with a static label. Confirm via the watch that the service was created. Delete the service via the service with the dynamic client with . Confirm via the watch that the service was deleted. The above steps have been implemented in the follwing . This query shows all the endpoints hit within a short period of running the above e2e test If a test with these calls gets merged, test coverage will go up by 1 point This test is also created with the goal of conformance promotion. /sig testing /sig network /area conformance\n/triage accepted\nWaiting on 2 week soak before promoting the test to conformance /reopen\nReopened this issue. <detailsIn response to : Waiting on 2 week soak before promoting the test to conformance /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_106032", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f24c5685fa6bb01dd198f367c52265d44ef66880fbed7b1d6e67f1636d09fa98", "query": "if pod.Name != mirrorPod.Name || pod.Namespace != mirrorPod.Namespace { return false } <del> return api.Semantic.DeepEqual(&pod.Spec, &mirrorPod.Spec) </del> <ins> hash, ok := getHashFromMirrorPod(mirrorPod) if !ok { return false } return hash == getPodHash(pod) </ins> } func podsMapToPods(UIDMap map[types.UID]*api.Pod) []*api.Pod {", "positive_passages": [{"docid": "doc-en-kubernetes-8bc8d69d49aedfb4a9bf3991de80f7c339e96bfbefe5b1f250dae70fa0393729", "text": "See for more context. Currently, kubelet compares the spec of a mirror pod (created via apiserver) with that of a static pod (config stored as a file) to decide whether the two are considered identical. If they differ, kubelet would delete the mirror pod and re-create it with the correct spec. Due to the fact that apiserver may set default values for some fields in the spec of the mirror pod, the specs could deviate undesirably. To avoid problems like this, we can store the config of a static pod as an annotation in the mirror pod, and compare the static pod with the annotation.\nWould a hash of the config be sufficient if we're only going to compare? The whole spec would generally be more useful, but I wonder if that is too much data to put in an annotation.\nThis seems totally reasonable to me, but I'm still desperately curious why you can't just bypass defaulting when you generate mirror pod from static pod? (i.e. just use the static pod's configuration verbatim)\nIt's not kubelet who applies the default values here. The admission plugin was only run at the apiserver, and to bypass that, you have to ask apiserver to treat mirror pods differently and potentially at multiple places.\nOn May 22, 2015 10:38 AM, \"Yu-Ju Hong\" wrote: Understood, but is it really multiple places? If so then I agree it's a bad idea. Otherwise it might be worth considering as an alternative.\nIt's untenable for Kubelet to assume to know/circumvent all fields that will be set by other entities: admission control, defaulting, late initialization, auto-something, whatever. It needs to obey the same rules as other clients.\nI don't understand why you would ever want to apply any of the things you mentioned to static pods. Static pods should be copied verbatim into the mirror pods, right? That's what I'm proposing.\nWhat if the master is updated before the kubelet, and the master adds a new API field with a default value?\nThat case should be discussed in\nI agree that mirror pod should reflect the true status of the static pod running on the node, and no default values should be set in this case.", "commid": "kubernetes_issue_8683", "tokennum": 499}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f24c5685fa6bb01dd198f367c52265d44ef66880fbed7b1d6e67f1636d09fa98", "query": "if pod.Name != mirrorPod.Name || pod.Namespace != mirrorPod.Namespace { return false } <del> return api.Semantic.DeepEqual(&pod.Spec, &mirrorPod.Spec) </del> <ins> hash, ok := getHashFromMirrorPod(mirrorPod) if !ok { return false } return hash == getPodHash(pod) </ins> } func podsMapToPods(UIDMap map[types.UID]*api.Pod) []*api.Pod {", "positive_passages": [{"docid": "doc-en-kubernetes-0491e123884f0f20f50d0a788bca7a6a29e2fa08227703a00221ecbd3bcf483c", "text": "However, I think it'd be harder to implement this way since, as stated above, that there are many things to circumvent in the apiserver itself. It could also be harder to keep this special case from being broken by a yet another new feature/plugin. Keeping the hash of the config in the annotation seems like a good compromise even though it may not reflect the true status 100% accurately. I think this is acceptable. What do you think?\nSure, if you think the annotation approach is easier, I would go with that. I guess in the case Brian mentoined (master adds a new API field with a default value), you would not update the mirror pod, because the static pod definition has not changed?\nYes, a hash would be sufficient.\nIt shouldn't be necessary to update the mirror pod in the case that a new default field was updated, because that field should be populated automatically by the apiserver on decode from etcd.\nWe should fix this so we don't have this problem again in 1.2.", "commid": "kubernetes_issue_8683", "tokennum": 226}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f25ee5470849701b59b97001f00a458a23ad30592940f31728ca8ce2e9c77c30", "query": "return p, err } <del> // waitForRCPodToDisappear returns nil if the pod from the given replication controller (described by rcName) no longer exists. // In case of failure or too long waiting time, an error is returned. func waitForRCPodToDisappear(c *client.Client, ns, rcName, podName string) error { label := labels.SelectorFromSet(labels.Set(map[string]string{\"name\": rcName})) return wait.Poll(20*time.Second, 5*time.Minute, func() (bool, error) { </del> <ins> func waitForPodToDisappear(c *client.Client, ns, podName string, label labels.Selector, interval, timeout time.Duration) error { return wait.Poll(interval, timeout, func() (bool, error) { </ins> Logf(\"Waiting for pod %s to disappear\", podName) pods, err := c.Pods(ns).List(label, fields.Everything()) if err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-57d83ef880aa3c3668480a2a99a63d94dfed9404bcfb6c9db559f5ee8b331861", "text": "More detail can be seen in e2e test\ncc\n, Marek Grabowski wrote:\nyou are running an older version of the test. can you get the latest and try again ? This test had not failed at all yesterday in our automated test runs yesterday. Closing issue for now.\nThis failure depends on if the pod is really deleted and kube-proxy (the test container on) catch that the endpoint is deleted in 5s . After sending \"delete pod\" request for 5s, if the pod was still there and kube-proxy still contains this endpoints(this may happen under pressure), hit test can still detect 5 endpoints. At least we should ensure the pod was deleted. Anyway, I think will be helpful to this test. What do you think?\nIt doesn't matter if the pod is actually deleted or not. We just care that kube-proxy thinks that it should not be part of the service endpoint. Having said that, it still doesn't hurt to do the check that you are doing. I will assign your PR to myself and review it. In the meantime, can you rebase your PR ?\nThanks for your review. The PR is up to date.\nFailed twice today in kubernetes-e2e-gce-parallel\nOne more today. The error message is not very helpful.\n18:28:37 STEP: dialing(http) endpointPodIP:endpointHttpPort from node1 18:28:37 STEP: Dialing from node. command:for i in ' wc -l This is the point where the test fails. Am looking into it. We need to have more tries, we just do seq (1 1), instead of seq (6 6). this is causing flakiness.\nFixed by PR", "commid": "kubernetes_issue_14342", "tokennum": 372}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f28523489dbbebc6eb5a04614cf33647cab55e841322e1d19e7420a73672e9b8", "query": "}, }, }, <del> map[string]interface{}{\"field\": map[string]interface{}{}}, }, false}, {\"!nullable against null\", args{ apiextensions.JSONSchemaProps{ Properties: map[string]apiextensions.JSONSchemaProps{ \"field\": { Type:     \"object\", Nullable: false, }, }, </del> <ins> objects: []interface{}{ map[string]interface{}{}, map[string]interface{}{\"field\": map[string]interface{}{}}, </ins> }, <del> map[string]interface{}{\"field\": nil}, }, true}, {\"!nullable against undefined\", args{ apiextensions.JSONSchemaProps{ </del> <ins> failingObjects: []interface{}{ map[string]interface{}{\"field\": \"foo\"}, map[string]interface{}{\"field\": 42}, map[string]interface{}{\"field\": true}, map[string]interface{}{\"field\": 1.2}, map[string]interface{}{\"field\": []interface{}{}}, }, }, {name: \"nullable\", schema: apiextensions.JSONSchemaProps{ </ins> Properties: map[string]apiextensions.JSONSchemaProps{ \"field\": { Type:     \"object\", <del> Nullable: false, </del> <ins> Nullable: true, </ins> }, }, }, <del> map[string]interface{}{}, }, false}, {\"nullable against non-null\", args{ apiextensions.JSONSchemaProps{ </del> <ins> objects: []interface{}{ map[string]interface{}{}, map[string]interface{}{\"field\": map[string]interface{}{}}, map[string]interface{}{\"field\": nil}, }, failingObjects: []interface{}{ map[string]interface{}{\"field\": \"foo\"}, map[string]interface{}{\"field\": 42}, map[string]interface{}{\"field\": true}, map[string]interface{}{\"field\": 1.2}, map[string]interface{}{\"field\": []interface{}{}}, }, }, {name: \"nullable and no type\", schema: apiextensions.JSONSchemaProps{ </ins> Properties: map[string]apiextensions.JSONSchemaProps{ \"field\": { <del> Type:     \"object\", </del> Nullable: true, }, }, }, <del> map[string]interface{}{\"field\": map[string]interface{}{}}, }, false}, {\"nullable against null\", args{ apiextensions.JSONSchemaProps{ </del> <ins> objects: []interface{}{ map[string]interface{}{}, map[string]interface{}{\"field\": map[string]interface{}{}}, map[string]interface{}{\"field\": nil}, map[string]interface{}{\"field\": \"foo\"}, map[string]interface{}{\"field\": 42}, map[string]interface{}{\"field\": true}, map[string]interface{}{\"field\": 1.2}, map[string]interface{}{\"field\": []interface{}{}}, }, }, {name: \"x-kubernetes-int-or-string\", schema: apiextensions.JSONSchemaProps{ </ins> Properties: map[string]apiextensions.JSONSchemaProps{ \"field\": { <del> Type:     \"object\", Nullable: true, </del> <ins> XIntOrString: true, </ins> }, }, }, <del> map[string]interface{}{\"field\": nil}, }, false}, {\"!nullable against undefined\", args{ apiextensions.JSONSchemaProps{ </del> <ins> objects: []interface{}{ map[string]interface{}{}, map[string]interface{}{\"field\": 42}, map[string]interface{}{\"field\": \"foo\"}, }, failingObjects: []interface{}{ map[string]interface{}{\"field\": nil}, map[string]interface{}{\"field\": true}, map[string]interface{}{\"field\": 1.2}, map[string]interface{}{\"field\": map[string]interface{}{}}, map[string]interface{}{\"field\": []interface{}{}}, }, }, {name: \"nullable and x-kubernetes-int-or-string\", schema: apiextensions.JSONSchemaProps{ </ins> Properties: map[string]apiextensions.JSONSchemaProps{ \"field\": { <del> Type:     \"object\", Nullable: true, </del> <ins> Nullable:     true, XIntOrString: true, </ins> }, }, }, <del> map[string]interface{}{}, }, false}, {\"nullable and no type against non-nil\", args{ apiextensions.JSONSchemaProps{ </del> <ins> objects: []interface{}{ map[string]interface{}{}, map[string]interface{}{\"field\": 42}, map[string]interface{}{\"field\": \"foo\"}, map[string]interface{}{\"field\": nil}, }, failingObjects: []interface{}{ map[string]interface{}{\"field\": true}, map[string]interface{}{\"field\": 1.2}, map[string]interface{}{\"field\": map[string]interface{}{}}, map[string]interface{}{\"field\": []interface{}{}}, }, }, {name: \"nullable, x-kubernetes-int-or-string and user-provided anyOf\", schema: apiextensions.JSONSchemaProps{ </ins> Properties: map[string]apiextensions.JSONSchemaProps{ \"field\": { <del> Nullable: true, </del> <ins> Nullable:     true, XIntOrString: true, AnyOf: []apiextensions.JSONSchemaProps{ {Type: \"integer\"}, {Type: \"string\"}, }, </ins> }, }, }, <del> map[string]interface{}{\"field\": 42}, }, false}, {\"nullable and no type against nil\", args{ apiextensions.JSONSchemaProps{ </del> <ins> objects: []interface{}{ map[string]interface{}{}, map[string]interface{}{\"field\": nil}, map[string]interface{}{\"field\": 42}, map[string]interface{}{\"field\": \"foo\"}, }, failingObjects: []interface{}{ map[string]interface{}{\"field\": true}, map[string]interface{}{\"field\": 1.2}, map[string]interface{}{\"field\": map[string]interface{}{}}, map[string]interface{}{\"field\": []interface{}{}}, }, }, {name: \"nullable, x-kubernetes-int-or-string and user-provider allOf\", schema: apiextensions.JSONSchemaProps{ </ins> Properties: map[string]apiextensions.JSONSchemaProps{ \"field\": { <del> Nullable: true, </del> <ins> Nullable:     true, XIntOrString: true, AllOf: []apiextensions.JSONSchemaProps{ { AnyOf: []apiextensions.JSONSchemaProps{ {Type: \"integer\"}, {Type: \"string\"}, }, }, }, </ins> }, }, }, <del> map[string]interface{}{\"field\": nil}, }, false}, {\"invalid regex\", args{ apiextensions.JSONSchemaProps{ </del> <ins> objects: []interface{}{ map[string]interface{}{}, map[string]interface{}{\"field\": nil}, map[string]interface{}{\"field\": 42}, map[string]interface{}{\"field\": \"foo\"}, }, failingObjects: []interface{}{ map[string]interface{}{\"field\": true}, map[string]interface{}{\"field\": 1.2}, map[string]interface{}{\"field\": map[string]interface{}{}}, map[string]interface{}{\"field\": []interface{}{}}, }, }, {name: \"invalid regex\", schema: apiextensions.JSONSchemaProps{ </ins> Properties: map[string]apiextensions.JSONSchemaProps{ \"field\": { Type:    \"string\",", "positive_passages": [{"docid": "doc-en-kubernetes-42eca355948acd2923f06d9ab50c5116c5afebe4d73334e949a0d732f7352d29", "text": "The server-side validation does not check the type of values with . Create a CRD like: Then create a CR: It is not rejected, but should because must not be a boolean.", "commid": "kubernetes_issue_78817", "tokennum": 40}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f286a1e96d66903fca4ee0789949116482edb1c5736ca29bf6dd3033dfb39405", "query": "}, { message: \"{\", <del> err:     \"error stream protocol error: unexpected end of JSON input in \"{\"\", </del> <ins> err:     \"unexpected end of JSON input in \"{\"\", </ins> }, { message: `{\"status\": \"Success\" }`,", "positive_passages": [{"docid": "doc-en-kubernetes-984aaf2876c4d4651f6765b291626bccfb7d6364087d7ebb11c97e2832c59ee5", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Below k8s UT fail when run with master-golang. TestCheckpointStateRestore/RestorecheckpointwithinvalidJSON error:=== RUN TestCheckpointStateRestore/RestorecheckpointwithinvalidJSON I1124 05:38:14. ] [cpumanager] initializing new in-memory state store unexpected error while creatng checkpointState: could not restore state from checkpoint: json: unexpected end of JSON input, please drain this node and delete the CPU manager checkpoint file \"/tmp/cpumanagerstatetest479660663/cpumanagercheckpointtest\" before restarting Kubelet --- FAIL: TestCheckpointStateRestore/RestorecheckpointwithinvalidJSON (0.00s) TestStrategicMergePatchInvalid error:=== RUN TestStrategicMergePatchInvalid expected \"invalid character 'b' looking for beginning of value\", got \"json: invalid character 'b' looking for beginning of value\" --- FAIL: TestStrategicMergePatchInvalid (0.00s) TestJSONPatch error:=== RUN TestJSONPatch invalid-syntax: expected error invalid character 'i' looking for beginning of value, but got json: invalid character 'i' looking for beginning of value --- FAIL: TestJSONPatch (0.00s) TestV4ErrorDecoder expandless error:=== RUN TestV4ErrorDecoder wrong error for message \"{\": want=\"error stream protocol error: unexpected end of JSON input in \"{\"\", got=\"error stream protocol error: json: unexpected end of JSON input in \"{\"\" --- FAIL: TestV4ErrorDecoder (0.00s What you expected to happen: The tests should pass with no error. How to reproduce it (as minimally and precisely as possible): a stable version of golang installed master go from upstream git clone cd go/src cd ../.. cp -r ./go /usr/local export PATH=/usr/local/go/bin:$PATH kubernetes repo and run the unit tests. () Anything else we need to know?: These failures are occurring due to mismatch of error messages between upstream go and the k8s tests.", "commid": "kubernetes_issue_96853", "tokennum": 597}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f286a1e96d66903fca4ee0789949116482edb1c5736ca29bf6dd3033dfb39405", "query": "}, { message: \"{\", <del> err:     \"error stream protocol error: unexpected end of JSON input in \"{\"\", </del> <ins> err:     \"unexpected end of JSON input in \"{\"\", </ins> }, { message: `{\"status\": \"Success\" }`,", "positive_passages": [{"docid": "doc-en-kubernetes-d960907779eeb813df14a2ea4a00c97f52784ded937dbf1c71e5b05391843c78", "text": "There is an addition \"json:\" prefix to SyntaxError messages after this below commit: Environment: Kubernetes version (use ): latest source code from upstream Cloud provider or hardware configuration: OS (e.g: ): \"CentOS Linux 8 (Core)\" Kernel (e.g. ): Linux rajalakshmi-workspace 4.18.0-193.19.1.el82.ppc64le SMP Mon Sep 14 14:48:04 UTC 2020 ppc64le ppc64le ppc64le GNU/Linux Install tools: [root go]# go version go version devel + Fri Nov 20 00:54:43 2020 +0000 linux/ppc64le [root go]# Network plugin and version (if this is a network-related bug): Others:\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig testing\nwill fix it in Go 1.16 as release-blocker.\nI would fix the test here to be more tolerant. exact string matches on error messages aren't really an API\u2026 I would not expect that to block the golang release\nAgree too, we can think about having a substring match to avoid these issues instead!\n/assign Lets see if we can fix this in the k8s tests", "commid": "kubernetes_issue_96853", "tokennum": 352}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f28aa540f00652cdf4d0f03188d3b56eb67f09abfe7af4e61faa98cc4959cf36", "query": "package mount import ( <ins> \"reflect\" </ins> \"strings\" \"testing\" )", "positive_passages": [{"docid": "doc-en-kubernetes-2eda896003caba863d0609f67aa343029dbd4049babda0317e758512fcccca95", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature What happened: In some files, i found that there are many self-contained function, whose feature is as same as some util function. Obviously, they are redundant. What you expected to happen: Use util function to replace self-contained function How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration**: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/assign\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\nsimilar comment to Can you edit the description in to say instead of ? Thanks!\nThanks. Done.", "commid": "kubernetes_issue_50952", "tokennum": 279}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f2a71729954894b52f6cb3a79e046146ca5f30b2edfd719032c2ee9b4d16f1ed", "query": "// Leave something on the stack, so that calls to struct tag getters never fail. s.srcStack.push(scopeStackElem{}) s.destStack.push(scopeStackElem{}) <del> return c.convert(sv, dv, s) </del> <ins> return f(sv, dv, s) </ins> } // callCustom calls 'custom' with sv & dv. custom must be a conversion function.", "positive_passages": [{"docid": "doc-en-kubernetes-518f837785f17a5fd9706a6c0a0614adac703d65f6bb6045d79a025795dcb97b", "text": "Files storing latest versions for minors are not updated since infix was to the version string. Example Similar issues can be found in 1.25 and 1.24 builds (last 1.23 build infix so it has not happened there yet): I expect the files to be overwritten with newer version of the build. Manually run build job for one of the minors. No response Not related. Not related. No response No response No response No response\nI believe this may be also responsible for breaking kubemark tests: since they fail due to version mismatch\n/sig release\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority high 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\nThanks for raising the issue! /cc who is working on before\nI assume this will be fixed automatically with the next patches, because then we would compare with . Anyway, I think we should fix that intermediately by manually updating the version markers to match their correct version. I did that now for the bucket\nWe had to update the versions markers again, because those were pointing to two commits earlier and didn't include the Go updates. The latest version markers are: v1.24.12-35+ v1.25.8-37+ v1.26.3-41+\nlatest-1.27 has been affected by this as well. I updated it manually to v1.27.0-9+. See this thread for more details:\n/triage accepted\nThis should be fixed now, closing it. Feel free to reopen if we missed anything.\nThis issue is still present, see this Slack thread for more details: /reopen\nReopened this issue. <detailsIn response to : This issue is still present, see this Slack thread for more details: /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nWe have a similar situation with latest-1.28 which is currently pointing to: . This is one commit before the release commit: ! It's mostly like that the release step didn't update version markers, we should look into this.", "commid": "kubernetes_issue_117115", "tokennum": 486}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f2a71729954894b52f6cb3a79e046146ca5f30b2edfd719032c2ee9b4d16f1ed", "query": "// Leave something on the stack, so that calls to struct tag getters never fail. s.srcStack.push(scopeStackElem{}) s.destStack.push(scopeStackElem{}) <del> return c.convert(sv, dv, s) </del> <ins> return f(sv, dv, s) </ins> } // callCustom calls 'custom' with sv & dv. custom must be a conversion function.", "positive_passages": [{"docid": "doc-en-kubernetes-5a00e106d863b6b2d6ffe122805a64f76a2709c3a46b9a75024b175401623671", "text": "As of now, I'm going to manually update this version marker to unblock 1.28.1 patch release. I'll also take a look into this. /assign\nThe PR that fixed this issue got reverted so this is still relevant: /reopen\nReopened this issue. <detailsIn response to : The PR that fixed this issue got reverted so this is still relevant: /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nWe're running into this issue again with stable-1.29 marker. It's currently pointing to which is It should instead point to I'm going to manually change it following the same procedure as the last time. Version marker updated to\nThis issue is labeled with but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release. You can: Confirm that this issue is still relevant with (org members only) Deprioritize it with or Close this issue with For more details on the triage process, see /remove-triage accepted\n/triage accepted\nSame issue for 1.30, where I had to update the version marker manually again.", "commid": "kubernetes_issue_117115", "tokennum": 278}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f2d2143a508f3a1e534bec04e74f6be618a436cd4176c1ac3d84ba9cd65e3437", "query": "existingFilterChains := proxier.getExistingChains(proxier.filterChainsData, utiliptables.TableFilter) existingNATChains := proxier.getExistingChains(proxier.iptablesData, utiliptables.TableNAT) <ins> // ensure KUBE-MARK-DROP chain exist but do not change any rules for _, ch := range iptablesEnsureChains { if _, err := proxier.iptables.EnsureChain(ch.table, ch.chain); err != nil { klog.Errorf(\"Failed to ensure that %s chain %s exists: %v\", ch.table, ch.chain, err) return } } </ins> // Make sure we keep stats for the top-level chains for _, ch := range iptablesChains { if _, err := proxier.iptables.EnsureChain(ch.table, ch.chain); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-6cbf7dcb5e6486cb532532a59cda0ac4f93a00ec9c96bc20136b3a20d89cc61b", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: ci-kubernetes-e2e-gci-gce-ipvs Which test(s) are failing: [sig-network] Services should only allow access from service loadbalancer source ranges [Slow] Testgrid link: https://k8s- Reason for failure: Anything else we need to know: The test is failing consistently, however, there is also test that is failing a lot but not always, may it be related?\n/sig-network /area ipvs /cc /help wanted\n/sig network\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/assign\n/remove-triage unresolved\nHi, , turnout this is because mark drop rule in be deleted, I raied a pr to fix this issue, PTAL. : )\n/close as duplicate of\nClosing this issue. <detailsIn response to : /close as duplicate of 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\n/reopen this was affecting ipvs only before , let's keep it open until we verify is not failing anymore\nReopened this issue. <detailsIn response to : /reopen this was affecting ipvs only before , let's keep it open until we verify is not failing anymore 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\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign Ok I tested this out with kind in ipvs-mode with metallb. In iptables mode I had zero failures but ipvs does not pass at all during the timeout window. This is likely due to", "commid": "kubernetes_issue_94356", "tokennum": 488}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f2d3bc4aad61c40584e39737d5d223f0a060e06110f0f5de1877c561caeb5b02", "query": "fi fi <ins> # generate the controller manager token here since its only used on the master. KUBE_CONTROLLER_MANAGER_TOKEN=$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64 | tr -d \"=+/\" | dd bs=32 count=1 2>/dev/null) </ins> # KUBERNETES_CONTAINER_RUNTIME is set by the `kube-env` file, but it's a bit of a mouthful if [[ \"${CONTAINER_RUNTIME:-}\" == \"\" ]]; then CONTAINER_RUNTIME=\"${KUBERNETES_CONTAINER_RUNTIME:-docker}\"", "positive_passages": [{"docid": "doc-en-kubernetes-19a61d82ec14336213ef377c4e39e11807c2ce9673880ce3d82a192d5a783624", "text": "Typically, the dns and dashboard is in crash loop. Ref cc\nif you check the file, does it contain lines like ?\nPrevious comment is ref: from I'll copy that to container-linux as well.", "commid": "kubernetes_issue_39395", "tokennum": 44}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f2e92ff035352b5e99069e5720438db879d6c7cf2b80839556f2a5fac363cf8b", "query": "apierrors \"k8s.io/apimachinery/pkg/api/errors\" \"k8s.io/apimachinery/pkg/api/resource\" metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" <ins> \"k8s.io/apimachinery/pkg/apis/meta/v1/unstructured\" \"k8s.io/apimachinery/pkg/runtime/schema\" \"k8s.io/apimachinery/pkg/types\" </ins> \"k8s.io/apimachinery/pkg/util/sets\" \"k8s.io/apimachinery/pkg/util/wait\" clientset \"k8s.io/client-go/kubernetes\" <ins> \"k8s.io/client-go/util/retry\" </ins> batchinternal \"k8s.io/kubernetes/pkg/apis/batch\" \"k8s.io/kubernetes/test/e2e/framework\" e2ejob \"k8s.io/kubernetes/test/e2e/framework/job\"", "positive_passages": [{"docid": "doc-en-kubernetes-9deab690131da58e4566d26be974a26500a50c4525ef4b542cd9399a25bc940c", "text": "[x] Test PR : [x] Two weeks soak end date : 6 April 2022 [X] Test promotion PR : According to this APIsnoop query, there are still some remaining Job status endpoints which are untested. There are conformance tests for CronJob status endpoints already the existing as a template, a new for job test has been created. The e2e logs for this test are listed below. This query shows the endpoints hit within a short period of running the e2e test If a test with these calls gets merged, test coverage will go up by 3 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance\n/triage accepted\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_108113", "tokennum": 205}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f2f6c47d546d84798950b888afe622a749a7521985a15fa404e29a7fba4bfa18", "query": "import ( \"fmt\" \"sync\" <ins> \"time\" </ins> \"github.com/golang/glog\"", "positive_passages": [{"docid": "doc-en-kubernetes-b8d2c0da68304e83135ba886da3cc34043a1f75faa72e9753c7e99fa612dae72", "text": "From etcd3: May need to retry poststarthook a few times to avoid bootstrapping failures like this.", "commid": "kubernetes_issue_39108", "tokennum": 26}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f31a66de7a792b9ed2eeed3febd01148ea3ffc1f214396ca2acb4d14d508758f", "query": "metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" \"k8s.io/apimachinery/pkg/labels\" \"k8s.io/apimachinery/pkg/util/wait\" <ins> \"k8s.io/apiserver/pkg/admission\" </ins> \"k8s.io/client-go/informers\" clientset \"k8s.io/client-go/kubernetes\" typedappsv1 \"k8s.io/client-go/kubernetes/typed/apps/v1\" typedv1 \"k8s.io/client-go/kubernetes/typed/core/v1\" restclient \"k8s.io/client-go/rest\" \"k8s.io/client-go/util/retry\" <ins> api \"k8s.io/kubernetes/pkg/apis/core\" </ins> //svc \"k8s.io/kubernetes/pkg/api/v1/service\" \"k8s.io/kubernetes/pkg/controller/statefulset\"", "positive_passages": [{"docid": "doc-en-kubernetes-0cad02d163e61aff3cc2c1257b68701a42fb1145e0b51f6816fd9a85adca78e6", "text": "I create a ResourceQuota with two pods limit in my namespace. Then, I create a statefuleSet with 3 replicas. As expected, two pods are created successfully, and the third pod failed to create. But, the ReadyReplicas is not 2 ,but 1. The ReadyReplicas is correct 1Create a ResourceQuota with two pods limit in a new namespace. 2Create a statefulSet with 3 replicas 3Check if the ReadyReplicas of statefulSet matchs the number of stateful running pods. 1According to the logic of the statefulSet controller, new pod created in current sync is not be immediately counted into the ReadyReplicas. 2Failure to create pod will cause to return error, then skip updating status. <details</details<details</details<detailskind v1.23.3 </details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig apps\n/assign", "commid": "kubernetes_issue_108837", "tokennum": 302}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f34dbb4acafd63ebdf0884dcf2c0332708146f8c5e380cfc5a7905d9e45a3f38", "query": "framework.Logf(\"Service %s deleted\", testSvcName) }) <del> ginkgo.It(\"should delete a collection of services\", func() { </del> <ins> /* Release: v1.23 Testname: Service, deletes a collection of services Description: Create three services with the required labels and ports. It MUST locate three services in the test namespace. It MUST succeed at deleting a collection of services via a label selector. It MUST locate only one service after deleting the service collection. */ framework.ConformanceIt(\"should delete a collection of services\", func() { </ins> ns := f.Namespace.Name svcClient := f.ClientSet.CoreV1().Services(ns)", "positive_passages": [{"docid": "doc-en-kubernetes-5e1e446ffee113a0fecf68600791d8062befcc769908a1fdd16ec9abcfdd9c85", "text": "[X] Two weeks soak end date: Nov 18 According to this APIsnoop query, there are still a remaining Service endpoint which is untested. A service resource didn&rsquo;t support endpoint until was merged. Create a watch to track service events Create a service with a static label. Confirm via the watch that the service was created. Delete the service via the service with the dynamic client with . Confirm via the watch that the service was deleted. The above steps have been implemented in the follwing . This query shows all the endpoints hit within a short period of running the above e2e test If a test with these calls gets merged, test coverage will go up by 1 point This test is also created with the goal of conformance promotion. /sig testing /sig network /area conformance\n/triage accepted\nWaiting on 2 week soak before promoting the test to conformance /reopen\nReopened this issue. <detailsIn response to : Waiting on 2 week soak before promoting the test to conformance /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_106032", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f3b92121551ba3fdf7822de70b9c4114669295c0540f32d42d23f21b041f5df7", "query": "nodePortAddresses []string, ) (proxy.Provider, error) { // Create an ipv4 instance of the single-stack proxier <ins> nodePortAddresses4, nodePortAddresses6 := utilproxy.FilterIncorrectCIDRVersion(nodePortAddresses, false) </ins> ipv4Proxier, err := NewProxier(ipt[0], sysctl, exec, syncPeriod, minSyncPeriod, masqueradeAll, masqueradeBit, localDetectors[0], hostname, <del> nodeIP[0], recorder, healthzServer, nodePortAddresses) </del> <ins> nodeIP[0], recorder, healthzServer, nodePortAddresses4) </ins> if err != nil { return nil, fmt.Errorf(\"unable to create ipv4 proxier: %v\", err) } ipv6Proxier, err := NewProxier(ipt[1], sysctl, exec, syncPeriod, minSyncPeriod, masqueradeAll, masqueradeBit, localDetectors[1], hostname, <del> nodeIP[1], recorder, healthzServer, nodePortAddresses) </del> <ins> nodeIP[1], recorder, healthzServer, nodePortAddresses6) </ins> if err != nil { return nil, fmt.Errorf(\"unable to create ipv6 proxier: %v\", err) }", "positive_passages": [{"docid": "doc-en-kubernetes-10e0800334eabc101ba3e719bde6addc76496fd00734e09bb571fcc5b6be7d48", "text": "What happened: In a dual-stack cluster when specifying both ipv6 and ipv4 addresses in the entries are inserted in ipvs for the ipv6 nodeports but with an invalid ipv4 address; The example shows the ipv4 loopback address but any ipv4 address in will cause a faulty entry. What you expected to happen: No ipv4 entry shall be inserted for the ipv6 nodeport. How to reproduce it (as minimally and precisely as possible): Configure with both ipv4 and ipv6 addresses Bring up a dual-stack cluster with proxy-mode Create a service with ipFamily:IPv6 Do Anything else we need to know?: Proxy-mode=iptables seems to work. With no ipv4 entries are inserted for ipv6 nodeports. In it is recommended to use but doing so makes kube-proxy enter rules for address (in addition to \"127.0.0.1\"). While these entries cause no harm they can't be used and should not be there. These entries are created for both proxy-mode \"iptables\" and \"ipvs\". This should not be handled in this issue but in another (new) issue if needed. Example; Environment: Kubernetes version (use ):Cloud provider or hardware configuration: Kvm's on Ubuntu OS (e.g: ): xcluster Kernel (e.g. ):Install tools: \"from scratch\" Network plugin and version (if this is a network-related bug): calico/cni:v3.12.0 Others: /sig network\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/area ipvs /area ipv6\n/remove-triage unresolved /assign I take this myself if no one objects.\nThe ipv4 address is obviously a ipv4-converted ipv6 from .\nAccording to the code here (), we may need to filter the before passing it to .\nLooks that that's it. Please go ahead and make a PR, or I can do it if you prefer. I will help test the PR of course. Here are some review comments right away; Use v1.IPFamily as param to the filter function rather than The filter function seem usable and generic and may be placed in some \"util\" package, but leave it as-is and let the maintainers decide that.\nHi feel free to send a PR please, as you have took this already :) I'd like to help review it!\nThe \"addresses\" are really CIDRs which make the fix even simpler.", "commid": "kubernetes_issue_89923", "tokennum": 576}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f3bc6a11135c7caa85a55e6a1704bb47385debd91538599eb4d9b5700d7b08ba", "query": "\"k8s.io/apimachinery/pkg/runtime/schema\" \"k8s.io/apiserver/pkg/authentication/serviceaccount\" clientset \"k8s.io/client-go/kubernetes\" <ins> imageutils \"k8s.io/kubernetes/test/utils/image\" </ins> \"github.com/onsi/ginkgo\"", "positive_passages": [{"docid": "doc-en-kubernetes-d654f914f6cdd0bd3bce5db6eb3c4ebef631bd8d2558ac9d591cab12ba724061", "text": "What happened: e2e tests detect whether PSP is enabled based on presence of PSP API objects. An addon that proactively includes a PSP in a manifest can trigger that detection and enable PSP-specific e2e tests that should not be run. What you expected to happen: In addition to detecting presence of PSP objects, consider dry-run creating a pod and verifying the annotation indicating the selected PSP policy is , indicating the admission plugin is active. /sig auth /assign", "commid": "kubernetes_issue_91463", "tokennum": 109}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f3be04498e5fe5a582f8bf721da99303bd7f4ade9a2fd3c676c035723e144ba4", "query": "<ins> /* Copyright 2016 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package main import ( \"encoding/json\" \"flag\" \"fmt\" \"os\" \"path\" \"strconv\" \"strings\" \"time\" \"github.com/coreos/etcd/etcdserver\" pb \"github.com/coreos/etcd/etcdserver/etcdserverpb\" \"github.com/coreos/etcd/etcdserver/membership\" \"github.com/coreos/etcd/mvcc/backend\" \"github.com/coreos/etcd/mvcc/mvccpb\" \"github.com/coreos/etcd/pkg/pbutil\" \"github.com/coreos/etcd/pkg/types\" \"github.com/coreos/etcd/raft/raftpb\" \"github.com/coreos/etcd/snap\" \"github.com/coreos/etcd/store\" \"github.com/coreos/etcd/wal\" \"github.com/coreos/etcd/wal/walpb\" \"github.com/golang/glog\" ) const rollbackVersion = \"2.3.7\" var ( migrateDatadir = flag.String(\"data-dir\", \"\", \"Path to the data directory\") ttl            = flag.Duration(\"ttl\", time.Hour, \"TTL of event keys (default 1 hour)\") ) func main() { flag.Parse() if len(*migrateDatadir) == 0 { glog.Fatal(\"need to set '--data-dir'\") } dbpath := path.Join(*migrateDatadir, \"member\", \"snap\", \"db\") // etcd3 store backend. We will use it to parse v3 data files and extract information. be := backend.NewDefaultBackend(dbpath) tx := be.BatchTx() // etcd2 store backend. We will use v3 data to update this and then save snapshot to disk. st := store.New(etcdserver.StoreClusterPrefix, etcdserver.StoreKeysPrefix) expireTime := time.Now().Add(*ttl) tx.Lock() err := tx.UnsafeForEach([]byte(\"key\"), func(k, v []byte) error { kv := &mvccpb.KeyValue{} kv.Unmarshal(v) // This is compact key. if !strings.HasPrefix(string(kv.Key), \"/\") { return nil } ttlOpt := store.TTLOptionSet{} if kv.Lease != 0 { ttlOpt = store.TTLOptionSet{ExpireTime: expireTime} } if !isTombstone(k) { sk := path.Join(strings.Trim(etcdserver.StoreKeysPrefix, \"/\"), string(kv.Key)) _, err := st.Set(sk, false, string(kv.Value), ttlOpt) if err != nil { return err } } else { st.Delete(string(kv.Key), false, false) } return nil }) if err != nil { glog.Fatal(err) } tx.Unlock() if err := traverseAndDeleteEmptyDir(st, \"/\"); err != nil { glog.Fatal(err) } // rebuild cluster state. metadata, hardstate, oldSt, err := rebuild(*migrateDatadir) if err != nil { glog.Fatal(err) } // In the following, it's low level logic that saves metadata and data into v2 snapshot. backupPath := *migrateDatadir + \".rollback.backup\" if err := os.Rename(*migrateDatadir, backupPath); err != nil { glog.Fatal(err) } if err := os.MkdirAll(path.Join(*migrateDatadir, \"member\", \"snap\"), 0700); err != nil { glog.Fatal(err) } walDir := path.Join(*migrateDatadir, \"member\", \"wal\") w, err := wal.Create(walDir, metadata) if err != nil { glog.Fatal(err) } err = w.SaveSnapshot(walpb.Snapshot{Index: hardstate.Commit, Term: hardstate.Term}) if err != nil { glog.Fatal(err) } w.Close() event, err := oldSt.Get(etcdserver.StoreClusterPrefix, true, false) if err != nil { glog.Fatal(err) } // nodes (members info) for ConfState nodes := []uint64{} traverseMetadata(event.Node, func(n *store.NodeExtern) { if n.Key != etcdserver.StoreClusterPrefix { // update store metadata v := \"\" if !n.Dir { v = *n.Value } if n.Key == path.Join(etcdserver.StoreClusterPrefix, \"version\") { v = rollbackVersion } if _, err := st.Set(n.Key, n.Dir, v, store.TTLOptionSet{}); err != nil { glog.Fatal(err) } // update nodes fields := strings.Split(n.Key, \"/\") if len(fields) == 4 && fields[2] == \"members\" { nodeID, err := strconv.ParseUint(fields[3], 16, 64) if err != nil { glog.Fatalf(\"failed to parse member ID (%s): %v\", fields[3], err) } nodes = append(nodes, nodeID) } } }) data, err := st.Save() if err != nil { glog.Fatal(err) } raftSnap := raftpb.Snapshot{ Data: data, Metadata: raftpb.SnapshotMetadata{ Index: hardstate.Commit, Term:  hardstate.Term, ConfState: raftpb.ConfState{ Nodes: nodes, }, }, } snapshotter := snap.New(path.Join(*migrateDatadir, \"member\", \"snap\")) if err := snapshotter.SaveSnap(raftSnap); err != nil { glog.Fatal(err) } fmt.Println(\"Finished successfully\") } func traverseMetadata(head *store.NodeExtern, handleFunc func(*store.NodeExtern)) { q := []*store.NodeExtern{head} for len(q) > 0 { n := q[0] q = q[1:] handleFunc(n) for _, next := range n.Nodes { q = append(q, next) } } } const ( revBytesLen       = 8 + 1 + 8 markedRevBytesLen = revBytesLen + 1 markBytePosition  = markedRevBytesLen - 1 markTombstone byte = 't' ) func isTombstone(b []byte) bool { return len(b) == markedRevBytesLen && b[markBytePosition] == markTombstone } func traverseAndDeleteEmptyDir(st store.Store, dir string) error { e, err := st.Get(dir, true, false) if err != nil { return err } if len(e.Node.Nodes) == 0 { st.Delete(dir, true, true) return nil } for _, node := range e.Node.Nodes { if !node.Dir { glog.V(2).Infof(\"key: %s\", node.Key[len(etcdserver.StoreKeysPrefix):]) } else { err := traverseAndDeleteEmptyDir(st, node.Key) if err != nil { return err } } } return nil } func rebuild(datadir string) ([]byte, *raftpb.HardState, store.Store, error) { waldir := path.Join(datadir, \"member\", \"wal\") snapdir := path.Join(datadir, \"member\", \"snap\") ss := snap.New(snapdir) snapshot, err := ss.Load() if err != nil && err != snap.ErrNoSnapshot { return nil, nil, nil, err } var walsnap walpb.Snapshot if snapshot != nil { walsnap.Index, walsnap.Term = snapshot.Metadata.Index, snapshot.Metadata.Term } w, err := wal.OpenForRead(waldir, walsnap) if err != nil { return nil, nil, nil, err } defer w.Close() meta, hardstate, ents, err := w.ReadAll() if err != nil { return nil, nil, nil, err } st := store.New(etcdserver.StoreClusterPrefix, etcdserver.StoreKeysPrefix) if snapshot != nil { err := st.Recovery(snapshot.Data) if err != nil { return nil, nil, nil, err } } cluster := membership.NewCluster(\"\") cluster.SetStore(st) applier := etcdserver.NewApplierV2(st, cluster) for _, ent := range ents { if ent.Type == raftpb.EntryConfChange { var cc raftpb.ConfChange pbutil.MustUnmarshal(&cc, ent.Data) switch cc.Type { case raftpb.ConfChangeAddNode: m := new(membership.Member) if err := json.Unmarshal(cc.Context, m); err != nil { return nil, nil, nil, err } cluster.AddMember(m) case raftpb.ConfChangeRemoveNode: id := types.ID(cc.NodeID) cluster.RemoveMember(id) case raftpb.ConfChangeUpdateNode: m := new(membership.Member) if err := json.Unmarshal(cc.Context, m); err != nil { return nil, nil, nil, err } cluster.UpdateRaftAttributes(m.ID, m.RaftAttributes) } continue } var raftReq pb.InternalRaftRequest if !pbutil.MaybeUnmarshal(&raftReq, ent.Data) { // backward compatible var r pb.Request pbutil.MustUnmarshal(&r, ent.Data) applyRequest(&r, applier) } else { if raftReq.V2 != nil { req := raftReq.V2 applyRequest(req, applier) } } } return meta, &hardstate, st, nil } func toTTLOptions(r *pb.Request) store.TTLOptionSet { refresh, _ := pbutil.GetBool(r.Refresh) ttlOptions := store.TTLOptionSet{Refresh: refresh} if r.Expiration != 0 { ttlOptions.ExpireTime = time.Unix(0, r.Expiration) } return ttlOptions } func applyRequest(r *pb.Request, applyV2 etcdserver.ApplierV2) { toTTLOptions(r) switch r.Method { case \"PUT\": applyV2.Put(r) case \"DELETE\": applyV2.Delete(r) case \"POST\", \"QGET\", \"SYNC\": return default: glog.Fatal(\"unknown command\") } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-6208b2974deee3332ab4020708350835523c141c61d79e5104e4c7dba961daa5", "text": "ci-kubernetes-e2e-gce-device-plugin-gpu.Overall ci-kubernetes-e2e-gce-device-plugin-gpu.Pod kubetest.Up Intermittently since 02/23 No response No response /sig testing /sig release\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/cc /sig node BTW, would you help to confirm if this is a release cut blocker? We plan to release 1.30.0-alpha.3 on Tuesday 27th February 2024.\nIt passed! Maybe it was some infra issues?\nFailed again. /sig k8s-infra\nMany recreating of nodes in log.\nThis is caused by infra flaky.\nThe problem is\nThis job only runs one test and GPU instances are hard to find we don\u2019t need many of those instances for this job, can we please change this job to only use 2 workers?\n/cc\ntests failed in a recent run. It failed the first time. The Job failure now changed to test case failing today. It failed 4 times in a row.\n/assign\nI launched a test run, logged into the master node and took the kubeconfig and found the following: Relevant bit\nLink some related updates recently on this job.\nThe error above in is weird to me. It said No firmware image found . In successful run before, like (02-27), there are no such failure logs. failure in only kubelet log shows the pod crashed and restarted for many times. No pod log or containerd log.\nAfter , the CI is not always failing now and 4 in a row.\n/close\nClosing 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\n/reopen as keeps flaking\nReopened this issue. <detailsIn response to : /reopen as keeps flaking Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_123491", "tokennum": 511}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f3be04498e5fe5a582f8bf721da99303bd7f4ade9a2fd3c676c035723e144ba4", "query": "<ins> /* Copyright 2016 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package main import ( \"encoding/json\" \"flag\" \"fmt\" \"os\" \"path\" \"strconv\" \"strings\" \"time\" \"github.com/coreos/etcd/etcdserver\" pb \"github.com/coreos/etcd/etcdserver/etcdserverpb\" \"github.com/coreos/etcd/etcdserver/membership\" \"github.com/coreos/etcd/mvcc/backend\" \"github.com/coreos/etcd/mvcc/mvccpb\" \"github.com/coreos/etcd/pkg/pbutil\" \"github.com/coreos/etcd/pkg/types\" \"github.com/coreos/etcd/raft/raftpb\" \"github.com/coreos/etcd/snap\" \"github.com/coreos/etcd/store\" \"github.com/coreos/etcd/wal\" \"github.com/coreos/etcd/wal/walpb\" \"github.com/golang/glog\" ) const rollbackVersion = \"2.3.7\" var ( migrateDatadir = flag.String(\"data-dir\", \"\", \"Path to the data directory\") ttl            = flag.Duration(\"ttl\", time.Hour, \"TTL of event keys (default 1 hour)\") ) func main() { flag.Parse() if len(*migrateDatadir) == 0 { glog.Fatal(\"need to set '--data-dir'\") } dbpath := path.Join(*migrateDatadir, \"member\", \"snap\", \"db\") // etcd3 store backend. We will use it to parse v3 data files and extract information. be := backend.NewDefaultBackend(dbpath) tx := be.BatchTx() // etcd2 store backend. We will use v3 data to update this and then save snapshot to disk. st := store.New(etcdserver.StoreClusterPrefix, etcdserver.StoreKeysPrefix) expireTime := time.Now().Add(*ttl) tx.Lock() err := tx.UnsafeForEach([]byte(\"key\"), func(k, v []byte) error { kv := &mvccpb.KeyValue{} kv.Unmarshal(v) // This is compact key. if !strings.HasPrefix(string(kv.Key), \"/\") { return nil } ttlOpt := store.TTLOptionSet{} if kv.Lease != 0 { ttlOpt = store.TTLOptionSet{ExpireTime: expireTime} } if !isTombstone(k) { sk := path.Join(strings.Trim(etcdserver.StoreKeysPrefix, \"/\"), string(kv.Key)) _, err := st.Set(sk, false, string(kv.Value), ttlOpt) if err != nil { return err } } else { st.Delete(string(kv.Key), false, false) } return nil }) if err != nil { glog.Fatal(err) } tx.Unlock() if err := traverseAndDeleteEmptyDir(st, \"/\"); err != nil { glog.Fatal(err) } // rebuild cluster state. metadata, hardstate, oldSt, err := rebuild(*migrateDatadir) if err != nil { glog.Fatal(err) } // In the following, it's low level logic that saves metadata and data into v2 snapshot. backupPath := *migrateDatadir + \".rollback.backup\" if err := os.Rename(*migrateDatadir, backupPath); err != nil { glog.Fatal(err) } if err := os.MkdirAll(path.Join(*migrateDatadir, \"member\", \"snap\"), 0700); err != nil { glog.Fatal(err) } walDir := path.Join(*migrateDatadir, \"member\", \"wal\") w, err := wal.Create(walDir, metadata) if err != nil { glog.Fatal(err) } err = w.SaveSnapshot(walpb.Snapshot{Index: hardstate.Commit, Term: hardstate.Term}) if err != nil { glog.Fatal(err) } w.Close() event, err := oldSt.Get(etcdserver.StoreClusterPrefix, true, false) if err != nil { glog.Fatal(err) } // nodes (members info) for ConfState nodes := []uint64{} traverseMetadata(event.Node, func(n *store.NodeExtern) { if n.Key != etcdserver.StoreClusterPrefix { // update store metadata v := \"\" if !n.Dir { v = *n.Value } if n.Key == path.Join(etcdserver.StoreClusterPrefix, \"version\") { v = rollbackVersion } if _, err := st.Set(n.Key, n.Dir, v, store.TTLOptionSet{}); err != nil { glog.Fatal(err) } // update nodes fields := strings.Split(n.Key, \"/\") if len(fields) == 4 && fields[2] == \"members\" { nodeID, err := strconv.ParseUint(fields[3], 16, 64) if err != nil { glog.Fatalf(\"failed to parse member ID (%s): %v\", fields[3], err) } nodes = append(nodes, nodeID) } } }) data, err := st.Save() if err != nil { glog.Fatal(err) } raftSnap := raftpb.Snapshot{ Data: data, Metadata: raftpb.SnapshotMetadata{ Index: hardstate.Commit, Term:  hardstate.Term, ConfState: raftpb.ConfState{ Nodes: nodes, }, }, } snapshotter := snap.New(path.Join(*migrateDatadir, \"member\", \"snap\")) if err := snapshotter.SaveSnap(raftSnap); err != nil { glog.Fatal(err) } fmt.Println(\"Finished successfully\") } func traverseMetadata(head *store.NodeExtern, handleFunc func(*store.NodeExtern)) { q := []*store.NodeExtern{head} for len(q) > 0 { n := q[0] q = q[1:] handleFunc(n) for _, next := range n.Nodes { q = append(q, next) } } } const ( revBytesLen       = 8 + 1 + 8 markedRevBytesLen = revBytesLen + 1 markBytePosition  = markedRevBytesLen - 1 markTombstone byte = 't' ) func isTombstone(b []byte) bool { return len(b) == markedRevBytesLen && b[markBytePosition] == markTombstone } func traverseAndDeleteEmptyDir(st store.Store, dir string) error { e, err := st.Get(dir, true, false) if err != nil { return err } if len(e.Node.Nodes) == 0 { st.Delete(dir, true, true) return nil } for _, node := range e.Node.Nodes { if !node.Dir { glog.V(2).Infof(\"key: %s\", node.Key[len(etcdserver.StoreKeysPrefix):]) } else { err := traverseAndDeleteEmptyDir(st, node.Key) if err != nil { return err } } } return nil } func rebuild(datadir string) ([]byte, *raftpb.HardState, store.Store, error) { waldir := path.Join(datadir, \"member\", \"wal\") snapdir := path.Join(datadir, \"member\", \"snap\") ss := snap.New(snapdir) snapshot, err := ss.Load() if err != nil && err != snap.ErrNoSnapshot { return nil, nil, nil, err } var walsnap walpb.Snapshot if snapshot != nil { walsnap.Index, walsnap.Term = snapshot.Metadata.Index, snapshot.Metadata.Term } w, err := wal.OpenForRead(waldir, walsnap) if err != nil { return nil, nil, nil, err } defer w.Close() meta, hardstate, ents, err := w.ReadAll() if err != nil { return nil, nil, nil, err } st := store.New(etcdserver.StoreClusterPrefix, etcdserver.StoreKeysPrefix) if snapshot != nil { err := st.Recovery(snapshot.Data) if err != nil { return nil, nil, nil, err } } cluster := membership.NewCluster(\"\") cluster.SetStore(st) applier := etcdserver.NewApplierV2(st, cluster) for _, ent := range ents { if ent.Type == raftpb.EntryConfChange { var cc raftpb.ConfChange pbutil.MustUnmarshal(&cc, ent.Data) switch cc.Type { case raftpb.ConfChangeAddNode: m := new(membership.Member) if err := json.Unmarshal(cc.Context, m); err != nil { return nil, nil, nil, err } cluster.AddMember(m) case raftpb.ConfChangeRemoveNode: id := types.ID(cc.NodeID) cluster.RemoveMember(id) case raftpb.ConfChangeUpdateNode: m := new(membership.Member) if err := json.Unmarshal(cc.Context, m); err != nil { return nil, nil, nil, err } cluster.UpdateRaftAttributes(m.ID, m.RaftAttributes) } continue } var raftReq pb.InternalRaftRequest if !pbutil.MaybeUnmarshal(&raftReq, ent.Data) { // backward compatible var r pb.Request pbutil.MustUnmarshal(&r, ent.Data) applyRequest(&r, applier) } else { if raftReq.V2 != nil { req := raftReq.V2 applyRequest(req, applier) } } } return meta, &hardstate, st, nil } func toTTLOptions(r *pb.Request) store.TTLOptionSet { refresh, _ := pbutil.GetBool(r.Refresh) ttlOptions := store.TTLOptionSet{Refresh: refresh} if r.Expiration != 0 { ttlOptions.ExpireTime = time.Unix(0, r.Expiration) } return ttlOptions } func applyRequest(r *pb.Request, applyV2 etcdserver.ApplierV2) { toTTLOptions(r) switch r.Method { case \"PUT\": applyV2.Put(r) case \"DELETE\": applyV2.Delete(r) case \"POST\", \"QGET\", \"SYNC\": return default: glog.Fatal(\"unknown command\") } } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-93e6b458b8ba607e02020a8718331e5d8d90eb2c8daf949aa5e83a98cf741ed8", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThe problem is different with the failure after the revert. We(release signal team) plan to open an issue for the flake later. (Probably, we should open that one and then close on behalf of that new issue later.)\nFeel free to close it then. However, it failed 3 times out of last 4 runs. It's more a failure than a flake in my opinion. If doesn't help/ not appropriate, I'd suggest to revert installer and image changes\ncomment is clear about the root cause, we have a problem installing the drivers, can you redirect this issue if you think is a bug?\nAfter was merged, there are 6 failure in last 24 run. Tab stats: 8 of 10 (80.0%) recent columns passed (258 of 262 or 98.5% cells) The Flaky rate is lower.", "commid": "kubernetes_issue_123491", "tokennum": 202}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f3bf24a042ea25e0f025fae7f60e3e1df9cae0d766aba7c7faa9f76a4baf2982", "query": "import ( \"fmt\" <ins> \"reflect\" </ins> \"k8s.io/apimachinery/pkg/api/meta\" \"k8s.io/apimachinery/pkg/labels\" \"k8s.io/apimachinery/pkg/runtime/schema\" <del> serializer \"k8s.io/apimachinery/pkg/runtime/serializer\" </del> <ins> \"k8s.io/apimachinery/pkg/runtime/serializer\" </ins> \"k8s.io/client-go/rest\" \"k8s.io/client-go/util/flowcontrol\"", "positive_passages": [{"docid": "doc-en-kubernetes-c04a0817a9f8c0cfea921bee7f0710f81a15653683e102754b69999644e85b55", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: What you expected to happen: kube-controller-manager should not panic. How to reproduce it (as minimally and precisely as possible): Kubernetes 1.12.6, , and Anything else we need to know?: It's running and , and logs says: Don't see any notable errors in . Is that because it's running the old ? Basically, is expecting , but somehow it's getting which I assume Environment: Kubernetes version (use ): v1.12.6 Cloud provider or hardware configuration: AWS EC2 OS (e.g: ): Amazon Linux 2 Kernel (e.g. ): 4.14.109-99.92.amzn2.x86_64\nCould be related to , but this happens with all the patches from the issue /sig scalability /cc\n/sig autoscaling /assign can you triage please?\n/sig-remove scalabilty\n/sig remove scalability\n/sig scalability remove\n/remove-sig scalability\nAPI returned v1.Status instead of v1beta2.MetricValueList. We should check what is the type of the object\n/sig instrumention\n/assign\n/sig instrumentation\nseems promising. Is it missing anything?\nI've root-caused the issue. Explained here -\nYep, should address the issue.", "commid": "kubernetes_issue_80390", "tokennum": 343}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f3c119848d862fd6cb46dd39a04479a25c3a0be0fecd27bf80abfcbbbf175ae2", "query": "return err } if !mountPoint { <del> return fmt.Errorf(\"azureDisk - Not a mounting point for disk %s on %s\", diskName, dir) </del> <ins> glog.V(4).Infof(\"azureDisk - already mounted to target %s\", dir) return nil </ins> } if err := os.MkdirAll(dir, 0750); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-af5dea5ad6c50703324bee116a030e07ea1fcd8083467f9a4affa3fed2c086d0", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: There will be error when kubelet restarts on a agent if pod in that agent has an azure disk mounted, the error would be like following: azureDisk - No t a mounting point for disk andykubewin175-dynamic-pvc--92c7-11e7-b86b- on varlibkubeletpods-92c7-11e7-b86b-volumespvc--92c7-11 e7-b86b- What you expected to happen: pod could still works well even if kubelet restarts on the agent How to reproduce it (as minimally and precisely as possible): consider following scenario: A pod mounting an azure disk in a k8s agent The kubelet is restarted in that k8s agent The pod could not start up, it always reports error as following: 4d 1m 3065 kubelet, 14777acs9000 Warning FailedMount MountVolume.SetUp failed for volume \"pvc--92c7-11e7-b86b-\" : azureDisk - No t a mounting point for disk andykubewin175-dynamic-pvc--92c7-11e7-b86b- on varlibkubeletpods-92c7-11e7-b86b-volumespvc--92c7-11 e7-b86b- 4d 1m 3157 kubelet, 14777acs9000 Warning FailedMount Error syncing pod Anything else we need to know?: Environment: Kubernetes version (use ): 1.7, 1.8 Cloud provider or hardware configuration**: azure OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list .", "commid": "kubernetes_issue_52261", "tokennum": 514}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f3c119848d862fd6cb46dd39a04479a25c3a0be0fecd27bf80abfcbbbf175ae2", "query": "return err } if !mountPoint { <del> return fmt.Errorf(\"azureDisk - Not a mounting point for disk %s on %s\", diskName, dir) </del> <ins> glog.V(4).Infof(\"azureDisk - already mounted to target %s\", dir) return nil </ins> } if err := os.MkdirAll(dir, 0750); err != nil {", "positive_passages": [{"docid": "doc-en-kubernetes-3017dae552427d7697f9eef98172533a65ddf628962bc7801cfca27e66cdff46", "text": "The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig azure\n/assign andyzhangx", "commid": "kubernetes_issue_52261", "tokennum": 39}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f3cdc11ba3b216d511de3cab3c38eb8540579d747129dd07eab0824c789d783d", "query": "if len(q.nominatedPods.nominatedPods[\"node1\"]) != 2 { t.Errorf(\"Expected medPriorityPod and unschedulablePod to be still present in nomindatePods: %v\", q.nominatedPods.nominatedPods[\"node1\"]) } <del> if q.unschedulableQ.get(&highPriNominatedPod) != &highPriNominatedPod { </del> <ins> if getUnschedulablePod(q, &highPriNominatedPod) != &highPriNominatedPod { </ins> t.Errorf(\"Pod %v was not found in the unschedulableQ.\", highPriNominatedPod.Name) } }", "positive_passages": [{"docid": "doc-en-kubernetes-e059cd0647305d70a174ce6bffb9584a993a023526be428075760ddef27cc3b0", "text": "Which jobs are failing: pull-kubernetes-bazel-test Which test(s) are failing: bazel test //pkg/scheduler/internal/queue:godefaulttest Since when has it been failing: Testgrid link: Reason for failure: WARNING: DATA RACE Read at 0x00c000230db0 by goroutine 47: runtime.mapiterinit() +0x0 (PriorityQueue).flushUnschedulableQLeftover() +0x17a (PriorityQueue).flushUnschedulableQLeftover-fm() +0x41 () +0x61 () +0xce () +0x5a Previous write at 0x00c000230db0 by goroutine 45: runtime.mapassignfaststr() +0x0 (UnschedulablePodsMap).addOrUpdate() +0x30e () +0x601 testing.tRunner() +0x162 Goroutine 47 (running) created at: (PriorityQueue).run() +0x172 () +0xe0b () +0x50 () +0x5a5 testing.tRunner() +0x162 Goroutine 45 (running) created at: testing.(T).Run() +0x659 testing.runTests.func1() +0xa8 testing.tRunner() +0x162 testing.runTests() +0x4ee testing.(M).Run() +0x2ee () bazel-out/k8- +0x2fb Anything else we need to know: I'm very sorry about that. UnschedulablePodsMap is not thread-safe. In , lock will be acquired before operating UnschedulablePodsMap. But in , lock isn\u2018t be acquired. In the previous case, only a single thread runs so it's ok. But after add goroutine , there will be data race. So I need to acquire lock before operating UnschedulablePodsMap.\n/sig testing /sig scheduling", "commid": "kubernetes_issue_73021", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f3d3bf36a0e3d97d22209da99dcc300cd99a628ea831dcec76fea4e3a7cc3d50", "query": "return \"\", err } <del> return image.TagFromImage(pod.Spec.Containers[0].Image), nil </del> <ins> return convertImageTagMetadataToSemver(image.TagFromImage(pod.Spec.Containers[0].Image)), nil } // convertImageTagMetadataToSemver converts imagetag in the format of semver_metadata to semver+metadata func convertImageTagMetadataToSemver(tag string) string { // Container registries do not support `+` characters in tag names. This prevents imagetags from // correctly representing semantic versions which use the plus symbol to delimit build metadata. // Kubernetes uses the convention of using an underscore in image registries to preserve // build metadata information in imagetags. return strings.Replace(tag, \"_\", \"+\", 1) </ins> }", "positive_passages": [{"docid": "doc-en-kubernetes-1d9713caefc449b5fa12697f2f529990c13dff1a712a56404b9120eb41d78bc3", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --When attempting to upgrade kubernetes using kubeadm upgrade apply, kubeadm fails to parse an etcd imagetag containing build metadata in the form of as a valid semver. An example upgrade produces an error similar to: Note this will occur even if the etcd version is unchanged. The +` character. This pattern is used to support custom kubernetes images, for instance kube-apiserver:v1.20.4+patch.0 will be converted to imagetag v1.20.4_patch.0 when running make quick-release-images. Add the following to kubeadm- Install kubernetes. Then upgrade kubernetes with kubeadm upgrade apply. I have tested a fix for this issue and will PR shortly. Kubernetes version (use ): N/A Cloud provider or hardware configuration: N/A OS (e.g: ): N/A Kernel (e.g. ): N/A Install tools: kubeadm Network plugin and version (if this is a network-related bug): N/A Others: N/A\n/sig cluster-lifecycle\n/area kubeadm\n/triage accepted", "commid": "kubernetes_issue_100349", "tokennum": 312}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f3dfe3bbb20982c454bb6cb44b63075a1252dd5c764644ce47d62feb98b744f8", "query": "// In case of failure or too long waiting time, an error is returned. func waitForRCPodToDisappear(c *client.Client, ns, rcName, podName string) error { label := labels.SelectorFromSet(labels.Set(map[string]string{\"name\": rcName})) <del> return waitForPodToDisappear(c, ns, podName, label, 20*time.Second, 5*time.Minute) </del> <ins> // NodeController evicts pod after 5 minutes, so we need timeout greater than that. // Additionally, there can be non-zero grace period, so we are setting 10 minutes // to be on the safe size. return waitForPodToDisappear(c, ns, podName, label, 20*time.Second, 10*time.Minute) </ins> } // waitForService waits until the service appears (exist == true), or disappears (exist == false)", "positive_passages": [{"docid": "doc-en-kubernetes-f3af4e5ee08342f3d9a5775ee2c1466702ed34eb1665ac9c4b71bf76c8f54023", "text": "Nodes Network when a minion node becomes unreachable [replication controller] recreates pods scheduled on the unreachable minion node AND allows scheduling of pods on a minion after it rejoins the cluster(Failed 17 times in the last 30 runs. Stability: 43 %)Failed with 0 retries\nfor triage\nI'll look into this.\nI talked to about this and he had a pretty good guess in about two seconds about what the problem is. ReplicationController sync method does this: but DaemonSet controller doesn't. (I guess when DaemonSet was copy-pasted from ReplicationController, this was accidentally removed.) Pod reflector and syncer are running in separate goroutines, and if pod reflector doesn't run then syncer will think there are no pods on the node.\nTo be clear: this is about the test Controller Manager should not create/delete replicas across restart which is the one that is actually failing.\nI'm confused you're saying that this is about , but you're updating . I thought they are about two different tests...\nYes sorry, I put my comment in the wrong issue. Reassigning this one to you, and I'll copy my comment into the other one.\nFirst failure: We check if all namespace are deleted. If other tests failed to delete their namespace this test will fail. I'm going to delete this logic as we already check if we have successfully deleted our namespace. See also for some more details.\nSecond failure: We disable network by running the following command: I checked and it seems that it results in ing master to hang. I suspect that Kubelet hangs on updating node status and depending when it breaks the connection (by timeout) it will fit in test timeouts or not.\nWhat is the default timeout for connections using client libraries to apiserver? I'm checking the code, but can't find it.\nI'm not sure if we set one, but we should. I guess I would expect to see that in the config, w/ default set by this function: , Filip Grzadkowski wrote:\nSo: let's add a timeout, and revert .\nI think that adding a timeout and reverting are orthogonal. I we want to simulate network problems with node-master communication then using REJECT is better anyway. At the same time adding timeout makes sense for many other reasons.", "commid": "kubernetes_issue_14695", "tokennum": 521}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f3dfe3bbb20982c454bb6cb44b63075a1252dd5c764644ce47d62feb98b744f8", "query": "// In case of failure or too long waiting time, an error is returned. func waitForRCPodToDisappear(c *client.Client, ns, rcName, podName string) error { label := labels.SelectorFromSet(labels.Set(map[string]string{\"name\": rcName})) <del> return waitForPodToDisappear(c, ns, podName, label, 20*time.Second, 5*time.Minute) </del> <ins> // NodeController evicts pod after 5 minutes, so we need timeout greater than that. // Additionally, there can be non-zero grace period, so we are setting 10 minutes // to be on the safe size. return waitForPodToDisappear(c, ns, podName, label, 20*time.Second, 10*time.Minute) </ins> } // waitForService waits until the service appears (exist == true), or disappears (exist == false)", "positive_passages": [{"docid": "doc-en-kubernetes-171a96c8c8138970f18a9330482c8efd4960f1ea370d03cb243605d2473f3591", "text": "OK then, let's add a timeout and test both DROP and REJECT-- no sort of network problem should hang a component.\nI think it didn't hang. It just that the kubelet was retrying too slow and sometimes it fit test timeout, sometime it didn't.\nCould we reduce the timeout to make it always fit the test timeout? , Filip Grzadkowski\nI guess we can. I'll try tomorrow.\nIt seems we have a new type of failure: It seems that kubelet on a machine where network is blocked doesn't notice new pod. After reading logs I assume that kubelet doesn't notice that the watch is broken and doesn't try to relist everything. It notices new pod only after watch timeout.\nUgh, I hope we don't have to start sending watch heartbeats.\nIt seems that all recent failures are with the following error: which means the reason is here: - can you please take a look or delegate?\nI did some more debugging of it. I was looking into this failure: There is something strange happening here: run performTemporaryNetworkFailure: succesfully block the load from kubelet: the succesfully wait for node to become not ready: some time nodecontroller successfully removes the pod: replication controller creates a new pod: here is something I don't undertand - because of some reason, the test doesn't observe that the pod actually disappeared. - any thoughts on it?\nBTW - this is exactly the same situation in:\nOK - I think this is related to default 30s deletion grace period.\nYes - it seems that this is exactly the case. I will send out PR fixing this out for review.\nI'm reopening it for tracking. If there won't be any failures within next few days - I will move the test back from flaky and close this issue.\nThanks for fixing, .\nIt seems that the main issue is fixed. However, there was one failure in the last 30 runs: in which one pod simply didn't started (and it was \"preparation\" for the test, not the test itself).\nDuring next 2 days there was exactly one more failure of this test: it is exactly the same as the previous one. However, those are duplicates of So I'm going to move this test out of flaky suite.", "commid": "kubernetes_issue_14695", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f3e081db144073cd2830de316b49b8635aa0a9a0deb182e9c667846d0b11055d", "query": "if utilfeature.DefaultFeatureGate.Enabled(features.CSIDriverRegistry) { csiClient := host.GetKubeClient() if csiClient == nil { <del> return errors.New(\"unable to get Kubernetes client\") </del> <ins> klog.Warning(log(\"kubeclient not set, assuming standalone kubelet\")) } else { // Start informer for CSIDrivers. factory := csiapiinformer.NewSharedInformerFactory(csiClient, csiResyncPeriod) p.csiDriverInformer = factory.Storage().V1beta1().CSIDrivers() p.csiDriverLister = p.csiDriverInformer.Lister() go factory.Start(wait.NeverStop) </ins> } <del> // Start informer for CSIDrivers. factory := csiapiinformer.NewSharedInformerFactory(csiClient, csiResyncPeriod) p.csiDriverInformer = factory.Storage().V1beta1().CSIDrivers() p.csiDriverLister = p.csiDriverInformer.Lister() go factory.Start(wait.NeverStop) </del> } // Initializing the label management channels", "positive_passages": [{"docid": "doc-en-kubernetes-c443ff5d18f1d6c2d29d44384ec9cc1635dcc5ac37c91445fd7d9e71b7cfce65", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: Which test(s) are failing: Since when has it been failing: It has been consistently failing since 3/6, flaking a lot before that. Failure coincides with . Testgrid link: Reason for failure: cc /kind flake /kind failing-test /priority important-soon /milestone v1.14 /sig cluster-lifecycle\nsig gcp may be of help here /sig gcp\n/assign for routing from SCL side. These are google owned tests.\nLooking into this now. Any other googlers also doing so feel free to ping me :-)\nLooks like this bug is known with a fix in flight: cc\n/assign\nThanks ! Will keep an eye on this for 5 consistent passes, will reopen if there's a problem.\n/reopen Most gke jobs are able to create clusters now, however the serial jobs are still seeing failures\nReopened this issue. <detailsIn response to : /reopen Most gke jobs are able to create clusters now, however the serial jobs are still seeing failures 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\nNevermind, it's because the serial job with the fix is still running. I've verified that the cluster creation succeeds in the latest job. /close\nClosing this issue. <detailsIn response to : Nevermind, it's because the serial job with the fix is still running. I've verified that the cluster creation succeeds in the latest job. /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\n/area platform/gke <img width=\"1106\" alt=\"Screen Shot 2019-03-16 at 12 00 52 PM\" src=\"https://user-\"Think we're done here", "commid": "kubernetes_issue_75145", "tokennum": 435}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f40c4b05bbb966b01fca153ff47622806d26bb9cfb5286aa5f46463d669635ca", "query": "// EnsureDesiredReplicasInRange ensure the replicas is in a desired range func (rc *ResourceConsumer) EnsureDesiredReplicasInRange(ctx context.Context, minDesiredReplicas, maxDesiredReplicas int, duration time.Duration, hpaName string) { interval := 10 * time.Second <del> err := wait.PollUntilContextTimeout(ctx, interval, duration, true, func(ctx context.Context) (bool, error) { replicas := rc.GetReplicas(ctx) framework.Logf(\"expecting there to be in [%d, %d] replicas (are: %d)\", minDesiredReplicas, maxDesiredReplicas, replicas) as, err := rc.GetHpa(ctx, hpaName) if err != nil { framework.Logf(\"Error getting HPA: %s\", err) } else { framework.Logf(\"HPA status: %+v\", as.Status) } if replicas < minDesiredReplicas { return false, fmt.Errorf(\"number of replicas below target\") } else if replicas > maxDesiredReplicas { return false, fmt.Errorf(\"number of replicas above target\") } else { return false, nil // Expected number of replicas found. Continue polling until timeout. } }) // The call above always returns an error, but if it is timeout, it's OK (condition satisfied all the time). if wait.Interrupted(err) { framework.Logf(\"Number of replicas was stable over %v\", duration) return </del> <ins> desiredReplicasErr := framework.Gomega().Consistently(ctx, func(ctx context.Context) int { return rc.GetReplicas(ctx) }).WithTimeout(duration).WithPolling(interval).Should(gomega.And(gomega.BeNumerically(\">=\", minDesiredReplicas), gomega.BeNumerically(\"<=\", maxDesiredReplicas))) // dump HPA for debugging as, err := rc.GetHpa(ctx, hpaName) if err != nil { framework.Logf(\"Error getting HPA: %s\", err) } else { framework.Logf(\"HPA status: %+v\", as.Status) </ins> } <del> framework.ExpectNoErrorWithOffset(1, err) </del> <ins> framework.ExpectNoError(desiredReplicasErr) </ins> } // Pause stops background goroutines responsible for consuming resources.", "positive_passages": [{"docid": "doc-en-kubernetes-c9c1c743d3f3434b5b176b4daffd6034698e7589ba7079b19c7793ebc64267f8", "text": "Kubernetes e2e suite. Kubernetes e2e suite.[It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicationController Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods and verify decision stability [sig-autoscaling, Feature:HPA, Serial, Slow] Kubernetes e2e suite.[It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicationController Should scale from 5 pods to 3 pods and then from 3 pods to 1 pod and verify decision stability [sig-autoscaling, Feature:HPA, Serial, Slow] Kubernetes e2e suite.[It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with autoscaling disabled shouldn't scale down [sig-autoscaling, Feature:HPA, Serial, Slow] Kubernetes e2e suite.[It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with autoscaling disabled shouldn't scale up [sig-autoscaling, Feature:HPA, Serial, Slow] Kubernetes e2e suite.[It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with both scale up and down controls configured should keep recommendation within the range with stabilization window and pod limit rate [sig-autoscaling, Feature:HPA, Serial, Slow] Kubernetes e2e suite.", "commid": "kubernetes_issue_121860", "tokennum": 407}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f40c4b05bbb966b01fca153ff47622806d26bb9cfb5286aa5f46463d669635ca", "query": "// EnsureDesiredReplicasInRange ensure the replicas is in a desired range func (rc *ResourceConsumer) EnsureDesiredReplicasInRange(ctx context.Context, minDesiredReplicas, maxDesiredReplicas int, duration time.Duration, hpaName string) { interval := 10 * time.Second <del> err := wait.PollUntilContextTimeout(ctx, interval, duration, true, func(ctx context.Context) (bool, error) { replicas := rc.GetReplicas(ctx) framework.Logf(\"expecting there to be in [%d, %d] replicas (are: %d)\", minDesiredReplicas, maxDesiredReplicas, replicas) as, err := rc.GetHpa(ctx, hpaName) if err != nil { framework.Logf(\"Error getting HPA: %s\", err) } else { framework.Logf(\"HPA status: %+v\", as.Status) } if replicas < minDesiredReplicas { return false, fmt.Errorf(\"number of replicas below target\") } else if replicas > maxDesiredReplicas { return false, fmt.Errorf(\"number of replicas above target\") } else { return false, nil // Expected number of replicas found. Continue polling until timeout. } }) // The call above always returns an error, but if it is timeout, it's OK (condition satisfied all the time). if wait.Interrupted(err) { framework.Logf(\"Number of replicas was stable over %v\", duration) return </del> <ins> desiredReplicasErr := framework.Gomega().Consistently(ctx, func(ctx context.Context) int { return rc.GetReplicas(ctx) }).WithTimeout(duration).WithPolling(interval).Should(gomega.And(gomega.BeNumerically(\">=\", minDesiredReplicas), gomega.BeNumerically(\"<=\", maxDesiredReplicas))) // dump HPA for debugging as, err := rc.GetHpa(ctx, hpaName) if err != nil { framework.Logf(\"Error getting HPA: %s\", err) } else { framework.Logf(\"HPA status: %+v\", as.Status) </ins> } <del> framework.ExpectNoErrorWithOffset(1, err) </del> <ins> framework.ExpectNoError(desiredReplicasErr) </ins> } // Pause stops background goroutines responsible for consuming resources.", "positive_passages": [{"docid": "doc-en-kubernetes-50a764361af76177e3b0fd7754c28175d0d0117b957f7afce14b1a8f0955f9e1", "text": "[It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with both scale up and down controls configured should keep recommendation within the range over two stabilization windows [sig-autoscaling, Feature:HPA, Serial, Slow] 11/3/2023 <*fmt.wrapError | 0xc000812080: client rate limiter Wait returned an error: context deadline exceeded { msg: \"client rate limiter Wait returned an error: context deadline exceeded\", err: <context.deadlineExceededError{}, } looks similiar to /sig autoscaling /sig windows\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_121860", "tokennum": 242}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f4208f2d0d0f428317e9af55e70bb3b85775210c45c328a4e20644d53b48fee1", "query": "ginkgo.It(\"should always delete fast (ALL of 100 namespaces in 150 seconds) [Feature:ComprehensiveNamespaceDraining]\", func() { extinguish(f, 100, 0, 150) }) <ins> ginkgo.It(\"should patch a Namespace\", func() { ginkgo.By(\"creating a Namespace\") namespaceName := \"nspatchtest-\" + string(uuid.NewUUID()) ns, err := f.CreateNamespace(namespaceName, nil) framework.ExpectNoError(err, \"failed creating Namespace\") namespaceName = ns.ObjectMeta.Name ginkgo.By(\"patching the Namespace\") nspatch, err := json.Marshal(map[string]interface{}{ \"metadata\": map[string]interface{}{ \"labels\": map[string]string{\"testLabel\": \"testValue\"}, }, }) framework.ExpectNoError(err, \"failed to marshal JSON patch data\") _, err = f.ClientSet.CoreV1().Namespaces().Patch(namespaceName, types.StrategicMergePatchType, []byte(nspatch)) framework.ExpectNoError(err, \"failed to patch Namespace\") ginkgo.By(\"get the Namespace and ensuring it has the label\") namespace, err := f.ClientSet.CoreV1().Namespaces().Get(namespaceName, metav1.GetOptions{}) framework.ExpectNoError(err, \"failed to get Namespace\") framework.ExpectEqual(namespace.ObjectMeta.Labels[\"testLabel\"], \"testValue\", \"namespace not patched\") }) </ins> })", "positive_passages": [{"docid": "doc-en-kubernetes-1e3d5f814d3d1cd0ae92f2f9adc262569d0e3418b95dbcb250b25bdb3821fc75", "text": "This issue proposes the writing of a new test for the API endpoint with the intention of promoting it to Conformance. This issue contains a very masic mock test in order to start the conversation about what a good e2e test would look like for this endpoint. The code below is verified to be hitting the intended endpoint, show as per the queries in APIsnoop's live view of the cluster's audit logs. According to this query, there is only one API endpoint which is for Namespace that isn't being covered. We selected patchCoreV1Namespace to write a test for. Dependencies: The mock test: If a test with these calls is build and merged, conformance will go up by 1 endpoint.\n/sig testing /sig architecture /area conformance", "commid": "kubernetes_issue_86051", "tokennum": 169}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f43535527db482bed8c7b18f0962bc61d93e11b2f14465a4f8f80b8b839bcda0", "query": "var map_EnvVarSource = map[string]string{ \"\":                 \"EnvVarSource represents a source for the value of an EnvVar.\", <del> \"fieldRef\":         \"Selects a field of the pod: supports metadata.name, metadata.namespace, metadata.labels, metadata.annotations, spec.nodeName, spec.serviceAccountName, status.hostIP, status.podIP, status.podIPs.\", </del> <ins> \"fieldRef\":         \"Selects a field of the pod: supports metadata.name, metadata.namespace, `metadata.labels['<KEY>']`, `metadata.annotations['<KEY>']`, spec.nodeName, spec.serviceAccountName, status.hostIP, status.podIP, status.podIPs.\", </ins> \"resourceFieldRef\": \"Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, limits.ephemeral-storage, requests.cpu, requests.memory and requests.ephemeral-storage) are currently supported.\", \"configMapKeyRef\":  \"Selects a key of a ConfigMap.\", \"secretKeyRef\":     \"Selects a key of a secret in the pod's namespace\",", "positive_passages": [{"docid": "doc-en-kubernetes-5018642be16ab87784521fef6d356d625aa306ba1fff6efc2d4048e42ef1a94c", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: When I tried to create a pod with env variables referencing to annotations: What you expected to happen: Should Proceed. As in It stated is a valid option How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): v1.18.2 Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig docs\nThe API docs need to be updated to indicate the correct supported values. See for correct values\nYou are a lifesaver. Thank you!\n/assign I can try to update the api documentation", "commid": "kubernetes_issue_91165", "tokennum": 215}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f46e339ea0ca663a58d8e41e07ebeb2212c9bcb0d18ca233ba4f4144261b88c1", "query": "safeIpset := newSafeIpset(ipset) <ins> nodePortAddresses4, nodePortAddresses6 := utilproxy.FilterIncorrectCIDRVersion(nodePortAddresses, false) </ins> // Create an ipv4 instance of the single-stack proxier ipv4Proxier, err := NewProxier(ipt[0], ipvs, safeIpset, sysctl, exec, syncPeriod, minSyncPeriod, filterCIDRs(false, excludeCIDRs), strictARP, tcpTimeout, tcpFinTimeout, udpTimeout, masqueradeAll, masqueradeBit, localDetectors[0], hostname, nodeIP[0], <del> recorder, healthzServer, scheduler, nodePortAddresses, kernelHandler) </del> <ins> recorder, healthzServer, scheduler, nodePortAddresses4, kernelHandler) </ins> if err != nil { return nil, fmt.Errorf(\"unable to create ipv4 proxier: %v\", err) }", "positive_passages": [{"docid": "doc-en-kubernetes-10e0800334eabc101ba3e719bde6addc76496fd00734e09bb571fcc5b6be7d48", "text": "What happened: In a dual-stack cluster when specifying both ipv6 and ipv4 addresses in the entries are inserted in ipvs for the ipv6 nodeports but with an invalid ipv4 address; The example shows the ipv4 loopback address but any ipv4 address in will cause a faulty entry. What you expected to happen: No ipv4 entry shall be inserted for the ipv6 nodeport. How to reproduce it (as minimally and precisely as possible): Configure with both ipv4 and ipv6 addresses Bring up a dual-stack cluster with proxy-mode Create a service with ipFamily:IPv6 Do Anything else we need to know?: Proxy-mode=iptables seems to work. With no ipv4 entries are inserted for ipv6 nodeports. In it is recommended to use but doing so makes kube-proxy enter rules for address (in addition to \"127.0.0.1\"). While these entries cause no harm they can't be used and should not be there. These entries are created for both proxy-mode \"iptables\" and \"ipvs\". This should not be handled in this issue but in another (new) issue if needed. Example; Environment: Kubernetes version (use ):Cloud provider or hardware configuration: Kvm's on Ubuntu OS (e.g: ): xcluster Kernel (e.g. ):Install tools: \"from scratch\" Network plugin and version (if this is a network-related bug): calico/cni:v3.12.0 Others: /sig network\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d\n/area ipvs /area ipv6\n/remove-triage unresolved /assign I take this myself if no one objects.\nThe ipv4 address is obviously a ipv4-converted ipv6 from .\nAccording to the code here (), we may need to filter the before passing it to .\nLooks that that's it. Please go ahead and make a PR, or I can do it if you prefer. I will help test the PR of course. Here are some review comments right away; Use v1.IPFamily as param to the filter function rather than The filter function seem usable and generic and may be placed in some \"util\" package, but leave it as-is and let the maintainers decide that.\nHi feel free to send a PR please, as you have took this already :) I'd like to help review it!\nThe \"addresses\" are really CIDRs which make the fix even simpler.", "commid": "kubernetes_issue_89923", "tokennum": 576}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f493a427d21a18310599379d48f941ded64099911dadabd815089ef0b5a6545a", "query": "// Not local instance, get instanceID from Azure ARM API. if !isLocalInstance { <del> return az.vmSet.GetInstanceIDByNodeName(nodeName) </del> <ins> if az.vmSet != nil { return az.vmSet.GetInstanceIDByNodeName(nodeName) } // vmSet == nil indicates credentials are not provided. return \"\", fmt.Errorf(\"no credentials provided for Azure cloud provider\") </ins> } // Get resource group name.", "positive_passages": [{"docid": "doc-en-kubernetes-effe9bff1df2586252b385cbf4a7cacd04cb77f4739ff9c987e63818f9dc1c82", "text": "Currently there is no way to run without any identity (be it service principal or E/MSI). In reality code running on a worker node can use via - and only via - without the need to access ARM. Here is the proposed change a new mode authN = this mode, is basically telling the cloud provider to work any identity, this means only IMDS calls is allowed. This mode can be detected from if no SPN set and both MSI settings are set to . to use a config map within the cluster. This config map can be loaded on the cluster statically. or created - if not existent - in that then only is used in The net new result of the above is users bootstrapping clusters can configure the worker node to use without any identity on said worker nodes.\n/sig azure These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by \u200d\nIn-tree AzureDisk volume plugin is also depending on Azure credential to fetch lun id. we should figure out how to solve it without credential\nfetch disk lun id is also a dependency in kubelet code now, after my investigation, it could be removed on Linux node, while it cannot be removed on Windows node, need to change the k/k upstream code, there is a discussion on going here: , let' wait for the discussion result.\nFor Linux: 1- use IMDS my understanding is new api versions will have the disk/lun pairs. 2- don't use arm for the return of is the second parameter passed to . For Windows: I don't understand the dep on ARM for this. The above still apply, we just need to find a way to encode the value as ut return from that allow us to find the disk by on a windows machine. might be a good source for this. Ideally speaking. The value should be the same. But i will leave it for you to decide.\ncould be a good idea since currently it's a LUN num returned by Attach() and then it could be changed to the windows disk num, I will make the code change on v1.15 later, thanks for discussion.\nUpdate: PR would remove the VM API calls when getting the LUN number for AzureDisk.", "commid": "kubernetes_issue_77309", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f4949ced9af0b45f1bfa8099a45bec008466ab0e4baaa62ffdf55566faa1ed5e", "query": "--bind-address=\"${API_HOST}\"  --insecure-port=\"${API_PORT}\"  --etcd-servers=\"http://${ETCD_HOST}:${ETCD_PORT}\"  <ins> --etcd-prefix=\"${ETCD_PREFIX}\"  </ins> --runtime-config=\"${RUNTIME_CONFIG}\"  --cert-dir=\"${TMPDIR:-/tmp/}\"  --service-cluster-ip-range=\"10.0.0.0/24\" ", "positive_passages": [{"docid": "doc-en-kubernetes-74ce4fea7378dc634ccb83a22893b6255fa243ed3e0b4f0e57320154ecc66caf", "text": "removed this test. We need to continue testing this. This wasn't about testing upgrades, the prefix has nothing to do with upgrades. It's just there so people can share etcd. We maybe don't need to double everything but we do need to make sure that keeps working.\nTo be honest - I think that what we was testing before didn't give us completely any information. We didn't testing what information we are storing in etcd and where. That said, if we had a hardcoded prefix somewhere in our code, we wouldn't discover it at all, and those tests would still be passing. We should have a test that is directly checking etcd contents. I think it should be possible to write a simple unit test for it. Will try to put something together next week.", "commid": "kubernetes_issue_26489", "tokennum": 167}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f4a18ee30d26c34111d883fdada694d537c6d354e6e720ea9c8cbc7e4ea2943a", "query": "}, \"securityContext\": { \"$ref\": \"#/definitions/io.k8s.api.core.v1.SecurityContext\", <del> \"description\": \"Security options the pod should run with. More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/\" </del> <ins> \"description\": \"SecurityContext defines the security options the container should be run with. If set, the fields of SecurityContext override the equivalent fields of PodSecurityContext. More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/\" </ins> }, \"startupProbe\": { \"$ref\": \"#/definitions/io.k8s.api.core.v1.Probe\",", "positive_passages": [{"docid": "doc-en-kubernetes-2eefef1a83ddd783604f0989f7bcbb86ee11f3e15f09ced1fa06f0ad1ee322e6", "text": "What happened: states that Container.SecurityContext applies to a Pod, which can be misleading since we already have PodSecurityContext. What you expected to happen: Documentation states that it applies to container How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment:\n/sig api-machinery /kind documentation\n/cc\nIssues 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\nNot stale.\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten\nIssues 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\n/remove-lifecycle rotten\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close\nClosing 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", "commid": "kubernetes_issue_90634", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f4c6e72e64583bd7773bda6d6f03f203e8d5be167ee47b74b4fda7b7b913bf5b", "query": ") const ( <del> validTmpl    = \"image: {{ .ImageRepository }}/pause-{{ .Arch }}:3.0\" validTmplOut = \"image: gcr.io/google_containers/pause-amd64:3.0\" doNothing    = \"image: gcr.io/google_containers/pause-amd64:3.0\" </del> <ins> validTmpl    = \"image: {{ .ImageRepository }}/pause-{{ .Arch }}:3.1\" validTmplOut = \"image: gcr.io/google_containers/pause-amd64:3.1\" doNothing    = \"image: gcr.io/google_containers/pause-amd64:3.1\" </ins> invalidTmpl1 = \"{{ .baz }/d}\" invalidTmpl2 = \"{{ !foobar }}\" )", "positive_passages": [{"docid": "doc-en-kubernetes-a834f77ddd825b3d04a660aa7c11d0734893e4dcde6e0d4a7399e3b3daf56428", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: What happened: the pause-amd64:3.0 image on has an empty schema2 manifest, which prevents is from being pulled by proxy/caches which only support V2 registries. What you expected to happen: Being able to pull ` using a V2 manifest compatible client. Anything else we need to know?: The proxy/cahce is requesting this\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nAfter talking with , he mentionned the following\nAFAIK, does not support well. After inspecting the image, you can find is still using manifest v1.\n/cc FYI\nIm not sure which exact version x sch\u00e9ma X is needed. What I know is that we can download through the proxy/cache all other Kubernetes kube-system images, only the pause image is giving us trouble. Therefore, I would say that having the image available using the same format as the other kube-system images would be the request here.\nYeah, we haven't updated the pause image in a while, since it doesn't really ever change. I'm not sure whether rebuilding + pushing over the existing tag is safe, or if we should bump to or something. thoughts?\nIf we do rebuilding/updating the image, that would help and a bunch of similar issues.\nit's better/save to go with new tag\nI didn't realize there were changes to the pause binary that were never actually deployed. It seems like we should probably just do that (and bump the tag).\nthat sounds great. Any idea when the existing 3.0 tag could be pushed again?\nWe shouldn't push over the 3.0 tag; we should push a 3.1 or 4.0 tag instead. I'm not sure who owns the pause container who should drive this. Maybe sig-node and/or\nIt seems like it should be sig-node. I'll look into it.\nThe new container has been built, can you test with\nIts working! thanks! I was able to pull it through our artifactory proxy , Lee Verberne <:\nexcellent, thanks for checking. /assign", "commid": "kubernetes_issue_56253", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f4c6e72e64583bd7773bda6d6f03f203e8d5be167ee47b74b4fda7b7b913bf5b", "query": ") const ( <del> validTmpl    = \"image: {{ .ImageRepository }}/pause-{{ .Arch }}:3.0\" validTmplOut = \"image: gcr.io/google_containers/pause-amd64:3.0\" doNothing    = \"image: gcr.io/google_containers/pause-amd64:3.0\" </del> <ins> validTmpl    = \"image: {{ .ImageRepository }}/pause-{{ .Arch }}:3.1\" validTmplOut = \"image: gcr.io/google_containers/pause-amd64:3.1\" doNothing    = \"image: gcr.io/google_containers/pause-amd64:3.1\" </ins> invalidTmpl1 = \"{{ .baz }/d}\" invalidTmpl2 = \"{{ !foobar }}\" )", "positive_passages": [{"docid": "doc-en-kubernetes-7628cd26f0dafa992a4ea43a6c68b9bcdbf056fca43ee32b40ab60cef4154c17", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: pause does not reap zombie processes using the default pause container provided by What you expected to happen: should include the up to date pause code to reap zombie processes when using docker = 1.13.1 found here How to reproduce it (as minimally and precisely as possible): a.out will leave a zombie process that is not cleaned up Anything else we need to know?: Building the pause container from master solves this issue Related: Environment: Kubernetes version (use ): 1.7.0+ Cloud provider or hardware configuration**: N/A OS (e.g. from /etc/os-release): CentOS 7 Kernel (e.g. ): 4.10.13+ Install tools: Others: docker = 1.13.1\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\ni get a simliar problem when i run crond service in pod container, every day it makes some [anacron] zombie progresses UID PID PPID C STIME TTY TIME CMD root 1 0 0 Nov14 ? 00:00:00 /pause root 7 0 0 Nov14 ? 00:00:00 /usr/local/bin/dumb-init /usr/lo root 13 7 0 Nov14 ? 00:00:00 nginx: master process /usr/local nobody 21 13 0 Nov14 ? 00:00:01 nginx: worker process nobody 22 13 0 Nov14 ? 00:00:07 nginx: worker process nobody 23 13 0 Nov14 ? 00:00:07 nginx: worker process nobody 24 13 0 Nov14 ? 00:00:05 nginx: worker process root 77 1 0 Nov14 ? 00:00:00 [anacron] root 1 0 00:01 ? 00:00:00 [anacron] <defunctroot 1 0 01:01 ? 00:00:00 [anacron] <defunctroot 1 0 02:01 ?", "commid": "kubernetes_issue_50865", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f4c6e72e64583bd7773bda6d6f03f203e8d5be167ee47b74b4fda7b7b913bf5b", "query": ") const ( <del> validTmpl    = \"image: {{ .ImageRepository }}/pause-{{ .Arch }}:3.0\" validTmplOut = \"image: gcr.io/google_containers/pause-amd64:3.0\" doNothing    = \"image: gcr.io/google_containers/pause-amd64:3.0\" </del> <ins> validTmpl    = \"image: {{ .ImageRepository }}/pause-{{ .Arch }}:3.1\" validTmplOut = \"image: gcr.io/google_containers/pause-amd64:3.1\" doNothing    = \"image: gcr.io/google_containers/pause-amd64:3.1\" </ins> invalidTmpl1 = \"{{ .baz }/d}\" invalidTmpl2 = \"{{ !foobar }}\" )", "positive_passages": [{"docid": "doc-en-kubernetes-6179feaaee46a15cd909bb088c82657b9b59fba8efdee1296995076588512032", "text": "00:00:00 [anacron] <defunctroot 1 0 03:01 ? 00:00:00 [anacron] <defunctroot 0 0 11:49 ? 00:00:00 /bin/bash root 0 1 19:15 ? 00:00:00 /bin/bash root 0 19:15 ? 00:00:00 ps -ef !\nDo we know why this was never resolved / was never deployed?\nI just fought through this issue with a rabbitmq helm chart. I had to custom build a pause container from master to fix it. The rabbitmq helm chart uses for its liveness checks. It's a thin wrapper around a call to the rabbitmq-server daemon, which is not PID 1 (/pause is PID 1). The rabbitmq-server process forks some children to do the work and then they exit. Since the pause-amd64:3.0 is not reaping, those processes stick around as zombies. The liveness check runs every 5 seconds. After about 4 hours, there are about 27K zombies and the node begins failing to launch new containers because it's starved for resources. The pause container built from current master fixes that behavior, no zombies at all in the container.\nThe plan is to build a new version of pause-amd64 and then update the image referenced by Kubernetes. This means the default image will change in the next Kubernetes release. We can make the new image available once the freeze lifts and we can merge .\nLooks like this made it into 1.10", "commid": "kubernetes_issue_50865", "tokennum": 336}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f4c971f79683015692d9acc8d1693406940f24dd83472ee0467b3e460bad9586", "query": "<del> apiVersion: v1 kind: ServiceAccount metadata: name: elasticsearch </del>", "positive_passages": [{"docid": "doc-en-kubernetes-5fef938b0452d0f6b58e576cd11f17813fb6d6b970f83a7868d905b7784a5e39", "text": "Presently, the elasticsearch example Kubernetes configurations target elasticsearch v1.7.1, which is quite old. As of this writing, the latest elasticsearch release is v5.6.2, with many deployment changes since then. Could the elasticsearch examples be updated to target the v5 series of elasticsearch? See for a more up to date reference configuration.\ncc\nhey it's been a long while since I last contributed to the docs. i can do it soon but i need pointers on how to properly do it.\nhey, so we need to update the stuff under examples/elasticsearch/ *&repos=kubernetes So basically update the images, yaml files etc and test that everything works (and submit a PR)\n/sig testing\nAh, so there's no documentation updates anymore. OK I'll take care of it, assign it to me.\nIssues 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\nGitHub didn't allow me to assign the following users: me. Note that only and repo collaborators can be assigned. <detailsIn response to : /assign me 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\n/assign pires\n/remove-lifecycle stale\nit seems that the example moved to I am now reading that repo guidelines and will update this there. I'll also open a PR that cleans this folder in the current repo and closes this issue.", "commid": "kubernetes_issue_53142", "tokennum": 387}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f4f1567d15f1f09f67c42502cdaaec4d43af12ac0d92f3c4ab2abfc38e30cd73", "query": "return } <del> RemoveCleanupAction(f.cleanupHandle) </del> // This should not happen. Given ClientSet is a public field a test must have updated it! // Error out early before any API calls during cleanup. if f.ClientSet == nil {", "positive_passages": [{"docid": "doc-en-kubernetes-2e8b5198754cc6270240a247dfa503fa4a3eeae2d5481e425503db2c2c68474d", "text": "Here is a list of TODOs that could be fixed for Ginkgo migration from v1 to v2. [x] Lost the validation on the SIGDescribe: [x] Ginkgo V2 currently cannot get the number of specs that will run in , this might be fixed in the Ginkgo's minor release of V2 in the future. [x] <delGinkgo dry-run mode has dropped the test spec in V2 (), consider to switch back to use to generate test spec when the feature is ready in . </del--- This has been fixed in Ginkgo 2.1.4 [x] <delMigrate all the custom reporter in , should be lightweight and not sure where those custom reporters are used. </delFixed here: [x] Replace all the camel case flags to kebab case flags, e.g. to . [x] <delRemove the legacy e2e test binary's parameter and in 1.28, those parameters were used to manage report, this is no longer needed for Ginkgo v2. </delno longer needed. [x] upgrade vendor when is migrated to ginkgo v2, this will help to remove the dependency of - [x] <delrevisit to explore the possibility to cover the test in Ginkgo V2. </delfixed by [x] remove the workaround introduced in Ginkgo V1 ( is not called after hitting ^c): partially addressed by: , some cleanup needed for each sig before removing the hook entirely. I think has the pr to fix this entirely, but I cannot get the link for that, mark it as resolved. : [x] New work item (?): capture only a single output text output stream () in JUnit (this issue was resolved along with another one in ) [ ] Due to the junit format change, some tool which use to grab \"value\" directly cannot get the failure reason as what it does in v1. [x] Test failures are missing information since GinkgoV2 migration [ ] is clustering stack traces, not failure text () Address those leftovers if there is any update from Ginkgo in the future. see the relevant link on the each of the issues.", "commid": "kubernetes_issue_109744", "tokennum": 483}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f4f1567d15f1f09f67c42502cdaaec4d43af12ac0d92f3c4ab2abfc38e30cd73", "query": "return } <del> RemoveCleanupAction(f.cleanupHandle) </del> // This should not happen. Given ClientSet is a public field a test must have updated it! // Error out early before any API calls during cleanup. if f.ClientSet == nil {", "positive_passages": [{"docid": "doc-en-kubernetes-c4753cc2146447a07d108ff02ffe6d67b2be2a6ba7adffaf5026d0a94c1c787a", "text": "No response_ <details</details<detailsall </details<details</details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig testing\n/cc\n/cc\nhello! I would like to work on this issues\nI think we cannot do anything now except the last two, and those two should be based on top of the:\nI would like to work on task 5 of this issue\nno problem, pls wait for an while until that PR got merged, then you can create a pr to fix those deprecated parameters.\nRegarding : searching for points out the places where the workaround is used and needs to be replaced once is solved.\nI just noticed this comment in\nseems like is not used in k/k, but in other sigs.\nhmm... I just grepped the test code, will push a pr to fix this.\n/open\n/re-open\nokay, this is not resolved actually, but I have no way to re-open it.\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n~ it seems that some more jobs needs to be adapted to not use parallel~ [repo][0]=kubernetes/test-infra~ ~ACTION REQUIRED: Ginkgo V2 doesn't accept go test's flags to parallelize Ginkgo specs, please switch to use or instead.~ Sorry for the noise, the flag is passed to kubetest, and it correctly translate it to , it is not the issue here\nnp, thanks for the update!\nNew work item (?): capture only a single output text output stream () in JUnit.\nupdated the issue, haven't got a chance to take a close look at the item though.\nThis should be resolved by \"open stdout\" now should only appear if a test intentionally records SpecReports.\nmark it as resolved.\nis this complete now?", "commid": "kubernetes_issue_109744", "tokennum": 519}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f4f1567d15f1f09f67c42502cdaaec4d43af12ac0d92f3c4ab2abfc38e30cd73", "query": "return } <del> RemoveCleanupAction(f.cleanupHandle) </del> // This should not happen. Given ClientSet is a public field a test must have updated it! // Error out early before any API calls during cleanup. if f.ClientSet == nil {", "positive_passages": [{"docid": "doc-en-kubernetes-138d08f1aeca8e81cbf8aa639b51baa29b1653208e0d897ccfc4810c9421dc3e", "text": ", Only two of them left, I need to follow this one, here is the issue for this one opened in the Ginkgo: I think this should be fixed in the third party tools instead of Kubernetes, if we agree with that, we can mark it as completed as well. For the first one, I will continue to follow until there is a update from Ginkgo's side, for the later one, there is no consensus yet IIUC, we can open a separate issue for that, I am gonna to close this one since there is no much thing we can do now. /close\nWe agreed to fix the tool, but had no issue open for it. I just created one:\nAnother issue for", "commid": "kubernetes_issue_109744", "tokennum": 149}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f50c2191cb28957e7af69b36d252738c37ecc815d22d31c17dccf984188a4064", "query": "} } <del> func newDeployment(deploymentName string, replicas int, podLabels map[string]string, imageName string, image string) *extensions.Deployment { </del> <ins> func newDeployment(deploymentName string, replicas int, podLabels map[string]string, imageName string, image string, strategyType extensions.DeploymentStrategyType) *extensions.Deployment { </ins> return &extensions.Deployment{ ObjectMeta: api.ObjectMeta{ Name: deploymentName, }, Spec: extensions.DeploymentSpec{ <del> Replicas:       replicas, Selector:       podLabels, </del> <ins> Replicas: replicas, Selector: podLabels, Strategy: extensions.DeploymentStrategy{ Type: strategyType, }, </ins> UniqueLabelKey: extensions.DefaultDeploymentUniqueLabelKey, Template: api.PodTemplateSpec{ ObjectMeta: api.ObjectMeta{", "positive_passages": [{"docid": "doc-en-kubernetes-ceb20554e653f6657baad1bbb36c40e66d8a76887956e3c674b77febc82d4455", "text": "There's some practical limit on the number of concurrent access tokens that can be used in a Kubernetes cluster before it begins to spend all of its time in the authn stack verifying them. Absent fixes to it was < 500; with the fixes linked there it's still not infinitely scalable-- I still hit (what I believe to be) with ~ 5k unique tokens @ ~700QPS. This request is to this dimension an official name & definition, and list it with others, e.g. here: it it have a useful value (I think it should be 10k) /kind bug /sig scalability\n/cc\noh and 4. add tests which verify it is as high as believed.\ncc since projected tokens will increase the number of unique tokens\n/sig auth\nLRUs are not good at scaling and sharding has some major pitfalls as pointed out. I would suggest that we try to drop the LRU cache for successful authentication results in the token cache. The main benefit of using an LRU here is bound cache size. Entries in the token cache have a fast expiration independent of the LRU policy. The records probably take up O(2kb) (guesstimate) of memory. Given that these are successful attempts with presumably valid tokens, I don't think we are getting any benefit from the LRU. If we don't have a constraint on fixed cache size, we can back the token cache with a sync.Map and run a single background goroutine to periodically walk the map and remove expired entries. This would fix the problematic locking and eviction due to nonuniform distribution of tokens over shards. The failure cache is less important and we don't cache failures by default. If we consider this the \"slowpath\", we can probably leave it as. If that's not good enough, we have a couple options (with various tradeoffs) to improve it.\nIf off by default is not enough, more reasoning why the failed cache is not super useful: it might help with an accidental DoS but it doesn't prevent anything actively malicious DoS. I think we can focus our improvements on the success cache.\n/assign He is already working on adding an explicit test for it.\nhas taken it over and is actively working on this. Unfortunately, I cannot assign this issue to him as he's not a k8s member yet\nIt's not closed - all testes must be submitted and appropriate documentation must be\nThanks everyone!!", "commid": "kubernetes_issue_83375", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f55c0256574318aa178b0dae1548fdc61e2a308d3fb7ed09f76dbcb9ebf1e6ba", "query": "package logs import ( <ins> \"bufio\" </ins> \"bytes\" \"context\" <ins> \"fmt\" \"io\" \"io/ioutil\" </ins> \"os\" \"testing\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-1611cacb700fc7bde4bed341ff7dc392aeb6c35e6c0f63ce6a10b84981e8d04a", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Docker has a hardcoded 16K limit on log line length, which splits lines longer than that into multiple messages in the log file. in , however, doesn't account for this when is set to and prints the timestamp in front of every entry in the log file instead of every logical line. This leads to random timestamps appearing in the middle of log lines, potentially breaking the applications that parse these logs. What you expected to happen: inserts timestamps once per logical line, so original log data is preserved. Alternatively, allow API to request the logs in a sane format like JSON, which would allow merging the lines back and combining them with the timestamps more intelligently on the application side. How to reproduce it (as minimally and precisely as possible): Create : apiVersion: v1 kind: Pod metadata: name: log-lines spec: containers: name: main image: busybox command: ['sh', '-c', 'while sleep 1; do echo -n ; for i in $(seq 1 ); do echo -n A; done; echo ; done'] Start the pod with Fetch the logs with , or using the API () Observe random timestamps inserted in the middle of the log lines. Environment: Kubernetes version (use ):\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI will work on it. /sig cli /remove-sig node\nThe logs are being corrupted by the API endpoint in kubelet, so shouldn't it be in scope of SIG node?\nThe log is not corrupted by k8s. The same log could be got using \"docker container logs -t CONTAINERID\" I think you should post your requirement to Docker.", "commid": "kubernetes_issue_77603", "tokennum": 465}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f55c0256574318aa178b0dae1548fdc61e2a308d3fb7ed09f76dbcb9ebf1e6ba", "query": "package logs import ( <ins> \"bufio\" </ins> \"bytes\" \"context\" <ins> \"fmt\" \"io\" \"io/ioutil\" </ins> \"os\" \"testing\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-495f248c0af4a1a8db07569505db46eac9f11be4907de183bc6923cd7882b142", "text": "Please refer following code Line 50 ~ 52 if config.Timestamps { logLine = append([]byte(msg.Timestamp.Format(jsonmessage.RFC3339NanoFixed)+\" \"), logLine...) }\nkubelet doesn't rely on Docker when reading logs, it reads the files itself (see the code linked in the issue). I don't think Docker would change the forced line splitting (see for example), so this should be fixed in Kubernetes.\nYour are right and kubelet read log file from host such as /var/log/pods/pods/NAMESPACEPOD-NAMExxx/....(JSON format) I will post a PR for it. /remove-sig cli /sig node\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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 .", "commid": "kubernetes_issue_77603", "tokennum": 539}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f55c0256574318aa178b0dae1548fdc61e2a308d3fb7ed09f76dbcb9ebf1e6ba", "query": "package logs import ( <ins> \"bufio\" </ins> \"bytes\" \"context\" <ins> \"fmt\" \"io\" \"io/ioutil\" </ins> \"os\" \"testing\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-2f614c9ad06da31fe9313a5b2eaea6d6901d55cba8508cf5ebe57105d301c4f6", "text": "Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\nStale 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\nI saw the attempt fixing this but it was scary (echo this comment: ). I suggested a way it may be improved. Also the proposed fix didn't introduce any e2e tests to validate that runtime behavior is not changed and runtimes keep the no-newline-on-splitted-log logic. are you or anybody on this thread are still interested to work on this? Please re-open if so. Meanwhile closing this ahead of bot doing it because the inactivity. /close\nClosing this issue. <detailsIn response to : I saw the attempt fixing this but it was scary (echo this comment: ). I suggested a way it may be improved. Also the proposed fix didn't introduce any e2e tests to validate that runtime behavior is not changed and runtimes keep the no-newline-on-splitted-log logic. Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_77603", "tokennum": 493}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f55c0256574318aa178b0dae1548fdc61e2a308d3fb7ed09f76dbcb9ebf1e6ba", "query": "package logs import ( <ins> \"bufio\" </ins> \"bytes\" \"context\" <ins> \"fmt\" \"io\" \"io/ioutil\" </ins> \"os\" \"testing\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-2e8714433462894a36e35ec9c24fb7c5a56d0558d2953a09bb86920b184c167e", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nYou can't reopen an issue/PR unless you authored it or you are a collaborator. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/remove-lifecycle rotten /reopen will fix it.\nReopened this issue. <detailsIn response to : /remove-lifecycle rotten /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/triage accepted\nThe Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.", "commid": "kubernetes_issue_77603", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f55c0256574318aa178b0dae1548fdc61e2a308d3fb7ed09f76dbcb9ebf1e6ba", "query": "package logs import ( <ins> \"bufio\" </ins> \"bytes\" \"context\" <ins> \"fmt\" \"io\" \"io/ioutil\" </ins> \"os\" \"testing\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-422d52914e9725e7355cb5e937e13c24e15f273f63951d92fe52d86a167487cb", "text": "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]:\nThe 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]:\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_77603", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f55c0256574318aa178b0dae1548fdc61e2a308d3fb7ed09f76dbcb9ebf1e6ba", "query": "package logs import ( <ins> \"bufio\" </ins> \"bytes\" \"context\" <ins> \"fmt\" \"io\" \"io/ioutil\" </ins> \"os\" \"testing\" \"time\"", "positive_passages": [{"docid": "doc-en-kubernetes-0e28d298340708e57a780633dba41fa2a744d19c9ab3d061a118f6b1e6c3d902", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI received a bug report about this issue. The root cause is that the buffer reads up to a new line. If the line is greater than 4096 bytes and '--timestamps' is turrned on the kubelet will write the timestamp and the partial log line. We will need to refactor the ReadLogs function to allow for a partial line read.", "commid": "kubernetes_issue_77603", "tokennum": 104}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f55ece34f732a75829cae4337808636e142cbf8f0ff161de11b35719866d5672", "query": "proberDurationLabels := metrics.Labels{ \"probe_type\": w.probeType.String(), \"container\":  w.container.Name, <del> \"pod\":        podName, </del> <ins> \"pod\":        w.pod.Name, </ins> \"namespace\":  w.pod.Namespace, }", "positive_passages": [{"docid": "doc-en-kubernetes-8720ed8a574bdce7c104bd3a62cc93935fad36eef53bf2f2ff98186bbe4abc40", "text": "The metric used to report acutal pod in the label , but now I see the podname prefix only. The full pod name in the label, so I can trace the metric to the failing pod. Check raw api and verify the actual pod name with uids. <details</detailsAzure AKS <details</detailsNo response No response No response_\n/sig node\n/triage accepted /priority important-soon /cc As discussed this is a change in functionaloty that wasn't highlighted in release notes. Need to decide on what do do with it. I understand it's a change of functionality. what is the side effect of this for you? Does the label without last part not informational enough?\nI've been using the metric in my custom grafana dashboard that shows CPU, RAM, IO usage of pods with graph of increases in probes. If the apps are stable, the probe graph looks steadily. I can see if some irregularities in system metrics are influencing probes of respective pod. Also, if readiness probe is failing, the pod is removed from service, but is not restarted so I must have knowledge of pods with failing readiness probes. I attach the screenshot of my graph. ! So I'd welcome the possibility to pair the probes with exact pod and thank you for looking into it.\nare we thinking that this resulted in an undesirable change? Spologies for being a bit late to reply, I'm returning from a brief paternity leave staycation.\nThis issue is labeled with but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release. You can: Confirm that this issue is still relevant with (org members only) Deprioritize it with or Close this issue with For more details on the triage process, see /remove-triage accepted\nWell this is awkward... I still believe the actual behavior does not respect the intended idea...\nThis issue makes it hard to link probe metrics with right pods. The value of pod label in and are also inconsistent with how it is used in other kubelet metrics, see: vs Definitely a bug, regression since 1.25.\nI can't get anyone to look at the fix/revert: you may have better luck\n/milestone v1.28\ndiscussion in\nYou've pushed it through, congrats!", "commid": "kubernetes_issue_115766", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f5c914240d396374c1aa353d5ae00433613de616d82a2945b1c3942b2f5b5eb8", "query": "service Node { // NodePrepareResources prepares several ResourceClaims // for use on the node. If an error is returned, the <del> // response is ignored. Failures for individidual claims </del> <ins> // response is ignored. Failures for individual claims </ins> // can be reported inside NodePrepareResourcesResponse. rpc NodePrepareResources (NodePrepareResourcesRequest) returns (NodePrepareResourcesResponse) {}", "positive_passages": [{"docid": "doc-en-kubernetes-e8eec0a3f7a81297ed919db6952e73e9801661fbfe386a524b19b8189beefe88", "text": "When ResourceClaimParameters or ResourceClassParameters fail validation in resource driver during PodSchedulingContext sync loop, the error is visible only in the events of the PodSchedulingContext. The error should be visible on the object that fails validation as well, ResourceClaim or ResourceClass respectively. Creating ResourceClaim with unsupported parameters' values or unsupported No response <details</details<details</details<details</details<details</details<details</details<details</details\n/assign\n/sig node\n/triage accepted\nKEP:", "commid": "kubernetes_issue_121063", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f5dce306954e9e0e50aef74fac640713a9cc69cf0fb563dc4d1e0a0978b93253", "query": "var _ = Describe(\"Shell\", func() { defer GinkgoRecover() <del> // A number of scripts only work on gce if testContext.Provider != \"gce\" && testContext.Provider != \"gke\" { By(fmt.Sprintf(\"Skipping Shell test, which is only supported for provider gce and gke (not %s)\", testContext.Provider)) return } </del> // Slurp up all the tests in hack/e2e-suite bashE2ERoot := filepath.Join(root, \"hack/e2e-suite\") files, err := ioutil.ReadDir(bashE2ERoot)", "positive_passages": [{"docid": "doc-en-kubernetes-5702d542be386cac9e4333778515fd94620fcdb52c66d8dfc11487da78971dda", "text": "I noticed while running e2e tests locally that some tests were apparently being incorrectly skipped: I checked, and this is also true for our Jenkins runs. Currently it looks like and have this bug, though only the former actually skips the test, I think. The issue appears to be that the code inside the top-level in these files is being run before the testContext struct is filled out (and before is even called), and so testContext.Provider is empty. I'm not immediately sure what the proper fix is; I'm also worried that there might be other things broken by the fact that these blocks are called before initialization is complete. We also probably investigate if there is a better way to mark these tests as skipped; right now, there's no indication in the test report (, Jenkins test report, etc) that these tests were skipped.\nI merged and which tried to disable these tests for non-{gke,gce} but apparently didn't follow-up and verify that they were still running on our platforms. /cc\nSeems easy enough to fix. I'll have a PR out to fix this before Monday.", "commid": "kubernetes_issue_7008", "tokennum": 242}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f62a1f397a8d719414d5127bed707330442add96089b4acb5d16d48275fd1b9e", "query": "klog.ErrorS(err, \"Unable to connect to device plugin client with socket path\", \"path\", c.socket) return err } <ins> c.mutex.Lock() </ins> c.grpc = conn c.client = client <ins> c.mutex.Unlock() </ins> return c.handler.PluginConnected(c.resource, c) }", "positive_passages": [{"docid": "doc-en-kubernetes-5bc96dc4d12a3dcdc2937e744d86eb7f421f613963225d2302a19e261319d9fc", "text": "Seen in and in No hits on stack strace nothing evident on the git history of the test itself, but it seems , so most probable something in the device manager has changed? /sig node /kind flake\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\n/cc as this flakes a lot in", "commid": "kubernetes_issue_121451", "tokennum": 142}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f64a5aa235920f09a7fc87037349e8454b3a0191abba92d8659256a423c4ebd1", "query": "\"Required Drop Capabilities:s*<none>\", \"Allowed Capabilities:s*<none>\", \"Allowed Volume Types:s*<none>\", <ins> \"Allowed Unsafe Sysctls:s*kernel.*,net.ipv4.ip_local_port_range\", \"Forbidden Sysctls:s*net.ipv4.ip_default_ttl\", </ins> \"Allow Host Network:s*false\", \"Allow Host Ports:s*<none>\", \"Allow Host PID:s*false\",", "positive_passages": [{"docid": "doc-en-kubernetes-1c37f3b13ef66319b53623e24b4fece0550cb85e7e62ca9b694924c6c433e0c8", "text": "/kind bug What happened: does not show the description for the new field in What you expected to happen: should describe the new field. How to reproduce it (as minimally and precisely as possible): Environment: Kubernetes version (use ): master\n/sig auth\nGitHub didn't allow me to assign the following users: fanzhangio. Note that only and repo collaborators can be assigned. <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\nIf nobody has started yet, I wanna to pick it up.\nwas working on it AFAIR.\nIndeed. if you don't mind, I'd take over.", "commid": "kubernetes_issue_65181", "tokennum": 165}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f657a8cf5ec84653406e5b5341ac48a37aac2d5c9658a2d50139551f941e349f", "query": "assert.Equal(t, test.expectStderr, stderrBuf.String()) } } <ins> func TestReadLogsLimitsWithTimestamps(t *testing.T) { logLineFmt := \"2022-10-29T16:10:22.592603036-05:00 stdout P %vn\" logLineNewLine := \"2022-10-29T16:10:22.592603036-05:00 stdout F n\" tmpfile, err := ioutil.TempFile(\"\", \"log.*.txt\") assert.NoError(t, err) count := 10000 for i := 0; i < count; i++ { tmpfile.WriteString(fmt.Sprintf(logLineFmt, i)) } tmpfile.WriteString(logLineNewLine) for i := 0; i < count; i++ { tmpfile.WriteString(fmt.Sprintf(logLineFmt, i)) } tmpfile.WriteString(logLineNewLine) // two lines are in the buffer defer os.Remove(tmpfile.Name()) // clean up assert.NoError(t, err) tmpfile.Close() var buf bytes.Buffer w := io.MultiWriter(&buf) err = ReadLogs(context.Background(), tmpfile.Name(), \"\", &LogOptions{tail: -1, bytes: -1, timestamp: true}, nil, w, w) assert.NoError(t, err) lineCount := 0 scanner := bufio.NewScanner(bytes.NewReader(buf.Bytes())) for scanner.Scan() { lineCount++ // Split the line ts, logline, _ := bytes.Cut(scanner.Bytes(), []byte(\" \")) // Verification //   1. The timestamp should exist //   2. The last item in the log should be 9999 _, err = time.Parse(time.RFC3339, string(ts)) assert.NoError(t, err, \"timestamp not found\") assert.Equal(t, true, bytes.HasSuffix(logline, []byte(\"9999\")), \"is the complete log found\") } assert.Equal(t, 2, lineCount, \"should have two lines\") } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-1611cacb700fc7bde4bed341ff7dc392aeb6c35e6c0f63ce6a10b84981e8d04a", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: Docker has a hardcoded 16K limit on log line length, which splits lines longer than that into multiple messages in the log file. in , however, doesn't account for this when is set to and prints the timestamp in front of every entry in the log file instead of every logical line. This leads to random timestamps appearing in the middle of log lines, potentially breaking the applications that parse these logs. What you expected to happen: inserts timestamps once per logical line, so original log data is preserved. Alternatively, allow API to request the logs in a sane format like JSON, which would allow merging the lines back and combining them with the timestamps more intelligently on the application side. How to reproduce it (as minimally and precisely as possible): Create : apiVersion: v1 kind: Pod metadata: name: log-lines spec: containers: name: main image: busybox command: ['sh', '-c', 'while sleep 1; do echo -n ; for i in $(seq 1 ); do echo -n A; done; echo ; done'] Start the pod with Fetch the logs with , or using the API () Observe random timestamps inserted in the middle of the log lines. Environment: Kubernetes version (use ):\nReiterating the mentions to trigger a notification: <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI will work on it. /sig cli /remove-sig node\nThe logs are being corrupted by the API endpoint in kubelet, so shouldn't it be in scope of SIG node?\nThe log is not corrupted by k8s. The same log could be got using \"docker container logs -t CONTAINERID\" I think you should post your requirement to Docker.", "commid": "kubernetes_issue_77603", "tokennum": 465}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f657a8cf5ec84653406e5b5341ac48a37aac2d5c9658a2d50139551f941e349f", "query": "assert.Equal(t, test.expectStderr, stderrBuf.String()) } } <ins> func TestReadLogsLimitsWithTimestamps(t *testing.T) { logLineFmt := \"2022-10-29T16:10:22.592603036-05:00 stdout P %vn\" logLineNewLine := \"2022-10-29T16:10:22.592603036-05:00 stdout F n\" tmpfile, err := ioutil.TempFile(\"\", \"log.*.txt\") assert.NoError(t, err) count := 10000 for i := 0; i < count; i++ { tmpfile.WriteString(fmt.Sprintf(logLineFmt, i)) } tmpfile.WriteString(logLineNewLine) for i := 0; i < count; i++ { tmpfile.WriteString(fmt.Sprintf(logLineFmt, i)) } tmpfile.WriteString(logLineNewLine) // two lines are in the buffer defer os.Remove(tmpfile.Name()) // clean up assert.NoError(t, err) tmpfile.Close() var buf bytes.Buffer w := io.MultiWriter(&buf) err = ReadLogs(context.Background(), tmpfile.Name(), \"\", &LogOptions{tail: -1, bytes: -1, timestamp: true}, nil, w, w) assert.NoError(t, err) lineCount := 0 scanner := bufio.NewScanner(bytes.NewReader(buf.Bytes())) for scanner.Scan() { lineCount++ // Split the line ts, logline, _ := bytes.Cut(scanner.Bytes(), []byte(\" \")) // Verification //   1. The timestamp should exist //   2. The last item in the log should be 9999 _, err = time.Parse(time.RFC3339, string(ts)) assert.NoError(t, err, \"timestamp not found\") assert.Equal(t, true, bytes.HasSuffix(logline, []byte(\"9999\")), \"is the complete log found\") } assert.Equal(t, 2, lineCount, \"should have two lines\") } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-495f248c0af4a1a8db07569505db46eac9f11be4907de183bc6923cd7882b142", "text": "Please refer following code Line 50 ~ 52 if config.Timestamps { logLine = append([]byte(msg.Timestamp.Format(jsonmessage.RFC3339NanoFixed)+\" \"), logLine...) }\nkubelet doesn't rely on Docker when reading logs, it reads the files itself (see the code linked in the issue). I don't think Docker would change the forced line splitting (see for example), so this should be fixed in Kubernetes.\nYour are right and kubelet read log file from host such as /var/log/pods/pods/NAMESPACEPOD-NAMExxx/....(JSON format) I will post a PR for it. /remove-sig cli /sig node\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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 .", "commid": "kubernetes_issue_77603", "tokennum": 539}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f657a8cf5ec84653406e5b5341ac48a37aac2d5c9658a2d50139551f941e349f", "query": "assert.Equal(t, test.expectStderr, stderrBuf.String()) } } <ins> func TestReadLogsLimitsWithTimestamps(t *testing.T) { logLineFmt := \"2022-10-29T16:10:22.592603036-05:00 stdout P %vn\" logLineNewLine := \"2022-10-29T16:10:22.592603036-05:00 stdout F n\" tmpfile, err := ioutil.TempFile(\"\", \"log.*.txt\") assert.NoError(t, err) count := 10000 for i := 0; i < count; i++ { tmpfile.WriteString(fmt.Sprintf(logLineFmt, i)) } tmpfile.WriteString(logLineNewLine) for i := 0; i < count; i++ { tmpfile.WriteString(fmt.Sprintf(logLineFmt, i)) } tmpfile.WriteString(logLineNewLine) // two lines are in the buffer defer os.Remove(tmpfile.Name()) // clean up assert.NoError(t, err) tmpfile.Close() var buf bytes.Buffer w := io.MultiWriter(&buf) err = ReadLogs(context.Background(), tmpfile.Name(), \"\", &LogOptions{tail: -1, bytes: -1, timestamp: true}, nil, w, w) assert.NoError(t, err) lineCount := 0 scanner := bufio.NewScanner(bytes.NewReader(buf.Bytes())) for scanner.Scan() { lineCount++ // Split the line ts, logline, _ := bytes.Cut(scanner.Bytes(), []byte(\" \")) // Verification //   1. The timestamp should exist //   2. The last item in the log should be 9999 _, err = time.Parse(time.RFC3339, string(ts)) assert.NoError(t, err, \"timestamp not found\") assert.Equal(t, true, bytes.HasSuffix(logline, []byte(\"9999\")), \"is the complete log found\") } assert.Equal(t, 2, lineCount, \"should have two lines\") } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-2f614c9ad06da31fe9313a5b2eaea6d6901d55cba8508cf5ebe57105d301c4f6", "text": "Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\n/remove-lifecycle stale\nIssues 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\nStale 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\nI saw the attempt fixing this but it was scary (echo this comment: ). I suggested a way it may be improved. Also the proposed fix didn't introduce any e2e tests to validate that runtime behavior is not changed and runtimes keep the no-newline-on-splitted-log logic. are you or anybody on this thread are still interested to work on this? Please re-open if so. Meanwhile closing this ahead of bot doing it because the inactivity. /close\nClosing this issue. <detailsIn response to : I saw the attempt fixing this but it was scary (echo this comment: ). I suggested a way it may be improved. Also the proposed fix didn't introduce any e2e tests to validate that runtime behavior is not changed and runtimes keep the no-newline-on-splitted-log logic. Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_77603", "tokennum": 493}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f657a8cf5ec84653406e5b5341ac48a37aac2d5c9658a2d50139551f941e349f", "query": "assert.Equal(t, test.expectStderr, stderrBuf.String()) } } <ins> func TestReadLogsLimitsWithTimestamps(t *testing.T) { logLineFmt := \"2022-10-29T16:10:22.592603036-05:00 stdout P %vn\" logLineNewLine := \"2022-10-29T16:10:22.592603036-05:00 stdout F n\" tmpfile, err := ioutil.TempFile(\"\", \"log.*.txt\") assert.NoError(t, err) count := 10000 for i := 0; i < count; i++ { tmpfile.WriteString(fmt.Sprintf(logLineFmt, i)) } tmpfile.WriteString(logLineNewLine) for i := 0; i < count; i++ { tmpfile.WriteString(fmt.Sprintf(logLineFmt, i)) } tmpfile.WriteString(logLineNewLine) // two lines are in the buffer defer os.Remove(tmpfile.Name()) // clean up assert.NoError(t, err) tmpfile.Close() var buf bytes.Buffer w := io.MultiWriter(&buf) err = ReadLogs(context.Background(), tmpfile.Name(), \"\", &LogOptions{tail: -1, bytes: -1, timestamp: true}, nil, w, w) assert.NoError(t, err) lineCount := 0 scanner := bufio.NewScanner(bytes.NewReader(buf.Bytes())) for scanner.Scan() { lineCount++ // Split the line ts, logline, _ := bytes.Cut(scanner.Bytes(), []byte(\" \")) // Verification //   1. The timestamp should exist //   2. The last item in the log should be 9999 _, err = time.Parse(time.RFC3339, string(ts)) assert.NoError(t, err, \"timestamp not found\") assert.Equal(t, true, bytes.HasSuffix(logline, []byte(\"9999\")), \"is the complete log found\") } assert.Equal(t, 2, lineCount, \"should have two lines\") } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-2e8714433462894a36e35ec9c24fb7c5a56d0558d2953a09bb86920b184c167e", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nYou can't reopen an issue/PR unless you authored it or you are a collaborator. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/remove-lifecycle rotten /reopen will fix it.\nReopened this issue. <detailsIn response to : /remove-lifecycle rotten /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/triage accepted\nThe Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.", "commid": "kubernetes_issue_77603", "tokennum": 477}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f657a8cf5ec84653406e5b5341ac48a37aac2d5c9658a2d50139551f941e349f", "query": "assert.Equal(t, test.expectStderr, stderrBuf.String()) } } <ins> func TestReadLogsLimitsWithTimestamps(t *testing.T) { logLineFmt := \"2022-10-29T16:10:22.592603036-05:00 stdout P %vn\" logLineNewLine := \"2022-10-29T16:10:22.592603036-05:00 stdout F n\" tmpfile, err := ioutil.TempFile(\"\", \"log.*.txt\") assert.NoError(t, err) count := 10000 for i := 0; i < count; i++ { tmpfile.WriteString(fmt.Sprintf(logLineFmt, i)) } tmpfile.WriteString(logLineNewLine) for i := 0; i < count; i++ { tmpfile.WriteString(fmt.Sprintf(logLineFmt, i)) } tmpfile.WriteString(logLineNewLine) // two lines are in the buffer defer os.Remove(tmpfile.Name()) // clean up assert.NoError(t, err) tmpfile.Close() var buf bytes.Buffer w := io.MultiWriter(&buf) err = ReadLogs(context.Background(), tmpfile.Name(), \"\", &LogOptions{tail: -1, bytes: -1, timestamp: true}, nil, w, w) assert.NoError(t, err) lineCount := 0 scanner := bufio.NewScanner(bytes.NewReader(buf.Bytes())) for scanner.Scan() { lineCount++ // Split the line ts, logline, _ := bytes.Cut(scanner.Bytes(), []byte(\" \")) // Verification //   1. The timestamp should exist //   2. The last item in the log should be 9999 _, err = time.Parse(time.RFC3339, string(ts)) assert.NoError(t, err, \"timestamp not found\") assert.Equal(t, true, bytes.HasSuffix(logline, []byte(\"9999\")), \"is the complete log found\") } assert.Equal(t, 2, lineCount, \"should have two lines\") } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-422d52914e9725e7355cb5e937e13c24e15f273f63951d92fe52d86a167487cb", "text": "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]:\nThe 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]:\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available .", "commid": "kubernetes_issue_77603", "tokennum": 512}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f657a8cf5ec84653406e5b5341ac48a37aac2d5c9658a2d50139551f941e349f", "query": "assert.Equal(t, test.expectStderr, stderrBuf.String()) } } <ins> func TestReadLogsLimitsWithTimestamps(t *testing.T) { logLineFmt := \"2022-10-29T16:10:22.592603036-05:00 stdout P %vn\" logLineNewLine := \"2022-10-29T16:10:22.592603036-05:00 stdout F n\" tmpfile, err := ioutil.TempFile(\"\", \"log.*.txt\") assert.NoError(t, err) count := 10000 for i := 0; i < count; i++ { tmpfile.WriteString(fmt.Sprintf(logLineFmt, i)) } tmpfile.WriteString(logLineNewLine) for i := 0; i < count; i++ { tmpfile.WriteString(fmt.Sprintf(logLineFmt, i)) } tmpfile.WriteString(logLineNewLine) // two lines are in the buffer defer os.Remove(tmpfile.Name()) // clean up assert.NoError(t, err) tmpfile.Close() var buf bytes.Buffer w := io.MultiWriter(&buf) err = ReadLogs(context.Background(), tmpfile.Name(), \"\", &LogOptions{tail: -1, bytes: -1, timestamp: true}, nil, w, w) assert.NoError(t, err) lineCount := 0 scanner := bufio.NewScanner(bytes.NewReader(buf.Bytes())) for scanner.Scan() { lineCount++ // Split the line ts, logline, _ := bytes.Cut(scanner.Bytes(), []byte(\" \")) // Verification //   1. The timestamp should exist //   2. The last item in the log should be 9999 _, err = time.Parse(time.RFC3339, string(ts)) assert.NoError(t, err, \"timestamp not found\") assert.Equal(t, true, bytes.HasSuffix(logline, []byte(\"9999\")), \"is the complete log found\") } assert.Equal(t, 2, lineCount, \"should have two lines\") } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-0e28d298340708e57a780633dba41fa2a744d19c9ab3d061a118f6b1e6c3d902", "text": "If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI received a bug report about this issue. The root cause is that the buffer reads up to a new line. If the line is greater than 4096 bytes and '--timestamps' is turrned on the kubelet will write the timestamp and the partial log line. We will need to refactor the ReadLogs function to allow for a partial line read.", "commid": "kubernetes_issue_77603", "tokennum": 104}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f6a5f086e16a35780fc69f27f64ffbcc5faa21cf4adbe1ed40ffe8d8859c614b", "query": "cp \"${src_file}\" /etc/kubernetes/manifests } <ins> # Starts cluster autoscaler. function start-cluster-autoscaler { if [ \"${ENABLE_NODE_AUTOSCALER:-}\" = \"true\" ]; then touch /etc/kubernetes/start-cluster-autoscaler-enabled # Remove salt comments and replace variables with values src_file=\"${KUBE_HOME}/kube-manifests/kubernetes/gci-trusty/cluster-autoscaler.manifest\" remove-salt-config-comments \"${src_file}\" local params=`sed 's/^/\"/;s/ /\",\"/g;s/$/\",/' <<< \"${AUTOSCALER_MIG_CONFIG}\"` sed -i -e \"s@\"{{param}}\",@${params}@g\" \"${src_file}\" sed -i -e \"s@{%.*%}@@g\" \"${src_file}\" cp \"${src_file}\" /etc/kubernetes/manifests fi } </ins> # A helper function for copying addon manifests and set dir/files # permissions. #", "positive_passages": [{"docid": "doc-en-kubernetes-cafbbd3cd664270b9fbd0ce7e8faa35ad0e8800a7c5d7cdeb5164eec0f1b24f1", "text": "For some reason they stopped working and we even don't create manifest file for cluster autoscaler. I used the following command to start the cluster:\nIt's possible it's related to", "commid": "kubernetes_issue_26346", "tokennum": 40}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f6f7c6384c04bab0a1dd81fa2e794f07858a9d7b47b566b9cf486eeda7169e53", "query": "if StatusStrategy.AllowCreateOnUpdate() { t.Errorf(\"Namespaces should not allow create on update\") } <ins> now := util.Now() </ins> oldNamespace := &api.Namespace{ ObjectMeta: api.ObjectMeta{Name: \"foo\", ResourceVersion: \"10\"}, Spec:       api.NamespaceSpec{Finalizers: []api.FinalizerName{\"kubernetes\"}}, Status:     api.NamespaceStatus{Phase: api.NamespaceActive}, } namespace := &api.Namespace{ <del> ObjectMeta: api.ObjectMeta{Name: \"foo\", ResourceVersion: \"9\"}, </del> <ins> ObjectMeta: api.ObjectMeta{Name: \"foo\", ResourceVersion: \"9\", DeletionTimestamp: &now}, </ins> Status:     api.NamespaceStatus{Phase: api.NamespaceTerminating}, } StatusStrategy.PrepareForUpdate(namespace, oldNamespace)", "positive_passages": [{"docid": "doc-en-kubernetes-859a8b847337ca2cf9879726f3bdb71f0db5559ee2589591ceae612e41f71a1b", "text": "There is a funny subtle behvaiour in get namespaces, in which if i call more than one time, it seems that the removal from Terminating state is accelarated. It seems this might indicate a bug, or maybe its not a bug and the eventual semantics of is a little funny sometimes. in any case, here's what we are seeing : 1) when i delete a namespace the first time usning kubectl, we get a state change to . that is correct, of course. 2) but ... if make the call a second time, then the same status line is immediately removed from . Expected behaviour : A second call to \"kubectl delete ...\" shouldn't have any effect on the timing of removal of a namespace from 'Terminating' state*... So i guess there is some \"eventual consistency\" subtle bug that is resolved by repeated calls to\nsuggests this may not be e bug, maybe its just the etcd eventual deleter thingy.\nLooks to definitely be a bug. The 2nd delete seems to have interrupted the delete process and artifacts (like events) from the namespace still exist in etcd.\ninvestigating...\noops, see the error, will submit a fix.\nI have a fix, but need a test case, will submit PR tomorrow AM", "commid": "kubernetes_issue_6633", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f6ffe2edad939090f6912ed2d681b52b1f1172ea3fd462600a61b2c39023fb2b", "query": "nodeIP:            netutils.ParseIPSloppy(\"::\"), nodeAddresses:     []v1.NodeAddress{}, cloudProviderType: cloudProviderExternal, <del> expectedAddresses: []v1.NodeAddress{}, shouldError:       false, </del> <ins> expectedAddresses: []v1.NodeAddress{ {Type: v1.NodeHostName, Address: testKubeletHostname}, }, shouldError: false, </ins> }, { name:              \"cloud provider is external and no nodeIP\", nodeAddresses:     []v1.NodeAddress{}, cloudProviderType: cloudProviderExternal, <del> expectedAddresses: []v1.NodeAddress{}, shouldError:       false, </del> <ins> expectedAddresses: []v1.NodeAddress{ {Type: v1.NodeHostName, Address: testKubeletHostname}, }, shouldError: false, </ins> }, { name: \"cloud doesn't report hostname, no override, detected hostname mismatch\",", "positive_passages": [{"docid": "doc-en-kubernetes-7c861bbb23da2f1ab2b6ca68ce44086076d9635fab7f36a80cef91e7d1c385de", "text": "It looks like there was a change that first appeared in Kubernetes 1.29, where in 1.29 the flag on kubelet is no longer being used to populate the Node's Addresses.Hostname value. Here is the relevant output from a for a 1.28 cluster with : And here's the output from a 1.29 cluster with the same configuration: Here is the full list of parameters in case that is helpful: This is from an IBM Cloud Kubernetes Service 1.28 and 1.29 cluster. We do not think there was any cloud-configuration-manager or any other related change that would cause this difference. Is it possible it is a side effect of ? I expected the behavior to be consistent between Kubernetes releases, since I didn't find any reference to this change in Create an IBM Cloud Kubernetes Service cluster at 1.28 and 1.29 and see the difference No response <details</details<details</details<details</details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nyeah, it seems likely my change broke this, it should keep working as you say, let me take a look /assign\n/sig network /sig cloud-provider\n/assign /unassign Thanks\nFYI it was an unintended side effect of:\nDo the sig cloud provider folks need to help here? We did make external cloud providers the default as of 1.29, which may have uncovered this. Let us know!\nNo, it's just a dumb kubelet startup bug. Well, not dumb, but easy to fix.\nIt seems the problem is that once kubelet sets the hostname the cloud controller manager does not override it so maybe the right behavior is only override it if is actually overridden ?\nwhat problem?", "commid": "kubernetes_issue_124453", "tokennum": 469}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f6ffe2edad939090f6912ed2d681b52b1f1172ea3fd462600a61b2c39023fb2b", "query": "nodeIP:            netutils.ParseIPSloppy(\"::\"), nodeAddresses:     []v1.NodeAddress{}, cloudProviderType: cloudProviderExternal, <del> expectedAddresses: []v1.NodeAddress{}, shouldError:       false, </del> <ins> expectedAddresses: []v1.NodeAddress{ {Type: v1.NodeHostName, Address: testKubeletHostname}, }, shouldError: false, </ins> }, { name:              \"cloud provider is external and no nodeIP\", nodeAddresses:     []v1.NodeAddress{}, cloudProviderType: cloudProviderExternal, <del> expectedAddresses: []v1.NodeAddress{}, shouldError:       false, </del> <ins> expectedAddresses: []v1.NodeAddress{ {Type: v1.NodeHostName, Address: testKubeletHostname}, }, shouldError: false, </ins> }, { name: \"cloud doesn't report hostname, no override, detected hostname mismatch\",", "positive_passages": [{"docid": "doc-en-kubernetes-cb25003b88a3fd857f2f7edabf578ed21b587771e769d62a703fb5f227a9b05a", "text": "we are discussing if the fix should be backported or not It seems you are relaying on the with type Hostname and this not clearly documented We also find out recently that the behavior of this address will be overriden if the external cloud provider configures it if the external cloud provider returns the hostname , then this problem will be solved without need to backport\n(Well, to clarify my comments there: it's not well-defined between different clouds and node linux distros. If you know what cloud and distro you are on, then the behavior might be consistent and usable, but that still makes for a lousy kubernetes API.) Anyway, the question here is: was this actually breaking anything major, or did you just happen to notice this and think \"that's weird\"? (Also, if anyone else was broken by this bug, feel free to chime in; trying to figure out what to do about backporting this, because the original fix for this bug ended up introducing another bug, and the fix for that_ bug is maybe not backport-able...)\nSo far I have only heard from a single customer (who was using IBM Cloud Kubernetes Service) who had something in their cluster relying on cluster node's Address.Hostname value, and so when they updated to 1.29 they were broken. I believe they just modified their code to get this \"Hostname\" value (which was really the node IP) from somewhere else. So, to answer the question, it is somewhere between the \"I noticed it and thought 'that's weird'\" option and the \"it broke something major\" option. We have this documented in our 1.29 release notes for IBM Cloud Kubernetes Service, so other customers will have fair warning before updating. So at this point I don't consider fixing this in 1.29 as essential.", "commid": "kubernetes_issue_124453", "tokennum": 399}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f731ab3816a92c1b6569a231fe6aebed16045fbb6eb7b386929bc865484b58eb", "query": "} func (mounter *execMounter) IsNotMountPoint(dir string) (bool, error) { <del> return IsNotMountPoint(mounter, dir) </del> <ins> return isNotMountPoint(mounter, dir) </ins> } func (mounter *execMounter) IsLikelyNotMountPoint(file string) (bool, error) {", "positive_passages": [{"docid": "doc-en-kubernetes-4bcfc015d2b9d9fa1e84475a3e08fb9ef8299b4e5f821f790188ad7bdae6ecbc", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: There's , and . The former is used by local and nfs volume plugins, while the latter is used by , which is also used by local and nfs volume plugins. What you expected to happen: Can we consolidate these? This is really confusing and could easily be the source of bugs. <!-- DO NOT EDIT BELOW THIS LINE --/kind cleanup\ncc\n/assign I'd like to clean up code.", "commid": "kubernetes_issue_72387", "tokennum": 133}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f73ac31aad0d03fcbc40548d97e3710f76602dd53a791335b19ad6cd6a910673", "query": "<ins> // Build it with: //   $ dot -Tsvg releasing.dot >releasing.svg digraph tagged_release { size = \"5,5\" // Arrows go up. rankdir = BT subgraph left { // Group the left nodes together. ci012abc -> pr101 -> ci345cde -> pr102 style = invis } subgraph right { // Group the right nodes together. version_commit -> dev_commit style = invis } { // Align the version commit and the info about it. rank = same // Align them with pr101 pr101 version_commit // release_info shows the change in the commit. release_info } { // Align the dev commit and the info about it. rank = same // Align them with 345cde ci345cde dev_commit dev_info } // Join the nodes from subgraph left. pr99 -> ci012abc pr102 -> pr100 // Do the version node. pr99 -> version_commit dev_commit -> pr100 tag -> version_commit pr99 [ label = \"Merge PR #99\" shape = box fillcolor = \"#ccccff\" style = \"filled\" fontname = \"Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif\" ]; ci012abc [ label = \"012abc\" shape = circle fillcolor = \"#ffffcc\" style = \"filled\" fontname = \"Consolas, Liberation Mono, Menlo, Courier, monospace\" ]; pr101 [ label = \"Merge PR #101\" shape = box fillcolor = \"#ccccff\" style = \"filled\" fontname = \"Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif\" ]; ci345cde [ label = \"345cde\" shape = circle fillcolor = \"#ffffcc\" style = \"filled\" fontname = \"Consolas, Liberation Mono, Menlo, Courier, monospace\" ]; pr102 [ label = \"Merge PR #102\" shape = box fillcolor = \"#ccccff\" style = \"filled\" fontname = \"Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif\" ]; version_commit [ label = \"678fed\" shape = circle fillcolor = \"#ccffcc\" style = \"filled\" fontname = \"Consolas, Liberation Mono, Menlo, Courier, monospace\" ]; dev_commit [ label = \"456dcb\" shape = circle fillcolor = \"#ffffcc\" style = \"filled\" fontname = \"Consolas, Liberation Mono, Menlo, Courier, monospace\" ]; pr100 [ label = \"Merge PR #100\" shape = box fillcolor = \"#ccccff\" style = \"filled\" fontname = \"Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif\" ]; release_info [ label = \"pkg/version/base.go:ngitVersion = \"v0.5\";\" shape = none fontname = \"Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif\" ]; dev_info [ label = \"pkg/version/base.go:ngitVersion = \"v0.5-dev\";\" shape = none fontname = \"Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif\" ]; tag [ label = \"$ git tag -a v0.5\" fillcolor = \"#ffcccc\" style = \"filled\" fontname = \"Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif\" ]; } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-7c5448078f172c3dba4d1f6f6ed5d66f21d2fc0ea9dd38dbb1ed9b4cc49eea15", "text": "Right now, we have a mixture of user documentation and developer documentation in the top-level directory. We should make it easier to find a just user documentation. Step 1 would be to move developer documentation into a subdir like docs/development or something like that. User docs would stay in the top-level docs dir.\nmove to", "commid": "kubernetes_issue_1797", "tokennum": 71}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f73c008b8718ffbb658f43045944adee08e9a5a9c371df0f20354292eb3067a5", "query": "loadBalancerName := cloudprovider.GetLoadBalancerName(apiService) serviceName := types.NamespacedName{Namespace: apiService.Namespace, Name: apiService.Name} <del> securityGroupIDs, err := c.buildELBSecurityGroupList(serviceName, loadBalancerName, annotations[ServiceAnnotationLoadBalancerExtraSecurityGroups]) </del> <ins> securityGroupIDs, err := c.buildELBSecurityGroupList(serviceName, loadBalancerName, annotations) </ins> if err != nil { return nil, err }", "positive_passages": [{"docid": "doc-en-kubernetes-f0769863fab39b633cda95f4d162dbe6bf42638a791c88a2a3acb41bb68633b3", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature /sig aws What happened: In k8s 1.7, when creating a service of type LoadBalancer, K8S creates the ELB and a Security Group for it. For these resources, it adds a tag, constructed dynamically, containing the cluster id: \"${cluster_id}\" with the value \"true\" What you expected to happen: We'd like to have also a statically named tag , as it was in 1.5 (\"KubernetesCluster\") with the value of the cluster id. How to reproduce it (as minimally and precisely as possible): Running on AWS cloud provider, create a service of type LoadBalancer. Anything else we need to know?: The reason for what we expect is that we have tight security constraints that require us to fine tune the IAM policies for the Instance profiles that the controllers use. With a statically named tag we were able, in 1.5, to restrict the permissions in the IAM policy to act only on the k8s managed resources (ELBs, security groups). Here is the relevant part of the IAM policy: With a dynamically named tag we are not able to do this any more as AWS IAM doesn't support something like: We are sharing the Instance Profiles among different k8s clusters, hence the \"\" in the value of the tag. Environment: Kubernetes version (use ):Cloud provider or hardware configuration*: AWS OS (e.g. from /etc/os-release):Kernel (e.g. ):Install tools: kube-aws Others:\nReiterating the mentions to trigger a notification: <detailsIn response to : <!-- This form is for bug reports and feature requests ONLY! -- /sig aws In k8s 1.7, when creating a service of type LoadBalancer, K8S creates the ELB and a Security Group for it. For these resources, it adds a tag, constructed dynamically, containing the cluster id: \"${cluster_id}\" with the value \"true\" We'd like to have also a statically named tag , as it was in 1.5 (\"KubernetesCluster\") with the value of the cluster id. Running on AWS cloud provider, create a service of type LoadBalancer.", "commid": "kubernetes_issue_53489", "tokennum": 543}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f73c008b8718ffbb658f43045944adee08e9a5a9c371df0f20354292eb3067a5", "query": "loadBalancerName := cloudprovider.GetLoadBalancerName(apiService) serviceName := types.NamespacedName{Namespace: apiService.Namespace, Name: apiService.Name} <del> securityGroupIDs, err := c.buildELBSecurityGroupList(serviceName, loadBalancerName, annotations[ServiceAnnotationLoadBalancerExtraSecurityGroups]) </del> <ins> securityGroupIDs, err := c.buildELBSecurityGroupList(serviceName, loadBalancerName, annotations) </ins> if err != nil { return nil, err }", "positive_passages": [{"docid": "doc-en-kubernetes-a01a3c41e631760f28b69af73c7e0688234151a20f7dd4b67642a3c81f6b4dfa", "text": "The reason for what we expect is that we have tight security constraints that require us to fine tune the IAM policies for the Instance profiles that the controllers use. With a statically named tag we were able, in 1.5, to restrict the permissions in the IAM policy to act only on the k8s managed resources (ELBs, security groups). Here is the relevant part of the IAM policy: Environment: Kubernetes version (use ):OS (e.g. from /etc/os-release):Others: </details\nI believe they are moving away from the tag since there are many resources that can be shared by multiple clusters. could you use an annotation?\nWe removed the condition in roles in the end. Thank you for your suggestion.\nThat annotation affects the ELB but not any security groups that are created. can you please reopen this? You reported a real issue, and even if it no longer affects you, it needs to be tracked and fixed.\nIndeed, this might be a feature that someone else would need.\nIn fact, this is a feature I need!\nFood for thought: should we propagate the tags on the ELB to the SG, or should we introduce an annotation for the SG specifically?", "commid": "kubernetes_issue_53489", "tokennum": 265}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f740146422fa9d92b4512091e13b031ffaa922c4132cc8fe40f7222b881d84d0", "query": "kube::test::get_object_assert 'rc mock2' \"{{${labels_field}.status}}\" 'replaced' fi fi <ins> # Command: kubectl edit multiple resources temp_editor=\"${KUBE_TEMP}/tmp-editor.sh\" echo -e '#!/bin/bashnsed -i \"s/status: replaced/status: edited/g\" $@' > \"${temp_editor}\" chmod +x \"${temp_editor}\" EDITOR=\"${temp_editor}\" kubectl edit \"${kube_flags[@]}\" -f \"${file}\" # Post-condition: mock service (and mock2) and mock rc (and mock2) are edited if [ \"$has_svc\" = true ]; then kube::test::get_object_assert 'services mock' \"{{${labels_field}.status}}\" 'edited' if [ \"$two_svcs\" = true ]; then kube::test::get_object_assert 'services mock2' \"{{${labels_field}.status}}\" 'edited' fi fi if [ \"$has_rc\" = true ]; then kube::test::get_object_assert 'rc mock' \"{{${labels_field}.status}}\" 'edited' if [ \"$two_rcs\" = true ]; then kube::test::get_object_assert 'rc mock2' \"{{${labels_field}.status}}\" 'edited' fi fi # cleaning rm \"${temp_editor}\" </ins> # Command # We need to set --overwrite, because otherwise, if the first attempt to run \"kubectl label\" # fails on some, but not all, of the resources, retries will fail because it tries to modify", "positive_passages": [{"docid": "doc-en-kubernetes-5d8539be161cacf223528437869590f13423a31b1176c381211bcba6b79e0cca", "text": "When trying to edit multiple resources, for example: will panic. Ref as the possible cause cc\nif was the cause, any fix needs to happen in 1.1 as well, was already cherry picked there\nAlso shows that we need a test for this case.\nis the cause. When we edit multiple resources (i.e., list-type objects), the list's Accessor.annotations (type ) is nil and will panic when UpdateApplyAnnotation tries to SetAnnotations ().", "commid": "kubernetes_issue_15907", "tokennum": 108}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f753848d008009a168ddea7e54613ff956313bb3557540a5d16ecd085fff672c", "query": "// Returns true if and only if changes were made // The security group must already exist func (c *Cloud) addSecurityGroupIngress(securityGroupID string, addPermissions []*ec2.IpPermission) (bool, error) { <ins> // We do not want to make changes to the Global defined SG if securityGroupID == c.cfg.Global.ElbSecurityGroup { return false, nil } </ins> group, err := c.findSecurityGroup(securityGroupID) if err != nil { glog.Warningf(\"Error retrieving security group: %q\", err)", "positive_passages": [{"docid": "doc-en-kubernetes-d6a2e132f72678770d8d41e08acf9f7359a4b887e33d930dbbc18ea7ecc9db7e", "text": "/kind bug What happened: When setting an elbSecurityGroup in for AWS, and deploying multiple services with differing ports, then the security group rules flap in AWS, causing services to become inaccessible (only one will be correctly configured at a time). What you expected to happen: I expect that the configured elbSecurityGroup's rules will not be touched at all. It must be pre-configured to permit access. Alternatively, all ports for all services are queried and managed together. How to reproduce it (as minimally and precisely as possible): See above. Anything else we need to know?: Most people are not running large clusters which may hit the AWS limits, so they won't use this option, nor see this issue. Environment: Kubernetes version (use ): 1.7.1 Cloud provider or hardware configuration**: AWS OS (e.g. from /etc/os-release): CentOS 7 Kernel (e.g. ): 4.10.13-1-ARCH Install tools: Custom Others:\nThere are no sig labels on this issue. Please by: a sig: e.g., to notify the contributor experience sig, OR the label manually: e.g., to apply the label Note: Method 1 will trigger an email to the group. You can find the group list and label list . The in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals\n/sig aws\nThis is fixed by", "commid": "kubernetes_issue_50105", "tokennum": 331}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f75bc6f5ba449199a1a2a5da407a278944bf4906792a5f2400ed5b69e3ce26be", "query": "// canConnect returns true if a network connection is possible to the SSHPort. func canConnect(host string) bool { <ins> if _, ok := os.LookupEnv(sshBastionEnvKey); ok { return true } </ins> hostPort := net.JoinHostPort(host, SSHPort) conn, err := net.DialTimeout(\"tcp\", hostPort, 3*time.Second) if err != nil { <ins> e2elog.Logf(\"cannot dial %s: %v\", hostPort, err) </ins> return false } conn.Close()", "positive_passages": [{"docid": "doc-en-kubernetes-375711dd290c57e850707ef6745091e3080fe654060082beb69e30fe80db0e88", "text": "ci-kubernetes-e2e-gce-scale-correctness Kubernetes e2e suite: [sig-node] SSH should SSH to all nodes and run commands kubetest.Test Jul 10 14:01:51 UTC+0200 Kubernetes e2e suite: [sig-node] SSH should SSH to all nodes and run commands: more . Test /sig node\n/cc\n/triage accepted\nUhhh, this may help here\n/milestone v1.22\n/sig scalability FYI\nI got annoyed that I couldn't click through to see the other logs, so now you can, ref: (spyglass doesn't render build- because it's 500MB, and the limit for rendering is 100MB)\n/assign SIG Scalability chairs/TLs, please find someone to address or call this a non-release-blocking failure\nAssigning to current scalability oncall (): /assign\nThis is sig-node issue - should be addres by SIG-node folks. /sig node\nis being discussed as a fix for this and I'm not sure it's correct\nis it sig scalability's intent that 5k node clusters should support SSH?\nThe SSH test in question passes in the \"default\" job: So the fact that this failure is unique to a scalability job means to me that scalability needs to own at least some part of this\nI did a little bit of digging and ci-kubernetes-e2e-gce-scale-correctness uses option in kubetest, which according to seems to be setting KUBESSHBASTION env. So I believe this is main difference between our scalability job and \"default\".\nDebugging the test in and providing a fix there. The crictl host PR () is doing something different.", "commid": "kubernetes_issue_103688", "tokennum": 400}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f76ff24bccf498c6a4594c8faff83b00ada38f698111905c32b479ca1e1ad08e", "query": "\"//pkg/scheduler/algorithm:go_default_library\", \"//pkg/scheduler/algorithm/predicates:go_default_library\", \"//pkg/scheduler/cache:go_default_library\", <ins> \"//pkg/scheduler/metrics:go_default_library\", </ins> \"//pkg/util/hash:go_default_library\", \"//staging/src/k8s.io/api/core/v1:go_default_library\", \"//staging/src/k8s.io/apimachinery/pkg/util/sets:go_default_library\",", "positive_passages": [{"docid": "doc-en-kubernetes-aa59e6a5adfc1b233e34e0c1fe9e3a0ec7f2fe6a4636f877a41f4c9aef45f71d", "text": "/kind feature The equivalence cache feature is planned to move to beta in 1.11, and it would be useful to have some metrics attached to it. The equivalence cache should improve scheduling throughput, so we want to be able to correlate e.g. throughput with eCache hit rate. /sig scheduling /sig instrumentation\n/assign misterikkit\nIssues 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\n/remove-lifecycle stale", "commid": "kubernetes_issue_63259", "tokennum": 154}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f7777a468576d8a545d38f9d5508f015e7b3136d23cecc3575aadd9afb3528ae", "query": "hard[v1.ResourceQuotas] = resource.MustParse(\"1\") hard[v1.ResourceCPU] = resource.MustParse(\"1\") hard[v1.ResourceMemory] = resource.MustParse(\"500Mi\") <del> hard[v1.ResourceConfigMaps] = resource.MustParse(\"2\") </del> <ins> hard[v1.ResourceConfigMaps] = resource.MustParse(\"10\") </ins> hard[v1.ResourceSecrets] = resource.MustParse(\"10\") hard[v1.ResourcePersistentVolumeClaims] = resource.MustParse(\"10\") hard[v1.ResourceRequestsStorage] = resource.MustParse(\"10Gi\")", "positive_passages": [{"docid": "doc-en-kubernetes-7efc22ed3a8fb290fc16a7b40edf13445187015d16976624a8ed8ba9d9def220", "text": "I ran conformance tests on a cluster that had a controller enabled that syncs a configmap across all clusters. It failed: Appears to be due to a 2 configmap limit: These clusters should pass conformance. This is a very common pattern (even Kubernetes itself does it!). I didn't run it myself, but apparently just install Istio and run the conformance suite. See for details Kubernetes version (use ): v1.20.2\n/assign\nmy guess is the CA configmap created by default in 1.20 exacerbated this issue. I agree the conformance test should make fewer assumptions about the cluster it is running in and should accomodate default configmaps. left a comment on the PR in flight for this. I'd like to see the change picked to 1.20 as well.\n/triage accepted /priority important-soon", "commid": "kubernetes_issue_100016", "tokennum": 195}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f78047637f4dcf9e8ca1f0afbb35ef45c2a421785b9a45e2d3178bb83bd626a0", "query": "- base - debian-auto-upgrades - salt-helpers <ins> {% if grains.get('cloud') == 'aws' %} - ntp {% endif %} </ins> 'roles:kubernetes-pool': - match: grain", "positive_passages": [{"docid": "doc-en-kubernetes-2c743938ba30f2fba7527b26804dcfbb8cfcfa24fc2e107c2d5fed7244e0552d", "text": "At least on AWS, if the clock drifts 300 seconds (which it will), then we get the rather cryptic message: This is because AWS includes the timestamp in the request. Installing ntpd would stop this drifting from happening. If the drift does happen, the likely symptom is that EC2 calls would stop working: attach/detach volumes on the minions, instance sync and routing configuration on the master. I don't believe that GCE has the same problem.", "commid": "kubernetes_issue_11371", "tokennum": 102}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f78551fdd9a516f286253b61bc6635bab2691d8df7070e2079c175b1dd4307b4", "query": "<ins> /* Copyright 2016 The Kubernetes Authors All rights reserved. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ // This file was autogenerated by go-to-protobuf. Do not edit it manually! syntax = 'proto2'; package k8s.io.kubernetes.pkg.apis.apps.v1alpha1; import \"k8s.io/kubernetes/pkg/api/resource/generated.proto\"; import \"k8s.io/kubernetes/pkg/api/unversioned/generated.proto\"; import \"k8s.io/kubernetes/pkg/api/v1/generated.proto\"; import \"k8s.io/kubernetes/pkg/util/intstr/generated.proto\"; // Package-wide variables from generator \"generated\". option go_package = \"v1alpha1\"; // PetSet represents a set of pods with consistent identities. // Identities are defined as: //  - Network: A single stable DNS and hostname. //  - Storage: As many VolumeClaims as requested. // The PetSet guarantees that a given network identity will always // map to the same storage identity. PetSet is currently in alpha // and subject to change without notice. message PetSet { optional k8s.io.kubernetes.pkg.api.v1.ObjectMeta metadata = 1; // Spec defines the desired identities of pets in this set. optional PetSetSpec spec = 2; // Status is the current status of Pets in this PetSet. This data // may be out of date by some window of time. optional PetSetStatus status = 3; } // PetSetList is a collection of PetSets. message PetSetList { optional k8s.io.kubernetes.pkg.api.unversioned.ListMeta metadata = 1; repeated PetSet items = 2; } // A PetSetSpec is the specification of a PetSet. message PetSetSpec { // Replicas is the desired number of replicas of the given Template. // These are replicas in the sense that they are instantiations of the // same Template, but individual replicas also have a consistent identity. // If unspecified, defaults to 1. // TODO: Consider a rename of this field. optional int32 replicas = 1; // Selector is a label query over pods that should match the replica count. // If empty, defaulted to labels on the pod template. // More info: http://releases.k8s.io/HEAD/docs/user-guide/labels.md#label-selectors optional k8s.io.kubernetes.pkg.api.unversioned.LabelSelector selector = 2; // Template is the object that describes the pod that will be created if // insufficient replicas are detected. Each pod stamped out by the PetSet // will fulfill this Template, but have a unique identity from the rest // of the PetSet. optional k8s.io.kubernetes.pkg.api.v1.PodTemplateSpec template = 3; // VolumeClaimTemplates is a list of claims that pets are allowed to reference. // The PetSet controller is responsible for mapping network identities to // claims in a way that maintains the identity of a pet. Every claim in // this list must have at least one matching (by name) volumeMount in one // container in the template. A claim in this list takes precedence over // any volumes in the template, with the same name. // TODO: Define the behavior if a claim already exists with the same name. repeated k8s.io.kubernetes.pkg.api.v1.PersistentVolumeClaim volumeClaimTemplates = 4; // ServiceName is the name of the service that governs this PetSet. // This service must exist before the PetSet, and is responsible for // the network identity of the set. Pets get DNS/hostnames that follow the // pattern: pet-specific-string.serviceName.default.svc.cluster.local // where \"pet-specific-string\" is managed by the PetSet controller. optional string serviceName = 5; } // PetSetStatus represents the current state of a PetSet. message PetSetStatus { // most recent generation observed by this autoscaler. optional int64 observedGeneration = 1; // Replicas is the number of actual replicas. optional int32 replicas = 2; } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-21b704a68514d2b400f1a4f479b12f48c6dc4bd890b9d4b14cffa5ee4c13d7d4", "text": "During\nany chance this is related to pass: https://k8s- fail: https://k8s- https://k8s-\nThis is because for some reason the submit queue rebuild didn't catch the flake before merging. Protobuf landed first, merging a new api object like petset should have failed.\nQuick fix is to rebuild the proto marshalers and push.\nAlso, hack/verify-generated- is broken, which probably is the root cause.\nLooking at it now\nThree problems: -generated-protobuf wasn't updated when we made update-generated-protobuf use docker, so it didn't fail out script was verifying the old API groups, not any of the new API groups that have been merged without protobuf serializations (although pkg/api/serialization_test should have failed, possibly the job didn't build with the latest master?), which caused the tests to fail\nSomething about the merge bot is broken - it merged without all the tests being green: . That's why this broke -\nSpawned since there is something wrong with update-generated-protobuf - will merge that to fix the failing test and then debug the generator in the morning.\nThe bot can race with pushes between when it starts testing and when it merges...", "commid": "kubernetes_issue_24579", "tokennum": 281}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f7ce21d49c9cc28eb20a11850a34026bfa251c080f39dedac8a4904e2c2ff4cd", "query": "var errBadJSONDoc = fmt.Errorf(\"Invalid JSON Document\") var errBadJSONPatch = fmt.Errorf(\"Invalid JSON Patch\") <ins> var errBadMergeTypes = fmt.Errorf(\"Mismatched JSON Documents\") </ins> // MergeMergePatches merges two merge patches together, such that // applying this resulting merged merge patch to a document yields the same", "positive_passages": [{"docid": "doc-en-kubernetes-e51351c05e6844b765acf34eaa6a0653d5a4e3452baed4722f32f9c5caa3ece5", "text": "/kind bug What happened: Wrote a that returned a faulty json patch which specified an our of range index (e.G. when there is only one container). This resulted in the apiserver crashing. Stacktrace: What you expected to happen: No crash /sig-api-machinery\n/sig api-machinery\nThis maybe a bug in . I will follow this question.\nThis bug had been fixed in PR: you can checkout it.\nThanks for your comment but I don't think the linked PR fixed the issue, as it got merged almost a year ago and I am running Kube 1.10.1 which does contain that patch but still panics. Just from quickly looking at the code I the linked PR I believe there are two things wrong: The check if the index is valid only happens when a negative index was given should be\nOnce the PR of is merged I will update kubernetes.\n/kind bug", "commid": "kubernetes_issue_64291", "tokennum": 194}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f7ff62d616972738022bbb109de62d090adbb925e77279916310f81d743b548d", "query": "} func getMemoryStat(f *framework.Framework, host string) (rss, workingSet float64) { <del> memCmd := \"cat /sys/fs/cgroup/memory/system.slice/node-problem-detector.service/memory.usage_in_bytes && cat /sys/fs/cgroup/memory/system.slice/node-problem-detector.service/memory.stat\" </del> <ins> var memCmd string isCgroupV2 := isHostRunningCgroupV2(f, host) if isCgroupV2 { memCmd = \"cat /sys/fs/cgroup/system.slice/node-problem-detector.service/memory.current && cat /sys/fs/cgroup/system.slice/node-problem-detector.service/memory.stat\" } else { memCmd = \"cat /sys/fs/cgroup/memory/system.slice/node-problem-detector.service/memory.usage_in_bytes && cat /sys/fs/cgroup/memory/system.slice/node-problem-detector.service/memory.stat\" } </ins> result, err := e2essh.SSH(memCmd, host, framework.TestContext.Provider) framework.ExpectNoError(err) framework.ExpectEqual(result.Code, 0)", "positive_passages": [{"docid": "doc-en-kubernetes-0c07e91eb7d66ee92c3b6d05f523cece58039dffcf1123c44ba752c30922deab", "text": "N/A [sig-node] NodeProblemDetector: N/A https://prow- Not cgroupv2 compatible when access cpu and memory data\n/sig node\nHi, can i work on this ?\nSure. Thanks\n/assign\n/triage accepted\n/priority important-soon\n/cc\nare you still working on this? Were you able to setup environment to repro the test failure? Let us know if you need any help. Thanks!\nSorry for the delay, I followed the wrong guide and ended up getting stuck. But now I have managed to set it up. Please give me few more days to work on it.\nThanks Feel free to reach out here or on slack if you need any help, thanks for working on this!\n/retitle Make nodeproblemdetector test cgroupv2 compatible\nFailing job:\nTestgrid:", "commid": "kubernetes_issue_105178", "tokennum": 180}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f833c7e5ae75777383ee75161fd366da4959cd37f4f3d83a0648d20922988aaf", "query": ") const ( <del> diskPartitionSuffix = \"\" checkSleepDuration  = time.Second </del> <ins> diskPartitionSuffix     = \"\" nvmeDiskPartitionSuffix = \"p\" checkSleepDuration      = time.Second </ins> ) // AWSDiskUtil provides operations for EBS volume.", "positive_passages": [{"docid": "doc-en-kubernetes-d5a9e8b7bbc510dc155bb81dd6aed03e6a233b66a01ab8a13237a98090288309", "text": "When using a AWS EBS PV or on-line volume with a partition on a Nitro machine, the volume is available as NVMe device. Kubelet is not able to format & mount the partition: It seems to me that AWS EBS volume plugin does not support partitions at all. The partition is mounted. Using an in-line volume with this pod:\n/sig storage /sig cloud-provider /area provider/aws\n/triage accepted", "commid": "kubernetes_issue_100499", "tokennum": 100}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f84ec6d37ca6f6e505d05bdddcd62aeb35a12044aca2d4da45d178d45d5dd393", "query": "<-stoppedChan // Simulate what DSOWP does <del> pv.Spec.Capacity[v1.ResourceStorage] = tc.newPVSize volumeSpec = &volume.Spec{PersistentVolume: pv} </del> <ins> pvWithSize.Spec.Capacity[v1.ResourceStorage] = tc.newPVSize volumeSpec = &volume.Spec{PersistentVolume: pvWithSize} </ins> dsw.AddPodToVolume(podName, pod, volumeSpec, volumeSpec.Name(), \"\" /* volumeGidValue */) // mark volume as resize required asw.MarkFSResizeRequired(volumeName, podName)", "positive_passages": [{"docid": "doc-en-kubernetes-d047193f0eb4348dad25266c8f06cc7d0100df3011e6281006c74e70d78d442e", "text": "<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI --pull-kubernetes-unit : (PR with no go code changes, should not have failed any unit tests) links to appreciated links to specific failures in spyglass appreciated <!-- Please see the deflaking doc () for more guidance! --/sig storage\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assigne\n/assign\n/assign tried to fix it in", "commid": "kubernetes_issue_99815", "tokennum": 196}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f850ccaa6a71334670066bd500c025d804261cec3aac7fa37f7c765b5e877ccc", "query": "@JsonIgnoreProperties(ignoreUnknown = true) static class Address { <del> public String IP; </del> <ins> public String ip; </ins> } @JsonIgnoreProperties(ignoreUnknown = true)", "positive_passages": [{"docid": "doc-en-kubernetes-600b05087b3e5a02baef82de4ad7a72820fecd2de58582bba171390ab13fae8d", "text": "The namespace seems to be hard coded :\ncc:\nThanks. We can improve it after v1 release.", "commid": "kubernetes_issue_10034", "tokennum": 22}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f8605dd6db376a30731e3663f2e483081aba64b5673b1cdf1b86c450f18f7654", "query": "<ins> apiVersion: v1beta3 </ins> kind: ReplicationController <del> apiVersion: v1beta1 id: kube-dns namespace: default labels: k8s-app: kube-dns kubernetes.io/cluster-service: \"true\" desiredState: </del> <ins> metadata: labels: k8s-app: kube-dns kubernetes.io/cluster-service: \"true\" name: kube-dns namespace: default spec: </ins> replicas: {{ pillar['dns_replicas'] }} <del> replicaSelector: </del> <ins> selector: </ins> k8s-app: kube-dns <del> podTemplate: labels: name: kube-dns k8s-app: kube-dns kubernetes.io/cluster-service: \"true\" desiredState: manifest: version: v1beta2 id: kube-dns dnsPolicy: \"Default\"  # Don't use cluster DNS. containers: - name: etcd image: gcr.io/google_containers/etcd:2.0.9 command: [ \"/usr/local/bin/etcd\", \"--addr\", \"127.0.0.1:4001\", \"--bind-addr\", \"127.0.0.1:4001\", \"-initial-cluster-token=skydns-etcd\", ] - name: kube2sky image: gcr.io/google_containers/kube2sky:1.4 volumeMounts: - name: dns-token mountPath: /etc/dns_token readOnly: true command: [ # entrypoint = \"/kube2sky\", \"-domain={{ pillar['dns_domain'] }}\", \"-kubecfg_file=/etc/dns_token/kubeconfig\", ] - name: skydns image: gcr.io/google_containers/skydns:2015-03-11-001 command: [ # entrypoint = \"/skydns\", \"-machines=http://localhost:4001\", \"-addr=0.0.0.0:53\", \"-domain={{ pillar['dns_domain'] }}.\", ] ports: - name: dns containerPort: 53 protocol: UDP volumes: - name: dns-token source: secret: target: kind: Secret namespace: default name: token-system-dns </del> <ins> template: metadata: labels: k8s-app: kube-dns kubernetes.io/cluster-service: \"true\" name: kube-dns spec: containers: - name: etcd image: gcr.io/google_containers/etcd:2.0.9 command: - /usr/local/bin/etcd - --addr - 127.0.0.1:4001 - --bind-addr - 127.0.0.1:4001 - -initial-cluster-token=skydns-etcd - name: kube2sky image: gcr.io/google_containers/kube2sky:1.4 args: # entrypoint = \"/kube2sky\" - -domain={{ pillar['dns_domain'] }} - -kubecfg_file=/etc/dns_token/kubeconfig volumeMounts: - mountPath: /etc/dns_token name: dns-token readOnly: true - name: skydns image: gcr.io/google_containers/skydns:2015-03-11-001 args: # entrypoint = \"/skydns\" - -machines=http://localhost:4001 - -addr=0.0.0.0:53 - -domain={{ pillar['dns_domain'] }}. ports: - containerPort: 53 name: dns protocol: UDP livenessProbe: exec: command: - \"/bin/sh\" - \"-c\" # The health check succeeds by virtue of not hanging. It'd be nice # to also check local services are known, but if that's broken then # etcd or kube2sky has to be restarted, not skydns. - \"nslookup foobar 127.0.0.1 &> /dev/null; echo ok\" initialDelaySeconds: 30 timeoutSeconds: 5 dnsPolicy: Default  # Don't use cluster DNS. volumes: - name: dns-token secret: secretName: token-system-dns </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-73f410f7efe3cc7bf518718d7991551770a7ae4fe70afae3d631ca538f35fb20", "text": "I have observed the DNS pod sometimes getting stuck. Need a health-check that tries to do a lookup or something like that.\nalso DNS should probably come up with N=2 by default\nWhy is this attached to 1.0 if it's P3? One of those is wrong.\nHealth checks I can believe. We're in the process of doing that for everything else -- Nothing else is HA, so I don't buy N=2 for DNS but not for other components.\nOther components are somewhat harder to make HA. DNS is trivially HA-able. But not too important, it's available after the fact, too. , Brian Grant wrote:\nso you mean a generic solution for health checking, or just you are adding health check for other service. In other words should I start adding health check for DNS?\nI'd still like to see a health-check for DNS, but I am not sure what is appropriate, though. Maybe have kube2sky open an HTTP server and answer /healthz iff it can complete a non-existing DNS query? Better ideas? It seems the collected other fixes add up to a more stable DNS server? , Piotr Szczesniak wrote:\nI assume this is about adding liveness probes to one or more of the containers in the dns pod: Is dig in the skydns image? We could use an exec probe to perform a DNS query.\nduh, exec probe is obviously better :) But it doesn't need to get a name, it just needs to complete and not hang. so something like sh -c \"alarm 5 nslookup foobar\" maybe? , Brian Grant wrote:\nleaving unassigned since I'm not working on it right now\nare you currently working on this? If not, I'll grab it. Thanks! --brendan\nI think that was looking into this today.\nYeah, I sat on it a little today due to not being able to get it to actually work, but I'm pretty sure it wasn't working because exec liveness probes as a whole are broken (). Sent PR to resolve this once exec probes are functional.", "commid": "kubernetes_issue_4852", "tokennum": 466}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f8732e6e3988eef5b5467e97817b0a0f377b90d2958309d22f8c4019b94f3b3a", "query": "## Prerequisites This example requires a running Kubernetes cluster and kubectl in the version at least 1.1. <ins> [Heapster](https://github.com/kubernetes/heapster) monitoring needs to be deployed in the cluster as horizontal pod autoscaler uses it to collect metrics (if you followed [getting started on GCE guide](../../../docs/getting-started-guides/gce.md), heapster monitoring will be turned-on by default). </ins> ## Step One: Run & expose php-apache server", "positive_passages": [{"docid": "doc-en-kubernetes-0f2f59a4098799df231d0f4ddd6804f8b020392d4e4aa17c98fa7a6b4bb4eccd", "text": "The heapster needs to be installed if end user want to use autoscaler feature, we should mention this in document.", "commid": "kubernetes_issue_17466", "tokennum": 25}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f874189ec9cfac3c2e7c3767ea2bc90359ac87506d526b0a1352251035258f88", "query": "env.ServiceManagementEndpoint) } <del> return nil, fmt.Errorf(\"No credentials provided for AAD application %s\", config.AADClientID) </del> <ins> return nil, ErrorNoAuth </ins> } // ParseAzureEnvironment returns azure environment by name", "positive_passages": [{"docid": "doc-en-kubernetes-effe9bff1df2586252b385cbf4a7cacd04cb77f4739ff9c987e63818f9dc1c82", "text": "Currently there is no way to run without any identity (be it service principal or E/MSI). In reality code running on a worker node can use via - and only via - without the need to access ARM. Here is the proposed change a new mode authN = this mode, is basically telling the cloud provider to work any identity, this means only IMDS calls is allowed. This mode can be detected from if no SPN set and both MSI settings are set to . to use a config map within the cluster. This config map can be loaded on the cluster statically. or created - if not existent - in that then only is used in The net new result of the above is users bootstrapping clusters can configure the worker node to use without any identity on said worker nodes.\n/sig azure These SIGs are my best guesses for this issue. Please comment if I am incorrect about one. I am a bot run by \u200d\nIn-tree AzureDisk volume plugin is also depending on Azure credential to fetch lun id. we should figure out how to solve it without credential\nfetch disk lun id is also a dependency in kubelet code now, after my investigation, it could be removed on Linux node, while it cannot be removed on Windows node, need to change the k/k upstream code, there is a discussion on going here: , let' wait for the discussion result.\nFor Linux: 1- use IMDS my understanding is new api versions will have the disk/lun pairs. 2- don't use arm for the return of is the second parameter passed to . For Windows: I don't understand the dep on ARM for this. The above still apply, we just need to find a way to encode the value as ut return from that allow us to find the disk by on a windows machine. might be a good source for this. Ideally speaking. The value should be the same. But i will leave it for you to decide.\ncould be a good idea since currently it's a LUN num returned by Attach() and then it could be changed to the windows disk num, I will make the code change on v1.15 later, thanks for discussion.\nUpdate: PR would remove the VM API calls when getting the LUN number for AzureDisk.", "commid": "kubernetes_issue_77309", "tokennum": 490}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f87b99a25f9a793b04ba641e269dd3ec09c3fa3c220fe546de2b7de449e562b4", "query": "return -1, danglingErr } <del> if disk.DiskProperties != nil && disk.DiskProperties.Encryption != nil && disk.DiskProperties.Encryption.DiskEncryptionSetID != nil { diskEncryptionSetID = *disk.DiskProperties.Encryption.DiskEncryptionSetID </del> <ins> if disk.DiskProperties != nil { if disk.DiskProperties.DiskSizeGB != nil && *disk.DiskProperties.DiskSizeGB >= diskCachingLimit && cachingMode != compute.CachingTypesNone { // Disk Caching is not supported for disks 4 TiB and larger // https://docs.microsoft.com/en-us/azure/virtual-machines/premium-storage-performance#disk-caching cachingMode = compute.CachingTypesNone klog.Warningf(\"size of disk(%s) is %dGB which is bigger than limit(%dGB), set cacheMode as None\", diskURI, *disk.DiskProperties.DiskSizeGB, diskCachingLimit) } if disk.DiskProperties.Encryption != nil && disk.DiskProperties.Encryption.DiskEncryptionSetID != nil { diskEncryptionSetID = *disk.DiskProperties.Encryption.DiskEncryptionSetID } </ins> } if v, ok := disk.Tags[WriteAcceleratorEnabled]; ok { if v != nil && strings.EqualFold(*v, \"true\") { writeAcceleratorEnabled = true", "positive_passages": [{"docid": "doc-en-kubernetes-3186f04d894d2e98a9b770821be5e33542dd055d445ea6f78bf8e42e85bb59f7", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: there is a disk resize scenario: In the beginning, it\u2019s 3TiB with cachingMode=ReadOnly, and then disk detached, resized to 4TiB, then user find they could not attach that disk back to any agent node, I think that\u2019s a bug we need to fix. What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others: /kind bug /assign /priority important-soon /sig cloud-provider /area provider/azure\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details", "commid": "kubernetes_issue_95465", "tokennum": 311}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f8a0255790bc3c5700ba6c6090be5d9a19f08ee0066cc445e0d4568df594f868", "query": "return nil, err } <del> leaderElectionClient := clientset.NewForConfigOrDie(restclient.AddUserAgent(kubeconfig, \"leader-election\")) </del> <ins> // shallow copy, do not modify the kubeconfig.Timeout. config := *kubeconfig config.Timeout = s.GenericComponent.LeaderElection.RenewDeadline.Duration leaderElectionClient := clientset.NewForConfigOrDie(restclient.AddUserAgent(&config, \"leader-election\")) </ins> eventRecorder := createRecorder(client, KubeControllerManagerUserAgent)", "positive_passages": [{"docid": "doc-en-kubernetes-638d244f4d44257351ae4786f705d88f47a0e12c74ce71a459164cb07c9c1943", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . If the matter is security related, please disclose it privately via --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: kube-cm kube-scheduler does not exit when kube-apiserver suspended What you expected to happen: kube-cm kube-scheduler should exit after LeaderElector stops leading How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/sig api-machinery /kind bug\n/assign\n/cc", "commid": "kubernetes_issue_65090", "tokennum": 179}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f8a6e0531ecdb6da2735962cfb98eb0c57cec7b361bde59f22317f92bc86ec5a", "query": "assert.Exactly(t, []*PodLifecycleEvent{event}, actualEvents) } } <ins> func TestRunningPodAndContainerCount(t *testing.T) { fakeRuntime := &containertest.FakeRuntime{} runtimeCache, _ := kubecontainer.NewRuntimeCache(fakeRuntime) metrics.Register(runtimeCache) testPleg := newTestGenericPLEG() pleg, runtime := testPleg.pleg, testPleg.runtime runtime.AllPodList = []*containertest.FakePod{ {Pod: &kubecontainer.Pod{ ID: \"1234\", Containers: []*kubecontainer.Container{ createTestContainer(\"c1\", kubecontainer.ContainerStateRunning), createTestContainer(\"c2\", kubecontainer.ContainerStateUnknown), createTestContainer(\"c3\", kubecontainer.ContainerStateUnknown), }, }}, {Pod: &kubecontainer.Pod{ ID: \"4567\", Containers: []*kubecontainer.Container{ createTestContainer(\"c1\", kubecontainer.ContainerStateExited), }, }}, } pleg.relist() // assert for container count with label \"running\" actualMetricRunningContainerCount := &dto.Metric{} expectedMetricRunningContainerCount := float64(1) metrics.RunningContainerCount.WithLabelValues(string(kubecontainer.ContainerStateRunning)).Write(actualMetricRunningContainerCount) assert.Equal(t, expectedMetricRunningContainerCount, actualMetricRunningContainerCount.GetGauge().GetValue()) // assert for container count with label \"unknown\" actualMetricUnknownContainerCount := &dto.Metric{} expectedMetricUnknownContainerCount := float64(2) metrics.RunningContainerCount.WithLabelValues(string(kubecontainer.ContainerStateUnknown)).Write(actualMetricUnknownContainerCount) assert.Equal(t, expectedMetricUnknownContainerCount, actualMetricUnknownContainerCount.GetGauge().GetValue()) // assert for running pod count actualMetricRunningPodCount := &dto.Metric{} metrics.RunningPodCount.Write(actualMetricRunningPodCount) expectedMetricRunningPodCount := float64(2) assert.Equal(t, expectedMetricRunningPodCount, actualMetricRunningPodCount.GetGauge().GetValue()) } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-3f173d1022a4408031efac17c8299f04d835794ab8a77d69bb7667b0107a08bf", "text": "Some kubelet metrics use non-standard prometheus collectors unnecessarily. Specifically, we have which can be simple gauges. Since we cannot migrate non-standard prometheus collectors using the internal metrics stability framework, we will need to convert these metrics into standard prometheus variants. /sig instrumentation /assign\nGitHub didn't allow me to assign the following users: solodov. Note that only and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : Some kubelet metrics use non-standard prometheus collectors unnecessarily. Specifically, we have which can be simple gauges. Since we cannot migrate non-standard prometheus collectors using the internal metrics stability framework, we will need to convert these metrics into standard prometheus variants. /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\nrecommends that we generate those metrics in the GenericPLEG during the relist. We can generate the data directly from the pods call there ().\nI would be interested to work on this issue if no one else is working on it currently\nGo for it!\n/assign", "commid": "kubernetes_issue_79286", "tokennum": 282}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f8a8e302e4a026e47c36fdce91d3ad335d8e6dc9a8eb510585ee0081875bf364", "query": "ginkgo.By(\"Wait for the node to be ready\") waitForNodeReady() <del> for _, customClass := range []*schedulingv1.PriorityClass{customClassA, customClassB, customClassC} { </del> <ins> customClasses := []*schedulingv1.PriorityClass{customClassA, customClassB, customClassC} for _, customClass := range customClasses { </ins> _, err := f.ClientSet.SchedulingV1().PriorityClasses().Create(context.Background(), customClass, metav1.CreateOptions{}) <del> framework.ExpectNoError(err) </del> <ins> if err != nil && !apierrors.IsAlreadyExists(err) { framework.ExpectNoError(err) } </ins> } <ins> gomega.Eventually(func() error { for _, customClass := range customClasses { _, err := f.ClientSet.SchedulingV1().PriorityClasses().Get(context.Background(), customClass.Name, metav1.GetOptions{}) if err != nil { return err } } return nil }, priorityClassesCreateTimeout, pollInterval).Should(gomega.BeNil()) </ins> }) ginkgo.AfterEach(func() {", "positive_passages": [{"docid": "doc-en-kubernetes-bc1f56f76d806f780c64417014c4b072addf1f4df6d254dd55319774f349a24c", "text": "Flaked a couple of times on serial lane with the same error. Test is relatively new. This run only has the single test flake: /sig node /kind flake /cc\n/assign\nNew recent failures: /triage accepted", "commid": "kubernetes_issue_106664", "tokennum": 50}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f8b438deb7fa7722c017632bbde01b3ba0d04ea323fc2e4af096a81de288565b", "query": "n.mu.RLock() defer n.mu.RUnlock() value, ok = n.cache[predicateKey][equivalenceHash] <ins> if ok { metrics.EquivalenceCacheHits.Inc() } else { metrics.EquivalenceCacheMisses.Inc() } </ins> return value, ok }", "positive_passages": [{"docid": "doc-en-kubernetes-aa59e6a5adfc1b233e34e0c1fe9e3a0ec7f2fe6a4636f877a41f4c9aef45f71d", "text": "/kind feature The equivalence cache feature is planned to move to beta in 1.11, and it would be useful to have some metrics attached to it. The equivalence cache should improve scheduling throughput, so we want to be able to correlate e.g. throughput with eCache hit rate. /sig scheduling /sig instrumentation\n/assign misterikkit\nIssues 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\n/remove-lifecycle stale", "commid": "kubernetes_issue_63259", "tokennum": 154}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f8bad76e6eb67ed972dc87604f81ab99a4bcebe934e7e5bad9316d817dfbec77", "query": "import ( \"context\" <ins> \"strings\" </ins> metav1 \"k8s.io/apimachinery/pkg/apis/meta/v1\" utilversion \"k8s.io/apimachinery/pkg/util/version\" \"k8s.io/apiserver/pkg/endpoints/discovery\"", "positive_passages": [{"docid": "doc-en-kubernetes-d1e994e5749edcd07edbd0f19c7df9185dabd2833b25fd1731e4d47ccf8dce07", "text": "<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI --Which jobs are flaking: pull-kubernetes-e2e-gce Which test(s) are flaking: Discovery should validate PreferredVersion for each APIGroup Testgrid link: Reason for failure: The test does not handle API groups which are or removed dynamically during the run of the test. Just because an API group is present in at the beginning of the test does not mean or will be present by the end of the test. This is particularly true for the dynamic/custom-resource API groups registered/unregistered during the e2e test run /sig api-machinery /assign\nmitigation opened at\nSaw this today in It seems to happen relatively often Likely due to the CRD created in: Should the ValidatingAdmissionPolicy test CRD have its group name template changed to match the existing test exclusion for groups ending in /cc", "commid": "kubernetes_issue_93215", "tokennum": 222}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f8d1da8080510cd2186469dff04103556f34aed75d956740330d88ac439e57f5", "query": "mockCadvisor.On(\"VersionInfo\").Return(versionInfo, nil) expectedNode := &api.Node{ <del> ObjectMeta: api.ObjectMeta{Name: \"127.0.0.1\"}, </del> <ins> ObjectMeta: api.ObjectMeta{Name: testKubeletHostname}, </ins> Spec:       api.NodeSpec{}, Status: api.NodeStatus{ Conditions: []api.NodeCondition{", "positive_passages": [{"docid": "doc-en-kubernetes-d16ca614c05197aa8b2652e3bf008c3a9a5ce41d960188a2ba3459b13d8b1102", "text": "Looks like some kubelet unit tests perform a lookupIp which ends up depending on the health of the local resolver. Specifically has this failing: Which leads to the test in: And we recently swapped out the node names from testnode to 127.0.0.1, so probably the culprit?\n/ref\nInteresting. I did swap out the node names in the unit test as part of to be 127.0.0.1, party because I thought that it wouldn't have any problems resolving during unit tests.\n/cc", "commid": "kubernetes_issue_8549", "tokennum": 113}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f8d1da8080510cd2186469dff04103556f34aed75d956740330d88ac439e57f5", "query": "mockCadvisor.On(\"VersionInfo\").Return(versionInfo, nil) expectedNode := &api.Node{ <del> ObjectMeta: api.ObjectMeta{Name: \"127.0.0.1\"}, </del> <ins> ObjectMeta: api.ObjectMeta{Name: testKubeletHostname}, </ins> Spec:       api.NodeSpec{}, Status: api.NodeStatus{ Conditions: []api.NodeCondition{", "positive_passages": [{"docid": "doc-en-kubernetes-4a4c75dd985aaeba56d487bbde17d68f0425afc5d7e1167fdf1a1abcb97cd0b6", "text": "cc\nWhat is the environment where you are running the tests? They pass for me on my mac, a linux box, and shippable seems to be passing them as well.\nI couldn 't reproduce the failure either.\nI'm out right now; i'll try them when i get back. For the record, I run hack/test- Paul Morie wrote:\nAhem FTR This acronym is going to go quad-plat Paul Morie wrote:\nI ran on both platforms and saw the tests pass.\nI'm still seeing it. Won't have bandwidth to dig in personally until tomorrow.\nseeing a similar failure after a git pull\nI knew I wasn't crazy\nenvironment: fedora 21, golang: 1.4, docker: 1.6\nI think I see the problem. When I set the node name to in the test I was assuming it would parse as a valid ip address and not end up at the LookupIP call. But only the node name (and not the kubelet hostname) is being set (except in my new test where I ) so it's trying to do a lookup. Do you think you could test just changing the default hostname from \"testnode\" to \"127.0.0.1\" and see if that fixes it for you?\nTrying now\nI still get failures but no panic / threaddump.\ngist coming\nthis looks like again?\nGood that it isn't panicing any longer. I can dig into the test failures tomorrow (I think it should be relatively simple to resolve).\ncool, thanks for looking\nPasses in master now for me. Closing.\nFYI, they will break again once goes in, and then we can merge my PR to see if that fixes it for you.\n:+1:\nis in -- are these tests breaking again?\nI just rebased which I think will fix them.\nThey are breaking again.\nis on it.", "commid": "kubernetes_issue_8522", "tokennum": 407}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f8f2cd9db5113e76efd6fbbc0b5f47b04c8a6a37531996c6417011bfdb2322c8", "query": "func TestVersion(t *testing.T) { fakeRuntime, endpoint := createAndStartFakeRemoteRuntime(t) <del> defer fakeRuntime.Stop() </del> <ins> defer func() { fakeRuntime.Stop() // clear endpoint file if addr, _, err := util.GetAddressAndDialer(endpoint); err == nil { if _, err := os.Stat(addr); err == nil { os.Remove(addr) } } }() </ins> r := createRemoteRuntimeService(endpoint, t) version, err := r.Version(apitest.FakeVersion)", "positive_passages": [{"docid": "doc-en-kubernetes-a55cc9cf23a1aa66af6ba96638da8c1361b9b34938bf9fbe2ee98dcb858f1383", "text": "Which jobs are flaking: periodics-kubernetes-bazel-test Which test(s) are flaking: //pkg/kubelet/cri/remote TestVersion Testgrid link: Reason for failure: Error: Received unexpected error: rpc error: code = Unavailable desc = transport is closing panic: runtime error: invalid memory address or nil pointer dereference [recovered] panic: runtime error: invalid memory address or nil pointer dereference Anything else we need to know: To reproduce with stress: go test -race -c ./pkg/kubelet/cri/remote stress - TestVersion Detailed logs\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig testing\nI 'll give it a see and fix it :)\n/assign\n/remove-sig testing SIG node owns their unit tests. SIG testing owns the framework, infrastructure, etc.\n/sig node", "commid": "kubernetes_issue_96950", "tokennum": 277}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f9092873f54c1ef07c56a1364024bc84dfd5c8f62ea70ed79349cf7eba056d37", "query": "\"testing\" \"time\" <ins> dto \"github.com/prometheus/client_model/go\" </ins> \"github.com/stretchr/testify/assert\" \"k8s.io/apimachinery/pkg/types\" \"k8s.io/apimachinery/pkg/util/clock\" \"k8s.io/apimachinery/pkg/util/diff\" kubecontainer \"k8s.io/kubernetes/pkg/kubelet/container\" containertest \"k8s.io/kubernetes/pkg/kubelet/container/testing\" <ins> \"k8s.io/kubernetes/pkg/kubelet/metrics\" </ins> ) const (", "positive_passages": [{"docid": "doc-en-kubernetes-3f173d1022a4408031efac17c8299f04d835794ab8a77d69bb7667b0107a08bf", "text": "Some kubelet metrics use non-standard prometheus collectors unnecessarily. Specifically, we have which can be simple gauges. Since we cannot migrate non-standard prometheus collectors using the internal metrics stability framework, we will need to convert these metrics into standard prometheus variants. /sig instrumentation /assign\nGitHub didn't allow me to assign the following users: solodov. Note that only and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : Some kubelet metrics use non-standard prometheus collectors unnecessarily. Specifically, we have which can be simple gauges. Since we cannot migrate non-standard prometheus collectors using the internal metrics stability framework, we will need to convert these metrics into standard prometheus variants. /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\nrecommends that we generate those metrics in the GenericPLEG during the relist. We can generate the data directly from the pods call there ().\nI would be interested to work on this issue if no one else is working on it currently\nGo for it!\n/assign", "commid": "kubernetes_issue_79286", "tokennum": 282}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f9167060562ca9418529f280bee20408d287e8a054460e56b0416620ec384bc9", "query": "if config.EnableContentionProfiling { goruntime.SetBlockProfileRate(1) } <ins> routes.DebugFlags{}.Install(pathRecorderMux, \"v\", routes.StringFlagPutHandler(logs.GlogSetter)) </ins> } return pathRecorderMux }", "positive_passages": [{"docid": "doc-en-kubernetes-1ae4374d89f67ace7ae0a669d00ed1569d20a542da5564faf73570670010978e", "text": "What would you like to be : Support dynamically set log level for kube-scheduler, is blocked on node controller approval, but we can move forward with a scheduler only change. /sig scheduling\n/help\n/assign /remove-help\ndo you have a PR for this one?\nI submitted the PR.", "commid": "kubernetes_issue_83783", "tokennum": 65}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f9316cbf3446c7bc3d1fdcf8342fb3f479b00049c0d1c6f0eae0e1a94933dd15", "query": "\"k8s.io/client-go/restmapper\" \"k8s.io/component-base/featuregate\" featuregatetesting \"k8s.io/component-base/featuregate/testing\" <ins> \"k8s.io/component-base/metrics/legacyregistry\" </ins> \"k8s.io/klog/v2\" \"k8s.io/kubernetes/test/integration/framework\" testutils \"k8s.io/kubernetes/test/utils\"", "positive_passages": [{"docid": "doc-en-kubernetes-43f40e78041c5b4f7b71fe448bfb25306103aa8e8278b5a81de2f92cd8b688c4", "text": "In the new scheduler performance testing framework, (bool) is provided to benchmark performance of pods created in an \"operator\": (L11 below) However, the initialized Pods created in L5~L7 seem to be also benchmarked, although it doesn't specify . (please see the reproduce steps below). I think it's b/c once scheduler starts, the associated Prometheus artifacts are also up, and it's a single in-memory datastore. So no matter we start to collect the metric in which step, the prometheus data is already up-to-date. In the above workload config, the final data have benchmarked 1500 pods instead of 1000 pods. I guess it won't work either if running in the pod initialization step or not. Unless we manage a breakpoint at the end of each step, and calculate delta histogram for the step that specifies . Pods created in step without are not benchmarked. Apply the following diff: And then run: You will get an output sth. like: /sig scheduling\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nCould you please help confirm if it's an issue?\ncc\nUnfortunately, does not apply for metrics gathered from . As you mentioned. The default gatherer collects all metrics produced by the scheduler. It's the scheduler itself who knows pod specs and would have to decide which pods will get ignored when updating metrics. The question is if computing metrics for a subset of pods processed by the scheduler is a valid use case.\nThis is probably what we want. Is something like that possible ?\nI think being able to absolutely ignore certain pods for metrics is an overkill.\nThe use case is to ignore the pods created in steps that don't specify , so as to collect the Pod metrics create at particular step(s) (). Otherwise, the semantics of option is quite misleading. Nope, that's not the intention. We don't need to target certain pods, like using label selector or whatever. Just as I mentioned, measure pods created at particular steps.", "commid": "kubernetes_issue_99218", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f9316cbf3446c7bc3d1fdcf8342fb3f479b00049c0d1c6f0eae0e1a94933dd15", "query": "\"k8s.io/client-go/restmapper\" \"k8s.io/component-base/featuregate\" featuregatetesting \"k8s.io/component-base/featuregate/testing\" <ins> \"k8s.io/component-base/metrics/legacyregistry\" </ins> \"k8s.io/klog/v2\" \"k8s.io/kubernetes/test/integration/framework\" testutils \"k8s.io/kubernetes/test/utils\"", "positive_passages": [{"docid": "doc-en-kubernetes-a8b513dba6e655a29138693e1746ea6f16e628420cb4b4aca138e84f0ed453fc", "text": "I would do something like the following: if a step has collectMetrics:false, we wait for them to finish scheduling, and then we take a snapshot of the histogram. Then for the next step that has collectMetrics:true, we take the diff with the latest snapshot to report the results. This might not be perfect, as we don't control if the metrics have finished syncing when we take the snapshot. But I think that's fine. Would doing this be possible? Now, if we have steps that run in parallel, one with collectMetrics:false and another with collectMetrics:true, then this doesn't work. Note that I don't know the details of how the gatherer works.\nThat adheres to what I have in my mind - we can only manage this on client side. I think it's fine. As we are already fetching the \"snapshot\" when pods get scheduled when equals true. True. An alternative is to design the case to be like: the step with to employ Pods that are all unschedulable, and then specify a custom metric \"schedulere2eschedulingdurationseconds[result=\"unschedulable\"]\" to target a particular histogram instead of all histograms (default option) inside a histogramVec. Note this can only be possible when and some subsequent changes get in place.\nWe might just call Histogram.Clear() method which will clear what has been collected so far at the end of phase: Assuming individual phases have no pods in common and each phase can clear metrics without affecting other phases. Though, as said, it will work only for serial case.\nWDYT\nI'm afraid doesn't work. That was my initial thought as well, but no luck. I guess it's b/c, theoretically, we cannot reset a metric on the server side - Promoetheus' model doesn't support this. But let me know if I miss anything.\nThe performance tests assume all the metrics all gathered and accessed in the same binary. As long as that's the case, works.", "commid": "kubernetes_issue_99218", "tokennum": 457}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f9316cbf3446c7bc3d1fdcf8342fb3f479b00049c0d1c6f0eae0e1a94933dd15", "query": "\"k8s.io/client-go/restmapper\" \"k8s.io/component-base/featuregate\" featuregatetesting \"k8s.io/component-base/featuregate/testing\" <ins> \"k8s.io/component-base/metrics/legacyregistry\" </ins> \"k8s.io/klog/v2\" \"k8s.io/kubernetes/test/integration/framework\" testutils \"k8s.io/kubernetes/test/utils\"", "positive_passages": [{"docid": "doc-en-kubernetes-c977cd9286b4a197ec98b02fe65342de07359c1835b69599916b95554e8a5e53", "text": "We already call in the code:\nThat was my understanding as well, but no luck :( Here is a diff to call in case when \"concreteOp.CollectMetrics\" is false: <details<summaryDiff:</summary<p</p</detailsAnd below is the output - it's still 1500 (500 init pods plus 1000 measured pods) instead of 1000 being benchmarked: <details<summaryOutput:</summary<p</p</details\nAlso, if you run the tests and together, the result proves doesn't work as expected:\nBut I do find a way to fix this: .", "commid": "kubernetes_issue_99218", "tokennum": 136}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f9b58627dfa0a3ab8c41f1728ed5adccb967351e35c9a897e7eab0ff5c0f0dce", "query": "allErrs = append(allErrs, field.Invalid(fldPath.Child(\"type\"), s.Type, \"must be object at the root\")) } <ins> // restrict metadata schemas to name and generateName only if metadata, found := s.Properties[\"metadata\"]; found && lvl == rootLevel { // metadata is a shallow copy. We can mutate it. _, foundName := metadata.Properties[\"name\"] _, foundGenerateName := metadata.Properties[\"generateName\"] if foundName && foundGenerateName && len(metadata.Properties) == 2 { metadata.Properties = nil } else if (foundName || foundGenerateName) && len(metadata.Properties) == 1 { metadata.Properties = nil } metadata.Type = \"\" if metadata.ValueValidation == nil { metadata.ValueValidation = &ValueValidation{} } if !reflect.DeepEqual(metadata, Structural{ValueValidation: &ValueValidation{}}) { // TODO: this is actually a field.Invalid error, but we cannot do JSON serialization of metadata here to get a proper message allErrs = append(allErrs, field.Forbidden(fldPath.Child(\"properties\").Key(\"metadata\"), \"must not specify anything other than name and generateName, but metadata is implicitly specified\")) } } </ins> if s.XEmbeddedResource && !s.XPreserveUnknownFields && s.Properties == nil { allErrs = append(allErrs, field.Required(fldPath.Child(\"properties\"), \"must not be empty if x-kubernetes-embedded-resource is true without x-kubernetes-preserve-unknown-fields\")) }", "positive_passages": [{"docid": "doc-en-kubernetes-4be11de3bdb9e2a86ad3a19c4d6f5342db422d48e5979c118fca9ce077f64900", "text": "We allow CRD authors to write . Currently we don't restrict writing validation for , which means people can have . For example, people can have additive name constraints (require CR to be ) with the following schema: This brings us two questions: do we if \"metadata\" is included in the schema: simplest option is to publish standard metav1.ObjectMeta schema info, and use any CRD-specified \"metadata\" properties as additive validation (just like in-tree types do, publishing standard ObjectMeta schema info, and implementing type-specific name validation internally) alternatively, we can try merging user-specified metadata schema with the standard one. Technically people should only add extra validation to existing metadata properties (adding new fields to metadata won't work since they will be pruned by built-in validation first), but it's unclear to me how arbitrary people may want the metadata validation to be term question is whether to allow people specifying metadata validation at all, or just allow a subset (like name validation) in CRD v1 /sig api-machinery /area custom-resources cc\nWhat is the difference between these two? I mean the end result is the same right? The only thing that can be is validation. Nothing else works unless you are considering extensions?\nThe former means we drop/hide user-specified metadata schema when we publish CRD OpenAPI. We still validate user-specified constraints on server side, but client-side validation won't see them. The latter enables client-side user-specified metadata validation.\nIf it's possible to merge with standard metadata schema info, or at the cost of not publishing the standard schema. My inclination would be to publish the complete standard schema for metadata/apiVersion/kind, which we know is complete and accurate, and use and user-specified schema for those fields as addition validations server side", "commid": "kubernetes_issue_74620", "tokennum": 396}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f9b69c967ae0669bdad7480ada8ba77cbc709f187f424322518bf320f8c9a115", "query": "// cleanupPodsInNamespace deletes the pods in the given namespace and waits for them to // be actually deleted. func cleanupPodsInNamespace(cs clientset.Interface, t *testing.T, ns string) { <del> if err := cs.CoreV1().Pods(ns).DeleteCollection(context.TODO(), *metav1.NewDeleteOptions(0), metav1.ListOptions{}); err != nil { </del> <ins> if err := cs.CoreV1().Pods(ns).DeleteCollection(context.TODO(), metav1.DeleteOptions{}, metav1.ListOptions{}); err != nil { </ins> t.Errorf(\"error while listing pod in namespace %v: %v\", ns, err) return }", "positive_passages": [{"docid": "doc-en-kubernetes-0c3eca7956c73a24f455c71a58b712ce183e874d4a3e3eb9b913120c8a8ac10c", "text": "<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: Conformance - GCE - master (ci-kubernetes-gce-conformance-latest) Which test(s) are failing: [sig-scheduling] SchedulerPreemption [Serial] PreemptionExecutionPath runs ReplicaSets to verify preemption running path [Conformance]Changes Since when has it been failing: 2020-06-08 22:27 PDT Testgrid link: Reason for failure: Regression by Anything else we need to know: /sig scheduling /priority critical-urgent\ncc/ /assign", "commid": "kubernetes_issue_91972", "tokennum": 148}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f9cbc29abc0eac857048d407a3e88b27c1b988cf440d601d7c88f1245cef7c9f", "query": "} // Walks through the plugin directory discover any existing plugin sockets. <ins> // Goroutines started here will be waited for in Stop() before cleaning up. // Ignore all errors except root dir not being walkable </ins> func (w *Watcher) traversePluginDir(dir string) error { return w.fs.Walk(dir, func(path string, info os.FileInfo, err error) error { if err != nil { <del> return fmt.Errorf(\"error accessing path: %s error: %v\", path, err) </del> <ins> if path == dir { return fmt.Errorf(\"error accessing path: %s error: %v\", path, err) } glog.Errorf(\"error accessing path: %s error: %v\", path, err) return nil </ins> } switch mode := info.Mode(); {", "positive_passages": [{"docid": "doc-en-kubernetes-6f8ca0211eec05ccf55bb519cf8df0569345414eb205c19a4215b8fda8e40904", "text": "<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: https://k8s- Which test(s) are failing: should unmount if pod is force deleted while kubelet is down [Disruptive][Slow] Since when has it been failing: 11/07/18 15:02 Testgrid link: https://k8s- Reason for failure: The test case stops and starts kubelet, and it seems like kubelet is unable to start again Anything else we need to know: <!-- DO NOT EDIT BELOW THIS LINE --/kind failing-test\ncc\nThanks for opening this Looking at , looks like could be the cause? /assign can you please look into this as priority. This is failing critical release blocking tests. /cc /sig cli /priority critical-urgent /milestone v1.13\nIt looks like kubelet keeps restarting. The error right before restarting is:\n/assign\nThis bug could have been exposed by the newly tests in\nHmm, so I see two errors: Which is a Fatal error and would prevent Kubelet from starting anyways. In which case this error is handled correctly by the pluginwatcher, but I'm not sure preventing Kubelet from starting is the desired behavior. Should we log this error and skip it? There also seem to be a cleanup issue here on that file is this expected? This one is clearly a bug and not really handled correctly. It's due to the fact that we encounter an error at start, cleanup but don't wait for the gorountines to finish before cleaning up. I can send in a fix pretty easily for the second issue, basically add a waitgroup in the . For the first error, what do we think is the expected behavior?\nThis was mentioned in as well. /cc\nIs this related to the issue where plugin watcher is recursively scanning for sockets?\nAlso, it should be noted that the path it's erroring on is not a socket type.\nThat's a bit different, as it is intended to scan recursively. Also note that the error here is produced by . What should be our behavior in such a case? Ignore that error?\nI'm not sure if we want to be recursively scanning. The volume directories are mount points, which means there could be lots of files/directories existing in those volumes.", "commid": "kubernetes_issue_70810", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f9cbc29abc0eac857048d407a3e88b27c1b988cf440d601d7c88f1245cef7c9f", "query": "} // Walks through the plugin directory discover any existing plugin sockets. <ins> // Goroutines started here will be waited for in Stop() before cleaning up. // Ignore all errors except root dir not being walkable </ins> func (w *Watcher) traversePluginDir(dir string) error { return w.fs.Walk(dir, func(path string, info os.FileInfo, err error) error { if err != nil { <del> return fmt.Errorf(\"error accessing path: %s error: %v\", path, err) </del> <ins> if path == dir { return fmt.Errorf(\"error accessing path: %s error: %v\", path, err) } glog.Errorf(\"error accessing path: %s error: %v\", path, err) return nil </ins> } switch mode := info.Mode(); {", "positive_passages": [{"docid": "doc-en-kubernetes-5fd14dcabf74b34a3f64d7f7feeb636f4d13fa903d9084a91cc242778a1c3d1e", "text": "maybe we can put a limit on depth of plugin directory for on the same PR:\nIdeally the directory that the plugin sockets are dropped in should be different from the directory where mounts happens. Currently the plugin socket directory is: ) The mounts directory is (so far so good). Problem is the \"global mount\" directory is also :( So options are: recursively scanning like suggested, and say plugins will can only be directly under This will break existing plugins, for example, the GCP plugin is at (see ). recursively scanning but change the plugin socket directory to ? This will also break existing plugins, like the GCP one pointed out above. the plugin dir the same, and leave recursion in, but put a limit on depth of plugin directory as suggested by This is ugly but may be the cleanest solution.\nThis conversation is completely different from the bug surfaced by this issue. Let's move that to the corresponding issue: I have a fix ready to go out for the panic, we should figure out what behavior we expect Kubelet to have when encountering this error from filepath.Walk: Should we ignore it?\nIgnoring the error (with a warning maybe) instead of failing all of kubelet seems reasonable to me. If the plugin did not setup their registration socket correctly, then the end result should be that the plugin fails to register, but all other plugins should continue to work correctly.\nthe latest runs of this job no longer timesout - Instead I am seeing a new CSI related failure Is this expected. Do we want to track that failure in this bug now or do we have a separate issue?\nthe latest test logs indicate some test-infra issue:\nthe same shows up as a timeout on that particular test. Lets wait for the next run. but somehow the timeout seems to have gone. Are we still planning to merge and associated with this issue?\nshould be merged as it fixes a bug. can you help with approval? Thanks!\nare you missing the right PR# in the comment above?\nthis is the correct PR -\n/reopen Keeping it open until we can see the job pass a couple of rounds\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository.", "commid": "kubernetes_issue_70810", "tokennum": 497}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f9cbc29abc0eac857048d407a3e88b27c1b988cf440d601d7c88f1245cef7c9f", "query": "} // Walks through the plugin directory discover any existing plugin sockets. <ins> // Goroutines started here will be waited for in Stop() before cleaning up. // Ignore all errors except root dir not being walkable </ins> func (w *Watcher) traversePluginDir(dir string) error { return w.fs.Walk(dir, func(path string, info os.FileInfo, err error) error { if err != nil { <del> return fmt.Errorf(\"error accessing path: %s error: %v\", path, err) </del> <ins> if path == dir { return fmt.Errorf(\"error accessing path: %s error: %v\", path, err) } glog.Errorf(\"error accessing path: %s error: %v\", path, err) return nil </ins> } switch mode := info.Mode(); {", "positive_passages": [{"docid": "doc-en-kubernetes-7a1e75b2dd238a9264dd7ee20adbbea7f5a6949137fb440b1e66e3d97a7ebee9", "text": "</details\nI see just one CSI test timing out in serial job Is that something the fixes here attempted to resolve? if not I can open a new issue if it persists and close this one out. Thanks.\nThe test mentioned in my comment above was a flake.. closing this issue now. will open a new issue for the flake\nI'm getting the following related error on a busy Node: In the above case it's a full filesystem, but I imagine the same error would pop up with a RO filesystem as well. Looking at the patch, I'd expect kubelet would still be failing to start when it tries to watch it. (above was from a v1.12.3 cluster) , what do you reckon?\nplugin watcher fixes for 1.12 are expected to be released with 1.12.5:\n, I understand that I'm missing that patch. The patch code, however, would not make a difference in this case, if I read it correctly. It would not prevent the recursive dive into mounted volumes, as the errors happening at the deeper levels of that dive.\nThe patch blacklists the plugin watcher from searching the directory\nOK, I was looking at the wrong patch after all (). Thanks for the clarifications.", "commid": "kubernetes_issue_70810", "tokennum": 274}], "negative_passages": []}
{"query_id": "q-en-kubernetes-f9d415b1c25fa210512361ca3c7472740259055a5750ebed78f838d7a742b003", "query": "} return nil }, <ins> // MinionList.Items had a wrong name in v1beta1 func(in *MinionList, out *v1beta1.MinionList) error { Convert(&in.JSONBase, &out.JSONBase) Convert(&in.Items, &out.Items) out.Minions = out.Items return nil }, func(in *v1beta1.MinionList, out *MinionList) error { Convert(&in.JSONBase, &out.JSONBase) if len(in.Items) == 0 { Convert(&in.Minions, &out.Items) } else { Convert(&in.Items, &out.Items) } return nil }, </ins> ) }", "positive_passages": [{"docid": "doc-en-kubernetes-a574ac2a261fa7b4cd59d0907178e287efcaa3989e734104cb2eecf5d89ff460", "text": "should have the JSON attribute name \"items\", not \"minions\"\nDoh! Fix now and break clients?\nDefine Items and Minions and use Convertors to resolve it?\nSure. I'll make a fix.", "commid": "kubernetes_issue_1101", "tokennum": 45}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fa09ab41b5e12bb6bc8ee74665b9e578edcbfc2894e7a160da324531e4b96bc7", "query": "\"k8s.io/kubernetes/pkg/kubelet/network\" proberesults \"k8s.io/kubernetes/pkg/kubelet/prober/results\" kubetypes \"k8s.io/kubernetes/pkg/kubelet/types\" <del> \"k8s.io/kubernetes/pkg/kubelet/util/cache\" </del> \"k8s.io/kubernetes/pkg/types\" \"k8s.io/kubernetes/pkg/util/flowcontrol\" \"k8s.io/kubernetes/pkg/util/oom\"", "positive_passages": [{"docid": "doc-en-kubernetes-c9313de66f3508f8886cd07268b253d5e2cfa321359afb89838b6984a0afe883", "text": "The recently merged PR a version cache in dockertools, which makes the test  flaky. The reason is that injected error into fakedockerclient and then expected to see the error from right after that (See ). However, the error was consumed by the goroutine which periodically updates the version cache (See ). The docker daemon version is rarely updated, and we only need version once for each container creating, during which we also do container create, start, inspect #etc. 1) Do we care about the cost of the call so much that we have to introduce the complexity? 2) Kubelet periodically calls , can we rely on that to update the cache? Anyhow, at least, we should disable the cache or have a fake one in the unit test. :) /cc\nI once considered move this cache to runtime level, while thus may need to change runtime interface. What if only cache apiversion?\nWe can only get via , so there will still be the data race. :) One option is to update the version cache in , now kubelet periodically call to check the runtime status. Another better option is to cache the version in layer, now is under our control, we can refactor it with an additional argument indicating whether to use cached value or get directly from the daemon. If we cache the version only for performance, I prefer the second option which is cleaner and more efficient. :)\nOK, will look into this tonight\nThe unit test itself should not start a goroutine to update the cache (unless you're actually testing the goroutine). We should disable it anyway, as we often do in our unit tests. It also sounds like we don't need a goroutine dedicated for this. If we can tolerate the additional overhead from time to time, we can set a expiration time (e.g., 1 minute), and only call the runtime if the entry expires.\nTotally agree. :) Maybe a new function in wrapping the update logic, or wrapping the logic in the .\nexpiration time sounds good in this case\nThis is happening quite frequently - increasing priority to P0.", "commid": "kubernetes_issue_24298", "tokennum": 452}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fa4c420c42221a713697c9022bbe57fca63d1ed29681f6d16276bee34b127686", "query": "<del> ##### Deprecation Notice: This directory has entered maintenance mode and will not be accepting new providers. Cloud Providers in this directory will continue to be actively developed or maintained and supported at their current level of support as a longer-term solution evolves. ## Overview: </del> <ins> ##### Deprecation Notice: cloud providers in this directory are deprecated and will be removed in favor of external (a.k.a out-of-tree) providers. Existing providers in this directory (a.k.a in-tree providers) should only make small incremental changes as needed and avoid large refactors or new features. New providers seeking to support Kubernetes should follow the out-of-tree model as specified in the [Running Kubernetes Cloud Controller Manager docs](https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/). For more information on the future of Kubernetes cloud providers see [KEP-0002](https://github.com/kubernetes/community/blob/master/keps/sig-cloud-provider/0002-cloud-controller-manager.md) and [KEP-0013](https://github.com/kubernetes/community/blob/master/keps/sig-cloud-provider/0013-build-deploy-ccm.md). Cloud Providers in this directory will continue to be actively developed or maintained and supported at their current level of support as a longer-term solution evolves. ## Overview: </ins> The mechanism for supporting cloud providers is currently in transition:  the original method of implementing cloud provider-specific functionality within the main kubernetes tree (here) is no longer advised; however, the proposed solution is still in development. <del> #### Guidance for potential cloud providers: * Support for cloud providers is currently in a state of flux. Background information on motivation and the proposal for improving is in the github [proposal](https://git.k8s.io/community/contributors/design-proposals/cloud-provider/cloud-provider-refactoring.md). * In support of this plan, a new cloud-controller-manager binary was added in 1.6. This was the first of several steps (see the proposal for more information). * Attempts to contribute new cloud providers or (to a lesser extent) persistent volumes to the core repo will likely meet with some pushback from reviewers/approvers. * It is understood that this is an unfortunate situation in which 'the old way is no longer supported but the new way is not ready yet', but the initial path is unsustainable, and contributors are encouraged to participate in the implementation of the proposed long-term solution, as there is risk that PRs for new cloud providers here will not be approved. * Though the fully productized support envisioned in the proposal is still 2 - 3 releases out, the foundational work is underway, and a motivated cloud provider could accomplish the work in a forward-looking way. Contributors are encouraged to assist with the implementation of the design outlined in the proposal. #### Some additional context on status / direction: </del> <ins> #### Guidance for potential cloud providers: * Support for cloud providers is currently in a state of flux. Background information on motivation and the proposal for improving is in the github [proposal](https://git.k8s.io/community/contributors/design-proposals/cloud-provider/cloud-provider-refactoring.md). * In support of this plan, a new cloud-controller-manager binary was added in 1.6. This was the first of several steps (see the proposal for more information). * Attempts to contribute new cloud providers or (to a lesser extent) persistent volumes to the core repo will likely meet with some pushback from reviewers/approvers. * It is understood that this is an unfortunate situation in which 'the old way is no longer supported but the new way is not ready yet', but the initial path is unsustainable, and contributors are encouraged to participate in the implementation of the proposed long-term solution, as there is risk that PRs for new cloud providers here will not be approved. * Though the fully productized support envisioned in the proposal is still 2 - 3 releases out, the foundational work is underway, and a motivated cloud provider could accomplish the work in a forward-looking way. Contributors are encouraged to assist with the implementation of the design outlined in the proposal. #### Some additional context on status / direction: </ins> * 1.6 added a new cloud-controller-manager binary that may be used for testing the new out-of-core cloudprovider flow. * Setting cloud-provider=external allows for creation of a separate controller-manager binary <del> * 1.7 adds [extensible admission control](https://git.k8s.io/community/contributors/design-proposals/api-machinery/admission_control_extension.md), further enabling topology customization. </del> <ins> * 1.7 adds [extensible admission control](https://git.k8s.io/community/contributors/design-proposals/api-machinery/admission_control_extension.md), further enabling topology customization. </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-d011033a8c2d848ce3561906ba09865c53f3ece940f2eb809bc8d8929df344ea", "text": "The needs updating to be in line with community agreed trajectory for the movement of cloud provider code out of k/k. For example the current statement: This statement is approximately 16 months old and implies there is still ambiguity, where there is now a much more clear plan which should be clearly communicated to those who might waste their time investing work in modifying something in this directory. The situation is one increasingly past maintenance mode, with out-of-tree implementations the goal in the 1.13 cycle followed by removal of in-tree provider code a few cycles later. See also discussion on slack: /kind cleanup /priority important-soon /sig cloud-provider /assign\nThanks for the reminder Tim, sorry this fell off my radar, will put together a PR today :)\nIssues 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\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten Need to update the README again to link out to the enhancement issues per cloud provider.\nPTAL :)\nawesome\nIssues 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\n/close\nClosing 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", "commid": "kubernetes_issue_68234", "tokennum": 445}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fa50d510924add1ed53eff584fc3722e8a4b3052b0e2c25e42d658fb17fd6d1d", "query": "// Sleep 1s to verify no detach are triggered after second pod is added in the future. time.Sleep(1000 * time.Millisecond) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <del> verifyVolumeNoStatusUpdateNeeded(t, logger, generatedVolumeName, nodeName1, asw) </del> <ins> // verifyVolumeNoStatusUpdateNeeded(t, logger, generatedVolumeName, nodeName1, asw) </ins> // Add a third pod which tries to attach the volume to a different node. // At this point, volume is still attached to first node. There are no status update for both nodes.", "positive_passages": [{"docid": "doc-en-kubernetes-dc8aac09a0e4bb26f9dc5f50aef7f845ea9d7c4b925d34b9f6eda044925f80f5", "text": "TestRunOneVolumeDetachFailNodeWithReadWriteOnce 4 times since 03-19 23:00 PDT, intermittently ! https://k8s- Still investigating whether this is a tolerable flake or not with more history than testgrid view, or otherwise would appreciate input from anyone with expertise in this test, especially as regards to whether this should be a blocker for tomorrows beta cut. maybe: /sig storage /sig testing\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nis already open for this, looks like it is attempting to fix it\nthank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. /close\nClosing this issue. <detailsIn response to : thank you!!! closing this in favor of that one, which I also to our CI signal project board for visibility. For completeness: since it's a longer standing issue, well identified as a flake and not a failure and also actively in progress, NOT considering it a blocker for the go/nogo signal for the beta tomorrow. 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", "commid": "kubernetes_issue_116774", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fa50d510924add1ed53eff584fc3722e8a4b3052b0e2c25e42d658fb17fd6d1d", "query": "// Sleep 1s to verify no detach are triggered after second pod is added in the future. time.Sleep(1000 * time.Millisecond) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <del> verifyVolumeNoStatusUpdateNeeded(t, logger, generatedVolumeName, nodeName1, asw) </del> <ins> // verifyVolumeNoStatusUpdateNeeded(t, logger, generatedVolumeName, nodeName1, asw) </ins> // Add a third pod which tries to attach the volume to a different node. // At this point, volume is still attached to first node. There are no status update for both nodes.", "positive_passages": [{"docid": "doc-en-kubernetes-aef7ec00dc93616f97177ca3d23f28217445848b34c429e5746962ea28329f43", "text": "pull-kubernetes-unit TestRunOneVolumeDetachFailNodeWithReadWriteOnce Jan 7th, 2022 Check volume <fake-plugin/volume-nameis reported as attached to node <fail-detach-node, got false, expected true No response_ /sig storage\n/cc\nthis is the top unit test flake according to\ncc\nThe 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]:\nI think this test is no longer flaky by checking the test grid, close it now.\nUnfortunately this does still seem to be flaky: Here was the output from : /reopen\nReopened this issue. <detailsIn response to : Unfortunately this does still seem to be flaky: 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\n/remove-lifecycle stale\nstill the case\nHow about adding some logging to help troubleshoot this? I looked at it a little, but it is hard to tell which part of the test is failing. PR\n/\nThis is still happening\n/triage accepted\nFrom the logs, in the OneVolumeDetachFailNodeWithReadWriteOnce test, succeeded, but the next verification failed. In verifyVolumeAttachedToNode, the attachState is from calling and within asw, it calls . In verifyVolumeReportedAsAttachedToNode, the volumes are obtained from calling , it seems that the node is not in asw.nodesToUpdateStatusFor at this step. Cannot reproduce locally. I tried to run the test 100 times locally with debug.Stack()... 3 * 100 times all passed.\nTried to run stress test on my linux machine as well but still cannot reproduce. Command: Result: Also tried running n process in parallel. Command: Result:\nIt seems like it happens more frequently.", "commid": "kubernetes_issue_107414", "tokennum": 526}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fa50d510924add1ed53eff584fc3722e8a4b3052b0e2c25e42d658fb17fd6d1d", "query": "// Sleep 1s to verify no detach are triggered after second pod is added in the future. time.Sleep(1000 * time.Millisecond) verifyVolumeAttachedToNode(t, generatedVolumeName, nodeName1, cache.AttachStateAttached, asw) <del> verifyVolumeNoStatusUpdateNeeded(t, logger, generatedVolumeName, nodeName1, asw) </del> <ins> // verifyVolumeNoStatusUpdateNeeded(t, logger, generatedVolumeName, nodeName1, asw) </ins> // Add a third pod which tries to attach the volume to a different node. // At this point, volume is still attached to first node. There are no status update for both nodes.", "positive_passages": [{"docid": "doc-en-kubernetes-62e47fd83b7fc1cc39259be1688a9f133b9cd2dc48247eb5d858fae7fd13955b", "text": "But I may have no time to dig into the cause. Let's see.\ncc as the test author.\nThe problem is that this test has a lot of dependency on the sleeps that are hardcoded with a very narrow scope, but our CI seems to be able to stress it much more. As soon as you slightly change one of the sleep duration it starts to flake locally The test can not make an assumption that timing is perfect, even more in the sub second range can someone in sig-storage review this test and make it less dependant on those tight sleeps?\nAccording to most failures, it failed at Line 660. Let me run some stress locally. with 250ms sleep with 100ms sleep\nI agree this test case is too brittle due to its specific timing dependencies. To fix this, I suggest reworking the test case to: 1) Add retry with timeout to wait for final conditions 2) Remove the intermediate timing-based state transition checks. Instead, we can keep track of state transitions in the Fakes and validate those stats. wdyt?\nFriendly ping from 1.27 CI Signal that this test is still a noisy flake on the master-blocking dashboard as CI Signal has flagged it in and", "commid": "kubernetes_issue_107414", "tokennum": 253}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fa6c3b2574294352298d01d63385cc37ed2abba4723d80cefd0769a4f955f99f", "query": "How To Run ------ <del> ``` cd kubernetes/test/integration/scheduler_perf </del> <ins> ```shell # In Kubernetes root path make generated_files cd test/integration/scheduler_perf </ins> ./test-performance.sh ```", "positive_passages": [{"docid": "doc-en-kubernetes-251eef963dff19e63098abde61cb32ad4061447eb4b1f67f70c9d3499d1dc77d", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Scheduler performance test does not work: What you expected to happen: How to reproduce it (as minimally and precisely as possible): Run schedulerperf by following: Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration**: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\n/assign\n/sig scheduling", "commid": "kubernetes_issue_51090", "tokennum": 141}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fa8124a3bea0a8a72cbbd9c1a7ea2aec1fbb0cb525fa94b09bba67813b09cb22", "query": "cniArch          = \"amd64\" cniDirectory     = \"cni/bin\" // The CNI tarball places binaries under directory under \"cni/bin\". cniConfDirectory = \"cni/net.d\" <del> cniURL           = \"https://storage.googleapis.com/kubernetes-release/network-plugins/cni-plugins-\" + cniArch + \"-\" + cniVersion + \".tgz\" </del> <ins> cniURL           = \"https://dl.k8s.io/network-plugins/cni-plugins-\" + cniArch + \"-\" + cniVersion + \".tgz\" </ins> ) const cniConfig = `{", "positive_passages": [{"docid": "doc-en-kubernetes-af2890d14d0991d34b559e2e2a7effc23a0b7cafb90e6ce93894f3fac456697c", "text": "We have a new vanity url, , which redirects to the GCS release bucket - e.g. Right now, the https endpoint doesn't work, since isn't in the list of domains on the certificate. Once it works, we should switch all references over to the nicer vanity URL. x-ref\nSo what it required to make this issues actionable? Where to add this for the certificate?\nthe issue tracking that is\nThis needs to be triaged as a release-blocker or not for 1.5\nnot a release blocker.\nIs it appropriate to move this to the next milestone or clear the 1.5 milestone? (and remove the non-release-blocker tag as well)\ncan this be closed?\nI forgot to get to this in 1.6, but it'd still be good to do.\ndo you want this in v1.7? is there a sig to own this?\ndoesn't need to block 1.7, no.\nThere are no sig labels on this issue. Please by:<br(1) mentioning a sig: <br(2) specifying the label manually: <br<brNote: method (1) will trigger a notification to the team. You can find the team list .\n/sig release", "commid": "kubernetes_issue_33726", "tokennum": 270}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fa8ef9f34c29137e79fd04fbbda414424bbc054b4d1e77b0b32589f4ef5a8da1", "query": "func TestSyncReplicationControllerCreates(t *testing.T) { c := clientset.NewForConfigOrDie(&restclient.Config{Host: \"\", ContentConfig: restclient.ContentConfig{GroupVersion: &api.Registry.GroupOrDie(v1.GroupName).GroupVersion}}) <del> manager, _, rcInformer := newReplicationManagerFromClient(c, BurstReplicas) </del> <ins> manager, podInformer, rcInformer := newReplicationManagerFromClient(c, BurstReplicas) </ins> <del> // A controller with 2 replicas and no pods in the store, 2 creates expected </del> <ins> // A controller with 2 replicas and no active pods in the store. // Inactive pods should be ignored. 2 creates expected. </ins> rc := newReplicationController(2) rcInformer.Informer().GetIndexer().Add(rc) <ins> failedPod := newPod(\"failed-pod\", rc, v1.PodFailed, nil, true) deletedPod := newPod(\"deleted-pod\", rc, v1.PodRunning, nil, true) deletedPod.DeletionTimestamp = &metav1.Time{Time: time.Now()} podInformer.Informer().GetIndexer().Add(failedPod) podInformer.Informer().GetIndexer().Add(deletedPod) </ins> fakePodControl := controller.FakePodControl{} manager.podControl = &fakePodControl", "positive_passages": [{"docid": "doc-en-kubernetes-38d52777560a5c6fb71d98b8b0953e61c4be2731ef4a377191b06cc53fcf6655", "text": "https://k8s- Failed: [] Network Partition [Disruptive] [Slow] [] [ReplicationController] should eagerly create replacement pod during network partition when termination grace is non-zero {Kubernetes e2e suite}\nhttps://k8s- seems to be the first failure here. It seems to have gone in with a bunch of RC/RS changes () cc/", "commid": "kubernetes_issue_37479", "tokennum": 88}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fa91c274be48353536b59a6844c80620f2da4bdf37336c477935f11b860bb98a", "query": "} // TODO: switch this to full namespacers <del> type rsListFunc func(string, metav1.ListOptions) ([]*extensions.ReplicaSet, error) </del> <ins> type RsListFunc func(string, metav1.ListOptions) ([]*extensions.ReplicaSet, error) </ins> type podListFunc func(string, metav1.ListOptions) (*v1.PodList, error) // ListReplicaSets returns a slice of RSes the given deployment targets. // Note that this does NOT attempt to reconcile ControllerRef (adopt/orphan), // because only the controller itself should do that. // However, it does filter out anything whose ControllerRef doesn't match. <del> func ListReplicaSets(deployment *extensions.Deployment, getRSList rsListFunc) ([]*extensions.ReplicaSet, error) { </del> <ins> func ListReplicaSets(deployment *extensions.Deployment, getRSList RsListFunc) ([]*extensions.ReplicaSet, error) { </ins> // TODO: Right now we list replica sets by their labels. We should list them by selector, i.e. the replica set's selector //       should be a superset of the deployment's selector, see https://github.com/kubernetes/kubernetes/issues/19830. namespace := deployment.Namespace", "positive_passages": [{"docid": "doc-en-kubernetes-2f9c6224492589431ce544bf6b6edab10c3ff06174d612eb6875bebaba0cb87e", "text": "IMO it feels like a bad practice to have mutating resource handlers. The deletePod handler is used for queueing a Recreate deployment once it has no pods running. It should merely look at the ReplicaSets that have owner refs as opposed to using dc.getReplicaSetsForDeployment. The orphaning/adoption dance is already happening inside the reconcilation loop.\nI'd like to work on this\nfeel free to grab it. I can't assign the issue to you so I'll add myself; ping me on the PR when you have one.", "commid": "kubernetes_issue_46933", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fadce43c7652280d7667d6a50cfcb93490b456a80343ccd6b9046c6167a33c4a", "query": "defer logs.FlushLogs() if err := command.Execute(); err != nil { <del> fmt.Fprintf(os.Stderr, \"%vn\", err) </del> os.Exit(1) } }", "positive_passages": [{"docid": "doc-en-kubernetes-0b2213d42768c43adcb1b4f15cf67b8722c82d28c3ec9792f5837d41705eb847", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: kubectl version --client=yes command is giving the following error message. Error message is repeated at the start and the end and also containing programming jargon Error: invalid argument \"yes\" for \"--client\" flag: strconv.ParseBool: parsing \"yes\": invalid syntax Examples: Print the client and server versions for the current context kubectl version Options: --client=false: Client version only (no server required). -o, --output='': One of 'yaml' or 'json'. --short=false: Print just the version number. Usage: kubectl version [flags] [options] Use \"kubectl options\" for a list of global command-line options (applies to all commands). invalid argument \"yes\" for \"--client\" flag: strconv.ParseBool: parsing \"yes\": invalid syntax What you expected to happen: The error message can be improved with one of the two variants invalid argument \"yes\" for \"--client\" flag Examples: Print the client and server versions for the current context kubectl version Options: --client=false: Client version only (no server required). -o, --output='': One of 'yaml' or 'json'. --short=false: Print just the version number. Usage: kubectl version [flags] [options] Use \"kubectl options\" for a list of global command-line options (applies to all commands). (or) Invalid argument \"yes\" for \"--client\" flag How to reproduce it (as minimally and precisely as possible): Run the command kubectl version --client=yes Anything else we need to know?: Environment: Kubernetes version (use ): 1.15 Cloud provider or hardware configuration: AWS OS (e.g: ): Amazon Linux Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig cli\nHi Thanks for posting this issue! It turns out that this duplicate output has been in kubectl, and all the other cli cmds, since . This should be fixed by , and hopefully we can cherry pick it back to at least .", "commid": "kubernetes_issue_79454", "tokennum": 560}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fafdcd171430fd022edd55d11537c413d9ce30549fd40fb8d801e560fbd5a557", "query": "} } <ins> // BindOverrideFlags is a convenience method to bind the specified flags to their associated variables func BindOverrideFlags(overrides *ConfigOverrides, flags *pflag.FlagSet, flagNames ConfigOverrideFlags) { BindAuthInfoFlags(&overrides.AuthInfo, flags, flagNames.AuthOverrideFlags) BindClusterFlags(&overrides.ClusterInfo, flags, flagNames.ClusterOverrideFlags) BindContextFlags(&overrides.Context, flags, flagNames.ContextOverrideFlags) flagNames.CurrentContext.BindStringFlag(flags, &overrides.CurrentContext) flagNames.Timeout.BindStringFlag(flags, &overrides.Timeout) } </ins> // BindAuthInfoFlags is a convenience method to bind the specified flags to their associated variables func BindAuthInfoFlags(authInfo *clientcmdapi.AuthInfo, flags *pflag.FlagSet, flagNames AuthOverrideFlags) { flagNames.ClientCertificate.BindStringFlag(flags, &authInfo.ClientCertificate)", "positive_passages": [{"docid": "doc-en-kubernetes-4e19a56e8ccacbab4546f622baecdb0b8ef30250430c55f8bcdc4de99b100cd2", "text": "Found in openshift, but I'm pretty sure the codepaths are the same. That means the token is getting ignored and in-cluster config is being used in preference to flags.\nIs a similar issue?\nYep, kind of regression.\nSigh.\nYes, most likely the same cause.\nI'm on it.\nUnit test :)\nProbably will want to cherrypick this into 1.5.\nWIP in", "commid": "kubernetes_issue_38834", "tokennum": 89}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fb41bc2f57f290ad2e0fcee010aeabb7819939dbeda9a9f1ec505d188835f1c1", "query": "<ins> apiVersion: v1beta3 kind: ResourceQuota metadata: name: quota spec: hard: cpu: \"20\" memory: 1Gi persistentvolumeclaims: \"10\" pods: \"10\" replicationcontrollers: \"20\" resourcequotas: \"1\" secrets: \"10\" services: \"5\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-b9774b02da3d7547dcc6ec82c6d1246d6586e28e6fe16ad58f3c28b2558ac905", "text": "Resource quota example is missing readme. Was it once there and was accidentally deleted?\nI wrote something up in Origin repo I need to repurpose for Kubernetes. Sent from my iPhone", "commid": "kubernetes_issue_8749", "tokennum": 41}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fb7a96b013da8d318f8877e2ad0a4fd18ec20103169e0f0bd582d570b4042534", "query": "\"github.com/golang/glog\" \"k8s.io/apimachinery/pkg/types\" <del> \"k8s.io/kubernetes/pkg/cloudprovider\" </del> ) // AttachDisk attaches a vhd to vm", "positive_passages": [{"docid": "doc-en-kubernetes-6cfc50824280daf2f66f5e84f9a8c720c316cfa724f1e90fa02f306c798e5010", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind cleanup What happened: VirtualMachineScaleSetVM and VirtualMachine are different data structures (because of different API versions), so the disk attach operation seems duplicate between vm and vmss. That means although disk operations are in same logic, some duplication are still required now. They should use same api version in the future and should be merged into same code base, e.g. move sharing logic to Refer What you expected to happen: vmss and vm disk operations should share same code logic. How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others:\nI have checked with currently we can\u2019t merge, e.g. following two structs are different since they using different sdk-for-azure versions. While in the end when sdk-for-azure version is upgraded, above two versions should be same and at that time, we should merge functions like \u2018AttachDisk\u2019, \u2018DetachDiskByName\u2019, 'GetDiskLun', GetNextDiskLun, DisksAreAttached", "commid": "kubernetes_issue_59736", "tokennum": 313}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fb876af0ba403181d60a8eccd4e95c068bf882669c4635b1509668fdee6232c0", "query": "[[projects]] <del> name = \"github.com/json-iterator/go\" packages = [\".\"] revision = \"ca39e5af3ece67bbcda3d0f4f56a8e24d9f2dad4\" version = \"1.1.3\" [[projects]] </del> name = \"github.com/modern-go/concurrent\" packages = [\".\"] revision = \"e0a39a4cb4216ea8db28e22a69f4ec25610d513a\"", "positive_passages": [{"docid": "doc-en-kubernetes-0d085a3ee589d9a38ade8c650d9534110265a809ec41b82f41ce81cebea870e6", "text": "is a library yet is is instead of release tag. Please consider vendoring by tag whenever possible. Thanks.\nWe vendored it that way because the commit that fixed a bug (which we needed to be fixed and vendored back in) was This was merged on June 13. The release 1.1.4 () was released on July 1. If we want to update it to 1.1.4, I believe it should be fine. Between the commit we have vendored right now and the latest release, there are only three commits: adds tests merges (?) the case-sensitive fix - I'm not really sure what this commit is doing. fixes renaming when naming strategy is set (looks fine). Also, there are also no licensing changes. opinions?\n/sig api-machinery\n+1 to what said, it was a fire drill and 1.11.0 release was in trouble. Though in hind sight, we should have opened a issue to track that. something better to do next time. cc\nI'm indifferent to updating this. I'm okay with moving up if it doesn't break anything, or I'm fine with leaving things as is. We don't require deps to match semver. We can version out any commit in a deps tree, as we rely on our vendored copy.\nIt is always a good idea to match semver and it should be a default policy. Even if it doesn't matter to you, it should, because it is a best practice. Moreover downstream it matters much more as dependencies may be un-vendored in favour of tested re-usable packages.\n/cc\nIssues 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\nSomeone please take care of this or bot will eventually close this valid issue without action...\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .", "commid": "kubernetes_issue_66422", "tokennum": 501}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fb876af0ba403181d60a8eccd4e95c068bf882669c4635b1509668fdee6232c0", "query": "[[projects]] <del> name = \"github.com/json-iterator/go\" packages = [\".\"] revision = \"ca39e5af3ece67bbcda3d0f4f56a8e24d9f2dad4\" version = \"1.1.3\" [[projects]] </del> name = \"github.com/modern-go/concurrent\" packages = [\".\"] revision = \"e0a39a4cb4216ea8db28e22a69f4ec25610d513a\"", "positive_passages": [{"docid": "doc-en-kubernetes-3d634ec524d1253e3e5f3f0b99b6d74925e6b15b79d6d989e49b255bf837eee0", "text": "/lifecycle rotten\n/lifecycle rotten\n/remove-lifecycle rotten PR open (thanks,\noops! sorry, I meant to remove it. thanks!\nThanks.\nplease do feel free to open issues/prs of this sort early in the release cycle, so we can work through things needed well before the milestones/freeze etc. we are getting some heat about updating dependencies and we kind of settled on some guidelines here: if you think that needs updating, we could definitely debate that as well :) (on a PR against that doc)\nit have nothing to do with release cycle or justification for upgrade if/when dependency has been vendored incorrectly. It is basically a vendoring bug. No debate is necessary although that kind of issues usually meet some resistance and even hostility here... Bugs are filed when they are discovered, regardless of release cycle. It would be wrong to sit on the bug without reporting it in order to synchronise with release cycle.", "commid": "kubernetes_issue_66422", "tokennum": 200}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fb991e5df075657c1eb93149eabee869d0215cb54fd817b1588e553fd834eaa6", "query": "# TODO: This timeout should really be lower, this is a *long* time to test one # package, however pkg/api/testing in particular will fail with a lower timeout # currently. We should attempt to lower this over time. <del> KUBE_TIMEOUT=${KUBE_TIMEOUT:--timeout=170s} </del> <ins> KUBE_TIMEOUT=${KUBE_TIMEOUT:--timeout=180s} </ins> KUBE_COVER=${KUBE_COVER:-n} # set to 'y' to enable coverage collection KUBE_COVERMODE=${KUBE_COVERMODE:-atomic} # The directory to save test coverage reports to, if generating them. If unset,", "positive_passages": [{"docid": "doc-en-kubernetes-6e8eb8f0999228ea44b81934b9bc720e607abe0b26d40545836abe46d9ceca36", "text": "/kind failing-test Not sure if flake. Gubernator is showing a big spike in failures that started 06/14 around 10:00 ~UTC~ PT. This seems to be when merged. Failed on my PR: /sig testing\n/sig api-machinery\n/cc\nfiled I'm hesistant to bump it all the way back to 240, if you follow back the original PR / issue trail I ran a number of iterations of testing and it really shouldn't take 240s. four minutes is ludicrous for unit testing one package.\nthere are 39 failures in the last day in from timeout :/ /priority critical-urgent\nDid any timed-out run produce any logs?\nwe capture the test logs but itself doesn't appear to have any.\ne.g. at random (from triage above) =\"raw build-\" I'm not sure this code emits any when it fails.\nLikely it's timing out on some step, but I would have expected some logging from something related -- I was just going to look at the last thing logged and figure that something after that must be the culprit. Does that log capture stderr and stdout of the test invocations?\nit should, e.g. see a different kind of failure with logs: we're running with json output formatting then through to junit, and prow will capture stdout/stderr of whatever is running within the job as build-\nreopening to keep an eye on this.\nsigh: 180s\nit's doing better (all recent runs passed, looks like 3 flakes due to this since the PR merged this afternoon) but we may still want to bump it again\nWe're at 100% pass rate the past 3 hours but CI is not very active right now. still just 3 fails. If we have a similar rate tomorrow morning I'd opt for another small bump (maybe 180s -190s) to cover remaining limited flakes still over going all the way back to 4 minutes.\nIf we knew which sub test was slow when it is slow, that would possibly narrow it down to a haystack small enough to look for needles in.\ndug into it locally, follow up in:\nFairly confident this is now fixed after\nclosing as fixed by\nconfirmed\nexample:\nthat run happened at the fix merged at", "commid": "kubernetes_issue_102887", "tokennum": 491}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fbab38252b6d037ea3d2d4764f6d72c06b42eef4e971fdb7d2428615d6db6a08", "query": "case \"$tree\" in w/-text) # Only binary files have a size limit. <del> size=\"$(stat --printf=%s \"$file\")\" </del> <ins> size=\"$(wc -c < \"$file\")\" </ins> if [ \"${size}\" -gt \"$maxsize\" ] && ! kube::util::array_contains \"$file\" \"${allowlist[@]}\"; then echo    \"$file is too large ($size bytes)\"", "positive_passages": [{"docid": "doc-en-kubernetes-e910e751895c9a4adcc4aa9b295e34f4b420f777f06ea81f9820be7ed4c99f5c", "text": "The script encounters an error when executed on Mac OS X because the option is not supported. The error message appears as follows: I expected the script to execute successfully. Execute the command on macOS. No response <details</details<details</details<details</details<details</details<details</details<details</details\n/sig testing\n/triage accepted\n/priority backlog", "commid": "kubernetes_issue_124155", "tokennum": 84}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fbbe0d04760fa4703fbd0cc64c8e3c4015ed70ce31d8ba0ed58b044c47001e90", "query": "HostIP: \"1.2.3.4\", }, }, false}, <ins> {api.Node{ ObjectMeta: api.ObjectMeta{ Name:   \"foo\", Labels: map[string]string{\"bar\": \"foo\"}, }, Status: api.NodeStatus{ HostIP: \"1.2.3.4\", }, }, api.Node{ ObjectMeta: api.ObjectMeta{ Name:   \"foo\", Labels: map[string]string{\"bar\": \"fooobaz\"}, }, }, true}, </ins> } for _, test := range tests { errs := ValidateMinionUpdate(&test.oldMinion, &test.minion)", "positive_passages": [{"docid": "doc-en-kubernetes-88a6665f471219ba222a644b43576808b71f5f4fb39e5a18e0bc0e94ac9cb36e", "text": "Two problems: on node do not have namepace, but kubectl requires namespace. However, if explicitly set namespace to 'default', this will cause an error because we are updating not allowed field (only label update is allowed). is usually created by node controller, update node label with a file is tedious since user needs to create a file with id, resource.capacity, etc. can we make it easier?\nIt would make more sense to have a special global namespace than no namespace. We should make it easy in kubectl to update a single field or subset of fields, generally, for all objects. What this would do is GET, merge, and PUT.\nI had a discussion with on IRC about namespace on node. We'd like to just use \"\" (empty string) as of now. As we are not supporting any namespace feature on node, it's less confusing if we can hide the concept for now. Thinking a little more, \"\" is the special global namespace. I'm going to update kubectl to not assume 'default' namespace on every resources. It works fine for pod, service, but not for node, external LB, etc.\nThere was some discussion about \"\" being (essentially) an alias to \"default\": is that dead? , Deyuan Deng wrote:\nI've seen two versions of NamespaceALL (\"\") NamespaceAll is the default argument to specify on a context when you want to list or filter resources across An empty namespace is equivalent to the , but \"default\" is the canonical representation. Either means , or the definition conflicts - all namespace should include \"default\" namespace. Also, for things like Node, I'd really like a NamespaceNone.\n- I think there is a confusion here because of a poor naming choice. is a constant intended to be used as a filter to LIST/WATCH across multiple namespaces. It is NOT intended to be the value that is set on a resource for persistence. The discussion was to update to which I think is still a good thing to do. I have held off doing that until after we embed the namespace as a path parameter in our URLs instead of a query parameter, which I plan to look at after the holidays. is a constant intended to be used as the namespace context of a request when it's not explicitly stated on a request URL.", "commid": "kubernetes_issue_2548", "tokennum": 510}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fbbe0d04760fa4703fbd0cc64c8e3c4015ed70ce31d8ba0ed58b044c47001e90", "query": "HostIP: \"1.2.3.4\", }, }, false}, <ins> {api.Node{ ObjectMeta: api.ObjectMeta{ Name:   \"foo\", Labels: map[string]string{\"bar\": \"foo\"}, }, Status: api.NodeStatus{ HostIP: \"1.2.3.4\", }, }, api.Node{ ObjectMeta: api.ObjectMeta{ Name:   \"foo\", Labels: map[string]string{\"bar\": \"fooobaz\"}, }, }, true}, </ins> } for _, test := range tests { errs := ValidateMinionUpdate(&test.oldMinion, &test.minion)", "positive_passages": [{"docid": "doc-en-kubernetes-5a4d1d083bc5e635544966baa95a7511fe688574aded9d8644d8c7753070f0a1", "text": "Since create operations pull the namespace from the context during persistence, it is also the value intended to be persisted. This is referring to a request URL that does not specify a namespace. It is not referring to the persisted value in the database directly - although that is the value that gets pulled. I think a is a good thing to add AFTER we make the change to specify namespace as a path parameter instead of a query parameter, and we update/rename to something that clarifies that its a wild-card filter whose value is probably best represented as.\nok, sounds good. Thanks. Look forward to see api.NamespaceAll = \"*\" and api.NamespaceNone :)", "commid": "kubernetes_issue_2548", "tokennum": 145}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fbfbad523648010f75f75eda52015a203819bfd213b9fdbf65c0683bfbc1e410", "query": "for _, l := range strings.Split(string(f.Lines), \"n\") { if strings.Contains(l, fmt.Sprintf(\"-A %v\", chainName)) { newRule := Rule(map[string]string{}) <del> for _, arg := range []string{Destination, Source, DPort, Protocol, Jump, ToDest, Recent} { </del> <ins> for _, arg := range []string{Destination, Source, DPort, Protocol, Jump, ToDest, Recent, MatchSet} { </ins> tok := getToken(l, arg) if tok != \"\" { newRule[arg] = tok", "positive_passages": [{"docid": "doc-en-kubernetes-4b95e73f98faca5940a16ee2fccddf37ae93437213e073578ff34d76b732271f", "text": "Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Service loadbalancer source range don't work in ipvs proxy mode. Which result in gci-gce-ipvs CI failed. http://k8s- How to reproduce it (as minimally and precisely as possible): In gce environment. a service with backend. service type to service util service external IP is specified. the service from pod inside and pod out of the . Environment: Kubernetes version (use ): master Cloud provider or hardware configuration: gce OS (e.g. from /etc/os-release): ubuntu Kernel (e.g. ): Install tools: cluster/kube- Others:\n/kind bug /sig network /label ipvs\n/area ipvs\nThe test seems to be flaky now. Can you take a look please?\nI don't know why, but I think this flaky have the similiar reason with other normal service-test cases, like Those flaky are pretty annoying, problem is, I have run those cases in my own environment many times, never fail... : ( But still, I'll do my best to find the reason.", "commid": "kubernetes_issue_61090", "tokennum": 264}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fbfbd517739c1490804871fd5366020886ee18d1837b317043ea14660ab84e28", "query": "# machines) we have to talk directly to the container IP.  There is no one # strategy that works in all cases so we test to figure out which situation we # are in. <del> if kube::build::probe_address 127.0.0.1 ${mapped_port}; then </del> <ins> if kube::build::rsync_probe 127.0.0.1 ${mapped_port}; then </ins> KUBE_RSYNC_ADDR=\"127.0.0.1:${mapped_port}\" <del> sleep 0.5 </del> return 0 <del> elif kube::build::probe_address \"${container_ip}\" ${KUBE_CONTAINER_RSYNC_PORT}; then </del> <ins> elif kube::build::rsync_probe \"${container_ip}\" ${KUBE_CONTAINER_RSYNC_PORT}; then </ins> KUBE_RSYNC_ADDR=\"${container_ip}:${KUBE_CONTAINER_RSYNC_PORT}\" <del> sleep 0.5 </del> return 0 fi", "positive_passages": [{"docid": "doc-en-kubernetes-23c92439a8a6a56c88d16c6d832940b868e99c5934b866ad407565ebf4fae31b", "text": "https://k8s-\nI have a similar problem when I try to make release on my local desktop:\nRelated to .\nSimilar problem for :\nCan you open a new issue for your problem with information about your set up. Mac/Linux? Docker version? etc.\nPlease add details to (to be opened) issue. I suspect that is a different issue.\nNew issue:", "commid": "kubernetes_issue_34214", "tokennum": 79}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fc1a4b39e6f041452bc65cfebe5495adbe45f427a36b50e69e7221ca39488694", "query": "<del> apiVersion: v1 kind: ReplicationController metadata: name: es-master labels: component: elasticsearch role: master spec: replicas: 1 template: metadata: labels: component: elasticsearch role: master spec: serviceAccount: elasticsearch containers: - name: es-master securityContext: capabilities: add: - IPC_LOCK image: quay.io/pires/docker-elasticsearch-kubernetes:1.7.1-4 env: - name: KUBERNETES_CA_CERTIFICATE_FILE value: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt - name: NAMESPACE valueFrom: fieldRef: fieldPath: metadata.namespace - name: \"CLUSTER_NAME\" value: \"myesdb\" - name: NODE_MASTER value: \"true\" - name: NODE_DATA value: \"false\" - name: HTTP_ENABLE value: \"false\" ports: - containerPort: 9300 name: transport protocol: TCP volumeMounts: - mountPath: /data name: storage volumes: - name: storage emptyDir: {} </del>", "positive_passages": [{"docid": "doc-en-kubernetes-5fef938b0452d0f6b58e576cd11f17813fb6d6b970f83a7868d905b7784a5e39", "text": "Presently, the elasticsearch example Kubernetes configurations target elasticsearch v1.7.1, which is quite old. As of this writing, the latest elasticsearch release is v5.6.2, with many deployment changes since then. Could the elasticsearch examples be updated to target the v5 series of elasticsearch? See for a more up to date reference configuration.\ncc\nhey it's been a long while since I last contributed to the docs. i can do it soon but i need pointers on how to properly do it.\nhey, so we need to update the stuff under examples/elasticsearch/ *&repos=kubernetes So basically update the images, yaml files etc and test that everything works (and submit a PR)\n/sig testing\nAh, so there's no documentation updates anymore. OK I'll take care of it, assign it to me.\nIssues 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\nGitHub didn't allow me to assign the following users: me. Note that only and repo collaborators can be assigned. <detailsIn response to : /assign me 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\n/assign pires\n/remove-lifecycle stale\nit seems that the example moved to I am now reading that repo guidelines and will update this there. I'll also open a PR that cleans this folder in the current repo and closes this issue.", "commid": "kubernetes_issue_53142", "tokennum": 387}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fc2079ad34362adea24961c313ecd587c88639df9d7b6ad6819146371685876a", "query": "# Nodelocal DNS Cache <ins> Using NodeLocal DNSCache in Kubernetes clusters(https://kubernetes.io/docs/tasks/administer-cluster/nodelocaldns/). </ins> This addon runs a node-local-dns pod on all cluster nodes. The pod runs CoreDNS as the dns cache. It runs with `hostNetwork:True` and creates a dedicated dummy interface with a link local ip(169.254.20.10/32 by default) to listen for DNS queries. The cache instances connect to clusterDNS in case of cache misses. <del> Design details [here](https://git.k8s.io/enhancements/keps/sig-network/0030-nodelocal-dns-cache.md) KEP to graduate to beta [here](https://git.k8s.io/enhancements/keps/sig-network/20190424-NodeLocalDNS-beta-proposal.md) </del> <ins> Design details [here](https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/1024-nodelocal-cache-dns/README.md) </ins> <del> This feature is graduating to Beta in release 1.15. </del> <ins> This feature is graduating to GA in release 1.18(Beta in release 1.15). </ins> ## nodelocaldns addon template This directory contains the addon config yaml - `nodelocaldns.yaml` The variables will be substituted by the configure scripts when the yaml is copied into master. <del> We have the following variables in the yaml: `__PILLAR__DNS__SERVER__` - set to kube-dns service IP. `__PILLAR__LOCAL__DNS__`  - set to the link-local IP(169.254.20.10 by default). `__PILLAR__DNS__DOMAIN__` - set to the cluster domain(cluster.local by default). </del> <ins> We have the following variables in the yaml: `__PILLAR__DNS__SERVER__` - set to kube-dns service IP. `__PILLAR__LOCAL__DNS__`  - set to the link-local IP(169.254.20.10 by default). `__PILLAR__DNS__DOMAIN__` - set to the cluster domain(cluster.local by default). Note: The local listen IP address for NodeLocal DNSCache can be any address that can be guaranteed to not collide with any existing IP in your cluster. It's recommended to use an address with a local scope, per example, from the link-local range 169.254.0.0/16 for IPv4 or from the Unique Local Address range in IPv6 fd00::/8. </ins> The following variables will be set by the node-cache images - k8s.gcr.io/k8s-dns-node-cache:1.15.6 or later. The values will be determined by reading the kube-dns configMap for custom <del> Upstream server configuration. `__PILLAR__CLUSTER__DNS__` - Upstream server for in-cluster queries. `__PILLAR__UPSTREAM__SERVERS__` - Upstream servers for external queries. </del> <ins> Upstream server configuration. `__PILLAR__CLUSTER__DNS__` - Upstream server for in-cluster queries. `__PILLAR__UPSTREAM__SERVERS__` - Upstream servers for external queries. </ins> ### Network policy and DNS connectivity When running nodelocaldns addon on clusters using network policy, additional rules might be required to enable dns connectivity. <del> Using a namespace selector for dns egress traffic as shown [here](https://docs.projectcalico.org/v2.6/getting-started/kubernetes/tutorials/advanced-policy) </del> <ins> Using a namespace selector for dns egress traffic as shown [here](https://docs.projectcalico.org/security/tutorials/kubernetes-policy-advanced) </ins> might not be enough since the node-local-dns pods run with `hostNetwork: True` One way to enable connectivity from node-local-dns pods to clusterDNS ip is to use an ipBlock rule instead:", "positive_passages": [{"docid": "doc-en-kubernetes-ffd505027484e14846d7eca4dd46da75100eeb1e560f155a9f5f3a05b8321559", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --This is probably just a documentation / example issue. I'm a real noob so I can just tell this is an issue, but I can't fix the docs through a PR, otherwise I'd do it happily. Hope it's not a dupe. Following the guide at with IPVS. Using the following script: This generates the following YAML (only the interesting part): You see that the line has an extra comma. It's instead of (extra comma after second argument) This generates the following log: Removing the extra comma fixes everything. Setup a cluster with Kube-DNS IPVS mode Generate the nodelocaldns Deploy the manifest Pods are crashing Kubernetes version v1.21.0 Cloud provider or hardware configuration: Bare Metal with HA setup (behind an external LB, Kube-proxy as IPVS) OS (e.g: ): CentOS Linux 8 Kernel (e.g. ): Linux 4.18.0-240.10.1.el83.x8664 SMP Mon Jan 18 17:05:51 UTC 2021 x8664 x8664 x86_64 GNU/LinuxInstall tools: none, a classic kubeadm initNetwork plugin and version (if this is a network-related bug): Not relevant, but Canal (Calico + Flannel) Others: nothing. Love you all for making K8S. Thank you a billion times.\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig docs\n, it seems like that don't get a value return. i saw command in Can you try this again and check if can kubedns get a value?\n/area dns /sig network /assign Documentation here is not changed since Sep 2019 and needs to be updated as well.", "commid": "kubernetes_issue_101339", "tokennum": 514}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fc2079ad34362adea24961c313ecd587c88639df9d7b6ad6819146371685876a", "query": "# Nodelocal DNS Cache <ins> Using NodeLocal DNSCache in Kubernetes clusters(https://kubernetes.io/docs/tasks/administer-cluster/nodelocaldns/). </ins> This addon runs a node-local-dns pod on all cluster nodes. The pod runs CoreDNS as the dns cache. It runs with `hostNetwork:True` and creates a dedicated dummy interface with a link local ip(169.254.20.10/32 by default) to listen for DNS queries. The cache instances connect to clusterDNS in case of cache misses. <del> Design details [here](https://git.k8s.io/enhancements/keps/sig-network/0030-nodelocal-dns-cache.md) KEP to graduate to beta [here](https://git.k8s.io/enhancements/keps/sig-network/20190424-NodeLocalDNS-beta-proposal.md) </del> <ins> Design details [here](https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/1024-nodelocal-cache-dns/README.md) </ins> <del> This feature is graduating to Beta in release 1.15. </del> <ins> This feature is graduating to GA in release 1.18(Beta in release 1.15). </ins> ## nodelocaldns addon template This directory contains the addon config yaml - `nodelocaldns.yaml` The variables will be substituted by the configure scripts when the yaml is copied into master. <del> We have the following variables in the yaml: `__PILLAR__DNS__SERVER__` - set to kube-dns service IP. `__PILLAR__LOCAL__DNS__`  - set to the link-local IP(169.254.20.10 by default). `__PILLAR__DNS__DOMAIN__` - set to the cluster domain(cluster.local by default). </del> <ins> We have the following variables in the yaml: `__PILLAR__DNS__SERVER__` - set to kube-dns service IP. `__PILLAR__LOCAL__DNS__`  - set to the link-local IP(169.254.20.10 by default). `__PILLAR__DNS__DOMAIN__` - set to the cluster domain(cluster.local by default). Note: The local listen IP address for NodeLocal DNSCache can be any address that can be guaranteed to not collide with any existing IP in your cluster. It's recommended to use an address with a local scope, per example, from the link-local range 169.254.0.0/16 for IPv4 or from the Unique Local Address range in IPv6 fd00::/8. </ins> The following variables will be set by the node-cache images - k8s.gcr.io/k8s-dns-node-cache:1.15.6 or later. The values will be determined by reading the kube-dns configMap for custom <del> Upstream server configuration. `__PILLAR__CLUSTER__DNS__` - Upstream server for in-cluster queries. `__PILLAR__UPSTREAM__SERVERS__` - Upstream servers for external queries. </del> <ins> Upstream server configuration. `__PILLAR__CLUSTER__DNS__` - Upstream server for in-cluster queries. `__PILLAR__UPSTREAM__SERVERS__` - Upstream servers for external queries. </ins> ### Network policy and DNS connectivity When running nodelocaldns addon on clusters using network policy, additional rules might be required to enable dns connectivity. <del> Using a namespace selector for dns egress traffic as shown [here](https://docs.projectcalico.org/v2.6/getting-started/kubernetes/tutorials/advanced-policy) </del> <ins> Using a namespace selector for dns egress traffic as shown [here](https://docs.projectcalico.org/security/tutorials/kubernetes-policy-advanced) </ins> might not be enough since the node-local-dns pods run with `hostNetwork: True` One way to enable connectivity from node-local-dns pods to clusterDNS ip is to use an ipBlock rule instead:", "positive_passages": [{"docid": "doc-en-kubernetes-d83335fcac537a45eafa3dfd42630478844385174c0958db0174f56a0ffa2f73", "text": "Dual-stack and ipv6 are used more widely now.\nI do get a value, but is replaced with as the extra comma doesn't seem to be replaced.\n/assign", "commid": "kubernetes_issue_101339", "tokennum": 38}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fc7fc76d0264e2b2ed2b1640fb8c48705defe85178f89e7db7e9022c8b526c14", "query": "allErrs = append(allErrs, field.Invalid(fldPath.Child(\"SyncPeriod\"), config.MinSyncPeriod, fmt.Sprintf(\"must be greater than or equal to %s\", fldPath.Child(\"MinSyncPeriod\").String()))) } <ins> allErrs = append(allErrs, validateIPVSTimeout(config, fldPath)...) </ins> allErrs = append(allErrs, validateIPVSSchedulerMethod(kubeproxyconfig.IPVSSchedulerMethod(config.Scheduler), fldPath.Child(\"Scheduler\"))...) allErrs = append(allErrs, validateIPVSExcludeCIDRs(config.ExcludeCIDRs, fldPath.Child(\"ExcludeCidrs\"))...)", "positive_passages": [{"docid": "doc-en-kubernetes-be027d483b5644a511b34dd42acd191f0a8a8265cd239e919307434a4dbdd401", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: kube-proxy doesn't validate the configurable IPVS tcp, tcpfin and udp timeouts. For example, when kube-proxy starts with , it will always log a warning: . What you expected to happen: kube-proxy should validate --ipvs-tcp-timeout, --ipvs-tcpfin-timeout, --ipvs-udp-timeout flag values at start. How to reproduce it (as minimally and precisely as possible): add flags to kube-proxy Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:\n/sig network /area ipvs\n/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. \u200d", "commid": "kubernetes_issue_88656", "tokennum": 269}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fcde7d934394c92d95322a48c50f8677a28908db4743cbaa74d20f1d19ddf5bb", "query": "<ins> /* Copyright 2016 The Kubernetes Authors. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package util import ( \"testing\" \"time\" federation_api \"k8s.io/kubernetes/federation/apis/federation/v1beta1\" federation_release_1_4 \"k8s.io/kubernetes/federation/client/clientset_generated/federation_release_1_4\" fake_federation_release_1_4 \"k8s.io/kubernetes/federation/client/clientset_generated/federation_release_1_4/fake\" api \"k8s.io/kubernetes/pkg/api\" api_v1 \"k8s.io/kubernetes/pkg/api/v1\" \"k8s.io/kubernetes/pkg/client/cache\" \"k8s.io/kubernetes/pkg/client/testing/core\" \"k8s.io/kubernetes/pkg/controller/framework\" \"k8s.io/kubernetes/pkg/runtime\" \"k8s.io/kubernetes/pkg/watch\" \"github.com/stretchr/testify/assert\" ) // Basic test for Federated Informer. Checks whether the subinformer are added and deleted // when the corresponding cluster entries appear and dissapear from etcd. func TestFederatedInformer(t *testing.T) { fakeClient := &fake_federation_release_1_4.Clientset{} // Add a single cluster to federation and remove it when needed. cluster := federation_api.Cluster{ ObjectMeta: api_v1.ObjectMeta{ Name: \"mycluster\", }, Status: federation_api.ClusterStatus{ Conditions: []federation_api.ClusterCondition{ {Type: federation_api.ClusterReady, Status: api_v1.ConditionTrue}, }, }, } fakeClient.AddReactor(\"list\", \"clusters\", func(action core.Action) (bool, runtime.Object, error) { return true, &federation_api.ClusterList{Items: []federation_api.Cluster{cluster}}, nil }) deleteChan := make(chan struct{}) fakeClient.AddWatchReactor(\"clusters\", func(action core.Action) (bool, watch.Interface, error) { fakeWatch := watch.NewFake() go func() { <-deleteChan fakeWatch.Delete(&cluster) }() return true, fakeWatch, nil }) // There is a single service ns1/s1 in cluster mycluster. service := api_v1.Service{ ObjectMeta: api_v1.ObjectMeta{ Namespace: \"ns1\", Name:      \"s1\", }, } fakeClient.AddReactor(\"list\", \"services\", func(action core.Action) (bool, runtime.Object, error) { return true, &api_v1.ServiceList{Items: []api_v1.Service{service}}, nil }) fakeClient.AddWatchReactor(\"services\", func(action core.Action) (bool, watch.Interface, error) { return true, watch.NewFake(), nil }) targetInformerFactory := func(cluster *federation_api.Cluster, clientset federation_release_1_4.Interface) (cache.Store, framework.ControllerInterface) { return framework.NewInformer( &cache.ListWatch{ ListFunc: func(options api.ListOptions) (runtime.Object, error) { return clientset.Core().Services(api_v1.NamespaceAll).List(options) }, WatchFunc: func(options api.ListOptions) (watch.Interface, error) { return clientset.Core().Services(api_v1.NamespaceAll).Watch(options) }, }, &api_v1.Service{}, 10*time.Second, framework.ResourceEventHandlerFuncs{}) } informer := NewFederatedInformer(fakeClient, targetInformerFactory).(*federatedInformerImpl) informer.clientFactory = func(cluster *federation_api.Cluster) (federation_release_1_4.Interface, error) { return fakeClient, nil } assert.NotNil(t, informer) informer.Start() // Wait until mycluster is synced. for !informer.GetTargetStore().ClustersSynced([]*federation_api.Cluster{&cluster}) { time.Sleep(time.Millisecond * 100) } readyClusters, err := informer.GetReadyClusters() assert.NoError(t, err) assert.Contains(t, readyClusters, &cluster) serviceList, err := informer.GetTargetStore().List() assert.NoError(t, err) assert.Contains(t, serviceList, &service) service1, found, err := informer.GetTargetStore().GetByKey(\"mycluster\", \"ns1/s1\") assert.NoError(t, err) assert.True(t, found) assert.EqualValues(t, &service, service1) // All checked, lets delete the cluster. deleteChan <- struct{}{} for !informer.GetTargetStore().ClustersSynced([]*federation_api.Cluster{}) { time.Sleep(time.Millisecond * 100) } readyClusters, err = informer.GetReadyClusters() assert.NoError(t, err) assert.Empty(t, readyClusters) serviceList, err = informer.GetTargetStore().List() assert.NoError(t, err) assert.Empty(t, serviceList) // Test complete. informer.Stop() } </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-4f983686ce6cef6162dd147e0e53be05aced0afa9196140d2e8041aafeaab5cd", "text": "As discussed, similar patterns occur in many of the controller for federated objects. Lift this into a common library that can be used by all of the controllers. Open separate issues for each of the above, and track there. This can be the tracking issue over those.\nHi, , we have been starting develop work about cluster-controller and RS controller, so would you like to share me the plan about this work? Thanks.\nTracked in PR's referenced above. Closing this tracking issue.", "commid": "kubernetes_issue_29347", "tokennum": 99}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fcf325d258126fb7a32b4ae1314279d929af7ec21f56d8c21e74e4f7d6d27dd7", "query": "import ( \"errors\" \"fmt\" <del> \"k8s.io/klog\" </del> \"path\" \"strconv\" \"strings\" <ins> \"k8s.io/klog\" </ins> ) // FindMultipathDeviceForDevice given a device name like /dev/sdx, find the devicemapper parent", "positive_passages": [{"docid": "doc-en-kubernetes-2bba8e4fb458ddf612a1ae84873c0951878ae27f68765b5b6efc434715382796", "text": "If one target in multipath volume gets down and a pod that uses the volume is deleted and quickly recreated (e.g. by a Deployment), the new pod never starts. How to reproduce it (as minimally and precisely as possible): Deployment with single replica with one multipath iSCSI volume one target (e.g. switch the machine off). Multipath will mark appropriate path as failed: the deployment pod. will quickly start a new pod for the Deployment. new pod will be (or ) forever, What happened: Kubelet tries to WaitForAttach / SetUp volume for the new pod. The volume is still attached. Kubelet goes through all targets and tries to find out if it's logged in or not. Eventually it tries to read of the failed path and that returns error: What you expected to happen: Kubelet assumes that the path is failed / not logged in and tries to recover it. If it fails it continues with multipath with 2 available devices and 1 failed one. IMO, simple instead of will do its job just fine. /assign /sig storage cc for iSCSI expertise\nFix:", "commid": "kubernetes_issue_74305", "tokennum": 238}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fd1f62fc136a8c086ddc8eaa283661413ba8c9270e8ee069703b419c310b76a1", "query": "\"net/http\" \"net/url\" gpath \"path\" <ins> \"strings\" </ins> \"time\" \"k8s.io/kubernetes/pkg/admission\"", "positive_passages": [{"docid": "doc-en-kubernetes-c21754b57b54e9212f2cf7773a0f449c984b1bc5da8671633611701b2ce62a1e", "text": "Given a request with a Content-Type header set to , the server will respond with an error because it does not exactly match the existing strings. Some browsers (Firefox, see: ) will automatically add to a Content-Type header when making an XHR request.", "commid": "kubernetes_issue_14872", "tokennum": 56}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fd22047972ce572eb059f1c19db7b9072555918440d247d8f5829932cb870413", "query": "# # $1 - server architecture kube::build::get_docker_wrapped_binaries() { <del> local debian_iptables_version=buster-v1.4.0 </del> <ins> local debian_iptables_version=buster-v1.5.0 </ins> local go_runner_version=buster-v2.2.4 ### If you change any of these lists, please also update DOCKERIZED_BINARIES ### in build/BUILD. And kube::golang::server_image_targets", "positive_passages": [{"docid": "doc-en-kubernetes-ee0826757468ea334f95c77509b257c3d392b6713b4311ba7afa125d642dcec9", "text": "The based container images for are shipped with the wrong architecture within the manifest if not amd64: Refers to We updated the images a few minutes ago to buster-v1.3.0, which are now ready to be used as base for the multi-architecture images. If the images contain the right architectures, then it may magically happen that the kube-proxy images are fixed, too. This is because we already use the build syntax for it: /cc\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig release", "commid": "kubernetes_issue_98229", "tokennum": 187}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fd8cc5ce2c382d7d7a21e3e296a481542730dd2080d2a7f0cb727b25109c4301", "query": "function kube-up { <ins> echo \"Starting cluster using os distro: ${KUBE_OS_DISTRIBUTION}\" >&2 </ins> get-tokens detect-image", "positive_passages": [{"docid": "doc-en-kubernetes-22d12c96031ea08416343124eb9503ad24bb849f7be271f6e9f581299968b0bd", "text": "Example: kubectl cluster-info shows a redundant line: The cluster is already up, so the phrase \"Starting cluster\" is confusing in context of the command. (My kubernetes test cluster is running on AWS i.e. KUBERNETES_PROVIDER=aws. I had used kube- to create a test kubernetes cluster on aws). Log of my shell session:\nThanks for the bug report I've filed a PR to fix it.", "commid": "kubernetes_issue_9246", "tokennum": 103}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fe11371e53fe658eb65505e429001fa9694b088af4385396930b11753c0e15a5", "query": "if strings.Compare(p.Status.Conditions[0].Reason, \"Unschedulable\") != 0 { t.Fatalf(\"Failed as Pod %s reason was: %s but expected: Unschedulable\", podName, p.Status.Conditions[0].Reason) } <del> if !strings.Contains(p.Status.Conditions[0].Message, \"MatchNodeSelector\") || !strings.Contains(p.Status.Conditions[0].Message, \"VolumeNodeAffinityConflict\") { t.Fatalf(\"Failed as Pod's %s failure message does not contain expected keywords: MatchNodeSelector, VolumeNodeAffinityConflict\", podName) </del> <ins> if !strings.Contains(p.Status.Conditions[0].Message, \"node(s) didn't match node selector\") || !strings.Contains(p.Status.Conditions[0].Message, \"node(s) had volume node affinity conflict\") { t.Fatalf(\"Failed as Pod's %s failure message does not contain expected message: node(s) didn't match node selector, node(s) had volume node affinity conflict\", podName) </ins> } if err := config.client.CoreV1().Pods(config.ns).Delete(podName, &metav1.DeleteOptions{}); err != nil { t.Fatalf(\"Failed to delete Pod %s: %v\", podName, err)", "positive_passages": [{"docid": "doc-en-kubernetes-10c13016eb5239afc7a330cfdab91dbf78232a49f2993f71669df735dbb939e1", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind feature The is not user friendly. There has been to make it better, but we still print in the pending message. We should change these errors to a more human readable message. For example, should be changed to something like . /sig scheduling", "commid": "kubernetes_issue_58546", "tokennum": 91}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fe13a9fbadb3be24fb180c4aa9202eda575ff8279c5d07a0a76cbccaacdde5dd", "query": "} delete(plugin.podCIDRs, id) <ins> glog.V(3).Infof(\"Calling cni plugins to remove container from network with cni runtime: %+v\", rt) </ins> if err := plugin.cniConfig.DelNetwork(plugin.netConfig, rt); err != nil { return fmt.Errorf(\"Error removing container from network: %v\", err) }", "positive_passages": [{"docid": "doc-en-kubernetes-3e2b7d9568ee0bf267de4bcdac04137844677bca3ba3f5eceb5026951de8c86d", "text": "Event for a pod: The cni plugins do exist at /opt/cni/bin. They cannot be executed and bash is complaining:\ncc\nI'm guessing this is a shared lib problem, since /usr/grte/v4/lib64/ld-linux-x86- doesn't exist on my gce vm. We should update docs to make it clear how someone would install manually (if they run into such problems again) and statically link (if the problem is indeed the shared lib) with something like Unsure how we'd support different GOOS (vend different tarballs vs checking in and building the plugin inline with our make scripts)\nuggh. These binaries need to be ultra-static or else we need to containerize them.\nEssentially doing would've prevented this bug :)\nAnd see for the CNI_ARGS problems\nalso , re ... however, I'm not too sure if your comment was mean to be on this ticket.\ncc\nI have a working version. I uploaded my cni binary with bug fix on GCS. change source to change sourcehash to Welcome to give it a try.\nAlso see problem:", "commid": "kubernetes_issue_23011", "tokennum": 252}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fe5068a2f7a389a4d4f0dba88c8c2495cb9066a8255a1624e10213069aca5e16", "query": "<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/horizontal-pod-autoscaling/README.md?pixel)]() <del> <!-- END MUNGE: GENERATED_ANALYTICS --> </del> <ins> <!-- END MUNGE: GENERATED_ANALYTICS --> </ins>  No newline at end of file", "positive_passages": [{"docid": "doc-en-kubernetes-0f2f59a4098799df231d0f4ddd6804f8b020392d4e4aa17c98fa7a6b4bb4eccd", "text": "The heapster needs to be installed if end user want to use autoscaler feature, we should mention this in document.", "commid": "kubernetes_issue_17466", "tokennum": 25}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fe50a90f73b1cb6aefb125036495938af3a51ac1cc7fea157d4be14411b2fa04", "query": "return nil } <del> func (ctrl *controller) getParameters(ctx context.Context, claim *resourcev1alpha2.ResourceClaim, class *resourcev1alpha2.ResourceClass) (claimParameters, classParameters interface{}, err error) { </del> <ins> func (ctrl *controller) getParameters(ctx context.Context, claim *resourcev1alpha2.ResourceClaim, class *resourcev1alpha2.ResourceClass, notifyClaim bool) (claimParameters, classParameters interface{}, err error) { </ins> classParameters, err = ctrl.driver.GetClassParameters(ctx, class) if err != nil { <ins> ctrl.eventRecorder.Event(class, v1.EventTypeWarning, \"Failed\", err.Error()) </ins> err = fmt.Errorf(\"class parameters %s: %v\", class.ParametersRef, err) return } claimParameters, err = ctrl.driver.GetClaimParameters(ctx, claim, class, classParameters) if err != nil { <ins> if notifyClaim { ctrl.eventRecorder.Event(claim, v1.EventTypeWarning, \"Failed\", err.Error()) } </ins> err = fmt.Errorf(\"claim parameters %s: %v\", claim.Spec.ParametersRef, err) return }", "positive_passages": [{"docid": "doc-en-kubernetes-e8eec0a3f7a81297ed919db6952e73e9801661fbfe386a524b19b8189beefe88", "text": "When ResourceClaimParameters or ResourceClassParameters fail validation in resource driver during PodSchedulingContext sync loop, the error is visible only in the events of the PodSchedulingContext. The error should be visible on the object that fails validation as well, ResourceClaim or ResourceClass respectively. Creating ResourceClaim with unsupported parameters' values or unsupported No response <details</details<details</details<details</details<details</details<details</details<details</details\n/assign\n/sig node\n/triage accepted\nKEP:", "commid": "kubernetes_issue_121063", "tokennum": 126}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fe567d9cf78409720bcbb87b1ad6339cb18b53dd88041da1d575419b6cc2df05", "query": "<ins> # The Kubernetes API Primary system and API concepts are documented in the [User guide](user-guide.md). Overall API conventions are described in the [API conventions doc](api-conventions.md). Complete API details are documented via [Swagger](http://swagger.io/). The Kubernetes apiserver (aka \"master\") exports an API that can be used to retrieve the [Swagger spec](https://github.com/swagger-api/swagger-spec/tree/master/schemas/v1.2) for the Kubernetes API, by default at `/swaggerapi`, and a UI you can use to browse the API documentation at `/swaggerui`. We also periodically update a [statically generated UI](http://kubernetes.io/third_party/swagger-ui/). Remote access to the API is discussed in the [access doc](accessing_the_api.md). The Kubernetes API also serves as the foundation for the declarative configuration schema for the system. The [Kubectl](kubectl.md) command-line tool can be used to create, update, delete, and get API objects. Kubernetes also stores its serialized state (currently in [etcd](https://coreos.com/docs/distributed-configuration/getting-started-with-etcd/)) in terms of the API resources. Kubernetes itself is decomposed into multiple components, which interact through its API. ## API changes In our experience, any system that is successful needs to grow and change as new use cases emerge or existing ones change. Therefore, we expect the Kubernetes API to continuously change and grow. However, we intend to not break compatibility with existing clients, for an extended period of time. In general, new API resources and new resource fields can be expected to be added frequently. Elimination of resources or fields will require following a deprecation process. The precise deprecation policy for eliminating features is TBD, but once we reach our 1.0 milestone, there will be a specific policy. What constitutes a compatible change and how to change the API are detailed by the [API change document](devel/api_changes.md). ## API versioning Fine-grain resource evolution alone makes it difficult to eliminate fields or restructure resource representations. Therefore, Kubernetes supports multiple API versions, each at a different API path prefix, such as `/api/v1beta3`. These are simply different interfaces to read and/or modify the same underlying resources. In general, all API resources are accessible via all API versions, though there may be some cases in the future where that is not true. Distinct API versions present more clear, consistent views of system resources and behavior than intermingled, independently evolved resources. They also provide a more straightforward mechanism for controlling access to end-of-lifed and/or experimental APIs. The [API and release versioning proposal](versioning.md) describes the current thinking on the API version evolution process. ## v1beta1 and v1beta2 are deprecated; please move to v1beta3 ASAP As of April 1, 2015, the Kubernetes v1beta3 API has been enabled by default, and the v1beta1 and v1beta2 APIs are deprecated. v1beta3 should be considered the v1 release-candidate API, and the v1 API is expected to be substantially similar. As \"pre-release\" APIs, v1beta1, v1beta2, and v1beta3 will be eliminated once the v1 API is available, by the end of June 2015. ## v1beta3 conversion tips We're working to convert all documentation and examples to v1beta3. Most examples already contain a v1beta3 subdirectory with the API objects translated to v1beta3. A simple [API conversion tool](cluster_management.md#switching-your-config-files-to-a-new-api-version) has been written to simplify the translation process. Use `kubectl create --validate` in order to validate your json or yaml against our Swagger spec. Some important differences between v1beta1/2 and v1beta3: * The resource `id` is now called `name`. * `name`, `labels`, `annotations`, and other metadata are now nested in a map called `metadata` * `desiredState` is now called `spec`, and `currentState` is now called `status` * `/minions` has been moved to `/nodes`, and the resource has kind `Node` * The namespace is required (for all namespaced resources) and has moved from a URL parameter to the path: `/api/v1beta3/namespaces/{namespace}/{resource_collection}/{resource_name}` * The names of all resource collections are now lower cased - instead of `replicationControllers`, use `replicationcontrollers`. * To watch for changes to a resource, open an HTTP or Websocket connection to the collection URL and provide the `?watch=true` URL parameter along with the desired `resourceVersion` parameter to watch from. * The container `entrypoint` has been renamed to `command`, and `command` has been renamed to `args`. * Container, volume, and node resources are expressed as nested maps (e.g., `resources{cpu:1}`) rather than as individual fields, and resource values support [scaling suffixes](resources.md#resource-quantities) rather than fixed scales (e.g., milli-cores). * Restart policy is represented simply as a string (e.g., \"Always\") rather than as a nested map (\"always{}\"). * The volume `source` is inlined into `volume` rather than nested. </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-c802a37aad85dfdce2d6232f30f1e039273d58e19f8aa63b8acb725eeb2b6040", "text": "it's impossible to GET replication controllers on v3. on v1 on the same server it works fine. example request: GET on http://localhost:8080/api/v1beta3/replicationControllers returns 404 http://localhost:8080/api/v1beta1/replicationControllers returns 200\nv1beta3 moved to all lower case URL Would give that a try first Sent from my iPhone\nlooks like it's working. but it breaks backwards for clients who worked with v1. For instance, in my gem I can't now smoothly work with both versions because I need to treat the name of the resource differently. why don't at least redirect those who call replicationControllers to the lowercase too? Also, there's no way to know which resources are available and their names. A lot of REST api on their most top level at least publish the links to main resources, but if I call: http://localhost:8080/api/v1beta3/ it returns 404\nBecause we are actively trying to drop support for mixed case prior to 1.0, I did not continue supporting the old url paths. If you look at the go client, we have a \"legacy\" flag we use to control this and a few other behaviors.\nwell yes, but breaking backwards creates more work for the users... more \"if this version ...\" kind of stuff.\nWe got v1bet1/2 wrong and don't want to carry it forever. Stopping it early before v1 is our priority.\nok :( are the REST apis going through any kind of design review or code review?\nv1beta1 is really an alpha quality API. It grew organically and did not go through any kind of design review, as evidenced by the many issues you've filed. We want to get rid of it ASAP. We intend v1beta3 to be the \"release candidate\" for the v1 API, which will be the stable API. As for knowing what exists, you can now browse or GET . Additionally, pull is in progress, and will return a list of valid paths to GET .\nthanks. will check swagger for now", "commid": "kubernetes_issue_3670", "tokennum": 478}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fe567d9cf78409720bcbb87b1ad6339cb18b53dd88041da1d575419b6cc2df05", "query": "<ins> # The Kubernetes API Primary system and API concepts are documented in the [User guide](user-guide.md). Overall API conventions are described in the [API conventions doc](api-conventions.md). Complete API details are documented via [Swagger](http://swagger.io/). The Kubernetes apiserver (aka \"master\") exports an API that can be used to retrieve the [Swagger spec](https://github.com/swagger-api/swagger-spec/tree/master/schemas/v1.2) for the Kubernetes API, by default at `/swaggerapi`, and a UI you can use to browse the API documentation at `/swaggerui`. We also periodically update a [statically generated UI](http://kubernetes.io/third_party/swagger-ui/). Remote access to the API is discussed in the [access doc](accessing_the_api.md). The Kubernetes API also serves as the foundation for the declarative configuration schema for the system. The [Kubectl](kubectl.md) command-line tool can be used to create, update, delete, and get API objects. Kubernetes also stores its serialized state (currently in [etcd](https://coreos.com/docs/distributed-configuration/getting-started-with-etcd/)) in terms of the API resources. Kubernetes itself is decomposed into multiple components, which interact through its API. ## API changes In our experience, any system that is successful needs to grow and change as new use cases emerge or existing ones change. Therefore, we expect the Kubernetes API to continuously change and grow. However, we intend to not break compatibility with existing clients, for an extended period of time. In general, new API resources and new resource fields can be expected to be added frequently. Elimination of resources or fields will require following a deprecation process. The precise deprecation policy for eliminating features is TBD, but once we reach our 1.0 milestone, there will be a specific policy. What constitutes a compatible change and how to change the API are detailed by the [API change document](devel/api_changes.md). ## API versioning Fine-grain resource evolution alone makes it difficult to eliminate fields or restructure resource representations. Therefore, Kubernetes supports multiple API versions, each at a different API path prefix, such as `/api/v1beta3`. These are simply different interfaces to read and/or modify the same underlying resources. In general, all API resources are accessible via all API versions, though there may be some cases in the future where that is not true. Distinct API versions present more clear, consistent views of system resources and behavior than intermingled, independently evolved resources. They also provide a more straightforward mechanism for controlling access to end-of-lifed and/or experimental APIs. The [API and release versioning proposal](versioning.md) describes the current thinking on the API version evolution process. ## v1beta1 and v1beta2 are deprecated; please move to v1beta3 ASAP As of April 1, 2015, the Kubernetes v1beta3 API has been enabled by default, and the v1beta1 and v1beta2 APIs are deprecated. v1beta3 should be considered the v1 release-candidate API, and the v1 API is expected to be substantially similar. As \"pre-release\" APIs, v1beta1, v1beta2, and v1beta3 will be eliminated once the v1 API is available, by the end of June 2015. ## v1beta3 conversion tips We're working to convert all documentation and examples to v1beta3. Most examples already contain a v1beta3 subdirectory with the API objects translated to v1beta3. A simple [API conversion tool](cluster_management.md#switching-your-config-files-to-a-new-api-version) has been written to simplify the translation process. Use `kubectl create --validate` in order to validate your json or yaml against our Swagger spec. Some important differences between v1beta1/2 and v1beta3: * The resource `id` is now called `name`. * `name`, `labels`, `annotations`, and other metadata are now nested in a map called `metadata` * `desiredState` is now called `spec`, and `currentState` is now called `status` * `/minions` has been moved to `/nodes`, and the resource has kind `Node` * The namespace is required (for all namespaced resources) and has moved from a URL parameter to the path: `/api/v1beta3/namespaces/{namespace}/{resource_collection}/{resource_name}` * The names of all resource collections are now lower cased - instead of `replicationControllers`, use `replicationcontrollers`. * To watch for changes to a resource, open an HTTP or Websocket connection to the collection URL and provide the `?watch=true` URL parameter along with the desired `resourceVersion` parameter to watch from. * The container `entrypoint` has been renamed to `command`, and `command` has been renamed to `args`. * Container, volume, and node resources are expressed as nested maps (e.g., `resources{cpu:1}`) rather than as individual fields, and resource values support [scaling suffixes](resources.md#resource-quantities) rather than fixed scales (e.g., milli-cores). * Restart policy is represented simply as a string (e.g., \"Always\") rather than as a nested map (\"always{}\"). * The volume `source` is inlined into `volume` rather than nested. </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-22f9249afaa8c5861790bc63eab4a28e4fa1ff4ac55253dc70acafd4d0034e9c", "text": "Already we're getting bugs from people who are missing some of the more subtle conversions.\nPoint them at the conversion tool: cmd/kube-version-\nPriority? Team? Milestone?\nDone:", "commid": "kubernetes_issue_6272", "tokennum": 41}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fe615ecb605ea9cd4d39dd3f2bc4e9030d18bdc2bf65717f3edfb2f949cf2290", "query": "}, } <del> resolvConf, cleanup := getResolvConf(t) defer cleanup() </del> <ins> resolvConfContent := []byte(fmt.Sprintf(\"nameserver %snsearch %sn\", testHostNameserver, testHostDomain)) tmpfile, err := os.CreateTemp(\"\", \"tmpResolvConf\") if err != nil { t.Fatal(err) } defer os.Remove(tmpfile.Name()) if _, err := tmpfile.Write(resolvConfContent); err != nil { t.Fatal(err) } if err := tmpfile.Close(); err != nil { t.Fatal(err) } </ins> <del> configurer := NewConfigurer(recorder, nodeRef, nil, []net.IP{netutils.ParseIPSloppy(testClusterNameserver)}, testClusterDNSDomain, resolvConf) configurer.getHostDNSConfig = fakeGetHostDNSConfigCustom </del> <ins> configurer := NewConfigurer(recorder, nodeRef, nil, []net.IP{netutils.ParseIPSloppy(testClusterNameserver)}, testClusterDNSDomain, tmpfile.Name()) </ins> testCases := []struct { desc              string", "positive_passages": [{"docid": "doc-en-kubernetes-5e93ba1a338583c6193506912a68a67fcc908451a37c483694071bc120df2bcb", "text": "When a --resolv-conf (DNS resolver config) is passed to kubelet on a Windows node, the config content is used as part of sandbox initialization (through getHostDNSConfig()). Now with the recent changes (), it seems now to fail with an error like: E0315 10:22:16. 4764 ] \"Error syncing pod, skipping\" err=\"failed to \"CreatePodSandbox\" for \"img-pull-(-b40a-459d-9033-)\" with CreatePodSandboxError: \"Failed to generate sandbox config for pod \"img-pull-(-b40a-459d-9033-)\": Unexpected resolver config value: \"C:etckubernetescni\". Expected \"\" or \"Host\".\"\" pod=\"img-puller-3842/img-pull-\" podUID=-b40a-459d-9033- This is showing on all the runs of GCE testgrid (latest): Reading/using the passed resolv config on Windows Run a Windows pool with DNS resolv config being set as part of kubelet params. No response_ 27 alpha.3 1.27 beta.0 master <detailsGCE </details<details</details<details</details<details</details<details</details\n/triage accepted /milestone v1.27 /sig node /sig network\n/sig windows /cc\n/priority criticial-urgent as this is likely a release blocking\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority criticial-urgent 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\n/priority critical-urgent\nHmm, so you're setting the [1]. This PR introduced the capability to read the DNS config options from the Windows host registries while removing the capability to read from a file, introducing a regression. I've sent a PR addressing this issue: [1]\nIs the file you are pointing to a UNIX-style or something else?\nWas the file changing the behavior of the node?", "commid": "kubernetes_issue_116782", "tokennum": 565}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fe615ecb605ea9cd4d39dd3f2bc4e9030d18bdc2bf65717f3edfb2f949cf2290", "query": "}, } <del> resolvConf, cleanup := getResolvConf(t) defer cleanup() </del> <ins> resolvConfContent := []byte(fmt.Sprintf(\"nameserver %snsearch %sn\", testHostNameserver, testHostDomain)) tmpfile, err := os.CreateTemp(\"\", \"tmpResolvConf\") if err != nil { t.Fatal(err) } defer os.Remove(tmpfile.Name()) if _, err := tmpfile.Write(resolvConfContent); err != nil { t.Fatal(err) } if err := tmpfile.Close(); err != nil { t.Fatal(err) } </ins> <del> configurer := NewConfigurer(recorder, nodeRef, nil, []net.IP{netutils.ParseIPSloppy(testClusterNameserver)}, testClusterDNSDomain, resolvConf) configurer.getHostDNSConfig = fakeGetHostDNSConfigCustom </del> <ins> configurer := NewConfigurer(recorder, nodeRef, nil, []net.IP{netutils.ParseIPSloppy(testClusterNameserver)}, testClusterDNSDomain, tmpfile.Name()) </ins> testCases := []struct { desc              string", "positive_passages": [{"docid": "doc-en-kubernetes-a55794e1d2c420cf7484c297920657922704eb45d045ae8237364febdd60d634", "text": "Yeah, what used on GCE/GKE, seems to be a Linux-like conf, eg: nameserver 10.128.0.1 search c.<project_name.internal google.internal ` We haven't tried to remove from kubelet to see the behavior.\nThis Issue/PR has been marked as release blocker. Please have the fix merged by eod today otherwise the feature has to be reverted. For the Issue/PR owner: please have a revert/feature disable PR open today in case the fix failed to get in. Thank you! See the -- Kubernetes 1.27 release manager\nI opened up a revert PR in case this PR does not merge by code freeze.\nThanks for the resolution! both 2019 and 2022 grids seems to be back to green now!\nThanks for confirming! I opened to ensure gets updated too", "commid": "kubernetes_issue_116782", "tokennum": 185}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fe6ea681b06ea1488875f2efa43792cd90e0aa823b784a94af1bc84fb6c69146", "query": "useCustomImsCache: true, expectedErrMsg:    fmt.Errorf(\"getError\"), }, <del> { name:           \"NodeAddresses should report error if VMSS instanceID is invalid\", nodeName:       \"vm123456\", metadataName:   \"vmss_$123\", providerID:     \"azure:///subscriptions/subscription/resourceGroups/rg/providers/Microsoft.Compute/virtualMachines/vm1\", vmType:         vmTypeVMSS, expectedErrMsg: fmt.Errorf(\"failed to parse VMSS instanceID %q: strconv.ParseInt: parsing %q: invalid syntax\", \"$123\", \"$123\"), }, </del> } for _, test := range testcases {", "positive_passages": [{"docid": "doc-en-kubernetes-93c0a615d6725c12b66abb2dead01e17ca700d451119b1467d3edce68f73a013", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: If computer name prefix does not match VMSS name, then Azure cloud provider will use VMSS API instead of using metadata service data. This leads to throttling, because every affected kubelet is making API requests. What you expected to happen: Azure cloud provider should use metadata service data instead of calling VMSS API when instance is current. How to reproduce it (as minimally and precisely as possible): Set computer name prefix of the VMSS to something different than default. You should observe Azure provider making requests to the VMSS API rather than using metadata service, which leads to throttling if you have multiple kubelets with this bug. Anything else we need to know?: This is bug was introduced by - returns false even if instance is current, because it expects node name to match VMSS name + instance id, however node name is derived from the computer-name-prefix which can be different than VMSS name. Node name should be matched against , not against . Environment: Kubernetes version (use ): 1.18.x and higher Cloud provider or hardware configuration: azure /sig cloud-provider\n/sig cloud-provider\n/area provider/azure\nCC\n/remove-sig cloud-provider /sig cloud-provider (trying to remove the label)\n/sig cloud-provider\nThanks for the reporting. Unfortunately, computer name prefix is not included in IMDS, so it can't be used without VMSS API for constructing the NodeName. Would check what could we do to workaround the issue.\nCan you memorize the computer name prefix in the first request to the Azure API and then use it for the isCurrentInstance check?\nopened to fix the issue. Would you like to have a look?\nI can confirm that your change should fix the problem I reported. Do you know if your fix will be to 1.18.x?\nis working on the cherry pick\nThank you for quick fix!", "commid": "kubernetes_issue_92733", "tokennum": 464}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fe76167d8ae3d15798dd16b90dfdbba3d89fdb02cf02abbc63ab856aefb5bd69", "query": "// +listType=map // +listMapKey=name // +optional <del> Variables []Variable `json:\"variables\" patchStrategy:\"merge\" patchMergeKey:\"name\" protobuf:\"bytes,7,rep,name=variables\"` </del> <ins> Variables []Variable `json:\"variables,omitempty\" patchStrategy:\"merge\" patchMergeKey:\"name\" protobuf:\"bytes,7,rep,name=variables\"` </ins> } // ParamKind is a tuple of Group Kind and Version.", "positive_passages": [{"docid": "doc-en-kubernetes-f7dbb3a7bd33f39ed155e3c1ad6b8c55c94743d34cf8c863dee73b5ba5ef4403", "text": "spec.variables should be marked omitempty. I'm trying to create a validating admission policy that uses in v1.27 as follows: I'm setting : to \"Strict\" in CreateOptions so that the server will reject requests with unknown fields but it complains that the don't exist in v1.27 and it does make sense because this field was introduced in v1.28: I'm using a 1.28 client.\n/sig api-machinery\n/assign\n/assign /triage accepted\nThanks for raising this! /cc", "commid": "kubernetes_issue_120491", "tokennum": 117}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fe7d5cf580fb63e809a501c6d500e8b5dfd74f13d1a63f513e748afe0b37534d", "query": "return len(br) } <ins> // Less breaks ties first by creation timestamp, then by name </ins> func (br byRevision) Less(i, j int) bool { <ins> if br[i].Revision == br[j].Revision { if br[j].CreationTimestamp.Equal(&br[i].CreationTimestamp) { return br[i].Name < br[j].Name } return br[j].CreationTimestamp.After(br[i].CreationTimestamp.Time) } </ins> return br[i].Revision < br[j].Revision }", "positive_passages": [{"docid": "doc-en-kubernetes-4d5dc3f2fd1aa2418695125e98dd263b9bbd4b25db7ea8b25723d335bfe8c79b", "text": "<!-- This form is for bug reports and feature requests ONLY! If you're looking for help check and the . --Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: Statefulsets are sometimes continually rolling pods and I don't know why statefulset created: storageclass referenced: kubectl describe statefulset statefulset-test: As you can see from the above describe, the pod in the statefulset has been restarted a lot of times. Observing the created pod, 1) The pod comes up ready 2) immediately transitions to terminating 3) Is terminated 4) A new pod is created 5) Go back to (1) (repeats forever) Despite no updates to the statefulset spec ocurring. Making a change to the statefulset template (for example a trivial change adding a nonsense annotation) stops the rolling and fixes the issue When this statefulset was created, there was a mutating webhook enabled. After the observed pod rolling. I disabled this by making its configuration invalid and making it non required, and the rolling persisted. The status of the statefulset: : You can see that there is a discrepency between currentRevision and updateRevision. currentRevision: statefulset-test- updateRevision: statefulset-test- A short while later the status is changed to contain currentRevision: statefulset-test- updateRevision: statefulset-test- This change happened at Sun Apr 1 19:48:48 2018 Presumably after the rollout of statefulset-test- is complete.", "commid": "kubernetes_issue_61998", "tokennum": 342}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fe7d5cf580fb63e809a501c6d500e8b5dfd74f13d1a63f513e748afe0b37534d", "query": "return len(br) } <ins> // Less breaks ties first by creation timestamp, then by name </ins> func (br byRevision) Less(i, j int) bool { <ins> if br[i].Revision == br[j].Revision { if br[j].CreationTimestamp.Equal(&br[i].CreationTimestamp) { return br[i].Name < br[j].Name } return br[j].CreationTimestamp.After(br[i].CreationTimestamp.Time) } </ins> return br[i].Revision < br[j].Revision }", "positive_passages": [{"docid": "doc-en-kubernetes-25284c3702a45280c2a40fae68a3ba4d1c026c9e5d96ab43c2dee09fe3985aa0", "text": "Here are all the controllerrevisions from above: kubectl get controllerrevision statefulset-test- -o yaml kubectl get controllerrevision statefulset-test- -o yaml: kubectl get controllerrevision statefulset-test- -o yaml: The differences between the above controllerrevisions are insignificant (the hash, the creation timestamp, the name, the resource version, the uid, the self link) Interestingly all these controllerrevisions were created very close together in time shortly after I created the statefulset The current controllerrevisions are After watching the state change for a while, it actually seems like the statefulset is just cycling through the updateRevision being one of the above 10 controllerrevisions Leaders during this time From kube-controller-manager logs during this time, here is one excerpt: The error sync in there is suspicous, and as you can see the controllerrevisions are changing in the logs I have the full logs from a 5 minute window on either side of the above if necessary. The reason I'm inclined to think this is a kubernetes bug is that any update to the statefulset template fixes the problem. How to reproduce it (as minimally and precisely as possible): Not really sure. Worth just trying to create the above statefulset (requires creating the I tried deleting and recreating the above statefulset and it didn't happen, so something flaky is going on Anything else we need to know?: kubernetes 1.9.3 (client and server) cloud provider: aws\n/sig apps\nI realize this will probably need some further debugging, happy to get some direction\nConsistent repro: Create a statefulset that creates a controllerrevision whose hash is between max int32 and max uint32 (this shouldn't be that hard to do, possibly a 50/50 chance of this). Manually create a controllerrevision identical to the first (same revision), incrementing both the name and hash by one. See that the statefulset controller will continually switch which controller revision should be the target of the statefulset.\nDue to the issue fixed here: , under some circumstances controllerrevisions whose revision is the same were being considered equal.", "commid": "kubernetes_issue_61998", "tokennum": 496}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fe7d5cf580fb63e809a501c6d500e8b5dfd74f13d1a63f513e748afe0b37534d", "query": "return len(br) } <ins> // Less breaks ties first by creation timestamp, then by name </ins> func (br byRevision) Less(i, j int) bool { <ins> if br[i].Revision == br[j].Revision { if br[j].CreationTimestamp.Equal(&br[i].CreationTimestamp) { return br[i].Name < br[j].Name } return br[j].CreationTimestamp.After(br[i].CreationTimestamp.Time) } </ins> return br[i].Revision < br[j].Revision }", "positive_passages": [{"docid": "doc-en-kubernetes-59ace9008f72ca5d82f22a23445c41e6f5a4a98690d88922022af0dc9f3faebe", "text": "This ends up causing this bug to manifest as follows: ListRevisions finds many controllerrevisions with the same revision (unclear how this state happens, but it can happen) The sort here randomly sorts them Due to the linked bug , FindEqualRevisions incorrectly finds that all these controller revisions are equal to the proposed udpate. The updateRevision selects the last revision found here Therefore, updateRevision, is randomly selected and causes the bug. This fixes the immediate issue, but the sort should probably be made stable (i.e not just look at the revision number, perhaps just consider the hash for tie breakers)\nAs an update, fixing the equality check will not be sufficient because it is possible for multiple controller revisions to be created that are actually equal, including the same hash, that have the same revision number. I believe the fix will need to be equal controllerrevisions with the same revision number from being created sort the controllerrevisions so that the controllerrevision that is the target of the statefulset is stable\nIssues 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\n/remove-lifecycle stale\nping I use the K8S which version is 1.11.4 and encounter the same problem. I want to reproduce the problem and find your way: Manually create a controllerrevision identical to the first (same revision), incrementing both the name and hash by one. Could you tell me how to mannually create a same controllerrevision identical to the first? Thanks in anvance.", "commid": "kubernetes_issue_61998", "tokennum": 374}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fe8f820400f1edc5d05f4f6403cece3f14d841eec9396013f16753e8c8aa16bf", "query": "<ins> DOCKER_OPTS=\"\" </ins> {% if grains.docker_opts is defined %} <del> {% set docker_opts = grains.docker_opts %} {% else %} {% set docker_opts = \"\" %} </del> <ins> DOCKER_OPTS=\"${DOCKER_OPTS} {{grains.docker_opts}}\" </ins> {% endif %} <del> DOCKER_OPTS=\"{{docker_opts}} --bridge cbr0 --iptables=false --ip-masq=false -r=false\" </del> <ins> DOCKER_OPTS=\"${DOCKER_OPTS} --bridge cbr0 --iptables=false --ip-masq=false -r=false\" </ins>", "positive_passages": [{"docid": "doc-en-kubernetes-142e8decd8d12f564814b0a08026ec0c2500ddcd8040f0182edc6a7f51b222f8", "text": "0/8 is with a company's intranet, so it can be insecure. This is similiar to \"For GCE, allow insecure registries anywhere in 10.0.0.0/8\" Thanks!\nLinking to and .\nThis was", "commid": "kubernetes_issue_2807", "tokennum": 55}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fe96420bd3c7c731cfd4aea2e5a3c852aa2f473c0f9243d695f26a84f2918450", "query": "# Downloaded kubernetes binary release tar ball kubernetes.tar.gz <del> # generated files in any directory # TODO(thockin): uncomment this when we stop committing the generated files. #zz_generated.* zz_generated.openapi.go </del> <ins> # Phony test files used as part of coverage generation </ins> zz_generated_*_test.go <del> # TODO(roycaihw): remove this when we stop committing the generated definition !staging/src/k8s.io/apiextensions-apiserver/pkg/generated/openapi/zz_generated.openapi.go !staging/src/k8s.io/kube-aggregator/pkg/generated/openapi/zz_generated.openapi.go # low-change blueprint in code-generator to notice changes !staging/src/k8s.io/code-generator/examples/apiserver/openapi/zz_generated.openapi.go # low-change sample-apiserver spec to be compilable when published !staging/src/k8s.io/sample-apiserver/pkg/generated/openapi/zz_generated.openapi.go </del> # make-related metadata /.make/", "positive_passages": [{"docid": "doc-en-kubernetes-72f2121d9c00ea31717a3620ac148f7960937c4f1fc6a8c75433d9055d46cc48", "text": "Checked in: Not checked in: Can anyone explain why?\nones published outside k/k that are in libraries/modules expected to be usable without running custom code generation steps are checked in\nexample issue: there were similar issues with other instances\n/triage accepted\nI guess I am asking why not check in\noh, I'd be in favor of that :)\ndownstream users very often end up realizing that we warn folks not to use ( ) because they go looking for why this file is not checked in. This paper cut makes people realize that they are doing something that we don't want them to do. (not arguing for or against, just stating where this was effective before)\nI think the v0.0.0 local replace directives in accomplish similar things w.r.t. making people go digging about friction using k/k as a library", "commid": "kubernetes_issue_107625", "tokennum": 173}], "negative_passages": []}
{"query_id": "q-en-kubernetes-feaf310fbf1b6e9f34b0a68c0ede7fb60ed6a0c35f828c7279e02ee3f940300e", "query": "EXPOSE 2379 2380 4001 7001 <ins> WORKDIR C:/usr/local/bin </ins> COPY etcd* etcdctl* /usr/local/bin/ COPY migrate-if-needed.bat /usr/local/bin/ COPY migrate /usr/local/bin/migrate.exe", "positive_passages": [{"docid": "doc-en-kubernetes-0635574d21f9ddc47e43e2c6f74baefafb7ed59d6808398eff3b67c17fc82a45", "text": "build only 2 runs are available. ERROR: () build -dd5a-468e-9a7a- completed with status \"FAILURE\" \u001b[33m1 warning found (use --debug to expand): \u001b[0m - InvalidDefaultArgInFrom: Default value for ARG ${RUNNERIMAGE} results in empty or invalid base image name (line 16) Dockerfile.windows:22 20 | COPY etcd etcdctl /usr/local/bin/ 21 | COPY migrate-if- /usr/local/bin/ 22 | COPY migrate 23 | 24 | # NOTE(claudiub): docker buildx sets the PATH env variable to a Linux-like PATH, ERROR: failed to solve: mkdir /var/lib/buildkit/runc-overlayfs/cachemounts/buildkit3627953617/usr/local/bin: not a directory make[1]: Leaving directory '/workspace/cluster/images/etcd' make[1]: [Makefile:132: build] Error 1 make: [Makefile:217: sub-push-image-windows-amd64-1809] Error 2 ERROR ERROR: build step 0 \"\" failed: step exited with non-zero status: 2\n2024/07/25 02:39:53 Failed to run some build jobs: [error running [gcloud builds submit --verbosity info --config The etcd 3.5.15 post CI failed to build the image. needs to promote the image: This is post submit CI for /sig release etcd\n/cc\ncan you please try this?\ncc Folks, We could use your help fixing the etcd image for windows!\n/triage accepted /priority important-soon\nactually passed in", "commid": "kubernetes_issue_126348", "tokennum": 392}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fef182742fa73788d0e84559094ae552984664c9789cc551608b6db19a16cc32", "query": "}{ { expected: api.VolumeMount{ <del> Name:      \"pki\", </del> <ins> Name:      \"k8s\", </ins> MountPath: \"/etc/kubernetes/\", ReadOnly:  true, },", "positive_passages": [{"docid": "doc-en-kubernetes-aa0efe62d493b3611250d6c4d1b34c71d8fe0e732e78e4445af443d5c2b2f03c", "text": "<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.--What keywords did you search in Kubernetes issues before filing this one? controller /etc/ssl/certs kubeadm /etc/ssl/certs Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT <!-- If this is a BUG REPORT, please: Fill in as much of the template below as you can. If you leave out information, we can't help you as well. If this is a FEATURE REQUEST, please: Describe in detail the feature/behavior/change you'd like to see. In both cases, be ready for followup questions, and please respond in a timely manner. If we can't reproduce a bug or think a feature already exists, we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why. --Kubernetes version (use ): 5 custom built master I also use a custom built hyperkube image instead of the single app images for apiserver, controller, ... Environment: Cloud provider or hardware configuration: azure OS (e.g. from /etc/os-release): CentOS 7.2 Kernel (e.g. ): Linux ma-kub8ms0 3.10.0-327.36.3.el7.x8664 SMP Mon Oct 24 16:09:20 UTC 2016 x8664 x8664 x8664 GNU/Linux Install tools: kubeadm Others: deployed with Azure RM template and ansible What happened: controller is not able to do https, including calls to the Azure RM API What you expected to happen: https should work as usual How to reproduce it (as minimally and precisely as possible): Use kubeadm to install kubernetes on CentOS exec into the controller and try \"curl \" Anything else do we need to know: It looks like caused this issue. On CentOS, I see these files on the host OS: I suspect the symlinks to /etc/pki/... being the problem here, as they are not available inside the hyperkube Debian image. I also tried to verify this with It seems to not be based on Debian and thus gives a different error: I see 2 possible solutions: of host mounting /etc/ssl/certs into the controller pod, the ca certificates could be installed into the image.", "commid": "kubernetes_issue_36150", "tokennum": 529}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fef182742fa73788d0e84559094ae552984664c9789cc551608b6db19a16cc32", "query": "}{ { expected: api.VolumeMount{ <del> Name:      \"pki\", </del> <ins> Name:      \"k8s\", </ins> MountPath: \"/etc/kubernetes/\", ReadOnly:  true, },", "positive_passages": [{"docid": "doc-en-kubernetes-41c6565c36e0283a9e2054713b809a870281386c810e77c1faf5476befe20dbf", "text": "This is already done for hyperkube and would work out of the box when the host mount would be omitted. could try to figure out if /etc/pki should also be host mounted and add this to the controller manifest if required. I'd be happy to provide a fix by myself, I just need to know which solution you would prefer.\nSame problem seems to apply to the apiserver. Not sure however if it actually does https calls.\nimplements solution 2.\nThis issue was moved to kubernetes/kubeadm", "commid": "kubernetes_issue_36150", "tokennum": 111}], "negative_passages": []}
{"query_id": "q-en-kubernetes-fefa3bdc49b8af56fdf7c0009763645d4cef3b1dc70a58e932a40b134322da0a", "query": "fifo := cache.NewDeltaFIFO(cache.MetaNamespaceKeyFunc, nil, downstream) // Let's do threadsafe output to get predictable test results. <del> outputSetLock := sync.Mutex{} outputSet := util.StringSet{} </del> <ins> deletionCounter := make(chan string, 1000) </ins> cfg := &framework.Config{ Queue:            fifo,", "positive_passages": [{"docid": "doc-en-kubernetes-20ba07f969c78351406740c712da4b4d48c539c847c31f97f90729edba71a7c4", "text": "From shippable, I noticed there are several failed cases, for example, E0413 17:34:38. ] watch of *api.Pod ended with: Stop requested --- FAIL: Example (0.61s) got: want: a-hello b-controller c-framework FAIL coverage: 85.9% of statements FAIL 7.652s cc/\nanother example:\nah-- this is a different thing. I will fix this, too.\nI'm seeing this from an unrelated change\nYeah I think that's the one I expected to see.", "commid": "kubernetes_issue_6777", "tokennum": 121}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ff27ed26835e4e73c8ed77068b0bb07f1b03eac9af8dc0e81d9bdce7477b7ae9", "query": "} output, err := json.Marshal(agg) require.NoError(t, err) <del> // Content-type is \"aggregated\" discovery format. w.Header().Set(\"Content-Type\", AcceptV2Beta1) </del> <ins> // Content-type is \"aggregated\" discovery format. Add extra parameter // to ensure we are resilient to these extra parameters. w.Header().Set(\"Content-Type\", AcceptV2Beta1+\"; charset=utf-8\") </ins> w.WriteHeader(http.StatusOK) w.Write(output) }))", "positive_passages": [{"docid": "doc-en-kubernetes-3257ecff81fbc60fa2a8f982346c462089eb7c896f62cce1d4e02ff6df66d913", "text": "We are using (and ) to interact with Kubernetes clusters behind a couple of proxy layers. One of these proxies completes the headers to include character encoding details. This was working fine until recently, when client-go/kubectl have started to fail when interacting with the discovery API. It seems that a recent change has made kubectl more restrictive of the content-type that it expects. I suspect that it is related to this commit: For example, this is an error from a kubectl command: We can of course try to fix it on our end, removing that charset information. However, it is a valid content-type and the way kubectl is handling the content-type there seems like it is relying on implementation details of kube-apiserver (that it does not add metadata to the content-type). I propose to fix this issue in , by properly parsing and handling the content-type.\ncc /kind regression /kind bug /sig api-machinery /priority important-soon looks like the switch statement in downloadLegacy() needs to be more tolerant of the variety of content-types it can get from a server (including text/plain or no content-type if old servers could have returned that...)\n/transfer kubernetes/kubernetes\nSomething went wrong or the destination repo kubernetes/kubernetes/kubernetes does not exist. <detailsIn response to : /transfer kubernetes/kubernetes 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\n/transfer kubernetes\nYep, the string comparison for the content-type is flimsy, let's address that. Thanks for the report!\n/assign\n/triage accepted\n/cc\nThe fix is being cherry-picked back to: : :", "commid": "kubernetes_issue_117562", "tokennum": 408}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ff40ad39cb54ef746f3c01e40f700b6cfdbf2c866e5ce8e5c0ec0fc25d054c54", "query": "If you have questions or want to start contributing please reach out.  We don't bite! <del> The Kubernetes team is hanging out on IRC on the [#google-containers channel on freenode.net](http://webchat.freenode.net/?channels=google-containers).  We also have the [google-containers Google Groups mailing list](https://groups.google.com/forum/#!forum/google-containers) for questions and discussion as well as the [kubernetes-announce mailing list](https://groups.google.com/forum/#!forum/kubernetes-announce) for important announcements (low-traffic, no chatter). </del> <ins> The Kubernetes team is hanging out on IRC on the [#google-containers channel on freenode.net](http://webchat.freenode.net/?channels=google-containers). This client may be overloaded from time to time. If this happens you can use any [IRC client out there](http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) to talk to us. We also have the [google-containers Google Groups mailing list](https://groups.google.com/forum/#!forum/google-containers) for questions and discussion as well as the [kubernetes-announce mailing list](https://groups.google.com/forum/#!forum/kubernetes-announce) for important announcements (low-traffic, no chatter). </ins> If you are a company and are looking for a more formal engagement with Google around Kubernetes and containers at Google as a whole, please fill out [this form](https://docs.google.com/a/google.com/forms/d/1_RfwC8LZU4CKe4vKq32x5xpEJI5QZ-j0ShGmZVv9cm4/viewform) and we'll be in touch.", "positive_passages": [{"docid": "doc-en-kubernetes-84aabe4fdfca214c63d40e53a4b999fdb647fe5392c3ce898f956f6c961b8068", "text": "POD is OOM. k8s v1.19.4+docker is OK. but v1.21+cri-o+buildah does not work properly. Why the limits are not effective.Not the container limit memory, It's physical memory centos7 kernel use limits memory use -XX:+UseContainerSupport Cannot read memory.limitinbytes k8s version cri-o version buildah version oracleJdk or openjdk have same problem It is normal to use xms and Xmx\n/sig node\nSupplement v19+docker v21+cri-o+buildah\n/assign taking a look, thanks for opening the issue\nseems relevant, have you checked your kernel supports the memory cgroup (I know docker does work, but let's sanity check first) I checked on my machine (fedora 34) and successfully can see usageinbytes in a container on our latest 1.22 branch. also, attaching the crio logs will likely help me debug\nalso curious about the runc version\ncri-o logs runc Looks like a problem with cgroup v1\nhm the memory cgroup seems to be enabled. what is the image you're using?\ncentos7.9.2009\n/triage needs-information\nwhat cgroup manager are you using?\nkubeadm kubectl config crio ps aux|grep kubelet\nI seem to have found this bug Delete the following two items to return to normal. deployment\nthat is unexpected... Great find!\nDoes the problem manifest if either are different? (hostNetwork: false, but dnsPolicy ClusterFirstWithHostNet)\nhostNetwork: true hostNetwork: false delete hostNetwork and dnsPolicy\nRocky 8.4, kernel-5.4, kubernetes v1.21.4 has the same problem\nah! I found the issue\nthanks for your patience\nIs crio 1.21.3 fixed? This problem still occurs after the upgrade. Branch v1.21.3 did not see the commit\nno the initial PR hasn't merged yet, I will try to revive it\nsorry this fell through the cracks, I'll try to get this through ASAP\nwill get it in 1.22.1. is that sufficient or would you like it backported to 1.21?", "commid": "kubernetes_issue_104034", "tokennum": 507}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ff40ad39cb54ef746f3c01e40f700b6cfdbf2c866e5ce8e5c0ec0fc25d054c54", "query": "If you have questions or want to start contributing please reach out.  We don't bite! <del> The Kubernetes team is hanging out on IRC on the [#google-containers channel on freenode.net](http://webchat.freenode.net/?channels=google-containers).  We also have the [google-containers Google Groups mailing list](https://groups.google.com/forum/#!forum/google-containers) for questions and discussion as well as the [kubernetes-announce mailing list](https://groups.google.com/forum/#!forum/kubernetes-announce) for important announcements (low-traffic, no chatter). </del> <ins> The Kubernetes team is hanging out on IRC on the [#google-containers channel on freenode.net](http://webchat.freenode.net/?channels=google-containers). This client may be overloaded from time to time. If this happens you can use any [IRC client out there](http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) to talk to us. We also have the [google-containers Google Groups mailing list](https://groups.google.com/forum/#!forum/google-containers) for questions and discussion as well as the [kubernetes-announce mailing list](https://groups.google.com/forum/#!forum/kubernetes-announce) for important announcements (low-traffic, no chatter). </ins> If you are a company and are looking for a more formal engagement with Google around Kubernetes and containers at Google as a whole, please fill out [this form](https://docs.google.com/a/google.com/forms/d/1_RfwC8LZU4CKe4vKq32x5xpEJI5QZ-j0ShGmZVv9cm4/viewform) and we'll be in touch.", "positive_passages": [{"docid": "doc-en-kubernetes-5b183b7c89c3db39645de6f41384495ddabd41009f9474756ae64b18b81d7478", "text": "Thank you Both are OK, I currently use java -xmx instead.I will update in the next version. Preferably v1.21, v1.22 version I will upgrade later.\nI've opened as well :)\n/remove-triage needs-information /triage accepted /close as this is being tracked as a CRI-O bug\nClosing this issue. <detailsIn response to : /remove-triage needs-information /triage accepted 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", "commid": "kubernetes_issue_104034", "tokennum": 129}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ff6cbd9a0afafde0b71b39c7567f5fa26fef06b47c989d69348cf657be0580cc", "query": "var notMnt bool var err error if extensiveMountPointCheck { <del> notMnt, err = IsNotMountPoint(mounter, mountPath) </del> <ins> notMnt, err = mounter.IsNotMountPoint(mountPath) </ins> } else { notMnt, err = mounter.IsLikelyNotMountPoint(mountPath) }", "positive_passages": [{"docid": "doc-en-kubernetes-4bcfc015d2b9d9fa1e84475a3e08fb9ef8299b4e5f821f790188ad7bdae6ecbc", "text": "<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--What happened: There's , and . The former is used by local and nfs volume plugins, while the latter is used by , which is also used by local and nfs volume plugins. What you expected to happen: Can we consolidate these? This is really confusing and could easily be the source of bugs. <!-- DO NOT EDIT BELOW THIS LINE --/kind cleanup\ncc\n/assign I'd like to clean up code.", "commid": "kubernetes_issue_72387", "tokennum": 133}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ffa42b8d7ffb77b2d5b2a9e41359720876eff709bf2b63221f4df3d8cdeb03a4", "query": "import ( \"fmt\" \"os\" <ins> \"sort\" </ins> \"strings\" \"github.com/spf13/cobra\"", "positive_passages": [{"docid": "doc-en-kubernetes-38c129cdce20cdb2ede95770ab1d3483b461da6e2945915e074275e9575e4c1c", "text": "Similar to issue , building kubernetes1.23 resulted in 1 variation: builds should be fully determined by inputs on openSUSE or Debian, This bug was found while working on . <details23.0 </details<details</details<details</details<details</details<details</details<details</details\n/sig release /area build-release\n/assign\n/sig cli\n/triage accepted /assign", "commid": "kubernetes_issue_108245", "tokennum": 94}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ffadf208832ed9b44182bdcdb9d4cadf431b7f2f48d87bb5ec5356359efc00c7", "query": "if err != nil { framework.Logf(\"Failed to delete adapter deployment file: %s\", err) } <del> cleanupClusterAdminBinding(namespace) </del> <ins> cleanupClusterAdminBinding() </ins> } <del> func cleanupClusterAdminBinding(namespace string) { stat, err := framework.RunKubectl(namespace, \"delete\", \"clusterrolebinding\", ClusterAdminBinding) </del> <ins> func cleanupClusterAdminBinding() { stat, err := framework.RunKubectl(\"\", \"delete\", \"clusterrolebinding\", ClusterAdminBinding) </ins> framework.Logf(stat) if err != nil { framework.Logf(\"Failed to delete cluster admin binding: %s\", err)", "positive_passages": [{"docid": "doc-en-kubernetes-cecee0a132f84dbf6d5783d328e94b49c8666ebba8eef4ded1687e53b0451e97", "text": "/kind failing-test <!-- If this is a flake, please add: /kind flake --/sig autoscaling Looks like it just started happening today (@ 2020-09-15 03:54:19 +0000 UTC) !\ncc the namespace from the provided object \"kube-system\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=kube-system' to perform this operation. the namespace from the provided object \"custom-metrics\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=custom-metrics' to perform this operation. the namespace from the provided object \"custom-metrics\" does not match the namespace \"horizontal-pod-autoscaling-830\". You must pass '--namespace=custom-metrics' to perform this operation.\nrelated fix:\nNo I don't think that's the fix for this (that is just a little cleanup). Actually I think we have to delete namespace parameter in line : Because before , the will have no actually effect. But now with the change of , it will have namespace : at the end of the command. But the namespace in yaml file is which is different from . We should not have parameter when applying from file because this test didn't have before, right? Related PR:\n/assign", "commid": "kubernetes_issue_94809", "tokennum": 318}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ffd75e950e3acba300669c082557ae1dd3fac98677e61f852102c6ecd50bd855", "query": "}, }, SchemaProps: spec.SchemaProps{ <del> Description: \"List of ports to expose from the container. Exposing a port here gives the system additional information about the network connections a container uses, but is primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default \"0.0.0.0\" address inside a container will be accessible from the network. Cannot be updated.\", </del> <ins> Description: \"List of ports to expose from the container. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default \"0.0.0.0\" address inside a container will be accessible from the network. Modifying this array with strategic merge patch may corrupt the data. For more information See https://github.com/kubernetes/kubernetes/issues/108255. Cannot be updated.\", </ins> Type:        []string{\"array\"}, Items: &spec.SchemaOrArray{ Schema: &spec.Schema{", "positive_passages": [{"docid": "doc-en-kubernetes-754763163ccf179fd132c393411aa2d267e649990c98a81bb38938ec6debc8b2", "text": "The comments in says that : However there are several cases where this is false : When using a Service with a targetPort that references a name in the ports arrays of the pod. Some software (ab)uses this API to get which ports are used (See Although unfixable, my goal is to fix the documentation so other people don't have the same problem). The Azure Load Balancer implementation does this for instance. Some other network/security software might use this information. Also, is it possible to document/reference the above issue in the comment ? Since it is described as informational I expected for the network to work without this information. But it's definitely not the case. Not needed since it's mostly a doc issue. I'm interested in contributing this patch but would like some feedbacks before doing it. :) <details</details<details</details<details</details<details</details<details</details<details</details\n/sig network\n/triage accepted -- thoughts? I believe the doc are due for a refresh.\nI'd take this one. /assign\nI didn't see that you wanted to do this patch, I am very sorry and now I unassign it. /unassign\nNo worries But I'm still not sure where / what to add. Should I only fix the part saying it is only informational ? Is there anything else ? (cc\nThe 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]:\n/remove-lifecycle stale", "commid": "kubernetes_issue_108255", "tokennum": 435}], "negative_passages": []}
{"query_id": "q-en-kubernetes-ffe304c79f860ba60bab5beae2f53125b8ee6474edfc4a2179f955d021396ebf", "query": "network_mode: openvswitch networkInterfaceName: eth1 etcd_servers: $MASTER_IP <ins> api_servers: $MASTER_IP </ins> cloud: vagrant cloud_provider: vagrant roles:", "positive_passages": [{"docid": "doc-en-kubernetes-8f6e6c1f685c98cc169477efadd1a12031a77645ead6fa9fa244a9ca04430443", "text": "is sent as a fix. cc It's a test failure reported by the publishing robot.\nThe line it fails at:\nIt looks like a vendor copy vs gopath copy issue.\nOne possible fix is removing from the vendor/ directory. I'm testing locally.\nConfirmed removing from the vendor/ directory fixed the test in robot.\nWe need to add the \"issue filer\" feature to the publishing robot, we can't rely on to report robot issues everytime :P I'm just not sure how long the publishing robot will be needed (i.e., when we will get rid of the staging/ directory) so not sure whether we should invest more time on the robot.", "commid": "kubernetes_issue_45693", "tokennum": 141}], "negative_passages": []}