labels.geo=Geo
labels.groups=Gruppi
labels.hash=Hash
labels.maxSize=Dimensione massima
labels.order=Ordine
labels.purgeSuggestSearchLogDay=Elimina informazioni suggerite precedenti
labels.q=Query
labels.roles=Ruoli
labels.suggestSearchLog=Log di ricerca suggeriti
labels.suggestWord=Parola suggerita
labels.targetLabel=Etichetta
labels.term=Termine di ricerca
labels.fields=Campi
labels.ex_q=Query estesa

        secondLine.put("userBoost", item.getUserBoost());
        secondLine.put("score", (item.getQueryFreq() + item.getDocFreq()) * item.getUserBoost());
        secondLine.put("tags", item.getTags());
        secondLine.put("roles", item.getRoles());
        secondLine.put("kinds", Arrays.toString(item.getKinds()));
        secondLine.put("@timestamp", item.getTimestamp());

   * deal with overflow, then stored permits could be given out /slower/ than fresh ones. Thus, we
   * require a (different in each case) function that translates storedPermits to throttling time.
   *
   * This role is played by storedPermitsToWaitTime(double storedPermits, double permitsToTake). The
   * underlying model is a continuous function mapping storedPermits (from 0.0 to maxStoredPermits)

sure to match it to minioAPIPort port: "9000" nodePort: 32000 ## Configure Ingress based on the documentation here: https://kubernetes.io/docs/concepts/services-networking/ingress/ ## ingress: enabled: false # ingressClassName: "" labels: {} # node-role.kubernetes.io/ingress: platform annotations: {} # kubernetes.io/ingress.class: nginx # kubernetes.io/tls-acme: "true" # kubernetes.io/ingress.allow-http: "false" # kubernetes.io/ingress.global-static-ip-name: "" # nginx.ingress.kubernetes.io/secure-backends:...

#### **RBAC**

*   New permissions have been added to default RBAC roles ([#52654](https://github.com/kubernetes/kubernetes/pull/52654),[ @liggitt](https://github.com/liggitt)):
    *   The default admin and edit roles now include read/write permissions
    *   The view role includes read permissions on poddisruptionbudget.policy resources.

labels.errorCountMin=최소 오류 수
labels.facet=패싯
labels.geo=지오
labels.groups=그룹
labels.hash=해시
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=새 비밀번호

        assertEquals("yes", pom.getValue("developers[1]/properties/developer"));
        assertEquals(1, ((List<?>) pom.getValue("developers[1]/roles")).size());
        assertEquals("devel", pom.getValue("developers[1]/roles[1]"));

        assertEquals(1, ((List<?>) pom.getValue("contributors")).size());
        assertEquals("project-contributor", pom.getValue("contributors[1]/name"));

  - The label applied to control-plane nodes "node-role.kubernetes.io/master" is now deprecated and will be removed in a future release after a GA deprecation period.
  - Introduce a new label "node-role.kubernetes.io/control-plane" that will be applied in parallel to "node-role.kubernetes.io/master" until the removal of the "node-role.kubernetes.io/master" label.

`settings/v1alpha1`, and `scheduling/v1alpha1` APIs are disabled by default.

* The `system:node` role is no longer automatically granted to the `system:nodes` group in new clusters. The role gives broad read access to resources, including secrets and configmaps. Use the `Node` authorization mode to authorize the nodes in new clusters. To continue providing the `system:node` role to the members of the `system:nodes` group, create an installation-specific `ClusterRoleBinding` in the installation....

labels.errorCountMin=最小错误数
labels.facet=分面
labels.geo=地理
labels.groups=组
labels.hash=哈希
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=新密码