labels.facet=分面
labels.geo=地理
labels.groups=组
labels.hash=哈希
labels.kuromojiFile=Kuromoji文件
labels.maxSize=最大大小
labels.order=顺序
labels.purgeSuggestSearchLogDay=删除以前的建议信息
labels.q=查询
labels.roles=角色
labels.suggestSearchLog=建议搜索日志
labels.suggestWord=建议词
labels.targetLabel=标签
labels.term=搜索词
labels.fields=字段
labels.ex_q=扩展查询
labels.oldPassword=当前密码
labels.newPassword=新密码

          <description>The URL of the organization.</description>
          <type>String</type>
        </field>
        <field>
          <name>roles</name>
          <version>3.0.0+</version>
          <description>
            The roles the contributor plays in the project. Each role is described by a
            {@code role} element, the body of which is a role name. This can also be used to

labels.groups=Grupos
labels.hash=Hash
labels.kuromojiFile=Arquivo Kuromoji
labels.maxSize=Tamanho máximo
labels.order=Ordem
labels.purgeSuggestSearchLogDay=Excluir informações de sugestão anteriores
labels.q=Consulta
labels.roles=Funções
labels.suggestSearchLog=Log de pesquisa para sugestões
labels.suggestWord=Palavra sugerida
labels.targetLabel=Rótulo
labels.term=Termo de pesquisa
labels.fields=Campos
labels.ex_q=Consulta estendida

labels.facet=ファセット
labels.geo=ジオ
labels.groups=グループ
labels.hash=ハッシュ
labels.kuromojiFile=Kuromojiファイル
labels.maxSize=最大サイズ
labels.order=順番
labels.purgeSuggestSearchLogDay=以前のサジェスト情報を削除
labels.q=クエリー
labels.roles=ロール
labels.suggestSearchLog=サジェスト用検索ログ
labels.suggestWord=サジェストワード
labels.targetLabel=ラベル
labels.term=検索語
labels.fields=フィールド
labels.ex_q=拡張クエリー
labels.oldPassword=現在のパスワード
labels.newPassword=新しいパスワード

`system:aggregate-to-edit` role no longer includes write access to the Endpoints API. For new Kubernetes 1.22 clusters, the `edit` and `admin` roles will no longer include that access in newly created Kubernetes 1.22 clusters. This will have no affect on existing clusters upgrading to Kubernetes 1.22. To retain write access to Endpoints in the aggregated `edit` and `admin` roles for newly created 1.22 clusters, refer to https://github.com/kubernetes/website/pull/29025. ([#103704](https://github.com/kubernet...

  passed a file which contains RBAC roles, rolebindings, clusterroles, or
  clusterrolebindings, this command computes covers and adds the missing rules.
  The logic required to properly apply RBAC permissions is more complicated
  than a JSON merge because you have to compute logical covers operations between
  rule sets. This means that we cannot use `kubectl apply` to update RBAC roles

- **Auth**
  - [alpha] Further polishing of the Role-based access control alpha API including a default set of cluster roles. ([docs](http://kubernetes.io/docs/admin/authorization/)) ([kubernetes/features#2](https://github.com/kubernetes/enhancements/issues/2))

    it keeps your `HeldCertificate` and its chain. On the client it keeps the root certificates
    that are trusted to sign a server's certificate chain. `HandshakeCertificates` also works with
    mutual TLS where these roles are reversed.

    These classes make it possible to enable HTTPS in MockWebServer in [just a few lines of
    code][https_server_sample].

    /** The key of the message: Query */
    public static final String LABELS_Q = "{labels.q}";

    /** The key of the message: Roles */
    public static final String LABELS_ROLES = "{labels.roles}";

    /** The key of the message: Suggest Search Log */
    public static final String LABELS_SUGGEST_SEARCH_LOG = "{labels.suggestSearchLog}";

* Kubernetes now supports up to 5,000 nodes via etcd v3, which is enabled by default.
* [Role-based access control (RBAC)](https://kubernetes.io//docs/admin/authorization/rbac) has graduated to beta, and defines secure default roles for control plane, node, and controller components.
* The [`kubeadm` cluster bootstrap tool](https://kubernetes.io/docs/getting-started-guides/kubeadm/) has graduated to beta. Some highlights: