jiebi/CodeConvo huggingface dataset:
Code change:
service.beta.kubernetes.io/aws-load-balancer-security-groups: "sg-53fae93f" # A list of existing security groups to be configured on the ELB created. Unlike the annotation <del> # service.beta.kubernetes.io/aws-load-balancer-extra-security-groups, this replaces all other security groups previously assigned to the ELB and also overrides the creation </del> <ins> # service.beta.kubernetes.io/aws-load-balancer-extra-security-groups, this replaces all other security groups previously assigned to the ELB and also overrides the creation </ins> # of a uniquely generated security group for this ELB. # The first security group ID on this list is used as a source to permit incoming traffic to target worker nodes (service traffic and health checks). # If multiple ELBs are configured with the same security group ID, only a single permit line will be added to the worker node security groups, that means if you delete any

Related discussion:
text: This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: marks the userspace kube-proxy as deprecated. This was missed from the v1.23 docs updates and . Proposed Solution: Mark the kube-proxy in userspace mode as deprecated. Page to Update: <!--Additional Information:--/sig network /language en /priority important-longterm
/lifecycle frozen /triage accepted
/assign
Code change:
(backward-compatible) changes to the way the Kubernetes cluster DNS server processes DNS queries, to facilitate the lookup of federated services (which span multiple Kubernetes clusters). <del> See the [Cluster Federation Administrators' Guide](/docs/admin/federation/index.md) for more </del> <ins> See the [Cluster Federation Administrators' Guide](/docs/admin/federation) for more </ins> details on Cluster Federation and multi-site support. ## References

Related discussion:
text: I wish /docs/getting-started-guides/docker/ I wish this page existed
Code change:
(backward-compatible) changes to the way the Kubernetes cluster DNS server processes DNS queries, to facilitate the lookup of federated services (which span multiple Kubernetes clusters). <del> See the [Cluster Federation Administrators' Guide](/docs/admin/federation/index.md) for more </del> <ins> See the [Cluster Federation Administrators' Guide](/docs/admin/federation) for more </ins> details on Cluster Federation and multi-site support. ## References

Related discussion:
text: I wish /docs/admin/dns/ linked correctly to the federation guide, at
Code change:
<br> <br> {{ end }} <ins> </div> </ins> </div> {{ end }}  No newline at end of file

Related discussion:
text: ~This is Support~ In the , i am able to see under Kubernetes Documentation. Respective tiled content buttons are aligned respective the content length or size. As a user , i would like to see them aligned as a bordered tile content with buttons are aligned look like a row irrespective of tile content length. This improves the user experience Please let me know if drawings are needed to understand.So that i can take a capture of it and attach.
/area web-development /kind cleanup a mockup would be useful
/priority awaiting-more-evidence (adjust this once the discussion has made it clear)
- PFA.It is screenshot of button aligned.I have the tile border which is not the primary objective though(Just to border line the content) ! Hope this mockup helps.
/remove-priority awaiting-more-evidence /priority backlog
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /close
Closing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/reopen /lifecycle frozen /retitle Poor alignment between tiles and buttons on home page for docs
Reopened this issue. <detailsIn response to : /reopen /lifecycle frozen /retitle Poor alignment between tiles and buttons on home page for docs Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/remove-kind cleanup /triage accepted
Code change:
* `apiserver_flowcontrol_rejected_requests_total` is a counter vector (cumulative since server start) of requests that were rejected, <del> broken down by the labels `flowSchema` (indicating the one that matched the request), `priorityLevel` (indicating the one to which </del> <ins> broken down by the labels `flow_schema` (indicating the one that matched the request), `priority_level` (indicating the one to which </ins> the request was assigned), and `reason`.  The `reason` label will be have one of the following values: * `queue-full`, indicating that too many requests were already

Related discussion:
text: Keep the doc consistent with
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details