Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 8 of 8 for IDs (0.13 sec)

  1. istioctl/pkg/authz/testdata/configdump.yaml

                        }
                       }
                      ],
                      "principals": [
                       {
                        "and_ids": {
                         "ids": [
                          {
                           "or_ids": {
                            "ids": [
                             {
                              "filter_state": {
                               "key": "io.istio.peer_principal",
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Wed Jun 21 14:20:23 GMT 2023
    - 206.7K bytes
    - Viewed (2)
  2. manifests/charts/istiod-remote/values.yaml

        # 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 different Mesh IDs
        # assigned.
        #
    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)
  3. manifests/charts/istio-control/istio-discovery/values.yaml

        # 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 different Mesh IDs
        # assigned.
        #
    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)
  4. src/main/config/openapi/openapi-user.yaml

            '500':
              $ref: '#/components/responses/InternalServerError'
    
      /favorites:
        get:
          tags:
            - favorite
          summary: List favorites
          description: Returns favorited document IDs
          operationId: listFavorites
          parameters:
            - name: queryId
              in: query
              description: Query ID where the document is contained
              required: true
              schema:
    Others
    - Registered: Mon May 06 08:04:11 GMT 2024
    - Last Modified: Mon Jun 19 13:30:00 GMT 2023
    - 21.6K bytes
    - Viewed (1)
  5. common/config/sass-lint.yml

      no-color-keywords: 0
      no-color-literals: 0
      no-combinators: 0
      no-css-comments: 2
      no-debug: 2
      no-disallowed-properties: 2
      no-duplicate-properties: 2
      no-empty-rulesets: 2
      no-extends: 2
      no-ids: 0
      no-invalid-hex: 2
      no-important: 0
      no-mergeable-selectors: 2
      no-misspelled-properties: 2
      no-qualifying-elements: 0
      no-trailing-whitespace: 2
      no-trailing-zero: 2
      no-transition-all: 0
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Wed Sep 11 23:32:21 GMT 2019
    - 2K bytes
    - Viewed (0)
  6. manifests/charts/gateways/istio-egress/values.yaml

        # 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 different Mesh IDs
        # assigned.
        #
    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)
  7. manifests/charts/gateways/istio-ingress/values.yaml

        # 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 different Mesh IDs
        # assigned.
        #
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Feb 27 16:55:16 GMT 2024
    - 13K bytes
    - Viewed (0)
  8. operator/cmd/mesh/testdata/manifest-generate/data-snapshot.tar.gz

    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 different Mesh IDs # assigned. # # Within a multicluster mesh, each cluster must be (manually or auto) # configured...
    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)
Back to top