* action required: Cloud providers other than GCE might want to update their deployments or sample yaml files to reuse the role created via add-on.

### Other notable changes

    /** The key of the message: Upload */
    public static final String LABELS_backup_button_upload = "{labels.backup_button_upload}";

    /** The key of the message: The limit of a search time was exceeded. The partial result might be displayed. */
    public static final String LABELS_process_time_is_exceeded = "{labels.process_time_is_exceeded}";

    /** The key of the message: First Name */

* Add get/delete cluster, delete context to kubectl...

  </mime-type>
  <mime-type type="application/vnd.ibm.modcap">
    <glob pattern="*.afp"/>
    <glob pattern="*.listafp"/>
    <glob pattern="*.list3820"/>
  </mime-type>
  <mime-type type="application/vnd.ibm.rights-management">
    <glob pattern="*.irm"/>
  </mime-type>
  <mime-type type="application/vnd.ibm.secure-container">
    <glob pattern="*.sc"/>
  </mime-type>
  <mime-type type="application/vnd.iccprofile">

					},
				},
				UpdatedAt: acc.UpdatedAt,
			}); err != nil {
				return errSRIAMError(err)
			}
		}
	}

	// Next should be Groups for some of these users, LDAP might have some Group
	// DNs here
	{
		groups := make(map[string]GroupInfo)
		err := globalIAMSys.store.loadGroups(ctx, groups)
		if err != nil {
			return errSRBackendIssue(err)
		}

- Add possibility to configure controller manager to use IPv6 dual stack:
  use `--cluster-cidr="<cidr1>,<cidr2>"`.
  Notes:
  1. Only the first two CIDRs are used (soft limits for Alpha, might be lifted later on).
  2. Only the "RangeAllocator" (default) is allowed as a value for `--cidr-allocator-type`. Cloud allocators are not compatible with IPv6 dual stack

* Fixes issue [[#68899](https://github.com/kubernetes/kubernetes/pull/68899)](https://github.com/kubernetes/kubernetes/issues/68899) where pods might schedule on an unschedulable node. ([#68984](https://github.com/kubernetes/kubernetes/pull/68984), [@k82cn](https://github.com/k82cn))

- Fixes issue [#68899](https://github.com/kubernetes/kubernetes/issues/68899) where pods might schedule on an unschedulable node. ([#68984](https://github.com/kubernetes/kubernetes/issues/68984), [@k82cn](https://github.com/k82cn))

### Not Very Notable (that is, non-user-facing)

- Failed pods associated with a job with `parallelism = 1` are recreated by the job controller honoring exponential backoff delay again. However, for jobs with `parallelism > 1`, pods might be created without exponential backoff delay. ([#115022](https://github.com/kubernetes/kubernetes/pull/115022), [@nikhita](https://github.com/nikhita)) [SIG Apps]