- [Taints and Tolerations](#taints-and-tolerations)
    - [Volumes](#volumes-2)
  - [Changes to Major Components](#changes-to-major-components)
    - [API Server](#api-server)
    - [API Server Aggregator](#api-server-aggregator)
      - [Generic API Server](#generic-api-server)
    - [Client](#client)
      - [client-go](#client-go)
    - [Cloud Provider](#cloud-provider)
      - [AWS](#aws)
      - [Azure](#azure)

        if (aggregations != null) {
            aggregations.forEach(aggregation -> {
                if (aggregation.getName().startsWith(Constants.FACET_FIELD_PREFIX)) {
                    final Terms termFacet = (Terms) aggregation;
                    fieldList.add(new Field(termFacet));
                } else if (aggregation.getName().startsWith(Constants.FACET_QUERY_PREFIX)) {

- Kube-aggregator: always sets unavailableGauge metric to reflect the current state of a service. ([#87778](https://github.com/kubernetes/kubernetes/pull/87778), [@p0lyn0mial](https://github.com/p0lyn0mial)) [SIG API Machinery]

- Discovery document will correctly return the resources for aggregated apiservers that do not implement aggregated disovery ([#115770](https://github.com/kubernetes/kubernetes/pull/115770), [@Jefftree](https://github.com/Jefftree))

            assertTrue(result.success(), "Orchestrator should succeed");
            assertEquals(2, result.processedPoms().size(), "Should aggregate processed POMs");
            assertEquals(2, result.modifiedPoms().size(), "Should aggregate modified POMs");
            assertEquals(0, result.errorPoms().size(), "Should have no errors");
        }

        @Test

 * and user information logs. It supports different aggregation types for
 * analytics and reporting purposes.
 */
public class SearchLogService {

    /** Date format pattern for parsing time ranges. */
    private static final String YYYY_MM_DD_HH_MM = "yyyy-MM-dd HH:mm";

    /** Field name for count values in aggregation results. */
    private static final String COUNT = "count";

- When proxying to an aggregated API server, kube-apiserver used the
  `EndpointSlices` of the `service` indicated by the `APIServer`, rather than
  using Endpoints.
  
  If you were using the aggregated API server feature, and you were writing out
  the endpoints for it by hand (rather than letting kube-controller-manager

            }
        }

        writer.accept("\t\t-----------------------------------------------------------------------");
        if (mojoExecution.getMojoDescriptor().isAggregator()) {
            writer.accept("\t\tAggregator goal:        " + mojoExecId);
        } else {
            writer.accept("\t\tGoal:                   " + mojoExecId);
        }
        if (mojoExecution.getConfiguration() != null) {

etes-api/migrate-third-party-resource/).

* [beta] User-provided apiservers can be aggregated (served along with) the rest of the Kubernetes API. See [Extending the Kubernetes API with the aggregation layer](https://kubernetes.io/docs/concepts/api-extension/apiserver-aggregation/), [Configure the aggregation layer](https://kubernetes.io/docs/tasks/access-kubernetes-api/configure-aggregation-layer/), and [Setup an extension API server](https://kubernetes.io/docs/tasks/access-kubernete...

([#67349](https://github.com/kubernetes/kubernetes/pull/67349), [@mikedanese](https://github.com/mikedanese))
- The admin RBAC role now aggregates edit and view.  The edit RBAC role now aggregates view.  ([#66684](https://github.com/kubernetes/kubernetes/pull/66684), [@deads2k](https://github.com/deads2k))