* Fix kube-proxy PodSecurityPolicy binding on GCE & GKE. This was only an issue when running kube-proxy as a DaemonSet, with PodSecurityPolicy enabled. ([#72761](https://github.com/kubernetes/kubernetes/pull/72761), [@tallclair](https://github.com/tallclair))

    /**
     * Array of new input character sequences for update operations.
     * When not null, indicates this item has pending updates.
     */
    private String[] newInputs;

    /**
     * The new output character sequence for update operations.
     * When not null, indicates this item has pending updates.
     */
    private String newOutput;

    /**

                            pending = new ArrayList<>();
                        }
                    } else {
                        pending.add(element.clone());
                    }
                }

                List<Plugin> result = new ArrayList<>(src.size() + tgt.size());
                for (Map.Entry<Object, Plugin> entry : master.entrySet()) {

 *
 * ## Warning: Certificate Pinning is Dangerous!
 *
 * Pinning certificates limits your server team's abilities to update their TLS certificates. By
 * pinning certificates, you take on additional operational complexity and limit your ability to
 * migrate between certificate authorities. Do not use certificate pinning without the blessing of
 * your server's TLS administrator!
 *

_2016-02-25_

 *  Fix: Change the certificate pinner to always build full chains. This
    prevents a potential crash when using certificate pinning with the Google
    Play Services security provider.


## Version 2.7.4

_2016-02-07_

 *  Fix: Don't crash when finding the trust manager if the Play Services (GMS)
    security provider is installed.
 *  Fix: The previous release introduced a performance regression on Android,

import javax.inject.Named;
import javax.inject.Singleton;

/**
 * {@code rar} packaging plugins bindings provider for {@code default} lifecycle.
 */
@Named("rar")
@Singleton
public final class RarLifecycleMappingProvider extends AbstractLifecycleMappingProvider {
    // START SNIPPET: rar
    private static final String[] BINDINGS = {
        "process-resources",

import javax.inject.Named;
import javax.inject.Singleton;

/**
 * {@code pom} packaging plugins bindings provider for {@code default} lifecycle.
 */
@Named("pom")
@Singleton
public final class PomLifecycleMappingProvider extends AbstractLifecycleMappingProvider {
    // START SNIPPET: pom
    private static final String[] BINDINGS = {
        "install", "org.apache.maven.plugins:maven-install-plugin:" + INSTALL_PLUGIN_VERSION + ":install",

// - replicated size for all objects sent to this target
// - replica size for all objects received from this target
// - replication pending size for all objects pending replication to this target
// - replication failed size for all objects failed replication to this target
// - replica pending count
// - replica failed count
type BucketTargetUsageInfo struct {
	ReplicationPendingSize  uint64 `json:"objectsPendingReplicationTotalSize"`

# Generate CONTRIBUTORS.md: contributors.sh

# Tip for finding duplicates (besides scanning the output of CONTRIBUTORS.md for name
# duplicates that aren't also email duplicates): scan the output of:
#   git log --format='%aE - %aN' | sort -uf
#
# For explanation on this file format: man git-shortlog

Anand Babu (AB) Periasamy <******@****.***> Anand Babu (AB) Periasamy <******@****.***>
Anand Babu (AB) Periasamy <******@****.***> <******@****.***>

  linking directly to the master branch. This ensures that links reference a
  specific point in time, rather than a document that may change over time.
  
  See here for guidance on getting permanent links to files: https://help.github.com/en/articles/getting-permanent-links-to-files
  
  Please use the following format for linking documentation:
  - [KEP]: <link>
  - [Usage]: <link>