Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 16 for aggregated (0.2 sec)

  1. common-protos/k8s.io/api/apidiscovery/v2beta1/generated.proto

    }
    
    // APIGroupDiscoveryList is a resource containing a list of APIGroupDiscovery.
    // This is one of the types able to be returned from the /api and /apis endpoint and contains an aggregated
    // list of API resources (built-ins, Custom Resource Definitions, resources from aggregated servers)
    // that a cluster supports.
    message APIGroupDiscoveryList {
      // ResourceVersion will not be set, because this does not have a replayable ordering among multiple apiservers.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 7.8K bytes
    - Viewed (0)
  2. manifests/charts/istio-control/istio-discovery/values.yaml

        # globally/universally unique. For example, if any of the following are true,
        # then two meshes must have different Mesh IDs:
        # - Meshes will have their telemetry aggregated in one place
        # - Meshes will be federated together
        # - Policy will be written referencing one mesh from the other
        #
        # If an administrator expects that any of these conditions may become true in
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Apr 22 22:00:40 GMT 2024
    - 20.3K bytes
    - Viewed (0)
  3. architecture/security/istio-agent.md

    requests to the agent, causing the agent to submit a CSR to the configured CA (generally Istiod). For other configuration,
    Envoy will send [ADS](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/operations/dynamic_configuration#aggregated-xds-ads)
    requests to the agent, which will be forwarded to the configured discovery server (general Istiod).
    
    ## CA Flow
    
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Aug 22 16:45:50 GMT 2023
    - 7.2K bytes
    - Viewed (1)
  4. manifests/charts/istiod-remote/values.yaml

        # globally/universally unique. For example, if any of the following are true,
        # then two meshes must have different Mesh IDs:
        # - Meshes will have their telemetry aggregated in one place
        # - Meshes will be federated together
        # - Policy will be written referencing one mesh from the other
        #
        # If an administrator expects that any of these conditions may become true in
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Apr 22 22:00:40 GMT 2024
    - 20.2K bytes
    - Viewed (0)
  5. manifests/charts/istiod-remote/templates/reader-serviceaccount.yaml

    # This service account aggregates reader permissions for the revisions in a given cluster
    # Should be used for remote secret creation.
    apiVersion: v1
    kind: ServiceAccount
      {{- if .Values.global.imagePullSecrets }}
    imagePullSecrets:
      {{- range .Values.global.imagePullSecrets }}
      - name: {{ . }}
        {{- end }}
        {{- end }}
    metadata:
      name: istio-reader-service-account
      namespace: {{ .Values.global.istioNamespace }}
      labels:
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Jul 12 16:44:21 GMT 2021
    - 489 bytes
    - Viewed (0)
  6. manifests/charts/base/templates/reader-serviceaccount.yaml

    # This service account aggregates reader permissions for the revisions in a given cluster
    # Should be used for remote secret creation.
    apiVersion: v1
    kind: ServiceAccount
      {{- if .Values.global.imagePullSecrets }}
    imagePullSecrets:
      {{- range .Values.global.imagePullSecrets }}
      - name: {{ . }}
        {{- end }}
        {{- end }}
    metadata:
      name: istio-reader-service-account
      namespace: {{ .Values.global.istioNamespace }}
      labels:
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon May 31 07:10:20 GMT 2021
    - 489 bytes
    - Viewed (0)
  7. operator/cmd/mesh/testdata/manifest-generate/data-snapshot.tar.gz

    the scope where # meshes will interact with each other, but it is not required to be # globally/universally unique. For example, if any of the following are true, # then two meshes must have different Mesh IDs: # - Meshes will have their telemetry aggregated in one place # - Meshes will be federated together # - Policy will be written referencing one mesh from the other # # If an administrator expects that any of these conditions may become true in # the future, they should ensure their meshes have...
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Wed Jan 10 05:10:03 GMT 2024
    - 198.1K bytes
    - Viewed (1)
  8. common-protos/k8s.io/api/rbac/v1/generated.proto

    import "k8s.io/apimachinery/pkg/runtime/schema/generated.proto";
    
    // Package-wide variables from generator "generated".
    option go_package = "k8s.io/api/rbac/v1";
    
    // AggregationRule describes how to locate ClusterRoles to aggregate into the ClusterRole
    message AggregationRule {
      // ClusterRoleSelectors holds a list of selectors which will be used to find ClusterRoles and create the rules.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 7.6K bytes
    - Viewed (0)
  9. manifests/charts/gateways/istio-egress/values.yaml

        # globally/universally unique. For example, if any of the following are true,
        # then two meshes must have different Mesh IDs:
        # - Meshes will have their telemetry aggregated in one place
        # - Meshes will be federated together
        # - Policy will be written referencing one mesh from the other
        #
        # If an administrator expects that any of these conditions may become true in
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Feb 27 16:55:16 GMT 2024
    - 12.4K bytes
    - Viewed (0)
  10. manifests/charts/gateways/istio-ingress/values.yaml

        # globally/universally unique. For example, if any of the following are true,
        # then two meshes must have different Mesh IDs:
        # - Meshes will have their telemetry aggregated in one place
        # - Meshes will be federated together
        # - Policy will be written referencing one mesh from the other
        #
        # If an administrator expects that any of these conditions may become true in
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Feb 27 16:55:16 GMT 2024
    - 13K bytes
    - Viewed (0)
Back to top